[RTG-DIR] RtgDir review: draft-ietf-ccamp-gmpls-g-694-lambda-labels-10.txt

[Tomonori TAKEDA <[e-mail]>]

Hello,

I have been selected as the Routing Directorate reviewer for this draft.
The Routing Directorate seeks to review all routing or routing-related
drafts as they pass through IETF last call and IESG review. The purpose
of the review is to provide assistance to the Routing ADs. For more
information about the Routing Directorate, please see
http://www.ietf.org/iesg/directorate/routing.html

Although these comments are primarily for the use of the Routing ADs, it
would be helpful if you could consider them along with any other IETF
Last Call comments that you receive, and strive to resolve them through
discussion or by updating the draft.

Document: draft-ietf-ccamp-gmpls-g-694-lambda-labels-10.txt
Reviewer: Tomonori Takeda
Review Date: 28 December 2010
IETF LC End Date: Unknown
Intended Status: Standards Track


Summary:
I have some minor concerns about this document that I think should be
resolved before publication.


Comments:
This document is well written and easy to read. I have several nits and
one minor question.


Major Issues:
No major issues found.


Minor Issues:

Section 3.2 (and Section 3.3):
Text on the identifier field is a bit hard to understand.
- In the abstract, it says that the label format defined in this
  document can be used in GMPLS signaling and routing protocols.
  However, it seems that text from Section 3.2 (3) Identifier applies to
  signaling only. Does it mean that Identifier field is set to zero when
  used in routing, and set to a value according to Section 3.2 (3)
  Identifier when used in signaling?
- I can not simply understand text regarding use of identifier in a
  label ERO subobject. Does it mean that when non-zero value is assigned
  to the identifier field in a label ERO subobject, the referenced node
  MUST use the assigned value for the identifier field in the
  corresponding LSP related messages? (e.g., the referenced node MUST
  use the assigned value for the identifier field in a Label object in
  Resv message?)


Nits:

Section 3.1, 3rd paragraph:
s/standardize/standardized

-- 
Tomonori TAKEDA
NTT Network Service Systems Lab.
Phone: [phone]