IETF Logo Mail Archive

Re: [Ntp] Antw: Re: Antw: Re: Antw: [EXT] A different NTPv5 design

Miroslav Lichvar <mlichvar@redhat.com> Thu, 30 April 2020 13:00 UTC

Return-Path: <mlichvar@redhat.com>
X-Original-To: ntp@ietfa.amsl.com
Delivered-To: ntp@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 43EB13A08F6 for <ntp@ietfa.amsl.com>; Thu, 30 Apr 2020 06:00:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.921
X-Spam-Level:
X-Spam-Status: No, score=-2.921 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_MSPIKE_H2=-0.82, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=redhat.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id U4aNDI9XGl8h for <ntp@ietfa.amsl.com>; Thu, 30 Apr 2020 06:00:11 -0700 (PDT)
Received: from us-smtp-1.mimecast.com (us-smtp-delivery-1.mimecast.com [207.211.31.120]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A2C183A08E8 for <ntp@ietf.org>; Thu, 30 Apr 2020 06:00:11 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1588251610; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=pLh81YBMIMJOJNuTuw63jZt1qss0vfXGz4IEcJi/Djs=; b=EsTpAZpVRMpncDDDnHfzoGxigFuwYF+V3jQ3fdrXakNGlc7X3GZ9Wbk1AGS5h4m3wEY3id dlgIYStu/UUgvmGUaafMaMRqbIkAzaeGsf5KHqpyOC+vCUkHM4r6evhXSat/ZpBGCRjw0x c5+kn00JxOgZfzw0G/Nco5BBXLkPUhw=
Received: from mimecast-mx01.redhat.com (mimecast-mx01.redhat.com [209.132.183.4]) (Using TLS) by relay.mimecast.com with ESMTP id us-mta-233-unOzyG2iNASu0DfE5wDi1w-1; Thu, 30 Apr 2020 09:00:07 -0400
X-MC-Unique: unOzyG2iNASu0DfE5wDi1w-1
Received: from smtp.corp.redhat.com (int-mx01.intmail.prod.int.phx2.redhat.com [10.5.11.11]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx01.redhat.com (Postfix) with ESMTPS id B281A8014D6; Thu, 30 Apr 2020 13:00:06 +0000 (UTC)
Received: from localhost (holly.tpb.lab.eng.brq.redhat.com [10.43.134.11]) by smtp.corp.redhat.com (Postfix) with ESMTPS id 03FAE512F5; Thu, 30 Apr 2020 13:00:05 +0000 (UTC)
Date: Thu, 30 Apr 2020 15:00:04 +0200
From: Miroslav Lichvar <mlichvar@redhat.com>
To: Ulrich Windl <Ulrich.Windl@rz.uni-regensburg.de>
Cc: "ntp@ietf.org" <ntp@ietf.org>
Message-ID: <20200430130004.GC25085@localhost>
References: <7114_1588171569_5EA99331_7114_20_1_20200429144540.GD8457@localhost> <5EAA7620020000A1000389F2@gwsmtp.uni-regensburg.de> <20200430101644.GA25085@localhost> <5EAAB0D1020000A100038A21@gwsmtp.uni-regensburg.de> <20200430115622.GB25085@localhost> <5EAAC5E2020000A100038A3D@gwsmtp.uni-regensburg.de>
MIME-Version: 1.0
In-Reply-To: <5EAAC5E2020000A100038A3D@gwsmtp.uni-regensburg.de>
X-Scanned-By: MIMEDefang 2.79 on 10.5.11.11
X-Mimecast-Spam-Score: 0
X-Mimecast-Originator: redhat.com
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline
Archived-At: <https://mailarchive.ietf.org/arch/msg/ntp/m5Do86ZzZP_Ksl4mEdcxYB7OFtM>
Subject: Re: [Ntp] Antw: Re: Antw: Re: Antw: [EXT] A different NTPv5 design
X-BeenThere: ntp@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: <ntp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ntp>, <mailto:ntp-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ntp/>
List-Post: <mailto:ntp@ietf.org>
List-Help: <mailto:ntp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ntp>, <mailto:ntp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 30 Apr 2020 13:00:14 -0000

On Thu, Apr 30, 2020 at 02:34:42PM +0200, Ulrich Windl wrote:
> > There was a time (before RFC 5905) when ntpd announced it whole month
> > before. That lead to the leap indicator getting stuck as there was no
> > period where it should be unset. I'd rather not risk that happening
> > again.
> 
> I was talking about an extension field that ol versions don't know of AND I
> was proposing to add the time when the leap event is to occur...

If a timestamp of the leap second is provided in an extension field,
it would better have its own leap indicator, so it can be set as soon
as the Bulletin C is published. The leap indicator in the header
should be useful without this extension field.

-- 
Miroslav Lichvar

v2.23.0 | Report a Bug | By Email