[CCAMP] Final Text ITU-T Liaison flexi-grid // Was: Draft Text for ITU-T - CCAMP Liason regarding Flexi-grid

Ramon Casellas <ramon.casellas@cttc.es> Thu, 20 March 2014 07:21 UTC

Return-Path: <ramon.casellas@cttc.es>
X-Original-To: ccamp@ietfa.amsl.com
Delivered-To: ccamp@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com []) by ietfa.amsl.com (Postfix) with ESMTP id AD4F11A0069 for <ccamp@ietfa.amsl.com>; Thu, 20 Mar 2014 00:21:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001] autolearn=ham
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id 9cIaZHOCHsZI for <ccamp@ietfa.amsl.com>; Thu, 20 Mar 2014 00:21:33 -0700 (PDT)
Received: from torres.puc.rediris.es (torres.puc.rediris.es [IPv6:2001:720:418:ca00::22]) by ietfa.amsl.com (Postfix) with ESMTP id 551F91A03DF for <ccamp@ietf.org>; Thu, 20 Mar 2014 00:21:32 -0700 (PDT)
Received: from [] (helo=leo) by torres.puc.rediris.es with esmtpsa (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.72) (envelope-from <ramon.casellas@cttc.es>) id 1WQXHs-0003VY-Iy; Thu, 20 Mar 2014 08:21:12 +0100
Received: from [] (unknown []) (using TLSv1 with cipher ECDHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by leo (Postfix) with ESMTPSA id 615871FDFD; Thu, 20 Mar 2014 08:21:09 +0100 (CET)
X-Envelope-From: ramon.casellas@cttc.es
Message-ID: <532A96E3.3010806@cttc.es>
Date: Thu, 20 Mar 2014 08:21:07 +0100
From: Ramon Casellas <ramon.casellas@cttc.es>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:24.0) Gecko/20100101 Thunderbird/24.4.0
MIME-Version: 1.0
To: "BRUNGARD, DEBORAH A" <db3546@att.com>, Iftekhar Hussain <IHussain@infinera.com>, "Zhangxian (Xian)" <zhang.xian@huawei.com>
References: <D7D7AB44C06A2440B716F1F1F5E70AE53FB23DC1@SV-EXDB-PROD1.infinera.com> <OFD8D21453.D491AE4A-ON48257C9F.0023736F-48257C9F.0024039F@zte.com.cn> <C636AF2FA540124E9B9ACB5A6BECCE6B302137BE@SZXEMA512-MBS.china.huawei.com> <53282314.1040201@cttc.es> <D7D7AB44C06A2440B716F1F1F5E70AE53FB2643D@SV-EXDB-PROD1.infinera.com> <C636AF2FA540124E9B9ACB5A6BECCE6B30213972@SZXEMA512-MBS.china.huawei.com> <D7D7AB44C06A2440B716F1F1F5E70AE53FB277A1@SV-EXDB-PROD1.infinera.com> <F64C10EAA68C8044B33656FA214632C80C16D989@MISOUT7MSGUSR9O.ITServices.sbc.com>
In-Reply-To: <F64C10EAA68C8044B33656FA214632C80C16D989@MISOUT7MSGUSR9O.ITServices.sbc.com>
Content-Type: multipart/alternative; boundary="------------090807020706020901080506"
X-Spamina-Bogosity: Ham
Archived-At: http://mailarchive.ietf.org/arch/msg/ccamp/mqeJbjU8aWZhlVpycnqZu9a6I3A
Cc: "ccamp@ietf.org" <ccamp@ietf.org>
Subject: [CCAMP] Final Text ITU-T Liaison flexi-grid // Was: Draft Text for ITU-T - CCAMP Liason regarding Flexi-grid
X-BeenThere: ccamp@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Discussion list for the CCAMP working group <ccamp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ccamp>, <mailto:ccamp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ccamp/>
List-Post: <mailto:ccamp@ietf.org>
List-Help: <mailto:ccamp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ccamp>, <mailto:ccamp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 20 Mar 2014 07:21:36 -0000


As Deborah mentioned, the text of the liaison should be ready by now. 
Accommodating most (all?) comments by now, I would say the following 
seems to be quite final.

Chairs, could you please proceed? many thanks in advance



In order to progress our work on the draft “Framework and Requirements 
for GMPLS based control of Flexi-grid DWDM networks” [1] and subsequent 
solution documents within the IETF CCAMP working group, we would like to 
receive your comments/clarification on the following items (addressing 
ITU-T experts within Q6, Q12 and Q14):

· Please comment on future changes regarding the values of nominal 
central frequency (NCF) granularity [NCFG, currently 6.25 GHz] and slot 
width granularity [currently 12.5 GHz], as defined in G.694.1. Is ITU-T 
considering alternative values (e.g. 3.125 GHz) for NCFG in the 
foreseeable future? If yes, is it correct to assume, that the following 
always holds, w.r.t. slot width granularity and NCF granularity?
SWG = 2 * NCFG [Note: changes in these values may require additional 
code-points within encodings at control plane protocols.]

· Clarification on the maximum values of the slot width (m parameter) 
and the expected use cases (e.g. to cover the whole C band).
[Note: Knowing these values is required since it has an impact on their 

· Opinion / Clarification on the data plane “hitless” and “hitless” 
capabilities. Is ITU-T considering any hitless procedure, such as 
resizing / restoration of a network media channel (in terms of its 
frequency slot)? Examples of cases where hitless capabilities may be 
considered are:

o   Case 1: Recovery where the new network media channel uses a diverse path
o   Case 2: shrink / enlarge frequency slot width, invariant NCF (n)
o   Case 3: shift the NCF (n), maintaining the frequency slot width (m)

· Clarification on the case where an OTUCn is carried by a (co-routed) 
group of network media channels which must be managed as a single entity 
(including set up, recovery, and hardware cross-connection). If this is 
in scope, what is the estimated availability of ITU-T Recommendation 
covering this new requirement?
[Note: CCAMP has considered so far the following requirement: “The 
control plane architecture SHOULD allow multiple media channels to be 
logically associated.  The control plane SHOULD allow the co-routing of 
a set of media channels logically associated”. If ITU-T covers this new 
requirement, it may have an impact on the control plane representation 
and related procedures.]

· G.872 defines that a media channel may carry more than one OCh-P 
signal. It also defines that a network media channel is the end-to-end 
channel allocated to transport a single OCh-P.  We would appreciate 
clarification on the application of network media channel with respect 
to media channel related to management and configuration aspects.

[1] http://tools.ietf.org/html/draft-ietf-ccamp-flexi-grid-fwk-01