Received: from localhost by CS.UTK.EDU with SMTP (cf v2.9s-UTK) id DAA17163; Thu, 24 Aug 1995 03:08:11 -0400 X-Resent-To: drums@CS.UTK.EDU ; Thu, 24 Aug 1995 03:08:09 EDT Errors-to: owner-drums@CS.UTK.EDU Received: from domen.uninett.no by CS.UTK.EDU with SMTP (cf v2.9s-UTK) id DAA17153; Thu, 24 Aug 1995 03:08:02 -0400 Received: from dale.uninett.no by domen.uninett.no with SMTP (PP) id <15001-0@domen.uninett.no>; Thu, 24 Aug 1995 09:07:18 +0200 Received: from dale.uninett.no (localhost [127.0.0.1]) by dale.uninett.no (8.6.9/8.6.9) with ESMTP id AAA08605; Thu, 24 Aug 1995 00:57:24 +0200 Message-Id: <199508232257.AAA08605@dale.uninett.no> From: Harald.T.Alvestrand@uninett.no To: Jacob Palme cc: ietf-drums Subject: Re: Ambiguity of the "Newsgroups:" heading field in e-mail In-reply-to: Your message of "Thu, 27 Jul 1995 11:18:13 +0200." MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <8602.809218643.1@dale.uninett.no> Date: Thu, 24 Aug 1995 00:57:23 +0200 Sender: hta@dale.uninett.no Formally, the DRUMS group cannot attach a given meaning to Newsgroups:, since it is barred from including anything that it not at least Draft Standard, and RFC 1036 is a Proposed Standard. In reality, it should make a generic statement about interpreting headers - something like "a header is a header, independent of the medium in which it is carried. For instance, the Newsgroups: header used by News should not have its meaning changed because the medium of transportation is SMTP and not NNTP", clearly favoring one of your alternatives. Harald A