IETF Logo Mail Archive

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

Nicholas Weaver <nweaver@ICSI.Berkeley.EDU> Thu, 23 October 2008 19:43 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 4D8EA3A6C41; Thu, 23 Oct 2008 12:43:00 -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 83FB83A6AAD for <p2pi@core3.amsl.com>; Thu, 23 Oct 2008 12:42:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.737
X-Spam-Level:
X-Spam-Status: No, score=-5.737 tagged_above=-999 required=5 tests=[AWL=0.862, 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 srz0TkR5K8nj for <p2pi@core3.amsl.com>; Thu, 23 Oct 2008 12:42:58 -0700 (PDT)
Received: from fruitcake.ICSI.Berkeley.EDU (fruitcake.ICSI.Berkeley.EDU [192.150.186.11]) by core3.amsl.com (Postfix) with ESMTP id D26223A6CAE for <p2pi@ietf.org>; Thu, 23 Oct 2008 12:41:56 -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 m9NJh54n007294; Thu, 23 Oct 2008 12:43:05 -0700 (PDT)
Message-Id: <44E22385-AB0D-4CEB-B6F2-A86FE551FEE6@ICSI.Berkeley.EDU>
From: Nicholas Weaver <nweaver@ICSI.Berkeley.EDU>
To: "Woundy, Richard" <Richard_Woundy@cable.comcast.com>
In-Reply-To: <74CCBBDF76102846AFA7B29F3A98D3F60289634A@PACDCEXCMB06.cable.comcast.com>
Mime-Version: 1.0 (Apple Message framework v929.2)
Date: Thu, 23 Oct 2008 12:43:04 -0700
References: <74CCBBDF76102846AFA7B29F3A98D3F60289634A@PACDCEXCMB06.cable.comcast.com>
X-Mailer: Apple Mail (2.929.2)
Cc: p2pi@ietf.org, Nicholas Weaver <nweaver@ICSI.Berkeley.EDU>
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

On Oct 23, 2008, at 12:32 PM, Woundy, Richard wrote:

>> 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. :)

Well, you use the last-hop resolver, by looking at the address from  
the authoritative server side, not from the client side.

eg, query
server.nettest.icir.org

The answer is the recursive resolver which contacted our DNS server.   
(well, when our experimental server is running that is)


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

v2.23.0 | Report a Bug | By Email