GENERAL INSTRUCTIONS


Use the above Contact Template for registering new Contacts, for making
changes to existing Contact records, and for removing a Contact from the
InterNIC database.  The template, and only the template, should be sent
via email to HOSTMASTER@INTERNIC.NET.  Please do not send hardcopy
registrations to the InterNIC.  Your Internet Service Provider (ISP)
should be able to send email applications if you are not connected.
In the Subject of the message, use words "NEW CONTACT", "MODIFY CONTACT",
or "DELETE CONTACT" appropriately, followed by the NIC handle of the
Contact to help sort and locate incoming registration requests.  In
response to the submission of a template, you should receive an auto-reply
with a tracking number.  Use the tracking number in the Subject of any
subsequent message you send regarding that registration action.  When the
registration is completed you will receive a notification via email.

Please DO NOT modify the template or remove the version number.  The software
that processes the template looks for an item number, followed by a period,
followed by a colon.  Information following the colon is compared with and
inserted into the database.  Please send only one template per message.
When completing the template, make use of WHOIS at RS.INTERNIC.NET to
check to see if the Contact has been registered.  Use that information
where appropriate.  

Frequent users of the old User Template will notice significant differences
between the old User Template and the new Contact Template.  The Contact 
Template allows users to associate and protect their information with an 
encrypted password or Pretty Good Privacy (PGP) encryption software.
Please note that you MUST have the PGP software set up on your machine
before you can use it to protect your registered information.

If the Contact does not wish to use an encrypted password or PGP to protect
registered information, any request to update the Contact's information
MUST come from the currently listed email address of the Contact.  If the
email address of the Contact is changing, a request should be sent to the
InterNIC BEFORE the currently listed email address becomes inactive.  

To MODIFY or DELETE the record of an existing Contact, enter the appropriate
NIC handle and include data for the fields that are changing. The NIC handle
of a Contact is REQUIRED for MODIFYs and DELETEs.  The NIC handle can be
found in the WHOIS database by typing the Contact's name at the WHOIS prompt
in the format:

   Last Name, First Name

Requests for modification or deletion of a Contact's information MUST come
from the currently listed email address of the Contact.  However, the
request can come from another email address if the user has specified
encrypted password or PGP as its authentication scheme, and the correct
password is supplied or the message is encrypted and signed with the
Contact's secret PGP key.  If an update request originates from the correct
email address but an incorrect password is given or the message is not
encrypted with a valid PGP key, authorization from the Contact will be
REQUIRED.

Please note that only one record is allowed for a Contact in the InterNIC
database. Each Contact should be registered only once.  If a user is a
Contact for some Domain or Network records, those records MUST be updated
before the user's NIC handle is deleted.  

The Contact Template can only be used to update Contact information.  To
replace a Contact on a Domain record, use the Domain Template.  To replace
a Contact on a Host record, use the Host Template.

                       DETAILED INSTRUCTIONS


Section 0 - Authorization

Item 0a (N)ew (M)odify (D)elete

   Enter N or NEW to register a new Contact, M or MODIFY to update
   information associated with a Contact's handle, or D or DELETE
   to remove a Contact from the InterNIC database.

Item 0b Auth Scheme    
Item 0c Auth Info

   Items 0b and 0c should be left blank during the registration of a NEW
   Contact.  These items contain the authorization information for the
   sender of an update request and help determine if the request is
   coming from a valid sender.  These items are REQUIRED only when a
   Contact is being modified or deleted.

   Item 0b is the type of authentication scheme.  It can have values
   MAIL-FROM, CRYPT-PW, or PGP.  Item 0c is the authorization information
   for the selected authentication scheme.  As shown by the table below,
   items 0b and 0c are REQUIRED only when CRYPT-PW is the selected
   authentication scheme.  

   The different items 0b and 0c combinations are:

   If Item 0b is      Then Item 0c is

   MAIL-FROM          Ignored.  The FROM field in the mail header of an
                      update message will be checked to verify the sender.

                      MAIL-FROM is the DEFAULT authentication scheme.

   CRYPT-PW           Cleartext password (the plain text of the encrypted 
                      password).

   PGP                Ignored.  The sender should sign the entire update
                      message with its secret PGP key and send it in
                      cleartext to the InterNIC.


Section 1 - Contact Information

Item 1a NIC Handle

   Item 1a is REQUIRED only for MODIFYs and DELETEs.  DO NOT include a
   handle during registration of a new user.  The registration software
   automatically generates NIC handles for all the Contact records that
   are newly added to the InterNIC database.

Item 1b (I)ndividual (R)ole

   Use item 1b to identify the Contact as an individual or an organizational
   role account.  Enter I or INDIVIDUAL if the Contact being registered is
   an individual user, or R or ROLE if the Contact being registered is an
   organization or a group of users.  Item 1b is REQUIRED.
 
Item 1c Name
Item 1d Organization Name

   Item 1c is REQUIRED for NEWs, MODIFYs, and DELETEs.  If the Contact is
   an individual user, the name should be entered as:

      LASTNAME, FIRSTNAME MIDDLENAME

   For example: 

      Smith, John X.

   If you are adding or updating information for an organization, list the
   name of the role account in item 1c and the name of the organization
   the role account represents in item 1d.  Item 1c is REQUIRED for all
   Contacts.  If the name of the role account is the same as that of the
   organization, fill in item 1c with that name and leave item 1d blank.

