draft-ietf-teas-yang-te-topo-19.txt		draft-ietf-teas-yang-te-topo-20.txt
	TEAS Working Group Xufeng Liu		TEAS Working Group Xufeng Liu
	Internet Draft Volta Networks		Internet Draft Volta Networks
	Intended status: Standards Track Igor Bryskin		Intended status: Standards Track Igor Bryskin
	Huawei Technologies		Huawei Technologies
	Vishnu Pavan Beeram		Vishnu Pavan Beeram
	Juniper Networks
	Tarek Saad		Tarek Saad
	Cisco Systems Inc		Juniper Networks
	Himanshu Shah		Himanshu Shah
	Ciena		Ciena
	Oscar Gonzalez De Dios		Oscar Gonzalez De Dios
	Telefonica		Telefonica
	Expires: August 11, 2019 February 11, 2019		Expires: October 12, 2019 April 12, 2019
	YANG Data Model for Traffic Engineering (TE) Topologies		YANG Data Model for Traffic Engineering (TE) Topologies
	draft-ietf-teas-yang-te-topo-19		draft-ietf-teas-yang-te-topo-20
	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 1, line 41 ¶		skipping to change at page 1, line 40 ¶
	and may be updated, replaced, or obsoleted by other documents at any		and may be updated, replaced, or obsoleted by other documents at any
	time. It is inappropriate to use Internet-Drafts as reference		time. It is inappropriate to use Internet-Drafts as reference
	material or to cite them other than as "work in progress."		material or to cite them other than as "work in progress."
	The list of current Internet-Drafts can be accessed at		The list of current Internet-Drafts can be accessed at
	http://www.ietf.org/ietf/1id-abstracts.txt		http://www.ietf.org/ietf/1id-abstracts.txt
	The list of Internet-Draft Shadow Directories can be accessed at		The list of Internet-Draft Shadow Directories can be accessed at
	http://www.ietf.org/shadow.html		http://www.ietf.org/shadow.html
	This Internet-Draft will expire on August 11, 2019.		This Internet-Draft will expire on October 12, 2019.
	Copyright Notice		Copyright Notice
	Copyright (c) 2019 IETF Trust and the persons identified as the		Copyright (c) 2019 IETF Trust and the persons identified as the
	document authors. All rights reserved.		document authors. All rights reserved.
	This document is subject to BCP 78 and the IETF Trust's Legal		This document is subject to BCP 78 and the IETF Trust's Legal
	Provisions Relating to IETF Documents		Provisions Relating to IETF Documents
	(http://trustee.ietf.org/license-info) in effect on the date of		(http://trustee.ietf.org/license-info) in effect on the date of
	publication of this document. Please review these documents		publication of this document. Please review these documents
	skipping to change at page 32, line 46 ¶		skipping to change at page 32, line 46 ¶
	to the corresponding configuration.		to the corresponding configuration.
	5.10. Scheduling Parameters		5.10. Scheduling Parameters
	The model allows time scheduling parameters to be specified for each		The model allows time scheduling parameters to be specified for each
	topological element or for the topology as a whole. These parameters		topological element or for the topology as a whole. These parameters
	allow the provider to present different topological views to the		allow the provider to present different topological views to the
	client at different time slots. The use of "scheduling parameters" is		client at different time slots. The use of "scheduling parameters" is
	optional.		optional.
	The YANG data model for configuration scheduling is defined in [I-		The YANG data model for configuration scheduling is defined in
	D.liu-netmod-yang-schedule], which allows specifying configuration		[I-D.liu-netmod-yang-schedule], which allows specifying configuration
	schedules without altering this data model.		schedules without altering this data model.
	5.11. Notifications		5.11. Notifications
	Notifications are a key component of any topology data model.		Notifications are a key component of any topology data model.
	[I-D.ietf-netconf-subscribed-notifications] and [I-D.ietf-netconf-		[I-D.ietf-netconf-subscribed-notifications] and
	yang-push] define a subscription and push mechanism for YANG		[I-D.ietf-netconf-yang-push] define a subscription and push mechanism
	datastores. This mechanism currently allows the user to:		for YANG datastores. This mechanism currently allows the user to:
	- Subscribe notifications on a per client basis		- Subscribe notifications on a per client basis
	- Specify subtree filters or xpath filters so that only interested		- Specify subtree filters or xpath filters so that only interested
	contents will be sent.		contents will be sent.
	- Specify either periodic or on-demand notifications.		- Specify either periodic or on-demand notifications.
	6. Guidance for Writing Technology Specific TE Topology Augmentations		6. Guidance for Writing Technology Specific TE Topology Augmentations
	The TE topology model defined in this document is technology agnostic		The TE topology model defined in this document is technology agnostic
	as it defines concepts, abstractions and attributes that are common		as it defines concepts, abstractions and attributes that are common
	across multiple network technologies. It is envisioned that this base		across multiple network technologies. It is envisioned that this base
	model will be widely used when defining technology specific TE		model will be widely used when defining technology specific TE
	topology models for various layer networks. [I-D.ietf-ccamp-wson-		topology models for various layer networks.
	yang], [I-D.ietf-ccamp-otn-topo-yang], and [I-D.ietf-teas-yang-l3-te-		[I-D.ietf-ccamp-wson-yang], [I-D.ietf-ccamp-otn-topo-yang], and
	topo] are some examples of technology specific TE Topology models.		[I-D.ietf-teas-yang-l3-te-topo] are some examples of technology
	Writers of such models are encouraged to augment the basic TE		specific TE Topology models. Writers of such models are encouraged to
	topology model's containers, such as TE Topology, TE Node, TE Link,		augment the basic TE topology model's containers, such as TE
	Link Termination Point (LTP), Tunnel Termination Point (TTP),		Topology, TE Node, TE Link, Link Termination Point (LTP), Tunnel
	Bandwidth and Label with the layer specific attributes instead of		Termination Point (TTP), Bandwidth and Label with the layer specific
	defining new containers.		attributes instead of defining new containers.
	Consider the following technology specific example-topology model:		Consider the following technology specific example-topology model:
	module: example-topology		module: example-topology
	augment /nw:networks/nw:network/nw:network-types/tet:te-topology:		augment /nw:networks/nw:network/nw:network-types/tet:te-topology:
	+--rw example-topology!		+--rw example-topology!
	augment /nw:networks/nw:network/tet:te:		augment /nw:networks/nw:network/tet:te:
	+--rw attributes		+--rw attributes
	+--rw attribute-1? uint8		+--rw attribute-1? uint8
	augment /nw:networks/nw:network/nw:node/tet:te		augment /nw:networks/nw:network/nw:node/tet:te
	skipping to change at page 47, line 22 ¶		skipping to change at page 47, line 22 ¶
	Editor: Xufeng Liu		Editor: Xufeng Liu
	<mailto:xufeng.liu.ietf@gmail.com>		<mailto:xufeng.liu.ietf@gmail.com>
	Editor: Igor Bryskin		Editor: Igor Bryskin
	<mailto:Igor.Bryskin@huawei.com>		<mailto:Igor.Bryskin@huawei.com>
	Editor: Vishnu Pavan Beeram		Editor: Vishnu Pavan Beeram
	<mailto:vbeeram@juniper.net>		<mailto:vbeeram@juniper.net>
	Editor: Tarek Saad		Editor: Tarek Saad
	<mailto:tsaad@cisco.com>		<mailto:tsaad@juniper.net>
	Editor: Himanshu Shah		Editor: Himanshu Shah
	<mailto:hshah@ciena.com>		<mailto:hshah@ciena.com>
	Editor: Oscar Gonzalez De Dios		Editor: Oscar Gonzalez De Dios
	<mailto:oscar.gonzalezdedios@telefonica.com>";		<mailto:oscar.gonzalezdedios@telefonica.com>";
	description		description
	"TE topology model for representing and manipulating technology		"TE topology model for representing and manipulating technology
	agnostic TE Topologies.		agnostic TE Topologies.
	skipping to change at page 92, line 18 ¶		skipping to change at page 92, line 18 ¶
	<CODE ENDS>		<CODE ENDS>
	8. Security Considerations		8. Security Considerations
	The YANG module specified in this document defines a schema for data		The YANG module specified in this document defines a schema for data
	that is designed to be accessed via network management protocols such		that is designed to be accessed via network management protocols such
	as NETCONF [RFC6241] or RESTCONF [RFC8040]. The lowest NETCONF layer		as NETCONF [RFC6241] or RESTCONF [RFC8040]. The lowest NETCONF layer
	is the secure transport layer, and the mandatory-to-implement secure		is the secure transport layer, and the mandatory-to-implement secure
	transport is Secure Shell (SSH) [RFC6242]. The lowest RESTCONF layer		transport is Secure Shell (SSH) [RFC6242]. The lowest RESTCONF layer
	is HTTPS, and the mandatory-to-implement secure transport is TLS		is HTTPS, and the mandatory-to-implement secure transport is TLS
	[RFC5246].		[RFC8446].
	The NETCONF access control model [RFC6536] provides the means to		The Network Configuration Access Control Model (NACM) [RFC8341]
	restrict access for particular NETCONF or RESTCONF users to a		provides the means to restrict access for particular NETCONF or
	preconfigured subset of all available NETCONF or RESTCONF protocol		RESTCONF users to a preconfigured subset of all available NETCONF or
	operations and content.		RESTCONF protocol operations and content.
	There are a number of data nodes defined in this YANG module that are		There are a number of data nodes defined in this YANG module that are
	writable/creatable/deletable (i.e., config true, which is the		writable/creatable/deletable (i.e., config true, which is the
	default). These data nodes may be considered sensitive or vulnerable		default). These data nodes may be considered sensitive or vulnerable
	in some network environments. Write operations (e.g., edit-config) to		in some network environments. Write operations (e.g., edit-config) to
	these data nodes without proper protection can have a negative effect		these data nodes without proper protection can have a negative effect
	on network operations. These are the subtrees and data nodes and		on network operations. These are the subtrees and data nodes and
	their sensitivity/vulnerability:		their sensitivity/vulnerability:
	o /nw:networks/nw:network/nw:network-types/tet:te-topology		o /nw:networks/nw:network/nw:network-types/tet:te-topology
	skipping to change at page 95, line 6 ¶		skipping to change at page 95, line 6 ¶
	[RFC3688] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688,		[RFC3688] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688,
	DOI 10.17487/RFC3688, January 2004,		DOI 10.17487/RFC3688, January 2004,
	<https://www.rfc-editor.org/info/rfc3688>.		<https://www.rfc-editor.org/info/rfc3688>.
	[RFC3945] Mannie, E., Ed., "Generalized Multi-Protocol Label		[RFC3945] Mannie, E., Ed., "Generalized Multi-Protocol Label
	Switching (GMPLS) Architecture", RFC 3945,		Switching (GMPLS) Architecture", RFC 3945,
	DOI 10.17487/RFC3945, October 2004,		DOI 10.17487/RFC3945, October 2004,
	<https://www.rfc-editor.org/info/rfc3945>.		<https://www.rfc-editor.org/info/rfc3945>.
	[RFC5246] Dierks, T. and E. Rescorla, "The Transport Layer Security
	(TLS) Protocol Version 1.2", RFC 5246,
	DOI 10.17487/RFC5246, August 2008,
	<https://www.rfc-editor.org/info/rfc5246>.
	[RFC6241] Enns, R., Ed., Bjorklund, M., Ed., Schoenwaelder, J., Ed.,		[RFC6241] Enns, R., Ed., Bjorklund, M., Ed., Schoenwaelder, J., Ed.,
	and A. Bierman, Ed., "Network Configuration Protocol		and A. Bierman, Ed., "Network Configuration Protocol
	(NETCONF)", RFC 6241, DOI 10.17487/RFC6241, June 2011,		(NETCONF)", RFC 6241, DOI 10.17487/RFC6241, June 2011,
	<https://www.rfc-editor.org/info/rfc6241>.		<https://www.rfc-editor.org/info/rfc6241>.
	[RFC6242] Wasserman, M., "Using the NETCONF Protocol over Secure		[RFC6242] Wasserman, M., "Using the NETCONF Protocol over Secure
	Shell (SSH)", RFC 6242, DOI 10.17487/RFC6242, June 2011,		Shell (SSH)", RFC 6242, DOI 10.17487/RFC6242, June 2011,
	<https://www.rfc-editor.org/info/rfc6242>.		<https://www.rfc-editor.org/info/rfc6242>.
	[RFC6536] Bierman, A. and M. Bjorklund, "Network Configuration
	Protocol (NETCONF) Access Control Model", RFC 6536,
	DOI 10.17487/RFC6536, March 2012,
	<https://www.rfc-editor.org/info/rfc6536>.
	[RFC6991] Schoenwaelder, J., Ed., "Common YANG Data Types",		[RFC6991] Schoenwaelder, J., Ed., "Common YANG Data Types",
	RFC 6991, DOI 10.17487/RFC6991, July 2013,		RFC 6991, DOI 10.17487/RFC6991, July 2013,
	<https://www.rfc-editor.org/info/rfc6991>.		<https://www.rfc-editor.org/info/rfc6991>.
	[RFC7926] Farrel, A., Ed., Drake, J., Bitar, N., Swallow, G.,		[RFC7926] Farrel, A., Ed., Drake, J., Bitar, N., Swallow, G.,
	Ceccarelli, D., and X. Zhang, "Problem Statement and		Ceccarelli, D., and X. Zhang, "Problem Statement and
	Architecture for Information Exchange between		Architecture for Information Exchange between
	Interconnected Traffic-Engineered Networks", BCP 206,		Interconnected Traffic-Engineered Networks", BCP 206,
	RFC 7926, DOI 10.17487/RFC7926, July 2016,		RFC 7926, DOI 10.17487/RFC7926, July 2016,
	<https://www.rfc-editor.org/info/rfc7926>.		<https://www.rfc-editor.org/info/rfc7926>.
	skipping to change at page 95, line 48 ¶		skipping to change at page 95, line 38 ¶
	<https://www.rfc-editor.org/info/rfc7950>.		<https://www.rfc-editor.org/info/rfc7950>.
	[RFC8040] Bierman, A., Bjorklund, M., and K. Watsen, "RESTCONF		[RFC8040] Bierman, A., Bjorklund, M., and K. Watsen, "RESTCONF
	Protocol", RFC 8040, DOI 10.17487/RFC8040, January 2017,		Protocol", RFC 8040, DOI 10.17487/RFC8040, January 2017,
	<https://www.rfc-editor.org/info/rfc8040>.		<https://www.rfc-editor.org/info/rfc8040>.
	[RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC		[RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC
	2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174,		2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174,
	May 2017, <https://www.rfc-editor.org/info/rfc8174>.		May 2017, <https://www.rfc-editor.org/info/rfc8174>.
			[RFC8341] Bierman, A. and M. Bjorklund, "Network Configuration
			Access Control Model", STD 91, RFC 8341, DOI
			10.17487/RFC8341, March 2018, <https://www.rfc-
			editor.org/info/rfc8341>.
	[RFC8342] Bjorklund, M., Schoenwaelder, J., Shafer, P., Watsen, K.,		[RFC8342] Bjorklund, M., Schoenwaelder, J., Shafer, P., Watsen, K.,
	and R. Wilton, "Network Management Datastore Architecture		and R. Wilton, "Network Management Datastore Architecture
	(NMDA)", RFC 8342, DOI 10.17487/RFC8342, March 2018,		(NMDA)", RFC 8342, DOI 10.17487/RFC8342, March 2018,
	<https://www.rfc-editor.org/info/rfc8342>.		<https://www.rfc-editor.org/info/rfc8342>.
	[RFC8345] Clemm, A., Medved, J., Varga, R., Bahadur, N.,		[RFC8345] Clemm, A., Medved, J., Varga, R., Bahadur, N.,
	Ananthakrishnan, H., and X. Liu, "A YANG Data Model for		Ananthakrishnan, H., and X. Liu, "A YANG Data Model for
	Network Topologies", RFC 8345, DOI 10.17487/RFC8345, March		Network Topologies", RFC 8345, DOI 10.17487/RFC8345, March
	2018, <https://www.rfc-editor.org/info/rfc8345>.		2018, <https://www.rfc-editor.org/info/rfc8345>.
			[RFC8446] Rescorla, E., "The Transport Layer Security (TLS) Protocol
			Version 1.3", RFC 8446, DOI 10.17487/RFC8446, August
			2018, <https://www.rfc-editor.org/info/rfc8446>.
	[I-D.ietf-teas-yang-te-types]		[I-D.ietf-teas-yang-te-types]
	Saad, T., Gandhi, R., Liu, X., Beeram, V., and		Saad, T., Gandhi, R., Liu, X., Beeram, V., and
	I. Bryskin, "Traffic Engineering Common YANG Types",		I. Bryskin, "Traffic Engineering Common YANG Types",
	draft-ietf-teas-yang-te-types-03 (work in progress),		draft-ietf-teas-yang-te-types-08 (work in progress),
	January 2019.		April 2019.
	10.2. Informative References		10.2. Informative References
	[G.709] ITU-T, "Interfaces for the optical transport network",		[G.709] ITU-T, "Interfaces for the optical transport network",
	ITU-T Recommendation G.709, June 2016.		ITU-T Recommendation G.709, June 2016.
	[G.805] ITU-T, "Generic functional architecture of transport		[G.805] ITU-T, "Generic functional architecture of transport
	networks", ITU-T Recommendation G.805, March 2000.		networks", ITU-T Recommendation G.805, March 2000.
	[G.872] ITU-T, "Architecture of optical transport networks", ITU-T		[G.872] ITU-T, "Architecture of optical transport networks", ITU-T
	skipping to change at page 99, line 20 ¶		skipping to change at page 99, line 19 ¶
	<https://www.rfc-editor.org/info/rfc7752>.		<https://www.rfc-editor.org/info/rfc7752>.
	[RFC8340] Bjorklund, M. and L. Berger, Ed., "YANG Tree Diagrams",		[RFC8340] Bjorklund, M. and L. Berger, Ed., "YANG Tree Diagrams",
	BCP 215, RFC 8340, DOI 10.17487/RFC8340, March 2018,		BCP 215, RFC 8340, DOI 10.17487/RFC8340, March 2018,
	<https://www.rfc-editor.org/info/rfc8340>.		<https://www.rfc-editor.org/info/rfc8340>.
	[I-D.ietf-netconf-subscribed-notifications]		[I-D.ietf-netconf-subscribed-notifications]
	Voit, E., Clemm, A., Prieto, A., Nilsen-Nygaard, E., and		Voit, E., Clemm, A., Prieto, A., Nilsen-Nygaard, E., and
	A. Tripathy, "Customized Subscriptions to a Publisher's		A. Tripathy, "Customized Subscriptions to a Publisher's
	Event Streams", draft-ietf-netconf-subscribed-		Event Streams", draft-ietf-netconf-subscribed-
	notifications-12 (work in progress), April 2018.		notifications-23 (work in progress), February 2019.
	[I-D.ietf-netconf-yang-push]		[I-D.ietf-netconf-yang-push]
	Clemm, A., Voit, E., Prieto, A., Tripathy, A., Nilsen-		Clemm, A., Voit, E., Prieto, A., Tripathy, A., Nilsen-
	Nygaard, E., Bierman, A., and B. Lengyel, "YANG Datastore		Nygaard, E., Bierman, A., and B. Lengyel, "YANG Datastore
	Subscription", draft-ietf-netconf-yang-push-16 (work in		Subscription", draft-ietf-netconf-yang-push-22 (work in
	progress), May 2018.		progress), February 2019.
	[I-D.liu-netmod-yang-schedule]		[I-D.liu-netmod-yang-schedule]
	Liu, X., Bryskin, I., Beeram, V., Saad, T., Shah, H., and		Liu, X., Bryskin, I., Beeram, V., Saad, T., Shah, H., and
	O. Dios, "A YANG Data Model for Configuration Scheduling",		O. Dios, "A YANG Data Model for Configuration Scheduling",
	draft-liu-netmod-yang-schedule-05 (work in progress),		draft-liu-netmod-yang-schedule-05 (work in progress),
	March 2018.		March 2018.
	[I-D.ietf-ccamp-wson-yang]		[I-D.ietf-ccamp-wson-yang]
	Lee, Y., Dhody, D., Zhang, X., Guo, A., Lopezalvarez, V.,		Lee, Y., Dhody, D., Zhang, X., Guo, A., Lopezalvarez, V.,
	King, D., Yoon, B., and R. Vilata, "A Yang Data Model for		King, D., Yoon, B., and R. Vilata, "A Yang Data Model for
	WSON Optical Networks", draft-ietf-ccamp-wson-yang-10		WSON Optical Networks", draft-ietf-ccamp-wson-yang-20
	(work in progress), February 2018.		(work in progress), March 2019.
	[I-D.ietf-ccamp-otn-topo-yang]		[I-D.ietf-ccamp-otn-topo-yang]
	zhenghaomian@huawei.com, z., Guo, A., Busi, I., Sharma,		zhenghaomian@huawei.com, z., Guo, A., Busi, I., Sharma,
	A., Liu, X., Belotti, S., Xu, Y., Wang, L., and O. Dios,		A., Liu, X., Belotti, S., Xu, Y., Wang, L., and O. Dios,
	"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-06 (work in
	progress), June 2018.		progress), February 2019.
	[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-04 (work in progress),
	March 2018.		March 2019.
	[I-D.ietf-teas-te-topo-and-tunnel-modeling]		[I-D.ietf-teas-te-topo-and-tunnel-modeling]
	Bryskin, I., Beeram, V., Saad, T., and X. Liu, "TE		Bryskin, I., Beeram, V., Saad, T., and X. Liu, "TE
	Topology and Tunnel Modeling for Transport Networks",		Topology and Tunnel Modeling for Transport Networks",
	draft-ietf-teas-te-topo-and-tunnel-modeling-01 (work in		draft-ietf-teas-te-topo-and-tunnel-modeling-03 (work in
	progress), March 2018.		progress), October 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
	skipping to change at page 164, line 31 ¶		skipping to change at page 164, line 31 ¶
	Editor: Xufeng Liu		Editor: Xufeng Liu
	<mailto:xufeng.liu.ietf@gmail.com>		<mailto:xufeng.liu.ietf@gmail.com>
	Editor: Igor Bryskin		Editor: Igor Bryskin
	<mailto:Igor.Bryskin@huawei.com>		<mailto:Igor.Bryskin@huawei.com>
	Editor: Vishnu Pavan Beeram		Editor: Vishnu Pavan Beeram
	<mailto:vbeeram@juniper.net>		<mailto:vbeeram@juniper.net>
	Editor: Tarek Saad		Editor: Tarek Saad
	<mailto:tsaad@cisco.com>		<mailto:tsaad@juniper.net>
	Editor: Himanshu Shah		Editor: Himanshu Shah
	<mailto:hshah@ciena.com>		<mailto:hshah@ciena.com>
	Editor: Oscar Gonzalez De Dios		Editor: Oscar Gonzalez De Dios
	<mailto:oscar.gonzalezdedios@telefonica.com>";		<mailto:oscar.gonzalezdedios@telefonica.com>";
	description		description
	"TE topology state model.		"TE topology state model.
	skipping to change at page 210, line 44 ¶		skipping to change at page 210, line 44 ¶
	Igor Bryskin		Igor Bryskin
	Huawei Technologies		Huawei Technologies
	Email: Igor.Bryskin@huawei.com		Email: Igor.Bryskin@huawei.com
	Vishnu Pavan Beeram		Vishnu Pavan Beeram
	Juniper Networks		Juniper Networks
	Email: vbeeram@juniper.net		Email: vbeeram@juniper.net
	Tarek Saad		Tarek Saad
	Cisco Systems Inc		Juniper Networks
	Email: tsaad@cisco.com		Email: tsaad@juniper.net
	Himanshu Shah		Himanshu Shah
	Ciena		Ciena
	Email: hshah@ciena.com		Email: hshah@ciena.com
	Oscar Gonzalez De Dios		Oscar Gonzalez De Dios
	Telefonica		Telefonica
	Email: oscar.gonzalezdedios@telefonica.com		Email: oscar.gonzalezdedios@telefonica.com
End of changes. 24 change blocks.
	50 lines changed or deleted		48 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/