- CPWG - lists.icann.org

Reminder for Comments: Evolving the Governance of the Root Server System
by Evin Erdogdu July 12, 2019

July 12, 2019

Dear All, As per the action item<https://community.icann.org/x/kqWjBg> from yesterday's At-Large Consolidated Policy Working Group (CPWG) meeting, this is a request for feedback from CPWG members on an ALAC statement in development regarding the Evolving Governance of the Root Server System?<https://community.icann.org/x/2IajBg>. Please login and contribute comments on the At-Large workspace here: https://community.icann.org/x/2IajBg Thank you. Kind Regards, Evin

3 2

Fwd: [Gnso-newgtld-wg] ALAC position on newgTLD subpro
by John Laprise July 11, 2019

July 11, 2019

Sent from my Pixel 3XL John Laprise, Ph.D. ---------- Forwarded message --------- From: Carlos Raul Gutierrez <carlosraul(a)gutierrez.se> Date: Thu, Jul 11, 2019, 4:36 PM Subject: Re: [Gnso-newgtld-wg] ALAC position on newgTLD subpro To: John Laprise <jlaprise(a)gmail.com> Cc: Cheryl Langdon-Orr <langdonorr(a)gmail.com> Hi John! Quick question: has ALAC dealt the message from the Board regarding CCT recommedations? The GNSO Council is working its part right now. Can you update us on this? (cc: clo GNSO council liaison) https://mm.icann.org/pipermail/council/2019-June/022775.html thanks --- Carlos Raúl Gutiérrez carlosraul(a)gutierrez.se +506 8837 7176 Aparatado 1571-1000 COSTA RICA El 2019-07-11 03:20, John Laprise escribió: Hi everyone, Just a useful reminder of ALAC’s position as asserted to ICANN GDD at ICANN65: ALAC will not support a new gTLD round until full implementation of CCT and RPM recommendations are fully implemented. Best regards, John Laprise, Ph.D. NARALO ALAC Representative ALAC Vice Chair-Policy _______________________________________________ Gnso-newgtld-wg mailing list Gnso-newgtld-wg(a)icann.org https://mm.icann.org/mailman/listinfo/gnso-newgtld-wg _______________________________________________ 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.

1 0

New ICANN Blog on Zoom and new Blog by TTF Co Chair Dev Anand Teelucksingh
by Judith Hellerstein July 11, 2019

July 11, 2019

1 0

Re: [CPWG] [Gnso-newgtld-wg] ALAC position on newgTLD subpro
by John Laprise July 11, 2019

July 11, 2019

