Re: [Sidrops] Block ROA creation for AS23456?

Alex Band <alexb@ripe.net> Thu, 18 May 2017 12:37 UTC

Return-Path: <alexb@ripe.net>
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 E708C129B5B for <sidrops@ietfa.amsl.com>; Thu, 18 May 2017 05:37:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.9
X-Spam-Level:
X-Spam-Status: No, score=-6.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.001, URIBL_BLOCKED=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 ek9PmGjhQNHR for <sidrops@ietfa.amsl.com>; Thu, 18 May 2017 05:37:03 -0700 (PDT)
Received: from molamola.ripe.net (molamola.ripe.net [IPv6:2001:67c:2e8:11::c100:1371]) (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 42689129549 for <sidrops@ietf.org>; Thu, 18 May 2017 05:31:42 -0700 (PDT)
Received: from nene.ripe.net ([193.0.23.10]) by molamola.ripe.net with esmtps (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256) (Exim 4.88) (envelope-from <alexb@ripe.net>) id 1dBKag-0000XF-VG; Thu, 18 May 2017 14:31:40 +0200
Received: from sslvpn.ipv6.ripe.net ([2001:67c:2e8:9::c100:14e6] helo=[IPv6:2001:67c:2e8:5009::21]) by nene.ripe.net with esmtps (TLSv1.2:DHE-RSA-AES256-GCM-SHA384:256) (Exim 4.84_2) (envelope-from <alexb@ripe.net>) id 1dBKag-0000v0-Pw; Thu, 18 May 2017 14:31:38 +0200
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
From: Alex Band <alexb@ripe.net>
In-Reply-To: <06d5677bff924ad0b23e56c685369fc1@XCH-RTP-011.cisco.com>
Date: Thu, 18 May 2017 14:31:38 +0200
Cc: "sidrops@ietf.org" <sidrops@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <E0567D84-4C4D-4D15-BBE4-2124155BC791@ripe.net>
References: <m2o9uq4jb6.wl-randy@psg.com> <9C01478A-B764-48C4-AB93-4DEACB229A09@ripe.net> <06d5677bff924ad0b23e56c685369fc1@XCH-RTP-011.cisco.com>
To: "Roque Gagliano (rogaglia)" <rogaglia@cisco.com>
X-Mailer: Apple Mail (2.3273)
X-ACL-Warn: Delaying message
X-RIPE-Spam-Level: -------
X-RIPE-Spam-Report: Spam Total Points: -7.5 points pts rule name description ---- ---------------------- ------------------------------------ -7.5 ALL_TRUSTED Passed through trusted hosts only via SMTP
X-RIPE-Signature: ddd0bbf11d1e21354000f5f053f5ae69998123fa77ad94843288220f51b9d041
Archived-At: <https://mailarchive.ietf.org/arch/msg/sidrops/GrmR_P3egCUTbXOmzEb4spPjlZc>
Subject: Re: [Sidrops] Block ROA creation for AS23456?
X-BeenThere: sidrops@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: <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: Thu, 18 May 2017 12:37:10 -0000

Hi Roque,

We’re only talking about actively preventing creation of the ROA under the CA.

Cheers,

Alex


> On 18 May 2017, at 14:25, Roque Gagliano (rogaglia) <rogaglia@cisco.com> wrote:
> 
> Hi Alex,
> 
> Are we talking about the CA should prevent creation and/or the RP should ignore it when validating?
> 
> Roque
> 
> ----- Reply message -----
> From: "Alex Band" <alexb@ripe.net>
> To: "sidrops@ietf.org" <sidrops@ietf.org>
> Subject: [Sidrops] Block ROA creation for AS23456?
> Date: Thu, May 18, 2017 13:42
> 
> Hello SidrOps folks,
> 
> One of our members argues that we should be preventing that ROAs are created which authorise AS23456, as referred to in RFC6793 [1]. It would allegedly open up possibilities for abuse. You could make the same argument for several other special registry AS Numbers [2]. 
> 
> I’m curious to hear if you think this argument holds any truth, and if we should be thinking about such measures.
> 
> Cheers,
> 
> Alex Band
> Product Manager
> RIPE NCC
> 
> [1] https://tools.ietf.org/html/rfc6793
> [2] https://www.iana.org/assignments/iana-as-numbers-special-registry/iana-as-numbers-special-registry.xhtml