Re: [Ianaplan] Transition proposal for naming-related functions

John Curran <jcurran@arin.net> Mon, 04 May 2015 21:50 UTC

Return-Path: <jcurran@arin.net>
X-Original-To: ianaplan@ietfa.amsl.com
Delivered-To: ianaplan@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 600211B2CA6 for <ianaplan@ietfa.amsl.com>; Mon, 4 May 2015 14:50:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.909
X-Spam-Level:
X-Spam-Status: No, score=-1.909 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
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 sfYX_Tk6gyRb for <ianaplan@ietfa.amsl.com>; Mon, 4 May 2015 14:50:32 -0700 (PDT)
Received: from smtp1.arin.net (smtp1.arin.net [IPv6:2001:500:4:13::33]) by ietfa.amsl.com (Postfix) with ESMTP id D64511B2CA0 for <ianaplan@ietf.org>; Mon, 4 May 2015 14:50:31 -0700 (PDT)
Received: by smtp1.arin.net (Postfix, from userid 323) id 8AA07164E70; Mon, 4 May 2015 17:50:31 -0400 (EDT)
Received: from chaedge01.corp.arin.net (chaedge01.corp.arin.net [192.149.252.118]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by smtp1.arin.net (Postfix) with ESMTP id 9D700164E5E; Mon, 4 May 2015 17:50:30 -0400 (EDT)
Received: from CHACAS01.corp.arin.net (10.1.30.107) by chaedge01.corp.arin.net (192.149.252.118) with Microsoft SMTP Server (TLS) id 14.3.210.2; Mon, 4 May 2015 17:56:34 -0400
Received: from CHAMBX01.corp.arin.net ([fe80::1cef:1d7:cca9:5953]) by CHACAS01.corp.arin.net ([fe80::a98b:1e52:e85a:5979%13]) with mapi id 14.03.0224.002; Mon, 4 May 2015 17:50:29 -0400
From: John Curran <jcurran@arin.net>
To: Steve Crocker <steve@shinkuro.com>
Thread-Topic: [Ianaplan] Transition proposal for naming-related functions
Thread-Index: AQHQhrRWivG3jDBxNUeO1Tu1DRM6Iw==
Date: Mon, 4 May 2015 21:50:29 +0000
Message-ID: <E381F582-33AE-40DF-A66C-8F8631064ED3@arin.net>
References: <6FADE19B-E3BD-48F8-9A2D-91FA6F88E6DC@cooperw.in> <554637C4.2010400@gondrom.org> <64F5CADC-5739-4CB1-B2E3-BAA3B21DA0EB@cooperw.in> <C6F030D4-58DF-4B2B-969E-6D4F2B00C742@shinkuro.com>
In-Reply-To: <C6F030D4-58DF-4B2B-969E-6D4F2B00C742@shinkuro.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [192.149.252.96]
Content-Type: multipart/alternative; boundary="_000_E381F58233AE40DFA66C8F8631064ED3arinnet_"
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/ianaplan/81NKQgBEHiEt6y64l_y-f6G1jsY>
Cc: Tobias Gondrom <tobias.gondrom@gondrom.org>, "ianaplan@ietf.org" <ianaplan@ietf.org>, Alissa Cooper <alissa@cooperw.in>
Subject: Re: [Ianaplan] Transition proposal for naming-related functions
X-BeenThere: ianaplan@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IANA Plan <ianaplan.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ianaplan>, <mailto:ianaplan-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ianaplan/>
List-Post: <mailto:ianaplan@ietf.org>
List-Help: <mailto:ianaplan-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ianaplan>, <mailto:ianaplan-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 04 May 2015 21:50:35 -0000

On May 4, 2015, at 4:56 PM, Steve Crocker <steve@shinkuro.com<mailto:steve@shinkuro.com>> wrote:

Alyssa, Tobias, et al,

We normally take time internally to coordinate our formal statements, but I consider this particular detail to be unambiguous, settled long ago, and something I spoke forcefully about at the IETF meeting in London, so I’ll speak immediately on this list.

ICANN publishes the IANA registries for anyone to use without charge, and it asserts no ownership or control of the information in the registries.  No matter what additional structures are created, this basic rule must continue.  There are no subtle or hidden meanings here, and if anyone manages to see an ambiguity, I can assure you none is intended and we will be happy to restate this in language that removes the perceived ambiguity.  Anything less would be inconsistent with the spirit, history and ethic of the IANA function.

Steve -

That good to know, and matches the expectations stated in the Internet number community’s proposal
for IANA Stewardship Transition planning (i.e. the CRISP team proposal) -

               "It is important that the IPR status of the registries remains clear and ensures free and unrestricted access to the public registry data throughout the stewardship transition. It is the expectation of the Internet Number Community that the IANA Number Registries are in the public domain.

<https://www.nro.net/wp-content/uploads/ICG-RFP-Number-Resource-Proposal.pdf>

FYI,
/John

John Curran
President and CEO
ARIN