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

"Woundy, Richard" <Richard_Woundy@cable.comcast.com> Thu, 23 October 2008 20:24 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 3EF053A6A2C; Thu, 23 Oct 2008 13:24:21 -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 667FB3A6A2C for <p2pi@core3.amsl.com>; Thu, 23 Oct 2008 13:24:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.236
X-Spam-Level:
X-Spam-Status: No, score=-0.236 tagged_above=-999 required=5 tests=[AWL=0.227, BAYES_00=-2.599, HELO_EQ_MODEMCABLE=0.768, HOST_EQ_MODEMCABLE=1.368]
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 aFKyxI15AhmT for <p2pi@core3.amsl.com>; Thu, 23 Oct 2008 13:24:19 -0700 (PDT)
Received: from paoakoavas10.cable.comcast.com (paoakoavas10.cable.comcast.com [208.17.35.59]) by core3.amsl.com (Postfix) with ESMTP id 80BD93A6AA7 for <p2pi@ietf.org>; Thu, 23 Oct 2008 13:24:16 -0700 (PDT)
Received: from ([10.52.116.30]) by paoakoavas10.cable.comcast.com with ESMTP id KP-TDCH7.52271889; Thu, 23 Oct 2008 16:25:22 -0400
Received: from PACDCEXCMB06.cable.comcast.com ([24.40.15.22]) by PAOAKEXCSMTP01.cable.comcast.com with Microsoft SMTPSVC(6.0.3790.3959); Thu, 23 Oct 2008 16:25:22 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Thu, 23 Oct 2008 16:25:21 -0400
Message-ID: <74CCBBDF76102846AFA7B29F3A98D3F60289634D@PACDCEXCMB06.cable.comcast.com>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [p2pi] WG Review: Application-Layer Traffic Optimization (alto)
Thread-Index: Ack1R6El0f3m8U4ySr+s0TwVv1oqFwABdfRO
From: "Woundy, Richard" <Richard_Woundy@cable.comcast.com>
To: <nweaver@ICSI.Berkeley.EDU>
X-OriginalArrivalTime: 23 Oct 2008 20:25:22.0314 (UTC) FILETIME=[79738EA0:01C9354D]
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="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: p2pi-bounces@ietf.org
Errors-To: p2pi-bounces@ietf.org

>Well, you use the last-hop resolver

That makes more sense. :)

In our network, we have a number of clusters of caching DNS servers. Two customer computers in the same geography may happen to use different caching servers in the same cluster. Two computers in different geographies may use different caching clusters.

-- Rich


----- Original Message -----
From: Nicholas Weaver <nweaver@ICSI.Berkeley.EDU>
To: Woundy, Richard
Cc: Nicholas Weaver <nweaver@ICSI.Berkeley.EDU>DU>; p2pi@ietf.org <p2pi@ietf.org>
Sent: Thu Oct 23 15:43:04 2008
Subject: Re: [p2pi] WG Review: Application-Layer Traffic Optimization (alto)


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