Re: Origins of DATE command

Tom Limoncelli <tal@plts.org> Mon, 15 July 1996 03:27 UTC

Received: from ietf.cnri.reston.va.us by IETF.CNRI.Reston.VA.US id aa00634; 14 Jul 96 23:27 EDT
Received: from CNRI.Reston.VA.US by IETF.CNRI.Reston.VA.US id aa00630; 14 Jul 96 23:27 EDT
Received: from PHEASANT.ACADEM.COM by CNRI.Reston.VA.US id aa00433; 14 Jul 96 23:27 EDT
Received: from academ.com (root@ACADEM.COM [198.137.249.2]) by pheasant.academ.com (8.7.5/8.6.9) with ESMTP id WAA05487 for <ietf-nntp@PHEASANT.ACADEM.COM>; Sun, 14 Jul 1996 22:26:41 -0500
Received: from jupiter.superlink.net (root@jupiter.superlink.net [204.97.220.2]) by academ.com (8.7.5/8.7.1) with ESMTP id WAA02095 for <ietf-nntp@academ.com>; Sun, 14 Jul 1996 22:26:39 -0500 (CDT)
Received: from earth.superlink.net (earth.superlink.net [204.97.220.6]) by jupiter.superlink.net (8.7.4/8.7.3) with SMTP id XAA14106; Sun, 14 Jul 1996 23:26:10 -0400 (EDT)
Received: from plts.org by earth.superlink.net via ESMTP (950413.SGI.8.6.12/940406.SGI) id XAA06024; Sun, 14 Jul 1996 23:26:07 -0400
Received: (from tal@localhost) by plts.org (8.7.3/8.7.3) id XAA00777; Sun, 14 Jul 1996 23:27:42 -0400 (EDT)
Sender: ietf-archive-request@IETF.CNRI.Reston.VA.US
From: Tom Limoncelli <tal@plts.org>
Message-Id: <199607150327.XAA00777@plts.org>
Subject: Re: Origins of DATE command
To: Brian Kantor <brian@nothing.ucsd.edu>
Date: Sun, 14 Jul 1996 23:27:41 -0400 (EDT)
Cc: ietf-nntp@academ.com, paulo@turnpike.com
In-Reply-To: <199607150129.SAA03029@nothing.ucsd.edu> from "Brian Kantor" at Jul 14, 96 06:29:46 pm
Content-Type: text

> In the arguments over the NNTPv2 spec, one of the concerns was that
> clients would use the DATE command as a remote time clock, and beat
> the NNTP server to death asking about the time of day.  [In today's
> [...]
> add a command (never named) which would represent a 'magic cookie'
> that could be fed to the NEWNEWS command just as the ISO date is in
> the v1 implementation.  It was to be a server-dependent item; you would
> request it and save it and return it, but you didn't interpret it.
> Whether it was an ISO format timestamp, an encrypted version of it,
> an offset into the history file, or whatever, wasn't important.  It

Let me be a polyanna and suggest that we simply return the date in
YYYYMMDDHHMM format... that is, we don't return the number of seconds.
It still works for NEWNEWS, you just might get a couple more articles
since losing the number of seconds means rounding down.  We just have
to make sure it doesn't break (many) existing implementations.

If someone chooses to set their clock by that rather than by installing
NTP, rdate or something else... all power to them.

I'd prefer not to invent a lot in this area.  Let's spend our
"invention" budget on search mechanisms, improved transports, and truth,
justice, and 8-bit text.

--tal


-- 
             Tom Limoncelli -- http://mars.superlink.net/user/tal
            tal@plts.org (home)  --  tal@dnrc.bell-labs.com (work)
Okay, we've seen Franklin with no shirt, Garibaldi with no shirt, and Sheridan
   with no shirt.  When do you get some shirtless screentime with Marcus???