IETF Last Call Review of draft-ietf-sidrops-rpki-ccr-08
review-ietf-sidrops-rpki-ccr-08-genart-lc-sarikaya-2026-06-18-00
| Request | Review of | draft-ietf-sidrops-rpki-ccr |
|---|---|---|
| Requested revision | No specific revision (document currently at 11) | |
| Type | IETF Last Call Review | |
| Team | General Area Review Team (Gen-ART) (genart) | |
| Deadline | 2026-06-17 | |
| Requested | 2026-06-03 | |
| Authors | Job Snijders , Bart Bakker , Tim Bruijnzeels , Theo Buehler | |
| I-D last updated | 2026-07-17 (Latest revision 2026-07-01) | |
| Completed reviews |
Secdir IETF Last Call review of -08
by Joseph A. Salowey
(diff)
Genart IETF Last Call review of -08 by Behcet Sarikaya (diff) Rtgdir IETF Last Call review of -08 by Zheng Zhang (diff) |
|
| Assignment | Reviewer | Behcet Sarikaya |
| State | Completed | |
| Request | IETF Last Call review on draft-ietf-sidrops-rpki-ccr by General Area Review Team (Gen-ART) Assigned | |
| Posted at | https://mailarchive.ietf.org/arch/msg/gen-art/e1GMJ1Fe70mXT3xVM3iNdnQrwy8 | |
| Reviewed revision | 08 (document currently at 11) | |
| Result | Ready w/nits | |
| Completed | 2026-06-18 |
review-ietf-sidrops-rpki-ccr-08-genart-lc-sarikaya-2026-06-18-00
I am the assigned Gen-ART reviewer for this draft. The General Area Review Team (Gen-ART) reviews all IETF documents being processed by the IESG for the IETF Chair. Please treat these comments just like any other last call comments. For more information, please see the FAQ at <https://wiki.ietf.org/en/group/gen/GenArtFAQ>. Document: draft-ietf-sidrops-rpki-ccr-?? Reviewer: Behcet Sarikaya Review Date: 2026-06-18 IETF LC End Date: 2026-06-17 IESG Telechat date: 2026-07-02 Summary: The document defines a DER-encoded data format for RPKI Relying Party software to share validated cache state. The document provides a standardized method for audit trails and analytics by creating a Canonical Cache Representation (CCR). Major issues: Minor issues: Nits/editorial comments: unused refs RFC6268 RFC8792 Section 3.4.4 SHA-1 SHA-1 as a cryptographic algorithm is deprecated and should be phased out by Dec. 31, 2030 I was confused with Section 4.1 Erik protocol but have no comment, can be ignored.