In <p0630000ec26532b2d53d(_at_)[75(_dot_)204(_dot_)224(_dot_)24]> Pete Resnick
<presnick(_at_)qualcomm(_dot_)com> writes:
- Define the left hand side of the "@" in msg-id to be (dot-atom-text
/ ob-id-left)
- Leave the right hand side of msg-id as it is (dot-atom-text /
no-fold-literal / obs-id-right)
- Leave the text to normatively RECOMMEND (or should it be REQUIRE?)
that the right hand side be a domain identifier (either domain name
or domain literal)
I'd prefer to leave the ABNF of domain-literal the way it is and
limit in the text.
I'm not too happy with that. The only things that need removing are
redundant <quoted-pair>s (e.g "\a") and maybe NO-WS-CTLs. That is nothing
like the mess of trying to fix <no-fold-quote>s in ABNF, and in fact the
syntax in the USEFOR draft is all that you would need:
no-fold-literal = "[" *( mdtext / "\[" / "\]" / "\\" ) "]"
mdtext = %d33-61 / ; The rest of the US-ASCII
%d63-90 / ; characters not including
%d94-126 ; ">", "[", "]", or "\"
OK, you would need to add an obs- bit to that.
I'd also be inclined to *not* talk about case-sensitivity and
comparisons since nowhere is it discussed in 2822.
OK. You seem to have allowed <local-part>s to be case sensitive without
actually saying so, so the same would apply to <msg-id>s. The only slight
worry is that people might still try to argue that the stuff after the "@"
is a domain-name, and therefore case-insenitive. Yes, that argument is
wrong as RFC 2822 is written, but not so obviously wrong that people are
not going to try it. Perhaps some remark (not normative) that <mesg-id>s
have been so designed that equality between them is simply a matter of
octet-by-octet comparison.
--
Charles H. Lindsey ---------At Home, doing my own thing------------------------
Tel: +44 161 436 6131 Fax: +44 161 436 6133 Web: http://www.cs.man.ac.uk/~chl
Email: chl(_at_)clerew(_dot_)man(_dot_)ac(_dot_)uk Snail: 5 Clerewood Ave,
CHEADLE, SK8 3JU, U.K.
PGP: 2C15F1A9 Fingerprint: 73 6D C2 51 93 A0 01 E7 65 E8 64 7E 14 A4 AB A5