<div dir="auto"><div dir="ltr">Dear Laura, Hadia, Justine, <div>thank you for this very useful, a comprehensive updates, your reports/work.</div><div dir="auto"><br></div><div dir="auto"><br clear="all"><div dir="auto"><div dir="ltr" class="gmail_signature" data-smartmail="gmail_signature"><div dir="ltr">Best regards, <br>Natalia Filina<div><br></div><div>Moscow, Russia</div><div><span></span><span></span><br></div><div><br></div><div><div><br></div></div></div></div></div><br></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">вт, 20 февр. 2024 г. в 13:47, Hadia El Miniawi via ALAC <<a href="mailto:alac@atlarge-lists.icann.org" target="_blank" rel="noreferrer">alac@atlarge-lists.icann.org</a>>:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div><div style="font-family:"times new roman","new york",times,serif;font-size:13px"><div style="font-family:"times new roman","new york",times,serif;font-size:13px"></div>
<div dir="ltr" style="text-align:justify"><font face="Arial, sans-serif"><span style="font-size:14.6667px">Dear All,</span></font></div><div dir="ltr" style="text-align:justify"><font face="Arial, sans-serif"><span style="font-size:14.6667px"><br></span></font></div><div dir="ltr" style="text-align:justify"><font face="Arial, sans-serif"><span style="font-size:14.6667px">Thank you Laura for the update.</span></font></div><div dir="ltr" style="text-align:justify"><font face="Arial, sans-serif"><span style="font-size:14.6667px"><br></span></font></div><div dir="ltr" style="text-align:justify"><font face="Arial, sans-serif"><span style="font-size:14.6667px">With regard to the IDN EPDP for gTLD and the ccNSO IDN PDP4. </span></font><span style="font-family:Arial,sans-serif;font-size:14.6667px">The issue pertaining to who develops the charter was discussed extensively during the past calls of both the IDN EPDP for gTLD and the ccNSO IDN PDP4. According to the IDN EPDP for gTLD ICANN board IDN-UA working group would be responsible for developing the charter. At the time this issue was discussed during the ccNSO PDP4 call, this was not fully clear to the ccNSO IDN PDP4 members. </span></div><div dir="ltr" style="font-family:"times new roman","new york",times,serif;font-size:13px"><span><span style="color:rgb(0,0,0);font-family:Arial,sans-serif;font-size:14.6667px;text-align:justify"><br></span></span></div><div dir="ltr" style="font-family:"times new roman","new york",times,serif;font-size:13px"><span><div><div dir="ltr" style="color:rgb(0,0,0);font-family:"times new roman","new york",times,serif"><span style="font-family:Arial,sans-serif;font-size:14.6667px;text-align:justify"><span id="m_-6632908772588911006m_1631441651493603189ydp8fac5bbdocs-internal-guid-755611c1-7fff-5fd5-3f5d-4e82b021f431"><span style="font-size:11pt;background-color:transparent;vertical-align:baseline">The IDN EPDP for gTLD working group has been working on refining the recommendation. Consequently, the new recommendation makes it clear that CANN Board IDN-UA Working Group (IDN-UA WG) or its relevant successor will be responsible for developing the f<span id="m_-6632908772588911006m_1631441651493603189ydp263c532fdocs-internal-guid-9fdff76d-7fff-dfc1-d775-e225dbdf9357"><span style="font-size:11pt;background-color:transparent;vertical-align:baseline">ormal charter for the community group that will develop future versions of the IDN Implementation Guidelines. (Recommendation 14.1)</span></span></span></span></span><br></div><div><span style="font-family:Arial,sans-serif;font-size:14.6667px;text-align:justify"><span><span style="font-size:11pt;background-color:transparent;vertical-align:baseline"><span><span style="font-size:11pt;background-color:transparent;vertical-align:baseline"><br></span></span></span></span></span></div></div></span></div><div dir="ltr" style="font-family:"times new roman","new york",times,serif;font-size:13px"><span style="font-family:Arial,sans-serif;font-size:14.6667px;text-align:justify">As a result, I believe that the concerns raised by the ccNSO IDN PDP4 members regarding the charter and the potential "egg and chicken" problem has been addressed.</span><br></div><div dir="ltr" style="text-align:justify"><font face="Arial, sans-serif"><span style="font-size:14.6667px"><br></span></font></div><div dir="ltr" style="text-align:justify"><font face="Arial, sans-serif"><span style="font-size:14.6667px">Kind regards</span></font></div><div dir="ltr" style="text-align:justify"><font face="Arial, sans-serif"><span style="font-size:14.6667px">Hadia </span></font></div><div style="font-family:"times new roman","new york",times,serif;font-size:13px"><br></div>
</div><div id="m_-6632908772588911006m_1631441651493603189ydp83cbb2d8yahoo_quoted_8512605737">
<div style="font-family:"Helvetica Neue",Helvetica,Arial,sans-serif;font-size:13px;color:rgb(38,40,42)">
<div>
On Monday, February 19, 2024 at 01:05:55 PM GMT+2, Justine Chew via ALAC <<a href="mailto:alac@atlarge-lists.icann.org" target="_blank" rel="noreferrer">alac@atlarge-lists.icann.org</a>> wrote:
</div>
<div><br></div>
<div><br></div>
<div><div id="m_-6632908772588911006m_1631441651493603189ydp83cbb2d8yiv2630893025"><div><div dir="ltr">Thank you for this report, Laura. <br clear="none"><br clear="none">I'm sure Satish, Hadia and AK will also bring us up to speed with GNSO EPDP on IDNs Phase 2 preliminary recommendations and the proposed approach for the updating the IDN Implementation Guidelines from the gTLD perspective to complement your update.<br clear="all"><div><div dir="ltr"><div dir="ltr"><br clear="none"><font color="#000000">Kind regards,</font><br clear="none"><font color="#000000">Justine</font><br clear="none"><b><br clear="none"></b></div></div></div><br clear="none"></div><br clear="none"><div><div id="m_-6632908772588911006m_1631441651493603189ydp83cbb2d8yiv2630893025yqt78140"><div dir="ltr">On Mon, 19 Feb 2024 at 12:03, Laura Margolis via ALAC <<a shape="rect" href="mailto:alac@atlarge-lists.icann.org" rel="nofollow noreferrer" target="_blank">alac@atlarge-lists.icann.org</a>> wrote:<br clear="none"></div><blockquote style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr">Dear All:<div><br clear="none"></div><div>ccNSO Council meeting #202 was held on February 15th.</div><div><br clear="none"></div><div>Here is the full <a shape="rect" href="https://community.icann.org/display/atlarge/ALAC+Liaison+to+the+ccNSO+Reports?preview=/2262570/305299478/Agenda%20meeting%20202%2015%20February%202024%20v1.pdf" rel="nofollow noreferrer" target="_blank">agenda</a> and <a shape="rect" href="https://community.icann.org/display/atlarge/ALAC+Liaison+to+the+ccNSO+Reports?preview=/2262570/305299478/Agenda%20meeting%20202%2015%20February%202024%20v1.pdf" rel="nofollow noreferrer" target="_blank">notes</a>.</div><div><br clear="none"></div><div>I would like to highlight some important updates regarding ccPDP4:</div><div><br clear="none"></div><div><b>Updates on <a shape="rect" href="https://ccnso.icann.org/en/workinggroups/idn-cctld-strings.htm" rel="nofollow noreferrer" target="_blank">ccPDP4</a></b></div><div><br clear="none"></div><div><p style="margin:0cm;text-align:justify;line-height:normal;background-image:initial;background-position:initial;background-size:initial;background-repeat:initial;vertical-align:baseline;font-size:11pt;font-family:Calibri,sans-serif"><b><span style="font-family:Arial,sans-serif;color:black">a.</span></b><b><span style="font-size:7pt;font-family:"New serif";color:black"> </span></b><b><i><span style="font-family:Arial,sans-serif;color:black">Progress and expected
timeline ccNSO Decision making</span></i></b></p><p style="margin:0cm;text-align:justify;line-height:normal;background-image:initial;background-position:initial;background-size:initial;background-repeat:initial;vertical-align:baseline;font-size:11pt;font-family:Calibri,sans-serif"><b><i><span style="font-family:Arial,sans-serif;color:black"><br clear="none"></span></i></b></p><p style="margin:0cm;text-align:justify;line-height:normal;background-image:initial;background-position:initial;background-size:initial;background-repeat:initial;vertical-align:baseline;font-size:11pt;font-family:Calibri,sans-serif"><span style="color:black;font-family:Arial,sans-serif;font-size:11pt">The ccPDP4 WG expects to
complete its work by 20 February 2024, and the Issue manager will submit
the report prior to ICANN79 for consideration and decision making by the
Council. </span><b style="color:black;font-family:Arial,sans-serif;font-size:11pt">The Final report does include both policy recommendations</b><span style="color:black;font-family:Arial,sans-serif;font-size:11pt"> </span><b style="color:black;font-family:Arial,sans-serif;font-size:11pt">and
advice to ccTLDs</b><span style="color:black;font-family:Arial,sans-serif;font-size:11pt">. The advice is on topics that were considered out of scope
of the PDP by the WG, and the decision-making process is not defined through
Annex B of the Bylaws, but through the Internal rules of the ccNSO. </span></p><p style="margin:0cm 0cm 0cm 72pt;text-align:justify;line-height:normal;background-image:initial;background-position:initial;background-size:initial;background-repeat:initial;font-size:11pt;font-family:Calibri,sans-serif"><span style="font-size:12pt;font-family:Arial,sans-serif"></span></p>
<p style="margin:0cm;line-height:normal;background-image:initial;background-position:initial;background-size:initial;background-repeat:initial;font-size:11pt;font-family:Calibri,sans-serif"><span style="font-size:12pt;font-family:Arial,sans-serif"> </span></p>
<p style="margin:0cm;text-align:justify;line-height:normal;background-image:initial;background-position:initial;background-size:initial;background-repeat:initial;font-size:11pt;font-family:Calibri,sans-serif"><b><span style="font-family:Arial,sans-serif;color:black">Two different tracks</span></b><span style="font-family:Arial,sans-serif;color:black">: </span></p>
<p style="margin:0cm;text-align:justify;line-height:normal;background-image:initial;background-position:initial;background-size:initial;background-repeat:initial;font-size:11pt;font-family:Calibri,sans-serif"><span style="font-size:11pt;font-family:Arial,sans-serif;color:black">1)<span style="font-stretch:normal;font-size:7pt;line-height:normal;font-family:New">
</span></span><span style="font-size:11pt;font-family:Arial,sans-serif;color:black"> <b>Set of policy
recommendations</b>.</span></p><p style="margin:0cm;text-align:justify;line-height:normal;background-image:initial;background-position:initial;background-size:initial;background-repeat:initial;font-size:11pt;font-family:Calibri,sans-serif"><span style="color:black;font-family:Arial,sans-serif;font-size:11pt">That was the task of the
WG, to develop this policy and propose it.</span></p><p style="margin:0cm;text-align:justify;line-height:normal;background-image:initial;background-position:initial;background-size:initial;background-repeat:initial;font-size:11pt;font-family:Calibri,sans-serif"><span style="font-size:12pt;font-family:Arial,sans-serif">2)<span style="font-stretch:normal;font-size:7pt;line-height:normal;font-family:New"> </span></span><span style="font-size:11pt;font-family:Arial,sans-serif;color:black"> <b>Advice to ccTLD managers</b>.</span></p><p style="margin:0cm;text-align:justify;line-height:normal;background-image:initial;background-position:initial;background-size:initial;background-repeat:initial;font-size:11pt;font-family:Calibri,sans-serif"><span style="color:black;font-family:Arial,sans-serif;font-size:11pt">Submitting IDN tables for
second level domains.</span></p><p style="margin:0cm;text-align:justify;line-height:normal;background-image:initial;background-position:initial;background-size:initial;background-repeat:initial;font-size:11pt;font-family:Calibri,sans-serif"><span style="color:black;font-family:Arial,sans-serif;font-size:11pt">Secondly, about </span><b style="color:black;font-family:Arial,sans-serif;font-size:11pt">registering
IDN domain names and variants to the same entity</b><span style="color:black;font-family:Arial,sans-serif;font-size:11pt">.</span></p><p style="margin:0cm;text-align:justify;line-height:normal;background-image:initial;background-position:initial;background-size:initial;background-repeat:initial;font-size:11pt;font-family:Calibri,sans-serif"><span style="color:black;font-family:Arial,sans-serif;font-size:11pt"><br clear="none"></span></p><p style="margin:0cm;text-align:justify;line-height:normal;background-image:initial;background-position:initial;background-size:initial;background-repeat:initial;font-size:11pt;font-family:Calibri,sans-serif"><span style="color:black;font-family:Arial,sans-serif;font-size:11pt">It will have 2 sides: one
is for </span><b style="color:black;font-family:Arial,sans-serif;font-size:11pt">policy making</b><span style="color:black;font-family:Arial,sans-serif;font-size:11pt">. As per the ccPDP process. First council will be asked
to support the recommendations, and then the membership, before being sent to
board.</span></p><p style="margin:0cm 0cm 0cm 36pt;text-align:justify;line-height:normal;background-image:initial;background-position:initial;background-size:initial;background-repeat:initial;font-size:11pt;font-family:Calibri,sans-serif"><span style="font-size:12pt;font-family:Arial,sans-serif"></span></p>
<p style="margin:0cm 0cm 0cm 36pt;text-align:justify;line-height:normal;background-image:initial;background-position:initial;background-size:initial;background-repeat:initial;font-size:11pt;font-family:Calibri,sans-serif"><span style="font-size:12pt;font-family:Arial,sans-serif"> </span></p>
<p style="margin:0cm;text-align:justify;line-height:normal;background-image:initial;background-position:initial;background-size:initial;background-repeat:initial;font-size:11pt;font-family:Calibri,sans-serif"><span style="font-family:Arial,sans-serif;color:black">The advice is governed by the internal rules of the ccNSO.
That will be a council decision, with the option to have a veto by the members.
There is also a proposed timeline for the member's vote. After the June’s
meeting, the recommendations can be submitted to the board.</span></p>
<p style="margin:0cm;text-align:justify;line-height:normal;background-image:initial;background-position:initial;background-size:initial;background-repeat:initial;font-size:11pt;font-family:Calibri,sans-serif"><span style="font-family:Arial,sans-serif;color:black"> </span></p>
<p style="margin:0cm;text-align:justify;line-height:normal;background-image:initial;background-position:initial;background-size:initial;background-repeat:initial;font-size:11pt;font-family:Calibri,sans-serif"><span style="font-family:Arial,sans-serif;color:black"><u>Note: </u></span></p><p style="margin:0cm;text-align:justify;line-height:normal;background-image:initial;background-position:initial;background-size:initial;background-repeat:initial;font-size:11pt;font-family:Calibri,sans-serif"><span style="font-family:Arial,sans-serif;color:black">2 types of decisions</span></p><p style="margin:0cm;text-align:justify;line-height:normal;background-image:initial;background-position:initial;background-size:initial;background-repeat:initial;font-size:11pt;font-family:Calibri,sans-serif"><span style="font-size:10pt;font-family:Symbol;color:black">·<span style="font-stretch:normal;font-size:7pt;line-height:normal;font-family:New"> </span></span><span style="font-size:11pt;font-family:Arial,sans-serif;color:black">One within the context of
the PDP itself</span></p><p style="margin:0cm;text-align:justify;line-height:normal;background-image:initial;background-position:initial;background-size:initial;background-repeat:initial;font-size:11pt;font-family:Calibri,sans-serif"><span style="font-size:10pt;font-family:Symbol">·<span style="font-stretch:normal;font-size:7pt;line-height:normal;font-family:New"> </span></span><span style="font-size:11pt;font-family:Arial,sans-serif;color:black">Second one out of scope of
the PDP, and will be a regular resolution.</span></p>
<p style="margin:0cm 0cm 8pt;line-height:107%;font-size:11pt;font-family:Calibri,sans-serif"><b><span style="font-size:14pt;line-height:107%"> </span></b><b style="font-size:11pt"><span style="font-size:14pt;line-height:107%"> </span></b></p>
<p style="margin:0cm;text-align:justify;line-height:normal;background-image:initial;background-position:initial;background-size:initial;background-repeat:initial;vertical-align:baseline;font-size:11pt;font-family:Calibri,sans-serif"><b><span style="font-family:Arial,sans-serif;color:black">b.</span></b><b><span style="font-size:7pt;font-family:"New serif";color:black"> </span></b><b><i><span style="font-family:Arial,sans-serif;color:black">Discussion and views Draft
Recommendation 14 on participation of ccNSO in developing IDN Guidelines.</span></i></b><span style="font-size:12pt;font-family:Arial,sans-serif"></span></p>
<p style="margin:0cm;line-height:normal;background-image:initial;background-position:initial;background-size:initial;background-repeat:initial;font-size:11pt;font-family:Calibri,sans-serif"><span style="font-size:12pt;font-family:Arial,sans-serif"> </span></p>
<p style="margin:0cm;text-align:justify;line-height:normal;background-image:initial;background-position:initial;background-size:initial;background-repeat:initial;font-size:11pt;font-family:Calibri,sans-serif"><span style="font-family:Arial,sans-serif;color:black">The <b>IDNccPDP4 WG</b> was requested to provide feedback
on a draft recommendation by the Phase 2 GNSO IDN EPDP WG on proposal to create
a formal process for convening a group that would <b>propose amendments to IDN
Guidelines</b>. These Guidelines may affect (IDN & ASCII)) ccTLDs, with IDN
second level domains under management and were developed by a group of experts,
including members of the ccTLD community. According to the proposal, the
ccNSO and GNSO Councils will have a role in developing the charter for the
community group that will develop future versions of the IDN Implementation
Guidelines.</span><span style="font-size:12pt;font-family:Arial,sans-serif"></span></p>
<p style="margin:0cm;line-height:normal;background-image:initial;background-position:initial;background-size:initial;background-repeat:initial;font-size:11pt;font-family:Calibri,sans-serif"><span style="font-size:12pt;font-family:Arial,sans-serif"> </span></p>
<p style="margin:0cm;text-align:justify;line-height:normal;background-image:initial;background-position:initial;background-size:initial;background-repeat:initial;font-size:11pt;font-family:Calibri,sans-serif"><b><span style="font-family:Arial,sans-serif;color:black">EPDP GNSO</span></b><span style="font-family:Arial,sans-serif;color:black"> <b>has a phase 2,</b> currently in drafting mode. One of
the recommendations (draft rec. 14 in the report) is about <b>suggesting a more
predictable process on changing the IDN</b> <b>implementation guidelines</b>.
Board development guideline on the format how to submit tables to IANA. Board
initiated process. CcNSO appointed some members. Suggestion is to make the
process more rigorous. Reason for raising it now: they foresee a role for ccNSO
council</span><span style="font-size:12pt;font-family:Arial,sans-serif"></span></p>
<p style="margin:0cm;text-align:justify;line-height:normal;background-image:initial;background-position:initial;background-size:initial;background-repeat:initial;font-size:11pt;font-family:Calibri,sans-serif"><b><span style="font-family:Arial,sans-serif;color:black">Firstly, to approve the process to be designed</span></b><span style="font-family:Arial,sans-serif;color:black">, every time the board is
initiating the process</span><span style="font-size:12pt;font-family:Arial,sans-serif"></span></p>
<p style="margin:0cm;text-align:justify;line-height:normal;background-image:initial;background-position:initial;background-size:initial;background-repeat:initial;font-size:11pt;font-family:Calibri,sans-serif"><b><span style="font-family:Arial,sans-serif;color:black">Secondly, to appoint members to this WG and monitor the
outcome for the community</span></b><b><span style="font-size:12pt;font-family:Arial,sans-serif"></span></b></p>
<p style="margin:0cm;text-align:justify;line-height:normal;background-image:initial;background-position:initial;background-size:initial;background-repeat:initial;font-size:11pt;font-family:Calibri,sans-serif"><span style="font-family:Arial,sans-serif;color:black"> </span></p>
<p style="margin:0cm;text-align:justify;line-height:normal;background-image:initial;background-position:initial;background-size:initial;background-repeat:initial;font-size:11pt;font-family:Calibri,sans-serif"><span style="font-family:Arial,sans-serif;color:black">This is relevant for ccTLDS, <b>IDN tables need to have
a format</b>. Determined by the implementation guideline. Therefore ccNSO will be involved in the evolution of the IDN implementation
guideline. </span><span style="font-size:12pt;font-family:Arial,sans-serif"></span></p>
<p style="margin:0cm 0cm 8pt;line-height:107%;font-size:11pt;font-family:Calibri,sans-serif"> </p></div><div>Also, please take a look at the <a shape="rect" href="https://community.icann.org/display/atlarge/ALAC+Liaison+to+the+ccNSO+Reports?preview=/2262570/305299473/ccNSO%20Newsletter%20%20February%202024.pdf#ccNSO--1198923559" rel="nofollow noreferrer" target="_blank">February newsletter</a>.<br clear="none"></div><div><br clear="none"></div><div>Thank you and have a nice week!<br clear="none"></div><div><br clear="none"></div><div><br clear="none"></div><div><div dir="ltr"><div dir="ltr"><div><div><div><b><font color="#073763">Laura Margolis</font></b></div><div>ALAC Liaison to ccNSO</div><div><br clear="none"></div><div><a shape="rect" href="mailto:margolisl@gmail.com" rel="nofollow noreferrer" target="_blank">margolisl@gmail.com</a></div><div>+59899690992</div><div>skype: lauri.margolis</div><div><br clear="none"></div><div><a shape="rect" href="https://community.icann.org/display/atlarge/ALAC+Liaison+to+the+ccNSO+Reports#ccNSO-696341623" rel="nofollow noreferrer" target="_blank"><font color="#0b5394">ccNSO Liaison Workspace</font></a></div><div><br clear="none"></div></div></div></div></div></div></div>
_______________________________________________<br clear="none">
ALAC mailing list<br clear="none">
<a shape="rect" href="mailto:ALAC@atlarge-lists.icann.org" rel="nofollow noreferrer" target="_blank">ALAC@atlarge-lists.icann.org</a><br clear="none">
<a shape="rect" href="https://atlarge-lists.icann.org/mailman/listinfo/alac" rel="nofollow noreferrer" target="_blank">https://atlarge-lists.icann.org/mailman/listinfo/alac</a><br clear="none">
<br clear="none">
At-Large Online: <a shape="rect" href="http://www.atlarge.icann.org" rel="nofollow noreferrer" target="_blank">http://www.atlarge.icann.org</a><br clear="none">
ALAC Working Wiki: <a shape="rect" href="https://community.icann.org/display/atlarge/At-Large+Advisory+Committee+(ALAC)" rel="nofollow noreferrer" target="_blank">https://community.icann.org/display/atlarge/At-Large+Advisory+Committee+(ALAC)</a><br clear="none">
_______________________________________________<br clear="none">
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 (<a shape="rect" href="https://www.icann.org/privacy/policy" rel="nofollow noreferrer" target="_blank">https://www.icann.org/privacy/policy</a>) and the website Terms of Service (<a shape="rect" href="https://www.icann.org/privacy/tos" rel="nofollow noreferrer" target="_blank">https://www.icann.org/privacy/tos</a>). 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.</blockquote></div></div>
</div></div><div id="m_-6632908772588911006m_1631441651493603189ydp83cbb2d8yqt96429">_______________________________________________<br clear="none">ALAC mailing list<br clear="none"><a shape="rect" href="mailto:ALAC@atlarge-lists.icann.org" rel="nofollow noreferrer" target="_blank">ALAC@atlarge-lists.icann.org</a><br clear="none"><a shape="rect" href="https://atlarge-lists.icann.org/mailman/listinfo/alac" rel="nofollow noreferrer" target="_blank">https://atlarge-lists.icann.org/mailman/listinfo/alac</a><br clear="none"><br clear="none">At-Large Online: <a shape="rect" href="http://www.atlarge.icann.org" rel="nofollow noreferrer" target="_blank">http://www.atlarge.icann.org</a><br clear="none">ALAC Working Wiki: <a href="https://community.icann.org/display/atlarge/At-Large+Advisory+Committee+(ALAC)" target="_blank" rel="noreferrer">https://community.icann.org/display/atlarge/At-Large+Advisory+Committee+(ALAC)</a><br clear="none">_______________________________________________<br clear="none">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 (<a href="https://www.icann.org/privacy/policy" target="_blank" rel="noreferrer">https://www.icann.org/privacy/policy</a>) and the website Terms of Service (<a href="https://www.icann.org/privacy/tos" target="_blank" rel="noreferrer">https://www.icann.org/privacy/tos</a>). 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.</div></div>
</div>
</div></div>_______________________________________________<br>
ALAC mailing list<br>
<a href="mailto:ALAC@atlarge-lists.icann.org" target="_blank" rel="noreferrer">ALAC@atlarge-lists.icann.org</a><br>
<a href="https://atlarge-lists.icann.org/mailman/listinfo/alac" rel="noreferrer noreferrer" target="_blank">https://atlarge-lists.icann.org/mailman/listinfo/alac</a><br>
<br>
At-Large Online: <a href="http://www.atlarge.icann.org" rel="noreferrer noreferrer" target="_blank">http://www.atlarge.icann.org</a><br>
ALAC Working Wiki: <a href="https://community.icann.org/display/atlarge/At-Large+Advisory+Committee+(ALAC)" rel="noreferrer noreferrer" target="_blank">https://community.icann.org/display/atlarge/At-Large+Advisory+Committee+(ALAC)</a><br>
_______________________________________________<br>
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 (<a href="https://www.icann.org/privacy/policy" rel="noreferrer noreferrer" target="_blank">https://www.icann.org/privacy/policy</a>) and the website Terms of Service (<a href="https://www.icann.org/privacy/tos" rel="noreferrer noreferrer" target="_blank">https://www.icann.org/privacy/tos</a>). 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.</blockquote></div></div>