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

Young Lee <ylee@huawei.com> Tue, 31 August 2010 19:01 UTC

Return-Path: <ylee@huawei.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 6F1883A6A84 for <cso@core3.amsl.com>; Tue, 31 Aug 2010 12:01:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.254
X-Spam-Level:
X-Spam-Status: No, score=-2.254 tagged_above=-999 required=5 tests=[AWL=0.344, BAYES_00=-2.599, 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 yoKKtvpv4967 for <cso@core3.amsl.com>; Tue, 31 Aug 2010 12:01:02 -0700 (PDT)
Received: from usaga02-in.huawei.com (usaga02-in.huawei.com [206.16.17.70]) by core3.amsl.com (Postfix) with ESMTP id A6D693A6A96 for <cso@ietf.org>; Tue, 31 Aug 2010 12:00:55 -0700 (PDT)
Received: from huawei.com (localhost [127.0.0.1]) by usaga02-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0L8100LY9669F1@usaga02-in.huawei.com> for cso@ietf.org; Tue, 31 Aug 2010 12:01:22 -0700 (PDT)
Received: from L73682 ([10.124.12.96]) by usaga02-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTPA id <0L810053L668PY@usaga02-in.huawei.com> for cso@ietf.org; Tue, 31 Aug 2010 12:01:21 -0700 (PDT)
Date: Tue, 31 Aug 2010 14:01:20 -0500
From: Young Lee <ylee@huawei.com>
In-reply-to: <14584D6EE26B314187A4F68BA206060005084816@ASHEVS008.mcilink.com>
To: "'So, Ning'" <ning.so@verizonbusiness.com>, "'McDysan, David E (Dave)'" <dave.mcdysan@verizon.com>
Message-id: <004001cb493e$e63a94f0$600c7c0a@china.huawei.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.3664
X-Mailer: Microsoft Office Outlook 11
Content-type: multipart/alternative; boundary="Boundary_(ID_cVrPOIR9tTa0g+Izj1JXaw)"
Thread-index: ActAsaxi+70ccMW+QhqgDdMr/6lT5wEfwl/gAAEaGsAAATt10ADHKHLgADMtMCAABijRUAAAavBA
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>
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: Tue, 31 Aug 2010 19:01:09 -0000

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