[CLUE-Adm] Domain template for clue.denver.co.us

[Lynn Danielson]

Below the "us" domain template needed for updating the
clue.denver.co.us and associated domains.  Other domains
which we currently are using include linux.denver.co.us
and lug.denver.co.us.

The maintainer for denver.co.us is (or at least was)
Chris Garner <chris.garner at qwest.com>.  The last time we
communicated his reply-to was <cgarner at qip.quest.net> and
he copied the correspondence to <DNS at WorldServe.com>.

I'm going to try to follow this up with more complete notes
about how to determine who the current maintainer is and
where a current template can be found.  Unless someone has
a better suggestion, I can put a link to this up on our
admin web page, so that we don't lose it.

Lynn

===========================================================
===========================================================

US DOMAIN TEMPLATE

US Version:  Jul 97

PLEASE DO NOT ALTER THIS APPLICATION IN ANY WAY.  Send your 
.US registration to us-domain at isi.edu.  See attached detailed
instructions.

*****************************************************************

      1.   REGISTRATION TYPE
           (N)ew (M)odify (D)elete..:

      2.   FULLY-QUALIFIED DOMAIN NAME:

      3.   ORGANIZATION INFORMATION
      3a.  Organization Name.....:
      3b.  Address Line 1........:
      3b.  Address Line 2........:
      3c.  City..................:
      3d.  State.................:
      3e.  Zip/Code..............:

      4.   DESCRIPTION OF ORG/DOMAIN:

      5.   Date Operational......:

      6.   ADMINISTRATIVE CONTACT OF ORG/DOMAIN
      6a.  NIChandle (if known)..:
      6b.  Whole Name............:
      6c.  Organization Name.....:
      6d.  Address Line 1........:
      6d.  Address Line 2........:
      6e.  City..................:
      6f.  State.................:
      6g.  Zip/Code..............:
      6h.  Voice Phone...........:
      6i.  Electronic Mailbox....:

      7.   TECHNICAL AND ZONE CONTACT
      7a.  NIChandle (if known)..:
      7b.  Whole Name............:
      7c.  Organization Name.....:
      7d.  Address Line 1........:
      7d.  Address Line 2........:
      7e.  City..................:
      7f.  State.................:
      7g.  Zip/Code..............:
      7h.  Voice Phone...........:
      7i.  Electronic Mailbox....:
      7j.  Registration Mailbox..:
      7k.  Fax Number............:

      8.   PRIMARY SERVER: HOSTNAME, NETADDRESS
      8j.  Hostname..............:
      8k.  IP Address............:

      9.   SECONDARY SERVER: HOSTNAME, NETADDRESS
      9a.  Hostname..............:
      9b.  IP Address............:
^L
**************************************************************************
                           DISCLAIMER

By the registration of your name on the Internet, the IANA, the
InterNIC, Network Solutions Inc., the University of Southern
California, and the National Science Foundation are accepting in good
faith that you have the right to the use the name.

The IANA and InterNIC/Network Solutions' function in registering names
on the Internet is to assure that the name does not conflict with any
other name in the name space requested.

The user by its registration and use of the name and/or their
continued use of an existing name, agrees, as part of their request
for name registration, to indemnify and hold harmless from any and all
costs, fees, expenses arising from litigation involving trademark,
trade name, service mark, and any other name infringements, or other
reasons, the IANA, the InterNIC, Network Solutions Inc., the
University of Southern California, and the National Science
Foundation.

The party requesting registration of this name certifies that to
her/his knowledge, the use of this name does not violate trademark or
other statutes.

It is assumed by the US Domain Administrator that every applicant for
the delegation (or redelegation) of a locality name has the written
agreement of the legitimate government for that locality for the
applicant to manage the domain name of that locality.

Registering a domain name does not confer any legal rights to that
name and any disputes between parties over the rights to use a
particular name are to be settled between the contending parties using
normal legal methods (See RFC 1591).

Domains must provide at least two independent servers that provide the
domain service for translating names to addresses for hosts in this
domain. Establishing the servers in physically separate locations and
on different PSNs and/or networks is strongly recommended.

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 assigment and have given the server(s) a net-address before
sending in the domain application. To apply for an IP address, contact
your service provider or send a message to "hostmaster at internic.net".
The US Domain Registry registers US Domain names only.


***************************  CUT HERE  **********************************
^L
                INSTRUCTIONS FOR THE US DOMAIN TEMPLATE


The US Domain Template must be sent to the US Domain Registrar
(US-Domain at ISI.EDU) or the contact of a delegated zone.

