Re: [I18ndir] HTML, email addresses, etc

[Nico Williams <[e-mail]>]

On Mon, Jun 08, 2020 at 07:51:43AM -0400, Marc Blanchet wrote:
> On 7 Jun 2020, at 23:46, John C Klensin wrote:
> > (2) We could actually modify those specs to prohibit, or
> > strongly recommend against, allocating email addresses whose
> > local-parts contain anything but Unicode code points associated
> > with graphics, or even letters, digits, and a small selection of
> > symbols (possibly bringing the local-part recommendations close
> > to a PRECIS profile).
> 
> this is what I was going to say. IMHO, any protocol identifier (such as EAI)
> using something more than ASCII must define a PRECIS profile. This is the
> only chance to get it working. plain UTF8 for an identifier is just plain
> wrong.

I'm inclined to be as permissive as possible.

Ever play video games or used social media?  Have you noticed that many
people have usernames with -gasp- whitespace in them?  SASL wanted to
prohibit that -- a recipe for those applications not using SASL[*], a
recipe for failure.

Let's be permissive.  I'm OK with disallowing non-ASCII punctuation,
quotation marks, and misc things like non-breaking spaces (which should
be squeezed out) and so on, but I don't think we should try too hard to
make lists of banned characters.

Nico

[*] Well, OK, they don't and weren't going to use SASL, most likely.
    But the point stands.  These are policies that should be
    site-specific, not Internet-wide.