draft-ietf-teas-yang-te-topo-17.txt		draft-ietf-teas-yang-te-topo-18.txt
	skipping to change at page 1, line 15 ¶		skipping to change at page 1, line 15 ¶
	Huawei Technologies		Huawei Technologies
	Vishnu Pavan Beeram		Vishnu Pavan Beeram
	Juniper Networks		Juniper Networks
	Tarek Saad		Tarek Saad
	Cisco Systems Inc		Cisco Systems Inc
	Himanshu Shah		Himanshu Shah
	Ciena		Ciena
	Oscar Gonzalez De Dios		Oscar Gonzalez De Dios
	Telefonica		Telefonica
	Expires: December 23, 2018 June 23, 2018		Expires: December 27, 2018 June 27, 2018
	YANG Data Model for Traffic Engineering (TE) Topologies		YANG Data Model for Traffic Engineering (TE) Topologies
	draft-ietf-teas-yang-te-topo-17		draft-ietf-teas-yang-te-topo-18
	Status of this Memo		Status of this Memo
	This Internet-Draft is submitted in full conformance with the		This Internet-Draft is submitted in full conformance with the
	provisions of BCP 78 and BCP 79.		provisions of BCP 78 and BCP 79.
	Internet-Drafts are working documents of the Internet Engineering		Internet-Drafts are working documents of the Internet Engineering
	Task Force (IETF), its areas, and its working groups. Note that		Task Force (IETF), its areas, and its working groups. Note that
	other groups may also distribute working documents as Internet-		other groups may also distribute working documents as Internet-
	Drafts.		Drafts.
	skipping to change at page 5, line 50 ¶		skipping to change at page 5, line 50 ¶
	- TE Topologies are protocol independent. Information about		- TE Topologies are protocol independent. Information about
	topological elements may be learnt via link-state protocols, but		topological elements may be learnt via link-state protocols, but
	the topology can exist without being dependent on any particular		the topology can exist without being dependent on any particular
	protocol.		protocol.
	- TE Topology may not be congruent to the routing topology in a		- TE Topology may not be congruent to the routing topology in a
	given TE System. The routing topology is constructed based on		given TE System. The routing topology is constructed based on
	routing adjacencies. There isn't always a one-to-one association		routing adjacencies. There isn't always a one-to-one association
	between a TE-link and a routing adjacency. For example, the		between a TE-link and a routing adjacency. For example, the
	presence of a TE link between a pair of nodes doesn't necessarily		presence of a TE link between a pair of nodes doesn't necessarily
	imply the existence of a routing-adjacency between these nodes.		imply the existence of a routing-adjacency between these nodes. To
			learn more, see [I-D.ietf-teas-te-topo-and-tunnel-modeling] and
			[I-D.ietf-teas-yang-l3-te-topo].
	- Each TE Topological element has at least one information source		- Each TE Topological element has at least one information source
	associated with it. In some scenarios, there could be more than		associated with it. In some scenarios, there could be more than
	one information source associated with any given topological		one information source associated with any given topological
	element.		element.
	- TE Topologies can be hierarchical. Each node and link of a given		- TE Topologies can be hierarchical. Each node and link of a given
	TE Topology can be associated with respective underlay topology.		TE Topology can be associated with respective underlay topology.
	This means that each node and link of a given TE Topology can be		This means that each node and link of a given TE Topology can be
	associated with an independent stack of supporting TE Topologies.		associated with an independent stack of supporting TE Topologies.
	skipping to change at page 100, line 22 ¶		skipping to change at page 100, line 22 ¶
	"A YANG Data Model for Optical Transport Network		"A YANG Data Model for Optical Transport Network
	Topology", draft-ietf-ccamp-otn-topo-yang-03 (work in		Topology", draft-ietf-ccamp-otn-topo-yang-03 (work in
	progress), June 2018.		progress), June 2018.
	[I-D.ietf-teas-yang-l3-te-topo]		[I-D.ietf-teas-yang-l3-te-topo]
	Liu, X., Bryskin, I., Beeram, V., Saad, T., Shah, H., and		Liu, X., Bryskin, I., Beeram, V., Saad, T., Shah, H., and
	O. Dios, "YANG Data Model for Layer 3 TE Topologies",		O. Dios, "YANG Data Model for Layer 3 TE Topologies",
	draft-ietf-teas-yang-l3-te-topo-01 (work in progress),		draft-ietf-teas-yang-l3-te-topo-01 (work in progress),
	March 2018.		March 2018.
			[I-D.ietf-teas-te-topo-and-tunnel-modeling]
			Bryskin, I., Beeram, V., Saad, T., and X. Liu, "TE
			Topology and Tunnel Modeling for Transport Networks",
			draft-ietf-teas-te-topo-and-tunnel-modeling-01 (work in
			progress), March 2018.
	11. Acknowledgments		11. Acknowledgments
	The authors would like to thank Lou Berger, Sue Hares, Mazen Khaddam,		The authors would like to thank Lou Berger, Sue Hares, Mazen Khaddam,
	Cyril Margaria and Zafar Ali for participating in design discussions		Cyril Margaria and Zafar Ali for participating in design discussions
	and providing valuable insights.		and providing valuable insights.
	Appendix A. Complete Model Tree Structure		Appendix A. Complete Model Tree Structure
	module: ietf-te-topology		module: ietf-te-topology
	augment /nw:networks/nw:network/nw:network-types:		augment /nw:networks/nw:network/nw:network-types:
End of changes. 4 change blocks.
	3 lines changed or deleted		11 lines changed or added
This html diff was produced by rfcdiff 1.47. The latest version is available from http://tools.ietf.org/tools/rfcdiff/