Thanks Jeff, We've been following the discussion and are in the process of producing more detailed advice which will be forthcoming. However I can respond to points 1 & 4 now. It is our view that the subpro work is akin to refining the machinery while initiating a round is using the machinery. One necessarily precedes the other and we support the subpro work. We want it completed before we start using it in the future. On point 4: this is documented in ALACs #ICANN65 talking points document as well as recordings and transcripts of ALAC's session with GDD. We've also communicated this to the board with regularity and the other ACs. At Large's Consolidated Policy Working Group (CPWG) will be providing further detail as you requested. Sent from my Pixel 3XL John Laprise, Ph.D. On Thu, Jul 11, 2019, 10:52 AM Jeff Neuman <jeff.neuman(a)comlaude.com> wrote: > Thanks John for this e-mail. > > > > > > We discussed this comment and a few questions were raised during the call > last night. > > > > 1. “ALAC will not support a new gTLD round….” Can you please confirm > that the ALAC position refers only to the opening of the application window > as opposed to ICANN and the community taking steps to prepare for the > opening of the next application window. When something like this came up > previously with respect to the NCAP studies being a dependency for the next > round, Justine in the attached e-mail, explained: > > > > *“The Subsequent Procedures WG can conclude its work, and implementation > may proceed, BUT EITHER ICANN may not launch the application window until > the NCAP study(ies) are completed and any recommendations resulting from > those study(ies) are addressed in implementation OR ICANN may launch the > application window and start the evaluation process, but no TLD may be > delegated until the NCAP Study(ies) is/are completed and any > recommendations resulting from those study(ies) are retroactively > incorporated.”* > > > > Can you please explain if this should be interpreted similarly – > namely, that implementation can proceed in ALAC’s view? > > > > 1. “full implementation of CCT….recommendations are fully > implemented.” As you are no doubt aware, the CCT recommendations contain a > number of levels. Some are labeled as pre-requisites to the launch of the > next round, others are not. > > > > 1. Is the ALAC only referring to those recommendations that are deemed > to be pre-requisites? Or is the ALAC actually referring to ALL > recommendations regardless of how they were labeled? > 2. In addition, not all of the recommendations were accepted by the > ICANN Board for immediate implementation. Is the ALAC referring to only > the ones that were accepted by the ICANN Board or to literally all of the > recommendations regardless of whether they were accepted by the ICANN Board. > > > > 1. “full implementation of…RPM Recommendations are fully implemented” > 1. Is the ALAC only referring to Phase One of the RPM work or to > both Phase One (New gTLD protections) and Phase Two (UDRP)? > 2. The GNSO RPM PDP Working Group leaders represented to the GNSO > Council that they only believed that Phase One needed to be implemented by > the time the first new gTLD in the next round enters into an Agreement or > is delegated (not sure there was agreement on which one). But in either > case the GNSO has discussed the possibility of moving forward with SubPro > (assuming it finishes first and has consensus recommendations accepted by > the Council, etc.) even if the RPM Phase 1 Work is not done. So, this is > really related to Question 1 (see above). > > > > 1. Finally, your e-mail refers to “ALAC’s position as asserted to > ICANN GDD at ICANN65.” > 1. Is that position documented? And if so, can you please send the > position statement and rationale to this PDP Working Group for our review? > 2. When was the ALAC position communicated to ICANN GDD? > 3. Is there a transcript, presentation material, etc. of that > meeting and can they be sent to this Working Group for Review? > > > > I know these seem like a lot of questions, but I am assuming the e-mail > you sent us was a brief summary of the conclusion of the ALAC position and > it would be helpful for us to have all of the detail. > > > Thanks. > > > > *Jeffrey J. Neuman* > Senior Vice President > > > *Com Laude | Valideus *1751 Pinnacle Drive , Suite 600 > Mclean , VA 22102 > UNITED STATES > > T: +1.703.635.7514 > M: +1.202.549.5079 > > > > > > CONFIRMATION OF ORDERS: Please note that we always confirm receipt of > orders. To assist us in identifying orders, please use the word ORDER in > the subject line of your email. If you have sent us an order and have not > received confirmation on the same working day (PST) it is possible that > your order has not been received or has been trapped by our spam filter. > In this case, please contact your client manager or admin(a)comlaude.com > for confirmation that the order has been received and is being processed. > Thank you. > > > > *From:* Gnso-newgtld-wg <gnso-newgtld-wg-bounces(a)icann.org> *On Behalf Of > *John Laprise > *Sent:* Wednesday, July 10, 2019 10:20 PM > *To:* gnso-newgtld-wg(a)icann.org > *Cc:* 'ALAC Members' <ALAC-members(a)icann.org>; 'ICANN At-Large Staff' < > staff(a)atlarge.icann.org> > *Subject:* [Gnso-newgtld-wg] ALAC position on newgTLD subpro > > > > Hi everyone, > > > > Just a useful reminder of ALAC’s position as asserted to ICANN GDD at > ICANN65: > > > > ALAC will not support a new gTLD round until full implementation of CCT > and RPM recommendations are fully implemented. > > > > Best regards, > > > > John Laprise, Ph.D. > > NARALO ALAC Representative > > ALAC Vice Chair-Policy > > > ------------------------------ > The contents of this email and any attachments are confidential to the > intended recipient. They may not be disclosed, used by or copied in any way > by anyone other than the intended recipient. If you have received this > message in error, please return it to the sender (deleting the body of the > email and attachments in your reply) and immediately and permanently delete > it. Please note that the Com Laude Group does not accept any responsibility > for viruses and it is your responsibility to scan or otherwise check this > email and any attachments. The Com Laude Group does not accept liability > for statements which are clearly the sender's own and not made on behalf of > the group or one of its member entities. The Com Laude Group includes > Nom-IQ Limited t/a Com Laude, a company registered in England and Wales > with company number 5047655 and registered office at 28-30 Little Russell > Street, London, WC1A 2HN England; Valideus Limited, a company registered in > England and Wales with company number 06181291 and registered office at > 28-30 Little Russell Street, London, WC1A 2HN England; Demys Limited, a > company registered in Scotland with company number SC197176, having its > registered office at 33 Melville Street, Edinburgh, Lothian, EH3 7JF > Scotland; Consonum, Inc. dba Com Laude USA and Valideus USA, headquartered > at 1751 Pinnacle Drive, Suite 600, McLean, VA 22102, USA; Com Laude (Japan) > Corporation, a company registered in Japan having its registered office at > Suite 319,1-3-21 Shinkawa, Chuo-ku, Tokyo, 104-0033, Japan. For further > information see www.comlaude.com <https://comlaude.com> > > > > ---------- Forwarded message ---------- > From: Justine Chew <justine.chew(a)gmail.com> > To: Jeff Neuman <jeff.neuman(a)comlaude.com> > Cc: "gnso-newgtld-wg-sgb(a)icann.org" <gnso-newgtld-wg-sgb(a)icann.org>, > Olivier MJ Crepin-Leblond <ocl(a)gih.com>, Jonathan Zuck < > JZuck(a)innovatorsnetwork.org> > Bcc: > Date: Mon, 1 Apr 2019 14:18:28 +0000 > Subject: Re: [GNSO-NewGTLD-WG-SGB] ALAC responses to Sub-group B triage > exercise on Topics 2.7.5 IDNs and 2.7.8 Name Collisions > Hi Jeff, > > In reply to your request for further clarification, the ALAC is saying: > > The Subsequent Procedures WG can conclude its work, and implementation may > proceed, BUT EITHER ICANN may not launch the application window until the > NCAP study(ies) are completed and any recommendations resulting from those > study(ies) are addressed in implementation OR ICANN may launch the > application window and start the evaluation process, but no TLD may be > delegated until the NCAP Study(ies) is/are completed and any > recommendations resulting from those study(ies) are retroactively > incorporated. > > Kind regards, > > Justine Chew > ALAC liaison for Subsequent Procedures > ----- > > > On Mon, 25 Mar 2019 at 22:10, Jeff Neuman <jeff.neuman(a)comlaude.com> > wrote: > >> Thanks Justine and thanks to the ALAC. I have one further clarification >> question on Name Collisions: >> >> >> >> Below it states: “*Based on recent developments to the SSAC NCAP, the >> ALAC advocates for any implementation, if not development, of policy with >> respect to dealing with Names Collision, be subject to informed guidance >> from the SSAC NCAP Study 1, at the minimum, as well as Study 2 and Study 3 >> (if Studies 2 and 3 were to proceed), and that the policy allow for the >> implementation to take any NCAP recommendations into full account.”* >> >> >> >> This can be interpreted in a number of different ways. Is the ALAC >> saying: >> >> >> >> 1. SubPro should include a reference to the NCAP study(ies) in its >> Final Report and state that the implementation of the Next Round include >> recommendations (if any) from the that study (those studies) if and when >> those are made available. The New TLD Program can continue and launch, but >> just have a process to allow for changes due too the results of the NCAP >> Study(ies); or >> 2. SubPro should not complete its work in producing a final report >> until NCAP Study(ies) is/are completed; or >> 3. SubPro can conclude its work, but implementation cannot begin >> until the NCAP Study(ies) is/are completed; or >> 4. SubPro can conclude its work, implementation can continue, but >> ICANN may not launch the application window until the NCAP study(ies) are >> completed; or >> 5. SubPro can continue its work, implementation can complete, ICANN >> can launch the application window and go through the evaluation process, >> but the TLD may not be delegated until the NCAP Study(ies) is/are completed; >> 6. None of the above? >> >> >> >> As we get down to the wire it is going to be incredibly important to make >> sure that we are precise. All 5 options above could be consistent with >> the statement above. >> >> >> Thanks! >> >> >> >> *Jeff Neuman* >> >> Senior Vice President >> >> >> >> >> *Com Laude | Valideus *1751 Pinnacle Drive >> >> Suite 600, McLean >> >> VA 22102, USA >> >> >> M: +1.202.549.5079 >> >> D: +1.703.635.7514 >> >> E: *jeff.neuman(a)comlaude.com <jeff.neuman(a)comlaude.com>* >> www.comlaude.com >> >> >> Liability cannot be accepted for statements made which are clearly the >> sender’s own and not made on behalf of Com Laude USA or Valideus USA. This >> message is intended solely for the addressee and may contain confidential >> information. If you have received this message in error, please send it >> back to us, and immediately and permanently delete it. Do not use, copy or >> disclose the information contained in this message or in any attachment.Com >> Laude USA and Valideus are trading names of Consonum, Inc. >> >> >> >> *From:* GNSO-NewGTLD-WG-SGB <gnso-newgtld-wg-sgb-bounces(a)icann.org> *On >> Behalf Of *Justine Chew >> *Sent:* Sunday, March 24, 2019 10:05 PM >> *To:* gnso-newgtld-wg-sgb(a)icann.org >> *Cc:* Olivier MJ Crepin-Leblond <ocl(a)gih.com>; Jonathan Zuck < >> JZuck(a)innovatorsnetwork.org> >> *Subject:* [GNSO-NewGTLD-WG-SGB] ALAC responses to Sub-group B triage >> exercise on Topics 2.7.5 IDNs and 2.7.8 Name Collisions >> >> >> >> Dear all, >> >> Thank you for allowing the ALAC the opportunity and time to respond to >> the following alert and request for clarification on the topics of (I) >> 2.7..5 IDNs and (II) 2.7.8 Name Collisions, respectively. I thankfully had >> the opportunity to properly consult my colleagues during ICANN64 on the >> same and am now pleased to provide the following ALAC responses. >> >> I would be most grateful for an acknowledgment of receipt of this email, >> by leadership and/or staff, noting that Sub-group B has completed its work >> on 5 March, so that the ALAC can be assured these feedback will be taken >> into account accordingly in the upcoming deliberations of the Subsequent >> Procedures WG at the plenary level. >> >> >> * (I) 2.7.5 IDNs* >> At the Sub-group B's call of 20 February, Rubens Kuhl very kindly alerted >> us to a contradiction in ALAC's comment to *Q 2.7.5.e.2* and afforded an >> opportunity to remove the contradiction. The ALAC gratefully accepts the >> opportunity and wishes to re-state its comment as follows:- >> >> >> >> *The ALAC suggests that the "Same Entity Constraint" is enforced for all >> variants, ie all variants are either allocated to the same registrant as >> the primary label, or blocked. This would require registries (and possibly >> registrars) to implement the necessary checks during the registration >> process. Further, registrants may need to be educated about the reasons why >> such a constraint exists.* >> >> >> *(II) 2.7.8 Name Collisions* >> At the Sub-group B's call of 5 March, there was a request/action item for >> me to clarify the ALAC comment of "Wait on SSAC recommendations" to all >> preliminary recommendations and questions in section 2.7.8, except for >> 2.7.8.c.1. In response, the ALAC wishes to re-state its comment for >> clarity, and which is in line with its comment to preliminary >> recommendation 2.7.8.c.1, as follows:- >> >> *Based on recent developments to the SSAC NCAP, the ALAC advocates for >> any implementation, if not development, of policy with respect to dealing >> with Names Collision, be subject to informed guidance from the SSAC NCAP >> Study 1, at the minimum, as well as Study 2 and Study 3 (if Studies 2 and 3 >> were to proceed), and that the policy allow for the implementation to take >> any NCAP recommendations into full account. * >> >> >> FYI, I have copied Olivier Crepin-Leblond and Jonathan Zuck for their >> information, in their capacity as Co-Chairs of the At-Large Consolidated >> Policy Working Group (CPWG). >> >> Many thanks and kind regards, >> >> >> Justine Chew >> >> ALAC liaison for Subsequent Procedures >> >> >> ----- >> >> >> > >

