Re: [Ntp] draft-mlichvar-ntp-ntpv5-01
Miroslav Lichvar <mlichvar@redhat.com> Mon, 14 December 2020 11:19 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 7AC5D3A0FE2 for <ntp@ietfa.amsl.com>; Mon, 14 Dec 2020 03:19:40 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.199
X-Spam-Level:
X-Spam-Status: No, score=-0.199 tagged_above=-999 required=5 tests=[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_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, 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 PBYa-pDkB_b6 for <ntp@ietfa.amsl.com>; Mon, 14 Dec 2020 03:19:39 -0800 (PST)
Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [216.205.24.124]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 347183A0FDF for <ntp@ietf.org>; Mon, 14 Dec 2020 03:19:38 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1607944778; 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=vZ8BwaB9aLN8I6J+tvhAdYUOlecFmHmLZNSTCMfCyUw=; b=hdb+SXJSv/qU3bkHIfrT4xwz8R2FpJv6xvdhiNfivAinPm32PMDwpGv2dT4bHMTI5cagSQ sNlTKHQnqGuPWIVZVVjZ0/D0MPFgqU86qocjuUo/EoTpUtTaHAbXjARwOtjBP86kzXZBEo P29jXbZw4G9AhmnRgv/SWmg/7R7n3y8=
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-533-rSyNZGCBORGv6Adj2UPfzQ-1; Mon, 14 Dec 2020 06:19:36 -0500
X-MC-Unique: rSyNZGCBORGv6Adj2UPfzQ-1
Received: from smtp.corp.redhat.com (int-mx03.intmail.prod.int.phx2.redhat.com [10.5.11.13]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx01.redhat.com (Postfix) with ESMTPS id 1BBF1107ACE8; Mon, 14 Dec 2020 11:19:35 +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 9AEFA709B1; Mon, 14 Dec 2020 11:19:33 +0000 (UTC)
Date: Mon, 14 Dec 2020 12:19:32 +0100
From: Miroslav Lichvar <mlichvar@redhat.com>
To: g16 <g16g16g16@gmail.com>
Cc: ntp@ietf.org
Message-ID: <20201214111932.GD2540645@localhost>
References: <CAFZ=0Sx3WeG5JY7RV+OS7OqFMLcVRCaW-w2OZG+d39_cJ5hbpg@mail.gmail.com>
MIME-Version: 1.0
In-Reply-To: <CAFZ=0Sx3WeG5JY7RV+OS7OqFMLcVRCaW-w2OZG+d39_cJ5hbpg@mail.gmail.com>
X-Scanned-By: MIMEDefang 2.79 on 10.5.11.13
Authentication-Results: relay.mimecast.com; auth=pass smtp.auth=CUSA124A263 smtp.mailfrom=mlichvar@redhat.com
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/RRiShYasJIMtKwVBp-ABIkhS7ak>
Subject: Re: [Ntp] draft-mlichvar-ntp-ntpv5-01
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: Mon, 14 Dec 2020 11:19:40 -0000
On Fri, Dec 11, 2020 at 01:23:07AM +0900, g16 wrote: > As written, Some NTPv4 implementations drop requests with unknown > extensions. As I read the draft, there is no mention of handling unknown > extensions. So, can NTPv5 make it a MUST requirement to just ignore > unknown extensions instead of dropping packets? (Counted for symmetry of > data volume) Thanks for catching that. I added it to the draft. > I'd say it's good for future extensibility. > > When new extensions are defined in the future, a client indicates a > supported extension by sending the extension in a request, and the server > can only send extensions that the client supports.The client knows if the > server understands the extension by seeing the same extension in the > response. Yes, that's how it is supposed to work. -- Miroslav Lichvar
- [Ntp] draft-mlichvar-ntp-ntpv5-01 Miroslav Lichvar
- Re: [Ntp] draft-mlichvar-ntp-ntpv5-01 g16
- Re: [Ntp] draft-mlichvar-ntp-ntpv5-01 Miroslav Lichvar
- Re: [Ntp] draft-mlichvar-ntp-ntpv5-02 Miroslav Lichvar