- UA-discuss - lists.iana.org

Recent www.uasg.tech publications
by Don Hollander Sept. 28, 2017

Sept. 28, 2017

We’ve published a number of items on the UASG website: 1) UASG016 - Review of Popular Browsers for UA Readiness - English <https://uasg.tech/wp-content/uploads/2017/09/UASG-Report-UASG016.pdf> 2) UASG017 - Review of Popular Websites for UA Readiness - English <https://uasg.tech/wp-content/uploads/2017/09/UASG-Report-UASG017.pdf> 3) Blogpost covering these two https://uasg.tech/2017/09/universal-acceptance-ua-key-reaching-next-billion… <https://uasg.tech/2017/09/universal-acceptance-ua-key-reaching-next-billion…> 4) UASG018 - Evaluation Criteria for Programming Languages English <https://uasg.tech/wp-content/uploads/2017/09/UASG018-Programming-Languages-…> The Appendices for all three of these have rich and interesting material. Don Don Hollander Universal Acceptance Steering Group Skype: don_hollander

2 1

What’s in a (Domain) Name? - October 19, 2017 from 14:00 to 15:00 - EASTERN Standard Time
by Don Hollander Sept. 26, 2017

Sept. 26, 2017

Dear all… IDC, one of the largest IT media companies in the world, will be hosting a Webinar on Broccoli Issues (Universal Acceptance, IPv6 and DNSSEC) It’s set for October 19, 2017 from 14:00 to 15:00 - EASTERN Standard Time (USA) - Washington DC Time Zone. You can register at the link below Here’s the link to the public registration site. http://council.cio.com/webinars/domain-name-ua/ <http://council.cio.com/webinars/domain-name-ua/> It will be recorded and we’ll share the details once their published. Don Don Hollander Universal Acceptance Steering Group Skype: don_hollander

1 0

More UA Coverage - this time in the June 2017 Issue of CSI Communications (India)
by Don Hollander Sept. 21, 2017

Sept. 21, 2017

Thanks Satish for making this happen. Don

3 2

UA Voices @ ICANN60 - EAI
by Don Hollander Sept. 21, 2017

Sept. 21, 2017

The UASG has secured a video ‘taping’ slot on 31 October @ 13:00 at the ICANN meeting in Abu Dhabi. We’re looking for 3-6 people to talk about EAI in 60-90 second bursts. We’ll put it together something akin to https://youtu.be/0VAwYpe24ZA which we did in India last year. Topics to include: Why EAI is important for you, your business or your community What you’re doing about EAI Why you’re doing something about EAI If you want to speak in a language other than English, can you please provide a translation that we can use for captioning (you can see that in the above video too) Short, passionate, clear. If you’re interested, please let me know off list. Thanks. Don

1 0

Regular Expression
by Don Hollander Sept. 15, 2017

Sept. 15, 2017

Please note that this is a Geeky post - so carry on if that’s not you. Email validation is an area where many websites fall short as we found in our study on Website UA Readiness (nearing publication) 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. 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. 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. /^.+@(?:[^.]+\.)+(?:[^.]{2,})$ 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. Your thoughts? Don Hollander Universal Acceptance Steering Group Skype: don_hollander

14 25

Re: [UA-discuss] Re : Re: Regular Expression
by Tex Sept. 14, 2017

Sept. 14, 2017

1 0

Re : Re: Regular Expression
by Dr. AJAY D A T A Sept. 14, 2017

Sept. 14, 2017