1 0

Fwd: Re: Zoom Structural Vulnerability Discovered
by Marita Moll July 11, 2019

July 11, 2019

Hello all. I did bring up issues around the Zoom platform in early June and I have not yet had a chance to take the issues I see with the platform any further. But there is a robust discussion going on at NCSG with the idea below re: a joint recommendation from SO's/AC's for community input into the choices that are made about platform changes that affect us so profoundly. Perhaps we should indicate our support for this sort of action -- through our technology task force. Marita -------- Forwarded Message -------- Subject: Re: Zoom Structural Vulnerability Discovered Date: Wed, 10 Jul 2019 15:21:51 +0200 From: Jean-Jacques Subrenat <jjs(a)DYALOG.NET> Reply-To: Jean-Jacques Subrenat <jjs(a)DYALOG.NET> To: NCSG-DISCUSS(a)LISTSERV.SYR.EDU First, a remark: for Adobe, Zoom or other tool providers, ICANN may not be the single largest client, but it is certainly a significant one owing to its nature (quasi-regulatory, multi-stakeholder, some parts geared to non-commercial users). Then, a recommendation to Chairs of ACs and SOs: ICANN Board and CEO could be requested to set up a specifications sheet for a desirable conferencing tool, based on needs expressed by the multi-stakeholder community, and publish that as a tender. Offers received could then be reviewed not only by Staff, but in consultation with ACs and SOs. This would get us closer to what we, collectively, consider as the appropriate tool for the numerous conference calls held throughout ICANN. Jean-Jacques Subrenat. Le 10 juillet 2019 à 14:46:20, Paul Rosenzweig (paul.rosenzweig(a)redbranchconsulting.com <mailto:paul.rosenzweig@redbranchconsulting.com>) a écrit: > This is assuredly right. The change from Adobe to Zoom may, or may > not, have been right for ICANN and for this group for any number of > reasons ranging from cost, to security, to scalability and utility. > But let’s not romanticize Adobe. They are not a terribly secure > platform generically. As James said, the Zoom response is poor – but > we can’t hang that around the neck of ICANN org. > > P > > Paul Rosenzweig > > paul.rosenzweig(a)redbranchconsulting.com > <mailto:paul.rosenzweig@redbranchconsulting.com> > > O: +1 (202) 547-0660 > > M: +1 (202) 329-9650 > > VOIP: +1 (202) 738-1739 > > www.redbranchconsulting.com <http://www.redbranchconsulting.com/> > > My PGP Key: > https://keys.mailvelope.com/pks/lookup?op=get&search=0x9A830097CA066684 > > *From:* NCSG-Discuss <NCSG-DISCUSS(a)LISTSERV.SYR.EDU> *On Behalf Of > *James Gannon > *Sent:* Wednesday, July 10, 2019 12:52 AM > *To:* NCSG-DISCUSS(a)LISTSERV.SYR.EDU > *Subject:* Re: Zoom Structural Vulnerability Discovered > > Just want to call out that Adobe has likely the worst reputation in > the entire tech industry when it comes to security, I really would not > hold them out as either prompt or without serious issues (I believe > they still hold the record for number of CVSS 9+ vulns). > > Zooms response is poor I agree, but on a data driven comparison it is > a far more secure platform. > > *From: *NCSG-Discuss <NCSG-DISCUSS(a)LISTSERV.SYR.EDU > <mailto:NCSG-DISCUSS@LISTSERV.SYR.EDU>> on behalf of Ayden Férdeline > <icann(a)FERDELINE.COM <mailto:icann@FERDELINE.COM>> > *Reply-To: *Ayden Férdeline <icann(a)FERDELINE.COM > <mailto:icann@FERDELINE.COM>> > *Date: *Tuesday, 9 July 2019 at 14:13 > *To: *"NCSG-DISCUSS(a)LISTSERV.SYR.EDU > <mailto:NCSG-DISCUSS@LISTSERV.SYR.EDU>" <NCSG-DISCUSS(a)LISTSERV.SYR.EDU > <mailto:NCSG-DISCUSS@LISTSERV.SYR.EDU>> > *Subject: *Re: Zoom Structural Vulnerability Discovered > > That is true, but note that this security researcher notified Zoom of > the exploit and they were in no rush to repair it. Look at the > timeline in the Medium post. They only sought to fix it after the > vulnerability drew media attention. > > Adobe Connect was not perfect but it met our needs and the occasional > security issues that arose were promptly fixed by Adobe and never as > serious as this one! > > Best wishes, Ayden > > On Tue, Jul 9, 2019 at 18:07, Adeel Sadiq <11beeasadiq(a)seecs.edu.pk > <mailto:11beeasadiq@seecs.edu.pk>> wrote: > > Speaking from a technical perspective, no software is perfect or > bug-free. Its only a matter of time a loophole is found and > exploited and eventually patched up. If you think Adobe Connect or > ezTalks were/are free of these architectural issues, think again! > That's the way we technical community do things. > > Regards > > Adeel > > Pakistan > > On Wed, Jul 10, 2019 at 1:37 AM Ayden Férdeline > <icann(a)ferdeline.com <mailto:icann@ferdeline.com>> wrote: > > Unfortunately, uninstalling the application does not rectify > the situation, due to poor architecture (acknowledged by Zoom > on their blog today). They are working on a fix, now that > public scrutiny demands one. So disappointing that ICANN has > put us in this terrible situation. > > Ayden > > On Tue, Jul 9, 2019 at 16:15, Vaibhav Aggarwal, Catalyst & > Group CEO <va(a)BLADEBRAINS.COM <mailto:va@BLADEBRAINS.COM>> wrote: > > Thanks for this. Till the next Update, I have removed the > Zoom For Mac Client with immediate effect. > > Regards, > > Vaibhav Aggarwal > > New Delhi > > VaibhavAggarwal.com <http://VaibhavAggarwal.com> > > On Jul 10, 2019, at 12:30 AM, Michael Karanicolas > <mkaranicolas(a)GMAIL.COM > <mailto:mkaranicolas@GMAIL.COM>> wrote: > > Hey - remember when ICANN switched everyone from Adobe > over to Zoom as a way of enhancing information > security and data privacy? > > "A vulnerability in the Mac Zoom Client allows any > malicious website to enable your camera without your > permission... This vulnerability allows any website to > forcibly join a user to a Zoom call, with their video > camera activated, without the user's permission. On > top of this, this vulnerability would have allowed any > webpage to DOS (Denial of Service) a Mac by repeatedly > joining a user to an invalid call. Additionally, if > you’ve ever installed the Zoom client and then > uninstalled it, you still have a localhost web server > on your machine that will happily re-install the Zoom > client for you, without requiring any user interaction > on your behalf besides visiting a webpage. This > re-install ‘feature’ continues to work to this day." > > Read more here: > https://medium.com/@jonathan.leitschuh/zoom-zero-day-4-million-webcams-mayb… >

