Excellent ideas - If I could build upon them, some more robust variance in unicode.unicode with respect to working with varied scripts (especially RTL.LTR / LTR.RTL combinations - though fringe, might help counter potential homograph email forgery) as the inter-operability of these is going to be important.


Jothan Frakes
Tel: +1.206-355-0230


On Fri, Oct 2, 2015 at 1:54 PM, Brent London <brentlondon@google.com> wrote:

Domain Test is a tool that we made to help with this. It's accessible at http://domaintest.foo and on ~120 other TLDs (including some IDNs).

It's similar to what you propose, except that it by design can only work with valid domain names. (For obvious reasons, we can't have an invalid TLD point to a hosted test suite.)

Check out the documentation link from the page above to learn how it works and what domains are compatible with it.

Brent //mobile

On Oct 2, 2015 12:36 AM, "Don Hollander" <don.hollander@icann.org> wrote:
Dear all:

One of the tasks that’s being consider is the create of a Test Suite of domain names and e-mail addresses that can be used to test an application for it’s UA readiness.

This might include:

1.     Ascii.com

2.     Invalid TLD

3.     Ascii.nTLD

4.     Ascii.punycode

5.     Ascii.unicode

6.     Unicode.unicode

7.     Long TLD

8.     Five Character TLD

9.     Nascent TLD



Some people may be happy to register their own domain name for each of the categories - but not everyone might.  Particularly for the Unicode.unicode.

I’m wondering if people have any ideas of how we might be able to create a public resource that people can use to test their systems if they don’t want to secure their own domain names?    One thought had been to set up a mailing list that is publicly visible and people can access that to see if their welcome message appears.   

I would very much welcome those of you with a Geeky bent to let me know (on or off list) of any ideas the you think might work.

Thanks.

Don