RFC Errata
RFC 9832, "BGP Classful Transport Planes", September 2025
Source of RFC: idr (rtg)See Also: RFC 9832 w/ inline errata
Errata ID: 8583
Status: Verified
Type: Editorial
Publication Format(s) : TEXT, PDF, HTML
Reported By: Natrajan Venkataraman
Date Reported: 2025-09-25
Verifier Name: Ketan Talaulikar
Date Verified: 2025-09-30
Section 3 says:
Original Text 1: Figure 1 depicts the intra-AS and inter-AS application of these constructs. Interactions between SN1 and PE11 describe the intra-AS usage. Interactions between PE21 and PE11 describe the inter-AS usage. Original Text 2: For the intra-AS case, SN1 maps this intra-AS route on RSVP-TE tunnels with TC ID 100 by using the Resolution Scheme for color:0:100. Original Text 3: PE21 maps the inter-AS service routes received with color:0:100 from AS1 on BGP CT tunnel with TC ID 100 by using the Resolution Scheme for color:0:100. Note that this procedure is same as that followed by SN1 in the intra-AS case.
It should say:
Corrected Text 1: Figure 1 depicts the intra-AS and inter-AS application of these constructs. Interactions between SN11 and PE11 describe the intra-AS usage. Interactions between PE21 and PE11 describe the inter-AS usage. Corrected Text 2: For the intra-AS case, SN11 maps this intra-AS route on RSVP-TE tunnels with TC ID 100 by using the Resolution Scheme for color:0:100. Corrected Text 3: PE21 maps the inter-AS service routes received with color:0:100 from AS1 on BGP CT tunnel with TC ID 100 by using the Resolution Scheme for color:0:100. Note that this procedure is same as that followed by SN11 in the intra-AS case.
Notes:
In Section 3, Architecture Overview, the diagram shows "SN11" as a service node in AS1. In this section, there are 3 occurrences of "SN11" wrongly labeled as "SN1" in Section 3 text. I kindly request that this editorial misrepresentation be corrected. Original and Corrected text have been added for all the three occurrences.
