Received: from localhost by CS.UTK.EDU with SMTP (cf v2.9s-UTK)
	id HAA11273; Thu, 17 Aug 1995 07:01:36 -0400
X-Resent-To: drums@CS.UTK.EDU ; Thu, 17 Aug 1995 07:01:34 EDT
Errors-to: owner-drums@CS.UTK.EDU
Received: from domen.uninett.no by CS.UTK.EDU with SMTP (cf v2.9s-UTK)
	id HAA11258; Thu, 17 Aug 1995 07:01:32 -0400
Received: from dale.uninett.no by domen.uninett.no with SMTP (PP) 
          id <07610-0@domen.uninett.no>; Thu, 17 Aug 1995 13:01:26 +0200
Received: from dale.uninett.no (localhost [127.0.0.1]) 
          by dale.uninett.no (8.6.9/8.6.9) with ESMTP id NAA03256;
          Thu, 17 Aug 1995 13:01:21 +0200
Message-Id: <199508171101.NAA03256@dale.uninett.no>
X-Mailer: exmh version 1.5.3 12/28/94
From: Harald.T.Alvestrand@uninett.no
To: Jacob Palme <jpalme@dsv.su.se>
cc: ietf-drums <drums@CS.UTK.EDU>
Subject: Re: Does "References:" form threads?
In-reply-to: Your message of "Wed, 16 Aug 1995 18:25:05 +0200." <Pine.SUN.3.91.950816182446.21591C-100000@ester>
Mime-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Date: Thu, 17 Aug 1995 13:01:19 +0200
Sender: hta@dale.uninett.no

Jacob,
I think we'd be nuts if we tried to define References: to mean anything
but what Usenet News thinks it does, and we should make DRUMS say that.

The important practical difference now is that In-reply-to: quotes the
*previous* message in the chain, and can include optional text (I think
we should make the message-ID as mandatory as possible), but References:
(as in News) gives you *all* the message-IDs in the thread, allowing you
to reconstruct the thread even if you haven't got all of the messages yet=
=2E

         Harald A