RDAP Directory Services Sample Clauses

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.
Sample 1Sample 2Sample 3See All (15)
AutoNDA by SimpleDocs
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.
Sample 1Sample 2Sample 3See All (8)
RDAP Directory Services. 1.2.1. Registrar shall implement the most recent version of the RDAP Technical Implementation Guide and RDAP Response Profile posted at xxxxx://xxxxx.xxx/gtld-rdap-profile. Registrar 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.
Sample 1Sample 2

Related to RDAP Directory Services

  • Registration Data Directory Services Until ICANN requires a different protocol, Registry Operator will operate a WHOIS service available via port 43 in accordance with XXX 0000, and a web-­‐based Directory Service at <whois.nic.TLD> providing free public query-­‐based access to at least the following elements in the following format. ICANN reserves the right to specify alternative formats and protocols, 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. 1.1. The format of responses shall follow a semi-­‐free text format outline below, followed by a blank line and a legal disclaimer specifying the rights of Registry Operator, and of the user querying the database. 1.2. Each data object shall be represented as a set of key/value pairs, with lines beginning with keys, followed by a colon and a space as delimiters, followed by the value. 1.3. For fields where more than one value exists, multiple key/value pairs with the same key shall be allowed (for example to list multiple name servers). The first key/value pair after a blank line should be considered the start of a new record, and should be considered as identifying that record, and is used to group data, such as hostnames and IP addresses, or a domain name and registrant information, together. 1.4. The fields specified below set forth the minimum output requirements. Registry Operator may output data fields in addition to those specified below, subject to approval by ICANN, which approval shall not be unreasonably withheld.

  • Hospice Services Services are available for a Member whose Attending Physician has determined the Member's illness will result in a remaining life span of six months or less.

  • Pharmacy Services The Contractor shall establish a network of pharmacies. The Contractor or its PBM must provide at least two (2) pharmacy providers within thirty (30) miles or thirty (30) minutes from a member’s residence in each county, as well as at least two (2) durable medical equipment providers in each county or contiguous county.

Draft better contracts in just 5 minutes Get the weekly Law Insider newsletter packed with expert videos, webinars, ebooks, and more!