[Idr] I-D Action: draft-ietf-idr-bgp-ct-35.txt

internet-drafts@ietf.org Fri, 24 January 2025 21:10 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
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <173775300536.520627.17674603246772955591@dt-datatracker-5584d84fb4-tg2td>
Date: Fri, 24 Jan 2025 13:10:05 -0800
Message-ID-Hash: NQAO4RP5KLF5UNDZ3JVFYFMRNQGOVB3R
CC: idr@ietf.org
Reply-To: idr@ietf.org
Subject: [Idr] I-D Action: draft-ietf-idr-bgp-ct-35.txt
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/mdttmjzUzCNjxMqAeIjMCPcKMVA>

Internet-Draft draft-ietf-idr-bgp-ct-35.txt is now available. It is a work
item of the Inter-Domain Routing (IDR) WG of the IETF.

   Title:   BGP Classful Transport Planes
   Authors: Kaliraj Vairavakkalai
            Natrajan Venkataraman
   Name:    draft-ietf-idr-bgp-ct-35.txt
   Pages:   76
   Dates:   2025-01-24

Abstract:

   This document specifies a mechanism referred to as "Intent Driven
   Service Mapping".  The mechanism uses BGP to express intent based
   association of overlay routes with underlay routes having specific
   Traffic Engineering (TE) characteristics satisfying a certain Service
   Level Agreement (SLA).  This is achieved by defining new constructs
   to group underlay routes with sufficiently similar TE characteristics
   into identifiable classes (called "Transport Classes"), that overlay
   routes use as an ordered set to resolve reachability (Resolution
   Schemes) towards service endpoints.  These constructs can be used,
   for example, to realize the "IETF Network Slice" defined in TEAS
   Network Slices framework.

   Additionally, this document specifies protocol procedures for BGP
   that enable dissemination of service mapping information in a network
   that may span multiple cooperating administrative domains.  These
   domains may be administered either by the same provider or by closely
   coordinating providers.  A new BGP address family that leverages RFC
   4364 ("BGP/MPLS IP Virtual Private Networks (VPNs)" procedures and
   follows RFC 8277 ("Using BGP to Bind MPLS Labels to Address
   Prefixes") NLRI encoding is defined to enable each advertised
   underlay route to be identified by its class.  This new address
   family is called "BGP Classful Transport", a.k.a., BGP CT.

The IETF datatracker status page for this Internet-Draft is:
https://datatracker.ietf.org/doc/draft-ietf-idr-bgp-ct/

There is also an HTMLized version available at:
https://datatracker.ietf.org/doc/html/draft-ietf-idr-bgp-ct-35

A diff from the previous version is available at:
https://author-tools.ietf.org/iddiff?url2=draft-ietf-idr-bgp-ct-35

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

[Idr] I-D Action: draft-ietf-idr-bgp-ct-35.txt internet-drafts