Re: [CCAMP] [RTG-DIR] RtgDir review: draft-ietf-ccamp-general-constraint-encode-16.txt

Leeyoung <> Mon, 19 January 2015 22:54 UTC

Return-Path: <>
Received: from localhost ( []) by (Postfix) with ESMTP id 2BB4A1B2D13; Mon, 19 Jan 2015 14:54:35 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -3.21
X-Spam-Status: No, score=-3.21 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HK_RANDOM_ENVFROM=0.001, HK_RANDOM_FROM=1, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id YKCfPflU-jON; Mon, 19 Jan 2015 14:54:32 -0800 (PST)
Received: from ( []) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 011B31B2D0A; Mon, 19 Jan 2015 14:54:30 -0800 (PST)
Received: from (EHLO ([]) by (MOS 4.3.7-GA FastPath queued) with ESMTP id BRN15525; Mon, 19 Jan 2015 22:54:29 +0000 (GMT)
Received: from ( by ( with Microsoft SMTP Server (TLS) id; Mon, 19 Jan 2015 22:54:28 +0000
Received: from ([]) by dfweml702-chm ([]) with mapi id 14.03.0158.001; Mon, 19 Jan 2015 14:54:19 -0800
From: Leeyoung <>
To: Tomonori Takeda <>, "" <>
Thread-Topic: [RTG-DIR] RtgDir review: draft-ietf-ccamp-general-constraint-encode-16.txt
Thread-Index: AdAyVmdKICzu0mt5SZ+spYC7d3T1cAB2eNGw
Date: Mon, 19 Jan 2015 22:54:18 +0000
Message-ID: <7AEB3D6833318045B4AE71C2C87E8E1729C7B111@dfweml706-chm>
References: <>
In-Reply-To: <>
Accept-Language: en-US
Content-Language: en-US
x-originating-ip: []
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <>
Cc: "''" <>, "''" <>, "''" <>
Subject: Re: [CCAMP] [RTG-DIR] RtgDir review: draft-ietf-ccamp-general-constraint-encode-16.txt
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Discussion list for the CCAMP working group <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Mon, 19 Jan 2015 22:54:35 -0000

Hi Tomonori,

Thanks for providing good comments. Here's my response. Please see in-line.


-----Original Message-----
From: rtg-dir [] On Behalf Of Tomonori Takeda
Sent: Saturday, January 17, 2015 7:59 AM
Cc: ''org'; ''org'; ''
Subject: [RTG-DIR] RtgDir review: draft-ietf-ccamp-general-constraint-encode-16.txt


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 ​ 

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-general-constraint-encode-16.txt 
Reviewer: Tomonori Takeda
Review Date: 17 January, 2015
IETF LC End Date: 17 January, 2015
Intended Status: Standards Track


This document is basically ready for publication, but has nits that should be considered prior to publication.


This document specifies protocol-agnostic encodings for general information elements described in draft-ietf-ccamp-rwa-info.
I think the document is in good shape but there are a few points that should be clarified for better understanding.

Major Issues:


Minor Issues:



1) In section 1.2, label continuity constraint (e.g., wavelength continuity in WSON) is mentioned. However, I am not sure whether information elements for which this document specifies encodings can describe such constraint. My reading is that information element such as Port Label Restriction is rather for describing wavelength tuning capabilities/restrictions.

YOUNG>> Label continuity constraints can be inferred from the two places in the draft: (i) Port Label Restriction, which gives the set of labels (wavelengths) that may not be available on certain links including tuning range/restriction; (ii) Available/Shared Backup Label Fields (section 2.4 & section 2.5). There is no encoding for label continuity constraint per se. The aforementioned constraints are encoded to give a node or a PCE to be able to compute a path (i.e., path with wavelength continuity) subject to these constraints. 

2) In section 2.1, it says "two matrices will not have the same {src port, src label, dst port, dst label}". To be precise, I guess this should be "two matrices will not have the same {src port, src label}, and two matrices will not have the same {dst port, dst label}"?

YOUNG>> I think your suggestion may be too restrictive. For instance, if we have one source (port 1) and one destination (port 2) with two labels each. Then we would have: {(1,1,2,1), (1,1,2,2), (1,2,2,1), (1,2,2,2)} I think with the current statement, we can send this info in any combination of multiple matrices, which I think perfectly fine. With your suggestion, I would not be able send (1,1,2,1) and (1,1,2,2) together. Why would this not be made possible? My take is as long as each submatrix represents a set of disjoint quadruples, that should be allowed. 

3) In section 2.1, it says "The value of 0xFF is reserved for use with port wavelength constraints". I think "port wavelength constraints" should be "port label restriction".

YOUNG>> Yes, thanks. 

4) In section 2.1, for Link Set A dir=bidirectional, Link Set B dir=bidirectional, if any signal on an input link X is output on a link Y, then any signal on an input link Y is output on a link X (after cross-connect)? Or any constraint on such signal flow (after cross-connect) is out of scope?

YOUNG>> I am not sure what "after cross-connect" is meant. 

5) In section 2.2.1, it says "In this case the accompanying label set indicates the labels permitted on the port." I think "port" should be "port/matrix".

YOUNG>> Yes, thanks. 

6) In section 2.2.2, it would be better to describe the type (e.g., integer) for MaxNumChannels.
This also applies for MaxLabelRange (in section 2.2.3) and Num Labels (in section 2.6).


7) In section 2.6, it says "Label Set Field is used within the <AvailableLabels> or the <SharedBackupLabels>". But I think Label Set Field is also used within SIMPLE_LABEL, LABEL_RANGE and SIMPLE_LABEL & CHANNEL_COUNT.

YOUNG>> Yes, it is used in multiple places. 

How about:
OLD: Label Set Field is used within the <AvailableLabels> or the
   <SharedBackupLabels>, which is defined in Section 2.4. and 2.5.,
NEW: Label Set Field is used within the <AvailableLabels> or the
   <SharedBackupLabels>, which is defined in Section 2.4. and 2.5.,
   respectively. It is also used within the <SIMPLE_LABEL>, 
   <LABEL_RANGE>, <SIMPLE_LABEL> or <CHANNEL_COUNT>, which is defined
   in Sections 2.1.1 - 2.1.4, respectively.