[Internal-cg] Fwd: [NRO-IANAXFER] Next steps?

Alissa Cooper alissa at cooperw.in
Tue Feb 24 21:36:09 UTC 2015


On Feb 24, 2015, at 1:09 PM, WUKnoben <wolf-ulrich.knoben at t-online.de> wrote:

> Thanks Alissa,
>  
> here I understand Izumi describing the responsibilities of CRISP vs RIRs.

Yes, and also the important note about them awaiting the conclusion of our Step 2 assessment.

Alissa

> Depending on the level of implementation details needed for the proposal further action may be required (e.g. draft charter of the Review Committee).
> 
> Looking forward to here you later
> 
> Wolf-Ulrich
> 
>  
> From: Alissa Cooper
> Sent: Tuesday, February 24, 2015 9:44 PM
> To: ICG
> Subject: [Internal-cg] Fwd: [NRO-IANAXFER] Next steps?
>  
> This is relevant to some of the questions Wolf-Ulrich has raised about implementation, so I’m forwarding it.
>  
> Begin forwarded message:
> 
>> From: Izumi Okutani <izumi at nic.ad.jp>
>> Subject: Re: [NRO-IANAXFER] Next steps?
>> Date: January 26, 2015 at 6:12:27 PM PST
>> To: Seun Ojedeji <seun.ojedeji at gmail.com>
>> Cc: "ianaxfer at nro.net" <ianaxfer at nro.net>
>>  
>> Hello Seun and colleagues on the IANAXFER list,
>> 
>> 
>> 
>> Thank you once again Seun for your question about the next steps.
>> I think this is a useful question for others in the community as well.
>> 
>> As you are aware, our proposal to the ICG describes high level
>> principles about the Review Committee and the SLA including "IANA
>> Service Level Agreement Principles" in the proposal, so RIRs will
>> consider implementation based on this guidance.
>> 
>> Our role as the CRISP team is to provide guidance to the RIRs in
>> the implementation of the proposal, and the details and process of
>> implementation of the proposal is the responsibility of the RIRs. The
>> charter of the review committee and actual contract text are part of
>> implementation of the proposal which is the responsibility of the RIRs.
>> 
>> Having said this, the CRISP Team believes it is important for the
>> community to have clear visibility that RIRs acknowledges this proposal
>> which references actions by them.
>> 
>> Therefore, after Step2 of the ICG's latest timeline, when the proposals
>> by all three operational communities are consolidated by the ICG, the
>> CRISP Team plans to formally inform the executives of the RIRs about the
>> proposal submitted to the ICG which references actions by the RIRs.
>> 
>> https://www.icann.org/en/system/files/files/icg-process-timeline-07jan15-en.pdf
>> 
>> We expect that there will be formal acknowledgement from the five RIRs
>> about this, so it is clear to the community that the RIRs will take the
>> appropriate steps to implement the proposal from the Number Resources
>> community. We trust each RIR will consult with their respective
>> communities as needed in preparing the SLA, and the Review Committee is
>> to be established in an open and bottom-up manner, as we have described
>> in the proposal.
>> 
>> I hope this clarifies the role of the CRISP team and RIRs in future steps.
>> 
>> 
>> 
>> Regards,
>> Izumi Okutani
>> The CRISP Team
>> 
>> On 2015/01/22 23:45, Seun Ojedeji wrote:
>>> Great thanks for the first level clarification Izumi.
>>> 
>>> Cheers!
>>> 
>>> On Thu, Jan 22, 2015 at 6:06 AM, Izumi Okutani <izumi at nic.ad.jp> wrote:
>>> 
>>>> Hello Seun,
>>>> 
>>>> 
>>>> Just from what I can answer for now,
>>>> 
>>>>>> - SLA requirements
>>>> 
>>>> "IANA Service Level Agreement Principles" are described in Section
>>>> III.A.3 of our proposal, as you are probably aware. This lists
>>>> principles and elements to be included in the SLA.
>>>> 
>>>> Both of the processes listed below will be lead by the RIRs and not the
>>>> CRISP Team. I trust the RIRs will start the process, so that we have
>>>> these them ready before the transition.
>>>> 
>>>>>> - Charter of review committee
>>>>>> - Contract actual text
>>>> 
>>>> I need to double check if there is anything more we can say at this
>>>> stage as the CRISP Team - Thanks for your question and patience!
>>>> 
>>>> 
>>>> Regards,
>>>> Izumi
>>>> 
>>>> On 2015/01/22 13:29, Seun Ojedeji wrote:
>>>>> Hello Izumi,
>>>>> 
>>>>> You may have missed this mail, could you/or any crisp team kindly provide
>>>>> update?
>>>>> 
>>>>> Just to clarify (in line of recent development), not all the 3 items are
>>>>> expected to be developed by this WG but will be good to know when those
>>>>> processes will start.
>>>>> 
>>>>> Thanks
>>>>> 
>>>>> sent from Google nexus 4
>>>>> kindly excuse brevity and typos.
>>>>> On 21 Jan 2015 09:37, "Seun Ojedeji" <seun.ojedeji at gmail.com> wrote:
>>>>> 
>>>>>> Hello Izumi, CRISP team
>>>>>> 
>>>>>> Thanks again to you and the entire team. I just want to ask about what
>>>> the
>>>>>> next line of action will be? i.e are we to wait until the ICG release
>>>> their
>>>>>> final proposal? or while we wait on ICG, we also start the drafting
>>>> process
>>>>>> for the following:
>>>>>> 
>>>>>> - Charter of review committee
>>>>>> - SLA requirements
>>>>>> - Contract actual text
>>>>>> 
>>>>>> Thanks as i look forward to your response
>>>>>> 
>>>>>> Regards
>>>>>> 
>>>>>> --
>>>>>> ------------------------------------------------------------------------
>>>>>> 
>>>>>> 
>>>>>> 
>>>>>> 
>>>>>> 
>>>>>> *Seun Ojedeji,Federal University Oye-Ekitiweb:
>>>>>> http://www.fuoye.edu.ng <http://www.fuoye.edu.ng> Mobile:
>>>> +2348035233535**alt
>>>>>> email: <http://goog_1872880453>seun.ojedeji at fuoye.edu.ng
>>>>>> <seun.ojedeji at fuoye.edu.ng>*
>>>>>> 
>>>>>> The key to understanding is humility - my view !
>>>>>> 
>>>>>> 
>>>>>> 
>>>>> 
>>>> 
>>>> 
>>> 
>>> 
>> 
>> 
>> _______________________________________________
>> ianaxfer mailing list
>> ianaxfer at nro.net
>> https://www.nro.net/mailman/listinfo/ianaxfer
> 
> 
> _______________________________________________
> Internal-cg mailing list
> Internal-cg at icann.org
> https://mm.icann.org/mailman/listinfo/internal-cg

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mm.icann.org/pipermail/internal-cg/attachments/20150224/55caec1b/attachment-0001.html>


More information about the Internal-cg mailing list