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

"Woundy, Richard" <Richard_Woundy@cable.comcast.com> Thu, 23 October 2008 19:31 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 ACDC33A685C; Thu, 23 Oct 2008 12:31:49 -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 665AA3A685C for <p2pi@core3.amsl.com>; Thu, 23 Oct 2008 12:31:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.045
X-Spam-Level:
X-Spam-Status: No, score=0.045 tagged_above=-999 required=5 tests=[AWL=-0.092, BAYES_00=-2.599, HELO_EQ_MODEMCABLE=0.768, HOST_EQ_MODEMCABLE=1.368, J_CHICKENPOX_62=0.6]
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 rvr5pjoXsvVF for <p2pi@core3.amsl.com>; Thu, 23 Oct 2008 12:31:47 -0700 (PDT)
Received: from paoakoavas10.cable.comcast.com (paoakoavas10.cable.comcast.com [208.17.35.59]) by core3.amsl.com (Postfix) with ESMTP id 14F893A67D6 for <p2pi@ietf.org>; Thu, 23 Oct 2008 12:31:46 -0700 (PDT)
Received: from ([24.40.15.92]) by paoakoavas10.cable.comcast.com with ESMTP id KP-TDCH7.52267689; Thu, 23 Oct 2008 15:32:42 -0400
Received: from PACDCEXCMB06.cable.comcast.com ([24.40.15.22]) by PACDCEXCSMTP03.cable.comcast.com with Microsoft SMTPSVC(6.0.3790.3959); Thu, 23 Oct 2008 15:32:42 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Thu, 23 Oct 2008 15:32:41 -0400
Message-ID: <74CCBBDF76102846AFA7B29F3A98D3F60289634A@PACDCEXCMB06.cable.comcast.com>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [p2pi] WG Review: Application-Layer Traffic Optimization (alto)
Thread-Index: AckzwVP5lOp2SgLzQqWiqkmcA8Lx6wBhMlt/
From: "Woundy, Richard" <Richard_Woundy@cable.comcast.com>
To: <nweaver@ICSI.Berkeley.EDU>
X-OriginalArrivalTime: 23 Oct 2008 19:32:42.0498 (UTC) FILETIME=[1E0DE620:01C93546]
Cc: p2pi@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-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
Sender: p2pi-bounces@ietf.org
Errors-To: p2pi-bounces@ietf.org

>The question is the simpler coordinate: "who's MY resolver and who else uses it".

This is an interesting idea.

One perhaps obvious thought. I wouldn't use the IP address as the sole identifier of the DNS resolver. Lots of hosts on different networks are likely to use 192.168.x.1 as their DNS resolver, eg their home gateway. :)

-- Rich


----- Original Message -----
From: p2pi-bounces@ietf.org <p2pi-bounces@ietf.org>
To: Vijay K. Gurbani <vkg@alcatel-lucent.com>
Cc: p2pi@ietf.org <p2pi@ietf.org>rg>; Nicholas Weaver <nweaver@ICSI.Berkeley.EDU>
Sent: Tue Oct 21 17:09:07 2008
Subject: Re: [p2pi] WG Review: Application-Layer Traffic Optimization (alto)

Ono is leveraging off Akamai's DNS information:  You do a few queries  
to akamai'ed (and other CDN'ed) domains, and use the results as a  
coordinate space.

The question is the simpler coordinate: "who's MY resolver and who  
else uses it".



On Oct 21, 2008, at 2:05 PM, Vijay K. Gurbani wrote:

> 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?
>
> Doesn't Ono [1] do that?  Or am I missing something?  CDNs also
> use DNS redirects to redirect clients to nearest servers.
>
> [1] David R. Choffnes and Fabián E. Bustamante. Taming the Torrent:
>    A practical approach to reducing cross-ISP traffic in P2P
>    systems, Proc. of ACM SIGCOMM 2008, August 2008.
>
> Thanks,
>
> - vijay
> -- 
> Vijay K. Gurbani, Bell Laboratories, Alcatel-Lucent
> 1960 Lucent Lane, Rm. 9C-533, Naperville, Illinois 60566 (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 mailing list
p2pi@ietf.org
https://www.ietf.org/mailman/listinfo/p2pi
_______________________________________________
p2pi mailing list
p2pi@ietf.org
https://www.ietf.org/mailman/listinfo/p2pi