IETF Logo Mail Archive

Re: [Sidrops] Block ROA creation for AS23456?

"Roque Gagliano (rogaglia)" <rogaglia@cisco.com> Thu, 18 May 2017 12:56 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 8D56B128DE5 for <sidrops@ietfa.amsl.com>; Thu, 18 May 2017 05:56:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.522
X-Spam-Level:
X-Spam-Status: No, score=-14.522 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, 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 lFU-Cs3wQ_hV for <sidrops@ietfa.amsl.com>; Thu, 18 May 2017 05:56:12 -0700 (PDT)
Received: from rcdn-iport-5.cisco.com (rcdn-iport-5.cisco.com [173.37.86.76]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 739E5129467 for <sidrops@ietf.org>; Thu, 18 May 2017 05:51:11 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=2402; q=dns/txt; s=iport; t=1495111871; x=1496321471; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-id:content-transfer-encoding: mime-version; bh=vx/q62GGbO2CVZ37YzKFeADffpeA5EjgbGMpCO7foKE=; b=cTNY68dYdgUY7LSSrSPGg0vl+pMDNgP5gwQgm99AP1uzMpX0vpqFjJ85 Dny2b1n/9goNDLY+eCi2nqJc9VyR5RdM3U2MLyf+vehviv1azoX7bXfq2 Nv0hz+qkzv44IEd+DQHvXGPNrLje5I94HO7oxLpKH8Lc+d3IYpAyBf2tI A=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0BDAQCJlx1Z/4cNJK1cGQEBAQEBAQEBAQEBBwEBAQEBg1VigQwHg2aKGJFKIZV2gg8whXQCGoVTPxgBAgEBAQEBAQFrKIUYAQEBAQIBIxFFEAIBCBEDAQIBAgImAgICMBUICAIEDgUbigAIDq5XgiaKfwEBAQEBAQEBAQEBAQEBAQEBAQEBARgFgQuFVIIJC4JlgTyDJxeCey+CMQWeEwGHG4t/kW6URQEfOD9LcBVYAYRwgXN2AYV2K4EDgQ0BAQE
X-IronPort-AV: E=Sophos;i="5.38,359,1491264000"; d="scan'208";a="28978973"
Received: from alln-core-2.cisco.com ([173.36.13.135]) by rcdn-iport-5.cisco.com with ESMTP/TLS/DHE-RSA-AES256-SHA; 18 May 2017 12:51:10 +0000
Received: from XCH-RTP-013.cisco.com (xch-rtp-013.cisco.com [64.101.220.153]) by alln-core-2.cisco.com (8.14.5/8.14.5) with ESMTP id v4ICpA6T028931 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Thu, 18 May 2017 12:51:10 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:51:09 -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:51:09 -0400
From: "Roque Gagliano (rogaglia)" <rogaglia@cisco.com>
To: Alex Band <alexb@ripe.net>
CC: "sidrops@ietf.org" <sidrops@ietf.org>
Thread-Topic: [Sidrops] Block ROA creation for AS23456?
Thread-Index: AQHSz8vQ4v467+xHeUe7nzVTaE8HHqH6BCCWgABEugCAACb5AA==
Date: Thu, 18 May 2017 12:51:09 +0000
Message-ID: <C083CBCB-3FB5-4934-9BA0-22F02D15016D@cisco.com>
References: <m2o9uq4jb6.wl-randy@psg.com> <9C01478A-B764-48C4-AB93-4DEACB229A09@ripe.net> <06d5677bff924ad0b23e56c685369fc1@XCH-RTP-011.cisco.com> <E0567D84-4C4D-4D15-BBE4-2124155BC791@ripe.net>
In-Reply-To: <E0567D84-4C4D-4D15-BBE4-2124155BC791@ripe.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/f.20.0.170309
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.61.109.198]
Content-Type: text/plain; charset="utf-8"
Content-ID: <DEA1448161D1A043B39AC0EFBBEFE710@emea.cisco.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/sidrops/pv18OFkMuKerZdG1e9s0bI5yYC8>
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:56:14 -0000

Hi,

I would be more inclined to let the RP to solve it. Maybe with a switch to “ignore-roas-with-reserved-asn-other-than-0” and let that to be a SP decision to turn it ON/OFF with maybe the default to be to ignore them.

Regards,
Roque
    


— 
Roque Gagliano
Tail-f Solutions Architect Southern Europe
+41 76 449 8867


On 18/05/17 14:31, "Alex Band" <alexb@ripe.net> wrote:

    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

v2.23.0 | Report a Bug | By Email