RFC 9829: Handling of Resource Public Key Infrastructure (RPKI) Certificate Revocation List (CRL) Number Extensions
In plain English — editorial summary, not part of the RFC
This document revises how the Resource Public Key Infrastructure (RPKI) handles Certificate Revocation List (CRL) Number extensions. This document updates RFC 6487.
Document record
- Document ID
- RFC9829
- Published
- July 2025
- Authors
- J. Snijders; B. Maddison; T. Buehler
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- ops
- Pages
- 7
- Also known as
- —
- Updates:
- RFC 6487
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 9981Resource Public Key Infrastructure (RPKI) Manifest Number HandlingCurrent
May 2026
- RFC 9582A Profile for Route Origin Authorizations (ROAs)Current
May 2024
- RFC 6382Unique Origin Autonomous System Numbers (ASNs) per Node for Globally Anycasted ServicesCurrent
October 2011
- RFC 8207BGPsec Operational ConsiderationsCurrent
September 2017
- RFC 6916Algorithm Agility Procedure for the Resource Public Key Infrastructure (RPKI)Current
April 2013
- RFC 6483Validation of Route Origination Using the Resource Certificate Public Key Infrastructure (PKI) and Route Origin Authorizations (ROAs)Current
February 2012
- RFC 6482A Profile for Route Origin Authorizations (ROAs)Obsoleted
February 2012
- RFC 6480An Infrastructure to Support Secure Internet RoutingCurrent
February 2012
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?