IETF Logo Mail Archive

Re: [p2pi] Information in an ALTO protocol

Yu-Shun Wang <Yu-Shun.Wang@microsoft.com> Tue, 19 August 2008 18:05 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 890A53A6B49; Tue, 19 Aug 2008 11:05:41 -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 728003A6B49 for <p2pi@core3.amsl.com>; Tue, 19 Aug 2008 11:05:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.599
X-Spam-Level:
X-Spam-Status: No, score=-10.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
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 R0JOYxwMscuo for <p2pi@core3.amsl.com>; Tue, 19 Aug 2008 11:05:36 -0700 (PDT)
Received: from smtp.microsoft.com (mail1.microsoft.com [131.107.115.212]) by core3.amsl.com (Postfix) with ESMTP id B3A963A685E for <p2pi@ietf.org>; Tue, 19 Aug 2008 11:05:36 -0700 (PDT)
Received: from tk5-exhub-c104.redmond.corp.microsoft.com (157.54.88.97) by TK5-EXGWY-E801.partners.extranet.microsoft.com (10.251.56.50) with Microsoft SMTP Server (TLS) id 8.1.291.1; Tue, 19 Aug 2008 11:04:42 -0700
Received: from NA-EXMSG-C102.redmond.corp.microsoft.com ([157.54.110.49]) by tk5-exhub-c104.redmond.corp.microsoft.com ([157.54.88.97]) with mapi; Tue, 19 Aug 2008 11:04:42 -0700
From: Yu-Shun Wang <Yu-Shun.Wang@microsoft.com>
To: "Vijay K. Gurbani" <vkg@alcatel-lucent.com>, "john@jlc.net" <john@jlc.net>
Date: Tue, 19 Aug 2008 11:04:41 -0700
Thread-Topic: [p2pi] Information in an ALTO protocol
Thread-Index: AckCJBBIHk/Tjfa5QGqvcAucMEIgRQAARrpw
Message-ID: <43AEA9A9F7768B42A89F554F0EBF7ED82B5FDCEE3A@NA-EXMSG-C102.redmond.corp.microsoft.com>
References: <74CCBBDF76102846AFA7B29F3A98D3F60107C32A@PACDCEXCMB06.cable.comcast.com> <200808120901.m7C91q6H012752@bagheera.jungle.bt.co.uk> <48A48779.60507@alcatel-lucent.com> <20080814204249.GS25453@verdi> <48AB0761.7070507@alcatel-lucent.com>
In-Reply-To: <48AB0761.7070507@alcatel-lucent.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US
MIME-Version: 1.0
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-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: p2pi-bounces@ietf.org
Errors-To: p2pi-bounces@ietf.org

Short comment on this bit:

> >>   (4) Geographic location
> >
> > Often wildly inaccurate, and even more often quite unrelated to
> > network topology. Would be _very_ useful in an alternate universe
> > where routing found next-hops _physically_ closer to the
> > destination...
>
> Probably needs a bit more discussion on whether or not this is
> valuable before discarding it.

This may have policy (distribution rights, etc.) implications.
That said, not sure if we want to go there. Maybe worth retaining
it, but leave the interpretation/usage up to the apps.

yushun
_______________________________________________
p2pi mailing list
p2pi@ietf.org
https://www.ietf.org/mailman/listinfo/p2pi

v2.23.0 | Report a Bug | By Email