Web Interface Usage Conditions for Domain Registration and Admin istration
Web Interface Usage Conditions for Domain Registration and Admin Sample Clauses
Related to Web Interface Usage Conditions for Domain Registration and Admin
Bulk Registration Data Access to Icann Periodic Access to Thin Registration Data. In order to verify and ensure the operational stability of Registry Services as well as to facilitate compliance checks on accredited registrars, Registry Operator will provide ICANN on a weekly basis (the day to be designated by ICANN) with up-to-date Registration Data as specified below. Data will include data committed as of 00:00:00 UTC on the day previous to the one designated for retrieval by ICANN.
Exceptional Access to Thick Registration Data In case of a registrar failure, deaccreditation, court order, etc. that prompts the temporary or definitive transfer of its domain names to another registrar, at the request of ICANN, Registry Operator will provide ICANN with up-‐to-‐date data for the domain names of the losing registrar. The data will be provided in the format specified in Specification 2 for Data Escrow. The file will only contain data related to the domain names of the losing registrar. Registry Operator will provide the data as soon as commercially practicable, but in no event later than five (5) calendar days following ICANN’s request. Unless otherwise agreed by Registry Operator and ICANN, the file will be made available for download by ICANN in the same manner as the data specified in Section 3.1 of this Specification.
Periodic Access to Thin Registration Data In order to verify and ensure the operational stability of Registry Services as well as to facilitate compliance checks on accredited registrars, Registry Operator will provide ICANN on a weekly basis (the day to be designated by ICANN) with up-‐to-‐date Registration Data as specified below. Data will include data committed as of 00:00:00 UTC on the day previous to the one designated for retrieval by ICANN.
Conversion of Live Telephone Exchange Service to Analog 2W Loops The following coordination procedures shall apply to “live” cutovers of VERIZON Customers who are converting their Telephone Exchange Services to SPRINT Telephone Exchange Services provisioned over Analog 2W unbundled Local Loops (“Analog 2W Loops”) to be provided by VERIZON to SPRINT.
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.
Public Posting of Approved Users’ Research Use Statement The PI agrees that information about themselves and the approved research use will be posted publicly on the dbGaP website. The information includes the PI’s name and Requester, project name, Research Use Statement, and a Non-Technical Summary of the Research Use Statement. In addition, and if applicable, this information may include the Cloud Computing Use Statement and name of the CSP or PCS. Citations of publications resulting from the use of controlled-access datasets obtained through this DAR may also be posted on the dbGaP website.
Supplemental JBoss Software Conditions Software Access and Software Maintenance for Supplemental JBoss Software is intended and available for Development Purposes only and for up to 25 users for each 16 Core Band Subscription of Red Hat JBoss Middleware Software that you purchased. If you deploy or use the Supplemental JBoss Software for Production Purposes or for more than 25 users, you agree to purchase the appropriate Software Subscriptions for each Unit that you deploy or use. Red Hat’s Open Source Assurance Program applies only to the Red Hat JBoss Middleware Software Subscription that you purchased (such as Red Hat JBoss Enterprise Application Platform in the example above) and does not apply to Supplemental JBoss Software. JBoss xPaaS Subscriptions (defined below) are not considered Supplemental JBoss Software. Each installation and use of JBoss xPaaS Subscriptions Software for either Development Purposes or Production Purposes is a Unit and requires a paid Software Subscription.
Red Hat Enterprise Linux Desktop Software Subscriptions Software Subscriptions for Red Hat Enterprise Linux Desktops and Workstations are subject to the parameters set forth in Table 6 below. Each Red Hat Enterprise Linux Desktop and Workstation Software Subscription includes one Red Hat Network system entitlement and one Smart Management Module, each to be used solely with a single Red Hat Enterprise Linux Desktop or Workstation System. Production Support for Red Hat Enterprise Linux Desktop subscriptions is limited to web-based support only for your helpdesk support personnel. Red Hat is not obligated to support your end users directly.
IN CASE OF ERRORS OR QUESTIONS ABOUT YOUR ELECTRONIC TRANSFERS In the event that you believe there has been an error with respect to any original check or image thereof transmitted to the Credit Union for deposit or a breach of this Agreement and Disclosure, you will immediately contact the Credit Union regarding such error or breach as set forth below. • By calling the Credit Union at: 000-000-0000; • By emailing the Credit Union at: xxxxxxxxxx@xxxxxxxxxxx.xxx; or • By writing a letter and sending it to P.O. Box 60890, Los Angeles, CA 00000-0000. Contact us as soon as you can if you think your statement or receipt is wrong or if you need more information about a transfer listed on the statement or receipt. We must hear from you no later than 60 days after we sent the FIRST statement on which the problem or error appeared. • Tell us your name and Account number. • Describe the error or the transfer you are unsure about, and explain as clearly as you can why you believe it is an error or why you need more information. • Tell us the dollar amount of the suspected error. If you tell us orally, we may require that you send us your complaint or question in writing within ten (10) business days. We will tell you the results of our investigation within ten (10)* business days after we hear from you and will correct any error promptly. If we need more time, however, we may take up to 45** days to investigate your complaint or question. If we decide to do this, we will provisionally credit your Account within ten (10)* business days for the amount you think is in error, so that you will have the use of the money during the time it takes us to complete our investigation. If we ask you to put your complaint or question in writing and we do not receive it within ten (10) business days, we may not credit your Account. If we decide that there was no error, we will send you a written explanation within three (3) business days after we finish our investigation. You may ask for copies of the documents that we used in our investigation. * If you assert an error within 30 days after you make the first deposit to your Account, we will have 20 business days instead of ten (10) business days. ** If you give notice of an error within 30 days after you make the first deposit to your Account, or notice of an error involving a transaction initiated outside the United States, its possessions and territories, we will have 90 days instead of 45 days to investigate. In accordance with Visa Operating Rules and Regulations, you will receive a provisional credit for Visa Check Card losses for unauthorized use within five (5) business days after you have notified us of the loss. This does not apply to ATM transactions using a PIN(s).
LICENSE HOLDER CONTACT INFORMATION This noƟce is being provided for informaƟon purposes. It does not create an obligaƟon for you to use the broker’s services. Please acknowledge receipt of this noƟce below and retain a copy for your records. Davidson Bogel Real Estate, LLC 9004427 xxxx@xx0xx.xxx 214-526-3626 Licensed Broker /Broker Firm Name or Primary Assumed Business Name License No. Email Phone Xxxxxxx Xxxxxx Xxxxx XX 598526 xxxxxx@xx0xx.xxx 214-526-3626 Designated Broker of Firm License No. Email Phone Xxxxxxxxxxx Xxxx Xxxxxx 672133 xxxxxxx@xx0xx.xxx 214-526-3626 Licensed Supervisor of Sales Agent/ Associate License No. Email Phone N/A N/A N/A N/A Sales Agent/Associate’s Name License No. Email Phone Buyer/Tenant/Seller/Landlord Initials Date Regulated by the Texas Real Estate Commission InformaƟon available at xxx.xxxx.xxxxx.xxx
