<div dir="auto">Perhaps this makes convincing for a PDP less difficult. Thanks for sharing this important information Michele<br><br>I wonder how this can be applicable to regions who experience total Internet shutdowns so well. May be something to explore if/when a PDP happens.<div dir="auto"><br>Regards<br><div data-smartmail="gmail_signature" dir="auto">Sent from my mobile<br>Kindly excuse brevity and typos</div></div></div><div class="gmail_extra"><br><div class="gmail_quote">On Nov 17, 2017 3:58 PM, "Kan Kaili" <<a href="mailto:kankaili@gmail.com">kankaili@gmail.com</a>> wrote:<br type="attribution"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><u></u>





<div lang="EN-IE" link="blue" bgcolor="#ffffff" vlink="purple">
<div><font size="2" face="宋体">Hi, Michele,</font></div>
<div><font size="2" face="宋体"></font> </div>
<div><font size="2" face="宋体">Thank you very much for this info.  It seems like 
ICANN is acting fast on this.</font></div>
<div><font size="2" face="宋体"></font> </div>
<div><font size="2" face="宋体">ICANN's guidance also indicates "the potential need 
for a policy initiative to protect registrants when they are unable to renew 
their domains as a result of natural disasters or other extraordinary 
circumstances", in fact suggesting a PDP to be considered by GNSO.</font></div>
<div><font size="2" face="宋体"></font> </div>
<div><font size="2" face="宋体">Thus, my question is, what should/could other 
parties do, especially ALAC?</font></div>
<div><font size="2" face="宋体"></font> </div>
<div><font size="2" face="宋体">Thanks again.</font></div>
<div><font size="2" face="宋体"></font> </div>
<div><font size="2" face="宋体">Kaili</font></div>
<div><font size="2" face="宋体"></font> </div>
<blockquote style="BORDER-LEFT:#000000 2px solid;PADDING-LEFT:5px;PADDING-RIGHT:0px;MARGIN-LEFT:5px;MARGIN-RIGHT:0px" dir="ltr">
  <div style="FONT:9pt 宋体">----- Original Message ----- </div>
  <div style="FONT:9pt 宋体;BACKGROUND:#e4e4e4"><b>From:</b> 
  <a title="michele@blacknight.com" href="mailto:michele@blacknight.com" target="_blank">Michele 
  Neylon - Blacknight</a> </div>
  <div style="FONT:9pt 宋体"><b>To:</b> <a title="javrua@gmail.com" href="mailto:javrua@gmail.com" target="_blank">Javier Rua</a> ; <a title="kankaili@gmail.com" href="mailto:kankaili@gmail.com" target="_blank">Kan Kaili</a> </div>
  <div style="FONT:9pt 宋体"><b>Cc:</b> <a title="alac-internal@atlarge-lists.icann.org" href="mailto:alac-internal@atlarge-lists.icann.org" target="_blank">ALAC Internal List</a> ; 
  <a title="at-large@atlarge-lists.icann.org" href="mailto:at-large@atlarge-lists.icann.org" target="_blank">At-Large</a> </div>
  <div style="FONT:9pt 宋体"><b>Sent:</b> Friday, November 17, 2017 10:21 
PM</div>
  <div style="FONT:9pt 宋体"><b>Subject:</b> Re: [At-Large] [ALAC-Internal] 
  Hurricane Maria Domain Registration protectionProtocol</div>
  <div><br></div>
  <div class="m_6458118516800140713WordSection1">
  <p class="MsoNormal"><span lang="EN-GB">FYI<br><a href="https://www.internetnews.me/2017/11/17/icann-issues-guidance-registrars-registries-light-hurricane-maria/" target="_blank">https://www.internetnews.me/<wbr>2017/11/17/icann-issues-<wbr>guidance-registrars-<wbr>registries-light-hurricane-<wbr>maria/</a><u></u><u></u></span></p>
  <p class="MsoNormal"><span lang="EN-GB"><u></u> <u></u></span></p>
  <p class="MsoNormal"><span lang="EN-GB"><u></u> <u></u></span></p>
  <div>
  <p class="MsoNormal"><span style="COLOR:black" lang="EN-GB">--<u></u><u></u></span></p>
  <p class="MsoNormal"><span style="COLOR:black" lang="EN-GB">Mr Michele Neylon<u></u><u></u></span></p>
  <p class="MsoNormal"><span style="COLOR:black" lang="EN-GB">Blacknight Solutions<u></u><u></u></span></p>
  <p class="MsoNormal"><span style="COLOR:black" lang="EN-GB">Hosting, Colocation & Domains<u></u><u></u></span></p>
  <p class="MsoNormal"><span style="COLOR:black" lang="EN-GB"><a href="https://www.blacknight.com/" target="_blank">https://www.blacknight.com/</a><u></u><u></u></span></p>
  <p class="MsoNormal"><span style="COLOR:black" lang="EN-GB"><a href="http://blacknight.blog/" target="_blank">http://blacknight.blog/</a><u></u><u></u></span></p>
  <p class="MsoNormal"><span style="COLOR:black" lang="EN-GB">Intl. <a href="tel:+353%2059%20918%203072" value="+353599183072" target="_blank">+353 (0) 59  9183072</a><u></u><u></u></span></p>
  <p class="MsoNormal"><span style="COLOR:black" lang="EN-GB">Direct Dial: <a href="tel:+353%2059%20918%203090" value="+353599183090" target="_blank">+353 (0)59 9183090</a><u></u><u></u></span></p>
  <p class="MsoNormal"><span style="COLOR:black" lang="EN-GB">Personal blog: <a href="https://michele.blog/" target="_blank">https://michele.blog/</a><u></u><u></u></span></p>
  <p class="MsoNormal"><span style="COLOR:black" lang="EN-GB">Some thoughts: <a href="https://ceo.hosting/" target="_blank">https://ceo.hosting/</a> <u></u><u></u></span></p>
  <p class="MsoNormal"><span style="COLOR:black" lang="EN-GB">------------------------------<wbr>-<u></u><u></u></span></p>
  <p class="MsoNormal"><span style="COLOR:black" lang="EN-GB">Blacknight Internet Solutions Ltd, Unit 12A,Barrowside Business 
  Park,Sleaty<u></u><u></u></span></p></div>
  <p class="MsoNormal"><span style="COLOR:black" lang="EN-GB">Road,Graiguecullen,Carlow,R93 X265,Ireland  Company No.: 
  370845</span><span lang="EN-GB"><u></u><u></u></span></p>
  <div style="BORDER-BOTTOM:medium none;BORDER-LEFT:medium none;PADDING-BOTTOM:0cm;PADDING-LEFT:0cm;PADDING-RIGHT:0cm;BORDER-TOP:#b5c4df 1pt solid;BORDER-RIGHT:medium none;PADDING-TOP:3pt">
  <p class="MsoNormal"><b><span style="COLOR:black;FONT-SIZE:12pt">From: 
  </span></b><span style="COLOR:black;FONT-SIZE:12pt">At-Large <<a href="mailto:at-large-bounces@atlarge-lists.icann.org" target="_blank">at-large-bounces@atlarge-<wbr>lists.icann.org</a>> 
  on behalf of Javier Rua <<a href="mailto:javrua@gmail.com" target="_blank">javrua@gmail.com</a>><br><b>Date: </b>Friday 17 
  November 2017 at 02:58<br><b>To: </b>Kan Kaili 
  <<a href="mailto:kankaili@gmail.com" target="_blank">kankaili@gmail.com</a>><br><b>Cc: </b>ALAC Internal List 
  <<a href="mailto:alac-internal@atlarge-lists.icann.org" target="_blank">alac-internal@atlarge-lists.<wbr>icann.org</a>>, At-Large Worldwide 
  <<a href="mailto:at-large@atlarge-lists.icann.org" target="_blank">at-large@atlarge-lists.icann.<wbr>org</a>><br><b>Subject: </b>Re: [At-Large] 
  [ALAC-Internal] Hurricane Maria Domain Registration 
  protectionProtocol<u></u><u></u></span></p></div>
  <div>
  <p class="MsoNormal"><u></u> <u></u></p></div>
  <p style="MARGIN-BOTTOM:12pt" class="MsoNormal"><a name="m_6458118516800140713__MailOriginalBody">We 
  must start changing the name of the thread to something like General Disaster 
  (Natural & otherwise) Reg. Protocol, since it’s not only hurricanes we 
  will be dealing with more and more in this crazy brave new 
  world.<u></u><u></u></a></p>
  <div id="m_6458118516800140713AppleMailSignature">
  <p class="MsoNormal"><span>Javier 
  Rúa-Jovet <u></u><u></u></span></p>
  <div>
  <p class="MsoNormal"><span><u></u> <u></u></span></p></div>
  <div>
  <div>
  <p class="MsoNormal"><span><a href="tel:+1%20787-396-6511" value="+17873966511" target="_blank">+1-787-396-6511</a><u></u><u></u></span></p></div>
  <div>
  <p class="MsoNormal"><span>twitter: 
  @javrua<u></u><u></u></span></p></div>
  <div>
  <p class="MsoNormal"><span>skype: 
  javier.rua1<u></u><u></u></span></p></div>
  <div>
  <p class="MsoNormal"><span></span><a href="https://www.linkedin.com/in/javrua" target="_blank"><span>https://www.linkedin.com/in/<wbr>javrua</span><span></span></a><span><span style="COLOR:black"> </span></span><span><u></u><u></u></span></p></div>
  <div>
  <p class="MsoNormal"><span><u></u> <u></u></span></p></div></div></div>
  <div>
  <p style="MARGIN-BOTTOM:12pt" class="MsoNormal"><span><br>On Nov 16, 2017, at 10:34 PM, Kan 
  Kaili <</span><a href="mailto:kankaili@gmail.com" target="_blank"><span>kankaili@gmail.com</span><span></span></a><span>> 
