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

"Das, Saumitra" <saumitra@qualcomm.com> Tue, 21 October 2008 21:59 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 B9F1D3A6BC1; Tue, 21 Oct 2008 14:59:46 -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 9C2BD3A6BB8 for <p2pi@core3.amsl.com>; Tue, 21 Oct 2008 14:59:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -104.071
X-Spam-Level:
X-Spam-Status: No, score=-104.071 tagged_above=-999 required=5 tests=[AWL=1.327, BAYES_00=-2.599, HTML_MESSAGE=0.001, J_CHICKENPOX_41=0.6, J_CHICKENPOX_62=0.6, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
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 8xe1ZXOHDXSk for <p2pi@core3.amsl.com>; Tue, 21 Oct 2008 14:59:41 -0700 (PDT)
Received: from wolverine01.qualcomm.com (wolverine01.qualcomm.com [199.106.114.254]) by core3.amsl.com (Postfix) with ESMTP id 0361F3A6BBD for <p2pi@ietf.org>; Tue, 21 Oct 2008 14:59:40 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=qualcomm.com; i=saumitra@qualcomm.com; q=dns/txt; s=qcdkim; t=1224626456; x=1256162456; h=from:to:date:subject:thread-topic:thread-index: message-id:accept-language:content-language: x-ms-has-attach:x-ms-tnef-correlator:acceptlanguage: content-type:mime-version:x-ironport-av; z=From:=20"Das,=20Saumitra"=20<saumitra@qualcomm.com>|To: =20"p2pi@ietf.org"=20<p2pi@ietf.org>|Date:=20Tue,=2021=20 Oct=202008=2015:00:45=20-0700|Subject:=20Re:=20WG=20Revie w:=20Application-Layer=20Traffic=20Optimization=20(alto) |Thread-Topic:=20Re:=20WG=20Review:=20Application-Layer =20Traffic=20Optimization=20(alto)|Thread-Index:=20AckzyH ggmQfRLWs9RyKCT8n1zde6+Q=3D=3D|Message-ID:=20<4A27D05E36D E7E47B96BCF7DD8F3FD7101D352FD38@NASANEXMB04.na.qualcomm.c om>|Accept-Language:=20en-US|Content-Language:=20en-US |X-MS-Has-Attach:|X-MS-TNEF-Correlator:|acceptlanguage: =20en-US|Content-Type:=20multipart/alternative=3B=0D=0A =09boundary=3D"_000_4A27D05E36DE7E47B96BCF7DD8F3FD7101D35 2FD38NASANEXMB04na_"|MIME-Version:=201.0|X-IronPort-AV: =20E=3DMcAfee=3Bi=3D"5300,2777,5411"=3B=20a=3D"11220442"; bh=di0NVrA3r3tlrDG6h8fULsn7merS0sTrzpQOkfMW97k=; b=f3WA30l7TU7ygpa2G/OXIlcYYLqb946suiCGyiXg6crK7ZFKVbYwqPpH ziQpgizRUrgbPyS2Hgfqj2CeCkfavEqS+WDXlN9JffZduPyp8MplcXPId fpelJCdYVtXlrbzRN3DrAQjYraWLzekMV2Bgbay0KniFsSayl8ACOi8f6 M=;
X-IronPort-AV: E=McAfee;i="5300,2777,5411"; a="11220442"
Received: from pdmz-ns-mip.qualcomm.com (HELO ithilien.qualcomm.com) ([199.106.114.10]) by wolverine01.qualcomm.com with ESMTP/TLS/DHE-RSA-AES256-SHA; 21 Oct 2008 15:00:56 -0700
Received: from totoro.qualcomm.com (totoro.qualcomm.com [129.46.61.158]) by ithilien.qualcomm.com (8.14.2/8.14.2/1.0) with ESMTP id m9LM0tnj022734 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL) for <p2pi@ietf.org>; Tue, 21 Oct 2008 15:00:56 -0700
Received: from nasanexhc02.na.qualcomm.com (nasanexhc02.na.qualcomm.com [172.30.33.23]) by totoro.qualcomm.com (8.14.2/8.14.2/1.0) with ESMTP id m9LM0t1v017078 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT) for <p2pi@ietf.org>; Tue, 21 Oct 2008 15:00:55 -0700 (PDT)
Received: from NASANEXMB04.na.qualcomm.com ([129.46.52.85]) by nasanexhc02.na.qualcomm.com ([172.30.33.23]) with mapi; Tue, 21 Oct 2008 15:00:54 -0700
From: "Das, Saumitra" <saumitra@qualcomm.com>
To: "p2pi@ietf.org" <p2pi@ietf.org>
Date: Tue, 21 Oct 2008 15:00:45 -0700
Thread-Topic: Re: WG Review: Application-Layer Traffic Optimization (alto)
Thread-Index: AckzyHggmQfRLWs9RyKCT8n1zde6+Q==
Message-ID: <4A27D05E36DE7E47B96BCF7DD8F3FD7101D352FD38@NASANEXMB04.na.qualcomm.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US
MIME-Version: 1.0
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: multipart/mixed; boundary="===============0369441580=="
Sender: p2pi-bounces@ietf.org
Errors-To: p2pi-bounces@ietf.org

>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


This may work for general ISP users who likely share the same DNS resolvers. However others like say universities would have their own DNS resovler set up although they may also buy access from an ISP as well. So this information will nto be enough to figure out that peers in other universities that can be reached via the Abilene network should be preferred by p2p applications since they will likely have different DNS resolvers.



However this is different from the Taming the torrent approach which uses Akami to infer "being in the same ISPness". They may in some cases have more information about closeness based on cooperation with ISPs.



Thanks,

Saumitra



www.saumitra.info<http://www.saumitra.info>

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