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

S Moonesamy <sm+ietf@elandsys.com> Thu, 13 March 2014 07:49 UTC

Return-Path: <sm@elandsys.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 8FC931A095A for <internetgovtech@ietfa.amsl.com>; Thu, 13 Mar 2014 00:49:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.337
X-Spam-Level:
X-Spam-Status: No, score=-2.337 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, RP_MATCHES_RCVD=-0.547, T_DKIM_INVALID=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 4wwbH4GAt0DB for <internetgovtech@ietfa.amsl.com>; Thu, 13 Mar 2014 00:49:35 -0700 (PDT)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id 281E61A094E for <internetgovtech@iab.org>; Thu, 13 Mar 2014 00:49:35 -0700 (PDT)
Received: from SUBMAN.elandsys.com ([197.224.142.145]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id s2D7nCog008823 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 13 Mar 2014 00:49:23 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1394696965; bh=vyyqSMnlaJjfFg48X0zwssyT26VMgN1VeMCroYZSCig=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=l4f2XuBAKC9BPKg9di2D2ljXQBya1doyRkRiYuCtRhqGcXk9ngA3x77oBzHtxQjG/ BWSevFAcyf4wMMKWDP4ri3asO2wUhFzzuATngqjJDZsBVPKPCfzXY7vMI9VHISqy3D GIh2N5RiZhIc22KvvqHgPHBLpNdBSk7RIW65OJco=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=elandsys.com; s=mail; t=1394696965; i=@elandsys.com; bh=vyyqSMnlaJjfFg48X0zwssyT26VMgN1VeMCroYZSCig=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=Ky+eueqW8gdykuF8bnQlBgilb10g1tZ9tej5WE3POOa+RZLmt3bjYTZbJGTLJr+jY bzLtMNH7q4x7dkzAB28YV6OpRgxRLmCW/QRKg1CLlyW/OmPwRPNwg5zLgJJImC8fSQ biFynpxe5TwKovvr8IcaNdzBb2brU+8SVfd1GfGo=
Message-Id: <6.2.5.6.2.20140312231344.0c54d7b8@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Thu, 13 Mar 2014 00:46:05 -0700
To: Geoff Huston <gih@apnic.net>, l.wood@surrey.ac.uk
From: S Moonesamy <sm+ietf@elandsys.com>
In-Reply-To: <3F12C9B5-61B6-4C28-B73A-320D80A6AE17@apnic.net>
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> <290E20B455C66743BE178C5C84F1240847E633476A@EXMB01CMS.surrey.ac.uk> <3F12C9B5-61B6-4C28-B73A-320D80A6AE17@apnic.net>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format="flowed"
Archived-At: http://mailarchive.ietf.org/arch/msg/internetgovtech/uyzpoiD7I0QJI7s-4EhMWV4p0f0
Cc: internetgovtech@iab.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: Thu, 13 Mar 2014 07:49:36 -0000

Hi Geoff,
At 22:23 12-03-2014, Geoff Huston wrote:
>Weaving the web of wording around various RFCs and the distinctions 
>between the IASA, the IAOC and the IETF, I have absolutely no idea 
>whether a) the IETF itself is an ISOC activity per se and b) issues 
>about the intellectual property rights associated with the protocol 
>parameter registry contents vest with any of the preceding bodies. 
>But I thought we were talking principles, and the principle I was 
>espousing was that all intellectual property rights in the content 
>of the protocol parameters registries remains with the IETF, and 
>does not vest with the registry operator. I guess I'm treading on 
>the toes of an historic US position that in the past appeared to be 
>that the intellectual property rights of the IANA protocol parameter 
>registries that were operated under the terms of contracts with 
>variously ARPA, DARPA and the NSF vested with the USG in some 
>fashion, and its a question that we appear to want to avoid as there 
>has never been any statements from the NTIA that expressly disclaim 
>this, and noone appears to want to press the point.

I'll comment about (b).  There is a RFC published in 2011 which 
states that the intellectual property rights of IETF protocol 
parameter assignment information is held by the IETF Trust.  There 
isn't any (formal) agreement about the intellectual property 
rights.  There is, as mentioned above, the legacy stuff.  The bottom 
line is that the legal aspect is unclear.

Regards,
S. Moonesamy