Registrar and Registry Engagement teams. The Registrar and Registry Engagement teams provide access to specific expertise to properly advise the Event Director and facilitate work as warranted by the situation at hand.
Registrar and Registry Engagement teams Sample Clauses
Related to Registrar and Registry Engagement teams
Registrar and Transfer Agent To maintain, at its expense, a registrar and transfer agent for the Stock.
Registrar Data 1.6.1 Query format: whois “registrar Example Registrar, Inc.” 1.6.2 Response format: Registrar Name: Example Registrar, Inc. Street: 0000 Xxxxxxxxx Xxx City: Marina del Rey State/Province: CA Postal Code: 90292 Country: US Phone Number: +1.0000000000 Fax Number: +1.3105551213 Email: xxxxxxxxx@xxxxxxx.xxx WHOIS Server: whois.example-‐registrar.tld Referral URL: xxxx://xxx.xxxxxxx-‐registrar.tld Admin Contact: Xxx Registrar Phone Number: +1.3105551213 Fax Number: +1.3105551213 Email: joeregistrar@example-‐registrar.tld Admin Contact: Xxxx Registrar Phone Number: +1.3105551214 Fax Number: +1.3105551213 Email: janeregistrar@example-‐registrar.tld Technical Contact: Xxxx Geek Phone Number: +1.3105551215 Fax Number: +1.3105551216 Email: johngeek@example-‐registrar.tld >>> Last update of WHOIS database: 2009-‐05-‐29T20:15:00Z <<<
Registrar and Paying Agent The Company shall maintain an office or agency where Notes may be presented for registration of transfer or for exchange ("Registrar") and an office or agency where Notes may be presented for payment ("Paying Agent"). The Registrar shall keep a register of the Notes and of their transfer and exchange. The Company may appoint one or more co-registrars and one or more additional paying agents. The term "
Name, Office and Registered Agent The name of the Partnership is XXXXX Operating Partnership L.P. The specified office and principal place of business of the Partnership shall be 000 Xxxx Xxxxxx, Xxx Xxxx, Xxx Xxxx 00000. The General Partner may at any time change the location of such office, provided the General Partner gives notice to the Partners of any such change. The name and address of the Partnership’s registered agent is Intertrust Corporate Services Delaware Ltd., 000 Xxxxxxxx Xxxxxxx, Xxxxx 000, Xxxxxxxx Park Corporate Center, Xxxxxxxxxx, Xxxxxxxx, 00000. The sole duty of the registered agent as such is to forward to the Partnership any notice that is served on him as registered agent.
ICANN testing registrar Registry Operator agrees that ICANN will have a testing registrar used for purposes of measuring the SLRs described above. Registry Operator agrees to not provide any differentiated treatment for the testing registrar other than no billing of the transactions. ICANN shall not use the registrar for registering domain names (or other registry objects) for itself or others, except for the purposes of verifying contractual compliance with the conditions described in this Agreement. 1. Registry Operator will use only ICANN accredited registrars that are party to the Registrar Accreditation Agreement approved by the ICANN Board of Directors on 27 June 2013 in registering domain names. A list of such registrars shall be maintained by ICANN on ICANN’s website. 2. (Intentionally omitted. Registry Operator has not included commitments, statements of intent or business plans provided for in its application to ICANN for the TLD.) 3. Registry Operator agrees to perform the following specific public interest commitments, which commitments shall be enforceable by ICANN and through the Public Interest Commitment Dispute Resolution Process established by ICANN (posted at xxxx://xxx.xxxxx.xxx/en/resources/registries/picdrp), which may be revised in immaterial respects by ICANN from time to time (the “PICDRP”). Registry Operator shall comply with the PICDRP. Registry Operator agrees to implement and adhere to any remedies ICANN imposes (which may include any reasonable remedy, including for the avoidance of doubt, the termination of the Registry Agreement pursuant to Section 4.3(e) of the Agreement) following a determination by any PICDRP panel and to be bound by any such determination. a. Registry Operator will include a provision in its Registry-‐Registrar Agreement that requires Registrars to include in their Registration Agreements a provision prohibiting Registered Name Holders from distributing malware, abusively operating botnets, phishing, piracy, trademark or copyright infringement, fraudulent or deceptive practices, counterfeiting or otherwise engaging in activity contrary to applicable law, and providing (consistent with applicable law and any related procedures) consequences for such activities including suspension of the domain name. b. Registry Operator will periodically conduct a technical analysis to assess whether domains in the TLD are being used to perpetrate security threats, such as pharming, phishing, malware, and botnets. Registry Operator will maintain statistical reports on the number of security threats identified and the actions taken as a result of the periodic security checks. Registry Operator will maintain these reports for the term of the Agreement unless a shorter period is required by law or approved by ICANN, and will provide them to ICANN upon request. c. Registry Operator will operate the TLD in a transparent manner consistent with general principles of openness and non-‐discrimination by establishing, publishing and adhering to clear registration policies. d. Registry Operator of a “Generic String” TLD may not impose eligibility criteria for registering names in the TLD that limit registrations exclusively to a single person or entity and/or that person’s or entity’s “Affiliates” (as defined in Section 2.9(c) of the Registry Agreement). “Generic String” means a string consisting of a word or term that denominates or describes a general class of goods, services, groups, organizations or things, as opposed to distinguishing a specific brand of goods, services, groups, organizations or things from those of others.
Project Manager, County The County shall appoint a Project Manager to act as liaison between the County and the Subrecipient during the term of this Contract. The County’s Project Manager shall coordinate the activities of the County staff assigned to work with the Subrecipient.
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. 1.1. 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. 1.2. 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. 1.3. 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. 1.4. 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.
Labour Management Meetings The committee meeting shall normally be held every second month however, either party may call a meeting of the Joint Labour Management Committee. The meeting shall be held at a time and place fixed by mutual agreement but no later than fourteen (14) calendar days after the initial request, unless mutually agreed.
Registry Services “Registry Services” are, for purposes of the Agreement, defined as the following: (a) those services that are operations of the registry critical to the following tasks: the receipt of data from registrars concerning registrations of domain names and name servers; provision to registrars of status information relating to the zone servers for the TLD; dissemination of TLD zone files; operation of the registry DNS servers; and dissemination of contact and other information concerning domain name server registrations in the TLD as required by this Agreement; (b) other products or services that the Registry Operator is required to provide because of the establishment of a Consensus Policy as defined in Specification 1; (c) any other products or services that only a registry operator is capable of providing, by reason of its designation as the registry operator; and (d) material changes to any Registry Service within the scope of (a), (b) or (c) above.
Union/Management Meetings The Union Committee and the Senior Union Official of the Union, or her/his representative, shall, as occasion warrants, meet with the Committee on Labour Relations for the purpose of discussing and negotiating a speedy settlement of any grievance or dispute arising between the Employer and the employee concerned, including possible re-negotiations relative to this Agreement and the Schedules which are a part hereof. However, except for renegotiations of Agreements, these matters shall be introduced to such meetings only after the established grievance procedure has been followed. Grievances of a general nature may be initiated by a member of the Union Committee in step two of the grievance procedure outlined in Article 9.04.
