Return-Path: <zhangfatai@huawei.com>
X-Original-To: ccamp@ietfa.amsl.com
Delivered-To: ccamp@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com
 (Postfix) with ESMTP id 564431A03C9 for <ccamp@ietfa.amsl.com>;
 Tue, 18 Mar 2014 04:46:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.747
X-Spam-Level: 
X-Spam-Status: No,
 score=-4.747 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,
 HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.547,
 SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com
 [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id KgleFJ-QsUSx for
 <ccamp@ietfa.amsl.com>; Tue, 18 Mar 2014 04:46:28 -0700 (PDT)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) by
 ietfa.amsl.com (Postfix) with ESMTP id B47F41A06CC for <ccamp@ietf.org>;
 Tue, 18 Mar 2014 04:46:14 -0700 (PDT)
Received: from 172.18.7.190 (EHLO lhreml204-edg.china.huawei.com)
 ([172.18.7.190]) by lhrrg02-dlp.huawei.com (MOS 4.3.7-GA FastPath queued)
 with ESMTP id BCE53175; Tue, 18 Mar 2014 11:46:05 +0000 (GMT)
Received: from LHREML406-HUB.china.huawei.com (10.201.5.243) by
 lhreml204-edg.china.huawei.com (172.18.7.223) with Microsoft SMTP Server
 (TLS) id 14.3.158.1; Tue, 18 Mar 2014 11:45:53 +0000
Received: from SZXEMA401-HUB.china.huawei.com (10.82.72.33) by
 lhreml406-hub.china.huawei.com (10.201.5.243) with Microsoft SMTP Server
 (TLS) id 14.3.158.1; Tue, 18 Mar 2014 11:45:55 +0000
Received: from SZXEMA504-MBS.china.huawei.com ([169.254.8.15]) by
 SZXEMA401-HUB.china.huawei.com ([10.82.72.33]) with mapi id 14.03.0158.001;
 Tue, 18 Mar 2014 19:45:50 +0800
From: Fatai Zhang <zhangfatai@huawei.com>
To: Ramon Casellas <ramon.casellas@cttc.es>, "ccamp@ietf.org" <ccamp@ietf.org>
Thread-Topic: [CCAMP] Draft Text for ITU-T - CCAMP Liason regarding Flexi-grid
Thread-Index: AQHPPSwcqGay97GfJkiJ4/JTd6KXbZrcCU0AgAAXtHCACPbDAIAAZOSwgAAHvID//4WcAIAAjaGAgAAx4QCAAB1UAIAAzHP1gAAQRrA=
Date: Tue, 18 Mar 2014 11:45:49 +0000
Message-ID: <F82A4B6D50F9464B8EBA55651F541CF85CAD8F40@SZXEMA504-MBS.china.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>
In-Reply-To: <53282314.1040201@cttc.es>
Accept-Language: zh-CN, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.66.72.159]
Content-Type: multipart/alternative;
 boundary="_000_F82A4B6D50F9464B8EBA55651F541CF85CAD8F40SZXEMA504MBSchi_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: http://mailarchive.ietf.org/arch/msg/ccamp/UoHjuy0PplxWnOKGoTobOjVMrdI
Subject: Re: [CCAMP] 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: Tue, 18 Mar 2014 11:46:32 -0000

--_000_F82A4B6D50F9464B8EBA55651F541CF85CAD8F40SZXEMA504MBSchi_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Hi Ramon,
You mentioned NCFG and SWG before the question, but you did not specify alt=
ernative values for what (e.g, NCFG or SWG or both).
I assume that you meant "Is ITU-T considering alternative values (e.g. 3.12=
5 GHz) of NCFG in the foreseeable future?".
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
Is ITU-T considering alternative values (e.g. 3.125 GHz) in the foreseeable=
 future?



Best Regards

Fatai

From: CCAMP [mailto:ccamp-bounces@ietf.org] On Behalf Of Ramon Casellas
Sent: Tuesday, March 18, 2014 6:42 PM
To: ccamp@ietf.org
Subject: Re: [CCAMP] Draft Text for ITU-T - CCAMP Liason regarding Flexi-gr=
id

Dear all,

Thanks for your comments. Below a revised text, still open for discussion.

Personally, I am afraid i still don't fully grasp the last bullet, so pleas=
e elaborate a bit more or re-formulate (Iftekhar, Rajan?)

