A federal name space has been established for the federal government
agencies. For example, the subdomain for the Federal Reserve Bank of
Minneapolis is MNPL.FRB.FED.US. Other examples are listed below.

The "DNI" branch was created directly under the top-level US. This
is to be used for organizations that span state, regional, and other
organizational boundaries; are national in scope, and have
distributed facilities. An example would be:

The MetaCenter Network will enable applications and services like
file systems and archival storage to be operated in a distributed
fashion; thus, allowing the resources at the four centers to appear
integrated and "seamless" to users of the centers.

2.7 General Independent Entities

This name space was created for organizations that don't really fit
anywhere else, such as state-wide associations, clubs, and "domain
parks". Think of this as the miscellaneous category.

The examples are state-wide clubs. For example, the Garden Club of
Arizona, might want to be "GARDEN.GEN.AZ.US". Such a club has
membership from all over the state and is not associated with any one
city (or locality). Another example is "domain parks" that have been
established up-to-now as entities in ORG. For example, there is
"LONESTAR.ORG", which is a kind of computer club in Texas that has
lots of dial-in computers registered. In the US Domain such an
entity might have a name like "LONESTAR.GEN.TX.US".

The organizations registered in GEN may typically be non-profit
entities. These organizations don't fit in a <locality> and are not
a school, library, or state agency. Ordinary businesses are not
registered in GEN.

Some suggest that these kinds of organizations are just like all the
other things and ought to be registered under some <locality>. This
may be true, but sometimes one just can't find any way to convince
the applicant that it is the right thing to do. One can argue that
any organization has to have a headquarters, or an office, or
something about it that is in a fixed place, and thus the
organization could be registered in that place.

Some suggest that no token is needed, these entities could be
directly under the <state-code>. The problem with not having a
token, is that you can't delegate the responsibility for registering
these entities to someone separate from whoever is responsible for
the <state-code>. You want to be able to delegate for both name-
uniqueness reasons, and operational management reasons. Having a
token there makes both easy.

Cooper & Postel [Page 16]

RFC 1480 The US Domain June 1993
General Independent Entities:
-----------------------------

CAL-Comp-Club.GEN.CA.US <==== The Computer Club of California

2.8 Examples of Names

For small entities like individuals or small businesses, there is
usually no problem with selecting locality based names.

For example: Zuckys.Santa-Monica.CA.US

For large entities like large corporations with multiple
facilities in several cities or states this often seems like an
unreasonable constraint (especially when compared with the
alternative of registering directly in the COM domain). However,
a company does have a headquarters office in a particular locality
and so could register with that name. Example: IBM.Armonk.NY.US

PRIVATE (business or individual)
================================

Camp-Curry.Yosemite.CA.US <==== a business
IBM.Armonk.NY.US <==== a business
Dogwood.atl.GA.US <==== a business
Geo-Petrellis.Culver-City.CA.US <==== a restaurant
Zuckys.Santa-Monica.CA.US <==== a restaurant
Joe-Josts.Long-Beach.CA.US <==== a bar
Holodek.Santa-Cruz.CA.US <==== a personal computer

GARDEN.GEN.AZ.US <==== a garden club of Arizona
CITY | CI | COUNTY | CO (locality)
==================================

Parks.CI.Culver-City.CA.US <==== a city department
Fire-Dept.CI.Los-Angeles.CA.US <==== a city department
Fire-Dept.CO.Los-Angeles.CA.US <==== a county department
Planning.CO.Fulton.GA.US. <==== a county department
Main.Library.CI.Los-Angeles.CA.US <==== a city department
MDR.Library.CO.Los-Angeles.CA.US <==== a county department
TOWNSHIP | PARISH (locality)
============================

Hamilton.High.LA-Unified.K12.CA.US <==== a public school
Sherman-Oaks.Elem.LA-Unified.K12.CA.US <==== a public K12 school
John-Muir.Middle.Santa-Monica.K12.CA.US <==== a public K12 school
Culver-High.CCSD.K12.CA.US <==== a public K12 school

St-Monica.High.Santa-Monica.CA.US <==== a private school
Crossroads-School.Santa-Monica.CA.US <==== a private school
Mary-Ellens.Montessori-School.LA.CA.US <==== a private school
Progress-Learning-Center.PVT.K12.CA.US <==== a private school

SMCC.Santa-Monica.CC.CA.US <==== a public community college
Trade-Tech.Los-Angeles.CC.CA.US <==== a public community college
Valley.Los-Angeles.CC.CA.US <==== a public community college

