vint at google.com
Mon Apr 13 02:09:30 CEST 2009
Most States in the US have a similar restriction. I remember trying to
generate pronounceable passwords, 8 chars long, using alternating consonants
and vowels. To see how this might work out in practice, I generated about
500,000 samples and was immediately surprised to find that "DEFECATE" fit
this formula perfectly. I am sure you can think of others. Imagine now
trying to find a way to automatically avoid sending to a new user his or her
automatically generated, pronouceable password without accidently sending
something really offensive. :-)
On Sun, Apr 12, 2009 at 6:38 PM, John C Klensin <klensin at jck.com> wrote:
> --On Monday, April 13, 2009 00:02 +0200 Jaap Akkerhuis
> <jaap at NLnetLabs.nl> wrote:
> > The next message "Saudis ban 'lewd' license plates"
> > http://news.bbc.co.uk/2/hi/middle_east/7995865.stm
> > made me giggle. Of course, IDNA will have to deal
> > with this problem as well :-).
> IDNA, as a protocol, does not. It is going to be a lot of fun
> for registries and those who regulate them, especially given the
> number of words that people can find offensive, especially when
> one script is transliterated into another.
> In particular, I think we should extend our best wishes to ICANN
> Idna-update mailing list
> Idna-update at alvestrand.no
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Idna-update