Last Call Review of draft-ietf-ccamp-flexigrid-lambda-label-04
review-ietf-ccamp-flexigrid-lambda-label-04-opsdir-lc-pignataro-2015-09-11-00

Request Review of draft-ietf-ccamp-flexigrid-lambda-label
Requested rev. no specific revision (document currently at 05)
Type Last Call Review
Team Ops Directorate (opsdir)
Deadline 2015-09-15
Requested 2015-09-01
Draft last updated 2015-09-11
Completed reviews Genart Last Call review of -04 by Robert Sparks (diff)
Genart Telechat review of -05 by Robert Sparks
Secdir Last Call review of -04 by Paul Wouters (diff)
Opsdir Last Call review of -04 by Carlos Pignataro (diff)

Assignments

Review
review-ietf-ccamp-flexigrid-lambda-label-04-opsdir-lc-pignataro-2015-09-11

Hi!

I have reviewed this document as part of the Operational directorate's ongoing effort to review all IETF documents being processed by the IESG.  These comments were written with the intent of improving the operational aspects of the IETF drafts. Comments that are not addressed in last call may be included in AD reviews during the IESG review.  Document editors and WG chairs should treat these comments just like any other last call comments.

This document is on the Standards Track, and defines a new GMPLS lambda label format in support of Flexi-Grid.

This document is very well written, comprehensive, and complete — thank you! In particular, thank you for adding the Manageability Considerations section!

Summary: Ready with questions.

Major:

None.


Minor:

This document says it updates RFC 3471 and RFC 6205. It is not totally clear to me how it is updating those RFCs. In general, defining a new feature or format (e.g., new label encoding) creates a Normative dependency, not an Updates. In particular, when a document updates another one, I believe that a Section should be added explaining exactly what is updated (ideally with OLD/NEW text format). Even less so I see the update to RFC 3471 by this document.

Could the exact details of what is updated be explained, and explicitly added to the doc.


Nits:

Section 1: s/Packet Switching Capable (PSC)/Packet Switch Capable (PSC)/ (according to RFC 3471)


Hope these help,

— Carlos.

_______________________________________________
OPS-DIR mailing list
OPS-DIR at ietf.org


https://www.ietf.org/mailman/listinfo/ops-dir




Attachment:


signature.asc




Description:

 Message signed with OpenPGP using GPGMail