Re: [Sidrops] as23456 in ROAs

Randy Bush <randy@psg.com> Mon, 01 April 2019 03:26 UTC

Return-Path: <randy@psg.com>
X-Original-To: sidrops@ietfa.amsl.com
Delivered-To: sidrops@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AA1D512004A for <sidrops@ietfa.amsl.com>; Sun, 31 Mar 2019 20:26:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.901
X-Spam-Level:
X-Spam-Status: No, score=-6.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id SR4b76Z0emw3 for <sidrops@ietfa.amsl.com>; Sun, 31 Mar 2019 20:26:23 -0700 (PDT)
Received: from ran.psg.com (ran.psg.com [IPv6:2001:418:8006::18]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DC61F12003F for <sidrops@ietf.org>; Sun, 31 Mar 2019 20:26:22 -0700 (PDT)
Received: from localhost ([127.0.0.1] helo=ryuu.rg.net) by ran.psg.com with esmtp (Exim 4.90_1) (envelope-from <randy@psg.com>) id 1hAnaV-0000rp-ST; Mon, 01 Apr 2019 03:26:20 +0000
Date: Sun, 31 Mar 2019 20:26:19 -0700
Message-ID: <m2sgv2jtic.wl-randy@psg.com>
From: Randy Bush <randy@psg.com>
To: Christopher Morrow <christopher.morrow@gmail.com>
Cc: Jay Borkenhagen <jayb@braeburn.org>, SIDR Operations WG <sidrops@ietf.org>, Ruediger Volk <rv@nic.dtag.de>
In-Reply-To: <CAL9jLaY7uMn+n+dcD0NWAvNfSti5m2OEBaiqg=4G20d-7fg8Eg@mail.gmail.com>
References: <23713.4600.388005.282115@oz.mt.att.com> <CAL9jLaY7uMn+n+dcD0NWAvNfSti5m2OEBaiqg=4G20d-7fg8Eg@mail.gmail.com>
User-Agent: Wanderlust/2.15.9 (Almost Unreal) Emacs/25.3 Mule/6.0 (HANACHIRUSATO)
MIME-Version: 1.0 (generated by SEMI-EPG 1.14.7 - "Harue")
Content-Type: text/plain; charset=US-ASCII
Archived-At: <https://mailarchive.ietf.org/arch/msg/sidrops/jTrxzdWmupF6Yllj4jFgX09nBC0>
Subject: Re: [Sidrops] as23456 in ROAs
X-BeenThere: sidrops@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: A list for the SIDR Operations WG <sidrops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/sidrops>, <mailto:sidrops-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/sidrops/>
List-Post: <mailto:sidrops@ietf.org>
List-Help: <mailto:sidrops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sidrops>, <mailto:sidrops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 01 Apr 2019 03:26:25 -0000

> > Not saying I like it or would recommend taking steps to work around
> > networks that still do not grok 4B-ASNs in 2019, but perhaps an
> > as23456 ROA is not totally without motivation.
> > ]
> 
> So, I thought one of the requirements for doing BGPSEC (maybe not OV
> though?) was: "must have 4-byte capability"
> clearly signing a ROA for: "shared asn" is a poor plan :( but really
> you shouldn't ever see 23456 in a secure path... (again, sure that's
> BGPSEC not OV)

do routers which do not support 4-byte asns support rpki policy to say
"mark announcements where the origin is as23456 as notfound?"

randy