Received: from localhost by CS.UTK.EDU with SMTP (cf v2.9s-UTK) id NAA10751; Tue, 29 Aug 1995 13:36:16 -0400 X-Resent-To: drums@CS.UTK.EDU ; Tue, 29 Aug 1995 13:36:12 EDT Errors-to: owner-drums@CS.UTK.EDU Received: from info.cren.net by CS.UTK.EDU with ESMTP (cf v2.9s-UTK) id NAA10743; Tue, 29 Aug 1995 13:36:10 -0400 Received: from [192.52.179.12] (conklin-180c.cren.net [192.52.179.12]) by info.cren.net (8.6.12/8.6.4 (CREN)) with SMTP id NAA00716; Tue, 29 Aug 1995 13:35:32 -0400 Message-Id: <199508291735.NAA00716@info.cren.net> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Tue, 29 Aug 1995 13:38:36 +0100 To: Jacob Palme , ietf-drums From: conklin@info.cren.net (Jim Conklin) Subject: Re: From the Chair: the Reply-To issue I think that Jacob's suggestion may be a workable compromise, since it leaves the present situation usable but builds toward a long-term solution that would be desirable. It also encompases the idea behind the "Wide-Reply-To" header. Jim At 4:48 PM 8/28/95 +0200, Jacob Palme wrote: >Invent two new header-fields "Personal-Reply-To" and "Group-Reply-To". >Say that the old field "Reply-To" is kept but that its use is >depreciated in favor of the two new fields. If a message has >both the old and one or both of the new fields, the old field >should be disregarded. > >After 5 or 10 years, when all implementors have changed to the >new implementation, the old ambiguous "Reply-To" can be eliminated.