< draft-ietf-idr-bgp-prefix-sid-06.txt		draft-ietf-idr-bgp-prefix-sid-07.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: December 18, 2017 A. Sreekantiah		Expires: April 20, 2018 A. Sreekantiah
	Cisco Systems		Cisco Systems
	H. Gredler		H. Gredler
	RtBrick Inc.		RtBrick Inc.
	June 16, 2017		October 17, 2017
	Segment Routing Prefix SID extensions for BGP		Segment Routing Prefix SID extensions for BGP
	draft-ietf-idr-bgp-prefix-sid-06		draft-ietf-idr-bgp-prefix-sid-07
	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 at the ingress node of the SR domain.
	skipping to change at page 1, line 44 ¶		skipping to change at page 1, line 44 ¶
	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 http://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 December 18, 2017.		This Internet-Draft will expire on April 20, 2018.
	Copyright Notice		Copyright Notice
	Copyright (c) 2017 IETF Trust and the persons identified as the		Copyright (c) 2017 IETF Trust and the persons identified as the
	document authors. All rights reserved.		document authors. All rights reserved.
	This document is subject to BCP 78 and the IETF Trust's Legal		This document is subject to BCP 78 and the IETF Trust's Legal
	Provisions Relating to IETF Documents		Provisions Relating to IETF Documents
	(http://trustee.ietf.org/license-info) in effect on the date of		(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
	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
	skipping to change at page 13, line 30 ¶		skipping to change at page 13, line 30 ¶
	[RFC3107].		[RFC3107].
	The BGP Prefix-SID attribute addresses the requirements introduced in		The BGP Prefix-SID attribute addresses the requirements introduced in
	[I-D.ietf-spring-segment-routing-msdc] and It has to be noted, as		[I-D.ietf-spring-segment-routing-msdc] and It has to be noted, as
	described in Section 8, that this document refer to a deployment		described in Section 8, that this document refer to a deployment
	model where all nodes are under the same administration. In this		model where all nodes are under the same administration. In this
	context, we assume that the operator doesn't want to leak outside of		context, we assume that the operator doesn't want to leak outside of
	the domain any information related to internal prefixes and topology.		the domain any information related to internal prefixes and topology.
	The internal information includes the BGP Prefix-SID. In order to		The internal information includes the BGP Prefix-SID. In order to
	prevent such leaking, the standard BGP mechanisms (filters) are		prevent such leaking, the standard BGP mechanisms (filters) are
	applied on the boundary of the 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 12 ¶		skipping to change at page 14, line 12 ¶
	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., Decraene, B., Litkowski, S.,
	and R. Shakir, "Segment Routing Architecture", draft-ietf-		and R. Shakir, "Segment Routing Architecture", draft-ietf-
	spring-segment-routing-11 (work in progress), February		spring-segment-routing-12 (work in progress), June 2017.
	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-08		data plane", draft-ietf-spring-segment-routing-mpls-10
	(work in progress), March 2017.		(work in progress), June 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,
	<http://www.rfc-editor.org/info/rfc2119>.		<https://www.rfc-editor.org/info/rfc2119>.
	[RFC3107] Rekhter, Y. and E. Rosen, "Carrying Label Information in		[RFC3107] Rekhter, Y. and E. Rosen, "Carrying Label Information in
	BGP-4", RFC 3107, DOI 10.17487/RFC3107, May 2001,		BGP-4", RFC 3107, DOI 10.17487/RFC3107, May 2001,
	<http://www.rfc-editor.org/info/rfc3107>.		<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,
	<http://www.rfc-editor.org/info/rfc4271>.		<https://www.rfc-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, <http://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,
	<http://www.rfc-editor.org/info/rfc7606>.		<https://www.rfc-editor.org/info/rfc7606>.
	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., Chen,		Previdi, S., Psenak, P., Filsfils, C., Gredler, H., and M.
	M., and j. jefftant@gmail.com, "BGP Link-State extensions		Chen, "BGP Link-State extensions for Segment Routing",
	for Segment Routing", draft-ietf-idr-bgp-ls-segment-		draft-ietf-idr-bgp-ls-segment-routing-ext-03 (work in
	routing-ext-01 (work in progress), February 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-12 (work in progress), April 2017.		epe-13 (work in progress), June 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-04 (work		centers", draft-ietf-spring-segment-routing-msdc-05 (work
	in progress), March 2017.		in progress), June 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,
	<http://www.rfc-editor.org/info/rfc4760>.		<https://www.rfc-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,
	<http://www.rfc-editor.org/info/rfc7752>.		<https://www.rfc-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
End of changes. 19 change blocks.
	25 lines changed or deleted		24 lines changed or added
This html diff was produced by rfcdiff 1.48. The latest version is available from http://tools.ietf.org/tools/rfcdiff/