[CRISP-TEAM] Draft response/position: IANA IPR issues

[Izumi Okutani]

Alan and CRISP Team,


 > When an end user or RIR receives address space, they also receive an
 > associated subdomain under IN-ADDR.ARPA or IP6.ARPA.  I think that the
 > data associated with managing the subdomains under IN-ADDR.ARPA and
 > IP6.ARPA domains, should be subject to the same intellectual property
 > considerations as the data associated with the allocation or assignment
 > of IPv4 and IPv6 addresses (which is also reflected in the WHOIS
 > database).  I don't have a wording suggestion, but I think that we
 > should make that point.
 >
 > I think it's perfectly reasonable for the IAB to cotinue to be the
 > registered administrative contact for the .ARPA top-level domain, and
 > for the IANA operator to be the technical contact.


My current understanding is that for ".arpa" TLD, NTIA is involved as 
TLD, but IN-ADDR.ARPA or IP6.ARPA are the second level domain, so NTIA 
does not have direct involvement.

It's not totally clear to me whether there will be any changes in 
intellectual property rights on IN-ADDR.ARPA or IP6.ARPA, as a result of 
NTIA's stewardship transition, if ".arpa" domain continues to be under 
the IETF. Perhaps someone with more legal expertise can give us a more 
clear picture.

Based on this understanding (and I welcome corrections if this is a 
wrong understanding), if the suggested description will be added, I feel 
it's important to clarify that this it not the part where NTIA is 
directly involved.


Izumi



On 2014/12/31 22:39, Alan Barrett wrote:
> On Mon, 29 Dec 2014, Andrei Robachevsky wrote:
>> Please find below a description for the IPR issues, along with the
>> proposed responses. The IPR issue covers database rights, trademarks as
>> well as IANA.ORG, IN-ADDR.ARPA and IP6.ARPA domains.
>
> Thank you.  It's especially useful to have references to
> appropriate RFCs and sections of the NTIA IANA contract.
>
>> *Issue: Intellectual Property Rights/IN-ADDR.ARPA and IP6.ARPA domains
>> ---------------------------------------------------------------
>> *Background and rationale:
>>
>> Contrary to the issue related to IANA.ORG domain the holdership of the
>> above domains is with the IAB, aligned with the policy for these
>> registries specified in RFC3172 "Management Guidelines & Operational
>> Requirements for the Address and Routing Parameter Area Domain
>> ("arpa")". Specifically, these zones are delegated to IANA by the
>> Internet Architecture Board (���IAB���) and ���[s]ub-delegations
>> within this
>> hierarchy are undertaken in accordance with the IANA���s address
>> allocation practices��� (RFC3172).
>>
>> *Proposed text in the response:
>>
>> It is unclear to me if there are any IPR concerns from the RIR
>> communities associated with these domains. Especially since this service
>> is outside the scope of the NTIA contract. On a separate track, the
>> CRISP team may, along with the response, provide a recommendation that
>> an MoU between the RIRs and the IETF and IAB is created that will cover
>> the overlaps and express the mutual commitment to open and reliable
>> operation of the global registry system for the benefit of the community.
>>
>> No specific text in the response.
>
> When an end user or RIR receives address space, they also receive an
> associated subdomain under IN-ADDR.ARPA or IP6.ARPA.  I think that the
> data associated with managing the subdomains under IN-ADDR.ARPA and
> IP6.ARPA domains, should be subject to the same intellectual property
> considerations as the data associated with the allocation or assignment
> of IPv4 and IPv6 addresses (which is also reflected in the WHOIS
> database).  I don't have a wording suggestion, but I think that we
> should make that point.
>
> I think it's perfectly reasonable for the IAB to cotinue to be the
> registered administrative contact for the .ARPA top-level domain, and
> for the IANA operator to be the technical contact.
>
> --apb (Alan Barrett)
>
> _______________________________________________
> CRISP mailing list
> CRISP at nro.net
> https://www.nro.net/mailman/listinfo/crisp