Common use of RDAP Directory Services Clause in Contracts

RDAP Directory Services. 1.2.1 Registry Operator shall implement the most recent version of the RDAP Technical Implementation Guide and RDAP Response Profile posted at xxxxx://xxxxx.xxx/gtld-rdap-profile. Registry Operator will implement new versions of the RDAP Technical Implementation Guide and RDAP Response Profile no later than one hundred eighty (180) calendar days after notification from ICANN. 1.2.2 Registry Operator shall provide lookup query support for: (1) domain information as described in the section “Domain Path Segment Specification” of RFC 9082. (2) nameserver information as described in the section “Nameserver Path Segment Specification” of RFC 9082; provided, however, that Registry Operator shall not be required to (but may still choose to) support nameserver lookup if Registry Operator specifies name servers as domain attributes in EPP. (3) registrar information as described in the section “Entity Path Segment Specification” of RFC 9082. (4) help information as described in the section "Help Path Segment Specification" of RFC 9082. 1.2.3 ICANN reserves the right to specify alternative formats and protocols approved as “Internet Standards” (as opposed to Informational or Experimental standards) through the applicable IETF processes with respect to Registration Data. Upon such specification, ICANN shall: (a) work collaboratively with gTLD registries and ICANN-accredited registrars to define all operational requirements necessary to implement the applicable standard; and (b) if applicable, initiate negotiations to define all reporting requirements (if any), and reasonable service level requirements commensurate with similarly situated services.

RDAP Directory Services. 1.2.1 Registry Operator shall implement the most recent version of the RDAP Technical Implementation Guide and RDAP Response Profile posted at xxxxx://xxxxx.xxx/gtld-rdap-profile. Registry Operator will implement new versions of the RDAP Technical Implementation Guide and RDAP Response Profile no later than one hundred eighty (180) calendar days after notification from ICANN. 1.2.2 Registry Operator shall provide lookup query support for: (1) domain information as described in the section “Domain Path Segment Specification” of RFC 9082. (2) nameserver information as described in the section “Nameserver Path Segment Specification” of RFC 9082; provided, however, that Registry Operator shall not be required to (but may still choose to) support nameserver lookup if Registry Operator specifies name servers as domain attributes in EPP. (3) registrar information as described in the section “Entity Path Segment Specification” of RFC 9082. (4) help information as described in the section "Help Path Segment Specification" of RFC 9082. 1.2.3 ICANN reserves the right to specify alternative formats and protocols approved as “Internet Standards” (as opposed to Informational or Experimental standards) through the applicable IETF processes with respect to Registration Data. Upon such specification, ICANN shall: (a) work collaboratively with gTLD registries and ICANN-accredited registrars to define all operational requirements necessary to implement the applicable standard; and (b) if applicable, initiate negotiations to define all reporting requirements (if any), and reasonable service level requirements commensurate with similarly situated services, and upon such specification, the Registry Operator will implement such alternative specification as soon as reasonably practicable. Registry Operator shall implement a new standard supporting access to domain name registration data (SAC 051) no later than one hundred thirty-five (135) days after it is requested by ICANN if: 1) the IETF produces a standard (i.e., it is published, at least, as a Proposed Standard RFC as specified in RFC 2026); and 2) its implementation is commercially reasonable in the context of the overall operation of the registry.

RDAP Directory Services. 1.2.1 Registry Operator shall implement the most recent version of the RDAP Technical Implementation Guide and RDAP Response Profile posted at xxxxx://xxxxx.xxx/gtld-rdap-profile. Registry Operator will implement new versions of the RDAP Technical Implementation Guide and RDAP Response Profile no later than one hundred eighty (180) calendar days after notification from ICANN. 1.2.2 Registry Operator shall provide lookup query support for: (1) domain information as described in the section “Domain Path Segment Specification” of RFC 9082XXX 0000. (2) nameserver information as described in the section “Nameserver Path Segment Specification” of RFC 9082XXX 0000; provided, however, that Registry Operator shall not be required to (but may still choose to) support nameserver lookup if Registry Operator specifies name servers as domain attributes in EPP. (3) registrar information as described in the section “Entity Path Segment Specification” of RFC 9082XXX 0000. (4) help information as described in the section "Help Path Segment Specification" of RFC 9082. 1.2.3 ICANN reserves the right to specify alternative formats and protocols approved as “Internet Standards” (as opposed to Informational or Experimental standards) through the applicable IETF processes with respect to Registration Data. Upon such specification, ICANN shall: (a) work collaboratively with gTLD registries and ICANN-accredited registrars to define all operational requirements necessary to implement the applicable standard; and (b) if applicable, initiate negotiations to define all reporting requirements (if any), and reasonable service level requirements commensurate with similarly situated services.and

RDAP Directory Services. 1.2.1 Registry Operator shall implement the most recent version of the RDAP Technical Implementation Guide and RDAP Response Profile posted at xxxxx://xxxxx.xxx/gtld-rdap-profile. Registry Operator will implement new versions of the RDAP Technical Implementation Guide and RDAP Response Profile no later than one hundred eighty (180) calendar days after notification from ICANN. 1.2.2 Registry Operator shall provide lookup query support for: (1) domain information as described in the section “Domain Path Segment Specification” of RFC 9082XXX 0000. (2) nameserver information as described in the section “Nameserver Path Segment Specification” of RFC 9082XXX 0000; provided, however, that Registry Operator shall not be required to (but may still choose to) support nameserver lookup if Registry Operator specifies name servers as domain attributes in EPP. (3) registrar information as described in the section “Entity Path Segment Specification” of RFC 9082XXX 0000. (4) help information as described in the section "Help Path Segment Specification" of RFC 9082. 1.2.3 ICANN reserves the right to specify alternative formats and protocols approved as “Internet Standards” (as opposed to Informational or Experimental standards) through the applicable IETF processes with respect to Registration Data. Upon such specification, ICANN shall: (a) work collaboratively with gTLD registries and ICANN-accredited registrars to define all operational requirements necessary to implement the applicable standard; and (b) if applicable, initiate negotiations to define all reporting requirements (if any), and reasonable service level requirements commensurate with similarly situated services.