I-D Action: draft-kaliraj-idr-bgp-classful-transport-planes-14.txt

internet-drafts@ietf.org Wed, 27 April 2022 15:22 UTC

MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: internet-drafts@ietf.org
To: <i-d-announce@ietf.org>
Cc: idr@ietf.org
Subject: I-D Action: draft-kaliraj-idr-bgp-classful-transport-planes-14.txt
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: idr@ietf.org
Message-ID: <165107293109.1514.2550112572370499087@ietfa.amsl.com>
Date: Wed, 27 Apr 2022 08:22:11 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/i-d-announce/o-9WH1myoYVxTHeibWYyGhq3MMs>

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Inter-Domain Routing WG of the IETF.

        Title           : BGP Classful Transport Planes
        Authors         : Kaliraj Vairavakkalai
                          Natrajan Venkataraman
                          Balaji Rajagopalan
                          Gyan Mishra
                          Mazen Khaddam
                          Xiaohu Xu
                          Rafal Jan Szarecki
                          Deepak J Gowda
                          Chaitanya Yadlapalli
	Filename        : draft-kaliraj-idr-bgp-classful-transport-planes-14.txt
	Pages           : 32
	Date            : 2022-04-26

Abstract:
   This document specifies a mechanism, referred to as "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 co-operating administrative domains.  These domains may be
   administetered by the same provider or closely co-ordinating provider
   networks.

   It makes it possible to advertise multiple tunnels to the same
   destination address, thus avoiding need of multiple loopbacks on the
   egress node.

   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.

   It carries transport prefixes across tunnel domain boundaries (e.g.
   in Inter-AS Option-C networks), 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.



The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-kaliraj-idr-bgp-classful-transport-planes/

There is also an htmlized version available at:
https://datatracker.ietf.org/doc/html/draft-kaliraj-idr-bgp-classful-transport-planes-14

A diff from the previous version is available at:
https://www.ietf.org/rfcdiff?url2=draft-kaliraj-idr-bgp-classful-transport-planes-14


Internet-Drafts are also available by rsync at rsync.ietf.org::internet-drafts

I-D Action: draft-kaliraj-idr-bgp-classful-transp… internet-drafts