Brick-and-Basket-Institute.TEC.CA.US <== a technical college
When appropriate, subdomains are delegated and partioned in
various categories, such as:

There are two types of registrations (1) Delegation, where a branch
of the US Domain is delegated to an organization running name servers
to support that branch; or (2) Direct Registration, in which the
information is put directly into the main database.

In Direct Registration there are two cases: (a) an IP-host (with an
IP address), and (b) non-IP host (for example, a UUCP host). Any
particular registration will involve any one of these three
situations.

3.1 Requirements

Anyone requesting to register a host in the US Domain is sent a copy
of the "Instructions for the US Domain Template", and must fill out a
US Domain template.

The US Domain template, is similar to the InterNIC Domain template,
but it is not the same. To request a copy of the US Domain template,
send a message to the US Domain registrar (us-domain@isi.edu).

If you are registering a name in a delegated zone, please register
with the contact for that zone. You can FTP the file "in-notes/us-
domain-delegated.txt" from venera.isi.edu, via anonymous FTP. This
information is also available via email from RFC-INFO@ISI.EDU
(include as the only text in the message
"Help: us_domain_delegated_domains").

The key people must have electronic mailboxes (that work). Please
provide all the information indicated in the "Administrator" and
"Technical Contact" slots.

The administrator will be the point of contact for any administrative
and policy questions about the domain. The administrator is usually
the person who manages the organization being registered.

The technical contact can also be administrator, or the systems
person, or someone who is familiar with the technical details of the
Internet. The technical contact should have a valid working email
address. This is necessary in case something goes wrong.

It is important that your "Return-Path" and "From" field indicate an
Internet-style address. UUCP-style addresses such as "host1!user"
will not work. This is fine within the UUCP world, but not the
Internet. If you want people on the Internet to be able to send mail
to you, your return path needs to be an Internet-style address such
as: host1!user@Internet.gateway.host or user@Internet.gateway.host.

Cooper & Postel [Page 20]

RFC 1480 The US Domain June 1993
It is also possible to register through one of the Internet service
providers that have established working relationships with the US
Domain Administrator.

If everything checks out, the turn around time for registering a host
is usually a few days. The name servers are updated anywhere from 12
to 24 hours later.

There are two ways to be registered in the US Domain, directly, or by
delegation.

3.2 Direct Entries

Direct entry in the database of the US Domain appeals most to
individuals and small companies. You may fill out the application
and send it directly to the US Domain Administrator. If you are in
an area where the zone is delegated to someone else your request will
be forwarded to the zone administrator for your registration. Or,
you may send the form directly to the manager of a delegated zone
(see Section 3.1).

3.2.1 IP-Hosts

These are hosts with IP addresses which correspond to "A" records in
the DNS database.

3.2.2 Non-IP Hosts

Many applicants have hosts in the UUCP world. Some are one hop away,
some two and three hops away from their "Internet Forwarder", this is
acceptable. What is important is getting an Internet host to be your
forwarder. If you do not already have an Internet forwarder, there
are several businesses that provide this service for a fee, such as
UUNET.UU.NET (postmaster@uunet.uu.net), PSI (postmaster@UU2.PSI.COM)
and CERFNET (help@cerf.net). Sometimes local colleges in your area
are already on the Internet and may be willing to act as an Internet
Forwarder. You would need to work this out with the systems
administrator as we cannot make these arrangements for you.

Although we work with UUCP service providers, the Internet US Domain
registration is not affiliated with the registration of UUCP Map
entries. The UUCP map entry does not provide us with sufficient
information. If you do not have a copy of the US Domain
questionnaire template, please send a message to: us-domain@isi.edu
and request one. See Appendix-II.
Cooper & Postel [Page 21]

RFC 1480 The US Domain June 1993
The example below is not an appropriate registration for the US Domain.

If you are registering your host as a central site for a USENET group
where other UUCP sites will feed from you, that's fine. These UUCP
sites do not need to register. If however, the other sites become a
subdomain of your hostname, then we will need to register them
individually or add a wildcard record. (See Section 4.4. Wildcards).

To use US Domain names for non-IP hosts, there must be a forwarder
host that is an IP host. There must be an administrative agreement
and a technical procedure for relaying mail between the non-IP host
and the forwarder host.

Case 1:
-------