wrote:<u></u><u></u></span></p></div>
  <blockquote style="MARGIN-TOP:5pt;MARGIN-BOTTOM:5pt">
    <div>
    <div>
    <div>
    <p class="MsoNormal"><span><span style="FONT-FAMILY:SimSun;FONT-SIZE:10pt">Hi, </span></span><span><u></u><u></u></span></p></div>
    <div>
    <p class="MsoNormal"><span> <u></u><u></u></span></p></div>
    <div>
    <p class="MsoNormal"><span><span style="FONT-FAMILY:SimSun;FONT-SIZE:10pt">As Maureen pointed out, this 
    indeed would be a good joint activity of ALAC and ccNSO.  According to 
    the response collected, ccNSO's response is likely to be 
    positive.</span></span><span><u></u><u></u></span></p></div>
    <div>
    <p class="MsoNormal"><span> <u></u><u></u></span></p></div>
    <div>
    <p class="MsoNormal"><span><span style="FONT-FAMILY:SimSun;FONT-SIZE:10pt">On the other hand, it is also 
    true that ICANN's Board cannot order the ccTLDs to do something beyond their 
    contracts.  This reminds me of the multi-stakeholder structure of ISC 
    (Internet Society of China).  Whenever there is something that harms 
    consumers' interest, e.g., spam, the following happens:</span></span><span><u></u><u></u></span></p></div>
    <div>
    <p class="MsoNormal"><span><span style="FONT-FAMILY:SimSun;FONT-SIZE:10pt">- ISC's academic people will go 
    to the media and have it heard.  </span></span><span><u></u><u></u></span></p></div>
    <div>
    <p class="MsoNormal"><span><span style="FONT-FAMILY:SimSun;FONT-SIZE:10pt">- In response, a few ISC's 
    industry members will respond with a voluntary 
    solution. </span></span><span><u></u><u></u></span></p></div>
    <div>
    <p class="MsoNormal"><span><span style="FONT-FAMILY:SimSun;FONT-SIZE:10pt">- ISC's scholars will compare 
    different solutions and present a preferred one to ISC.</span></span><span><u></u><u></u></span></p></div>
    <div>
    <p class="MsoNormal"><span><span style="FONT-FAMILY:SimSun;FONT-SIZE:10pt">- A number of ISC's corporate 
    members adopt to this solution and comeup with a joint announcement, 
    e.g., "Anti-Spam Declaration", making it the industry 
    standard.</span></span><span><u></u><u></u></span></p></div>
    <div>
    <p class="MsoNormal"><span><span style="FONT-FAMILY:SimSun;FONT-SIZE:10pt">- ISC will oversee the 
    implementation of this standard, and publicly award industry members for 
    good behaviors.  (Companies not complying will be at a great 
    disadvantage.)</span></span><span><u></u><u></u></span></p></div>
    <div>
    <p class="MsoNormal"><span><span style="FONT-FAMILY:SimSun;FONT-SIZE:10pt">- The ministry (MIIT) closely 
    observes the whole process, provides support, and makes the solution into 
    regulation when it is widely followed.</span></span><span><u></u><u></u></span></p></div>
    <div>
    <p class="MsoNormal"><span> <u></u><u></u></span></p></div>
    <div>
    <p class="MsoNormal"><span><span style="FONT-FAMILY:SimSun;FONT-SIZE:10pt">As ICANN is also a 
    multistakeholder organization, I wonder if we could take a similar approach 
    with ALAC playing the role of ISC or its scholars representing 
    consumers' interests.</span></span><span><u></u><u></u></span></p></div>
    <div>
    <p class="MsoNormal"><span> <u></u><u></u></span></p></div>
    <div>
    <p class="MsoNormal"><span><span style="FONT-FAMILY:SimSun;FONT-SIZE:10pt">As I see it, ccNSO is likely to 
    first adopt to this "distress relief" measure, while GNSO will then have to 
    follow.</span></span><span><u></u><u></u></span></p></div>
    <div>
    <p class="MsoNormal"><span> <u></u><u></u></span></p></div>
    <div>
    <p class="MsoNormal"><span><span style="FONT-FAMILY:SimSun;FONT-SIZE:10pt">Thank you!</span></span><span><u></u><u></u></span></p></div>
    <div>
    <p class="MsoNormal"><span> <u></u><u></u></span></p></div>
    <div>
    <p class="MsoNormal"><span><span style="FONT-FAMILY:SimSun;FONT-SIZE:10pt">Kaili</span></span><span><u></u><u></u></span></p></div>
    <div>
    <p class="MsoNormal"><span> <u></u><u></u></span></p></div>
    <div>
    <p class="MsoNormal"><span> <u></u><u></u></span></p></div></div>
    <blockquote style="BORDER-BOTTOM:medium none;BORDER-LEFT:black 1.5pt solid;PADDING-BOTTOM:0cm;MARGIN:5pt 0cm 5pt 3.75pt;PADDING-LEFT:4pt;PADDING-RIGHT:0cm;BORDER-TOP:medium none;BORDER-RIGHT:medium none;PADDING-TOP:0cm">
      <div>
      <p class="MsoNormal"><span><span style="FONT-FAMILY:SimSun;FONT-SIZE:9pt">----- Original Message ----- 
      <u></u><u></u></span></span></p></div>
      <div>
      <p style="BACKGROUND:#e4e4e4" class="MsoNormal"><span><b><span style="FONT-FAMILY:SimSun;FONT-SIZE:9pt">From:</span></b></span><span><span style="FONT-FAMILY:SimSun;FONT-SIZE:9pt"> </span></span><a title="maureen.hilyard@gmail.com" href="mailto:maureen.hilyard@gmail.com" target="_blank"><span><span style="FONT-FAMILY:SimSun;FONT-SIZE:9pt">Maureen 
      Hilyard</span></span><span></span></a><span><span style="FONT-FAMILY:SimSun;FONT-SIZE:9pt"> 
      <u></u><u></u></span></span></p></div>
      <div>
      <p class="MsoNormal"><span><b><span style="FONT-FAMILY:SimSun;FONT-SIZE:9pt">To:</span></b></span><span><span style="FONT-FAMILY:SimSun;FONT-SIZE:9pt"> </span></span><a title="alac-internal@atlarge-lists.icann.org" href="mailto:alac-internal@atlarge-lists.icann.org" target="_blank"><span><span style="FONT-FAMILY:SimSun;FONT-SIZE:9pt">ALAC Internal 
      List</span></span><span></span></a><span><span style="FONT-FAMILY:SimSun;FONT-SIZE:9pt"> 
      <u></u><u></u></span></span></p></div>
      <div>
      <p class="MsoNormal"><span><b><span style="FONT-FAMILY:SimSun;FONT-SIZE:9pt">Sent:</span></b></span><span><span style="FONT-FAMILY:SimSun;FONT-SIZE:9pt"> Friday, November 17, 2017 
      12:30 AM<u></u><u></u></span></span></p></div>
      <div>
      <p class="MsoNormal"><span><b><span style="FONT-FAMILY:SimSun;FONT-SIZE:9pt">Subject:</span></b></span><span><span style="FONT-FAMILY:SimSun;FONT-SIZE:9pt"> Re: [ALAC-Internal] Hurricane 
      Maria Domain Registration 
      protectionProtocol<u></u><u></u></span></span></p></div>
      <div>
      <p class="MsoNormal"><span><u></u> <u></u></span></p></div>
      <div>
      <p class="MsoNormal"><span>Hi 
      everyone <u></u><u></u></span></p>
      <div>
      <p class="MsoNormal"><span><u></u> <u></u></span></p></div>
      <div>
      <p class="MsoNormal"><span>I have 
      had a response from Katrina (CCNSO Chair) and she agrees that it would be 
      worth exploring and discussing possibilities to help domain name 
      registrants and registrars from affected 
