Re: [CCAMP] TR: New Version Notificationfordraft-peloso-ccamp-wson-ospf-oeo-03.txt

"Margaria, Cyril (NSN - DE/Munich)" <cyril.margaria@nsn.com> Fri, 17 June 2011 08:26 UTC

Return-Path: <cyril.margaria@nsn.com>
X-Original-To: ccamp@ietfa.amsl.com
Delivered-To: ccamp@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 68F7B11E80D6 for <ccamp@ietfa.amsl.com>; Fri, 17 Jun 2011 01:26:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.598
X-Spam-Level:
X-Spam-Status: No, score=-6.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Vz-9kTa7EtcN for <ccamp@ietfa.amsl.com>; Fri, 17 Jun 2011 01:26:27 -0700 (PDT)
Received: from demumfd002.nsn-inter.net (demumfd002.nsn-inter.net [93.183.12.31]) by ietfa.amsl.com (Postfix) with ESMTP id A95A911E808A for <ccamp@ietf.org>; Fri, 17 Jun 2011 01:26:25 -0700 (PDT)
Received: from demuprx016.emea.nsn-intra.net ([10.150.129.55]) by demumfd002.nsn-inter.net (8.12.11.20060308/8.12.11) with ESMTP id p5H8QG8g008840 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Fri, 17 Jun 2011 10:26:16 +0200
Received: from demuexc024.nsn-intra.net (demuexc024.nsn-intra.net [10.159.32.11]) by demuprx016.emea.nsn-intra.net (8.12.11.20060308/8.12.11) with ESMTP id p5H8Q9ck027181; Fri, 17 Jun 2011 10:26:16 +0200
Received: from DEMUEXC012.nsn-intra.net ([10.150.128.23]) by demuexc024.nsn-intra.net with Microsoft SMTPSVC(6.0.3790.4675); Fri, 17 Jun 2011 10:26:15 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01CC2CC8.39505928"
Date: Fri, 17 Jun 2011 10:26:07 +0200
Message-ID: <D5EABC6FDAFDAA47BC803114C68AABF202806DEE@DEMUEXC012.nsn-intra.net>
In-Reply-To: A<7AEB3D6833318045B4AE71C2C87E8E170C62F931@DFWEML501-MBX.china.huawei.com>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [CCAMP] TR: New Version Notificationfordraft-peloso-ccamp-wson-ospf-oeo-03.txt
Thread-Index: AQHMKy7wF/Jk2YXkdkS+Ik/0p3cqT5TAbmVQgAC2/VA=
References: <CCBFBB7025DF984494DEC3285C058152129673243E@FRMRSSXCHMBSA1.dc-m.alcatel-lucent.com> <4DF654C6.3070304@grotto-networking.com> <D5EABC6FDAFDAA47BC803114C68AABF2027CAC27@DEMUEXC012.nsn-intra.net> A<7AEB3D6833318045B4AE71C2C87E8E170C62F931@DFWEML501-MBX.china.huawei.com>
From: "Margaria, Cyril (NSN - DE/Munich)" <cyril.margaria@nsn.com>
To: ext Leeyoung <leeyoung@huawei.com>, ext Greg Bernstein <gregb@grotto-networking.com>, ccamp@ietf.org
X-OriginalArrivalTime: 17 Jun 2011 08:26:15.0626 (UTC) FILETIME=[3979B2A0:01CC2CC8]
Subject: Re: [CCAMP] TR: New Version Notificationfordraft-peloso-ccamp-wson-ospf-oeo-03.txt
X-BeenThere: ccamp@ietf.org
X-Mailman-Version: 2.1.12
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: Fri, 17 Jun 2011 08:26:32 -0000

Hi Young Lee, Ccamper's, 

 

Reducing the type of regenerator makes sense but  mixing regenerator
type makes also sense, as you would try to avoid having only 40G-capable
3R when you can go for a cheaper 10G regenerator, depending on your
demands. 

 

  In Greenfield deployments single rate makes sense, in an existing
networks having multi-rate (2) support with different electrical module
may be less common but should still be supported.  

   This kind of network would need 6 description for the processing
capability alone.  The total number of resource description need to be
higher, as in the info model  the description of a regenerator include
the number of resource. Each time the connectivity imply a different
number of regenerator are grouped together a separate ResourceBlockInfo
should be used (Separating connectivity and regenerator setup would help
here).

 

Best case would see indeed 0-2 type of regenerator, intermediate actual
deployments can see 6 types of regenerator, we also considered looking
at possible evolutions, 10 being in our opinion a reasonable number.

 

I hope it could help you understand better what is considered in the
draft. Those consideration will be more detailed in the next revision
of the draft.

 

Best Regards

 

 

 

From: ext Leeyoung [mailto:leeyoung@huawei.com] 
Sent: Thursday, June 16, 2011 10:47 PM
To: Margaria, Cyril (NSN - DE/Munich); ext Greg Bernstein;
ccamp@ietf.org
Subject: RE: [CCAMP] TR: New Version
Notificationfordraft-peloso-ccamp-wson-ospf-oeo-03.txt

 

