Signalling RLD using BGP-LS
draft-vandevelde-idr-bgp-ls-segment-routing-rld-01

Document Type Active Internet-Draft (individual)
Last updated 2017-03-03
Stream (None)
Intended RFC status (None)
Formats plain text pdf html bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state I-D Exists
Telechat date
Responsible AD (None)
Send notices to (None)
IDR Working Group                                   G. Van de Velde, Ed.
Internet-Draft                                             W. Henderickx
Intended status: Standards Track                                M. Bocci
Expires: September 4, 2017                                         Nokia
                                                           March 3, 2017

                      Signalling RLD using BGP-LS
           draft-vandevelde-idr-bgp-ls-segment-routing-rld-01

Abstract

   This document defines the attribute to use for BGP-LS to expose a
   node RLD "Readable Label Depth" to a centralised controller (PCE/
   SDN).

Requirements Language

   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
   "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
   document are to be interpreted as described in RFC 2119 [1].

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 http://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 September 4, 2017.

Copyright Notice

   Copyright (c) 2017 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
   (http://trustee.ietf.org/license-info) in effect on the date of
   publication of this document.  Please review these documents

Van de Velde, et al.    Expires September 4, 2017               [Page 1]
Internet-Draft         Signalling RLD using BGP-LS            March 2017

   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
   2.  Conventions used in this document . . . . . . . . . . . . . .   2
     2.1.  Terminology . . . . . . . . . . . . . . . . . . . . . . .   2
   3.  Problem Statement . . . . . . . . . . . . . . . . . . . . . .   3
   4.  RLD support by a node . . . . . . . . . . . . . . . . . . . .   3
   5.  Security Considerations . . . . . . . . . . . . . . . . . . .   4
   6.  Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .   4
   7.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   4
   8.  References  . . . . . . . . . . . . . . . . . . . . . . . . .   4
     8.1.  Normative References  . . . . . . . . . . . . . . . . . .   4
     8.2.  Informative References  . . . . . . . . . . . . . . . . .   4
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .   4

1.  Introduction

   When Segment Routing tunnels are computed by a centralised
   controller, it is beneficial that the controller knows the RLD
   "Readable Label Depth" of each node the computed tunnel traverses.

   RLD awareness of each node will allow the network SDN controller to
   influence the path used for each tunnel.  The SDN controller may for
   example only create tunnels with a label stack smaller or equal as
   the RLD of each node on the path.  This will allow the network to
   behave accordingly (e.g.  make use of Entropy Labels to improve ECMP)
   upon the imposed Segment Routing labels on each packet.

   This document describes how to use BGP-LS to expose the RLD of a
   node.

2.  Conventions used in this document

2.1.  Terminology

   BGP-LS: Distribution of Link-State and TE Information using Border
   Gateway Protocol

   RLD: Readable Label Depth

   PCC: Path Computation Client

Van de Velde, et al.    Expires September 4, 2017               [Page 2]
Internet-Draft         Signalling RLD using BGP-LS            March 2017

   PCE: Path Computation Element

   PCEP: Path Computation Element Protocol

   SID: Segment Identifier

   SR: Segment routing

3.  Problem Statement

   In existing technology both ISIS [4] and OSPF [3] have proposed
Show full document text