ietf-nntp Re: Date
Brian Kantor <brian@nothing.ucsd.edu> Sat, 28 December 1996 18:42 UTC
Received: from cnri by ietf.org id aa29901; 28 Dec 96 13:42 EST
Received: from ACADEM2.ACADEM.COM by CNRI.Reston.VA.US id aa11800;
28 Dec 96 13:42 EST
Received: (from majordomo@localhost) by academ2.academ.com (8.8.4/8.7.3) id
MAA03464 for ietf-nntp-outgoing; Sat, 28 Dec 1996 12:40:34 -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 MAA03459 for
<ietf-nntp@ACADEM2.ACADEM.COM>; Sat, 28 Dec 1996 12:40:32 -0600 (CST)
Received: from nothing.ucsd.edu (nothing.ucsd.edu [132.239.1.4]) by academ.com
(8.8.4/8.7.1) with ESMTP id MAA00837 for <ietf-nntp@academ.com>;
Sat, 28 Dec 1996 12:40:31 -0600 (CST)
Received: by nothing.ucsd.edu (8.8.3/UCSDGENERIC.5)
id SAA21393 to ietf-nntp@academ.com; Sat, 28 Dec 1996 18:39:22 GMT
Date: Sat, 28 Dec 1996 18:39:22 GMT
From: Brian Kantor <brian@nothing.ucsd.edu>
Message-Id: <199612281839.SAA21393@nothing.ucsd.edu>
To: ietf-nntp@academ.com
Subject: ietf-nntp Re: Date
Sender: owner-ietf-nntp@academ.com
Precedence: bulk
The Date: header should remain the posting date - that is, the date that the article was generated and inserted into the news system as evaluated at the originating client/server. If an arrival date is solely required for expiration reasons, there is no reason to modify the article to store it - it is not supplied to reading clients nor transport peers, so it is solely an implementation issue. If people wish to have a client be able to inquire when the article arrived (was cancelled, will be expired, etc), these are site-specific data that might be a subject for some sort of 'optional information' command. - Brian
- ietf-nntp Re: Date Brian Kantor