Re: [TICTOC] Problem statement

Yaakov Stein <yaakov_s@rad.com> Wed, 30 July 2008 14:22 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 546F328C35B; Wed, 30 Jul 2008 07:22:15 -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 BFDE03A67C1 for <tictoc@core3.amsl.com>; Wed, 30 Jul 2008 07:22:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.602
X-Spam-Level:
X-Spam-Status: No, score=-1.602 tagged_above=-999 required=5 tests=[AWL=-0.555, 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 ihKvAvVwbl69 for <tictoc@core3.amsl.com>; Wed, 30 Jul 2008 07:22:06 -0700 (PDT)
Received: from antivir2.rad.co.il (unknown [212.199.240.16]) by core3.amsl.com (Postfix) with ESMTP id 6346E3A6B37 for <tictoc@ietf.org>; Wed, 30 Jul 2008 07:22:03 -0700 (PDT)
Received: from exrad4.ad.rad.co.il ([192.114.24.47]) by antivir2.rad.co.il with ESMTP; 30 Jul 2008 17:21:49 +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 17:21:48 +0300
From: Yaakov Stein <yaakov_s@rad.com>
To: "Pietilainen, Antti (NSN - FI/Espoo)" <antti.pietilainen@nsn.com>, ext Doug Arnold <darnold@symmetricom.com>, ext Danny Mayer <mayer@ntp.org>, "tictoc@ietf.org" <tictoc@ietf.org>
Date: Wed, 30 Jul 2008 17:21:47 +0300
Thread-Topic: [TICTOC] Problem statement
Thread-Index: AcjyLjKUI9Aak8iLTOqFziYWJSs39AAANlegAACX2BAAAK/ngAAF9DcQ
Message-ID: <424CDC689E5CEF4D9FEADE56A378D9221C7280A5@exrad4.ad.rad.co.il>
In-Reply-To: <B5535400D800AE498532700125ACF3DF387403@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="===============0554592870=="
Sender: tictoc-bounces@ietf.org
Errors-To: tictoc-bounces@ietf.org

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?


Have a look at the autokey draft - you have until Friday to provide LC comments.

In any case, these are NOT new terms. They have been around since the original Autokey.

Y(J)S
_______________________________________________
TICTOC mailing list
TICTOC@ietf.org
https://www.ietf.org/mailman/listinfo/tictoc