2 6

Meeting invitation: At-Large Consolidated Policy Working Group (CPWG) Call on Wednesday, 17 July 2019 at 13:00 UTC
by ICANN At-Large Staff July 10, 2019

July 10, 2019

Dear All, The next At-Large Consolidated Policy Working Group (CPWG) Call is scheduled for Wednesday, 17 July 2019 at 13:00 UTC for 90 mins. For other times: https://tinyurl.com/y3s3gomp The agenda (to be updated) and call details can be found at: https://community.icann.org/x/BKqjBg Zoom Room: https://icann.zoom.us/j/318373383 /<https://icann.zoom.us/j/318373383%20/> Meeting ID: 318-373-383 ADIGO Conference Bridge: EN: 1638 ES: 1738 Toll-free access number (US and Canada): 800 550 6865 Other toll-free numbers: https://www.adigo.com/icann At-Large Consolidated Policy Working Group (CPWG) Wiki Space: https://community.icann.org/x/jYDpB If you require a dial-out please contact At-Large staff at: staff(a)atlarge.icann.org<mailto:staff@atlarge.icann.org> Thank you. Kind regards, At-Large Staff ICANN Policy Staff in support of the At-Large Community Website: atlarge.icann.org<https://atlarge.icann.org/> Facebook: facebook.com/icann<https://www.facebook.com/icannatlarge>atlarge<https://www.facebook.com/icannatlarge> Twitter: @<https://twitter.com/ICANNAtLarge>ICANNAtLarge<https://twitter.com/ICANNAtLarge>

