draft-ietf-isis-segment-routing-extensions-19.txt		draft-ietf-isis-segment-routing-extensions-20.txt
	IS-IS for IP Internets S. Previdi, Ed.		IS-IS for IP Internets S. Previdi, Ed.
	Internet-Draft L. Ginsberg, Ed.		Internet-Draft Huawei
	Intended status: Standards Track C. Filsfils		Intended status: Standards Track L. Ginsberg, Ed.
	Expires: January 20, 2019 Cisco Systems, Inc.		Expires: May 12, 2019 C. Filsfils
			Cisco Systems, Inc.
	A. Bashandy		A. Bashandy
			Individual
	H. Gredler		H. Gredler
	RtBrick Inc.		RtBrick Inc.
	S. Litkowski
	B. Decraene		B. Decraene
	Orange		Orange
	J. Tantsura		November 8, 2018
	Nuage Networks
	July 19, 2018
	IS-IS Extensions for Segment Routing		IS-IS Extensions for Segment Routing
	draft-ietf-isis-segment-routing-extensions-19		draft-ietf-isis-segment-routing-extensions-20
	Abstract		Abstract
	Segment Routing (SR) allows for a flexible definition of end-to-end		Segment Routing (SR) allows for a flexible definition of end-to-end
	paths within IGP topologies by encoding paths as sequences of		paths within IGP topologies by encoding paths as sequences of
	topological sub-paths, called "segments". These segments are		topological sub-paths, called "segments". These segments are
	advertised by the link-state routing protocols (IS-IS and OSPF).		advertised by the link-state routing protocols (IS-IS and OSPF).
	This draft describes the necessary IS-IS extensions that need to be		This draft describes the necessary IS-IS extensions that need to be
	introduced for Segment Routing operating on an MPLS data-plane.		introduced for Segment Routing operating on an MPLS data-plane.
	skipping to change at page 2, line 10 ¶		skipping to change at page 2, line 7 ¶
	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 January 20, 2019.		This Internet-Draft will expire on May 12, 2019.
	Copyright Notice		Copyright Notice
	Copyright (c) 2018 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		(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 3, line 15 ¶		skipping to change at page 3, line 12 ¶
	5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 27		5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 27
	5.1. Sub TLVs for Type 22,23,25,141,222, and 223 . . . . . . . 27		5.1. Sub TLVs for Type 22,23,25,141,222, and 223 . . . . . . . 27
	5.2. Sub TLVs for Type 135,235,236 and 237 . . . . . . . . . . 28		5.2. Sub TLVs for Type 135,235,236 and 237 . . . . . . . . . . 28
	5.3. Sub TLVs for Type 242 . . . . . . . . . . . . . . . . . . 28		5.3. Sub TLVs for Type 242 . . . . . . . . . . . . . . . . . . 28
	5.4. New TLV Codepoint and Sub-TLV registry . . . . . . . . . 29		5.4. New TLV Codepoint and Sub-TLV registry . . . . . . . . . 29
	6. Security Considerations . . . . . . . . . . . . . . . . . . . 30		6. Security Considerations . . . . . . . . . . . . . . . . . . . 30
	7. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 30		7. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 30
	8. Contributors . . . . . . . . . . . . . . . . . . . . . . . . 30		8. Contributors . . . . . . . . . . . . . . . . . . . . . . . . 30
	9. References . . . . . . . . . . . . . . . . . . . . . . . . . 32		9. References . . . . . . . . . . . . . . . . . . . . . . . . . 32
	9.1. Normative References . . . . . . . . . . . . . . . . . . 32		9.1. Normative References . . . . . . . . . . . . . . . . . . 32
	9.2. Informative References . . . . . . . . . . . . . . . . . 33		9.2. Informative References . . . . . . . . . . . . . . . . . 34
	Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 34		Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 34
	1. Introduction		1. Introduction
	Segment Routing (SR) allows for a flexible definition of end-to-end		Segment Routing (SR) allows for a flexible definition of end-to-end
	paths within IGP topologies by encoding paths as sequences of		paths within IGP topologies by encoding paths as sequences of
	topological sub-paths, called "segments". These segments are		topological sub-paths, called "segments". These segments are
	advertised by the link-state routing protocols (IS-IS and OSPF).		advertised by the link-state routing protocols (IS-IS and OSPF).
	Prefix segments represent an ecmp-aware shortest-path to a prefix (or		Prefix segments represent an ecmp-aware shortest-path to a prefix (or
	a node), as per the state of the IGP topology. Adjacency segments		a node), as per the state of the IGP topology. Adjacency segments
	skipping to change at page 30, line 45 ¶		skipping to change at page 30, line 45 ¶
	We would like to thank Dave Ward, Dan Frost, Stewart Bryant, Pierre		We would like to thank Dave Ward, Dan Frost, Stewart Bryant, Pierre
	Francois and Jesper Skrivers for their contribution to the content of		Francois and Jesper Skrivers for their contribution to the content of
	this document.		this document.
	8. Contributors		8. Contributors
	The following people gave a substantial contribution to the content		The following people gave a substantial contribution to the content
	of this document and should be considered as co-authors:		of this document and should be considered as co-authors:
			Stephane Litkowski
			Orange
			FR
			Email: stephane.litkowski@orange.com
			Jeff Tantsura
			Apstra, Inc.
			Email: jefftant@gmail.com
	Peter Psenak		Peter Psenak
	Cisco Systems Inc.		Cisco Systems Inc.
	US		US
	Email: ppsenak@cisco.com		Email: ppsenak@cisco.com
	Martin Horneffer		Martin Horneffer
	Deutsche Telekom		Deutsche Telekom
	DE		DE
	Email: Martin.Horneffer@telekom.de		Email: Martin.Horneffer@telekom.de
	Wim Henderickx		Wim Henderickx
	Nokia		Nokia
	BE		BE
	skipping to change at page 32, line 24 ¶		skipping to change at page 32, line 33 ¶
	[I-D.ietf-spring-segment-routing]		[I-D.ietf-spring-segment-routing]
	Filsfils, C., Previdi, S., Ginsberg, L., Decraene, B.,		Filsfils, C., Previdi, S., Ginsberg, L., Decraene, B.,
	Litkowski, S., and R. Shakir, "Segment Routing		Litkowski, S., and R. Shakir, "Segment Routing
	Architecture", draft-ietf-spring-segment-routing-15 (work		Architecture", draft-ietf-spring-segment-routing-15 (work
	in progress), January 2018.		in progress), January 2018.
	[I-D.ietf-spring-segment-routing-ldp-interop]		[I-D.ietf-spring-segment-routing-ldp-interop]
	Bashandy, A., Filsfils, C., Previdi, S., Decraene, B., and		Bashandy, A., Filsfils, C., Previdi, S., Decraene, B., and
	S. Litkowski, "Segment Routing interworking with LDP",		S. Litkowski, "Segment Routing interworking with LDP",
	draft-ietf-spring-segment-routing-ldp-interop-14 (work in		draft-ietf-spring-segment-routing-ldp-interop-15 (work in
	progress), July 2018.		progress), September 2018.
	[I-D.ietf-spring-segment-routing-mpls]		[I-D.ietf-spring-segment-routing-mpls]
	Bashandy, A., Filsfils, C., Previdi, S., Decraene, B.,		Bashandy, A., Filsfils, C., Previdi, S., 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-14		data plane", draft-ietf-spring-segment-routing-mpls-15
	(work in progress), June 2018.		(work in progress), October 2018.
	[ISO10589]		[ISO10589]
	International Organization for Standardization,		International Organization for Standardization,
	"Intermediate system to Intermediate system intra-domain		"Intermediate system to Intermediate system intra-domain
	routeing information exchange protocol for use in		routeing information exchange protocol for use in
	conjunction with the protocol for providing the		conjunction with the protocol for providing the
	connectionless-mode Network Service (ISO 8473)", ISO/		connectionless-mode Network Service (ISO 8473)", ISO/
	IEC 10589:2002, Second Edition, Nov 2002.		IEC 10589:2002, Second Edition, Nov 2002.
	[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate		[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
	skipping to change at page 34, line 20 ¶		skipping to change at page 34, line 32 ¶
	[RFC8355] Filsfils, C., Ed., Previdi, S., Ed., Decraene, B., and R.		[RFC8355] Filsfils, C., Ed., Previdi, S., Ed., Decraene, B., and R.
	Shakir, "Resiliency Use Cases in Source Packet Routing in		Shakir, "Resiliency Use Cases in Source Packet Routing in
	Networking (SPRING) Networks", RFC 8355,		Networking (SPRING) Networks", RFC 8355,
	DOI 10.17487/RFC8355, March 2018,		DOI 10.17487/RFC8355, March 2018,
	<https://www.rfc-editor.org/info/rfc8355>.		<https://www.rfc-editor.org/info/rfc8355>.
	Authors' Addresses		Authors' Addresses
	Stefano Previdi (editor)		Stefano Previdi (editor)
	Cisco Systems, Inc.		Huawei
	IT		IT
	Email: stefano@previdi.net		Email: stefano@previdi.net
	Les Ginsberg (editor)		Les Ginsberg (editor)
	Cisco Systems, Inc.		Cisco Systems, Inc.
	IT		IT
	Email: ginsberg@cisco.com		Email: ginsberg@cisco.com
	skipping to change at page 34, line 37 ¶		skipping to change at page 35, line 4 ¶
	IT		IT
	Email: ginsberg@cisco.com		Email: ginsberg@cisco.com
	Clarence Filsfils		Clarence Filsfils
	Cisco Systems, Inc.		Cisco Systems, Inc.
	Brussels		Brussels
	BE		BE
	Email: cfilsfil@cisco.com		Email: cfilsfil@cisco.com
	Ahmed Bashandy		Ahmed Bashandy
			Individual
	Email: abashandy.ietf@gmail.com		Email: abashandy.ietf@gmail.com
	Hannes Gredler		Hannes Gredler
	RtBrick Inc.		RtBrick Inc.
	Email: hannes@rtbrick.com		Email: hannes@rtbrick.com
	Stephane Litkowski
	Orange
	FR
	Email: stephane.litkowski@orange.com
	Bruno Decraene		Bruno Decraene
	Orange		Orange
	FR		FR
	Email: bruno.decraene@orange.com		Email: bruno.decraene@orange.com
	Jeff Tantsura
	Nuage Networks
	Email: jefftant@gmail.com
End of changes. 16 change blocks.
	22 lines changed or deleted		26 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/