Search RFCs

RFC Editor

File formats:

Status:

PROPOSED STANDARD

Updated by:

RFC 8206

Authors:

M. Lepinski, Ed.
K. Sriram, Ed.

Stream:

IETF

Source:

sidr (rtg)

Cite this RFC:TXT  | XML  |  BibTeX

DOI:  https://doi.org/10.17487/RFC8205

Discuss this RFC: Send questions or comments to the mailing listsidr@ietf.org

Other actions:Submit Errata  | Find IPR Disclosures from the IETF  | View History of RFC 8205

Abstract

This document describes BGPsec, an extension to the Border GatewayProtocol (BGP) that provides security for the path of AutonomousSystems (ASes) through which a BGP UPDATE message passes. BGPsec isimplemented via an optional non-transitive BGP path attribute thatcarries digital signatures produced by each AS that propagates theUPDATE message. The digital signatures provide confidence that everyAS on the path of ASes listed in the UPDATE message has explicitlyauthorized the advertisement of the route.

For the definition ofStatus,seeRFC 2026.

For the definition ofStream, seeRFC 8729.