<html><head><meta http-equiv="Content-Type" content="text/html charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><br class=""><div><blockquote type="cite" class=""><div class="">On Sep 12, 2017, at 3:44 PM, Don Hollander <<a href="mailto:don.hollander@icann.org" class="">don.hollander@icann.org</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><meta http-equiv="Content-Type" content="text/html charset=utf-8" class=""><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">Please note that this is a Geeky post - so carry on if that’s not you.<div class=""><br class=""></div><div class=""><br class=""></div><div class="">Email validation is an area where many websites fall short as we found in our study on Website UA Readiness (nearing publication)</div><div class=""><br class=""></div><div class="">The technologies behind these websites generally use a Regular Expression as their first line of defence against rubbish data. The issue is that most of these RegExs are overly restrictive.</div><div class=""><br class=""></div><div class="">As an appendix to the Website review, we looked at some of the technologies behind the websites to see if there were common denominators for good and bad experiences.</div><div class=""><br class=""></div><div class="">One RegEx has stood out as being simple and correct. I’d like the UASG to consider recommending this in our documentation. Toward that end, this thread is for discussion.</div><div class=""><br class=""></div><div class=""><div style="text-align: center; margin: 0px; line-height: normal; font-family: 'Helvetica Neue'; color: rgb(69, 69, 69);" class="">/^.+@(?:[^.]+\.)+(?:[^.]{2,})$</div><div style="margin: 0px; line-height: normal; font-family: 'Helvetica Neue'; color: rgb(69, 69, 69);" class=""><br class=""></div><div style="margin: 0px; line-height: normal; font-family: 'Helvetica Neue'; color: rgb(69, 69, 69);" class=""><br class=""></div><div style="margin: 0px; line-height: normal; font-family: 'Helvetica Neue'; color: rgb(69, 69, 69);" class="">Regular expression check in Javascript. This accepts any Unicode characters, only insisting that the domain must have more than one label and the TLD is 2 characters or longer. </div><div style="margin: 0px; line-height: normal; font-family: 'Helvetica Neue'; color: rgb(69, 69, 69);" class=""><br class=""></div><div style="margin: 0px; line-height: normal; font-family: 'Helvetica Neue'; color: rgb(69, 69, 69);" class="">Your thoughts?</div></div></div></div></blockquote><br class=""></div><div>Single IDN TLDs for some scripts is something being considered for subsequent procedures, so I would think of 1 or more and prevent the same UA challenges previous rounds TLDs are suffering. </div><div><br class=""></div><div><br class=""></div><div>Rubens</div><div><br class=""></div><br class=""></body></html>