Your host is not an IP host but does talk directly with a host that
is an IP host.
+-----------------+
+----------+ +---------+ | |
|your-host |---UUCP-----|forwarder|----IP/TCP--| INTERNET |
+----------+ +---------+ | |
+-----------------+
"Forwarder" must be an IP host on the Internet.

You must ask "forwarder" if they are willing to be the Internet
forwarder for "your-host".

In the US Domain of the DNS data base there must be an entry like
this:
"your-host" MX 10 "forwarder"

Cooper & Postel [Page 22]

RFC 1480 The US Domain June 1993
This must be entered by the US Domain Administrator.

In the "forwarder" routing tables there must be information about
"your-host" with a rule like: If I see mail for "your-host" I will
send it via uucp by calling phone number "123-4567".

You must ask "forwarder" if they are willing to be the Internet
Forwarder for "Your-Host". You must ask "path-host" to relay your
mail.

In the US Domain of the DNS Database there must be an entry like this:

"your-host" MX 10 "forwarder"

This must be entered by the US Domain Administrator.

In the "forwarder" routing tables there must be information about
"your-host" with a rule like: If I see mail for "your-host" I will
send it via UUCP to "path-host" by calling phone number "123-4567".
and "path-host" must also know how to relay the mail to "your-host".

Note: It is assumed that "path-host" is already MXed to "forwarder".
It is not appropriate to ask to MX "your-host" to "path-host" (this
is sometimes called double MXing). The host on the right hand side
of an MX entry must be a host on the Internet with an IP address
(e.g., 128.9.2.32).
Cooper & Postel [Page 23]

RFC 1480 The US Domain June 1993
3.3 Delegated Subdomains

Many branches of the US Domain are delegated. There must be a
knowledgeable and competent technical contact, familiar with the
Internet DNS. This requirement is easily satisified if the technical
contact already runs some other name servers.

Examples of delegations are K12.TX.US for the Kindergarten through
12th Grade public schools in Texas, the locality "berkeley.ca.us", or
the LIB.MN.US branch for the libraries in Minnesota.

The administrator of the US Domain is responsible for the assignment
of all the DNS names that end with ".US". Of course, one person or
even one group can't handle all this in the long run so portions of
the name space are delegated to others.

The major concern in selecting a designated manager for a domain is
that it be able to carry out the necessary responsibilities, and have
the ability to do an equitable, just, honest, and competent job.

The key requirement is that for each domain there be a designated
manager for supervising that domain's name space.

These designated authorities are trustees for the delegated domain,
and have a duty to serve the community.

The designated manager is the trustee of the domain for the domain
itself and the global Internet community.

Concerns about "rights" and "ownership" of domains are inappropriate.
It is appropriate to be concerned about "responsibilities" and
"service" to the community.

The designated manager must be equitable to all groups in the domain
that request domain names.

This means that the same rules are applied to all requests. All
requests must be processed in a nondiscriminatory fashion, and
academic and commercial (and other) users are treated on an equal
basis. No bias shall be shown regarding requests that may come from
customers of some other business related to the manager -- e.g., no
preferential service for customers of a particular data network
provider. There can be no requirement that a particular mail system
(or other application), protocol, or product be used.

There are no requirements on subdomains beyond the requirements on
higher-level domains themselves. That is, the requirements are
applied recursively. In particular, all subdomains shall be allowed

Cooper & Postel [Page 24]

RFC 1480 The US Domain June 1993
to operate their own domain name servers, providing in them whatever
information the subdomain manager sees fit (as long as it is true and
correct).

Significantly interested parties in the domain should agree that the
designated manager is the appropriate party.

The US Domain Administrator tries to have any contending parties
reach agreement among themselves, and generally takes no action to
change things unless all the contending parties agree; only in cases
where the designated manager has substantially neglected their
responsibilities would the US Domain Administrator step in.

The designated manager must do a satisfactory job of operating the
DNS service for the domain.

That is, the actual management of the assigning of domain names,
delegating subdomains and operating name servers must be done with
technical competence. This includes keeping the US Domain
Administrator or other higher-level domain managers advised of the
status of the domain, responding to requests in a timely manner, and
operating the database with accuracy, robustness, and resilience.

There must be a primary and a secondary name server that have IP
connectivity to the Internet and can be easily checked for
operational status and database accuracy by the US Domain
Administrator.

One of the aspects of having two name servers for each domain (or
zone), is for robustness. One concern under this heading is that the
name service not go out entirely if there is a local power failure
(earthquake, tornado, or other disaster).