Hi Cyril,

 

I think your analysis below is very theoretical and a bit out of reality
in WSON node configuration. 

 

We are dealing with wavelength level so that OTUk level is transparent
to WSON. In typical optical switch node configuration in WSON, we don't
simply mix up all possible kinds of regenerators per each modulation
type. It is true that we have many modulation types for each rate and
the model should support all possibility. But this does not mean we have
all "10 types" at the same time in a node design. As you know,
regenerator is one of the most expensive WSON elements and having many
types in a node is not economical and not realistic. 

 

As far as my understanding of node design, we don't have such thing as
you said in your email to support 10+ different types of regenerators in
a node. In a typical commercially deployed WSON switching node, we have
one rate (e.g., 10G or 40G, or possibly others) and one regenerator type
for each rate. If we have multi-rate support, we may have two rates and
thus two regenerators in a typical WSON switching node. 

 

I would be interested in the node design diagram that supports 10+
different regenerators at the same time. I haven't seen such one myself
yet.

 

Please also note that the WSON model has to support transparent node
configuration, which we don't have "regen" element. 

 

Best Regards,

Young

 

 

 

________________________________

From: ccamp-bounces@ietf.org [mailto:ccamp-bounces@ietf.org] On Behalf
Of Margaria, Cyril (NSN - DE/Munich)
Sent: Wednesday, June 15, 2011 2:36 AM
To: ext Greg Bernstein; ccamp@ietf.org
Subject: Re: [CCAMP] TR: New Version Notification
fordraft-peloso-ccamp-wson-ospf-oeo-03.txt

 

 


Hi Greg, CCAMPers, 

 

Regarding point (2), using one regen type per OTUk (k in [[1..4]]), and
2 type of laser module per reach makes already 8 type of oeo properties.
Adding slightly different hw types (i.e old board with old modulation
and a more recent with DP-QPSK) makes an easy 10 types for a big node.

 

Without going into product families this sounded reasonable (for
instance a typical product would indicate supports for 10 and 40g with
different modulation, so lets say 2 sub-board type, which makes 6 regen
type); The introduction of OTU4 and later OTU5 will increase the types
of regenerator supported.

 

The size expansion is indeed related to the number of regenerator type,
resource blocks contain connectivity, oeo-feature and how the blocks are
grouped.

 

The other point would indeed clarify the document, the setup of resource
pools/blocks is shown in Figure 1, a resource pool aggregating  the
connectivity for several resource blocks.

 

Best regards.

 

 

 

From: ccamp-bounces@ietf.org [mailto:ccamp-bounces@ietf.org] On Behalf
Of ext Greg Bernstein
Sent: Monday, June 13, 2011 8:20 PM
To: ccamp@ietf.org
Subject: Re: [CCAMP] TR: New Version Notification
fordraft-peloso-ccamp-wson-ospf-oeo-03.txt

 

Hi Pierre and draft authors, can you provide:
(1) Diagrams of the example switches particularly with respect to the
structure of the resource pools/blocks.
(2) Explanation of why so many different types (not number) of
regenerators in an optical node. You site 5 different types for a small
node and 10 for a large node. Can you point to a product family?  I
would think 0-1 types of regenerators for a small node and at maybe 2
for a large node or nodes that deal with long haul and metro types
modulations.  
(3) Can you provide the example encodings such as done in the appendix
of the encoding document so we can understand where the expansion is
taking place.

It seems that the size expansions is directly related to the number of
regenerator types, but hard to tell from this document.  Are there any
other WSON interested parties that have a need for so many regenerator
types?

Cheers

Greg B.

On 6/10/2011 7:19 AM, PELOSO, PIERRE (PIERRE) wrote: 

Hi Ccampers,
 
During Prague meeting I was asked to provide a draft detailing the
solution we were presenting then concerning OSPF-TE extensions for
Wavelength Switched Optical Networks (see point 10 of ccamp minutes).
Julien, Giovanni, Cyril and I have tackled this work of providing a
complete description of the solution with commonalities and deltas from
the existing solution held in the following drafts:
  - draft-ietf-ccamp-rwa-info-11
  - draft-ietf-ccamp-general-constraint-encode-04
  - draft-ietf-ccamp-gmpls-general-constraints-ospf-te-00
  - draft-ietf-ccamp-rwa-wson-encode-11
  - draft-ietf-ccamp-wson-signal-compatibility-ospf-04
 
Feedback from the working group is welcome.
 
To trigger this feedback, this draft holds inside section 5 a numerical
study on the amount of static and dynamic information to be flooded.
This study was conducted on various typical WSON nodes and compares the
size of the LSAs between the two solutions.
 
Regards,
 
- Pierre
 
 
_______________________________________________
CCAMP mailing list
CCAMP@ietf.org
https://www.ietf.org/mailman/listinfo/ccamp

 

-- 
===================================================
Dr Greg Bernstein, Grotto Networking (510) 573-2237