[CRISP-TEAM] VI. Community Process Re: Updated proposal draft - reordering answers edit

[Izumi Okutani]

In VI. Community Process Section, I'm not sure we answered this question :

"An assessment of the level of consensus behind your community’s 
proposal, includinga description of areas of contention or disagreement."

I feel it's important to clearly explain and demonstrate we overcame 
differences and reached an agreement.

My suggestion is to briefly describe major differences in proposals in 
each RIR region and how CRISP team agreed to accomodate. Also explain 
each region went through consensus process/conducted survey.

We may want to add observations, after the 2nd draft that no major 
concerns were expressed on the global/regional MLs for the published 
draft as a way of seeing the level of consensus (which I hope would be 
true).

Any thoughts about this ?

Izumi

(2014/12/23 5:13), Michael Abejuela wrote:
> Hello Everyone,
>
> Please find attached the updated proposal draft as discussed during the conference call earlier today.  You will observe both a redline version highlighting the changes proposed by myself, Izumi and Alan.  In addition, a clean version is attached for ease of review that includes minor formatting changes.
>
> Please let me know if you have any questions.  Izumi and Alan, I trust I was able to capture all of your edits but please review and let me know if I have missed any.  I look forward to the team�s comments.
>
> 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<mailto: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.
>