Item 1e Street Address
Item 1f City
Item 1g State
Item 1h Postal Code
Item 1i Country Code

   At least one line of address information is REQUIRED in item 1e.  This
   address should be the postal mailing address for any correspondence
   directed to the Contact.  Enter the city and the standard two-letter
   state abbreviation in items 1f and 1g respectively if the Contact is
   located in the United States.

   You may add as many lines as necessary for your street address.  You may 
   do so by repeating item 1e.

   For the U.S. addresses, the postal code is REQUIRED in item 1h.

   Enter the ISO two-letter country code in Item 1i.  If no country code
   is entered, the Contact is assumed to be located in the United States.
   A list of ISO two-letter country codes is available at:
 
      ftp://rs.internic.net/netinfo/iso3166-countrycodes

Item 1j Phone Number
Item 1k Fax Number

   Every Contact is REQUIRED to provide at least one valid phone number in
   item 1j.  For informational purposes, you may supply a fax number in
   item 1k.   

Item 1l E-Mailbox

   A valid Internet email address is REQUIRED for all Contacts in item 1l.
   Separate the username and hostname parts of the mailbox by an "@" symbol.

   For example:

      user@example.com 


Section 2 - Notify Information

Item 2a Notify Update
Item 2b Notify Use

   The Contact Template allows a Contact to choose when to be notified about 
   the changes made to any information that the Contact record is associated
   with.

   Notify Update allows a Contact to indicate whether it should to notified 
   before or after updates to any record it is associated with are completed.

   Notify Use allows a Contact to indicate whether it should be notified
   before or after an Object it is associated with is used.  For example,
   if a Contact is the Technical Contact for a name server, the Contact
   may specify to be notified before the name server is listed on a Domain
   record.    

   Listing BEFORE-UPDATE or BEFORE-USE may delay registrations or updates
   since authorization may be required before an Object can be registered
   or updated.
  
   Items 2a and 2b contain the notification information for a Contact.
   These items are respectively the Notify Update and Notify Use attributes
   of a Contact.  The values for item 2a can be BEFORE-UPDATE, AFTER-UPDATE,
   or NOT-CARE.  The values for item 2b can be BEFORE-USE, AFTER-USE, or
   NOT-CARE.

Notify Update:

   BEFORE-UPDATE   The Contact will be notified before any database record
                   it is associated with is updated.

   AFTER-UPDATE    The Contact will be notified after any database record
                   it is associated with is updated.
  
                   AFTER-UPDATE is the DEFAULT value.

   NOT-CARE        The Contact will not be notified about any updates
                   because it does not want to be notified.

Notify Use:

   BEFORE-USE      The Contact will be notified before an Object it is
                   associated with is used.   

   AFTER-USE       The Contact will be notified after an Object it is
                   associated with is used.

                   AFTER-USE is the DEFAULT value.

   NOT-CARE        The Contact will not be notified about use of any
                   Object because it does not want to be notified.


Section 3 - Authentication Information

Item 3a Auth Scheme
Item 3b Auth Info
Item 3c Public (Y/N)

   Items 3a to 3c contain the authentication information for a Contact.
   These items are REQUIRED only if either the authentication information
   is being added to an existing Contact or a new Contact with authentication
   information is being registered.  Items 3a, 3b, and 3c are respectively
   the Auth Scheme, Auth Info, and Public attributes of a Contact.

Auth Scheme:

   This is the authentication scheme used to authenticate a Contact before
   updating any database record the Contact is associated with.  For example,
   if a Contact is listed as a point of contact for some Domain records, the
   auth scheme and auth info will be used during the update of any of those
   Domain records.

   The authentication schemes in an increasing order of strength are
   MAIL-FROM, CRYPT-PW, and PGP.

   MAIL-FROM    MAIL-FROM will check the FROM field in the email header
                of an update message and match it with the email address
                of the Contact.

                MAIL-FROM is the DEFAULT authentication scheme.

   CRYPT-PW     Initially when a new Contact is being registered or the
                authentication information is being added to an existing
                Contact, the encrypted password MUST be supplied.  The
                Unix crypt(3) routine should be used to encrypt a password.

                When the Contact record is being updated, or a record the
                Contact is associated with is being updated, the cleartext
                password MUST be supplied in item 0c of the template.

                CRYPT-PW will then encrypt the cleartext password supplied
                in the update message and match it with the encrypted
                password of the Contact in the InterNIC database.

   PGP          PGP stands for Pretty Good Privacy.  It is a military-grade
                authentication scheme.  In order to use this scheme, a
                Contact MUST have the PGP software installed on its machine.  
                   
                Before a Contact can use PGP to guard a database record,
                the Contact MUST register its public PGP key with the
                InterNIC.  To find out how to register your public PGP key
                with the InterNIC, send an email message with the Subject
                of "Help" to:

                pgpreg@internic.net   

                Once a Contact has installed the PGP software and has 
                registered its public PGP key with the InterNIC, the
                Contact will sign the update message with its secret PGP
                key and send it in cleartext to the InterNIC.  The
                InterNIC will verify the received update message with the
                Contact's public PGP key.

Auth Info:

   Authentication information for the selected authorization scheme.
   The authentication information stored in the database for a Contact
   registered with the InterNIC is: 

   MAIL-FROM    Email address of a Contact.

   CRYPT-PW     Encrypted password of a Contact.  When first registering 
                a Contact or when adding authentication information for a
                Contact, the encrypted password should be listed in item 3b. 
                The Unix crypt(3) routine should be used to generate the 
                encrypted password.  

   PGP          Key ID of the public PGP key of a Contact.

Public:

   Use this item to indicate whether the authentication information for a
   Contact will be public or not.  Public means visible in WHOIS. It can
   have values Y (Yes) or N (No).  The DEFAULT value is N.  Regardless of
   whether Yes or No is selected, the Contact's name, postal address,
   phone number, fax number, and email address will appear in the WHOIS
   database.

                          EXAMPLES


A file containing examples of completed templates is available at:

   ftp://rs.internic.net/templates/contact-template-examples.txt