Skip to main content

A Profile for Resource Public Key Infrastructure (RPKI) Canonical Cache Representation (CCR)
draft-ietf-sidrops-rpki-ccr-11

Revision differences

Document history

Date Rev. By Action
2026-07-17
11 (System) IANA Action state changed to RFC-Ed-Ack from Waiting on RFC Editor
2026-07-16
11 (System) IANA Action state changed to Waiting on RFC Editor from In Progress
2026-07-16
11 (System) IANA Action state changed to In Progress from Waiting on Authors
2026-07-10
11 (System) IANA Action state changed to Waiting on Authors from In Progress
2026-07-07
11 (System) RPC status changed to blocked: Reference Not Received
2026-07-07
11 (System) RFC Editor state changed to Blocked
2026-07-07
11 (System) IESG state changed to RFC Ed Queue from Approved-announcement sent
2026-07-07
11 (System) Announcement was received by RFC Editor
2026-07-04
11 Barry Leiba Closed request for IETF Last Call review by ARTART with state 'Overtaken by Events': Document has completed IESG processing
2026-07-04
11 Barry Leiba Assignment of request for IETF Last Call review by ARTART to Darrel Miller was marked no-response
2026-07-02
11 (System) IANA Action state changed to In Progress
2026-07-02
11 Liz Flynn IESG state changed to Approved-announcement sent from Approved-announcement to be sent
2026-07-02
11 Liz Flynn IESG has approved the document
2026-07-02
11 Liz Flynn Closed "Approve" ballot
2026-07-02
11 Liz Flynn Ballot approval text was generated
2026-07-02
11 (System) Removed all action holders (IESG state changed)
2026-07-02
11 Morgan Condie IESG state changed to Approved-announcement to be sent from IESG Evaluation
2026-07-01
11 Tommy Jensen [Ballot Position Update] New position, No Objection, has been recorded for Tommy Jensen
2026-07-01
11 Christopher Inacio
[Ballot comment]
Thanks to Joe S. for the SECDIR review.

Thanks for the well written draft.

My only comment is to second Deb's comment about …
[Ballot comment]
Thanks to Joe S. for the SECDIR review.

Thanks for the well written draft.

My only comment is to second Deb's comment about SHA-1.  It is being used as a hash, but you can create collisions in it - what would happen if someone engineered the rpki certificates to cause a hash collision?
2026-07-01
11 Christopher Inacio [Ballot Position Update] New position, No Objection, has been recorded for Christopher Inacio
2026-07-01
11 Amanda Baber IANA Review state changed to IANA OK - Actions Needed from Version Changed - Review Needed
2026-07-01
11 (System) IANA Review state changed to Version Changed - Review Needed from IANA OK - Actions Needed
2026-07-01
11 Job Snijders New version available: draft-ietf-sidrops-rpki-ccr-11.txt
2026-07-01
11 Job Snijders New version accepted (logged-in submitter: Job Snijders)
2026-07-01
11 Job Snijders Uploaded new revision
2026-06-30
10 Andy Newton [Ballot Position Update] New position, No Objection, has been recorded for Andy Newton
2026-06-29
10 Éric Vyncke [Ballot comment]
Thanks for the work done, clear cut draft with the correct use of BCP14 terms per https://datatracker.ietf.org/doc/statement-iesg-statement-on-clarifying-the-use-of-bcp-14-key-words/
2026-06-29
10 Éric Vyncke [Ballot Position Update] New position, No Objection, has been recorded for Éric Vyncke
2026-06-29
10 (System) IANA Review state changed to IANA OK - Actions Needed from Version Changed - Review Needed
2026-06-29
10 Roman Danyliw [Ballot comment]
Thank you to Behcet Sarikaya for the GENART review.
2026-06-29
10 Roman Danyliw [Ballot Position Update] New position, No Objection, has been recorded for Roman Danyliw
2026-06-28
10 Job Snijders New version available: draft-ietf-sidrops-rpki-ccr-10.txt
2026-06-28
10 Job Snijders New version accepted (logged-in submitter: Job Snijders)
2026-06-28
10 Job Snijders Uploaded new revision
2026-06-28
09 Mahesh Jethanandani
[Ballot comment]
Section 8.1, Normative References, [I-D.ietf-sidrops-aspa-profile] entry:

659 >    [I-D.ietf-sidrops-aspa-profile]
660 >              Snijders, …
[Ballot comment]
Section 8.1, Normative References, [I-D.ietf-sidrops-aspa-profile] entry:

659 >    [I-D.ietf-sidrops-aspa-profile]
660 >              Snijders, J., Azimov, A., Uskov, E., Bush, R., Housley,
661 >              R., and B. Maddison, "A Profile for Autonomous System
662 >              Provider Authorization", Work in Progress, Internet-Draft,
663 >              draft-ietf-sidrops-aspa-profile-26, 19 April 2026,
664 >                              aspa-profile-26>.

