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

Harlan Stenn <stenn@ntp.org> Wed, 23 December 2015 22:44 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 2A0BF1A88D0 for <ietfarch-ntp-archives-ahFae6za@ietfa.amsl.com>; Wed, 23 Dec 2015 14:44:16 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.91
X-Spam-Level:
X-Spam-Status: No, score=-6.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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 ekkL-dibz5iM for <ietfarch-ntp-archives-ahFae6za@ietfa.amsl.com>; Wed, 23 Dec 2015 14:44:14 -0800 (PST)
Received: from lists.ntp.org (lists.ntp.org [149.20.68.7]) by ietfa.amsl.com (Postfix) with ESMTP id A365E1A88CF for <ntp-archives-ahFae6za@lists.ietf.org>; Wed, 23 Dec 2015 14:44:14 -0800 (PST)
Received: from lists.ntp.org (lists.ntp.org [149.20.68.7]) by lists.ntp.org (Postfix) with ESMTP id 7811586DB4B for <ntp-archives-ahFae6za@lists.ietf.org>; Wed, 23 Dec 2015 22:44:14 +0000 (UTC)
X-Original-To: ntpwg@lists.ntp.org
Delivered-To: ntpwg@lists.ntp.org
Received: from stenn.ntp.org (stenn.ntp.org [IPv6:2001:4f8:fff7:1::30]) by lists.ntp.org (Postfix) with ESMTP id 6903C86D73C; Wed, 23 Dec 2015 21:26:06 +0000 (UTC)
Received: from [::1] (helo=stenn.ntp.org) by stenn.ntp.org with esmtp (Exim 4.86 (FreeBSD)) (envelope-from <stenn@stenn.ntp.org>) id 1aBqsh-000DyN-O6; Wed, 23 Dec 2015 21:23:35 +0000
From: Harlan Stenn <stenn@ntp.org>
To: mayer@ntp.org
In-reply-to: <567AC246.60901@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> <OF0AC1CCBA.2E240196-ONC1257F23.00313FBA-C1257F23.0033AC80@ptb.de> <5679639D.4010906@nwtime.org> <56799A3E.3020506@ntp.org> <OFB626AB50.8283A0AC-ONC1257F24.002B274D-C1257F24.002CE30C@ptb.de> <567AB392.8040008@ntp.org> <OF658FFA8B.3F275355-ONC1257F24.00546224-C1257F24.0054F811@ptb.de> <567AC246.60901@ntp.org>
Comments: In-reply-to Danny Mayer <mayer@ntp.org> message dated "Wed, 23 Dec 2015 10:48:22 -0500."
X-Mailer: MH-E 7.4.2; nmh 1.6; XEmacs 21.4 (patch 24)
Mime-Version: 1.0 (generated by tm-edit 1.8)
Date: Wed, 23 Dec 2015 21:23:35 +0000
Message-Id: <E1aBqsh-000DyN-O6@stenn.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, ntpwg <ntpwg-bounces+dieter.sibold=ptb.de@lists.ntp.org>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
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>

Danny Mayer writes:
> On 12/23/2015 10:28 AM, dieter.sibold@ptb.de wrote:
> > So, the intention of the MAC extension field is to replace the current
> > MAC field? And it will support the current pre-shared key authentication
> > scheme?
> 
> Yes. It will be close to the existing MAC but implemented as an
> extension field. I'm hoping to get rid of the existing MAC in favor of
> it as an extension field to give us the needed flexibility.
> 
> Danny

I'm curious to see how you will deal with backward compatibility.

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