Amendment No. 2 to the .NAME Registry Agreement
(14 July 2010)

Amendment No. 2 to the .NAME Registry Agreement

ICANN and VeriSign Information Services, Inc. agree that the following modification is made to Appendix 1, Exhibit C, of the .NAME Registry Agreement dated 15 August 2007:

[old text]

Exhibit C
ESCROW TRANSFER PROCESS

Deposit Transfer Process. Registry Operator shall prepare and transfer the Deposit file by the following steps, in sequence:

1. The Reports making up the Deposit will first be created according to the format specification. (See Exhibit B above, "Escrow Deposit Format Specification").

2. The Reports making up the Deposit will be concatenated. The resulting file shall be named according to the following format: "name-SEQN," where "SEQN" is a four digit decimal number that is incremented as each report is prepared.

3. ICANN may, at its option, provide to Registry Operator a tool that will verify the deposit complies with the format specification and contains reports of the same date/time (for a Full Deposit), count the number of objects of the various types in the Deposit, and append to the file a report of the program's results.

4. Registry Operator may optionally split the resulting file using the Unix SPLIT command (or equivalent) to produce files no less than 1 GB each (except the final file). If Deposit files are split, a .MD5 file (produced with MD5SUM or equivalent) must be included with the split files to isolate errors in case of transfer fault.

5. The Deposit file(s) will then be encrypted using Escrow Agent's public key for PGP/GPG and signed using Registry Operator's private key for PGP/GPG, both version 1.2.6 or above, with a key of DSA Elgamal type and 2048/1024-byte length.

The formatted, encrypted and signed Deposit file(s) will be sent, by anonymous secure file transfer protocol, SCP or similar, to Escrow Agent's server within the specified time window.

[new text]

Exhibit C
ESCROW TRANSFER PROCESS

Deposit Transfer Process. Registry Operator shall prepare and transfer the Deposit file by the following steps, in sequence:

1. The Reports making up the Deposit will first be created according to the format specification. (See Exhibit B above, "Escrow Deposit Format Specification").

2. The Reports making up the Deposit will be concatenated. The resulting file shall be named according to the following format: "name-SEQN-YYYYMMDD," where “SEQN” is a four digit decimal number that is incremented as each report is prepared, "YYYY" represents the year, “MM” the month, and “DD” the day of the date to which the file relates.

3. ICANN may, at its option, provide to Registry Operator a tool that will verify the deposit complies with the format specification and contains reports of the same date/time (for a Full Deposit), count the number of objects of the various types in the Deposit, and append to the file a report of the program's results.

4. Registry Operator may optionally split the resulting file using the Unix SPLIT command (or equivalent) to produce files no less than 1 GB each (except the final file). If Deposit files are split, a .MD5 file (produced with MD5SUM or equivalent) must be included with the split files to isolate errors in case of transfer fault.

5. The Deposit file(s) will then be encrypted using Escrow Agent's public key for PGP/GPG and signed using Registry Operator's private key for PGP/GPG, both version 1.2.6 or above, with a key of DSA Elgamal type and 2048/1024-byte length.

The formatted, encrypted and signed Deposit file(s) will be sent, by anonymous secure file transfer protocol, SCP or similar, to Escrow Agent's server within the specified time window.

The parties have duly executed this Amendment as of the date first written below.

Comments concerning the layout, construction and functionality of this site
should be sent to webmaster@icann.org.

© 2010  The Internet Corporation for Assigned Names and Numbers. All rights reserved.