Name Servers should be in distinctly separate physical locations. It
is appropriate to have more than two name servers, but there must be
at least two.

For any transfer of the designated manager trusteeship from one
organization to another, the higher-level domain manager must receive
communications from both the old organization and the new
organization that assures the US Domain Administrator that the
transfer in mutually agreed, and that the new organization
understands its responsibilities.

It is also very helpful for the US Domain Administrator to receive
communications from other parties that may be concerned or affected
by the transfer.
Cooper & Postel [Page 25]

RFC 1480 The US Domain June 1993
Delegation of cities, companies within cities, schools (K12),
community colleges (CC), libraries (LIB), state government (STATE),
and federal government agencies (FED), etc., is acceptable and
practical.

For a delegated portion of the name space, for example a city, no
alterations can be made to that name, no abbreviations added, etc.
unless applied for.

Sometimes there may be two people running name servers in the same
city because different portions of the name space has been delegated
to them. For example, someone may be delegated the <city>.<state>.US
name space, and someone else from a state government agency may have
the .STATE.<state>.US, portion. For example, Fred may run the name
servers for Sacramento.CA.US and Joe may run the name servers for
STATE.CA.US in Sacramento.

If a company would like to have wildcard records added, or run their
own name servers in a city that we have delegated name space to, this
is acceptable.

Delegation of the whole State name space is not yet implemented. The
delegated part of the name space is in the form of:

When a subdomain is delegated, the following requirements must be
met:

1) There must be a knowledgeable and competent technical contact,
familiar with the Internet DNS. This requirement is easily
satisified if the technical contact already runs some other
name servers.

Cooper & Postel [Page 26]

RFC 1480 The US Domain June 1993
2) Organizations requesting delegations must provide at least two
independent (robust and reliable) DNS name servers in
physically separate locations on the Internet.

3) The subdomain must accept all applicants on an equal basis.

4) The subdomain must provide timely processing of requests. To
do this, it is helpful to have several individuals
knowledgeable about the procedures so that the operations are
not delayed due to one persons unavailability (for example, by
being on vacation).

5) The subdomain manager must tell the US Domain Administrator
when there are changes in the name servers that should be
reflected in the US Domain zone files, or changes in the
contact information.

K12 Administrators

In the long term, registering schools will be a big job. So you
need to have in mind delegating parts of the work to various
school districts. If you can delegate every school district in
the state then you are finished, except for checking that they are
all operating correctly. However, initially you will have quite a
bit to do with educating people, helping them choose names and
getting name servers arranged. You are responsible for seeing
that the naming of schools follow the guidelines suggested in this
memo.

All K12 Administrators will initially be responsible for managing
the "pseudo district" PVT for private schools. Private schools
have the option of registering as <school-name>.PVT.K12.<state>.US
or as a business under the city based names.

Locality Administrators

If you have been delegated a locality subdomain, you will be
responsible for registering not only businesses directly under the
locality, but city and county agencies under the "CI" and "CO"
branches. When appropriate these branches should be delegated.

If you want, you may spell out "CITY" instead of "CI" or "COUNTY"
instead of "CO", but you must be consistent and use only one or
the other in a given locality. The whole city government should
be under one branch.
Cooper & Postel [Page 27]

RFC 1480 The US Domain June 1993
WHOIS Database

Only the second and third level delegated name spaces will be
entered in the WHOIS database. For example, K12.CA.US would have
an entry in WHOIS. Anything under K12.CA.US will not be listed.
The US Domain Administrator will send the information that you
supplied on your US Domain template to the InterNIC. It is the
hope that in the future, each delegated subdomain will provide
their own WHOIS directory database for their branch.

3.3.2 Delegation Procedures

The procedure that is followed when a subdomain is delegated includes
the following steps:

1) Evaluate the technical contact's experience with DNS. Make
sure there is a need for the proposed delegation. Make sure
the technical contact has the information about the US Domain
and the suggested naming structure. Two contacts with email
addresses are necessary in case something goes wrong.

2) Add the new technical contact to the "us-dom-adm" mailing list
for distributing updates concerning the US Domain policies and
procedures.

3) Delete any hosts from our zone file that belongs in the newly
delegated subdomain and make sure they now have the hosts in
their zone file.

4) Send them a copy of the zone file so their initial zone file
is identical to ours. For example:

5) The US Domain zone file must have the following records,
showing the name, address, email, and phone number of the
technical contact for the delegated subdomain and the name of
the delegated name space and the names of the name servers.

