{"draft":"draft-ietf-idr-bgp-ct-39","doc_id":"RFC9832","title":"BGP Classful Transport Planes","authors":["K. Vairavakkalai, Ed.","N. Venkataraman, Ed."],"format":["HTML","TEXT","PDF","XML"],"page_count":"67","pub_status":"EXPERIMENTAL","status":"EXPERIMENTAL","source":"Inter-Domain Routing","abstract":"This document specifies a mechanism referred to as \"Intent-Driven\r\nService Mapping\". The mechanism uses BGP to express Intent-based\r\nassociation of overlay routes with underlay routes having specific\r\nTraffic Engineering (TE) characteristics satisfying a certain Service\r\nLevel Agreement (SLA). This is achieved by defining new constructs to\r\ngroup underlay routes with sufficiently similar TE characteristics\r\ninto identifiable classes (called \"Transport Classes\" or \"TCs\"), that\r\noverlay routes use as an ordered set to resolve reachability\r\n(Resolution Schemes) towards service endpoints. These constructs can\r\nbe used, for example, to realize the \"IETF Network Slice\" defined in\r\nthe TEAS Network Slices framework (RFC 9543).\r\n\r\nAdditionally, this document specifies protocol procedures for BGP\r\nthat enable dissemination of service mapping information in a network\r\nthat may span multiple cooperating administrative domains. These\r\ndomains may be administered either by the same provider or by closely\r\ncoordinating providers. A new BGP address family that leverages the\r\nprocedures described in RFC 4364 (\"BGP\/MPLS IP Virtual Private\r\nNetworks (VPNs)\") and follows the NLRI encoding described in RFC 8277\r\n(\"Using BGP to Bind MPLS Labels to Address Prefixes\") is defined to\r\nenable each advertised underlay route to be identified by its class.\r\nThis new address family is called \"BGP Classful Transport\" (or \"BGP\r\nCT\").","pub_date":"September 2025","keywords":["BGP-CT","CT","Intent-Based Routing","BGP Service Mapping"],"obsoletes":[],"obsoleted_by":[],"updates":[],"updated_by":[],"see_also":[],"doi":"10.17487\/RFC9832","errata_url":null}