RFC 8635: Router Keying for BGPsec
In plain English — editorial summary, not part of the RFC
BGPsec-speaking routers are provisioned with private keys in order to sign BGPsec announcements. The corresponding public keys are published in the Global Resource Public Key Infrastructure (RPKI), enabling verification of BGPsec messages. This document describes two methods of generating the public-private key pairs: router-driven and operator-driven.
Document record
- Document ID
- RFC8635
- Published
- August 2019
- Authors
- R. Bush; S. Turner; K. Patel
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- ops
- Pages
- 21
- Also known as
- —
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 8634BGPsec Router Certificate RolloverCurrent
August 2019
- RFC 8639Subscription to YANG NotificationsCurrent
September 2019
- RFC 8630Resource Public Key Infrastructure (RPKI) Trust Anchor LocatorCurrent
August 2019
- RFC 8640Dynamic Subscription to YANG Events and Datastores over NETCONFCurrent
September 2019
- RFC 8641Subscription to YANG Notifications for Datastore UpdatesCurrent
September 2019
- RFC 8642Policy Behavior for Well-Known BGP CommunitiesCurrent
August 2019
- RFC 8624Algorithm Implementation Requirements and Usage Guidance for DNSSECObsoleted
June 2019
- RFC 8650Dynamic Subscription to YANG Events and Datastores over RESTCONFCurrent
November 2019
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?