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 <<<
USE OF NASA NAME AND NASA EMBLEMS A. NASA Name and Initials Partner shall not use "National Aeronautics and Space Administration" or "NASA" in a way that creates the impression that a product or service has the authorization, support, sponsorship, or endorsement of NASA, which does not, in fact, exist. Except for releases under the "Release of General Information to the Public and Media" Article, Partner must submit any proposed public use of the NASA name or initials (including press releases and all promotional and advertising use) to the NASA Associate Administrator for the Office of Communications or designee ("NASA Communications") for review and approval. Approval by NASA Office of Communications shall be based on applicable law and policy governing the use of the NASA name and initials. B. NASA Emblems Use of NASA emblems (i.e., NASA Seal, NASA Insignia, NASA logotype, NASA Program Identifiers, and the NASA Flag) is governed by 14 C.F.R. Part 1221. Partner must submit any proposed use of the emblems to NASA Communications for review and approval.
Use of FIIOC’s and FSC's Name The Trust shall not use the name of FIIOC and FSC in any Prospectus, sales literature or other material relating to the Trust or any Fund of the Trust in a manner not consented to by FIIOC and FSC prior to use; provided, however, that FIIOC and FSC shall approve all uses of its name which merely refer in accurate terms to its appointments, duties or fees hereunder or which are required by the Securities and Exchange Commission ("SEC" or “Commission”) or a state securities commission; and further, provided that in no event shall such approval be unreasonably withheld.
Use of Customer Name Contractor may use County’s name without County’s prior written consent only in Contractor’s customer lists. Any other use of County’s name by Contractor must have the prior written consent of County.
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.
Use of Name and Logo The Trust agrees that it shall furnish to the Manager, prior to any use or distribution thereof, copies of all prospectuses, statements of additional information, proxy statements, reports to stockholders, sales literature, advertisements, and other material prepared for distribution to stockholders of the Trust or to the public, which in any way refer to or describe the Manager or which include any trade names, trademarks or logos of the Manager or of any affiliate of the Manager. The Trust further agrees that it shall not use or distribute any such material if the Manager reasonably objects in writing to such use or distribution within five (5) business days after the date such material is furnished to the Manager. The Manager and/or its affiliates own the names "Sierra", "Composite" and any other names which may be listed from time to time on a Schedule B to be attached hereto that they may develop for use in connection with the Trust, which names may be used by the Trust only with the consent of the Manager and/or its affiliates. The Manager, on behalf of itself and/or its affiliates, consents to the use by the Trust of such names or any other names embodying such names, but only on condition and so long as (i) this Agreement shall remain in full force, (ii) the Fund and the Trust shall fully perform, fulfill and comply with all provisions of this Agreement expressed herein to be performed, fulfilled or complied with by it, and (iii) the Manager is the manager of each Fund of the Trust. No such name shall be used by the Trust at any time or in any place or for any purposes or under any conditions except as provided in this section. The foregoing authorization by the Manager, on behalf of itself and/or its affiliates, to the Trust to use such names as part of a business or name is not exclusive of the right of the Manager and/or its affiliates themselves to use, or to authorize others to use, the same; the Trust acknowledges and agrees that as between the Manager and/or its affiliates and a Fund or the Trust, the Manager and/or its affiliates have the exclusive right so to use, or authorize others to use, such names, and the Trust agrees to take such action as may reasonably be requested by the Manager, on behalf of itself and/or its affiliates, to give full effect to the provisions of this section (including, without limitation, consenting to such use of such names). Without limiting the generality of the foregoing, the Trust agrees that, upon (i) any violation of the provisions of this Agreement by the Trust or (ii) any termination of this Agreement, by either party or otherwise, the Trust will, at the request of the Manager, on behalf of itself and/or its affiliates, made within six months after such violation or termination, use its best efforts to change the name of the Trust so as to eliminate all reference, if any, to such names and will not thereafter transact any business in a name containing such names in any form or combination whatsoever, or designate itself as the same entity as or successor to an entity of such names, or otherwise use such names or any other reference to the Manager and/or its affiliates, except as may be required by law. Such covenants on the part of the Trust shall be binding upon it, its Trustees, officers, shareholders, creditors and all other persons claiming under or through it. The provisions of this section shall survive termination of this Agreement.
FORMAT AND CONTENT FOR REGISTRY OPERATOR MONTHLY REPORTING Registry Operator shall provide one set of monthly reports per gTLD, using the API described in draft-‐xxxxxx-‐icann-‐registry-‐interfaces, see Specification 2, Part A, Section 9, reference 5, with the following content. ICANN may request in the future that the reports be delivered by other means and using other formats. ICANN will use reasonable commercial efforts to preserve the confidentiality of the information reported until three (3) months after the end of the month to which the reports relate. Unless set forth in this Specification 3, any reference to a specific time refers to Coordinated Universal Time (UTC). Monthly reports shall consist of data that reflects the state of the registry at the end of the month (UTC).
Publication of Registration Data Registry Operator shall provide public access to registration data in accordance with Specification 4 attached hereto (“Specification 4”).
Department of State Registration Consistent with Title XXXVI, F.S., the Contractor and any subcontractors that assert status, other than a sole proprietor, must provide the Department with conclusive evidence of a certificate of status, not subject to qualification, if a Florida business entity, or of a certificate of authorization if a foreign business entity.
No Reliance on Administrative Agent’s Customer Identification Program Each Lender acknowledges and agrees that neither such Lender, nor any of its Affiliates, participants or assignees, may rely on the Administrative Agent to carry out such Lender’s, Affiliate’s, participant’s or assignee’s customer identification program, or other obligations required or imposed under or pursuant to the USA Patriot Act or the regulations thereunder, including the regulations contained in 31 CFR 103.121 (as hereafter amended or replaced, the “CIP Regulations”), or any other Anti-Terrorism Law, including any programs involving any of the following items relating to or in connection with any of the Loan Parties, their Affiliates or their agents, the Loan Documents or the transactions hereunder or contemplated hereby: (i) any identity verification procedures, (ii) any recordkeeping, (iii) comparisons with government lists, (iv) customer notices or (v) other procedures required under the CIP Regulations or such other Laws.
