<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META content="text/html; charset=utf-8" http-equiv=Content-Type>
<META name=GENERATOR content="MSHTML 8.00.6001.23942">
<STYLE></STYLE>
</HEAD>
<BODY bgColor=#ffffff>
<DIV>
<DIV><FONT size=2 face=宋体>Hi, </FONT></DIV>
<DIV><FONT size=2 face=宋体></FONT> </DIV>
<DIV><FONT size=2 face=宋体>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.</FONT></DIV>
<DIV><FONT size=2 face=宋体></FONT> </DIV>
<DIV><FONT size=2 face=宋体>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:</FONT></DIV>
<DIV><FONT size=2 face=宋体>- ISC's academic people will go to the media and have
it heard. </FONT></DIV>
<DIV><FONT size=2 face=宋体>- In response, a few ISC's industry members will
respond with a voluntary solution. </FONT></DIV>
<DIV><FONT size=2 face=宋体>- ISC's scholars will compare different solutions and
present a preferred one to ISC.</FONT></DIV>
<DIV><FONT size=2 face=宋体>- 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.</FONT></DIV>
<DIV><FONT size=2 face=宋体>- 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.)</FONT></DIV>
<DIV><FONT size=2 face=宋体>- The ministry (MIIT) closely observes the whole
process, provides support, and makes the solution into regulation when it
is widely followed.</FONT></DIV>
<DIV><FONT size=2 face=宋体></FONT> </DIV>
<DIV><FONT size=2 face=宋体>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.</FONT></DIV>
<DIV><FONT size=2 face=宋体></FONT> </DIV>
<DIV><FONT size=2 face=宋体>As I see it, ccNSO is likely to first adopt to this
"distress relief" measure, while GNSO will then have to follow.</FONT></DIV>
<DIV><FONT size=2 face=宋体></FONT> </DIV>
<DIV><FONT size=2 face=宋体>Thank you!</FONT></DIV>
<DIV><FONT size=2 face=宋体></FONT> </DIV>
<DIV><FONT size=2 face=宋体>Kaili</FONT></DIV>
<DIV><FONT size=2 face=宋体></FONT> </DIV>
<DIV><FONT size=2 face=宋体></FONT> </DIV></DIV>
<BLOCKQUOTE
style="BORDER-LEFT: #000000 2px solid; PADDING-LEFT: 5px; PADDING-RIGHT: 0px; MARGIN-LEFT: 5px; MARGIN-RIGHT: 0px">
<DIV style="FONT: 9pt 宋体">----- Original Message ----- </DIV>
<DIV style="FONT: 9pt 宋体; BACKGROUND: #e4e4e4; font-color: black"><B>From:</B>
<A title=maureen.hilyard@gmail.com
href="mailto:maureen.hilyard@gmail.com">Maureen Hilyard</A> </DIV>
<DIV style="FONT: 9pt 宋体"><B>To:</B> <A
title=alac-internal@atlarge-lists.icann.org
href="mailto:alac-internal@atlarge-lists.icann.org">ALAC Internal List</A>
</DIV>
<DIV style="FONT: 9pt 宋体"><B>Sent:</B> Friday, November 17, 2017 12:30
AM</DIV>
<DIV style="FONT: 9pt 宋体"><B>Subject:</B> Re: [ALAC-Internal] Hurricane Maria
Domain Registration protectionProtocol</DIV>
<DIV><BR></DIV>
<DIV dir=ltr>Hi everyone
<DIV><BR></DIV>
<DIV>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.</DIV>
<DIV><BR></DIV>
<DIV>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"</DIV>
<DIV><BR></DIV>
<DIV>Katrina, in conjunction with Alejandra who is their Meeting Programme
Coordinator, have suggested: </DIV>
<DIV>
<P
style="MARGIN: 0cm 0cm 0pt 36pt; FONT-FAMILY: 'Times New Roman',serif; FONT-SIZE: 12pt"
class=gmail-m_7099697691176340694MsoListParagraph><SPAN
style="FONT-FAMILY: Calibri,sans-serif; COLOR: rgb(31,73,125); FONT-SIZE: 11pt"><BR></SPAN></P>
<P
style="MARGIN: 0cm 0cm 0pt 36pt; FONT-FAMILY: 'Times New Roman',serif; FONT-SIZE: 12pt"
class=gmail-m_7099697691176340694MsoListParagraph><SPAN
style="FONT-FAMILY: Calibri,sans-serif; COLOR: rgb(31,73,125); FONT-SIZE: 11pt">-<SPAN
style="LINE-HEIGHT: normal; FONT-FAMILY: 'Times New Roman'; FONT-SIZE: 7pt; font-stretch: normal"> </SPAN></SPAN><U></U><SPAN
style="FONT-FAMILY: Calibri,sans-serif; COLOR: rgb(31,73,125); FONT-SIZE: 11pt">We
organise a discussion at ccNSO Members meeting <SPAN class=gmail-aBn
tabIndex=0><SPAN class=gmail-aQJ>on Tuesday</SPAN></SPAN> or <SPAN
class=gmail-aBn tabIndex=0><SPAN
class=gmail-aQJ>Wednesday</SPAN></SPAN><U></U><U></U></SPAN></P>
<P
style="MARGIN: 0cm 0cm 0pt 36pt; FONT-FAMILY: 'Times New Roman',serif; FONT-SIZE: 12pt"
class=gmail-m_7099697691176340694MsoListParagraph><U></U><SPAN
style="FONT-FAMILY: Calibri,sans-serif; COLOR: rgb(31,73,125); FONT-SIZE: 11pt">-<SPAN
style="LINE-HEIGHT: normal; FONT-FAMILY: 'Times New Roman'; FONT-SIZE: 7pt; font-stretch: normal"> </SPAN></SPAN><U></U><SPAN
style="FONT-FAMILY: Calibri,sans-serif; COLOR: rgb(31,73,125); FONT-SIZE: 11pt">“How
to help ccTLDs, registrars and registrants in case of severely damaged
infrastructure?” (or a similar title)<U></U><U></U></SPAN></P>
<P
style="MARGIN: 0cm 0cm 0pt 36pt; FONT-FAMILY: 'Times New Roman',serif; FONT-SIZE: 12pt"
class=gmail-m_7099697691176340694MsoListParagraph><U></U><SPAN
style="FONT-FAMILY: Calibri,sans-serif; COLOR: rgb(31,73,125); FONT-SIZE: 11pt">-<SPAN
style="LINE-HEIGHT: normal; FONT-FAMILY: 'Times New Roman'; FONT-SIZE: 7pt; font-stretch: normal"> </SPAN></SPAN><U></U><SPAN
style="FONT-FAMILY: Calibri,sans-serif; COLOR: rgb(31,73,125); FONT-SIZE: 11pt">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<U></U><U></U></SPAN></P>
<P
style="MARGIN: 0cm 0cm 0pt 36pt; FONT-FAMILY: 'Times New Roman',serif; FONT-SIZE: 12pt"
class=gmail-m_7099697691176340694MsoListParagraph><U></U><SPAN
style="FONT-FAMILY: Calibri,sans-serif; COLOR: rgb(31,73,125); FONT-SIZE: 11pt">-<SPAN
style="LINE-HEIGHT: normal; FONT-FAMILY: 'Times New Roman'; FONT-SIZE: 7pt; font-stretch: normal"> </SPAN></SPAN><U></U><SPAN
style="FONT-FAMILY: Calibri,sans-serif; COLOR: rgb(31,73,125); FONT-SIZE: 11pt">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<U></U><U></U></SPAN></P>
<P
style="MARGIN: 0cm 0cm 0pt 36pt; FONT-FAMILY: 'Times New Roman',serif; FONT-SIZE: 12pt"
class=gmail-m_7099697691176340694MsoListParagraph><U></U><SPAN
style="FONT-FAMILY: Calibri,sans-serif; COLOR: rgb(31,73,125); FONT-SIZE: 11pt">-<SPAN
style="LINE-HEIGHT: normal; FONT-FAMILY: 'Times New Roman'; FONT-SIZE: 7pt; font-stretch: normal"> </SPAN></SPAN><U></U><SPAN
style="FONT-FAMILY: Calibri,sans-serif; COLOR: rgb(31,73,125); FONT-SIZE: 11pt">We
will invite ROs. They are the driving force and the ones who can help the
most. <U></U></SPAN><SPAN
style="FONT-FAMILY: arial,sans-serif; FONT-SIZE: small"> </SPAN><SPAN
style="FONT-FAMILY: Calibri,sans-serif; COLOR: rgb(31,73,125); FONT-SIZE: 14px">For
example, during the LACTLD Technical workshop they try to establish redundancy
among fellow ccTLDs, especially for small registries.</SPAN></P>
<P
style="MARGIN: 0cm 0cm 0pt 36pt; FONT-FAMILY: 'Times New Roman',serif; FONT-SIZE: 12pt"
class=gmail-m_7099697691176340694MsoListParagraph><U></U><SPAN
style="FONT-FAMILY: Calibri,sans-serif; COLOR: rgb(31,73,125); FONT-SIZE: 11pt">-<SPAN
style="LINE-HEIGHT: normal; FONT-FAMILY: 'Times New Roman'; FONT-SIZE: 7pt; font-stretch: normal"> </SPAN></SPAN><U></U><SPAN
style="FONT-FAMILY: Calibri,sans-serif; COLOR: rgb(31,73,125); FONT-SIZE: 11pt">Discussions</SPAN></P>
<P
style="MARGIN: 0cm 0cm 0pt 36pt; FONT-FAMILY: 'Times New Roman',serif; FONT-SIZE: 12pt"
class=gmail-m_7099697691176340694MsoListParagraph><SPAN
style="FONT-FAMILY: Calibri,sans-serif; COLOR: rgb(31,73,125); FONT-SIZE: 11pt"><BR></SPAN></P>
<P
style="MARGIN: 0cm 0cm 0pt 36pt; FONT-FAMILY: 'Times New Roman',serif; FONT-SIZE: 12pt"
class=gmail-m_7099697691176340694MsoListParagraph><SPAN
style="FONT-FAMILY: arial,sans-serif; FONT-SIZE: small">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
style="FONT-FAMILY: Calibri,sans-serif; COLOR: rgb(31,73,125); FONT-SIZE: 11pt"><BR></SPAN></P>
<P
style="MARGIN: 0cm 0cm 0pt 36pt; FONT-FAMILY: 'Times New Roman',serif; FONT-SIZE: 12pt"
class=gmail-m_7099697691176340694MsoListParagraph><SPAN
style="FONT-FAMILY: arial,sans-serif; FONT-SIZE: small"><BR></SPAN></P>
<P
style="MARGIN: 0cm 0cm 0pt 36pt; FONT-FAMILY: 'Times New Roman',serif; FONT-SIZE: 12pt"
class=gmail-m_7099697691176340694MsoListParagraph><SPAN
style="FONT-FAMILY: arial,sans-serif; FONT-SIZE: small">Comments?</SPAN></P>
<P
style="MARGIN: 0cm 0cm 0pt 36pt; FONT-FAMILY: 'Times New Roman',serif; FONT-SIZE: 12pt"
class=gmail-m_7099697691176340694MsoListParagraph><SPAN
style="FONT-FAMILY: Calibri,sans-serif; COLOR: rgb(31,73,125); FONT-SIZE: 11pt"><BR></SPAN></P></DIV></DIV>
<DIV class=gmail_extra><BR>
<DIV class=gmail_quote>On Wed, Nov 15, 2017 at 8:24 PM, Javier Rua <SPAN
dir=ltr><<A href="mailto:javrua@gmail.com"
target=_blank>javrua@gmail.com</A>></SPAN> wrote:<BR>
<BLOCKQUOTE
style="BORDER-LEFT: #ccc 1px solid; MARGIN: 0px 0px 0px 0.8ex; PADDING-LEFT: 1ex"
class=gmail_quote>
<DIV dir=auto>Don’t leave out gTLDs !<BR><BR>
<DIV id=m_3055778373556209487AppleMailSignature>Javier Rúa-Jovet<SPAN>
<DIV><BR></DIV>
<DIV>
<DIV><SPAN><A href="tel:+1%20787-396-6511" target=_blank
value="+17873966511">+1-787-396-6511</A></SPAN></DIV>
<DIV><SPAN>twitter: @javrua</SPAN></DIV>
<DIV><SPAN>skype: javier.rua1</SPAN></DIV>
<DIV><FONT color=#000000><A href="https://www.linkedin.com/in/javrua"
target=_blank>https://www.linkedin.com/in/<WBR>javrua</A> </FONT></DIV>
<DIV><BR></DIV></DIV></SPAN></DIV>
<DIV>
<DIV class=h5>
<DIV><BR>On Nov 16, 2017, at 2:19 AM, Maureen Hilyard <<A
href="mailto:maureen.hilyard@gmail.com"
target=_blank>maureen.hilyard@gmail.com</A>> wrote:<BR><BR></DIV>
<BLOCKQUOTE type="cite">
<DIV>
<DIV dir=ltr>I agree Seun
<DIV><BR></DIV>
<DIV>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. </DIV>
<DIV><BR></DIV>
<DIV>Ill get back to the team when she responds.</DIV>
<DIV><BR></DIV>
<DIV>Maureen</DIV></DIV>
<DIV class=gmail_extra><BR>
<DIV class=gmail_quote>On Wed, Nov 15, 2017 at 7:53 PM, Seun Ojedeji <SPAN
dir=ltr><<A href="mailto:seun.ojedeji@gmail.com"
target=_blank>seun.ojedeji@gmail.com</A>></SPAN> wrote:<BR>
<BLOCKQUOTE
style="BORDER-LEFT: #ccc 1px solid; MARGIN: 0px 0px 0px 0.8ex; PADDING-LEFT: 1ex"
class=gmail_quote>
<DIV dir=auto>Hello Alan,
<DIV dir=auto><BR></DIV>
<DIV dir=auto>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.</DIV>
<DIV dir=auto><BR></DIV>
<DIV dir=auto>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<SPAN><BR>
<DIV dir=auto data-smartmail="gmail_signature">Sent from
my mobile<BR>Kindly excuse brevity and
typos</DIV></SPAN></DIV></DIV>
<DIV class=m_3055778373556209487HOEnZb>
<DIV class=m_3055778373556209487h5>
<DIV class=gmail_extra><BR>
<DIV class=gmail_quote>On Nov 15, 2017 8:46 PM, "Alan Greenberg" <<A
href="mailto:alan.greenberg@mcgill.ca"
target=_blank>alan.greenberg@mcgill.ca</A>> wrote:<BR
type="attribution">
<BLOCKQUOTE
style="BORDER-LEFT: #ccc 1px solid; MARGIN: 0px 0px 0px 0.8ex; PADDING-LEFT: 1ex"
class=gmail_quote>
<DIV>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 - <A
href="https://www.icann.org/resources/pages/governance/bylaws-en/#annexA"
target=_blank>https://www.icann.org/resource<WBR>s/pages/governance/bylaws-en/#<WBR>annexA</A>.
The Request for an Issue Report and the processes which should precede
it are laid out in the GNSO PDP Manual (<A
href="https://gnso.icann.org/en/council/annex-2-pdp-manual-01sep16-en.pdf"
target=_blank>
https://gnso.icann.org/en/coun<WBR>cil/annex-2-pdp-manual-01sep16<WBR>-en.pdf</A>
).<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>
<BLOCKQUOTE
class=m_3055778373556209487m_-4360846149451879971m_-5413868106952254039cite
type="cite">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" <<A href="mailto:sebicann@bachollet.fr"
target=_blank>sebicann@bachollet.fr</A>> wrote:<BR>
<DL>
<DD>Hello Great exchange,<BR>
<DD>And very well done by .pr<BR><BR>
<DD>I am not sure that the first step is to jump into a PDP.<BR>
<DD>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.<BR>
<DD>Supporting cc and g to take actions for that purpose.<BR>
<DD>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).<BR>
<DD>It i very important to frame it as a global issue for users
(both individual, SME and NGO) what ever DN they are using.<BR>
<DD>We may wish to involve the RIR if such issue is a problem for
IP addresses or for any support.<BR>
<DD>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 ;)).<BR><BR>
<DD>Can we ask At-Large staff to open a wiki page to have this
exchange and start writing something on the issue?<BR><BR>
<DD>I will not be able to participate to the call organized by Ken
as I will be in a plane to Montreal.<BR><BR>
<DD>All the best<BR>
<DD>SeB<BR><BR>
<BLOCKQUOTE
class=m_3055778373556209487m_-4360846149451879971m_-5413868106952254039cite
type="cite">
<DD>Le 15 nov. 2017 Ã 07:59, Kan Kaili <<A
href="mailto:kankaili@gmail.com"
target=_blank>kankaili@gmail.com</A>> a écrit :<BR><BR>
<DD><FONT size=2>Hi, Alan and all,<BR></FONT>
<DD><BR>
<DD><FONT size=2>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. "<BR></FONT>
<DD><BR>
<DD><FONT size=2>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.<BR></FONT>
<DD><BR>
<DD><FONT size=2>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.<BR></FONT>
<DD><BR>
<DD><FONT size=2>Thus, if nobody else, I would like to take the
lead on this issue and try it out.<BR></FONT>
<DD><BR>
<DD><FONT size=2>Thank you!<BR></FONT>
<DD><BR>
<DD><FONT size=2>Kaili<BR></FONT>
<DD><BR>
<DD><BR>
<DD><BR>
<BLOCKQUOTE
class=m_3055778373556209487m_-4360846149451879971m_-5413868106952254039cite
type="cite">
<DD>----- Original Message -----<BR>
<DD>From: <A href="mailto:alan.greenberg@mcgill.ca"
target=_blank>Alan Greenberg</A><BR>
<DD>To: <A href="mailto:alac-internal@atlarge-lists.icann.org"
target=_blank>ALAC Internal List</A> ; <A
href="mailto:alac-internal@atlarge-lists.icann.org"
target=_blank>ALAC Internal List</A><BR>
<DD>Sent: Wednesday, November 15, 2017 3:58 AM<BR>
<DD>Subject: Re: [ALAC-Internal] Hurricane Maria Domain
Registration protection Protocol<BR><BR>
<DD>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.
<BR><BR>
<DD>Alan<BR><BR>
<DD>At 14/11/2017 01:47 PM, Seun Ojedeji wrote:<BR><BR>
<BLOCKQUOTE
class=m_3055778373556209487m_-4360846149451879971m_-5413868106952254039cite
type="cite">
<DD>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. <BR><BR>
<DD>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. <BR><BR>
<DD>Nevertheless perhaps it's worth a try.<BR><BR>
<DD>Regards<BR>
<DD>Sent from my mobile<BR>
<DD>Kindly excuse brevity and typos<BR><BR>
<DD>On Nov 14, 2017 7:09 PM, "Javier Rua" <<A
href="mailto:javrua@gmail.com"
target=_blank>javrua@gmail.com</A>> wrote:
<DL>
<DD>Dear ALAC,
<DD>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><BR>
<DD>Javier Rúa-Jovet<BR><BR>
<DD><A href="tel:+1%20787-396-6511"
target=_blank>+1-787-396-6511</A>
<DD>twitter: @javrua
<DD>skype: javier.rua1
<DD><A href="https://www.linkedin.com/in/javrua"
target=_blank>https://www.linkedin.com/in/ja<WBR>vrua</A>
<BR>
<DD>On Nov 14, 2017, at 1:23 PM, Pablo Rodriguez <<A
href="mailto:pablo@nic.pr"
target=_blank>pablo@nic.pr</A>> wrote:<BR><BR>
<BLOCKQUOTE
class=m_3055778373556209487m_-4360846149451879971m_-5413868106952254039cite
type="cite">
<DD>Dear Javier,
<DD>In 2011, Japan suferred two terrible disasters, an
9.0 earthquake followed by a Tsunami.
<DD>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.
<DD>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.
<DD>Hurricane MarÃÂa Domain Registration
protection Protocol
<DD>Puerto Rico Top Level Domain (.pr) has been 100%
operational pre-, during, and post hurricane Maria.
<DD>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.
<DD>Huracán MarÃÂa Protocolo de protección
de registros de dominios
<DD>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</DD></BLOCKQUOTE></DD></DL></DD></BLOCKQUOTE></DD></BLOCKQUOTE></DD></BLOCKQUOTE></DD></DL></BLOCKQUOTE>
<DD>______________________________<WBR>_________________
<DD>ALAC-Internal mailing list
<DD><A href="mailto:ALAC-Internal@atlarge-lists.icann.org"
target=_blank>ALAC-Internal@atlarge-lists.ic<WBR>ann.org</A>
<DD><A
href="https://atlarge-lists.icann.org/mailman/listinfo/alac-internal"
target=_blank>https://atlarge-lists.icann.or<WBR>g/mailman/listinfo/alac-intern<WBR>al</A>
<DD>ALAC Wiki: <A
href="https://community.icann.org/display/atlarge/At-Large+Advisory+Committee+(ALAC)"
target=_blank>https://community.icann.org/di<WBR>splay/atlarge/At-Large+Advisor<WBR>y+Committee+(ALAC)</A>
<DD>At-Large Website: <A href="http://atlarge.icann.org/"
target=_blank>http://atlarge.icann.org</A><BR><BR><BR>
<DD>Content-Type: text/plain; charset="us-ascii"<BR>
<DD>Content-Transfer-Encoding: 7bit<BR>
<DD>Content-Disposition: inline<BR>
<DD>X-Microsoft-Exchange-Diagnosti<WBR>cs:<BR>
<DD>
1;YQXPR0101MB1589;27:raBhEnfAM<WBR>JQK4wDOm1IlxWVVwpJp+Dg0C5wgVnr<WBR>S735mqr7nV2PJY5mpD8PCkL3jVCGhd<WBR>cabIpVgTSg8PzXBKr8W07FfOt/LOau<WBR>7AiM7k0B2uK67oGU/T3LPrIzm0RcQ<BR><BR>
<DD>______________________________<WBR>_________________<BR>
<DD>ALAC-Internal mailing list<BR>
<DD><A href="mailto:ALAC-Internal@atlarge-lists.icann.org"
target=_blank>ALAC-Internal@atlarge-lists.ic<WBR>ann.org</A><BR>
<DD><A
href="https://atlarge-lists.icann.org/mailman/listinfo/alac-internal"
target=_blank>https://atlarge-lists.icann.or<WBR>g/mailman/listinfo/alac-intern<WBR>al</A><BR><BR>
<DD>ALAC Wiki: <A
href="https://community.icann.org/display/atlarge/At-Large+Advisory+Committee+(ALAC"
target=_blank>https://community.icann.org/di<WBR>splay/atlarge/At-Large+Advisor<WBR>y+Committee+(ALAC</A>
)<BR><BR>
<DD>At-Large Website: <A href="http://atlarge.icann.org/"
target=_blank>http://atlarge.icann.org</A> </DD></DIV></BLOCKQUOTE><BR>
<HR>
<BR>
<DD>______________________________<WBR>_________________<BR>
<DD>ALAC-Internal mailing list<BR>
<DD><A href="mailto:ALAC-Internal@atlarge-lists.icann.org"
target=_blank>ALAC-Internal@atlarge-lists.ic<WBR>ann.org</A><BR>
<DD><A
href="https://atlarge-lists.icann.org/mailman/listinfo/alac-internal"
target=_blank>https://atlarge-lists.icann.or<WBR>g/mailman/listinfo/alac-intern<WBR>al</A><BR><BR>
<DD>ALAC Wiki: <A
href="https://community.icann.org/display/atlarge/At-Large+Advisory+Committee+(ALAC)"
target=_blank>https://community.icann.org/di<WBR>splay/atlarge/At-Large+Advisor<WBR>y+Committee+(ALAC)</A>
<BR><BR>
<DD>At-Large Website: <A href="http://atlarge.icann.org"
target=_blank>http://atlarge.icann.org</A>
<DD>______________________________<WBR>_________________<BR>
<DD>ALAC-Internal mailing list<BR>
<DD><A href="mailto:ALAC-Internal@atlarge-lists.icann.org"
target=_blank>ALAC-Internal@atlarge-lists.ic<WBR>ann.org</A><BR>
<DD><A
href="https://atlarge-lists.icann.org/mailman/listinfo/alac-internal"
target=_blank>https://atlarge-lists.icann.or<WBR>g/mailman/listinfo/alac-intern<WBR>al</A><BR><BR>
<DD>ALAC Wiki: <A
href="https://community.icann.org/display/atlarge/At-Large+Advisory+Committee+(ALAC)"
target=_blank>https://community.icann.org/di<WBR>splay/atlarge/At-Large+Advisor<WBR>y+Committee+(ALAC)</A>
<BR><BR>
<DD>At-Large Website: <A href="http://atlarge.icann.org/"
target=_blank>http://atlarge.icann.org</A> <BR><BR>
<DD>______________________________<WBR>_________________<BR>
<DD>ALAC-Internal mailing list<BR>
<DD><A href="mailto:ALAC-Internal@atlarge-lists.icann.org"
target=_blank>ALAC-Internal@atlarge-lists.ic<WBR>ann.org</A><BR>
<DD><A
href="https://atlarge-lists.icann.org/mailman/listinfo/alac-internal"
target=_blank>https://atlarge-lists.icann.or<WBR>g/mailman/listinfo/alac-intern<WBR>al</A><BR><BR>
<DD>ALAC Wiki: <A
href="https://community.icann.org/display/atlarge/At-Large+Advisory+Committee+(ALAC)"
target=_blank>https://community.icann.org/di<WBR>splay/atlarge/At-Large+Advisor<WBR>y+Committee+(ALAC)</A>
<BR><BR>
<DD>At-Large Website: <A href="http://atlarge.icann.org"
target=_blank>http://atlarge.icann.org</A><BR><BR>Content-Type:
text/plain; charset="us-ascii"<BR>Content-Transfer-Encoding:
7bit<BR>Content-Disposition:
inline<BR>X-Microsoft-Exchange-Diagnosti<WBR>cs:<BR><U></U> <U></U>
1;YQXPR0101MB1589;27:lyPeFsMR2<WBR>LTmaP9avmNEF6jqNJ598Y+br+SsHKk<WBR>IAjDu+lGgTNx7rt1tleHhx8p4RzNSv<WBR>OInojFp9kpA8rUgsNDq2reLZaNotHx<WBR>XgV/Y14faCFJ7u3u8T+umX+wQQtKZ<BR><BR>______________________________<WBR>_________________<BR>ALAC-Internal
mailing list<BR><A href="mailto:ALAC-Internal@atlarge-lists.icann.org"
target=_blank>ALAC-Internal@atlarge-lists.ic<WBR>ann.org</A><BR><A
href="https://atlarge-lists.icann.org/mailman/listinfo/alac-internal"
target=_blank>https://atlarge-lists.icann.or<WBR>g/mailman/listinfo/alac-intern<WBR>al</A><BR><BR>ALAC
Wiki: <A
href="https://community.icann.org/display/atlarge/At-Large+Advisory+Committee+(ALAC"
target=_blank>https://community.icann.org/di<WBR>splay/atlarge/At-Large+Advisor<WBR>y+Committee+(ALAC</A>
)<BR><BR>At-Large Website: <A href="http://atlarge.icann.org/"
target=_blank>http://atlarge.icann.org</A></DD></DIV><BR>______________________________<WBR>_________________<BR>ALAC-Internal
mailing list<BR><A href="mailto:ALAC-Internal@atlarge-lists.icann.org"
target=_blank>ALAC-Internal@atlarge-lists.ic<WBR>ann.org</A><BR><A
href="https://atlarge-lists.icann.org/mailman/listinfo/alac-internal"
rel=noreferrer
target=_blank>https://atlarge-lists.icann.or<WBR>g/mailman/listinfo/alac-intern<WBR>al</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/di<WBR>splay/atlarge/At-Large+Advisor<WBR>y+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></DIV></DIV></DIV><BR>______________________________<WBR>_________________<BR>ALAC-Internal
mailing list<BR><A href="mailto:ALAC-Internal@atlarge-lists.icann.org"
target=_blank>ALAC-Internal@atlarge-lists.ic<WBR>ann.org</A><BR><A
href="https://atlarge-lists.icann.org/mailman/listinfo/alac-internal"
rel=noreferrer
target=_blank>https://atlarge-lists.icann.or<WBR>g/mailman/listinfo/alac-intern<WBR>al</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/di<WBR>splay/atlarge/At-Large+Advisor<WBR>y+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><BR></DIV></DIV></BLOCKQUOTE>
<BLOCKQUOTE type="cite">
<DIV><SPAN>______________________________<WBR>_________________</SPAN><BR><SPAN>ALAC-Internal
mailing list</SPAN><BR><SPAN><A
href="mailto:ALAC-Internal@atlarge-lists.icann.org"
target=_blank>ALAC-Internal@atlarge-lists.<WBR>icann.org</A></SPAN><BR><SPAN><A
href="https://atlarge-lists.icann.org/mailman/listinfo/alac-internal"
target=_blank>https://atlarge-lists.icann.<WBR>org/mailman/listinfo/alac-<WBR>internal</A></SPAN><BR><SPAN></SPAN><BR><SPAN>ALAC
Wiki: <A
href="https://community.icann.org/display/atlarge/At-Large+Advisory+Committee+(ALAC)"
target=_blank>https://community.icann.org/<WBR>display/atlarge/At-Large+<WBR>Advisory+Committee+(ALAC)</A></SPAN><BR><SPAN></SPAN><BR><SPAN>At-Large
Website: <A href="http://atlarge.icann.org"
target=_blank>http://atlarge.icann.org</A></SPAN><BR></DIV></BLOCKQUOTE></DIV></DIV></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><BR></DIV>
<P>
<HR>
<P></P>_______________________________________________<BR>ALAC-Internal
mailing
list<BR>ALAC-Internal@atlarge-lists.icann.org<BR>https://atlarge-lists.icann.org/mailman/listinfo/alac-internal<BR><BR>ALAC
Wiki:
https://community.icann.org/display/atlarge/At-Large+Advisory+Committee+(ALAC)<BR><BR>At-Large
Website: http://atlarge.icann.org<BR></BLOCKQUOTE></BODY></HTML>