BGPsec Protocol Specification, September 2017
- File formats:
- PROPOSED STANDARD
- Updated by:
- RFC 8206
- M. Lepinski, Ed.
K. Sriram, Ed.
- sidr (rtg)
Cite this RFC: TXT | XML | BibTeX
Discuss this RFC: Send questions or comments to the mailing list firstname.lastname@example.org
Other actions: Submit Errata | Find IPR Disclosures from the IETF | View History of RFC 8205
This document describes BGPsec, an extension to the Border Gateway Protocol (BGP) that provides security for the path of Autonomous Systems (ASes) through which a BGP UPDATE message passes. BGPsec is implemented via an optional non-transitive BGP path attribute that carries digital signatures produced by each AS that propagates the UPDATE message. The digital signatures provide confidence that every AS on the path of ASes listed in the UPDATE message has explicitly authorized the advertisement of the route.
For the definition of Status, see RFC 2026.
For the definition of Stream, see RFC 8729.