[CRISP-TEAM] Feedback before UTC14:30 Re: Draft response on the IANAXFER Fwd: Re: Next steps?

Mon Jan 26 16:22:01 CET 2015

Thanks for very useful suggestions Michael and John for expressing support.

I agree with the suggestions and reflected them, with two minor change -

1. I swapped order of sensentences in the third paragraph, as it
    sounded repetetives in the original order. It is now structured as:

     - General distinction of proposal/implementation-->
       listing specific points considered as implementation.
     - Old version was the otherway around)

2. Added "Having said this" at the beginning of the fourth paragraph.
    Would like to give the message, we don't simply say that's just
    implementation and non of our business but we tried to clarify
    possible question from the community.

I do want to make sure we are all comfortable as the CRISP Team with 
what we reply for the next steps, so I welcome further comments:

   Until UTC23:59 today 26th Jan.

I will incorporate comments received until then and plan to send the 
reply at UTC01:20am 27th Jan.

Thanks,
Izumi

----
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/26 23:40, Sweeting, John wrote:
> I like these suggested changes
>
> +1
>
> On 1/26/15, 9:37 AM, "Michael Abejuela" <mabejuela at arin.net> wrote:
>
>> Just a few edits for the groups consideration:
>>
>> Any reference to ��require�� perhaps is better changed to ��reference��?
>>
>> ��RIRs acknowledges this proposal which require actions by them��
>> to
>> ��RIRs acknowledge this proposal which references actions by them"
>>
>>
>> and
>>
>> "submitted to the ICG which require actions by the RIRs"
>>
>> to
>> "submitted to the ICG which references actions by the RIRs"
>>
>>
>> And this reference to be slightly changed as follows:
>>
>> "that necessary actions will be taken by RIRs to implement the proposal"
>> to
>>
>> ��that the RIRs will take the appropriate steps to implement the proposal"
>>
>> Lastly, a couple minor style/typo edits:
>>
>> "The charter of review committee and Contract actual text is the
>> implementation of the proposal where RIRs are responsible.��
>> to
>> ��The charter of the review committee and actual contract text are part of
>> implementation of the proposal which is the responsibility of the RIRs��
>>
>> "While our role as the CRISP Team is providing guidance to the RIRs in the
>> implementation, and the decision of the implementation and its
>> preparations is for the RIRs to make"
>> To
>> ��While our role as the CRISP team is to provide guidance to the RIRs in
>> the implementation of the proposal, the details and process of
>> implementation of the proposal is the responsibility of the RIRs.
>>
>> "RIRs to make, the CRISP Team believe it is important��
>> to
>> ����responsibility of the RIRs.(edit from above) The CRISP Team believes it
>> is important...��  (breaking into separate sentence and adding ��s�� to
>> believe)
>>
>> "We trust the RIRs will consult with relevant community as needed in
>> preparing the SLA��
>> to
>> ��We trust each RIR will consult with their respective communities as
>> needed in preparing the SLA��
>>
>>
>> Just a few of my thoughts.
>>
>> Thanks,
>> -Michael
>>
>>
>>
>>
>>
>>
>> --
>> Michael R. Abejuela
>> Associate General Counsel
>> ARIN
>> 3635 Concorde Parkway
>> Suite 200
>> Chantilly, VA 20151
>> (703) 227-9875 (p)
>> (703) 263-0111 (f)
>> mabejuela at arin.net
>>
>> Confidentiality Notice: This e-mail message, including any attachments, is
>> for the sole use of the intended recipient(s) and may contain confidential
>> and privileged information.  Any unauthorized review, copy, use,
>> disclosure, or distribution is prohibited.   If you are not the intended
>> recipient, please contact the sender by reply e-mail and destroy all
>> copies of the original message.
>>
>>
>>
>>
>>
>>
>>
>> On 1/26/15, 6:38 AM, "Izumi Okutani" <izumi at nic.ad.jp> wrote:
>>
>>> CRISP Team,
>>>
>>>
>>> For this as well, I will wait until UTC14:30 today Jan 26th for feedback
>>> before sending this out.
>>>
>>> Please let me know if you have any concerns/suggestions for changes or
>>> would like me to hold sending it at above time, so you have more time to
>>> review.
>>>
>>>
>>>
>>> Thanks,
>>> Izumi
>>>
>>>
>>> On 2015/01/24 2:10, Izumi Okutani wrote:
>>>> CRISP Team,
>>>>
>>>>
>>>> Please see my draft response to the IANAXFER list regarding the next
>>>> steps.
>>>>
>>>> I tried to incorporate our discussions in "Future steps and
>>>> communicating with RIRs" thread, and welcome any feedback or
>>>> clarifications you may have.
>>>>
>>>> Before I send this out, I do wish to hear especially from RIR staff who
>>>> are the CRISP Team members, in case this description about our
>>>> expections from the RIRs causes any issues or concerns for the RIRs.
>>>>
>>>>
>>>> Thanks,
>>>> Izumi
>>>>
>>>>
>>>> ----
>>>> 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.
>>>>
>>>> The charter of review committee and Contract actual text is the
>>>> implementation of the proposal where RIRs are responsible.
>>>>
>>>> While our role as the CRISP Team is providing guidance to the RIRs in
>>>> the implementation, and the decision of the implementation and its
>>>> preparations is for the RIRs to make, the CRISP Team believe it is
>>>> important for the community to have clear visibility that RIRs
>>>> acknowledges this proposal which require 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 require 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 necessary actions will
>>>> be taken by RIRs to implement the proposal from the Number Resources
>>>> community. We trust the RIRs will consult with relevant community 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
>>>>
>>>>
>>>>
>>>>
>>>> -------- Forwarded Message --------
>>>> Subject: Re: Next steps?
>>>> Date: Thu, 22 Jan 2015 14:06:05 +0900
>>>> From: Izumi Okutani <izumi at nic.ad.jp>
>>>> To: Seun Ojedeji <seun.ojedeji at gmail.com>
>>>> CC: ianaxfer at nro.net
>>>>
>>>> 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 !
>>>>>>
>>>>>>
>>>>>>
>>>>>
>>>>
>>>>
>>>>
>>>>
>>>> _______________________________________________
>>>> 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.
>