Public Comments and ICANN Response Sample Clauses

Public Comments and ICANN Response. On February 18, 2009, ICANN published a 154-page analysis of the more than 300 comments it received in the seven public comment forums concerning the first draft of the DAG.10 This analysis was published in conjunction with the second draft of the DAG. The analysis divided the comments into thirteen categories and multiple sub-categories. For each category, ICANN provided: • A summary of the key points; • A summary of the comments; • A list of the main issues raised; • An analysis of these issues; and • Its proposed position (as reflected in the second version of the DAG, published concurrently with the analysis). Articles and blog posts published by followers of the gTLD process during this public comment period pointed to the fact that multiple companies and the United States government opposed the expansion of new gTLDs.11 ICANN responded to this criticism by pointing to the GNSO policy recommendations on new gTLDs, which underwent multiple public comment periods and discussions with a variety of stakeholders and were 8 ICANN, “Comparison between gTLD Agreements from 2005-2007 and Draft Base Registry Agreement for New gTLDs," December 3, 2008, xxxx://xxx.xxxxx.xxx/en/topics/new-gtlds/draft-agreement-annotated- comparison-03dec08-en.pdf. 9 Xxxxxxx Xxxxxx, “ICANN’s gTLD Proposal Hits a Wall: Now What? ," Circle ID, December 23, 2008, xxxx://xxx.xxxxxxxx.xxx/posts/icann_gtld_proposal_hits_wall_now_what/.. 10 ICANN, “New gTLD Draft Applicant Guidebook: Analysis of Public Comment," February 18, 2009, xxxx://xxx.xxxxx.xxx/en/topics/new-gtlds/agv1-analysis-public-comments-18feb09-en.pdf. 11 Xxxx Xxxxxx, “ICANN plan for new TLDs comes under barrage of criticism," Ars Technica, December 16, 2008, xxxx://xxxxxxxxxxx.xxx/security/news/2008/12/icann-plan-for-new-tlds-comes-under-barrage-of- criticism.ars. See also Xxxxxxx Xxxxxx, “ICANN’s gTLD Proposal Hits a Wall: Now What? ," Circle ID, December approved by a supermajority within the GNSO. Annex A of ICANN’s Bylaws, which governs the GNSO policy development process, states that “the Board shall adopt the policy according to the GNSO Supermajority Vote recommendation unless by a vote of more than sixty-six (66%) percent of the Board determines that such policy is not in the best interests of the ICANN community or ICANN.”12 In addition, ICANN commits in its Bylaws to “introducing and promoting competition in the registration of domain names where practicable and beneficial in the public interest.”13 While certain ...
AutoNDA by SimpleDocs
Public Comments and ICANN Response. On May 31, 2009, ICANN staff published an analysis of comments on the second draft of the DAG. This analysis was published concurrently with a series of revised excerpts from the DAG; in the analysis, ICANN promised to publish the third draft of the DAG after its June 2009 meeting. As with the first analysis of comments, ICANN staff separated the comments into categories and provided a list of key points, a summary of input, an analysis of the major issues raised, and a proposed position for each category. 16
Public Comments and ICANN Response. ICANN published an analysis of the comments it received on the revised excerpts of the DAG on October 4, 2009, in conjunction with the third draft of the DAG.21 These comments included specific criticisms of the way ICANN was incorporating public participation in the development of the new gTLD program:
Public Comments and ICANN Response. ICANN published an analysis of the public comments on version three of the DAG on February 15, 2010.23
Public Comments and ICANN Response. Separate analyses were published for each public comment forum (10 in all) on May 28, 2009.25 Xxxxxx xxx Xxxxxxxxx of Minds + Machines highlighted several key areas of change in version four of the DAG that raise questions related to public participation: • At the March 2010 ICANN meeting in Nairobi, the ICANN Board voted to maintain vertical separation between registries and registrars. This is reflected in the fourth version of the DAG, though it is subject to change in accordance with the recommendations of the GNSO working group on vertical integration. Xxx Xxxxxxxxx points out that this working group consists “almost wholly of registrars and registries aiming 23 ICANN, “New gTLD Draft Applicant Guidebook Version 3: Public Comments Summary and Analysis," February 15, 2010, xxxx://xxx.xxxxx.xxx/en/topics/new-gtlds/summary-analysis-agv3-15feb10-en.pdf.
Public Comments and ICANN Response. ICANN has not yet published its analysis of public comments on the fourth version of the DAG. The public comment forum for the guidebook as a whole contains 125 e-mails, while the six individual module forums contain a total of 25 additional e-mails.29 26 ICANN, “Vertical Integration PDP,” xxxxx://xx.xxxxx.xxx/vert-integration- pdp/index.cgi?https_st_icann_org_vert_integration_pdp_index_cgi_vi_resources. 27 Xxxxxx xxx Xxxxxxxxx, “Latest Version of ICANN’s Applicant Guidebook – DAG4," Minds + Machines, June 1, 2010, xxxx://xxx.xxxxxxxxxxxxxxxx.xxx/2010/06/latest-version-of-icanns-applicant-guidebook-dag4/.

