[CRISP-TEAM] Fwd: [NRO-IANAXFER] Transition proposal for naming-related functions
nurani at netnod.se
Thu Apr 30 09:33:58 CEST 2015
I assume you have all seen this post by Alissa. Just posting here to make sure all CRISP members are aware of this.
> Begin forwarded message:
> From: Alissa Cooper <alissa at cooperw.in>
> Date: 29 april 2015 15:26:55 CEST
> To: ianaxfer at nro.net
> Subject: [NRO-IANAXFER] Transition proposal for naming-related functions
> Dear RIR community,
> You may be aware that the Cross Community Working Group developing the IANA stewardship transition proposal for naming-related functions has recently put its proposal out for public comment <https://www.icann.org/public-comments/cwg-stewardship-draft-proposal-2015-04-22-en <https://www.icann.org/public-comments/cwg-stewardship-draft-proposal-2015-04-22-en>>. We wanted to highlight a few aspects of the proposal that we believe would benefit from review and perhaps comment by your community:
> 1) Overlaps and interdependencies (Section I.D and Annex A)
> As in your community’s proposal, the CWG proposal contains information concerning overlaps and interdependencies with the other communities.
> 2) Post-Transition IANA (Section III)
> The CWG is proposing that a new separate legal entity, Post-Transition IANA (PTI), would be formed as an affiliate of ICANN. The existing IANA naming functions, administrative staff and related resources, processes, data and know-how would be legally transferred into PTI. Your community may want to consider a number of associated implications:
> * The likelihood that personnel and resources dedicated to the non-naming IANA functions would be moved to PTI. Your community may also want to consider its view on having all IANA functions provided by the same entity or allowing them to be separated.
> * Contracting. For existing or new contracts your community may have related to the IANA functions, there may be multiple options available, including maintaining existing contracts with ICANN and letting them subcontract their execution to PTI, assigning an existing contract to PTI, or re-contracting with PTI.
> * PTI Board. The composition of the PTI Board is not highly specified in the CWG proposal. There has been some discussion within the CWG about including representation for the RIRs and IETF on the PTI Board.
> * PTI ownership. If the PTI is formed as an affiliate of ICANN as the CWG proposes, as a legal entity it would be wholly owned by ICANN. Your community may want to consider its view of this whole ownership versus joint ownership involving all or multiple communities.
> 3) Liaisons to IANA Functions Review Team (Section III.A.i.d and Annex F)
> The CWG proposes that the performance of IANA be periodically reviewed post-transition and that the numbering and protocol parameter communities be offered the opportunity to appoint liaisons to the team performing reviews.
> 4) Customer Service Complaint Resolution Process (Annex I)
> The CWG proposes a complain resolution process for naming-related services, but which is open to the protocol parameters and numbering resources communities.
> If the ICG can be of further assistance in coordinating your review or understanding of the CWG proposal, please let us know.
> Alissa Cooper on behalf of the ICG
> ianaxfer mailing list
> ianaxfer at nro.net
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the CRISP