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 wait for direction from your
document shepherd or AD before posting a new version of the draft.
For more information, please see the FAQ at
<https://wiki.ietf.org/en/group/gen/GenArtFAQ>.
Document: draft-ietf-spring-srv6-security-16
Reviewer: Paul Kyzivat
Review Date: 2026-09-14
IETF LC End Date: 2026-09-17
IESG Telechat date: ???
Summary: This draft is ready for publication as an Informational RFC.
Note: I drew the assignment to do the Gen-Art review of this document.
But I lack the knowledge of routing protocols to meaningfully assess
this subject matter. Superficially it is well structured, and the few
issues raised by IdNits are bogus.
I do have an observation that I don't want to raise to the level of an
Issue:
I find the purpose of this document unclear. It is declared as
Informational, but who is intended to consume this information, and to
what purpose? Another review suggested that this ought to be a BCP. That
would give it a purpose, but then it would probably need to me more
specific in its recommended mitigations. Alternatively, it could be
intended as background for other BCP or normative documents that
elaborate the mitigations. In any case, it would be helpful to be
explicit about the intent.
_______________________________________________
spring mailing list -- [email protected]
To unsubscribe send an email to [email protected]
