Re: Origins of DATE command
Brian Kantor <brian@nothing.ucsd.edu> Mon, 15 July 1996 03:58 UTC
Received: from ietf.cnri.reston.va.us by IETF.CNRI.Reston.VA.US id aa03609;
14 Jul 96 23:58 EDT
Received: from CNRI.Reston.VA.US by IETF.CNRI.Reston.VA.US id aa03598;
14 Jul 96 23:58 EDT
Received: from PHEASANT.ACADEM.COM by CNRI.Reston.VA.US id aa00786;
14 Jul 96 23:58 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 WAA05610 for
<ietf-nntp@PHEASANT.ACADEM.COM>; Sun, 14 Jul 1996 22:57:41 -0500
Received: from nothing.ucsd.edu (nothing.ucsd.edu [132.239.1.4]) by academ.com
(8.7.5/8.7.1) with SMTP id WAA02144 for <ietf-nntp@academ.com>;
Sun, 14 Jul 1996 22:57:39 -0500 (CDT)
Received: by nothing.ucsd.edu (8.6.12/UCSDGENERIC.5)
id UAA05650 to ; Sun, 14 Jul 1996 20:57:22 -0700
Date: Sun, 14 Jul 1996 20:57:22 -0700
Sender: ietf-archive-request@IETF.CNRI.Reston.VA.US
From: Brian Kantor <brian@nothing.ucsd.edu>
Message-Id: <199607150357.UAA05650@nothing.ucsd.edu>
To: tal@plts.org
Subject: Re: Origins of DATE command
Cc: ietf-nntp@academ.com
>YYYYMMDDHHMM I think we wound up suggesting ISO8601 (?) format in one of the drafts YYYYMMDDHHMMSS[.sss] e.g., 19960714210000.000 the nice thing about standards is that there are so many to choose from - Brian
- Origins of DATE command Paul Overell
- Re: Origins of DATE command Stan Barber
- Re: Origins of DATE command Brian Kantor
- Re: Origins of DATE command Tom Limoncelli
- Re: Origins of DATE command Brian Kantor
- Re: Origins of DATE command markd
- Re: Origins of DATE command Harald Kipp