Skip to main content

10. IANA Considerations

10.1. BGP CAR SAFIs​

IANA has allocated SAFI value 83 (BGP CAR) and SAFI value 84 (BGP VPN CAR) from the "SAFI Values" registry within the "Subsequent Address Family Identifiers (SAFI) Parameters" registration group, with this document as reference.

10.2. "BGP CAR NLRI Types" Registry​

IANA has created the "BGP CAR NLRI Types" registry within the "Border Gateway Protocol (BGP) Parameters" registration group, with this document as reference. This registry is used to assign 1-octet code points for BGP CAR NLRI types:

TypeNLRI TypeReference
0ReservedRFC 9871
1Color-Aware RouteRFC 9871
2IP PrefixRFC 9871
3-255Unassigned-

Assignments within the registry should follow the "Specification Required" policy as specified in [RFC8126].

10.3. "BGP CAR NLRI TLV" Registry​

IANA has created the "BGP CAR NLRI TLV Types" registry within the "Border Gateway Protocol (BGP) Parameters" registration group, with this document as reference. This registry is used to assign 6-bit code points for BGP CAR NLRI non-key TLV types:

TypeNLRI TLV TypeReference
0ReservedRFC 9871
1LabelRFC 9871
2Label-IndexRFC 9871
3SRv6 SIDRFC 9871
4-64Unassigned-

10.4. Guidance for Designated Experts​

Designated Experts (DEs) should confirm that specifications meet the requirements of the "Specification Required" policy. DEs MUST verify that any code point request has been made available for review and comment within the IETF and ensure it does not conflict with active or published work within the IETF.

10.4.1. Additional Evaluation Criteria for "BGP CAR NLRI Types" Registry​

  • Check interoperability between new NLRI types and current NLRI types specified for BGP CAR SAFI in this document
  • Verify design integrity and consistency

10.4.2. Additional Evaluation Criteria for "BGP CAR NLRI TLV" Registry​

  • Check interoperability of new TLV types with existing TLV types
  • Verify clarity and consistency of TLV design

10.5. "Border Gateway Protocol (BGP) Extended Communities" Registry​

IANA has allocated subtype value 0x1b in the "Transitive Opaque Extended Community Sub-Types" registry of the "BGP Extended Communities" registry, with name "Local Color Mapping", referencing this document.

11. Manageability and Operational Considerations

Operational Considerations​

Color Planning:

  • Operators should carefully plan color assignment strategies
  • Maintain consistent color-to-intent mapping within organizations
  • Perform appropriate color remapping at color domain boundaries

Routing Policy:

  • Configure appropriate routing policies to control CAR route advertisement and acceptance
  • Use filtering mechanisms to limit unnecessary route propagation
  • Implement on-demand route subscription to optimize scalability

Monitoring and Debugging:

  • Monitor CAR route propagation and resolution
  • Verify color-aware paths are established as expected
  • Use appropriate tools to track service traffic steering

Interoperability:

  • Ensure interoperability across different vendor devices
  • Conduct thorough testing before deploying new features
  • Coordinate color mapping with peering domains

Deployment Strategy:

  • Adopt a gradual deployment approach
  • Start from core network and gradually expand to edges
  • Leverage hierarchical design to improve scalability

12. Security Considerations

BGP CAR inherits all security considerations of the BGP protocol as described in [RFC4271].

Key Security Considerations​

Routing Security:

  • BGP CAR routes should be exchanged within trusted domains
  • Use appropriate BGP session protection mechanisms (e.g., TCP MD5, BGP-SEC)
  • Implement strict routing policies to prevent unauthorized route injection

Color Manipulation:

  • Misconfigured color mappings may lead to suboptimal path selection
  • Malicious nodes may attempt to manipulate color values to influence traffic engineering
  • Use routing policies to validate and filter color values

Data Plane Security:

  • Ensure security of encapsulation mechanisms (MPLS, SR, SRv6)
  • Prevent label spoofing and SID manipulation
  • Use encrypted transport when necessary

DoS Protection:

  • Implement rate limiting to prevent BGP update flooding
  • Monitor abnormal route churn
  • Be aware of scalability impacts when using BGP ADD-PATH

Privacy Considerations:

  • Color and intent information may reveal network topology and policies
  • Carefully consider information sharing across organizational boundaries
  • Use appropriate access controls to limit visibility of routing information

13. References

13.1. Normative References​

This document normatively references the following RFCs:

  • [RFC2119]: Key words for use in RFCs to Indicate Requirement Levels
  • [RFC4271]: A Border Gateway Protocol 4 (BGP-4)
  • [RFC4360]: BGP Extended Communities Attribute
  • [RFC4760]: Multiprotocol Extensions for BGP-4
  • [RFC7311]: The Accumulated IGP Metric Attribute for BGP
  • [RFC7606]: Revised Error Handling for BGP UPDATE Messages
  • [RFC8174]: Ambiguity of Uppercase vs Lowercase in RFC 2119 Key Words
  • [RFC8277]: Using BGP to Bind MPLS Labels to Address Prefixes
  • [RFC8402]: Segment Routing Architecture
  • [RFC8669]: Segment Routing Prefix Segment Identifier Extensions for BGP
  • [RFC9012]: The BGP Tunnel Encapsulation Attribute
  • [RFC9252]: BGP Overlay Services Based on Segment Routing over IPv6 (SRv6)
  • [RFC9256]: Segment Routing Policy Architecture
  • [RFC8126]: Guidelines for Writing an IANA Considerations Section in RFCs

13.2. Informative References​

This document informatively references the following documents:

  • [INTENT-AWARE]: Intent-Aware Transport Problem Statement and Requirements
  • [RFC2545]: Use of BGP-4 Multiprotocol Extensions for IPv6 Inter-Domain Routing
  • [RFC4684]: Constrained Route Distribution for Border Gateway Protocol/MultiProtocol Label Switching (BGP/MPLS) Internet Protocol (IP) Virtual Private Networks (VPNs)
  • [RFC7911]: Advertisement of Multiple Paths in BGP
  • [RFC8986]: Segment Routing over IPv6 (SRv6) Network Programming
  • [RFC9350]: IGP Flexible Algorithm
  • [SRv6-INTERWORK]: SRv6 and MPLS Interworking

(For other references, please see RFC 9871 original text)

Note: For complete reference list and detailed security analysis, please refer to RFC 9871 original text.

Last updated on