Skip to main content

BGP Classful Transport Planes
draft-kaliraj-idr-bgp-classful-transport-planes-17

Document Type Replaced Internet-Draft (idr WG)
Expired & archived
Authors Kaliraj Vairavakkalai , Natrajan Venkataraman , Balaji Rajagopalan , Gyan Mishra , Mazen Khaddam , Xiaohu Xu , Rafal Jan Szarecki , Deepak J Gowda , Chaitanya Yadlapalli , Israel Means
Last updated 2022-07-28 (Latest revision 2022-06-30)
Replaces draft-kaliraj-idr-bgp-transport-vpn
Replaced by draft-ietf-idr-bgp-classful-transport-planes
RFC stream Internet Engineering Task Force (IETF)
Intended RFC status (None)
Formats
Stream WG state Adopted by a WG
Document shepherd Susan Hares
IESG IESG state Replaced by draft-ietf-idr-bgp-classful-transport-planes
Consensus boilerplate Unknown
Telechat date (None)
Responsible AD (None)
Send notices to shares@ndzh.com

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 "Intent Driven Service Mapping" to express association of overlay routes with underlay routes satisfying a certain SLA using BGP. The document describes a framework for classifying underlay routes into transport classes and mapping service routes to specific transport class. The "Transport class" construct maps to a desired SLA and can be used to realize the "Topology Slice" in 5G Network slicing architecture. This document specifies BGP protocol procedures that enable dissemination of such service mapping information that may span multiple cooperating administrative domains. These domains may be administetered by the same provider or by closely co-ordinating provider networks. A new BGP transport layer address family (SAFI 76) is defined for this purpose that uses RFC-4364 technology and follows RFC-8277 NLRI encoding. This new address family is called "BGP Classful Transport", aka BGP CT. BGP CT makes it possible to advertise multiple tunnels to the same destination address, thus avoiding need of multiple loopbacks on the egress node. It carries transport prefixes across tunnel domain boundaries (e.g. in Inter-AS Option-C networks), which is parallel to BGP LU (SAFI 4) . It disseminates "Transport class" information for the transport prefixes across the participating domains, which is not possible with BGP LU. This makes the end-to-end network a "Transport Class" aware tunneled network. Though BGP CT family is used only in the option-C inter-AS neworks, the Service Mapping procedures described in this document apply in the same manner to Intra-AS service end points as well as Inter-AS option-A, option-B and option-C variations.

Authors

Kaliraj Vairavakkalai
Natrajan Venkataraman
Balaji Rajagopalan
Gyan Mishra
Mazen Khaddam
Xiaohu Xu
Rafal Jan Szarecki
Deepak J Gowda
Chaitanya Yadlapalli
Israel Means

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