WHOIS Data Directory Services after the WHOIS Services Sunset Date Sample Clauses

WHOIS Data Directory Services after the WHOIS Services Sunset Date. If Registry Operator continues to offer WHOIS Data Directory Services after the WHOIS Services Sunset Date the following requirements will apply: 1.5.1 If Registry Operator continues to offer a WHOIS service available via port 43, Registry Operator shall do so in accordance with RFC 3912. 1.5.2 Registry Operator shall submit a change request to the IANA functions operator updating any outdated or inaccurate WHOIS records of the TLD as described in Specification 6, Section 1.6. 1.5.3 Personal data included in registration data must be redacted in accordance with ICANN Consensus Policies and Temporary Policies; 1.5.4 Registry Operator must adhere to the requirements related to additional fields of the Consistent Labeling and Display Consensus Policy if they choose to add data fields. 1.5.5 If the Registry Operator provides less registration data in WHOIS Data Directory Services than that available in the RDAP Directory Services, Registry Operator must add the following disclaimer in the WHOIS output footer: “The registration data available in this service is limited. Additional data may be available at xxxxx://xxxxxx.xxxxx.xxx”. 1.5.6 After the WHOIS Services Sunset Date, in the event of a conflict between the WHOIS Data Directory Service requirements and Consensus Policies or any Temporary Policy effective after the WHOIS Services Sunset Date, the Consensus Policies or Temporary Policy shall control, but only with respect to subject matter in conflict. 1.5.7 Until such time that updates are made and effective for Consensus Policies and procedures pursuant to the Phase 1 GNSO Consensus Policy recommendations of the Expedited Policy Development Process on the Temporary Specification for gTLD Registration Data, adopted by the ICANN Board in May 2019, as of the WHOIS Services Sunset Date, the following terms in such policies will be interpreted as follows: (1) With the exception of “Searchable Whois” and the “Whois contact lookup service”, the following terms: “WHOIS”, “Whois”, “Whois service”, “Publicly accessible Whois”, and variations thereof shall be interpreted to refer to RDDS as defined in this Specification.
Sample 1Sample 2Sample 3See All (12)
AutoNDA by SimpleDocs
WHOIS Data Directory Services after the WHOIS Services Sunset Date. If Registry Operator continues to offer WHOIS Data Directory Services after the WHOIS Services Sunset Date the following requirements will apply:
Sample 1Sample 2
WHOIS Data Directory Services after the WHOIS Services Sunset Date. If Registry Operator continues to offer WHOIS Data Directory Services after the WHOIS Services Sunset Date the following requirements will apply: 1.5.1 If Registry Operator continues to offer a WHOIS service available via port 43, Registry Operator shall do so in accordance with RFC 3912. 1.5.2 Registry Operator shall submit a change request to the IANA functions operator updating any outdated or inaccurate WHOIS records of the TLD as described in Specification 6, Section 1.6. 1.5.3 Personal data included in registration data must be redacted in accordance with ICANN Consensus Policies and Temporary Policies;
Sample 1Sample 2

Related to WHOIS Data Directory Services after the WHOIS Services Sunset Date

  • 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.

  • Unbundled Network Terminating Wire (UNTW) 2.8.3.1 UNTW is unshielded twisted copper wiring that is used to extend circuits from an intra-building network cable terminal or from a building entrance terminal to an individual End User’s point of demarcation. It is the final portion of the Loop that in multi-subscriber configurations represents the point at which the network branches out to serve individual subscribers. 2.8.3.2 This element will be provided in MDUs and/or Multi-Tenants Units (MTUs) where either Party owns wiring all the way to the End User’s premises. Neither Party will provide this element in locations where the property owner provides its own wiring to the End User’s premises, where a third party owns the wiring to the End User’s premises.

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