Received: from localhost by CS.UTK.EDU with SMTP (cf v2.9s-UTK) id IAA03179; Wed, 6 Dec 1995 08:34:04 -0500 Received: by cs.cs.utk.edu (bulk_mailer v1.3); Wed, 6 Dec 1995 08:33:14 -0500 Received: from ester.dsv.su.se by CS.UTK.EDU with ESMTP (cf v2.9s-UTK) id IAA03141; Wed, 6 Dec 1995 08:33:13 -0500 Received: (from jpalme@localhost) by ester.dsv.su.se (8.7.1/8.7.1) id OAA29285; Wed, 6 Dec 1995 14:33:09 +0100 (MET) Date: Wed, 6 Dec 1995 14:33:07 +0100 (MET) From: Jacob Palme To: ietf-drums Subject: Clarify amibuities Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sorry if I go back to the old issue of reply-to again. The reason I do it is that Keith said at the drums meeting at IETF yesterday, that one of the major goals of the drums group is to remove ambiguities in the e-mail standards. I guess everyone agrees after the discussion we have had, that reply-to is ambiguous. And to resolve this by just saying that "reply-to gives the e-mail address to which the sender wants replies to be sent" does *not* remove that ambiguity. If we really want to perform what we are meant to do, i.e. to remove ambiguities, then we will have to (1) Either select one of the ambiguous uses as the only permitted. This is obviously impossible to get consensus on. (2) Deprecate the whole header. (3) Replace the command with two or more new headers, one for each of the ambiguous meanings. The worst thing I know about standards is vague statements and ambiguous statements, especially if these have been put into the standard in order to reach conensus on controversial issues. But that is exactly what we will do if we keep the ambiguity. ------------------------------------------------------------------------ Jacob Palme (Stockholm University and KTH) for more info see URL: http://www.dsv.su.se/~jpalme