[CRISP-TEAM] IPR considerations - Final text

Izumi Okutani izumi at nic.ad.jp
Thu Jan 8 04:04:44 CET 2015


It is past the comment time of UTC13:00, and this is not a text
suggestion, simply expressing support for the text for clarity.

Thank you Andrei. This version looks good to me, reflecting comments
from both Alan and myself.


Regards,
Izumi


On 2015/01/08 0:56, Andrei Robachevsky wrote:
> HI,
> 
> Attached is the updated version of the redlined document I sent before,
> now incorporating new text. As before the bulk of the amendments is in
> the section III, and a mention of the  dependencies on IANA/IANA.ORG in
> section I
> 
> The full updated text in section III are:
> 
> Intellectual property rights (IPR) related to the provision of the IANA
> services stay with the community
> 
> There are several intellectual properties related to the provision of
> the IANA services whose status should be clarified as part of the
> transition. Namely, the "IANA" trademark, the "IANA.ORG" domain name,
> and public databases related to the performance of the IANA function.
> 
> It is important that through the stewardship transition the IPR status
> of the registries is clear and ensures free unlimited access to the
> public registry data. It is the expectation of the RIR communities that
> the public number resource registries are in the public domain.  It is
> also the expectation of the RIR communities that non-public information
> related to the IANA number resource registries and corresponding
> services, including the provision of reverse DNS delegation in
> IN-ADDR.ARPA and IP6.ARPA, is managed by the IANA operator and will be
> transferred to its successor(s) along with relevant rights.  It is the
> preference of the RIR communities that all relevant parties acknowledge
> that fact as part of the transition.
> 
> With regards to the IANA trademark and the iana.org domain it is the
> expectation of the RIR communities that both are associated with the
> IANA function and not with a particular IANA functions operator.
> Identifying an organisation, not associated with an IANA operator, that
> hold these assets permanently will facilitate a smooth transition should
> another operator (or operators) be selected at some point in the future.
> It is the preference of the RIR communities that the IANA trademark and
> the IANA.ORG domain name be transferred to an entity independent of the
> IANA functions operator that will ensure these assets are used
> purposefully in a non-discriminatory manner for the benefit of all
> operational communities. From the RIR communities' perspective, the IETF
> Trust would be an acceptable candidate for this role.
> 
> The transfer of the IANA trademark and iana.org domain to the IETF Trust
> will require additional coordination with the other affected communities
> of the IANA functions, namely protocol parameters and names.
> 
> 
> 
> 
> 
> 
> 
> _______________________________________________
> CRISP mailing list
> CRISP at nro.net
> https://www.nro.net/mailman/listinfo/crisp
> 





More information about the CRISP mailing list