From robin Thu Apr 9 00:22:47 2020 From: robin (Robin Gross) Date: Wed, 8 Apr 2020 14:22:47 -0700 Subject: [PC-NCSG] [NCSG-EC] Fwd: PLEASE READ: NCPH election for Board seat 14 In-Reply-To: <50546364-b2fd-bd3d-77a3-f6613a7c33e9@mail.utoronto.ca> References: <57A94745-69DE-4628-8168-8F15F1C7D467@icann.org> <50546364-b2fd-bd3d-77a3-f6613a7c33e9@mail.utoronto.ca> Message-ID: <6539E322-F58B-410A-B3D4-A05C6C868113@ipjustice.org> Hi all, I?ve add the NCSG-PC onto this thread since it is the PC who will vote and select our board nominee (pursuant to NCSG Charter). Thanks, Robin > On Apr 8, 2020, at 2:20 PM, Stephanie E Perrin via NCSG-EC wrote: > > I need to consult you guys, then we (csg and ncsg) need to set up an election, where we pick someone to vote for us, and if we get two votes for Matthew (ie each side votes for him) we tell staff and Council he is our nominee. It seems a bit clumsy but since we have had a meltdown in the past, we needed procedures.... > > I presume staff will set up that election for us, will ask Carlos Reyes who is now in charge of our policy support, not Mary Wong. > > cheers Steph > > PS Dean Marks is doing the same thing with the CSG guys. > > > On 2020-04-08 5:16 p.m., Raphael Beauregard-Lacroix wrote: >> Sure, I'm just not sure what needs to be done! >> >> On Wed, Apr 8, 2020 at 1:04 PM Stephanie E Perrin via NCSG-EC > wrote: >> Hi folks, we need to organize on the election of Matthew Shears for Board seat 14. I have reached out to Carlton Samuels, to tick the box of consulting with our nomcom appointee (no response so far) and I have been chatting with Dean Marks from the CSG, who is keen to cooperate. We are trying to meet this new deadline of April 20, can we organize to hold our election next week in time to offer our name? The CSG thinks they can. >> Sorry to push but we have to get this done faster now due to ICANN's revised timelines....since we are agreed on the candidate, it is just paperwork.... >> cheers Steph >> >> >> -------- Forwarded Message -------- >> Subject: PLEASE READ: NCPH election for Board seat 14 >> Date: Tue, 7 Apr 2020 20:17:14 +0000 >> From: Mary Wong >> To: Dean Marks , Stephanie E Perrin , Bruna Martins dos Santos , Joan Kerr , Rafik Dammak , Selli, Claudia , csg-excomm at icann.org , Barbara Wanner >> CC: Chantelle Doerksen , Maryam Bakoshi , Andrea Glandon , Carlos Reyes >> >> Dear CSG and NCSG leaders, >> >> >> I would like to apologize for bringing up this topic at this late stage, and at a time when I know that many community members are focusing on important personal and family matters during the current COVID-19 situation. Please understand that we as staff would not have raised this were it not a Bylaws-related matter. >> >> >> Here is the issue: under the ICANN Bylaws, formal notification of a nominee for either Board seat 13 or 14 must be provided to the Empowered Community Administration at least six (6) months prior to the commencement of that potential Director?s term. As the 2020 Annual General Meeting is due to conclude on 22 October 2020 (which we realize is somewhat earlier than previous AGMs), this means that the Empowered Community Administration must receive the Non-Contracted Parties House (NCPH) nomination of a Director to fill Board seat 14 by 22 April 2020 (and not May as we had advised you previously). >> >> >> I understand that the NCPH?s current plan is to hold the formal vote (via a CSG and NCSG representative and in accordance with the NCPH?s agreed procedures) on or around 29 April. In light of the need to notify the GNSO Chair of the result (as under the GNSO Operating Procedures Keith has the responsibility of notifying the Empowered Community Administration), I would like to ask if it will be possible for the NCPH to complete its vote on a nominee for Board seat 14 by Monday 20 April, to allow Keith time to inform the GNSO Council (as has been customary) and to formally notify the Empowered Community Administration. >> >> >> I and the whole GNSO support team are sincerely sorry for our previous guidance to you that had mistakenly set 21 May as the final date. Please accept our heartfelt apologies for this rare error as well as for the inconvenience that we know our mistake must cause you and your groups. >> >> >> In view of the situation, please be assured that the CSG and NCSG support staff are happy to assist you with conducting the vote as efficiently and smoothly as possible, to minimize disruption and inconvenience to you. Please let me know if you have any questions or concerns with either the timing or mechanism for the upcoming vote and, once again, I am so very sorry for the trouble. >> >> >> Thank you all very much for your kind understanding. >> >> >> Best regards, >> >> Mary >> >> >> >> _______________________________________________ >> NCSG-EC mailing list >> NCSG-EC at lists.ncsg.is >> https://lists.ncsg.is/mailman/listinfo/ncsg-ec > _______________________________________________ > NCSG-EC mailing list > NCSG-EC at lists.ncsg.is > https://lists.ncsg.is/mailman/listinfo/ncsg-ec -------------- next part -------------- An HTML attachment was scrubbed... URL: From stephanie.perrin Thu Apr 9 00:31:47 2020 From: stephanie.perrin (Stephanie E Perrin) Date: Wed, 8 Apr 2020 17:31:47 -0400 Subject: [PC-NCSG] [NCSG-EC] Fwd: PLEASE READ: NCPH election for Board seat 14 In-Reply-To: <6539E322-F58B-410A-B3D4-A05C6C868113@ipjustice.org> References: <57A94745-69DE-4628-8168-8F15F1C7D467@icann.org> <50546364-b2fd-bd3d-77a3-f6613a7c33e9@mail.utoronto.ca> <6539E322-F58B-410A-B3D4-A05C6C868113@ipjustice.org> Message-ID: <83d286ea-18e3-760e-548d-b3eb897df46e@mail.utoronto.ca> In which case, I am happy to step back and permit the PC to organize this.? I have reached out to Carlton Samuels, as his collaboration on this is required.? I have not heard back from him, as yet.? Over to you, Rafik. Stephanie On 2020-04-08 5:22 p.m., Robin Gross wrote: > Hi all, > > I?ve add the NCSG-PC onto this thread since it is the PC who will vote > and select our board nominee (pursuant to NCSG Charter). > > Thanks, > Robin > >> On Apr 8, 2020, at 2:20 PM, Stephanie E Perrin via NCSG-EC >> > wrote: >> >> I need to consult you guys, then we (csg and ncsg) need to set up an >> election, where we pick someone to vote for us, and if we get two >> votes for Matthew (ie each side votes for him) we tell staff and >> Council he is our nominee.? It seems a bit clumsy but since we have >> had a meltdown in the past, we needed procedures.... >> >> I presume staff will set up that election for us, will ask Carlos >> Reyes who is now in charge of our policy support, not Mary Wong. >> >> cheers Steph >> >> PS Dean Marks is doing the same thing with the CSG guys. >> >> >> On 2020-04-08 5:16 p.m., Raphael Beauregard-Lacroix wrote: >>> Sure, I'm just not sure what needs to be done! >>> >>> On Wed, Apr 8, 2020 at 1:04 PM Stephanie E Perrin via NCSG-EC >>> > wrote: >>> >>> Hi folks, we need to organize on the election of Matthew Shears >>> for Board seat 14. I have reached out to Carlton Samuels, to >>> tick the box of consulting with our nomcom appointee (no >>> response so far) and I have been chatting with Dean Marks from >>> the CSG, who is keen to cooperate.? We are trying to meet this >>> new deadline of April 20, can we organize to hold our election >>> next week in time to offer our name?? The CSG thinks they can. >>> >>> Sorry to push but we have to get this done faster now due to >>> ICANN's revised timelines....since we are agreed on the >>> candidate, it is just paperwork.... >>> >>> cheers Steph >>> >>> >>> >>> -------- Forwarded Message -------- >>> Subject: PLEASE READ: NCPH election for Board seat 14 >>> Date: Tue, 7 Apr 2020 20:17:14 +0000 >>> From: Mary Wong >>> To: Dean Marks , >>> Stephanie E Perrin >>> , Bruna Martins dos >>> Santos , >>> Joan Kerr , Rafik >>> Dammak , >>> Selli, Claudia >>> , csg-excomm at icann.org >>> >>> , Barbara Wanner >>> >>> CC: Chantelle Doerksen >>> , Maryam Bakoshi >>> , >>> Andrea Glandon >>> , Carlos Reyes >>> >>> >>> >>> >>> Dear CSG and NCSG leaders, >>> >>> >>> I would like to apologize for bringing up this topic at this >>> late stage, and at a time when I know that many community >>> members are focusing on important personal and family matters >>> during the current COVID-19 situation. Please understand that we >>> as staff would not have raised this were it not a Bylaws-related >>> matter. >>> >>> >>> Here is the issue: under the ICANN Bylaws, formal notification >>> of a nominee for either Board seat 13 or 14 must be provided to >>> the Empowered Community Administration at least six (6) months >>> prior to the commencement of that potential Director?s term. As >>> the 2020 Annual General Meeting is due to conclude on 22 October >>> 2020 (which we realize is somewhat earlier than previous AGMs), >>> this means that _the Empowered Community Administration must >>> receive the Non-Contracted Parties House (NCPH) nomination of a >>> Director to fill Board seat 14 by *22 April 2020*_ (and not May >>> as we had advised you previously). >>> >>> >>> I understand that the NCPH?s current plan is to hold the formal >>> vote (via a CSG and NCSG representative and in accordance with >>> the NCPH?s agreed procedures) on or around 29 April. In light of >>> the need to notify the GNSO Chair of the result (as under the >>> GNSO Operating Procedures Keith has the responsibility of >>> notifying the Empowered Community Administration), I would like >>> to ask _if it will be possible for the NCPH to complete its vote >>> on a nominee for Board seat 14 by *Monday 20 April*_, to allow >>> Keith time to inform the GNSO Council (as has been customary) >>> and to formally notify the Empowered Community Administration. >>> >>> >>> I and the whole GNSO support team are sincerely sorry for our >>> previous guidance to you that had mistakenly set 21 May as the >>> final date. Please accept our heartfelt apologies for this rare >>> error as well as for the inconvenience that we know our mistake >>> must cause you and your groups. >>> >>> >>> In view of the situation, please be assured that the CSG and >>> NCSG support staff are happy to assist you with conducting the >>> vote as efficiently and smoothly as possible, to minimize >>> disruption and inconvenience to you. Please let me know if you >>> have any questions or concerns with either the timing or >>> mechanism for the upcoming vote and, once again, I am so very >>> sorry for the trouble. >>> >>> >>> Thank you all very much for your kind understanding. >>> >>> >>> Best regards, >>> >>> Mary >>> >>> >>> >>> _______________________________________________ >>> NCSG-EC mailing list >>> NCSG-EC at lists.ncsg.is >>> https://lists.ncsg.is/mailman/listinfo/ncsg-ec >>> >> _______________________________________________ >> NCSG-EC mailing list >> NCSG-EC at lists.ncsg.is >> https://lists.ncsg.is/mailman/listinfo/ncsg-ec > -------------- next part -------------- An HTML attachment was scrubbed... URL: From rafik.dammak Thu Apr 9 07:58:41 2020 From: rafik.dammak (Rafik Dammak) Date: Thu, 9 Apr 2020 13:58:41 +0900 Subject: [PC-NCSG] [NCSG-EC] Fwd: PLEASE READ: NCPH election for Board seat 14 In-Reply-To: <83d286ea-18e3-760e-548d-b3eb897df46e@mail.utoronto.ca> References: <57A94745-69DE-4628-8168-8F15F1C7D467@icann.org> <50546364-b2fd-bd3d-77a3-f6613a7c33e9@mail.utoronto.ca> <6539E322-F58B-410A-B3D4-A05C6C868113@ipjustice.org> <83d286ea-18e3-760e-548d-b3eb897df46e@mail.utoronto.ca> Message-ID: Thanks Stephanie for sharing the info as first action, I put this as an item for update to our membership in next week policy call, then follow-up in list to ensure that information is shared broadly. with regard to the vote, we can coordinate with all representatives about the support and appoint who will cast the vote on behalf of NCSG. I think the vote by 20th April is doable. Best, Rafik Le jeu. 9 avr. 2020 ? 06:31, Stephanie E Perrin via NCSG-EC < ncsg-ec at lists.ncsg.is> a ?crit : > In which case, I am happy to step back and permit the PC to organize > this. I have reached out to Carlton Samuels, as his collaboration on this > is required. I have not heard back from him, as yet. Over to you, Rafik. > > Stephanie > On 2020-04-08 5:22 p.m., Robin Gross wrote: > > Hi all, > > I?ve add the NCSG-PC onto this thread since it is the PC who will vote and > select our board nominee (pursuant to NCSG Charter). > > Thanks, > Robin > > On Apr 8, 2020, at 2:20 PM, Stephanie E Perrin via NCSG-EC < > ncsg-ec at lists.ncsg.is> wrote: > > I need to consult you guys, then we (csg and ncsg) need to set up an > election, where we pick someone to vote for us, and if we get two votes for > Matthew (ie each side votes for him) we tell staff and Council he is our > nominee. It seems a bit clumsy but since we have had a meltdown in the > past, we needed procedures.... > > I presume staff will set up that election for us, will ask Carlos Reyes > who is now in charge of our policy support, not Mary Wong. > > cheers Steph > > PS Dean Marks is doing the same thing with the CSG guys. > > > On 2020-04-08 5:16 p.m., Raphael Beauregard-Lacroix wrote: > > Sure, I'm just not sure what needs to be done! > > On Wed, Apr 8, 2020 at 1:04 PM Stephanie E Perrin via NCSG-EC < > ncsg-ec at lists.ncsg.is> wrote: > >> Hi folks, we need to organize on the election of Matthew Shears for Board >> seat 14. I have reached out to Carlton Samuels, to tick the box of >> consulting with our nomcom appointee (no response so far) and I have been >> chatting with Dean Marks from the CSG, who is keen to cooperate. We are >> trying to meet this new deadline of April 20, can we organize to hold our >> election next week in time to offer our name? The CSG thinks they can. >> >> Sorry to push but we have to get this done faster now due to ICANN's >> revised timelines....since we are agreed on the candidate, it is just >> paperwork.... >> >> cheers Steph >> >> >> -------- Forwarded Message -------- >> Subject: PLEASE READ: NCPH election for Board seat 14 >> Date: Tue, 7 Apr 2020 20:17:14 +0000 >> From: Mary Wong >> To: Dean Marks , Stephanie E Perrin >> , >> Bruna Martins dos Santos , >> Joan Kerr , Rafik Dammak >> , Selli, Claudia >> , >> csg-excomm at icann.org , >> Barbara Wanner >> CC: Chantelle Doerksen >> , Maryam Bakoshi >> , Andrea Glandon >> , Carlos Reyes >> >> >> Dear CSG and NCSG leaders, >> >> >> I would like to apologize for bringing up this topic at this late stage, >> and at a time when I know that many community members are focusing on >> important personal and family matters during the current COVID-19 >> situation. Please understand that we as staff would not have raised this >> were it not a Bylaws-related matter. >> >> >> Here is the issue: under the ICANN Bylaws, formal notification of a >> nominee for either Board seat 13 or 14 must be provided to the Empowered >> Community Administration at least six (6) months prior to the commencement >> of that potential Director?s term. As the 2020 Annual General Meeting is >> due to conclude on 22 October 2020 (which we realize is somewhat earlier >> than previous AGMs), this means that *the Empowered Community >> Administration must receive the Non-Contracted Parties House (NCPH) >> nomination of a Director to fill Board seat 14 by 22 April 2020* (and >> not May as we had advised you previously). >> >> >> I understand that the NCPH?s current plan is to hold the formal vote (via >> a CSG and NCSG representative and in accordance with the NCPH?s agreed >> procedures) on or around 29 April. In light of the need to notify the GNSO >> Chair of the result (as under the GNSO Operating Procedures Keith has the >> responsibility of notifying the Empowered Community Administration), I >> would like to ask *if it will be possible for the NCPH to complete its >> vote on a nominee for Board seat 14 by Monday 20 April*, to allow Keith >> time to inform the GNSO Council (as has been customary) and to formally >> notify the Empowered Community Administration. >> >> >> I and the whole GNSO support team are sincerely sorry for our previous >> guidance to you that had mistakenly set 21 May as the final date. Please >> accept our heartfelt apologies for this rare error as well as for the >> inconvenience that we know our mistake must cause you and your groups. >> >> >> In view of the situation, please be assured that the CSG and NCSG support >> staff are happy to assist you with conducting the vote as efficiently and >> smoothly as possible, to minimize disruption and inconvenience to you. >> Please let me know if you have any questions or concerns with either the >> timing or mechanism for the upcoming vote and, once again, I am so very >> sorry for the trouble. >> >> >> Thank you all very much for your kind understanding. >> >> >> Best regards, >> >> Mary >> >> >> _______________________________________________ >> NCSG-EC mailing list >> NCSG-EC at lists.ncsg.is >> https://lists.ncsg.is/mailman/listinfo/ncsg-ec >> > _______________________________________________ > NCSG-EC mailing list > NCSG-EC at lists.ncsg.is > https://lists.ncsg.is/mailman/listinfo/ncsg-ec > > > _______________________________________________ > NCSG-EC mailing list > NCSG-EC at lists.ncsg.is > https://lists.ncsg.is/mailman/listinfo/ncsg-ec > -------------- next part -------------- An HTML attachment was scrubbed... URL: From rafik.dammak Thu Apr 9 13:03:22 2020 From: rafik.dammak (Rafik Dammak) Date: Thu, 9 Apr 2020 19:03:22 +0900 Subject: [PC-NCSG] [NCSG-EC] Fwd: PLEASE READ: NCPH election for Board seat 14 In-Reply-To: References: <57A94745-69DE-4628-8168-8F15F1C7D467@icann.org> <50546364-b2fd-bd3d-77a3-f6613a7c33e9@mail.utoronto.ca> <6539E322-F58B-410A-B3D4-A05C6C868113@ipjustice.org> <83d286ea-18e3-760e-548d-b3eb897df46e@mail.utoronto.ca> Message-ID: Addding the correct pc list address On Thu, Apr 9, 2020, 13:58 Rafik Dammak wrote: > Thanks Stephanie for sharing the info > as first action, I put this as an item for update to our membership in > next week policy call, then follow-up in list to ensure that information is > shared broadly. > with regard to the vote, we can coordinate with all representatives about > the support and appoint who will cast the vote on behalf of NCSG. I think > the vote by 20th April is doable. > > Best, > > Rafik > > Le jeu. 9 avr. 2020 ? 06:31, Stephanie E Perrin via NCSG-EC < > ncsg-ec at lists.ncsg.is> a ?crit : > >> In which case, I am happy to step back and permit the PC to organize >> this. I have reached out to Carlton Samuels, as his collaboration on this >> is required. I have not heard back from him, as yet. Over to you, Rafik. >> >> Stephanie >> On 2020-04-08 5:22 p.m., Robin Gross wrote: >> >> Hi all, >> >> I?ve add the NCSG-PC onto this thread since it is the PC who will vote >> and select our board nominee (pursuant to NCSG Charter). >> >> Thanks, >> Robin >> >> On Apr 8, 2020, at 2:20 PM, Stephanie E Perrin via NCSG-EC < >> ncsg-ec at lists.ncsg.is> wrote: >> >> I need to consult you guys, then we (csg and ncsg) need to set up an >> election, where we pick someone to vote for us, and if we get two votes for >> Matthew (ie each side votes for him) we tell staff and Council he is our >> nominee. It seems a bit clumsy but since we have had a meltdown in the >> past, we needed procedures.... >> >> I presume staff will set up that election for us, will ask Carlos Reyes >> who is now in charge of our policy support, not Mary Wong. >> >> cheers Steph >> >> PS Dean Marks is doing the same thing with the CSG guys. >> >> >> On 2020-04-08 5:16 p.m., Raphael Beauregard-Lacroix wrote: >> >> Sure, I'm just not sure what needs to be done! >> >> On Wed, Apr 8, 2020 at 1:04 PM Stephanie E Perrin via NCSG-EC < >> ncsg-ec at lists.ncsg.is> wrote: >> >>> Hi folks, we need to organize on the election of Matthew Shears for >>> Board seat 14. I have reached out to Carlton Samuels, to tick the box of >>> consulting with our nomcom appointee (no response so far) and I have been >>> chatting with Dean Marks from the CSG, who is keen to cooperate. We are >>> trying to meet this new deadline of April 20, can we organize to hold our >>> election next week in time to offer our name? The CSG thinks they can. >>> >>> Sorry to push but we have to get this done faster now due to ICANN's >>> revised timelines....since we are agreed on the candidate, it is just >>> paperwork.... >>> >>> cheers Steph >>> >>> >>> -------- Forwarded Message -------- >>> Subject: PLEASE READ: NCPH election for Board seat 14 >>> Date: Tue, 7 Apr 2020 20:17:14 +0000 >>> From: Mary Wong >>> To: Dean Marks , Stephanie E >>> Perrin >>> , Bruna Martins dos Santos >>> , Joan Kerr >>> , Rafik Dammak >>> , Selli, Claudia >>> , >>> csg-excomm at icann.org , >>> Barbara Wanner >>> CC: Chantelle Doerksen >>> , Maryam Bakoshi >>> , Andrea Glandon >>> , Carlos Reyes >>> >>> >>> Dear CSG and NCSG leaders, >>> >>> >>> I would like to apologize for bringing up this topic at this late stage, >>> and at a time when I know that many community members are focusing on >>> important personal and family matters during the current COVID-19 >>> situation. Please understand that we as staff would not have raised this >>> were it not a Bylaws-related matter. >>> >>> >>> Here is the issue: under the ICANN Bylaws, formal notification of a >>> nominee for either Board seat 13 or 14 must be provided to the Empowered >>> Community Administration at least six (6) months prior to the commencement >>> of that potential Director?s term. As the 2020 Annual General Meeting is >>> due to conclude on 22 October 2020 (which we realize is somewhat earlier >>> than previous AGMs), this means that *the Empowered Community >>> Administration must receive the Non-Contracted Parties House (NCPH) >>> nomination of a Director to fill Board seat 14 by 22 April 2020* (and >>> not May as we had advised you previously). >>> >>> >>> I understand that the NCPH?s current plan is to hold the formal vote >>> (via a CSG and NCSG representative and in accordance with the NCPH?s agreed >>> procedures) on or around 29 April. In light of the need to notify the GNSO >>> Chair of the result (as under the GNSO Operating Procedures Keith has the >>> responsibility of notifying the Empowered Community Administration), I >>> would like to ask *if it will be possible for the NCPH to complete its >>> vote on a nominee for Board seat 14 by Monday 20 April*, to allow Keith >>> time to inform the GNSO Council (as has been customary) and to formally >>> notify the Empowered Community Administration. >>> >>> >>> I and the whole GNSO support team are sincerely sorry for our previous >>> guidance to you that had mistakenly set 21 May as the final date. Please >>> accept our heartfelt apologies for this rare error as well as for the >>> inconvenience that we know our mistake must cause you and your groups. >>> >>> >>> In view of the situation, please be assured that the CSG and NCSG >>> support staff are happy to assist you with conducting the vote as >>> efficiently and smoothly as possible, to minimize disruption and >>> inconvenience to you. Please let me know if you have any questions or >>> concerns with either the timing or mechanism for the upcoming vote and, >>> once again, I am so very sorry for the trouble. >>> >>> >>> Thank you all very much for your kind understanding. >>> >>> >>> Best regards, >>> >>> Mary >>> >>> >>> _______________________________________________ >>> NCSG-EC mailing list >>> NCSG-EC at lists.ncsg.is >>> https://lists.ncsg.is/mailman/listinfo/ncsg-ec >>> >> _______________________________________________ >> NCSG-EC mailing list >> NCSG-EC at lists.ncsg.is >> https://lists.ncsg.is/mailman/listinfo/ncsg-ec >> >> >> _______________________________________________ >> NCSG-EC mailing list >> NCSG-EC at lists.ncsg.is >> https://lists.ncsg.is/mailman/listinfo/ncsg-ec >> > -------------- next part -------------- An HTML attachment was scrubbed... URL: From rafik.dammak at gmail.com Wed Apr 1 13:10:25 2020 From: rafik.dammak at gmail.com (Rafik Dammak) Date: Wed, 1 Apr 2020 19:10:25 +0900 Subject: [NCSG-PC] [NCSG-Discuss] Action required_NCSG Draft Comment on Draft Proposal for NextGen@ICANN Program Improvements In-Reply-To: References: Message-ID: Hi all, seeing no objection and several expressions of support, I will submit the comment. Thanks, Best, Rafik Le mar. 31 mars 2020 ? 20:26, Rafik Dammak a ?crit : > hi all, > > reminder to review the draft comment. > > Best, > > Rafik > > > Le lun. 30 mars 2020 ? 08:44, Rafik Dammak a > ?crit : > >> thanks all, >> just reminder that deadline for submission is 31st Marc, last change to >> review the draft and express any concern. >> >> Best, >> >> Rafik >> >> Le sam. 28 mars 2020 ? 02:07, Tatiana Tropina >> a ?crit : >> >>> No objection from me either -- thanks Olga! >>> Warm regards, >>> Tanya >>> >>> >>> On Fri, 27 Mar 2020 at 18:00, Oreoluwa Somolu Lesi >>> wrote: >>> >>>> This is a nicely put-together comment and I have no objection to it. >>>> >>>> Kind regards, >>>> Ore >>>> -- >>>> Oreoluwa Lesi >>>> Executive Director, Women's Technology Empowerment Centre (W.TEC) >>>> +234.803.621.1307, +234.813.339.9999 | www.wtec.org.ng >>>> | @wteconline >>>> >>>> >>>> On 27/03/2020 5:18 pm, James Gannon wrote: >>>> >>>> No objection here too >>>> >>>> Sent from my iPhone >>>> >>>> On 27 Mar 2020, at 15:52, Liz Orembo >>>> wrote: >>>> >>>> ? >>>> Me too. No major objections. >>>> >>>> On Fri, Mar 27, 2020 at 6:37 PM Juan Manuel Rojas via NCSG-PC < >>>> ncsg-pc at lists.ncsg.is> wrote: >>>> >>>>> Dear all, >>>>> I have read the comment and I have no objections to being sent. >>>>> >>>>> JUAN MANUEL ROJAS P. >>>>> Presidente - AGEIA DENSI Colombia >>>>> GNSO Councilor - ICANN >>>>> Cluster Orinoco TIC member >>>>> Master IT candidate, Universidad de los Andes >>>>> >>>>> Cel. +57 3017435600 >>>>> Twitter: @JmanuRojas >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> El viernes, 27 de marzo de 2020 01:34:45 a. m. GMT-5, Farell FOLLY < >>>>> farell at benin2point0.org> escribi?: >>>>> >>>>> >>>>> Dear All, >>>>> >>>>> Thank you very much for pulling this together. I believe that the >>>>> current content addresses all the very important point around the Next-Gen >>>>> program. Others should review it ASAP, otherwise; it is good shape to be >>>>> submitted part from typos or minors. >>>>> >>>>> @__f_f__ >>>>> >>>>> Best Regards >>>>> ____________________________________ >>>>> >>>>> (Ekue) Farell FOLLY >>>>> GNSO Councillor >>>>> linkedin.com/in/farellf >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> On 26 Mar 2020, at 00:28, Rafik Dammak wrote: >>>>> >>>>> hi all, >>>>> >>>>> we have a public comment draft for review and endorsement. >>>>> the deadline for submission is the 31st March. >>>>> >>>>> Best. >>>>> >>>>> Rafik >>>>> >>>>> ---------- Forwarded message --------- >>>>> De : *Olga Kyryliuk* >>>>> Date: jeu. 26 mars 2020 ? 00:23 >>>>> Subject: [NCSG-Discuss] Action required_NCSG Draft Comment on Draft >>>>> Proposal for NextGen at ICANN Program Improvements >>>>> To: >>>>> >>>>> >>>>> Dear All, >>>>> >>>>> We have prepared a draft NCSG comment >>>>> to >>>>> the Draft Proposal for NextGen at ICANN Program Improvements. The >>>>> deadline for submission is 31 March. We also need to leave some time for >>>>> the PC to approve the comment. >>>>> >>>>> Please, take a moment to review the draft and leave your >>>>> edits/comments in track changes for easier reference. We will be waiting >>>>> for your contributions *till Friday, 27 March, end of the day*. >>>>> >>>>> Thanks in advance! >>>>> >>>>> Best, >>>>> Olga >>>>> _______________________________________________ >>>>> NCSG-PC mailing list >>>>> NCSG-PC at lists.ncsg.is >>>>> https://lists.ncsg.is/mailman/listinfo/ncsg-pc >>>>> >>>>> >>>>> _______________________________________________ >>>>> NCSG-PC mailing list >>>>> NCSG-PC at lists.ncsg.is >>>>> https://lists.ncsg.is/mailman/listinfo/ncsg-pc >>>>> _______________________________________________ >>>>> NCSG-PC mailing list >>>>> NCSG-PC at lists.ncsg.is >>>>> https://lists.ncsg.is/mailman/listinfo/ncsg-pc >>>>> >>>> >>>> >>>> -- >>>> >>>> Best regards. >>>> Liz. >>>> >>>> PGP ID: 0x1F3488BF >>>> _______________________________________________ >>>> NCSG-PC mailing list >>>> NCSG-PC at lists.ncsg.is >>>> https://lists.ncsg.is/mailman/listinfo/ncsg-pc >>>> >>>> >>>> _______________________________________________ >>>> NCSG-PC mailing listNCSG-PC at lists.ncsg.ishttps://lists.ncsg.is/mailman/listinfo/ncsg-pc >>>> >>>> >>>> _______________________________________________ >>>> NCSG-PC mailing list >>>> NCSG-PC at lists.ncsg.is >>>> https://lists.ncsg.is/mailman/listinfo/ncsg-pc >>>> >>> _______________________________________________ >>> NCSG-PC mailing list >>> NCSG-PC at lists.ncsg.is >>> https://lists.ncsg.is/mailman/listinfo/ncsg-pc >>> >> -------------- next part -------------- An HTML attachment was scrubbed... URL: From maryam.bakoshi at icann.org Wed Apr 1 15:28:48 2020 From: maryam.bakoshi at icann.org (Maryam Bakoshi) Date: Wed, 1 Apr 2020 12:28:48 +0000 Subject: [NCSG-PC] Proposed NCSG Policy calls until AGM 2020 Message-ID: <1AC6CFA4-4502-40A9-AE8D-2249828CE500@icann.org> Dear all, As requested by Rafik, please find proposed NCSG Policy calls until AGM 2020 Proposed time: 12:00 UTC Tuesday, 14 April Tuesday, 19 May Tuesday, 23 June (tentative as it?s ICANN68 week) Tuesday, 21 July Tuesday, 18 August Tuesday, 22 September Once you confirm, I will send a calendar invite for the agreed dates. Many thanks, -- Maryam Bakoshi | SO/AC Collaboration Services Sr. Coordinator ICANN | Internet Corporation for Assigned Names and Numbers S: Maryam.bakoshi.icann | T: +44 7846 471777 -------------- next part -------------- An HTML attachment was scrubbed... URL: From rafik.dammak at gmail.com Wed Apr 1 16:41:09 2020 From: rafik.dammak at gmail.com (Rafik Dammak) Date: Wed, 1 Apr 2020 22:41:09 +0900 Subject: [NCSG-PC] [Public Comments] Call for Volunteers for NCSG Comment on Name Collision Analysis Project (NCAP) Study 1 In-Reply-To: References: <96FA7067-0C34-4DD4-A710-E84348CB278A@benin2point0.org> Message-ID: Hi all, reminder to review the draft comment (short one). please raise concern if you have any, Best, Rafik Le mar. 31 mars 2020 ? 20:25, Rafik Dammak a ?crit : > hi all, > > reminder to review the draft comment. > > Best, > > Rafik > Le lun. 30 mars 2020 ? 22:49, Rafik Dammak a > ?crit : > >> >> Hi all, >> >> We have this draft comment for your review. >> >> Best, >> >> Rafik >> >> ---------- Forwarded message --------- >> From: Farell FOLLY >> Date: Mon, Mar 30, 2020, 03:51 >> Subject: Re: [Public Comments] Call for Volunteers for NCSG Comment on >> Name Collision Analysis Project (NCAP) Study 1 >> To: Rafik Dammak >> Cc: NCSG-DISCUSS at listserv.syr.edu >> >> >> Dear all, >> >> Due to the approaching deadline, Rafik and I worked to propose a draft >> response >> to >> this Public comment and would like to gather your inputs for the draft >> report >> published >> by the contractor (Karen Scarfone, Scarfone Cybersecurity) for Study 1 for >> the Name Collision Analysis Project. Please note that there are only 2 days >> (even less) lefts for the PC to be closed. The report is very brief, one >> page long. >> >> What is needed from you: >> >> >> 1. Do you think that this study (Study 1 of 3) was broad enough to >> include all prior works related to the Name Collisions related issues? >> 2. According to you, is the approach used efficient? >> >> >> For a quick background on the topic: >> >> 1) In October 2018 the BTC asked for OCTO?s assessment of the NCAP >> proposal, which OCTO provided on 27 November 2018. Subsequently, OCTO and >> SSAC had discussions that provided additional information and further >> clarification to OCTO on the details of the proposal. OCTO provided its >> assessment on all three studies that comprise the NCAP proposal. In that >> assessment, OCTO expressed concerns about the scope of Study 1, that the >> goals of Studies 2 and 3 might not be achievable, and that the overall >> project might not ultimately provide the necessary information to the Board >> to make decisions on whether or not a TLD is a ?collision string? and can >> be safely delegated. OCTO also noted the high cost and long duration of the >> overall project. (Source) >> >> 2) Study 1 (subjected to this call for Public Comment) is focused on >> performing a survey of all the research that has been undertaken in the >> area of name collision since 2014 and evaluating if this work could meet, >> or assist in meeting, the objectives set out in the Board resolutions. The >> study includes a decision on if the project should proceed based on the >> results of the survey and the availability of data necessary to perform >> Studies 2 and 3. Study 1 also calls for creating a data repository and >> associated policies and processes to store data necessary for use in >> subsequent studies. (Source) >> >> 3) In July 2019, ICANN publishes a call for applications to select a >> contractor to conduct Study 1. Details can be found here >> . >> 4) The RFC for proposal that outline the requirements that the >> contractor in 3) should meet is available here >> >> . >> >> 5) Our draft response is available through this link >> >> . >> >> >> That is all?.by now ;) >> >> @__f_f__ >> >> Best Regards >> ____________________________________ >> >> (Ekue) Farell FOLLY >> GNSO Councillor >> linkedin.com/in/farellf >> >> >> >> >> >> >> On 14 Feb 2020, at 02:52, Rafik Dammak wrote: >> >> Hi all >> >> ICANN just published a consultation on Name Collision Analysis Project >> (NCAP) Study 1. You can find here all the details here >> https://www.icann.org/public-comments/ncap-study-1-2020-02-13-en . We >> preciously commented on NCAP plan and so this is an opportunity to comment >> on the study and follow-up. >> >> I created this google doc to be used during the drafting and accessible >> to all in order to kick off the discussion and comments: >> https://docs.google.com/document/d/1_27iFmqrAnVJ7Aq1jedo9CmBlb6MbBFq-roaMpb-xGU/edit >> >> >> Please let me offline if you want to volunteer to participate in drafting >> the NCSG comment and join the drafting team. For those interested by the >> policy and technology discussion, this is a good topic to review and work >> on drafting a comment. >> >> You can find previous public comments submitted by NCSG in this wiki page >> https://community.icann.org/display/gnsononcomstake/Public+Comments+-+2020 and >> listing those who drafted them. >> >> Best Regards, >> >> Rafik Dammak >> >> NCSG Policy Committee Chair >> >> >> -------------- next part -------------- An HTML attachment was scrubbed... URL: From rafik.dammak at gmail.com Wed Apr 1 16:43:26 2020 From: rafik.dammak at gmail.com (Rafik Dammak) Date: Wed, 1 Apr 2020 22:43:26 +0900 Subject: [NCSG-PC] NCSG Policy Committee meeting follow-up In-Reply-To: <5e73d75d.1c69fb81.a3faa.0b10SMTPIN_ADDED_MISSING@mx.google.com> References: <1584644768.209537000.w24hbddb@frv50.fwdcdn.com> <5e73d75d.1c69fb81.a3faa.0b10SMTPIN_ADDED_MISSING@mx.google.com> Message-ID: Hi all, thanks for the comments. with no objection, I guess next step it is to circulate a draft plan/timeline for the selection and get that done quickly as possible. I acknowledge the current situation impacting and I think we can proceed giving enough time to everyone. Best, Rafik Le ven. 20 mars 2020 ? 05:34, oreoluwa a ?crit : > Hi Rafik and everyone, > > I have no objections. > > Kind regards > Ore > > > > -- > Oreoluwa Lesi > Executive Director, Women's Technology Empowerment Centre (W.TEC) > www.wtec.org.ng | @wteconline > > > Sent from my Samsung Galaxy smartphone. > > > -------- Original message -------- > From: Olga Kyryliuk > Date: 19/03/2020 20:07 (GMT+01:00) > To: Rafik Dammak > Cc: ncsg-pc > Subject: Re: [NCSG-PC] NCSG Policy Committee meeting follow-up > > Hi Rafik, > > Sounds good. No objection from my side. > > Best, > Olga > > > *16 ????? 2020, 09:06:54, ?? "Rafik Dammak" >:* > > Hi all, > > sending reminder to ask for input. if there is no objection, we can start > quickly the NCSG PC chair election and vice-chairs selection. > > Best, > > Rafik > > Le jeu. 5 mars 2020 ? 07:50, Rafik Dammak a > ?crit : > > Thanks Farell, > looking to hear from others too. it is possible to have staggered terms > but need to think how to implement that since it is the beginning and > according to chater it is 1 year term. > > Best, > > Rafik > > Le jeu. 5 mars 2020 ? 04:22, Farell FOLLY a > ?crit : > > Hello All, > > Thanks Rafik for organizing this. I am sorry to have missed.. Something > went wrong?. > > I have listened to the audio and I am glad to note all that have been > discussed is wonderful. > > I would be open to apply for any vice - chair position (it appears that > most of the experienced members are currently term-limited) or as a liaison > to council. Also, with my project management background, I could help on > managing and following tasks, identifying risks and setting priorities. > > I would also like to recommend that the terms of the vice chairs are set > in a way that chair and vice chairs could all leave their seats after one > election? I mean that it should never happen the terms of the VC and chair > come to end at the same time. > > > > @__f_f__ > > Best Regards > ____________________________________ > > (Ekue) Farell FOLLY > GNSO Councillor > linkedin.com/in/farellf > > > > > > > On 2 Mar 2020, at 01:35, Rafik Dammak wrote: > > Hi all, > > as you know we had last week our PC meeting to discuss several items > regarding election, improvements etc. We got already some action item to > follow-up > > 1- PC chair Election: there was agreement to go with the idea of having > chair and 2 vice-chairs. The point was also to have proper open process > (that can be documented for future). so the action here is to agree on > timeline and process (nomination, vote). it shouldn't be complicated. I > believe we can get this done in this month e.g. 1 week for nomination and 1 > week for voting. > 2- Having a regular PC call, hopefully monthly call and coordinating more > with our NCSG reps to council. The action would be to agree on regular > day/time. I think that can be 2 weeks after NCSG Policy. > 3- Regarding documentation and development of workflow, I believe that can > be done with reworking again on PC operating procedure and documenting > previous activities. I am sharing here the PC operating procedures draft > being worked on before > https://docs.google.com/document/d/1G_M4wBGVEyXm30m79olplfF0RNkJnDwaVBBeldDfO8U/edit > . For anything missing, we can start first to identify that and have > volunteers to draft it. For Chair job description, I can use what I > presented and develop a draft. > 4- Sharing here the slides I presented in last call: > https://docs.google.com/presentation/d/1SnpMYmb6lTw1FqO6tvSqCdpgL-QMg1DJXIJGrx8vB6A/edit#slide=id.p > 5- for NCSG Policy call improvements, we will have the NCSG Policy call in > coming days and I will try to make some adjustments to extent of possible. > It might be shorter than usual as we will have NCSG meeting next week. From > April NCSG Policy call, we can start identifying other topics we would like > to cover other than council meeting and usual policy updates. > > One activity we will need to do soon and follow-up is to work about > prioritization. GNSO Council will discuss the GNSO future work soon and we > need to be ready and align our work around that. That also aligns with the > discussion we had about prioritizing our work and it starts with > identifying what is in the pipeline. > > let me know if I missed anything. > > Best. > > Rafik > > _______________________________________________ > NCSG-PC mailing list > NCSG-PC at lists.ncsg.is > https://lists.ncsg.is/mailman/listinfo/ncsg-pc > > _______________________________________________ > NCSG-PC mailing listNCSG-PC at lists.ncsg.ishttps://lists.ncsg.is/mailman/listinfo/ncsg-pc > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From lists at icann.guru Wed Apr 1 20:16:50 2020 From: lists at icann.guru (James Gannon) Date: Wed, 1 Apr 2020 17:16:50 +0000 Subject: [NCSG-PC] Proposed NCSG Policy calls until AGM 2020 In-Reply-To: <1AC6CFA4-4502-40A9-AE8D-2249828CE500@icann.org> References: <1AC6CFA4-4502-40A9-AE8D-2249828CE500@icann.org> Message-ID: If we can get these to 60mins calls then that?s great, longer than that and I will be very tentative for all of them --- James Gannon From: NCSG-PC on behalf of Maryam Bakoshi Date: Wednesday, 1 April 2020 at 13:29 To: NCSG PC Subject: [NCSG-PC] Proposed NCSG Policy calls until AGM 2020 Dear all, As requested by Rafik, please find proposed NCSG Policy calls until AGM 2020 Proposed time: 12:00 UTC Tuesday, 14 April Tuesday, 19 May Tuesday, 23 June (tentative as it?s ICANN68 week) Tuesday, 21 July Tuesday, 18 August Tuesday, 22 September Once you confirm, I will send a calendar invite for the agreed dates. Many thanks, -- Maryam Bakoshi | SO/AC Collaboration Services Sr. Coordinator ICANN | Internet Corporation for Assigned Names and Numbers S: Maryam.bakoshi.icann | T: +44 7846 471777 -------------- next part -------------- An HTML attachment was scrubbed... URL: From stephanie.perrin at mail.utoronto.ca Wed Apr 1 21:48:41 2020 From: stephanie.perrin at mail.utoronto.ca (Stephanie E Perrin) Date: Wed, 1 Apr 2020 14:48:41 -0400 Subject: [NCSG-PC] Proposed NCSG Policy calls until AGM 2020 In-Reply-To: References: <1AC6CFA4-4502-40A9-AE8D-2249828CE500@icann.org> Message-ID: I understand the benefits of a regularly scheduled time....and I know 12 UTC is a compromise for the time zone split.? I do wonder if rotation is not a good idea though.....for anyone who finds Tuesday a bad day for any reason (staff meetings, teaching, whatever) it seems more fair to vary the schedule to accommodate folks. Stephanie On 2020-04-01 1:16 p.m., James Gannon wrote: > > If we can get these to 60mins calls then that?s great, longer than > that and I will be very tentative for all of them > > --- > > *James?Gannon* > > *From: *NCSG-PC on behalf of Maryam > Bakoshi > *Date: *Wednesday, 1 April 2020 at 13:29 > *To: *NCSG PC > *Subject: *[NCSG-PC] Proposed NCSG Policy calls until AGM 2020 > > Dear all, > > As requested by Rafik, please find proposed NCSG Policy calls until > AGM 2020 > > *Proposed time: 12:00 UTC * > > Tuesday, 14 April > > Tuesday, 19 May > > Tuesday, 23 June (tentative as it?s ICANN68 week) > > Tuesday, 21 July > > Tuesday, 18 August > > Tuesday, 22 September > > Once you confirm, I will send a calendar invite for the agreed dates. > > Many thanks, > > -- > > *Maryam Bakoshi*?| SO/AC Collaboration Services Sr. Coordinator > > *ICANN*?| Internet Corporation for Assigned Names and Numbers > > *S*: Maryam.bakoshi.icann | *T*:?+44 7846 471777 > > > _______________________________________________ > NCSG-PC mailing list > NCSG-PC at lists.ncsg.is > https://lists.ncsg.is/mailman/listinfo/ncsg-pc -------------- next part -------------- An HTML attachment was scrubbed... URL: From rafik.dammak at gmail.com Thu Apr 2 12:50:44 2020 From: rafik.dammak at gmail.com (Rafik Dammak) Date: Thu, 2 Apr 2020 18:50:44 +0900 Subject: [NCSG-PC] [Public Comments] Call for Volunteers for NCSG Comment on Name Collision Analysis Project (NCAP) Study 1 In-Reply-To: References: <96FA7067-0C34-4DD4-A710-E84348CB278A@benin2point0.org> Message-ID: Hi all, hearing no objection, I will submit the comment by end of the day. Best, Rafik Le mer. 1 avr. 2020 ? 22:41, Rafik Dammak a ?crit : > Hi all, > > reminder to review the draft comment (short one). please raise concern if > you have any, > > Best, > > Rafik > > Le mar. 31 mars 2020 ? 20:25, Rafik Dammak a > ?crit : > >> hi all, >> >> reminder to review the draft comment. >> >> Best, >> >> Rafik >> Le lun. 30 mars 2020 ? 22:49, Rafik Dammak a >> ?crit : >> >>> >>> Hi all, >>> >>> We have this draft comment for your review. >>> >>> Best, >>> >>> Rafik >>> >>> ---------- Forwarded message --------- >>> From: Farell FOLLY >>> Date: Mon, Mar 30, 2020, 03:51 >>> Subject: Re: [Public Comments] Call for Volunteers for NCSG Comment on >>> Name Collision Analysis Project (NCAP) Study 1 >>> To: Rafik Dammak >>> Cc: NCSG-DISCUSS at listserv.syr.edu >>> >>> >>> Dear all, >>> >>> Due to the approaching deadline, Rafik and I worked to propose a draft >>> response >>> to >>> this Public comment and would like to gather your inputs for the draft >>> report >>> published >>> by the contractor (Karen Scarfone, Scarfone Cybersecurity) for Study 1 for >>> the Name Collision Analysis Project. Please note that there are only 2 days >>> (even less) lefts for the PC to be closed. The report is very brief, one >>> page long. >>> >>> What is needed from you: >>> >>> >>> 1. Do you think that this study (Study 1 of 3) was broad enough to >>> include all prior works related to the Name Collisions related issues? >>> 2. According to you, is the approach used efficient? >>> >>> >>> For a quick background on the topic: >>> >>> 1) In October 2018 the BTC asked for OCTO?s assessment of the NCAP >>> proposal, which OCTO provided on 27 November 2018. Subsequently, OCTO and >>> SSAC had discussions that provided additional information and further >>> clarification to OCTO on the details of the proposal. OCTO provided its >>> assessment on all three studies that comprise the NCAP proposal. In that >>> assessment, OCTO expressed concerns about the scope of Study 1, that the >>> goals of Studies 2 and 3 might not be achievable, and that the overall >>> project might not ultimately provide the necessary information to the Board >>> to make decisions on whether or not a TLD is a ?collision string? and can >>> be safely delegated. OCTO also noted the high cost and long duration of the >>> overall project. (Source) >>> >>> 2) Study 1 (subjected to this call for Public Comment) is focused on >>> performing a survey of all the research that has been undertaken in the >>> area of name collision since 2014 and evaluating if this work could meet, >>> or assist in meeting, the objectives set out in the Board resolutions. The >>> study includes a decision on if the project should proceed based on the >>> results of the survey and the availability of data necessary to perform >>> Studies 2 and 3. Study 1 also calls for creating a data repository and >>> associated policies and processes to store data necessary for use in >>> subsequent studies. (Source) >>> >>> 3) In July 2019, ICANN publishes a call for applications to select a >>> contractor to conduct Study 1. Details can be found here >>> . >>> 4) The RFC for proposal that outline the requirements that the >>> contractor in 3) should meet is available here >>> >>> . >>> >>> 5) Our draft response is available through this link >>> >>> . >>> >>> >>> That is all?.by now ;) >>> >>> @__f_f__ >>> >>> Best Regards >>> ____________________________________ >>> >>> (Ekue) Farell FOLLY >>> GNSO Councillor >>> linkedin.com/in/farellf >>> >>> >>> >>> >>> >>> >>> On 14 Feb 2020, at 02:52, Rafik Dammak wrote: >>> >>> Hi all >>> >>> ICANN just published a consultation on Name Collision Analysis Project >>> (NCAP) Study 1. You can find here all the details here >>> https://www.icann.org/public-comments/ncap-study-1-2020-02-13-en . We >>> preciously commented on NCAP plan and so this is an opportunity to comment >>> on the study and follow-up. >>> >>> I created this google doc to be used during the drafting and accessible >>> to all in order to kick off the discussion and comments: >>> https://docs.google.com/document/d/1_27iFmqrAnVJ7Aq1jedo9CmBlb6MbBFq-roaMpb-xGU/edit >>> >>> >>> Please let me offline if you want to volunteer to participate in >>> drafting the NCSG comment and join the drafting team. For those interested >>> by the policy and technology discussion, this is a good topic to review and >>> work on drafting a comment. >>> >>> You can find previous public comments submitted by NCSG in this wiki >>> page >>> https://community.icann.org/display/gnsononcomstake/Public+Comments+-+2020 and >>> listing those who drafted them. >>> >>> Best Regards, >>> >>> Rafik Dammak >>> >>> NCSG Policy Committee Chair >>> >>> >>> -------------- next part -------------- An HTML attachment was scrubbed... URL: From olga_kyryliuk at ukr.net Thu Apr 2 23:49:54 2020 From: olga_kyryliuk at ukr.net (Olga Kyryliuk) Date: Thu, 02 Apr 2020 23:49:54 +0300 Subject: [NCSG-PC] Proposed NCSG Policy calls until AGM 2020 In-Reply-To: References: <1AC6CFA4-4502-40A9-AE8D-2249828CE500@icann.org> Message-ID: <1585860390.331731000.xphbsjhi@frv50.fwdcdn.com> I would agree with Stephanie. Even at the moment it is difficult to know what can be the commitments for those specific dates. Maybe we could agree on specific date of the next call during each call we have? At least everyone could fastly check the personal calendar and be sure that there are no other clashing commitments for that day. Best, Olga? 1 ?????? 2020, 21:48:56, ?? "Stephanie E Perrin" : I understand the benefits of a regularly scheduled time....and I know 12 UTC is a compromise for the time zone split.? I do wonder if rotation is not a good idea though.....for anyone who finds Tuesday a bad day for any reason (staff meetings, teaching, whatever) it seems more fair to vary the schedule to accommodate folks. Stephanie On 2020-04-01 1:16 p.m., James Gannon wrote: If we can get these to 60mins calls then that?s great, longer than that and I will be very tentative for all of them --- James?Gannon From: NCSG-PC on behalf of Maryam Bakoshi Date: Wednesday, 1 April 2020 at 13:29 To: NCSG PC Subject: [NCSG-PC] Proposed NCSG Policy calls until AGM 2020 Dear all, As requested by Rafik, please find proposed NCSG Policy calls until AGM 2020 Proposed time: 12:00 UTC? Tuesday, 14 April? Tuesday, 19 May? Tuesday, 23 June (tentative as it?s ICANN68 week) Tuesday, 21 July Tuesday, 18 August Tuesday, 22 September Once you confirm, I will send a calendar invite for the agreed dates. Many thanks, --? Maryam Bakoshi?| SO/AC Collaboration Services Sr. Coordinator? ICANN?| Internet Corporation for Assigned Names and Numbers? S: Maryam.bakoshi.icann |?T:?+44 7846 471777 _______________________________________________ NCSG-PC mailing list NCSG-PC at lists.ncsg.is https://lists.ncsg.is/mailman/listinfo/ncsg-pc _______________________________________________ NCSG-PC mailing list NCSG-PC at lists.ncsg.is https://lists.ncsg.is/mailman/listinfo/ncsg-pc -------------- next part -------------- An HTML attachment was scrubbed... URL: From lists at icann.guru Fri Apr 3 01:27:47 2020 From: lists at icann.guru (James Gannon) Date: Thu, 2 Apr 2020 22:27:47 +0000 Subject: [NCSG-PC] Proposed NCSG Policy calls until AGM 2020 In-Reply-To: <1585860390.331731000.xphbsjhi@frv50.fwdcdn.com> References: <1AC6CFA4-4502-40A9-AE8D-2249828CE500@icann.org> <1585860390.331731000.xphbsjhi@frv50.fwdcdn.com> Message-ID: Im the opposite, with a very busy work calendar unless we are scheduling these as early as possible its impossible for me to take 1-2 hours out of the middle of a workday, particularly at the moment in current circumstances. --- James Gannon From: NCSG-PC on behalf of Olga Kyryliuk Date: Thursday, 2 April 2020 at 21:50 To: Stephanie E Perrin Cc: "ncsg-pc at lists.ncsg.is" Subject: Re: [NCSG-PC] Proposed NCSG Policy calls until AGM 2020 I would agree with Stephanie. Even at the moment it is difficult to know what can be the commitments for those specific dates. Maybe we could agree on specific date of the next call during each call we have? At least everyone could fastly check the personal calendar and be sure that there are no other clashing commitments for that day. Best, Olga 1 ?????? 2020, 21:48:56, ?? "Stephanie E Perrin" >: I understand the benefits of a regularly scheduled time....and I know 12 UTC is a compromise for the time zone split. I do wonder if rotation is not a good idea though.....for anyone who finds Tuesday a bad day for any reason (staff meetings, teaching, whatever) it seems more fair to vary the schedule to accommodate folks. Stephanie On 2020-04-01 1:16 p.m., James Gannon wrote: If we can get these to 60mins calls then that?s great, longer than that and I will be very tentative for all of them --- James Gannon From: NCSG-PC on behalf of Maryam Bakoshi Date: Wednesday, 1 April 2020 at 13:29 To: NCSG PC Subject: [NCSG-PC] Proposed NCSG Policy calls until AGM 2020 Dear all, As requested by Rafik, please find proposed NCSG Policy calls until AGM 2020 Proposed time: 12:00 UTC Tuesday, 14 April Tuesday, 19 May Tuesday, 23 June (tentative as it?s ICANN68 week) Tuesday, 21 July Tuesday, 18 August Tuesday, 22 September Once you confirm, I will send a calendar invite for the agreed dates. Many thanks, -- Maryam Bakoshi | SO/AC Collaboration Services Sr. Coordinator ICANN | Internet Corporation for Assigned Names and Numbers S: Maryam.bakoshi.icann | T: +44 7846 471777 _______________________________________________ NCSG-PC mailing list NCSG-PC at lists.ncsg.is https://lists.ncsg.is/mailman/listinfo/ncsg-pc _______________________________________________ NCSG-PC mailing list NCSG-PC at lists.ncsg.is https://lists.ncsg.is/mailman/listinfo/ncsg-pc -------------- next part -------------- An HTML attachment was scrubbed... URL: From stephanie at digitaldiscretion.ca Fri Apr 3 06:14:48 2020 From: stephanie at digitaldiscretion.ca (Stephanie Perrin) Date: Thu, 2 Apr 2020 23:14:48 -0400 Subject: [NCSG-PC] Proposed NCSG Policy calls until AGM 2020 In-Reply-To: References: Message-ID: <21F0DA40-DBEA-4BCF-A964-EB244FB43CB4@digitaldiscretion.ca> I understand that james, what i am saying is vary the day. Set The whole year if you like, but make it tuesday in april, wednesday in may, thursday june etc. I would also toggle the time the odd time Sent from my iPhone > On Apr 1, 2020, at 13:17, James Gannon wrote: > > ? > If we can get these to 60mins calls then that?s great, longer than that and I will be very tentative for all of them > > --- > James Gannon > > From: NCSG-PC on behalf of Maryam Bakoshi > Date: Wednesday, 1 April 2020 at 13:29 > To: NCSG PC > Subject: [NCSG-PC] Proposed NCSG Policy calls until AGM 2020 > > Dear all, > > As requested by Rafik, please find proposed NCSG Policy calls until AGM 2020 > Proposed time: 12:00 UTC > Tuesday, 14 April > Tuesday, 19 May > Tuesday, 23 June (tentative as it?s ICANN68 week) > Tuesday, 21 July > Tuesday, 18 August > Tuesday, 22 September > Once you confirm, I will send a calendar invite for the agreed dates. > > Many thanks, > -- > > Maryam Bakoshi | SO/AC Collaboration Services Sr. Coordinator > ICANN | Internet Corporation for Assigned Names and Numbers > S: Maryam.bakoshi.icann | T: +44 7846 471777 > > _______________________________________________ > NCSG-PC mailing list > NCSG-PC at lists.ncsg.is > https://lists.ncsg.is/mailman/listinfo/ncsg-pc -------------- next part -------------- An HTML attachment was scrubbed... URL: From rafik.dammak at gmail.com Fri Apr 3 07:47:08 2020 From: rafik.dammak at gmail.com (Rafik Dammak) Date: Fri, 3 Apr 2020 13:47:08 +0900 Subject: [NCSG-PC] Proposed NCSG Policy calls until AGM 2020 In-Reply-To: <21F0DA40-DBEA-4BCF-A964-EB244FB43CB4@digitaldiscretion.ca> References: <21F0DA40-DBEA-4BCF-A964-EB244FB43CB4@digitaldiscretion.ca> Message-ID: hi all, thanks for the comments, I would like add a caveat here: - the idea of planning for several months is to give everyone heads-up to organize and plan for attending. Of course, there will be some emergencies or any unplanned things for some of us that cannot be avoided. We can always reschedule in extreme case like last time meeting but we still need some regularity. - rotation for day and time: for day, it will be complicated because the meeting usually happen prior to council meeting and after we get the agenda for council meeting in order to prepare for it, that limit the number of available days. We have also to avoid regular slots of PDP WGs and other ICANN related committees. For time, I will be candid here, rotation means everyone accepting to have calls at their 23:00 or 6:00 not just calls from 9:00 to 17:00, how many are ready for that? Personally, most of ICANN calls I attend are late in evening or early morning, not keen to add more. Council has 3 time slots in theory but the reality we are using only two and one is the same time we are already using for NCSG policy call. We can ask Maryam to make a spreadsheet to check which timezones are friendly to the member of PC and select from there but I want also to point our that the call is also for our NCSG members (satisfying a larger group will be more complicated). - Duration, we can reduce to 90min, 60min will be more challenging. We also talked about adding another call or regular webinars and a separate PC monthly call. Happy to hear from others. Best, Rafik Le ven. 3 avr. 2020 ? 12:14, Stephanie Perrin < stephanie at digitaldiscretion.ca> a ?crit : > I understand that james, what i am saying is vary the day. Set The whole > year if you like, but make it tuesday in april, wednesday in may, thursday > june etc. I would also toggle the time the odd time > > Sent from my iPhone > > On Apr 1, 2020, at 13:17, James Gannon wrote: > > ? > > If we can get these to 60mins calls then that?s great, longer than that > and I will be very tentative for all of them > > > > --- > > *James Gannon* > > > > *From: *NCSG-PC on behalf of Maryam > Bakoshi > *Date: *Wednesday, 1 April 2020 at 13:29 > *To: *NCSG PC > *Subject: *[NCSG-PC] Proposed NCSG Policy calls until AGM 2020 > > > > Dear all, > > > > As requested by Rafik, please find proposed NCSG Policy calls until AGM > 2020 > > *Proposed time: 12:00 UTC * > > Tuesday, 14 April > > Tuesday, 19 May > > Tuesday, 23 June (tentative as it?s ICANN68 week) > > Tuesday, 21 July > > Tuesday, 18 August > > Tuesday, 22 September > > Once you confirm, I will send a calendar invite for the agreed dates. > > > > Many thanks, > > -- > > > > *Maryam Bakoshi* | SO/AC Collaboration Services Sr. Coordinator > > *ICANN* | Internet Corporation for Assigned Names and Numbers > > *S*: Maryam.bakoshi.icann | *T*: +44 7846 471777 > > > _______________________________________________ > NCSG-PC mailing list > NCSG-PC at lists.ncsg.is > https://lists.ncsg.is/mailman/listinfo/ncsg-pc > > _______________________________________________ > NCSG-PC mailing list > NCSG-PC at lists.ncsg.is > https://lists.ncsg.is/mailman/listinfo/ncsg-pc > -------------- next part -------------- An HTML attachment was scrubbed... URL: From olga_kyryliuk at ukr.net Fri Apr 3 11:15:01 2020 From: olga_kyryliuk at ukr.net (Olga Kyryliuk) Date: Fri, 03 Apr 2020 11:15:01 +0300 Subject: [NCSG-PC] Proposed NCSG Policy calls until AGM 2020 In-Reply-To: References: <21F0DA40-DBEA-4BCF-A964-EB244FB43CB4@digitaldiscretion.ca> Message-ID: <1585901622.569433000.27jpa356@frv50.fwdcdn.com> I see, Rafik. Let?s go then with your initially proposed dates. Best, Olga 3 ?????? 2020, 07:47:27, ?? "Rafik Dammak" < rafik.dammak at gmail.com >: hi all, thanks for the comments, I would like add a caveat here: - the idea of planning for several months is to give everyone heads-up to organize and plan for attending. Of course, there will be some? emergencies or any unplanned things for some of us that cannot be avoided. We can always?reschedule in extreme case like last time meeting but we still need some regularity.? - rotation for day and time: for day, it will be complicated because the meeting usually happen prior to council meeting and after we get the agenda for council meeting in order to prepare for it, that limit the number of available days. We have also to avoid regular slots of PDP WGs and other ICANN related committees.? For time, I will be candid here, rotation means? everyone accepting to have calls at their 23:00 or 6:00 not just calls from 9:00 to 17:00, how many are ready for that? Personally, most?of ICANN calls I attend are late in evening or early morning, not keen to add more. Council has 3 time slots in theory but the reality we are using only two and one is the same time we are already using for NCSG policy call.? We can ask Maryam to make a spreadsheet to check which timezones are friendly to the member of PC and select from there but I want also to point our that the call is also for our NCSG members (satisfying a larger group will be more complicated).? - Duration, we can reduce to 90min, 60min will be more challenging. We also talked about adding another call? or regular webinars and a separate PC monthly call.? Happy to hear from others. Best, Rafik Le?ven. 3 avr. 2020 ??12:14, Stephanie Perrin a ?crit?: I understand that james, what i am saying is vary the day.? Set The whole year if you like, but make it tuesday in april, wednesday in may, thursday june etc.? I would also toggle the time the odd time Sent from my iPhone On Apr 1, 2020, at 13:17, James Gannon wrote: ? If we can get these to 60mins calls then that?s great, longer than that and I will be very tentative for all of them ? --- James?Gannon ? From: NCSG-PC on behalf of Maryam Bakoshi Date: Wednesday, 1 April 2020 at 13:29 To: NCSG PC Subject: [NCSG-PC] Proposed NCSG Policy calls until AGM 2020 ? Dear all, ? As requested by Rafik, please find proposed NCSG Policy calls until AGM 2020 Proposed time: 12:00 UTC? Tuesday, 14 April? Tuesday, 19 May? Tuesday, 23 June (tentative as it?s ICANN68 week) Tuesday, 21 July Tuesday, 18 August Tuesday, 22 September Once you confirm, I will send a calendar invite for the agreed dates. ? Many thanks, --? ? Maryam Bakoshi?| SO/AC Collaboration Services Sr. Coordinator? ICANN?| Internet Corporation for Assigned Names and Numbers? S: Maryam.bakoshi.icann |?T:?+44 7846 471777 ? _______________________________________________ NCSG-PC mailing list NCSG-PC at lists.ncsg.is https://lists.ncsg.is/mailman/listinfo/ncsg-pc _______________________________________________ NCSG-PC mailing list NCSG-PC at lists.ncsg.is https://lists.ncsg.is/mailman/listinfo/ncsg-pc _______________________________________________ NCSG-PC mailing list NCSG-PC at lists.ncsg.is https://lists.ncsg.is/mailman/listinfo/ncsg-pc -------------- next part -------------- An HTML attachment was scrubbed... URL: From rafik.dammak at gmail.com Tue Apr 7 02:19:48 2020 From: rafik.dammak at gmail.com (Rafik Dammak) Date: Tue, 7 Apr 2020 08:19:48 +0900 Subject: [NCSG-PC] Proposed NCSG Policy calls until AGM 2020 In-Reply-To: <1585901622.569433000.27jpa356@frv50.fwdcdn.com> References: <21F0DA40-DBEA-4BCF-A964-EB244FB43CB4@digitaldiscretion.ca> <1585901622.569433000.27jpa356@frv50.fwdcdn.com> Message-ID: thanks Olga. we have Council meeting next week Thursday, so I suggest to have the call next Tuesday at 12:00UTC . Best, Rafik Le ven. 3 avr. 2020 ? 17:15, Olga Kyryliuk a ?crit : > I see, Rafik. Let?s go then with your initially proposed dates. > > Best, > Olga > > > * 3 ?????? 2020, 07:47:27, ?? "Rafik Dammak" < rafik.dammak at gmail.com > >: * > > hi all, > > thanks for the comments, I would like add a caveat here: > > - the idea of planning for several months is to give everyone heads-up to > organize and plan for attending. Of course, there will be some emergencies > or any unplanned things for some of us that cannot be avoided. We can > always reschedule in extreme case like last time meeting but we still need > some regularity. > - rotation for day and time: for day, it will be complicated because the > meeting usually happen prior to council meeting and after we get the agenda > for council meeting in order to prepare for it, that limit the number of > available days. We have also to avoid regular slots of PDP WGs and other > ICANN related committees. > For time, I will be candid here, rotation means everyone accepting to > have calls at their 23:00 or 6:00 not just calls from 9:00 to 17:00, how > many are ready for that? Personally, most of ICANN calls I attend are late > in evening or early morning, not keen to add more. Council has 3 time slots > in theory but the reality we are using only two and one is the same time we > are already using for NCSG policy call. > We can ask Maryam to make a spreadsheet to check which timezones are > friendly to the member of PC and select from there but I want also to point > our that the call is also for our NCSG members (satisfying a larger group > will be more complicated). > - Duration, we can reduce to 90min, 60min will be more challenging. We > also talked about adding another call or regular webinars and a separate > PC monthly call. > Happy to hear from others. > > Best, > > Rafik > > Le ven. 3 avr. 2020 ? 12:14, Stephanie Perrin < > stephanie at digitaldiscretion.ca> a ?crit : > > I understand that james, what i am saying is vary the day. Set The whole > year if you like, but make it tuesday in april, wednesday in may, thursday > june etc. I would also toggle the time the odd time > > Sent from my iPhone > > On Apr 1, 2020, at 13:17, James Gannon wrote: > > ? > > If we can get these to 60mins calls then that?s great, longer than that > and I will be very tentative for all of them > > > > --- > > *James Gannon* > > > > *From: *NCSG-PC on behalf of Maryam > Bakoshi > *Date: *Wednesday, 1 April 2020 at 13:29 > *To: *NCSG PC > *Subject: *[NCSG-PC] Proposed NCSG Policy calls until AGM 2020 > > > > Dear all, > > > > As requested by Rafik, please find proposed NCSG Policy calls until AGM > 2020 > > *Proposed time: 12:00 UTC * > > Tuesday, 14 April > > Tuesday, 19 May > > Tuesday, 23 June (tentative as it?s ICANN68 week) > > Tuesday, 21 July > > Tuesday, 18 August > > Tuesday, 22 September > > Once you confirm, I will send a calendar invite for the agreed dates. > > > > Many thanks, > > -- > > > > *Maryam Bakoshi* | SO/AC Collaboration Services Sr. Coordinator > > *ICANN* | Internet Corporation for Assigned Names and Numbers > > *S*: Maryam.bakoshi.icann | *T*: +44 7846 471777 <+447846471777> > > > _______________________________________________ > NCSG-PC mailing list > NCSG-PC at lists.ncsg.is > https://lists.ncsg.is/mailman/listinfo/ncsg-pc > > _______________________________________________ > NCSG-PC mailing list > NCSG-PC at lists.ncsg.is > https://lists.ncsg.is/mailman/listinfo/ncsg-pc > > _______________________________________________ > NCSG-PC mailing listNCSG-PC at lists.ncsg.ishttps://lists.ncsg.is/mailman/listinfo/ncsg-pc > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From lizorembo at gmail.com Tue Apr 7 10:54:27 2020 From: lizorembo at gmail.com (Liz Orembo) Date: Tue, 7 Apr 2020 10:54:27 +0300 Subject: [NCSG-PC] Proposed NCSG Policy calls until AGM 2020 In-Reply-To: References: <21F0DA40-DBEA-4BCF-A964-EB244FB43CB4@digitaldiscretion.ca> <1585901622.569433000.27jpa356@frv50.fwdcdn.com> Message-ID: I look forward to the calendar invites. On Tue, Apr 7, 2020 at 2:20 AM Rafik Dammak wrote: > thanks Olga. > we have Council meeting next week Thursday, so I suggest to have the call > next Tuesday at 12:00UTC . > > Best, > > Rafik > > Le ven. 3 avr. 2020 ? 17:15, Olga Kyryliuk a > ?crit : > >> I see, Rafik. Let?s go then with your initially proposed dates. >> >> Best, >> Olga >> >> >> * 3 ?????? 2020, 07:47:27, ?? "Rafik Dammak" < rafik.dammak at gmail.com >> >: * >> >> hi all, >> >> thanks for the comments, I would like add a caveat here: >> >> - the idea of planning for several months is to give everyone heads-up to >> organize and plan for attending. Of course, there will be some emergencies >> or any unplanned things for some of us that cannot be avoided. We can >> always reschedule in extreme case like last time meeting but we still need >> some regularity. >> - rotation for day and time: for day, it will be complicated because the >> meeting usually happen prior to council meeting and after we get the agenda >> for council meeting in order to prepare for it, that limit the number of >> available days. We have also to avoid regular slots of PDP WGs and other >> ICANN related committees. >> For time, I will be candid here, rotation means everyone accepting to >> have calls at their 23:00 or 6:00 not just calls from 9:00 to 17:00, how >> many are ready for that? Personally, most of ICANN calls I attend are late >> in evening or early morning, not keen to add more. Council has 3 time slots >> in theory but the reality we are using only two and one is the same time we >> are already using for NCSG policy call. >> We can ask Maryam to make a spreadsheet to check which timezones are >> friendly to the member of PC and select from there but I want also to point >> our that the call is also for our NCSG members (satisfying a larger group >> will be more complicated). >> - Duration, we can reduce to 90min, 60min will be more challenging. We >> also talked about adding another call or regular webinars and a separate >> PC monthly call. >> Happy to hear from others. >> >> Best, >> >> Rafik >> >> Le ven. 3 avr. 2020 ? 12:14, Stephanie Perrin < >> stephanie at digitaldiscretion.ca> a ?crit : >> >> I understand that james, what i am saying is vary the day. Set The whole >> year if you like, but make it tuesday in april, wednesday in may, thursday >> june etc. I would also toggle the time the odd time >> >> Sent from my iPhone >> >> On Apr 1, 2020, at 13:17, James Gannon wrote: >> >> ? >> >> If we can get these to 60mins calls then that?s great, longer than that >> and I will be very tentative for all of them >> >> >> >> --- >> >> *James Gannon* >> >> >> >> *From: *NCSG-PC on behalf of Maryam >> Bakoshi >> *Date: *Wednesday, 1 April 2020 at 13:29 >> *To: *NCSG PC >> *Subject: *[NCSG-PC] Proposed NCSG Policy calls until AGM 2020 >> >> >> >> Dear all, >> >> >> >> As requested by Rafik, please find proposed NCSG Policy calls until AGM >> 2020 >> >> *Proposed time: 12:00 UTC * >> >> Tuesday, 14 April >> >> Tuesday, 19 May >> >> Tuesday, 23 June (tentative as it?s ICANN68 week) >> >> Tuesday, 21 July >> >> Tuesday, 18 August >> >> Tuesday, 22 September >> >> Once you confirm, I will send a calendar invite for the agreed dates. >> >> >> >> Many thanks, >> >> -- >> >> >> >> *Maryam Bakoshi* | SO/AC Collaboration Services Sr. Coordinator >> >> *ICANN* | Internet Corporation for Assigned Names and Numbers >> >> *S*: Maryam.bakoshi.icann | *T*: +44 7846 471777 <+447846471777> >> >> >> _______________________________________________ >> NCSG-PC mailing list >> NCSG-PC at lists.ncsg.is >> https://lists.ncsg.is/mailman/listinfo/ncsg-pc >> >> _______________________________________________ >> NCSG-PC mailing list >> NCSG-PC at lists.ncsg.is >> https://lists.ncsg.is/mailman/listinfo/ncsg-pc >> >> _______________________________________________ >> NCSG-PC mailing listNCSG-PC at lists.ncsg.ishttps://lists.ncsg.is/mailman/listinfo/ncsg-pc >> >> _______________________________________________ > NCSG-PC mailing list > NCSG-PC at lists.ncsg.is > https://lists.ncsg.is/mailman/listinfo/ncsg-pc > -- Best regards. Liz. PGP ID: 0x1F3488BF -------------- next part -------------- An HTML attachment was scrubbed... URL: From rafik.dammak at gmail.com Tue Apr 7 17:20:10 2020 From: rafik.dammak at gmail.com (Rafik Dammak) Date: Tue, 7 Apr 2020 23:20:10 +0900 Subject: [NCSG-PC] Proposed NCSG Policy calls until AGM 2020 In-Reply-To: References: <21F0DA40-DBEA-4BCF-A964-EB244FB43CB4@digitaldiscretion.ca> <1585901622.569433000.27jpa356@frv50.fwdcdn.com> Message-ID: thanks, I will ask to get at least the invitation for next week meeting sent. Best, Rafik Le mar. 7 avr. 2020 ? 16:54, Liz Orembo a ?crit : > > I look forward to the calendar invites. > > On Tue, Apr 7, 2020 at 2:20 AM Rafik Dammak > wrote: > >> thanks Olga. >> we have Council meeting next week Thursday, so I suggest to have the call >> next Tuesday at 12:00UTC . >> >> Best, >> >> Rafik >> >> Le ven. 3 avr. 2020 ? 17:15, Olga Kyryliuk a >> ?crit : >> >>> I see, Rafik. Let?s go then with your initially proposed dates. >>> >>> Best, >>> Olga >>> >>> >>> * 3 ?????? 2020, 07:47:27, ?? "Rafik Dammak" < rafik.dammak at gmail.com >>> >: * >>> >>> hi all, >>> >>> thanks for the comments, I would like add a caveat here: >>> >>> - the idea of planning for several months is to give everyone heads-up >>> to organize and plan for attending. Of course, there will be some >>> emergencies or any unplanned things for some of us that cannot be avoided. >>> We can always reschedule in extreme case like last time meeting but we >>> still need some regularity. >>> - rotation for day and time: for day, it will be complicated because the >>> meeting usually happen prior to council meeting and after we get the agenda >>> for council meeting in order to prepare for it, that limit the number of >>> available days. We have also to avoid regular slots of PDP WGs and other >>> ICANN related committees. >>> For time, I will be candid here, rotation means everyone accepting to >>> have calls at their 23:00 or 6:00 not just calls from 9:00 to 17:00, how >>> many are ready for that? Personally, most of ICANN calls I attend are late >>> in evening or early morning, not keen to add more. Council has 3 time slots >>> in theory but the reality we are using only two and one is the same time we >>> are already using for NCSG policy call. >>> We can ask Maryam to make a spreadsheet to check which timezones are >>> friendly to the member of PC and select from there but I want also to point >>> our that the call is also for our NCSG members (satisfying a larger group >>> will be more complicated). >>> - Duration, we can reduce to 90min, 60min will be more challenging. We >>> also talked about adding another call or regular webinars and a separate >>> PC monthly call. >>> Happy to hear from others. >>> >>> Best, >>> >>> Rafik >>> >>> Le ven. 3 avr. 2020 ? 12:14, Stephanie Perrin < >>> stephanie at digitaldiscretion.ca> a ?crit : >>> >>> I understand that james, what i am saying is vary the day. Set The >>> whole year if you like, but make it tuesday in april, wednesday in may, >>> thursday june etc. I would also toggle the time the odd time >>> >>> Sent from my iPhone >>> >>> On Apr 1, 2020, at 13:17, James Gannon wrote: >>> >>> ? >>> >>> If we can get these to 60mins calls then that?s great, longer than that >>> and I will be very tentative for all of them >>> >>> >>> >>> --- >>> >>> *James Gannon* >>> >>> >>> >>> *From: *NCSG-PC on behalf of Maryam >>> Bakoshi >>> *Date: *Wednesday, 1 April 2020 at 13:29 >>> *To: *NCSG PC >>> *Subject: *[NCSG-PC] Proposed NCSG Policy calls until AGM 2020 >>> >>> >>> >>> Dear all, >>> >>> >>> >>> As requested by Rafik, please find proposed NCSG Policy calls until AGM >>> 2020 >>> >>> *Proposed time: 12:00 UTC * >>> >>> Tuesday, 14 April >>> >>> Tuesday, 19 May >>> >>> Tuesday, 23 June (tentative as it?s ICANN68 week) >>> >>> Tuesday, 21 July >>> >>> Tuesday, 18 August >>> >>> Tuesday, 22 September >>> >>> Once you confirm, I will send a calendar invite for the agreed dates. >>> >>> >>> >>> Many thanks, >>> >>> -- >>> >>> >>> >>> *Maryam Bakoshi* | SO/AC Collaboration Services Sr. Coordinator >>> >>> *ICANN* | Internet Corporation for Assigned Names and Numbers >>> >>> *S*: Maryam.bakoshi.icann | *T*: +44 7846 471777 <+447846471777> >>> >>> >>> _______________________________________________ >>> NCSG-PC mailing list >>> NCSG-PC at lists.ncsg.is >>> https://lists.ncsg.is/mailman/listinfo/ncsg-pc >>> >>> _______________________________________________ >>> NCSG-PC mailing list >>> NCSG-PC at lists.ncsg.is >>> https://lists.ncsg.is/mailman/listinfo/ncsg-pc >>> >>> _______________________________________________ >>> NCSG-PC mailing listNCSG-PC at lists.ncsg.ishttps://lists.ncsg.is/mailman/listinfo/ncsg-pc >>> >>> _______________________________________________ >> NCSG-PC mailing list >> NCSG-PC at lists.ncsg.is >> https://lists.ncsg.is/mailman/listinfo/ncsg-pc >> > > > -- > > Best regards. > Liz. > > PGP ID: 0x1F3488BF > -------------- next part -------------- An HTML attachment was scrubbed... URL: From PolicyCalendar at icann.org Tue Apr 7 18:12:20 2020 From: PolicyCalendar at icann.org (ICANN Policy Calendar) Date: Tue, 7 Apr 2020 15:12:20 +0000 Subject: [NCSG-PC] NCSG Policy Committee call on Tuesday, 14 April 2020 at 1200 UTC Message-ID: Topic: NCSG POLICY CALL Time: Apr 14, 2020 12:00 Universal Time UTC; other times: https://tinyurl.com/rkphtua. Join Zoom Meeting https://icann.zoom.us/j/5524218263?pwd=WHVjUUQ1a2Y4MHRGdC94RlkrNS8zUT09 Meeting ID: 552 421 8263 Password: 54321 One tap mobile +442034815237,,5524218263# United Kingdom +442034815240,,5524218263# United Kingdom Dial by your location +44 203 481 5237 United Kingdom +44 203 481 5240 United Kingdom +44 208 080 6591 United Kingdom +44 208 080 6592 United Kingdom +44 330 088 5830 United Kingdom +44 131 460 1196 United Kingdom 0 800 260 5801 United Kingdom Toll-free 0 800 358 2817 United Kingdom Toll-free 0 800 031 5717 United Kingdom Toll-free +1 669 900 6833 US (San Jose) +1 346 248 7799 US (Houston) +1 301 715 8592 US +1 312 626 6799 US (Chicago) +1 929 436 2866 US (New York) +1 253 215 8782 US 888 788 0099 US Toll-free 877 853 5247 US Toll-free +213 98 24 02 675 Algeria +54 341 512 2188 Argentina +54 343 414 5986 Argentina +54 112 040 0447 Argentina 822 345 9889 Argentina Toll-free +61 731 853 730 Australia +61 861 193 900 Australia +61 8 7150 1149 Australia +61 2 8015 6011 Australia +61 3 7018 2005 Australia 1800 893 423 Australia Toll-free 1800 945 157 Australia Toll-free 1800 317 562 Australia Toll-free +43 12 535 502 Austria +43 670 309 0165 Austria +43 72 011 5988 Austria +43 12 535 501 Austria 800 104 430 Austria Toll-free 0 800 102 309 Austria Toll-free 1800 389 0808 Bahamas Toll-free +973 1619 8488 Bahrain +973 1619 7601 Bahrain 800 197 96 Bahrain Toll-free 0004 054 189 Uruguay Toll-free 800 120 1235 Uzbekistan Toll-free 0 800 100 5564 Venezuela (Bolivarian Republic of) Toll-free +263 864 404 1086 Zimbabwe +84 28 4458 2373 Viet Nam 0 800 800 138 Ukraine Toll-free 0 800 501 567 Ukraine Toll-free 800 035 704 555 United Arab Emirates Toll-free 800 0491 0899 United Arab Emirates Toll-free 800 035 704 239 United Arab Emirates Toll-free +256 206 300 097 Uganda +90 216 900 2606 Turkey +90 216 900 1866 Turkey 811 213 0011 Turkey Toll-free +216 31 397 748 Tunisia +1 868 224 5838 Trinidad and Tobago +66 60 003 5790 Thailand +66 2018 2486 Thailand 1 800 013 864 Thailand Toll-free 1 800 012 275 Thailand Toll-free +886 (2) 7741 7473 Taiwan 08 0909 9864 Taiwan Toll-free +41 31 528 09 88 Switzerland +41 43 210 70 42 Switzerland +41 43 210 71 08 Switzerland +41 22 591 00 05 Switzerland +41 22 591 01 56 Switzerland 0 800 561 252 Switzerland Toll-free 0 800 002 622 Switzerland Toll-free +46 8 5050 0829 Sweden +46 8 5052 0017 Sweden +46 850 539 728 Sweden +46 8 4468 2488 Sweden +46 8 5050 0828 Sweden 0 200 123 720 Sweden Toll-free 0 200 123 514 Sweden Toll-free +94 7 2091 0374 Sri Lanka +34 91 787 0058 Spain +34 917 873 431 Spain +34 84 368 5025 Spain 800 906 063 Spain Toll-free 900 053 647 Spain Toll-free 800 654 404 Spain Toll-free +82 2 6105 4111 Korea, Republic of +82 2 6022 2322 Korea, Republic of 0 808 220 250 Korea, Republic of Toll-free +27 87 551 7702 South Africa +27 87 550 3946 South Africa 0 800 064 584 South Africa Toll-free 0 800 008 728 South Africa Toll-free +386 1888 8788 Slovenia +386 1600 3102 Slovenia 0 80 488 840 Slovenia Toll-free +421 233 418 515 Slovakia +421 233 056 888 Slovakia 0 800 049 025 Slovakia Toll-free 0 800 005 424 Slovakia Toll-free 0 800 500 702 Serbia Toll-free +65 3165 1065 Singapore +65 3158 7288 Singapore 800 852 6054 Singapore Toll-free 800 101 3814 Singapore Toll-free 800 814 3820 Saudi Arabia Toll-free 800 850 0304 Saudi Arabia Toll-free 800 811 0528 Saudi Arabia Toll-free +7 812 426 8988 Russian Federation +7 495 283 9788 Russian Federation 8800 301 7427 Russian Federation Toll-free (Landline) 8800 100 6938 Russian Federation Toll-free 00 800 100363 Qatar Toll-free 00 800 100 059 Qatar Toll-free +40 37 170 0418 Romania +40 31 630 1088 Romania 0 800 890 203 Romania Toll-free 0 800 672 631 Romania Toll-free +1 787 966 7727 Puerto Rico +1 787 945 1488 Puerto Rico 800 239 1922 Puerto Rico Toll-free +351 265 120 012 Portugal +351 308 804 188 Portugal +351 308 810 988 Portugal +351 211 202 618 Portugal 800 780 072 Portugal Toll-free 800 780 052 Portugal Toll-free +48 22 398 7356 Poland +48 22 307 3488 Poland 00 800 321 1464 Poland Toll-free 00 800 112 5171 Poland Toll-free +63 92 3099 0478 Philippines 1800 1110 2219 Philippines Toll-free +51 1 730 6777 Peru +51 1 707 5788 Peru 0 800 78743 Peru Toll-free 0 800 76930 Peru Toll-free 0098 0011 0288 Paraguay Toll-free +507 833 9588 Panama 800 0558 Panama Toll-free +92 21 3879 9843 Pakistan 800 74201 Oman Toll-free +47 7349 4877 Norway +47 2396 0588 Norway 800 248 88 Norway Toll-free +234 1227 8806 Nigeria 0 708 060 1822 Nigeria Toll-free 1800 220 2436 Nicaragua Toll-free (Mobile) 1800 220 2039 Nicaragua Toll-free (Landline) +64 9 884 6780 New Zealand +64 4 886 0026 New Zealand 0 800 527 544 New Zealand Toll-free 0 800 307 929 New Zealand Toll-free +31 20 794 6519 Netherlands +31 20 794 6520 Netherlands +31 20 794 7345 Netherlands +31 20 241 0288 Netherlands +31 20 794 0854 Netherlands 0 800 220 0040 Netherlands Toll-free 0 800 022 1954 Netherlands Toll-free +52 554 161 4288 Mexico +52 229 910 0061 Mexico 800 733 4118 Mexico Toll-free 800 062 7287 Mexico Toll-free +356 2778 1288 Malta +356 2776 1777 Malta 800 62987 Malta Toll-free 800 62714 Malta Toll-free +60 3 9212 1727 Malaysia +60 3 3099 2229 Malaysia 1 800 818 425 Malaysia Toll-free 0 800 904 59 North Macedonia Toll-free +853 6262 1604 Macau, China 0 800 910 Macau, China Toll-free 0 800 191 Macau, China Toll-free +352 2786 4277 Luxembourg +352 2786 1188 Luxembourg 800 810 88 Luxembourg Toll-free +370 5214 1488 Lithuania +370 3799 9260 Lithuania 8 800 303 19 Lithuania Toll-free +371 6303 1888 Latvia +371 6303 1808 Latvia 8000 0281 Latvia Toll-free +965 2206 9157 Kuwait 0 800 733 310 Kenya Toll-free 800 720 248 Kenya Toll-free +7 727 312 2408 Kazakhstan 800 222 03 Jordan Toll-free +81 524 564 439 Japan +81 3 4578 1488 Japan 0 800 100 5040 Japan Toll-free 00 663 381 4092 Japan Toll-free +1 876 633 1687 Jamaica 800 491 6523 Jamaica Toll-free +39 021 241 28 823 Italy +39 069 480 6488 Italy +39 020 066 7245 Italy 800 125 671 Italy Toll-free 800 790 654 Italy Toll-free 800 088 202 Italy Toll-free +972 55 330 1762 Israel +972 3 978 6688 Israel 1801 227 228 Israel Toll-free +353 1 653 3897 Ireland +353 1 653 3898 Ireland +353 6 163 9031 Ireland +353 1 536 9320 Ireland +353 1 653 3895 Ireland 1800 943 965 Ireland Toll-free 1800 949 238 Ireland Toll-free 1800 901 561 Ireland Toll-free +62 21 3950 1721 Indonesia +62 215 086 1500 Indonesia +62 21 2789 9657 Indonesia +91 806 480 2722 India +91 80 71 279 440 India +91 116 480 2722 India +91 22 48 798 004 India +91 224 879 8012 India +91 226 480 2722 India +91 22 71 279 525 India +91 406 480 2722 India +91 446 480 2722 India 000 800 050 5050 India Toll-free 000 800 040 1530 India Toll-free 0080 07 473 Iceland Toll-free +36 1 701 0488 Hungary +36 1 408 8456 Hungary 800 881 88 Hungary Toll-free +852 5803 3731 Hong Kong, China +852 5808 6088 Hong Kong, China +852 5803 3730 Hong Kong, China 800 931 189 Hong Kong, China Toll-free 800 931 645 Hong Kong, China Toll-free 800 906 780 Hong Kong, China Toll-free 800 2791 9494 Honduras Toll-free 1800 3000 161 Guatemala Toll-free +30 231 118 0599 Greece +30 211 198 4488 Greece 800 848 1188 Greece Toll-free 30 708 4860 Ghana Toll-free 30 708 4676 Ghana Toll-free +49 695 050 2596 Germany +49 69 7104 9922 Germany +49 30 5679 5800 Germany 0 800 000 6954 Germany Toll-free 0 800 1800 150 Germany Toll-free 0 800 000 1590 Germany Toll-free +995 7067 77954 Georgia +995 3224 73988 Georgia +33 1 7095 0103 France +33 1 7095 0350 France +33 7 5678 4048 France +33 1 7037 2246 France +33 1 7037 9729 France 0 800 944 049 France Toll-free 0 800 940 415 France Toll-free +358 9 4245 1488 Finland +358 3 4109 2129 Finland 0 800 102 188 Finland Toll-free 0080 02 592 Fiji Toll-free +372 880 1188 Estonia +372 660 1699 Estonia +503 2136 6444 El Salvador +503 2113 9088 El Salvador 0800 000 9608 Egypt Toll-free 1800 000 785 Ecuador Toll-free +1 829 956 2188 Dominican Republic +1 829 947 9220 Dominican Republic 800 751 9718 Dominican Republic Toll-free +45 32 72 80 10 Denmark +45 32 72 80 11 Denmark +45 89 88 37 88 Denmark +45 32 70 12 06 Denmark +45 32 71 31 57 Denmark 80 71 12 56 Denmark Toll-free 80 71 12 51 Denmark Toll-free +420 5 3889 0161 Czechia +420 2 2888 2388 Czechia 828 848 888 Czechia Toll-free +357 2 505 4777 Cyprus +357 2 200 0888 Cyprus 800 773 38 Cyprus Toll-free +385 1777 6333 Croatia +385 1300 0988 Croatia 0 800 200 588 Croatia Toll-free +506 4000 3843 Costa Rica +57 2 620 7388 Colombia +57 1 508 7702 Colombia 1 800 518 4301 Colombia Toll-free +86 10 8783 3177 China +86 10 5387 6330 China 400 616 8835 China Toll-free 400 669 9381 China Toll-free 400 182 3168 China Toll-free +56 41 256 0288 Chile +56 23 210 9066 Chile 800 914 125 Chile Toll-free 123 002 00163 Chile Toll-free +1 345 769 1930 Cayman Islands +1 647 374 4685 Canada +1 647 558 0588 Canada +1 778 907 2071 Canada +1 438 809 7799 Canada +1 587 328 1099 Canada 855 703 8985 Canada Toll-free 1800 201 503 Cambodia Toll-free +359 3 257 1633 Bulgaria +359 2 492 5688 Bulgaria 00 800 111 3251 Bulgaria Toll-free +55 21 3958 7888 Brazil +55 11 4680 6788 Brazil 0 800 878 3108 Brazil Toll-free 0 800 282 5751 Brazil Toll-free 0 800 828 50 Bosnia and Herzegovina Toll-free 800 100 560 Bolivia (Plurinational State of) Toll-free 866 237 6875 Bermuda Toll-free +32 2 588 4188 Belgium +32 2 788 0172 Belgium +32 2 788 0173 Belgium +32 1579 5132 Belgium +32 2 290 9360 Belgium 0 800 294 51 Belgium Toll-free 0 800 293 46 Belgium Toll-free Meeting ID: 552 421 8263 Password: 54321 Find your local number: https://icann.zoom.us/u/adUojhAPmk -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: text/calendar Size: 12726 bytes Desc: not available URL: From jumaropi at yahoo.com Tue Apr 7 23:41:53 2020 From: jumaropi at yahoo.com (Juan Manuel Rojas) Date: Tue, 7 Apr 2020 20:41:53 +0000 (UTC) Subject: [NCSG-PC] Proposed NCSG Policy calls until AGM 2020 In-Reply-To: References: <21F0DA40-DBEA-4BCF-A964-EB244FB43CB4@digitaldiscretion.ca> <1585901622.569433000.27jpa356@frv50.fwdcdn.com> Message-ID: <1644168491.2094067.1586292113681@mail.yahoo.com> Dear all,?I'd agree on this tentative schedule with posibility to re-schedule if necesary.?? Best regards, JUAN MANUEL ROJAS P. Presidente?-?AGEIA DENSI?ColombiaGNSO Councilor - ICANNCluster Orinoco TIC memberMaster IT candidate, Universidad de los Andes Cel. +57 3017435600 Twitter:?@JmanuRojas ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? El martes, 7 de abril de 2020 09:20:31 a.?m. GMT-5, Rafik Dammak escribi?: thanks, I will ask to get at least the invitation for next week meeting sent. Best, Rafik Le?mar. 7 avr. 2020 ??16:54, Liz Orembo a ?crit?: I look forward to the calendar invites. On Tue, Apr 7, 2020 at 2:20 AM Rafik Dammak wrote: thanks Olga.we have Council meeting next week Thursday, so I suggest to have the call next Tuesday at 12:00UTC . Best, Rafik Le?ven. 3 avr. 2020 ??17:15, Olga Kyryliuk a ?crit?: I see, Rafik. Let?s go then with your initially proposed dates. Best,Olga 3 ?????? 2020, 07:47:27, ?? "Rafik Dammak" < rafik.dammak at gmail.com >: hi all, thanks for the comments, I would like add a caveat here: - the idea of planning for several months is to give everyone heads-up to organize and plan for attending. Of course, there will be some? emergencies or any unplanned things for some of us that cannot be avoided. We can always?reschedule in extreme case like last time meeting but we still need some regularity.?- rotation for day and time: for day, it will be complicated because the meeting usually happen prior to council meeting and after we get the agenda for council meeting in order to prepare for it, that limit the number of available days. We have also to avoid regular slots of PDP WGs and other ICANN related committees.?For time, I will be candid here, rotation means? everyone accepting to have calls at their 23:00 or 6:00 not just calls from 9:00 to 17:00, how many are ready for that? Personally, most?of ICANN calls I attend are late in evening or early morning, not keen to add more. Council has 3 time slots in theory but the reality we are using only two and one is the same time we are already using for NCSG policy call.?We can ask Maryam to make a spreadsheet to check which timezones are friendly to the member of PC and select from there but I want also to point our that the call is also for our NCSG members (satisfying a larger group will be more complicated).?- Duration, we can reduce to 90min, 60min will be more challenging. We also talked about adding another call? or regular webinars and a separate PC monthly call.?Happy to hear from others. Best, Rafik Le?ven. 3 avr. 2020 ??12:14, Stephanie Perrin a ?crit?: I understand that james, what i am saying is vary the day.? Set The whole year if you like, but make it tuesday in april, wednesday in may, thursday june etc.? I would also toggle the time the odd time Sent from my iPhone On Apr 1, 2020, at 13:17, James Gannon wrote: ? If we can get these to 60mins calls then that?s great, longer than that and I will be very tentative for all of them ? --- James?Gannon ? From: NCSG-PC on behalf of Maryam Bakoshi Date: Wednesday, 1 April 2020 at 13:29 To: NCSG PC Subject: [NCSG-PC] Proposed NCSG Policy calls until AGM 2020 ? Dear all, ? As requested by Rafik, please find proposed NCSG Policy calls until AGM 2020 Proposed time: 12:00 UTC? Tuesday, 14 April? Tuesday, 19 May? Tuesday, 23 June (tentative as it?s ICANN68 week) Tuesday, 21 July Tuesday, 18 August Tuesday, 22 September Once you confirm, I will send a calendar invite for the agreed dates. ? Many thanks, --? ? Maryam Bakoshi?| SO/AC Collaboration Services Sr. Coordinator? ICANN?| Internet Corporation for Assigned Names and Numbers? S: Maryam.bakoshi.icann |?T:?+44 7846 471777 ? _______________________________________________ NCSG-PC mailing list NCSG-PC at lists.ncsg.is https://lists.ncsg.is/mailman/listinfo/ncsg-pc _______________________________________________ NCSG-PC mailing list NCSG-PC at lists.ncsg.is https://lists.ncsg.is/mailman/listinfo/ncsg-pc _______________________________________________ NCSG-PC mailing list NCSG-PC at lists.ncsg.is https://lists.ncsg.is/mailman/listinfo/ncsg-pc _______________________________________________ NCSG-PC mailing list NCSG-PC at lists.ncsg.is https://lists.ncsg.is/mailman/listinfo/ncsg-pc -- Best regards. Liz. PGP ID: 0x1F3488BF _______________________________________________ NCSG-PC mailing list NCSG-PC at lists.ncsg.is https://lists.ncsg.is/mailman/listinfo/ncsg-pc -------------- next part -------------- An HTML attachment was scrubbed... URL: From rafik.dammak at gmail.com Wed Apr 8 14:54:59 2020 From: rafik.dammak at gmail.com (Rafik Dammak) Date: Wed, 8 Apr 2020 20:54:59 +0900 Subject: [NCSG-PC] Fwd: [NCSG-Discuss] Public Comment: Revised Community Travel Support Guidelines In-Reply-To: <196c3ee1-49f6-df88-e2d7-403edb64365b@wtec.org.ng> References: <196c3ee1-49f6-df88-e2d7-403edb64365b@wtec.org.ng> Message-ID: hi all, we have a draft comment for review. the deadline for submission is the 13 thApril. Best, Rafik ---------- Forwarded message --------- De : Oreoluwa Somolu Lesi Date: mer. 8 avr. 2020 ? 05:38 Subject: [NCSG-Discuss] Public Comment: Revised Community Travel Support Guidelines To: Hello everyone, Muriel Alapini, Pascal Bekono and I drafted a comment on behalf of NCSG for the call for public comments for the *Revised Community Travel Support Guidelines*. https://docs.google.com/document/d/18QoHr3Un3HFvLy6jClpl_ESWkXqZLdvrspQLjudP75k/edit We invite the community to review. The deadline for submission for comments is next Monday, April 13, which is Easter Monday for those who celebrate this. Therefore we would like to get all comments in by *Wednesday, April 8* so that the PC can review and the final version submitted by Thursday, April 9. Apologies for this tight deadline. Thank you all for your input. Kind regards, Ore -- Oreoluwa Lesi Executive Director, Women's Technology Empowerment Centre (W.TEC) +234.803.621.1307, +234.813.339.9999 | www.wtec.org.ng | @wteconline -------------- next part -------------- An HTML attachment was scrubbed... URL: From lists at icann.guru Wed Apr 8 15:08:58 2020 From: lists at icann.guru (lists at icann.guru) Date: Wed, 08 Apr 2020 13:08:58 +0100 Subject: [NCSG-PC] Fwd: [NCSG-Discuss] Public Comment: Revised Community Travel Support Guidelines In-Reply-To: References: <196c3ee1-49f6-df88-e2d7-403edb64365b@wtec.org.ng> Message-ID: lgtm --- James Gannon On 08/04/2020 12:56:05, Rafik Dammak wrote: hi all, we have a draft comment for review. the deadline for submission is the 13 thApril. Best, Rafik ---------- Forwarded message --------- De?: Oreoluwa Somolu Lesi Date: mer. 8 avr. 2020 ??05:38 Subject: [NCSG-Discuss] Public Comment: Revised Community Travel Support Guidelines To: Hello everyone, Muriel Alapini, Pascal Bekono and I drafted a comment on behalf of NCSG for the call for public comments for the Revised Community Travel Support Guidelines. https://docs.google.com/document/d/18QoHr3Un3HFvLy6jClpl_ESWkXqZLdvrspQLjudP75k/edit [https://docs.google.com/document/d/18QoHr3Un3HFvLy6jClpl_ESWkXqZLdvrspQLjudP75k/edit] We invite the community to review. The deadline for submission for comments is next Monday, April 13, which is Easter Monday for those who celebrate this. Therefore we would like to get all comments in by Wednesday, April 8 so that the PC can review and the final version submitted by Thursday, April 9. Apologies for this tight deadline. Thank you all for your input. Kind regards, Ore -- Oreoluwa Lesi Executive Director, Women's Technology Empowerment Centre (W.TEC) +234.803.621.1307, +234.813.339.9999 | www.wtec.org.ng [https://wtec.org.ng/] | @wteconline [https://www.instagram.com/wteconline/] _______________________________________________ NCSG-PC mailing list NCSG-PC at lists.ncsg.is https://lists.ncsg.is/mailman/listinfo/ncsg-pc -------------- next part -------------- An HTML attachment was scrubbed... URL: From lists at icann.guru Wed Apr 8 17:44:02 2020 From: lists at icann.guru (lists at icann.guru) Date: Wed, 08 Apr 2020 15:44:02 +0100 Subject: [NCSG-PC] Fw: [council] FW: Final Proposed Agenda GNSO Council Meeting - 16 April 2020 at 12:00 UTC In-Reply-To: References: Message-ID: Happy to hear any input from folks here. --- James Gannon ------ Forwarded Message -------- From: Drazek, Keith via council Date: 08/04/2020 15:42:33 Subject: [council] FW: Final Proposed Agenda GNSO Council Meeting - 16 April 2020 at 12:00 UTC To: council at gnso.icann.org , haforrestesq at gmail.com , Donna.Austin at team.neustar , claudia.selli at intl.att.com , wolf-ulrich.knoben at t-online.de , joankerr at fbsc.org , bruna.mrtns at gmail.com , stephanie.perrin at mail.utoronto.ca , Graeme Bunton Cc: gnso-secs at icann.org Hi all, ? During the 16 April GNSO Council meeting, we will discuss the impact of COVID-19 on ICANN, the ICANN Community, and around our ability to conduct Council work. This will include an evolving discussion on planning and prioritization, as our prior discussions in January have been overtaken by events. Please work with your respective SGs and Cs to develop any input to this important conversation. I have included the Chairs of our GNSO SGs and Cs so we are all on the same page in these unprecedented circumstances. ? Thanks in advance, and I hope everyone is keeping healthy and safe. ? Best regards, Keith ? ? ? From: council On Behalf Of Terri Agnew Sent: Wednesday, April 8, 2020 10:29 AM To: council at gnso.icann.org Cc: gnso-secs at icann.org Subject: [EXTERNAL] [council] Final Proposed Agenda GNSO Council Meeting - 16 April 2020 at 12:00 UTC ? Dear all, ? Please find below the final proposed agenda for the GNSO Council Meeting on 16 April 2020 at 12:00 UTC. Draft GNSO Council Agenda 16 April 2020 Please note that all documents referenced in the agenda have been gathered on a Wiki page for convenience and easier access: https://community.icann.org/x/myWJBw [https://community.icann.org/x/myWJBw] ? This agenda was established according to the GNSO Operating Procedures [https://gnso.icann.org/en/council/op-procedures-30jan18-en.pdf] v3.3, updated on 30 January 2018 For convenience: * An excerpt of the ICANN Bylaws defining the voting thresholds is provided in Appendix 1 at the end of this agenda. * An excerpt from the Council Operating Procedures defining the absentee voting procedures is provided in Appendix 2 at the end of this agenda. ? GNSO Council meeting held at 12:00 UTC ? Coordinated Universal Time: 12:00 UTC: https://tinyurl.com/vau3jkd [https://tinyurl.com/vau3jkd] ? 05:00 Los Angeles; 08:00 Washington DC; 13:00 London; 17:00 Islamabad; 21:00 Tokyo; 22:00 Melbourne? GNSO Council Meeting Webinar Room https://icann.zoom.us/j/895774606 [https://icann.zoom.us/j/895774606] ? Councilors should notify the GNSO Secretariat in advance if they will not be able to attend and/or need a dial out call. ___________________________________ Item 1: Administrative Matters (10 mins) 1.1 - Roll Call 1.2 - Updates to Statements of Interest 1.3 - Review / Amend Agenda 1.4 - Note the status of minutes for the previous Council meetings per the GNSO Operating Procedures:? Minutes [https://gnso.icann.org/sites/default/files/policy/2019/minutes/minutes-gnso-council-20feb20-en.pdf] of the GNSO Council meeting on the 20 February 2020 will be posted on 6 March 2020 Minutes [https://gnso.icann.org/sites/default/files/policy/2019/minutes/minutes-council-11mar20-en.pdf] of the GNSO Council meeting on the 11 March 2020 were posted on 27 March 2020. ? Item 2: Opening Remarks / Review of Projects & Action List (10 minutes) 2.1 - Review focus areas and provide updates on specific key themes / topics, to include review of Projects List [https://gnso.icann.org/en/council/project]and Action Item List.? [https://community.icann.org/x/RgZlAg] ? Item 3: Consent Agenda (0 minutes)? * None ? ? Item 4: COUNCIL DISCUSSION - Impact of Coronavirus (COVID-19) (10 minutes) Everyone is affected by the coronavirus pandemic, including members of the Council, members of the Stakeholder Groups and Constituencies, and staff. The impact is substantial for some, who in addition to their regular job are now also playing additional roles as day care provider and educator. For some, their work may be directly related to the effort to combat coronavirus.? Here, the Council will have a brief discussion about how the coronavirus pandemic may impact the capacity of the GNSO Council and the SG/Cs as well as ICANN Org?s operations and staff, and that it should be accounted for in discussing all of the subsequent agenda items during this meeting. 4.1 ? Introduction of topic (Council leadership) 4.2 ? Council discussion 4.3 ? Next steps ? ? ? ? Item 5: COUNCIL DISCUSSION ? GNSO Work Prioritization - 2020 Work Plan / Impact From Coronavirus (25 minutes) After the GNSO Council?s Strategic Planning Session in January 2020, the Council acknowledged that there are limited resources available for policy development activities and related work. This resource limitation means that the GNSO Council must efficiently complete its current work, but also prioritize the new work waiting in its pipeline. At the Strategic Planning Session, Councilors participated in an informal and non-binding ranking survey, which was used as a ?sense of the room.? This informational survey result was shared with Councilors to then share with their respective Stakeholder Groups and Constituencies, to gain a better sense of the various groups? top priorities. The Council touched on this topic briefly during the February Council meeting and again during its March meeting. Council leadership and staff developed a draft work plan for the Council?s consideration. Previously, the focus was on prioritization of the GNSO?s work, which implies that the work should be ranked in order of priority. However, Council leadership determined that it might be more practical to think of this exercise more simply as establishing a work plan, which does still consider the urgency of the work, but also looks at each element of work in a more granular fashion and identifies potential dependencies. What this allows the Council to do is to potentially carve out pieces of work from a project that might be initiated in the near-term, some of which may then serve as the preparatory/informational basis for Council next steps. While this topic is focused on a relatively long-term work plan for the GNSO, the landscape has changed significantly since the Strategic Planning Session in late January of 2020. It is possible that capacity within the community, as well as Policy staff, is or may be diminished by the impact from the coronavirus pandemic. For instance, the Council had anticipated initiating the IGO Work Track just after ICANN68, but Council leadership believes discussion is warranted on whether the timing still remains appropriate. Here, the Council will discuss this change in approach (and draft document) to establishing the Council?s draft work plan for 2020, and potentially beyond, but will also consider whether the coronavirus pandemic might impact that plan. 5.1 ? Introduction of topic (Council leadership) 5.2 ? Council discussion 5.3 ? Next steps ? Item 6: COUNCIL DISCUSSION - Report from the Transfer Policy Scoping Team (15 minutes) On April 22, 2019, ICANN Org delivered the most recent version of the Transfer Policy Status Report (TPSR) [https://gnso.icann.org/sites/default/files/file/field-file-attach/irtp-status-30nov18-en.pdf] to the GNSO Council. ICANN Org delivered the TPSR pursuant to Recommendation 17 of the Inter-Registrar Transfer Policy (IRTP) Part D PDP Working Group?s Final Report [https://gnso.icann.org/sites/default/files/filefield_46639/irtp-d-final-25sep14-en.pdf], which provides, ?[t]he Working Group recommends that contracted parties and ICANN should start to gather data and other relevant information that will help inform a future IRTP review team in its efforts.?? The GNSO Council established the Transfer Policy Review Scoping Team to review the TPSR and consider the best approach/mechanism to conduct the review, composition of the potential review team, and the scope of the review and future policy work related to the Transfer Policy. The team believes that the GDPR and similar national privacy legislations have rendered the Transfer Policy ineffective and unworkable as written and recommends that a PDP, or series of PDPs, be established to conduct policy work on the Transfer Policy. Further, as a first step, the team recommends that the GNSO Council instruct ICANN Policy staff to draft an Issues Report in line with the Scoping Document [https://gnso.icann.org/sites/default/files/file/field-file-attach/transfer-policy-review-scoping-team-06apr20-en.pdf] delivered to the GNSO Council on 7 April 2020.. Here, the Council will discuss the report from the Transfer Policy Scoping Team and consider possible next steps, including the request of an Issue Report on the Transfer Policy. 6.1 - Introduction of topic (Council leadership) 6.2 ? Council discussion 6.3 ? Next steps ? Item 7: Registration Directory Service (RDS) - Program Management (35 minutes) The GNSO Council has a number of Registration Directory Service (RDS) related topics to consider. * EPDP Phase 1, Recommendation 27 Wave 1 report - The Council was provided with the updated version of the Wave 1 report [https://mm.icann.org/pipermail/council/2020-February/023534.html] on 19 February 2020. On 24 March 2020, a suggested approach [https://mm.icann.org/pipermail/council/2020-March/023615.html] for addressing the Council?s work related to recommendation 27 was shared with the Council. The Council has not yet discussed how it wants to prioritize and allocate this work, which will have an impact on the Council?s work plan. * Whois Procedure Implementation Advisory Group (WPIAG) - At the Council?s 13 March 2019 meeting, it agreed to defer further discussion of the WPIAG for 12 months, reserving the right to revisit at any time. With 12 months having lapsed, what action, if any, should be taken? * Registration Directory Service Review Team (RDS-RT) - On 18 March 2020, the Council was informed [https://mm.icann.org/pipermail/council/2020-March/023606.html] that the ICANN Board passed two recommendations to the Council, in whole or in part, for its consideration as documented in the scorecard [https://www.icann.org/en/system/files/files/resolutions-board-action-rds-whois2-final-recs-25feb20-en.pdf] associated with the Board resolution [https://www.icann.org/resources/board-material/resolutions-2020-02-25-en]. The Council has not yet discussed how it will consider the two relevant recommendations (i.e., CC1 and CC.4). Here, the Council will discuss the bullet points above and discuss next steps, as applicable. 7.1 ? Introduction of topic (Council leadership) 7.2 ? Council discussion 7.3 ? Next steps ? Item 8: ANY OTHER BUSINESS (15 minutes) ? * 8.1 - GNSO Chair election timeline [https://gnso.icann.org/sites/default/files/file/field-file-attach/proposed-council-chair-27mar20-en.pdf] announced * 8.2 - EPDP Phase 2 Initial Report and latest EPDP Project Package [https://community.icann.org/x/6BdIBg] - Any questions? * 8.3 - RDS data accuracy - possible next steps? * 8.4 - Expectations for ICANN68 (if virtual)? * 8.5 - Letter [https://gnso.icann.org/sites/default/files/file/field-file-attach/botterman-to-drazek-2-11mar20-en.pdf] from the ICANN Board regarding a potential impasse concerning the implementation of EPDP Phase 1 Recommendation 7, related to Thick WHOIS Transition Policy.. ? _______________________________ Appendix 1: GNSO Council Voting Thresholds (ICANN Bylaws, Article 11, Section 11.3(i)) See https://www.icann.org/resources/pages/governance/bylaws-en/#article11 [https://www.icann.org/resources/pages/governance/bylaws-en/#article11]. Appendix 2: GNSO Council Absentee Voting Procedures (GNSO Operating Procedures, Section 4.4) See https://gnso.icann.org/sites/default/files/file/field-file-attach/op-procedures-30jan18-en.pdf [https://gnso.icann.org/sites/default/files/file/field-file-attach/op-procedures-30jan18-en.pdf] ? References for Coordinated Universal Time of 12:00 UTC? Local time between October and March Winter in the NORTHERN hemisphere ---------------------------------------------------------------------------- California, USA (PDT) UTC-7 05:00 San Jos?, Costa Rica (CST) UTC-6 06:00 New York/Washington DC, USA (EDT) UTC-4 08:00 Buenos Aires, Argentina (ART) UTC-3 09:00 Rio de Janeiro, Brazil (BRST) UTC-3 09:00 London, United Kingdom (GMT) UTC+1 13:00 Kinshasa, Democratic Republic of Congo (WAT) UTC+1 13:00 Paris, France (CEST) UTC+2 14:00 Islamabad, Pakistan (PKT) (+1 day) UTC+5 17:00? Singapore (SGT) UTC+8? 20:00? Tokyo, Japan (JST) UTC+9 21:00? Melbourne, Australia (AEST) UTC+10 22:00?? ---------------------------------------------------------------------------- DST starts/ends on Sunday 25 of October 2020, 2:00 or 3:00 local time (with exceptions) for EU countries and on Sunday 01 of November 2020 for the US. ---------------------------------------------------------------------- For other places see http://www.timeanddate.com [http://www.timeanddate.com/] and https://tinyurl.com/vau3jkd [https://tinyurl.com/vau3jkd] ? ? -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: ATT00001.txt URL: -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: att_5e83d3b025e242729520e376c1df0463.txt URL: From rafik.dammak at gmail.com Thu Apr 9 02:49:08 2020 From: rafik.dammak at gmail.com (Rafik Dammak) Date: Thu, 9 Apr 2020 08:49:08 +0900 Subject: [NCSG-PC] Draft Agenda for NCSG Monthly Policy Call 14th April In-Reply-To: References: Message-ID: Hi all, I am sharing the draft agenda for the next NCSG Policy call next Tuesday. The focus would be council agenda which is focused on: - impact of covid-19 on ICANN and council work : there was request for any input from SG/C and so it is a question for NCSG to share thoughts on how it might impact us and in which aspect. - GNSO Work prioritization: there will be a proposed framework to outline a workplan for GNSO council taking into account several parameters including the current situation with covid-19. Our task will be to review the framework and workplan. - Transfer Policy next steps: we will discuss how to proceed with the recommendations coming from the scoping team and to some extent this is related to the previous item i.e. when we can kick-off such work. The first step will be to have the issues report which is done by staff. - RDS program management: we will try here to review the several RDS related topics like EPDP wave1 report, WPIAG or RDS-RT recs and how to deal with them. We won't do the same mistake of having a heavy RDS WG. As you can see it is about planning and strategizing while having in mind the current situations and uncertainty for coming months. The policy call will be opportunity to familiarize everyone and get some input to guide us for council deliberations. For the rest of the agenda: - for policy update, I will identify/confirm with some volunteers if they can give us short updates from the WG. if we won't have enough volunteers attending, I will follow-up with asking for written update and skip this part. - Board seat election: to inform membership about the election and confirm the steps. we have to rush because the deadlines. - ICANN68: there is planning meeting scheduled next week and board is expected to make decision about ICANN68 soon. Regarding (mini-)webinars to complement the policy call, we need to have some ideas of what we would like cover as topic and schedule them. so any suggestion is welcome Please let me know if you have any comments or amendment for the agenda: I. Introduction II. GNSO Council Call Preparation - Council agenda:(TBC) III. Policy Update - Updates from PDP WG and RT if available - Public comments status: https://www.icann.org/public-comments#open-public https://community.icann.org/display/gnsononcomstake/Public+Comments+-+2020 - Any Policy topic IV. Others - Board seat election - ICANN68 Best Regards, Rafik -------------- next part -------------- An HTML attachment was scrubbed... URL: From rafik.dammak at gmail.com Thu Apr 9 03:11:23 2020 From: rafik.dammak at gmail.com (Rafik Dammak) Date: Thu, 9 Apr 2020 09:11:23 +0900 Subject: [NCSG-PC] PC Chair election / Vice-chairs appointments In-Reply-To: References: Message-ID: Hi all, following-up (with delay) on one the agreed action items which is the PC chair election and vice-chairs appointment, I am proposing here a draft process and timeline. it might sound formal compared to what we discussed previously but I am using this a draft for building fully fledged process in future: 1- Nomination period: from 17th to 24th April Nomination and self-nomination are both permitted from and within PC members (NCSG councillors, NCSG Chair, representatives from NCUC and NPOC to PC), for one year term for PC chair position. The nominee should accept the nomination and send a short SOI by the 24th April. 2- Election : from 27th April to 1st May all PC members should vote. the GNSO support staff will act as the election officer. The options in the ballot should be the candidates who confirmed by the deadline and NOTA 3- Result: should be available by 2nd May the candidate who get 2/3 vote of the NCSG?PC membership will be declared winner. 4- Vice-chairs appointments: After PC chair confirmation, a call for interest should be made to have up to 2 vice-chairs. The appointment of the volunteers will be confirmed if there is no objection within PC. this is just draft process and should be fleshed out to documented for future. I didn't outline all cases regarding the election for example. After that, the next step will be to work on job description for those positions. Please let me know your thoughts/comments on what is proposed. Best, Rafik ---------- Forwarded message --------- De : Rafik Dammak Date: lun. 2 mars 2020 ? 09:35 Subject: NCSG Policy Committee meeting follow-up To: ncsg-pc Hi all, as you know we had last week our PC meeting to discuss several items regarding election, improvements etc. We got already some action item to follow-up 1- PC chair Election: there was agreement to go with the idea of having chair and 2 vice-chairs. The point was also to have proper open process (that can be documented for future). so the action here is to agree on timeline and process (nomination, vote). it shouldn't be complicated. I believe we can get this done in this month e.g. 1 week for nomination and 1 week for voting. 2- Having a regular PC call, hopefully monthly call and coordinating more with our NCSG reps to council. The action would be to agree on regular day/time. I think that can be 2 weeks after NCSG Policy. 3- Regarding documentation and development of workflow, I believe that can be done with reworking again on PC operating procedure and documenting previous activities. I am sharing here the PC operating procedures draft being worked on before https://docs.google.com/document/d/1G_M4wBGVEyXm30m79olplfF0RNkJnDwaVBBeldDfO8U/edit . For anything missing, we can start first to identify that and have volunteers to draft it. For Chair job description, I can use what I presented and develop a draft. 4- Sharing here the slides I presented in last call: https://docs.google.com/presentation/d/1SnpMYmb6lTw1FqO6tvSqCdpgL-QMg1DJXIJGrx8vB6A/edit#slide=id.p 5- for NCSG Policy call improvements, we will have the NCSG Policy call in coming days and I will try to make some adjustments to extent of possible. It might be shorter than usual as we will have NCSG meeting next week. From April NCSG Policy call, we can start identifying other topics we would like to cover other than council meeting and usual policy updates. One activity we will need to do soon and follow-up is to work about prioritization. GNSO Council will discuss the GNSO future work soon and we need to be ready and align our work around that. That also aligns with the discussion we had about prioritizing our work and it starts with identifying what is in the pipeline. let me know if I missed anything. Best. Rafik -------------- next part -------------- An HTML attachment was scrubbed... URL: From rafik.dammak at gmail.com Thu Apr 9 13:03:22 2020 From: rafik.dammak at gmail.com (Rafik Dammak) Date: Thu, 9 Apr 2020 19:03:22 +0900 Subject: [NCSG-PC] [NCSG-EC] Fwd: PLEASE READ: NCPH election for Board seat 14 In-Reply-To: References: <57A94745-69DE-4628-8168-8F15F1C7D467@icann.org> <50546364-b2fd-bd3d-77a3-f6613a7c33e9@mail.utoronto.ca> <6539E322-F58B-410A-B3D4-A05C6C868113@ipjustice.org> <83d286ea-18e3-760e-548d-b3eb897df46e@mail.utoronto.ca> Message-ID: Addding the correct pc list address On Thu, Apr 9, 2020, 13:58 Rafik Dammak wrote: > Thanks Stephanie for sharing the info > as first action, I put this as an item for update to our membership in > next week policy call, then follow-up in list to ensure that information is > shared broadly. > with regard to the vote, we can coordinate with all representatives about > the support and appoint who will cast the vote on behalf of NCSG. I think > the vote by 20th April is doable. > > Best, > > Rafik > > Le jeu. 9 avr. 2020 ? 06:31, Stephanie E Perrin via NCSG-EC < > ncsg-ec at lists.ncsg.is> a ?crit : > >> In which case, I am happy to step back and permit the PC to organize >> this. I have reached out to Carlton Samuels, as his collaboration on this >> is required. I have not heard back from him, as yet. Over to you, Rafik. >> >> Stephanie >> On 2020-04-08 5:22 p.m., Robin Gross wrote: >> >> Hi all, >> >> I?ve add the NCSG-PC onto this thread since it is the PC who will vote >> and select our board nominee (pursuant to NCSG Charter). >> >> Thanks, >> Robin >> >> On Apr 8, 2020, at 2:20 PM, Stephanie E Perrin via NCSG-EC < >> ncsg-ec at lists.ncsg.is> wrote: >> >> I need to consult you guys, then we (csg and ncsg) need to set up an >> election, where we pick someone to vote for us, and if we get two votes for >> Matthew (ie each side votes for him) we tell staff and Council he is our >> nominee. It seems a bit clumsy but since we have had a meltdown in the >> past, we needed procedures.... >> >> I presume staff will set up that election for us, will ask Carlos Reyes >> who is now in charge of our policy support, not Mary Wong. >> >> cheers Steph >> >> PS Dean Marks is doing the same thing with the CSG guys. >> >> >> On 2020-04-08 5:16 p.m., Raphael Beauregard-Lacroix wrote: >> >> Sure, I'm just not sure what needs to be done! >> >> On Wed, Apr 8, 2020 at 1:04 PM Stephanie E Perrin via NCSG-EC < >> ncsg-ec at lists.ncsg.is> wrote: >> >>> Hi folks, we need to organize on the election of Matthew Shears for >>> Board seat 14. I have reached out to Carlton Samuels, to tick the box of >>> consulting with our nomcom appointee (no response so far) and I have been >>> chatting with Dean Marks from the CSG, who is keen to cooperate. We are >>> trying to meet this new deadline of April 20, can we organize to hold our >>> election next week in time to offer our name? The CSG thinks they can. >>> >>> Sorry to push but we have to get this done faster now due to ICANN's >>> revised timelines....since we are agreed on the candidate, it is just >>> paperwork.... >>> >>> cheers Steph >>> >>> >>> -------- Forwarded Message -------- >>> Subject: PLEASE READ: NCPH election for Board seat 14 >>> Date: Tue, 7 Apr 2020 20:17:14 +0000 >>> From: Mary Wong >>> To: Dean Marks , Stephanie E >>> Perrin >>> , Bruna Martins dos Santos >>> , Joan Kerr >>> , Rafik Dammak >>> , Selli, Claudia >>> , >>> csg-excomm at icann.org , >>> Barbara Wanner >>> CC: Chantelle Doerksen >>> , Maryam Bakoshi >>> , Andrea Glandon >>> , Carlos Reyes >>> >>> >>> Dear CSG and NCSG leaders, >>> >>> >>> I would like to apologize for bringing up this topic at this late stage, >>> and at a time when I know that many community members are focusing on >>> important personal and family matters during the current COVID-19 >>> situation. Please understand that we as staff would not have raised this >>> were it not a Bylaws-related matter. >>> >>> >>> Here is the issue: under the ICANN Bylaws, formal notification of a >>> nominee for either Board seat 13 or 14 must be provided to the Empowered >>> Community Administration at least six (6) months prior to the commencement >>> of that potential Director?s term. As the 2020 Annual General Meeting is >>> due to conclude on 22 October 2020 (which we realize is somewhat earlier >>> than previous AGMs), this means that *the Empowered Community >>> Administration must receive the Non-Contracted Parties House (NCPH) >>> nomination of a Director to fill Board seat 14 by 22 April 2020* (and >>> not May as we had advised you previously). >>> >>> >>> I understand that the NCPH?s current plan is to hold the formal vote >>> (via a CSG and NCSG representative and in accordance with the NCPH?s agreed >>> procedures) on or around 29 April. In light of the need to notify the GNSO >>> Chair of the result (as under the GNSO Operating Procedures Keith has the >>> responsibility of notifying the Empowered Community Administration), I >>> would like to ask *if it will be possible for the NCPH to complete its >>> vote on a nominee for Board seat 14 by Monday 20 April*, to allow Keith >>> time to inform the GNSO Council (as has been customary) and to formally >>> notify the Empowered Community Administration. >>> >>> >>> I and the whole GNSO support team are sincerely sorry for our previous >>> guidance to you that had mistakenly set 21 May as the final date. Please >>> accept our heartfelt apologies for this rare error as well as for the >>> inconvenience that we know our mistake must cause you and your groups. >>> >>> >>> In view of the situation, please be assured that the CSG and NCSG >>> support staff are happy to assist you with conducting the vote as >>> efficiently and smoothly as possible, to minimize disruption and >>> inconvenience to you. Please let me know if you have any questions or >>> concerns with either the timing or mechanism for the upcoming vote and, >>> once again, I am so very sorry for the trouble. >>> >>> >>> Thank you all very much for your kind understanding. >>> >>> >>> Best regards, >>> >>> Mary >>> >>> >>> _______________________________________________ >>> NCSG-EC mailing list >>> NCSG-EC at lists.ncsg.is >>> https://lists.ncsg.is/mailman/listinfo/ncsg-ec >>> >> _______________________________________________ >> NCSG-EC mailing list >> NCSG-EC at lists.ncsg.is >> https://lists.ncsg.is/mailman/listinfo/ncsg-ec >> >> >> _______________________________________________ >> NCSG-EC mailing list >> NCSG-EC at lists.ncsg.is >> https://lists.ncsg.is/mailman/listinfo/ncsg-ec >> > -------------- next part -------------- An HTML attachment was scrubbed... URL: From olga_kyryliuk at ukr.net Thu Apr 9 19:52:38 2020 From: olga_kyryliuk at ukr.net (Olga Kyryliuk) Date: Thu, 09 Apr 2020 19:52:38 +0300 Subject: [NCSG-PC] PC Chair election / Vice-chairs appointments In-Reply-To: References: Message-ID: <1586450736.48619000.hwnrgmku@frv52.fwdcdn.com> Hi Rafik, Thanks for putting this together. The procedure is clear and the deadlines seem totally doable. I have only one concern - what if a candidate for a chair position gets less than 2/3 votes but it is still the biggest number of votes? Shall we use instead majority of votes to define the result? But if it?s based on previous practice and didn?t raise any issue, then keep it as it is. I would also suggest indicating term of service for both positions.? Best, Olga 9 ?????? 2020, 03:11:42, ?? "Rafik Dammak" < rafik.dammak at gmail.com >: Hi all, following-up (with delay) on one the agreed action items which is the PC chair election and vice-chairs appointment, I am proposing here a draft process and timeline. it might sound formal compared to what we discussed previously but I am using this a draft for building fully fledged?process in future: 1- Nomination period: from 17th to 24th April Nomination and self-nomination are both permitted from and within PC members (NCSG councillors, NCSG Chair, representatives from NCUC and NPOC to PC), for one year term for PC chair position. The nominee should accept the nomination and send a short SOI by the 24th April. 2- Election : from 27th April to 1st May all PC members should vote. the GNSO support staff will act as the election officer. The options in the ballot should be the candidates who confirmed by the deadline and NOTA? 3- Result: should be available by 2nd May the candidate who get??2/3 vote of the NCSG?PC membership will be declared winner. 4- Vice-chairs appointments: After PC chair confirmation, a call for interest should be made to have up to 2 vice-chairs. The appointment of the volunteers will be confirmed if there is no objection within PC. this is just draft process and should be fleshed out to documented for future. I didn't outline all cases regarding the election for example. After that, the next step will be to work on job description for those positions. Please let me know your thoughts/comments on what is proposed. Best, Rafik ---------- Forwarded message --------- De?: Rafik Dammak Date: lun. 2 mars 2020 ??09:35 Subject: NCSG Policy Committee meeting follow-up To: ncsg-pc Hi all, as you know we had last week our PC meeting to discuss several items regarding election, improvements etc. We got already some action item to follow-up 1- PC chair Election: there was agreement to go with?the idea of having chair and 2 vice-chairs. The point was also to have proper open process (that can be documented for future). so the action here is? to agree on timeline and process (nomination, vote). it shouldn't be complicated. I believe?we can get this done in this month e.g. 1 week for nomination and 1 week for voting. 2- Having a regular PC call, hopefully monthly call and coordinating more with our NCSG reps to council. The action would be to agree on regular day/time. I think that can be 2 weeks after NCSG Policy. 3- Regarding documentation and development of workflow, I believe that can be done with reworking again on PC operating?procedure?and documenting previous activities. I am sharing here the PC operating?procedures?draft being worked on before?https://docs.google.com/document/d/1G_M4wBGVEyXm30m79olplfF0RNkJnDwaVBBeldDfO8U/edit?. For anything missing, we can start first to identify that and have volunteers to draft it. For Chair job description, I can use what I presented and develop a draft. 4- Sharing here the slides I presented in last call:?https://docs.google.com/presentation/d/1SnpMYmb6lTw1FqO6tvSqCdpgL-QMg1DJXIJGrx8vB6A/edit#slide=id.p 5- for NCSG Policy call improvements, we will have the NCSG Policy call in coming days and I will try to make some adjustments to extent of possible. It might be shorter than usual as we will have NCSG meeting next week. From April NCSG Policy call, we can start identifying other topics we would like to cover other than council meeting and usual policy updates. One activity we will need to do soon and follow-up is to work about prioritization. GNSO Council will discuss the GNSO future work soon and we need to be ready and align our work around that. That also aligns with the discussion we had about prioritizing our work and it starts with identifying what is in the pipeline. let me know if I missed anything. Best. Rafik _______________________________________________ NCSG-PC mailing list NCSG-PC at lists.ncsg.is https://lists.ncsg.is/mailman/listinfo/ncsg-pc -------------- next part -------------- An HTML attachment was scrubbed... URL: From rafik.dammak at gmail.com Fri Apr 10 00:51:31 2020 From: rafik.dammak at gmail.com (Rafik Dammak) Date: Fri, 10 Apr 2020 06:51:31 +0900 Subject: [NCSG-PC] PC Chair election / Vice-chairs appointments In-Reply-To: <1586450736.48619000.hwnrgmku@frv52.fwdcdn.com> References: <1586450736.48619000.hwnrgmku@frv52.fwdcdn.com> Message-ID: Hi Olga, thanks for the comments, Le ven. 10 avr. 2020 ? 01:52, Olga Kyryliuk a ?crit : > Hi Rafik, > > Thanks for putting this together. The procedure is clear and the deadlines > seem totally doable. I have only one concern - what if a candidate for a > chair position gets less than 2/3 votes but it is still the biggest number > of votes? Shall we use instead majority of votes to define the result? But > if it?s based on previous practice and didn?t raise any issue, then keep it > as it is. > > the 2/3 threshold provision is mentioned in the charter. the practice at least from GNSO OP side (e.g. GNSO chair election) if no candidate reach the threshold, it is to run another round with the candidate having most of the votes to run against NOTA. if that round doesn't end with the candidate having 2/3 the a new election is required .that is in term of process and procedure. I would also suggest indicating term of service for both positions. > it is 1 year term. the charter doesn't mention any term limit. Best, Rafik > > > * 9 ?????? 2020, 03:11:42, ?? "Rafik Dammak" < rafik.dammak at gmail.com > >: * > > Hi all, > > following-up (with delay) on one the agreed action items which is the PC > chair election and vice-chairs appointment, I am proposing here a draft > process and timeline. it might sound formal compared to what we discussed > previously but I am using this a draft for building fully fledged process > in future: > > 1- Nomination period: from 17th to 24th April > > Nomination and self-nomination are both permitted from and within PC > members (NCSG councillors, NCSG Chair, representatives from NCUC and NPOC > to PC), for one year term for PC chair position. > The nominee should accept the nomination and send a short SOI by the 24th > April. > > 2- Election : from 27th April to 1st May > > all PC members should vote. the GNSO support staff will act as the > election officer. The options in the ballot should be the candidates who > confirmed by the deadline and NOTA > > 3- Result: should be available by 2nd May > > the candidate who get 2/3 vote of the NCSG?PC membership will be > declared winner. > > 4- Vice-chairs appointments: > > After PC chair confirmation, a call for interest should be made to have up > to 2 vice-chairs. The appointment of the volunteers will be confirmed if > there is no objection within PC. > > > this is just draft process and should be fleshed out to documented for > future. I didn't outline all cases regarding the election for example. > After that, the next step will be to work on job description for those > positions. > > Please let me know your thoughts/comments on what is proposed. > > Best, > > Rafik > > > ---------- Forwarded message --------- > De : *Rafik Dammak* > Date: lun. 2 mars 2020 ? 09:35 > Subject: NCSG Policy Committee meeting follow-up > To: ncsg-pc > > > Hi all, > > as you know we had last week our PC meeting to discuss several items > regarding election, improvements etc. We got already some action item to > follow-up > > 1- PC chair Election: there was agreement to go with the idea of having > chair and 2 vice-chairs. The point was also to have proper open process > (that can be documented for future). so the action here is to agree on > timeline and process (nomination, vote). it shouldn't be complicated. I > believe we can get this done in this month e.g. 1 week for nomination and 1 > week for voting. > 2- Having a regular PC call, hopefully monthly call and coordinating more > with our NCSG reps to council. The action would be to agree on regular > day/time. I think that can be 2 weeks after NCSG Policy. > 3- Regarding documentation and development of workflow, I believe that can > be done with reworking again on PC operating procedure and documenting > previous activities. I am sharing here the PC operating procedures draft > being worked on before > https://docs.google.com/document/d/1G_M4wBGVEyXm30m79olplfF0RNkJnDwaVBBeldDfO8U/edit . > For anything missing, we can start first to identify that and have > volunteers to draft it. For Chair job description, I can use what I > presented and develop a draft. > 4- Sharing here the slides I presented in last call: > https://docs.google.com/presentation/d/1SnpMYmb6lTw1FqO6tvSqCdpgL-QMg1DJXIJGrx8vB6A/edit#slide=id.p > 5- for NCSG Policy call improvements, we will have the NCSG Policy call in > coming days and I will try to make some adjustments to extent of possible. > It might be shorter than usual as we will have NCSG meeting next week. From > April NCSG Policy call, we can start identifying other topics we would like > to cover other than council meeting and usual policy updates. > > One activity we will need to do soon and follow-up is to work about > prioritization. GNSO Council will discuss the GNSO future work soon and we > need to be ready and align our work around that. That also aligns with the > discussion we had about prioritizing our work and it starts with > identifying what is in the pipeline. > > let me know if I missed anything. > > Best. > > Rafik > > _______________________________________________ > NCSG-PC mailing listNCSG-PC at lists.ncsg.ishttps://lists.ncsg.is/mailman/listinfo/ncsg-pc > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From rafik.dammak at gmail.com Fri Apr 10 02:14:36 2020 From: rafik.dammak at gmail.com (Rafik Dammak) Date: Fri, 10 Apr 2020 08:14:36 +0900 Subject: [NCSG-PC] [NCSG-Discuss] Public Comment: Revised Community Travel Support Guidelines In-Reply-To: References: <196c3ee1-49f6-df88-e2d7-403edb64365b@wtec.org.ng> Message-ID: hi all, a reminder to review the draft comment. Best, Rafik Le mer. 8 avr. 2020 ? 20:54, Rafik Dammak a ?crit : > hi all, > > we have a draft comment for review. the deadline for submission is the 13 > thApril. > > Best, > > Rafik > > ---------- Forwarded message --------- > De : Oreoluwa Somolu Lesi > Date: mer. 8 avr. 2020 ? 05:38 > Subject: [NCSG-Discuss] Public Comment: Revised Community Travel Support > Guidelines > To: > > > Hello everyone, > > Muriel Alapini, Pascal Bekono and I drafted a comment on behalf of NCSG > for the call for public comments for the *Revised Community Travel > Support Guidelines*. > > > https://docs.google.com/document/d/18QoHr3Un3HFvLy6jClpl_ESWkXqZLdvrspQLjudP75k/edit > > We invite the community to review. > > The deadline for submission for comments is next Monday, April 13, which > is Easter Monday for those who celebrate this. Therefore we would like to > get all comments in by *Wednesday, April 8* so that the PC can review and > the final version submitted by Thursday, April 9. Apologies for this tight > deadline. > > Thank you all for your input. > > Kind regards, > > Ore > -- > Oreoluwa Lesi > Executive Director, Women's Technology Empowerment Centre (W.TEC) > +234.803.621.1307, +234.813.339.9999 | www.wtec.org.ng > | @wteconline > > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From rafik.dammak at gmail.com Mon Apr 13 11:18:15 2020 From: rafik.dammak at gmail.com (Rafik Dammak) Date: Mon, 13 Apr 2020 17:18:15 +0900 Subject: [NCSG-PC] [NCSG-Discuss] Public Comment: Revised Community Travel Support Guidelines In-Reply-To: References: <196c3ee1-49f6-df88-e2d7-403edb64365b@wtec.org.ng> Message-ID: Hi all, today is the deadline for submission of the comment. please speak up if you have any strong objection, Best, Rafik Le ven. 10 avr. 2020 ? 08:14, Rafik Dammak a ?crit : > hi all, > > a reminder to review the draft comment. > > Best, > > Rafik > Le mer. 8 avr. 2020 ? 20:54, Rafik Dammak a > ?crit : > >> hi all, >> >> we have a draft comment for review. the deadline for submission is the 13 >> thApril. >> >> Best, >> >> Rafik >> >> ---------- Forwarded message --------- >> De : Oreoluwa Somolu Lesi >> Date: mer. 8 avr. 2020 ? 05:38 >> Subject: [NCSG-Discuss] Public Comment: Revised Community Travel Support >> Guidelines >> To: >> >> >> Hello everyone, >> >> Muriel Alapini, Pascal Bekono and I drafted a comment on behalf of NCSG >> for the call for public comments for the *Revised Community Travel >> Support Guidelines*. >> >> >> https://docs.google.com/document/d/18QoHr3Un3HFvLy6jClpl_ESWkXqZLdvrspQLjudP75k/edit >> >> We invite the community to review. >> >> The deadline for submission for comments is next Monday, April 13, which >> is Easter Monday for those who celebrate this. Therefore we would like to >> get all comments in by *Wednesday, April 8* so that the PC can review >> and the final version submitted by Thursday, April 9. Apologies for this >> tight deadline. >> >> Thank you all for your input. >> >> Kind regards, >> >> Ore >> -- >> Oreoluwa Lesi >> Executive Director, Women's Technology Empowerment Centre (W.TEC) >> +234.803.621.1307, +234.813.339.9999 | www.wtec.org.ng >> | @wteconline >> >> >> >> -------------- next part -------------- An HTML attachment was scrubbed... URL: From rafik.dammak at gmail.com Mon Apr 13 11:20:02 2020 From: rafik.dammak at gmail.com (Rafik Dammak) Date: Mon, 13 Apr 2020 17:20:02 +0900 Subject: [NCSG-PC] [NCSG-EC] Fwd: PLEASE READ: NCPH election for Board seat 14 In-Reply-To: References: <57A94745-69DE-4628-8168-8F15F1C7D467@icann.org> <50546364-b2fd-bd3d-77a3-f6613a7c33e9@mail.utoronto.ca> <6539E322-F58B-410A-B3D4-A05C6C868113@ipjustice.org> <83d286ea-18e3-760e-548d-b3eb897df46e@mail.utoronto.ca> Message-ID: Hi all, please let me know if there is any comment or question. we should appoint who will vote on behalf of NCSG. Best, Rafik Le jeu. 9 avr. 2020 ? 19:03, Rafik Dammak a ?crit : > Addding the correct pc list address > > On Thu, Apr 9, 2020, 13:58 Rafik Dammak wrote: > >> Thanks Stephanie for sharing the info >> as first action, I put this as an item for update to our membership in >> next week policy call, then follow-up in list to ensure that information is >> shared broadly. >> with regard to the vote, we can coordinate with all representatives about >> the support and appoint who will cast the vote on behalf of NCSG. I think >> the vote by 20th April is doable. >> >> Best, >> >> Rafik >> >> Le jeu. 9 avr. 2020 ? 06:31, Stephanie E Perrin via NCSG-EC < >> ncsg-ec at lists.ncsg.is> a ?crit : >> >>> In which case, I am happy to step back and permit the PC to organize >>> this. I have reached out to Carlton Samuels, as his collaboration on this >>> is required. I have not heard back from him, as yet. Over to you, Rafik. >>> >>> Stephanie >>> On 2020-04-08 5:22 p.m., Robin Gross wrote: >>> >>> Hi all, >>> >>> I?ve add the NCSG-PC onto this thread since it is the PC who will vote >>> and select our board nominee (pursuant to NCSG Charter). >>> >>> Thanks, >>> Robin >>> >>> On Apr 8, 2020, at 2:20 PM, Stephanie E Perrin via NCSG-EC < >>> ncsg-ec at lists.ncsg.is> wrote: >>> >>> I need to consult you guys, then we (csg and ncsg) need to set up an >>> election, where we pick someone to vote for us, and if we get two votes for >>> Matthew (ie each side votes for him) we tell staff and Council he is our >>> nominee. It seems a bit clumsy but since we have had a meltdown in the >>> past, we needed procedures.... >>> >>> I presume staff will set up that election for us, will ask Carlos Reyes >>> who is now in charge of our policy support, not Mary Wong. >>> >>> cheers Steph >>> >>> PS Dean Marks is doing the same thing with the CSG guys. >>> >>> >>> On 2020-04-08 5:16 p.m., Raphael Beauregard-Lacroix wrote: >>> >>> Sure, I'm just not sure what needs to be done! >>> >>> On Wed, Apr 8, 2020 at 1:04 PM Stephanie E Perrin via NCSG-EC < >>> ncsg-ec at lists.ncsg.is> wrote: >>> >>>> Hi folks, we need to organize on the election of Matthew Shears for >>>> Board seat 14. I have reached out to Carlton Samuels, to tick the box of >>>> consulting with our nomcom appointee (no response so far) and I have been >>>> chatting with Dean Marks from the CSG, who is keen to cooperate. We are >>>> trying to meet this new deadline of April 20, can we organize to hold our >>>> election next week in time to offer our name? The CSG thinks they can. >>>> >>>> Sorry to push but we have to get this done faster now due to ICANN's >>>> revised timelines....since we are agreed on the candidate, it is just >>>> paperwork.... >>>> >>>> cheers Steph >>>> >>>> >>>> -------- Forwarded Message -------- >>>> Subject: PLEASE READ: NCPH election for Board seat 14 >>>> Date: Tue, 7 Apr 2020 20:17:14 +0000 >>>> From: Mary Wong >>>> To: Dean Marks , Stephanie E >>>> Perrin >>>> , Bruna Martins dos Santos >>>> , Joan Kerr >>>> , Rafik Dammak >>>> , Selli, Claudia >>>> , >>>> csg-excomm at icann.org , >>>> Barbara Wanner >>>> CC: Chantelle Doerksen >>>> , Maryam Bakoshi >>>> , Andrea Glandon >>>> , Carlos Reyes >>>> >>>> >>>> Dear CSG and NCSG leaders, >>>> >>>> >>>> I would like to apologize for bringing up this topic at this late >>>> stage, and at a time when I know that many community members are focusing >>>> on important personal and family matters during the current COVID-19 >>>> situation. Please understand that we as staff would not have raised this >>>> were it not a Bylaws-related matter. >>>> >>>> >>>> Here is the issue: under the ICANN Bylaws, formal notification of a >>>> nominee for either Board seat 13 or 14 must be provided to the Empowered >>>> Community Administration at least six (6) months prior to the commencement >>>> of that potential Director?s term. As the 2020 Annual General Meeting is >>>> due to conclude on 22 October 2020 (which we realize is somewhat earlier >>>> than previous AGMs), this means that *the Empowered Community >>>> Administration must receive the Non-Contracted Parties House (NCPH) >>>> nomination of a Director to fill Board seat 14 by 22 April 2020* (and >>>> not May as we had advised you previously). >>>> >>>> >>>> I understand that the NCPH?s current plan is to hold the formal vote >>>> (via a CSG and NCSG representative and in accordance with the NCPH?s agreed >>>> procedures) on or around 29 April. In light of the need to notify the GNSO >>>> Chair of the result (as under the GNSO Operating Procedures Keith has the >>>> responsibility of notifying the Empowered Community Administration), I >>>> would like to ask *if it will be possible for the NCPH to complete its >>>> vote on a nominee for Board seat 14 by Monday 20 April*, to allow >>>> Keith time to inform the GNSO Council (as has been customary) and to >>>> formally notify the Empowered Community Administration. >>>> >>>> >>>> I and the whole GNSO support team are sincerely sorry for our previous >>>> guidance to you that had mistakenly set 21 May as the final date. Please >>>> accept our heartfelt apologies for this rare error as well as for the >>>> inconvenience that we know our mistake must cause you and your groups. >>>> >>>> >>>> In view of the situation, please be assured that the CSG and NCSG >>>> support staff are happy to assist you with conducting the vote as >>>> efficiently and smoothly as possible, to minimize disruption and >>>> inconvenience to you. Please let me know if you have any questions or >>>> concerns with either the timing or mechanism for the upcoming vote and, >>>> once again, I am so very sorry for the trouble. >>>> >>>> >>>> Thank you all very much for your kind understanding. >>>> >>>> >>>> Best regards, >>>> >>>> Mary >>>> >>>> >>>> _______________________________________________ >>>> NCSG-EC mailing list >>>> NCSG-EC at lists.ncsg.is >>>> https://lists.ncsg.is/mailman/listinfo/ncsg-ec >>>> >>> _______________________________________________ >>> NCSG-EC mailing list >>> NCSG-EC at lists.ncsg.is >>> https://lists.ncsg.is/mailman/listinfo/ncsg-ec >>> >>> >>> _______________________________________________ >>> NCSG-EC mailing list >>> NCSG-EC at lists.ncsg.is >>> https://lists.ncsg.is/mailman/listinfo/ncsg-ec >>> >> -------------- next part -------------- An HTML attachment was scrubbed... URL: From lists at icann.guru Mon Apr 13 11:22:36 2020 From: lists at icann.guru (lists at icann.guru) Date: Mon, 13 Apr 2020 09:22:36 +0100 Subject: [NCSG-PC] [NCSG-EC] Fwd: PLEASE READ: NCPH election for Board seat 14 In-Reply-To: References: <57A94745-69DE-4628-8168-8F15F1C7D467@icann.org> <50546364-b2fd-bd3d-77a3-f6613a7c33e9@mail.utoronto.ca> <6539E322-F58B-410A-B3D4-A05C6C868113@ipjustice.org> <83d286ea-18e3-760e-548d-b3eb897df46e@mail.utoronto.ca> Message-ID: I assume that you as the PC Chair will vote on our behalf? --- James Gannon On 13/04/2020 09:20:26, Rafik Dammak wrote: Hi all, please let me know if there is any comment or question. we should appoint who will vote on behalf of NCSG. Best, Rafik Le?jeu. 9 avr. 2020 ??19:03, Rafik Dammak a ?crit?: Addding the correct pc list address On Thu, Apr 9, 2020, 13:58 Rafik Dammak wrote: Thanks Stephanie for sharing the info as first action, I put this as an item for update to our membership in next week policy call, then follow-up in list to ensure that information is shared broadly. with regard to the vote, we can coordinate with all representatives about the support and appoint who will cast the vote on behalf of NCSG.? I think the vote by 20th April is doable.? Best, Rafik Le?jeu. 9 avr. 2020 ??06:31, Stephanie E Perrin via NCSG-EC a ?crit?: In which case, I am happy to step back and permit the PC to organize this.? I have reached out to Carlton Samuels, as his collaboration on this is required.? I have not heard back from him, as yet.? Over to you, Rafik. Stephanie On 2020-04-08 5:22 p.m., Robin Gross wrote: Hi all, I?ve add the NCSG-PC onto this thread since it is the PC who will vote and select our board nominee (pursuant to NCSG Charter). Thanks, Robin On Apr 8, 2020, at 2:20 PM, Stephanie E Perrin via NCSG-EC wrote: I need to consult you guys, then we (csg and ncsg) need to set up an election, where we pick someone to vote for us, and if we get two votes for Matthew (ie each side votes for him) we tell staff and Council he is our nominee.? It seems a bit clumsy but since we have had a meltdown in the past, we needed procedures.... I presume staff will set up that election for us, will ask Carlos Reyes who is now in charge of our policy support, not Mary Wong. cheers Steph PS Dean Marks is doing the same thing with the CSG guys. On 2020-04-08 5:16 p.m., Raphael Beauregard-Lacroix wrote: Sure, I'm just not sure what needs to be done!? On Wed, Apr 8, 2020 at 1:04 PM Stephanie E Perrin via NCSG-EC wrote: Hi folks, we need to organize on the election of Matthew Shears for Board seat 14.? I have reached out to Carlton Samuels, to tick the box of consulting with our nomcom appointee (no response so far) and I have been chatting with Dean Marks from the CSG, who is keen to cooperate.? We are trying to meet this new deadline of April 20, can we organize to hold our election next week in time to offer our name?? The CSG thinks they can. Sorry to push but we have to get this done faster now due to ICANN's revised timelines....since we are agreed on the candidate, it is just paperwork.... cheers Steph -------- Forwarded Message -------- Subject: PLEASE READ: NCPH election for Board seat 14 Date: Tue, 7 Apr 2020 20:17:14 +0000 From: Mary Wong [mailto:mary.wong at icann.org] To: Dean Marks [mailto:ed4coa at gmail.com], Stephanie E Perrin [mailto:stephanie.perrin at mail.utoronto.ca], Bruna Martins dos Santos [mailto:bruna.mrtns at gmail.com], Joan Kerr [mailto:joankerr at FBSC.ORG], Rafik Dammak [mailto:rafik.dammak at gmail.com], Selli, Claudia [mailto:claudia.selli at intl.att.com], csg-excomm at icann.org [mailto:csg-excomm at icann.org] [mailto:csg-excomm at icann.org], Barbara Wanner [mailto:bwanner at uscib.org] CC: Chantelle Doerksen [mailto:chantelle.doerksen at icann.org], Maryam Bakoshi [mailto:maryam.bakoshi at icann.org], Andrea Glandon [mailto:andrea.glandon at icann.org], Carlos Reyes [mailto:carlos.reyes at icann.org] Dear CSG and NCSG leaders, ? I would like to apologize for bringing up this topic at this late stage, and at a time when I know that many community members are focusing on important personal and family matters during the current COVID-19 situation. Please understand that we as staff would not have raised this were it not a Bylaws-related matter. ? Here is the issue: under the ICANN Bylaws, formal notification of a nominee for either Board seat 13 or 14 must be provided to the Empowered Community Administration at least six (6) months prior to the commencement of that potential Director?s term. As the 2020 Annual General Meeting is due to conclude on 22 October 2020 (which we realize is somewhat earlier than previous AGMs), this means that the Empowered Community Administration must receive the Non-Contracted Parties House (NCPH) nomination of a Director to fill Board seat 14 by 22 April 2020 (and not May as we had advised you previously). ? I understand that the NCPH?s current plan is to hold the formal vote (via a CSG and NCSG representative and in accordance with the NCPH?s agreed procedures) on or around 29 April. In light of the need to notify the GNSO Chair of the result (as under the GNSO Operating Procedures Keith has the responsibility of notifying the Empowered Community Administration), I would like to ask if it will be possible for the NCPH to complete its vote on a nominee for Board seat 14 by Monday 20 April, to allow Keith time to inform the GNSO Council (as has been customary) and to formally notify the Empowered Community Administration. ? I and the whole GNSO support team are sincerely sorry for our previous guidance to you that had mistakenly set 21 May as the final date. Please accept our heartfelt apologies for this rare error as well as for the inconvenience that we know our mistake must cause you and your groups. ? In view of the situation, please be assured that the CSG and NCSG support staff are happy to assist you with conducting the vote as efficiently and smoothly as possible, to minimize disruption and inconvenience to you. Please let me know if you have any questions or concerns with either the timing or mechanism for the upcoming vote and, once again, I am so very sorry for the trouble. ? Thank you all very much for your kind understanding. ? Best regards, Mary ? ? _______________________________________________ NCSG-EC mailing list NCSG-EC at lists.ncsg.is [mailto:NCSG-EC at lists.ncsg.is] https://lists.ncsg.is/mailman/listinfo/ncsg-ec [https://lists.ncsg.is/mailman/listinfo/ncsg-ec] _______________________________________________ NCSG-EC mailing list NCSG-EC at lists.ncsg.is [mailto:NCSG-EC at lists.ncsg.is] https://lists.ncsg.is/mailman/listinfo/ncsg-ec [https://lists.ncsg.is/mailman/listinfo/ncsg-ec] _______________________________________________ NCSG-EC mailing list NCSG-EC at lists.ncsg.is [mailto:NCSG-EC at lists.ncsg.is] https://lists.ncsg.is/mailman/listinfo/ncsg-ec [https://lists.ncsg.is/mailman/listinfo/ncsg-ec] _______________________________________________ NCSG-PC mailing list NCSG-PC at lists.ncsg.is https://lists.ncsg.is/mailman/listinfo/ncsg-pc -------------- next part -------------- An HTML attachment was scrubbed... URL: From rafik.dammak at gmail.com Mon Apr 13 16:30:42 2020 From: rafik.dammak at gmail.com (Rafik Dammak) Date: Mon, 13 Apr 2020 22:30:42 +0900 Subject: [NCSG-PC] [NCSG-EC] Fwd: PLEASE READ: NCPH election for Board seat 14 In-Reply-To: References: <57A94745-69DE-4628-8168-8F15F1C7D467@icann.org> <50546364-b2fd-bd3d-77a3-f6613a7c33e9@mail.utoronto.ca> <6539E322-F58B-410A-B3D4-A05C6C868113@ipjustice.org> <83d286ea-18e3-760e-548d-b3eb897df46e@mail.utoronto.ca> Message-ID: Hi James, thanks, short answer, not necessarily :) Best, Rafik Le lun. 13 avr. 2020 ? 17:22, lists at icann.guru a ?crit : > I assume that you as the PC Chair will vote on our behalf? > > *---* > *James Gannon* > > On 13/04/2020 09:20:26, Rafik Dammak wrote: > Hi all, > > please let me know if there is any comment or question. > we should appoint who will vote on behalf of NCSG. > > Best, > > Rafik > > Le jeu. 9 avr. 2020 ? 19:03, Rafik Dammak a > ?crit : > >> Addding the correct pc list address >> >> On Thu, Apr 9, 2020, 13:58 Rafik Dammak wrote: >> >>> Thanks Stephanie for sharing the info >>> as first action, I put this as an item for update to our membership in >>> next week policy call, then follow-up in list to ensure that information is >>> shared broadly. >>> with regard to the vote, we can coordinate with all representatives >>> about the support and appoint who will cast the vote on behalf of NCSG. I >>> think the vote by 20th April is doable. >>> >>> Best, >>> >>> Rafik >>> >>> Le jeu. 9 avr. 2020 ? 06:31, Stephanie E Perrin via NCSG-EC < >>> ncsg-ec at lists.ncsg.is> a ?crit : >>> >>>> In which case, I am happy to step back and permit the PC to organize >>>> this. I have reached out to Carlton Samuels, as his collaboration on this >>>> is required. I have not heard back from him, as yet. Over to you, Rafik. >>>> >>>> Stephanie >>>> On 2020-04-08 5:22 p.m., Robin Gross wrote: >>>> >>>> Hi all, >>>> >>>> I?ve add the NCSG-PC onto this thread since it is the PC who will vote >>>> and select our board nominee (pursuant to NCSG Charter). >>>> >>>> Thanks, >>>> Robin >>>> >>>> On Apr 8, 2020, at 2:20 PM, Stephanie E Perrin via NCSG-EC < >>>> ncsg-ec at lists.ncsg.is> wrote: >>>> >>>> I need to consult you guys, then we (csg and ncsg) need to set up an >>>> election, where we pick someone to vote for us, and if we get two votes for >>>> Matthew (ie each side votes for him) we tell staff and Council he is our >>>> nominee. It seems a bit clumsy but since we have had a meltdown in the >>>> past, we needed procedures.... >>>> >>>> I presume staff will set up that election for us, will ask Carlos Reyes >>>> who is now in charge of our policy support, not Mary Wong. >>>> >>>> cheers Steph >>>> >>>> PS Dean Marks is doing the same thing with the CSG guys. >>>> >>>> >>>> On 2020-04-08 5:16 p.m., Raphael Beauregard-Lacroix wrote: >>>> >>>> Sure, I'm just not sure what needs to be done! >>>> >>>> On Wed, Apr 8, 2020 at 1:04 PM Stephanie E Perrin via NCSG-EC < >>>> ncsg-ec at lists.ncsg.is> wrote: >>>> >>>>> Hi folks, we need to organize on the election of Matthew Shears for >>>>> Board seat 14. I have reached out to Carlton Samuels, to tick the box of >>>>> consulting with our nomcom appointee (no response so far) and I have been >>>>> chatting with Dean Marks from the CSG, who is keen to cooperate. We are >>>>> trying to meet this new deadline of April 20, can we organize to hold our >>>>> election next week in time to offer our name? The CSG thinks they can. >>>>> >>>>> Sorry to push but we have to get this done faster now due to ICANN's >>>>> revised timelines....since we are agreed on the candidate, it is just >>>>> paperwork.... >>>>> >>>>> cheers Steph >>>>> >>>>> >>>>> -------- Forwarded Message -------- >>>>> Subject: PLEASE READ: NCPH election for Board seat 14 >>>>> Date: Tue, 7 Apr 2020 20:17:14 +0000 >>>>> From: Mary Wong >>>>> To: Dean Marks , Stephanie E >>>>> Perrin >>>>> , Bruna Martins dos Santos >>>>> , Joan Kerr >>>>> , Rafik Dammak >>>>> , Selli, Claudia >>>>> , >>>>> csg-excomm at icann.org , >>>>> Barbara Wanner >>>>> CC: Chantelle Doerksen >>>>> , Maryam Bakoshi >>>>> , Andrea Glandon >>>>> , Carlos Reyes >>>>> >>>>> >>>>> Dear CSG and NCSG leaders, >>>>> >>>>> >>>>> I would like to apologize for bringing up this topic at this late >>>>> stage, and at a time when I know that many community members are focusing >>>>> on important personal and family matters during the current COVID-19 >>>>> situation. Please understand that we as staff would not have raised this >>>>> were it not a Bylaws-related matter. >>>>> >>>>> >>>>> Here is the issue: under the ICANN Bylaws, formal notification of a >>>>> nominee for either Board seat 13 or 14 must be provided to the Empowered >>>>> Community Administration at least six (6) months prior to the commencement >>>>> of that potential Director?s term. As the 2020 Annual General Meeting is >>>>> due to conclude on 22 October 2020 (which we realize is somewhat earlier >>>>> than previous AGMs), this means that *the Empowered Community >>>>> Administration must receive the Non-Contracted Parties House (NCPH) >>>>> nomination of a Director to fill Board seat 14 by 22 April 2020* (and >>>>> not May as we had advised you previously). >>>>> >>>>> >>>>> I understand that the NCPH?s current plan is to hold the formal vote >>>>> (via a CSG and NCSG representative and in accordance with the NCPH?s agreed >>>>> procedures) on or around 29 April. In light of the need to notify the GNSO >>>>> Chair of the result (as under the GNSO Operating Procedures Keith has the >>>>> responsibility of notifying the Empowered Community Administration), I >>>>> would like to ask *if it will be possible for the NCPH to complete >>>>> its vote on a nominee for Board seat 14 by Monday 20 April*, to allow >>>>> Keith time to inform the GNSO Council (as has been customary) and to >>>>> formally notify the Empowered Community Administration. >>>>> >>>>> >>>>> I and the whole GNSO support team are sincerely sorry for our previous >>>>> guidance to you that had mistakenly set 21 May as the final date. Please >>>>> accept our heartfelt apologies for this rare error as well as for the >>>>> inconvenience that we know our mistake must cause you and your groups. >>>>> >>>>> >>>>> In view of the situation, please be assured that the CSG and NCSG >>>>> support staff are happy to assist you with conducting the vote as >>>>> efficiently and smoothly as possible, to minimize disruption and >>>>> inconvenience to you. Please let me know if you have any questions or >>>>> concerns with either the timing or mechanism for the upcoming vote and, >>>>> once again, I am so very sorry for the trouble. >>>>> >>>>> >>>>> Thank you all very much for your kind understanding. >>>>> >>>>> >>>>> Best regards, >>>>> >>>>> Mary >>>>> >>>>> >>>>> _______________________________________________ >>>>> NCSG-EC mailing list >>>>> NCSG-EC at lists.ncsg.is >>>>> https://lists.ncsg.is/mailman/listinfo/ncsg-ec >>>>> >>>> _______________________________________________ >>>> NCSG-EC mailing list >>>> NCSG-EC at lists.ncsg.is >>>> https://lists.ncsg.is/mailman/listinfo/ncsg-ec >>>> >>>> >>>> _______________________________________________ >>>> NCSG-EC mailing list >>>> NCSG-EC at lists.ncsg.is >>>> https://lists.ncsg.is/mailman/listinfo/ncsg-ec >>>> >>> _______________________________________________ NCSG-PC mailing list > NCSG-PC at lists.ncsg.is https://lists.ncsg.is/mailman/listinfo/ncsg-pc > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From lists at icann.guru Mon Apr 13 16:40:33 2020 From: lists at icann.guru (lists at icann.guru) Date: Mon, 13 Apr 2020 14:40:33 +0100 Subject: [NCSG-PC] [NCSG-EC] Fwd: PLEASE READ: NCPH election for Board seat 14 In-Reply-To: References: <57A94745-69DE-4628-8168-8F15F1C7D467@icann.org> <50546364-b2fd-bd3d-77a3-f6613a7c33e9@mail.utoronto.ca> <6539E322-F58B-410A-B3D4-A05C6C868113@ipjustice.org> <83d286ea-18e3-760e-548d-b3eb897df46e@mail.utoronto.ca> Message-ID: Hah ok, well in that case I propose you vote for Matt on our behalf =) --- James Gannon On 13/04/2020 14:30:55, Rafik Dammak wrote: Hi James, thanks, short answer, not necessarily :)? Best, Rafik Le?lun. 13 avr. 2020 ??17:22, lists at icann.guru a ?crit?: I assume that you as the PC Chair will vote on our behalf? --- James Gannon On 13/04/2020 09:20:26, Rafik Dammak wrote: Hi all, please let me know if there is any comment or question. we should appoint who will vote on behalf of NCSG. Best, Rafik Le?jeu. 9 avr. 2020 ??19:03, Rafik Dammak a ?crit?: Addding the correct pc list address On Thu, Apr 9, 2020, 13:58 Rafik Dammak wrote: Thanks Stephanie for sharing the info as first action, I put this as an item for update to our membership in next week policy call, then follow-up in list to ensure that information is shared broadly. with regard to the vote, we can coordinate with all representatives about the support and appoint who will cast the vote on behalf of NCSG.? I think the vote by 20th April is doable.? Best, Rafik Le?jeu. 9 avr. 2020 ??06:31, Stephanie E Perrin via NCSG-EC a ?crit?: In which case, I am happy to step back and permit the PC to organize this.? I have reached out to Carlton Samuels, as his collaboration on this is required.? I have not heard back from him, as yet.? Over to you, Rafik. Stephanie On 2020-04-08 5:22 p.m., Robin Gross wrote: Hi all, I?ve add the NCSG-PC onto this thread since it is the PC who will vote and select our board nominee (pursuant to NCSG Charter). Thanks, Robin On Apr 8, 2020, at 2:20 PM, Stephanie E Perrin via NCSG-EC wrote: I need to consult you guys, then we (csg and ncsg) need to set up an election, where we pick someone to vote for us, and if we get two votes for Matthew (ie each side votes for him) we tell staff and Council he is our nominee.? It seems a bit clumsy but since we have had a meltdown in the past, we needed procedures.... I presume staff will set up that election for us, will ask Carlos Reyes who is now in charge of our policy support, not Mary Wong. cheers Steph PS Dean Marks is doing the same thing with the CSG guys. On 2020-04-08 5:16 p.m., Raphael Beauregard-Lacroix wrote: Sure, I'm just not sure what needs to be done!? On Wed, Apr 8, 2020 at 1:04 PM Stephanie E Perrin via NCSG-EC wrote: Hi folks, we need to organize on the election of Matthew Shears for Board seat 14.? I have reached out to Carlton Samuels, to tick the box of consulting with our nomcom appointee (no response so far) and I have been chatting with Dean Marks from the CSG, who is keen to cooperate.? We are trying to meet this new deadline of April 20, can we organize to hold our election next week in time to offer our name?? The CSG thinks they can. Sorry to push but we have to get this done faster now due to ICANN's revised timelines....since we are agreed on the candidate, it is just paperwork.... cheers Steph -------- Forwarded Message -------- Subject: PLEASE READ: NCPH election for Board seat 14 Date: Tue, 7 Apr 2020 20:17:14 +0000 From: Mary Wong [mailto:mary.wong at icann.org] To: Dean Marks [mailto:ed4coa at gmail.com], Stephanie E Perrin [mailto:stephanie.perrin at mail.utoronto.ca], Bruna Martins dos Santos [mailto:bruna.mrtns at gmail.com], Joan Kerr [mailto:joankerr at FBSC.ORG], Rafik Dammak [mailto:rafik.dammak at gmail.com], Selli, Claudia [mailto:claudia.selli at intl.att.com], csg-excomm at icann.org [mailto:csg-excomm at icann.org] [mailto:csg-excomm at icann.org], Barbara Wanner [mailto:bwanner at uscib.org] CC: Chantelle Doerksen [mailto:chantelle.doerksen at icann.org], Maryam Bakoshi [mailto:maryam.bakoshi at icann.org], Andrea Glandon [mailto:andrea.glandon at icann.org], Carlos Reyes [mailto:carlos.reyes at icann.org] Dear CSG and NCSG leaders, ? I would like to apologize for bringing up this topic at this late stage, and at a time when I know that many community members are focusing on important personal and family matters during the current COVID-19 situation. Please understand that we as staff would not have raised this were it not a Bylaws-related matter. ? Here is the issue: under the ICANN Bylaws, formal notification of a nominee for either Board seat 13 or 14 must be provided to the Empowered Community Administration at least six (6) months prior to the commencement of that potential Director?s term. As the 2020 Annual General Meeting is due to conclude on 22 October 2020 (which we realize is somewhat earlier than previous AGMs), this means that the Empowered Community Administration must receive the Non-Contracted Parties House (NCPH) nomination of a Director to fill Board seat 14 by 22 April 2020 (and not May as we had advised you previously). ? I understand that the NCPH?s current plan is to hold the formal vote (via a CSG and NCSG representative and in accordance with the NCPH?s agreed procedures) on or around 29 April. In light of the need to notify the GNSO Chair of the result (as under the GNSO Operating Procedures Keith has the responsibility of notifying the Empowered Community Administration), I would like to ask if it will be possible for the NCPH to complete its vote on a nominee for Board seat 14 by Monday 20 April, to allow Keith time to inform the GNSO Council (as has been customary) and to formally notify the Empowered Community Administration. ? I and the whole GNSO support team are sincerely sorry for our previous guidance to you that had mistakenly set 21 May as the final date. Please accept our heartfelt apologies for this rare error as well as for the inconvenience that we know our mistake must cause you and your groups. ? In view of the situation, please be assured that the CSG and NCSG support staff are happy to assist you with conducting the vote as efficiently and smoothly as possible, to minimize disruption and inconvenience to you. Please let me know if you have any questions or concerns with either the timing or mechanism for the upcoming vote and, once again, I am so very sorry for the trouble. ? Thank you all very much for your kind understanding. ? Best regards, Mary ? ? _______________________________________________ NCSG-EC mailing list NCSG-EC at lists.ncsg.is [mailto:NCSG-EC at lists.ncsg.is] https://lists.ncsg.is/mailman/listinfo/ncsg-ec [https://lists.ncsg.is/mailman/listinfo/ncsg-ec] _______________________________________________ NCSG-EC mailing list NCSG-EC at lists.ncsg.is [mailto:NCSG-EC at lists.ncsg.is] https://lists.ncsg.is/mailman/listinfo/ncsg-ec [https://lists.ncsg.is/mailman/listinfo/ncsg-ec] _______________________________________________ NCSG-EC mailing list NCSG-EC at lists.ncsg.is [mailto:NCSG-EC at lists.ncsg.is] https://lists.ncsg.is/mailman/listinfo/ncsg-ec [https://lists.ncsg.is/mailman/listinfo/ncsg-ec] _______________________________________________ NCSG-PC mailing list NCSG-PC at lists.ncsg.is [mailto:NCSG-PC at lists.ncsg.is] https://lists.ncsg.is/mailman/listinfo/ncsg-pc [https://lists.ncsg.is/mailman/listinfo/ncsg-pc] -------------- next part -------------- An HTML attachment was scrubbed... URL: From rafik.dammak at gmail.com Tue Apr 14 17:07:46 2020 From: rafik.dammak at gmail.com (Rafik Dammak) Date: Tue, 14 Apr 2020 23:07:46 +0900 Subject: [NCSG-PC] [NCSG-EC] Fwd: PLEASE READ: NCPH election for Board seat 14 In-Reply-To: References: <57A94745-69DE-4628-8168-8F15F1C7D467@icann.org> <50546364-b2fd-bd3d-77a3-f6613a7c33e9@mail.utoronto.ca> <6539E322-F58B-410A-B3D4-A05C6C868113@ipjustice.org> <83d286ea-18e3-760e-548d-b3eb897df46e@mail.utoronto.ca> Message-ID: Hi James, thanks :) I believe it should be Stephanie as NCSG chair and already dealt with Dean from CSG. we just need to make it formal regarding the vote: voting yes for Mathew Shears for seat #14. details about election are being flush out either a vote through phone call or through tally ballot. NCSG chair as representative will vote on NCSG behalf. Also Carlton as NCA was reached out and he confirmed his support for Matt. Best, Rafik Le lun. 13 avr. 2020 ? 22:40, lists at icann.guru a ?crit : > Hah ok, well in that case I propose you vote for Matt on our behalf =) > > *---* > *James Gannon* > > On 13/04/2020 14:30:55, Rafik Dammak wrote: > Hi James, > thanks, > short answer, not necessarily :) > > Best, > Rafik > > > Le lun. 13 avr. 2020 ? 17:22, lists at icann.guru a > ?crit : > >> I assume that you as the PC Chair will vote on our behalf? >> >> *---* >> *James Gannon* >> >> On 13/04/2020 09:20:26, Rafik Dammak wrote: >> Hi all, >> >> please let me know if there is any comment or question. >> we should appoint who will vote on behalf of NCSG. >> >> Best, >> >> Rafik >> >> Le jeu. 9 avr. 2020 ? 19:03, Rafik Dammak a >> ?crit : >> >>> Addding the correct pc list address >>> >>> On Thu, Apr 9, 2020, 13:58 Rafik Dammak wrote: >>> >>>> Thanks Stephanie for sharing the info >>>> as first action, I put this as an item for update to our membership in >>>> next week policy call, then follow-up in list to ensure that information is >>>> shared broadly. >>>> with regard to the vote, we can coordinate with all representatives >>>> about the support and appoint who will cast the vote on behalf of NCSG. I >>>> think the vote by 20th April is doable. >>>> >>>> Best, >>>> >>>> Rafik >>>> >>>> Le jeu. 9 avr. 2020 ? 06:31, Stephanie E Perrin via NCSG-EC < >>>> ncsg-ec at lists.ncsg.is> a ?crit : >>>> >>>>> In which case, I am happy to step back and permit the PC to organize >>>>> this. I have reached out to Carlton Samuels, as his collaboration on this >>>>> is required. I have not heard back from him, as yet. Over to you, Rafik. >>>>> >>>>> Stephanie >>>>> On 2020-04-08 5:22 p.m., Robin Gross wrote: >>>>> >>>>> Hi all, >>>>> >>>>> I?ve add the NCSG-PC onto this thread since it is the PC who will vote >>>>> and select our board nominee (pursuant to NCSG Charter). >>>>> >>>>> Thanks, >>>>> Robin >>>>> >>>>> On Apr 8, 2020, at 2:20 PM, Stephanie E Perrin via NCSG-EC < >>>>> ncsg-ec at lists.ncsg.is> wrote: >>>>> >>>>> I need to consult you guys, then we (csg and ncsg) need to set up an >>>>> election, where we pick someone to vote for us, and if we get two votes for >>>>> Matthew (ie each side votes for him) we tell staff and Council he is our >>>>> nominee. It seems a bit clumsy but since we have had a meltdown in the >>>>> past, we needed procedures.... >>>>> >>>>> I presume staff will set up that election for us, will ask Carlos >>>>> Reyes who is now in charge of our policy support, not Mary Wong. >>>>> >>>>> cheers Steph >>>>> >>>>> PS Dean Marks is doing the same thing with the CSG guys. >>>>> >>>>> >>>>> On 2020-04-08 5:16 p.m., Raphael Beauregard-Lacroix wrote: >>>>> >>>>> Sure, I'm just not sure what needs to be done! >>>>> >>>>> On Wed, Apr 8, 2020 at 1:04 PM Stephanie E Perrin via NCSG-EC < >>>>> ncsg-ec at lists.ncsg.is> wrote: >>>>> >>>>>> Hi folks, we need to organize on the election of Matthew Shears for >>>>>> Board seat 14. I have reached out to Carlton Samuels, to tick the box of >>>>>> consulting with our nomcom appointee (no response so far) and I have been >>>>>> chatting with Dean Marks from the CSG, who is keen to cooperate. We are >>>>>> trying to meet this new deadline of April 20, can we organize to hold our >>>>>> election next week in time to offer our name? The CSG thinks they can. >>>>>> >>>>>> Sorry to push but we have to get this done faster now due to ICANN's >>>>>> revised timelines....since we are agreed on the candidate, it is just >>>>>> paperwork.... >>>>>> >>>>>> cheers Steph >>>>>> >>>>>> >>>>>> -------- Forwarded Message -------- >>>>>> Subject: PLEASE READ: NCPH election for Board seat 14 >>>>>> Date: Tue, 7 Apr 2020 20:17:14 +0000 >>>>>> From: Mary Wong >>>>>> To: Dean Marks , Stephanie E >>>>>> Perrin >>>>>> , Bruna Martins dos Santos >>>>>> , Joan Kerr >>>>>> , Rafik Dammak >>>>>> , Selli, Claudia >>>>>> , >>>>>> csg-excomm at icann.org , >>>>>> Barbara Wanner >>>>>> CC: Chantelle Doerksen >>>>>> , Maryam Bakoshi >>>>>> , Andrea >>>>>> Glandon , >>>>>> Carlos Reyes >>>>>> >>>>>> Dear CSG and NCSG leaders, >>>>>> >>>>>> >>>>>> I would like to apologize for bringing up this topic at this late >>>>>> stage, and at a time when I know that many community members are focusing >>>>>> on important personal and family matters during the current COVID-19 >>>>>> situation. Please understand that we as staff would not have raised this >>>>>> were it not a Bylaws-related matter. >>>>>> >>>>>> >>>>>> Here is the issue: under the ICANN Bylaws, formal notification of a >>>>>> nominee for either Board seat 13 or 14 must be provided to the Empowered >>>>>> Community Administration at least six (6) months prior to the commencement >>>>>> of that potential Director?s term. As the 2020 Annual General Meeting is >>>>>> due to conclude on 22 October 2020 (which we realize is somewhat earlier >>>>>> than previous AGMs), this means that *the Empowered Community >>>>>> Administration must receive the Non-Contracted Parties House (NCPH) >>>>>> nomination of a Director to fill Board seat 14 by 22 April 2020* >>>>>> (and not May as we had advised you previously). >>>>>> >>>>>> >>>>>> I understand that the NCPH?s current plan is to hold the formal vote >>>>>> (via a CSG and NCSG representative and in accordance with the NCPH?s agreed >>>>>> procedures) on or around 29 April. In light of the need to notify the GNSO >>>>>> Chair of the result (as under the GNSO Operating Procedures Keith has the >>>>>> responsibility of notifying the Empowered Community Administration), I >>>>>> would like to ask *if it will be possible for the NCPH to complete >>>>>> its vote on a nominee for Board seat 14 by Monday 20 April*, to >>>>>> allow Keith time to inform the GNSO Council (as has been customary) and to >>>>>> formally notify the Empowered Community Administration. >>>>>> >>>>>> >>>>>> I and the whole GNSO support team are sincerely sorry for our >>>>>> previous guidance to you that had mistakenly set 21 May as the final date. >>>>>> Please accept our heartfelt apologies for this rare error as well as for >>>>>> the inconvenience that we know our mistake must cause you and your groups. >>>>>> >>>>>> >>>>>> In view of the situation, please be assured that the CSG and NCSG >>>>>> support staff are happy to assist you with conducting the vote as >>>>>> efficiently and smoothly as possible, to minimize disruption and >>>>>> inconvenience to you. Please let me know if you have any questions or >>>>>> concerns with either the timing or mechanism for the upcoming vote and, >>>>>> once again, I am so very sorry for the trouble. >>>>>> >>>>>> >>>>>> Thank you all very much for your kind understanding. >>>>>> >>>>>> >>>>>> Best regards, >>>>>> >>>>>> Mary >>>>>> >>>>>> >>>>>> _______________________________________________ >>>>>> NCSG-EC mailing list >>>>>> NCSG-EC at lists.ncsg.is >>>>>> https://lists.ncsg.is/mailman/listinfo/ncsg-ec >>>>>> >>>>> _______________________________________________ >>>>> NCSG-EC mailing list >>>>> NCSG-EC at lists.ncsg.is >>>>> https://lists.ncsg.is/mailman/listinfo/ncsg-ec >>>>> >>>>> >>>>> _______________________________________________ >>>>> NCSG-EC mailing list >>>>> NCSG-EC at lists.ncsg.is >>>>> https://lists.ncsg.is/mailman/listinfo/ncsg-ec >>>>> >>>> _______________________________________________ NCSG-PC mailing list >> NCSG-PC at lists.ncsg.is https://lists.ncsg.is/mailman/listinfo/ncsg-pc >> >> -------------- next part -------------- An HTML attachment was scrubbed... URL: From rafik.dammak at gmail.com Tue Apr 14 17:08:37 2020 From: rafik.dammak at gmail.com (Rafik Dammak) Date: Tue, 14 Apr 2020 23:08:37 +0900 Subject: [NCSG-PC] PC Chair election / Vice-chairs appointments In-Reply-To: References: Message-ID: Hi all, a reminder regarding PC chair process and vice-chairs appointments. if there is any objection or comment. Best, Rafik Le jeu. 9 avr. 2020 ? 09:11, Rafik Dammak a ?crit : > Hi all, > > following-up (with delay) on one the agreed action items which is the PC > chair election and vice-chairs appointment, I am proposing here a draft > process and timeline. it might sound formal compared to what we discussed > previously but I am using this a draft for building fully fledged process > in future: > > 1- Nomination period: from 17th to 24th April > > Nomination and self-nomination are both permitted from and within PC > members (NCSG councillors, NCSG Chair, representatives from NCUC and NPOC > to PC), for one year term for PC chair position. > The nominee should accept the nomination and send a short SOI by the 24th > April. > > 2- Election : from 27th April to 1st May > > all PC members should vote. the GNSO support staff will act as the > election officer. The options in the ballot should be the candidates who > confirmed by the deadline and NOTA > > 3- Result: should be available by 2nd May > > the candidate who get 2/3 vote of the NCSG?PC membership will be > declared winner. > > 4- Vice-chairs appointments: > > After PC chair confirmation, a call for interest should be made to have up > to 2 vice-chairs. The appointment of the volunteers will be confirmed if > there is no objection within PC. > > > this is just draft process and should be fleshed out to documented for > future. I didn't outline all cases regarding the election for example. > After that, the next step will be to work on job description for those > positions. > > Please let me know your thoughts/comments on what is proposed. > > Best, > > Rafik > > > ---------- Forwarded message --------- > De : Rafik Dammak > Date: lun. 2 mars 2020 ? 09:35 > Subject: NCSG Policy Committee meeting follow-up > To: ncsg-pc > > > Hi all, > > as you know we had last week our PC meeting to discuss several items > regarding election, improvements etc. We got already some action item to > follow-up > > 1- PC chair Election: there was agreement to go with the idea of having > chair and 2 vice-chairs. The point was also to have proper open process > (that can be documented for future). so the action here is to agree on > timeline and process (nomination, vote). it shouldn't be complicated. I > believe we can get this done in this month e.g. 1 week for nomination and 1 > week for voting. > 2- Having a regular PC call, hopefully monthly call and coordinating more > with our NCSG reps to council. The action would be to agree on regular > day/time. I think that can be 2 weeks after NCSG Policy. > 3- Regarding documentation and development of workflow, I believe that can > be done with reworking again on PC operating procedure and documenting > previous activities. I am sharing here the PC operating procedures draft > being worked on before > https://docs.google.com/document/d/1G_M4wBGVEyXm30m79olplfF0RNkJnDwaVBBeldDfO8U/edit . > For anything missing, we can start first to identify that and have > volunteers to draft it. For Chair job description, I can use what I > presented and develop a draft. > 4- Sharing here the slides I presented in last call: > https://docs.google.com/presentation/d/1SnpMYmb6lTw1FqO6tvSqCdpgL-QMg1DJXIJGrx8vB6A/edit#slide=id.p > 5- for NCSG Policy call improvements, we will have the NCSG Policy call in > coming days and I will try to make some adjustments to extent of possible. > It might be shorter than usual as we will have NCSG meeting next week. From > April NCSG Policy call, we can start identifying other topics we would like > to cover other than council meeting and usual policy updates. > > One activity we will need to do soon and follow-up is to work about > prioritization. GNSO Council will discuss the GNSO future work soon and we > need to be ready and align our work around that. That also aligns with the > discussion we had about prioritizing our work and it starts with > identifying what is in the pipeline. > > let me know if I missed anything. > > Best. > > Rafik > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From oreoluwa at wtec.org.ng Wed Apr 15 21:38:33 2020 From: oreoluwa at wtec.org.ng (oreoluwa) Date: Wed, 15 Apr 2020 19:38:33 +0100 Subject: [NCSG-PC] PC Chair election / Vice-chairs appointments In-Reply-To: Message-ID: Good day all,Thanks for sharing this, Rafik. This timeline and process looks fine to me.Just to clarify, these appointments would start at the AGM in October?Kind regards,?Oreoluwa?--Oreoluwa Lesi Executive Director, Women's Technology Empowerment Centre (W.TEC)www.wtec.org.ng | @wteconlineSent from my Samsung Galaxy smartphone. -------- Original message --------From: Rafik Dammak Date: 14/04/2020 15:09 (GMT+01:00) To: ncsg-pc Subject: Re: [NCSG-PC] PC Chair election / Vice-chairs appointments Hi all,a reminder regarding PC chair process and vice-chairs appointments.if there is any objection or comment.Best,RafikLe?jeu. 9 avr. 2020 ??09:11, Rafik Dammak a ?crit?:Hi all,following-up (with delay) on one the agreed action items which is the PC chair election and vice-chairs appointment, I am proposing here a draft process and timeline. it might sound formal compared to what we discussed previously but I am using this a draft for building fully fledged?process in future:1- Nomination period: from 17th to 24th AprilNomination and self-nomination are both permitted from and within PC members (NCSG councillors, NCSG Chair, representatives from NCUC and NPOC to PC), for one year term for PC chair position.The nominee should accept the nomination and send a short SOI by the 24th April.2- Election : from 27th April to 1st Mayall PC members should vote. the GNSO support staff will act as the election officer. The options in the ballot should be the candidates who confirmed by the deadline and NOTA?3- Result: should be available by 2nd Maythe candidate who get??2/3 vote of the NCSG?PC membership will be declared winner.4- Vice-chairs appointments:After PC chair confirmation, a call for interest should be made to have up to 2 vice-chairs. The appointment of the volunteers will be confirmed if there is no objection within PC.this is just draft process and should be fleshed out to documented for future. I didn't outline all cases regarding the election for example. After that, the next step will be to work on job description for those positions.Please let me know your thoughts/comments on what is proposed.Best,Rafik---------- Forwarded message ---------De?: Rafik Dammak Date: lun. 2 mars 2020 ??09:35Subject: NCSG Policy Committee meeting follow-upTo: ncsg-pc Hi all,as you know we had last week our PC meeting to discuss several items regarding election, improvements etc. We got already some action item to follow-up1- PC chair Election: there was agreement to go with?the idea of having chair and 2 vice-chairs. The point was also to have proper open process (that can be documented for future). so the action here is? to agree on timeline and process (nomination, vote). it shouldn't be complicated. I believe?we can get this done in this month e.g. 1 week for nomination and 1 week for voting.2- Having a regular PC call, hopefully monthly call and coordinating more with our NCSG reps to council. The action would be to agree on regular day/time. I think that can be 2 weeks after NCSG Policy.3- Regarding documentation and development of workflow, I believe that can be done with reworking again on PC operating?procedure?and documenting previous activities. I am sharing here the PC operating?procedures?draft being worked on before?https://docs.google.com/document/d/1G_M4wBGVEyXm30m79olplfF0RNkJnDwaVBBeldDfO8U/edit?. For anything missing, we can start first to identify that and have volunteers to draft it. For Chair job description, I can use what I presented and develop a draft.4- Sharing here the slides I presented in last call:?https://docs.google.com/presentation/d/1SnpMYmb6lTw1FqO6tvSqCdpgL-QMg1DJXIJGrx8vB6A/edit#slide=id.p5- for NCSG Policy call improvements, we will have the NCSG Policy call in coming days and I will try to make some adjustments to extent of possible. It might be shorter than usual as we will have NCSG meeting next week. From April NCSG Policy call, we can start identifying other topics we would like to cover other than council meeting and usual policy updates.One activity we will need to do soon and follow-up is to work about prioritization. GNSO Council will discuss the GNSO future work soon and we need to be ready and align our work around that. That also aligns with the discussion we had about prioritizing our work and it starts with identifying what is in the pipeline.let me know if I missed anything.Best.Rafik -------------- next part -------------- An HTML attachment was scrubbed... URL: From rafik.dammak at gmail.com Thu Apr 16 02:18:21 2020 From: rafik.dammak at gmail.com (Rafik Dammak) Date: Thu, 16 Apr 2020 08:18:21 +0900 Subject: [NCSG-PC] PC Chair election / Vice-chairs appointments In-Reply-To: <5e9755ad.1c69fb81.31009.5bcaSMTPIN_ADDED_MISSING@mx.google.com> References: <5e9755ad.1c69fb81.31009.5bcaSMTPIN_ADDED_MISSING@mx.google.com> Message-ID: Hi Oreoluwa, thanks for the question. the term will start right away after the election. we are quite late :) Best, Rafik Le jeu. 16 avr. 2020 ? 03:42, oreoluwa a ?crit : > Good day all, > > Thanks for sharing this, Rafik. This timeline and process looks fine to me. > > Just to clarify, these appointments would start at the AGM in October? > > Kind regards, > Oreoluwa > > > > -- > Oreoluwa Lesi > Executive Director, Women's Technology Empowerment Centre (W.TEC) > www.wtec.org.ng | @wteconline > > > Sent from my Samsung Galaxy smartphone. > > > -------- Original message -------- > From: Rafik Dammak > Date: 14/04/2020 15:09 (GMT+01:00) > To: ncsg-pc > Subject: Re: [NCSG-PC] PC Chair election / Vice-chairs appointments > > Hi all, > > a reminder regarding PC chair process and vice-chairs appointments. > if there is any objection or comment. > > Best, > > Rafik > Le jeu. 9 avr. 2020 ? 09:11, Rafik Dammak a > ?crit : > >> Hi all, >> >> following-up (with delay) on one the agreed action items which is the PC >> chair election and vice-chairs appointment, I am proposing here a draft >> process and timeline. it might sound formal compared to what we discussed >> previously but I am using this a draft for building fully fledged process >> in future: >> >> 1- Nomination period: from 17th to 24th April >> >> Nomination and self-nomination are both permitted from and within PC >> members (NCSG councillors, NCSG Chair, representatives from NCUC and NPOC >> to PC), for one year term for PC chair position. >> The nominee should accept the nomination and send a short SOI by the 24th >> April. >> >> 2- Election : from 27th April to 1st May >> >> all PC members should vote. the GNSO support staff will act as the >> election officer. The options in the ballot should be the candidates who >> confirmed by the deadline and NOTA >> >> 3- Result: should be available by 2nd May >> >> the candidate who get 2/3 vote of the NCSG?PC membership will be >> declared winner. >> >> 4- Vice-chairs appointments: >> >> After PC chair confirmation, a call for interest should be made to have >> up to 2 vice-chairs. The appointment of the volunteers will be confirmed if >> there is no objection within PC. >> >> >> this is just draft process and should be fleshed out to documented for >> future. I didn't outline all cases regarding the election for example. >> After that, the next step will be to work on job description for those >> positions. >> >> Please let me know your thoughts/comments on what is proposed. >> >> Best, >> >> Rafik >> >> >> ---------- Forwarded message --------- >> De : Rafik Dammak >> Date: lun. 2 mars 2020 ? 09:35 >> Subject: NCSG Policy Committee meeting follow-up >> To: ncsg-pc >> >> >> Hi all, >> >> as you know we had last week our PC meeting to discuss several items >> regarding election, improvements etc. We got already some action item to >> follow-up >> >> 1- PC chair Election: there was agreement to go with the idea of having >> chair and 2 vice-chairs. The point was also to have proper open process >> (that can be documented for future). so the action here is to agree on >> timeline and process (nomination, vote). it shouldn't be complicated. I >> believe we can get this done in this month e.g. 1 week for nomination and 1 >> week for voting. >> 2- Having a regular PC call, hopefully monthly call and coordinating more >> with our NCSG reps to council. The action would be to agree on regular >> day/time. I think that can be 2 weeks after NCSG Policy. >> 3- Regarding documentation and development of workflow, I believe that >> can be done with reworking again on PC operating procedure and documenting >> previous activities. I am sharing here the PC operating procedures draft >> being worked on before >> https://docs.google.com/document/d/1G_M4wBGVEyXm30m79olplfF0RNkJnDwaVBBeldDfO8U/edit . >> For anything missing, we can start first to identify that and have >> volunteers to draft it. For Chair job description, I can use what I >> presented and develop a draft. >> 4- Sharing here the slides I presented in last call: >> https://docs.google.com/presentation/d/1SnpMYmb6lTw1FqO6tvSqCdpgL-QMg1DJXIJGrx8vB6A/edit#slide=id.p >> 5- for NCSG Policy call improvements, we will have the NCSG Policy call >> in coming days and I will try to make some adjustments to extent of >> possible. It might be shorter than usual as we will have NCSG meeting next >> week. From April NCSG Policy call, we can start identifying other topics we >> would like to cover other than council meeting and usual policy updates. >> >> One activity we will need to do soon and follow-up is to work about >> prioritization. GNSO Council will discuss the GNSO future work soon and we >> need to be ready and align our work around that. That also aligns with the >> discussion we had about prioritizing our work and it starts with >> identifying what is in the pipeline. >> >> let me know if I missed anything. >> >> Best. >> >> Rafik >> >> -------------- next part -------------- An HTML attachment was scrubbed... URL: From rafik.dammak at gmail.com Thu Apr 16 03:22:30 2020 From: rafik.dammak at gmail.com (Rafik Dammak) Date: Thu, 16 Apr 2020 09:22:30 +0900 Subject: [NCSG-PC] Fwd: [NCSG-Discuss] [Consultation] PIR Transaction and Proposed Public Interest Commitments Update In-Reply-To: References: <1134142044748.1122025845763.1521253088.0.711100JL.2002@scheduler.constantcontact.com> <11CE170D-5897-424C-BE73-090F1016BE03@icann.org> <20200414145555.Horde.ZryOSs7ES2rEDNmraokEKm_@a2plcpnl0836.prod.iad2.secureserver.net> <20200415061845.Horde.av7LkyXqOGutJdfH2T-eJsd@a2plcpnl0836.prod.iad2.secureserver.net> Message-ID: hi all, this requires an urgent and swift response from PC. we have a thread regarding this short consultation from ICANN regarding .org sale and the proposed PICs. based on comments shared in the list, Bruna quickly drafted the statement below. please review ! Best, Rafik ---------- Forwarded message --------- De : Bruna Martins dos Santos Date: jeu. 16 avr. 2020 ? 06:27 Subject: Re: [NCSG-Discuss] [Consultation] PIR Transaction and Proposed Public Interest Commitments Update To: Dear all, Putting together some of the comments on this list, this is what the NCSG "comment" looks like: Pad: https://pad.codingrights.org/p/NCSGCommentPIR ------- *NCSG Statement on the "PIR Transaction and Proposed Public Interest Commitments Update"* Back in november 2011, the Noncommercial Stakeholders Group issued a letter to the ICANN Board advocating for Ethos Capital to uphold its previously acquired obligations with regards to noncommercial registrants. The letter also pointed out that it was ICANN's duty to to enter into negotiations with Ethos Capital to ensure that its operation of the ORG domain conforms to criteria upon which the original award of ORG was contingent (related to noncommercial registrants). *Lack of a Freedom of Expression related provision on the PIC* Due to concerns regarding eventual restrictions to rights such as Freedom of Expression, NCSG asked that the PIC text included both a process-oriented commitment to allow the Org Stewardship Council to veto ?modifications? of RO?s policies pertaining to free expression and a positive commitment to ensuring rights such as freedom of expression in the .Org domain. Despite stating this point previously in statements and to the PIR Leadership team, the lack of mention to this request on the modified PIC makes it harder for us to fully support the revised document. *Extended registration terms for .org registrants * With regards to the possible extension of registration terms for .org registrants this was also a topic in which NCSG pointed out the need for a stronger PIR commitment. Despite understanding the eventual policy changes entailed by the proposed change, we would like to, once again, state the need for a sronger PIR involvement in creating such a change. *Org Stewardship Council * We would like to also offer our concerns with regards to the proposed stewardship council. NCSG understands that the OSC must be able to present a counter point or even oppose to policy implementations on behalf of PIR. Foreseeing the possible issues with the implementation of policies such as the PIR Anti-Abuse Policy that allows PIR ?to comply with any applicable laws, government rules or requirements, requests of law enforcement, or any dispute resolutio process" we would like to note the importance of an independent OSC able to express powers to examine difficult issues of jurisdiction and protect free expression for organizations and individuals engaged in political debates. Another possible issue listed on the same policy is the discussion of ?trusted notifiers? as a type of fast-track method of reporting and taking down domain names with disliked content. In order for this provision to happen in an adequate manner we must ensure that the OSC composition also have experts in topics such as Freedom of Expression, Free Speech and Human rights. These experts must have deep substantive legal and policy background and ability to independently research and expertly comment on substantive and procedural issues brought before them by Ethos/PIR. *OSC Representation and NCSG participation* NCSG also informed the PIR leadership the need for more independence on the proposed ORG Stewardship Council (OSC). Despite being a point that was mentioned on the new PICs and PIR statements, we believe the proposed process could still be improved. Specifically, they say ?The PIR Board will not appoint the first five members of the .ORG Stewardship Council. To ensure independence, Ethos will engage an internationally-recognized executive search firm to oversee and manage a process for identifying candidates to be the inaugural members. The search firm will solicit applications from a variety of .ORG Stakeholders, including ICANN?s Non-Commercial Stakeholder Group (NCSG) and At-Large Advisory Committee (ALAC) and provide its proposed nominations to a Selection Committee established by the PIR Board.?. When it comes to the ORG Stewardship Council representatives, we would like to state the following: (a) From what it seems, even with the new proposed selection process, PIR will still be responsbible for selecting all the OSC members. Additionally, despite the mention to NCSG on the document, there are no guarantees that the selection committee nor PIR will ensure NCSGs participation on the OSC. We also must note that ALAC contains, and to some extent is more representative of, commercial users as well as noncommercial users and has no historical connection to the ORG domain; (b) PIR and Ethos Capital should ensure that the OSC members include include multiple and well-known experts in free speech and freedom of expression, human rights, copyright/trademark/fair use. Also, as pointed above, it is of utter importance that the selected appointees hold the same compromise with ensuring that the registry keeps its allignment with the Noncommercial registrants. Le mer. 15 avr. 2020 ? 17:08, Peter Micek a ?crit : > Hi all, > > I fully support a comment by NCSG. Access Now are just finalizing ours, > I'll paste a draft below. I support holding them to account for their > promise of clarity on the selection process, but as you can see, I feel > that committee is more like a deck chair arrangement than hand on the > ship's tiller. > > Best, > Peter > > > > > > > *In Access Now?s last letter > to ICANN, we > outlined some of the many reasons why the proposed Public Interest > Commitments (PICs) would in no way be sufficient to hold PIR ? and Ethos > Capital as its controlling investor ? accountable to the .ORG community or > to ensure the needs and interests of those who rely on .ORG are protected. > The several adjustments Ethos has made to its proposal since we wrote that > letter are not significant and do not change our position.ICANN has an > important opportunity to restore the .ORG community?s confidence, and to do > its part in protecting online civic space ? which is already under attack > all around the world. It can do that by taking the following steps:Extend > the public comment period. If ICANN is serious about getting meaningful > input from the community on the current proposal, a seven-day comment > period isn?t enough. At a minimum ICANN needs to allow its standard 30-day > window for comments, especially considering the additional strain civil > society around the world is burdening under the ongoing COVID-19 crisis. > This falls in line with guidance > > from the UN special rapporteur on the freedom of assembly, that > ?multilateral institutions should take steps to ensure civil society > organizations can continue to participate in all policy decisions, > including those related to the Covid-19 response, especially in the case of > public-private partnerships.? That ICANN is multi-stakeholder, not > multilateral (like the UN), only adds to its responsibility to meaningfully > consult civil society.Negotiate an extension with PIR and Ethos.ICANN is > rushing to get in public comments in just seven days, with only two working > days to process the results ahead of their April 20th deadline for deciding > .ORG?s future. Further, ICANN is still waiting for responses > > from Ethos to many very important questions (covering issues like PIR?s > financial solvency, avenues for community input going forward, and who > would actually be in control of PIR across the several holding companies > involved in the transaction). Getting the information they need both from > Ethos and the community is essential to the long-term sustainability of > .ORG, and ICANN should insist on more time to make this decision.Withhold > consent to the transfer of control of .ORG.Even without extended comment > periods and additional information, though, ICANN already has all it needs > to reject this deal. Simply put, this is an underhanded and dangerous deal > that puts all of us at risk, and ICANN should stop it. After several rounds > of empty concessions from Ethos, and their continued failure to produce > essential information about how the deal is structured, it is very clear > that there is no path to redeeming this sale.Lead a community consultation > on the future of .ORG.ICANN should provide an inclusive, substantive, > community-driven venue for discussing a viable path forward for .ORG. If > ISOC no longer has an interest in being a steward for the domain, it is > essential that we can collectively identify a new solution that ? first and > foremost ? meets the needs of the .ORG community, now and in the future.* > > On Wed, Apr 15, 2020 at 9:20 AM wrote: > >> Raphael, >> Tx for your comments. You'll note my comments/points reference both >> free speech (law where .ORG has been based for 34 years, and of its >> proposed upcoming owners) and free expression (referencing Article 19 >> of the UN Declaration of Human Rights). It is the language of both >> sets of laws, and expertise in both, that I advise in points 1 and 3 >> below. >> >> I can't imagine how that would be controversial -- there are people >> who are experts on protecting free expression around the world -- and >> if this controversial sale goes through, we will need them here. It's >> hard to hold your ground in complex circumstances (against private >> corporate attorneys) if you are not an expert -- we want people who >> know the precedent and the laws and protections around the world. Glad >> you like the second proposition! >> >> In all events, our NCSG voice needs to be heard here. Bruna offered >> to prepare a quick comment -- I think we we should move forward. Time >> is of the essence! >> >> Best, Kathy >> >> Quoting Raphael Beauregard-Lacroix : >> >> > I think we have some materials for a comment, but are lacking a few more >> > days to put things together. Not only is that 7 days too short, but >> > blogpost comments are not quite appropriate either to say the least. >> Given >> > the unanimity of those who commented on the blogpost, we can hope they >> will >> > change their mind (and we can individually join such request for a >> standard >> > public comment period. >> > >> > As for the substance of our comment, I find myself closer to Milton's >> > propositions. Kathy, I think your first and third proposition are >> difficult >> > to work out in practice without enunciating what the base line is >> supposed >> > to be - I understand it would be the US (i.e. assuming jurisdiction, PIR >> > should not comply with requests which could not validly be made under US >> > law by a US entity) I have difficulties with that position as it puts US >> > free speech law on a pedestal and means committee members must be >> immersed >> > in the US understanding of free speech. Globally, with its extremely >> high >> > thresholds before the government can directly regulate speech, the US >> rides >> > alone. >> > >> > But the problem is not solved by choosing any other law, or some sort of >> > generic transnational mix of "free speech best practices" as a strict >> set >> > of legal rules. I get your worry that PIR will comply with any law >> > enforcement order it receives, bogus and legitimate alike, for business >> > reasons. I guess the domain name industry is not in a position to make >> the >> > very brazen move to apply US speech regulation threholds to all their >> > customers... Nor even to do so with a slightly watered down best >> practices. >> > While that's not new, I still think we can ask for PIR to do better than >> > others. But the choice they would be facing is jeopardizing their >> business >> > (or their finances, eventually) in the name of values. >> > >> > Hence the language that Milton suggests, a written commitment to a more >> > general value and ensuring that members of the committee come from >> diverse >> > civil society background, is, I find, more likely to find a broader >> appeal >> > among our community and the ICANN/dot org community in general. Public >> > opinion and community pressure (stirred by a vigilant council) might be >> a >> > better safeguard against opportunistic or otherwise undesirable >> behavior by >> > PIR with regards to LEA requests than some sort of inbedded court of >> review >> > with an ad-hoc set of very binding but still very vague rules. >> > >> > Your second proposition seems fine as is! We can legitimately request >> that >> > trusted notifiers be actually neutral and not a IP >> > rightsholders association... >> > >> > have a nice evening, >> > >> > On Tue, Apr 14, 2020 at 5:57 PM wrote: >> > >> >> To Milton's proposed comments below, I offer key substantive changes >> >> -- otherwise I fear the Stewardship Council will be completely >> >> bypassed by Ethos and PIR. >> >> >> >> Specifically: >> >> >> >> Powers of the Stewardship Council must allow it to strongly, clearly >> >> and with authority support (or oppose) Ethos/PIR LLC's implementation >> >> of PIR's Anti-Abuse Policy. >> >> >> >> Background: In October 2019, the then-new PIR President Jon Nevett >> >> announced a PIR Anti-Abuse Policy that allows PIR ?to comply with any >> >> applicable laws, government rules or requirements, requests of law >> >> enforcement, or any dispute resolution process.? >> >> https://thenew.org/doing-our-part-for-a-safer-stronger-dns/ The >> >> Stewardship Council -- to protect free speech and free expression in >> >> .ORG -- *must* have the ability to oversee (and veto) Ethos/PIR's >> >> interpretation and implementation of the PIR Anti-Abuse Policy. >> >> Otherwise, it cannot protect .ORG registrants against censorship. >> >> >> >> Concern 1: The Anti-Abuse Policy commits PIR to responses to >> >> "requests of law enforcement" without stating whether the law >> >> enforcement requests must come from a law enforcement agency with >> >> jurisdiction over the registry, registrar or registrant. Is the >> >> request for takedown of speech even legal in the country in which the >> >> speech originated? Is the speech perhaps purposely and intentionally >> >> directed to expose corruption or malfeasance of a national government >> >> or official who has stepped beyond their authority and law? >> >> >> >> **Accordingly, the Stewardship Council must have express powers to >> >> examine difficult issues of jurisdiction and protect free expression >> >> for organizations and individuals engaged in political debates. >> >> >> >> Concern 2: The PIR Anti-Abuse policy discusses ?trusted notifiers? as >> >> a type of fast-track method of reporting and taking down domain names >> >> with disliked content. Recent PIR President Jon Nevett, when he was >> >> General Counsel/VP of Donuts, paired up with controversial ?trusted >> >> notifier? the Motion Picture Association (MPAA), >> >> >> >> >> https://www.multichannel.com/news/mpaa-donuts-team-takedown-best-practice-402440 >> >> The MPAA is not known for its neutrality or fairness in its >> accusations, >> >> see e.g., >> >> >> https://www.brainz.org/14-most-ridiculous-lawsuits-filed-riaa-and-mpaa/ >> >> >> >> ** Accordingly, the Stewardship Council must be able to review all >> >> ?trusted notifiers? and veto those that are not genuinely fair and >> >> neutral and will not genuinely protect free speech and free >> >> expression, including legitimate critique and legal fair use. >> >> >> >> Problem 3: Nice people on the Stewardship Council without deep >> >> expertise in free speech, free expression, human rights, privacy and >> >> relate laws can be easily captured by Ethos/PIR?s own research and >> >> reasoning. >> >> >> >> ** Accordingly, all Stewardship Councils must include *multiple and >> >> well-known experts in free speech and free expression, human rights, >> >> copyright/trademark/fair use.* These experts must have deep >> >> substantive legal and policy background and ability to independently >> >> research and expertly comment on substantive and procedural issues >> >> brought before them by Ethos/PIR. >> >> >> >> Best, Kathy >> >> >> >> Quoting "Mueller, Milton L" : >> >> >> >> > Rafik: >> >> > Thanks for your initiative. NCSG must comment on this. We are being >> >> > derelict in our duties to represent noncommercial users if we don?t. >> >> > >> >> > I may not be up to date about this, but one important issue still >> >> > seems to be unresolved. In its commitment to amend the PIC in a way >> >> > that would satisfy the concerns of noncommercial registrants, PIR >> >> > wrote that ?he search firm and nomination criteria process will be >> >> > announced on March 23, 2020.? Has that been done? If so, I don?t >> >> > know where it is. >> >> > >> >> > Some comments about the modified PIC that could be used as is or >> >> > incorporated into a NCSG comment. >> >> > >> >> > >> >> > 1. We had asked that the PIC text include not just a >> >> > process-oriented commitment to allow the Org Stewardship Council to >> >> > veto ?modifications? of RO?s policies pertaining to free expression, >> >> > but a positive commitment to fostering freedom of expression in the >> >> > .Org domain. The CEO of Org seemed to express a favorable view of >> >> > that request in a public consultation. The modified PIC contains no >> >> > such modification. This is disappointing, and makes it impossible >> >> > for us to fully support the revised PIC. >> >> > >> >> > 2. We had also asked for PIR to express a stronger commitment >> >> > to extending registration terms for org registrants. While we >> >> > understand that extending registration terms requires a policy >> >> > change, we were hoping for a statement that PIR would join in >> >> > efforts to create such a change. The modified PIC contains no such >> >> > commitment. >> >> > >> >> > 3. We informed PIR that the ORG Stewardship Council (OSC) >> >> > needed to be more independent of PIR. The new PICs and PIR >> >> > statements have been partially responsive to that request, but still >> >> > fall short. Specifically, they say ?The PIR Board will not appoint >> >> > the first five members of the .ORG Stewardship Council. To ensure >> >> > independence, Ethos will engage an internationally-recognized >> >> > executive search firm to oversee and manage a process for >> >> > identifying candidates to be the inaugural members. The search firm >> >> > will solicit applications from a variety of .ORG Stakeholders, >> >> > including ICANN?s Non-Commercial Stakeholder Group (NCSG) and >> >> > At-Large Advisory Committee (ALAC) and provide its proposed >> >> > nominations to a Selection Committee established by the PIR Board.? >> >> > Clearly, in this process PIR will still select all the OSC members. >> >> > While the solicitation of applications specifically mentions NCSG, >> >> > there is no guaranteed representation from NCSG on the OSC. We also >> >> > must note that ALAC contains, and to some extent is more >> >> > representative of, commercial users as well as noncommercial users >> >> > and has no historical connection to the ORG domain. >> >> > >> >> > From: NCSG-Discuss On Behalf Of >> Rafik >> >> Dammak >> >> > Sent: Monday, April 13, 2020 7:25 PM >> >> > To: NCSG-DISCUSS at LISTSERV.SYR.EDU >> >> > Subject: Re: [Consultation] PIR Transaction and Proposed Public >> >> > Interest Commitments Update >> >> > >> >> > hi all, >> >> > >> >> > resending this to ask if there is anything we would like to comment >> >> > regarding .org proposed PICs. >> >> > >> >> > Best, >> >> > >> >> > Rafik >> >> > >> >> > Le ven. 10 avr. 2020 ? 08:30, Rafik Dammak >> >> > > a ?crit : >> >> > Hi all, >> >> > >> >> > there is an update related to PIR and ,org sale with regard to >> >> > communication between PIR and ICANN, and the matter of PIC (Public >> >> > Interest Commitments). As ICANN has to make decision within the >> >> > timeline regarding the change on control of PIR , it is asking the >> >> > community to provide feedback regarding the proposed PICs. it won't >> >> > be through usual public comment but either by responding as comment >> >> > to the blog (unusual) or sending letter to the board. >> >> > >> >> > As this topic is of interest to NCSG and it is an opportunity to >> >> > share comments on the PIC, we should draft a letter quickly and send >> >> > it as correspondence to boars. For more information you can check >> >> > the blog post here >> >> > >> >> >> https://www.icann.org/news/blog/pir-transaction-and-proposed-public-interest-commitments-update >> >> or >> >> > below. >> >> > >> >> > Best regards, >> >> > >> >> > Rafik >> >> > >> >> > ---------- Forwarded message --------- >> >> > De : Michelle DeSmyter >> >> > > >> >> > Date: ven. 10 avr. 2020 ? 00:02 >> >> > Subject: [council] FYI: [ICANN Community Leaders] 9 April 2020 >> >> > To: GNSO Council List > >> council at gnso.icann.org>> >> >> > Cc: gnso-secs at icann.org >> >> > > >> >> > >> >> > >> >> > FYI: >> >> > [Image removed by sender.] >> >> > Thursday, 9 April 2020 >> >> > >> >> > ICANN Community Leadership Digest >> >> > >> >> > [Image removed by sender.] >> >> > >> >> > The ICANN org Policy Development Support function publishes this >> >> > twice-weekly digest >> >> > to help ICANN community leaders track requests and follow updates. >> >> > >> >> > Table of Contents >> >> > >> >> > Information Sharing >> >> > ? NEW: PIR Transaction and Proposed Public Interest Commitments >> >> Update >> >> > ? NEW: Addressing Recent Zoom News >> >> > ? ENDS TOMORROW: Your Feedback about this Digest >> >> > ? REMINDER: Call for Expressions of Interest: Standing Panel for >> >> > ICANN?s Independent Review Process >> >> > Public Comment >> >> > ? CLOSES MONDAY: Revised Community Travel Support Guidelines >> >> > ? Proposal for Chinese Script Root Zone Label Generation Rules >> >> > ? Proposal for Bangla Script Root Zone Label Generation Rules >> >> > ? Phase 1 Initial Report of the Review of All Rights Protection >> >> > Mechanisms in All gTLDs Policy Development Process >> >> > ? Addendum to the Initial Report of the Expedited Policy >> >> > Development Process (EPDP) on the Temporary Specification for gTLD >> >> > Registration Data Team ? Phase 2 >> >> > ? Guidelines for Developing Reference Label Generation Rules >> >> > (LGRs) for the Second Level Version 2 >> >> > >> >> > >> >> > >> >> > Information Sharing >> >> > >> >> > NEW: PIR Transaction and Proposed Public Interest Commitments Update >> >> > Executive: G?ran Marby, ICANN President and CEO >> >> > >> >> > Since Public Interest Registry (PIR) formally notified ICANN of the >> >> > proposed change of control transaction on 14 November 2019 >> >> > [r20.rs6.net]< >> >> >> https://urldefense.proofpoint.com/v2/url?u=http-3A__r20.rs6.net_tn.jsp-3Ff-3D001ksZaHYpLxs73N74vLz88Vq0p2eY7hNPIUETQItxPS1zFOkKdqUiWFt-2DqViuZxFtMbojNo0l3-5FANH24DHECSiWoBxsLSaqGlloXx-5FUcAwJwakeQ9Zmj6QVbLPEgY1YoMQ30XcWD0EfoICTUD3fQsUgTRutD1d4E9y-2D5LUMBGXHzz5KkRxQtTHxwFk0xJWQ0E5Dc20U-2DqwV-5FjHI6W5uMb0IMvlWR-2D5vUUlNlzJnBCaG0Q-3D-26c-3Dwy9XJGNosEnEjdPoYLdJwvuIgsRRZOESZYkznmQPNTaHtmURx3UpcA-3D-3D-26ch-3D3Nfh4df3oGcxggBTYNdpswIf0un3QheyxW0pkf2jmeEOezCq3E9Zxg-3D-3D&d=DwMFaQ&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=8_WhWIPqsLT6TmF1Zmyci866vcPSFO4VShFqESGe_5iHWGlBLwwwehFBfjrsjWv9&m=Lr1oOkYZ9081GhqSfAb5smovhT1n5h6sykrEY1gEbF0&s=mLXHpNOHqUpl4b9smtPPhoUEZkfXME5gylo_YK5fpHA&e= >> >, >> >> the ICANN org and Board have worked together to thoughtfully and >> thoroughly >> >> evaluate the proposed acquisition to ensure that the .ORG registry >> remains >> >> secure, reliable, and stable. Throughout this process, ICANN has urged >> PIR, >> >> the Internet Society (ISOC), and Ethos Capital (Ethos) to engage and >> >> consult with the .ORG community, and to provide full transparency >> regarding >> >> the proposed >> >> > transaction. >> >> > >> >> > Today, ICANN is publishing >> >> > [r20.rs6.net]< >> >> >> https://urldefense.proofpoint.com/v2/url?u=http-3A__r20.rs6.net_tn.jsp-3Ff-3D001ksZaHYpLxs73N74vLz88Vq0p2eY7hNPIUETQItxPS1zFOkKdqUiWFt-2DqViuZxFtMjl-2DLfzT9kl16ErkR6z6u2dnFIk8nbt5udOqVrVKLsftd1T8OPz2mml3-2DC-2DH7IAjX29PnKBS-5FBmWKWgICCjqgyzR4c8NWnenXlseFPEKyVB16RneWbnmGzb0G1T7WZWmhO-2DJA9b67bhA0s30fnk2HieXDOgw9WXF6u-5FntnNq2sjl-2DbfHRdB-5F-5FCg-3D-3D-26c-3Dwy9XJGNosEnEjdPoYLdJwvuIgsRRZOESZYkznmQPNTaHtmURx3UpcA-3D-3D-26ch-3D3Nfh4df3oGcxggBTYNdpswIf0un3QheyxW0pkf2jmeEOezCq3E9Zxg-3D-3D&d=DwMFaQ&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=8_WhWIPqsLT6TmF1Zmyci866vcPSFO4VShFqESGe_5iHWGlBLwwwehFBfjrsjWv9&m=Lr1oOkYZ9081GhqSfAb5smovhT1n5h6sykrEY1gEbF0&s=ts4XYR8T3ZJT4y-6SxsLyD1y4BIj0BUeGrarBKdExLU&e= >> > >> >> PIR's recently updated Public Interest Commitments (PICs), which were >> >> received by ICANN on 7 April 2020. PIR proposes that these PICs be >> added to >> >> the .< >> >> >> http://r20.rs6.net/tn.jsp?f=001ksZaHYpLxs73N74vLz88Vq0p2eY7hNPIUETQItxPS1zFOkKdqUiWFt-qViuZxFtMMIlnB_968dbzElej_FsRAoGq9Eqxvee5Q_KV5Ct9-uvF3B31UTR6Pun8VJszaEAlzU4xxfVyba-mp3rK4vMyrYD5X7zBxTYL-Y2bodULglcmjvrcd2FKT5ZvSFm834cHPq-Lo-SHUpaAa10pknkz_QmRkfJzm_COPRwJcwnEAZIq0fVsl5mIrAuPWKCpT_0bS9JLJoOeypYS3lYOf8USOG9-Lnbs0VPbBZvw6z7abI16KnPdxcAd8ilswdLQVIKP58l2duFHIEfp_5jKkTmexLuak03kILHIa569s8HYm2jzhPYFwc30tXVW7a89Hu-2JoexXh6ZHsF4Ly5aM9lr3oG1z5LFmgsIBEZuu4ZtvCdXnl3JIDWTLsCvY5gP8VaKpDf_sU5EVVKYmg9DuNkuIpPYMB4w6Knz3koBfDS71iKx_MiXAc-a4n0KRH04OAFSnK9SoDHcro7hFDPzd-y_oY-NdPKWVWBy43QVOxGMzUxgS0TgrW6gmetCRBpI_TDSU62AMXlzBng-VsqHgkUvtQ==&c=wy9XJGNosEnEjdPoYLdJwvuIgsRRZOESZYkznmQPNTaHtmURx3UpcA==&ch=3Nfh4df3oGcxggBTYNdpswIf0un3QheyxW0pkf2jmeEOezCq3E9Zxg== >> >ORG >> >> Registry Agreement [r20.rs6.net]< >> >> >> https://urldefense.proofpoint.com/v2/url?u=http-3A__r20.rs6.net_tn.jsp-3Ff-3D001ksZaHYpLxs73N74vLz88Vq0p2eY7hNPIUETQItxPS1zFOkKdqUiWFt-2DqViuZxFtMt8ZrQ-5FUUDPTpBScWUeesMbPDgtiEx9JsqUZ2RBBSmfuo3amjba4h6H0FCK6sF6ZzI563CxHXZiQNwwMvlhv1A-5FqJiOclOyojun5IxJ71bhFSHVpJ8RCrubAItweNsQgV39EXBLH9hvA-3D-26c-3Dwy9XJGNosEnEjdPoYLdJwvuIgsRRZOESZYkznmQPNTaHtmURx3UpcA-3D-3D-26ch-3D3Nfh4df3oGcxggBTYNdpswIf0un3QheyxW0pkf2jmeEOezCq3E9Zxg-3D-3D&d=DwMFaQ&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=8_WhWIPqsLT6TmF1Zmyci866vcPSFO4VShFqESGe_5iHWGlBLwwwehFBfjrsjWv9&m=Lr1oOkYZ9081GhqSfAb5smovhT1n5h6sykrEY1gEbF0&s=PFZv7yhgsFMq0lzJYXDEZdNlTGoZ4scsPzhlOXouNvA&e= >> >should >> >> ICANN approve the change of control request submitted by PIR. Two >> versions >> >> of the PICs are being published: a "clean [r20.rs6.net]< >> >> >> https://urldefense.proofpoint.com/v2/url?u=http-3A__r20.rs6.net_tn.jsp-3Ff-3D001ksZaHYpLxs73N74vLz88Vq0p2eY7hNPIUETQItxPS1zFOkKdqUiWFt-2DqViuZxFtMPkg-5FIhS82AYz2s0agDU9ankQXLYTjJeksRZN597OYN1pXU7CA-2DizP91h-2DCxUrMPyE581jkJBcMq5gWufSkDdhOW2M-2DkMl3vUtj4urTtIr99h-5FkiqRZTERHDJtge9P-5Fz5WerwaZluwmVlaNURyQf-2DAvXUwzYPpFr-5FYvXFhHORQWqTP5NK7uD3-5Fg-3D-3D-26c-3Dwy9XJGNosEnEjdPoYLdJwvuIgsRRZOESZYkznmQPNTaHtmURx3UpcA-3D-3D-26ch-3D3Nfh4df3oGcxggBTYNdpswIf0un3QheyxW0pkf2jmeEOezCq3E9Zxg-3D-3D&d=DwMFaQ&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=8_WhWIPqsLT6TmF1Zmyci866vcPSFO4VShFqESGe_5iHWGlBLwwwehFBfjrsjWv9&m=Lr1oOkYZ9081GhqSfAb5smovhT1n5h6sykrEY1gEbF0&s=yrlvXk8vaOH9RSyqAuJb1YP_VxI3vFuz6Yyo4WxRdkc&e= >> >" >> >> version and a "redline [r20.rs6.net]< >> >> >> https://urldefense.proofpoint.com/v2/url?u=http-3A__r20.rs6.net_tn.jsp-3Ff-3D001ksZaHYpLxs73N74vLz88Vq0p2eY7hNPIUETQItxPS1zFOkKdqUiWFt-2DqViuZxFtM2NGnW2TWIbAuSn-5Fra-2DV40EhKb8SQVrjtcMLlKR3PwRnjHjXMd-5FJWOT4i6SC-5FtTb-5FuTMBKCjdgG-5FAnOVMddwuP-5F-2DZMTcbzNklSTp6b1EE960w0cwLdtSoQOXwcvOfLoT1zI-2DzoNWdc4nTxw5lQIXMfgZyb5cgQbeVhbscHVmg5otVtAqawVBTSLJaHeGb7Xy2-26c-3Dwy9XJGNosEnEjdPoYLdJwvuIgsRRZOESZYkznmQPNTaHtmURx3UpcA-3D-3D-26ch-3D3Nfh4df3oGcxggBTYNdpswIf0un3QheyxW0pkf2jmeEOezCq3E9Zxg-3D-3D&d=DwMFaQ&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=8_WhWIPqsLT6TmF1Zmyci866vcPSFO4VShFqESGe_5iHWGlBLwwwehFBfjrsjWv9&m=Lr1oOkYZ9081GhqSfAb5smovhT1n5h6sykrEY1gEbF0&s=L2bmKUr5EWBlGGQCZOhCeVTqRJu6SEUQgFgHIAjmJ1M&e= >> >" >> >> version that shows changes made by PIR from its 16 March 2020 version >> >> submitted to ICANN following PIR's Public Engagement process. >> >> > [r20.rs6.net]< >> >> >> https://urldefense.proofpoint.com/v2/url?u=http-3A__r20.rs6.net_tn.jsp-3Ff-3D001ksZaHYpLxs73N74vLz88Vq0p2eY7hNPIUETQItxPS1zFOkKdqUiWFt-2DqViuZxFtM1ecPoHkp0Qu90ued5Lbmf3r3DQM-2DRewknXnd2HMqbj-2DaC7vftx82qbFD6UixhfAJk6asLfO5ZiM5vpvaysPdcYLV2k7nAGJHjgvpt54cmoCnd2VcNM43hg-3D-3D-26c-3Dwy9XJGNosEnEjdPoYLdJwvuIgsRRZOESZYkznmQPNTaHtmURx3UpcA-3D-3D-26ch-3D3Nfh4df3oGcxggBTYNdpswIf0un3QheyxW0pkf2jmeEOezCq3E9Zxg-3D-3D&d=DwMFaQ&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=8_WhWIPqsLT6TmF1Zmyci866vcPSFO4VShFqESGe_5iHWGlBLwwwehFBfjrsjWv9&m=Lr1oOkYZ9081GhqSfAb5smovhT1n5h6sykrEY1gEbF0&s=ANKFOin7HLmMPYHXq1AFPnYmvexcAakJovbMGTdQr8A&e= >> >> > >> >> > >> >> > The revised PICs that ICANN is publishing today are in response to >> >> > additional questions posed by ICANN as part of its diligence around >> >> > the change of control request. On 3 April 2020, ICANN provided PIR >> >> > with two sets of questions. One set of questions are in follow-up to >> >> > previous ICANN inquiries designed to further understand the proposed >> >> > transaction and its potential effect on PIR and the .ORG top-level >> >> > domain (TLD). The second set of questions relate specifically to the >> >> > proposed PICs. PIR has indicated that it is working to answer all of >> >> > the questions from ICANN. >> >> > >> >> > It is ICANN's intention to post PIR's responses to these questions >> >> > when they are available, subject to any appropriate requests for >> >> > confidentiality made by PIR. >> >> > >> >> > Many people have questioned the enforceability of PICs by ICANN. To >> >> > be clear, PICs are enforceable by ICANN. Any Internet user may >> >> > submit complaints to ICANN Contractual Compliance. In addition, >> >> > ICANN Contractual Compliance may identify an issue through its >> >> > proactive monitoring. ICANN's follow-up questions to PIR seek to >> >> > ensure that ICANN has a clear understanding of each commitment >> >> > within the PICs, such that it could be enforced should the need >> >> > arise. The ICANN Board continues to have reservations regarding the >> >> > enforceability of PIR's proposed PICs. >> >> > >> >> > The .ORG Registry Agreement stipulates a specified time period for >> >> > ICANN to approve or withhold consent of the proposed change of >> >> > control of PIR. ICANN and PIR have agreed to extend the deadline >> >> > several times since the original deadline in mid-January, and the >> >> > deadline for ICANN's response is now 20 April 2020. >> >> > >> >> > Similar to when voluntary commitments in the form of PICs were >> >> > proposed by applicants for new generic TLDs, ICANN is providing >> >> > PIR's proposed PICs to the ICANN community with this public notice. >> >> > Given the fast-approaching deadline for ICANN to make a decision to >> >> > approve or withhold consent on the requested change of control of >> >> > PIR, the typical 30-day public notice period has been condensed to >> >> > seven days. We recognize the full engagement of the .ORG community >> >> > in PIR's consultation process, but wanted to ensure ICANN remained >> >> > fully transparent in what is being considered, the concerns still >> >> > present in the Board's review, and what the Board will be reviewing. >> >> > >> >> > How to Participate: Feedback may be submitted as a comment to this >> >> > blog >> >> > [r20.rs6.net]< >> >> >> https://urldefense.proofpoint.com/v2/url?u=http-3A__r20.rs6.net_tn.jsp-3Ff-3D001ksZaHYpLxs73N74vLz88Vq0p2eY7hNPIUETQItxPS1zFOkKdqUiWFt-2DqViuZxFtMlCsaRdGZCZWr6aGU7qSTQtpUsX57iyMIgI8JJa96lU54JNF3m0f3uwiK5VBqZGvI76JFMJ2xpZj-5FzGN7OihHOFJm5gB4DU1i7ZfKQR5gT36asgmsO8S0kradGtN09wQ0WCwZLgYbr-5F5OrqP-5F5rE8mBR-2DqBQzg-5FCJ1NMSJx02GVq7aag0yuegdg-3D-3D-26c-3Dwy9XJGNosEnEjdPoYLdJwvuIgsRRZOESZYkznmQPNTaHtmURx3UpcA-3D-3D-26ch-3D3Nfh4df3oGcxggBTYNdpswIf0un3QheyxW0pkf2jmeEOezCq3E9Zxg-3D-3D&d=DwMFaQ&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=8_WhWIPqsLT6TmF1Zmyci866vcPSFO4VShFqESGe_5iHWGlBLwwwehFBfjrsjWv9&m=Lr1oOkYZ9081GhqSfAb5smovhT1n5h6sykrEY1gEbF0&s=IWPBCoMxSRD7G3awtw0MQUJ1KUg5OrIsYh5MhUj_Jvk&e= >> > >> >> or through correspondence to me or the ICANN >> >> > Board. >> >> > >> >> > We thank the ICANN community for its active participation in this >> >> > matter and remain committed to keeping you informed of new >> >> > developments. >> >> > >> >> > >> >> > >> >> > NEW: Addressing Recent Zoom News >> >> > Executive: Ashwin Rangan, Senior Vice President, Engineering and >> >> > Chief Information Officer >> >> > >> >> > ICANN?s video conferencing platform, Zoom, has been in the news >> >> > quite a bit. With shelter-in-place and work-from-home becoming more >> >> > familiar, not only for the ICANN community but the world at large, >> >> > Zoom has become a vital tool for many businesses. With this recent >> >> > increase in Zoom usage, we?ve also seen a number of bugs, flaws, and >> >> > security vulnerabilities come to light. >> >> > >> >> > It?s natural that a hugely popular system like Zoom will be poked >> >> > and prodded, and it?s likely that alarming bits of information will >> >> > continue to be revealed in the coming weeks and months. >> >> > >> >> > However, it?s important to remember that almost any piece of >> >> > software has bugs and glitches. What?s vitally important in these >> >> > moments is how the software vendor reacts to receiving such >> >> > information. In this regard, ICANN applauds Zoom for their efforts. >> >> > Every time a new vulnerability has been exposed, Zoom has reacted >> >> > swiftly by releasing patches within a day or two, while remaining >> >> > transparent about the nature of the underlying issues. >> >> > >> >> > If you care to learn more about any specific vulnerability or how >> >> > Zoom has responded, we highly recommend taking a look at Zoom?s >> >> > blog, which is available here >> >> > [r20.rs6.net]< >> >> >> https://urldefense.proofpoint.com/v2/url?u=http-3A__r20.rs6.net_tn.jsp-3Ff-3D001ksZaHYpLxs73N74vLz88Vq0p2eY7hNPIUETQItxPS1zFOkKdqUiWFt-2DqViuZxFtM6QSfysSoBf4quheUTAwEiPz0sCAeBTGnXtBWT3VOUDdgLqy-5FjkRDUX-2DDoc-5FAIJBNsEZCrqBaQEMqmDJxayUWRYd8HvkuefBV-26c-3Dwy9XJGNosEnEjdPoYLdJwvuIgsRRZOESZYkznmQPNTaHtmURx3UpcA-3D-3D-26ch-3D3Nfh4df3oGcxggBTYNdpswIf0un3QheyxW0pkf2jmeEOezCq3E9Zxg-3D-3D&d=DwMFaQ&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=8_WhWIPqsLT6TmF1Zmyci866vcPSFO4VShFqESGe_5iHWGlBLwwwehFBfjrsjWv9&m=Lr1oOkYZ9081GhqSfAb5smovhT1n5h6sykrEY1gEbF0&s=PcGAwKynwBZUH87c_nxV4y4WJ4UDzgrIgLEF0Y-yy3M&e= >> >. >> >> As stated before, it?s likely that this won?t be the last time we will >> hear >> >> about Zoom?s flaws, either from security researchers or new attack >> >> > vectors. >> >> > >> >> > While we continue to monitor developments, ICANN remains committed >> >> > to Zoom. We strive to offer the best solutions to our community, and >> >> > at this time, we are still confident that Zoom fits the bill. >> >> > >> >> > If you have any questions or comments regarding Zoom and how it may >> >> > relate to you, please do not hesitate to reach out to >> >> > mts at icann.org. >> >> > >> >> > >> >> > >> >> > ENDS TOMORROW: Your Feedback about this Digest >> >> > Executive: David Olive, Senior Vice President, Policy Development >> Support >> >> > >> >> > Reflecting on the first year of the ICANN Community Leadership >> >> > Digest, the ICANN org Policy Development Support function seeks your >> >> > feedback. Please take this brief survey >> >> > [r20.rs6.net]< >> >> >> https://urldefense.proofpoint.com/v2/url?u=http-3A__r20.rs6.net_tn.jsp-3Ff-3D001ksZaHYpLxs73N74vLz88Vq0p2eY7hNPIUETQItxPS1zFOkKdqUiWFkIoDPRoPRvsBdZ-5FGoiv0BcyEsqTchFFXXkzDy-5FPrXuLQ2wWkGUnqMG5vB-5FBsL-2DexDGGYx9Z93RcP-5FqESAsVE1N-5Fes14Oc-5FQcEOwODWQkSy-2D-26c-3Dwy9XJGNosEnEjdPoYLdJwvuIgsRRZOESZYkznmQPNTaHtmURx3UpcA-3D-3D-26ch-3D3Nfh4df3oGcxggBTYNdpswIf0un3QheyxW0pkf2jmeEOezCq3E9Zxg-3D-3D&d=DwMFaQ&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=8_WhWIPqsLT6TmF1Zmyci866vcPSFO4VShFqESGe_5iHWGlBLwwwehFBfjrsjWv9&m=Lr1oOkYZ9081GhqSfAb5smovhT1n5h6sykrEY1gEbF0&s=9DQ1pHoBVR4vpcEUVnWV4Lw8sYIcbujzoWdUKYawy9U&e= >> > >> >> by Friday, 10 April >> >> > 2020. >> >> > >> >> > >> >> > >> >> > REMINDER: Call for Expressions of Interest: Standing Panel for >> >> > ICANN?s Independent Review Process >> >> > Announcement >> >> > [r20.rs6.net]< >> >> >> https://urldefense.proofpoint.com/v2/url?u=http-3A__r20.rs6.net_tn.jsp-3Ff-3D001ksZaHYpLxs73N74vLz88Vq0p2eY7hNPIUETQItxPS1zFOkKdqUiWFhDXvOWShZvD2hLEBznqukU-2DzpGY9SKvgZYnzs8Pb7q6cYigVDx3lR28KNIIg1OZSSrtV6PTHjePVwGIxmZNiT5QJa0uMX2tqVpBsJG4J0BWWru2lfXIvdoYMrq-5FhNGeLCfd1j-5F1OZaM-26c-3Dwy9XJGNosEnEjdPoYLdJwvuIgsRRZOESZYkznmQPNTaHtmURx3UpcA-3D-3D-26ch-3D3Nfh4df3oGcxggBTYNdpswIf0un3QheyxW0pkf2jmeEOezCq3E9Zxg-3D-3D&d=DwMFaQ&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=8_WhWIPqsLT6TmF1Zmyci866vcPSFO4VShFqESGe_5iHWGlBLwwwehFBfjrsjWv9&m=Lr1oOkYZ9081GhqSfAb5smovhT1n5h6sykrEY1gEbF0&s=wh1fzSPiKMlK_nF31FLv2uByqlUbU5tu7_fdgg8Hif4&e= >> >> > >> >> > >> >> > On 31 March 2020, ICANN opened a call for Expressions of Interest >> >> > for panelists to serve on the omnibus Standing Panel for ICANN's >> >> > Independent Review Process (IRP). The deadline to submit Expressions >> >> > of Interest is 31 July 2020 at 23:59 UTC. >> >> > >> >> > Candidates for the IRP omnibus Standing Panel should review the >> >> > Expressions of Interest document >> >> > [r20.rs6.net]< >> >> >> https://urldefense.proofpoint.com/v2/url?u=http-3A__r20.rs6.net_tn.jsp-3Ff-3D001ksZaHYpLxs73N74vLz88Vq0p2eY7hNPIUETQItxPS1zFOkKdqUiWFhDXvOWShZvDgPvUW1EhP8WCVbm7MS0BsmCnAHsaFMUEoj9AM6ObL9ubtekC1N1ukFoJ-5FBciA-2DgkijA-2DFBr90Ud-5FTOGNu8PWMhrNjdjjyZvqFIQ450g94Vru2c4WBkwiqkUG0w7QB7QlvcBo0S6i9KT2Lp9FwvFhrK2SAcT3d8Ft-26c-3Dwy9XJGNosEnEjdPoYLdJwvuIgsRRZOESZYkznmQPNTaHtmURx3UpcA-3D-3D-26ch-3D3Nfh4df3oGcxggBTYNdpswIf0un3QheyxW0pkf2jmeEOezCq3E9Zxg-3D-3D&d=DwMFaQ&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=8_WhWIPqsLT6TmF1Zmyci866vcPSFO4VShFqESGe_5iHWGlBLwwwehFBfjrsjWv9&m=Lr1oOkYZ9081GhqSfAb5smovhT1n5h6sykrEY1gEbF0&s=G4e0eHDidhaSHCLG-Lp0mdVooTB9Udt6NFCT4_hfNvQ&e= >> >before >> >> submission. The document includes the following >> >> > information: >> >> > >> >> > ? Panel Position Description >> >> > ? Required or Highly Preferred Skills >> >> > ? Required or Highly Preferred Experience >> >> > ? Time Commitment >> >> > ? Compensation and Selection >> >> > >> >> > Expressions of Interest should be submitted to >> >> > IRP-Standingpanel-EOI2020 at icann.org> >> IRP-Standingpanel-EOI2020 at icann.org> by 23:59 UTC on 31 July >> >> > 2020. >> >> > >> >> > Public Comment >> >> > >> >> > CLOSES MONDAY: Revised Community Travel Support Guidelines >> >> > [r20.rs6.net]< >> >> >> https://urldefense.proofpoint.com/v2/url?u=http-3A__r20.rs6.net_tn.jsp-3Ff-3D001ksZaHYpLxs73N74vLz88Vq0p2eY7hNPIUETQItxPS1zFOkKdqUiWFtY89CwSG4vGP9QyFiNsydEQVAWcEV-5Fx-5FyYMuDyD9mhUkKrwtZ0UYkgE52pUAGJUVyllQf8HsJVLqUb7Hl-2DQJvk-2DtNR7dPmp0y3V4wbIVgix6rHxXUJcoqQekwI114IIACiTWznCmlJwYRq4nQbpRTCw-2Dara5yu37Emw-5FDvyjlUE-26c-3Dwy9XJGNosEnEjdPoYLdJwvuIgsRRZOESZYkznmQPNTaHtmURx3UpcA-3D-3D-26ch-3D3Nfh4df3oGcxggBTYNdpswIf0un3QheyxW0pkf2jmeEOezCq3E9Zxg-3D-3D&d=DwMFaQ&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=8_WhWIPqsLT6TmF1Zmyci866vcPSFO4VShFqESGe_5iHWGlBLwwwehFBfjrsjWv9&m=Lr1oOkYZ9081GhqSfAb5smovhT1n5h6sykrEY1gEbF0&s=KZRoix0AC0mirjIIP5MqMXYT8_kOVKpVj-AnQc4qVEI&e= >> >> > >> >> > Close Date: Monday, 13 April 2020 >> >> > >> >> > Proposal for Chinese Script Root Zone Label Generation Rules >> >> > [r20.rs6.net]< >> >> >> https://urldefense.proofpoint.com/v2/url?u=http-3A__r20.rs6.net_tn.jsp-3Ff-3D001ksZaHYpLxs73N74vLz88Vq0p2eY7hNPIUETQItxPS1zFOkKdqUiWFhiNYDgFY8zJdVvy8ZlKxm9ygyJmLgZOGIYB-2DzeG5FSuiAXh8oBSRbqMjNeUcl0ggkZN8rs6RO4JLtosigTh8p4JBv7Amc7V4tOTqIRpzAXok0l9gaWxurzrwTxTbtIpqbNaih-5Fc5l85eB854mYXP0gKGto16a6-5FING4f4AaT1yo-26c-3Dwy9XJGNosEnEjdPoYLdJwvuIgsRRZOESZYkznmQPNTaHtmURx3UpcA-3D-3D-26ch-3D3Nfh4df3oGcxggBTYNdpswIf0un3QheyxW0pkf2jmeEOezCq3E9Zxg-3D-3D&d=DwMFaQ&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=8_WhWIPqsLT6TmF1Zmyci866vcPSFO4VShFqESGe_5iHWGlBLwwwehFBfjrsjWv9&m=Lr1oOkYZ9081GhqSfAb5smovhT1n5h6sykrEY1gEbF0&s=g3VHZG_hmZ8ewQKGAD8iSf-O0ckPMC4xfCiO6F2bQkc&e= >> >> > >> >> > Close Date: Monday, 20 April 2020 >> >> > >> >> > Proposal for Bangla Script Root Zone Label Generation Rules >> >> > [r20.rs6.net]< >> >> >> https://urldefense.proofpoint.com/v2/url?u=http-3A__r20.rs6.net_tn.jsp-3Ff-3D001ksZaHYpLxs73N74vLz88Vq0p2eY7hNPIUETQItxPS1zFOkKdqUiWFmKYv52uy6-2D4iiVzpAClZnxseaCCiGyXl0PjEyfQjPwmxWMXlc-5FOuVGUsBSfBJ4Mb8jrSF2ecxJcaUOwQrllleeTthNvI-5FKg7imzq2TklU4gGyf05gDt8XdZloNEILhO5PZupDyzOeDc6VBNUfC5kOBo8PJR7FS3KaJ6Hp2dBRu8-26c-3Dwy9XJGNosEnEjdPoYLdJwvuIgsRRZOESZYkznmQPNTaHtmURx3UpcA-3D-3D-26ch-3D3Nfh4df3oGcxggBTYNdpswIf0un3QheyxW0pkf2jmeEOezCq3E9Zxg-3D-3D&d=DwMFaQ&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=8_WhWIPqsLT6TmF1Zmyci866vcPSFO4VShFqESGe_5iHWGlBLwwwehFBfjrsjWv9&m=Lr1oOkYZ9081GhqSfAb5smovhT1n5h6sykrEY1gEbF0&s=7RSaqRNE7rwHcd2Sia8v2TRbLiflkRsGySbo33Pq9D0&e= >> >> > >> >> > Close Date: Thursday, 23 April 2020 >> >> > >> >> > Phase 1 Initial Report of the Review of All Rights Protection >> >> > Mechanisms in All gTLDs Policy Development Process >> >> > [r20.rs6.net]< >> >> >> https://urldefense.proofpoint.com/v2/url?u=http-3A__r20.rs6.net_tn.jsp-3Ff-3D001ksZaHYpLxs73N74vLz88Vq0p2eY7hNPIUETQItxPS1zFOkKdqUiWFj9fpHfmJJBeKb1epUydWc3EzsZSj8Uwcoii-2DXmD2XtnFwFaGxB-2Dx6I16WKdSg0EkEC8BAhBu2WHMbFq2sUIRInh2xgGkOwZhGqyawEOqZ634-5FhH7CQ8RxlXu63kefU2cg85EZjcOb2duwpwhMjATiAMPeaPDlTsxA-3D-3D-26c-3Dwy9XJGNosEnEjdPoYLdJwvuIgsRRZOESZYkznmQPNTaHtmURx3UpcA-3D-3D-26ch-3D3Nfh4df3oGcxggBTYNdpswIf0un3QheyxW0pkf2jmeEOezCq3E9Zxg-3D-3D&d=DwMFaQ&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=8_WhWIPqsLT6TmF1Zmyci866vcPSFO4VShFqESGe_5iHWGlBLwwwehFBfjrsjWv9&m=Lr1oOkYZ9081GhqSfAb5smovhT1n5h6sykrEY1gEbF0&s=nM36roD_xIofeZLEMtaGs4IFjj_j1wl-og3VAEvdazg&e= >> >> > >> >> > Close Date: Monday, 27 April 2020 >> >> > >> >> > Addendum to the Initial Report of the Expedited Policy Development >> >> > Process (EPDP) on the Temporary Specification for gTLD Registration >> >> > Data Team ? Phase 2 >> >> > [r20.rs6.net]< >> >> >> https://urldefense.proofpoint.com/v2/url?u=http-3A__r20.rs6.net_tn.jsp-3Ff-3D001ksZaHYpLxs73N74vLz88Vq0p2eY7hNPIUETQItxPS1zFOkKdqUiWFkIoDPRoPRvs82iXYdszIj2pYDMS0rHPlAwpwN9mhLx55-5FummJlrmbA4Y8TZsI1OX7YHgEoYiLKBHSAHoMPs0M9SBwTeNrArt-5F5k46yplBom7C7hdDtQ5K1ogJhd-5Fl8lJkSnqckbjs4vzHjRTRP8RF2guXWgh9xErA-3D-3D-26c-3Dwy9XJGNosEnEjdPoYLdJwvuIgsRRZOESZYkznmQPNTaHtmURx3UpcA-3D-3D-26ch-3D3Nfh4df3oGcxggBTYNdpswIf0un3QheyxW0pkf2jmeEOezCq3E9Zxg-3D-3D&d=DwMFaQ&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=8_WhWIPqsLT6TmF1Zmyci866vcPSFO4VShFqESGe_5iHWGlBLwwwehFBfjrsjWv9&m=Lr1oOkYZ9081GhqSfAb5smovhT1n5h6sykrEY1gEbF0&s=372vmvMQMKD1hyBnYvsBdaqs5ENaZ83CYOFt3YlQQ5Q&e= >> >> > >> >> > Close Date: Tuesday, 5 May 2020 >> >> > Guidelines for Developing Reference Label Generation Rules (LGRs) >> >> > for the Second Level Version 2 >> >> > [r20.rs6.net]< >> >> >> https://urldefense.proofpoint.com/v2/url?u=http-3A__r20.rs6.net_tn.jsp-3Ff-3D001ksZaHYpLxs73N74vLz88Vq0p2eY7hNPIUETQItxPS1zFOkKdqUiWFhkxpqfCSVcEKH3lZoDdmOeJGHXZWUszKwUfZd4u0uFjsOQLvwjUSG7DpH9-5Fmg09z483tj0jtrRtSrD-5FQHfMU-5F1gfUAgtIzJrrXdCCz60eVKM-2DMSL68SnYO77GMdeDFp8s8YUM5faEvCxgvyQZ-2D9yFNacpgtcwSCHA-3D-3D-26c-3Dwy9XJGNosEnEjdPoYLdJwvuIgsRRZOESZYkznmQPNTaHtmURx3UpcA-3D-3D-26ch-3D3Nfh4df3oGcxggBTYNdpswIf0un3QheyxW0pkf2jmeEOezCq3E9Zxg-3D-3D&d=DwMFaQ&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=8_WhWIPqsLT6TmF1Zmyci866vcPSFO4VShFqESGe_5iHWGlBLwwwehFBfjrsjWv9&m=Lr1oOkYZ9081GhqSfAb5smovhT1n5h6sykrEY1gEbF0&s=2L3B7qhd8walcslu4Qzo1xk083LuHFdGUKBwCMoEcVI&e= >> >> > >> >> > Close Date: Tuesday, 12 May 2020 >> >> > >> >> > Volume 2, Issue 29 | Archive >> >> > [r20.rs6.net]< >> >> >> https://urldefense.proofpoint.com/v2/url?u=http-3A__r20.rs6.net_tn.jsp-3Ff-3D001ksZaHYpLxs73N74vLz88Vq0p2eY7hNPIUETQItxPS1zFOkKdqUiWFvN81lnNY4rwlNDFDEUS18xytYwuCwvTM36th-2DNM1lg23ibrV1QS9vnURID3EAHR2bL3FO7PSkQ2LjAdsmzGVn3m9oxJsnuRYZ7gwJeaIqWDGMtkORnO7mab4cIUHDskuHoIGeGQcvuVLX-2D-2DaoviPHPVhZVgldulZGKw9xaC8AS22-5FJL9uFCJzA-3D-26c-3Dwy9XJGNosEnEjdPoYLdJwvuIgsRRZOESZYkznmQPNTaHtmURx3UpcA-3D-3D-26ch-3D3Nfh4df3oGcxggBTYNdpswIf0un3QheyxW0pkf2jmeEOezCq3E9Zxg-3D-3D&d=DwMFaQ&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=8_WhWIPqsLT6TmF1Zmyci866vcPSFO4VShFqESGe_5iHWGlBLwwwehFBfjrsjWv9&m=Lr1oOkYZ9081GhqSfAb5smovhT1n5h6sykrEY1gEbF0&s=LLA54bpW6lPOCy5iKFZ3Vb9RORKPyANq7iVQ7ex-Q_8&e= >> > >> >> | Next Issue: Monday, 13 April >> >> > 2020 >> >> > >> >> > >> >> > _______________________________________________ >> >> > council mailing list >> >> > council at gnso.icann.org >> >> > https://mm.icann.org/mailman/listinfo/council >> >> > >> >> > _______________________________________________ >> >> > 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. >> >> >> > -- *Bruna Martins dos Santos * Skype ID: bruna.martinsantos @boomartins -------------- next part -------------- An HTML attachment was scrubbed... URL: From rafik.dammak at gmail.com Sun Apr 19 13:10:35 2020 From: rafik.dammak at gmail.com (Rafik Dammak) Date: Sun, 19 Apr 2020 19:10:35 +0900 Subject: [NCSG-PC] [NCSG-EC] Fwd: PLEASE READ: NCPH election for Board seat 14 In-Reply-To: References: <57A94745-69DE-4628-8168-8F15F1C7D467@icann.org> <50546364-b2fd-bd3d-77a3-f6613a7c33e9@mail.utoronto.ca> <6539E322-F58B-410A-B3D4-A05C6C868113@ipjustice.org> <83d286ea-18e3-760e-548d-b3eb897df46e@mail.utoronto.ca> Message-ID: hi all, the voting will happen in 20th April and Stephanie will vote yes for Matt in our behalf (the call will be recorded). Best, Rafik Le mar. 14 avr. 2020 ? 23:07, Rafik Dammak a ?crit : > Hi James, > > thanks :) I believe it should be Stephanie as NCSG chair and already dealt > with Dean from CSG. > we just need to make it formal regarding the vote: voting yes for Mathew > Shears for seat #14. details about election are being flush out either a > vote through phone call or through tally ballot. NCSG chair as > representative will vote on NCSG behalf. > Also Carlton as NCA was reached out and he confirmed his support for Matt. > > Best, > > Rafik > Le lun. 13 avr. 2020 ? 22:40, lists at icann.guru a > ?crit : > >> Hah ok, well in that case I propose you vote for Matt on our behalf =) >> >> *---* >> *James Gannon* >> >> On 13/04/2020 14:30:55, Rafik Dammak wrote: >> Hi James, >> thanks, >> short answer, not necessarily :) >> >> Best, >> Rafik >> >> >> Le lun. 13 avr. 2020 ? 17:22, lists at icann.guru a >> ?crit : >> >>> I assume that you as the PC Chair will vote on our behalf? >>> >>> *---* >>> *James Gannon* >>> >>> On 13/04/2020 09:20:26, Rafik Dammak wrote: >>> Hi all, >>> >>> please let me know if there is any comment or question. >>> we should appoint who will vote on behalf of NCSG. >>> >>> Best, >>> >>> Rafik >>> >>> Le jeu. 9 avr. 2020 ? 19:03, Rafik Dammak a >>> ?crit : >>> >>>> Addding the correct pc list address >>>> >>>> On Thu, Apr 9, 2020, 13:58 Rafik Dammak wrote: >>>> >>>>> Thanks Stephanie for sharing the info >>>>> as first action, I put this as an item for update to our membership in >>>>> next week policy call, then follow-up in list to ensure that information is >>>>> shared broadly. >>>>> with regard to the vote, we can coordinate with all representatives >>>>> about the support and appoint who will cast the vote on behalf of NCSG. I >>>>> think the vote by 20th April is doable. >>>>> >>>>> Best, >>>>> >>>>> Rafik >>>>> >>>>> Le jeu. 9 avr. 2020 ? 06:31, Stephanie E Perrin via NCSG-EC < >>>>> ncsg-ec at lists.ncsg.is> a ?crit : >>>>> >>>>>> In which case, I am happy to step back and permit the PC to organize >>>>>> this. I have reached out to Carlton Samuels, as his collaboration on this >>>>>> is required. I have not heard back from him, as yet. Over to you, Rafik. >>>>>> >>>>>> Stephanie >>>>>> On 2020-04-08 5:22 p.m., Robin Gross wrote: >>>>>> >>>>>> Hi all, >>>>>> >>>>>> I?ve add the NCSG-PC onto this thread since it is the PC who will >>>>>> vote and select our board nominee (pursuant to NCSG Charter). >>>>>> >>>>>> Thanks, >>>>>> Robin >>>>>> >>>>>> On Apr 8, 2020, at 2:20 PM, Stephanie E Perrin via NCSG-EC < >>>>>> ncsg-ec at lists.ncsg.is> wrote: >>>>>> >>>>>> I need to consult you guys, then we (csg and ncsg) need to set up an >>>>>> election, where we pick someone to vote for us, and if we get two votes for >>>>>> Matthew (ie each side votes for him) we tell staff and Council he is our >>>>>> nominee. It seems a bit clumsy but since we have had a meltdown in the >>>>>> past, we needed procedures.... >>>>>> >>>>>> I presume staff will set up that election for us, will ask Carlos >>>>>> Reyes who is now in charge of our policy support, not Mary Wong. >>>>>> >>>>>> cheers Steph >>>>>> >>>>>> PS Dean Marks is doing the same thing with the CSG guys. >>>>>> >>>>>> >>>>>> On 2020-04-08 5:16 p.m., Raphael Beauregard-Lacroix wrote: >>>>>> >>>>>> Sure, I'm just not sure what needs to be done! >>>>>> >>>>>> On Wed, Apr 8, 2020 at 1:04 PM Stephanie E Perrin via NCSG-EC < >>>>>> ncsg-ec at lists.ncsg.is> wrote: >>>>>> >>>>>>> Hi folks, we need to organize on the election of Matthew Shears for >>>>>>> Board seat 14. I have reached out to Carlton Samuels, to tick the box of >>>>>>> consulting with our nomcom appointee (no response so far) and I have been >>>>>>> chatting with Dean Marks from the CSG, who is keen to cooperate. We are >>>>>>> trying to meet this new deadline of April 20, can we organize to hold our >>>>>>> election next week in time to offer our name? The CSG thinks they can. >>>>>>> >>>>>>> Sorry to push but we have to get this done faster now due to ICANN's >>>>>>> revised timelines....since we are agreed on the candidate, it is just >>>>>>> paperwork.... >>>>>>> >>>>>>> cheers Steph >>>>>>> >>>>>>> >>>>>>> -------- Forwarded Message -------- >>>>>>> Subject: PLEASE READ: NCPH election for Board seat 14 >>>>>>> Date: Tue, 7 Apr 2020 20:17:14 +0000 >>>>>>> From: Mary Wong >>>>>>> To: Dean Marks , Stephanie E >>>>>>> Perrin >>>>>>> , Bruna Martins dos Santos >>>>>>> , Joan Kerr >>>>>>> , Rafik Dammak >>>>>>> , Selli, Claudia >>>>>>> , >>>>>>> csg-excomm at icann.org , >>>>>>> Barbara Wanner >>>>>>> CC: Chantelle Doerksen >>>>>>> , Maryam Bakoshi >>>>>>> , Andrea >>>>>>> Glandon , >>>>>>> Carlos Reyes >>>>>>> >>>>>>> Dear CSG and NCSG leaders, >>>>>>> >>>>>>> >>>>>>> I would like to apologize for bringing up this topic at this late >>>>>>> stage, and at a time when I know that many community members are focusing >>>>>>> on important personal and family matters during the current COVID-19 >>>>>>> situation. Please understand that we as staff would not have raised this >>>>>>> were it not a Bylaws-related matter. >>>>>>> >>>>>>> >>>>>>> Here is the issue: under the ICANN Bylaws, formal notification of a >>>>>>> nominee for either Board seat 13 or 14 must be provided to the Empowered >>>>>>> Community Administration at least six (6) months prior to the commencement >>>>>>> of that potential Director?s term. As the 2020 Annual General Meeting is >>>>>>> due to conclude on 22 October 2020 (which we realize is somewhat earlier >>>>>>> than previous AGMs), this means that *the Empowered Community >>>>>>> Administration must receive the Non-Contracted Parties House (NCPH) >>>>>>> nomination of a Director to fill Board seat 14 by 22 April 2020* >>>>>>> (and not May as we had advised you previously). >>>>>>> >>>>>>> >>>>>>> I understand that the NCPH?s current plan is to hold the formal vote >>>>>>> (via a CSG and NCSG representative and in accordance with the NCPH?s agreed >>>>>>> procedures) on or around 29 April. In light of the need to notify the GNSO >>>>>>> Chair of the result (as under the GNSO Operating Procedures Keith has the >>>>>>> responsibility of notifying the Empowered Community Administration), I >>>>>>> would like to ask *if it will be possible for the NCPH to complete >>>>>>> its vote on a nominee for Board seat 14 by Monday 20 April*, to >>>>>>> allow Keith time to inform the GNSO Council (as has been customary) and to >>>>>>> formally notify the Empowered Community Administration. >>>>>>> >>>>>>> >>>>>>> I and the whole GNSO support team are sincerely sorry for our >>>>>>> previous guidance to you that had mistakenly set 21 May as the final date. >>>>>>> Please accept our heartfelt apologies for this rare error as well as for >>>>>>> the inconvenience that we know our mistake must cause you and your groups. >>>>>>> >>>>>>> >>>>>>> In view of the situation, please be assured that the CSG and NCSG >>>>>>> support staff are happy to assist you with conducting the vote as >>>>>>> efficiently and smoothly as possible, to minimize disruption and >>>>>>> inconvenience to you. Please let me know if you have any questions or >>>>>>> concerns with either the timing or mechanism for the upcoming vote and, >>>>>>> once again, I am so very sorry for the trouble. >>>>>>> >>>>>>> >>>>>>> Thank you all very much for your kind understanding. >>>>>>> >>>>>>> >>>>>>> Best regards, >>>>>>> >>>>>>> Mary >>>>>>> >>>>>>> >>>>>>> _______________________________________________ >>>>>>> NCSG-EC mailing list >>>>>>> NCSG-EC at lists.ncsg.is >>>>>>> https://lists.ncsg.is/mailman/listinfo/ncsg-ec >>>>>>> >>>>>> _______________________________________________ >>>>>> NCSG-EC mailing list >>>>>> NCSG-EC at lists.ncsg.is >>>>>> https://lists.ncsg.is/mailman/listinfo/ncsg-ec >>>>>> >>>>>> >>>>>> _______________________________________________ >>>>>> NCSG-EC mailing list >>>>>> NCSG-EC at lists.ncsg.is >>>>>> https://lists.ncsg.is/mailman/listinfo/ncsg-ec >>>>>> >>>>> _______________________________________________ NCSG-PC mailing list >>> NCSG-PC at lists.ncsg.is https://lists.ncsg.is/mailman/listinfo/ncsg-pc >>> >>> -------------- next part -------------- An HTML attachment was scrubbed... URL: From rafik.dammak at gmail.com Tue Apr 21 02:44:23 2020 From: rafik.dammak at gmail.com (Rafik Dammak) Date: Tue, 21 Apr 2020 08:44:23 +0900 Subject: [NCSG-PC] Reminder PC Chair election / Vice-chairs appointments In-Reply-To: References: Message-ID: Hi all, there were few comments/questions about the proposed process. I didn't see any objection . Adjusting the timeline and the process based on comments. and assuming there is support for the process (edits in red): 1- Nomination period: from 24th April to 1st May Nomination and self-nomination are both permitted from and within PC members (NCSG councillors, NCSG Chair, representatives from NCUC and NPOC to PC), for one year term for PC chair position. The nominee should accept the nomination and send a short SOI by the 1st May. 2- Election : 1st May to 8th May all PC members should vote. the GNSO support staff will act as the election officer. The options in the ballot should be the candidates who confirmed by the deadline and NOTA 3- Result: should be available by 9th May the candidate who get 2/3 vote of the NCSG?PC membership will be declared winner. in case of nobody get the 2/3 vote a second round should be organized with the candidate who get most of votes against NOTA. if the candidate doesn't get 2/3 of votes, a new election process should be initiated asap. 4- Vice-chairs appointments: After PC chair confirmation, a call for interest should be made to have up to 2 vice-chairs. The appointment of the volunteers will be confirmed if there is no objection within PC. 5- the term of PC chair and vice-chairs is 1 year term. if there is no objection we will start this Friday. Best, Rafik Le jeu. 9 avr. 2020 ? 09:11, Rafik Dammak a ?crit : > Hi all, > > following-up (with delay) on one the agreed action items which is the PC > chair election and vice-chairs appointment, I am proposing here a draft > process and timeline. it might sound formal compared to what we discussed > previously but I am using this a draft for building fully fledged process > in future: > > 1- Nomination period: from 17th to 24th April > > Nomination and self-nomination are both permitted from and within PC > members (NCSG councillors, NCSG Chair, representatives from NCUC and NPOC > to PC), for one year term for PC chair position. > The nominee should accept the nomination and send a short SOI by the 24th > April. > > 2- Election : from 27th April to 1st May > > all PC members should vote. the GNSO support staff will act as the > election officer. The options in the ballot should be the candidates who > confirmed by the deadline and NOTA > > 3- Result: should be available by 2nd May > > the candidate who get 2/3 vote of the NCSG?PC membership will be > declared winner. > > 4- Vice-chairs appointments: > > After PC chair confirmation, a call for interest should be made to have up > to 2 vice-chairs. The appointment of the volunteers will be confirmed if > there is no objection within PC. > > > this is just draft process and should be fleshed out to documented for > future. I didn't outline all cases regarding the election for example. > After that, the next step will be to work on job description for those > positions. > > Please let me know your thoughts/comments on what is proposed. > > Best, > > Rafik > > > ---------- Forwarded message --------- > De : Rafik Dammak > Date: lun. 2 mars 2020 ? 09:35 > Subject: NCSG Policy Committee meeting follow-up > To: ncsg-pc > > > Hi all, > > as you know we had last week our PC meeting to discuss several items > regarding election, improvements etc. We got already some action item to > follow-up > > 1- PC chair Election: there was agreement to go with the idea of having > chair and 2 vice-chairs. The point was also to have proper open process > (that can be documented for future). so the action here is to agree on > timeline and process (nomination, vote). it shouldn't be complicated. I > believe we can get this done in this month e.g. 1 week for nomination and 1 > week for voting. > 2- Having a regular PC call, hopefully monthly call and coordinating more > with our NCSG reps to council. The action would be to agree on regular > day/time. I think that can be 2 weeks after NCSG Policy. > 3- Regarding documentation and development of workflow, I believe that can > be done with reworking again on PC operating procedure and documenting > previous activities. I am sharing here the PC operating procedures draft > being worked on before > https://docs.google.com/document/d/1G_M4wBGVEyXm30m79olplfF0RNkJnDwaVBBeldDfO8U/edit . > For anything missing, we can start first to identify that and have > volunteers to draft it. For Chair job description, I can use what I > presented and develop a draft. > 4- Sharing here the slides I presented in last call: > https://docs.google.com/presentation/d/1SnpMYmb6lTw1FqO6tvSqCdpgL-QMg1DJXIJGrx8vB6A/edit#slide=id.p > 5- for NCSG Policy call improvements, we will have the NCSG Policy call in > coming days and I will try to make some adjustments to extent of possible. > It might be shorter than usual as we will have NCSG meeting next week. From > April NCSG Policy call, we can start identifying other topics we would like > to cover other than council meeting and usual policy updates. > > One activity we will need to do soon and follow-up is to work about > prioritization. GNSO Council will discuss the GNSO future work soon and we > need to be ready and align our work around that. That also aligns with the > discussion we had about prioritizing our work and it starts with > identifying what is in the pipeline. > > let me know if I missed anything. > > Best. > > Rafik > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From rafik.dammak at gmail.com Fri Apr 24 18:55:56 2020 From: rafik.dammak at gmail.com (Rafik Dammak) Date: Sat, 25 Apr 2020 00:55:56 +0900 Subject: [NCSG-PC] Reminder PC Chair election / Vice-chairs appointments In-Reply-To: References: Message-ID: Hi all. As there was no objection, the election is starting with nomination period. Best, Rafik On Tue, Apr 21, 2020, 08:44 Rafik Dammak wrote: > Hi all, > > there were few comments/questions about the proposed process. I didn't see > any objection . Adjusting the timeline and the process based on comments. > and assuming there is support for the process (edits in red): > > 1- Nomination period: from 24th April to 1st May > > Nomination and self-nomination are both permitted from and within PC > members (NCSG councillors, NCSG Chair, representatives from NCUC and NPOC > to PC), for one year term for PC chair position. > The nominee should accept the nomination and send a short SOI by the 1st > May. > > 2- Election : 1st May to 8th May > > all PC members should vote. the GNSO support staff will act as the > election officer. The options in the ballot should be the candidates who > confirmed by the deadline and NOTA > > 3- Result: should be available by 9th May > > the candidate who get 2/3 vote of the NCSG?PC membership will be > declared winner. > > in case of nobody get the 2/3 vote a second round should be organized with > the candidate who get most of votes against NOTA. if the candidate doesn't > get 2/3 of votes, a new election process should be initiated asap. > > 4- Vice-chairs appointments: > > After PC chair confirmation, a call for interest should be made to have up > to 2 vice-chairs. The appointment of the volunteers will be confirmed if > there is no objection within PC. > > 5- the term of PC chair and vice-chairs is 1 year term. > > if there is no objection we will start this Friday. > > Best, > > Rafik > > Le jeu. 9 avr. 2020 ? 09:11, Rafik Dammak a > ?crit : > >> Hi all, >> >> following-up (with delay) on one the agreed action items which is the PC >> chair election and vice-chairs appointment, I am proposing here a draft >> process and timeline. it might sound formal compared to what we discussed >> previously but I am using this a draft for building fully fledged process >> in future: >> >> 1- Nomination period: from 17th to 24th April >> >> Nomination and self-nomination are both permitted from and within PC >> members (NCSG councillors, NCSG Chair, representatives from NCUC and NPOC >> to PC), for one year term for PC chair position. >> The nominee should accept the nomination and send a short SOI by the 24th >> April. >> >> 2- Election : from 27th April to 1st May >> >> all PC members should vote. the GNSO support staff will act as the >> election officer. The options in the ballot should be the candidates who >> confirmed by the deadline and NOTA >> >> 3- Result: should be available by 2nd May >> >> the candidate who get 2/3 vote of the NCSG?PC membership will be >> declared winner. >> >> 4- Vice-chairs appointments: >> >> After PC chair confirmation, a call for interest should be made to have >> up to 2 vice-chairs. The appointment of the volunteers will be confirmed if >> there is no objection within PC. >> >> >> this is just draft process and should be fleshed out to documented for >> future. I didn't outline all cases regarding the election for example. >> After that, the next step will be to work on job description for those >> positions. >> >> Please let me know your thoughts/comments on what is proposed. >> >> Best, >> >> Rafik >> >> >> ---------- Forwarded message --------- >> De : Rafik Dammak >> Date: lun. 2 mars 2020 ? 09:35 >> Subject: NCSG Policy Committee meeting follow-up >> To: ncsg-pc >> >> >> Hi all, >> >> as you know we had last week our PC meeting to discuss several items >> regarding election, improvements etc. We got already some action item to >> follow-up >> >> 1- PC chair Election: there was agreement to go with the idea of having >> chair and 2 vice-chairs. The point was also to have proper open process >> (that can be documented for future). so the action here is to agree on >> timeline and process (nomination, vote). it shouldn't be complicated. I >> believe we can get this done in this month e.g. 1 week for nomination and 1 >> week for voting. >> 2- Having a regular PC call, hopefully monthly call and coordinating more >> with our NCSG reps to council. The action would be to agree on regular >> day/time. I think that can be 2 weeks after NCSG Policy. >> 3- Regarding documentation and development of workflow, I believe that >> can be done with reworking again on PC operating procedure and documenting >> previous activities. I am sharing here the PC operating procedures draft >> being worked on before >> https://docs.google.com/document/d/1G_M4wBGVEyXm30m79olplfF0RNkJnDwaVBBeldDfO8U/edit . >> For anything missing, we can start first to identify that and have >> volunteers to draft it. For Chair job description, I can use what I >> presented and develop a draft. >> 4- Sharing here the slides I presented in last call: >> https://docs.google.com/presentation/d/1SnpMYmb6lTw1FqO6tvSqCdpgL-QMg1DJXIJGrx8vB6A/edit#slide=id.p >> 5- for NCSG Policy call improvements, we will have the NCSG Policy call >> in coming days and I will try to make some adjustments to extent of >> possible. It might be shorter than usual as we will have NCSG meeting next >> week. From April NCSG Policy call, we can start identifying other topics we >> would like to cover other than council meeting and usual policy updates. >> >> One activity we will need to do soon and follow-up is to work about >> prioritization. GNSO Council will discuss the GNSO future work soon and we >> need to be ready and align our work around that. That also aligns with the >> discussion we had about prioritizing our work and it starts with >> identifying what is in the pipeline. >> >> let me know if I missed anything. >> >> Best. >> >> Rafik >> >> -------------- next part -------------- An HTML attachment was scrubbed... URL: From rafik.dammak at gmail.com Mon Apr 27 02:35:54 2020 From: rafik.dammak at gmail.com (Rafik Dammak) Date: Mon, 27 Apr 2020 08:35:54 +0900 Subject: [NCSG-PC] [NCSG-Discuss] [Consultation] PIR Transaction and Proposed Public Interest Commitments Update In-Reply-To: References: <1134142044748.1122025845763.1521253088.0.711100JL.2002@scheduler.constantcontact.com> <11CE170D-5897-424C-BE73-090F1016BE03@icann.org> <20200414145555.Horde.ZryOSs7ES2rEDNmraokEKm_@a2plcpnl0836.prod.iad2.secureserver.net> <20200415061845.Horde.av7LkyXqOGutJdfH2T-eJsd@a2plcpnl0836.prod.iad2.secureserver.net> Message-ID: hi all, we are quite late for this. ICANN extended the period for its review so we can still submit/send our statement. please review. Best, Rafik Le jeu. 16 avr. 2020 ? 09:22, Rafik Dammak a ?crit : > hi all, > > this requires an urgent and swift response from PC. we have a thread > regarding this short consultation from ICANN regarding .org sale and the > proposed PICs. > based on comments shared in the list, Bruna quickly drafted the statement > below. > please review ! > > Best, > Rafik > ---------- Forwarded message --------- > De : Bruna Martins dos Santos > Date: jeu. 16 avr. 2020 ? 06:27 > Subject: Re: [NCSG-Discuss] [Consultation] PIR Transaction and Proposed > Public Interest Commitments Update > To: > > > Dear all, > > Putting together some of the comments on this list, this is what the NCSG > "comment" looks like: > > Pad: https://pad.codingrights.org/p/NCSGCommentPIR > ------- > > *NCSG Statement on the "PIR Transaction and Proposed Public Interest > Commitments Update"* > > Back in november 2011, the Noncommercial Stakeholders Group issued a > letter to the ICANN Board advocating for Ethos Capital to uphold its > previously acquired obligations with regards to noncommercial registrants. > The letter also pointed out that it was ICANN's duty to to enter into > negotiations with Ethos Capital to ensure that its operation of the ORG > domain conforms to criteria upon which the original award of ORG was > contingent (related to noncommercial registrants). > > *Lack of a Freedom of Expression related provision on the PIC* > Due to concerns regarding eventual restrictions to rights such as Freedom > of Expression, NCSG asked that the PIC text included both a > process-oriented commitment to allow the Org Stewardship Council to veto > ?modifications? of RO?s policies pertaining to free expression and a > positive commitment to ensuring rights such as freedom of expression in the > .Org domain. Despite stating this point previously in statements and to the > PIR Leadership team, the lack of mention to this request on the modified > PIC makes it harder for us to fully support the revised document. > > *Extended registration terms for .org registrants * > With regards to the possible extension of registration terms for .org > registrants this was also a topic in which NCSG pointed out the need for a > stronger PIR commitment. Despite understanding the eventual policy changes > entailed by the proposed change, we would like to, once again, state the > need for a sronger PIR involvement in creating such a change. > > *Org Stewardship Council * > We would like to also offer our concerns with regards to the proposed > stewardship council. NCSG understands that the OSC must be able to present > a counter point or even oppose to policy implementations on behalf of PIR. > Foreseeing the possible issues with the implementation of policies such as > the PIR Anti-Abuse Policy that allows PIR ?to comply with any applicable > laws, government rules or requirements, requests of law enforcement, or any > dispute resolutio process" we would like to note the importance of an > independent OSC able to express powers to examine difficult issues of > jurisdiction and protect free expression for organizations and individuals > engaged in political debates. > > Another possible issue listed on the same policy is the discussion of > ?trusted notifiers? as a type of fast-track method of reporting and taking > down domain names with disliked content. In order for this provision to > happen in an adequate manner we must ensure that the OSC composition also > have experts in topics such as Freedom of Expression, Free Speech and Human > rights. These experts must have deep substantive legal and policy > background and ability to independently research and expertly comment on > substantive and procedural issues brought before them by Ethos/PIR. > > > *OSC Representation and NCSG participation* > NCSG also informed the PIR leadership the need for more independence on > the proposed ORG Stewardship Council (OSC). Despite being a point that was > mentioned on the new PICs and PIR statements, we believe the proposed > process could still be improved. Specifically, they say ?The PIR Board > will not appoint the first five members of the .ORG Stewardship Council. To > ensure independence, Ethos will engage an internationally-recognized > executive search firm to oversee and manage a process for identifying > candidates to be the inaugural members. The search firm will solicit > applications from a variety of .ORG Stakeholders, including ICANN?s > Non-Commercial Stakeholder Group (NCSG) and At-Large Advisory Committee > (ALAC) and provide its proposed nominations to a Selection Committee > established by the PIR Board.?. > > When it comes to the ORG Stewardship Council representatives, we would > like to state the following: > > (a) From what it seems, even with the new proposed selection process, PIR > will still be responsbible for selecting all the OSC members. Additionally, > despite the mention to NCSG on the document, there are no guarantees that > the selection committee nor PIR will ensure NCSGs participation on the OSC. > We also must note that ALAC contains, and to some extent is more > representative of, commercial users as well as noncommercial users and has > no historical connection to the ORG domain; > (b) PIR and Ethos Capital should ensure that the OSC members include > include multiple and well-known experts in free speech and freedom of > expression, human rights, copyright/trademark/fair use. Also, as pointed > above, it is of utter importance that the selected appointees hold the same > compromise with ensuring that the registry keeps its allignment with the > Noncommercial registrants. > > > Le mer. 15 avr. 2020 ? 17:08, Peter Micek a ?crit : > >> Hi all, >> >> I fully support a comment by NCSG. Access Now are just finalizing ours, >> I'll paste a draft below. I support holding them to account for their >> promise of clarity on the selection process, but as you can see, I feel >> that committee is more like a deck chair arrangement than hand on the >> ship's tiller. >> >> Best, >> Peter >> >> >> >> >> >> >> *In Access Now?s last letter >> to ICANN, we >> outlined some of the many reasons why the proposed Public Interest >> Commitments (PICs) would in no way be sufficient to hold PIR ? and Ethos >> Capital as its controlling investor ? accountable to the .ORG community or >> to ensure the needs and interests of those who rely on .ORG are protected. >> The several adjustments Ethos has made to its proposal since we wrote that >> letter are not significant and do not change our position.ICANN has an >> important opportunity to restore the .ORG community?s confidence, and to do >> its part in protecting online civic space ? which is already under attack >> all around the world. It can do that by taking the following steps:Extend >> the public comment period. If ICANN is serious about getting meaningful >> input from the community on the current proposal, a seven-day comment >> period isn?t enough. At a minimum ICANN needs to allow its standard 30-day >> window for comments, especially considering the additional strain civil >> society around the world is burdening under the ongoing COVID-19 crisis. >> This falls in line with guidance >> >> from the UN special rapporteur on the freedom of assembly, that >> ?multilateral institutions should take steps to ensure civil society >> organizations can continue to participate in all policy decisions, >> including those related to the Covid-19 response, especially in the case of >> public-private partnerships.? That ICANN is multi-stakeholder, not >> multilateral (like the UN), only adds to its responsibility to meaningfully >> consult civil society.Negotiate an extension with PIR and Ethos.ICANN is >> rushing to get in public comments in just seven days, with only two working >> days to process the results ahead of their April 20th deadline for deciding >> .ORG?s future. Further, ICANN is still waiting for responses >> >> from Ethos to many very important questions (covering issues like PIR?s >> financial solvency, avenues for community input going forward, and who >> would actually be in control of PIR across the several holding companies >> involved in the transaction). Getting the information they need both from >> Ethos and the community is essential to the long-term sustainability of >> .ORG, and ICANN should insist on more time to make this decision.Withhold >> consent to the transfer of control of .ORG.Even without extended comment >> periods and additional information, though, ICANN already has all it needs >> to reject this deal. Simply put, this is an underhanded and dangerous deal >> that puts all of us at risk, and ICANN should stop it. After several rounds >> of empty concessions from Ethos, and their continued failure to produce >> essential information about how the deal is structured, it is very clear >> that there is no path to redeeming this sale.Lead a community consultation >> on the future of .ORG.ICANN should provide an inclusive, substantive, >> community-driven venue for discussing a viable path forward for .ORG. If >> ISOC no longer has an interest in being a steward for the domain, it is >> essential that we can collectively identify a new solution that ? first and >> foremost ? meets the needs of the .ORG community, now and in the future.* >> >> On Wed, Apr 15, 2020 at 9:20 AM wrote: >> >>> Raphael, >>> Tx for your comments. You'll note my comments/points reference both >>> free speech (law where .ORG has been based for 34 years, and of its >>> proposed upcoming owners) and free expression (referencing Article 19 >>> of the UN Declaration of Human Rights). It is the language of both >>> sets of laws, and expertise in both, that I advise in points 1 and 3 >>> below. >>> >>> I can't imagine how that would be controversial -- there are people >>> who are experts on protecting free expression around the world -- and >>> if this controversial sale goes through, we will need them here. It's >>> hard to hold your ground in complex circumstances (against private >>> corporate attorneys) if you are not an expert -- we want people who >>> know the precedent and the laws and protections around the world. Glad >>> you like the second proposition! >>> >>> In all events, our NCSG voice needs to be heard here. Bruna offered >>> to prepare a quick comment -- I think we we should move forward. Time >>> is of the essence! >>> >>> Best, Kathy >>> >>> Quoting Raphael Beauregard-Lacroix : >>> >>> > I think we have some materials for a comment, but are lacking a few >>> more >>> > days to put things together. Not only is that 7 days too short, but >>> > blogpost comments are not quite appropriate either to say the least. >>> Given >>> > the unanimity of those who commented on the blogpost, we can hope they >>> will >>> > change their mind (and we can individually join such request for a >>> standard >>> > public comment period. >>> > >>> > As for the substance of our comment, I find myself closer to Milton's >>> > propositions. Kathy, I think your first and third proposition are >>> difficult >>> > to work out in practice without enunciating what the base line is >>> supposed >>> > to be - I understand it would be the US (i.e. assuming jurisdiction, >>> PIR >>> > should not comply with requests which could not validly be made under >>> US >>> > law by a US entity) I have difficulties with that position as it puts >>> US >>> > free speech law on a pedestal and means committee members must be >>> immersed >>> > in the US understanding of free speech. Globally, with its extremely >>> high >>> > thresholds before the government can directly regulate speech, the US >>> rides >>> > alone. >>> > >>> > But the problem is not solved by choosing any other law, or some sort >>> of >>> > generic transnational mix of "free speech best practices" as a strict >>> set >>> > of legal rules. I get your worry that PIR will comply with any law >>> > enforcement order it receives, bogus and legitimate alike, for business >>> > reasons. I guess the domain name industry is not in a position to make >>> the >>> > very brazen move to apply US speech regulation threholds to all their >>> > customers... Nor even to do so with a slightly watered down best >>> practices. >>> > While that's not new, I still think we can ask for PIR to do better >>> than >>> > others. But the choice they would be facing is jeopardizing their >>> business >>> > (or their finances, eventually) in the name of values. >>> > >>> > Hence the language that Milton suggests, a written commitment to a more >>> > general value and ensuring that members of the committee come from >>> diverse >>> > civil society background, is, I find, more likely to find a broader >>> appeal >>> > among our community and the ICANN/dot org community in general. Public >>> > opinion and community pressure (stirred by a vigilant council) might >>> be a >>> > better safeguard against opportunistic or otherwise undesirable >>> behavior by >>> > PIR with regards to LEA requests than some sort of inbedded court of >>> review >>> > with an ad-hoc set of very binding but still very vague rules. >>> > >>> > Your second proposition seems fine as is! We can legitimately request >>> that >>> > trusted notifiers be actually neutral and not a IP >>> > rightsholders association... >>> > >>> > have a nice evening, >>> > >>> > On Tue, Apr 14, 2020 at 5:57 PM wrote: >>> > >>> >> To Milton's proposed comments below, I offer key substantive changes >>> >> -- otherwise I fear the Stewardship Council will be completely >>> >> bypassed by Ethos and PIR. >>> >> >>> >> Specifically: >>> >> >>> >> Powers of the Stewardship Council must allow it to strongly, clearly >>> >> and with authority support (or oppose) Ethos/PIR LLC's implementation >>> >> of PIR's Anti-Abuse Policy. >>> >> >>> >> Background: In October 2019, the then-new PIR President Jon Nevett >>> >> announced a PIR Anti-Abuse Policy that allows PIR ?to comply with any >>> >> applicable laws, government rules or requirements, requests of law >>> >> enforcement, or any dispute resolution process.? >>> >> https://thenew.org/doing-our-part-for-a-safer-stronger-dns/ The >>> >> Stewardship Council -- to protect free speech and free expression in >>> >> .ORG -- *must* have the ability to oversee (and veto) Ethos/PIR's >>> >> interpretation and implementation of the PIR Anti-Abuse Policy. >>> >> Otherwise, it cannot protect .ORG registrants against censorship. >>> >> >>> >> Concern 1: The Anti-Abuse Policy commits PIR to responses to >>> >> "requests of law enforcement" without stating whether the law >>> >> enforcement requests must come from a law enforcement agency with >>> >> jurisdiction over the registry, registrar or registrant. Is the >>> >> request for takedown of speech even legal in the country in which the >>> >> speech originated? Is the speech perhaps purposely and intentionally >>> >> directed to expose corruption or malfeasance of a national government >>> >> or official who has stepped beyond their authority and law? >>> >> >>> >> **Accordingly, the Stewardship Council must have express powers to >>> >> examine difficult issues of jurisdiction and protect free expression >>> >> for organizations and individuals engaged in political debates. >>> >> >>> >> Concern 2: The PIR Anti-Abuse policy discusses ?trusted notifiers? as >>> >> a type of fast-track method of reporting and taking down domain names >>> >> with disliked content. Recent PIR President Jon Nevett, when he was >>> >> General Counsel/VP of Donuts, paired up with controversial ?trusted >>> >> notifier? the Motion Picture Association (MPAA), >>> >> >>> >> >>> https://www.multichannel.com/news/mpaa-donuts-team-takedown-best-practice-402440 >>> >> The MPAA is not known for its neutrality or fairness in its >>> accusations, >>> >> see e.g., >>> >> >>> https://www.brainz.org/14-most-ridiculous-lawsuits-filed-riaa-and-mpaa/ >>> >> >>> >> ** Accordingly, the Stewardship Council must be able to review all >>> >> ?trusted notifiers? and veto those that are not genuinely fair and >>> >> neutral and will not genuinely protect free speech and free >>> >> expression, including legitimate critique and legal fair use. >>> >> >>> >> Problem 3: Nice people on the Stewardship Council without deep >>> >> expertise in free speech, free expression, human rights, privacy and >>> >> relate laws can be easily captured by Ethos/PIR?s own research and >>> >> reasoning. >>> >> >>> >> ** Accordingly, all Stewardship Councils must include *multiple and >>> >> well-known experts in free speech and free expression, human rights, >>> >> copyright/trademark/fair use.* These experts must have deep >>> >> substantive legal and policy background and ability to independently >>> >> research and expertly comment on substantive and procedural issues >>> >> brought before them by Ethos/PIR. >>> >> >>> >> Best, Kathy >>> >> >>> >> Quoting "Mueller, Milton L" : >>> >> >>> >> > Rafik: >>> >> > Thanks for your initiative. NCSG must comment on this. We are being >>> >> > derelict in our duties to represent noncommercial users if we don?t. >>> >> > >>> >> > I may not be up to date about this, but one important issue still >>> >> > seems to be unresolved. In its commitment to amend the PIC in a way >>> >> > that would satisfy the concerns of noncommercial registrants, PIR >>> >> > wrote that ?he search firm and nomination criteria process will be >>> >> > announced on March 23, 2020.? Has that been done? If so, I don?t >>> >> > know where it is. >>> >> > >>> >> > Some comments about the modified PIC that could be used as is or >>> >> > incorporated into a NCSG comment. >>> >> > >>> >> > >>> >> > 1. We had asked that the PIC text include not just a >>> >> > process-oriented commitment to allow the Org Stewardship Council to >>> >> > veto ?modifications? of RO?s policies pertaining to free expression, >>> >> > but a positive commitment to fostering freedom of expression in the >>> >> > .Org domain. The CEO of Org seemed to express a favorable view of >>> >> > that request in a public consultation. The modified PIC contains no >>> >> > such modification. This is disappointing, and makes it impossible >>> >> > for us to fully support the revised PIC. >>> >> > >>> >> > 2. We had also asked for PIR to express a stronger commitment >>> >> > to extending registration terms for org registrants. While we >>> >> > understand that extending registration terms requires a policy >>> >> > change, we were hoping for a statement that PIR would join in >>> >> > efforts to create such a change. The modified PIC contains no such >>> >> > commitment. >>> >> > >>> >> > 3. We informed PIR that the ORG Stewardship Council (OSC) >>> >> > needed to be more independent of PIR. The new PICs and PIR >>> >> > statements have been partially responsive to that request, but still >>> >> > fall short. Specifically, they say ?The PIR Board will not appoint >>> >> > the first five members of the .ORG Stewardship Council. To ensure >>> >> > independence, Ethos will engage an internationally-recognized >>> >> > executive search firm to oversee and manage a process for >>> >> > identifying candidates to be the inaugural members. The search firm >>> >> > will solicit applications from a variety of .ORG Stakeholders, >>> >> > including ICANN?s Non-Commercial Stakeholder Group (NCSG) and >>> >> > At-Large Advisory Committee (ALAC) and provide its proposed >>> >> > nominations to a Selection Committee established by the PIR Board.? >>> >> > Clearly, in this process PIR will still select all the OSC members. >>> >> > While the solicitation of applications specifically mentions NCSG, >>> >> > there is no guaranteed representation from NCSG on the OSC. We also >>> >> > must note that ALAC contains, and to some extent is more >>> >> > representative of, commercial users as well as noncommercial users >>> >> > and has no historical connection to the ORG domain. >>> >> > >>> >> > From: NCSG-Discuss On Behalf Of >>> Rafik >>> >> Dammak >>> >> > Sent: Monday, April 13, 2020 7:25 PM >>> >> > To: NCSG-DISCUSS at LISTSERV.SYR.EDU >>> >> > Subject: Re: [Consultation] PIR Transaction and Proposed Public >>> >> > Interest Commitments Update >>> >> > >>> >> > hi all, >>> >> > >>> >> > resending this to ask if there is anything we would like to comment >>> >> > regarding .org proposed PICs. >>> >> > >>> >> > Best, >>> >> > >>> >> > Rafik >>> >> > >>> >> > Le ven. 10 avr. 2020 ? 08:30, Rafik Dammak >>> >> > > a ?crit : >>> >> > Hi all, >>> >> > >>> >> > there is an update related to PIR and ,org sale with regard to >>> >> > communication between PIR and ICANN, and the matter of PIC (Public >>> >> > Interest Commitments). As ICANN has to make decision within the >>> >> > timeline regarding the change on control of PIR , it is asking the >>> >> > community to provide feedback regarding the proposed PICs. it won't >>> >> > be through usual public comment but either by responding as comment >>> >> > to the blog (unusual) or sending letter to the board. >>> >> > >>> >> > As this topic is of interest to NCSG and it is an opportunity to >>> >> > share comments on the PIC, we should draft a letter quickly and send >>> >> > it as correspondence to boars. For more information you can check >>> >> > the blog post here >>> >> > >>> >> >>> https://www.icann.org/news/blog/pir-transaction-and-proposed-public-interest-commitments-update >>> >> or >>> >> > below. >>> >> > >>> >> > Best regards, >>> >> > >>> >> > Rafik >>> >> > >>> >> > ---------- Forwarded message --------- >>> >> > De : Michelle DeSmyter >>> >> > > >>> >> > Date: ven. 10 avr. 2020 ? 00:02 >>> >> > Subject: [council] FYI: [ICANN Community Leaders] 9 April 2020 >>> >> > To: GNSO Council List >> >> council at gnso.icann.org>> >>> >> > Cc: gnso-secs at icann.org >>> >> > > >>> >> > >>> >> > >>> >> > FYI: >>> >> > [Image removed by sender.] >>> >> > Thursday, 9 April 2020 >>> >> > >>> >> > ICANN Community Leadership Digest >>> >> > >>> >> > [Image removed by sender.] >>> >> > >>> >> > The ICANN org Policy Development Support function publishes this >>> >> > twice-weekly digest >>> >> > to help ICANN community leaders track requests and follow updates. >>> >> > >>> >> > Table of Contents >>> >> > >>> >> > Information Sharing >>> >> > ? NEW: PIR Transaction and Proposed Public Interest Commitments >>> >> Update >>> >> > ? NEW: Addressing Recent Zoom News >>> >> > ? ENDS TOMORROW: Your Feedback about this Digest >>> >> > ? REMINDER: Call for Expressions of Interest: Standing Panel for >>> >> > ICANN?s Independent Review Process >>> >> > Public Comment >>> >> > ? CLOSES MONDAY: Revised Community Travel Support Guidelines >>> >> > ? Proposal for Chinese Script Root Zone Label Generation Rules >>> >> > ? Proposal for Bangla Script Root Zone Label Generation Rules >>> >> > ? Phase 1 Initial Report of the Review of All Rights Protection >>> >> > Mechanisms in All gTLDs Policy Development Process >>> >> > ? Addendum to the Initial Report of the Expedited Policy >>> >> > Development Process (EPDP) on the Temporary Specification for gTLD >>> >> > Registration Data Team ? Phase 2 >>> >> > ? Guidelines for Developing Reference Label Generation Rules >>> >> > (LGRs) for the Second Level Version 2 >>> >> > >>> >> > >>> >> > >>> >> > Information Sharing >>> >> > >>> >> > NEW: PIR Transaction and Proposed Public Interest Commitments Update >>> >> > Executive: G?ran Marby, ICANN President and CEO >>> >> > >>> >> > Since Public Interest Registry (PIR) formally notified ICANN of the >>> >> > proposed change of control transaction on 14 November 2019 >>> >> > [r20.rs6.net]< >>> >> >>> https://urldefense.proofpoint.com/v2/url?u=http-3A__r20.rs6.net_tn.jsp-3Ff-3D001ksZaHYpLxs73N74vLz88Vq0p2eY7hNPIUETQItxPS1zFOkKdqUiWFt-2DqViuZxFtMbojNo0l3-5FANH24DHECSiWoBxsLSaqGlloXx-5FUcAwJwakeQ9Zmj6QVbLPEgY1YoMQ30XcWD0EfoICTUD3fQsUgTRutD1d4E9y-2D5LUMBGXHzz5KkRxQtTHxwFk0xJWQ0E5Dc20U-2DqwV-5FjHI6W5uMb0IMvlWR-2D5vUUlNlzJnBCaG0Q-3D-26c-3Dwy9XJGNosEnEjdPoYLdJwvuIgsRRZOESZYkznmQPNTaHtmURx3UpcA-3D-3D-26ch-3D3Nfh4df3oGcxggBTYNdpswIf0un3QheyxW0pkf2jmeEOezCq3E9Zxg-3D-3D&d=DwMFaQ&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=8_WhWIPqsLT6TmF1Zmyci866vcPSFO4VShFqESGe_5iHWGlBLwwwehFBfjrsjWv9&m=Lr1oOkYZ9081GhqSfAb5smovhT1n5h6sykrEY1gEbF0&s=mLXHpNOHqUpl4b9smtPPhoUEZkfXME5gylo_YK5fpHA&e= >>> >, >>> >> the ICANN org and Board have worked together to thoughtfully and >>> thoroughly >>> >> evaluate the proposed acquisition to ensure that the .ORG registry >>> remains >>> >> secure, reliable, and stable. Throughout this process, ICANN has >>> urged PIR, >>> >> the Internet Society (ISOC), and Ethos Capital (Ethos) to engage and >>> >> consult with the .ORG community, and to provide full transparency >>> regarding >>> >> the proposed >>> >> > transaction. >>> >> > >>> >> > Today, ICANN is publishing >>> >> > [r20.rs6.net]< >>> >> >>> https://urldefense.proofpoint.com/v2/url?u=http-3A__r20.rs6.net_tn.jsp-3Ff-3D001ksZaHYpLxs73N74vLz88Vq0p2eY7hNPIUETQItxPS1zFOkKdqUiWFt-2DqViuZxFtMjl-2DLfzT9kl16ErkR6z6u2dnFIk8nbt5udOqVrVKLsftd1T8OPz2mml3-2DC-2DH7IAjX29PnKBS-5FBmWKWgICCjqgyzR4c8NWnenXlseFPEKyVB16RneWbnmGzb0G1T7WZWmhO-2DJA9b67bhA0s30fnk2HieXDOgw9WXF6u-5FntnNq2sjl-2DbfHRdB-5F-5FCg-3D-3D-26c-3Dwy9XJGNosEnEjdPoYLdJwvuIgsRRZOESZYkznmQPNTaHtmURx3UpcA-3D-3D-26ch-3D3Nfh4df3oGcxggBTYNdpswIf0un3QheyxW0pkf2jmeEOezCq3E9Zxg-3D-3D&d=DwMFaQ&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=8_WhWIPqsLT6TmF1Zmyci866vcPSFO4VShFqESGe_5iHWGlBLwwwehFBfjrsjWv9&m=Lr1oOkYZ9081GhqSfAb5smovhT1n5h6sykrEY1gEbF0&s=ts4XYR8T3ZJT4y-6SxsLyD1y4BIj0BUeGrarBKdExLU&e= >>> > >>> >> PIR's recently updated Public Interest Commitments (PICs), which were >>> >> received by ICANN on 7 April 2020. PIR proposes that these PICs be >>> added to >>> >> the .< >>> >> >>> http://r20.rs6.net/tn.jsp?f=001ksZaHYpLxs73N74vLz88Vq0p2eY7hNPIUETQItxPS1zFOkKdqUiWFt-qViuZxFtMMIlnB_968dbzElej_FsRAoGq9Eqxvee5Q_KV5Ct9-uvF3B31UTR6Pun8VJszaEAlzU4xxfVyba-mp3rK4vMyrYD5X7zBxTYL-Y2bodULglcmjvrcd2FKT5ZvSFm834cHPq-Lo-SHUpaAa10pknkz_QmRkfJzm_COPRwJcwnEAZIq0fVsl5mIrAuPWKCpT_0bS9JLJoOeypYS3lYOf8USOG9-Lnbs0VPbBZvw6z7abI16KnPdxcAd8ilswdLQVIKP58l2duFHIEfp_5jKkTmexLuak03kILHIa569s8HYm2jzhPYFwc30tXVW7a89Hu-2JoexXh6ZHsF4Ly5aM9lr3oG1z5LFmgsIBEZuu4ZtvCdXnl3JIDWTLsCvY5gP8VaKpDf_sU5EVVKYmg9DuNkuIpPYMB4w6Knz3koBfDS71iKx_MiXAc-a4n0KRH04OAFSnK9SoDHcro7hFDPzd-y_oY-NdPKWVWBy43QVOxGMzUxgS0TgrW6gmetCRBpI_TDSU62AMXlzBng-VsqHgkUvtQ==&c=wy9XJGNosEnEjdPoYLdJwvuIgsRRZOESZYkznmQPNTaHtmURx3UpcA==&ch=3Nfh4df3oGcxggBTYNdpswIf0un3QheyxW0pkf2jmeEOezCq3E9Zxg== >>> >ORG >>> >> Registry Agreement [r20.rs6.net]< >>> >> >>> https://urldefense.proofpoint.com/v2/url?u=http-3A__r20.rs6.net_tn.jsp-3Ff-3D001ksZaHYpLxs73N74vLz88Vq0p2eY7hNPIUETQItxPS1zFOkKdqUiWFt-2DqViuZxFtMt8ZrQ-5FUUDPTpBScWUeesMbPDgtiEx9JsqUZ2RBBSmfuo3amjba4h6H0FCK6sF6ZzI563CxHXZiQNwwMvlhv1A-5FqJiOclOyojun5IxJ71bhFSHVpJ8RCrubAItweNsQgV39EXBLH9hvA-3D-26c-3Dwy9XJGNosEnEjdPoYLdJwvuIgsRRZOESZYkznmQPNTaHtmURx3UpcA-3D-3D-26ch-3D3Nfh4df3oGcxggBTYNdpswIf0un3QheyxW0pkf2jmeEOezCq3E9Zxg-3D-3D&d=DwMFaQ&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=8_WhWIPqsLT6TmF1Zmyci866vcPSFO4VShFqESGe_5iHWGlBLwwwehFBfjrsjWv9&m=Lr1oOkYZ9081GhqSfAb5smovhT1n5h6sykrEY1gEbF0&s=PFZv7yhgsFMq0lzJYXDEZdNlTGoZ4scsPzhlOXouNvA&e= >>> >should >>> >> ICANN approve the change of control request submitted by PIR. Two >>> versions >>> >> of the PICs are being published: a "clean [r20.rs6.net]< >>> >> >>> https://urldefense.proofpoint.com/v2/url?u=http-3A__r20.rs6.net_tn.jsp-3Ff-3D001ksZaHYpLxs73N74vLz88Vq0p2eY7hNPIUETQItxPS1zFOkKdqUiWFt-2DqViuZxFtMPkg-5FIhS82AYz2s0agDU9ankQXLYTjJeksRZN597OYN1pXU7CA-2DizP91h-2DCxUrMPyE581jkJBcMq5gWufSkDdhOW2M-2DkMl3vUtj4urTtIr99h-5FkiqRZTERHDJtge9P-5Fz5WerwaZluwmVlaNURyQf-2DAvXUwzYPpFr-5FYvXFhHORQWqTP5NK7uD3-5Fg-3D-3D-26c-3Dwy9XJGNosEnEjdPoYLdJwvuIgsRRZOESZYkznmQPNTaHtmURx3UpcA-3D-3D-26ch-3D3Nfh4df3oGcxggBTYNdpswIf0un3QheyxW0pkf2jmeEOezCq3E9Zxg-3D-3D&d=DwMFaQ&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=8_WhWIPqsLT6TmF1Zmyci866vcPSFO4VShFqESGe_5iHWGlBLwwwehFBfjrsjWv9&m=Lr1oOkYZ9081GhqSfAb5smovhT1n5h6sykrEY1gEbF0&s=yrlvXk8vaOH9RSyqAuJb1YP_VxI3vFuz6Yyo4WxRdkc&e= >>> >" >>> >> version and a "redline [r20.rs6.net]< >>> >> >>> https://urldefense.proofpoint.com/v2/url?u=http-3A__r20.rs6.net_tn.jsp-3Ff-3D001ksZaHYpLxs73N74vLz88Vq0p2eY7hNPIUETQItxPS1zFOkKdqUiWFt-2DqViuZxFtM2NGnW2TWIbAuSn-5Fra-2DV40EhKb8SQVrjtcMLlKR3PwRnjHjXMd-5FJWOT4i6SC-5FtTb-5FuTMBKCjdgG-5FAnOVMddwuP-5F-2DZMTcbzNklSTp6b1EE960w0cwLdtSoQOXwcvOfLoT1zI-2DzoNWdc4nTxw5lQIXMfgZyb5cgQbeVhbscHVmg5otVtAqawVBTSLJaHeGb7Xy2-26c-3Dwy9XJGNosEnEjdPoYLdJwvuIgsRRZOESZYkznmQPNTaHtmURx3UpcA-3D-3D-26ch-3D3Nfh4df3oGcxggBTYNdpswIf0un3QheyxW0pkf2jmeEOezCq3E9Zxg-3D-3D&d=DwMFaQ&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=8_WhWIPqsLT6TmF1Zmyci866vcPSFO4VShFqESGe_5iHWGlBLwwwehFBfjrsjWv9&m=Lr1oOkYZ9081GhqSfAb5smovhT1n5h6sykrEY1gEbF0&s=L2bmKUr5EWBlGGQCZOhCeVTqRJu6SEUQgFgHIAjmJ1M&e= >>> >" >>> >> version that shows changes made by PIR from its 16 March 2020 version >>> >> submitted to ICANN following PIR's Public Engagement process. >>> >> > [r20.rs6.net]< >>> >> >>> https://urldefense.proofpoint.com/v2/url?u=http-3A__r20.rs6.net_tn.jsp-3Ff-3D001ksZaHYpLxs73N74vLz88Vq0p2eY7hNPIUETQItxPS1zFOkKdqUiWFt-2DqViuZxFtM1ecPoHkp0Qu90ued5Lbmf3r3DQM-2DRewknXnd2HMqbj-2DaC7vftx82qbFD6UixhfAJk6asLfO5ZiM5vpvaysPdcYLV2k7nAGJHjgvpt54cmoCnd2VcNM43hg-3D-3D-26c-3Dwy9XJGNosEnEjdPoYLdJwvuIgsRRZOESZYkznmQPNTaHtmURx3UpcA-3D-3D-26ch-3D3Nfh4df3oGcxggBTYNdpswIf0un3QheyxW0pkf2jmeEOezCq3E9Zxg-3D-3D&d=DwMFaQ&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=8_WhWIPqsLT6TmF1Zmyci866vcPSFO4VShFqESGe_5iHWGlBLwwwehFBfjrsjWv9&m=Lr1oOkYZ9081GhqSfAb5smovhT1n5h6sykrEY1gEbF0&s=ANKFOin7HLmMPYHXq1AFPnYmvexcAakJovbMGTdQr8A&e= >>> >> > >>> >> > >>> >> > The revised PICs that ICANN is publishing today are in response to >>> >> > additional questions posed by ICANN as part of its diligence around >>> >> > the change of control request. On 3 April 2020, ICANN provided PIR >>> >> > with two sets of questions. One set of questions are in follow-up to >>> >> > previous ICANN inquiries designed to further understand the proposed >>> >> > transaction and its potential effect on PIR and the .ORG top-level >>> >> > domain (TLD). The second set of questions relate specifically to the >>> >> > proposed PICs. PIR has indicated that it is working to answer all of >>> >> > the questions from ICANN. >>> >> > >>> >> > It is ICANN's intention to post PIR's responses to these questions >>> >> > when they are available, subject to any appropriate requests for >>> >> > confidentiality made by PIR. >>> >> > >>> >> > Many people have questioned the enforceability of PICs by ICANN. To >>> >> > be clear, PICs are enforceable by ICANN. Any Internet user may >>> >> > submit complaints to ICANN Contractual Compliance. In addition, >>> >> > ICANN Contractual Compliance may identify an issue through its >>> >> > proactive monitoring. ICANN's follow-up questions to PIR seek to >>> >> > ensure that ICANN has a clear understanding of each commitment >>> >> > within the PICs, such that it could be enforced should the need >>> >> > arise. The ICANN Board continues to have reservations regarding the >>> >> > enforceability of PIR's proposed PICs. >>> >> > >>> >> > The .ORG Registry Agreement stipulates a specified time period for >>> >> > ICANN to approve or withhold consent of the proposed change of >>> >> > control of PIR. ICANN and PIR have agreed to extend the deadline >>> >> > several times since the original deadline in mid-January, and the >>> >> > deadline for ICANN's response is now 20 April 2020. >>> >> > >>> >> > Similar to when voluntary commitments in the form of PICs were >>> >> > proposed by applicants for new generic TLDs, ICANN is providing >>> >> > PIR's proposed PICs to the ICANN community with this public notice. >>> >> > Given the fast-approaching deadline for ICANN to make a decision to >>> >> > approve or withhold consent on the requested change of control of >>> >> > PIR, the typical 30-day public notice period has been condensed to >>> >> > seven days. We recognize the full engagement of the .ORG community >>> >> > in PIR's consultation process, but wanted to ensure ICANN remained >>> >> > fully transparent in what is being considered, the concerns still >>> >> > present in the Board's review, and what the Board will be reviewing. >>> >> > >>> >> > How to Participate: Feedback may be submitted as a comment to this >>> >> > blog >>> >> > [r20.rs6.net]< >>> >> >>> https://urldefense.proofpoint.com/v2/url?u=http-3A__r20.rs6.net_tn.jsp-3Ff-3D001ksZaHYpLxs73N74vLz88Vq0p2eY7hNPIUETQItxPS1zFOkKdqUiWFt-2DqViuZxFtMlCsaRdGZCZWr6aGU7qSTQtpUsX57iyMIgI8JJa96lU54JNF3m0f3uwiK5VBqZGvI76JFMJ2xpZj-5FzGN7OihHOFJm5gB4DU1i7ZfKQR5gT36asgmsO8S0kradGtN09wQ0WCwZLgYbr-5F5OrqP-5F5rE8mBR-2DqBQzg-5FCJ1NMSJx02GVq7aag0yuegdg-3D-3D-26c-3Dwy9XJGNosEnEjdPoYLdJwvuIgsRRZOESZYkznmQPNTaHtmURx3UpcA-3D-3D-26ch-3D3Nfh4df3oGcxggBTYNdpswIf0un3QheyxW0pkf2jmeEOezCq3E9Zxg-3D-3D&d=DwMFaQ&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=8_WhWIPqsLT6TmF1Zmyci866vcPSFO4VShFqESGe_5iHWGlBLwwwehFBfjrsjWv9&m=Lr1oOkYZ9081GhqSfAb5smovhT1n5h6sykrEY1gEbF0&s=IWPBCoMxSRD7G3awtw0MQUJ1KUg5OrIsYh5MhUj_Jvk&e= >>> > >>> >> or through correspondence to me or the ICANN >>> >> > Board. >>> >> > >>> >> > We thank the ICANN community for its active participation in this >>> >> > matter and remain committed to keeping you informed of new >>> >> > developments. >>> >> > >>> >> > >>> >> > >>> >> > NEW: Addressing Recent Zoom News >>> >> > Executive: Ashwin Rangan, Senior Vice President, Engineering and >>> >> > Chief Information Officer >>> >> > >>> >> > ICANN?s video conferencing platform, Zoom, has been in the news >>> >> > quite a bit. With shelter-in-place and work-from-home becoming more >>> >> > familiar, not only for the ICANN community but the world at large, >>> >> > Zoom has become a vital tool for many businesses. With this recent >>> >> > increase in Zoom usage, we?ve also seen a number of bugs, flaws, and >>> >> > security vulnerabilities come to light. >>> >> > >>> >> > It?s natural that a hugely popular system like Zoom will be poked >>> >> > and prodded, and it?s likely that alarming bits of information will >>> >> > continue to be revealed in the coming weeks and months. >>> >> > >>> >> > However, it?s important to remember that almost any piece of >>> >> > software has bugs and glitches. What?s vitally important in these >>> >> > moments is how the software vendor reacts to receiving such >>> >> > information. In this regard, ICANN applauds Zoom for their efforts. >>> >> > Every time a new vulnerability has been exposed, Zoom has reacted >>> >> > swiftly by releasing patches within a day or two, while remaining >>> >> > transparent about the nature of the underlying issues. >>> >> > >>> >> > If you care to learn more about any specific vulnerability or how >>> >> > Zoom has responded, we highly recommend taking a look at Zoom?s >>> >> > blog, which is available here >>> >> > [r20.rs6.net]< >>> >> >>> https://urldefense.proofpoint.com/v2/url?u=http-3A__r20.rs6.net_tn.jsp-3Ff-3D001ksZaHYpLxs73N74vLz88Vq0p2eY7hNPIUETQItxPS1zFOkKdqUiWFt-2DqViuZxFtM6QSfysSoBf4quheUTAwEiPz0sCAeBTGnXtBWT3VOUDdgLqy-5FjkRDUX-2DDoc-5FAIJBNsEZCrqBaQEMqmDJxayUWRYd8HvkuefBV-26c-3Dwy9XJGNosEnEjdPoYLdJwvuIgsRRZOESZYkznmQPNTaHtmURx3UpcA-3D-3D-26ch-3D3Nfh4df3oGcxggBTYNdpswIf0un3QheyxW0pkf2jmeEOezCq3E9Zxg-3D-3D&d=DwMFaQ&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=8_WhWIPqsLT6TmF1Zmyci866vcPSFO4VShFqESGe_5iHWGlBLwwwehFBfjrsjWv9&m=Lr1oOkYZ9081GhqSfAb5smovhT1n5h6sykrEY1gEbF0&s=PcGAwKynwBZUH87c_nxV4y4WJ4UDzgrIgLEF0Y-yy3M&e= >>> >. >>> >> As stated before, it?s likely that this won?t be the last time we >>> will hear >>> >> about Zoom?s flaws, either from security researchers or new attack >>> >> > vectors. >>> >> > >>> >> > While we continue to monitor developments, ICANN remains committed >>> >> > to Zoom. We strive to offer the best solutions to our community, and >>> >> > at this time, we are still confident that Zoom fits the bill. >>> >> > >>> >> > If you have any questions or comments regarding Zoom and how it may >>> >> > relate to you, please do not hesitate to reach out to >>> >> > mts at icann.org. >>> >> > >>> >> > >>> >> > >>> >> > ENDS TOMORROW: Your Feedback about this Digest >>> >> > Executive: David Olive, Senior Vice President, Policy Development >>> Support >>> >> > >>> >> > Reflecting on the first year of the ICANN Community Leadership >>> >> > Digest, the ICANN org Policy Development Support function seeks your >>> >> > feedback. Please take this brief survey >>> >> > [r20.rs6.net]< >>> >> >>> https://urldefense.proofpoint.com/v2/url?u=http-3A__r20.rs6.net_tn.jsp-3Ff-3D001ksZaHYpLxs73N74vLz88Vq0p2eY7hNPIUETQItxPS1zFOkKdqUiWFkIoDPRoPRvsBdZ-5FGoiv0BcyEsqTchFFXXkzDy-5FPrXuLQ2wWkGUnqMG5vB-5FBsL-2DexDGGYx9Z93RcP-5FqESAsVE1N-5Fes14Oc-5FQcEOwODWQkSy-2D-26c-3Dwy9XJGNosEnEjdPoYLdJwvuIgsRRZOESZYkznmQPNTaHtmURx3UpcA-3D-3D-26ch-3D3Nfh4df3oGcxggBTYNdpswIf0un3QheyxW0pkf2jmeEOezCq3E9Zxg-3D-3D&d=DwMFaQ&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=8_WhWIPqsLT6TmF1Zmyci866vcPSFO4VShFqESGe_5iHWGlBLwwwehFBfjrsjWv9&m=Lr1oOkYZ9081GhqSfAb5smovhT1n5h6sykrEY1gEbF0&s=9DQ1pHoBVR4vpcEUVnWV4Lw8sYIcbujzoWdUKYawy9U&e= >>> > >>> >> by Friday, 10 April >>> >> > 2020. >>> >> > >>> >> > >>> >> > >>> >> > REMINDER: Call for Expressions of Interest: Standing Panel for >>> >> > ICANN?s Independent Review Process >>> >> > Announcement >>> >> > [r20.rs6.net]< >>> >> >>> https://urldefense.proofpoint.com/v2/url?u=http-3A__r20.rs6.net_tn.jsp-3Ff-3D001ksZaHYpLxs73N74vLz88Vq0p2eY7hNPIUETQItxPS1zFOkKdqUiWFhDXvOWShZvD2hLEBznqukU-2DzpGY9SKvgZYnzs8Pb7q6cYigVDx3lR28KNIIg1OZSSrtV6PTHjePVwGIxmZNiT5QJa0uMX2tqVpBsJG4J0BWWru2lfXIvdoYMrq-5FhNGeLCfd1j-5F1OZaM-26c-3Dwy9XJGNosEnEjdPoYLdJwvuIgsRRZOESZYkznmQPNTaHtmURx3UpcA-3D-3D-26ch-3D3Nfh4df3oGcxggBTYNdpswIf0un3QheyxW0pkf2jmeEOezCq3E9Zxg-3D-3D&d=DwMFaQ&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=8_WhWIPqsLT6TmF1Zmyci866vcPSFO4VShFqESGe_5iHWGlBLwwwehFBfjrsjWv9&m=Lr1oOkYZ9081GhqSfAb5smovhT1n5h6sykrEY1gEbF0&s=wh1fzSPiKMlK_nF31FLv2uByqlUbU5tu7_fdgg8Hif4&e= >>> >> > >>> >> > >>> >> > On 31 March 2020, ICANN opened a call for Expressions of Interest >>> >> > for panelists to serve on the omnibus Standing Panel for ICANN's >>> >> > Independent Review Process (IRP). The deadline to submit Expressions >>> >> > of Interest is 31 July 2020 at 23:59 UTC. >>> >> > >>> >> > Candidates for the IRP omnibus Standing Panel should review the >>> >> > Expressions of Interest document >>> >> > [r20.rs6.net]< >>> >> >>> https://urldefense.proofpoint.com/v2/url?u=http-3A__r20.rs6.net_tn.jsp-3Ff-3D001ksZaHYpLxs73N74vLz88Vq0p2eY7hNPIUETQItxPS1zFOkKdqUiWFhDXvOWShZvDgPvUW1EhP8WCVbm7MS0BsmCnAHsaFMUEoj9AM6ObL9ubtekC1N1ukFoJ-5FBciA-2DgkijA-2DFBr90Ud-5FTOGNu8PWMhrNjdjjyZvqFIQ450g94Vru2c4WBkwiqkUG0w7QB7QlvcBo0S6i9KT2Lp9FwvFhrK2SAcT3d8Ft-26c-3Dwy9XJGNosEnEjdPoYLdJwvuIgsRRZOESZYkznmQPNTaHtmURx3UpcA-3D-3D-26ch-3D3Nfh4df3oGcxggBTYNdpswIf0un3QheyxW0pkf2jmeEOezCq3E9Zxg-3D-3D&d=DwMFaQ&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=8_WhWIPqsLT6TmF1Zmyci866vcPSFO4VShFqESGe_5iHWGlBLwwwehFBfjrsjWv9&m=Lr1oOkYZ9081GhqSfAb5smovhT1n5h6sykrEY1gEbF0&s=G4e0eHDidhaSHCLG-Lp0mdVooTB9Udt6NFCT4_hfNvQ&e= >>> >before >>> >> submission. The document includes the following >>> >> > information: >>> >> > >>> >> > ? Panel Position Description >>> >> > ? Required or Highly Preferred Skills >>> >> > ? Required or Highly Preferred Experience >>> >> > ? Time Commitment >>> >> > ? Compensation and Selection >>> >> > >>> >> > Expressions of Interest should be submitted to >>> >> > IRP-Standingpanel-EOI2020 at icann.org>> >> IRP-Standingpanel-EOI2020 at icann.org> by 23:59 UTC on 31 July >>> >> > 2020. >>> >> > >>> >> > Public Comment >>> >> > >>> >> > CLOSES MONDAY: Revised Community Travel Support Guidelines >>> >> > [r20.rs6.net]< >>> >> >>> https://urldefense.proofpoint.com/v2/url?u=http-3A__r20.rs6.net_tn.jsp-3Ff-3D001ksZaHYpLxs73N74vLz88Vq0p2eY7hNPIUETQItxPS1zFOkKdqUiWFtY89CwSG4vGP9QyFiNsydEQVAWcEV-5Fx-5FyYMuDyD9mhUkKrwtZ0UYkgE52pUAGJUVyllQf8HsJVLqUb7Hl-2DQJvk-2DtNR7dPmp0y3V4wbIVgix6rHxXUJcoqQekwI114IIACiTWznCmlJwYRq4nQbpRTCw-2Dara5yu37Emw-5FDvyjlUE-26c-3Dwy9XJGNosEnEjdPoYLdJwvuIgsRRZOESZYkznmQPNTaHtmURx3UpcA-3D-3D-26ch-3D3Nfh4df3oGcxggBTYNdpswIf0un3QheyxW0pkf2jmeEOezCq3E9Zxg-3D-3D&d=DwMFaQ&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=8_WhWIPqsLT6TmF1Zmyci866vcPSFO4VShFqESGe_5iHWGlBLwwwehFBfjrsjWv9&m=Lr1oOkYZ9081GhqSfAb5smovhT1n5h6sykrEY1gEbF0&s=KZRoix0AC0mirjIIP5MqMXYT8_kOVKpVj-AnQc4qVEI&e= >>> >> > >>> >> > Close Date: Monday, 13 April 2020 >>> >> > >>> >> > Proposal for Chinese Script Root Zone Label Generation Rules >>> >> > [r20.rs6.net]< >>> >> >>> https://urldefense.proofpoint.com/v2/url?u=http-3A__r20.rs6.net_tn.jsp-3Ff-3D001ksZaHYpLxs73N74vLz88Vq0p2eY7hNPIUETQItxPS1zFOkKdqUiWFhiNYDgFY8zJdVvy8ZlKxm9ygyJmLgZOGIYB-2DzeG5FSuiAXh8oBSRbqMjNeUcl0ggkZN8rs6RO4JLtosigTh8p4JBv7Amc7V4tOTqIRpzAXok0l9gaWxurzrwTxTbtIpqbNaih-5Fc5l85eB854mYXP0gKGto16a6-5FING4f4AaT1yo-26c-3Dwy9XJGNosEnEjdPoYLdJwvuIgsRRZOESZYkznmQPNTaHtmURx3UpcA-3D-3D-26ch-3D3Nfh4df3oGcxggBTYNdpswIf0un3QheyxW0pkf2jmeEOezCq3E9Zxg-3D-3D&d=DwMFaQ&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=8_WhWIPqsLT6TmF1Zmyci866vcPSFO4VShFqESGe_5iHWGlBLwwwehFBfjrsjWv9&m=Lr1oOkYZ9081GhqSfAb5smovhT1n5h6sykrEY1gEbF0&s=g3VHZG_hmZ8ewQKGAD8iSf-O0ckPMC4xfCiO6F2bQkc&e= >>> >> > >>> >> > Close Date: Monday, 20 April 2020 >>> >> > >>> >> > Proposal for Bangla Script Root Zone Label Generation Rules >>> >> > [r20.rs6.net]< >>> >> >>> https://urldefense.proofpoint.com/v2/url?u=http-3A__r20.rs6.net_tn.jsp-3Ff-3D001ksZaHYpLxs73N74vLz88Vq0p2eY7hNPIUETQItxPS1zFOkKdqUiWFmKYv52uy6-2D4iiVzpAClZnxseaCCiGyXl0PjEyfQjPwmxWMXlc-5FOuVGUsBSfBJ4Mb8jrSF2ecxJcaUOwQrllleeTthNvI-5FKg7imzq2TklU4gGyf05gDt8XdZloNEILhO5PZupDyzOeDc6VBNUfC5kOBo8PJR7FS3KaJ6Hp2dBRu8-26c-3Dwy9XJGNosEnEjdPoYLdJwvuIgsRRZOESZYkznmQPNTaHtmURx3UpcA-3D-3D-26ch-3D3Nfh4df3oGcxggBTYNdpswIf0un3QheyxW0pkf2jmeEOezCq3E9Zxg-3D-3D&d=DwMFaQ&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=8_WhWIPqsLT6TmF1Zmyci866vcPSFO4VShFqESGe_5iHWGlBLwwwehFBfjrsjWv9&m=Lr1oOkYZ9081GhqSfAb5smovhT1n5h6sykrEY1gEbF0&s=7RSaqRNE7rwHcd2Sia8v2TRbLiflkRsGySbo33Pq9D0&e= >>> >> > >>> >> > Close Date: Thursday, 23 April 2020 >>> >> > >>> >> > Phase 1 Initial Report of the Review of All Rights Protection >>> >> > Mechanisms in All gTLDs Policy Development Process >>> >> > [r20.rs6.net]< >>> >> >>> https://urldefense.proofpoint.com/v2/url?u=http-3A__r20.rs6.net_tn.jsp-3Ff-3D001ksZaHYpLxs73N74vLz88Vq0p2eY7hNPIUETQItxPS1zFOkKdqUiWFj9fpHfmJJBeKb1epUydWc3EzsZSj8Uwcoii-2DXmD2XtnFwFaGxB-2Dx6I16WKdSg0EkEC8BAhBu2WHMbFq2sUIRInh2xgGkOwZhGqyawEOqZ634-5FhH7CQ8RxlXu63kefU2cg85EZjcOb2duwpwhMjATiAMPeaPDlTsxA-3D-3D-26c-3Dwy9XJGNosEnEjdPoYLdJwvuIgsRRZOESZYkznmQPNTaHtmURx3UpcA-3D-3D-26ch-3D3Nfh4df3oGcxggBTYNdpswIf0un3QheyxW0pkf2jmeEOezCq3E9Zxg-3D-3D&d=DwMFaQ&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=8_WhWIPqsLT6TmF1Zmyci866vcPSFO4VShFqESGe_5iHWGlBLwwwehFBfjrsjWv9&m=Lr1oOkYZ9081GhqSfAb5smovhT1n5h6sykrEY1gEbF0&s=nM36roD_xIofeZLEMtaGs4IFjj_j1wl-og3VAEvdazg&e= >>> >> > >>> >> > Close Date: Monday, 27 April 2020 >>> >> > >>> >> > Addendum to the Initial Report of the Expedited Policy Development >>> >> > Process (EPDP) on the Temporary Specification for gTLD Registration >>> >> > Data Team ? Phase 2 >>> >> > [r20.rs6.net]< >>> >> >>> https://urldefense.proofpoint.com/v2/url?u=http-3A__r20.rs6.net_tn.jsp-3Ff-3D001ksZaHYpLxs73N74vLz88Vq0p2eY7hNPIUETQItxPS1zFOkKdqUiWFkIoDPRoPRvs82iXYdszIj2pYDMS0rHPlAwpwN9mhLx55-5FummJlrmbA4Y8TZsI1OX7YHgEoYiLKBHSAHoMPs0M9SBwTeNrArt-5F5k46yplBom7C7hdDtQ5K1ogJhd-5Fl8lJkSnqckbjs4vzHjRTRP8RF2guXWgh9xErA-3D-3D-26c-3Dwy9XJGNosEnEjdPoYLdJwvuIgsRRZOESZYkznmQPNTaHtmURx3UpcA-3D-3D-26ch-3D3Nfh4df3oGcxggBTYNdpswIf0un3QheyxW0pkf2jmeEOezCq3E9Zxg-3D-3D&d=DwMFaQ&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=8_WhWIPqsLT6TmF1Zmyci866vcPSFO4VShFqESGe_5iHWGlBLwwwehFBfjrsjWv9&m=Lr1oOkYZ9081GhqSfAb5smovhT1n5h6sykrEY1gEbF0&s=372vmvMQMKD1hyBnYvsBdaqs5ENaZ83CYOFt3YlQQ5Q&e= >>> >> > >>> >> > Close Date: Tuesday, 5 May 2020 >>> >> > Guidelines for Developing Reference Label Generation Rules (LGRs) >>> >> > for the Second Level Version 2 >>> >> > [r20.rs6.net]< >>> >> >>> https://urldefense.proofpoint.com/v2/url?u=http-3A__r20.rs6.net_tn.jsp-3Ff-3D001ksZaHYpLxs73N74vLz88Vq0p2eY7hNPIUETQItxPS1zFOkKdqUiWFhkxpqfCSVcEKH3lZoDdmOeJGHXZWUszKwUfZd4u0uFjsOQLvwjUSG7DpH9-5Fmg09z483tj0jtrRtSrD-5FQHfMU-5F1gfUAgtIzJrrXdCCz60eVKM-2DMSL68SnYO77GMdeDFp8s8YUM5faEvCxgvyQZ-2D9yFNacpgtcwSCHA-3D-3D-26c-3Dwy9XJGNosEnEjdPoYLdJwvuIgsRRZOESZYkznmQPNTaHtmURx3UpcA-3D-3D-26ch-3D3Nfh4df3oGcxggBTYNdpswIf0un3QheyxW0pkf2jmeEOezCq3E9Zxg-3D-3D&d=DwMFaQ&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=8_WhWIPqsLT6TmF1Zmyci866vcPSFO4VShFqESGe_5iHWGlBLwwwehFBfjrsjWv9&m=Lr1oOkYZ9081GhqSfAb5smovhT1n5h6sykrEY1gEbF0&s=2L3B7qhd8walcslu4Qzo1xk083LuHFdGUKBwCMoEcVI&e= >>> >> > >>> >> > Close Date: Tuesday, 12 May 2020 >>> >> > >>> >> > Volume 2, Issue 29 | Archive >>> >> > [r20.rs6.net]< >>> >> >>> https://urldefense.proofpoint.com/v2/url?u=http-3A__r20.rs6.net_tn.jsp-3Ff-3D001ksZaHYpLxs73N74vLz88Vq0p2eY7hNPIUETQItxPS1zFOkKdqUiWFvN81lnNY4rwlNDFDEUS18xytYwuCwvTM36th-2DNM1lg23ibrV1QS9vnURID3EAHR2bL3FO7PSkQ2LjAdsmzGVn3m9oxJsnuRYZ7gwJeaIqWDGMtkORnO7mab4cIUHDskuHoIGeGQcvuVLX-2D-2DaoviPHPVhZVgldulZGKw9xaC8AS22-5FJL9uFCJzA-3D-26c-3Dwy9XJGNosEnEjdPoYLdJwvuIgsRRZOESZYkznmQPNTaHtmURx3UpcA-3D-3D-26ch-3D3Nfh4df3oGcxggBTYNdpswIf0un3QheyxW0pkf2jmeEOezCq3E9Zxg-3D-3D&d=DwMFaQ&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=8_WhWIPqsLT6TmF1Zmyci866vcPSFO4VShFqESGe_5iHWGlBLwwwehFBfjrsjWv9&m=Lr1oOkYZ9081GhqSfAb5smovhT1n5h6sykrEY1gEbF0&s=LLA54bpW6lPOCy5iKFZ3Vb9RORKPyANq7iVQ7ex-Q_8&e= >>> > >>> >> | Next Issue: Monday, 13 April >>> >> > 2020 >>> >> > >>> >> > >>> >> > _______________________________________________ >>> >> > council mailing list >>> >> > council at gnso.icann.org >>> >> > https://mm.icann.org/mailman/listinfo/council >>> >> > >>> >> > _______________________________________________ >>> >> > 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. >>> >> >>> >> > > -- > *Bruna Martins dos Santos * > > Skype ID: bruna.martinsantos > @boomartins > -------------- next part -------------- An HTML attachment was scrubbed... URL: From rafik.dammak at gmail.com Wed Apr 29 01:35:37 2020 From: rafik.dammak at gmail.com (Rafik Dammak) Date: Wed, 29 Apr 2020 07:35:37 +0900 Subject: [NCSG-PC] [Urgent] NCSG statement PIR Transaction and Proposed Public Interest Commitments Update In-Reply-To: References: <1134142044748.1122025845763.1521253088.0.711100JL.2002@scheduler.constantcontact.com> <11CE170D-5897-424C-BE73-090F1016BE03@icann.org> Message-ID: Hi, here the latest version fo NCSG statement regarding .org sale and proposed PICs https://docs.google.com/document/d/17smIcztTiGNcdOefZuUeM3ytY2HGYRaBu3Npt5FW4uA/edit We need to act now as the board is going to make decision. Last edit the statement was made and the draft was in NCSG list for a while. If there is no objection within the next 24 hours, I will send the letter to ICANN board and CEO. I understand the current situation with covid-19 and confinement but we also still to respond. Best, Rafik -------------- next part -------------- An HTML attachment was scrubbed... URL: From rafik.dammak at gmail.com Wed Apr 29 01:59:09 2020 From: rafik.dammak at gmail.com (Rafik Dammak) Date: Wed, 29 Apr 2020 07:59:09 +0900 Subject: [NCSG-PC] Reminder PC Chair election / Vice-chairs appointments In-Reply-To: References: Message-ID: Hi all, I am sending my SOI for the position of NCSG PC chair: "I am honored to put my name for reelection for last term as NCSG Policy Committee Chair as my term as councillor will end this AGM. I am volunteering to continue for the rest in year in order to prepare for transition and support new leadership for the policy committee and NCSG in general. My goals if elected would be to apply what we agreed as NCSG PC in our first call, continue that discussion and finish remaining tasks in order to improve our functioning and being more effective while taking into consideration the current situation and challenges we are all living. The policy committee has an important role to ensure NCSG effective participation and representation in PDPs, following council activities and build NCSG policy positions. I understand that we have to improve our reporting, engagement with our members such as the monthly policy calls, webinars and tweak their format, to formalize our operating procedures and enhance our working methods, and engaging all PC members in the work and discussion. I commit to collaborate with the vice-chairs, the rest of NCSG leadership and of the constituencies as we have some some challenges such as dealing with ongoing PDPs and future work, and how to work mostly online including ICANN meetings" Best, Rafik Le mar. 21 avr. 2020 ? 08:44, Rafik Dammak a ?crit : > Hi all, > > there were few comments/questions about the proposed process. I didn't see > any objection . Adjusting the timeline and the process based on comments. > and assuming there is support for the process (edits in red): > > 1- Nomination period: from 24th April to 1st May > > Nomination and self-nomination are both permitted from and within PC > members (NCSG councillors, NCSG Chair, representatives from NCUC and NPOC > to PC), for one year term for PC chair position. > The nominee should accept the nomination and send a short SOI by the 1st > May. > > 2- Election : 1st May to 8th May > > all PC members should vote. the GNSO support staff will act as the > election officer. The options in the ballot should be the candidates who > confirmed by the deadline and NOTA > > 3- Result: should be available by 9th May > > the candidate who get 2/3 vote of the NCSG?PC membership will be > declared winner. > > in case of nobody get the 2/3 vote a second round should be organized with > the candidate who get most of votes against NOTA. if the candidate doesn't > get 2/3 of votes, a new election process should be initiated asap. > > 4- Vice-chairs appointments: > > After PC chair confirmation, a call for interest should be made to have up > to 2 vice-chairs. The appointment of the volunteers will be confirmed if > there is no objection within PC. > > 5- the term of PC chair and vice-chairs is 1 year term. > > if there is no objection we will start this Friday. > > Best, > > Rafik > > Le jeu. 9 avr. 2020 ? 09:11, Rafik Dammak a > ?crit : > >> Hi all, >> >> following-up (with delay) on one the agreed action items which is the PC >> chair election and vice-chairs appointment, I am proposing here a draft >> process and timeline. it might sound formal compared to what we discussed >> previously but I am using this a draft for building fully fledged process >> in future: >> >> 1- Nomination period: from 17th to 24th April >> >> Nomination and self-nomination are both permitted from and within PC >> members (NCSG councillors, NCSG Chair, representatives from NCUC and NPOC >> to PC), for one year term for PC chair position. >> The nominee should accept the nomination and send a short SOI by the 24th >> April. >> >> 2- Election : from 27th April to 1st May >> >> all PC members should vote. the GNSO support staff will act as the >> election officer. The options in the ballot should be the candidates who >> confirmed by the deadline and NOTA >> >> 3- Result: should be available by 2nd May >> >> the candidate who get 2/3 vote of the NCSG?PC membership will be >> declared winner. >> >> 4- Vice-chairs appointments: >> >> After PC chair confirmation, a call for interest should be made to have >> up to 2 vice-chairs. The appointment of the volunteers will be confirmed if >> there is no objection within PC. >> >> >> this is just draft process and should be fleshed out to documented for >> future. I didn't outline all cases regarding the election for example. >> After that, the next step will be to work on job description for those >> positions. >> >> Please let me know your thoughts/comments on what is proposed. >> >> Best, >> >> Rafik >> >> >> ---------- Forwarded message --------- >> De : Rafik Dammak >> Date: lun. 2 mars 2020 ? 09:35 >> Subject: NCSG Policy Committee meeting follow-up >> To: ncsg-pc >> >> >> Hi all, >> >> as you know we had last week our PC meeting to discuss several items >> regarding election, improvements etc. We got already some action item to >> follow-up >> >> 1- PC chair Election: there was agreement to go with the idea of having >> chair and 2 vice-chairs. The point was also to have proper open process >> (that can be documented for future). so the action here is to agree on >> timeline and process (nomination, vote). it shouldn't be complicated. I >> believe we can get this done in this month e.g. 1 week for nomination and 1 >> week for voting. >> 2- Having a regular PC call, hopefully monthly call and coordinating more >> with our NCSG reps to council. The action would be to agree on regular >> day/time. I think that can be 2 weeks after NCSG Policy. >> 3- Regarding documentation and development of workflow, I believe that >> can be done with reworking again on PC operating procedure and documenting >> previous activities. I am sharing here the PC operating procedures draft >> being worked on before >> https://docs.google.com/document/d/1G_M4wBGVEyXm30m79olplfF0RNkJnDwaVBBeldDfO8U/edit . >> For anything missing, we can start first to identify that and have >> volunteers to draft it. For Chair job description, I can use what I >> presented and develop a draft. >> 4- Sharing here the slides I presented in last call: >> https://docs.google.com/presentation/d/1SnpMYmb6lTw1FqO6tvSqCdpgL-QMg1DJXIJGrx8vB6A/edit#slide=id.p >> 5- for NCSG Policy call improvements, we will have the NCSG Policy call >> in coming days and I will try to make some adjustments to extent of >> possible. It might be shorter than usual as we will have NCSG meeting next >> week. From April NCSG Policy call, we can start identifying other topics we >> would like to cover other than council meeting and usual policy updates. >> >> One activity we will need to do soon and follow-up is to work about >> prioritization. GNSO Council will discuss the GNSO future work soon and we >> need to be ready and align our work around that. That also aligns with the >> discussion we had about prioritizing our work and it starts with >> identifying what is in the pipeline. >> >> let me know if I missed anything. >> >> Best. >> >> Rafik >> >> -------------- next part -------------- An HTML attachment was scrubbed... URL: From tatiana.tropina at gmail.com Wed Apr 29 02:31:25 2020 From: tatiana.tropina at gmail.com (Tatiana Tropina) Date: Wed, 29 Apr 2020 01:31:25 +0200 Subject: [NCSG-PC] [Urgent] NCSG statement PIR Transaction and Proposed Public Interest Commitments Update In-Reply-To: References: <1134142044748.1122025845763.1521253088.0.711100JL.2002@scheduler.constantcontact.com> <11CE170D-5897-424C-BE73-090F1016BE03@icann.org> Message-ID: Hi Rafik, I support sending this. Cheers, Tanya On Wed, 29 Apr 2020 at 00:35, Rafik Dammak wrote: > Hi, > > here the latest version fo NCSG statement regarding .org sale and proposed > PICs > https://docs.google.com/document/d/17smIcztTiGNcdOefZuUeM3ytY2HGYRaBu3Npt5FW4uA/edit > We need to act now as the board is going to make decision. Last edit the > statement was made and the draft was in NCSG list for a while. If there is > no objection within the next 24 hours, I will send the letter to ICANN > board and CEO. > I understand the current situation with covid-19 and confinement but we > also still to respond. > > Best, > > Rafik > _______________________________________________ > NCSG-PC mailing list > NCSG-PC at lists.ncsg.is > https://lists.ncsg.is/mailman/listinfo/ncsg-pc > -------------- next part -------------- An HTML attachment was scrubbed... URL: From kathy at kathykleiman.com Wed Apr 29 02:37:51 2020 From: kathy at kathykleiman.com (Kathy Kleiman) Date: Tue, 28 Apr 2020 19:37:51 -0400 Subject: [NCSG-PC] [Urgent] NCSG statement PIR Transaction and Proposed Public Interest Commitments Update In-Reply-To: Message-ID: <691d51f73d1779e100cce9af92f5c4624261ef6d@gmmn-6gkh.accessdomain.com> ? All,I'm afraid the timing for this letter was very important a week ago.? As I watched the letter sit, I feared we were "fiddling while Rome was burning."? (to use a very old phrase). Our letter is no longer timely. Huge events have taken place in the last week -- led by those who submitted their letters to the Board by 4/15.? To not reference those letters and these events is to diminish them -- and we have no NCSG agreement to do that. Timing is everything.Best, Kathy ----- Original Message ----- From: "Rafik Dammak" To:"ncsg-pc" Cc: Sent:Wed, 29 Apr 2020 07:35:37 +0900 Subject:[NCSG-PC] [Urgent] NCSG statement PIR Transaction and Proposed Public Interest Commitments Update Hi, here the latest version fo NCSG statement regarding .org sale and proposed PICs?https://docs.google.com/document/d/17smIcztTiGNcdOefZuUeM3ytY2HGYRaBu3Npt5FW4uA/edit [1]We need to act now as the board is going to make decision. Last edit the statement was made and the draft was in NCSG list for a while. If there is no objection within the next 24 hours, I will send the letter to ICANN board and CEO.I understand the current situation with covid-19 and confinement but we also still to respond. Best, Rafik Links: ------ [1] https://docs.google.com/document/d/17smIcztTiGNcdOefZuUeM3ytY2HGYRaBu3Npt5FW4uA/edit -------------- next part -------------- An HTML attachment was scrubbed... URL: From kathy at kathykleiman.com Wed Apr 29 07:24:30 2020 From: kathy at kathykleiman.com (Kathy Kleiman) Date: Wed, 29 Apr 2020 00:24:30 -0400 Subject: [NCSG-PC] [Urgent] NCSG statement PIR Transaction and Proposed Public Interest Commitments Update In-Reply-To: <691d51f73d1779e100cce9af92f5c4624261ef6d@gmmn-6gkh.accessdomain.com> Message-ID: On further reflection, is there any way to acknowledge the importance of the California AG's letter (whatever you think of it, it is very important when a company is contacted by its AG), and continue to submit these comments? Kathy ----- Original Message ----- From: "Kathy Kleiman" To:"Rafik Dammak" , "ncsg-pc" Cc: Sent:Tue, 28 Apr 2020 19:37:51 -0400 Subject:Re: [NCSG-PC] [Urgent] NCSG statement PIR Transaction and Proposed Public Interest Commitments Update ? All,I'm afraid the timing for this letter was very important a week ago.? As I watched the letter sit, I feared we were "fiddling while Rome was burning."? (to use a very old phrase). Our letter is no longer timely. Huge events have taken place in the last week -- led by those who submitted their letters to the Board by 4/15.? To not reference those letters and these events is to diminish them -- and we have no NCSG agreement to do that. Timing is everything.Best, Kathy ----- Original Message ----- From: "Rafik Dammak" To:"ncsg-pc" Cc: Sent:Wed, 29 Apr 2020 07:35:37 +0900 Subject:[NCSG-PC] [Urgent] NCSG statement PIR Transaction and Proposed Public Interest Commitments Update Hi, here the latest version fo NCSG statement regarding .org sale and proposed PICs?https://docs.google.com/document/d/17smIcztTiGNcdOefZuUeM3ytY2HGYRaBu3Npt5FW4uA/edit [1]We need to act now as the board is going to make decision. Last edit the statement was made and the draft was in NCSG list for a while. If there is no objection within the next 24 hours, I will send the letter to ICANN board and CEO.I understand the current situation with covid-19 and confinement but we also still to respond. Best, Rafik Links: ------ [1] https://docs.google.com/document/d/17smIcztTiGNcdOefZuUeM3ytY2HGYRaBu3Npt5FW4uA/edit -------------- next part -------------- An HTML attachment was scrubbed... URL: From kathy at kathykleiman.com Thu Apr 30 01:09:49 2020 From: kathy at kathykleiman.com (Kathy Kleiman) Date: Wed, 29 Apr 2020 18:09:49 -0400 Subject: [NCSG-PC] [Urgent] NCSG statement PIR Transaction and Proposed Public Interest Commitments Update Message-ID: <196244591c2dae63c832fec4a1d6c59b68c8f0d3@gmmn-6gkh.accessdomain.com> Rafik and All, I've added two sentences and a few words at the outset to note that our comments are limited in scope -- and not intended to replace any other type of evaluation taking place on the .ORG sale. That said, these are important comments and I agree with Rafik we should submit them (lightly taking into accounts events of the last week). Best, Kathy On 4/28/2020 6:35 PM, Rafik Dammak wrote: Hi, here the latest version fo NCSG statement regarding .org sale and proposed PICs?https://docs.google.com/document/d/17smIcztTiGNcdOefZuUeM3ytY2HGYRaBu3Npt5FW4uA/edit [1]We need to act now as the board is going to make decision. Last edit the statement was made and the draft was in NCSG list for a while. If there is no objection within the next 24 hours, I will send the letter to ICANN board and CEO.I understand the current situation with covid-19 and confinement but we also still to respond. Best, Rafik Links: ------ [1] https://docs.google.com/document/d/17smIcztTiGNcdOefZuUeM3ytY2HGYRaBu3Npt5FW4uA/edit -------------- next part -------------- An HTML attachment was scrubbed... URL: From dgdorothydg at gmail.com Thu Apr 30 01:21:38 2020 From: dgdorothydg at gmail.com (dorothy g) Date: Wed, 29 Apr 2020 22:21:38 +0000 Subject: [NCSG-PC] [Urgent] NCSG statement PIR Transaction and Proposed Public Interest Commitments Update In-Reply-To: <196244591c2dae63c832fec4a1d6c59b68c8f0d3@gmmn-6gkh.accessdomain.com> References: <196244591c2dae63c832fec4a1d6c59b68c8f0d3@gmmn-6gkh.accessdomain.com> Message-ID: Dear all, I am observer on the PC however I do hope members take a decision on this taken quickly. best regards Dorothy On Wed, Apr 29, 2020 at 10:10 PM Kathy Kleiman wrote: > Rafik and All, > > I've added two sentences and a few words at the outset to note that our > comments are limited in scope -- and not intended to replace any other type > of evaluation taking place on the .ORG sale. > > That said, these are important comments and I agree with Rafik we should > submit them (lightly taking into accounts events of the last week). > > Best, Kathy > On 4/28/2020 6:35 PM, Rafik Dammak wrote: > > Hi, > > here the latest version fo NCSG statement regarding .org sale and proposed > PICs > https://docs.google.com/document/d/17smIcztTiGNcdOefZuUeM3ytY2HGYRaBu3Npt5FW4uA/edit > We need to act now as the board is going to make decision. Last edit the > statement was made and the draft was in NCSG list for a while. If there is > no objection within the next 24 hours, I will send the letter to ICANN > board and CEO. > I understand the current situation with covid-19 and confinement but we > also still to respond. > > Best, > > Rafik > > _______________________________________________ > NCSG-PC mailing list > NCSG-PC at lists.ncsg.is > https://lists.ncsg.is/mailman/listinfo/ncsg-pc > -- Dorothy Gordon -------------- next part -------------- An HTML attachment was scrubbed... URL: From oreoluwa at wtec.org.ng Thu Apr 30 02:02:24 2020 From: oreoluwa at wtec.org.ng (oreoluwa) Date: Thu, 30 Apr 2020 00:02:24 +0100 Subject: [NCSG-PC] [Urgent] NCSG statement PIR Transaction and Proposed Public Interest Commitments Update In-Reply-To: Message-ID: Hello everyone,I have no objection to the letter.?Thank you to everyone who worked on it.Kind regards,?Ore--Oreoluwa Lesi Executive Director, Women's Technology Empowerment Centre (W.TEC)www.wtec.org.ng | @wteconlineSent from my Samsung Galaxy smartphone. -------- Original message --------From: dorothy g Date: 29/04/2020 23:22 (GMT+01:00) To: Kathy Kleiman Cc: NCSG PC Subject: Re: [NCSG-PC] [Urgent] NCSG statement PIR Transaction and Proposed Public Interest Commitments Update Dear all,? I am observer?on the PC however I do hope members take a decision on this taken quickly.best regardsDorothyOn Wed, Apr 29, 2020 at 10:10 PM Kathy Kleiman wrote:Rafik and All,I've added two sentences and a few words at the outset to note that our comments are limited in scope -- and not intended to replace any other type of evaluation taking place on the .ORG sale.That said, these are important comments and I agree with Rafik we should submit them (lightly taking into accounts events of the last week).Best, Kathy On 4/28/2020 6:35 PM, Rafik Dammak wrote: Hi,here the latest version fo NCSG statement regarding .org sale and proposed PICs?https://docs.google.com/document/d/17smIcztTiGNcdOefZuUeM3ytY2HGYRaBu3Npt5FW4uA/editWe need to act now as the board is going to make decision. Last edit the statement was made and the draft was in NCSG list for a while. If there is no objection within the next 24 hours, I will send the letter to ICANN board and CEO.I understand the current situation with covid-19 and confinement but we also still to respond.Best,Rafik _______________________________________________ NCSG-PC mailing list NCSG-PC at lists.ncsg.is https://lists.ncsg.is/mailman/listinfo/ncsg-pc -- Dorothy Gordon -------------- next part -------------- An HTML attachment was scrubbed... URL: From lizorembo at gmail.com Thu Apr 30 07:09:09 2020 From: lizorembo at gmail.com (Liz Orembo) Date: Thu, 30 Apr 2020 07:09:09 +0300 Subject: [NCSG-PC] [Urgent] NCSG statement PIR Transaction and Proposed Public Interest Commitments Update In-Reply-To: <20200429230247.90BE984F6@posti.effi.org> References: <20200429230247.90BE984F6@posti.effi.org> Message-ID: I've gone through the document and is good. No objection from my side. On Thu, Apr 30, 2020, 02:02 oreoluwa wrote: > Hello everyone, > > I have no objection to the letter. > > Thank you to everyone who worked on it. > > Kind regards, > Ore > > > > -- > Oreoluwa Lesi > Executive Director, Women's Technology Empowerment Centre (W.TEC) > www.wtec.org.ng | @wteconline > > > Sent from my Samsung Galaxy smartphone. > > > -------- Original message -------- > From: dorothy g > Date: 29/04/2020 23:22 (GMT+01:00) > To: Kathy Kleiman > Cc: NCSG PC > Subject: Re: [NCSG-PC] [Urgent] NCSG statement PIR Transaction and > Proposed Public Interest Commitments Update > > Dear all, I am observer on the PC however I do hope members take a > decision on this taken quickly. > > best regards > Dorothy > > On Wed, Apr 29, 2020 at 10:10 PM Kathy Kleiman > wrote: > >> Rafik and All, >> >> I've added two sentences and a few words at the outset to note that our >> comments are limited in scope -- and not intended to replace any other type >> of evaluation taking place on the .ORG sale. >> >> That said, these are important comments and I agree with Rafik we should >> submit them (lightly taking into accounts events of the last week). >> >> Best, Kathy >> On 4/28/2020 6:35 PM, Rafik Dammak wrote: >> >> Hi, >> >> here the latest version fo NCSG statement regarding .org sale and >> proposed PICs >> https://docs.google.com/document/d/17smIcztTiGNcdOefZuUeM3ytY2HGYRaBu3Npt5FW4uA/edit >> We need to act now as the board is going to make decision. Last edit the >> statement was made and the draft was in NCSG list for a while. If there is >> no objection within the next 24 hours, I will send the letter to ICANN >> board and CEO. >> I understand the current situation with covid-19 and confinement but we >> also still to respond. >> >> Best, >> >> Rafik >> >> _______________________________________________ >> NCSG-PC mailing list >> NCSG-PC at lists.ncsg.is >> https://lists.ncsg.is/mailman/listinfo/ncsg-pc >> > > > -- > Dorothy Gordon > _______________________________________________ > NCSG-PC mailing list > NCSG-PC at lists.ncsg.is > https://lists.ncsg.is/mailman/listinfo/ncsg-pc > -------------- next part -------------- An HTML attachment was scrubbed... URL: