Re: [p2pi] Refining the ALTO problem statement [Was: Re: discussing P2PI-related standardization in Dublin]
"Vijay K. Gurbani" <vkg@alcatel-lucent.com> Fri, 13 June 2008 15:53 UTC
Return-Path: <p2pi-bounces@ietf.org>
X-Original-To: p2pi-archive@ietf.org
Delivered-To: ietfarch-p2pi-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id B00033A69EC; Fri, 13 Jun 2008 08:53:46 -0700 (PDT)
X-Original-To: p2pi@core3.amsl.com
Delivered-To: p2pi@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 804733A69EC for <p2pi@core3.amsl.com>; Fri, 13 Jun 2008 08:53:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.493
X-Spam-Level:
X-Spam-Status: No, score=-2.493 tagged_above=-999 required=5 tests=[AWL=0.106, BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2BLFlGKVI-1J for <p2pi@core3.amsl.com>; Fri, 13 Jun 2008 08:53:44 -0700 (PDT)
Received: from ihemail3.lucent.com (ihemail3.lucent.com [135.245.0.37]) by core3.amsl.com (Postfix) with ESMTP id 719F23A698D for <p2pi@ietf.org>; Fri, 13 Jun 2008 08:53:43 -0700 (PDT)
Received: from umail.lucent.com (h135-3-40-61.lucent.com [135.3.40.61]) by ihemail3.lucent.com (8.13.8/IER-o) with ESMTP id m5DFsAWW014688 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 13 Jun 2008 10:54:10 -0500 (CDT)
Received: from [135.185.244.90] (il0015vkg1.ih.lucent.com [135.185.244.90]) by umail.lucent.com (8.13.8/TPES) with ESMTP id m5DFs77Z026730; Fri, 13 Jun 2008 10:54:07 -0500 (CDT)
Message-ID: <48529822.2030101@alcatel-lucent.com>
Date: Fri, 13 Jun 2008 10:54:10 -0500
From: "Vijay K. Gurbani" <vkg@alcatel-lucent.com>
Organization: Bell Labs Security Technology Research Group
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: stefano previdi <sprevidi@cisco.com>
References: <C47801ED.68DB8%sprevidi@cisco.com>
In-Reply-To: <C47801ED.68DB8%sprevidi@cisco.com>
X-Scanned-By: MIMEDefang 2.57 on 135.245.2.37
Cc: "p2pi@ietf.org" <p2pi@ietf.org>
Subject: Re: [p2pi] Refining the ALTO problem statement [Was: Re: discussing P2PI-related standardization in Dublin]
X-BeenThere: p2pi@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: P2P Infrastructure Discussion <p2pi.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/p2pi>, <mailto:p2pi-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/p2pi>
List-Post: <mailto:p2pi@ietf.org>
List-Help: <mailto:p2pi-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/p2pi>, <mailto:p2pi-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: p2pi-bounces@ietf.org
Errors-To: p2pi-bounces@ietf.org
stefano previdi wrote: > Enrico, > > I mostly agree mostly with everything below. Stefano: Thank you. > My suggestion (as a routing guy more than an apps guy) is also to > scope what could be extended/enhanced in routing protocols in order > to improve localization mechanisms (whatever they are). I think the issue of scoping is something that we definitely have to work on. I also suspect that ALTO solutions deployed by network operators will probably make use of information carried in routing protocols and, if it turns out that extensions to such protocols may be beneficial, they should be specified in coordination with ALTO, but probably in the Routing area. At the current time, the viewpoints of the ADs appear to be that ALTO will be either in RAI or Apps. > As an example, we have extended ISIS routing protocol in order to > carry some application related information (at this stage is an empty > container) and probably these kind of enhancements may have a use in > localization/oracle services. It would be great if you could describe this in a draft. One of the points we made in our workshop paper was the need for layer cooperation. Your existing work would go a long way to provide some illumination of feasibility in that area. Ciao. - vijay -- Vijay K. Gurbani, Bell Laboratories, Alcatel-Lucent 2701 Lucent Lane, Rm. 9F-546, Lisle, Illinois 60532 (USA) Email: vkg@{alcatel-lucent.com,bell-labs.com,acm.org} WWW: http://www.alcatel-lucent.com/bell-labs _______________________________________________ p2pi mailing list p2pi@ietf.org https://www.ietf.org/mailman/listinfo/p2pi
- [p2pi] discussing P2PI-related standardization in… Lars Eggert
- Re: [p2pi] discussing P2PI-related standardizatio… Lars Eggert
- Re: [p2pi] discussing P2PI-related standardizatio… Vijay K. Gurbani
- Re: [p2pi] discussing P2PI-related standardizatio… Peterson, Jon
- Re: [p2pi] discussing P2PI-related standardizatio… Livingood, Jason
- [p2pi] Refining the ALTO problem statement [Was: … Enrico Marocco
- Re: [p2pi] Refining the ALTO problem statement [W… stefano previdi
- Re: [p2pi] Refining the ALTO problem statement [W… John Leslie
- Re: [p2pi] Refining the ALTO problem statement [W… Vijay K. Gurbani
- Re: [p2pi] Refining the ALTO problem statement [W… Lars Eggert
- Re: [p2pi] Refining the ALTO problem statement [W… Lars Eggert
- Re: [p2pi] discussing P2PI-related standardizatio… Lars Eggert
- Re: [p2pi] Refining the ALTO problem statement [W… Enrico Marocco
- Re: [p2pi] Refining the ALTO problem statement John Leslie
- Re: [p2pi] discussing P2PI-related standardizatio… Richard Bennett
- Re: [p2pi] discussing P2PI-related standardizatio… Lars Eggert
- Re: [p2pi] Refining the ALTO problem statement [W… Lars Eggert
- Re: [p2pi] Refining the ALTO problem statement Lars Eggert
- Re: [p2pi] Refining the ALTO problem statement [W… stefano previdi
- Re: [p2pi] Refining the ALTO problem statement Spencer Dawkins
- Re: [p2pi] Refining the ALTO problem statement John Leslie
- Re: [p2pi] Refining the ALTO problem statement John Leslie
- Re: [p2pi] Refining the ALTO problem statement Spencer Dawkins
- Re: [p2pi] Refining the ALTO problem statement [W… Henning Schulzrinne
- Re: [p2pi] Refining the ALTO problem statement [W… Stanislav Shalunov
- Re: [p2pi] Refining the ALTO problem statement [W… Lars Eggert
- Re: [p2pi] Refining the ALTO problem statement Lars Eggert
- Re: [p2pi] Refining the ALTO problem statement Spencer Dawkins
- Re: [p2pi] Refining the ALTO problem statement John Leslie
- Re: [p2pi] Refining the ALTO problem statement Robert Snively
- Re: [p2pi] Refining the ALTO problem statement Stanislav Shalunov
- Re: [p2pi] Refining the ALTO problem statement Laird Popkin
- Re: [p2pi] Refining the ALTO problem statement stefano previdi
- Re: [p2pi] Refining the ALTO problem statement Stanislav Shalunov
- Re: [p2pi] Refining the ALTO problem statement Lars Eggert