IETF Logo Mail Archive

Re: [altoext] i2aex BOF - Large Bandwidth Use Case

DIEGO LOPEZ GARCIA <diego@tid.es> Sun, 08 April 2012 14:14 UTC

Return-Path: <diego@tid.es>
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 445A321F855D for <altoext@ietfa.amsl.com>; Sun, 8 Apr 2012 07:14:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.999
X-Spam-Level:
X-Spam-Status: No, score=-2.999 tagged_above=-999 required=5 tests=[AWL=1.000, BAYES_50=0.001, RCVD_IN_DNSWL_MED=-4]
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 U8NibMp6k+NT for <altoext@ietfa.amsl.com>; Sun, 8 Apr 2012 07:14:42 -0700 (PDT)
Received: from correo-bck.tid.es (correo-bck.tid.es [195.235.93.200]) by ietfa.amsl.com (Postfix) with ESMTP id 166B321F854A for <altoext@ietf.org>; Sun, 8 Apr 2012 07:14:41 -0700 (PDT)
Received: from sbrightmailg02.hi.inet (Sbrightmailg02.hi.inet [10.95.78.105]) by tid.hi.inet (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0M2500C86ZKEBG@tid.hi.inet> for altoext@ietf.org; Sun, 08 Apr 2012 16:14:38 +0200 (MEST)
Received: from vanvan (vanvan.hi.inet [10.95.78.49]) by sbrightmailg02.hi.inet (Symantec Messaging Gateway) with SMTP id C1.AE.02597.E4D918F4; Sun, 08 Apr 2012 16:14:38 +0200 (CEST)
Received: from correo.tid.es (mailhost.hi.inet [10.95.64.100]) by tid.hi.inet (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTPS id <0M2500C82ZKEBG@tid.hi.inet> for altoext@ietf.org; Sun, 08 Apr 2012 16:14:38 +0200 (MEST)
Received: from EXCLU2K7.hi.inet ([10.95.67.65]) by htcasmad2.hi.inet ([192.168.0.2]) with mapi; Sun, 08 Apr 2012 16:14:38 +0200
Date: Sun, 08 Apr 2012 16:14:24 +0200
From: DIEGO LOPEZ GARCIA <diego@tid.es>
In-reply-to: <4F7C862C.1070504@grotto-networking.com>
To: Greg Bernstein <gregb@grotto-networking.com>
Message-id: <8E665867-9576-4806-890C-4622873F98D3@tid.es>
MIME-version: 1.0
Content-type: text/plain; charset="Windows-1252"
Content-language: en-US
Content-transfer-encoding: quoted-printable
Accept-Language: en-US
Thread-topic: [altoext] i2aex BOF - Large Bandwidth Use Case
Thread-index: Ac0VkeZ6o3aB94v7TYqr6uKqwQKO+A==
acceptlanguage: en-US
X-AuditID: 0a5f4e69-b7f4d6d000000a25-ce-4f819d4e9ecd
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFlrAKsWRmVeSWpSXmKPExsXCFe9nqOs3t9HfYPZORYtbkyexOzB6LFny kymAMYrLJiU1J7MstUjfLoEr4/G0XqaCuYIVjSctGxi/8HYxcnJICJhIzP+ynBXCFpO4cG89 WxcjF4eQwHZGiS2f97OAJIQEfjNKXHpnCpFoZJSY3rmUHSTBIqAq0fFuHhuIzSagLtFy9BtY g7CAtUTLsntgcU4BU4k/Ly6C2SICBhLLzj8Aq2EW0JTYd+oIkM3BwStgKbH6YQJImFdAUOLH 5HtQJXoSH//cZoSwxSWaW29CxbUlnry7AHY0I9DR30+tYYIYbyPx+WU3lK0n0ffpFTNEjajE nfb1jBBPCkgs2XOeGcIWlXj5+B8r1MPMEr1rJrBOYBSfheSOWUjumIXkjllI7ljAyLKKUaw4 qSgzPaMkNzEzJ93ASC8jUy8zL7VkEyMkijJ3MC7fqXKIUYCDUYmHN0K03l+INbGsuDL3EKMk B5OSKO+hGY3+QnxJ+SmVGYnFGfFFpTmpxYcYJTiYlUR4mfuAcrwpiZVVqUX5MCkZDg4lCd7e OUApwaLU9NSKtMwcYKqASTNxcIK08wC1F4DU8BYXJOYWZ6ZD5E8xqnI8P9R7hVGIJS8/L1VK nDcTpEgApCijNA9uzitGcaCDhXlLQbI8wGQHN+EV0HAmoOE1r+pBhpckIqSkGhhXXPmXVnXg J9f6Mnd17/sdhVfnF9ye/+CNleRZ3bg36Q95f/yVmX+p/Y2C90/HRZMsxTfObjb79MP03Lxv +QpmIj/mFZc8nlO1Kcb6TmzuAdtb2QfVPkgynn+y8WBMVoytms6GVfXbFk5azxl00dZzYYjS 3b3Sb29v5M544v11V17txpojvPmFSizFGYmGWsxFxYkAkeqCIzMDAAA=
References: <7AEB3D6833318045B4AE71C2C87E8E1720C8E5DC@dfweml511-mbx.china.huawei.com> <2C0E90B7-4B30-45F4-A7B0-1887E8654A66@cs.yale.edu> <4F6F686F.5020202@grotto-networking.com> <4F6FD6BE.2040606@cs.yale.edu> <4F71F275.4000800@grotto-networking.com> <29679E68-FD87-44EA-9908-BEE4940021D6@tid.es> <4F74A608.4060303@grotto-networking.com> <0A4496B5-1F35-4DE9-BA20-6431F880A1D4@tid.es> <4F7C862C.1070504@grotto-networking.com>
Cc: "altoext@ietf.org" <altoext@ietf.org>
Subject: Re: [altoext] i2aex BOF - Large Bandwidth 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: Sun, 08 Apr 2012 14:14:43 -0000

On 4 Apr 2012, at 19:34 , Greg Bernstein wrote:
> It is very interesting to compare the different notions of "Network as a Service" (NaaS) and see what type of additional information various NaaS notions would require from the network.
>
> . . .
>
> It seems that the graph based I2AEX extensions that we like would apply to (a) and (d), and to all casesl if traffic engineering (layer 2 or 3) is desired.  Comments? Other examples that we should look at? I'm working to formalize the graph stuff we showed at the BoF in proper ALTO protocol form and should have a draft in a few more weeks.

My take is that the NaaS proposals are tailored to the kind of user communities
they address. As far as I understand them, both Mantychore and GEYSERS intend
to provide additional tools to network engineers themselves, and therefore
expose a more detailed network abstraction. Two remarks that come to my mind
is that I definitely have to look into Quantum in more detail, and the
interesting fact that GEYSERS is intended to have bidirectional information
flows (describing computing resources as well).

The i2aex interfaces shall be able to deal to these different level of
abstraction and with the different abstract models that different use cases
rely on. For example, in the DC case a L2 abstraction seems the most
appropriate (hiding overlay details), while a CDN will likely want to know
about L3 topology details (albeit in a rather management rather than physical
manner).

And I'm looking forward to seeing your formalization proposal.

Be goode,

--
"Esta vez no fallaremos, Doctor Infierno"

Dr Diego R. Lopez
Telefonica I+D
http://people.tid.es/diego.lopez/

e-mail: diego@tid.es
Tel:    +34 913 129 041
Mobile: +34 682 051 091
-----------------------------------------


Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra política de envío y recepción de correo electrónico en el enlace situado más abajo.
This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at
http://www.tid.es/ES/PAGINAS/disclaimer.aspx

v2.23.0 | Report a Bug | By Email