RFC 9323: A Profile for RPKI Signed Checklists (RSCs)
In plain English — editorial summary, not part of the RFC
This document defines a Cryptographic Message Syntax (CMS) protected content type for use with the Resource Public Key Infrastructure (RPKI) to carry a general-purpose listing of checksums (a 'checklist'). The objective is to allow for the creation of an attestation, termed an "RPKI Signed Checklist (RSC)", which contains one or more checksums of arbitrary digital objects (files) that are signed with a specific set of Internet Number Resources. When validated, an RSC confirms that the respective Internet resource holder produced the RSC.
Document record
- Document ID
- RFC9323
- Published
- November 2022
- Authors
- J. Snijders; T. Harrison; B. Maddison
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- ops
- Pages
- 13
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- 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 8387Practical Considerations and Implementation Experiences in Securing Smart Object NetworksCurrent
May 2018
- RFC 6518Keying and Authentication for Routing Protocols (KARP) Design GuidelinesCurrent
February 2012
- RFC 5091Identity-Based Cryptography Standard (IBCS) #1: Supersingular Curve Implementations of the BF and BB1 CryptosystemsUpdated
December 2007
- RFC 4306Internet Key Exchange (IKEv2) ProtocolObsoleted
December 2005
- RFC 2560X.509 Internet Public Key Infrastructure Online Certificate Status Protocol - OCSPObsoleted
June 1999
- RFC 9456Updates to the TLS Transport Model for SNMPCurrent
November 2023
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?