[irs-discuss] IRS and I2AEX BoF

"Vijay K. Gurbani" <vkg@bell-labs.com> Mon, 12 November 2012 15:21 UTC

Return-Path: <vkg@bell-labs.com>
X-Original-To: irs-discuss@ietfa.amsl.com
Delivered-To: irs-discuss@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2C2C821F8682 for <irs-discuss@ietfa.amsl.com>; Mon, 12 Nov 2012 07:21:31 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -107.932
X-Spam-Level:
X-Spam-Status: No, score=-107.932 tagged_above=-999 required=5 tests=[AWL=-1.333, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id wvMEWeo3-jZD for <irs-discuss@ietfa.amsl.com>; Mon, 12 Nov 2012 07:21:30 -0800 (PST)
Received: from ihemail3.lucent.com (ihemail3.lucent.com [135.245.0.37]) by ietfa.amsl.com (Postfix) with ESMTP id 0D5B421F860D for <irs-discuss@ietf.org>; Mon, 12 Nov 2012 07:21:29 -0800 (PST)
Received: from usnavsmail4.ndc.alcatel-lucent.com (usnavsmail4.ndc.alcatel-lucent.com [135.3.39.12]) by ihemail3.lucent.com (8.13.8/IER-o) with ESMTP id qACFLPTn018011 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL) for <irs-discuss@ietf.org>; Mon, 12 Nov 2012 09:21:25 -0600 (CST)
Received: from umail.lucent.com (umail-ce2.ndc.lucent.com [135.3.40.63]) by usnavsmail4.ndc.alcatel-lucent.com (8.14.3/8.14.3/GMO) with ESMTP id qACFLPcD020436 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT) for <irs-discuss@ietf.org>; Mon, 12 Nov 2012 09:21:25 -0600
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 qACFLOGJ021157 for <irs-discuss@ietf.org>; Mon, 12 Nov 2012 09:21:25 -0600 (CST)
Message-ID: <50A11442.5080908@bell-labs.com>
Date: Mon, 12 Nov 2012 09:22:42 -0600
From: "Vijay K. Gurbani" <vkg@bell-labs.com>
Organization: Bell Laboratories, Alcatel-Lucent
User-Agent: Mozilla/5.0 (X11; Linux i686; rv:13.0) Gecko/20120605 Thunderbird/13.0
MIME-Version: 1.0
To: irs-discuss@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.37
X-Scanned-By: MIMEDefang 2.64 on 135.3.39.12
Subject: [irs-discuss] IRS and I2AEX BoF
X-BeenThere: irs-discuss@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Interface to The Internet Routing System \(IRS\)" <irs-discuss.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/irs-discuss>, <mailto:irs-discuss-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/irs-discuss>
List-Post: <mailto:irs-discuss@ietf.org>
List-Help: <mailto:irs-discuss-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/irs-discuss>, <mailto:irs-discuss-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 12 Nov 2012 15:21:31 -0000

All: During the discussion in Atlanta, I had pointed to some
overlap between IRS and a BoF held in Paris called i2aex (Infrastructure
to Application Information Exchange).  i2aex maintains that the
network infrastructure has volumnious amount of information that is
disseminated among the network infrastructure entities using many
existing protocols: BGP, IGP, netflow, CLI/SSH, SNMP, etc.  Applications
running outside the network infrastructure (or even in the network
infrastructure) would likely benefit from this information.  So, the
question is: in a fully- and partially-controlled environments,
how do we disseminate this information to the applications?
Do we need a new protocol for this?  Can we extend ALTO since a lot
of the requirements for this work came into the ALTO WG initially?

To some extent (modulo whether ALTO can be a candidate protocol), the
above captures the essence of slide 3 in [1].

We had a good discussion that may have some bearing on IRS.  For folks
who are interested, the slides and chunked audio stream (i.e., audio
stream corresponding to each agenda item discussion) is at [2].  i2aex
met as a non-WG forming BoF as well in Paris and concluded after having
met its objective in winnowing down the set of potential protocols that
could serve as an i2aex interface [3].

I understand that IRS is not looking for a specific protocol right now,
but some of what was discussed during i2aex may be of interest to the
IRS folks.

Please let me and Spencer Dawkins (co-chairs of i2aex BoF) know if you
have any specific questions.

[1] http://www.ietf.org/proceedings/85/slides/slides-85-irs-1.pptx
[2] http://www.ietf.org/proceedings/83/minutes/minutes-83-i2aex.html
[3] http://www.ietf.org/mail-archive/web/altoext/current/msg00083.html

Thanks,

- vijay
-- 
Vijay K. Gurbani, Bell Laboratories, Alcatel-Lucent
1960 Lucent Lane, Rm. 9C-533, Naperville, Illinois 60563 (USA)
Email: vkg@{bell-labs.com,acm.org} / vijay.gurbani@alcatel-lucent.com
Web:   http://ect.bell-labs.com/who/vkg/