[Internal-cg] Fwd: [NRO-IANAXFER] Next steps?
Daniel Karrenberg
daniel.karrenberg at ripe.net
Tue Mar 3 11:51:46 UTC 2015
Kavouss,
a good summary of RIR accountability across all regions is at
https://www.nro.net/about-the-nro/rir-governance-matrix
This is looks pretty clear to me. What is it in particular that is
unclear to you here?
Daniel
On 1.03.15 10:08 , Kavouss Arasteh wrote:
> Step 2 ,ICG Assessement of Cummunity proposals
> Dear Vice chair,
> May you please ask Jari and Alan Barretor Paul Wilson to provide the
> foloowings;
> A COMPARATIVE Table indicating the prcess of accountability currently in
> force and implemented and those which will be required after Transitiion.
> It would be useful to have that comparative Table enabling ICG Members
> to better undersatnd how the accountability of Protocol Parameter and
> Numbers are affected by Transition.
> The reports of these two communities are difficult to make such a
> comparision.
> Without that I will have serious difficulties to comment on the
> exacteness and appropriateness of the content of these two comminities
> on accountability before and after transition.
> By the way, Jari promised to provide a graphic Diagram regarding
> internal accountability being carried out by IETF
> mOREOVER, aLAN bARRET / Paul Wilson ,are respectfully requested to
> provide similar graphic Diagram about the accountability currently in
> force in RIRs ,in particular that RIRs have a more decentralized
> process of five regional communities and the overall accountabilities of
> the entire Rir s are not clear
> Rergards
> KAVOUSS
>
> 2015-02-24 22:36 GMT+01:00 Alissa Cooper <alissa at cooperw.in
> <mailto:alissa at cooperw.in>>:
>
>
> On Feb 24, 2015, at 1:09 PM, WUKnoben
> <wolf-ulrich.knoben at t-online.de
> <mailto: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 <mailto:alissa at cooperw.in>
>> *Sent:* Tuesday, February 24, 2015 9:44 PM
>> *To:* ICG <mailto:internal-cg at icann.org>
>> *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 <mailto: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
>>> <mailto:seun.ojedeji at gmail.com>>
>>> *Cc: *"ianaxfer at nro.net <mailto:ianaxfer at nro.net>"
>>> <ianaxfer at nro.net <mailto: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
>>>> <mailto: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
>>>>>> <mailto: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/>
>>>>>>> <http://www.fuoye.edu.ng <http://www.fuoye.edu.ng/>> Mobile:
>>>>> +2348035233535 <tel:%2B2348035233535>**alt
>>>>>>> email: <http://goog_1872880453
>>>>>>> <http://goog_1872880453/>>seun.ojedeji at fuoye.edu.ng
>>>>>>> <mailto:seun.ojedeji at fuoye.edu.ng>
>>>>>>> <seun.ojedeji at fuoye.edu.ng <mailto:seun.ojedeji at fuoye.edu.ng>>*
>>>>>>>
>>>>>>> The key to understanding is humility - my view !
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>
>>>>>
>>>>>
>>>>
>>>>
>>>
>>>
>>> _______________________________________________
>>> ianaxfer mailing list
>>> ianaxfer at nro.net <mailto:ianaxfer at nro.net>
>>> https://www.nro.net/mailman/listinfo/ianaxfer
>>
>>
>> ------------------------------------------------------------------------
>> _______________________________________________
>> Internal-cg mailing list
>> Internal-cg at icann.org <mailto:Internal-cg at icann.org>
>> https://mm.icann.org/mailman/listinfo/internal-cg
>
>
> _______________________________________________
> Internal-cg mailing list
> Internal-cg at icann.org <mailto:Internal-cg at icann.org>
> https://mm.icann.org/mailman/listinfo/internal-cg
>
>
>
>
> _______________________________________________
> Internal-cg mailing list
> Internal-cg at icann.org
> https://mm.icann.org/mailman/listinfo/internal-cg
>
More information about the Internal-cg
mailing list