Re: [p2pi] WG Review: Application-Layer Traffic Optimization (alto)

Dean Anderson <dean@av8.com> Wed, 22 October 2008 18:38 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 DAF063A6821; Wed, 22 Oct 2008 11:38:48 -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 A7F163A69B7; Wed, 22 Oct 2008 09:53:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.777
X-Spam-Level:
X-Spam-Status: No, score=-1.777 tagged_above=-999 required=5 tests=[AWL=0.822, 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 2sJiAysm9KB3; Wed, 22 Oct 2008 09:53:19 -0700 (PDT)
Received: from cirrus.av8.net (cirrus.av8.net [130.105.36.66]) by core3.amsl.com (Postfix) with ESMTP id 97D513A6778; Wed, 22 Oct 2008 09:53:19 -0700 (PDT)
Received: from citation2.av8.net (citation2.av8.net [130.105.12.10]) (authenticated bits=0) by cirrus.av8.net (8.12.11/8.12.11) with ESMTP id m9MGs2Og019474 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Wed, 22 Oct 2008 12:54:02 -0400
Date: Wed, 22 Oct 2008 12:54:01 -0400 (EDT)
From: Dean Anderson <dean@av8.com>
X-X-Sender: dean@citation2.av8.net
To: Nicholas Weaver <nweaver@ICSI.Berkeley.EDU>
In-Reply-To: <EE0DFEE3-0646-45F7-B194-199B83B2E9D4@icsi.berkeley.edu>
Message-ID: <Pine.LNX.4.44.0810221225270.11807-100000@citation2.av8.net>
MIME-Version: 1.0
X-Mailman-Approved-At: Wed, 22 Oct 2008 11:38:48 -0700
Cc: "ietf@ietf.org" <ietf@ietf.org>, "p2pi@ietf.org" <p2pi@ietf.org>, IESG IESG <iesg@ietf.org>, Karl Auerbach <karl@cavebear.com>
Subject: Re: [p2pi] WG Review: Application-Layer Traffic Optimization (alto)
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


On Tue, 21 Oct 2008, Nicholas Weaver wrote:

> Hey, stupid thought...
> 
> Could you do proximity based on "who's your DNS resolver"?  Do a few  
> name lookups: one to register YOU as using YOUR DNS resolver to the  
> remote coordinator, and one to get "who are other peers using the same  
> resolver"?
> 
> An ugly, UGLY hack, but it might be interesting to think about.
> 
> Has anyone done this already?

This is a very good idea.  You can get 'who are your peers?' through BGP
analysis. (look at quagga/zebra).  Quagga can get routes from the 
routers, and then do whatever, feed that to a database, etc.

So one could start with BGP data, and then perhaps test and cache actual
hops to the target, rather like DNS, but not actually DNS.

		--Dean





-- 
Av8 Internet   Prepared to pay a premium for better service?
www.av8.net         faster, more reliable, better service
617 344 9000   


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