lukas
Uploaded by
7 SLIDES
205 VIEWS
70LIKES

Addressing the Operational Issues of ICANN/IANA for Non-Contracted ccTLDs

DESCRIPTION

This document discusses critical operational challenges faced by ICANN/IANA, particularly regarding their responsiveness to non-contracted country code top-level domains (ccTLDs). It highlights the lack of agreed operational procedures, the mixing of policy and operational roles, and the ambiguity in cost accountability. The reality of U.S. Government's continued engagement with ICANN raises concerns about the future distribution of IANA functions and the need for clear, well-defined procedures. It invites dialogue on how to address these concerns while ensuring no interference in national policy-making.

1 / 7

Download Presentation

Addressing the Operational Issues of ICANN/IANA for Non-Contracted ccTLDs

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. IANA – Plan BDr Willie Black25 March 2003

  2. The Problem • ICANN/IANA not responsive to requests from non-contracted ccTLDs • ICANN/IANA has not agreed operational procedures with those who need the service • ICANN/IANA mixing policy with operations • ICANN/IANA not costing operation clearly

  3. Current Contracts Situation • Doc – Verisign to propagate the root zone file • Doc – ICANN/IANA to maintain database • ccTLDs – IANA ???

  4. ccIANA ftom Shanghai • Technical • Schema, Authentication, Process • Legal • Very lightweight contract (call it an MoU!) • Authority to operator to put into root • Authority to remove temporarily in extremis • Payment of costs • Regionally distributed • Political • Acceptance by DoC • Support of regional governments

  5. Reality • USG has renewed with ICANN (6 months+) • USG probably not willing to distribute IANA function or have outside US • Possibility that USG will open a tender if ICANN/IANA fails to address community needs?

  6. Possible Criteria for IANA • No interference in national policy-making • No subjectivity judgments by IANA??? • Ring-fenced funding & Not-for-profit regime • Separate contracts ONLY for IANA part • Specification and Management of operating policies only by the TLD managers and IANA • Well-defined procedures and SLAs

  7. Questions • Agree criteria with changes? • Publish in communiqué? • Agree technical spec? Who? How? • Should we have dialogue with ICANN? How? • Dialogue with other parties? Who? How?

More Related