Re: [dc] Announcing the i2aex BoF

Linda Dunbar <linda.dunbar@huawei.com> Thu, 22 March 2012 19:43 UTC

Return-Path: <linda.dunbar@huawei.com>
X-Original-To: dc@ietfa.amsl.com
Delivered-To: dc@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5638621E8028; Thu, 22 Mar 2012 12:43:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.553
X-Spam-Level:
X-Spam-Status: No, score=-2.553 tagged_above=-999 required=5 tests=[AWL=0.046, BAYES_00=-2.599]
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 pM24XEoCbLuy; Thu, 22 Mar 2012 12:43:08 -0700 (PDT)
Received: from dfwrgout.huawei.com (dfwrgout.huawei.com [206.16.17.72]) by ietfa.amsl.com (Postfix) with ESMTP id EBA3121F85D6; Thu, 22 Mar 2012 12:43:07 -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 AEP68367; Thu, 22 Mar 2012 15:43:06 -0400 (EDT)
Received: from DFWEML404-HUB.china.huawei.com (10.193.5.203) by dfweml201-edg.china.huawei.com (172.18.9.107) with Microsoft SMTP Server (TLS) id 14.1.323.3; Thu, 22 Mar 2012 12:41:57 -0700
Received: from DFWEML505-MBX.china.huawei.com ([10.124.31.100]) by dfweml404-hub.china.huawei.com ([10.193.5.203]) with mapi id 14.01.0323.003; Thu, 22 Mar 2012 12:42:00 -0700
From: Linda Dunbar <linda.dunbar@huawei.com>
To: Spencer Dawkins <spencer@wonderhamster.org>, "apps-discuss@ietf.org" <apps-discuss@ietf.org>, "opsawg@ietf.org" <opsawg@ietf.org>, "tsvwg@ietf.org" <tsvwg@ietf.org>, "cdni@ietf.org" <cdni@ietf.org>, "dc@ietf.org" <dc@ietf.org>
Thread-Topic: [dc] Announcing the i2aex BoF
Thread-Index: AQHNB4Tsxr8YheQTEUmLhaS9a9PrIpZ2th0g
Date: Thu, 22 Mar 2012 19:42:00 +0000
Message-ID: <4A95BA014132FF49AE685FAB4B9F17F632E4F713@dfweml505-mbx>
References: <4F6A0A41.3050006@wonderhamster.org>
In-Reply-To: <4F6A0A41.3050006@wonderhamster.org>
Accept-Language: en-US, zh-CN
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.47.144.61]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Subject: Re: [dc] Announcing the i2aex BoF
X-BeenThere: dc@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF Data Center Mailing List <dc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dc>, <mailto:dc-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dc>
List-Post: <mailto:dc@ietf.org>
List-Help: <mailto:dc-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dc>, <mailto:dc-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 22 Mar 2012 19:43:09 -0000

Are there specific applications in mind for the Intra-structure to expose to? 

Linda

> -----Original Message-----
> From: dc-bounces@ietf.org [mailto:dc-bounces@ietf.org] On Behalf Of
> Spencer Dawkins
> Sent: Wednesday, March 21, 2012 12:05 PM
> To: apps-discuss@ietf.org; opsawg@ietf.org; tsvwg@ietf.org;
> cdni@ietf.org; dc@ietf.org
> Subject: [dc] Announcing the i2aex BoF
> 
> Hi all,
> 
> David Harrington asked me to act as BoF Shepherd for the
> Infrastructure-to-application Information Exposure (i2aex) BoF, and I
> wanted to make sure that a broad community of interest was aware of
> this
> BoF, especially since the BoF is scheduled for Monday, Afternoon
> Session
> 1, at 1300 PM.
> 
> Preliminary discussion has been going on for some time now on the
> altoext@ietf.org mailing list, mainly among people in some way involved
> in the standardization the ALTO protocol. In order to have a
> conversation that's as productive as possible in Paris, we would really
> like to invite people who are involved on different sides of the same
> problem to bring their perspective as well.
> 
> Here's a short description, with the usual pointers. Follow-ups to
> altoext@ietf.org, please.
> 
> The goal of the (non-WG-forming) BoF is to investigate infrastructure-
> to-application information exposure and communications requirements in
> fully controlled (e.g., data centers) or partially controlled
> environments (e.g. CDN). Existing mechanisms such as SNMP, IGP, BGP and
> other protocols that monitor and manage infrastructure may reveal much
> if not all of the possibly required information, but are typically only
> accessible to the operators of the network infrastructure. CDNs and
> data
> center applications have some requirements to operate over the Internet,
> possibly between administrative domains. On the other hand, the ALTO
> protocol was initially designed to address peer-to-peer application
> requirements, but was designed to be extensible and could be quite
> easily adapted to export the pieces of information that CDN and data
> center applications would benefit from.
> 
> The BoF will thus primarily seek an answer to the following questions:
> 
>    + do CDN and data center applications require (or benefit in a
>      significant way from) accessing to information that cannot be made
>      available through existing mechanisms in a practical way?
> 
>    + is an extension to the ALTO protocol (or to any other protocol) a
>      viable way to address such requirements?
> 
> Additional information about the topic is available on the BoF wiki
> entry: http://trac.tools.ietf.org/bof/trac/#Transport
> 
> The provisional agenda for the meeting is online at:
> http://www.ietf.org/proceedings/83/agenda/agenda-83-i2aex.txt
> _______________________________________________
> dc mailing list
> dc@ietf.org
> https://www.ietf.org/mailman/listinfo/dc