I note for awareness that draft-ietf-sidrops-aspa-profile is a normative
reference that, as of the telechat date, remains a WG document in "I-D
Exists" state: it has not been submitted to the IESG and is not in the RFC
Editor queue. I imagine it will sit in MISREF in the RFC Editor queue.

----------------------------------------------------------------------
NIT
----------------------------------------------------------------------

All comments below are about very minor potential issues that you may
choose to address in some way - or ignore - as you see fit. Some were
flagged by automated tools (via
https://github.com/larseggert/ietf-reviewtool), so there will likely
be some false positives. There is no need to let me know what you did
with these suggestions.

Section 6, Security Considerations, contextual bounds example:

528 >    stop further processing on failure.  For example, the maxLength
529 >    element in a ROAIPAddress cannot contain an integer smaller than the
530 >    length of the accompanying prefix, the manifestNumber field is cannot
531 >    be longer than 20 octets, etc.

s/the manifestNumber field is cannot/the manifestNumber field cannot/

---

Appendix A, Acknowledgements:

800 >    The authors wish to thank Russ Housley, Luuk Hendriks, Fedor Vompe,
801 >    Tom Harrison, Changwang Lin, Luigi Iannone, Luuk Hendriks, Mohamed
802 >    Boucadair, Deb Cooley, and Gunter van de Velde for their generous
803 >    feedback on this specification.

Luuk Hendriks appears twice (lines 800 and 801). Twice the credit :-)
2026-06-28
09 Mahesh Jethanandani [Ballot Position Update] New position, No Objection, has been recorded for Mahesh Jethanandani
2026-06-27
09 Gorry Fairhurst [Ballot Position Update] New position, No Objection, has been recorded for Gorry Fairhurst
2026-06-26
09 Ketan Talaulikar
[Ballot comment]
Thanks to the authors and the WG for their work on this document.

I have a few comments, questions, and suggestions for consideration …
[Ballot comment]
Thanks to the authors and the WG for their work on this document.

I have a few comments, questions, and suggestions for consideration by the authors and the WG:

1) Section 3: Is the hard lower limit size of 1000 fully thought out ... for today, tomorrow (e.g., something changes to reduce/compress?)

ManifestInstance ::= SEQUENCE {
  hash              Digest,
  size              INTEGER (1000..MAX), <<<< this one!
  aki              KeyIdentifier,
  manifestNumber    INTEGER (0..MAX),
  thisUpdate        GeneralizedTime,
  locations        SEQUENCE (SIZE(1..MAX)) OF AccessDescription,
  subordinates      SEQUENCE (SIZE(1..MAX)) OF SubjectKeyIdentifier
                      OPTIONAL }

2) Section 3 - not an expert on ASN.1 nor this particular feature/technology ... but CertificateSerialNumber FROM PKIX1Explicit-2009 is unused. Please cross-check if there hasn't been an error or remove unused.

3) section 3.1

"In this version of the specification, it MUST be 0." seems a bit odd.

Perhaps: Version MUST be set to 0 for the CCR content specified in this document.

4) section 5.3 ... a nit

"CCRs compress very well due to its data layout characteristics"

Perhaps: "CCRs compress very well due to their data layout characteristics" or "A CCR file compresses very well due to its data layout characteristics"
2026-06-26
09 Ketan Talaulikar [Ballot Position Update] New position, No Objection, has been recorded for Ketan Talaulikar
2026-06-24
09 (System) IANA Review state changed to Version Changed - Review Needed from IANA OK - Actions Needed
2026-06-24
09 Job Snijders New version available: draft-ietf-sidrops-rpki-ccr-09.txt
2026-06-24
09 Job Snijders New version accepted (logged-in submitter: Job Snijders)
2026-06-24
09 Job Snijders Uploaded new revision
2026-06-23
08 Gunter Van de Velde
[Ballot comment]
Hi Authors, WG,

# Gunter Van de Velde, RTG AD, comments for draft-ietf-sidrops-rpki-ccr-08

# line numbers are rendered from the idnits tool found …
[Ballot comment]
Hi Authors, WG,

# Gunter Van de Velde, RTG AD, comments for draft-ietf-sidrops-rpki-ccr-08

# line numbers are rendered from the idnits tool found at https://author-tools.ietf.org/api/idnits?url=https://www.ietf.org/archive/id/draft-ietf-sidrops-rpki-ccr-08.txt

# Potential Missing References
Would these references improve the document?
RFC 8897 (Requirements for RPKI Relying Parties): CCR is fundamentally a validated-cache export format. A citation to RP requirements could provide useful context for implementers regarding cache behavior and validation assumptions.
RFC 9323 (RPKI Signed Checklists): The document conceptually resembles a compact signed representation of validated state. While not required, a brief informative comparison may help readers understand why CCR exists and how it differs from RSCs.

