Registration Data Directory Services Sample Clauses

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.
Sample 1Sample 2Sample 3See All (3k)
AutoNDA by SimpleDocs
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. 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. 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. 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. 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. Domain Name Data: Query format: whois EXAMPLE.TLD Response format:
Sample 1Sample 2Sample 3See All (1k)
Registration Data Directory Services. Registration Data Directory Services (or RDDS) refers to the collective of WHOIS (via port 43), WHOIS web-based directory service(s) and Registration Data Access Protocol (“RDAP”) services, as defined in this Appendix. Registry Operator shall offer public IPv6 and IPv4 transports for its RDDS. Registry Operator will operate a WHOIS service available via port 43 in accordance with RFC 3912 at xxxxx.xxxxxxxx.xxx, and a WHOIS web- based directory service at xxx.xxxxxxxx.xxx/xxxxx providing free public query- based access to the elements defined in this Appendix 5A.
Sample 1Sample 2Sample 3See All (6)
Registration Data Directory Services. Until ICANN requires a different protocol, Registry Operator will operate a
Sample 1Sample 2Sample 3See All (4)
Registration Data Directory Services. Registration Data Directory Services or “RDDS” refers to the collective of WHOIS Data Directory Services (as defined in this Appendix 5A) and RDAP Directory Services, as defined in Appendix 5B.
Sample 1Sample 2Sample 3See All (4)
Registration Data Directory Services. Until cxDA requires a different protocol, XxXXX 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. cxDA reserves the right to specify alternative formats and protocols, and upon such specification, XxXXX will implement such alternative specification as soon as reasonably practicable. XxXXX 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 cxDA 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.
Sample 1Sample 2
Registration Data Directory Services. 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.
Sample 1Sample 2
AutoNDA by SimpleDocs
Registration Data Directory Services. Until ICANN requires a different protocol, Registry Operator will operate a WHOIS service available via port 43 in accordance with RFC 3912 at xxxxx.xxxxxxxx.xxx, and a web-based Directory Service at xxx.xxxxxxxx.xxx/xxxxxxx <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.
Sample 1
Registration Data Directory Services 
Sample 1Sample 2Sample 3See All (11)

Related to Registration Data Directory Services

  • Hosting Services 13.1 If Supplier or its subcontractor, affiliate or any other person or entity providing products or services under the Contract Hosts Customer Data in connection with an Acquisition, the provisions of Appendix 1, attached hereto and incorporated herein, apply to such Acquisition.

  • Internet Services Transfer Agent shall make available to Fund and Shareholders, through its web sites, including but not limited to xxx.xxxxxxxxxxxxx.xxx (collectively, “Web Site”), online access to certain Account and Shareholder information and certain transaction capabilities (“Internet Services”), subject to Transfer Agent’s security procedures and the terms and conditions set forth herein and on the Web Site. Transfer Agent provides Internet Services “as is,” on an “as available” basis, and hereby specifically disclaims any and all representations or warranties, express or implied, regarding such Internet Services, including any implied warranty of merchantability or fitness for a particular purpose and implied warranties arising from course of dealing or course of performance. Transfer Agent shall at all times use reasonable care in performing Internet Services under this Agreement.

  • Support Services HP’s support services will be described in the applicable Supporting Material, which will cover the description of HP’s offering, eligibility requirements, service limitations and Customer responsibilities, as well as the Customer systems supported.

  • TECHNICAL SUPPORT SERVICES 2.1 The technical support services (the "Services"): Party A agrees to provide to Party B the relevant services requested by Party B, which are specified in Exhibit 1 attached hereto ("Exhibit 1").

  • Information Services The Custodian may rely upon information received from issuers of Securities or agents of such issuers, information received from Subcustodians or depositories, information from data reporting services that provide detail on corporate actions and other securities information, and other commercially reasonable industry sources; and, provided the Custodian has acted in accordance with the standard of care set forth in Section 6 (a), the Custodian shall have no liability as a result of relying upon such information sources, including but not limited to errors in any such information.

Time is Money Join Law Insider Premium to draft better contracts faster.