Received: from localhost by CS.UTK.EDU with SMTP (cf v2.9s-UTK)
	id OAA07080; Mon, 11 Sep 1995 14:27:14 -0400
X-Resent-To: drums@CS.UTK.EDU ; Mon, 11 Sep 1995 14:27:12 EDT
Errors-to: owner-drums@CS.UTK.EDU
Received: from wilma.cs.utk.edu by CS.UTK.EDU with ESMTP (cf v2.9s-UTK)
	id OAA07072; Mon, 11 Sep 1995 14:27:11 -0400
Received: from localhost by wilma.cs.utk.edu with SMTP (cf v2.11c-UTK)
          id OAA13208; Mon, 11 Sep 1995 14:27:09 -0400
Message-Id: <199509111827.OAA13208@wilma.cs.utk.edu>
X-URI: http://www.cs.utk.edu/~moore/
From: Keith Moore <moore@CS.UTK.EDU>
To: Olle Jarnefors <ojarnef@admin.kth.se>
cc: drums@CS.UTK.EDU, moore@CS.UTK.EDU
Subject: Re: Another header-munging example..... 
In-reply-to: Your message of "Mon, 11 Sep 1995 19:51:41 +0200."
             <9509111751.AA26353@mercutio.admin.kth.se> 
Date: Mon, 11 Sep 1995 14:27:03 -0400
Sender: moore@CS.UTK.EDU

(from the chair)

Briefly: extensions to 822 to better support mailing lists are not 
in our charter.  At most, we can "fix" the existing support in 822 
that appears to be broken (like Resent-*).

While there is probably general agreement that mailing lists don't work
as well as they might, there's a wide disagreement about the best way
to fix it.  Discussion of how to add headers to 822 to fix mailing lists 
is unlikely to be productive.

We should confine our discussion to:

+ clarifying what the existing 822 headers mean
+ clarifying the existing 822 language about how "text message
  teleconferencing" (see section 4.4.3) servers can use existing 822 
  fields like Resent-* and Reply-to
+ clarifying how user agents should interpret 822 fields
  (to the extent that we define user agent behavior at all)

Keith