IETF Logo Mail Archive

Re: ietf-nntp New wording on article numbers

Jon Ribbens <jon@oaktree.co.uk> Sun, 29 December 1996 00:39 UTC

Received: from cnri by ietf.org id aa11398; 28 Dec 96 19:39 EST
Received: from ACADEM2.ACADEM.COM by CNRI.Reston.VA.US id aa16363; 28 Dec 96 19:39 EST
Received: (from majordomo@localhost) by academ2.academ.com (8.8.4/8.7.3) id SAA05151 for ietf-nntp-outgoing; Sat, 28 Dec 1996 18:36:45 -0600 (CST)
X-Authentication-Warning: academ2.academ.com: majordomo set sender to owner-ietf-nntp using -f
Received: from academ.com (root@ACADEM.COM [198.137.249.2]) by academ2.academ.com (8.8.4/8.7.3) with ESMTP id SAA05146 for <ietf-nntp@ACADEM2.ACADEM.COM>; Sat, 28 Dec 1996 18:36:42 -0600 (CST)
Received: from black.oaktree.co.uk (root@black.oaktree.co.uk [194.217.216.129]) by academ.com (8.8.4/8.7.1) with ESMTP id SAA02502 for <ietf-nntp@academ.com>; Sat, 28 Dec 1996 18:36:40 -0600 (CST)
Received: (from jon@localhost) by black.oaktree.co.uk (8.7.5/8.7.3) id AAA28642; Sun, 29 Dec 1996 00:36:26 GMT
From: Jon Ribbens <jon@oaktree.co.uk>
Message-Id: <199612290036.AAA28642@black.oaktree.co.uk>
Subject: Re: ietf-nntp New wording on article numbers
To: "Clive D.W. Feather" <clive@demon.net>
Date: Sun, 29 Dec 1996 00:36:26 +0000 (GMT)
Cc: jack@wildbear.on.ca, ccaputo@alt.net, ietf-nntp@academ.com
In-Reply-To: <851806634.29143.0@office.demon.net> from "Clive D.W. Feather" at Dec 28, 96 08:57:14 pm
X-Mailer: ELM [version 2.4 PL25]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-ietf-nntp@academ.com
Precedence: bulk

Clive D.W. Feather wrote:
> > Personally, I wouldn't mind seeing a header that states the
> > time it was originally inserted into the news system, say 'Posting-Date',
> > and what time it is posted on my local system, say 'Receive-Date' (or
> > some better name).  I would like to see something that may tell me
> > how old an article is, and if so, why it took so long.
> 
> It would be an implementation nightmare to include this in the article
> itself, as many implementations forward articles to peers from the spool;
> therefore it mustn't be placed in the spool copy, but added by the NNTP
> server on retrieval.

We're going backwards in time here, folks... ;-) There used
to be a header, 'Date-Received', which I presume was exactly
what the suggested 'Receive-Date' header above is. 'Date'
already performs the function of 'Posting-Date'.

'Date-Received' was dropped for a reason. I don't know
what that reason was, but I presume it was a good one ;-).

Cheers


Jon
____
\  //    Jon Ribbens    // 10MB virtual-hosted // www.oaktree.co.uk
 \// jon@oaktree.co.uk // web space for 49UKP //

v2.8.7 | Report a Bug | By Email