Re: [dc] Announcing the i2aex BoF
Bhumip Khasnabish <vumip1@gmail.com> Wed, 21 March 2012 17:50 UTC
Return-Path: <vumip1@gmail.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 9C90421E808C; Wed, 21 Mar 2012 10:50:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.492
X-Spam-Level:
X-Spam-Status: No, score=-2.492 tagged_above=-999 required=5 tests=[AWL=-0.560, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1, SARE_HTML_USL_OBFU=1.666]
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 Wd0wZ7JN4zPv; Wed, 21 Mar 2012 10:50:31 -0700 (PDT)
Received: from mail-yx0-f172.google.com (mail-yx0-f172.google.com [209.85.213.172]) by ietfa.amsl.com (Postfix) with ESMTP id 381DB21E8040; Wed, 21 Mar 2012 10:50:31 -0700 (PDT)
Received: by yenm5 with SMTP id m5so1308124yen.31 for <multiple recipients>; Wed, 21 Mar 2012 10:50:30 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=zC0cm5QYiRjo5405z/iXCy1JqbVw+rHCtRUW70A0pPs=; b=NP27W+seIGqA/JW8UnZjgNF7vOZqgqPG14AV1VMOkwJNGyLAd/ZqB+4FqhiGkRyY4s aOIeEkHFf1l2GZq6iOhKxR1r8yAoLez+rpVVtfDSZU2D+uICDGnDRah5AlIwRx25Rjkd qwjgTH5llq7Ck5jbhHKg4xlNRpXG2yNAaWMdRnvj3vI5r5ESAZCqBxN5Ks6/VMmTo1yG 36BoxmMVlnNOeK/7oAgGV6uauoWZyYA/gfbTTq2u9lR6Uyizye0S1RLbZVedXLo+T+9G jRTYP8qX1ROLmY/r1jpHpIMkOi07DC0n3DvoRSvqoaYQhows1SrKqq/wY+0Jds0HQs1U JBhw==
MIME-Version: 1.0
Received: by 10.182.54.114 with SMTP id i18mr5776882obp.49.1332352230691; Wed, 21 Mar 2012 10:50:30 -0700 (PDT)
Received: by 10.182.12.234 with HTTP; Wed, 21 Mar 2012 10:50:30 -0700 (PDT)
In-Reply-To: <4F6A0A41.3050006@wonderhamster.org>
References: <4F6A0A41.3050006@wonderhamster.org>
Date: Wed, 21 Mar 2012 13:50:30 -0400
Message-ID: <CANtnpwiCn5X=hcSfhXObaw7ruFiCFXp87Ryd==sA_+iy1S+kHw@mail.gmail.com>
From: Bhumip Khasnabish <vumip1@gmail.com>
To: Spencer Dawkins <spencer@wonderhamster.org>
Content-Type: multipart/alternative; boundary="14dae93a122f6d130b04bbc46d8a"
Cc: dc@ietf.org, opsawg@ietf.org, cdni@ietf.org, tsvwg@ietf.org, apps-discuss@ietf.org
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: Wed, 21 Mar 2012 17:50:32 -0000
Hi Spencer, Is this similar to Cloud Infrastructure Management Interface (CIMI) Model and REST Interface over HTTP An Interface for Managing Cloud Infrastructure( http://dmtf.org/standards/cloud)? What is the trigger for this?! Thanks for clarifying. Best. Bhumip On Wed, Mar 21, 2012 at 1:05 PM, Spencer Dawkins <spencer@wonderhamster.org>wrote: > 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<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<http://www.ietf.org/proceedings/83/agenda/agenda-83-i2aex.txt> > ______________________________**_________________ > dc mailing list > dc@ietf.org > https://www.ietf.org/mailman/**listinfo/dc<https://www.ietf.org/mailman/listinfo/dc> >
- [dc] Announcing the i2aex BoF Spencer Dawkins
- Re: [dc] Announcing the i2aex BoF Bhumip Khasnabish
- Re: [dc] Announcing the i2aex BoF David Harrington
- Re: [dc] Announcing the i2aex BoF Linda Dunbar