TapRoot
|
The TapRoot Committee
of the Top Level
Domain Association shall both maintain and publish publicly a
non-operational document referred to as the TLDA TapRoot, which shall
contain all of the requisite operational data to provide DNS resolution
for all known, operational Top Level Domains that exist in the Internet
Name Space. To wit: The Inclusive Name Space.
The TapRoot Committee shall take its direction from, and serve at the
pleasure of, the Board of Directors, and report its findings,
recommendations, and observations regarding the functions and operations
of Top-Level Domains, their DNS Name Servers, and other applicable contact
information for those Top-Level Domains to the Board, as well as input it
may receive from the Compliance/Endorsements
Committee. The TapRoot
Committee will attempt to the best of its ability to define accurately the
instances of TLDs being carried by various DNS providers and which
instances of those TLDs are being carried in the event of duplicate
strings (with the assistance of the Compliance/Endorsements Committee),
and whether the instances being carried by those DNS service providers are
the TLDA recommended instances or not.
The TapRoot Committee, in conjunction with the Compliance/Endorsements
Committee will assist with developing a reporting system as to the level
of Compliance for each identified DNS service provider regarding their
adherence to the TLDA recommended published TLDs, as well as the level of
perceived inclusiveness relating to how complete a particular DNS service
providers portfolio of TLDs from the Inclusive Name Space is.
The format of the published TapRoot shall be in accordance with the
following example:
; Administered by: [Key operational entity tag/Handle]
; Creation Date: 01 January 1962;
; Zone contact: BillGates@MSN.com [RP in the zonefile]
;
; Delegation/Contact Data:
; Company/Individual name
; 1122 East boogie wooogie avenue
; 3nd Floor
; New York, NY 10003
; POC: Mary Contrary
; Phone: +1.888.555.1212
; fax: +1.888.555.1234
; Email: info@noplace.comma [Administrative/managerial contacts]
; Email: mcontrary@noplace.tweedledee
; URL: http://www.registrysite.tld
;
;
;
;
tld. IN NS ns.TLD.Server.
tld. IN NS ns1.TLD.Server
;
;
ns.TLD.Server. IN A 1.2.3.4
ns1.TLD.Server IN A 2.3.4.5
There shall be no SOA (Start of Authority) in the TapRoot since it is not
intended to be an operational file.
|
Compliance
|
The Compliance/Endorsements
Committee of the TLDA shall study, investigate, and record
all claims for Top Level Domains it can discover, both operational and
otherwise, where there exists the possibility or there is the actual
occurrence of duplicate TLD strings in the Inclusive Name Space.
The Compliance/Endorsements committee shall, to the best of its ability
and in the interest of the TLDA, determine which instances of any claims
to Top-level Domains in the Inclusive Name Space should be marked or
otherwise designated as the recommended version of a colliding duplicate
TLD string for the purposes of being carried by all of the various and
publicly available DNS service providers. Such recommendations will be
provided to the Records and TapRoot Committees for archives and
publishing, subject to approval of these findings by the Board of
Directors, and the TapRoot committee will so designate the recommended TLD
strings as per the findings and recommendations of the
Compliance/Endorsements Committee.
The Compliance/Endorsements Committee, in conjunction with the TapRoot
Committee will also issue reports of the level of compliance for each
identified DNS service provider including the level of operational
viability and compliance of individual TLDs regarding their adherence to
the TLDA recommended published TLDs, as well as the level of perceived
inclusiveness relating to how complete a particular DNS service providers
repertoire of TLDs from the Inclusive Name Space is. For DNS service
providers, such as root-level service providers, they will be rated on a
percentage basis in a dual rating of %#1 / %#2, where the first percentage
number equals the level of compliance with TLD published recommendations
and the second percentage number equals the level of inclusiveness with
the total number of TLDs carried by the service provider compared to the
total number of non-colliding instances of TLD strings in the TapRoot. For
the individual TLDs the rating shall be on a level basis where there are
multiple levels of compliance and operational viability (Level 1, Level 2,
etc.) according to the published recommendations of the TLDA and without
regard to whether such TLDs are in collision with other TLDs by the same
String.
|
|