Re: [Ntp] Temporary extension field types for NTPv5
Miroslav Lichvar <mlichvar@redhat.com> Sat, 05 November 2022 14:43 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 3824BC14CF0A for <ntp@ietfa.amsl.com>; Sat, 5 Nov 2022 07:43:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.679
X-Spam-Level:
X-Spam-Status: No, score=-2.679 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.571, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_MSPIKE_H2=-0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_NONE=0.001, T_SCC_BODY_TEXT_LINE=-0.01] 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 ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 60HlNz4jb_nS for <ntp@ietfa.amsl.com>; Sat, 5 Nov 2022 07:43:19 -0700 (PDT)
Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [170.10.133.124]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 274B3C14F724 for <ntp@ietf.org>; Sat, 5 Nov 2022 07:43:18 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1667659397; 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: in-reply-to:in-reply-to:references:references; bh=NRsC+SHpwOiy2fqkeEr/gjCt29hiLZX/TyFOhW+GTfM=; b=VG1wCoQ2woT1FZ5BCPiH3vKtBCM0edjhH/1bjcrllBvc1baU5ka4Uxgg5p49rn4pvQD/Pl jSBVsJQWmVMtuv/AuWKQ27Xm1thdcXp/uWkiS0Sr4JNlH/hQ7P8YJU1RPfOmwkCsjdT6JU oaQy4MG7zAVuorCAwoi+brO1rdTugT0=
Received: from mimecast-mx02.redhat.com (mimecast-mx02.redhat.com [66.187.233.88]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id us-mta-52-XZ-V_QpENamOi637U4FGfQ-1; Sat, 05 Nov 2022 10:43:14 -0400
X-MC-Unique: XZ-V_QpENamOi637U4FGfQ-1
Received: from smtp.corp.redhat.com (int-mx05.intmail.prod.int.rdu2.redhat.com [10.11.54.5]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx02.redhat.com (Postfix) with ESMTPS id 2A04E801231; Sat, 5 Nov 2022 14:43:14 +0000 (UTC)
Received: from localhost (unknown [10.43.135.229]) by smtp.corp.redhat.com (Postfix) with ESMTPS id A8AC418EB4; Sat, 5 Nov 2022 14:43:13 +0000 (UTC)
Date: Sat, 05 Nov 2022 15:43:12 +0100
From: Miroslav Lichvar <mlichvar@redhat.com>
To: David Venhoek <david@venhoek.nl>
Cc: ntp@ietf.org
Message-ID: <Y2Z2gCeG6IPG4frX@localhost>
References: <CAPz_-SWYHWnoe70YLxuLyjMZYP7gUHkr7r4twUm+XsSpcDUOkQ@mail.gmail.com>
MIME-Version: 1.0
In-Reply-To: <CAPz_-SWYHWnoe70YLxuLyjMZYP7gUHkr7r4twUm+XsSpcDUOkQ@mail.gmail.com>
X-Scanned-By: MIMEDefang 3.1 on 10.11.54.5
X-Mimecast-Spam-Score: 0
X-Mimecast-Originator: redhat.com
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
Archived-At: <https://mailarchive.ietf.org/arch/msg/ntp/D3V35atOFPTnUd94LZsqL390fbA>
Subject: Re: [Ntp] Temporary extension field types for NTPv5
X-BeenThere: ntp@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: Network Time Protocol <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: Sat, 05 Nov 2022 14:43:21 -0000
On Sun, Oct 30, 2022 at 07:45:17PM +0100, David Venhoek wrote: > + <t>This field, with type 0xFFFF, is used to indicate which > draft of the specification > + an implementation is based upon. It MUST be included in any > NTPv5 message produced > + by an implementation based on a draft of this > specification, and MUST NOT be included > + in any NTPv5 message produced by an implementation based on > the final version of > + this specification.</t> I think this needs to be changed a bit to avoid traffic amplification when the server is a draft implementation and the client is not, e.g. handle it as another optional field, which can be required for draft clients, and server reponds with it only if it's a draft implementation and the client requested it. -- Miroslav Lichvar
- [Ntp] Temporary extension field types for NTPv5 David Venhoek
- Re: [Ntp] Temporary extension field types for NTP… Miroslav Lichvar