Received: from localhost by CS.UTK.EDU with SMTP (cf v2.9s-UTK) id HAA10784; Wed, 17 Mar 1999 07:33:30 -0500 (EST) Received: by cs.cs.utk.edu (bulk_mailer v1.12); Wed, 17 Mar 1999 07:31:29 -0500 Received: by CS.UTK.EDU (cf v2.9s-UTK) id HAA10588; Wed, 17 Mar 1999 07:31:27 -0500 (EST) Received: from out0.mx.skynet.be (out0.mx.skynet.be [195.238.2.35]) by CS.UTK.EDU with ESMTP (cf v2.9s-UTK) id HAA10568; Wed, 17 Mar 1999 07:31:18 -0500 (EST) Received: from [195.238.1.121] (brad.techos.skynet.be [195.238.1.121]) by out0.mx.skynet.be (8.9.3/odie-relay-v1.0) with SMTP id NAA23907 for ; Wed, 17 Mar 1999 13:31:06 +0100 (MET) In-Reply-To: <19990316235013.666.qmail@cr.yp.to> X-Mailer: CTM PowerMail 2.4b2 X-URL: http://www.skynet.be x-sender: blk@foxbert.skynet.be Date: Wed, 17 Mar 1999 09:25:03 +0100 To: drums@cs.utk.edu From: Brad Knowles Subject: Re: References/In-Reply-To replacement text Message-Id: <19990317092503.012164@relay.skynet.be> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit List-Unsubscribe: On Tue, Mar 16, 1999, D. J. Bernstein wrote: >What's the benefit of creating both In-Reply-To and References when >there's only one parent? This seems unnecessarily complicated. You have obviously not been reading your mail. There is not just one parent. Existing RFC 821 terminology allows for multiple parents. What we have been discussing is the exact wording of how these fields should be described so as to make this fact more explicit, and to give a little more active direction to those folks who are writing MUAs that might make use of these facts when constructing message threads. -- These are my opinions -- not to be taken as official Skynet policy ____________________________________________________________________ |o| Brad Knowles, Belgacom Skynet NV/SA |o| |o| Systems Architect, News/mail/FTP Admin Rue Col. Bourg, 124 |o| |o| Phone/Fax: +32-2-706.11.11/12.49 B-1140 Brussels |o| |o| http://www.skynet.be Belgium |o| \/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/ Usenet is not the web. Just because the web handles some things poorly is not a good reason to apply those same solutions to Usenet.