[dc] Announcing the i2aex BoF

Spencer Dawkins <spencer@wonderhamster.org> Wed, 21 March 2012 17:05 UTC

Return-Path: <spencer@wonderhamster.org>
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 B3BF121F85A4; Wed, 21 Mar 2012 10:05:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.932
X-Spam-Level:
X-Spam-Status: No, score=-102.932 tagged_above=-999 required=5 tests=[AWL=-0.333, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 lzd0-eBg2F1n; Wed, 21 Mar 2012 10:05:22 -0700 (PDT)
Received: from mout.perfora.net (mout.perfora.net [74.208.4.194]) by ietfa.amsl.com (Postfix) with ESMTP id 1285A21F84F7; Wed, 21 Mar 2012 10:05:22 -0700 (PDT)
Received: from [192.168.2.9] (cpe-76-182-255-76.tx.res.rr.com [76.182.255.76]) by mrelay.perfora.net (node=mrus2) with ESMTP (Nemesis) id 0MGis5-1S6KVm1sxN-00EE8B; Wed, 21 Mar 2012 13:05:21 -0400
Message-ID: <4F6A0A41.3050006@wonderhamster.org>
Date: Wed, 21 Mar 2012 12:05:05 -0500
From: Spencer Dawkins <spencer@wonderhamster.org>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:10.0.2) Gecko/20120216 Thunderbird/10.0.2
MIME-Version: 1.0
To: apps-discuss@ietf.org, opsawg@ietf.org, tsvwg@ietf.org, cdni@ietf.org, dc@ietf.org
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
X-Provags-ID: V02:K0:37kwmDyh1PGtEv1+GuK5JGGumWHU/GEI1BmdmoUug8c hWnMw72RwkhAxsiU6NG7N79qlJQ2XV6Z5awI9Cd48xzXeg5xFU 776j0JR0CGgz/Me5v58EWM1FwIxl3WeJpt1rC5lVJTGIRDApNj Y5EGXhxNayCTqYWx4P27UPyH5xJ2sNZ6axI84XY2/21DUaEibd X2jyXDdNbpDdekwqfzSMsiWaa0wMb7Wy87HIiScZG9r+c85VYG tfT5MBRwtPWjQlRfl1m4rnht0aaWMtrR59lQpOw2/QpT5+wlQu epn5Vg7T+8MSL4TRS9TDCWCg16mEyA/Z8zH6ksI23CL/SnqZNv P5TKeqNw8EBjZjP2pah70i10iOL6ag912CaluRy5Y
Subject: [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: Wed, 21 Mar 2012 17:05:22 -0000

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