BGP Link-State Extensions for BGP-only Fabric
draft-ketant-idr-bgp-ls-bgp-only-fabric-01

Document Type Active Internet-Draft (individual)
Last updated 2018-09-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)
Inter-Domain Routing                                       K. Talaulikar
Internet-Draft                                               C. Filsfils
Intended status: Standards Track                                K. Swamy
Expires: March 7, 2019                                     Cisco Systems
                                                                S. Zandi
                                                                G. Dawra
                                                                LinkedIn
                                                              M. Durrani
                                                                 Equinix
                                                       September 3, 2018

             BGP Link-State Extensions for BGP-only Fabric
               draft-ketant-idr-bgp-ls-bgp-only-fabric-01

Abstract

   BGP is used as the only routing protocol in some networks today.  In
   such networks, it is useful to get a detailed view of the nodes and
   underlying links in the topology along with their attributes similar
   to one available when using link state routing protocols.  Such a
   view of a BGP-only fabric enables use cases like traffic engineering
   and forwarding of services along paths other than the BGP best path
   selection.

   This document defines extensions to the BGP Link-state address-family
   (BGP-LS) and the procedures for advertisement of the topology in a
   BGP-only network.  It also describes a specific use-case for traffic
   engineering based on Segment Routing.

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

Talaulikar, et al.        Expires March 7, 2019                 [Page 1]
Internet-Draft         BGP LS for BGP-only Fabric         September 2018

   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 7, 2019.

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
   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  . . . . . . . . . . . . . . . . . . . . . . . .   3
   2.  Topology Collection Mechanism . . . . . . . . . . . . . . . .   3
   3.  Advertising BGP-only Network Topology . . . . . . . . . . . .   5
     3.1.  Node Advertisements . . . . . . . . . . . . . . . . . . .   5
     3.2.  Link Advertisements . . . . . . . . . . . . . . . . . . .   6
     3.3.  Prefix Advertisements . . . . . . . . . . . . . . . . . .   8
     3.4.  TE Policy Advertisements  . . . . . . . . . . . . . . . .   9
   4.  Procedures  . . . . . . . . . . . . . . . . . . . . . . . . .  10
     4.1.  Advertisement of Router's Node Attributes . . . . . . . .  10
     4.2.  Advertisement of Router's Local Links Attributes  . . . .  11
     4.3.  Advertisement of Router's Prefix Attributes . . . . . . .  13
     4.4.  Advertisement of Router's TE Policy Attributes  . . . . .  14
   5.  Usage of BGP Topology . . . . . . . . . . . . . . . . . . . .  14
     5.1.  Topology View for Monitoring  . . . . . . . . . . . . . .  15
     5.2.  SR-TE in BGP Networks . . . . . . . . . . . . . . . . . .  15
   6.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .  17
   7.  Manageability Considerations  . . . . . . . . . . . . . . . .  17
     7.1.  Operational Considerations  . . . . . . . . . . . . . . .  17
       7.1.1.  Operations  . . . . . . . . . . . . . . . . . . . . .  17
   8.  Security Considerations . . . . . . . . . . . . . . . . . . .  17
   9.  Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .  17
   10. References  . . . . . . . . . . . . . . . . . . . . . . . . .  17
     10.1.  Normative References . . . . . . . . . . . . . . . . . .  17
Show full document text