Re: [altoext] [alto] i2aex BOF - SDN Use Case

Tina TSOU <Tina.Tsou.Zouting@huawei.com> Mon, 26 March 2012 20:52 UTC

Return-Path: <Tina.Tsou.Zouting@huawei.com>
X-Original-To: altoext@ietfa.amsl.com
Delivered-To: altoext@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A111721F8470; Mon, 26 Mar 2012 13:52:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.34
X-Spam-Level:
X-Spam-Status: No, score=-2.34 tagged_above=-999 required=5 tests=[AWL=0.258, BAYES_00=-2.599, HTML_MESSAGE=0.001]
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 kPW7H7B1A1z9; Mon, 26 Mar 2012 13:52:13 -0700 (PDT)
Received: from dfwrgout.huawei.com (dfwrgout.huawei.com [206.16.17.72]) by ietfa.amsl.com (Postfix) with ESMTP id 44C1321F8471; Mon, 26 Mar 2012 13:52:13 -0700 (PDT)
Received: from 172.18.9.243 (EHLO dfweml201-edg.china.huawei.com) ([172.18.9.243]) by dfwrg01-dlp.huawei.com (MOS 4.2.3-GA FastPath) with ESMTP id AES22487; Mon, 26 Mar 2012 16:52:13 -0400 (EDT)
Received: from DFWEML408-HUB.china.huawei.com (10.193.5.134) by dfweml201-edg.china.huawei.com (172.18.9.107) with Microsoft SMTP Server (TLS) id 14.1.323.3; Mon, 26 Mar 2012 13:50:11 -0700
Received: from SZXEML420-HUB.china.huawei.com (10.82.67.159) by dfweml408-hub.china.huawei.com (10.193.5.134) with Microsoft SMTP Server (TLS) id 14.1.323.3; Mon, 26 Mar 2012 13:50:13 -0700
Received: from SZXEML526-MBX.china.huawei.com ([169.254.2.214]) by szxeml420-hub.china.huawei.com ([10.82.67.159]) with mapi id 14.01.0323.003; Tue, 27 Mar 2012 04:50:05 +0800
From: Tina TSOU <Tina.Tsou.Zouting@huawei.com>
To: Ping Pan <ping@pingpan.org>
Thread-Topic: [alto] i2aex BOF - SDN Use Case
Thread-Index: AQHNCVE34jHi76bTg0mrCbeiWIyrP5Z58zbggABezwCAABQigIACq0Bf
Date: Mon, 26 Mar 2012 20:50:04 +0000
Message-ID: <915E2435-C268-4211-87E5-30DBC76168E1@huawei.com>
References: <7AEB3D6833318045B4AE71C2C87E8E1720C8E5DC@dfweml511-mbx.china.huawei.com> <C0E0A32284495243BDE0AC8A066631A80C8FF933@szxeml526-mbx.china.huawei.com> <C0E0A32284495243BDE0AC8A066631A80C90136F@szxeml526-mbx.china.huawei.com> <B0D29E0424F2DE47A0B36779EC66677916CD6125@szxeml504-mbs.china.huawei.com>, <CAHEV9L3KjM6Fua6T0dGHRbQB91V3R1NS1jKuR2tawjcMf38=uQ@mail.gmail.com>
In-Reply-To: <CAHEV9L3KjM6Fua6T0dGHRbQB91V3R1NS1jKuR2tawjcMf38=uQ@mail.gmail.com>
Accept-Language: en-US, zh-CN
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Content-Type: multipart/alternative; boundary="_000_915E2435C268421187E530DBC76168E1huaweicom_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Cc: "altoext@ietf.org" <altoext@ietf.org>, "Vijay K. Gurbani" <vkg@bell-labs.com>, "alto@ietf.org" <alto@ietf.org>, Spencer Dawkins <spencer@wonderhamster.org>, ZongNing <zongning@huawei.com>
Subject: Re: [altoext] [alto] i2aex BOF - SDN Use Case
X-BeenThere: altoext@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Non-WG list for discussions related to ALTO Protocol Extensions <altoext.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/altoext>, <mailto:altoext-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/altoext>
List-Post: <mailto:altoext@ietf.org>
List-Help: <mailto:altoext-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/altoext>, <mailto:altoext-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 26 Mar 2012 20:52:14 -0000

