IETF Logo Mail Archive

[Sidrops] Block ROA creation for AS23456?

Alex Band <alexb@ripe.net> Thu, 18 May 2017 11:42 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 8B6CB1293DB for <sidrops@ietfa.amsl.com>; Thu, 18 May 2017 04:42:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.199
X-Spam-Level:
X-Spam-Status: No, score=-4.199 tagged_above=-999 required=5 tests=[BAYES_50=0.8, HTML_MESSAGE=0.001, 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 wBGMNwOrHIqw for <sidrops@ietfa.amsl.com>; Thu, 18 May 2017 04:42:15 -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 80D8B12EBC1 for <sidrops@ietf.org>; Thu, 18 May 2017 04:36:48 -0700 (PDT)
Received: from titi.ripe.net ([193.0.23.11]) by molamola.ripe.net with esmtps (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256) (Exim 4.88) (envelope-from <alexb@ripe.net>) id 1dBJja-0008Nv-6T for sidrops@ietf.org; Thu, 18 May 2017 13:36:47 +0200
Received: from sslvpn.ipv6.ripe.net ([2001:67c:2e8:9::c100:14e6] helo=[IPv6:2001:67c:2e8:5009::21]) by titi.ripe.net with esmtps (TLSv1.2:DHE-RSA-AES256-GCM-SHA384:256) (Exim 4.84_2) (envelope-from <alexb@ripe.net>) id 1dBJja-0004r8-4F for sidrops@ietf.org; Thu, 18 May 2017 13:36:46 +0200
From: Alex Band <alexb@ripe.net>
Content-Type: multipart/alternative; boundary="Apple-Mail=_3420DDD7-7195-4797-816C-760B8F5BC5D7"
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
Message-Id: <9C01478A-B764-48C4-AB93-4DEACB229A09@ripe.net>
References: <m2o9uq4jb6.wl-randy@psg.com>
To: sidrops@ietf.org
Date: Thu, 18 May 2017 13:36:45 +0200
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 0.0 HTML_MESSAGE BODY: HTML included in message
X-RIPE-Signature: ddd0bbf11d1e21354000f5f053f5ae69592dfc399fb508b25de5f6be3f50fbe8
Archived-At: <https://mailarchive.ietf.org/arch/msg/sidrops/twr9INgLca1iqmILexLkKVYlZJc>
Subject: [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 11:42:17 -0000

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 <https://tools.ietf.org/html/rfc6793>
[2] https://www.iana.org/assignments/iana-as-numbers-special-registry/iana-as-numbers-special-registry.xhtml <https://www.iana.org/assignments/iana-as-numbers-special-registry/iana-as-numbers-special-registry.xhtml>

v2.23.0 | Report a Bug | By Email