Skip to main content

Early Review of draft-ietf-sidrops-aspa-verification-26
review-ietf-sidrops-aspa-verification-26-genart-early-yee-2026-07-20-00

Request Review of draft-ietf-sidrops-aspa-verification
Requested revision No specific revision (document currently at 27)
Type Early Review
Team General Area Review Team (Gen-ART) (genart)
Deadline 2026-07-19
Requested 2026-07-07
Requested by Jean Mahoney
Authors Alexander Azimov , Eugene Bogomazov , Randy Bush , Keyur Patel , Job Snijders , Kotikalapudi Sriram
I-D last updated 2026-08-03 (Latest revision 2026-07-20)
Completed reviews Genart Early review of -26 by Peter E. Yee (diff)
Comments
From the original request made by Luigi Iannone:

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.
Assignment Reviewer Peter E. Yee
State Completed
Request Early review on draft-ietf-sidrops-aspa-verification by General Area Review Team (Gen-ART) Assigned
Posted at https://mailarchive.ietf.org/arch/msg/gen-art/ZKvd_UNYmkP-SNx7ghNPePu-wzk
Reviewed revision 26 (document currently at 27)
Result Ready w/nits
Completed 2026-07-20
review-ietf-sidrops-aspa-verification-26-genart-early-yee-2026-07-20-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-aspa-profile-27
Reviewer: Peter Yee
Review Date: 2026-07-19
IETF LC End Date:
IESG Telechat date: Not scheduled for a telechat

Summary:

This draft describes how ASPA objects are used to detect and mitigate certain
route leaks and BGP AS_PATH trickery. The document is well written. Given my
lack of deep routing knowledge, I can only say I believe it does what’s
claimed. There are few minor nits that could be fixed. [Ready with Nits]

Major issues: None

Minor issues: None

Nits/editorial comments:

Page 3, section 1, 1st paragraph, last sentence: change “occur,” to “occur.

Page 4, section 4, 2nd paragraph, 1st sentence: insert “the” before “Provider”.

Page 5, 5th paragraph: change “certificate” to “certification”.

Page 5, section 5, 2nd paragraph, 3rd sentence: expand “IX” on its first use
here.

Page 6, 1st paragraph after Figure 2, 6th sentence: delete “that”.

Page 6, 1st paragraph after Figure 2, 7th sentence: delete “that”.

Page 7, section 5.2, 2nd paragraph, 2nd sentence: change “equals” to “is equal”.

Page 11, section 7.1, 1st paragraph, last sentence: append a comma after “e.g.”.