BGP Transport VPNs
draft-kaliraj-idr-bgp-transport-vpn-00
Document | Type |
Replaced Internet-Draft
(individual)
Expired & archived
|
|
---|---|---|---|
Authors | Kaliraj Vairavakkalai , Natrajan Venkataraman , Balaji Rajagopalan | ||
Last updated | 2020-03-07 | ||
Replaced by | draft-kaliraj-idr-bgp-classful-transport-planes | ||
RFC stream | (None) | ||
Intended RFC status | (None) | ||
Formats | |||
Stream | Stream state | (No stream defined) | |
Consensus boilerplate | Unknown | ||
RFC Editor Note | (None) | ||
IESG | IESG state | Replaced by draft-kaliraj-idr-bgp-classful-transport-planes | |
Telechat date | (None) | ||
Responsible AD | (None) | ||
Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
Abstract
This document specifies a mechanism, referred to as "service mapping", to express association of overlay routes with underlay routes using BGP. The document describes a framework for service mapping, and specifies BGP protocol procedures that enable dissimination of the service mapping information that may span across administrative domains. It makes it possible to advertise multiple tunnels to the same destination. A new BGP transport address family is defined for this purpose that uses BGP-VPN [RFC4364] technology and follows MPLS-BGP [RFC8277] NLRI encoding. This new address family is called "Transport-VPN".
Authors
Kaliraj Vairavakkalai
Natrajan Venkataraman
Balaji Rajagopalan
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)