Signaling MSD (Maximum SID Depth) using Border Gateway Protocol Link-State
draft-ietf-idr-bgp-ls-segment-routing-msd-08

Document Type Active Internet-Draft (idr WG)
Last updated 2019-09-17
Replaces draft-tantsura-idr-bgp-ls-segment-routing-msd
Stream IETF
Intended RFC status Proposed Standard
Formats plain text xml pdf htmlized bibtex
Reviews
Stream WG state WG Consensus: Waiting for Write-Up
Doc Shepherd Follow-up Underway
Document shepherd Susan Hares
Shepherd write-up Show (last changed 2019-09-11)
IESG IESG state I-D Exists
Consensus Boilerplate Yes
Telechat date
Responsible AD (None)
Send notices to Susan Hares <shares@ndzh.com>
IDR Working Group                                            J. Tantsura
Internet-Draft                                              Apstra, Inc.
Intended status: Standards Track                             U. Chunduri
Expires: March 19, 2020                           Futurewei Technologies
                                                           K. Talaulikar
                                                           Cisco Systems
                                                               G. Mirsky
                                                               ZTE Corp.
                                                        N. Triantafillis
                                                            Apstra, Inc.
                                                      September 16, 2019

 Signaling MSD (Maximum SID Depth) using Border Gateway Protocol Link-
                                 State
              draft-ietf-idr-bgp-ls-segment-routing-msd-08

Abstract

   This document defines a way for a Border Gateway Protocol Link-State
   (BGP-LS) speaker to advertise multiple types of supported Maximum SID
   Depths (MSDs) at node and/or link granularity.

   Such advertisements allow entities (e.g., centralized controllers) to
   determine whether a particular Segment Identifier (SID) stack can be
   supported in a given network.

Status of This Memo

   This Internet-Draft is submitted in full conformance with the
   provisions of BCP 78 and BCP 79.

   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 March 19, 2020.

Tantsura, et al.         Expires March 19, 2020                 [Page 1]
Internet-Draft         Signaling MSD using BGP-LS         September 2019

Copyright Notice

   Copyright (c) 2019 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
   carefully, as they describe your rights and restrictions with respect
   to this document.  Code Components extracted from this document must
   include Simplified BSD License text as described in Section 4.e of
   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
     1.1.  Conventions used in this document . . . . . . . . . . . .   3
       1.1.1.  Terminology . . . . . . . . . . . . . . . . . . . . .   3
       1.1.2.  Requirements Language . . . . . . . . . . . . . . . .   4
   2.  Advertisement of MSD via BGP-LS . . . . . . . . . . . . . . .   4
   3.  Node MSD TLV  . . . . . . . . . . . . . . . . . . . . . . . .   4
   4.  Link MSD TLV  . . . . . . . . . . . . . . . . . . . . . . . .   5
   5.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   6
   6.  Manageability Considerations  . . . . . . . . . . . . . . . .   6
   7.  Security Considerations . . . . . . . . . . . . . . . . . . .   7
   8.  Contributors  . . . . . . . . . . . . . . . . . . . . . . . .   8
   9.  Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .   8
   10. References  . . . . . . . . . . . . . . . . . . . . . . . . .   8
     10.1.  Normative References . . . . . . . . . . . . . . . . . .   8
     10.2.  Informative References . . . . . . . . . . . . . . . . .   8
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .  10

1.  Introduction

   When Segment Routing (SR) [RFC8402] paths are computed by a
   centralized controller, it is critical that the controller learns the
   Maximum SID Depth (MSD) that can be imposed at each node/link on a
   given SR path.  This ensures that the Segment Identifier (SID) stack
   depth of a computed path doesn't exceed the number of SIDs the node
   is capable of imposing.

   [I-D.ietf-pce-segment-routing] defines how to signal MSD in the Path
   Computation Element Protocol (PCEP).  The OSPF and IS-IS extensions
   for signaling of MSD are defined in [RFC8476] and [RFC8491]
   respectively.

Tantsura, et al.         Expires March 19, 2020                 [Page 2]
Internet-Draft         Signaling MSD using BGP-LS         September 2019

   However, if PCEP is not supported/configured on the head-end of a SR
   tunnel or a Binding-SID anchor node, and controller does not
Show full document text