RFC 5871

RFC 5871

RFC 5871 is an Internet Standards-track document that specifies an extension to the Border Gateway Protocol version 4 used in interdomain routing. It defines a capability for advertising support for a specific route discovery mechanism and augments BGP message formats to carry supplementary attributes. The document interacts with multiple IETF working groups and informs implementations by network vendors and service providers.

Background and Purpose

The specification was developed within the Internet Engineering Task Force and relates to work by the IETF Routing Area, the IETF Working Group on Inter-Domain Routing, and contributors associated with the Internet Architecture Board. It addresses operational requirements encountered by operators of Autonomous Systems such as those run by regional registries like the American Registry for Internet Numbers, as well as major network operators represented at industry fora and standards bodies. Influences include operational experiences shared at events like NANOG and RIPE meetings, and technical coordination with standards such as those from the Internet Assigned Numbers Authority and the Institute of Electrical and Electronics Engineers.

Specification Summary

The document augments existing BGP capabilities by defining a capability code and associated parameters that are encoded within BGP OPEN messages and route attributes that may be carried in UPDATE messages. It references the BGP-4 protocol, interaction patterns specified in connection with Autonomous System path attributes, and considerations derived from the operational models exemplified by large-edge networks and transit providers. The specification details message formats, encoding rules, and error-handling behavior influenced by precedents from other Internet Standards and protocols developed within the IETF community.

Protocol Extensions and Mechanisms

The extension introduces new capability advertisement mechanisms in the BGP OPEN handshake and defines how peers negotiate the optional capability. It specifies new attribute types and optional transitive semantics that affect route propagation, comparable to other BGP enhancements. The mechanism includes procedures for capability negotiation, attribute validation, attribute propagation across route reflector topologies, and interactions with policies commonly implemented by ISPs, content delivery networks, cloud providers, and exchange point participants. The document also describes interactions with existing attributes such as AS_PATH, NEXT_HOP, and community-like constructs used by operators.

Security Considerations

The document includes considerations for authentication and integrity of capability negotiation, alignment with deployment practices used by large providers and registries, and mitigation strategies against misconfiguration and malicious advertisement. It addresses potential threats familiar from incidents discussed in reports by organizations such as the Internet Society and operator communities, and suggests operational safeguards and monitoring practices informed by the security research community and standards from bodies like the National Institute of Standards and Technology.

Implementation and Deployment

Implementations were produced by multiple network equipment vendors and integrated into router platforms used by service providers, cloud operators, and content networks. Deployments were coordinated through operational communities and network operator exchanges, with incremental rollout strategies reflecting practices promoted at regional forums and standards workshops. Interoperability testing took place in vendor labs and at multi-vendor interoperability events, and the specification influenced software-based routers and routing suites maintained by open source communities and industry vendors.

History and Reception

The extension was proposed in the context of ongoing efforts to evolve interdomain routing capabilities and was discussed in IETF meetings and mailing lists frequented by engineers from Internet service providers, content providers, and academic research groups. Reception among operators and implementers reflected typical debates over trade-offs between additional capability expressiveness and operational complexity, with adoption patterns shaped by vendor support, operator policy frameworks, and the operational experiences reported at conferences and working group sessions.

Internet Engineering Task Force Border Gateway Protocol BGP-4 Autonomous System American Registry for Internet Numbers NANOG RIPE Internet Architecture Board Internet Society National Institute of Standards and Technology IETF Working Group Internet Assigned Numbers Authority route reflector Internet Standards network operator content delivery network cloud provider exchange point open source vendor interoperability routing routing policy message format capability negotiation UPDATE message OPEN message AS_PATH NEXT_HOP community (BGP) security authentication integrity misconfiguration monitoring operational community inter-domain routing transit provider edge network standards workshop mailing list vendor lab interoperability event deployment strategy incremental rollout operational safeguard encoding rules error handling attribute validation propagation topology multivendor software-based router routing suite research group conference working group session

Category:Internet standards