# Section 1 Introduction: The introduction states CCR represents the state of a validated cache at a point in time.
Question "Is the representation intended to be deterministic across implementations given identical validated inputs?"
The term "Canonical" strongly implies byte-for-byte reproducibility. If this is a design goal, I recommend stating it explicitly.
If deterministic output is not guaranteed, the introduction should clarify what properties are canonical.

# Section 2 (CCR Structure): Would the document benefit from a stronger statement regarding ordering rules?
Questions: Are all contained elements required to be sorted? If so, what exact sort order is required?,  Is DER alone sufficient to guarantee canonical representation, or are additional ordering constraints required?
DER canonicalizes encoding but not necessarily semantic ordering of collections.

Kind Regards,
Gunter Van de Velde
Routing Area Director
2026-06-23
08 Gunter Van de Velde [Ballot Position Update] New position, No Objection, has been recorded for Gunter Van de Velde
2026-06-23
08 Jim Guichard [Ballot Position Update] New position, No Objection, has been recorded for Jim Guichard
2026-06-22
08 Deb Cooley
[Ballot comment]
I would appreciate consideration, most of these can be resolved pretty easily.

Thanks to Joe Salowey for their secdir review. I agree with …
[Ballot comment]
I would appreciate consideration, most of these can be resolved pretty easily.

Thanks to Joe Salowey for their secdir review. I agree with Joe's assessment:

- The continued use of SHA-1 (Section 3.4.1.1 Subordinates and Section 3.4.4): At some point, a migration will have to happen, because at some point implementations won't have SHA-1 implemented.  If it doesn't make sense to fix this issue in this draft, I recommend that the risks be mentioned in Section 6.

- Privacy/sensitive information:  The ramifications of the information not being public should be explained in Section 6 where it is mentioned in the last para.

Section 5.1:  Verifying a hash value that isn't signed isn't actually an integrity check, except in the case of unintentional integrity issues.  Certainly an attacker can modify both the original data and the hash.  Please clarify what type of integrity is required/intended.

Section 6, last para:  I'm not sure how the fact that CCRs are not signed is related to whether the RPKI information is public (or not).  Perhaps two paragraphs are needed?  Move the middle sentence out into its own paragraph (since it has nothing to do with signatures or authenticity.
2026-06-22
08 Deb Cooley [Ballot Position Update] New position, No Objection, has been recorded for Deb Cooley
2026-06-18
08 Behcet Sarikaya Request for IETF Last Call review by GENART Completed: Ready with Nits. Reviewer: Behcet Sarikaya. Sent review to list.
2026-06-17
08 Mohamed Boucadair Placed on agenda for telechat - 2026-07-02
2026-06-17
08 Mohamed Boucadair Ballot has been issued
2026-06-17
08 Mohamed Boucadair [Ballot Position Update] New position, Yes, has been recorded for Mohamed Boucadair
2026-06-17
08 Mohamed Boucadair Created "Approve" ballot
2026-06-17
08 Mohamed Boucadair IESG state changed to IESG Evaluation from Waiting for AD Go-Ahead
2026-06-17
08 Mohamed Boucadair Ballot writeup was changed
2026-06-17
08 (System) IESG state changed to Waiting for AD Go-Ahead from In Last Call
2026-06-16
08 Zheng Zhang Request for IETF Last Call review by RTGDIR Completed: Ready. Reviewer: Zheng Zhang. Sent review to list. Submission of review completed at an earlier date.
2026-06-16
08 Zheng Zhang Request for IETF Last Call review by RTGDIR Completed: Ready. Reviewer: Zheng Zhang.
2026-06-15
08 Joseph Salowey
Request for IETF Last Call review by SECDIR Completed: Has Issues. Reviewer: Joseph Salowey. Sent review to list. Submission of review completed at an earlier …
Request for IETF Last Call review by SECDIR Completed: Has Issues. Reviewer: Joseph Salowey. Sent review to list. Submission of review completed at an earlier date.
2026-06-15
08 Joseph Salowey Request for IETF Last Call review by SECDIR Completed: Has Issues. Reviewer: Joseph Salowey.
2026-06-12
08 Tero Kivinen Request for IETF Last Call review by SECDIR is assigned to Joseph Salowey
2026-06-10
08 Rifaat Shekh-Yusef Assignment of request for IETF Last Call review by SECDIR to Rifaat Shekh-Yusef was rejected
2026-06-08
08 Haomian Zheng Request for IETF Last Call review by RTGDIR is assigned to Zheng Zhang
2026-06-08
08 Tero Kivinen Request for IETF Last Call review by SECDIR is assigned to Rifaat Shekh-Yusef
2026-06-07
08 Sasha Vainshtein Assignment of request for IETF Last Call review by RTGDIR to Sasha Vainshtein was rejected
2026-06-07
08 Haomian Zheng Request for IETF Last Call review by RTGDIR is assigned to Sasha Vainshtein
2026-06-05
08 Sabrina Tanamal IANA Experts State changed to Expert Reviews OK from Reviews assigned
2026-06-05
08 (System) IANA Review state changed to IANA OK - Actions Needed from IANA - Review Needed
2026-06-04
08 Jean Mahoney Request for IETF Last Call review by GENART is assigned to Behcet Sarikaya
2026-06-03
08 David Dong IANA Experts State changed to Reviews assigned
2026-06-03
08 Morgan Condie IANA Review state changed to IANA - Review Needed
2026-06-03
08 Morgan Condie
The following Last Call announcement was sent out (ends 2026-06-17):

