EXAMPLES 1. How to Register an Individual as a New Contact 2. How to Register an Organization as a New Contact 3. How to Register a New Contact With an Encrypted Password 4. How to Register a New Contact With the PGP Authentication Scheme 5. How to Add Authentication Information to an Existing Contact's Record 6. How to Update a Contact That is Protected with an Encrypted Password 7. How to Change an Encrypted Password 8. How to Switch From Using an Encrypted Password to Using PGP 9. How to Remove Authentication Information From a Contact's Record 10. How to Delete a Contact 1. How to Register an Individual as a New Contact [ URL ftp://rs.internic.net/templates/Contact-template.txt ] [ 5/96 ] ***************** Please DO NOT REMOVE Version Number ***************** Contact Version Number: 1.0 ************** Please see attached detailed instructions ************** Authorization 0a. (N)ew (M)odify (D)elete.: N 0b. Auth Scheme.............: 0c. Auth Info...............: Contact Information 1a. NIC Handle..............: 1b. (I)ndividual (R)ole.....: I 1c. Name....................: Eden, Eric J. 1d. Organization Name.......: Network Solutions, Inc. 1e. Street Address..........: 505 Huntmar Park Dr. 1f. City....................: Herndon 1g. State...................: VA 1h. Postal Code.............: 22070 1i. Country Code............: US 1j. Phone Number............: 703-742-4777 1k. Fax Number..............: 703-742-4811 1l. E-Mailbox...............: erice@internic.net Notify Information 2a. Notify Update...........: BEFORE-UPDATE 2b. Notify Use..............: AFTER-USE Authentication Information 3a. Auth Scheme.............: 3b. Auth Info...............: 3c. Public (Y/N)............: Here, a new Contact, Eric J. Eden, is registered. The contact will be notified before any records he is associated with are updated AND after any other user starts using an object he is responsible for. Future updates to this record will have to originate from the e-mail address erice@internic.net A NIC handle would automatically be generated for the contact by the InterNIC's software. 2. How to Register an Organization as a New Contact [ URL ftp://rs.internic.net/templates/Contact-template.txt ] [ 5/96 ] ***************** Please DO NOT REMOVE Version Number ***************** Contact Version Number: 1.0 ************** Please see attached detailed instructions ************** Authorization 0a. (N)ew (M)odify (D)elete.: N 0b. Auth Scheme.............: 0c. Auth Info...............: Contact Information 1a. NIC Handle..............: 1b. (I)ndividual (R)ole.....: R 1c. Name....................: Hostmaster Role Account 1d. Organization Name.......: Network Solutions, Inc. 1e. Street Address..........: 505 Huntmar Park Dr. 1f. City....................: Herndon 1g. State...................: VA 1h. Postal Code.............: 22070 1i. Country Code............: US 1j. Phone Number............: 703-742-4777 1k. Fax Number..............: 703-742-4811 1l. E-Mailbox...............: hostmaster@internic.net Notify Information 2a. Notify Update...........: BEFORE-UPDATE 2b. Notify Use..............: AFTER-USE Authentication Information 3a. Auth Scheme.............: 3b. Auth Info...............: 3c. Public (Y/N)............: Here, the Hostmaster Role Account is registered as a contact. The Role Account will be notified before any records that it is associated with are updated AND after any other user starts using an object that it is responsible for. Future updates to this record will have to be sent from the e-mail address hostmaster@internic.net 3. How to Register a New Contact With an Encrypted Password [ URL ftp://rs.internic.net/templates/Contact-template.txt ] [ 5/96 ] ***************** Please DO NOT REMOVE Version Number ***************** Contact Version Number: 1.0 ************** Please see attached detailed instructions ************** Authorization 0a. (N)ew (M)odify (D)elete.: N 0b. Auth Scheme.............: 0c. Auth Info...............: Contact Information 1a. NIC Handle..............: 1b. (I)ndividual (R)ole.....: I 1c. Name....................: Eden, Eric J. 1d. Organization Name.......: Network Solutions, Inc. 1e. Street Address..........: 505 Huntmar Park Dr. 1f. City....................: Herndon 1g. State...................: VA 1h. Postal Code.............: 22070 1i. Country Code............: US 1j. Phone Number............: 703-742-4777 1k. Fax Number..............: 703-742-4811 1l. E-Mailbox...............: erice@internic.net Notify Information 2a. Notify Update...........: AFTER-UPDATE 2b. Notify Use..............: AFTER-USE Authentication Information 3a. Auth Scheme.............: CRYPT-PW 3b. Auth Info...............: %.d!Hr3@rm.Gh 3c. Public (Y/N)............: N Here, a new contact, Eric J. Eden, is registered with CRYPT-PW, an encrypted password, as his Authentication Scheme. The Contact will be notified after any record he is associated with is updated AND after any other user starts using an Object he is responsible for. The authentication information for the Contact, %.d!Hr3@rm.Gh, will not be visible in WHOIS. NOTE: Although the plain text of the encrypted password was HELLO, the encrypted password was correctly listed in Item 3b. 4. How to Register a New Contact With the PGP Authentication Scheme Before using PGP to protect a contact, and all the records that the contact is associated with, the contact must have the PGP software installed at their site. The public key of the contact must also be registered with the InterNIC before PGP can be used as an authentication scheme. The template can be encrypted with the contact's secret key and e-mailed to the InterNIC, or a plain text message may be sent with the key ID of the PGP public key listed in Item 3b. Either way, the template should originally look similar to the following example. [ URL ftp://rs.internic.net/templates/Contact-template.txt ] [ 5/96 ] ***************** Please DO NOT REMOVE Version Number ***************** Contact Version Number: 1.0 ************** Please see attached detailed instructions ************** Authorization 0a. (N)ew (M)odify (D)elete.: N 0b. Auth Scheme.............: 0c. Auth Info...............: Contact Information 1a. NIC Handle..............: 1b. (I)ndividual (R)ole.....: I 1c. Name....................: Eden, Eric J. 1d. Organization Name.......: Network Solutions, Inc. 1e. Street Address..........: 505 Huntmar Park Dr. 1f. City....................: Herndon 1g. State...................: VA 1h. Postal Code.............: 22070 1i. Country Code............: US 1j. Phone Number............: 703-742-4777 1k. Fax Number..............: 703-742-4811 1l. E-Mailbox...............: erice@internic.net Notify Information 2a. Notify Update...........: AFTER-UPDATE 2b. Notify Use..............: AFTER-USE Authentication Information 3a. Auth Scheme.............: PGP 3b. Auth Info...............: 710EDA97 3c. Public (Y/N)............: N 5. How to Add Authentication Information to an Existing Contact's Record In the below example, the contact EJE2 adds MAIL-FROM as an authentication scheme. The major benefit of this is that an update can now be sent from the e-mail address listed on the contact record (erice@internic.net) or the e-mail address listed in Item 3b (erice@zzzzzzzz.net) Note: To add authentication information, such as an encrypted password or PGP protection to a contact, the request must originate from the contact's current e-mail address in the WHOIS database. [ URL ftp://rs.internic.net/templates/Contact-template.txt ] [ 5/96 ] ***************** Please DO NOT REMOVE Version Number ***************** Contact Version Number: 1.0 ************** Please see attached detailed instructions ************** Authorization 0a. (N)ew (M)odify (D)elete.: M 0b. Auth Scheme.............: 0c. Auth Info...............: Contact Information 1a. NIC Handle..............: EJE2 1b. (I)ndividual (R)ole.....: I 1c. Name....................: Eden, Eric J. 1d. Organization Name.......: 1e. Street Address..........: 1f. City....................: 1g. State...................: 1h. Postal Code.............: 1i. Country Code............: 1j. Phone Number............: 1k. Fax Number..............: 1l. E-Mailbox...............: erice@internic.net Notify Information 2a. Notify Update...........: NOT-CARE 2b. Notify Use..............: NOT-CARE Authentication Information 3a. Auth Scheme.............: MAIL-FROM 3b. Auth Info...............: erice@zzzzzzzz.net 3c. Public (Y/N)............: N Here, future requests can be sent to update records associated with EJE2 from erice@zzzzzzzz.net or erice@internic.net because the contact has listed a second e-mail address in Item 3b. The contact will never be notified about updates to any records he is associated with because he has specified NOT-CARE for Notify Update and Notify Use. 6. How to Update a Contact That Has Protected its records with an Encrypted Password [ URL ftp://rs.internic.net/templates/Contact-template.txt ] [ 5/96 ] ***************** Please DO NOT REMOVE Version Number ***************** Contact Version Number: 1.0 ************** Please see attached detailed instructions ************** Authorization 0a. (N)ew (M)odify (D)elete.: M 0b. Auth Scheme.............: CRYPT-PW 0c. Auth Info...............: HELLO Contact Information 1a. NIC Handle..............: EJE2 1b. (I)ndividual (R)ole.....: I 1c. Name....................: Eden, Eric J. 1d. Organization Name.......: 1e. Street Address..........: 1f. City....................: 1g. State...................: 1h. Postal Code.............: 1i. Country Code............: 1j. Phone Number............: 1k. Fax Number..............: 1l. E-Mailbox...............: Notify Information 2a. Notify Update...........: 2b. Notify Use..............: Authentication Information 3a. Auth Scheme.............: 3b. Auth Info...............: 3c. Public (Y/N)............: Here, the authorization information in items 0a-0b is first verified and then the record for the Contact EJE2 is updated. The word HELLO in Item 0c is the plain text of the contact's encrypted password. 7. How to Change an Encrypted Password [ URL ftp://rs.internic.net/templates/Contact-template.txt ] [ 5/96 ] ***************** Please DO NOT REMOVE Version Number ***************** Contact Version Number: 1.0 ************** Please see attached detailed instructions ************** Authorization 0a. (N)ew (M)odify (D)elete.: M 0b. Auth Scheme.............: CRYPT-PW 0c. Auth Info...............: HELLO Contact Information 1a. NIC Handle..............: EJE2 1b. (I)ndividual (R)ole.....: I 1c. Name....................: Eden, Eric J. 1d. Organization Name.......: 1e. Street Address..........: 1f. City....................: 1g. State...................: 1h. Postal Code.............: 1i. Country Code............: 1j. Phone Number............: 1k. Fax Number..............: 1l. E-Mailbox...............: Notify Information 2a. Notify Update...........: 2b. Notify Use..............: Authentication Information 3a. Auth Scheme.............: CRYPT-PW 3b. Auth Info...............: 1er%472hs%t 3c. Public (Y/N)............: N Here, the contact is changing his encrypted password from HELLO to GOOD-BYE. The plain text of his original encrypted password is included in item 0c. The auth scheme CRYPT-PW is specified in 3a and the words GOOD-BYE are encrypted using the Unix crypt(3) routine and inserted in item 3b. 8. How to Switch From Using an Encrypted Password to Using PGP [ URL ftp://rs.internic.net/templates/Contact-template.txt ] [ 5/96 ] ***************** Please DO NOT REMOVE Version Number ***************** Contact Version Number: 1.0 ************** Please see attached detailed instructions ************** Authorization 0a. (N)ew (M)odify (D)elete.: M 0b. Auth Scheme.............: CRYPT-PW 0c. Auth Info...............: GOOD-BYE Contact Information 1a. NIC Handle..............: EJE2 1b. (I)ndividual (R)ole.....: 1c. Name....................: 1d. Organization Name.......: 1e. Street Address..........: 1f. City....................: 1g. State...................: 1h. Postal Code.............: 1i. Country Code............: 1j. Phone Number............: 1k. Fax Number..............: 1l. E-Mailbox...............: erice@internic.net Notify Information 2a. Notify Update...........: BEFORE-USE 2b. Notify Use..............: BEFORE-UPDATE Authentication Information 3a. Auth Scheme.............: PGP 3b. Auth Info...............: 710EDA97 3c. Public (Y/N)............: N Here, the contact is currently using CRYPT-PW as the authentication scheme for his record. Assuming the plain text of the encrypted password is verified as GOOD-BYE, the authentication scheme will be changed to PGP. The key ID of the contact's public key is inserted in Item 3b. Since BEFORE-USE and BEFORE UPDATE are specified, the contact will be notified before any object he is associated with is used AND he will be notified before any object he is associated with is updated. 9. How to Remove Authentication Information From A contact's record. [ URL ftp://rs.internic.net/templates/Contact-template.txt ] [ 5/96 ] ***************** Please DO NOT REMOVE Version Number ***************** Contact Version Number: 1.0 ************** Please see attached detailed instructions ************** Authorization 0a. (N)ew (M)odify (D)elete.: M 0b. Auth Scheme.............: CRYPT-PW 0c. Auth Info...............: HELLO Contact Information 1a. NIC Handle..............: EJE2 1b. (I)ndividual (R)ole.....: 1c. Name....................: 1d. Organization Name.......: 1e. Street Address..........: 1f. City....................: 1g. State...................: 1h. Postal Code.............: 1i. Country Code............: 1j. Phone Number............: 1k. Fax Number..............: 1l. E-Mailbox...............: erice@internic.net Notify Information 2a. Notify Update...........: 2b. Notify Use..............: Authentication Information 3a. Auth Scheme.............: NONE 3b. Auth Info...............: NONE 3c. Public (Y/N)............: N The word NONE in Item 3a and 3b indicate that the contact is giving up on being a Guardian and returning to being a regular contact with the authentication scheme of MAIL-FROM. All future updates to this contact's record will need to come from the e-mail address erice@internic.net. 10. How to Delete a Contact [ URL ftp://rs.internic.net/templates/Contact-template.txt ] [ 5/96 ] ***************** Please DO NOT REMOVE Version Number ***************** Contact Version Number: 1.0 ************** Please see attached detailed instructions ************** Authorization 0a. (N)ew (M)odify (D)elete.: D 0b. Auth Scheme.............: CRYPT-PW 0c. Auth Info...............: HELLO Contact Information 1a. NIC Handle..............: EJE2 1b. (I)ndividual (R)ole.....: I 1c. Name....................: Eden, Eric J. 1d. Organization Name.......: 1e. Street Address..........: 1f. City....................: 1g. State...................: 1h. Postal Code.............: 1i. Country Code............: 1j. Phone Number............: 1k. Fax Number..............: 1l. E-Mailbox...............: Notify Information 2a. Notify Update...........: 2b. Notify Use..............: Authentication Information 3a. Auth Scheme.............: 3b. Auth Info...............: 3c. Public (Y/N)............: Here, the plain text of the contact's encrypted password is supplied in Item 0c. Upon verification that HELLO is the plain text of the contact's encrypted password, the contact will be deleted. If the contact had specified PGP as its authentication scheme, 0b would be PGP and the message would be encrypted with the contact's secret key and e-mailed to the InterNIC. If the PGP key is verified, the contact's record would be deleted. If the contact had not specified CRYPT-PW or PGP as an authentication scheme, the request would have to originate from the contact's e-mail address erice@internic.net. The contact will not be deleted if it is still listed as a point of contact for any domain or network records. All database records the contact is associated with must be updated before the contact can be deleted.