IETF Logo Mail Archive

Re: [ntpwg] New Version Notification for draft-ietf-ntp-network-time-security-12.txt and draft-ietf-ntp-using-nts-for-ntp-03.txt

dieter.sibold@ptb.de Tue, 22 December 2015 09:34 UTC

Return-Path: <ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org>
X-Original-To: ietfarch-ntp-archives-ahFae6za@ietfa.amsl.com
Delivered-To: ietfarch-ntp-archives-ahFae6za@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E088C1A8849 for <ietfarch-ntp-archives-ahFae6za@ietfa.amsl.com>; Tue, 22 Dec 2015 01:34:51 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.909
X-Spam-Level:
X-Spam-Status: No, score=-6.909 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
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 rskA3BommQX4 for <ietfarch-ntp-archives-ahFae6za@ietfa.amsl.com>; Tue, 22 Dec 2015 01:34:50 -0800 (PST)
Received: from lists.ntp.org (lists.ntp.org [149.20.68.7]) by ietfa.amsl.com (Postfix) with ESMTP id 218441A8848 for <ntp-archives-ahFae6za@lists.ietf.org>; Tue, 22 Dec 2015 01:34:50 -0800 (PST)
Received: from lists.ntp.org (lists.ntp.org [149.20.68.7]) by lists.ntp.org (Postfix) with ESMTP id E53E086DB2A for <ntp-archives-ahFae6za@lists.ietf.org>; Tue, 22 Dec 2015 09:34:49 +0000 (UTC)
X-Original-To: ntpwg@lists.ntp.org
Delivered-To: ntpwg@lists.ntp.org
Received: from mail1.ntp.org (mail1.ntp.org [IPv6:2001:4f8:fff7:1::5]) by lists.ntp.org (Postfix) with ESMTP id 19B3386DAD8 for <ntpwg@lists.ntp.org>; Tue, 22 Dec 2015 09:24:40 +0000 (UTC)
Received: from mx1.bs.ptb.de ([192.53.103.120]) by mail1.ntp.org with esmtps (TLSv1:AES256-SHA:256) (Exim 4.77 (FreeBSD)) (envelope-from <dieter.sibold@ptb.de>) id 1aBJBH-000AMt-8N; Tue, 22 Dec 2015 09:24:40 +0000
Received: from smtp-hub.bs.ptb.de (smtpint01.bs.ptb.de [141.25.87.32]) by mx1.bs.ptb.de with ESMTP id tBM9ORn1006290-tBM9ORn3006290 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-SHA bits=256 verify=FAIL); Tue, 22 Dec 2015 10:24:27 +0100
Received: from rose.bs.ptb.de (rose.bs.ptb.de [141.25.85.201]) by smtp-hub.bs.ptb.de (Postfix) with ESMTP id 28F0DDC3D; Tue, 22 Dec 2015 10:24:27 +0100 (CET)
In-Reply-To: <567877FB.7030608@ntp.org>
References: <56785CE5.6080102@ntp.org> <OFDECED69B.3FA71F92-ONC1257F22.0063AA4C-C1257F22.006401FE@ptb.de> <OF3D6DD6FA.812C6BCC-ONC1257F22.00775A28-C1257F22.00775A29@ptb.de> <567877FB.7030608@ntp.org>
To: mayer@ntp.org
MIME-Version: 1.0
Message-ID: <OF0AC1CCBA.2E240196-ONC1257F23.00313FBA-C1257F23.0033AC80@ptb.de>
From: dieter.sibold@ptb.de
Date: Tue, 22 Dec 2015 10:24:25 +0100
X-SA-Exim-Connect-IP: 192.53.103.120
X-SA-Exim-Rcpt-To: mayer@ntp.org, ntpwg@lists.ntp.org
X-SA-Exim-Mail-From: dieter.sibold@ptb.de
X-SA-Exim-Version: 4.2
X-SA-Exim-Scanned: Yes (on mail1.ntp.org)
Subject: Re: [ntpwg] New Version Notification for draft-ietf-ntp-network-time-security-12.txt and draft-ietf-ntp-using-nts-for-ntp-03.txt
X-BeenThere: ntpwg@lists.ntp.org
X-Mailman-Version: 2.1.20
Precedence: list
List-Id: IETF Working Group for Network Time Protocol <ntpwg.lists.ntp.org>
List-Unsubscribe: <http://lists.ntp.org/options/ntpwg>, <mailto:ntpwg-request@lists.ntp.org?subject=unsubscribe>
List-Archive: <http://lists.ntp.org/pipermail/ntpwg/>
List-Post: <mailto:ntpwg@lists.ntp.org>
List-Help: <mailto:ntpwg-request@lists.ntp.org?subject=help>
List-Subscribe: <http://lists.ntp.org/listinfo/ntpwg>, <mailto:ntpwg-request@lists.ntp.org?subject=subscribe>
Cc: ntpwg@lists.ntp.org
Content-Type: multipart/mixed; boundary="===============6360225780768715808=="
Errors-To: ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org
Sender: ntpwg <ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org>

You can see it in the draft "draft-ietf-ntp-using-nts-for-ntp-03". There 
it is mentioned e.g. in sect. 6.1.3.2. The idea is that NTS for NTP 
defines one additional extension field (see section IANA registration) and 
that all NTS-messages are using this extension field. The different NTS 
message types are distinguished by their respective OID (see the next 
version of the draft "draft-ietf-ntp-cms-for-nts-message"). This also is 
true for the MAC. Kristof please correct me if I'm wrong. The field type 
of the NTS extension field is not registered yet. This has to be done as 
soon as possible. This was also discussed with the NTF.

Dieter

-------------------------------------
Dr. Dieter Sibold
Physikalisch-Technische Bundesanstalt
Q.42 - Serversysteme und Datenhaltung
QM-Verantwortlicher der Stelle IT
Bundesallee 100 
D-38116 Braunschweig
Tel:    +49-531-592-84 20
E-Mail: dieter.sibold@ptb.de


Danny Mayer <mayer@ntp.org> schrieb am 21.12.2015 23:06:51:

> Von: Danny Mayer <mayer@ntp.org>
> An: kristof.teichel@ptb.de
> Kopie: dieter.sibold@ptb.de, ntpwg@lists.ntp.org
> Datum: 21.12.2015 23:06
> Betreff: Re: [ntpwg] New Version Notification for draft-ietf-ntp-
> network-time-security-12.txt and draft-ietf-ntp-using-nts-for-ntp-03.txt
> 
> On 12/21/2015 4:43 PM, kristof.teichel@ptb.de wrote:
> > Hi Danny,
> > 
> > since one of the past versions, we have discontinued usage of the MAC
> > field and now use an additional extension field which carries exactly
> > the MAC (covering everything else).
> > If you find any fragments in the documents that say otherwise, please
> > let us know.
> > 
> > Kristof
> 
> Can you point to the description of this? I haven't seen one and we need
> a complete description of any Extension Field.
> 
> Danny
> 

_______________________________________________
ntpwg mailing list
ntpwg@lists.ntp.org
http://lists.ntp.org/listinfo/ntpwg

v2.23.0 | Report a Bug | By Email