From: The IESG
To: IETF-Announce
CC: draft-ietf-sidrops-rpki-ccr@ietf.org, housley@vigilsec.com, mohamed.boucadair@orange.com, sidrops-chairs@ietf.org, sidrops@ietf.org …
The following Last Call announcement was sent out (ends 2026-06-17):

From: The IESG
To: IETF-Announce
CC: draft-ietf-sidrops-rpki-ccr@ietf.org, housley@vigilsec.com, mohamed.boucadair@orange.com, sidrops-chairs@ietf.org, sidrops@ietf.org
Reply-To: last-call@ietf.org
Sender:
Subject: Last Call:  (A Profile for Resource Public Key Infrastructure (RPKI) Canonical Cache Representation (CCR)) to Proposed Standard


The IESG has received a request from the SIDR Operations WG (sidrops) to
consider the following document: - 'A Profile for Resource Public Key
Infrastructure (RPKI) Canonical
  Cache Representation (CCR)'
  as Proposed Standard

The IESG plans to make a decision in the next few weeks, and solicits final
comments on this action. Please send substantive comments to the
last-call@ietf.org mailing lists by 2026-06-17. Exceptionally, comments may
be sent to iesg@ietf.org instead. In either case, please retain the beginning
of the Subject line to allow automated sorting.

Abstract


  This document specifies a Canonical Cache Representation (CCR)
  content type for use with the Resource Public Key Infrastructure
  (RPKI).  CCR is a Distinguished Encoding Rules (DER) encoded data
  interchange format which can be used to represent various aspects of
  the state of a validated RPKI cache at a particular point in time.
  The CCR profile is a compact and versatile format, well-suited for a
  variety of applications, for example, audit trails, analytics
  pipelines, and validated payload dissemination.




The file can be obtained via
https://datatracker.ietf.org/doc/draft-ietf-sidrops-rpki-ccr/



No IPR declarations have been submitted directly on this I-D.


The document contains these normative downward references.
See RFC 3967 for additional information:
    draft-ietf-sidrops-aspa-profile: A Profile for Autonomous System Provider Authorization (None - Internet Engineering Task Force (IETF) stream)



2026-06-03
08 Morgan Condie IESG state changed to In Last Call from Last Call Requested
2026-06-03
08 Barry Leiba Request for IETF Last Call review by ARTART is assigned to Darrel Miller
2026-06-03
08 Mohamed Boucadair Requested IETF Last Call review by ARTART
2026-06-03
08 Mohamed Boucadair Requested IETF Last Call review by RTGDIR
2026-06-03
08 Mohamed Boucadair Requested IETF Last Call review by SECDIR
2026-06-03
08 Mohamed Boucadair Last call was requested
2026-06-03
08 Mohamed Boucadair Last call announcement was generated
2026-06-03
08 Mohamed Boucadair Ballot approval text was generated
2026-06-03
08 Mohamed Boucadair Ballot writeup was generated
2026-06-03
08 Mohamed Boucadair IESG state changed to Last Call Requested from AD Evaluation::AD Followup
2026-06-03
08 Mohamed Boucadair
AD review addressed.

On the point about the ambiguity about handling CCR files with ordering not followed: whether this is considered as invalid or tolerated …
AD review addressed.