Related to Public Comments and ICANN Response

  • Lobbying Activities - Standard Form - LLL No response Do not upload this form unless Vendor has reportable lobbying activities. There are Attributes entitled, “2 CFR Part 200 or Federal Provision - Xxxx Anti-Lobbying Amendment – Continued.” Properly respond to those Attributes and only upload this form if applicable/instructed. If upload is required based on your response to those Attributes, the Disclosure of Lobbying Activities – Standard Form - LLL must be downloaded from the “Attachments” section of the IonWave eBid System, reviewed, properly completed, and uploaded to this location.

  • Supplemental Vendor Information Only) No response Optional. If Vendor desires that their logo be displayed on their public TIPS profile for TIPS and TIPS Member viewing, Vendor may upload that logo at this location. These supplemental documents shall not be considered part of the TIPS Contract. Rather, they are Vendor Supplemental Information for marketing and informational purposes only. Some participating public entities are required to seek Disadvantaged/Minority/Women Business & Federal HUBZone ("D/M/WBE/Federal HUBZone") vendors. Does Vendor certify that their entity is a D/M/WBE/Federal HUBZone vendor? If you respond "Yes," you must upload current certification proof in the appropriate "Response Attachments" location. NO Some participating public entities are required to seek Historically Underutilized Business (HUB) vendors as defined by the Texas Comptroller of Public Accounts Statewide HUB Program. Does Vendor certify that their entity is a HUB vendor? If you respond "Yes," you must upload current certification proof in the appropriate "Response Attachments" location. No Can the Vendor provide its proposed goods and services to all 50 US States? No

  • General Responsibilities of the Parties 1. The Parties will work together in a spirit of cooperation and partnership, with the responsibilities and accountabilities set out in this Agreement, to implement the Programme Documents in full in a timely, efficient, and effective, manner. 2. The Parties agree to carry out their respective responsibilities in accordance with the provisions of this Agreement, including the Programme Documents. 3. The Parties shall keep each other informed of all relevant activities pertaining to the implementation of the Programme Documents, and shall hold consultations when either Party considers it appropriate, including any circumstance that may affect the achievement of the results of the Programme and the Programme Documents. 4. The Parties shall fulfill their commitments with the fullest regard for the terms and conditions of this Agreement and the principles of the United Nations.

  • Workplace Violence Prevention and Crisis Response (applicable to any Party and any subcontractors and sub-grantees whose employees or other service providers deliver social or mental health services directly to individual recipients of such services): Party shall establish a written workplace violence prevention and crisis response policy meeting the requirements of Act 109 (2016), 33 VSA §8201(b), for the benefit of employees delivering direct social or mental health services. Party shall, in preparing its policy, consult with the guidelines promulgated by the U.S. Occupational Safety and Health Administration for Preventing Workplace Violence for Healthcare and Social Services Workers, as those guidelines may from time to time be amended. Party, through its violence protection and crisis response committee, shall evaluate the efficacy of its policy, and update the policy as appropriate, at least annually. The policy and any written evaluations thereof shall be provided to employees delivering direct social or mental health services. Party will ensure that any subcontractor and sub-grantee who hires employees (or contracts with service providers) who deliver social or mental health services directly to individual recipients of such services, complies with all requirements of this Section.

  • Vendor Logo (Supplemental Vendor Information Only) No response Optional. If Vendor desires that their logo be displayed on their public TIPS profile for TIPS and TIPS Member viewing, Vendor may upload that logo at this location. These supplemental documents shall not be considered part of the TIPS Contract. Rather, they are Vendor Supplemental Information for marketing and informational purposes only. Some participating public entities are required to seek Disadvantaged/Minority/Women Business & Federal HUBZone ("D/M/WBE/Federal HUBZone") vendors. Does Vendor certify that their entity is a D/M/WBE/Federal HUBZone vendor? If you respond "Yes," you must upload current certification proof in the appropriate "Response Attachments" location. NO Some participating public entities are required to seek Historically Underutilized Business (HUB) vendors as defined by the Texas Comptroller of Public Accounts Statewide HUB Program. Does Vendor certify that their entity is a HUB vendor? If you respond "Yes," you must upload current certification proof in the appropriate "Response Attachments" location. No Can the Vendor provide its proposed goods and services to all 50 US States? Yes

  • General Responsibilities Issuer hereby engages Distributor to act as exclusive distributor of the shares of each class of the Funds. The Funds subject to this Agreement as of the date hereof are identified on SCHEDULE A, which may be amended from time to time in accordance with Section 11 below. Sales of a Fund's shares shall be made only to investors residing in those states in which such Fund is registered. After effectiveness of each Fund’s registration statement, Distributor will hold itself available to receive, as agent for the Fund, and will receive by mail, telex, telephone, or such other method as may be agreed upon between Distributor and Issuer, orders for the purchase of Fund shares, and will accept or reject such orders on behalf of the Fund in accordance with the provisions of the applicable Fund’s prospectus. Distributor will be available to transmit orders, as promptly as possible after it accepts such orders, to the Fund’s transfer agent for processing at the shares’ net asset value next determined in accordance with the prospectuses.

  • Mutual Responsibilities It is recognized by this Agreement to be the duty of the Company to explain fully the terms of this Agreement to all its officers, foremen and others engaged in a supervisory capacity and it is recognized to be the duty of the Union to explain fully to its members, its and their responsibilities and obligations under this Agreement.

  • Amendments and Supplements to Permitted Section 5(d) Communications If at any time following the distribution of any Permitted Section 5(d) Communication, there occurred or occurs an event or development as a result of which such Permitted Section 5(d) Communication included or would include an untrue statement of a material fact or omitted or would omit to state a material fact necessary in order to make the statements therein, in the light of the circumstances existing at that subsequent time, not misleading, the Company will promptly notify the Representatives and will promptly amend or supplement, at its own expense, such Permitted Section 5(d) Communication to eliminate or correct such untrue statement or omission.

  • Contractor’s General Responsibilities The Contractor, regardless of any delegation or subcontract entered by the Contractor, shall be responsible for the following when providing information technology staff augmentation services: 3.1 The Contractor is responsible for the comprehensive management of Staff. Staff shall not be deemed an employee of the State or deemed to be entitled to any benefits associated with such employment and the Contractor shall be responsible for the administration and maintenance of all employment and payroll records, payroll processing, remittance of payroll and taxes, and all administrative tasks required by state and federal law associated with payment of Staff. 3.2 The Contractor shall provide Staff in accordance with Customer Requests for Quote (RFQ), and as described in Contract Exhibit J, Job Family Descriptions document. Customers may include detailed scopes of work, specific requirements of the work to be performed, and any requirements of Staff within the Request for Quote. 3.3 The Contractor shall possess the professional and technical staff necessary to allocate, outsource, and manage qualified Staff to perform the services requested by the Customer. 3.4 The Contractor shall provide Customers with Staff who have sufficient skill and experience to perform the services assigned to them. 3.5 The Contractor is responsible for ensuring that all information technology staff augmentation services furnished under the Contract meet the professional standards and quality that prevails among information technology professionals in the same discipline and of similar knowledge and skill engaged in related work throughout Florida under the same or similar circumstances. 3.6 The Contractor shall provide, at its own expense, training necessary for keeping Contractor’s Staff abreast of industry advances and for maintaining proficiency in equipment and systems that are available on the commercial market. 3.7 The Contractor shall, at its own expense, be responsible for adhering to the Contract background screening requirements, testing, evaluations, advertising, recruitment, and disciplinary actions of Contractor’s Staff. 3.8 The Contractor, throughout the term of the Contract, shall maintain all licenses, permits, qualifications, insurance, and approvals of whatever nature that are legally required for Contractor and Staff to perform the information technology staff augmentation services. 3.9 Contractor shall be responsible for all costs associated with the administration of this Contract. 3.10 The Contractor shall adhere to all work policies, procedures, and standards established by the Department and Customer. 3.11 The Contractor shall ensure that Staff conform with the Customer’s policies in all respects while on the Customer’s premises, and is responsible for obtaining all rules, regulations, policies, etc. 3.12 Contractor shall only provide information technology staff augmentation services for those Job Titles awarded to the Contractor and shall be paid on an hourly basis. Contracts resulting from this solicitation should not be structured as fixed-price agreements or used for any services requiring authorization for payment of milestone tasks.

  • General Responsibility The Consultant shall, at all times during the Agreement, remain responsible. The Consultant agrees, if requested by the Commissioner of NYSDOT or his or her designee, to present evidence of its continuing legal authority to do business in New York State, integrity, experience, ability, prior performance, and organizational and financial capacity.

Draft better contracts in just 5 minutes Get the weekly Law Insider newsletter packed with expert videos, webinars, ebooks, and more!