[Idr] I-D Action: draft-ietf-idr-bgp-classful-transport-planes-00.txt

internet-drafts@ietf.org Wed, 10 August 2022 19:26 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
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: idr@ietf.org
Message-ID: <166015960377.17900.14944754493202872385@ietfa.amsl.com>
Date: Wed, 10 Aug 2022 12:26:43 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/v1Lp8SokaFGGIIxJ3JOPO_qo7Rs>
Subject: [Idr] I-D Action: draft-ietf-idr-bgp-classful-transport-planes-00.txt

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
                          Israel Means
  Filename        : draft-ietf-idr-bgp-classful-transport-planes-00.txt
  Pages           : 37
  Date            : 2022-08-10

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.



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

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


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

[Idr] I-D Action: draft-ietf-idr-bgp-classful-tra… internet-drafts