The document provides an update on the IANA stewardship transition process from the perspective of the Address Supporting Organization (ASO) and the CRISP (Consolidated RIR IANA Stewardship Proposal) team. It summarizes the CRISP team proposal, which was submitted to the IANA Transition Coordination Group in January 2015. It also discusses feedback received, next steps, and communication with other communities involved in the IANA stewardship transition.
1. Update on IANA Stewardship Transition
By
Mwendwa Kivuva
Date: 4th June 2015
2. 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
2
3. • CRISP Team Update
• Next Steps
• Communication with other operation
communities
• Q&A
AGENDA
3
5. 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
5
6. 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
6
8. • 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
8
10. • 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
10
11. 1. Separation of policy development and operational roles.
The IANA Numbering Services Operator will merely execute the
global policies adopted according to the global Policy Development
Process defined in the ASO MoU.
2. Description of services provided to RIRs. The IANA
Numbering Services Operator will maintain the IANA Number
Registries and provide IANA Numbering Services to the RIRs in
accordance with the specific processes and timelines described in
this section of the agreement.
IANA SLA Principles *
* Section III.A.3. of the proposal
11
12. 3. Obligation to issue reports on transparency and
accountability. The IANA Numbering Services Operator will commit to
certain obligations so as to perform the function as expected by the
Internet Number Community and will be obliged to periodically issue
reports illustrating its compliance with the Internet Number
Community's expectations.
4. Security, performance and audit requirements. The IANA
Numbering Services Operator will commit to specific security
standards, metric requirements, and audit requirements and will be
obliged to periodically issue reports illustrating its compliance with
them.
IANA SLA Principles
13. 5. Review of the IANA operation. The RIRs will perform reviews to
assess whether the IANA Numbering Services Operator complies with
all requirements described in the agreement whenever they deem
appropriate. The IANA Numbering Services Operator will be obliged to
facilitate this review.
6. Failure to perform. If the IANA Numbering Services Operator fails
to perform as agreed, there will be specific consequences. One of
these consequences may be termination of the agreement.
7. Term and termination of contract. RIRs will be able to
periodically review the agreement and evaluate whether they want to
renew the agreement. Either party may terminate the agreement with
reasonable prior notice.
IANA SLA Principles
14. 8. Continuity of operations. If, at the end of the term, the RIRs
decide to sign an agreement for provision of IANA Numbering Services
by a different party, the previous IANA Numbering Services Operator
will be obliged to ensure an orderly transition of the function while
maintaining continuity and security of operations.
9. Intellectual property rights and rights over data. The contract
will implement the RIR community expectations as described in section
III.A.2.
10. Dispute resolution. Disputes between the parties related to the
SLA will be resolved through arbitration
11. Cost-based Fee. The fee is based on costs incurred by the IANA
Numbering Services Operator in providing the IANA Numbering
Service.
IANA SLA Principles
15. • 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
15
16. • 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
16
17. • 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
17
18. • 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
18
19. • 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 that reached consensus
19
20. 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
21. • Analyse SLA for consistency with CRISP
proposal
• Liaise with the two other operational
communities for consistency in final output
by ICG
Next Steps
21
22. • CWG 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 CWG
22
23. • 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?
CWG - CRISP response
23
24. • 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
CWG - CRISP response
24
25. • 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
– 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
25
26. • Once an agreement has been reached on the
new oversight mechanism, the actual transition
process will begin.
When will transition occur?
26
SLA with ICANN
Review Committee will review ICANN’s adherence to the SLA, and report to NRO after a given period of time. At this point, RIRs are satisfied with the work ICANN has been doing.
1. RIRs can change the IANA operator if there are issues with the SLA. SLA is not the only condition for termination
4. All IPR related to numbering functions to be transferred to IETF trust.
ICANN publishes the IANA registries for anyone to use without charge, and it asserts no ownership or control of the information in the registries. No matter what additional structures are created, this basic rule must continue – ICANN Board Chairman Steve Crocker, on ianaplan@ietf.org on 5th May 2015
PTI – Origin, what it was to address, feedback on it ….