Re: [Dtls-iot] Secure Time (again)

stephen.farrell@cs.tcd.ie Tue, 11 August 2015 19:00 UTC

Return-Path: <stephen.farrell@cs.tcd.ie>
X-Original-To: dtls-iot@ietfa.amsl.com
Delivered-To: dtls-iot@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F1AA91AD248 for <dtls-iot@ietfa.amsl.com>; Tue, 11 Aug 2015 12:00:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.311
X-Spam-Level:
X-Spam-Status: No, score=-4.311 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, 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 RI3KVrEQ0a5X for <dtls-iot@ietfa.amsl.com>; Tue, 11 Aug 2015 12:00:48 -0700 (PDT)
Received: from mercury.scss.tcd.ie (mercury.scss.tcd.ie [134.226.56.6]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0E0941B29DE for <dtls-iot@ietf.org>; Tue, 11 Aug 2015 12:00:39 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mercury.scss.tcd.ie (Postfix) with ESMTP id CD4F8BE7B; Tue, 11 Aug 2015 20:00:37 +0100 (IST)
X-Virus-Scanned: Debian amavisd-new at scss.tcd.ie
Received: from mercury.scss.tcd.ie ([127.0.0.1]) by localhost (mercury.scss.tcd.ie [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id UBkqByz9-UgD; Tue, 11 Aug 2015 20:00:36 +0100 (IST)
Received: from [127.0.0.1] (unknown [86.46.29.218]) by mercury.scss.tcd.ie (Postfix) with ESMTPSA id 83EEEBE75; Tue, 11 Aug 2015 20:00:36 +0100 (IST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cs.tcd.ie; s=mail; t=1439319636; bh=xbkw9cxWqtgJ3IMy7eq7mexH+NmBQOzMacNxLl7Eypg=; h=To:Cc:From:Subject:In-Reply-To:References:Date:From; b=u4a/ji3FFM8DkkqKpAnypcpbAO4C9U437isGBt2MbnOelGkgN9wBJXrGma8wfMEat RbWeieGWoANAG6xVdunNiW2Cyyxbu2ic5LAiFkBD9SGkFOphkmWBIVyVOvQsTi8TnJ ktFPYKEEZQNK8+hMUKkOzCbTIxidT8EAtAkSiL1s=
X-Priority: 3
To: msj@nthpermutation.com
From: stephen.farrell@cs.tcd.ie
In-Reply-To: <55CA3F65.20002@nthpermutation.com>
References: <55C4D1CE.6010802@gmx.net> <55C79A90.5070900@nthpermutation.com> <55C9CFB4.5070702@gmx.net> <CABcZeBPfV9fmu_67sT0ewf+dRy5Ww4_nZUeQyhBQ9+RsHb_g2g@mail.gmail.com> <55CA0692.9000509@gmx.net> <55CA0837.5050008@nthpermutation.com> <55CA0A5C.1020304@sics.se> <55CA0AAB.8070808@gmx.net> <55CA0D93.5020209@nthpermutation.com> <55CA153C.2080001@cs.tcd.ie> <55CA3F65.20002@nthpermutation.com>
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
Date: Tue, 11 Aug 2015 19:00:34 +0000
Message-ID: <cgyrfl.nsxm50.2vaerq-qmf@mercury.scss.tcd.ie>
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/dtls-iot/RqiyXEi6r_iaOhHHEebUC4tX7xU>
Cc: dtls-iot@ietf.org
Subject: Re: [Dtls-iot] Secure Time (again)
X-BeenThere: dtls-iot@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: DTLS for IoT discussion list <dtls-iot.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dtls-iot>, <mailto:dtls-iot-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dtls-iot/>
List-Post: <mailto:dtls-iot@ietf.org>
List-Help: <mailto:dtls-iot-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dtls-iot>, <mailto:dtls-iot-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 11 Aug 2015 19:00:50 -0000


On Tue Aug 11 19:31:01 2015 GMT+0100, Michael StJohns wrote:
> On 8/11/2015 11:31 AM, Stephen Farrell wrote:
> >
> > On 11/08/15 15:58, Michael StJohns wrote:
> >> I'm wondering if it might not be a bad idea to invite Dave Mills to come
> >> to an IETF to do a presentation on secure mesh time and give us his
> >> thoughts.
> > We could and that'd be a really useful great talk if it happened. But
> > we also have an active WG on this topic. [1] Maybe starting by asking
> > there would help?
> >
> > S.
> >
> > [1] https://tools.ietf.org/wg/tictoc/
> 
> Hi Stephen -
> 
>  From the tictoc charter:
> > The Timing over IP Connections and Transfer Of Clock (TICTOC) WG is
> >      concerned with highly accurate time and frequency distribution over
> >      native IP and MPLS-enabled IP Packet Switched Networks (PSNs)
> 
> I knew about the group, but I didn't think it was a great fit for IOT 
> stuff for a lot of reasons including their desire for "highly accurate 
> time" against the IOT desire for lightweight.   As I read the charter, 
> tictoc is NTP on steroids and what we want is NTP on depressants.  :-)  
> They really aren't trying to solve a problem in a manner that would have 
> applicability to IOT.

Sure. All I meant by 'asking' was, well, asking:-) I fully agree that were work in the IETF on this topic needed we'd have to figure out how/where to best do that but the folks on that list would I guess be better informed (than me anyway:-)

S.
 

> 
> Mike
> 
> 
> _______________________________________________
> dtls-iot mailing list
> dtls-iot@ietf.org
> https://www.ietf.org/mailman/listinfo/dtls-iot
>