Javascript disabled? Like other modern websites, the IETF Datatracker relies on Javascript. Please enable Javascript for full functionality.

BGPsec Router Certificate Rollover
RFC 8634 also known as BCP 224

Revision differences

From revision

To revision

Diff format

Document history

Date	By	Action
2023-12-12	(System)	Imported membership of rfc8634 in bcp224 via sync to the rfc-index
2023-12-12	(System)	No history of BCP224 is currently available in the datatracker before this point
2019-08-07	(System)	Received changes through RFC Editor sync (created alias RFC 8634, changed abstract to 'Certification Authorities (CAs) within the Resource Public Key Infrastructure (RPKI) manage … Received changes through RFC Editor sync (created alias RFC 8634, changed abstract to 'Certification Authorities (CAs) within the Resource Public Key Infrastructure (RPKI) manage BGPsec router certificates as well as RPKI certificates. The rollover of BGPsec router certificates must be carefully performed in order to synchronize the distribution of router public keys with BGPsec UPDATE messages verified with those router public keys. This document describes a safe rollover process, and it discusses when and why the rollover of BGPsec router certificates is necessary. When this rollover process is followed, the rollover will be performed without routing information being lost.', changed standardization level to Best Current Practice, changed state to RFC, added RFC published event at 2019-08-07, changed IESG state to RFC Published, created alias BCP 224)
2019-08-07	(System)	RFC published