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

"Joel M. Halpern" <> Fri, 18 September 2020 00:20 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 0EEFB3A0F7B for <>; Thu, 17 Sep 2020 17:20:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -2.121
X-Spam-Status: No, score=-2.121 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, NICE_REPLY_A=-0.001, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: (amavisd-new); dkim=pass (1024-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id UKdCXpHEqHtB for <>; Thu, 17 Sep 2020 17:20:21 -0700 (PDT)
Received: from ( []) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id BC4823A0F79 for <>; Thu, 17 Sep 2020 17:20:21 -0700 (PDT)
Received: from localhost (localhost []) by (Postfix) with ESMTP id 4BsvcP4YfGz1pByj; Thu, 17 Sep 2020 17:20:21 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=2.tigertech; t=1600388421; bh=Z9jkpy2rVaoZhTkLd9j7L4JLw8yZqdCrDMu4KN57tY4=; h=Subject:To:References:From:Date:In-Reply-To:From; b=QjDDx06kZqZJKKUvl+9xYvFuo60c6JLSOQ1gRFfBMSOxvf/8kn3U+QURhY9JElfmW pIGKyiOQ2U9oDRTKTL/ubu1eURSrlxu4LzqbTtGTdcDqvF9Wqo35STIUWONETjeFsk fkD5r7rkJt5Q6P4QgbLPsmU6s83Bujh0GaZuTWe0=
X-Quarantine-ID: <W-6zD4tpqkKk>
X-Virus-Scanned: Debian amavisd-new at
Received: from [] ( []) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by (Postfix) with ESMTPSA id 4BsvcP0CzGz1pByc; Thu, 17 Sep 2020 17:20:20 -0700 (PDT)
To: "R. Atkinson" <>,
References: <> <>
From: "Joel M. Halpern" <>
Message-ID: <>
Date: Thu, 17 Sep 2020 20:20:19 -0400
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:68.0) Gecko/20100101 Thunderbird/68.12.0
MIME-Version: 1.0
In-Reply-To: <>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Language: en-US
Content-Transfer-Encoding: 8bit
Archived-At: <>
Subject: Re: [tlp-interest] Proposed Policy on Rights in IANA Parameter Registry Data
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Discussion of proposed revisions to the Trust Legal Provisions <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Fri, 18 Sep 2020 00:20:23 -0000

On the one hand, it is clearly not the trust's intention to change the 
IANA policies for any of the allocation.

On the other hand, with the existing understanding of policy (that we 
are trying to formalize) anyone can copy the IANA data to their own 
site, and then ad entries claiming other values on their site.  I do not 
know of any way we can sensibly change the terms to prevent that.

Was that the abuse case you had in mind Ran, or were you considering 
some other kind of problem?

On 9/17/2020 7:37 PM, R. Atkinson wrote:
>> On Sep 16, 2020, at 22:09, The IETF Trust <> wrote:
>> 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.
> Hi,
> I think it likely that such a formal declaration would cause people to believe
> that anyone can use OR allocate — any value (including values which are
> reserved or otherwise not yet formally assigned by IANA) for any purpose
> they wish.
>  From a protocol interoperability perspective, it is important that the current
> situation where defined policies guide IANA and IANA controls what is in
> the IANA registries remain under IETF & IANA control.
> The alternative to the current policy-driven IANA management of the IANA
> registries is likely to be chaos and increased non-interoperability.
> It might be (not sure) that this concern could be resolved by some declaration
> other than CC0 or by adding additional words as an integral part of some
> declaration (to be written by Trust lawyers) in the style of CC0 but explicitly
> reserving IANA control over registry allocations (in accord with the various
> allocation policies which have been defined and will be defined in future).
> Yours,
> Ran
> _______________________________________________
> tlp-interest mailing list