| < draft-ietf-idr-bgp-ls-segment-routing-msd-07.txt | draft-ietf-idr-bgp-ls-segment-routing-msd-08.txt > | |||
|---|---|---|---|---|
| IDR Working Group J. Tantsura | IDR Working Group J. Tantsura | |||
| Internet-Draft Apstra, Inc. | Internet-Draft Apstra, Inc. | |||
| Intended status: Standards Track U. Chunduri | Intended status: Standards Track U. Chunduri | |||
| Expires: March 14, 2020 Futurewei Technologies | Expires: March 19, 2020 Futurewei Technologies | |||
| K. Talaulikar | K. Talaulikar | |||
| Cisco Systems | Cisco Systems | |||
| G. Mirsky | G. Mirsky | |||
| ZTE Corp. | ZTE Corp. | |||
| N. Triantafillis | N. Triantafillis | |||
| Apstra, Inc. | Apstra, Inc. | |||
| September 11, 2019 | September 16, 2019 | |||
| Signaling MSD (Maximum SID Depth) using Border Gateway Protocol Link- | Signaling MSD (Maximum SID Depth) using Border Gateway Protocol Link- | |||
| State | State | |||
| draft-ietf-idr-bgp-ls-segment-routing-msd-07 | draft-ietf-idr-bgp-ls-segment-routing-msd-08 | |||
| Abstract | Abstract | |||
| This document defines a way for a Border Gateway Protocol Link-State | This document defines a way for a Border Gateway Protocol Link-State | |||
| (BGP-LS) speaker to advertise multiple types of supported Maximum SID | (BGP-LS) speaker to advertise multiple types of supported Maximum SID | |||
| Depths (MSDs) at node and/or link granularity. | Depths (MSDs) at node and/or link granularity. | |||
| Such advertisements allow entities (e.g., centralized controllers) to | Such advertisements allow entities (e.g., centralized controllers) to | |||
| determine whether a particular Segment Identifier (SID) stack can be | determine whether a particular Segment Identifier (SID) stack can be | |||
| supported in a given network. | supported in a given network. | |||
| skipping to change at page 1, line 44 ¶ | skipping to change at page 1, line 44 ¶ | |||
| 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 March 14, 2020. | This Internet-Draft will expire on March 19, 2020. | |||
| Copyright Notice | Copyright Notice | |||
| Copyright (c) 2019 IETF Trust and the persons identified as the | Copyright (c) 2019 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 5 ¶ | skipping to change at page 4, line 5 ¶ | |||
| SR: Segment routing | SR: Segment routing | |||
| Label Imposition: Imposition is the act of modifying and/or adding | Label Imposition: Imposition is the act of modifying and/or adding | |||
| labels to the outgoing label stack associated with a packet. This | labels to the outgoing label stack associated with a packet. This | |||
| includes: | includes: | |||
| o replacing the label at the top of the label stack with a new | o replacing the label at the top of the label stack with a new | |||
| label. | label. | |||
| o pushing one or more new labels onto the label stack The number of | o pushing one or more new labels onto the label stack. The number | |||
| labels imposed is then the sum of the number of labels that are | of labels imposed is then the sum of the number of labels that are | |||
| replaced and the number of labels that are pushed. See [RFC3031] | replaced and the number of labels that are pushed. See [RFC3031] | |||
| for further details. | for further details. | |||
| 1.1.2. Requirements Language | 1.1.2. Requirements Language | |||
| The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", | The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", | |||
| "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and | "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and | |||
| "OPTIONAL" in this document are to be interpreted as described in BCP | "OPTIONAL" in this document are to be interpreted as described in BCP | |||
| 14 [RFC2119] [RFC8174] when, and only when, they appear in all | 14 [RFC2119] [RFC8174] when, and only when, they appear in all | |||
| capitals, as shown here . | capitals, as shown here . | |||
| End of changes. 5 change blocks. | ||||
| 6 lines changed or deleted | 6 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/ | ||||