[CRISP-TEAM] IANA Intellectual Property Rights: Minimum Requirements

Sweeting, John john.sweeting at twcable.com
Thu Oct 15 14:45:32 CEST 2015


+1

Sent from my iPhone

> On Oct 15, 2015, at 7:16 AM, Andrei Robachevsky <robachevsky at isoc.org> wrote:
>
> Colleagues, further to this...
>
> It was brought to my attention that by saying "It is the view of the
> CRISP Team that these requirements are..." we may get a better leverage
> to ensure that the community requirements are met, and met in time.
>
> Thinking more about this, I tend to agree that at this stage speaking
> with our own voice has advantages, so I am fine with Izumi's suggestion.
>
> Andrei
>
> Andrei Robachevsky wrote on 15/10/15 10:10:
>> Hi Izumi,
>>
>> This is an important point indeed.
>>
>> My suggestion was based on the general assumption that all items
>> specified in the proposal must be implemented as part of the transition:
>> the SLA, the Review Committee setup and the IPR. Put it another way - we
>> cannot say the transition is complete before all the requirements and
>> expectations are met, can we?
>>
>> Since the objective of this document was to better articulate these
>> requirements, I thought articulating the timing aspect was also important.
>>
>> Andrei
>>
>> Izumi Okutani wrote on 15/10/15 02:12:
>>> CRISP Team,
>>>
>>>
>>> Based on Andrei's suggestion, I worked on to add the text "From the Internet Number Community’s perspective these requirements must be implemented as part of the transition." and have a suggestion for a change.
>>>
>>> May I suggest we say :
>>> - "It is the view of the CRISP Team that these requirements are..." instead of "From the Internet Number Community's perspective"?
>>>
>>> In reviewing our proposal, I wonder if we can say "the Internet Number Community's perspective" but it is certainly true that the CRISP Team have discussed and agreed on this.
>>> Do you have any concerns about this suggested change?
>>>
>>> I have drafted our message for the three operational communities, adding our observation about the suggested approach on the IANAPLAN.
>>> Please share your comments before UTC13:00 Friday 16th Oct.
>>>
>>> I would like to send this out to the global ianaxfer, IANAPLAN and CWG-Stewardship MLs before COB Friday 16th Oct Dublin time so people can see before the start of ICG meeting.
>>>
>>>
>>> (FYI, I'm flying out today, at UTC13:00 and will arrive in Dublin 12:05pm local time. I am not likely to be able to respond to e-mails during these times + 2 hours before/after)
>>>
>>>
>>> ----
>>> Dear all,
>>>
>>>
>>> The CRISP Team would like to share the minimum requirements we have developed on the IANA Intellectual Property Rights.
>>> They will serve to highlight the key points from the number community perspective in coordination among the operational communities to prepare for the IPR implementation.
>>>
>>> Further, we note that the IETF community has shared an approach for implementation of the IPR on the IANAPLAN mailing list: https://mailarchive.ietf.org/arch/msg/ianaplan/gbPZgVdXAKIQKJRM1po6Nbod-6w
>>>
>>> Based on an understanding that details of the text of the agreements are to be further considered with coordination among the three operational communities, the CRISP Team observes no inconsistencies between the approach introduced in the IANAPLAN and the minimum IPR requirements for the numbers community. We support this approach and open to discuss further details in how we prepare its implementation.
>>>
>>>
>>> ===
>>>
>>> IANA Intellectual Property Rights: Minimum Requirements
>>>
>>> This document outlines the Internet Number Community’s minimum requirements regarding IANA Intellectual Property Rights (IPR), as expressed in the Number Community proposal.
>>> It is the view of the CRISP Team that these requirements must be implemented as part of the transition.
>>>
>>> Minimum Requirements Regarding the IANA Trademark and IANA.ORG <http://iana.org/>
>>>
>>> The IANA trademark and the IANA.ORG <http://iana.org/> domain name will be associated with the IANA numbering services and not with a particular IANA Numbering Services Operator.
>>>
>>> The IANA trademark and the IANA.ORG <http://iana.org/> domain will be transferred and permanently held by an organisation that:
>>>
>>> -       Is not the IANA Numbering Services Operator
>>> -       Is an entity independent of the IANA Numbering Services Operator
>>> -       Is neutral, trusted by the community of IANA stakeholders and has a proven track record of competence and transparency
>>> -       Will facilitate a smooth transition of licenses and permissions should another operator (or operators) be selected in the future
>>> -       Will ensure that these assets are used in a non-discriminatory manner for the benefit of the entire Internet community
>>>
>>> From the Internet Number Community’s perspective, the IETF Trust would be an acceptable candidate for this role based on the minimum requirements described above.
>>>
>>> Minimum Requirements Regarding the IPR Status of Registries Related to the Performance of the IANA Numbering Services
>>>
>>> The IPR status of registries related to the performance of IANA numbering services must ensure free and unrestricted access to the public registry data throughout the stewardship transition and beyond.
>>>
>>> In particular:
>>>
>>> -       The IANA Number Registries must be in the public domain
>>> -       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)
>>> -       All rights to non-public information related to the IANA number resource registries and corresponding services must be transferred to the RIRs
>>>
>>> == end
>>>
>>>
>>> Regards,
>>> Izumi Okutani and Nurani Nimpuno on behalf of the CRISP Team
>>>
>>>
>>>> On 2015/10/13 22:43, Nurani Nimpuno wrote:
>>>> Thanks for that Andrei.
>>>>
>>>> Are there any objections from the group to including this in the text?
>>>>
>>>> Nurani
>>>>
>>>>> On 13 okt 2015, at 12:02, Andrei Robachevsky <robachevsky at isoc.org> wrote:
>>>>>
>>>>> Nurani, I do not think we agreed on the exact text. How about the
>>>>> following (as a closing sentence:
>>>>>
>>>>> "From the Internet Number Community’s perspective these requirements
>>>>> must be implemented as part of the transition".
>>>>>
>>>>> What others think about this?
>>>>>
>>>>> Andrei
>>>>>
>>>>>
>>>>> Nurani Nimpuno wrote on 13/10/15 11:26:
>>>>>> Ah my apologies if I missed that. It was not clear to me that we had agreed that this should go into this document.
>>>>>>
>>>>>> Was there agreed text on this?
>>>>>>
>>>>>> Nurani
>>>>>>
>>>>>>> On 13 okt 2015, at 10:49, Andrei Robachevsky <robachevsky at isoc.org> wrote:
>>>>>>>
>>>>>>> Hi Nurani,
>>>>>>>
>>>>>>> I was under the impression that we agreed to reflect in this document
>>>>>>> that the requirements must be implemented as part of the transition,
>>>>>>> before the NTIA contract expires.
>>>>>>>
>>>>>>> Thanks,
>>>>>>>
>>>>>>> Andrei
>>>>>>>
>>>>>>> Nurani Nimpuno wrote on 13/10/15 08:20:
>>>>>>>> Hi all,
>>>>>>>>
>>>>>>>> As agreed at the last CRISP call, we added a reference about the IETF
>>>>>>>> trust to the text that Paul wrote. We will share this with the global
>>>>>>>> nro-ianaxfer list as well as the other communities.
>>>>>>>>
>>>>>>>> As noted in the last CRISP call, the IANAPLAN group has also published a
>>>>>>>> statement on the IPR issue, which the CRISP team found was consistent
>>>>>>>> with the Number Community’s minimum requirements.
>>>>>>>>
>>>>>>>> Kind regards,
>>>>>>>>
>>>>>>>> Nurani
>>>>>>>>
>>>>>>>> ===
>>>>>>>>
>>>>>>>> *IANA Intellectual Property Rights: Minimum Requirements*
>>>>>>>> * *
>>>>>>>> This document outlines the Internet Number Community’s minimum
>>>>>>>> requirements regarding IANA Intellectual Property Rights (IPR), as
>>>>>>>> expressed in the Number Community proposal.
>>>>>>>>
>>>>>>>> *Minimum Requirements Regarding the IANA Trademark/ /and IANA.ORG
>>>>>>>> <http://IANA.ORG>//*
>>>>>>>>
>>>>>>>> The IANA trademark and the IANA.ORG <http://IANA.ORG> domain name will
>>>>>>>> be associated with the IANA numbering services and not with a particular
>>>>>>>> IANA Numbering Services Operator.
>>>>>>>>
>>>>>>>> The IANA trademark and the IANA.ORG <http://IANA.ORG> domain will be
>>>>>>>> transferred and permanently held by an organisation that:
>>>>>>>>
>>>>>>>> -       Is not the IANA Numbering Services Operator
>>>>>>>> -       Is an entity independent of the IANA Numbering Services Operator
>>>>>>>> -       Is neutral, trusted by the community of IANA stakeholders and
>>>>>>>> has a proven track record of competence and transparency
>>>>>>>> -       Will facilitate a smooth transition of licenses and permissions
>>>>>>>> should another operator (or operators) be selected in the future
>>>>>>>> -       Will ensure that these assets are used in a non-discriminatory
>>>>>>>> manner for the benefit of the entire Internet community
>>>>>>>>
>>>>>>>> From the Internet Number Community’s perspective, the IETF Trust would
>>>>>>>> be an acceptable candidate for this role based on the minimum
>>>>>>>> requirements described above.
>>>>>>>>
>>>>>>>> *Minimum Requirements Regarding the IPR Status of Registries Related to
>>>>>>>> the Performance of the IANA Numbering Services*
>>>>>>>>
>>>>>>>> The IPR status of registries related to the performance of IANA
>>>>>>>> numbering services must ensure free and unrestricted access to the
>>>>>>>> public registry data throughout the stewardship transition and beyond.
>>>>>>>>
>>>>>>>> In particular:
>>>>>>>>
>>>>>>>> -       The IANA Number Registries must be in the public domain
>>>>>>>> -       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)
>>>>>>>> -       All rights to non-public information related to the IANA number
>>>>>>>> resource registries and corresponding services must be transferred to
>>>>>>>> the RIRs
>>>>>>>>
>>>>>>>> == end
>>>>>>>>
>>>>>>>>
>>>>>>>> _______________________________________________
>>>>>>>> CRISP mailing list
>>>>>>>> CRISP at nro.net
>>>>>>>> https://www.nro.net/mailman/listinfo/crisp
>>>>
>>>>
>>>> _______________________________________________
>>>> CRISP mailing list
>>>> CRISP at nro.net
>>>> https://www.nro.net/mailman/listinfo/crisp
>
> _______________________________________________
> CRISP mailing list
> CRISP at nro.net
> https://www.nro.net/mailman/listinfo/crisp

________________________________

This E-mail and any of its attachments may contain Time Warner Cable proprietary information, which is privileged, confidential, or subject to copyright belonging to Time Warner Cable. This E-mail is intended solely for the use of the individual or entity to which it is addressed. If you are not the intended recipient of this E-mail, you are hereby notified that any dissemination, distribution, copying, or action taken in relation to the contents of and attachments to this E-mail is strictly prohibited and may be unlawful. If you have received this E-mail in error, please notify the sender immediately and permanently delete the original and any copy of this E-mail and any printout.



More information about the CRISP mailing list