IETF Logo Mail Archive

Re: [Sidrops] Block ROA creation for AS23456?

"Roque Gagliano (rogaglia)" <rogaglia@cisco.com> Thu, 18 May 2017 12:30 UTC

Return-Path: <rogaglia@cisco.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 747C212EB7D for <sidrops@ietfa.amsl.com>; Thu, 18 May 2017 05:30:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.521
X-Spam-Level:
X-Spam-Status: No, score=-14.521 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.com
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 eVhSVH28Vik3 for <sidrops@ietfa.amsl.com>; Thu, 18 May 2017 05:30:44 -0700 (PDT)
Received: from rcdn-iport-3.cisco.com (rcdn-iport-3.cisco.com [173.37.86.74]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 500F3129AA8 for <sidrops@ietf.org>; Thu, 18 May 2017 05:25:41 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=3355; q=dns/txt; s=iport; t=1495110341; x=1496319941; h=from:to:subject:date:message-id:references:in-reply-to: mime-version; bh=voMdMMnjon7wpJ7mN/h+5JllxGxi9MMEYN9UtWH19kc=; b=czjzAmuF1YVUFhQU9KwctP+7rfF18woOCga+zwTxHO/mKxbzQ9bcmFPo OgPMK9X5OH56iiTmfxnV9Ze9PjnJQ26oiEkUqsjJKpAfmF0xGkYFcq60v uN+i1lIVvpvZvXLOEvz8Uu2YVajT6WghnrO9XbMsgIXFwhTeDjvUxE7Pe 4=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0CYAADtkR1Z/4sNJK1cGQEBAQEBAQEBAQEBBwEBAQEBg1VigQyOBZFrkD6FOIIPMIV0AoVsPxgBAgEBAQEBAQFrKIUYAQEBAQOBCQIBCAQNAwECLzIdCAIEARIIihsOsGWKfwEBAQEBAQEBAQEBAQEBAQEBAQEBARgFhl+EeYE8g0eFUgWeEwGHG4t2kXeURQEfOIEKcBWHPHYBhXYrghABAQE
X-IronPort-AV: E=Sophos;i="5.38,359,1491264000"; d="scan'208,217";a="236547319"
Received: from alln-core-6.cisco.com ([173.36.13.139]) by rcdn-iport-3.cisco.com with ESMTP/TLS/DHE-RSA-AES256-SHA; 18 May 2017 12:25:40 +0000
Received: from XCH-RTP-013.cisco.com (xch-rtp-013.cisco.com [64.101.220.153]) by alln-core-6.cisco.com (8.14.5/8.14.5) with ESMTP id v4ICPdII018413 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Thu, 18 May 2017 12:25:40 GMT
Received: from xch-rtp-011.cisco.com (64.101.220.151) by XCH-RTP-013.cisco.com (64.101.220.153) with Microsoft SMTP Server (TLS) id 15.0.1210.3; Thu, 18 May 2017 08:25:39 -0400
Received: from xch-rtp-011.cisco.com ([64.101.220.151]) by XCH-RTP-011.cisco.com ([64.101.220.151]) with mapi id 15.00.1210.000; Thu, 18 May 2017 08:25:39 -0400
From: "Roque Gagliano (rogaglia)" <rogaglia@cisco.com>
To: Alex Band <alexb@ripe.net>, "sidrops@ietf.org" <sidrops@ietf.org>
Thread-Topic: [Sidrops] Block ROA creation for AS23456?
Thread-Index: AQHSz8vQ4v467+xHeUe7nzVTaE8HHqH6BCCW
Date: Thu, 18 May 2017 12:25:39 +0000
Message-ID: <06d5677bff924ad0b23e56c685369fc1@XCH-RTP-011.cisco.com>
References: <m2o9uq4jb6.wl-randy@psg.com>, <9C01478A-B764-48C4-AB93-4DEACB229A09@ripe.net>
In-Reply-To: <9C01478A-B764-48C4-AB93-4DEACB229A09@ripe.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-ms-exchange-transport-fromentityheader: Hosted
Content-Type: multipart/alternative; boundary="_000_06d5677bff924ad0b23e56c685369fc1XCHRTP011ciscocom_"
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/sidrops/fdNoO0dbwcy_ECi8GWwMsV9i2eU>
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:30:46 -0000

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

v2.23.0 | Report a Bug | By Email