IETF Logo Mail Archive

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

Nicholas Weaver <nweaver@ICSI.Berkeley.EDU> Tue, 21 October 2008 20:42 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 C7DAE3A6B96; Tue, 21 Oct 2008 13:42:34 -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 24AA03A6B94; Tue, 21 Oct 2008 13:42:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.637
X-Spam-Level:
X-Spam-Status: No, score=-5.637 tagged_above=-999 required=5 tests=[AWL=0.962, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
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 OHlELgnjjYIm; Tue, 21 Oct 2008 13:42:33 -0700 (PDT)
Received: from fruitcake.ICSI.Berkeley.EDU (fruitcake.ICSI.Berkeley.EDU [192.150.186.11]) by core3.amsl.com (Postfix) with ESMTP id 623543A6804; Tue, 21 Oct 2008 13:42:33 -0700 (PDT)
Received: from [IPv6:::1] (fruitcake [192.150.186.11]) by fruitcake.ICSI.Berkeley.EDU (8.12.11.20060614/8.12.11) with ESMTP id m9LKhUDf027272; Tue, 21 Oct 2008 13:43:31 -0700 (PDT)
Message-Id: <EE0DFEE3-0646-45F7-B194-199B83B2E9D4@icsi.berkeley.edu>
From: Nicholas Weaver <nweaver@ICSI.Berkeley.EDU>
To: Karl Auerbach <karl@cavebear.com>
In-Reply-To: <48F4E20B.8000609@cavebear.com>
Mime-Version: 1.0 (Apple Message framework v929.2)
Date: Tue, 21 Oct 2008 13:43:30 -0700
References: <20081006203532.B1D673A68AF@core3.amsl.com> <BE82361A0E26874DBC2ED1BA244866B9276373BA@NALASEXMB08.na.qualcomm.com> <48EEB19C.4000303@bbn.com> <48EEE549.1080208@qualcomm.com> <48EF477E.4080708@telecomitalia.it> <48EF706C.9050508@qualcomm.com> <48EFA0BE.1040809@alcatel-lucent.com> <ca722a9e0810101221yb84ac3ar8ff0f267718c88c9@mail.gmail.com> <48EFD2BC.8050706@qualcomm.com> <48F000FD.5000302@telecomitalia.it> <3C654581-ABA5-45B9-A36D-E0BD9B52366B@nokia.com> <48F4E20B.8000609@cavebear.com>
X-Mailer: Apple Mail (2.929.2)
Cc: "p2pi@ietf.org" <p2pi@ietf.org>, Nicholas Weaver <nweaver@ICSI.Berkeley.EDU>, IESG IESG <iesg@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>
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-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"; DelSp="yes"
Sender: p2pi-bounces@ietf.org
Errors-To: p2pi-bounces@ietf.org

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?

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

v2.23.0 | Report a Bug | By Email