IETF Logo Mail Archive

[p2pi] ASN utility

Lisa Dusseault <ldusseault@commerce.net> Tue, 21 October 2008 20:28 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 13F0128C1A5; Tue, 21 Oct 2008 13:28:31 -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 747F93A693C for <p2pi@core3.amsl.com>; Mon, 29 Sep 2008 10:54:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
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 89NRjwnzRdRc for <p2pi@core3.amsl.com>; Mon, 29 Sep 2008 10:54:53 -0700 (PDT)
Received: from gateout02.mbox.net (gateout02.mbox.net [165.212.64.22]) by core3.amsl.com (Postfix) with ESMTP id A78673A6AF4 for <p2pi@ietf.org>; Mon, 29 Sep 2008 10:54:53 -0700 (PDT)
Received: from gateout02 (gwo2-lo [127.0.0.1]) by gateout02.mbox.net (Postfix) with ESMTP id 26D284BD187; Mon, 29 Sep 2008 17:54:29 +0000 (GMT)
Received: from GW1.EXCHPROD.USA.NET [165.212.116.254] by gateout02 via smtad (C8.MAIN.3.45U) with ESMTP id XID753miCR3d2592Xo2; Mon, 29 Sep 2008 17:54:29 -0000
X-USANET-Source: 165.212.116.254 IN ldusseault@commerce.net GW1.EXCHPROD.USA.NET
X-USANET-MsgId: XID753miCR3d2592Xo2
Received: from [10.1.1.130] ([157.22.41.236]) by GW1.EXCHPROD.USA.NET over TLS secured channel with Microsoft SMTPSVC(6.0.3790.3959); Mon, 29 Sep 2008 11:54:28 -0600
Message-Id: <C3B6543E-5F9C-444B-8348-DF9C7C2FA682@commerce.net>
From: Lisa Dusseault <ldusseault@commerce.net>
To: p2pi@ietf.org, Dave Ward <dward@cisco.com>
Mime-Version: 1.0 (Apple Message framework v929.2)
Date: Mon, 29 Sep 2008 10:54:27 -0700
X-Mailer: Apple Mail (2.929.2)
X-OriginalArrivalTime: 29 Sep 2008 17:54:29.0084 (UTC) FILETIME=[6B6449C0:01C9225C]
X-Mailman-Approved-At: Tue, 21 Oct 2008 13:28:30 -0700
Subject: [p2pi] ASN utility
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


When the IESG looked at the proposed ALTO charter last week, Dave had  
some comments about ASNs which I'd like to follow up on by dragging  
Dave into the conversation.

What I understand the ASN related suggestions so far to be, is to have  
the ALTO server return a list of ASN numbers to prefer or avoid.  This  
sort of information could only be provided by an ISP-operated ALTO  
server.  A peer, armed with this information, can do whatever they do  
today to figure
out which IP address falls in which ASN.  The P4P and Yale folks claim  
that returning a preference of ASNs helped their application  
tremendously.

Dave, was your concern about discovering ASN being unnecessary, or  
about ranking of ASNs being unhelpful?  Can you restate?

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

v2.8.7 | Report a Bug | By Email