Nom Domain Charter
A. Purpose
1. This Top-Level Domain is intended for the registration of
complete names of natural persons; for example,
John.Jacob.Hinkelmeijer.Smith.nom. Performance or Literary
pseudonyms (such as Madonna, or the Symbol formerly called
Prince) do not qualify.
2. The same or similar name shall not be registered by the same
organization in any other zone of the DNS (such as under a
country TLD), unless an exception for good cause is granted
under the registration appeal process (described below).
3. The registration of a name or combination of names does not
convey any TradeMark or ServiceMark status.
4. Each zone within this Top-Level Domain shall be open to
registration of additional zone delegations. The designated
Nom registry may maintain such zones, or may designate
subordinate registries that provide the best combination of
costs and services and conform to the requirements for
registry operation (described below).
5. The designated Nom registry management shall require that
these same terms be carried forward by its registrants.
B. Registration Process
1. Registration of leaf domains is open to all qualifying
applicants on a non-discriminatory, fair-use, first-come,
first-served basis, in compliance with the most recent revision
of the Generic Top Level Domain Memorandum of Understanding
(gTLD-MoU).
2. Each qualifying leaf domain must have (or share) 2 or more
topologically dispersed secondary zone servers, in addition to
the primary master.
3. In any dispute as to the registration of a particular name, the
registrar shall have no role or responsibility, other than to
provide the contact information for all parties, and abide by
the results of the appeals process. Appeals are taken by
following the current process designated by the gTLD-MoU -- the
Administrative Domain Name Challenge Panels.
4. Whenever it is determined, on its own initiative or acting in
response to a petition from any person, that an error in
leaf domain registration has occurred -- including (but not
limited to) ineligibility, change in qualification status, or
failure of the SOA contact to respond promptly to queries --
the designated registry manager shall revoke or transfer the
registration:
a) no sooner than 21 days after sending notification to the SOA
specified contact;
b) with appeal of administrative and factual issues to the
gTLD-MoU established Council of Registrars (CORE);
c) and final appeal of process issues to the gTLD-MoU
established Policy Oversight Committee (POC).
C. Registry Operation
1. The repository for the primary master zone server (the
registry) shall be designated by the Council of Registrars
(CORE), in compliance with the most recent revision of their
Memorandum of Understanding (CORE-MoU), and with the
concurrance of the Policy Oversight Committee (POC).
2. The registry must have (or share) 5 or more topologically
dispersed secondary zone servers, in addition to the primary
master.
3. The registry may seek reimbursement for each registration on an
annualized non-profit cost-recovery basis, and in compliance
with the CORE-MoU.
4. Whenever it is determined, on its own initiative or acting in
response to a petition from any person, that a registry has
failed to conform to any registry requirements or that another
registry could provide a significantly better combination of
costs and services, the Council of Registrars (CORE) may
designate a change to another registry:
a) no sooner than 49 days after sending notification to the SOA
specified contact;
b) with appeal of administrative and factual issues to the
Policy Oversight Committee (POC);
c) and final appeal of process issues to the authority
designated by the Internet Architecture Board (IAB) --
currently the Internet Assigned Numbers Authority (IANA) --
or its successor.
WSimpson@UMich.edu
Key fingerprint = 17 40 5E 67 15 6F 31 26 DD 0D B9 9B 6A 15 2C 32