[Editor: In my limited understanding:
- A NMC as bound to 1 OCh-P by definition of the in-force G.872.
- a Media channel may carry more than 1 OCh-P, but MC !=3D NMC
- With a Optical Tributary Signal (OTS) there is a 1:1 mapping between OTS:=
NMC.
- A particular case of OTS is an OCh-P
For my understanding, can a OTS group multiple OCh-P?]


Thanks
R.

--------------------------------------------------------

In order to progress our work on the draft "Framework and Requirements for =
GMPLS based control of Flexi-grid DWDM networks" [1] and subsequent solutio=
n documents within the IETF CCAMP working group, we would like to receive y=
our comments/clarification as follows (addressing ITU-T experts within Q6, =
Q12 and Q14):

*    Please comment on future changes regarding the values of nominal centr=
al frequency (NCF) granularity [NCFG, currently 6.25 GHz] and slot width gr=
anularity [currently 12.5 GHz], as defined in G.694.1. Is ITU-T considering=
 alternative values (e.g. 3.125 GHz) in the foreseeable future? If yes, is =
it correct to assume, that the following always holds, w.r.t. slot width gr=
anularity and NCF granularity?
SWG =3D 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) an=
d the expected use cases (e.g. to cover the whole C band).
Knowing these values is required since it has an impact on their encoding.

*    Opinion / Clarification on the data plane "hitless" and "hitless" capa=
bilities. Is ITU-T considering any hitless procedure, such as resizing / re=
storation of a network media channel (in terms of its frequency slot)? Exam=
ples of cases where hitless capabilities may be considered are:
o    Case 1: Recovery where the new network media channel uses a diverse pa=
th
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) g=
roup of network media channels which must be managed as a single entity (in=
cluding set up, recovery, and hardware cross-connection). If this is in sco=
pe, what is the estimated availability of ITU-T Recommendation covering thi=
s new requirement?
[Note: CCAMP has considered so far the following requirement: "The control =
plane architecture SHOULD allow multiple media channels to be logically ass=
ociated.  The control plane SHOULD allow the co-routing of a set of media c=
hannels logically associated". If ITU-T covers this new requirement, it may=
 have an impact on the control plane representation and related procedures]

*    Current in-force G.872 recommendation defines that a media channel may=
 carry more than one OCh-P signal. It also defines that a network media cha=
nnel is a specific use of media channel with a single OCh-P.  May a network=
 media channel be defined as associated with more than one OCh-P?

[1] http://tools.ietf.org/html/draft-ietf-ccamp-flexi-grid-fwk-01

--_000_F82A4B6D50F9464B8EBA55651F541CF85CAD8F40SZXEMA504MBSchi_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
<meta name=3D"Generator" content=3D"Microsoft Word 12 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
	{font-family:SimSun;
	panose-1:2 1 6 0 3 1 1 1 1 1;}
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
	{font-family:SimSun;
	panose-1:2 1 6 0 3 1 1 1 1 1;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin-top:0cm;
	margin-right:0cm;
	margin-bottom:8.0pt;
	margin-left:0cm;
	line-height:106%;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";
	color:black;}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
tt
	{mso-style-priority:99;
	font-family:"Courier New";}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
	{mso-style-priority:34;
	margin-top:0cm;
	margin-right:0cm;
	margin-bottom:8.0pt;
	margin-left:36.0pt;
	line-height:106%;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";
	color:black;}
p.MsoListParagraphCxSpFirst, li.MsoListParagraphCxSpFirst, div.MsoListParag=
raphCxSpFirst
	{mso-style-priority:34;
	mso-style-type:export-only;
	margin-top:0cm;
	margin-right:0cm;
	margin-bottom:0cm;
	margin-left:36.0pt;
	margin-bottom:.0001pt;
	line-height:106%;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";
	color:black;}
p.MsoListParagraphCxSpMiddle, li.MsoListParagraphCxSpMiddle, div.MsoListPar=
agraphCxSpMiddle
	{mso-style-priority:34;
	mso-style-type:export-only;
	margin-top:0cm;
	margin-right:0cm;
	margin-bottom:0cm;
	margin-left:36.0pt;
	margin-bottom:.0001pt;
	line-height:106%;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";
	color:black;}
p.MsoListParagraphCxSpLast, li.MsoListParagraphCxSpLast, div.MsoListParagra=
phCxSpLast
	{mso-style-priority:34;
	mso-style-type:export-only;
	margin-top:0cm;
	margin-right:0cm;
	margin-bottom:8.0pt;
	margin-left:36.0pt;
	line-height:106%;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";
	color:black;}
