Re: msg-id (was: Issues outstanding)

["Charles Lindsey" <chl@xxxxxxxxxxxxxxxx>]

In <41CA96C6.50F6@xxxxxxxxxxxxxxxxx> Frank Ellermann <nobody@xxxxxxxxxxxxxxxxx> writes:

>Frank Ellermann wrote (another error):

>  [Charles said:]
>>> adopt the RFC 2821 restriction (i.e. to an ipv4 or ipv6
>>> address).

>> a memo about news articles is not in the business
>> of defining address literals, that's the job of other texts,
>> and so far the results are a proper subset of [dot-atom-text]

>Nice argument, but completely wrong, ":" is not in atext, but
>RfC 3513 2.2 and other texts with address literals need it.
>We could get away with...

>| mdomain          = dot-atom-text / ("[" address-literal "]")
>| address-mliteral = 1*( atext / "." / ":" )    ; see RfC 2821

Yes, that is the only bit of RFC 2821 I had in mind to adopt. Indeed, Dan
Kohn's original draft (and the usefor-draft-01) had that, but it was taken
out because the WG had never agreed to that, and it was contrary to our
remit to stick with RFC 2822. But if our Chair is willing to allow it ...


>A simplified solution for the "must-quote" double-dots problem:

>| unique-quote = 1*( unique-part unique-lit unique-part )) /
>|                ("." unique-part) / (unique-part ".")
>| unique-part  = *([dot-atom-text] / [unique-lit])
>| unique-lit   = *(".") unique-text *(".")
>| unique-text  = "(" / ")" / "<" / ; all specials, minus ">",
>|                "[" / "]" / "@" / ; minus DQUOTE, minus "\",
>|                ":" / ";" / "," / ; and minus "." (dot), plus
>|                "\\" / ("\" DQUOTE) / ".."


But that looks exactly the same as my current <id-left>. Was there
supposed to be some difference?

-- 
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@xxxxxxxxxxxxxxxx      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