draft-ietf-isis-segment-routing-msd-12.txt   draft-ietf-isis-segment-routing-msd-13.txt 
IS-IS Working Group J. Tantsura IS-IS Working Group J. Tantsura
Internet-Draft Nuage Networks Internet-Draft Nuage Networks
Intended status: Standards Track U. Chunduri Intended status: Standards Track U. Chunduri
Expires: November 17, 2018 Huawei Technologies Expires: January 25, 2019 Huawei Technologies
S. Aldrin S. Aldrin
Google, Inc Google, Inc
L. Ginsberg L. Ginsberg
Cisco Systems Cisco Systems
May 16, 2018 July 24, 2018
Signaling MSD (Maximum SID Depth) using IS-IS Signaling MSD (Maximum SID Depth) using IS-IS
draft-ietf-isis-segment-routing-msd-12 draft-ietf-isis-segment-routing-msd-13
Abstract Abstract
This document defines a way for an IS-IS Router to advertise multiple This document defines a way for an IS-IS Router to advertise multiple
types of supported Maximum SID Depths (MSDs) at node and/or link types of supported Maximum SID Depths (MSDs) at node and/or link
granularity. Such advertisements allow entities (e.g., centralized granularity. Such advertisements allow entities (e.g., centralized
controllers) to determine whether a particular SID stack can be controllers) to determine whether a particular SID stack can be
supported in a given network. This document only defines one type of supported in a given network. This document only defines one type of
MSD maximum label imposition, but defines an encoding that can MSD maximum label imposition, but defines an encoding that can
support other MSD types. support other MSD types.
skipping to change at page 1, line 41 skipping to change at page 1, line 41
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 November 17, 2018. This Internet-Draft will expire on January 25, 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 4, line 37 skipping to change at page 4, line 37
Figure 1: Node MSD Sub-TLV Figure 1: Node MSD Sub-TLV
Type: 23 (allocated by IANA via the early assignment process) Type: 23 (allocated by IANA via the early assignment process)
Length: variable (minimum of 2, multiple of 2 octets) and represents Length: variable (minimum of 2, multiple of 2 octets) and represents
the total length of value field. the total length of value field.
Value: field consists of one or more pairs of a 1 octet MSD-Type and Value: field consists of one or more pairs of a 1 octet MSD-Type and
1 octet MSD-Value. 1 octet MSD-Value.
MSD-Type is one of the values defined in the MSD Types registry MSD-Type is one of the values defined in the IGP MSD Types registry
created by the IANA Section of this document. created by the IANA Section of this document.
MSD-Value is a number in the range of 0-255. For all MSD-Types, 0 MSD-Value is a number in the range of 0-255. For all MSD-Types, 0
represents lack of the ability to support SID stack of any depth; any represents lack of the ability to support SID stack of any depth; any
other value represents that of the node. This value MUST represent other value represents that of the node. This value MUST represent
the lowest value supported by any link configured for use by the the lowest value supported by any link configured for use by the
advertising IS-IS instance. advertising IS-IS instance.
This sub-TLV is optional. The scope of the advertisement is specific This sub-TLV is optional. The scope of the advertisement is specific
to the deployment. to the deployment.
skipping to change at page 7, line 26 skipping to change at page 7, line 26
TLV 22 23 25 141 222 223 TLV 22 23 25 141 222 223
--- -------------------- --- --------------------
y y y y y y y y y y y y
Figure 5: TLVs where LINK MSD Sub-TLV can be present Figure 5: TLVs where LINK MSD Sub-TLV can be present
This document requests creation of an IANA managed registry under a This document requests creation of an IANA managed registry under a
new category of "Interior Gateway Protocol (IGP) Parameters" IANA new category of "Interior Gateway Protocol (IGP) Parameters" IANA
registries to identify MSD types as proposed in Section 2 and registries to identify MSD types as proposed in Section 2 and
Section 3. The registration procedure is "Expert Review" as defined Section 3. The registration procedure is "Expert Review" as defined
in [RFC8126]. Suggested registry name is "MSD types". Types are an in [RFC8126]. Suggested registry name is "IGP MSD Types". Types are
unsigned 8 bit number. The following values are defined by this an unsigned 8 bit number. The following values are defined by this
document document
Value Name Reference Value Name Reference
----- --------------------- ------------- ----- --------------------- -------------
0 Reserved This document 0 Reserved This document
1 Base MPLS Imposition MSD This document 1 Base MPLS Imposition MSD This document
2-250 Unassigned This document 2-250 Unassigned This document
251-254 Experimental This document 251-254 Experimental This document
255 Reserved This document 255 Reserved This document
skipping to change at page 9, line 8 skipping to change at page 9, line 8
[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 and Litkowski, "Signaling Entropy Label Capability and
Readable Label-stack Depth Using IS-IS", draft-ietf-isis- Readable Label-stack Depth Using IS-IS", draft-ietf-isis-
mpls-elc-03 (work in progress), January 2018. mpls-elc-03 (work in progress), January 2018.
[I-D.ietf-pce-segment-routing] [I-D.ietf-pce-segment-routing]
Sivabalan, S., Filsfils, C., Tantsura, J., Henderickx, W., Sivabalan, S., Filsfils, C., Tantsura, J., Henderickx, W.,
and J. Hardwick, "PCEP Extensions for Segment Routing", and J. Hardwick, "PCEP Extensions for Segment Routing",
draft-ietf-pce-segment-routing-11 (work in progress), draft-ietf-pce-segment-routing-12 (work in progress), June
November 2017. 2018.
[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-editor.org/info/rfc7752>. <https://www.rfc-editor.org/info/rfc7752>.
[RFC8126] Cotton, M., Leiba, B., and T. Narten, "Guidelines for [RFC8126] Cotton, M., Leiba, B., and T. Narten, "Guidelines for
Writing an IANA Considerations Section in RFCs", BCP 26, Writing an IANA Considerations Section in RFCs", BCP 26,
RFC 8126, DOI 10.17487/RFC8126, June 2017, RFC 8126, DOI 10.17487/RFC8126, June 2017,
 End of changes. 7 change blocks. 
9 lines changed or deleted 9 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/