Domain Name Registration If Customer submits a Service Order(s) for domain name registration services, the following terms shall also apply:
Publication of Registration Data Registry Operator shall provide public access to registration data in accordance with Specification 4 attached hereto (“Specification 4”).
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.
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.
Registration Data Upon placing an order for Pilot Voice, and at subsequent times as requested by Pilot, Customer agrees to provide Pilot with its (i) true, accurate, current, and complete business name, (ii) physical addresses where Voice Service will be used, (iii) 911 registered address for each applicable endpoint, (iv) a designated Account Administrator, and (v) user email addresses, phone numbers, and any other requested data which may be necessary to administer its Voice Service account (the “Account”) (collectively, “Registration Data”). Customer represents and warrants that the information it provides is accurate, current, and complete, and agrees to promptly update any of the information if it changes. If Customer provides Registration Data that is false, inaccurate, not current, incomplete, fraudulent, or otherwise unlawful, Pilot has the right, in its sole discretion, to suspend or terminate the Voice Services and refuse any and all current or future use of all Voice Services by Customer, its business(es), affiliates and all users of its Account. Upon provision of all Registration Data and acceptance of Customer’s Service Order, Pilot may provide Customer’s designated Account Administrator and other Pilot Voice users with, as applicable, administrator or user web portal logins and other Account information. Customer is solely liable for any transactions or activities by it or any third- party that occurs on its Account. Customer shall immediately notify Pilot of any unauthorized use of its Account or if any other breach of security has occurred. In no event shall Pilot be liable for any unauthorized, third-party use of your Account.
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.
NERC Registration If and to the extent any of the NTO’s facilities are NERC jurisdictional facilities, the ISO will register for certain NERC functions applicable to those NTO facilities. Such functions may include, without limitation, those functions designated by NERC to be “Reliability Coordinator” and “Balancing Authority” and “Transmission Planner” and “Planning Coordinator.” The Parties agree to negotiate in good faith the compliance obligations for the NERC functions applicable to, and to be performed by, each Party with respect to the NTO’s facilities. Notwithstanding the foregoing, the ISO shall register for the “Transmission Operator” function for all NTO Transmission Facilities under ISO Operational Control identified in Appendix A-1 of this Agreement.
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.
Abuse and Neglect of Children and Vulnerable Adults:
Abuse Registry Party agrees not to employ any individual, to use any volunteer or other service provider, or to otherwise provide reimbursement to any individual who in the performance of services connected with this agreement provides care, custody, treatment, transportation, or supervision to children or to vulnerable adults if there has been a substantiation of abuse or neglect or exploitation involving that individual. Party is responsible for confirming as to each individual having such contact with children or vulnerable adults the non-existence of a substantiated allegation of abuse, neglect or exploitation by verifying that fact though (a) as to vulnerable adults, the Adult Abuse Registry maintained by the Department of Disabilities, Aging and Independent Living and (b) as to children, the Central Child Protection Registry (unless the Party holds a valid child care license or registration from the Division of Child Development, Department for Children and Families). See 33 V.S.A. §4919(a)(3) and 33 V.S.A. §6911(c)(3).
Registration for E - Bidders 4.1. Parties who are interested to participate in public auction as (“E-Bidders”) may do so by logging on to the Auctioneer’s website and register as a user.
