draft-ietf-idr-bgp-prefix-sid-07.txt		draft-ietf-idr-bgp-prefix-sid-08.txt
	IDR S. Previdi, Ed.		IDR S. Previdi, Ed.
	Internet-Draft C. Filsfils		Internet-Draft C. Filsfils
	Intended status: Standards Track A. Lindem		Intended status: Standards Track A. Lindem
	Expires: April 20, 2018 A. Sreekantiah		Expires: July 6, 2018 Cisco Systems
	Cisco Systems		A. Sreekantiah
	H. Gredler		H. Gredler
	RtBrick Inc.		RtBrick Inc.
	October 17, 2017		January 2, 2018
	Segment Routing Prefix SID extensions for BGP		Segment Routing Prefix SID extensions for BGP
	draft-ietf-idr-bgp-prefix-sid-07		draft-ietf-idr-bgp-prefix-sid-08
	Abstract		Abstract
	Segment Routing (SR) architecture allows a node to steer a packet		Segment Routing (SR) architecture allows a node to steer a packet
	flow through any topological path and service chain by leveraging		flow through any topological path and service chain by leveraging
	source routing. The ingress node prepends a SR header to a packet		source routing. The ingress node prepends a SR header to a packet
	containing a set of segment identifiers (SID). Each SID represents a		containing a set of segment identifiers (SID). Each SID represents a
	topological or a service-based instruction. Per-flow state is		topological or a service-based instruction. Per-flow state is
	maintained only at the ingress node of the SR domain.		maintained only on the ingress node of the SR domain.
	This document defines a new optional, transitive BGP attribute for		This document defines an optional, transitive BGP attribute for
	announcing BGP Prefix Segment Identifiers (BGP Prefix-SID)		announcing BGP Prefix Segment Identifiers (BGP Prefix-SID)
	information.		information.
	Requirements Language		Requirements Language
	The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",		The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
	"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this		"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
	document are to be interpreted as described in RFC 2119 [RFC2119]		document are to be interpreted as described in RFC 2119 [RFC2119]
	only when they appear in all upper case. They may also appear in		only when they appear in all upper case. They may also appear in
	lower or mixed case as English words, without any normative meaning.		lower or mixed case as English words, without any normative meaning.
	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). 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 http://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 April 20, 2018.
			This Internet-Draft will expire on July 6, 2018.
	Copyright Notice		Copyright Notice
	Copyright (c) 2017 IETF Trust and the persons identified as the		Copyright (c) 2018 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		(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
	carefully, as they describe your rights and restrictions with respect		carefully, as they describe your rights and restrictions with respect
	to this document. Code Components extracted from this document must		to this document. Code Components extracted from this document must
	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. BGP-Prefix-SID . . . . . . . . . . . . . . . . . . . . . . . 4		2. BGP-Prefix-SID . . . . . . . . . . . . . . . . . . . . . . . 4
	2.1. MPLS BGP Prefix SID . . . . . . . . . . . . . . . . . . . 4		2.1. MPLS BGP Prefix SID . . . . . . . . . . . . . . . . . . . 4
	2.2. IPv6 Prefix Segment . . . . . . . . . . . . . . . . . . . 5		2.2. IPv6 Prefix Segment . . . . . . . . . . . . . . . . . . . 5
	3. BGP-Prefix-SID Attribute . . . . . . . . . . . . . . . . . . 5		3. BGP-Prefix-SID Attribute . . . . . . . . . . . . . . . . . . 5
	3.1. Label-Index TLV . . . . . . . . . . . . . . . . . . . . . 6		3.1. Label-Index TLV . . . . . . . . . . . . . . . . . . . . . 6
	3.2. IPv6 SID . . . . . . . . . . . . . . . . . . . . . . . . 7		3.2. IPv6 SID . . . . . . . . . . . . . . . . . . . . . . . . 6
	3.3. Originator SRGB TLV . . . . . . . . . . . . . . . . . . . 7		3.3. Originator SRGB TLV . . . . . . . . . . . . . . . . . . . 7
	4. Receiving BGP-Prefix-SID Attribute . . . . . . . . . . . . . 9		4. Receiving BGP-Prefix-SID Attribute . . . . . . . . . . . . . 9
	4.1. MPLS Dataplane: Labeled Unicast . . . . . . . . . . . . . 9		4.1. MPLS Dataplane: Labeled Unicast . . . . . . . . . . . . . 9
	4.2. IPv6 Dataplane . . . . . . . . . . . . . . . . . . . . . 10		4.2. IPv6 Dataplane . . . . . . . . . . . . . . . . . . . . . 10
	5. Announcing BGP-Prefix-SID Attribute . . . . . . . . . . . . . 10		5. Announcing BGP-Prefix-SID Attribute . . . . . . . . . . . . . 10
	5.1. MPLS Dataplane: Labeled Unicast . . . . . . . . . . . . . 10		5.1. MPLS Dataplane: Labeled Unicast . . . . . . . . . . . . . 10
	5.2. IPv6 Dataplane . . . . . . . . . . . . . . . . . . . . . 11		5.2. IPv6 Dataplane . . . . . . . . . . . . . . . . . . . . . 11
	6. Error Handling of BGP-Prefix-SID Attribute . . . . . . . . . 11		6. Error Handling of BGP-Prefix-SID Attribute . . . . . . . . . 11
	7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 12		7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 12
	8. Manageability Considerations . . . . . . . . . . . . . . . . 12		8. Manageability Considerations . . . . . . . . . . . . . . . . 12
	skipping to change at page 3, line 34 ¶		skipping to change at page 3, line 34 ¶
	attached to a BGP prefix. A BGP Prefix-SID is always a global SID		attached to a BGP prefix. A BGP Prefix-SID is always a global SID
	([I-D.ietf-spring-segment-routing]) within the SR/BGP domain (i.e.,		([I-D.ietf-spring-segment-routing]) within the SR/BGP domain (i.e.,
	the set of Autonomous Systems under a common administration and		the set of Autonomous Systems under a common administration and
	control and where SR is used) and identifies an instruction to		control and where SR is used) and identifies an instruction to
	forward the packet over the ECMP-aware best-path computed by BGP to		forward the packet over the ECMP-aware best-path computed by BGP to
	the related prefix. The BGP Prefix-SID is the identifier of the BGP		the related prefix. The BGP Prefix-SID is the identifier of the BGP
	prefix segment. In this document, we always refer to the BGP Segment		prefix segment. In this document, we always refer to the BGP Segment
	by the BGP Prefix-SID.		by the BGP Prefix-SID.
	This document describes the BGP extension to signal the BGP Prefix-		This document describes the BGP extension to signal the BGP Prefix-
	SID. Specifically, this document defines a new BGP attribute known		SID. Specifically, this document defines a BGP attribute known as
	as the BGP Prefix-SID attribute and specifies the rules to originate,		the BGP Prefix-SID attribute and specifies the rules to originate,
	receive and handle error conditions of the new attribute.		receive, and handle error conditions for the attribute.
	As described in [I-D.ietf-spring-segment-routing-msdc], the BGP		The BGP Prefix-SID attribute defined in this document can be attached
	Prefix-SID attribute defined in this document can be attached to		to prefixes from AFI/SAFI:
	prefixes from AFI/SAFI:
	Multiprotocol BGP labeled IPv4/IPv6 Unicast ([RFC3107]).		Multiprotocol BGP labeled IPv4/IPv6 Unicast ([RFC8277]).
	Multiprotocol BGP ([RFC4760]) unlabeled IPv6 Unicast.		Multiprotocol BGP ([RFC4760]) unlabeled IPv6 Unicast.
	[I-D.ietf-spring-segment-routing-msdc] describes use cases where the		[I-D.ietf-spring-segment-routing-msdc] describes example use cases
	Prefix-SID is used for the above AFI/SAFI.		where the Prefix-SID is used for the above AFI/SAFI.
	It has to be noted that:		It should be noted that:
	o A BGP Prefix-SID MAY be global between domains when the		o A BGP Prefix-SID MAY be global between domains when the
	interconnected domains agree on the SID allocation scheme.		interconnected domains agree on the SID allocation scheme.
	Alternatively, when interconnecting domains, the ASBRs of each		Alternatively, when interconnecting domains, the ASBRs of each
	domain will have to handle the advertisement of unique SIDs. The		domain will have to handle the advertisement of unique SIDs. The
	mechanisms for such interconnection are outside the scope of the		mechanisms for such interconnection are outside the scope of the
	protocol extensions defined in this document.		protocol extensions defined in this document.
	o As described in [I-D.ietf-spring-segment-routing-msdc], a BGP		o A BGP Prefix-SID MAY be attached to a prefix. In addition, each
	Prefix-SID MAY be attached to a prefix. In addition, each prefix		prefix will likely have a different AS_PATH attribute. This
	will likely have a different as_path attribute. This implies that		implies that each prefix is advertised individually, reducing the
	each prefix is advertised individually, reducing the ability to		ability to pack BGP advertisements (when sharing common
	pack BGP advertisements (when sharing common attributes).		attributes).
	2. BGP-Prefix-SID		2. BGP-Prefix-SID
	The BGP Prefix-SID attached to a BGP prefix P represents the		The BGP Prefix-SID attached to a BGP prefix P represents the
	instruction "go to Prefix P" along its BGP bestpath (potentially		instruction "go to Prefix P" along its BGP best path (potentially
	ECMP-enabled).		ECMP-enabled).
	2.1. MPLS BGP Prefix SID		2.1. MPLS BGP Prefix SID
	The BGP Prefix-SID is realized on the MPLS dataplane		The BGP Prefix-SID is realized on the MPLS dataplane
	([I-D.ietf-spring-segment-routing-mpls]) in the following way:		([I-D.ietf-spring-segment-routing-mpls]) in the following way:
	As described in [I-D.ietf-spring-segment-routing-msdc] the		The operator assigns a globally unique "index", L_I, to a locally
	operator assigns a globally unique "index", L_I, to a locally
	sourced prefix of a BGP speaker N which is advertised to all other		sourced prefix of a BGP speaker N which is advertised to all other
	BGP speakers in the SR domain.		BGP speakers in the SR domain.
	According to [I-D.ietf-spring-segment-routing], each BGP speaker		According to [I-D.ietf-spring-segment-routing], each BGP speaker
	is configured with a label block called the Segment Routing Global		is configured with a label block called the Segment Routing Global
	Block (SRGB). While [I-D.ietf-spring-segment-routing] recommends		Block (SRGB). While [I-D.ietf-spring-segment-routing] recommends
	to use the same SRGB across all the nodes within the SR domain,		to use the same SRGB across all the nodes within the SR domain,
	the SRGB of a node is a local property and could be different on		the SRGB of a node is a local property and could be different on
	different speakers. The drawbacks of the use case where BGP		different speakers. The drawbacks of the use case where BGP
	speakers have different SRGBs are documented in		speakers have different SRGBs are documented in
	[I-D.ietf-spring-segment-routing] and		[I-D.ietf-spring-segment-routing] and
	[I-D.ietf-spring-segment-routing-msdc].		[I-D.ietf-spring-segment-routing-msdc].
	If traffic-engineering within the SR domain is required, each node		If traffic-engineering within the SR domain is required, each node
	may also be required to advertise topological information and		may also be required to advertise topological information and
	Peering SID's for each of its links and peers. This information		Peering SID's for each of its links and peers. This information
	is required in order to perform the explicit path computation and		is required to perform the explicit path computation and to
	to express any explicit path into a list of SIDs. The		express any explicit path into a list of SIDs. The advertisement
	advertisement of topological information and Peer segments (Peer		of topological information and Peer segments (Peer SIDs) is
	SIDs) is assumed to be done through		assumed to be done through
	[I-D.ietf-idr-bgpls-segment-routing-epe].		[I-D.ietf-idr-bgpls-segment-routing-epe].
	If the BGP speakers are not all configured with the same SRGB, and		If the BGP speakers are not all configured with the same SRGB, and
	if traffic-engineering within the SR domain is required, each node		if traffic-engineering within the SR domain is required, each node
	may be required to advertise its local SRGB in addition to the		may be required to advertise its local SRGB in addition to the
	topological information.		topological information.
	This documents assumes that BGP-LS is the preferred method for		This documents assumes that BGP-LS is the preferred method for
	collecting both topological, peer segments (Peer SIDs) and SRGB		collecting both topological, peer segments (Peer SIDs) and SRGB
	information through [RFC7752],		information through [RFC7752],
	skipping to change at page 5, line 21 ¶		skipping to change at page 5, line 19 ¶
	[I-D.ietf-idr-bgp-ls-segment-routing-ext]. However, as an		[I-D.ietf-idr-bgp-ls-segment-routing-ext]. However, as an
	optional alternative for the advertisement of the local SRGB		optional alternative for the advertisement of the local SRGB
	without the topology nor the peer SID's, hence without		without the topology nor the peer SID's, hence without
	applicability for TE, the Originator SRGB TLV of the prefix-SID		applicability for TE, the Originator SRGB TLV of the prefix-SID
	attribute, is specified in Section 3.3 of this document.		attribute, is specified in Section 3.3 of this document.
	As defined in [I-D.ietf-spring-segment-routing-mpls], the index		As defined in [I-D.ietf-spring-segment-routing-mpls], the index
	L_I is an offset in the SRGB. Each BGP speaker derives its local		L_I is an offset in the SRGB. Each BGP speaker derives its local
	MPLS label, L, by adding L_I to the start value of its own SRGB,		MPLS label, L, by adding L_I to the start value of its own SRGB,
	and programs L in its MPLS dataplane as its incoming/local label		and programs L in its MPLS dataplane as its incoming/local label
	for the prefix. It has to be noted that while SRGBs and SIDs are		for the prefix. It should be noted that while SRGBs and SIDs are
	advertised using 32 bit values, the derived label is to be		advertised using 32-bit values, the derived label is to be
	considered as the 20 right-most bits. See Section 4.1 for more		considered as the 20 right-most bits. See Section 4.1 for more
	details.		details.
	The outgoing label for the prefix is found in the NLRI of the		The outgoing label for the prefix is found in the NLRI of the
	Multiprotocol BGP labeled IPv4/IPv6 Unicast prefix advertisement.		Multiprotocol BGP labeled IPv4/IPv6 Unicast prefix advertisement.
	The index L_I is only used as a hint to derive the local/incoming		The index L_I is only used as a hint to derive the local/incoming
	label.		label.
	Section 3.1 of this document specifies the Label-Index TLV of the		Section 3.1 of this document specifies the Label-Index TLV of the
	BGP Prefix-SID attribute; this TLV can be used to advertise the		BGP Prefix-SID attribute; this TLV can be used to advertise the
	label index of a given prefix.		label index of a given prefix.
	In order to advertise the label index of a given prefix P and,		In order to advertise the label index of a given prefix P and,
	optionally, the SRGB, a new extension to BGP is needed: the BGP		optionally, the SRGB, an extension to BGP is needed: the BGP Prefix-
	Prefix-SID attribute. This extension is described in subsequent		SID attribute. This extension is described in subsequent sections.
	sections.
	2.2. IPv6 Prefix Segment		2.2. IPv6 Prefix Segment
	As illustrated in [I-D.ietf-spring-segment-routing-msdc], when SR is		When SR is used over an IPv6 dataplane, the BGP Prefix-SID consists
	used over an IPv6 dataplane, the BGP Prefix-SID consists of an IPv6		of an IPv6 address assigned to the BGP speaker.
	address assigned to the BGP speaker.
	3. BGP-Prefix-SID Attribute		3. BGP-Prefix-SID Attribute
	The BGP Prefix-SID attribute is an optional, transitive BGP path		The BGP Prefix-SID attribute is an optional, transitive BGP path
	attribute. The attribute type code 40 has been assigned by IANA (see		attribute. The attribute type code 40 has been assigned by IANA (see
	Section 7).		Section 7).
	The BGP Prefix-SID attribute is defined here to be a set of elements		The BGP Prefix-SID attribute is defined here to be a set of elements
	encoded as "Type/Length/Value" (i.e., a set of TLVs). The following		encoded as "Type/Length/Value" (i.e., a set of TLVs). The following
	TLVs are defined:		TLVs are defined:
	skipping to change at page 6, line 23 ¶		skipping to change at page 6, line 16 ¶
	o Originator SRGB TLV		o Originator SRGB TLV
	Label-Index and Originator SRGB TLVs are used only when SR is applied		Label-Index and Originator SRGB TLVs are used only when SR is applied
	to the MPLS dataplane.		to the MPLS dataplane.
	IPv6 SID TLV is used only when SR is applied to the IPv6 dataplane.		IPv6 SID TLV is used only when SR is applied to the IPv6 dataplane.
	3.1. Label-Index TLV		3.1. Label-Index TLV
	The Label-Index TLV MUST be present in the Prefix-SID attribute		The Label-Index TLV MUST be present in the Prefix-SID attribute
	attached to Labeled IPv4/IPv6 unicast prefixes ([RFC3107]) and has		attached to Labeled IPv4/IPv6 unicast prefixes ([RFC8277]) and has
	the following format:		the following format:
	0 1 2 3		0 1 2 3
	0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1		0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
	+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+		+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
	| Type | Length | RESERVED |		| Type | Length | RESERVED |
	+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+		+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
	| Flags | Label Index |		| Flags | Label Index |
	+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+		+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
	| Label Index |		| Label Index |
	+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+		+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
	where:		where:
	o Type is 1.		o Type is 1.
	o Length: is 7, the total length of the value portion of the TLV.		o Length: is 7, the total length of the value portion of the TLV.
	o RESERVED: 8 bit field. MUST be clear on transmission an MUST be		o RESERVED: 8-bit field. MUST be clear on transmission and MUST be
	ignored at reception..		ignored on reception.
	o Flags: 16 bits of flags. None is defined by this document. The		o Flags: 16 bits of flags. None are defined by this document. The
	flag field MUST be clear on transmission and MUST be ignored at		flag field MUST be clear on transmission and MUST be ignored on
	reception.		reception.
	o Label Index: 32 bit value representing the index value in the SRGB		o Label Index: 32-bit value representing the index value in the SRGB
	space.		space.
	3.2. IPv6 SID		3.2. IPv6 SID
	The IPv6-SID TLV MAY be present in the Prefix-SID attribute attached		The IPv6-SID TLV MAY be present in the Prefix-SID attribute attached
	to MP-BGP unlabeled IPv6 unicast prefixes ([RFC4760]) and has the		to MP-BGP unlabeled IPv6 unicast prefixes ([RFC4760]) and has the
	following format:		following format:
	0 1 2 3		0 1 2 3
	0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1		0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
	skipping to change at page 7, line 31 ¶		skipping to change at page 7, line 25 ¶
	| +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+		| +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
	| |		| |
	+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+		+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
	where:		where:
	o Type is 2.		o Type is 2.
	o Length: is 19, the total length of the value portion of the TLV.		o Length: is 19, the total length of the value portion of the TLV.
	o RESERVED: 24 bit field for future use. MUST be clear on		o RESERVED: 24-bit field for future use. MUST be clear on
	transmission an MUST be ignored at reception.		transmission and MUST be ignored on reception.
	o IPv6 SID: 16 octets.		o IPv6 SID: 16 octets.
	3.3. Originator SRGB TLV		3.3. Originator SRGB TLV
	The Originator SRGB TLV is an optional TLV and has the following		The Originator SRGB TLV is an optional TLV and has the following
	format:		format:
	0 1 2 3		0 1 2 3
	0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1		0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
	skipping to change at page 8, line 32 ¶		skipping to change at page 8, line 32 ¶
	| |		| |
	+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+		+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
	where:		where:
	o Type is 3.		o Type is 3.
	o Length is the total length of the value portion of the TLV: 2 +		o Length is the total length of the value portion of the TLV: 2 +
	multiple of 6.		multiple of 6.
	o Flags: 16 bits of flags. None is defined in this document. Flags		o Flags: 16 bits of flags. None are defined in this document.
	MUST be clear on transmission an MUST be ignored at reception.		Flags MUST be clear on transmission and MUST be ignored on
			reception.
	o SRGB: 3 octets of base followed by 3 octets of range. Note that		o SRGB: 3 octets of base followed by 3 octets of range. Note that
	the SRGB field MAY appear multiple times. If the SRGB field		the SRGB field MAY appear multiple times. If the SRGB field
	appears multiple times, the SRGB consists of multiple ranges.		appears multiple times, the SRGB consists of multiple ranges.
	The Originator SRGB TLV contains the SRGB of the node originating the		The Originator SRGB TLV contains the SRGB of the node originating the
	prefix to which the BGP Prefix-SID is attached. The Originator SRGB		prefix to which the BGP Prefix-SID is attached. The Originator SRGB
	TLV MUST NOT be changed during the propagation of the BGP update.		TLV MUST NOT be changed during the propagation of the BGP update.
	The originator SRGB describes the SRGB of the node where the BGP		The originator SRGB describes the SRGB of the node where the BGP
	Prefix SID is attached. It is used to build segment routing policies		Prefix SID is attached. It is used to build segment routing policies
	when different SRGB's are used in the fabric		when different SRGBs are used in the fabric, for example
	([I-D.ietf-spring-segment-routing-msdc]).		([I-D.ietf-spring-segment-routing-msdc]).
	The originator SRGB may only appear on Prefix-SID attribute attached		The originator SRGB may only appear on Prefix-SID attribute attached
	to prefixes of SAFI 4 (labeled unicast, [RFC3107]).		to prefixes of SAFI 4 (labeled unicast, [RFC8277]).
	4. Receiving BGP-Prefix-SID Attribute		4. Receiving BGP-Prefix-SID Attribute
	A BGP speaker receiving a BGP Prefix-SID attribute from an EBGP		A BGP speaker receiving a BGP Prefix-SID attribute from an EBGP
	neighbor residing outside the boundaries of the SR domain, SHOULD		neighbor residing outside the boundaries of the SR domain, SHOULD
	discard the attribute unless it is configured to accept the attribute		discard the attribute unless it is configured to accept the attribute
	from the EBGP neighbor. A BGP speaker MAY log an error for further		from the EBGP neighbor. A BGP speaker MAY log an error for further
	analysis when discarding an attribute.		analysis when discarding an attribute.
	4.1. MPLS Dataplane: Labeled Unicast		4.1. MPLS Dataplane: Labeled Unicast
	A Multiprotocol BGP labeled IPv4/IPv6 Unicast ([RFC3107]) session		A Multiprotocol BGP labeled IPv4/IPv6 Unicast ([RFC8277]) session
	type is required.		type is required.
	A BGP speaker MAY be locally configured with an SRGB=[SRGB_Start,		A BGP speaker MAY be locally configured with an SRGB=[SRGB_Start,
	SRGB_End]. The preferred method for deriving the SRGB is a matter of		SRGB_End]. The preferred method for deriving the SRGB is a matter of
	local node configuration.		local node configuration.
	Given a label_index L_I, we call L = L_I + SRGB_Start as the derived		Given a label_index L_I, we call L = L_I + SRGB_Start as the derived
	label. A BGP Prefix-SID attribute is called "unacceptable" for a		label. A BGP Prefix-SID attribute is designated "unacceptable" for a
	speaker M if the derived label value L lies outside the SRGB		speaker M if the derived label value L lies outside the SRGB
	configured on M. Otherwise the Label Index attribute is called		configured on M. Otherwise the Label Index attribute is designated
	"acceptable" to speaker M.		"acceptable" to speaker M.
	The mechanisms through which a given label_index value is assigned to		The mechanisms through which a given label_index value is assigned to
	a given prefix are outside the scope of this document. The label-		a given prefix are outside the scope of this document. The label-
	index value associated with a prefix is locally configured at the BGP		index value associated with a prefix is locally configured at the BGP
	node originating the prefix.		node originating the prefix.
	The Prefix-SID attribute MUST contain the Label-Index TLV and MAY		The Prefix-SID attribute MUST contain the Label-Index TLV and MAY
	contain the Originator SRGB TLV. A BGP Prefix-SID attribute received		contain the Originator SRGB TLV. A BGP Prefix-SID attribute received
	without a Label-Index TLV MUST be considered as "unacceptable" by the		without a Label-Index TLV MUST be considered as "unacceptable" by the
	receiving speaker.		receiving speaker.
	If multiple prefixes are received with the same label_index value,		If multiple prefixes are received with the same label_index value,
	all these prefixes MUST have their BGP Prefix-SID attribute		all these prefixes MUST have their BGP Prefix-SID attribute
	considered as "unacceptable" by the receiving speaker.		considered as "unacceptable" by the receiving speaker.
	When a BGP speaker receives a path from a neighbor with an acceptable		When a BGP speaker receives a path from a neighbor with an acceptable
	BGP Prefix-SID attribute, it MUST program the derived label as the		BGP Prefix-SID attribute, it MUST program the derived label as the
	local label for the prefix in its MPLS dataplane. In case of any		local label for the prefix in its MPLS dataplane. In case of any
	error, a BGP speaker MUST resort to the error handling rules		error, a BGP speaker MUST follow to the error handling rules
	specified in Section 6. A BGP speaker MAY log an error for further		specified in Section 6. A BGP speaker MAY log an error for further
	analysis.		analysis.
	When a BGP speaker receives a path from a neighbor with an		When a BGP speaker receives a path from a neighbor with an
	unacceptable BGP Prefix-SID attribute or when a BGP speaker receives		unacceptable BGP Prefix-SID attribute or when a BGP speaker receives
	a path from a neighbor with a BGP Prefix-SID attribute but is unable		a path from a neighbor with a BGP Prefix-SID attribute but is unable
	to process it (it does not have the capability or local policy		to process it (it does not have the capability or local policy
	disables the capability), it MUST treat the path as if it came		disables the capability), it MUST treat the path as if it came
	without a Prefix-SID attribute. For the purposes of local label		without a Prefix-SID attribute. For the purposes of local label
	allocation, a BGP speaker MUST assign a local (also called dynamic)		allocation, a BGP speaker MUST assign a local (also called dynamic)
	label (non-SRGB) for such a prefix as per classic Multiprotocol BGP		label (non-SRGB) for such a prefix as per classic Multiprotocol BGP
	labeled IPv4/IPv6 Unicast ([RFC3107]) operation. A BGP speaker MAY		labeled IPv4/IPv6 Unicast ([RFC8277]) operation. A BGP speaker MAY
	log an error for further analysis.		log an error for further analysis.
	The outgoing label is always programmed as per classic Multiprotocol		The outgoing label is always programmed as per classic Multiprotocol
	BGP labeled IPv4/IPv6 Unicast (RFC3107 [RFC3107]) operation.		BGP labeled IPv4/IPv6 Unicast (RFC8277 [RFC8277]) operation.
	Specifically, a BGP speaker receiving a prefix with a Prefix-SID		Specifically, a BGP speaker receiving a prefix with a Prefix-SID
	attribute and a label NLRI field of implicit-null from a neighbor		attribute and a label NLRI field of implicit-null from a neighbor
	MUST adhere to standard behavior and program its MPLS dataplane to		MUST adhere to standard behavior and program its MPLS dataplane to
	pop the top label when forwarding traffic to the prefix. The label		pop the top label when forwarding traffic to the prefix. The label
	NLRI defines the outbound label that MUST be used by the receiving		NLRI defines the outbound label that MUST be used by the receiving
	node. The Label Index gives the information to the receiving node on		node. The Label Index gives the information to the receiving node on
	which local/incoming label the BGP speaker SHOULD use.		which local/incoming label the BGP speaker SHOULD use.
	4.2. IPv6 Dataplane		4.2. IPv6 Dataplane
	skipping to change at page 10, line 40 ¶		skipping to change at page 10, line 40 ¶
	A BGP speaker receiving a BGP Prefix-SID attribute from an EBGP		A BGP speaker receiving a BGP Prefix-SID attribute from an EBGP
	neighbor residing outside the boundaries of the SR domain, SHOULD		neighbor residing outside the boundaries of the SR domain, SHOULD
	discard the attribute unless it is configured to accept the attribute		discard the attribute unless it is configured to accept the attribute
	from the EBGP neighbor. A BGP speaker MAY log an error for further		from the EBGP neighbor. A BGP speaker MAY log an error for further
	analysis when discarding an attribute.		analysis when discarding an attribute.
	5. Announcing BGP-Prefix-SID Attribute		5. Announcing BGP-Prefix-SID Attribute
	The BGP Prefix-SID attribute MAY be attached to labeled BGP prefixes		The BGP Prefix-SID attribute MAY be attached to labeled BGP prefixes
	(IPv4/IPv6) [RFC3107] or to IPv6 prefixes [RFC4760]. In order to		(IPv4/IPv6) [RFC8277] or to IPv6 prefixes [RFC4760]. In order to
	prevent distribution of the BGP Prefix-SID attribute beyond its		prevent distribution of the BGP Prefix-SID attribute beyond its
	intended scope of applicability, attribute filtering SHOULD be		intended scope of applicability, attribute filtering SHOULD be
	deployed.		deployed.
	5.1. MPLS Dataplane: Labeled Unicast		5.1. MPLS Dataplane: Labeled Unicast
	A BGP speaker that originates a prefix attaches the Prefix-SID		A BGP speaker that originates a prefix attaches the Prefix-SID
	attribute when it advertises the prefix to its neighbors via		attribute when it advertises the prefix to its neighbors via
	Multiprotocol BGP labeled IPv4/IPv6 Unicast ([RFC3107]). The value		Multiprotocol BGP labeled IPv4/IPv6 Unicast ([RFC8277]). The value
	of the Label-Index in the Label-Index TLV is determined by		of the Label-Index in the Label-Index TLV is determined by
	configuration.		configuration.
	A BGP speaker that originates a Prefix-SID attribute MAY optionally		A BGP speaker that originates a Prefix-SID attribute MAY optionally
	announce Originator SRGB TLV along with the mandatory Label-Index		announce Originator SRGB TLV along with the mandatory Label-Index
	TLV. The content of the Originator SRGB TLV is determined by the		TLV. The content of the Originator SRGB TLV is determined by the
	configuration.		configuration.
	Since the Label-index value must be unique within an SR domain, by		Since the Label-index value must be unique within an SR domain, by
	default an implementation SHOULD NOT advertise the BGP Prefix-SID		default an implementation SHOULD NOT advertise the BGP Prefix-SID
	attribute outside an Autonomous System unless it is explicitly		attribute outside an Autonomous System unless it is explicitly
	configured to do so.		configured to do so.
	A BGP speaker that advertises a path received from one of its		A BGP speaker that advertises a path received from one of its
	neighbors SHOULD advertise the Prefix-SID received with the path		neighbors SHOULD advertise the Prefix-SID received with the path
	without modification regardless of whether the Prefix-SID was		without modification, regardless of whether the Prefix-SID was
	acceptable. If the path did not come with a Prefix-SID attribute,		acceptable. If the path did not come with a Prefix-SID attribute,
	the speaker MAY attach a Prefix-SID to the path if configured to do		the speaker MAY attach a Prefix-SID to the path if configured to do
	so. The content of the TLVs present in the Prefix-SID is determined		so. The content of the TLVs present in the Prefix-SID is determined
	by the configuration.		by the configuration.
	In all cases, the label field of the advertised NLRI ([RFC3107],		In all cases, the label field of the advertised NLRI ([RFC8277],
	[RFC4364]) MUST be set to the local/incoming label programmed in the		[RFC4364]) MUST be set to the local/incoming label programmed in the
	MPLS dataplane for the given advertised prefix. If the prefix is		MPLS dataplane for the given advertised prefix. If the prefix is
	associated with one of the BGP speakers interfaces, this label is the		associated with one of the BGP speaker's interfaces, this label is
	usual MPLS label (such as the implicit or explicit NULL label).		the usual MPLS label (such as the implicit or explicit NULL label).
	5.2. IPv6 Dataplane		5.2. IPv6 Dataplane
	A BGP speaker that originates an IPv6 prefix with the Prefix-SID		A BGP speaker that originates an IPv6 prefix with the Prefix-SID
	attribute, MAY include the IPv6 SID TLV.		attribute, MAY include the IPv6 SID TLV.
	A BGP speaker that advertises a path received from one of its		A BGP speaker that advertises a path received from one of its
	neighbors SHOULD advertise the Prefix-SID received with the path		neighbors SHOULD advertise the Prefix-SID received with the path
	without modification regardless of whether the Prefix-SID was		without modification, regardless of whether the Prefix-SID was
	acceptable. If the path did not come with a Prefix-SID attribute,		acceptable. If the path did not come with a Prefix-SID attribute,
	the speaker MAY attach a Prefix-SID to the path if configured to do		the speaker MAY attach a Prefix-SID to the path if configured to do
	so.		so.
	6. Error Handling of BGP-Prefix-SID Attribute		6. Error Handling of BGP-Prefix-SID Attribute
	When a BGP Speaker receives a BGP Update message containing a		When a BGP Speaker receives a BGP Update message containing a
	malformed BGP Prefix-SID attribute, it MUST ignore the received BGP		malformed BGP Prefix-SID attribute, it MUST ignore the received BGP
	Prefix-SID attributes and not pass it to other BGP peers. This is		Prefix-SID attributes and not pass it to other BGP peers. This is
	equivalent to the -attribute discard- action specified in [RFC7606].		equivalent to the "Attribute discard" action specified in [RFC7606].
	When discarding an attribute, a BGP speaker MAY log an error for		When discarding an attribute, a BGP speaker MAY log an error for
	further analysis.		further analysis.
	If the BGP Prefix-SID attribute appears more than once in an BGP		If the BGP Prefix-SID attribute appears more than once in an BGP
	Update message, then, according to [RFC7606], all the occurrences of		Update message, then, according to [RFC7606], all the occurrences of
	the attribute other than the first one SHALL be discarded and the BGP		the attribute other than the first one SHALL be discarded and the BGP
	Update message SHALL continue to be processed.		Update message SHALL continue to be processed.
	When a BGP speaker receives an unacceptable Prefix-SID attribute, it		When a BGP speaker receives an unacceptable Prefix-SID attribute, it
	MAY log an error for further analysis.		MAY log an error for further analysis.
	7. IANA Considerations		7. IANA Considerations
	This document defines a new BGP path attribute known as the BGP		This document defines a BGP path attribute known as the BGP Prefix-
	Prefix-SID attribute. This document requests IANA to assign a new		SID attribute. This document requests IANA to assign an attribute
	attribute code type (suggested value: 40) for BGP the Prefix-SID		code type (suggested value: 40) for BGP the Prefix-SID attribute from
	attribute from the BGP Path Attributes registry.		the BGP Path Attributes registry.
	Currently, IANA temporarily assigned the following:		Currently, IANA temporarily assigned the following:
	40 BGP Prefix-SID (TEMPORARY - registered 2015-09-30, expires		40 BGP Prefix-SID (TEMPORARY - registered 2015-09-30, expires
	2016-09-30) [draft-ietf-idr-bgp-prefix-sid]		2016-09-30) [draft-ietf-idr-bgp-prefix-sid]
	This document defines 3 new TLVs for BGP Prefix-SID attribute. These		This document defines 3 TLVs for BGP Prefix-SID attribute. These
	TLVs need to be registered with IANA. We request IANA to create a		TLVs need to be registered with IANA. We request IANA to create a
	new registry for BGP Prefix-SID Attribute TLVs as follows:		registry for BGP Prefix-SID Attribute TLVs as follows:
	Under "Border Gateway Protocol (BGP) Parameters" registry, "BGP		Under "Border Gateway Protocol (BGP) Parameters" registry, "BGP
	Prefix-SID attribute Types" Reference: draft-ietf-idr-bgp-prefix-sid		Prefix-SID attribute Types" Reference: draft-ietf-idr-bgp-prefix-sid
	Registration Procedure(s): Values 1-254 First Come, First Served,		Registration Procedure(s): Values 1-254 First Come, First Served,
	Value 0 and 255 reserved		Value 0 and 255 reserved
	Value Type Reference		Value Type Reference
	0 Reserved this document		0 Reserved this document
	1 Label-Index this document		1 Label-Index this document
	2 IPv6 SID this document		2 IPv6 SID this document
	3 Originator SRGB this document		3 Originator SRGB this document
	4-254 Unassigned		4-254 Unassigned
	255 Reserved this document		255 Reserved this document
	8. Manageability Considerations		8. Manageability Considerations
	This document defines a new BGP attribute in order to address the use		This document defines a BGP attribute to address use cases such as
	case described in [I-D.ietf-spring-segment-routing-msdc]. It i		the one described in [I-D.ietf-spring-segment-routing-msdc]. It is
	assumed that the new attribute (BGP Prefix-SID) advertisement is		assumed that the BGP Prefix-SID attribute advertisement is controlled
	controlled by the operator in order to:		by the operator in order to:
	o prevent undesired origination/advertisement of the BGP Prefix-SID		o Prevent undesired origination/advertisement of the BGP Prefix-SID
	attribute. By default, a BGP Prefix-SID attribute SHOULD NOT be		attribute. By default, a BGP Prefix-SID attribute SHOULD NOT be
	originated and attached to a prefix. The operator MUST be capable		originated and attached to a prefix. The operator MUST be capable
	of explicitly enabling the BGP Prefix-SID origination.		of explicitly enabling BGP Prefix-SID origination.
	o Prevent any undesired propagation of the BGP Prefix-SID attribute.		o Prevent any undesired propagation of the BGP Prefix-SID attribute.
	By default the BGP Prefix-SID is not advertised outside the		By default, the BGP Prefix-SID is not advertised outside the
	boundary of an AS. The propagation to other ASs MUST be		boundary of an AS. The propagation to other ASs MUST be
	explicitly configured.		explicitly configured.
	The deployment model described in		The deployment model described in
	[I-D.ietf-spring-segment-routing-msdc] assumes multiple Autonomous		[I-D.ietf-spring-segment-routing-msdc] assumes multiple Autonomous
	Systems (AS) under a common administration. The BGP Prefix-SID		Systems (AS) under a common administrative domain. For this use
	advertisement is therefore applicable to inter-AS context while it is		case, the BGP Prefix-SID advertisement is applicable to the inter-AS
	confined within a single SR Domain.		context, i.e., EBGP, while it is confined to a single administrative
			domain.
	9. Security Considerations		9. Security Considerations
	This document introduces a new BGP attribute (BGP Prefix-SID) which		This document introduces a BGP attribute (BGP Prefix-SID) which
	inherits the security considerations expressed in: [RFC4271] and		inherits the security considerations expressed in: [RFC4271] and
	[RFC3107].		[RFC8277].
	The BGP Prefix-SID attribute addresses the requirements introduced in		It should be noted, as described in Section 8, that this document
	[I-D.ietf-spring-segment-routing-msdc] and It has to be noted, as		refers to a deployment model where all nodes are under the single
	described in Section 8, that this document refer to a deployment		administrative domain. In this context, we assume that the operator
	model where all nodes are under the same administration. In this		doesn't want to leak outside of the domain any information related to
	context, we assume that the operator doesn't want to leak outside of		internal prefixes and topology. The internal information includes
	the domain any information related to internal prefixes and topology.		the BGP Prefix-SID. In order to prevent such leaking, the standard
	The internal information includes the BGP Prefix-SID. In order to		BGP mechanisms (filters) are applied on the boundary of the SR
	prevent such leaking, the standard BGP mechanisms (filters) are		domain.
	applied on the boundary of the SR domain.
	10. Contributors		10. Contributors
	Keyur Patel		Keyur Patel
	Arrcus, Inc.		Arrcus, Inc.
	US		US
	Email: Keyur@arrcus.com		Email: Keyur@arrcus.com
	Saikat Ray		Saikat Ray
	skipping to change at page 14, line 10 ¶		skipping to change at page 14, line 10 ¶
	11. Acknowledgements		11. Acknowledgements
	The authors would like to thanks Satya Mohanty for his contribution		The authors would like to thanks Satya Mohanty for his contribution
	to this document.		to this document.
	12. References		12. References
	12.1. Normative References		12.1. Normative References
	[I-D.ietf-spring-segment-routing]		[I-D.ietf-spring-segment-routing]
	Filsfils, C., Previdi, S., Decraene, B., Litkowski, S.,		Filsfils, C., Previdi, S., Ginsberg, L., Decraene, B.,
	and R. Shakir, "Segment Routing Architecture", draft-ietf-		Litkowski, S., and R. Shakir, "Segment Routing
	spring-segment-routing-12 (work in progress), June 2017.		Architecture", draft-ietf-spring-segment-routing-14 (work
			in progress), December 2017.
	[I-D.ietf-spring-segment-routing-mpls]		[I-D.ietf-spring-segment-routing-mpls]
	Filsfils, C., Previdi, S., Bashandy, A., Decraene, B.,		Filsfils, C., Previdi, S., Bashandy, A., Decraene, B.,
	Litkowski, S., and R. Shakir, "Segment Routing with MPLS		Litkowski, S., and R. Shakir, "Segment Routing with MPLS
	data plane", draft-ietf-spring-segment-routing-mpls-10		data plane", draft-ietf-spring-segment-routing-mpls-11
	(work in progress), June 2017.		(work in progress), October 2017.
	[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-
	<https://www.rfc-editor.org/info/rfc2119>.		editor.org/info/rfc2119>.
	[RFC3107] Rekhter, Y. and E. Rosen, "Carrying Label Information in
	BGP-4", RFC 3107, DOI 10.17487/RFC3107, May 2001,
	<https://www.rfc-editor.org/info/rfc3107>.
	[RFC4271] Rekhter, Y., Ed., Li, T., Ed., and S. Hares, Ed., "A		[RFC4271] Rekhter, Y., Ed., Li, T., Ed., and S. Hares, Ed., "A
	Border Gateway Protocol 4 (BGP-4)", RFC 4271,		Border Gateway Protocol 4 (BGP-4)", RFC 4271,
	DOI 10.17487/RFC4271, January 2006,		DOI 10.17487/RFC4271, January 2006, <https://www.rfc-
	<https://www.rfc-editor.org/info/rfc4271>.		editor.org/info/rfc4271>.
	[RFC4364] Rosen, E. and Y. Rekhter, "BGP/MPLS IP Virtual Private		[RFC4364] Rosen, E. and Y. Rekhter, "BGP/MPLS IP Virtual Private
	Networks (VPNs)", RFC 4364, DOI 10.17487/RFC4364, February		Networks (VPNs)", RFC 4364, DOI 10.17487/RFC4364, February
	2006, <https://www.rfc-editor.org/info/rfc4364>.		2006, <https://www.rfc-editor.org/info/rfc4364>.
	[RFC7606] Chen, E., Ed., Scudder, J., Ed., Mohapatra, P., and K.		[RFC7606] Chen, E., Ed., Scudder, J., Ed., Mohapatra, P., and K.
	Patel, "Revised Error Handling for BGP UPDATE Messages",		Patel, "Revised Error Handling for BGP UPDATE Messages",
	RFC 7606, DOI 10.17487/RFC7606, August 2015,		RFC 7606, DOI 10.17487/RFC7606, August 2015,
	<https://www.rfc-editor.org/info/rfc7606>.		<https://www.rfc-editor.org/info/rfc7606>.
			[RFC8277] Rosen, E., "Using BGP to Bind MPLS Labels to Address
			Prefixes", RFC 8277, DOI 10.17487/RFC8277, October 2017,
			<https://www.rfc-editor.org/info/rfc8277>.
	12.2. Informative References		12.2. Informative References
	[I-D.ietf-idr-bgp-ls-segment-routing-ext]		[I-D.ietf-idr-bgp-ls-segment-routing-ext]
	Previdi, S., Psenak, P., Filsfils, C., Gredler, H., and M.		Previdi, S., Psenak, P., Filsfils, C., Gredler, H., and M.
	Chen, "BGP Link-State extensions for Segment Routing",		Chen, "BGP Link-State extensions for Segment Routing",
	draft-ietf-idr-bgp-ls-segment-routing-ext-03 (work in		draft-ietf-idr-bgp-ls-segment-routing-ext-03 (work in
	progress), July 2017.		progress), July 2017.
	[I-D.ietf-idr-bgpls-segment-routing-epe]		[I-D.ietf-idr-bgpls-segment-routing-epe]
	Previdi, S., Filsfils, C., Patel, K., Ray, S., and J.		Previdi, S., Filsfils, C., Patel, K., Ray, S., and J.
	Dong, "BGP-LS extensions for Segment Routing BGP Egress		Dong, "BGP-LS extensions for Segment Routing BGP Egress
	Peer Engineering", draft-ietf-idr-bgpls-segment-routing-		Peer Engineering", draft-ietf-idr-bgpls-segment-routing-
	epe-13 (work in progress), June 2017.		epe-14 (work in progress), December 2017.
	[I-D.ietf-spring-segment-routing-msdc]		[I-D.ietf-spring-segment-routing-msdc]
	Filsfils, C., Previdi, S., Mitchell, J., Aries, E., and P.		Filsfils, C., Previdi, S., Mitchell, J., Aries, E., and P.
	Lapukhov, "BGP-Prefix Segment in large-scale data		Lapukhov, "BGP-Prefix Segment in large-scale data
	centers", draft-ietf-spring-segment-routing-msdc-05 (work		centers", draft-ietf-spring-segment-routing-msdc-08 (work
	in progress), June 2017.		in progress), December 2017.
	[RFC4760] Bates, T., Chandra, R., Katz, D., and Y. Rekhter,		[RFC4760] Bates, T., Chandra, R., Katz, D., and Y. Rekhter,
	"Multiprotocol Extensions for BGP-4", RFC 4760,		"Multiprotocol Extensions for BGP-4", RFC 4760,
	DOI 10.17487/RFC4760, January 2007,		DOI 10.17487/RFC4760, January 2007, <https://www.rfc-
	<https://www.rfc-editor.org/info/rfc4760>.		editor.org/info/rfc4760>.
	[RFC7752] Gredler, H., Ed., Medved, J., Previdi, S., Farrel, A., and		[RFC7752] Gredler, H., Ed., Medved, J., Previdi, S., Farrel, A., and
	S. Ray, "North-Bound Distribution of Link-State and		S. Ray, "North-Bound Distribution of Link-State and
	Traffic Engineering (TE) Information Using BGP", RFC 7752,		Traffic Engineering (TE) Information Using BGP", RFC 7752,
	DOI 10.17487/RFC7752, March 2016,		DOI 10.17487/RFC7752, March 2016, <https://www.rfc-
	<https://www.rfc-editor.org/info/rfc7752>.		editor.org/info/rfc7752>.
	Authors' Addresses		Authors' Addresses
	Stefano Previdi (editor)		Stefano Previdi (editor)
	Cisco Systems		Cisco Systems
	IT		IT
	Email: stefano@previdi.net		Email: stefano@previdi.net
	Clarence Filsfils		Clarence Filsfils
	skipping to change at page 16, line 5 ¶		skipping to change at page 16, line 5 ¶
	Email: cfilsfils@cisco.com		Email: cfilsfils@cisco.com
	Acee Lindem		Acee Lindem
	Cisco Systems		Cisco Systems
	170 W. Tasman Drive		170 W. Tasman Drive
	San Jose, CA 95124 95134		San Jose, CA 95124 95134
	USA		USA
	Email: acee@cisco.com		Email: acee@cisco.com
	Arjun Sreekantiah		Arjun Sreekantiah
	Cisco Systems
	170 W. Tasman Drive
	San Jose, CA 95124 95134
	USA
	Email: asreekan@cisco.com		Email: arjunhrs@gmail.com
	Hannes Gredler		Hannes Gredler
	RtBrick Inc.		RtBrick Inc.
	Email: hannes@rtbrick.com		Email: hannes@rtbrick.com
End of changes. 66 change blocks.
	120 lines changed or deleted		115 lines changed or added
This html diff was produced by rfcdiff 1.46. The latest version is available from http://tools.ietf.org/tools/rfcdiff/