Thanks for this, George. All - this proposed implementation relates only to the GNSO policy recommendations that have been approved to date by the ICANN Board and does not concern the remaining ones that are inconsistent with GAC advice. For IGOs this means the implementation is limited only to the full names on the GAC list that are to be reserved, and not to IGO acronyms. Petter is a member of the implementation team so he may have more to add. Cheers Mary Sent from a mobile phone, sorry for any errors and brevity. On May 18, 2017, at 13:44, George Kirikos <icann@leap.com<mailto:icann@leap.com>> wrote: FYI, ICANN published this last night: https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_public-2D... and conceivably it might impact our work to some degree. More comments later, once I've had time to analyze it fully. Sincerely, George Kirikos 416-588-0269 https://urldefense.proofpoint.com/v2/url?u=http-3A__www.leap.com_&d=DwICAg&c... _______________________________________________ Gnso-igo-ingo-crp mailing list Gnso-igo-ingo-crp@icann.org<mailto:Gnso-igo-ingo-crp@icann.org> https://mm.icann.org/mailman/listinfo/gnso-igo-ingo-crp