Re: [tlp-interest] Proposed Policy on Rights in IANA Parameter Registry Data

Russ Housley <housley@vigilsec.com> Thu, 17 September 2020 15:56 UTC

Return-Path: <housley@vigilsec.com>
X-Original-To: tlp-interest@ietfa.amsl.com
Delivered-To: tlp-interest@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C312B3A0CE7 for <tlp-interest@ietfa.amsl.com>; Thu, 17 Sep 2020 08:56:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.897
X-Spam-Level:
X-Spam-Status: No, score=-1.897 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_NONE=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 5J9YxZhXP06e for <tlp-interest@ietfa.amsl.com>; Thu, 17 Sep 2020 08:56:41 -0700 (PDT)
Received: from mail.smeinc.net (mail.smeinc.net [209.135.209.11]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 814CC3A0CE6 for <tlp-interest@ietf.org>; Thu, 17 Sep 2020 08:56:41 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mail.smeinc.net (Postfix) with ESMTP id B6C6D300B5B for <tlp-interest@ietf.org>; Thu, 17 Sep 2020 11:56:38 -0400 (EDT)
X-Virus-Scanned: amavisd-new at mail.smeinc.net
Received: from mail.smeinc.net ([127.0.0.1]) by localhost (mail.smeinc.net [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id nLX38HHdw17j for <tlp-interest@ietf.org>; Thu, 17 Sep 2020 11:56:36 -0400 (EDT)
Received: from a860b60074bd.fios-router.home (pool-141-156-161-153.washdc.fios.verizon.net [141.156.161.153]) by mail.smeinc.net (Postfix) with ESMTPSA id 9AB60300AA2 for <tlp-interest@ietf.org>; Thu, 17 Sep 2020 11:56:36 -0400 (EDT)
From: Russ Housley <housley@vigilsec.com>
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.15\))
Date: Thu, 17 Sep 2020 11:56:37 -0400
References: <160030855140.10301.1377983716672020951@ietfa.amsl.com>
To: tlp-interest@ietf.org
In-Reply-To: <160030855140.10301.1377983716672020951@ietfa.amsl.com>
Message-Id: <F6878352-F6DD-458A-B088-7516ADF415C2@vigilsec.com>
X-Mailer: Apple Mail (2.3445.104.15)
Archived-At: <https://mailarchive.ietf.org/arch/msg/tlp-interest/jGjMpo4DO2LlvZ5KLO9IbJCMuts>
Subject: Re: [tlp-interest] Proposed Policy on Rights in IANA Parameter Registry Data
X-BeenThere: tlp-interest@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Discussion of proposed revisions to the Trust Legal Provisions <tlp-interest.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tlp-interest>, <mailto:tlp-interest-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tlp-interest/>
List-Post: <mailto:tlp-interest@ietf.org>
List-Help: <mailto:tlp-interest-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tlp-interest>, <mailto:tlp-interest-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 17 Sep 2020 15:56:44 -0000

The second paragraph of the document  Introduction is fine for the Internet-Draft.  After community discussion, what do you plan to say here?  Just deleting the second paragraph would leave an incomplete section.  I would prefer to see a proposal for the final Introduction and a paragraph that is to be deleted by the RFC Editor prior to publication that talks about providing the background to inform discussion.

In Section 2, you might point to the message by Steve Crocker at ICANN Chairman during the IANA Transition.  That message affirms the stated intent, and IANA was a department of ICANN at the time.

Section 4.1, number 2:  It seems wrong to capitalize "You".

Russ


> On Sep 16, 2020, at 10:09 PM, The IETF Trust <ietf-trust@ietf.org> wrote:
> 
> The IETF Trust is asking for community input on a Proposed Policy on Rights in IANA Parameter Registry Data as explained in Draft-halpern-trust-ianapolicy  (https://www.ietf.org/id/draft-halpern-trust-ianapolicy-00.html)
> 
> Background:  The IANA Parameter Registry Data is not subject to copyright, and is intended to be freely and openly usable by adopters.  However, no formal notice of this appears on the IANA Parameter Registry Data and the absence of a formal notice has caused confusion for some adopters which has resulted in many emails to IANA seeking guidance.    This proposed policy by the IETF Trustees is intended to clarify the situation by providing a formal declaration that the material is to be considered in the Public Domain as detailed in the Creative Commons Zero (CC0) declaration.   
> 
> The IETF Trustees believe that this assertion is in keeping with the current and historic intention for the material, and that this declaration neither adds nor removes any compliance restrictions to the open and free use that is intended for the data in the IANA Parameter Registry.  This proposed policy is merely a means to clarify the intended usage rules to those whom have been confused by the absence of a formal declaration.
> 
> This has been developed by the IETF Trustees with input from the IETF Trust’s legal counsel, and with engagement with IANA. 
> 
> Please read the draft for specifics of the proposal, the legal aspects behind it, and the motivation for the policy before commenting as the draft attempts to address what are anticipated to be common questions on the proposal.
> 
> This consultation will last for 30 days.
> 
> Please send comments TLP-INTEREST@IETF.ORG before October 17,2020
> 
> Thank you,
> Glenn Deen,    IETF Trust Chair on behalf of the IETF Trustees