Updating a proposal database

1.6 "Personal Data" refers to data about any identified or identifiable natural person.1.7 "Registered Name" refers to a domain name within the domain of a TLD that is the subject of an appendix to this Agreement, whether consisting of two (2) or more (e.g., john.smith.name) levels, about which a TLD Registry Operator (or an affiliate engaged in providing Registry Services) maintains data in a Registry Database, arranges for such maintenance, or derives revenue from such maintenance.3.3.3 Registrar may subcontract its obligation to provide the public access described in Subsection 3.3.1 and the updating described in Subsection 3.3.2, provided that Registrar shall remain fully responsible for the proper provision of the access and updating.3.3.4 Registrar shall abide by any ICANN specification or policy established as a Consensus Policy according to Section 4 that requires registrars to cooperatively implement a distributed capability that provides query-based Whois search functionality across all registrars.Such media include but are not limited to e-mail, telephone, facsimile, postal mail, SMS, and wireless alerts.

For additional information about this waiver, see the ICANN blog (https:// and the RAA Insurance Waiver FAQs [https:// For purposes of this Agreement, the following definitions shall apply: 1.1 "Accredit" means to identify and set minimum standards for the performance of registration functions, to recognize persons or entities meeting those standards, and to enter into an accreditation agreement that sets forth the rules and procedures applicable to the provision of Registrar Services.1.13 "Registry Database" means a database comprised of data about one or more DNS domain names within the domain of a registry that is used to generate either DNS resource records that are published authoritatively or responses to domain-name availability lookup requests or Whois queries, for some or all of those names.1.14 A "Registry Operator" is the person or entity then responsible, in accordance with an agreement between ICANN (or its assignee) and that person or entity (those persons or entities) or, if that agreement is terminated or expires, in accordance with an agreement between the US Government and that person or entity (those persons or entities), for providing Registry Services for a specific TLD.Unless and until ICANN establishes a different policy according to Section 4, Registrar shall permit use of data it provides in response to queries for any lawful purposes except to: (a) allow, enable, or otherwise support the transmission by e-mail, telephone, or facsimile of mass, unsolicited, commercial advertising or solicitations to entities other than the data recipient's own existing customers; or (b) enable high volume, automated, electronic processes that send queries or data to the systems of any Registry Operator or ICANN-Accredited registrar, except as reasonably necessary to register domain names or modify existing registrations.3.3.6 In addition, Registrar shall provide third-party bulk access to the data subject to public access under Subsection 3.3.1 under the following terms and conditions: 3.3.6.1 Registrar shall make a complete electronic copy of the data available at least one (1) time per week for download by third parties who have entered into a bulk access agreement with Registrar.

Leave a Reply