Re: [sidr] pCNT & (AS_PATH) prepending: Is it in scope?

Randy Bush <randy@psg.com> Mon, 01 August 2011 17:17 UTC

Return-Path: <randy@psg.com>
X-Original-To: sidr@ietfa.amsl.com
Delivered-To: sidr@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CC74411E80AB for <sidr@ietfa.amsl.com>; Mon, 1 Aug 2011 10:17:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.514
X-Spam-Level:
X-Spam-Status: No, score=-2.514 tagged_above=-999 required=5 tests=[AWL=0.085, BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Kvb0NoW67nnT for <sidr@ietfa.amsl.com>; Mon, 1 Aug 2011 10:17:55 -0700 (PDT)
Received: from ran.psg.com (ran.psg.com [IPv6:2001:418:1::36]) by ietfa.amsl.com (Postfix) with ESMTP id 04D2821F8A67 for <sidr@ietf.org>; Mon, 1 Aug 2011 10:17:36 -0700 (PDT)
Received: from localhost ([127.0.0.1] helo=rair.psg.com.psg.com) by ran.psg.com with esmtp (Exim 4.76 (FreeBSD)) (envelope-from <randy@psg.com>) id 1Qnw7T-0003z2-Fa; Mon, 01 Aug 2011 17:17:35 +0000
Date: Tue, 02 Aug 2011 02:17:34 +0900
Message-ID: <m2sjplf3v5.wl%randy@psg.com>
From: Randy Bush <randy@psg.com>
To: "t.petch" <ietfc@btconnect.com>
In-Reply-To: <04fe01cc5061$90fdbe60$4001a8c0@gateway.2wire.net>
References: <19BD9B69-B1EE-495E-8795-38DDE3BF6D4A@castlepoint.net> <D7A0423E5E193F40BE6E94126930C493087C7907B3@MBCLUSTER.xchange.nist.gov> <2C3246E7-A4AD-4335-BCDA-73D98DDB0274@castlepoint.net> <04fe01cc5061$90fdbe60$4001a8c0@gateway.2wire.net>
User-Agent: Wanderlust/2.15.9 (Almost Unreal) Emacs/22.3 Mule/5.0 (SAKAKI)
MIME-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka")
Content-Type: text/plain; charset="US-ASCII"
Cc: sidr@ietf.org
Subject: Re: [sidr] pCNT & (AS_PATH) prepending: Is it in scope?
X-BeenThere: sidr@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Secure Interdomain Routing <sidr.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/sidr>, <mailto:sidr-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/sidr>
List-Post: <mailto:sidr@ietf.org>
List-Help: <mailto:sidr-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sidr>, <mailto:sidr-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 01 Aug 2011 17:17:55 -0000

not your fault, but very hard to find your text amid the top posting,
lack of line wraps, quoting disasters, ...

> I do not think that it was simplification that led to the deprecation
> of AS-SET, rather the difficulty or impossibility of securing it to
> the same extent as a single AS; which led to the discovery that AS_SET
> were rare and that their loss would not affect almost all of the
> Internet.

we knew as-sets were rare.  but before moving to deprecate we decided to
actually measure how rare.

note that as-sets affect both origin validation and path validation.

> Question is; how common is prepending?  I thought that it was
> widespread and 'normal' but there would have to be hard data first,
> before deprecation could be contemplated.

we could measure.  but given that we can see that it is quite common,
and we have reasonable ways to deal with it, why should we spend the
time?  what might we learn?

randy