FYI -ed The latest edition is now available. New gTLD Subsequent Procedures PDP March 2020 Newsletter CURRENT STATUS In March, the Working Group focused on reviewing draft final recommendations <http://r20.rs6.net/tn.jsp?f=0012o43qFtByCzXTlyp2V1JdJzK09-9R4y1oPVvCuXRIhAaMTlz2IhXN3kqaJLO7WuZn3l7aXlX8m9BUoCLiSZ7gcbIqa639w3kmtVDEFy2VrE9xrWf5uJRA8x10njQ34OhtRwasjc-N0k3adXo4M4B0bWuzU9CqMqXjnJ7oSMnOCyE52598gbPdEeY7uQKXgIpeF4ExV80MY8CJjW7lLovUuB4WmTNPyepWgZAXgrg3U0=&c=sCUQFj-kH9b2XBY_2r1_zFnWcDEVJpKSwfoc8ze89YGoSekV12XdSQ==&ch=tjunA6750DOFha4BTAHzsZ-pyISDlTsfH2Bpje19R0OBI950UNGBPw==>** on a topic-by-topic basis. The meetings in March focused on recommendations for the following topics: - 2 March <http://r20.rs6.net/tn.jsp?f=0012o43qFtByCzXTlyp2V1JdJzK09-9R4y1oPVvCuXRIhAaM...>: Registrant Protections, Registrar Non-Discrimination / Registry/Registrar Standardization, Registrar Support for New gTLDs - 5 March <http://r20.rs6.net/tn.jsp?f=0012o43qFtByCzXTlyp2V1JdJzK09-9R4y1oPVvCuXRIhAaM...>: TLD Rollout, Contractual Compliance - 16 March <http://r20.rs6.net/tn.jsp?f=0012o43qFtByCzXTlyp2V1JdJzK09-9R4y1oPVvCuXRIhAaM...>: Community Applications - 19 March <http://r20.rs6.net/tn.jsp?f=0012o43qFtByCzXTlyp2V1JdJzK09-9R4y1oPVvCuXRIhAaM...>: Community Applications, Public Interest Commitments/Registry Voluntary Commitments - 23 March <http://r20.rs6.net/tn.jsp?f=0012o43qFtByCzXTlyp2V1JdJzK09-9R4y1oPVvCuXRIhAaM...>: Role of GAC Consensus Advice & GAC Early Warning - 26 March <http://r20.rs6.net/tn.jsp?f=0012o43qFtByCzXTlyp2V1JdJzK09-9R4y1oPVvCuXRIhAaM...>: Applicant Support - 30 March <http://r20.rs6.net/tn.jsp?f=0012o43qFtByCzXTlyp2V1JdJzK09-9R4y1oPVvCuXRIhAaM...>: String Similarity The Working Group held three sessions as part of the ICANN67 Virtual Community Forum <http://r20.rs6.net/tn.jsp?f=0012o43qFtByCzXTlyp2V1JdJzK09-9R4y1oPVvCuXRIhAaM...> and focused these sessions on topics that are of particular interest to Governmental Advisory Committee (GAC) members. In doing so, the Working Group sought to take advantage of the GAC’s focus on new gTLDs at ICANN67 and its encouragement of GAC member participation throughout the meetings. In the first session <http://r20.rs6.net/tn.jsp?f=0012o43qFtByCzXTlyp2V1JdJzK09-9R4y1oPVvCuXRIhAaM...> on 9 March <http://r20.rs6.net/tn.jsp?f=0012o43qFtByCzXTlyp2V1JdJzK09-9R4y1oPVvCuXRIhAaM...>, the Working Group focused on the topic of closed generic top-level domains (TLDs), and specifically discussed different perspectives on whether the Working Group should recommend allowing, limiting, or prohibiting these TLDs in subsequent application rounds. The second session <http://r20.rs6.net/tn.jsp?f=0012o43qFtByCzXTlyp2V1JdJzK09-9R4y1oPVvCuXRIhAaM...> on 10 March <http://r20.rs6.net/tn.jsp?f=0012o43qFtByCzXTlyp2V1JdJzK09-9R4y1oPVvCuXRIhAaM...> was devoted to the topic of the Global Public Interest, including Mandatory Public Interest Commitments (PICs), Voluntary Public Interest Commitments (which the Working Group is tentatively calling Registry Voluntary Commitments, or RVCs, for the purposes of subsequent procedures), DNS abuse, and Verified TLDs. In the third session <http://r20.rs6.net/tn.jsp?f=0012o43qFtByCzXTlyp2V1JdJzK09-9R4y1oPVvCuXRIhAaM...> on 12 March <http://r20.rs6.net/tn.jsp?f=0012o43qFtByCzXTlyp2V1JdJzK09-9R4y1oPVvCuXRIhAaM...>, the Working Group discussed possible draft recommendations on GAC Consensus Advice and GAC Early Warning and considered potential improvements to the Applicant Support Program. ** Note that draft recommendations for a subset of the topics (Closed Generics, Public Interest Commitments/Registry Voluntary Commitments, GAC Consensus Advice and GAC Early Warning, Applicant Support, and Community Applications) are currently included in a separate document <http://r20.rs6.net/tn.jsp?f=0012o43qFtByCzXTlyp2V1JdJzK09-9R4y1oPVvCuXRIhAaM...> . NEXT STEPS The Working Group will continue to develop draft final recommendations taking into consideration the Working Group’s review of its summary documents and any additional deliberations that have taken place. For the schedule of topics that will be covered in April, please see the Working Group’s wiki <http://r20.rs6.net/tn.jsp?f=0012o43qFtByCzXTlyp2V1JdJzK09-9R4y1oPVvCuXRIhAaM...> . WHAT IS THIS ABOUT? In June 2014, the GNSO Council established a Discussion Group that was intended to evaluate the experiences of the 2012 round gTLD Program and to identify possible areas for future GNSO policy development. The Discussion Group’s deliverables <http://r20.rs6.net/tn.jsp?f=0012o43qFtByCzXTlyp2V1JdJzK09-9R4y1oPVvCuXRIhAaM...> served as the basis for the GNSO Council request for a Preliminary Issue Report in June of 2015. Following the publication of the Final Issue Report <http://r20.rs6.net/tn.jsp?f=0012o43qFtByCzXTlyp2V1JdJzK09-9R4y1oPVvCuXRIhAaM...>, the GNSO Council adopted the charter <http://r20.rs6.net/tn.jsp?f=0012o43qFtByCzXTlyp2V1JdJzK09-9R4y1oPVvCuXRIhAaM...> for the PDP Working Group, which began its work in February 2016. The Working Group initially concentrated on a set of overarching issues. It later conducted deliberations on additional topics in its charter using five separate Work Tracks: Work Track 1 - Overall Process/Support/Outreach, Work Track 2 - Legal/Regulatory, Work Track 3: String Contention/Objections & Disputes, Work Track 4: Internationalized Domain Names/Technical & Operations, Work Track 5: Geographic Names at the Top Level. WHY IS THIS IMPORTANT? The Discussion Group identified a number of subjects that may require further analysis and possible formulation of policy language. There are existing policy recommendations adopted by the GNSO Council and ICANN Board, which will remain in place unless the PDP WG determines that changes are needed. More Information - Workspace Wiki <http://r20.rs6.net/tn.jsp?f=0012o43qFtByCzXTlyp2V1JdJzK09-9R4y1oPVvCuXRIhAaM...> - Charter <http://r20.rs6.net/tn.jsp?f=0012o43qFtByCzXTlyp2V1JdJzK09-9R4y1oPVvCuXRIhAaM...> - Active Project Page <http://r20.rs6.net/tn.jsp?f=0012o43qFtByCzXTlyp2V1JdJzK09-9R4y1oPVvCuXRIhAaM...> - GNSO Website <http://r20.rs6.net/tn.jsp?f=0012o43qFtByCzXTlyp2V1JdJzK09-9R4y1oPVvCuXRIhAaM...> To join this effort, please email the GNSO Secretariat: gnso-secs@icann.org. All are welcome! Follow the GNSO on Twitter [image: Twitter] <http://r20.rs6.net/tn.jsp?f=0012o43qFtByCzXTlyp2V1JdJzK09-9R4y1oPVvCuXRIhAaM...> ICANN | 12025 Waterfront Drive, Suite 300, Los Angeles, CA 90094-2536 Unsubscribe maureen.hilyard@gmail.com <https://visitor.constantcontact.com/do?p=un&m=00115LrDzKl3LoTB9FWCDiE2A%3D&c...> Update Profile <https://visitor.constantcontact.com/do?p=oo&m=00115LrDzKl3LoTB9FWCDiE2A%3D&c...> | About Constant Contact <http://www.constantcontact.com/legal/about-constant-contact> Sent by emily.barabas@icann.org in collaboration with [image: Trusted Email from Constant Contact - Try it FREE today.] <http://www.constantcontact.com/index.jsp?cc=nge&rmc=VF19_3GE> Try email marketing for free today! <http://www.constantcontact.com/index.jsp?cc=nge&rmc=VF19_3GE> _______________________________________________ ALAC mailing list ALAC@atlarge-lists.icann.org https://atlarge-lists.icann.org/mailman/listinfo/alac At-Large Online: http://www.atlarge.icann.org ALAC Working Wiki: https://community.icann.org/display/atlarge/At-Large+Advisory+Committee+(ALA...) _______________________________________________ By submitting your personal data, you consent to the processing of your personal data for purposes of subscribing to this mailing list accordance with the ICANN Privacy Policy (https://www.icann.org/privacy/policy) and the website Terms of Service (https://www.icann.org/privacy/tos). You can visit the Mailman link above to change your membership status or configuration, including unsubscribing, setting digest-style delivery or disabling delivery altogether (e.g., for a vacation), and so on. -- *NOTICE:* This email may contain information which is confidential and/or subject to legal privilege, and is intended for the use of the named addressee only. If you are not the intended recipient, you must not use, disclose or copy any part of this email. If you have received this email by mistake, please notify the sender and delete this message immediately.