Received: from localhost by CS.UTK.EDU with SMTP (cf v2.9s-UTK) id OAA19638; Sat, 16 Sep 1995 14:50:10 -0400 X-Resent-To: drums@CS.UTK.EDU ; Sat, 16 Sep 1995 14:50:03 EDT Errors-to: owner-drums@CS.UTK.EDU Received: from munnari.oz.au by CS.UTK.EDU with SMTP (cf v2.9s-UTK) id OAA19603; Sat, 16 Sep 1995 14:49:59 -0400 Received: from mundamutti.cs.mu.OZ.AU by munnari.oz.au with SMTP (5.83--+1.3.1+0.50) id AA05772; Sun, 17 Sep 1995 04:49:42 +1000 (from kre@munnari.OZ.AU) To: Jacob Palme Cc: ietf-drums Subject: Re: Another header-munging example In-Reply-To: Your message of "Fri, 15 Sep 1995 17:38:03 +0200." Date: Sun, 17 Sep 1995 04:49:11 +1000 Message-Id: <17714.811277351@munnari.OZ.AU> From: Robert Elz Date: Fri, 15 Sep 1995 17:38:03 +0200 (MET DST) From: Jacob Palme Message-ID: (1) The "Reply-To" controversy is not about adding new functionality. The different interpretations of "Reply-To" are both in wide usage today. Yes. This is the problem. (2) There is no possible way of "clarifying the language", since there are different incompatible uses in wide usage. Unless your "clarification" is some obscure statement which allows both alternatives, but that is excatly what one should *not* do when making standards. No, clarifying the language means picking one of the uses to be blessed, and deprecating the other. That is, removing the ambiguity. (3) This is not only about mailing lists. It relates to all messages which have more than one recipient. Absolutely, I wish we could simply forget about mailing lists when discussing this topic, they are not relevant at all. Even better, let's just refer back to Keith's "from the chair" message of a couple of days ago, and leave it like that, that is, now simply stop discussing this issue any more, at all. kre