REGISTRATION DATA DIRECTORY SERVICE LABELING SPECIFICATION Sample Clauses

REGISTRATION DATA DIRECTORY SERVICE LABELING SPECIFICATION. 1. Provider shall maintain the following contact details and other data for each Customer associated with a Registered Name for which Provider is providing the Services. Domain Name Data: • Query format: whois EXAMPLE.TLD • Response format: Domain Name: EXAMPLE.TLD Registry Domain ID: D1234567-EXAMPLE Registrar WHOIS Server: whois.example-registrar.tld Registrar URL: xxxx://xxx.xxxxxxx-xxxxxxxxx.xxx Updated Date: 2009-05-29T20:13:00Z Creation Date: 2000-10-08T00:45:00Z Registry Expiry Date: 2010-10-08T00:44:59Z Registrar Registration Expiration Date: 2010-10-08T00:44:59Z Registrar: EXAMPLE REGISTRAR LLC Registrar IANA ID: 5555555 Registrar Abuse Contact Email: xxxxx@xxxxxxxxx.xxx Registrar Abuse Contact Phone: +1.1235551234 Reseller: EXAMPLE RESELLER1 Domain Status: clientDeleteProhibited xxxxx://xxxxx.xxx/epp#clientDeleteProhibited Domain Status: clientRenewProhibited xxxxx://xxxxx.xxx/epp#clientRenewProhibited Domain Status: clientTransferProhibited xxxxx://xxxxx.xxx/epp#clientTransferProhibited Registry Registrant ID: 5372808-EXAMPLE Registrant Name: EXAMPLE REGISTRANT Registrant Organization: EXAMPLE ORGANIZATION Registrant Street: 000 XXXXXXX XXXXXX Xxxxxxxxxx Xxxx: ANYTOWN Registrant State/Province: AP Registrant Postal Code: A1A1A116 Registrant Country: AA
Sample 1Sample 2
AutoNDA by SimpleDocs

Related to REGISTRATION DATA DIRECTORY SERVICE LABELING SPECIFICATION

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

  • Billing Specifications 55.6.1 The Parties agree that billing requirements and outputs will be consistent with the Ordering & Billing Form (OBF) and also with Telcordia Technologies Billing Output Specifications (BOS).

  • ODUF Packing Specifications 6.3.1 The data will be packed using ATIS EMI records. A pack will contain a minimum of one (1) message record or a maximum of ninety-nine thousand nine hundred and ninety-nine (99,999) message records plus a pack header record and a pack trailer record. One transmission can contain a maximum of ninety-nine (99) packs and a minimum of one (1) pack.

  • Service Specification The Parties have agreed upon the scope and specification of the Services provided under this Service Agreement in the Service Specification.

  • Specification and Service Levels The Specification sets out the Services that the Contractor has undertaken to provide. The Specification includes Service Levels setting out particular levels of service that the Contractor has undertaken to meet.

  • EODUF Packing Specifications 7.3.1 The data will be packed using ATIS EMI records. A pack will contain a minimum of one (1) message record or a maximum of ninety-nine thousand nine hundred and ninety-nine (99,999) message records plus a pack header record and a pack trailer record. One transmission can contain a maximum of ninety-nine (99) packs and a minimum of one (1) pack.

  • Product Specifications The Company agrees that all Products sold to Xxxx hereunder shall conform to the respective specifications set forth on Schedule A or to such other specifications as are from time to time agreed upon by the Parties.

  • Authorized User’s Statement of Work A competitive Mini-Bid is required for every transaction under this Centralized Contract. An Authorized User must prepare a detailed Statement of Work using Appendix F, Attachment 1, Mini-Bid Template. The Authorized User must distribute the Mini-Bid to all qualified Vendors per Lot(s) (unless a Vendor has removed itself from consideration via the Appendix F, Attachment 5, Mini-Bid Participation Interest Template). Contact information, organized by Lot, will be available on the OGS website for this Contract. An Authorized User shall conduct its Mini-Bid in accordance with the requirements set forth in Appendix F, Attachment 2, How to Use this Contract. The following terms and conditions shall apply to each Mini-Bid issued by an Authorized User:  An Authorized User may require the execution of unique forms, such as Confidentiality Non- Disclosure agreements; and  An Authorized User is required to make tentative award and non-award notifications to each Contractor who submitted a response to the Mini-Bid. Additionally, the minimum time, excluding the date of release, between issuance of the Mini-Bid by the Authorized User to the Mini-Bid Opening is as follows:  Xxx 0 Xxxx-Xxxx: Xxxx (0) Xxxxxxxx Xxxx  Xxx 0 Mini-Bids: Ten (10) Business Days

  • Technical Specification As enumerated in Special Conditions of Contract/Scope of Work/attached Drawing/ Details/Schedule of Rates.

  • Packing Specifications 7.3.1 A pack will contain a minimum of one message record or a maximum of 99,999 message records plus a pack header record and a pack trailer record. One transmission can contain a maximum of 99 packs and a minimum of one pack.

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