RFC 8208: BGPsec Algorithms, Key Formats, and Signature Formats
This RFC has been replaced. Do not implement against it for new work — it was formally obsoleted by RFC 8608.
Current version: RFC 8608 — BGPsec Algorithms, Key Formats, and Signature Formats
In plain English — editorial summary, not part of the RFC
This document specifies the algorithms, algorithm parameters, asymmetric key formats, asymmetric key sizes, and signature formats used in BGPsec (Border Gateway Protocol Security). This document updates RFC 7935 ("The Profile for Algorithms and Key Sizes for Use in the Resource Public Key Infrastructure"). This document also includes example BGPsec UPDATE messages as well as the private keys used to generate the messages and the certificates necessary to validate those signatures.
Document record
- Document ID
- RFC8208
- Published
- September 2017
- Authors
- S. Turner; O. Borchert
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- rtg
- Pages
- 19
- Also known as
- —
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.
- RFC 8209A Profile for BGPsec Router Certificates, Certificate Revocation Lists, and Certification RequestsCurrent
September 2017
- RFC 8207BGPsec Operational ConsiderationsCurrent
September 2017
- RFC 8206BGPsec Considerations for Autonomous System (AS) MigrationCurrent
September 2017
- RFC 8210The Resource Public Key Infrastructure (RPKI) to Router Protocol, Version 1Current
September 2017
- RFC 8205BGPsec Protocol SpecificationUpdated
September 2017
- RFC 8211Adverse Actions by a Certification Authority (CA) or Repository Manager in the Resource Public Key Infrastructure (RPKI)Current
September 2017
- RFC 8203BGP Administrative Shutdown CommunicationObsoleted
July 2017
- RFC 8202IS-IS Multi-InstanceCurrent
June 2017
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?