John L

Hm, you're right. Let me see if I can pin it down further.

If we're going to resume making changes to the v3 grammar before the RSWG weighs in, I have a quite a few I'd like to add.

Per my note to the mailing list, how about thinking about XML to describe IANA registries and entries so we can automate 90% of the update process rather than 2%?

It's more complex than that, and it's not about ß which is an odd special case. EAI (internationalized) mail can handle addresses like пример@Бориса.РФ. While the domain part can turn...

s/reject/accept/ and I agree

> https://html.spec.whatwg.org/multipage/input.html#e-mail-state-(type=email) defines > he value attribute, if specified and not empty, must have a value that is a single valid e-mail address. > > The value sanitization algorithm is...

It certainly has to be valid Unicode (e.g., no unpaired UTF-16 surrogates, no invalid UTF-8 bytes), and follow the rules like no unpaired quotes. Restricting it more than that is...

Mailbox names are pretty much arbitrary UTF-8. It doesn't have to be normalized, for that matter, it can be a sequence of ZWJ and Arabic combining marks. While I agree...

the RHS has to be a hostname, which limits the characters to the ones valid in U-labels

xml2rfc v2 used PIs but v3 does not. They've been replaced by attributes of the `` element