BGP Transport VPNs
draft-kaliraj-idr-bgp-transport-vpn-00

Document Type Replaced Internet-Draft (individual)
Last updated 2020-03-07
Replaced by draft-kaliraj-idr-bgp-classful-transport-planes
Stream (None)
Intended RFC status (None)
Formats
Expired & archived
pdf htmlized (tools) htmlized bibtex
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
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-kaliraj-idr-bgp-transport-vpn-00.txt

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 (kaliraj@juniper.net)
Natrajan Venkataraman (natv@juniper.net)
Balaji Rajagopalan (balajir@juniper.net)

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