; A glue record is not needed this time. Glue records are
; needed when the name of the server is a subdomain of the
; delegated domain.
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;

6) Check to see that delegated subdomain name servers are up and
running, and make sure the delegated hosts are installed in
their zone file. Now delete any hosts from the US Domain zone
file that belongs in the newly delegated subdomain.

7) Inform the technical contact of the newly delegated subdomain
that wildcard records are allowed in the zone file under the
organizational subdomain but no wildcard records are allowed
under the "city" or "state" domain.

8) Make sure each administrator has a copy of this RFC and
follows the guidelines set forth.

3.3.3 Subdomain Contacts

The number of hosts registered under each subdomain is unknown. See
Section 3.1 for information on the delegated domains and the
contacts.

Cooper & Postel [Page 29]

RFC 1480 The US Domain June 1993
4. DATABASE INFORMATION

4.1. Name Servers

Name servers are the repositories of information that make up the
domain database. The database is divided up into sections called
zones, which are distributed among the name servers. While name
servers can have several optional functions and sources of data, the
essential task of a name server is to answer queries using data in
its zones. The response to a query can always be generated using
only local data, and either contains the answer to the question or a
referral to other name servers "closer" to the desired information.

A given zone will be available from several name servers to insure
its availability in spite of host or communication link failure.
Every zone is required to be available on at least two servers, and
many zones have more redundancy than that.

A "zone" is a registry of domains kept by a particular organization.
A zone registry is "authoritative", that is, the master copy of the
registry is kept by the zone organization, and this copy is, by
definition, always up-to-date. Copies of this registry may be
distributed to other places and kept in caches, but these caches are
not authoritative, and may be out-of-date.

Every zone has at least one node, and hence domain name, for which it
is authoritative, and all of the nodes in a particular zone are
connected. Given the tree structure, every zone has a highest node
which is closer to the root than any other node in the zone. The
name of this node is often used to identify the zone. The data that
describes a zone has four major parts:

1) Authoritative data for all nodes within the zone.

2) Data that defines the top node of the zone
(can be thought of as part of the authoritative data).

Cooper & Postel [Page 30]

RFC 1480 The US Domain June 1993
3) Data that describes delegated subzones, i.e., cuts
around the bottom of the zone,

4) Data that allows access to name servers for subzones
(sometimes called "glue" data).

The zone administrator has to maintain the zones at all the name
servers which are authoritative for the zone. When the changes are
made, they must be distributed to all of the name servers.

Copies of the zone files are not available unless you are on the
Internet. To look at the zone files use the "dig" program of the DNS
domain name system.

dig @nshost host-your-checking axfr

4.3 Resource Records

Records in the zone data files are called resource records (RRs).
The standard Resource records (RR) are specified in STD 13, RFC 1034
and STD 13, RFC 1035 (3,4). An RR has a standard format as shown.

<name> [<ttl>] [<class>] <type> <data>

The first field is always the name of the domain record. The second
field is an optional time to live field. This specifies how long
this data will be stored in the data base. The third field is the
address class; the class field specifies the protocol group most
often this is the Internet class "IN". The fourth field states the
type of the resource record. The fields after that are dependent on
the Type of RR. The fifth field is the data field which is defined
differently for each type and class of data. Here is a list of the
current commonly used types:

1) domain name
2) time to live information
3) mail exchanger record
4) preference value to determine (if more than one
forwarder) which mailer to use first, lower number
higher preference
5) the Internet forwarding host.

4.3.1 "A" Records

Internet (IP) Address. The data for an "A" record is an Internet
address in a dotted decimal form. A sample "A" record might look
like:

venera.isi.edu. A 128.9.0.32
(name) (A) (address)

The name field is the machine name, and the address is the network
address. There should be only one "A" record for each address of a
host.

4.3.2 CNAME Records

Canonical Name resource record, CNAME, specifies an alias for a
canonical name. This is essentially a pointer to the official name
for the requested name. All other RRs appear under this official
name. A machine named FERNWOOD.MPK.CA.US may want to have the
nickname ANTERIOR.MPK.CA.US. In that case, the following RR would be
used:

Nicknames (the name associated with the RR is the nickname) may be
added for awhile when a host changes its name, usually because it
moves to another state. It helps to have this CNAME pointer so if
any mail comes to the old address it will get forwarded to the new
one. There cannot be any other RRs associated with a nickname of the
same class.

Cooper & Postel [Page 32]

RFC 1480 The US Domain June 1993
4.3.3 MX Records

