Re: [TICTOC] Problem statement
Yaakov Stein <yaakov_s@rad.com> Wed, 30 July 2008 10:48 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 7BF6528C2D9; Wed, 30 Jul 2008 03:48:30 -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 5252028C304 for <tictoc@core3.amsl.com>; Wed, 30 Jul 2008 03:48:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.721
X-Spam-Level:
X-Spam-Status: No, score=-1.721 tagged_above=-999 required=5 tests=[AWL=-0.674, BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HTML_MESSAGE=0.001, RDNS_NONE=0.1]
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 l3t4Ne6m3foC for <tictoc@core3.amsl.com>; Wed, 30 Jul 2008 03:48:26 -0700 (PDT)
Received: from antivir2.rad.co.il (unknown [212.199.240.16]) by core3.amsl.com (Postfix) with ESMTP id A7FDC28C2DE for <tictoc@ietf.org>; Wed, 30 Jul 2008 03:48:25 -0700 (PDT)
Received: from exrad4.ad.rad.co.il ([192.114.24.47]) by antivir2.rad.co.il with ESMTP; 30 Jul 2008 13:48:39 +0300
Received: from exrad4.ad.rad.co.il ([192.114.24.47]) by exrad4.ad.rad.co.il ([192.114.24.47]) with mapi; Wed, 30 Jul 2008 13:48:39 +0300
From: Yaakov Stein <yaakov_s@rad.com>
To: "Pietilainen, Antti (NSN - FI/Espoo)" <antti.pietilainen@nsn.com>, ext Doug Arnold <darnold@symmetricom.com>, "tictoc@ietf.org" <tictoc@ietf.org>
Date: Wed, 30 Jul 2008 13:48:37 +0300
Thread-Topic: [TICTOC] Problem statement
Thread-Index: AcjyLjKUI9Aak8iLTOqFziYWJSs39AAANlegAACX2BA=
Message-ID: <424CDC689E5CEF4D9FEADE56A378D9221C727EF2@exrad4.ad.rad.co.il>
In-Reply-To: <B5535400D800AE498532700125ACF3DF3873BF@FIESEXC014.nsn-intra.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US
MIME-Version: 1.0
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="===============0357672421=="
Sender: tictoc-bounces@ietf.org
Errors-To: tictoc-bounces@ietf.org
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)