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

The information below is for an old version of the document
Document Type Expired Internet-Draft (individual)
Last updated 2019-03-07 (latest revision 2018-09-03)
Stream (None)
Intended RFC status (None)
Formats
Expired & archived
plain text pdf html bibtex
Additional URLs
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state Expired
Telechat date
Responsible AD (None)
Send notices to (None)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft can be found at
https://www.ietf.org/archive/id/draft-ketant-idr-bgp-ls-bgp-only-fabric-01.txt

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.

Authors

Ketan Talaulikar (ketant@cisco.com)
Clarence Filsfils (cfilsfil@cisco.com)
krishnaswamy ananthamurthy (kriswamy@cisco.com)
Shawn Zandi (szandi@linkedin.com)
Gaurav Dawra (gdawra.ietf@gmail.com)
Muhammad Durrani (mdurrani@equinix.com)

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)