Re: [cso] Cross-Stratum Optimization Problem Statement revision

Ning So <ningso@yahoo.com> Wed, 01 September 2010 14:54 UTC

Return-Path: <ningso@yahoo.com>
X-Original-To: cso@core3.amsl.com
Delivered-To: cso@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 470333A6812 for <cso@core3.amsl.com>; Wed, 1 Sep 2010 07:54:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.739
X-Spam-Level:
X-Spam-Status: No, score=-0.739 tagged_above=-999 required=5 tests=[BAYES_20=-0.74, HTML_MESSAGE=0.001]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2vpjIS6cLzZd for <cso@core3.amsl.com>; Wed, 1 Sep 2010 07:54:18 -0700 (PDT)
Received: from web84106.mail.mud.yahoo.com (web84106.mail.mud.yahoo.com [68.142.206.193]) by core3.amsl.com (Postfix) with SMTP id 02C1F3A694E for <cso@ietf.org>; Wed, 1 Sep 2010 07:54:17 -0700 (PDT)
Received: (qmail 23853 invoked by uid 60001); 1 Sep 2010 14:54:46 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s1024; t=1283352886; bh=kIuKLrGywQKygfONTiDKt456eRZkkWkE0MOqMFFr35w=; h=Message-ID:X-YMail-OSG:Received:X-Mailer:References:Date:From:Subject:To:Cc:In-Reply-To:MIME-Version:Content-Type; b=lBsaosJ/TJd7NksgSy/1ymrUO8fBz5cLpSBVcPf7+4JALXCV5REavjbVx7BFTSP6+kCRAsHUl4X1H1365VWT06DH7WDrVuZY1SXeICgBt+ideOsnkjmRoOF50A+jXqI1FsMkq2MrZSlRKYMW+vC36DqMWX7wXOPpycPs3SgzLS4=
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=Message-ID:X-YMail-OSG:Received:X-Mailer:References:Date:From:Subject:To:Cc:In-Reply-To:MIME-Version:Content-Type; b=3CsANZnJwz+Ix6V1WFUU/2BPo3fZrEq40XH6z2ND8I30TpapmvRJ4WewX1qvOdhgaKs2CTybU4yxNUn/rJOxNKg/Nloalcw3bJe4Dbx6eBYZPe5Vp4eAUY3j6p0+ZVvmeaR/Aa1OsfoDF6LUCOG7s4JX9Zrrk4z/AvfDNv+6I9M=;
Message-ID: <586328.23732.qm@web84106.mail.mud.yahoo.com>
X-YMail-OSG: vtLuShkVM1l1ZFv0f8MB2VKmIF5iqx76opmDJyGp2VE2DDa pzazBVN5mLQ9ZCFtlN19TfB83wBzfh6CrWevgZO2UhNJA.c8iHOD8PMPtnrb fvmghxJYKkJIAGd04p8zmSNb5A7kCaPCbWaF4h7NO9gqjXfrpNKbUm0DDV45 BbxTqjY4yPMPjO6UTGf8Nii.qgnw9NZpZ9K1VYNEmcFi6K7gpM7tScCq9h7l kgmTjEgibbESUQObm86bHkA2mNOUyqSTlfWCcNt3XBlr_AlB18BDNjXKnzXQ 5Yo175VRv9nmeWsDfsK9U5KBkoxiQfXw7h3j5TH9hrYXotT.K2s8FBcbusp6 h
Received: from [173.57.91.24] by web84106.mail.mud.yahoo.com via HTTP; Wed, 01 Sep 2010 07:54:46 PDT
X-Mailer: YahooMailRC/470 YahooMailWebService/0.8.105.279950
References: <003001cb40b1$acf382a0$600c7c0a@china.huawei.com> <14584D6EE26B314187A4F68BA206060004F91674@ASHEVS008.mcilink.com> <005001cb4537$de270c90$600c7c0a@china.huawei.com> <14584D6EE26B314187A4F68BA206060004F9174C@ASHEVS008.mcilink.com> <2464076D83FAED4D985BF2622111AAC40F06614097@FHDP1LUMXC7V11.us.one.verizon.com> <002501cb492d$0fba1380$600c7c0a@china.huawei.com> <14584D6EE26B314187A4F68BA206060005084816@ASHEVS008.mcilink.com> <004001cb493e$e63a94f0$600c7c0a@china.huawei.com> <14584D6EE26B314187A4F68BA2060600050848C0@ASHEVS008.mcilink.com>
Date: Wed, 1 Sep 2010 07:54:46 -0700 (PDT)
From: Ning So <ningso@yahoo.com>
To: "So, Ning" <ning.so@verizonbusiness.com>, Young Lee <ylee@huawei.com>, "McDysan, David E \(Dave\)" <dave.mcdysan@verizon.com>
In-Reply-To: <14584D6EE26B314187A4F68BA2060600050848C0@ASHEVS008.mcilink.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="0-1701212846-1283352886=:23732"
Cc: cso@ietf.org
Subject: Re: [cso] Cross-Stratum Optimization Problem Statement revision
X-BeenThere: cso@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: This list is for pre-WG technical discussion of cross stratum optimization <cso.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/cso>, <mailto:cso-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/cso>
List-Post: <mailto:cso@ietf.org>
List-Help: <mailto:cso-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/cso>, <mailto:cso-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 01 Sep 2010 14:54:21 -0000

