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

John Curran <jcurran@arin.net> Sat, 27 October 2018 13: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 522A1130E95 for <sidrops@ietfa.amsl.com>; Sat, 27 Oct 2018 06:03:56 -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 bPV4mJKTmnW5 for <sidrops@ietfa.amsl.com>; Sat, 27 Oct 2018 06:03:54 -0700 (PDT)
Received: from smtp2.arin.net (smtp2.arin.net [IPv6:2001:500:110:201::52]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 58E33130DF2 for <sidrops@ietf.org>; Sat, 27 Oct 2018 06:03:54 -0700 (PDT)
Received: by smtp2.arin.net (Postfix, from userid 323) id 9A03210757B8; Sat, 27 Oct 2018 09:03:51 -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 smtp2.arin.net (Postfix) with ESMTPS id B73BC10757B5; Sat, 27 Oct 2018 09:03:50 -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 09:03:19 -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 09:03:32 -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 09:03:32 -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/KAgAAEtwCAAMCFgIAAcweAgAATR4A=
Date: Sat, 27 Oct 2018 13:03:31 +0000
Message-ID: <9D7159E9-8540-4104-8FF6-D071221D2E0B@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> <3F9D49C5-0812-426B-8E60-CF0E93CC684E@arin.net> <m2lg6jhafc.wl-randy@psg.com>
In-Reply-To: <m2lg6jhafc.wl-randy@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: <EE18A393C8672D4B85CE96D849404F53@corp.arin.net>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/sidrops/TPFi5Y4LYnL9AfgL0DugXEUZ2Cg>
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 13:03:56 -0000

On 27 Oct 2018, at 1:54 PM, Randy Bush <randy@psg.com> wrote:
> 
>> To my knowledge, all of the RIRs require a contract to provide
>> services, ARIN included.
> 
> yes, but only arins may be changed unilaterally by the rir and grabs all
> your rights.

Unilateral change by ARIN was removed in 2015; the current RSA/LRSA only allows amendment to conform to an applicable law/caselaw change or after approval of the ARIN membership by ratification vote (ARIN RSA 12/LRSA 4, Sec. 1(e) https://www.arin.net/resources/agreements/rsa.pdf)

> but we have been through this a thousand times.  

Yes, and this isn’t the appropriate forum in any case – those interested in accurate information should probably review the ARIN website and/or ask on an ARIN mailing list.

Thanks!
/John

John Curran
President and CEO
American Registry for Internet Numbers