Hi, 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. 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: - ISC's academic people will go to the media and have it heard. - In response, a few ISC's industry members will respond with a voluntary solution. - ISC's scholars will compare different solutions and present a preferred one to ISC. - 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. - 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.) - The ministry (MIIT) closely observes the whole process, provides support, and makes the solution into regulation when it is widely followed. 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. As I see it, ccNSO is likely to first adopt to this "distress relief" measure, while GNSO will then have to follow. Thank you! Kaili ----- Original Message ----- From: Maureen Hilyard To: ALAC Internal List Sent: Friday, November 17, 2017 12:30 AM Subject: Re: [ALAC-Internal] Hurricane Maria Domain Registration protectionProtocol Hi everyone 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. 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" Katrina, in conjunction with Alejandra who is their Meeting Programme Coordinator, have suggested: - We organise a discussion at ccNSO Members meeting on Tuesday or Wednesday - “How to help ccTLDs, registrars and registrants in case of severely damaged infrastructure?” (or a similar title) - 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 - 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 - We will invite ROs. They are the driving force and the ones who can help the most. For example, during the LACTLD Technical workshop they try to establish redundancy among fellow ccTLDs, especially for small registries. - Discussions 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. Comments? On Wed, Nov 15, 2017 at 8:24 PM, Javier Rua <javrua@gmail.com> wrote: Don’t leave out gTLDs ! Javier Rúa-Jovet +1-787-396-6511 twitter: @javrua skype: javier.rua1 https://www.linkedin.com/in/javrua On Nov 16, 2017, at 2:19 AM, Maureen Hilyard <maureen.hilyard@gmail.com> wrote: I agree Seun 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. Ill get back to the team when she responds. Maureen On Wed, Nov 15, 2017 at 7:53 PM, Seun Ojedeji <seun.ojedeji@gmail.com> wrote: Hello Alan, 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. 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. Reese's Sent from my mobile Kindly excuse brevity and typos On Nov 15, 2017 8:46 PM, "Alan Greenberg" <alan.greenberg@mcgill.ca> wrote: Seun, what kind of advice are you thinking of? Advice should be actionable. 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. 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 - https://www.icann.org/resources/pages/governance/bylaws-en/#annexA. The Request for an Issue Report and the processes which should precede it are laid out in the GNSO PDP Manual ( https://gnso.icann.org/en/council/annex-2-pdp-manual-01sep16-en.pdf ). It is a long process, and includes all sorts of checks and balances. Alan At 15/11/2017 01:37 PM, Seun Ojedeji wrote: I like the idea of going the advice route for a start using the .PR as a case study. We may then include in the advice a recommendation for a PDP if necessary. Regards Sent from my mobile Kindly excuse brevity and typos On Nov 15, 2017 9:41 AM, "Sebicann Bachollet" <sebicann@bachollet.fr> wrote: Hello Great exchange, And very well done by .pr I am not sure that the first step is to jump into a PDP. 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. Supporting cc and g to take actions for that purpose. 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). It i very important to frame it as a global issue for users (both individual, SME and NGO) what ever DN they are using. We may wish to involve the RIR if such issue is a problem for IP addresses or for any support. 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 ;)). Can we ask At-Large staff to open a wiki page to have this exchange and start writing something on the issue? I will not be able to participate to the call organized by Ken as I will be in a plane to Montreal. All the best SeB Le 15 nov. 2017 à 07:59, Kan Kaili <kankaili@gmail.com> a écrit : Hi, Alan and all, 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. " 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. 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. Thus, if nobody else, I would like to take the lead on this issue and try it out. Thank you! Kaili ----- Original Message ----- From: Alan Greenberg To: ALAC Internal List ; ALAC Internal List Sent: Wednesday, November 15, 2017 3:58 AM Subject: Re: [ALAC-Internal] Hurricane Maria Domain Registration protection Protocol 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. Alan At 14/11/2017 01:47 PM, Seun Ojedeji wrote: 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. 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. Nevertheless perhaps it's worth a try. Regards Sent from my mobile Kindly excuse brevity and typos On Nov 14, 2017 7:09 PM, "Javier Rua" <javrua@gmail.com> wrote: Dear ALAC, 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. Javier Rúa-Jovet +1-787-396-6511 twitter: @javrua skype: javier.rua1 https://www.linkedin.com/in/javrua On Nov 14, 2017, at 1:23 PM, Pablo Rodriguez <pablo@nic.pr> wrote: Dear Javier, In 2011, Japan suferred two terrible disasters, an 9.0 earthquake followed by a Tsunami. 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. 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. Hurricane MarÃÂa Domain Registration protection Protocol Puerto Rico Top Level Domain (.pr) has been 100% operational pre-, during, and post hurricane Maria. 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. Huracán MarÃÂa Protocolo de protección de registros de dominios 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 _______________________________________________ ALAC-Internal mailing list ALAC-Internal@atlarge-lists.icann.org https://atlarge-lists.icann.org/mailman/listinfo/alac-internal ALAC Wiki: https://community.icann.org/display/atlarge/At-Large+Advisory+Committee+(ALA...) At-Large Website: http://atlarge.icann.org Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Content-Disposition: inline X-Microsoft-Exchange-Diagnostics: 1;YQXPR0101MB1589;27:raBhEnfAMJQK4wDOm1IlxWVVwpJp+Dg0C5wgVnrS735mqr7nV2PJY5mpD8PCkL3jVCGhdcabIpVgTSg8PzXBKr8W07FfOt/LOau7AiM7k0B2uK67oGU/T3LPrIzm0RcQ _______________________________________________ ALAC-Internal mailing list ALAC-Internal@atlarge-lists.icann.org https://atlarge-lists.icann.org/mailman/listinfo/alac-internal ALAC Wiki: https://community.icann.org/display/atlarge/At-Large+Advisory+Committee+(ALA... ) At-Large Website: http://atlarge.icann.org ------------------------------------------------------------------------ _______________________________________________ ALAC-Internal mailing list ALAC-Internal@atlarge-lists.icann.org https://atlarge-lists.icann.org/mailman/listinfo/alac-internal ALAC Wiki: https://community.icann.org/display/atlarge/At-Large+Advisory+Committee+(ALA...) At-Large Website: http://atlarge.icann.org _______________________________________________ ALAC-Internal mailing list ALAC-Internal@atlarge-lists.icann.org https://atlarge-lists.icann.org/mailman/listinfo/alac-internal ALAC Wiki: https://community.icann.org/display/atlarge/At-Large+Advisory+Committee+(ALA...) At-Large Website: http://atlarge.icann.org _______________________________________________ ALAC-Internal mailing list ALAC-Internal@atlarge-lists.icann.org https://atlarge-lists.icann.org/mailman/listinfo/alac-internal ALAC Wiki: https://community.icann.org/display/atlarge/At-Large+Advisory+Committee+(ALA...) At-Large Website: http://atlarge.icann.org Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Content-Disposition: inline X-Microsoft-Exchange-Diagnostics: 1;YQXPR0101MB1589;27:lyPeFsMR2LTmaP9avmNEF6jqNJ598Y+br+SsHKkIAjDu+lGgTNx7rt1tleHhx8p4RzNSvOInojFp9kpA8rUgsNDq2reLZaNotHxXgV/Y14faCFJ7u3u8T+umX+wQQtKZ _______________________________________________ ALAC-Internal mailing list ALAC-Internal@atlarge-lists.icann.org https://atlarge-lists.icann.org/mailman/listinfo/alac-internal ALAC Wiki: https://community.icann.org/display/atlarge/At-Large+Advisory+Committee+(ALA... ) At-Large Website: http://atlarge.icann.org _______________________________________________ ALAC-Internal mailing list ALAC-Internal@atlarge-lists.icann.org https://atlarge-lists.icann.org/mailman/listinfo/alac-internal ALAC Wiki: https://community.icann.org/display/atlarge/At-Large+Advisory+Committee+(ALA...) At-Large Website: http://atlarge.icann.org _______________________________________________ ALAC-Internal mailing list ALAC-Internal@atlarge-lists.icann.org https://atlarge-lists.icann.org/mailman/listinfo/alac-internal ALAC Wiki: https://community.icann.org/display/atlarge/At-Large+Advisory+Committee+(ALA...) At-Large Website: http://atlarge.icann.org _______________________________________________ ALAC-Internal mailing list ALAC-Internal@atlarge-lists.icann.org https://atlarge-lists.icann.org/mailman/listinfo/alac-internal ALAC Wiki: https://community.icann.org/display/atlarge/At-Large+Advisory+Committee+(ALA...) At-Large Website: http://atlarge.icann.org _______________________________________________ ALAC-Internal mailing list ALAC-Internal@atlarge-lists.icann.org https://atlarge-lists.icann.org/mailman/listinfo/alac-internal ALAC Wiki: https://community.icann.org/display/atlarge/At-Large+Advisory+Committee+(ALA...) At-Large Website: http://atlarge.icann.org ------------------------------------------------------------------------------ _______________________________________________ ALAC-Internal mailing list ALAC-Internal@atlarge-lists.icann.org https://atlarge-lists.icann.org/mailman/listinfo/alac-internal ALAC Wiki: https://community.icann.org/display/atlarge/At-Large+Advisory+Committee+(ALA...) At-Large Website: http://atlarge.icann.org