IETF Logo Mail Archive

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

"Montgomery, Douglas" <dougm@nist.gov> Mon, 01 August 2011 19:01 UTC

Return-Path: <dougm@nist.gov>
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 AB4C621F8D19 for <sidr@ietfa.amsl.com>; Mon, 1 Aug 2011 12:01:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.031
X-Spam-Level:
X-Spam-Status: No, score=-2.031 tagged_above=-999 required=5 tests=[AWL=-0.054, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622]
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 L77VkscjoUJW for <sidr@ietfa.amsl.com>; Mon, 1 Aug 2011 12:01:48 -0700 (PDT)
Received: from wsget2.nist.gov (wsget2.nist.gov [129.6.13.151]) by ietfa.amsl.com (Postfix) with ESMTP id A2CE421F8D17 for <sidr@ietf.org>; Mon, 1 Aug 2011 12:01:47 -0700 (PDT)
Received: from WSXGHUB1.xchange.nist.gov (129.6.18.96) by wsget2.nist.gov (129.6.13.151) with Microsoft SMTP Server (TLS) id 14.1.323.0; Mon, 1 Aug 2011 15:01:53 -0400
Received: from MBCLUSTER.xchange.nist.gov ([fe80::d479:3188:aec0:cb66]) by WSXGHUB1.xchange.nist.gov ([129.6.18.96]) with mapi; Mon, 1 Aug 2011 15:01:51 -0400
From: "Montgomery, Douglas" <dougm@nist.gov>
To: Randy Bush <randy@psg.com>, "t.petch" <ietfc@btconnect.com>
Date: Mon, 01 Aug 2011 15:01:49 -0400
Thread-Topic: [sidr] pCNT & (AS_PATH) prepending: Is it in scope?
Thread-Index: AcxQfWVxKOd0kXBwSeC6p2H3t8ro4Q==
Message-ID: <CA5C6F74.5BE9B%dougm.tlist@gmail.com>
In-Reply-To: <m2sjplf3v5.wl%randy@psg.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/14.10.0.110310
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Cc: "sidr@ietf.org" <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 19:01:48 -0000

On 8/1/11 1:17 PM, "Randy Bush" <randy@psg.com> wrote:

>
>
>> 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's answer was better.  Given that it is easy to do, what is the down
side to enabling one to tell if someone else added/subtracted from your
prepend list?

Maybe to help that discussion, I will note by "tell" above, what the
current proposal suggests is that such adding/trimming would cause BGPSEC
path validation to FAIL.

Dougm

v2.23.0 | Report a Bug | By Email