1 0

At-Large Consolidated Policy Working Group (CPWG) Call
by ICANN Policy Calendar July 10, 2019

July 10, 2019

Dear All, The next At-Large Consolidated Policy Working Group (CPWG) Call is scheduled for Wednesday, 17 July 2019 at 13:00 UTC for 90 mins. For other times: https://tinyurl.com/y3s3gomp The agenda (to be updated) and call details can be found at: https://community.icann.org/x/BKqjBg Zoom Room: https://icann.zoom.us/j/318373383 /<https://icann.zoom.us/j/318373383%20/> Meeting ID: 318-373-383 ADIGO Conference Bridge: EN: 1638 ES: 1738 Toll-free access number (US and Canada): 800 550 6865 Other toll-free numbers: https://www.adigo.com/icann At-Large Consolidated Policy Working Group (CPWG) Wiki Space: https://community.icann.org/x/jYDpB If you require a dial-out please contact At-Large staff at: staff(a)atlarge.icann.org<mailto:staff@atlarge.icann.org> Thank you. Kind regards, At-Large Staff ICANN Policy Staff in support of the At-Large Community Website: atlarge.icann.org<https://atlarge.icann.org/> Facebook: facebook.com/icann<https://www.facebook.com/icannatlarge>atlarge<https://www.facebook.com/icannatlarge> Twitter: @<https://twitter.com/ICANNAtLarge>ICANNAtLarge<https://twitter.com/ICANNAtLarge>

