[CRISP-TEAM] Community engagement in developing SLA Fwd: Re: [NRO-IANAXFER] Thank you for the feedback and update on CRISP Team Status

Izumi Okutani izumi at nic.ad.jp
Wed Jan 7 11:57:43 CET 2015


Sounds very reasonable to me. I support to incorporate in the propsal as
well. Thank you Andrei.

Thoughts from others?

After comfirming at the call today, I suggest we share our position on
the IANAXFER list shortly after that, so that we can hear additional
feedback if there is any.


Izumi

On 2015/01/07 19:49, Andrei Robachevsky wrote:
> Izumi, team,
> 
> Izumi Okutani wrote on 07/01/15 11:05:
>> CRISP Team,
>>
>>
>> The second point raised is on Community engagement in developing SLA
>>
>> "May i know how/if the CRISP intend to engage the community in the
>> development of the contract and SLA?"
>>
>> It is not the scope of CRISP Team to take a lead about SLA ofcourse but
>> I think the point of the question is if there will be any community
>> engagement in the development of the contract.
>>
>>
>> What are your thoughts on this?
>>
> 
> I agree that this is outside the scope, since this proposal is concerned
> with high-level requirements and implementation of these will be
> delegated to the RIRs. But also agree that we should respond to this
> question. How about:
> 
> The CRISP team is essentially tasking the RIR staff with developing the
> text of the agreement, but we assume and would strongly encourage the
> RIR staff to do this in a transparent manner that engages the community
> throughout the process.
> 
> That could be the reply to the list, and could even (with some
> massaging) be included in the proposal if people felt that was useful.
> 
> Andrei
> 
> 
>>
>>
>> Izumi
>>
>>
>> -------- Forwarded Message --------
>> Subject: Re: [NRO-IANAXFER] Thank you for the feedback and update on
>> CRISP Team Status
>> Date: Wed, 07 Jan 2015 18:46:30 +0900
>> From: Izumi Okutani <izumi at nic.ad.jp>
>> To: Seun Ojedeji <seun.ojedeji at gmail.com>
>> CC: ianaxfer at nro.net <ianaxfer at nro.net>
>>
>> Dear Seun,
>>
>>
>>> - I had made suggestion about process of building the review team i.e the
>>> formation, charter et all be determined before the transition is
>> completed.
>>> May i know what the CRISP team decided about this?
>>> - May i know how/if the CRISP intend to engage the community in the
>>> development of the contract and SLA?
>>
>> We haven't discussed on these points since they appear to be more
>> detailed than what we are currenting planning to cover in our propsal to
>> ICG.
>>
>> However, I note you are interested to confirm about these points and
>> I'll raise it within CRISP team.
>>
>> Thank you for taking a look into our status and raising what was not
>> clear to you.
>>
>> If there is anyone else who feels your comments have not been considered
>> by CRISP Team from the spreadsheet I shared, it's helpful if you could
>> share it here. Thanks.
>>
>>
>> Regards,
>> Izumi
>>
>> On 2015/01/07 18:21, Seun Ojedeji wrote:
>>> Dear Izumi,
>>>
>>> Thanks for the update. I have just 2 minor comments below:
>>>
>>> - I had made suggestion about process of building the review team i.e the
>>> formation, charter et all be determined before the transition is completed.
>>> May i know what the CRISP team decided about this?
>>> - May i know how/if the CRISP intend to engage the community in the
>>> development of the contract and SLA?
>>>
>>> Regards
>>>
>>> On Wed, Jan 7, 2015 at 9:48 AM, Izumi Okutani <izumi at nic.ad.jp> wrote:
>>>
>>>> Dear Colleagues,
>>>>
>>>>
>>>> CRISP Team would like to thank everyone who have provided your inputs to
>>>> the first draft of our proposal.
>>>>
>>>> We have closed comments for the first draft, and completed to form CRISP
>>>> Team's position on all issues express on <ianaxfer at nro.net> mailing list
>>>> at the 8th CRISP Team call, at UTC13:00 Mon 5th Jan.
>>>>
>>>> CRISP Team is now working to publish the second draft, which is planned
>>>> to be published on Thu 8th Jan. We will make an announcement on this
>>>> mailing list, and call for comments from the global community once it is
>>>> published, as we did for the first draft.
>>>>
>>>> In the meantime, attached is the status list of issue raised on
>>>> <ianaxfer at nro.net> for you to confirm status of CRISP Team
>>>> considerations. Please note this is to be updated as our work progresses.
>>>>
>>>> We are planning to publish the updated issues status list when we
>>>> publish our second draft.
>>>>
>>>> Thank you once again for taking your time to review the first draft of
>>>> our proposal and sharing your views.
>>>>
>>>>
>>>> Best Regards,
>>>> Izumi Okutani
>>>> CRISP Team Chair
>>>>
>>>> _______________________________________________
>>>> ianaxfer mailing list
>>>> ianaxfer at nro.net
>>>> https://www.nro.net/mailman/listinfo/ianaxfer
>>>>
>>>>
>>>
>>>
>>
>>
>>
>>
>> _______________________________________________
>> CRISP mailing list
>> CRISP at nro.net
>> https://www.nro.net/mailman/listinfo/crisp
>>





More information about the CRISP mailing list