[altoext] Next steps for i2aex

"Vijay K. Gurbani" <vkg@bell-labs.com> Thu, 07 June 2012 14:23 UTC

Return-Path: <vkg@bell-labs.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 4BA4921F8855 for <altoext@ietfa.amsl.com>; Thu, 7 Jun 2012 07:23:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -108.999
X-Spam-Level:
X-Spam-Status: No, score=-108.999 tagged_above=-999 required=5 tests=[AWL=1.600, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, 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 gsi8FdoEH+8a for <altoext@ietfa.amsl.com>; Thu, 7 Jun 2012 07:23:22 -0700 (PDT)
Received: from ihemail2.lucent.com (ihemail2.lucent.com [135.245.0.35]) by ietfa.amsl.com (Postfix) with ESMTP id 230A621F8611 for <altoext@ietf.org>; Thu, 7 Jun 2012 07:23:19 -0700 (PDT)
Received: from usnavsmail1.ndc.alcatel-lucent.com (usnavsmail1.ndc.alcatel-lucent.com [135.3.39.9]) by ihemail2.lucent.com (8.13.8/IER-o) with ESMTP id q57ENIgK008060 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK) for <altoext@ietf.org>; Thu, 7 Jun 2012 09:23:18 -0500 (CDT)
Received: from umail.lucent.com (umail-ce2.ndc.lucent.com [135.3.40.63]) by usnavsmail1.ndc.alcatel-lucent.com (8.14.3/8.14.3/GMO) with ESMTP id q57ENHlj012682 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT) for <altoext@ietf.org>; Thu, 7 Jun 2012 09:23:18 -0500
Received: from shoonya.ih.lucent.com (shoonya.ih.lucent.com [135.185.237.229]) by umail.lucent.com (8.13.8/TPES) with ESMTP id q57ENHvW020891 for <altoext@ietf.org>; Thu, 7 Jun 2012 09:23:17 -0500 (CDT)
Message-ID: <4FD0BAA5.40501@bell-labs.com>
Date: Thu, 07 Jun 2012 09:28:53 -0500
From: "Vijay K. Gurbani" <vkg@bell-labs.com>
Organization: Bell Laboratories, Alcatel-Lucent
User-Agent: Mozilla/5.0 (X11; Linux i686; rv:12.0) Gecko/20120430 Thunderbird/12.0.1
MIME-Version: 1.0
To: altoext@ietf.org
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
X-Scanned-By: MIMEDefang 2.57 on 135.245.2.35
X-Scanned-By: MIMEDefang 2.64 on 135.3.39.9
Subject: [altoext] Next steps for i2aex
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: Thu, 07 Jun 2012 14:23:28 -0000

Folks: The i2aex BoF was created to guide the community in arriving at
a reasonable view on a small set of protocols, one of which would then
be chosen to serve as the "i2aex protocol" to convey information from
the infrastructure to the applications.

At this point, we are not planning another BoF primarily because the
Paris BoF served its purpose in engaging the community on the choice of
a protocol for i2aex.  At the end of the BoF and subsequent discussions,
three such candidate protocols were discussed: ALTO, BGP, and SNMP,
with a reasonable amount of discussion around ALTO.

The ALTO protocol is currently in WGLC in its respective working group.
Proponents of other protocols to serve as the "i2aex protocol" are urged
to post a draft to the i2aex mailing list outlining their proposal in
detail.  We will keep the mailing list open until the Vancouver IETF
for further discussions on other candidate protocols.

Thank you,

Vijay K. Gurbani and Spencer Dawkins