Young,

Here are a couple of example of what I think CSO work may be needed in the 
"customer Prem" sitting.

1.  Inter-VLAN but within the same data center.  In this case, the data center 
can be extremely large.  The largest one I have seen is a city block with 
multiple buildings acting as a single data center from the provisioning and 
designing perspective.  VMs and Servers hosting specific applications can move 
freely across the access and aggregation switches within the data center.  The 
Layer 2 network within the data center may be MSTP or Shortest Path Bridging or 
something else all together.  I see a needs for the Network CSO Gateway to play 
some functions in this type of layer 2 network environment within the data 
center due to its complexity and scale.

2.  Intra-VLAN and outside of a single data center, but within a cluster of data 
centers within the same subnet.  In this case, the cluster of data centers are 
usually within a metro area, and connected by MAN/WAN network such as PBB, VPLS, 
IPLS, and so on.  Network CSO Gateway's function is also needed, in my point of 
view.

Please let me know your thoughts.

Ning 




________________________________
From: "So, Ning" <ning.so@verizonbusiness.com>
To: Young Lee <ylee@huawei.com>om>; "McDysan, David E (Dave)" 
<dave.mcdysan@verizon.com>
Cc: cso@ietf.org
Sent: Tue, August 31, 2010 2:33:46 PM
Subject: Re: [cso] Cross-Stratum Optimization Problem Statement revision

 
Young,
 
I am thinking more of “customer Prem”, in this case, intra-data center and 
Intra-VLAN but inter-data center network.  

 
Ning So
Transport & Data Network Evolution Planning
Verizon, Inc.
(office) 972-729-7905
(Cell) 972-955-0914
 

________________________________
 
From:Young Lee [mailto:ylee@huawei.com] 
Sent: Tuesday, August 31, 2010 2:01 PM
To: So, Ning;  McDysan, David E (Dave)
Cc: cso@ietf.org
Subject: RE: Cross-Stratum Optimization Problem Statement revision
 
Ning,
 
Network refers to the network stratum which is defined in the latest Problem 
Statement document as: 

 
The network stratum is the functional block which manages and controls network 
resources and provides transport of data between clients/end-users and 
application sources. Network Resources are resources of any layer 3 or below 
(L1/L2/L3) such as bandwidth, links, paths, path processing (creation, deletion, 
and management), network databases, path computation, admission control, and 
resource reservation. 

 
I wasn’t sure in what context LAN networks are included in your definition of 
“network”?  I was thinking “network” more or less “transport” networks that 
belong to carriers. There is a boundary between “carrier networks” and “customer 
prem” --- Are you thinking about LAN belonging to customer networks? 

 
Regards,
Young
 
 

