Re: [p2pi] Information in an ALTO protocol
"Vijay K. Gurbani" <vkg@alcatel-lucent.com> Thu, 14 August 2008 19:29 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 1606F3A6886; Thu, 14 Aug 2008 12:29:03 -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 497713A6822 for <p2pi@core3.amsl.com>; Thu, 14 Aug 2008 12:29:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[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 e8I9f7DK5PIt for <p2pi@core3.amsl.com>; Thu, 14 Aug 2008 12:29:01 -0700 (PDT)
Received: from ihemail2.lucent.com (ihemail2.lucent.com [135.245.0.35]) by core3.amsl.com (Postfix) with ESMTP id 180B43A68BF for <p2pi@ietf.org>; Thu, 14 Aug 2008 12:29:00 -0700 (PDT)
Received: from umail.lucent.com (h135-3-40-61.lucent.com [135.3.40.61]) by ihemail2.lucent.com (8.13.8/IER-o) with ESMTP id m7EJSx5u020494 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 14 Aug 2008 14:29:00 -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 m7EJSpxc011569; Thu, 14 Aug 2008 14:28:53 -0500 (CDT)
Message-ID: <48A48779.60507@alcatel-lucent.com>
Date: Thu, 14 Aug 2008 14:28:57 -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: rbriscoe@jungle.bt.co.uk
References: <74CCBBDF76102846AFA7B29F3A98D3F60107C32A@PACDCEXCMB06.cable.comcast.com> <200808120901.m7C91q6H012752@bagheera.jungle.bt.co.uk>
In-Reply-To: <200808120901.m7C91q6H012752@bagheera.jungle.bt.co.uk>
X-Scanned-By: MIMEDefang 2.57 on 135.245.2.35
Cc: "p2pi@ietf.org" <p2pi@ietf.org>
Subject: Re: [p2pi] Information in an ALTO protocol
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-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Sender: p2pi-bounces@ietf.org
Errors-To: p2pi-bounces@ietf.org
Bob Briscoe wrote: > I want the charter to acknowledge the same old point I started with at > the mic and on the list: > - that unconditional localisation will not be sufficient for /any/ ISP, Bob: It is my belief that the post-BoF charter acknowledges this (please see http://alto.tilab.com/docs/charter.txt). That said ... > so the parameters that the ALTO service will have to gather are more > than just the static ones: topology and policies I think that which parameters to gather will turn out to be an interesting topic to nail down. Enrico had sent an email out last week to try and gather this information; there was some discussion and the issue got sidetracked. So, I'd like to refocus on that issue. At present, we have the following discrete pieces of information mentioned in the post-BoF charter: (1) Routing preferences (2) Priority values (3) AS numbers (4) Geographic location Add to this the two more: (5) Policies (6) Topology 1, 2, and 5 are something that the network operator is in possession of. 3 and 4 can be gleaned in some manner (probably not using any standardized APIs but well known services, nonetheless.) 6 can be provided by the network operator or approximated using synthetic coordinate systems and the like. Information that has been deemed out of scope based on list discussion is: (1) Last hop bandwidth (reason: too much uncertainty -- are we talking about upload or download bandwidth? Provisioned band- width or current snapshot? User privacy concerns, ISP marketing concerns, etc. In short, while this is a good research problem, it may not be a good piece of information to be provided by ALTO.) What other sort of information should be a focus of ALTO? Thanks, - 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] After-BoF charter Enrico Marocco
- Re: [p2pi] After-BoF charter Lars Eggert
- Re: [p2pi] After-BoF charter John Leslie
- Re: [p2pi] After-BoF charter Laird Popkin
- Re: [p2pi] After-BoF charter David R Oran
- Re: [p2pi] After-BoF charter John Leslie
- Re: [p2pi] After-BoF charter David R Oran
- Re: [p2pi] After-BoF charter Bob Briscoe
- Re: [p2pi] After-BoF charter Bob Briscoe
- Re: [p2pi] After-BoF charter Bruce Davie
- Re: [p2pi] After-BoF charter Laird Popkin
- Re: [p2pi] After-BoF charter Woundy, Richard
- Re: [p2pi] After-BoF charter Stanislav Shalunov
- Re: [p2pi] After-BoF charter Bob Briscoe
- Re: [p2pi] After-BoF charter Laird Popkin
- Re: [p2pi] After-BoF charter Enrico Marocco
- Re: [p2pi] After-BoF charter Enrico Marocco
- Re: [p2pi] After-BoF charter Laird Popkin
- Re: [p2pi] Information in an ALTO protocol Vijay K. Gurbani
- Re: [p2pi] Information in an ALTO protocol John Leslie
- Re: [p2pi] Information in an ALTO protocol Laird Popkin
- Re: [p2pi] Information in an ALTO protocol Vijay K. Gurbani
- Re: [p2pi] Information in an ALTO protocol Yu-Shun Wang
- Re: [p2pi] Information in an ALTO protocol John Leslie
- Re: [p2pi] Information in an ALTO protocol Woundy, Richard
- Re: [p2pi] Information in an ALTO protocol John Leslie
- Re: [p2pi] After-BoF charter Bob Briscoe
- Re: [p2pi] After-BoF charter Bob Briscoe
- Re: [p2pi] After-BoF charter Vijay K. Gurbani
- Re: [p2pi] After-BoF charter Stanislav Shalunov
- Re: [p2pi] After-BoF charter Laird Popkin
- Re: [p2pi] Information in an ALTO protocol Woundy, Richard
- Re: [p2pi] Information in an ALTO protocol Woundy, Richard
- Re: [p2pi] Information in an ALTO protocol Reinaldo Penno
- Re: [p2pi] Information in an ALTO protocol Woundy, Richard