[CRISP-TEAM] [Feedback] CRISP Team Statement: Our role and the next steps

[Sweeting, John]

Hi Izumi,

The description is fine.

Thanks,
John

On 4/9/15, 9:27 AM, "Izumi Okutani" <izumi at nic.ad.jp> wrote:

>CRISP Team,
>
>
>As a follow up from yesterday's call, this is a very preliminary draft of
>the statement to share with our global and regional mailing lists.
>I tried to write more on how the communinity can be enaged but I found it
>hard, as this is the part that RIRs will be consulting with the
>community, not the CRISP Team.
>
>I welcome you all to comment in the coming 24h.
>Let's target to share, at this point, at around UTC15:00 10 Apri to the
>global IANAXFER list and each of the RIR mailing list within Friday your
>time.
>
>To ARIN region representatives,
>Please confirm whether the description of the session and what to expect
>is correct.
>
>
>
>German/RIR staff,
>May I suggest to add a list of coming RIR meetings at :
>
>
>https://www.nro.net/nro-and-internet-governance/iana-oversight/sla-develop
>ments
>
>This way, the community can not only confirm what was discussed but also
>what to expect as future engagement opportunities.
>
>
>
>
>Izumi
>
>
>--------------------------------------------------------------------------
>---------
>Subject: Next Steps in the Process and the Community Engagement
>
>
>
>Dear Colleagues,
>
>
>As a follow up from APNIC39 Conference which was held in Fukuoka in March
>2015, which discussed the next steps on preparation of implementation for
>the numbers proposal, summary of major discussion points are now
>available from the NRO website.
>
>
>https://www.nro.net/nro-and-internet-governance/iana-oversight/sla-develop
>ments
>
>I would like to highlight three key points from the meeting.
>
>  1. Separability of the IANA Numbering Services operator from ICANN
>     In course of developing SLA, it was consulted at the meeting whether
>separability is a critical and essential part of the SLA contract.
>     It was confirmed at the meeting that :
>
>      - The separability of services from ICANN is seen as one of the
>most important elements in ensuring the accountability of the IANA
>numbering function operator.
>      - As defined in the numbers community proposal, the possibility of
>changing the operator from ICANN in the future should remain open, which
>is expected to be reflected in the SLA.
>      - APNIC confirmed that the RIR would work on an SLA that is
>consistent with the numbers community proposal.
>
>  2. Transparency in providing feedback for the proposal
>      - If any entities have concerns about reflecting the seperability
>of the IANA Numbering Services operator or any other part of the numbers
>proposal in the SLA, this should be communicated to the community¹s
>attention in a
>        transparent manner for further consultation.
>
>  3. Future steps in the community consultation on implementation
>      - The plan is to carry the community consultation over the course
>of the coming months at the RIR meetings ­ this APNIC meeting is the
>first of these.
>      - During this period, all regions will have the chance to discuss
>issues relevant to the drafting of the SLA.
>      - After all the regional consultations are complete and all these
>processes have run their course, we should have a final agreed SLA as the
>outcome, which would then be part of the implementation of the numbers
>community proposal.
>
> From this stage, the RIRs will be responsible in preparing
>implementation of the IANA stewardship transition for the IANA Numbering
>Services and consulting with the community on its implementation as
>needed, based on the numbers community proposal.
>
>In preparation for implementation, RIRs will be consulting with the
>community at the coming RIR meetings as well as on the global
>ianaxfer at nro.net and each regional mailing lists as when appropriate.
>
>The CRISP Team have completed its role of developing the community based
>proposal for the IANA Numbering Services after its submission to the ICG
>but continues to be engaged in :
>      - Clarifying the intention of the proposal to the RIRs in preparing
>its implementation, in transparent manner with the community
>      - Share observation to the RIRs on community feedback received
>about implementation,  whether it is consistent with the proposal
>      - Follow up with the RIRs on the status and latest timeline of the
>preparation of implementation
>
>As the coming RIR meeting where the community will be consulted on the
>status of implementation, ARIN35 Meeting will be held in San Francisco
>with a CRISP Panel at 11:00 AM-12:00 PM (UTC-7) Monday, 13 April, 2015.
>Panelists will report on the Consolidated RIR IANA Stewardship Proposal
>(CRISP) Team's proposal, which was submitted to the IANA Stewardship
>Coordination Group, as well as talk about current status and the next
>steps.
>
>
>http://www.cvent.com/events/arin-35-public-policy-and-members-meeting/agen
>da-ddecdd5dcaeb4ae497d104bec676c023.aspx
>
>Online participation is possible for those who cannot attend the meeting
>physically, and I encourage the community members to join the community
>consultation at ARIN35.
>
>
>Best Regards,
>Izumi Okutani
>Chair, the CRISP Team
>
>--------------------------------------------------------------------------
>---------
>
>
>
>
>
>
>_______________________________________________
>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.