Mail Exchanger records, MX, are used to specify a machine that knows
how to deliver mail to a machine that is not directly connected to
the Internet. For example, venera.isi.edu is the mail gateway that
knows how to deliver mail to foo.la.ca.us, but other machines on the
network cannot deliver mail directly to foo.la.ca.us. These two
machines may have a private connection or use a different transport
medium (such as uucp). The preference value (10) is the order that a
mailer should follow when there is more than one way to deliver mail
to a single machine. The lower the number the higher the preference.

Host information resource records, HINFO is for host specific data.
This lists the hardware and operating system that are running at the
listed host. It should be noted that a space separates the hardware
information and the operating system information. If you want to
include a space in the machine name you must quote the name. Host
information is not specific to any class, so ANY may be used for the
address class. There should be one HINFO record for each host.

acb.la.ca.us. HINFO VAX-11/780 UNIX
(Hardware) (Operating System)

The official HINFO types can be found in the latest Assigned Numbers
RFC, the most recent edition being STD 2, RFC 1340 [9]. The hardware
type is called the Machine Name, and the software type is called the
System Name.

The information users supply about this is often inconsistent or
incomplete. Please follow the terms in the current "Assigned
Numbers".

4.3.5 PTR Records

A Domain Name Pointer record, PTR, allows special names to point to
some other location in the domain data base. These are typically
used in setting up reverse pointers for the special IN-ADDR.ARPA
domain. PTR names should be unique to the zone.

RFC 1480 The US Domain June 1993
A PTR record is to be added to the IN-ADDR.ARPA domain for every "A"
record registered in the US Domain. These PTR records need to be
added by the administrator of the network where the host is
connected. The US Domain Administration does not administer the
network and cannot make these entries in the DNS database.

4.4 Wildcards

The wildcard records are of the form "*.<anydomain>", where
<anydomain> is any domain name. The wildcards potentially apply to
descendents of <anydomain>, but not to <anydomain> itself.

For example, suppose a large company located in California with a
large, non-IP/TCP, network wanted to create a mail gateway. If the
company was called DWP.LA.CA.US, and the IP/TCP capable gateway
machine (Internet forwarder) was called ELROY.JPL.NASA.GOV, the
following RRs might be entered into the .US zone.

The wildcard record *.DWP.LA.CA.US would cause an MX query for any
domain name ending in DWP.LA.CA.US to return an MX RR pointing at
ELROY.JPL.NASA.GOV. The entry without the "*" is needed so the host
dwp can be found.

In the US Domain, wildcard records are allowed in our zone files
under the organizational subdomain (and where noted otherwise) but no
wildcard records are allowed under the "City" or "State" domain.

The authors strongly believe that it is in everyone's
interest and good for the Internet to have each host
explicitly registered (that is, we believe that wildcards
should not be used), we also realize that not everyone
agrees with this belief. Thus, we will allow wildcard
records in the US Domain under groups or organizations.
For example, *.DWP.LA.CA.US.

The reason we feel single entries are the best is by the mere
fact that if anyone wanted to find one of the hosts in the
domain name system it would be there, and problems can be
detected more easily. When using wildcards records all the
hosts under a subdomain are hidden.
Cooper & Postel [Page 34]

<fed-name> ::= <the dotted hierarchical name of a US
federal government agency>

<dni-name> ::= <the dotted hierarchical name of a
distributed national institution>

<locality> ::= <the full name of a city from the
zip code directory> |
<a short code name for a city> |
<the full name of a county, township,
or parish> |
<other well known and commonly used
locality name>

<state-agency-name> ::= <the dotted hierarchical name of a state
government agency>

<regional-agency-name> ::= <the dotted hierarchical name of a
special agency or district not an
element of the state government and
typically larger than a single city or
county, for example, the Southern
California Air Quality Management District>

Cooper & Postel [Page 37]

RFC 1480 The US Domain June 1993
<entity-name> ::= <the dotted hierarchical name of an
entity within a city, for example: a
company, business, private school, club,
organization, or individual>

<city-name> ::= <the dotted hierarchical name of a city
government agency>

<county-name> ::= <the dotted hierarchical name of a county,
township, or parish government agency>

<local-agency-name> ::= <the dotted hierarchical name of a special
agency or district not an element of a
city or county government and typically
equal or smaller than a single city or
county, for example, the Bunker Hill
Improvement District>

"K12" may be used for public school districts. A special name
"PVT" can be used in the place of a school district name for
private schools.

