Received: from localhost (daemon@localhost) by CS.UTK.EDU with SMTP (cf v2.9s-UTK) id TAA26222; Thu, 6 Nov 1997 19:34:28 -0500 (EST) Received: by CS.UTK.EDU (bulk_mailer v1.7); Thu, 6 Nov 1997 19:31:07 -0500 Received: by CS.UTK.EDU (cf v2.9s-UTK) id TAA26132; Thu, 6 Nov 1997 19:31:06 -0500 (EST) Received: from THOR.INNOSOFT.COM (THOR.INNOSOFT.COM [192.160.253.66]) by CS.UTK.EDU with ESMTP (cf v2.9s-UTK) id TAA26119; Thu, 6 Nov 1997 19:30:55 -0500 (EST) Received: from eleanor.innosoft.com ("port 52676"@ELEANOR.INNOSOFT.COM) by INNOSOFT.COM (PMDF V5.1-10 #8694) with SMTP id <01IPP2EP6H429JEYIU@INNOSOFT.COM> for drums@cs.utk.edu; Thu, 6 Nov 1997 16:29:45 PST Date: Thu, 06 Nov 1997 16:31:56 -0800 (PST) From: Chris Newman Subject: Re: Proposed charter update In-reply-to: <3.0.32.19971106110345.00883880@pop.dial.pipex.com> To: Graham Klyne Cc: Detailed Revision/Update of Message Standards Message-id: MIME-version: 1.0 Content-type: TEXT/PLAIN; charset=US-ASCII Originator-Info: login-id=chris; server=thor.innosoft.com On Thu, 6 Nov 1997, Graham Klyne wrote: > I understand the "reply-to" debate has rumbled on and on rather (guilty as > charged, m'lud) but I am not convinced that bringing new reply headers into > scope is going to help get it resolved ay sooner. It is already explicitly within our charter to "fix" reply-to and I believe we have concensus that it needs corrections/clarifications. However, any clarification to reply-to which disambiguates the current situation will likely outlaw certain functions for which reply-to is currently used. Therefore I don't believe we can effectively evaluate proposed corrections/clarifications to reply-to unless we also consider the new features necessary to replace uses which are outlawed. I'll give an example of such a proposal in a separate message. Do you still object to the proposed charter update? - Chris