RE: [Syslog] TIMESTAMP and leap seconds

"Andrew Ross" <andrew@kiwisyslog.com> Tue, 03 January 2006 09:32 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 1EtiWh-0001gz-JO; Tue, 03 Jan 2006 04:32:19 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EtiWe-0001fQ-W3 for syslog@megatron.ietf.org; Tue, 03 Jan 2006 04:32:17 -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 EAA26791 for <syslog@ietf.org>; Tue, 3 Jan 2006 04:31:03 -0500 (EST)
Received: from relay03.pair.com ([209.68.5.17]) by ietf-mx.ietf.org with smtp (Exim 4.43) id 1Etibt-0003bS-89 for syslog@ietf.org; Tue, 03 Jan 2006 04:37:42 -0500
Received: (qmail 34370 invoked from network); 3 Jan 2006 09:32:06 -0000
Received: from unknown (HELO KiwiAndrew) (unknown) by unknown with SMTP; 3 Jan 2006 09:32:06 -0000
X-pair-Authenticated: 222.152.148.36
From: Andrew Ross <andrew@kiwisyslog.com>
To: 'Rainer Gerhards' <rgerhards@hq.adiscon.com>
Subject: RE: [Syslog] TIMESTAMP and leap seconds
Date: Tue, 03 Jan 2006 22:32:02 +1300
Organization: Kiwi Enterprises
Message-ID: <000501c61048$8eb2cc90$d9a8a8c0@KiwiAndrew>
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook, Build 10.0.6626
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.2180
Importance: Normal
In-Reply-To: <577465F99B41C842AAFBE9ED71E70ABA0E416E@grfint2.intern.adiscon.com>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 769a46790fb42fbb0b0cc700c82f7081
Content-Transfer-Encoding: 7bit
Cc: syslog@ietf.org
X-BeenThere: syslog@lists.ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: andrew@kiwisyslog.com
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 Rainer,

Happy new year!

Your idea of ignoring the leap seconds sounds very sensible to me.

Cheers

Andrew


-----Original Message-----
From: syslog-bounces@lists.ietf.org [mailto:syslog-bounces@lists.ietf.org]
On Behalf Of Rainer Gerhards
Sent: Monday, 2 January 2006 11:42 p.m.
To: syslog@ietf.org
Subject: [Syslog] TIMESTAMP and leap seconds


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


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