Format. The format for the above files shall be as specified by ICANN, after consultation with Registry Operator. The procedures for providing daily access shall be as mutually agreed by ICANN and Registry Operator. In the absence of an agreement, the files shall be provided by Registry Operator sending the files in encrypted form to the party designated by ICANN by Internet File Transfer Protocol.
Appears in 8 contracts
Samples: Registry Operator's Monthly Reports, Registry Operator's Monthly Reports, Registry Agreement (Verisign Inc/Ca)
Format. The format for the above files shall be as specified by ICANN, after consultation with Registry Operator. The procedures for providing daily access shall be as mutually agreed by ICANN and Registry Operator. In the absence of an agreement, an up-to-date version (encrypted using a public key supplied by ICANN) of the files shall be provided by Registry Operator sending the files in encrypted form to the party placed at least once per day on a designated server and available for downloading by ICANN by Internet File Transfer Protocol.
Appears in 5 contracts
Samples: Registry Agreement (Verisign Inc/Ca), Registry Agreement, Registry Agreement (Verisign Inc/Ca)
Format. The format for the above files shall be as specified by ICANN, after consultation with Registry Operator. Procedures for Providing Access The procedures for providing daily access shall be as mutually agreed by ICANN and Registry Operator. In the absence of an agreement, the files shall be provided by Registry Operator sending the files in encrypted form to the party designated by ICANN by Internet File Transfer Protocol.
Appears in 2 contracts
Samples: Whois Specifications, Whois Specifications
Format. The format for the above files shall be as specified by ICANN, after consultation with Registry Operator. Procedures for Providing Access The procedures for providing daily access shall be as mutually agreed by ICANN and Registry Operator. In the absence of an agreement, an up-to-date version (encrypted using a public key supplied by ICANN) of the files shall be provided by Registry Operator sending the files in encrypted form to the party placed at least once per day on a designated server and available for downloading by ICANN by Internet File Transfer Protocol.
Appears in 2 contracts
Samples: Registry Agreement, Registry Agreement
Format. The format for the above files shall be as specified by ICANN, after consultation with Registry Operator. Procedures for Providing Access The procedures for providing daily access shall be as mutually agreed by ICANN and Registry Operator. In the absence of an agreement, an up-to-date version (encrypted using a public key supplied by ICANN) of the files shall be provided by Registry Operator sending the files in encrypted form to the party placed at least once per day on a designated server and available for downloading by ICANN by Internet File Transfer Protocol.. .NET Registry Agreement Appendix 5A Whois Specifications
Appears in 1 contract
Samples: Registry Agreement
Format. The format for the above files shall be as specified by ICANN, after consultation with Registry Operator. The procedures for providing daily access shall be as mutually agreed by ICANN and Registry Operator. In the absence of an agreement, an up-to-date version (encrypted using a public key supplied by ICANN) of the files shall be provided by Registry Operator sending the files in encrypted form to the party placed at least once per day on a designated server and available for downloading by ICANN by Internet File Transfer Protocol.. .COM Agreement Appendix 7 Functional and Performance Specifications These functional specifications for the Registry TLD consist of the following parts:
Appears in 1 contract
Samples: Registry Operator's Monthly Reports
