IETF Logo Mail Archive

Re: [Sidrops] ARIN RPKI Repository issue - Wednesday 24 October 2018

John Curran <jcurran@arin.net> Fri, 26 October 2018 17:17 UTC

Return-Path: <jcurran@arin.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 05FBD12870E for <sidrops@ietfa.amsl.com>; Fri, 26 Oct 2018 10:17:19 -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 iGRN2pnQ4lrI for <sidrops@ietfa.amsl.com>; Fri, 26 Oct 2018 10:17:18 -0700 (PDT)
Received: from smtp1.arin.net (smtp1.arin.net [192.136.136.51]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DF73B127133 for <sidrops@ietf.org>; Fri, 26 Oct 2018 10:17:17 -0700 (PDT)
Received: by smtp1.arin.net (Postfix, from userid 323) id E6AF3103620A; Fri, 26 Oct 2018 13:17:14 -0400 (EDT)
Received: from ASHEDGE02.corp.arin.net (ashedge02.corp.arin.net [199.43.0.123]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by smtp1.arin.net (Postfix) with ESMTPS id EA0E910365BE; Fri, 26 Oct 2018 13:17:12 -0400 (EDT)
Received: from CAS02ASH.corp.arin.net (10.4.30.63) by ASHEDGE02.corp.arin.net (199.43.0.123) with Microsoft SMTP Server (TLS) id 15.0.847.32; Fri, 26 Oct 2018 13:16:44 -0400
Received: from CAS01ASH.corp.arin.net (10.4.30.62) by CAS02ASH.corp.arin.net (10.4.30.63) with Microsoft SMTP Server (TLS) id 15.0.1210.3; Fri, 26 Oct 2018 13:16:54 -0400
Received: from CAS01ASH.corp.arin.net ([fe80::4803:bd5b:dc93:20f6]) by CAS01ASH.corp.arin.net ([fe80::4803:bd5b:dc93:20f6%18]) with mapi id 15.00.1210.000; Fri, 26 Oct 2018 13:16:54 -0400
From: John Curran <jcurran@arin.net>
To: Randy Bush <randy@psg.com>
CC: "sidrops@ietf.org" <sidrops@ietf.org>
Thread-Topic: [Sidrops] ARIN RPKI Repository issue - Wednesday 24 October 2018
Thread-Index: AQHUbDVwQ+w/GZIS1kqGfzrvfX1d/aUwaJGAgAFsBgCAACF7AIAAE/KA
Date: Fri, 26 Oct 2018 17:16:54 +0000
Message-ID: <47F7E3F4-6EE9-4DDB-B2A0-8631DA54D111@arin.net>
References: <15B30322-2CE0-4E0B-A54A-86A2743B73AF@arin.net> <m2h8hahu7c.wl-randy@psg.com> <D0CFFF51-9ADD-49B4-A22A-A89790DBB014@arin.net> <351C77B9-1984-4F1B-B14E-B524E6D18D88@psg.com>
In-Reply-To: <351C77B9-1984-4F1B-B14E-B524E6D18D88@psg.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [199.43.0.117]
Content-Type: text/plain; charset="utf-8"
Content-ID: <7E38A1B92FF99142BE060BA54CD4C2E2@corp.arin.net>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/sidrops/cLKow4wnNHxKGv7HZQHRv7utD5c>
Subject: Re: [Sidrops] ARIN RPKI Repository issue - Wednesday 24 October 2018
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: Fri, 26 Oct 2018 17:17:19 -0000

On 26 Oct 2018, at 6:05 PM, Randy Bush <randy@psg.com> wrote:
> 
>> we’re aiming for high transparency in operations, given the nature/purpose of the service…
> 
> if arin really groked the nature/purpose of the service, a number
> of things would change

Randy - 

That’s quite possible, but note that many things have already been changing:

 - Moved from explicit email logging to access ARIN TAL to click “accept” on TAL page to access
 - Moved from click “accept” on TAL page to simply download TAL from the ARIN TAL page
 - Published explicit directions so software installation tools can download ARIN TAL for user
 - Committed to an easier ROA creation interface as part of the ARIN database-integrated IRR refresh

There’s likely more things that you’d like to see changed with respect to ARIN RPKI service – feel free to send me a list when you have a moment (as we’re likely to revisit a number of things after the UPenn law “ARIN RPKI legal hurdles" study is completed and issues its report in early December.)

Thanks!
/John

John Curran
President and CEO
American Registry for Internet Numbers

v2.23.0 | Report a Bug | By Email