BGP-LS Extend for Inter-AS Topology Retrieval
draft-wang-idr-bgpls-inter-as-topology-ext-01

The information below is for an old version of the document
Document Type Active Internet-Draft (individual)
Author Aijun Wang 
Last updated 2018-06-28
Replaced by draft-ietf-idr-bgpls-inter-as-topology-ext
Stream (None)
Intended RFC status (None)
Formats pdf htmlized (tools) htmlized 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                                                A. Wang
Internet-Draft                                             China Telecom
Intended status: Standards Track                           June 28, 2018
Expires: December 30, 2018

             BGP-LS Extend for Inter-AS Topology Retrieval
             draft-wang-idr-bgpls-inter-as-topology-ext-01

Abstract

   This document describes the process to build BGP-LS key parameters in
   Native IP multi-domain scenario and defines some new inter-AS TE
   related TLVs for BGP-LS to let SDN controller retrieve the network
   topology automatically under various environments.

   Such process and extension can expand the usage of BGP-LS protocol to
   multi- domain, enable the network operator to collect the connection
   relationship between different AS domains and then calculate the
   overall network topology automatically based on the information
   provided by BGP-LS protocol.

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 December 30, 2018.

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

Wang                    Expires December 30, 2018               [Page 1]
Internet-Draft             BGP-LS-Inter-As-Ext                 June 2018

   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 . . . . . . . . . . . . . .   3
   3.  Inter-AS Domain Scenarios.  . . . . . . . . . . . . . . . . .   3
     3.1.  IS-IS/OSPF Inter-AS Native IP Scenario  . . . . . . . . .   3
     3.2.  IS-IS/OSPF Inter-AS TE Scenario . . . . . . . . . . . . .   4
   4.  Inter-AS TE related TLVs  . . . . . . . . . . . . . . . . . .   5
   5.  Topology Reconstruction.  . . . . . . . . . . . . . . . . . .   5
   6.  Security Considerations . . . . . . . . . . . . . . . . . . .   5
   7.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   5
   8.  Acknowledgement . . . . . . . . . . . . . . . . . . . . . . .   5
   9.  Normative References  . . . . . . . . . . . . . . . . . . . .   6
   Author's Address  . . . . . . . . . . . . . . . . . . . . . . . .   7

1.  Introduction

   BGP-LS [RFC7752] describes the methodology that using BGP protocol to
   transfer the Link-State information.  Such method can enable SDN
   controller to collect the underlay network topology automatically,
   but normally it can only get the information within one IGP domain.
   If the operator has more than one IGP domain, and these domains
   interconnect with each other, there is no general TLV within current
   BGP- LS to transfer the interconnect information.

   Draft [I-D.ietf-idr-bgpls-segment-routing-epe] defines some
   extensions for exporting BGP peering node topology information
   (including its peers, interfaces and peering ASs) in a way that is
   exploitable in order to compute efficient BGP Peering Engineering
   policies and strategies.  Such information can also be used to
   calculate the interconnection topology among different IGP domains,
   but it requires the border routers to run BGP-LS protocol to collect
   this information and report them to the PCE/SDN controller, which
   restricts the deployment flexibility of BGP-LS protocol.

   This draft analysizes the situations that the PCE/SDN controller
   needs to get about the inter-connected information between different
   AS domains, defines new TLVs to extend the BGP-LS protocol to
   transfer the key information related to the interconnect TE topology.
   After that, the SDN controller can then deduce the multi-domain
   topology automatically based on the information from BGP-LS protocol.

Wang                    Expires December 30, 2018               [Page 2]
Show full document text