span.EmailStyle20
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:612.0pt 792.0pt;
	margin:72.0pt 90.0pt 72.0pt 90.0pt;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
</head>
<body bgcolor=3D"white" lang=3D"ZH-CN" link=3D"blue" vlink=3D"purple">
<div class=3D"WordSection1">
<p class=3D"MsoNormal"><span lang=3D"ES" style=3D"font-size:10.5pt;line-hei=
ght:106%;color:#1F497D">Hi Ramon,<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.5pt;line-=
height:106%;color:#1F497D">You mentioned NCFG and SWG before the question, =
but you did not specify alternative values for what (e.g, NCFG or SWG or bo=
th).<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.5pt;line-=
height:106%;color:#1F497D">I assume that you meant &#8220;Is ITU-T consider=
ing alternative values (e.g. 3.125 GHz) of NCFG in the foreseeable future?&=
#8221;.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.5pt;line-=
height:106%;color:#1F497D">=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D<o:p></o:p></span>=
</p>
<p class=3D"MsoNormal"><tt><span lang=3D"ES" style=3D"font-size:10.0pt;line=
-height:106%">Is ITU-T considering alternative values (e.g. 3.125 GHz) in t=
he foreseeable future?</span></tt><span lang=3D"ES" style=3D"font-size:10.5=
pt;line-height:106%;color:#1F497D"><o:p></o:p></span></p>
<div>
<p class=3D"MsoNormal" style=3D"margin-bottom:0cm;margin-bottom:.0001pt;tex=
t-align:justify;text-justify:inter-ideograph;line-height:normal">
<span lang=3D"EN-US" style=3D"font-size:10.5pt;color:#1F497D"><o:p>&nbsp;</=
o:p></span></p>
<p class=3D"MsoNormal" style=3D"margin-bottom:0cm;margin-bottom:.0001pt;tex=
t-align:justify;text-justify:inter-ideograph;line-height:normal">
<span lang=3D"EN-US" style=3D"font-size:10.5pt;color:#1F497D"><o:p>&nbsp;</=
o:p></span></p>
<p class=3D"MsoNormal" style=3D"margin-bottom:0cm;margin-bottom:.0001pt;tex=
t-align:justify;text-justify:inter-ideograph;line-height:normal">
<span lang=3D"EN-US" style=3D"font-size:10.5pt;color:#1F497D"><o:p>&nbsp;</=
o:p></span></p>
<p class=3D"MsoNormal" style=3D"margin-bottom:0cm;margin-bottom:.0001pt;tex=
t-align:justify;text-justify:inter-ideograph;line-height:normal">
<span lang=3D"EN-US" style=3D"font-size:10.5pt;color:#1F497D">Best Regards<=
o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"margin-bottom:0cm;margin-bottom:.0001pt;tex=
t-align:justify;text-justify:inter-ideograph;line-height:normal">
<span lang=3D"EN-US" style=3D"font-size:10.5pt;color:#1F497D"><o:p>&nbsp;</=
o:p></span></p>
<p class=3D"MsoNormal" style=3D"margin-bottom:0cm;margin-bottom:.0001pt;tex=
t-align:justify;text-justify:inter-ideograph;line-height:normal">
<span lang=3D"EN-US" style=3D"font-size:10.5pt;color:#1F497D">Fatai<o:p></o=
:p></span></p>
</div>
<p class=3D"MsoNormal"><span lang=3D"ES" style=3D"font-size:10.5pt;line-hei=
ght:106%;color:#1F497D"><o:p>&nbsp;</o:p></span></p>
<div>
<div style=3D"border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm =
0cm 0cm">
<p class=3D"MsoNormal" style=3D"margin-bottom:0cm;margin-bottom:.0001pt;lin=
e-height:normal">
<b><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Tahoma&=
quot;,&quot;sans-serif&quot;;color:windowtext">From:</span></b><span lang=
=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Tahoma&quot;,&quot;s=
ans-serif&quot;;color:windowtext"> CCAMP [mailto:ccamp-bounces@ietf.org]
<b>On Behalf Of </b>Ramon Casellas<br>
<b>Sent:</b> Tuesday, March 18, 2014 6:42 PM<br>
<b>To:</b> ccamp@ietf.org<br>
<b>Subject:</b> Re: [CCAMP] Draft Text for ITU-T - CCAMP Liason regarding F=
lexi-grid<o:p></o:p></span></p>
</div>
</div>
<p class=3D"MsoNormal"><span lang=3D"ES"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal" style=3D"margin-bottom:0cm;margin-bottom:.0001pt;lin=
e-height:normal">
<tt><span lang=3D"ES" style=3D"font-size:10.0pt">Dear all,</span></tt><span=
 lang=3D"ES" style=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;"=
