[Syslog] TIMESTAMP and leap seconds

"Rainer Gerhards" <rgerhards@hq.adiscon.com> Mon, 02 January 2006 10:42 UTC

Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EtN97-0007ZR-GN; Mon, 02 Jan 2006 05:42:33 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EtN96-0007YC-I3 for syslog@megatron.ietf.org; Mon, 02 Jan 2006 05:42:32 -0500
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA12928 for <syslog@ietf.org>; Mon, 2 Jan 2006 05:41:18 -0500 (EST)
Received: from hetzner.adiscon.com ([85.10.201.79]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EtNDd-0003Sb-3S for syslog@ietf.org; Mon, 02 Jan 2006 05:47:46 -0500
Received: from localhost (localhost [127.0.0.1]) by hetzner.adiscon.com (Postfix) with ESMTP id CB34E27C02C for <syslog@ietf.org>; Mon, 2 Jan 2006 11:36:12 +0100 (CET)
Received: from hetzner.adiscon.com ([127.0.0.1]) by localhost (debian [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 24073-02 for <syslog@ietf.org>; Mon, 2 Jan 2006 11:36:12 +0100 (CET)
Received: from fmint2.intern.adiscon.com (pd95b68d5.dip0.t-ipconnect.de [217.91.104.213]) by hetzner.adiscon.com (Postfix) with ESMTP id 9191E27C02B for <syslog@ietf.org>; Mon, 2 Jan 2006 11:36:12 +0100 (CET)
Received: from grfint2.intern.adiscon.com ([172.19.0.6]) by fmint2.intern.adiscon.com with Microsoft SMTPSVC(6.0.3790.1830); Mon, 2 Jan 2006 11:41:36 +0100
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable
Date: Mon, 02 Jan 2006 11:41:31 +0100
Message-ID: <577465F99B41C842AAFBE9ED71E70ABA0E416E@grfint2.intern.adiscon.com>
X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0
Thread-Topic: TIMESTAMP and leap seconds
Thread-Index: AcYPiRf7ApYn2aaJTU2lmv3YiiNzhQ==
From: Rainer Gerhards <rgerhards@hq.adiscon.com>
To: syslog@ietf.org
X-OriginalArrivalTime: 02 Jan 2006 10:41:36.0924 (UTC) FILETIME=[1B476DC0:01C60F89]
X-Virus-Scanned: by amavisd-new-20030616-p10 (Debian) at adiscon.com
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 798b2e660f1819ae38035ac1d8d5e3ab
Content-Transfer-Encoding: quoted-printable
Cc:
Subject: [Syslog] TIMESTAMP and leap seconds
X-BeenThere: syslog@lists.ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Security Issues in Network Event Logging <syslog.lists.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/syslog>, <mailto:syslog-request@lists.ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/syslog>
List-Post: <mailto:syslog@lists.ietf.org>
List-Help: <mailto:syslog-request@lists.ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/syslog>, <mailto:syslog-request@lists.ietf.org?subject=subscribe>
Sender: syslog-bounces@lists.ietf.org
Errors-To: syslog-bounces@lists.ietf.org

Hi all,

first of all, I would like to whish a happy new year to each of you!

I am now back in the office and at final edits to syslog-protocol. I
discovered one more thing: The current draft supports leap seconds.
There already is a lot of discussion whether or not leap seconds should
be introduced in the future. However, the way leap seconds are handled
will be largely invisible to a syslog sender (except where it is sitting
on a time-tracking device, which is highly unlikely). On the other hand,
leap second processing can be pretty complicated at the receiver side. I
expect that most implementations will not abide strict handling in any
case.

As such, I suggest that leap second support be removed from the
TIMESTAMP. Similarily, a sender with unknown time should then not use
the special TIMESTAMP but "-", which also keeps it consistent with the
rest of the header NIL values.

If nobody objects, I'll change this during the edit.

Rainer

_______________________________________________
Syslog mailing list
Syslog@lists.ietf.org
https://www1.ietf.org/mailman/listinfo/syslog