Common use of RDAP Directory Services Clause in Contracts

RDAP Directory Services. 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/gltd-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. 2.2 Registry Operator shall provide lookup query support for: 2.2.1 domain information as described in the section “Domain Path Segment Specification” of RFC 9082. 2.2.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. 2.2.3 registrar information as described in the section “Entity Path Segment Specification” of RFC 9082. 2.2.4 help information as described in the section "Help Path Segment Specification" of RFC 9082.

RDAP Directory Services. 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/gltd-rdap-profilexxxxx://xxxxx.xxx/gltd- 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. 2.2 Registry Operator shall provide lookup query support for: 2.2.1 domain information as described in the section “Domain Path Segment Specification” of RFC 9082. 2.2.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. 2.2.3 registrar information as described in the section “Entity Path Segment Specification” of RFC 9082. 2.2.4 help information as described in the section "Help Path Segment Specification" of RFC 9082.