><br>
<br>
</span><tt><span lang=3D"ES" style=3D"font-size:10.0pt">Thanks for your com=
ments. Below a revised text, still open for discussion.</span></tt><span la=
ng=3D"ES" style=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;"><b=
r>
<br>
</span><tt><span lang=3D"ES" style=3D"font-size:10.0pt">Personally, I am af=
raid i still don't fully grasp the last bullet, so please elaborate a bit m=
ore or re-formulate (Iftekhar, Rajan?)
</span></tt><span lang=3D"ES" style=3D"font-size:10.0pt;font-family:&quot;C=
ourier New&quot;"><br>
<br>
</span><tt><span lang=3D"ES" style=3D"font-size:10.0pt">[Editor: In my limi=
ted understanding:</span></tt><span lang=3D"ES" style=3D"font-size:10.0pt;f=
ont-family:&quot;Courier New&quot;"><br>
</span><tt><span lang=3D"ES" style=3D"font-size:10.0pt">- A NMC as bound to=
 1 OCh-P by definition of the in-force G.872.
</span></tt><span lang=3D"ES" style=3D"font-size:10.0pt;font-family:&quot;C=
ourier New&quot;"><br>
</span><tt><span lang=3D"ES" style=3D"font-size:10.0pt">- a Media channel m=
ay carry more than 1 OCh-P, but MC !=3D NMC</span></tt><span lang=3D"ES" st=
yle=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;"><br>
</span><tt><span lang=3D"ES" style=3D"font-size:10.0pt">- With a Optical Tr=
ibutary Signal (OTS) there is a 1:1 mapping between OTS:NMC.
</span></tt><span lang=3D"ES" style=3D"font-size:10.0pt;font-family:&quot;C=
ourier New&quot;"><br>
</span><tt><span lang=3D"ES" style=3D"font-size:10.0pt">- A particular case=
 of OTS is an OCh-P</span></tt><span lang=3D"ES" style=3D"font-size:10.0pt;=
font-family:&quot;Courier New&quot;"><br>
</span><tt><span lang=3D"ES" style=3D"font-size:10.0pt">For my understandin=
g, can a OTS group multiple OCh-P?]</span></tt><span lang=3D"ES" style=3D"f=
ont-size:10.0pt;font-family:&quot;Courier New&quot;"><br>
<br>
<br>
</span><tt><span lang=3D"ES" style=3D"font-size:10.0pt">Thanks</span></tt><=
span lang=3D"ES" style=3D"font-size:10.0pt;font-family:&quot;Courier New&qu=
ot;"><br>
</span><tt><span lang=3D"ES" style=3D"font-size:10.0pt">R.</span></tt><span=
 lang=3D"ES" style=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;"=
><br>
<br>
</span><tt><span lang=3D"ES" style=3D"font-size:10.0pt">-------------------=
-------------------------------------</span></tt><span lang=3D"ES" style=3D=
"font-size:10.0pt;font-family:&quot;Courier New&quot;"><br>
<br>
</span><tt><span lang=3D"ES" style=3D"font-size:10.0pt">In order to progres=
s our work on the draft &#8220;Framework and Requirements for GMPLS based c=
ontrol of Flexi-grid DWDM networks&#8221; [1] and subsequent solution docum=
ents within the IETF CCAMP working group, we would
 like to receive your comments/clarification as follows (addressing ITU-T e=
xperts within Q6, Q12 and Q14):</span></tt><span lang=3D"ES" style=3D"font-=
size:10.0pt;font-family:&quot;Courier New&quot;"><br>
<br>
</span><tt><span lang=3D"ES" style=3D"font-size:10.0pt">&#8226;&nbsp;&nbsp;=
&nbsp; Please comment on future changes regarding the values of nominal cen=
tral 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) in the foreseeabl=
e future? If yes, is it correct to assume, that the following always holds,=
 w.r.t. slot width granularity and NCF granularity? &nbsp;&nbsp;&nbsp;
