Re: [Internetgovtech] Guiding the Evolution of the IANA Protocol Parameter Registries

Steve Crocker <steve@shinkuro.com> Wed, 12 March 2014 20:56 UTC

Return-Path: <steve@shinkuro.com>
X-Original-To: internetgovtech@ietfa.amsl.com
Delivered-To: internetgovtech@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A6B621A0754 for <internetgovtech@ietfa.amsl.com>; Wed, 12 Mar 2014 13:56:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.319
X-Spam-Level:
X-Spam-Status: No, score=-1.319 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_DSL=1.129, RP_MATCHES_RCVD=-0.547, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, UNPARSEABLE_RELAY=0.001] autolearn=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 GMk2OQA9kaW1 for <internetgovtech@ietfa.amsl.com>; Wed, 12 Mar 2014 13:56:20 -0700 (PDT)
Received: from execdsl.com (remote.shinkuro.com [50.56.68.178]) by ietfa.amsl.com (Postfix) with ESMTP id 9B8301A076A for <internetgovtech@iab.org>; Wed, 12 Mar 2014 13:56:16 -0700 (PDT)
Received: from dummy.name; Wed, 12 Mar 2014 20:56:10 +0000
Content-Type: text/plain; charset="windows-1252"
Mime-Version: 1.0 (Mac OS X Mail 7.2 \(1874\))
From: Steve Crocker <steve@shinkuro.com>
In-Reply-To: <0F0A2653-1FC8-475F-B123-01E96E26CECF@apnic.net>
Date: Wed, 12 Mar 2014 16:56:08 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <C7C8A6F9-85DE-4857-B011-8400C5852A13@shinkuro.com>
References: <53066F72.6080809@cisco.com> <CF2CB88C.1B2CA%alissa@cooperw.in> <53078600.3090104@cisco.com> <CF2CCDF6.1B3E7%alissa@cooperw.in> <53086568.7050707@cisco.com> <3FFD6830-DC12-4707-AE2B-0FE1F251B198@vigilsec.com> <530921E3.7060005@cisco.com> <DFC22E37-7FA1-4973-A804-73C00685419C@iab.org> <DF55C3B2-FF68-4001-B778-4CBC4354CAB6@iab.org> <39ED9EBA-C644-40A4-B45B-9764032CE277@apnic.net> <BA199E69-BA8D-4CFF-BEE4-DE444115C4D9@shinkuro.com> <0F0A2653-1FC8-475F-B123-01E96E26CECF@apnic.net>
To: Geoff Huston <gih@apnic.net>
X-Mailer: Apple Mail (2.1874)
Archived-At: http://mailarchive.ietf.org/arch/msg/internetgovtech/7lmOVUi_cue_2cmv0lM2-lq_wq0
Cc: "Stephen D. Crocker" <steve@shinkuro.com>, internetgovtech@iab.org, "ietf@ietf.org Mailing List" <ietf@ietf.org>
Subject: Re: [Internetgovtech] Guiding the Evolution of the IANA Protocol Parameter Registries
X-BeenThere: internetgovtech@iab.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Internet Governance and IETF technical work <internetgovtech.iab.org>
List-Unsubscribe: <https://www.iab.org/mailman/options/internetgovtech>, <mailto:internetgovtech-request@iab.org?subject=unsubscribe>
List-Archive: <http://www.iab.org/mail-archive/web/internetgovtech/>
List-Post: <mailto:internetgovtech@iab.org>
List-Help: <mailto:internetgovtech-request@iab.org?subject=help>
List-Subscribe: <https://www.iab.org/mailman/listinfo/internetgovtech>, <mailto:internetgovtech-request@iab.org?subject=subscribe>
X-List-Received-Date: Wed, 12 Mar 2014 20:56:21 -0000

Geoff,

Thanks.  No argument.  It was interesting to me as I was speaking during the session and asserting that we have no claim to the intellectual property that we (ICANN) might find ourselves having quite strong feelings if we were told we had to implement restrictive policies.  It’s not a scenario that, to my knowledge, has ever come up before, but I think it fits into your general framework of espousing principles.

Steve

On Mar 12, 2014, at 4:50 PM, Geoff Huston <gih@apnic.net> wrote:

> Hi Steve,
> 
> Firstly I should reiterate that this is not about ICANN. I agree wholeheartedly with the "important observation" in Russ's posting, and I am very heartened to read your undertaking relating to ICANN having no intellectual property interests in the material it publishes in this role as protocol parameter registry operator. For me, it was very welcome as a statement at the meeting, and equally welcome as a statement here, and, while I can only speak personally, I would like to sincerely extend my thanks for making this undertaking.
> 
> My posting was not about the specific, but about the principle. I believe it to be incumbent on the IETF to clearly state the principle, namely that the operator of a protocol parameter registry is doing so at the specific behest of the IETF, and as an agent of the IETF. All intellectual property rights in the content of the registries remains that of the IETF, and does not vest with the registry operator. This is desire that I believe is entirely consistent with your undertaking that ICANN as a protocol parameter registry operator makes no such claim, however I suppose I am wanting this to be a principle that applies generally.
> 
> As to folk changing their mind in the future, its true that the future is a constant source of surprise to us, and statements that include terms such as "never" or "forever" are constantly being mocked by the unfolding of time. But I don't think we need to cross every bridge here - we can at best set forth our values and principles on the day and hope that our successors at least consider what we were trying to achieve and why we thought it to be important as they make their changes to suit their world. These principles appear to be an earnest effort in that direction.
> 
> kind regards,
> 
>   Geoff
> 
> 
> On 13 Mar 2014, at 7:07 am, Steve Crocker <steve@shinkuro.com> wrote:
> 
>> Geoff, et al,
>> 
>> I made a statement in the igovupdate session and I’ll reiterate here in the spirit of using the list as the definitive record and not the face to face session.
>> 
>> ICANN has NO intellectual property interests in the material it publishes.  My understanding of copyright law is that copyright attaches to the creator of content, irrespective of whether they register that copyright.  (There is utility in registering copyrights  I am not enough of expert to expound on those details, nor do I think they’re relevant to this discussion.)
>> 
>> During the discussion in the igovupdate session I heard brief mention of possible issues regarding various RFCs and registries over the years.  These pertained to various government agencies and others, but did not involve ICANN.
>> 
>> If the community desires a formal document saying what I’ve said above, I will personally shepherd it through our system.
>> 
>> Let me address two other points, one that is mentioned below and one that is entirely separate.
>> 
>> I believe the scenario of moving the protocol parameter registries to another operator has already been explored.  I am given to understand that the IETF has conducted exercises that mirror these registries.  I am not familiar with the details.  The IAOC is probably the best group to say more about this.  In any case, I don’t think would be problematic and as a matter of good business practice we will cooperate with any reasonable exercise or demonstration to provide that assurance.
>> 
>> Something that occurred to me during the discussion which I have not seen mentioned before is the following.  All of us follow the principle that the information created by the IETF is available to anyone, anywhere, without cost.  What would happen if the IETF changes its position and requires IANA to either restrict its distribution of information and/or charge for it?  I think we’d have to think carefully about that.  Would the IETF be willing to assert as part of its principles that it won’t do such a thing?
>> 
>> Thanks,
>> 
>> Steve Crocker
>> Chair, ICANN Board of Directors
>> 
> 
> _______________________________________________
> Internetgovtech mailing list
> Internetgovtech@iab.org
> https://www.iab.org/mailman/listinfo/internetgovtech