ietf-822
[Top] [All Lists]

Re: how to merge obs-id-{left,right} into a new msg-id on reply?

2001-09-10 02:34:22

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Monday 10 September 2001 02:44, Keith Moore wrote: 
Suppose I reply to a message whose Message-ID field has a left id 
that conforms to obs-left-id, but not left-id. How should I copy 
the msg-id then? Strip the non-comforming parts and risk to break 
older mailers' threading or copy everything from the "<" through to 
the ">" verbatim from the parent, risking to thus create a message 
in violation of rfc2822? 

I'd say the latter.  It's certainly incorrect to create a completely 
new message-id (correct or not) and say that you've replied to it. 
 
That wasn't my intention. It was more a question of whether to keep 
CFWS, which is allowed in the obs-msg-id, but not in (rfc2822-) msg-id 
anymore, or strip it. The semantic value of the message-id would not 
change. Consider e.g. 
 
Message-ID: <ABCFD@(domain-part) 
 kde.org> 
 
RFC2822 would disallow the creation of this. Now I could convert it to 
Message-ID: <ABCFD(_at_)kde(_dot_)org> 
or keep it exactly like I received it. The only problem I see with 
converting is breaking old mailers that do not tokenize headers 
according to rfc822 before interpreting them, but use the verbatim text 
(incl. comment and folding wsp) to compare msgid's. 
 
Say you were replying to a message that had a newly-invalid From 
address (valid under 822 and invalid under 2822). Would you create a 
new address as the destination of the reply? 
 
There are rfc822-from addresses that are invalid under 2822? Didn't know 
that yet... 
 
Marc 
 
- --  
The Commission and Member States are urged to devise appropriate 
measures to promote, develop and manufacture European encryption 
technology and software and above all to support projects aimed at 
developing user-friendly open-source encryption software. 
- -- EuroParl. Temp. Committee on the ECHELON Interception System 
   http://www.europarl.eu.int/tempcom/echelon/pdf/prechelon_en.pdf 
 
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: For info see http://www.gnupg.org

iD8DBQE7nN2z3oWD+L2/6DgRAjjvAKDZkH4t7dtKrIZ9ONZ8fqvsBds49QCfeSB8
TZ/6+doT3MnbImY13tJA4ew=
=NOsp
-----END PGP SIGNATURE-----
pè? A~pè?wA?pè?sA?pè?pA?pè?)A?