FYI> -ed The latest edition is now available. New gTLD Subsequent Procedures PDP October 2020 Newsletter CURRENT STATUS Following the 30 September closure of the public comment <http://r20.rs6.net/tn.jsp?f=001U-BQ5mcgXWrMRrH2an1xRd78K7B3SIHG9tfmRTc3aEdlt...> period on the Working Group’s draft Final Report <http://r20.rs6.net/tn.jsp?f=001U-BQ5mcgXWrMRrH2an1xRd78K7B3SIHG9tfmRTc3aEdlt...>, the Working Group has begun its review of the input received. The Working Group is using a series of review tool <http://r20.rs6.net/tn.jsp?f=001U-BQ5mcgXWrMRrH2an1xRd78K7B3SIHG9tfmRTc3aEdlt...> spreadsheets to support this analysis. Working Group meetings in October focused on the following topics: - 1 October <http://r20.rs6.net/tn.jsp?f=001U-BQ5mcgXWrMRrH2an1xRd78K7B3SIHG9tfmRTc3aEdlt...>: Community Priority Evaluation Guidelines - 8 October <http://r20.rs6.net/tn.jsp?f=001U-BQ5mcgXWrMRrH2an1xRd78K7B3SIHG9tfmRTc3aEdlt...>: Comments received from the ICANN Board on the draft Final Report - 19 October <http://r20.rs6.net/tn.jsp?f=001U-BQ5mcgXWrMRrH2an1xRd78K7B3SIHG9tfmRTc3aEdlt...>: Discussion with SSAC members on topics included in the draft Final Report - 27 October <http://r20.rs6.net/tn.jsp?f=001U-BQ5mcgXWrMRrH2an1xRd78K7B3SIHG9tfmRTc3aEdlt...>: Review of public comments on Predictability <http://r20.rs6.net/tn.jsp?f=001U-BQ5mcgXWrMRrH2an1xRd78K7B3SIHG9tfmRTc3aEdlt...>, as well as general comments <http://r20.rs6.net/tn.jsp?f=001U-BQ5mcgXWrMRrH2an1xRd78K7B3SIHG9tfmRTc3aEdlt...> - 29 October <http://r20.rs6.net/tn.jsp?f=001U-BQ5mcgXWrMRrH2an1xRd78K7B3SIHG9tfmRTc3aEdlt...>: Review of public comments on Applicant Support <http://r20.rs6.net/tn.jsp?f=001U-BQ5mcgXWrMRrH2an1xRd78K7B3SIHG9tfmRTc3aEdlt...>, Limited Challenge/Appeal Mechanism <http://r20.rs6.net/tn.jsp?f=001U-BQ5mcgXWrMRrH2an1xRd78K7B3SIHG9tfmRTc3aEdlt...>, Applicant Guidebook <http://r20.rs6.net/tn.jsp?f=001U-BQ5mcgXWrMRrH2an1xRd78K7B3SIHG9tfmRTc3aEdlt...>, Communications <http://r20.rs6.net/tn.jsp?f=001U-BQ5mcgXWrMRrH2an1xRd78K7B3SIHG9tfmRTc3aEdlt...>, and Systems <http://r20.rs6.net/tn.jsp?f=001U-BQ5mcgXWrMRrH2an1xRd78K7B3SIHG9tfmRTc3aEdlt...> During ICANN69, the working group had two sessions (session 1 <http://r20.rs6.net/tn.jsp?f=001U-BQ5mcgXWrMRrH2an1xRd78K7B3SIHG9tfmRTc3aEdlt...>, session 2 <http://r20.rs6.net/tn.jsp?f=001U-BQ5mcgXWrMRrH2an1xRd78K7B3SIHG9tfmRTc3aEdlt...>) on 14 October in which it reviewed public comment submissions on two topics: Applicant Support <http://r20.rs6.net/tn.jsp?f=001U-BQ5mcgXWrMRrH2an1xRd78K7B3SIHG9tfmRTc3aEdlt...> and Community Applications <http://r20.rs6.net/tn.jsp?f=001U-BQ5mcgXWrMRrH2an1xRd78K7B3SIHG9tfmRTc3aEdlt...> . NEXT STEPS The Working Group will continue to review and analyze the input received through public comment with the objective of finalizing its recommendations and Final Report. The Working Group’s work plan <http://r20.rs6.net/tn.jsp?f=001U-BQ5mcgXWrMRrH2an1xRd78K7B3SIHG9tfmRTc3aEdlt...> provides additional information about the topics that will be discussed on upcoming calls. 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 <http://r20.rs6.net/tn.jsp?f=001U-BQ5mcgXWrMRrH2an1xRd78K7B3SIHG9tfmRTc3aEdlt...> deliverables <http://r20.rs6.net/tn.jsp?f=001U-BQ5mcgXWrMRrH2an1xRd78K7B3SIHG9tfmRTc3aEdlt...> served as the basis for the GNSO Council request for a Preliminary Issue Report in June of 2015. Following the publication of the <http://r20.rs6.net/tn.jsp?f=001U-BQ5mcgXWrMRrH2an1xRd78K7B3SIHG9tfmRTc3aEdltYxnin4nHb_3N8ss1JOrZ8LtOsnXi50ykUx_7VsBCrX-jHKSL6Rsz77wYNu15WCfMqdCZxvrTA1UW1YDzVhXK885tZ0K0mRQ8qRFUbYJwrXvTDfu3S2x8zZ_21yKvLlsBPHyw14DJOJrzELtHALkbiTgEwR44k9jnRZzAaSKni8KGYz9Y-3qHZOPjmMvNQAs-Wpo0DB6Yw==&c=GYK1y5UPwqyMOy103FGq3hrjhgakkidTPf75QTfFcd2L1f7v5HkbwQ==&ch=0fxV4aV3DLt9XY9BExdN0JJRI0TPLUdGUac8Hxx3aRiwKJlRBfNM-w==>Final Issue Report <http://r20.rs6.net/tn.jsp?f=001U-BQ5mcgXWrMRrH2an1xRd78K7B3SIHG9tfmRTc3aEdlt...>, the GNSO Council adopted the <http://r20.rs6.net/tn.jsp?f=001U-BQ5mcgXWrMRrH2an1xRd78K7B3SIHG9tfmRTc3aEdlt...> charter <http://r20.rs6.net/tn.jsp?f=001U-BQ5mcgXWrMRrH2an1xRd78K7B3SIHG9tfmRTc3aEdlt...> for the PDP Working Group, which began its work in February 2016. The Working Group first concentrated on a set of overarching issues. It then conducted initial 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. Following publication of the Working Group’s Initial Report <http://r20.rs6.net/tn.jsp?f=001U-BQ5mcgXWrMRrH2an1xRd78K7B3SIHG9tfmRTc3aEdlt...>, Supplemental Initial Report <http://r20.rs6.net/tn.jsp?f=001U-BQ5mcgXWrMRrH2an1xRd78K7B3SIHG9tfmRTc3aEdlt...>, and the Final Report produced by Work Track 5 <http://r20.rs6.net/tn.jsp?f=001U-BQ5mcgXWrMRrH2an1xRd78K7B3SIHG9tfmRTc3aEdlt...>, the Working Group reviewed public comments received on the Initial Report and Supplemental Initial Report, refined its outputs and published a draft Final Report <http://r20.rs6.net/tn.jsp?f=001U-BQ5mcgXWrMRrH2an1xRd78K7B3SIHG9tfmRTc3aEdlt...> for public comment. 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=001U-BQ5mcgXWrMRrH2an1xRd78K7B3SIHG9tfmRTc3aEdlt...> - Charter <http://r20.rs6.net/tn.jsp?f=001U-BQ5mcgXWrMRrH2an1xRd78K7B3SIHG9tfmRTc3aEdlt...> - Active Project Page <http://r20.rs6.net/tn.jsp?f=001U-BQ5mcgXWrMRrH2an1xRd78K7B3SIHG9tfmRTc3aEdlt...> - GNSO Website <http://r20.rs6.net/tn.jsp?f=001U-BQ5mcgXWrMRrH2an1xRd78K7B3SIHG9tfmRTc3aEdlt...> 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=001U-BQ5mcgXWrMRrH2an1xRd78K7B3SIHG9tfmRTc3aEdlt...> 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 our service provider <http://www.constantcontact.com/legal/service-provider?cc=about-service-provi...> Sent by emily.barabas@icann.org powered by [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.