-
Communiqués
More
-
Correspondence
More
-
Itemized Advice
More
-
Principles & Guidelines
More
2005-04-05-ccTLD-8
GAC Advice
2005-04-05-ccTLD-8
N/A
Consensus met
2005-04-05-ccTLD-8
Communication
10. Communication Between ICANN and the ccTLD Registry
10.1 Principle
A Registry should not sub-contract part or all of the technical operations of the ccTLD Registry affecting the global stability of the DNS without ensuring that the subcontractor has the appropriate technical capability, and informing ICANN accordingly.
10.2 Guidelines
10.2.1. The communication between ICANN and the Registry should as a minimum contain ICANN's commitment to:
10.2.1.1 Maintain, or cause to be maintained, a stable, secure, authoritative and publicly available database of relevant information for each ccTLD (see below);
10.2.1.2 Ensure that authoritative and accurate root zone information is generated in a timely manner from such database and contribute to the root servers' operating in stable and secure manner. Also, ensure that changes to the root zone database are made on the basis of reliable authentication procedures confirming the authority and identity of the requesting party;
10.2.1.3 Maintain, or cause to be maintained, authoritative records and an audit trail regarding ccTLD delegations and records related to these delegations; and
10.2.1.4 Inform the Registry in a timely manner of any changes to ICANN's contact information.
10.2.2 The communication between ICANN and the Registry should contain the Registry's commitment to:
10.2.2.1. Cause to be operated and maintained in a stable and secure manner the authoritative primary and secondary name servers for the ccTLD, adequate to resolve names within the ccTLD for users throughout the Internet, and any sub-domains over which they retain administrative authority;
10.2.2.2. Inform ICANN in a timely manner of any changes to the ccTLD's contact information held by ICANN;
10.2.2.3. Set out clear conditions and parameters for any payment by the ccTLD.
Communication
10. Communication Between ICANN and the ccTLD Registry
10.1 Principle
A Registry should not sub-contract part or all of the technical operations of the ccTLD Registry affecting the global stability of the DNS without ensuring that the subcontractor has the appropriate technical capability, and informing ICANN accordingly.
10.2 Guidelines
10.2.1. The communication between ICANN and the Registry should as a minimum contain ICANN's commitment to:
10.2.1.1 Maintain, or cause to be maintained, a stable, secure, authoritative and publicly available database of relevant information for each ccTLD (see below);
10.2.1.2 Ensure that authoritative and accurate root zone information is generated in a timely manner from such database and contribute to the root servers' operating in stable and secure manner. Also, ensure that changes to the root zone database are made on the basis of reliable authentication procedures confirming the authority and identity of the requesting party;
10.2.1.3 Maintain, or cause to be maintained, authoritative records and an audit trail regarding ccTLD delegations and records related to these delegations; and
10.2.1.4 Inform the Registry in a timely manner of any changes to ICANN's contact information.
10.2.2 The communication between ICANN and the Registry should contain the Registry's commitment to:
10.2.2.1. Cause to be operated and maintained in a stable and secure manner the authoritative primary and secondary name servers for the ccTLD, adequate to resolve names within the ccTLD for users throughout the Internet, and any sub-domains over which they retain administrative authority;
10.2.2.2. Inform ICANN in a timely manner of any changes to the ccTLD's contact information held by ICANN;
10.2.2.3. Set out clear conditions and parameters for any payment by the ccTLD.