[Iana-transition] Common Understanding & Clarifications

Sweeting, John john.sweeting at twcable.com
Tue Dec 30 10:32:19 EST 2014

Good morning,

Please find the current understanding, clarifications and direction that
the CRISP team is moving towards. If you have any input please consider
joining the NRO-IANAXFER mailing list. If you would like you can post it
here and it will be shared with the CRISP team by the ARIN CRISP team

CRISP Team member

>Summary of the current situation
>  What will be affected by NTIA's announcement
>   - NTIA will transfer stewardship on the IANA functions as defined in
>     the IANA contract
>   - AoC, between ICANN and the US goverment remains (not transfered)
>Current RIR legal arrangements with ICANN
>   - Global Policies: ASO MoU
>     Dispute resolution mechanism by the thirty party is defined in the
>     MoU, in case ICANN board is not accountable
>   - IANA function services provided to RIRs
>     No official legal document today: stewardship was considered to be
>     maintained based on IANA contract by the US government
>Proposed elements
>  a. ICANN continues to be the operator of IANA
>  b. Exchange SLA with ICANN on IANA number resources function
>  c. Review Committee (Name to be decided)
>     - NRO EC will conduct the review whether ICANN performs the IANA
>       functios on numbers according to SLA
>     - Review Commitee will provide advice to NRO EC as community
>       representives to increase credibility of NRO EC's review, that it
>       has taken in inputs from its communities
>     - Members of the review committee will be selected from each RIR
>       region, with simliar concept/scheme as CRISP Team
>       (It is not creating a new entity)
>Rationale for proposed elements
>  a. ICANN continues to be the operator of IANA
>    - RIRs are satisfied with the current services by ICANN
>    - Continuing with the current operator(i.e, ICANN) is desirable, if
>      we are satisfied, for stability of the function
>  b. Exchange SLA with ICANN on IANA number resources function
>    - To clarify relationships that that RIRs are delegating operation
>      of the IANA functions on number resources to ICANN
>      (also consistent rationale with IETF's proposal)
>    - Ensure our expected service level is maintained
>    - Allows RIRs to terminate the contract with the IANA function
>      service operator (i.e., ICANN) if ICANN doesn't sufficiently
>      address needs of RIRs and its communities
>  c. Review Committee
>     - Gives credibilities to the review of SLA to be conducted by the
>       NRO EC, on the number resources related IANA function services
>Other consideration we made
>  d. Global Policy Development process
>     - I was agreed, it is important to seperate IANA function on number
>       resources and global Policy Development Process (gPDP).
>     - We should focus our proposal on IANA function on number
>       resources, as this is what is affected by NTIA stewardship
>       transition. NTIA plays no role/involvement in gPDP.
>Rationale for not adopting some elements proposed on some RIR region(s)
>  e. Reasons for not supporting AoC
>  - The CRISP Team should focus to consider what would be missing as a
>    result of the NTIA IANA stewardship transition
>  - The US goverment keeps the AoC, so there is no need to replace this
>    part
>  - The part that will be missing is the contract related to the IANA
>    functions, which will be covered by SLA between ICANN and RIRs
>  - SLA is sufficient in ensuring to receive the IANA services and
>    accountabilities related this function
>  - Do not see why RIRs must be accountable to ICANN and define in AoC
>    RIRs should be accountantable to its communities, not ICANN
>  f. Reasons for change from MONC to Review Committee
>    - Some of the RIRs believe that MONC is complex and overly
>      burdensome, to oversee the performance of a contract where, over
>      the past 12 months, the IANA functions operator has performed only
>      eight transactions for the RIRs
>    - Have the scheme based on the existing framework, rather than
>      creating a new entity

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.

More information about the Iana-transition mailing list