</span></tt><span lang=3D"ES" style=3D"font-size:10.0pt;font-family:&quot;C=
ourier New&quot;"><br>
</span><tt><span lang=3D"ES" style=3D"font-size:10.0pt">SWG =3D 2 * NCFG [N=
ote: changes in these values may require additional code-points within enco=
dings at control plane protocols]</span></tt><span lang=3D"ES" style=3D"fon=
t-size:10.0pt;font-family:&quot;Courier New&quot;"><br>
<br>
</span><tt><span lang=3D"ES" style=3D"font-size:10.0pt">&#8226;&nbsp;&nbsp;=
&nbsp; Clarification on the maximum values of the slot width (m parameter) =
and the expected use cases (e.g. to cover the whole C band). &nbsp;&nbsp;&n=
bsp;
</span></tt><span lang=3D"ES" style=3D"font-size:10.0pt;font-family:&quot;C=
ourier New&quot;"><br>
</span><tt><span lang=3D"ES" style=3D"font-size:10.0pt">Knowing these value=
s is required since it has an impact on their encoding.
</span></tt><span lang=3D"ES" style=3D"font-size:10.0pt;font-family:&quot;C=
ourier New&quot;"><br>
<br>
</span><tt><span lang=3D"ES" style=3D"font-size:10.0pt">&#8226;&nbsp;&nbsp;=
&nbsp; Opinion / Clarification on the data plane &#8220;hitless&#8221; and =
&#8220;hitless&#8221; capabilities. Is ITU-T considering any hitless proced=
ure, 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:=
</span></tt><span lang=3D"ES" style=3D"font-size:10.0pt;font-family:&quot;C=
ourier New&quot;"><br>
</span><tt><span lang=3D"ES" style=3D"font-size:10.0pt">o&nbsp;&nbsp;&nbsp;=
 Case 1: Recovery where the new network media channel uses a diverse path
</span></tt><span lang=3D"ES" style=3D"font-size:10.0pt;font-family:&quot;C=
ourier New&quot;"><br>
</span><tt><span lang=3D"ES" style=3D"font-size:10.0pt">o&nbsp;&nbsp;&nbsp;=
 Case 2: shrink / enlarge frequency slot width, invariant NCF (n)</span></t=
t><span lang=3D"ES" style=3D"font-size:10.0pt;font-family:&quot;Courier New=
&quot;"><br>
</span><tt><span lang=3D"ES" style=3D"font-size:10.0pt">o&nbsp;&nbsp;&nbsp;=
 Case 3: shift the NCF (n), maintaining the frequency slot width (m)
</span></tt><span lang=3D"ES" style=3D"font-size:10.0pt;font-family:&quot;C=
ourier New&quot;"><br>
<br>
</span><tt><span lang=3D"ES" style=3D"font-size:10.0pt">&#8226;&nbsp;&nbsp;=
&nbsp; 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 Recommend=
ation covering this new requirement?
</span></tt><span lang=3D"ES" style=3D"font-size:10.0pt;font-family:&quot;C=
ourier New&quot;"><br>
</span><tt><span lang=3D"ES" style=3D"font-size:10.0pt">[Note: CCAMP has co=
nsidered so far the following requirement: &#8220;The control plane archite=
cture SHOULD allow multiple media channels to be logically associated.&nbsp=
; The control plane SHOULD allow the co-routing
 of a set of media channels logically associated&#8221;. If ITU-T covers th=
is new requirement, it may have an impact on the control plane representati=
on and related procedures]</span></tt><span lang=3D"ES" style=3D"font-size:=
10.0pt;font-family:&quot;Courier New&quot;"><br>
<br>
</span><tt><span lang=3D"ES" style=3D"font-size:10.0pt">&#8226;&nbsp;&nbsp;=
&nbsp; Current in-force G.872 recommendation defines that a media channel m=
ay carry more than one OCh-P signal. It also defines that a network media c=
hannel is a specific use of media channel with a single OCh-P.&nbsp;
 May a network media channel be defined as associated with more than one OC=
h-P?</span></tt><span lang=3D"ES" style=3D"font-size:10.0pt;font-family:&qu=
ot;Courier New&quot;"><br>
<br>
</span><tt><span lang=3D"EN-US" style=3D"font-size:10.0pt">[1] <a href=3D"h=
ttp://tools.ietf.org/html/draft-ietf-ccamp-flexi-grid-fwk-01">
http://tools.ietf.org/html/draft-ietf-ccamp-flexi-grid-fwk-01</a> </span></=
tt><span lang=3D"EN-US" style=3D"font-size:12.0pt;font-family:&quot;Times N=
ew Roman&quot;,&quot;serif&quot;"><o:p></o:p></span></p>
</div>
</body>
</html>

--_000_F82A4B6D50F9464B8EBA55651F541CF85CAD8F40SZXEMA504MBSchi_--

