draft-ietf-mpls-tp-rosetta-stone-08.txt		draft-ietf-mpls-tp-rosetta-stone-09.txt
	MPLS Working Group H. van Helvoort (Ed)		MPLS Working Group H. van Helvoort (Ed)
	Internet Draft Huawei Technologies		Internet Draft Huawei Technologies
	Intended status: Informational		Intended status: Informational
	Expires: July 2013 L. Andersson (Ed)		Expires: July 2013 L. Andersson (Ed)
	Ericsson		Huawei Technologies
	N. Sprecher (Ed)		N. Sprecher (Ed)
	Nokia Siemens Networks		Nokia Siemens Networks
	January 15, 2013		January 20, 2013
	A Thesaurus for the Terminology used in Multiprotocol Label		A Thesaurus for the Terminology used in Multiprotocol Label
	Switching Transport Profile (MPLS-TP) drafts/RFCs and ITU-T's		Switching Transport Profile (MPLS-TP) drafts/RFCs and ITU-T's
	Transport Network Recommendations.		Transport Network Recommendations.
	draft-ietf-mpls-tp-rosetta-stone-08		draft-ietf-mpls-tp-rosetta-stone-09
	Status of this Memo		Status of this Memo
	This Internet-Draft is submitted to IETF in full conformance with		This Internet-Draft is submitted to IETF in full conformance with
	the provisions of BCP 78 and BCP 79.		the 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 3, line 16		skipping to change at page 3, line 16
	3.17. Span: 9		3.17. Span: 9
	3.18. Sublayer: 9		3.18. Sublayer: 9
	3.19. Tandem Connection: 9		3.19. Tandem Connection: 9
	3.20. Transport Network: 9		3.20. Transport Network: 9
	3.21. Transport path: 10		3.21. Transport path: 10
	3.22. Transport path layer: 10		3.22. Transport path layer: 10
	3.23. Transport service layer: 10		3.23. Transport service layer: 10
	3.24. Transmission media layer: 10		3.24. Transmission media layer: 10
	3.25. Unidirectional path: 10		3.25. Unidirectional path: 10
	3.26. Failure: 10		3.26. Failure: 10
	3.27. Fault: 11		3.27. Fault: 10
	3.28. Defect: 11		3.28. Defect: 11
	3.29. MPLS Transport Profile (MPLS-TP): 11		3.29. MPLS Transport Profile (MPLS-TP): 11
	3.30. MPLS Section: 11		3.30. MPLS Section: 11
	3.31. MPLS-TP NE: 11		3.31. MPLS-TP NE: 11
	3.32. MPLS-TP network: 11		3.32. MPLS-TP network: 11
	3.33. Equipment Management Function (EMF): 11		3.33. Equipment Management Function (EMF): 11
	3.34. Data Communication Network (DCN): 11		3.34. Data Communication Network (DCN): 11
	3.35. Communication Channel (CC): 12		3.35. Communication Channel (CC): 11
	3.36. Embedded Communication Channel (ECC): 12		3.36. Embedded Communication Channel (ECC): 12
	3.37. Management Communication Channel (MCC): 12		3.37. Management Communication Channel (MCC): 12
	3.38. Management Communication Network (MCN): 12		3.38. Management Communication Network (MCN): 12
	3.39. Signaling Communication Channel (SCC): 12		3.39. Signaling Communication Channel (SCC): 12
	3.40. Signaling Communication Network (SCN): 12		3.40. Signaling Communication Network (SCN): 12
	3.41. Operations System (OS): 12		3.41. Operations System (OS): 12
	3.42. OAM flow: 12		3.42. OAM flow: 12
	3.43. Maintenance Entity Group (MEG): 13		3.43. Maintenance Entity Group (MEG): 13
	3.44. Maintenance Entity (ME): 13		3.44. Maintenance Entity (ME): 13
	3.45. Maintenance Entity Group End Point (MEP): 13		3.45. Maintenance Entity Group End Point (MEP): 13
	skipping to change at page 5, line 29		skipping to change at page 5, line 29
	SCC Signaling Communication Channel		SCC Signaling Communication Channel
	SCN Signaling Communication Network		SCN Signaling Communication Network
	2. Terminology		2. Terminology
	2.1. MPLS-TP Terminology Sources		2.1. MPLS-TP Terminology Sources
	MPLS-TP terminology is principally defined in [RFC3031]. Other		MPLS-TP terminology is principally defined in [RFC3031]. Other
	documents provide further key definitions including [RFC4397], and		documents provide further key definitions including [RFC4397].
	[RFC....].
	2.2. ITU-T Transport Network Terminology Sources		2.2. ITU-T Transport Network Terminology Sources
	The ITU-T Transport Network is specified in a number of		The ITU-T Transport Network is specified in a number of
	recommendations: generic functional architectures and requirements		recommendations: generic functional architectures and requirements
	are specified in Error! Reference source not found., Error!		are specified in [ITU-T_G.805], [ITU-T_G.806], and [ITU-T_G.872].
	Reference source not found., and Error! Reference source not found..		ITU-T Recommendation [ITU-T_G.8101] contains an overview of the
	ITU-T Recommendation Error! Reference source not found. contains an		Terms and Definitions for transport MPLS.
	overview of the Terms and Definitions for transport MPLS.
	2.3. Common Terminology Sources		2.3. Common Terminology Sources
	The work in this document builds on the shared view of MPLS		The work in this document builds on the shared view of MPLS
	requirements.		requirements.
	The following sources are used:		The following sources are used:
	IETF framework and requirements RFCs: [RFC6371], [RFC6372],		IETF framework and requirements RFCs: [RFC6371], [RFC6372],
	[RFC5654], [RFC5921], [RFC5860], [RFC5951], [RFC3031] and [RFC4397].		[RFC5654], [RFC5921], [RFC5860], [RFC5951], [RFC3031] and [RFC4397].
	ITU-T architecture and requirements Recommendations: [ITU-T_G.8101],		ITU-T architecture and requirements Recommendations: [ITU-T_G.8101],
	[ITU-T_G.805], [ITU-T_G.806], [ITU-T_G.872], [ITU-T G.7710] and		[ITU-T_G.805], [ITU-T_G.806], [ITU-T_G.872], [ITU-T G.7710] and
	[ITU-T Y.2611]		[ITU-T Y.2611]
	3. Thesaurus		3. Thesaurus
	3.1. Associated bidirectional path:		3.1. Associated bidirectional path:
	A path that supports traffic flow in both directions but that is		A path that supports traffic flow in both directions but that is
	constructed from a pair of unidirectional paths (one for each		constructed from a pair of unidirectional paths (one for each
	direction) that are associated with one another at the path's		direction) that are associated with one another at the path's
	skipping to change at page 6, line 28		skipping to change at page 6, line 27
	they may or may not follow the same route (links and nodes) across		they may or may not follow the same route (links and nodes) across
	the network.		the network.
	3.2. Bidirectional path:		3.2. Bidirectional path:
	A path that supports traffic flow in two opposite directions, i.e.		A path that supports traffic flow in two opposite directions, i.e.
	the forward and backward direction.		the forward and backward direction.
	3.3. Client layer network:		3.3. Client layer network:
	In a client/server relationship (see Error! Reference source not		In a client/server relationship (see [ITU-T_G.805]), the client
	found.), the client layer network receives a (transport) service		layer network receives a (transport) service from the lower server
	from the lower server layer network (usually the layer network under		layer network (usually the layer network under consideration).
	consideration).
	3.4. Concatenated Segment:		3.4. Concatenated Segment:
	A serial-compound link connection as defined in Error! Reference		A serial-compound link connection as defined in [ITU-T_G.805]. A
	source not found.. A concatenated segment is a contiguous part of		concatenated segment is a contiguous part of an LSP or multi-segment
	an LSP or multi-segment PW that comprises a set of segments and		PW that comprises a set of segments and their interconnecting nodes
	their interconnecting nodes in sequence. See also "Segment".		in sequence. See also "Segment".
	3.5. Control Plane:		3.5. Control Plane:
	Within the scope of [RFC5654], the control plane performs transport		Within the scope of [RFC5654], the control plane performs transport
	path control functions. Through signalling, the control plane sets		path control functions. Through signalling, the control plane sets
	up, modifies and releases transport paths, and may recover a		up, modifies and releases transport paths, and may recover a
	transport path in case of a failure. The control plane also		transport path in case of a failure. The control plane also
	performs other functions in support of transport path control, such		performs other functions in support of transport path control, such
	as routing information dissemination.		as routing information dissemination.
	skipping to change at page 7, line 24		skipping to change at page 7, line 24
	A domain represents a collection of entities (for example network		A domain represents a collection of entities (for example network
	elements) that are grouped for a particular purpose, examples of		elements) that are grouped for a particular purpose, examples of
	which are administrative and/or managerial responsibilities, trust		which are administrative and/or managerial responsibilities, trust
	relationships, addressing schemes, infrastructure capabilities,		relationships, addressing schemes, infrastructure capabilities,
	aggregation, survivability techniques, distributions of control		aggregation, survivability techniques, distributions of control
	functionality, etc. Examples of such domains include IGP areas and		functionality, etc. Examples of such domains include IGP areas and
	Autonomous Systems.		Autonomous Systems.
	3.8. Layer network:		3.8. Layer network:
	Layer network is defined in Error! Reference source not found.. A		Layer network is defined in [ITU-T_G.805]. A layer network provides
	layer network provides for the transfer of client information and		for the transfer of client information and independent operation of
	independent operation of the client OAM. A layer network may be		the client OAM. A layer network may be described in a service
	described in a service context as follows: one layer network may		context as follows: one layer network may provide a (transport)
	provide a (transport) service to a higher client layer network and		service to a higher client layer network and may, in turn, be a
	may, in turn, be a client to a lower-layer network. A layer network		client to a lower-layer network. A layer network is a logical
	is a logical construction somewhat independent of arrangement or		construction somewhat independent of arrangement or composition of
	composition of physical network elements. A particular physical		physical network elements. A particular physical network element
	network element may topologically belong to more than one layer		may topologically belong to more than one layer network, depending
	network, depending on the actions it takes on the encapsulation		on the actions it takes on the encapsulation associated with the
	associated with the logical layers (e.g., the label stack), and thus		logical layers (e.g., the label stack), and thus could be modeled as
	could be modeled as multiple logical elements. A layer network may		multiple logical elements. A layer network may consist of one or
	consist of one or more sublayers. For additional explanation of how		more sublayers. For additional explanation of how layer networks
	layer networks relate to the OSI concept of layering, see Appendix I		relate to the OSI concept of layering, see Appendix I of [ITU-T
	of Error! Reference source not found..		Y.2611].
	3.9. Link:		3.9. Link:
	A physical or logical connection between a pair of LSRs that are		A physical or logical connection between a pair of LSRs that are
	adjacent at the (sub)layer network under consideration. A link may		adjacent at the (sub)layer network under consideration. A link may
	carry zero, one or more LSPs or PWs. A packet entering a link will		carry zero, one or more LSPs or PWs. A packet entering a link will
	emerge with the same label stack entry values.		emerge with the same label stack entry values.
	A link as defined in Error! Reference source not found. is used to		A link as defined in [ITU-T_G.805] is used to describe a fixed
	describe a fixed relationship between two ports.		relationship between two ports.
	3.10. MPLS-TP Logical Ring:		3.10. MPLS-TP Logical Ring:
	An MPLS-TP logical ring is constructed from a set of LSRs and		An MPLS-TP logical ring is constructed from a set of LSRs and
	logical data links (such as MPLS-TP LSP tunnels or MSPL-TP		logical data links (such as MPLS-TP LSP tunnels or MSPL-TP
	pseudowires) and physical data links that form a ring topology.		pseudowires) and physical data links that form a ring topology.
	3.11. MPLS-TP Physical Ring:		3.11. MPLS-TP Physical Ring:
	An MPLS-TP physical ring is constructed from a set of LSRs and		An MPLS-TP physical ring is constructed from a set of LSRs and
	skipping to change at page 8, line 37		skipping to change at page 8, line 37
	3.13. Path:		3.13. Path:
	See Transport path.		See Transport path.
	3.14. Section Layer Network:		3.14. Section Layer Network:
	A section layer is a server layer (which may be MPLS-TP or a		A section layer is a server layer (which may be MPLS-TP or a
	different technology) that provides for the transfer of the section-		different technology) that provides for the transfer of the section-
	layer client information between adjacent nodes in the transport-		layer client information between adjacent nodes in the transport-
	path layer or transport-service layer. A section layer may provide		path layer or transport-service layer. A section layer may provide
	for aggregation of multiple MPLS-TP clients. Note that Error!		for aggregation of multiple MPLS-TP clients. Note that [ITU-
	Reference source not found. defines the section layer as one of the		T_G.805] defines the section layer as one of the two layer networks
	two layer networks in a transmission-media layer network. The other		in a transmission-media layer network. The other layer network is
	layer network is the physical-media layer network.		the physical-media layer network.
	Section layer networks are concerned with all the functions which		Section layer networks are concerned with all the functions which
	provide for the transfer of information between locations in path		provide for the transfer of information between locations in path
	layer networks.		layer networks.
	Physical media layer networks are concerned with the actual fibres,		Physical media layer networks are concerned with the actual fibres,
	metallic wires or radio frequency channels which support a section		metallic wires or radio frequency channels which support a section
	layer network.		layer network.
	3.15. Segment:		3.15. Segment:
	A link connection as defined in Error! Reference source not found..		A link connection as defined in [ITU-T_G.805]. A segment is the
	A segment is the part of an LSP that traverses a single link or the		part of an LSP that traverses a single link or the part of a PW that
	part of a PW that traverses a single link (i.e., that connects a		traverses a single link (i.e., that connects a pair of adjacent
	pair of adjacent {Switching|Terminating} Provider Edges). See also		{Switching|Terminating} Provider Edges). See also "Concatenated
	"Concatenated Segment".		Segment".
	3.16. Server layer:		3.16. Server layer:
	A layer network in which transport paths are used to carry a		A layer network in which transport paths are used to carry a
	customer's (individual or bundled) service (may be point-to-point,		customer's (individual or bundled) service (may be point-to-point,
	point-to-multipoint or multipoint-to-multipoint services).		point-to-multipoint or multipoint-to-multipoint services).
	In a client/server relationship (see Error! Reference source not		In a client/server relationship (see [ITU-T_G.805]). the server
	found.). the server layer network provides a (transport) service to		layer network provides a (transport) service to the higher client
	the higher client layer network (usually the layer network under		layer network (usually the layer network under consideration).
	consideration).
	3.17. Span:		3.17. Span:
	A span is synonymous with a link.		A span is synonymous with a link.
	3.18. Sublayer:		3.18. Sublayer:
	Sublayer is defined in Error! Reference source not found.. The		Sublayer is defined in [ITU-T_G.805]. The distinction between a
	distinction between a layer network and a sublayer is that a		layer network and a sublayer is that a sublayer is not directly
	sublayer is not directly accessible to clients outside of its		accessible to clients outside of its encapsulating layer network and
	encapsulating layer network and offers no direct transport service		offers no direct transport service for a higher layer (client)
	for a higher layer (client) network.		network.
	3.19. Tandem Connection:		3.19. Tandem Connection:
	A tandem connection is an arbitrary part of a transport path that		A tandem connection is an arbitrary part of a transport path that
	can be monitored (via OAM) independently from the end-to-end		can be monitored (via OAM) independently from the end-to-end
	monitoring (OAM). It may be a monitored segment, a monitored		monitoring (OAM). It may be a monitored segment, a monitored
	concatenated segment or any other monitored ordered sequence of		concatenated segment or any other monitored ordered sequence of
	contiguous hops and/or segments (and their interconnecting nodes) of		contiguous hops and/or segments (and their interconnecting nodes) of
	a transport path.		a transport path.
	skipping to change at page 10, line 12		skipping to change at page 10, line 11
	Transport Network is independent of any higher-layer network that		Transport Network is independent of any higher-layer network that
	may exist between clients, except to the extent required to supply		may exist between clients, except to the extent required to supply
	this transmission service. In addition to client traffic, a		this transmission service. In addition to client traffic, a
	Transport Network may carry traffic to facilitate its own operation,		Transport Network may carry traffic to facilitate its own operation,
	such as that required to support connection control, network		such as that required to support connection control, network
	management, and Operations, Administration and Maintenance (OAM)		management, and Operations, Administration and Maintenance (OAM)
	functions.		functions.
	3.21. Transport path:		3.21. Transport path:
	A network connection as defined in Error! Reference source not		A network connection as defined in [ITU-T_G.805]. In an MPLS-TP
	found.. In an MPLS-TP environment a transport path corresponds to		environment a transport path corresponds to an LSP or a PW.
	an LSP or a PW.
	3.22. Transport path layer:		3.22. Transport path layer:
	A (sub)layer network that provides point-to-point or point-to-		A (sub)layer network that provides point-to-point or point-to-
	multipoint transport paths. It provides OAM that is independent of		multipoint transport paths. It provides OAM that is independent of
	the clients that it is transporting.		the clients that it is transporting.
	3.23. Transport service layer:		3.23. Transport service layer:
	A layer network in which transport paths are used to carry a		A layer network in which transport paths are used to carry a
	customer's (individual or bundled) service (may be point-to-point,		customer's (individual or bundled) service (may be point-to-point,
	point-to-multipoint or multipoint-to-multipoint services).		point-to-multipoint or multipoint-to-multipoint services).
	3.24. Transmission media layer:		3.24. Transmission media layer:
	A layer network, consisting of a section layer network and a		A layer network, consisting of a section layer network and a
	physical layer network as defined in Error! Reference source not		physical layer network as defined in [ITU-T_G.805], that provides
	found., that provides sections (two-port point-to-point connections)		sections (two-port point-to-point connections) to carry the
	to carry the aggregate of network-transport path or network-service		aggregate of network-transport path or network-service layers on
	layers on various physical media.		various physical media.
	3.25. Unidirectional path:		3.25. Unidirectional path:
	A Unidirectional Path is a path that supports traffic flow in only		A Unidirectional Path is a path that supports traffic flow in only
	one direction.		one direction.
	3.26. Failure:		3.26. Failure:
	The fault cause persisted long enough to consider the ability of an		The fault cause persisted long enough to consider the ability of an
	item to perform a required function to be terminated. The item may		item to perform a required function to be terminated. The item may
	be considered as failed; a fault has now been detected. See also		be considered as failed; a fault has now been detected. See also
	Error! Reference source not found..		[ITU-T_G.806].
	3.27. Fault:		3.27. Fault:
	A Fault is the inability of a function to perform a required action.		A Fault is the inability of a function to perform a required action.
	This does not include an inability due to preventive maintenance,		This does not include an inability due to preventive maintenance,
	lack of external resources, or planned actions. See also Error!		lack of external resources, or planned actions. See also [ITU-
	Reference source not found..		T_G.806].
	3.28. Defect:		3.28. Defect:
	The situation for which the density of anomalies has reached a level		The situation for which the density of anomalies has reached a level
	where the ability to perform a required function has been		where the ability to perform a required function has been
	interrupted. Defects are used as input for PM, the control of		interrupted. Defects are used as input for PM, the control of
	consequent actions, and the determination of fault cause. See also		consequent actions, and the determination of fault cause. See also
	Error! Reference source not found..		[ITU-T_G.806].
	3.29. MPLS Transport Profile (MPLS-TP):		3.29. MPLS Transport Profile (MPLS-TP):
	The set of MPLS functions used to support packet transport services		The set of MPLS functions used to support packet transport services
	and network operations.		and network operations.
	3.30. MPLS Section:		3.30. MPLS Section:
	A network segment between two LSRs that are immediately adjacent at		A network segment between two LSRs that are immediately adjacent at
	the MPLS layer.		the MPLS layer.
	skipping to change at page 11, line 40		skipping to change at page 11, line 35
	3.31. MPLS-TP NE:		3.31. MPLS-TP NE:
	A network element (NE) that supports MPLS-TP functions.		A network element (NE) that supports MPLS-TP functions.
	3.32. MPLS-TP network:		3.32. MPLS-TP network:
	A network in which MPLS-TP NEs are deployed		A network in which MPLS-TP NEs are deployed
	3.33. Equipment Management Function (EMF):		3.33. Equipment Management Function (EMF):
	The management functions within an NE. See Error! Reference source		The management functions within an NE. See [ITU-T G.7710].
	not found..
	3.34. Data Communication Network (DCN):		3.34. Data Communication Network (DCN):
	A network that supports Layer 1 (physical layer), Layer 2 (data-link		A network that supports Layer 1 (physical layer), Layer 2 (data-link
	layer), and Layer 3 (network layer) functionality for distributed		layer), and Layer 3 (network layer) functionality for distributed
	management communications related to the management plane, for		management communications related to the management plane, for
	distributed signaling communications related to the control plane,		distributed signaling communications related to the control plane,
	and other operations communications (e.g., order-wire/voice		and other operations communications (e.g., order-wire/voice
	communications, software downloads, etc.).		communications, software downloads, etc.).
	skipping to change at page 16, line 32		skipping to change at page 16, line 32
	The MPLS-TP based network requires management. The MPLS-TP		The MPLS-TP based network requires management. The MPLS-TP
	specifications include considerable efforts to provide operator		specifications include considerable efforts to provide operator
	control and monitoring, as well as Operations and Management (OAM)		control and monitoring, as well as Operations and Management (OAM)
	functionality.		functionality.
	These concepts are, however, out of scope of this document.		These concepts are, however, out of scope of this document.
	6. Security Considerations		6. Security Considerations
	Security is also a significant requirement of MPLS-TP.		Security is a significant requirement of MPLS-TP.
	However, this informational document is intended only to provide a		However, this informational document is intended only to provide a
	lexicography, and the security concerns are, therefore, out of		lexicography, and the security concerns are, therefore, out of
	scope.		scope.
	7. IANA Considerations		7. IANA Considerations
	To be incorporated in a future revision of this document		There are no IANA actions resulting from this document.
	<<TBA>>
	8. Acknowledgments		8. Acknowledgments
	The authors would like to thank all members of the teams (the Joint		The authors would like to thank all members of the teams (the Joint
	Working Team, the MPLS Interoperability Design Team in IETF and the		Working Team, the MPLS Interoperability Design Team in IETF and the
	MPLS-TP Ad Hoc Group in ITU-T) involved in the definition and		MPLS-TP Ad Hoc Group in ITU-T) involved in the definition and
	specification of MPLS Transport Profile.		specification of MPLS Transport Profile.
	9. References		9. References
	skipping to change at page 17, line 36		skipping to change at page 17, line 36
	[RFC5921] Bocci, M., Bryant, S., Levrau, L., "A Framework for MPLS		[RFC5921] Bocci, M., Bryant, S., Levrau, L., "A Framework for MPLS
	in Transport Networks", July 2010		in Transport Networks", July 2010
	[RFC5860] Vigoureux, M., Betts, M., Ward, D., "Requirements for OAM		[RFC5860] Vigoureux, M., Betts, M., Ward, D., "Requirements for OAM
	in MPLS Transport Networks", May 2010		in MPLS Transport Networks", May 2010
	[RFC5951] Gray, E., Mansfield, S., et al., "MPLS TP Network		[RFC5951] Gray, E., Mansfield, S., et al., "MPLS TP Network
	Management Requirements", September 2010		Management Requirements", September 2010
	[RFC3031] E. Rosen, et al., "Requirements of an MPLS Transport		[RFC3031] E. Rosen, et al., "Requirements of an MPLS Transport
	Profile", january 2001		Profile", January 2001
	For information on the availability of the following documents,		For information on the availability of the following documents,
	please see http://www.itu.int		please see http://www.itu.int
	[ITU-T_G.8101] ITU-T Recommendation G.8101/Y.1355 (12/2006), Terms		[ITU-T_G.8101] ITU-T Recommendation G.8101/Y.1355 (12/2006), "Terms
	and definitions for transport MPLS.		and definitions for transport MPLS."
	[ITU-T_G.805] ITU-T Recommendation G.805 (03/2000), Generic		[ITU-T_G.805] ITU-T Recommendation G.805 (03/2000), "Generic
	functional architecture of transport networks.		functional architecture of transport networks."
	[ITU-T_G.806] ITU-T Recommendation G.806 (03/2006), Characteristics		[ITU-T_G.806] ITU-T Recommendation G.806 (03/2006), "Characteristics
	of transport equipment - Description methodology and		of transport equipment - Description methodology and
	generic functionality.		generic functionality."
	[ITU-T_G.872] ITU-T Recommendation G.872 (11/2001), Architecture of		[ITU-T_G.872] ITU-T Recommendation G.872 (11/2001), "Architecture of
	optical transport networks.		optical transport networks."
	[ITU-T G.7710] ITU-T Recommendation G.7710 (07/2007), Common		[ITU-T G.7710] ITU-T Recommendation G.7710 (07/2007), "Common
	equipment management function requirements		equipment management function requirements."
	[ITU-T Y.2611] ITU-T Recommendation Y.2611 (12/2006), High-level		[ITU-T Y.2611] ITU-T Recommendation Y.2611 (12/2006), "High-level
	architecture of future packet-based networks		architecture of future packet-based networks."
	9.2. Informative References		9.2. Informative References
	[RFC4397] I. Bryskin, A. Farrel, "A Lexicography for the		[RFC4397] I. Bryskin, A. Farrel, "A Lexicography for the
	Interpretation of Generalized Multiprotocol Label		Interpretation of Generalized Multiprotocol Label
	Switching (GMPLS) Terminology within the Context of the		Switching (GMPLS) Terminology within the Context of the
	ITU-T's Automatically Switched Optical Network (ASON)		ITU-T's Automatically Switched Optical Network (ASON)
	Architecture", february 2006		Architecture", February 2006
	[RFC3945] E. Mannie, "Generalized Multi-Protocol Label Switching		[RFC3945] E. Mannie, "Generalized Multi-Protocol Label Switching
	(GMPLS) Architecture", October 2004		(GMPLS) Architecture", October 2004
	Authors' Addresses		Authors' Addresses
	Huub van Helvoort (Editor)		Huub van Helvoort (Editor)
	Huawei Technologies Co., Ltd.		Huawei Technologies Co., Ltd.
	Email: Huub.van.Helvoort@huawei.com		Email: Huub.van.Helvoort@huawei.com
	Loa Andersson (Editor)		Loa Andersson (Editor)
	Ericsson		Huawei Technologies Co., Ltd.
	Email: loa.andersson@ericsson.com		Email: loa@mail01.huawei.com
	Nurit Sprecher (Editor)		Nurit Sprecher (Editor)
	Nokia Siemens Networks		Nokia Siemens Networks
	Email: nurit.sprecher@nsn.com		Email: nurit.sprecher@nsn.com
	Contributing Authors' Addresses
End of changes. 36 change blocks.
	88 lines changed or deleted		80 lines changed or added
This html diff was produced by rfcdiff 1.41. The latest version is available from http://tools.ietf.org/tools/rfcdiff/