
From internet-drafts@ietf.org  Mon Oct 21 13:36:23 2013
Return-Path: <internet-drafts@ietf.org>
X-Original-To: tictoc@ietfa.amsl.com
Delivered-To: tictoc@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D245C11E835A; Mon, 21 Oct 2013 13:36:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.575
X-Spam-Level: 
X-Spam-Status: No, score=-102.575 tagged_above=-999 required=5 tests=[AWL=0.025, BAYES_00=-2.599, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id MAzcn0B43jNv; Mon, 21 Oct 2013 13:36:19 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id D8B5E11E82B4; Mon, 21 Oct 2013 13:36:14 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
From: internet-drafts@ietf.org
To: i-d-announce@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 4.80.p3
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20131021203613.32548.47406.idtracker@ietfa.amsl.com>
Date: Mon, 21 Oct 2013 13:36:13 -0700
Cc: tictoc@ietf.org
Subject: [TICTOC] I-D Action: draft-ietf-tictoc-security-requirements-06.txt
X-BeenThere: tictoc@ietf.org
X-Mailman-Version: 2.1.12
List-Id: Timing over IP Connection and Transfer of Clock BOF <tictoc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tictoc>, <mailto:tictoc-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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>
X-List-Received-Date: Mon, 21 Oct 2013 20:36:23 -0000

A New Internet-Draft is available from the on-line Internet-Drafts director=
ies.
 This draft is a work item of the Timing over IP Connection and Transfer of=
 Clock Working Group of the IETF.

	Title           : Security Requirements of Time Protocols in Packet Switch=
ed Networks
	Author(s)       : Tal Mizrahi
	Filename        : draft-ietf-tictoc-security-requirements-06.txt
	Pages           : 33
	Date            : 2013-10-21

Abstract:
   As time and frequency distribution protocols are becoming
   increasingly common and widely deployed, concern about their exposure
   to various security threats is increasing. This document defines a
   set of security requirements for time protocols, focusing on the
   Precision Time Protocol (PTP) and the Network Time Protocol (NTP).
   This document also discusses the security impacts of time protocol
   practices, the performance implications of external security
   practices on time protocols and the dependencies between other
   security services and time synchronization.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-tictoc-security-requirements

There's also a htmlized version available at:
http://tools.ietf.org/html/draft-ietf-tictoc-security-requirements-06

A diff from the previous version is available at:
http://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-tictoc-security-requirements-=
06


Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/


From talmi@marvell.com  Mon Oct 21 22:51:44 2013
Return-Path: <talmi@marvell.com>
X-Original-To: tictoc@ietfa.amsl.com
Delivered-To: tictoc@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F20E211E8140 for <tictoc@ietfa.amsl.com>; Mon, 21 Oct 2013 22:51:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.987
X-Spam-Level: 
X-Spam-Status: No, score=-2.987 tagged_above=-999 required=5 tests=[AWL=-0.722, BAYES_00=-2.599, HTML_MESSAGE=0.001, IP_NOT_FRIENDLY=0.334]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id GwgQIu3Q72Sk for <tictoc@ietfa.amsl.com>; Mon, 21 Oct 2013 22:51:39 -0700 (PDT)
Received: from mx0b-0016f401.pphosted.com (mx0b-0016f401.pphosted.com [67.231.156.173]) by ietfa.amsl.com (Postfix) with ESMTP id 99BE211E845E for <tictoc@ietf.org>; Mon, 21 Oct 2013 22:51:38 -0700 (PDT)
Received: from pps.filterd (m0045851.ppops.net [127.0.0.1]) by mx0b-0016f401.pphosted.com (8.14.5/8.14.5) with SMTP id r9M5pcTw010354 for <tictoc@ietf.org>; Mon, 21 Oct 2013 22:51:38 -0700
Received: from sc-owa01.marvell.com ([199.233.58.136]) by mx0b-0016f401.pphosted.com with ESMTP id 1fm29nruj9-9 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT) for <tictoc@ietf.org>; Mon, 21 Oct 2013 22:51:37 -0700
Received: from YK-HUB01.marvell.com (10.4.102.51) by sc-owa01.marvell.com (10.93.76.21) with Microsoft SMTP Server (TLS) id 8.3.213.0; Mon, 21 Oct 2013 22:51:33 -0700
Received: from IL-MB01.marvell.com ([10.4.102.53]) by YK-HUB01.marvell.com ([10.4.102.51]) with mapi; Tue, 22 Oct 2013 07:51:30 +0200
From: Tal Mizrahi <talmi@marvell.com>
To: "tictoc@ietf.org" <tictoc@ietf.org>
Date: Tue, 22 Oct 2013 08:51:29 +0200
Thread-Topic: New version of draft-ietf-tictoc-security-requirements
Thread-Index: Ac7O6mQOhjYn/CIeSRSD7rYgGJnQLw==
Message-ID: <74470498B659FA4687F0B0018C19A89C01B87D7A42AA@IL-MB01.marvell.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: multipart/alternative; boundary="_000_74470498B659FA4687F0B0018C19A89C01B87D7A42AAILMB01marve_"
MIME-Version: 1.0
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:5.10.8794, 1.0.431, 0.0.0000 definitions=2013-10-22_02:2013-10-22, 2013-10-22, 1970-01-01 signatures=0
X-Proofpoint-Spam-Details: rule=outbound_notspam policy=outbound score=0 spamscore=0 suspectscore=0 phishscore=1 adultscore=1 bulkscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=7.0.1-1305240000 definitions=main-1310210166
Subject: [TICTOC] New version of draft-ietf-tictoc-security-requirements
X-BeenThere: tictoc@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Timing over IP Connection and Transfer of Clock BOF <tictoc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tictoc>, <mailto:tictoc-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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>
X-List-Received-Date: Tue, 22 Oct 2013 05:51:44 -0000

--_000_74470498B659FA4687F0B0018C19A89C01B87D7A42AAILMB01marve_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Hi,

I submitted a slightly updated version of the draft, mainly to avoid expira=
tion.
No significant changes compared to the previous version.

http://tools.ietf.org/html/draft-ietf-tictoc-security-requirements

Thanks,
Tal.


--_000_74470498B659FA4687F0B0018C19A89C01B87D7A42AAILMB01marve_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40"><head><META HTTP-EQUIV=3D"Content-Type" CONTENT=
=3D"text/html; charset=3Dus-ascii"><meta name=3DGenerator content=3D"Micros=
oft Word 14 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-family:"Calibri","sans-serif";}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.25in 1.0in 1.25in;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]--></head><body lang=3DEN-US link=3Dblue vli=
nk=3Dpurple><div class=3DWordSection1><p class=3DMsoNormal>Hi,<o:p></o:p></=
p><p class=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3DMsoNormal>I submitte=
d a slightly updated version of the draft, mainly to avoid expiration.<o:p>=
</o:p></p><p class=3DMsoNormal>No significant changes compared to the previ=
ous version.<o:p></o:p></p><p class=3DMsoNormal><o:p>&nbsp;</o:p></p><p cla=
ss=3DMsoNormal><a href=3D"http://tools.ietf.org/html/draft-ietf-tictoc-secu=
rity-requirements">http://tools.ietf.org/html/draft-ietf-tictoc-security-re=
quirements</a><o:p></o:p></p><p class=3DMsoNormal><o:p>&nbsp;</o:p></p><p c=
lass=3DMsoNormal>Thanks,<o:p></o:p></p><p class=3DMsoNormal><span style=3D'=
font-size:10.0pt;font-family:"Arial","sans-serif"'>Tal.<o:p></o:p></span></=
p><p class=3DMsoNormal><o:p>&nbsp;</o:p></p></div></body></html>=

--_000_74470498B659FA4687F0B0018C19A89C01B87D7A42AAILMB01marve_--

From doug.arnold2@gmail.com  Thu Oct 24 17:35:19 2013
Return-Path: <doug.arnold2@gmail.com>
X-Original-To: tictoc@ietfa.amsl.com
Delivered-To: tictoc@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0D0F911E821E for <tictoc@ietfa.amsl.com>; Thu, 24 Oct 2013 17:35:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.118
X-Spam-Level: 
X-Spam-Status: No, score=-0.118 tagged_above=-999 required=5 tests=[BAYES_20=-0.74, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id upLVAbTtdRhU for <tictoc@ietfa.amsl.com>; Thu, 24 Oct 2013 17:35:15 -0700 (PDT)
Received: from mail-ie0-x232.google.com (mail-ie0-x232.google.com [IPv6:2607:f8b0:4001:c03::232]) by ietfa.amsl.com (Postfix) with ESMTP id 7C55411E825B for <tictoc@ietf.org>; Thu, 24 Oct 2013 17:35:11 -0700 (PDT)
Received: by mail-ie0-f178.google.com with SMTP id x13so5203522ief.37 for <tictoc@ietf.org>; Thu, 24 Oct 2013 17:35:10 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:date:message-id:subject:from:to:content-type; bh=6atcCxYPdpTgXLhGcqHUhHwdUvL8YpOEImFlTo6W7Gk=; b=iIVPePSyxgVRflgLI4Hc5oSkL8HcTBT/vVi3fgcY0TXtFRNiyqL0AaDx/u1J7BXVZm RnKzSSvp/fAthnkxnjHgQDNVutXXO5aHIOAYAPhMU+o+2yS3Jeaqym/HVFBGUQTjm1BW 43V3W3MoT5zaiwwKOox04AYBh1JhUP12jJ5scop0diWclTFvDeCvm2k6T+oFsT3US3GN GaXCOUBTZ6NdtzS6DFFrMJZjGPlpvxnKVrdIHpBaZL9hsAAiwltxxlEw491PAOwr4xII QtPoDz3GXdmjEK4H9Tro29KYU9LoKt/lNPf1AYA9xQTwMwOo3q6SvHVHQNwpoeHaU4xi YwMA==
MIME-Version: 1.0
X-Received: by 10.43.152.78 with SMTP id kv14mr3405780icc.13.1382661310733; Thu, 24 Oct 2013 17:35:10 -0700 (PDT)
Sender: doug.arnold2@gmail.com
Received: by 10.64.59.196 with HTTP; Thu, 24 Oct 2013 17:35:10 -0700 (PDT)
Date: Thu, 24 Oct 2013 17:35:10 -0700
X-Google-Sender-Auth: jna9T1qZeI4joVTK1TD43G0RlPE
Message-ID: <CACQYgzFmOtFY+Td0jZMyykeZ17KwAuCc+LY+C2be_UPgZKh9GA@mail.gmail.com>
From: Douglas Arnold <doug.arnold@meinberg-usa.com>
To: "tictoc@ietf.org" <tictoc@ietf.org>
Content-Type: multipart/mixed; boundary=001a11c30a844563a804e985ec3e
X-Mailman-Approved-At: Thu, 24 Oct 2013 21:16:17 -0700
Subject: [TICTOC] Enterprise Profile
X-BeenThere: tictoc@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Timing over IP Connection and Transfer of Clock BOF <tictoc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tictoc>, <mailto:tictoc-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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>
X-List-Received-Date: Fri, 25 Oct 2013 00:35:19 -0000

--001a11c30a844563a804e985ec3e
Content-Type: multipart/alternative; boundary=001a11c30a8445639a04e985ec3c

--001a11c30a8445639a04e985ec3c
Content-Type: text/plain; charset=ISO-8859-1

Hello Everyone,

Attached is an updated version of the Enterprise profile.  Sorry I missed
the upload deadline for  the Vancouver meeting.  If you get a chance to
look at it before then I will be there and would love to discuss it.

Summary of changes:

I also changed the TLV format to fit the latest proposal in the 1588
revision.

I added a statement about not going into the master state unless one had a
current UTC offset.

I added to the TLV fields to indicate maximum phase correction over a sync
cycle.

-- 
Doug Arnold
Principal Technologist
*JTime!* Meinberg USA
+1-707-303-5559

--001a11c30a8445639a04e985ec3c
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Hello Everyone,<div><br></div><div>Attached is an updated =
version of the Enterprise profile. =A0Sorry I missed the upload deadline fo=
r=A0=A0the Vancouver meeting. =A0If you get a chance to look at it before t=
hen I will be there and would love to discuss it.=A0</div>
<div><br></div><div>Summary of changes:</div><div><br></div><div><span styl=
e=3D"font-family:arial,sans-serif;font-size:12.727272033691406px">I also ch=
anged the TLV format to fit the latest proposal in the 1588 revision. =A0</=
span></div>
<div><span style=3D"font-family:arial,sans-serif;font-size:12.7272720336914=
06px"><br></span></div><div><span style=3D"font-family:arial,sans-serif;fon=
t-size:12.727272033691406px">I added a statement about not going into the m=
aster state unless one had a current UTC offset. =A0</span></div>
<div><span style=3D"font-family:arial,sans-serif;font-size:12.7272720336914=
06px"><br></span></div><div><span style=3D"font-family:arial,sans-serif;fon=
t-size:12.727272033691406px">I added to the TLV fields to indicate maximum =
phase correction over a sync cycle.</span><br>
</div><div><div><br></div>-- <br><div dir=3D"ltr">Doug Arnold<div>Principal=
 Technologist<br><div><i>JTime!</i>=A0Meinberg USA</div></div><div>+1-707-3=
03-5559</div><div><br></div><div><br></div></div>
</div></div>

--001a11c30a8445639a04e985ec3c--
--001a11c30a844563a804e985ec3e
Content-Type: text/plain; charset=US-ASCII; 
	name="draft-ietf-tictoc-ptp-enterprise-profile-01.txt"
Content-Disposition: attachment; 
	filename="draft-ietf-tictoc-ptp-enterprise-profile-01.txt"
Content-Transfer-Encoding: base64
X-Attachment-Id: f_hn6osfy40

SW50ZXJuZXQtRHJhZnQgICAgICAgICAgRW50ZXJwcmlzZSBQcm9maWxlIGZvciBQVFAgICAgICAg
ICAgT2N0b2JlciAyMDEzClRJQ1RPQyBXb3JraW5nIEdyb3VwICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgICBEb3VnIEFybm9sZApJbnRlcm5ldCBEcmFmdCAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICBNZWluYmVyZy1VU0EKSW50ZW5kZWQg
c3RhdHVzOiBTdGFuZGFyZHMgVHJhY2sgICAgICAgICAgICAgICAgICAgICAgICAgIEhlaWtvIEdl
cnN0dW5nCiAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICBNZWluYmVyZwpFeHBpcmVzOiBBcHJpbCAxNSwgMjAxNCAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgICBPY3QgMTUsIDIwMTMKCiAgICAgICAgICBFbnRlcnBy
aXNlIFByb2ZpbGUgZm9yIHRoZSBQcmVjaXNpb24gVGltZSBQcm90b2NvbAogICAgICAgICAgICAg
ICBXaXRoIE1peGVkIE11bHRpY2FzdCBhbmQgVW5pY2FzdCBNZXNzYWdlcwoKCiAgICAgICAgICAg
ZHJhZnQtaWV0Zi10aWN0b2MtcHRwLWVudGVycHJpc2UtcHJvZmlsZS0wMS50eHQKCgpTdGF0dXMg
b2YgdGhpcyBNZW1vCiAgICAgVGhpcyBJbnRlcm5ldC1EcmFmdCBpcyBzdWJtaXR0ZWQgaW4gZnVs
bCBjb25mb3JtYW5jZSB3aXRoIHRoZQogICAgIHByb3Zpc2lvbnMgb2YgQkNQIDc4IGFuZCBCQ1Ag
NzkuIFRoaXMgZG9jdW1lbnQgbWF5IG5vdCBiZQogICAgIG1vZGlmaWVkLCBhbmQgZGVyaXZhdGl2
ZSB3b3JrcyBvZiBpdCBtYXkgbm90IGJlIGNyZWF0ZWQsIGV4Y2VwdCB0bwogICAgIHB1Ymxpc2gg
aXQgYXMgYW4gUkZDIGFuZCB0byB0cmFuc2xhdGUgaXQgaW50byBsYW5ndWFnZXMgb3RoZXIgdGhh
bgogICAgIEVuZ2xpc2guCgogICAgIEludGVybmV0LURyYWZ0cyBhcmUgd29ya2luZyBkb2N1bWVu
dHMgb2YgdGhlIEludGVybmV0IEVuZ2luZWVyaW5nCiAgICAgVGFzayBGb3JjZSAoSUVURiksIGl0
cyBhcmVhcywgYW5kIGl0cyB3b3JraW5nIGdyb3Vwcy4gIE5vdGUgdGhhdAogICAgIG90aGVyIGdy
b3VwcyBtYXkgYWxzbyBkaXN0cmlidXRlIHdvcmtpbmcgZG9jdW1lbnRzIGFzIEludGVybmV0LQog
ICAgIERyYWZ0cy4KICAgIAogICAgIEludGVybmV0LURyYWZ0cyBhcmUgZHJhZnQgZG9jdW1lbnRz
IHZhbGlkIGZvciBhIG1heGltdW0gb2Ygc2l4CiAgICAgbW9udGhzIGFuZCBtYXkgYmUgdXBkYXRl
ZCwgcmVwbGFjZWQsIG9yIG9ic29sZXRlZCBieSBvdGhlcgogICAgIGRvY3VtZW50cyBhdCBhbnkg
dGltZS4gIEl0IGlzIGluYXBwcm9wcmlhdGUgdG8gdXNlIEludGVybmV0LURyYWZ0cwogICAgIGFz
IHJlZmVyZW5jZSBtYXRlcmlhbCBvciB0byBjaXRlIHRoZW0gb3RoZXIgdGhhbiBhcyAid29yayBp
bgogICAgIHByb2dyZXNzLiIKCiAgICAgVGhlIGxpc3Qgb2YgY3VycmVudCBJbnRlcm5ldC1EcmFm
dHMgY2FuIGJlIGFjY2Vzc2VkIGF0CiAgICAgaHR0cDovL3d3dy5pZXRmLm9yZy9pZXRmLzFpZC1h
YnN0cmFjdHMudHh0CgogICAgIFRoZSBsaXN0IG9mIEludGVybmV0LURyYWZ0IFNoYWRvdyBEaXJl
Y3RvcmllcyBjYW4gYmUgYWNjZXNzZWQgYXQKICAgICBodHRwOi8vd3d3LmlldGYub3JnL3NoYWRv
dy5odG1sCgogICAgIFRoaXMgSW50ZXJuZXQtRHJhZnQgd2lsbCBleHBpcmUgb24gQXByaWwgMTUs
IDIwMTQuCgpDb3B5cmlnaHQgTm90aWNlCiAgICAgQ29weXJpZ2h0IChjKSAyMDEzIElFVEYgVHJ1
c3QgYW5kIHRoZSBwZXJzb25zIGlkZW50aWZpZWQgYXMgdGhlCiAgICAgZG9jdW1lbnQgYXV0aG9y
cy4gQWxsIHJpZ2h0cyByZXNlcnZlZC4KCiAgICAgVGhpcyBkb2N1bWVudCBpcyBzdWJqZWN0IHRv
IEJDUCA3OCBhbmQgdGhlIElFVEYgVHJ1c3QncyBMZWdhbAogICAgIFByb3Zpc2lvbnMgUmVsYXRp
bmcgdG8gSUVURiBEb2N1bWVudHMKICAgICAoaHR0cDovL3RydXN0ZWUuaWV0Zi5vcmcvbGljZW5z
ZS1pbmZvKSBpbiBlZmZlY3Qgb24gdGhlIGRhdGUgb2YKICAgICBwdWJsaWNhdGlvbiBvZiB0aGlz
IGRvY3VtZW50LiBQbGVhc2UgcmV2aWV3IHRoZXNlIGRvY3VtZW50cwogICAgIGNhcmVmdWxseSwg
YXMgdGhleSBkZXNjcmliZSB5b3VyIHJpZ2h0cyBhbmQgcmVzdHJpY3Rpb25zIHdpdGgKICAgICBy
ZXNwZWN0IHRvIHRoaXMgZG9jdW1lbnQuIENvZGUgQ29tcG9uZW50cyBleHRyYWN0ZWQgZnJvbSB0
aGlzCiAgICAgZG9jdW1lbnQgbXVzdCBpbmNsdWRlIFNpbXBsaWZpZWQgQlNEIExpY2Vuc2UgdGV4
dCBhcyBkZXNjcmliZWQgaW4KICAgICBTZWN0aW9uIDQuZSBvZiB0aGUgVHJ1c3QgTGVnYWwgUHJv
dmlzaW9ucyBhbmQgYXJlIHByb3ZpZGVkIHdpdGhvdXQKICAgICB3YXJyYW50eSBhcyBkZXNjcmli
ZWQgaW4gdGhlIFNpbXBsaWZpZWQgQlNEIExpY2Vuc2UuCgoKQXJub2xkIGFuZCBHZXJzdHVuZyAg
ICAgICAgICAgICAgT2N0b2JlciAxNSwgMjAxMyAgICAgICAgICAgICAgIFtQYWdlIDFdCgwKIApJ
bnRlcm5ldC1EcmFmdCAgICAgICAgICBFbnRlcnByaXNlIFByb2ZpbGUgZm9yIFBUUCAgICAgICAg
ICAgICAgT2N0IDIwMTMKCkFic3RyYWN0CgogICAgVGhpcyBkb2N1bWVudCBkZXNjcmliZXMgYSBw
cm9maWxlIGZvciB0aGUgdXNlIG9mIHRoZSBQcmVjaXNpb24KICAgIFRpbWUgUHJvdG9jb2wgaW4g
YW4gSVBWNCBvciBJUHY2IEVudGVycHJpc2UgaW5mb3JtYXRpb24gc3lzdGVtCiAgICBlbnZpcm9u
bWVudC4gIFRoZSBwcm9maWxlIHVzZXMgdGhlIEVuZCB0byBFbmQgRGVsYXkgTWVhc3VyZW1lbnQK
ICAgIE1lY2hhbmlzbSwgYWxsb3dzIGJvdGggbXVsdGljYXN0IGFuZCB1bmljYXN0IERlbGF5IFJl
cXVlc3QgYW5kIERlbGF5CiAgICBSZXNwb25zZSBNZXNzYWdlcy4KCiAgICAKVGFibGUgb2YgQ29u
dGVudHMKCjEuICAgSW50cm9kdWN0aW9uICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgMgoy
LiAgIENvbnZlbnRpb25zIHVzZWQgaW4gdGhpcyBkb2N1bWVudCAgICAgICAgIDMKMy4gICBUZWNo
bmljYWwgVGVybXMgICAgICAgICAgICAgICAgICAgICAgICAgICA0CjQuICAgUHJvYmxlbSBTdGF0
ZW1lbnQgICAgICAgICAgICAgICAgICAgICAgICAgNQo1LiAgIE5ldHdvcmsgVGVjaG5vbG9neSAg
ICAgICAgICAgICAgICAgICAgICAgIDYgCQo2LiAgIFRpbWUgVHJhbnNmZXIgYW5kIERlbGF5IE1l
YXN1cmVtZW50ICAgICAgIDcKICAgICA2LjEuICAgVW5pY2FzdCBEZWxheSBNZWFzdXJlbWVudCBN
b2RlICAgICA3CiAgICAgNi4yLiAgIE11bHRpY2FzdCBEZWxheSBNZWFzdXJlbWVudCBNb2RlICAg
NwogICAgIDYuMy4gICBIeWJyaWQgZGVsYXkgTWVhc3VyZW1lbnQgTW9kZSAgICAgIDgKNy4gICBE
ZWZhdWx0IE1lc3NhZ2UgUmF0ZXMgICAgICAgICAgICAgICAgICAgICA4CjguICAgUmVxdWlyZW1l
bnRzIGZvciBNYXN0ZXIgQ2xvY2tzICAgICAgICAgICAgOAo5LiAgIFJlcXVpcmVtZW50cyBmb3Ig
U2xhdmUgQ2xvY2tzICAgICAgICAgICAgMTAKMTAuICBSZXF1aXJlbWVudHMgZm9yIFRyYW5zcGFy
ZW50IENsb2NrcyAgICAgIDEwCjExLiAgTWFuYWdlbWVudCBhbmQgU2lnbmFsaW5nIE1lc3NhZ2Vz
ICAgICAgICAxMAoxMi4gIEZvcmJpZGRlbiBQVFAgT3B0aW9ucyAgICAgICAgICAgICAgICAgICAg
MTEKMTMuICBJbnRlcm9wZXJhdGlvbiB3aXRoIE90aGVyIFBUUCBQcm9maWxlcyAgIDExCjE0LiAg
U2VjdXJpdHkgQ29uc2lkZXJhdGlvbnMgICAgICAgICAgICAgICAgICAxMQoxNS4gIElBTkEgQ29u
c2lkZXJhdGlvbnMgICAgICAgICAgICAgICAgICAgICAgMTIKMTYuICBSZWZlcmVuY2VzICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgIDEyCiAgICAgMTYuMS4gIE5vcm1hdGl2ZSBSZWZlcmVu
Y2VzICAgICAgICAgICAgICAxMgogICAgIDE2LjIuICBJbmZvcm1hdGl2ZSBSZWZlcmVuY2VzICAg
ICAgICAgICAgMTIKMTcuICBBY2tub3dsZWRnbWVudHMgICAgICAgICAgICAgICAgICAgICAgICAg
IDEzCjE4LiBBdXRob3JzIGFkZHJlc3NlcyAgICAgICAgICAgICAgICAgICAgICAgICAxMwoKMS4g
IEludHJvZHVjdGlvbgoKICAgICBUaGUgUHJlY2lzaW9uIFRpbWUgUHJvdG9jb2wgKCJQVFAiKSwg
c3RhbmRhcmRpemVkIGluIElFRUUgMTU4OCwKICAgICBoYXMgYmVlbiBkZXNpZ25lZCBpbiBpdHMg
Zmlyc3QgdmVyc2lvbiAoSUVFRSAxNTg4LTIwMDIpIHdpdGggdGhlCiAgICAgZ29hbCB0byBtaW5p
bWl6ZSBjb25maWd1cmF0aW9uIG9uIHRoZSBwYXJ0aWNpcGF0aW5nIG5vZGVzLiBOZXR3b3JrCiAg
ICAgY29tbXVuaWNhdGlvbiB3YXMgYmFzZWQgc29sZWx5IG9uIG11bHRpY2FzdCBtZXNzYWdlcywg
d2hpY2ggdW5saWtlCiAgICAgTlRQIGRpZCBub3QgcmVxdWlyZSB0aGF0IGEgcmVjZWl2aW5nIG5v
ZGUgKCJzbGF2ZSBjbG9jayIpIGluCiAgICAgW0lFRUUxNTg4XSBuZWVkcyB0byBrbm93IHRoZSBp
ZGVudGl0eSBvZiB0aGUgdGltZSBzb3VyY2VzIGluIHRoZQogICAgIG5ldHdvcmsgKHRoZSBNYXN0
ZXIgQ2xvY2tzKS4KCSAKICAgICBUaGUgc28tY2FsbGVkICJCZXN0IE1hc3RlciBDbG9jayBBbGdv
cml0aG0iIChbSUVFRTE1ODhdIENsYXVzZQogICAgIDkuMyksIGEgbWVjaGFuaXNtIHRoYXQgYWxs
IHBhcnRpY2lwYXRpbmcgUFRQIG5vZGVzIG11c3QgZm9sbG93LAogICAgIHNldCB1cCBzdHJpY3Qg
cnVsZXMgZm9yIGFsbCBtZW1iZXJzIG9mIGEgUFRQIGRvbWFpbiB0byBkZXRlcm1pbmUKICAgICB3
aGljaCBub2RlIHNoYWxsIGJlIHRoZSBhY3RpdmUgc2VuZGluZyB0aW1lIHNvdXJjZSAoTWFzdGVy
IENsb2NrKS4KICAgICBBbHRob3VnaCB0aGUgbXVsdGljYXN0IGNvbW11bmljYXRpb24gbW9kZWwg
aGFzIGFkdmFudGFnZXMgaW4KICAgICBzbWFsbGVyIG5ldHdvcmtzLCBpdCBjb21wbGljYXRlZCB0
aGUgYXBwbGljYXRpb24gb2YgUFRQIGluIGxhcmdlcgogICAgIG5ldHdvcmtzLCBmb3IgZXhhbXBs
ZSBpbiBlbnZpcm9ubWVudHMgbGlrZSBJUCBiYXNlZAogICAgIHRlbGVjb21tdW5pY2F0aW9uIG5l
dHdvcmtzIG9yIGZpbmFuY2lhbCBkYXRhIGNlbnRlcnMuIEl0IGlzCgoKQXJub2xkIGFuZCBHZXJz
dHVuZyAgICAgICAgICAgICAgT2N0b2JlciAxNSwgMjAxMyAgICAgICAgICAgICAgIFtQYWdlIDJd
CgwKCkludGVybmV0LURyYWZ0ICAgICAgICAgIEVudGVycHJpc2UgUHJvZmlsZSBmb3IgUFRQICAg
ICAgICAgICAgICBPY3QgMjAxMwoKICAgICBjb25zaWRlcmVkIGluZWZmaWNpZW50IHRoYXQsIGV2
ZW4gaWYgdGhlIGNvbnRlbnQgb2YgYSBtZXNzYWdlCiAgICAgYXBwbGllcyBvbmx5IHRvIG9uZSBy
ZWNlaXZlciwgaXQgaXMgZm9yd2FyZGVkIGJ5IHRoZSB1bmRlcmx5aW5nCiAgICAgbmV0d29yayAo
SVApIHRvIGFsbCBub2RlcywgcmVxdWlyaW5nIHRoZW0gdG8gc3BlbmQgbmV0d29yawogICAgIGJh
bmR3aWR0aCBhbmQgb3RoZXIgcmVzb3VyY2VzIGxpa2UgQ1BVIGN5Y2xlcyB0byBkcm9wIHRoZSBt
ZXNzYWdlLgogICAgIFRoZSBzZWNvbmQgcmV2aXNpb24gb2YgdGhlIHN0YW5kYXJkIChJRUVFIDE1
ODgtMjAwOCkgaXMgdGhlCiAgICAgY3VycmVudCB2ZXJzaW9uIChhbHNvIGtub3duIGFzIFBUUHYy
KSBhbmQgaW50cm9kdWNlZCB0aGUKICAgICBwb3NzaWJpbGl0eSB0byB1c2UgdW5pY2FzdCBjb21t
dW5pY2F0aW9uIGJldHdlZW4gdGhlIFBUUCBub2RlcyBpbgogICAgIG9yZGVyIHRvIG92ZXJjb21l
IHRoZSBsaW1pdGF0aW9uIG9mIHVzaW5nIG11bHRpY2FzdCBtZXNzYWdlcyBmb3IKICAgICB0aGUg
YmktZGlyZWN0aW9uYWwgaW5mb3JtYXRpb24gZXhjaGFuZ2UgYmV0d2VlbiBQVFAgbm9kZXMuIFRo
ZQogICAgIHVuaWNhc3QgYXBwcm9hY2ggYXZvaWRlZCB0aGF0LCBpbiBQVFAgZG9tYWlucyB3aXRo
IGEgbG90IG9mIG5vZGVzLAogICAgIGRldmljZXMgaGFkIHRvIHRocm93IGF3YXkgdXAgdG8gOTkl
IG9mIHRoZSByZWNlaXZlZCBtdWx0aWNhc3QKICAgICBtZXNzYWdlcyBiZWNhdXNlIHRoZXkgY2Fy
cmllZCBpbmZvcm1hdGlvbiBmb3Igc29tZSBvdGhlciBub2RlLgogICAgIFBUUHYyIGFsc28gaW50
cm9kdWNlZCBzby1jYWxsZWQgIlBUUCBwcm9maWxlcyIgKFtJRUVFMTU4OF0gQ2xhdXNlCiAgICAg
MTkuMykuIFRoaXMgY29uc3RydWN0IGFsbG93cyBvcmdhbml6YXRpb25zIHRvIHNwZWNpZnkgc2Vs
ZWN0aW9ucwogICAgIG9mIGF0dHJpYnV0ZSB2YWx1ZXMgYW5kIG9wdGlvbmFsIGZlYXR1cmVzLCBz
aW1wbGlmeWluZyB0aGUKICAgICBjb25maWd1cmF0aW9uIG9mIFBUUCBub2RlcyBmb3IgYSBzcGVj
aWZpYyBhcHBsaWNhdGlvbi4gSW5zdGVhZCBvZgogICAgIGhhdmluZyB0byBnbyB0aHJvdWdoIGFs
bCBwb3NzaWJsZSBwYXJhbWV0ZXJzIGFuZCBjb25maWd1cmF0aW9uCiAgICAgb3B0aW9ucyBhbmQg
aW5kaXZpZHVhbGx5IHNldCB0aGVtIHVwLCBzZWxlY3RpbmcgYSBwcm9maWxlIG9uIGEgUFRQCiAg
ICAgbm9kZSB3aWxsIHNldCBhbGwgdGhlIHBhcmFtZXRlcnMgdGhhdCBhcmUgc3BlY2lmaWVkIGlu
IHRoZSBwcm9maWxlCiAgICAgdG8gYSBkZWZpbmVkIHZhbHVlLiBJZiBhIFBUUCBwcm9maWxlIGRl
ZmluaXRpb24gYWxsb3dzIG11bHRpcGxlCiAgICAgdmFsdWVzIGZvciBhIHBhcmFtZXRlciwgc2Vs
ZWN0aW9uIG9mIHRoZSBwcm9maWxlIHdpbGwgc2V0IHRoZQogICAgIHByb2ZpbGUtc3BlY2lmaWMg
ZGVmYXVsdCB2YWx1ZSBmb3IgdGhpcyBwYXJhbWV0ZXIuIFBhcmFtZXRlcnMgbm90CiAgICAgYWxs
b3dpbmcgbXVsdGlwbGUgdmFsdWVzIGFyZSBzZXQgdG8gdGhlIHZhbHVlIGRlZmluZWQgaW4gdGhl
IFBUUAogICAgIHByb2ZpbGUuIEEgbnVtYmVyIG9mIFBUUCBmZWF0dXJlcyBhbmQgZnVuY3Rpb25z
IGFyZSBvcHRpb25hbCBhbmQgYQogICAgIHByb2ZpbGUgc2hvdWxkIGFsc28gZGVmaW5lIHdoaWNo
IG9wdGlvbmFsIGZlYXR1cmVzIG9mIFBUUCBhcmUKICAgICByZXF1aXJlZCwgcGVybWl0dGVkIG9y
IHByb2hpYml0ZWQuIEl0IGlzIHBvc3NpYmxlIHRvIGV4dGVuZCB0aGUKICAgICBQVFAgc3RhbmRh
cmQgd2l0aCBhIFBUUCBwcm9maWxlIGJ5IHVzaW5nIHRoZSBUTFYgbWVjaGFuaXNtIG9mIFBUUAog
ICAgIChzZWUgW0lFRUUxNTg4XSBDbGF1c2UgMTMuNCksIGRlZmluaW5nIGFuIG9wdGlvbmFsIEJl
c3QgTWFzdGVyCiAgICAgQ2xvY2sgQWxnb3JpdGhtIGFuZCBhIGZldyBvdGhlciB3YXlzLiBQVFAg
aGFzIGl0cyBvd24gbWFuYWdlbWVudAogICAgIHByb3RvY29sIChkZWZpbmVkIGluIFtJRUVFMTU4
OF0gQ2xhdXNlIDE1LjIpIGJ1dCBhbGxvd3MgYSBQVFAKICAgICBwcm9maWxlIHNwZWNpZnkgYW4g
YWx0ZXJuYXRpdmUgbWFuYWdlbWVudCBtZWNoYW5pc20sIGZvciBleGFtcGxlCiAgICAgU05NUC4K
CgoyLiAgQ29udmVudGlvbnMgdXNlZCBpbiB0aGlzIGRvY3VtZW50CgogICAgIFRoZSBrZXkgd29y
ZHMgIk1VU1QiLCAiTVVTVCBOT1QiLCAiUkVRVUlSRUQiLCAiU0hBTEwiLCAiU0hBTEwKICAgICBO
T1QiLCAiU0hPVUxEIiwgIlNIT1VMRCBOT1QiLCAiUkVDT01NRU5ERUQiLCAiTUFZIiwgYW5kICJP
UFRJT05BTCIKICAgICBpbiB0aGlzIGRvY3VtZW50IGFyZSB0byBiZSBpbnRlcnByZXRlZCBhcyBk
ZXNjcmliZWQgaW4gUkZDLTIxMTkKICAgICBbUkZDMjExOV0uCgogICAgIEluIHRoaXMgZG9jdW1l
bnQsIHRoZXNlIHdvcmRzIHdpbGwgYXBwZWFyIHdpdGggdGhhdCBpbnRlcnByZXRhdGlvbgogICAg
IG9ubHkgd2hlbiBpbiBBTEwgQ0FQUy4gTG93ZXIgY2FzZSB1c2VzIG9mIHRoZXNlIHdvcmRzIGFy
ZSBub3QgdG8KICAgICBiZSBpbnRlcnByZXRlZCBhcyBjYXJyeWluZyBSRkMtMjExOSBzaWduaWZp
Y2FuY2UuCiAKCkFybm9sZCBhbmQgR2Vyc3R1bmcgICAgICAgICAgICAgIE9jdG9iZXIgMTUsIDIw
MTMgICAgICAgICAgICAgIFtQYWdlIDNdCgwKCkludGVybmV0LURyYWZ0ICAgICAgICAgRW50ZXJw
cmlzZSBQcm9maWxlIGZvciBQVFAgICAgICAgICAgICAgIE9jdCAyMDEzCgozLiAgVGVjaG5pY2Fs
IFRlcm1zCgogICAgIEFjY2VwdGFibGUgTWFzdGVyIFRhYmxlOiBBIFBUUCBTbGF2ZSBDbG9jayBt
YXkgbWFpbnRhaW4gYSBsaXN0IG9mCiAgICAgbWFzdGVycyB3aGljaCBpdCBpcyB3aWxsaW5nIHRv
IHN5bmNocm9uaXplIHRvLgoKICAgICBBbHRlcm5hdGUgTWFzdGVyOiBBIFBUUCBNYXN0ZXIgQ2xv
Y2ssIHdoaWNoIGlzIG5vdCB0aGUgQmVzdAogICAgIE1hc3RlciwgbWF5IGFjdCBhcyBhIG1hc3Rl
ciB3aXRoIHRoZSBBbHRlcm5hdGUgTWFzdGVyIGZsYWcgc2V0IG9uCiAgICAgdGhlIG1lc3NhZ2Vz
IGl0IHNlbmRzLgoKICAgICBBbm5vdW5jZSBtZXNzYWdlOiBDb250YWlucyB0aGUgbWFzdGVyIGNs
b2NrIHByb3BlcnRpZXMgb2YgYSBNYXN0ZXIKICAgICBjbG9jay4gIFVzZWQgdG8gZGV0ZXJtaW5l
IHRoZSBCZXN0IE1hc3Rlci4KCiAgICAgQmVzdCBNYXN0ZXI6ICBBIGNsb2NrIHdpdGggYSBwb3J0
IGluIHRoZSBtYXN0ZXIgc3RhdGUsIG9wZXJhdGluZwogICAgIGNvbnNpc3RlbnRseSB3aXRoIHRo
ZSBCZXN0IE1hc3RlciBDbG9jayBBbGdvcml0aG0uCgogICAgIEJlc3QgTWFzdGVyIENsb2NrIEFs
Z29yaXRobTogQSBtZXRob2QgZm9yIGRldGVybWluaW5nIHdoaWNoIHN0YXRlCiAgICAgYSBwb3J0
IG9mIGEgUFRQIGNsb2NrIHNob3VsZCBiZSBpbi4gIFRoZSBhbGdvcml0aG0gd29ya3MgYnkKICAg
ICBpZGVudGlmeWluZyB3aGljaCBvZiBzZXZlcmFsIFBUUCBNYXN0ZXIgY2FwYWJsZSBjbG9ja3Mg
aXMgdGhlIGJlc3QKICAgICBtYXN0ZXIuICBDbG9ja3MgaGF2ZSBwcmlvcml0eSB0byBiZWNvbWUg
dGhlIGFjdGluZyBHcmFuZG1hc3RlciwKICAgICBiYXNlZCBvbiB0aGUgcHJvcGVydGllcyBlYWNo
IE1hc3RlciBDbG9jayBzZW5kcyBpbiBpdHMgQW5ub3VuY2UKICAgICBNZXNzYWdlLgoKICAgICBC
b3VuZGFyeSBDbG9jazogQSBkZXZpY2Ugd2l0aCBtb3JlIHRoYW4gb25lIFBUUCBwb3J0LiAgR2Vu
ZXJhbGx5CiAgICAgYm91bmRhcnkgY2xvY2tzIHdpbGwgaGF2ZSBvbmUgcG9ydCBpbiBzbGF2ZSBz
dGF0ZSB0byByZWNlaXZlCiAgICAgdGltaW5nIGFuZCB0aGVuIG90aGVyIHBvcnRzIGluIG1hc3Rl
ciBzdGF0ZSB0byByZS1kaXN0cmlidXRlIHRoZQogICAgIHRpbWluZy4KCiAgICAgQ2xvY2sgSWRl
bnRpdHk6IEluIElFRUUgMTU4OC0yMDA4IHRoaXMgaXMgYW4gNjQtYml0IG51bWJlcgogICAgIGFz
c2lnbmVkIHRvIGVhY2ggUFRQIGNsb2NrIHdoaWNoIG11c3QgYmUgdW5pcXVlLiBPZnRlbiB0aGUK
ICAgICBFdGhlcm5ldCBNQUMgYWRkcmVzcyBpcyB1c2VkIHNpbmNlIHRoZXJlIGlzIGFscmVhZHkg
YW4KICAgICBpbnRlcm5hdGlvbmFsIGluZnJhc3RydWN0dXJlIGZvciBhc3NpZ25pbmcgdW5pcXVl
IG51bWJlcnMgdG8gZWFjaAogICAgIGRldmljZSBtYW51ZmFjdHVyZWQuCgogICAgIEVuZCB0byBF
bmQgRGVsYXkgTWVhc3VyZW1lbnQgTWVjaGFuaXNtOiBBIG5ldHdvcmsgZGVsYXkKICAgICBtZWFz
dXJlbWVudCBtZWNoYW5pc20gaW4gUFRQIGZhY2lsaXRhdGVkIGJ5IGFuIGV4Y2hhbmdlIG9mCiAg
ICAgbWVzc2FnZXMgYmV0d2VlbiBhIE1hc3RlciBDbG9jayBhbmQgU2xhdmUgQ2xvY2suCgogICAg
IEdyYW5kbWFzdGVyOiB0aGUgcHJpbWFyeSBtYXN0ZXIgY2xvY2sgd2l0aGluIGEgZG9tYWluIG9m
IGEgUFRQCiAgICAgc3lzdGVtCgogICAgIElFRUUgMTU4ODogVGhlIHRpbWluZyBhbmQgc3luY2hy
b25pemF0aW9uIHN0YW5kYXJkIHdoaWNoIGRlZmluZXMKICAgICBQVFAsIGFuZCBkZXNjcmliZXMg
VGhlIG5vZGUsIHN5c3RlbSwgYW5kIGNvbW11bmljYXRpb24gcHJvcGVydGllcwogICAgIG5lY2Vz
c2FyeSB0byBzdXBwb3J0IFBUUC4KCiAgICAgTWFzdGVyIGNsb2NrOiBhIGNsb2NrIHdpdGggYXQg
bGVhc3Qgb25lIHBvcnQgaW4gdGhlIG1hc3RlciBzdGF0ZS4KCiAgICAgTlRQOiBOZXR3b3JrIFRp
bWUgUHJvdG9jb2wsIGRlZmluZWQgYnkgUkZDIDU5MDUsIHNlZSBbTlRQXS4KCiAgICAgT3JkaW5h
cnkgQ2xvY2s6IEEgY2xvY2sgdGhhdCBoYXMgYSBzaW5nbGUgUHJlY2lzaW9uIFRpbWUgUHJvdG9j
b2wKICAgICAoUFRQKSBwb3J0IGluIGEgZG9tYWluIGFuZCBtYWludGFpbnMgdGhlIHRpbWVzY2Fs
ZSB1c2VkIGluIHRoZQogICAgIGRvbWFpbi4gSXQgbWF5IHNlcnZlIGFzIGEgbWFzdGVyIGNsb2Nr
LCBvciBiZSBhIHNsYXZlIGNsb2NrLgoKICAgICAKQXJub2xkIGFuZCBHZXJzdHVuZyAgICAgICAg
ICAgICAgIE9jdG9iZXIgMTUsIDIwMTMgICAgICAgICAgICAgIFtQYWdlIDRdCgwKCkludGVybmV0
LURyYWZ0ICAgICAgICAgIEVudGVycHJpc2UgUHJvZmlsZSBmb3IgUFRQICAgICAgICAgICAgICBP
Y3QgMjAxMwoKICAgICBQZWVyIHRvIFBlZXIgRGVsYXkgTWVhc3VyZW1lbnQgTWVjaGFuaXNtOiBB
IG5ldHdvcmsgZGVsYXkKICAgICBtZWFzdXJlbWVudCBtZWNoYW5pc20gaW4gUFRQIGZhY2lsaXRh
dGVkIGJ5IGFuIGV4Y2hhbmdlIG9mCiAgICAgbWVzc2FnZXMgYmV0d2VlbiBhZGphY2VudCBkZXZp
Y2VzIGluIGEgbmV0d29yay4KCiAgICAgUHJlZmVycmVkIE1hc3RlcjogQSBkZXZpY2UgaW50ZW5k
ZWQgdG8gYWN0IHByaW1hcmlseSBhcyB0aGUKICAgICBHcmFuZG1hc3RlciBvZiBhIFBUUCBzeXN0
ZW0sIG9yIGFzIGEgYmFjayB1cCB0byBhIEdyYW5kbWFzdGVyLgoKICAgICBQVFA6IFRoZSBQcmVj
aXNpb24gVGltZSBQcm90b2NvbCwgdGhlIHRpbWluZyBhbmQgc3luY2hyb25pemF0aW9uCiAgICAg
cHJvdG9jb2wgZGVmaW5lIGJ5IElFRUUgMTU4OC4KICAgICAKICAgICBQVFAgcG9ydDogQW4gaW50
ZXJmYWNlIG9mIGEgUFRQIGNsb2NrIHdpdGggdGhlIG5ldHdvcmsuICBOb3RlIHRoYXQKICAgICB0
aGVyZSBtYXkgYmUgbXVsdGlwbGUgUFRQIHBvcnRzIHJ1bm5pbmcgb24gb25lIHBoeXNpY2FsIGlu
dGVyZmFjZSwKICAgICBmb3IgZXhhbXBsZSBhIHVuaWNhc3Qgc2xhdmUgd2hpY2ggdGFsa3MgdG8g
c2V2ZXJhbCBHcmFuZG1hc3RlcgogICAgIGNsb2NrcyBpbiBwYXJhbGxlbC4KCiAgICAgUFRQdjI6
IFJlZmVycyBzcGVjaWZpY2FsbHkgdG8gdGhlIHNlY29uZCB2ZXJzaW9uIG9mIFBUUCBkZWZpbmVk
IGJ5CiAgICAgSUVFRSAxNTg4LTIwMDguCgogICAgIFJvZ3VlIE1hc3RlcjogQSBjbG9jayB3aXRo
IGEgcG9ydCBpbiB0aGUgbWFzdGVyIHN0YXRlLCBldmVuIHRob3VnaAogICAgIGl0IHNob3VsZCBu
b3QgYmUgaW4gdGhlIG1hc3RlciBzdGF0ZSBhY2NvcmRpbmcgdG8gdGhlIEJlc3QgTWFzdGVyCiAg
ICAgQ2xvY2sgQWxnb3JpdGhtLCBhbmQgZG9lcyBub3Qgc2V0IHRoZSBhbHRlcm5hdGUgbWFzdGVy
IGZsYWcuCgogICAgIFNsYXZlIGNsb2NrOiBhIGNsb2NrIHdpdGggYXQgbGVhc3Qgb25lIHBvcnQg
aW4gdGhlIHNsYXZlIHN0YXRlLAogICAgIGFuZCBubyBwb3J0cyBpbiB0aGUgbWFzdGVyIHN0YXRl
LgoKICAgICBTbGF2ZSBPbmx5IENsb2NrOiBBbiBPcmRpbmFyeSBjbG9jayB3aGljaCBjYW5ub3Qg
YmVjb21lIGEgTWFzdGVyCiAgICAgY2xvY2suCgogICAgIFRMVjogVHlwZSBMZW5ndGggVmFsdWUs
IGEgbWVjaGFuaXNtIGZvciBleHRlbmRpbmcgbWVzc2FnZXMgaW4KICAgICBuZXR3b3JrZWQgY29t
bXVuaWNhdGlvbnMuCgogICAgIFRyYW5zcGFyZW50IENsb2NrLiAgQSBkZXZpY2UgdGhhdCBtZWFz
dXJlcyB0aGUgdGltZSB0YWtlbiBmb3IgYQogICAgIFBUUCBldmVudCBtZXNzYWdlIHRvIHRyYW5z
aXQgdGhlIGRldmljZSBhbmQgdGhlbiB1cGRhdGVzIHRoZQogICAgIG1lc3NhZ2Ugd2l0aCBhIGNv
cnJlY3Rpb24gZm9yIHRoaXMgdHJhbnNpdCB0aW1lLgoKICAgICBVbmljYXN0IERpc2NvdmVyeTog
QSBtZWNoYW5pc20gZm9yIFBUUCBzbGF2ZXMgdG8gZXN0YWJsaXNoIGEKICAgICB1bmljYXN0IGNv
bW11bmljYXRpb24gd2l0aCBQVFAgbWFzdGVycyB1c2luZyBhIGNvbmZpZ3VyZXMgdGFibGUgb2YK
ICAgICBtYXN0ZXIgSVAgYWRkcmVzc2VzIGFuZCBVbmljYXN0IE1lc3NhZ2UgTmVnb3RpYXRpb24u
CgogICAgIFVuaWNhc3QgTmVnb3RpYXRpb246IEEgbWVjaGFuaXNtIGluIFBUUCBmb3IgU2xhdmUg
Q2xvY2tzIHRvCiAgICAgbmVnb3RpYXRlIHVuaWNhc3QgU3luYywgYW5ub3VuY2UgYW5kIERlbGF5
IFJlcXVlc3QgTWVzc2FnZSBSYXRlcwogICAgIGZyb20gYSBNYXN0ZXIgQ2xvY2suCgogICAgIAo0
LiAgUHJvYmxlbSBTdGF0ZW1lbnQKCiAgICAgVGhpcyBkb2N1bWVudCBkZXNjcmliZXMgYSB2ZXJz
aW9uIG9mIFBUUCBpbnRlbmRlZCB0byB3b3JrIGluIGxhcmdlCiAgICAgZW50ZXJwcmlzZSBuZXR3
b3Jrcy4gIFN1Y2ggbmV0d29ya3MgYXJlIGRlcGxveWVkLCBmb3IgZXhhbXBsZSwgaW4gCiAgICAg
ZmluYW5jaWFsIGNvcnBvcmF0aW9ucy4gIEl0IGlzIGJlY29taW5nIGluY3JlYXNpbmdseSBjb21t
b24gaW4gc3VjaCAKICAgICBuZXR3b3JrcyB0byBwZXJmb3JtIGRpc3RyaWJ1dGVkIHRpbWUgdGFn
Z2VkIG1lYXN1cmVtZW50cywgc3VjaCBhcyAKICAgICBvbmUtd2F5IHBhY2tldCBsYXRlbmNpZXMg
YW5kIGN1bXVsYXRpdmUgZGVsYXlzIG9uIHNvZnR3YXJlCiAgICAgc3lzdGVtcyBzcHJlYWQgYWNy
b3NzIG11bHRpcGxlIGNvbXB1dGVycy4gRnVydGhlcm1vcmUgdGhlcmUgaXMKCiAgICAgCkFybm9s
ZCBhbmQgR2Vyc3R1bmcgICAgICAgICAgICAgICBPY3RvYmVyIDE1LCAyMDEzICAgICAgICAgICAg
ICBbUGFnZSA1XQoMCgpJbnRlcm5ldC1EcmFmdCAgICAgICAgICBFbnRlcnByaXNlIFByb2ZpbGUg
Zm9yIFBUUCAgICAgICAgICAgICAgT2N0IDIwMTMKICAgICAgCgogICAgIG9mdGVuIGEgZGVzaXJl
IHRvIGNoZWNrIHRoZSBhZ2Ugb2YgaW5mb3JtYXRpb24gdGltZSB0YWdnZWQgYnkgYQogICAgIGRp
ZmZlcmVudCBtYWNoaW5lLiAgVG8gcGVyZm9ybSB0aGVzZSBtZWFzdXJlbWVudHMgaXQgaXMgbmVj
ZXNzYXJ5CiAgICAgdG8gZGVsaXZlciBhIGNvbW1vbiBwcmVjaXNlIHRpbWUgdG8gbXVsdGlwbGUg
ZGV2aWNlcyBvbiBhIG5ldHdvcmsuCiAgICAgQWNjdXJhY3kgY3VycmVudGx5IHJlcXVpcmVkIGlu
IHRoZSBGaW5hbmNpYWwgSW5kdXN0cnkgcmFuZ2UgZnJvbQogICAgIDEwMCBtaWNyb3NlY29uZHMg
dG8gNTAwIG5hbm9zZWNvbmRzIHRvIHRoZSBHcmFuZG1hc3Rlci4gIFRoaXMgCiAgICAgcHJvZmls
ZSBkb2VzIG5vdCBzcGVjaWZ5IHRpbWluZyBwZXJmb3JtYW5jZSByZXF1aXJlbWVudHMsIGJ1dCBz
dWNoIAogICAgIHJlcXVpcmVtZW50cyBleHBsYWluIHdoeSB0aGUgbmVlZHMgY2Fubm90IGFsd2F5
cyBiZSBtZXQgYnkgTlRQLCBhcyAKICAgICBjb21tb25seSBpbXBsZW1lbnRlZC4gU3VjaCBhY2N1
cmFjeSBjYW5ub3QgdXN1YWxseSBiZSBhY2hpZXZlZCB3aXRoCiAgICAgYSB0cmFkaXRpb25hbCB0
aW1lIHRyYW5zZmVyIHN1Y2ggYXMgTlRQLCB3aXRob3V0IGFkZGluZyAKICAgICBub24tc3RhbmRh
cmQgY3VzdG9taXphdGlvbnMgc3VjaCBhcyBoYXJkd2FyZSB0aW1lIHN0YW1waW5nLCBhbmQgb24g
CiAgICAgcGF0aCBzdXBwb3J0LiAgVGhlc2UgZmVhdHVyZXMgYXJlIGN1cnJlbnRseSBwYXJ0IG9m
IFBUUCwgb3IgYXJlIAogICAgIGFsbG93ZWQgYnkgaXQuICBCZWNhdXNlIFBUUCBoYXMgYSBjb21w
bGV4IHJhbmdlIG9mIGZlYXR1cmVzIGFuZCAKICAgICBvcHRpb25zIGl0IGlzIG5lY2Vzc2FyeSB0
byBjcmVhdGUgYSBwcm9maWxlIGZvciBlbnRlcnByaXNlIAogICAgIG5ldHdvcmtzIHRvIGFjaGll
dmUgaW50ZXJvcGVyYWJpbGl0eSBiZXR3ZWVuIGVxdWlwbWVudAogICAgIG1hbnVmYWN0dXJlZCBi
eSBkaWZmZXJlbnQgdmVuZG9ycy4KCiAgICAgQWx0aG91Z2ggZW50ZXJwcmlzZSBuZXR3b3JrcyBj
YW4gYmUgbGFyZ2UsIGl0IGlzIGJlY29taW5nCiAgICAgaW5jcmVhc2luZ2x5IGNvbW1vbiB0byBk
ZXBsb3kgbXVsdGljYXN0IHByb3RvY29scywgZXZlbiBhY3Jvc3MKICAgICBtdWx0aXBsZSBzdWJu
ZXRzLiBGb3IgdGhpcyByZWFzb24gaXQgaXMgZGVzaXJlZCB0byBtYWtlIHVzZSBvZgogICAgIG11
bHRpY2FzdCB3aGVuZXZlciB0aGUgaW5mb3JtYXRpb24gZ29pbmcgdG8gbWFueSBkZXN0aW5hdGlv
bnMgaXMKICAgICB0aGUgc2FtZS4gIEl0IGlzIGFsc28gYWR2YW50YWdlb3VzIHRvIHNlbmQgaW5m
b3JtYXRpb24gd2hpY2ggaXMKICAgICB1bmlxdWUgdG8gb25lIGRldmljZSBhcyBhIHVuaWNhc3Qg
bWVzc2FnZS4gIFRoZSBsYXR0ZXIgY2FuIGJlCiAgICAgZXNzZW50aWFsIGFzIHRoZSBudW1iZXIg
b2YgUFRQIHNsYXZlcyBiZWNvbWVzIGh1bmRyZWRzIG9yCiAgICAgdGhvdXNhbmRzLgoKICAgICBQ
VFAgZGV2aWNlcyBvcGVyYXRpbmcgaW4gdGhlc2UgbmV0d29ya3MgbmVlZCB0byBiZSByb2J1c3Qu
ICBUaGlzCiAgICAgaW5jbHVkZXMgdGhlIGFiaWxpdHkgdG8gaWdub3JlIFBUUCBtZXNzYWdlcyB3
aGljaCBjYW4gYmUKICAgICBpZGVudGlmaWVkIGFzIGltcHJvcGVyLCBhbmQgdG8gaGF2ZSByZWR1
bmRhbnQgc291cmNlcyBvZiB0aW1lLgoKICAgICAKNS4gIE5ldHdvcmsgVGVjaG5vbG9neQoKICAg
ICBUaGlzIFBUUCBwcm9maWxlIFNIQUxMIG9wZXJhdGUgb25seSBpbiBuZXR3b3JrcyBjaGFyYWN0
ZXJpemVkIGJ5CiAgICAgVURQIFtSRkM3NjhdIG92ZXIgZWl0aGVyIElQdjQgW1JGQzc5MV0gb3Ig
SVB2NiBbUkZDMjQ2MF0sIGFzCiAgICAgZGVzY3JpYmVkIGJ5IEFubmV4ZXMgRCBhbmQgRSBpbiBb
SUVFRTE1ODhdIHJlc3BlY3RpdmVseS4gIElmIGEKICAgICBuZXR3b3JrIGNvbnRhaW5zIGJvdGgg
SVB2NCBhbmQgSVB2NiwgdGhlbiB0aGV5IFNIQUxMIGJlIHRyZWF0ZWQgYXMKICAgICBzZXBhcmF0
ZSBjb21tdW5pY2F0aW9uIHBhdGhzLiAgQ2xvY2tzIHdoaWNoIGNvbW11bmljYXRlIHVzaW5nIElQ
djQKICAgICBjYW4gaW50ZXJhY3Qgd2l0aCBjbG9ja3MgdXNpbmcgSVB2NiBpZiB0aGVyZSBpcyBh
biBpbnRlcm1lZGlhcnkKICAgICBkZXZpY2Ugd2hpY2ggc2ltdWx0YW5lb3VzbHkgY29tbXVuaWNh
dGVzIHdpdGggYm90aCBJUCB2ZXJzaW9ucy4gQQogICAgIGJvdW5kYXJ5IGNsb2NrIG1pZ2h0IHBl
cmZvcm0gdGhpcyBmdW5jdGlvbiwgZm9yIGV4YW1wbGUuICBBIFBUUAogICAgIGRvbWFpbiBTSEFM
TCB1c2UgZWl0aGVyIElQdjQgb3IgSVB2NiBvdmVyIGEgY29tbXVuaWNhdGlvbiBwYXRoLAogICAg
IGJ1dCBub3QgYm90aC4gVGhlIFBUUCBzeXN0ZW0gTUFZIGluY2x1ZGUgc3dpdGNoZXMgYW5kIHJv
dXRlcnMuCiAgICAgVGhlc2UgZGV2aWNlcyBNQVkgYmUgdHJhbnNwYXJlbnQgY2xvY2tzLCBib3Vu
ZGFyeSBjbG9ja3MsIG9yCiAgICAgbmVpdGhlciwgaW4gYW55IGNvbWJpbmF0aW9uLiAgUFRQIENs
b2NrcyBNQVkgYmUgUHJlZmVycmVkIE1hc3RlcnMsCiAgICAgT3JkaW5hcnkgQ2xvY2tzLCBvciBC
b3VuZGFyeSBDbG9ja3MuICBUaGUgb3JkaW5hcnkgY2xvY2tzIG1heSBiZQogICAgIFNsYXZlIE9u
bHkgQ2xvY2tzLCBvciBiZSBtYXN0ZXIgY2FwYWJsZS4KCgpBcm5vbGQgYW5kIEdlcnN0dW5nICAg
ICAgICAgICAgICAgT2N0b2JlciAxNSwgMjAxMyAgICAgICAgICAgICAgW1BhZ2UgNl0KDAoKSW50
ZXJuZXQtRHJhZnQgICAgICAgICAgRW50ZXJwcmlzZSBQcm9maWxlIGZvciBQVFAgICAgICAgICAg
ICAgIE9jdCAyMDEzCiAgICAgTm90ZSB0aGF0IGNsb2NrcyBTSE9VTEQgYWx3YXlzIGJlIGlkZW50
aWZpZWQgYnkgdGhlaXIgY2xvY2sgSUQgYW5kCiAgICAgbm90IHRoZSBJUCBvciBMYXllciAyIGFk
ZHJlc3MuICBUaGlzIGlzIGltcG9ydGFudCBpbiBJUHY2IG5ldHdvcmtzCiAgICAgc2luY2UgVHJh
bnNwYXJlbnQgY2xvY2tzIGFyZSByZXF1aXJlZCB0byBjaGFuZ2UgdGhlIHNvdXJjZSBhZGRyZXNz
CiAgICAgb2YgYW55IHBhY2tldCB3aGljaCB0aGV5IGFsdGVyLiAgSW4gSVB2NCBuZXR3b3JrcyBz
b21lIGNsb2NrcwogICAgIG1pZ2h0IGJlIGhpZGRlbiBiZWhpbmQgYSBOQVQsIHdoaWNoIGhpZGVz
IHRoZWlyIElQIGFkZHJlc3NlcyBmcm9tCiAgICAgdGhlIHJlc3Qgb2YgdGhlIG5ldHdvcmsuICBO
b3RlIGFsc28gdGhhdCB0aGUgdXNlIG9mIE5BVHMgbWF5IHBsYWNlCiAgICAgbGltaXRhdGlvbnMg
b24gdGhlIHRvcG9sb2d5IG9mIFBUUCBuZXR3b3JrcywgZGVwZW5kaW5nIG9uIHRoZSBwb3J0CiAg
ICAgZm9yd2FyZGluZyBzY2hlbWUgZW1wbG95ZWQuICBEZXRhaWxzIG9mIGltcGxlbWVudGluZyBQ
VFAgd2l0aCBOQVRzCiAgICAgYXJlIG91dCBvZiBzY29wZSBvZiB0aGlzIGRvY3VtZW50LgoKICAg
ICBTaW1pbGFyIHRvIE5UUCwgUFRQIG1ha2VzIHRoZSBhc3N1bXB0aW9uIHRoYXQgdGhlIG9uZSB3
YXkgbmV0d29yawogICAgIGRlbGF5IGZvciBTeW5jIE1lc3NhZ2VzIGFuZCBEZWxheSBSZXNwb25z
ZSBNZXNzYWdlcyBhcmUgdGhlIHNhbWUuCiAgICAgV2hlbiB0aGlzIGlzIG5vdCB0cnVlIGl0IGNh
biBjYXVzZSBlcnJvcnMgaW4gdGhlIHRyYW5zZmVyIG9mIHRpbWUKICAgICBmcm9tIHRoZSBNYXN0
ZXIgdG8gdGhlIFNsYXZlLiBJdCBpcyB1cCB0byB0aGUgc3lzdGVtIGludGVncmF0b3IgdG8KICAg
ICBkZXNpZ24gdGhlIG5ldHdvcmsgc28gdGhhdCBzdWNoIGVmZmVjdHMgZG8gbm90IHByZXZlbnQg
dGhlIFBUUAogICAgIHN5c3RlbSBmcm9tIG1lZXRpbmcgdGhlIHRpbWluZyByZXF1aXJlbWVudHMu
IFRoZSBkZXRhaWxzIG9mCiAgICAgbmV0d29yayBhc3ltbWV0cnkgYXJlIG91dHNpZGUgdGhlIHNj
b3BlIG9mIHRoaXMgZG9jdW1lbnQuICBTZWUgZm9yCiAgICAgZXhhbXBsZSwgW0c4MjcxXS4KCiAg
ICAgCjYuICBUaW1lIFRyYW5zZmVyIGFuZCBEZWxheSBNZWFzdXJlbWVudAoKICAgICBNYXN0ZXIg
Y2xvY2tzLCBUcmFuc3BhcmVudCBjbG9ja3MgYW5kIEJvdW5kYXJ5IGNsb2NrcyBNQVkgYmUKICAg
ICBlaXRoZXIgb25lLXN0ZXAgY2xvY2tzIG9yIHR3by1zdGVwIGNsb2Nrcy4gIFNsYXZlIGNsb2Nr
cyBNVVNUCiAgICAgc3VwcG9ydCBib3RoIGJlaGF2aW9ycy4gVGhlIEVuZCB0byBFbmQgRGVsYXkg
TWVhc3VyZW1lbnQgTWV0aG9kCiAgICAgTVVTVCBiZSB1c2VkLgoKICAgICBOb3RlIHRoYXQsIGlu
IElQIG5ldHdvcmtzLCBTeW5jIG1lc3NhZ2VzIGFuZCBEZWxheSBSZXF1ZXN0CiAgICAgbWVzc2Fn
ZXMgZXhjaGFuZ2VkIGJldHdlZW4gYSBtYXN0ZXIgYW5kIHNsYXZlIGRvIG5vdCBuZWNlc3Nhcmls
eQogICAgIHRyYXZlcnNlIHRoZSBzYW1lIHBoeXNpY2FsIHBhdGguIFRodXMsIHdoZXJldmVyIHBv
c3NpYmxlLCB0aGUKICAgICBuZXR3b3JrIFNIT1VMRCBiZSB0cmFmZmljIGVuZ2luZWVyZWQgc28g
dGhhdCB0aGUgZm9yd2FyZCBhbmQKICAgICByZXZlcnNlIHJvdXRlcyB0cmF2ZXJzZSB0aGUgc2Ft
ZSBwaHlzaWNhbCBwYXRoLiAgVHJhZmZpYwogICAgIGVuZ2luZWVyaW5nIHRlY2huaXF1ZXMgZm9y
IHBhdGggY29uc2lzdGVuY3kgYXJlIG91dCBvZiBzY29wZSBvZgogICAgIHRoaXMgZG9jdW1lbnQu
CgogICAgIEluIGFsbCB0aHJlZSBvZiB0aGUgZGVsYXkgbWVhc3VyZW1lbnQgbW9kZXMsICBTeW5j
IG1lc3NhZ2VzIE1VU1QKICAgICBiZSBzZW50IGFzIFBUUCBldmVudCBtdWx0aWNhc3QgbWVzc2Fn
ZXMgKFVEUCBwb3J0IDMxOSkgdG8gdGhlIFBUUAogICAgIHByaW1hcnkgSVAgYWRkcmVzcy4gICBU
d28gc3RlcCBjbG9ja3MgU0hBTEwgc2VuZCBGb2xsb3ctdXAKICAgICBtZXNzYWdlcyBhcyBQVFAg
Z2VuZXJhbCBtZXNzYWdlcyAoVURQIHBvcnQgMzIwKS4gQW5ub3VuY2UgbWVzc2FnZXMKICAgICBN
VVNUIGJlIHNlbnQgYXMgbXVsdGljYXN0IG1lc3NhZ2VzIChVRFAgcG9ydCAzMjApIHRvIHRoZSBQ
VFAKICAgICBwcmltYXJ5IGFkZHJlc3MuICBUaGUgUFRQIHByaW1hcnkgSVAgYWRkcmVzcyBpcyAy
MjQuMC4xLjEyOSBmb3IKICAgICBJUHY0IGFuZCBGRjBYOjA6MDowOjA6MDowOjE4MSBmb3IgSXB2
Niwgd2hlcmUgWCBjYW4gYmUgYSB2YWx1ZSAKICAgICBiZXR3ZWVuIDB4MCBhbmQgMHhGLCBzZWUg
W0lFRUUxNTg4XSBBbm5leCBFLCBTZWN0aW9uIEUuMy4KCjYuMS4gICBVbmljYXN0IERlbGF5IE1l
YXN1cmVtZW50IE1vZGUKCiAgICAgQWxsIERlbGF5IFJlcXVlc3QgUFRQIGV2ZW50IG1lc3NhZ2Vz
IGFuZCBEZWxheSBSZXNwb25zZSBQVFAKICAgICBnZW5lcmFsIG1lc3NhZ2VzIE1VU1QgYmUgc2Vu
dCBhcyB1bmljYXN0IG1lc3NhZ2VzLiBVbmljYXN0CiAgICAgRGlzY292ZXJ5IGFuZCBVbmljYXN0
IE1lc3NhZ2UgTmVnb3RpYXRpb24gb3B0aW9ucyBNVVNUIE5PVCBiZQogICAgIHV0aWxpemVkLgoK
Ni4yLiAgIE11bHRpY2FzdCBEZWxheSBNZWFzdXJlbWVudCBNb2RlCgogICAgIEFsbCBEZWxheSBS
ZXF1ZXN0IFBUUCBldmVudCBtZXNzYWdlcyBhbmQgRGVsYXkgUmVzcG9uc2UgZ2VuZXJhbAogICAg
IG1lc3NhZ2VzIE1VU1QgYmUgc2VudCBhcyBtdWx0aWNhc3QgbWVzc2FnZXMuCgpBcm5vbGQgYW5k
IEdlcnN0dW5nICAgICAgICAgICAgICAgT2N0b2JlciAxNSwgMjAxMyAgICAgICAgICAgICAgW1Bh
Z2UgN10KDAoKSW50ZXJuZXQtRHJhZnQgICAgICAgICAgRW50ZXJwcmlzZSBQcm9maWxlIGZvciBQ
VFAgICAgICAgICAgICAgIE9jdCAyMDEzCgo2LjMuICAgSHlicmlkIERlbGF5IE1lYXN1cmVtZW50
IE1vZGUKCiAgICAgRGVsYXkgUmVxdWVzdCBNZXNzYWdlcyBNQVkgYmUgc2VudCBhcyBlaXRoZXIg
bXVsdGljYXN0IG9yIHVuaWNhc3QKICAgICBQVFAgZXZlbnQgbWVzc2FnZXMuIE1hc3RlciBjbG9j
a3MgU0hBTEwgcmVzcG9uZCB0byBtdWx0aWNhc3QgRGVsYXkKICAgICBSZXF1ZXN0IG1lc3NhZ2Vz
IHdpdGggbXVsdGljYXN0IERlbGF5IFJlc3BvbnNlIFBUUCBnZW5lcmFsCiAgICAgbWVzc2FnZXMu
IE1hc3RlciBjbG9ja3MgU0hBTEwgcmVzcG9uZCB0byB1bmljYXN0IERlbGF5IFJlcXVlc3QgUFRQ
CiAgICAgZXZlbnQgbWVzc2FnZXMgd2l0aCB1bmljYXN0IERlbGF5IFJlc3BvbnNlIFBUUCBnZW5l
cmFsIG1lc3NhZ2VzLgoKICAgICBUaGUgZGVmYXVsdCBtb2RlIGZvciBFbnRlcnByaXNlIFByb2Zp
bGUgUFRQIE1hc3RlciBDbG9ja3MgaXMKICAgICBIeWJyaWQgRGVsYXkgTWVhc3VyZW1lbnQgTW9k
ZS4gVGhpcyBhbGxvdyBmb3IgdGhlIHVzZSBvZiBPcmRpbmFyeQogICAgIGNsb2NrcyB3aGljaCBk
byBub3Qgc3VwcG9ydCB0aGUgRW50ZXJwcmlzZSBQcm9maWxlLCBhcyBsb25nIGFzCiAgICAgdGhl
eSBhcmUgc2xhdmUgT25seSBDbG9ja3MuCgogICAgIAo3LiAgRGVmYXVsdCBNZXNzYWdlIFJhdGVz
CgogICAgIFRoZSBTeW5jLCBBbm5vdW5jZSBhbmQgRGVsYXkgUmVxdWVzdCBkZWZhdWx0IG1lc3Nh
Z2UgcmF0ZXMgU0hBTEwKICAgICBlYWNoIGJlIG9uY2UgcGVyIHNlY29uZC4gIFRoZSBTeW5jIGFu
ZCBEZWxheSBSZXF1ZXN0IG1lc3NhZ2UgcmF0ZXMKICAgICBNQVkgYmUgc2V0IHRvIG90aGVyIHZh
bHVlcywgYnV0IG5vdCBsZXNzIHRoYW4gb25jZSBldmVyeSAxMjgKICAgICBzZWNvbmRzLCBhbmQg
bm90IG1vcmUgdGhhbiAxMjggbWVzc2FnZXMgcGVyIHNlY29uZC4gIFRoZSBBbm5vdW5jZQogICAg
IG1lc3NhZ2UgcmF0ZSBTSEFMTCBOT1QgYmUgY2hhbmdlZCBmcm9tIHRoZSBkZWZhdWx0IHZhbHVl
LiAgVGhlCiAgICAgQW5ub3VuY2UgUmVjZWlwdCBUaW1lb3V0IEludGVydmFsIFNIQUxMIGJlIHRo
cmVlIEFubm91bmNlCiAgICAgSW50ZXJ2YWxzIGZvciBQcmVmZXJyZWQgTWFzdGVycywgYW5kIGZv
dXIgQW5ub3VuY2UgSW50ZXJ2YWxzIGZvcgogICAgIGFsbCBvdGhlciBtYXN0ZXJzLgoKICAgICAK
OC4gIFJlcXVpcmVtZW50cyBmb3IgTWFzdGVyIENsb2NrcwoKICAgICBNYXN0ZXIgY2xvY2tzIFNI
QUxMIG9iZXkgdGhlIHN0YW5kYXJkIEJlc3QgTWFzdGVyIENsb2NrIEFsZ29yaXRobQogICAgIGZy
b20gW0lFRUUxNTg4XS4gIENsb2NrcyB3aGljaCBhcmUgbWFzdGVyIGNhcGFibGUgTUFZIGFjdCBh
cwogICAgIEFsdGVybmF0ZSBtYXN0ZXJzIGFjY29yZGluZyB0byBbSUVFRTE1ODhdLiAgUHJlZmVy
cmVkIE1hc3RlcgogICAgIENsb2NrcyBTSE9VTEQgb3BlcmF0ZSBhcyBBbHRlcm5hdGUgTWFzdGVy
cyB3aGVuIHRoZXkgYXJlIG5vdCB0aGUKICAgICBCZXN0IE1hc3Rlci4gVXNpbmcgbXVsdGlwbGUg
bWFzdGVycyBjYW4gbWl0aWdhdGUgcm9ndWUgbWFzdGVyIGFuZAogICAgIG1hbi1pbi10aGUtbWlk
ZGxlIGF0dGFja3Mgc3VjaCBhcyBkZWxheSBhdHRhY2tzLCBwYWNrZXQKICAgICBpbnRlcmNlcHRp
b24gLyBtYW5pcHVsYXRpb24gYXR0YWNrcy4gQXNzdW1pbmcgdGhlIHBhdGggdG8gZWFjaAogICAg
IG1hc3RlciBpcyBkaWZmZXJlbnQsIGFuIGF0dGFja2VyIHdvdWxkIGhhdmUgdG8gYXR0YWNrIG1v
cmUgdGhhbgogICAgIG9uZSBwYXRoIHNpbXVsdGFuZW91c2x5LgoKICAgICBBIHBvcnQgb2YgYSBj
bG9jayBTSEFMTCBOT1QgYmUgaW4gdGhlIG1hc3RlciBzdGF0ZSB1bmxlc3MgdGhlCiAgICAgY2xv
Y2sgaGFzIGEgY3VycmVudCB2YWx1ZSBmb3IgdGhlIG51bWJlciBvZiBVVEMgbGVhcAogICAgIHNl
Y29uZHMuICBBIGNsb2NrIHdpdGggYSBwb3J0IGluIHRoZSBtYXN0ZXIgc3RhdGUgU0hPVUxEIGlu
ZGljYXRlCiAgICAgdGhlIG1heGltdW0gYWRqdXN0bWVudCB0byBpdHMgaW50ZXJuYWwgY2xvY2sg
d2l0aGluIG9uZSBzeW5jCiAgICAgaW50ZXJ2YWwuICBUaGUgbWF4aW11bSBwaGFzZSBhZGp1c3Rt
ZW50IGlzIGluZGljYXRlZCBpbiB0aGUgCiAgICAgRW50ZXJwcmlzZSBQcm9maWxlIGFubm91bmNl
IFRMViBmaWVsZCBmb3IgTWF4aW11bSBQaGFzZSBBZGp1c3RtZW50LgoKICAgICAKQXJub2xkIGFu
ZCBHZXJzdHVuZyAgICAgICAgICAgICAgIE9jdG9iZXIgMTUsIDIwMTMgICAgICAgICAgICAgIFtQ
YWdlIDhdCgwKCkludGVybmV0LURyYWZ0ICAgICAgICAgIEVudGVycHJpc2UgUHJvZmlsZSBmb3Ig
UFRQICAgICAgICAgICAgICBPY3QgMjAxMyAgIAoKICAgICBUaGUgQW5ub3VuY2UgTWVzc2FnZXMg
U0hBTEwgaW5jbHVkZSBhIFRMViB3aGljaCBpbmRpY2F0ZXMgdGhhdCB0aGUKICAgICBjbG9jayBp
cyBvcGVyYXRpbmcgaW4gdGhlIEVudGVycHJpc2UgUHJvZmlsZS4gIFRoZSBUTFYgc2hhbGwgaGF2
ZQogICAgIHRoZSBmb2xsb3dpbmcgc3RydWN0dXJlOgoKICAgICBUTFYgVHlwZSAoRW51bWVyYXRp
b24xNik6IE9SR0FOSVpBVElPTl9FWFRFTlNJT04gdmFsdWUgPSAwMDAzIGhleAoKICAgICBMZW5n
dGggRmllbGQgKFVJbnRlZ2VyMTYpOiB2YWx1ZSA9IDEyLiBUaGUgbnVtYmVyIG9mIFRMViBvY3Rl
dHMKICAgICAKICAgICBQb3J0IE51bWJlciAoVUludGVnZXIxNik6IFRoZSBQb3J0IE51bWJlciBv
ZiB0aGUgcG9ydCB0cmFuc21pdHRpbmcKICAgICB0aGUgVExWLiBUaGUgYWxsLW9uZXMgUG9ydCBO
dW1iZXIsIHdpdGggdmFsdWUgRkZGRmhleCwgaXMgdXNlZCB0byAKICAgICBpbmRpY2F0ZSB0aGF0
IHRoZSBpZGVudGlmaWVkIHByb2ZpbGUgaXMgYXBwbGljYWJsZSB0byBhbGwgcG9ydHMgb24gCiAg
ICAgdGhlIGNsb2NrLgoKICAgICBPcmdhbml6YXRpb24gVW5pcXVlIElkZW50aWZpZXIgKDMgT2N0
ZXRzKTogVGhlIE9yZ2FuaXphdGlvbiBJRCAKICAgICB2YWx1ZSBmb3IgSUVURiBhc3NpZ25lZCBi
eSBJRUVFID0gMDAwMDVFaGV4CiAgICAgCiAgICAgSUVURiBQcm9maWxlIG51bWJlciAoVUludGVn
ZXIxNik6IHZhbHVlID0gMQogICAgIAogICAgIFJldmlzaW9uIG51bWJlciAoVUludGVnZXI4KTog
dmFsdWUgPSAxCgogICAgIERlbGF5IE1lYXN1cmVtZW50IE1vZGUgKEVudW1lcmF0aW9uOCk6CiAg
ICAgICAgICAgICAgIFZhbHVlIDAgPSBNdWx0aWNhc3QgRGVsYXkgTWVhc3VyZW1lbnQgTW9kZQog
ICAgICAgICAgICAgICBWYWx1ZSAxID0gVW5pY2FzdCBEZWxheSBNZWFzdXJlbWVudCBNb2RlCiAg
ICAgICAgICAgICAgIFZhbHVlIDIgPSBIeWJyaWQgRGVsYXkgTWVhc3VyZW1lbnQgTW9kZQogICAg
ICAgICAgICAgICBWYWx1ZXMgMy0yNTUgPSByZXNlcnZlZCBmb3IgZnV0dXJlIHVzZS4KICAgICAK
ICAgICBNYXhpbXVtIEFic29sdXRlIFBoYXNlIEFkanVzdG1lbnQgVmFsdWUgIHdpdGhpbiBvbmUg
c3luYyBpbnRlcnZhbAogICAgIChVSW50ZWdlcjE2KTogdmFsdWUKICAgICAKICAgICBNYXhpbXVt
IFBoYXNlIEFkanVzdG1lbnQgVW5pdHMgKEVudW1lcmF0aW9uOCk6CiAgICAgICAgICAgICAgIFZh
bHVlIDAgPSB1bmtub3duCiAgICAgICAgICAgICAgIFZhbHVlIDEgPSBzZWNvbmRzCiAgICAgICAg
ICAgICAgIFZhbHVlIDMgPSBtaWxsaXNlY29uZHMKICAgICAgICAgICAgICAgVmFsdWUgNiA9IG1p
Y3Jvc2Vjb25kcwogICAgICAgICAgICAgICBWYWx1ZSA5ID0gbmFub3NlY29uZHMKICAgICAgICAg
ICAgICAgVmFsdWUgMTIgPSBwaWNvc2Vjb25kcwogICAgICAgICAgICAgICBWYWx1ZSAxNSA9IGZl
bXRvc2Vjb25kcwogICAgICAgICAgICAgICBBbGwgb3RoZXIgdmFsdWVzIHJlc2VydmVkIGZvciBm
dXR1cmUgdXNlCiAgICAgICAgICAgICAgIAoKICAgICBUaGUgVExWIHJlcHJlc2VudHMgdGhlIERl
bGF5IFJlcXVlc3QgTW9kZSBvZiB0aGUgTWFzdGVyLCBub3QKICAgICBuZWNlc3NhcmlseSB0aGUg
R3JhbmRtYXN0ZXIuIFNvIGZvciBleGFtcGxlLCBvbmUgcG9ydCBvZiBhCiAgICAgQm91bmRhcnkg
Y2xvY2sgY291bGQgYmUgc2V0IHRvIFVuaWNhc3QgRGVsYXkgTWVhc3VyZW1lbnQgTW9kZSwKICAg
ICB3aGlsZSB0aGUgcmVzdCBvZiB0aGUgbmV0d29yayBpcyBIeWJyaWQgRGVsYXkgTWVhc3VyZW1l
bnQgTW9kZS4KCgpBcm5vbGQgYW5kIEdlcnN0dW5nICAgICAgICAgICAgICAgT2N0b2JlciAxNSwg
MjAxMyAgICAgICAgICAgICAgW1BhZ2UgOV0KDAoKSW50ZXJuZXQtRHJhZnQgICAgICAgICAgRW50
ZXJwcmlzZSBQcm9maWxlIGZvciBQVFAgICAgICAgICAgICAgIE9jdCAyMDEzCjkuICAgICBSZXF1
aXJlbWVudHMgZm9yIFNsYXZlIENsb2NrcwoKICAgICBTbGF2ZSBjbG9ja3MgTVVTVCBiZSBhYmxl
IHRvIG9wZXJhdGUgcHJvcGVybHkgaW4gYSBuZXR3b3JrIHdoaWNoCiAgICAgY29udGFpbnMgQWx0
ZXJuYXRlIE1hc3RlcnMuICBTbGF2ZXMgU0hPVUxEIG1ha2UgdXNlIG9mIGluZm9ybWF0aW9uCiAg
ICAgZnJvbSB0aGUgQWx0ZXJuYXRlIE1hc3RlcnMgaW4gdGhlaXIgY2xvY2sgY29udHJvbCBzdWJz
eXN0ZW1zLgogICAgIFNsYXZlIENsb2NrcyBNVVNUIGJlIGFibGUgdG8gb3BlcmF0ZSBwcm9wZXJs
eSBpbiB0aGUgcHJlc2VuY2Ugb2YgYQogICAgIFJvZ3VlIE1hc3Rlci4gIFNsYXZlcyBTSE9VTEQg
Tk9UIFN5bmNocm9uaXplIHRvIGEgUm9ndWUgTWFzdGVyLgogICAgIFNsYXZlcyBNQVkgdXNlIGFu
IEFjY2VwdGFibGUgTWFzdGVyIFRhYmxlLiAgSWYgdGhlIEJlc3QgTWFzdGVyIGlzCiAgICAgbm90
IGFuIEFjY2VwdGFibGUgTWFzdGVyLCBidXQgYW4gQWx0ZXJuYXRlIE1hc3RlciBpcyBhbiBBY2Nl
cHRhYmxlCiAgICAgTWFzdGVyLCB0aGVuIHRoZSBTbGF2ZSBTSE9VTEQgc3luY2hyb25pemUgdG8g
dGhlIGFjY2VwdGFibGUKICAgICBBbHRlcm5hdGUgTWFzdGVyLiBOb3RlIHRoYXQgSUVFRSAxNTg4
LTIwMDggcmVxdWlyZXMgc2xhdmUgY2xvY2tzIHRvCiAgICAgc3VwcG9ydCBib3RoIHR3by1zdGVw
IG9yIG9uZS1zdGVwIE1hc3RlciBjbG9ja3MuICBTZWUgW0lFRUUxNTg4XSwgCiAgICAgc2VjdGlv
biAxMS4yLgoKICAgICBTaW5jZSBBbm5vdW5jZSBtZXNzYWdlcyBhcmUgc2VudCBhcyBtdWx0aWNh
c3QgbWVzc2FnZXMgaW4gYWxsCiAgICAgbW9kZSwgc2xhdmVzIGNhbiBvYnRhaW4gdGhlIElQIGFk
ZHJlc3NlcyBvZiBtYXN0ZXIgZnJvbSB0aGUKICAgICBBbm5vdW5jZSBtZXNzYWdlcy4gIE5vdGUg
dGhhdCB0aGUgSVAgc291cmNlIGFkZHJlc3NlcyBvZiBTeW5jIGFuZAogICAgIEZvbGxvdy11cCBt
ZXNzYWdlcyBtYXkgaGF2ZSBiZWVuIHJlcGxhY2VkIGJ5IHRoZSBzb3VyY2UgYWRkcmVzc2VzCiAg
ICAgb2YgYSB0cmFuc3BhcmVudCBjbG9jaywgc28gc2xhdmVzIE1VU1Qgc2VuZCBEZWxheSBSZXF1
ZXN0IG1lc3NhZ2VzCiAgICAgdG8gdGhlIElQIGFkZHJlc3MgaW4gdGhlIEFubm91bmNlIG1lc3Nh
Z2UuICBTeW5jIGFuZCBGb2xsb3ctdXAKICAgICBtZXNzYWdlcyBjYW4gYmUgY29ycmVsYXRlZCB3
aXRoIHRoZSBBbm5vdW5jZSBtZXNzYWdlIHVzaW5nIHRoZQogICAgIGNsb2NrIElELCB3aGljaCBp
cyBuZXZlciBhbHRlcmVkIGJ5IFRyYW5zcGFyZW50IGNsb2Nrcy4KCiAgICAgCjEwLiAgICAgUmVx
dWlyZW1lbnRzIGZvciBUcmFuc3BhcmVudCBDbG9ja3MKCgogICAgIFRyYW5zcGFyZW50IGNsb2Nr
cyBTSEFMTCBOT1QgY2hhbmdlIHRoZSB0cmFuc21pc3Npb24gbW9kZSBvZiBhbgogICAgIEVudGVy
cHJpc2UgcHJvZmlsZSBQVFAgbWVzc2FnZS4gIEZvciBleGFtcGxlIGEgVHJhbnNwYXJlbnQgY2xv
Y2sKICAgICBTSEFMTCBOT1QgY2hhbmdlIGEgdW5pY2FzdCBtZXNzYWdlIHRvIGEgbXVsdGljYXN0
IG1lc3NhZ2UuCiAgICAgVHJhbnNwYXJlbnQgY2xvY2tzIFNIQUxMIE5PVCBhbHRlciB0aGUgRW50
ZXJwcmlzZSBQcm9maWxlIFRMViBvZgogICAgIGFuIEFubm91bmNlIG1lc3NhZ2UsIG9yIGFueSBv
dGhlciBwYXJ0IG9mIGFuIEFubm91bmNlIG1lc3NhZ2UuCgogICAgIAoxMS4gICAgIE1hbmFnZW1l
bnQgYW5kIFNpZ25hbGluZyBNZXNzYWdlcwoKICAgIFBUUCBNYW5hZ2VtZW50IG1lc3NhZ2VzIE1B
WSBiZSB1c2VkLiAgQW55IFBUUCBtYW5hZ2VtZW50IG1lc3NhZ2UKICAgIHdoaWNoIGlzIHNlbnQg
d2l0aCB0aGUgdGFyZ2V0UG9ydElkZW50aXR5LmNsb2NrSWRlbnRpdHkgc2V0IHRvIGFsbAogICAg
MXMgKGFsbCBjbG9ja3MpIE1VU1QgYmUgc2VudCBhcyBhIG11bHRpY2FzdCBtZXNzYWdlLiAgTWFu
YWdlbWVudAogICAgbWVzc2FnZXMgd2l0aCBhbnkgb3RoZXIgdmFsdWUgb2YgZm9yIHRoZSBDbG9j
ayBJZGVudGl0eSBpcwogICAgaW50ZW5kZWQgZm9yIGEgc3BlY2lmaWMgY2xvY2sgYW5kIE1VU1Qg
YmUgc2VudCBhcyBhIHVuaWNhc3QKICAgIG1lc3NhZ2UuICBTaW1pbGFybHksIGlmIGFueSBzaWdu
YWxpbmcgbWVzc2FnZXMgYXJlIHVzZWQgdGhleQogICAgTVVTVCBhbHNvIGJlIHNlbnQgYXMgdW5p
Y2FzdCBtZXNzYWdlcyB3aGVuZXZlciB0aGUgbWVzc2FnZSBpcwogICAgaW50ZW5kZWQgZm9yIGEg
c3BlY2lmaWMgY2xvY2suCgogICAgCgpBcm5vbGQgYW5kIEdlcnN0dW5nICAgICAgICAgICAgICAg
T2N0b2JlciAxNSwgMjAxMyAgICAgICAgICAgICBbUGFnZSAxMF0KDAoKSW50ZXJuZXQtRHJhZnQg
ICAgICAgICAgRW50ZXJwcmlzZSBQcm9maWxlIGZvciBQVFAgICAgICAgICAgICAgIE9jdCAyMDEz
CgoxMi4gICAgIEZvcmJpZGRlbiBQVFAgT3B0aW9ucwoKICAgICBDbG9ja3Mgb3BlcmF0aW5nIGlu
IHRoZSBFbnRlcnByaXNlIFByb2ZpbGUgU0hBTEwgTk9UIHVzZSBwZWVyIHRvCiAgICAgcGVlciB0
aW1pbmcgZm9yIGRlbGF5IG1lYXN1cmVtZW50LiAgQ2xvY2tzIG9wZXJhdGluZyBpbiB0aGUKICAg
ICBFbnRlcnByaXNlIFByb2ZpbGUgU0hBTEwgTk9UIHVzZSBVbmljYXN0IE1lc3NhZ2UgTmVnb3Rp
YXRpb24gdG8KICAgICBkZXRlcm1pbmUgbWVzc2FnZSByYXRlcy4gU2xhdmUgY2xvY2tzIG9wZXJh
dGluZyBpbiB0aGUgRW50ZXJwcmlzZQogICAgIFByb2ZpbGUgU0hBTEwgTk9UIHVzZSBVbmljYXN0
IERpc2NvdmVyeSB0byBlc3RhYmxpc2ggY29ubmVjdGlvbiB0bwogICAgIE1hc3RlciBjbG9ja3Mu
ICBHcmFuZG1hc3RlciBDbHVzdGVycyBhcmUgTk9UIEFMTE9XRUQuIENsb2NrcwogICAgIG9wZXJh
dGluZyBpbiB0aGUgRW50ZXJwcmlzZSBQcm9maWxlIFNIQUxMIE5PVCB1c2UgQWx0ZXJuYXRpdmUg
VGltZQogICAgIFNjYWxlcy4KCiAgICAgCjEzLiAgICAgSW50ZXJvcGVyYXRpb24gd2l0aCBPdGhl
ciBQVFAgUHJvZmlsZXMKCiAgICAgQ2xvY2tzIG9wZXJhdGluZyBpbiB0aGUgRW50ZXJwcmlzZSBw
cm9maWxlIHdpbGwgbm90IGludGVyb3BlcmF0ZQogICAgIHdpdGggY2xvY2tzIG9wZXJhdGluZyBp
biB0aGUgUG93ZXIgUHJvZmlsZSBbQzM3LjIzOF0sIGJlY2F1c2UgdGhlCgogICAgIEVudGVycHJp
c2UgUHJvZmlsZSByZXF1aXJlcyB0aGUgRW5kIHRvIEVuZCBEZWxheSBNZWFzdXJlbWVudAogICAg
IE1lY2hhbmlzbSBhbmQgdGhlIFBvd2VyIFByb2ZpbGUgcmVxdWlyZXMgdGhlIFBlZXIgdG8gUGVl
ciBEZWxheQogICAgIE1lYXN1cmVtZW50IE1lY2hhbmlzbS4KCiAgICAgQ2xvY2tzIG9wZXJhdGlu
ZyBpbiB0aGUgRW50ZXJwcmlzZSBwcm9maWxlIHdpbGwgbm90IGludGVyb3BlcmF0ZQogICAgIHdp
dGggY2xvY2tzIG9wZXJhdGluZyBpbiB0aGUgVGVsZWNvbSBQcm9maWxlIGZvciBGcmVxdWVuY3kK
ICAgICBTeW5jaHJvbml6YXRpb25bRzgyNjUuMV0sIGJlY2F1c2UgdGhlIEVudGVycHJpc2UgUHJv
ZmlsZSBmb3JiaWRzCiAgICAgVW5pY2FzdCBNZXNzYWdlIE5lZ290aWF0aW9uLCBhbmQgVW5pY2Fz
dCBEaXNjb3ZlcnkuICBUaGVzZQogICAgIGZlYXR1cmVzIGFyZSBwYXJ0IG9mIHRoZSBkZWZhdWx0
IG1hbm5lciBvZiBvcGVyYXRpb24gZm9yIHRoZQogICAgIFRlbGVjb20gUHJvZmlsZSBmb3IgRnJl
cXVlbmN5IFN5bmNocm9uaXphdGlvbi4KCiAgICAgQ2xvY2tzIG9wZXJhdGluZyBpbiB0aGUgRW50
ZXJwcmlzZSBwcm9maWxlIHdpbGwgaW50ZXJvcGVyYXRlIHdpdGgKICAgICBjbG9ja3Mgb3BlcmF0
aW5nIGluIHRoZSBkZWZhdWx0IHByb2ZpbGUgaWYgdGhlIGRlZmF1bHQgcHJvZmlsZQogICAgIGNs
b2NrcyBvcGVyYXRlIG9uIElQdjQgb3IgSVB2NiBuZXR3b3JrcywgdXNlIHRoZSBFbmQgdG8gRW5k
IERlbGF5CiAgICAgTWVhc3VyZW1lbnQgTWVjaGFuaXNtLCBhbmQgdXNlIG1hbmFnZW1lbnQgbWVz
c2FnZXMgaW4gdW5pY2FzdCB3aGVuCiAgICAgdGhvc2UgbWVzc2FnZXMgYXJlIGRpcmVjdGVkIGF0
IGEgc3BlY2lmaWMgY2xvY2suICBJZiBhbnkgb2YgdGhlc2UKICAgICByZXF1aXJlbWVudHMgYXJl
IG5vdCBtZXQgdGhhbiBFbnRlcnByaXNlIFByb2ZpbGUgY2xvY2tzIHdpbGwgbm90CiAgICAgaW50
ZXJvcGVyYXRlIHdpdGggRGVmYXVsdCBQcm9maWxlIENsb2Nrcy4gIFRoZSBEZWZhdWx0IFByb2Zp
bGUgaXMKICAgICBkZXNjcmliZWQgaW4gQW5uZXggSiBvZiBbSUVFRTE1ODhdLgoKICAgICBFbnRl
cnByaXNlIFByb2ZpbGUgQ2xvY2tzIHdpbGwgaW50ZXJvcGVyYXRlIHdpdGggY2xvY2tzIG9wZXJh
dGluZwogICAgIGluIG90aGVyIHByb2ZpbGVzIGlmIHRoZSBjbG9ja3MgaW4gdGhlIG90aGVyIHBy
b2ZpbGVzIG9iZXkgdGhlCiAgICAgcnVsZXMgb2YgdGhlIEVudGVycHJpc2UgUHJvZmlsZS4gIFRo
ZXNlIHJ1bGVzIE1VU1QgTk9UIGJlIGNoYW5nZWQKICAgICB0byBhY2hpZXZlIGludGVyb3BlcmFi
aWxpdHkgd2l0aCBvdGhlciBwcm9maWxlcy4KCiAgICAgCjE0LiAgICAgU2VjdXJpdHkgQ29uc2lk
ZXJhdGlvbnMKCiAgICAgUHJvdG9jb2xzIHVzZWQgdG8gdHJhbnNmZXIgdGltZSwgc3VjaCBhcyBQ
VFAgYW5kIE5UUCBjYW4gYmUKICAgICBpbXBvcnRhbnQgdG8gc2VjdXJpdHkgbWVjaGFuaXNtcyB3
aGljaCB1c2UgdGltZSB3aW5kb3dzIGZvciBrZXlzCiAgICAgYW5kIGF1dGhvcml6YXRpb24uIFBh
c3NpbmcgdGltZSB0aHJvdWdoIHRoZSBuZXR3b3JrcyBwb3NlcyBhCiAgICAgc2VjdXJpdHkgcmlz
ayBzaW5jZSB0aW1lIGNhbiBwb3RlbnRpYWxseSBiZSBtYW5pcHVsYXRlZC4KCgpBcm5vbGQgYW5k
IEdlcnN0dW5nICAgICAgICAgICAgICAgT2N0b2JlciAxNSwgMjAxMyAgICAgICAgICAgICBbUGFn
ZSAxMV0KDAoKSW50ZXJuZXQtRHJhZnQgICAgICAgICAgRW50ZXJwcmlzZSBQcm9maWxlIGZvciBQ
VFAgICAgICAgICAgICAgIE9jdCAyMDEzCgkJCQkJIAogICAgIFRoZSB1c2Ugb2YgbXVsdGlwbGUg
c2ltdWx0YW5lb3VzIG1hc3RlcnMsIHVzaW5nIHRoZSBJRUVFIDE1ODgKICAgICBBbHRlcm5hdGUg
TWFzdGVyIG9wdGlvbiBjYW4gbWl0aWdhdGUgcHJvYmxlbXMgZnJvbSByb2d1ZSBtYXN0ZXJzCiAg
ICAgYW5kIG1hbi1pbi10aGUtbWlkZGxlIGF0dGFja3MuICBTZWUgc2VjdGlvbnMgOSBhbmQgMTAu
IEFkZGl0aW9uYWwKICAgICBzZWN1cml0eSBtZWNoYW5pc21zIGFyZSBvdXRzaWRlIHRoZSBzY29w
ZSBvZiB0aGlzIGRvY3VtZW50LgogICAgICAgICAgIAoxNS4gICAgIElBTkEgQ29uc2lkZXJhdGlv
bnMKCiAgICAgVGhlcmUgYXJlIG5vIElBTkEgcmVxdWlyZW1lbnRzIGluIHRoaXMgc3BlY2lmaWNh
dGlvbi4KCgoxNi4gICAgIFJlZmVyZW5jZXMKCjE2LjEuICAgICAgTm9ybWF0aXZlIFJlZmVyZW5j
ZXMKCiAgICAgICAgICAgW0lFRUUxNTg4XSBJRUVFIHN0ZC4gMTU4OC0yMDA4LCAiSUVFRSBTdGFu
ZGFyZCBmb3IgYSAKICAgICAgICAgICAgICAgICAgICAgIFByZWNpc2lvbiBDbG9jayBTeW5jaHJv
bml6YXRpb24gZm9yIE5ldHdvcmtlZAogICAgICAgICAgICAgICAgICAgICAgTWVhc3VyZW1lbnQg
YW5kIENvbnRyb2wgU3lzdGVtcy4iIEp1bHksIDIwMDguIAogICAgICAgICAgIFtSRkM3NjhdICAg
UG9zdGVsLCBKLiwgIlVzZXIgRGF0YWdyYW0gUHJvdG9jb2wsIiBSRkMgNzY4LAogICAgICAgICAg
ICAgICAgICAgICAgQXVndXN0LCA5ODAuCgkJCQkJIAogICAgICAgICAgIFtSRkM3OTFdICAgIklu
dGVybmV0IFByb3RvY29sIERBUlBBIEludGVybmV0IFByb2dyYW0gUHJvdG9jb2wKICAgICAgICAg
ICAgICAgICAgICAgIFNwZWNpZmljYXRpb24sIiBSRkMgNzkxLCBTZXB0ZW1iZXIsIDE5ODEuCgkJ
CQkJIAogICAgICAgICAgIFtSRkMyMTE5XSAgQnJhZG5lciwgUy4sICJLZXkgd29yZHMgZm9yIHVz
ZSBpbiBSRkNzIHRvCiAgICAgICAgICAgICAgICAgICAgICBJbmRpY2F0ZSBSZXF1aXJlbWVudCBM
ZXZlbHMiLCBCQ1AgMTQsIFJGQyAyMTE5LAogICAgICAgICAgICAgICAgICAgICAgTWFyY2ggMTk5
Ny4KCQkJCQkgCiAgICAgICAgICAgW1JGQzI0NjBdICBEZWVyaW5nLCBTLiwgSGluZGVuLCBSLiwg
IkludGVybmV0IFByb3RvY29sLAogICAgICAgICAgICAgICAgICAgICAgVmVyc2lvbiA2IChJUHY2
KSBTcGVjaWZpY2F0aW9uLCIgUkZDIDI0NjAsIAogICAgICAgICAgICAgICAgICAgICAgRGVjZW1i
ZXIsIDE5OTguCgoxNi4yLiAgICAgIEluZm9ybWF0aXZlIFJlZmVyZW5jZXMKCiAgICAgICAgICAg
W0MzNy4yMzhdICBJRUVFIHN0ZC4gQzM3LjIzOC0yMDExLCAiSUVFRSBTdGFuZGFyZCBQcm9maWxl
IGZvcgogICAgICAgICAgICAgICAgICAgICAgVXNlIG9mIElFRUUgMTU4OCBQcmVjaXNpb24gVGlt
ZSBQcm90b2NvbCBpbiBQb3dlcgogICAgICAgICAgICAgICAgICAgICAgU3lzdGVtIEFwcGxpY2F0
aW9ucywiIEp1bHkgMjAxMS4KCiAgICAgICAgICAgW0c4MjY1LjFdICBJVFUtVCBHLjgyNjUuMS9Z
LjEzNjUuMSwgIlByZWNpc2lvbiB0aW1lIHByb3RvY29sCiAgICAgICAgICAgICAgICAgICAgICB0
ZWxlY29tIHByb2ZpbGUgZm9yIGZyZXF1ZW5jeSBzeW5jaHJvbml6YXRpb24sIgogICAgICAgICAg
ICAgICAgICAgICAgT2N0b2JlciAyMDExLgoKICAgICAgICAgICBbRzgyNzFdICAgIElUVS1UIEcu
ODI3MS9ZLjEzNjYsICJUaW1lIGFuZCBQaGFzZQogICAgICAgICAgICAgICAgICAgICAgU3luY2hy
b25pemF0aW9uIEFzcGVjdHMgb2YgUGFja2V0IE5ldHdvcmtzIgogICAgICAgICAgICAgICAgICAg
ICAgRmVicnVhcnksIDIwMTIuCgogICAgICAgICAgIFtOVFBdICAgICAgTWlsbHMsIEQuLCBNYXJ0
aW4sIEouLCBCdXJiYW5rLCBKLiwgS2FzY2gsIFcuLAogICAgICAgICAgICAgICAgICAgICAgIk5l
dHdvcmsgVGltZSBQcm90b2NvbCBWZXJzaW9uIDQ6IFByb3RvY29sIGFuZAogICAgICAgICAgICAg
ICAgICAgICAgQWxnb3JpdGhtcyBTcGVjaWZpY2F0aW9uLCIgUkZDIDU5MDUsIEp1bmUgMjAxMC4K
CgpBcm5vbGQgYW5kIEdlcnN0dW5nICAgICAgICAgICAgICBPY3RvYmVyIDE1LCAyMDEzICAgICAg
ICAgICAgICBbUGFnZSAxMl0KDAoKSW50ZXJuZXQtRHJhZnQgICAgICAgICAgIEVudGVycHJpc2Ug
UHJvZmlsZSBmb3IgUFRQICAgICAgICAgICAgIE9jdCAyMDEzCjE3LiAgICAgIEFja25vd2xlZGdt
ZW50cwoKICAgICBUaGUgYXV0aG9ycyB3b3VsZCBsaWtlIHRvIHRoYW5rIG1lbWJlcnMgb2YgSUVU
RiBmb3IgcmV2aWV3aW5nIGFuZAogICAgIHByb3ZpZGluZyBmZWVkYmFjayBvbiB0aGlzIGRyYWZ0
LgoKICAgICBUaGlzIGRvY3VtZW50IHdhcyBwcmVwYXJlZCB1c2luZyAyLVdvcmQtdjIuMC50ZW1w
bGF0ZS5kb3QuCgoKMTguICAgICBBdXRob3JzJyBBZGRyZXNzZXMKCiAgICAgRG91ZyBBcm5vbGQK
ICAgICBNZWluYmVyZyBVU0EKICAgICAyMjggV2luZHNvciBSaXZlciBSZAogICAgIFdpbmRzb3Is
IENBIDk1NDkyCiAgICAgVVNBCgogICAgIEVtYWlsOiBkb3VnLmFybm9sZEBtZWluYmVyZy11c2Eu
Y29tCgoKICAgICBIZWlrbyBHZXJzdHVuZwogICAgIE1laW5iZXJnIEZ1bmt1aHJlbiBHbWJIICYg
Q28uIEtHCiAgICAgTGFuZ2UgV2FuZCA5CiAgICAgRC0zMTgxMiBCYWQgUHlybW9udAogICAgIEdl
cm1hbnkKCiAgICAgRW1haWw6IEhlaWtvLmdlcnN0dW5nQG1laW5iZXJnLmRlCgoKQXJub2xkIGFu
ZCBHZXJzdHVuZyAgICAgICAgICAgICAgIE9jdG9iZXIgMTUsIDIwMTMgICAgICAgICAgICAgW1Bh
Z2UgMTNdCg==
--001a11c30a844563a804e985ec3e--

From John.Fletcher@bbc.co.uk  Fri Oct 25 03:01:25 2013
Return-Path: <John.Fletcher@bbc.co.uk>
X-Original-To: tictoc@ietfa.amsl.com
Delivered-To: tictoc@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A5C8411E8387 for <tictoc@ietfa.amsl.com>; Fri, 25 Oct 2013 03:01:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.109
X-Spam-Level: 
X-Spam-Status: No, score=-9.109 tagged_above=-999 required=5 tests=[BAYES_05=-1.11, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id msVPZ8TrFZvU for <tictoc@ietfa.amsl.com>; Fri, 25 Oct 2013 03:01:20 -0700 (PDT)
Received: from mailout0.mh.bbc.co.uk (mailout0.mh.bbc.co.uk [132.185.144.151]) by ietfa.amsl.com (Postfix) with ESMTP id D77B311E80FA for <tictoc@ietf.org>; Fri, 25 Oct 2013 03:01:19 -0700 (PDT)
Received: from BGB01XI1002.national.core.bbc.co.uk ([10.184.50.52]) by mailout0.mh.bbc.co.uk (8.14.4/8.14.3) with ESMTP id r9PA1FJp025295;  Fri, 25 Oct 2013 11:01:15 +0100 (BST)
Received: from BGB01XI1016.national.core.bbc.co.uk (10.161.14.79) by BGB01XI1002.national.core.bbc.co.uk (10.184.50.52) with Microsoft SMTP Server (TLS) id 14.2.342.4; Fri, 25 Oct 2013 11:01:14 +0100
Received: from BGB01XUD1002.national.core.bbc.co.uk ([169.254.11.105]) by BGB01XI1016.national.core.bbc.co.uk ([10.161.14.79]) with mapi id 14.02.0342.004; Fri, 25 Oct 2013 11:01:14 +0100
From: John Fletcher <John.Fletcher@bbc.co.uk>
To: Douglas Arnold <doug.arnold@meinberg-usa.com>
Thread-Topic: [TICTOC] Enterprise Profile
Thread-Index: AQHO0Tj+EfJkN9q+/USLYOoP7dIkB5oFJTNg
Date: Fri, 25 Oct 2013 10:01:11 +0000
Message-ID: <B1D49063AD5FBD4688F3EEDEC68B201751132BDF@BGB01XUD1002.national.core.bbc.co.uk>
References: <CACQYgzFmOtFY+Td0jZMyykeZ17KwAuCc+LY+C2be_UPgZKh9GA@mail.gmail.com>
In-Reply-To: <CACQYgzFmOtFY+Td0jZMyykeZ17KwAuCc+LY+C2be_UPgZKh9GA@mail.gmail.com>
Accept-Language: en-GB, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.162.14.18]
Content-Type: multipart/alternative; boundary="_000_B1D49063AD5FBD4688F3EEDEC68B201751132BDFBGB01XUD1002nat_"
MIME-Version: 1.0
X-EXCLAIMER-MD-CONFIG: c91d45b2-6e10-4209-9543-d9970fac71b7
X-EXCLAIMER-MD-CONFIG: 1cd3ac1c-62e5-43f2-8404-6b688271c769
Cc: "tictoc@ietf.org" <tictoc@ietf.org>
Subject: Re: [TICTOC] Enterprise Profile
X-BeenThere: tictoc@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Timing over IP Connection and Transfer of Clock BOF <tictoc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tictoc>, <mailto:tictoc-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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>
X-List-Received-Date: Fri, 25 Oct 2013 10:01:26 -0000

--_000_B1D49063AD5FBD4688F3EEDEC68B201751132BDFBGB01XUD1002nat_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Doug,

I would be interested to know the circumstances when you see the maximum ph=
ase adjustment information being used.

Some comments:

In section 6, you say, "In all three of the delay measurement modes...".  A=
t that point in the text you have not yet mentioned multicast, hybrid and u=
nicast modes so it's not clear which modes you are referring to.

In section 9, you say, "Slaves SHOULD NOT Synchronize to a Rogue Master."  =
It's not clear how a slave would know that a master is rogue; presumably it=
 would need to examine the announce messages of all masters and do its own =
BMCA evaluation.  A more realistic "rogue" master would probably meet the B=
MCA criteria for selection.

In section 12, "Alternative Time Scales" should be "Alternate Timescales".


Regards,
John Fletcher

From: tictoc-bounces@ietf.org [mailto:tictoc-bounces@ietf.org] On Behalf Of=
 Douglas Arnold
Sent: 25 October 2013 01:35
To: tictoc@ietf.org
Subject: [TICTOC] Enterprise Profile

Hello Everyone,

Attached is an updated version of the Enterprise profile.  Sorry I missed t=
he upload deadline for  the Vancouver meeting.  If you get a chance to look=
 at it before then I will be there and would love to discuss it.

Summary of changes:

I also changed the TLV format to fit the latest proposal in the 1588 revisi=
on.

I added a statement about not going into the master state unless one had a =
current UTC offset.

I added to the TLV fields to indicate maximum phase correction over a sync =
cycle.

--
Doug Arnold
Principal Technologist
JTime! Meinberg USA
+1-707-303-5559





----------------------------

http://www.bbc.co.uk
This e-mail (and any attachments) is confidential and may contain personal =
views which are not the views of the BBC unless specifically stated.
If you have received it in error, please delete it from your system.
Do not use, copy or disclose the information in any way nor act in reliance=
 on it and notify the sender immediately.
Please note that the BBC monitors e-mails sent or received.
Further communication will signify your consent to this.

---------------------

--_000_B1D49063AD5FBD4688F3EEDEC68B201751132BDFBGB01XUD1002nat_
Content-Type: text/html; charset="utf-8"
Content-Transfer-Encoding: quoted-printable

<HTML xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40">
<HEAD><!-- Template generated by Exclaimer Mail Disclaimers on 11:01:15 Fri=
day, 25 October 2013 -->
<STYLE type=3Dtext/css>P.4aeb0e0f-c67f-42ce-bc35-6d175fcbd3cd {
	MARGIN: 0cm 0cm 0pt
}
LI.4aeb0e0f-c67f-42ce-bc35-6d175fcbd3cd {
	MARGIN: 0cm 0cm 0pt
}
DIV.4aeb0e0f-c67f-42ce-bc35-6d175fcbd3cd {
	MARGIN: 0cm 0cm 0pt
}
TABLE.4aeb0e0f-c67f-42ce-bc35-6d175fcbd3cdTable {
	MARGIN: 0cm 0cm 0pt
}
DIV.Section1 {
	page: Section1
}
</STYLE>

<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dutf-8" />
<meta name=3D"Generator" content=3D"Microsoft Word 14 (filtered medium)" />
<style><!--
/* Font Definitions */
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
span.EmailStyle17
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;
	mso-fareast-language:EN-US;}
@page WordSection1
	{size:612.0pt 792.0pt;
	margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
</HEAD>

<BODY lang=3D"EN-GB" link=3D"blue" vlink=3D"purple">
<P class=3D4aeb0e0f-c67f-42ce-bc35-6d175fcbd3cd>
<div class=3D"WordSection1">
<p class=3D"MsoNormal"><span style=3Dfont-size:11.0pt;font-family:&quot;Cal=
ibri&quot;,&quot;sans-serif&quot;;color:#1F497D>Doug,<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3Dfont-size:11.0pt;font-family:&quot;Cal=
ibri&quot;,&quot;sans-serif&quot;;color:#1F497D><o:p>&nbsp;</o:p></span></p=
>
<p class=3D"MsoNormal"><span style=3Dfont-size:11.0pt;font-family:&quot;Cal=
ibri&quot;,&quot;sans-serif&quot;;color:#1F497D>I would be interested to kn=
ow the circumstances when you see the maximum phase adjustment information =
being used.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3Dfont-size:11.0pt;font-family:&quot;Cal=
ibri&quot;,&quot;sans-serif&quot;;color:#1F497D><o:p>&nbsp;</o:p></span></p=
>
<p class=3D"MsoNormal"><span style=3Dfont-size:11.0pt;font-family:&quot;Cal=
ibri&quot;,&quot;sans-serif&quot;;color:#1F497D>Some comments:<o:p></o:p></=
span></p>
<p class=3D"MsoNormal"><span style=3Dfont-size:11.0pt;font-family:&quot;Cal=
ibri&quot;,&quot;sans-serif&quot;;color:#1F497D><o:p>&nbsp;</o:p></span></p=
>
<p class=3D"MsoNormal"><span style=3Dfont-size:11.0pt;font-family:&quot;Cal=
ibri&quot;,&quot;sans-serif&quot;;color:#1F497D>In section 6, you say, &#82=
20;In all three of the delay measurement modes&#8230;&#8221;.&nbsp; At that=
 point in the text you have not yet mentioned multicast, hybrid and unicast=
 modes
 so it&#8217;s not clear which modes you are referring to.<o:p></o:p></span=
></p>
<p class=3D"MsoNormal"><span style=3Dfont-size:11.0pt;font-family:&quot;Cal=
ibri&quot;,&quot;sans-serif&quot;;color:#1F497D><o:p>&nbsp;</o:p></span></p=
>
<p class=3D"MsoNormal"><span style=3Dfont-size:11.0pt;font-family:&quot;Cal=
ibri&quot;,&quot;sans-serif&quot;;color:#1F497D>In section 9, you say, &#82=
20;Slaves SHOULD NOT Synchronize to a Rogue Master.&#8221;&nbsp; It&#8217;s=
 not clear how a slave would know that a master is rogue; presumably it wou=
ld
 need to examine the announce messages of all masters and do its own BMCA e=
valuation.&nbsp; A more realistic &#8220;rogue&#8221; master would probably=
 meet the BMCA criteria for selection.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3Dfont-size:11.0pt;font-family:&quot;Cal=
ibri&quot;,&quot;sans-serif&quot;;color:#1F497D><o:p>&nbsp;</o:p></span></p=
>
<p class=3D"MsoNormal"><span style=3Dfont-size:11.0pt;font-family:&quot;Cal=
ibri&quot;,&quot;sans-serif&quot;;color:#1F497D>In section 12, &#8220;Alter=
native Time Scales&#8221; should be &#8220;Alternate Timescales&#8221;.<o:p=
></o:p></span></p>
<p class=3D"MsoNormal"><span style=3Dfont-size:11.0pt;font-family:&quot;Cal=
ibri&quot;,&quot;sans-serif&quot;;color:#1F497D><o:p>&nbsp;</o:p></span></p=
>
<p class=3D"MsoNormal"><span style=3Dfont-size:11.0pt;font-family:&quot;Cal=
ibri&quot;,&quot;sans-serif&quot;;color:#1F497D><o:p>&nbsp;</o:p></span></p=
>
<p class=3D"MsoNormal"><span style=3Dfont-size:11.0pt;font-family:&quot;Cal=
ibri&quot;,&quot;sans-serif&quot;;color:#1F497D>Regards,<o:p></o:p></span><=
/p>
<p class=3D"MsoNormal"><span style=3Dfont-size:11.0pt;font-family:&quot;Cal=
ibri&quot;,&quot;sans-serif&quot;;color:#1F497D>John Fletcher<o:p></o:p></s=
pan></p>
<p class=3D"MsoNormal"><span style=3Dfont-size:11.0pt;font-family:&quot;Cal=
ibri&quot;,&quot;sans-serif&quot;;color:#1F497D><o:p>&nbsp;</o:p></span></p=
>
<p class=3D"MsoNormal"><b><span lang=3D"EN-US" style=3Dfont-size:10.0pt;fon=
t-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;>From:</span></b><span la=
ng=3D"EN-US" style=3Dfont-size:10.0pt;font-family:&quot;Tahoma&quot;,&quot;=
sans-serif&quot;> tictoc-bounces@ietf.org [mailto:tictoc-bounces@ietf.org]
<b>On Behalf Of </b>Douglas Arnold<br />
<b>Sent:</b> 25 October 2013 01:35<br />
<b>To:</b> tictoc@ietf.org<br />
<b>Subject:</b> [TICTOC] Enterprise Profile<o:p></o:p></span></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<div>
<p class=3D"MsoNormal">Hello Everyone,<o:p></o:p></p>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<div>
<p class=3D"MsoNormal">Attached is an updated version of the Enterprise pro=
file. &nbsp;Sorry I missed the upload deadline for&nbsp;&nbsp;the Vancouver=
 meeting. &nbsp;If you get a chance to look at it before then I will be the=
re and would love to discuss it.&nbsp;<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<div>
<p class=3D"MsoNormal">Summary of changes:<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3Dfont-size:9.5pt;font-family:&quot;Aria=
l&quot;,&quot;sans-serif&quot;>I also changed the TLV format to fit the lat=
est proposal in the 1588 revision. &nbsp;</span><o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3Dfont-size:9.5pt;font-family:&quot;Aria=
l&quot;,&quot;sans-serif&quot;>I added a statement about not going into the=
 master state unless one had a current UTC offset. &nbsp;</span><o:p></o:p>=
</p>
</div>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3Dfont-size:9.5pt;font-family:&quot;Aria=
l&quot;,&quot;sans-serif&quot;>I added to the TLV fields to indicate maximu=
m phase correction over a sync cycle.</span><o:p></o:p></p>
</div>
<div>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<p class=3D"MsoNormal">-- <o:p></o:p></p>
<div>
<p class=3D"MsoNormal">Doug Arnold<o:p></o:p></p>
<div>
<p class=3D"MsoNormal">Principal Technologist<o:p></o:p></p>
<div>
<p class=3D"MsoNormal"><i>JTime!</i>&nbsp;Meinberg USA<o:p></o:p></p>
</div>
</div>
<div>
<p class=3D"MsoNormal">&#43;1-707-303-5559<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
</div>
</div>
</div>
</div>
</P>
<P class=3D4aeb0e0f-c67f-42ce-bc35-6d175fcbd3cd>&nbsp;</P>
<P class=3D4aeb0e0f-c67f-42ce-bc35-6d175fcbd3cd>---------------------------=
-<BR /><FONT size=3D3 face=3D"Times New Roman"><FONT size=3D3 face=3D"Times=
 New Roman"><FONT size=3D3 face=3D"Times New Roman"><BR /><FONT size=3D3 fa=
ce=3D"Times New Roman"><A href=3D"http://www.bbc.co.uk" target=3D_blank>htt=
p://www.<SPAN class=3Dil>bbc</SPAN>.<SPAN class=3Dil>co</SPAN>.<SPAN class=
=3Dil>uk</SPAN></A><BR />This e-mail (and any attachments) is confidential =
and=20
may contain personal views which are not the views of the <SPAN class=3Dil>=
BBC</SPAN> unless specifically stated.<BR />If you have received it in=20
error, please delete it from your system.<BR />Do not use, copy or disclose=
 the=20
information in any way nor act in reliance on it and notify the sender=20
immediately.<BR />Please note that the <SPAN class=3Dil>BBC</SPAN> monitors=
 e-mails=20
sent or received.<BR />Further communication will signify your consent to=20
this.</FONT></FONT></FONT></FONT></P>
<P class=3D4aeb0e0f-c67f-42ce-bc35-6d175fcbd3cd>---------------------</P></=
BODY>
</HTML>


--_000_B1D49063AD5FBD4688F3EEDEC68B201751132BDFBGB01XUD1002nat_--

From mayer@ntp.org  Sun Oct 27 12:19:25 2013
Return-Path: <mayer@ntp.org>
X-Original-To: tictoc@ietfa.amsl.com
Delivered-To: tictoc@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 22C8011E81C3 for <tictoc@ietfa.amsl.com>; Sun, 27 Oct 2013 12:19:25 -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]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ckJn58s1yLbW for <tictoc@ietfa.amsl.com>; Sun, 27 Oct 2013 12:19:24 -0700 (PDT)
Received: from mail1.ntp.org (mail1.ntp.org [IPv6:2001:4f8:fff7:1::5]) by ietfa.amsl.com (Postfix) with ESMTP id 6C06911E80E9 for <tictoc@ietf.org>; Sun, 27 Oct 2013 12:19:24 -0700 (PDT)
Received: from pool-173-76-231-254.bstnma.fios.verizon.net ([173.76.231.254] helo=[192.168.1.7]) by mail1.ntp.org with esmtpsa (TLSv1:CAMELLIA256-SHA:256) (Exim 4.77 (FreeBSD)) (envelope-from <mayer@ntp.org>) id 1VaVrn-000NWs-Sy; Sun, 27 Oct 2013 19:19:18 +0000
Message-ID: <526D671A.7050908@ntp.org>
Date: Sun, 27 Oct 2013 15:18:50 -0400
From: Danny Mayer <mayer@ntp.org>
Organization: NTP
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.0.1
MIME-Version: 1.0
To: Tal Mizrahi <talmi@marvell.com>,  "ntpwg@lists.ntp.org" <ntpwg@lists.ntp.org>, "tictoc@ietf.org" <tictoc@ietf.org>
References: <74470498B659FA4687F0B0018C19A89C01B87D7A40A6@IL-MB01.marvell.com> <526C30F9.1040400@ntp.org> <74470498B659FA4687F0B0018C19A89C01B87D7A4C6E@IL-MB01.marvell.com> <526D165D.3040902@ntp.org> <74470498B659FA4687F0B0018C19A89C01B87D7A4DC7@IL-MB01.marvell.com>
In-Reply-To: <74470498B659FA4687F0B0018C19A89C01B87D7A4DC7@IL-MB01.marvell.com>
X-Enigmail-Version: 1.6
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
X-SA-Exim-Connect-IP: 173.76.231.254
X-SA-Exim-Rcpt-To: talmi@marvell.com, ntpwg@lists.ntp.org, tictoc@ietf.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: Re: [TICTOC] [ntpwg] New version of draft-mizrahi-ntp-checksum-trailer
X-BeenThere: tictoc@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: mayer@ntp.org
List-Id: Timing over IP Connection and Transfer of Clock BOF <tictoc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tictoc>, <mailto:tictoc-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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>
X-List-Received-Date: Sun, 27 Oct 2013 19:19:25 -0000

On 10/27/2013 9:42 AM, Tal Mizrahi wrote:
> Hi Danny,
> 
>> That also means that the extension field MUST NOT be added by any intermediate nodes if it does not exist.
> 
> I am not sure we want to go there, for 2 reasons:
> 
> 1. Let's not forget that the source and the intermediate node are in
fact two modules in the same client/server (see Figure 1 in the draft).
>From an interoperability perspective it would be exactly the same if the
source created the extension field, or the intermediate node did. Why
would we mandate a specific implementation detail that would be
completely transparent to the network?

Maybe I missed that in the draft, but don't you want the sending server
to decide whether or not it expects the timestamp be updated? Having
intermediate systems update the timestamp and extension field without
the originating server sanctioning it seems even worse (to me).

> 
> 2. A clock that receives an NTP message has no way of knowing
> whether
an extension field was added by the source or by an intermediate node,
and thus there is no way to enforce (enforce from a security
perspective) the requirement you suggested.
> 

True enough but don't you want the originator to have a say in this so
that this becomes a recommendation for developers?

I've added TICTOC to the discussion. It was not in the original mail.

Danny

> Tal.
> 
> 
> -----Original Message-----
> From: Danny Mayer [mailto:mayer@ntp.org] 
> Sent: Sunday, October 27, 2013 3:34 PM
> To: Tal Mizrahi; ntpwg@lists.ntp.org
> Subject: Re: [ntpwg] New version of draft-mizrahi-ntp-checksum-trailer
> 
> On 10/27/2013 3:58 AM, Tal Mizrahi wrote:
>> Hi Danny,
>>
>>> The draft does not state whether or not the source of the packet creates the extension field before it is sent to the recipient.
>>> That needs to be clarified.
>>
>> The source should create the extension field in advance. I will clarify this in the draft.
>>
> 
> That also means that the extension field MUST NOT be added by any intermediate nodes if it does not exist.
> 
> Danny
> 
>>
>>> I am aware that it is easy enough to change the contents of a packet 
>>> AND the UDP checksum and noone would be the wiser
>>
>> Right, I completely agree.
>>
>>> but I don't think that it's good policy.
>>
>>
>> Thanks,
>> Tal.
>>
>>
>> -----Original Message-----
>> From: Danny Mayer [mailto:mayer@ntp.org]
>> Sent: Sunday, October 27, 2013 12:16 AM
>> To: Tal Mizrahi; ntpwg@lists.ntp.org
>> Subject: Re: [ntpwg] New version of draft-mizrahi-ntp-checksum-trailer
>>
>> On 10/21/2013 5:59 AM, Tal Mizrahi wrote:
>>> Hi,
>>> A new version is available:
>>>
>>> http://tools.ietf.org/html/draft-mizrahi-ntp-checksum-trailer-01
>>>
>>> The most significant change since the last draft is that this draft 
>>> is
>>> **not** intended for authenticated mode.
>>>
>>> This was in response to security related concerns from Danny and Harlan.
>>>
>>> I believe the current draft does not present a new security 
>>> vulnerability compared to the existing NTPv4.
>>>
>>> (I think) I managed to convince Harlan of this. I am not sure I 
>>> convinced Danny yetÃ,Â.
>>>
>>
>> Let me try and explain my worries about this extension field.
>> The draft is marked as experimental so it falls into the category of something someone want's to try but won't necessarily make it further than that.
>>
>> The proposal's intent is to allow the packet to be modified in-flight to change the previously provided timestamp with another one. When one does that the packet's existing UDP checksum becomes invalid. In order to deal with this, instead of updating the UDP checksum itself, the extension field is either added, or updated, I'm not clear which, so that the additional set of bits makes the original UDP checksum be correct. The draft does not state whether or not the source of the packet creates the extension field before it is sent to the recipient.
>> That needs to be clarified. Either way the intent of the extension field is just to provide a delta so that the originator's original UDP checksum works. It has no other function. Potentially the timestamp could be updated multiple times by intermediaries and the extension field updated each time. This also means that a MAC cannot be present unless the MAC is updated each time and security like autokey cannot be used.
>>
>> My worry here is that this just provides another way of changing the contents of the NTP packet without disturbing the original UDP checksum.
>> It's not something I would want to encourage. I am aware that it is easy enough to change the contents of a packet AND the UDP checksum and noone would be the wiser but I don't think that it's good policy.
>>
>>
>> Danny
>>
> 
> 
> 


From talmi@marvell.com  Sun Oct 27 23:34:30 2013
Return-Path: <talmi@marvell.com>
X-Original-To: tictoc@ietfa.amsl.com
Delivered-To: tictoc@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BDDEF21E8093 for <tictoc@ietfa.amsl.com>; Sun, 27 Oct 2013 23:34:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.193
X-Spam-Level: 
X-Spam-Status: No, score=-3.193 tagged_above=-999 required=5 tests=[AWL=-0.928, BAYES_00=-2.599, IP_NOT_FRIENDLY=0.334]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id MHXjVlfYGMGY for <tictoc@ietfa.amsl.com>; Sun, 27 Oct 2013 23:34:26 -0700 (PDT)
Received: from mx0a-0016f401.pphosted.com (mx0a-0016f401.pphosted.com [67.231.148.174]) by ietfa.amsl.com (Postfix) with ESMTP id 1D30711E8105 for <tictoc@ietf.org>; Sun, 27 Oct 2013 23:34:25 -0700 (PDT)
Received: from pps.filterd (m0045849.ppops.net [127.0.0.1]) by mx0a-0016f401.pphosted.com (8.14.5/8.14.5) with SMTP id r9S6YPol029707; Sun, 27 Oct 2013 23:34:25 -0700
Received: from sc-owa01.marvell.com ([199.233.58.136]) by mx0a-0016f401.pphosted.com with ESMTP id 1fr72krp84-1 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Sun, 27 Oct 2013 23:34:25 -0700
Received: from YK-HUB01.marvell.com (10.4.102.51) by sc-owa01.marvell.com (10.93.76.21) with Microsoft SMTP Server (TLS) id 8.3.213.0; Sun, 27 Oct 2013 23:34:18 -0700
Received: from IL-MB01.marvell.com ([10.4.102.53]) by YK-HUB01.marvell.com ([10.4.102.51]) with mapi; Mon, 28 Oct 2013 08:34:15 +0200
From: Tal Mizrahi <talmi@marvell.com>
To: "mayer@ntp.org" <mayer@ntp.org>, "ntpwg@lists.ntp.org" <ntpwg@lists.ntp.org>, "tictoc@ietf.org" <tictoc@ietf.org>
Date: Mon, 28 Oct 2013 08:34:11 +0200
Thread-Topic: [ntpwg] New version of draft-mizrahi-ntp-checksum-trailer
Thread-Index: Ac7TSXDmU3Tqo1l/RNqHMSTqY7BmbgAXdwTw
Message-ID: <74470498B659FA4687F0B0018C19A89C01B87D7A4EB8@IL-MB01.marvell.com>
References: <74470498B659FA4687F0B0018C19A89C01B87D7A40A6@IL-MB01.marvell.com> <526C30F9.1040400@ntp.org> <74470498B659FA4687F0B0018C19A89C01B87D7A4C6E@IL-MB01.marvell.com> <526D165D.3040902@ntp.org> <74470498B659FA4687F0B0018C19A89C01B87D7A4DC7@IL-MB01.marvell.com> <526D671A.7050908@ntp.org>
In-Reply-To: <526D671A.7050908@ntp.org>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:5.10.8794, 1.0.431, 0.0.0000 definitions=2013-10-27_03:2013-10-26, 2013-10-27, 1970-01-01 signatures=0
X-Proofpoint-Spam-Details: rule=outbound_notspam policy=outbound score=0 spamscore=0 suspectscore=0 phishscore=0 adultscore=0 bulkscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=7.0.1-1305240000 definitions=main-1310270347
Subject: Re: [TICTOC] [ntpwg] New version of draft-mizrahi-ntp-checksum-trailer
X-BeenThere: tictoc@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Timing over IP Connection and Transfer of Clock BOF <tictoc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tictoc>, <mailto:tictoc-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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>
X-List-Received-Date: Mon, 28 Oct 2013 06:34:30 -0000

Hi Danny,

>> 2. A clock that receives an NTP message has no way of knowing whether
>>an extension field was added by the source or by an intermediate node, an=
d thus there is no way to enforce (enforce from a security
>>perspective) the requirement you suggested.

>True enough but don't you want the originator to have a say in this so tha=
t this becomes a recommendation for developers?

As a recommendation it makes sense, and indeed I will add it as a SHOULD.=20

Thanks,
Tal.


-----Original Message-----
From: Danny Mayer [mailto:mayer@ntp.org]=20
Sent: Sunday, October 27, 2013 9:19 PM
To: Tal Mizrahi; ntpwg@lists.ntp.org; tictoc@ietf.org
Subject: Re: [ntpwg] New version of draft-mizrahi-ntp-checksum-trailer

On 10/27/2013 9:42 AM, Tal Mizrahi wrote:
> Hi Danny,
>=20
>> That also means that the extension field MUST NOT be added by any interm=
ediate nodes if it does not exist.
>=20
> I am not sure we want to go there, for 2 reasons:
>=20
> 1. Let's not forget that the source and the intermediate node are in
fact two modules in the same client/server (see Figure 1 in the draft).
>From an interoperability perspective it would be exactly the same if the so=
urce created the extension field, or the intermediate node did. Why would w=
e mandate a specific implementation detail that would be completely transpa=
rent to the network?

Maybe I missed that in the draft, but don't you want the sending server to =
decide whether or not it expects the timestamp be updated? Having intermedi=
ate systems update the timestamp and extension field without the originatin=
g server sanctioning it seems even worse (to me).

>=20
> 2. A clock that receives an NTP message has no way of knowing whether
an extension field was added by the source or by an intermediate node, and =
thus there is no way to enforce (enforce from a security
perspective) the requirement you suggested.
>=20

True enough but don't you want the originator to have a say in this so that=
 this becomes a recommendation for developers?

I've added TICTOC to the discussion. It was not in the original mail.

Danny

> Tal.
>=20
>=20
> -----Original Message-----
> From: Danny Mayer [mailto:mayer@ntp.org]
> Sent: Sunday, October 27, 2013 3:34 PM
> To: Tal Mizrahi; ntpwg@lists.ntp.org
> Subject: Re: [ntpwg] New version of draft-mizrahi-ntp-checksum-trailer
>=20
> On 10/27/2013 3:58 AM, Tal Mizrahi wrote:
>> Hi Danny,
>>
>>> The draft does not state whether or not the source of the packet create=
s the extension field before it is sent to the recipient.
>>> That needs to be clarified.
>>
>> The source should create the extension field in advance. I will clarify =
this in the draft.
>>
>=20
> That also means that the extension field MUST NOT be added by any interme=
diate nodes if it does not exist.
>=20
> Danny
>=20
>>
>>> I am aware that it is easy enough to change the contents of a packet=20
>>> AND the UDP checksum and noone would be the wiser
>>
>> Right, I completely agree.
>>
>>> but I don't think that it's good policy.
>>
>>
>> Thanks,
>> Tal.
>>
>>
>> -----Original Message-----
>> From: Danny Mayer [mailto:mayer@ntp.org]
>> Sent: Sunday, October 27, 2013 12:16 AM
>> To: Tal Mizrahi; ntpwg@lists.ntp.org
>> Subject: Re: [ntpwg] New version of=20
>> draft-mizrahi-ntp-checksum-trailer
>>
>> On 10/21/2013 5:59 AM, Tal Mizrahi wrote:
>>> Hi,
>>> A new version is available:
>>>
>>> http://tools.ietf.org/html/draft-mizrahi-ntp-checksum-trailer-01
>>>
>>> The most significant change since the last draft is that this draft=20
>>> is
>>> **not** intended for authenticated mode.
>>>
>>> This was in response to security related concerns from Danny and Harlan=
.
>>>
>>> I believe the current draft does not present a new security=20
>>> vulnerability compared to the existing NTPv4.
>>>
>>> (I think) I managed to convince Harlan of this. I am not sure I=20
>>> convinced Danny yet=C3,=C2.
>>>
>>
>> Let me try and explain my worries about this extension field.
>> The draft is marked as experimental so it falls into the category of som=
ething someone want's to try but won't necessarily make it further than tha=
t.
>>
>> The proposal's intent is to allow the packet to be modified in-flight to=
 change the previously provided timestamp with another one. When one does t=
hat the packet's existing UDP checksum becomes invalid. In order to deal wi=
th this, instead of updating the UDP checksum itself, the extension field i=
s either added, or updated, I'm not clear which, so that the additional set=
 of bits makes the original UDP checksum be correct. The draft does not sta=
te whether or not the source of the packet creates the extension field befo=
re it is sent to the recipient.
>> That needs to be clarified. Either way the intent of the extension field=
 is just to provide a delta so that the originator's original UDP checksum =
works. It has no other function. Potentially the timestamp could be updated=
 multiple times by intermediaries and the extension field updated each time=
. This also means that a MAC cannot be present unless the MAC is updated ea=
ch time and security like autokey cannot be used.
>>
>> My worry here is that this just provides another way of changing the con=
tents of the NTP packet without disturbing the original UDP checksum.
>> It's not something I would want to encourage. I am aware that it is easy=
 enough to change the contents of a packet AND the UDP checksum and noone w=
ould be the wiser but I don't think that it's good policy.
>>
>>
>> Danny
>>
>=20
>=20
>=20


From stenn@stenn.ntp.org  Mon Oct 28 01:12:25 2013
Return-Path: <stenn@stenn.ntp.org>
X-Original-To: tictoc@ietfa.amsl.com
Delivered-To: tictoc@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C3ACC11E8227 for <tictoc@ietfa.amsl.com>; Mon, 28 Oct 2013 01:12:24 -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]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id FWnbuTOw8tog for <tictoc@ietfa.amsl.com>; Mon, 28 Oct 2013 01:12:19 -0700 (PDT)
Received: from stenn.ntp.org (stenn.ntp.org [149.20.68.30]) by ietfa.amsl.com (Postfix) with ESMTP id 2398C11E822B for <tictoc@ietf.org>; Mon, 28 Oct 2013 01:11:01 -0700 (PDT)
Received: from localhost.ntp.org ([::1] helo=stenn.ntp.org) by stenn.ntp.org with esmtp (Exim 4.80.1 (FreeBSD)) (envelope-from <stenn@stenn.ntp.org>) id 1Vahsr-000Kke-9c; Mon, 28 Oct 2013 08:09:09 +0000
From: Harlan Stenn <stenn@ntp.org>
To: Tal Mizrahi <talmi@marvell.com>
In-reply-to: <74470498B659FA4687F0B0018C19A89C01B87D7A4EB8@IL-MB01.marvell.com>
References: <74470498B659FA4687F0B0018C19A89C01B87D7A40A6@IL-MB01.marvell.com> <526C30F9.1040400@ntp.org> <74470498B659FA4687F0B0018C19A89C01B87D7A4C6E@IL-MB01.marvell.com> <526D165D.3040902@ntp.org> <74470498B659FA4687F0B0018C19A89C01B87D7A4DC7@IL-MB01.marvell.com> <526D671A.7050908@ntp.org> <74470498B659FA4687F0B0018C19A89C01B87D7A4EB8@IL-MB01.marvell.com>
Comments: In-reply-to Tal Mizrahi <talmi@marvell.com> message dated "Mon, 28 Oct 2013 08:34:11 +0200."
X-Mailer: MH-E 7.4.2; nmh 1.5; XEmacs 21.4 (patch 22)
Mime-Version: 1.0 (generated by tm-edit 1.8)
Content-Type: text/plain; charset=US-ASCII
Date: Mon, 28 Oct 2013 08:09:09 +0000
Message-Id: <E1Vahsr-000Kke-9c@stenn.ntp.org>
Cc: "ntpwg@lists.ntp.org" <ntpwg@lists.ntp.org>, "tictoc@ietf.org" <tictoc@ietf.org>
Subject: Re: [TICTOC] [ntpwg] New version of draft-mizrahi-ntp-checksum-trailer
X-BeenThere: tictoc@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Timing over IP Connection and Transfer of Clock BOF <tictoc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tictoc>, <mailto:tictoc-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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>
X-List-Received-Date: Mon, 28 Oct 2013 08:12:27 -0000

Just some thoughts, and I hope I'm awake enough to type this...

There seem to be several issues here.

In the "Figure 1" case "core" packet timestamps come from the kernel
and the new packet timestamp will be added by the hardware engine.  I
understand the following question is outside the scope of this document,
but how can one determine how well sync'd the internal clock is with the
clock in the accurate timestamp engine?

If we have TX and RX hardware timestamping capabilities, we can use
NTP's interleave mode to communicate these timestamps as well.  Having
said that, I'm sure there is something to be learned from implementing
Tal's proposal.

H

From talmi@marvell.com  Mon Oct 28 01:40:30 2013
Return-Path: <talmi@marvell.com>
X-Original-To: tictoc@ietfa.amsl.com
Delivered-To: tictoc@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 420EF11E822A for <tictoc@ietfa.amsl.com>; Mon, 28 Oct 2013 01:39:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.228
X-Spam-Level: 
X-Spam-Status: No, score=-3.228 tagged_above=-999 required=5 tests=[AWL=-0.963, BAYES_00=-2.599, IP_NOT_FRIENDLY=0.334]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id sFEjodniFInn for <tictoc@ietfa.amsl.com>; Mon, 28 Oct 2013 01:39:38 -0700 (PDT)
Received: from mx0b-0016f401.pphosted.com (mx0b-0016f401.pphosted.com [67.231.156.173]) by ietfa.amsl.com (Postfix) with ESMTP id AB88411E81BC for <tictoc@ietf.org>; Mon, 28 Oct 2013 01:39:37 -0700 (PDT)
Received: from pps.filterd (m0045851.ppops.net [127.0.0.1]) by mx0b-0016f401.pphosted.com (8.14.5/8.14.5) with SMTP id r9S8db3L031234; Mon, 28 Oct 2013 01:39:37 -0700
Received: from sc-owa01.marvell.com ([199.233.58.136]) by mx0b-0016f401.pphosted.com with ESMTP id 1fr72uxqx5-3 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Mon, 28 Oct 2013 01:39:37 -0700
Received: from YK-HUB02.marvell.com (10.4.102.52) by sc-owa01.marvell.com (10.93.76.21) with Microsoft SMTP Server (TLS) id 8.3.213.0; Mon, 28 Oct 2013 01:39:35 -0700
Received: from IL-MB01.marvell.com ([10.4.102.53]) by YK-HUB02.marvell.com ([10.4.102.52]) with mapi; Mon, 28 Oct 2013 10:38:59 +0200
From: Tal Mizrahi <talmi@marvell.com>
To: Harlan Stenn <stenn@ntp.org>
Date: Mon, 28 Oct 2013 10:38:55 +0200
Thread-Topic: [ntpwg] New version of draft-mizrahi-ntp-checksum-trailer
Thread-Index: Ac7TtQETTHSIehLBQt2pl+Gi3LYL7wAAzUoQ
Message-ID: <74470498B659FA4687F0B0018C19A89C01B87D8329E8@IL-MB01.marvell.com>
References: <74470498B659FA4687F0B0018C19A89C01B87D7A40A6@IL-MB01.marvell.com> <526C30F9.1040400@ntp.org> <74470498B659FA4687F0B0018C19A89C01B87D7A4C6E@IL-MB01.marvell.com> <526D165D.3040902@ntp.org> <74470498B659FA4687F0B0018C19A89C01B87D7A4DC7@IL-MB01.marvell.com> <526D671A.7050908@ntp.org> <74470498B659FA4687F0B0018C19A89C01B87D7A4EB8@IL-MB01.marvell.com> <E1Vahsr-000Kke-9c@stenn.ntp.org>
In-Reply-To: <E1Vahsr-000Kke-9c@stenn.ntp.org>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:5.10.8794, 1.0.431, 0.0.0000 definitions=2013-10-27_03:2013-10-26, 2013-10-27, 1970-01-01 signatures=0
X-Proofpoint-Spam-Details: rule=outbound_notspam policy=outbound score=0 spamscore=0 suspectscore=0 phishscore=0 adultscore=0 bulkscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=7.0.1-1305240000 definitions=main-1310280017
Cc: "ntpwg@lists.ntp.org" <ntpwg@lists.ntp.org>, "tictoc@ietf.org" <tictoc@ietf.org>
Subject: Re: [TICTOC] [ntpwg] New version of draft-mizrahi-ntp-checksum-trailer
X-BeenThere: tictoc@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Timing over IP Connection and Transfer of Clock BOF <tictoc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tictoc>, <mailto:tictoc-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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>
X-List-Received-Date: Mon, 28 Oct 2013 08:40:30 -0000

Hi Harlan,

>In the "Figure 1" case "core" packet timestamps come from the kernel and t=
he new packet timestamp will be added by the hardware engine. =20
>I understand the following question is outside the scope of this document,=
 but how can one determine how well sync'd the internal clock is with the c=
lock in the accurate timestamp engine?

Well, indeed it is strictly an implementation question. For example, in typ=
ical PTP implementations (that I am familiar with) the accurate clock is on=
ly maintained in one place, i.e., in the HW engine. The SW stack includes t=
he servo algorithm; the SW stack regularly computes the necessary offset or=
 frequency adjustments, and whenever necessary sends update commands to the=
 HW engine about these adjustments. Thus, the SW stack does not need to mai=
ntain an additional clock, since all its computations are performed WRT the=
 HW clock.

Thanks,
Tal.


-----Original Message-----
From: Harlan Stenn [mailto:stenn@ntp.org]=20
Sent: Monday, October 28, 2013 10:09 AM
To: Tal Mizrahi
Cc: mayer@ntp.org; ntpwg@lists.ntp.org; tictoc@ietf.org
Subject: Re: [ntpwg] New version of draft-mizrahi-ntp-checksum-trailer

Just some thoughts, and I hope I'm awake enough to type this...

There seem to be several issues here.

In the "Figure 1" case "core" packet timestamps come from the kernel and th=
e new packet timestamp will be added by the hardware engine.  I understand =
the following question is outside the scope of this document, but how can o=
ne determine how well sync'd the internal clock is with the clock in the ac=
curate timestamp engine?

If we have TX and RX hardware timestamping capabilities, we can use NTP's i=
nterleave mode to communicate these timestamps as well.  Having said that, =
I'm sure there is something to be learned from implementing Tal's proposal.

H

From John.Fletcher@bbc.co.uk  Mon Oct 28 08:10:40 2013
Return-Path: <John.Fletcher@bbc.co.uk>
X-Original-To: tictoc@ietfa.amsl.com
Delivered-To: tictoc@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 360C721E805D for <tictoc@ietfa.amsl.com>; Mon, 28 Oct 2013 08:10:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.553
X-Spam-Level: 
X-Spam-Status: No, score=-6.553 tagged_above=-999 required=5 tests=[AWL=-2.555, BAYES_50=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id IcVyLPHozGbu for <tictoc@ietfa.amsl.com>; Mon, 28 Oct 2013 08:10:32 -0700 (PDT)
Received: from mailout1.mh.bbc.co.uk (mailout1.mh.bbc.co.uk [132.185.144.153]) by ietfa.amsl.com (Postfix) with ESMTP id 256EF11E8186 for <tictoc@ietf.org>; Mon, 28 Oct 2013 08:10:32 -0700 (PDT)
Received: from BGB01XI1006.national.core.bbc.co.uk ([10.184.50.56]) by mailout1.mh.bbc.co.uk (8.14.4/8.14.3) with ESMTP id r9SFAR61024273;  Mon, 28 Oct 2013 15:10:28 GMT
Received: from BGB01XUD1011.national.core.bbc.co.uk ([169.254.10.4]) by BGB01XI1006.national.core.bbc.co.uk ([10.184.50.56]) with mapi id 14.02.0342.004; Mon, 28 Oct 2013 15:10:27 +0000
From: John Fletcher <John.Fletcher@bbc.co.uk>
To: Douglas Arnold <doug.arnold@meinberg-usa.com>
Thread-Topic: [TICTOC] Enterprise Profile
Thread-Index: AQHO0Tj+EfJkN9q+/USLYOoP7dIkB5oFJTNggAUWS6E=
Date: Mon, 28 Oct 2013 15:10:27 +0000
Message-ID: <B1D49063AD5FBD4688F3EEDEC68B20175113E0AA@BGB01XUD1011.national.core.bbc.co.uk>
References: <CACQYgzFmOtFY+Td0jZMyykeZ17KwAuCc+LY+C2be_UPgZKh9GA@mail.gmail.com>, <B1D49063AD5FBD4688F3EEDEC68B201751132BDF@BGB01XUD1002.national.core.bbc.co.uk>
In-Reply-To: <B1D49063AD5FBD4688F3EEDEC68B201751132BDF@BGB01XUD1002.national.core.bbc.co.uk>
Accept-Language: en-GB, en-US
Content-Language: en-GB
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [172.19.113.201]
x-exclaimer-md-config: 1cd3ac1c-62e5-43f2-8404-6b688271c769
Content-Type: multipart/alternative; boundary="_000_B1D49063AD5FBD4688F3EEDEC68B20175113E0AABGB01XUD1011nat_"
MIME-Version: 1.0
Cc: "tictoc@ietf.org" <tictoc@ietf.org>
Subject: Re: [TICTOC] Enterprise Profile
X-BeenThere: tictoc@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Timing over IP Connection and Transfer of Clock BOF <tictoc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tictoc>, <mailto:tictoc-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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>
X-List-Received-Date: Mon, 28 Oct 2013 15:10:40 -0000

--_000_B1D49063AD5FBD4688F3EEDEC68B20175113E0AABGB01XUD1011nat_
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64

SSdkIGFsc28gbGlrZSB0byBhc2sgdGhhdCB5b3UgZG9uJ3QgcHJvaGliaXQgdGhlIEFsdGVybmF0
ZSBUaW1lc2NhbGVzIG9wdGlvbi4gIFRoaXMgaXMgcG90ZW50aWFsbHkgdXNlZnVsIHRvIGRpc3Ry
aWJ1dGUgImxvY2FsIHRpbWUiICh5b3VyIHRpbWUtem9uZSBhbmQgZHN0KSBhbmQgdGhlcmUgZG9l
c24ndCBzZWVtIHRvIGJlIGFueSBuZWVkIHRvIHByb2hpYml0IGl0Lg0KDQpKb2huDQpfX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fXw0KRnJvbTogdGljdG9jLWJvdW5jZXNAaWV0Zi5vcmcg
W3RpY3RvYy1ib3VuY2VzQGlldGYub3JnXSBvbiBiZWhhbGYgb2YgSm9obiBGbGV0Y2hlciBbSm9o
bi5GbGV0Y2hlckBiYmMuY28udWtdDQpTZW50OiAyNSBPY3RvYmVyIDIwMTMgMTE6MDENClRvOiBE
b3VnbGFzIEFybm9sZA0KQ2M6IHRpY3RvY0BpZXRmLm9yZw0KU3ViamVjdDogUmU6IFtUSUNUT0Nd
IEVudGVycHJpc2UgUHJvZmlsZQ0KDQpEb3VnLA0KDQpJIHdvdWxkIGJlIGludGVyZXN0ZWQgdG8g
a25vdyB0aGUgY2lyY3Vtc3RhbmNlcyB3aGVuIHlvdSBzZWUgdGhlIG1heGltdW0gcGhhc2UgYWRq
dXN0bWVudCBpbmZvcm1hdGlvbiBiZWluZyB1c2VkLg0KDQpTb21lIGNvbW1lbnRzOg0KDQpJbiBz
ZWN0aW9uIDYsIHlvdSBzYXksIOKAnEluIGFsbCB0aHJlZSBvZiB0aGUgZGVsYXkgbWVhc3VyZW1l
bnQgbW9kZXPigKbigJ0uICBBdCB0aGF0IHBvaW50IGluIHRoZSB0ZXh0IHlvdSBoYXZlIG5vdCB5
ZXQgbWVudGlvbmVkIG11bHRpY2FzdCwgaHlicmlkIGFuZCB1bmljYXN0IG1vZGVzIHNvIGl04oCZ
cyBub3QgY2xlYXIgd2hpY2ggbW9kZXMgeW91IGFyZSByZWZlcnJpbmcgdG8uDQoNCkluIHNlY3Rp
b24gOSwgeW91IHNheSwg4oCcU2xhdmVzIFNIT1VMRCBOT1QgU3luY2hyb25pemUgdG8gYSBSb2d1
ZSBNYXN0ZXIu4oCdICBJdOKAmXMgbm90IGNsZWFyIGhvdyBhIHNsYXZlIHdvdWxkIGtub3cgdGhh
dCBhIG1hc3RlciBpcyByb2d1ZTsgcHJlc3VtYWJseSBpdCB3b3VsZCBuZWVkIHRvIGV4YW1pbmUg
dGhlIGFubm91bmNlIG1lc3NhZ2VzIG9mIGFsbCBtYXN0ZXJzIGFuZCBkbyBpdHMgb3duIEJNQ0Eg
ZXZhbHVhdGlvbi4gIEEgbW9yZSByZWFsaXN0aWMg4oCccm9ndWXigJ0gbWFzdGVyIHdvdWxkIHBy
b2JhYmx5IG1lZXQgdGhlIEJNQ0EgY3JpdGVyaWEgZm9yIHNlbGVjdGlvbi4NCg0KSW4gc2VjdGlv
biAxMiwg4oCcQWx0ZXJuYXRpdmUgVGltZSBTY2FsZXPigJ0gc2hvdWxkIGJlIOKAnEFsdGVybmF0
ZSBUaW1lc2NhbGVz4oCdLg0KDQoNClJlZ2FyZHMsDQpKb2huIEZsZXRjaGVyDQoNCkZyb206IHRp
Y3RvYy1ib3VuY2VzQGlldGYub3JnIFttYWlsdG86dGljdG9jLWJvdW5jZXNAaWV0Zi5vcmddIE9u
IEJlaGFsZiBPZiBEb3VnbGFzIEFybm9sZA0KU2VudDogMjUgT2N0b2JlciAyMDEzIDAxOjM1DQpU
bzogdGljdG9jQGlldGYub3JnDQpTdWJqZWN0OiBbVElDVE9DXSBFbnRlcnByaXNlIFByb2ZpbGUN
Cg0KSGVsbG8gRXZlcnlvbmUsDQoNCkF0dGFjaGVkIGlzIGFuIHVwZGF0ZWQgdmVyc2lvbiBvZiB0
aGUgRW50ZXJwcmlzZSBwcm9maWxlLiAgU29ycnkgSSBtaXNzZWQgdGhlIHVwbG9hZCBkZWFkbGlu
ZSBmb3IgIHRoZSBWYW5jb3V2ZXIgbWVldGluZy4gIElmIHlvdSBnZXQgYSBjaGFuY2UgdG8gbG9v
ayBhdCBpdCBiZWZvcmUgdGhlbiBJIHdpbGwgYmUgdGhlcmUgYW5kIHdvdWxkIGxvdmUgdG8gZGlz
Y3VzcyBpdC4NCg0KU3VtbWFyeSBvZiBjaGFuZ2VzOg0KDQpJIGFsc28gY2hhbmdlZCB0aGUgVExW
IGZvcm1hdCB0byBmaXQgdGhlIGxhdGVzdCBwcm9wb3NhbCBpbiB0aGUgMTU4OCByZXZpc2lvbi4N
Cg0KSSBhZGRlZCBhIHN0YXRlbWVudCBhYm91dCBub3QgZ29pbmcgaW50byB0aGUgbWFzdGVyIHN0
YXRlIHVubGVzcyBvbmUgaGFkIGEgY3VycmVudCBVVEMgb2Zmc2V0Lg0KDQpJIGFkZGVkIHRvIHRo
ZSBUTFYgZmllbGRzIHRvIGluZGljYXRlIG1heGltdW0gcGhhc2UgY29ycmVjdGlvbiBvdmVyIGEg
c3luYyBjeWNsZS4NCg0KLS0NCkRvdWcgQXJub2xkDQpQcmluY2lwYWwgVGVjaG5vbG9naXN0DQpK
VGltZSEgTWVpbmJlcmcgVVNBDQorMS03MDctMzAzLTU1NTkNCg0KDQoNCg0KDQotLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tDQoNCmh0dHA6Ly93d3cuYmJjLmNvLnVrDQpUaGlzIGUtbWFpbCAo
YW5kIGFueSBhdHRhY2htZW50cykgaXMgY29uZmlkZW50aWFsIGFuZCBtYXkgY29udGFpbiBwZXJz
b25hbCB2aWV3cyB3aGljaCBhcmUgbm90IHRoZSB2aWV3cyBvZiB0aGUgQkJDIHVubGVzcyBzcGVj
aWZpY2FsbHkgc3RhdGVkLg0KSWYgeW91IGhhdmUgcmVjZWl2ZWQgaXQgaW4gZXJyb3IsIHBsZWFz
ZSBkZWxldGUgaXQgZnJvbSB5b3VyIHN5c3RlbS4NCkRvIG5vdCB1c2UsIGNvcHkgb3IgZGlzY2xv
c2UgdGhlIGluZm9ybWF0aW9uIGluIGFueSB3YXkgbm9yIGFjdCBpbiByZWxpYW5jZSBvbiBpdCBh
bmQgbm90aWZ5IHRoZSBzZW5kZXIgaW1tZWRpYXRlbHkuDQpQbGVhc2Ugbm90ZSB0aGF0IHRoZSBC
QkMgbW9uaXRvcnMgZS1tYWlscyBzZW50IG9yIHJlY2VpdmVkLg0KRnVydGhlciBjb21tdW5pY2F0
aW9uIHdpbGwgc2lnbmlmeSB5b3VyIGNvbnNlbnQgdG8gdGhpcy4NCg0KLS0tLS0tLS0tLS0tLS0t
LS0tLS0tDQoNCg0KDQotLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tDQoNCmh0dHA6Ly93d3cu
YmJjLmNvLnVrDQpUaGlzIGUtbWFpbCAoYW5kIGFueSBhdHRhY2htZW50cykgaXMgY29uZmlkZW50
aWFsIGFuZCBtYXkgY29udGFpbiBwZXJzb25hbCB2aWV3cyB3aGljaCBhcmUgbm90IHRoZSB2aWV3
cyBvZiB0aGUgQkJDIHVubGVzcyBzcGVjaWZpY2FsbHkgc3RhdGVkLg0KSWYgeW91IGhhdmUgcmVj
ZWl2ZWQgaXQgaW4gZXJyb3IsIHBsZWFzZSBkZWxldGUgaXQgZnJvbSB5b3VyIHN5c3RlbS4NCkRv
IG5vdCB1c2UsIGNvcHkgb3IgZGlzY2xvc2UgdGhlIGluZm9ybWF0aW9uIGluIGFueSB3YXkgbm9y
IGFjdCBpbiByZWxpYW5jZSBvbiBpdCBhbmQgbm90aWZ5IHRoZSBzZW5kZXIgaW1tZWRpYXRlbHku
DQpQbGVhc2Ugbm90ZSB0aGF0IHRoZSBCQkMgbW9uaXRvcnMgZS1tYWlscyBzZW50IG9yIHJlY2Vp
dmVkLg0KRnVydGhlciBjb21tdW5pY2F0aW9uIHdpbGwgc2lnbmlmeSB5b3VyIGNvbnNlbnQgdG8g
dGhpcy4NCg0KLS0tLS0tLS0tLS0tLS0tLS0tLS0tDQo=

--_000_B1D49063AD5FBD4688F3EEDEC68B20175113E0AABGB01XUD1011nat_
Content-Type: text/html; charset="utf-8"
Content-Transfer-Encoding: base64

PGh0bWwgZGlyPSJsdHIiPg0KPGhlYWQ+DQo8IS0tIFRlbXBsYXRlIGdlbmVyYXRlZCBieSBFeGNs
YWltZXIgTWFpbCBEaXNjbGFpbWVycyBvbiAwMzoxMDoyNyBNb25kYXksIDI4IE9jdG9iZXIgMjAx
MyAtLT4NCjxtZXRhIGh0dHAtZXF1aXY9IkNvbnRlbnQtVHlwZSIgY29udGVudD0idGV4dC9odG1s
OyBjaGFyc2V0PXV0Zi04Ij4NCjxzdHlsZSB0eXBlPSJ0ZXh0L2NzcyI+UC41ZWUzYWFmNi02MjY0
LTQ0NDEtYjE4OC02MTYwMjM5Zjg0MzIgew0KCU1BUkdJTjogMGNtIDBjbSAwcHQNCn0NCkxJLjVl
ZTNhYWY2LTYyNjQtNDQ0MS1iMTg4LTYxNjAyMzlmODQzMiB7DQoJTUFSR0lOOiAwY20gMGNtIDBw
dA0KfQ0KRElWLjVlZTNhYWY2LTYyNjQtNDQ0MS1iMTg4LTYxNjAyMzlmODQzMiB7DQoJTUFSR0lO
OiAwY20gMGNtIDBwdA0KfQ0KVEFCTEUuNWVlM2FhZjYtNjI2NC00NDQxLWIxODgtNjE2MDIzOWY4
NDMyVGFibGUgew0KCU1BUkdJTjogMGNtIDBjbSAwcHQNCn0NCkRJVi5TZWN0aW9uMSB7DQoJcGFn
ZTogU2VjdGlvbjENCn0NCjwvc3R5bGU+PHN0eWxlIHR5cGU9InRleHQvY3NzIj4KPCEtLQotLT4K
PC9zdHlsZT48c3R5bGU+CjwhLS0KQGZvbnQtZmFjZQoJe2ZvbnQtZmFtaWx5OkNhbGlicml9CkBm
b250LWZhY2UKCXtmb250LWZhbWlseTpUYWhvbWF9CnAuTXNvTm9ybWFsLCBsaS5Nc29Ob3JtYWws
IGRpdi5Nc29Ob3JtYWwKCXttYXJnaW46MGNtOwoJbWFyZ2luLWJvdHRvbTouMDAwMXB0OwoJZm9u
dC1zaXplOjEyLjBwdDsKCWZvbnQtZmFtaWx5OiJUaW1lcyBOZXcgUm9tYW4iLCJzZXJpZiJ9CmE6
bGluaywgc3Bhbi5Nc29IeXBlcmxpbmsKCXtjb2xvcjpibHVlOwoJdGV4dC1kZWNvcmF0aW9uOnVu
ZGVybGluZX0KYTp2aXNpdGVkLCBzcGFuLk1zb0h5cGVybGlua0ZvbGxvd2VkCgl7Y29sb3I6cHVy
cGxlOwoJdGV4dC1kZWNvcmF0aW9uOnVuZGVybGluZX0Kc3Bhbi5FbWFpbFN0eWxlMTcKCXtmb250
LWZhbWlseToiQ2FsaWJyaSIsInNhbnMtc2VyaWYiOwoJY29sb3I6IzFGNDk3RH0KQHBhZ2UgV29y
ZFNlY3Rpb24xCgl7bWFyZ2luOjcyLjBwdCA3Mi4wcHQgNzIuMHB0IDcyLjBwdH0KLS0+Cjwvc3R5
bGU+PHN0eWxlIHR5cGU9InRleHQvY3NzIiBpZD0ib3dhUGFyYVN0eWxlIj48L3N0eWxlPjxzdHls
ZSB0eXBlPSJ0ZXh0L2NzcyI+PC9zdHlsZT48c3R5bGUgdHlwZT0idGV4dC9jc3MiPjwvc3R5bGU+
DQo8L2hlYWQ+DQo8Ym9keSBsYW5nPSJFTi1HQiIgbGluaz0iYmx1ZSIgdmxpbms9InB1cnBsZSIg
ZnBzdHlsZT0iMSIgb2NzaT0iMCI+DQo8cCBjbGFzcz0iNWVlM2FhZjYtNjI2NC00NDQxLWIxODgt
NjE2MDIzOWY4NDMyIj48L3A+DQo8ZGl2IHN0eWxlPSJkaXJlY3Rpb246IGx0cjtmb250LWZhbWls
eTogVGFob21hO2NvbG9yOiAjMDAwMDAwO2ZvbnQtc2l6ZTogMTBwdDsiPkknZCBhbHNvIGxpa2Ug
dG8gYXNrIHRoYXQgeW91IGRvbid0IHByb2hpYml0IHRoZSBBbHRlcm5hdGUgVGltZXNjYWxlcyBv
cHRpb24uICZuYnNwO1RoaXMgaXMgcG90ZW50aWFsbHkgdXNlZnVsIHRvIGRpc3RyaWJ1dGUgJnF1
b3Q7bG9jYWwgdGltZSZxdW90OyAoeW91ciB0aW1lLXpvbmUgYW5kIGRzdCkgYW5kIHRoZXJlIGRv
ZXNuJ3Qgc2VlbQ0KIHRvIGJlIGFueSBuZWVkIHRvIHByb2hpYml0IGl0Lg0KPGRpdj48YnI+DQo8
L2Rpdj4NCjxkaXY+Sm9objxicj4NCjxkaXYgc3R5bGU9ImZvbnQtZmFtaWx5OiBUaW1lcyBOZXcg
Um9tYW47IGNvbG9yOiAjMDAwMDAwOyBmb250LXNpemU6IDE2cHgiPg0KPGhyIHRhYmluZGV4PSIt
MSI+DQo8ZGl2IGlkPSJkaXZScEY1MjcyODQiIHN0eWxlPSJkaXJlY3Rpb246IGx0cjsiPjxmb250
IGZhY2U9IlRhaG9tYSIgc2l6ZT0iMiIgY29sb3I9IiMwMDAwMDAiPjxiPkZyb206PC9iPiB0aWN0
b2MtYm91bmNlc0BpZXRmLm9yZyBbdGljdG9jLWJvdW5jZXNAaWV0Zi5vcmddIG9uIGJlaGFsZiBv
ZiBKb2huIEZsZXRjaGVyIFtKb2huLkZsZXRjaGVyQGJiYy5jby51a108YnI+DQo8Yj5TZW50Ojwv
Yj4gMjUgT2N0b2JlciAyMDEzIDExOjAxPGJyPg0KPGI+VG86PC9iPiBEb3VnbGFzIEFybm9sZDxi
cj4NCjxiPkNjOjwvYj4gdGljdG9jQGlldGYub3JnPGJyPg0KPGI+U3ViamVjdDo8L2I+IFJlOiBb
VElDVE9DXSBFbnRlcnByaXNlIFByb2ZpbGU8YnI+DQo8L2ZvbnQ+PGJyPg0KPC9kaXY+DQo8ZGl2
PjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSI0YWViMGUwZi1jNjdmLTQyY2UtYmMzNS02ZDE3NWZj
YmQzY2QiPjwvcD4NCjxkaXYgY2xhc3M9IldvcmRTZWN0aW9uMSI+DQo8cCBjbGFzcz0iTXNvTm9y
bWFsIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjExLjBwdDsgZm9udC1mYW1pbHk6JnF1b3Q7Q2Fs
aWJyaSZxdW90OywmcXVvdDtzYW5zLXNlcmlmJnF1b3Q7OyBjb2xvcjojMUY0OTdEIj5Eb3VnLDwv
c3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjEx
LjBwdDsgZm9udC1mYW1pbHk6JnF1b3Q7Q2FsaWJyaSZxdW90OywmcXVvdDtzYW5zLXNlcmlmJnF1
b3Q7OyBjb2xvcjojMUY0OTdEIj4mbmJzcDs8L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1h
bCI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMS4wcHQ7IGZvbnQtZmFtaWx5OiZxdW90O0NhbGli
cmkmcXVvdDssJnF1b3Q7c2Fucy1zZXJpZiZxdW90OzsgY29sb3I6IzFGNDk3RCI+SSB3b3VsZCBi
ZSBpbnRlcmVzdGVkIHRvIGtub3cgdGhlIGNpcmN1bXN0YW5jZXMgd2hlbiB5b3Ugc2VlIHRoZSBt
YXhpbXVtIHBoYXNlIGFkanVzdG1lbnQgaW5mb3JtYXRpb24gYmVpbmcgdXNlZC48L3NwYW4+PC9w
Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMS4wcHQ7IGZv
bnQtZmFtaWx5OiZxdW90O0NhbGlicmkmcXVvdDssJnF1b3Q7c2Fucy1zZXJpZiZxdW90OzsgY29s
b3I6IzFGNDk3RCI+Jm5ic3A7PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFu
IHN0eWxlPSJmb250LXNpemU6MTEuMHB0OyBmb250LWZhbWlseTomcXVvdDtDYWxpYnJpJnF1b3Q7
LCZxdW90O3NhbnMtc2VyaWYmcXVvdDs7IGNvbG9yOiMxRjQ5N0QiPlNvbWUgY29tbWVudHM6PC9z
cGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTEu
MHB0OyBmb250LWZhbWlseTomcXVvdDtDYWxpYnJpJnF1b3Q7LCZxdW90O3NhbnMtc2VyaWYmcXVv
dDs7IGNvbG9yOiMxRjQ5N0QiPiZuYnNwOzwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFs
Ij48c3BhbiBzdHlsZT0iZm9udC1zaXplOjExLjBwdDsgZm9udC1mYW1pbHk6JnF1b3Q7Q2FsaWJy
aSZxdW90OywmcXVvdDtzYW5zLXNlcmlmJnF1b3Q7OyBjb2xvcjojMUY0OTdEIj5JbiBzZWN0aW9u
IDYsIHlvdSBzYXksIOKAnEluIGFsbCB0aHJlZSBvZiB0aGUgZGVsYXkgbWVhc3VyZW1lbnQgbW9k
ZXPigKbigJ0uJm5ic3A7IEF0IHRoYXQgcG9pbnQgaW4gdGhlIHRleHQgeW91IGhhdmUgbm90IHll
dCBtZW50aW9uZWQgbXVsdGljYXN0LCBoeWJyaWQgYW5kIHVuaWNhc3QNCiBtb2RlcyBzbyBpdOKA
mXMgbm90IGNsZWFyIHdoaWNoIG1vZGVzIHlvdSBhcmUgcmVmZXJyaW5nIHRvLjwvc3Bhbj48L3A+
DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjExLjBwdDsgZm9u
dC1mYW1pbHk6JnF1b3Q7Q2FsaWJyaSZxdW90OywmcXVvdDtzYW5zLXNlcmlmJnF1b3Q7OyBjb2xv
cjojMUY0OTdEIj4mbmJzcDs8L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4g
c3R5bGU9ImZvbnQtc2l6ZToxMS4wcHQ7IGZvbnQtZmFtaWx5OiZxdW90O0NhbGlicmkmcXVvdDss
JnF1b3Q7c2Fucy1zZXJpZiZxdW90OzsgY29sb3I6IzFGNDk3RCI+SW4gc2VjdGlvbiA5LCB5b3Ug
c2F5LCDigJxTbGF2ZXMgU0hPVUxEIE5PVCBTeW5jaHJvbml6ZSB0byBhIFJvZ3VlIE1hc3Rlci7i
gJ0mbmJzcDsgSXTigJlzIG5vdCBjbGVhciBob3cgYSBzbGF2ZSB3b3VsZCBrbm93IHRoYXQgYSBt
YXN0ZXIgaXMgcm9ndWU7IHByZXN1bWFibHkgaXQgd291bGQNCiBuZWVkIHRvIGV4YW1pbmUgdGhl
IGFubm91bmNlIG1lc3NhZ2VzIG9mIGFsbCBtYXN0ZXJzIGFuZCBkbyBpdHMgb3duIEJNQ0EgZXZh
bHVhdGlvbi4mbmJzcDsgQSBtb3JlIHJlYWxpc3RpYyDigJxyb2d1ZeKAnSBtYXN0ZXIgd291bGQg
cHJvYmFibHkgbWVldCB0aGUgQk1DQSBjcml0ZXJpYSBmb3Igc2VsZWN0aW9uLjwvc3Bhbj48L3A+
DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjExLjBwdDsgZm9u
dC1mYW1pbHk6JnF1b3Q7Q2FsaWJyaSZxdW90OywmcXVvdDtzYW5zLXNlcmlmJnF1b3Q7OyBjb2xv
cjojMUY0OTdEIj4mbmJzcDs8L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4g
c3R5bGU9ImZvbnQtc2l6ZToxMS4wcHQ7IGZvbnQtZmFtaWx5OiZxdW90O0NhbGlicmkmcXVvdDss
JnF1b3Q7c2Fucy1zZXJpZiZxdW90OzsgY29sb3I6IzFGNDk3RCI+SW4gc2VjdGlvbiAxMiwg4oCc
QWx0ZXJuYXRpdmUgVGltZSBTY2FsZXPigJ0gc2hvdWxkIGJlIOKAnEFsdGVybmF0ZSBUaW1lc2Nh
bGVz4oCdLjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9u
dC1zaXplOjExLjBwdDsgZm9udC1mYW1pbHk6JnF1b3Q7Q2FsaWJyaSZxdW90OywmcXVvdDtzYW5z
LXNlcmlmJnF1b3Q7OyBjb2xvcjojMUY0OTdEIj4mbmJzcDs8L3NwYW4+PC9wPg0KPHAgY2xhc3M9
Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMS4wcHQ7IGZvbnQtZmFtaWx5OiZx
dW90O0NhbGlicmkmcXVvdDssJnF1b3Q7c2Fucy1zZXJpZiZxdW90OzsgY29sb3I6IzFGNDk3RCI+
Jm5ic3A7PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250
LXNpemU6MTEuMHB0OyBmb250LWZhbWlseTomcXVvdDtDYWxpYnJpJnF1b3Q7LCZxdW90O3NhbnMt
c2VyaWYmcXVvdDs7IGNvbG9yOiMxRjQ5N0QiPlJlZ2FyZHMsPC9zcGFuPjwvcD4NCjxwIGNsYXNz
PSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTEuMHB0OyBmb250LWZhbWlseTom
cXVvdDtDYWxpYnJpJnF1b3Q7LCZxdW90O3NhbnMtc2VyaWYmcXVvdDs7IGNvbG9yOiMxRjQ5N0Qi
PkpvaG4gRmxldGNoZXI8L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5
bGU9ImZvbnQtc2l6ZToxMS4wcHQ7IGZvbnQtZmFtaWx5OiZxdW90O0NhbGlicmkmcXVvdDssJnF1
b3Q7c2Fucy1zZXJpZiZxdW90OzsgY29sb3I6IzFGNDk3RCI+Jm5ic3A7PC9zcGFuPjwvcD4NCjxw
IGNsYXNzPSJNc29Ob3JtYWwiPjxiPjxzcGFuIGxhbmc9IkVOLVVTIiBzdHlsZT0iZm9udC1zaXpl
OjEwLjBwdDsgZm9udC1mYW1pbHk6JnF1b3Q7VGFob21hJnF1b3Q7LCZxdW90O3NhbnMtc2VyaWYm
cXVvdDsiPkZyb206PC9zcGFuPjwvYj48c3BhbiBsYW5nPSJFTi1VUyIgc3R5bGU9ImZvbnQtc2l6
ZToxMC4wcHQ7IGZvbnQtZmFtaWx5OiZxdW90O1RhaG9tYSZxdW90OywmcXVvdDtzYW5zLXNlcmlm
JnF1b3Q7Ij4gdGljdG9jLWJvdW5jZXNAaWV0Zi5vcmcgW21haWx0bzp0aWN0b2MtYm91bmNlc0Bp
ZXRmLm9yZ10NCjxiPk9uIEJlaGFsZiBPZiA8L2I+RG91Z2xhcyBBcm5vbGQ8YnI+DQo8Yj5TZW50
OjwvYj4gMjUgT2N0b2JlciAyMDEzIDAxOjM1PGJyPg0KPGI+VG86PC9iPiB0aWN0b2NAaWV0Zi5v
cmc8YnI+DQo8Yj5TdWJqZWN0OjwvYj4gW1RJQ1RPQ10gRW50ZXJwcmlzZSBQcm9maWxlPC9zcGFu
PjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPiZuYnNwOzwvcD4NCjxkaXY+DQo8cCBjbGFzcz0i
TXNvTm9ybWFsIj5IZWxsbyBFdmVyeW9uZSw8L3A+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1h
bCI+Jm5ic3A7PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+QXR0YWNo
ZWQgaXMgYW4gdXBkYXRlZCB2ZXJzaW9uIG9mIHRoZSBFbnRlcnByaXNlIHByb2ZpbGUuICZuYnNw
O1NvcnJ5IEkgbWlzc2VkIHRoZSB1cGxvYWQgZGVhZGxpbmUgZm9yJm5ic3A7Jm5ic3A7dGhlIFZh
bmNvdXZlciBtZWV0aW5nLiAmbmJzcDtJZiB5b3UgZ2V0IGEgY2hhbmNlIHRvIGxvb2sgYXQgaXQg
YmVmb3JlIHRoZW4gSSB3aWxsIGJlIHRoZXJlIGFuZCB3b3VsZCBsb3ZlIHRvIGRpc2N1c3MgaXQu
Jm5ic3A7PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+Jm5ic3A7PC9w
Pg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+U3VtbWFyeSBvZiBjaGFuZ2Vz
OjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPiZuYnNwOzwvcD4NCjwv
ZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6
OS41cHQ7IGZvbnQtZmFtaWx5OiZxdW90O0FyaWFsJnF1b3Q7LCZxdW90O3NhbnMtc2VyaWYmcXVv
dDsiPkkgYWxzbyBjaGFuZ2VkIHRoZSBUTFYgZm9ybWF0IHRvIGZpdCB0aGUgbGF0ZXN0IHByb3Bv
c2FsIGluIHRoZSAxNTg4IHJldmlzaW9uLiAmbmJzcDs8L3NwYW4+PC9wPg0KPC9kaXY+DQo8ZGl2
Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+Jm5ic3A7PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xh
c3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZTo5LjVwdDsgZm9udC1mYW1pbHk6
JnF1b3Q7QXJpYWwmcXVvdDssJnF1b3Q7c2Fucy1zZXJpZiZxdW90OyI+SSBhZGRlZCBhIHN0YXRl
bWVudCBhYm91dCBub3QgZ29pbmcgaW50byB0aGUgbWFzdGVyIHN0YXRlIHVubGVzcyBvbmUgaGFk
IGEgY3VycmVudCBVVEMgb2Zmc2V0LiAmbmJzcDs8L3NwYW4+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0K
PHAgY2xhc3M9Ik1zb05vcm1hbCI+Jm5ic3A7PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9
Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZTo5LjVwdDsgZm9udC1mYW1pbHk6JnF1
b3Q7QXJpYWwmcXVvdDssJnF1b3Q7c2Fucy1zZXJpZiZxdW90OyI+SSBhZGRlZCB0byB0aGUgVExW
IGZpZWxkcyB0byBpbmRpY2F0ZSBtYXhpbXVtIHBoYXNlIGNvcnJlY3Rpb24gb3ZlciBhIHN5bmMg
Y3ljbGUuPC9zcGFuPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9y
bWFsIj4mbmJzcDs8L3A+DQo8L2Rpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPi0tIDwvcD4NCjxk
aXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj5Eb3VnIEFybm9sZDwvcD4NCjxkaXY+DQo8cCBjbGFz
cz0iTXNvTm9ybWFsIj5QcmluY2lwYWwgVGVjaG5vbG9naXN0PC9wPg0KPGRpdj4NCjxwIGNsYXNz
PSJNc29Ob3JtYWwiPjxpPkpUaW1lITwvaT4mbmJzcDtNZWluYmVyZyBVU0E8L3A+DQo8L2Rpdj4N
CjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPiYjNDM7MS03MDctMzAzLTU1NTk8
L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj4mbmJzcDs8L3A+DQo8L2Rp
dj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj4mbmJzcDs8L3A+DQo8L2Rpdj4NCjwvZGl2
Pg0KPC9kaXY+DQo8L2Rpdj4NCjwvZGl2Pg0KPHA+PC9wPg0KPHAgY2xhc3M9IjRhZWIwZTBmLWM2
N2YtNDJjZS1iYzM1LTZkMTc1ZmNiZDNjZCI+Jm5ic3A7PC9wPg0KPHAgY2xhc3M9IjRhZWIwZTBm
LWM2N2YtNDJjZS1iYzM1LTZkMTc1ZmNiZDNjZCI+LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LTxicj4NCjxmb250IHNpemU9IjMiIGZhY2U9IlRpbWVzIE5ldyBSb21hbiI+PGZvbnQgc2l6ZT0i
MyIgZmFjZT0iVGltZXMgTmV3IFJvbWFuIj48Zm9udCBzaXplPSIzIiBmYWNlPSJUaW1lcyBOZXcg
Um9tYW4iPjxicj4NCjxmb250IHNpemU9IjMiIGZhY2U9IlRpbWVzIE5ldyBSb21hbiI+PGEgaHJl
Zj0iaHR0cDovL3d3dy5iYmMuY28udWsiIHRhcmdldD0iX2JsYW5rIj5odHRwOi8vd3d3LjxzcGFu
IGNsYXNzPSJpbCI+YmJjPC9zcGFuPi48c3BhbiBjbGFzcz0iaWwiPmNvPC9zcGFuPi48c3BhbiBj
bGFzcz0iaWwiPnVrPC9zcGFuPjwvYT48YnI+DQpUaGlzIGUtbWFpbCAoYW5kIGFueSBhdHRhY2ht
ZW50cykgaXMgY29uZmlkZW50aWFsIGFuZCBtYXkgY29udGFpbiBwZXJzb25hbCB2aWV3cyB3aGlj
aCBhcmUgbm90IHRoZSB2aWV3cyBvZiB0aGUNCjxzcGFuIGNsYXNzPSJpbCI+QkJDPC9zcGFuPiB1
bmxlc3Mgc3BlY2lmaWNhbGx5IHN0YXRlZC48YnI+DQpJZiB5b3UgaGF2ZSByZWNlaXZlZCBpdCBp
biBlcnJvciwgcGxlYXNlIGRlbGV0ZSBpdCBmcm9tIHlvdXIgc3lzdGVtLjxicj4NCkRvIG5vdCB1
c2UsIGNvcHkgb3IgZGlzY2xvc2UgdGhlIGluZm9ybWF0aW9uIGluIGFueSB3YXkgbm9yIGFjdCBp
biByZWxpYW5jZSBvbiBpdCBhbmQgbm90aWZ5IHRoZSBzZW5kZXIgaW1tZWRpYXRlbHkuPGJyPg0K
UGxlYXNlIG5vdGUgdGhhdCB0aGUgPHNwYW4gY2xhc3M9ImlsIj5CQkM8L3NwYW4+IG1vbml0b3Jz
IGUtbWFpbHMgc2VudCBvciByZWNlaXZlZC48YnI+DQpGdXJ0aGVyIGNvbW11bmljYXRpb24gd2ls
bCBzaWduaWZ5IHlvdXIgY29uc2VudCB0byB0aGlzLjwvZm9udD48L2ZvbnQ+PC9mb250PjwvZm9u
dD48L3A+DQo8cCBjbGFzcz0iNGFlYjBlMGYtYzY3Zi00MmNlLWJjMzUtNmQxNzVmY2JkM2NkIj4t
LS0tLS0tLS0tLS0tLS0tLS0tLS08L3A+DQo8L2Rpdj4NCjwvZGl2Pg0KPC9kaXY+DQo8L2Rpdj4N
CjxwPjwvcD4NCjxwIGNsYXNzPSI1ZWUzYWFmNi02MjY0LTQ0NDEtYjE4OC02MTYwMjM5Zjg0MzIi
PiZuYnNwOzwvcD4NCjxwIGNsYXNzPSI1ZWUzYWFmNi02MjY0LTQ0NDEtYjE4OC02MTYwMjM5Zjg0
MzIiPi0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS08YnI+DQo8Zm9udCBzaXplPSIzIiBmYWNl
PSJUaW1lcyBOZXcgUm9tYW4iPjxmb250IHNpemU9IjMiIGZhY2U9IlRpbWVzIE5ldyBSb21hbiI+
PGZvbnQgc2l6ZT0iMyIgZmFjZT0iVGltZXMgTmV3IFJvbWFuIj48YnI+DQo8Zm9udCBzaXplPSIz
IiBmYWNlPSJUaW1lcyBOZXcgUm9tYW4iPjxhIGhyZWY9Imh0dHA6Ly93d3cuYmJjLmNvLnVrIiB0
YXJnZXQ9Il9ibGFuayI+aHR0cDovL3d3dy48c3BhbiBjbGFzcz0iaWwiPmJiYzwvc3Bhbj4uPHNw
YW4gY2xhc3M9ImlsIj5jbzwvc3Bhbj4uPHNwYW4gY2xhc3M9ImlsIj51azwvc3Bhbj48L2E+PGJy
Pg0KVGhpcyBlLW1haWwgKGFuZCBhbnkgYXR0YWNobWVudHMpIGlzIGNvbmZpZGVudGlhbCBhbmQg
bWF5IGNvbnRhaW4gcGVyc29uYWwgdmlld3Mgd2hpY2ggYXJlIG5vdCB0aGUgdmlld3Mgb2YgdGhl
DQo8c3BhbiBjbGFzcz0iaWwiPkJCQzwvc3Bhbj4gdW5sZXNzIHNwZWNpZmljYWxseSBzdGF0ZWQu
PGJyPg0KSWYgeW91IGhhdmUgcmVjZWl2ZWQgaXQgaW4gZXJyb3IsIHBsZWFzZSBkZWxldGUgaXQg
ZnJvbSB5b3VyIHN5c3RlbS48YnI+DQpEbyBub3QgdXNlLCBjb3B5IG9yIGRpc2Nsb3NlIHRoZSBp
bmZvcm1hdGlvbiBpbiBhbnkgd2F5IG5vciBhY3QgaW4gcmVsaWFuY2Ugb24gaXQgYW5kIG5vdGlm
eSB0aGUgc2VuZGVyIGltbWVkaWF0ZWx5Ljxicj4NClBsZWFzZSBub3RlIHRoYXQgdGhlIDxzcGFu
IGNsYXNzPSJpbCI+QkJDPC9zcGFuPiBtb25pdG9ycyBlLW1haWxzIHNlbnQgb3IgcmVjZWl2ZWQu
PGJyPg0KRnVydGhlciBjb21tdW5pY2F0aW9uIHdpbGwgc2lnbmlmeSB5b3VyIGNvbnNlbnQgdG8g
dGhpcy48L2ZvbnQ+PC9mb250PjwvZm9udD48L2ZvbnQ+PC9wPg0KPHAgY2xhc3M9IjVlZTNhYWY2
LTYyNjQtNDQ0MS1iMTg4LTYxNjAyMzlmODQzMiI+LS0tLS0tLS0tLS0tLS0tLS0tLS0tPC9wPg0K
PC9ib2R5Pg0KPC9odG1sPg0K

--_000_B1D49063AD5FBD4688F3EEDEC68B20175113E0AABGB01XUD1011nat_--

From kevin.b.stanton@gmail.com  Mon Oct 28 10:52:29 2013
Return-Path: <kevin.b.stanton@gmail.com>
X-Original-To: tictoc@ietfa.amsl.com
Delivered-To: tictoc@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4433411E814C for <tictoc@ietfa.amsl.com>; Mon, 28 Oct 2013 10:52:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id uF5BaoVAHa57 for <tictoc@ietfa.amsl.com>; Mon, 28 Oct 2013 10:52:28 -0700 (PDT)
Received: from mail-ee0-x232.google.com (mail-ee0-x232.google.com [IPv6:2a00:1450:4013:c00::232]) by ietfa.amsl.com (Postfix) with ESMTP id DF32511E81A5 for <tictoc@ietf.org>; Mon, 28 Oct 2013 10:52:24 -0700 (PDT)
Received: by mail-ee0-f50.google.com with SMTP id l10so3608230eei.9 for <tictoc@ietf.org>; Mon, 28 Oct 2013 10:52:24 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=RFLL7NUTiS6NwbupqPMMoPK9Lw+wq/31aDdHgKumfpE=; b=XBwQXLyxi6F0Af0/YXW1SYq3BbqU0i93k2OpbYaQGgNZFd8ngkSbR+7iluqLpPQ9Gc AiEVmSwjbE/nSKFyUReN5qTBB/7f80+W5DXCyxRZhsBf4goxxmyVe309p4hupcU29kkE ApZjWB572Xg7TiELqCs/NoyVMLniaz3xy1NYqODBBHmroY4GFDgiOgd6zD8fnnkADcUJ TsnK38lUZnrqaFYMnsc+TmdCA1S7DnMGh4jaLvYyE9zTFTrDMyjWnUi993qu3LN7XHmV IcDQJu9MMVESwfRSWnaayZOSNnCl9KN1u2TsHHoWG8kJ3otlStRTAKx50PIEr6A/VcH2 ZErg==
X-Received: by 10.15.99.72 with SMTP id bk48mr23563909eeb.22.1382982743867; Mon, 28 Oct 2013 10:52:23 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.14.142.198 with HTTP; Mon, 28 Oct 2013 10:52:03 -0700 (PDT)
In-Reply-To: <74470498B659FA4687F0B0018C19A89C01B87D8329E8@IL-MB01.marvell.com>
References: <74470498B659FA4687F0B0018C19A89C01B87D7A40A6@IL-MB01.marvell.com> <526C30F9.1040400@ntp.org> <74470498B659FA4687F0B0018C19A89C01B87D7A4C6E@IL-MB01.marvell.com> <526D165D.3040902@ntp.org> <74470498B659FA4687F0B0018C19A89C01B87D7A4DC7@IL-MB01.marvell.com> <526D671A.7050908@ntp.org> <74470498B659FA4687F0B0018C19A89C01B87D7A4EB8@IL-MB01.marvell.com> <E1Vahsr-000Kke-9c@stenn.ntp.org> <74470498B659FA4687F0B0018C19A89C01B87D8329E8@IL-MB01.marvell.com>
From: Kevin Stanton <kevin.b.stanton@gmail.com>
Date: Mon, 28 Oct 2013 10:52:03 -0700
Message-ID: <CA++G9tCYC_fmMiXN-Y22EKLYU_hrXGyQGixNnyVjPx01ki1JmQ@mail.gmail.com>
To: Tal Mizrahi <talmi@marvell.com>
Content-Type: multipart/alternative; boundary=089e016816162dc6d604e9d0c31b
Cc: "ntpwg@lists.ntp.org" <ntpwg@lists.ntp.org>, Harlan Stenn <stenn@ntp.org>, "tictoc@ietf.org" <tictoc@ietf.org>
Subject: Re: [TICTOC] [ntpwg] New version of draft-mizrahi-ntp-checksum-trailer
X-BeenThere: tictoc@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Timing over IP Connection and Transfer of Clock BOF <tictoc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tictoc>, <mailto:tictoc-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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>
X-List-Received-Date: Mon, 28 Oct 2013 17:52:29 -0000

--089e016816162dc6d604e9d0c31b
Content-Type: text/plain; charset=ISO-8859-1

This is a somewhat unrelated question, but why not eliminate the servo?

If a software entity is the consumer of PTP time, I wonder if the benefit
of avoiding the y=mx+b computation (to compute PTP time from the time of
the free-running LAN hardware counter) is worth the trouble of disciplining
the hardware clock.

In other words, the hardware engine maintains a time reference and software
maintains the parameters for translating that time reference to PTP time
(also for hardware-captured Rx and Tx timestamps).  Of course, this doesn't
apply to one-step master ports.

Thoughts?

Kevin Stanton.


On Mon, Oct 28, 2013 at 1:38 AM, Tal Mizrahi <talmi@marvell.com> wrote:

> Hi Harlan,
>
> >In the "Figure 1" case "core" packet timestamps come from the kernel and
> the new packet timestamp will be added by the hardware engine.
> >I understand the following question is outside the scope of this
> document, but how can one determine how well sync'd the internal clock is
> with the clock in the accurate timestamp engine?
>
> Well, indeed it is strictly an implementation question. For example, in
> typical PTP implementations (that I am familiar with) the accurate clock is
> only maintained in one place, i.e., in the HW engine. The SW stack includes
> the servo algorithm; the SW stack regularly computes the necessary offset
> or frequency adjustments, and whenever necessary sends update commands to
> the HW engine about these adjustments. Thus, the SW stack does not need to
> maintain an additional clock, since all its computations are performed WRT
> the HW clock.
>
> Thanks,
> Tal.
>
>
> -----Original Message-----
> From: Harlan Stenn [mailto:stenn@ntp.org]
> Sent: Monday, October 28, 2013 10:09 AM
> To: Tal Mizrahi
> Cc: mayer@ntp.org; ntpwg@lists.ntp.org; tictoc@ietf.org
> Subject: Re: [ntpwg] New version of draft-mizrahi-ntp-checksum-trailer
>
> Just some thoughts, and I hope I'm awake enough to type this...
>
> There seem to be several issues here.
>
> In the "Figure 1" case "core" packet timestamps come from the kernel and
> the new packet timestamp will be added by the hardware engine.  I
> understand the following question is outside the scope of this document,
> but how can one determine how well sync'd the internal clock is with the
> clock in the accurate timestamp engine?
>
> If we have TX and RX hardware timestamping capabilities, we can use NTP's
> interleave mode to communicate these timestamps as well.  Having said that,
> I'm sure there is something to be learned from implementing Tal's proposal.
>
> H
> _______________________________________________
> TICTOC mailing list
> TICTOC@ietf.org
> https://www.ietf.org/mailman/listinfo/tictoc
>

--089e016816162dc6d604e9d0c31b
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div>This is a somewhat unrelated question, but why not el=
iminate the servo?</div><div><br></div><div>If a software entity is the con=
sumer of PTP time, I wonder if the benefit of avoiding the y=3Dmx+b computa=
tion (to compute PTP time from the time of the free-running LAN hardware co=
unter) is worth the trouble of disciplining the hardware clock.<br>


</div><div><br></div><div>In other words, the hardware engine maintains a t=
ime reference and software maintains the parameters for translating that ti=
me reference to PTP time (also for hardware-captured Rx and Tx timestamps).=
 =A0Of course, this doesn&#39;t apply to one-step master ports.</div>


<div><br></div><div>Thoughts?</div><div><br></div><div>Kevin Stanton.</div>=
<div class=3D"gmail_extra"><br><br><div class=3D"gmail_quote">On Mon, Oct 2=
8, 2013 at 1:38 AM, Tal Mizrahi <span dir=3D"ltr">&lt;<a href=3D"mailto:tal=
mi@marvell.com" target=3D"_blank">talmi@marvell.com</a>&gt;</span> wrote:<b=
r>


<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">Hi Harlan,<br>
<div><br>
&gt;In the &quot;Figure 1&quot; case &quot;core&quot; packet timestamps com=
e from the kernel and the new packet timestamp will be added by the hardwar=
e engine.<br>
&gt;I understand the following question is outside the scope of this docume=
nt, but how can one determine how well sync&#39;d the internal clock is wit=
h the clock in the accurate timestamp engine?<br>
<br>
</div>Well, indeed it is strictly an implementation question. For example, =
in typical PTP implementations (that I am familiar with) the accurate clock=
 is only maintained in one place, i.e., in the HW engine. The SW stack incl=
udes the servo algorithm; the SW stack regularly computes the necessary off=
set or frequency adjustments, and whenever necessary sends update commands =
to the HW engine about these adjustments. Thus, the SW stack does not need =
to maintain an additional clock, since all its computations are performed W=
RT the HW clock.<br>



<br>
Thanks,<br>
Tal.<br>
<div><br>
<br>
-----Original Message-----<br>
From: Harlan Stenn [mailto:<a href=3D"mailto:stenn@ntp.org" target=3D"_blan=
k">stenn@ntp.org</a>]<br>
Sent: Monday, October 28, 2013 10:09 AM<br>
To: Tal Mizrahi<br>
Cc: <a href=3D"mailto:mayer@ntp.org" target=3D"_blank">mayer@ntp.org</a>; <=
a href=3D"mailto:ntpwg@lists.ntp.org" target=3D"_blank">ntpwg@lists.ntp.org=
</a>; <a href=3D"mailto:tictoc@ietf.org" target=3D"_blank">tictoc@ietf.org<=
/a><br>


Subject: Re: [ntpwg] New version of draft-mizrahi-ntp-checksum-trailer<br>
<br>
</div><div><div>Just some thoughts, and I hope I&#39;m awake enough to type=
 this...<br>
<br>
There seem to be several issues here.<br>
<br>
In the &quot;Figure 1&quot; case &quot;core&quot; packet timestamps come fr=
om the kernel and the new packet timestamp will be added by the hardware en=
gine. =A0I understand the following question is outside the scope of this d=
ocument, but how can one determine how well sync&#39;d the internal clock i=
s with the clock in the accurate timestamp engine?<br>



<br>
If we have TX and RX hardware timestamping capabilities, we can use NTP&#39=
;s interleave mode to communicate these timestamps as well. =A0Having said =
that, I&#39;m sure there is something to be learned from implementing Tal&#=
39;s proposal.<br>



<br>
H<br>
_______________________________________________<br>
TICTOC mailing list<br>
<a href=3D"mailto:TICTOC@ietf.org" target=3D"_blank">TICTOC@ietf.org</a><br=
>
<a href=3D"https://www.ietf.org/mailman/listinfo/tictoc" target=3D"_blank">=
https://www.ietf.org/mailman/listinfo/tictoc</a><br>
</div></div></blockquote></div><br></div></div>

--089e016816162dc6d604e9d0c31b--

From btv1==013fb014d0b==gdowd@symmetricom.com  Mon Oct 28 11:16:32 2013
Return-Path: <btv1==013fb014d0b==gdowd@symmetricom.com>
X-Original-To: tictoc@ietfa.amsl.com
Delivered-To: tictoc@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7C92311E8295 for <tictoc@ietfa.amsl.com>; Mon, 28 Oct 2013 11:16:32 -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=[BAYES_00=-2.599, HTML_MESSAGE=0.001, IP_NOT_FRIENDLY=0.334]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id l7NHNb-0ihUY for <tictoc@ietfa.amsl.com>; Mon, 28 Oct 2013 11:16:28 -0700 (PDT)
Received: from mail5.symmetricom.com (mail5.symmetricom.com [69.25.98.10]) by ietfa.amsl.com (Postfix) with ESMTP id E567D11E8155 for <tictoc@ietf.org>; Mon, 28 Oct 2013 11:16:14 -0700 (PDT)
X-ASG-Debug-ID: 1382984173-05bdbc07004c3b90001-4wH9i1
Received: from SJC-HUB-01.symmetricom.com ([192.168.10.171]) by mail5.symmetricom.com with ESMTP id dvc3tTEDzeG9DUA5 (version=TLSv1 cipher=AES128-SHA bits=128 verify=NO); Mon, 28 Oct 2013 11:16:13 -0700 (PDT)
X-Barracuda-Envelope-From: gdowd@symmetricom.com
X-ASG-Whitelist: Client
Received: from SJC-MBX-01.symmetricom.com ([169.254.1.121]) by SJC-HUB-01.symmetricom.com ([::1]) with mapi id 14.01.0289.001; Mon, 28 Oct 2013 11:16:13 -0700
From: Greg Dowd <gdowd@symmetricom.com>
To: Kevin Stanton <kevin.b.stanton@gmail.com>, Tal Mizrahi <talmi@marvell.com>
Thread-Topic: [TICTOC] [ntpwg] New version of draft-mizrahi-ntp-checksum-trailer
X-ASG-Orig-Subj: RE: [TICTOC] [ntpwg] New version of draft-mizrahi-ntp-checksum-trailer
Thread-Index: AQHO1AZ5DH+wauYAB0ajhRxEI/xQ5JoKaQjQ
Date: Mon, 28 Oct 2013 18:16:13 +0000
Message-ID: <26FBD265CD8D234EAF41115A180F92BB6ED68392@SJC-MBX-01.symmetricom.com>
References: <74470498B659FA4687F0B0018C19A89C01B87D7A40A6@IL-MB01.marvell.com> <526C30F9.1040400@ntp.org> <74470498B659FA4687F0B0018C19A89C01B87D7A4C6E@IL-MB01.marvell.com> <526D165D.3040902@ntp.org> <74470498B659FA4687F0B0018C19A89C01B87D7A4DC7@IL-MB01.marvell.com> <526D671A.7050908@ntp.org> <74470498B659FA4687F0B0018C19A89C01B87D7A4EB8@IL-MB01.marvell.com> <E1Vahsr-000Kke-9c@stenn.ntp.org> <74470498B659FA4687F0B0018C19A89C01B87D8329E8@IL-MB01.marvell.com> <CA++G9tCYC_fmMiXN-Y22EKLYU_hrXGyQGixNnyVjPx01ki1JmQ@mail.gmail.com>
In-Reply-To: <CA++G9tCYC_fmMiXN-Y22EKLYU_hrXGyQGixNnyVjPx01ki1JmQ@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [192.168.3.29]
Content-Type: multipart/alternative; boundary="_000_26FBD265CD8D234EAF41115A180F92BB6ED68392SJCMBX01symmetr_"
MIME-Version: 1.0
X-Barracuda-Connect: UNKNOWN[192.168.10.171]
X-Barracuda-Start-Time: 1382984173
X-Barracuda-Encrypted: AES128-SHA
X-Barracuda-URL: http://192.168.10.96:80/cgi-mod/mark.cgi
X-Virus-Scanned: by bsmtpd at symmetricom.com
X-Barracuda-BRTS-Status: 1
Cc: "ntpwg@lists.ntp.org" <ntpwg@lists.ntp.org>, Harlan Stenn <stenn@ntp.org>, "tictoc@ietf.org" <tictoc@ietf.org>
Subject: Re: [TICTOC] [ntpwg] New version of	draft-mizrahi-ntp-checksum-trailer
X-BeenThere: tictoc@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Timing over IP Connection and Transfer of Clock BOF <tictoc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tictoc>, <mailto:tictoc-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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>
X-List-Received-Date: Mon, 28 Oct 2013 18:17:06 -0000

--_000_26FBD265CD8D234EAF41115A180F92BB6ED68392SJCMBX01symmetr_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

There are a variety of different implementation techniques, some of which d=
o use free-running counters on the hw side, mapped to a software function u=
p higher.  Some NIC vendors are already doing that.  One of the challenges =
for that type of operation is that the entire system must be aware and desi=
gned for that purpose until kernels/drivers/applications catch up.  The bea=
uty of the "inline" function is that it can be inserted into the process, c=
orrecting errors on the input and/or output without changing the system at =
other layers.

The tight coupling of the servo to the timing hardware also tends to allow =
better precision in many cases, running in real-time or at high(er) data ra=
tes.  For some of our designs, we are synchronizing slave clocks in the sub=
 100ns (or better) in the presence of very high traffic loads.  Obviously, =
the application for this class of synchronization service is much more targ=
eted than Internet (capital I) but the market does exist so why not use the=
 technology.

From: tictoc-bounces@ietf.org [mailto:tictoc-bounces@ietf.org] On Behalf Of=
 Kevin Stanton
Sent: Monday, October 28, 2013 10:52 AM
To: Tal Mizrahi
Cc: ntpwg@lists.ntp.org; Harlan Stenn; tictoc@ietf.org
Subject: Re: [TICTOC] [ntpwg] New version of draft-mizrahi-ntp-checksum-tra=
iler

This is a somewhat unrelated question, but why not eliminate the servo?

If a software entity is the consumer of PTP time, I wonder if the benefit o=
f avoiding the y=3Dmx+b computation (to compute PTP time from the time of t=
he free-running LAN hardware counter) is worth the trouble of disciplining =
the hardware clock.

In other words, the hardware engine maintains a time reference and software=
 maintains the parameters for translating that time reference to PTP time (=
also for hardware-captured Rx and Tx timestamps).  Of course, this doesn't =
apply to one-step master ports.

Thoughts?

Kevin Stanton.

On Mon, Oct 28, 2013 at 1:38 AM, Tal Mizrahi <talmi@marvell.com<mailto:talm=
i@marvell.com>> wrote:
Hi Harlan,

>In the "Figure 1" case "core" packet timestamps come from the kernel and t=
he new packet timestamp will be added by the hardware engine.
>I understand the following question is outside the scope of this document,=
 but how can one determine how well sync'd the internal clock is with the c=
lock in the accurate timestamp engine?
Well, indeed it is strictly an implementation question. For example, in typ=
ical PTP implementations (that I am familiar with) the accurate clock is on=
ly maintained in one place, i.e., in the HW engine. The SW stack includes t=
he servo algorithm; the SW stack regularly computes the necessary offset or=
 frequency adjustments, and whenever necessary sends update commands to the=
 HW engine about these adjustments. Thus, the SW stack does not need to mai=
ntain an additional clock, since all its computations are performed WRT the=
 HW clock.

Thanks,
Tal.


-----Original Message-----
From: Harlan Stenn [mailto:stenn@ntp.org<mailto:stenn@ntp.org>]
Sent: Monday, October 28, 2013 10:09 AM
To: Tal Mizrahi
Cc: mayer@ntp.org<mailto:mayer@ntp.org>; ntpwg@lists.ntp.org<mailto:ntpwg@l=
ists.ntp.org>; tictoc@ietf.org<mailto:tictoc@ietf.org>
Subject: Re: [ntpwg] New version of draft-mizrahi-ntp-checksum-trailer
Just some thoughts, and I hope I'm awake enough to type this...

There seem to be several issues here.

In the "Figure 1" case "core" packet timestamps come from the kernel and th=
e new packet timestamp will be added by the hardware engine.  I understand =
the following question is outside the scope of this document, but how can o=
ne determine how well sync'd the internal clock is with the clock in the ac=
curate timestamp engine?

If we have TX and RX hardware timestamping capabilities, we can use NTP's i=
nterleave mode to communicate these timestamps as well.  Having said that, =
I'm sure there is something to be learned from implementing Tal's proposal.

H
_______________________________________________
TICTOC mailing list
TICTOC@ietf.org<mailto:TICTOC@ietf.org>
https://www.ietf.org/mailman/listinfo/tictoc


--_000_26FBD265CD8D234EAF41115A180F92BB6ED68392SJCMBX01symmetr_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:x=3D"urn:schemas-microsoft-com:office:excel" xmlns:p=3D"urn:schemas-m=
icrosoft-com:office:powerpoint" xmlns:a=3D"urn:schemas-microsoft-com:office=
:access" xmlns:dt=3D"uuid:C2F41010-65B3-11d1-A29F-00AA00C14882" xmlns:s=3D"=
uuid:BDC6E3F0-6DA3-11d1-A2A3-00AA00C14882" xmlns:rs=3D"urn:schemas-microsof=
t-com:rowset" xmlns:z=3D"#RowsetSchema" xmlns:b=3D"urn:schemas-microsoft-co=
m:office:publisher" xmlns:ss=3D"urn:schemas-microsoft-com:office:spreadshee=
t" xmlns:c=3D"urn:schemas-microsoft-com:office:component:spreadsheet" xmlns=
:odc=3D"urn:schemas-microsoft-com:office:odc" xmlns:oa=3D"urn:schemas-micro=
soft-com:office:activation" xmlns:html=3D"http://www.w3.org/TR/REC-html40" =
xmlns:q=3D"http://schemas.xmlsoap.org/soap/envelope/" xmlns:rtc=3D"http://m=
icrosoft.com/officenet/conferencing" xmlns:D=3D"DAV:" xmlns:Repl=3D"http://=
schemas.microsoft.com/repl/" xmlns:mt=3D"http://schemas.microsoft.com/share=
point/soap/meetings/" xmlns:x2=3D"http://schemas.microsoft.com/office/excel=
/2003/xml" xmlns:ppda=3D"http://www.passport.com/NameSpace.xsd" xmlns:ois=
=3D"http://schemas.microsoft.com/sharepoint/soap/ois/" xmlns:dir=3D"http://=
schemas.microsoft.com/sharepoint/soap/directory/" xmlns:ds=3D"http://www.w3=
.org/2000/09/xmldsig#" xmlns:dsp=3D"http://schemas.microsoft.com/sharepoint=
/dsp" xmlns:udc=3D"http://schemas.microsoft.com/data/udc" xmlns:xsd=3D"http=
://www.w3.org/2001/XMLSchema" xmlns:sub=3D"http://schemas.microsoft.com/sha=
repoint/soap/2002/1/alerts/" xmlns:ec=3D"http://www.w3.org/2001/04/xmlenc#"=
 xmlns:sp=3D"http://schemas.microsoft.com/sharepoint/" xmlns:sps=3D"http://=
schemas.microsoft.com/sharepoint/soap/" xmlns:xsi=3D"http://www.w3.org/2001=
/XMLSchema-instance" xmlns:udcs=3D"http://schemas.microsoft.com/data/udc/so=
ap" xmlns:udcxf=3D"http://schemas.microsoft.com/data/udc/xmlfile" xmlns:udc=
p2p=3D"http://schemas.microsoft.com/data/udc/parttopart" xmlns:wf=3D"http:/=
/schemas.microsoft.com/sharepoint/soap/workflow/" xmlns:dsss=3D"http://sche=
mas.microsoft.com/office/2006/digsig-setup" xmlns:dssi=3D"http://schemas.mi=
crosoft.com/office/2006/digsig" xmlns:mdssi=3D"http://schemas.openxmlformat=
s.org/package/2006/digital-signature" xmlns:mver=3D"http://schemas.openxmlf=
ormats.org/markup-compatibility/2006" xmlns:m=3D"http://schemas.microsoft.c=
om/office/2004/12/omml" xmlns:mrels=3D"http://schemas.openxmlformats.org/pa=
ckage/2006/relationships" xmlns:spwp=3D"http://microsoft.com/sharepoint/web=
partpages" xmlns:ex12t=3D"http://schemas.microsoft.com/exchange/services/20=
06/types" xmlns:ex12m=3D"http://schemas.microsoft.com/exchange/services/200=
6/messages" xmlns:pptsl=3D"http://schemas.microsoft.com/sharepoint/soap/Sli=
deLibrary/" xmlns:spsl=3D"http://microsoft.com/webservices/SharePointPortal=
Server/PublishedLinksService" xmlns:Z=3D"urn:schemas-microsoft-com:" xmlns:=
st=3D"&#1;" xmlns=3D"http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
<meta name=3D"Generator" content=3D"Microsoft Word 12 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
span.EmailStyle17
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=3D"EN-US" link=3D"blue" vlink=3D"purple">
<div class=3D"WordSection1">
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">There are a variety of di=
fferent implementation techniques, some of which do use free-running counte=
rs on the hw side, mapped to a software function up higher.&nbsp;
 Some NIC vendors are already doing that.&nbsp; One of the challenges for t=
hat type of operation is that the entire system must be aware and designed =
for that purpose until kernels/drivers/applications catch up.&nbsp; The bea=
uty of the &#8220;inline&#8221; function is that it can
 be inserted into the process, correcting errors on the input and/or output=
 without changing the system at other layers.&nbsp;
<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">The tight coupling of the=
 servo to the timing hardware also tends to allow better precision in many =
cases, running in real-time or at high(er) data rates.&nbsp;
 For some of our designs, we are synchronizing slave clocks in the sub 100n=
s (or better) in the presence of very high traffic loads.&nbsp; Obviously, =
the application for this class of synchronization service is much more targ=
eted than Internet (capital I) but the
 market does exist so why not use the technology.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<div style=3D"border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in =
0in 0in">
<p class=3D"MsoNormal"><b><span style=3D"font-size:10.0pt;font-family:&quot=
;Tahoma&quot;,&quot;sans-serif&quot;">From:</span></b><span style=3D"font-s=
ize:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;"> tictoc-b=
ounces@ietf.org [mailto:tictoc-bounces@ietf.org]
<b>On Behalf Of </b>Kevin Stanton<br>
<b>Sent:</b> Monday, October 28, 2013 10:52 AM<br>
<b>To:</b> Tal Mizrahi<br>
<b>Cc:</b> ntpwg@lists.ntp.org; Harlan Stenn; tictoc@ietf.org<br>
<b>Subject:</b> Re: [TICTOC] [ntpwg] New version of draft-mizrahi-ntp-check=
sum-trailer<o:p></o:p></span></p>
</div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<div>
<div>
<p class=3D"MsoNormal">This is a somewhat unrelated question, but why not e=
liminate the servo?<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<div>
<p class=3D"MsoNormal">If a software entity is the consumer of PTP time, I =
wonder if the benefit of avoiding the y=3Dmx&#43;b computation (to compute =
PTP time from the time of the free-running LAN hardware counter) is worth t=
he trouble of disciplining the hardware
 clock.<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<div>
<p class=3D"MsoNormal">In other words, the hardware engine maintains a time=
 reference and software maintains the parameters for translating that time =
reference to PTP time (also for hardware-captured Rx and Tx timestamps). &n=
bsp;Of course, this doesn't apply to one-step
 master ports.<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<div>
<p class=3D"MsoNormal">Thoughts?<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<div>
<p class=3D"MsoNormal">Kevin Stanton.<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt"><o:p>&nbsp;</o:p></p>
<div>
<p class=3D"MsoNormal">On Mon, Oct 28, 2013 at 1:38 AM, Tal Mizrahi &lt;<a =
href=3D"mailto:talmi@marvell.com" target=3D"_blank">talmi@marvell.com</a>&g=
t; wrote:<o:p></o:p></p>
<p class=3D"MsoNormal">Hi Harlan,<o:p></o:p></p>
<div>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt"><br>
&gt;In the &quot;Figure 1&quot; case &quot;core&quot; packet timestamps com=
e from the kernel and the new packet timestamp will be added by the hardwar=
e engine.<br>
&gt;I understand the following question is outside the scope of this docume=
nt, but how can one determine how well sync'd the internal clock is with th=
e clock in the accurate timestamp engine?<o:p></o:p></p>
</div>
<p class=3D"MsoNormal">Well, indeed it is strictly an implementation questi=
on. For example, in typical PTP implementations (that I am familiar with) t=
he accurate clock is only maintained in one place, i.e., in the HW engine. =
The SW stack includes the servo algorithm;
 the SW stack regularly computes the necessary offset or frequency adjustme=
nts, and whenever necessary sends update commands to the HW engine about th=
ese adjustments. Thus, the SW stack does not need to maintain an additional=
 clock, since all its computations
 are performed WRT the HW clock.<br>
<br>
Thanks,<br>
Tal.<o:p></o:p></p>
<div>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt"><br>
<br>
-----Original Message-----<br>
From: Harlan Stenn [mailto:<a href=3D"mailto:stenn@ntp.org" target=3D"_blan=
k">stenn@ntp.org</a>]<br>
Sent: Monday, October 28, 2013 10:09 AM<br>
To: Tal Mizrahi<br>
Cc: <a href=3D"mailto:mayer@ntp.org" target=3D"_blank">mayer@ntp.org</a>; <=
a href=3D"mailto:ntpwg@lists.ntp.org" target=3D"_blank">
ntpwg@lists.ntp.org</a>; <a href=3D"mailto:tictoc@ietf.org" target=3D"_blan=
k">tictoc@ietf.org</a><br>
Subject: Re: [ntpwg] New version of draft-mizrahi-ntp-checksum-trailer<o:p>=
</o:p></p>
</div>
<div>
<div>
<p class=3D"MsoNormal">Just some thoughts, and I hope I'm awake enough to t=
ype this...<br>
<br>
There seem to be several issues here.<br>
<br>
In the &quot;Figure 1&quot; case &quot;core&quot; packet timestamps come fr=
om the kernel and the new packet timestamp will be added by the hardware en=
gine. &nbsp;I understand the following question is outside the scope of thi=
s document, but how can one determine how well sync'd the
 internal clock is with the clock in the accurate timestamp engine?<br>
<br>
If we have TX and RX hardware timestamping capabilities, we can use NTP's i=
nterleave mode to communicate these timestamps as well. &nbsp;Having said t=
hat, I'm sure there is something to be learned from implementing Tal's prop=
osal.<br>
<br>
H<br>
_______________________________________________<br>
TICTOC mailing list<br>
<a href=3D"mailto:TICTOC@ietf.org" target=3D"_blank">TICTOC@ietf.org</a><br=
>
<a href=3D"https://www.ietf.org/mailman/listinfo/tictoc" target=3D"_blank">=
https://www.ietf.org/mailman/listinfo/tictoc</a><o:p></o:p></p>
</div>
</div>
</div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
</div>
</div>
</body>
</html>

--_000_26FBD265CD8D234EAF41115A180F92BB6ED68392SJCMBX01symmetr_--

From talmi@marvell.com  Mon Oct 28 11:57:51 2013
Return-Path: <talmi@marvell.com>
X-Original-To: tictoc@ietfa.amsl.com
Delivered-To: tictoc@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 80EC611E81AD for <tictoc@ietfa.amsl.com>; Mon, 28 Oct 2013 11:57:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.249
X-Spam-Level: 
X-Spam-Status: No, score=-3.249 tagged_above=-999 required=5 tests=[AWL=-0.985, BAYES_00=-2.599, HTML_MESSAGE=0.001, IP_NOT_FRIENDLY=0.334]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Y3zR5OsYnbql for <tictoc@ietfa.amsl.com>; Mon, 28 Oct 2013 11:57:33 -0700 (PDT)
Received: from mx0a-0016f401.pphosted.com (mx0a-0016f401.pphosted.com [67.231.148.174]) by ietfa.amsl.com (Postfix) with ESMTP id EC50711E81C8 for <tictoc@ietf.org>; Mon, 28 Oct 2013 11:57:31 -0700 (PDT)
Received: from pps.filterd (m0045849.ppops.net [127.0.0.1]) by mx0a-0016f401.pphosted.com (8.14.5/8.14.5) with SMTP id r9SIvUZx002631; Mon, 28 Oct 2013 11:57:30 -0700
Received: from sc-owa01.marvell.com ([199.233.58.136]) by mx0a-0016f401.pphosted.com with ESMTP id 1fr72kvwkd-7 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Mon, 28 Oct 2013 11:57:30 -0700
Received: from YK-HUB02.marvell.com (10.4.102.52) by sc-owa01.marvell.com (10.93.76.21) with Microsoft SMTP Server (TLS) id 8.3.213.0; Mon, 28 Oct 2013 11:57:30 -0700
Received: from IL-MB01.marvell.com ([10.4.102.53]) by YK-HUB02.marvell.com ([10.4.102.52]) with mapi; Mon, 28 Oct 2013 20:57:25 +0200
From: Tal Mizrahi <talmi@marvell.com>
To: Kevin Stanton <kevin.b.stanton@gmail.com>
Date: Mon, 28 Oct 2013 20:57:20 +0200
Thread-Topic: [TICTOC] [ntpwg] New version of draft-mizrahi-ntp-checksum-trailer
Thread-Index: Ac7UBniVzuInGczdQHuhXb12t+vraAAB6piQ
Message-ID: <74470498B659FA4687F0B0018C19A89C01B87D832C14@IL-MB01.marvell.com>
References: <74470498B659FA4687F0B0018C19A89C01B87D7A40A6@IL-MB01.marvell.com> <526C30F9.1040400@ntp.org> <74470498B659FA4687F0B0018C19A89C01B87D7A4C6E@IL-MB01.marvell.com> <526D165D.3040902@ntp.org> <74470498B659FA4687F0B0018C19A89C01B87D7A4DC7@IL-MB01.marvell.com> <526D671A.7050908@ntp.org> <74470498B659FA4687F0B0018C19A89C01B87D7A4EB8@IL-MB01.marvell.com> <E1Vahsr-000Kke-9c@stenn.ntp.org> <74470498B659FA4687F0B0018C19A89C01B87D8329E8@IL-MB01.marvell.com> <CA++G9tCYC_fmMiXN-Y22EKLYU_hrXGyQGixNnyVjPx01ki1JmQ@mail.gmail.com>
In-Reply-To: <CA++G9tCYC_fmMiXN-Y22EKLYU_hrXGyQGixNnyVjPx01ki1JmQ@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: multipart/alternative; boundary="_000_74470498B659FA4687F0B0018C19A89C01B87D832C14ILMB01marve_"
MIME-Version: 1.0
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:5.10.8794, 1.0.431, 0.0.0000 definitions=2013-10-28_03:2013-10-28, 2013-10-28, 1970-01-01 signatures=0
X-Proofpoint-Spam-Details: rule=outbound_notspam policy=outbound score=0 spamscore=0 suspectscore=0 phishscore=0 adultscore=0 bulkscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=7.0.1-1305240000 definitions=main-1310280145
Cc: "ntpwg@lists.ntp.org" <ntpwg@lists.ntp.org>, Harlan Stenn <stenn@ntp.org>, "tictoc@ietf.org" <tictoc@ietf.org>
Subject: Re: [TICTOC] [ntpwg] New version of draft-mizrahi-ntp-checksum-trailer
X-BeenThere: tictoc@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Timing over IP Connection and Transfer of Clock BOF <tictoc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tictoc>, <mailto:tictoc-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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>
X-List-Received-Date: Mon, 28 Oct 2013 18:57:54 -0000

--_000_74470498B659FA4687F0B0018C19A89C01B87D832C14ILMB01marve_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Hi Kevin,

Just to make sure we are on the same page: this thread started out as a thr=
ead about NTP, and specifically about the following draft:
http://tools.ietf.org/html/draft-mizrahi-ntp-checksum-trailer-01

I think the point you suggested is basically a religious discussion of one-=
step vs. two-step clocks in PTP.
The example I referred to in the thread below is a PTP slave as an analogou=
s example to an NTP client. Since NTP is always one-step (no two-step mode =
in NTP), in our context the actual time-of-day has to be maintained in HW.

Please let me know if this makes sense.

Thanks,
Tal.

From: Kevin Stanton [mailto:kevin.b.stanton@gmail.com]
Sent: Monday, October 28, 2013 7:52 PM
To: Tal Mizrahi
Cc: Harlan Stenn; ntpwg@lists.ntp.org; tictoc@ietf.org
Subject: Re: [TICTOC] [ntpwg] New version of draft-mizrahi-ntp-checksum-tra=
iler

This is a somewhat unrelated question, but why not eliminate the servo?

If a software entity is the consumer of PTP time, I wonder if the benefit o=
f avoiding the y=3Dmx+b computation (to compute PTP time from the time of t=
he free-running LAN hardware counter) is worth the trouble of disciplining =
the hardware clock.

In other words, the hardware engine maintains a time reference and software=
 maintains the parameters for translating that time reference to PTP time (=
also for hardware-captured Rx and Tx timestamps).  Of course, this doesn't =
apply to one-step master ports.

Thoughts?

Kevin Stanton.

On Mon, Oct 28, 2013 at 1:38 AM, Tal Mizrahi <talmi@marvell.com<mailto:talm=
i@marvell.com>> wrote:
Hi Harlan,

>In the "Figure 1" case "core" packet timestamps come from the kernel and t=
he new packet timestamp will be added by the hardware engine.
>I understand the following question is outside the scope of this document,=
 but how can one determine how well sync'd the internal clock is with the c=
lock in the accurate timestamp engine?
Well, indeed it is strictly an implementation question. For example, in typ=
ical PTP implementations (that I am familiar with) the accurate clock is on=
ly maintained in one place, i.e., in the HW engine. The SW stack includes t=
he servo algorithm; the SW stack regularly computes the necessary offset or=
 frequency adjustments, and whenever necessary sends update commands to the=
 HW engine about these adjustments. Thus, the SW stack does not need to mai=
ntain an additional clock, since all its computations are performed WRT the=
 HW clock.

Thanks,
Tal.


-----Original Message-----
From: Harlan Stenn [mailto:stenn@ntp.org<mailto:stenn@ntp.org>]
Sent: Monday, October 28, 2013 10:09 AM
To: Tal Mizrahi
Cc: mayer@ntp.org<mailto:mayer@ntp.org>; ntpwg@lists.ntp.org<mailto:ntpwg@l=
ists.ntp.org>; tictoc@ietf.org<mailto:tictoc@ietf.org>
Subject: Re: [ntpwg] New version of draft-mizrahi-ntp-checksum-trailer
Just some thoughts, and I hope I'm awake enough to type this...

There seem to be several issues here.

In the "Figure 1" case "core" packet timestamps come from the kernel and th=
e new packet timestamp will be added by the hardware engine.  I understand =
the following question is outside the scope of this document, but how can o=
ne determine how well sync'd the internal clock is with the clock in the ac=
curate timestamp engine?

If we have TX and RX hardware timestamping capabilities, we can use NTP's i=
nterleave mode to communicate these timestamps as well.  Having said that, =
I'm sure there is something to be learned from implementing Tal's proposal.

H
_______________________________________________
TICTOC mailing list
TICTOC@ietf.org<mailto:TICTOC@ietf.org>
https://www.ietf.org/mailman/listinfo/tictoc


--_000_74470498B659FA4687F0B0018C19A89C01B87D832C14ILMB01marve_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40"><head><meta http-equiv=3DContent-Type content=
=3D"text/html; charset=3Dus-ascii"><meta name=3DGenerator content=3D"Micros=
oft Word 14 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
	{mso-style-priority:99;
	mso-style-link:"Balloon Text Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:8.0pt;
	font-family:"Tahoma","sans-serif";}
span.EmailStyle17
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
span.BalloonTextChar
	{mso-style-name:"Balloon Text Char";
	mso-style-priority:99;
	mso-style-link:"Balloon Text";
	font-family:"Tahoma","sans-serif";}
.MsoChpDefault
	{mso-style-type:export-only;
	font-family:"Calibri","sans-serif";}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.25in 1.0in 1.25in;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]--></head><body lang=3DEN-US link=3Dblue vli=
nk=3Dpurple><div class=3DWordSection1><p class=3DMsoNormal><span style=3D'f=
ont-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Hi Kevin,=
<o:p></o:p></span></p><p class=3DMsoNormal><span style=3D'font-size:11.0pt;=
font-family:"Calibri","sans-serif";color:#1F497D'><o:p>&nbsp;</o:p></span><=
/p><p class=3DMsoNormal><span style=3D'font-size:11.0pt;font-family:"Calibr=
i","sans-serif";color:#1F497D'>Just to make sure we are on the same page: t=
his thread started out as a thread about NTP, and specifically about the fo=
llowing draft:<o:p></o:p></span></p><p class=3DMsoNormal><span style=3D'fon=
t-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><a href=3D"=
http://tools.ietf.org/html/draft-mizrahi-ntp-checksum-trailer-01">http://to=
ols.ietf.org/html/draft-mizrahi-ntp-checksum-trailer-01</a><o:p></o:p></spa=
n></p><p class=3DMsoNormal><span style=3D'font-size:11.0pt;font-family:"Cal=
ibri","sans-serif";color:#1F497D'><o:p>&nbsp;</o:p></span></p><p class=3DMs=
oNormal><span style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";=
color:#1F497D'>I think the point you suggested is basically a religious dis=
cussion of one-step vs. two-step clocks in PTP.<o:p></o:p></span></p><p cla=
ss=3DMsoNormal><span style=3D'font-size:11.0pt;font-family:"Calibri","sans-=
serif";color:#1F497D'>The example I referred to in the thread below is a PT=
P slave as an analogous example to an NTP client. Since NTP is always one-s=
tep (no two-step mode in NTP), in our context the actual time-of-day has to=
 be maintained in HW.<o:p></o:p></span></p><p class=3DMsoNormal><span style=
=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p=
>&nbsp;</o:p></span></p><p class=3DMsoNormal><span style=3D'font-size:11.0p=
t;font-family:"Calibri","sans-serif";color:#1F497D'>Please let me know if t=
his makes sense.<o:p></o:p></span></p><p class=3DMsoNormal><span style=3D'f=
ont-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p>&nbs=
p;</o:p></span></p><p class=3DMsoNormal><span style=3D'font-size:11.0pt;fon=
t-family:"Calibri","sans-serif";color:#1F497D'>Thanks,<o:p></o:p></span></p=
><p class=3DMsoNormal><span style=3D'font-size:10.0pt;font-family:"Arial","=
sans-serif";color:#1F497D'>Tal.<o:p></o:p></span></p><p class=3DMsoNormal><=
span style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F=
497D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><b><span style=3D'fo=
nt-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span></b><span sty=
le=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'> Kevin Stanton [m=
ailto:kevin.b.stanton@gmail.com] <br><b>Sent:</b> Monday, October 28, 2013 =
7:52 PM<br><b>To:</b> Tal Mizrahi<br><b>Cc:</b> Harlan Stenn; ntpwg@lists.n=
tp.org; tictoc@ietf.org<br><b>Subject:</b> Re: [TICTOC] [ntpwg] New version=
 of draft-mizrahi-ntp-checksum-trailer<o:p></o:p></span></p><p class=3DMsoN=
ormal><o:p>&nbsp;</o:p></p><div><div><p class=3DMsoNormal>This is a somewha=
t unrelated question, but why not eliminate the servo?<o:p></o:p></p></div>=
<div><p class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><div><p class=3DMsoNor=
mal>If a software entity is the consumer of PTP time, I wonder if the benef=
it of avoiding the y=3Dmx+b computation (to compute PTP time from the time =
of the free-running LAN hardware counter) is worth the trouble of disciplin=
ing the hardware clock.<o:p></o:p></p></div><div><p class=3DMsoNormal><o:p>=
&nbsp;</o:p></p></div><div><p class=3DMsoNormal>In other words, the hardwar=
e engine maintains a time reference and software maintains the parameters f=
or translating that time reference to PTP time (also for hardware-captured =
Rx and Tx timestamps). &nbsp;Of course, this doesn't apply to one-step mast=
er ports.<o:p></o:p></p></div><div><p class=3DMsoNormal><o:p>&nbsp;</o:p></=
p></div><div><p class=3DMsoNormal>Thoughts?<o:p></o:p></p></div><div><p cla=
ss=3DMsoNormal><o:p>&nbsp;</o:p></p></div><div><p class=3DMsoNormal>Kevin S=
tanton.<o:p></o:p></p></div><div><p class=3DMsoNormal style=3D'margin-botto=
m:12.0pt'><o:p>&nbsp;</o:p></p><div><p class=3DMsoNormal>On Mon, Oct 28, 20=
13 at 1:38 AM, Tal Mizrahi &lt;<a href=3D"mailto:talmi@marvell.com" target=
=3D"_blank">talmi@marvell.com</a>&gt; wrote:<o:p></o:p></p><p class=3DMsoNo=
rmal>Hi Harlan,<o:p></o:p></p><div><p class=3DMsoNormal style=3D'margin-bot=
tom:12.0pt'><br>&gt;In the &quot;Figure 1&quot; case &quot;core&quot; packe=
t timestamps come from the kernel and the new packet timestamp will be adde=
d by the hardware engine.<br>&gt;I understand the following question is out=
side the scope of this document, but how can one determine how well sync'd =
the internal clock is with the clock in the accurate timestamp engine?<o:p>=
</o:p></p></div><p class=3DMsoNormal>Well, indeed it is strictly an impleme=
ntation question. For example, in typical PTP implementations (that I am fa=
miliar with) the accurate clock is only maintained in one place, i.e., in t=
he HW engine. The SW stack includes the servo algorithm; the SW stack regul=
arly computes the necessary offset or frequency adjustments, and whenever n=
ecessary sends update commands to the HW engine about these adjustments. Th=
us, the SW stack does not need to maintain an additional clock, since all i=
ts computations are performed WRT the HW clock.<br><br>Thanks,<br>Tal.<o:p>=
</o:p></p><div><p class=3DMsoNormal style=3D'margin-bottom:12.0pt'><br><br>=
-----Original Message-----<br>From: Harlan Stenn [mailto:<a href=3D"mailto:=
stenn@ntp.org" target=3D"_blank">stenn@ntp.org</a>]<br>Sent: Monday, Octobe=
r 28, 2013 10:09 AM<br>To: Tal Mizrahi<br>Cc: <a href=3D"mailto:mayer@ntp.o=
rg" target=3D"_blank">mayer@ntp.org</a>; <a href=3D"mailto:ntpwg@lists.ntp.=
org" target=3D"_blank">ntpwg@lists.ntp.org</a>; <a href=3D"mailto:tictoc@ie=
tf.org" target=3D"_blank">tictoc@ietf.org</a><br>Subject: Re: [ntpwg] New v=
ersion of draft-mizrahi-ntp-checksum-trailer<o:p></o:p></p></div><div><div>=
<p class=3DMsoNormal>Just some thoughts, and I hope I'm awake enough to typ=
e this...<br><br>There seem to be several issues here.<br><br>In the &quot;=
Figure 1&quot; case &quot;core&quot; packet timestamps come from the kernel=
 and the new packet timestamp will be added by the hardware engine. &nbsp;I=
 understand the following question is outside the scope of this document, b=
ut how can one determine how well sync'd the internal clock is with the clo=
ck in the accurate timestamp engine?<br><br>If we have TX and RX hardware t=
imestamping capabilities, we can use NTP's interleave mode to communicate t=
hese timestamps as well. &nbsp;Having said that, I'm sure there is somethin=
g to be learned from implementing Tal's proposal.<br><br>H<br>_____________=
__________________________________<br>TICTOC mailing list<br><a href=3D"mai=
lto:TICTOC@ietf.org" target=3D"_blank">TICTOC@ietf.org</a><br><a href=3D"ht=
tps://www.ietf.org/mailman/listinfo/tictoc" target=3D"_blank">https://www.i=
etf.org/mailman/listinfo/tictoc</a><o:p></o:p></p></div></div></div><p clas=
s=3DMsoNormal><o:p>&nbsp;</o:p></p></div></div></div></body></html>=

--_000_74470498B659FA4687F0B0018C19A89C01B87D832C14ILMB01marve_--

From mayer@ntp.org  Mon Oct 28 12:13:55 2013
Return-Path: <mayer@ntp.org>
X-Original-To: tictoc@ietfa.amsl.com
Delivered-To: tictoc@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4D90911E81B7 for <tictoc@ietfa.amsl.com>; Mon, 28 Oct 2013 12:13:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5z9r79ODLGpc for <tictoc@ietfa.amsl.com>; Mon, 28 Oct 2013 12:13:54 -0700 (PDT)
Received: from mail1.ntp.org (mail1.ntp.org [IPv6:2001:4f8:fff7:1::5]) by ietfa.amsl.com (Postfix) with ESMTP id 01A5211E80E7 for <tictoc@ietf.org>; Mon, 28 Oct 2013 12:13:50 -0700 (PDT)
Received: from [198.22.153.36] (helo=[10.2.64.81]) by mail1.ntp.org with esmtpsa (TLSv1:CAMELLIA256-SHA:256) (Exim 4.77 (FreeBSD)) (envelope-from <mayer@ntp.org>) id 1VasG3-0009mV-9E; Mon, 28 Oct 2013 19:13:48 +0000
Message-ID: <526EB751.9020308@ntp.org>
Date: Mon, 28 Oct 2013 15:13:21 -0400
From: Danny Mayer <mayer@ntp.org>
Organization: NTP
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.0.1
MIME-Version: 1.0
To: Magnus Danielson <magnus@rubidium.dyndns.org>, ntpwg@lists.ntp.org,  "tictoc@ietf.org" <tictoc@ietf.org>
References: <74470498B659FA4687F0B0018C19A89C01B87D7A40A6@IL-MB01.marvell.com>	<526C30F9.1040400@ntp.org>	<74470498B659FA4687F0B0018C19A89C01B87D7A4C6E@IL-MB01.marvell.com>	<526D165D.3040902@ntp.org>	<74470498B659FA4687F0B0018C19A89C01B87D7A4DC7@IL-MB01.marvell.com> <526D1EF0.4070208@rubidium.dyndns.org>
In-Reply-To: <526D1EF0.4070208@rubidium.dyndns.org>
X-Enigmail-Version: 1.6
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-SA-Exim-Connect-IP: 198.22.153.36
X-SA-Exim-Rcpt-To: magnus@rubidium.dyndns.org, ntpwg@lists.ntp.org, tictoc@ietf.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: Re: [TICTOC] [ntpwg] New version of draft-mizrahi-ntp-checksum-trailer
X-BeenThere: tictoc@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: mayer@ntp.org
List-Id: Timing over IP Connection and Transfer of Clock BOF <tictoc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tictoc>, <mailto:tictoc-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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>
X-List-Received-Date: Mon, 28 Oct 2013 19:13:55 -0000

On 10/27/2013 10:10 AM, Magnus Danielson wrote:
> On 10/27/2013 02:42 PM, Tal Mizrahi wrote:
>> Hi Danny,
>>
>>> That also means that the extension field MUST NOT be added by any intermediate nodes if it does not exist.
>> I am not sure we want to go there, for 2 reasons:
>>
>> 1. Let's not forget that the source and the intermediate node are in fact two modules in the same client/server (see Figure 1 in the draft). From an interoperability perspective it would be exactly the same if the source created the extension field, or the intermediate node did. Why would we mandate a specific implementation detail that would be completely transparent to the network?
>>
>> 2. A clock that receives an NTP message has no way of knowing whether an extension field was added by the source or by an intermediate node, and thus there is no way to enforce (enforce from a security perspective) the requirement you suggested.
> I think this discussion would benefit from separating "interface node"
> from "intermediate node" as these have different roles. The interface
> node would add the output time-stamp of the sending node. If
> intermediate nodes where allowed to add fields, we could have buffer
> compensation in NTP just as in PTP's transparent clock.

I'm not sure that there's a real difference here. From a topological
point of view the interface node and an intermediate node are just a
node in the network. You are just calling it a different name.

> At the same time, as long as there is no authentication on this, any
> intermediate node can create any form of modification that the receiver
> node will accept, malicious or unintentional. Hence, there is only so
> much protection you can create in the semantics.
> 

There's no protection whatsoever here.

Danny


From doug.arnold2@gmail.com  Mon Oct 28 13:05:48 2013
Return-Path: <doug.arnold2@gmail.com>
X-Original-To: tictoc@ietfa.amsl.com
Delivered-To: tictoc@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E52FE11E81D9 for <tictoc@ietfa.amsl.com>; Mon, 28 Oct 2013 13:05:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id xn9VHqO2OnJU for <tictoc@ietfa.amsl.com>; Mon, 28 Oct 2013 13:05:46 -0700 (PDT)
Received: from mail-ie0-x235.google.com (mail-ie0-x235.google.com [IPv6:2607:f8b0:4001:c03::235]) by ietfa.amsl.com (Postfix) with ESMTP id 712A521E8095 for <tictoc@ietf.org>; Mon, 28 Oct 2013 13:05:44 -0700 (PDT)
Received: by mail-ie0-f181.google.com with SMTP id ar20so11900714iec.26 for <tictoc@ietf.org>; Mon, 28 Oct 2013 13:05:44 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=B+OOKzvF+X0z+MoA1UZesrpuzd0bv14ot2hPETgYKE8=; b=KdMtTkhCtxMhtP0fzBOq9mng8bGHreSLyQwFxCoYjYtbSbK07Dq+0yBgoHeZ9+lJ7n LJFeTVWJNSEbFlfOPSAGTWEVJ81XjR1mAFSxUnneJAT/ByLc/W9z7/nf/zeLvsIqSvZ9 tGanC+EcJwC5rOSqhHGsRUyuaCXg3+BDew7eT+LhoEIcN7oUCEYmctHo9mMqWHvl15hW YP4jAOhwDdbsoDMxFIDjimtDMItRorMjkaDhAbzjNI5efVIqpbL4GPsdTRtu+380qiJE i1AEbpIZZEMq9YvqJqTkXYvJ1wyKOXnvTvaIXwUJWaKlmgrq9vkFjGF/nRRpQ+98xg3e 0B7Q==
MIME-Version: 1.0
X-Received: by 10.42.126.18 with SMTP id c18mr2422766ics.46.1382990743941; Mon, 28 Oct 2013 13:05:43 -0700 (PDT)
Received: by 10.64.59.196 with HTTP; Mon, 28 Oct 2013 13:05:43 -0700 (PDT)
In-Reply-To: <B1D49063AD5FBD4688F3EEDEC68B20175113E0AA@BGB01XUD1011.national.core.bbc.co.uk>
References: <CACQYgzFmOtFY+Td0jZMyykeZ17KwAuCc+LY+C2be_UPgZKh9GA@mail.gmail.com> <B1D49063AD5FBD4688F3EEDEC68B201751132BDF@BGB01XUD1002.national.core.bbc.co.uk> <B1D49063AD5FBD4688F3EEDEC68B20175113E0AA@BGB01XUD1011.national.core.bbc.co.uk>
Date: Mon, 28 Oct 2013 13:05:43 -0700
Message-ID: <CACQYgzEEcZPLEBgyTPUyqYbRjNi_7oFvm7TVxhGthQL-hx6nYA@mail.gmail.com>
From: Douglas Arnold <doug.arnold2@gmail.com>
To: John Fletcher <John.Fletcher@bbc.co.uk>
Content-Type: multipart/alternative; boundary=20cf3010e4df053b6704e9d2a0a7
Cc: "tictoc@ietf.org" <tictoc@ietf.org>
Subject: Re: [TICTOC] Enterprise Profile
X-BeenThere: tictoc@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Timing over IP Connection and Transfer of Clock BOF <tictoc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tictoc>, <mailto:tictoc-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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>
X-List-Received-Date: Mon, 28 Oct 2013 20:05:48 -0000

--20cf3010e4df053b6704e9d2a0a7
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: quoted-printable

Hello John,

I agree that local time is useful.  I would not be averse to creating a TLV
to distribute local time offset, so that end node can convert to local time
and present it to users.

However, I do not support the idea of using a local time epoch in the PTP
timestamp fields. This is an allowed option in IEEE 1588-2008, but I
believe that this is likely to cause interoperability problems, when some
vendors support it and others do not.  Also some system architechs have
indicated that they deploy PTP across large networks, which span time
zones. This is the feature that should be forbidden.

In the NTP standard (RFC5905) the timestamps in the packet all use a
specific time epoch, and generate all other desired time epoch as
corrections performed at the end points.  Note also that in most computer
operating systems a single standard time epoch is used in and local time is
generated at the presentation layer for human readable interfaces.

Doug


On Mon, Oct 28, 2013 at 8:10 AM, John Fletcher <John.Fletcher@bbc.co.uk>wro=
te:

>  I'd also like to ask that you don't prohibit the Alternate Timescales
> option.  This is potentially useful to distribute "local time" (your
> time-zone and dst) and there doesn't seem to be any need to prohibit it.
>
>  John
>  ------------------------------
> *From:* tictoc-bounces@ietf.org [tictoc-bounces@ietf.org] on behalf of
> John Fletcher [John.Fletcher@bbc.co.uk]
> *Sent:* 25 October 2013 11:01
> *To:* Douglas Arnold
> *Cc:* tictoc@ietf.org
> *Subject:* Re: [TICTOC] Enterprise Profile
>
>    Doug,
>
>
>
> I would be interested to know the circumstances when you see the maximum
> phase adjustment information being used.
>
>
>
> Some comments:
>
>
>
> In section 6, you say, =93In all three of the delay measurement modes=85=
=94.  At
> that point in the text you have not yet mentioned multicast, hybrid and
> unicast modes so it=92s not clear which modes you are referring to.
>
>
>
> In section 9, you say, =93Slaves SHOULD NOT Synchronize to a Rogue Master=
.=94
> It=92s not clear how a slave would know that a master is rogue; presumabl=
y it
> would need to examine the announce messages of all masters and do its own
> BMCA evaluation.  A more realistic =93rogue=94 master would probably meet=
 the
> BMCA criteria for selection.
>
>
>
> In section 12, =93Alternative Time Scales=94 should be =93Alternate Times=
cales=94.
>
>
>
>
>
> Regards,
>
> John Fletcher
>
>
>
> *From:* tictoc-bounces@ietf.org [mailto:tictoc-bounces@ietf.org] *On
> Behalf Of *Douglas Arnold
> *Sent:* 25 October 2013 01:35
> *To:* tictoc@ietf.org
> *Subject:* [TICTOC] Enterprise Profile
>
>
>
> Hello Everyone,
>
>
>
> Attached is an updated version of the Enterprise profile.  Sorry I missed
> the upload deadline for  the Vancouver meeting.  If you get a chance to
> look at it before then I will be there and would love to discuss it.
>
>
>
> Summary of changes:
>
>
>
> I also changed the TLV format to fit the latest proposal in the 1588
> revision.
>
>
>
> I added a statement about not going into the master state unless one had =
a
> current UTC offset.
>
>
>
> I added to the TLV fields to indicate maximum phase correction over a syn=
c
> cycle.
>
>
>
> --
>
> Doug Arnold
>
> Principal Technologist
>
> *JTime!* Meinberg USA
>
> +1-707-303-5559
>
>
>
>
>
>
>
> ----------------------------
>
> http://www.bbc.co.uk
> This e-mail (and any attachments) is confidential and may contain persona=
l
> views which are not the views of the BBC unless specifically stated.
> If you have received it in error, please delete it from your system.
> Do not use, copy or disclose the information in any way nor act in
> reliance on it and notify the sender immediately.
> Please note that the BBC monitors e-mails sent or received.
> Further communication will signify your consent to this.
>
> ---------------------
>
>
>
> ----------------------------
>
> http://www.bbc.co.uk
> This e-mail (and any attachments) is confidential and may contain persona=
l
> views which are not the views of the BBC unless specifically stated.
> If you have received it in error, please delete it from your system.
> Do not use, copy or disclose the information in any way nor act in
> reliance on it and notify the sender immediately.
> Please note that the BBC monitors e-mails sent or received.
> Further communication will signify your consent to this.
>
> ---------------------
>



--=20
Doug

--20cf3010e4df053b6704e9d2a0a7
Content-Type: text/html; charset=windows-1252
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Hello John,<div><br></div><div>I agree that local time is =
useful. =A0I would not be averse to creating a TLV to distribute local time=
 offset, so that end node can convert to local time and present it to users=
.</div>
<div><br></div><div>However, I do not support the idea of using a local tim=
e epoch in the PTP timestamp fields. This is an allowed option in IEEE 1588=
-2008, but I believe that this is likely to cause interoperability problems=
, when some vendors support it and others do not.=A0=A0Also some system arc=
hitechs have indicated that they deploy PTP across large networks, which sp=
an time zones.=A0This is the feature that should be forbidden. =A0</div>
<div><br></div><div>In the NTP standard (RFC5905) the timestamps in the pac=
ket all use a specific time epoch, and generate all other desired time epoc=
h as corrections performed at the end points. =A0Note also that in most com=
puter operating systems a single standard time epoch is used in and local t=
ime is generated at the presentation layer for human readable interfaces.</=
div>
<div><br></div><div>Doug</div></div><div class=3D"gmail_extra"><br><br><div=
 class=3D"gmail_quote">On Mon, Oct 28, 2013 at 8:10 AM, John Fletcher <span=
 dir=3D"ltr">&lt;<a href=3D"mailto:John.Fletcher@bbc.co.uk" target=3D"_blan=
k">John.Fletcher@bbc.co.uk</a>&gt;</span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">





<div lang=3D"EN-GB" link=3D"blue" vlink=3D"purple">
<p></p>
<div style=3D"direction:ltr;font-size:10pt;font-family:Tahoma">I&#39;d also=
 like to ask that you don&#39;t prohibit the Alternate Timescales option. =
=A0This is potentially useful to distribute &quot;local time&quot; (your ti=
me-zone and dst) and there doesn&#39;t seem
 to be any need to prohibit it.
<div><br>
</div>
<div>John<br>
<div style=3D"font-size:16px;font-family:Times New Roman">
<hr>
<div style=3D"direction:ltr"><font face=3D"Tahoma" color=3D"#000000"><b>Fro=
m:</b> <a href=3D"mailto:tictoc-bounces@ietf.org" target=3D"_blank">tictoc-=
bounces@ietf.org</a> [<a href=3D"mailto:tictoc-bounces@ietf.org" target=3D"=
_blank">tictoc-bounces@ietf.org</a>] on behalf of John Fletcher [<a href=3D=
"mailto:John.Fletcher@bbc.co.uk" target=3D"_blank">John.Fletcher@bbc.co.uk<=
/a>]<br>

<b>Sent:</b> 25 October 2013 11:01<br>
<b>To:</b> Douglas Arnold<br>
<b>Cc:</b> <a href=3D"mailto:tictoc@ietf.org" target=3D"_blank">tictoc@ietf=
.org</a><br>
<b>Subject:</b> Re: [TICTOC] Enterprise Profile<br>
</font><br>
</div><div><div class=3D"h5">
<div></div>
<div>
<p></p>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">Doug,</span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">=A0</span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">I would be interested to =
know the circumstances when you see the maximum phase adjustment informatio=
n being used.</span></p>

<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">=A0</span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">Some comments:</span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">=A0</span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">In section 6, you say, =
=93In all three of the delay measurement modes=85=94.=A0 At that point in t=
he text you have not yet mentioned multicast, hybrid and unicast
 modes so it=92s not clear which modes you are referring to.</span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">=A0</span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">In section 9, you say, =
=93Slaves SHOULD NOT Synchronize to a Rogue Master.=94=A0 It=92s not clear =
how a slave would know that a master is rogue; presumably it would
 need to examine the announce messages of all masters and do its own BMCA e=
valuation.=A0 A more realistic =93rogue=94 master would probably meet the B=
MCA criteria for selection.</span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">=A0</span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">In section 12, =93Alterna=
tive Time Scales=94 should be =93Alternate Timescales=94.</span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">=A0</span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">=A0</span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">Regards,</span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">John Fletcher</span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">=A0</span></p>
<p class=3D"MsoNormal"><b><span lang=3D"EN-US" style=3D"font-size:10.0pt;fo=
nt-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;">From:</span></b><span =
lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Tahoma&quot;,&qu=
ot;sans-serif&quot;"> <a href=3D"mailto:tictoc-bounces@ietf.org" target=3D"=
_blank">tictoc-bounces@ietf.org</a> [mailto:<a href=3D"mailto:tictoc-bounce=
s@ietf.org" target=3D"_blank">tictoc-bounces@ietf.org</a>]
<b>On Behalf Of </b>Douglas Arnold<br>
<b>Sent:</b> 25 October 2013 01:35<br>
<b>To:</b> <a href=3D"mailto:tictoc@ietf.org" target=3D"_blank">tictoc@ietf=
.org</a><br>
<b>Subject:</b> [TICTOC] Enterprise Profile</span></p>
<p class=3D"MsoNormal">=A0</p>
<div>
<p class=3D"MsoNormal">Hello Everyone,</p>
<div>
<p class=3D"MsoNormal">=A0</p>
</div>
<div>
<p class=3D"MsoNormal">Attached is an updated version of the Enterprise pro=
file. =A0Sorry I missed the upload deadline for=A0=A0the Vancouver meeting.=
 =A0If you get a chance to look at it before then I will be there and would=
 love to discuss it.=A0</p>

</div>
<div>
<p class=3D"MsoNormal">=A0</p>
</div>
<div>
<p class=3D"MsoNormal">Summary of changes:</p>
</div>
<div>
<p class=3D"MsoNormal">=A0</p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:9.5pt;font-family:&quot;Ari=
al&quot;,&quot;sans-serif&quot;">I also changed the TLV format to fit the l=
atest proposal in the 1588 revision. =A0</span></p>
</div>
<div>
<p class=3D"MsoNormal">=A0</p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:9.5pt;font-family:&quot;Ari=
al&quot;,&quot;sans-serif&quot;">I added a statement about not going into t=
he master state unless one had a current UTC offset. =A0</span></p>
</div>
<div>
<p class=3D"MsoNormal">=A0</p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:9.5pt;font-family:&quot;Ari=
al&quot;,&quot;sans-serif&quot;">I added to the TLV fields to indicate maxi=
mum phase correction over a sync cycle.</span></p>
</div>
<div>
<div>
<p class=3D"MsoNormal">=A0</p>
</div>
<p class=3D"MsoNormal">-- </p>
<div>
<p class=3D"MsoNormal">Doug Arnold</p>
<div>
<p class=3D"MsoNormal">Principal Technologist</p>
<div>
<p class=3D"MsoNormal"><i>JTime!</i>=A0Meinberg USA</p>
</div>
</div>
<div>
<p class=3D"MsoNormal"><a href=3D"tel:%2B1-707-303-5559" value=3D"+17073035=
559" target=3D"_blank">+1-707-303-5559</a></p>
</div>
<div>
<p class=3D"MsoNormal">=A0</p>
</div>
<div>
<p class=3D"MsoNormal">=A0</p>
</div>
</div>
</div>
</div>
</div>
<p></p>
<p>=A0</p>
<p>----------------------------<br>
<font size=3D"3" face=3D"Times New Roman"><font size=3D"3" face=3D"Times Ne=
w Roman"><font size=3D"3" face=3D"Times New Roman"><br>
<font size=3D"3" face=3D"Times New Roman"><a href=3D"http://www.bbc.co.uk" =
target=3D"_blank">http://www.<span>bbc</span>.<span>co</span>.<span>uk</spa=
n></a><br>
This e-mail (and any attachments) is confidential and may contain personal =
views which are not the views of the
<span>BBC</span> unless specifically stated.<br>
If you have received it in error, please delete it from your system.<br>
Do not use, copy or disclose the information in any way nor act in reliance=
 on it and notify the sender immediately.<br>
Please note that the <span>BBC</span> monitors e-mails sent or received.<br=
>
Further communication will signify your consent to this.</font></font></fon=
t></font></p>
<p>---------------------</p>
</div>
</div></div></div>
</div>
</div><div><div class=3D"h5">
<p></p>
<p>=A0</p>
<p>----------------------------<br>
<font size=3D"3" face=3D"Times New Roman"><font size=3D"3" face=3D"Times Ne=
w Roman"><font size=3D"3" face=3D"Times New Roman"><br>
<font size=3D"3" face=3D"Times New Roman"><a href=3D"http://www.bbc.co.uk" =
target=3D"_blank">http://www.<span>bbc</span>.<span>co</span>.<span>uk</spa=
n></a><br>
This e-mail (and any attachments) is confidential and may contain personal =
views which are not the views of the
<span>BBC</span> unless specifically stated.<br>
If you have received it in error, please delete it from your system.<br>
Do not use, copy or disclose the information in any way nor act in reliance=
 on it and notify the sender immediately.<br>
Please note that the <span>BBC</span> monitors e-mails sent or received.<br=
>
Further communication will signify your consent to this.</font></font></fon=
t></font></p>
<p>---------------------</p>
</div></div></div>

</blockquote></div><br><br clear=3D"all"><div><br></div>-- <br><div dir=3D"=
ltr">Doug</div>
</div>

--20cf3010e4df053b6704e9d2a0a7--

From btv1==013fb014d0b==gdowd@symmetricom.com  Mon Oct 28 13:25:56 2013
Return-Path: <btv1==013fb014d0b==gdowd@symmetricom.com>
X-Original-To: tictoc@ietfa.amsl.com
Delivered-To: tictoc@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BC61411E81C9 for <tictoc@ietfa.amsl.com>; Mon, 28 Oct 2013 13:25:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.987
X-Spam-Level: 
X-Spam-Status: No, score=-2.987 tagged_above=-999 required=5 tests=[AWL=-0.722, BAYES_00=-2.599, HTML_MESSAGE=0.001, IP_NOT_FRIENDLY=0.334]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id QCC-cREbKCk6 for <tictoc@ietfa.amsl.com>; Mon, 28 Oct 2013 13:25:51 -0700 (PDT)
Received: from mail5.symmetricom.com (mail5.symmetricom.com [69.25.98.10]) by ietfa.amsl.com (Postfix) with ESMTP id 3796621F9FB5 for <tictoc@ietf.org>; Mon, 28 Oct 2013 13:25:38 -0700 (PDT)
X-ASG-Debug-ID: 1382991934-05bdbc07004c5950001-4wH9i1
Received: from SJC-HUB-01.symmetricom.com ([192.168.10.171]) by mail5.symmetricom.com with ESMTP id lDZvFzImYoo0mRke (version=TLSv1 cipher=AES128-SHA bits=128 verify=NO); Mon, 28 Oct 2013 13:25:34 -0700 (PDT)
X-Barracuda-Envelope-From: gdowd@symmetricom.com
X-ASG-Whitelist: Client
Received: from SJC-MBX-01.symmetricom.com ([169.254.1.121]) by SJC-HUB-01.symmetricom.com ([::1]) with mapi id 14.01.0289.001; Mon, 28 Oct 2013 13:25:34 -0700
From: Greg Dowd <gdowd@symmetricom.com>
To: Tal Mizrahi <talmi@marvell.com>, Kevin Stanton <kevin.b.stanton@gmail.com>
Thread-Topic: [ntpwg] [TICTOC] New version of draft-mizrahi-ntp-checksum-trailer
X-ASG-Orig-Subj: RE: [ntpwg] [TICTOC] New version of draft-mizrahi-ntp-checksum-trailer
Thread-Index: AQHO1A+WN7xN4b2hsEWNxkF9hy9LW5oKjoCQ
Date: Mon, 28 Oct 2013 20:25:32 +0000
Message-ID: <26FBD265CD8D234EAF41115A180F92BB6ED6853E@SJC-MBX-01.symmetricom.com>
References: <74470498B659FA4687F0B0018C19A89C01B87D7A40A6@IL-MB01.marvell.com> <526C30F9.1040400@ntp.org> <74470498B659FA4687F0B0018C19A89C01B87D7A4C6E@IL-MB01.marvell.com> <526D165D.3040902@ntp.org> <74470498B659FA4687F0B0018C19A89C01B87D7A4DC7@IL-MB01.marvell.com> <526D671A.7050908@ntp.org> <74470498B659FA4687F0B0018C19A89C01B87D7A4EB8@IL-MB01.marvell.com> <E1Vahsr-000Kke-9c@stenn.ntp.org> <74470498B659FA4687F0B0018C19A89C01B87D8329E8@IL-MB01.marvell.com> <CA++G9tCYC_fmMiXN-Y22EKLYU_hrXGyQGixNnyVjPx01ki1JmQ@mail.gmail.com> <74470498B659FA4687F0B0018C19A89C01B87D832C14@IL-MB01.marvell.com>
In-Reply-To: <74470498B659FA4687F0B0018C19A89C01B87D832C14@IL-MB01.marvell.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [192.168.3.29]
Content-Type: multipart/alternative; boundary="_000_26FBD265CD8D234EAF41115A180F92BB6ED6853ESJCMBX01symmetr_"
MIME-Version: 1.0
X-Barracuda-Connect: UNKNOWN[192.168.10.171]
X-Barracuda-Start-Time: 1382991934
X-Barracuda-Encrypted: AES128-SHA
X-Barracuda-URL: http://192.168.10.96:80/cgi-mod/mark.cgi
X-Barracuda-BRTS-Status: 1
X-Virus-Scanned: by bsmtpd at symmetricom.com
Cc: "ntpwg@lists.ntp.org" <ntpwg@lists.ntp.org>, "tictoc@ietf.org" <tictoc@ietf.org>
Subject: Re: [TICTOC] [ntpwg] New version of draft-mizrahi-ntp-checksum-trailer
X-BeenThere: tictoc@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Timing over IP Connection and Transfer of Clock BOF <tictoc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tictoc>, <mailto:tictoc-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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>
X-List-Received-Date: Mon, 28 Oct 2013 20:25:56 -0000

--_000_26FBD265CD8D234EAF41115A180F92BB6ED6853ESJCMBX01symmetr_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Actually, that's not completely correct.  While the NTP standard doesn't ha=
ve any definition of two-step, the reference implementation ntpd includes s=
upport for two-step operation in some modes.  It is called interleaved mode=
.  It still doesn't change any of your points but it is there.

From: ntpwg-bounces+gdowd=3Dsymmetricom.com@lists.ntp.org [mailto:ntpwg-bou=
nces+gdowd=3Dsymmetricom.com@lists.ntp.org] On Behalf Of Tal Mizrahi
Sent: Monday, October 28, 2013 11:57 AM
To: Kevin Stanton
Cc: ntpwg@lists.ntp.org; tictoc@ietf.org
Subject: Re: [ntpwg] [TICTOC] New version of draft-mizrahi-ntp-checksum-tra=
iler

Hi Kevin,

Just to make sure we are on the same page: this thread started out as a thr=
ead about NTP, and specifically about the following draft:
http://tools.ietf.org/html/draft-mizrahi-ntp-checksum-trailer-01

I think the point you suggested is basically a religious discussion of one-=
step vs. two-step clocks in PTP.
The example I referred to in the thread below is a PTP slave as an analogou=
s example to an NTP client. Since NTP is always one-step (no two-step mode =
in NTP), in our context the actual time-of-day has to be maintained in HW.

Please let me know if this makes sense.

Thanks,
Tal.

From: Kevin Stanton [mailto:kevin.b.stanton@gmail.com]
Sent: Monday, October 28, 2013 7:52 PM
To: Tal Mizrahi
Cc: Harlan Stenn; ntpwg@lists.ntp.org; tictoc@ietf.org
Subject: Re: [TICTOC] [ntpwg] New version of draft-mizrahi-ntp-checksum-tra=
iler

This is a somewhat unrelated question, but why not eliminate the servo?

If a software entity is the consumer of PTP time, I wonder if the benefit o=
f avoiding the y=3Dmx+b computation (to compute PTP time from the time of t=
he free-running LAN hardware counter) is worth the trouble of disciplining =
the hardware clock.

In other words, the hardware engine maintains a time reference and software=
 maintains the parameters for translating that time reference to PTP time (=
also for hardware-captured Rx and Tx timestamps).  Of course, this doesn't =
apply to one-step master ports.

Thoughts?

Kevin Stanton.

On Mon, Oct 28, 2013 at 1:38 AM, Tal Mizrahi <talmi@marvell.com<mailto:talm=
i@marvell.com>> wrote:
Hi Harlan,

>In the "Figure 1" case "core" packet timestamps come from the kernel and t=
he new packet timestamp will be added by the hardware engine.
>I understand the following question is outside the scope of this document,=
 but how can one determine how well sync'd the internal clock is with the c=
lock in the accurate timestamp engine?
Well, indeed it is strictly an implementation question. For example, in typ=
ical PTP implementations (that I am familiar with) the accurate clock is on=
ly maintained in one place, i.e., in the HW engine. The SW stack includes t=
he servo algorithm; the SW stack regularly computes the necessary offset or=
 frequency adjustments, and whenever necessary sends update commands to the=
 HW engine about these adjustments. Thus, the SW stack does not need to mai=
ntain an additional clock, since all its computations are performed WRT the=
 HW clock.

Thanks,
Tal.


-----Original Message-----
From: Harlan Stenn [mailto:stenn@ntp.org<mailto:stenn@ntp.org>]
Sent: Monday, October 28, 2013 10:09 AM
To: Tal Mizrahi
Cc: mayer@ntp.org<mailto:mayer@ntp.org>; ntpwg@lists.ntp.org<mailto:ntpwg@l=
ists.ntp.org>; tictoc@ietf.org<mailto:tictoc@ietf.org>
Subject: Re: [ntpwg] New version of draft-mizrahi-ntp-checksum-trailer
Just some thoughts, and I hope I'm awake enough to type this...

There seem to be several issues here.

In the "Figure 1" case "core" packet timestamps come from the kernel and th=
e new packet timestamp will be added by the hardware engine.  I understand =
the following question is outside the scope of this document, but how can o=
ne determine how well sync'd the internal clock is with the clock in the ac=
curate timestamp engine?

If we have TX and RX hardware timestamping capabilities, we can use NTP's i=
nterleave mode to communicate these timestamps as well.  Having said that, =
I'm sure there is something to be learned from implementing Tal's proposal.

H
_______________________________________________
TICTOC mailing list
TICTOC@ietf.org<mailto:TICTOC@ietf.org>
https://www.ietf.org/mailman/listinfo/tictoc


--_000_26FBD265CD8D234EAF41115A180F92BB6ED6853ESJCMBX01symmetr_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:x=3D"urn:schemas-microsoft-com:office:excel" xmlns:p=3D"urn:schemas-m=
icrosoft-com:office:powerpoint" xmlns:a=3D"urn:schemas-microsoft-com:office=
:access" xmlns:dt=3D"uuid:C2F41010-65B3-11d1-A29F-00AA00C14882" xmlns:s=3D"=
uuid:BDC6E3F0-6DA3-11d1-A2A3-00AA00C14882" xmlns:rs=3D"urn:schemas-microsof=
t-com:rowset" xmlns:z=3D"#RowsetSchema" xmlns:b=3D"urn:schemas-microsoft-co=
m:office:publisher" xmlns:ss=3D"urn:schemas-microsoft-com:office:spreadshee=
t" xmlns:c=3D"urn:schemas-microsoft-com:office:component:spreadsheet" xmlns=
:odc=3D"urn:schemas-microsoft-com:office:odc" xmlns:oa=3D"urn:schemas-micro=
soft-com:office:activation" xmlns:html=3D"http://www.w3.org/TR/REC-html40" =
xmlns:q=3D"http://schemas.xmlsoap.org/soap/envelope/" xmlns:rtc=3D"http://m=
icrosoft.com/officenet/conferencing" xmlns:D=3D"DAV:" xmlns:Repl=3D"http://=
schemas.microsoft.com/repl/" xmlns:mt=3D"http://schemas.microsoft.com/share=
point/soap/meetings/" xmlns:x2=3D"http://schemas.microsoft.com/office/excel=
/2003/xml" xmlns:ppda=3D"http://www.passport.com/NameSpace.xsd" xmlns:ois=
=3D"http://schemas.microsoft.com/sharepoint/soap/ois/" xmlns:dir=3D"http://=
schemas.microsoft.com/sharepoint/soap/directory/" xmlns:ds=3D"http://www.w3=
.org/2000/09/xmldsig#" xmlns:dsp=3D"http://schemas.microsoft.com/sharepoint=
/dsp" xmlns:udc=3D"http://schemas.microsoft.com/data/udc" xmlns:xsd=3D"http=
://www.w3.org/2001/XMLSchema" xmlns:sub=3D"http://schemas.microsoft.com/sha=
repoint/soap/2002/1/alerts/" xmlns:ec=3D"http://www.w3.org/2001/04/xmlenc#"=
 xmlns:sp=3D"http://schemas.microsoft.com/sharepoint/" xmlns:sps=3D"http://=
schemas.microsoft.com/sharepoint/soap/" xmlns:xsi=3D"http://www.w3.org/2001=
/XMLSchema-instance" xmlns:udcs=3D"http://schemas.microsoft.com/data/udc/so=
ap" xmlns:udcxf=3D"http://schemas.microsoft.com/data/udc/xmlfile" xmlns:udc=
p2p=3D"http://schemas.microsoft.com/data/udc/parttopart" xmlns:wf=3D"http:/=
/schemas.microsoft.com/sharepoint/soap/workflow/" xmlns:dsss=3D"http://sche=
mas.microsoft.com/office/2006/digsig-setup" xmlns:dssi=3D"http://schemas.mi=
crosoft.com/office/2006/digsig" xmlns:mdssi=3D"http://schemas.openxmlformat=
s.org/package/2006/digital-signature" xmlns:mver=3D"http://schemas.openxmlf=
ormats.org/markup-compatibility/2006" xmlns:m=3D"http://schemas.microsoft.c=
om/office/2004/12/omml" xmlns:mrels=3D"http://schemas.openxmlformats.org/pa=
ckage/2006/relationships" xmlns:spwp=3D"http://microsoft.com/sharepoint/web=
partpages" xmlns:ex12t=3D"http://schemas.microsoft.com/exchange/services/20=
06/types" xmlns:ex12m=3D"http://schemas.microsoft.com/exchange/services/200=
6/messages" xmlns:pptsl=3D"http://schemas.microsoft.com/sharepoint/soap/Sli=
deLibrary/" xmlns:spsl=3D"http://microsoft.com/webservices/SharePointPortal=
Server/PublishedLinksService" xmlns:Z=3D"urn:schemas-microsoft-com:" xmlns:=
st=3D"&#1;" xmlns=3D"http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
<meta name=3D"Generator" content=3D"Microsoft Word 12 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
	{mso-style-priority:99;
	mso-style-link:"Balloon Text Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:8.0pt;
	font-family:"Tahoma","sans-serif";}
span.BalloonTextChar
	{mso-style-name:"Balloon Text Char";
	mso-style-priority:99;
	mso-style-link:"Balloon Text";
	font-family:"Tahoma","sans-serif";}
span.EmailStyle19
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
span.EmailStyle20
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.25in 1.0in 1.25in;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=3D"EN-US" link=3D"blue" vlink=3D"purple">
<div class=3D"WordSection1">
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">Actually, that&#8217;s no=
t completely correct.&nbsp; While the NTP standard doesn&#8217;t have any d=
efinition of two-step, the reference implementation ntpd includes support
 for two-step operation in some modes.&nbsp; It is called interleaved mode.=
&nbsp; It still doesn&#8217;t change any of your points but it is there.<o:=
p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<div>
<div style=3D"border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in =
0in 0in">
<p class=3D"MsoNormal"><b><span style=3D"font-size:10.0pt;font-family:&quot=
;Tahoma&quot;,&quot;sans-serif&quot;">From:</span></b><span style=3D"font-s=
ize:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;"> ntpwg-bo=
unces&#43;gdowd=3Dsymmetricom.com@lists.ntp.org [mailto:ntpwg-bounces&#43;g=
dowd=3Dsymmetricom.com@lists.ntp.org]
<b>On Behalf Of </b>Tal Mizrahi<br>
<b>Sent:</b> Monday, October 28, 2013 11:57 AM<br>
<b>To:</b> Kevin Stanton<br>
<b>Cc:</b> ntpwg@lists.ntp.org; tictoc@ietf.org<br>
<b>Subject:</b> Re: [ntpwg] [TICTOC] New version of draft-mizrahi-ntp-check=
sum-trailer<o:p></o:p></span></p>
</div>
</div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">Hi Kevin,<o:p></o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">Just to make sure we are =
on the same page: this thread started out as a thread about NTP, and specif=
ically about the following draft:<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><a href=3D"http://tools.i=
etf.org/html/draft-mizrahi-ntp-checksum-trailer-01">http://tools.ietf.org/h=
tml/draft-mizrahi-ntp-checksum-trailer-01</a><o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">I think the point you sug=
gested is basically a religious discussion of one-step vs. two-step clocks =
in PTP.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">The example I referred to=
 in the thread below is a PTP slave as an analogous example to an NTP clien=
t. Since NTP is always one-step (no two-step mode in NTP),
 in our context the actual time-of-day has to be maintained in HW.<o:p></o:=
p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">Please let me know if thi=
s makes sense.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">Thanks,<o:p></o:p></span>=
</p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Ar=
ial&quot;,&quot;sans-serif&quot;;color:#1F497D">Tal.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<p class=3D"MsoNormal"><b><span style=3D"font-size:10.0pt;font-family:&quot=
;Tahoma&quot;,&quot;sans-serif&quot;">From:</span></b><span style=3D"font-s=
ize:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;"> Kevin St=
anton [mailto:kevin.b.stanton@gmail.com]
<br>
<b>Sent:</b> Monday, October 28, 2013 7:52 PM<br>
<b>To:</b> Tal Mizrahi<br>
<b>Cc:</b> Harlan Stenn; ntpwg@lists.ntp.org; tictoc@ietf.org<br>
<b>Subject:</b> Re: [TICTOC] [ntpwg] New version of draft-mizrahi-ntp-check=
sum-trailer<o:p></o:p></span></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<div>
<div>
<p class=3D"MsoNormal">This is a somewhat unrelated question, but why not e=
liminate the servo?<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<div>
<p class=3D"MsoNormal">If a software entity is the consumer of PTP time, I =
wonder if the benefit of avoiding the y=3Dmx&#43;b computation (to compute =
PTP time from the time of the free-running LAN hardware counter) is worth t=
he trouble of disciplining the hardware
 clock.<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<div>
<p class=3D"MsoNormal">In other words, the hardware engine maintains a time=
 reference and software maintains the parameters for translating that time =
reference to PTP time (also for hardware-captured Rx and Tx timestamps). &n=
bsp;Of course, this doesn't apply to one-step
 master ports.<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<div>
<p class=3D"MsoNormal">Thoughts?<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<div>
<p class=3D"MsoNormal">Kevin Stanton.<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt"><o:p>&nbsp;</o:p></p>
<div>
<p class=3D"MsoNormal">On Mon, Oct 28, 2013 at 1:38 AM, Tal Mizrahi &lt;<a =
href=3D"mailto:talmi@marvell.com" target=3D"_blank">talmi@marvell.com</a>&g=
t; wrote:<o:p></o:p></p>
<p class=3D"MsoNormal">Hi Harlan,<o:p></o:p></p>
<div>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt"><br>
&gt;In the &quot;Figure 1&quot; case &quot;core&quot; packet timestamps com=
e from the kernel and the new packet timestamp will be added by the hardwar=
e engine.<br>
&gt;I understand the following question is outside the scope of this docume=
nt, but how can one determine how well sync'd the internal clock is with th=
e clock in the accurate timestamp engine?<o:p></o:p></p>
</div>
<p class=3D"MsoNormal">Well, indeed it is strictly an implementation questi=
on. For example, in typical PTP implementations (that I am familiar with) t=
he accurate clock is only maintained in one place, i.e., in the HW engine. =
The SW stack includes the servo algorithm;
 the SW stack regularly computes the necessary offset or frequency adjustme=
nts, and whenever necessary sends update commands to the HW engine about th=
ese adjustments. Thus, the SW stack does not need to maintain an additional=
 clock, since all its computations
 are performed WRT the HW clock.<br>
<br>
Thanks,<br>
Tal.<o:p></o:p></p>
<div>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt"><br>
<br>
-----Original Message-----<br>
From: Harlan Stenn [mailto:<a href=3D"mailto:stenn@ntp.org" target=3D"_blan=
k">stenn@ntp.org</a>]<br>
Sent: Monday, October 28, 2013 10:09 AM<br>
To: Tal Mizrahi<br>
Cc: <a href=3D"mailto:mayer@ntp.org" target=3D"_blank">mayer@ntp.org</a>; <=
a href=3D"mailto:ntpwg@lists.ntp.org" target=3D"_blank">
ntpwg@lists.ntp.org</a>; <a href=3D"mailto:tictoc@ietf.org" target=3D"_blan=
k">tictoc@ietf.org</a><br>
Subject: Re: [ntpwg] New version of draft-mizrahi-ntp-checksum-trailer<o:p>=
</o:p></p>
</div>
<div>
<div>
<p class=3D"MsoNormal">Just some thoughts, and I hope I'm awake enough to t=
ype this...<br>
<br>
There seem to be several issues here.<br>
<br>
In the &quot;Figure 1&quot; case &quot;core&quot; packet timestamps come fr=
om the kernel and the new packet timestamp will be added by the hardware en=
gine. &nbsp;I understand the following question is outside the scope of thi=
s document, but how can one determine how well sync'd the
 internal clock is with the clock in the accurate timestamp engine?<br>
<br>
If we have TX and RX hardware timestamping capabilities, we can use NTP's i=
nterleave mode to communicate these timestamps as well. &nbsp;Having said t=
hat, I'm sure there is something to be learned from implementing Tal's prop=
osal.<br>
<br>
H<br>
_______________________________________________<br>
TICTOC mailing list<br>
<a href=3D"mailto:TICTOC@ietf.org" target=3D"_blank">TICTOC@ietf.org</a><br=
>
<a href=3D"https://www.ietf.org/mailman/listinfo/tictoc" target=3D"_blank">=
https://www.ietf.org/mailman/listinfo/tictoc</a><o:p></o:p></p>
</div>
</div>
</div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
</div>
</div>
</body>
</html>

--_000_26FBD265CD8D234EAF41115A180F92BB6ED6853ESJCMBX01symmetr_--

From kevin.gross@avanw.com  Mon Oct 28 18:42:30 2013
Return-Path: <kevin.gross@avanw.com>
X-Original-To: tictoc@ietfa.amsl.com
Delivered-To: tictoc@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E16AD11E81CA for <tictoc@ietfa.amsl.com>; Mon, 28 Oct 2013 18:42:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.186
X-Spam-Level: 
X-Spam-Status: No, score=0.186 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FH_RELAY_NODNS=1.451, FM_FORGED_GMAIL=0.622, HELO_MISMATCH_NET=0.611, HTML_MESSAGE=0.001, RDNS_NONE=0.1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id iN1qgmPIt+l2 for <tictoc@ietfa.amsl.com>; Mon, 28 Oct 2013 18:42:18 -0700 (PDT)
Received: from qmta15.emeryville.ca.mail.comcast.net (qmta15.emeryville.ca.mail.comcast.net [IPv6:2001:558:fe2d:44:76:96:27:228]) by ietfa.amsl.com (Postfix) with ESMTP id A697511E81CB for <tictoc@ietf.org>; Mon, 28 Oct 2013 18:40:57 -0700 (PDT)
Received: from omta06.emeryville.ca.mail.comcast.net ([76.96.30.51]) by qmta15.emeryville.ca.mail.comcast.net with comcast id ipHm1m00616AWCUAFpgrBn; Tue, 29 Oct 2013 01:40:51 +0000
Received: from mail-wg0-f54.google.com ([74.125.82.54]) by omta06.emeryville.ca.mail.comcast.net with comcast id ipeu1m00C1AKKuq8Spevzr; Tue, 29 Oct 2013 01:38:56 +0000
Received: by mail-wg0-f54.google.com with SMTP id c11so7685852wgh.9 for <tictoc@ietf.org>; Mon, 28 Oct 2013 18:38:53 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=e38Px8Q1UVDwwzHdqPvYlON7U6ofV1NPIk5VCRGqjfQ=; b=GJsgEGog5nqo9gWeg1vjzd1gVYzTni9hSAtQr1tXoN9zaWa2sfRAn7alWckYYtBsC4 id8s6Z91So9CQ7aZ8LCFCIU7fgKDo5CM++AwJ/RQFCr6iTcp47cJ0rd0eDkMpbmiart0 ivwSX6+YTdhA+pyaiDXMi8R6sZJ4/y6IH07cVZ0nv/AIsdjDhPAYMHXa+mgjxRvfsIsx 5bLb95mqpYT4eVn0m0t39FAF49kvTmvhUB1fv9n0cEw7cCal6IveaRJd1z03SGOXWBGh fAnAoqSVZ+bMjlgXNCjYLsqr2LhKq+jP4H1de9GhelrtG9Ybg2gII7irHa0p+1JkMerN G1kg==
MIME-Version: 1.0
X-Received: by 10.180.212.51 with SMTP id nh19mr9226114wic.52.1383010733517; Mon, 28 Oct 2013 18:38:53 -0700 (PDT)
Received: by 10.216.202.7 with HTTP; Mon, 28 Oct 2013 18:38:53 -0700 (PDT)
In-Reply-To: <CACQYgzEEcZPLEBgyTPUyqYbRjNi_7oFvm7TVxhGthQL-hx6nYA@mail.gmail.com>
References: <CACQYgzFmOtFY+Td0jZMyykeZ17KwAuCc+LY+C2be_UPgZKh9GA@mail.gmail.com> <B1D49063AD5FBD4688F3EEDEC68B201751132BDF@BGB01XUD1002.national.core.bbc.co.uk> <B1D49063AD5FBD4688F3EEDEC68B20175113E0AA@BGB01XUD1011.national.core.bbc.co.uk> <CACQYgzEEcZPLEBgyTPUyqYbRjNi_7oFvm7TVxhGthQL-hx6nYA@mail.gmail.com>
Date: Mon, 28 Oct 2013 19:38:53 -0600
Message-ID: <CALw1_Q2bbbt+tCoW8nFnrLz5YFtq2zCq8oB3oqki=_d7YiZS3g@mail.gmail.com>
From: Kevin Gross <kevin.gross@avanw.com>
To: Douglas Arnold <doug.arnold2@gmail.com>
Content-Type: multipart/alternative; boundary=001a11c357607df4b504e9d747ce
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20121106; t=1383010851; bh=e38Px8Q1UVDwwzHdqPvYlON7U6ofV1NPIk5VCRGqjfQ=; h=Received:Received:Received:MIME-Version:Received:Date:Message-ID: Subject:From:To:Content-Type; b=Egwzxjf9tcWjNmtfHXnnEIoGny+QaoKS0GmCCJ5BtRUgZg9LBWPKmo18VExWa5njU MzPkQcNZuL1m+sUxo0aC3m/MouYy8d9zPpkfeD+j6DxNHE7Q1Nj3ilO7CBfN/3+Gbm cSwHXTHVidwpSyRr3puEYy9JZEhQOqAljYK/LM13D8nkw4sHj8T1tNeBdxmHK8qeku I5naYazwJJf9xT9LirO6teulx1go7kzjcopcvOiK6uIgToiNF0PRjGALIFrNaA0ct3 EPk3xh5IavT7xitVT/JrHoQRnnnE/5WKL4Qx8uODYS9f6d4wkH0K5f9vbDsBlN4GDF 8Q2N6aJaqXUUg==
Cc: "tictoc@ietf.org" <tictoc@ietf.org>
Subject: Re: [TICTOC] Enterprise Profile
X-BeenThere: tictoc@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Timing over IP Connection and Transfer of Clock BOF <tictoc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tictoc>, <mailto:tictoc-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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>
X-List-Received-Date: Tue, 29 Oct 2013 01:42:35 -0000

--001a11c357607df4b504e9d747ce
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: quoted-printable

Enterprise networks definitely span timezones - if not now then eventually
through mergers and acquisition. I think having the wrong local time is
worse than having no local time. I support disabling the capability for
this profile.

Kevin Gross
+1-303-447-0517
Media Network Consultant
AVA Networks - www.AVAnw.com <http://www.avanw.com/>


On Mon, Oct 28, 2013 at 2:05 PM, Douglas Arnold <doug.arnold2@gmail.com>wro=
te:

> Hello John,
>
> I agree that local time is useful.  I would not be averse to creating a
> TLV to distribute local time offset, so that end node can convert to loca=
l
> time and present it to users.
>
> However, I do not support the idea of using a local time epoch in the PTP
> timestamp fields. This is an allowed option in IEEE 1588-2008, but I
> believe that this is likely to cause interoperability problems, when some
> vendors support it and others do not.  Also some system architechs have
> indicated that they deploy PTP across large networks, which span time
> zones. This is the feature that should be forbidden.
>
> In the NTP standard (RFC5905) the timestamps in the packet all use a
> specific time epoch, and generate all other desired time epoch as
> corrections performed at the end points.  Note also that in most computer
> operating systems a single standard time epoch is used in and local time =
is
> generated at the presentation layer for human readable interfaces.
>
> Doug
>
>
> On Mon, Oct 28, 2013 at 8:10 AM, John Fletcher <John.Fletcher@bbc.co.uk>w=
rote:
>
>>  I'd also like to ask that you don't prohibit the Alternate Timescales
>> option.  This is potentially useful to distribute "local time" (your
>> time-zone and dst) and there doesn't seem to be any need to prohibit it.
>>
>>  John
>>  ------------------------------
>> *From:* tictoc-bounces@ietf.org [tictoc-bounces@ietf.org] on behalf of
>> John Fletcher [John.Fletcher@bbc.co.uk]
>> *Sent:* 25 October 2013 11:01
>> *To:* Douglas Arnold
>> *Cc:* tictoc@ietf.org
>> *Subject:* Re: [TICTOC] Enterprise Profile
>>
>>    Doug,
>>
>>
>>
>> I would be interested to know the circumstances when you see the maximum
>> phase adjustment information being used.
>>
>>
>>
>> Some comments:
>>
>>
>>
>> In section 6, you say, =93In all three of the delay measurement modes=85=
=94.
>> At that point in the text you have not yet mentioned multicast, hybrid a=
nd
>> unicast modes so it=92s not clear which modes you are referring to.
>>
>>
>>
>> In section 9, you say, =93Slaves SHOULD NOT Synchronize to a Rogue
>> Master.=94  It=92s not clear how a slave would know that a master is rog=
ue;
>> presumably it would need to examine the announce messages of all masters
>> and do its own BMCA evaluation.  A more realistic =93rogue=94 master wou=
ld
>> probably meet the BMCA criteria for selection.
>>
>>
>>
>> In section 12, =93Alternative Time Scales=94 should be =93Alternate Time=
scales=94.
>>
>>
>>
>>
>>
>> Regards,
>>
>> John Fletcher
>>
>>
>>
>> *From:* tictoc-bounces@ietf.org [mailto:tictoc-bounces@ietf.org] *On
>> Behalf Of *Douglas Arnold
>> *Sent:* 25 October 2013 01:35
>> *To:* tictoc@ietf.org
>> *Subject:* [TICTOC] Enterprise Profile
>>
>>
>>
>> Hello Everyone,
>>
>>
>>
>> Attached is an updated version of the Enterprise profile.  Sorry I misse=
d
>> the upload deadline for  the Vancouver meeting.  If you get a chance to
>> look at it before then I will be there and would love to discuss it.
>>
>>
>>
>> Summary of changes:
>>
>>
>>
>> I also changed the TLV format to fit the latest proposal in the 1588
>> revision.
>>
>>
>>
>> I added a statement about not going into the master state unless one had
>> a current UTC offset.
>>
>>
>>
>> I added to the TLV fields to indicate maximum phase correction over a
>> sync cycle.
>>
>>
>>
>> --
>>
>> Doug Arnold
>>
>> Principal Technologist
>>
>> *JTime!* Meinberg USA
>>
>> +1-707-303-5559
>>
>>
>>
>>
>>
>>
>>
>> ----------------------------
>>
>> http://www.bbc.co.uk
>> This e-mail (and any attachments) is confidential and may contain
>> personal views which are not the views of the BBC unless specifically
>> stated.
>> If you have received it in error, please delete it from your system.
>> Do not use, copy or disclose the information in any way nor act in
>> reliance on it and notify the sender immediately.
>> Please note that the BBC monitors e-mails sent or received.
>> Further communication will signify your consent to this.
>>
>> ---------------------
>>
>>
>>
>> ----------------------------
>>
>> http://www.bbc.co.uk
>> This e-mail (and any attachments) is confidential and may contain
>> personal views which are not the views of the BBC unless specifically
>> stated.
>> If you have received it in error, please delete it from your system.
>> Do not use, copy or disclose the information in any way nor act in
>> reliance on it and notify the sender immediately.
>> Please note that the BBC monitors e-mails sent or received.
>> Further communication will signify your consent to this.
>>
>> ---------------------
>>
>
>
>
> --
> Doug
>
> _______________________________________________
> TICTOC mailing list
> TICTOC@ietf.org
> https://www.ietf.org/mailman/listinfo/tictoc
>
>

--001a11c357607df4b504e9d747ce
Content-Type: text/html; charset=windows-1252
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Enterprise networks definitely span timezones - if not now=
 then eventually through mergers and acquisition. I think having the wrong =
local time is worse than having no local time. I support disabling the capa=
bility for this profile.</div>
<div class=3D"gmail_extra"><br clear=3D"all"><div><div dir=3D"ltr">Kevin Gr=
oss<br><div>+1-303-447-0517</div><div>Media Network Consultant<br><div>AVA =
Networks -=A0<a href=3D"http://www.avanw.com/" target=3D"_blank">www.AVAnw.=
com</a></div>
</div></div></div>
<br><br><div class=3D"gmail_quote">On Mon, Oct 28, 2013 at 2:05 PM, Douglas=
 Arnold <span dir=3D"ltr">&lt;<a href=3D"mailto:doug.arnold2@gmail.com" tar=
get=3D"_blank">doug.arnold2@gmail.com</a>&gt;</span> wrote:<br><blockquote =
class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid=
;padding-left:1ex">
<div dir=3D"ltr">Hello John,<div><br></div><div>I agree that local time is =
useful. =A0I would not be averse to creating a TLV to distribute local time=
 offset, so that end node can convert to local time and present it to users=
.</div>

<div><br></div><div>However, I do not support the idea of using a local tim=
e epoch in the PTP timestamp fields. This is an allowed option in IEEE 1588=
-2008, but I believe that this is likely to cause interoperability problems=
, when some vendors support it and others do not.=A0=A0Also some system arc=
hitechs have indicated that they deploy PTP across large networks, which sp=
an time zones.=A0This is the feature that should be forbidden. =A0</div>

<div><br></div><div>In the NTP standard (RFC5905) the timestamps in the pac=
ket all use a specific time epoch, and generate all other desired time epoc=
h as corrections performed at the end points. =A0Note also that in most com=
puter operating systems a single standard time epoch is used in and local t=
ime is generated at the presentation layer for human readable interfaces.</=
div>

<div><br></div><div>Doug</div></div><div class=3D"gmail_extra"><div><div cl=
ass=3D"h5"><br><br><div class=3D"gmail_quote">On Mon, Oct 28, 2013 at 8:10 =
AM, John Fletcher <span dir=3D"ltr">&lt;<a href=3D"mailto:John.Fletcher@bbc=
.co.uk" target=3D"_blank">John.Fletcher@bbc.co.uk</a>&gt;</span> wrote:<br>

<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">





<div lang=3D"EN-GB" link=3D"blue" vlink=3D"purple">
<p></p>
<div style=3D"direction:ltr;font-size:10pt;font-family:Tahoma">I&#39;d also=
 like to ask that you don&#39;t prohibit the Alternate Timescales option. =
=A0This is potentially useful to distribute &quot;local time&quot; (your ti=
me-zone and dst) and there doesn&#39;t seem
 to be any need to prohibit it.
<div><br>
</div>
<div>John<br>
<div style=3D"font-size:16px;font-family:Times New Roman">
<hr>
<div style=3D"direction:ltr"><font face=3D"Tahoma" color=3D"#000000"><b>Fro=
m:</b> <a href=3D"mailto:tictoc-bounces@ietf.org" target=3D"_blank">tictoc-=
bounces@ietf.org</a> [<a href=3D"mailto:tictoc-bounces@ietf.org" target=3D"=
_blank">tictoc-bounces@ietf.org</a>] on behalf of John Fletcher [<a href=3D=
"mailto:John.Fletcher@bbc.co.uk" target=3D"_blank">John.Fletcher@bbc.co.uk<=
/a>]<br>


<b>Sent:</b> 25 October 2013 11:01<br>
<b>To:</b> Douglas Arnold<br>
<b>Cc:</b> <a href=3D"mailto:tictoc@ietf.org" target=3D"_blank">tictoc@ietf=
.org</a><br>
<b>Subject:</b> Re: [TICTOC] Enterprise Profile<br>
</font><br>
</div><div><div>
<div></div>
<div>
<p></p>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">Doug,</span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">=A0</span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">I would be interested to =
know the circumstances when you see the maximum phase adjustment informatio=
n being used.</span></p>


<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">=A0</span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">Some comments:</span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">=A0</span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">In section 6, you say, =
=93In all three of the delay measurement modes=85=94.=A0 At that point in t=
he text you have not yet mentioned multicast, hybrid and unicast
 modes so it=92s not clear which modes you are referring to.</span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">=A0</span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">In section 9, you say, =
=93Slaves SHOULD NOT Synchronize to a Rogue Master.=94=A0 It=92s not clear =
how a slave would know that a master is rogue; presumably it would
 need to examine the announce messages of all masters and do its own BMCA e=
valuation.=A0 A more realistic =93rogue=94 master would probably meet the B=
MCA criteria for selection.</span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">=A0</span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">In section 12, =93Alterna=
tive Time Scales=94 should be =93Alternate Timescales=94.</span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">=A0</span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">=A0</span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">Regards,</span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">John Fletcher</span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">=A0</span></p>
<p class=3D"MsoNormal"><b><span lang=3D"EN-US" style=3D"font-size:10.0pt;fo=
nt-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;">From:</span></b><span =
lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Tahoma&quot;,&qu=
ot;sans-serif&quot;"> <a href=3D"mailto:tictoc-bounces@ietf.org" target=3D"=
_blank">tictoc-bounces@ietf.org</a> [mailto:<a href=3D"mailto:tictoc-bounce=
s@ietf.org" target=3D"_blank">tictoc-bounces@ietf.org</a>]
<b>On Behalf Of </b>Douglas Arnold<br>
<b>Sent:</b> 25 October 2013 01:35<br>
<b>To:</b> <a href=3D"mailto:tictoc@ietf.org" target=3D"_blank">tictoc@ietf=
.org</a><br>
<b>Subject:</b> [TICTOC] Enterprise Profile</span></p>
<p class=3D"MsoNormal">=A0</p>
<div>
<p class=3D"MsoNormal">Hello Everyone,</p>
<div>
<p class=3D"MsoNormal">=A0</p>
</div>
<div>
<p class=3D"MsoNormal">Attached is an updated version of the Enterprise pro=
file. =A0Sorry I missed the upload deadline for=A0=A0the Vancouver meeting.=
 =A0If you get a chance to look at it before then I will be there and would=
 love to discuss it.=A0</p>


</div>
<div>
<p class=3D"MsoNormal">=A0</p>
</div>
<div>
<p class=3D"MsoNormal">Summary of changes:</p>
</div>
<div>
<p class=3D"MsoNormal">=A0</p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:9.5pt;font-family:&quot;Ari=
al&quot;,&quot;sans-serif&quot;">I also changed the TLV format to fit the l=
atest proposal in the 1588 revision. =A0</span></p>
</div>
<div>
<p class=3D"MsoNormal">=A0</p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:9.5pt;font-family:&quot;Ari=
al&quot;,&quot;sans-serif&quot;">I added a statement about not going into t=
he master state unless one had a current UTC offset. =A0</span></p>
</div>
<div>
<p class=3D"MsoNormal">=A0</p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:9.5pt;font-family:&quot;Ari=
al&quot;,&quot;sans-serif&quot;">I added to the TLV fields to indicate maxi=
mum phase correction over a sync cycle.</span></p>
</div>
<div>
<div>
<p class=3D"MsoNormal">=A0</p>
</div>
<p class=3D"MsoNormal">-- </p>
<div>
<p class=3D"MsoNormal">Doug Arnold</p>
<div>
<p class=3D"MsoNormal">Principal Technologist</p>
<div>
<p class=3D"MsoNormal"><i>JTime!</i>=A0Meinberg USA</p>
</div>
</div>
<div>
<p class=3D"MsoNormal"><a href=3D"tel:%2B1-707-303-5559" value=3D"+17073035=
559" target=3D"_blank">+1-707-303-5559</a></p>
</div>
<div>
<p class=3D"MsoNormal">=A0</p>
</div>
<div>
<p class=3D"MsoNormal">=A0</p>
</div>
</div>
</div>
</div>
</div>
<p></p>
<p>=A0</p>
<p>----------------------------<br>
<font size=3D"3" face=3D"Times New Roman"><font size=3D"3" face=3D"Times Ne=
w Roman"><font size=3D"3" face=3D"Times New Roman"><br>
<font size=3D"3" face=3D"Times New Roman"><a href=3D"http://www.bbc.co.uk" =
target=3D"_blank">http://www.<span>bbc</span>.<span>co</span>.<span>uk</spa=
n></a><br>
This e-mail (and any attachments) is confidential and may contain personal =
views which are not the views of the
<span>BBC</span> unless specifically stated.<br>
If you have received it in error, please delete it from your system.<br>
Do not use, copy or disclose the information in any way nor act in reliance=
 on it and notify the sender immediately.<br>
Please note that the <span>BBC</span> monitors e-mails sent or received.<br=
>
Further communication will signify your consent to this.</font></font></fon=
t></font></p>
<p>---------------------</p>
</div>
</div></div></div>
</div>
</div><div><div>
<p></p>
<p>=A0</p>
<p>----------------------------<br>
<font size=3D"3" face=3D"Times New Roman"><font size=3D"3" face=3D"Times Ne=
w Roman"><font size=3D"3" face=3D"Times New Roman"><br>
<font size=3D"3" face=3D"Times New Roman"><a href=3D"http://www.bbc.co.uk" =
target=3D"_blank">http://www.<span>bbc</span>.<span>co</span>.<span>uk</spa=
n></a><br>
This e-mail (and any attachments) is confidential and may contain personal =
views which are not the views of the
<span>BBC</span> unless specifically stated.<br>
If you have received it in error, please delete it from your system.<br>
Do not use, copy or disclose the information in any way nor act in reliance=
 on it and notify the sender immediately.<br>
Please note that the <span>BBC</span> monitors e-mails sent or received.<br=
>
Further communication will signify your consent to this.</font></font></fon=
t></font></p>
<p>---------------------</p>
</div></div></div>

</blockquote></div><br><br clear=3D"all"><div><br></div></div></div><span c=
lass=3D"HOEnZb"><font color=3D"#888888">-- <br><div dir=3D"ltr">Doug</div>
</font></span></div>
<br>_______________________________________________<br>
TICTOC mailing list<br>
<a href=3D"mailto:TICTOC@ietf.org">TICTOC@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/tictoc" target=3D"_blank">=
https://www.ietf.org/mailman/listinfo/tictoc</a><br>
<br></blockquote></div><br></div>

--001a11c357607df4b504e9d747ce--

From mayer@pdmconsulting.net  Mon Oct 28 12:13:19 2013
Return-Path: <mayer@pdmconsulting.net>
X-Original-To: tictoc@ietfa.amsl.com
Delivered-To: tictoc@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EA08011E81B7 for <tictoc@ietfa.amsl.com>; Mon, 28 Oct 2013 12:13:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4LW2hKJh7z48 for <tictoc@ietfa.amsl.com>; Mon, 28 Oct 2013 12:13:14 -0700 (PDT)
Received: from gizmo.everett.org (gizmo.everett.org [66.220.13.237]) by ietfa.amsl.com (Postfix) with ESMTP id 83B5B11E81AD for <tictoc@ietf.org>; Mon, 28 Oct 2013 12:13:10 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by gizmo.everett.org (Postfix) with SMTP id D235F1CD56 for <tictoc@ietf.org>; Mon, 28 Oct 2013 12:13:09 -0700 (PDT) (envelope-from mayer@pdmconsulting.net)
Received: from [10.2.64.81] (unknown [198.22.153.36]) by gizmo.everett.org (Postfix) with ESMTPSA id 14EE41CCC9; Mon, 28 Oct 2013 12:13:08 -0700 (PDT) (envelope-from mayer@pdmconsulting.net)
Message-ID: <526EB72F.1050004@pdmconsulting.net>
Date: Mon, 28 Oct 2013 15:12:47 -0400
From: Danny Mayer <mayer@pdmconsulting.net>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.0.1
MIME-Version: 1.0
To: Magnus Danielson <magnus@rubidium.dyndns.org>, ntpwg@lists.ntp.org,  "tictoc@ietf.org" <tictoc@ietf.org>
References: <74470498B659FA4687F0B0018C19A89C01B87D7A40A6@IL-MB01.marvell.com>	<526C30F9.1040400@ntp.org>	<74470498B659FA4687F0B0018C19A89C01B87D7A4C6E@IL-MB01.marvell.com>	<526D165D.3040902@ntp.org>	<74470498B659FA4687F0B0018C19A89C01B87D7A4DC7@IL-MB01.marvell.com> <526D1EF0.4070208@rubidium.dyndns.org>
In-Reply-To: <526D1EF0.4070208@rubidium.dyndns.org>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-DSPAM-Result: Innocent
X-DSPAM-Processed: Mon Oct 28 12:13:09 2013
X-DSPAM-Confidence: 1.0000
X-DSPAM-Probability: -1.0000
X-DSPAM-Signature: 526eb745411221099612492
X-Mailman-Approved-At: Mon, 28 Oct 2013 23:17:04 -0700
Subject: Re: [TICTOC] [ntpwg] New version of draft-mizrahi-ntp-checksum-trailer
X-BeenThere: tictoc@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: mayer@pdmconsulting.net
List-Id: Timing over IP Connection and Transfer of Clock BOF <tictoc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tictoc>, <mailto:tictoc-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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>
X-List-Received-Date: Mon, 28 Oct 2013 19:13:20 -0000

On 10/27/2013 10:10 AM, Magnus Danielson wrote:
> On 10/27/2013 02:42 PM, Tal Mizrahi wrote:
>> Hi Danny,
>>
>>> That also means that the extension field MUST NOT be added by any intermediate nodes if it does not exist.
>> I am not sure we want to go there, for 2 reasons:
>>
>> 1. Let's not forget that the source and the intermediate node are in fact two modules in the same client/server (see Figure 1 in the draft). From an interoperability perspective it would be exactly the same if the source created the extension field, or the intermediate node did. Why would we mandate a specific implementation detail that would be completely transparent to the network?
>>
>> 2. A clock that receives an NTP message has no way of knowing whether an extension field was added by the source or by an intermediate node, and thus there is no way to enforce (enforce from a security perspective) the requirement you suggested.
> I think this discussion would benefit from separating "interface node"
> from "intermediate node" as these have different roles. The interface
> node would add the output time-stamp of the sending node. If
> intermediate nodes where allowed to add fields, we could have buffer
> compensation in NTP just as in PTP's transparent clock.

I'm not sure that there's a real difference here. From a topological
point of view the interface node and an intermediate node are just a
node in the network. You are just calling it a different name.

> At the same time, as long as there is no authentication on this, any
> intermediate node can create any form of modification that the receiver
> node will accept, malicious or unintentional. Hence, there is only so
> much protection you can create in the semantics.
> 

There's no protection whatsoever here.

Danny



From John.Fletcher@bbc.co.uk  Tue Oct 29 03:18:54 2013
Return-Path: <John.Fletcher@bbc.co.uk>
X-Original-To: tictoc@ietfa.amsl.com
Delivered-To: tictoc@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 333E321E8104 for <tictoc@ietfa.amsl.com>; Tue, 29 Oct 2013 03:18:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -8.576
X-Spam-Level: 
X-Spam-Status: No, score=-8.576 tagged_above=-999 required=5 tests=[AWL=2.022,  BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id DtB84Xr8gQ4w for <tictoc@ietfa.amsl.com>; Tue, 29 Oct 2013 03:18:49 -0700 (PDT)
Received: from mailout1.thls.bbc.co.uk (mailout1.thls.bbc.co.uk [132.185.240.36]) by ietfa.amsl.com (Postfix) with ESMTP id 6E8CF21E8106 for <tictoc@ietf.org>; Tue, 29 Oct 2013 03:18:35 -0700 (PDT)
Received: from BGB01XI1004.national.core.bbc.co.uk ([10.184.50.54]) by mailout1.thls.bbc.co.uk (8.14.4/8.14.3) with ESMTP id r9TAIR2p023768; Tue, 29 Oct 2013 10:18:28 GMT
Received: from BGB01XUD1011.national.core.bbc.co.uk ([169.254.10.4]) by BGB01XI1004.national.core.bbc.co.uk ([10.184.50.54]) with mapi id 14.02.0342.004; Tue, 29 Oct 2013 10:18:27 +0000
From: John Fletcher <John.Fletcher@bbc.co.uk>
To: "'Douglas Arnold'" <doug.arnold2@gmail.com>, "'Kevin Gross' (kevin.gross@avanw.com)" <kevin.gross@avanw.com>
Thread-Topic: [TICTOC] Enterprise Profile
Thread-Index: AQHO0Tj+EfJkN9q+/USLYOoP7dIkB5oFJTNggAUWS6GAAFQ5gIAA6iNA
Date: Tue, 29 Oct 2013 10:18:27 +0000
Message-ID: <B1D49063AD5FBD4688F3EEDEC68B20175114537C@BGB01XUD1011.national.core.bbc.co.uk>
References: <CACQYgzFmOtFY+Td0jZMyykeZ17KwAuCc+LY+C2be_UPgZKh9GA@mail.gmail.com> <B1D49063AD5FBD4688F3EEDEC68B201751132BDF@BGB01XUD1002.national.core.bbc.co.uk> <B1D49063AD5FBD4688F3EEDEC68B20175113E0AA@BGB01XUD1011.national.core.bbc.co.uk> <CACQYgzEEcZPLEBgyTPUyqYbRjNi_7oFvm7TVxhGthQL-hx6nYA@mail.gmail.com>
In-Reply-To: <CACQYgzEEcZPLEBgyTPUyqYbRjNi_7oFvm7TVxhGthQL-hx6nYA@mail.gmail.com>
Accept-Language: en-GB, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.162.14.18]
x-exclaimer-md-config: 1cd3ac1c-62e5-43f2-8404-6b688271c769
Content-Type: multipart/alternative; boundary="_000_B1D49063AD5FBD4688F3EEDEC68B20175114537CBGB01XUD1011nat_"
MIME-Version: 1.0
Cc: "tictoc@ietf.org" <tictoc@ietf.org>
Subject: Re: [TICTOC] Enterprise Profile
X-BeenThere: tictoc@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Timing over IP Connection and Transfer of Clock BOF <tictoc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tictoc>, <mailto:tictoc-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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>
X-List-Received-Date: Tue, 29 Oct 2013 10:18:54 -0000

--_000_B1D49063AD5FBD4688F3EEDEC68B20175114537CBGB01XUD1011nat_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Just to be clear, I am not suggesting use of a different epoch in timestamp=
 fields.  I am talking about the optional TLV described in section 16.3 whi=
ch can give you the offset(s) between PTP time and one or more timescales o=
f your choice.

Regarding spanning timezones, there is a difference between the extent of t=
he enterprise network and the extent of the part of network served by a PTP=
 master.  The latter is probably a subnet since multicast messages (e.g. An=
nounce) are usually confined to a subnet.  A subnet spanning multiple timez=
ones would be less common.  However you can have more than one Alternate Ti=
mescale if necessary.

This feature is just an option; I'm not suggesting it be required, just tha=
t it not be forbidden.

John

From: Douglas Arnold [mailto:doug.arnold2@gmail.com]
Sent: 28 October 2013 20:06
To: John Fletcher
Cc: tictoc@ietf.org
Subject: Re: [TICTOC] Enterprise Profile

Hello John,

I agree that local time is useful.  I would not be averse to creating a TLV=
 to distribute local time offset, so that end node can convert to local tim=
e and present it to users.

However, I do not support the idea of using a local time epoch in the PTP t=
imestamp fields. This is an allowed option in IEEE 1588-2008, but I believe=
 that this is likely to cause interoperability problems, when some vendors =
support it and others do not.  Also some system architechs have indicated t=
hat they deploy PTP across large networks, which span time zones. This is t=
he feature that should be forbidden.

In the NTP standard (RFC5905) the timestamps in the packet all use a specif=
ic time epoch, and generate all other desired time epoch as corrections per=
formed at the end points.  Note also that in most computer operating system=
s a single standard time epoch is used in and local time is generated at th=
e presentation layer for human readable interfaces.

Doug

On Mon, Oct 28, 2013 at 8:10 AM, John Fletcher <John.Fletcher@bbc.co.uk<mai=
lto:John.Fletcher@bbc.co.uk>> wrote:
I'd also like to ask that you don't prohibit the Alternate Timescales optio=
n.  This is potentially useful to distribute "local time" (your time-zone a=
nd dst) and there doesn't seem to be any need to prohibit it.

John
________________________________
From: tictoc-bounces@ietf.org<mailto:tictoc-bounces@ietf.org> [tictoc-bounc=
es@ietf.org<mailto:tictoc-bounces@ietf.org>] on behalf of John Fletcher [Jo=
hn.Fletcher@bbc.co.uk<mailto:John.Fletcher@bbc.co.uk>]
Sent: 25 October 2013 11:01
To: Douglas Arnold
Cc: tictoc@ietf.org<mailto:tictoc@ietf.org>
Subject: Re: [TICTOC] Enterprise Profile
Doug,

I would be interested to know the circumstances when you see the maximum ph=
ase adjustment information being used.

Some comments:

In section 6, you say, "In all three of the delay measurement modes...".  A=
t that point in the text you have not yet mentioned multicast, hybrid and u=
nicast modes so it's not clear which modes you are referring to.

In section 9, you say, "Slaves SHOULD NOT Synchronize to a Rogue Master."  =
It's not clear how a slave would know that a master is rogue; presumably it=
 would need to examine the announce messages of all masters and do its own =
BMCA evaluation.  A more realistic "rogue" master would probably meet the B=
MCA criteria for selection.

In section 12, "Alternative Time Scales" should be "Alternate Timescales".


Regards,
John Fletcher

From: tictoc-bounces@ietf.org<mailto:tictoc-bounces@ietf.org> [mailto:ticto=
c-bounces@ietf.org<mailto:tictoc-bounces@ietf.org>] On Behalf Of Douglas Ar=
nold
Sent: 25 October 2013 01:35
To: tictoc@ietf.org<mailto:tictoc@ietf.org>
Subject: [TICTOC] Enterprise Profile

Hello Everyone,

Attached is an updated version of the Enterprise profile.  Sorry I missed t=
he upload deadline for  the Vancouver meeting.  If you get a chance to look=
 at it before then I will be there and would love to discuss it.

Summary of changes:

I also changed the TLV format to fit the latest proposal in the 1588 revisi=
on.

I added a statement about not going into the master state unless one had a =
current UTC offset.

I added to the TLV fields to indicate maximum phase correction over a sync =
cycle.

--
Doug Arnold
Principal Technologist
JTime! Meinberg USA
+1-707-303-5559<tel:%2B1-707-303-5559>





----------------------------

http://www.bbc.co.uk
This e-mail (and any attachments) is confidential and may contain personal =
views which are not the views of the BBC unless specifically stated.
If you have received it in error, please delete it from your system.
Do not use, copy or disclose the information in any way nor act in reliance=
 on it and notify the sender immediately.
Please note that the BBC monitors e-mails sent or received.
Further communication will signify your consent to this.

---------------------



----------------------------

http://www.bbc.co.uk
This e-mail (and any attachments) is confidential and may contain personal =
views which are not the views of the BBC unless specifically stated.
If you have received it in error, please delete it from your system.
Do not use, copy or disclose the information in any way nor act in reliance=
 on it and notify the sender immediately.
Please note that the BBC monitors e-mails sent or received.
Further communication will signify your consent to this.

---------------------



--
Doug

--_000_B1D49063AD5FBD4688F3EEDEC68B20175114537CBGB01XUD1011nat_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
<meta name=3D"Generator" content=3D"Microsoft Word 14 (filtered medium)">
<!--[if !mso]><style>v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style><![endif]--><style><!--
/* Font Definitions */
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
p
	{mso-style-priority:99;
	mso-margin-top-alt:auto;
	margin-right:0cm;
	mso-margin-bottom-alt:auto;
	margin-left:0cm;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
	{mso-style-priority:99;
	mso-style-link:"Balloon Text Char";
	margin:0cm;
	margin-bottom:.0001pt;
	font-size:8.0pt;
	font-family:"Tahoma","sans-serif";}
span.BalloonTextChar
	{mso-style-name:"Balloon Text Char";
	mso-style-priority:99;
	mso-style-link:"Balloon Text";
	font-family:"Tahoma","sans-serif";
	mso-fareast-language:EN-GB;}
span.EmailStyle20
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-family:"Calibri","sans-serif";
	mso-fareast-language:EN-US;}
@page WordSection1
	{size:612.0pt 792.0pt;
	margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=3D"EN-GB" link=3D"blue" vlink=3D"purple">
<div class=3D"WordSection1">
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">Just to be clear, I am no=
t suggesting use of a different epoch in timestamp fields.&nbsp; I am talki=
ng about the optional TLV described in section 16.3 which can
 give you the offset(s) between PTP time and one or more timescales of your=
 choice.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">Regarding spanning timezo=
nes, there is a difference between the extent of the enterprise network and=
 the extent of the part of network served by a PTP master.&nbsp;
 The latter is probably a subnet since multicast messages (e.g. Announce) a=
re usually confined to a subnet.&nbsp; A subnet spanning multiple timezones=
 would be less common.&nbsp; However you can have more than one Alternate T=
imescale if necessary.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">This feature is just an o=
ption; I&#8217;m not suggesting it be required, just that it not be forbidd=
en.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">John<o:p></o:p></span></p=
>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<p class=3D"MsoNormal"><b><span lang=3D"EN-US" style=3D"font-size:10.0pt;fo=
nt-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;">From:</span></b><span =
lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Tahoma&quot;,&qu=
ot;sans-serif&quot;"> Douglas Arnold [mailto:doug.arnold2@gmail.com]
<br>
<b>Sent:</b> 28 October 2013 20:06<br>
<b>To:</b> John Fletcher<br>
<b>Cc:</b> tictoc@ietf.org<br>
<b>Subject:</b> Re: [TICTOC] Enterprise Profile<o:p></o:p></span></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<div>
<p class=3D"MsoNormal">Hello John,<o:p></o:p></p>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<div>
<p class=3D"MsoNormal">I agree that local time is useful. &nbsp;I would not=
 be averse to creating a TLV to distribute local time offset, so that end n=
ode can convert to local time and present it to users.<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<div>
<p class=3D"MsoNormal">However, I do not support the idea of using a local =
time epoch in the PTP timestamp fields. This is an allowed option in IEEE 1=
588-2008, but I believe that this is likely to cause interoperability probl=
ems, when some vendors support it
 and others do not.&nbsp;&nbsp;Also some system architechs have indicated t=
hat they deploy PTP across large networks, which span time zones.&nbsp;This=
 is the feature that should be forbidden. &nbsp;<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<div>
<p class=3D"MsoNormal">In the NTP standard (RFC5905) the timestamps in the =
packet all use a specific time epoch, and generate all other desired time e=
poch as corrections performed at the end points. &nbsp;Note also that in mo=
st computer operating systems a single
 standard time epoch is used in and local time is generated at the presenta=
tion layer for human readable interfaces.<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<div>
<p class=3D"MsoNormal">Doug<o:p></o:p></p>
</div>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt"><o:p>&nbsp;</o:p></p>
<div>
<p class=3D"MsoNormal">On Mon, Oct 28, 2013 at 8:10 AM, John Fletcher &lt;<=
a href=3D"mailto:John.Fletcher@bbc.co.uk" target=3D"_blank">John.Fletcher@b=
bc.co.uk</a>&gt; wrote:<o:p></o:p></p>
<div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Ta=
homa&quot;,&quot;sans-serif&quot;">I'd also like to ask that you don't proh=
ibit the Alternate Timescales option. &nbsp;This is potentially useful to d=
istribute &quot;local time&quot; (your time-zone and dst) and there doesn't
 seem to be any need to prohibit it. <o:p></o:p></span></p>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Ta=
homa&quot;,&quot;sans-serif&quot;"><o:p>&nbsp;</o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Ta=
homa&quot;,&quot;sans-serif&quot;">John<o:p></o:p></span></p>
<div>
<div class=3D"MsoNormal" align=3D"center" style=3D"text-align:center">
<hr size=3D"2" width=3D"100%" align=3D"center">
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt"><b><span style=3D"fon=
t-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;;color:black">From:</span=
></b><span style=3D"font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;;c=
olor:black">
<a href=3D"mailto:tictoc-bounces@ietf.org" target=3D"_blank">tictoc-bounces=
@ietf.org</a> [<a href=3D"mailto:tictoc-bounces@ietf.org" target=3D"_blank"=
>tictoc-bounces@ietf.org</a>] on behalf of John Fletcher [<a href=3D"mailto=
:John.Fletcher@bbc.co.uk" target=3D"_blank">John.Fletcher@bbc.co.uk</a>]<br=
>
<b>Sent:</b> 25 October 2013 11:01<br>
<b>To:</b> Douglas Arnold<br>
<b>Cc:</b> <a href=3D"mailto:tictoc@ietf.org" target=3D"_blank">tictoc@ietf=
.org</a><br>
<b>Subject:</b> Re: [TICTOC] Enterprise Profile</span><o:p></o:p></p>
</div>
<div>
<div>
<div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:#1F497D">Doug,</span><o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:#1F497D">&nbsp;</span><o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:#1F497D">I would be interested to know the circu=
mstances when you see the maximum phase adjustment information
 being used.</span><o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:#1F497D">&nbsp;</span><o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:#1F497D">Some comments:</span><o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:#1F497D">&nbsp;</span><o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:#1F497D">In section 6, you say, &#8220;In all th=
ree of the delay measurement modes&#8230;&#8221;.&nbsp; At that point in th=
e text
 you have not yet mentioned multicast, hybrid and unicast modes so it&#8217=
;s not clear which modes you are referring to.</span><o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:#1F497D">&nbsp;</span><o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:#1F497D">In section 9, you say, &#8220;Slaves SH=
OULD NOT Synchronize to a Rogue Master.&#8221;&nbsp; It&#8217;s not clear h=
ow a slave
 would know that a master is rogue; presumably it would need to examine the=
 announce messages of all masters and do its own BMCA evaluation.&nbsp; A m=
ore realistic &#8220;rogue&#8221; master would probably meet the BMCA crite=
ria for selection.</span><o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:#1F497D">&nbsp;</span><o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:#1F497D">In section 12, &#8220;Alternative Time =
Scales&#8221; should be &#8220;Alternate Timescales&#8221;.</span><o:p></o:=
p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:#1F497D">&nbsp;</span><o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:#1F497D">&nbsp;</span><o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:#1F497D">Regards,</span><o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:#1F497D">John Fletcher</span><o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:#1F497D">&nbsp;</span><o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><b><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quo=
t;Tahoma&quot;,&quot;sans-serif&quot;">From:</span></b><span lang=3D"EN-US"=
 style=3D"font-size:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&=
quot;">
<a href=3D"mailto:tictoc-bounces@ietf.org" target=3D"_blank">tictoc-bounces=
@ietf.org</a> [mailto:<a href=3D"mailto:tictoc-bounces@ietf.org" target=3D"=
_blank">tictoc-bounces@ietf.org</a>]
<b>On Behalf Of </b>Douglas Arnold<br>
<b>Sent:</b> 25 October 2013 01:35<br>
<b>To:</b> <a href=3D"mailto:tictoc@ietf.org" target=3D"_blank">tictoc@ietf=
.org</a><br>
<b>Subject:</b> [TICTOC] Enterprise Profile</span><o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">&nbsp;<o:p></o:p></p>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">Hello Everyone,<o:p></o:p></p>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">&nbsp;<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">Attached is an updated version of the Enterprise profile. &nbsp;So=
rry I missed the upload deadline for&nbsp;&nbsp;the Vancouver meeting. &nbs=
p;If you get a chance to look at it before then I will be
 there and would love to discuss it.&nbsp;<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">&nbsp;<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">Summary of changes:<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">&nbsp;<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:9.5pt;font-family:&quot;Arial&quot;,&quot=
;sans-serif&quot;">I also changed the TLV format to fit the latest proposal=
 in the 1588 revision. &nbsp;</span><o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">&nbsp;<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:9.5pt;font-family:&quot;Arial&quot;,&quot=
;sans-serif&quot;">I added a statement about not going into the master stat=
e unless one had a current UTC offset. &nbsp;</span><o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">&nbsp;<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:9.5pt;font-family:&quot;Arial&quot;,&quot=
;sans-serif&quot;">I added to the TLV fields to indicate maximum phase corr=
ection over a sync cycle.</span><o:p></o:p></p>
</div>
<div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">&nbsp;<o:p></o:p></p>
</div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">--
<o:p></o:p></p>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">Doug Arnold<o:p></o:p></p>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">Principal Technologist<o:p></o:p></p>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><i>JTime!</i>&nbsp;Meinberg USA<o:p></o:p></p>
</div>
</div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><a href=3D"tel:%2B1-707-303-5559" target=3D"_blank">&#43;1-707-303=
-5559</a><o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">&nbsp;<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">&nbsp;<o:p></o:p></p>
</div>
</div>
</div>
</div>
</div>
<p>&nbsp;<o:p></o:p></p>
<p>----------------------------<br>
<br>
<a href=3D"http://www.bbc.co.uk" target=3D"_blank">http://www.bbc.co.uk</a>=
<br>
This e-mail (and any attachments) is confidential and may contain personal =
views which are not the views of the BBC unless specifically stated.<br>
If you have received it in error, please delete it from your system.<br>
Do not use, copy or disclose the information in any way nor act in reliance=
 on it and notify the sender immediately.<br>
Please note that the BBC monitors e-mails sent or received.<br>
Further communication will signify your consent to this.<o:p></o:p></p>
<p>---------------------<o:p></o:p></p>
</div>
</div>
</div>
</div>
</div>
</div>
<div>
<div>
<p>&nbsp;<o:p></o:p></p>
<p>----------------------------<br>
<br>
<a href=3D"http://www.bbc.co.uk" target=3D"_blank">http://www.bbc.co.uk</a>=
<br>
This e-mail (and any attachments) is confidential and may contain personal =
views which are not the views of the BBC unless specifically stated.<br>
If you have received it in error, please delete it from your system.<br>
Do not use, copy or disclose the information in any way nor act in reliance=
 on it and notify the sender immediately.<br>
Please note that the BBC monitors e-mails sent or received.<br>
Further communication will signify your consent to this.<o:p></o:p></p>
<p>---------------------<o:p></o:p></p>
</div>
</div>
</div>
</div>
<p class=3D"MsoNormal"><br>
<br clear=3D"all">
<o:p></o:p></p>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<p class=3D"MsoNormal">-- <o:p></o:p></p>
<div>
<p class=3D"MsoNormal">Doug<o:p></o:p></p>
</div>
</div>
</div>
</body>
</html>

--_000_B1D49063AD5FBD4688F3EEDEC68B20175114537CBGB01XUD1011nat_--

From kevin.gross@avanw.com  Tue Oct 29 08:47:33 2013
Return-Path: <kevin.gross@avanw.com>
X-Original-To: tictoc@ietfa.amsl.com
Delivered-To: tictoc@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 25C6F11E830F for <tictoc@ietfa.amsl.com>; Tue, 29 Oct 2013 08:47:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.186
X-Spam-Level: 
X-Spam-Status: No, score=0.186 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FH_RELAY_NODNS=1.451, FM_FORGED_GMAIL=0.622, HELO_MISMATCH_NET=0.611, HTML_MESSAGE=0.001, RDNS_NONE=0.1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id tTpVuIgja7iZ for <tictoc@ietfa.amsl.com>; Tue, 29 Oct 2013 08:47:28 -0700 (PDT)
Received: from qmta14.westchester.pa.mail.comcast.net (qmta14.westchester.pa.mail.comcast.net [IPv6:2001:558:fe14:44:76:96:59:212]) by ietfa.amsl.com (Postfix) with ESMTP id 78AD211E82FD for <tictoc@ietf.org>; Tue, 29 Oct 2013 08:47:13 -0700 (PDT)
Received: from omta03.westchester.pa.mail.comcast.net ([76.96.62.27]) by qmta14.westchester.pa.mail.comcast.net with comcast id j1kB1m00K0bG4ec5E3nBmX; Tue, 29 Oct 2013 15:47:11 +0000
Received: from mail-we0-f172.google.com ([74.125.82.172]) by omta03.westchester.pa.mail.comcast.net with comcast id j3lA1m00l3j4fmJ3P3lBhn; Tue, 29 Oct 2013 15:45:11 +0000
Received: by mail-we0-f172.google.com with SMTP id q58so27351wes.31 for <tictoc@ietf.org>; Tue, 29 Oct 2013 08:45:09 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=FYxLjWQYl9GJofSegeO24JTXcTebrcu8/cZbn7Kr7y0=; b=P7Yt7PIJxwmsGBTJGaXzg9IuOXXVCp8PBuPtVdyKYEfMt+aDPFz5OKifjclPVzuHSg mfVz56LUbk5OQtjJ379J+acjmvDLQW6M4QnXVS6PRjunWULJWHE8iyeacfrboNxHGq+8 j8B7V4t8fOV9Gduu76oclv/fRKI0MFdUrXczXxfhOaL3+93UqND6YHeV6gl98FledrjQ lCj3LzRslSgYB2oULuMrqosN7TgRi1xsBVOfCc47+xdIO8r4fO6OWL10D99X7Vr7Mc8g SfYV6ZgWWhj4qJGvcB+TBv7iNZapn1l42jL3ZGKhb9ZN4BGncKrM3GeMrAonN9uZci1m GrwA==
MIME-Version: 1.0
X-Received: by 10.194.110.166 with SMTP id ib6mr446018wjb.14.1383061509793; Tue, 29 Oct 2013 08:45:09 -0700 (PDT)
Received: by 10.216.202.7 with HTTP; Tue, 29 Oct 2013 08:45:09 -0700 (PDT)
In-Reply-To: <B1D49063AD5FBD4688F3EEDEC68B20175114537C@BGB01XUD1011.national.core.bbc.co.uk>
References: <CACQYgzFmOtFY+Td0jZMyykeZ17KwAuCc+LY+C2be_UPgZKh9GA@mail.gmail.com> <B1D49063AD5FBD4688F3EEDEC68B201751132BDF@BGB01XUD1002.national.core.bbc.co.uk> <B1D49063AD5FBD4688F3EEDEC68B20175113E0AA@BGB01XUD1011.national.core.bbc.co.uk> <CACQYgzEEcZPLEBgyTPUyqYbRjNi_7oFvm7TVxhGthQL-hx6nYA@mail.gmail.com> <B1D49063AD5FBD4688F3EEDEC68B20175114537C@BGB01XUD1011.national.core.bbc.co.uk>
Date: Tue, 29 Oct 2013 09:45:09 -0600
Message-ID: <CALw1_Q10rT9eyh40Udk1NQLHbREPPtxPSTYQ9GFKhZdeD7-EqA@mail.gmail.com>
From: Kevin Gross <kevin.gross@avanw.com>
To: John Fletcher <John.Fletcher@bbc.co.uk>
Content-Type: multipart/alternative; boundary=047d7bf198e0fe711d04e9e319f7
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20121106; t=1383061631; bh=FYxLjWQYl9GJofSegeO24JTXcTebrcu8/cZbn7Kr7y0=; h=Received:Received:Received:MIME-Version:Received:Date:Message-ID: Subject:From:To:Content-Type; b=FPchAGo8VLXUMmb3US3GHOXbuJ2djPJU8arNQZanp8yVatDpdrvys0pcJMWK1GJ1W 2grJvkfn/F/Y/9Ghb8Im2LyJ0aUVLsgISiOrMQCVsNgK+nlyJOXv5akomXu0hOUF6y sJlckgN5yhXX7b1BegdDo9Yo/1wkWl0ZcLZ4QEl3tt/a7dcDBKJwxcR3NHPosbpOkl aMtd7iEg2vGShyVPxBlDLICr4U/0BTJNuzDA4mwdhLHYO7AfKQzLRqyvoDF0nt4ZF/ WK9rYINlwgbgGUky2jdU3mOmTFguurWgetbzd0Cb1Z6moBcBqvOLzImx7vkZlM+NwG ZnQu4pnD4kVaA==
Cc: Douglas Arnold <doug.arnold2@gmail.com>, "tictoc@ietf.org" <tictoc@ietf.org>
Subject: Re: [TICTOC] Enterprise Profile
X-BeenThere: tictoc@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Timing over IP Connection and Transfer of Clock BOF <tictoc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tictoc>, <mailto:tictoc-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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>
X-List-Received-Date: Tue, 29 Oct 2013 15:47:34 -0000

--047d7bf198e0fe711d04e9e319f7
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: quoted-printable

Multicast IP routing allows multicast messaging beyond a subnet. Multicast
IP routing is not available over the internet but it is now fairly common
on enterprise networks.

John, can you describe a use case for alternate timescales and explain how
the endstation can know that the timescale is correct local time or which
alternate timescale to use if there are multiple?

Kevin Gross
+1-303-447-0517
Media Network Consultant
AVA Networks - www.AVAnw.com <http://www.avanw.com/>


On Tue, Oct 29, 2013 at 4:18 AM, John Fletcher <John.Fletcher@bbc.co.uk>wro=
te:

>  Just to be clear, I am not suggesting use of a different epoch in
> timestamp fields.  I am talking about the optional TLV described in secti=
on
> 16.3 which can give you the offset(s) between PTP time and one or more
> timescales of your choice.****
>
> ** **
>
> Regarding spanning timezones, there is a difference between the extent of
> the enterprise network and the extent of the part of network served by a
> PTP master.  The latter is probably a subnet since multicast messages (e.=
g.
> Announce) are usually confined to a subnet.  A subnet spanning multiple
> timezones would be less common.  However you can have more than one
> Alternate Timescale if necessary.****
>
> ** **
>
> This feature is just an option; I=92m not suggesting it be required, just
> that it not be forbidden.****
>
> ** **
>
> John****
>
> ** **
>
> *From:* Douglas Arnold [mailto:doug.arnold2@gmail.com]
> *Sent:* 28 October 2013 20:06
> *To:* John Fletcher
>
> *Cc:* tictoc@ietf.org
> *Subject:* Re: [TICTOC] Enterprise Profile****
>
> ** **
>
> Hello John,****
>
> ** **
>
> I agree that local time is useful.  I would not be averse to creating a
> TLV to distribute local time offset, so that end node can convert to loca=
l
> time and present it to users.****
>
> ** **
>
> However, I do not support the idea of using a local time epoch in the PTP
> timestamp fields. This is an allowed option in IEEE 1588-2008, but I
> believe that this is likely to cause interoperability problems, when some
> vendors support it and others do not.  Also some system architechs have
> indicated that they deploy PTP across large networks, which span time
> zones. This is the feature that should be forbidden.  ****
>
> ** **
>
> In the NTP standard (RFC5905) the timestamps in the packet all use a
> specific time epoch, and generate all other desired time epoch as
> corrections performed at the end points.  Note also that in most computer
> operating systems a single standard time epoch is used in and local time =
is
> generated at the presentation layer for human readable interfaces.****
>
> ** **
>
> Doug****
>
> ** **
>
> On Mon, Oct 28, 2013 at 8:10 AM, John Fletcher <John.Fletcher@bbc.co.uk>
> wrote:****
>
> I'd also like to ask that you don't prohibit the Alternate Timescales
> option.  This is potentially useful to distribute "local time" (your
> time-zone and dst) and there doesn't seem to be any need to prohibit it. =
*
> ***
>
> ** **
>
> John****
>  ------------------------------
>
> *From:* tictoc-bounces@ietf.org [tictoc-bounces@ietf.org] on behalf of
> John Fletcher [John.Fletcher@bbc.co.uk]
> *Sent:* 25 October 2013 11:01
> *To:* Douglas Arnold
> *Cc:* tictoc@ietf.org
> *Subject:* Re: [TICTOC] Enterprise Profile****
>
> Doug,****
>
>  ****
>
> I would be interested to know the circumstances when you see the maximum
> phase adjustment information being used.****
>
>  ****
>
> Some comments:****
>
>  ****
>
> In section 6, you say, =93In all three of the delay measurement modes=85=
=94.  At
> that point in the text you have not yet mentioned multicast, hybrid and
> unicast modes so it=92s not clear which modes you are referring to.****
>
>  ****
>
> In section 9, you say, =93Slaves SHOULD NOT Synchronize to a Rogue Master=
.=94
> It=92s not clear how a slave would know that a master is rogue; presumabl=
y it
> would need to examine the announce messages of all masters and do its own
> BMCA evaluation.  A more realistic =93rogue=94 master would probably meet=
 the
> BMCA criteria for selection.****
>
>  ****
>
> In section 12, =93Alternative Time Scales=94 should be =93Alternate Times=
cales=94.
> ****
>
>  ****
>
>  ****
>
> Regards,****
>
> John Fletcher****
>
>  ****
>
> *From:* tictoc-bounces@ietf.org [mailto:tictoc-bounces@ietf.org] *On
> Behalf Of *Douglas Arnold
> *Sent:* 25 October 2013 01:35
> *To:* tictoc@ietf.org
> *Subject:* [TICTOC] Enterprise Profile****
>
>  ****
>
> Hello Everyone,****
>
>  ****
>
> Attached is an updated version of the Enterprise profile.  Sorry I missed
> the upload deadline for  the Vancouver meeting.  If you get a chance to
> look at it before then I will be there and would love to discuss it. ****
>
>  ****
>
> Summary of changes:****
>
>  ****
>
> I also changed the TLV format to fit the latest proposal in the 1588
> revision.  ****
>
>  ****
>
> I added a statement about not going into the master state unless one had =
a
> current UTC offset.  ****
>
>  ****
>
> I added to the TLV fields to indicate maximum phase correction over a syn=
c
> cycle.****
>
>  ****
>
> -- ****
>
> Doug Arnold****
>
> Principal Technologist****
>
> *JTime!* Meinberg USA****
>
> +1-707-303-5559****
>
>  ****
>
>  ****
>
>  ****
>
> ----------------------------
>
> http://www.bbc.co.uk
> This e-mail (and any attachments) is confidential and may contain persona=
l
> views which are not the views of the BBC unless specifically stated.
> If you have received it in error, please delete it from your system.
> Do not use, copy or disclose the information in any way nor act in
> reliance on it and notify the sender immediately.
> Please note that the BBC monitors e-mails sent or received.
> Further communication will signify your consent to this.****
>
> ---------------------****
>
>  ****
>
> ----------------------------
>
> http://www.bbc.co.uk
> This e-mail (and any attachments) is confidential and may contain persona=
l
> views which are not the views of the BBC unless specifically stated.
> If you have received it in error, please delete it from your system.
> Do not use, copy or disclose the information in any way nor act in
> reliance on it and notify the sender immediately.
> Please note that the BBC monitors e-mails sent or received.
> Further communication will signify your consent to this.****
>
> ---------------------****
>
>
>
> ****
>
> ** **
>
> -- ****
>
> Doug****
>

--047d7bf198e0fe711d04e9e319f7
Content-Type: text/html; charset=windows-1252
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Multicast IP routing allows multicast messaging beyond a s=
ubnet. Multicast IP routing is not available over the internet but it is no=
w fairly common on enterprise networks.<div><br></div><div>John, can you de=
scribe a use case for alternate timescales and explain how the endstation c=
an know that the timescale is correct local time or which alternate timesca=
le to use if there are multiple?</div>
</div><div class=3D"gmail_extra"><br clear=3D"all"><div><div dir=3D"ltr">Ke=
vin Gross<br><div>+1-303-447-0517</div><div>Media Network Consultant<br><di=
v>AVA Networks -=A0<a href=3D"http://www.avanw.com/" target=3D"_blank">www.=
AVAnw.com</a></div>
</div></div></div>
<br><br><div class=3D"gmail_quote">On Tue, Oct 29, 2013 at 4:18 AM, John Fl=
etcher <span dir=3D"ltr">&lt;<a href=3D"mailto:John.Fletcher@bbc.co.uk" tar=
get=3D"_blank">John.Fletcher@bbc.co.uk</a>&gt;</span> wrote:<br><blockquote=
 class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc soli=
d;padding-left:1ex">






<div lang=3D"EN-GB" link=3D"blue" vlink=3D"purple">
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">Just to be clear, I am no=
t suggesting use of a different epoch in timestamp fields.=A0 I am talking =
about the optional TLV described in section 16.3 which can
 give you the offset(s) between PTP time and one or more timescales of your=
 choice.<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d"><u></u>=A0<u></u></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">Regarding spanning timezo=
nes, there is a difference between the extent of the enterprise network and=
 the extent of the part of network served by a PTP master.=A0
 The latter is probably a subnet since multicast messages (e.g. Announce) a=
re usually confined to a subnet.=A0 A subnet spanning multiple timezones wo=
uld be less common.=A0 However you can have more than one Alternate Timesca=
le if necessary.<u></u><u></u></span></p>

<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d"><u></u>=A0<u></u></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">This feature is just an o=
ption; I=92m not suggesting it be required, just that it not be forbidden.<=
u></u><u></u></span></p>

<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d"><u></u>=A0<u></u></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">John<u></u><u></u></span>=
</p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d"><u></u>=A0<u></u></span><=
/p>
<p class=3D"MsoNormal"><b><span lang=3D"EN-US" style=3D"font-size:10.0pt;fo=
nt-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;">From:</span></b><span =
lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Tahoma&quot;,&qu=
ot;sans-serif&quot;"> Douglas Arnold [mailto:<a href=3D"mailto:doug.arnold2=
@gmail.com" target=3D"_blank">doug.arnold2@gmail.com</a>]
<br>
<b>Sent:</b> 28 October 2013 20:06<br>
<b>To:</b> John Fletcher</span></p><div><div class=3D"h5"><br>
<b>Cc:</b> <a href=3D"mailto:tictoc@ietf.org" target=3D"_blank">tictoc@ietf=
.org</a><br>
<b>Subject:</b> Re: [TICTOC] Enterprise Profile<u></u><u></u></div></div><p=
></p><div><div class=3D"h5">
<p class=3D"MsoNormal"><u></u>=A0<u></u></p>
<div>
<p class=3D"MsoNormal">Hello John,<u></u><u></u></p>
<div>
<p class=3D"MsoNormal"><u></u>=A0<u></u></p>
</div>
<div>
<p class=3D"MsoNormal">I agree that local time is useful. =A0I would not be=
 averse to creating a TLV to distribute local time offset, so that end node=
 can convert to local time and present it to users.<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><u></u>=A0<u></u></p>
</div>
<div>
<p class=3D"MsoNormal">However, I do not support the idea of using a local =
time epoch in the PTP timestamp fields. This is an allowed option in IEEE 1=
588-2008, but I believe that this is likely to cause interoperability probl=
ems, when some vendors support it
 and others do not.=A0=A0Also some system architechs have indicated that th=
ey deploy PTP across large networks, which span time zones.=A0This is the f=
eature that should be forbidden. =A0<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><u></u>=A0<u></u></p>
</div>
<div>
<p class=3D"MsoNormal">In the NTP standard (RFC5905) the timestamps in the =
packet all use a specific time epoch, and generate all other desired time e=
poch as corrections performed at the end points. =A0Note also that in most =
computer operating systems a single
 standard time epoch is used in and local time is generated at the presenta=
tion layer for human readable interfaces.<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><u></u>=A0<u></u></p>
</div>
<div>
<p class=3D"MsoNormal">Doug<u></u><u></u></p>
</div>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt"><u></u>=A0<u></u></p>
<div>
<p class=3D"MsoNormal">On Mon, Oct 28, 2013 at 8:10 AM, John Fletcher &lt;<=
a href=3D"mailto:John.Fletcher@bbc.co.uk" target=3D"_blank">John.Fletcher@b=
bc.co.uk</a>&gt; wrote:<u></u><u></u></p>
<div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Ta=
homa&quot;,&quot;sans-serif&quot;">I&#39;d also like to ask that you don&#3=
9;t prohibit the Alternate Timescales option. =A0This is potentially useful=
 to distribute &quot;local time&quot; (your time-zone and dst) and there do=
esn&#39;t
 seem to be any need to prohibit it. <u></u><u></u></span></p>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Ta=
homa&quot;,&quot;sans-serif&quot;"><u></u>=A0<u></u></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Ta=
homa&quot;,&quot;sans-serif&quot;">John<u></u><u></u></span></p>
<div>
<div class=3D"MsoNormal" align=3D"center" style=3D"text-align:center">
<hr size=3D"2" width=3D"100%" align=3D"center">
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt"><b><span style=3D"fon=
t-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;">From:</span></b><span s=
tyle=3D"font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;">
<a href=3D"mailto:tictoc-bounces@ietf.org" target=3D"_blank">tictoc-bounces=
@ietf.org</a> [<a href=3D"mailto:tictoc-bounces@ietf.org" target=3D"_blank"=
>tictoc-bounces@ietf.org</a>] on behalf of John Fletcher [<a href=3D"mailto=
:John.Fletcher@bbc.co.uk" target=3D"_blank">John.Fletcher@bbc.co.uk</a>]<br=
>

<b>Sent:</b> 25 October 2013 11:01<br>
<b>To:</b> Douglas Arnold<br>
<b>Cc:</b> <a href=3D"mailto:tictoc@ietf.org" target=3D"_blank">tictoc@ietf=
.org</a><br>
<b>Subject:</b> Re: [TICTOC] Enterprise Profile</span><u></u><u></u></p>
</div>
<div>
<div>
<div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">Doug,</span><u></u><u></u=
></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">=A0</span><u></u><u></u><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">I would be interested to =
know the circumstances when you see the maximum phase adjustment informatio=
n
 being used.</span><u></u><u></u></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">=A0</span><u></u><u></u><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">Some comments:</span><u><=
/u><u></u></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">=A0</span><u></u><u></u><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">In section 6, you say, =
=93In all three of the delay measurement modes=85=94.=A0 At that point in t=
he text
 you have not yet mentioned multicast, hybrid and unicast modes so it=92s n=
ot clear which modes you are referring to.</span><u></u><u></u></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">=A0</span><u></u><u></u><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">In section 9, you say, =
=93Slaves SHOULD NOT Synchronize to a Rogue Master.=94=A0 It=92s not clear =
how a slave
 would know that a master is rogue; presumably it would need to examine the=
 announce messages of all masters and do its own BMCA evaluation.=A0 A more=
 realistic =93rogue=94 master would probably meet the BMCA criteria for sel=
ection.</span><u></u><u></u></p>

<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">=A0</span><u></u><u></u><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">In section 12, =93Alterna=
tive Time Scales=94 should be =93Alternate Timescales=94.</span><u></u><u><=
/u></p>

<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">=A0</span><u></u><u></u><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">=A0</span><u></u><u></u><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">Regards,</span><u></u><u>=
</u></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">John Fletcher</span><u></=
u><u></u></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">=A0</span><u></u><u></u><=
/p>
<p class=3D"MsoNormal"><b><span lang=3D"EN-US" style=3D"font-size:10.0pt;fo=
nt-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;">From:</span></b><span =
lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Tahoma&quot;,&qu=
ot;sans-serif&quot;">
<a href=3D"mailto:tictoc-bounces@ietf.org" target=3D"_blank">tictoc-bounces=
@ietf.org</a> [mailto:<a href=3D"mailto:tictoc-bounces@ietf.org" target=3D"=
_blank">tictoc-bounces@ietf.org</a>]
<b>On Behalf Of </b>Douglas Arnold<br>
<b>Sent:</b> 25 October 2013 01:35<br>
<b>To:</b> <a href=3D"mailto:tictoc@ietf.org" target=3D"_blank">tictoc@ietf=
.org</a><br>
<b>Subject:</b> [TICTOC] Enterprise Profile</span><u></u><u></u></p>
<p class=3D"MsoNormal">=A0<u></u><u></u></p>
<div>
<p class=3D"MsoNormal">Hello Everyone,<u></u><u></u></p>
<div>
<p class=3D"MsoNormal">=A0<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">Attached is an updated version of the Enterprise pro=
file. =A0Sorry I missed the upload deadline for=A0=A0the Vancouver meeting.=
 =A0If you get a chance to look at it before then I will be
 there and would love to discuss it.=A0<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">=A0<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">Summary of changes:<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">=A0<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:9.5pt;font-family:&quot;Ari=
al&quot;,&quot;sans-serif&quot;">I also changed the TLV format to fit the l=
atest proposal in the 1588 revision. =A0</span><u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">=A0<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:9.5pt;font-family:&quot;Ari=
al&quot;,&quot;sans-serif&quot;">I added a statement about not going into t=
he master state unless one had a current UTC offset. =A0</span><u></u><u></=
u></p>

</div>
<div>
<p class=3D"MsoNormal">=A0<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:9.5pt;font-family:&quot;Ari=
al&quot;,&quot;sans-serif&quot;">I added to the TLV fields to indicate maxi=
mum phase correction over a sync cycle.</span><u></u><u></u></p>
</div>
<div>
<div>
<p class=3D"MsoNormal">=A0<u></u><u></u></p>
</div>
<p class=3D"MsoNormal">--
<u></u><u></u></p>
<div>
<p class=3D"MsoNormal">Doug Arnold<u></u><u></u></p>
<div>
<p class=3D"MsoNormal">Principal Technologist<u></u><u></u></p>
<div>
<p class=3D"MsoNormal"><i>JTime!</i>=A0Meinberg USA<u></u><u></u></p>
</div>
</div>
<div>
<p class=3D"MsoNormal"><a href=3D"tel:%2B1-707-303-5559" target=3D"_blank">=
+1-707-303-5559</a><u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">=A0<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">=A0<u></u><u></u></p>
</div>
</div>
</div>
</div>
</div>
<p>=A0<u></u><u></u></p>
<p>----------------------------<br>
<br>
<a href=3D"http://www.bbc.co.uk" target=3D"_blank">http://www.bbc.co.uk</a>=
<br>
This e-mail (and any attachments) is confidential and may contain personal =
views which are not the views of the BBC unless specifically stated.<br>
If you have received it in error, please delete it from your system.<br>
Do not use, copy or disclose the information in any way nor act in reliance=
 on it and notify the sender immediately.<br>
Please note that the BBC monitors e-mails sent or received.<br>
Further communication will signify your consent to this.<u></u><u></u></p>
<p>---------------------<u></u><u></u></p>
</div>
</div>
</div>
</div>
</div>
</div>
<div>
<div>
<p>=A0<u></u><u></u></p>
<p>----------------------------<br>
<br>
<a href=3D"http://www.bbc.co.uk" target=3D"_blank">http://www.bbc.co.uk</a>=
<br>
This e-mail (and any attachments) is confidential and may contain personal =
views which are not the views of the BBC unless specifically stated.<br>
If you have received it in error, please delete it from your system.<br>
Do not use, copy or disclose the information in any way nor act in reliance=
 on it and notify the sender immediately.<br>
Please note that the BBC monitors e-mails sent or received.<br>
Further communication will signify your consent to this.<u></u><u></u></p>
<p>---------------------<u></u><u></u></p>
</div>
</div>
</div>
</div>
<p class=3D"MsoNormal"><br>
<br clear=3D"all">
<u></u><u></u></p>
<div>
<p class=3D"MsoNormal"><u></u>=A0<u></u></p>
</div>
<p class=3D"MsoNormal">-- <u></u><u></u></p>
<div>
<p class=3D"MsoNormal">Doug<u></u><u></u></p>
</div>
</div>
</div></div></div>
</div>

</blockquote></div><br></div>

--047d7bf198e0fe711d04e9e319f7--

From John.Fletcher@bbc.co.uk  Thu Oct 31 08:28:59 2013
Return-Path: <John.Fletcher@bbc.co.uk>
X-Original-To: tictoc@ietfa.amsl.com
Delivered-To: tictoc@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DD4EA21F9FAB for <tictoc@ietfa.amsl.com>; Thu, 31 Oct 2013 08:28:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.25
X-Spam-Level: 
X-Spam-Status: No, score=-9.25 tagged_above=-999 required=5 tests=[AWL=1.348,  BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id J3SSHZ4hFdwi for <tictoc@ietfa.amsl.com>; Thu, 31 Oct 2013 08:28:55 -0700 (PDT)
Received: from mailout1.thls.bbc.co.uk (mailout1.thls.bbc.co.uk [132.185.240.36]) by ietfa.amsl.com (Postfix) with ESMTP id D96D621F9DAF for <tictoc@ietf.org>; Thu, 31 Oct 2013 08:28:54 -0700 (PDT)
Received: from BGB01XI1012.national.core.bbc.co.uk (bgb01xi1012.national.core.bbc.co.uk [10.161.14.16]) by mailout1.thls.bbc.co.uk (8.14.4/8.14.3) with ESMTP id r9VFSlhO017805; Thu, 31 Oct 2013 15:28:47 GMT
Received: from BGB01XUD1011.national.core.bbc.co.uk ([169.254.10.4]) by BGB01XI1012.national.core.bbc.co.uk ([10.161.14.16]) with mapi id 14.02.0342.004; Thu, 31 Oct 2013 15:28:47 +0000
From: John Fletcher <John.Fletcher@bbc.co.uk>
To: "'Kevin Gross'" <kevin.gross@avanw.com>
Thread-Topic: [TICTOC] Enterprise Profile
Thread-Index: AQHO0Tj+EfJkN9q+/USLYOoP7dIkB5oFJTNggAUWS6GAAFQ5gIAA6iNAgABfZYCAAxt4EA==
Date: Thu, 31 Oct 2013 15:28:46 +0000
Message-ID: <B1D49063AD5FBD4688F3EEDEC68B20175115B33B@BGB01XUD1011.national.core.bbc.co.uk>
References: <CACQYgzFmOtFY+Td0jZMyykeZ17KwAuCc+LY+C2be_UPgZKh9GA@mail.gmail.com> <B1D49063AD5FBD4688F3EEDEC68B201751132BDF@BGB01XUD1002.national.core.bbc.co.uk> <B1D49063AD5FBD4688F3EEDEC68B20175113E0AA@BGB01XUD1011.national.core.bbc.co.uk> <CACQYgzEEcZPLEBgyTPUyqYbRjNi_7oFvm7TVxhGthQL-hx6nYA@mail.gmail.com> <B1D49063AD5FBD4688F3EEDEC68B20175114537C@BGB01XUD1011.national.core.bbc.co.uk> <CALw1_Q10rT9eyh40Udk1NQLHbREPPtxPSTYQ9GFKhZdeD7-EqA@mail.gmail.com>
In-Reply-To: <CALw1_Q10rT9eyh40Udk1NQLHbREPPtxPSTYQ9GFKhZdeD7-EqA@mail.gmail.com>
Accept-Language: en-GB, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.162.14.18]
x-exclaimer-md-config: 1cd3ac1c-62e5-43f2-8404-6b688271c769
Content-Type: multipart/alternative; boundary="_000_B1D49063AD5FBD4688F3EEDEC68B20175115B33BBGB01XUD1011nat_"
MIME-Version: 1.0
Cc: Douglas Arnold <doug.arnold2@gmail.com>, "tictoc@ietf.org" <tictoc@ietf.org>
Subject: Re: [TICTOC] Enterprise Profile
X-BeenThere: tictoc@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Timing over IP Connection and Transfer of Clock BOF <tictoc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tictoc>, <mailto:tictoc-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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>
X-List-Received-Date: Thu, 31 Oct 2013 15:29:00 -0000

--_000_B1D49063AD5FBD4688F3EEDEC68B20175115B33BBGB01XUD1011nat_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Hi Kevin,

Well, I think it already accepted that there are applications where it is u=
seful to know the local time.  Generating SMPTE Timecode is one that you kn=
ow about.

>From Doug's comment, I'm not clear if he wanted to prohibit something diffe=
rent, i.e. using an ARB timescale to represent local time.  I'm happy to pr=
ohibit that but I would like to see the Alternate Timescales TLV of section=
 16.3 allowed - not required, just allowed.

How can the endstation know which is the correct local time?  Most likely u=
se case is that the PTP deployment is designed so that masters do not serve=
 more than one timezone.  Failing that, it could be user selection based on=
 the name of the alternate timescale.

Yes, you can route multicast messages beyond a subnet but many network admi=
nistrators, e.g. in my own company's enterprise network, choose not to allo=
w that, especially for "Any Source Multicast" as used by 1588.

John

From: Kevin Gross [mailto:kevin.gross@avanw.com]
Sent: 29 October 2013 15:45
To: John Fletcher
Cc: Douglas Arnold; tictoc@ietf.org
Subject: Re: [TICTOC] Enterprise Profile

Multicast IP routing allows multicast messaging beyond a subnet. Multicast =
IP routing is not available over the internet but it is now fairly common o=
n enterprise networks.

John, can you describe a use case for alternate timescales and explain how =
the endstation can know that the timescale is correct local time or which a=
lternate timescale to use if there are multiple?

Kevin Gross
+1-303-447-0517
Media Network Consultant
AVA Networks - www.AVAnw.com<http://www.avanw.com/>

On Tue, Oct 29, 2013 at 4:18 AM, John Fletcher <John.Fletcher@bbc.co.uk<mai=
lto:John.Fletcher@bbc.co.uk>> wrote:
Just to be clear, I am not suggesting use of a different epoch in timestamp=
 fields.  I am talking about the optional TLV described in section 16.3 whi=
ch can give you the offset(s) between PTP time and one or more timescales o=
f your choice.

Regarding spanning timezones, there is a difference between the extent of t=
he enterprise network and the extent of the part of network served by a PTP=
 master.  The latter is probably a subnet since multicast messages (e.g. An=
nounce) are usually confined to a subnet.  A subnet spanning multiple timez=
ones would be less common.  However you can have more than one Alternate Ti=
mescale if necessary.

This feature is just an option; I'm not suggesting it be required, just tha=
t it not be forbidden.

John

From: Douglas Arnold [mailto:doug.arnold2@gmail.com<mailto:doug.arnold2@gma=
il.com>]
Sent: 28 October 2013 20:06
To: John Fletcher

Cc: tictoc@ietf.org<mailto:tictoc@ietf.org>
Subject: Re: [TICTOC] Enterprise Profile

Hello John,

I agree that local time is useful.  I would not be averse to creating a TLV=
 to distribute local time offset, so that end node can convert to local tim=
e and present it to users.

However, I do not support the idea of using a local time epoch in the PTP t=
imestamp fields. This is an allowed option in IEEE 1588-2008, but I believe=
 that this is likely to cause interoperability problems, when some vendors =
support it and others do not.  Also some system architechs have indicated t=
hat they deploy PTP across large networks, which span time zones. This is t=
he feature that should be forbidden.

In the NTP standard (RFC5905) the timestamps in the packet all use a specif=
ic time epoch, and generate all other desired time epoch as corrections per=
formed at the end points.  Note also that in most computer operating system=
s a single standard time epoch is used in and local time is generated at th=
e presentation layer for human readable interfaces.

Doug

On Mon, Oct 28, 2013 at 8:10 AM, John Fletcher <John.Fletcher@bbc.co.uk<mai=
lto:John.Fletcher@bbc.co.uk>> wrote:
I'd also like to ask that you don't prohibit the Alternate Timescales optio=
n.  This is potentially useful to distribute "local time" (your time-zone a=
nd dst) and there doesn't seem to be any need to prohibit it.

John
________________________________
From: tictoc-bounces@ietf.org<mailto:tictoc-bounces@ietf.org> [tictoc-bounc=
es@ietf.org<mailto:tictoc-bounces@ietf.org>] on behalf of John Fletcher [Jo=
hn.Fletcher@bbc.co.uk<mailto:John.Fletcher@bbc.co.uk>]
Sent: 25 October 2013 11:01
To: Douglas Arnold
Cc: tictoc@ietf.org<mailto:tictoc@ietf.org>
Subject: Re: [TICTOC] Enterprise Profile
Doug,

I would be interested to know the circumstances when you see the maximum ph=
ase adjustment information being used.

Some comments:

In section 6, you say, "In all three of the delay measurement modes...".  A=
t that point in the text you have not yet mentioned multicast, hybrid and u=
nicast modes so it's not clear which modes you are referring to.

In section 9, you say, "Slaves SHOULD NOT Synchronize to a Rogue Master."  =
It's not clear how a slave would know that a master is rogue; presumably it=
 would need to examine the announce messages of all masters and do its own =
BMCA evaluation.  A more realistic "rogue" master would probably meet the B=
MCA criteria for selection.

In section 12, "Alternative Time Scales" should be "Alternate Timescales".


Regards,
John Fletcher

From: tictoc-bounces@ietf.org<mailto:tictoc-bounces@ietf.org> [mailto:ticto=
c-bounces@ietf.org<mailto:tictoc-bounces@ietf.org>] On Behalf Of Douglas Ar=
nold
Sent: 25 October 2013 01:35
To: tictoc@ietf.org<mailto:tictoc@ietf.org>
Subject: [TICTOC] Enterprise Profile

Hello Everyone,

Attached is an updated version of the Enterprise profile.  Sorry I missed t=
he upload deadline for  the Vancouver meeting.  If you get a chance to look=
 at it before then I will be there and would love to discuss it.

Summary of changes:

I also changed the TLV format to fit the latest proposal in the 1588 revisi=
on.

I added a statement about not going into the master state unless one had a =
current UTC offset.

I added to the TLV fields to indicate maximum phase correction over a sync =
cycle.

--
Doug Arnold
Principal Technologist
JTime! Meinberg USA
+1-707-303-5559<tel:%2B1-707-303-5559>





----------------------------

http://www.bbc.co.uk
This e-mail (and any attachments) is confidential and may contain personal =
views which are not the views of the BBC unless specifically stated.
If you have received it in error, please delete it from your system.
Do not use, copy or disclose the information in any way nor act in reliance=
 on it and notify the sender immediately.
Please note that the BBC monitors e-mails sent or received.
Further communication will signify your consent to this.

---------------------



----------------------------

http://www.bbc.co.uk
This e-mail (and any attachments) is confidential and may contain personal =
views which are not the views of the BBC unless specifically stated.
If you have received it in error, please delete it from your system.
Do not use, copy or disclose the information in any way nor act in reliance=
 on it and notify the sender immediately.
Please note that the BBC monitors e-mails sent or received.
Further communication will signify your consent to this.

---------------------



--
Doug


--_000_B1D49063AD5FBD4688F3EEDEC68B20175115B33BBGB01XUD1011nat_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
<meta name=3D"Generator" content=3D"Microsoft Word 14 (filtered medium)">
<!--[if !mso]><style>v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style><![endif]--><style><!--
/* Font Definitions */
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
p
	{mso-style-priority:99;
	mso-margin-top-alt:auto;
	margin-right:0cm;
	mso-margin-bottom-alt:auto;
	margin-left:0cm;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
	{mso-style-priority:99;
	mso-style-link:"Balloon Text Char";
	margin:0cm;
	margin-bottom:.0001pt;
	font-size:8.0pt;
	font-family:"Tahoma","sans-serif";}
span.BalloonTextChar
	{mso-style-name:"Balloon Text Char";
	mso-style-priority:99;
	mso-style-link:"Balloon Text";
	font-family:"Tahoma","sans-serif";
	mso-fareast-language:EN-GB;}
span.EmailStyle20
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-family:"Calibri","sans-serif";
	mso-fareast-language:EN-US;}
@page WordSection1
	{size:612.0pt 792.0pt;
	margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=3D"EN-GB" link=3D"blue" vlink=3D"purple">
<div class=3D"WordSection1">
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">Hi Kevin,<o:p></o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">Well, I think it already =
accepted that there are applications where it is useful to know the local t=
ime.&nbsp; Generating SMPTE Timecode is one that you know about.<o:p></o:p>=
</span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">From Doug&#8217;s comment=
, I&#8217;m not clear if he wanted to prohibit something different, i.e. us=
ing an ARB timescale to represent local time.&nbsp; I&#8217;m happy to proh=
ibit
 that but I would like to see the Alternate Timescales TLV of section 16.3 =
allowed &#8211; not required, just allowed.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">How can the endstation kn=
ow which is the correct local time?&nbsp; Most likely use case is that the =
PTP deployment is designed so that masters do not serve more
 than one timezone.&nbsp; Failing that, it could be user selection based on=
 the name of the alternate timescale.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">Yes, you can route multic=
ast messages beyond a subnet but many network administrators, e.g. in my ow=
n company&#8217;s enterprise network, choose not to allow that,
 especially for &#8220;Any Source Multicast&#8221; as used by 1588.<o:p></o=
:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">John<o:p></o:p></span></p=
>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<p class=3D"MsoNormal"><b><span lang=3D"EN-US" style=3D"font-size:10.0pt;fo=
nt-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;">From:</span></b><span =
lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Tahoma&quot;,&qu=
ot;sans-serif&quot;"> Kevin Gross [mailto:kevin.gross@avanw.com]
<br>
<b>Sent:</b> 29 October 2013 15:45<br>
<b>To:</b> John Fletcher<br>
<b>Cc:</b> Douglas Arnold; tictoc@ietf.org<br>
<b>Subject:</b> Re: [TICTOC] Enterprise Profile<o:p></o:p></span></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<div>
<p class=3D"MsoNormal">Multicast IP routing allows multicast messaging beyo=
nd a subnet. Multicast IP routing is not available over the internet but it=
 is now fairly common on enterprise networks.<o:p></o:p></p>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<div>
<p class=3D"MsoNormal">John, can you describe a use case for alternate time=
scales and explain how the endstation can know that the timescale is correc=
t local time or which alternate timescale to use if there are multiple?<o:p=
></o:p></p>
</div>
</div>
<div>
<p class=3D"MsoNormal"><br clear=3D"all">
<o:p></o:p></p>
<div>
<div>
<p class=3D"MsoNormal">Kevin Gross<o:p></o:p></p>
<div>
<p class=3D"MsoNormal">&#43;1-303-447-0517<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal">Media Network Consultant<o:p></o:p></p>
<div>
<p class=3D"MsoNormal">AVA Networks -&nbsp;<a href=3D"http://www.avanw.com/=
" target=3D"_blank">www.AVAnw.com</a><o:p></o:p></p>
</div>
</div>
</div>
</div>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt"><o:p>&nbsp;</o:p></p>
<div>
<p class=3D"MsoNormal">On Tue, Oct 29, 2013 at 4:18 AM, John Fletcher &lt;<=
a href=3D"mailto:John.Fletcher@bbc.co.uk" target=3D"_blank">John.Fletcher@b=
bc.co.uk</a>&gt; wrote:<o:p></o:p></p>
<div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:#1F497D">Just to be clear, I am not suggesting u=
se of a different epoch in timestamp fields.&nbsp; I am talking
 about the optional TLV described in section 16.3 which can give you the of=
fset(s) between PTP time and one or more timescales of your choice.</span><=
o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:#1F497D">&nbsp;</span><o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:#1F497D">Regarding spanning timezones, there is =
a difference between the extent of the enterprise network
 and the extent of the part of network served by a PTP master.&nbsp; The la=
tter is probably a subnet since multicast messages (e.g. Announce) are usua=
lly confined to a subnet.&nbsp; A subnet spanning multiple timezones would =
be less common.&nbsp; However you can have more
 than one Alternate Timescale if necessary.</span><o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:#1F497D">&nbsp;</span><o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:#1F497D">This feature is just an option; I&#8217=
;m not suggesting it be required, just that it not be forbidden.</span><o:p=
></o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:#1F497D">&nbsp;</span><o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:#1F497D">John</span><o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:#1F497D">&nbsp;</span><o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><b><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quo=
t;Tahoma&quot;,&quot;sans-serif&quot;">From:</span></b><span lang=3D"EN-US"=
 style=3D"font-size:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&=
quot;"> Douglas
 Arnold [mailto:<a href=3D"mailto:doug.arnold2@gmail.com" target=3D"_blank"=
>doug.arnold2@gmail.com</a>]
<br>
<b>Sent:</b> 28 October 2013 20:06<br>
<b>To:</b> John Fletcher</span><o:p></o:p></p>
<div>
<div>
<p class=3D"MsoNormal"><br>
<b>Cc:</b> <a href=3D"mailto:tictoc@ietf.org" target=3D"_blank">tictoc@ietf=
.org</a><br>
<b>Subject:</b> Re: [TICTOC] Enterprise Profile<o:p></o:p></p>
</div>
</div>
<div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">&nbsp;<o:p></o:p></p>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">Hello John,<o:p></o:p></p>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">&nbsp;<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">I agree that local time is useful. &nbsp;I would not be averse to =
creating a TLV to distribute local time offset, so that end node can conver=
t to local time and present it to users.<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">&nbsp;<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">However, I do not support the idea of using a local time epoch in =
the PTP timestamp fields. This is an allowed option in IEEE 1588-2008, but =
I believe that this is likely to cause
 interoperability problems, when some vendors support it and others do not.=
&nbsp;&nbsp;Also some system architechs have indicated that they deploy PTP=
 across large networks, which span time zones.&nbsp;This is the feature tha=
t should be forbidden. &nbsp;<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">&nbsp;<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">In the NTP standard (RFC5905) the timestamps in the packet all use=
 a specific time epoch, and generate all other desired time epoch as correc=
tions performed at the end points. &nbsp;Note
 also that in most computer operating systems a single standard time epoch =
is used in and local time is generated at the presentation layer for human =
readable interfaces.<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">&nbsp;<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">Doug<o:p></o:p></p>
</div>
</div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;margin-bottom:12.0p=
t">&nbsp;<o:p></o:p></p>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">On Mon, Oct 28, 2013 at 8:10 AM, John Fletcher &lt;<a href=3D"mail=
to:John.Fletcher@bbc.co.uk" target=3D"_blank">John.Fletcher@bbc.co.uk</a>&g=
t; wrote:<o:p></o:p></p>
<div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:10.0pt;font-family:&quot;Tahoma&quot;,&qu=
ot;sans-serif&quot;">I'd also like to ask that you don't prohibit the Alter=
nate Timescales option. &nbsp;This is potentially useful to distribute
 &quot;local time&quot; (your time-zone and dst) and there doesn't seem to =
be any need to prohibit it.
</span><o:p></o:p></p>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:10.0pt;font-family:&quot;Tahoma&quot;,&qu=
ot;sans-serif&quot;">&nbsp;</span><o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:10.0pt;font-family:&quot;Tahoma&quot;,&qu=
ot;sans-serif&quot;">John</span><o:p></o:p></p>
<div>
<div class=3D"MsoNormal" align=3D"center" style=3D"text-align:center">
<hr size=3D"2" width=3D"100%" align=3D"center">
</div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;margin-bottom:12.0p=
t"><b><span style=3D"font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;"=
>From:</span></b><span style=3D"font-family:&quot;Tahoma&quot;,&quot;sans-s=
erif&quot;">
<a href=3D"mailto:tictoc-bounces@ietf.org" target=3D"_blank">tictoc-bounces=
@ietf.org</a> [<a href=3D"mailto:tictoc-bounces@ietf.org" target=3D"_blank"=
>tictoc-bounces@ietf.org</a>] on behalf of John Fletcher [<a href=3D"mailto=
:John.Fletcher@bbc.co.uk" target=3D"_blank">John.Fletcher@bbc.co.uk</a>]<br=
>
<b>Sent:</b> 25 October 2013 11:01<br>
<b>To:</b> Douglas Arnold<br>
<b>Cc:</b> <a href=3D"mailto:tictoc@ietf.org" target=3D"_blank">tictoc@ietf=
.org</a><br>
<b>Subject:</b> Re: [TICTOC] Enterprise Profile</span><o:p></o:p></p>
</div>
<div>
<div>
<div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:#1F497D">Doug,</span><o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:#1F497D">&nbsp;</span><o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:#1F497D">I would be interested to know the circu=
mstances when you see the maximum phase adjustment information
 being used.</span><o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:#1F497D">&nbsp;</span><o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:#1F497D">Some comments:</span><o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:#1F497D">&nbsp;</span><o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:#1F497D">In section 6, you say, &#8220;In all th=
ree of the delay measurement modes&#8230;&#8221;.&nbsp; At that point in th=
e text
 you have not yet mentioned multicast, hybrid and unicast modes so it&#8217=
;s not clear which modes you are referring to.</span><o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:#1F497D">&nbsp;</span><o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:#1F497D">In section 9, you say, &#8220;Slaves SH=
OULD NOT Synchronize to a Rogue Master.&#8221;&nbsp; It&#8217;s not clear h=
ow a slave
 would know that a master is rogue; presumably it would need to examine the=
 announce messages of all masters and do its own BMCA evaluation.&nbsp; A m=
ore realistic &#8220;rogue&#8221; master would probably meet the BMCA crite=
ria for selection.</span><o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:#1F497D">&nbsp;</span><o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:#1F497D">In section 12, &#8220;Alternative Time =
Scales&#8221; should be &#8220;Alternate Timescales&#8221;.</span><o:p></o:=
p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:#1F497D">&nbsp;</span><o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:#1F497D">&nbsp;</span><o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:#1F497D">Regards,</span><o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:#1F497D">John Fletcher</span><o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:#1F497D">&nbsp;</span><o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><b><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quo=
t;Tahoma&quot;,&quot;sans-serif&quot;">From:</span></b><span lang=3D"EN-US"=
 style=3D"font-size:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&=
quot;">
<a href=3D"mailto:tictoc-bounces@ietf.org" target=3D"_blank">tictoc-bounces=
@ietf.org</a> [mailto:<a href=3D"mailto:tictoc-bounces@ietf.org" target=3D"=
_blank">tictoc-bounces@ietf.org</a>]
<b>On Behalf Of </b>Douglas Arnold<br>
<b>Sent:</b> 25 October 2013 01:35<br>
<b>To:</b> <a href=3D"mailto:tictoc@ietf.org" target=3D"_blank">tictoc@ietf=
.org</a><br>
<b>Subject:</b> [TICTOC] Enterprise Profile</span><o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">&nbsp;<o:p></o:p></p>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">Hello Everyone,<o:p></o:p></p>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">&nbsp;<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">Attached is an updated version of the Enterprise profile. &nbsp;So=
rry I missed the upload deadline for&nbsp;&nbsp;the Vancouver meeting. &nbs=
p;If you get a chance to look at it before then I will be
 there and would love to discuss it.&nbsp;<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">&nbsp;<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">Summary of changes:<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">&nbsp;<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:9.5pt;font-family:&quot;Arial&quot;,&quot=
;sans-serif&quot;">I also changed the TLV format to fit the latest proposal=
 in the 1588 revision. &nbsp;</span><o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">&nbsp;<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:9.5pt;font-family:&quot;Arial&quot;,&quot=
;sans-serif&quot;">I added a statement about not going into the master stat=
e unless one had a current UTC offset. &nbsp;</span><o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">&nbsp;<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:9.5pt;font-family:&quot;Arial&quot;,&quot=
;sans-serif&quot;">I added to the TLV fields to indicate maximum phase corr=
ection over a sync cycle.</span><o:p></o:p></p>
</div>
<div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">&nbsp;<o:p></o:p></p>
</div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">--
<o:p></o:p></p>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">Doug Arnold<o:p></o:p></p>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">Principal Technologist<o:p></o:p></p>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><i>JTime!</i>&nbsp;Meinberg USA<o:p></o:p></p>
</div>
</div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><a href=3D"tel:%2B1-707-303-5559" target=3D"_blank">&#43;1-707-303=
-5559</a><o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">&nbsp;<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">&nbsp;<o:p></o:p></p>
</div>
</div>
</div>
</div>
</div>
<p>&nbsp;<o:p></o:p></p>
<p>----------------------------<br>
<br>
<a href=3D"http://www.bbc.co.uk" target=3D"_blank">http://www.bbc.co.uk</a>=
<br>
This e-mail (and any attachments) is confidential and may contain personal =
views which are not the views of the BBC unless specifically stated.<br>
If you have received it in error, please delete it from your system.<br>
Do not use, copy or disclose the information in any way nor act in reliance=
 on it and notify the sender immediately.<br>
Please note that the BBC monitors e-mails sent or received.<br>
Further communication will signify your consent to this.<o:p></o:p></p>
<p>---------------------<o:p></o:p></p>
</div>
</div>
</div>
</div>
</div>
</div>
<div>
<div>
<p>&nbsp;<o:p></o:p></p>
<p>----------------------------<br>
<br>
<a href=3D"http://www.bbc.co.uk" target=3D"_blank">http://www.bbc.co.uk</a>=
<br>
This e-mail (and any attachments) is confidential and may contain personal =
views which are not the views of the BBC unless specifically stated.<br>
If you have received it in error, please delete it from your system.<br>
Do not use, copy or disclose the information in any way nor act in reliance=
 on it and notify the sender immediately.<br>
Please note that the BBC monitors e-mails sent or received.<br>
Further communication will signify your consent to this.<o:p></o:p></p>
<p>---------------------<o:p></o:p></p>
</div>
</div>
</div>
</div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><br>
<br clear=3D"all">
<o:p></o:p></p>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">&nbsp;<o:p></o:p></p>
</div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">--
<o:p></o:p></p>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">Doug<o:p></o:p></p>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
</div>
</body>
</html>

--_000_B1D49063AD5FBD4688F3EEDEC68B20175115B33BBGB01XUD1011nat_--

From kevin.gross@avanw.com  Thu Oct 31 13:57:09 2013
Return-Path: <kevin.gross@avanw.com>
X-Original-To: tictoc@ietfa.amsl.com
Delivered-To: tictoc@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5574811E81B9 for <tictoc@ietfa.amsl.com>; Thu, 31 Oct 2013 13:57:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.782
X-Spam-Level: 
X-Spam-Status: No, score=0.782 tagged_above=-999 required=5 tests=[AWL=0.596,  BAYES_00=-2.599, FH_RELAY_NODNS=1.451, FM_FORGED_GMAIL=0.622, HELO_MISMATCH_NET=0.611, HTML_MESSAGE=0.001, RDNS_NONE=0.1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id wzxb0+KAxwOP for <tictoc@ietfa.amsl.com>; Thu, 31 Oct 2013 13:57:03 -0700 (PDT)
Received: from qmta02.westchester.pa.mail.comcast.net (qmta02.westchester.pa.mail.comcast.net [IPv6:2001:558:fe14:43:76:96:62:24]) by ietfa.amsl.com (Postfix) with ESMTP id DA9B611E826F for <tictoc@ietf.org>; Thu, 31 Oct 2013 13:56:57 -0700 (PDT)
Received: from omta12.westchester.pa.mail.comcast.net ([76.96.62.44]) by qmta02.westchester.pa.mail.comcast.net with comcast id jnx71m0030xGWP851wwvWe; Thu, 31 Oct 2013 20:56:55 +0000
Received: from mail-wi0-x22e.google.com ([IPv6:2a00:1450:400c:c05::22e]) by omta12.westchester.pa.mail.comcast.net with comcast id jwwu1m00C0mcyYt3YwwvNE; Thu, 31 Oct 2013 20:56:55 +0000
Received: by mail-wi0-f174.google.com with SMTP id cb5so292685wib.1 for <tictoc@ietf.org>; Thu, 31 Oct 2013 13:56:54 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=az/wfvcUkAwJbM3MKRjJKcuC1Fc4NvNgvuAwsnr3FcU=; b=VYHWfWqUaNXTxqq9X4WpcT+X9b0IoNd57YSmu8xkrSxCiZOPVTeAmdV447jSuBcXRl pdxdDRgKrkU28iSSNR26z+0twac34Qqh3zqyszdpL2nnYapdk8KUm/1/SccQwhxKkFrq kkpPyTVNEQhAxI6qbc4WrBp5q8PGuBYmTbwX+WNspW+81LFQt65KsIIc456rWVp8sHnp FJZWDaNcsCorBud6MDZJ8MzERQAUY9N+lMbQHOZpxJdlQz1M9kKBhfYTZcN5xcrKJYnC kr8ufsaUlakLXZNvQEMVYnPXNHB0WG7nF7oKz4w6wYpfsjmwP2ZDYDnRx2ToCpfzJwdL bYHA==
MIME-Version: 1.0
X-Received: by 10.180.212.51 with SMTP id nh19mr1104237wic.52.1383253014092; Thu, 31 Oct 2013 13:56:54 -0700 (PDT)
Received: by 10.216.202.7 with HTTP; Thu, 31 Oct 2013 13:56:54 -0700 (PDT)
In-Reply-To: <B1D49063AD5FBD4688F3EEDEC68B20175115B33B@BGB01XUD1011.national.core.bbc.co.uk>
References: <CACQYgzFmOtFY+Td0jZMyykeZ17KwAuCc+LY+C2be_UPgZKh9GA@mail.gmail.com> <B1D49063AD5FBD4688F3EEDEC68B201751132BDF@BGB01XUD1002.national.core.bbc.co.uk> <B1D49063AD5FBD4688F3EEDEC68B20175113E0AA@BGB01XUD1011.national.core.bbc.co.uk> <CACQYgzEEcZPLEBgyTPUyqYbRjNi_7oFvm7TVxhGthQL-hx6nYA@mail.gmail.com> <B1D49063AD5FBD4688F3EEDEC68B20175114537C@BGB01XUD1011.national.core.bbc.co.uk> <CALw1_Q10rT9eyh40Udk1NQLHbREPPtxPSTYQ9GFKhZdeD7-EqA@mail.gmail.com> <B1D49063AD5FBD4688F3EEDEC68B20175115B33B@BGB01XUD1011.national.core.bbc.co.uk>
Date: Thu, 31 Oct 2013 14:56:54 -0600
Message-ID: <CALw1_Q1VC=3Jdvjhzj_ctNZVqvhebnhosGfVgmbEPi-FqBGxPA@mail.gmail.com>
From: Kevin Gross <kevin.gross@avanw.com>
To: John Fletcher <John.Fletcher@bbc.co.uk>
Content-Type: multipart/alternative; boundary=001a11c357608a23f604ea0fb06e
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20121106; t=1383253015; bh=az/wfvcUkAwJbM3MKRjJKcuC1Fc4NvNgvuAwsnr3FcU=; h=Received:Received:Received:MIME-Version:Received:Date:Message-ID: Subject:From:To:Content-Type; b=PDZJafYHtqr9dsRvBFpjgH/jsTNINXER+Q8FCFCafJ1sei1OpuZiXMvZZwwuMMT5k jJJgJVQDuEvY7ocDTOt3NQq8qAf5HN68/APQRLiaQWs/y3hru5CIYiJcMBDlKBTVbk HumTnp6v3Jw5gN5ptMDMTnSF8CUd6eVlZB2eQMca/mh90yHS8toJp/gnVcvg4DMKtV 9dkykGSeG3QCFVhySQHgkB7s5w9ccdhOgV6O0G/yTgqKOSPycu0g895Odm+OlN96+8 3Hc7oS+cJtkaHrdvwz/Q0hm4R97wG+apF/WAyIIcVfm5A3hVj/oX+XMYpmK0yi5E4D 1bUprx2dHBFew==
Cc: Douglas Arnold <doug.arnold2@gmail.com>, "tictoc@ietf.org" <tictoc@ietf.org>
Subject: Re: [TICTOC] Enterprise Profile
X-BeenThere: tictoc@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Timing over IP Connection and Transfer of Clock BOF <tictoc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tictoc>, <mailto:tictoc-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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>
X-List-Received-Date: Thu, 31 Oct 2013 20:57:09 -0000

--001a11c357608a23f604ea0fb06e
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: quoted-printable

So the use case would be timecode distribution in a broadcast facility
where multicast routing is administratively confined to the facility. Sound
reasonable.

I think that the reason alternate timescales are not included in the
enterprise profile is that the enterprise profile is trying to do things
the NTP way. NTP does not know about timezones; that is left up to the
individual workstations to sort out.

I expect your argument for allowing it that systems that wish to continue
to operate in this way can simply ignore the alternate timescale and even
if there is a disagreement about what the local time is, they're no worse
off than they currently are.

Kevin Gross
+1-303-447-0517
Media Network Consultant
AVA Networks - www.AVAnw.com <http://www.avanw.com/>


On Thu, Oct 31, 2013 at 9:28 AM, John Fletcher <John.Fletcher@bbc.co.uk>wro=
te:

>  Hi Kevin,****
>
> ** **
>
> Well, I think it already accepted that there are applications where it is
> useful to know the local time.  Generating SMPTE Timecode is one that you
> know about.****
>
> ** **
>
> From Doug=92s comment, I=92m not clear if he wanted to prohibit something
> different, i.e. using an ARB timescale to represent local time.  I=92m ha=
ppy
> to prohibit that but I would like to see the Alternate Timescales TLV of
> section 16.3 allowed =96 not required, just allowed.****
>
> ** **
>
> How can the endstation know which is the correct local time?  Most likely
> use case is that the PTP deployment is designed so that masters do not
> serve more than one timezone.  Failing that, it could be user selection
> based on the name of the alternate timescale.****
>
> ** **
>
> Yes, you can route multicast messages beyond a subnet but many network
> administrators, e.g. in my own company=92s enterprise network, choose not=
 to
> allow that, especially for =93Any Source Multicast=94 as used by 1588.***=
*
>
> ** **
>
> John****
>
> ** **
>
> *From:* Kevin Gross [mailto:kevin.gross@avanw.com]
> *Sent:* 29 October 2013 15:45
> *To:* John Fletcher
> *Cc:* Douglas Arnold; tictoc@ietf.org
>
> *Subject:* Re: [TICTOC] Enterprise Profile****
>
> ** **
>
> Multicast IP routing allows multicast messaging beyond a subnet. Multicas=
t
> IP routing is not available over the internet but it is now fairly common
> on enterprise networks.****
>
> ** **
>
> John, can you describe a use case for alternate timescales and explain ho=
w
> the endstation can know that the timescale is correct local time or which
> alternate timescale to use if there are multiple?****
>
>
> ****
>
> Kevin Gross****
>
> +1-303-447-0517****
>
> Media Network Consultant****
>
> AVA Networks - www.AVAnw.com <http://www.avanw.com/>****
>
> ** **
>
> On Tue, Oct 29, 2013 at 4:18 AM, John Fletcher <John.Fletcher@bbc.co.uk>
> wrote:****
>
> Just to be clear, I am not suggesting use of a different epoch in
> timestamp fields.  I am talking about the optional TLV described in secti=
on
> 16.3 which can give you the offset(s) between PTP time and one or more
> timescales of your choice.****
>
>  ****
>
> Regarding spanning timezones, there is a difference between the extent of
> the enterprise network and the extent of the part of network served by a
> PTP master.  The latter is probably a subnet since multicast messages (e.=
g.
> Announce) are usually confined to a subnet.  A subnet spanning multiple
> timezones would be less common.  However you can have more than one
> Alternate Timescale if necessary.****
>
>  ****
>
> This feature is just an option; I=92m not suggesting it be required, just
> that it not be forbidden.****
>
>  ****
>
> John****
>
>  ****
>
> *From:* Douglas Arnold [mailto:doug.arnold2@gmail.com]
> *Sent:* 28 October 2013 20:06
> *To:* John Fletcher****
>
>
> *Cc:* tictoc@ietf.org
> *Subject:* Re: [TICTOC] Enterprise Profile****
>
>  ****
>
> Hello John,****
>
>  ****
>
> I agree that local time is useful.  I would not be averse to creating a
> TLV to distribute local time offset, so that end node can convert to loca=
l
> time and present it to users.****
>
>  ****
>
> However, I do not support the idea of using a local time epoch in the PTP
> timestamp fields. This is an allowed option in IEEE 1588-2008, but I
> believe that this is likely to cause interoperability problems, when some
> vendors support it and others do not.  Also some system architechs have
> indicated that they deploy PTP across large networks, which span time
> zones. This is the feature that should be forbidden.  ****
>
>  ****
>
> In the NTP standard (RFC5905) the timestamps in the packet all use a
> specific time epoch, and generate all other desired time epoch as
> corrections performed at the end points.  Note also that in most computer
> operating systems a single standard time epoch is used in and local time =
is
> generated at the presentation layer for human readable interfaces.****
>
>  ****
>
> Doug****
>
>  ****
>
> On Mon, Oct 28, 2013 at 8:10 AM, John Fletcher <John.Fletcher@bbc.co.uk>
> wrote:****
>
> I'd also like to ask that you don't prohibit the Alternate Timescales
> option.  This is potentially useful to distribute "local time" (your
> time-zone and dst) and there doesn't seem to be any need to prohibit it. =
*
> ***
>
>  ****
>
> John****
>  ------------------------------
>
> *From:* tictoc-bounces@ietf.org [tictoc-bounces@ietf.org] on behalf of
> John Fletcher [John.Fletcher@bbc.co.uk]
> *Sent:* 25 October 2013 11:01
> *To:* Douglas Arnold
> *Cc:* tictoc@ietf.org
> *Subject:* Re: [TICTOC] Enterprise Profile****
>
> Doug,****
>
>  ****
>
> I would be interested to know the circumstances when you see the maximum
> phase adjustment information being used.****
>
>  ****
>
> Some comments:****
>
>  ****
>
> In section 6, you say, =93In all three of the delay measurement modes=85=
=94.  At
> that point in the text you have not yet mentioned multicast, hybrid and
> unicast modes so it=92s not clear which modes you are referring to.****
>
>  ****
>
> In section 9, you say, =93Slaves SHOULD NOT Synchronize to a Rogue Master=
.=94
> It=92s not clear how a slave would know that a master is rogue; presumabl=
y it
> would need to examine the announce messages of all masters and do its own
> BMCA evaluation.  A more realistic =93rogue=94 master would probably meet=
 the
> BMCA criteria for selection.****
>
>  ****
>
> In section 12, =93Alternative Time Scales=94 should be =93Alternate Times=
cales=94.
> ****
>
>  ****
>
>  ****
>
> Regards,****
>
> John Fletcher****
>
>  ****
>
> *From:* tictoc-bounces@ietf.org [mailto:tictoc-bounces@ietf.org] *On
> Behalf Of *Douglas Arnold
> *Sent:* 25 October 2013 01:35
> *To:* tictoc@ietf.org
> *Subject:* [TICTOC] Enterprise Profile****
>
>  ****
>
> Hello Everyone,****
>
>  ****
>
> Attached is an updated version of the Enterprise profile.  Sorry I missed
> the upload deadline for  the Vancouver meeting.  If you get a chance to
> look at it before then I will be there and would love to discuss it. ****
>
>  ****
>
> Summary of changes:****
>
>  ****
>
> I also changed the TLV format to fit the latest proposal in the 1588
> revision.  ****
>
>  ****
>
> I added a statement about not going into the master state unless one had =
a
> current UTC offset.  ****
>
>  ****
>
> I added to the TLV fields to indicate maximum phase correction over a syn=
c
> cycle.****
>
>  ****
>
> -- ****
>
> Doug Arnold****
>
> Principal Technologist****
>
> *JTime!* Meinberg USA****
>
> +1-707-303-5559****
>
>  ****
>
>  ****
>
>  ****
>
> ----------------------------
>
> http://www.bbc.co.uk
> This e-mail (and any attachments) is confidential and may contain persona=
l
> views which are not the views of the BBC unless specifically stated.
> If you have received it in error, please delete it from your system.
> Do not use, copy or disclose the information in any way nor act in
> reliance on it and notify the sender immediately.
> Please note that the BBC monitors e-mails sent or received.
> Further communication will signify your consent to this.****
>
> ---------------------****
>
>  ****
>
> ----------------------------
>
> http://www.bbc.co.uk
> This e-mail (and any attachments) is confidential and may contain persona=
l
> views which are not the views of the BBC unless specifically stated.
> If you have received it in error, please delete it from your system.
> Do not use, copy or disclose the information in any way nor act in
> reliance on it and notify the sender immediately.
> Please note that the BBC monitors e-mails sent or received.
> Further communication will signify your consent to this.****
>
> ---------------------****
>
>
>
> ****
>
>  ****
>
> -- ****
>
> Doug****
>
> ** **
>

--001a11c357608a23f604ea0fb06e
Content-Type: text/html; charset=windows-1252
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">So the use case would be timecode distribution in a broadc=
ast facility where multicast routing is administratively confined to the fa=
cility. Sound reasonable.<div><br></div><div>I think that the reason altern=
ate timescales are not included in the enterprise profile is that the enter=
prise profile is trying to do things the NTP way. NTP does not know about t=
imezones; that is left up to the individual workstations to sort out.</div>
<div><br></div><div>I expect your argument for allowing it that systems tha=
t wish to continue to operate in this way can simply ignore the alternate t=
imescale and even if there is a disagreement about what the local time is, =
they&#39;re no worse off than they currently are.</div>
</div><div class=3D"gmail_extra"><br clear=3D"all"><div><div dir=3D"ltr">Ke=
vin Gross<br><div>+1-303-447-0517</div><div>Media Network Consultant<br><di=
v>AVA Networks -=A0<a href=3D"http://www.avanw.com/" target=3D"_blank">www.=
AVAnw.com</a></div>
</div></div></div>
<br><br><div class=3D"gmail_quote">On Thu, Oct 31, 2013 at 9:28 AM, John Fl=
etcher <span dir=3D"ltr">&lt;<a href=3D"mailto:John.Fletcher@bbc.co.uk" tar=
get=3D"_blank">John.Fletcher@bbc.co.uk</a>&gt;</span> wrote:<br><blockquote=
 class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc soli=
d;padding-left:1ex">






<div lang=3D"EN-GB" link=3D"blue" vlink=3D"purple">
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">Hi Kevin,<u></u><u></u></=
span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d"><u></u>=A0<u></u></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">Well, I think it already =
accepted that there are applications where it is useful to know the local t=
ime.=A0 Generating SMPTE Timecode is one that you know about.<u></u><u></u>=
</span></p>

<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d"><u></u>=A0<u></u></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">From Doug=92s comment, I=
=92m not clear if he wanted to prohibit something different, i.e. using an =
ARB timescale to represent local time.=A0 I=92m happy to prohibit
 that but I would like to see the Alternate Timescales TLV of section 16.3 =
allowed =96 not required, just allowed.<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d"><u></u>=A0<u></u></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">How can the endstation kn=
ow which is the correct local time?=A0 Most likely use case is that the PTP=
 deployment is designed so that masters do not serve more
 than one timezone.=A0 Failing that, it could be user selection based on th=
e name of the alternate timescale.<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d"><u></u>=A0<u></u></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">Yes, you can route multic=
ast messages beyond a subnet but many network administrators, e.g. in my ow=
n company=92s enterprise network, choose not to allow that,
 especially for =93Any Source Multicast=94 as used by 1588.<u></u><u></u></=
span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d"><u></u>=A0<u></u></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">John<u></u><u></u></span>=
</p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d"><u></u>=A0<u></u></span><=
/p>
<p class=3D"MsoNormal"><b><span lang=3D"EN-US" style=3D"font-size:10.0pt;fo=
nt-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;">From:</span></b><span =
lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Tahoma&quot;,&qu=
ot;sans-serif&quot;"> Kevin Gross [mailto:<a href=3D"mailto:kevin.gross@ava=
nw.com" target=3D"_blank">kevin.gross@avanw.com</a>]
<br>
<b>Sent:</b> 29 October 2013 15:45<br>
<b>To:</b> John Fletcher<br>
<b>Cc:</b> Douglas Arnold; <a href=3D"mailto:tictoc@ietf.org" target=3D"_bl=
ank">tictoc@ietf.org</a></span></p><div><div class=3D"h5"><br>
<b>Subject:</b> Re: [TICTOC] Enterprise Profile<u></u><u></u></div></div><p=
></p><div><div class=3D"h5">
<p class=3D"MsoNormal"><u></u>=A0<u></u></p>
<div>
<p class=3D"MsoNormal">Multicast IP routing allows multicast messaging beyo=
nd a subnet. Multicast IP routing is not available over the internet but it=
 is now fairly common on enterprise networks.<u></u><u></u></p>
<div>
<p class=3D"MsoNormal"><u></u>=A0<u></u></p>
</div>
<div>
<p class=3D"MsoNormal">John, can you describe a use case for alternate time=
scales and explain how the endstation can know that the timescale is correc=
t local time or which alternate timescale to use if there are multiple?<u><=
/u><u></u></p>

</div>
</div>
<div>
<p class=3D"MsoNormal"><br clear=3D"all">
<u></u><u></u></p>
<div>
<div>
<p class=3D"MsoNormal">Kevin Gross<u></u><u></u></p>
<div>
<p class=3D"MsoNormal"><a href=3D"tel:%2B1-303-447-0517" value=3D"+13034470=
517" target=3D"_blank">+1-303-447-0517</a><u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">Media Network Consultant<u></u><u></u></p>
<div>
<p class=3D"MsoNormal">AVA Networks -=A0<a href=3D"http://www.avanw.com/" t=
arget=3D"_blank">www.AVAnw.com</a><u></u><u></u></p>
</div>
</div>
</div>
</div>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt"><u></u>=A0<u></u></p>
<div>
<p class=3D"MsoNormal">On Tue, Oct 29, 2013 at 4:18 AM, John Fletcher &lt;<=
a href=3D"mailto:John.Fletcher@bbc.co.uk" target=3D"_blank">John.Fletcher@b=
bc.co.uk</a>&gt; wrote:<u></u><u></u></p>
<div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">Just to be clear, I am no=
t suggesting use of a different epoch in timestamp fields.=A0 I am talking
 about the optional TLV described in section 16.3 which can give you the of=
fset(s) between PTP time and one or more timescales of your choice.</span><=
u></u><u></u></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">=A0</span><u></u><u></u><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">Regarding spanning timezo=
nes, there is a difference between the extent of the enterprise network
 and the extent of the part of network served by a PTP master.=A0 The latte=
r is probably a subnet since multicast messages (e.g. Announce) are usually=
 confined to a subnet.=A0 A subnet spanning multiple timezones would be les=
s common.=A0 However you can have more
 than one Alternate Timescale if necessary.</span><u></u><u></u></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">=A0</span><u></u><u></u><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">This feature is just an o=
ption; I=92m not suggesting it be required, just that it not be forbidden.<=
/span><u></u><u></u></p>

<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">=A0</span><u></u><u></u><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">John</span><u></u><u></u>=
</p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">=A0</span><u></u><u></u><=
/p>
<p class=3D"MsoNormal"><b><span lang=3D"EN-US" style=3D"font-size:10.0pt;fo=
nt-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;">From:</span></b><span =
lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Tahoma&quot;,&qu=
ot;sans-serif&quot;"> Douglas
 Arnold [mailto:<a href=3D"mailto:doug.arnold2@gmail.com" target=3D"_blank"=
>doug.arnold2@gmail.com</a>]
<br>
<b>Sent:</b> 28 October 2013 20:06<br>
<b>To:</b> John Fletcher</span><u></u><u></u></p>
<div>
<div>
<p class=3D"MsoNormal"><br>
<b>Cc:</b> <a href=3D"mailto:tictoc@ietf.org" target=3D"_blank">tictoc@ietf=
.org</a><br>
<b>Subject:</b> Re: [TICTOC] Enterprise Profile<u></u><u></u></p>
</div>
</div>
<div>
<div>
<p class=3D"MsoNormal">=A0<u></u><u></u></p>
<div>
<p class=3D"MsoNormal">Hello John,<u></u><u></u></p>
<div>
<p class=3D"MsoNormal">=A0<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">I agree that local time is useful. =A0I would not be=
 averse to creating a TLV to distribute local time offset, so that end node=
 can convert to local time and present it to users.<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">=A0<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">However, I do not support the idea of using a local =
time epoch in the PTP timestamp fields. This is an allowed option in IEEE 1=
588-2008, but I believe that this is likely to cause
 interoperability problems, when some vendors support it and others do not.=
=A0=A0Also some system architechs have indicated that they deploy PTP acros=
s large networks, which span time zones.=A0This is the feature that should =
be forbidden. =A0<u></u><u></u></p>

</div>
<div>
<p class=3D"MsoNormal">=A0<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">In the NTP standard (RFC5905) the timestamps in the =
packet all use a specific time epoch, and generate all other desired time e=
poch as corrections performed at the end points. =A0Note
 also that in most computer operating systems a single standard time epoch =
is used in and local time is generated at the presentation layer for human =
readable interfaces.<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">=A0<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">Doug<u></u><u></u></p>
</div>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt">=A0<u></u><u></u></p>
<div>
<p class=3D"MsoNormal">On Mon, Oct 28, 2013 at 8:10 AM, John Fletcher &lt;<=
a href=3D"mailto:John.Fletcher@bbc.co.uk" target=3D"_blank">John.Fletcher@b=
bc.co.uk</a>&gt; wrote:<u></u><u></u></p>
<div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Ta=
homa&quot;,&quot;sans-serif&quot;">I&#39;d also like to ask that you don&#3=
9;t prohibit the Alternate Timescales option. =A0This is potentially useful=
 to distribute
 &quot;local time&quot; (your time-zone and dst) and there doesn&#39;t seem=
 to be any need to prohibit it.
</span><u></u><u></u></p>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Ta=
homa&quot;,&quot;sans-serif&quot;">=A0</span><u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Ta=
homa&quot;,&quot;sans-serif&quot;">John</span><u></u><u></u></p>
<div>
<div class=3D"MsoNormal" align=3D"center" style=3D"text-align:center">
<hr size=3D"2" width=3D"100%" align=3D"center">
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt"><b><span style=3D"fon=
t-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;">From:</span></b><span s=
tyle=3D"font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;">
<a href=3D"mailto:tictoc-bounces@ietf.org" target=3D"_blank">tictoc-bounces=
@ietf.org</a> [<a href=3D"mailto:tictoc-bounces@ietf.org" target=3D"_blank"=
>tictoc-bounces@ietf.org</a>] on behalf of John Fletcher [<a href=3D"mailto=
:John.Fletcher@bbc.co.uk" target=3D"_blank">John.Fletcher@bbc.co.uk</a>]<br=
>

<b>Sent:</b> 25 October 2013 11:01<br>
<b>To:</b> Douglas Arnold<br>
<b>Cc:</b> <a href=3D"mailto:tictoc@ietf.org" target=3D"_blank">tictoc@ietf=
.org</a><br>
<b>Subject:</b> Re: [TICTOC] Enterprise Profile</span><u></u><u></u></p>
</div>
<div>
<div>
<div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">Doug,</span><u></u><u></u=
></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">=A0</span><u></u><u></u><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">I would be interested to =
know the circumstances when you see the maximum phase adjustment informatio=
n
 being used.</span><u></u><u></u></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">=A0</span><u></u><u></u><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">Some comments:</span><u><=
/u><u></u></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">=A0</span><u></u><u></u><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">In section 6, you say, =
=93In all three of the delay measurement modes=85=94.=A0 At that point in t=
he text
 you have not yet mentioned multicast, hybrid and unicast modes so it=92s n=
ot clear which modes you are referring to.</span><u></u><u></u></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">=A0</span><u></u><u></u><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">In section 9, you say, =
=93Slaves SHOULD NOT Synchronize to a Rogue Master.=94=A0 It=92s not clear =
how a slave
 would know that a master is rogue; presumably it would need to examine the=
 announce messages of all masters and do its own BMCA evaluation.=A0 A more=
 realistic =93rogue=94 master would probably meet the BMCA criteria for sel=
ection.</span><u></u><u></u></p>

<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">=A0</span><u></u><u></u><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">In section 12, =93Alterna=
tive Time Scales=94 should be =93Alternate Timescales=94.</span><u></u><u><=
/u></p>

<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">=A0</span><u></u><u></u><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">=A0</span><u></u><u></u><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">Regards,</span><u></u><u>=
</u></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">John Fletcher</span><u></=
u><u></u></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">=A0</span><u></u><u></u><=
/p>
<p class=3D"MsoNormal"><b><span lang=3D"EN-US" style=3D"font-size:10.0pt;fo=
nt-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;">From:</span></b><span =
lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Tahoma&quot;,&qu=
ot;sans-serif&quot;">
<a href=3D"mailto:tictoc-bounces@ietf.org" target=3D"_blank">tictoc-bounces=
@ietf.org</a> [mailto:<a href=3D"mailto:tictoc-bounces@ietf.org" target=3D"=
_blank">tictoc-bounces@ietf.org</a>]
<b>On Behalf Of </b>Douglas Arnold<br>
<b>Sent:</b> 25 October 2013 01:35<br>
<b>To:</b> <a href=3D"mailto:tictoc@ietf.org" target=3D"_blank">tictoc@ietf=
.org</a><br>
<b>Subject:</b> [TICTOC] Enterprise Profile</span><u></u><u></u></p>
<p class=3D"MsoNormal">=A0<u></u><u></u></p>
<div>
<p class=3D"MsoNormal">Hello Everyone,<u></u><u></u></p>
<div>
<p class=3D"MsoNormal">=A0<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">Attached is an updated version of the Enterprise pro=
file. =A0Sorry I missed the upload deadline for=A0=A0the Vancouver meeting.=
 =A0If you get a chance to look at it before then I will be
 there and would love to discuss it.=A0<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">=A0<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">Summary of changes:<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">=A0<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:9.5pt;font-family:&quot;Ari=
al&quot;,&quot;sans-serif&quot;">I also changed the TLV format to fit the l=
atest proposal in the 1588 revision. =A0</span><u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">=A0<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:9.5pt;font-family:&quot;Ari=
al&quot;,&quot;sans-serif&quot;">I added a statement about not going into t=
he master state unless one had a current UTC offset. =A0</span><u></u><u></=
u></p>

</div>
<div>
<p class=3D"MsoNormal">=A0<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:9.5pt;font-family:&quot;Ari=
al&quot;,&quot;sans-serif&quot;">I added to the TLV fields to indicate maxi=
mum phase correction over a sync cycle.</span><u></u><u></u></p>
</div>
<div>
<div>
<p class=3D"MsoNormal">=A0<u></u><u></u></p>
</div>
<p class=3D"MsoNormal">--
<u></u><u></u></p>
<div>
<p class=3D"MsoNormal">Doug Arnold<u></u><u></u></p>
<div>
<p class=3D"MsoNormal">Principal Technologist<u></u><u></u></p>
<div>
<p class=3D"MsoNormal"><i>JTime!</i>=A0Meinberg USA<u></u><u></u></p>
</div>
</div>
<div>
<p class=3D"MsoNormal"><a href=3D"tel:%2B1-707-303-5559" target=3D"_blank">=
+1-707-303-5559</a><u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">=A0<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">=A0<u></u><u></u></p>
</div>
</div>
</div>
</div>
</div>
<p>=A0<u></u><u></u></p>
<p>----------------------------<br>
<br>
<a href=3D"http://www.bbc.co.uk" target=3D"_blank">http://www.bbc.co.uk</a>=
<br>
This e-mail (and any attachments) is confidential and may contain personal =
views which are not the views of the BBC unless specifically stated.<br>
If you have received it in error, please delete it from your system.<br>
Do not use, copy or disclose the information in any way nor act in reliance=
 on it and notify the sender immediately.<br>
Please note that the BBC monitors e-mails sent or received.<br>
Further communication will signify your consent to this.<u></u><u></u></p>
<p>---------------------<u></u><u></u></p>
</div>
</div>
</div>
</div>
</div>
</div>
<div>
<div>
<p>=A0<u></u><u></u></p>
<p>----------------------------<br>
<br>
<a href=3D"http://www.bbc.co.uk" target=3D"_blank">http://www.bbc.co.uk</a>=
<br>
This e-mail (and any attachments) is confidential and may contain personal =
views which are not the views of the BBC unless specifically stated.<br>
If you have received it in error, please delete it from your system.<br>
Do not use, copy or disclose the information in any way nor act in reliance=
 on it and notify the sender immediately.<br>
Please note that the BBC monitors e-mails sent or received.<br>
Further communication will signify your consent to this.<u></u><u></u></p>
<p>---------------------<u></u><u></u></p>
</div>
</div>
</div>
</div>
<p class=3D"MsoNormal"><br>
<br clear=3D"all">
<u></u><u></u></p>
<div>
<p class=3D"MsoNormal">=A0<u></u><u></u></p>
</div>
<p class=3D"MsoNormal">--
<u></u><u></u></p>
<div>
<p class=3D"MsoNormal">Doug<u></u><u></u></p>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
<p class=3D"MsoNormal"><u></u>=A0<u></u></p>
</div>
</div></div></div>
</div>

</blockquote></div><br></div>

--001a11c357608a23f604ea0fb06e--
