Name Collision Report Handling. 6.3.1 During the first two years after delegation of the TLD, Registry Operator’s emergency operations department shall be available to receive reports, relayed by ICANN, alleging demonstrably severe harm from collisions with overlapping use of the names outside of the authoritative DNS.
Appears in 2168 contracts
Samples: Registry Agreement, Registry Agreement, Registry Agreement
Name Collision Report Handling. 6.3.1 During the first two years after delegation of the TLD, Registry Operator’s emergency operations department shall be available to receive reports, relayed by ICANN, alleging demonstrably severe harm from collisions with overlapping use of the names outside of the authoritative DNS.
Appears in 1078 contracts
Samples: Registry Agreement, Registry Agreement, Registry Agreement
Name Collision Report Handling. 6.3.1 1. During the first two years after delegation of the TLD, Registry Operator’s emergency operations department shall be available to receive reports, relayed by ICANN, alleging demonstrably severe harm from collisions with overlapping use of the names outside of the authoritative DNS.
Appears in 3 contracts
Samples: Registry Agreement, Registry Agreement, Registry Agreement
Name Collision Report Handling. 6.3.1 During the first two years after delegation of the TLD, Registry OperatorO perator’s emergency operations department shall be available to receive reports, relayed by ICANN, alleging demonstrably severe harm from collisions with overlapping use of the names outside of the authoritative DNS.
Appears in 1 contract
Samples: Registry Agreement
Name Collision Report Handling. 6.3.1 During the first two years after delegation of the TLD, Registry Operator’s emergency operations department shall be available to receive reports, relayed by ICANN, alleging demonstrably severe harm from collisions with overlapping use of the names outside of the ofthe authoritative DNS.
Appears in 1 contract
Samples: Registry Agreement