"CC" may be used only for public community colleges.
Cooper & Postel [Page 38]

RFC 1480 The US Domain June 1993
"LIB" may be only used by libraries.

"TEC" is used only for technical and vocational schools and colleges.

"GEN" is for general independent entities, that is, organizations
that don't really fit anywhere else (such as statewide associations,
clubs, and "domain parks").

"STATE" may be used only for state government entities.

Below US, parallel to States:

"FED" is for agencies of the federal government.

"DNI" is for distributed national institutes; organizations that
span state, regional, and other organizational boundaries; that
are national in scope, and have distributed facilities.

Examples:
=========

Geo-Petrellis.Culver-City.CA.US <== resturant

Joe-Josts.Long-Beach.CA.US <== bar

IBM.Armonk.NY.US <== business

Camp-Curry.Yosemite.CA.US <== business

Yosemite.NPS.Interior.FED.US <== federal agency

Senate.FED.US <== US Senate

DOD.FED.US <== US Defense Dept.

DOT.FED.US <== US Transportation Dept.

MNPL.FRB.FED.US <== the Minneapolis branch of
the Federal Reserve Bank

MetaCenter.DNI.US <== distributed Nat'l Inst

Senate.STATE.MN.US <== state Senate

House.STATE.MN.US <== state House of Reps

Assembly.STATE.CA.US <== state Assembly
Cooper & Postel [Page 39]

RFC 1480 The US Domain June 1993
MDH.STATE.MN.US <== state Health Dept.

DOT.STATE.MN.US <== state Transportation Dept

CALTRANS.STATE.CA.US <== state Transportation Dept

DMV.STATE.CA.US <== state Motor Vehicles Dept

Culver-City.DMV.STATE.CA.US <== local office of DMV

Police.CI.Culver-City.CA.US <== city department

Fire-Dept.CI.Los-Angeles.CA.US <== city department

Fire-Dept.CO.Los-Angeles.CA.US <== county department

Main.Library.CI.Los-Angeles.CA.US <== city department

MDR.Library.CO.Los-Angeles.CA.US <== county department

Huntington.LIB.CA.US <== private library

SMCC.Santa-Monica.CC.CA.US <== public community college

Trade-Tech.Los-Angeles.CC.CA.US <== public community college

Valley.Los-Angeles.CC.CA.US <== public community college

Hamilton.High.LA-Unified.K12.CA.US <== public school

Sherman-Oaks.Elem.LA-Unified.K12.CA.US <== public school

John-Muir.Middle.Santa-Monica.K12.CA.US <== public school

St-Monicas.High.Santa-Monica.CA.US <== private school

Crossroads-School.Santa-Monica.CA.US <== private school

Mary-Ellens-Montessori-School.LA.CA.US <== private school

Progress-Learning-Center.PVT.K12.CA.US <== private school

Brick-and-Basket-Institute.TEC.CA.US <== technical college

Bunker-Hill.DISTRICT.Los-Angeles.CA.US <== local district

SCAQMD.DISTRICT.CA.US <== regional district
Cooper & Postel [Page 40]

RFC 1480 The US Domain June 1993
Berkeley.UC.STATE.CA.US <== "CAL"

Los-Angeles.UC.STATE.CA.US <== UCLA

Irvine.UC.STATE.CA.US <== UC Irvine

Northridge.CSU.STATE.CA.US <== CSUN

Los-Angeles.CSU.STATE.CA.US <== Cal State LA

Leland-Stanford-Jr-University.Stanford.CA.US <== private school

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

Cooper & Postel [Page 41]

RFC 1480 The US Domain June 1993
APPENDIX-II: US DOMAIN QUESTIONNAIRE FOR HOST ENTRY
To register a host in the US domain, the US Domain Template must be
sent to the US Domain Registrar (US-Domain@ISI.EDU). The first few
pages explain each question on the attached template. FILL OUT THE
TWO PAGE TEMPLATE AT THE END. Questions may be sent by electronic
mail to the above address, or by phone to Ann Cooper, USC/Information
Sciences Institute, (310) 822-1511.

(1) Please specify whether this is a new application, modification to
an existing registration, or deletion.
(2) The name of the domain. This is the name that will be used in
tables and lists associating the domain with the domain server
addresses. See RFC 1480 - The US Domain for more details.

For example: networthy.santa-clara.ca.us.
(3) The name of the entity represented, that is, the organization
being named. For example: The Networthy Corporation. Not the
name of the organization submitting the request.
(4) Please describe the domain briefly.

