Page History

...

(*) Comments submitted after the posted Close Date/Time are not guaranteed to be considered in any final summary, analysis, reporting, or decision-making that takes place once this period lapses. 

FINAL VERSION TO BE SUBMITTED IF RATIFIED

Please click here to download the PDF below.

FINAL DRAFT VERSION TO BE VOTED UPON BY THE ALAC

...

Based on these responsibilities, the central administration of global resources must to be operated by a non-political, non-commercial, and non-policy-making single-purpose entity. As such, it is best that IANA be charged with this task.

In order to obtain a mandate for such an organization, the responsibilities to be completed and managed by IANA should be as clearly defined, transparent, and documented as possible. Each contract, delegation, allocation, and definition must be openly listed and easily accessible.

...

1. The current documentation of responsibilities makes it difficult for a typical end-user to find the official path from the IANA webpage to the party (LIR, registrar, reseller, etc.) responsible for processing a request. The current webpage of IANA needs to become much clearer on the hierarchy of allocations and sub-assignments. This change should also cover the resource allocation pages, including abstracts of the downstream registration process and the retrieval of existing assignments (i.e. Thin Whois).
2. Each registry operated by IANA is currently purely technical. Given the context of the registry in question, the current documentation is usually sufficient. Unfortunately the technical background differs in historical and operational aspects, various word changes, and the requesting methods given the current policy or RFC that defines the registry. Without a solid knowledge of this very special issue, the requested resource is irrelevant; as of now, the IANA pages are confusing up to a point of being a distraction. This problem cannot be solved in a simple way, each of those registries are different and the applicable rules change over time. As a result, it is hard to provide a consistent presentation of such a variety of resources. Nevertheless, it should be undertaken.
3. There should be a documented way, viewable on the IANA webpage, of how an end-user can change the parties in the allocation hierarchy of the end-users Internet resource. How else can an end-user know how to change the LIR or RIR of his address space (i.e. after a relocation to a different country)? How else can an end-user change a reseller or registrar for a domain name? What happens if an intermediate party ceases to exist? What happens if an intermediate party wants to change the uptree party if the LIR changes the RIR, the reseller changes the registrar, the reseller changes the registry, etc.? How is the end-user involved?
4. The IANA web page should be easily accessible for people with disabilities. Plain HTML, a good choice of CSS, and only some scripting for comfort features should be implemented in this regard.

...

FIRST DRAFT SUBMITTED

Central part of the IANA contract is to provide responsibility for the following by a single organization:

...