[cso] Some thoughts from the CSO Bar BOF...

Greg Bernstein <gregb@grotto-networking.com> Tue, 09 November 2010 20:28 UTC

Return-Path: <gregb@grotto-networking.com>
X-Original-To: cso@core3.amsl.com
Delivered-To: cso@core3.amsl.com
Received: from localhost (localhost []) by core3.amsl.com (Postfix) with ESMTP id 4693F3A6879 for <cso@core3.amsl.com>; Tue, 9 Nov 2010 12:28:03 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.157
X-Spam-Status: No, score=-2.157 tagged_above=-999 required=5 tests=[AWL=0.443, BAYES_00=-2.599]
Received: from mail.ietf.org ([]) by localhost (core3.amsl.com []) (amavisd-new, port 10024) with ESMTP id nysnLBd-itOj for <cso@core3.amsl.com>; Tue, 9 Nov 2010 12:28:02 -0800 (PST)
Received: from mail30c40.carrierzone.com (mail30c40.carrierzone.com []) by core3.amsl.com (Postfix) with ESMTP id 1EBF93A682B for <cso@ietf.org>; Tue, 9 Nov 2010 12:28:01 -0800 (PST)
X-Authenticated-User: gregb.grotto-networking.com
Received: from [] (dhcp-4605.meeting.ietf.org []) (authenticated bits=0) by mail30c40.carrierzone.com (8.13.6/8.13.1) with ESMTP id oA9KSNPD016116 for <cso@ietf.org>; Tue, 9 Nov 2010 20:28:25 GMT
Message-ID: <4CD9AEE4.1040600@grotto-networking.com>
Date: Tue, 09 Nov 2010 12:28:20 -0800
From: Greg Bernstein <gregb@grotto-networking.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv: Gecko/20101027 Lightning/1.0b2 Thunderbird/3.1.6
MIME-Version: 1.0
To: cso@ietf.org
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-CSC: 0
X-CHA: v=1.1 cv=wkLTqIGD4PnaI63YEUKVjjIcskqVcXaDBw7/dUeHjcA= c=1 sm=1 a=m4LGnKmqDocA:10 a=8nJEP1OIZ-IA:10 a=WAtAgKIrLSnMrdtHviu8Xw==:17 a=iB_l81eejX6ldRvCCuwA:9 a=RivgwcwHavwDC0YbohAA:7 a=JXnuUH6zRtwq_SIGFeI9lcCcIpYA:4 a=wPNLvfGTeEIA:10 a=EgY3od2ZU2QA:10 a=h-I_03WOSDMA:10 a=3mM25VQlHUhHPqq8:21 a=ZcE_4kHN3harrZsG:21 a=WAtAgKIrLSnMrdtHviu8Xw==:117
Subject: [cso] Some thoughts from the CSO Bar BOF...
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, 09 Nov 2010 20:28:03 -0000

Hi folks interested in cross stratum optimization (CSO) a few thoughts 
on some of the interesting points raised at the Bar BOF and to possibly 
stimulate further discussion:

(a) Who benefits from CSO? The application provider or the carrier? It 
seems to be viable CSO should benefit both. The network operator 
(carrier, ISP, IT department, etc...) should benefit from more effective 
utilization of network resources (links, switches, routers, etc...) and 
gain more flexibility in dealing with fault conditions. The application 
provider benefits from being able to offer either higher quality 
services or better assurances on service quality. Essentially the 
network operator gets to influence the placement of load on the network 
while the application provider gets information that allows them to 
optimize their resources along with their customers experience.

(b) Isn't the Internet "best effort"? How can you talk of providing a 
better "network experience" to applications?
First CSO isn't strictly aimed at the "Internet" in general, but would 
start with various network domains (LAN, OSPF area, AS, etc...). Also 
"best effort" is a somewhat misleading term since it doesn't take into 
account overall statistical quality measures that are very important to 
user experiences. For example 2000 sessions sharing a link on a first 
come first serve basis are considered "best effort" whether the link is 
a T1 or an OC-192 but will generally experience greatly different 
"average" QoS ;-) . Depending on the network context and technology 
various service level guarantees may be explicit or implicit.

(c) What's a "data center" and do we include "hosts"? Folks interested 
in CSO come from a number application and network areas.  The essence is 
that guidance from the network provider to the application provider 
concerning network state and capability provides benefits to both. In 
one of the drafts we tried a definition of a "data center" as something 
like "a location within the network where application resources maybe 
I'd say a "host" (or my laptop) would qualify. Other ideas?

(d) Examples? During some of the background work for the CSO drafts we 
looked at a number of examples that we published in the original draft. 
We've also looked at "pre-CSO" type mechanisms that are being used to 
try and optimize applications. These include "old school" and "new 
school" CDN approaches,  load balancing within and between data centers 
(local versus global),  various papers dealing with local and wide area 
VM migration, and High Performance Computing applications (radio 
astronomy being an interest of mine). Would it be useful to organize 
these in some way? We had some of these in the original CLO draft but 
the overall length was getting to long.  For our WSON work we set up web 
pages to keep track not just editors copies of our drafts (for all to 
work with) but supplemental material (some of which was later published 
in IEEE/OSA journals).

Just some thoughts from a jet lagged Californian ;-)

Greg B.

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