Sorry I could not attend today's meeting, as I was in ER.
Comments r in line.

Sent from my iPad

On Mar 25, 2012, at 2:05 PM, "Ping Pan" <ping@pingpan.org<mailto:ping@pingpan.org>> wrote:

Concur.

ALTO is currently used in support of P2P and CDN operation. It has the functionality to query the network topological data. However that's where the similarity with SDN ends. Running them together, how are they inter-related?
That is the purpose of this draft to handle

Also you have brought up the concept of SDN Domains. What are they? Who owns them? Why do we need them? For scaling? For admin? If for scaling, SDN controller intrinsically has no scaling problem per sa. For admin, SDN is to offer an overlay architecture on top of the network with a uniformed view from application perspective, which is opposite of having some sort of peering models. Please elaborate your thoughts.
SDN domains are built by network operator for flexible admin purpose. It depends on the scale of underlying network that operator how to divide whole network into SDN domains. For some small scale data centers, only one SDN domain may be enough. For some carrier’s large networks, it make sense to operate thru several SDNs. Letting single one SDN controller to overview whole ATT/Verizon’s network seems not realistic. For example, Operator can divide its network into different SDN domains based on physical locations. It can lease such part of its network to local content provider, or DC, etc. Such deployment scenario requires SDN controller providing powerful network service capability to applications which depends on implementation. Here we only talk about some basic requirements for SDN, like collecting fine grain underlying device information. This information can be shared with ALTO. ALTO protocol can be simplified with SDN, and SDN can use ALTO’s result to provide more flexible service to user applications in path defining. Here we are assuming SDN controller works as an open platform based on that user can build its own applications.

On Sun, Mar 25, 2012 at 12:52 PM, ZongNing <zongning@huawei.com<mailto:zongning@huawei.com>> wrote:
Hi, Tina,

Very interesting topic! One comment after a quick review:
In page 5 in the slides, it seems that you prefer to put ALTO on top of SDN controller. I am wondering if the primary goal of ALTO-SDN is for better SDN control or better ALTO service?
We are not saying the goal is for better SDN or better ALTO. We are talking both of them can benefit from each other when they work interactively. Since SDN is only emerging and has no such real products, so here we can say it may be better for ALTO.  While with the development and implementation of SDN techniques, we think SDN can benefit as well from ALTO and provide in path defining and selection at user application level.
If the goal is for better SDN, then how ALTO could help SDN? Receive information from SDN controller, then combine with other ALTO information and feedback to SDN?
Also in page 5, I don't understand why the data are forwarded from SDN to ALTO?
Would you please elaborate this? Thanks.

-Ning
________________________________________
From: altoext-bounces@ietf.org<mailto:altoext-bounces@ietf.org> [altoext-bounces@ietf.org<mailto:altoext-bounces@ietf.org>] on behalf of Tina TSOU [Tina.Tsou.Zouting@huawei.com<mailto:Tina.Tsou.Zouting@huawei.com>]
Sent: Sunday, March 25, 2012 5:14 AM
To: Vijay K. Gurbani; Spencer Dawkins
Cc: altoext@ietf.org<mailto:altoext@ietf.org>; alto@ietf.org<mailto:alto@ietf.org>
Subject: Re: [altoext] i2aex BOF - SDN Use Case

Attached are the updated slides after some discussion with chairs. Thank you.
C u soon in Paris.

Tina


> -----Original Message-----
> From: altoext-bounces@ietf.org<mailto:altoext-bounces@ietf.org> [mailto:altoext-bounces@ietf.org<mailto:altoext-bounces@ietf.org>] On
> Behalf Of Tina TSOU
> Sent: Friday, March 23, 2012 4:34 PM
> To: Vijay K. Gurbani; Spencer Dawkins
> Cc: altoext@ietf.org<mailto:altoext@ietf.org>; alto@ietf.org<mailto:alto@ietf.org>
> Subject: [altoext] i2aex BOF - SDN Use Case
>
> Dear i2aex BoF chairs,
> Attached please find slides for
>
> Infrastructure to Application Exposure (I2AEX) Use Case
>
>  - Software Define/Driven Networking (SDN)
>
>
> Comments are welcome.
>
>
> Tina
_______________________________________________
alto mailing list
alto@ietf.org<mailto:alto@ietf.org>
https://www.ietf.org/mailman/listinfo/alto