The document discusses the IANA stewardship transition and the CRISP Team proposal from the Internet numbers community. It provides an update on the proposal development process, which included input from the global Internet community. It also outlines next steps, such as analyzing the proposed IANA service level agreement and coordinating with the other operational communities. The document addresses questions and feedback from the ICANN, IETF and CCWG groups regarding consistency between the proposals.

1. Update on IANA
Stewardship Transition – AFRINIC22
AFRINIC team members:
Mwendwa Kivuva – University of Nairobi
Ernest Byaruhanga (Appointed RIR staff)
Janvier Ngnoulaye* – University of Yaounde
* Janvier Ngoulaye replaced Alan
Barrett in April 2015
1AFRINIC 22, 1 June - 5 June 2015

2.  CRISP Team Update
 Next Steps
 Communication with other operation communities
 Q&A
AGENDA
2AFRINIC 22, 1 June - 5 June 2015

3. RIR Communities
3AFRINIC 22, 1 June - 5 June 2015

4. Required Principles of the new
proposals
 Support and enhance the multistakeholder model
 Maintain the security, stability, and resiliency of the
Internet DNS
 Meet the needs and expectations of the global
customers and partners of the IANA services
 Maintain the openness of the Internet
4AFRINIC 22, 1 June - 5 June 2015

5. Timelines – v9 April 2015
Activity Date
STEP 0 Request for communities to produce proposals 8 Sep 2014 – 20 Oct 2014
STEP 1 Communities develop proposals 8 Sep 2014 – 15 Jan 2015
STEP 2 ICG develops Draft Response 15 Jan 2015 – 13 Mar 2015
STEP 3 Communities Review of Draft response 13 Mar 2015 – 15 Mar 2015
STEP 4 Testing – demonstrate system can run as proposed 13 Mar 2015 – July 2015
STEP 5 ICG Develops final response 15 Mar 2015 – 19 Jun 2015
STEP 6 Final Response Review 19 Jun 2015 – 17 July 2015
STEP 7 Proposal Delivery 17 July 2015 – 31 July 2015
STEP 8 NTIA Approval 31 July 2015 – 30 Sep 2015
5AFRINIC 22, 1 June - 5 June 2015

6. Proposal Development Process
6AFRINIC 22, 1 June - 5 June 2015

7.  June 2014 - IANA Stewardship Transition Coordination
Group (ICG) issues Request for Proposals to three
IANA “affected communities”
 Q4 2014 - Consolidated RIR IANA Stewardship
Proposal Team (CRISP Team) established to prepare
an Internet numbers community proposal. Global
discussion platform established: ianaxfer@nro.net
 January 2015 - Internet numbers community IANA
stewardship proposal submitted to the ICG
The Process
7AFRINIC 22, 1 June - 5 June 2015

8. CRISP Team Proposal
8AFRINIC 22, 1 June - 5 June 2015

9.  IANA function stability and reliability: ICANN to continue as the IANA Numbering
Services Operator, orderly transition to another operator should such need arise
 Replace the role of the NTIA with the RIRs (as representatives of RIR
communities): RIRs to establish a service level agreement with the IANA
Numbering Services Operator
 Establishment of a Review Committee: To review the performance of IANA
Numbering Services and advise the RIRs
 Clarify IPR-related issues: Intellectual property rights (IPR) related to the
provision of the IANA services stay with the community
Components of the Proposal
9AFRINIC 22, 1 June - 5 June 2015

10. 1. Separation of policy development and operational roles
2. Description of services provided to RIRs
3. Obligation to issue reports on transparency and accountability
4. Security, performance and audit requirements
5. Review of the IANA operation
6. Failure to perform
7. Term and termination of contract
8. Continuity of operations
9. Intellectual property rights and rights over data
10. Dispute resolution
11. Cost-based Fee
IANA SLA Principles *
* Section III.A.3. of the proposal
10AFRINIC 22, 1 June - 5 June 2015

11.  Advise RIRs on review of the service level described in SLA
 Provide feedback from the community’s perspective
 Community representatives from each RIR service region
 Equal representation from each RIR service region
 The process of selecting representatives will be driven by the RIRs based on
open and bottom-up principles
Review Committee
11AFRINIC 22, 1 June - 5 June 2015

12.  Each version of the proposal was shared on:
 The global <ianaxfer@nro.net> mailing list (open to anyone)
 NRO CRISP web page
 The CRISP Team members forwarded each version to each RIR community’s mailing lists
 Feedback from the community was confirmed and discussed at every CRISP Team
