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") and obsoletes RFC 8208 ("BGPsec Algorithms, Key Formats, and Signature Formats") by adding Documentation and Experimentation Algorithm IDs, correcting the range of unassigned algorithms IDs to fill the complete range, and restructuring the document for better reading. 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
- RFC8608
- Published
- June 2019
- Authors
- S. Turner; O. Borchert
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- ops
- Pages
- 21
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 9053CBOR Object Signing and Encryption (COSE): Initial AlgorithmsUpdated
August 2022
- RFC 7908Problem Definition and Classification of BGP Route LeaksCurrent
June 2016
- RFC 9323A Profile for RPKI Signed Checklists (RSCs)Current
November 2022
- RFC 9691A Profile for Resource Public Key Infrastructure (RPKI) Trust Anchor Keys (TAKs)Current
December 2024
- RFC 8725JSON Web Token Best Current PracticesCurrent
February 2020
- RFC 8463A New Cryptographic Signature Method for DomainKeys Identified Mail (DKIM)Current
September 2018
- RFC 8422Elliptic Curve Cryptography (ECC) Cipher Suites for Transport Layer Security (TLS) Versions 1.2 and EarlierObsoleted
August 2018
- RFC 8416Simplified Local Internet Number Resource Management with the RPKI (SLURM)Current
August 2018
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?