US Domain Registrar
USC/Information Sciences Institute
4676 Admiralty Way,
Marina del Rey, CA 90292
Phone: 310-822-1511

The list of delegated subdomains in each state for (K12, CC, TEC,
STATE, LIB, MUS, GEN, DST, COG and localities) can be retrieved 
via WWW, and FTP.

  URL:  ftp://isi.edu/in-notes/us-domain-delegated.txt

OTHER TYPES OF REGISTRATIONS:

To register domain names under (COM, EDU,GOV, NET), get IP Addresses,
or register your IN-ADDR, contact your service provider, or send email
to "hostmaster at internic.net" or retrieve information from:

   URL:  http://rs.internic.net/rs-internic.html

Please Note: All K12 schools, community colleges/technical schools,
state and local governments are required to register under the US
domain. Only four year universities are allowed to register under EDU.
Only federal agencies are allowed under GOV. See RFC 1480, 1591 and
1816 for further details.

RFCs
   RFC 1480 - THE US DOMAIN
              URL: ftp://ftp.isi.edu/in-notes/rfc1480.txt
   RFC 1591 - THE DOMAIN NAME SYSTEM STRUCTURE AND DELEGATION
              URL: ftp://ftp.isi.edu/in-notes/rfc1591.txt
   RFC 1811 - U.S. GOVERNMENT INTERNET DOMAIN NAMES
              URL: ftp://ftp.isi.edu/in-notes/rfc1811.txt

*******************************************************************************8
^L

                REGISTERING A NEW US DOMAIN NAME


1. REGISTRATION TYPE:  NEW, MODIFICATION, 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 Naming Structure Table below.  The following 
   formats are accepted as a US Domain name.

      Domain Name Example:  networthy.santa-clara.ca.us

============================================================================
                TABLE:  US DOMAIN NAMING STRUCTURE
============================================================================

Locality Names          <host>.<locality>.<state-code>.US 
  City Government       <host>.CI.<locality>.<state-code>.US
  County Government     <host>.CO.<locality>.<state-code>.US 

Schools 
  K12 Districts         <school-district>.K12.<state-code>.US
  K12 Schools           <school>.<district>.K12.<state-code>.US
  Private               <school>.PVT.K12.<state-code>.US
  Private Opt.          <school>.<locality>.<state-code>.US
Community Colleges      <school>.CC.<state-code>.US
Technical Schools       <school>.TEC.<state-code>.US

Library                 <library-name>.LIB.<state-code>.US
State Gov.              <state-agency>.STATE.<state-code>.US
GEN (statewide assoc.)  <org-name>.GEN.<state-code>.US
Museums                 <org-name>.MUS.<state-code>.US
Councils of Gov.        <org-name>.COG.<state-code>.US
DST (districts)         <org-name>.DST.<state-code>.US
FED                     <federal-agency>.FED.US
NSN                     <indian-nation>.NSN.US
ISA (multi-state-gov.)  <org-name>.ISA.US

============================================================================

3.  THE NAME OF THE ENTITY REPRESENTED, (i.e., ORGANIZATION, LOCALITY,
    SCHOOL, etc., being named.  The name that describes the Fully
    Qualified Domain Name that will be entered in the WHOIS database.
    For example:  The Networthy Corporation, not the name of the
    Network Service Provider or 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.


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).  We will create a US one for you.  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.  That is, the Administrative
    Contact would be a person from the organization that is the
    ultimate user of the domain name, not a person from the
    organization running the nameserver.  Specifically, when the
    organization using the domain name is a city government, the
    Administrative Contact must be a city government employee, not an
    employee of the service provider arranging the Internet connection
    for the city.  It is assumed by the US Domain Administrator that
    every applicant for the delegation (or redelegation) of a locality
    name has the written agreement of the legitimate government for
    that locality for the applicant to manage the domain name of that
    locality.


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 nameserver.
    The REGISTRATION REQUEST MAILBOX (7j) is where domain name
    requests are mailed and processed for the delegated domain.
    Mailboxes names would be like: hostmaster, support, domreg).

8.  PRIMARY SERVER. The complete host name of the primary server as
    well as the IP address.

9.  SECONDARY SERVER.The complete host name of the secondary server as
    well as the IP address.

Domains must provide at least two independent servers that provide the
domain service for translating names to addresses for hosts in this
domain. Establishing the servers in physically separate locations and on
different PSNs and/or networks is strongly recommended.

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 assigment and have given the server(s) a net-address before
sending in the domain application.  To apply for an IP address,
contact your service provider or send a message to
"hostmaster at internic.net".  The US Domain registry registers US Domain
names only.

+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+