[Ntp] SNTP and extension fields (WAS: Re: Antw: Re: Antw: Re: Antw: [EXT] NTPv5 Loop Detection without Stratum)

kristof.teichel@ptb.de Tue, 06 September 2022 09:50 UTC

Return-Path: <kristof.teichel@ptb.de>
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 E0B8CC1522C5; Tue, 6 Sep 2022 02:50:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.405
X-Spam-Level:
X-Spam-Status: No, score=-4.405 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=ptb.de
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 uuMQtJEsEoch; Tue, 6 Sep 2022 02:50:22 -0700 (PDT)
Received: from mx1.bs.ptb.de (mx1.bs.ptb.de [192.53.103.120]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C2C76C14CE40; Tue, 6 Sep 2022 02:50:20 -0700 (PDT)
Received: from smtp-hub.bs.ptb.de (smtpint01.bs.ptb.de [141.25.87.32]) by mx1.bs.ptb.de with ESMTP id 2869oHFQ000306-2869oHFS000306 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK) for <halmurray@sonic.net>; Tue, 6 Sep 2022 11:50:17 +0200
In-Reply-To: <20220906070439.08DEE28C1D8@107-137-68-211.lightspeed.sntcca.sbcglobal.net>
References: Message from "Ulrich Windl" <Ulrich.Windl@rz.uni-regensburg.de> of "Tue, 06 Sep 2022 08:23:16 +0200." <6316E754020000A10004D6D4@gwsmtp.uni-regensburg.de> <20220906070439.08DEE28C1D8@107-137-68-211.lightspeed.sntcca.sbcglobal.net>
To: Hal Murray <halmurray@sonic.net>
Cc: "ntp@ietf.org" <ntp@ietf.org>, ntp <ntp-bounces@ietf.org>, Ulrich Windl <Ulrich.Windl@rz.uni-regensburg.de>
MIME-Version: 1.0
X-KeepSent: 28F46941:3B68CC6E-C12588B5:00356D41; type=4; name=$KeepSent
From: kristof.teichel@ptb.de
Message-ID: <OF28F46941.3B68CC6E-ONC12588B5.00356D41-C12588B5.0036092A@ptb.de>
Date: Tue, 06 Sep 2022 11:50:09 +0200
X-MIMETrack: Serialize by Router on MAILGW01/PTB at 09/06/2022 11:50:17 AM, Serialize complete at 09/06/2022 11:50:17 AM
Content-Type: multipart/alternative; boundary="=_alternative 00360929C12588B5_="
X-FE-Last-Public-Client-IP: 141.25.87.32
X-FE-Policy-ID: 5:5:5:SYSTEM
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; d=ptb.de; s=s1-ptbde; c=relaxed/relaxed; h=references:to:cc:mime-version:subject:from:message-id:date:content-type; bh=ACukZbQcGorGNbVTyRUQ5iDg3xglPEDgdI4ugttHPSY=; b=ieECA3FjSYOXcZNRv9a28Cg6ktOSkG18jV0Zfg3Ht658N0oc2dxL/HSH70CmLKOrJbRJGA7usEtg e0gdX1ZEH4MbD9UP1Qctx5w5fyznMGBswIfgzTTKJJNAdHLf3ytVEivn4wa+VX7CU+0KKIn1SsFD XWHuI6DFVFcDOvqNztEM0Mi9Zi8/Plr17PKqfltm9YYhDDZHpGOLhFByfr36SZDIsYVmenMbnJAi KobkfnnXY9cwvd7IFgifuRpT6FDzbMhXx0lDbOfJgjlmQ/Uc7WOWit/j3jYWOW88P+BrQQEsuL8V F5nEWrs5BS2nBnvVKDVpTgAxrB2nz18JjDlpbA==
Archived-At: <https://mailarchive.ietf.org/arch/msg/ntp/xdiVzg5V33VmOmfjPkI_vroKYL4>
Subject: [Ntp] SNTP and extension fields (WAS: Re: Antw: Re: Antw: Re: Antw: [EXT] NTPv5 Loop Detection without Stratum)
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: Tue, 06 Sep 2022 09:50:27 -0000

> 
> Ulrich.Windl@rz.uni-regensburg.de said:
> > Yes, but a "packet format" does not mean a fixed-length packet IMHO; 
instead
> > if should contain a mechanism for a variable number of optional fields 
that
> > can have a variable length and should be parseable even if it's only 
to
> > ignore them. I think that is what the e tension fields had in mind, 
but
> > somewhat short-sighted. 
> 
> You are tangling 2 threads.  The chunk you are replying to is discussing 
SNTP.
> 
> The S is for Simple.  I hope SNTP will work without extension fields.
> 

Wouldn't that preclude use of NTS?
(It would, and also that of any other security measures other than v3-era 
symmetric key MAC with unspecified key exchange, if I'm not mistaken...) 

If that's correct: can we afford to rule out modern (well-scaling) 
authentication for any and all SNTP clients?