Re: [TICTOC] Problem statement
"Greg Dowd" <GDowd@symmetricom.com> Wed, 30 July 2008 12:20 UTC
Return-Path: <tictoc-bounces@ietf.org>
X-Original-To: tictoc-archive@optimus.ietf.org
Delivered-To: ietfarch-tictoc-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 4CDAB3A68C1; Wed, 30 Jul 2008 05:20:37 -0700 (PDT)
X-Original-To: tictoc@core3.amsl.com
Delivered-To: tictoc@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id C0C5E3A68C4 for <tictoc@core3.amsl.com>; Wed, 30 Jul 2008 05:20:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.264
X-Spam-Level:
X-Spam-Status: No, score=-2.264 tagged_above=-999 required=5 tests=[AWL=-0.000, BAYES_00=-2.599, HTML_MESSAGE=0.001, IP_NOT_FRIENDLY=0.334]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id O8KFKNUc8uXX for <tictoc@core3.amsl.com>; Wed, 30 Jul 2008 05:20:34 -0700 (PDT)
Received: from mail4.symmetricom.com (mail4.symmetricom.com [69.25.98.6]) by core3.amsl.com (Postfix) with SMTP id 806153A68A6 for <tictoc@ietf.org>; Wed, 30 Jul 2008 05:20:34 -0700 (PDT)
X-ASG-Debug-ID: 1217420430-358300cc0000-4wH9i1
X-Barracuda-URL: http://192.168.10.95:80/cgi-bin/mark.cgi
Received: from sjowa.symmetricom.com (localhost [127.0.0.1]) by mail4.symmetricom.com (Spam Firewall) with ESMTP id D3C2F57DFCA; Wed, 30 Jul 2008 05:20:30 -0700 (PDT)
Received: from sjowa.symmetricom.com ([192.168.10.41]) by mail4.symmetricom.com with ESMTP id jTMJbu0KCHBY72c0; Wed, 30 Jul 2008 05:20:30 -0700 (PDT)
X-ASG-Whitelist: Client
Received: from sjmail2.symmetricom.com ([192.168.10.66]) by sjowa.symmetricom.com with Microsoft SMTPSVC(6.0.3790.3959); Wed, 30 Jul 2008 05:20:30 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
X-ASG-Orig-Subj: RE: [TICTOC] Problem statement
Date: Wed, 30 Jul 2008 05:20:31 -0700
Message-ID: <CB45EB047BD43041BF1F4CC7D6DB21BF0137B2D6@sjmail2.symmetricom.com>
In-Reply-To: <B5535400D800AE498532700125ACF3DF387403@FIESEXC014.nsn-intra.net>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [TICTOC] Problem statement
Thread-Index: AcjyLjKUI9Aak8iLTOqFziYWJSs39AAANlegAACX2BAAAK/ngAACjhwg
References: <B5535400D800AE498532700125ACF3DF3873BF@FIESEXC014.nsn-intra.net><424CDC689E5CEF4D9FEADE56A378D9221C727EF2@exrad4.ad.rad.co.il> <B5535400D800AE498532700125ACF3DF387403@FIESEXC014.nsn-intra.net>
From: Greg Dowd <GDowd@symmetricom.com>
To: "Pietilainen, Antti (NSN - FI/Espoo)" <antti.pietilainen@nsn.com>, ext Yaakov Stein <yaakov_s@rad.com>, Doug Arnold <darnold@symmetricom.com>, ext Danny Mayer <mayer@ntp.org>, tictoc@ietf.org
X-OriginalArrivalTime: 30 Jul 2008 12:20:30.0523 (UTC) FILETIME=[A847C8B0:01C8F23E]
X-Barracuda-Connect: UNKNOWN[192.168.10.41]
X-Barracuda-Start-Time: 1217420430
X-Barracuda-Virus-Scanned: by Symmetricom Spam Gateway at symmetricom.com
Subject: Re: [TICTOC] Problem statement
X-BeenThere: tictoc@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Timing over IP Connection and Transfer of Clock BOF <tictoc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/tictoc>, <mailto:tictoc-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/tictoc>
List-Post: <mailto:tictoc@ietf.org>
List-Help: <mailto:tictoc-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tictoc>, <mailto:tictoc-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0613654261=="
Sender: tictoc-bounces@ietf.org
Errors-To: tictoc-bounces@ietf.org
http://www.eecis.udel.edu/~mills/ntp.html and Mill's book on NTP are excellent sources for material on security in the world of time transfer. Greg Dowd gdowd at symmetricom dot com (antispam format) Symmetricom, Inc. www.symmetricom.com <blocked::http://www.symmetricom.com/> "Everything should be made as simple as possible, but no simpler" Albert Einstein ________________________________ From: tictoc-bounces@ietf.org [mailto:tictoc-bounces@ietf.org] On Behalf Of Pietilainen, Antti (NSN - FI/Espoo) Sent: Wednesday, July 30, 2008 4:30 AM To: ext Yaakov Stein; Doug Arnold; ext Danny Mayer; tictoc@ietf.org Subject: Re: [TICTOC] Problem statement Yaakov, What you said may be true but it does not change the validity of my statement: It is incorrect to claim that IEEE 1588 committee did not come up with a security mechanism. Thus, my previous comment still applies. By the way, "zero-knowledge proof of time", "breaking the loop of authentication requiring time", and "time requiring authentication" are all new terms. At least I did not find any hits in Google except the two to the tictoc minutes from Paris. There must be some references that describe these problems. Could you provide a pointer to a reference (or pointers) for the group so that the validity of the terms could be reviewed? Quick comment for Danny Mayer. IETF is one of the organizations that may define IEEE 1588 profiles. One should check, though, how free hands IEEE 1588 profile makers have. Antti ________________________________ From: ext Yaakov Stein [mailto:yaakov_s@rad.com] Sent: 30 July, 2008 13:49 To: Pietilainen, Antti (NSN - FI/Espoo); ext Doug Arnold; tictoc@ietf.org Subject: RE: [TICTOC] Problem statement Antii We could discuss the annex at some later meeting, however, the annex you mention does not address the main concerns of a security mechanism for timing, namely zero-knowledge proof of time and breaking the loop of authentication requiring time and time requiring authentication (see the relevant slide from the interim meeting report). Y(J)S ________________________________ From: tictoc-bounces@ietf.org [mailto:tictoc-bounces@ietf.org] On Behalf Of Pietilainen, Antti (NSN - FI/Espoo) Sent: Wednesday, July 30, 2008 1:45 PM To: ext Doug Arnold; tictoc@ietf.org Subject: Re: [TICTOC] Problem statement Doug, You said that the IEEE 1588 committee failed to come up with a security mechanism. However, it did come up with one in the form of a security protocol annex. It is informative and experimental but it was overviewed by NIST security experts. Consequently, I propose to re-word your statement so that the existing security annex is credited somehow. I also propose to start possible security work by seeing how far one can go with the existing annex. You might include Ron Cohen as cc so he has the option to comment. Antti ________________________________ From: tictoc-bounces@ietf.org [mailto:tictoc-bounces@ietf.org] On Behalf Of ext Doug Arnold Sent: 30 July, 2008 13:23 To: tictoc@ietf.org Subject: [TICTOC] Problem statement Comment on TICTOC problem statement: draft-bryant-tictoc-probstat-02.txt The need for precise time and frequency transfer in engineered LANs is gernally met by IEEE 1588-2008. Such networks include high speed printing presses and other industrial automation applications, power utility substation sync, etc. However the 1588 committee failed to come up with a security mechanism. So secure time and frequency transfer in engineered LANs could be one of the charters for TICTOC. //Doug
_______________________________________________ TICTOC mailing list TICTOC@ietf.org https://www.ietf.org/mailman/listinfo/tictoc
- [TICTOC] Problem statement Doug Arnold
- Re: [TICTOC] Problem statement Pietilainen, Antti (NSN - FI/Espoo)
- Re: [TICTOC] Problem statement Yaakov Stein
- Re: [TICTOC] Problem statement Danny Mayer
- Re: [TICTOC] Problem statement Pietilainen, Antti (NSN - FI/Espoo)
- Re: [TICTOC] Problem statement Greg Dowd
- Re: [TICTOC] Problem statement Doug Arnold
- Re: [TICTOC] Problem statement Yaakov Stein
- Re: [TICTOC] Problem statement Pietilainen, Antti (NSN - FI/Espoo)