<div dir="ltr"><div dir="ltr"><div dir="ltr">Hey all, <div><br></div><div>Hope this email finds you well! </div><div><br></div><div>I am writing just to inform you that NCSG has joined the planning teams of the two plenary sessions of ICANN70, and I highlight below important points regarding the RVCs Plenary Session initial planning meeting<span style="color:rgb(32,33,36);font-family:arial,sans-serif;font-size:14px">:</span></div><div><font color="#202124" face="arial, sans-serif"><br></font></div><div><font color="#202124" face="arial, sans-serif"><b>1. Registry Voluntary Commitments </b></font></div><div><font color="#202124" face="arial, sans-serif">Main outcome would be to discuss enforceable mechanisms for contracted parties to make commitments to the community, enforced by ICANN contract compliance and so forth. Session will also present a short discussion on PICs after the 2012 round and the Subpro process that took us to today's moment of RVCs. </font></div><div><font color="#202124" face="arial, sans-serif"><span style="font-size:14px"><br></span></font></div><div><font color="#202124" face="arial, sans-serif"><b>Introduction</b> - History of PICs and RVCs </font>(Jeff Neuman)</div><div><font color="#202124" face="arial, sans-serif"><br></font></div><div><font color="#202124" face="arial, sans-serif"><b>Guiding questions</b></font></div><div><span id="gmail-docs-internal-guid-51eedeb8-7fff-c445-9a62-1d7f2ea9c4ce"><ol style="margin-top:0px;margin-bottom:0px"><li dir="ltr" style="list-style-type:decimal;font-family:Arial;color:rgb(0,0,0);background-color:transparent;font-variant-numeric:normal;font-variant-east-asian:normal;vertical-align:baseline;white-space:pre"><p dir="ltr" style="line-height:1.38;margin-top:0pt;margin-bottom:0pt"><span style="background-color:transparent;font-variant-numeric:normal;font-variant-east-asian:normal;vertical-align:baseline;white-space:pre-wrap">On the assumption that PICs/RVCs are the main mechanism for Contracted Parties to make enforceable commitments to the ICANN community (or public), are there limits on their enforceability, e.g. under the ICANN Bylaws?</span></p></li><li dir="ltr" style="list-style-type:decimal;font-family:Arial;color:rgb(0,0,0);background-color:transparent;font-variant-numeric:normal;font-variant-east-asian:normal;vertical-align:baseline;white-space:pre"><p dir="ltr" style="line-height:1.38;margin-top:0pt;margin-bottom:0pt"><span style="background-color:transparent;font-variant-numeric:normal;font-variant-east-asian:normal;vertical-align:baseline;white-space:pre-wrap">Are there specific challenges with enforcing PICs/RVCs as part of the Registry Agreement (i.e. binding contract that all gTLD registry operators enter into with ICANN)? </span></p></li><ol style="margin-top:0px;margin-bottom:0px"><li dir="ltr" style="list-style-type:lower-alpha;font-family:Arial;color:rgb(0,0,0);background-color:transparent;font-variant-numeric:normal;font-variant-east-asian:normal;vertical-align:baseline;white-space:pre"><p dir="ltr" style="line-height:1.38;margin-top:0pt;margin-bottom:0pt"><span style="background-color:transparent;font-variant-numeric:normal;font-variant-east-asian:normal;vertical-align:baseline;white-space:pre-wrap">Panelists should give real-life examples if possible.</span></p></li></ol><li dir="ltr" style="list-style-type:decimal;font-family:Arial;color:rgb(0,0,0);font-variant-numeric:normal;font-variant-east-asian:normal;vertical-align:baseline;white-space:pre"><p dir="ltr" style="line-height:1.38;margin-top:0pt;margin-bottom:0pt"><span style="background-color:transparent;font-variant-numeric:normal;font-variant-east-asian:normal;vertical-align:baseline;white-space:pre-wrap">What are the education gaps that ICANN org, Contracted Parties, or other parties (if any) should</span><span style="background-color:rgb(255,255,255)"><span style="font-variant-numeric:normal;font-variant-east-asian:normal;vertical-align:baseline;white-space:pre-wrap"> be addressing </span><span style="font-variant-numeric:normal;font-variant-east-asian:normal;vertical-align:baseline;white-space:pre-wrap">prior to further gTLD expansion</span><span style="font-variant-numeric:normal;font-variant-east-asian:normal;vertical-align:baseline;white-space:pre-wrap">?</span></span></p></li><li dir="ltr" style="list-style-type:decimal;font-family:Arial;color:rgb(0,0,0);background-color:transparent;font-variant-numeric:normal;font-variant-east-asian:normal;vertical-align:baseline;white-space:pre"><p dir="ltr" style="line-height:1.38;margin-top:0pt;margin-bottom:0pt"><span style="background-color:transparent;font-variant-numeric:normal;font-variant-east-asian:normal;vertical-align:baseline;white-space:pre-wrap">How can enforcement of PICs/RVCs be framed to avoid the risk that ICANN org will need to make potential decisions on content? </span></p></li><ol style="margin-top:0px;margin-bottom:0px"><li dir="ltr" style="list-style-type:lower-alpha;font-family:Arial;color:rgb(0,0,0);background-color:transparent;font-variant-numeric:normal;font-variant-east-asian:normal;vertical-align:baseline;white-space:pre"><p dir="ltr" style="line-height:1.38;margin-top:0pt;margin-bottom:0pt"><span style="background-color:transparent;font-variant-numeric:normal;font-variant-east-asian:normal;vertical-align:baseline;white-space:pre-wrap">What registrant rights or interests need to be protected?</span></p></li><li dir="ltr" style="list-style-type:lower-alpha;font-family:Arial;color:rgb(0,0,0);background-color:transparent;font-variant-numeric:normal;font-variant-east-asian:normal;vertical-align:baseline;white-space:pre"><p dir="ltr" style="line-height:1.38;margin-top:0pt;margin-bottom:0pt"><span style="background-color:transparent;font-variant-numeric:normal;font-variant-east-asian:normal;vertical-align:baseline;white-space:pre-wrap">What practical options can panelists suggest?</span></p></li></ol></ol></span></div><div><br></div><div>This session shall have discussants, and I have secured a slot for NCSG, but I have the deadline until friday to inform staff about who our discussant will be. </div><div><font color="#202124" face="arial, sans-serif"><span style="font-size:14px"><br clear="all"></span></font><div></div></div><div><font color="#202124" face="arial, sans-serif"><span style="font-size:14px">best, </span></font></div><div><br></div><div>-- <br><div dir="ltr" class="gmail_signature"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div><b><i>Bruna Martins dos Santos <br></i></b><div dir="ltr" style="color:rgb(34,34,34)"><br></div><p style="color:rgb(34,34,34);margin:0cm 0cm 0.0001pt"><span style="font-family:arial,sans-serif"><font color="#000000"><span style="font-size:11px"></span></font></span></p><p style="color:rgb(34,34,34);margin:0cm 0cm 0.0001pt"><font size="2"><span style="font-family:arial,sans-serif"><font color="#000000">Advocacy Coordinator | <a href="https://www.dataprivacybr.org/en/" target="_blank">Data Privacy Brazil Research</a></font></span></font></p><p style="color:rgb(34,34,34);margin:0cm 0cm 0.0001pt"><font size="2"><span style="font-family:arial,sans-serif"><font color="#000000">Member | <a href="https://direitosnarede.org.br/" target="_blank">Coalizão Direitos na Rede</a> <br>Chair</font></span></font><span style="color:rgb(0,0,0);font-family:arial,sans-serif"> | <a href="https://gnso.icann.org/en/about/stakeholders-constituencies/ncsg" target="_blank">Non-Commercial Stakeholder Group at ICANN</a><br></span><font size="2"><span style="font-family:arial,sans-serif"><font color="#000000">Co-Coordinator</font></span></font><span style="color:rgb(0,0,0);font-family:arial,sans-serif"> | <a href="https://igcaucus.org/" target="_blank">Internet Governance Caucus </a><br></span><font size="2"><span style="font-family:arial,sans-serif"><font color="#000000"><br></font></span></font></p><div style="color:rgb(34,34,34)"><span style="font-family:arial,sans-serif"><font size="1" color="#000000"><font size="2">Twitter: <a href="https://twitter.com/boomartins" target="_blank"><font color="#1155cc">@</font>boomartins</a> // </font></font></span><span style="color:rgb(32,33,36)">Skype: bruna.martinsantos</span></div></div><div><font size="1"><a href="mailto:bruna@dataprivacybr.org" target="_blank">bruna@dataprivacybr.org</a> and <a href="mailto:bruna.mrtns@gmail.com" target="_blank">bruna.mrtns@gmail.com</a></font></div></div></div></div></div></div></div></div></div></div></div>