Brian: I have not had the opportunity to contribute as much as I would like due to very active work in another WG but definitely +1 for strawman and will try to submit comments/markup soon on the provisions you have circulated. Thanks. Best regards, Scott [cid:image001.png@01D30C89.C99DC810][IntellectualPropertyLaw 100] [microbadge[1]] <http://www.avvo.com/attorneys/33308-fl-scott-austin-1261914.html> Scott R. Austin | Board Certified Intellectual Property Attorney | VLP Law Group LLP 101 NE Third Avenue, Suite 1500, Fort Lauderdale, FL 33301 Phone: (954) 204-3744 | Fax: (954) 320-0233 | SAustin@VLPLawGroup.com<mailto:SAustin@VLPLawGroup.com> From: translationtransliterationirt-bounces@icann.org [mailto:translationtransliterationirt-bounces@icann.org] On Behalf Of Brian Aitchison Sent: Friday, July 28, 2017 1:15 PM To: translationtransliterationirt@icann.org Subject: [Translationtransliterationirt] Ways Forward for T/T Dear T/T IRT, Thank you for your patience as we work on our end to consolidate and analyze the input we’ve received from you over the course of this implementation. We’ve come to the conclusion that we have two paths available to us, which we’d like your input on: 1. Draft a strawman policy document based on all the input we’ve gathered so far, recognizing that all the aims and intents of the original T/T recommendations may not be fulfilled given the vagueness of some of the language within the Recommendations, and the technical obstacles inherent to implementing them. This option may still take us back to the GNSO for input, but will give us something tangible to circulate within our group and with relevant stakeholders for input and critique before pursuing the GNSO path. 2. Continue discussion on the meaning of “easy identification” in the context of the T/T recommendations, as well as guidelines for identifying languages. This option will likely lead us to the GNSO for input quite quickly given the difficulties we’ve had answering questions on the meaning of “easy identification”, language identification, and how to collect and validate language data. We’re gravitating toward option 1 as it would give us a tangible work product to show from our efforts, as well as provide a basis for further work and improvements. Of course, we’re open to your suggestions on these or other potential paths. Please let us know what you think by the end of next week. As always, thank you for your valuable contributions to this effort. Best, Brian -- Brian Aitchison, MRes, PhD Lead Researcher Operations & Policy Research Internet Corporation for Assigned Names and Numbers (ICANN) 12025 Waterfront Drive, Suite 300 Los Angeles, CA 90094 Office: +1 310 578 8688 Mobile: +1 424 353 9041 brian.aitchison@icann.org<mailto:eleeza.agopian@icann.org> CONFIDENTIALITY NOTICE: This email and any attachments are for the sole use of the intended recipient(s) and contain information that may be confidential and/or legally privileged. If you have received this email in error, please notify the sender by reply email and delete the message. Any disclosure, copying, distribution or use of this communication by someone other than the intended recipient is prohibited. This message contains information which may be confidential and legally privileged. Unless you are the addressee, you may not use, copy or disclose to anyone this message or any information contained in the message. If you have received this message in error, please send me an email and delete this message. Any tax advice provided by VLP is for your use only and cannot be used to avoid tax penalties or for promotional or marketing purposes.
