Steve, “consistent with 1.1 (c ) doesn’t hit the mark because 1.1(a) is an exception to 1.1 (c). So the question is more properly phrased to ask how this is consistent with the “express scope of 1.1(a) of the ByLaws as required by 1.1(c)” or something like that. In other words, it’s just confusing to refer to 1.1(c) without acknowledging the exception in 1.1(c) to 1.1(a). Anne Anne E. Aikman-Scalese Of Counsel 520.629.4428 office 520.879.4725 fax AAikman@lrrc.com<mailto:AAikman@lrrc.com> _____________________________ [cid:image001.png@01D2C2A4.14DD05A0] Lewis Roca Rothgerber Christie LLP One South Church Avenue, Suite 700 Tucson, Arizona 85701-1611 lrrc.com<http://lrrc.com/> From: Steve Chan [mailto:steve.chan@icann.org] Sent: Monday, May 01, 2017 5:39 PM To: Aikman-Scalese, Anne; gnso-newgtld-wg@icann.org Subject: Re: [Ext] RE: [Gnso-newgtld-wg] Proposed Agenda: New gTLD Subsequent Procedures Working Group, 2 May 2017 at 03:00 UTC Dear Anne, If I am understanding your comment/suggestion properly, staff has attempted to incorporate the issues raised by you and Kristina Rosette in the last sentence of the comments to Recommendation 14. I’ve extracted that sentence for your consideration here: “Finally, it would be helpful if the CCT-RT would clarify how the reference to “relationship of content of a gTLD to its name” is consistent with Section 1.1(c) of the ICANN Bylaws.” If you do not feel that this sentence adequately captures your concerns, you can suggest updated text in the Google doc directly and/or discuss the topic during the upcoming call. Best, Steve From: "Aikman-Scalese, Anne" <AAikman@lrrc.com<mailto:AAikman@lrrc.com>> Date: Monday, May 1, 2017 at 5:05 PM To: Steve Chan <steve.chan@icann.org<mailto:steve.chan@icann.org>>, "gnso-newgtld-wg@icann.org<mailto:gnso-newgtld-wg@icann.org>" <gnso-newgtld-wg@icann.org<mailto:gnso-newgtld-wg@icann.org>> Subject: [Ext] RE: [Gnso-newgtld-wg] Proposed Agenda: New gTLD Subsequent Procedures Working Group, 2 May 2017 at 03:00 UTC Thank you. Regarding the proposed change to the comments as to Recommendation 14, I think this question would have to be rephrased to ask how the Recommendation fits within the Mission specified in 1.1 (a). The reason for this is that the big “carve-out” from 1.1 (c) is the “express scope of Section 1.1(a)”: [cid:image005.png@01D2C2A4.14AE5480] So it seems the question in the draft comment to Recommendation 14 would have to be “How is this recommendation consistent with the express scope of ICANN’s Mission as set forth in Section 1.1(a) of the ByLaws?” The draft comment currently says: “On the 10 April WG call, members of the CCT-RT provided additional context for this recommendation. According to the CCT-RT members, research findings indicate that end users expect to see a relationship between TLDs and the meaning of the string and/or usage of associated domains. It seems that the spirit of this recommendation is to create incentives to encourage that correlation, so as to promote user trust.” Section 1.1(a) of the ByLaws provides: Section 1.1. MISSION (a) The mission of the Internet Corporation for Assigned Names and Numbers (“ICANN”) is to ensure the stable and secure operation of the Internet’s unique identifier systems as described in this Section 1.1(a) (the “Mission”). Specifically, ICANN: (i) Coordinates the allocation and assignment of names in the root zone of the Domain Name System (“DNS”) and coordinates the development and implementation of policies concerning the registration of second-level domain names in generic top-level domains (“gTLDs”). In this role, ICANN’s scope is to coordinate the development and implementation of policies: • For which uniform or coordinated resolution is reasonably necessary to facilitate the openness, interoperability, resilience, security and/or stability of the DNS including, with respect to gTLD registrars and registries, policies in the areas described in Annex G-1 and Annex G-2; and • That are developed through a bottom-up consensus-based multistakeholder process and designed to ensure the stable and secure operation of the Internet’s unique names systems. Anne E. Aikman-Scalese Of Counsel 520.629.4428 office 520.879.4725 fax AAikman@lrrc.com<mailto:AAikman@lrrc.com> _____________________________ [cid:image006.png@01D2C2A4.14AE5480] Lewis Roca Rothgerber Christie LLP One South Church Avenue, Suite 700 Tucson, Arizona 85701-1611 lrrc.com[lrrc.com]<https://urldefense.proofpoint.com/v2/url?u=http-3A__lrrc.com_&d=DwMGaQ&c=FmY...> From: gnso-newgtld-wg-bounces@icann.org<mailto:gnso-newgtld-wg-bounces@icann.org> [mailto:gnso-newgtld-wg-bounces@icann.org] On Behalf Of Steve Chan Sent: Monday, May 01, 2017 4:35 PM To: gnso-newgtld-wg@icann.org<mailto:gnso-newgtld-wg@icann.org> Subject: Re: [Gnso-newgtld-wg] Proposed Agenda: New gTLD Subsequent Procedures Working Group, 2 May 2017 at 03:00 UTC Dear WG Members, Staff has attempted to incorporate suggestions and guidance received during the last WG call on the draft response to the CCT-RT (see agenda item 4 below). You can see the edits in the Google doc here https://docs.google.com/document/d/1LC-1-Z2auN2XTSJXyW34eWnGgNuuDInIOeJ1TcZ7z58/edit?usp=sharing[docs.google.com]<https://urldefense.proofpoint.com/v2/url?u=https-3A__docs.google.com_document_d_1LC-2D1-2DZ2auN2XTSJXyW34eWnGgNuuDInIOeJ1TcZ7z58_edit-3Fusp-3Dsharing&d=DwMGaQ&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=UAy6fqdE7uFkRCc7uzN4yui8bwTtqofadZHiQEIO1vw&m=7XCgy-sGAnaq6gXu1XoRIK4nJVHzJ4UXCtmA2qEz4Rc&s=Rih_Sd5AE7o7Gi759uWbrF3Iv6dZST05MTkCB4I57i0&e=> or in the attached Word doc, for those that may have issues accessing a Google doc. Best, Steve From: <gnso-newgtld-wg-bounces@icann.org<mailto:gnso-newgtld-wg-bounces@icann.org>> on behalf of Steve Chan <steve.chan@icann.org<mailto:steve.chan@icann.org>> Date: Friday, April 28, 2017 at 1:58 PM To: "gnso-newgtld-wg@icann.org<mailto:gnso-newgtld-wg@icann.org>" <gnso-newgtld-wg@icann.org<mailto:gnso-newgtld-wg@icann.org>> Subject: [Gnso-newgtld-wg] Proposed Agenda: New gTLD Subsequent Procedures Working Group, 2 May 2017 at 03:00 UTC Dear WG Members, Below, please find the proposed agenda for the New gTLD Subsequent Procedures WG meeting scheduled for Monday, 2 May 2017 at 03:00 UTC for 90 minutes. 1. Welcome/review agenda 2. SOIs 3. Work Track Updates 4. Second Reading - Review of draft response to the Competition, Consumer Trust & Consumer Choice Review Team (CCT-RT) - available here https://docs.google.com/document/d/1LC-1-Z2auN2XTSJXyW34eWnGgNuuDInIOeJ1TcZ7z58/edit?usp=sharing[docs.google.com]<https://urldefense.proofpoint.com/v2/url?u=https-3A__docs.google.com_document_d_1LC-2D1-2DZ2auN2XTSJXyW34eWnGgNuuDInIOeJ1TcZ7z58_edit-3Fusp-3Dsharing&d=DwMGaQ&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=UAy6fqdE7uFkRCc7uzN4yui8bwTtqofadZHiQEIO1vw&m=7XCgy-sGAnaq6gXu1XoRIK4nJVHzJ4UXCtmA2qEz4Rc&s=Rih_Sd5AE7o7Gi759uWbrF3Iv6dZST05MTkCB4I57i0&e=> 5. Update on Drafting Teams 6. AOB If you need a dial-out or want to send an apology, please email gnso-secs@icann.org<mailto:gnso-secs@icann.org>. Best, Steve Steven Chan Sr. Policy Manager ICANN 12025 Waterfront Drive, Suite 300 Los Angeles, CA 90094-2536 steve.chan@icann.org<mailto:steve.chan@icann.org> mobile: +1.310.339.4410 office tel: +1.310.301.5800 office fax: +1.310.823.8649 Find out more about the GNSO by taking our interactive courses<applewebdata://310CAD3E-E244-4690-A938-C2655DD44BDE/learn.icann.org/courses/gnso> and visiting the GNSO Newcomer pages[gnso.icann.org]<https://urldefense.proofpoint.com/v2/url?u=http-3A__gnso.icann.org_sites_gns...>. Follow @GNSO on Twitter: https://twitter.com/ICANN_GNSO[twitter.com]<https://urldefense.proofpoint.com/v2/url?u=https-3A__twitter.com_ICANN-5FGNSO&d=DwMGaQ&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=UAy6fqdE7uFkRCc7uzN4yui8bwTtqofadZHiQEIO1vw&m=7XCgy-sGAnaq6gXu1XoRIK4nJVHzJ4UXCtmA2qEz4Rc&s=s6kC5ODL4KchT-jgc_yLovPDUH14rScZgmzdKyZvMcg&e=> Follow the GNSO on Facebook: https://www.facebook.com/icanngnso/[facebook.com]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.facebook.com_icanngnso_&d=DwMGaQ&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=UAy6fqdE7uFkRCc7uzN4yui8bwTtqofadZHiQEIO1vw&m=7XCgy-sGAnaq6gXu1XoRIK4nJVHzJ4UXCtmA2qEz4Rc&s=Paj-XEADdwR0omPGBdkhbfhoqX3KTzk7g87b8CJp98Q&e=> http://gnso.icann.org/en/[gnso.icann.org]<https://urldefense.proofpoint.com/v2/url?u=http-3A__gnso.icann.org_en_&d=DwMGaQ&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=UAy6fqdE7uFkRCc7uzN4yui8bwTtqofadZHiQEIO1vw&m=7XCgy-sGAnaq6gXu1XoRIK4nJVHzJ4UXCtmA2qEz4Rc&s=5smvGrOuCrUsGLyHE8eAmGaLU46uti_lbSQijXsK5Do&e=> ________________________________ This message and any attachments are intended only for the use of the individual or entity to which they are addressed. If the reader of this message or an attachment is not the intended recipient or the employee or agent responsible for delivering the message or attachment to the intended recipient you are hereby notified that any dissemination, distribution or copying of this message or any attachment is strictly prohibited. If you have received this communication in error, please notify us immediately by replying to the sender. The information transmitted in this message and any attachments may be privileged, is intended only for the personal and confidential use of the intended recipients, and is covered by the Electronic Communications Privacy Act, 18 U.S.C. §2510-2521. ________________________________ This message and any attachments are intended only for the use of the individual or entity to which they are addressed. If the reader of this message or an attachment is not the intended recipient or the employee or agent responsible for delivering the message or attachment to the intended recipient you are hereby notified that any dissemination, distribution or copying of this message or any attachment is strictly prohibited. If you have received this communication in error, please notify us immediately by replying to the sender. The information transmitted in this message and any attachments may be privileged, is intended only for the personal and confidential use of the intended recipients, and is covered by the Electronic Communications Privacy Act, 18 U.S.C. §2510-2521.
