IETF Logo Mail Archive

Re: [p2pi] ASN utility

David Ward <dward@cisco.com> Tue, 21 October 2008 20:50 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 3BBEC28C192; Tue, 21 Oct 2008 13:50:18 -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 C7CAD3A679F for <p2pi@core3.amsl.com>; Tue, 21 Oct 2008 13:50:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.553
X-Spam-Level:
X-Spam-Status: No, score=-6.553 tagged_above=-999 required=5 tests=[AWL=0.046, 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 IG+mXbdPQlkz for <p2pi@core3.amsl.com>; Tue, 21 Oct 2008 13:50:15 -0700 (PDT)
Received: from rtp-iport-2.cisco.com (rtp-iport-2.cisco.com [64.102.122.149]) by core3.amsl.com (Postfix) with ESMTP id 346453A6B94 for <p2pi@ietf.org>; Tue, 21 Oct 2008 13:50:15 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.33,460,1220227200"; d="scan'208";a="25179414"
Received: from rtp-dkim-1.cisco.com ([64.102.121.158]) by rtp-iport-2.cisco.com with ESMTP; 21 Oct 2008 20:51:29 +0000
Received: from rtp-core-2.cisco.com (rtp-core-2.cisco.com [64.102.124.13]) by rtp-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id m9LKpTk3022233; Tue, 21 Oct 2008 16:51:29 -0400
Received: from xbh-rtp-201.amer.cisco.com (xbh-rtp-201.cisco.com [64.102.31.12]) by rtp-core-2.cisco.com (8.13.8/8.13.8) with ESMTP id m9LKpTnI006968; Tue, 21 Oct 2008 20:51:29 GMT
Received: from xmb-rtp-202.amer.cisco.com ([64.102.31.52]) by xbh-rtp-201.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); Tue, 21 Oct 2008 16:51:29 -0400
Received: from [127.0.0.1] ([171.68.225.134]) by xmb-rtp-202.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); Tue, 21 Oct 2008 16:50:46 -0400
In-Reply-To: <62F04BA8-07BD-4DA4-BB13-09E3498ACA87@multicasttech.com>
References: <C3B6543E-5F9C-444B-8348-DF9C7C2FA682@commerce.net> <62F04BA8-07BD-4DA4-BB13-09E3498ACA87@multicasttech.com>
Mime-Version: 1.0 (Apple Message framework v753.1)
Message-Id: <10062CD4-88B8-47EC-8809-D02486A3D05D@cisco.com>
From: David Ward <dward@cisco.com>
Date: Tue, 21 Oct 2008 15:50:40 -0500
To: Marshall Eubanks <tme@multicasttech.com>
X-Mailer: Apple Mail (2.753.1)
X-OriginalArrivalTime: 21 Oct 2008 20:50:46.0105 (UTC) FILETIME=[B0E01C90:01C933BE]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=1727; t=1224622289; x=1225486289; c=relaxed/simple; s=rtpdkim1001; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=dward@cisco.com; z=From:=20David=20Ward=20<dward@cisco.com> |Subject:=20Re=3A=20[p2pi]=20ASN=20utility |Sender:=20 |To:=20Marshall=20Eubanks=20<tme@multicasttech.com>; bh=q08cCYE058djRDBMPQjp54f/T17xAYh/7l8PffnO3Gs=; b=jIxw+1eOS3PC1lTo1KxKM5QvN4arQzRbJC7qa704eCnsX4GVcdL6wIqWQ8 jMKYSncbwuvkdffregIqiRRD0KAw3WW6s9ecqHnxY+i7usc4W8klzz155yHq aZwofebcj6;
Authentication-Results: rtp-dkim-1; header.From=dward@cisco.com; dkim=pass ( sig from cisco.com/rtpdkim1001 verified; );
Cc: p2pi@ietf.org, Lisa Dusseault <ldusseault@commerce.net>
Subject: Re: [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

Marshall -

I mentioned that this is one deployment model and is as it works  
today but, the charter is unclear if they want to support any other  
model. I do think it is considerably harder to deduce a current  
AS_path from simple prefix -> ASN information.

-DWard

On Oct 21, 2008, at 3:38 PM, Marshall Eubanks wrote:

>
> On Sep 29, 2008, at 1:54 PM, Lisa Dusseault wrote:
>
>>
>>
>> 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.
>
> Are you sure about that ?
>
> A peer can (for example) query route views, or I (or a host of  
> others) can send it BGP / address block tables. It would not be  
> hard to collate address information with ASN and ASN paths and draw  
> conclusions. I don't see why an ISP is necessarily involved.
>
> Regards
> Marshall
>
>
>
>> 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
>

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

v2.23.0 | Report a Bug | By Email