1 0

****CALL ON IN 15 MINUTES****Meeting Invitation: At-Large Consolidated Policy Working Group (CPWG) Call on Wednesday, 10 July 2019 at 19:00 UTC for 90 mins
by ICANN At-Large Staff July 10, 2019

July 10, 2019

Dear All, The next At-Large Consolidated Policy Working Group (CPWG) Call is scheduled for Wednesday, 10 July 2019 at 19:00 UTC for 90 mins. For other times: https://tinyurl.com/y6aefcwx The agenda (to be updated) and call details can be found at: https://community.icann.org/x/jqWjBg Zoom Room: https://icann.zoom.us/j/143724036 ADIGO Conference Bridge: EN: 1638 ES: 1738 Toll-free access number (US and Canada): 800 550 6865 Other toll-free numbers: https://www.adigo.com/icann At-Large Consolidated Policy Working Group (CPWG) Wiki Space: https://community.icann.org/x/jYDpB If you require a dial-out please contact At-Large staff at: staff(a)atlarge.icann.org<mailto:staff@atlarge.icann.org> Thank you. Kind regards, At-Large Staff ICANN Policy Staff in support of the At-Large Community Website: atlarge.icann.org<https://atlarge.icann.org/> Facebook: facebook.com/icann<https://www.facebook.com/icannatlarge>atlarge<https://www.facebook.com/icannatlarge> Twitter: @<https://twitter.com/ICANNAtLarge>ICANNAtLarge<https://twitter.com/ICANNAtLarge>