areas.<u></u><u></u></span></p></div>
      <div>
      <p class="MsoNormal"><span><u></u> <u></u></span></p></div>
      <div>
      <p class="MsoNormal"><span>In 
      response to some suggestions I gave as to how we might contribution to a 
      solution, Katrina raised the concern that "ICANN would not be able to tell 
      ccTLDs what to do, it would have to be their own decision, but this does 
      not mean that the ccNSO shouldn't or can't do 
      anything"<u></u><u></u></span></p></div>
      <div>
      <p class="MsoNormal"><span><u></u> <u></u></span></p></div>
      <div>
      <p class="MsoNormal"><span>Katrina, 
      in conjunction with Alejandra who is their Meeting Programme Coordinator, 
      have suggested: <u></u><u></u></span></p></div>
      <div>
      <p style="MARGIN-BOTTOM:0pt;MARGIN-LEFT:36pt;MARGIN-RIGHT:0cm" class="m_6458118516800140713gmail-m7099697691176340694msolistparagraph"><span><span style="FONT-FAMILY:'Times New Roman',serif;FONT-SIZE:12pt"><u></u> <u></u></span></span></p>
      <p style="MARGIN-BOTTOM:0pt;MARGIN-LEFT:36pt;MARGIN-RIGHT:0cm" class="m_6458118516800140713gmail-m7099697691176340694msolistparagraph"><span><span style="COLOR:#1f497d">-</span></span><span><span style="FONT-FAMILY:'Times New Roman',serif;COLOR:#1f497d;FONT-SIZE:7pt">        </span></span><span><span style="COLOR:#1f497d">We 
      organise a discussion at ccNSO Members meeting <span class="m_6458118516800140713gmail-aqj">on Tuesday</span> or <span class="m_6458118516800140713gmail-aqj">Wednesday</span></span></span><span><span style="FONT-FAMILY:'Times New Roman',serif;FONT-SIZE:12pt"><u></u><u></u></span></span></p>
      <p style="MARGIN-BOTTOM:0pt;MARGIN-LEFT:36pt;MARGIN-RIGHT:0cm" class="m_6458118516800140713gmail-m7099697691176340694msolistparagraph"><span><span style="COLOR:#1f497d">-</span></span><span><span style="FONT-FAMILY:'Times New Roman',serif;COLOR:#1f497d;FONT-SIZE:7pt">        </span></span><span><span style="COLOR:#1f497d">“How 
      to help ccTLDs, registrars and registrants in case of severely damaged 
      infrastructure?” (or a similar title)</span></span><span><span style="FONT-FAMILY:'Times New Roman',serif;FONT-SIZE:12pt"><u></u><u></u></span></span></p>
      <p style="MARGIN-BOTTOM:0pt;MARGIN-LEFT:36pt;MARGIN-RIGHT:0cm" class="m_6458118516800140713gmail-m7099697691176340694msolistparagraph"><span><span style="COLOR:#1f497d">-</span></span><span><span style="FONT-FAMILY:'Times New Roman',serif;COLOR:#1f497d;FONT-SIZE:7pt">        </span></span><span><span style="COLOR:#1f497d">We 
      will ask Pablo and perhaps somebody from .us or other ccTLDs to tell what 
      it means for people to be cut from the outside world and what they did to 
      help</span></span><span><span style="FONT-FAMILY:'Times New Roman',serif;FONT-SIZE:12pt"><u></u><u></u></span></span></p>
      <p style="MARGIN-BOTTOM:0pt;MARGIN-LEFT:36pt;MARGIN-RIGHT:0cm" class="m_6458118516800140713gmail-m7099697691176340694msolistparagraph"><span><span style="COLOR:#1f497d">-</span></span><span><span style="FONT-FAMILY:'Times New Roman',serif;COLOR:#1f497d;FONT-SIZE:7pt">        </span></span><span><span style="COLOR:#1f497d">We 
      would like to invite you (or somebody else from ALAC) and maybe from some 
      other SO/ACs – would be nice if you could share your concerns and your 
      ideas/proposals</span></span><span><span style="FONT-FAMILY:'Times New Roman',serif;FONT-SIZE:12pt"><u></u><u></u></span></span></p>
      <p style="MARGIN-BOTTOM:0pt;MARGIN-LEFT:36pt;MARGIN-RIGHT:0cm" class="m_6458118516800140713gmail-m7099697691176340694msolistparagraph"><span><span style="COLOR:#1f497d">-</span></span><span><span style="FONT-FAMILY:'Times New Roman',serif;COLOR:#1f497d;FONT-SIZE:7pt">        </span></span><span><span style="COLOR:#1f497d">We 
      will invite ROs. They are the driving force and the ones who can help the 
      most. </span></span><span><span style="FONT-FAMILY:'Arial',sans-serif;FONT-SIZE:12pt"> </span></span><span><span style="COLOR:#1f497d;FONT-SIZE:10.5pt">For example, during the LACTLD 
      Technical workshop they try to establish redundancy among fellow ccTLDs, 
      especially for small registries.</span></span><span><span style="FONT-FAMILY:'Times New Roman',serif;FONT-SIZE:12pt"><u></u><u></u></span></span></p>
      <p style="MARGIN-BOTTOM:0pt;MARGIN-LEFT:36pt;MARGIN-RIGHT:0cm" class="m_6458118516800140713gmail-m7099697691176340694msolistparagraph"><span><span style="COLOR:#1f497d">-</span></span><span><span style="FONT-FAMILY:'Times New Roman',serif;COLOR:#1f497d;FONT-SIZE:7pt">        </span></span><span><span style="COLOR:#1f497d">Discussions</span></span><span><span style="FONT-FAMILY:'Times New Roman',serif;FONT-SIZE:12pt"><u></u><u></u></span></span></p>
      <p style="MARGIN-BOTTOM:0pt;MARGIN-LEFT:36pt;MARGIN-RIGHT:0cm" class="m_6458118516800140713gmail-m7099697691176340694msolistparagraph"><span><span style="FONT-FAMILY:'Times New Roman',serif;FONT-SIZE:12pt"><u></u> <u></u></span></span></p>
      <p style="MARGIN-BOTTOM:0pt;MARGIN-LEFT:36pt;MARGIN-RIGHT:0cm" class="m_6458118516800140713gmail-m7099697691176340694msolistparagraph"><span><span style="FONT-FAMILY:'Arial',sans-serif;FONT-SIZE:12pt">It sounds like a 
      great plan for our ALAC/ccNSO session, and very relevant that the meeting 
      will be held in Puerto Rico. Alejandra and I could work together to 
      negotiate a suitable time for the ALAC to participate in the session. Be a 
      change if we went to their meeting place. We could encourage input from 
      other SO/ACs.</span></span><span><span style="FONT-FAMILY:'Times New Roman',serif;FONT-SIZE:12pt"><u></u><u></u></span></span></p>
      <p style="MARGIN-BOTTOM:0pt;MARGIN-LEFT:36pt;MARGIN-RIGHT:0cm" class="m_6458118516800140713gmail-m7099697691176340694msolistparagraph"><span><span style="FONT-FAMILY:'Times New Roman',serif;FONT-SIZE:12pt"><u></u> <u></u></span></span></p>
      <p style="MARGIN-BOTTOM:0pt;MARGIN-LEFT:36pt;MARGIN-RIGHT:0cm" class="m_6458118516800140713gmail-m7099697691176340694msolistparagraph"><span><span style="FONT-FAMILY:'Arial',sans-serif;FONT-SIZE:12pt">Comments?</span></span><span><span style="FONT-FAMILY:'Times New Roman',serif;FONT-SIZE:12pt"><u></u><u></u></span></span></p>
      <p style="MARGIN-BOTTOM:0pt;MARGIN-LEFT:36pt;MARGIN-RIGHT:0cm" class="m_6458118516800140713gmail-m7099697691176340694msolistparagraph"><span><span style="FONT-FAMILY:'Times New Roman',serif;FONT-SIZE:12pt"><u></u> <u></u></span></span></p></div></div>
      <div>
      <p class="MsoNormal"><span><u></u> <u></u></span></p>
      <div>
      <p class="MsoNormal"><span>On Wed, 
      Nov 15, 2017 at 8:24 PM, Javier Rua <</span><a href="mailto:javrua@gmail.com" target="_blank"><span>javrua@gmail.com</span><span></span></a><span>> wrote:<u></u><u></u></span></p>
      <blockquote style="BORDER-BOTTOM:medium none;BORDER-LEFT:#cccccc 1pt solid;PADDING-BOTTOM:0cm;PADDING-LEFT:6pt;PADDING-RIGHT:0cm;MARGIN-LEFT:4.8pt;BORDER-TOP:medium none;MARGIN-RIGHT:0cm;BORDER-RIGHT:medium none;PADDING-TOP:0cm">
        <div>
        <p style="MARGIN-BOTTOM:12pt" class="MsoNormal"><span>Don’t leave out gTLDs 
        !<u></u><u></u></span></p>
        <div id="m_6458118516800140713m_3055778373556209487AppleMailSignature">
        <p class="MsoNormal"><span>Javier 
        Rúa-Jovet <u></u><u></u></span></p>
        <div>
        <p class="MsoNormal"><span><u></u> <u></u></span></p></div>
        <div>
        <div>
        <p class="MsoNormal"><span></span><a href="tel:+1%20787-396-6511" target="_blank"><span>+1-787-396-6511</span><span></span></a><span><u></u><u></u></span></p></div>
        <div>
        <p class="MsoNormal"><span>twitter: 
        @javrua<u></u><u></u></span></p></div>
        <div>
        <p class="MsoNormal"><span>skype: 
        javier.rua1<u></u><u></u></span></p></div>
        <div>
        <p class="MsoNormal"><span></span><a href="https://www.linkedin.com/in/javrua" target="_blank"><span>https://www.linkedin.com/in/<wbr>javrua</span><span></span></a><span><span style="COLOR:black"> </span></span><span><u></u><u></u></span></p></div>
        <div>
        <p class="MsoNormal"><span><u></u> <u></u></span></p></div></div></div>
        <div>
        <div>
        <div>
        <p style="MARGIN-BOTTOM:12pt" class="MsoNormal"><span><br>On Nov 16, 2017, at 2:19 AM, 
        Maureen Hilyard <</span><a href="mailto:maureen.hilyard@gmail.com" target="_blank"><span>maureen.hilyard@gmail.com</span><span></span></a><span>> 
        wrote:<u></u><u></u></span></p></div>
        <blockquote style="MARGIN-TOP:5pt;MARGIN-BOTTOM:5pt">
          <div>
          <div>
          <p class="MsoNormal"><span>I 
          agree Seun <u></u><u></u></span></p>
          <div>
          <p class="MsoNormal"><span><u></u> <u></u></span></p></div>
          <div>
          <p class="MsoNormal"><span>And I 
          have already reached out to Katrina and explained our discussion (and 
          also commended her ccNSO Councillor Pablo Rodriguez's involvement in 
          it). I have asked her how receptive the ccNSO might be to working with 
          At-Large on developing some sort of advice with respect to a more 
          general policy to cover all ccTLD managers who found themselves in a 
          similar situation. <u></u><u></u></span></p></div>
          <div>
          <p class="MsoNormal"><span><u></u> <u></u></span></p></div>
          <div>
          <p class="MsoNormal"><span>Ill 
          get back to the team when she responds.<u></u><u></u></span></p></div>
          <div>
          <p class="MsoNormal"><span><u></u> <u></u></span></p></div>
          <div>
          <p class="MsoNormal"><span>Maureen<u></u><u></u></span></p></div></div>
          <div>
          <p class="MsoNormal"><span><u></u> <u></u></span></p>
          <div>
          <p class="MsoNormal"><span>On 
          Wed, Nov 15, 2017 at 7:53 PM, Seun Ojedeji <</span><a href="mailto:seun.ojedeji@gmail.com" target="_blank"><span>seun.ojedeji@gmail.com</span><span></span></a><span>> 
          wrote:<u></u><u></u></span></p>
          <blockquote style="BORDER-BOTTOM:medium none;BORDER-LEFT:#cccccc 1pt solid;PADDING-BOTTOM:0cm;PADDING-LEFT:6pt;PADDING-RIGHT:0cm;MARGIN-LEFT:4.8pt;BORDER-TOP:medium none;MARGIN-RIGHT:0cm;BORDER-RIGHT:medium none;PADDING-TOP:0cm">
            <div>
            <p class="MsoNormal"><span>Hello Alan, 
            <u></u><u></u></span></p>
            <div>
            <p class="MsoNormal"><span><u></u> <u></u></span></p></div>
            <div>
            <p class="MsoNormal"><span>My 
            personal feeling is that the PDP will be a long process and I have 
            my doubts that this can survive a PDP process espcially because a 
            possible solution will involve regiatrar/Registry sacrifice funds. 
            However I think it's worth a try and I think we could check the 
            temperature before even starting a PDP by sending a statement in 
            form of advice to all concerned part of the 
            community.<u></u><u></u></span></p></div>
            <div>
            <p class="MsoNormal"><span><u></u> <u></u></span></p></div>
            <div>
            <p class="MsoNormal"><span>So 
            the kind of advice I am referring to is to send in a teaser to see 
            the reaction from the community. Such advice would note and commend 
            the action taken by .pr and will then encourage/request the 
            respective parties to implement such. ccNSO for instance can take 
            such advice back home to their ccTLD policy process. For GNSO we can 
            then suggest a PDP and hear their initial reaction. For the RIR we 
            can by that advice hear their view about the applicability of this 
            to numbers. So it's kind of a call to action 
            advice.<br><br>Reese's<u></u><u></u></span></p>
            <div>
            <p class="MsoNormal"><span>Sent from 
            my mobile<br>Kindly excuse brevity and 
            typos<u></u><u></u></span></p></div></div></div>
            <div>
            <div>
            <div>
            <p class="MsoNormal"><span><u></u> <u></u></span></p>
            <div>
            <p class="MsoNormal"><span>On 
            Nov 15, 2017 8:46 PM, "Alan Greenberg" <</span><a href="mailto:alan.greenberg@mcgill.ca" target="_blank"><span>alan.greenberg@mcgill.ca</span><span></span></a><span>> 
            wrote:<u></u><u></u></span></p>
            <blockquote style="BORDER-BOTTOM:medium none;BORDER-LEFT:#cccccc 1pt solid;PADDING-BOTTOM:0cm;PADDING-LEFT:6pt;PADDING-RIGHT:0cm;MARGIN-LEFT:4.8pt;BORDER-TOP:medium none;MARGIN-RIGHT:0cm;BORDER-RIGHT:medium none;PADDING-TOP:0cm">
              <div>
              <p class="MsoNormal"><span>Seun, what kind of advice 
              are you thinking of? <br><br>Advice should be actionable. 
              <br><br>The Board could take would be to enact emergency policy 
              and immediately require that a PDP be initiated to permanently 
              address the issue. I am not sure if the Board has ever used that 
              power and I cannot imagine it doing so now without embarking on a 
              longer study of what sort of mediation was really 
              reasonable.<br><br>To be clear, we cannot simply start a PDP. We 
              can build a case clearly defining the issue and what a PDP should 
              address, and request that staff create an Issue Report. Once that 
              report is completed (having first issued a Preliminary Issue 
              Report and then having it subjected to a Public Comment), the GNSO 
              Council must then vote on whether or not to initiate a PDP. This 
              is all layed out in detail in Annex A of the ICANN Bylaws - 
              </span><a href="https://www.icann.org/resources/pages/governance/bylaws-en/#annexA" target="_blank"><span>https://www.icann.org/<wbr>resources/pages/governance/<wbr>bylaws-en/#annexA</span><span></span></a><span>. The Request for an Issue 
              Report and the processes which should precede it are laid out in 
              the GNSO PDP Manual (</span><a href="https://gnso.icann.org/en/council/annex-2-pdp-manual-01sep16-en.pdf" target="_blank"><span> 
              https://gnso.icann.org/en/<wbr>council/annex-2-pdp-manual-<wbr>01sep16-en.pdf</span><span></span></a><span> ).<br><br>It is a long 
              process, and includes all sorts of checks and 
              balances.<br><br>Alan<br><br>At 15/11/2017 01:37 PM, Seun Ojedeji 
              wrote:<br><br><br><u></u><u></u></span></p>
              <blockquote style="MARGIN-TOP:5pt;MARGIN-BOTTOM:5pt">
                <p class="MsoNormal"><span>I like the idea of going 
                the advice route for a start using the .PR as a case 
                study.<br><br>We may then include in the advice a recommendation 
                for a PDP if necessary.<br><br>Regards<br><br>Sent from my 
                mobile<br>Kindly excuse brevity and typos<br><br>On Nov 15, 2017 
                9:41 AM, "Sebicann Bachollet" <</span><a href="mailto:sebicann@bachollet.fr" target="_blank"><span>sebicann@bachollet.fr</span><span></span></a><span>> 
                wrote:<u></u><u></u></span></p>
                <p style="MARGIN-LEFT:36pt" class="MsoNormal"><span>Hello Great 
                exchange,<u></u><u></u></span></p>
                <p style="MARGIN-BOTTOM:12pt;MARGIN-LEFT:36pt;MARGIN-RIGHT:0cm" class="MsoNormal"><span>And very well done by 
                .pr<u></u><u></u></span></p>
                <p style="MARGIN-LEFT:36pt" class="MsoNormal"><span>I am not sure that the 
                first step is to jump into a PDP.<u></u><u></u></span></p>
                <p style="MARGIN-LEFT:36pt" class="MsoNormal"><span>At-Large can start to 
                express a concerne about this situation, send an advice to both 
                the Board, the gNSO and the ccNSO and the same as info to the 
                GAC and other SO/AC, taking as a good practice (here even a best 
                one ;)) what was done by .pr.<u></u><u></u></span></p>
                <p style="MARGIN-LEFT:36pt" class="MsoNormal"><span>Supporting cc and g to 
                take actions for that purpose.<u></u><u></u></span></p>
                <p style="MARGIN-LEFT:36pt" class="MsoNormal"><span>Ask staff to gather info 
                about any practice both in cc and g worlds (and yes it can 
                become an issue paper at a latest stage).<u></u><u></u></span></p>
                <p style="MARGIN-LEFT:36pt" class="MsoNormal"><span>It i very important to 
                frame it as a global issue for users (both individual, SME and 
                NGO) what ever DN they are using.<u></u><u></u></span></p>
                <p style="MARGIN-LEFT:36pt" class="MsoNormal"><span>We may wish to involve 
                the RIR if such issue is a problem for IP addresses or for any 
                support.<u></u><u></u></span></p>
                <p style="MARGIN-BOTTOM:12pt;MARGIN-LEFT:36pt;MARGIN-RIGHT:0cm" class="MsoNormal"><span>We 
                may also take that into account as a possible exemple of good 
                usage of some fund of the auction proceed (and it is in ICANN 
                mission ;)).<u></u><u></u></span></p>
                <p style="MARGIN-BOTTOM:12pt;MARGIN-LEFT:36pt;MARGIN-RIGHT:0cm" class="MsoNormal"><span>Can we ask At-Large 
                staff to open a wiki page to have this exchange and start 
                writing something on the issue?<u></u><u></u></span></p>
                <p style="MARGIN-BOTTOM:12pt;MARGIN-LEFT:36pt;MARGIN-RIGHT:0cm" class="MsoNormal"><span>I 
                will not be able to participate to the call organized by Ken as 
                I will be in a plane to Montreal.<u></u><u></u></span></p>
                <p style="MARGIN-LEFT:36pt" class="MsoNormal"><span>All the 
                best<u></u><u></u></span></p>
                <p style="MARGIN-LEFT:36pt" class="MsoNormal"><span>SeB<br><br><br><u></u><u></u></span></p>
                <blockquote>
                  <p style="MARGIN-BOTTOM:12pt;MARGIN-LEFT:36pt;MARGIN-RIGHT:0cm" class="MsoNormal"><span>Le 15 nov. 2017 
                  Ã  07:59, Kan Kaili <</span><a href="mailto:kankaili@gmail.com" target="_blank"><span>kankaili@gmail.com</span><span></span></a><span>> a Ã©crit 
                  :<u></u><u></u></span></p>
                  <p style="MARGIN-LEFT:36pt" class="MsoNormal"><span><span style="FONT-SIZE:10pt">Hi, Alan and all,</span></span><span><u></u><u></u></span></p>
                  <p style="MARGIN-LEFT:36pt" class="MsoNormal"><span><br>  
                  <u></u><u></u></span></p>
                  <p style="MARGIN-LEFT:36pt" class="MsoNormal"><span><span style="FONT-SIZE:10pt">Javier's forwarded email says: "In an 
                  effort to protect .pr registrants from losing their domain 
                  names within the affected area by hurricane Maria, Puerto Rico 
                  Top Level Domain will extend the expiration date of all the 
                  domain names that expired on September 20th or thereafter to 
                  January 2, 2018. We will reassess the situation at the end of 
                  the previously mentioned period to determine whether or not it 
                  is necessary to take other preventive measures. 
                  "</span></span><span><u></u><u></u></span></p>
                  <p style="MARGIN-LEFT:36pt" class="MsoNormal"><span><br>  
                  <u></u><u></u></span></p>
                  <p style="MARGIN-LEFT:36pt" class="MsoNormal"><span><span style="FONT-SIZE:10pt">As I understand, if the registrant 
                  does not renew in time, the registry/registrar would terminate 
                  this registration and make the domain available to other 
                  potential buyers.  This would take some manpower (and 
                  cost) to implement.  However, if nothing is done for a 
                  period of time, there should not be much, if any, occuring 
                  costs.</span></span><span><u></u><u></u></span></p>
                  <p style="MARGIN-LEFT:36pt" class="MsoNormal"><span><br>  
                  <u></u><u></u></span></p>
                  <p style="MARGIN-LEFT:36pt" class="MsoNormal"><span><span style="FONT-SIZE:10pt">If my above understanding is correct, 
                  this should indeed be a rather straightforward PDP.  As a 
                  matter of fact, I suspect some of the registries/registrars 
                  would prefer to include this in their contracts with the 
                  registrant in order to be more competitive.</span></span><span><u></u><u></u></span></p>
                  <p style="MARGIN-LEFT:36pt" class="MsoNormal"><span><br>  
                  <u></u><u></u></span></p>
                  <p style="MARGIN-LEFT:36pt" class="MsoNormal"><span><span style="FONT-SIZE:10pt">Thus, if nobody else, I would like to 
                  take the lead on this issue and try it out.</span></span><span><u></u><u></u></span></p>
                  <p style="MARGIN-LEFT:36pt" class="MsoNormal"><span><br>  
                  <u></u><u></u></span></p>
                  <p style="MARGIN-LEFT:36pt" class="MsoNormal"><span><span style="FONT-SIZE:10pt">Thank you!</span></span><span><u></u><u></u></span></p>
                  <p style="MARGIN-LEFT:36pt" class="MsoNormal"><span><br>  
                  <u></u><u></u></span></p>
                  <p style="MARGIN-LEFT:36pt" class="MsoNormal"><span><span style="FONT-SIZE:10pt">Kaili</span></span><span><u></u><u></u></span></p>
                  <p style="MARGIN-LEFT:36pt" class="MsoNormal"><span><br>  
                  <u></u><u></u></span></p>
                  <p style="MARGIN-LEFT:36pt" class="MsoNormal"><span><br>  
                  <u></u><u></u></span></p>
                  <p style="MARGIN-LEFT:36pt" class="MsoNormal"><span><br><br><u></u><u></u></span></p>
                  <blockquote>
                    <p style="MARGIN-LEFT:36pt" class="MsoNormal"><span>----- Original 
                    Message -----<u></u><u></u></span></p>
                    <p style="MARGIN-LEFT:36pt" class="MsoNormal"><span>From: </span><a href="mailto:alan.greenberg@mcgill.ca" target="_blank"><span>Alan 
                    Greenberg</span><span></span></a><span><u></u><u></u></span></p>
                    <p style="MARGIN-LEFT:36pt" class="MsoNormal"><span>To: </span><a href="mailto:alac-internal@atlarge-lists.icann.org" target="_blank"><span>ALAC Internal 
                    List</span><span></span></a><span> ; </span><a href="mailto:alac-internal@atlarge-lists.icann.org" target="_blank"><span>ALAC Internal 
                    List</span><span></span></a><span><u></u><u></u></span></p>
                    <p style="MARGIN-LEFT:36pt" class="MsoNormal"><span>Sent: Wednesday, 
                    November 15, 2017 3:58 AM<u></u><u></u></span></p>
                    <p style="MARGIN-BOTTOM:12pt;MARGIN-LEFT:36pt;MARGIN-RIGHT:0cm" class="MsoNormal"><span>Subject: Re: 
                    [ALAC-Internal] Hurricane Maria Domain Registration 
                    protection Protocol<u></u><u></u></span></p>
                    <p style="MARGIN-BOTTOM:12pt;MARGIN-LEFT:36pt;MARGIN-RIGHT:0cm" class="MsoNormal"><span>Actually Seun, I 
                    think this could be a rather easy PDP, if approached 
                    properly and if we can propose a remediation that makes 
                    sense. One of the more interesting aspects is that any 
                    remediation implies registrars and registries providing 
                    service without being paid up-front, or potentially ever. 
                    <u></u><u></u></span></p>
                    <p style="MARGIN-BOTTOM:12pt;MARGIN-LEFT:36pt;MARGIN-RIGHT:0cm" class="MsoNormal"><span>Alan<u></u><u></u></span></p>
                    <p style="MARGIN-LEFT:36pt" class="MsoNormal"><span>At 14/11/2017 01:47 
                    PM, Seun Ojedeji wrote:<br><br><br><u></u><u></u></span></p>
                    <blockquote>
                      <p style="MARGIN-BOTTOM:12pt;MARGIN-LEFT:36pt;MARGIN-RIGHT:0cm" class="MsoNormal"><span>Great gesture from 
                      .PR. I see why .pr could easily take this up and I hope 
                      future applicable ccTLD will learn from the gesture of 
                      .pr. <u></u><u></u></span></p>
                      <p style="MARGIN-BOTTOM:12pt;MARGIN-LEFT:36pt;MARGIN-RIGHT:0cm" class="MsoNormal"><span>That said, I 
                      wonder how this can be applicable globally for gtlds, 
                      except through a PDP but I do have my doubt if this can 
                      survive a GNSO PDP. <u></u><u></u></span></p>
                      <p style="MARGIN-BOTTOM:12pt;MARGIN-LEFT:36pt;MARGIN-RIGHT:0cm" class="MsoNormal"><span>Nevertheless 
                      perhaps it's worth a try.<u></u><u></u></span></p>
                      <p style="MARGIN-LEFT:36pt" class="MsoNormal"><span>Regards<u></u><u></u></span></p>
                      <p style="MARGIN-LEFT:36pt" class="MsoNormal"><span>Sent from my 
                      mobile<u></u><u></u></span></p>
                      <p style="MARGIN-BOTTOM:12pt;MARGIN-LEFT:36pt;MARGIN-RIGHT:0cm" class="MsoNormal"><span>Kindly excuse 
                      brevity and typos<u></u><u></u></span></p>
                      <p style="MARGIN-LEFT:36pt" class="MsoNormal"><span>On Nov 14, 2017 
                      7:09 PM, "Javier Rua" <</span><a href="mailto:javrua@gmail.com" target="_blank"><span>javrua@gmail.com</span><span></span></a><span>> wrote: 
                      <u></u><u></u></span></p>
                      <p style="MARGIN-LEFT:36pt" class="MsoNormal"><span>Dear ALAC, 
                      <u></u><u></u></span></p>
                      <p style="MARGIN-BOTTOM:12pt;MARGIN-LEFT:36pt;MARGIN-RIGHT:0cm" class="MsoNormal"><span>On the important 
                      issue that has been diligently brought by John, and 
                      seconded by many, myself included, regarding potential 
                      risks of gTLD expirations (non-renewal) during and post 
                      natural disaster-related electricity, internet and general 
                      logistical failures, I share a bit of info that can be 
                      helpful (sent to me by our friends at .PR/ccNSO) to 
                      continue framing a discussion of possible ALAC 
                      recommendations on global ICANN/ARIN prevention and/or 
                      mitigation measures.<br><br><u></u><u></u></span></p>
                      <p style="MARGIN-BOTTOM:12pt;MARGIN-LEFT:36pt;MARGIN-RIGHT:0cm" class="MsoNormal"><span>Javier 
                      Rúa-Jovet<u></u><u></u></span></p>
                      <p style="MARGIN-LEFT:36pt" class="MsoNormal"><span></span><a href="tel:+1%20787-396-6511" target="_blank"><span>+1-787-396-6511</span><span></span></a><span> 
                      <u></u><u></u></span></p>
                      <p style="MARGIN-LEFT:36pt" class="MsoNormal"><span>twitter: @javrua 
                      <u></u><u></u></span></p>
                      <p style="MARGIN-LEFT:36pt" class="MsoNormal"><span>skype: javier.rua1 
                      <u></u><u></u></span></p>
                      <p style="MARGIN-LEFT:36pt" class="MsoNormal"><span></span><a href="https://www.linkedin.com/in/javrua" target="_blank"><span>https://www.linkedin.com/in/<wbr>javrua</span><span></span></a><span> 
                      <u></u><u></u></span></p>
                      <p style="MARGIN-LEFT:36pt" class="MsoNormal"><span>On Nov 14, 2017, 
                      at 1:23 PM, Pablo Rodriguez <</span><a href="mailto:pablo@nic.pr" target="_blank"><span>pablo@nic.pr</span><span></span></a><span>> 
                      wrote:<br><br><br><u></u><u></u></span></p>
                      <blockquote>
                        <p style="MARGIN-LEFT:36pt" class="MsoNormal"><span>Dear Javier, 
                        <u></u><u></u></span></p>
                        <p style="MARGIN-LEFT:36pt" class="MsoNormal"><span>In 2011, Japan 
                        suferred two terrible disasters, an 9.0 earthquake 
                        followed by a Tsunami. <u></u><u></u></span></p>
                        <p style="MARGIN-LEFT:36pt" class="MsoNormal"><span>Puerto Rico Top 
                        Level Domain (.pr) sprung into action and search our 
                        databases to find all the domain name registrations in 
                        which "Japan"  appeared as the  country in any 
                        of the three contacts (registrant, admin, or Tech). 
                        Several of our registrars in Japan were very pleased to 
                        learn when they were finally able to contact us that we 
                        had proactively extended their expiration dates to 
                        prevent domain name losses due to lack of connectivity 
                        as a result of the disasters. <u></u><u></u></span></p>
                        <p style="MARGIN-LEFT:36pt" class="MsoNormal"><span>Below you will 
                        find a similar example to protect the cyber real estate 
                        of registrants who reside in Puerto Rico and the 
                        affected areas (AVI, BVI, etc) by hurricane Maria. 
                        <u></u><u></u></span></p>
                        <p style="MARGIN-LEFT:36pt" class="MsoNormal"><span>Hurricane 
                        María Domain Registration protection Protocol 
                        <u></u><u></u></span></p>
                        <p style="MARGIN-LEFT:36pt" class="MsoNormal"><span>Puerto Rico Top 
                        Level Domain (.pr) has been 100% operational pre-, 
                        during, and post hurricane Maria. <u></u><u></u></span></p>
                        <p style="MARGIN-LEFT:36pt" class="MsoNormal"><span>In an effort to 
                        protect .pr registrants from losing their domain names 
                        within the affected area by hurricane Maria, Puerto Rico 
                        Top Level Domain will extend the expiration date of all 
                        the domain names that expired on September 20th or 
                        thereafter to January 2, 2018. We will reassess the 
                        situation at the end of the previously mentioned period 
                        to determine whether or not it is necessary to take 
                        other preventive measures.     
                        <u></u><u></u></span></p>
                        <p style="MARGIN-LEFT:36pt" class="MsoNormal"><span>Huracán 
                        María Protocolo de protección de registros de 
                        dominios <u></u><u></u></span></p>
                        <p style="MARGIN-LEFT:36pt" class="MsoNormal"><span>Puerto Rico Top 
                        Level Domain ha estado 100% operacional previo a, 
                        durante, y post huracán María. En una 
                        iniciativa para proteger los registros de 
                        d<u></u><u></u></span></p></blockquote></blockquote></blockquote></blockquote></blockquote>
              <p style="MARGIN-LEFT:36pt" class="MsoNormal"><span>______________________________<wbr>_________________ 
              <u></u><u></u></span></p>
              <p style="MARGIN-LEFT:36pt" class="MsoNormal"><span>ALAC-Internal mailing list 
              <u></u><u></u></span></p>
              <p style="MARGIN-LEFT:36pt" class="MsoNormal"><span></span><a href="mailto:ALAC-Internal@atlarge-lists.icann.org" target="_blank"><span>ALAC-Internal@atlarge-lists.<wbr>icann.org</span><span></span></a><span> <u></u><u></u></span></p>
              <p style="MARGIN-LEFT:36pt" class="MsoNormal"><span></span><a href="https://atlarge-lists.icann.org/mailman/listinfo/alac-internal" target="_blank"><span>https://atlarge-lists.icann.<wbr>org/mailman/listinfo/alac-<wbr>internal</span><span></span></a><span> <u></u><u></u></span></p>
              <p style="MARGIN-LEFT:36pt" class="MsoNormal"><span>ALAC Wiki: </span><a href="https://community.icann.org/display/atlarge/At-Large+Advisory+Committee+(ALAC)" target="_blank"><span>https://community.icann.org/<wbr>display/atlarge/At-Large+<wbr>Advisory+Committee+(ALAC)</span><span></span></a><span> <u></u><u></u></span></p>
              <p style="MARGIN-BOTTOM:12pt;MARGIN-LEFT:36pt;MARGIN-RIGHT:0cm" class="MsoNormal"><span>At-Large Website: 
              </span><a href="http://atlarge.icann.org/" target="_blank"><span>http://atlarge.icann.org</span><span></span></a><span><br><br><u></u><u></u></span></p>
              <p style="MARGIN-LEFT:36pt" class="MsoNormal"><span>Content-Type: text/plain; 
              charset="us-ascii"<u></u><u></u></span></p>
              <p style="MARGIN-LEFT:36pt" class="MsoNormal"><span>Content-Transfer-Encoding: 
              7bit<u></u><u></u></span></p>
              <p style="MARGIN-LEFT:36pt" class="MsoNormal"><span>Content-Disposition: 
              inline<u></u><u></u></span></p>
              <p style="MARGIN-LEFT:36pt" class="MsoNormal"><span>X-Microsoft-Exchange-<wbr>Diagnostics:<u></u><u></u></span></p>
              <p style="MARGIN-BOTTOM:12pt;MARGIN-LEFT:36pt;MARGIN-RIGHT:0cm" class="MsoNormal"><span>        
              1;YQXPR0101MB1589;27:<wbr>raBhEnfAMJQK4wDOm1IlxWVVwpJp+<wbr>Dg0C5wgVnrS735mqr7nV2PJY5mpD8P<wbr>CkL3jVCGhdcabIpVgTSg8PzXBKr8W0<wbr>7FfOt/LOau7AiM7k0B2uK67oGU/<wbr>T3LPrIzm0RcQ<u></u><u></u></span></p>
              <p style="MARGIN-LEFT:36pt" class="MsoNormal"><span>______________________________<wbr>_________________<u></u><u></u></span></p>
              <p style="MARGIN-LEFT:36pt" class="MsoNormal"><span>ALAC-Internal mailing 
              list<u></u><u></u></span></p>
              <p style="MARGIN-LEFT:36pt" class="MsoNormal"><span></span><a href="mailto:ALAC-Internal@atlarge-lists.icann.org" target="_blank"><span>ALAC-Internal@atlarge-lists.<wbr>icann.org</span><span></span></a><span><u></u><u></u></span></p>
              <p style="MARGIN-BOTTOM:12pt;MARGIN-LEFT:36pt;MARGIN-RIGHT:0cm" class="MsoNormal"><span></span><a href="https://atlarge-lists.icann.org/mailman/listinfo/alac-internal" target="_blank"><span>https://atlarge-lists.icann.<wbr>org/mailman/listinfo/alac-<wbr>internal</span><span></span></a><span><u></u><u></u></span></p>
              <p style="MARGIN-BOTTOM:12pt;MARGIN-LEFT:36pt;MARGIN-RIGHT:0cm" class="MsoNormal"><span>ALAC 
              Wiki: </span><a href="https://community.icann.org/display/atlarge/At-Large+Advisory+Committee+(ALAC" target="_blank"><span>https://community.icann.org/<wbr>display/atlarge/At-Large+<wbr>Advisory+Committee+(ALAC</span><span></span></a><span> )<u></u><u></u></span></p>
              <p style="MARGIN-LEFT:36pt" class="MsoNormal"><span>At-Large Website: 
              </span><a href="http://atlarge.icann.org/" target="_blank"><span>http://atlarge.icann.org</span><span></span></a><span> 
              <u></u><u></u></span></p></div></blockquote>
            <p class="MsoNormal"><span><u></u> <u></u></span></p>
            <p class="MsoNormal"><span><img style="WIDTH:14.51in;HEIGHT:0.01in" id="m_6458118516800140713Horizontal_x0020_Line_x0020_1" border="0" src="cid:48DBEBF99ADB416CA4129A0D25683220@LENOVOC0574B68" width="1393" height="1"></span><span><u></u><u></u></span></p>
            <p class="MsoNormal"><span><u></u> <u></u></span></p>
            <p style="MARGIN-LEFT:36pt" class="MsoNormal"><span>______________________________<wbr>_________________<u></u><u></u></span></p>
            <p style="MARGIN-LEFT:36pt" class="MsoNormal"><span>ALAC-Internal mailing 
            list<u></u><u></u></span></p>
            <p style="MARGIN-LEFT:36pt" class="MsoNormal"><span></span><a href="mailto:ALAC-Internal@atlarge-lists.icann.org" target="_blank"><span>ALAC-Internal@atlarge-lists.<wbr>icann.org</span><span></span></a><span><u></u><u></u></span></p>
            <p style="MARGIN-BOTTOM:12pt;MARGIN-LEFT:36pt;MARGIN-RIGHT:0cm" class="MsoNormal"><span></span><a href="https://atlarge-lists.icann.org/mailman/listinfo/alac-internal" target="_blank"><span>https://atlarge-lists.icann.<wbr>org/mailman/listinfo/alac-<wbr>internal</span><span></span></a><span><u></u><u></u></span></p>
            <p style="MARGIN-BOTTOM:12pt;MARGIN-LEFT:36pt;MARGIN-RIGHT:0cm" class="MsoNormal"><span>ALAC 
            Wiki: </span><a href="https://community.icann.org/display/atlarge/At-Large+Advisory+Committee+(ALAC)" target="_blank"><span>https://community.icann.org/<wbr>display/atlarge/At-Large+<wbr>Advisory+Committee+(ALAC)</span><span></span></a><span> <u></u><u></u></span></p>
            <p style="MARGIN-LEFT:36pt" class="MsoNormal"><span>At-Large Website: </span><a href="http://atlarge.icann.org" target="_blank"><span>http://atlarge.icann.org</span><span></span></a><span> <u></u><u></u></span></p>
            <p style="MARGIN-LEFT:36pt" class="MsoNormal"><span>______________________________<wbr>_________________<u></u><u></u></span></p>
            <p style="MARGIN-LEFT:36pt" class="MsoNormal"><span>ALAC-Internal mailing 
            list<u></u><u></u></span></p>
            <p style="MARGIN-LEFT:36pt" class="MsoNormal"><span></span><a href="mailto:ALAC-Internal@atlarge-lists.icann.org" target="_blank"><span>ALAC-Internal@atlarge-lists.<wbr>icann.org</span><span></span></a><span><u></u><u></u></span></p>
            <p style="MARGIN-BOTTOM:12pt;MARGIN-LEFT:36pt;MARGIN-RIGHT:0cm" class="MsoNormal"><span></span><a href="https://atlarge-lists.icann.org/mailman/listinfo/alac-internal" target="_blank"><span>https://atlarge-lists.icann.<wbr>org/mailman/listinfo/alac-<wbr>internal</span><span></span></a><span><u></u><u></u></span></p>
            <p style="MARGIN-BOTTOM:12pt;MARGIN-LEFT:36pt;MARGIN-RIGHT:0cm" class="MsoNormal"><span>ALAC 
            Wiki: </span><a href="https://community.icann.org/display/atlarge/At-Large+Advisory+Committee+(ALAC)" target="_blank"><span>https://community.icann.org/<wbr>display/atlarge/At-Large+<wbr>Advisory+Committee+(ALAC)</span><span></span></a><span> <u></u><u></u></span></p>
            <p style="MARGIN-BOTTOM:12pt;MARGIN-LEFT:36pt;MARGIN-RIGHT:0cm" class="MsoNormal"><span>At-Large Website: </span><a href="http://atlarge.icann.org/" target="_blank"><span>http://atlarge.icann.org</span><span></span></a><span> <u></u><u></u></span></p>
            <p style="MARGIN-LEFT:36pt" class="MsoNormal"><span>______________________________<wbr>_________________<u></u><u></u></span></p>
            <p style="MARGIN-LEFT:36pt" class="MsoNormal"><span>ALAC-Internal mailing 
            list<u></u><u></u></span></p>
            <p style="MARGIN-LEFT:36pt" class="MsoNormal"><span></span><a href="mailto:ALAC-Internal@atlarge-lists.icann.org" target="_blank"><span>ALAC-Internal@atlarge-lists.<wbr>icann.org</span><span></span></a><span><u></u><u></u></span></p>
            <p style="MARGIN-BOTTOM:12pt;MARGIN-LEFT:36pt;MARGIN-RIGHT:0cm" class="MsoNormal"><span></span><a href="https://atlarge-lists.icann.org/mailman/listinfo/alac-internal" target="_blank"><span>https://atlarge-lists.icann.<wbr>org/mailman/listinfo/alac-<wbr>internal</span><span></span></a><span><u></u><u></u></span></p>
            <p style="MARGIN-BOTTOM:12pt;MARGIN-LEFT:36pt;MARGIN-RIGHT:0cm" class="MsoNormal"><span>ALAC 
            Wiki: </span><a href="https://community.icann.org/display/atlarge/At-Large+Advisory+Committee+(ALAC)" target="_blank"><span>https://community.icann.org/<wbr>display/atlarge/At-Large+<wbr>Advisory+Committee+(ALAC)</span><span></span></a><span> <u></u><u></u></span></p>
            <p style="MARGIN-LEFT:36pt" class="MsoNormal"><span>At-Large Website: </span><a href="http://atlarge.icann.org" target="_blank"><span>http://atlarge.icann.org</span><span></span></a><span><br><br>Content-Type: 
            text/plain; charset="us-ascii"<br>Content-Transfer-Encoding: 
            7bit<br>Content-Disposition: 
            inline<br>X-Microsoft-Exchange-<wbr>Diagnostics:<br>         
            1;YQXPR0101MB1589;27:<wbr>lyPeFsMR2LTmaP9avmNEF6jqNJ598Y<wbr>+br+SsHKkIAjDu+<wbr>lGgTNx7rt1tleHhx8p4RzNSvOInojF<wbr>p9kpA8rUgsNDq2reLZaNotHxXgV/<wbr>Y14faCFJ7u3u8T+umX+wQQtKZ<br><br>______________________________<wbr>_________________<br>ALAC-Internal 
            mailing list<br></span><a href="mailto:ALAC-Internal@atlarge-lists.icann.org" target="_blank"><span>ALAC-Internal@atlarge-lists.<wbr>icann.org</span><span></span></a><span><br></span><a href="https://atlarge-lists.icann.org/mailman/listinfo/alac-internal" target="_blank"><span>https://atlarge-lists.icann.<wbr>org/mailman/listinfo/alac-<wbr>internal</span><span></span></a><span><br><br>ALAC Wiki: </span><a href="https://community.icann.org/display/atlarge/At-Large+Advisory+Committee+(ALAC" target="_blank"><span>https://community.icann.org/<wbr>display/atlarge/At-Large+<wbr>Advisory+Committee+(ALAC</span><span></span></a><span> )<br><br>At-Large Website: 
            </span><a href="http://atlarge.icann.org/" target="_blank"><span>http://atlarge.icann.org</span><span></span></a><span><u></u><u></u></span></p></div>
            <p style="MARGIN-BOTTOM:12pt" class="MsoNormal"><span><br>______________________________<wbr>_________________<br>ALAC-Internal 
            mailing list<br></span><a href="mailto:ALAC-Internal@atlarge-lists.icann.org" target="_blank"><span>ALAC-Internal@atlarge-lists.<wbr>icann.org</span><span></span></a><span><br></span><a href="https://atlarge-lists.icann.org/mailman/listinfo/alac-internal" target="_blank"><span>https://atlarge-lists.icann.<wbr>org/mailman/listinfo/alac-<wbr>internal</span><span></span></a><span><br><br>ALAC Wiki: </span><a href="https://community.icann.org/display/atlarge/At-Large+Advisory+Committee+(ALAC)" target="_blank"><span>https://community.icann.org/<wbr>display/atlarge/At-Large+<wbr>Advisory+Committee+(ALAC)</span><span></span></a><span><br><br>At-Large Website: 
            </span><a href="http://atlarge.icann.org" target="_blank"><span>http://atlarge.icann.org</span><span></span></a><span><u></u><u></u></span></p></div></div></div>
            <p style="MARGIN-BOTTOM:12pt" class="MsoNormal"><span><br>______________________________<wbr>_________________<br>ALAC-Internal 
            mailing list<br></span><a href="mailto:ALAC-Internal@atlarge-lists.icann.org" target="_blank"><span>ALAC-Internal@atlarge-lists.<wbr>icann.org</span><span></span></a><span><br></span><a href="https://atlarge-lists.icann.org/mailman/listinfo/alac-internal" target="_blank"><span>https://atlarge-lists.icann.<wbr>org/mailman/listinfo/alac-<wbr>internal</span><span></span></a><span><br><br>ALAC Wiki: </span><a href="https://community.icann.org/display/atlarge/At-Large+Advisory+Committee+(ALAC)" target="_blank"><span>https://community.icann.org/<wbr>display/atlarge/At-Large+<wbr>Advisory+Committee+(ALAC)</span><span></span></a><span><br><br>At-Large Website: 
            </span><a href="http://atlarge.icann.org" target="_blank"><span>http://atlarge.icann.org</span><span></span></a><span><u></u><u></u></span></p></blockquote></div>
          <p class="MsoNormal"><span><u></u> <u></u></span></p></div></div></blockquote>
        <blockquote style="MARGIN-TOP:5pt;MARGIN-BOTTOM:5pt">
          <div>
          <p class="MsoNormal"><span>______________________________<wbr>_________________<br>ALAC-Internal 
          mailing list<br></span><a href="mailto:ALAC-Internal@atlarge-lists.icann.org" target="_blank"><span>ALAC-Internal@atlarge-lists.<wbr>icann.org</span><span></span></a><span><br></span><a href="https://atlarge-lists.icann.org/mailman/listinfo/alac-internal" target="_blank"><span>https://atlarge-lists.icann.<wbr>org/mailman/listinfo/alac-<wbr>internal</span><span></span></a><span><br><br>ALAC Wiki: </span><a href="https://community.icann.org/display/atlarge/At-Large+Advisory+Committee+(ALAC)" target="_blank"><span>https://community.icann.org/<wbr>display/atlarge/At-Large+<wbr>Advisory+Committee+(ALAC)</span><span></span></a><span><br><br>At-Large Website: 
          </span><a href="http://atlarge.icann.org" target="_blank"><span>http://atlarge.icann.org</span><span></span></a><span><u></u><u></u></span></p></div></blockquote></div></div></div>
        <p style="MARGIN-BOTTOM:12pt" class="MsoNormal"><span><br>______________________________<wbr>_________________<br>ALAC-Internal 
        mailing list<br></span><a href="mailto:ALAC-Internal@atlarge-lists.icann.org" target="_blank"><span>ALAC-Internal@atlarge-lists.<wbr>icann.org</span><span></span></a><span><br></span><a href="https://atlarge-lists.icann.org/mailman/listinfo/alac-internal" target="_blank"><span>https://atlarge-lists.icann.<wbr>org/mailman/listinfo/alac-<wbr>internal</span><span></span></a><span><br><br>ALAC Wiki: </span><a href="https://community.icann.org/display/atlarge/At-Large+Advisory+Committee+(ALAC)" target="_blank"><span>https://community.icann.org/<wbr>display/atlarge/At-Large+<wbr>Advisory+Committee+(ALAC)</span><span></span></a><span><br><br>At-Large Website: 
        </span><a href="http://atlarge.icann.org" target="_blank"><span>http://atlarge.icann.org</span><span></span></a><span><u></u><u></u></span></p></blockquote></div>
      <p class="MsoNormal"><span><u></u> <u></u></span></p></div>
      <p class="MsoNormal"><span><img style="WIDTH:15.833in;HEIGHT:0.01in" id="m_6458118516800140713Horizontal_x0020_Line_x0020_2" border="0" src="cid:05AEAA3BD024432FB06B099232F3E21E@LENOVOC0574B68" width="1520" height="1"></span><span><u></u><u></u></span></p>
      <p class="MsoNormal"><span>______________________________<wbr>_________________<br>ALAC-Internal 
      mailing list<br></span><a href="mailto:ALAC-Internal@atlarge-lists.icann.org" target="_blank"><span>ALAC-Internal@atlarge-lists.<wbr>icann.org</span><span></span></a><span><br></span><a href="https://atlarge-lists.icann.org/mailman/listinfo/alac-internal" target="_blank"><span>https://atlarge-lists.icann.<wbr>org/mailman/listinfo/alac-<wbr>internal</span><span></span></a><span><br><br>ALAC Wiki: </span><a href="https://community.icann.org/display/atlarge/At-Large+Advisory+Committee+(ALAC)" target="_blank"><span>https://community.icann.org/<wbr>display/atlarge/At-Large+<wbr>Advisory+Committee+(ALAC)</span><span></span></a><span><br><br>At-Large Website: 
      </span><a href="http://atlarge.icann.org" target="_blank"><span>http://atlarge.icann.org</span><span></span></a><span><u></u><u></u></span></p></blockquote></div></blockquote>
  <blockquote style="MARGIN-TOP:5pt;MARGIN-BOTTOM:5pt">
    <div>
    <p class="MsoNormal"><span>______________________________<wbr>_________________<br>At-Large 
    mailing list<br></span><a href="mailto:At-Large@atlarge-lists.icann.org" target="_blank"><span>At-Large@atlarge-lists.icann.<wbr>org</span><span></span></a><span><br></span><a href="https://atlarge-lists.icann.org/mailman/listinfo/at-large" target="_blank"><span>https://atlarge-lists.icann.<wbr>org/mailman/listinfo/at-large</span><span></span></a><span><br><br>At-Large Official Site: 
    </span><a href="http://atlarge.icann.org" target="_blank"><span>http://atlarge.icann.org</span><span></span></a><span></span><u></u><u></u></p></div></blockquote></div></blockquote></div>
<br>______________________________<wbr>_________________<br>
ALAC-Internal mailing list<br>
<a href="mailto:ALAC-Internal@atlarge-lists.icann.org">ALAC-Internal@atlarge-lists.<wbr>icann.org</a><br>
<a href="https://atlarge-lists.icann.org/mailman/listinfo/alac-internal" rel="noreferrer" target="_blank">https://atlarge-lists.icann.<wbr>org/mailman/listinfo/alac-<wbr>internal</a><br>
<br>
ALAC Wiki: <a href="https://community.icann.org/display/atlarge/At-Large+Advisory+Committee+(ALAC)" rel="noreferrer" target="_blank">https://community.icann.org/<wbr>display/atlarge/At-Large+<wbr>Advisory+Committee+(ALAC)</a><br>
<br>
At-Large Website: <a href="http://atlarge.icann.org" rel="noreferrer" target="_blank">http://atlarge.icann.org</a><br>
<br></blockquote></div></div>