This is what Microsoft suggests for EAI Validation.https://blogs.msdn.microsoft.com/shawnste/2014/04/01/eai-email-a… Dr. Ajay DATA | Founder &amp CEO Get email id like अजय(a)xn--c2bd1gb.xn--h2brj9c in your own language,visit www.xgenplus.com From: Don Hollander MailId : [73397993]To: Mark Svancarek Cc: Universal Acceptance Subject: Re: [UA-discuss] Regular ExpressionDate: 13 Sep 2017 10:37:07 PM Mark.What would such a RegEx look like?D> On 14/09/2017, at 4:26 AM, Mark Svancarek via UA-discuss wrote:> > Depending on your mail client, you may have experienced a linkification error in my response. Weird. > > -----Original Message-----> From: Mark Svancarek > Sent: Wednesday, September 13, 2017 9:21 AM> To: `Vittorio Bertola` Chaals McCathie Nevile ua-discuss(a)icann.org> Subject: RE: [UA-discuss] Regular Expression> > I believe that validation should be as light as possible. "Contains `@` " is about the extent of it unless you are willing to look at bidi and IFS. Just capture the string and send a test message.> > -----Original Message-----> From: ua-discuss-bounces(a)icann.org [mailto:ua-discuss-bounces@icann.org] On Behalf Of Vittorio Bertola> Sent: Wednesday, September 13, 2017 1:34 AM> To: Chaals McCathie Nevile ua-discuss(a)icann.org> Subject: Re: [UA-discuss] Regular Expression> >> Il 13 settembre 2017 alle 0.01 Chaals McCathie Nevile ha scritto:>> >> >> On Tue, 12 Sep 2017 22:43:09 +0200, Don Hollander >> wrote:>> >> I think there is value in validation - first, to determine whether an >> email address is real - if it isn`t, you are probably better off >> getting a warning than trying to send it.> > But this is nothing you can do just with a regexp. The regexp could allow you to intercept blatant mistakes - e.g., there are national keyboards where typing "@" requires pressing Alt or some uncommon combination of keys, so it`s easy to mistype it and you can easily warn the user that their entered string does not have a "@" - but anything beyond that is unnecessary, because, if a user mistypes an email address in any other way, it`s very likely that he will still end up entering a valid email address that no regexp will be able to tell as non-existing, or that could even exist but belong to someone else.> > On the other hand, if you try to implement a complex regexp, and especially if you try to figure it out on your own, it`s almost certain that you will mark as invalid several valid email addresses that are corner cases but should be accepted, as well as many future developments of the standards which are invalid now but will be valid in the future.> >> Second, I find it very helpful, including as a protection against >> phishing emails, to be told if an email is not recognised as a contact >> to whom I have *sent* an email, which is a stricter validation check.>> Applications that do that for me - especially for scripts I don`t read >> fluently like Chinese - are common, and I would be upset if they were to stop validating.> > But this, again, is a validation that cannot be done via a regexp (can you write a regexp representing your entire contact book?) and that, on the other hand, poses an additional stricter condition than just "the email address is valid". We are just discussing how to check that the email address is syntactically valid, any other checks could still be implemented however appropriate.> > The point here is that you should not try to determine whether an email address is valid by checking its syntax, other than checking that it has a "@" and possibly a "." on the right of it (but even this latter condition is already too strict, as the ideographic full stop "。" should be accepted in place of the ASCII dot, if you check strings in IDN form). Anything beyond that is going to exclude some valid addresses while not increasing in any significant way your chances of intercepting user input error at this stage - and you will still intercept any user error a few seconds later, when you send the validation/confirmation message.> > Regards,> -- > > Vittorio Bertola | Research &amp Innovation Engineer vittorio.bertola(a)open-xchange.com Open-Xchange Srl - Office @ Via Treviso 12, 10144 Torino, ItalyDon HollanderUniversal Acceptance Steering GroupSkype: don_hollanderDo not Remove:[HID]20170913223703930[-HID]

4 4

Draft Programme for ICANN 60
by Don Hollander Sept. 14, 2017

Sept. 14, 2017

See this link https://docs.google.com/document/d/11Nwy50gMGPu14tGdrCJEzUXtBfMHgI6K7a1N6Ty… to the latest program for the UASG @ ICANN60. Please note we still don’t have dates. But we will organize lunch on the full-day workshop. Here’s a current state look: UASG @ ICANN60 Abu Dhabi UASG Workshop – Day 0 (TBC) DurationTopicLeader 115Introduction & WelcomeRam 230Review of the State of UASGDon 330Programming Language LibrariesA look at the approach and skillset necessary to pursue the issues. 460Industry Group Engagements: IETF, W3C, M3WAAG, ISOC, etc 560Communication StrategyLars/Christian 620Budget Review 740Local Initiatives UA in China UA in MENA Yaling TanAbdelmonim Galilla 840Evaluation Studies Websites Browsers Linkification EAI 960EAIYao/Mark 1030Documentation 11 UASG Administration 12 Other 13 Other 1420UA@ICANN IT UASG Public Forum – 90 minutes 115Introduction & WelcomeRam/Don 220CommunicationsLars/Christian 320EAIYao/Mark 420Evaluation StudiesDon 515Q&A Don

1 0

Recall: Regular Expression
by Mark Svancarek Sept. 13, 2017

Sept. 13, 2017

Mark Svancarek would like to recall the message, "[UA-discuss] Regular Expression".

1 0

Re: [UA-discuss] Regular Expression
by Tan Tanaka, Dennis Sept. 12, 2017

Sept. 12, 2017

David, good article. A couple of excerpts … “Just send them an email already No, I’m not joking. Just send your users an email. The activation email is a practice that’s been in use for years…” “If you really, really want to make sure people are typing in an actual email address, just use the /@/ regular expression and call it done. If that makes you nervous, then check for the dot too: /.+@.+\..+/i. Anything more is overkill.” -Dennis From: <ua-discuss-bounces(a)icann.org> on behalf of David Conrad <david.conrad(a)icann.org> Date: Tuesday, September 12, 2017 at 2:52 PM To: Don Hollander <don.hollander(a)icann.org> Cc: "UA-discuss(a)icann.org" <ua-discuss(a)icann.org> Subject: [EXTERNAL] Re: [UA-discuss] Regular Expression Don, Perhaps also pointing people at https://davidcel.is/posts/stop-validating-email-addresses-with-regex/? Regards, -drc On Sep 12, 2017, at 11:44 AM, Don Hollander <don.hollander(a)icann.org<mailto:don.hollander@icann.org>> wrote: Please note that this is a Geeky post - so carry on if that’s not you. Email validation is an area where many websites fall short as we found in our study on Website UA Readiness (nearing publication) 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. 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. 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. /^.+@(?:[^.]+\.)+(?:[^.]{2,})$ 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. Your thoughts? Don Hollander Universal Acceptance Steering Group Skype: don_hollander

1 0