On the point about the ambiguity about handling CCR files with ordering not followed: whether this is considered as invalid or tolerated by readers: the authors clarified this is invalid, but not explicit mention was added to the spec. See more at: https://mailarchive.ietf.org/arch/msg/sidrops/z_mx89wgc94hnEzYM4oTi9fOdiY/.
2026-06-03
08 (System) Changed action holders to Mohamed Boucadair (IESG state changed)
2026-06-03
08 (System) Sub state has been changed to AD Followup from Revised I-D Needed
2026-06-03
08 Job Snijders New version available: draft-ietf-sidrops-rpki-ccr-08.txt
2026-06-03
08 Job Snijders New version accepted (logged-in submitter: Job Snijders)
2026-06-03
08 Job Snijders Uploaded new revision
2026-06-01
07 Mohamed Boucadair AD Review: https://mailarchive.ietf.org/arch/msg/sidrops/yLTgns2DnaLt3jyRFq59ORMYvME/
2026-06-01
07 (System) Changed action holders to Job Snijders, Bart Bakker, Tim Bruijnzeels, Theo Buehler (IESG state changed)
2026-06-01
07 Mohamed Boucadair IESG state changed to AD Evaluation::Revised I-D Needed from AD Evaluation
2026-05-31
07 Mohamed Boucadair Changed document external resources from: None to:

github_repo https://github.com/job/draft-sidrops-rpki-ccr
2026-05-31
07 Mohamed Boucadair IESG state changed to AD Evaluation from Publication Requested
2026-05-30
07 Russ Housley
Shepherd Write-up for draft-ietf-sidrops-rpki-ccr-07

# Document History

1.  Does the working group (WG) consensus represent the strong concurrence of a
    few individuals, with …
Shepherd Write-up for draft-ietf-sidrops-rpki-ccr-07

# Document History

1.  Does the working group (WG) consensus represent the strong concurrence of a
    few individuals, with others being silent, or did it reach broad agreement?

    There is consensus for this document.

2.  Was there controversy about particular points, or were there decisions where
    the consensus was particularly rough?

    There was no significant controversy, and suggestions for improvement were
    readily accepted by the authors.

3.  Has anyone threatened an appeal or otherwise indicated extreme discontent? If
    so, please summarize the areas of conflict in separate email messages to the
    responsible Area Director. (It should be in a separate email because this
    questionnaire is publicly available.)

    No one has threatened an appeal.

4.  For protocol documents, are there existing implementations of the contents of
    the document? Have a significant number of potential implementers indicated
    plans to implement? Are any existing implementations reported somewhere,
    either in the document itself (as RFC 7942 recommends) or elsewhere
    (where)?

    Appendix c shows implementation experience.  Appendix C will be dropped by
    the RFC Editor.

# Additional Reviews

5.  Do the contents of this document closely interact with technologies in other
    IETF working groups or external organizations, and would it therefore benefit
    from their review? Have those reviews occurred? If yes, describe which
    reviews took place.

    No external review is needed.

6.  Describe how the document meets any required formal expert review criteria,
    such as the MIB Doctor, YANG Doctor, media type, and URI type reviews.

    No special reviews are needed.

7.  If the document contains a YANG module, has the final version of the module
    been checked with any of the recommended validation tools for syntax and
    formatting validation? If there are any resulting errors or warnings, what is
    the justification for not fixing them at this time? Does the YANG module
    comply with the Network Management Datastore Architecture (NMDA) as specified
    in RFC 8342?

    YANG is not used in this document.

8.  Describe reviews and automated checks performed to validate sections of the
    final version of the document written in a formal language, such as XML code,
    BNF rules, MIB definitions, CBOR's CDDL, etc.

    This document uses ASN.1.  After inserting a placeholder module identifier,
    the ASN.1 module compiles without error.

# Document Shepherd Checks

9. Based on the shepherd's review of the document, is it their opinion that this
    document is needed, clearly written, complete, correctly designed, and ready
    to be handed off to the responsible Area Director?

    Yes, the document is ready, clear, and complete.  The document shepherd did
    a thorough review of the document as part of WG Last Call.  All issues that
    were raised during WG Last Call have been resolved.

10. Several IETF Areas have assembled lists of common issues that their
    reviewers encounter. For which areas have such issues been identified
    and addressed? For which does this still need to happen in subsequent
    reviews?

    No concerns.

11. What type of RFC publication is being requested on the IETF stream (Best
    Current Practice, Proposed Standard, Internet Standard,
    Informational, Experimental or Historic)? Why is this the proper type
    of RFC? Do all Datatracker state attributes correctly reflect this intent?

    Proposed Standard.  Yes, the header calls for a Standards Track RFC, and
    this is reflected in the Datatracker.

12. Have reasonable efforts been made to remind all authors of the intellectual
    property rights (IPR) disclosure obligations described in BCP 79? To
    the best of your knowledge, have all required disclosures been filed? If
    not, explain why. If yes, summarize any relevant discussion, including links
    to publicly-available messages when applicable.

    The authors have explicitly stated that they are unaware of any IPR
    related with the document.

    No IPR disclosures were issued against this document.

13. Has each author, editor, and contributor shown their willingness to be
    listed as such? If the total number of authors and editors on the front
    page is greater than five, please provide a justification.

    Yes, each author has stated their willingness to be listed.