________________________________
 
From:So, Ning [mailto:ning.so@verizonbusiness.com] 
Sent: Tuesday, August 31, 2010 1:48 PM
To: Young Lee;  McDysan, David E (Dave)
Cc: cso@ietf.org
Subject: RE: Cross-Stratum Optimization Problem Statement revision
 
Young,
 
I like the way you described the goal and how you narrowed it down.  Just want 
to clarify that the definition of “network” in network CSO Gateway include WAN 
(all Layer 1, 2 and 3) networks as well as LAN networks, right?       
 
Ning So
Transport & Data Network Evolution Planning
Verizon, Inc.
(office) 972-729-7905
(Cell) 972-955-0914
 

________________________________
 
From:Young Lee [mailto:ylee@huawei.com] 
Sent: Tuesday, August 31, 2010 11:54 AM
To: McDysan,  David E (Dave); So, Ning
Cc: cso@ietf.org
Subject: RE: Cross-Stratum Optimization Problem Statement revision
 
Hi Dave and Ning,
 
Relating to the issue of scoping the CSO work, I just wanted to make sure we 
have the same understanding. 

 
The initial work under CSO is simply defining protocol between the ACG 
(Application CSO Gateway) and NCG (Network CSO Gateway). I think you refer to 
this as proxy-signaling. 

The following figure shows the focus of CSO work. 
 
                    -------------------------------------------
                   |                    Application Overlay    |
                   |                                           |
 ----------        |    -------------         --------------  
 |                                                                                                                                                                                                   
 
| End-User |       |   | Application |. . . .| Application  |  |
|          |. . . >|   | CSO Gateway |       |  Processes   |  |
 ----------        |   |    (ACG)    |        --------------   |
                   |   |             |        --------------   |
                   |    ------------- . . . .| Application  |  
|                          

                   |          /\             | Related Data |  |
                   |          ||              --------------   |
                    ----------||-------------------------------
                              ||
                              ||   Application - Network
                              ||   Communication Interface & 
                              ||   Protocol (Focus of WG)
                              ||   
                    ----------||-------------------------------
                   |          \/         Network Underlay      |
                   |                                           
|                                           

                   |    -------------        ­---------------­-  |
                   |   |   Network   |. . . |    Network     | |
                   |   | CSO Gateway |      |    Processes   | |
                   |   |    (NCG)    |       ----------------  |
                   |   |             |       ---------------­-  |
                   |    ------------- . . . |    Network     | |
                   |                        |  Related Data  | |
                   |                         ----------------  |
                    -------------------------------------------
 
 
The protocol is simply request/reply and should support:
-          path estimation (from application to network) 
-          path configuration/reservation (from application to network – here 
the application profile needs to be communicated)
-          notification (e.g., congestion/failure indication from/to application 
to/from network)
-          virtual/abstract info query from/to application to/from network (we 
need to define what information to exchange)
 
Once this protocol is clearly defined, then we have quite a few works to be done 
in the network side at a minimum:  
-          Interface between NCG and PCE (including multi-domain PCE) 
-          Interface between NCG and Diameter/Radius (for IP network) and 
Control Plane (for MPLS/GMPLS network) 

-          How can we make communication of properties (e.g., latency) more 
dynamic/agile across functional groups in the network stratum
-          How to provide atomic NM/configuration for the whole network elements
 
But these items need to be worked on other WG groups such as CCAMP/MPLS, PCE, 
PCN, Diameter, netconf/ying, etc. I think the confusion takes place because all 
these functions are thought to be part of CSO work. 

CSO is only the trigger for these works to be done in other WG’s. 
 
Let’s continue to discuss. 
 
Best Regards,
Young