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

[Brian E Carpenter <[e-mail]>]

Hi,

I support this in general, but have a few comments:

1) I would like to be reassured that ICANN has no problems with this. It seems quite consistent with history and current practice, but ICANN actually operates the IANA service and the public registries, so I don't think we can declare the policy without informing them.

As a reminder, the IETF/IANA MoU says:

       4.4. The IANA shall make available to the public, on-line and free of
       charge, information about each current assignment, including contact
       details for the assignee.

2) I believe that the text should note that most domain registrations are not concerned by this, but that the "technical" domain registrations are. And the same applies to the "specialised" address block assignments. We surely "own" names like .localhost., example.com, in-addr.arpa and address blocks like 64:ff9b:1::/48.

As a reminder, the IETF/IANA MoU says:

       4.3. Two particular assigned spaces present policy issues in addition
       to the technical considerations specified by the IETF: the assignment
       of domain names, and the assignment of IP address blocks. These
       policy issues are outside the scope of this MOU.

       Note that (a) assignments of domain names for technical uses (such as
       domain names for inverse DNS lookup), (b) assignments of specialised
       address blocks (such as multicast or anycast blocks), and (c)
       experimental assignments are not considered to be policy issues, and
       shall remain subject to the provisions of this Section 4...

Regards
   Brian Carpenter

On 17-Sep-20 14:09, The IETF Trust 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)