Re: [ntpwg] Fwd: Early Allocations for NTS drafts from the IETF NTP Working Group

Kurt Roeckx <kurt@roeckx.be> Mon, 14 March 2016 22:35 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 (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5CBA212D7BF for <ietfarch-ntp-archives-ahFae6za@ietfa.amsl.com>; Mon, 14 Mar 2016 15:35:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.9
X-Spam-Level:
X-Spam-Status: No, score=-6.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.001, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.001] autolearn=ham autolearn_force=no
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 f-vENHxXCVIf for <ietfarch-ntp-archives-ahFae6za@ietfa.amsl.com>; Mon, 14 Mar 2016 15:35:28 -0700 (PDT)
Received: from lists.ntp.org (lists.ntp.org [IPv6:2001:4f8:fff7:1::7]) by ietfa.amsl.com (Postfix) with ESMTP id 10AC112D7AA for <ntp-archives-ahFae6za@lists.ietf.org>; Mon, 14 Mar 2016 15:35:28 -0700 (PDT)
Received: from lists.ntp.org (lists.ntp.org [149.20.68.7]) by lists.ntp.org (Postfix) with ESMTP id 084B286DB71 for <ntp-archives-ahFae6za@lists.ietf.org>; Mon, 14 Mar 2016 22:35:28 +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 B029286DB1B for <ntpwg@lists.ntp.org>; Mon, 14 Mar 2016 22:35:21 +0000 (UTC)
Received: from excelsior.roeckx.be ([2a01:70:ffff:1::3]) by mail1.ntp.org with esmtps (TLSv1:AES256-SHA:256) (Exim 4.77 (FreeBSD)) (envelope-from <kurt@roeckx.be>) id 1afb56-00079V-2M for ntpwg@lists.ntp.org; Mon, 14 Mar 2016 22:35:21 +0000
Received: from intrepid.roeckx.be (localhost [127.0.0.1]) by excelsior.roeckx.be (Postfix) with ESMTP id 4AFB9A8A14CE; Mon, 14 Mar 2016 22:35:17 +0000 (UTC)
Received: by intrepid.roeckx.be (Postfix, from userid 1000) id DE3EB1FE0237; Mon, 14 Mar 2016 23:35:16 +0100 (CET)
Date: Mon, 14 Mar 2016 23:35:16 +0100
From: Kurt Roeckx <kurt@roeckx.be>
To: Hal Murray <hmurray@megapathdsl.net>
Message-ID: <20160314223516.GA8205@roeckx.be>
References: <stenn@ntp.org> <E1afaHU-000PJc-Sw@stenn.ntp.org> <20160314220644.240EC406057@ip-64-139-1-69.sjc.megapath.net>
MIME-Version: 1.0
Content-Disposition: inline
In-Reply-To: <20160314220644.240EC406057@ip-64-139-1-69.sjc.megapath.net>
User-Agent: Mutt/1.5.24 (2015-08-30)
X-SA-Exim-Connect-IP: 2a01:70:ffff:1::3
X-SA-Exim-Rcpt-To: ntpwg@lists.ntp.org
X-SA-Exim-Mail-From: kurt@roeckx.be
X-SA-Exim-Version: 4.2
X-SA-Exim-Scanned: Yes (on mail1.ntp.org)
Subject: Re: [ntpwg] Fwd: Early Allocations for NTS drafts from the IETF NTP Working Group
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: 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>

On Mon, Mar 14, 2016 at 03:06:44PM -0700, Hal Murray wrote:
>
> If I have symmetric keys, why would I bother with NTS?
>
> Is there some crypto argument about changing keys after using a
> key on X
> bytes of data?

As far as I know, it depends on how you use that key, but I would
say yes.

Even if it doesn't depend on it, it might still be a good idea to
replace it on regular basis.

> If so, what is X

I think here the answer is even more complicated.

> how does that translate to something like years of NTP traffic?

Depending on how you use the key, it might not relate to the NTP
traffic.  That is, the key used for the NTP traffic might not be
the same.

If you want more specific answers you should ask more specific
questions, including on how you intend to use it.  And you should
probably ask someone who knows more about such things.

I also have no idea if there has been a real study of the proposal
or not, and I would strongly suggest that happens.


Kurt

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