< draft-ietf-isis-segment-routing-msd-03.txt		draft-ietf-isis-segment-routing-msd-04.txt >
	IS-IS Working Group J. Tantsura		IS-IS Working Group J. Tantsura
	Internet-Draft Individual		Internet-Draft Individual
	Intended status: Standards Track U. Chunduri		Intended status: Standards Track U. Chunduri
	Expires: September 29, 2017 Huawei Technologies		Expires: December 6, 2017 Huawei Technologies
	S. Aldrin		S. Aldrin
	Google, Inc		Google, Inc
	L. Ginsberg		L. Ginsberg
	Cisco Systems		Cisco Systems
	March 28, 2017		June 04, 2017
	Signaling MSD (Maximum SID Depth) using IS-IS		Signaling MSD (Maximum SID Depth) using IS-IS
	draft-ietf-isis-segment-routing-msd-03		draft-ietf-isis-segment-routing-msd-04
	Abstract		Abstract
	This document proposes a way to signal Maximum SID Depth (MSD)		This document proposes a way to signal Maximum SID Depth (MSD)
	supported by a node at node and/or link granularity by an IS-IS		supported by a node at node and/or link granularity by an IS-IS
	Router. In a Segment Routing (SR) enabled network a centralized		Router. In a Segment Routing (SR) enabled network a centralized
	controller that programs SR tunnels needs to know the MSD supported		controller that programs SR tunnels needs to know the MSD supported
	by the head-end at node and/or link granularity to push the SID stack		by the head-end at node and/or link granularity to push the SID stack
	of an appropriate depth. MSD is relevant to the head-end of a SR		of an appropriate depth. MSD is relevant to the head-end of a SR
	tunnel or Binding-SID anchor node where Binding-SID expansions might		tunnel or Binding-SID anchor node where Binding-SID expansions might
	skipping to change at page 1, line 42 ¶		skipping to change at page 1, line 42 ¶
	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 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 September 29, 2017.		This Internet-Draft will expire on December 6, 2017.
	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		(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
	skipping to change at page 3, line 19 ¶		skipping to change at page 3, line 19 ¶
	[I-D.ietf-isis-mpls-elc] defines Readable Label Depth Capability		[I-D.ietf-isis-mpls-elc] defines Readable Label Depth Capability
	(RLDC) that is used by a head-end to insert Entropy Label (EL) at		(RLDC) that is used by a head-end to insert Entropy Label (EL) at
	appropriate depth, so it could be read by transit nodes. MSD in		appropriate depth, so it could be read by transit nodes. MSD in
	contrary signals ability to push SID's stack of a particular depth.		contrary signals ability to push SID's stack of a particular depth.
	MSD of type 1 (IANA Registry), called Base MSD, is used to signal the		MSD of type 1 (IANA Registry), called Base MSD, is used to signal the
	total number of SIDs a node is capable of imposing, to be used by a		total number of SIDs a node is capable of imposing, to be used by a
	path computation element/controller. In case, there are additional		path computation element/controller. In case, there are additional
	labels (e.g. service) that are to be pushed to the stack - this would		labels (e.g. service) that are to be pushed to the stack - this would
	be signaled with an another MSD type (TBD), MSD SHOULD be adjusted to		be signaled with an another MSD type (TBD), no adjustment to the Base
	reflect that. In the future, new MSD types could be defined to		MSD should be made. In the future, new MSD types could be defined to
	signal additional capabilities: entropy labels, labels that can be		signal additional capabilities: entropy labels, labels that can be
	pushed thru recirculation, or another dataplane e.g IPv6.		pushed thru recirculation, or another dataplane e.g IPv6.
	1.1. Conventions used in this document		1.1. Conventions used in this document
	1.1.1. Terminology		1.1.1. Terminology
	BGP-LS: Distribution of Link-State and TE Information using Border		BGP-LS: Distribution of Link-State and TE Information using Border
	Gateway Protocol		Gateway Protocol
	skipping to change at page 6, line 5 ¶		skipping to change at page 6, line 5 ¶
	Also for link MSD, we request IANA to allocate new sub-TLV codes as		Also for link MSD, we request IANA to allocate new sub-TLV codes as
	defined in Section 4 from Sub-TLVs for TLVs 22, 23, 141, 222 and 223		defined in Section 4 from Sub-TLVs for TLVs 22, 23, 141, 222 and 223
	registry.		registry.
	Type: 15 (suggested - to be assigned by IANA)		Type: 15 (suggested - to be assigned by IANA)
	Description: Link MSD		Description: Link MSD
	Per TLV information where LINK MSD sub-TLV can be part of:		Per TLV information where LINK MSD sub-TLV can be part of:
	TLV 22 23 141 222 223		TLV 22 23 25 141 222 223
	----------------------		--------------------
	y y y y y		y y y y y y
	Figure 3: TLVs where LINK MSD Sub-TLV can be present		Figure 3: TLVs where LINK MSD Sub-TLV can be present
	This document requests the creation of a new IANA managed registry to		This document requests the creation of a new IANA managed registry to
	identify MSD types as proposed in Section 3, Section 4. The		identify MSD types as proposed in Section 3, Section 4. The
	registration procedure is "Expert Review" as defined in [RFC5226].		registration procedure is "Expert Review" as defined in [RFC5226].
	Suggested registry name is "MSD Sub-types". Types are an unsigned 8		Suggested registry name is "MSD Sub-types". Types are an unsigned 8
	bit number. The following values are defined by this document		bit number. The following values are defined by this document
	Value Name Reference		Value Name Reference
	skipping to change at page 7, line 29 ¶		skipping to change at page 7, line 29 ¶
	10.2. Informative References		10.2. Informative References
	[I-D.ietf-isis-mpls-elc]		[I-D.ietf-isis-mpls-elc]
	Xu, X., Kini, S., Sivabalan, S., Filsfils, C., and S.		Xu, X., Kini, S., Sivabalan, S., Filsfils, C., and S.
	Litkowski, "Signaling Entropy Label Capability Using IS-		Litkowski, "Signaling Entropy Label Capability Using IS-
	IS", draft-ietf-isis-mpls-elc-02 (work in progress),		IS", draft-ietf-isis-mpls-elc-02 (work in progress),
	October 2016.		October 2016.
	[I-D.ietf-pce-segment-routing]		[I-D.ietf-pce-segment-routing]
	Sivabalan, S., Medved, J., Filsfils, C., Crabbe, E.,		Sivabalan, S., Filsfils, C., Tantsura, J., Henderickx, W.,
	Raszuk, R., Lopez, V., Tantsura, J., Henderickx, W., and		and J. Hardwick, "PCEP Extensions for Segment Routing",
	J. Hardwick, "PCEP Extensions for Segment Routing", draft-		draft-ietf-pce-segment-routing-09 (work in progress),
	ietf-pce-segment-routing-08 (work in progress), October		April 2017.
	2016.
	[I-D.tantsura-idr-bgp-ls-segment-routing-msd]		[I-D.tantsura-idr-bgp-ls-segment-routing-msd]
	Tantsura, J., Chunduri, U., Mirsky, G., and S. Sivabalan,		Tantsura, J., Chunduri, U., Mirsky, G., and S. Sivabalan,
	"Signaling Maximum SID Depth using Border Gateway Protocol		"Signaling Maximum SID Depth using Border Gateway Protocol
	Link-State", draft-tantsura-idr-bgp-ls-segment-routing-		Link-State", draft-tantsura-idr-bgp-ls-segment-routing-
	msd-03 (work in progress), March 2017.		msd-04 (work in progress), March 2017.
	[RFC1195] Callon, R., "Use of OSI IS-IS for routing in TCP/IP and		[RFC1195] Callon, R., "Use of OSI IS-IS for routing in TCP/IP and
	dual environments", RFC 1195, DOI 10.17487/RFC1195,		dual environments", RFC 1195, DOI 10.17487/RFC1195,
	December 1990, <http://www.rfc-editor.org/info/rfc1195>.		December 1990, <http://www.rfc-editor.org/info/rfc1195>.
	[RFC5120] Przygienda, T., Shen, N., and N. Sheth, "M-ISIS: Multi		[RFC5120] Przygienda, T., Shen, N., and N. Sheth, "M-ISIS: Multi
	Topology (MT) Routing in Intermediate System to		Topology (MT) Routing in Intermediate System to
	Intermediate Systems (IS-ISs)", RFC 5120,		Intermediate Systems (IS-ISs)", RFC 5120,
	DOI 10.17487/RFC5120, February 2008,		DOI 10.17487/RFC5120, February 2008,
	<http://www.rfc-editor.org/info/rfc5120>.		<http://www.rfc-editor.org/info/rfc5120>.
End of changes. 8 change blocks.
	15 lines changed or deleted		14 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/