Skip to main content

Early Review of draft-ietf-sidrops-aspa-profile-26
review-ietf-sidrops-aspa-profile-26-secdir-early-salz-2026-06-08-01

Request Review of draft-ietf-sidrops-aspa-profile
Requested revision No specific revision (document currently at 29)
Type Early Review
Team Security Area Directorate (secdir)
Deadline 2026-07-03
Requested 2026-06-05
Requested by Luigi Iannone
Authors Job Snijders , Alexander Azimov , Eugene Uskov , Randy Bush , Russ Housley , Ben Maddison
I-D last updated 2026-08-03 (Latest revision 2026-07-29)
Completed reviews Secdir Early review of -26 by Rich Salz (diff)
Bgpdir Early review of -27 by Srihari R. Sangli (diff)
Artart Early review of -27 by Gavin Brown (diff)
Genart Early review of -27 by Peter E. Yee (diff)
Comments
This document is part of a cluster of documents thightly related, namely:

https://datatracker.ietf.org/doc/draft-ietf-sidrops-aspa-profile/
https://datatracker.ietf.org/doc/draft-ietf-sidrops-8210bis/
https://datatracker.ietf.org/doc/draft-ietf-sidrops-aspa-verification/

If possible, it would make sense that the assigned reviewer for this document is willing to review the other two documents.
The plan is to have early reviews for all the three documents before IETF 126.
Thanks
Assignment Reviewer Rich Salz
State Completed
Request Early review on draft-ietf-sidrops-aspa-profile by Security Area Directorate Assigned
Reviewed revision 26 (document currently at 29)
Result Ready
Completed 2026-06-08
review-ietf-sidrops-aspa-profile-26-secdir-early-salz-2026-06-08-01
I reviewed this document as part of the Security Directorate which tries to
review all drafts. Treat this as any other comments.

I have no technical comments to make. The ASN.1 makes sense, as I would expect,
and the bulk of this documenting is explaining the semantics of the object
fields.  "DEFAULT 0" paired with "must be 1" for the id field is cute.

I don't understand why the "contribution" is a separate section, and not a
separate paragraph in the Acknowledgement.