[TICTOC] FW: IEEE 1588 availability
"Laurent Montini (lmontini)" <lmontini@cisco.com> Tue, 29 July 2008 22:46 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 4DEA33A6B65; Tue, 29 Jul 2008 15:46:21 -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 461FE3A6B7B for <tictoc@core3.amsl.com>; Tue, 29 Jul 2008 15:46:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.598
X-Spam-Level:
X-Spam-Status: No, score=-6.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4]
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 fTBSBE4PybQ5 for <tictoc@core3.amsl.com>; Tue, 29 Jul 2008 15:46:12 -0700 (PDT)
Received: from ams-iport-1.cisco.com (ams-iport-1.cisco.com [144.254.224.140]) by core3.amsl.com (Postfix) with ESMTP id 8874A3A6B89 for <tictoc@ietf.org>; Tue, 29 Jul 2008 15:46:11 -0700 (PDT)
X-IronPort-AV: E=Sophos; i="4.31,274,1215388800"; d="scan'208,217"; a="15744880"
Received: from ams-dkim-2.cisco.com ([144.254.224.139]) by ams-iport-1.cisco.com with ESMTP; 29 Jul 2008 22:46:23 +0000
Received: from ams-core-1.cisco.com (ams-core-1.cisco.com [144.254.224.150]) by ams-dkim-2.cisco.com (8.12.11/8.12.11) with ESMTP id m6TMkNqS028772 for <tictoc@ietf.org>; Wed, 30 Jul 2008 00:46:23 +0200
Received: from xbh-ams-332.emea.cisco.com (xbh-ams-332.cisco.com [144.254.231.87]) by ams-core-1.cisco.com (8.13.8/8.13.8) with ESMTP id m6TMkNIG029154 for <tictoc@ietf.org>; Tue, 29 Jul 2008 22:46:23 GMT
Received: from xmb-ams-33a.cisco.com ([144.254.231.85]) by xbh-ams-332.emea.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); Wed, 30 Jul 2008 00:46:23 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Wed, 30 Jul 2008 00:46:23 +0200
Message-ID: <AF5B7FD06839284AAA2D622960544BCD05DEC78B@xmb-ams-33a.emea.cisco.com>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: IEEE 1588 availability
Thread-Index: Acjxx9Gz3pgBOCr3T8aFljo5dJA18AAAGF1g
X-Priority: 1
Priority: Urgent
Importance: high
From: "Laurent Montini (lmontini)" <lmontini@cisco.com>
To: tictoc@ietf.org
X-OriginalArrivalTime: 29 Jul 2008 22:46:23.0479 (UTC) FILETIME=[ED2C6070:01C8F1CC]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=22038; t=1217371583; x=1218235583; c=relaxed/simple; s=amsdkim2001; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=lmontini@cisco.com; z=From:=20=22Laurent=20Montini=20(lmontini)=22=20<lmontini@c isco.com> |Subject:=20FW=3A=20IEEE=201588=20availability |Sender:=20; bh=XRFrf8+X1J+j6fQPmuO0WFhjEsKD6j/RSLH9D1t6xjY=; b=T65qBszjBH8/0UMFUPSQHz+Cqm9Gzi32hfAkN9HHEQvyQUzwlL+2Cf453H DZuM4tEGuufCkob1BG/zQZNMprtuA9bMk9FIsY7nyhArW75EMHv/l42VreSx WEfRYPdQDD;
Authentication-Results: ams-dkim-2; header.From=lmontini@cisco.com; dkim=pass ( sig from cisco.com/amsdkim2001 verified; );
Subject: [TICTOC] FW: IEEE 1588 availability
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="===============1202132531=="
Sender: tictoc-bounces@ietf.org
Errors-To: tictoc-bounces@ietf.org
FYI- ________________________________ From: john_eidson@agilent.com [mailto:john_eidson@agilent.com] Sent: mardi 29 juillet 2008 23:10 To: undisclosed-recipients Subject: IEEE 1588 availability and ISPCS deadlines Importance: High To all: Several items pertaining to IEEE 1588-2008. 1. The editorial work on IEEE 1588-2008 has been completed by the IEEE editors. I am told that the final version should be on the IEEE Standards Association web site within a few weeks. The title already appears if you search on 1588 however I have been told that it is only a placeholder at this point in time. My only advice is to try periodically to see if you can actually complete the purchase process on the site. http://standards.ieee.org/ 2. The correct title of the standard is 1588-2008 IEEE Standard for a Precision Clock Synchronization Protocol for Networked Measurement and Control Systems <JavaScript:c_d(s_12,new%20Array(%221-2414Y%22,%22s_5_2_9_2%22,%22SWERow Id0=1-2414Y%22),s_13,s_14,this)> 3. Sometime later this year this standard will also appear on the site as 61588:2008 reflecting its status as an IEC standard. The IEC approval process is in process. Regards, john ____________________________________________________________ John Eidson Wrt the two drafts (draft-rodrigues-lindqvist-tictoc-req-00 and draft-stein-tictoc-modules-02), I guess the reference should be changed with PTP as the protocol, with reference to 1588-2002 as the first iteration (with PTP v1) and 1588-2008 as the newest version of "IEEE Standard for a Precision Clock Synchronization Protocol for Networked Measurement and Control Systems". For instance in draft-rodrigues-lindqvist-tictoc-req-00.txt, Annex A.3 There are two well-known protocols capable of running over a general- purpose packet network, NTP [RFC1305], and PTP [1588]. NTP is the product of the IETF, and is currently undergoing revision to version 4. PTP (a product of the IEEE 1588 Test and Measurement community) is specified in a limited first version (1588-2002), and the second version was approved recently (1588-2008). and Annex A.3.2 The information exchange component of IEEE 1588 is a protocol known as Precision Time Protocol (PTP). PTP version 1 (1588-2002) was a time transfer protocol that exclusively used a fairly crude multicast technique. It is widely anticipated that wide scale deployment of PTP will be based on PTP version 2 (1588-2008). Or IEEE Std 1588-2002 was a time transfer protocol that exclusively used a fairly crude multicast technique. It is widely anticipated that wide scale deployment of 1588 will be based on 1588-2008. The information exchange component of IEEE 1588 is a protocol known as Precision Time Protocol (PTP). Few other instances afterwards. BTW, I believe we should make the distinction between the protocol (PTP) and the clock functions that can be used with PTP and that 1588 described. This is what Annex A points out in 3.2 The information exchange component of IEEE 1588 is a protocol known as Precision Time Protocol (PTP). but that becomes confusing in other part of the text. .lm
_______________________________________________ TICTOC mailing list TICTOC@ietf.org https://www.ietf.org/mailman/listinfo/tictoc
- [TICTOC] FW: IEEE 1588 availability Laurent Montini (lmontini)