Skip to main content

Early Review of draft-ietf-mpls-mna-requirements-14
review-ietf-mpls-mna-requirements-14-rtgdir-early-alston-2024-05-24-00

Request Review of draft-ietf-mpls-mna-requirements
Requested revision No specific revision (document currently at 16)
Type Early Review
Team Routing Area Directorate (rtgdir)
Deadline 2024-05-06
Requested 2024-04-22
Requested by Jim Guichard
Authors Matthew Bocci , Stewart Bryant , John Drake
I-D last updated 2024-05-24
Completed reviews Rtgdir Early review of -14 by Andrew Alston (diff)
Secdir Early review of -13 by Dan Harkins (diff)
Genart Last Call review of -13 by Susan Hares (diff)
Rtgdir Early review of -12 by Susan Hares (diff)
Rtgdir Early review of -05 by Sasha Vainshtein (diff)
Assignment Reviewer Andrew Alston
State Completed
Request Early review on draft-ietf-mpls-mna-requirements by Routing Area Directorate Assigned
Posted at https://mailarchive.ietf.org/arch/msg/rtg-dir/R_MSvxNea9zQA71rffuSdOz1-44
Reviewed revision 14 (document currently at 16)
Result Has issues
Completed 2024-05-24
review-ietf-mpls-mna-requirements-14-rtgdir-early-alston-2024-05-24-00
Hello,

I have been selected to do a routing directorate "early" review of
https://datatracker.ietf.org/doc/draft-ietf-mpls-mna-requirements/

While this was originally specified as an early review, following conversations
with the relevant AD, I have treated this as a last call review.

Reviewer: Andrew Alston
Review Date: 24/05/2024
Intended Status: Informational (See comments section)

Summary:

No issues found, the document is ready to proceed to the IESG - with an
important caveat as mentioned below.

Comments:

I found the document to be well written and easy to understand, and well as
being comprehensive in nature. I have concerns however about the intended
status of this document.  Has the working group considered making this document
standards track rather than informational. My rationale for asking this
question is founded in the amount of normative language in the document.  This
document will obviously feed into other standards track future documents, that
MUST conform to what this document lays out, as such, this document almost
becomes a standards document by which other standards are to be authored - and
is far more than just an informational document.  It is rare to see a document
with this amount of normative language in an informational context, as such, at
minimum, I believe that if this discussion has not happened on the mailing
list, it should occur and there needs to be a fairly comprehensive writeup in
the shepards review as to a justification of track.

Beyond that, thank you for the document - as stated I found it well written and
clear.