Re: [cso] Potential CSO Research Area: Designing Routing to handle variable traffic loads

"Nicola Ciulli" <n.ciulli@nextworks.it> Tue, 30 August 2011 16:34 UTC

Return-Path: <n.ciulli@nextworks.it>
X-Original-To: cso@ietfa.amsl.com
Delivered-To: cso@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8E54021F8BB8 for <cso@ietfa.amsl.com>; Tue, 30 Aug 2011 09:34:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 2.188
X-Spam-Level: **
X-Spam-Status: No, score=2.188 tagged_above=-999 required=5 tests=[BAYES_50=0.001, FH_RELAY_NODNS=1.451, HELO_EQ_IT=0.635, HTML_MESSAGE=0.001, RDNS_NONE=0.1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id TRtruufHvRnm for <cso@ietfa.amsl.com>; Tue, 30 Aug 2011 09:34:26 -0700 (PDT)
Received: from mercurio.nextworks.it (unknown [213.182.68.141]) by ietfa.amsl.com (Postfix) with SMTP id 87E4D21F8B42 for <cso@ietf.org>; Tue, 30 Aug 2011 09:34:24 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mercurio.nextworks.it (Postfix) with ESMTP id 59C0C304005 for <cso@ietf.org>; Tue, 30 Aug 2011 18:35:52 +0200 (CEST)
X-Virus-Scanned: amavisd-new at nextworks.it
Received: from mercurio.nextworks.it ([127.0.0.1]) by localhost (mercurio.nextworks.it [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id lrWkMsPFmUXd for <cso@ietf.org>; Tue, 30 Aug 2011 18:35:48 +0200 (CEST)
Received: from herbert (herbert.nextworks.it [10.0.2.225]) by mercurio.nextworks.it (Postfix) with ESMTP id 64199304004 for <cso@ietf.org>; Tue, 30 Aug 2011 18:35:48 +0200 (CEST)
Message-ID: <48D17DB6D844463D811D4CE8ECA9B103@herbert>
From: "Nicola Ciulli" <n.ciulli@nextworks.it>
To: <cso@ietf.org>
References: <7AEB3D6833318045B4AE71C2C87E8E1718159B59@DFWEML501-MBX.china.huawei.com>
Date: Tue, 30 Aug 2011 18:35:36 +0200
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_0224_01CC6743.9BDDB5D0"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2900.5931
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.6109
Subject: Re: [cso] Potential CSO Research Area: Designing Routing to handle variable traffic loads
X-BeenThere: cso@ietf.org
X-Mailman-Version: 2.1.12
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/options/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, 30 Aug 2011 16:34:27 -0000

Hi Young, all,

I can point the EC-funded GEYSERS project, as already introduced at the CSO workshop in Daejeon.
http://www.geysers.eu/

Imho, the following two deliverables are of specific relevance for the CSO works:

Deliverable 4.2: NIPS user-network interface and procedures
http://www.geysers.eu/images/stories/deliverables/geysers-deliverable_4.2.pdf

Deliverable 2.2: GEYSERS overall architecture & interfaces specification and service provisioning workflow http://www.geysers.eu/images/stories/deliverables/geysers-deliverable_2.2_update_final.pdf

Also some requirements and use cases documents from WP1 (D1.x), from the list in http://www.geysers.eu/index.php/deliverables, could be useful.

Hope this helps.

best regards,
Nicola.




------------------------------------------------------------------------------
  From: cso-bounces@ietf.org [mailto:cso-bounces@ietf.org] On Behalf Of Leeyoung
  Sent: Friday, August 19, 2011 10:20 AM
  To: cso@ietf.org
  Subject: Re: [cso] Potential CSO Research Area: Designing Routing to handle variable traffic loads


  Hi all,

  I think we have a good progress on the CSO work in the last meeting in Quebec City. It seems that more people are interested in the idea. I'd like to say thanks Dr. Dave McDaysan for providing a few links that might be related to CSO research. 

  It might be a good idea to bring any on-going activities in research community to the discussion that resonate with the CSO idea and its spirit.  

  I have found the following activities: 

  http://pnrl.stanford.edu/HyperFlow/HyperFlow_summary.htm
  http://web.mit.edu/chan/www/vincent_project.html (please see optical flow swtiching and future optical network architecture)

  Hyperflow project is a NSF funded project that has a great synergy with the CSO's vision for joint otpimization across physical transport network with application stratum. Here's an excerpt from Standford's Hyperflow descritpion:

  "HyperFlow relies on a novel optical network infrastructure comprising new transport mechanisms and a new comprehensive control plane including network protocols from the physical layer up to the application layer."

  I think UTD's Dr. Andrea Fumagalli (one of the three PI's for Hyperflow project and one of the main supporters of the CSO work ) can provide more insight on Hyperflow in light of CSO spirit. 
    
  Please feel free to pitch in any research activities you either have been involved with or are aware of that might contribute the CSO work to move forward in IRTF. 

  Thanks & Best Regards,
  Young



------------------------------------------------------------------------------
  From: cso-bounces@ietf.org [mailto:cso-bounces@ietf.org] On Behalf Of Mcdysan, David E
  Sent: Wednesday, July 27, 2011 8:33 PM
  To: cso@ietf.org
  Subject: [cso] Potential CSO Research Area: Designing Routing to handle variable traffic loads


  The other research paper that I mentioned:




  Efficient and Robust Routing of Highly Variable Traffic



  What network routing should an Inter- net Service Provider use so as to (i) accommodate users demanding "good" service while being unpredictable in the traffic that they would like to send to different destinations, (ii) minimize the amount of "overprovi- sioning" that needs to be done in the network in or- der to make "best effort networking better" without re- sorting to sophisticated traffic prediction and manage- ment mechanisms, (iii) operate the network efficiently with mostly static routing configurations and without dynamic routing adjustments to avoid congestion due to drastic changes in traffic flows between a network's ingress and egress routers.



  http://www.cc.gatech.edu/classes/AY2007/cs7260_spring/papers/variable.pdf


  Dave