November 2019 - council - lists.icann.org

Confirmation of GNSO Representative on the Empowered Community Administration
by Nathalie Peregrine 20 Oct '22

20 Oct '22

Dear John, Please find the attached a letter with the motion passed at the GNSO Council meeting on 29 November 2018. The Council confirmed the appointment of the GNSO Chair, currently Keith Drazek, representing the GNSO as the Decisional Participant on the Empowered Community Administration until the end of his term at ICANN66. The letter will be published on page: https://gnso.icann.org/en/council/correspondence<https://urldefense.proofpoint.com/v2/url?u=https-3A__gnso.icann.org_en_coun…> Thank you. Respectfully submitted. Nathalie Nathalie Peregrine Manager, Operations Support (GNSO) Internet Corporation for Assigned Names and Numbers (ICANN) Email: nathalie.peregrine(a)icann.org <nathalie.peregrine(a)icann.org%20> Skype: nathalie.peregrine.icann Find out more about the GNSO by taking our interactive courses<applewebdata://EB3A6F47-9760-400D-A39B-A7EFFC56B467/learn.icann.org/courses…> and visiting the GNSO Newcomer pages<https://urldefense.proofpoint.com/v2/url?u=http-3A__gnso.icann.org_sites_gn…>

1 4

Document and Motion deadline Monday 9 December 2019 at 23:59 UTC for GNSO Council Meeting 19 December 2019 at 21:00 UTC
by Nathalie Peregrine 06 Dec '19

06 Dec '19

Dear all, Reports, motions and documents for consideration are due no later than (NLT) 10 days in advance (i.e. Monday 9 December 2019 at 23:59 UTC) of the GNSO Council Meeting on Thursday 19 December 2019 at 21:00 UTC. Motions should be sent to the Council mailing list by a councilor and will then be posted on the Wiki at: https://community.icann.org/x/DZIzBw Thank you very much. With kind regards, Nathalie Nathalie Peregrine Manager, Operations Support (GNSO) Internet Corporation for Assigned Names and Numbers (ICANN) Email: nathalie.peregrine(a)icann.org <nathalie.peregrine(a)icann.org%20> Skype: nathalie.peregrine.icann Find out more about the GNSO by visiting: https://learn.icann.org/ <https://urldefense.proofpoint.com/v2/url?u=https-3A__learn.icann.org_&d=DwM…> Follow @GNSO on Twitter: https://twitter.com/ICANN_GNSO <https://urldefense.proofpoint.com/v2/url?u=https-3A__twitter.com_ICANN-5FGN…> Transcripts and recordings of GNSO Working Group and Council events are located on the GNSO Master Calendar <https://urldefense.proofpoint.com/v2/url?u=https-3A__gnso.icann.org_en_grou…> See All SO and AC events on the ICANN Global calendar [features.icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__features.icann.org_cal…>

1 3

GNSO Review of ICANN66 Montreal GAC communique
by Johan Helsingius 06 Dec '19

06 Dec '19

Dear Council colleagues, The draft GNSO Review of ICANN66 Montreal GAC communique is now at https://docs.google.com/document/d/1hbXl51OUWr4UtkJg13uHmwztv1gRd3bJ2BW9Xbm… This time the group working on the response was extremely fast and efficient. We didn't have any disagreements or debates within the group - many thanks to Steve, Tom, Michele and Tanya! As the GAC leadership will be meeting with the Board in early December, we need to get our views to the Board in a timely manner, so please, if you have any disagreement, let us know as soon as possible. Julf

4 6

Request for Volunteer(s) -- Transfer Policy Review Scoping Team
by Drazek, Keith 30 Nov '19

30 Nov '19

Dear Councilors: The Transfer Policy Review Scoping Team will begin its work shortly, and to date, no GNSO Councilors have signed up to participate in this Scoping Team. As this Scoping Team may ultimately recommend chartering a new PDP, it would be preferable to have at least one GNSO Council liaison aware of the recommendations the group intends to make. Additionally, a Council member would also be helpful in keeping the Scoping Team mindful of the GNSO Council and community's current and upcoming workload. While we are sympathetic to everyone's busy schedules, we would like to ask for at least one volunteer, though more than one is encouraged, to follow and/or contribute to the work of the Transfer Policy Review Scoping Team. This Scoping Team is expected to meet on a bi-weekly basis and conduct most of its work offline. This commitment is expected to last through February 2020. If anyone is willing to step forward to assist, please respond to the list. This is just one example of our need for active engagement by Councilors in the year ahead. Best regards, Keith