1 0

Meeting Invitation: At-Large Consolidated Policy Working Group (CPWG) Call on Wednesday, 10 July 2019 at 19:00 UTC for 90 mins
by ICANN At-Large Staff July 10, 2019

July 10, 2019

Dear All, The next At-Large Consolidated Policy Working Group (CPWG) Call is scheduled for Wednesday, 10 July 2019 at 19:00 UTC for 90 mins. For other times: https://tinyurl.com/y6aefcwx The agenda (to be updated) and call details can be found at: https://community.icann.org/x/jqWjBg Zoom Room: https://icann.zoom.us/j/143724036 ADIGO Conference Bridge: EN: 1638 ES: 1738 Toll-free access number (US and Canada): 800 550 6865 Other toll-free numbers: https://www.adigo.com/icann At-Large Consolidated Policy Working Group (CPWG) Wiki Space: https://community.icann.org/x/jYDpB If you require a dial-out please contact At-Large staff at: staff(a)atlarge.icann.org<mailto:staff@atlarge.icann.org> Thank you. Kind regards, At-Large Staff ICANN Policy Staff in support of the At-Large Community Website: atlarge.icann.org<https://atlarge.icann.org/> Facebook: facebook.com/icann<https://www.facebook.com/icannatlarge>atlarge<https://www.facebook.com/icannatlarge> Twitter: @<https://twitter.com/ICANNAtLarge>ICANNAtLarge<https://twitter.com/ICANNAtLarge>

2 1

Evolving the Governance of the Root Server System
by Olivier MJ Crépin-Leblond July 9, 2019

July 9, 2019

Dear Colleagues, having reviewed the documentation relating to the Public Comment "Evolving the Governance of the Root Server System", I invite you to read my comment on https://community.icann.org/x/2IajBg This is a significant change in the way the world's 13 Root Servers work. It is likely to bring a more stable and scalable Internet Root Server System in the future. It is likely to bring a more coordinated Internet Root Server System with bottom-up, multistakeholder policy development. It is also likely to cost more money - with the source of funding being ICANN. Kindest regards, Olivier

2 1