Re: [cso] Directional Changes for CSO work

Ning So <ningso@yahoo.com> Fri, 10 September 2010 15:19 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 4C4FC3A6860 for <cso@core3.amsl.com>; Fri, 10 Sep 2010 08:19:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 2.278
X-Spam-Level: **
X-Spam-Status: No, score=2.278 tagged_above=-999 required=5 tests=[BAYES_50=0.001, DC_GIF_UNO_LARGO=2.275, HTML_IMAGE_RATIO_08=0.001, 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 IR3Ci4GUJRsh for <cso@core3.amsl.com>; Fri, 10 Sep 2010 08:19:35 -0700 (PDT)
Received: from web84102.mail.mud.yahoo.com (web84102.mail.mud.yahoo.com [68.142.206.189]) by core3.amsl.com (Postfix) with SMTP id 251913A6835 for <cso@ietf.org>; Fri, 10 Sep 2010 08:19:33 -0700 (PDT)
Received: (qmail 77672 invoked by uid 60001); 10 Sep 2010 15:19:57 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s1024; t=1284131997; bh=oJbLSYaS2FbqGp3NMF7UlRQNkQYcaXLNbo1mc/W3yDA=; h=Message-ID:X-YMail-OSG:Received:X-Mailer:References:Date:From:Subject:To:In-Reply-To:MIME-Version:Content-Type; b=zw7/9DGTOXfPe66AIK2v3T/psQPYg8uhnBQm3G13tFvWMJ2/kz2q3BoTDDG2lNcUy4+CuoTjHCkG49chFZdlRyDcUTvCpyNgBLkz6StC3NB1FJXKrlOuz5meP10hrvU5G3BOX22RrnGtbB150W6f++ip8ik+lPXjYA/oheP1oOY=
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:In-Reply-To:MIME-Version:Content-Type; b=kLIBIl8490XBTrma7C1o4d29s+wznK2pbw9zzF/uut5yq7B2kCuKWhDCzWL9mA2pf6k3OUtKgM0VWh/6BY/u6mV/nh5Olbu7jV/Rcb2nqQPoS/xK6zGilA2xQTC4qko3aeIZv3XJDdYIFNP4aRowicrUWM4c2fEwWcsBoZIhq0s=;
Message-ID: <221543.75527.qm@web84102.mail.mud.yahoo.com>
X-YMail-OSG: 8ik82RgVM1kxY0rPnfUjOmINBBEK8AQx8l6ie8aHhUPaIe9 yIAGHJ77dcz8hSOSqDHrUKkHJUDzVk2UJ2mS6prFT1QB9FunvvdQ.GjJ_dt9 ZZcFlEYO2rdwyjO82VZSXj1XLsD5U93Quo0hH3MU3D1w_VztdDWvyxwSOdjM ADG3khwulJrNbBya3MwiKnArSzUIEwFaCfn.k_lmflm2pKtyUv7LqWjKPaEl I0vStyg.tL5L4uE9uNTPhnOon4JnuAkYpgPoreUyxSI37gCwpDhuN4VsRvQR AZgQ_2IaDXsxjj2rC0f_Mcg58AsH8HwnvKgD70HAWpxgkCn16ZXlh6LCAQ0g -
Received: from [131.146.203.81] by web84102.mail.mud.yahoo.com via HTTP; Fri, 10 Sep 2010 08:19:57 PDT
X-Mailer: YahooMailRC/470 YahooMailWebService/0.8.105.279950
References: <009b01cb505f$109b9ce0$600c7c0a@china.huawei.com> <4C8A4C37.20203@grotto-networking.com>
Date: Fri, 10 Sep 2010 08:19:57 -0700 (PDT)
From: Ning So <ningso@yahoo.com>
To: Greg Bernstein <gregb@grotto-networking.com>, cso@ietf.org
In-Reply-To: <4C8A4C37.20203@grotto-networking.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="0-1304750653-1284131997=:75527"
Subject: Re: [cso] Directional Changes for CSO work
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: Fri, 10 Sep 2010 15:19:36 -0000

Greg,

I agree with your view.

Ning




________________________________
From: Greg Bernstein <gregb@grotto-networking.com>
To: cso@ietf.org
Sent: Fri, September 10, 2010 10:18:15 AM
Subject: Re: [cso] Directional Changes for CSO work

Hi Young and all, from the point of view of finding out what the network has to 
offer the application (or what it is currently providing) the emphasis on data 
centers seems appropriate.
It seems to me that we potentially have three networking scenarios of interest:
(1) Internal to the data center (between processors, storage, external 
communications) (intra-data center)
(2) Between data centers (for larger distributed applications, for migration, 
data distribution, etc..) (inter-data center)
(3) Between end users and data centers 
These three areas also represent sucessively larger network contexts where we 
would have limits on what we can expect (or ask) of the underlying network.
Is this in line with what folks are thinking? Young, I'll separately send you 
some possible additional text on the NS Query document.

Cheers

Greg B.

On 9/9/2010 1:39 PM, Young Lee wrote: 
Hi, 
> 
>After a couple of conference calls with Ron Bonica (OPS AD) and Dan Romanscanu 
>(OPS AD), we narrowed down the scope of work and have broken the CSO work into 
>two pieces:
> 
>(i) Network Aware Application Mobility (NAAM)  
> 
>(ii) Network Stratum Query (NS Query)
> 
>Please see the draft charter descriptions in the attachment. 
> 
>Depending on the result of the IESG approval, we might pursue these two pieces 
>as separate work items down the road if both are approved. 
>
> 
>Please also note that among many potential CSO applicability, we have narrowed 
>the work in the context of Data Centers.  The following diagram depicts the 
>contexts of both NAAM and NS Query. 
>
> 
> 
>If you are still interested in the new scope, we’d appreciate your comments on 
>the charter descriptions or any other related matters. 
>
>Thanks. 
> 
>Best Regards,
>Young


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