14. Document any remaining I-D nits in this document. Simply running the
    IDnits tool is not enough; please review the "Content Guidelines" on
    authors.ietf.org. (Also note that the current idnits tool generates
    some incorrect warnings; a rewrite is underway.)

    IDnits complains about a non-ASCII character, which is part of the
    [CRDT] reference.  This is not a concern.

    IDnits complains that the document has examples using IPv4 documentation
    addresses, but it does not use any IPv6 documentation addresses; however,
    Appendix B has a complete example that uses both IPv4 and IPv6 addresses
    from live Internet traffic.

    IDnits complains about an unused reference to [RFC6268], which is not
    correct.  The ASN.1 module imports some definitions from [RFC6268].

    IDnits raises a concern about a possible downref for [SHS], which is not
    correct.  [SHS] has been published by US NIST.

15. Should any informative references be normative or vice-versa? See the IESG
    Statement on Normative and Informative References.

    No concerns.

16. List any normative references that are not freely available to anyone.
    Did the community have sufficient access to review any such normative
    references?

    All normative references are RFCs, which are, of course, freely available.

17. Are there any normative downward references (see RFC 3967 and BCP 97)
    that are not already listed in the DOWNREF registry? If so, list them.

    There are no downward normative references.

18. Are there normative references to documents that are not ready to be
    submitted to the IESG for publication or are otherwise in an unclear
    state? If so, what is the plan for their completion?

    One normative reference has not yet been published.  That document is
    in WG Last Call, and it should be with the IESG shortly.

19. Will publication of this document change the status of any existing RFCs?
    If so, does the Datatracker metadata correctly reflect this and are those
    RFCs listed on the title page, in the abstract, and discussed in the
    introduction? If not, explain why and point to the part of the document
    where the relationship of this document to these other RFCs is discussed.

    No document status changes.

20. Describe the document shepherd's review of the IANA considerations section,
    especially with regard to its consistency with the body of the document.
    Confirm that all aspects of the document requiring IANA assignments are
    associated with the appropriate reservations in IANA registries. Confirm
    that any referenced IANA registries have been clearly identified. Confirm
    that each newly created IANA registry specifies its initial contents,
    allocations procedures, and a reasonable name (see RFC 8126).

    First, IANA has already allocated one object identifier in the
    "SMI Security for S/MIME CMS Content Type (1.2.840.113549.1.9.16.1)"
    registry.  The allocation of id-ct-rpkiCanonicalCacheRepresentation
    was necessary for interoperable implementations.

    Second, IANA is requested to add the Canonical Cache Representation file
    extension (".ccr") to the "RPKI Repository Name Schemes" registry.

    Third, IANA is requested to allocate one object identifier in the
    "SMI Security for S/MIME Module Identifier (1.2.840.113549.1.9.16.0)"
    registry for the ASN.1 module in this document.

    Fourth, IANA is requested to register two media types:
    "application/rpki-ccr" and "application/rpki-ccr+gzip".
    The document authors have started a thread on media-types@iana.org
    to discuss these registrations.

21. List any new IANA registries that require Designated Expert Review for
    future allocations. Are the instructions to the Designated Expert clear?
    Please include suggestions of designated experts, if appropriate.

    None are needed.
2026-05-30
07 Russ Housley IETF WG state changed to Submitted to IESG for Publication from WG Consensus: Waiting for Write-Up
2026-05-30
07 Russ Housley IESG state changed to Publication Requested from I-D Exists
2026-05-30
07 (System) Changed action holders to Mohamed Boucadair (IESG state changed)
2026-05-30
07 Russ Housley Responsible AD changed to Mohamed Boucadair
2026-05-30
07 Russ Housley Document is now in IESG state Publication Requested
2026-05-30
07 Russ Housley Notification list changed to housley@vigilsec.com because the document shepherd was set
2026-05-30
07 Russ Housley Document shepherd changed to Russ Housley
2026-05-30
07 Russ Housley
Shepherd Write-up for draft-ietf-sidrops-rpki-ccr-07

# Document History

1.  Does the working group (WG) consensus represent the strong concurrence of a
    few individuals, with …
Shepherd Write-up for draft-ietf-sidrops-rpki-ccr-07

# Document History

1.  Does the working group (WG) consensus represent the strong concurrence of a
    few individuals, with others being silent, or did it reach broad agreement?

    There is consensus for this document.

2.  Was there controversy about particular points, or were there decisions where
    the consensus was particularly rough?

    There was no significant controversy, and suggestions for improvement were
    readily accepted by the authors.

3.  Has anyone threatened an appeal or otherwise indicated extreme discontent? If
    so, please summarize the areas of conflict in separate email messages to the
    responsible Area Director. (It should be in a separate email because this
    questionnaire is publicly available.)

    No one has threatened an appeal.