teleconference
 The global <ianaxfer@nro.net> mailing list
 Feedback per RIR region (conveyed by the CRISP Team members)
 CRISP Team consideration for feedback shared on the <ianaxfer@nro.net> mailing
list/spreadsheet of issues list so that:
 Directions were clear to the community
 Further comments/clarification questions could be made if needed
Community Engagement by the CRISP Team
12AFRINIC 22, 1 June - 5 June 2015

13.  Some data/facts – Before proposal submission:
 377 posts
 53 unique posters
 Public archives of <ianaxfer@nro.net> mailing list available
 Support expressed for the proposal
 One poster requested adding more details on some of the proposal components,
but the suggestion failed to receive support from other posters
 Two comments to global icg-forum expressing concerns
• No objections for the proposal components
Feedback Received
13AFRINIC 22, 1 June - 5 June 2015

14.  During the ICANN 52 Public Forum, ICANN Chair Steve
Crocker said that, in regards to the ICG proposals from the
numbers and protocol parameters communities, the ICANN
Board felt there was “nothing fundamental in them that we
have a problem with, full stop.”
http://blog.apnic.net/2015/02/20/event-wrap-icann-52/
ICANN Public Feedback
14AFRINIC 22, 1 June - 5 June 2015

15.  Clarify about IPR
 High-level principles of the IANA Service Level Agreement
 Clarify that RIRs will consult their respective communities during drafting of the SLA
 High-level principles in review committee selection process
 Need for clarification of IANA intellectual property rights
Input not incorporated
 Specify a particular jurisdiction/dispute resolution mechanism
 Specify a particular selection process for the Review Committee
 Incorporate SLA text as a part of the proposal
CRISP Proposal submitted to ICG on Jan 15th, 2015
Input that reached consensus
15AFRINIC 22, 1 June - 5 June 2015

16.  Analyse SLA for consistency with CRISP proposal
 Liase with the two other operational communities for
consistency in final output by ICG
Next Steps
16AFRINIC 22, 1 June - 5 June 2015

17.  CCWG proposed a Post-Transition IANA (PTI) - separate legal
"wholly owned subsidiary" of ICANN. For the IANA naming
services, the creation of PTI ensures both functional and legal
separation within the ICANN organization
 Contract between PTI and ICANN that would give PTI the rights
and obligations as the IANA Functions Operator.
 The IANA Functions would continue to reside within ICANN,
subject to accountability mechanisms already in existence
Communication with CCWG
AFRINIC 22, 1 June - 5 June 2015 17

18.  It is “essential each operational community be free to
make independent arrangement with an IFO including
ability to chose the IFO itself”
 PTI – CRISP is analyzing whether to exchange SLA
with ICANN or PTI
 PTI Board – Keep roles and structures minimal. Should
RIRs have representation?
CCWG - CRISP response
18AFRINIC 22, 1 June - 5 June 2015

19.  Budget for IFO: CRISP proposal had a fixed cost paid
annually to IFO
 Customer Standing Committee (CSC): Have a mechanism
for communication exchange with NRO-Review Committee
(NRO-RC). No role for RIRs in CSC
 IPR: More dialogue needed between IETF, CCWG, and
CRISP
 Multi-stakeholder IANA Function Review team: Restrict to
names function only
CCWG - CRISP response
AFRINIC 22, 1 June - 5 June 2015 19

20.  Intellectual property rights on IANA trademark and
IANA.org: Clarity needed on these issues in case of a
change of IANA operator. IETF has no objection to
this.
 Section III.A.3 last paragraph: “The transfer of the IANA trademark and
IANA.ORG domain to the IETF Trust will require additional coordination with the other
affected communities of the IANA Services, namely, protocol parameters and names. It
is the preference of the Internet Numbers Community that all relevant parties agree to
these expectations as part of the transition.”
Communication with IETF
20AFRINIC 22, 1 June - 5 June 2015

21.  Crisp Team Url: https://www.nro.net/crisp-team
 Proposal Url: http://www.nro.net/crisp-final-proposal
 FAQ: http://www.nro.net/crisp-proposal-faq
 RIR SLA: https://www.nro.net/wp-content/uploads/Numbers-SLA-
1.0.pdf
 CCWG Proposal: https://www.icann.org/public-comments/cwg-
stewardship-draft-proposal-2015-04-22-en
 IETF Proposal: http://ietf.org/iana-transition.html
More Information
21AFRINIC 22, 1 June - 5 June 2015

22.  Once an agreement has been reached on the new
oversight mechanism, the actual transition process
will begin.
When will transition occur?
22AFRINIC 22, 1 June - 5 June 2015

23. End
23AFRINIC 22, 1 June - 5 June 2015