metasystema.org
UpdatedPROPOSED STANDARDIETF stream

RFC 8205: BGPsec Protocol Specification

Still current, but amended. Parts of this document are changed or extended by RFC 8206. Read both.

In plain English — editorial summary, not part of the RFC

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.

Document record

Document ID
RFC8205
Published
September 2017
Authors
M. Lepinski; K. Sriram
Status
PROPOSED STANDARD
Stream
IETF
Area
rtg
Pages
45
Also known as
—
Updated by:
RFC 8206

Topics

Referenced by

One later RFC formally updates or obsoletes part of this document.

Related documents

Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.

Also filed under

About this page

The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.

Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.

Data sources · Editorial policy · Report a correction · What is an RFC?

canonical URL: /rfc/8205-bgpsec-protocol-specification