<?xml version="1.0" encoding="UTF-8"?>
<reference anchor="I-D.ietf-idr-bgp-ct" target="https://datatracker.ietf.org/doc/html/draft-ietf-idr-bgp-ct-11">
   <front>
      <title>BGP Classful Transport Planes</title>
      <author initials="K." surname="Vairavakkalai" fullname="Kaliraj Vairavakkalai">
         <organization>Juniper Networks, Inc.</organization>
      </author>
      <author initials="N." surname="Venkataraman" fullname="Natrajan Venkataraman">
         <organization>Juniper Networks, Inc.</organization>
      </author>
      <date month="July" day="5" year="2023" />
      <abstract>
	 <t>   This document specifies a mechanism, referred to as &quot;Intent Driven
   Service Mapping&quot;, that uses BGP to express intent based association
   of overlay routes, with underlay routes having specific Traffic
   Engineering (TE) characteristics, that satisfy a certain Service
   Level Agreement (SLA).  The document achieves this by defining new
   constructs, to group underlay routes with sufficienty similar TE
   characteristics into identifiable classes (Transport Class), that
   overlay routes use as an ordered set to resolve reachability
   (Resolution Scheme) towards service endpoints.  These constructs can
   be used to realize the &quot;IETF Network Slice&quot; defined in TEAS Network
   Slices framework.

   This document specifies protocol procedures for BGP that enable
   dissemination of such 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 procedures and follows RFC-8277 NLRI encoding, is defined to
   advertise underlay routes with its identified class.  This new
   address family is called &quot;BGP Classful Transport&quot;, a.k.a., BGP CT.


	 </t>
      </abstract>
   </front>
   <seriesInfo name="Internet-Draft" value="draft-ietf-idr-bgp-ct-11" />
   
</reference>