2 1

FW: [ICANN Community Leaders] 28 November Update
by Nathalie Peregrine 28 Nov '19

28 Nov '19

[http://r20.rs6.net/on.jsp?ca=7e1ffefd-3375-4be5-97d5-8b278b0bc228&a=1122025…] Thursday, 28 November 2019 ICANN Community Leadership Digest [https://files.constantcontact.com/304b3fd3501/31f30ab5-1445-45c3-aef7-c0ea4…] The ICANN org Policy Development Support team publishes this twice-weekly digest to help ICANN community leaders track requests and updates. Table of Contents Information Sharing · REMINDER: NextGen@ICANN Community Consultation · REMINDER: ICANN Fellowship Program Mentors ICANN67 Planning · REMINDER: ICANN67 Publication Support · REMINDER: CROP Deadline for ICANN67 Public Comment · EXTENDED: Registration Directory Service (WHOIS2) Review Team Final Report · Implementation Plan for the GNSO Consensus Policy Relating to the Protection of Certain Red Cross Names · Proposal for Future Root Zone KSK Rollovers Information Sharing REMINDER: NextGen@ICANN Community Consultation Executive: Sally Costerton, Senior Vice President, Global Stakeholder Engagement FOR: All Community Leaders INFORMATION SHARING The NextGen@ICANN program is currently undergoing a community consultation [r20.rs6.net]<https://urldefense.proofpoint.com/v2/url?u=http-3A__r20.rs6.net_tn.jsp-3Ff-…>. One request from the preliminary feedback received to-date was for ICANN org to explore the feasibility of having community volunteer representatives from Supporting Organizations (SOs), Advisory Committees (ACs), Stakeholder Groups (SGs), and Constituencies (Cs) to nominate individuals for the following two roles: 1. NextGen Selection Committee members 2. NextGen mentors For the Selection Committee, a time commitment of approximately 20 hours over three weeks is required (for each application round). Selection Committee members will typically serve for two years (or six application rounds). Mentors are expected to devote approximately 24 hours to pre-ICANN Public Meeting preparation with their mentees, to offer advice, networking support, and regular check-ins on-site, and to complete evaluations following the ICANN Public Meeting. Based on previous estimates, mentors spend about two hours per week during the six-week preparation period in advance of the meeting and about two hours per day providing on-site support at the ICANN Public Meeting. Mentors will typically serve for one year (or three meetings). Is your group interested in nominating individuals for either of these roles? By Monday, 16 December 2019, please take the following poll [r20.rs6.net]<https://urldefense.proofpoint.com/v2/url?u=http-3A__r20.rs6.net_tn.jsp-3Ff-…> to help ICANN org can gauge the level of community interest. The findings of this poll will inform the proposed NextGen program approach that will be published for Public Comment. Note: You will not be asked to submit the names of potential volunteers for roles at this time. REMINDER: ICANN Fellowship Program Mentors From: Sally Costerton, Senior Vice President, Global Stakeholder Engagement FOR: All Community Leaders INFORMATION SHARING ICANN's Supporting Organizations (SOs) and Advisory Committees (ACs) are invited to nominate [r20.rs6.net]<https://urldefense.proofpoint.com/v2/url?u=http-3A__r20.rs6.net_tn.jsp-3Ff-…> one individual each (total of seven) to serve as a mentor in the ICANN Fellowship Program. Mentors will serve a term that includes three consecutive ICANN Public Meetings, beginning with ICANN68. They will provide extensive pre-meeting preparation and on-site support for their assigned fellows, as well as complete a survey after each meeting. Mentors are expected to follow Fellowship Program guidelines to help ensure consistency in capacity development opportunities for fellows. They also play an important role to help fellows actively participate in ICANN's work. Mentors will receive travel funding support. Mentors cannot serve on the Fellowship Program Selection Committee [r20.rs6.net]<https://urldefense.proofpoint.com/v2/url?u=http-3A__r20.rs6.net_tn.jsp-3Ff-…> at the same time they are serving as mentors. For more information on the guidelines and expectations for mentors, please read about the program here [r20.rs6.net]<https://urldefense.proofpoint.com/v2/url?u=http-3A__r20.rs6.net_tn.jsp-3Ff-…>. SOs/ACs should first select their respective Fellowship Program mentor by Thursday, 31 January 2020, and notify fellowshipconsultation(a)icann.org. Individual self-nominations will not be considered. ICANN67 Planning REMINDER: ICANN67 Publication Support From: David Olive, Senior Vice President, Policy Development Support FOR: All Community Leaders INFORMATION SHARING Design Deadline If you require design assistance for an ICANN67 publication, all text, images, layout, and publication type/size requirements (i.e. newsletter, 1-pager, tri-fold, etc.) are due Friday, 3 January 2020. Please ensure that all materials, new or updated, are evergreen. Translation Deadline If your ICANN67 publication requires translation, please provide the final material(s) by Monday, 27 January 2020. This ensures that there is enough time to translate the publication by the print deadline. If your materials require design assistance (outlined above), please note that the final materials will have to be complete, including the edit/approval process, by this deadline in order to be translated. Print-Only Deadline If you only need your ICANN67 publication printed (meaning your publication is ready to send directly to the printer and needs no translation or design/layout modifications), please provide the file along with the quantity you want printed and dimensions of the publication by Friday, 7 February 2020. Please work directly with your support staff to submit these requests to chantelle.doerksen(a)icann.org and liana.teo(a)icann.org. REMINDER: CROP Deadline for ICANN67 From: David Olive, Senior Vice President, Policy Development Support FOR: All Community Leaders INFORMATION SHARING For eligible groups planning to use Community Regional Outreach Program (CROP) funds to conduct outreach during ICANN67, requests must be submitted no later than Friday, 17 January 2020. No exceptions will be made. When submitting a CROP travel request, please keep in mind the following: Trip requests must be approved by the respective community leadership team. For FY20, the trip request must be filled in by the CROP participant via the CROP workspace [r20.rs6.net]<https://urldefense.proofpoint.com/v2/url?u=http-3A__r20.rs6.net_tn.jsp-3Ff-…>. In order to access it, applicants must first have an account; please let the CROP coordinator know if you need an account. All individuals requesting CROP funding must also review the CROP Guidelines [r20.rs6.net]<https://urldefense.proofpoint.com/v2/url?u=http-3A__r20.rs6.net_tn.jsp-3Ff-…> prior to submitting a request. Please contact crop-staff(a)icann.org with any questions. Public Comment Registration Directory Service (WHOIS2) Review Team Final Report [r20.rs6.net]<https://urldefense.proofpoint.com/v2/url?u=http-3A__r20.rs6.net_tn.jsp-3Ff-…> EXTENDED: Monday, 9 December 2019 Implementation Plan for the GNSO Consensus Policy Relating to the Protection of Certain Red Cross Names [r20.rs6.net]<https://urldefense.proofpoint.com/v2/url?u=http-3A__r20.rs6.net_tn.jsp-3Ff-…> Close Date: Thursday, 12 December 2019 Proposal for Future Root Zone KSK Rollover [r20.rs6.net]<https://urldefense.proofpoint.com/v2/url?u=http-3A__r20.rs6.net_tn.jsp-3Ff-…> Close Date: Friday, 31 January 2020 Volume 1, Issue 69 | Archive [r20.rs6.net]<https://urldefense.proofpoint.com/v2/url?u=http-3A__r20.rs6.net_tn.jsp-3Ff-…> | Next Issue: Monday, 2 December 2019 ICANN | 12025 Waterfront Drive, Suite 300, Los Angeles, CA 90094-2536 Unsubscribe so-ac-sg-cleaders(a)icann.org [visitor.constantcontact.com]<https://urldefense.proofpoint.com/v2/url?u=https-3A__visitor.constantcontac…> Update Profile [visitor.constantcontact.com]<https://urldefense.proofpoint.com/v2/url?u=https-3A__visitor.constantcontac…> | About Constant Contact [constantcontact.com]<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.constantcontact.com…> Sent by david.olive(a)icann.org<mailto:david.olive@icann.org> in collaboration with [Trusted Email from Constant Contact - Try it FREE today.][constantcontact.com]<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.constantcontact.com…> Try email marketing for free today! [constantcontact.com]<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.constantcontact.com…>

1 0

Re: [council] Electronic vote result / Motion to support the Approval Action pertaining to the Fundamental Bylaws Amendment regarding the IANA Naming Function Review Team
by Maarten Simon 28 Nov '19

28 Nov '19

Dear Councilors, Thank you all for your support. We have also received approval from the GAC, ALAC and ccNSO itself. This will make it easier for the ccNSO and the broader ccTLD-community to timely select suitable candidates for any future IANA Function Review Team. Best, Maarten Simon ccNSO liason to the GNSO Van: council <council-bounces(a)gnso.icann.org> namens Terri Agnew <terri.agnew(a)icann.org> Datum: donderdag 28 november 2019 om 01:10 Aan: "council(a)gnso.icann.org" <council(a)gnso.icann.org> CC: "gnso-secs(a)icann.org" <gnso-secs(a)icann.org> Onderwerp: [council] Electronic vote result / Motion to support the Approval Action pertaining to the Fundamental Bylaws Amendment regarding the IANA Naming Function Review Team Dear Councilors, The GNSO Council email vote on the motion to support the Approval Action pertaining to the Fundamental Bylaws Amendment regarding the IANA Naming Function Review Team Composition (see: https://community.icann.org/x/OJIzBw ) which closed at 23:59 UTC on Wednesday 27 November 2019. With 7 votes in favor in the Contracted Party House, and 13 votes in favor in the Non-Contracted Party House, the motion passes with 100% votes in favor in the CPH and 100% in favor in the NCPH. Please find the results attached and at the url:https://tally.icann.org/cgi/adm/monitor?a=me&e=f7bcd092b20 There were 20 eligible voters, 20 voters expressed their vote. Please note that James Bladel voted as temporary alternate for Darcy Southwell. Elsa Saade held the proxy for Farzaneh Badii and communicated her proxy vote to the GNSO Secretariat via email on Tuesday 26 November 2019. The resolutions from this vote will be posted on page: http://gnso.icann.org/en/council/resolutions<https://urldefense.proofpoint.com/v2/url?u=http-3A__gnso.icann.org_en_counc…> Thank you for your cooperation in completing the vote. With kind regards, Nathalie

1 0

Update: ALAC Feedback: Invitation to Provide Input for PDP 3.0 Implementation
by Julie Bisland 27 Nov '19

27 Nov '19

Dear All, There is one revision added to the statement (attached) in the second paragraph on the first page: The ALAC appreciates proposed reforms to the PDP process that may make the process more effective and efficient in achieving outcomes. However, concern was expressed that the “reforms” suggested by the PDP 3.0 could be used to actually limit the participation by the ALAC / At-Large Community. In striving for timely, inclusive, productive and broad-based participation in PDP 3.0, the ALAC wish to share some feedback with the GNSO Council. Best regards, Julie From: Gnso-secs <gnso-secs-bounces(a)icann.org> on behalf of Julie Bisland <julie.bisland(a)icann.org> Date: Wednesday, November 27, 2019 at 3:16 PM To: "council(a)gnso.icann.org" <council(a)gnso.icann.org> Cc: "gnso-secs(a)icann.org" <gnso-secs(a)icann.org> Subject: [gnso-secs] ALAC Feedback: Invitation to Provide Input for PDP 3.0 Implementation Apologies, with attachment! From: Gnso-secs <gnso-secs-bounces(a)icann.org> on behalf of Julie Bisland <julie.bisland(a)icann.org> Date: Wednesday, November 27, 2019 at 3:07 PM To: "council(a)gnso.icann.org" <council(a)gnso.icann.org> Cc: "gnso-secs(a)icann.org" <gnso-secs(a)icann.org> Subject: [gnso-secs] FW: ALAC Feedback: Invitation to Provide Input for PDP 3.0 Implementation Dear all, Please see below: From: Gnso-secs <gnso-secs-bounces(a)icann.org> on behalf of Ariel Liang <ariel.liang(a)icann.org> Date: Wednesday, November 27, 2019 at 3:00 PM To: ICANN At-Large Staff <staff(a)atlarge.icann.org>, Steve Chan <steve.chan(a)icann.org> Cc: Evin Erdogdu <evin.erdogdu(a)icann.org>, "gnso-secs(a)icann.org" <gnso-secs(a)icann.org>, Justine Chew <justine.chew(a)gmail.com>, Holly Raiche <h.raiche(a)internode.on.net>, Alan Greenberg <alan.greenberg(a)mcgill.ca>, Maureen Hilyard <maureen.hilyard(a)gmail.com> Subject: Re: [gnso-secs] ALAC Feedback: Invitation to Provide Input for PDP 3.0 Implementation Hello Evin and all, Thank you very much for sending the ALAC input for the PDP 3.0 improvements. We will forward it to the GNSO Council list and share with the Council Small Team that supports the PDP 3.0 implementation efforts. Have a wonderful Thanksgiving holiday for those who are celebrating! Best Regards, Ariel Ariel Xinyue Liang GNSO Policy Support Specialist Internet Corporation for Assigned Names and Numbers (ICANN) From: ICANN At-Large Staff <staff(a)atlarge.icann.org> Date: Wednesday, November 27, 2019 at 3:49 PM To: Ariel Liang <ariel.liang(a)icann.org>, Steve Chan <steve.chan(a)icann.org> Cc: "gnso-secs(a)icann.org" <gnso-secs(a)icann.org>, Maureen Hilyard <maureen.hilyard(a)gmail.com>, Alan Greenberg <alan.greenberg(a)mcgill.ca>, Holly Raiche <h.raiche(a)internode.on.net>, Justine Chew <justine.chew(a)gmail.com>, Evin Erdogdu <evin.erdogdu(a)icann.org>, ICANN At-Large Staff <staff(a)atlarge.icann.org> Subject: ALAC Feedback: Invitation to Provide Input for PDP 3.0 Implementation Dear All, In response to the GNSO Invitation to Provide Input for PDP 3.0 Implementation, please find attached the requested ALAC feedback. Please confirm receipt. Thank you. Kind Regards, ICANN Policy Staff in support of the At-Large Community Website: atlarge.icann.org [atlarge.icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__atlarge.icann.org_&d=D…> Facebook: facebook.com/icann [facebook.com]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.facebook.com_icann…>atlarge [facebook.com]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.facebook.com_icann…> Twitter: @ [twitter.com]<https://urldefense.proofpoint.com/v2/url?u=https-3A__twitter.com_ICANNAtLar…>ICANNAtLarge [twitter.com]<https://urldefense.proofpoint.com/v2/url?u=https-3A__twitter.com_ICANNAtLar…>

1 0

GNSO Council resolution 27 November 2019
by Terri Agnew 27 Nov '19

27 Nov '19

Dear all, Please find below the resolution from the GNSO council email vote ending on 27 November 2019 which has been posted on the GNSO resolutions<https://urldefense.proofpoint.com/v2/url?u=https-3A__gnso.icann.org_en_coun…> page. 20191127 – 1 Motion to Support the Approval Action pertaining to the Fundamental Bylaws Amendment regarding the IANA Naming Function Review Team Composition Whereas: 1. Due to changing composition of the ccNSO in the years since the IANA Stewardship Transition, the ccNSO Council had difficulty locating a non-ccNSO ccTLD representative to the IANA Naming Function Review Team (IFR Team) as required by Section 18.7(b) of the ICANN Bylaws. As a result, this significantly delayed the completion of composition of the IFR Team, and this same difficulty is anticipated to arise for future IANA Naming Function Reviews. 2. On 12 April 2019 the ccNSO Council requested the ICANN Board to initiate an amendment to the ICANN Bylaws to remedy this situation, and proposed language for such amendment. Per ICANN Board request, the proposed amendment to Section 18.7 of the ICANN Bylaws was posted for public comment<https://www.icann.org/public-comments/bylaws-amend-iana-naming-function-201…> from 10 June – 9 August 2019. Six comments were received, and no commenters were opposed to the amendment. 3. On 8 September 2019, the ICANN Board approved<https://www.icann.org/resources/board-material/prelim-report-2019-09-08-en#…> the amendment to the Fundamental Bylaws at Article 18, Section 18.7 regarding IANA Naming Function Review Team composition. 4. The amended Bylaws at Article 18, Section 18.7 reads the following: "(a) Three representatives who are associated with ccTLD managers, appointed by the ccNSO Council. Representatives need not be associated with a ccNSO member. The ccNSO Council should use an inclusive process, which is open to all ccTLD managers, independent of their membership to the ccNSO. It is strongly recommended that the ccNSO Council reaches out to all ccTLD managers directly and or through regional ccTLD organizations (i.e., AfTLD, APTLD, LACTLD, and CENTR) in seeking volunteers." The other portions of Section 18.7 are renumbered as a result of this modification. The full redline of the Board approved changes to Section 18.7 is available here<https://www.icann.org/en/system/files/files/draft-proposed-bylaws-amend-sec…>. 5. Per Annex D, Section 1.3(c) of the ICANN Bylaws, the Approval Action Community Forum<https://66.schedule.icann.org/meetings/1116779> pertaining to the Fundamental Bylaws amendment regarding the IANA Naming Function Review Team Composition convened, at the request of the Empowered Community, during ICANN's 66th public meeting on Sunday, 3 November at 8:00-9:00 am EST. 6. The Approval Action Community Forum Period pertaining to the Fundamental Bylaws amendment regarding the IANA Naming Function Review Team Composition has expired on 7 November 2019 at 11:59 pm EST. 7. Per Annex D, Section 1.4(a) of the ICANN Bylaws, at any time or date prior to 11:59 p.m. PST on Thursday 28 November 2019, with respect to the Fundamental Bylaws amendment regarding the IANA Naming Function Review Team Composition, each Decisional Participant shall inform the EC Administration in writing as to whether such Decisional Participant (i) supports such Approval Action, (ii) objects to such Approval Action or (iii) has determined to abstain from the matter (which shall not count as supporting or objecting to such Approval Action), and each Decisional Participant shall forward such notice to the Secretary for ICANN to promptly post on the Website. 8. From 07 November 2019 to 19 November 2019, the GNSO Stakeholder Groups and Constituencies had the opportunity to provide feedback, opinions or comments on the merits of the Approval Action prior to the GNSO Council vote to decide its support, objection to, or abstention from the matter. 9. Per Section 11.3(j)(iv) of the ICANN Bylaws, amendments to Fundamental Bylaws requires an affirmative vote of a GNSO Supermajority. 10. Per Section 11.3(i) of the ICANN Bylaws, GNSO Supermajority means: (A) two-thirds (2/3) of the Council members of each House, or (B) three-fourths (3/4) of the Council members of one House and a majority of the Council members of the other House. Resolved: 1. The GNSO Council supports the Approval Action pertaining to the Fundamental Bylaws amendment regarding the IANA Naming Function Review Team Composition that was approved by the ICANN Board. 2. The GNSO Council requests the GNSO Representative on the EC Administration to promptly inform the EC Administration, the other Decisional Participants, and the ICANN Corporate Secretary about the GNSO Council's decision with respect to the Approval Action. Vote results<https://gnso.icann.org/sites/default/files/file/field-file-attach/gnso-coun…>

1 0

Electronic vote result / Motion to support the Approval Action pertaining to the Fundamental Bylaws Amendment regarding the IANA Naming Function Review Team
by Terri Agnew 27 Nov '19

27 Nov '19

Dear Councilors, The GNSO Council email vote on the motion to support the Approval Action pertaining to the Fundamental Bylaws Amendment regarding the IANA Naming Function Review Team Composition (see: https://community.icann.org/x/OJIzBw ) which closed at 23:59 UTC on Wednesday 27 November 2019. With 7 votes in favor in the Contracted Party House, and 13 votes in favor in the Non-Contracted Party House, the motion passes with 100% votes in favor in the CPH and 100% in favor in the NCPH. Please find the results attached and at the url:https://tally.icann.org/cgi/adm/monitor?a=me&e=f7bcd092b20 There were 20 eligible voters, 20 voters expressed their vote. Please note that James Bladel voted as temporary alternate for Darcy Southwell. Elsa Saade held the proxy for Farzaneh Badii and communicated her proxy vote to the GNSO Secretariat via email on Tuesday 26 November 2019. The resolutions from this vote will be posted on page: http://gnso.icann.org/en/council/resolutions<https://urldefense.proofpoint.com/v2/url?u=http-3A__gnso.icann.org_en_counc…> Thank you for your cooperation in completing the vote. With kind regards, Nathalie

1 0

ALAC Feedback: Invitation to Provide Input for PDP 3.0 Implementation
by Julie Bisland 27 Nov '19

27 Nov '19

Apologies, with attachment! From: Gnso-secs <gnso-secs-bounces(a)icann.org> on behalf of Julie Bisland <julie.bisland(a)icann.org> Date: Wednesday, November 27, 2019 at 3:07 PM To: "council(a)gnso.icann.org" <council(a)gnso.icann.org> Cc: "gnso-secs(a)icann.org" <gnso-secs(a)icann.org> Subject: [gnso-secs] FW: ALAC Feedback: Invitation to Provide Input for PDP 3.0 Implementation Dear all, Please see below: From: Gnso-secs <gnso-secs-bounces(a)icann.org> on behalf of Ariel Liang <ariel.liang(a)icann.org> Date: Wednesday, November 27, 2019 at 3:00 PM To: ICANN At-Large Staff <staff(a)atlarge.icann.org>, Steve Chan <steve.chan(a)icann.org> Cc: Evin Erdogdu <evin.erdogdu(a)icann.org>, "gnso-secs(a)icann.org" <gnso-secs(a)icann.org>, Justine Chew <justine.chew(a)gmail.com>, Holly Raiche <h.raiche(a)internode.on.net>, Alan Greenberg <alan.greenberg(a)mcgill.ca>, Maureen Hilyard <maureen.hilyard(a)gmail.com> Subject: Re: [gnso-secs] ALAC Feedback: Invitation to Provide Input for PDP 3.0 Implementation Hello Evin and all, Thank you very much for sending the ALAC input for the PDP 3.0 improvements. We will forward it to the GNSO Council list and share with the Council Small Team that supports the PDP 3.0 implementation efforts. Have a wonderful Thanksgiving holiday for those who are celebrating! Best Regards, Ariel Ariel Xinyue Liang GNSO Policy Support Specialist Internet Corporation for Assigned Names and Numbers (ICANN) From: ICANN At-Large Staff <staff(a)atlarge.icann.org> Date: Wednesday, November 27, 2019 at 3:49 PM To: Ariel Liang <ariel.liang(a)icann.org>, Steve Chan <steve.chan(a)icann.org> Cc: "gnso-secs(a)icann.org" <gnso-secs(a)icann.org>, Maureen Hilyard <maureen.hilyard(a)gmail.com>, Alan Greenberg <alan.greenberg(a)mcgill.ca>, Holly Raiche <h.raiche(a)internode.on.net>, Justine Chew <justine.chew(a)gmail.com>, Evin Erdogdu <evin.erdogdu(a)icann.org>, ICANN At-Large Staff <staff(a)atlarge.icann.org> Subject: ALAC Feedback: Invitation to Provide Input for PDP 3.0 Implementation Dear All, In response to the GNSO Invitation to Provide Input for PDP 3.0 Implementation, please find attached the requested ALAC feedback. Please confirm receipt. Thank you. Kind Regards, ICANN Policy Staff in support of the At-Large Community Website: atlarge.icann.org [atlarge.icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__atlarge.icann.org_&d=D…> Facebook: facebook.com/icann [facebook.com]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.facebook.com_icann…>atlarge [facebook.com]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.facebook.com_icann…> Twitter: @ [twitter.com]<https://urldefense.proofpoint.com/v2/url?u=https-3A__twitter.com_ICANNAtLar…>ICANNAtLarge [twitter.com]<https://urldefense.proofpoint.com/v2/url?u=https-3A__twitter.com_ICANNAtLar…>

1 0