Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

FINAL DRAFT VERSION TO BE VOTED UPON BY THE ALAC

Central A central part of the IANA contract is to provide responsibility for the following by a single organisationfor a single organization to fulfill the following responsibilities:

  • Maintain unbiased, fair, and open registries for protocol numbers as requested in the RFCs as Request for Comments defined by the IETF.Internet Engineering Task Force;
  • Manage allocations the allocation of limited global ressources resources for the operation of the Internet ifself itself, based on verified actual needs only. This management includes Internet Protocol addresses and Autonoumus Autonomous System Numbers.;
  • Maintain the contract registry for Top Level Domains containing the contracts or MoU Memorandums of Understanding between each registry and ICANN for ccTLDs and gTLDs. Manage This responsibility also includes the management of the database for the delegation of data especially including glue , specifically including Glue Records, Name Servers and DNSSEC keys.;
  • Operate a free, open, unrestricted, and central WHOIS service (currently know as found at whois.iana.org) for all globally defined allocations and delegations (domain names, IP adressesaddresses, and ASNs). This services service should return the contractual details of each allocation or delegation, as well as the address addresses of the WHOIS services to obtain further details.;
  • Operate and maintain a registry for special purpose domain names like *.ARPA.

...

  • such as .arpa; and
  • Ensure that the Internet works as a neutral transportation platform and that all end-points

...

  • are able to access each other in a non-discriminating way.

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

In order to get acceptance obtain a mandate for such an organisationorganization, the activities responsibilities to be completed and managed should be as clearly defined, transparent, and documented as possible. Each contract, each delegation, allocation, or and definition needs to must be openly listed and easily accessable of the full sources, resulting in this actionaccessible.

For the end-user requesting any ressouceresource, the IANA website should contain a clear documentation , of how the ressource resources can be obtained. Because As IANA is usually not the institutiuon institution to make assign the ressouce resource allocation, it should point the end-user users to the party which that is responsible for processing the requestrequests. Nevertheless IANA should also provide a major abstract summary of each requesting process. A few lines are sufficient and should be provided by the sub-registry IANA is delegation torequest process.

For the sake of transparency, IANA should provide an open and easy to access interface to following easily accessible interface that follows the thin-WHOIS approach of whois.iana.org. Each interested user must be able to understand , why a ressouce resource is allocated to which a registry and where the information can be found using the next level of WHOIS downstream. IANA may provide a recursive, multi-lingual web-interface resolving the deeper levels of WHOIS and provide a an all-in-one access to the final end-user data the ressouce is that resources are assigned to. Of course this interface has to respect the local laws , where the data was is retrieved from.

The ALAC would also like to note the following four points.: 

  1. The current documentation of responsibilities makes it hard difficult for a typical end-user to find the canonical way official path from the IANA webpage down to the party (LIR, registrar, reseller, etc.) responsible to process his for processing a request. The current web page webpage of IANA needs to become much clearer on the hierarchy of allocations and ( sub)-assignments. This need change should also cover the ressouce resource allocation pages (include , including abstracts of the downstream registration process ) as well as and the retrieval of existing assignments (thin i.e. Thin Whois).
  2. Each registry operated by IANA is currently pure purely technical. Given the context of the registry in question, the current documentaion documentation is usually sufficient. Unfortunly Unfortunately the technical background differ differs in historical and operational aspects, wordings change over time, various word changes, and the requesting methods depend on given the current policy or RFC defining that defines the registyregistry. Without a solid knowledge in of this very sepecial special issue, the requested ressouce is relevantresource is irrelevant; as of now, the IANA pages are confusing up to distractinga point of being a distraction. This problem can't cannot be solved in a simple way, each of those registries are different and the applicable rules changes change over time. It's As a result, it is hard to provide a consistent presentation of such a varity variety of ressoucesresources. Nevertheless, but it should be triedundertaken.
  3. There should be a documented way (seen , viewable on the IANA webpage) , of how a an end-user can change the parties in the allocation hierarchy of his internet ressoucethe 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 his a reseller or registrar for his a domain name? What happens if an intermediate party chease ceases to exist? What happens of if an intermediate party want wants to change the uptree party (if the LIR changes the RIR, the reseller changes the registrar, the reseller changes the (com-)registry)registry, etc.? How is the end-user involved?
  4. The IANA web page should be easly easily accessible even for people with disablitiesdisabilities. Plain HTML, a good choice of CSS, and only some scripting for comfort features should be the way to go.implemented in this regard.

 

FIRST DRAFT SUBMITTED

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

...