4.  For protocol documents, are there existing implementations of the contents of
    the document? Have a significant number of potential implementers indicated
    plans to implement? Are any existing implementations reported somewhere,
    either in the document itself (as RFC 7942 recommends) or elsewhere
    (where)?

    Appendix c shows implementation experience.  Appendix C will be dropped by
    the RFC Editor.

# Additional Reviews

5.  Do the contents of this document closely interact with technologies in other
    IETF working groups or external organizations, and would it therefore benefit
    from their review? Have those reviews occurred? If yes, describe which
    reviews took place.

    No external review is needed.

6.  Describe how the document meets any required formal expert review criteria,
    such as the MIB Doctor, YANG Doctor, media type, and URI type reviews.

    No special reviews are needed.

7.  If the document contains a YANG module, has the final version of the module
    been checked with any of the recommended validation tools for syntax and
    formatting validation? If there are any resulting errors or warnings, what is
    the justification for not fixing them at this time? Does the YANG module
    comply with the Network Management Datastore Architecture (NMDA) as specified
    in RFC 8342?

    YANG is not used in this document.

8.  Describe reviews and automated checks performed to validate sections of the
    final version of the document written in a formal language, such as XML code,
    BNF rules, MIB definitions, CBOR's CDDL, etc.

    This document uses ASN.1.  After inserting a placeholder module identifier,
    the ASN.1 module compiles without error.

# Document Shepherd Checks

9. Based on the shepherd's review of the document, is it their opinion that this
    document is needed, clearly written, complete, correctly designed, and ready
    to be handed off to the responsible Area Director?

    Yes, the document is ready, clear, and complete.  The document shepherd did
    a thorough review of the document as part of WG Last Call.  All issues that
    were raised during WG Last Call have been resolved.

10. Several IETF Areas have assembled lists of common issues that their
    reviewers encounter. For which areas have such issues been identified
    and addressed? For which does this still need to happen in subsequent
    reviews?

    No concerns.

11. What type of RFC publication is being requested on the IETF stream (Best
    Current Practice, Proposed Standard, Internet Standard,
    Informational, Experimental or Historic)? Why is this the proper type
    of RFC? Do all Datatracker state attributes correctly reflect this intent?

    Proposed Standard.  Yes, the header calls for a Standards Track RFC, and
    this is reflected in the Datatracker.

12. Have reasonable efforts been made to remind all authors of the intellectual
    property rights (IPR) disclosure obligations described in BCP 79? To
    the best of your knowledge, have all required disclosures been filed? If
    not, explain why. If yes, summarize any relevant discussion, including links
    to publicly-available messages when applicable.

    The authors have explicitly stated that they are unaware of any IPR
    related with the document.

    No IPR disclosures were issued against this document.

13. Has each author, editor, and contributor shown their willingness to be
    listed as such? If the total number of authors and editors on the front
    page is greater than five, please provide a justification.

    Yes, each author has stated their willingness to be listed.

14. Document any remaining I-D nits in this document. Simply running the
    IDnits tool is not enough; please review the "Content Guidelines" on
    authors.ietf.org. (Also note that the current idnits tool generates
    some incorrect warnings; a rewrite is underway.)

    IDnits complains about a non-ASCII character, which is part of the
    [CRDT] reference.  This is not a concern.

    IDnits complains that the document has examples using IPv4 documentation
    addresses, but it does not use any IPv6 documentation addresses; however,
    Appendix B has a complete example that uses both IPv4 and IPv6 addresses
    from live Internet traffic.

    IDnits complains about an unused reference to [RFC6268], which is not
    correct.  The ASN.1 module imports some definitions from [RFC6268].

    IDnits raises a concern about a possible downref for [SHS], which is not
    correct.  [SHS] has been published by US NIST.

15. Should any informative references be normative or vice-versa? See the IESG
    Statement on Normative and Informative References.

    No concerns.

16. List any normative references that are not freely available to anyone.
    Did the community have sufficient access to review any such normative
    references?

    All normative references are RFCs, which are, of course, freely available.

17. Are there any normative downward references (see RFC 3967 and BCP 97)
    that are not already listed in the DOWNREF registry? If so, list them.

    There are no downward normative references.

18. Are there normative references to documents that are not ready to be
    submitted to the IESG for publication or are otherwise in an unclear
    state? If so, what is the plan for their completion?

    One normative reference has not yet been published.  That document is
    in WG Last Call, and it should be with the IESG shortly.

19. Will publication of this document change the status of any existing RFCs?
    If so, does the Datatracker metadata correctly reflect this and are those
    RFCs listed on the title page, in the abstract, and discussed in the
    introduction? If not, explain why and point to the part of the document
    where the relationship of this document to these other RFCs is discussed.

    No document status changes.