For example: The Networthy Corporation is a consulting
organization of people working with UNIX and the C language
in an electronic networking environment. It sponsors two
technical conferences annually and distributes a bimonthly
newsletter.
(5) The date you expect the domain to be fully operational.

Cooper & Postel [Page 42]

RFC 1480 The US Domain June 1993
For every registration, we need both the Administrative and the
Technical contacts of a domain (questions 6 & 7) and we MUST have a
network mailbox for each. If you have a NIC handle (a unique NIC
database identifier) please enter it. (If you don't know what a NIC
handle is leave it blank). Also the title, mailing address, phone
number, organization, and network mailbox.

(6) The name of the administrative head of the "organization". The
administrator is the contact point for administrative and policy
questions about the domain. The Domain administrator should work
closely with the personnel he has designated as the "technical
contact" for his domain. In this example the Domain Administrator
would be the Administrator of the Networthy Corporation, not the
Administrator of the organization running the name server
(unless it is the same person).

(7) The name of the technical and zone contact. The technical and
zone contact handles the technical aspects of maintaining the
domain's name server and resolver software, and database files.
He keeps the name server running. More than likely, this person
would be the technical contact running the primary name server.

(a) Delegation (i.e., a portion of the US Domain name space is
given to an organization running name servers to support that
branch; For example, K12.TX.US, for all K12 schools in Texas).
For (a) answer questions 8 and 9.

(8) PRIMARY SERVER Information. It is required to supply both the
Contact information as well as hardware/software information of
the primary name server.

(9)* SECONDARY SERVER Information. It is required to supply the
hardware and software information of all secondary name servers.
Cooper & Postel [Page 43]

RFC 1480 The US Domain June 1993
Domains must provide at least two independent servers that provide the
domain service for translating names to addresses for hosts in this
domain. If you are applying for a domain and a network number
assignment simultaneously and a host on your proposed network will be
used as a server for the domain, you must wait until you receive your
network number assignment and have given the server(s) a net- address
before sending in the domain application. Establishing the servers in
physically separate locations and on different PSNs and/or networks is
strongly recommended.

NOTE: For those applicants not able to run name servers, or for non-IP
hosts the Name Server information is not applicable. (See #10 and #11).
=======================================================================
QUESTION FOR DIRECT IP HOSTS (If you answered 8 & 9 do not answer
10, 11, or 12).

(10) What Domain Name System (DNS) Resource Records (RR) and values are
to be entered for your IP host (must have an "A" record).

It is your responsibility to see that an IN-ADDR pointer record is
entered in the DNS database. (For Internet hosts only). Contact the
administrator of the IP network your host is on to have this done.
The US Domain administration does not administer the network and
cannot make these entries in the DNS database.

Many applicants have hosts in the UUCP world. Some are one hop away,
some two and three hops away from their "Internet Forwarder", this is
ok. What is important is getting an Internet host to be your
forwarder. If you do not already have an Internet forwarder, there
are several businesses that provide this service for a fee, (see
RFC 1359 - Connecting to the Internet What Connecting Institutions
Should Anticipate, ACM SIGUCCS, August 1992). Sometimes local colleges
in your area are already on the Internet and may be willing to act
as an Internet Forwarder. You would need to work this out with the
systems administrator. We cannot make these arrangements for you.

(11a) What is the name of your Internet forwarding host?
For example: The host Yacht-Club.MDR.CA.US uses
UUCP to connect to RELAY.ISI.EDU which is an Internet
host. (i.e., RELAY.ISI.EDU is the forwarding host).

(11b) What is the name of your contact person at forwarding host?
The Administrator of RELAY.ISI.EDU must agree to be the
forwarding host for Yacht-Club.MDR.CA.US, and the
forwarding host must know a delivery method and route to
Networthy. No double MXing.

(11c) What is the mailbox of your contact?
What is the mailbox of the administrator of the forwarding
host.

PLEASE SUBMIT THE FOLLOWING TWO PAGE TEMPLATE TO (Us-Domain@isi.edu).
Sections or fields of this form marked with an asterisk (*) may be
copied as many times as necessary. (For example: If you had two phone
numbers for the Administrative Contact, you would use the same number
"6h" twice. PLEASE DO NOT ALTER THIS APPLICATION IN ANY WAY.
=====================================================================
1. REGISTRATION TYPE
(N)ew (M)odify (D)elete..: