--- 1/draft-ietf-ospf-segment-routing-msd-23.txt 2018-10-17 12:14:00.645229689 -0700 +++ 2/draft-ietf-ospf-segment-routing-msd-24.txt 2018-10-17 12:14:00.669230258 -0700 @@ -1,23 +1,23 @@ OSPF Working Group J. Tantsura Internet-Draft Apstra, Inc. Intended status: Standards Track U. Chunduri -Expires: April 15, 2019 Huawei Technologies +Expires: April 20, 2019 Huawei Technologies S. Aldrin Google, Inc P. Psenak Cisco Systems - October 12, 2018 + October 17, 2018 Signaling MSD (Maximum SID Depth) using OSPF - draft-ietf-ospf-segment-routing-msd-23 + draft-ietf-ospf-segment-routing-msd-24 Abstract This document defines a way for an Open Shortest Path First (OSPF) Router to advertise multiple types of supported Maximum SID(Segment Identifier) Depths (MSDs) at node and/or link granularity. Such advertisements allow entities (e.g., centralized controllers) to determine whether a particular SID stack can be supported in a given network. This document defines only one type of MSD, but defines an encoding that can support other MSD types. Here the term OSPF means @@ -31,21 +31,21 @@ Internet-Drafts are working documents of the Internet Engineering Task Force (IETF). Note that other groups may also distribute working documents as Internet-Drafts. The list of current Internet- Drafts is at https://datatracker.ietf.org/drafts/current/. Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress." - This Internet-Draft will expire on April 15, 2019. + This Internet-Draft will expire on April 20, 2019. Copyright Notice Copyright (c) 2018 IETF Trust and the persons identified as the document authors. All rights reserved. This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (https://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents @@ -180,21 +180,21 @@ Figure 1: Node MSD TLV Type: TBD1 Length: variable (multiple of 2 octets) and represents the total length of value field in octets. Value: consists of one or more pairs of a 1 octet MSD-type and 1 octet MSD-Value. - MSD-Type: one of the values defined in the IGP MSD Types registry + MSD-Type: one of the values defined in the IGP MSD-Types registry defined in [I-D.ietf-isis-segment-routing-msd]. MSD-Value: a number in the range of 0-255. For all MSD-Types, 0 represents lack of the ability to impose MSD stack of any depth; any other value represents that of the node. This value MUST represent the lowest value supported by any link configured for use by the advertising OSPF instance. This TLV is applicable to OSPFv2 and to OSPFv3 and is optional. The scope of the advertisement is specific to the deployment. @@ -238,21 +238,21 @@ For OSPFv3, the Link level MSD-Value is advertised as an optional Sub-TLV of the E-Router-LSA TLV as defined in [RFC8362], and has a type of TBD3. Length: variable and same as defined in Section 2. Value: consists of one or more pairs of a 1 octet MSD-type and 1 octet MSD-Value. - MSD-Type: one of the values defined in the MSD Types registry defined + MSD-Type: one of the values defined in the MSD-Types registry defined in [I-D.ietf-isis-segment-routing-msd]. MSD-Value field contains Link MSD of the router originating the corresponding LSA as specified for OSPFv2 and OSPFv3. Link MSD is a number in the range of 0-255. For all MSD-Types, 0 represents lack of the ability to impose MSD stack of any depth; any other value represents that of the particular link when used as an outgoing interface. If this sub-TLV is advertised multiple times in the same OSPFv2