IETF Logo Mail Archive

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

John Curran <jcurran@arin.net> Sat, 27 October 2018 05:03 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 30A7C12DD85 for <sidrops@ietfa.amsl.com>; Fri, 26 Oct 2018 22:03:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-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 K3VcXZQyrqtR for <sidrops@ietfa.amsl.com>; Fri, 26 Oct 2018 22:03:35 -0700 (PDT)
Received: from smtp1.arin.net (smtp1.arin.net [IPv6:2001:500:110:201::51]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5C5571292AD for <sidrops@ietf.org>; Fri, 26 Oct 2018 22:03:35 -0700 (PDT)
Received: by smtp1.arin.net (Postfix, from userid 323) id AAEA91001F8E; Sat, 27 Oct 2018 01:03:34 -0400 (EDT)
Received: from ashedge01.corp.arin.net (ashedge01.corp.arin.net [199.43.0.122]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by smtp1.arin.net (Postfix) with ESMTPS id E888B1000256; Sat, 27 Oct 2018 01:03:33 -0400 (EDT)
Received: from CAS01ASH.corp.arin.net (10.4.30.62) by ashedge01.corp.arin.net (199.43.0.122) with Microsoft SMTP Server (TLS) id 15.0.847.32; Sat, 27 Oct 2018 01:02:39 -0400
Received: from CAS01ASH.corp.arin.net (10.4.30.62) by CAS01ASH.corp.arin.net (10.4.30.62) with Microsoft SMTP Server (TLS) id 15.0.1210.3; Sat, 27 Oct 2018 01:02:51 -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; Sat, 27 Oct 2018 01:02:51 -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/KAgAAEtwCAAMCFgA==
Date: Sat, 27 Oct 2018 05:02:50 +0000
Message-ID: <3F9D49C5-0812-426B-8E60-CF0E93CC684E@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> <47F7E3F4-6EE9-4DDB-B2A0-8631DA54D111@arin.net> <4638BB0C-DBEA-4A8F-AE25-75D9103356DF@psg.com>
In-Reply-To: <4638BB0C-DBEA-4A8F-AE25-75D9103356DF@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: <F5BB6729E33D9A43B34377D8CBE93225@corp.arin.net>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/sidrops/ObetQQAh_eNPKMWsiLFtMNlEFPM>
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: Sat, 27 Oct 2018 05:03:37 -0000

To my knowledge, all of the RIRs require a contract to provide services, ARIN included. 

(We’re updated the LRSA four times to make changes as requested by the community, but it still might not meet your expectations.) 

/John 

> On 26 Oct 2018, at 7:33 PM, Randy Bush <randy@psg.com> wrote:
> 
> Lotta smoke
> 
> Tell me she the vast majority of noam address space is allowed to have roas without egregious contract. 
> 
> randy, on a phone
> 
>> On Oct 26, 2018, at 10:16, John Curran <jcurran@arin.net> wrote:
>> 
>>> 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
>> 
>> 
>> 
> 
> _______________________________________________
> Sidrops mailing list
> Sidrops@ietf.org
> https://www.ietf.org/mailman/listinfo/sidrops

v2.46.0 | Report a Bug | By Email | System Status