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.
Indemnification for Marketing Materials In addition to the foregoing indemnification, the Fund and the Investment Adviser also, jointly and severally, agree to indemnify and hold harmless each Underwriter, affiliates, directors, officers, employees and agents of each Underwriter, and each person, if any, who controls any Underwriter within the meaning of Section 15 of the 1933 Act or Section 20 of the 1934 Act, against any and all loss, liability, claim, damage and expense described in the indemnity contained in Section 6(a), as limited by the proviso set forth therein, with respect to any sales material.
EPP query-‐command RTT Refers to the RTT of the sequence of packets that includes the sending of a query command plus the reception of the EPP response for only one EPP query command. It does not include packets needed for the start or close of either the EPP or the TCP session. EPP query commands are those described in section 2.9.2 of EPP RFC 5730. If the RTT is 5-‐times or more the corresponding SLR, the RTT will be considered undefined.
Registration Compliance; No Stop Order No order suspending the effectiveness of the Registration Statement shall be in effect, and no proceeding for such purpose, pursuant to Rule 401(g)(2) or pursuant to Section 8A under the Securities Act shall be pending before or threatened by the Commission; the Prospectus and each Issuer Free Writing Prospectus shall have been timely filed with the Commission under the Securities Act (in the case of an Issuer Free Writing Prospectus, to the extent required by Rule 433 under the Securities Act) and in accordance with Section 4(a) hereof; and all requests by the Commission for additional information shall have been complied with to the reasonable satisfaction of the Representatives.
Registration Compliance; No Stop Orders The Registration Statement has become effective under the Securities Act, and no stop order suspending the effectiveness of the Registration Statement or any part thereof, preventing or suspending the use of any Preliminary Prospectus, the Prospectus or any Permitted Free Writing Prospectus or any part thereof shall have been issued and no proceedings for that purpose or pursuant to Section 8A under the Securities Act shall have been initiated or threatened by the Commission, and all requests for additional information on the part of the Commission (to be included in the Registration Statement or the Prospectus or otherwise) shall have been complied with to the reasonable satisfaction of the Representative; the Rule 462(b) Registration Statement, if any, and the Prospectus shall have been filed with the Commission within the applicable time period prescribed for such filing by, and in compliance with, the Rules and Regulations and in accordance with Section 4(a) of this Agreement, and the Rule 462(b) Registration Statement, if any, shall have become effective immediately upon its filing with the Commission; and FINRA shall have raised no unresolved objection to the fairness and reasonableness of the terms of this Agreement or the transactions contemplated hereby.
Commercialization Plan At such times as the JGC will deem appropriate, the JGC will direct the Parties to mutually prepare a Worldwide Commercialization Plan, and the JGC will review and approve such initial Worldwide Commercialization Plan. Thereafter, the JGC will have one or the other Party (or both) update the Worldwide Commercialization Plan each calendar year, and the JGC will review and approve any such update or any other amendment to the Worldwide Commercialization Plan. Notwithstanding anything in this CCPS Agreement to the contrary, the Parties acknowledge and agree that (i) Bluebird may decline to perform any Commercialization activity proposed to be conducted by Bluebird in the Worldwide Commercialization Plan (other than Manufacturing of Vectors and associated Payloads), and (ii) the Worldwide Commercialization Plan will not include, and Bluebird will have no obligation to perform, any such Commercialization activity that Bluebird has declined to perform, provided that once Bluebird has agreed to perform a Commercialization activity, it will be obligated to perform, and cannot decline to perform, such activity. In addition, either Party may request at any time that the JGC consider and approve other updates to the Worldwide Commercialization Plan. Further:
(a) The JGC will set the required form and contents of the Worldwide Commercialization Plan. The Worldwide Commercialization Plan will reflect a singular marketing and sales approach worldwide, and will specify, among other things, the number of sales reps in the U.S. for each Party, allocation of regions in the U.S. for each Parties’ sales force, creation of marketing materials, planning for conferences, and other marketing activities. CERTAIN CONFIDENTIAL PORTIONS OF THIS EXHIBIT WERE OMITTED AND REPLACED WITH “[***]”. A COMPLETE VERSION OF THIS EXHIBIT HAS BEEN FILED SEPARATELY WITH THE SECRETARY OF THE SECURITIES AND EXCHANGE COMMISSION PURSUANT TO AN APPLICATION REQUESTING CONFIDENTIAL TREATMENT PURSUANT TO RULE 406 PROMULGATED UNDER THE SECURITIES ACT OF 1933, AS AMENDED.
(b) Neither Party (itself or by or through any others, including any Affiliates or Sublicensees) will take any material action regarding the Commercialization of Licensed Product unless described in the Worldwide Commercialization Plan or approved by the JGC.
(c) All Commercialization of Licensed Product for U.S. Administration will be conducted under the supervision of the JGC and as part of the U.S. Development & Commercialization Program.
(d) Celgene will have final decision making authority for all Commercialization activities worldwide, including timing of launch and pricing and the Worldwide Development Plan.
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.
Supported Initial and Renewal Registration Periods a. Initial registrations of Registered Names (where available according to functional specifications and other requirements) may be made in the registry for terms of up to ten years.
b. Renewal registrations of Registered Names (where available according to functional specifications and other requirements) may be made in the registry for terms not exceeding a total of ten years.
c. Upon change of sponsorship of the registration of a Registered Name from one registrar to another, according to Part A of the ICANN Policy on Transfer of Registrations between Registrars, the term of registration of the Registered Name shall be extended by one year, provided that the maximum term of the registration as of the effective date of the sponsorship change shall not exceed ten years.
d. The change of sponsorship of registration of Registered Names from one registrar to another, according to Part B of the ICANN Policy on Transfer of Registrations between Registrars shall not result in the extension of the term of the registration and Registry Operator may assist in such change of sponsorship.
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.
Updated Information Submission by Interconnection Customer The updated information submission by the Interconnection Customer, including manufacturer information, shall occur no later than one hundred eighty (180) Calendar Days prior to the Trial Operation. The Interconnection Customer shall submit a completed copy of the Electric Generating Unit data requirements contained in Appendix 1 to the LGIP. It shall also include any additional information provided to the Participating TO and the CAISO for the Interconnection Studies. Information in this submission shall be the most current Electric Generating Unit design or expected performance data. Information submitted for stability models shall be compatible with the Participating TO and CAISO standard models. If there is no compatible model, the Interconnection Customer will work with a consultant mutually agreed to by the Parties to develop and supply a standard model and associated information.