20. Describe the document shepherd's review of the IANA considerations section,
    especially with regard to its consistency with the body of the document.
    Confirm that all aspects of the document requiring IANA assignments are
    associated with the appropriate reservations in IANA registries. Confirm
    that any referenced IANA registries have been clearly identified. Confirm
    that each newly created IANA registry specifies its initial contents,
    allocations procedures, and a reasonable name (see RFC 8126).

    First, IANA has already allocated one object identifier in the
    "SMI Security for S/MIME CMS Content Type (1.2.840.113549.1.9.16.1)"
    registry.  The allocation of id-ct-rpkiCanonicalCacheRepresentation
    was necessary for interoperable implementations.

    Second, IANA is requested to add the Canonical Cache Representation file
    extension (".ccr") to the "RPKI Repository Name Schemes" registry.

    Third, IANA is requested to allocate one object identifier in the
    "SMI Security for S/MIME Module Identifier (1.2.840.113549.1.9.16.0)"
    registry for the ASN.1 module in this document.

    Fourth, IANA is requested to register two media types:
    "application/rpki-ccr" and "application/rpki-ccr+gzip".
    The document authors have started a thread on media-types@iana.org
    to discuss these registrations.

21. List any new IANA registries that require Designated Expert Review for
    future allocations. Are the instructions to the Designated Expert clear?
    Please include suggestions of designated experts, if appropriate.

    None are needed.
2026-05-28
07 Russ Housley Tag Revised I-D Needed - Issue raised by WGLC cleared.
2026-05-28
07 Russ Housley IETF WG state changed to WG Consensus: Waiting for Write-Up from Waiting for WG Chair Go-Ahead
2026-05-28
07 Job Snijders New version available: draft-ietf-sidrops-rpki-ccr-07.txt
2026-05-28
07 Job Snijders New version accepted (logged-in submitter: Job Snijders)
2026-05-28
07 Job Snijders Uploaded new revision
2026-05-28
06 Russ Housley Intended Status changed to Proposed Standard from None
2026-05-28
06 Russ Housley Changed consensus to Yes from Unknown
2026-05-28
06 Russ Housley Tag Revised I-D Needed - Issue raised by WGLC set.
2026-05-28
06 Russ Housley IETF WG state changed to Waiting for WG Chair Go-Ahead from In WG Last Call
2026-05-27
06 Job Snijders New version available: draft-ietf-sidrops-rpki-ccr-06.txt
2026-05-27
06 Job Snijders New version accepted (logged-in submitter: Job Snijders)
2026-05-27
06 Job Snijders Uploaded new revision
2026-05-18
05 Job Snijders New version available: draft-ietf-sidrops-rpki-ccr-05.txt
2026-05-18
05 (System) New version approved
2026-05-18
05 (System) Request for posting confirmation emailed to previous authors: Bart Bakker , Job Snijders , Theo Buehler , Tim Bruijnzeels
2026-05-18
05 Job Snijders Uploaded new revision
2026-05-12
04 Russ Housley IETF WG state changed to In WG Last Call from WG Document
2026-05-06
04 Job Snijders New version available: draft-ietf-sidrops-rpki-ccr-04.txt
2026-05-06
04 Job Snijders New version accepted (logged-in submitter: Job Snijders)
2026-05-06
04 Job Snijders Uploaded new revision
2026-04-14
03 Job Snijders New version available: draft-ietf-sidrops-rpki-ccr-03.txt
2026-04-14
03 Job Snijders New version accepted (logged-in submitter: Job Snijders)
2026-04-14
03 Job Snijders Uploaded new revision
2026-03-10
02 Luigi Iannone Added to session: IETF-125: sidrops  Thu-0600
2025-12-04
02 Job Snijders New version available: draft-ietf-sidrops-rpki-ccr-02.txt
2025-12-04
02 Job Snijders New version accepted (logged-in submitter: Job Snijders)
2025-12-04
02 Job Snijders Uploaded new revision
2025-12-02
01 Job Snijders New version available: draft-ietf-sidrops-rpki-ccr-01.txt
2025-12-02
01 Job Snijders New version accepted (logged-in submitter: Job Snijders)
2025-12-02
01 Job Snijders Uploaded new revision
2025-12-01
00 Luigi Iannone This document now replaces draft-spaghetti-sidrops-rpki-ccr instead of None
2025-12-01
00 Job Snijders New version available: draft-ietf-sidrops-rpki-ccr-00.txt
2025-12-01
00 Luigi Iannone WG -00 approved
2025-12-01
00 Job Snijders Set submitter to "Job Snijders ", replaces to draft-spaghetti-sidrops-rpki-ccr and sent approval email to group chairs: sidrops-chairs@ietf.org
2025-12-01
00 Job Snijders Uploaded new revision