draft-ietf-idr-te-lsp-distribution-10.txt		draft-ietf-idr-te-lsp-distribution-11.txt
	Network Working Group S. Previdi		Network Working Group S. Previdi
	Internet-Draft		Internet-Draft
	Intended status: Standards Track K. Talaulikar, Ed.		Intended status: Standards Track K. Talaulikar, Ed.
	Expires: August 30, 2019 Cisco Systems, Inc.		Expires: November 3, 2019 Cisco Systems, Inc.
	J. Dong, Ed.		J. Dong, Ed.
	M. Chen		M. Chen
	Huawei Technologies		Huawei Technologies
	H. Gredler		H. Gredler
	RtBrick Inc.		RtBrick Inc.
	J. Tantsura		J. Tantsura
	Apstra		Apstra
	February 26, 2019		May 2, 2019
	Distribution of Traffic Engineering (TE) Policies and State using BGP-LS		Distribution of Traffic Engineering (TE) Policies and State using BGP-LS
	draft-ietf-idr-te-lsp-distribution-10		draft-ietf-idr-te-lsp-distribution-11
	Abstract		Abstract
	This document describes a mechanism to collect the Traffic		This document describes a mechanism to collect the Traffic
	Engineering and Policy information that is locally available in a		Engineering and Policy information that is locally available in a
	node and advertise it into BGP Link State (BGP-LS) updates. Such		node and advertise it into BGP Link State (BGP-LS) updates. Such
	information can be used by external components for path computation,		information can be used by external components for path computation,
	re-optimization, service placement, network visualization, etc.		re-optimization, service placement, network visualization, etc.
	Requirements Language		Requirements Language
	skipping to change at page 2, line 4 ¶		skipping to change at page 2, line 4 ¶
	Internet-Drafts are working documents of the Internet Engineering		Internet-Drafts are working documents of the Internet Engineering
	Task Force (IETF). Note that other groups may also distribute		Task Force (IETF). Note that other groups may also distribute
	working documents as Internet-Drafts. The list of current Internet-		working documents as Internet-Drafts. The list of current Internet-
	Drafts is at https://datatracker.ietf.org/drafts/current/.		Drafts is at https://datatracker.ietf.org/drafts/current/.
	Internet-Drafts are draft documents valid for a maximum of six months		Internet-Drafts are draft documents valid for a maximum of six months
	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."
	This Internet-Draft will expire on August 30, 2019.		This Internet-Draft will expire on November 3, 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
	(https://trustee.ietf.org/license-info) in effect on the date of		(https://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 2, line 27 ¶		skipping to change at page 2, line 27 ¶
	include Simplified BSD License text as described in Section 4.e of		include Simplified BSD License text as described in Section 4.e of
	the Trust Legal Provisions and are provided without warranty as		the Trust Legal Provisions and are provided without warranty as
	described in the Simplified BSD License.		described in the Simplified BSD License.
	Table of Contents		Table of Contents
	1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3		1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3
	2. Carrying TE Policy Information in BGP . . . . . . . . . . . . 5		2. Carrying TE Policy Information in BGP . . . . . . . . . . . . 5
	3. TE Policy NLRI . . . . . . . . . . . . . . . . . . . . . . . 6		3. TE Policy NLRI . . . . . . . . . . . . . . . . . . . . . . . 6
	4. TE Policy Descriptors . . . . . . . . . . . . . . . . . . . . 7		4. TE Policy Descriptors . . . . . . . . . . . . . . . . . . . . 7
	4.1. Tunnel Identifier (Tunnel ID) . . . . . . . . . . . . . . 7		4.1. Tunnel Identifier (Tunnel ID) . . . . . . . . . . . . . . 8
	4.2. LSP Identifier (LSP ID) . . . . . . . . . . . . . . . . . 7		4.2. LSP Identifier (LSP ID) . . . . . . . . . . . . . . . . . 8
	4.3. IPv4/IPv6 Tunnel Head-End Address . . . . . . . . . . . . 8		4.3. IPv4/IPv6 Tunnel Head-End Address . . . . . . . . . . . . 9
	4.4. IPv4/IPv6 Tunnel Tail-End Address . . . . . . . . . . . . 8		4.4. IPv4/IPv6 Tunnel Tail-End Address . . . . . . . . . . . . 9
	4.5. SR Policy Candidate Path Descriptor . . . . . . . . . . . 9		4.5. SR Policy Candidate Path Descriptor . . . . . . . . . . . 10
	4.6. Local MPLS Cross Connect . . . . . . . . . . . . . . . . 11		4.6. Local MPLS Cross Connect . . . . . . . . . . . . . . . . 11
	4.6.1. MPLS Cross Connect Interface . . . . . . . . . . . . 12		4.6.1. MPLS Cross Connect Interface . . . . . . . . . . . . 13
	4.6.2. MPLS Cross Connect FEC . . . . . . . . . . . . . . . 13		4.6.2. MPLS Cross Connect FEC . . . . . . . . . . . . . . . 14
	5. MPLS-TE Policy State TLV . . . . . . . . . . . . . . . . . . 14		5. MPLS-TE Policy State TLV . . . . . . . . . . . . . . . . . . 15
	5.1. RSVP Objects . . . . . . . . . . . . . . . . . . . . . . 15		5.1. RSVP Objects . . . . . . . . . . . . . . . . . . . . . . 16
	5.2. PCEP Objects . . . . . . . . . . . . . . . . . . . . . . 16		5.2. PCEP Objects . . . . . . . . . . . . . . . . . . . . . . 17
	6. SR Policy State TLVs . . . . . . . . . . . . . . . . . . . . 17		6. SR Policy State TLVs . . . . . . . . . . . . . . . . . . . . 18
	6.1. SR Binding SID . . . . . . . . . . . . . . . . . . . . . 17		6.1. SR Binding SID . . . . . . . . . . . . . . . . . . . . . 18
	6.2. SR Candidate Path State . . . . . . . . . . . . . . . . . 19		6.2. SR Candidate Path State . . . . . . . . . . . . . . . . . 20
	6.3. SR Candidate Path Name . . . . . . . . . . . . . . . . . 21		6.3. SR Candidate Path Name . . . . . . . . . . . . . . . . . 22
	6.4. SR Candidate Path Constraints . . . . . . . . . . . . . . 21		6.4. SR Candidate Path Constraints . . . . . . . . . . . . . . 22
	6.4.1. SR Affinity Constraint . . . . . . . . . . . . . . . 23		6.4.1. SR Affinity Constraint . . . . . . . . . . . . . . . 24
	6.4.2. SR SRLG Constraint . . . . . . . . . . . . . . . . . 24		6.4.2. SR SRLG Constraint . . . . . . . . . . . . . . . . . 25
	6.4.3. SR Bandwidth Constraint . . . . . . . . . . . . . . . 25		6.4.3. SR Bandwidth Constraint . . . . . . . . . . . . . . . 26
	6.4.4. SR Disjoint Group Constraint . . . . . . . . . . . . 25		6.4.4. SR Disjoint Group Constraint . . . . . . . . . . . . 26
	6.5. SR Segment List . . . . . . . . . . . . . . . . . . . . . 27		6.5. SR Segment List . . . . . . . . . . . . . . . . . . . . . 28
	6.6. SR Segment . . . . . . . . . . . . . . . . . . . . . . . 30		6.6. SR Segment . . . . . . . . . . . . . . . . . . . . . . . 31
	6.6.1. Segment Descriptors . . . . . . . . . . . . . . . . . 31		6.6.1. Segment Descriptors . . . . . . . . . . . . . . . . . 32
	6.7. SR Segment List Metric . . . . . . . . . . . . . . . . . 38		6.7. SR Segment List Metric . . . . . . . . . . . . . . . . . 39
	7. Procedures . . . . . . . . . . . . . . . . . . . . . . . . . 40		7. Procedures . . . . . . . . . . . . . . . . . . . . . . . . . 41
	8. Manageability Considerations . . . . . . . . . . . . . . . . 41		8. Manageability Considerations . . . . . . . . . . . . . . . . 42
	9. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 41		9. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 42
	9.1. BGP-LS NLRI-Types . . . . . . . . . . . . . . . . . . . . 41		9.1. BGP-LS NLRI-Types . . . . . . . . . . . . . . . . . . . . 42
	9.2. BGP-LS Protocol-IDs . . . . . . . . . . . . . . . . . . . 41		9.2. BGP-LS Protocol-IDs . . . . . . . . . . . . . . . . . . . 42
	9.3. BGP-LS TLVs . . . . . . . . . . . . . . . . . . . . . . . 42		9.3. BGP-LS TLVs . . . . . . . . . . . . . . . . . . . . . . . 43
	9.4. BGP-LS SR Policy Protocol Origin . . . . . . . . . . . . 42		9.4. BGP-LS SR Policy Protocol Origin . . . . . . . . . . . . 43
	9.5. BGP-LS TE State Object Origin . . . . . . . . . . . . . . 43		9.5. BGP-LS TE State Object Origin . . . . . . . . . . . . . . 44
	9.6. BGP-LS TE State Address Family . . . . . . . . . . . . . 43		9.6. BGP-LS TE State Address Family . . . . . . . . . . . . . 44
	9.7. BGP-LS SR Segment Descriptors . . . . . . . . . . . . . . 44		9.7. BGP-LS SR Segment Descriptors . . . . . . . . . . . . . . 45
	9.8. BGP-LS Metric Type . . . . . . . . . . . . . . . . . . . 44		9.8. BGP-LS Metric Type . . . . . . . . . . . . . . . . . . . 45
	10. Security Considerations . . . . . . . . . . . . . . . . . . . 45		10. Security Considerations . . . . . . . . . . . . . . . . . . . 46
	11. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 45		11. Contributors . . . . . . . . . . . . . . . . . . . . . . . . 46
	12. Contributors . . . . . . . . . . . . . . . . . . . . . . . . 45		12. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 46
	13. References . . . . . . . . . . . . . . . . . . . . . . . . . 45		13. References . . . . . . . . . . . . . . . . . . . . . . . . . 46
	13.1. Normative References . . . . . . . . . . . . . . . . . . 45		13.1. Normative References . . . . . . . . . . . . . . . . . . 46
	13.2. Informative References . . . . . . . . . . . . . . . . . 47		13.2. Informative References . . . . . . . . . . . . . . . . . 48
	Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 48		Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 49
	1. Introduction		1. Introduction
	In many network environments, traffic engineering (TE) policies are		In many network environments, traffic engineering (TE) policies are
	instantiated into various forms:		instantiated into various forms:
	o MPLS Traffic Engineering Label Switched Paths (TE-LSPs).		o MPLS Traffic Engineering Label Switched Paths (TE-LSPs).
	o IP based tunnels (IP in IP, GRE, etc).		o IP based tunnels (IP in IP, GRE, etc).
	skipping to change at page 6, line 41 ¶		skipping to change at page 6, line 41 ¶
	+-------------+----------------------------------+		+-------------+----------------------------------+
	| Protocol-ID | NLRI information source protocol |		| Protocol-ID | NLRI information source protocol |
	+-------------+----------------------------------+		+-------------+----------------------------------+
	| TBD | RSVP-TE |		| TBD | RSVP-TE |
	| TBD | Segment Routing |		| TBD | Segment Routing |
	+-------------+----------------------------------+		+-------------+----------------------------------+
	o "Identifier" is an 8 octet value as defined in [RFC7752].		o "Identifier" is an 8 octet value as defined in [RFC7752].
	o "Headend" consists of a Node Descriptor defined in [RFC7752].		o "Headend" consists of a Local Node Descriptor (TLV 256) as defined
			in [RFC7752].
	o "TE Policy Descriptors" consists of one or more of the TLVs listed		o "TE Policy Descriptors" consists of one or more of the TLVs listed
	as below: (values TBD see IANA Considerations Section 9.3):		as below: (values TBD see IANA Considerations Section 9.3):
	+-----------+----------------------------------+		+-----------+----------------------------------+
	| Codepoint | Descriptor TLVs |		| Codepoint | Descriptor TLVs |
	+-----------+----------------------------------+		+-----------+----------------------------------+
	| TBD | Tunnel ID |		| TBD | Tunnel ID |
	| TBD | LSP ID |		| TBD | LSP ID |
	| TBD | IPv4/6 Tunnel Head-end address |		| TBD | IPv4/6 Tunnel Head-end address |
	| TBD | IPv4/6 Tunnel Tail-end address |		| TBD | IPv4/6 Tunnel Tail-end address |
	| TBD | SR Policy Candidate Path |		| TBD | SR Policy Candidate Path |
	| TBD | Local MPLS Cross Connect |		| TBD | Local MPLS Cross Connect |
	+-----------+----------------------------------+		+-----------+----------------------------------+
			The Local Node Descriptor TLV MUST include the following Node
			Descriptor TLVs:
			o BGP Router-ID (TLV 516) [I-D.ietf-idr-bgpls-segment-routing-epe],
			which contains a valid BGP Identifier of the local node.
			o Autonomous System Number (TLV 512) [RFC7752], which contains the
			ASN or AS Confederation Identifier (ASN) [RFC5065], if
			confederations are used, of the local node.
			The Local Node Descriptor TLV SHOULD include the following Node
			Descriptor TLVs:
			o IPv4 Router-ID of Local Node (TLV 1028) [RFC7752], which contains
			the IPv4 TE Router-ID of the local node when one is provisioned.
			o IPv6 Router-ID of Local Node (TLV 1029) [RFC7752], which contains
			the IPv6 TE Router-ID of the local node when one is provisioned.
			The Local Node Descriptor TLV MAY include the following Node
			Descriptor TLVs:
			o Member-ASN (TLV 517) [I-D.ietf-idr-bgpls-segment-routing-epe],
			which contains the ASN of the confederation member (i.e. Member-
			AS Number), if BGP confederations are used, of the local node.
			o Node Descriptors as defined in [RFC7752].
	4. TE Policy Descriptors		4. TE Policy Descriptors
	This sections defines the TE Policy Descriptors TLVs which are used		This sections defines the TE Policy Descriptors TLVs which are used
	to describe the TE Policy being advertised by using the new BGP-LS TE		to describe the TE Policy being advertised by using the new BGP-LS TE
	Policy NLRI type defined in Section 3.		Policy NLRI type defined in Section 3.
	4.1. Tunnel Identifier (Tunnel ID)		4.1. Tunnel Identifier (Tunnel ID)
	The Tunnel Identifier TLV contains the Tunnel ID defined in [RFC3209]		The Tunnel Identifier TLV contains the Tunnel ID defined in [RFC3209]
	and is used for RSVP-TE protocol TE Policies. It has the following		and is used for RSVP-TE protocol TE Policies. It has the following
	skipping to change at page 41, line 33 ¶		skipping to change at page 42, line 33 ¶
	9. IANA Considerations		9. IANA Considerations
	This document requires new IANA assigned codepoints.		This document requires new IANA assigned codepoints.
	9.1. BGP-LS NLRI-Types		9.1. BGP-LS NLRI-Types
	IANA maintains a registry called "Border Gateway Protocol - Link		IANA maintains a registry called "Border Gateway Protocol - Link
	State (BGP-LS) Parameters" with a sub-registry called "BGP-LS NLRI-		State (BGP-LS) Parameters" with a sub-registry called "BGP-LS NLRI-
	Types".		Types".
	The following codepoints is suggested (to be assigned by IANA):		The following codepoints is suggested (for early allocation by IANA):
	+------+----------------------------+---------------+		+------+----------------------------+---------------+
	| Type | NLRI Type | Reference |		| Type | NLRI Type | Reference |
	+------+----------------------------+---------------+		+------+----------------------------+---------------+
	| 5 | TE Policy NLRI type | this document |		| 5 | TE Policy NLRI type | this document |
	+------+----------------------------+---------------+		+------+----------------------------+---------------+
	9.2. BGP-LS Protocol-IDs		9.2. BGP-LS Protocol-IDs
	IANA maintains a registry called "Border Gateway Protocol - Link		IANA maintains a registry called "Border Gateway Protocol - Link
	State (BGP-LS) Parameters" with a sub-registry called "BGP-LS		State (BGP-LS) Parameters" with a sub-registry called "BGP-LS
	Protocol-IDs".		Protocol-IDs".
	The following Protocol-ID codepoints are suggested (to be assigned by		The following Protocol-ID codepoints are suggested (for early
	IANA):		allocation by IANA):
	+-------------+----------------------------------+---------------+		+-------------+----------------------------------+---------------+
	| Protocol-ID | NLRI information source protocol | Reference |		| Protocol-ID | NLRI information source protocol | Reference |
	+-------------+----------------------------------+---------------+		+-------------+----------------------------------+---------------+
	| 8 | RSVP-TE | this document |		| 8 | RSVP-TE | this document |
	| 9 | Segment Routing | this document |		| 9 | Segment Routing | this document |
	+-------------+----------------------------------+---------------+		+-------------+----------------------------------+---------------+
	9.3. BGP-LS TLVs		9.3. BGP-LS TLVs
	IANA maintains a registry called "Border Gateway Protocol - Link		IANA maintains a registry called "Border Gateway Protocol - Link
	State (BGP-LS) Parameters" with a sub-registry called "Node Anchor,		State (BGP-LS) Parameters" with a sub-registry called "Node Anchor,
	Link Descriptor and Link Attribute TLVs".		Link Descriptor and Link Attribute TLVs".
	The following TLV codepoints are suggested (to be assigned by IANA):		The following TLV codepoints are suggested (for early allocation by
			IANA):
	+----------+----------------------------------------+---------------+		+----------+----------------------------------------+---------------+
	| TLV Code | Description | Value defined |		| TLV Code | Description | Value defined |
	| Point | | in |		| Point | | in |
	+----------+----------------------------------------+---------------+		+----------+----------------------------------------+---------------+
	| TBD | Tunnel ID TLV | this document |		| 550 | Tunnel ID TLV | this document |
	| TBD | LSP ID TLV | this document |		| 551 | LSP ID TLV | this document |
	| TBD | IPv4/6 Tunnel Head-end address TLV | this document |		| 552 | IPv4/6 Tunnel Head-end address TLV | this document |
	| TBD | IPv4/6 Tunnel Tail-end address TLV | this document |		| 553 | IPv4/6 Tunnel Tail-end address TLV | this document |
	| TBD | SR Policy CP Descriptor TLV | this document |		| 554 | SR Policy CP Descriptor TLV | this document |
	| TBD | MPLS Local Cross Connect TLV | this document |		| 555 | MPLS Local Cross Connect TLV | this document |
	| TBD | MPLS Cross Connect Interface TLV | this document |		| 556 | MPLS Cross Connect Interface TLV | this document |
	| TBD | MPLS Cross Connect FEC TLV | this document |		| 557 | MPLS Cross Connect FEC TLV | this document |
	| TBD | MPLS-TE Policy State TLV | this document |		| 1200 | MPLS-TE Policy State TLV | this document |
	| TBD | SR BSID TLV | this document |		| 1201 | SR BSID TLV | this document |
	| TBD | SR CP State TLV | this document |		| 1202 | SR CP State TLV | this document |
	| TBD | SR CP Name TLV | this document |		| 1203 | SR CP Name TLV | this document |
	| TBD | SR CP Constraints TLV | this document |		| 1204 | SR CP Constraints TLV | this document |
	| TBD | SR Segment List TLV | this document |		| 1205 | SR Segment List TLV | this document |
	| TBD | SR Segment sub-TLV | this document |		| 1206 | SR Segment sub-TLV | this document |
	| TBD | SR Segment List Metric sub-TLV | this document |		| 1207 | SR Segment List Metric sub-TLV | this document |
	| TBD | SR Affinity Constraint sub-TLV | this document |		| 1208 | SR Affinity Constraint sub-TLV | this document |
	| TBD | SR SRLG Constraint sub-TLV | this document |		| 1209 | SR SRLG Constraint sub-TLV | this document |
	| TBD | SR Bandwidth Constraint sub-TLV | this document |		| 1210 | SR Bandwidth Constraint sub-TLV | this document |
	| TBD | SR Disjoint Group Constraint sub-TLV | this document |		| 1211 | SR Disjoint Group Constraint sub-TLV | this document |
	+----------+----------------------------------------+---------------+		+----------+----------------------------------------+---------------+
	9.4. BGP-LS SR Policy Protocol Origin		9.4. BGP-LS SR Policy Protocol Origin
	This document requests IANA to maintain a new sub-registry under		This document requests IANA to maintain a new sub-registry under
	"Border Gateway Protocol - Link State (BGP-LS) Parameters". The new		"Border Gateway Protocol - Link State (BGP-LS) Parameters". The new
	registry is called "SR Policy Protocol Origin" and contains the		registry is called "SR Policy Protocol Origin" and contains the
	codepoints allocated to the "Protocol Origin" field defined in		codepoints allocated to the "Protocol Origin" field defined in
	Section 4.5. The registry contains the following codepoints		Section 4.5. The registry contains the following codepoints
	(suggested values, to be assigned by IANA):		(suggested values, to be assigned by IANA):
	skipping to change at page 45, line 18 ¶		skipping to change at page 46, line 18 ¶
	| 0 | IGP Metric |		| 0 | IGP Metric |
	| 1 | Min Unidirectional Link Delay [RFC7471] |		| 1 | Min Unidirectional Link Delay [RFC7471] |
	| 2 | TE Metric [RFC3630] |		| 2 | TE Metric [RFC3630] |
	+------------+-----------------------------------------+		+------------+-----------------------------------------+
	10. Security Considerations		10. Security Considerations
	Procedures and protocol extensions defined in this document do not		Procedures and protocol extensions defined in this document do not
	affect the BGP security model. See [RFC6952] for details.		affect the BGP security model. See [RFC6952] for details.
	11. Acknowledgements		11. Contributors
	The authors would like to thank Dhruv Dhody, Mohammed Abdul Aziz
	Khalid, Lou Berger, Acee Lindem, Siva Sivabalan, Arjun Sreekantiah,
	and Dhanendra Jain for their review and valuable comments.
	12. Contributors
	The following people have substantially contributed to the editing of		The following people have substantially contributed to the editing of
	this document:		this document:
	Clarence Filsfils		Clarence Filsfils
	Cisco Systems		Cisco Systems
	Email: cfilsfil@cisco.com		Email: cfilsfil@cisco.com
			12. Acknowledgements
			The authors would like to thank Dhruv Dhody, Mohammed Abdul Aziz
			Khalid, Lou Berger, Acee Lindem, Siva Sivabalan, Arjun Sreekantiah,
			and Dhanendra Jain for their review and valuable comments.
	13. References		13. References
	13.1. Normative References		13.1. Normative References
			[I-D.ietf-idr-bgpls-segment-routing-epe]
			Previdi, S., Talaulikar, K., Filsfils, C., Patel, K., Ray,
			S., and J. Dong, "BGP-LS extensions for Segment Routing
			BGP Egress Peer Engineering", draft-ietf-idr-bgpls-
			segment-routing-epe-18 (work in progress), March 2019.
	[I-D.ietf-spring-segment-routing-policy]		[I-D.ietf-spring-segment-routing-policy]
	Filsfils, C., Sivabalan, S., daniel.voyer@bell.ca, d.,		Filsfils, C., Sivabalan, S., daniel.voyer@bell.ca, d.,
	bogdanov@google.com, b., and P. Mattes, "Segment Routing		bogdanov@google.com, b., and P. Mattes, "Segment Routing
	Policy Architecture", draft-ietf-spring-segment-routing-		Policy Architecture", draft-ietf-spring-segment-routing-
	policy-02 (work in progress), October 2018.		policy-02 (work in progress), October 2018.
	[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate		[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
	Requirement Levels", BCP 14, RFC 2119,		Requirement Levels", BCP 14, RFC 2119,
	DOI 10.17487/RFC2119, March 1997,		DOI 10.17487/RFC2119, March 1997,
	<https://www.rfc-editor.org/info/rfc2119>.		<https://www.rfc-editor.org/info/rfc2119>.
	skipping to change at page 47, line 37 ¶		skipping to change at page 48, line 48 ¶
	[RFC4202] Kompella, K., Ed. and Y. Rekhter, Ed., "Routing Extensions		[RFC4202] Kompella, K., Ed. and Y. Rekhter, Ed., "Routing Extensions
	in Support of Generalized Multi-Protocol Label Switching		in Support of Generalized Multi-Protocol Label Switching
	(GMPLS)", RFC 4202, DOI 10.17487/RFC4202, October 2005,		(GMPLS)", RFC 4202, DOI 10.17487/RFC4202, October 2005,
	<https://www.rfc-editor.org/info/rfc4202>.		<https://www.rfc-editor.org/info/rfc4202>.
	[RFC4655] Farrel, A., Vasseur, J., and J. Ash, "A Path Computation		[RFC4655] Farrel, A., Vasseur, J., and J. Ash, "A Path Computation
	Element (PCE)-Based Architecture", RFC 4655,		Element (PCE)-Based Architecture", RFC 4655,
	DOI 10.17487/RFC4655, August 2006,		DOI 10.17487/RFC4655, August 2006,
	<https://www.rfc-editor.org/info/rfc4655>.		<https://www.rfc-editor.org/info/rfc4655>.
			[RFC5065] Traina, P., McPherson, D., and J. Scudder, "Autonomous
			System Confederations for BGP", RFC 5065,
			DOI 10.17487/RFC5065, August 2007,
			<https://www.rfc-editor.org/info/rfc5065>.
	[RFC6952] Jethanandani, M., Patel, K., and L. Zheng, "Analysis of		[RFC6952] Jethanandani, M., Patel, K., and L. Zheng, "Analysis of
	BGP, LDP, PCEP, and MSDP Issues According to the Keying		BGP, LDP, PCEP, and MSDP Issues According to the Keying
	and Authentication for Routing Protocols (KARP) Design		and Authentication for Routing Protocols (KARP) Design
	Guide", RFC 6952, DOI 10.17487/RFC6952, May 2013,		Guide", RFC 6952, DOI 10.17487/RFC6952, May 2013,
	<https://www.rfc-editor.org/info/rfc6952>.		<https://www.rfc-editor.org/info/rfc6952>.
	[RFC7308] Osborne, E., "Extended Administrative Groups in MPLS		[RFC7308] Osborne, E., "Extended Administrative Groups in MPLS
	Traffic Engineering (MPLS-TE)", RFC 7308,		Traffic Engineering (MPLS-TE)", RFC 7308,
	DOI 10.17487/RFC7308, July 2014,		DOI 10.17487/RFC7308, July 2014,
	<https://www.rfc-editor.org/info/rfc7308>.		<https://www.rfc-editor.org/info/rfc7308>.
End of changes. 16 change blocks.
	77 lines changed or deleted		118 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/