From ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org Tue Oct 9 07:58:58 2012 Return-Path: X-Original-To: ietfarch-ntp-archives-ahFae6za@ietfa.amsl.com Delivered-To: ietfarch-ntp-archives-ahFae6za@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1B62E11E8097 for ; Tue, 9 Oct 2012 07:58:58 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -104.598 X-Spam-Level: X-Spam-Status: No, score=-104.598 tagged_above=-999 required=5 tests=[AWL=2.000, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, UNPARSEABLE_RELAY=0.001, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id aC8is9N6RADi for ; Tue, 9 Oct 2012 07:58:44 -0700 (PDT) Received: from lists.ntp.org (lists.ntp.org [149.20.68.7]) by ietfa.amsl.com (Postfix) with ESMTP id 792B221F84F1 for ; Tue, 9 Oct 2012 07:58:42 -0700 (PDT) Received: from lists.ntp.org (lists.ntp.org [149.20.68.7]) by lists.ntp.org (Postfix) with ESMTP id 03A0086D784 for ; Tue, 9 Oct 2012 14:58:41 +0000 (UTC) X-Original-To: ntpwg@lists.ntp.org Delivered-To: ntpwg@lists.ntp.org Received: from mail1.ntp.org (mail1.ntp.org [IPv6:2001:4f8:fff7:1::5]) by lists.ntp.org (Postfix) with ESMTP id 4CC1986D4F1 for ; Tue, 9 Oct 2012 14:58:20 +0000 (UTC) Received: from mailrelay01.rad.co.il ([62.0.23.252] helo=rad.co.il) by mail1.ntp.org with esmtps (TLSv1:AES256-SHA:256) (Exim 4.77 (FreeBSD)) (envelope-from ) id 1TLbGF-000JAa-MD for ntpwg@lists.ntp.org; Tue, 09 Oct 2012 14:58:20 +0000 Received: from Internal Mail-Server by MailRelay01 (envelope-from yaakov?s@rad.com) with AES128-SHA encrypted SMTP; 9 Oct 2012 17:09:37 +0200 Received: from EXRAD5.ad.rad.co.il ([192.114.24.28]) by EXRAD5.ad.rad.co.il ([192.114.24.28]) with mapi id 14.02.0298.004; Tue, 9 Oct 2012 16:58:05 +0200 From: Yaakov Stein To: RFC Errata System , "brian@innovationslab.net" , "mills@udel.edu" , "rdroms.ietf@gmail.com" , "brian@innovationslab.net" , "odonoghue@isoc.org" Thread-Topic: [ntpwg] [Editorial Errata Reported] RFC5906 (3348) Thread-Index: AQHNkPnLL4+Hiy3uRU28FM5xEsoQXpexNOkg Date: Tue, 9 Oct 2012 14:58:04 +0000 Message-ID: <07F7D7DED63154409F13298786A2ADC9045922BD@EXRAD5.ad.rad.co.il> References: <20120912151434.F11D1B1E003@rfc-editor.org> In-Reply-To: <20120912151434.F11D1B1E003@rfc-editor.org> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [192.115.243.62] MIME-Version: 1.0 X-Commtouch-Refid: str=0001.0A090208.50743B7E.0056,ss=1,fgs=0 X-SA-Exim-Connect-IP: 62.0.23.252 X-SA-Exim-Rcpt-To: ntpwg@lists.ntp.org X-SA-Exim-Mail-From: yaakov_s@rad.com X-SA-Exim-Version: 4.2 X-SA-Exim-Scanned: Yes (on mail1.ntp.org) Cc: "ntpwg@lists.ntp.org" , "lyh20042008@sina.com" Subject: Re: [ntpwg] [Editorial Errata Reported] RFC5906 (3348) X-BeenThere: ntpwg@lists.ntp.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: IETF Working Group for Network Time Protocol List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Errors-To: ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org Sender: ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org The changes in the naming of the status bits VAL -> CERT IFF -> VRFY AUT -> AUTO LPT -> LEAP were all made in version 02 of draft-ietf-ntp-autokey, and apparently were made inconsistently in that Section 5 was not appropriately updated. So they are all technically correct. However, I do not believe than implementations would be negatively impacted as there aren't other fields with the same names that would lead to interop problems. So I believe that according to the guidelines errata 3345, 3346, 3348, and 3349 should all be listed as "Held for Document Update" (although "Verified" is also an option). Regarding erratum 3347 I am not sure I understand the objection. Is the problem a wording one with "using the public key of the server" or with the possibility of brute-forcing the cookie or seed (which has been previously reported) ? Neither of these possibilities seems to match the note "how to decrypt?" Y(J)S _______________________________________________ ntpwg mailing list ntpwg@lists.ntp.org http://lists.ntp.org/listinfo/ntpwg From ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org Mon Oct 15 07:28:33 2012 Return-Path: X-Original-To: ietfarch-ntp-archives-ahFae6za@ietfa.amsl.com Delivered-To: ietfarch-ntp-archives-ahFae6za@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 336F521F86DE for ; Mon, 15 Oct 2012 07:28:33 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -4.598 X-Spam-Level: X-Spam-Status: No, score=-4.598 tagged_above=-999 required=5 tests=[AWL=2.000, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4] Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id mbkITN+lNChT for ; Mon, 15 Oct 2012 07:28:32 -0700 (PDT) Received: from lists.ntp.org (lists.ntp.org [149.20.68.7]) by ietfa.amsl.com (Postfix) with ESMTP id 67D1421F86D5 for ; Mon, 15 Oct 2012 07:28:32 -0700 (PDT) Received: from lists.ntp.org (lists.ntp.org [149.20.68.7]) by lists.ntp.org (Postfix) with ESMTP id F186486D76B for ; Mon, 15 Oct 2012 14:28:31 +0000 (UTC) X-Original-To: ntpwg@lists.ntp.org Delivered-To: ntpwg@lists.ntp.org Received: from mail1.ntp.org (mail1.ntp.org [IPv6:2001:4f8:fff7:1::5]) by lists.ntp.org (Postfix) with ESMTP id CAB7886D422 for ; Mon, 15 Oct 2012 14:28:13 +0000 (UTC) Received: from galiil.marvell.com ([199.203.130.254]) by mail1.ntp.org with esmtps (TLSv1:RC4-MD5:128) (Exim 4.77 (FreeBSD)) (envelope-from ) id 1TNleO-0008Ao-Pu for ntpwg@lists.ntp.org; Mon, 15 Oct 2012 14:28:13 +0000 From: Tal Mizrahi To: "ntpwg@lists.ntp.org" Date: Mon, 15 Oct 2012 16:26:56 +0200 Thread-Topic: New draft: draft-mizrahi-ntp-extension-field-00 Thread-Index: Ac2q4OrWiKP7k3aVShqb3NL9wojM9Q== Message-ID: <74470498B659FA4687F0B0018C19A89C01A0F8CAD980@IL-MB01.marvell.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US MIME-Version: 1.0 X-SA-Exim-Connect-IP: 199.203.130.254 X-SA-Exim-Rcpt-To: ntpwg@lists.ntp.org X-SA-Exim-Mail-From: talmi@marvell.com X-SA-Exim-Version: 4.2 X-SA-Exim-Scanned: Yes (on mail1.ntp.org) Subject: [ntpwg] New draft: draft-mizrahi-ntp-extension-field-00 X-BeenThere: ntpwg@lists.ntp.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: IETF Working Group for Network Time Protocol List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============1457368029695493890==" Errors-To: ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org Sender: ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org --===============1457368029695493890== Content-Language: en-US Content-Type: multipart/alternative; boundary="_000_74470498B659FA4687F0B0018C19A89C01A0F8CAD980ILMB01marve_" --_000_74470498B659FA4687F0B0018C19A89C01A0F8CAD980ILMB01marve_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Hi, This draft tries to resolve an issue that was discussed on the mailing list= a few months ago, regarding the usage of NTP extension fields in the absen= ce of a MAC. http://tools.ietf.org/html/draft-mizrahi-ntp-extension-field-00 A link to the old thread: http://lists.ntp.org/pipermail/ntpwg/2011-Decembe= r/001757.html Comments will be appreciated. Regards, Tal Mizrahi. --_000_74470498B659FA4687F0B0018C19A89C01A0F8CAD980ILMB01marve_ Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

Hi,

 

This draft= tries to resolve an issue that was discussed on the mailing list a few mon= ths ago, regarding the usage of NTP extension fields in the absence of a MA= C.

http://tools.ietf.org/html/draft-miz= rahi-ntp-extension-field-00

&nb= sp;

A link to the old thread: http://lists.nt= p.org/pipermail/ntpwg/2011-December/001757.html

 

Comments will be app= reciated.

 

Regards,

Tal Mizrahi.

 

= --_000_74470498B659FA4687F0B0018C19A89C01A0F8CAD980ILMB01marve_-- --===============1457368029695493890== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ ntpwg mailing list ntpwg@lists.ntp.org http://lists.ntp.org/listinfo/ntpwg --===============1457368029695493890==-- From ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org Mon Oct 15 08:41:49 2012 Return-Path: X-Original-To: ietfarch-ntp-archives-ahFae6za@ietfa.amsl.com Delivered-To: ietfarch-ntp-archives-ahFae6za@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 00A6C21F877A for ; Mon, 15 Oct 2012 08:41:49 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -4.998 X-Spam-Level: X-Spam-Status: No, score=-4.998 tagged_above=-999 required=5 tests=[AWL=1.600, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4] Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id wSE3LQhpV1Yv for ; Mon, 15 Oct 2012 08:41:48 -0700 (PDT) Received: from lists.ntp.org (lists.ntp.org [IPv6:2001:4f8:fff7:1::7]) by ietfa.amsl.com (Postfix) with ESMTP id 7B00421F8741 for ; Mon, 15 Oct 2012 08:41:47 -0700 (PDT) Received: from lists.ntp.org (lists.ntp.org [149.20.68.7]) by lists.ntp.org (Postfix) with ESMTP id 9C8BE86DAAE for ; Mon, 15 Oct 2012 15:41:46 +0000 (UTC) X-Original-To: ntpwg@lists.ntp.org Delivered-To: ntpwg@lists.ntp.org Received: from mail1.ntp.org (mail1.ntp.org [IPv6:2001:4f8:fff7:1::5]) by lists.ntp.org (Postfix) with ESMTP id 35F5386D422 for ; Mon, 15 Oct 2012 15:41:35 +0000 (UTC) Received: from galiil.marvell.com ([199.203.130.254]) by mail1.ntp.org with esmtps (TLSv1:RC4-MD5:128) (Exim 4.77 (FreeBSD)) (envelope-from ) id 1TNmnN-0008Wv-VX for ntpwg@lists.ntp.org; Mon, 15 Oct 2012 15:41:35 +0000 From: Tal Mizrahi To: "tictoc@ietf.org" , "ntpwg@lists.ntp.org" Date: Mon, 15 Oct 2012 17:41:02 +0200 Thread-Topic: New draft: draft-shpiner-multi-path-synchronization Thread-Index: Ac2q6tIkQE9Kshk0R6GnQ/yIUtH2/A== Message-ID: <74470498B659FA4687F0B0018C19A89C01A0F8CAD9C5@IL-MB01.marvell.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US MIME-Version: 1.0 X-SA-Exim-Connect-IP: 199.203.130.254 X-SA-Exim-Rcpt-To: ntpwg@lists.ntp.org X-SA-Exim-Mail-From: talmi@marvell.com X-SA-Exim-Version: 4.2 X-SA-Exim-Scanned: Yes (on mail1.ntp.org) Subject: [ntpwg] New draft: draft-shpiner-multi-path-synchronization X-BeenThere: ntpwg@lists.ntp.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: IETF Working Group for Network Time Protocol List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============2178882656084187874==" Errors-To: ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org Sender: ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org --===============2178882656084187874== Content-Language: en-US Content-Type: multipart/alternative; boundary="_000_74470498B659FA4687F0B0018C19A89C01A0F8CAD9C5ILMB01marve_" --_000_74470498B659FA4687F0B0018C19A89C01A0F8CAD9C5ILMB01marve_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Hi, We have posted a new draft called "Multi-Path Time Synchronization". This is an experimental draft that describes the usage of multiple concurre= nt paths between the master and slave in PTP and NTP. http://tools.ietf.org/html/draft-shpiner-multi-path-synchronization We will appreciate your feedbacks. Thanks, Tal. --_000_74470498B659FA4687F0B0018C19A89C01A0F8CAD9C5ILMB01marve_ Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

Hi,

 

We have po= sted a new draft called “Multi-Path Time Synchronization”.=

This is an experimental draft that describes= the usage of multiple concurrent paths between the master and slave in PTP= and NTP.

 

http://tools.ietf.org/html/draft-shpiner-multi-path-synch= ronization

 

We will appreciate your feedbacks.

 

Thanks,

Tal.

 

= --_000_74470498B659FA4687F0B0018C19A89C01A0F8CAD9C5ILMB01marve_-- --===============2178882656084187874== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ ntpwg mailing list ntpwg@lists.ntp.org http://lists.ntp.org/listinfo/ntpwg --===============2178882656084187874==-- From ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org Tue Oct 16 05:43:26 2012 Return-Path: X-Original-To: ietfarch-ntp-archives-ahFae6za@ietfa.amsl.com Delivered-To: ietfarch-ntp-archives-ahFae6za@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4F32821F896A for ; Tue, 16 Oct 2012 05:43:26 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -6.599 X-Spam-Level: X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4] Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id C1EYAXl7EMJB for ; Tue, 16 Oct 2012 05:43:25 -0700 (PDT) Received: from lists.ntp.org (lists.ntp.org [IPv6:2001:4f8:fff7:1::7]) by ietfa.amsl.com (Postfix) with ESMTP id E808121F894F for ; Tue, 16 Oct 2012 05:43:24 -0700 (PDT) Received: from lists.ntp.org (lists.ntp.org [149.20.68.7]) by lists.ntp.org (Postfix) with ESMTP id 160BA86D783 for ; Tue, 16 Oct 2012 12:43:24 +0000 (UTC) X-Original-To: ntpwg@lists.ntp.org Delivered-To: ntpwg@lists.ntp.org Received: from mail1.ntp.org (mail1.ntp.org [IPv6:2001:4f8:fff7:1::5]) by lists.ntp.org (Postfix) with ESMTP id E913386D422 for ; Tue, 16 Oct 2012 12:43:11 +0000 (UTC) Received: from [198.22.153.96] (helo=[10.2.64.106]) by mail1.ntp.org with esmtpsa (TLSv1:CAMELLIA256-SHA:256) (Exim 4.77 (FreeBSD)) (envelope-from ) id 1TO6UJ-000IfA-46 for ntpwg@lists.ntp.org; Tue, 16 Oct 2012 12:43:11 +0000 Message-ID: <507D5652.20600@ntp.org> Date: Tue, 16 Oct 2012 08:42:58 -0400 From: Danny Mayer User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:15.0) Gecko/20120824 Thunderbird/15.0 MIME-Version: 1.0 To: NTP Working Group X-Enigmail-Version: 1.4.4 X-SA-Exim-Connect-IP: 198.22.153.96 X-SA-Exim-Rcpt-To: ntpwg@lists.ntp.org X-SA-Exim-Mail-From: mayer@ntp.org X-SA-Exim-Version: 4.2 X-SA-Exim-Scanned: Yes (on mail1.ntp.org) Subject: [ntpwg] Time Crystals X-BeenThere: ntpwg@lists.ntp.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: IETF Working Group for Network Time Protocol List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Errors-To: ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org Sender: ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org People may be interested in this article on a new idea for clocks. You probably need a physics background to understand most of this but it's worth reading. http://physics.aps.org/articles/v5/116 Danny _______________________________________________ ntpwg mailing list ntpwg@lists.ntp.org http://lists.ntp.org/listinfo/ntpwg From ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org Tue Oct 16 09:52:16 2012 Return-Path: X-Original-To: ietfarch-ntp-archives-ahFae6za@ietfa.amsl.com Delivered-To: ietfarch-ntp-archives-ahFae6za@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3BC1221F89E0 for ; Tue, 16 Oct 2012 09:52:16 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -4.621 X-Spam-Level: X-Spam-Status: No, score=-4.621 tagged_above=-999 required=5 tests=[AWL=1.978, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4] Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id pzK5QQKVZ8ZH for ; Tue, 16 Oct 2012 09:52:15 -0700 (PDT) Received: from lists.ntp.org (lists.ntp.org [IPv6:2001:4f8:fff7:1::7]) by ietfa.amsl.com (Postfix) with ESMTP id 2AECF21F8A06 for ; Tue, 16 Oct 2012 09:52:15 -0700 (PDT) Received: from lists.ntp.org (lists.ntp.org [149.20.68.7]) by lists.ntp.org (Postfix) with ESMTP id 8BE0586D769 for ; Tue, 16 Oct 2012 16:52:14 +0000 (UTC) X-Original-To: ntpwg@lists.ntp.org Delivered-To: ntpwg@lists.ntp.org Received: from mail1.ntp.org (mail1.ntp.org [IPv6:2001:4f8:fff7:1::5]) by lists.ntp.org (Postfix) with ESMTP id BDF1586D422 for ; Tue, 16 Oct 2012 16:51:56 +0000 (UTC) Received: from elasmtp-dupuy.atl.sa.earthlink.net ([209.86.89.62]) by mail1.ntp.org with esmtp (Exim 4.77 (FreeBSD)) (envelope-from ) id 1TOAN1-000KdG-8C for ntpwg@lists.ntp.org; Tue, 16 Oct 2012 16:51:56 +0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=dk20050327; d=earthlink.net; b=hXZ8K2acGGvAj7uwQjhX9a+3bVH5XmhpPrwKSFiE2YaeBy0qNgWrCshphUcROhAu; h=Received:Message-ID:Date:From:User-Agent:MIME-Version:To:Subject:References:In-Reply-To:Content-Type:Content-Transfer-Encoding:X-ELNK-Trace:X-Originating-IP; Received: from [67.180.133.21] (helo=[192.168.15.2]) by elasmtp-dupuy.atl.sa.earthlink.net with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.67) (envelope-from ) id 1TOAMv-0005S5-5c for ntpwg@lists.ntp.org; Tue, 16 Oct 2012 12:51:49 -0400 Message-ID: <507D90A4.9080509@earthlink.net> Date: Tue, 16 Oct 2012 09:51:48 -0700 From: tglassey User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:13.0) Gecko/20120614 Thunderbird/13.0.1 MIME-Version: 1.0 To: ntpwg@lists.ntp.org References: <507D5652.20600@ntp.org> In-Reply-To: <507D5652.20600@ntp.org> X-ELNK-Trace: 01b7a7e171bdf5911aa676d7e74259b7b3291a7d08dfec7951e0dd08b3cc3ba4e6d2f9beda9c5246350badd9bab72f9c350badd9bab72f9c350badd9bab72f9c X-Originating-IP: 67.180.133.21 X-SA-Exim-Connect-IP: 209.86.89.62 X-SA-Exim-Rcpt-To: ntpwg@lists.ntp.org X-SA-Exim-Mail-From: tglassey@earthlink.net X-SA-Exim-Version: 4.2 X-SA-Exim-Scanned: Yes (on mail1.ntp.org) Subject: Re: [ntpwg] Time Crystals X-BeenThere: ntpwg@lists.ntp.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: IETF Working Group for Network Time Protocol List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="us-ascii"; Format="flowed" Errors-To: ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org Sender: ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org On 10/16/2012 5:42 AM, Danny Mayer wrote: > People may be interested in this article on a new idea for clocks. You > probably need a physics background to understand most of this but it's > worth reading. > > http://physics.aps.org/articles/v5/116 Danny this is a great article on how to create a time-scale instance from the physics standpoint - just wait until a crystal oscillator with a gravity pump becomes possible... Todd > Danny > _______________________________________________ > ntpwg mailing list > ntpwg@lists.ntp.org > http://lists.ntp.org/listinfo/ntpwg > > > ----- > No virus found in this message. > Checked by AVG - www.avg.com > Version: 2013.0.2741 / Virus Database: 2614/5834 - Release Date: 10/15/12 > > -- Regards TSG "Ex-Cruce-Leo" //Confidential Mailing - Please destroy this if you are not the intended recipient. _______________________________________________ ntpwg mailing list ntpwg@lists.ntp.org http://lists.ntp.org/listinfo/ntpwg From ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org Mon Oct 22 07:47:39 2012 Return-Path: X-Original-To: ietfarch-ntp-archives-ahFae6za@ietfa.amsl.com Delivered-To: ietfarch-ntp-archives-ahFae6za@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6122E21F8B79 for ; Mon, 22 Oct 2012 07:47:39 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -5.17 X-Spam-Level: X-Spam-Status: No, score=-5.17 tagged_above=-999 required=5 tests=[AWL=1.429, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4] Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id pjvUD+aQcmyl for ; Mon, 22 Oct 2012 07:47:38 -0700 (PDT) Received: from lists.ntp.org (lists.ntp.org [IPv6:2001:4f8:fff7:1::7]) by ietfa.amsl.com (Postfix) with ESMTP id 21B4F21F8BAC for ; Mon, 22 Oct 2012 07:47:36 -0700 (PDT) Received: from lists.ntp.org (lists.ntp.org [149.20.68.7]) by lists.ntp.org (Postfix) with ESMTP id 4433986D9BE for ; Mon, 22 Oct 2012 14:47:35 +0000 (UTC) X-Original-To: ntpwg@lists.ntp.org Delivered-To: ntpwg@lists.ntp.org Received: from mail1.ntp.org (mail1.ntp.org [IPv6:2001:4f8:fff7:1::5]) by lists.ntp.org (Postfix) with ESMTP id 95FEB86D333 for ; Mon, 22 Oct 2012 14:47:15 +0000 (UTC) Received: from galiil.marvell.com ([199.203.130.254]) by mail1.ntp.org with esmtps (TLSv1:RC4-MD5:128) (Exim 4.77 (FreeBSD)) (envelope-from ) id 1TQJHe-000GP5-83 for ntpwg@lists.ntp.org; Mon, 22 Oct 2012 14:47:15 +0000 From: Tal Mizrahi To: "draft-ietf-tictoc-1588overmpls@tools.ietf.org" Date: Mon, 22 Oct 2012 16:47:01 +0200 Thread-Topic: [TICTOC] I-D Action: draft-ietf-tictoc-1588overmpls-03.txt Thread-Index: Ac2wLz6IX3wAdPM6Rli0vli80YML5wANHcIg Message-ID: <74470498B659FA4687F0B0018C19A89C01A0F8D26CAB@IL-MB01.marvell.com> References: <20121022082804.12835.73453.idtracker@ietfa.amsl.com> In-Reply-To: <20121022082804.12835.73453.idtracker@ietfa.amsl.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US MIME-Version: 1.0 X-SA-Exim-Connect-IP: 199.203.130.254 X-SA-Exim-Rcpt-To: ntpwg@lists.ntp.org X-SA-Exim-Mail-From: talmi@marvell.com X-SA-Exim-Version: 4.2 X-SA-Exim-Scanned: Yes (on mail1.ntp.org) Cc: "ntpwg@lists.ntp.org" , "tictoc@ietf.org" Subject: Re: [ntpwg] [TICTOC] I-D Action: draft-ietf-tictoc-1588overmpls-03.txt X-BeenThere: ntpwg@lists.ntp.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: IETF Working Group for Network Time Protocol List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Errors-To: ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org Sender: ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org Hi Shahram et al. What is the motivation for adding NTP to this draft? Are we planning to define something similar to a correctionField in NTP? Regards, Tal. -----Original Message----- From: tictoc-bounces@ietf.org [mailto:tictoc-bounces@ietf.org] On Behalf Of internet-drafts@ietf.org Sent: Monday, October 22, 2012 10:28 AM To: i-d-announce@ietf.org Cc: tictoc@ietf.org Subject: [TICTOC] I-D Action: draft-ietf-tictoc-1588overmpls-03.txt A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Timing over IP Connection and Transfer of Clock Working Group of the IETF. Title : Transporting Timing messages over MPLS Networks Author(s) : Shahram Davari Amit Oren Manav Bhatia Peter Roberts Laurent Montini Filename : draft-ietf-tictoc-1588overmpls-03.txt Pages : 36 Date : 2012-10-22 Abstract: This document defines the method for transporting Timing messages such as PTP and NTP over an MPLS network. The method allows for the easy identification of these PDUs at the port level to allow for port level processing of these PDUs in both LERs and LSRs. The basic idea is to transport Timing messages inside dedicated MPLS LSPs. These LSPs only carry timing messages and possibly Control and Management packets, but they do not carry customer traffic. Two methods for transporting Timing messages over MPLS are defined. The first method is to transport Timing messages directly over the dedicated MPLS LSP via UDP/IP encapsulation, which is suitable for MPLS networks. The second method is to transport Timing messages inside a PW via Ethernet encapsulation, which is suitable for both MPLS and MPLS-TP networks. The IETF datatracker status page for this draft is: https://datatracker.ietf.org/doc/draft-ietf-tictoc-1588overmpls There's also a htmlized version available at: http://tools.ietf.org/html/draft-ietf-tictoc-1588overmpls-03 A diff from the previous version is available at: http://www.ietf.org/rfcdiff?url2=draft-ietf-tictoc-1588overmpls-03 Internet-Drafts are also available by anonymous FTP at: ftp://ftp.ietf.org/internet-drafts/ _______________________________________________ TICTOC mailing list TICTOC@ietf.org https://www.ietf.org/mailman/listinfo/tictoc _______________________________________________ ntpwg mailing list ntpwg@lists.ntp.org http://lists.ntp.org/listinfo/ntpwg From ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org Mon Oct 22 13:35:55 2012 Return-Path: X-Original-To: ietfarch-ntp-archives-ahFae6za@ietfa.amsl.com Delivered-To: ietfarch-ntp-archives-ahFae6za@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1F8BA21F849A for ; Mon, 22 Oct 2012 13:35:55 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -5.265 X-Spam-Level: X-Spam-Status: No, score=-5.265 tagged_above=-999 required=5 tests=[AWL=1.334, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4] Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id pPe0LK9iWLAD for ; Mon, 22 Oct 2012 13:35:54 -0700 (PDT) Received: from lists.ntp.org (lists.ntp.org [149.20.68.7]) by ietfa.amsl.com (Postfix) with ESMTP id 0ABCE21F8480 for ; Mon, 22 Oct 2012 13:35:51 -0700 (PDT) Received: from lists.ntp.org (lists.ntp.org [149.20.68.7]) by lists.ntp.org (Postfix) with ESMTP id 59ABB86DADC for ; Mon, 22 Oct 2012 20:35:50 +0000 (UTC) X-Original-To: ntpwg@lists.ntp.org Delivered-To: ntpwg@lists.ntp.org Received: from mail1.ntp.org (mail1.ntp.org [IPv6:2001:4f8:fff7:1::5]) by lists.ntp.org (Postfix) with ESMTP id 09F4586D333 for ; Mon, 22 Oct 2012 20:35:39 +0000 (UTC) Received: from galiil.marvell.com ([199.203.130.254]) by mail1.ntp.org with esmtps (TLSv1:RC4-MD5:128) (Exim 4.77 (FreeBSD)) (envelope-from ) id 1TQOim-0009RJ-N8 for ntpwg@lists.ntp.org; Mon, 22 Oct 2012 20:35:39 +0000 From: Tal Mizrahi To: Shahram Davari , "draft-ietf-tictoc-1588overmpls@tools.ietf.org" Date: Mon, 22 Oct 2012 22:35:28 +0200 Thread-Topic: [TICTOC] I-D Action: draft-ietf-tictoc-1588overmpls-03.txt Thread-Index: AQHNsC8+pgP7aJ4X+k2ew0adKz8PKJfF3SqA//+rRECAAD4keQ== Message-ID: <74470498B659FA4687F0B0018C19A89C01A0F842952E@IL-MB01.marvell.com> References: <20121022082804.12835.73453.idtracker@ietfa.amsl.com> <74470498B659FA4687F0B0018C19A89C01A0F8D26CAB@IL-MB01.marvell.com>, <4A6CE49E6084B141B15C0713B8993F281BD0E582@SJEXCHMB12.corp.ad.broadcom.com> In-Reply-To: <4A6CE49E6084B141B15C0713B8993F281BD0E582@SJEXCHMB12.corp.ad.broadcom.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US MIME-Version: 1.0 X-SA-Exim-Connect-IP: 199.203.130.254 X-SA-Exim-Rcpt-To: ntpwg@lists.ntp.org X-SA-Exim-Mail-From: talmi@marvell.com X-SA-Exim-Version: 4.2 X-SA-Exim-Scanned: Yes (on mail1.ntp.org) Cc: "ntpwg@lists.ntp.org" , "tictoc@ietf.org" Subject: Re: [ntpwg] [TICTOC] I-D Action: draft-ietf-tictoc-1588overmpls-03.txt X-BeenThere: ntpwg@lists.ntp.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: IETF Working Group for Network Time Protocol List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Errors-To: ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org Sender: ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org Hi Shahram, Thanks for the prompt response. I would suggest to add some text to explain the scope of this draft in the context of NTP, i.e., your explanation below. A question to the WG chairs: if NTP TCs are indeed on the agenda, wouldn't it be best to define these entities in parallel to the MPLS draft? It seems more natural, and more likely to produce a coherent mechanism. Thanks, Tal. ________________________________________ From: Shahram Davari [davari@broadcom.com] Sent: Monday, October 22, 2012 6:46 PM To: Tal Mizrahi; draft-ietf-tictoc-1588overmpls@tools.ietf.org Cc: tictoc@ietf.org; ntpwg@lists.ntp.org Subject: RE: [TICTOC] I-D Action: draft-ietf-tictoc-1588overmpls-03.txt Hi Tal, If you recall the Area director asked for generalizing this draft to NTP and other possible future Timing methods such as a Shim header that can carry Timing. I know NTP does not have TC, but IETF may add TC in future. Also on the egress LER the timing Label (defined in the draft) may be used as an indicator to sample ToD at the port level. Thanks Shahram -----Original Message----- From: Tal Mizrahi [mailto:talmi@marvell.com] Sent: Monday, October 22, 2012 7:47 AM To: draft-ietf-tictoc-1588overmpls@tools.ietf.org Cc: tictoc@ietf.org; ntpwg@lists.ntp.org Subject: RE: [TICTOC] I-D Action: draft-ietf-tictoc-1588overmpls-03.txt Hi Shahram et al. What is the motivation for adding NTP to this draft? Are we planning to define something similar to a correctionField in NTP? Regards, Tal. -----Original Message----- From: tictoc-bounces@ietf.org [mailto:tictoc-bounces@ietf.org] On Behalf Of internet-drafts@ietf.org Sent: Monday, October 22, 2012 10:28 AM To: i-d-announce@ietf.org Cc: tictoc@ietf.org Subject: [TICTOC] I-D Action: draft-ietf-tictoc-1588overmpls-03.txt A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Timing over IP Connection and Transfer of Clock Working Group of the IETF. Title : Transporting Timing messages over MPLS Networks Author(s) : Shahram Davari Amit Oren Manav Bhatia Peter Roberts Laurent Montini Filename : draft-ietf-tictoc-1588overmpls-03.txt Pages : 36 Date : 2012-10-22 Abstract: This document defines the method for transporting Timing messages such as PTP and NTP over an MPLS network. The method allows for the easy identification of these PDUs at the port level to allow for port level processing of these PDUs in both LERs and LSRs. The basic idea is to transport Timing messages inside dedicated MPLS LSPs. These LSPs only carry timing messages and possibly Control and Management packets, but they do not carry customer traffic. Two methods for transporting Timing messages over MPLS are defined. The first method is to transport Timing messages directly over the dedicated MPLS LSP via UDP/IP encapsulation, which is suitable for MPLS networks. The second method is to transport Timing messages inside a PW via Ethernet encapsulation, which is suitable for both MPLS and MPLS-TP networks. The IETF datatracker status page for this draft is: https://datatracker.ietf.org/doc/draft-ietf-tictoc-1588overmpls There's also a htmlized version available at: http://tools.ietf.org/html/draft-ietf-tictoc-1588overmpls-03 A diff from the previous version is available at: http://www.ietf.org/rfcdiff?url2=draft-ietf-tictoc-1588overmpls-03 Internet-Drafts are also available by anonymous FTP at: ftp://ftp.ietf.org/internet-drafts/ _______________________________________________ TICTOC mailing list TICTOC@ietf.org https://www.ietf.org/mailman/listinfo/tictoc _______________________________________________ ntpwg mailing list ntpwg@lists.ntp.org http://lists.ntp.org/listinfo/ntpwg From ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org Tue Oct 23 08:11:21 2012 Return-Path: X-Original-To: ietfarch-ntp-archives-ahFae6za@ietfa.amsl.com Delivered-To: ietfarch-ntp-archives-ahFae6za@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5DF7211E80AE for ; Tue, 23 Oct 2012 08:11:21 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -105.099 X-Spam-Level: X-Spam-Status: No, score=-105.099 tagged_above=-999 required=5 tests=[AWL=1.500, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id J7aZXWpd98KD for ; Tue, 23 Oct 2012 08:11:20 -0700 (PDT) Received: from lists.ntp.org (lists.ntp.org [IPv6:2001:4f8:fff7:1::7]) by ietfa.amsl.com (Postfix) with ESMTP id 76B9721F868B for ; Tue, 23 Oct 2012 08:11:20 -0700 (PDT) Received: from lists.ntp.org (lists.ntp.org [149.20.68.7]) by lists.ntp.org (Postfix) with ESMTP id 9F1AA86DAB4 for ; Tue, 23 Oct 2012 15:11:19 +0000 (UTC) X-Original-To: ntpwg@lists.ntp.org Delivered-To: ntpwg@lists.ntp.org Received: from mail1.ntp.org (mail1.ntp.org [IPv6:2001:4f8:fff7:1::5]) by lists.ntp.org (Postfix) with ESMTP id 863E986D333 for ; Tue, 23 Oct 2012 15:10:55 +0000 (UTC) Received: from mail-oa0-f41.google.com ([209.85.219.41]) by mail1.ntp.org with esmtps (TLSv1:RC4-SHA:128) (Exim 4.77 (FreeBSD)) (envelope-from ) id 1TQg82-000L1d-BX for ntpwg@lists.ntp.org; Tue, 23 Oct 2012 15:10:55 +0000 Received: by mail-oa0-f41.google.com with SMTP id k14so4492428oag.14 for ; Tue, 23 Oct 2012 08:10:44 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=sender:message-id:date:from:reply-to:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=5BT0rd211KdCnCjra5t4j46D0iTv8pV8utIVh2dULP0=; b=GvdL160TOWE4AqoFcBYtdJofCvibwxqvBuYPHyxI8dd8SRiEEF9ASJWWTv+JzisN6C Mb4bZaIgDCgnhz7rmZuhUoO1/rPeQqIUaYB+yj0Ibab7KpONgEAvaSvgA9fdIoEYW7Kw dssVkdNhBlVybivb8zTKGDGEkd+b5SW2A3lZVc0BswMJTkmKXQl9/IwDIhCmLjH76TG6 QqUGHC9WbtzJJIBKTX0/7HF8G7NuEgnLuodRom3Ix6ifOQ3UPsspE7UfdRj7XVuEdEBQ wweWUpaeDj4+nW9H41fjmWr/qJx7boM43WGsqLHcRosQ0LCrgY4Inmp/dKPVWg/OLh8I sZHw== Received: by 10.60.171.164 with SMTP id av4mr11327648oec.59.1351005044554; Tue, 23 Oct 2012 08:10:44 -0700 (PDT) Received: from dhcp-223-97.meetings.nanog.org (dhcp-223-97.meetings.nanog.org. [199.187.223.97]) by mx.google.com with ESMTPS id ig3sm12971335obb.0.2012.10.23.08.10.42 (version=SSLv3 cipher=OTHER); Tue, 23 Oct 2012 08:10:43 -0700 (PDT) Message-ID: <5086B371.6020700@pobox.com> Date: Tue, 23 Oct 2012 11:10:41 -0400 From: Karen O'Donoghue User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:15.0) Gecko/20120907 Thunderbird/15.0.1 MIME-Version: 1.0 To: Tal Mizrahi References: <20121022082804.12835.73453.idtracker@ietfa.amsl.com> <74470498B659FA4687F0B0018C19A89C01A0F8D26CAB@IL-MB01.marvell.com>, <4A6CE49E6084B141B15C0713B8993F281BD0E582@SJEXCHMB12.corp.ad.broadcom.com> <74470498B659FA4687F0B0018C19A89C01A0F842952E@IL-MB01.marvell.com> In-Reply-To: <74470498B659FA4687F0B0018C19A89C01A0F842952E@IL-MB01.marvell.com> X-SA-Exim-Connect-IP: 209.85.219.41 X-SA-Exim-Rcpt-To: ntpwg@lists.ntp.org X-SA-Exim-Mail-From: kodonog@gmail.com X-SA-Exim-Version: 4.2 X-SA-Exim-Scanned: Yes (on mail1.ntp.org) Cc: "ntpwg@lists.ntp.org" , Shahram Davari , "tictoc@ietf.org" , "draft-ietf-tictoc-1588overmpls@tools.ietf.org" Subject: Re: [ntpwg] [TICTOC] I-D Action: draft-ietf-tictoc-1588overmpls-03.txt X-BeenThere: ntpwg@lists.ntp.org X-Mailman-Version: 2.1.14 Precedence: list Reply-To: kodonog@pobox.com List-Id: IETF Working Group for Network Time Protocol List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="us-ascii"; Format="flowed" Errors-To: ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org Sender: ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org Tal, It is true that developing an NTP option in parallel would potentially be more efficient and coherent; however, we have thus far had no volunteers to work on that document. The current approach is flexible enough to support PTP, NTP, and possibly other timing methods which is a generalization of the solution originally proposed. We welcome proposals and volunteer document editors who wish to pursue the NTP option. Regards, Karen On 10/22/12 4:35 PM, Tal Mizrahi wrote: > Hi Shahram, > > Thanks for the prompt response. > I would suggest to add some text to explain the scope of this draft in the context of NTP, i.e., your explanation below. > > A question to the WG chairs: if NTP TCs are indeed on the agenda, wouldn't it be best to define these entities in parallel to the MPLS draft? It seems more natural, and more likely to produce a coherent mechanism. > > Thanks, > Tal. > > ________________________________________ > From: Shahram Davari [davari@broadcom.com] > Sent: Monday, October 22, 2012 6:46 PM > To: Tal Mizrahi; draft-ietf-tictoc-1588overmpls@tools.ietf.org > Cc: tictoc@ietf.org; ntpwg@lists.ntp.org > Subject: RE: [TICTOC] I-D Action: draft-ietf-tictoc-1588overmpls-03.txt > > Hi Tal, > > If you recall the Area director asked for generalizing this draft to NTP and other possible future Timing methods such as a Shim header that can carry Timing. I know NTP does not have TC, but IETF may add TC in future. Also on the egress LER the timing Label (defined in the draft) may be used as an indicator to sample ToD at the port level. > > Thanks > Shahram > > -----Original Message----- > From: Tal Mizrahi [mailto:talmi@marvell.com] > Sent: Monday, October 22, 2012 7:47 AM > To: draft-ietf-tictoc-1588overmpls@tools.ietf.org > Cc: tictoc@ietf.org; ntpwg@lists.ntp.org > Subject: RE: [TICTOC] I-D Action: draft-ietf-tictoc-1588overmpls-03.txt > > Hi Shahram et al. > > What is the motivation for adding NTP to this draft? > Are we planning to define something similar to a correctionField in NTP? > > Regards, > Tal. > > > -----Original Message----- > From: tictoc-bounces@ietf.org [mailto:tictoc-bounces@ietf.org] On Behalf Of internet-drafts@ietf.org > Sent: Monday, October 22, 2012 10:28 AM > To: i-d-announce@ietf.org > Cc: tictoc@ietf.org > Subject: [TICTOC] I-D Action: draft-ietf-tictoc-1588overmpls-03.txt > > > A New Internet-Draft is available from the on-line Internet-Drafts directories. > This draft is a work item of the Timing over IP Connection and Transfer of Clock Working Group of the IETF. > > Title : Transporting Timing messages over MPLS Networks > Author(s) : Shahram Davari > Amit Oren > Manav Bhatia > Peter Roberts > Laurent Montini > Filename : draft-ietf-tictoc-1588overmpls-03.txt > Pages : 36 > Date : 2012-10-22 > > Abstract: > This document defines the method for transporting Timing messages > such as PTP and NTP over an MPLS network. The method allows for the > easy identification of these PDUs at the port level to allow for port > level processing of these PDUs in both LERs and LSRs. > > The basic idea is to transport Timing messages inside dedicated MPLS > LSPs. These LSPs only carry timing messages and possibly Control and > Management packets, but they do not carry customer traffic. > > Two methods for transporting Timing messages over MPLS are defined. > The first method is to transport Timing messages directly over the > dedicated MPLS LSP via UDP/IP encapsulation, which is suitable for > MPLS networks. The second method is to transport Timing messages > inside a PW via Ethernet encapsulation, which is suitable for both > MPLS and MPLS-TP networks. > > > The IETF datatracker status page for this draft is: > https://datatracker.ietf.org/doc/draft-ietf-tictoc-1588overmpls > > There's also a htmlized version available at: > http://tools.ietf.org/html/draft-ietf-tictoc-1588overmpls-03 > > A diff from the previous version is available at: > http://www.ietf.org/rfcdiff?url2=draft-ietf-tictoc-1588overmpls-03 > > > Internet-Drafts are also available by anonymous FTP at: > ftp://ftp.ietf.org/internet-drafts/ > > _______________________________________________ > TICTOC mailing list > TICTOC@ietf.org > https://www.ietf.org/mailman/listinfo/tictoc > _______________________________________________ > ntpwg mailing list > ntpwg@lists.ntp.org > http://lists.ntp.org/listinfo/ntpwg _______________________________________________ ntpwg mailing list ntpwg@lists.ntp.org http://lists.ntp.org/listinfo/ntpwg From ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org Wed Oct 24 10:25:47 2012 Return-Path: X-Original-To: ietfarch-ntp-archives-ahFae6za@ietfa.amsl.com Delivered-To: ietfarch-ntp-archives-ahFae6za@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2502221F851E for ; Wed, 24 Oct 2012 10:25:47 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -104.932 X-Spam-Level: X-Spam-Status: No, score=-104.932 tagged_above=-999 required=5 tests=[AWL=1.667, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ngcLT2NLZ1e0 for ; Wed, 24 Oct 2012 10:25:46 -0700 (PDT) Received: from lists.ntp.org (lists.ntp.org [IPv6:2001:4f8:fff7:1::7]) by ietfa.amsl.com (Postfix) with ESMTP id F02E221F8529 for ; Wed, 24 Oct 2012 10:25:45 -0700 (PDT) Received: from lists.ntp.org (lists.ntp.org [149.20.68.7]) by lists.ntp.org (Postfix) with ESMTP id 3B90386D83B for ; Wed, 24 Oct 2012 17:25:45 +0000 (UTC) X-Original-To: ntpwg@lists.ntp.org Delivered-To: ntpwg@lists.ntp.org Received: from mail1.ntp.org (mail1.ntp.org [IPv6:2001:4f8:fff7:1::5]) by lists.ntp.org (Postfix) with ESMTP id D065686D422 for ; Wed, 24 Oct 2012 17:25:27 +0000 (UTC) Received: from smtp138.dfw.emailsrvr.com ([67.192.241.138]) by mail1.ntp.org with esmtps (TLSv1:AES256-SHA:256) (Exim 4.77 (FreeBSD)) (envelope-from ) id 1TR4ho-0008Xs-M6 for ntpwg@lists.ntp.org; Wed, 24 Oct 2012 17:25:27 +0000 Received: from localhost (localhost.localdomain [127.0.0.1]) by smtp13.relay.dfw1a.emailsrvr.com (SMTP Server) with ESMTP id BBAA8502A4; Wed, 24 Oct 2012 13:25:18 -0400 (EDT) X-Virus-Scanned: OK Received: by smtp13.relay.dfw1a.emailsrvr.com (Authenticated sender: odonoghue-AT-isoc.org) with ESMTPSA id 82579502A5; Wed, 24 Oct 2012 13:25:18 -0400 (EDT) Message-ID: <5088247E.4070600@isoc.org> Date: Wed, 24 Oct 2012 13:25:18 -0400 From: Karen O'Donoghue Organization: ISOC User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:16.0) Gecko/20121010 Thunderbird/16.0.1 MIME-Version: 1.0 To: "tictoc@ietf.org" , NTP Working Group X-SA-Exim-Connect-IP: 67.192.241.138 X-SA-Exim-Rcpt-To: ntpwg@lists.ntp.org X-SA-Exim-Mail-From: odonoghue@isoc.org X-SA-Exim-Version: 4.2 X-SA-Exim-Scanned: Yes (on mail1.ntp.org) Subject: [ntpwg] draft agenda for tictoc/ntp joint meeting at IETF 85 X-BeenThere: ntpwg@lists.ntp.org X-Mailman-Version: 2.1.14 Precedence: list Reply-To: odonoghue@isoc.org List-Id: IETF Working Group for Network Time Protocol List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="us-ascii"; Format="flowed" Errors-To: ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org Sender: ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org Folks, Below is a draft agenda for the upcoming meeting. Comments, corrections, and additions are welcome. Note this is a fairly long agenda so discussion on the mailing lists in advance would be helpful. Thanks, Karen ***** DRAFT ***** TICTOC WG - IETF 85 Agenda ========================== Thursday, 8 November 2012, 1300-1500 EDT (1800 - 2000 UTC) 1. Administrivia and Agenda Bashing (Chairs) 2. ITU-T SG15/Q13 update (??) 3. IEEE 1588 update (O'Donoghue) 4. Transporting Timing messages over MPLS Networks draft-ietf-tictoc-1588overmpls-03 Note: this document has been generalized to all timing messages. The filename will be changed to reflect this generalization in the next version (Shahram Davari) 5. Status of additional drafts in other working groups to support timing over MPLS. (Manav Bhatia) 6. Precision Time Protocol Version 2 (PTPv2) Management Information Base draft-ietf-tictoc-ptp-mib-03 (Vinay Shankarkumar) 7. TICTOC Security Requirements draft-ietf-tictoc-security-requirements-03 (Tal Mizrahi) 8. Proposal for an enterprise profile for IEEE 1588 (Doug Arnold) 9. Multi-Path Time Synchronization draft-shpiner-multi-path-synchronization-00 (Tal Mizrahi) 10. Autokey Version 2 Specification draft-sibold-autokey-00 (Dieter Sibold) 11. Using NTP Extension Field without Authentication draft-mizrahi-ntp-extension-field-00 (Tal Mizrahi) 12. Control Messages Protocol for Use with NTPv4 (expired: draft-odonoghue-ntpv4-control-01) 13. Securing Model-C Inter-Provider VPLS L2 VPNs with Label Hopping and TicToc draft-mjsraman-l2vpn-vpls-tictoc-label-hop-01 (if time permits) 14. Securing Model-C Inter-Provider VPNs with Label Hopping and TicToc draft-mjsraman-l3vpn-tictoc-label-hop-01 (if time permits) 15. AOB 16. Wrap-up / Way Forward _______________________________________________ ntpwg mailing list ntpwg@lists.ntp.org http://lists.ntp.org/listinfo/ntpwg From ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org Wed Oct 31 04:29:46 2012 Return-Path: X-Original-To: ietfarch-ntp-archives-ahFae6za@ietfa.amsl.com Delivered-To: ietfarch-ntp-archives-ahFae6za@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 42F7B21F880D for ; Wed, 31 Oct 2012 04:29:46 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -5.099 X-Spam-Level: X-Spam-Status: No, score=-5.099 tagged_above=-999 required=5 tests=[AWL=1.500, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4] Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5HYbbjl+Vn-1 for ; Wed, 31 Oct 2012 04:29:45 -0700 (PDT) Received: from lists.ntp.org (lists.ntp.org [149.20.68.7]) by ietfa.amsl.com (Postfix) with ESMTP id 43C7321F879E for ; Wed, 31 Oct 2012 04:29:42 -0700 (PDT) Received: from lists.ntp.org (lists.ntp.org [149.20.68.7]) by lists.ntp.org (Postfix) with ESMTP id A290786D77E for ; Wed, 31 Oct 2012 11:29:41 +0000 (UTC) X-Original-To: ntpwg@lists.ntp.org Delivered-To: ntpwg@lists.ntp.org Received: from mail1.ntp.org (mail1.ntp.org [IPv6:2001:4f8:fff7:1::5]) by lists.ntp.org (Postfix) with ESMTP id 7256386D33D for ; Tue, 30 Oct 2012 22:41:55 +0000 (UTC) Received: from ch1ehsobe001.messaging.microsoft.com ([216.32.181.181] helo=ch1outboundpool.messaging.microsoft.com) by mail1.ntp.org with esmtps (TLSv1:AES128-SHA:128) (Exim 4.77 (FreeBSD)) (envelope-from ) id 1TTKVN-0006tv-6H for ntpwg@lists.ntp.org; Tue, 30 Oct 2012 22:41:55 +0000 Received: from mail223-ch1-R.bigfish.com (10.43.68.227) by CH1EHSOBE003.bigfish.com (10.43.70.53) with Microsoft SMTP Server id 14.1.225.23; Tue, 30 Oct 2012 22:41:46 +0000 Received: from mail223-ch1 (localhost [127.0.0.1]) by mail223-ch1-R.bigfish.com (Postfix) with ESMTP id A91202207B1; Tue, 30 Oct 2012 22:41:46 +0000 (UTC) X-Forefront-Antispam-Report: CIP:209.226.172.12; KIP:(null); UIP:(null); IPV:NLI; H:ottsrv0014.microsemi.net; RD:none; EFVD:NLI X-SpamScore: -27 X-BigFish: VS-27(zz9371I4015I179cMzz1202h1d1ah1d2ahzz1033IL17326ah8275dhz2dh668h839h944hd25hf0ah1220h1288h12a5h12a9h12bdh137ah13b6h1441h14ddh1504h1537h153bh1155h) Received: from mail223-ch1 (localhost.localdomain [127.0.0.1]) by mail223-ch1 (MessageSwitch) id 1351636904230698_18565; Tue, 30 Oct 2012 22:41:44 +0000 (UTC) Received: from CH1EHSMHS042.bigfish.com (snatpool3.int.messaging.microsoft.com [10.43.68.228]) by mail223-ch1.bigfish.com (Postfix) with ESMTP id 366DC4A005C; Tue, 30 Oct 2012 22:41:44 +0000 (UTC) Received: from ottsrv0014.microsemi.net (209.226.172.12) by CH1EHSMHS042.bigfish.com (10.43.69.251) with Microsoft SMTP Server id 14.1.225.23; Tue, 30 Oct 2012 22:41:41 +0000 Received: from ottsrv0015.microsemi.net ([134.199.15.151]) by ottsrv0014.microsemi.net with Microsoft SMTPSVC(6.0.3790.4675); Tue, 30 Oct 2012 18:42:05 -0400 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-Class: urn:content-classes:message MIME-Version: 1.0 Date: Tue, 30 Oct 2012 18:40:48 -0400 Message-ID: <64683B4805156847B0ED373DAB3057CAD965B3@ottsrv0015.microsemi.net> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: [TICTOC] New draft: draft-shpiner-multi-path-synchronization Thread-Index: Ac2q6tIkQE9Kshk0R6GnQ/yIUtH2/ALzrABQ References: <74470498B659FA4687F0B0018C19A89C01A0F8CAD9C5@IL-MB01.marvell.com> From: "Meyer, Peter" To: Tal Mizrahi X-OriginalArrivalTime: 30 Oct 2012 22:42:05.0341 (UTC) FILETIME=[C93F24D0:01CDB6EF] X-OriginatorOrg: microsemi.com X-SA-Exim-Connect-IP: 216.32.181.181 X-SA-Exim-Rcpt-To: ntpwg@lists.ntp.org X-SA-Exim-Mail-From: Peter.Meyer@microsemi.com X-SA-Exim-Version: 4.2 X-SA-Exim-Scanned: Yes (on mail1.ntp.org) X-Mailman-Approved-At: Wed, 31 Oct 2012 11:29:04 +0000 Cc: ntpwg@lists.ntp.org, tictoc@ietf.org Subject: Re: [ntpwg] [TICTOC] New draft: draft-shpiner-multi-path-synchronization X-BeenThere: ntpwg@lists.ntp.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: IETF Working Group for Network Time Protocol List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Errors-To: ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org Sender: ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org Hi Tal et al, Interesting. Looks like a useful idea. For the IEEE 1588 option, there are a bunch of items that need some more thought as to how it would be compliant or compatible with IEEE 1588-2008. I didn't review the NTP option. I didn't comment on the Two-way MPPTP until I am better understanding the One-way MPPTP option. + [SLAVEDIV] is not a publicly available document + Section 5 mandates using unicast, which would put the clock operation as unicast negotiation for all message types. I think there is important distinction between unicast (not standard) and unicast negotiation (standard), as contract negotiation uses the transport layer (e.g. IP address) as the connection identifier, rather than the PTP clock id. This is perhaps something that should be fixed in the next revision of IEEE 1588. + 5.1.1. One-Way MPPTP Synchronization Message Exchange The one-way MPPTP message exchange procedure is as follows. o Each one-way MPPTP clock has a fixed set of N IP addresses and N corresponding clockIdentities . One of the IP addresses and clockIdentity values are defined as the clock primary identity. PGM> This makes N clocks in the domain per network element. It is not clear the determination of which one is the "primary". There is no clear indication how the N clocks talk to each other, if at all. o The BMC algorithm determines the master. PGM> This BMCA runs per individual port per clock, so you now have N best masters? Could end up with N Grandmasters if the local network element is the best in the network. o Every one-way MPPTP port that is not in the 'slave' state (i.e., either a master or a clock that has just joined the network) periodically sends Announce messages using its primary identity. PGM> Announce messages are negotiated by request of the remote entity. It is unclear why the master would request Announce service from the 'slave' port, unless this other clock also is updated to follow a new specification. o A one-way MPPTP clock that is in the 'slave' state periodically transmits a set of N Announce messages using its N identities, while a clock in the 'master' state only transmits Announce messages using its primary identity. PGM> From previous bullet is unclear how the model has Announce per port AND Announce per clock. The Announce is negotiated by request of the remote entity. o The master periodically sends unicast Sync messages from its primary identity address to each of the slaves identified by the sourcePortIdentity and IP address. PGM> Sync messages are controlled by unicast negotiation contracts. These are established exclusively by IP address in IEEE 1588-2008 (for IP transport layer mapping Annex D & E). o The slave, upon receiving a Sync message, identifies its path according to the destination IP address. In response to the Sync message the slave sends a Delay_Req unicast message to the primary identity of the master. This message is sent using the slave identity corresponding to the path the Sync was received through. PGM> There is no strict requirement to send a Delay_Req upon receiving a Sync (there are a couple schemes allowed in IEEE 1588-2008). With uni-cast negotiation it may also be possible to run asymmetric rates for Sync & Delay_Req. o The master, in response to a Delay_Req message from the slave, responds with a Delay_Resp message using the IP address and sourcePortIdentity from the Delay_Req message. o Upon receiving the Delay_Resp message, the slave identifies the path using the destination IP address and the requestingPortIdentity. The slave can then compute the corresponding path delay and the offset from the master. Regards, Peter From: tictoc-bounces@ietf.org [mailto:tictoc-bounces@ietf.org] On Behalf Of Tal Mizrahi Sent: October 15, 2012 11:41 AM To: tictoc@ietf.org; ntpwg@lists.ntp.org Subject: [TICTOC] New draft: draft-shpiner-multi-path-synchronization Hi, We have posted a new draft called "Multi-Path Time Synchronization". This is an experimental draft that describes the usage of multiple concurrent paths between the master and slave in PTP and NTP. http://tools.ietf.org/html/draft-shpiner-multi-path-synchronization We will appreciate your feedbacks. Thanks, Tal. _______________________________________________ ntpwg mailing list ntpwg@lists.ntp.org http://lists.ntp.org/listinfo/ntpwg From ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org Wed Oct 31 04:42:30 2012 Return-Path: X-Original-To: ietfarch-ntp-archives-ahFae6za@ietfa.amsl.com Delivered-To: ietfarch-ntp-archives-ahFae6za@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8519021F87B0 for ; Wed, 31 Oct 2012 04:42:30 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -4.599 X-Spam-Level: X-Spam-Status: No, score=-4.599 tagged_above=-999 required=5 tests=[AWL=2.000, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4] Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id pH0aI3nrdCES for ; Wed, 31 Oct 2012 04:42:27 -0700 (PDT) Received: from lists.ntp.org (lists.ntp.org [IPv6:2001:4f8:fff7:1::7]) by ietfa.amsl.com (Postfix) with ESMTP id 4E43A21F87A7 for ; Wed, 31 Oct 2012 04:42:27 -0700 (PDT) Received: from lists.ntp.org (lists.ntp.org [149.20.68.7]) by lists.ntp.org (Postfix) with ESMTP id BEDEE86D55E for ; Wed, 31 Oct 2012 11:42:25 +0000 (UTC) X-Original-To: ntpwg@lists.ntp.org Delivered-To: ntpwg@lists.ntp.org Received: from mail1.ntp.org (mail1.ntp.org [IPv6:2001:4f8:fff7:1::5]) by lists.ntp.org (Postfix) with ESMTP id EB1E286D33D for ; Wed, 31 Oct 2012 11:41:47 +0000 (UTC) Received: from galiil.marvell.com ([199.203.130.254]) by mail1.ntp.org with esmtps (TLSv1:RC4-MD5:128) (Exim 4.77 (FreeBSD)) (envelope-from ) id 1TTWg5-000FS5-7L for ntpwg@lists.ntp.org; Wed, 31 Oct 2012 11:41:47 +0000 From: Tal Mizrahi To: "Meyer, Peter" Date: Wed, 31 Oct 2012 13:40:34 +0200 Thread-Topic: [TICTOC] New draft: draft-shpiner-multi-path-synchronization Thread-Index: Ac2q6tIkQE9Kshk0R6GnQ/yIUtH2/ALzrABQAB30uZA= Message-ID: <74470498B659FA4687F0B0018C19A89C01A0F8DA8EA3@IL-MB01.marvell.com> References: <74470498B659FA4687F0B0018C19A89C01A0F8CAD9C5@IL-MB01.marvell.com> <64683B4805156847B0ED373DAB3057CAD965B3@ottsrv0015.microsemi.net> In-Reply-To: <64683B4805156847B0ED373DAB3057CAD965B3@ottsrv0015.microsemi.net> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US MIME-Version: 1.0 X-SA-Exim-Connect-IP: 199.203.130.254 X-SA-Exim-Rcpt-To: ntpwg@lists.ntp.org X-SA-Exim-Mail-From: talmi@marvell.com X-SA-Exim-Version: 4.2 X-SA-Exim-Scanned: Yes (on mail1.ntp.org) Cc: "ntpwg@lists.ntp.org" , "tictoc@ietf.org" Subject: Re: [ntpwg] [TICTOC] New draft: draft-shpiner-multi-path-synchronization X-BeenThere: ntpwg@lists.ntp.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: IETF Working Group for Network Time Protocol List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Errors-To: ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org Sender: ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org Hi Peter, Thanks for your comments. You have made a few comments regarding the usage of Announce messages and unicast negotiation. This is good feedback, and in the next draft we will clarify these two aspects. See some comments inline, marked with [TM]. Thanks. Tal. -----Original Message----- From: Meyer, Peter [mailto:Peter.Meyer@microsemi.com] Sent: Wednesday, October 31, 2012 12:41 AM To: Tal Mizrahi Cc: tictoc@ietf.org; ntpwg@lists.ntp.org Subject: RE: [TICTOC] New draft: draft-shpiner-multi-path-synchronization Hi Tal et al, Interesting. Looks like a useful idea. For the IEEE 1588 option, there are a bunch of items that need some more thought as to how it would be compliant or compatible with IEEE 1588-2008. I didn't review the NTP option. I didn't comment on the Two-way MPPTP until I am better understanding the One-way MPPTP option. + [SLAVEDIV] is not a publicly available document [TM] It is available from IEEE Xplore. If you do not have access please contact me offline. + Section 5 mandates using unicast, which would put the clock operation as unicast negotiation for all message types. I think there is important distinction between unicast (not standard) and unicast negotiation (standard), as contract negotiation uses the transport layer (e.g. IP address) as the connection identifier, rather than the PTP clock id. This is perhaps something that should be fixed in the next revision of IEEE 1588. [TM] We probably need to add some details about the negotiation. But anyway, the fact that the IP address is used as the identifier does not conflict with the assumption in this subsection, which is that each clockIdentity uses a different IP address. + 5.1.1. One-Way MPPTP Synchronization Message Exchange The one-way MPPTP message exchange procedure is as follows. o Each one-way MPPTP clock has a fixed set of N IP addresses and N corresponding clockIdentities . One of the IP addresses and clockIdentity values are defined as the clock primary identity. PGM> This makes N clocks in the domain per network element. It is not clear the determination of which one is the "primary". There is no clear indication how the N clocks talk to each other, if at all. [TM] Each clock arbitrarily chooses one of its identities as the "primary" one. The "primary" identity is the one that takes part in the BMCA and may become a master. If the BMCA determines that the "primary" identity is a master, then only the "primary" identity is active, while the other identities do not send/receive any PTP messages. We will clarify this in the next draft. o The BMC algorithm determines the master. PGM> This BMCA runs per individual port per clock, so you now have N best masters? Could end up with N Grandmasters if the local network element is the best in the network. [TM] Only the primary clock takes part in the BMCA, which prevents us from getting N grandmasters in this case. Again, we will clarify this. o Every one-way MPPTP port that is not in the 'slave' state (i.e., either a master or a clock that has just joined the network) periodically sends Announce messages using its primary identity. PGM> Announce messages are negotiated by request of the remote entity. It is unclear why the master would request Announce service from the 'slave' port, unless this other clock also is updated to follow a new specification. o A one-way MPPTP clock that is in the 'slave' state periodically transmits a set of N Announce messages using its N identities, while a clock in the 'master' state only transmits Announce messages using its primary identity. PGM> From previous bullet is unclear how the model has Announce per port AND Announce per clock. The Announce is negotiated by request of the remote entity. o The master periodically sends unicast Sync messages from its primary identity address to each of the slaves identified by the sourcePortIdentity and IP address. PGM> Sync messages are controlled by unicast negotiation contracts. These are established exclusively by IP address in IEEE 1588-2008 (for IP transport layer mapping Annex D & E). o The slave, upon receiving a Sync message, identifies its path according to the destination IP address. In response to the Sync message the slave sends a Delay_Req unicast message to the primary identity of the master. This message is sent using the slave identity corresponding to the path the Sync was received through. PGM> There is no strict requirement to send a Delay_Req upon receiving a Sync (there are a couple schemes allowed in IEEE 1588-2008). With uni-cast negotiation it may also be possible to run asymmetric rates for Sync & Delay_Req. [TM] Right, we are not implying that it is mandatory to send a Delay_Req for each Sync, so we will rephrase this. o The master, in response to a Delay_Req message from the slave, responds with a Delay_Resp message using the IP address and sourcePortIdentity from the Delay_Req message. o Upon receiving the Delay_Resp message, the slave identifies the path using the destination IP address and the requestingPortIdentity. The slave can then compute the corresponding path delay and the offset from the master. Regards, Peter From: tictoc-bounces@ietf.org [mailto:tictoc-bounces@ietf.org] On Behalf Of Tal Mizrahi Sent: October 15, 2012 11:41 AM To: tictoc@ietf.org; ntpwg@lists.ntp.org Subject: [TICTOC] New draft: draft-shpiner-multi-path-synchronization Hi, We have posted a new draft called "Multi-Path Time Synchronization". This is an experimental draft that describes the usage of multiple concurrent paths between the master and slave in PTP and NTP. http://tools.ietf.org/html/draft-shpiner-multi-path-synchronization We will appreciate your feedbacks. Thanks, Tal. _______________________________________________ ntpwg mailing list ntpwg@lists.ntp.org http://lists.ntp.org/listinfo/ntpwg