[CCAMP] R: RtgDir review: draft-ietf-ccamp-otn-g709-info-model-11.txt

Hello Joel,

thanks for your comments.
Below in line our reply, marked "authors".

Best Regards

The authors

Belotti Sergio-  System Architect
ALCATE-LUCENT  Optics Division
via Trento 30 Vimercate (MB) - Italy
phone +39 (039) 6863033
-----Messaggio originale-----
Da: ccamp-bounces@ietf.org [mailto:ccamp-bounces@ietf.org] Per conto di Joel M. Halpern
Inviato: lunedì 9 settembre 2013 14:15
A: rtg-ads@tools.ietf.org; rtg-dir@ietf.org; draft-ietf-ccamp-otn-g709-info-model.all@tools.ietf.org; CCAMP WG
Oggetto: [CCAMP] RtgDir review: draft-ietf-ccamp-otn-g709-info-model-11.txt

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, and sometimes on special request. 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-otn-g709-info-model-11.txt
Reviewer: Joel Halpern
Review Date: 9-September-2013
IETF LC End Date: 19-Sept-2013
Intended Status: Informational

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

Comments:
     In general, the document needs to be consistently clear as to what gaps it identifies.  Many cases are quite clear, and some are not.  I will try to identify the less clear cases in the comments below. The last paragraph of section 3.2 is clear and explicit, and what I expected at the end of each section.  The previous paragraph ("Specific information could be defined") is much less helpful.

Moderate Issues:
     It is unclear if there are gaps or requirements identified by sections 3.1.1 or 3.1.2.

Authors> The scope of both paragraph are not to suggest gaps or requirements but to describe data plane characteristics that are useful in the follow of the doc. Particularly they introduce the relationship between payload type concept in OTN and the Tributary Slot granularity, and this relation is reported in the session 3.2 in which specific CP requirements are defined.

     Given that this document is about mapping to G.709, it is unclear what is intended by the usage of "LSP".  My guess is that it is intended to mean Label Switch Paths set up by GMPLS to carry OTU/UDU elements. 
It should be stated explicitly.

Authors> We can specify this as you suggest even if we considered not necessary to specify the usage of LSP in relation to data plane specific. Encoding type should cope with this issue. 

Minor Issues:
     All acronyms should be expanded upon first use.

Authors> OK

     In section 2 particularly, the OCh (Optical Channel?) should also be clear how that relates to the OTU and ODU being discussed.

Authors> OK, you're right

     Figure 4 uses the abbreviation TSG, which is not defined, and not used elsewhere.  If it is needed in the figure, it might suffice to follow "TS granularity" in the caption with "(TSG)".

Authors> We can add TSG at the beginning of chapter 3.2 when TS granularity is mentioned

     Section 8 on Maximum LSP Bandwdith seems to be objecting to too much information leading to a "waste of bits".  While possibly of interest to the WG, that does not seem to fit a gap analysis.
     Similarly, section 10 on Priority Support reads as implementation advice rather than a gap needing protocol changes.

Authors> The basic scope of the draft is to underline gaps, and even if what described in Ch.8 and 10, do not prevent routing to work , it is suggested here an requirement for optimization based on OTN requirements (e.g. no need to advertise fixed ODU container Max LSP BW since implicit in the signal type.)

Nit:

_______________________________________________
CCAMP mailing list
CCAMP@ietf.org
https://www.ietf.org/mailman/listinfo/ccamp