BGP Extensions for IDs Allocation
draft-wu-idr-bgp-segment-allocation-ext-02

Document Type Active Internet-Draft (candidate for idr WG)
Last updated 2019-04-18 (latest revision 2019-04-17)
Stream IETF
Intended RFC status (None)
Formats plain text pdf html bibtex
Stream WG state Call For Adoption By WG Issued
Document shepherd No shepherd assigned
IESG IESG state I-D Exists
Consensus Boilerplate Unknown
Telechat date
Responsible AD (None)
Send notices to (None)
IDR Working Group                                                  N. Wu
Internet-Draft                                                 Z. Zhuang
Intended status: Standards Track                                 H. Chen
Expires: October 19, 2019                                         Huawei
                                                          April 17, 2019

                   BGP Extensions for IDs Allocation
               draft-wu-idr-bgp-segment-allocation-ext-02

Abstract

   This document describes extensions to the BGP-LS for IDs allocation.
   The IDs are SIDs for segment routing and indirection IDs for flow
   redirect.  They are distributed to their domains if needed.

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 [RFC2119].

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 October 19, 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

Wu, et al.              Expires October 19, 2019                [Page 1]
Internet-Draft           BGP for IDs Allocation               April 2019

   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.  Terminology . . . . . . . . . . . . . . . . . . . . . . . . .   2
   3.  Protocol Extensions . . . . . . . . . . . . . . . . . . . . .   3
     3.1.  Node NLRI for IDs Allocation  . . . . . . . . . . . . . .   3
     3.2.  Link NLRI for IDs Allocation  . . . . . . . . . . . . . .   4
     3.3.  Prefix NLRI for IDs Allocation  . . . . . . . . . . . . .   5
   4.  Application Examples  . . . . . . . . . . . . . . . . . . . .   6
     4.1.  Allocating IDs for DC BGP Network . . . . . . . . . . . .   6
       4.1.1.  Node-SID Distribution via Prefix NLRI . . . . . . . .   7
       4.1.2.  Adj-SID Distribution via Link NLRI  . . . . . . . . .   8
       4.1.3.  IID Distribution via Node NLRI  . . . . . . . . . . .   9
     4.2.  Allocating IDs for IGP Network  . . . . . . . . . . . . .   9
   5.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .  10
   6.  Security Considerations . . . . . . . . . . . . . . . . . . .  10
   7.  Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .  10
   8.  References  . . . . . . . . . . . . . . . . . . . . . . . . .  10
     8.1.  Normative References  . . . . . . . . . . . . . . . . . .  10
     8.2.  Informative References  . . . . . . . . . . . . . . . . .  11
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .  12

1.  Introduction

   In a network with a central controller, the controller has the link
   state information of the network, including traffic engineering
   information.  In addition, the controller allocates and manages the
   resources of the network in general.  It is natural and beneficial
   for the controller to allocate and manage IDs as a kind of network
   resources.

   This document proposes extensions to the BGP-LS as a controller for
   allocating Segment Identifers (SIDs) for segment routing (SR) and
   indirection identifiers (IIDs) for flow redirect.  If needed, some
   IDs will be distributed into their network domains.

2.  Terminology

   The following terminology is used in this document.

   SR:  Segment Routing.

Wu, et al.              Expires October 19, 2019                [Page 2]
Internet-Draft           BGP for IDs Allocation               April 2019

   SID:  Segment Identifier.

   IID:  Indirection Identifier.

   SR-Path:  Segment Routing Path.
Show full document text