
From luchuk@snmp.com  Mon Jun  3 10:53:38 2013
Return-Path: <luchuk@snmp.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 BAD3321F8DDD for <tictoc@ietfa.amsl.com>; Mon,  3 Jun 2013 10:53:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.11
X-Spam-Level: 
X-Spam-Status: No, score=-1.11 tagged_above=-999 required=5 tests=[BAYES_05=-1.11]
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 KB8vEpdtvlHo for <tictoc@ietfa.amsl.com>; Mon,  3 Jun 2013 10:53:20 -0700 (PDT)
Received: from mailbox.snmp.com (mailbox.snmp.com [192.147.142.80]) by ietfa.amsl.com (Postfix) with ESMTP id AF79521F87CD for <tictoc@ietf.org>; Mon,  3 Jun 2013 10:51:10 -0700 (PDT)
Received: from adminfs.snmp.com (adminfs.snmp.com [192.147.142.39]) by mailbox.snmp.com (8.9.3p2-20030922/m.0080228) with ESMTP id NAA20739; Mon, 3 Jun 2013 13:51:08 -0400 (EDT)
Received: (from luchuk@localhost) by adminfs.snmp.com (8.9.3p2-20030922/snmpclient.mc-990525) id NAA02085; Mon, 3 Jun 2013 13:51:04 -0400 (EDT)
Date: Mon, 3 Jun 2013 13:51:04 -0400 (EDT)
From: Alan Luchuk <luchuk@snmp.com>
Message-Id: <201306031751.NAA02085@adminfs.snmp.com>
To: tictoc@ietf.org
X-Mailman-Approved-At: Mon, 03 Jun 2013 22:48:13 -0700
Cc: luchuk@snmp.com
Subject: Re: [TICTOC] WGLC on draft-ietf-tictoc-ptp-mib-05.txt
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, 03 Jun 2013 17:53:38 -0000

Hello,

SNMP Research created an SNMP agent prototype from the most current
PTPBASE-MIB (with a last updated date of 201207230000Z).   We had no
technical difficulties doing so, and do not know of SNMP-related
technical reasons that draft-ietf-tictoc-ptp-mib-05.txt cannot be
advanced in the standardization process.  That said, we do not have
PTP expertise, and are not qualified to comment about whether the
instrumentation itself would be useful to the internet community.

We hope this information is useful to the TICTOC WG, and will be happy
to answer more specific questions or provide additional information.

Regards,
--Alan

 ------------------------------------------------------------------------------
 Alan Luchuk               SNMP Research, Inc.          Voice:  +1 865 573 1434
 Senior Software Engineer  3001 Kimberlin Heights Road  FAX:    +1 865 573 9197
 luchuk at snmp.com        Knoxville, TN  37920-9716    http://www.snmp.com/
 ------------------------------------------------------------------------------


From davari@broadcom.com  Tue Jun  4 16:40:05 2013
Return-Path: <davari@broadcom.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 8167E21F8F29 for <tictoc@ietfa.amsl.com>; Tue,  4 Jun 2013 16:40:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id JbGYPAFF4qcf for <tictoc@ietfa.amsl.com>; Tue,  4 Jun 2013 16:40:01 -0700 (PDT)
Received: from mms1.broadcom.com (mms1.broadcom.com [216.31.210.17]) by ietfa.amsl.com (Postfix) with ESMTP id 4860621F8F0C for <tictoc@ietf.org>; Tue,  4 Jun 2013 16:39:58 -0700 (PDT)
Received: from [10.9.208.57] by mms1.broadcom.com with ESMTP (Broadcom SMTP Relay (Email Firewall v6.5)); Tue, 04 Jun 2013 16:36:11 -0700
X-Server-Uuid: 06151B78-6688-425E-9DE2-57CB27892261
Received: from SJEXCHCAS07.corp.ad.broadcom.com (10.16.203.16) by IRVEXCHCAS08.corp.ad.broadcom.com (10.9.208.57) with Microsoft SMTP Server (TLS) id 14.1.438.0; Tue, 4 Jun 2013 16:39:49 -0700
Received: from SJEXCHMB12.corp.ad.broadcom.com ( [fe80::bc15:c1e1:c29a:36f7]) by SJEXCHCAS07.corp.ad.broadcom.com ( [::1]) with mapi id 14.01.0438.000; Tue, 4 Jun 2013 16:39:48 -0700
From: "Shahram Davari" <davari@broadcom.com>
To: "Meyer, Peter" <Peter.Meyer@microsemi.com>, "tictoc@ietf.org" <tictoc@ietf.org>
Thread-Topic: [TICTOC] comments on draft-ietf-tictoc-1588overmpls-04.txt
Thread-Index: AQHOHrvIG9Qp4DAEq0WS7lIAjM8M8JkmuDRw
Date: Tue, 4 Jun 2013 23:39:48 +0000
Message-ID: <4A6CE49E6084B141B15C0713B8993F281BE28013@SJEXCHMB12.corp.ad.broadcom.com>
References: <20130223072233.32735.89371.idtracker@ietfa.amsl.com> <64683B4805156847B0ED373DAB3057CA015E930D@ottsrv0015.microsemi.net>
In-Reply-To: <64683B4805156847B0ED373DAB3057CA015E930D@ottsrv0015.microsemi.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.16.203.100]
MIME-Version: 1.0
X-WSS-ID: 7DB0A66131W31352691-01-01
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Subject: Re: [TICTOC] comments on draft-ietf-tictoc-1588overmpls-04.txt
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, 04 Jun 2013 23:40:05 -0000

Hi Peter,

Thanks for your god comments. Please see my responses inline. Please let me=
 know whether you are satisfied with my responses since I am updating the d=
raft in the next couple of days.

Thanks
Shahram

-----Original Message-----
From: tictoc-bounces@ietf.org [mailto:tictoc-bounces@ietf.org] On Behalf Of=
 Meyer, Peter
Sent: Monday, March 11, 2013 5:49 PM
To: tictoc@ietf.org
Subject: Re: [TICTOC] comments on draft-ietf-tictoc-1588overmpls-04.txt

Hi Shahram et al,

Some comments on draft -04.


1) Section 3.  "A generic method is defined in this document that does
not require deep packet inspection at line rate, and can
deterministically identify Timing messages.  The generic method is
applicable to MPLS and MPLS-TP networks."

May want to add that this would apply only to one-step TC (I imagine
that is the point of the correction at line rate).  A two-step TC would
need to do deep packet inspection as it uses sourcePortIdentity &
sequenceId fields for Follow_up or Delay_Resp.

SD> For 2-step, all that is needed is for an interface to detect the Timing=
 message (based on top MPLS Label)  and record the Time along with some inf=
ormation from the Timing packet and send them to CPU while forwarding the T=
iming message as usual. Then the CPU based on the information received gene=
rates Follow-up message and injects it in to the LSP.  Therefore it is the =
job of CPU to look at sourcePortIdentity & sequenceId fields not the Hardwa=
re.


2) Section 4.  "An MPLS domain can serve multiple customers.  This means
that the MPLS domain (maintained by a service provider) may provide
timing services to multiple customers, each having their own Timing
domain.  Therefore LER BCs need to interact with multiple grandmasters,
and consequently multiple time references."

This should be re-phrased.  It switches from an optional situation ("may
provide timing services") to mandatory situation ("LER BCs need to
interact").   Some words such as "in such a deployment scenario, ...."
and replace "can" with "may".   We have seen at ITU at least (with
participation from operators BT, FT, DT, CMCC, AT&T, Sprint, etc.) that
this multiple operator domain case was not useful enough to be included
in standardization process for Telecom networks.

SD> I rephrased it as following:

" An MPLS domain can serve multiple customers.  This means that the
   MPLS domain (maintained by a service provider) may provide timing
   services to multiple customers, each having their own Timing domain.
   Therefore in such deployment scenarios, LER BCs may interact with multip=
le grandmasters,=20
and consequently multiple time references.  Also, LER/LSR TCs MUST be synch=
ronized to the=20
same master clock (which is the service provider Master clock), which impli=
es that they need=20
to choose one master to synchronize to."


3) Section 19.  "For transporting such peer delay measurement messages a
single-hop LSP SHOULD to be created between the two adjacent LSRs
engaged in peer delay measurement to carry peer delay measurement
messages. Other methods such as PTP transport over Ethernet MAY be used
for transporting peer delay measurement messages if the link between the
two routers is Ethernet."


This new statement to handle peer-delay (which in earlier drafts did not
have a communication path listed), also allows a BC to be embedded in an
LSR with a communication path between BC's as a single-hop LSP
(mentioned March 22, 2012 in my feedback to draft -03, subject "[TICTOC]
Updated 1588 over MPLS draf-03").

SD> When a single-hop LSP is created then I call the both ends of that LSP,=
 LERs and not LSRs.
Note that a router can act as LSR for some LSPs and LER for other LSPs. The=
 point is that we can't
Terminate a packet in the middle of an LSP (i.e., in an LSR). So BC functio=
nality can't exist in the middle
Of a PTP LSP. So I think it is a matter of terminology otherwise I agree th=
at you could have BC in the core
(not edge).=20

Architecture diagrams Figure 1 and Figure should be updated to reflect
the possibility of either BC or TC implementation.   Section 18.2 and
section 18.3 and section 21 should also be updated to reflect the
possibility of either BC or TC.  I understand the RFC is intended to be
generic and not targeted only at TC.



4) Section 20.  "When the MPLS network (provider network) serves
multiple customers, it is important to maintain and process each
customers clock and Timing messages separately from other customers to
ensure there is no cross- customer effect.   For example if an LER BC is
synchronized to a specific grandmaster, belonging to customer A, then
the LER MUST use that BC clock only for customer A to ensure that
customer A cannot attack other customers by manipulating its time."

This seems much more applicable to the TC LSR and should be stated.
>From section 4 we see the TC uses the primary synchronization domain
(that of the service provide) to correct PTP messages.

SD> I don't see how in a TC LSR, one customer timing can affect other custo=
mer timings?
Since in a TC, we just update the Timestamp of a packet based on the Servic=
e provider Time.
May be I have not understood your point. Could you please clarify with an e=
xample.



5) Section 20.  "Timing messages (as opposed to regular customer data)
SHOULD not be encrypted or authenticated on an end-to-end basis."  I
think there is a security draft in parallel being developed that may be
relevant to that statement.

SD> I have updated the  text as following:

" Timing messages MAY be encrypted or authenticated, provided that the LERs=
/LSRs that are Timing capable/aware can authenticate/ decrypt the timing me=
ssages."




Regards,
Peter


-----Original Message-----
From: tictoc-bounces@ietf.org [mailto:tictoc-bounces@ietf.org] On Behalf
Of internet-drafts@ietf.org
Sent: February 23, 2013 2:23 AM
To: i-d-announce@ietf.org
Cc: tictoc@ietf.org
Subject: [TICTOC] I-D Action: draft-ietf-tictoc-1588overmpls-04.txt


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

	Title           : Transporting Timing messages over MPLS
Networks
	Author(s)       : Shahram Davari
                          Amit Oren
                          Manav Bhatia
                          Peter Roberts
                          Laurent Montini
	Filename        : draft-ietf-tictoc-1588overmpls-04.txt
	Pages           : 36
	Date            : 2013-02-22

Abstract:
   This document defines the method for transporting Timing messages
   such as PTP and NTP over an MPLS network.  The method allows for the
   easy identification of these PDUs at the port level to allow for port
   level processing of these PDUs in both LERs and LSRs.

   The basic idea is to transport Timing messages inside dedicated MPLS
   LSPs.  These LSPs only carry timing messages and possibly Control and
   Management packets, but they do not carry customer traffic.

   Two methods for transporting Timing messages over MPLS are defined.
   The first method is to transport Timing messages directly over the
   dedicated MPLS LSP via UDP/IP encapsulation, which is suitable for
   MPLS networks.  The second method is to transport Timing messages
   inside a PW via Ethernet encapsulation, which is suitable for both
   MPLS and MPLS-TP networks.


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

There's also a htmlized version available at:
http://tools.ietf.org/html/draft-ietf-tictoc-1588overmpls-04

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


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

_______________________________________________
TICTOC mailing list
TICTOC@ietf.org
https://www.ietf.org/mailman/listinfo/tictoc


_______________________________________________
TICTOC mailing list
TICTOC@ietf.org
https://www.ietf.org/mailman/listinfo/tictoc



From davari@broadcom.com  Tue Jun  4 17:58:19 2013
Return-Path: <davari@broadcom.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 CA32421F9A3E for <tictoc@ietfa.amsl.com>; Tue,  4 Jun 2013 17:58:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id p-+M5818clPM for <tictoc@ietfa.amsl.com>; Tue,  4 Jun 2013 17:58:15 -0700 (PDT)
Received: from mms2.broadcom.com (mms2.broadcom.com [216.31.210.18]) by ietfa.amsl.com (Postfix) with ESMTP id 9BABE21F9A39 for <tictoc@ietf.org>; Tue,  4 Jun 2013 17:58:15 -0700 (PDT)
Received: from [10.9.208.55] by mms2.broadcom.com with ESMTP (Broadcom SMTP Relay (Email Firewall v6.5)); Tue, 04 Jun 2013 17:52:18 -0700
X-Server-Uuid: 4500596E-606A-40F9-852D-14843D8201B2
Received: from SJEXCHCAS07.corp.ad.broadcom.com (10.16.203.16) by IRVEXCHCAS07.corp.ad.broadcom.com (10.9.208.55) with Microsoft SMTP Server (TLS) id 14.1.438.0; Tue, 4 Jun 2013 17:57:56 -0700
Received: from SJEXCHMB12.corp.ad.broadcom.com ( [fe80::bc15:c1e1:c29a:36f7]) by SJEXCHCAS07.corp.ad.broadcom.com ( [::1]) with mapi id 14.01.0438.000; Tue, 4 Jun 2013 17:57:56 -0700
From: "Shahram Davari" <davari@broadcom.com>
To: "Yaakov Stein" <yaakov_s@rad.com>, "tictoc@ietf.org" <tictoc@ietf.org>
Thread-Topic: [TICTOC] comments on draft-ietf-tictoc-1588overmpls-04.txt
Thread-Index: AQHOHrvIG9Qp4DAEq0WS7lIAjM8M8JihO/3AgACemICAhPOAQA==
Date: Wed, 5 Jun 2013 00:57:56 +0000
Message-ID: <4A6CE49E6084B141B15C0713B8993F281BE2A0F0@SJEXCHMB12.corp.ad.broadcom.com>
References: <20130223072233.32735.89371.idtracker@ietfa.amsl.com> <64683B4805156847B0ED373DAB3057CA015E930D@ottsrv0015.microsemi.net> <4A6CE49E6084B141B15C0713B8993F281BD9A385@SJEXCHMB12.corp.ad.broadcom.com> <07F7D7DED63154409F13298786A2ADC904C98194@EXRAD5.ad.rad.co.il>
In-Reply-To: <07F7D7DED63154409F13298786A2ADC904C98194@EXRAD5.ad.rad.co.il>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.16.203.100]
MIME-Version: 1.0
X-WSS-ID: 7DB054481R026377012-01-01
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Subject: Re: [TICTOC] comments on draft-ietf-tictoc-1588overmpls-04.txt
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: Wed, 05 Jun 2013 00:58:20 -0000

Hi Yaakov,

Thanks for your great comments, please see my response inline.

Thx
Shahram

-----Original Message-----
From: Yaakov Stein [mailto:yaakov_s@rad.com]=20
Sent: Monday, March 11, 2013 8:26 PM
To: Shahram Davari; tictoc@ietf.org
Subject: RE: [TICTOC] comments on draft-ietf-tictoc-1588overmpls-04.txt

Shahram

A few more comments.

First, I don't like the terminology "both MPLS and MPLS-TP".
MPLS-TP is MPLS too. And in any case "environments" (in the plural).

SD> I have removed such text and replaced it with MPLS/MPLS-TP

"Extensions to signaling protocols (e.g., RSVP-TE) are required"
well, you COULD set them up manually, in which case no extensions are requi=
red.

SD> I have changed the text to" If singling is used then extension to signa=
ling is required ...."

Section 5 GAL/ACH -> GAL/G-Ach (and throughout the document you have variou=
s mis-spellings of G-Ach)

SD> Done

In section 6.2 you require the Ethernet to be tagged, and in fact to be dou=
ble tagged.
Since we now have an offset from BoS to the TC, why is this required ?
I realize that we want to limit the number of different encaps to be suppor=
ted,
but I believe this is too harsh a limitation.
And why must the tagged mode of 4448 be used ? =20
You can have tags and still use raw mode.

SD> I made both tags optional and also optional to use Raw or tagged mode

Section 6.3 - If NTP or some new method is used,=20
with which part of the packet is the timestamp associated ?
Also "the control and signaling requirements in this document are defined .=
.."
needs to be removed (they are NOT defined here any more).

SD> I don't understand your comment that says " with which part of the pack=
et is the timestamp associated ?" could you please clarify.

Section 7: technically a TC is not a timestamp, it is a time difference.
Also updating the TC is not time-stamping either.

SD> I have changed the text to state " time-stamping or correction field up=
date"

I see that in Section 8 the recommendation regarding protection switching i=
s SHOULD be used.
As you know I don't agree, but let's see if the WG agrees to this in LC.
Taking my view to the extreme, why outlaw ECMP in Section 9?
I agree with ruling it out, but if you allow protection switching, then why=
 not ECMP?
Properly performed TC will remove the major portion of the delay difference=
s.

SD> We could rephrase as:

" Therefore this specification recommends that protection
   switching SHOULD NOT be used, unless the operator knows that the
   protection switching does NOT have adverse effect on the slave clock."

SD> But both mean the same thing.

Section 11: entropy -> entropy label

Perhaps sections 14 and 15 can be combined. I am not sure which way is bett=
er.

SD> Done

If I remember the last meeting correctly,=20
we asked for the signaling material to be mentioned in an Appendix.
Here it is in Sections 16 and 17.
I am not sure that this is terrible, but I don't think these belong in the =
body of a PS draft.

SD> Done, both moved to Appendix

Section 19 ware -> aware, it needs -> they need

SD> Done

I am not sure we need the applicability statement.

SD> Applicability statement removed

In the Acknowledgements: Luca Moniti -> Luca Martini

SD> Done

Y(J)S

-----Original Message-----
From: tictoc-bounces@ietf.org [mailto:tictoc-bounces@ietf.org] On Behalf Of=
 Shahram Davari
Sent: 12 March, 2013 02:59
To: Meyer, Peter; tictoc@ietf.org
Subject: Re: [TICTOC] comments on draft-ietf-tictoc-1588overmpls-04.txt

Peter,

Good feedback. I will update the draft after the Orlando to include your co=
mments.

Thx
Shahram

-----Original Message-----
From: tictoc-bounces@ietf.org [mailto:tictoc-bounces@ietf.org] On Behalf Of=
 Meyer, Peter
Sent: Monday, March 11, 2013 5:49 PM
To: tictoc@ietf.org
Subject: Re: [TICTOC] comments on draft-ietf-tictoc-1588overmpls-04.txt

Hi Shahram et al,

Some comments on draft -04.


1) Section 3.  "A generic method is defined in this document that does
not require deep packet inspection at line rate, and can
deterministically identify Timing messages.  The generic method is
applicable to MPLS and MPLS-TP networks."

May want to add that this would apply only to one-step TC (I imagine
that is the point of the correction at line rate).  A two-step TC would
need to do deep packet inspection as it uses sourcePortIdentity &
sequenceId fields for Follow_up or Delay_Resp.


2) Section 4.  "An MPLS domain can serve multiple customers.  This means
that the MPLS domain (maintained by a service provider) may provide
timing services to multiple customers, each having their own Timing
domain.  Therefore LER BCs need to interact with multiple grandmasters,
and consequently multiple time references."

This should be re-phrased.  It switches from an optional situation ("may
provide timing services") to mandatory situation ("LER BCs need to
interact").   Some words such as "in such a deployment scenario, ...."
and replace "can" with "may".   We have seen at ITU at least (with
participation from operators BT, FT, DT, CMCC, AT&T, Sprint, etc.) that
this multiple operator domain case was not useful enough to be included
in standardization process for Telecom networks.


3) Section 19.  "For transporting such peer delay measurement messages a
single-hop LSP SHOULD to be created between the two adjacent LSRs
engaged in peer delay measurement to carry peer delay measurement
messages. Other methods such as PTP transport over Ethernet MAY be used
for transporting peer delay measurement messages if the link between the
two routers is Ethernet."


This new statement to handle peer-delay (which in earlier drafts did not
have a communication path listed), also allows a BC to be embedded in an
LSR with a communication path between BC's as a single-hop LSP
(mentioned March 22, 2012 in my feedback to draft -03, subject "[TICTOC]
Updated 1588 over MPLS draf-03").

Architecture diagrams Figure 1 and Figure should be updated to reflect
the possibility of either BC or TC implementation.   Section 18.2 and
section 18.3 and section 21 should also be updated to reflect the
possibility of either BC or TC.  I understand the RFC is intended to be
generic and not targeted only at TC.



4) Section 20.  "When the MPLS network (provider network) serves
multiple customers, it is important to maintain and process each
customers clock and Timing messages separately from other customers to
ensure there is no cross- customer effect.   For example if an LER BC is
synchronized to a specific grandmaster, belonging to customer A, then
the LER MUST use that BC clock only for customer A to ensure that
customer A cannot attack other customers by manipulating its time."

This seems much more applicable to the TC LSR and should be stated.
>From section 4 we see the TC uses the primary synchronization domain
(that of the service provide) to correct PTP messages.



5) Section 20.  "Timing messages (as opposed to regular customer data)
SHOULD not be encrypted or authenticated on an end-to-end basis."  I
think there is a security draft in parallel being developed that may be
relevant to that statement.



Regards,
Peter


-----Original Message-----
From: tictoc-bounces@ietf.org [mailto:tictoc-bounces@ietf.org] On Behalf
Of internet-drafts@ietf.org
Sent: February 23, 2013 2:23 AM
To: i-d-announce@ietf.org
Cc: tictoc@ietf.org
Subject: [TICTOC] I-D Action: draft-ietf-tictoc-1588overmpls-04.txt


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

	Title           : Transporting Timing messages over MPLS
Networks
	Author(s)       : Shahram Davari
                          Amit Oren
                          Manav Bhatia
                          Peter Roberts
                          Laurent Montini
	Filename        : draft-ietf-tictoc-1588overmpls-04.txt
	Pages           : 36
	Date            : 2013-02-22

Abstract:
   This document defines the method for transporting Timing messages
   such as PTP and NTP over an MPLS network.  The method allows for the
   easy identification of these PDUs at the port level to allow for port
   level processing of these PDUs in both LERs and LSRs.

   The basic idea is to transport Timing messages inside dedicated MPLS
   LSPs.  These LSPs only carry timing messages and possibly Control and
   Management packets, but they do not carry customer traffic.

   Two methods for transporting Timing messages over MPLS are defined.
   The first method is to transport Timing messages directly over the
   dedicated MPLS LSP via UDP/IP encapsulation, which is suitable for
   MPLS networks.  The second method is to transport Timing messages
   inside a PW via Ethernet encapsulation, which is suitable for both
   MPLS and MPLS-TP networks.


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

There's also a htmlized version available at:
http://tools.ietf.org/html/draft-ietf-tictoc-1588overmpls-04

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


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

_______________________________________________
TICTOC mailing list
TICTOC@ietf.org
https://www.ietf.org/mailman/listinfo/tictoc


_______________________________________________
TICTOC mailing list
TICTOC@ietf.org
https://www.ietf.org/mailman/listinfo/tictoc


_______________________________________________
TICTOC mailing list
TICTOC@ietf.org
https://www.ietf.org/mailman/listinfo/tictoc



From Peter.Meyer@microsemi.com  Wed Jun  5 11:01:37 2013
Return-Path: <Peter.Meyer@microsemi.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 64E2E21F99EE for <tictoc@ietfa.amsl.com>; Wed,  5 Jun 2013 11:01:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 0Txlptc61n34 for <tictoc@ietfa.amsl.com>; Wed,  5 Jun 2013 11:01:22 -0700 (PDT)
Received: from co9outboundpool.messaging.microsoft.com (co9ehsobe004.messaging.microsoft.com [207.46.163.27]) by ietfa.amsl.com (Postfix) with ESMTP id D969321F9744 for <tictoc@ietf.org>; Wed,  5 Jun 2013 11:01:01 -0700 (PDT)
Received: from mail184-co9-R.bigfish.com (10.236.132.228) by CO9EHSOBE015.bigfish.com (10.236.130.78) with Microsoft SMTP Server id 14.1.225.23; Wed, 5 Jun 2013 18:01:00 +0000
Received: from mail184-co9 (localhost [127.0.0.1])	by mail184-co9-R.bigfish.com (Postfix) with ESMTP id A74B21000F0; Wed,  5 Jun 2013 18:01:00 +0000 (UTC)
X-Forefront-Antispam-Report: CIP:209.226.172.12; KIP:(null); UIP:(null); IPV:NLI; H:ottsrv0014.microsemi.net; RD:none; EFVD:NLI
X-SpamScore: -23
X-BigFish: VS-23(zz9371I936eIc85fh542Izz1f42h1ee6h1de0h1fdah1202h1e76h1d1ah1d2ah1fc6hzz1033IL17326ah8275dhz2dh668h839hd25hf0ah1288h12a5h12bdh137ah1441h14ddh1504h1537h153bh15d0h162dh1631h1758h184fh18e1h1946h19b5h1ad9h1b0ah1bceh1c24h1d0ch1d2eh1d3fh1dfeh1dffh1e1dh34h1155h)
Received: from mail184-co9 (localhost.localdomain [127.0.0.1]) by mail184-co9 (MessageSwitch) id 1370455257729471_27000; Wed,  5 Jun 2013 18:00:57 +0000 (UTC)
Received: from CO9EHSMHS006.bigfish.com (unknown [10.236.132.250])	by mail184-co9.bigfish.com (Postfix) with ESMTP id AD9C660004C; Wed,  5 Jun 2013 18:00:57 +0000 (UTC)
Received: from ottsrv0014.microsemi.net (209.226.172.12) by CO9EHSMHS006.bigfish.com (10.236.130.16) with Microsoft SMTP Server id 14.1.225.23; Wed, 5 Jun 2013 18:00:54 +0000
Received: from ottsrv0015.microsemi.net ([134.199.15.151]) by ottsrv0014.microsemi.net with Microsoft SMTPSVC(6.0.3790.4675); Wed, 5 Jun 2013 14:00:54 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-Class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="----_=_NextPart_001_01CE6216.959AB4A8"
Date: Wed, 5 Jun 2013 14:00:37 -0400
Message-ID: <64683B4805156847B0ED373DAB3057CA01B19D5F@ottsrv0015.microsemi.net>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [TICTOC] comments on draft-ietf-tictoc-1588overmpls-04.txt
Thread-Index: AQHOHrvIG9Qp4DAEq0WS7lIAjM8M8JkmuDRwgAE3KqA=
References: <20130223072233.32735.89371.idtracker@ietfa.amsl.com> <64683B4805156847B0ED373DAB3057CA015E930D@ottsrv0015.microsemi.net> <4A6CE49E6084B141B15C0713B8993F281BE28013@SJEXCHMB12.corp.ad.broadcom.com>
From: "Meyer, Peter" <Peter.Meyer@microsemi.com>
To: Shahram Davari <davari@broadcom.com>, <tictoc@ietf.org>
X-OriginalArrivalTime: 05 Jun 2013 18:00:54.0120 (UTC) FILETIME=[9F449E80:01CE6216]
X-OriginatorOrg: microsemi.com
Subject: Re: [TICTOC] comments on draft-ietf-tictoc-1588overmpls-04.txt
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: Wed, 05 Jun 2013 18:01:37 -0000

------_=_NextPart_001_01CE6216.959AB4A8
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Hi Shahram,

I hope in-line with my comments I have edited the text of draft -04.

I'm not sure how the formatting worked out (PC-based, line length, page
length).

I modified sections 3, 4, 18, 19 & 20.

I include here both original and modified version so you can diff (most
of the changes in 3 are due to line length / re-org, not actual text
changes).

File attachment:
"draft-ietf-tictoc-1588overmpls-04-org.txt" (52 KB)
"draft-ietf-tictoc-1588overmpls-04-pm.txt" (53 KB)


Regards,
Peter


-----Original Message-----
From: Shahram Davari [mailto:davari@broadcom.com]=20
Sent: June 4, 2013 7:40 PM
To: Meyer, Peter; tictoc@ietf.org
Subject: RE: [TICTOC] comments on draft-ietf-tictoc-1588overmpls-04.txt

Hi Peter,

Thanks for your god comments. Please see my responses inline. Please let
me know whether you are satisfied with my responses since I am updating
the draft in the next couple of days.

Thanks
Shahram

-----Original Message-----
From: tictoc-bounces@ietf.org [mailto:tictoc-bounces@ietf.org] On Behalf
Of Meyer, Peter
Sent: Monday, March 11, 2013 5:49 PM
To: tictoc@ietf.org
Subject: Re: [TICTOC] comments on draft-ietf-tictoc-1588overmpls-04.txt

Hi Shahram et al,

Some comments on draft -04.


1) Section 3.  "A generic method is defined in this document that does
not require deep packet inspection at line rate, and can
deterministically identify Timing messages.  The generic method is
applicable to MPLS and MPLS-TP networks."

May want to add that this would apply only to one-step TC (I imagine
that is the point of the correction at line rate).  A two-step TC would
need to do deep packet inspection as it uses sourcePortIdentity &
sequenceId fields for Follow_up or Delay_Resp.

SD> For 2-step, all that is needed is for an interface to detect the
Timing message (based on top MPLS Label)  and record the Time along with
some information from the Timing packet and send them to CPU while
forwarding the Timing message as usual. Then the CPU based on the
information received generates Follow-up message and injects it in to
the LSP.  Therefore it is the job of CPU to look at sourcePortIdentity &
sequenceId fields not the Hardware.


2) Section 4.  "An MPLS domain can serve multiple customers.  This means
that the MPLS domain (maintained by a service provider) may provide
timing services to multiple customers, each having their own Timing
domain.  Therefore LER BCs need to interact with multiple grandmasters,
and consequently multiple time references."

This should be re-phrased.  It switches from an optional situation ("may
provide timing services") to mandatory situation ("LER BCs need to
interact").   Some words such as "in such a deployment scenario, ...."
and replace "can" with "may".   We have seen at ITU at least (with
participation from operators BT, FT, DT, CMCC, AT&T, Sprint, etc.) that
this multiple operator domain case was not useful enough to be included
in standardization process for Telecom networks.

SD> I rephrased it as following:

" An MPLS domain can serve multiple customers.  This means that the
   MPLS domain (maintained by a service provider) may provide timing
   services to multiple customers, each having their own Timing domain.
   Therefore in such deployment scenarios, LER BCs may interact with
multiple grandmasters,=20
and consequently multiple time references.  Also, LER/LSR TCs MUST be
synchronized to the=20
same master clock (which is the service provider Master clock), which
implies that they need=20
to choose one master to synchronize to."


3) Section 19.  "For transporting such peer delay measurement messages a
single-hop LSP SHOULD to be created between the two adjacent LSRs
engaged in peer delay measurement to carry peer delay measurement
messages. Other methods such as PTP transport over Ethernet MAY be used
for transporting peer delay measurement messages if the link between the
two routers is Ethernet."


This new statement to handle peer-delay (which in earlier drafts did not
have a communication path listed), also allows a BC to be embedded in an
LSR with a communication path between BC's as a single-hop LSP
(mentioned March 22, 2012 in my feedback to draft -03, subject "[TICTOC]
Updated 1588 over MPLS draf-03").

SD> When a single-hop LSP is created then I call the both ends of that
LSP, LERs and not LSRs.
Note that a router can act as LSR for some LSPs and LER for other LSPs.
The point is that we can't
Terminate a packet in the middle of an LSP (i.e., in an LSR). So BC
functionality can't exist in the middle
Of a PTP LSP. So I think it is a matter of terminology otherwise I agree
that you could have BC in the core
(not edge).=20

Architecture diagrams Figure 1 and Figure should be updated to reflect
the possibility of either BC or TC implementation.   Section 18.2 and
section 18.3 and section 21 should also be updated to reflect the
possibility of either BC or TC.  I understand the RFC is intended to be
generic and not targeted only at TC.



4) Section 20.  "When the MPLS network (provider network) serves
multiple customers, it is important to maintain and process each
customers clock and Timing messages separately from other customers to
ensure there is no cross- customer effect.   For example if an LER BC is
synchronized to a specific grandmaster, belonging to customer A, then
the LER MUST use that BC clock only for customer A to ensure that
customer A cannot attack other customers by manipulating its time."

This seems much more applicable to the TC LSR and should be stated.
>From section 4 we see the TC uses the primary synchronization domain
(that of the service provide) to correct PTP messages.

SD> I don't see how in a TC LSR, one customer timing can affect other
customer timings?
Since in a TC, we just update the Timestamp of a packet based on the
Service provider Time.
May be I have not understood your point. Could you please clarify with
an example.



5) Section 20.  "Timing messages (as opposed to regular customer data)
SHOULD not be encrypted or authenticated on an end-to-end basis."  I
think there is a security draft in parallel being developed that may be
relevant to that statement.

SD> I have updated the  text as following:

" Timing messages MAY be encrypted or authenticated, provided that the
LERs/LSRs that are Timing capable/aware can authenticate/ decrypt the
timing messages."




Regards,
Peter


-----Original Message-----
From: tictoc-bounces@ietf.org [mailto:tictoc-bounces@ietf.org] On Behalf
Of internet-drafts@ietf.org
Sent: February 23, 2013 2:23 AM
To: i-d-announce@ietf.org
Cc: tictoc@ietf.org
Subject: [TICTOC] I-D Action: draft-ietf-tictoc-1588overmpls-04.txt


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

	Title           : Transporting Timing messages over MPLS
Networks
	Author(s)       : Shahram Davari
                          Amit Oren
                          Manav Bhatia
                          Peter Roberts
                          Laurent Montini
	Filename        : draft-ietf-tictoc-1588overmpls-04.txt
	Pages           : 36
	Date            : 2013-02-22

Abstract:
   This document defines the method for transporting Timing messages
   such as PTP and NTP over an MPLS network.  The method allows for the
   easy identification of these PDUs at the port level to allow for port
   level processing of these PDUs in both LERs and LSRs.

   The basic idea is to transport Timing messages inside dedicated MPLS
   LSPs.  These LSPs only carry timing messages and possibly Control and
   Management packets, but they do not carry customer traffic.

   Two methods for transporting Timing messages over MPLS are defined.
   The first method is to transport Timing messages directly over the
   dedicated MPLS LSP via UDP/IP encapsulation, which is suitable for
   MPLS networks.  The second method is to transport Timing messages
   inside a PW via Ethernet encapsulation, which is suitable for both
   MPLS and MPLS-TP networks.


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

There's also a htmlized version available at:
http://tools.ietf.org/html/draft-ietf-tictoc-1588overmpls-04

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


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

_______________________________________________
TICTOC mailing list
TICTOC@ietf.org
https://www.ietf.org/mailman/listinfo/tictoc


_______________________________________________
TICTOC mailing list
TICTOC@ietf.org
https://www.ietf.org/mailman/listinfo/tictoc




------_=_NextPart_001_01CE6216.959AB4A8
Content-Type: text/plain; name="draft-ietf-tictoc-1588overmpls-04-org.txt"
Content-Transfer-Encoding: base64
Content-Description: draft-ietf-tictoc-1588overmpls-04-org.txt
Content-Disposition: attachment;
	filename="draft-ietf-tictoc-1588overmpls-04-org.txt"

DQoNCg0KVElDVE9DIFdvcmtpbmcgR3JvdXAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgUy4gRGF2YXJpDQpJbnRlcm5ldC1EcmFmdCAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgIEEuIE9yZW4NCkludGVuZGVkIHN0YXR1czog
U3RhbmRhcmRzIFRyYWNrICAgICAgICAgICAgICAgICAgICAgICAgICBCcm9hZGNvbSBDb3JwLg0K
RXhwaXJlczogQXVndXN0IDI3LCAyMDEzICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgTS4gQmhhdGlhDQogICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgIFAuIFJvYmVydHMNCiAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICBBbGNhdGVsLUx1Y2VudA0KICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICBM
LiBNb250aW5pDQogICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgIENpc2NvIFN5c3RlbXMNCiAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgICBGZWJydWFyeSAyMywgMjAxMw0KDQoNCiAgICAgICAg
ICAgIFRyYW5zcG9ydGluZyBUaW1pbmcgbWVzc2FnZXMgb3ZlciBNUExTIE5ldHdvcmtzDQogICAg
ICAgICAgICAgICAgICAgZHJhZnQtaWV0Zi10aWN0b2MtMTU4OG92ZXJtcGxzLTA0DQoNCkFic3Ry
YWN0DQoNCiAgIFRoaXMgZG9jdW1lbnQgZGVmaW5lcyB0aGUgbWV0aG9kIGZvciB0cmFuc3BvcnRp
bmcgVGltaW5nIG1lc3NhZ2VzDQogICBzdWNoIGFzIFBUUCBhbmQgTlRQIG92ZXIgYW4gTVBMUyBu
ZXR3b3JrLiAgVGhlIG1ldGhvZCBhbGxvd3MgZm9yIHRoZQ0KICAgZWFzeSBpZGVudGlmaWNhdGlv
biBvZiB0aGVzZSBQRFVzIGF0IHRoZSBwb3J0IGxldmVsIHRvIGFsbG93IGZvciBwb3J0DQogICBs
ZXZlbCBwcm9jZXNzaW5nIG9mIHRoZXNlIFBEVXMgaW4gYm90aCBMRVJzIGFuZCBMU1JzLg0KDQog
ICBUaGUgYmFzaWMgaWRlYSBpcyB0byB0cmFuc3BvcnQgVGltaW5nIG1lc3NhZ2VzIGluc2lkZSBk
ZWRpY2F0ZWQgTVBMUw0KICAgTFNQcy4gIFRoZXNlIExTUHMgb25seSBjYXJyeSB0aW1pbmcgbWVz
c2FnZXMgYW5kIHBvc3NpYmx5IENvbnRyb2wgYW5kDQogICBNYW5hZ2VtZW50IHBhY2tldHMsIGJ1
dCB0aGV5IGRvIG5vdCBjYXJyeSBjdXN0b21lciB0cmFmZmljLg0KDQogICBUd28gbWV0aG9kcyBm
b3IgdHJhbnNwb3J0aW5nIFRpbWluZyBtZXNzYWdlcyBvdmVyIE1QTFMgYXJlIGRlZmluZWQuDQog
ICBUaGUgZmlyc3QgbWV0aG9kIGlzIHRvIHRyYW5zcG9ydCBUaW1pbmcgbWVzc2FnZXMgZGlyZWN0
bHkgb3ZlciB0aGUNCiAgIGRlZGljYXRlZCBNUExTIExTUCB2aWEgVURQL0lQIGVuY2Fwc3VsYXRp
b24sIHdoaWNoIGlzIHN1aXRhYmxlIGZvcg0KICAgTVBMUyBuZXR3b3Jrcy4gIFRoZSBzZWNvbmQg
bWV0aG9kIGlzIHRvIHRyYW5zcG9ydCBUaW1pbmcgbWVzc2FnZXMNCiAgIGluc2lkZSBhIFBXIHZp
YSBFdGhlcm5ldCBlbmNhcHN1bGF0aW9uLCB3aGljaCBpcyBzdWl0YWJsZSBmb3IgYm90aA0KICAg
TVBMUyBhbmQgTVBMUy1UUCBuZXR3b3Jrcy4NCg0KU3RhdHVzIG9mIHRoaXMgTWVtbw0KDQogICBU
aGlzIEludGVybmV0LURyYWZ0IGlzIHN1Ym1pdHRlZCBpbiBmdWxsIGNvbmZvcm1hbmNlIHdpdGgg
dGhlDQogICBwcm92aXNpb25zIG9mIEJDUCA3OCBhbmQgQkNQIDc5Lg0KDQogICBJbnRlcm5ldC1E
cmFmdHMgYXJlIHdvcmtpbmcgZG9jdW1lbnRzIG9mIHRoZSBJbnRlcm5ldCBFbmdpbmVlcmluZw0K
ICAgVGFzayBGb3JjZSAoSUVURikuICBOb3RlIHRoYXQgb3RoZXIgZ3JvdXBzIG1heSBhbHNvIGRp
c3RyaWJ1dGUNCiAgIHdvcmtpbmcgZG9jdW1lbnRzIGFzIEludGVybmV0LURyYWZ0cy4gIFRoZSBs
aXN0IG9mIGN1cnJlbnQgSW50ZXJuZXQtDQogICBEcmFmdHMgaXMgYXQgaHR0cDovL2RhdGF0cmFj
a2VyLmlldGYub3JnL2RyYWZ0cy9jdXJyZW50Ly4NCg0KICAgSW50ZXJuZXQtRHJhZnRzIGFyZSBk
cmFmdCBkb2N1bWVudHMgdmFsaWQgZm9yIGEgbWF4aW11bSBvZiBzaXggbW9udGhzDQogICBhbmQg
bWF5IGJlIHVwZGF0ZWQsIHJlcGxhY2VkLCBvciBvYnNvbGV0ZWQgYnkgb3RoZXIgZG9jdW1lbnRz
IGF0IGFueQ0KICAgdGltZS4gIEl0IGlzIGluYXBwcm9wcmlhdGUgdG8gdXNlIEludGVybmV0LURy
YWZ0cyBhcyByZWZlcmVuY2UNCiAgIG1hdGVyaWFsIG9yIHRvIGNpdGUgdGhlbSBvdGhlciB0aGFu
IGFzICJ3b3JrIGluIHByb2dyZXNzLiINCg0KICAgVGhpcyBJbnRlcm5ldC1EcmFmdCB3aWxsIGV4
cGlyZSBvbiBBdWd1c3QgMjcsIDIwMTMuDQoNCg0KDQpEYXZhcmksIGV0IGFsLiAgICAgICAgICAg
RXhwaXJlcyBBdWd1c3QgMjcsIDIwMTMgICAgICAgICAgICAgICAgW1BhZ2UgMV0NCgwNCkludGVy
bmV0LURyYWZ0ICAgICAgICBUcmFuc3BvcnRpbmcgVGltaW5nIG92ZXIgTVBMUyAgICAgICAgRmVi
cnVhcnkgMjAxMw0KDQoNCkNvcHlyaWdodCBOb3RpY2UNCg0KICAgQ29weXJpZ2h0IChjKSAyMDEz
IElFVEYgVHJ1c3QgYW5kIHRoZSBwZXJzb25zIGlkZW50aWZpZWQgYXMgdGhlDQogICBkb2N1bWVu
dCBhdXRob3JzLiAgQWxsIHJpZ2h0cyByZXNlcnZlZC4NCg0KICAgVGhpcyBkb2N1bWVudCBpcyBz
dWJqZWN0IHRvIEJDUCA3OCBhbmQgdGhlIElFVEYgVHJ1c3QncyBMZWdhbA0KICAgUHJvdmlzaW9u
cyBSZWxhdGluZyB0byBJRVRGIERvY3VtZW50cw0KICAgKGh0dHA6Ly90cnVzdGVlLmlldGYub3Jn
L2xpY2Vuc2UtaW5mbykgaW4gZWZmZWN0IG9uIHRoZSBkYXRlIG9mDQogICBwdWJsaWNhdGlvbiBv
ZiB0aGlzIGRvY3VtZW50LiAgUGxlYXNlIHJldmlldyB0aGVzZSBkb2N1bWVudHMNCiAgIGNhcmVm
dWxseSwgYXMgdGhleSBkZXNjcmliZSB5b3VyIHJpZ2h0cyBhbmQgcmVzdHJpY3Rpb25zIHdpdGgg
cmVzcGVjdA0KICAgdG8gdGhpcyBkb2N1bWVudC4gIENvZGUgQ29tcG9uZW50cyBleHRyYWN0ZWQg
ZnJvbSB0aGlzIGRvY3VtZW50IG11c3QNCiAgIGluY2x1ZGUgU2ltcGxpZmllZCBCU0QgTGljZW5z
ZSB0ZXh0IGFzIGRlc2NyaWJlZCBpbiBTZWN0aW9uIDQuZSBvZg0KICAgdGhlIFRydXN0IExlZ2Fs
IFByb3Zpc2lvbnMgYW5kIGFyZSBwcm92aWRlZCB3aXRob3V0IHdhcnJhbnR5IGFzDQogICBkZXNj
cmliZWQgaW4gdGhlIFNpbXBsaWZpZWQgQlNEIExpY2Vuc2UuDQoNCg0KDQoNCg0KDQoNCg0KDQoN
Cg0KDQoNCg0KDQoNCg0KDQoNCg0KDQoNCg0KDQoNCg0KDQoNCg0KDQoNCg0KDQoNCg0KDQoNCkRh
dmFyaSwgZXQgYWwuICAgICAgICAgICBFeHBpcmVzIEF1Z3VzdCAyNywgMjAxMyAgICAgICAgICAg
ICAgICBbUGFnZSAyXQ0KDA0KSW50ZXJuZXQtRHJhZnQgICAgICAgIFRyYW5zcG9ydGluZyBUaW1p
bmcgb3ZlciBNUExTICAgICAgICBGZWJydWFyeSAyMDEzDQoNCg0KVGFibGUgb2YgQ29udGVudHMN
Cg0KICAgMS4gIEludHJvZHVjdGlvbiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4g
LiAuIC4gLiAuIC4gLiAuICA2DQoNCiAgIDIuICBUZXJtaW5vbG9neSAgLiAuIC4gLiAuIC4gLiAu
IC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAgOA0KDQogICAzLiAgUHJvYmxlbSBT
dGF0ZW1lbnQgIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gIDkN
Cg0KICAgNC4gIFRpbWluZyBvdmVyIE1QTFMgQXJjaGl0ZWN0dXJlICAuIC4gLiAuIC4gLiAuIC4g
LiAuIC4gLiAuIC4gLiAuIDEwDQoNCiAgIDUuICBEZWRpY2F0ZWQgTFNQcyBmb3IgVGltaW5nIG1l
c3NhZ2VzIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAxMg0KDQogICA2LiAgVGltaW5nIG92
ZXIgTFNQIEVuY2Fwc3VsYXRpb24gIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gMTMN
CiAgICAgNi4xLiAgVGltaW5nIG92ZXIgVURQL0lQIG92ZXIgTVBMUyBFbmNhcHN1bGF0aW9uIC4g
LiAuIC4gLiAuIC4gLiAxMw0KICAgICA2LjIuICBUaW1pbmcgb3ZlciBQVyBFbmNhcHN1bGF0aW9u
IC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIDEzDQogICAgIDYuMy4gIE90aGVyIFRpbWlu
ZyBFbmNhcHN1bGF0aW9uIG1ldGhvZHMgLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gMTQNCg0KICAg
Ny4gIFRpbWluZyBtZXNzYWdlIFByb2Nlc3NpbmcgIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4g
LiAuIC4gLiAuIDE1DQoNCiAgIDguICBQcm90ZWN0aW9uIGFuZCBSZWR1bmRhbmN5ICAuIC4gLiAu
IC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAxNg0KDQogICA5LiAgRUNNUCAuIC4gLiAuIC4g
LiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gMTcNCg0KICAg
MTAuIFBIUCAgLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4g
LiAuIC4gLiAuIDE4DQoNCiAgIDExLiBFbnRyb3B5ICAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAu
IC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAxOQ0KDQogICAxMi4gT0FNLCBDb250cm9sIGFu
ZCBNYW5hZ2VtZW50ICAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gMjANCg0KICAg
MTMuIFFvUyBDb25zaWRlcmF0aW9ucyAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4g
LiAuIC4gLiAuIDIxDQoNCiAgIDE0LiBGQ1MgUmVjYWxjdWxhdGlvbiAgLiAuIC4gLiAuIC4gLiAu
IC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAyMg0KDQogICAxNS4gVURQIENoZWNrc3VtIENv
cnJlY3Rpb24gIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gMjMNCg0KICAg
MTYuIFJvdXRpbmcgZXh0ZW5zaW9ucyBmb3IgVGltaW5nLWF3YXJlIFJvdXRlcnMgIC4gLiAuIC4g
LiAuIC4gLiAuIDI0DQoNCiAgIDE3LiBTaWduYWxpbmcgRXh0ZW5zaW9ucyBmb3IgQ3JlYXRpbmcg
VGltaW5nIExTUHMgIC4gLiAuIC4gLiAuIC4gLiAyNQ0KDQogICAxOC4gQmVoYXZpb3Igb2YgTEVS
L0xTUiAgLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gMjYNCiAgICAg
MTguMS4gQmVoYXZpb3Igb2YgVGltaW5nLWNhcGFibGUvYXdhcmUgTEVSIC4gLiAuIC4gLiAuIC4g
LiAuIC4gLiAyNg0KICAgICAxOC4yLiBCZWhhdmlvciBvZiBUaW1pbmctY2FwYWJsZS9hd2FyZSBM
U1IgLiAuIC4gLiAuIC4gLiAuIC4gLiAuIDI2DQogICAgIDE4LjMuIEJlaGF2aW9yIG9mIG5vbi1U
aW1pbmctY2FwYWJsZS9hd2FyZSBMU1IgLiAuIC4gLiAuIC4gLiAuIC4gMjYNCg0KICAgMTkuIE90
aGVyIGNvbnNpZGVyYXRpb25zIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4g
LiAuIDI4DQoNCiAgIDIwLiBTZWN1cml0eSBDb25zaWRlcmF0aW9ucyAgLiAuIC4gLiAuIC4gLiAu
IC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAyOQ0KDQoNCg0KDQpEYXZhcmksIGV0IGFsLiAgICAgICAg
ICAgRXhwaXJlcyBBdWd1c3QgMjcsIDIwMTMgICAgICAgICAgICAgICAgW1BhZ2UgM10NCgwNCklu
dGVybmV0LURyYWZ0ICAgICAgICBUcmFuc3BvcnRpbmcgVGltaW5nIG92ZXIgTVBMUyAgICAgICAg
RmVicnVhcnkgMjAxMw0KDQoNCiAgIDIxLiBBcHBsaWNhYmlsaXR5IFN0YXRlbWVudCAgLiAuIC4g
LiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAzMA0KDQogICAyMi4gQWNrbm93bGVkZ2Vt
ZW50cyAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gMzENCg0K
ICAgMjMuIElBTkEgQ29uc2lkZXJhdGlvbnMgIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAu
IC4gLiAuIC4gLiAuIDMyDQoNCiAgIDI0LiBSZWZlcmVuY2VzIC4gLiAuIC4gLiAuIC4gLiAuIC4g
LiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAzMw0KICAgICAyNC4xLiBOb3JtYXRpdmUg
UmVmZXJlbmNlcyAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIDMzDQogICAg
IDI0LjIuIEluZm9ybWF0aXZlIFJlZmVyZW5jZXMgLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAu
IC4gLiAuIC4gMzMNCg0KICAgQXV0aG9ycycgQWRkcmVzc2VzIC4gLiAuIC4gLiAuIC4gLiAuIC4g
LiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIDM2DQoNCg0KDQoNCg0KDQoNCg0KDQoNCg0KDQoN
Cg0KDQoNCg0KDQoNCg0KDQoNCg0KDQoNCg0KDQoNCg0KDQoNCg0KDQoNCg0KDQoNCg0KDQoNCkRh
dmFyaSwgZXQgYWwuICAgICAgICAgICBFeHBpcmVzIEF1Z3VzdCAyNywgMjAxMyAgICAgICAgICAg
ICAgICBbUGFnZSA0XQ0KDA0KSW50ZXJuZXQtRHJhZnQgICAgICAgIFRyYW5zcG9ydGluZyBUaW1p
bmcgb3ZlciBNUExTICAgICAgICBGZWJydWFyeSAyMDEzDQoNCg0KICAgVGhlIGtleSB3b3JkcyAi
TVVTVCIsICJNVVNUIE5PVCIsICJSRVFVSVJFRCIsICJTSEFMTCIsICJTSEFMTCBOT1QiLA0KICAg
IlNIT1VMRCIsICJTSE9VTEQgTk9UIiwgIlJFQ09NTUVOREVEIiwgIk1BWSIsIGFuZCAiT1BUSU9O
QUwiIGluIHRoaXMNCiAgIGRvY3VtZW50IGFyZSB0byBiZSBpbnRlcnByZXRlZCBhcyBkZXNjcmli
ZWQgaW4gUkZDMjExOSBbUkZDMjExOV0uDQoNCiAgIFdoZW4gdXNlZCBpbiBsb3dlciBjYXNlLCB0
aGVzZSB3b3JkcyBjb252ZXkgdGhlaXIgdHlwaWNhbCB1c2UgaW4NCiAgIGNvbW1vbiBsYW5ndWFn
ZSwgYW5kIGFyZSBub3QgdG8gYmUgaW50ZXJwcmV0ZWQgYXMgZGVzY3JpYmVkIGluDQogICBSRkMy
MTE5IFtSRkMyMTE5XS4NCg0KDQoNCg0KDQoNCg0KDQoNCg0KDQoNCg0KDQoNCg0KDQoNCg0KDQoN
Cg0KDQoNCg0KDQoNCg0KDQoNCg0KDQoNCg0KDQoNCg0KDQoNCg0KDQoNCg0KDQpEYXZhcmksIGV0
IGFsLiAgICAgICAgICAgRXhwaXJlcyBBdWd1c3QgMjcsIDIwMTMgICAgICAgICAgICAgICAgW1Bh
Z2UgNV0NCgwNCkludGVybmV0LURyYWZ0ICAgICAgICBUcmFuc3BvcnRpbmcgVGltaW5nIG92ZXIg
TVBMUyAgICAgICAgRmVicnVhcnkgMjAxMw0KDQoNCjEuICBJbnRyb2R1Y3Rpb24NCg0KICAgVGhl
IG9iamVjdGl2ZSBvZiBQcmVjaXNpb24gVGltZSBQcm90b2NvbCAoUFRQKSBhbmQgTmV0d29yayBU
aW1pbmcNCiAgIFByb3RvY29sIChOVFApIGFyZSB0byBzeW5jaHJvbml6ZSBpbmRlcGVuZGVudCBj
bG9ja3MgcnVubmluZyBvbg0KICAgc2VwYXJhdGUgbm9kZXMgb2YgYSBkaXN0cmlidXRlZCBzeXN0
ZW0uDQoNCiAgIFtJRUVFXSBkZWZpbmVzIFBUUCBtZXNzYWdlcyBmb3IgZnJlcXVlbmN5LCBwaGFz
ZSBhbmQgdGltZQ0KICAgc3luY2hyb25pemF0aW9uLiAgVGhlIFBUUCBtZXNzYWdlcyBpbmNsdWRl
IFBUUCBQRFVzIG92ZXIgVURQL0lQDQogICAoQW5uZXggRCBhbmQgRSBvZiBbSUVFRV0pIGFuZCBQ
VFAgUERVcyBvdmVyIEV0aGVybmV0IChBbm5leCBGIG9mDQogICBbSUVFRS0gMTU4OF0pLiAgVGhp
cyBkb2N1bWVudCBkZWZpbmVzIG1hcHBpbmcgYW5kIHRyYW5zcG9ydCBvZiB0aGUNCiAgIFBUUCBt
ZXNzYWdlcyBkZWZpbmVkIGluIFtJRUVFXSBvdmVyIE1QTFMvTVBMUy1UUCBuZXR3b3Jrcy4gIFBU
UA0KICAgZGVmaW5lcyBzZXZlcmFsIGNsb2NrIHR5cGVzOiBvcmRpbmFyeSBjbG9ja3MsIGJvdW5k
YXJ5IGNsb2NrcywgZW5kLQ0KICAgdG8tZW5kIHRyYW5zcGFyZW50IGNsb2NrcywgYW5kIHBlZXIt
dG8tcGVlciB0cmFuc3BhcmVudCBjbG9ja3MuDQogICBUcmFuc3BhcmVudCBjbG9ja3MgcmVxdWly
ZSBpbnRlcm1lZGlhdGUgbm9kZXMgdG8gdXBkYXRlIGNvcnJlY3Rpb24NCiAgIGZpZWxkIGluc2lk
ZSBQVFAgbWVzc2FnZSB0aGF0IHJlZmxlY3RzIHRoZSB0cmFuc2l0IHRpbWUgaW4gdGhlIG5vZGUu
DQoNCiAgIFtSRkM1OTA1XSBkZWZpbmVzIE5UUCBtZXNzYWdlcyBmb3IgY2xvY2sgYW5kIHRpbWUg
c3luY2hyb25pemF0aW9uLg0KICAgVGhlIFBUUCBtZXNzYWdlcyAoUERVcykgYXJlIHRyYW5zcG9y
dGVkIG92ZXIgVURQL0lQLiAgVGhpcyBkb2N1bWVudA0KICAgZGVmaW5lcyBtYXBwaW5nIGFuZCB0
cmFuc3BvcnQgb2YgdGhlIE5UUCBtZXNzYWdlcyBkZWZpbmVkIGluDQogICBbUkZDNTkwNV0gb3Zl
ciBNUExTIG5ldHdvcmtzLg0KDQogICBPbmUga2V5IGF0dHJpYnV0ZSBvZiBhbGwgb2YgdGhlc2Ug
VGltaW5nIG1lc3NhZ2VzIGlzIHRoYXQgdGhlIFRpbWUNCiAgIHN0YW1wIHByb2Nlc3Npbmcgc2hv
dWxkIG9jY3VyIGFzIGNsb3NlIGFzIHBvc3NpYmxlIHRvIHRoZSBhY3R1YWwNCiAgIHRyYW5zbWlz
c2lvbiBhbmQgcmVjZXB0aW9uIGF0IHRoZSBwaHlzaWNhbCBwb3J0IGludGVyZmFjZS4gIFRoaXMN
CiAgIHRhcmdldHMgb3B0aW1hbCB0aW1lIGFuZC9vciBmcmVxdWVuY3kgcmVjb3ZlcnkgYnkgYXZv
aWRpbmcgdmFyaWFibGUNCiAgIGRlbGF5IGludHJvZHVjZWQgYnkgcXVldWVzIGludGVybmFsIHRv
IHRoZSBjbG9ja3MuDQoNCiAgIFRvIGZhY2lsaXRhdGUgdGhlIGZhc3QgYW5kIGVmZmljaWVudCBy
ZWNvZ25pdGlvbiBvZiBUaW1pbmcgbWVzc2FnZXMNCiAgIGF0IHRoZSBwb3J0IGxldmVsIHdoZW4g
dGhlIFRpbWluZyBtZXNzYWdlcyBhcmUgY2FycmllZCBvdmVyIE1QTFMNCiAgIExTUHMsIHRoaXMg
ZG9jdW1lbnQgZGVmaW5lcyB0aGUgc3BlY2lmaWMgZW5jYXBzdWxhdGlvbnMgdGhhdCBzaG91bGQN
CiAgIGJlIHVzZWQuICBJbiBhZGRpdGlvbiwgaXQgY2FuIGJlIGV4cGVjdGVkIHRoYXQgdGhlcmUg
d2lsbCBleGlzdCBMU1IvDQogICBMRVJzIHdoZXJlIG9ubHkgYSBzdWJzZXQgb2YgdGhlIHBoeXNp
Y2FsIHBvcnRzIHdpbGwgaGF2ZSB0aGUgcG9ydC0NCiAgIGJhc2VkIFRpbWluZyBtZXNzYWdlIHBy
b2Nlc3NpbmcgY2FwYWJpbGl0aWVzLiAgSW4gb3JkZXIgdG8gZW5zdXJlDQogICB0aGF0IHRoZSBM
U1BzIGNhcnJ5aW5nIFRpbWluZyBwYWNrZXRzIGFsd2F5cyBlbnRlciBhbmQgZXhpdCBwb3J0cw0K
ICAgd2l0aCB0aGlzIGNhcGFiaWxpdHksIHJvdXRpbmcgZXh0ZW5zaW9ucyBhcmUgZGVmaW5lZCB0
byBhZHZlcnRpc2UNCiAgIHRoaXMgY2FwYWJpbGl0eSBvbiBhIHBvcnQgYmFzaXMgYW5kIHRvIGFs
bG93IGZvciB0aGUgZXN0YWJsaXNobWVudCBvZg0KICAgTFNQcyB0aGF0IG9ubHkgdHJhbnNpdCBz
dWNoIHBvcnRzLiAgV2hpbGUgdGhpcyBwYXRoIGVzdGFibGlzaG1lbnQNCiAgIHJlc3RyaWN0aW9u
IG1heSBiZSBhcHBsaWVkIG9ubHkgYXQgdGhlIExFUiBJbmdyZXNzIGFuZC9vciBlZ3Jlc3MNCiAg
IHBvcnRzLCBpdCBiZWNvbWVzIG1vcmUgaW1wb3J0YW50IHdoZW4gdXNpbmcgdHJhbnNwYXJlbnQg
Y2xvY2sgY2FwYWJsZQ0KICAgTFNScyBpbiB0aGUgcGF0aC4NCg0KICAgUG9ydCBiYXNlZCBUaW1p
bmcgbWVzc2FnZSBwcm9jZXNzaW5nIGludm9sdmVzIFRpbWluZyBtZXNzYWdlDQogICByZWNvZ25p
dGlvbi4gIE9uY2UgdGhlIFRpbWluZyBtZXNzYWdlcyBhcmUgcmVjb2duaXplZCB0aGV5IGNhbiBi
ZQ0KICAgbW9kaWZpZWQgYmFzZWQgb24gdGhlIHJlY2VwdGlvbiBvciB0cmFuc21pc3Npb24gVGlt
ZS1zdGFtcC4NCg0KICAgVGhpcyBkb2N1bWVudCBwcm92aWRlcyB0d28gbWV0aG9kcyBmb3IgdHJh
bnNwb3J0aW5nIFRpbWluZyBtZXNzYWdlcw0KICAgb3ZlciBNUExTLiAgT25lIGlzIGFwcGxpY2Fi
bGUgdG8gTVBMUyBlbnZpcm9ubWVudCBhbmQgdGhlIG90aGVyIG9uZQ0KICAgaXMgYXBwbGljYWJs
ZSB0byBib3RoIE1QTFMgYW5kIE1QTFMtVFAgZW52aXJvbm1lbnQuDQoNCg0KDQpEYXZhcmksIGV0
IGFsLiAgICAgICAgICAgRXhwaXJlcyBBdWd1c3QgMjcsIDIwMTMgICAgICAgICAgICAgICAgW1Bh
Z2UgNl0NCgwNCkludGVybmV0LURyYWZ0ICAgICAgICBUcmFuc3BvcnRpbmcgVGltaW5nIG92ZXIg
TVBMUyAgICAgICAgRmVicnVhcnkgMjAxMw0KDQoNCiAgIFRoZSBzb2x1dGlvbiBpbnZvbHZlcyB0
cmFuc3BvcnRpbmcgVGltaW5nIG1lc3NhZ2VzIG92ZXIgZGVkaWNhdGVkDQogICBMU1BzIGNhbGxl
ZCBUaW1pbmcgTFNQcy4gIFRoZXNlIExTUHMgY2FycnkgVGltaW5nIG1lc3NhZ2VzIGFuZCBNQVkN
CiAgIGNhcnJ5IE1hbmFnZW1lbnQgYW5kIGNvbnRyb2wgbWVzc2FnZXMsIGJ1dCBub3QgZGF0YSBw
bGFuZSBjbGllbnQNCiAgIHRyYWZmaWMuICBUaW1pbmcgTFNQcyBjYW4gYmUgZXN0YWJsaXNoZWQg
c3RhdGljYWxseSBvciB2aWEgc2lnbmFsaW5nLg0KICAgRXh0ZW5zaW9ucyB0byBjb250cm9sIHBs
YW5lIChPU1BGLCBJU0lTLCBldGMuKSBpcyByZXF1aXJlZCB0byBlbmFibGUNCiAgIHJvdXRlcnMg
dG8gZGlzdHJpYnV0ZSB0aGVpciBUaW1pbmcgcHJvY2Vzc2luZyBjYXBhYmlsaXRpZXMgb3ZlciBN
UExTDQogICB0byBvdGhlciByb3V0ZXJzLiAgSG93ZXZlciBzdWNoIGV4dGVuc2lvbnMgYXJlIG91
dHNpZGUgdGhlIHNjb3BlIG9mDQogICB0aGlzIGRvY3VtZW50Lg0KDQogICBFeHRlbnNpb25zIHRv
IHNpZ25hbGluZyBwcm90b2NvbHMgKGUuZy4sIFJTVlAtVEUpIGFyZSByZXF1aXJlZCBmb3INCiAg
IGVzdGFibGlzaGluZyBQVFAgTFNQcy4gIEhvd2V2ZXIgc3VjaCBleHRlbnNpb25zIGFyZSBvdXRz
aWRlIHRoZSBzY29wZQ0KICAgb2YgdGhpcyBkb2N1bWVudC4NCg0KICAgV2hpbGUgdGhlIHRlY2hu
aXF1ZXMgaW5jbHVkZWQgaGVyZWluIGFsbG93IGZvciB0aGUgZXN0YWJsaXNobWVudCBvZg0KICAg
cGF0aHMgb3B0aW1pemVkIHRvIGluY2x1ZGUgVGltZS1zdGFtcGluZyBjYXBhYmxlIGxpbmtzLCB0
aGUNCiAgIHBlcmZvcm1hbmNlIG9mIHRoZSBTbGF2ZSBjbG9ja3MgaXMgb3V0c2lkZSB0aGUgc2Nv
cGUgb2YgdGhpcw0KICAgZG9jdW1lbnQuDQoNCiAgIEF0IHRoZSB0aW1lIG9mIHB1Ymxpc2hpbmcg
dGhpcyBzcGVjaWZpY2F0aW9uLCBUcmFuc3BhcmVudCBDbG9ja2luZw0KICAgKFRDKSBpcyBvbmx5
IGRlZmluZWQgZm9yIFBUUC4gIFRoZXJlZm9yZSBhdCB0aGlzIHRpbWUgYW55IHBhcnQgb2YNCiAg
IHRoaXMgc3BlY2lmaWNhdGlvbiB0aGF0IHRhbGtzIGFib3V0IFRyYW5zcGFyZW50IENsb2NraW5n
IGFwcGxpZXMgb25seQ0KICAgdG8gUFRQLg0KDQoNCg0KDQoNCg0KDQoNCg0KDQoNCg0KDQoNCg0K
DQoNCg0KDQoNCg0KDQoNCg0KDQoNCg0KDQoNCkRhdmFyaSwgZXQgYWwuICAgICAgICAgICBFeHBp
cmVzIEF1Z3VzdCAyNywgMjAxMyAgICAgICAgICAgICAgICBbUGFnZSA3XQ0KDA0KSW50ZXJuZXQt
RHJhZnQgICAgICAgIFRyYW5zcG9ydGluZyBUaW1pbmcgb3ZlciBNUExTICAgICAgICBGZWJydWFy
eSAyMDEzDQoNCg0KMi4gIFRlcm1pbm9sb2d5DQoNCiAgIDE1ODg6IFRoZSB0aW1pbmcgYW5kIHN5
bmNocm9uaXphdGlvbiBhcyBkZWZpbmVkIGJ5IElFRUUgMTU4OC4NCg0KICAgTlRQOiBUaGUgdGlt
aW5nIGFuZCBzeW5jaHJvbml6YXRpb24gcHJvdG9jb2wgZGVmaW5lZCBieSBJRVRGIFJGQy0xMzA1
DQogICBhbmQgUkZDLTU5MDUuDQoNCiAgIFBUUDogVGhlIHRpbWluZyBhbmQgc3luY2hyb25pemF0
aW9uIHByb3RvY29sIHVzZWQgYnkgMTU4OC4NCg0KICAgTWFzdGVyIENsb2NrOiBUaGUgc291cmNl
IG9mIDE1ODggdGltaW5nIHRvIGEgc2V0IG9mIHNsYXZlIGNsb2Nrcy4NCg0KICAgTWFzdGVyIFBv
cnQ6IEEgcG9ydCBvbiBhIG9yZGluYXJ5IG9yIGJvdW5kYXJ5IGNsb2NrIHRoYXQgaXMgaW4gTWFz
dGVyDQogICBzdGF0ZS4gIFRoaXMgaXMgdGhlIHNvdXJjZSBvZiB0aW1pbmcgdG93YXJkIHNsYXZl
IHBvcnRzLg0KDQogICBTbGF2ZSBDbG9jazogQSByZWNlaXZlciBvZiAxNTg4IHRpbWluZyBmcm9t
IGEgbWFzdGVyIGNsb2NrLg0KDQogICBTbGF2ZSBQb3J0OiBBIHBvcnQgb24gYSBib3VuZGFyeSBj
bG9jayBvciBvcmRpbmFyeSBjbG9jayB0aGF0IGlzDQogICByZWNlaXZpbmcgdGltaW5nIGZyb20g
YSBtYXN0ZXIgY2xvY2suDQoNCiAgIE9yZGluYXJ5IENsb2NrOiBBIGRldmljZSB3aXRoIGEgc2lu
Z2xlIFBUUCBwb3J0Lg0KDQogICBUcmFuc3BhcmVudCBDbG9jay4gIEEgZGV2aWNlIHRoYXQgbWVh
c3VyZXMgdGhlIHRpbWUgdGFrZW4gZm9yIGEgUFRQDQogICBldmVudCBtZXNzYWdlIHRvIHRyYW5z
aXQgdGhlIGRldmljZSBhbmQgdGhlbiB1cGRhdGVzIHRoZQ0KICAgY29ycmVjdGlvbkZpZWxkIG9m
IHRoZSBtZXNzYWdlIHdpdGggdGhpcyB0cmFuc2l0IHRpbWUuDQoNCiAgIEJvdW5kYXJ5IENsb2Nr
OiBBIGRldmljZSB3aXRoIG1vcmUgdGhhbiBvbmUgUFRQIHBvcnQuICBHZW5lcmFsbHkNCiAgIGJv
dW5kYXJ5IGNsb2NrcyB3aWxsIGhhdmUgb25lIHBvcnQgaW4gc2xhdmUgc3RhdGUgdG8gcmVjZWl2
ZSB0aW1pbmcNCiAgIGFuZCB0aGVuIG90aGVyIHBvcnRzIGluIG1hc3RlciBzdGF0ZSB0byByZS1k
aXN0cmlidXRlIHRoZSB0aW1pbmcuDQoNCiAgIFBUUCBMU1A6IEFuIExTUCBkZWRpY2F0ZWQgdG8g
Y2FycnkgUFRQIG1lc3NhZ2VzDQoNCiAgIFBUUCBQVzogQSBQVyB3aXRoaW4gYSBQVFAgTFNQIHRo
YXQgaXMgZGVkaWNhdGVkIHRvIGNhcnJ5IFBUUA0KICAgbWVzc2FnZXMuDQoNCiAgIENXOiBQc2V1
ZG93aXJlIENvbnRyb2wgV29yZA0KDQogICBMQUc6IExpbmsgQWdncmVnYXRpb24NCg0KICAgRUNN
UDogRXF1YWwgQ29zdCBNdWx0aXBhdGgNCg0KICAgQ0Y6IENvcnJlY3Rpb24gRmllbGQsIGEgZmll
bGQgaW5zaWRlIGNlcnRhaW4gUFRQIG1lc3NhZ2VzIChtZXNzYWdlDQogICB0eXBlIDAtMyl0aGF0
IGhvbGRzIHRoZSBhY2N1bXVsYXRpdmUgdHJhbnNpdCB0aW1lIGluc2lkZSBpbnRlcm1lZGlhdGUN
CiAgIHN3aXRjaGVzDQoNCiAgIFRpbWluZyBtZXNzYWdlczogVGltaW5nIFByb3RvY29sIG1lc3Nh
Z2VzIHRoYXQgYXJlIGV4Y2hhbmdlZCBiZXR3ZWVuDQogICByb3V0ZXJzIGluIG9yZGVyIHRvIGVz
dGFibGlzaCBhIHN5bmNocm9uaXplZCBjbG9jay4NCg0KDQoNCg0KDQpEYXZhcmksIGV0IGFsLiAg
ICAgICAgICAgRXhwaXJlcyBBdWd1c3QgMjcsIDIwMTMgICAgICAgICAgICAgICAgW1BhZ2UgOF0N
CgwNCkludGVybmV0LURyYWZ0ICAgICAgICBUcmFuc3BvcnRpbmcgVGltaW5nIG92ZXIgTVBMUyAg
ICAgICAgRmVicnVhcnkgMjAxMw0KDQoNCjMuICBQcm9ibGVtIFN0YXRlbWVudA0KDQogICBbSUVF
RV0gaGFzIGRlZmluZWQgbWV0aG9kcyBmb3IgdHJhbnNwb3J0aW5nIFBUUCBtZXNzYWdlcyBvdmVy
DQogICBFdGhlcm5ldCBhbmQgSVAgbmV0d29ya3MuICBbUkZDNTkwNV0gaGFzIGRlZmluZWQgdGhl
IG1ldGhvZCBvZg0KICAgdHJhbnNwb3J0aW5nIE5UUCBtZXNzYWdlcyBvdmVyIElQIG5ldHdvcmtz
LiAgVGhlcmUgaXMgYSBuZWVkIHRvDQogICB0cmFuc3BvcnQgVGltaW5nIG1lc3NhZ2VzIG92ZXIg
TVBMUyBuZXR3b3JrcyB3aGlsZSBzdXBwb3J0aW5nIHRoZQ0KICAgVHJhbnNwYXJlbnQgQ2xvY2sg
KFRDKSwgQm91bmRhcnkgQ2xvY2sgKEJDKSBhbmQgT3JkaW5hcnkgQ2xvY2sgKE9DKQ0KICAgZnVu
Y3Rpb25hbGl0eSBpbiB0aGUgTEVSIGFuZCBMU1JzIGluIHRoZSBNUExTIG5ldHdvcmsuDQoNCiAg
IFRoZXJlIGFyZSBtdWx0aXBsZSB3YXlzIG9mIHRyYW5zcG9ydGluZyBUaW1pbmcgb3ZlciBNUExT
LiAgSG93ZXZlciwNCiAgIHRoZXJlIGlzIGEgcmVxdWlyZW1lbnQgdG8gbGltaXQgdGhlIHBvc3Np
YmxlIGVuY2Fwc3VsYXRpb24gb3B0aW9ucyB0bw0KICAgc2ltcGxpZnkgdGhlIFRpbWluZyBtZXNz
YWdlIGlkZW50aWZpY2F0aW9uIGFuZCBwcm9jZXNzaW5nIHJlcXVpcmVkIGF0DQogICB0aGUgcG9y
dCBsZXZlbC4NCg0KICAgV2hlbiBUaW1pbmctYXdhcmVuZXNzIGlzIG5lZWRlZCwgVGltaW5nIG1l
c3NhZ2VzIHNob3VsZCBub3QgYmUNCiAgIHRyYW5zcG9ydGVkIG92ZXIgTFNQcyBvciBQV3MgdGhh
dCBhcmUgY2FycnlpbmcgY3VzdG9tZXIgdHJhZmZpYw0KICAgYmVjYXVzZSBMU1JzIHBlcmZvcm0g
TGFiZWwgc3dpdGNoaW5nIGJhc2VkIG9uIHRoZSB0b3AgbGFiZWwgaW4gdGhlDQogICBzdGFjay4g
IFRvIGRldGVjdCBUaW1pbmcgbWVzc2FnZXMgaW5zaWRlIHN1Y2ggTFNQcyByZXF1aXJlIHNwZWNp
YWwNCiAgIGhhcmR3YXJlIHRvIGRvIGRlZXAgcGFja2V0IGluc3BlY3Rpb24gYXQgbGluZSByYXRl
LiAgRXZlbiBpZiBzdWNoDQogICBoYXJkd2FyZSBleGlzdHMsIHRoZSBwYXlsb2FkIGNhbnQgYmUg
ZGV0ZXJtaW5pc3RpY2FsbHkgaWRlbnRpZmllZCBieQ0KICAgTFNScyBiZWNhdXNlIHRoZSBwYXls
b2FkIHR5cGUgaXMgYSBjb250ZXh0IG9mIHRoZSBQVyBsYWJlbCwgYW5kIHRoZQ0KICAgUFcgbGFi
ZWwgYW5kIGl0cyBjb250ZXh0IGFyZSBvbmx5IGtub3duIHRvIHRoZSBFZGdlIHJvdXRlcnMgKFBF
cy8NCiAgIExFUnMpOyBMU1JzIGRvbnQga25vdyB3aGF0IGlzIGEgUFdzIHBheWxvYWQgKEV0aGVy
bmV0LCBBVE0sIEZSLCBDRVMsDQogICBldGMpLiAgRXZlbiBpZiBvbmUgcmVzdHJpY3RzIGFuIExT
UCB0byBvbmx5IGNhcnJ5IEV0aGVybmV0IFBXcywgdGhlDQogICBMU1JzIGRvbnQgaGF2ZSB0aGUg
a25vd2xlZGdlIG9mIHdoZXRoZXIgUFcgQ29udHJvbCBXb3JkIChDVykgaXMNCiAgIHByZXNlbnQg
b3Igbm90IGFuZCB0aGVyZWZvcmUgY2FuIG5vdCBkZXRlcm1pbmlzdGljYWxseSBpZGVudGlmeSB0
aGUNCiAgIHBheWxvYWQuDQoNCiAgIEEgZ2VuZXJpYyBtZXRob2QgaXMgZGVmaW5lZCBpbiB0aGlz
IGRvY3VtZW50IHRoYXQgZG9lcyBub3QgcmVxdWlyZQ0KICAgZGVlcCBwYWNrZXQgaW5zcGVjdGlv
biBhdCBsaW5lIHJhdGUsIGFuZCBjYW4gZGV0ZXJtaW5pc3RpY2FsbHkNCiAgIGlkZW50aWZ5IFRp
bWluZyBtZXNzYWdlcy4gIFRoZSBnZW5lcmljIG1ldGhvZCBpcyBhcHBsaWNhYmxlIHRvIE1QTFMN
CiAgIGFuZCBNUExTLVRQIG5ldHdvcmtzLg0KDQoNCg0KDQoNCg0KDQoNCg0KDQoNCg0KDQoNCg0K
DQoNCg0KDQpEYXZhcmksIGV0IGFsLiAgICAgICAgICAgRXhwaXJlcyBBdWd1c3QgMjcsIDIwMTMg
ICAgICAgICAgICAgICAgW1BhZ2UgOV0NCgwNCkludGVybmV0LURyYWZ0ICAgICAgICBUcmFuc3Bv
cnRpbmcgVGltaW5nIG92ZXIgTVBMUyAgICAgICAgRmVicnVhcnkgMjAxMw0KDQoNCjQuICBUaW1p
bmcgb3ZlciBNUExTIEFyY2hpdGVjdHVyZQ0KDQogICBUaW1pbmcgbWVzc2FnZXMgYXJlIGV4Y2hh
bmdlIGJldHdlZW4gVGltaW5nIHBvcnRzIG9uIG9yZGluYXJ5IGFuZA0KICAgYm91bmRhcnkgY2xv
Y2tzLiAgQm91bmRhcnkgY2xvY2tzIHRlcm1pbmF0ZSB0aGUgVGltaW5nIG1lc3NhZ2VzIGFuZA0K
ICAgYWN0IGFzIG1hc3RlciBmb3Igb3RoZXIgYm91bmRhcnkgY2xvY2tzIG9yIGZvciBzbGF2ZSBj
bG9ja3MuICBFbmQtdG8tDQogICBFbmQgVHJhbnNwYXJlbnQgY2xvY2tzIGRvIG5vdCB0ZXJtaW5h
dGUgdGhlIFRpbWluZyBtZXNzYWdlcyBidXQgdGhleQ0KICAgZG8gbW9kaWZ5IHRoZSBjb250ZW50
cyBvZiB0aGUgVGltaW5nIG1lc3NhZ2VzIGFzIHRoZXkgdHJhbnNpdCBhY3Jvc3MNCiAgIHRoZSB0
cmFuc3BhcmVudCBjbG9jay4NCg0KICAgTWFzdGVyL1NsYXZlIGNsb2NrIGNvdWxkIGJlIGludGVn
cmF0ZWQgaW4gdGhlIExFUnMuICBBbiBleGFtcGxlIGlzDQogICBzaG93biBpbiBGaWd1cmUgMSwg
d2hlcmUgdGhlIExFUnMgYWN0IGFzIE9yZGluYXJ5IENsb2NrIChPQykgYW5kIGFyZQ0KICAgdGhl
IGluaXRpYXRpbmcvdGVybWluYXRpbmcgcG9pbnQgZm9yIFRpbWluZyBtZXNzYWdlcy4gIFRoZSBp
bmdyZXNzDQogICBMRVIgZW5jYXBzdWxhdGVzIHRoZSBUaW1pbmcgbWVzc2FnZXMgaW4gVGltaW5n
IExTUCBhbmQgdGhlIEVncmVzcyBMRVINCiAgIHRlcm1pbmF0ZXMgdGhlIFRpbWluZyBMU1AuICBU
aGUgTFNScyBhY3QgYXMgVHJhbnNwYXJlbnQgQ2xvY2sgKFRDKQ0KICAgYW5kIGp1c3QgdXBkYXRl
IHRoZSBUaW1pbmcgZmllbGQgaW4gdGhlIFRpbWluZyBtZXNzYWdlcy4NCg0KDQogICAgICArLS0t
LS0tLS0rICAgICArLS0tLS0tLSsgICAgICstLS0tLS0tKyAgICAgKy0tLS0tLS0rICAgICArLS0t
LS0tLS0rDQogICAgICB8U3dpdGNoLCB8ICAgICB8ICAgICAgIHwgICAgIHwgICAgICAgfCAgICAg
fCAgICAgICB8ICAgICB8U3dpdGNoLCB8DQogICAgICB8IFJvdXRlciB8LS0tLS18ICBMRVIgIHwt
LS0tLXwgIExTUiAgfC0tLS0tfCAgTEVSICB8LS0tLS18IFJvdXRlciB8DQogICAgICB8ICAgICAg
ICB8ICAgICB8ICBPQyAgIHwgICAgIHwgIFRDICAgfCAgICAgfCAgT0MgICB8ICAgICB8ICAgICAg
ICB8DQogICAgICArLS0tLS0tLS0rICAgICArLS0tLS0tLSsgICAgICstLS0tLS0tKyAgICAgKy0t
LS0tLS0rICAgICArLS0tLS0tLS0rDQogICAgICAgICAgICAgICAgICAgICAvICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgXA0KICAgICAgKy0tLS0tLS0rICAgICAvICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICBcICAgICArLS0tLS0tLSsNCiAgICAgIHwgIExFUiAgfCAg
ICAvICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgIFwgICAgfCAgTEVSICB8DQog
ICAgICB8IE1hc3RlcnwtLS0vICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
XC0tLXwgU2xhdmUgfA0KICAgICAgfCBDbG9jayB8ICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgICB8IENsb2NrIHwNCiAgICAgICstLS0tLS0tKyAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgKy0tLS0tLS0rDQoNCiAgICAgRmln
dXJlICgxKSAtIERlcGxveW1lbnQgZXhhbXBsZSAxIG9mIHRpbWluZyBvdmVyIE1QTFMvTVBMUy1U
UCBuZXR3b3JrDQoNCiAgIExFUnMgY291bGQgYWxzbyBhY3QgYXMgQm91bmRhcnkgQ2xvY2sgKEJD
KS4gIFRoaXMgaXMgc2hvd24gaW4gRmlndXJlDQogICAyLCB3aGVyZSBMRVJzIHRlcm1pbmF0ZSB0
aGUgVGltaW5nIG1lc3NhZ2VzIHJlY2VpdmVkIGZyb20gc3dpdGNoLw0KICAgcm91dGVycyB0aGF0
IGFyZSBvdXRzaWRlIG9mIHRoZSBNUExTIG5ldHdvcmsgYWN0aW5nIGFzIE9DIG9yIEJDLiAgSW4N
CiAgIHRoaXMgZXhhbXBsZSBMRVJzIHJlZ2VuZXJhdGUgdGhlIGNsb2NrIGFuZCBpbml0aWF0ZSB0
aW1pbmcgbWVzc2FnZXMNCiAgIGVuY2Fwc3VsYXRlZCBpbiBUaW1pbmcgTFNQIHRvd2FyZCB0aGUg
TVBMUyBuZXR3b3JrLCB3aGlsZSB0aGUgTFNScw0KICAgYWN0IGFzIFRyYW5zcGFyZW50IENsb2Nr
IChUQykgYW5kIGp1c3QgdXBkYXRlIHRoZSBUaW1pbmcgZmllbGQgaW4gdGhlDQogICBUaW1pbmcg
bWVzc2FnZXMsIHdoaWNoIGFyZSBhbHJlYWR5IGVuY2Fwc3VsYXRlZCBpbiBUaW1pbmcgTFNQcy4N
Cg0KICAgICArLS0tLS0tLS0rICAgICArLS0tLS0tLSsgICAgICstLS0tLS0tKyAgICAgKy0tLS0t
LS0rICAgICArLS0tLS0tLS0rDQogICAgIHxTd2l0Y2gsIHwgICAgIHwgICAgICAgfCAgICAgfCAg
ICAgICB8ICAgICB8ICAgICAgIHwgICAgIHxTd2l0Y2gsIHwNCiAgICAgfCBSb3V0ZXIgfC0tLS0t
fCAgTEVSICB8LS0tLS18ICBMU1IgIHwtLS0tLXwgIExFUiAgfC0tLS0tfCBSb3V0ZXIgfA0KICAg
ICB8IE9DL0JDICB8ICAgICB8ICBCQyAgIHwgICAgIHwgIFRDICAgfCAgICAgfCAgQkMgICB8ICAg
ICB8IE9DL0JDICB8DQogICAgICstLS0tLS0tLSsgICAgICstLS0tLS0tKyAgICAgKy0tLS0tLS0r
ICAgICArLS0tLS0tLSsgICAgICstLS0tLS0tLSsNCg0KICAgICBGaWd1cmUgKDIpIC0gRGVwbG95
bWVudCBleGFtcGxlIDIgb2YgdGltaW5nIG92ZXIgTVBMUy9NUExTLVRQIG5ldHdvcmsNCg0KDQoN
Cg0KDQpEYXZhcmksIGV0IGFsLiAgICAgICAgICAgRXhwaXJlcyBBdWd1c3QgMjcsIDIwMTMgICAg
ICAgICAgICAgICBbUGFnZSAxMF0NCgwNCkludGVybmV0LURyYWZ0ICAgICAgICBUcmFuc3BvcnRp
bmcgVGltaW5nIG92ZXIgTVBMUyAgICAgICAgRmVicnVhcnkgMjAxMw0KDQoNCiAgIExFUnMgY291
bGQgYWxzbyBhY3QgYXMgVHJhbnNwYXJlbnQgQ2xvY2sgKFRDKS4gIFRoaXMgaXMgc2hvd24gaW4N
CiAgIEZpZ3VyZSAzLCB3aGVyZSBMRVJzIGRvIG5vdCB0ZXJtaW5hdGUgdGhlIFRpbWluZyBtZXNz
YWdlcyByZWNlaXZlZA0KICAgZnJvbSBzd2l0Y2gvcm91dGVycyB0aGF0IGFyZSBvdXRzaWRlIG9m
IHRoZSBNUExTIG5ldHdvcmsgYWN0aW5nIGFzDQogICBPQywgVEMgb3IgQkMuICBUaGUgTEVScyBh
Y3QgYXMgVEMgYW5kIHVwZGF0ZSB0aGUgVGltaW5nIGZpZWxkIGluIHRoZQ0KICAgVGltaW5nIG1l
c3NhZ2VzIGFzIHRoZXkgdHJhbnNpdCB0aGUgTEVSLCB3aGlsZSBlbmNhcHN1bGF0aW5nIHRoZW0g
aW4NCiAgIHRpbWluZyBMU1AuICBUaGUgTFNScyBhbHNvIGFjdCBhcyBUcmFuc3BhcmVudCBDbG9j
ayAoVEMpIGFuZCBqdXN0DQogICB1cGRhdGUgdGhlIFRpbWluZyBmaWVsZCBpbiB0aGUgVGltaW5n
IG1lc3NhZ2VzIHdoaWNoIGFyZSBhbHJlYWR5DQogICBlbmNhcHN1bGF0ZWQgaW4gVGltaW5nIExT
UHMuDQoNCiAgICAgICstLS0tLS0tLSsgICAgICstLS0tLS0tKyAgICAgKy0tLS0tLS0rICAgICAr
LS0tLS0tLSsgICAgICstLS0tLS0tLSsNCiAgICAgIHxTd2l0Y2gsIHwgICAgIHwgICAgICAgfCAg
ICAgfCAgICAgICB8ICAgICB8ICAgICAgIHwgICAgIHxTd2l0Y2gsIHwNCiAgICAgIHwgUm91dGVy
IHwtLS0tLXwgIExFUiAgfC0tLS0tfCAgTFNSICB8LS0tLS18ICBMRVIgIHwtLS0tLXwgUm91dGVy
IHwNCiAgICAgIHxPQy9UQy9CQ3wgICAgIHwgIFRDICAgfCAgICAgfCAgVEMgICB8ICAgICB8ICBU
QyAgIHwgICAgIHxPQy9UQy9CQ3wNCiAgICAgICstLS0tLS0tLSsgICAgICstLS0tLS0tKyAgICAg
Ky0tLS0tLS0rICAgICArLS0tLS0tLSsgICAgICstLS0tLS0tLSsNCg0KICAgIEZpZ3VyZSAoMykg
LSBEZXBsb3ltZW50IGV4YW1wbGUgMyBvZiB0aW1pbmcgb3ZlciBNUExTL01QTFMtVFAgbmV0d29y
aw0KDQogICBBbiBNUExTIGRvbWFpbiBjYW4gc2VydmUgbXVsdGlwbGUgY3VzdG9tZXJzLiAgVGhp
cyBtZWFucyB0aGF0IHRoZQ0KICAgTVBMUyBkb21haW4gKG1haW50YWluZWQgYnkgYSBzZXJ2aWNl
IHByb3ZpZGVyKSBtYXkgcHJvdmlkZSB0aW1pbmcNCiAgIHNlcnZpY2VzIHRvIG11bHRpcGxlIGN1
c3RvbWVycywgZWFjaCBoYXZpbmcgdGhlaXIgb3duIFRpbWluZyBkb21haW4uDQogICBUaGVyZWZv
cmUgTEVSIEJDcyBuZWVkIHRvIGludGVyYWN0IHdpdGggbXVsdGlwbGUgZ3JhbmRtYXN0ZXJzLCBh
bmQNCiAgIGNvbnNlcXVlbnRseSBtdWx0aXBsZSB0aW1lIHJlZmVyZW5jZXMuICBBbHNvLCBMRVIv
TFNSIFRDcyBNVVNUIGJlDQogICBzeW5jaHJvbml6ZWQgdG8gdGhlIHNhbWUgbWFzdGVyIGNsb2Nr
ICh3aGljaCBpcyB0aGUgc2VydmljZSBwcm92aWRlcg0KICAgTWFzdGVyIGNsb2NrKSwgd2hpY2gg
aW1wbGllcyB0aGF0IHRoZXkgbmVlZCB0byBjaG9vc2Ugb25lIG1hc3RlciB0bw0KICAgc3luY2hy
b25pemUgdG8uDQoNCiAgIFRoZSBUaW1pbmcgb3ZlciBNUExTIGFyY2hpdGVjdHVyZSBhc3N1bWVz
IGZ1bGwgbWVzaCBvZiBUaW1pbmcgTFNQcw0KICAgYmV0d2VlbiBhbGwgTEVScyBzdXBwb3J0aW5n
IHRoaXMgc3BlY2lmaWNhdGlvbi4gIEl0IHN1cHBvcnRzDQogICBQb2ludC10by0gcG9pbnQgKFZQ
V1MpIGFuZCBNdWx0aXBvaW50IChWUExTKSBzZXJ2aWNlcy4gIFRoaXMgbWVhbnMNCiAgIHRoYXQg
YSBjdXN0b21lciBtYXkgcHVyY2hhc2UgYSBQb2ludC10by1wb2ludCBUaW1pbmcgc2VydmljZSBi
ZXR3ZWVuDQogICB0d28gY3VzdG9tZXIgc2l0ZXMgb3IgYSBNdWx0aXBvaW50IFRpbWluZyBzZXJ2
aWNlIGJldHdlZW4gbW9yZSB0aGFuDQogICB0d28gY3VzdG9tZXIgc2l0ZXMuDQoNCiAgIFRoZSBU
aW1pbmcgb3ZlciBNUExTIGFyY2hpdGVjdHVyZSBzdXBwb3J0cyBQMlAgb3IgUDJNUCBUaW1pbmcg
TFNQcy4NCiAgIFRoaXMgbWVhbnMgdGhhdCB0aGUgVGltaW5nIE11bHRpY2FzdCBtZXNzYWdlcyBz
dWNoIGFzIFBUUCBNdWx0aWNhc3QNCiAgIGV2ZW50IG1lc3NhZ2VzIGNhbiBiZSB0cmFuc3BvcnRl
ZCBvdmVyIFAyTVAgVGltaW5nIExTUCBvciBiZQ0KICAgcmVwbGljYXRlZCBhbmQgdHJhbnNwb3J0
ZWQgb3ZlciBtYW55IFAyUCBUaW1pbmcgTFNQcy4NCg0KICAgVGltaW5nIG1lc3NhZ2VzLCB0aGF0
IGRvIG5vdCByZXF1aXJlIFRpbWUgc3RhbXBpbmcgb3IgQ29ycmVjdGlvbg0KICAgRmllbGQgdXBk
YXRlIE1BWSBiZSB0cmFuc3BvcnRlZCBvdmVyIFRpbWluZyBMU1BzIHRvIHNpbXBsaWZ5IGhhcmR3
YXJlDQogICBhbmQgc29mdHdhcmUuDQoNCiAgIFBUUCBBbm5vdW5jZSBtZXNzYWdlcyB0aGF0IGRl
dGVybWluZSB0aGUgVGltaW5nIExTUCB0ZXJtaW5hdGluZyBwb2ludA0KICAgYmVoYXZpb3Igc3Vj
aCBhcyBCQy9PQy9UQyBTSE9VTEQgYmUgdHJhbnNwb3J0ZWQgb3ZlciB0aGUgVGltaW5nIExTUA0K
ICAgdG8gc2ltcGxpZnkgaGFyZHdhcmUgYW5kIHNvZnR3YXJlLg0KDQoNCg0KDQoNCg0KRGF2YXJp
LCBldCBhbC4gICAgICAgICAgIEV4cGlyZXMgQXVndXN0IDI3LCAyMDEzICAgICAgICAgICAgICAg
W1BhZ2UgMTFdDQoMDQpJbnRlcm5ldC1EcmFmdCAgICAgICAgVHJhbnNwb3J0aW5nIFRpbWluZyBv
dmVyIE1QTFMgICAgICAgIEZlYnJ1YXJ5IDIwMTMNCg0KDQo1LiAgRGVkaWNhdGVkIExTUHMgZm9y
IFRpbWluZyBtZXNzYWdlcw0KDQogICBNYW55IG1ldGhvZHMgaGF2ZSBiZWVuIGNvbnNpZGVyZWQg
Zm9yIGlkZW50aWZ5aW5nIHRoZSBUaW1pbmcgbWVzc2FnZXMNCiAgIHdoZW4gdGhleSBhcmUgZW5j
YXBzdWxhdGVkIGluIE1QTFMgc3VjaCBhcyB1c2luZyBHQUwvQUNIIG9yIGEgbmV3DQogICByZXNl
cnZlZCBsYWJlbC4gIFRoZXNlIG1ldGhvZHMgd2VyZSBub3QgYXR0cmFjdGl2ZSBzaW5jZSB0aGV5
IGVpdGhlcg0KICAgcmVxdWlyZWQgZGVlcCBwYWNrZXQgaW5zcGVjdGlvbiBhdCBsaW5lIHJhdGUg
aW4gdGhlIGludGVybWVkaWF0ZSBMU1JzDQogICBvciB0aGV5IHJlcXVpcmVkIHVzZSBvZiBhIHNj
YXJjZSBuZXcgcmVzZXJ2ZWQgbGFiZWwuICBBbHNvIG9uZSBvZiB0aGUNCiAgIGdvYWxzIHdhcyB0
byByZXVzZSBleGlzdGluZyBPQU0gbWVjaGFuaXNtcy4NCg0KICAgVGhlIG1ldGhvZCBkZWZpbmVk
IGluIHRoaXMgZG9jdW1lbnQgY2FuIGJlIHVzZWQgYnkgTEVSIGFuZCBMU1JzIHRvDQogICBpZGVu
dGlmeSBUaW1pbmcgbWVzc2FnZXMgaW4gTVBMUyB0dW5uZWxzIGJ5IGp1c3QgbG9va2luZyBhdCB0
aGUgdG9wDQogICBsYWJlbCBpbiB0aGUgTVBMUyBsYWJlbCBzdGFjaywgd2hpY2ggb25seSBjYXJy
eSBUaW1pbmcgbWVzc2FnZXMgYXMNCiAgIHdlbGwgYXMgT0FNLCBidXQgbm90IGRhdGEgcGxhbmUg
Y2xpZW50IHRyYWZmaWMuDQoNCiAgIENvbXBsaWFudCBpbXBsZW1lbnRhdGlvbnMgTVVTVCB1c2Ug
ZGVkaWNhdGVkIExTUHMgdG8gY2FycnkgVGltaW5nDQogICBtZXNzYWdlcyBvdmVyIE1QTFMuICBU
aGVzZSBMU1BzIGFyZSBoZXJlaW4gcmVmZXJyZWQgdG8gYXMgIlRpbWluZw0KICAgTFNQcyIgYW5k
IHRoZSBsYWJlbHMgYXNzb2NpYXRlZCB3aXRoIHRoZXNlIExTUHMgYXMgIlRpbWluZyBMU1ANCiAg
IGxhYmVscyIuICBUaGUgVGltaW5nIExTUHMgdGhhdCBydW5zIGJldHdlZW4gSW5ncmVzcyBhbmQg
RWdyZXNzIExFUnMNCiAgIE1VU1QgYmUgY28tcm91dGVkLiAgQWx0ZXJuYXRpdmVseSwgYSBzaW5n
bGUgYmlkaXJlY3Rpb25hbCBjby1yb3V0ZWQNCiAgIExTUCBjYW4gYmUgdXNlZC4NCg0KICAgQ28t
cm91dGluZyBvZiB0aGUgdHdvIGRpcmVjdGlvbnMgaXMgcmVxdWlyZWQgdG8gbGltaXQgdGhlIGRp
ZmZlcmVuY2UNCiAgIGluIHRoZSBkZWxheXMgaW4gdGhlIE1hc3RlciBjbG9jayB0byBTbGF2ZSBj
bG9jayBkaXJlY3Rpb24gY29tcGFyZWQNCiAgIHRvIHRoZSBTbGF2ZSBjbG9jayB0byBNYXN0ZXIg
Y2xvY2sgZGlyZWN0aW9uLiAgVGhlIFRpbWluZyBMU1AgTUFZIGJlDQogICBNUExTIExTUCBvciBN
UExTLVRQIExTUC4NCg0KICAgVGhlIFRpbWluZyBMU1BzIGNvdWxkIGJlIGNvbmZpZ3VyZWQgb3Ig
c2lnbmFsZWQgdmlhIFJTVlAtVEUvR01QTFMuDQogICBOZXcgRXh0ZW5zaW9ucyB0byBSU1ZQLVRF
L0dNUExTIFRMVnMgYXJlIHJlcXVpcmVkOyBob3dldmVyIHRoZXkgYXJlDQogICBvdXRzaWRlIHRo
ZSBzY29wZSBvZiB0aGlzIGRvY3VtZW50Lg0KDQogICBUaGUgVGltaW5nIExTUHMgTUFZIGNhcnJ5
IGVzc2VudGlhbCBNUExTL01QTFMtVFAgT0FNIHRyYWZmaWMgc3VjaCBhcw0KICAgQkZEIGFuZCBM
U1AgUGluZyBidXQgdGhlIExTUCBkYXRhIHBsYW5lIGNsaWVudCBwbGFuZSB0cmFmZmljIE1VU1Qg
YmUNCiAgIFRpbWluZyBwYWNrZXRzIG9ubHkuDQoNCg0KDQoNCg0KDQoNCg0KDQoNCg0KDQoNCg0K
DQoNCg0KDQpEYXZhcmksIGV0IGFsLiAgICAgICAgICAgRXhwaXJlcyBBdWd1c3QgMjcsIDIwMTMg
ICAgICAgICAgICAgICBbUGFnZSAxMl0NCgwNCkludGVybmV0LURyYWZ0ICAgICAgICBUcmFuc3Bv
cnRpbmcgVGltaW5nIG92ZXIgTVBMUyAgICAgICAgRmVicnVhcnkgMjAxMw0KDQoNCjYuICBUaW1p
bmcgb3ZlciBMU1AgRW5jYXBzdWxhdGlvbg0KDQogICBUaGlzIGRvY3VtZW50IGRlZmluZXMgdHdv
IG1ldGhvZHMgZm9yIGNhcnJ5aW5nIFRpbWluZyBtZXNzYWdlcyBvdmVyDQogICBNUExTLiAgVGhl
IGZpcnN0IG1ldGhvZCBpcyBjYXJyeWluZyBVRFAvSVAgZW5jYXBzdWxhdGVkIFRpbWluZw0KICAg
bWVzc2FnZXMgb3ZlciBUaW1pbmcgTFNQcywgd2hpY2ggaXMgc3VpdGFibGUgZm9yIE1QTFMgbmV0
d29ya3MgYW5kDQogICB0aGUgc2Vjb25kIG1ldGhvZCwgaXMgY2FycnlpbmcgRXRoZXJuZXQgZW5j
YXBzdWxhdGVkIFRpbWluZyBtZXNzYWdlcw0KICAgb3ZlciBFdGhlcm5ldCBQV3MgaW5zaWRlIFRp
bWluZyBMU1BzLCB3aGljaCBpcyBzdWl0YWJsZSBmb3IgTVBMUyBhbmQNCiAgIE1QTFMtVFAgbmV0
d29ya3MuDQoNCjYuMS4gIFRpbWluZyBvdmVyIFVEUC9JUCBvdmVyIE1QTFMgRW5jYXBzdWxhdGlv
bg0KDQogICBUaGUgc2ltcGxlc3QgbWV0aG9kIG9mIHRyYW5zcG9ydGluZyBUaW1pbmcgbWVzc2Fn
ZXMgb3ZlciBNUExTIGlzIHRvDQogICBlbmNhcHN1bGF0ZSBUaW1pbmcgUERVcyBpbiBVRFAvSVAg
YW5kIHRoZW4gZW5jYXBzdWxhdGUgdGhlbSBpbiBUaW1pbmcNCiAgIExTUC4gIFRoaXMgZm9ybWF0
IGlzIHNob3duIGluIEZpZ3VyZSA0Lg0KDQoNCiAgICAgICAgICAgICAgICAgICAgKy0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0rDQogICAgICAgICAgICAgICAgICAgIHwgICBUaW1pbmcgTFNQIExhYmVs
ICAgfA0KICAgICAgICAgICAgICAgICAgICArLS0tLS0tLS0tLS0tLS0tLS0tLS0tLSsNCiAgICAg
ICAgICAgICAgICAgICAgfCAgICAgICAgSVB2NC82ICAgICAgICB8DQogICAgICAgICAgICAgICAg
ICAgICstLS0tLS0tLS0tLS0tLS0tLS0tLS0tKw0KICAgICAgICAgICAgICAgICAgICB8ICAgICAg
ICAgVURQICAgICAgICAgIHwNCiAgICAgICAgICAgICAgICAgICAgKy0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0rDQogICAgICAgICAgICAgICAgICAgIHwgICAgIFRpbWluZyBQRFUgICAgICAgfA0KICAg
ICAgICAgICAgICAgICAgICArLS0tLS0tLS0tLS0tLS0tLS0tLS0tLSsNCg0KICAgICAgRmlndXJl
ICg0KSAtIFRpbWluZyBvdmVyIFVEUC9JUCBvdmVyIE1QTFMgRW5jYXBzdWxhdGlvbg0KDQoNCiAg
IFRoaXMgZW5jYXBzdWxhdGlvbiBpcyB2ZXJ5IHNpbXBsZSBhbmQgaXMgdXNlZnVsIHdoZW4gdGhl
IG5ldHdvcmsNCiAgIGJldHdlZW4gVGltaW5nIE1hc3RlciBDbG9jayBhbmQgU2xhdmUgQ2xvY2sg
aXMgTVBMUyBuZXR3b3JrLg0KDQogICBJbiBvcmRlciBmb3IgYW4gTEVSL0xTUiB0byBwcm9jZXNz
IFRpbWluZyBtZXNzYWdlcywgdGhlIFRpbWluZyBMU1ANCiAgIExhYmVsIG11c3QgYmUgYXQgdGhl
IHRvcCBsYWJlbCBvZiB0aGUgbGFiZWwgc3RhY2suICBUaGUgTEVSL0xTUiBNVVNUDQogICBrbm93
IHRoYXQgdGhlIFRpbWluZyBMU1AgTGFiZWwgaXMgdXNlZCBmb3IgY2FycnlpbmcgVGltaW5nIG1l
c3NhZ2VzLg0KICAgVGhpcyBjYW4gYmUgYWNjb21wbGlzaGVkIHZpYSBzdGF0aWMgY29uZmlndXJh
dGlvbiBvciB2aWEgUlNWUC1URQ0KICAgc2lnbmFsaW5nLg0KDQogICBUaGUgVURQL0lQIGVuY2Fw
c3VsYXRpb24gb2YgUFRQIE1VU1QgZm9sbG93IEFubmV4IEQgYW5kIEUgb2YgW0lFRUVdLg0KICAg
V2hpbGUgdGhlIFVEUC9JUCBlbmNhcHN1bGF0aW9uIG9mIE5UUCBNVVNUIGZvbGxvdyBbUkZDNTkw
NV0uDQoNCjYuMi4gIFRpbWluZyBvdmVyIFBXIEVuY2Fwc3VsYXRpb24NCg0KICAgQW5vdGhlciBt
ZXRob2Qgb2YgdHJhbnNwb3J0aW5nIFRpbWluZyBvdmVyIE1QTFMgbmV0d29ya3MgaXMgYnkNCiAg
IGVuY2Fwc3VsYXRpbmcgVGltaW5nIFBEVXMgaW4gUFcgd2hpY2ggaW4gdHVybiBpcyB0cmFuc3Bv
cnRlZCBvdmVyDQogICBUaW1pbmcgTFNQcy4gIEluIGNhc2Ugb2YgUFRQLCBFdGhlcm5ldCBQVyBl
bmNhcHN1bGF0aW9uIFtSRkM0NDQ4XSwNCiAgIHNob3duIGluIEZpZyA1KEEpIE1VU1QgYmUgdXNl
ZCBhbmQgdGhlIEV0aGVybmV0IGVuY2Fwc3VsYXRpb24gb2YgUFRQDQogICBNVVNUIGZvbGxvdyBB
bm5leCBGIG9mIFtJRUVFXS4NCg0KDQoNCkRhdmFyaSwgZXQgYWwuICAgICAgICAgICBFeHBpcmVz
IEF1Z3VzdCAyNywgMjAxMyAgICAgICAgICAgICAgIFtQYWdlIDEzXQ0KDA0KSW50ZXJuZXQtRHJh
ZnQgICAgICAgIFRyYW5zcG9ydGluZyBUaW1pbmcgb3ZlciBNUExTICAgICAgICBGZWJydWFyeSAy
MDEzDQoNCg0KICAgVGhlIFRhZ2dlZCBtb2RlIGRlZmluZWQgaW4gW1JGQy00NDQ4XSBNVVNUIGJl
IHVzZWQgYW5kIHRoZSBQYXlsb2FkDQogICBNVVNUIGhhdmUgMiBWTEFOIHRhZ3MgKFMtVkxBTiBh
bmQgQy1WTEFOKS4gIFRoZSBUaW1pbmcgb3ZlciBQVw0KICAgZW5jYXBzdWxhdGlvbiBNVVNUIHVz
ZSB0aGUgQ29udHJvbCBXb3JkIChDVykgYXMgc3BlY2lmaWVkIGluDQogICBbUkZDNDQ0OF0gdG8g
ZW5zdXJlIHByb3BlciBkZXRlY3Rpb24gb2YgUFRQIG1lc3NhZ2VzIGluc2lkZSB0aGUgTVBMUw0K
ICAgcGFja2V0cyBmb3IgVGltaW5nIG92ZXIgTFNQIGFuZCBUaW1pbmcgb3ZlciBQVyBlbmNhcHN1
bGF0aW9uLiAgVGhlDQogICB1c2Ugb2YgU2VxdWVuY2UgTnVtYmVyIGluIHRoZSBDVyBpcyBvcHRp
b25hbC4NCg0KICAgVGltaW5nIG92ZXIgUFcgZW5jYXBzdWxhdGlvbiBmb3IgTlRQIE1VU1QgdXNl
IE5UUCBvdmVyIFVEUC9JUCBvdmVyIFBXDQogICAodGhlIElQIFBXIGRpc2N1c3NlZCBpbiBbUkZD
NDQ0N10pIHNob3duIGluIEZpZyA1KEIpLg0KDQogICAgICAgICAgICAgICAgICArLS0tLS0tLS0t
LS0tLS0tLSsgICstLS0tLS0tLS0tLS0tLS0tKw0KICAgICAgICAgICAgICAgICAgfFRpbWluZyBM
U1AgTGFiZWx8ICB8VGltaW5nIExTUCBMYWJlbHwNCiAgICAgICAgICAgICAgICAgICstLS0tLS0t
LS0tLS0tLS0tKyAgKy0tLS0tLS0tLS0tLS0tLS0rDQogICAgICAgICAgICAgICAgICB8ICAgIFBX
IExhYmVsICAgIHwgIHwgICAgUFcgTGFiZWwgICAgfA0KICAgICAgICAgICAgICAgICAgKy0tLS0t
LS0tLS0tLS0tLS0rICArLS0tLS0tLS0tLS0tLS0tLSsNCiAgICAgICAgICAgICAgICAgIHwgIENv
bnRyb2wgV29yZCAgfCAgfCAgICAgIElQICAgICAgICB8DQogICAgICAgICAgICAgICAgICArLS0t
LS0tLS0tLS0tLS0tLSsgICstLS0tLS0tLS0tLS0tLS0tKw0KICAgICAgICAgICAgICAgICAgfCAg
ICBFdGhlcm5ldCAgICB8ICB8ICAgICAgVURQICAgICAgIHwNCiAgICAgICAgICAgICAgICAgIHwg
ICAgIEhlYWRlciAgICAgfCAgKy0tLS0tLS0tLS0tLS0tLS0rDQogICAgICAgICAgICAgICAgICAr
LS0tLS0tLS0tLS0tLS0tLSsgIHwgICBUaW1pbmcgUERVICAgfA0KICAgICAgICAgICAgICAgICAg
fCAgICAgUy1WTEFOICAgICB8ICB8ICAgICAgICAgICAgICAgIHwNCiAgICAgICAgICAgICAgICAg
ICstLS0tLS0tLS0tLS0tLS0tKyAgKy0tLS0tLS0tLS0tLS0tLS0rDQogICAgICAgICAgICAgICAg
ICB8ICAgICBDLVZMQU4gICAgIHwgICAgICAgIChCKQ0KICAgICAgICAgICAgICAgICAgKy0tLS0t
LS0tLS0tLS0tLS0rDQogICAgICAgICAgICAgICAgICB8ICAgVGltaW5nIFBEVSAgIHwNCiAgICAg
ICAgICAgICAgICAgIHwgICAgICAgICAgICAgICAgfA0KICAgICAgICAgICAgICAgICAgKy0tLS0t
LS0tLS0tLS0tLS0rDQogICAgICAgICAgICAgICAgICAgICAgICAgKEEpDQoNCg0KICAgICAgICAg
ICAgICBGaWd1cmUgKDUpIC0gVGltaW5nIG92ZXIgUFcgRW5jYXBzdWxhdGlvbnMNCg0KICAgSW4g
b3JkZXIgZm9yIGFuIExTUiB0byBwcm9jZXNzIFBUUCBtZXNzYWdlcywgdGhlIHRvcCBsYWJlbCBv
ZiB0aGUNCiAgIGxhYmVsIHN0YWNrICh0aGUgVHVubmVsIExhYmVsKSBNVVNUIGJlIGEgVGltaW5n
IGxhYmVsLg0KDQogICBUaGUgUFcgbWV0aG9kIG9mIHRyYW5zcG9ydGluZyBUaW1pbmcgb3ZlciBN
UExTIGlzIGFwcGxpY2FibGUgdG8gYm90aA0KICAgTVBMUyBhbmQgTVBMUy1UUCBuZXR3b3Jrcy4N
Cg0KNi4zLiAgT3RoZXIgVGltaW5nIEVuY2Fwc3VsYXRpb24gbWV0aG9kcw0KDQogICBJbiBmdXR1
cmUgb3RoZXIgdGltaW5nIGVuY2Fwc3VsYXRpb24gbWV0aG9kcyBtYXkgYmUgaW50cm9kdWNlZCwg
c3VjaA0KICAgYXMgYSBuZXcgc2hpbSBoZWFkZXIgYWZ0ZXIgdGhlIEJvdHRvbSBvZiBTdGFjayB0
byBjYXJyeSB0aGUgVGltaW5nDQogICBpbmZvcm1hdGlvbi4gIFN1Y2ggbmV3IGVuY2Fwc3VsYXRp
b25zIGFyZSBvdXRzaWRlIHRoZSBzY29wZSBvZiB0aGlzDQogICBkb2N1bWVudC4gIFRoZSBjb250
cm9sIGFuZCBzaWduYWxpbmcgcmVxdWlyZW1lbnRzIGluIHRoaXMgZG9jdW1lbnQNCiAgIGFyZSBk
ZWZpbmVkIGdlbmVyaWNhbGx5IGVub3VnaCB0byBhY2NvbW1vZGF0ZSBhbnkgc3VjaCBuZXcNCiAg
IGVuY2Fwc3VsYXRpb25zLg0KDQoNCg0KDQoNCkRhdmFyaSwgZXQgYWwuICAgICAgICAgICBFeHBp
cmVzIEF1Z3VzdCAyNywgMjAxMyAgICAgICAgICAgICAgIFtQYWdlIDE0XQ0KDA0KSW50ZXJuZXQt
RHJhZnQgICAgICAgIFRyYW5zcG9ydGluZyBUaW1pbmcgb3ZlciBNUExTICAgICAgICBGZWJydWFy
eSAyMDEzDQoNCg0KNy4gIFRpbWluZyBtZXNzYWdlIFByb2Nlc3NpbmcNCg0KICAgRWFjaCBUaW1p
bmcgcHJvdG9jb2wgc3VjaCBhcyBQVFAgYW5kIE5UUCwgZGVmaW5lIHRoZWlyIHNldCBvZiBUaW1p
bmcNCiAgIG1lc3NhZ2VzLiAgRm9yIGV4YW1wbGUgUFRQIGRlZmluZXMgU1lOQywgREVMQVlfUkVR
LCBERUxBWV9SRVNQLA0KICAgRk9MTE9XX1VQLCBldGMgbWVzc2FnZXMuDQoNCiAgIFNvbWUgb2Yg
dGhlIFRpbWluZyBtZXNzYWdlcyByZXF1aXJlIHRpbWUgc3RhbXBpbmcgYXQgcG9ydCBsZXZlbCBh
bmQNCiAgIHNvbWUgZG9udC4gIEl0IGlzIHRoZSBqb2Igb2YgdGhlIExFUi9MU1IgdG8gcGFyc2Ug
dGhlIHRpbWluZyBtZXNzYWdlDQogICBhbmQgZmluZCBvdXQgdGhlIHR5cGUgb2YgdGhlIFRpbWlu
ZyBtZXNzYWdlIGFuZCBkZWNpZGUgd2hldGhlciBhbmQNCiAgIGhvdyB0byBUaW1lLSBzdGFtcCBp
dCAoZS5nLiwgQkMpIG9yIG1vZGlmeSBleGlzdGluZyB0aW1lLXN0YW1wIGluIGl0DQogICAoZS5n
LiwgVEMpLg0KDQogICBGb3IgZXhhbXBsZSB0aGUgZm9sbG93aW5nIFBUUCBtZXNzYWdlcyAoY2Fs
bGVkIEV2ZW50IG1lc3NhZ2VzKQ0KICAgcmVxdWlyZSB0aW1lLXN0YW1waW5nLCB3aGlsZSBvdGhl
ciBOb24tRXZlbnQgUFRQIG1lc3NhZ2VzIGRvIG5vdCBuZWVkDQogICB0aW1lLXN0YW1waW5nLg0K
DQogICBvICBTWU5DDQoNCiAgIG8gIERFTEFZX1JFUSAoRGVsYXkgUmVxdWVzdCkNCg0KICAgbyAg
UERFTEFZX1JFUSAoUGVlciBEZWxheSBSZXF1ZXN0KQ0KDQogICBvICBQREVMQVlfUkVTUCAoUGVl
ciBEZWxheSBSZXNwb25zZSkNCg0KICAgU1lOQyBhbmQgREVMQVlfUkVRIGFyZSBleGNoYW5nZWQg
YmV0d2VlbiBNYXN0ZXIgQ2xvY2sgYW5kIFNsYXZlIENsb2NrDQogICBhbmQgTVVTVCBiZSB0cmFu
c3BvcnRlZCBvdmVyIFBUUCBMU1BzLiAgUERFTEFZX1JFUSBhbmQgUERFTEFZX1JFU1ANCiAgIGFy
ZSBleGNoYW5nZWQgYmV0d2VlbiBhZGphY2VudCBQVFAgY2xvY2tzIChpLmUuICBNYXN0ZXIsIFNs
YXZlLA0KICAgQm91bmRhcnksIG9yIFRyYW5zcGFyZW50KSBhbmQgU0hPVUxEIGJlIHRyYW5zcG9y
dGVkIG92ZXIgc2luZ2xlIGhvcA0KICAgUFRQIExTUHMuICBJZiBUd28gU3RlcCBQVFAgY2xvY2tz
IGFyZSBwcmVzZW50LCB0aGVuIHRoZSBGT0xMT1dfVVAsDQogICBERUxBWV9SRVNQLCBhbmQgUERF
TEFZX1JFU1BfRk9MTE9XX1VQIG1lc3NhZ2VzIE1VU1QgYWxzbyBiZQ0KICAgdHJhbnNwb3J0ZWQg
b3ZlciB0aGUgUFRQIExTUHMuDQoNCiAgIEZvciBhIGdpdmVuIGluc3RhbmNlIG9mIDE1ODggcHJv
dG9jb2wsIFNZTkMgYW5kIERFTEFZX1JFUSBNVVNUIGJlDQogICB0cmFuc3BvcnRlZCBvdmVyIHR3
byBQVFAgTFNQcyB0aGF0IGFyZSBpbiBvcHBvc2l0ZSBkaXJlY3Rpb25zLiAgVGhlc2UNCiAgIFBU
UCBMU1BzLCB3aGljaCBhcmUgaW4gb3Bwb3NpdGUgZGlyZWN0aW9ucyBNVVNUIGJlIGNvbmdydWVu
dCBhbmQgY28tDQogICByb3V0ZWQuICBBbHRlcm5hdGl2ZWx5LCBhIHNpbmdsZSBiaWRpcmVjdGlv
bmFsIGNvLXJvdXRlZCBMU1AgY2FuIGJlDQogICB1c2VkLg0KDQogICBFeGNlcHQgYXMgaW5kaWNh
dGVkIGFib3ZlIGZvciB0aGUgdHdvLXN0ZXAgUFRQIGNsb2NrcywgTm9uLUV2ZW50IFBUUA0KICAg
bWVzc2FnZSB0eXBlcyBkbyBub3QgbmVlZCB0byBiZSBwcm9jZXNzZWQgYnkgaW50ZXJtZWRpYXRl
IHJvdXRlcnMuDQogICBUaGVzZSBtZXNzYWdlIHR5cGVzIE1BWSBiZSBjYXJyaWVkIGluIFBUUCBU
dW5uZWwgTFNQcy4NCg0KDQoNCg0KDQoNCg0KDQoNCg0KRGF2YXJpLCBldCBhbC4gICAgICAgICAg
IEV4cGlyZXMgQXVndXN0IDI3LCAyMDEzICAgICAgICAgICAgICAgW1BhZ2UgMTVdDQoMDQpJbnRl
cm5ldC1EcmFmdCAgICAgICAgVHJhbnNwb3J0aW5nIFRpbWluZyBvdmVyIE1QTFMgICAgICAgIEZl
YnJ1YXJ5IDIwMTMNCg0KDQo4LiAgUHJvdGVjdGlvbiBhbmQgUmVkdW5kYW5jeQ0KDQogICBJbiBv
cmRlciB0byBlbnN1cmUgY29udGludW91cyB1bmludGVycnVwdGVkIG9wZXJhdGlvbiBvZiBzbGF2
ZQ0KICAgY2xvY2tzLCB1c3VhbGx5IGFzIGEgZ2VuZXJhbCBwcmFjdGljZSwgc2xhdmUgY2xvY2tz
IChvciBwb3J0cykgdHJhY2sNCiAgIHJlZHVuZGFudCBtYXN0ZXIgY2xvY2tzLg0KDQogICBJdCBp
cyB0aGUgcmVzcG9uc2liaWxpdHkgb2YgdGhlIG5ldHdvcmsgb3BlcmF0b3IgdG8gZW5zdXJlIHRo
YXQNCiAgIHBoeXNpY2FsbHkgZGlzam9pbnQgVGltaW5nIExTUHMgYXJlIGVzdGFibGlzaGVkIGJl
dHdlZW4gYSBzbGF2ZSBjbG9jaw0KICAgKG9yIHBvcnQpIGFuZCByZWR1bmRhbnQgbWFzdGVyIGNs
b2NrcyAob3IgcG9ydHMpLg0KDQogICBXaGVuIGEgc2xhdmUgY2xvY2sgKG9yIHBvcnQpIGxpc3Rl
bnMgdG8gcmVkdW5kYW50IG1hc3RlciBjbG9ja3Mgb3INCiAgIHBvcnRzLCBhbnkgcHJvbG9uZ2Vk
IFRpbWluZyBMU1Agb3V0YWdlIHdpbGwgdHJpZ2dlciB0aGUgc2xhdmUgY2xvY2sNCiAgIG9yIHBv
cnQgdG8gc3dpdGNoIHRvIGEgcmVkdW5kYW50IG1hc3RlciBjbG9jayBvciBwb3J0Lg0KDQogICBM
U1AvUFcgcHJvdGVjdGlvbiBzdWNoIGFzIExpbmVhciBwcm90ZWN0aW9uIFN3aXRjaGluZyAoMTox
LCAxKzEpLA0KICAgUmluZyBwcm90ZWN0aW9uIHN3aXRjaGluZyBvciBNUExTIEZhc3QgUmVyb3V0
ZSAoRlJSKSBnZW5lcmFsbHkgc3dpdGNoDQogICBhbHRlcm5hdGl2ZSBwYXRoIHRoYXQgdXN1YWxs
eSBjYXVzZSBhIGNoYW5nZSBpbiBkZWxheSwgd2hpY2ggaWYNCiAgIHVuZGV0ZWN0ZWQgYnkgc2xh
dmUgY2xvY2sgY2FuIHJlZHVjZSBhY2N1cmFjeSBvZiB0aGUgc2xhdmUgY2xvY2suDQogICBIb3dl
dmVyIGl0IGlzIGV4cGVjdGVkIHRoYXQgbW9zdCBTbGF2ZSBjbG9ja3MgY291bGQgZGV0ZWN0IHRo
ZSBjaGFuZ2UNCiAgIGluIGRlbGF5LiAgVGhlcmVmb3JlIHRoaXMgc3BlY2lmaWNhdGlvbiByZWNv
bW1lbmRzIHRoYXQgcHJvdGVjdGlvbg0KICAgc3dpdGNoaW5nIFNIT1VMRCBiZSB1c2VkLCB1bmxl
c3MgdGhlIG9wZXJhdG9yIGtub3dzIHRoYXQgdGhlDQogICBwcm90ZWN0aW9uIHN3aXRjaGluZyBt
YXkgaGF2ZSBhZHZlcnNlIGVmZmVjdCBvbiB0aGUgc2xhdmUgY2xvY2suDQoNCiAgIE5vdGUgdGhh
dCBhbnkgcHJvdGVjdGlvbiBvciByZXJvdXRlIG1lY2hhbmlzbSB0aGF0IGFkZHMgYWRkaXRpb25h
bA0KICAgTVBMUyBsYWJlbCB0byB0aGUgbGFiZWwgc3RhY2ssIHN1Y2ggYXMgRmFjaWxpdHkgQmFj
a3VwIEZhc3QgUmVyb3V0ZSwNCiAgIE1VU1QgZW5zdXJlIHRoYXQgdGhlIHB1c2hlZCBsYWJlbCBp
cyBhbHNvIGEgVGltaW5nIExhYmVsIHRvIGVuc3VyZQ0KICAgcmVjb2duaXRpb24gb2YgdGhlIE1Q
TFMgZnJhbWUgYXMgY29udGFpbmluZyBUaW1pbmcgbWVzc2FnZXMsIGFzIGl0DQogICB0cmFuc2l0
cyB0aGUgYmFja3VwIHBhdGguDQoNCg0KDQoNCg0KDQoNCg0KDQoNCg0KDQoNCg0KDQoNCg0KDQoN
Cg0KDQoNCg0KRGF2YXJpLCBldCBhbC4gICAgICAgICAgIEV4cGlyZXMgQXVndXN0IDI3LCAyMDEz
ICAgICAgICAgICAgICAgW1BhZ2UgMTZdDQoMDQpJbnRlcm5ldC1EcmFmdCAgICAgICAgVHJhbnNw
b3J0aW5nIFRpbWluZyBvdmVyIE1QTFMgICAgICAgIEZlYnJ1YXJ5IDIwMTMNCg0KDQo5LiAgRUNN
UA0KDQogICBUbyBlbnN1cmUgdGhlIG9wdGltYWwgb3BlcmF0aW9uIG9mIHNsYXZlIGNsb2NrcyBh
bmQgYXZvaWQgZXJyb3INCiAgIGludHJvZHVjZWQgYnkgZm9yd2FyZCBhbmQgcmV2ZXJzZSBwYXRo
IGRlbGF5IGFzeW1tZXRyeSwgdGhlIHBoeXNpY2FsDQogICBwYXRoIGZvciBUaW1pbmcgbWVzc2Fn
ZXMgZnJvbSBtYXN0ZXIgY2xvY2sgdG8gc2xhdmUgQ2xvY2sgYW5kIHZpY2UNCiAgIHZlcnNhIG11
c3QgYmUgdGhlIHNhbWUgZm9yIGFsbCBFdmVudCBUaW1pbmcgbWVzc2FnZXMgbGlzdGVkIGluDQog
ICBzZWN0aW9uIDcuDQoNCiAgIFRoZXJlZm9yZSB0aGUgVGltaW5nIExTUHMgTVVTVCBub3QgYmUg
c3ViamVjdCB0byBFQ01QIChFcXVhbCBDb3N0DQogICBNdWx0aXBhdGgpLg0KDQoNCg0KDQoNCg0K
DQoNCg0KDQoNCg0KDQoNCg0KDQoNCg0KDQoNCg0KDQoNCg0KDQoNCg0KDQoNCg0KDQoNCg0KDQoN
Cg0KDQoNCg0KDQoNCkRhdmFyaSwgZXQgYWwuICAgICAgICAgICBFeHBpcmVzIEF1Z3VzdCAyNywg
MjAxMyAgICAgICAgICAgICAgIFtQYWdlIDE3XQ0KDA0KSW50ZXJuZXQtRHJhZnQgICAgICAgIFRy
YW5zcG9ydGluZyBUaW1pbmcgb3ZlciBNUExTICAgICAgICBGZWJydWFyeSAyMDEzDQoNCg0KMTAu
ICBQSFANCg0KICAgVG8gZW5zdXJlIHRoYXQgdGhlIGxhYmVsIG9uIHRoZSB0b3Agb2YgdGhlIGxh
YmVsIHN0YWNrIGlzIHRoZSBUaW1pbmcNCiAgIExTUCBMYWJlbCwgUEhQIE1VU1Qgbm90IGJlIHVz
ZWQuDQoNCg0KDQoNCg0KDQoNCg0KDQoNCg0KDQoNCg0KDQoNCg0KDQoNCg0KDQoNCg0KDQoNCg0K
DQoNCg0KDQoNCg0KDQoNCg0KDQoNCg0KDQoNCg0KDQoNCg0KDQoNCg0KRGF2YXJpLCBldCBhbC4g
ICAgICAgICAgIEV4cGlyZXMgQXVndXN0IDI3LCAyMDEzICAgICAgICAgICAgICAgW1BhZ2UgMThd
DQoMDQpJbnRlcm5ldC1EcmFmdCAgICAgICAgVHJhbnNwb3J0aW5nIFRpbWluZyBvdmVyIE1QTFMg
ICAgICAgIEZlYnJ1YXJ5IDIwMTMNCg0KDQoxMS4gIEVudHJvcHkNCg0KICAgVG8gZW5zdXJlIGFs
bCBUaW1pbmcgbWVzc2FnZXMgaW4gYSBUaW1pbmcgTFNQIHRha2UgdGhlIHNhbWUgcGF0aCwNCiAg
IEVudHJvcHkgTVVTVCBOT1QgYmUgdXNlZCBmb3IgdGhlIFRpbWluZyBMU1AgW21wbHMtZW50cm9w
eV0gYW5kDQogICBFbnRyb3B5IE1TVVQgTk9UIGJlIHVzZWQgZm9yIHRoZSBQV3MgdGhhdCBhcmUg
Y2FycmllZCBpbnNpZGUgVGltaW5nDQogICBMU1AgW1JGQzYzOTFdLg0KDQoNCg0KDQoNCg0KDQoN
Cg0KDQoNCg0KDQoNCg0KDQoNCg0KDQoNCg0KDQoNCg0KDQoNCg0KDQoNCg0KDQoNCg0KDQoNCg0K
DQoNCg0KDQoNCg0KDQoNCg0KRGF2YXJpLCBldCBhbC4gICAgICAgICAgIEV4cGlyZXMgQXVndXN0
IDI3LCAyMDEzICAgICAgICAgICAgICAgW1BhZ2UgMTldDQoMDQpJbnRlcm5ldC1EcmFmdCAgICAg
ICAgVHJhbnNwb3J0aW5nIFRpbWluZyBvdmVyIE1QTFMgICAgICAgIEZlYnJ1YXJ5IDIwMTMNCg0K
DQoxMi4gIE9BTSwgQ29udHJvbCBhbmQgTWFuYWdlbWVudA0KDQogICBJbiBvcmRlciB0byBtb25p
dG9yIFRpbWluZyBMU1BzIGFuZCB0aGVpciBlbmNhcHN1bGF0ZWQgUFdzLCB0aGV5IE1VU1QNCiAg
IGJlIGFibGUgdG8gY2FycnkgT0FNIGFuZCBtYW5hZ2VtZW50IG1lc3NhZ2VzLiAgVGhlc2UgbWFu
YWdlbWVudA0KICAgbWVzc2FnZXMgTVVTVCBiZSBkaWZmZXJlbnRpYXRlZCBmcm9tIFRpbWluZyBt
ZXNzYWdlcyB2aWEgYWxyZWFkeQ0KICAgZGVmaW5lZCBJRVRGIG1ldGhvZHMuDQoNCiAgIEZvciBl
eGFtcGxlIEJGRCBbUkZDNTg4MF0sIFtSRkM1ODg0XSBhbmQgTFNQLVBpbmcgW1JGQzQzODldIE1B
WSBydW4NCiAgIG92ZXIgUFRQIExTUHMgdmlhIFVEUC9JUCBlbmNhcHN1bGF0aW9uIG9yIHZpYSBH
QUwvRy1BQ0guICBUaGVzZQ0KICAgTWFuYWdlbWVudCBwcm90b2NvbHMgY2FuIGVhc2lseSBiZSBp
ZGVudGlmaWVkIGJ5IHRoZSBVRFAgRGVzdGluYXRpb24NCiAgIFBvcnQgbnVtYmVyIG9yIGJ5IEdB
TC9BQ0ggcmVzcGVjdGl2ZWx5Lg0KDQogICBBbHNvIEJGRCwgTFNQLVBpbmcgYW5kIG90aGVyIG1h
bmFnZW1lbnQgbWVzc2FnZXMgTUFZIHJ1biBvdmVyIHRoZSBQV3MNCiAgIGVuY2Fwc3VsYXRlZCBp
biBUaW1pbmcgTFNQIHZpYSBvbmUgb2YgdGhlIGRlZmluZWQgVkNDVnMgKFR5cGUgMSwgMyBvcg0K
ICAgNCkgW1JGQzUwODVdIChub3RlIHRoYXQgVkNDViBUeXBlIDIgdXNpbmcgUm91dGVyIEFsZXJ0
IExhYmVsIGlzIGdvaW5nDQogICB0byBiZSBkZXByZWNhdGVkIGJ5IElFVEYpLiAgSW4gdGhpcyBj
YXNlIEctQUNILCBQVyBsYWJlbCAoVFRMPTEpIG9yDQogICBHQUwtQUNIIGFyZSB1c2VkIHRvIGlk
ZW50aWZ5IHN1Y2ggbWFuYWdlbWVudCBtZXNzYWdlcy4NCg0KDQoNCg0KDQoNCg0KDQoNCg0KDQoN
Cg0KDQoNCg0KDQoNCg0KDQoNCg0KDQoNCg0KDQoNCg0KDQoNCg0KDQoNCg0KRGF2YXJpLCBldCBh
bC4gICAgICAgICAgIEV4cGlyZXMgQXVndXN0IDI3LCAyMDEzICAgICAgICAgICAgICAgW1BhZ2Ug
MjBdDQoMDQpJbnRlcm5ldC1EcmFmdCAgICAgICAgVHJhbnNwb3J0aW5nIFRpbWluZyBvdmVyIE1Q
TFMgICAgICAgIEZlYnJ1YXJ5IDIwMTMNCg0KDQoxMy4gIFFvUyBDb25zaWRlcmF0aW9ucw0KDQog
ICBJbiBuZXR3b3JrIGRlcGxveW1lbnRzIHdoZXJlIG5vdCBldmVyeSBMU1IvTEVSIGlzIFRpbWlu
Zy1hd2FyZSwgaXQgaXMNCiAgIGltcG9ydGFudCB0byByZWR1Y2UgdGhlIGltcGFjdCBvZiB0aGUg
bm9uLVRpbWluZy1hd2FyZSBMU1IvTEVScyBvbg0KICAgdGhlIHRpbWluZyByZWNvdmVyeSBpbiB0
aGUgc2xhdmUgY2xvY2suICBUaGUgVGltaW5nIG1lc3NhZ2VzIGFyZSB0aW1lDQogICBjcml0aWNh
bCBhbmQgbXVzdCBiZSB0cmVhdGVkIHdpdGggdGhlIGhpZ2hlc3QgcHJpb3JpdHkuICBUaGVyZWZv
cmUNCiAgIFRpbWluZyBvdmVyIE1QTFMgbWVzc2FnZXMgbXVzdCBiZSB0cmVhdGVkIHdpdGggdGhl
IGhpZ2hlc3QgcHJpb3JpdHkNCiAgIGluIHRoZSByb3V0ZXJzLiAgVGhpcyBjYW4gYmUgYWNoaWV2
ZWQgYnkgcHJvcGVyIHNldHVwIG9mIFRpbWluZyBMU1BzLg0KDQogICBJdCBpcyByZWNvbW1lbmRl
ZCB0aGF0IHRoZSBUaW1pbmcgTFNQcyBhcmUgc2V0dXAgb3IgY29uZmlndXJlZA0KICAgcHJvcGVy
bHkgdG8gaW5kaWNhdGUgRUYtUEhCIFtSRkMzMjQ2XWZvciB0aGUgQ29TIGFuZCBHcmVlbiBbUkZD
MjY5N10NCiAgIGZvciBkcm9wIGVsaWdpYmlsaXR5Lg0KDQoNCg0KDQoNCg0KDQoNCg0KDQoNCg0K
DQoNCg0KDQoNCg0KDQoNCg0KDQoNCg0KDQoNCg0KDQoNCg0KDQoNCg0KDQoNCg0KDQoNCg0KRGF2
YXJpLCBldCBhbC4gICAgICAgICAgIEV4cGlyZXMgQXVndXN0IDI3LCAyMDEzICAgICAgICAgICAg
ICAgW1BhZ2UgMjFdDQoMDQpJbnRlcm5ldC1EcmFmdCAgICAgICAgVHJhbnNwb3J0aW5nIFRpbWlu
ZyBvdmVyIE1QTFMgICAgICAgIEZlYnJ1YXJ5IDIwMTMNCg0KDQoxNC4gIEZDUyBSZWNhbGN1bGF0
aW9uDQoNCiAgIFdoZW4gdGltZS1zdGFtcCBnZW5lcmF0aW9uIGFuZCB0aW1pbmcgcGFja2V0IGFk
anVzdG1lbnQgaXMgcGVyZm9ybWVkDQogICBuZWFyIHRoZSBwaHlzaWNhbCBwb3J0IGhhcmR3YXJl
LCB0aGUgcHJvY2VzcyBNVVNUIGluY2x1ZGUNCiAgIHJlY2FsY3VsYXRpb24gb2YgdGhlIEV0aGVy
bmV0IEZDUy4gIEFsc28gRkNTIHJldGVudGlvbiBmb3IgdGhlDQogICBwYXlsb2FkIEV0aGVybmV0
IGRlc2NyaWJlZCBpbiBbUkZDNDcyMF0gTVVTVCBOT1QgYmUgdXNlZC4NCg0KDQoNCg0KDQoNCg0K
DQoNCg0KDQoNCg0KDQoNCg0KDQoNCg0KDQoNCg0KDQoNCg0KDQoNCg0KDQoNCg0KDQoNCg0KDQoN
Cg0KDQoNCg0KDQoNCg0KDQoNCkRhdmFyaSwgZXQgYWwuICAgICAgICAgICBFeHBpcmVzIEF1Z3Vz
dCAyNywgMjAxMyAgICAgICAgICAgICAgIFtQYWdlIDIyXQ0KDA0KSW50ZXJuZXQtRHJhZnQgICAg
ICAgIFRyYW5zcG9ydGluZyBUaW1pbmcgb3ZlciBNUExTICAgICAgICBGZWJydWFyeSAyMDEzDQoN
Cg0KMTUuICBVRFAgQ2hlY2tzdW0gQ29ycmVjdGlvbg0KDQogICBGb3IgVURQL0lQIGVuY2Fwc3Vs
YXRpb24gbW9kZSBvZiBUaW1pbmcgb3ZlciBNUExTLCB0aGUgVURQIGNoZWNrc3VtDQogICBtYXkg
YmUgcmVxdWlyZWQgYXMgcGVyIFVEUCB0cmFuc3BvcnQgc3RhbmRhcmRzLg0KDQogICBXaGVuIFVE
UCBjaGVja3N1bSBpcyB1c2VkLCBlYWNoIFRpbWluZy1hd2FyZSBMRVIvTFNSIG11c3QgZWl0aGVy
DQogICBpbmNyZW1lbnRhbGx5IHVwZGF0ZSB0aGUgVURQIGNoZWNrc3VtIGFmdGVyIFRpbWUgc3Rh
bXBpbmcgb3INCiAgIENvcnJlY3Rpb24gRmllbGQgdXBkYXRlIG9yIHZlcmlmeSB0aGUgVURQIGNo
ZWNrc3VtIG9uIHJlY2VwdGlvbiBmcm9tDQogICB1cHN0cmVhbSBhbmQgcmVjYWxjdWxhdGUgdGhl
IGNoZWNrc3VtIGNvbXBsZXRlbHkgb24gdHJhbnNtaXNzaW9uIHRvDQogICBkb3duc3RyZWFtIG5v
ZGUgYWZ0ZXIgVGltZSBzdGFtcGluZyBvciBDb3JyZWN0aW9uIEZpZWxkIHVwZGF0ZS4NCg0KDQoN
Cg0KDQoNCg0KDQoNCg0KDQoNCg0KDQoNCg0KDQoNCg0KDQoNCg0KDQoNCg0KDQoNCg0KDQoNCg0K
DQoNCg0KDQoNCg0KDQoNCg0KDQpEYXZhcmksIGV0IGFsLiAgICAgICAgICAgRXhwaXJlcyBBdWd1
c3QgMjcsIDIwMTMgICAgICAgICAgICAgICBbUGFnZSAyM10NCgwNCkludGVybmV0LURyYWZ0ICAg
ICAgICBUcmFuc3BvcnRpbmcgVGltaW5nIG92ZXIgTVBMUyAgICAgICAgRmVicnVhcnkgMjAxMw0K
DQoNCjE2LiAgUm91dGluZyBleHRlbnNpb25zIGZvciBUaW1pbmctYXdhcmUgUm91dGVycw0KDQog
ICBNUExTLVRFIHJvdXRpbmcgcmVsaWVzIG9uIGV4dGVuc2lvbnMgdG8gT1NQRiBbUkZDMjMyOF0g
W1JGQzUzNDBdIGFuZA0KICAgSVMtSVMgW0lTT10gW1JGQzExOTVdIGluIG9yZGVyIHRvIGFkdmVy
dGlzZSBUcmFmZmljIEVuZ2luZWVyaW5nIChURSkNCiAgIGxpbmsgaW5mb3JtYXRpb24gdXNlZCBm
b3IgY29uc3RyYWludC1iYXNlZCByb3V0aW5nLg0KDQogICBJbmRlZWQsIGl0IGlzIHVzZWZ1bCB0
byBhZHZlcnRpc2UgZGF0YSBwbGFuZSBURSByb3V0ZXIgbGluaw0KICAgY2FwYWJpbGl0aWVzLCBz
dWNoIGFzIHRoZSBjYXBhYmlsaXR5IGZvciBhIHJvdXRlciB0byBiZSBUaW1pbmctYXdhcmUuDQog
ICBUaGlzIGNhcGFiaWxpdHkgTVVTVCB0aGVuIGJlIHRha2VuIGludG8gYWNjb3VudCBkdXJpbmcg
cGF0aA0KICAgY29tcHV0YXRpb24gdG8gcHJlZmVyIG9yIGV2ZW4gcmVxdWlyZSBsaW5rcyB0aGF0
IGFkdmVydGlzZSB0aGVtc2VsdmVzDQogICBhcyBUaW1pbmctYXdhcmUuICBJbiB0aGlzIHdheSB0
aGUgcGF0aCBjYW4gZW5zdXJlIHRoZSBlbnRyeSBhbmQgZXhpdA0KICAgcG9pbnRzIGludG8gdGhl
IExFUnMgYW5kLCBpZiBkZXNpcmVkLCB0aGUgbGlua3MgaW50byB0aGUgTFNScyBhcmUNCiAgIGFi
bGUgdG8gcGVyZm9ybSBwb3J0IGJhc2VkIHRpbWUtc3RhbXBpbmcgdGh1cyBtaW5pbWl6aW5nIHRo
ZWlyIGltcGFjdA0KICAgb24gdGhlIHBlcmZvcm1hbmNlIG9mIHRoZSBzbGF2ZSBjbG9jay4NCg0K
ICAgZXh0ZW5zaW9ucyBhcmUgcmVxdWlyZWQgdG8gT1NQRiBhbmQgSVMtSVMgaW4gb3JkZXIgdG8g
YWR2ZXJ0aXNlDQogICBUaW1pbmctYXdhcmUgY2FwYWJpbGl0aWVzIG9mIGEgbGluay4gIFN1Y2gg
ZXh0ZW5zaW9ucyBhcmUgb3V0c2lkZSB0aGUNCiAgIHNjb3BlIG9mIHRoaXMgZG9jdW1lbnQ7IGhv
d2V2ZXIgc3VjaCBleHRlbnNpb24gU0hPVUxEIGJlIGFibGUgdG8NCiAgIHNpZ25hbCB0aGUgZm9s
bG93aW5nIGluZm9ybWF0aW9uIHBlciBSb3V0ZXIgTGluazoNCg0KICAgbyAgQ2FwYWJsZSBvZiBw
cm9jZXNzaW5nIFBUUCwgTlRQIG9yIG90aGVyIFRpbWluZyBmbG93cw0KDQogICBvICBDYXBhYmxl
IG9mIHBlcmZvcm1pbmcgVHJhbnNwYXJlbnQgQ2xvY2sgb3BlcmF0aW9uDQoNCiAgIG8gIENhcGFi
bGUgb2YgcGVyZm9ybWluZyBCb3VuZGFyeSBDbG9jayBvcGVyYXRpb24NCg0KDQoNCg0KDQoNCg0K
DQoNCg0KDQoNCg0KDQoNCg0KDQoNCg0KDQoNCg0KDQoNCg0KDQpEYXZhcmksIGV0IGFsLiAgICAg
ICAgICAgRXhwaXJlcyBBdWd1c3QgMjcsIDIwMTMgICAgICAgICAgICAgICBbUGFnZSAyNF0NCgwN
CkludGVybmV0LURyYWZ0ICAgICAgICBUcmFuc3BvcnRpbmcgVGltaW5nIG92ZXIgTVBMUyAgICAg
ICAgRmVicnVhcnkgMjAxMw0KDQoNCjE3LiAgU2lnbmFsaW5nIEV4dGVuc2lvbnMgZm9yIENyZWF0
aW5nIFRpbWluZyBMU1BzDQoNCiAgIFJTVlAtVEUgc2lnbmFsaW5nIE1BWSBiZSB1c2VkIHRvIHNl
dHVwIHRoZSB0aW1pbmcgTFNQcy4gIFdoZW4gUlNWUC1URQ0KICAgaXMgdXNlZCB0byBzZXR1cCBU
aW1pbmcgTFNQcywgc29tZSBpbmZvcm1hdGlvbiB0aGF0IGluZGljYXRlcyB0aGF0DQogICB0aGUg
TFNQIGlzIGNhcnJ5aW5nIFRpbWluZyBmbG93cyBNVVNUIGJlIGluY2x1ZGVkIGluIHRoZSBuZXcN
CiAgIEV4dGVuc2lvbnMgdG8gUlNWUC1URToNCg0KICAgVGhlIGZvbGxvd2luZyBpbmZvcm1hdGlv
biBNQVkgYWxzbyBiZSBpbmNsdWRlZCBpbiB0aGUgbmV3IEV4dGVuc2lvbnMNCiAgIHRvIFJTVlAt
VEU6DQoNCiAgIG8gIE9mZnNldCBmcm9tIEJvdHRvbSBvZiBTdGFjayAoQm9TKSB0byB0aGUgc3Rh
cnQgb2YgdGhlIFRpbWUtc3RhbXANCiAgICAgIGZpZWxkDQoNCiAgIG8gIE51bWJlciBvZiBWTEFO
cyBpbiBjYXNlIG9mIFBXIGVuY2Fwc3VsYXRpb24NCg0KICAgbyAgVGltZXN0YW1wIGZpZWxkIFR5
cGUNCg0KICAgICAgKiAgQ29ycmVjdGlvbiBGaWVsZCwgVGltZXN0YW1wDQoNCiAgIG8gIFRpbWVz
dGFtcCBGaWVsZCBmb3JtYXQNCg0KICAgICAgKiAgNjQtYml0IFBUUHYxLCA4MC1iaXQgUFRQdjIs
IDMyLWJpdCBOVFAsIDY0LWJpdCBOVFAsIDEyOC1iaXQNCiAgICAgICAgIE5UUCwgZXRjLg0KDQog
ICBOb3RlIHRoYXQgaW4gY2FzZSB0aGUgYWJvdmUgb3B0aW9uYWwgaW5mb3JtYXRpb24gaXMgc2ln
bmFsZWQgd2l0aA0KICAgUlNWUC1URSBmb3IgYSBUaW1pbmcgTFNQLCBhbGwgdGhlIFRpbWluZyBw
YWNrZXRzIGNhcnJpZWQgaW4gdGhhdCBMU1ANCiAgIG11c3QgaGF2ZSB0aGUgc2FtZSBzaWduYWxl
ZCBjaGFyYWN0ZXJpc3RpY3MuICBGb3IgZXhhbXBsZSBpZg0KICAgVGltZXN0YW1wIGZvcm1hdCBp
cyBzaWduYWxlZCBhcyA2NC1iaXQgUFRQdjEsIHRoZW4gYWxsIFRpbWluZyBwYWNrZXRzDQogICBt
dXN0IHVzZSA2NC1iaXQgUFRQdjEgdGltZS1zdGFtcC4NCg0KDQoNCg0KDQoNCg0KDQoNCg0KDQoN
Cg0KDQoNCg0KDQoNCg0KDQoNCg0KRGF2YXJpLCBldCBhbC4gICAgICAgICAgIEV4cGlyZXMgQXVn
dXN0IDI3LCAyMDEzICAgICAgICAgICAgICAgW1BhZ2UgMjVdDQoMDQpJbnRlcm5ldC1EcmFmdCAg
ICAgICAgVHJhbnNwb3J0aW5nIFRpbWluZyBvdmVyIE1QTFMgICAgICAgIEZlYnJ1YXJ5IDIwMTMN
Cg0KDQoxOC4gIEJlaGF2aW9yIG9mIExFUi9MU1INCg0KICAgVGltaW5nLWNhcGFibGUvYXdhcmUg
TEVScyBhbmQgTFNScyBhcmUgcm91dGVycyB0aGF0IGhhdmUgb25lIG9yIG1vcmUNCiAgIGludGVy
ZmFjZXMgdGhhdCBjYW4gcGVyZm9ybSBUaW1pbmcgb3BlcmF0aW9ucyAoT0MvQkMvVEMpIG9uIFRp
bWluZw0KICAgcGFja2V0cyBhbmQgYXJlIGNvbmZpZ3VyZWQgdG8gZG8gc28uICBUaW1pbmctY2Fw
YWJsZS9hd2FyZSBMRVJzIGFuZA0KICAgTFNScyBjYW4gYWR2ZXJ0aXNlIHRoZWlyIFRpbWluZy1j
YXBhYmlsaXR5IHBlci1pbnRlcmZhY2UgdmlhIGNvbnRyb2wNCiAgIHBsYW5lIHN1Y2ggYXMgT1NQ
RiBvciBJUy1JUy4gIFRoZSBUaW1pbmctY2FwYWJsZS9hd2FyZSBMRVJzIGNhbiB0aGVuDQogICBz
aWduYWxzIFRpbWluZyBMU1BzIHZpYSBSU1ZQLVRFIHNpZ25hbGluZy4gIEFsdGVybmF0aXZlbHkg
dGhlIFRpbWluZw0KICAgY2FwYWJpbGl0eSBvZiBMRVIgYW5kIExTUnMgbWF5IGJlIGNvbmZpZ3Vy
ZWQgaW4gYSBjZW50cmFsaXplZA0KICAgY29udHJvbGxlciBhbmQgdGhlIFRpbWluZyBMU1AgbWF5
IGJlIHNldHVwIHVzaW5nIG1hbnVhbCBjb25maWd1cmF0aW9uDQogICBvciBvdGhlciBtZXRob2Rz
IHN1Y2ggYXMgU0ROLg0KDQoxOC4xLiAgQmVoYXZpb3Igb2YgVGltaW5nLWNhcGFibGUvYXdhcmUg
TEVSDQoNCiAgIFdoZW4gYSBUaW1pbmctY2FwYWJsZS9hd2FyZSBMRVIgYmVoYXZlcyBhcyBhIFRy
YW5zcGFyZW50IGNsb2NrIGFuZA0KICAgcmVjZWl2ZXMgYSBUaW1pbmcgbWVzc2FnZSBmcm9tIGEg
VGltaW5nLWNhcGFibGUvYXdhcmUgbm9uLU1QTFMNCiAgIGludGVyZmFjZSwgdGhlIExFUiB1cGRh
dGVzIHRoZSBDb3JyZWN0aW9uIEZpZWxkIChDRikgYW5kIGVuY2Fwc3VsYXRlcw0KICAgYW5kIGZv
cndhcmRzIHRoZSB0aW1pbmcgbWVzc2FnZSBvdmVyIHByZXZpb3VzbHkgZXN0YWJsaXNoZWQgVGlt
aW5nDQogICBMU1AuICBBbHNvIHdoZW4gYSBUaW1pbmcgbWVzc2FnZSBpcyByZWNlaXZlZCBmcm9t
IGEgVGltaW5nLWNhcGFibGUvDQogICBhd2FyZSBNUExTIGludGVyZmFjZSwgTEVSIHVwZGF0ZXMg
dGhlIENvcnJlY3Rpb24gRmlsZWQgKENGKSBhbmQNCiAgIGRlY2Fwc3VsYXRlcyB0aGUgTVBMUyBl
bmNhcHN1bGF0aW9uIGFuZCBmb3J3YXJkcyB0aGUgdGltaW5nIG1lc3NhZ2UNCiAgIHRvIGEgbm9u
LU1QTFMgaW50ZXJmYWNlLg0KDQogICBXaGVuIGEgVGltaW5nLWNhcGFibGUvYXdhcmUgTEVSIGJl
aGF2ZXMgYXMgYSBCb3VuZGFyeSBjbG9jayBhbmQNCiAgIHJlY2VpdmVzIGEgVGltaW5nIG1lc3Nh
Z2UgZnJvbSBhIFRpbWluZy1jYXBhYmxlL2F3YXJlIG5vbiBNUExTDQogICBpbnRlcmZhY2UsIHRo
ZSBMRVIgVGltZXN0YW1wcyB0aGUgVGltaW5nIHBhY2tldCBhbmQgc2VuZHMgaXQgdG8gdGhlDQog
ICBMRVJzIEJvdW5kYXJ5IGNsb2NrIHByb2Nlc3NpbmcgbW9kdWxlLiAgQWxzbyB3aGVuIGEgVGlt
aW5nIG1lc3NhZ2UgaXMNCiAgIHJlY2VpdmVkIGZyb20gYSBUaW1pbmctIGNhcGFibGUvYXdhcmUg
TVBMUyBpbnRlcmZhY2UsIHRoZSBMRVINCiAgIFRpbWVzdGFtcHMgdGhlIFRpbWluZyBwYWNrZXQg
YW5kIHNlbmRzIGl0IHRvIHRoZSBMRVJzIEJvdW5kYXJ5IGNsb2NrDQogICBwcm9jZXNzaW5nIG1v
ZHVsZS4NCg0KICAgV2hlbiBhIFRpbWluZy1jYXBhYmxlL2F3YXJlIExFUiBiZWhhdmVzIGFzIGFu
IE9yZGluYXJ5IENsb2NrIHRvd2FyZA0KICAgdGhlIE1QTFMgbmV0d29yaywgYW5kIHJlY2VpdmVz
IGEgVGltaW5nIG1lc3NhZ2UgZnJvbSBhIFRpbWluZy0NCiAgIGNhcGFibGUvYXdhcmUgTVBMUyBp
bnRlcmZhY2UsIHRoZSBMRVIgVGltZXN0YW1wcyB0aGUgVGltaW5nIHBhY2tldA0KICAgYW5kIHNl
bmRzIGl0IHRvIHRoZSBMRVJzIE9yZGluYXJ5IGNsb2NrIHByb2Nlc3NpbmcgbW9kdWxlLg0KDQox
OC4yLiAgQmVoYXZpb3Igb2YgVGltaW5nLWNhcGFibGUvYXdhcmUgTFNSDQoNCiAgIEEgVGltaW5n
LWNhcGFibGUvYXdhcmUgTFNSIGJlaGF2ZXMgYXMgYSBUcmFuc3BhcmVudCBjbG9jayBhbmQNCiAg
IHJlY2VpdmVzIGEgVGltaW5nIG1lc3NhZ2UgZnJvbSBhIFRpbWluZy1jYXBhYmxlL2F3YXJlIE1Q
TFMgaW50ZXJmYWNlLg0KICAgVGhlIExTUiB1cGRhdGVzIHRoZSBDb3JyZWN0aW9uIEZpbGVkIChD
RikgYW5kIGZvcndhcmRzIHRoZSB0aW1pbmcNCiAgIG1lc3NhZ2Ugb3ZlciBhbm90aGVyIE1QTFMg
aW50ZXJmYWNlLg0KDQoxOC4zLiAgQmVoYXZpb3Igb2Ygbm9uLVRpbWluZy1jYXBhYmxlL2F3YXJl
IExTUg0KDQogICBJdCBpcyBtb3N0IGJlbmVmaWNpYWwgd2hlbiBhbGwgTFNScyBpbiB0aGUgcGF0
aCBvZiBhIFRpbWluZyBMU1AgYmUNCiAgIHRpbWluZy1DYXBhYmxlL2F3YXJlIExTUnMuICBUaGlz
IHdvdWxkIGVuc3VyZSB0aGUgaGlnaGVzdCBxdWFsaXR5DQogICB0aW1lIGFuZCBjbG9jayBzeW5j
aHJvbml6YXRpb24gYnkgVGltaW5nIFNsYXZlIENsb2Nrcy4gIEhvd2V2ZXIsIHRoaXMNCg0KDQoN
CkRhdmFyaSwgZXQgYWwuICAgICAgICAgICBFeHBpcmVzIEF1Z3VzdCAyNywgMjAxMyAgICAgICAg
ICAgICAgIFtQYWdlIDI2XQ0KDA0KSW50ZXJuZXQtRHJhZnQgICAgICAgIFRyYW5zcG9ydGluZyBU
aW1pbmcgb3ZlciBNUExTICAgICAgICBGZWJydWFyeSAyMDEzDQoNCg0KICAgc3BlY2lmaWNhdGlv
biBkb2VzIG5vdCBtYW5kYXRlIHRoYXQgYWxsIExTUnMgaW4gcGF0aCBvZiBhIFRpbWluZyBMU1AN
CiAgIGJlIFRpbWluZy0gY2FwYWJsZS9hd2FyZS4NCg0KICAgTm9uLVRpbWluZy1jYXBhYmxlL2F3
YXJlIExTUnMganVzdCBzd2l0Y2ggdGhlIHBhY2tldHMgZW5jYXBzdWxhdGVkIGluDQogICBUaW1p
bmcgTFNQcyBhbmQgZG9udCBwZXJmb3JtIGFueSBUaW1pbmcgb3BlcmF0aW9uIChUQykuICBIb3dl
dmVyIGFzDQogICBleHBsYWluZWQgaW4gUW9TIHNlY3Rpb24gdGhlIFRpbWluZzggb3ZlciBNUExT
IHBhY2tldHMgTVVTVCBiZSBzdGlsbA0KICAgYmUgdHJlYXRlZCB3aXRoIHRoZSBoaWdoZXN0IHBy
aW9yaXR5IGJhc2VkIG9uIHRoZWlyIFRyYWZmaWMgQ2xhc3MNCiAgIChUQykgbWFya2luZy4NCg0K
DQoNCg0KDQoNCg0KDQoNCg0KDQoNCg0KDQoNCg0KDQoNCg0KDQoNCg0KDQoNCg0KDQoNCg0KDQoN
Cg0KDQoNCg0KDQoNCg0KDQoNCg0KDQoNCg0KRGF2YXJpLCBldCBhbC4gICAgICAgICAgIEV4cGly
ZXMgQXVndXN0IDI3LCAyMDEzICAgICAgICAgICAgICAgW1BhZ2UgMjddDQoMDQpJbnRlcm5ldC1E
cmFmdCAgICAgICAgVHJhbnNwb3J0aW5nIFRpbWluZyBvdmVyIE1QTFMgICAgICAgIEZlYnJ1YXJ5
IDIwMTMNCg0KDQoxOS4gIE90aGVyIGNvbnNpZGVyYXRpb25zDQoNCiAgIFtJRUVFXSBkZWZpbmVz
IGFuIG9wdGlvbmFsIHBlZXItdG8tcGVlciBUcmFuc3BhcmVudCBjbG9ja2luZyB0aGF0DQogICBy
ZXF1aXJlcyBwZWVyIGRlbGF5IG1lYXN1cmVtZW50IGJldHdlZW4gdHdvIGFkamFjZW50IFRpbWlu
Zy1jYXBhYmxlLw0KICAgYXdhcmUgcm91dGVycy9zd2l0Y2hlcy4gIFBlZXIgZGVsYXkgbWVhc3Vy
ZW1lbnQgbWVzc2FnZXMgbmVlZCB0byBiZQ0KICAgdGltZSBzdGFtcGVkIGFuZCB0ZXJtaW5hdGVk
IGJ5IHRoZSBUaW1pbmctY2FwYWJsZS9hd2FyZSByb3V0ZXJzLw0KICAgc3dpdGNoZXMuICBUaGlz
IG1lYW5zIHRoYXQgdHdvIGFkamFjZW50IExTUnMgbWF5IGJlIGVuZ2FnZWQgaW4gYSBwZWVyDQog
ICBkZWxheSBtZWFzdXJlbWVudC4NCg0KICAgRm9yIHRyYW5zcG9ydGluZyBzdWNoIHBlZXIgZGVs
YXkgbWVhc3VyZW1lbnQgbWVzc2FnZXMgYSBzaW5nbGUtaG9wDQogICBMU1AgU0hPVUxEIHRvIGJl
IGNyZWF0ZWQgYmV0d2VlbiB0aGUgdHdvIGFkamFjZW50IExTUnMgZW5nYWdlZCBpbg0KICAgcGVl
ciBkZWxheSBtZWFzdXJlbWVudCB0byBjYXJyeSBwZWVyIGRlbGF5IG1lYXN1cmVtZW50IG1lc3Nh
Z2VzLg0KICAgT3RoZXIgbWV0aG9kcyBzdWNoIGFzIFBUUCB0cmFuc3BvcnQgb3ZlciBFdGhlcm5l
dCBNQVkgYmUgdXNlZCBmb3INCiAgIHRyYW5zcG9ydGluZyBwZWVyIGRlbGF5IG1lYXN1cmVtZW50
IG1lc3NhZ2VzIGlmIHRoZSBsaW5rIGJldHdlZW4gdGhlDQogICB0d28gcm91dGVycyBpcyBFdGhl
cm5ldC4NCg0KICAgSW4gUGVlci10by1wZWVyIHRyYW5zcGFyZW50IGNsb2NraW5nIChQMlAgVEMp
LCBhIFRpbWluZy1jYXBhYmxlLyB3YXJlDQogICByb3V0ZXJzL3N3aXRjaGVzIE1VU1QgbWFpbnRh
aW4gYSBsaXN0IG9mIGFsbCB0aGUgbmVpZ2hib3JzIGl0IG5lZWRzDQogICB0byBzZW5kIGEgUERl
bGF5X1JlcSB0bywgd2hlcmUgZWFjaCBuZWlnaGJvciBjb3JyZXNwb25kcyB0byBhIHRpbWluZw0K
ICAgTFNQLg0KDQogICBUaGUgdXNlIG9mIEV4cGxpY2l0IE51bGwgTGFiZWwgKExhYmVsPSAwIG9y
IDIpIGlzIGFjY2VwdGFibGUgYXMgbG9uZw0KICAgYXMgZWl0aGVyIHRoZSBFeHBsaWNpdCBOdWxs
IGxhYmVsIGlzIHRoZSBib3R0b20gb2Ygc3RhY2sgbGFiZWwNCiAgIChhcHBsaWNhYmxlIG9ubHkg
dG8gVURQL0lQIGVuY2Fwc3VsYXRpb24pIG9yIHRoZSBsYWJlbCBiZWxvdyB0aGUNCiAgIEV4cGxp
Y2l0IE51bGwgbGFiZWwgaXMgYSBQVFAgbGFiZWwuDQoNCg0KDQoNCg0KDQoNCg0KDQoNCg0KDQoN
Cg0KDQoNCg0KDQoNCg0KDQoNCg0KDQoNCg0KRGF2YXJpLCBldCBhbC4gICAgICAgICAgIEV4cGly
ZXMgQXVndXN0IDI3LCAyMDEzICAgICAgICAgICAgICAgW1BhZ2UgMjhdDQoMDQpJbnRlcm5ldC1E
cmFmdCAgICAgICAgVHJhbnNwb3J0aW5nIFRpbWluZyBvdmVyIE1QTFMgICAgICAgIEZlYnJ1YXJ5
IDIwMTMNCg0KDQoyMC4gIFNlY3VyaXR5IENvbnNpZGVyYXRpb25zDQoNCiAgIE1QTFMgUFcgc2Vj
dXJpdHkgY29uc2lkZXJhdGlvbnMgaW4gZ2VuZXJhbCBhcmUgZGlzY3Vzc2VkIGluIFtSRkMzOTg1
XQ0KICAgYW5kIFtSRkM0NDQ3XSxhbmQgdGhvc2UgY29uc2lkZXJhdGlvbnMgYWxzbyBhcHBseSB0
byB0aGlzIGRvY3VtZW50Lg0KDQogICBBbiBleHBlcmltZW50YWwgc2VjdXJpdHkgcHJvdG9jb2wg
aXMgZGVmaW5lZCBpbiBbSUVFRV0uVGhlIFBUUA0KICAgc2VjdXJpdHkgZXh0ZW5zaW9uIGFuZCBw
cm90b2NvbCBwcm92aWRlcyBncm91cCBzb3VyY2UgYXV0aGVudGljYXRpb24sDQogICBtZXNzYWdl
IGludGVncml0eSwgYW5kIHJlcGxheSBhdHRhY2sgcHJvdGVjdGlvbiBmb3IgUFRQIG1lc3NhZ2Vz
Lg0KDQogICBXaGVuIHRoZSBNUExTIG5ldHdvcmsgKHByb3ZpZGVyIG5ldHdvcmspIHNlcnZlcyBt
dWx0aXBsZSBjdXN0b21lcnMsDQogICBpdCBpcyBpbXBvcnRhbnQgdG8gbWFpbnRhaW4gYW5kIHBy
b2Nlc3MgZWFjaCBjdXN0b21lcnMgY2xvY2sgYW5kDQogICBUaW1pbmcgbWVzc2FnZXMgc2VwYXJh
dGVseSBmcm9tIG90aGVyIGN1c3RvbWVycyB0byBlbnN1cmUgdGhlcmUgaXMgbm8NCiAgIGNyb3Nz
LSBjdXN0b21lciBlZmZlY3QuICBGb3IgZXhhbXBsZSBpZiBhbiBMRVIgQkMgaXMgc3luY2hyb25p
emVkIHRvDQogICBhIHNwZWNpZmljIGdyYW5kbWFzdGVyLCBiZWxvbmdpbmcgdG8gY3VzdG9tZXIg
QSwgdGhlbiB0aGUgTEVSIE1VU1QNCiAgIHVzZSB0aGF0IEJDIGNsb2NrIG9ubHkgZm9yIGN1c3Rv
bWVyIEEgdG8gZW5zdXJlIHRoYXQgY3VzdG9tZXIgQQ0KICAgY2Fubm90IGF0dGFjayBvdGhlciBj
dXN0b21lcnMgYnkgbWFuaXB1bGF0aW5nIGl0cyB0aW1lLg0KDQogICBUaW1pbmcgbWVzc2FnZXMg
KGFzIG9wcG9zZWQgdG8gcmVndWxhciBjdXN0b21lciBkYXRhKSBTSE9VTEQgbm90IGJlDQogICBl
bmNyeXB0ZWQgb3IgYXV0aGVudGljYXRlZCBvbiBhbiBlbmQtdG8tZW5kIGJhc2lzLiAgQWx0ZXJu
YXRpdmVseSwNCiAgIGF1dGhlbnRpY2F0aW9uL2ludGVncml0eSB2ZXJpZmljYXRpb24gbWVjaGFu
aXNtIGNhbiBiZSB1c2VkIGJ5IGENCiAgIHNoYXJlZCBzZWNyZXQgYmV0d2VlbiB0aGUgY3VzdG9t
ZXIgYW5kIHByb3ZpZGVyIG5vZGVzLg0KDQoNCg0KDQoNCg0KDQoNCg0KDQoNCg0KDQoNCg0KDQoN
Cg0KDQoNCg0KDQoNCg0KDQoNCg0KDQoNCg0KRGF2YXJpLCBldCBhbC4gICAgICAgICAgIEV4cGly
ZXMgQXVndXN0IDI3LCAyMDEzICAgICAgICAgICAgICAgW1BhZ2UgMjldDQoMDQpJbnRlcm5ldC1E
cmFmdCAgICAgICAgVHJhbnNwb3J0aW5nIFRpbWluZyBvdmVyIE1QTFMgICAgICAgIEZlYnJ1YXJ5
IDIwMTMNCg0KDQoyMS4gIEFwcGxpY2FiaWxpdHkgU3RhdGVtZW50DQoNCiAgIFRoZSBUaW1pbmcg
b3ZlciBNUExTIHRyYW5zcG9ydCBtZXRob2RzIGRlc2NyaWJlZCBpbiB0aGlzIGRvY3VtZW50DQog
ICBhcHBseSB0byB0aGUgZm9sbG93aW5nIG5ldHdvcmsgRWxlbWVudHM6DQoNCiAgIG8gIEFuIExF
UiByZWNlaXZlcyBJUCBvciBFdGhlcm5ldCBFbmNhcHN1bGF0ZWQgVGltaW5nIG1lc3NhZ2VzIGZy
b20gYQ0KICAgICAgbm9uLU1QTFMgaW50ZXJmYWNlIGFuZCBmb3J3YXJkcyB0aGVtIGFzIE1QTFMg
ZW5jYXBzdWxhdGVkIFRpbWluZw0KICAgICAgbWVzc2FnZXMgb3ZlciBUaW1pbmcgTFNQLCB3aGls
ZSBwZXJmb3JtaW5nIFRyYW5zcGFyZW50IENsb2NrDQogICAgICBmdW5jdGlvbmFsaXR5DQoNCiAg
IG8gIEFuIExFUiByZWNlaXZlcyBNUExTIGVuY2Fwc3VsYXRlZCBUaW1pbmcgbWVzc2FnZXMgZnJv
bSBhIFRpbWluZw0KICAgICAgTFNQIGFuZCBmb3J3YXJkcyB0aGVtIHRvIG5vbi1NUExTIGludGVy
ZmFjZSBhcyBJUCBvciBFdGhlcm5ldA0KICAgICAgRW5jYXBzdWxhdGVkIFRpbWluZyBtZXNzYWdl
cywgd2hpbGUgcGVyZm9ybWluZyBUcmFuc3BhcmVudCBDbG9jaw0KICAgICAgZnVuY3Rpb25hbGl0
eQ0KDQogICBvICBBbiBMRVIgcmVjZWl2ZXMgTVBMUyBlbmNhcHN1bGF0ZWQgVGltaW5nIG1lc3Nh
Z2VzIGZyb20gYSBUaW1pbmcNCiAgICAgIExTUCBhbmQgdGVybWluYXRlcyB0aGVtLCB3aGlsZSBw
ZXJmb3JtaW5nIHRoZSBPQyBvciBCQw0KICAgICAgZnVuY3Rpb25hbGl0eQ0KDQogICBvICBBbiBM
U1IgcmVjZWl2ZXMgTVBMUyBlbmNhcHN1bGF0ZWQgVGltaW5nIG1lc3NhZ2VzIGZyb20gYSBUaW1p
bmcNCiAgICAgIExTUCBhbmQgZm9yd2FyZHMgdGhlbSB0byBhbm90aGVyIE1QTFMgaW50ZXJmYWNl
LCB3aGlsZSBwZXJmb3JtaW5nDQogICAgICB0aGUgVEMgZnVuY3Rpb25hbGl0eQ0KDQogICBUaGlz
IGRvY3VtZW50IGFsc28gc3VwcG9ydHMgdGhlIGNhc2Ugd2hlcmUgbm90IGFsbCBMU1JzIGFyZSBU
aW1pbmctDQogICBjYXBhYmxlL2F3YXJlLiAgSXQgYWxzbyBzdXBwb3J0cyB0aGUgY2FzZSB3aGVy
ZSBub3QgYWxsIExFUi9MU1INCiAgIGludGVyZmFjZXMgYXJlIFRpbWluZy1jYXBhYmxlL2F3YXJl
Lg0KDQoNCg0KDQoNCg0KDQoNCg0KDQoNCg0KDQoNCg0KDQoNCg0KDQoNCg0KDQoNCg0KDQpEYXZh
cmksIGV0IGFsLiAgICAgICAgICAgRXhwaXJlcyBBdWd1c3QgMjcsIDIwMTMgICAgICAgICAgICAg
ICBbUGFnZSAzMF0NCgwNCkludGVybmV0LURyYWZ0ICAgICAgICBUcmFuc3BvcnRpbmcgVGltaW5n
IG92ZXIgTVBMUyAgICAgICAgRmVicnVhcnkgMjAxMw0KDQoNCjIyLiAgQWNrbm93bGVkZ2VtZW50
cw0KDQogICBUaGUgYXV0aG9ycyB3b3VsZCBsaWtlIHRvIHRoYW5rIEx1Y2EgTWFydGluaSwgUm9u
IENvaGVuLCBZYWFrb3YNCiAgIFN0ZWluLCBUYWwgTWl6cmFoaSwgU3RlZmFubyBSdWZmaW5pLCBM
dWNhIE1vbml0aSBhbmQgb3RoZXIgbWVtYmVycyBvZg0KICAgSUVURiBmb3IgcmV2aWV3aW5nIGFu
ZCBwcm92aWRpbmcgZmVlZGJhY2sgb24gdGhpcyBkcmFmdC4NCg0KDQoNCg0KDQoNCg0KDQoNCg0K
DQoNCg0KDQoNCg0KDQoNCg0KDQoNCg0KDQoNCg0KDQoNCg0KDQoNCg0KDQoNCg0KDQoNCg0KDQoN
Cg0KDQoNCg0KDQoNCg0KRGF2YXJpLCBldCBhbC4gICAgICAgICAgIEV4cGlyZXMgQXVndXN0IDI3
LCAyMDEzICAgICAgICAgICAgICAgW1BhZ2UgMzFdDQoMDQpJbnRlcm5ldC1EcmFmdCAgICAgICAg
VHJhbnNwb3J0aW5nIFRpbWluZyBvdmVyIE1QTFMgICAgICAgIEZlYnJ1YXJ5IDIwMTMNCg0KDQoy
My4gIElBTkEgQ29uc2lkZXJhdGlvbnMNCg0KICAgVGhlcmUgYXJlIG5vIElBTkEgcmVxdWlyZW1l
bnRzIGluIHRoaXMgc3BlY2lmaWNhdGlvbi4NCg0KDQoNCg0KDQoNCg0KDQoNCg0KDQoNCg0KDQoN
Cg0KDQoNCg0KDQoNCg0KDQoNCg0KDQoNCg0KDQoNCg0KDQoNCg0KDQoNCg0KDQoNCg0KDQoNCg0K
DQoNCg0KDQoNCkRhdmFyaSwgZXQgYWwuICAgICAgICAgICBFeHBpcmVzIEF1Z3VzdCAyNywgMjAx
MyAgICAgICAgICAgICAgIFtQYWdlIDMyXQ0KDA0KSW50ZXJuZXQtRHJhZnQgICAgICAgIFRyYW5z
cG9ydGluZyBUaW1pbmcgb3ZlciBNUExTICAgICAgICBGZWJydWFyeSAyMDEzDQoNCg0KMjQuICBS
ZWZlcmVuY2VzDQoNCjI0LjEuICBOb3JtYXRpdmUgUmVmZXJlbmNlcw0KDQogICBbSUVFRV0gICAg
IElFRUUgMTU4OC0yMDA4LCAiSUVFRSBTdGFuZGFyZCBmb3IgYSBQcmVjaXNpb24gQ2xvY2sNCiAg
ICAgICAgICAgICAgU3luY2hyb25pemF0aW9uIFByb3RvY29sIGZvciBOZXR3b3JrZWQgTWVhc3Vy
ZW1lbnQgYW5kDQogICAgICAgICAgICAgIENvbnRyb2wgU3lzdGVtcyIuDQoNCiAgIFtSRkMyMTE5
XSAgQnJhZG5lciwgUy4sICJLZXkgd29yZHMgZm9yIHVzZSBpbiBSRkNzIHRvIEluZGljYXRlDQog
ICAgICAgICAgICAgIFJlcXVpcmVtZW50IExldmVscyIsIEJDUCAxNCwgUkZDIDIxMTksIE1hcmNo
IDE5OTcuDQoNCiAgIFtSRkMzOTg1XSAgQnJ5YW50LCBTLiBhbmQgUC4gUGF0ZSwgIlBzZXVkbyBX
aXJlIEVtdWxhdGlvbiBFZGdlLXRvLQ0KICAgICAgICAgICAgICBFZGdlIChQV0UzKSBBcmNoaXRl
Y3R1cmUiLCBSRkMgMzk4NSwgTWFyY2ggMjAwNS4NCg0KICAgW1JGQzQzODldICBUaGFsZXIsIEQu
LCBUYWx3YXIsIE0uLCBhbmQgQy4gUGF0ZWwsICJOZWlnaGJvciBEaXNjb3ZlcnkNCiAgICAgICAg
ICAgICAgUHJveGllcyAoTkQgUHJveHkpIiwgUkZDIDQzODksIEFwcmlsIDIwMDYuDQoNCiAgIFtS
RkM0NDQ3XSAgTWFydGluaSwgTC4sIFJvc2VuLCBFLiwgRWwtQWF3YXIsIE4uLCBTbWl0aCwgVC4s
IGFuZCBHLg0KICAgICAgICAgICAgICBIZXJvbiwgIlBzZXVkb3dpcmUgU2V0dXAgYW5kIE1haW50
ZW5hbmNlIFVzaW5nIHRoZSBMYWJlbA0KICAgICAgICAgICAgICBEaXN0cmlidXRpb24gUHJvdG9j
b2wgKExEUCkiLCBSRkMgNDQ0NywgQXByaWwgMjAwNi4NCg0KICAgW1JGQzQ0NDhdICBNYXJ0aW5p
LCBMLiwgUm9zZW4sIEUuLCBFbC1BYXdhciwgTi4sIGFuZCBHLiBIZXJvbiwNCiAgICAgICAgICAg
ICAgIkVuY2Fwc3VsYXRpb24gTWV0aG9kcyBmb3IgVHJhbnNwb3J0IG9mIEV0aGVybmV0IG92ZXIg
TVBMUw0KICAgICAgICAgICAgICBOZXR3b3JrcyIsIFJGQyA0NDQ4LCBBcHJpbCAyMDA2Lg0KDQog
ICBbUkZDNDcyMF0gIE1hbGlzLCBBLiwgQWxsYW4sIEQuLCBhbmQgTi4gRGVsIFJlZ25vLCAiUHNl
dWRvd2lyZQ0KICAgICAgICAgICAgICBFbXVsYXRpb24gRWRnZS10by1FZGdlIChQV0UzKSBGcmFt
ZSBDaGVjayBTZXF1ZW5jZQ0KICAgICAgICAgICAgICBSZXRlbnRpb24iLCBSRkMgNDcyMCwgTm92
ZW1iZXIgMjAwNi4NCg0KICAgW1JGQzUwODVdICBOYWRlYXUsIFQuIGFuZCBDLiBQaWduYXRhcm8s
ICJQc2V1ZG93aXJlIFZpcnR1YWwgQ2lyY3VpdA0KICAgICAgICAgICAgICBDb25uZWN0aXZpdHkg
VmVyaWZpY2F0aW9uIChWQ0NWKTogQSBDb250cm9sIENoYW5uZWwgZm9yDQogICAgICAgICAgICAg
IFBzZXVkb3dpcmVzIiwgUkZDIDUwODUsIERlY2VtYmVyIDIwMDcuDQoNCiAgIFtSRkM1ODgwXSAg
S2F0eiwgRC4gYW5kIEQuIFdhcmQsICJCaWRpcmVjdGlvbmFsIEZvcndhcmRpbmcgRGV0ZWN0aW9u
DQogICAgICAgICAgICAgIChCRkQpIiwgUkZDIDU4ODAsIEp1bmUgMjAxMC4NCg0KICAgW1JGQzU4
ODRdICBBZ2dhcndhbCwgUi4sIEtvbXBlbGxhLCBLLiwgTmFkZWF1LCBULiwgYW5kIEcuIFN3YWxs
b3csDQogICAgICAgICAgICAgICJCaWRpcmVjdGlvbmFsIEZvcndhcmRpbmcgRGV0ZWN0aW9uIChC
RkQpIGZvciBNUExTIExhYmVsDQogICAgICAgICAgICAgIFN3aXRjaGVkIFBhdGhzIChMU1BzKSIs
IFJGQyA1ODg0LCBKdW5lIDIwMTAuDQoNCjI0LjIuICBJbmZvcm1hdGl2ZSBSZWZlcmVuY2VzDQoN
CiAgIFtJLUQuaWV0Zi1wd2UzLWZhdC1wd10NCiAgICAgICAgICAgICAgQnJ5YW50LCBTLiwgRmls
c2ZpbHMsIEMuLCBEcmFmeiwgVS4sIEtvbXBlbGxhLCBWLiwgUmVnYW4sDQogICAgICAgICAgICAg
IEouLCBhbmQgUy4gQW1hbnRlLCAiRmxvdyBBd2FyZSBUcmFuc3BvcnQgb2YgUHNldWRvd2lyZXMN
CiAgICAgICAgICAgICAgb3ZlciBhbiBNUExTIFBhY2tldCBTd2l0Y2hlZCBOZXR3b3JrIiwNCiAg
ICAgICAgICAgICAgZHJhZnQtaWV0Zi1wd2UzLWZhdC1wdy0wNyAod29yayBpbiBwcm9ncmVzcyks
IEp1bHkgMjAxMS4NCg0KDQoNCg0KRGF2YXJpLCBldCBhbC4gICAgICAgICAgIEV4cGlyZXMgQXVn
dXN0IDI3LCAyMDEzICAgICAgICAgICAgICAgW1BhZ2UgMzNdDQoMDQpJbnRlcm5ldC1EcmFmdCAg
ICAgICAgVHJhbnNwb3J0aW5nIFRpbWluZyBvdmVyIE1QTFMgICAgICAgIEZlYnJ1YXJ5IDIwMTMN
Cg0KDQogICBbSVNPXSAgICAgIElTTy9JRUMgMTA1ODk6MTk5MiwgIkludGVybWVkaWF0ZSBzeXN0
ZW0gdG8gSW50ZXJtZWRpYXRlDQogICAgICAgICAgICAgIHN5c3RlbSByb3V0ZWluZyBpbmZvcm1h
dGlvbiBleGNoYW5nZSBwcm90b2NvbCBmb3IgdXNlIGluDQogICAgICAgICAgICAgIGNvbmp1bmN0
aW9uIHdpdGggdGhlIFByb3RvY29sIGZvciBwcm92aWRpbmcgdGhlDQogICAgICAgICAgICAgIENv
bm5lY3Rpb25sZXNzLW1vZGUgTmV0d29yayBTZXJ2aWNlIChJU08gODQ3MykiLg0KDQogICBbUkZD
MTE5NV0gIENhbGxvbiwgUi4sICJVc2Ugb2YgT1NJIElTLUlTIGZvciByb3V0aW5nIGluIFRDUC9J
UCBhbmQNCiAgICAgICAgICAgICAgZHVhbCBlbnZpcm9ubWVudHMiLCBSRkMgMTE5NSwgRGVjZW1i
ZXIgMTk5MC4NCg0KICAgW1JGQzIzMjhdICBNb3ksIEouLCAiT1NQRiBWZXJzaW9uIDIiLCBTVEQg
NTQsIFJGQyAyMzI4LCBBcHJpbCAxOTk4Lg0KDQogICBbUkZDMjY5N10gIEhlaW5hbmVuLCBKLiBh
bmQgUi4gR3VlcmluLCAiQSBTaW5nbGUgUmF0ZSBUaHJlZSBDb2xvcg0KICAgICAgICAgICAgICBN
YXJrZXIiLCBSRkMgMjY5NywgU2VwdGVtYmVyIDE5OTkuDQoNCiAgIFtSRkMzMjQ2XSAgRGF2aWUs
IEIuLCBDaGFybnksIEEuLCBCZW5uZXQsIEouLCBCZW5zb24sIEsuLCBMZSBCb3VkZWMsDQogICAg
ICAgICAgICAgIEouLCBDb3VydG5leSwgVy4sIERhdmFyaSwgUy4sIEZpcm9pdSwgVi4sIGFuZCBE
Lg0KICAgICAgICAgICAgICBTdGlsaWFkaXMsICJBbiBFeHBlZGl0ZWQgRm9yd2FyZGluZyBQSEIg
KFBlci1Ib3ANCiAgICAgICAgICAgICAgQmVoYXZpb3IpIiwgUkZDIDMyNDYsIE1hcmNoIDIwMDIu
DQoNCiAgIFtSRkMzNjMwXSAgS2F0eiwgRC4sIEtvbXBlbGxhLCBLLiwgYW5kIEQuIFlldW5nLCAi
VHJhZmZpYyBFbmdpbmVlcmluZw0KICAgICAgICAgICAgICAoVEUpIEV4dGVuc2lvbnMgdG8gT1NQ
RiBWZXJzaW9uIDIiLCBSRkMgMzYzMCwNCiAgICAgICAgICAgICAgU2VwdGVtYmVyIDIwMDMuDQoN
CiAgIFtSRkMzNzg0XSAgU21pdCwgSC4gYW5kIFQuIExpLCAiSW50ZXJtZWRpYXRlIFN5c3RlbSB0
byBJbnRlcm1lZGlhdGUNCiAgICAgICAgICAgICAgU3lzdGVtIChJUy1JUykgRXh0ZW5zaW9ucyBm
b3IgVHJhZmZpYyBFbmdpbmVlcmluZyAoVEUpIiwNCiAgICAgICAgICAgICAgUkZDIDM3ODQsIEp1
bmUgMjAwNC4NCg0KICAgW1JGQzQ5NzBdICBMaW5kZW0sIEEuLCBTaGVuLCBOLiwgVmFzc2V1ciwg
SlAuLCBBZ2dhcndhbCwgUi4sIGFuZCBTLg0KICAgICAgICAgICAgICBTaGFmZmVyLCAiRXh0ZW5z
aW9ucyB0byBPU1BGIGZvciBBZHZlcnRpc2luZyBPcHRpb25hbA0KICAgICAgICAgICAgICBSb3V0
ZXIgQ2FwYWJpbGl0aWVzIiwgUkZDIDQ5NzAsIEp1bHkgMjAwNy4NCg0KICAgW1JGQzQ5NzFdICBW
YXNzZXVyLCBKUC4sIFNoZW4sIE4uLCBhbmQgUi4gQWdnYXJ3YWwsICJJbnRlcm1lZGlhdGUNCiAg
ICAgICAgICAgICAgU3lzdGVtIHRvIEludGVybWVkaWF0ZSBTeXN0ZW0gKElTLUlTKSBFeHRlbnNp
b25zIGZvcg0KICAgICAgICAgICAgICBBZHZlcnRpc2luZyBSb3V0ZXIgSW5mb3JtYXRpb24iLCBS
RkMgNDk3MSwgSnVseSAyMDA3Lg0KDQogICBbUkZDNTEyMF0gIFByenlnaWVuZGEsIFQuLCBTaGVu
LCBOLiwgYW5kIE4uIFNoZXRoLCAiTS1JU0lTOiBNdWx0aQ0KICAgICAgICAgICAgICBUb3BvbG9n
eSAoTVQpIFJvdXRpbmcgaW4gSW50ZXJtZWRpYXRlIFN5c3RlbSB0bw0KICAgICAgICAgICAgICBJ
bnRlcm1lZGlhdGUgU3lzdGVtcyAoSVMtSVNzKSIsIFJGQyA1MTIwLCBGZWJydWFyeSAyMDA4Lg0K
DQogICBbUkZDNTMwNV0gIExpLCBULiBhbmQgSC4gU21pdCwgIklTLUlTIEV4dGVuc2lvbnMgZm9y
IFRyYWZmaWMNCiAgICAgICAgICAgICAgRW5naW5lZXJpbmciLCBSRkMgNTMwNSwgT2N0b2JlciAy
MDA4Lg0KDQogICBbUkZDNTMyOV0gIElzaGlndXJvLCBLLiwgTWFucmFsLCBWLiwgRGF2ZXksIEEu
LCBhbmQgQS4gTGluZGVtLA0KICAgICAgICAgICAgICAiVHJhZmZpYyBFbmdpbmVlcmluZyBFeHRl
bnNpb25zIHRvIE9TUEYgVmVyc2lvbiAzIiwNCiAgICAgICAgICAgICAgUkZDIDUzMjksIFNlcHRl
bWJlciAyMDA4Lg0KDQogICBbUkZDNTM0MF0gIENvbHR1biwgUi4sIEZlcmd1c29uLCBELiwgTW95
LCBKLiwgYW5kIEEuIExpbmRlbSwgIk9TUEYNCiAgICAgICAgICAgICAgZm9yIElQdjYiLCBSRkMg
NTM0MCwgSnVseSAyMDA4Lg0KDQoNCg0KDQpEYXZhcmksIGV0IGFsLiAgICAgICAgICAgRXhwaXJl
cyBBdWd1c3QgMjcsIDIwMTMgICAgICAgICAgICAgICBbUGFnZSAzNF0NCgwNCkludGVybmV0LURy
YWZ0ICAgICAgICBUcmFuc3BvcnRpbmcgVGltaW5nIG92ZXIgTVBMUyAgICAgICAgRmVicnVhcnkg
MjAxMw0KDQoNCiAgIFtSRkM1OTA1XSAgTWlsbHMsIEQuLCBNYXJ0aW4sIEouLCBCdXJiYW5rLCBK
LiwgYW5kIFcuIEthc2NoLCAiTmV0d29yaw0KICAgICAgICAgICAgICBUaW1lIFByb3RvY29sIFZl
cnNpb24gNDogUHJvdG9jb2wgYW5kIEFsZ29yaXRobXMNCiAgICAgICAgICAgICAgU3BlY2lmaWNh
dGlvbiIsIFJGQyA1OTA1LCBKdW5lIDIwMTAuDQoNCiAgIFtSRkM2MzkxXSAgQnJ5YW50LCBTLiwg
Rmlsc2ZpbHMsIEMuLCBEcmFmeiwgVS4sIEtvbXBlbGxhLCBWLiwgUmVnYW4sDQogICAgICAgICAg
ICAgIEouLCBhbmQgUy4gQW1hbnRlLCAiRmxvdy1Bd2FyZSBUcmFuc3BvcnQgb2YgUHNldWRvd2ly
ZXMNCiAgICAgICAgICAgICAgb3ZlciBhbiBNUExTIFBhY2tldCBTd2l0Y2hlZCBOZXR3b3JrIiwg
UkZDIDYzOTEsDQogICAgICAgICAgICAgIE5vdmVtYmVyIDIwMTEuDQoNCg0KDQoNCg0KDQoNCg0K
DQoNCg0KDQoNCg0KDQoNCg0KDQoNCg0KDQoNCg0KDQoNCg0KDQoNCg0KDQoNCg0KDQoNCg0KDQoN
Cg0KDQoNCg0KDQoNCkRhdmFyaSwgZXQgYWwuICAgICAgICAgICBFeHBpcmVzIEF1Z3VzdCAyNywg
MjAxMyAgICAgICAgICAgICAgIFtQYWdlIDM1XQ0KDA0KSW50ZXJuZXQtRHJhZnQgICAgICAgIFRy
YW5zcG9ydGluZyBUaW1pbmcgb3ZlciBNUExTICAgICAgICBGZWJydWFyeSAyMDEzDQoNCg0KQXV0
aG9ycycgQWRkcmVzc2VzDQoNCiAgIFNoYWhyYW0gRGF2YXJpDQogICBCcm9hZGNvbSBDb3JwLg0K
ICAgU2FuIEpvc2UsIENBICA5NTEzNA0KICAgVVNBDQoNCiAgIEVtYWlsOiBkYXZhcmlAYnJvYWRj
b20uY29tDQoNCg0KICAgQW1pdCBPcmVuDQogICBCcm9hZGNvbSBDb3JwLg0KICAgU2FuIEpvc2Us
IENBICA5NTEzNA0KICAgVVNBDQoNCiAgIEVtYWlsOiBhbWl0b0Bicm9hZGNvbS5jb20NCg0KDQog
ICBNYW5hdiBCaGF0aWENCiAgIEFsY2F0ZWwtTHVjZW50DQogICBCYW5nYWxvcmUsDQogICBJbmRp
YQ0KDQogICBFbWFpbDogbWFuYXYuYmhhdGlhQGFsY2F0ZWwtbHVjZW50LmNvbQ0KDQoNCiAgIFBl
dGVyIFJvYmVydHMNCiAgIEFsY2F0ZWwtTHVjZW50DQogICBLYW5hdGEsDQogICBDYW5hZGENCg0K
ICAgRW1haWw6IHBldGVyLnJvYmVydHNAYWxjYXRlbC1sdWNlbnQuY29tDQoNCg0KICAgTGF1cmVu
dCBNb250aW5pDQogICBDaXNjbyBTeXN0ZW1zDQogICBTYW4gSm9zZSBDQQ0KICAgVVNBDQoNCiAg
IEVtYWlsOiBsbW9udGluaUBjaXNjby5jb20NCg0KDQoNCg0KDQoNCg0KDQoNCg0KDQpEYXZhcmks
IGV0IGFsLiAgICAgICAgICAgRXhwaXJlcyBBdWd1c3QgMjcsIDIwMTMgICAgICAgICAgICAgICBb
UGFnZSAzNl0NCgwNCg==

------_=_NextPart_001_01CE6216.959AB4A8
Content-Type: text/plain; name="draft-ietf-tictoc-1588overmpls-04-pm.txt"
Content-Transfer-Encoding: base64
Content-Description: draft-ietf-tictoc-1588overmpls-04-pm.txt
Content-Disposition: attachment;
	filename="draft-ietf-tictoc-1588overmpls-04-pm.txt"

DQoNCg0KVElDVE9DIFdvcmtpbmcgR3JvdXAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgUy4gRGF2YXJpDQpJbnRlcm5ldC1EcmFmdCAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgIEEuIE9yZW4NCkludGVuZGVkIHN0YXR1czog
U3RhbmRhcmRzIFRyYWNrICAgICAgICAgICAgICAgICAgICAgICAgICBCcm9hZGNvbSBDb3JwLg0K
RXhwaXJlczogQXVndXN0IDI3LCAyMDEzICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgTS4gQmhhdGlhDQogICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgIFAuIFJvYmVydHMNCiAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICBBbGNhdGVsLUx1Y2VudA0KICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICBM
LiBNb250aW5pDQogICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgIENpc2NvIFN5c3RlbXMNCiAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgICBGZWJydWFyeSAyMywgMjAxMw0KDQoNCiAgICAgICAg
ICAgIFRyYW5zcG9ydGluZyBUaW1pbmcgbWVzc2FnZXMgb3ZlciBNUExTIE5ldHdvcmtzDQogICAg
ICAgICAgICAgICAgICAgZHJhZnQtaWV0Zi10aWN0b2MtMTU4OG92ZXJtcGxzLTA0DQoNCkFic3Ry
YWN0DQoNCiAgIFRoaXMgZG9jdW1lbnQgZGVmaW5lcyB0aGUgbWV0aG9kIGZvciB0cmFuc3BvcnRp
bmcgVGltaW5nIG1lc3NhZ2VzDQogICBzdWNoIGFzIFBUUCBhbmQgTlRQIG92ZXIgYW4gTVBMUyBu
ZXR3b3JrLiAgVGhlIG1ldGhvZCBhbGxvd3MgZm9yIHRoZQ0KICAgZWFzeSBpZGVudGlmaWNhdGlv
biBvZiB0aGVzZSBQRFVzIGF0IHRoZSBwb3J0IGxldmVsIHRvIGFsbG93IGZvciBwb3J0DQogICBs
ZXZlbCBwcm9jZXNzaW5nIG9mIHRoZXNlIFBEVXMgaW4gYm90aCBMRVJzIGFuZCBMU1JzLg0KDQog
ICBUaGUgYmFzaWMgaWRlYSBpcyB0byB0cmFuc3BvcnQgVGltaW5nIG1lc3NhZ2VzIGluc2lkZSBk
ZWRpY2F0ZWQgTVBMUw0KICAgTFNQcy4gIFRoZXNlIExTUHMgb25seSBjYXJyeSB0aW1pbmcgbWVz
c2FnZXMgYW5kIHBvc3NpYmx5IENvbnRyb2wgYW5kDQogICBNYW5hZ2VtZW50IHBhY2tldHMsIGJ1
dCB0aGV5IGRvIG5vdCBjYXJyeSBjdXN0b21lciB0cmFmZmljLg0KDQogICBUd28gbWV0aG9kcyBm
b3IgdHJhbnNwb3J0aW5nIFRpbWluZyBtZXNzYWdlcyBvdmVyIE1QTFMgYXJlIGRlZmluZWQuDQog
ICBUaGUgZmlyc3QgbWV0aG9kIGlzIHRvIHRyYW5zcG9ydCBUaW1pbmcgbWVzc2FnZXMgZGlyZWN0
bHkgb3ZlciB0aGUNCiAgIGRlZGljYXRlZCBNUExTIExTUCB2aWEgVURQL0lQIGVuY2Fwc3VsYXRp
b24sIHdoaWNoIGlzIHN1aXRhYmxlIGZvcg0KICAgTVBMUyBuZXR3b3Jrcy4gIFRoZSBzZWNvbmQg
bWV0aG9kIGlzIHRvIHRyYW5zcG9ydCBUaW1pbmcgbWVzc2FnZXMNCiAgIGluc2lkZSBhIFBXIHZp
YSBFdGhlcm5ldCBlbmNhcHN1bGF0aW9uLCB3aGljaCBpcyBzdWl0YWJsZSBmb3IgYm90aA0KICAg
TVBMUyBhbmQgTVBMUy1UUCBuZXR3b3Jrcy4NCg0KU3RhdHVzIG9mIHRoaXMgTWVtbw0KDQogICBU
aGlzIEludGVybmV0LURyYWZ0IGlzIHN1Ym1pdHRlZCBpbiBmdWxsIGNvbmZvcm1hbmNlIHdpdGgg
dGhlDQogICBwcm92aXNpb25zIG9mIEJDUCA3OCBhbmQgQkNQIDc5Lg0KDQogICBJbnRlcm5ldC1E
cmFmdHMgYXJlIHdvcmtpbmcgZG9jdW1lbnRzIG9mIHRoZSBJbnRlcm5ldCBFbmdpbmVlcmluZw0K
ICAgVGFzayBGb3JjZSAoSUVURikuICBOb3RlIHRoYXQgb3RoZXIgZ3JvdXBzIG1heSBhbHNvIGRp
c3RyaWJ1dGUNCiAgIHdvcmtpbmcgZG9jdW1lbnRzIGFzIEludGVybmV0LURyYWZ0cy4gIFRoZSBs
aXN0IG9mIGN1cnJlbnQgSW50ZXJuZXQtDQogICBEcmFmdHMgaXMgYXQgaHR0cDovL2RhdGF0cmFj
a2VyLmlldGYub3JnL2RyYWZ0cy9jdXJyZW50Ly4NCg0KICAgSW50ZXJuZXQtRHJhZnRzIGFyZSBk
cmFmdCBkb2N1bWVudHMgdmFsaWQgZm9yIGEgbWF4aW11bSBvZiBzaXggbW9udGhzDQogICBhbmQg
bWF5IGJlIHVwZGF0ZWQsIHJlcGxhY2VkLCBvciBvYnNvbGV0ZWQgYnkgb3RoZXIgZG9jdW1lbnRz
IGF0IGFueQ0KICAgdGltZS4gIEl0IGlzIGluYXBwcm9wcmlhdGUgdG8gdXNlIEludGVybmV0LURy
YWZ0cyBhcyByZWZlcmVuY2UNCiAgIG1hdGVyaWFsIG9yIHRvIGNpdGUgdGhlbSBvdGhlciB0aGFu
IGFzICJ3b3JrIGluIHByb2dyZXNzLiINCg0KICAgVGhpcyBJbnRlcm5ldC1EcmFmdCB3aWxsIGV4
cGlyZSBvbiBBdWd1c3QgMjcsIDIwMTMuDQoNCg0KDQpEYXZhcmksIGV0IGFsLiAgICAgICAgICAg
RXhwaXJlcyBBdWd1c3QgMjcsIDIwMTMgICAgICAgICAgICAgICAgW1BhZ2UgMV0NCgwNCkludGVy
bmV0LURyYWZ0ICAgICAgICBUcmFuc3BvcnRpbmcgVGltaW5nIG92ZXIgTVBMUyAgICAgICAgRmVi
cnVhcnkgMjAxMw0KDQoNCkNvcHlyaWdodCBOb3RpY2UNCg0KICAgQ29weXJpZ2h0IChjKSAyMDEz
IElFVEYgVHJ1c3QgYW5kIHRoZSBwZXJzb25zIGlkZW50aWZpZWQgYXMgdGhlDQogICBkb2N1bWVu
dCBhdXRob3JzLiAgQWxsIHJpZ2h0cyByZXNlcnZlZC4NCg0KICAgVGhpcyBkb2N1bWVudCBpcyBz
dWJqZWN0IHRvIEJDUCA3OCBhbmQgdGhlIElFVEYgVHJ1c3QncyBMZWdhbA0KICAgUHJvdmlzaW9u
cyBSZWxhdGluZyB0byBJRVRGIERvY3VtZW50cw0KICAgKGh0dHA6Ly90cnVzdGVlLmlldGYub3Jn
L2xpY2Vuc2UtaW5mbykgaW4gZWZmZWN0IG9uIHRoZSBkYXRlIG9mDQogICBwdWJsaWNhdGlvbiBv
ZiB0aGlzIGRvY3VtZW50LiAgUGxlYXNlIHJldmlldyB0aGVzZSBkb2N1bWVudHMNCiAgIGNhcmVm
dWxseSwgYXMgdGhleSBkZXNjcmliZSB5b3VyIHJpZ2h0cyBhbmQgcmVzdHJpY3Rpb25zIHdpdGgg
cmVzcGVjdA0KICAgdG8gdGhpcyBkb2N1bWVudC4gIENvZGUgQ29tcG9uZW50cyBleHRyYWN0ZWQg
ZnJvbSB0aGlzIGRvY3VtZW50IG11c3QNCiAgIGluY2x1ZGUgU2ltcGxpZmllZCBCU0QgTGljZW5z
ZSB0ZXh0IGFzIGRlc2NyaWJlZCBpbiBTZWN0aW9uIDQuZSBvZg0KICAgdGhlIFRydXN0IExlZ2Fs
IFByb3Zpc2lvbnMgYW5kIGFyZSBwcm92aWRlZCB3aXRob3V0IHdhcnJhbnR5IGFzDQogICBkZXNj
cmliZWQgaW4gdGhlIFNpbXBsaWZpZWQgQlNEIExpY2Vuc2UuDQoNCg0KDQoNCg0KDQoNCg0KDQoN
Cg0KDQoNCg0KDQoNCg0KDQoNCg0KDQoNCg0KDQoNCg0KDQoNCg0KDQoNCg0KDQoNCg0KDQoNCkRh
dmFyaSwgZXQgYWwuICAgICAgICAgICBFeHBpcmVzIEF1Z3VzdCAyNywgMjAxMyAgICAgICAgICAg
ICAgICBbUGFnZSAyXQ0KDA0KSW50ZXJuZXQtRHJhZnQgICAgICAgIFRyYW5zcG9ydGluZyBUaW1p
bmcgb3ZlciBNUExTICAgICAgICBGZWJydWFyeSAyMDEzDQoNCg0KVGFibGUgb2YgQ29udGVudHMN
Cg0KICAgMS4gIEludHJvZHVjdGlvbiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4g
LiAuIC4gLiAuIC4gLiAuICA2DQoNCiAgIDIuICBUZXJtaW5vbG9neSAgLiAuIC4gLiAuIC4gLiAu
IC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAgOA0KDQogICAzLiAgUHJvYmxlbSBT
dGF0ZW1lbnQgIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gIDkN
Cg0KICAgNC4gIFRpbWluZyBvdmVyIE1QTFMgQXJjaGl0ZWN0dXJlICAuIC4gLiAuIC4gLiAuIC4g
LiAuIC4gLiAuIC4gLiAuIDEwDQoNCiAgIDUuICBEZWRpY2F0ZWQgTFNQcyBmb3IgVGltaW5nIG1l
c3NhZ2VzIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAxMg0KDQogICA2LiAgVGltaW5nIG92
ZXIgTFNQIEVuY2Fwc3VsYXRpb24gIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gMTMN
CiAgICAgNi4xLiAgVGltaW5nIG92ZXIgVURQL0lQIG92ZXIgTVBMUyBFbmNhcHN1bGF0aW9uIC4g
LiAuIC4gLiAuIC4gLiAxMw0KICAgICA2LjIuICBUaW1pbmcgb3ZlciBQVyBFbmNhcHN1bGF0aW9u
IC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIDEzDQogICAgIDYuMy4gIE90aGVyIFRpbWlu
ZyBFbmNhcHN1bGF0aW9uIG1ldGhvZHMgLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gMTQNCg0KICAg
Ny4gIFRpbWluZyBtZXNzYWdlIFByb2Nlc3NpbmcgIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4g
LiAuIC4gLiAuIDE1DQoNCiAgIDguICBQcm90ZWN0aW9uIGFuZCBSZWR1bmRhbmN5ICAuIC4gLiAu
IC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAxNg0KDQogICA5LiAgRUNNUCAuIC4gLiAuIC4g
LiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gMTcNCg0KICAg
MTAuIFBIUCAgLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4g
LiAuIC4gLiAuIDE4DQoNCiAgIDExLiBFbnRyb3B5ICAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAu
IC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAxOQ0KDQogICAxMi4gT0FNLCBDb250cm9sIGFu
ZCBNYW5hZ2VtZW50ICAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gMjANCg0KICAg
MTMuIFFvUyBDb25zaWRlcmF0aW9ucyAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4g
LiAuIC4gLiAuIDIxDQoNCiAgIDE0LiBGQ1MgUmVjYWxjdWxhdGlvbiAgLiAuIC4gLiAuIC4gLiAu
IC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAyMg0KDQogICAxNS4gVURQIENoZWNrc3VtIENv
cnJlY3Rpb24gIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gMjMNCg0KICAg
MTYuIFJvdXRpbmcgZXh0ZW5zaW9ucyBmb3IgVGltaW5nLWF3YXJlIFJvdXRlcnMgIC4gLiAuIC4g
LiAuIC4gLiAuIDI0DQoNCiAgIDE3LiBTaWduYWxpbmcgRXh0ZW5zaW9ucyBmb3IgQ3JlYXRpbmcg
VGltaW5nIExTUHMgIC4gLiAuIC4gLiAuIC4gLiAyNQ0KDQogICAxOC4gQmVoYXZpb3Igb2YgTEVS
L0xTUiAgLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gMjYNCiAgICAg
MTguMS4gQmVoYXZpb3Igb2YgVGltaW5nLWNhcGFibGUvYXdhcmUgTEVSIC4gLiAuIC4gLiAuIC4g
LiAuIC4gLiAyNg0KICAgICAxOC4yLiBCZWhhdmlvciBvZiBUaW1pbmctY2FwYWJsZS9hd2FyZSBM
U1IgLiAuIC4gLiAuIC4gLiAuIC4gLiAuIDI2DQogICAgIDE4LjMuIEJlaGF2aW9yIG9mIG5vbi1U
aW1pbmctY2FwYWJsZS9hd2FyZSBMU1IgLiAuIC4gLiAuIC4gLiAuIC4gMjYNCg0KICAgMTkuIE90
aGVyIGNvbnNpZGVyYXRpb25zIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4g
LiAuIDI4DQoNCiAgIDIwLiBTZWN1cml0eSBDb25zaWRlcmF0aW9ucyAgLiAuIC4gLiAuIC4gLiAu
IC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAyOQ0KDQoNCg0KDQpEYXZhcmksIGV0IGFsLiAgICAgICAg
ICAgRXhwaXJlcyBBdWd1c3QgMjcsIDIwMTMgICAgICAgICAgICAgICAgW1BhZ2UgM10NCgwNCklu
dGVybmV0LURyYWZ0ICAgICAgICBUcmFuc3BvcnRpbmcgVGltaW5nIG92ZXIgTVBMUyAgICAgICAg
RmVicnVhcnkgMjAxMw0KDQoNCiAgIDIxLiBBcHBsaWNhYmlsaXR5IFN0YXRlbWVudCAgLiAuIC4g
LiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAzMA0KDQogICAyMi4gQWNrbm93bGVkZ2Vt
ZW50cyAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gMzENCg0K
ICAgMjMuIElBTkEgQ29uc2lkZXJhdGlvbnMgIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAu
IC4gLiAuIC4gLiAuIDMyDQoNCiAgIDI0LiBSZWZlcmVuY2VzIC4gLiAuIC4gLiAuIC4gLiAuIC4g
LiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAzMw0KICAgICAyNC4xLiBOb3JtYXRpdmUg
UmVmZXJlbmNlcyAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIDMzDQogICAg
IDI0LjIuIEluZm9ybWF0aXZlIFJlZmVyZW5jZXMgLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAu
IC4gLiAuIC4gMzMNCg0KICAgQXV0aG9ycycgQWRkcmVzc2VzIC4gLiAuIC4gLiAuIC4gLiAuIC4g
LiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIDM2DQoNCg0KDQoNCg0KDQoNCg0KDQoNCg0KDQoN
Cg0KDQoNCg0KDQoNCg0KDQoNCg0KDQoNCg0KDQoNCg0KDQoNCg0KDQoNCg0KDQoNCg0KDQoNCkRh
dmFyaSwgZXQgYWwuICAgICAgICAgICBFeHBpcmVzIEF1Z3VzdCAyNywgMjAxMyAgICAgICAgICAg
ICAgICBbUGFnZSA0XQ0KDA0KSW50ZXJuZXQtRHJhZnQgICAgICAgIFRyYW5zcG9ydGluZyBUaW1p
bmcgb3ZlciBNUExTICAgICAgICBGZWJydWFyeSAyMDEzDQoNCg0KICAgVGhlIGtleSB3b3JkcyAi
TVVTVCIsICJNVVNUIE5PVCIsICJSRVFVSVJFRCIsICJTSEFMTCIsICJTSEFMTCBOT1QiLA0KICAg
IlNIT1VMRCIsICJTSE9VTEQgTk9UIiwgIlJFQ09NTUVOREVEIiwgIk1BWSIsIGFuZCAiT1BUSU9O
QUwiIGluIHRoaXMNCiAgIGRvY3VtZW50IGFyZSB0byBiZSBpbnRlcnByZXRlZCBhcyBkZXNjcmli
ZWQgaW4gUkZDMjExOSBbUkZDMjExOV0uDQoNCiAgIFdoZW4gdXNlZCBpbiBsb3dlciBjYXNlLCB0
aGVzZSB3b3JkcyBjb252ZXkgdGhlaXIgdHlwaWNhbCB1c2UgaW4NCiAgIGNvbW1vbiBsYW5ndWFn
ZSwgYW5kIGFyZSBub3QgdG8gYmUgaW50ZXJwcmV0ZWQgYXMgZGVzY3JpYmVkIGluDQogICBSRkMy
MTE5IFtSRkMyMTE5XS4NCg0KDQoNCg0KDQoNCg0KDQoNCg0KDQoNCg0KDQoNCg0KDQoNCg0KDQoN
Cg0KDQoNCg0KDQoNCg0KDQoNCg0KDQoNCg0KDQoNCg0KDQoNCg0KDQoNCg0KDQpEYXZhcmksIGV0
IGFsLiAgICAgICAgICAgRXhwaXJlcyBBdWd1c3QgMjcsIDIwMTMgICAgICAgICAgICAgICAgW1Bh
Z2UgNV0NCgwNCkludGVybmV0LURyYWZ0ICAgICAgICBUcmFuc3BvcnRpbmcgVGltaW5nIG92ZXIg
TVBMUyAgICAgICAgRmVicnVhcnkgMjAxMw0KDQoNCjEuICBJbnRyb2R1Y3Rpb24NCg0KICAgVGhl
IG9iamVjdGl2ZSBvZiBQcmVjaXNpb24gVGltZSBQcm90b2NvbCAoUFRQKSBhbmQgTmV0d29yayBU
aW1pbmcNCiAgIFByb3RvY29sIChOVFApIGFyZSB0byBzeW5jaHJvbml6ZSBpbmRlcGVuZGVudCBj
bG9ja3MgcnVubmluZyBvbg0KICAgc2VwYXJhdGUgbm9kZXMgb2YgYSBkaXN0cmlidXRlZCBzeXN0
ZW0uDQoNCiAgIFtJRUVFXSBkZWZpbmVzIFBUUCBtZXNzYWdlcyBmb3IgZnJlcXVlbmN5LCBwaGFz
ZSBhbmQgdGltZQ0KICAgc3luY2hyb25pemF0aW9uLiAgVGhlIFBUUCBtZXNzYWdlcyBpbmNsdWRl
IFBUUCBQRFVzIG92ZXIgVURQL0lQDQogICAoQW5uZXggRCBhbmQgRSBvZiBbSUVFRV0pIGFuZCBQ
VFAgUERVcyBvdmVyIEV0aGVybmV0IChBbm5leCBGIG9mDQogICBbSUVFRS0gMTU4OF0pLiAgVGhp
cyBkb2N1bWVudCBkZWZpbmVzIG1hcHBpbmcgYW5kIHRyYW5zcG9ydCBvZiB0aGUNCiAgIFBUUCBt
ZXNzYWdlcyBkZWZpbmVkIGluIFtJRUVFXSBvdmVyIE1QTFMvTVBMUy1UUCBuZXR3b3Jrcy4gIFBU
UA0KICAgZGVmaW5lcyBzZXZlcmFsIGNsb2NrIHR5cGVzOiBvcmRpbmFyeSBjbG9ja3MsIGJvdW5k
YXJ5IGNsb2NrcywgZW5kLQ0KICAgdG8tZW5kIHRyYW5zcGFyZW50IGNsb2NrcywgYW5kIHBlZXIt
dG8tcGVlciB0cmFuc3BhcmVudCBjbG9ja3MuDQogICBUcmFuc3BhcmVudCBjbG9ja3MgcmVxdWly
ZSBpbnRlcm1lZGlhdGUgbm9kZXMgdG8gdXBkYXRlIGNvcnJlY3Rpb24NCiAgIGZpZWxkIGluc2lk
ZSBQVFAgbWVzc2FnZSB0aGF0IHJlZmxlY3RzIHRoZSB0cmFuc2l0IHRpbWUgaW4gdGhlIG5vZGUu
DQoNCiAgIFtSRkM1OTA1XSBkZWZpbmVzIE5UUCBtZXNzYWdlcyBmb3IgY2xvY2sgYW5kIHRpbWUg
c3luY2hyb25pemF0aW9uLg0KICAgVGhlIFBUUCBtZXNzYWdlcyAoUERVcykgYXJlIHRyYW5zcG9y
dGVkIG92ZXIgVURQL0lQLiAgVGhpcyBkb2N1bWVudA0KICAgZGVmaW5lcyBtYXBwaW5nIGFuZCB0
cmFuc3BvcnQgb2YgdGhlIE5UUCBtZXNzYWdlcyBkZWZpbmVkIGluDQogICBbUkZDNTkwNV0gb3Zl
ciBNUExTIG5ldHdvcmtzLg0KDQogICBPbmUga2V5IGF0dHJpYnV0ZSBvZiBhbGwgb2YgdGhlc2Ug
VGltaW5nIG1lc3NhZ2VzIGlzIHRoYXQgdGhlIFRpbWUNCiAgIHN0YW1wIHByb2Nlc3Npbmcgc2hv
dWxkIG9jY3VyIGFzIGNsb3NlIGFzIHBvc3NpYmxlIHRvIHRoZSBhY3R1YWwNCiAgIHRyYW5zbWlz
c2lvbiBhbmQgcmVjZXB0aW9uIGF0IHRoZSBwaHlzaWNhbCBwb3J0IGludGVyZmFjZS4gIFRoaXMN
CiAgIHRhcmdldHMgb3B0aW1hbCB0aW1lIGFuZC9vciBmcmVxdWVuY3kgcmVjb3ZlcnkgYnkgYXZv
aWRpbmcgdmFyaWFibGUNCiAgIGRlbGF5IGludHJvZHVjZWQgYnkgcXVldWVzIGludGVybmFsIHRv
IHRoZSBjbG9ja3MuDQoNCiAgIFRvIGZhY2lsaXRhdGUgdGhlIGZhc3QgYW5kIGVmZmljaWVudCBy
ZWNvZ25pdGlvbiBvZiBUaW1pbmcgbWVzc2FnZXMNCiAgIGF0IHRoZSBwb3J0IGxldmVsIHdoZW4g
dGhlIFRpbWluZyBtZXNzYWdlcyBhcmUgY2FycmllZCBvdmVyIE1QTFMNCiAgIExTUHMsIHRoaXMg
ZG9jdW1lbnQgZGVmaW5lcyB0aGUgc3BlY2lmaWMgZW5jYXBzdWxhdGlvbnMgdGhhdCBzaG91bGQN
CiAgIGJlIHVzZWQuICBJbiBhZGRpdGlvbiwgaXQgY2FuIGJlIGV4cGVjdGVkIHRoYXQgdGhlcmUg
d2lsbCBleGlzdCBMU1IvDQogICBMRVJzIHdoZXJlIG9ubHkgYSBzdWJzZXQgb2YgdGhlIHBoeXNp
Y2FsIHBvcnRzIHdpbGwgaGF2ZSB0aGUgcG9ydC0NCiAgIGJhc2VkIFRpbWluZyBtZXNzYWdlIHBy
b2Nlc3NpbmcgY2FwYWJpbGl0aWVzLiAgSW4gb3JkZXIgdG8gZW5zdXJlDQogICB0aGF0IHRoZSBM
U1BzIGNhcnJ5aW5nIFRpbWluZyBwYWNrZXRzIGFsd2F5cyBlbnRlciBhbmQgZXhpdCBwb3J0cw0K
ICAgd2l0aCB0aGlzIGNhcGFiaWxpdHksIHJvdXRpbmcgZXh0ZW5zaW9ucyBhcmUgZGVmaW5lZCB0
byBhZHZlcnRpc2UNCiAgIHRoaXMgY2FwYWJpbGl0eSBvbiBhIHBvcnQgYmFzaXMgYW5kIHRvIGFs
bG93IGZvciB0aGUgZXN0YWJsaXNobWVudCBvZg0KICAgTFNQcyB0aGF0IG9ubHkgdHJhbnNpdCBz
dWNoIHBvcnRzLiAgV2hpbGUgdGhpcyBwYXRoIGVzdGFibGlzaG1lbnQNCiAgIHJlc3RyaWN0aW9u
IG1heSBiZSBhcHBsaWVkIG9ubHkgYXQgdGhlIExFUiBJbmdyZXNzIGFuZC9vciBlZ3Jlc3MNCiAg
IHBvcnRzLCBpdCBiZWNvbWVzIG1vcmUgaW1wb3J0YW50IHdoZW4gdXNpbmcgdHJhbnNwYXJlbnQg
Y2xvY2sgY2FwYWJsZQ0KICAgTFNScyBpbiB0aGUgcGF0aC4NCg0KICAgUG9ydCBiYXNlZCBUaW1p
bmcgbWVzc2FnZSBwcm9jZXNzaW5nIGludm9sdmVzIFRpbWluZyBtZXNzYWdlDQogICByZWNvZ25p
dGlvbi4gIE9uY2UgdGhlIFRpbWluZyBtZXNzYWdlcyBhcmUgcmVjb2duaXplZCB0aGV5IGNhbiBi
ZQ0KICAgbW9kaWZpZWQgYmFzZWQgb24gdGhlIHJlY2VwdGlvbiBvciB0cmFuc21pc3Npb24gVGlt
ZS1zdGFtcC4NCg0KICAgVGhpcyBkb2N1bWVudCBwcm92aWRlcyB0d28gbWV0aG9kcyBmb3IgdHJh
bnNwb3J0aW5nIFRpbWluZyBtZXNzYWdlcw0KICAgb3ZlciBNUExTLiAgT25lIGlzIGFwcGxpY2Fi
bGUgdG8gTVBMUyBlbnZpcm9ubWVudCBhbmQgdGhlIG90aGVyIG9uZQ0KICAgaXMgYXBwbGljYWJs
ZSB0byBib3RoIE1QTFMgYW5kIE1QTFMtVFAgZW52aXJvbm1lbnQuDQoNCg0KDQpEYXZhcmksIGV0
IGFsLiAgICAgICAgICAgRXhwaXJlcyBBdWd1c3QgMjcsIDIwMTMgICAgICAgICAgICAgICAgW1Bh
Z2UgNl0NCgwNCkludGVybmV0LURyYWZ0ICAgICAgICBUcmFuc3BvcnRpbmcgVGltaW5nIG92ZXIg
TVBMUyAgICAgICAgRmVicnVhcnkgMjAxMw0KDQoNCiAgIFRoZSBzb2x1dGlvbiBpbnZvbHZlcyB0
cmFuc3BvcnRpbmcgVGltaW5nIG1lc3NhZ2VzIG92ZXIgZGVkaWNhdGVkDQogICBMU1BzIGNhbGxl
ZCBUaW1pbmcgTFNQcy4gIFRoZXNlIExTUHMgY2FycnkgVGltaW5nIG1lc3NhZ2VzIGFuZCBNQVkN
CiAgIGNhcnJ5IE1hbmFnZW1lbnQgYW5kIGNvbnRyb2wgbWVzc2FnZXMsIGJ1dCBub3QgZGF0YSBw
bGFuZSBjbGllbnQNCiAgIHRyYWZmaWMuICBUaW1pbmcgTFNQcyBjYW4gYmUgZXN0YWJsaXNoZWQg
c3RhdGljYWxseSBvciB2aWEgc2lnbmFsaW5nLg0KICAgRXh0ZW5zaW9ucyB0byBjb250cm9sIHBs
YW5lIChPU1BGLCBJU0lTLCBldGMuKSBpcyByZXF1aXJlZCB0byBlbmFibGUNCiAgIHJvdXRlcnMg
dG8gZGlzdHJpYnV0ZSB0aGVpciBUaW1pbmcgcHJvY2Vzc2luZyBjYXBhYmlsaXRpZXMgb3ZlciBN
UExTDQogICB0byBvdGhlciByb3V0ZXJzLiAgSG93ZXZlciBzdWNoIGV4dGVuc2lvbnMgYXJlIG91
dHNpZGUgdGhlIHNjb3BlIG9mDQogICB0aGlzIGRvY3VtZW50Lg0KDQogICBFeHRlbnNpb25zIHRv
IHNpZ25hbGluZyBwcm90b2NvbHMgKGUuZy4sIFJTVlAtVEUpIGFyZSByZXF1aXJlZCBmb3INCiAg
IGVzdGFibGlzaGluZyBQVFAgTFNQcy4gIEhvd2V2ZXIgc3VjaCBleHRlbnNpb25zIGFyZSBvdXRz
aWRlIHRoZSBzY29wZQ0KICAgb2YgdGhpcyBkb2N1bWVudC4NCg0KICAgV2hpbGUgdGhlIHRlY2hu
aXF1ZXMgaW5jbHVkZWQgaGVyZWluIGFsbG93IGZvciB0aGUgZXN0YWJsaXNobWVudCBvZg0KICAg
cGF0aHMgb3B0aW1pemVkIHRvIGluY2x1ZGUgVGltZS1zdGFtcGluZyBjYXBhYmxlIGxpbmtzLCB0
aGUNCiAgIHBlcmZvcm1hbmNlIG9mIHRoZSBTbGF2ZSBjbG9ja3MgaXMgb3V0c2lkZSB0aGUgc2Nv
cGUgb2YgdGhpcw0KICAgZG9jdW1lbnQuDQoNCiAgIEF0IHRoZSB0aW1lIG9mIHB1Ymxpc2hpbmcg
dGhpcyBzcGVjaWZpY2F0aW9uLCBUcmFuc3BhcmVudCBDbG9ja2luZw0KICAgKFRDKSBpcyBvbmx5
IGRlZmluZWQgZm9yIFBUUC4gIFRoZXJlZm9yZSBhdCB0aGlzIHRpbWUgYW55IHBhcnQgb2YNCiAg
IHRoaXMgc3BlY2lmaWNhdGlvbiB0aGF0IHRhbGtzIGFib3V0IFRyYW5zcGFyZW50IENsb2NraW5n
IGFwcGxpZXMgb25seQ0KICAgdG8gUFRQLg0KDQoNCg0KDQoNCg0KDQoNCg0KDQoNCg0KDQoNCg0K
DQoNCg0KDQoNCg0KDQoNCg0KDQoNCg0KDQoNCkRhdmFyaSwgZXQgYWwuICAgICAgICAgICBFeHBp
cmVzIEF1Z3VzdCAyNywgMjAxMyAgICAgICAgICAgICAgICBbUGFnZSA3XQ0KDA0KSW50ZXJuZXQt
RHJhZnQgICAgICAgIFRyYW5zcG9ydGluZyBUaW1pbmcgb3ZlciBNUExTICAgICAgICBGZWJydWFy
eSAyMDEzDQoNCg0KMi4gIFRlcm1pbm9sb2d5DQoNCiAgIDE1ODg6IFRoZSB0aW1pbmcgYW5kIHN5
bmNocm9uaXphdGlvbiBhcyBkZWZpbmVkIGJ5IElFRUUgMTU4OC4NCg0KICAgTlRQOiBUaGUgdGlt
aW5nIGFuZCBzeW5jaHJvbml6YXRpb24gcHJvdG9jb2wgZGVmaW5lZCBieSBJRVRGIFJGQy0xMzA1
DQogICBhbmQgUkZDLTU5MDUuDQoNCiAgIFBUUDogVGhlIHRpbWluZyBhbmQgc3luY2hyb25pemF0
aW9uIHByb3RvY29sIHVzZWQgYnkgMTU4OC4NCg0KICAgTWFzdGVyIENsb2NrOiBUaGUgc291cmNl
IG9mIDE1ODggdGltaW5nIHRvIGEgc2V0IG9mIHNsYXZlIGNsb2Nrcy4NCg0KICAgTWFzdGVyIFBv
cnQ6IEEgcG9ydCBvbiBhIG9yZGluYXJ5IG9yIGJvdW5kYXJ5IGNsb2NrIHRoYXQgaXMgaW4gTWFz
dGVyDQogICBzdGF0ZS4gIFRoaXMgaXMgdGhlIHNvdXJjZSBvZiB0aW1pbmcgdG93YXJkIHNsYXZl
IHBvcnRzLg0KDQogICBTbGF2ZSBDbG9jazogQSByZWNlaXZlciBvZiAxNTg4IHRpbWluZyBmcm9t
IGEgbWFzdGVyIGNsb2NrLg0KDQogICBTbGF2ZSBQb3J0OiBBIHBvcnQgb24gYSBib3VuZGFyeSBj
bG9jayBvciBvcmRpbmFyeSBjbG9jayB0aGF0IGlzDQogICByZWNlaXZpbmcgdGltaW5nIGZyb20g
YSBtYXN0ZXIgY2xvY2suDQoNCiAgIE9yZGluYXJ5IENsb2NrOiBBIGRldmljZSB3aXRoIGEgc2lu
Z2xlIFBUUCBwb3J0Lg0KDQogICBUcmFuc3BhcmVudCBDbG9jay4gIEEgZGV2aWNlIHRoYXQgbWVh
c3VyZXMgdGhlIHRpbWUgdGFrZW4gZm9yIGEgUFRQDQogICBldmVudCBtZXNzYWdlIHRvIHRyYW5z
aXQgdGhlIGRldmljZSBhbmQgdGhlbiB1cGRhdGVzIHRoZQ0KICAgY29ycmVjdGlvbkZpZWxkIG9m
IHRoZSBtZXNzYWdlIHdpdGggdGhpcyB0cmFuc2l0IHRpbWUuDQoNCiAgIEJvdW5kYXJ5IENsb2Nr
OiBBIGRldmljZSB3aXRoIG1vcmUgdGhhbiBvbmUgUFRQIHBvcnQuICBHZW5lcmFsbHkNCiAgIGJv
dW5kYXJ5IGNsb2NrcyB3aWxsIGhhdmUgb25lIHBvcnQgaW4gc2xhdmUgc3RhdGUgdG8gcmVjZWl2
ZSB0aW1pbmcNCiAgIGFuZCB0aGVuIG90aGVyIHBvcnRzIGluIG1hc3RlciBzdGF0ZSB0byByZS1k
aXN0cmlidXRlIHRoZSB0aW1pbmcuDQoNCiAgIFBUUCBMU1A6IEFuIExTUCBkZWRpY2F0ZWQgdG8g
Y2FycnkgUFRQIG1lc3NhZ2VzDQoNCiAgIFBUUCBQVzogQSBQVyB3aXRoaW4gYSBQVFAgTFNQIHRo
YXQgaXMgZGVkaWNhdGVkIHRvIGNhcnJ5IFBUUA0KICAgbWVzc2FnZXMuDQoNCiAgIENXOiBQc2V1
ZG93aXJlIENvbnRyb2wgV29yZA0KDQogICBMQUc6IExpbmsgQWdncmVnYXRpb24NCg0KICAgRUNN
UDogRXF1YWwgQ29zdCBNdWx0aXBhdGgNCg0KICAgQ0Y6IENvcnJlY3Rpb24gRmllbGQsIGEgZmll
bGQgaW5zaWRlIGNlcnRhaW4gUFRQIG1lc3NhZ2VzIChtZXNzYWdlDQogICB0eXBlIDAtMyl0aGF0
IGhvbGRzIHRoZSBhY2N1bXVsYXRpdmUgdHJhbnNpdCB0aW1lIGluc2lkZSBpbnRlcm1lZGlhdGUN
CiAgIHN3aXRjaGVzDQoNCiAgIFRpbWluZyBtZXNzYWdlczogVGltaW5nIFByb3RvY29sIG1lc3Nh
Z2VzIHRoYXQgYXJlIGV4Y2hhbmdlZCBiZXR3ZWVuDQogICByb3V0ZXJzIGluIG9yZGVyIHRvIGVz
dGFibGlzaCBhIHN5bmNocm9uaXplZCBjbG9jay4NCg0KDQoNCg0KDQpEYXZhcmksIGV0IGFsLiAg
ICAgICAgICAgRXhwaXJlcyBBdWd1c3QgMjcsIDIwMTMgICAgICAgICAgICAgICAgW1BhZ2UgOF0N
CgwNCkludGVybmV0LURyYWZ0ICAgICAgICBUcmFuc3BvcnRpbmcgVGltaW5nIG92ZXIgTVBMUyAg
ICAgICAgRmVicnVhcnkgMjAxMw0KDQoNCjMuICBQcm9ibGVtIFN0YXRlbWVudA0KDQogICBbSUVF
RV0gaGFzIGRlZmluZWQgbWV0aG9kcyBmb3IgdHJhbnNwb3J0aW5nIFBUUCBtZXNzYWdlcyBvdmVy
DQogICBFdGhlcm5ldCBhbmQgSVAgbmV0d29ya3MuICBbUkZDNTkwNV0gaGFzIGRlZmluZWQgdGhl
IG1ldGhvZCBvZg0KICAgdHJhbnNwb3J0aW5nIE5UUCBtZXNzYWdlcyBvdmVyIElQIG5ldHdvcmtz
LiAgVGhlcmUgaXMgYSBuZWVkIHRvDQogICB0cmFuc3BvcnQgVGltaW5nIG1lc3NhZ2VzIG92ZXIg
TVBMUyBuZXR3b3JrcyB3aGlsZSBzdXBwb3J0aW5nIHRoZQ0KICAgVHJhbnNwYXJlbnQgQ2xvY2sg
KFRDKSwgQm91bmRhcnkgQ2xvY2sgKEJDKSBhbmQgT3JkaW5hcnkgQ2xvY2sgKE9DKQ0KICAgZnVu
Y3Rpb25hbGl0eSBpbiB0aGUgTEVSIGFuZCBMU1JzIGluIHRoZSBNUExTIG5ldHdvcmsuDQoNCiAg
IFRoZXJlIGFyZSBtdWx0aXBsZSB3YXlzIG9mIHRyYW5zcG9ydGluZyBUaW1pbmcgb3ZlciBNUExT
LiAgSG93ZXZlciwNCiAgIHRoZXJlIGlzIGEgcmVxdWlyZW1lbnQgdG8gbGltaXQgdGhlIHBvc3Np
YmxlIGVuY2Fwc3VsYXRpb24gb3B0aW9ucyB0bw0KICAgc2ltcGxpZnkgdGhlIFRpbWluZyBtZXNz
YWdlIGlkZW50aWZpY2F0aW9uIGFuZCBwcm9jZXNzaW5nIHJlcXVpcmVkIGF0DQogICB0aGUgcG9y
dCBsZXZlbC4NCg0KICAgV2hlbiBUaW1pbmctYXdhcmVuZXNzIGlzIG5lZWRlZCwgVGltaW5nIG1l
c3NhZ2VzIHNob3VsZCBub3QgYmUNCiAgIHRyYW5zcG9ydGVkIG92ZXIgTFNQcyBvciBQV3MgdGhh
dCBhcmUgY2FycnlpbmcgY3VzdG9tZXIgdHJhZmZpYw0KICAgYmVjYXVzZSBMU1JzIHBlcmZvcm0g
TGFiZWwgc3dpdGNoaW5nIGJhc2VkIG9uIHRoZSB0b3AgbGFiZWwgaW4gdGhlDQogICBzdGFjay4g
IFRvIGRldGVjdCBUaW1pbmcgbWVzc2FnZXMgaW5zaWRlIHN1Y2ggTFNQcyByZXF1aXJlIHNwZWNp
YWwNCiAgIGhhcmR3YXJlIHRvIGRvIGRlZXAgcGFja2V0IGluc3BlY3Rpb24gYXQgbGluZSByYXRl
LiAgRXZlbiBpZiBzdWNoDQogICBoYXJkd2FyZSBleGlzdHMsIHRoZSBwYXlsb2FkIGNhbnQgYmUg
ZGV0ZXJtaW5pc3RpY2FsbHkgaWRlbnRpZmllZCBieQ0KICAgTFNScyBiZWNhdXNlIHRoZSBwYXls
b2FkIHR5cGUgaXMgYSBjb250ZXh0IG9mIHRoZSBQVyBsYWJlbCwgYW5kIHRoZQ0KICAgUFcgbGFi
ZWwgYW5kIGl0cyBjb250ZXh0IGFyZSBvbmx5IGtub3duIHRvIHRoZSBFZGdlIHJvdXRlcnMgKFBF
cy8NCiAgIExFUnMpOyBMU1JzIGRvbnQga25vdyB3aGF0IGlzIGEgUFdzIHBheWxvYWQgKEV0aGVy
bmV0LCBBVE0sIEZSLCBDRVMsDQogICBldGMpLiAgRXZlbiBpZiBvbmUgcmVzdHJpY3RzIGFuIExT
UCB0byBvbmx5IGNhcnJ5IEV0aGVybmV0IFBXcywgdGhlDQogICBMU1JzIGRvbnQgaGF2ZSB0aGUg
a25vd2xlZGdlIG9mIHdoZXRoZXIgUFcgQ29udHJvbCBXb3JkIChDVykgaXMNCiAgIHByZXNlbnQg
b3Igbm90IGFuZCB0aGVyZWZvcmUgY2FuIG5vdCBkZXRlcm1pbmlzdGljYWxseSBpZGVudGlmeSB0
aGUNCiAgIHBheWxvYWQuDQoNCiAgIEEgZ2VuZXJpYyBtZXRob2QgaXMgZGVmaW5lZCBpbiB0aGlz
IGRvY3VtZW50IHRoYXQgZG9lcyBub3QgcmVxdWlyZQ0KICAgZGVlcCBwYWNrZXQgaW5zcGVjdGlv
biBhdCBsaW5lIHJhdGUsIGFuZCBjYW4gZGV0ZXJtaW5pc3RpY2FsbHkNCiAgIGlkZW50aWZ5IFRp
bWluZyBtZXNzYWdlcywgZm9yIG9uZS1zdGVwIG1vZGUgb2Ygb3BlcmF0aW9uLiAgVGhlIA0KICAg
Z2VuZXJpYyBtZXRob2QgaXMgYXBwbGljYWJsZSB0byBNUExTIGFuZCBNUExTLVRQIG5ldHdvcmtz
Lg0KDQoNCg0KDQoNCg0KDQoNCg0KDQoNCg0KDQoNCg0KDQoNCg0KDQpEYXZhcmksIGV0IGFsLiAg
ICAgICAgICAgRXhwaXJlcyBBdWd1c3QgMjcsIDIwMTMgICAgICAgICAgICAgICAgW1BhZ2UgOV0N
CgwNCkludGVybmV0LURyYWZ0ICAgICAgICBUcmFuc3BvcnRpbmcgVGltaW5nIG92ZXIgTVBMUyAg
ICAgICAgRmVicnVhcnkgMjAxMw0KDQoNCjQuICBUaW1pbmcgb3ZlciBNUExTIEFyY2hpdGVjdHVy
ZQ0KDQogICBUaW1pbmcgbWVzc2FnZXMgYXJlIGV4Y2hhbmdlIGJldHdlZW4gVGltaW5nIHBvcnRz
IG9uIG9yZGluYXJ5IGFuZA0KICAgYm91bmRhcnkgY2xvY2tzLiAgQm91bmRhcnkgY2xvY2tzIHRl
cm1pbmF0ZSB0aGUgVGltaW5nIG1lc3NhZ2VzIGFuZA0KICAgYWN0IGFzIG1hc3RlciBmb3Igb3Ro
ZXIgYm91bmRhcnkgY2xvY2tzIG9yIGZvciBzbGF2ZSBjbG9ja3MuICBFbmQtdG8tDQogICBFbmQg
VHJhbnNwYXJlbnQgY2xvY2tzIGRvIG5vdCB0ZXJtaW5hdGUgdGhlIFRpbWluZyBtZXNzYWdlcyBi
dXQgdGhleQ0KICAgZG8gbW9kaWZ5IHRoZSBjb250ZW50cyBvZiB0aGUgVGltaW5nIG1lc3NhZ2Vz
IGFzIHRoZXkgdHJhbnNpdCBhY3Jvc3MNCiAgIHRoZSB0cmFuc3BhcmVudCBjbG9jay4NCg0KICAg
TWFzdGVyL1NsYXZlIGNsb2NrcyAoT0NzKSwgQm91bmRhcnkgQ2xvY2tzIChCQykgYW5kIFRyYW5z
cGFyZW50IENsb2NrDQogICAoVEMpIGNvdWxkIGJlIGltcGxlbWVudGVkIGluIGVpdGhlciBMRVJz
IG9yIExTUnMuDQogICANCiAgIEFuIGV4YW1wbGUgaXMgc2hvd24gaW4gRmlndXJlIDEsIHdoZXJl
IHRoZSBMRVJzIGFjdCBhcyBPcmRpbmFyeSBDbG9jaw0KICAgKE9DKSBhbmQgYXJlIHRoZSBpbml0
aWF0aW5nL3Rlcm1pbmF0aW5nIHBvaW50IGZvciBUaW1pbmcgbWVzc2FnZXMuDQogICBUaGUgaW5n
cmVzcyBMRVIgZW5jYXBzdWxhdGVzIHRoZSBUaW1pbmcgbWVzc2FnZXMgaW4gVGltaW5nIExTUCBh
bmQgdGhlDQogICBFZ3Jlc3MgTEVSIHRlcm1pbmF0ZXMgdGhlIFRpbWluZyBMU1AuICANCg0KDQog
ICAgICArLS0tLS0tLS0rICAgICArLS0tLS0tLSsgICAgICstLS0tLS0tKyAgICAgKy0tLS0tLS0r
ICAgICArLS0tLS0tLS0rDQogICAgICB8U3dpdGNoLCB8ICAgICB8ICAgICAgIHwgICAgIHwgICAg
ICAgfCAgICAgfCAgICAgICB8ICAgICB8U3dpdGNoLCB8DQogICAgICB8IFJvdXRlciB8LS0tLS18
ICBMRVIgIHwtLS0tLXwgIExTUiAgfC0tLS0tfCAgTEVSICB8LS0tLS18IFJvdXRlciB8DQogICAg
ICB8ICAgICAgICB8ICAgICB8ICBPQyAgIHwgICAgIHwgIFRDICAgfCAgICAgfCAgT0MgICB8ICAg
ICB8ICAgICAgICB8DQogICAgICArLS0tLS0tLS0rICAgICArLS0tLS0tLSsgICAgICstLS0tLS0t
KyAgICAgKy0tLS0tLS0rICAgICArLS0tLS0tLS0rDQogICAgICAgICAgICAgICAgICAgICAvICAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgXA0KICAgICAgKy0tLS0tLS0rICAgICAvICAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICBcICAgICArLS0tLS0tLSsNCiAgICAgIHwg
IExFUiAgfCAgICAvICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgIFwgICAgfCAg
TEVSICB8DQogICAgICB8IE1hc3RlcnwtLS0vICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgXC0tLXwgU2xhdmUgfA0KICAgICAgfCBDbG9jayB8ICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgICB8IENsb2NrIHwNCiAgICAgICstLS0tLS0tKyAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgKy0tLS0tLS0rDQoN
CiAgICAgRmlndXJlICgxKSAtIERlcGxveW1lbnQgZXhhbXBsZSAxIG9mIHRpbWluZyBvdmVyIE1Q
TFMvTVBMUy1UUCBuZXR3b3JrDQoNCiAgIEFub3RoZXIgZXhhbXBsZSBpcyBzaG93biBpbiBGaWd1
cmUgMiwgd2hlcmUgTEVScyB0ZXJtaW5hdGUgdGhlIFRpbWluZw0KICAgbWVzc2FnZXMgcmVjZWl2
ZWQgZnJvbSBzd2l0Y2gvcm91dGVycyB0aGF0IGFyZSBvdXRzaWRlIG9mIHRoZSBNUExTIA0KICAg
bmV0d29yayBhY3RpbmcgYXMgT0Mgb3IgQkMuICBJbiB0aGlzIGV4YW1wbGUgTEVScyByZWdlbmVy
YXRlIHRoZSBjbG9jaw0KICAgYW5kIGluaXRpYXRlIHRpbWluZyBtZXNzYWdlcyBlbmNhcHN1bGF0
ZWQgaW4gVGltaW5nIExTUCB0b3dhcmQgdGhlIE1QTFMNCiAgIG5ldHdvcmssIHdoaWxlIHRoZSBM
U1JzIGFjdCBhcyBUcmFuc3BhcmVudCBDbG9jayAoVEMpIGFuZCBqdXN0IHVwZGF0ZQ0KICAgdGhl
IFRpbWluZyBmaWVsZCBpbiB0aGUgVGltaW5nIG1lc3NhZ2VzLCB3aGljaCBhcmUgYWxyZWFkeSBl
bmNhcHN1bGF0ZWQNCiAgIGluIFRpbWluZyBMU1BzLg0KDQogICAgICstLS0tLS0tLSsgICAgICst
LS0tLS0tKyAgICAgKy0tLS0tLS0rICAgICArLS0tLS0tLSsgICAgICstLS0tLS0tLSsNCiAgICAg
fFN3aXRjaCwgfCAgICAgfCAgICAgICB8ICAgICB8ICAgICAgIHwgICAgIHwgICAgICAgfCAgICAg
fFN3aXRjaCwgfA0KICAgICB8IFJvdXRlciB8LS0tLS18ICBMRVIgIHwtLS0tLXwgIExTUiAgfC0t
LS0tfCAgTEVSICB8LS0tLS18IFJvdXRlciB8DQogICAgIHwgT0MvQkMgIHwgICAgIHwgIEJDICAg
fCAgICAgfCAgVEMgICB8ICAgICB8ICBCQyAgIHwgICAgIHwgT0MvQkMgIHwNCiAgICAgKy0tLS0t
LS0tKyAgICAgKy0tLS0tLS0rICAgICArLS0tLS0tLSsgICAgICstLS0tLS0tKyAgICAgKy0tLS0t
LS0tKw0KDQogICAgIEZpZ3VyZSAoMikgLSBEZXBsb3ltZW50IGV4YW1wbGUgMiBvZiB0aW1pbmcg
b3ZlciBNUExTL01QTFMtVFAgbmV0d29yaw0KDQoNCg0KDQoNCkRhdmFyaSwgZXQgYWwuICAgICAg
ICAgICBFeHBpcmVzIEF1Z3VzdCAyNywgMjAxMyAgICAgICAgICAgICAgIFtQYWdlIDEwXQ0KDA0K
SW50ZXJuZXQtRHJhZnQgICAgICAgIFRyYW5zcG9ydGluZyBUaW1pbmcgb3ZlciBNUExTICAgICAg
ICBGZWJydWFyeSAyMDEzDQoNCg0KICAgQW5vdGhlciBleGFtcGxlIGlzIHNob3duIGluIEZpZ3Vy
ZSAzLCB3aGVyZSBMRVJzIGRvIG5vdCB0ZXJtaW5hdGUNCiAgIHRoZSBUaW1pbmcgbWVzc2FnZXMg
cmVjZWl2ZWQgZnJvbSBzd2l0Y2gvcm91dGVycyB0aGF0IGFyZSBvdXRzaWRlIG9mDQogICB0aGUg
TVBMUyBuZXR3b3JrIGFjdGluZyBhcyBPQywgVEMgb3IgQkMuICBUaGUgTEVScyBhY3QgYXMgVEMg
YW5kIHVwZGF0ZQ0KICAgdGhlIFRpbWluZyBmaWVsZCBpbiB0aGUgVGltaW5nIG1lc3NhZ2VzIGFz
IHRoZXkgdHJhbnNpdCB0aGUgTEVSLCB3aGlsZQ0KICAgZW5jYXBzdWxhdGluZyB0aGVtIGluIHRp
bWluZyBMU1AuICBUaGUgTFNScyBhbHNvIGFjdCBhcyBUcmFuc3BhcmVudCANCiAgIENsb2NrIChU
QykgYW5kIGp1c3QgdXBkYXRlIHRoZSBUaW1pbmcgZmllbGQgaW4gdGhlIFRpbWluZyBtZXNzYWdl
cw0KICAgd2hpY2ggYXJlIGFscmVhZHkgZW5jYXBzdWxhdGVkIGluIFRpbWluZyBMU1BzLg0KDQog
ICAgICArLS0tLS0tLS0rICAgICArLS0tLS0tLSsgICAgICstLS0tLS0tKyAgICAgKy0tLS0tLS0r
ICAgICArLS0tLS0tLS0rDQogICAgICB8U3dpdGNoLCB8ICAgICB8ICAgICAgIHwgICAgIHwgICAg
ICAgfCAgICAgfCAgICAgICB8ICAgICB8U3dpdGNoLCB8DQogICAgICB8IFJvdXRlciB8LS0tLS18
ICBMRVIgIHwtLS0tLXwgIExTUiAgfC0tLS0tfCAgTEVSICB8LS0tLS18IFJvdXRlciB8DQogICAg
ICB8T0MvVEMvQkN8ICAgICB8ICBUQyAgIHwgICAgIHwgIFRDICAgfCAgICAgfCAgVEMgICB8ICAg
ICB8T0MvVEMvQkN8DQogICAgICArLS0tLS0tLS0rICAgICArLS0tLS0tLSsgICAgICstLS0tLS0t
KyAgICAgKy0tLS0tLS0rICAgICArLS0tLS0tLS0rDQoNCiAgICBGaWd1cmUgKDMpIC0gRGVwbG95
bWVudCBleGFtcGxlIDMgb2YgdGltaW5nIG92ZXIgTVBMUy9NUExTLVRQIG5ldHdvcmsNCg0KDQoN
CiAgIEFub3RoZXIgZXhhbXBsZSBpcyBzaG93biBpbiBGaWd1cmUgNCwgd2hlcmUgTEVScyBhbmQg
TFNScyBzdXBwb3J0DQogICBCb3VuZGFyeSBDbG9ja3MuICBBIHNpbmdsZS1ob3AgTFNQIGlzIGNy
ZWF0ZWQgYmV0d2VlbiB0d28gYWRqYWNlbnQNCiAgIExTUnMgZW5nYWdlZCBpbiBCQyBvcGVyYXRp
b24sICBPdGhlciBtZXRob2RzIHN1Y2ggYXMgUFRQIHRyYW5zcG9ydCBvdmVyDQogICBFdGhlcm5l
dCBNQVkgYmUgdXNlZCBmb3IgdHJhbnNwb3J0aW5nIHRpbWluZyBtZXNzYWdlcyBpZiB0aGUgbGlu
ayANCiAgIGJldHdlZW4gdGhlIHR3byByb3V0ZXJzIGlzIEV0aGVybmV0Lg0KDQogICAgICstLS0t
LS0tLSsgICAgICstLS0tLS0tKyAgICAgKy0tLS0tLS0rICAgICArLS0tLS0tLSsgICAgICstLS0t
LS0tLSsNCiAgICAgfFN3aXRjaCwgfCAgICAgfCAgICAgICB8ICAgICB8ICAgICAgIHwgICAgIHwg
ICAgICAgfCAgICAgfFN3aXRjaCwgfA0KICAgICB8IFJvdXRlciB8LS0tLS18ICBMRVIgIHwtLS0t
LXwgIExTUiAgfC0tLS0tfCAgTEVSICB8LS0tLS18IFJvdXRlciB8DQogICAgIHwgT0MvQkMgIHwg
ICAgIHwgIEJDICAgfCAgICAgfCAgQkMgICB8ICAgICB8ICBCQyAgIHwgICAgIHwgT0MvQkMgIHwN
CiAgICAgKy0tLS0tLS0tKyAgICAgKy0tLS0tLS0rICAgICArLS0tLS0tLSsgICAgICstLS0tLS0t
KyAgICAgKy0tLS0tLS0tKw0KDQogICAgIEZpZ3VyZSAoNCkgLSBEZXBsb3ltZW50IGV4YW1wbGUg
MyBvZiB0aW1pbmcgb3ZlciBNUExTL01QTFMtVFAgbmV0d29yaw0KICAgICANCiAgICAgDQogICBB
biBNUExTIGRvbWFpbiBtYXkgc2VydmUgbXVsdGlwbGUgY3VzdG9tZXJzLiAgSW4gdGhlc2UgY2Fz
ZXMgdGhlDQogICBNUExTIGRvbWFpbiAobWFpbnRhaW5lZCBieSBhIHNlcnZpY2UgcHJvdmlkZXIp
IG1heSBwcm92aWRlIHRpbWluZw0KICAgc2VydmljZXMgdG8gbXVsdGlwbGUgY3VzdG9tZXJzLCBl
YWNoIGhhdmluZyB0aGVpciBvd24gVGltaW5nIGRvbWFpbi4NCiAgIElmIHNvLCB0aGVuIHRoZSBM
RVIgQkNzIGFuZCBUQ3MgbWF5IGludGVyYWN0IHdpdGggbXVsdGlwbGUgZ3JhbmRtYXN0ZXJzLA0K
ICAgYW5kIGNvbnNlcXVlbnRseSBtdWx0aXBsZSB0aW1lIHJlZmVyZW5jZXMuICBBbHNvLCBMRVIv
TFNSIFRDcyBNVVNUIGJlDQogICBzeW5jaHJvbml6ZWQgdG8gdGhlIHNhbWUgbWFzdGVyIGNsb2Nr
ICh3aGljaCBpcyB0aGUgc2VydmljZSBwcm92aWRlcg0KICAgTWFzdGVyIGNsb2NrKSwgd2hpY2gg
aW1wbGllcyB0aGF0IHRoZXkgbmVlZCB0byBjaG9vc2Ugb25lIG1hc3RlciB0bw0KICAgd2hpY2gg
aXQgd2lsbCBzeW5jaHJvbml6ZS4NCg0KICAgVGhlIFRpbWluZyBvdmVyIE1QTFMgYXJjaGl0ZWN0
dXJlIGFzc3VtZXMgZnVsbCBtZXNoIG9mIFRpbWluZyBMU1BzDQogICBiZXR3ZWVuIGFsbCBMRVJz
IHN1cHBvcnRpbmcgdGhpcyBzcGVjaWZpY2F0aW9uLiAgSXQgc3VwcG9ydHMNCiAgIFBvaW50LXRv
LSBwb2ludCAoVlBXUykgYW5kIE11bHRpcG9pbnQgKFZQTFMpIHNlcnZpY2VzLiAgVGhpcyBtZWFu
cw0KICAgdGhhdCBhIGN1c3RvbWVyIG1heSBwdXJjaGFzZSBhIFBvaW50LXRvLXBvaW50IFRpbWlu
ZyBzZXJ2aWNlIGJldHdlZW4NCiAgIHR3byBjdXN0b21lciBzaXRlcyBvciBhIE11bHRpcG9pbnQg
VGltaW5nIHNlcnZpY2UgYmV0d2VlbiBtb3JlIHRoYW4NCiAgIHR3byBjdXN0b21lciBzaXRlcy4N
Cg0KICAgVGhlIFRpbWluZyBvdmVyIE1QTFMgYXJjaGl0ZWN0dXJlIHN1cHBvcnRzIFAyUCBvciBQ
Mk1QIFRpbWluZyBMU1BzLg0KICAgVGhpcyBtZWFucyB0aGF0IHRoZSBUaW1pbmcgTXVsdGljYXN0
IG1lc3NhZ2VzIHN1Y2ggYXMgUFRQIE11bHRpY2FzdA0KICAgZXZlbnQgbWVzc2FnZXMgY2FuIGJl
IHRyYW5zcG9ydGVkIG92ZXIgUDJNUCBUaW1pbmcgTFNQIG9yIGJlDQogICByZXBsaWNhdGVkIGFu
ZCB0cmFuc3BvcnRlZCBvdmVyIG1hbnkgUDJQIFRpbWluZyBMU1BzLg0KDQogICBUaW1pbmcgbWVz
c2FnZXMsIHRoYXQgZG8gbm90IHJlcXVpcmUgVGltZSBzdGFtcGluZyBvciBDb3JyZWN0aW9uDQog
ICBGaWVsZCB1cGRhdGUgTUFZIGJlIHRyYW5zcG9ydGVkIG92ZXIgVGltaW5nIExTUHMgdG8gc2lt
cGxpZnkgaGFyZHdhcmUNCiAgIGFuZCBzb2Z0d2FyZS4NCg0KICAgUFRQIEFubm91bmNlIG1lc3Nh
Z2VzIHRoYXQgZGV0ZXJtaW5lIHRoZSBUaW1pbmcgTFNQIHRlcm1pbmF0aW5nIHBvaW50DQogICBi
ZWhhdmlvciBzdWNoIGFzIEJDL09DL1RDIFNIT1VMRCBiZSB0cmFuc3BvcnRlZCBvdmVyIHRoZSBU
aW1pbmcgTFNQDQogICB0byBzaW1wbGlmeSBoYXJkd2FyZSBhbmQgc29mdHdhcmUuDQoNCg0KDQoN
Cg0KDQpEYXZhcmksIGV0IGFsLiAgICAgICAgICAgRXhwaXJlcyBBdWd1c3QgMjcsIDIwMTMgICAg
ICAgICAgICAgICBbUGFnZSAxMV0NCgwNCkludGVybmV0LURyYWZ0ICAgICAgICBUcmFuc3BvcnRp
bmcgVGltaW5nIG92ZXIgTVBMUyAgICAgICAgRmVicnVhcnkgMjAxMw0KDQoNCjUuICBEZWRpY2F0
ZWQgTFNQcyBmb3IgVGltaW5nIG1lc3NhZ2VzDQoNCiAgIE1hbnkgbWV0aG9kcyBoYXZlIGJlZW4g
Y29uc2lkZXJlZCBmb3IgaWRlbnRpZnlpbmcgdGhlIFRpbWluZyBtZXNzYWdlcw0KICAgd2hlbiB0
aGV5IGFyZSBlbmNhcHN1bGF0ZWQgaW4gTVBMUyBzdWNoIGFzIHVzaW5nIEdBTC9BQ0ggb3IgYSBu
ZXcNCiAgIHJlc2VydmVkIGxhYmVsLiAgVGhlc2UgbWV0aG9kcyB3ZXJlIG5vdCBhdHRyYWN0aXZl
IHNpbmNlIHRoZXkgZWl0aGVyDQogICByZXF1aXJlZCBkZWVwIHBhY2tldCBpbnNwZWN0aW9uIGF0
IGxpbmUgcmF0ZSBpbiB0aGUgaW50ZXJtZWRpYXRlIExTUnMNCiAgIG9yIHRoZXkgcmVxdWlyZWQg
dXNlIG9mIGEgc2NhcmNlIG5ldyByZXNlcnZlZCBsYWJlbC4gIEFsc28gb25lIG9mIHRoZQ0KICAg
Z29hbHMgd2FzIHRvIHJldXNlIGV4aXN0aW5nIE9BTSBtZWNoYW5pc21zLg0KDQogICBUaGUgbWV0
aG9kIGRlZmluZWQgaW4gdGhpcyBkb2N1bWVudCBjYW4gYmUgdXNlZCBieSBMRVIgYW5kIExTUnMg
dG8NCiAgIGlkZW50aWZ5IFRpbWluZyBtZXNzYWdlcyBpbiBNUExTIHR1bm5lbHMgYnkganVzdCBs
b29raW5nIGF0IHRoZSB0b3ANCiAgIGxhYmVsIGluIHRoZSBNUExTIGxhYmVsIHN0YWNrLCB3aGlj
aCBvbmx5IGNhcnJ5IFRpbWluZyBtZXNzYWdlcyBhcw0KICAgd2VsbCBhcyBPQU0sIGJ1dCBub3Qg
ZGF0YSBwbGFuZSBjbGllbnQgdHJhZmZpYy4NCg0KICAgQ29tcGxpYW50IGltcGxlbWVudGF0aW9u
cyBNVVNUIHVzZSBkZWRpY2F0ZWQgTFNQcyB0byBjYXJyeSBUaW1pbmcNCiAgIG1lc3NhZ2VzIG92
ZXIgTVBMUy4gIFRoZXNlIExTUHMgYXJlIGhlcmVpbiByZWZlcnJlZCB0byBhcyAiVGltaW5nDQog
ICBMU1BzIiBhbmQgdGhlIGxhYmVscyBhc3NvY2lhdGVkIHdpdGggdGhlc2UgTFNQcyBhcyAiVGlt
aW5nIExTUA0KICAgbGFiZWxzIi4gIFRoZSBUaW1pbmcgTFNQcyB0aGF0IHJ1bnMgYmV0d2VlbiBJ
bmdyZXNzIGFuZCBFZ3Jlc3MgTEVScw0KICAgTVVTVCBiZSBjby1yb3V0ZWQuICBBbHRlcm5hdGl2
ZWx5LCBhIHNpbmdsZSBiaWRpcmVjdGlvbmFsIGNvLXJvdXRlZA0KICAgTFNQIGNhbiBiZSB1c2Vk
Lg0KDQogICBDby1yb3V0aW5nIG9mIHRoZSB0d28gZGlyZWN0aW9ucyBpcyByZXF1aXJlZCB0byBs
aW1pdCB0aGUgZGlmZmVyZW5jZQ0KICAgaW4gdGhlIGRlbGF5cyBpbiB0aGUgTWFzdGVyIGNsb2Nr
IHRvIFNsYXZlIGNsb2NrIGRpcmVjdGlvbiBjb21wYXJlZA0KICAgdG8gdGhlIFNsYXZlIGNsb2Nr
IHRvIE1hc3RlciBjbG9jayBkaXJlY3Rpb24uICBUaGUgVGltaW5nIExTUCBNQVkgYmUNCiAgIE1Q
TFMgTFNQIG9yIE1QTFMtVFAgTFNQLg0KDQogICBUaGUgVGltaW5nIExTUHMgY291bGQgYmUgY29u
ZmlndXJlZCBvciBzaWduYWxlZCB2aWEgUlNWUC1URS9HTVBMUy4NCiAgIE5ldyBFeHRlbnNpb25z
IHRvIFJTVlAtVEUvR01QTFMgVExWcyBhcmUgcmVxdWlyZWQ7IGhvd2V2ZXIgdGhleSBhcmUNCiAg
IG91dHNpZGUgdGhlIHNjb3BlIG9mIHRoaXMgZG9jdW1lbnQuDQoNCiAgIFRoZSBUaW1pbmcgTFNQ
cyBNQVkgY2FycnkgZXNzZW50aWFsIE1QTFMvTVBMUy1UUCBPQU0gdHJhZmZpYyBzdWNoIGFzDQog
ICBCRkQgYW5kIExTUCBQaW5nIGJ1dCB0aGUgTFNQIGRhdGEgcGxhbmUgY2xpZW50IHBsYW5lIHRy
YWZmaWMgTVVTVCBiZQ0KICAgVGltaW5nIHBhY2tldHMgb25seS4NCg0KDQoNCg0KDQoNCg0KDQoN
Cg0KDQoNCg0KDQoNCg0KDQoNCkRhdmFyaSwgZXQgYWwuICAgICAgICAgICBFeHBpcmVzIEF1Z3Vz
dCAyNywgMjAxMyAgICAgICAgICAgICAgIFtQYWdlIDEyXQ0KDA0KSW50ZXJuZXQtRHJhZnQgICAg
ICAgIFRyYW5zcG9ydGluZyBUaW1pbmcgb3ZlciBNUExTICAgICAgICBGZWJydWFyeSAyMDEzDQoN
Cg0KNi4gIFRpbWluZyBvdmVyIExTUCBFbmNhcHN1bGF0aW9uDQoNCiAgIFRoaXMgZG9jdW1lbnQg
ZGVmaW5lcyB0d28gbWV0aG9kcyBmb3IgY2FycnlpbmcgVGltaW5nIG1lc3NhZ2VzIG92ZXINCiAg
IE1QTFMuICBUaGUgZmlyc3QgbWV0aG9kIGlzIGNhcnJ5aW5nIFVEUC9JUCBlbmNhcHN1bGF0ZWQg
VGltaW5nDQogICBtZXNzYWdlcyBvdmVyIFRpbWluZyBMU1BzLCB3aGljaCBpcyBzdWl0YWJsZSBm
b3IgTVBMUyBuZXR3b3JrcyBhbmQNCiAgIHRoZSBzZWNvbmQgbWV0aG9kLCBpcyBjYXJyeWluZyBF
dGhlcm5ldCBlbmNhcHN1bGF0ZWQgVGltaW5nIG1lc3NhZ2VzDQogICBvdmVyIEV0aGVybmV0IFBX
cyBpbnNpZGUgVGltaW5nIExTUHMsIHdoaWNoIGlzIHN1aXRhYmxlIGZvciBNUExTIGFuZA0KICAg
TVBMUy1UUCBuZXR3b3Jrcy4NCg0KNi4xLiAgVGltaW5nIG92ZXIgVURQL0lQIG92ZXIgTVBMUyBF
bmNhcHN1bGF0aW9uDQoNCiAgIFRoZSBzaW1wbGVzdCBtZXRob2Qgb2YgdHJhbnNwb3J0aW5nIFRp
bWluZyBtZXNzYWdlcyBvdmVyIE1QTFMgaXMgdG8NCiAgIGVuY2Fwc3VsYXRlIFRpbWluZyBQRFVz
IGluIFVEUC9JUCBhbmQgdGhlbiBlbmNhcHN1bGF0ZSB0aGVtIGluIFRpbWluZw0KICAgTFNQLiAg
VGhpcyBmb3JtYXQgaXMgc2hvd24gaW4gRmlndXJlIDQuDQoNCg0KICAgICAgICAgICAgICAgICAg
ICArLS0tLS0tLS0tLS0tLS0tLS0tLS0tLSsNCiAgICAgICAgICAgICAgICAgICAgfCAgIFRpbWlu
ZyBMU1AgTGFiZWwgICB8DQogICAgICAgICAgICAgICAgICAgICstLS0tLS0tLS0tLS0tLS0tLS0t
LS0tKw0KICAgICAgICAgICAgICAgICAgICB8ICAgICAgICBJUHY0LzYgICAgICAgIHwNCiAgICAg
ICAgICAgICAgICAgICAgKy0tLS0tLS0tLS0tLS0tLS0tLS0tLS0rDQogICAgICAgICAgICAgICAg
ICAgIHwgICAgICAgICBVRFAgICAgICAgICAgfA0KICAgICAgICAgICAgICAgICAgICArLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLSsNCiAgICAgICAgICAgICAgICAgICAgfCAgICAgVGltaW5nIFBEVSAg
ICAgICB8DQogICAgICAgICAgICAgICAgICAgICstLS0tLS0tLS0tLS0tLS0tLS0tLS0tKw0KDQog
ICAgICBGaWd1cmUgKDQpIC0gVGltaW5nIG92ZXIgVURQL0lQIG92ZXIgTVBMUyBFbmNhcHN1bGF0
aW9uDQoNCg0KICAgVGhpcyBlbmNhcHN1bGF0aW9uIGlzIHZlcnkgc2ltcGxlIGFuZCBpcyB1c2Vm
dWwgd2hlbiB0aGUgbmV0d29yaw0KICAgYmV0d2VlbiBUaW1pbmcgTWFzdGVyIENsb2NrIGFuZCBT
bGF2ZSBDbG9jayBpcyBNUExTIG5ldHdvcmsuDQoNCiAgIEluIG9yZGVyIGZvciBhbiBMRVIvTFNS
IHRvIHByb2Nlc3MgVGltaW5nIG1lc3NhZ2VzLCB0aGUgVGltaW5nIExTUA0KICAgTGFiZWwgbXVz
dCBiZSBhdCB0aGUgdG9wIGxhYmVsIG9mIHRoZSBsYWJlbCBzdGFjay4gIFRoZSBMRVIvTFNSIE1V
U1QNCiAgIGtub3cgdGhhdCB0aGUgVGltaW5nIExTUCBMYWJlbCBpcyB1c2VkIGZvciBjYXJyeWlu
ZyBUaW1pbmcgbWVzc2FnZXMuDQogICBUaGlzIGNhbiBiZSBhY2NvbXBsaXNoZWQgdmlhIHN0YXRp
YyBjb25maWd1cmF0aW9uIG9yIHZpYSBSU1ZQLVRFDQogICBzaWduYWxpbmcuDQoNCiAgIFRoZSBV
RFAvSVAgZW5jYXBzdWxhdGlvbiBvZiBQVFAgTVVTVCBmb2xsb3cgQW5uZXggRCBhbmQgRSBvZiBb
SUVFRV0uDQogICBXaGlsZSB0aGUgVURQL0lQIGVuY2Fwc3VsYXRpb24gb2YgTlRQIE1VU1QgZm9s
bG93IFtSRkM1OTA1XS4NCg0KNi4yLiAgVGltaW5nIG92ZXIgUFcgRW5jYXBzdWxhdGlvbg0KDQog
ICBBbm90aGVyIG1ldGhvZCBvZiB0cmFuc3BvcnRpbmcgVGltaW5nIG92ZXIgTVBMUyBuZXR3b3Jr
cyBpcyBieQ0KICAgZW5jYXBzdWxhdGluZyBUaW1pbmcgUERVcyBpbiBQVyB3aGljaCBpbiB0dXJu
IGlzIHRyYW5zcG9ydGVkIG92ZXINCiAgIFRpbWluZyBMU1BzLiAgSW4gY2FzZSBvZiBQVFAsIEV0
aGVybmV0IFBXIGVuY2Fwc3VsYXRpb24gW1JGQzQ0NDhdLA0KICAgc2hvd24gaW4gRmlnIDUoQSkg
TVVTVCBiZSB1c2VkIGFuZCB0aGUgRXRoZXJuZXQgZW5jYXBzdWxhdGlvbiBvZiBQVFANCiAgIE1V
U1QgZm9sbG93IEFubmV4IEYgb2YgW0lFRUVdLg0KDQoNCg0KRGF2YXJpLCBldCBhbC4gICAgICAg
ICAgIEV4cGlyZXMgQXVndXN0IDI3LCAyMDEzICAgICAgICAgICAgICAgW1BhZ2UgMTNdDQoMDQpJ
bnRlcm5ldC1EcmFmdCAgICAgICAgVHJhbnNwb3J0aW5nIFRpbWluZyBvdmVyIE1QTFMgICAgICAg
IEZlYnJ1YXJ5IDIwMTMNCg0KDQogICBUaGUgVGFnZ2VkIG1vZGUgZGVmaW5lZCBpbiBbUkZDLTQ0
NDhdIE1VU1QgYmUgdXNlZCBhbmQgdGhlIFBheWxvYWQNCiAgIE1VU1QgaGF2ZSAyIFZMQU4gdGFn
cyAoUy1WTEFOIGFuZCBDLVZMQU4pLiAgVGhlIFRpbWluZyBvdmVyIFBXDQogICBlbmNhcHN1bGF0
aW9uIE1VU1QgdXNlIHRoZSBDb250cm9sIFdvcmQgKENXKSBhcyBzcGVjaWZpZWQgaW4NCiAgIFtS
RkM0NDQ4XSB0byBlbnN1cmUgcHJvcGVyIGRldGVjdGlvbiBvZiBQVFAgbWVzc2FnZXMgaW5zaWRl
IHRoZSBNUExTDQogICBwYWNrZXRzIGZvciBUaW1pbmcgb3ZlciBMU1AgYW5kIFRpbWluZyBvdmVy
IFBXIGVuY2Fwc3VsYXRpb24uICBUaGUNCiAgIHVzZSBvZiBTZXF1ZW5jZSBOdW1iZXIgaW4gdGhl
IENXIGlzIG9wdGlvbmFsLg0KDQogICBUaW1pbmcgb3ZlciBQVyBlbmNhcHN1bGF0aW9uIGZvciBO
VFAgTVVTVCB1c2UgTlRQIG92ZXIgVURQL0lQIG92ZXIgUFcNCiAgICh0aGUgSVAgUFcgZGlzY3Vz
c2VkIGluIFtSRkM0NDQ3XSkgc2hvd24gaW4gRmlnIDUoQikuDQoNCiAgICAgICAgICAgICAgICAg
ICstLS0tLS0tLS0tLS0tLS0tKyAgKy0tLS0tLS0tLS0tLS0tLS0rDQogICAgICAgICAgICAgICAg
ICB8VGltaW5nIExTUCBMYWJlbHwgIHxUaW1pbmcgTFNQIExhYmVsfA0KICAgICAgICAgICAgICAg
ICAgKy0tLS0tLS0tLS0tLS0tLS0rICArLS0tLS0tLS0tLS0tLS0tLSsNCiAgICAgICAgICAgICAg
ICAgIHwgICAgUFcgTGFiZWwgICAgfCAgfCAgICBQVyBMYWJlbCAgICB8DQogICAgICAgICAgICAg
ICAgICArLS0tLS0tLS0tLS0tLS0tLSsgICstLS0tLS0tLS0tLS0tLS0tKw0KICAgICAgICAgICAg
ICAgICAgfCAgQ29udHJvbCBXb3JkICB8ICB8ICAgICAgSVAgICAgICAgIHwNCiAgICAgICAgICAg
ICAgICAgICstLS0tLS0tLS0tLS0tLS0tKyAgKy0tLS0tLS0tLS0tLS0tLS0rDQogICAgICAgICAg
ICAgICAgICB8ICAgIEV0aGVybmV0ICAgIHwgIHwgICAgICBVRFAgICAgICAgfA0KICAgICAgICAg
ICAgICAgICAgfCAgICAgSGVhZGVyICAgICB8ICArLS0tLS0tLS0tLS0tLS0tLSsNCiAgICAgICAg
ICAgICAgICAgICstLS0tLS0tLS0tLS0tLS0tKyAgfCAgIFRpbWluZyBQRFUgICB8DQogICAgICAg
ICAgICAgICAgICB8ICAgICBTLVZMQU4gICAgIHwgIHwgICAgICAgICAgICAgICAgfA0KICAgICAg
ICAgICAgICAgICAgKy0tLS0tLS0tLS0tLS0tLS0rICArLS0tLS0tLS0tLS0tLS0tLSsNCiAgICAg
ICAgICAgICAgICAgIHwgICAgIEMtVkxBTiAgICAgfCAgICAgICAgKEIpDQogICAgICAgICAgICAg
ICAgICArLS0tLS0tLS0tLS0tLS0tLSsNCiAgICAgICAgICAgICAgICAgIHwgICBUaW1pbmcgUERV
ICAgfA0KICAgICAgICAgICAgICAgICAgfCAgICAgICAgICAgICAgICB8DQogICAgICAgICAgICAg
ICAgICArLS0tLS0tLS0tLS0tLS0tLSsNCiAgICAgICAgICAgICAgICAgICAgICAgICAoQSkNCg0K
DQogICAgICAgICAgICAgIEZpZ3VyZSAoNSkgLSBUaW1pbmcgb3ZlciBQVyBFbmNhcHN1bGF0aW9u
cw0KDQogICBJbiBvcmRlciBmb3IgYW4gTFNSIHRvIHByb2Nlc3MgUFRQIG1lc3NhZ2VzLCB0aGUg
dG9wIGxhYmVsIG9mIHRoZQ0KICAgbGFiZWwgc3RhY2sgKHRoZSBUdW5uZWwgTGFiZWwpIE1VU1Qg
YmUgYSBUaW1pbmcgbGFiZWwuDQoNCiAgIFRoZSBQVyBtZXRob2Qgb2YgdHJhbnNwb3J0aW5nIFRp
bWluZyBvdmVyIE1QTFMgaXMgYXBwbGljYWJsZSB0byBib3RoDQogICBNUExTIGFuZCBNUExTLVRQ
IG5ldHdvcmtzLg0KDQo2LjMuICBPdGhlciBUaW1pbmcgRW5jYXBzdWxhdGlvbiBtZXRob2RzDQoN
CiAgIEluIGZ1dHVyZSBvdGhlciB0aW1pbmcgZW5jYXBzdWxhdGlvbiBtZXRob2RzIG1heSBiZSBp
bnRyb2R1Y2VkLCBzdWNoDQogICBhcyBhIG5ldyBzaGltIGhlYWRlciBhZnRlciB0aGUgQm90dG9t
IG9mIFN0YWNrIHRvIGNhcnJ5IHRoZSBUaW1pbmcNCiAgIGluZm9ybWF0aW9uLiAgU3VjaCBuZXcg
ZW5jYXBzdWxhdGlvbnMgYXJlIG91dHNpZGUgdGhlIHNjb3BlIG9mIHRoaXMNCiAgIGRvY3VtZW50
LiAgVGhlIGNvbnRyb2wgYW5kIHNpZ25hbGluZyByZXF1aXJlbWVudHMgaW4gdGhpcyBkb2N1bWVu
dA0KICAgYXJlIGRlZmluZWQgZ2VuZXJpY2FsbHkgZW5vdWdoIHRvIGFjY29tbW9kYXRlIGFueSBz
dWNoIG5ldw0KICAgZW5jYXBzdWxhdGlvbnMuDQoNCg0KDQoNCg0KRGF2YXJpLCBldCBhbC4gICAg
ICAgICAgIEV4cGlyZXMgQXVndXN0IDI3LCAyMDEzICAgICAgICAgICAgICAgW1BhZ2UgMTRdDQoM
DQpJbnRlcm5ldC1EcmFmdCAgICAgICAgVHJhbnNwb3J0aW5nIFRpbWluZyBvdmVyIE1QTFMgICAg
ICAgIEZlYnJ1YXJ5IDIwMTMNCg0KDQo3LiAgVGltaW5nIG1lc3NhZ2UgUHJvY2Vzc2luZw0KDQog
ICBFYWNoIFRpbWluZyBwcm90b2NvbCBzdWNoIGFzIFBUUCBhbmQgTlRQLCBkZWZpbmUgdGhlaXIg
c2V0IG9mIFRpbWluZw0KICAgbWVzc2FnZXMuICBGb3IgZXhhbXBsZSBQVFAgZGVmaW5lcyBTWU5D
LCBERUxBWV9SRVEsIERFTEFZX1JFU1AsDQogICBGT0xMT1dfVVAsIGV0YyBtZXNzYWdlcy4NCg0K
ICAgU29tZSBvZiB0aGUgVGltaW5nIG1lc3NhZ2VzIHJlcXVpcmUgdGltZSBzdGFtcGluZyBhdCBw
b3J0IGxldmVsIGFuZA0KICAgc29tZSBkb250LiAgSXQgaXMgdGhlIGpvYiBvZiB0aGUgTEVSL0xT
UiB0byBwYXJzZSB0aGUgdGltaW5nIG1lc3NhZ2UNCiAgIGFuZCBmaW5kIG91dCB0aGUgdHlwZSBv
ZiB0aGUgVGltaW5nIG1lc3NhZ2UgYW5kIGRlY2lkZSB3aGV0aGVyIGFuZA0KICAgaG93IHRvIFRp
bWUtIHN0YW1wIGl0IChlLmcuLCBCQykgb3IgbW9kaWZ5IGV4aXN0aW5nIHRpbWUtc3RhbXAgaW4g
aXQNCiAgIChlLmcuLCBUQykuDQoNCiAgIEZvciBleGFtcGxlIHRoZSBmb2xsb3dpbmcgUFRQIG1l
c3NhZ2VzIChjYWxsZWQgRXZlbnQgbWVzc2FnZXMpDQogICByZXF1aXJlIHRpbWUtc3RhbXBpbmcs
IHdoaWxlIG90aGVyIE5vbi1FdmVudCBQVFAgbWVzc2FnZXMgZG8gbm90IG5lZWQNCiAgIHRpbWUt
c3RhbXBpbmcuDQoNCiAgIG8gIFNZTkMNCg0KICAgbyAgREVMQVlfUkVRIChEZWxheSBSZXF1ZXN0
KQ0KDQogICBvICBQREVMQVlfUkVRIChQZWVyIERlbGF5IFJlcXVlc3QpDQoNCiAgIG8gIFBERUxB
WV9SRVNQIChQZWVyIERlbGF5IFJlc3BvbnNlKQ0KDQogICBTWU5DIGFuZCBERUxBWV9SRVEgYXJl
IGV4Y2hhbmdlZCBiZXR3ZWVuIE1hc3RlciBDbG9jayBhbmQgU2xhdmUgQ2xvY2sNCiAgIGFuZCBN
VVNUIGJlIHRyYW5zcG9ydGVkIG92ZXIgUFRQIExTUHMuICBQREVMQVlfUkVRIGFuZCBQREVMQVlf
UkVTUA0KICAgYXJlIGV4Y2hhbmdlZCBiZXR3ZWVuIGFkamFjZW50IFBUUCBjbG9ja3MgKGkuZS4g
IE1hc3RlciwgU2xhdmUsDQogICBCb3VuZGFyeSwgb3IgVHJhbnNwYXJlbnQpIGFuZCBTSE9VTEQg
YmUgdHJhbnNwb3J0ZWQgb3ZlciBzaW5nbGUgaG9wDQogICBQVFAgTFNQcy4gIElmIFR3byBTdGVw
IFBUUCBjbG9ja3MgYXJlIHByZXNlbnQsIHRoZW4gdGhlIEZPTExPV19VUCwNCiAgIERFTEFZX1JF
U1AsIGFuZCBQREVMQVlfUkVTUF9GT0xMT1dfVVAgbWVzc2FnZXMgTVVTVCBhbHNvIGJlDQogICB0
cmFuc3BvcnRlZCBvdmVyIHRoZSBQVFAgTFNQcy4NCg0KICAgRm9yIGEgZ2l2ZW4gaW5zdGFuY2Ug
b2YgMTU4OCBwcm90b2NvbCwgU1lOQyBhbmQgREVMQVlfUkVRIE1VU1QgYmUNCiAgIHRyYW5zcG9y
dGVkIG92ZXIgdHdvIFBUUCBMU1BzIHRoYXQgYXJlIGluIG9wcG9zaXRlIGRpcmVjdGlvbnMuICBU
aGVzZQ0KICAgUFRQIExTUHMsIHdoaWNoIGFyZSBpbiBvcHBvc2l0ZSBkaXJlY3Rpb25zIE1VU1Qg
YmUgY29uZ3J1ZW50IGFuZCBjby0NCiAgIHJvdXRlZC4gIEFsdGVybmF0aXZlbHksIGEgc2luZ2xl
IGJpZGlyZWN0aW9uYWwgY28tcm91dGVkIExTUCBjYW4gYmUNCiAgIHVzZWQuDQoNCiAgIEV4Y2Vw
dCBhcyBpbmRpY2F0ZWQgYWJvdmUgZm9yIHRoZSB0d28tc3RlcCBQVFAgY2xvY2tzLCBOb24tRXZl
bnQgUFRQDQogICBtZXNzYWdlIHR5cGVzIGRvIG5vdCBuZWVkIHRvIGJlIHByb2Nlc3NlZCBieSBp
bnRlcm1lZGlhdGUgcm91dGVycy4NCiAgIFRoZXNlIG1lc3NhZ2UgdHlwZXMgTUFZIGJlIGNhcnJp
ZWQgaW4gUFRQIFR1bm5lbCBMU1BzLg0KDQoNCg0KDQoNCg0KDQoNCg0KDQpEYXZhcmksIGV0IGFs
LiAgICAgICAgICAgRXhwaXJlcyBBdWd1c3QgMjcsIDIwMTMgICAgICAgICAgICAgICBbUGFnZSAx
NV0NCgwNCkludGVybmV0LURyYWZ0ICAgICAgICBUcmFuc3BvcnRpbmcgVGltaW5nIG92ZXIgTVBM
UyAgICAgICAgRmVicnVhcnkgMjAxMw0KDQoNCjguICBQcm90ZWN0aW9uIGFuZCBSZWR1bmRhbmN5
DQoNCiAgIEluIG9yZGVyIHRvIGVuc3VyZSBjb250aW51b3VzIHVuaW50ZXJydXB0ZWQgb3BlcmF0
aW9uIG9mIHNsYXZlDQogICBjbG9ja3MsIHVzdWFsbHkgYXMgYSBnZW5lcmFsIHByYWN0aWNlLCBz
bGF2ZSBjbG9ja3MgKG9yIHBvcnRzKSB0cmFjaw0KICAgcmVkdW5kYW50IG1hc3RlciBjbG9ja3Mu
DQoNCiAgIEl0IGlzIHRoZSByZXNwb25zaWJpbGl0eSBvZiB0aGUgbmV0d29yayBvcGVyYXRvciB0
byBlbnN1cmUgdGhhdA0KICAgcGh5c2ljYWxseSBkaXNqb2ludCBUaW1pbmcgTFNQcyBhcmUgZXN0
YWJsaXNoZWQgYmV0d2VlbiBhIHNsYXZlIGNsb2NrDQogICAob3IgcG9ydCkgYW5kIHJlZHVuZGFu
dCBtYXN0ZXIgY2xvY2tzIChvciBwb3J0cykuDQoNCiAgIFdoZW4gYSBzbGF2ZSBjbG9jayAob3Ig
cG9ydCkgbGlzdGVucyB0byByZWR1bmRhbnQgbWFzdGVyIGNsb2NrcyBvcg0KICAgcG9ydHMsIGFu
eSBwcm9sb25nZWQgVGltaW5nIExTUCBvdXRhZ2Ugd2lsbCB0cmlnZ2VyIHRoZSBzbGF2ZSBjbG9j
aw0KICAgb3IgcG9ydCB0byBzd2l0Y2ggdG8gYSByZWR1bmRhbnQgbWFzdGVyIGNsb2NrIG9yIHBv
cnQuDQoNCiAgIExTUC9QVyBwcm90ZWN0aW9uIHN1Y2ggYXMgTGluZWFyIHByb3RlY3Rpb24gU3dp
dGNoaW5nICgxOjEsIDErMSksDQogICBSaW5nIHByb3RlY3Rpb24gc3dpdGNoaW5nIG9yIE1QTFMg
RmFzdCBSZXJvdXRlIChGUlIpIGdlbmVyYWxseSBzd2l0Y2gNCiAgIGFsdGVybmF0aXZlIHBhdGgg
dGhhdCB1c3VhbGx5IGNhdXNlIGEgY2hhbmdlIGluIGRlbGF5LCB3aGljaCBpZg0KICAgdW5kZXRl
Y3RlZCBieSBzbGF2ZSBjbG9jayBjYW4gcmVkdWNlIGFjY3VyYWN5IG9mIHRoZSBzbGF2ZSBjbG9j
ay4NCiAgIEhvd2V2ZXIgaXQgaXMgZXhwZWN0ZWQgdGhhdCBtb3N0IFNsYXZlIGNsb2NrcyBjb3Vs
ZCBkZXRlY3QgdGhlIGNoYW5nZQ0KICAgaW4gZGVsYXkuICBUaGVyZWZvcmUgdGhpcyBzcGVjaWZp
Y2F0aW9uIHJlY29tbWVuZHMgdGhhdCBwcm90ZWN0aW9uDQogICBzd2l0Y2hpbmcgU0hPVUxEIGJl
IHVzZWQsIHVubGVzcyB0aGUgb3BlcmF0b3Iga25vd3MgdGhhdCB0aGUNCiAgIHByb3RlY3Rpb24g
c3dpdGNoaW5nIG1heSBoYXZlIGFkdmVyc2UgZWZmZWN0IG9uIHRoZSBzbGF2ZSBjbG9jay4NCg0K
ICAgTm90ZSB0aGF0IGFueSBwcm90ZWN0aW9uIG9yIHJlcm91dGUgbWVjaGFuaXNtIHRoYXQgYWRk
cyBhZGRpdGlvbmFsDQogICBNUExTIGxhYmVsIHRvIHRoZSBsYWJlbCBzdGFjaywgc3VjaCBhcyBG
YWNpbGl0eSBCYWNrdXAgRmFzdCBSZXJvdXRlLA0KICAgTVVTVCBlbnN1cmUgdGhhdCB0aGUgcHVz
aGVkIGxhYmVsIGlzIGFsc28gYSBUaW1pbmcgTGFiZWwgdG8gZW5zdXJlDQogICByZWNvZ25pdGlv
biBvZiB0aGUgTVBMUyBmcmFtZSBhcyBjb250YWluaW5nIFRpbWluZyBtZXNzYWdlcywgYXMgaXQN
CiAgIHRyYW5zaXRzIHRoZSBiYWNrdXAgcGF0aC4NCg0KDQoNCg0KDQoNCg0KDQoNCg0KDQoNCg0K
DQoNCg0KDQoNCg0KDQoNCg0KDQpEYXZhcmksIGV0IGFsLiAgICAgICAgICAgRXhwaXJlcyBBdWd1
c3QgMjcsIDIwMTMgICAgICAgICAgICAgICBbUGFnZSAxNl0NCgwNCkludGVybmV0LURyYWZ0ICAg
ICAgICBUcmFuc3BvcnRpbmcgVGltaW5nIG92ZXIgTVBMUyAgICAgICAgRmVicnVhcnkgMjAxMw0K
DQoNCjkuICBFQ01QDQoNCiAgIFRvIGVuc3VyZSB0aGUgb3B0aW1hbCBvcGVyYXRpb24gb2Ygc2xh
dmUgY2xvY2tzIGFuZCBhdm9pZCBlcnJvcg0KICAgaW50cm9kdWNlZCBieSBmb3J3YXJkIGFuZCBy
ZXZlcnNlIHBhdGggZGVsYXkgYXN5bW1ldHJ5LCB0aGUgcGh5c2ljYWwNCiAgIHBhdGggZm9yIFRp
bWluZyBtZXNzYWdlcyBmcm9tIG1hc3RlciBjbG9jayB0byBzbGF2ZSBDbG9jayBhbmQgdmljZQ0K
ICAgdmVyc2EgbXVzdCBiZSB0aGUgc2FtZSBmb3IgYWxsIEV2ZW50IFRpbWluZyBtZXNzYWdlcyBs
aXN0ZWQgaW4NCiAgIHNlY3Rpb24gNy4NCg0KICAgVGhlcmVmb3JlIHRoZSBUaW1pbmcgTFNQcyBN
VVNUIG5vdCBiZSBzdWJqZWN0IHRvIEVDTVAgKEVxdWFsIENvc3QNCiAgIE11bHRpcGF0aCkuDQoN
Cg0KDQoNCg0KDQoNCg0KDQoNCg0KDQoNCg0KDQoNCg0KDQoNCg0KDQoNCg0KDQoNCg0KDQoNCg0K
DQoNCg0KDQoNCg0KDQoNCg0KDQoNCg0KRGF2YXJpLCBldCBhbC4gICAgICAgICAgIEV4cGlyZXMg
QXVndXN0IDI3LCAyMDEzICAgICAgICAgICAgICAgW1BhZ2UgMTddDQoMDQpJbnRlcm5ldC1EcmFm
dCAgICAgICAgVHJhbnNwb3J0aW5nIFRpbWluZyBvdmVyIE1QTFMgICAgICAgIEZlYnJ1YXJ5IDIw
MTMNCg0KDQoxMC4gIFBIUA0KDQogICBUbyBlbnN1cmUgdGhhdCB0aGUgbGFiZWwgb24gdGhlIHRv
cCBvZiB0aGUgbGFiZWwgc3RhY2sgaXMgdGhlIFRpbWluZw0KICAgTFNQIExhYmVsLCBQSFAgTVVT
VCBub3QgYmUgdXNlZC4NCg0KDQoNCg0KDQoNCg0KDQoNCg0KDQoNCg0KDQoNCg0KDQoNCg0KDQoN
Cg0KDQoNCg0KDQoNCg0KDQoNCg0KDQoNCg0KDQoNCg0KDQoNCg0KDQoNCg0KDQoNCg0KDQpEYXZh
cmksIGV0IGFsLiAgICAgICAgICAgRXhwaXJlcyBBdWd1c3QgMjcsIDIwMTMgICAgICAgICAgICAg
ICBbUGFnZSAxOF0NCgwNCkludGVybmV0LURyYWZ0ICAgICAgICBUcmFuc3BvcnRpbmcgVGltaW5n
IG92ZXIgTVBMUyAgICAgICAgRmVicnVhcnkgMjAxMw0KDQoNCjExLiAgRW50cm9weQ0KDQogICBU
byBlbnN1cmUgYWxsIFRpbWluZyBtZXNzYWdlcyBpbiBhIFRpbWluZyBMU1AgdGFrZSB0aGUgc2Ft
ZSBwYXRoLA0KICAgRW50cm9weSBNVVNUIE5PVCBiZSB1c2VkIGZvciB0aGUgVGltaW5nIExTUCBb
bXBscy1lbnRyb3B5XSBhbmQNCiAgIEVudHJvcHkgTVNVVCBOT1QgYmUgdXNlZCBmb3IgdGhlIFBX
cyB0aGF0IGFyZSBjYXJyaWVkIGluc2lkZSBUaW1pbmcNCiAgIExTUCBbUkZDNjM5MV0uDQoNCg0K
DQoNCg0KDQoNCg0KDQoNCg0KDQoNCg0KDQoNCg0KDQoNCg0KDQoNCg0KDQoNCg0KDQoNCg0KDQoN
Cg0KDQoNCg0KDQoNCg0KDQoNCg0KDQoNCg0KDQpEYXZhcmksIGV0IGFsLiAgICAgICAgICAgRXhw
aXJlcyBBdWd1c3QgMjcsIDIwMTMgICAgICAgICAgICAgICBbUGFnZSAxOV0NCgwNCkludGVybmV0
LURyYWZ0ICAgICAgICBUcmFuc3BvcnRpbmcgVGltaW5nIG92ZXIgTVBMUyAgICAgICAgRmVicnVh
cnkgMjAxMw0KDQoNCjEyLiAgT0FNLCBDb250cm9sIGFuZCBNYW5hZ2VtZW50DQoNCiAgIEluIG9y
ZGVyIHRvIG1vbml0b3IgVGltaW5nIExTUHMgYW5kIHRoZWlyIGVuY2Fwc3VsYXRlZCBQV3MsIHRo
ZXkgTVVTVA0KICAgYmUgYWJsZSB0byBjYXJyeSBPQU0gYW5kIG1hbmFnZW1lbnQgbWVzc2FnZXMu
ICBUaGVzZSBtYW5hZ2VtZW50DQogICBtZXNzYWdlcyBNVVNUIGJlIGRpZmZlcmVudGlhdGVkIGZy
b20gVGltaW5nIG1lc3NhZ2VzIHZpYSBhbHJlYWR5DQogICBkZWZpbmVkIElFVEYgbWV0aG9kcy4N
Cg0KICAgRm9yIGV4YW1wbGUgQkZEIFtSRkM1ODgwXSwgW1JGQzU4ODRdIGFuZCBMU1AtUGluZyBb
UkZDNDM4OV0gTUFZIHJ1bg0KICAgb3ZlciBQVFAgTFNQcyB2aWEgVURQL0lQIGVuY2Fwc3VsYXRp
b24gb3IgdmlhIEdBTC9HLUFDSC4gIFRoZXNlDQogICBNYW5hZ2VtZW50IHByb3RvY29scyBjYW4g
ZWFzaWx5IGJlIGlkZW50aWZpZWQgYnkgdGhlIFVEUCBEZXN0aW5hdGlvbg0KICAgUG9ydCBudW1i
ZXIgb3IgYnkgR0FML0FDSCByZXNwZWN0aXZlbHkuDQoNCiAgIEFsc28gQkZELCBMU1AtUGluZyBh
bmQgb3RoZXIgbWFuYWdlbWVudCBtZXNzYWdlcyBNQVkgcnVuIG92ZXIgdGhlIFBXcw0KICAgZW5j
YXBzdWxhdGVkIGluIFRpbWluZyBMU1AgdmlhIG9uZSBvZiB0aGUgZGVmaW5lZCBWQ0NWcyAoVHlw
ZSAxLCAzIG9yDQogICA0KSBbUkZDNTA4NV0gKG5vdGUgdGhhdCBWQ0NWIFR5cGUgMiB1c2luZyBS
b3V0ZXIgQWxlcnQgTGFiZWwgaXMgZ29pbmcNCiAgIHRvIGJlIGRlcHJlY2F0ZWQgYnkgSUVURiku
ICBJbiB0aGlzIGNhc2UgRy1BQ0gsIFBXIGxhYmVsIChUVEw9MSkgb3INCiAgIEdBTC1BQ0ggYXJl
IHVzZWQgdG8gaWRlbnRpZnkgc3VjaCBtYW5hZ2VtZW50IG1lc3NhZ2VzLg0KDQoNCg0KDQoNCg0K
DQoNCg0KDQoNCg0KDQoNCg0KDQoNCg0KDQoNCg0KDQoNCg0KDQoNCg0KDQoNCg0KDQoNCg0KDQpE
YXZhcmksIGV0IGFsLiAgICAgICAgICAgRXhwaXJlcyBBdWd1c3QgMjcsIDIwMTMgICAgICAgICAg
ICAgICBbUGFnZSAyMF0NCgwNCkludGVybmV0LURyYWZ0ICAgICAgICBUcmFuc3BvcnRpbmcgVGlt
aW5nIG92ZXIgTVBMUyAgICAgICAgRmVicnVhcnkgMjAxMw0KDQoNCjEzLiAgUW9TIENvbnNpZGVy
YXRpb25zDQoNCiAgIEluIG5ldHdvcmsgZGVwbG95bWVudHMgd2hlcmUgbm90IGV2ZXJ5IExTUi9M
RVIgaXMgVGltaW5nLWF3YXJlLCBpdCBpcw0KICAgaW1wb3J0YW50IHRvIHJlZHVjZSB0aGUgaW1w
YWN0IG9mIHRoZSBub24tVGltaW5nLWF3YXJlIExTUi9MRVJzIG9uDQogICB0aGUgdGltaW5nIHJl
Y292ZXJ5IGluIHRoZSBzbGF2ZSBjbG9jay4gIFRoZSBUaW1pbmcgbWVzc2FnZXMgYXJlIHRpbWUN
CiAgIGNyaXRpY2FsIGFuZCBtdXN0IGJlIHRyZWF0ZWQgd2l0aCB0aGUgaGlnaGVzdCBwcmlvcml0
eS4gIFRoZXJlZm9yZQ0KICAgVGltaW5nIG92ZXIgTVBMUyBtZXNzYWdlcyBtdXN0IGJlIHRyZWF0
ZWQgd2l0aCB0aGUgaGlnaGVzdCBwcmlvcml0eQ0KICAgaW4gdGhlIHJvdXRlcnMuICBUaGlzIGNh
biBiZSBhY2hpZXZlZCBieSBwcm9wZXIgc2V0dXAgb2YgVGltaW5nIExTUHMuDQoNCiAgIEl0IGlz
IHJlY29tbWVuZGVkIHRoYXQgdGhlIFRpbWluZyBMU1BzIGFyZSBzZXR1cCBvciBjb25maWd1cmVk
DQogICBwcm9wZXJseSB0byBpbmRpY2F0ZSBFRi1QSEIgW1JGQzMyNDZdZm9yIHRoZSBDb1MgYW5k
IEdyZWVuIFtSRkMyNjk3XQ0KICAgZm9yIGRyb3AgZWxpZ2liaWxpdHkuDQoNCg0KDQoNCg0KDQoN
Cg0KDQoNCg0KDQoNCg0KDQoNCg0KDQoNCg0KDQoNCg0KDQoNCg0KDQoNCg0KDQoNCg0KDQoNCg0K
DQoNCg0KDQpEYXZhcmksIGV0IGFsLiAgICAgICAgICAgRXhwaXJlcyBBdWd1c3QgMjcsIDIwMTMg
ICAgICAgICAgICAgICBbUGFnZSAyMV0NCgwNCkludGVybmV0LURyYWZ0ICAgICAgICBUcmFuc3Bv
cnRpbmcgVGltaW5nIG92ZXIgTVBMUyAgICAgICAgRmVicnVhcnkgMjAxMw0KDQoNCjE0LiAgRkNT
IFJlY2FsY3VsYXRpb24NCg0KICAgV2hlbiB0aW1lLXN0YW1wIGdlbmVyYXRpb24gYW5kIHRpbWlu
ZyBwYWNrZXQgYWRqdXN0bWVudCBpcyBwZXJmb3JtZWQNCiAgIG5lYXIgdGhlIHBoeXNpY2FsIHBv
cnQgaGFyZHdhcmUsIHRoZSBwcm9jZXNzIE1VU1QgaW5jbHVkZQ0KICAgcmVjYWxjdWxhdGlvbiBv
ZiB0aGUgRXRoZXJuZXQgRkNTLiAgQWxzbyBGQ1MgcmV0ZW50aW9uIGZvciB0aGUNCiAgIHBheWxv
YWQgRXRoZXJuZXQgZGVzY3JpYmVkIGluIFtSRkM0NzIwXSBNVVNUIE5PVCBiZSB1c2VkLg0KDQoN
Cg0KDQoNCg0KDQoNCg0KDQoNCg0KDQoNCg0KDQoNCg0KDQoNCg0KDQoNCg0KDQoNCg0KDQoNCg0K
DQoNCg0KDQoNCg0KDQoNCg0KDQoNCg0KDQoNCg0KRGF2YXJpLCBldCBhbC4gICAgICAgICAgIEV4
cGlyZXMgQXVndXN0IDI3LCAyMDEzICAgICAgICAgICAgICAgW1BhZ2UgMjJdDQoMDQpJbnRlcm5l
dC1EcmFmdCAgICAgICAgVHJhbnNwb3J0aW5nIFRpbWluZyBvdmVyIE1QTFMgICAgICAgIEZlYnJ1
YXJ5IDIwMTMNCg0KDQoxNS4gIFVEUCBDaGVja3N1bSBDb3JyZWN0aW9uDQoNCiAgIEZvciBVRFAv
SVAgZW5jYXBzdWxhdGlvbiBtb2RlIG9mIFRpbWluZyBvdmVyIE1QTFMsIHRoZSBVRFAgY2hlY2tz
dW0NCiAgIG1heSBiZSByZXF1aXJlZCBhcyBwZXIgVURQIHRyYW5zcG9ydCBzdGFuZGFyZHMuDQoN
CiAgIFdoZW4gVURQIGNoZWNrc3VtIGlzIHVzZWQsIGVhY2ggVGltaW5nLWF3YXJlIExFUi9MU1Ig
bXVzdCBlaXRoZXINCiAgIGluY3JlbWVudGFsbHkgdXBkYXRlIHRoZSBVRFAgY2hlY2tzdW0gYWZ0
ZXIgVGltZSBzdGFtcGluZyBvcg0KICAgQ29ycmVjdGlvbiBGaWVsZCB1cGRhdGUgb3IgdmVyaWZ5
IHRoZSBVRFAgY2hlY2tzdW0gb24gcmVjZXB0aW9uIGZyb20NCiAgIHVwc3RyZWFtIGFuZCByZWNh
bGN1bGF0ZSB0aGUgY2hlY2tzdW0gY29tcGxldGVseSBvbiB0cmFuc21pc3Npb24gdG8NCiAgIGRv
d25zdHJlYW0gbm9kZSBhZnRlciBUaW1lIHN0YW1waW5nIG9yIENvcnJlY3Rpb24gRmllbGQgdXBk
YXRlLg0KDQoNCg0KDQoNCg0KDQoNCg0KDQoNCg0KDQoNCg0KDQoNCg0KDQoNCg0KDQoNCg0KDQoN
Cg0KDQoNCg0KDQoNCg0KDQoNCg0KDQoNCg0KDQoNCkRhdmFyaSwgZXQgYWwuICAgICAgICAgICBF
eHBpcmVzIEF1Z3VzdCAyNywgMjAxMyAgICAgICAgICAgICAgIFtQYWdlIDIzXQ0KDA0KSW50ZXJu
ZXQtRHJhZnQgICAgICAgIFRyYW5zcG9ydGluZyBUaW1pbmcgb3ZlciBNUExTICAgICAgICBGZWJy
dWFyeSAyMDEzDQoNCg0KMTYuICBSb3V0aW5nIGV4dGVuc2lvbnMgZm9yIFRpbWluZy1hd2FyZSBS
b3V0ZXJzDQoNCiAgIE1QTFMtVEUgcm91dGluZyByZWxpZXMgb24gZXh0ZW5zaW9ucyB0byBPU1BG
IFtSRkMyMzI4XSBbUkZDNTM0MF0gYW5kDQogICBJUy1JUyBbSVNPXSBbUkZDMTE5NV0gaW4gb3Jk
ZXIgdG8gYWR2ZXJ0aXNlIFRyYWZmaWMgRW5naW5lZXJpbmcgKFRFKQ0KICAgbGluayBpbmZvcm1h
dGlvbiB1c2VkIGZvciBjb25zdHJhaW50LWJhc2VkIHJvdXRpbmcuDQoNCiAgIEluZGVlZCwgaXQg
aXMgdXNlZnVsIHRvIGFkdmVydGlzZSBkYXRhIHBsYW5lIFRFIHJvdXRlciBsaW5rDQogICBjYXBh
YmlsaXRpZXMsIHN1Y2ggYXMgdGhlIGNhcGFiaWxpdHkgZm9yIGEgcm91dGVyIHRvIGJlIFRpbWlu
Zy1hd2FyZS4NCiAgIFRoaXMgY2FwYWJpbGl0eSBNVVNUIHRoZW4gYmUgdGFrZW4gaW50byBhY2Nv
dW50IGR1cmluZyBwYXRoDQogICBjb21wdXRhdGlvbiB0byBwcmVmZXIgb3IgZXZlbiByZXF1aXJl
IGxpbmtzIHRoYXQgYWR2ZXJ0aXNlIHRoZW1zZWx2ZXMNCiAgIGFzIFRpbWluZy1hd2FyZS4gIElu
IHRoaXMgd2F5IHRoZSBwYXRoIGNhbiBlbnN1cmUgdGhlIGVudHJ5IGFuZCBleGl0DQogICBwb2lu
dHMgaW50byB0aGUgTEVScyBhbmQsIGlmIGRlc2lyZWQsIHRoZSBsaW5rcyBpbnRvIHRoZSBMU1Jz
IGFyZQ0KICAgYWJsZSB0byBwZXJmb3JtIHBvcnQgYmFzZWQgdGltZS1zdGFtcGluZyB0aHVzIG1p
bmltaXppbmcgdGhlaXIgaW1wYWN0DQogICBvbiB0aGUgcGVyZm9ybWFuY2Ugb2YgdGhlIHNsYXZl
IGNsb2NrLg0KDQogICBleHRlbnNpb25zIGFyZSByZXF1aXJlZCB0byBPU1BGIGFuZCBJUy1JUyBp
biBvcmRlciB0byBhZHZlcnRpc2UNCiAgIFRpbWluZy1hd2FyZSBjYXBhYmlsaXRpZXMgb2YgYSBs
aW5rLiAgU3VjaCBleHRlbnNpb25zIGFyZSBvdXRzaWRlIHRoZQ0KICAgc2NvcGUgb2YgdGhpcyBk
b2N1bWVudDsgaG93ZXZlciBzdWNoIGV4dGVuc2lvbiBTSE9VTEQgYmUgYWJsZSB0bw0KICAgc2ln
bmFsIHRoZSBmb2xsb3dpbmcgaW5mb3JtYXRpb24gcGVyIFJvdXRlciBMaW5rOg0KDQogICBvICBD
YXBhYmxlIG9mIHByb2Nlc3NpbmcgUFRQLCBOVFAgb3Igb3RoZXIgVGltaW5nIGZsb3dzDQoNCiAg
IG8gIENhcGFibGUgb2YgcGVyZm9ybWluZyBUcmFuc3BhcmVudCBDbG9jayBvcGVyYXRpb24NCg0K
ICAgbyAgQ2FwYWJsZSBvZiBwZXJmb3JtaW5nIEJvdW5kYXJ5IENsb2NrIG9wZXJhdGlvbg0KDQoN
Cg0KDQoNCg0KDQoNCg0KDQoNCg0KDQoNCg0KDQoNCg0KDQoNCg0KDQoNCg0KDQoNCkRhdmFyaSwg
ZXQgYWwuICAgICAgICAgICBFeHBpcmVzIEF1Z3VzdCAyNywgMjAxMyAgICAgICAgICAgICAgIFtQ
YWdlIDI0XQ0KDA0KSW50ZXJuZXQtRHJhZnQgICAgICAgIFRyYW5zcG9ydGluZyBUaW1pbmcgb3Zl
ciBNUExTICAgICAgICBGZWJydWFyeSAyMDEzDQoNCg0KMTcuICBTaWduYWxpbmcgRXh0ZW5zaW9u
cyBmb3IgQ3JlYXRpbmcgVGltaW5nIExTUHMNCg0KICAgUlNWUC1URSBzaWduYWxpbmcgTUFZIGJl
IHVzZWQgdG8gc2V0dXAgdGhlIHRpbWluZyBMU1BzLiAgV2hlbiBSU1ZQLVRFDQogICBpcyB1c2Vk
IHRvIHNldHVwIFRpbWluZyBMU1BzLCBzb21lIGluZm9ybWF0aW9uIHRoYXQgaW5kaWNhdGVzIHRo
YXQNCiAgIHRoZSBMU1AgaXMgY2FycnlpbmcgVGltaW5nIGZsb3dzIE1VU1QgYmUgaW5jbHVkZWQg
aW4gdGhlIG5ldw0KICAgRXh0ZW5zaW9ucyB0byBSU1ZQLVRFOg0KDQogICBUaGUgZm9sbG93aW5n
IGluZm9ybWF0aW9uIE1BWSBhbHNvIGJlIGluY2x1ZGVkIGluIHRoZSBuZXcgRXh0ZW5zaW9ucw0K
ICAgdG8gUlNWUC1URToNCg0KICAgbyAgT2Zmc2V0IGZyb20gQm90dG9tIG9mIFN0YWNrIChCb1Mp
IHRvIHRoZSBzdGFydCBvZiB0aGUgVGltZS1zdGFtcA0KICAgICAgZmllbGQNCg0KICAgbyAgTnVt
YmVyIG9mIFZMQU5zIGluIGNhc2Ugb2YgUFcgZW5jYXBzdWxhdGlvbg0KDQogICBvICBUaW1lc3Rh
bXAgZmllbGQgVHlwZQ0KDQogICAgICAqICBDb3JyZWN0aW9uIEZpZWxkLCBUaW1lc3RhbXANCg0K
ICAgbyAgVGltZXN0YW1wIEZpZWxkIGZvcm1hdA0KDQogICAgICAqICA2NC1iaXQgUFRQdjEsIDgw
LWJpdCBQVFB2MiwgMzItYml0IE5UUCwgNjQtYml0IE5UUCwgMTI4LWJpdA0KICAgICAgICAgTlRQ
LCBldGMuDQoNCiAgIE5vdGUgdGhhdCBpbiBjYXNlIHRoZSBhYm92ZSBvcHRpb25hbCBpbmZvcm1h
dGlvbiBpcyBzaWduYWxlZCB3aXRoDQogICBSU1ZQLVRFIGZvciBhIFRpbWluZyBMU1AsIGFsbCB0
aGUgVGltaW5nIHBhY2tldHMgY2FycmllZCBpbiB0aGF0IExTUA0KICAgbXVzdCBoYXZlIHRoZSBz
YW1lIHNpZ25hbGVkIGNoYXJhY3RlcmlzdGljcy4gIEZvciBleGFtcGxlIGlmDQogICBUaW1lc3Rh
bXAgZm9ybWF0IGlzIHNpZ25hbGVkIGFzIDY0LWJpdCBQVFB2MSwgdGhlbiBhbGwgVGltaW5nIHBh
Y2tldHMNCiAgIG11c3QgdXNlIDY0LWJpdCBQVFB2MSB0aW1lLXN0YW1wLg0KDQoNCg0KDQoNCg0K
DQoNCg0KDQoNCg0KDQoNCg0KDQoNCg0KDQoNCg0KDQpEYXZhcmksIGV0IGFsLiAgICAgICAgICAg
RXhwaXJlcyBBdWd1c3QgMjcsIDIwMTMgICAgICAgICAgICAgICBbUGFnZSAyNV0NCgwNCkludGVy
bmV0LURyYWZ0ICAgICAgICBUcmFuc3BvcnRpbmcgVGltaW5nIG92ZXIgTVBMUyAgICAgICAgRmVi
cnVhcnkgMjAxMw0KDQoNCjE4LiAgQmVoYXZpb3Igb2YgTEVSL0xTUg0KDQogICBUaW1pbmctY2Fw
YWJsZS9hd2FyZSBMRVJzIGFuZCBMU1JzIGFyZSByb3V0ZXJzIHRoYXQgaGF2ZSBvbmUgb3IgbW9y
ZQ0KICAgaW50ZXJmYWNlcyB0aGF0IGNhbiBwZXJmb3JtIFRpbWluZyBvcGVyYXRpb25zIChPQy9C
Qy9UQykgb24gVGltaW5nDQogICBwYWNrZXRzIGFuZCBhcmUgY29uZmlndXJlZCB0byBkbyBzby4g
IFRpbWluZy1jYXBhYmxlL2F3YXJlIExFUnMgYW5kDQogICBMU1JzIGNhbiBhZHZlcnRpc2UgdGhl
aXIgVGltaW5nLWNhcGFiaWxpdHkgcGVyLWludGVyZmFjZSB2aWEgY29udHJvbA0KICAgcGxhbmUg
c3VjaCBhcyBPU1BGIG9yIElTLUlTLiAgVGhlIFRpbWluZy1jYXBhYmxlL2F3YXJlIExFUnMgY2Fu
IHRoZW4NCiAgIHNpZ25hbHMgVGltaW5nIExTUHMgdmlhIFJTVlAtVEUgc2lnbmFsaW5nLiAgQWx0
ZXJuYXRpdmVseSB0aGUgVGltaW5nDQogICBjYXBhYmlsaXR5IG9mIExFUiBhbmQgTFNScyBtYXkg
YmUgY29uZmlndXJlZCBpbiBhIGNlbnRyYWxpemVkDQogICBjb250cm9sbGVyIGFuZCB0aGUgVGlt
aW5nIExTUCBtYXkgYmUgc2V0dXAgdXNpbmcgbWFudWFsIGNvbmZpZ3VyYXRpb24NCiAgIG9yIG90
aGVyIG1ldGhvZHMgc3VjaCBhcyBTRE4uDQoNCjE4LjEuICBCZWhhdmlvciBvZiBUaW1pbmctY2Fw
YWJsZS9hd2FyZSBMRVINCg0KICAgV2hlbiBhIFRpbWluZy1jYXBhYmxlL2F3YXJlIExFUiBiZWhh
dmVzIGFzIGEgVHJhbnNwYXJlbnQgY2xvY2sgYW5kDQogICByZWNlaXZlcyBhIFRpbWluZyBtZXNz
YWdlIGZyb20gYSBUaW1pbmctY2FwYWJsZS9hd2FyZSBub24tTVBMUw0KICAgaW50ZXJmYWNlLCB0
aGUgTEVSIHVwZGF0ZXMgdGhlIENvcnJlY3Rpb24gRmllbGQgKENGKSBhbmQgZW5jYXBzdWxhdGVz
DQogICBhbmQgZm9yd2FyZHMgdGhlIHRpbWluZyBtZXNzYWdlIG92ZXIgcHJldmlvdXNseSBlc3Rh
Ymxpc2hlZCBUaW1pbmcNCiAgIExTUC4gIEFsc28gd2hlbiBhIFRpbWluZyBtZXNzYWdlIGlzIHJl
Y2VpdmVkIGZyb20gYSBUaW1pbmctY2FwYWJsZS8NCiAgIGF3YXJlIE1QTFMgaW50ZXJmYWNlLCBM
RVIgdXBkYXRlcyB0aGUgQ29ycmVjdGlvbiBGaWxlZCAoQ0YpIGFuZA0KICAgZGVjYXBzdWxhdGVz
IHRoZSBNUExTIGVuY2Fwc3VsYXRpb24gYW5kIGZvcndhcmRzIHRoZSB0aW1pbmcgbWVzc2FnZQ0K
ICAgdG8gYSBub24tTVBMUyBpbnRlcmZhY2UuDQoNCiAgIFdoZW4gYSBUaW1pbmctY2FwYWJsZS9h
d2FyZSBMRVIgYmVoYXZlcyBhcyBhIEJvdW5kYXJ5IGNsb2NrIGFuZA0KICAgcmVjZWl2ZXMgYSBU
aW1pbmcgbWVzc2FnZSBmcm9tIGEgVGltaW5nLWNhcGFibGUvYXdhcmUgbm9uIE1QTFMNCiAgIGlu
dGVyZmFjZSwgdGhlIExFUiBUaW1lc3RhbXBzIHRoZSBUaW1pbmcgcGFja2V0IGFuZCBzZW5kcyBp
dCB0byB0aGUNCiAgIExFUnMgQm91bmRhcnkgY2xvY2sgcHJvY2Vzc2luZyBtb2R1bGUuICBBbHNv
IHdoZW4gYSBUaW1pbmcgbWVzc2FnZSBpcw0KICAgcmVjZWl2ZWQgZnJvbSBhIFRpbWluZy0gY2Fw
YWJsZS9hd2FyZSBNUExTIGludGVyZmFjZSwgdGhlIExFUg0KICAgVGltZXN0YW1wcyB0aGUgVGlt
aW5nIHBhY2tldCBhbmQgc2VuZHMgaXQgdG8gdGhlIExFUnMgQm91bmRhcnkgY2xvY2sNCiAgIHBy
b2Nlc3NpbmcgbW9kdWxlLg0KDQogICBXaGVuIGEgVGltaW5nLWNhcGFibGUvYXdhcmUgTEVSIGJl
aGF2ZXMgYXMgYW4gT3JkaW5hcnkgQ2xvY2sgdG93YXJkDQogICB0aGUgTVBMUyBuZXR3b3JrLCBh
bmQgcmVjZWl2ZXMgYSBUaW1pbmcgbWVzc2FnZSBmcm9tIGEgVGltaW5nLQ0KICAgY2FwYWJsZS9h
d2FyZSBNUExTIGludGVyZmFjZSwgdGhlIExFUiBUaW1lc3RhbXBzIHRoZSBUaW1pbmcgcGFja2V0
DQogICBhbmQgc2VuZHMgaXQgdG8gdGhlIExFUnMgT3JkaW5hcnkgY2xvY2sgcHJvY2Vzc2luZyBt
b2R1bGUuDQoNCjE4LjIuICBCZWhhdmlvciBvZiBUaW1pbmctY2FwYWJsZS9hd2FyZSBMU1INCg0K
ICAgV2hlbiBhIFRpbWluZy1jYXBhYmxlL2F3YXJlIExTUiBiZWhhdmVzIGFzIGEgVHJhbnNwYXJl
bnQgY2xvY2sgYW5kDQogICByZWNlaXZlcyBhIFRpbWluZyBtZXNzYWdlIGZyb20gYSBUaW1pbmct
Y2FwYWJsZS9hd2FyZSBNUExTIGludGVyZmFjZS4NCiAgIFRoZSBMU1IgdXBkYXRlcyB0aGUgQ29y
cmVjdGlvbiBGaWxlZCAoQ0YpIGFuZCBmb3J3YXJkcyB0aGUgdGltaW5nDQogICBtZXNzYWdlIG92
ZXIgYW5vdGhlciBNUExTIGludGVyZmFjZS4NCiAgIA0KICAgV2hlbiBhIFRpbWluZy1jYXBhYmxl
L2F3YXJlIExTUiBiZWhhdmVzIGFzIGEgQm91bmRhcnkgY2xvY2sgYW5kDQogICByZWNlaXZlcyBh
IFRpbWluZyBtZXNzYWdlIGZyb20gYSBUaW1pbmctY2FwYWJsZS9hd2FyZSBNUExTIGludGVyZmFj
ZS4NCiAgIFRoZSBMU1IgcGVyZm9ybXMgdGhlIGZ1bmN0aW9ucyBvZiBhIEJvdW5kYXJ5IENsb2Nr
IGluIHRlcm1pbmF0aW5nDQogICB0aGUgcmVjZWl2ZWQgVGltaW5nIG1lc3NhZ2UgYW5kIHJlLWdl
bmVyYXRpbmcgYSBuZXcgdGltaW5nIG1lc3NhZ2UNCiAgIG92ZXIgYW5vdGhlciAob3IgdGhlIHNh
bWUpIE1QTFMgaW50ZXJmYWNlLg0KDQoxOC4zLiAgQmVoYXZpb3Igb2Ygbm9uLVRpbWluZy1jYXBh
YmxlL2F3YXJlIExTUg0KDQogICBJdCBpcyBtb3N0IGJlbmVmaWNpYWwgd2hlbiBhbGwgTFNScyBp
biB0aGUgcGF0aCBvZiBhIFRpbWluZyBMU1AgYmUNCiAgIHRpbWluZy1DYXBhYmxlL2F3YXJlIExT
UnMuICBUaGlzIHdvdWxkIGVuc3VyZSB0aGUgaGlnaGVzdCBxdWFsaXR5DQogICB0aW1lIGFuZCBj
bG9jayBzeW5jaHJvbml6YXRpb24gYnkgVGltaW5nIFNsYXZlIENsb2Nrcy4gIEhvd2V2ZXIsIHRo
aXMNCg0KDQoNCkRhdmFyaSwgZXQgYWwuICAgICAgICAgICBFeHBpcmVzIEF1Z3VzdCAyNywgMjAx
MyAgICAgICAgICAgICAgIFtQYWdlIDI2XQ0KDA0KSW50ZXJuZXQtRHJhZnQgICAgICAgIFRyYW5z
cG9ydGluZyBUaW1pbmcgb3ZlciBNUExTICAgICAgICBGZWJydWFyeSAyMDEzDQoNCg0KICAgc3Bl
Y2lmaWNhdGlvbiBkb2VzIG5vdCBtYW5kYXRlIHRoYXQgYWxsIExTUnMgaW4gcGF0aCBvZiBhIFRp
bWluZyBMU1ANCiAgIGJlIFRpbWluZy0gY2FwYWJsZS9hd2FyZS4NCg0KICAgTm9uLVRpbWluZy1j
YXBhYmxlL2F3YXJlIExTUnMganVzdCBzd2l0Y2ggdGhlIHBhY2tldHMgZW5jYXBzdWxhdGVkIGlu
DQogICBUaW1pbmcgTFNQcyBhbmQgZG9udCBwZXJmb3JtIGFueSBUaW1pbmcgb3BlcmF0aW9uIChU
QyBvciBCQykuICBIb3dldmVyDQogICBhcyBleHBsYWluZWQgaW4gUW9TIHNlY3Rpb24gdGhlIFRp
bWluZzggb3ZlciBNUExTIHBhY2tldHMgTVVTVCBiZSBzdGlsbA0KICAgYmUgdHJlYXRlZCB3aXRo
IHRoZSBoaWdoZXN0IHByaW9yaXR5IGJhc2VkIG9uIHRoZWlyIFRyYWZmaWMgQ2xhc3MNCiAgIChU
QykgbWFya2luZy4NCg0KDQoNCg0KDQoNCg0KDQoNCg0KDQoNCg0KDQoNCg0KDQoNCg0KDQoNCg0K
DQoNCg0KDQoNCg0KDQoNCg0KDQoNCg0KDQoNCg0KDQoNCg0KDQoNCg0KRGF2YXJpLCBldCBhbC4g
ICAgICAgICAgIEV4cGlyZXMgQXVndXN0IDI3LCAyMDEzICAgICAgICAgICAgICAgW1BhZ2UgMjdd
DQoMDQpJbnRlcm5ldC1EcmFmdCAgICAgICAgVHJhbnNwb3J0aW5nIFRpbWluZyBvdmVyIE1QTFMg
ICAgICAgIEZlYnJ1YXJ5IDIwMTMNCg0KDQoxOS4gIE90aGVyIGNvbnNpZGVyYXRpb25zDQoNCiAg
IFtJRUVFXSBkZWZpbmVzIGFuIG9wdGlvbmFsIHBlZXItdG8tcGVlciBUcmFuc3BhcmVudCBjbG9j
a2luZyB0aGF0DQogICByZXF1aXJlcyBwZWVyIGRlbGF5IG1lYXN1cmVtZW50IGJldHdlZW4gdHdv
IGFkamFjZW50IFRpbWluZy1jYXBhYmxlLw0KICAgYXdhcmUgcm91dGVycy9zd2l0Y2hlcy4gIFBl
ZXIgZGVsYXkgbWVhc3VyZW1lbnQgbWVzc2FnZXMgbmVlZCB0byBiZQ0KICAgdGltZSBzdGFtcGVk
IGFuZCB0ZXJtaW5hdGVkIGJ5IHRoZSBUaW1pbmctY2FwYWJsZS9hd2FyZSByb3V0ZXJzLw0KICAg
c3dpdGNoZXMuICBUaGlzIG1lYW5zIHRoYXQgdHdvIGFkamFjZW50IExTUnMgbWF5IGJlIGVuZ2Fn
ZWQgaW4gYSBwZWVyDQogICBkZWxheSBtZWFzdXJlbWVudC4NCg0KICAgRm9yIHRyYW5zcG9ydGlu
ZyBzdWNoIHBlZXIgZGVsYXkgbWVhc3VyZW1lbnQgbWVzc2FnZXMgYSBzaW5nbGUtaG9wDQogICBM
U1AgU0hPVUxEIHRvIGJlIGNyZWF0ZWQgYmV0d2VlbiB0aGUgdHdvIGFkamFjZW50IExTUnMgZW5n
YWdlZCBpbg0KICAgcGVlciBkZWxheSBtZWFzdXJlbWVudCB0byBjYXJyeSBwZWVyIGRlbGF5IG1l
YXN1cmVtZW50IG1lc3NhZ2VzLg0KICAgT3RoZXIgbWV0aG9kcyBzdWNoIGFzIFBUUCB0cmFuc3Bv
cnQgb3ZlciBFdGhlcm5ldCBNQVkgYmUgdXNlZCBmb3INCiAgIHRyYW5zcG9ydGluZyBwZWVyIGRl
bGF5IG1lYXN1cmVtZW50IG1lc3NhZ2VzIGlmIHRoZSBsaW5rIGJldHdlZW4gdGhlDQogICB0d28g
cm91dGVycyBpcyBFdGhlcm5ldC4gIA0KICAgDQogICBMaWtld2lzZSBmb3IgQkNzIGVtYmVkZGVk
IGluIGFuIExTUiwgYSBzaW5nbGUtaG9wIExTUCBTSE9VTEQgYmUgDQogICBjcmVhdGVkIGJldHdl
ZW4gdGhlIHR3byBhZGphY2VudCBMU1JzIHRoYXQgYXJlIGFjdGluZyBhcyBCQ3MuICBPdGhlcg0K
ICAgbWV0aG9kcyBzdWNoIGFzIFBUUCB0cmFuc3BvcnQgb3ZlciBFdGhlcm5ldCBNQVkgYmUgdXNl
ZCBpZiB0aGUgbGluaw0KICAgYmV0d2VlbiB0aGUgdHdvIHJvdXRlcnMgaXMgRXRoZXJuZXQuICAN
CiAgIA0KDQogICBJbiBQZWVyLXRvLXBlZXIgdHJhbnNwYXJlbnQgY2xvY2tpbmcgKFAyUCBUQyks
IGEgVGltaW5nLWNhcGFibGUvIHdhcmUNCiAgIHJvdXRlcnMvc3dpdGNoZXMgTVVTVCBtYWludGFp
biBhIGxpc3Qgb2YgYWxsIHRoZSBuZWlnaGJvcnMgaXQgbmVlZHMNCiAgIHRvIHNlbmQgYSBQRGVs
YXlfUmVxIHRvLCB3aGVyZSBlYWNoIG5laWdoYm9yIGNvcnJlc3BvbmRzIHRvIGEgdGltaW5nDQog
ICBMU1AuDQoNCiAgIFRoZSB1c2Ugb2YgRXhwbGljaXQgTnVsbCBMYWJlbCAoTGFiZWw9IDAgb3Ig
MikgaXMgYWNjZXB0YWJsZSBhcyBsb25nDQogICBhcyBlaXRoZXIgdGhlIEV4cGxpY2l0IE51bGwg
bGFiZWwgaXMgdGhlIGJvdHRvbSBvZiBzdGFjayBsYWJlbA0KICAgKGFwcGxpY2FibGUgb25seSB0
byBVRFAvSVAgZW5jYXBzdWxhdGlvbikgb3IgdGhlIGxhYmVsIGJlbG93IHRoZQ0KICAgRXhwbGlj
aXQgTnVsbCBsYWJlbCBpcyBhIFBUUCBsYWJlbC4NCg0KDQoNCg0KDQoNCg0KDQoNCg0KDQoNCg0K
DQoNCg0KDQoNCg0KDQoNCg0KDQoNCg0KDQpEYXZhcmksIGV0IGFsLiAgICAgICAgICAgRXhwaXJl
cyBBdWd1c3QgMjcsIDIwMTMgICAgICAgICAgICAgICBbUGFnZSAyOF0NCgwNCkludGVybmV0LURy
YWZ0ICAgICAgICBUcmFuc3BvcnRpbmcgVGltaW5nIG92ZXIgTVBMUyAgICAgICAgRmVicnVhcnkg
MjAxMw0KDQoNCjIwLiAgU2VjdXJpdHkgQ29uc2lkZXJhdGlvbnMNCg0KICAgTVBMUyBQVyBzZWN1
cml0eSBjb25zaWRlcmF0aW9ucyBpbiBnZW5lcmFsIGFyZSBkaXNjdXNzZWQgaW4gW1JGQzM5ODVd
DQogICBhbmQgW1JGQzQ0NDddLGFuZCB0aG9zZSBjb25zaWRlcmF0aW9ucyBhbHNvIGFwcGx5IHRv
IHRoaXMgZG9jdW1lbnQuDQoNCiAgIEFuIGV4cGVyaW1lbnRhbCBzZWN1cml0eSBwcm90b2NvbCBp
cyBkZWZpbmVkIGluIFtJRUVFXS5UaGUgUFRQDQogICBzZWN1cml0eSBleHRlbnNpb24gYW5kIHBy
b3RvY29sIHByb3ZpZGVzIGdyb3VwIHNvdXJjZSBhdXRoZW50aWNhdGlvbiwNCiAgIG1lc3NhZ2Ug
aW50ZWdyaXR5LCBhbmQgcmVwbGF5IGF0dGFjayBwcm90ZWN0aW9uIGZvciBQVFAgbWVzc2FnZXMu
DQoNCiAgIFdoZW4gdGhlIE1QTFMgbmV0d29yayAocHJvdmlkZXIgbmV0d29yaykgc2VydmVzIG11
bHRpcGxlIGN1c3RvbWVycywNCiAgIGl0IGlzIGltcG9ydGFudCB0byBtYWludGFpbiBhbmQgcHJv
Y2VzcyBlYWNoIGN1c3RvbWVycyBjbG9jayBhbmQNCiAgIFRpbWluZyBtZXNzYWdlcyBzZXBhcmF0
ZWx5IGZyb20gb3RoZXIgY3VzdG9tZXJzIHRvIGVuc3VyZSB0aGVyZSBpcyBubw0KICAgY3Jvc3Mt
IGN1c3RvbWVyIGVmZmVjdC4NCiAgIA0KICAgVGltaW5nIG1lc3NhZ2VzIChhcyBvcHBvc2VkIHRv
IHJlZ3VsYXIgY3VzdG9tZXIgZGF0YSkgU0hPVUxEIG5vdCBiZQ0KICAgZW5jcnlwdGVkIG9yIGF1
dGhlbnRpY2F0ZWQgb24gYW4gZW5kLXRvLWVuZCBiYXNpcy4gIEFsdGVybmF0aXZlbHksDQogICBh
dXRoZW50aWNhdGlvbi9pbnRlZ3JpdHkgdmVyaWZpY2F0aW9uIG1lY2hhbmlzbSBjYW4gYmUgdXNl
ZCBieSBhDQogICBzaGFyZWQgc2VjcmV0IGJldHdlZW4gdGhlIGN1c3RvbWVyIGFuZCBwcm92aWRl
ciBub2Rlcy4NCg0KDQoNCg0KDQoNCg0KDQoNCg0KDQoNCg0KDQoNCg0KDQoNCg0KDQoNCg0KDQoN
Cg0KDQoNCg0KDQoNCkRhdmFyaSwgZXQgYWwuICAgICAgICAgICBFeHBpcmVzIEF1Z3VzdCAyNywg
MjAxMyAgICAgICAgICAgICAgIFtQYWdlIDI5XQ0KDA0KSW50ZXJuZXQtRHJhZnQgICAgICAgIFRy
YW5zcG9ydGluZyBUaW1pbmcgb3ZlciBNUExTICAgICAgICBGZWJydWFyeSAyMDEzDQoNCg0KMjEu
ICBBcHBsaWNhYmlsaXR5IFN0YXRlbWVudA0KDQogICBUaGUgVGltaW5nIG92ZXIgTVBMUyB0cmFu
c3BvcnQgbWV0aG9kcyBkZXNjcmliZWQgaW4gdGhpcyBkb2N1bWVudA0KICAgYXBwbHkgdG8gdGhl
IGZvbGxvd2luZyBuZXR3b3JrIEVsZW1lbnRzOg0KDQogICBvICBBbiBMRVIgcmVjZWl2ZXMgSVAg
b3IgRXRoZXJuZXQgRW5jYXBzdWxhdGVkIFRpbWluZyBtZXNzYWdlcyBmcm9tIGENCiAgICAgIG5v
bi1NUExTIGludGVyZmFjZSBhbmQgZm9yd2FyZHMgdGhlbSBhcyBNUExTIGVuY2Fwc3VsYXRlZCBU
aW1pbmcNCiAgICAgIG1lc3NhZ2VzIG92ZXIgVGltaW5nIExTUCwgd2hpbGUgcGVyZm9ybWluZyBU
cmFuc3BhcmVudCBDbG9jaw0KICAgICAgZnVuY3Rpb25hbGl0eQ0KDQogICBvICBBbiBMRVIgcmVj
ZWl2ZXMgTVBMUyBlbmNhcHN1bGF0ZWQgVGltaW5nIG1lc3NhZ2VzIGZyb20gYSBUaW1pbmcNCiAg
ICAgIExTUCBhbmQgZm9yd2FyZHMgdGhlbSB0byBub24tTVBMUyBpbnRlcmZhY2UgYXMgSVAgb3Ig
RXRoZXJuZXQNCiAgICAgIEVuY2Fwc3VsYXRlZCBUaW1pbmcgbWVzc2FnZXMsIHdoaWxlIHBlcmZv
cm1pbmcgVHJhbnNwYXJlbnQgQ2xvY2sNCiAgICAgIGZ1bmN0aW9uYWxpdHkNCg0KICAgbyAgQW4g
TEVSIHJlY2VpdmVzIElQIG9yIEV0aGVybmV0IGVuY2Fwc3VsYXRlZCBUaW1pbmcgbWVzc2FnZXMg
ZnJvbSBhDQogICAgICBub24tTVBMUyBpbnRlcmZhY2UgYW5kIHRlcm1pbmF0ZXMgdGhlbSwgd2hp
bGUgcGVyZm9ybWluZyB0aGUgT0Mgb3INCiAgICAgIEJDIGZ1bmN0aW9uYWxpdHkNCg0KICAgbyAg
QW4gTEVSIHJlY2VpdmVzIE1QTFMgZW5jYXBzdWxhdGVkIFRpbWluZyBtZXNzYWdlcyBmcm9tIGEg
VGltaW5nDQogICAgICBMU1AgYW5kIHRlcm1pbmF0ZXMgdGhlbSwgd2hpbGUgcGVyZm9ybWluZyB0
aGUgT0Mgb3IgQkMNCiAgICAgIGZ1bmN0aW9uYWxpdHkNCg0KICAgbyAgQW4gTFNSIHJlY2VpdmVz
IE1QTFMgZW5jYXBzdWxhdGVkIFRpbWluZyBtZXNzYWdlcyBmcm9tIGEgVGltaW5nDQogICAgICBM
U1AgYW5kIGZvcndhcmRzIHRoZW0gdG8gYW5vdGhlciBNUExTIGludGVyZmFjZSwgd2hpbGUgcGVy
Zm9ybWluZw0KICAgICAgdGhlIFRDIGZ1bmN0aW9uYWxpdHkNCg0KICAgbyAgQW4gTFNSIHJlY2Vp
dmVzIE1QTFMgZW5jYXBzdWxhdGVkIFRpbWluZyBtZXNzYWdlcyBmcm9tIGEgVGltaW5nDQogICAg
ICBMU1AgYW5kIHRlcm1pbmF0ZXMgdGhlbSwgd2hpbGUgcGVyZm9ybWluZyB0aGUgT0Mgb3IgQkMN
CiAgICAgIGZ1bmN0aW9uYWxpdHkuDQogICAgICANCiAgIFRoaXMgZG9jdW1lbnQgYWxzbyBzdXBw
b3J0cyB0aGUgY2FzZSB3aGVyZSBub3QgYWxsIExTUnMgYXJlIFRpbWluZy0NCiAgIGNhcGFibGUv
YXdhcmUuICBJdCBhbHNvIHN1cHBvcnRzIHRoZSBjYXNlIHdoZXJlIG5vdCBhbGwgTEVSL0xTUg0K
ICAgaW50ZXJmYWNlcyBhcmUgVGltaW5nLWNhcGFibGUvYXdhcmUuDQoNCg0KDQoNCg0KDQoNCg0K
DQoNCg0KDQoNCg0KDQoNCg0KDQoNCg0KDQoNCg0KDQoNCkRhdmFyaSwgZXQgYWwuICAgICAgICAg
ICBFeHBpcmVzIEF1Z3VzdCAyNywgMjAxMyAgICAgICAgICAgICAgIFtQYWdlIDMwXQ0KDA0KSW50
ZXJuZXQtRHJhZnQgICAgICAgIFRyYW5zcG9ydGluZyBUaW1pbmcgb3ZlciBNUExTICAgICAgICBG
ZWJydWFyeSAyMDEzDQoNCg0KMjIuICBBY2tub3dsZWRnZW1lbnRzDQoNCiAgIFRoZSBhdXRob3Jz
IHdvdWxkIGxpa2UgdG8gdGhhbmsgTHVjYSBNYXJ0aW5pLCBSb24gQ29oZW4sIFlhYWtvdg0KICAg
U3RlaW4sIFRhbCBNaXpyYWhpLCBTdGVmYW5vIFJ1ZmZpbmksIEx1Y2EgTW9uaXRpIGFuZCBvdGhl
ciBtZW1iZXJzIG9mDQogICBJRVRGIGZvciByZXZpZXdpbmcgYW5kIHByb3ZpZGluZyBmZWVkYmFj
ayBvbiB0aGlzIGRyYWZ0Lg0KDQoNCg0KDQoNCg0KDQoNCg0KDQoNCg0KDQoNCg0KDQoNCg0KDQoN
Cg0KDQoNCg0KDQoNCg0KDQoNCg0KDQoNCg0KDQoNCg0KDQoNCg0KDQoNCg0KDQoNCg0KDQpEYXZh
cmksIGV0IGFsLiAgICAgICAgICAgRXhwaXJlcyBBdWd1c3QgMjcsIDIwMTMgICAgICAgICAgICAg
ICBbUGFnZSAzMV0NCgwNCkludGVybmV0LURyYWZ0ICAgICAgICBUcmFuc3BvcnRpbmcgVGltaW5n
IG92ZXIgTVBMUyAgICAgICAgRmVicnVhcnkgMjAxMw0KDQoNCjIzLiAgSUFOQSBDb25zaWRlcmF0
aW9ucw0KDQogICBUaGVyZSBhcmUgbm8gSUFOQSByZXF1aXJlbWVudHMgaW4gdGhpcyBzcGVjaWZp
Y2F0aW9uLg0KDQoNCg0KDQoNCg0KDQoNCg0KDQoNCg0KDQoNCg0KDQoNCg0KDQoNCg0KDQoNCg0K
DQoNCg0KDQoNCg0KDQoNCg0KDQoNCg0KDQoNCg0KDQoNCg0KDQoNCg0KDQoNCg0KRGF2YXJpLCBl
dCBhbC4gICAgICAgICAgIEV4cGlyZXMgQXVndXN0IDI3LCAyMDEzICAgICAgICAgICAgICAgW1Bh
Z2UgMzJdDQoMDQpJbnRlcm5ldC1EcmFmdCAgICAgICAgVHJhbnNwb3J0aW5nIFRpbWluZyBvdmVy
IE1QTFMgICAgICAgIEZlYnJ1YXJ5IDIwMTMNCg0KDQoyNC4gIFJlZmVyZW5jZXMNCg0KMjQuMS4g
IE5vcm1hdGl2ZSBSZWZlcmVuY2VzDQoNCiAgIFtJRUVFXSAgICAgSUVFRSAxNTg4LTIwMDgsICJJ
RUVFIFN0YW5kYXJkIGZvciBhIFByZWNpc2lvbiBDbG9jaw0KICAgICAgICAgICAgICBTeW5jaHJv
bml6YXRpb24gUHJvdG9jb2wgZm9yIE5ldHdvcmtlZCBNZWFzdXJlbWVudCBhbmQNCiAgICAgICAg
ICAgICAgQ29udHJvbCBTeXN0ZW1zIi4NCg0KICAgW1JGQzIxMTldICBCcmFkbmVyLCBTLiwgIktl
eSB3b3JkcyBmb3IgdXNlIGluIFJGQ3MgdG8gSW5kaWNhdGUNCiAgICAgICAgICAgICAgUmVxdWly
ZW1lbnQgTGV2ZWxzIiwgQkNQIDE0LCBSRkMgMjExOSwgTWFyY2ggMTk5Ny4NCg0KICAgW1JGQzM5
ODVdICBCcnlhbnQsIFMuIGFuZCBQLiBQYXRlLCAiUHNldWRvIFdpcmUgRW11bGF0aW9uIEVkZ2Ut
dG8tDQogICAgICAgICAgICAgIEVkZ2UgKFBXRTMpIEFyY2hpdGVjdHVyZSIsIFJGQyAzOTg1LCBN
YXJjaCAyMDA1Lg0KDQogICBbUkZDNDM4OV0gIFRoYWxlciwgRC4sIFRhbHdhciwgTS4sIGFuZCBD
LiBQYXRlbCwgIk5laWdoYm9yIERpc2NvdmVyeQ0KICAgICAgICAgICAgICBQcm94aWVzIChORCBQ
cm94eSkiLCBSRkMgNDM4OSwgQXByaWwgMjAwNi4NCg0KICAgW1JGQzQ0NDddICBNYXJ0aW5pLCBM
LiwgUm9zZW4sIEUuLCBFbC1BYXdhciwgTi4sIFNtaXRoLCBULiwgYW5kIEcuDQogICAgICAgICAg
ICAgIEhlcm9uLCAiUHNldWRvd2lyZSBTZXR1cCBhbmQgTWFpbnRlbmFuY2UgVXNpbmcgdGhlIExh
YmVsDQogICAgICAgICAgICAgIERpc3RyaWJ1dGlvbiBQcm90b2NvbCAoTERQKSIsIFJGQyA0NDQ3
LCBBcHJpbCAyMDA2Lg0KDQogICBbUkZDNDQ0OF0gIE1hcnRpbmksIEwuLCBSb3NlbiwgRS4sIEVs
LUFhd2FyLCBOLiwgYW5kIEcuIEhlcm9uLA0KICAgICAgICAgICAgICAiRW5jYXBzdWxhdGlvbiBN
ZXRob2RzIGZvciBUcmFuc3BvcnQgb2YgRXRoZXJuZXQgb3ZlciBNUExTDQogICAgICAgICAgICAg
IE5ldHdvcmtzIiwgUkZDIDQ0NDgsIEFwcmlsIDIwMDYuDQoNCiAgIFtSRkM0NzIwXSAgTWFsaXMs
IEEuLCBBbGxhbiwgRC4sIGFuZCBOLiBEZWwgUmVnbm8sICJQc2V1ZG93aXJlDQogICAgICAgICAg
ICAgIEVtdWxhdGlvbiBFZGdlLXRvLUVkZ2UgKFBXRTMpIEZyYW1lIENoZWNrIFNlcXVlbmNlDQog
ICAgICAgICAgICAgIFJldGVudGlvbiIsIFJGQyA0NzIwLCBOb3ZlbWJlciAyMDA2Lg0KDQogICBb
UkZDNTA4NV0gIE5hZGVhdSwgVC4gYW5kIEMuIFBpZ25hdGFybywgIlBzZXVkb3dpcmUgVmlydHVh
bCBDaXJjdWl0DQogICAgICAgICAgICAgIENvbm5lY3Rpdml0eSBWZXJpZmljYXRpb24gKFZDQ1Yp
OiBBIENvbnRyb2wgQ2hhbm5lbCBmb3INCiAgICAgICAgICAgICAgUHNldWRvd2lyZXMiLCBSRkMg
NTA4NSwgRGVjZW1iZXIgMjAwNy4NCg0KICAgW1JGQzU4ODBdICBLYXR6LCBELiBhbmQgRC4gV2Fy
ZCwgIkJpZGlyZWN0aW9uYWwgRm9yd2FyZGluZyBEZXRlY3Rpb24NCiAgICAgICAgICAgICAgKEJG
RCkiLCBSRkMgNTg4MCwgSnVuZSAyMDEwLg0KDQogICBbUkZDNTg4NF0gIEFnZ2Fyd2FsLCBSLiwg
S29tcGVsbGEsIEsuLCBOYWRlYXUsIFQuLCBhbmQgRy4gU3dhbGxvdywNCiAgICAgICAgICAgICAg
IkJpZGlyZWN0aW9uYWwgRm9yd2FyZGluZyBEZXRlY3Rpb24gKEJGRCkgZm9yIE1QTFMgTGFiZWwN
CiAgICAgICAgICAgICAgU3dpdGNoZWQgUGF0aHMgKExTUHMpIiwgUkZDIDU4ODQsIEp1bmUgMjAx
MC4NCg0KMjQuMi4gIEluZm9ybWF0aXZlIFJlZmVyZW5jZXMNCg0KICAgW0ktRC5pZXRmLXB3ZTMt
ZmF0LXB3XQ0KICAgICAgICAgICAgICBCcnlhbnQsIFMuLCBGaWxzZmlscywgQy4sIERyYWZ6LCBV
LiwgS29tcGVsbGEsIFYuLCBSZWdhbiwNCiAgICAgICAgICAgICAgSi4sIGFuZCBTLiBBbWFudGUs
ICJGbG93IEF3YXJlIFRyYW5zcG9ydCBvZiBQc2V1ZG93aXJlcw0KICAgICAgICAgICAgICBvdmVy
IGFuIE1QTFMgUGFja2V0IFN3aXRjaGVkIE5ldHdvcmsiLA0KICAgICAgICAgICAgICBkcmFmdC1p
ZXRmLXB3ZTMtZmF0LXB3LTA3ICh3b3JrIGluIHByb2dyZXNzKSwgSnVseSAyMDExLg0KDQoNCg0K
DQpEYXZhcmksIGV0IGFsLiAgICAgICAgICAgRXhwaXJlcyBBdWd1c3QgMjcsIDIwMTMgICAgICAg
ICAgICAgICBbUGFnZSAzM10NCgwNCkludGVybmV0LURyYWZ0ICAgICAgICBUcmFuc3BvcnRpbmcg
VGltaW5nIG92ZXIgTVBMUyAgICAgICAgRmVicnVhcnkgMjAxMw0KDQoNCiAgIFtJU09dICAgICAg
SVNPL0lFQyAxMDU4OToxOTkyLCAiSW50ZXJtZWRpYXRlIHN5c3RlbSB0byBJbnRlcm1lZGlhdGUN
CiAgICAgICAgICAgICAgc3lzdGVtIHJvdXRlaW5nIGluZm9ybWF0aW9uIGV4Y2hhbmdlIHByb3Rv
Y29sIGZvciB1c2UgaW4NCiAgICAgICAgICAgICAgY29uanVuY3Rpb24gd2l0aCB0aGUgUHJvdG9j
b2wgZm9yIHByb3ZpZGluZyB0aGUNCiAgICAgICAgICAgICAgQ29ubmVjdGlvbmxlc3MtbW9kZSBO
ZXR3b3JrIFNlcnZpY2UgKElTTyA4NDczKSIuDQoNCiAgIFtSRkMxMTk1XSAgQ2FsbG9uLCBSLiwg
IlVzZSBvZiBPU0kgSVMtSVMgZm9yIHJvdXRpbmcgaW4gVENQL0lQIGFuZA0KICAgICAgICAgICAg
ICBkdWFsIGVudmlyb25tZW50cyIsIFJGQyAxMTk1LCBEZWNlbWJlciAxOTkwLg0KDQogICBbUkZD
MjMyOF0gIE1veSwgSi4sICJPU1BGIFZlcnNpb24gMiIsIFNURCA1NCwgUkZDIDIzMjgsIEFwcmls
IDE5OTguDQoNCiAgIFtSRkMyNjk3XSAgSGVpbmFuZW4sIEouIGFuZCBSLiBHdWVyaW4sICJBIFNp
bmdsZSBSYXRlIFRocmVlIENvbG9yDQogICAgICAgICAgICAgIE1hcmtlciIsIFJGQyAyNjk3LCBT
ZXB0ZW1iZXIgMTk5OS4NCg0KICAgW1JGQzMyNDZdICBEYXZpZSwgQi4sIENoYXJueSwgQS4sIEJl
bm5ldCwgSi4sIEJlbnNvbiwgSy4sIExlIEJvdWRlYywNCiAgICAgICAgICAgICAgSi4sIENvdXJ0
bmV5LCBXLiwgRGF2YXJpLCBTLiwgRmlyb2l1LCBWLiwgYW5kIEQuDQogICAgICAgICAgICAgIFN0
aWxpYWRpcywgIkFuIEV4cGVkaXRlZCBGb3J3YXJkaW5nIFBIQiAoUGVyLUhvcA0KICAgICAgICAg
ICAgICBCZWhhdmlvcikiLCBSRkMgMzI0NiwgTWFyY2ggMjAwMi4NCg0KICAgW1JGQzM2MzBdICBL
YXR6LCBELiwgS29tcGVsbGEsIEsuLCBhbmQgRC4gWWV1bmcsICJUcmFmZmljIEVuZ2luZWVyaW5n
DQogICAgICAgICAgICAgIChURSkgRXh0ZW5zaW9ucyB0byBPU1BGIFZlcnNpb24gMiIsIFJGQyAz
NjMwLA0KICAgICAgICAgICAgICBTZXB0ZW1iZXIgMjAwMy4NCg0KICAgW1JGQzM3ODRdICBTbWl0
LCBILiBhbmQgVC4gTGksICJJbnRlcm1lZGlhdGUgU3lzdGVtIHRvIEludGVybWVkaWF0ZQ0KICAg
ICAgICAgICAgICBTeXN0ZW0gKElTLUlTKSBFeHRlbnNpb25zIGZvciBUcmFmZmljIEVuZ2luZWVy
aW5nIChURSkiLA0KICAgICAgICAgICAgICBSRkMgMzc4NCwgSnVuZSAyMDA0Lg0KDQogICBbUkZD
NDk3MF0gIExpbmRlbSwgQS4sIFNoZW4sIE4uLCBWYXNzZXVyLCBKUC4sIEFnZ2Fyd2FsLCBSLiwg
YW5kIFMuDQogICAgICAgICAgICAgIFNoYWZmZXIsICJFeHRlbnNpb25zIHRvIE9TUEYgZm9yIEFk
dmVydGlzaW5nIE9wdGlvbmFsDQogICAgICAgICAgICAgIFJvdXRlciBDYXBhYmlsaXRpZXMiLCBS
RkMgNDk3MCwgSnVseSAyMDA3Lg0KDQogICBbUkZDNDk3MV0gIFZhc3NldXIsIEpQLiwgU2hlbiwg
Ti4sIGFuZCBSLiBBZ2dhcndhbCwgIkludGVybWVkaWF0ZQ0KICAgICAgICAgICAgICBTeXN0ZW0g
dG8gSW50ZXJtZWRpYXRlIFN5c3RlbSAoSVMtSVMpIEV4dGVuc2lvbnMgZm9yDQogICAgICAgICAg
ICAgIEFkdmVydGlzaW5nIFJvdXRlciBJbmZvcm1hdGlvbiIsIFJGQyA0OTcxLCBKdWx5IDIwMDcu
DQoNCiAgIFtSRkM1MTIwXSAgUHJ6eWdpZW5kYSwgVC4sIFNoZW4sIE4uLCBhbmQgTi4gU2hldGgs
ICJNLUlTSVM6IE11bHRpDQogICAgICAgICAgICAgIFRvcG9sb2d5IChNVCkgUm91dGluZyBpbiBJ
bnRlcm1lZGlhdGUgU3lzdGVtIHRvDQogICAgICAgICAgICAgIEludGVybWVkaWF0ZSBTeXN0ZW1z
IChJUy1JU3MpIiwgUkZDIDUxMjAsIEZlYnJ1YXJ5IDIwMDguDQoNCiAgIFtSRkM1MzA1XSAgTGks
IFQuIGFuZCBILiBTbWl0LCAiSVMtSVMgRXh0ZW5zaW9ucyBmb3IgVHJhZmZpYw0KICAgICAgICAg
ICAgICBFbmdpbmVlcmluZyIsIFJGQyA1MzA1LCBPY3RvYmVyIDIwMDguDQoNCiAgIFtSRkM1MzI5
XSAgSXNoaWd1cm8sIEsuLCBNYW5yYWwsIFYuLCBEYXZleSwgQS4sIGFuZCBBLiBMaW5kZW0sDQog
ICAgICAgICAgICAgICJUcmFmZmljIEVuZ2luZWVyaW5nIEV4dGVuc2lvbnMgdG8gT1NQRiBWZXJz
aW9uIDMiLA0KICAgICAgICAgICAgICBSRkMgNTMyOSwgU2VwdGVtYmVyIDIwMDguDQoNCiAgIFtS
RkM1MzQwXSAgQ29sdHVuLCBSLiwgRmVyZ3Vzb24sIEQuLCBNb3ksIEouLCBhbmQgQS4gTGluZGVt
LCAiT1NQRg0KICAgICAgICAgICAgICBmb3IgSVB2NiIsIFJGQyA1MzQwLCBKdWx5IDIwMDguDQoN
Cg0KDQoNCkRhdmFyaSwgZXQgYWwuICAgICAgICAgICBFeHBpcmVzIEF1Z3VzdCAyNywgMjAxMyAg
ICAgICAgICAgICAgIFtQYWdlIDM0XQ0KDA0KSW50ZXJuZXQtRHJhZnQgICAgICAgIFRyYW5zcG9y
dGluZyBUaW1pbmcgb3ZlciBNUExTICAgICAgICBGZWJydWFyeSAyMDEzDQoNCg0KICAgW1JGQzU5
MDVdICBNaWxscywgRC4sIE1hcnRpbiwgSi4sIEJ1cmJhbmssIEouLCBhbmQgVy4gS2FzY2gsICJO
ZXR3b3JrDQogICAgICAgICAgICAgIFRpbWUgUHJvdG9jb2wgVmVyc2lvbiA0OiBQcm90b2NvbCBh
bmQgQWxnb3JpdGhtcw0KICAgICAgICAgICAgICBTcGVjaWZpY2F0aW9uIiwgUkZDIDU5MDUsIEp1
bmUgMjAxMC4NCg0KICAgW1JGQzYzOTFdICBCcnlhbnQsIFMuLCBGaWxzZmlscywgQy4sIERyYWZ6
LCBVLiwgS29tcGVsbGEsIFYuLCBSZWdhbiwNCiAgICAgICAgICAgICAgSi4sIGFuZCBTLiBBbWFu
dGUsICJGbG93LUF3YXJlIFRyYW5zcG9ydCBvZiBQc2V1ZG93aXJlcw0KICAgICAgICAgICAgICBv
dmVyIGFuIE1QTFMgUGFja2V0IFN3aXRjaGVkIE5ldHdvcmsiLCBSRkMgNjM5MSwNCiAgICAgICAg
ICAgICAgTm92ZW1iZXIgMjAxMS4NCg0KDQoNCg0KDQoNCg0KDQoNCg0KDQoNCg0KDQoNCg0KDQoN
Cg0KDQoNCg0KDQoNCg0KDQoNCg0KDQoNCg0KDQoNCg0KDQoNCg0KDQoNCg0KDQoNCg0KRGF2YXJp
LCBldCBhbC4gICAgICAgICAgIEV4cGlyZXMgQXVndXN0IDI3LCAyMDEzICAgICAgICAgICAgICAg
W1BhZ2UgMzVdDQoMDQpJbnRlcm5ldC1EcmFmdCAgICAgICAgVHJhbnNwb3J0aW5nIFRpbWluZyBv
dmVyIE1QTFMgICAgICAgIEZlYnJ1YXJ5IDIwMTMNCg0KDQpBdXRob3JzJyBBZGRyZXNzZXMNCg0K
ICAgU2hhaHJhbSBEYXZhcmkNCiAgIEJyb2FkY29tIENvcnAuDQogICBTYW4gSm9zZSwgQ0EgIDk1
MTM0DQogICBVU0ENCg0KICAgRW1haWw6IGRhdmFyaUBicm9hZGNvbS5jb20NCg0KDQogICBBbWl0
IE9yZW4NCiAgIEJyb2FkY29tIENvcnAuDQogICBTYW4gSm9zZSwgQ0EgIDk1MTM0DQogICBVU0EN
Cg0KICAgRW1haWw6IGFtaXRvQGJyb2FkY29tLmNvbQ0KDQoNCiAgIE1hbmF2IEJoYXRpYQ0KICAg
QWxjYXRlbC1MdWNlbnQNCiAgIEJhbmdhbG9yZSwNCiAgIEluZGlhDQoNCiAgIEVtYWlsOiBtYW5h
di5iaGF0aWFAYWxjYXRlbC1sdWNlbnQuY29tDQoNCg0KICAgUGV0ZXIgUm9iZXJ0cw0KICAgQWxj
YXRlbC1MdWNlbnQNCiAgIEthbmF0YSwNCiAgIENhbmFkYQ0KDQogICBFbWFpbDogcGV0ZXIucm9i
ZXJ0c0BhbGNhdGVsLWx1Y2VudC5jb20NCg0KDQogICBMYXVyZW50IE1vbnRpbmkNCiAgIENpc2Nv
IFN5c3RlbXMNCiAgIFNhbiBKb3NlIENBDQogICBVU0ENCg0KICAgRW1haWw6IGxtb250aW5pQGNp
c2NvLmNvbQ0KDQoNCg0KDQoNCg0KDQoNCg0KDQoNCkRhdmFyaSwgZXQgYWwuICAgICAgICAgICBF
eHBpcmVzIEF1Z3VzdCAyNywgMjAxMyAgICAgICAgICAgICAgIFtQYWdlIDM2XQ0KDA0K

------_=_NextPart_001_01CE6216.959AB4A8--

From prvs=5868840e41=stefano.ruffini@ericsson.com  Wed Jun  5 11:32:02 2013
Return-Path: <prvs=5868840e41=stefano.ruffini@ericsson.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 CE02021F9630 for <tictoc@ietfa.amsl.com>; Wed,  5 Jun 2013 11:32:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.249
X-Spam-Level: 
X-Spam-Status: No, score=-6.249 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_SE=0.35, 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 n6gRJtP8Jr2c for <tictoc@ietfa.amsl.com>; Wed,  5 Jun 2013 11:31:40 -0700 (PDT)
Received: from mailgw2.ericsson.se (mailgw2.ericsson.se [193.180.251.37]) by ietfa.amsl.com (Postfix) with ESMTP id A046B21F859A for <tictoc@ietf.org>; Wed,  5 Jun 2013 11:30:35 -0700 (PDT)
X-AuditID: c1b4fb25-b7f4c6d000004656-38-51af83c7e15d
Received: from ESESSHC002.ericsson.se (Unknown_Domain [153.88.253.125]) by mailgw2.ericsson.se (Symantec Mail Security) with SMTP id D5.15.18006.7C38FA15; Wed,  5 Jun 2013 20:30:32 +0200 (CEST)
Received: from ESESSMB301.ericsson.se ([169.254.1.55]) by ESESSHC002.ericsson.se ([153.88.183.24]) with mapi id 14.02.0328.009; Wed, 5 Jun 2013 20:30:31 +0200
From: Stefano Ruffini <stefano.ruffini@ericsson.com>
To: "Meyer, Peter" <Peter.Meyer@microsemi.com>, Shahram Davari <davari@broadcom.com>, "tictoc@ietf.org" <tictoc@ietf.org>
Thread-Topic: [TICTOC] comments on draft-ietf-tictoc-1588overmpls-04.txt
Thread-Index: AQHOHrvIG9Qp4DAEq0WS7lIAjM8M8JkmuDRwgAE3KqCAAAYJEA==
Date: Wed, 5 Jun 2013 18:30:30 +0000
Message-ID: <1B5CAFEB4D81154AA0F020783784C3150C775B@ESESSMB301.ericsson.se>
References: <20130223072233.32735.89371.idtracker@ietfa.amsl.com> <64683B4805156847B0ED373DAB3057CA015E930D@ottsrv0015.microsemi.net> <4A6CE49E6084B141B15C0713B8993F281BE28013@SJEXCHMB12.corp.ad.broadcom.com> <64683B4805156847B0ED373DAB3057CA01B19D5F@ottsrv0015.microsemi.net>
In-Reply-To: <64683B4805156847B0ED373DAB3057CA01B19D5F@ottsrv0015.microsemi.net>
Accept-Language: it-IT, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [153.88.183.146]
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFrrALMWRmVeSWpSXmKPExsUyM+Jvre6J5vWBBu8e8lis7/W0aL94lMXi b3MPuwOzx6z7Z9k8liz5yeQxZ+1DtgDmKG6bpMSSsuDM9Dx9uwTujD1nXzIXXAmsOPPiAGMD 4w+HLkZODgkBE4kpdyezQ9hiEhfurWfrYuTiEBI4zChx6vJcKGcRo8SVyXsZQarYgDqeL17N 1MXIwSEiUC0x6YUQSFhYwF1i7v/lLCC2iICHxNSuJ1C2k0TrhSNsIDaLgIrE4/6vrCA2r4C3 xPppNxkh5s9iknjS0gxWxCkQILH9zzuwXYwCshITdi8Cs5kFxCVuPZnPBHGpgMSSPeeZIWxR iZeP/7FC2EoSPzZcYoGo15O4MXUKG4StLbFs4WtmiMWCEidnPmGZwCg6C8nYWUhaZiFpmYWk ZQEjyypG9tzEzJz0cqNNjMAIObjlt+oOxjvnRA4xSnOwKInz6vEuDhQSSE8sSc1OTS1ILYov Ks1JLT7EyMTBCSK4pBoYg89Js5265xZ78ICojcI+00nVs1Q/rfUMO1Lotvvb7B+rWX/Lcmqe 9uSdNu+hQ+LJ6T9vXc9exPq9o8fRa0/MpyPH+6O27jF6l/X438HNJrMfntbV7vu9d7bVnUCv ZbKGVU8YnKeHVS+fY801a+U99QeRcx5823/Y5uPLOP6mnmkyrSqG/olNU5VYijMSDbWYi4oT AXftzOBjAgAA
Subject: Re: [TICTOC] comments on draft-ietf-tictoc-1588overmpls-04.txt
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: Wed, 05 Jun 2013 18:32:02 -0000

Hi Shahram, Peter

There is one point I would disagree with (I am referring to Peter's latest =
proposal, but the same comment would apply to the previous text):
"
An MPLS domain may serve multiple customers.  In these cases the
   MPLS domain (maintained by a service provider) may provide timing
   services to multiple customers, each having their own Timing domain.
   If so, then the LER BCs and TCs may interact with multiple grandmasters,
   and consequently multiple time references.  Also, LER/LSR TCs MUST be
   synchronized to the same master clock (which is the service provider
   Master clock), which implies that they need to choose one master to
   which it will synchronize.
"

My understanding of this statement is that a LER would need to implement mu=
ltiple BC instances (with multiple clocks); this looks too complex.

The case of multiple operators, seems to me only practically applicable to =
figure 3 (LER TC).

I would then propose to remove the reference to LER BC in this statement .

Best regards
stefano


-----Original Message-----
From: tictoc-bounces@ietf.org [mailto:tictoc-bounces@ietf.org] On Behalf Of=
 Meyer, Peter
Sent: mercoled=EC 5 giugno 2013 20:01
To: Shahram Davari; tictoc@ietf.org
Subject: Re: [TICTOC] comments on draft-ietf-tictoc-1588overmpls-04.txt

Hi Shahram,

I hope in-line with my comments I have edited the text of draft -04.

I'm not sure how the formatting worked out (PC-based, line length, page len=
gth).

I modified sections 3, 4, 18, 19 & 20.

I include here both original and modified version so you can diff (most of =
the changes in 3 are due to line length / re-org, not actual text changes).

File attachment:
"draft-ietf-tictoc-1588overmpls-04-org.txt" (52 KB) "draft-ietf-tictoc-1588=
overmpls-04-pm.txt" (53 KB)


Regards,
Peter


-----Original Message-----
From: Shahram Davari [mailto:davari@broadcom.com]
Sent: June 4, 2013 7:40 PM
To: Meyer, Peter; tictoc@ietf.org
Subject: RE: [TICTOC] comments on draft-ietf-tictoc-1588overmpls-04.txt

Hi Peter,

Thanks for your god comments. Please see my responses inline. Please let me=
 know whether you are satisfied with my responses since I am updating the d=
raft in the next couple of days.

Thanks
Shahram

-----Original Message-----
From: tictoc-bounces@ietf.org [mailto:tictoc-bounces@ietf.org] On Behalf Of=
 Meyer, Peter
Sent: Monday, March 11, 2013 5:49 PM
To: tictoc@ietf.org
Subject: Re: [TICTOC] comments on draft-ietf-tictoc-1588overmpls-04.txt

Hi Shahram et al,

Some comments on draft -04.


1) Section 3.  "A generic method is defined in this document that does not =
require deep packet inspection at line rate, and can deterministically iden=
tify Timing messages.  The generic method is applicable to MPLS and MPLS-TP=
 networks."

May want to add that this would apply only to one-step TC (I imagine that i=
s the point of the correction at line rate).  A two-step TC would need to d=
o deep packet inspection as it uses sourcePortIdentity & sequenceId fields =
for Follow_up or Delay_Resp.

SD> For 2-step, all that is needed is for an interface to detect the
Timing message (based on top MPLS Label)  and record the Time along with so=
me information from the Timing packet and send them to CPU while forwarding=
 the Timing message as usual. Then the CPU based on the information receive=
d generates Follow-up message and injects it in to the LSP.  Therefore it i=
s the job of CPU to look at sourcePortIdentity & sequenceId fields not the =
Hardware.


2) Section 4.  "An MPLS domain can serve multiple customers.  This means th=
at the MPLS domain (maintained by a service provider) may provide timing se=
rvices to multiple customers, each having their own Timing domain.  Therefo=
re LER BCs need to interact with multiple grandmasters, and consequently mu=
ltiple time references."

This should be re-phrased.  It switches from an optional situation ("may pr=
ovide timing services") to mandatory situation ("LER BCs need to
interact").   Some words such as "in such a deployment scenario, ...."
and replace "can" with "may".   We have seen at ITU at least (with
participation from operators BT, FT, DT, CMCC, AT&T, Sprint, etc.) that thi=
s multiple operator domain case was not useful enough to be included in sta=
ndardization process for Telecom networks.

SD> I rephrased it as following:

" An MPLS domain can serve multiple customers.  This means that the
   MPLS domain (maintained by a service provider) may provide timing
   services to multiple customers, each having their own Timing domain.
   Therefore in such deployment scenarios, LER BCs may interact with multip=
le grandmasters, and consequently multiple time references.  Also, LER/LSR =
TCs MUST be synchronized to the same master clock (which is the service pro=
vider Master clock), which implies that they need to choose one master to s=
ynchronize to."


3) Section 19.  "For transporting such peer delay measurement messages a si=
ngle-hop LSP SHOULD to be created between the two adjacent LSRs engaged in =
peer delay measurement to carry peer delay measurement messages. Other meth=
ods such as PTP transport over Ethernet MAY be used for transporting peer d=
elay measurement messages if the link between the two routers is Ethernet."


This new statement to handle peer-delay (which in earlier drafts did not ha=
ve a communication path listed), also allows a BC to be embedded in an LSR =
with a communication path between BC's as a single-hop LSP (mentioned March=
 22, 2012 in my feedback to draft -03, subject "[TICTOC] Updated 1588 over =
MPLS draf-03").

SD> When a single-hop LSP is created then I call the both ends of that
LSP, LERs and not LSRs.
Note that a router can act as LSR for some LSPs and LER for other LSPs.
The point is that we can't
Terminate a packet in the middle of an LSP (i.e., in an LSR). So BC functio=
nality can't exist in the middle Of a PTP LSP. So I think it is a matter of=
 terminology otherwise I agree that you could have BC in the core (not edge=
).=20

Architecture diagrams Figure 1 and Figure should be updated to reflect
the possibility of either BC or TC implementation.   Section 18.2 and
section 18.3 and section 21 should also be updated to reflect the possibili=
ty of either BC or TC.  I understand the RFC is intended to be generic and =
not targeted only at TC.



4) Section 20.  "When the MPLS network (provider network) serves multiple c=
ustomers, it is important to maintain and process each customers clock and =
Timing messages separately from other customers to
ensure there is no cross- customer effect.   For example if an LER BC is
synchronized to a specific grandmaster, belonging to customer A, then the L=
ER MUST use that BC clock only for customer A to ensure that customer A can=
not attack other customers by manipulating its time."

This seems much more applicable to the TC LSR and should be stated.
>From section 4 we see the TC uses the primary synchronization domain (that =
of the service provide) to correct PTP messages.

SD> I don't see how in a TC LSR, one customer timing can affect other
customer timings?
Since in a TC, we just update the Timestamp of a packet based on the Servic=
e provider Time.
May be I have not understood your point. Could you please clarify with an e=
xample.



5) Section 20.  "Timing messages (as opposed to regular customer data) SHOU=
LD not be encrypted or authenticated on an end-to-end basis."  I think ther=
e is a security draft in parallel being developed that may be relevant to t=
hat statement.

SD> I have updated the  text as following:

" Timing messages MAY be encrypted or authenticated, provided that the LERs=
/LSRs that are Timing capable/aware can authenticate/ decrypt the timing me=
ssages."




Regards,
Peter


-----Original Message-----
From: tictoc-bounces@ietf.org [mailto:tictoc-bounces@ietf.org] On Behalf Of=
 internet-drafts@ietf.org
Sent: February 23, 2013 2:23 AM
To: i-d-announce@ietf.org
Cc: tictoc@ietf.org
Subject: [TICTOC] I-D Action: draft-ietf-tictoc-1588overmpls-04.txt


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           : Transporting Timing messages over MPLS
Networks
	Author(s)       : Shahram Davari
                          Amit Oren
                          Manav Bhatia
                          Peter Roberts
                          Laurent Montini
	Filename        : draft-ietf-tictoc-1588overmpls-04.txt
	Pages           : 36
	Date            : 2013-02-22

Abstract:
   This document defines the method for transporting Timing messages
   such as PTP and NTP over an MPLS network.  The method allows for the
   easy identification of these PDUs at the port level to allow for port
   level processing of these PDUs in both LERs and LSRs.

   The basic idea is to transport Timing messages inside dedicated MPLS
   LSPs.  These LSPs only carry timing messages and possibly Control and
   Management packets, but they do not carry customer traffic.

   Two methods for transporting Timing messages over MPLS are defined.
   The first method is to transport Timing messages directly over the
   dedicated MPLS LSP via UDP/IP encapsulation, which is suitable for
   MPLS networks.  The second method is to transport Timing messages
   inside a PW via Ethernet encapsulation, which is suitable for both
   MPLS and MPLS-TP networks.


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

There's also a htmlized version available at:
http://tools.ietf.org/html/draft-ietf-tictoc-1588overmpls-04

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


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

_______________________________________________
TICTOC mailing list
TICTOC@ietf.org
https://www.ietf.org/mailman/listinfo/tictoc


_______________________________________________
TICTOC mailing list
TICTOC@ietf.org
https://www.ietf.org/mailman/listinfo/tictoc




From Peter.Meyer@microsemi.com  Wed Jun  5 12:21:34 2013
Return-Path: <Peter.Meyer@microsemi.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 9E72621F99DD for <tictoc@ietfa.amsl.com>; Wed,  5 Jun 2013 12:21:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.099
X-Spam-Level: 
X-Spam-Status: No, score=-5.099 tagged_above=-999 required=5 tests=[AWL=-1.500, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-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 lfFC2C+lW7GR for <tictoc@ietfa.amsl.com>; Wed,  5 Jun 2013 12:21:24 -0700 (PDT)
Received: from ch1outboundpool.messaging.microsoft.com (ch1ehsobe004.messaging.microsoft.com [216.32.181.184]) by ietfa.amsl.com (Postfix) with ESMTP id D5BC321F99B9 for <tictoc@ietf.org>; Wed,  5 Jun 2013 12:21:22 -0700 (PDT)
Received: from mail167-ch1-R.bigfish.com (10.43.68.234) by CH1EHSOBE010.bigfish.com (10.43.70.60) with Microsoft SMTP Server id 14.1.225.23; Wed, 5 Jun 2013 19:21:22 +0000
Received: from mail167-ch1 (localhost [127.0.0.1])	by mail167-ch1-R.bigfish.com (Postfix) with ESMTP id 2B7EA1A012C; Wed,  5 Jun 2013 19:21:22 +0000 (UTC)
X-Forefront-Antispam-Report: CIP:209.226.172.12; KIP:(null); UIP:(null); IPV:NLI; H:ottsrv0014.microsemi.net; RD:none; EFVD:NLI
X-SpamScore: -23
X-BigFish: VS-23(zz9371Ic89bh936eI542Idb82hzz1f42h1ee6h1de0h1fdah1202h1e76h1d1ah1d2ah1fc6hzz1033IL17326ah8275dhz2dh668h839h947hd25hf0ah1288h12a5h12a9h12bdh137ah13b6h1441h14ddh1504h1537h153bh15d0h162dh1631h1758h184fh18e1h1946h19b5h1ad9h1b0ah1c24h1d0ch1d2eh1d3fh1dfeh1dffh1e1dh1155h)
Received: from mail167-ch1 (localhost.localdomain [127.0.0.1]) by mail167-ch1 (MessageSwitch) id 1370460080579899_12615; Wed,  5 Jun 2013 19:21:20 +0000 (UTC)
Received: from CH1EHSMHS031.bigfish.com (snatpool2.int.messaging.microsoft.com [10.43.68.230])	by mail167-ch1.bigfish.com (Postfix) with ESMTP id 8AFF8460048;	Wed,  5 Jun 2013 19:21:20 +0000 (UTC)
Received: from ottsrv0014.microsemi.net (209.226.172.12) by CH1EHSMHS031.bigfish.com (10.43.70.31) with Microsoft SMTP Server id 14.1.225.23; Wed, 5 Jun 2013 19:21:20 +0000
Received: from ottsrv0015.microsemi.net ([134.199.15.151]) by ottsrv0014.microsemi.net with Microsoft SMTPSVC(6.0.3790.4675); Wed, 5 Jun 2013 15:21:19 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-Class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Date: Wed, 5 Jun 2013 15:21:05 -0400
Message-ID: <64683B4805156847B0ED373DAB3057CA01B19DBA@ottsrv0015.microsemi.net>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [TICTOC] comments on draft-ietf-tictoc-1588overmpls-04.txt
Thread-Index: AQHOHrvIG9Qp4DAEq0WS7lIAjM8M8JkmuDRwgAE3KqCAAAYJEIAAD6Tw
References: <20130223072233.32735.89371.idtracker@ietfa.amsl.com><64683B4805156847B0ED373DAB3057CA015E930D@ottsrv0015.microsemi.net><4A6CE49E6084B141B15C0713B8993F281BE28013@SJEXCHMB12.corp.ad.broadcom.com> <64683B4805156847B0ED373DAB3057CA01B19D5F@ottsrv0015.microsemi.net> <1B5CAFEB4D81154AA0F020783784C3150C775B@ESESSMB301.ericsson.se>
From: "Meyer, Peter" <Peter.Meyer@microsemi.com>
To: Stefano Ruffini <stefano.ruffini@ericsson.com>, Shahram Davari <davari@broadcom.com>, <tictoc@ietf.org>
X-OriginalArrivalTime: 05 Jun 2013 19:21:19.0947 (UTC) FILETIME=[DBAF61B0:01CE6221]
X-OriginatorOrg: microsemi.com
Subject: Re: [TICTOC] comments on draft-ietf-tictoc-1588overmpls-04.txt
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: Wed, 05 Jun 2013 19:21:34 -0000

Hi Stefano,

I see Figure 3 and Figure 4 apply to the text above the figures, =
unrelated to multiple domains.

I see the multiple domain paragraph as a separate topic, perhaps could =
be its own sub-section.  We have seen systems that support multiple =
domains either as BC or TC.  I could support removal of the mention of =
multiple operator domains in total, if that is agreeable.  Otherwise I =
see BC and TC as both valid solutions available in the market today.

Regards,
Peter


-----Original Message-----
From: Stefano Ruffini [mailto:stefano.ruffini@ericsson.com]=20
Sent: June 5, 2013 2:31 PM
To: Meyer, Peter; Shahram Davari; tictoc@ietf.org
Subject: RE: [TICTOC] comments on draft-ietf-tictoc-1588overmpls-04.txt

Hi Shahram, Peter

There is one point I would disagree with (I am referring to Peter's =
latest proposal, but the same comment would apply to the previous text):
"
An MPLS domain may serve multiple customers.  In these cases the
   MPLS domain (maintained by a service provider) may provide timing
   services to multiple customers, each having their own Timing domain.
   If so, then the LER BCs and TCs may interact with multiple =
grandmasters,
   and consequently multiple time references.  Also, LER/LSR TCs MUST be
   synchronized to the same master clock (which is the service provider
   Master clock), which implies that they need to choose one master to
   which it will synchronize.
"

My understanding of this statement is that a LER would need to implement =
multiple BC instances (with multiple clocks); this looks too complex.

The case of multiple operators, seems to me only practically applicable =
to figure 3 (LER TC).

I would then propose to remove the reference to LER BC in this statement =
.

Best regards
stefano


-----Original Message-----
From: tictoc-bounces@ietf.org [mailto:tictoc-bounces@ietf.org] On Behalf =
Of Meyer, Peter
Sent: mercoled=EC 5 giugno 2013 20:01
To: Shahram Davari; tictoc@ietf.org
Subject: Re: [TICTOC] comments on draft-ietf-tictoc-1588overmpls-04.txt

Hi Shahram,

I hope in-line with my comments I have edited the text of draft -04.

I'm not sure how the formatting worked out (PC-based, line length, page =
length).

I modified sections 3, 4, 18, 19 & 20.

I include here both original and modified version so you can diff (most =
of the changes in 3 are due to line length / re-org, not actual text =
changes).

File attachment:
"draft-ietf-tictoc-1588overmpls-04-org.txt" (52 KB) =
"draft-ietf-tictoc-1588overmpls-04-pm.txt" (53 KB)


Regards,
Peter


-----Original Message-----
From: Shahram Davari [mailto:davari@broadcom.com]
Sent: June 4, 2013 7:40 PM
To: Meyer, Peter; tictoc@ietf.org
Subject: RE: [TICTOC] comments on draft-ietf-tictoc-1588overmpls-04.txt

Hi Peter,

Thanks for your god comments. Please see my responses inline. Please let =
me know whether you are satisfied with my responses since I am updating =
the draft in the next couple of days.

Thanks
Shahram

-----Original Message-----
From: tictoc-bounces@ietf.org [mailto:tictoc-bounces@ietf.org] On Behalf =
Of Meyer, Peter
Sent: Monday, March 11, 2013 5:49 PM
To: tictoc@ietf.org
Subject: Re: [TICTOC] comments on draft-ietf-tictoc-1588overmpls-04.txt

Hi Shahram et al,

Some comments on draft -04.


1) Section 3.  "A generic method is defined in this document that does =
not require deep packet inspection at line rate, and can =
deterministically identify Timing messages.  The generic method is =
applicable to MPLS and MPLS-TP networks."

May want to add that this would apply only to one-step TC (I imagine =
that is the point of the correction at line rate).  A two-step TC would =
need to do deep packet inspection as it uses sourcePortIdentity & =
sequenceId fields for Follow_up or Delay_Resp.

SD> For 2-step, all that is needed is for an interface to detect the
Timing message (based on top MPLS Label)  and record the Time along with =
some information from the Timing packet and send them to CPU while =
forwarding the Timing message as usual. Then the CPU based on the =
information received generates Follow-up message and injects it in to =
the LSP.  Therefore it is the job of CPU to look at sourcePortIdentity & =
sequenceId fields not the Hardware.


2) Section 4.  "An MPLS domain can serve multiple customers.  This means =
that the MPLS domain (maintained by a service provider) may provide =
timing services to multiple customers, each having their own Timing =
domain.  Therefore LER BCs need to interact with multiple grandmasters, =
and consequently multiple time references."

This should be re-phrased.  It switches from an optional situation ("may =
provide timing services") to mandatory situation ("LER BCs need to
interact").   Some words such as "in such a deployment scenario, ...."
and replace "can" with "may".   We have seen at ITU at least (with
participation from operators BT, FT, DT, CMCC, AT&T, Sprint, etc.) that =
this multiple operator domain case was not useful enough to be included =
in standardization process for Telecom networks.

SD> I rephrased it as following:

" An MPLS domain can serve multiple customers.  This means that the
   MPLS domain (maintained by a service provider) may provide timing
   services to multiple customers, each having their own Timing domain.
   Therefore in such deployment scenarios, LER BCs may interact with =
multiple grandmasters, and consequently multiple time references.  Also, =
LER/LSR TCs MUST be synchronized to the same master clock (which is the =
service provider Master clock), which implies that they need to choose =
one master to synchronize to."


3) Section 19.  "For transporting such peer delay measurement messages a =
single-hop LSP SHOULD to be created between the two adjacent LSRs =
engaged in peer delay measurement to carry peer delay measurement =
messages. Other methods such as PTP transport over Ethernet MAY be used =
for transporting peer delay measurement messages if the link between the =
two routers is Ethernet."


This new statement to handle peer-delay (which in earlier drafts did not =
have a communication path listed), also allows a BC to be embedded in an =
LSR with a communication path between BC's as a single-hop LSP =
(mentioned March 22, 2012 in my feedback to draft -03, subject "[TICTOC] =
Updated 1588 over MPLS draf-03").

SD> When a single-hop LSP is created then I call the both ends of that
LSP, LERs and not LSRs.
Note that a router can act as LSR for some LSPs and LER for other LSPs.
The point is that we can't
Terminate a packet in the middle of an LSP (i.e., in an LSR). So BC =
functionality can't exist in the middle Of a PTP LSP. So I think it is a =
matter of terminology otherwise I agree that you could have BC in the =
core (not edge).=20

Architecture diagrams Figure 1 and Figure should be updated to reflect
the possibility of either BC or TC implementation.   Section 18.2 and
section 18.3 and section 21 should also be updated to reflect the =
possibility of either BC or TC.  I understand the RFC is intended to be =
generic and not targeted only at TC.



4) Section 20.  "When the MPLS network (provider network) serves =
multiple customers, it is important to maintain and process each =
customers clock and Timing messages separately from other customers to
ensure there is no cross- customer effect.   For example if an LER BC is
synchronized to a specific grandmaster, belonging to customer A, then =
the LER MUST use that BC clock only for customer A to ensure that =
customer A cannot attack other customers by manipulating its time."

This seems much more applicable to the TC LSR and should be stated.
>From section 4 we see the TC uses the primary synchronization domain =
(that of the service provide) to correct PTP messages.

SD> I don't see how in a TC LSR, one customer timing can affect other
customer timings?
Since in a TC, we just update the Timestamp of a packet based on the =
Service provider Time.
May be I have not understood your point. Could you please clarify with =
an example.



5) Section 20.  "Timing messages (as opposed to regular customer data) =
SHOULD not be encrypted or authenticated on an end-to-end basis."  I =
think there is a security draft in parallel being developed that may be =
relevant to that statement.

SD> I have updated the  text as following:

" Timing messages MAY be encrypted or authenticated, provided that the =
LERs/LSRs that are Timing capable/aware can authenticate/ decrypt the =
timing messages."




Regards,
Peter


-----Original Message-----
From: tictoc-bounces@ietf.org [mailto:tictoc-bounces@ietf.org] On Behalf =
Of internet-drafts@ietf.org
Sent: February 23, 2013 2:23 AM
To: i-d-announce@ietf.org
Cc: tictoc@ietf.org
Subject: [TICTOC] I-D Action: draft-ietf-tictoc-1588overmpls-04.txt


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

	Title           : Transporting Timing messages over MPLS
Networks
	Author(s)       : Shahram Davari
                          Amit Oren
                          Manav Bhatia
                          Peter Roberts
                          Laurent Montini
	Filename        : draft-ietf-tictoc-1588overmpls-04.txt
	Pages           : 36
	Date            : 2013-02-22

Abstract:
   This document defines the method for transporting Timing messages
   such as PTP and NTP over an MPLS network.  The method allows for the
   easy identification of these PDUs at the port level to allow for port
   level processing of these PDUs in both LERs and LSRs.

   The basic idea is to transport Timing messages inside dedicated MPLS
   LSPs.  These LSPs only carry timing messages and possibly Control and
   Management packets, but they do not carry customer traffic.

   Two methods for transporting Timing messages over MPLS are defined.
   The first method is to transport Timing messages directly over the
   dedicated MPLS LSP via UDP/IP encapsulation, which is suitable for
   MPLS networks.  The second method is to transport Timing messages
   inside a PW via Ethernet encapsulation, which is suitable for both
   MPLS and MPLS-TP networks.


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

There's also a htmlized version available at:
http://tools.ietf.org/html/draft-ietf-tictoc-1588overmpls-04

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


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

_______________________________________________
TICTOC mailing list
TICTOC@ietf.org
https://www.ietf.org/mailman/listinfo/tictoc


_______________________________________________
TICTOC mailing list
TICTOC@ietf.org
https://www.ietf.org/mailman/listinfo/tictoc






From davari@broadcom.com  Wed Jun  5 14:32:04 2013
Return-Path: <davari@broadcom.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 D55EC11E80BA for <tictoc@ietfa.amsl.com>; Wed,  5 Jun 2013 14:32:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5HQPKGsTdkvs for <tictoc@ietfa.amsl.com>; Wed,  5 Jun 2013 14:31:58 -0700 (PDT)
Received: from mms1.broadcom.com (mms1.broadcom.com [216.31.210.17]) by ietfa.amsl.com (Postfix) with ESMTP id 6EDF311E80AE for <tictoc@ietf.org>; Wed,  5 Jun 2013 14:31:58 -0700 (PDT)
Received: from [10.9.208.53] by mms1.broadcom.com with ESMTP (Broadcom SMTP Relay (Email Firewall v6.5)); Wed, 05 Jun 2013 14:28:03 -0700
X-Server-Uuid: 06151B78-6688-425E-9DE2-57CB27892261
Received: from SJEXCHCAS07.corp.ad.broadcom.com (10.16.203.16) by IRVEXCHCAS06.corp.ad.broadcom.com (10.9.208.53) with Microsoft SMTP Server (TLS) id 14.1.438.0; Wed, 5 Jun 2013 14:31:41 -0700
Received: from SJEXCHMB12.corp.ad.broadcom.com ( [fe80::bc15:c1e1:c29a:36f7]) by SJEXCHCAS07.corp.ad.broadcom.com ( [::1]) with mapi id 14.01.0438.000; Wed, 5 Jun 2013 14:31:38 -0700
From: "Shahram Davari" <davari@broadcom.com>
To: "Meyer, Peter" <Peter.Meyer@microsemi.com>, "tictoc@ietf.org" <tictoc@ietf.org>
Thread-Topic: [TICTOC] comments on draft-ietf-tictoc-1588overmpls-04.txt
Thread-Index: AQHOHrvIG9Qp4DAEq0WS7lIAjM8M8JkmuDRwgAE3KqCAADsOgA==
Date: Wed, 5 Jun 2013 21:31:38 +0000
Message-ID: <4A6CE49E6084B141B15C0713B8993F281BE2FD85@SJEXCHMB12.corp.ad.broadcom.com>
References: <20130223072233.32735.89371.idtracker@ietfa.amsl.com> <64683B4805156847B0ED373DAB3057CA015E930D@ottsrv0015.microsemi.net> <4A6CE49E6084B141B15C0713B8993F281BE28013@SJEXCHMB12.corp.ad.broadcom.com> <64683B4805156847B0ED373DAB3057CA01B19D5F@ottsrv0015.microsemi.net>
In-Reply-To: <64683B4805156847B0ED373DAB3057CA01B19D5F@ottsrv0015.microsemi.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.16.203.100]
MIME-Version: 1.0
X-WSS-ID: 7DB172E931W31947205-01-01
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Subject: Re: [TICTOC] comments on draft-ietf-tictoc-1588overmpls-04.txt
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: Wed, 05 Jun 2013 21:32:04 -0000

Thanks Peter.=20

These edits where done before the publishing of draft-04. Correct?

-Shahram

-----Original Message-----
From: Meyer, Peter [mailto:Peter.Meyer@microsemi.com]=20
Sent: Wednesday, June 05, 2013 11:01 AM
To: Shahram Davari; tictoc@ietf.org
Subject: RE: [TICTOC] comments on draft-ietf-tictoc-1588overmpls-04.txt

Hi Shahram,

I hope in-line with my comments I have edited the text of draft -04.

I'm not sure how the formatting worked out (PC-based, line length, page
length).

I modified sections 3, 4, 18, 19 & 20.

I include here both original and modified version so you can diff (most
of the changes in 3 are due to line length / re-org, not actual text
changes).

File attachment:
"draft-ietf-tictoc-1588overmpls-04-org.txt" (52 KB)
"draft-ietf-tictoc-1588overmpls-04-pm.txt" (53 KB)


Regards,
Peter


-----Original Message-----
From: Shahram Davari [mailto:davari@broadcom.com]=20
Sent: June 4, 2013 7:40 PM
To: Meyer, Peter; tictoc@ietf.org
Subject: RE: [TICTOC] comments on draft-ietf-tictoc-1588overmpls-04.txt

Hi Peter,

Thanks for your god comments. Please see my responses inline. Please let
me know whether you are satisfied with my responses since I am updating
the draft in the next couple of days.

Thanks
Shahram

-----Original Message-----
From: tictoc-bounces@ietf.org [mailto:tictoc-bounces@ietf.org] On Behalf
Of Meyer, Peter
Sent: Monday, March 11, 2013 5:49 PM
To: tictoc@ietf.org
Subject: Re: [TICTOC] comments on draft-ietf-tictoc-1588overmpls-04.txt

Hi Shahram et al,

Some comments on draft -04.


1) Section 3.  "A generic method is defined in this document that does
not require deep packet inspection at line rate, and can
deterministically identify Timing messages.  The generic method is
applicable to MPLS and MPLS-TP networks."

May want to add that this would apply only to one-step TC (I imagine
that is the point of the correction at line rate).  A two-step TC would
need to do deep packet inspection as it uses sourcePortIdentity &
sequenceId fields for Follow_up or Delay_Resp.

SD> For 2-step, all that is needed is for an interface to detect the
Timing message (based on top MPLS Label)  and record the Time along with
some information from the Timing packet and send them to CPU while
forwarding the Timing message as usual. Then the CPU based on the
information received generates Follow-up message and injects it in to
the LSP.  Therefore it is the job of CPU to look at sourcePortIdentity &
sequenceId fields not the Hardware.


2) Section 4.  "An MPLS domain can serve multiple customers.  This means
that the MPLS domain (maintained by a service provider) may provide
timing services to multiple customers, each having their own Timing
domain.  Therefore LER BCs need to interact with multiple grandmasters,
and consequently multiple time references."

This should be re-phrased.  It switches from an optional situation ("may
provide timing services") to mandatory situation ("LER BCs need to
interact").   Some words such as "in such a deployment scenario, ...."
and replace "can" with "may".   We have seen at ITU at least (with
participation from operators BT, FT, DT, CMCC, AT&T, Sprint, etc.) that
this multiple operator domain case was not useful enough to be included
in standardization process for Telecom networks.

SD> I rephrased it as following:

" An MPLS domain can serve multiple customers.  This means that the
   MPLS domain (maintained by a service provider) may provide timing
   services to multiple customers, each having their own Timing domain.
   Therefore in such deployment scenarios, LER BCs may interact with
multiple grandmasters,=20
and consequently multiple time references.  Also, LER/LSR TCs MUST be
synchronized to the=20
same master clock (which is the service provider Master clock), which
implies that they need=20
to choose one master to synchronize to."


3) Section 19.  "For transporting such peer delay measurement messages a
single-hop LSP SHOULD to be created between the two adjacent LSRs
engaged in peer delay measurement to carry peer delay measurement
messages. Other methods such as PTP transport over Ethernet MAY be used
for transporting peer delay measurement messages if the link between the
two routers is Ethernet."


This new statement to handle peer-delay (which in earlier drafts did not
have a communication path listed), also allows a BC to be embedded in an
LSR with a communication path between BC's as a single-hop LSP
(mentioned March 22, 2012 in my feedback to draft -03, subject "[TICTOC]
Updated 1588 over MPLS draf-03").

SD> When a single-hop LSP is created then I call the both ends of that
LSP, LERs and not LSRs.
Note that a router can act as LSR for some LSPs and LER for other LSPs.
The point is that we can't
Terminate a packet in the middle of an LSP (i.e., in an LSR). So BC
functionality can't exist in the middle
Of a PTP LSP. So I think it is a matter of terminology otherwise I agree
that you could have BC in the core
(not edge).=20

Architecture diagrams Figure 1 and Figure should be updated to reflect
the possibility of either BC or TC implementation.   Section 18.2 and
section 18.3 and section 21 should also be updated to reflect the
possibility of either BC or TC.  I understand the RFC is intended to be
generic and not targeted only at TC.



4) Section 20.  "When the MPLS network (provider network) serves
multiple customers, it is important to maintain and process each
customers clock and Timing messages separately from other customers to
ensure there is no cross- customer effect.   For example if an LER BC is
synchronized to a specific grandmaster, belonging to customer A, then
the LER MUST use that BC clock only for customer A to ensure that
customer A cannot attack other customers by manipulating its time."

This seems much more applicable to the TC LSR and should be stated.
>From section 4 we see the TC uses the primary synchronization domain
(that of the service provide) to correct PTP messages.

SD> I don't see how in a TC LSR, one customer timing can affect other
customer timings?
Since in a TC, we just update the Timestamp of a packet based on the
Service provider Time.
May be I have not understood your point. Could you please clarify with
an example.



5) Section 20.  "Timing messages (as opposed to regular customer data)
SHOULD not be encrypted or authenticated on an end-to-end basis."  I
think there is a security draft in parallel being developed that may be
relevant to that statement.

SD> I have updated the  text as following:

" Timing messages MAY be encrypted or authenticated, provided that the
LERs/LSRs that are Timing capable/aware can authenticate/ decrypt the
timing messages."




Regards,
Peter


-----Original Message-----
From: tictoc-bounces@ietf.org [mailto:tictoc-bounces@ietf.org] On Behalf
Of internet-drafts@ietf.org
Sent: February 23, 2013 2:23 AM
To: i-d-announce@ietf.org
Cc: tictoc@ietf.org
Subject: [TICTOC] I-D Action: draft-ietf-tictoc-1588overmpls-04.txt


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

	Title           : Transporting Timing messages over MPLS
Networks
	Author(s)       : Shahram Davari
                          Amit Oren
                          Manav Bhatia
                          Peter Roberts
                          Laurent Montini
	Filename        : draft-ietf-tictoc-1588overmpls-04.txt
	Pages           : 36
	Date            : 2013-02-22

Abstract:
   This document defines the method for transporting Timing messages
   such as PTP and NTP over an MPLS network.  The method allows for the
   easy identification of these PDUs at the port level to allow for port
   level processing of these PDUs in both LERs and LSRs.

   The basic idea is to transport Timing messages inside dedicated MPLS
   LSPs.  These LSPs only carry timing messages and possibly Control and
   Management packets, but they do not carry customer traffic.

   Two methods for transporting Timing messages over MPLS are defined.
   The first method is to transport Timing messages directly over the
   dedicated MPLS LSP via UDP/IP encapsulation, which is suitable for
   MPLS networks.  The second method is to transport Timing messages
   inside a PW via Ethernet encapsulation, which is suitable for both
   MPLS and MPLS-TP networks.


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

There's also a htmlized version available at:
http://tools.ietf.org/html/draft-ietf-tictoc-1588overmpls-04

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


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

_______________________________________________
TICTOC mailing list
TICTOC@ietf.org
https://www.ietf.org/mailman/listinfo/tictoc


_______________________________________________
TICTOC mailing list
TICTOC@ietf.org
https://www.ietf.org/mailman/listinfo/tictoc





From Peter.Meyer@microsemi.com  Wed Jun  5 14:49:01 2013
Return-Path: <Peter.Meyer@microsemi.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 26DB121F955A for <tictoc@ietfa.amsl.com>; Wed,  5 Jun 2013 14:49:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.849
X-Spam-Level: 
X-Spam-Status: No, score=-3.849 tagged_above=-999 required=5 tests=[AWL=-1.250, 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 FrCYhV8rqI3N for <tictoc@ietfa.amsl.com>; Wed,  5 Jun 2013 14:48:49 -0700 (PDT)
Received: from db9outboundpool.messaging.microsoft.com (mail-db9lp0248.outbound.messaging.microsoft.com [213.199.154.248]) by ietfa.amsl.com (Postfix) with ESMTP id 00F1521F84B2 for <tictoc@ietf.org>; Wed,  5 Jun 2013 14:48:48 -0700 (PDT)
Received: from mail188-db9-R.bigfish.com (10.174.16.247) by DB9EHSOBE028.bigfish.com (10.174.14.91) with Microsoft SMTP Server id 14.1.225.23; Wed, 5 Jun 2013 21:48:48 +0000
Received: from mail188-db9 (localhost [127.0.0.1])	by mail188-db9-R.bigfish.com (Postfix) with ESMTP id E3B9F6E0246; Wed,  5 Jun 2013 21:48:47 +0000 (UTC)
X-Forefront-Antispam-Report: CIP:209.226.172.12; KIP:(null); UIP:(null); IPV:NLI; H:ottsrv0014.microsemi.net; RD:none; EFVD:NLI
X-SpamScore: -23
X-BigFish: VS-23(zz9371I936eI542Izz1f42h1ee6h1de0h1fdah1202h1e76h1d1ah1d2ah1fc6hzz1033IL17326ah8275dhz2dh668h839h944hd25hf0ah1220h1288h12a5h12a9h12bdh137ah13b6h1441h14ddh1504h1537h153bh15d0h162dh1631h1758h184fh18e1h1946h19b5h1ad9h1b0ah1c24h1d0ch1d2eh1d3fh1dfeh1dffh1e1dh1155h)
Received: from mail188-db9 (localhost.localdomain [127.0.0.1]) by mail188-db9 (MessageSwitch) id 137046892623295_22994; Wed,  5 Jun 2013 21:48:46 +0000 (UTC)
Received: from DB9EHSMHS015.bigfish.com (unknown [10.174.16.254])	by mail188-db9.bigfish.com (Postfix) with ESMTP id 00E2C160046; Wed,  5 Jun 2013 21:48:46 +0000 (UTC)
Received: from ottsrv0014.microsemi.net (209.226.172.12) by DB9EHSMHS015.bigfish.com (10.174.14.25) with Microsoft SMTP Server id 14.16.227.3; Wed, 5 Jun 2013 21:48:41 +0000
Received: from ottsrv0015.microsemi.net ([134.199.15.151]) by ottsrv0014.microsemi.net with Microsoft SMTPSVC(6.0.3790.4675); Wed, 5 Jun 2013 17:48:40 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-Class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Wed, 5 Jun 2013 17:48:27 -0400
Message-ID: <64683B4805156847B0ED373DAB3057CA01B19E70@ottsrv0015.microsemi.net>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [TICTOC] comments on draft-ietf-tictoc-1588overmpls-04.txt
Thread-Index: AQHOHrvIG9Qp4DAEq0WS7lIAjM8M8JkmuDRwgAE3KqCAADsOgIAABF6w
References: <20130223072233.32735.89371.idtracker@ietfa.amsl.com> <64683B4805156847B0ED373DAB3057CA015E930D@ottsrv0015.microsemi.net> <4A6CE49E6084B141B15C0713B8993F281BE28013@SJEXCHMB12.corp.ad.broadcom.com> <64683B4805156847B0ED373DAB3057CA01B19D5F@ottsrv0015.microsemi.net> <4A6CE49E6084B141B15C0713B8993F281BE2FD85@SJEXCHMB12.corp.ad.broadcom.com>
From: "Meyer, Peter" <Peter.Meyer@microsemi.com>
To: Shahram Davari <davari@broadcom.com>, <tictoc@ietf.org>
X-OriginalArrivalTime: 05 Jun 2013 21:48:40.0352 (UTC) FILETIME=[70FA2200:01CE6236]
X-OriginatorOrg: microsemi.com
X-FOPE-CONNECTOR: Id%0$Dn%*$RO%0$TLS%0$FQDN%$TlsDn%
Subject: Re: [TICTOC] comments on draft-ietf-tictoc-1588overmpls-04.txt
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: Wed, 05 Jun 2013 21:49:01 -0000

Hi Shahram,

I took the -04 that was advertised on the exploder in February (dated
February 23, 2013).  I then edited that copy.

(I think the diff may show a ton of changes due to line length or word
wrapping).

Regards,
Peter


-----Original Message-----
From: Shahram Davari [mailto:davari@broadcom.com]=20
Sent: June 5, 2013 5:32 PM
To: Meyer, Peter; tictoc@ietf.org
Subject: RE: [TICTOC] comments on draft-ietf-tictoc-1588overmpls-04.txt

Thanks Peter.=20

These edits where done before the publishing of draft-04. Correct?

-Shahram

-----Original Message-----
From: Meyer, Peter [mailto:Peter.Meyer@microsemi.com]=20
Sent: Wednesday, June 05, 2013 11:01 AM
To: Shahram Davari; tictoc@ietf.org
Subject: RE: [TICTOC] comments on draft-ietf-tictoc-1588overmpls-04.txt

Hi Shahram,

I hope in-line with my comments I have edited the text of draft -04.

I'm not sure how the formatting worked out (PC-based, line length, page
length).

I modified sections 3, 4, 18, 19 & 20.

I include here both original and modified version so you can diff (most
of the changes in 3 are due to line length / re-org, not actual text
changes).

File attachment:
"draft-ietf-tictoc-1588overmpls-04-org.txt" (52 KB)
"draft-ietf-tictoc-1588overmpls-04-pm.txt" (53 KB)


Regards,
Peter


-----Original Message-----
From: Shahram Davari [mailto:davari@broadcom.com]=20
Sent: June 4, 2013 7:40 PM
To: Meyer, Peter; tictoc@ietf.org
Subject: RE: [TICTOC] comments on draft-ietf-tictoc-1588overmpls-04.txt

Hi Peter,

Thanks for your god comments. Please see my responses inline. Please let
me know whether you are satisfied with my responses since I am updating
the draft in the next couple of days.

Thanks
Shahram

-----Original Message-----
From: tictoc-bounces@ietf.org [mailto:tictoc-bounces@ietf.org] On Behalf
Of Meyer, Peter
Sent: Monday, March 11, 2013 5:49 PM
To: tictoc@ietf.org
Subject: Re: [TICTOC] comments on draft-ietf-tictoc-1588overmpls-04.txt

Hi Shahram et al,

Some comments on draft -04.


1) Section 3.  "A generic method is defined in this document that does
not require deep packet inspection at line rate, and can
deterministically identify Timing messages.  The generic method is
applicable to MPLS and MPLS-TP networks."

May want to add that this would apply only to one-step TC (I imagine
that is the point of the correction at line rate).  A two-step TC would
need to do deep packet inspection as it uses sourcePortIdentity &
sequenceId fields for Follow_up or Delay_Resp.

SD> For 2-step, all that is needed is for an interface to detect the
Timing message (based on top MPLS Label)  and record the Time along with
some information from the Timing packet and send them to CPU while
forwarding the Timing message as usual. Then the CPU based on the
information received generates Follow-up message and injects it in to
the LSP.  Therefore it is the job of CPU to look at sourcePortIdentity &
sequenceId fields not the Hardware.


2) Section 4.  "An MPLS domain can serve multiple customers.  This means
that the MPLS domain (maintained by a service provider) may provide
timing services to multiple customers, each having their own Timing
domain.  Therefore LER BCs need to interact with multiple grandmasters,
and consequently multiple time references."

This should be re-phrased.  It switches from an optional situation ("may
provide timing services") to mandatory situation ("LER BCs need to
interact").   Some words such as "in such a deployment scenario, ...."
and replace "can" with "may".   We have seen at ITU at least (with
participation from operators BT, FT, DT, CMCC, AT&T, Sprint, etc.) that
this multiple operator domain case was not useful enough to be included
in standardization process for Telecom networks.

SD> I rephrased it as following:

" An MPLS domain can serve multiple customers.  This means that the
   MPLS domain (maintained by a service provider) may provide timing
   services to multiple customers, each having their own Timing domain.
   Therefore in such deployment scenarios, LER BCs may interact with
multiple grandmasters,=20
and consequently multiple time references.  Also, LER/LSR TCs MUST be
synchronized to the=20
same master clock (which is the service provider Master clock), which
implies that they need=20
to choose one master to synchronize to."


3) Section 19.  "For transporting such peer delay measurement messages a
single-hop LSP SHOULD to be created between the two adjacent LSRs
engaged in peer delay measurement to carry peer delay measurement
messages. Other methods such as PTP transport over Ethernet MAY be used
for transporting peer delay measurement messages if the link between the
two routers is Ethernet."


This new statement to handle peer-delay (which in earlier drafts did not
have a communication path listed), also allows a BC to be embedded in an
LSR with a communication path between BC's as a single-hop LSP
(mentioned March 22, 2012 in my feedback to draft -03, subject "[TICTOC]
Updated 1588 over MPLS draf-03").

SD> When a single-hop LSP is created then I call the both ends of that
LSP, LERs and not LSRs.
Note that a router can act as LSR for some LSPs and LER for other LSPs.
The point is that we can't
Terminate a packet in the middle of an LSP (i.e., in an LSR). So BC
functionality can't exist in the middle
Of a PTP LSP. So I think it is a matter of terminology otherwise I agree
that you could have BC in the core
(not edge).=20

Architecture diagrams Figure 1 and Figure should be updated to reflect
the possibility of either BC or TC implementation.   Section 18.2 and
section 18.3 and section 21 should also be updated to reflect the
possibility of either BC or TC.  I understand the RFC is intended to be
generic and not targeted only at TC.



4) Section 20.  "When the MPLS network (provider network) serves
multiple customers, it is important to maintain and process each
customers clock and Timing messages separately from other customers to
ensure there is no cross- customer effect.   For example if an LER BC is
synchronized to a specific grandmaster, belonging to customer A, then
the LER MUST use that BC clock only for customer A to ensure that
customer A cannot attack other customers by manipulating its time."

This seems much more applicable to the TC LSR and should be stated.
>From section 4 we see the TC uses the primary synchronization domain
(that of the service provide) to correct PTP messages.

SD> I don't see how in a TC LSR, one customer timing can affect other
customer timings?
Since in a TC, we just update the Timestamp of a packet based on the
Service provider Time.
May be I have not understood your point. Could you please clarify with
an example.



5) Section 20.  "Timing messages (as opposed to regular customer data)
SHOULD not be encrypted or authenticated on an end-to-end basis."  I
think there is a security draft in parallel being developed that may be
relevant to that statement.

SD> I have updated the  text as following:

" Timing messages MAY be encrypted or authenticated, provided that the
LERs/LSRs that are Timing capable/aware can authenticate/ decrypt the
timing messages."




Regards,
Peter


-----Original Message-----
From: tictoc-bounces@ietf.org [mailto:tictoc-bounces@ietf.org] On Behalf
Of internet-drafts@ietf.org
Sent: February 23, 2013 2:23 AM
To: i-d-announce@ietf.org
Cc: tictoc@ietf.org
Subject: [TICTOC] I-D Action: draft-ietf-tictoc-1588overmpls-04.txt


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

	Title           : Transporting Timing messages over MPLS
Networks
	Author(s)       : Shahram Davari
                          Amit Oren
                          Manav Bhatia
                          Peter Roberts
                          Laurent Montini
	Filename        : draft-ietf-tictoc-1588overmpls-04.txt
	Pages           : 36
	Date            : 2013-02-22

Abstract:
   This document defines the method for transporting Timing messages
   such as PTP and NTP over an MPLS network.  The method allows for the
   easy identification of these PDUs at the port level to allow for port
   level processing of these PDUs in both LERs and LSRs.

   The basic idea is to transport Timing messages inside dedicated MPLS
   LSPs.  These LSPs only carry timing messages and possibly Control and
   Management packets, but they do not carry customer traffic.

   Two methods for transporting Timing messages over MPLS are defined.
   The first method is to transport Timing messages directly over the
   dedicated MPLS LSP via UDP/IP encapsulation, which is suitable for
   MPLS networks.  The second method is to transport Timing messages
   inside a PW via Ethernet encapsulation, which is suitable for both
   MPLS and MPLS-TP networks.


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

There's also a htmlized version available at:
http://tools.ietf.org/html/draft-ietf-tictoc-1588overmpls-04

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


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

_______________________________________________
TICTOC mailing list
TICTOC@ietf.org
https://www.ietf.org/mailman/listinfo/tictoc


_______________________________________________
TICTOC mailing list
TICTOC@ietf.org
https://www.ietf.org/mailman/listinfo/tictoc







From davari@broadcom.com  Wed Jun  5 15:16:02 2013
Return-Path: <davari@broadcom.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 4246B21E804C for <tictoc@ietfa.amsl.com>; Wed,  5 Jun 2013 15:16:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id GzjqePH--Deu for <tictoc@ietfa.amsl.com>; Wed,  5 Jun 2013 15:15:57 -0700 (PDT)
Received: from mms3.broadcom.com (mms3.broadcom.com [216.31.210.19]) by ietfa.amsl.com (Postfix) with ESMTP id CED8521E8050 for <tictoc@ietf.org>; Wed,  5 Jun 2013 15:15:53 -0700 (PDT)
Received: from [10.9.208.53] by mms3.broadcom.com with ESMTP (Broadcom SMTP Relay (Email Firewall v6.5)); Wed, 05 Jun 2013 15:06:44 -0700
X-Server-Uuid: B86B6450-0931-4310-942E-F00ED04CA7AF
Received: from SJEXCHCAS04.corp.ad.broadcom.com (10.16.203.10) by IRVEXCHCAS06.corp.ad.broadcom.com (10.9.208.53) with Microsoft SMTP Server (TLS) id 14.1.438.0; Wed, 5 Jun 2013 15:15:38 -0700
Received: from SJEXCHMB12.corp.ad.broadcom.com ( [fe80::bc15:c1e1:c29a:36f7]) by SJEXCHCAS04.corp.ad.broadcom.com ( [::1]) with mapi id 14.01.0438.000; Wed, 5 Jun 2013 15:15:38 -0700
From: "Shahram Davari" <davari@broadcom.com>
To: "Meyer, Peter" <Peter.Meyer@microsemi.com>, "tictoc@ietf.org" <tictoc@ietf.org>
Thread-Topic: [TICTOC] comments on draft-ietf-tictoc-1588overmpls-04.txt
Thread-Index: AQHOHrvIG9Qp4DAEq0WS7lIAjM8M8JkmuDRwgAE3KqCAADsOgIAABF6wgAAHahA=
Date: Wed, 5 Jun 2013 22:15:37 +0000
Message-ID: <4A6CE49E6084B141B15C0713B8993F281BE2FE15@SJEXCHMB12.corp.ad.broadcom.com>
References: <20130223072233.32735.89371.idtracker@ietfa.amsl.com> <64683B4805156847B0ED373DAB3057CA015E930D@ottsrv0015.microsemi.net> <4A6CE49E6084B141B15C0713B8993F281BE28013@SJEXCHMB12.corp.ad.broadcom.com> <64683B4805156847B0ED373DAB3057CA01B19D5F@ottsrv0015.microsemi.net> <4A6CE49E6084B141B15C0713B8993F281BE2FD85@SJEXCHMB12.corp.ad.broadcom.com> <64683B4805156847B0ED373DAB3057CA01B19E70@ottsrv0015.microsemi.net>
In-Reply-To: <64683B4805156847B0ED373DAB3057CA01B19E70@ottsrv0015.microsemi.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.16.203.100]
MIME-Version: 1.0
X-WSS-ID: 7DB169FE2L828382327-01-01
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Subject: Re: [TICTOC] comments on draft-ietf-tictoc-1588overmpls-04.txt
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: Wed, 05 Jun 2013 22:16:02 -0000

Hi Peter,

I see that the majority of changes are related to LSR BC. I personally don'=
t think this is possible, since we can't terminate packets in the middle of=
 an LSP. Could you please provide an example for your suggestion of using L=
SR BC? How are the 1588 timing messages terminated?

Thanks
Shahram

-----Original Message-----
From: Meyer, Peter [mailto:Peter.Meyer@microsemi.com]=20
Sent: Wednesday, June 05, 2013 2:48 PM
To: Shahram Davari; tictoc@ietf.org
Subject: RE: [TICTOC] comments on draft-ietf-tictoc-1588overmpls-04.txt


Hi Shahram,

I took the -04 that was advertised on the exploder in February (dated
February 23, 2013).  I then edited that copy.

(I think the diff may show a ton of changes due to line length or word
wrapping).

Regards,
Peter


-----Original Message-----
From: Shahram Davari [mailto:davari@broadcom.com]=20
Sent: June 5, 2013 5:32 PM
To: Meyer, Peter; tictoc@ietf.org
Subject: RE: [TICTOC] comments on draft-ietf-tictoc-1588overmpls-04.txt

Thanks Peter.=20

These edits where done before the publishing of draft-04. Correct?

-Shahram

-----Original Message-----
From: Meyer, Peter [mailto:Peter.Meyer@microsemi.com]=20
Sent: Wednesday, June 05, 2013 11:01 AM
To: Shahram Davari; tictoc@ietf.org
Subject: RE: [TICTOC] comments on draft-ietf-tictoc-1588overmpls-04.txt

Hi Shahram,

I hope in-line with my comments I have edited the text of draft -04.

I'm not sure how the formatting worked out (PC-based, line length, page
length).

I modified sections 3, 4, 18, 19 & 20.

I include here both original and modified version so you can diff (most
of the changes in 3 are due to line length / re-org, not actual text
changes).

File attachment:
"draft-ietf-tictoc-1588overmpls-04-org.txt" (52 KB)
"draft-ietf-tictoc-1588overmpls-04-pm.txt" (53 KB)


Regards,
Peter


-----Original Message-----
From: Shahram Davari [mailto:davari@broadcom.com]=20
Sent: June 4, 2013 7:40 PM
To: Meyer, Peter; tictoc@ietf.org
Subject: RE: [TICTOC] comments on draft-ietf-tictoc-1588overmpls-04.txt

Hi Peter,

Thanks for your god comments. Please see my responses inline. Please let
me know whether you are satisfied with my responses since I am updating
the draft in the next couple of days.

Thanks
Shahram

-----Original Message-----
From: tictoc-bounces@ietf.org [mailto:tictoc-bounces@ietf.org] On Behalf
Of Meyer, Peter
Sent: Monday, March 11, 2013 5:49 PM
To: tictoc@ietf.org
Subject: Re: [TICTOC] comments on draft-ietf-tictoc-1588overmpls-04.txt

Hi Shahram et al,

Some comments on draft -04.


1) Section 3.  "A generic method is defined in this document that does
not require deep packet inspection at line rate, and can
deterministically identify Timing messages.  The generic method is
applicable to MPLS and MPLS-TP networks."

May want to add that this would apply only to one-step TC (I imagine
that is the point of the correction at line rate).  A two-step TC would
need to do deep packet inspection as it uses sourcePortIdentity &
sequenceId fields for Follow_up or Delay_Resp.

SD> For 2-step, all that is needed is for an interface to detect the
Timing message (based on top MPLS Label)  and record the Time along with
some information from the Timing packet and send them to CPU while
forwarding the Timing message as usual. Then the CPU based on the
information received generates Follow-up message and injects it in to
the LSP.  Therefore it is the job of CPU to look at sourcePortIdentity &
sequenceId fields not the Hardware.


2) Section 4.  "An MPLS domain can serve multiple customers.  This means
that the MPLS domain (maintained by a service provider) may provide
timing services to multiple customers, each having their own Timing
domain.  Therefore LER BCs need to interact with multiple grandmasters,
and consequently multiple time references."

This should be re-phrased.  It switches from an optional situation ("may
provide timing services") to mandatory situation ("LER BCs need to
interact").   Some words such as "in such a deployment scenario, ...."
and replace "can" with "may".   We have seen at ITU at least (with
participation from operators BT, FT, DT, CMCC, AT&T, Sprint, etc.) that
this multiple operator domain case was not useful enough to be included
in standardization process for Telecom networks.

SD> I rephrased it as following:

" An MPLS domain can serve multiple customers.  This means that the
   MPLS domain (maintained by a service provider) may provide timing
   services to multiple customers, each having their own Timing domain.
   Therefore in such deployment scenarios, LER BCs may interact with
multiple grandmasters,=20
and consequently multiple time references.  Also, LER/LSR TCs MUST be
synchronized to the=20
same master clock (which is the service provider Master clock), which
implies that they need=20
to choose one master to synchronize to."


3) Section 19.  "For transporting such peer delay measurement messages a
single-hop LSP SHOULD to be created between the two adjacent LSRs
engaged in peer delay measurement to carry peer delay measurement
messages. Other methods such as PTP transport over Ethernet MAY be used
for transporting peer delay measurement messages if the link between the
two routers is Ethernet."


This new statement to handle peer-delay (which in earlier drafts did not
have a communication path listed), also allows a BC to be embedded in an
LSR with a communication path between BC's as a single-hop LSP
(mentioned March 22, 2012 in my feedback to draft -03, subject "[TICTOC]
Updated 1588 over MPLS draf-03").

SD> When a single-hop LSP is created then I call the both ends of that
LSP, LERs and not LSRs.
Note that a router can act as LSR for some LSPs and LER for other LSPs.
The point is that we can't
Terminate a packet in the middle of an LSP (i.e., in an LSR). So BC
functionality can't exist in the middle
Of a PTP LSP. So I think it is a matter of terminology otherwise I agree
that you could have BC in the core
(not edge).=20

Architecture diagrams Figure 1 and Figure should be updated to reflect
the possibility of either BC or TC implementation.   Section 18.2 and
section 18.3 and section 21 should also be updated to reflect the
possibility of either BC or TC.  I understand the RFC is intended to be
generic and not targeted only at TC.



4) Section 20.  "When the MPLS network (provider network) serves
multiple customers, it is important to maintain and process each
customers clock and Timing messages separately from other customers to
ensure there is no cross- customer effect.   For example if an LER BC is
synchronized to a specific grandmaster, belonging to customer A, then
the LER MUST use that BC clock only for customer A to ensure that
customer A cannot attack other customers by manipulating its time."

This seems much more applicable to the TC LSR and should be stated.
>From section 4 we see the TC uses the primary synchronization domain
(that of the service provide) to correct PTP messages.

SD> I don't see how in a TC LSR, one customer timing can affect other
customer timings?
Since in a TC, we just update the Timestamp of a packet based on the
Service provider Time.
May be I have not understood your point. Could you please clarify with
an example.



5) Section 20.  "Timing messages (as opposed to regular customer data)
SHOULD not be encrypted or authenticated on an end-to-end basis."  I
think there is a security draft in parallel being developed that may be
relevant to that statement.

SD> I have updated the  text as following:

" Timing messages MAY be encrypted or authenticated, provided that the
LERs/LSRs that are Timing capable/aware can authenticate/ decrypt the
timing messages."




Regards,
Peter


-----Original Message-----
From: tictoc-bounces@ietf.org [mailto:tictoc-bounces@ietf.org] On Behalf
Of internet-drafts@ietf.org
Sent: February 23, 2013 2:23 AM
To: i-d-announce@ietf.org
Cc: tictoc@ietf.org
Subject: [TICTOC] I-D Action: draft-ietf-tictoc-1588overmpls-04.txt


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

	Title           : Transporting Timing messages over MPLS
Networks
	Author(s)       : Shahram Davari
                          Amit Oren
                          Manav Bhatia
                          Peter Roberts
                          Laurent Montini
	Filename        : draft-ietf-tictoc-1588overmpls-04.txt
	Pages           : 36
	Date            : 2013-02-22

Abstract:
   This document defines the method for transporting Timing messages
   such as PTP and NTP over an MPLS network.  The method allows for the
   easy identification of these PDUs at the port level to allow for port
   level processing of these PDUs in both LERs and LSRs.

   The basic idea is to transport Timing messages inside dedicated MPLS
   LSPs.  These LSPs only carry timing messages and possibly Control and
   Management packets, but they do not carry customer traffic.

   Two methods for transporting Timing messages over MPLS are defined.
   The first method is to transport Timing messages directly over the
   dedicated MPLS LSP via UDP/IP encapsulation, which is suitable for
   MPLS networks.  The second method is to transport Timing messages
   inside a PW via Ethernet encapsulation, which is suitable for both
   MPLS and MPLS-TP networks.


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

There's also a htmlized version available at:
http://tools.ietf.org/html/draft-ietf-tictoc-1588overmpls-04

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


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

_______________________________________________
TICTOC mailing list
TICTOC@ietf.org
https://www.ietf.org/mailman/listinfo/tictoc


_______________________________________________
TICTOC mailing list
TICTOC@ietf.org
https://www.ietf.org/mailman/listinfo/tictoc









From davari@broadcom.com  Wed Jun  5 15:18:48 2013
Return-Path: <davari@broadcom.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 B2FAE21F998D for <tictoc@ietfa.amsl.com>; Wed,  5 Jun 2013 15:18:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Tw4c9bPP6Ipq for <tictoc@ietfa.amsl.com>; Wed,  5 Jun 2013 15:18:44 -0700 (PDT)
Received: from mms3.broadcom.com (mms3.broadcom.com [216.31.210.19]) by ietfa.amsl.com (Postfix) with ESMTP id E058921E8082 for <tictoc@ietf.org>; Wed,  5 Jun 2013 15:18:30 -0700 (PDT)
Received: from [10.9.208.53] by mms3.broadcom.com with ESMTP (Broadcom SMTP Relay (Email Firewall v6.5)); Wed, 05 Jun 2013 15:09:27 -0700
X-Server-Uuid: B86B6450-0931-4310-942E-F00ED04CA7AF
Received: from SJEXCHCAS04.corp.ad.broadcom.com (10.16.203.10) by IRVEXCHCAS06.corp.ad.broadcom.com (10.9.208.53) with Microsoft SMTP Server (TLS) id 14.1.438.0; Wed, 5 Jun 2013 15:18:21 -0700
Received: from SJEXCHMB12.corp.ad.broadcom.com ( [fe80::bc15:c1e1:c29a:36f7]) by SJEXCHCAS04.corp.ad.broadcom.com ( [::1]) with mapi id 14.01.0438.000; Wed, 5 Jun 2013 15:18:21 -0700
From: "Shahram Davari" <davari@broadcom.com>
To: "Meyer, Peter" <Peter.Meyer@microsemi.com>, "tictoc@ietf.org" <tictoc@ietf.org>
Thread-Topic: [TICTOC] comments on draft-ietf-tictoc-1588overmpls-04.txt
Thread-Index: AQHOHrvIG9Qp4DAEq0WS7lIAjM8M8JkmuDRwgAE3KqCAADsOgIAABF6wgAAHahCAAAEIcA==
Date: Wed, 5 Jun 2013 22:18:20 +0000
Message-ID: <4A6CE49E6084B141B15C0713B8993F281BE2FE6E@SJEXCHMB12.corp.ad.broadcom.com>
References: <20130223072233.32735.89371.idtracker@ietfa.amsl.com> <64683B4805156847B0ED373DAB3057CA015E930D@ottsrv0015.microsemi.net> <4A6CE49E6084B141B15C0713B8993F281BE28013@SJEXCHMB12.corp.ad.broadcom.com> <64683B4805156847B0ED373DAB3057CA01B19D5F@ottsrv0015.microsemi.net> <4A6CE49E6084B141B15C0713B8993F281BE2FD85@SJEXCHMB12.corp.ad.broadcom.com> <64683B4805156847B0ED373DAB3057CA01B19E70@ottsrv0015.microsemi.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.16.203.100]
MIME-Version: 1.0
X-WSS-ID: 7DB1689D2L828383571-01-01
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Subject: Re: [TICTOC] comments on draft-ietf-tictoc-1588overmpls-04.txt
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: Wed, 05 Jun 2013 22:18:48 -0000

Peter,

I think we have a difference in terminology. To me an LSR is a router that =
does Label Swap and not Label pop. May be what you have in mind is PE and P=
 routers instead of LER and LSR.=20

Thx
Shahram

-----Original Message-----
From: Shahram Davari=20
Sent: Wednesday, June 05, 2013 3:16 PM
To: 'Meyer, Peter'; tictoc@ietf.org
Subject: RE: [TICTOC] comments on draft-ietf-tictoc-1588overmpls-04.txt

Hi Peter,

I see that the majority of changes are related to LSR BC. I personally don'=
t think this is possible, since we can't terminate packets in the middle of=
 an LSP. Could you please provide an example for your suggestion of using L=
SR BC? How are the 1588 timing messages terminated?

Thanks
Shahram

-----Original Message-----
From: Meyer, Peter [mailto:Peter.Meyer@microsemi.com]=20
Sent: Wednesday, June 05, 2013 2:48 PM
To: Shahram Davari; tictoc@ietf.org
Subject: RE: [TICTOC] comments on draft-ietf-tictoc-1588overmpls-04.txt


Hi Shahram,

I took the -04 that was advertised on the exploder in February (dated
February 23, 2013).  I then edited that copy.

(I think the diff may show a ton of changes due to line length or word
wrapping).

Regards,
Peter


-----Original Message-----
From: Shahram Davari [mailto:davari@broadcom.com]=20
Sent: June 5, 2013 5:32 PM
To: Meyer, Peter; tictoc@ietf.org
Subject: RE: [TICTOC] comments on draft-ietf-tictoc-1588overmpls-04.txt

Thanks Peter.=20

These edits where done before the publishing of draft-04. Correct?

-Shahram

-----Original Message-----
From: Meyer, Peter [mailto:Peter.Meyer@microsemi.com]=20
Sent: Wednesday, June 05, 2013 11:01 AM
To: Shahram Davari; tictoc@ietf.org
Subject: RE: [TICTOC] comments on draft-ietf-tictoc-1588overmpls-04.txt

Hi Shahram,

I hope in-line with my comments I have edited the text of draft -04.

I'm not sure how the formatting worked out (PC-based, line length, page
length).

I modified sections 3, 4, 18, 19 & 20.

I include here both original and modified version so you can diff (most
of the changes in 3 are due to line length / re-org, not actual text
changes).

File attachment:
"draft-ietf-tictoc-1588overmpls-04-org.txt" (52 KB)
"draft-ietf-tictoc-1588overmpls-04-pm.txt" (53 KB)


Regards,
Peter


-----Original Message-----
From: Shahram Davari [mailto:davari@broadcom.com]=20
Sent: June 4, 2013 7:40 PM
To: Meyer, Peter; tictoc@ietf.org
Subject: RE: [TICTOC] comments on draft-ietf-tictoc-1588overmpls-04.txt

Hi Peter,

Thanks for your god comments. Please see my responses inline. Please let
me know whether you are satisfied with my responses since I am updating
the draft in the next couple of days.

Thanks
Shahram

-----Original Message-----
From: tictoc-bounces@ietf.org [mailto:tictoc-bounces@ietf.org] On Behalf
Of Meyer, Peter
Sent: Monday, March 11, 2013 5:49 PM
To: tictoc@ietf.org
Subject: Re: [TICTOC] comments on draft-ietf-tictoc-1588overmpls-04.txt

Hi Shahram et al,

Some comments on draft -04.


1) Section 3.  "A generic method is defined in this document that does
not require deep packet inspection at line rate, and can
deterministically identify Timing messages.  The generic method is
applicable to MPLS and MPLS-TP networks."

May want to add that this would apply only to one-step TC (I imagine
that is the point of the correction at line rate).  A two-step TC would
need to do deep packet inspection as it uses sourcePortIdentity &
sequenceId fields for Follow_up or Delay_Resp.

SD> For 2-step, all that is needed is for an interface to detect the
Timing message (based on top MPLS Label)  and record the Time along with
some information from the Timing packet and send them to CPU while
forwarding the Timing message as usual. Then the CPU based on the
information received generates Follow-up message and injects it in to
the LSP.  Therefore it is the job of CPU to look at sourcePortIdentity &
sequenceId fields not the Hardware.


2) Section 4.  "An MPLS domain can serve multiple customers.  This means
that the MPLS domain (maintained by a service provider) may provide
timing services to multiple customers, each having their own Timing
domain.  Therefore LER BCs need to interact with multiple grandmasters,
and consequently multiple time references."

This should be re-phrased.  It switches from an optional situation ("may
provide timing services") to mandatory situation ("LER BCs need to
interact").   Some words such as "in such a deployment scenario, ...."
and replace "can" with "may".   We have seen at ITU at least (with
participation from operators BT, FT, DT, CMCC, AT&T, Sprint, etc.) that
this multiple operator domain case was not useful enough to be included
in standardization process for Telecom networks.

SD> I rephrased it as following:

" An MPLS domain can serve multiple customers.  This means that the
   MPLS domain (maintained by a service provider) may provide timing
   services to multiple customers, each having their own Timing domain.
   Therefore in such deployment scenarios, LER BCs may interact with
multiple grandmasters,=20
and consequently multiple time references.  Also, LER/LSR TCs MUST be
synchronized to the=20
same master clock (which is the service provider Master clock), which
implies that they need=20
to choose one master to synchronize to."


3) Section 19.  "For transporting such peer delay measurement messages a
single-hop LSP SHOULD to be created between the two adjacent LSRs
engaged in peer delay measurement to carry peer delay measurement
messages. Other methods such as PTP transport over Ethernet MAY be used
for transporting peer delay measurement messages if the link between the
two routers is Ethernet."


This new statement to handle peer-delay (which in earlier drafts did not
have a communication path listed), also allows a BC to be embedded in an
LSR with a communication path between BC's as a single-hop LSP
(mentioned March 22, 2012 in my feedback to draft -03, subject "[TICTOC]
Updated 1588 over MPLS draf-03").

SD> When a single-hop LSP is created then I call the both ends of that
LSP, LERs and not LSRs.
Note that a router can act as LSR for some LSPs and LER for other LSPs.
The point is that we can't
Terminate a packet in the middle of an LSP (i.e., in an LSR). So BC
functionality can't exist in the middle
Of a PTP LSP. So I think it is a matter of terminology otherwise I agree
that you could have BC in the core
(not edge).=20

Architecture diagrams Figure 1 and Figure should be updated to reflect
the possibility of either BC or TC implementation.   Section 18.2 and
section 18.3 and section 21 should also be updated to reflect the
possibility of either BC or TC.  I understand the RFC is intended to be
generic and not targeted only at TC.



4) Section 20.  "When the MPLS network (provider network) serves
multiple customers, it is important to maintain and process each
customers clock and Timing messages separately from other customers to
ensure there is no cross- customer effect.   For example if an LER BC is
synchronized to a specific grandmaster, belonging to customer A, then
the LER MUST use that BC clock only for customer A to ensure that
customer A cannot attack other customers by manipulating its time."

This seems much more applicable to the TC LSR and should be stated.
>From section 4 we see the TC uses the primary synchronization domain
(that of the service provide) to correct PTP messages.

SD> I don't see how in a TC LSR, one customer timing can affect other
customer timings?
Since in a TC, we just update the Timestamp of a packet based on the
Service provider Time.
May be I have not understood your point. Could you please clarify with
an example.



5) Section 20.  "Timing messages (as opposed to regular customer data)
SHOULD not be encrypted or authenticated on an end-to-end basis."  I
think there is a security draft in parallel being developed that may be
relevant to that statement.

SD> I have updated the  text as following:

" Timing messages MAY be encrypted or authenticated, provided that the
LERs/LSRs that are Timing capable/aware can authenticate/ decrypt the
timing messages."




Regards,
Peter


-----Original Message-----
From: tictoc-bounces@ietf.org [mailto:tictoc-bounces@ietf.org] On Behalf
Of internet-drafts@ietf.org
Sent: February 23, 2013 2:23 AM
To: i-d-announce@ietf.org
Cc: tictoc@ietf.org
Subject: [TICTOC] I-D Action: draft-ietf-tictoc-1588overmpls-04.txt


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

	Title           : Transporting Timing messages over MPLS
Networks
	Author(s)       : Shahram Davari
                          Amit Oren
                          Manav Bhatia
                          Peter Roberts
                          Laurent Montini
	Filename        : draft-ietf-tictoc-1588overmpls-04.txt
	Pages           : 36
	Date            : 2013-02-22

Abstract:
   This document defines the method for transporting Timing messages
   such as PTP and NTP over an MPLS network.  The method allows for the
   easy identification of these PDUs at the port level to allow for port
   level processing of these PDUs in both LERs and LSRs.

   The basic idea is to transport Timing messages inside dedicated MPLS
   LSPs.  These LSPs only carry timing messages and possibly Control and
   Management packets, but they do not carry customer traffic.

   Two methods for transporting Timing messages over MPLS are defined.
   The first method is to transport Timing messages directly over the
   dedicated MPLS LSP via UDP/IP encapsulation, which is suitable for
   MPLS networks.  The second method is to transport Timing messages
   inside a PW via Ethernet encapsulation, which is suitable for both
   MPLS and MPLS-TP networks.


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

There's also a htmlized version available at:
http://tools.ietf.org/html/draft-ietf-tictoc-1588overmpls-04

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


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

_______________________________________________
TICTOC mailing list
TICTOC@ietf.org
https://www.ietf.org/mailman/listinfo/tictoc


_______________________________________________
TICTOC mailing list
TICTOC@ietf.org
https://www.ietf.org/mailman/listinfo/tictoc









From Peter.Meyer@microsemi.com  Wed Jun  5 15:35:50 2013
Return-Path: <Peter.Meyer@microsemi.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 C139511E80AE for <tictoc@ietfa.amsl.com>; Wed,  5 Jun 2013 15:35:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.432
X-Spam-Level: 
X-Spam-Status: No, score=-5.432 tagged_above=-999 required=5 tests=[AWL=1.167,  BAYES_00=-2.599, 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 VZ-V60-JdHLj for <tictoc@ietfa.amsl.com>; Wed,  5 Jun 2013 15:35:45 -0700 (PDT)
Received: from co9outboundpool.messaging.microsoft.com (co9ehsobe001.messaging.microsoft.com [207.46.163.24]) by ietfa.amsl.com (Postfix) with ESMTP id 4F47D21F8EEA for <tictoc@ietf.org>; Wed,  5 Jun 2013 15:35:45 -0700 (PDT)
Received: from mail68-co9-R.bigfish.com (10.236.132.237) by CO9EHSOBE003.bigfish.com (10.236.130.66) with Microsoft SMTP Server id 14.1.225.23; Wed, 5 Jun 2013 22:35:22 +0000
Received: from mail68-co9 (localhost [127.0.0.1])	by mail68-co9-R.bigfish.com (Postfix) with ESMTP id 0D92C1800EA; Wed,  5 Jun 2013 22:35:22 +0000 (UTC)
X-Forefront-Antispam-Report: CIP:209.226.172.12; KIP:(null); UIP:(null); IPV:NLI; H:ottsrv0014.microsemi.net; RD:none; EFVD:NLI
X-SpamScore: -23
X-BigFish: VS-23(zz9371I936eI542Izz1f42h1ee6h1de0h1fdah1202h1e76h1d1ah1d2ah1fc6hzz1033IL17326ah8275dhz2dh668h839h944hd25hf0ah1220h1288h12a5h12a9h12bdh137ah13b6h1441h14ddh1504h1537h153bh15d0h162dh1631h1758h184fh18e1h1946h19b5h1ad9h1b0ah1c24h1d0ch1d2eh1d3fh1dfeh1dffh1e1dh1155h)
Received: from mail68-co9 (localhost.localdomain [127.0.0.1]) by mail68-co9 (MessageSwitch) id 1370471720808437_4304; Wed,  5 Jun 2013 22:35:20 +0000 (UTC)
Received: from CO9EHSMHS029.bigfish.com (unknown [10.236.132.250])	by mail68-co9.bigfish.com (Postfix) with ESMTP id C338A2E0080; Wed,  5 Jun 2013 22:35:20 +0000 (UTC)
Received: from ottsrv0014.microsemi.net (209.226.172.12) by CO9EHSMHS029.bigfish.com (10.236.130.39) with Microsoft SMTP Server id 14.1.225.23; Wed, 5 Jun 2013 22:35:20 +0000
Received: from ottsrv0015.microsemi.net ([134.199.15.151]) by ottsrv0014.microsemi.net with Microsoft SMTPSVC(6.0.3790.4675); Wed, 5 Jun 2013 18:35:19 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-Class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Wed, 5 Jun 2013 18:35:06 -0400
Message-ID: <64683B4805156847B0ED373DAB3057CA01B19E80@ottsrv0015.microsemi.net>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [TICTOC] comments on draft-ietf-tictoc-1588overmpls-04.txt
Thread-Index: AQHOHrvIG9Qp4DAEq0WS7lIAjM8M8JkmuDRwgAE3KqCAADsOgIAABF6wgAAHahCAAAEIcIAAAdVw
References: <20130223072233.32735.89371.idtracker@ietfa.amsl.com> <64683B4805156847B0ED373DAB3057CA015E930D@ottsrv0015.microsemi.net> <4A6CE49E6084B141B15C0713B8993F281BE28013@SJEXCHMB12.corp.ad.broadcom.com> <64683B4805156847B0ED373DAB3057CA01B19D5F@ottsrv0015.microsemi.net> <4A6CE49E6084B141B15C0713B8993F281BE2FD85@SJEXCHMB12.corp.ad.broadcom.com> <64683B4805156847B0ED373DAB3057CA01B19E70@ottsrv0015.microsemi.net> <4A6CE49E6084B141B15C0713B8993F281BE2FE6E@SJEXCHMB12.corp.ad.broadcom.com>
From: "Meyer, Peter" <Peter.Meyer@microsemi.com>
To: Shahram Davari <davari@broadcom.com>, <tictoc@ietf.org>
X-OriginalArrivalTime: 05 Jun 2013 22:35:19.0922 (UTC) FILETIME=[F5A69D20:01CE623C]
X-OriginatorOrg: microsemi.com
Subject: Re: [TICTOC] comments on draft-ietf-tictoc-1588overmpls-04.txt
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: Wed, 05 Jun 2013 22:35:50 -0000

Hi Shahram,

I attempted to elaborate in section 19 Other Considerations, perhaps it
is not well written.  I tried to mirror the language that already
existed.


With the original -04 draft, section 19 covered the situation for an LSR
acting as a TC when using peer-delay messages.   An LSR would have to
generate & terminate peer-delay messages from its physical neighbour,
and the recommendation was to use a single-hop LSP.  With your
terminology, if I am using it correctly, the Sync messages are switched
through the LSR without termination.   However, this is not allowed for
peer-delay messages which must be terminated for the TC to function
properly.

"  For transporting such peer delay measurement messages a single-hop
   LSP SHOULD to be created between the two adjacent LSRs engaged in
   peer delay measurement to carry peer delay measurement messages.
   Other methods such as PTP transport over Ethernet MAY be used for
   transporting peer delay measurement messages if the link between the
   two routers is Ethernet.  "


I use this same approach for an LSR acting as a BC.   A BC inside an LSR
is the same as a peer-delay TC inside an LSR.  The LSR would have to
generate & terminate end-to-end messages from its physical neighbour. I
modified the section to recommend a single-hop LSP for this purpose.

"  Likewise for BCs embedded in an LSR, a single-hop LSP SHOULD be=20
   created between the two adjacent LSRs that are acting as BCs.  Other
   methods such as PTP transport over Ethernet MAY be used if the link
   between the two routers is Ethernet.  "


Hope this makes sense.

Regards,
Peter


-----Original Message-----
From: Shahram Davari [mailto:davari@broadcom.com]=20
Sent: June 5, 2013 6:18 PM
To: Meyer, Peter; tictoc@ietf.org
Subject: RE: [TICTOC] comments on draft-ietf-tictoc-1588overmpls-04.txt

Peter,

I think we have a difference in terminology. To me an LSR is a router
that does Label Swap and not Label pop. May be what you have in mind is
PE and P routers instead of LER and LSR.=20

Thx
Shahram

-----Original Message-----
From: Shahram Davari=20
Sent: Wednesday, June 05, 2013 3:16 PM
To: 'Meyer, Peter'; tictoc@ietf.org
Subject: RE: [TICTOC] comments on draft-ietf-tictoc-1588overmpls-04.txt

Hi Peter,

I see that the majority of changes are related to LSR BC. I personally
don't think this is possible, since we can't terminate packets in the
middle of an LSP. Could you please provide an example for your
suggestion of using LSR BC? How are the 1588 timing messages terminated?

Thanks
Shahram

-----Original Message-----
From: Meyer, Peter [mailto:Peter.Meyer@microsemi.com]=20
Sent: Wednesday, June 05, 2013 2:48 PM
To: Shahram Davari; tictoc@ietf.org
Subject: RE: [TICTOC] comments on draft-ietf-tictoc-1588overmpls-04.txt


Hi Shahram,

I took the -04 that was advertised on the exploder in February (dated
February 23, 2013).  I then edited that copy.

(I think the diff may show a ton of changes due to line length or word
wrapping).

Regards,
Peter


-----Original Message-----
From: Shahram Davari [mailto:davari@broadcom.com]=20
Sent: June 5, 2013 5:32 PM
To: Meyer, Peter; tictoc@ietf.org
Subject: RE: [TICTOC] comments on draft-ietf-tictoc-1588overmpls-04.txt

Thanks Peter.=20

These edits where done before the publishing of draft-04. Correct?

-Shahram

-----Original Message-----
From: Meyer, Peter [mailto:Peter.Meyer@microsemi.com]=20
Sent: Wednesday, June 05, 2013 11:01 AM
To: Shahram Davari; tictoc@ietf.org
Subject: RE: [TICTOC] comments on draft-ietf-tictoc-1588overmpls-04.txt

Hi Shahram,

I hope in-line with my comments I have edited the text of draft -04.

I'm not sure how the formatting worked out (PC-based, line length, page
length).

I modified sections 3, 4, 18, 19 & 20.

I include here both original and modified version so you can diff (most
of the changes in 3 are due to line length / re-org, not actual text
changes).

File attachment:
"draft-ietf-tictoc-1588overmpls-04-org.txt" (52 KB)
"draft-ietf-tictoc-1588overmpls-04-pm.txt" (53 KB)


Regards,
Peter


-----Original Message-----
From: Shahram Davari [mailto:davari@broadcom.com]=20
Sent: June 4, 2013 7:40 PM
To: Meyer, Peter; tictoc@ietf.org
Subject: RE: [TICTOC] comments on draft-ietf-tictoc-1588overmpls-04.txt

Hi Peter,

Thanks for your god comments. Please see my responses inline. Please let
me know whether you are satisfied with my responses since I am updating
the draft in the next couple of days.

Thanks
Shahram

-----Original Message-----
From: tictoc-bounces@ietf.org [mailto:tictoc-bounces@ietf.org] On Behalf
Of Meyer, Peter
Sent: Monday, March 11, 2013 5:49 PM
To: tictoc@ietf.org
Subject: Re: [TICTOC] comments on draft-ietf-tictoc-1588overmpls-04.txt

Hi Shahram et al,

Some comments on draft -04.


1) Section 3.  "A generic method is defined in this document that does
not require deep packet inspection at line rate, and can
deterministically identify Timing messages.  The generic method is
applicable to MPLS and MPLS-TP networks."

May want to add that this would apply only to one-step TC (I imagine
that is the point of the correction at line rate).  A two-step TC would
need to do deep packet inspection as it uses sourcePortIdentity &
sequenceId fields for Follow_up or Delay_Resp.

SD> For 2-step, all that is needed is for an interface to detect the
Timing message (based on top MPLS Label)  and record the Time along with
some information from the Timing packet and send them to CPU while
forwarding the Timing message as usual. Then the CPU based on the
information received generates Follow-up message and injects it in to
the LSP.  Therefore it is the job of CPU to look at sourcePortIdentity &
sequenceId fields not the Hardware.


2) Section 4.  "An MPLS domain can serve multiple customers.  This means
that the MPLS domain (maintained by a service provider) may provide
timing services to multiple customers, each having their own Timing
domain.  Therefore LER BCs need to interact with multiple grandmasters,
and consequently multiple time references."

This should be re-phrased.  It switches from an optional situation ("may
provide timing services") to mandatory situation ("LER BCs need to
interact").   Some words such as "in such a deployment scenario, ...."
and replace "can" with "may".   We have seen at ITU at least (with
participation from operators BT, FT, DT, CMCC, AT&T, Sprint, etc.) that
this multiple operator domain case was not useful enough to be included
in standardization process for Telecom networks.

SD> I rephrased it as following:

" An MPLS domain can serve multiple customers.  This means that the
   MPLS domain (maintained by a service provider) may provide timing
   services to multiple customers, each having their own Timing domain.
   Therefore in such deployment scenarios, LER BCs may interact with
multiple grandmasters,=20
and consequently multiple time references.  Also, LER/LSR TCs MUST be
synchronized to the=20
same master clock (which is the service provider Master clock), which
implies that they need=20
to choose one master to synchronize to."


3) Section 19.  "For transporting such peer delay measurement messages a
single-hop LSP SHOULD to be created between the two adjacent LSRs
engaged in peer delay measurement to carry peer delay measurement
messages. Other methods such as PTP transport over Ethernet MAY be used
for transporting peer delay measurement messages if the link between the
two routers is Ethernet."


This new statement to handle peer-delay (which in earlier drafts did not
have a communication path listed), also allows a BC to be embedded in an
LSR with a communication path between BC's as a single-hop LSP
(mentioned March 22, 2012 in my feedback to draft -03, subject "[TICTOC]
Updated 1588 over MPLS draf-03").

SD> When a single-hop LSP is created then I call the both ends of that
LSP, LERs and not LSRs.
Note that a router can act as LSR for some LSPs and LER for other LSPs.
The point is that we can't
Terminate a packet in the middle of an LSP (i.e., in an LSR). So BC
functionality can't exist in the middle
Of a PTP LSP. So I think it is a matter of terminology otherwise I agree
that you could have BC in the core
(not edge).=20

Architecture diagrams Figure 1 and Figure should be updated to reflect
the possibility of either BC or TC implementation.   Section 18.2 and
section 18.3 and section 21 should also be updated to reflect the
possibility of either BC or TC.  I understand the RFC is intended to be
generic and not targeted only at TC.



4) Section 20.  "When the MPLS network (provider network) serves
multiple customers, it is important to maintain and process each
customers clock and Timing messages separately from other customers to
ensure there is no cross- customer effect.   For example if an LER BC is
synchronized to a specific grandmaster, belonging to customer A, then
the LER MUST use that BC clock only for customer A to ensure that
customer A cannot attack other customers by manipulating its time."

This seems much more applicable to the TC LSR and should be stated.
>From section 4 we see the TC uses the primary synchronization domain
(that of the service provide) to correct PTP messages.

SD> I don't see how in a TC LSR, one customer timing can affect other
customer timings?
Since in a TC, we just update the Timestamp of a packet based on the
Service provider Time.
May be I have not understood your point. Could you please clarify with
an example.



5) Section 20.  "Timing messages (as opposed to regular customer data)
SHOULD not be encrypted or authenticated on an end-to-end basis."  I
think there is a security draft in parallel being developed that may be
relevant to that statement.

SD> I have updated the  text as following:

" Timing messages MAY be encrypted or authenticated, provided that the
LERs/LSRs that are Timing capable/aware can authenticate/ decrypt the
timing messages."




Regards,
Peter


-----Original Message-----
From: tictoc-bounces@ietf.org [mailto:tictoc-bounces@ietf.org] On Behalf
Of internet-drafts@ietf.org
Sent: February 23, 2013 2:23 AM
To: i-d-announce@ietf.org
Cc: tictoc@ietf.org
Subject: [TICTOC] I-D Action: draft-ietf-tictoc-1588overmpls-04.txt


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

	Title           : Transporting Timing messages over MPLS
Networks
	Author(s)       : Shahram Davari
                          Amit Oren
                          Manav Bhatia
                          Peter Roberts
                          Laurent Montini
	Filename        : draft-ietf-tictoc-1588overmpls-04.txt
	Pages           : 36
	Date            : 2013-02-22

Abstract:
   This document defines the method for transporting Timing messages
   such as PTP and NTP over an MPLS network.  The method allows for the
   easy identification of these PDUs at the port level to allow for port
   level processing of these PDUs in both LERs and LSRs.

   The basic idea is to transport Timing messages inside dedicated MPLS
   LSPs.  These LSPs only carry timing messages and possibly Control and
   Management packets, but they do not carry customer traffic.

   Two methods for transporting Timing messages over MPLS are defined.
   The first method is to transport Timing messages directly over the
   dedicated MPLS LSP via UDP/IP encapsulation, which is suitable for
   MPLS networks.  The second method is to transport Timing messages
   inside a PW via Ethernet encapsulation, which is suitable for both
   MPLS and MPLS-TP networks.


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

There's also a htmlized version available at:
http://tools.ietf.org/html/draft-ietf-tictoc-1588overmpls-04

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


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

_______________________________________________
TICTOC mailing list
TICTOC@ietf.org
https://www.ietf.org/mailman/listinfo/tictoc


_______________________________________________
TICTOC mailing list
TICTOC@ietf.org
https://www.ietf.org/mailman/listinfo/tictoc











From davari@broadcom.com  Wed Jun  5 15:44:39 2013
Return-Path: <davari@broadcom.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 6B4AD11E80C5 for <tictoc@ietfa.amsl.com>; Wed,  5 Jun 2013 15:44:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[AWL=0.000,  BAYES_00=-2.599, 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 PTpsBhxjKuyS for <tictoc@ietfa.amsl.com>; Wed,  5 Jun 2013 15:43:53 -0700 (PDT)
Received: from mms1.broadcom.com (mms1.broadcom.com [216.31.210.17]) by ietfa.amsl.com (Postfix) with ESMTP id 2BF1B21F963F for <tictoc@ietf.org>; Wed,  5 Jun 2013 15:43:53 -0700 (PDT)
Received: from [10.9.208.53] by mms1.broadcom.com with ESMTP (Broadcom SMTP Relay (Email Firewall v6.5)); Wed, 05 Jun 2013 15:40:08 -0700
X-Server-Uuid: 06151B78-6688-425E-9DE2-57CB27892261
Received: from SJEXCHCAS07.corp.ad.broadcom.com (10.16.203.16) by IRVEXCHCAS06.corp.ad.broadcom.com (10.9.208.53) with Microsoft SMTP Server (TLS) id 14.1.438.0; Wed, 5 Jun 2013 15:42:41 -0700
Received: from SJEXCHMB12.corp.ad.broadcom.com ( [fe80::bc15:c1e1:c29a:36f7]) by SJEXCHCAS07.corp.ad.broadcom.com ( [::1]) with mapi id 14.01.0438.000; Wed, 5 Jun 2013 15:42:41 -0700
From: "Shahram Davari" <davari@broadcom.com>
To: "Meyer, Peter" <Peter.Meyer@microsemi.com>, "tictoc@ietf.org" <tictoc@ietf.org>
Thread-Topic: [TICTOC] comments on draft-ietf-tictoc-1588overmpls-04.txt
Thread-Index: AQHOHrvIG9Qp4DAEq0WS7lIAjM8M8JkmuDRwgAE3KqCAADsOgIAABF6wgAAHahCAAAEIcIAAAdVwgAAFM5A=
Date: Wed, 5 Jun 2013 22:42:41 +0000
Message-ID: <4A6CE49E6084B141B15C0713B8993F281BE2FED7@SJEXCHMB12.corp.ad.broadcom.com>
References: <20130223072233.32735.89371.idtracker@ietfa.amsl.com> <64683B4805156847B0ED373DAB3057CA015E930D@ottsrv0015.microsemi.net> <4A6CE49E6084B141B15C0713B8993F281BE28013@SJEXCHMB12.corp.ad.broadcom.com> <64683B4805156847B0ED373DAB3057CA01B19D5F@ottsrv0015.microsemi.net> <4A6CE49E6084B141B15C0713B8993F281BE2FD85@SJEXCHMB12.corp.ad.broadcom.com> <64683B4805156847B0ED373DAB3057CA01B19E70@ottsrv0015.microsemi.net> <4A6CE49E6084B141B15C0713B8993F281BE2FE6E@SJEXCHMB12.corp.ad.broadcom.com> <64683B4805156847B0ED373DAB3057CA01B19E80@ottsrv0015.microsemi.net>
In-Reply-To: <64683B4805156847B0ED373DAB3057CA01B19E80@ottsrv0015.microsemi.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.16.203.100]
MIME-Version: 1.0
X-WSS-ID: 7DB161C231W31978437-15-01
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Subject: Re: [TICTOC] comments on draft-ietf-tictoc-1588overmpls-04.txt
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: Wed, 05 Jun 2013 22:44:39 -0000

Hi Peter,

Thanks, now I get it.  I will update the draft as per your suggestion.

Thx
Shahram

-----Original Message-----
From: Meyer, Peter [mailto:Peter.Meyer@microsemi.com]=20
Sent: Wednesday, June 05, 2013 3:35 PM
To: Shahram Davari; tictoc@ietf.org
Subject: RE: [TICTOC] comments on draft-ietf-tictoc-1588overmpls-04.txt


Hi Shahram,

I attempted to elaborate in section 19 Other Considerations, perhaps it
is not well written.  I tried to mirror the language that already
existed.


With the original -04 draft, section 19 covered the situation for an LSR
acting as a TC when using peer-delay messages.   An LSR would have to
generate & terminate peer-delay messages from its physical neighbour,
and the recommendation was to use a single-hop LSP.  With your
terminology, if I am using it correctly, the Sync messages are switched
through the LSR without termination.   However, this is not allowed for
peer-delay messages which must be terminated for the TC to function
properly.

"  For transporting such peer delay measurement messages a single-hop
   LSP SHOULD to be created between the two adjacent LSRs engaged in
   peer delay measurement to carry peer delay measurement messages.
   Other methods such as PTP transport over Ethernet MAY be used for
   transporting peer delay measurement messages if the link between the
   two routers is Ethernet.  "


I use this same approach for an LSR acting as a BC.   A BC inside an LSR
is the same as a peer-delay TC inside an LSR.  The LSR would have to
generate & terminate end-to-end messages from its physical neighbour. I
modified the section to recommend a single-hop LSP for this purpose.

"  Likewise for BCs embedded in an LSR, a single-hop LSP SHOULD be=20
   created between the two adjacent LSRs that are acting as BCs.  Other
   methods such as PTP transport over Ethernet MAY be used if the link
   between the two routers is Ethernet.  "


Hope this makes sense.

Regards,
Peter


-----Original Message-----
From: Shahram Davari [mailto:davari@broadcom.com]=20
Sent: June 5, 2013 6:18 PM
To: Meyer, Peter; tictoc@ietf.org
Subject: RE: [TICTOC] comments on draft-ietf-tictoc-1588overmpls-04.txt

Peter,

I think we have a difference in terminology. To me an LSR is a router
that does Label Swap and not Label pop. May be what you have in mind is
PE and P routers instead of LER and LSR.=20

Thx
Shahram

-----Original Message-----
From: Shahram Davari=20
Sent: Wednesday, June 05, 2013 3:16 PM
To: 'Meyer, Peter'; tictoc@ietf.org
Subject: RE: [TICTOC] comments on draft-ietf-tictoc-1588overmpls-04.txt

Hi Peter,

I see that the majority of changes are related to LSR BC. I personally
don't think this is possible, since we can't terminate packets in the
middle of an LSP. Could you please provide an example for your
suggestion of using LSR BC? How are the 1588 timing messages terminated?

Thanks
Shahram

-----Original Message-----
From: Meyer, Peter [mailto:Peter.Meyer@microsemi.com]=20
Sent: Wednesday, June 05, 2013 2:48 PM
To: Shahram Davari; tictoc@ietf.org
Subject: RE: [TICTOC] comments on draft-ietf-tictoc-1588overmpls-04.txt


Hi Shahram,

I took the -04 that was advertised on the exploder in February (dated
February 23, 2013).  I then edited that copy.

(I think the diff may show a ton of changes due to line length or word
wrapping).

Regards,
Peter


-----Original Message-----
From: Shahram Davari [mailto:davari@broadcom.com]=20
Sent: June 5, 2013 5:32 PM
To: Meyer, Peter; tictoc@ietf.org
Subject: RE: [TICTOC] comments on draft-ietf-tictoc-1588overmpls-04.txt

Thanks Peter.=20

These edits where done before the publishing of draft-04. Correct?

-Shahram

-----Original Message-----
From: Meyer, Peter [mailto:Peter.Meyer@microsemi.com]=20
Sent: Wednesday, June 05, 2013 11:01 AM
To: Shahram Davari; tictoc@ietf.org
Subject: RE: [TICTOC] comments on draft-ietf-tictoc-1588overmpls-04.txt

Hi Shahram,

I hope in-line with my comments I have edited the text of draft -04.

I'm not sure how the formatting worked out (PC-based, line length, page
length).

I modified sections 3, 4, 18, 19 & 20.

I include here both original and modified version so you can diff (most
of the changes in 3 are due to line length / re-org, not actual text
changes).

File attachment:
"draft-ietf-tictoc-1588overmpls-04-org.txt" (52 KB)
"draft-ietf-tictoc-1588overmpls-04-pm.txt" (53 KB)


Regards,
Peter


-----Original Message-----
From: Shahram Davari [mailto:davari@broadcom.com]=20
Sent: June 4, 2013 7:40 PM
To: Meyer, Peter; tictoc@ietf.org
Subject: RE: [TICTOC] comments on draft-ietf-tictoc-1588overmpls-04.txt

Hi Peter,

Thanks for your god comments. Please see my responses inline. Please let
me know whether you are satisfied with my responses since I am updating
the draft in the next couple of days.

Thanks
Shahram

-----Original Message-----
From: tictoc-bounces@ietf.org [mailto:tictoc-bounces@ietf.org] On Behalf
Of Meyer, Peter
Sent: Monday, March 11, 2013 5:49 PM
To: tictoc@ietf.org
Subject: Re: [TICTOC] comments on draft-ietf-tictoc-1588overmpls-04.txt

Hi Shahram et al,

Some comments on draft -04.


1) Section 3.  "A generic method is defined in this document that does
not require deep packet inspection at line rate, and can
deterministically identify Timing messages.  The generic method is
applicable to MPLS and MPLS-TP networks."

May want to add that this would apply only to one-step TC (I imagine
that is the point of the correction at line rate).  A two-step TC would
need to do deep packet inspection as it uses sourcePortIdentity &
sequenceId fields for Follow_up or Delay_Resp.

SD> For 2-step, all that is needed is for an interface to detect the
Timing message (based on top MPLS Label)  and record the Time along with
some information from the Timing packet and send them to CPU while
forwarding the Timing message as usual. Then the CPU based on the
information received generates Follow-up message and injects it in to
the LSP.  Therefore it is the job of CPU to look at sourcePortIdentity &
sequenceId fields not the Hardware.


2) Section 4.  "An MPLS domain can serve multiple customers.  This means
that the MPLS domain (maintained by a service provider) may provide
timing services to multiple customers, each having their own Timing
domain.  Therefore LER BCs need to interact with multiple grandmasters,
and consequently multiple time references."

This should be re-phrased.  It switches from an optional situation ("may
provide timing services") to mandatory situation ("LER BCs need to
interact").   Some words such as "in such a deployment scenario, ...."
and replace "can" with "may".   We have seen at ITU at least (with
participation from operators BT, FT, DT, CMCC, AT&T, Sprint, etc.) that
this multiple operator domain case was not useful enough to be included
in standardization process for Telecom networks.

SD> I rephrased it as following:

" An MPLS domain can serve multiple customers.  This means that the
   MPLS domain (maintained by a service provider) may provide timing
   services to multiple customers, each having their own Timing domain.
   Therefore in such deployment scenarios, LER BCs may interact with
multiple grandmasters,=20
and consequently multiple time references.  Also, LER/LSR TCs MUST be
synchronized to the=20
same master clock (which is the service provider Master clock), which
implies that they need=20
to choose one master to synchronize to."


3) Section 19.  "For transporting such peer delay measurement messages a
single-hop LSP SHOULD to be created between the two adjacent LSRs
engaged in peer delay measurement to carry peer delay measurement
messages. Other methods such as PTP transport over Ethernet MAY be used
for transporting peer delay measurement messages if the link between the
two routers is Ethernet."


This new statement to handle peer-delay (which in earlier drafts did not
have a communication path listed), also allows a BC to be embedded in an
LSR with a communication path between BC's as a single-hop LSP
(mentioned March 22, 2012 in my feedback to draft -03, subject "[TICTOC]
Updated 1588 over MPLS draf-03").

SD> When a single-hop LSP is created then I call the both ends of that
LSP, LERs and not LSRs.
Note that a router can act as LSR for some LSPs and LER for other LSPs.
The point is that we can't
Terminate a packet in the middle of an LSP (i.e., in an LSR). So BC
functionality can't exist in the middle
Of a PTP LSP. So I think it is a matter of terminology otherwise I agree
that you could have BC in the core
(not edge).=20

Architecture diagrams Figure 1 and Figure should be updated to reflect
the possibility of either BC or TC implementation.   Section 18.2 and
section 18.3 and section 21 should also be updated to reflect the
possibility of either BC or TC.  I understand the RFC is intended to be
generic and not targeted only at TC.



4) Section 20.  "When the MPLS network (provider network) serves
multiple customers, it is important to maintain and process each
customers clock and Timing messages separately from other customers to
ensure there is no cross- customer effect.   For example if an LER BC is
synchronized to a specific grandmaster, belonging to customer A, then
the LER MUST use that BC clock only for customer A to ensure that
customer A cannot attack other customers by manipulating its time."

This seems much more applicable to the TC LSR and should be stated.
>From section 4 we see the TC uses the primary synchronization domain
(that of the service provide) to correct PTP messages.

SD> I don't see how in a TC LSR, one customer timing can affect other
customer timings?
Since in a TC, we just update the Timestamp of a packet based on the
Service provider Time.
May be I have not understood your point. Could you please clarify with
an example.



5) Section 20.  "Timing messages (as opposed to regular customer data)
SHOULD not be encrypted or authenticated on an end-to-end basis."  I
think there is a security draft in parallel being developed that may be
relevant to that statement.

SD> I have updated the  text as following:

" Timing messages MAY be encrypted or authenticated, provided that the
LERs/LSRs that are Timing capable/aware can authenticate/ decrypt the
timing messages."




Regards,
Peter


-----Original Message-----
From: tictoc-bounces@ietf.org [mailto:tictoc-bounces@ietf.org] On Behalf
Of internet-drafts@ietf.org
Sent: February 23, 2013 2:23 AM
To: i-d-announce@ietf.org
Cc: tictoc@ietf.org
Subject: [TICTOC] I-D Action: draft-ietf-tictoc-1588overmpls-04.txt


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

	Title           : Transporting Timing messages over MPLS
Networks
	Author(s)       : Shahram Davari
                          Amit Oren
                          Manav Bhatia
                          Peter Roberts
                          Laurent Montini
	Filename        : draft-ietf-tictoc-1588overmpls-04.txt
	Pages           : 36
	Date            : 2013-02-22

Abstract:
   This document defines the method for transporting Timing messages
   such as PTP and NTP over an MPLS network.  The method allows for the
   easy identification of these PDUs at the port level to allow for port
   level processing of these PDUs in both LERs and LSRs.

   The basic idea is to transport Timing messages inside dedicated MPLS
   LSPs.  These LSPs only carry timing messages and possibly Control and
   Management packets, but they do not carry customer traffic.

   Two methods for transporting Timing messages over MPLS are defined.
   The first method is to transport Timing messages directly over the
   dedicated MPLS LSP via UDP/IP encapsulation, which is suitable for
   MPLS networks.  The second method is to transport Timing messages
   inside a PW via Ethernet encapsulation, which is suitable for both
   MPLS and MPLS-TP networks.


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

There's also a htmlized version available at:
http://tools.ietf.org/html/draft-ietf-tictoc-1588overmpls-04

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


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

_______________________________________________
TICTOC mailing list
TICTOC@ietf.org
https://www.ietf.org/mailman/listinfo/tictoc


_______________________________________________
TICTOC mailing list
TICTOC@ietf.org
https://www.ietf.org/mailman/listinfo/tictoc













From davari@broadcom.com  Wed Jun  5 16:08:08 2013
Return-Path: <davari@broadcom.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 B7B0B21E804E for <tictoc@ietfa.amsl.com>; Wed,  5 Jun 2013 16:08:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id b+Q9Crbs8YOf for <tictoc@ietfa.amsl.com>; Wed,  5 Jun 2013 16:07:24 -0700 (PDT)
Received: from mms2.broadcom.com (mms2.broadcom.com [216.31.210.18]) by ietfa.amsl.com (Postfix) with ESMTP id 86CC921F8263 for <tictoc@ietf.org>; Wed,  5 Jun 2013 16:07:24 -0700 (PDT)
Received: from [10.9.208.55] by mms2.broadcom.com with ESMTP (Broadcom SMTP Relay (Email Firewall v6.5)); Wed, 05 Jun 2013 16:01:34 -0700
X-Server-Uuid: 4500596E-606A-40F9-852D-14843D8201B2
Received: from SJEXCHCAS06.corp.ad.broadcom.com (10.16.203.14) by IRVEXCHCAS07.corp.ad.broadcom.com (10.9.208.55) with Microsoft SMTP Server (TLS) id 14.1.438.0; Wed, 5 Jun 2013 16:03:58 -0700
Received: from SJEXCHMB12.corp.ad.broadcom.com ( [fe80::bc15:c1e1:c29a:36f7]) by SJEXCHCAS06.corp.ad.broadcom.com ( [::1]) with mapi id 14.01.0438.000; Wed, 5 Jun 2013 16:03:58 -0700
From: "Shahram Davari" <davari@broadcom.com>
To: "Shahram Davari" <davari@broadcom.com>, "Meyer, Peter" <Peter.Meyer@microsemi.com>, "tictoc@ietf.org" <tictoc@ietf.org>
Thread-Topic: [TICTOC] comments on draft-ietf-tictoc-1588overmpls-04.txt
Thread-Index: AQHOHrvIG9Qp4DAEq0WS7lIAjM8M8JkmuDRwgAE3KqCAADsOgIAABF6wgAAHahCAAAEIcIAAAdVwgAAFM5CAAAX/MA==
Date: Wed, 5 Jun 2013 23:03:58 +0000
Message-ID: <4A6CE49E6084B141B15C0713B8993F281BE2FF54@SJEXCHMB12.corp.ad.broadcom.com>
References: <20130223072233.32735.89371.idtracker@ietfa.amsl.com> <64683B4805156847B0ED373DAB3057CA015E930D@ottsrv0015.microsemi.net> <4A6CE49E6084B141B15C0713B8993F281BE28013@SJEXCHMB12.corp.ad.broadcom.com> <64683B4805156847B0ED373DAB3057CA01B19D5F@ottsrv0015.microsemi.net> <4A6CE49E6084B141B15C0713B8993F281BE2FD85@SJEXCHMB12.corp.ad.broadcom.com> <64683B4805156847B0ED373DAB3057CA01B19E70@ottsrv0015.microsemi.net> <4A6CE49E6084B141B15C0713B8993F281BE2FE6E@SJEXCHMB12.corp.ad.broadcom.com> <64683B4805156847B0ED373DAB3057CA01B19E80@ottsrv0015.microsemi.net> <4A6CE49E6084B141B15C0713B8993F281BE2FED7@SJEXCHMB12.corp.ad.broadcom.com>
In-Reply-To: <4A6CE49E6084B141B15C0713B8993F281BE2FED7@SJEXCHMB12.corp.ad.broadcom.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.16.203.100]
MIME-Version: 1.0
X-WSS-ID: 7DB11CC41R026913277-06-01
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Subject: Re: [TICTOC] comments on draft-ietf-tictoc-1588overmpls-04.txt
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: Wed, 05 Jun 2013 23:08:09 -0000

Peter,

Could you please also explain why the 2 step won't work with the method in =
this draft.

Thx
Shahram

-----Original Message-----
From: tictoc-bounces@ietf.org [mailto:tictoc-bounces@ietf.org] On Behalf Of=
 Shahram Davari
Sent: Wednesday, June 05, 2013 3:43 PM
To: Meyer, Peter; tictoc@ietf.org
Subject: Re: [TICTOC] comments on draft-ietf-tictoc-1588overmpls-04.txt

Hi Peter,

Thanks, now I get it.  I will update the draft as per your suggestion.

Thx
Shahram

-----Original Message-----
From: Meyer, Peter [mailto:Peter.Meyer@microsemi.com]=20
Sent: Wednesday, June 05, 2013 3:35 PM
To: Shahram Davari; tictoc@ietf.org
Subject: RE: [TICTOC] comments on draft-ietf-tictoc-1588overmpls-04.txt


Hi Shahram,

I attempted to elaborate in section 19 Other Considerations, perhaps it
is not well written.  I tried to mirror the language that already
existed.


With the original -04 draft, section 19 covered the situation for an LSR
acting as a TC when using peer-delay messages.   An LSR would have to
generate & terminate peer-delay messages from its physical neighbour,
and the recommendation was to use a single-hop LSP.  With your
terminology, if I am using it correctly, the Sync messages are switched
through the LSR without termination.   However, this is not allowed for
peer-delay messages which must be terminated for the TC to function
properly.

"  For transporting such peer delay measurement messages a single-hop
   LSP SHOULD to be created between the two adjacent LSRs engaged in
   peer delay measurement to carry peer delay measurement messages.
   Other methods such as PTP transport over Ethernet MAY be used for
   transporting peer delay measurement messages if the link between the
   two routers is Ethernet.  "


I use this same approach for an LSR acting as a BC.   A BC inside an LSR
is the same as a peer-delay TC inside an LSR.  The LSR would have to
generate & terminate end-to-end messages from its physical neighbour. I
modified the section to recommend a single-hop LSP for this purpose.

"  Likewise for BCs embedded in an LSR, a single-hop LSP SHOULD be=20
   created between the two adjacent LSRs that are acting as BCs.  Other
   methods such as PTP transport over Ethernet MAY be used if the link
   between the two routers is Ethernet.  "


Hope this makes sense.

Regards,
Peter


-----Original Message-----
From: Shahram Davari [mailto:davari@broadcom.com]=20
Sent: June 5, 2013 6:18 PM
To: Meyer, Peter; tictoc@ietf.org
Subject: RE: [TICTOC] comments on draft-ietf-tictoc-1588overmpls-04.txt

Peter,

I think we have a difference in terminology. To me an LSR is a router
that does Label Swap and not Label pop. May be what you have in mind is
PE and P routers instead of LER and LSR.=20

Thx
Shahram

-----Original Message-----
From: Shahram Davari=20
Sent: Wednesday, June 05, 2013 3:16 PM
To: 'Meyer, Peter'; tictoc@ietf.org
Subject: RE: [TICTOC] comments on draft-ietf-tictoc-1588overmpls-04.txt

Hi Peter,

I see that the majority of changes are related to LSR BC. I personally
don't think this is possible, since we can't terminate packets in the
middle of an LSP. Could you please provide an example for your
suggestion of using LSR BC? How are the 1588 timing messages terminated?

Thanks
Shahram

-----Original Message-----
From: Meyer, Peter [mailto:Peter.Meyer@microsemi.com]=20
Sent: Wednesday, June 05, 2013 2:48 PM
To: Shahram Davari; tictoc@ietf.org
Subject: RE: [TICTOC] comments on draft-ietf-tictoc-1588overmpls-04.txt


Hi Shahram,

I took the -04 that was advertised on the exploder in February (dated
February 23, 2013).  I then edited that copy.

(I think the diff may show a ton of changes due to line length or word
wrapping).

Regards,
Peter


-----Original Message-----
From: Shahram Davari [mailto:davari@broadcom.com]=20
Sent: June 5, 2013 5:32 PM
To: Meyer, Peter; tictoc@ietf.org
Subject: RE: [TICTOC] comments on draft-ietf-tictoc-1588overmpls-04.txt

Thanks Peter.=20

These edits where done before the publishing of draft-04. Correct?

-Shahram

-----Original Message-----
From: Meyer, Peter [mailto:Peter.Meyer@microsemi.com]=20
Sent: Wednesday, June 05, 2013 11:01 AM
To: Shahram Davari; tictoc@ietf.org
Subject: RE: [TICTOC] comments on draft-ietf-tictoc-1588overmpls-04.txt

Hi Shahram,

I hope in-line with my comments I have edited the text of draft -04.

I'm not sure how the formatting worked out (PC-based, line length, page
length).

I modified sections 3, 4, 18, 19 & 20.

I include here both original and modified version so you can diff (most
of the changes in 3 are due to line length / re-org, not actual text
changes).

File attachment:
"draft-ietf-tictoc-1588overmpls-04-org.txt" (52 KB)
"draft-ietf-tictoc-1588overmpls-04-pm.txt" (53 KB)


Regards,
Peter


-----Original Message-----
From: Shahram Davari [mailto:davari@broadcom.com]=20
Sent: June 4, 2013 7:40 PM
To: Meyer, Peter; tictoc@ietf.org
Subject: RE: [TICTOC] comments on draft-ietf-tictoc-1588overmpls-04.txt

Hi Peter,

Thanks for your god comments. Please see my responses inline. Please let
me know whether you are satisfied with my responses since I am updating
the draft in the next couple of days.

Thanks
Shahram

-----Original Message-----
From: tictoc-bounces@ietf.org [mailto:tictoc-bounces@ietf.org] On Behalf
Of Meyer, Peter
Sent: Monday, March 11, 2013 5:49 PM
To: tictoc@ietf.org
Subject: Re: [TICTOC] comments on draft-ietf-tictoc-1588overmpls-04.txt

Hi Shahram et al,

Some comments on draft -04.


1) Section 3.  "A generic method is defined in this document that does
not require deep packet inspection at line rate, and can
deterministically identify Timing messages.  The generic method is
applicable to MPLS and MPLS-TP networks."

May want to add that this would apply only to one-step TC (I imagine
that is the point of the correction at line rate).  A two-step TC would
need to do deep packet inspection as it uses sourcePortIdentity &
sequenceId fields for Follow_up or Delay_Resp.

SD> For 2-step, all that is needed is for an interface to detect the
Timing message (based on top MPLS Label)  and record the Time along with
some information from the Timing packet and send them to CPU while
forwarding the Timing message as usual. Then the CPU based on the
information received generates Follow-up message and injects it in to
the LSP.  Therefore it is the job of CPU to look at sourcePortIdentity &
sequenceId fields not the Hardware.


2) Section 4.  "An MPLS domain can serve multiple customers.  This means
that the MPLS domain (maintained by a service provider) may provide
timing services to multiple customers, each having their own Timing
domain.  Therefore LER BCs need to interact with multiple grandmasters,
and consequently multiple time references."

This should be re-phrased.  It switches from an optional situation ("may
provide timing services") to mandatory situation ("LER BCs need to
interact").   Some words such as "in such a deployment scenario, ...."
and replace "can" with "may".   We have seen at ITU at least (with
participation from operators BT, FT, DT, CMCC, AT&T, Sprint, etc.) that
this multiple operator domain case was not useful enough to be included
in standardization process for Telecom networks.

SD> I rephrased it as following:

" An MPLS domain can serve multiple customers.  This means that the
   MPLS domain (maintained by a service provider) may provide timing
   services to multiple customers, each having their own Timing domain.
   Therefore in such deployment scenarios, LER BCs may interact with
multiple grandmasters,=20
and consequently multiple time references.  Also, LER/LSR TCs MUST be
synchronized to the=20
same master clock (which is the service provider Master clock), which
implies that they need=20
to choose one master to synchronize to."


3) Section 19.  "For transporting such peer delay measurement messages a
single-hop LSP SHOULD to be created between the two adjacent LSRs
engaged in peer delay measurement to carry peer delay measurement
messages. Other methods such as PTP transport over Ethernet MAY be used
for transporting peer delay measurement messages if the link between the
two routers is Ethernet."


This new statement to handle peer-delay (which in earlier drafts did not
have a communication path listed), also allows a BC to be embedded in an
LSR with a communication path between BC's as a single-hop LSP
(mentioned March 22, 2012 in my feedback to draft -03, subject "[TICTOC]
Updated 1588 over MPLS draf-03").

SD> When a single-hop LSP is created then I call the both ends of that
LSP, LERs and not LSRs.
Note that a router can act as LSR for some LSPs and LER for other LSPs.
The point is that we can't
Terminate a packet in the middle of an LSP (i.e., in an LSR). So BC
functionality can't exist in the middle
Of a PTP LSP. So I think it is a matter of terminology otherwise I agree
that you could have BC in the core
(not edge).=20

Architecture diagrams Figure 1 and Figure should be updated to reflect
the possibility of either BC or TC implementation.   Section 18.2 and
section 18.3 and section 21 should also be updated to reflect the
possibility of either BC or TC.  I understand the RFC is intended to be
generic and not targeted only at TC.



4) Section 20.  "When the MPLS network (provider network) serves
multiple customers, it is important to maintain and process each
customers clock and Timing messages separately from other customers to
ensure there is no cross- customer effect.   For example if an LER BC is
synchronized to a specific grandmaster, belonging to customer A, then
the LER MUST use that BC clock only for customer A to ensure that
customer A cannot attack other customers by manipulating its time."

This seems much more applicable to the TC LSR and should be stated.
>From section 4 we see the TC uses the primary synchronization domain
(that of the service provide) to correct PTP messages.

SD> I don't see how in a TC LSR, one customer timing can affect other
customer timings?
Since in a TC, we just update the Timestamp of a packet based on the
Service provider Time.
May be I have not understood your point. Could you please clarify with
an example.



5) Section 20.  "Timing messages (as opposed to regular customer data)
SHOULD not be encrypted or authenticated on an end-to-end basis."  I
think there is a security draft in parallel being developed that may be
relevant to that statement.

SD> I have updated the  text as following:

" Timing messages MAY be encrypted or authenticated, provided that the
LERs/LSRs that are Timing capable/aware can authenticate/ decrypt the
timing messages."




Regards,
Peter


-----Original Message-----
From: tictoc-bounces@ietf.org [mailto:tictoc-bounces@ietf.org] On Behalf
Of internet-drafts@ietf.org
Sent: February 23, 2013 2:23 AM
To: i-d-announce@ietf.org
Cc: tictoc@ietf.org
Subject: [TICTOC] I-D Action: draft-ietf-tictoc-1588overmpls-04.txt


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

	Title           : Transporting Timing messages over MPLS
Networks
	Author(s)       : Shahram Davari
                          Amit Oren
                          Manav Bhatia
                          Peter Roberts
                          Laurent Montini
	Filename        : draft-ietf-tictoc-1588overmpls-04.txt
	Pages           : 36
	Date            : 2013-02-22

Abstract:
   This document defines the method for transporting Timing messages
   such as PTP and NTP over an MPLS network.  The method allows for the
   easy identification of these PDUs at the port level to allow for port
   level processing of these PDUs in both LERs and LSRs.

   The basic idea is to transport Timing messages inside dedicated MPLS
   LSPs.  These LSPs only carry timing messages and possibly Control and
   Management packets, but they do not carry customer traffic.

   Two methods for transporting Timing messages over MPLS are defined.
   The first method is to transport Timing messages directly over the
   dedicated MPLS LSP via UDP/IP encapsulation, which is suitable for
   MPLS networks.  The second method is to transport Timing messages
   inside a PW via Ethernet encapsulation, which is suitable for both
   MPLS and MPLS-TP networks.


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

There's also a htmlized version available at:
http://tools.ietf.org/html/draft-ietf-tictoc-1588overmpls-04

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


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

_______________________________________________
TICTOC mailing list
TICTOC@ietf.org
https://www.ietf.org/mailman/listinfo/tictoc


_______________________________________________
TICTOC mailing list
TICTOC@ietf.org
https://www.ietf.org/mailman/listinfo/tictoc












_______________________________________________
TICTOC mailing list
TICTOC@ietf.org
https://www.ietf.org/mailman/listinfo/tictoc



From Peter.Meyer@microsemi.com  Wed Jun  5 16:22:13 2013
Return-Path: <Peter.Meyer@microsemi.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 DBAF121F9634 for <tictoc@ietfa.amsl.com>; Wed,  5 Jun 2013 16:22:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.224
X-Spam-Level: 
X-Spam-Status: No, score=-4.224 tagged_above=-999 required=5 tests=[AWL=-0.625, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-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 e28cFOU-m+pj for <tictoc@ietfa.amsl.com>; Wed,  5 Jun 2013 16:22:07 -0700 (PDT)
Received: from va3outboundpool.messaging.microsoft.com (va3ehsobe004.messaging.microsoft.com [216.32.180.14]) by ietfa.amsl.com (Postfix) with ESMTP id 6171321F9678 for <tictoc@ietf.org>; Wed,  5 Jun 2013 16:22:04 -0700 (PDT)
Received: from mail208-va3-R.bigfish.com (10.7.14.250) by VA3EHSOBE002.bigfish.com (10.7.40.22) with Microsoft SMTP Server id 14.1.225.23; Wed, 5 Jun 2013 23:22:03 +0000
Received: from mail208-va3 (localhost [127.0.0.1])	by mail208-va3-R.bigfish.com (Postfix) with ESMTP id 84B3B720C93; Wed,  5 Jun 2013 23:22:03 +0000 (UTC)
X-Forefront-Antispam-Report: CIP:209.226.172.12; KIP:(null); UIP:(null); IPV:NLI; H:ottsrv0014.microsemi.net; RD:none; EFVD:NLI
X-SpamScore: -24
X-BigFish: VS-24(zz9371I936eI542I4015Izz1f42h1ee6h1de0h1fdah1202h1e76h1d1ah1d2ah1fc6hzz1033IL17326ah8275dhz2dh668h839h944hd25hf0ah1220h1288h12a5h12a9h12bdh137ah13b6h1441h14ddh1504h1537h153bh15d0h162dh1631h1758h184fh18e1h1946h19b5h1ad9h1b0ah1c24h1d0ch1d2eh1d3fh1dfeh1dffh1e1dh1155h)
Received: from mail208-va3 (localhost.localdomain [127.0.0.1]) by mail208-va3 (MessageSwitch) id 1370474521392710_4234; Wed,  5 Jun 2013 23:22:01 +0000 (UTC)
Received: from VA3EHSMHS023.bigfish.com (unknown [10.7.14.237])	by mail208-va3.bigfish.com (Postfix) with ESMTP id 5E071D4007A; Wed,  5 Jun 2013 23:22:01 +0000 (UTC)
Received: from ottsrv0014.microsemi.net (209.226.172.12) by VA3EHSMHS023.bigfish.com (10.7.99.33) with Microsoft SMTP Server id 14.1.225.23; Wed, 5 Jun 2013 23:22:01 +0000
Received: from ottsrv0015.microsemi.net ([134.199.15.151]) by ottsrv0014.microsemi.net with Microsoft SMTPSVC(6.0.3790.4675); Wed, 5 Jun 2013 19:22:00 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-Class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Wed, 5 Jun 2013 19:21:49 -0400
Message-ID: <64683B4805156847B0ED373DAB3057CA01B19E97@ottsrv0015.microsemi.net>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [TICTOC] comments on draft-ietf-tictoc-1588overmpls-04.txt
Thread-Index: AQHOHrvIG9Qp4DAEq0WS7lIAjM8M8JkmuDRwgAE3KqCAADsOgIAABF6wgAAHahCAAAEIcIAAAdVwgAAFM5CAAAX/MIAABGhA
References: <20130223072233.32735.89371.idtracker@ietfa.amsl.com> <64683B4805156847B0ED373DAB3057CA015E930D@ottsrv0015.microsemi.net> <4A6CE49E6084B141B15C0713B8993F281BE28013@SJEXCHMB12.corp.ad.broadcom.com> <64683B4805156847B0ED373DAB3057CA01B19D5F@ottsrv0015.microsemi.net> <4A6CE49E6084B141B15C0713B8993F281BE2FD85@SJEXCHMB12.corp.ad.broadcom.com> <64683B4805156847B0ED373DAB3057CA01B19E70@ottsrv0015.microsemi.net> <4A6CE49E6084B141B15C0713B8993F281BE2FE6E@SJEXCHMB12.corp.ad.broadcom.com> <64683B4805156847B0ED373DAB3057CA01B19E80@ottsrv0015.microsemi.net> <4A6CE49E6084B141B15C0713B8993F281BE2FED7@SJEXCHMB12.corp.ad.broadcom.com> <4A6CE49E6084B141B15C0713B8993F281BE2FF54@SJEXCHMB12.corp.ad.broadcom.com>
From: "Meyer, Peter" <Peter.Meyer@microsemi.com>
To: Shahram Davari <davari@broadcom.com>, <tictoc@ietf.org>
X-OriginalArrivalTime: 05 Jun 2013 23:22:00.0913 (UTC) FILETIME=[7B2BEC10:01CE6243]
X-OriginatorOrg: microsemi.com
Subject: Re: [TICTOC] comments on draft-ietf-tictoc-1588overmpls-04.txt
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: Wed, 05 Jun 2013 23:22:13 -0000

Hi Shahram,

I think you are referring to section 3=20

"   A generic method is defined in this document that does not require
   deep packet inspection at line rate, and can deterministically
   identify Timing messages, for one-step mode of operation.  The=20
   generic method is applicable to MPLS and MPLS-TP networks."


I was not intending to indicate two-step would not work.   I was
intending to highlight the important benefit of this document is
specifically to enable one-step capability more easily.  Without this
specification one-step is more difficult due to the need for deep packet
inspection.  Two-step would probably not benefit as much as a result of
this specification.

If I have not worded correctly, it can be removed/changed back to
original.


Regards,
Peter



-----Original Message-----
From: Shahram Davari [mailto:davari@broadcom.com]=20
Sent: June 5, 2013 7:04 PM
To: Shahram Davari; Meyer, Peter; tictoc@ietf.org
Subject: RE: [TICTOC] comments on draft-ietf-tictoc-1588overmpls-04.txt

Peter,

Could you please also explain why the 2 step won't work with the method
in this draft.

Thx
Shahram

-----Original Message-----
From: tictoc-bounces@ietf.org [mailto:tictoc-bounces@ietf.org] On Behalf
Of Shahram Davari
Sent: Wednesday, June 05, 2013 3:43 PM
To: Meyer, Peter; tictoc@ietf.org
Subject: Re: [TICTOC] comments on draft-ietf-tictoc-1588overmpls-04.txt

Hi Peter,

Thanks, now I get it.  I will update the draft as per your suggestion.

Thx
Shahram

-----Original Message-----
From: Meyer, Peter [mailto:Peter.Meyer@microsemi.com]=20
Sent: Wednesday, June 05, 2013 3:35 PM
To: Shahram Davari; tictoc@ietf.org
Subject: RE: [TICTOC] comments on draft-ietf-tictoc-1588overmpls-04.txt


Hi Shahram,

I attempted to elaborate in section 19 Other Considerations, perhaps it
is not well written.  I tried to mirror the language that already
existed.


With the original -04 draft, section 19 covered the situation for an LSR
acting as a TC when using peer-delay messages.   An LSR would have to
generate & terminate peer-delay messages from its physical neighbour,
and the recommendation was to use a single-hop LSP.  With your
terminology, if I am using it correctly, the Sync messages are switched
through the LSR without termination.   However, this is not allowed for
peer-delay messages which must be terminated for the TC to function
properly.

"  For transporting such peer delay measurement messages a single-hop
   LSP SHOULD to be created between the two adjacent LSRs engaged in
   peer delay measurement to carry peer delay measurement messages.
   Other methods such as PTP transport over Ethernet MAY be used for
   transporting peer delay measurement messages if the link between the
   two routers is Ethernet.  "


I use this same approach for an LSR acting as a BC.   A BC inside an LSR
is the same as a peer-delay TC inside an LSR.  The LSR would have to
generate & terminate end-to-end messages from its physical neighbour. I
modified the section to recommend a single-hop LSP for this purpose.

"  Likewise for BCs embedded in an LSR, a single-hop LSP SHOULD be=20
   created between the two adjacent LSRs that are acting as BCs.  Other
   methods such as PTP transport over Ethernet MAY be used if the link
   between the two routers is Ethernet.  "


Hope this makes sense.

Regards,
Peter


-----Original Message-----
From: Shahram Davari [mailto:davari@broadcom.com]=20
Sent: June 5, 2013 6:18 PM
To: Meyer, Peter; tictoc@ietf.org
Subject: RE: [TICTOC] comments on draft-ietf-tictoc-1588overmpls-04.txt

Peter,

I think we have a difference in terminology. To me an LSR is a router
that does Label Swap and not Label pop. May be what you have in mind is
PE and P routers instead of LER and LSR.=20

Thx
Shahram

-----Original Message-----
From: Shahram Davari=20
Sent: Wednesday, June 05, 2013 3:16 PM
To: 'Meyer, Peter'; tictoc@ietf.org
Subject: RE: [TICTOC] comments on draft-ietf-tictoc-1588overmpls-04.txt

Hi Peter,

I see that the majority of changes are related to LSR BC. I personally
don't think this is possible, since we can't terminate packets in the
middle of an LSP. Could you please provide an example for your
suggestion of using LSR BC? How are the 1588 timing messages terminated?

Thanks
Shahram

-----Original Message-----
From: Meyer, Peter [mailto:Peter.Meyer@microsemi.com]=20
Sent: Wednesday, June 05, 2013 2:48 PM
To: Shahram Davari; tictoc@ietf.org
Subject: RE: [TICTOC] comments on draft-ietf-tictoc-1588overmpls-04.txt


Hi Shahram,

I took the -04 that was advertised on the exploder in February (dated
February 23, 2013).  I then edited that copy.

(I think the diff may show a ton of changes due to line length or word
wrapping).

Regards,
Peter


-----Original Message-----
From: Shahram Davari [mailto:davari@broadcom.com]=20
Sent: June 5, 2013 5:32 PM
To: Meyer, Peter; tictoc@ietf.org
Subject: RE: [TICTOC] comments on draft-ietf-tictoc-1588overmpls-04.txt

Thanks Peter.=20

These edits where done before the publishing of draft-04. Correct?

-Shahram

-----Original Message-----
From: Meyer, Peter [mailto:Peter.Meyer@microsemi.com]=20
Sent: Wednesday, June 05, 2013 11:01 AM
To: Shahram Davari; tictoc@ietf.org
Subject: RE: [TICTOC] comments on draft-ietf-tictoc-1588overmpls-04.txt

Hi Shahram,

I hope in-line with my comments I have edited the text of draft -04.

I'm not sure how the formatting worked out (PC-based, line length, page
length).

I modified sections 3, 4, 18, 19 & 20.

I include here both original and modified version so you can diff (most
of the changes in 3 are due to line length / re-org, not actual text
changes).

File attachment:
"draft-ietf-tictoc-1588overmpls-04-org.txt" (52 KB)
"draft-ietf-tictoc-1588overmpls-04-pm.txt" (53 KB)


Regards,
Peter


-----Original Message-----
From: Shahram Davari [mailto:davari@broadcom.com]=20
Sent: June 4, 2013 7:40 PM
To: Meyer, Peter; tictoc@ietf.org
Subject: RE: [TICTOC] comments on draft-ietf-tictoc-1588overmpls-04.txt

Hi Peter,

Thanks for your god comments. Please see my responses inline. Please let
me know whether you are satisfied with my responses since I am updating
the draft in the next couple of days.

Thanks
Shahram

-----Original Message-----
From: tictoc-bounces@ietf.org [mailto:tictoc-bounces@ietf.org] On Behalf
Of Meyer, Peter
Sent: Monday, March 11, 2013 5:49 PM
To: tictoc@ietf.org
Subject: Re: [TICTOC] comments on draft-ietf-tictoc-1588overmpls-04.txt

Hi Shahram et al,

Some comments on draft -04.


1) Section 3.  "A generic method is defined in this document that does
not require deep packet inspection at line rate, and can
deterministically identify Timing messages.  The generic method is
applicable to MPLS and MPLS-TP networks."

May want to add that this would apply only to one-step TC (I imagine
that is the point of the correction at line rate).  A two-step TC would
need to do deep packet inspection as it uses sourcePortIdentity &
sequenceId fields for Follow_up or Delay_Resp.

SD> For 2-step, all that is needed is for an interface to detect the
Timing message (based on top MPLS Label)  and record the Time along with
some information from the Timing packet and send them to CPU while
forwarding the Timing message as usual. Then the CPU based on the
information received generates Follow-up message and injects it in to
the LSP.  Therefore it is the job of CPU to look at sourcePortIdentity &
sequenceId fields not the Hardware.


2) Section 4.  "An MPLS domain can serve multiple customers.  This means
that the MPLS domain (maintained by a service provider) may provide
timing services to multiple customers, each having their own Timing
domain.  Therefore LER BCs need to interact with multiple grandmasters,
and consequently multiple time references."

This should be re-phrased.  It switches from an optional situation ("may
provide timing services") to mandatory situation ("LER BCs need to
interact").   Some words such as "in such a deployment scenario, ...."
and replace "can" with "may".   We have seen at ITU at least (with
participation from operators BT, FT, DT, CMCC, AT&T, Sprint, etc.) that
this multiple operator domain case was not useful enough to be included
in standardization process for Telecom networks.

SD> I rephrased it as following:

" An MPLS domain can serve multiple customers.  This means that the
   MPLS domain (maintained by a service provider) may provide timing
   services to multiple customers, each having their own Timing domain.
   Therefore in such deployment scenarios, LER BCs may interact with
multiple grandmasters,=20
and consequently multiple time references.  Also, LER/LSR TCs MUST be
synchronized to the=20
same master clock (which is the service provider Master clock), which
implies that they need=20
to choose one master to synchronize to."


3) Section 19.  "For transporting such peer delay measurement messages a
single-hop LSP SHOULD to be created between the two adjacent LSRs
engaged in peer delay measurement to carry peer delay measurement
messages. Other methods such as PTP transport over Ethernet MAY be used
for transporting peer delay measurement messages if the link between the
two routers is Ethernet."


This new statement to handle peer-delay (which in earlier drafts did not
have a communication path listed), also allows a BC to be embedded in an
LSR with a communication path between BC's as a single-hop LSP
(mentioned March 22, 2012 in my feedback to draft -03, subject "[TICTOC]
Updated 1588 over MPLS draf-03").

SD> When a single-hop LSP is created then I call the both ends of that
LSP, LERs and not LSRs.
Note that a router can act as LSR for some LSPs and LER for other LSPs.
The point is that we can't
Terminate a packet in the middle of an LSP (i.e., in an LSR). So BC
functionality can't exist in the middle
Of a PTP LSP. So I think it is a matter of terminology otherwise I agree
that you could have BC in the core
(not edge).=20

Architecture diagrams Figure 1 and Figure should be updated to reflect
the possibility of either BC or TC implementation.   Section 18.2 and
section 18.3 and section 21 should also be updated to reflect the
possibility of either BC or TC.  I understand the RFC is intended to be
generic and not targeted only at TC.



4) Section 20.  "When the MPLS network (provider network) serves
multiple customers, it is important to maintain and process each
customers clock and Timing messages separately from other customers to
ensure there is no cross- customer effect.   For example if an LER BC is
synchronized to a specific grandmaster, belonging to customer A, then
the LER MUST use that BC clock only for customer A to ensure that
customer A cannot attack other customers by manipulating its time."

This seems much more applicable to the TC LSR and should be stated.
>From section 4 we see the TC uses the primary synchronization domain
(that of the service provide) to correct PTP messages.

SD> I don't see how in a TC LSR, one customer timing can affect other
customer timings?
Since in a TC, we just update the Timestamp of a packet based on the
Service provider Time.
May be I have not understood your point. Could you please clarify with
an example.



5) Section 20.  "Timing messages (as opposed to regular customer data)
SHOULD not be encrypted or authenticated on an end-to-end basis."  I
think there is a security draft in parallel being developed that may be
relevant to that statement.

SD> I have updated the  text as following:

" Timing messages MAY be encrypted or authenticated, provided that the
LERs/LSRs that are Timing capable/aware can authenticate/ decrypt the
timing messages."




Regards,
Peter


-----Original Message-----
From: tictoc-bounces@ietf.org [mailto:tictoc-bounces@ietf.org] On Behalf
Of internet-drafts@ietf.org
Sent: February 23, 2013 2:23 AM
To: i-d-announce@ietf.org
Cc: tictoc@ietf.org
Subject: [TICTOC] I-D Action: draft-ietf-tictoc-1588overmpls-04.txt


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

	Title           : Transporting Timing messages over MPLS
Networks
	Author(s)       : Shahram Davari
                          Amit Oren
                          Manav Bhatia
                          Peter Roberts
                          Laurent Montini
	Filename        : draft-ietf-tictoc-1588overmpls-04.txt
	Pages           : 36
	Date            : 2013-02-22

Abstract:
   This document defines the method for transporting Timing messages
   such as PTP and NTP over an MPLS network.  The method allows for the
   easy identification of these PDUs at the port level to allow for port
   level processing of these PDUs in both LERs and LSRs.

   The basic idea is to transport Timing messages inside dedicated MPLS
   LSPs.  These LSPs only carry timing messages and possibly Control and
   Management packets, but they do not carry customer traffic.

   Two methods for transporting Timing messages over MPLS are defined.
   The first method is to transport Timing messages directly over the
   dedicated MPLS LSP via UDP/IP encapsulation, which is suitable for
   MPLS networks.  The second method is to transport Timing messages
   inside a PW via Ethernet encapsulation, which is suitable for both
   MPLS and MPLS-TP networks.


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

There's also a htmlized version available at:
http://tools.ietf.org/html/draft-ietf-tictoc-1588overmpls-04

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


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

_______________________________________________
TICTOC mailing list
TICTOC@ietf.org
https://www.ietf.org/mailman/listinfo/tictoc


_______________________________________________
TICTOC mailing list
TICTOC@ietf.org
https://www.ietf.org/mailman/listinfo/tictoc












_______________________________________________
TICTOC mailing list
TICTOC@ietf.org
https://www.ietf.org/mailman/listinfo/tictoc





From davari@broadcom.com  Wed Jun  5 16:32:57 2013
Return-Path: <davari@broadcom.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 BB05C11E80E1 for <tictoc@ietfa.amsl.com>; Wed,  5 Jun 2013 16:32:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[AWL=0.000,  BAYES_00=-2.599, 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 vcfFnJlDy62B for <tictoc@ietfa.amsl.com>; Wed,  5 Jun 2013 16:32:52 -0700 (PDT)
Received: from mms2.broadcom.com (mms2.broadcom.com [216.31.210.18]) by ietfa.amsl.com (Postfix) with ESMTP id A7CFF21F8A68 for <tictoc@ietf.org>; Wed,  5 Jun 2013 16:32:52 -0700 (PDT)
Received: from [10.9.208.53] by mms2.broadcom.com with ESMTP (Broadcom SMTP Relay (Email Firewall v6.5)); Wed, 05 Jun 2013 16:26:35 -0700
X-Server-Uuid: 4500596E-606A-40F9-852D-14843D8201B2
Received: from SJEXCHCAS07.corp.ad.broadcom.com (10.16.203.16) by IRVEXCHCAS06.corp.ad.broadcom.com (10.9.208.53) with Microsoft SMTP Server (TLS) id 14.1.438.0; Wed, 5 Jun 2013 16:32:13 -0700
Received: from SJEXCHMB12.corp.ad.broadcom.com ( [fe80::bc15:c1e1:c29a:36f7]) by SJEXCHCAS07.corp.ad.broadcom.com ( [::1]) with mapi id 14.01.0438.000; Wed, 5 Jun 2013 16:32:13 -0700
From: "Shahram Davari" <davari@broadcom.com>
To: "Meyer, Peter" <Peter.Meyer@microsemi.com>, "tictoc@ietf.org" <tictoc@ietf.org>
Thread-Topic: [TICTOC] comments on draft-ietf-tictoc-1588overmpls-04.txt
Thread-Index: AQHOHrvIG9Qp4DAEq0WS7lIAjM8M8JkmuDRwgAE3KqCAADsOgIAABF6wgAAHahCAAAEIcIAAAdVwgAAFM5CAAAX/MIAABGhAgAADjKA=
Date: Wed, 5 Jun 2013 23:32:13 +0000
Message-ID: <4A6CE49E6084B141B15C0713B8993F281BE2FFE4@SJEXCHMB12.corp.ad.broadcom.com>
References: <20130223072233.32735.89371.idtracker@ietfa.amsl.com> <64683B4805156847B0ED373DAB3057CA015E930D@ottsrv0015.microsemi.net> <4A6CE49E6084B141B15C0713B8993F281BE28013@SJEXCHMB12.corp.ad.broadcom.com> <64683B4805156847B0ED373DAB3057CA01B19D5F@ottsrv0015.microsemi.net> <4A6CE49E6084B141B15C0713B8993F281BE2FD85@SJEXCHMB12.corp.ad.broadcom.com> <64683B4805156847B0ED373DAB3057CA01B19E70@ottsrv0015.microsemi.net> <4A6CE49E6084B141B15C0713B8993F281BE2FE6E@SJEXCHMB12.corp.ad.broadcom.com> <64683B4805156847B0ED373DAB3057CA01B19E80@ottsrv0015.microsemi.net> <4A6CE49E6084B141B15C0713B8993F281BE2FED7@SJEXCHMB12.corp.ad.broadcom.com> <4A6CE49E6084B141B15C0713B8993F281BE2FF54@SJEXCHMB12.corp.ad.broadcom.com> <64683B4805156847B0ED373DAB3057CA01B19E97@ottsrv0015.microsemi.net>
In-Reply-To: <64683B4805156847B0ED373DAB3057CA01B19E97@ottsrv0015.microsemi.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.16.203.100]
MIME-Version: 1.0
X-WSS-ID: 7DB116A11R026921994-01-01
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Subject: Re: [TICTOC] comments on draft-ietf-tictoc-1588overmpls-04.txt
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: Wed, 05 Jun 2013 23:32:58 -0000

How about rephrasing it as following:

"   A generic method is defined in this document that does not require
   deep packet inspection at line rate, and can deterministically
   identify Timing messages. This method is specifically beneficial for 1-s=
tep=20
 Transparent Clocking operation described in [IEEE-1588], while it also sup=
ports=20
2-Step Transparent Clocking."

Thx
SD

-----Original Message-----
From: Meyer, Peter [mailto:Peter.Meyer@microsemi.com]=20
Sent: Wednesday, June 05, 2013 4:22 PM
To: Shahram Davari; tictoc@ietf.org
Subject: RE: [TICTOC] comments on draft-ietf-tictoc-1588overmpls-04.txt

Hi Shahram,

I think you are referring to section 3=20

"   A generic method is defined in this document that does not require
   deep packet inspection at line rate, and can deterministically
   identify Timing messages, for one-step mode of operation.  The=20
   generic method is applicable to MPLS and MPLS-TP networks."


I was not intending to indicate two-step would not work.   I was
intending to highlight the important benefit of this document is
specifically to enable one-step capability more easily.  Without this
specification one-step is more difficult due to the need for deep packet
inspection.  Two-step would probably not benefit as much as a result of
this specification.

If I have not worded correctly, it can be removed/changed back to
original.


Regards,
Peter



-----Original Message-----
From: Shahram Davari [mailto:davari@broadcom.com]=20
Sent: June 5, 2013 7:04 PM
To: Shahram Davari; Meyer, Peter; tictoc@ietf.org
Subject: RE: [TICTOC] comments on draft-ietf-tictoc-1588overmpls-04.txt

Peter,

Could you please also explain why the 2 step won't work with the method
in this draft.

Thx
Shahram

-----Original Message-----
From: tictoc-bounces@ietf.org [mailto:tictoc-bounces@ietf.org] On Behalf
Of Shahram Davari
Sent: Wednesday, June 05, 2013 3:43 PM
To: Meyer, Peter; tictoc@ietf.org
Subject: Re: [TICTOC] comments on draft-ietf-tictoc-1588overmpls-04.txt

Hi Peter,

Thanks, now I get it.  I will update the draft as per your suggestion.

Thx
Shahram

-----Original Message-----
From: Meyer, Peter [mailto:Peter.Meyer@microsemi.com]=20
Sent: Wednesday, June 05, 2013 3:35 PM
To: Shahram Davari; tictoc@ietf.org
Subject: RE: [TICTOC] comments on draft-ietf-tictoc-1588overmpls-04.txt


Hi Shahram,

I attempted to elaborate in section 19 Other Considerations, perhaps it
is not well written.  I tried to mirror the language that already
existed.


With the original -04 draft, section 19 covered the situation for an LSR
acting as a TC when using peer-delay messages.   An LSR would have to
generate & terminate peer-delay messages from its physical neighbour,
and the recommendation was to use a single-hop LSP.  With your
terminology, if I am using it correctly, the Sync messages are switched
through the LSR without termination.   However, this is not allowed for
peer-delay messages which must be terminated for the TC to function
properly.

"  For transporting such peer delay measurement messages a single-hop
   LSP SHOULD to be created between the two adjacent LSRs engaged in
   peer delay measurement to carry peer delay measurement messages.
   Other methods such as PTP transport over Ethernet MAY be used for
   transporting peer delay measurement messages if the link between the
   two routers is Ethernet.  "


I use this same approach for an LSR acting as a BC.   A BC inside an LSR
is the same as a peer-delay TC inside an LSR.  The LSR would have to
generate & terminate end-to-end messages from its physical neighbour. I
modified the section to recommend a single-hop LSP for this purpose.

"  Likewise for BCs embedded in an LSR, a single-hop LSP SHOULD be=20
   created between the two adjacent LSRs that are acting as BCs.  Other
   methods such as PTP transport over Ethernet MAY be used if the link
   between the two routers is Ethernet.  "


Hope this makes sense.

Regards,
Peter


-----Original Message-----
From: Shahram Davari [mailto:davari@broadcom.com]=20
Sent: June 5, 2013 6:18 PM
To: Meyer, Peter; tictoc@ietf.org
Subject: RE: [TICTOC] comments on draft-ietf-tictoc-1588overmpls-04.txt

Peter,

I think we have a difference in terminology. To me an LSR is a router
that does Label Swap and not Label pop. May be what you have in mind is
PE and P routers instead of LER and LSR.=20

Thx
Shahram

-----Original Message-----
From: Shahram Davari=20
Sent: Wednesday, June 05, 2013 3:16 PM
To: 'Meyer, Peter'; tictoc@ietf.org
Subject: RE: [TICTOC] comments on draft-ietf-tictoc-1588overmpls-04.txt

Hi Peter,

I see that the majority of changes are related to LSR BC. I personally
don't think this is possible, since we can't terminate packets in the
middle of an LSP. Could you please provide an example for your
suggestion of using LSR BC? How are the 1588 timing messages terminated?

Thanks
Shahram

-----Original Message-----
From: Meyer, Peter [mailto:Peter.Meyer@microsemi.com]=20
Sent: Wednesday, June 05, 2013 2:48 PM
To: Shahram Davari; tictoc@ietf.org
Subject: RE: [TICTOC] comments on draft-ietf-tictoc-1588overmpls-04.txt


Hi Shahram,

I took the -04 that was advertised on the exploder in February (dated
February 23, 2013).  I then edited that copy.

(I think the diff may show a ton of changes due to line length or word
wrapping).

Regards,
Peter


-----Original Message-----
From: Shahram Davari [mailto:davari@broadcom.com]=20
Sent: June 5, 2013 5:32 PM
To: Meyer, Peter; tictoc@ietf.org
Subject: RE: [TICTOC] comments on draft-ietf-tictoc-1588overmpls-04.txt

Thanks Peter.=20

These edits where done before the publishing of draft-04. Correct?

-Shahram

-----Original Message-----
From: Meyer, Peter [mailto:Peter.Meyer@microsemi.com]=20
Sent: Wednesday, June 05, 2013 11:01 AM
To: Shahram Davari; tictoc@ietf.org
Subject: RE: [TICTOC] comments on draft-ietf-tictoc-1588overmpls-04.txt

Hi Shahram,

I hope in-line with my comments I have edited the text of draft -04.

I'm not sure how the formatting worked out (PC-based, line length, page
length).

I modified sections 3, 4, 18, 19 & 20.

I include here both original and modified version so you can diff (most
of the changes in 3 are due to line length / re-org, not actual text
changes).

File attachment:
"draft-ietf-tictoc-1588overmpls-04-org.txt" (52 KB)
"draft-ietf-tictoc-1588overmpls-04-pm.txt" (53 KB)


Regards,
Peter


-----Original Message-----
From: Shahram Davari [mailto:davari@broadcom.com]=20
Sent: June 4, 2013 7:40 PM
To: Meyer, Peter; tictoc@ietf.org
Subject: RE: [TICTOC] comments on draft-ietf-tictoc-1588overmpls-04.txt

Hi Peter,

Thanks for your god comments. Please see my responses inline. Please let
me know whether you are satisfied with my responses since I am updating
the draft in the next couple of days.

Thanks
Shahram

-----Original Message-----
From: tictoc-bounces@ietf.org [mailto:tictoc-bounces@ietf.org] On Behalf
Of Meyer, Peter
Sent: Monday, March 11, 2013 5:49 PM
To: tictoc@ietf.org
Subject: Re: [TICTOC] comments on draft-ietf-tictoc-1588overmpls-04.txt

Hi Shahram et al,

Some comments on draft -04.


1) Section 3.  "A generic method is defined in this document that does
not require deep packet inspection at line rate, and can
deterministically identify Timing messages.  The generic method is
applicable to MPLS and MPLS-TP networks."

May want to add that this would apply only to one-step TC (I imagine
that is the point of the correction at line rate).  A two-step TC would
need to do deep packet inspection as it uses sourcePortIdentity &
sequenceId fields for Follow_up or Delay_Resp.

SD> For 2-step, all that is needed is for an interface to detect the
Timing message (based on top MPLS Label)  and record the Time along with
some information from the Timing packet and send them to CPU while
forwarding the Timing message as usual. Then the CPU based on the
information received generates Follow-up message and injects it in to
the LSP.  Therefore it is the job of CPU to look at sourcePortIdentity &
sequenceId fields not the Hardware.


2) Section 4.  "An MPLS domain can serve multiple customers.  This means
that the MPLS domain (maintained by a service provider) may provide
timing services to multiple customers, each having their own Timing
domain.  Therefore LER BCs need to interact with multiple grandmasters,
and consequently multiple time references."

This should be re-phrased.  It switches from an optional situation ("may
provide timing services") to mandatory situation ("LER BCs need to
interact").   Some words such as "in such a deployment scenario, ...."
and replace "can" with "may".   We have seen at ITU at least (with
participation from operators BT, FT, DT, CMCC, AT&T, Sprint, etc.) that
this multiple operator domain case was not useful enough to be included
in standardization process for Telecom networks.

SD> I rephrased it as following:

" An MPLS domain can serve multiple customers.  This means that the
   MPLS domain (maintained by a service provider) may provide timing
   services to multiple customers, each having their own Timing domain.
   Therefore in such deployment scenarios, LER BCs may interact with
multiple grandmasters,=20
and consequently multiple time references.  Also, LER/LSR TCs MUST be
synchronized to the=20
same master clock (which is the service provider Master clock), which
implies that they need=20
to choose one master to synchronize to."


3) Section 19.  "For transporting such peer delay measurement messages a
single-hop LSP SHOULD to be created between the two adjacent LSRs
engaged in peer delay measurement to carry peer delay measurement
messages. Other methods such as PTP transport over Ethernet MAY be used
for transporting peer delay measurement messages if the link between the
two routers is Ethernet."


This new statement to handle peer-delay (which in earlier drafts did not
have a communication path listed), also allows a BC to be embedded in an
LSR with a communication path between BC's as a single-hop LSP
(mentioned March 22, 2012 in my feedback to draft -03, subject "[TICTOC]
Updated 1588 over MPLS draf-03").

SD> When a single-hop LSP is created then I call the both ends of that
LSP, LERs and not LSRs.
Note that a router can act as LSR for some LSPs and LER for other LSPs.
The point is that we can't
Terminate a packet in the middle of an LSP (i.e., in an LSR). So BC
functionality can't exist in the middle
Of a PTP LSP. So I think it is a matter of terminology otherwise I agree
that you could have BC in the core
(not edge).=20

Architecture diagrams Figure 1 and Figure should be updated to reflect
the possibility of either BC or TC implementation.   Section 18.2 and
section 18.3 and section 21 should also be updated to reflect the
possibility of either BC or TC.  I understand the RFC is intended to be
generic and not targeted only at TC.



4) Section 20.  "When the MPLS network (provider network) serves
multiple customers, it is important to maintain and process each
customers clock and Timing messages separately from other customers to
ensure there is no cross- customer effect.   For example if an LER BC is
synchronized to a specific grandmaster, belonging to customer A, then
the LER MUST use that BC clock only for customer A to ensure that
customer A cannot attack other customers by manipulating its time."

This seems much more applicable to the TC LSR and should be stated.
>From section 4 we see the TC uses the primary synchronization domain
(that of the service provide) to correct PTP messages.

SD> I don't see how in a TC LSR, one customer timing can affect other
customer timings?
Since in a TC, we just update the Timestamp of a packet based on the
Service provider Time.
May be I have not understood your point. Could you please clarify with
an example.



5) Section 20.  "Timing messages (as opposed to regular customer data)
SHOULD not be encrypted or authenticated on an end-to-end basis."  I
think there is a security draft in parallel being developed that may be
relevant to that statement.

SD> I have updated the  text as following:

" Timing messages MAY be encrypted or authenticated, provided that the
LERs/LSRs that are Timing capable/aware can authenticate/ decrypt the
timing messages."




Regards,
Peter


-----Original Message-----
From: tictoc-bounces@ietf.org [mailto:tictoc-bounces@ietf.org] On Behalf
Of internet-drafts@ietf.org
Sent: February 23, 2013 2:23 AM
To: i-d-announce@ietf.org
Cc: tictoc@ietf.org
Subject: [TICTOC] I-D Action: draft-ietf-tictoc-1588overmpls-04.txt


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

	Title           : Transporting Timing messages over MPLS
Networks
	Author(s)       : Shahram Davari
                          Amit Oren
                          Manav Bhatia
                          Peter Roberts
                          Laurent Montini
	Filename        : draft-ietf-tictoc-1588overmpls-04.txt
	Pages           : 36
	Date            : 2013-02-22

Abstract:
   This document defines the method for transporting Timing messages
   such as PTP and NTP over an MPLS network.  The method allows for the
   easy identification of these PDUs at the port level to allow for port
   level processing of these PDUs in both LERs and LSRs.

   The basic idea is to transport Timing messages inside dedicated MPLS
   LSPs.  These LSPs only carry timing messages and possibly Control and
   Management packets, but they do not carry customer traffic.

   Two methods for transporting Timing messages over MPLS are defined.
   The first method is to transport Timing messages directly over the
   dedicated MPLS LSP via UDP/IP encapsulation, which is suitable for
   MPLS networks.  The second method is to transport Timing messages
   inside a PW via Ethernet encapsulation, which is suitable for both
   MPLS and MPLS-TP networks.


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

There's also a htmlized version available at:
http://tools.ietf.org/html/draft-ietf-tictoc-1588overmpls-04

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


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

_______________________________________________
TICTOC mailing list
TICTOC@ietf.org
https://www.ietf.org/mailman/listinfo/tictoc


_______________________________________________
TICTOC mailing list
TICTOC@ietf.org
https://www.ietf.org/mailman/listinfo/tictoc












_______________________________________________
TICTOC mailing list
TICTOC@ietf.org
https://www.ietf.org/mailman/listinfo/tictoc







From Peter.Meyer@microsemi.com  Wed Jun  5 16:36:19 2013
Return-Path: <Peter.Meyer@microsemi.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 262EC11E80AE for <tictoc@ietfa.amsl.com>; Wed,  5 Jun 2013 16:36:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.599
X-Spam-Level: 
X-Spam-Status: No, score=-5.599 tagged_above=-999 required=5 tests=[AWL=1.000,  BAYES_00=-2.599, 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 VDmCZFcMQj5C for <tictoc@ietfa.amsl.com>; Wed,  5 Jun 2013 16:36:13 -0700 (PDT)
Received: from co9outboundpool.messaging.microsoft.com (co9ehsobe003.messaging.microsoft.com [207.46.163.26]) by ietfa.amsl.com (Postfix) with ESMTP id 8275F11E80D2 for <tictoc@ietf.org>; Wed,  5 Jun 2013 16:35:56 -0700 (PDT)
Received: from mail41-co9-R.bigfish.com (10.236.132.231) by CO9EHSOBE023.bigfish.com (10.236.130.86) with Microsoft SMTP Server id 14.1.225.23; Wed, 5 Jun 2013 23:35:26 +0000
Received: from mail41-co9 (localhost [127.0.0.1])	by mail41-co9-R.bigfish.com (Postfix) with ESMTP id 40E6924023A; Wed,  5 Jun 2013 23:35:26 +0000 (UTC)
X-Forefront-Antispam-Report: CIP:209.226.172.12; KIP:(null); UIP:(null); IPV:NLI; H:ottsrv0014.microsemi.net; RD:none; EFVD:NLI
X-SpamScore: -24
X-BigFish: VS-24(zz9371I936eI542I4015Izz1f42h1ee6h1de0h1fdah1202h1e76h1d1ah1d2ah1fc6hzz1033IL17326ah8275dhz2dh668h839h944hd25hf0ah1220h1288h12a5h12a9h12bdh137ah13b6h1441h14ddh1504h1537h153bh15d0h162dh1631h1758h184fh18e1h1946h19b5h1ad9h1b0ah1c24h1d0ch1d2eh1d3fh1dfeh1dffh1e1dh1155h)
Received: from mail41-co9 (localhost.localdomain [127.0.0.1]) by mail41-co9 (MessageSwitch) id 1370475323556764_15687; Wed,  5 Jun 2013 23:35:23 +0000 (UTC)
Received: from CO9EHSMHS022.bigfish.com (unknown [10.236.132.234])	by mail41-co9.bigfish.com (Postfix) with ESMTP id 792DAD0005F; Wed,  5 Jun 2013 23:35:23 +0000 (UTC)
Received: from ottsrv0014.microsemi.net (209.226.172.12) by CO9EHSMHS022.bigfish.com (10.236.130.32) with Microsoft SMTP Server id 14.1.225.23; Wed, 5 Jun 2013 23:35:22 +0000
Received: from ottsrv0015.microsemi.net ([134.199.15.151]) by ottsrv0014.microsemi.net with Microsoft SMTPSVC(6.0.3790.4675); Wed, 5 Jun 2013 19:35:21 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-Class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Wed, 5 Jun 2013 19:35:07 -0400
Message-ID: <64683B4805156847B0ED373DAB3057CA01B19E9C@ottsrv0015.microsemi.net>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [TICTOC] comments on draft-ietf-tictoc-1588overmpls-04.txt
Thread-Index: AQHOHrvIG9Qp4DAEq0WS7lIAjM8M8JkmuDRwgAE3KqCAADsOgIAABF6wgAAHahCAAAEIcIAAAdVwgAAFM5CAAAX/MIAABGhAgAADjKCAAABOQA==
References: <20130223072233.32735.89371.idtracker@ietfa.amsl.com> <64683B4805156847B0ED373DAB3057CA015E930D@ottsrv0015.microsemi.net> <4A6CE49E6084B141B15C0713B8993F281BE28013@SJEXCHMB12.corp.ad.broadcom.com> <64683B4805156847B0ED373DAB3057CA01B19D5F@ottsrv0015.microsemi.net> <4A6CE49E6084B141B15C0713B8993F281BE2FD85@SJEXCHMB12.corp.ad.broadcom.com> <64683B4805156847B0ED373DAB3057CA01B19E70@ottsrv0015.microsemi.net> <4A6CE49E6084B141B15C0713B8993F281BE2FE6E@SJEXCHMB12.corp.ad.broadcom.com> <64683B4805156847B0ED373DAB3057CA01B19E80@ottsrv0015.microsemi.net> <4A6CE49E6084B141B15C0713B8993F281BE2FED7@SJEXCHMB12.corp.ad.broadcom.com> <4A6CE49E6084B141B15C0713B8993F281BE2FF54@SJEXCHMB12.corp.ad.broadcom.com> <64683B4805156847B0ED373DAB3057CA01B19E97@ottsrv0015
From: "Meyer, Peter" <Peter.Meyer@microsemi.com>
To: Shahram Davari <davari@broadcom.com>, <tictoc@ietf.org>
X-OriginalArrivalTime: 05 Jun 2013 23:35:21.0772 (UTC) FILETIME=[58854EC0:01CE6245]
X-OriginatorOrg: microsemi.com
Subject: Re: [TICTOC] comments on draft-ietf-tictoc-1588overmpls-04.txt
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: Wed, 05 Jun 2013 23:36:19 -0000

Slightly modified ......

"   A generic method is defined in this document that does not require
   deep packet inspection at line rate, and can deterministically
   identify Timing messages. This method is specifically beneficial for
1-step=20
 Transparent Clock operation described in [IEEE-1588].  =20
2-Step Transparent Clock operation, Ordinary Clock operation and
Boundary Clock operation are also supported."


Regards,
Peter


-----Original Message-----
From: Shahram Davari [mailto:davari@broadcom.com]=20
Sent: June 5, 2013 7:32 PM
To: Meyer, Peter; tictoc@ietf.org
Subject: RE: [TICTOC] comments on draft-ietf-tictoc-1588overmpls-04.txt

How about rephrasing it as following:

"   A generic method is defined in this document that does not require
   deep packet inspection at line rate, and can deterministically
   identify Timing messages. This method is specifically beneficial for
1-step=20
 Transparent Clocking operation described in [IEEE-1588], while it also
supports=20
2-Step Transparent Clocking."

Thx
SD

-----Original Message-----
From: Meyer, Peter [mailto:Peter.Meyer@microsemi.com]=20
Sent: Wednesday, June 05, 2013 4:22 PM
To: Shahram Davari; tictoc@ietf.org
Subject: RE: [TICTOC] comments on draft-ietf-tictoc-1588overmpls-04.txt

Hi Shahram,

I think you are referring to section 3=20

"   A generic method is defined in this document that does not require
   deep packet inspection at line rate, and can deterministically
   identify Timing messages, for one-step mode of operation.  The=20
   generic method is applicable to MPLS and MPLS-TP networks."


I was not intending to indicate two-step would not work.   I was
intending to highlight the important benefit of this document is
specifically to enable one-step capability more easily.  Without this
specification one-step is more difficult due to the need for deep packet
inspection.  Two-step would probably not benefit as much as a result of
this specification.

If I have not worded correctly, it can be removed/changed back to
original.


Regards,
Peter



-----Original Message-----
From: Shahram Davari [mailto:davari@broadcom.com]=20
Sent: June 5, 2013 7:04 PM
To: Shahram Davari; Meyer, Peter; tictoc@ietf.org
Subject: RE: [TICTOC] comments on draft-ietf-tictoc-1588overmpls-04.txt

Peter,

Could you please also explain why the 2 step won't work with the method
in this draft.

Thx
Shahram

-----Original Message-----
From: tictoc-bounces@ietf.org [mailto:tictoc-bounces@ietf.org] On Behalf
Of Shahram Davari
Sent: Wednesday, June 05, 2013 3:43 PM
To: Meyer, Peter; tictoc@ietf.org
Subject: Re: [TICTOC] comments on draft-ietf-tictoc-1588overmpls-04.txt

Hi Peter,

Thanks, now I get it.  I will update the draft as per your suggestion.

Thx
Shahram

-----Original Message-----
From: Meyer, Peter [mailto:Peter.Meyer@microsemi.com]=20
Sent: Wednesday, June 05, 2013 3:35 PM
To: Shahram Davari; tictoc@ietf.org
Subject: RE: [TICTOC] comments on draft-ietf-tictoc-1588overmpls-04.txt


Hi Shahram,

I attempted to elaborate in section 19 Other Considerations, perhaps it
is not well written.  I tried to mirror the language that already
existed.


With the original -04 draft, section 19 covered the situation for an LSR
acting as a TC when using peer-delay messages.   An LSR would have to
generate & terminate peer-delay messages from its physical neighbour,
and the recommendation was to use a single-hop LSP.  With your
terminology, if I am using it correctly, the Sync messages are switched
through the LSR without termination.   However, this is not allowed for
peer-delay messages which must be terminated for the TC to function
properly.

"  For transporting such peer delay measurement messages a single-hop
   LSP SHOULD to be created between the two adjacent LSRs engaged in
   peer delay measurement to carry peer delay measurement messages.
   Other methods such as PTP transport over Ethernet MAY be used for
   transporting peer delay measurement messages if the link between the
   two routers is Ethernet.  "


I use this same approach for an LSR acting as a BC.   A BC inside an LSR
is the same as a peer-delay TC inside an LSR.  The LSR would have to
generate & terminate end-to-end messages from its physical neighbour. I
modified the section to recommend a single-hop LSP for this purpose.

"  Likewise for BCs embedded in an LSR, a single-hop LSP SHOULD be=20
   created between the two adjacent LSRs that are acting as BCs.  Other
   methods such as PTP transport over Ethernet MAY be used if the link
   between the two routers is Ethernet.  "


Hope this makes sense.

Regards,
Peter


-----Original Message-----
From: Shahram Davari [mailto:davari@broadcom.com]=20
Sent: June 5, 2013 6:18 PM
To: Meyer, Peter; tictoc@ietf.org
Subject: RE: [TICTOC] comments on draft-ietf-tictoc-1588overmpls-04.txt

Peter,

I think we have a difference in terminology. To me an LSR is a router
that does Label Swap and not Label pop. May be what you have in mind is
PE and P routers instead of LER and LSR.=20

Thx
Shahram

-----Original Message-----
From: Shahram Davari=20
Sent: Wednesday, June 05, 2013 3:16 PM
To: 'Meyer, Peter'; tictoc@ietf.org
Subject: RE: [TICTOC] comments on draft-ietf-tictoc-1588overmpls-04.txt

Hi Peter,

I see that the majority of changes are related to LSR BC. I personally
don't think this is possible, since we can't terminate packets in the
middle of an LSP. Could you please provide an example for your
suggestion of using LSR BC? How are the 1588 timing messages terminated?

Thanks
Shahram

-----Original Message-----
From: Meyer, Peter [mailto:Peter.Meyer@microsemi.com]=20
Sent: Wednesday, June 05, 2013 2:48 PM
To: Shahram Davari; tictoc@ietf.org
Subject: RE: [TICTOC] comments on draft-ietf-tictoc-1588overmpls-04.txt


Hi Shahram,

I took the -04 that was advertised on the exploder in February (dated
February 23, 2013).  I then edited that copy.

(I think the diff may show a ton of changes due to line length or word
wrapping).

Regards,
Peter


-----Original Message-----
From: Shahram Davari [mailto:davari@broadcom.com]=20
Sent: June 5, 2013 5:32 PM
To: Meyer, Peter; tictoc@ietf.org
Subject: RE: [TICTOC] comments on draft-ietf-tictoc-1588overmpls-04.txt

Thanks Peter.=20

These edits where done before the publishing of draft-04. Correct?

-Shahram

-----Original Message-----
From: Meyer, Peter [mailto:Peter.Meyer@microsemi.com]=20
Sent: Wednesday, June 05, 2013 11:01 AM
To: Shahram Davari; tictoc@ietf.org
Subject: RE: [TICTOC] comments on draft-ietf-tictoc-1588overmpls-04.txt

Hi Shahram,

I hope in-line with my comments I have edited the text of draft -04.

I'm not sure how the formatting worked out (PC-based, line length, page
length).

I modified sections 3, 4, 18, 19 & 20.

I include here both original and modified version so you can diff (most
of the changes in 3 are due to line length / re-org, not actual text
changes).

File attachment:
"draft-ietf-tictoc-1588overmpls-04-org.txt" (52 KB)
"draft-ietf-tictoc-1588overmpls-04-pm.txt" (53 KB)


Regards,
Peter


-----Original Message-----
From: Shahram Davari [mailto:davari@broadcom.com]=20
Sent: June 4, 2013 7:40 PM
To: Meyer, Peter; tictoc@ietf.org
Subject: RE: [TICTOC] comments on draft-ietf-tictoc-1588overmpls-04.txt

Hi Peter,

Thanks for your god comments. Please see my responses inline. Please let
me know whether you are satisfied with my responses since I am updating
the draft in the next couple of days.

Thanks
Shahram

-----Original Message-----
From: tictoc-bounces@ietf.org [mailto:tictoc-bounces@ietf.org] On Behalf
Of Meyer, Peter
Sent: Monday, March 11, 2013 5:49 PM
To: tictoc@ietf.org
Subject: Re: [TICTOC] comments on draft-ietf-tictoc-1588overmpls-04.txt

Hi Shahram et al,

Some comments on draft -04.


1) Section 3.  "A generic method is defined in this document that does
not require deep packet inspection at line rate, and can
deterministically identify Timing messages.  The generic method is
applicable to MPLS and MPLS-TP networks."

May want to add that this would apply only to one-step TC (I imagine
that is the point of the correction at line rate).  A two-step TC would
need to do deep packet inspection as it uses sourcePortIdentity &
sequenceId fields for Follow_up or Delay_Resp.

SD> For 2-step, all that is needed is for an interface to detect the
Timing message (based on top MPLS Label)  and record the Time along with
some information from the Timing packet and send them to CPU while
forwarding the Timing message as usual. Then the CPU based on the
information received generates Follow-up message and injects it in to
the LSP.  Therefore it is the job of CPU to look at sourcePortIdentity &
sequenceId fields not the Hardware.


2) Section 4.  "An MPLS domain can serve multiple customers.  This means
that the MPLS domain (maintained by a service provider) may provide
timing services to multiple customers, each having their own Timing
domain.  Therefore LER BCs need to interact with multiple grandmasters,
and consequently multiple time references."

This should be re-phrased.  It switches from an optional situation ("may
provide timing services") to mandatory situation ("LER BCs need to
interact").   Some words such as "in such a deployment scenario, ...."
and replace "can" with "may".   We have seen at ITU at least (with
participation from operators BT, FT, DT, CMCC, AT&T, Sprint, etc.) that
this multiple operator domain case was not useful enough to be included
in standardization process for Telecom networks.

SD> I rephrased it as following:

" An MPLS domain can serve multiple customers.  This means that the
   MPLS domain (maintained by a service provider) may provide timing
   services to multiple customers, each having their own Timing domain.
   Therefore in such deployment scenarios, LER BCs may interact with
multiple grandmasters,=20
and consequently multiple time references.  Also, LER/LSR TCs MUST be
synchronized to the=20
same master clock (which is the service provider Master clock), which
implies that they need=20
to choose one master to synchronize to."


3) Section 19.  "For transporting such peer delay measurement messages a
single-hop LSP SHOULD to be created between the two adjacent LSRs
engaged in peer delay measurement to carry peer delay measurement
messages. Other methods such as PTP transport over Ethernet MAY be used
for transporting peer delay measurement messages if the link between the
two routers is Ethernet."


This new statement to handle peer-delay (which in earlier drafts did not
have a communication path listed), also allows a BC to be embedded in an
LSR with a communication path between BC's as a single-hop LSP
(mentioned March 22, 2012 in my feedback to draft -03, subject "[TICTOC]
Updated 1588 over MPLS draf-03").

SD> When a single-hop LSP is created then I call the both ends of that
LSP, LERs and not LSRs.
Note that a router can act as LSR for some LSPs and LER for other LSPs.
The point is that we can't
Terminate a packet in the middle of an LSP (i.e., in an LSR). So BC
functionality can't exist in the middle
Of a PTP LSP. So I think it is a matter of terminology otherwise I agree
that you could have BC in the core
(not edge).=20

Architecture diagrams Figure 1 and Figure should be updated to reflect
the possibility of either BC or TC implementation.   Section 18.2 and
section 18.3 and section 21 should also be updated to reflect the
possibility of either BC or TC.  I understand the RFC is intended to be
generic and not targeted only at TC.



4) Section 20.  "When the MPLS network (provider network) serves
multiple customers, it is important to maintain and process each
customers clock and Timing messages separately from other customers to
ensure there is no cross- customer effect.   For example if an LER BC is
synchronized to a specific grandmaster, belonging to customer A, then
the LER MUST use that BC clock only for customer A to ensure that
customer A cannot attack other customers by manipulating its time."

This seems much more applicable to the TC LSR and should be stated.
>From section 4 we see the TC uses the primary synchronization domain
(that of the service provide) to correct PTP messages.

SD> I don't see how in a TC LSR, one customer timing can affect other
customer timings?
Since in a TC, we just update the Timestamp of a packet based on the
Service provider Time.
May be I have not understood your point. Could you please clarify with
an example.



5) Section 20.  "Timing messages (as opposed to regular customer data)
SHOULD not be encrypted or authenticated on an end-to-end basis."  I
think there is a security draft in parallel being developed that may be
relevant to that statement.

SD> I have updated the  text as following:

" Timing messages MAY be encrypted or authenticated, provided that the
LERs/LSRs that are Timing capable/aware can authenticate/ decrypt the
timing messages."




Regards,
Peter


-----Original Message-----
From: tictoc-bounces@ietf.org [mailto:tictoc-bounces@ietf.org] On Behalf
Of internet-drafts@ietf.org
Sent: February 23, 2013 2:23 AM
To: i-d-announce@ietf.org
Cc: tictoc@ietf.org
Subject: [TICTOC] I-D Action: draft-ietf-tictoc-1588overmpls-04.txt


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

	Title           : Transporting Timing messages over MPLS
Networks
	Author(s)       : Shahram Davari
                          Amit Oren
                          Manav Bhatia
                          Peter Roberts
                          Laurent Montini
	Filename        : draft-ietf-tictoc-1588overmpls-04.txt
	Pages           : 36
	Date            : 2013-02-22

Abstract:
   This document defines the method for transporting Timing messages
   such as PTP and NTP over an MPLS network.  The method allows for the
   easy identification of these PDUs at the port level to allow for port
   level processing of these PDUs in both LERs and LSRs.

   The basic idea is to transport Timing messages inside dedicated MPLS
   LSPs.  These LSPs only carry timing messages and possibly Control and
   Management packets, but they do not carry customer traffic.

   Two methods for transporting Timing messages over MPLS are defined.
   The first method is to transport Timing messages directly over the
   dedicated MPLS LSP via UDP/IP encapsulation, which is suitable for
   MPLS networks.  The second method is to transport Timing messages
   inside a PW via Ethernet encapsulation, which is suitable for both
   MPLS and MPLS-TP networks.


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

There's also a htmlized version available at:
http://tools.ietf.org/html/draft-ietf-tictoc-1588overmpls-04

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


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

_______________________________________________
TICTOC mailing list
TICTOC@ietf.org
https://www.ietf.org/mailman/listinfo/tictoc


_______________________________________________
TICTOC mailing list
TICTOC@ietf.org
https://www.ietf.org/mailman/listinfo/tictoc












_______________________________________________
TICTOC mailing list
TICTOC@ietf.org
https://www.ietf.org/mailman/listinfo/tictoc









From davari@broadcom.com  Wed Jun  5 16:39:51 2013
Return-Path: <davari@broadcom.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 7B5C511E80E0 for <tictoc@ietfa.amsl.com>; Wed,  5 Jun 2013 16:38:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id dpy8yOrtS2cI for <tictoc@ietfa.amsl.com>; Wed,  5 Jun 2013 16:38:54 -0700 (PDT)
Received: from mms1.broadcom.com (mms1.broadcom.com [216.31.210.17]) by ietfa.amsl.com (Postfix) with ESMTP id 7B15021E809D for <tictoc@ietf.org>; Wed,  5 Jun 2013 16:37:25 -0700 (PDT)
Received: from [10.9.208.55] by mms1.broadcom.com with ESMTP (Broadcom SMTP Relay (Email Firewall v6.5)); Wed, 05 Jun 2013 16:33:30 -0700
X-Server-Uuid: 06151B78-6688-425E-9DE2-57CB27892261
Received: from SJEXCHCAS03.corp.ad.broadcom.com (10.16.203.8) by IRVEXCHCAS07.corp.ad.broadcom.com (10.9.208.55) with Microsoft SMTP Server (TLS) id 14.1.438.0; Wed, 5 Jun 2013 16:37:08 -0700
Received: from SJEXCHMB12.corp.ad.broadcom.com ( [fe80::bc15:c1e1:c29a:36f7]) by SJEXCHCAS03.corp.ad.broadcom.com ( [::1]) with mapi id 14.01.0438.000; Wed, 5 Jun 2013 16:37:08 -0700
From: "Shahram Davari" <davari@broadcom.com>
To: "Meyer, Peter" <Peter.Meyer@microsemi.com>, "tictoc@ietf.org" <tictoc@ietf.org>
Thread-Topic: [TICTOC] comments on draft-ietf-tictoc-1588overmpls-04.txt
Thread-Index: AQHOHrvIG9Qp4DAEq0WS7lIAjM8M8JkmuDRwgAE3KqCAADsOgIAABF6wgAAHahCAAAEIcIAAAdVwgAAFM5CAAAX/MIAABGhAgAADjKCAAABOQIAAASMA
Date: Wed, 5 Jun 2013 23:37:08 +0000
Message-ID: <4A6CE49E6084B141B15C0713B8993F281BE30047@SJEXCHMB12.corp.ad.broadcom.com>
References: <20130223072233.32735.89371.idtracker@ietfa.amsl.com> <64683B4805156847B0ED373DAB3057CA015E930D@ottsrv0015.microsemi.net> <4A6CE49E6084B141B15C0713B8993F281BE28013@SJEXCHMB12.corp.ad.broadcom.com> <64683B4805156847B0ED373DAB3057CA01B19D5F@ottsrv0015.microsemi.net> <4A6CE49E6084B141B15C0713B8993F281BE2FD85@SJEXCHMB12.corp.ad.broadcom.com> <64683B4805156847B0ED373DAB3057CA01B19E70@ottsrv0015.microsemi.net> <4A6CE49E6084B141B15C0713B8993F281BE2FE6E@SJEXCHMB12.corp.ad.broadcom.com> <64683B4805156847B0ED373DAB3057CA01B19E80@ottsrv0015.microsemi.net> <4A6CE49E6084B141B15C0713B8993F281BE2FED7@SJEXCHMB12.corp.ad.broadcom.com> <4A6CE49E6084B141B15C0713B8993F281BE2FF54@SJEXCHMB12.corp.ad.broadcom.com> <64683B4805156847B0ED373DAB3057CA01B19E97@ottsrv0015 <64683B4805156847B0ED373DAB3057CA01B19E9C@ottsrv0015.microsemi.net>
In-Reply-To: <64683B4805156847B0ED373DAB3057CA01B19E9C@ottsrv0015.microsemi.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.16.203.100]
MIME-Version: 1.0
X-WSS-ID: 7DB1154031W31997699-01-01
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Subject: Re: [TICTOC] comments on draft-ietf-tictoc-1588overmpls-04.txt
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: Wed, 05 Jun 2013 23:39:51 -0000

Great. Done. =20

-----Original Message-----
From: Meyer, Peter [mailto:Peter.Meyer@microsemi.com]=20
Sent: Wednesday, June 05, 2013 4:35 PM
To: Shahram Davari; tictoc@ietf.org
Subject: RE: [TICTOC] comments on draft-ietf-tictoc-1588overmpls-04.txt



Slightly modified ......

"   A generic method is defined in this document that does not require
   deep packet inspection at line rate, and can deterministically
   identify Timing messages. This method is specifically beneficial for
1-step=20
 Transparent Clock operation described in [IEEE-1588].  =20
2-Step Transparent Clock operation, Ordinary Clock operation and
Boundary Clock operation are also supported."


Regards,
Peter


-----Original Message-----
From: Shahram Davari [mailto:davari@broadcom.com]=20
Sent: June 5, 2013 7:32 PM
To: Meyer, Peter; tictoc@ietf.org
Subject: RE: [TICTOC] comments on draft-ietf-tictoc-1588overmpls-04.txt

How about rephrasing it as following:

"   A generic method is defined in this document that does not require
   deep packet inspection at line rate, and can deterministically
   identify Timing messages. This method is specifically beneficial for
1-step=20
 Transparent Clocking operation described in [IEEE-1588], while it also
supports=20
2-Step Transparent Clocking."

Thx
SD

-----Original Message-----
From: Meyer, Peter [mailto:Peter.Meyer@microsemi.com]=20
Sent: Wednesday, June 05, 2013 4:22 PM
To: Shahram Davari; tictoc@ietf.org
Subject: RE: [TICTOC] comments on draft-ietf-tictoc-1588overmpls-04.txt

Hi Shahram,

I think you are referring to section 3=20

"   A generic method is defined in this document that does not require
   deep packet inspection at line rate, and can deterministically
   identify Timing messages, for one-step mode of operation.  The=20
   generic method is applicable to MPLS and MPLS-TP networks."


I was not intending to indicate two-step would not work.   I was
intending to highlight the important benefit of this document is
specifically to enable one-step capability more easily.  Without this
specification one-step is more difficult due to the need for deep packet
inspection.  Two-step would probably not benefit as much as a result of
this specification.

If I have not worded correctly, it can be removed/changed back to
original.


Regards,
Peter



-----Original Message-----
From: Shahram Davari [mailto:davari@broadcom.com]=20
Sent: June 5, 2013 7:04 PM
To: Shahram Davari; Meyer, Peter; tictoc@ietf.org
Subject: RE: [TICTOC] comments on draft-ietf-tictoc-1588overmpls-04.txt

Peter,

Could you please also explain why the 2 step won't work with the method
in this draft.

Thx
Shahram

-----Original Message-----
From: tictoc-bounces@ietf.org [mailto:tictoc-bounces@ietf.org] On Behalf
Of Shahram Davari
Sent: Wednesday, June 05, 2013 3:43 PM
To: Meyer, Peter; tictoc@ietf.org
Subject: Re: [TICTOC] comments on draft-ietf-tictoc-1588overmpls-04.txt

Hi Peter,

Thanks, now I get it.  I will update the draft as per your suggestion.

Thx
Shahram

-----Original Message-----
From: Meyer, Peter [mailto:Peter.Meyer@microsemi.com]=20
Sent: Wednesday, June 05, 2013 3:35 PM
To: Shahram Davari; tictoc@ietf.org
Subject: RE: [TICTOC] comments on draft-ietf-tictoc-1588overmpls-04.txt


Hi Shahram,

I attempted to elaborate in section 19 Other Considerations, perhaps it
is not well written.  I tried to mirror the language that already
existed.


With the original -04 draft, section 19 covered the situation for an LSR
acting as a TC when using peer-delay messages.   An LSR would have to
generate & terminate peer-delay messages from its physical neighbour,
and the recommendation was to use a single-hop LSP.  With your
terminology, if I am using it correctly, the Sync messages are switched
through the LSR without termination.   However, this is not allowed for
peer-delay messages which must be terminated for the TC to function
properly.

"  For transporting such peer delay measurement messages a single-hop
   LSP SHOULD to be created between the two adjacent LSRs engaged in
   peer delay measurement to carry peer delay measurement messages.
   Other methods such as PTP transport over Ethernet MAY be used for
   transporting peer delay measurement messages if the link between the
   two routers is Ethernet.  "


I use this same approach for an LSR acting as a BC.   A BC inside an LSR
is the same as a peer-delay TC inside an LSR.  The LSR would have to
generate & terminate end-to-end messages from its physical neighbour. I
modified the section to recommend a single-hop LSP for this purpose.

"  Likewise for BCs embedded in an LSR, a single-hop LSP SHOULD be=20
   created between the two adjacent LSRs that are acting as BCs.  Other
   methods such as PTP transport over Ethernet MAY be used if the link
   between the two routers is Ethernet.  "


Hope this makes sense.

Regards,
Peter


-----Original Message-----
From: Shahram Davari [mailto:davari@broadcom.com]=20
Sent: June 5, 2013 6:18 PM
To: Meyer, Peter; tictoc@ietf.org
Subject: RE: [TICTOC] comments on draft-ietf-tictoc-1588overmpls-04.txt

Peter,

I think we have a difference in terminology. To me an LSR is a router
that does Label Swap and not Label pop. May be what you have in mind is
PE and P routers instead of LER and LSR.=20

Thx
Shahram

-----Original Message-----
From: Shahram Davari=20
Sent: Wednesday, June 05, 2013 3:16 PM
To: 'Meyer, Peter'; tictoc@ietf.org
Subject: RE: [TICTOC] comments on draft-ietf-tictoc-1588overmpls-04.txt

Hi Peter,

I see that the majority of changes are related to LSR BC. I personally
don't think this is possible, since we can't terminate packets in the
middle of an LSP. Could you please provide an example for your
suggestion of using LSR BC? How are the 1588 timing messages terminated?

Thanks
Shahram

-----Original Message-----
From: Meyer, Peter [mailto:Peter.Meyer@microsemi.com]=20
Sent: Wednesday, June 05, 2013 2:48 PM
To: Shahram Davari; tictoc@ietf.org
Subject: RE: [TICTOC] comments on draft-ietf-tictoc-1588overmpls-04.txt


Hi Shahram,

I took the -04 that was advertised on the exploder in February (dated
February 23, 2013).  I then edited that copy.

(I think the diff may show a ton of changes due to line length or word
wrapping).

Regards,
Peter


-----Original Message-----
From: Shahram Davari [mailto:davari@broadcom.com]=20
Sent: June 5, 2013 5:32 PM
To: Meyer, Peter; tictoc@ietf.org
Subject: RE: [TICTOC] comments on draft-ietf-tictoc-1588overmpls-04.txt

Thanks Peter.=20

These edits where done before the publishing of draft-04. Correct?

-Shahram

-----Original Message-----
From: Meyer, Peter [mailto:Peter.Meyer@microsemi.com]=20
Sent: Wednesday, June 05, 2013 11:01 AM
To: Shahram Davari; tictoc@ietf.org
Subject: RE: [TICTOC] comments on draft-ietf-tictoc-1588overmpls-04.txt

Hi Shahram,

I hope in-line with my comments I have edited the text of draft -04.

I'm not sure how the formatting worked out (PC-based, line length, page
length).

I modified sections 3, 4, 18, 19 & 20.

I include here both original and modified version so you can diff (most
of the changes in 3 are due to line length / re-org, not actual text
changes).

File attachment:
"draft-ietf-tictoc-1588overmpls-04-org.txt" (52 KB)
"draft-ietf-tictoc-1588overmpls-04-pm.txt" (53 KB)


Regards,
Peter


-----Original Message-----
From: Shahram Davari [mailto:davari@broadcom.com]=20
Sent: June 4, 2013 7:40 PM
To: Meyer, Peter; tictoc@ietf.org
Subject: RE: [TICTOC] comments on draft-ietf-tictoc-1588overmpls-04.txt

Hi Peter,

Thanks for your god comments. Please see my responses inline. Please let
me know whether you are satisfied with my responses since I am updating
the draft in the next couple of days.

Thanks
Shahram

-----Original Message-----
From: tictoc-bounces@ietf.org [mailto:tictoc-bounces@ietf.org] On Behalf
Of Meyer, Peter
Sent: Monday, March 11, 2013 5:49 PM
To: tictoc@ietf.org
Subject: Re: [TICTOC] comments on draft-ietf-tictoc-1588overmpls-04.txt

Hi Shahram et al,

Some comments on draft -04.


1) Section 3.  "A generic method is defined in this document that does
not require deep packet inspection at line rate, and can
deterministically identify Timing messages.  The generic method is
applicable to MPLS and MPLS-TP networks."

May want to add that this would apply only to one-step TC (I imagine
that is the point of the correction at line rate).  A two-step TC would
need to do deep packet inspection as it uses sourcePortIdentity &
sequenceId fields for Follow_up or Delay_Resp.

SD> For 2-step, all that is needed is for an interface to detect the
Timing message (based on top MPLS Label)  and record the Time along with
some information from the Timing packet and send them to CPU while
forwarding the Timing message as usual. Then the CPU based on the
information received generates Follow-up message and injects it in to
the LSP.  Therefore it is the job of CPU to look at sourcePortIdentity &
sequenceId fields not the Hardware.


2) Section 4.  "An MPLS domain can serve multiple customers.  This means
that the MPLS domain (maintained by a service provider) may provide
timing services to multiple customers, each having their own Timing
domain.  Therefore LER BCs need to interact with multiple grandmasters,
and consequently multiple time references."

This should be re-phrased.  It switches from an optional situation ("may
provide timing services") to mandatory situation ("LER BCs need to
interact").   Some words such as "in such a deployment scenario, ...."
and replace "can" with "may".   We have seen at ITU at least (with
participation from operators BT, FT, DT, CMCC, AT&T, Sprint, etc.) that
this multiple operator domain case was not useful enough to be included
in standardization process for Telecom networks.

SD> I rephrased it as following:

" An MPLS domain can serve multiple customers.  This means that the
   MPLS domain (maintained by a service provider) may provide timing
   services to multiple customers, each having their own Timing domain.
   Therefore in such deployment scenarios, LER BCs may interact with
multiple grandmasters,=20
and consequently multiple time references.  Also, LER/LSR TCs MUST be
synchronized to the=20
same master clock (which is the service provider Master clock), which
implies that they need=20
to choose one master to synchronize to."


3) Section 19.  "For transporting such peer delay measurement messages a
single-hop LSP SHOULD to be created between the two adjacent LSRs
engaged in peer delay measurement to carry peer delay measurement
messages. Other methods such as PTP transport over Ethernet MAY be used
for transporting peer delay measurement messages if the link between the
two routers is Ethernet."


This new statement to handle peer-delay (which in earlier drafts did not
have a communication path listed), also allows a BC to be embedded in an
LSR with a communication path between BC's as a single-hop LSP
(mentioned March 22, 2012 in my feedback to draft -03, subject "[TICTOC]
Updated 1588 over MPLS draf-03").

SD> When a single-hop LSP is created then I call the both ends of that
LSP, LERs and not LSRs.
Note that a router can act as LSR for some LSPs and LER for other LSPs.
The point is that we can't
Terminate a packet in the middle of an LSP (i.e., in an LSR). So BC
functionality can't exist in the middle
Of a PTP LSP. So I think it is a matter of terminology otherwise I agree
that you could have BC in the core
(not edge).=20

Architecture diagrams Figure 1 and Figure should be updated to reflect
the possibility of either BC or TC implementation.   Section 18.2 and
section 18.3 and section 21 should also be updated to reflect the
possibility of either BC or TC.  I understand the RFC is intended to be
generic and not targeted only at TC.



4) Section 20.  "When the MPLS network (provider network) serves
multiple customers, it is important to maintain and process each
customers clock and Timing messages separately from other customers to
ensure there is no cross- customer effect.   For example if an LER BC is
synchronized to a specific grandmaster, belonging to customer A, then
the LER MUST use that BC clock only for customer A to ensure that
customer A cannot attack other customers by manipulating its time."

This seems much more applicable to the TC LSR and should be stated.
>From section 4 we see the TC uses the primary synchronization domain
(that of the service provide) to correct PTP messages.

SD> I don't see how in a TC LSR, one customer timing can affect other
customer timings?
Since in a TC, we just update the Timestamp of a packet based on the
Service provider Time.
May be I have not understood your point. Could you please clarify with
an example.



5) Section 20.  "Timing messages (as opposed to regular customer data)
SHOULD not be encrypted or authenticated on an end-to-end basis."  I
think there is a security draft in parallel being developed that may be
relevant to that statement.

SD> I have updated the  text as following:

" Timing messages MAY be encrypted or authenticated, provided that the
LERs/LSRs that are Timing capable/aware can authenticate/ decrypt the
timing messages."




Regards,
Peter


-----Original Message-----
From: tictoc-bounces@ietf.org [mailto:tictoc-bounces@ietf.org] On Behalf
Of internet-drafts@ietf.org
Sent: February 23, 2013 2:23 AM
To: i-d-announce@ietf.org
Cc: tictoc@ietf.org
Subject: [TICTOC] I-D Action: draft-ietf-tictoc-1588overmpls-04.txt


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

	Title           : Transporting Timing messages over MPLS
Networks
	Author(s)       : Shahram Davari
                          Amit Oren
                          Manav Bhatia
                          Peter Roberts
                          Laurent Montini
	Filename        : draft-ietf-tictoc-1588overmpls-04.txt
	Pages           : 36
	Date            : 2013-02-22

Abstract:
   This document defines the method for transporting Timing messages
   such as PTP and NTP over an MPLS network.  The method allows for the
   easy identification of these PDUs at the port level to allow for port
   level processing of these PDUs in both LERs and LSRs.

   The basic idea is to transport Timing messages inside dedicated MPLS
   LSPs.  These LSPs only carry timing messages and possibly Control and
   Management packets, but they do not carry customer traffic.

   Two methods for transporting Timing messages over MPLS are defined.
   The first method is to transport Timing messages directly over the
   dedicated MPLS LSP via UDP/IP encapsulation, which is suitable for
   MPLS networks.  The second method is to transport Timing messages
   inside a PW via Ethernet encapsulation, which is suitable for both
   MPLS and MPLS-TP networks.


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

There's also a htmlized version available at:
http://tools.ietf.org/html/draft-ietf-tictoc-1588overmpls-04

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


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

_______________________________________________
TICTOC mailing list
TICTOC@ietf.org
https://www.ietf.org/mailman/listinfo/tictoc


_______________________________________________
TICTOC mailing list
TICTOC@ietf.org
https://www.ietf.org/mailman/listinfo/tictoc












_______________________________________________
TICTOC mailing list
TICTOC@ietf.org
https://www.ietf.org/mailman/listinfo/tictoc











From prvs=98697ac1d0=stefano.ruffini@ericsson.com  Wed Jun  5 23:39:33 2013
Return-Path: <prvs=98697ac1d0=stefano.ruffini@ericsson.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 5281021F9640 for <tictoc@ietfa.amsl.com>; Wed,  5 Jun 2013 23:39:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.249
X-Spam-Level: 
X-Spam-Status: No, score=-6.249 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_SE=0.35, 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 z6-1crpYa6LV for <tictoc@ietfa.amsl.com>; Wed,  5 Jun 2013 23:39:28 -0700 (PDT)
Received: from mailgw1.ericsson.se (mailgw1.ericsson.se [193.180.251.45]) by ietfa.amsl.com (Postfix) with ESMTP id 832E321F9636 for <tictoc@ietf.org>; Wed,  5 Jun 2013 23:39:27 -0700 (PDT)
X-AuditID: c1b4fb2d-b7f5d6d000003d54-80-51b02e9de0f0
Received: from ESESSHC017.ericsson.se (Unknown_Domain [153.88.253.125]) by mailgw1.ericsson.se (Symantec Mail Security) with SMTP id CB.71.15700.D9E20B15; Thu,  6 Jun 2013 08:39:25 +0200 (CEST)
Received: from ESESSMB301.ericsson.se ([169.254.1.55]) by ESESSHC017.ericsson.se ([153.88.183.69]) with mapi id 14.02.0328.009; Thu, 6 Jun 2013 08:39:25 +0200
From: Stefano Ruffini <stefano.ruffini@ericsson.com>
To: "Meyer, Peter" <Peter.Meyer@microsemi.com>, Shahram Davari <davari@broadcom.com>, "tictoc@ietf.org" <tictoc@ietf.org>
Thread-Topic: [TICTOC] comments on draft-ietf-tictoc-1588overmpls-04.txt
Thread-Index: AQHOHrvIG9Qp4DAEq0WS7lIAjM8M8JkmuDRwgAE3KqCAAAYJEIAAD6TwgAC7zlA=
Date: Thu, 6 Jun 2013 06:39:23 +0000
Message-ID: <1B5CAFEB4D81154AA0F020783784C3150C789D@ESESSMB301.ericsson.se>
References: <20130223072233.32735.89371.idtracker@ietfa.amsl.com><64683B4805156847B0ED373DAB3057CA015E930D@ottsrv0015.microsemi.net><4A6CE49E6084B141B15C0713B8993F281BE28013@SJEXCHMB12.corp.ad.broadcom.com> <64683B4805156847B0ED373DAB3057CA01B19D5F@ottsrv0015.microsemi.net> <1B5CAFEB4D81154AA0F020783784C3150C775B@ESESSMB301.ericsson.se> <64683B4805156847B0ED373DAB3057CA01B19DBA@ottsrv0015.microsemi.net>
In-Reply-To: <64683B4805156847B0ED373DAB3057CA01B19DBA@ottsrv0015.microsemi.net>
Accept-Language: it-IT, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [153.88.183.20]
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFrrALMWRmVeSWpSXmKPExsUyM+Jvre5cvQ2BBldmWlqs7/W0aL94lMXi b3MPuwOzx6z7Z9k8liz5yeQxZ+1DtgDmKG6bpMSSsuDM9Dx9uwTujB1TOpgLFsRXrJ27grmB 8Yd3FyMnh4SAicTSrxvYIGwxiQv31gPZXBxCAocZJTbP+MQO4SxilJjT3cQOUsUG1PF88Wqm LkYODhGBaolJL4RAwsIC7hJz/y9nAbFFBDwkpnY9gbL9JPqPtTCC2CwCKhIL/zYxgdi8At4S fRfXM0HMn8MssX7GN7AiToEAiY5ph8BsRgFZiQm7F4HZzALiEreezGeCuFRAYsme88wQtqjE y8f/WCFsRYmr05czQdTrSdyYOoUNwtaWWLbwNTPEYkGJkzOfsExgFJ2FZOwsJC2zkLTMQtKy gJFlFSN7bmJmTnq54SZGYIQc3PJbdwfjqXMihxilOViUxHn1eBcHCgmkJ5akZqemFqQWxReV 5qQWH2Jk4uAEEVxSDYyZ9zZwZtyr6D6grFn1XOvc5IgPjr3mWda1fFWNPkc6J7lOf/eu5OFl zk/P1I8cfvMmWWvKIdvZQtcZY+pcuPqKGuq59fyTtDInKG/9+vjTLoOZL2R+Td5ltXxl4GyR ok3sbBcuHpya67zd+Ur3uv1cIg+31xy0OPFxrsWRUvsPDBM+lc21lVdRYinOSDTUYi4qTgQA 83uMvWMCAAA=
Subject: Re: [TICTOC] comments on draft-ietf-tictoc-1588overmpls-04.txt
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, 06 Jun 2013 06:39:33 -0000

Hi Peter,

The point is that while technically it might be possible, if compared with =
a TC, the use of BC in a multi operator context looks over complicated  (no=
te: I am not referring to a BC connected to multiple PTP domains and that i=
n the end must just select one of them; in this case the BC would have to a=
ctually maintain different time scales, independent datasets, run independe=
nt BMCA, etc.). This can be an issue in case where  the number of clients a=
 provider network needs to serve is significantly high. =20
At least a note with some warning could be beneficial (e.g. "Note: the appl=
icability of a BC in the context of multiple customers may need further inv=
estigation. ")

Br
stefano

-----Original Message-----
From: Meyer, Peter [mailto:Peter.Meyer@microsemi.com]=20
Sent: mercoled=EC 5 giugno 2013 21:21
To: Stefano Ruffini; Shahram Davari; tictoc@ietf.org
Subject: RE: [TICTOC] comments on draft-ietf-tictoc-1588overmpls-04.txt


Hi Stefano,

I see Figure 3 and Figure 4 apply to the text above the figures, unrelated =
to multiple domains.

I see the multiple domain paragraph as a separate topic, perhaps could be i=
ts own sub-section.  We have seen systems that support multiple domains eit=
her as BC or TC.  I could support removal of the mention of multiple operat=
or domains in total, if that is agreeable.  Otherwise I see BC and TC as bo=
th valid solutions available in the market today.

Regards,
Peter


-----Original Message-----
From: Stefano Ruffini [mailto:stefano.ruffini@ericsson.com]=20
Sent: June 5, 2013 2:31 PM
To: Meyer, Peter; Shahram Davari; tictoc@ietf.org
Subject: RE: [TICTOC] comments on draft-ietf-tictoc-1588overmpls-04.txt

Hi Shahram, Peter

There is one point I would disagree with (I am referring to Peter's latest =
proposal, but the same comment would apply to the previous text):
"
An MPLS domain may serve multiple customers.  In these cases the
   MPLS domain (maintained by a service provider) may provide timing
   services to multiple customers, each having their own Timing domain.
   If so, then the LER BCs and TCs may interact with multiple grandmasters,
   and consequently multiple time references.  Also, LER/LSR TCs MUST be
   synchronized to the same master clock (which is the service provider
   Master clock), which implies that they need to choose one master to
   which it will synchronize.
"

My understanding of this statement is that a LER would need to implement mu=
ltiple BC instances (with multiple clocks); this looks too complex.

The case of multiple operators, seems to me only practically applicable to =
figure 3 (LER TC).

I would then propose to remove the reference to LER BC in this statement .

Best regards
stefano


-----Original Message-----
From: tictoc-bounces@ietf.org [mailto:tictoc-bounces@ietf.org] On Behalf Of=
 Meyer, Peter
Sent: mercoled=EC 5 giugno 2013 20:01
To: Shahram Davari; tictoc@ietf.org
Subject: Re: [TICTOC] comments on draft-ietf-tictoc-1588overmpls-04.txt

Hi Shahram,

I hope in-line with my comments I have edited the text of draft -04.

I'm not sure how the formatting worked out (PC-based, line length, page len=
gth).

I modified sections 3, 4, 18, 19 & 20.

I include here both original and modified version so you can diff (most of =
the changes in 3 are due to line length / re-org, not actual text changes).

File attachment:
"draft-ietf-tictoc-1588overmpls-04-org.txt" (52 KB) "draft-ietf-tictoc-1588=
overmpls-04-pm.txt" (53 KB)


Regards,
Peter


-----Original Message-----
From: Shahram Davari [mailto:davari@broadcom.com]
Sent: June 4, 2013 7:40 PM
To: Meyer, Peter; tictoc@ietf.org
Subject: RE: [TICTOC] comments on draft-ietf-tictoc-1588overmpls-04.txt

Hi Peter,

Thanks for your god comments. Please see my responses inline. Please let me=
 know whether you are satisfied with my responses since I am updating the d=
raft in the next couple of days.

Thanks
Shahram

-----Original Message-----
From: tictoc-bounces@ietf.org [mailto:tictoc-bounces@ietf.org] On Behalf Of=
 Meyer, Peter
Sent: Monday, March 11, 2013 5:49 PM
To: tictoc@ietf.org
Subject: Re: [TICTOC] comments on draft-ietf-tictoc-1588overmpls-04.txt

Hi Shahram et al,

Some comments on draft -04.


1) Section 3.  "A generic method is defined in this document that does not =
require deep packet inspection at line rate, and can deterministically iden=
tify Timing messages.  The generic method is applicable to MPLS and MPLS-TP=
 networks."

May want to add that this would apply only to one-step TC (I imagine that i=
s the point of the correction at line rate).  A two-step TC would need to d=
o deep packet inspection as it uses sourcePortIdentity & sequenceId fields =
for Follow_up or Delay_Resp.

SD> For 2-step, all that is needed is for an interface to detect the
Timing message (based on top MPLS Label)  and record the Time along with so=
me information from the Timing packet and send them to CPU while forwarding=
 the Timing message as usual. Then the CPU based on the information receive=
d generates Follow-up message and injects it in to the LSP.  Therefore it i=
s the job of CPU to look at sourcePortIdentity & sequenceId fields not the =
Hardware.


2) Section 4.  "An MPLS domain can serve multiple customers.  This means th=
at the MPLS domain (maintained by a service provider) may provide timing se=
rvices to multiple customers, each having their own Timing domain.  Therefo=
re LER BCs need to interact with multiple grandmasters, and consequently mu=
ltiple time references."

This should be re-phrased.  It switches from an optional situation ("may pr=
ovide timing services") to mandatory situation ("LER BCs need to
interact").   Some words such as "in such a deployment scenario, ...."
and replace "can" with "may".   We have seen at ITU at least (with
participation from operators BT, FT, DT, CMCC, AT&T, Sprint, etc.) that thi=
s multiple operator domain case was not useful enough to be included in sta=
ndardization process for Telecom networks.

SD> I rephrased it as following:

" An MPLS domain can serve multiple customers.  This means that the
   MPLS domain (maintained by a service provider) may provide timing
   services to multiple customers, each having their own Timing domain.
   Therefore in such deployment scenarios, LER BCs may interact with multip=
le grandmasters, and consequently multiple time references.  Also, LER/LSR =
TCs MUST be synchronized to the same master clock (which is the service pro=
vider Master clock), which implies that they need to choose one master to s=
ynchronize to."


3) Section 19.  "For transporting such peer delay measurement messages a si=
ngle-hop LSP SHOULD to be created between the two adjacent LSRs engaged in =
peer delay measurement to carry peer delay measurement messages. Other meth=
ods such as PTP transport over Ethernet MAY be used for transporting peer d=
elay measurement messages if the link between the two routers is Ethernet."


This new statement to handle peer-delay (which in earlier drafts did not ha=
ve a communication path listed), also allows a BC to be embedded in an LSR =
with a communication path between BC's as a single-hop LSP (mentioned March=
 22, 2012 in my feedback to draft -03, subject "[TICTOC] Updated 1588 over =
MPLS draf-03").

SD> When a single-hop LSP is created then I call the both ends of that
LSP, LERs and not LSRs.
Note that a router can act as LSR for some LSPs and LER for other LSPs.
The point is that we can't
Terminate a packet in the middle of an LSP (i.e., in an LSR). So BC functio=
nality can't exist in the middle Of a PTP LSP. So I think it is a matter of=
 terminology otherwise I agree that you could have BC in the core (not edge=
).=20

Architecture diagrams Figure 1 and Figure should be updated to reflect
the possibility of either BC or TC implementation.   Section 18.2 and
section 18.3 and section 21 should also be updated to reflect the possibili=
ty of either BC or TC.  I understand the RFC is intended to be generic and =
not targeted only at TC.



4) Section 20.  "When the MPLS network (provider network) serves multiple c=
ustomers, it is important to maintain and process each customers clock and =
Timing messages separately from other customers to
ensure there is no cross- customer effect.   For example if an LER BC is
synchronized to a specific grandmaster, belonging to customer A, then the L=
ER MUST use that BC clock only for customer A to ensure that customer A can=
not attack other customers by manipulating its time."

This seems much more applicable to the TC LSR and should be stated.
>From section 4 we see the TC uses the primary synchronization domain (that =
of the service provide) to correct PTP messages.

SD> I don't see how in a TC LSR, one customer timing can affect other
customer timings?
Since in a TC, we just update the Timestamp of a packet based on the Servic=
e provider Time.
May be I have not understood your point. Could you please clarify with an e=
xample.



5) Section 20.  "Timing messages (as opposed to regular customer data) SHOU=
LD not be encrypted or authenticated on an end-to-end basis."  I think ther=
e is a security draft in parallel being developed that may be relevant to t=
hat statement.

SD> I have updated the  text as following:

" Timing messages MAY be encrypted or authenticated, provided that the LERs=
/LSRs that are Timing capable/aware can authenticate/ decrypt the timing me=
ssages."




Regards,
Peter


-----Original Message-----
From: tictoc-bounces@ietf.org [mailto:tictoc-bounces@ietf.org] On Behalf Of=
 internet-drafts@ietf.org
Sent: February 23, 2013 2:23 AM
To: i-d-announce@ietf.org
Cc: tictoc@ietf.org
Subject: [TICTOC] I-D Action: draft-ietf-tictoc-1588overmpls-04.txt


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           : Transporting Timing messages over MPLS
Networks
	Author(s)       : Shahram Davari
                          Amit Oren
                          Manav Bhatia
                          Peter Roberts
                          Laurent Montini
	Filename        : draft-ietf-tictoc-1588overmpls-04.txt
	Pages           : 36
	Date            : 2013-02-22

Abstract:
   This document defines the method for transporting Timing messages
   such as PTP and NTP over an MPLS network.  The method allows for the
   easy identification of these PDUs at the port level to allow for port
   level processing of these PDUs in both LERs and LSRs.

   The basic idea is to transport Timing messages inside dedicated MPLS
   LSPs.  These LSPs only carry timing messages and possibly Control and
   Management packets, but they do not carry customer traffic.

   Two methods for transporting Timing messages over MPLS are defined.
   The first method is to transport Timing messages directly over the
   dedicated MPLS LSP via UDP/IP encapsulation, which is suitable for
   MPLS networks.  The second method is to transport Timing messages
   inside a PW via Ethernet encapsulation, which is suitable for both
   MPLS and MPLS-TP networks.


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

There's also a htmlized version available at:
http://tools.ietf.org/html/draft-ietf-tictoc-1588overmpls-04

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


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

_______________________________________________
TICTOC mailing list
TICTOC@ietf.org
https://www.ietf.org/mailman/listinfo/tictoc


_______________________________________________
TICTOC mailing list
TICTOC@ietf.org
https://www.ietf.org/mailman/listinfo/tictoc






From prvs=28691d1904=stefano.ruffini@ericsson.com  Wed Jun  5 23:46:39 2013
Return-Path: <prvs=28691d1904=stefano.ruffini@ericsson.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 B04C921F8D27 for <tictoc@ietfa.amsl.com>; Wed,  5 Jun 2013 23:46:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.249
X-Spam-Level: 
X-Spam-Status: No, score=-6.249 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_SE=0.35, 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 bJY++slQ6BMt for <tictoc@ietfa.amsl.com>; Wed,  5 Jun 2013 23:46:34 -0700 (PDT)
Received: from mailgw1.ericsson.se (mailgw1.ericsson.se [193.180.251.45]) by ietfa.amsl.com (Postfix) with ESMTP id 859AE21F9920 for <tictoc@ietf.org>; Wed,  5 Jun 2013 23:46:33 -0700 (PDT)
X-AuditID: c1b4fb2d-b7f5d6d000003d54-a2-51b030482eb8
Received: from ESESSHC003.ericsson.se (Unknown_Domain [153.88.253.125]) by mailgw1.ericsson.se (Symantec Mail Security) with SMTP id 23.52.15700.84030B15; Thu,  6 Jun 2013 08:46:32 +0200 (CEST)
Received: from ESESSMB301.ericsson.se ([169.254.1.55]) by ESESSHC003.ericsson.se ([153.88.183.27]) with mapi id 14.02.0328.009; Thu, 6 Jun 2013 08:46:32 +0200
From: Stefano Ruffini <stefano.ruffini@ericsson.com>
To: "Meyer, Peter" <Peter.Meyer@microsemi.com>, Shahram Davari <davari@broadcom.com>, "tictoc@ietf.org" <tictoc@ietf.org>
Thread-Topic: [TICTOC] comments on draft-ietf-tictoc-1588overmpls-04.txt
Thread-Index: AQHOHrvIG9Qp4DAEq0WS7lIAjM8M8JkmuDRwgAE3KqCAAAYJEIAAD6TwgAC7zlCAAAQuYA==
Date: Thu, 6 Jun 2013 06:46:31 +0000
Message-ID: <1B5CAFEB4D81154AA0F020783784C3150C78BE@ESESSMB301.ericsson.se>
References: <20130223072233.32735.89371.idtracker@ietfa.amsl.com><64683B4805156847B0ED373DAB3057CA015E930D@ottsrv0015.microsemi.net><4A6CE49E6084B141B15C0713B8993F281BE28013@SJEXCHMB12.corp.ad.broadcom.com> <64683B4805156847B0ED373DAB3057CA01B19D5F@ottsrv0015.microsemi.net> <1B5CAFEB4D81154AA0F020783784C3150C775B@ESESSMB301.ericsson.se> <64683B4805156847B0ED373DAB3057CA01B19DBA@ottsrv0015.microsemi.net> 
Accept-Language: it-IT, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [153.88.183.20]
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFjrILMWRmVeSWpSXmKPExsUyM+Jvra6HwYZAg+1ftC3W93patF88ymLx t7mH3YHZY9b9s2weS5b8ZPKYs/YhWwBzFLdNUmJJWXBmep6+XQJ3RvNq+YKmpIqTs/6wNzBO 9+ti5OCQEDCRuHmav4uRE8gUk7hwbz1bFyMXh5DAYUaJF0s6mEESQgKLGCUWdFeC2GxA9c8X r2YC6RURqJaY9EIIJCws4C4x9/9yFhBbRMBDYmrXEyg7TGLPgbtsIDaLgIrEqs6vjCA2r4C3 xJPjG1ghds1lllh9birYLkYBWYkJuxeBFTELiEvcejKfCeI4AYkle84zQ9iiEi8f/2OFsBUl rk5fzgRRrydxY+oUNghbW2LZwtfMEMsEJU7OfMIygVFkFpKxs5C0zELSMgtJywJGllWM7LmJ mTnp5YabGIExcHDLb90djKfOiRxilOZgURLn1eNdHCgkkJ5YkpqdmlqQWhRfVJqTWnyIkYmD E0RwSTUwKr16ecFn872wNRUmu/59KepZsfwuY4LLn9v8Ch3Pf8mdM7a/mcvdMO3h7rbwr1ea YncxJb3n3CHXMqdBeL5ywhv/wN7QjSkMNjfd2ePnViy0V7fYtLOk6ZrfygOzzNMW5cdJLA3e 83ca97JnqdfzNxpHT3GLL3/wfk4yc5Px8sMaE3ekJO22V2Ipzkg01GIuKk4EAOkFsh5UAgAA
Subject: Re: [TICTOC] comments on draft-ietf-tictoc-1588overmpls-04.txt
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, 06 Jun 2013 06:46:40 -0000

Hi

I just saw the latest version of the draft.

I am fine with the  generic text proposed in this draft.=20

Thanks
stefano

-----Original Message-----
From: Stefano Ruffini=20
Sent: gioved=EC 6 giugno 2013 08:39
To: 'Meyer, Peter'; Shahram Davari; tictoc@ietf.org
Subject: RE: [TICTOC] comments on draft-ietf-tictoc-1588overmpls-04.txt

Hi Peter,

The point is that while technically it might be possible, if compared with =
a TC, the use of BC in a multi operator context looks over complicated  (no=
te: I am not referring to a BC connected to multiple PTP domains and that i=
n the end must just select one of them; in this case the BC would have to a=
ctually maintain different time scales, independent datasets, run independe=
nt BMCA, etc.). This can be an issue in case where  the number of clients a=
 provider network needs to serve is significantly high. =20
At least a note with some warning could be beneficial (e.g. "Note: the appl=
icability of a BC in the context of multiple customers may need further inv=
estigation. ")

Br
stefano

-----Original Message-----
From: Meyer, Peter [mailto:Peter.Meyer@microsemi.com]=20
Sent: mercoled=EC 5 giugno 2013 21:21
To: Stefano Ruffini; Shahram Davari; tictoc@ietf.org
Subject: RE: [TICTOC] comments on draft-ietf-tictoc-1588overmpls-04.txt


Hi Stefano,

I see Figure 3 and Figure 4 apply to the text above the figures, unrelated =
to multiple domains.

I see the multiple domain paragraph as a separate topic, perhaps could be i=
ts own sub-section.  We have seen systems that support multiple domains eit=
her as BC or TC.  I could support removal of the mention of multiple operat=
or domains in total, if that is agreeable.  Otherwise I see BC and TC as bo=
th valid solutions available in the market today.

Regards,
Peter


-----Original Message-----
From: Stefano Ruffini [mailto:stefano.ruffini@ericsson.com]=20
Sent: June 5, 2013 2:31 PM
To: Meyer, Peter; Shahram Davari; tictoc@ietf.org
Subject: RE: [TICTOC] comments on draft-ietf-tictoc-1588overmpls-04.txt

Hi Shahram, Peter

There is one point I would disagree with (I am referring to Peter's latest =
proposal, but the same comment would apply to the previous text):
"
An MPLS domain may serve multiple customers.  In these cases the
   MPLS domain (maintained by a service provider) may provide timing
   services to multiple customers, each having their own Timing domain.
   If so, then the LER BCs and TCs may interact with multiple grandmasters,
   and consequently multiple time references.  Also, LER/LSR TCs MUST be
   synchronized to the same master clock (which is the service provider
   Master clock), which implies that they need to choose one master to
   which it will synchronize.
"

My understanding of this statement is that a LER would need to implement mu=
ltiple BC instances (with multiple clocks); this looks too complex.

The case of multiple operators, seems to me only practically applicable to =
figure 3 (LER TC).

I would then propose to remove the reference to LER BC in this statement .

Best regards
stefano


-----Original Message-----
From: tictoc-bounces@ietf.org [mailto:tictoc-bounces@ietf.org] On Behalf Of=
 Meyer, Peter
Sent: mercoled=EC 5 giugno 2013 20:01
To: Shahram Davari; tictoc@ietf.org
Subject: Re: [TICTOC] comments on draft-ietf-tictoc-1588overmpls-04.txt

Hi Shahram,

I hope in-line with my comments I have edited the text of draft -04.

I'm not sure how the formatting worked out (PC-based, line length, page len=
gth).

I modified sections 3, 4, 18, 19 & 20.

I include here both original and modified version so you can diff (most of =
the changes in 3 are due to line length / re-org, not actual text changes).

File attachment:
"draft-ietf-tictoc-1588overmpls-04-org.txt" (52 KB) "draft-ietf-tictoc-1588=
overmpls-04-pm.txt" (53 KB)


Regards,
Peter


-----Original Message-----
From: Shahram Davari [mailto:davari@broadcom.com]
Sent: June 4, 2013 7:40 PM
To: Meyer, Peter; tictoc@ietf.org
Subject: RE: [TICTOC] comments on draft-ietf-tictoc-1588overmpls-04.txt

Hi Peter,

Thanks for your god comments. Please see my responses inline. Please let me=
 know whether you are satisfied with my responses since I am updating the d=
raft in the next couple of days.

Thanks
Shahram

-----Original Message-----
From: tictoc-bounces@ietf.org [mailto:tictoc-bounces@ietf.org] On Behalf Of=
 Meyer, Peter
Sent: Monday, March 11, 2013 5:49 PM
To: tictoc@ietf.org
Subject: Re: [TICTOC] comments on draft-ietf-tictoc-1588overmpls-04.txt

Hi Shahram et al,

Some comments on draft -04.


1) Section 3.  "A generic method is defined in this document that does not =
require deep packet inspection at line rate, and can deterministically iden=
tify Timing messages.  The generic method is applicable to MPLS and MPLS-TP=
 networks."

May want to add that this would apply only to one-step TC (I imagine that i=
s the point of the correction at line rate).  A two-step TC would need to d=
o deep packet inspection as it uses sourcePortIdentity & sequenceId fields =
for Follow_up or Delay_Resp.

SD> For 2-step, all that is needed is for an interface to detect the
Timing message (based on top MPLS Label)  and record the Time along with so=
me information from the Timing packet and send them to CPU while forwarding=
 the Timing message as usual. Then the CPU based on the information receive=
d generates Follow-up message and injects it in to the LSP.  Therefore it i=
s the job of CPU to look at sourcePortIdentity & sequenceId fields not the =
Hardware.


2) Section 4.  "An MPLS domain can serve multiple customers.  This means th=
at the MPLS domain (maintained by a service provider) may provide timing se=
rvices to multiple customers, each having their own Timing domain.  Therefo=
re LER BCs need to interact with multiple grandmasters, and consequently mu=
ltiple time references."

This should be re-phrased.  It switches from an optional situation ("may pr=
ovide timing services") to mandatory situation ("LER BCs need to
interact").   Some words such as "in such a deployment scenario, ...."
and replace "can" with "may".   We have seen at ITU at least (with
participation from operators BT, FT, DT, CMCC, AT&T, Sprint, etc.) that thi=
s multiple operator domain case was not useful enough to be included in sta=
ndardization process for Telecom networks.

SD> I rephrased it as following:

" An MPLS domain can serve multiple customers.  This means that the
   MPLS domain (maintained by a service provider) may provide timing
   services to multiple customers, each having their own Timing domain.
   Therefore in such deployment scenarios, LER BCs may interact with multip=
le grandmasters, and consequently multiple time references.  Also, LER/LSR =
TCs MUST be synchronized to the same master clock (which is the service pro=
vider Master clock), which implies that they need to choose one master to s=
ynchronize to."


3) Section 19.  "For transporting such peer delay measurement messages a si=
ngle-hop LSP SHOULD to be created between the two adjacent LSRs engaged in =
peer delay measurement to carry peer delay measurement messages. Other meth=
ods such as PTP transport over Ethernet MAY be used for transporting peer d=
elay measurement messages if the link between the two routers is Ethernet."


This new statement to handle peer-delay (which in earlier drafts did not ha=
ve a communication path listed), also allows a BC to be embedded in an LSR =
with a communication path between BC's as a single-hop LSP (mentioned March=
 22, 2012 in my feedback to draft -03, subject "[TICTOC] Updated 1588 over =
MPLS draf-03").

SD> When a single-hop LSP is created then I call the both ends of that
LSP, LERs and not LSRs.
Note that a router can act as LSR for some LSPs and LER for other LSPs.
The point is that we can't
Terminate a packet in the middle of an LSP (i.e., in an LSR). So BC functio=
nality can't exist in the middle Of a PTP LSP. So I think it is a matter of=
 terminology otherwise I agree that you could have BC in the core (not edge=
).=20

Architecture diagrams Figure 1 and Figure should be updated to reflect
the possibility of either BC or TC implementation.   Section 18.2 and
section 18.3 and section 21 should also be updated to reflect the possibili=
ty of either BC or TC.  I understand the RFC is intended to be generic and =
not targeted only at TC.



4) Section 20.  "When the MPLS network (provider network) serves multiple c=
ustomers, it is important to maintain and process each customers clock and =
Timing messages separately from other customers to
ensure there is no cross- customer effect.   For example if an LER BC is
synchronized to a specific grandmaster, belonging to customer A, then the L=
ER MUST use that BC clock only for customer A to ensure that customer A can=
not attack other customers by manipulating its time."

This seems much more applicable to the TC LSR and should be stated.
>From section 4 we see the TC uses the primary synchronization domain (that =
of the service provide) to correct PTP messages.

SD> I don't see how in a TC LSR, one customer timing can affect other
customer timings?
Since in a TC, we just update the Timestamp of a packet based on the Servic=
e provider Time.
May be I have not understood your point. Could you please clarify with an e=
xample.



5) Section 20.  "Timing messages (as opposed to regular customer data) SHOU=
LD not be encrypted or authenticated on an end-to-end basis."  I think ther=
e is a security draft in parallel being developed that may be relevant to t=
hat statement.

SD> I have updated the  text as following:

" Timing messages MAY be encrypted or authenticated, provided that the LERs=
/LSRs that are Timing capable/aware can authenticate/ decrypt the timing me=
ssages."




Regards,
Peter


-----Original Message-----
From: tictoc-bounces@ietf.org [mailto:tictoc-bounces@ietf.org] On Behalf Of=
 internet-drafts@ietf.org
Sent: February 23, 2013 2:23 AM
To: i-d-announce@ietf.org
Cc: tictoc@ietf.org
Subject: [TICTOC] I-D Action: draft-ietf-tictoc-1588overmpls-04.txt


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           : Transporting Timing messages over MPLS
Networks
	Author(s)       : Shahram Davari
                          Amit Oren
                          Manav Bhatia
                          Peter Roberts
                          Laurent Montini
	Filename        : draft-ietf-tictoc-1588overmpls-04.txt
	Pages           : 36
	Date            : 2013-02-22

Abstract:
   This document defines the method for transporting Timing messages
   such as PTP and NTP over an MPLS network.  The method allows for the
   easy identification of these PDUs at the port level to allow for port
   level processing of these PDUs in both LERs and LSRs.

   The basic idea is to transport Timing messages inside dedicated MPLS
   LSPs.  These LSPs only carry timing messages and possibly Control and
   Management packets, but they do not carry customer traffic.

   Two methods for transporting Timing messages over MPLS are defined.
   The first method is to transport Timing messages directly over the
   dedicated MPLS LSP via UDP/IP encapsulation, which is suitable for
   MPLS networks.  The second method is to transport Timing messages
   inside a PW via Ethernet encapsulation, which is suitable for both
   MPLS and MPLS-TP networks.


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

There's also a htmlized version available at:
http://tools.ietf.org/html/draft-ietf-tictoc-1588overmpls-04

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


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

_______________________________________________
TICTOC mailing list
TICTOC@ietf.org
https://www.ietf.org/mailman/listinfo/tictoc


_______________________________________________
TICTOC mailing list
TICTOC@ietf.org
https://www.ietf.org/mailman/listinfo/tictoc






From le@vitesse.com  Thu Jun  6 02:23:32 2013
Return-Path: <le@vitesse.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 36D3021F8EF7 for <tictoc@ietfa.amsl.com>; Thu,  6 Jun 2013 02:23:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id V3A6+Nw18wGH for <tictoc@ietfa.amsl.com>; Thu,  6 Jun 2013 02:23:27 -0700 (PDT)
Received: from na3sys009aog111.obsmtp.com (na3sys009aog111.obsmtp.com [74.125.149.205]) by ietfa.amsl.com (Postfix) with SMTP id 36A2321F9631 for <tictoc@ietf.org>; Thu,  6 Jun 2013 02:23:27 -0700 (PDT)
Received: from smtp.vitesse.com ([206.169.59.179]) (using TLSv1) by na3sys009aob111.postini.com ([74.125.148.12]) with SMTP ID DSNKUbBVCcXKWDszB+sfW28x5ievmwLP0W/d@postini.com; Thu, 06 Jun 2013 02:23:27 PDT
Received: from MBOX-CAM4.vitesse.com ([fe80::51ac:b24e:31d:d2c3]) by cash-cam3.vitesse.com ([::1]) with mapi id 14.02.0283.003; Thu, 6 Jun 2013 02:23:21 -0700
From: Lars Ellegaard <le@vitesse.com>
To: Stefano Ruffini <stefano.ruffini@ericsson.com>, "Meyer, Peter" <Peter.Meyer@microsemi.com>, Shahram Davari <davari@broadcom.com>, "tictoc@ietf.org" <tictoc@ietf.org>
Thread-Topic: [TICTOC] comments on draft-ietf-tictoc-1588overmpls-04.txt
Thread-Index: AQHOHrvIG9Qp4DAEq0WS7lIAjM8M8JkmuDRwgAE3KqCAAAYJEIAA94Ow
Date: Thu, 6 Jun 2013 09:23:20 +0000
Message-ID: <785DA01679B0C44F951747BE9CF66E6B017994ABA1@mbox-cam4.vitesse.com>
References: <20130223072233.32735.89371.idtracker@ietfa.amsl.com> <64683B4805156847B0ED373DAB3057CA015E930D@ottsrv0015.microsemi.net> <4A6CE49E6084B141B15C0713B8993F281BE28013@SJEXCHMB12.corp.ad.broadcom.com> <64683B4805156847B0ED373DAB3057CA01B19D5F@ottsrv0015.microsemi.net> <1B5CAFEB4D81154AA0F020783784C3150C775B@ESESSMB301.ericsson.se>
In-Reply-To: <1B5CAFEB4D81154AA0F020783784C3150C775B@ESESSMB301.ericsson.se>
Accept-Language: en-GB, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.9.40.66]
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: Re: [TICTOC] comments on draft-ietf-tictoc-1588overmpls-04.txt
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, 06 Jun 2013 09:23:32 -0000

Hi Shahram, Peter,

I noticed a point which I disagree on. As with Stefano's comment this refer=
s to both text proposals.
It regards the last sentence of the text block below:

"
Also, LER/LSR TCs MUST be
   synchronized to the same master clock (which is the service provider
   Master clock), which implies that they need to choose one master to
   which it will synchronize.
"

In general a TC need not be synchronized to a master. It may be so (syntoni=
zation) for increased accuracy but it is not a requirement per IEEE1588-200=
8. The TC may also be synchronized because the LER/LSR implementation inclu=
des OC-slave or BC functionality in addition to TC.

I suggest changing to

Also, LER/LSR TCs MAY be
   synchronized to the same master clock (which is the service provider
   Master clock), which implies that they need to choose one master to
   which it will synchronize.


Best regards,
Lars




-----Original Message-----
From: tictoc-bounces@ietf.org [mailto:tictoc-bounces@ietf.org] On Behalf Of=
 Stefano Ruffini
Sent: 05 June 2013 20:31
To: Meyer, Peter; Shahram Davari; tictoc@ietf.org
Subject: Re: [TICTOC] comments on draft-ietf-tictoc-1588overmpls-04.txt

Hi Shahram, Peter

There is one point I would disagree with (I am referring to Peter's latest =
proposal, but the same comment would apply to the previous text):
"
An MPLS domain may serve multiple customers.  In these cases the
   MPLS domain (maintained by a service provider) may provide timing
   services to multiple customers, each having their own Timing domain.
   If so, then the LER BCs and TCs may interact with multiple grandmasters,
   and consequently multiple time references.  Also, LER/LSR TCs MUST be
   synchronized to the same master clock (which is the service provider
   Master clock), which implies that they need to choose one master to
   which it will synchronize.
"

My understanding of this statement is that a LER would need to implement mu=
ltiple BC instances (with multiple clocks); this looks too complex.

The case of multiple operators, seems to me only practically applicable to =
figure 3 (LER TC).

I would then propose to remove the reference to LER BC in this statement .

Best regards
stefano


-----Original Message-----
From: tictoc-bounces@ietf.org [mailto:tictoc-bounces@ietf.org] On Behalf Of=
 Meyer, Peter
Sent: mercoled=EC 5 giugno 2013 20:01
To: Shahram Davari; tictoc@ietf.org
Subject: Re: [TICTOC] comments on draft-ietf-tictoc-1588overmpls-04.txt

Hi Shahram,

I hope in-line with my comments I have edited the text of draft -04.

I'm not sure how the formatting worked out (PC-based, line length, page len=
gth).

I modified sections 3, 4, 18, 19 & 20.

I include here both original and modified version so you can diff (most of =
the changes in 3 are due to line length / re-org, not actual text changes).

File attachment:
"draft-ietf-tictoc-1588overmpls-04-org.txt" (52 KB) "draft-ietf-tictoc-1588=
overmpls-04-pm.txt" (53 KB)


Regards,
Peter


-----Original Message-----
From: Shahram Davari [mailto:davari@broadcom.com]
Sent: June 4, 2013 7:40 PM
To: Meyer, Peter; tictoc@ietf.org
Subject: RE: [TICTOC] comments on draft-ietf-tictoc-1588overmpls-04.txt

Hi Peter,

Thanks for your god comments. Please see my responses inline. Please let me=
 know whether you are satisfied with my responses since I am updating the d=
raft in the next couple of days.

Thanks
Shahram

-----Original Message-----
From: tictoc-bounces@ietf.org [mailto:tictoc-bounces@ietf.org] On Behalf Of=
 Meyer, Peter
Sent: Monday, March 11, 2013 5:49 PM
To: tictoc@ietf.org
Subject: Re: [TICTOC] comments on draft-ietf-tictoc-1588overmpls-04.txt

Hi Shahram et al,

Some comments on draft -04.


1) Section 3.  "A generic method is defined in this document that does not =
require deep packet inspection at line rate, and can deterministically iden=
tify Timing messages.  The generic method is applicable to MPLS and MPLS-TP=
 networks."

May want to add that this would apply only to one-step TC (I imagine that i=
s the point of the correction at line rate).  A two-step TC would need to d=
o deep packet inspection as it uses sourcePortIdentity & sequenceId fields =
for Follow_up or Delay_Resp.

SD> For 2-step, all that is needed is for an interface to detect the
Timing message (based on top MPLS Label)  and record the Time along with so=
me information from the Timing packet and send them to CPU while forwarding=
 the Timing message as usual. Then the CPU based on the information receive=
d generates Follow-up message and injects it in to the LSP.  Therefore it i=
s the job of CPU to look at sourcePortIdentity & sequenceId fields not the =
Hardware.


2) Section 4.  "An MPLS domain can serve multiple customers.  This means th=
at the MPLS domain (maintained by a service provider) may provide timing se=
rvices to multiple customers, each having their own Timing domain.  Therefo=
re LER BCs need to interact with multiple grandmasters, and consequently mu=
ltiple time references."

This should be re-phrased.  It switches from an optional situation ("may pr=
ovide timing services") to mandatory situation ("LER BCs need to
interact").   Some words such as "in such a deployment scenario, ...."
and replace "can" with "may".   We have seen at ITU at least (with
participation from operators BT, FT, DT, CMCC, AT&T, Sprint, etc.) that thi=
s multiple operator domain case was not useful enough to be included in sta=
ndardization process for Telecom networks.

SD> I rephrased it as following:

" An MPLS domain can serve multiple customers.  This means that the
   MPLS domain (maintained by a service provider) may provide timing
   services to multiple customers, each having their own Timing domain.
   Therefore in such deployment scenarios, LER BCs may interact with multip=
le grandmasters, and consequently multiple time references.  Also, LER/LSR =
TCs MUST be synchronized to the same master clock (which is the service pro=
vider Master clock), which implies that they need to choose one master to s=
ynchronize to."


3) Section 19.  "For transporting such peer delay measurement messages a si=
ngle-hop LSP SHOULD to be created between the two adjacent LSRs engaged in =
peer delay measurement to carry peer delay measurement messages. Other meth=
ods such as PTP transport over Ethernet MAY be used for transporting peer d=
elay measurement messages if the link between the two routers is Ethernet."


This new statement to handle peer-delay (which in earlier drafts did not ha=
ve a communication path listed), also allows a BC to be embedded in an LSR =
with a communication path between BC's as a single-hop LSP (mentioned March=
 22, 2012 in my feedback to draft -03, subject "[TICTOC] Updated 1588 over =
MPLS draf-03").

SD> When a single-hop LSP is created then I call the both ends of that
LSP, LERs and not LSRs.
Note that a router can act as LSR for some LSPs and LER for other LSPs.
The point is that we can't
Terminate a packet in the middle of an LSP (i.e., in an LSR). So BC functio=
nality can't exist in the middle Of a PTP LSP. So I think it is a matter of=
 terminology otherwise I agree that you could have BC in the core (not edge=
).=20

Architecture diagrams Figure 1 and Figure should be updated to reflect
the possibility of either BC or TC implementation.   Section 18.2 and
section 18.3 and section 21 should also be updated to reflect the possibili=
ty of either BC or TC.  I understand the RFC is intended to be generic and =
not targeted only at TC.



4) Section 20.  "When the MPLS network (provider network) serves multiple c=
ustomers, it is important to maintain and process each customers clock and =
Timing messages separately from other customers to
ensure there is no cross- customer effect.   For example if an LER BC is
synchronized to a specific grandmaster, belonging to customer A, then the L=
ER MUST use that BC clock only for customer A to ensure that customer A can=
not attack other customers by manipulating its time."

This seems much more applicable to the TC LSR and should be stated.
>From section 4 we see the TC uses the primary synchronization domain (that =
of the service provide) to correct PTP messages.

SD> I don't see how in a TC LSR, one customer timing can affect other
customer timings?
Since in a TC, we just update the Timestamp of a packet based on the Servic=
e provider Time.
May be I have not understood your point. Could you please clarify with an e=
xample.



5) Section 20.  "Timing messages (as opposed to regular customer data) SHOU=
LD not be encrypted or authenticated on an end-to-end basis."  I think ther=
e is a security draft in parallel being developed that may be relevant to t=
hat statement.

SD> I have updated the  text as following:

" Timing messages MAY be encrypted or authenticated, provided that the LERs=
/LSRs that are Timing capable/aware can authenticate/ decrypt the timing me=
ssages."




Regards,
Peter


-----Original Message-----
From: tictoc-bounces@ietf.org [mailto:tictoc-bounces@ietf.org] On Behalf Of=
 internet-drafts@ietf.org
Sent: February 23, 2013 2:23 AM
To: i-d-announce@ietf.org
Cc: tictoc@ietf.org
Subject: [TICTOC] I-D Action: draft-ietf-tictoc-1588overmpls-04.txt


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           : Transporting Timing messages over MPLS
Networks
	Author(s)       : Shahram Davari
                          Amit Oren
                          Manav Bhatia
                          Peter Roberts
                          Laurent Montini
	Filename        : draft-ietf-tictoc-1588overmpls-04.txt
	Pages           : 36
	Date            : 2013-02-22

Abstract:
   This document defines the method for transporting Timing messages
   such as PTP and NTP over an MPLS network.  The method allows for the
   easy identification of these PDUs at the port level to allow for port
   level processing of these PDUs in both LERs and LSRs.

   The basic idea is to transport Timing messages inside dedicated MPLS
   LSPs.  These LSPs only carry timing messages and possibly Control and
   Management packets, but they do not carry customer traffic.

   Two methods for transporting Timing messages over MPLS are defined.
   The first method is to transport Timing messages directly over the
   dedicated MPLS LSP via UDP/IP encapsulation, which is suitable for
   MPLS networks.  The second method is to transport Timing messages
   inside a PW via Ethernet encapsulation, which is suitable for both
   MPLS and MPLS-TP networks.


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

There's also a htmlized version available at:
http://tools.ietf.org/html/draft-ietf-tictoc-1588overmpls-04

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


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

_______________________________________________
TICTOC mailing list
TICTOC@ietf.org
https://www.ietf.org/mailman/listinfo/tictoc


_______________________________________________
TICTOC mailing list
TICTOC@ietf.org
https://www.ietf.org/mailman/listinfo/tictoc



_______________________________________________
TICTOC mailing list
TICTOC@ietf.org
https://www.ietf.org/mailman/listinfo/tictoc

From davari@broadcom.com  Thu Jun  6 03:25:28 2013
Return-Path: <davari@broadcom.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 6CB0E21F992C for <tictoc@ietfa.amsl.com>; Thu,  6 Jun 2013 03:25:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id wHY0CJIAa-9j for <tictoc@ietfa.amsl.com>; Thu,  6 Jun 2013 03:25:24 -0700 (PDT)
Received: from mms3.broadcom.com (mms3.broadcom.com [216.31.210.19]) by ietfa.amsl.com (Postfix) with ESMTP id 378FB21F9926 for <tictoc@ietf.org>; Thu,  6 Jun 2013 03:25:24 -0700 (PDT)
Received: from [10.9.208.57] by mms3.broadcom.com with ESMTP (Broadcom SMTP Relay (Email Firewall v6.5)); Thu, 06 Jun 2013 03:16:19 -0700
X-Server-Uuid: B86B6450-0931-4310-942E-F00ED04CA7AF
Received: from SJEXCHCAS05.corp.ad.broadcom.com (10.16.203.12) by IRVEXCHCAS08.corp.ad.broadcom.com (10.9.208.57) with Microsoft SMTP Server (TLS) id 14.1.438.0; Thu, 6 Jun 2013 03:25:14 -0700
Received: from SJEXCHMB12.corp.ad.broadcom.com ( [fe80::bc15:c1e1:c29a:36f7]) by SJEXCHCAS05.corp.ad.broadcom.com ( [::1]) with mapi id 14.01.0438.000; Thu, 6 Jun 2013 03:25:14 -0700
From: "Shahram Davari" <davari@broadcom.com>
To: "Lars Ellegaard" <le@vitesse.com>
Thread-Topic: [TICTOC] comments on draft-ietf-tictoc-1588overmpls-04.txt
Thread-Index: AQHOHrvIG9Qp4DAEq0WS7lIAjM8M8JkmuDRwgAE3KqCAAAYJEIAA94OwgAAV4Qk=
Date: Thu, 6 Jun 2013 10:25:14 +0000
Message-ID: <7E018846-4BF7-42C2-9AE8-FA44C765E2F0@broadcom.com>
References: <20130223072233.32735.89371.idtracker@ietfa.amsl.com> <64683B4805156847B0ED373DAB3057CA015E930D@ottsrv0015.microsemi.net> <4A6CE49E6084B141B15C0713B8993F281BE28013@SJEXCHMB12.corp.ad.broadcom.com> <64683B4805156847B0ED373DAB3057CA01B19D5F@ottsrv0015.microsemi.net> <1B5CAFEB4D81154AA0F020783784C3150C775B@ESESSMB301.ericsson.se>, <785DA01679B0C44F951747BE9CF66E6B017994ABA1@mbox-cam4.vitesse.com>
In-Reply-To: <785DA01679B0C44F951747BE9CF66E6B017994ABA1@mbox-cam4.vitesse.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
MIME-Version: 1.0
X-WSS-ID: 7DAEBEF92L828724753-01-01
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: "tictoc@ietf.org" <tictoc@ietf.org>
Subject: Re: [TICTOC] comments on draft-ietf-tictoc-1588overmpls-04.txt
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, 06 Jun 2013 10:25:28 -0000

Hi Lars,

I have actually removed this paragraph completely for new version.

Regards,
Shahram


On Jun 6, 2013, at 2:23 AM, "Lars Ellegaard" <le@vitesse.com> wrote:

> Hi Shahram, Peter,
>=20
> I noticed a point which I disagree on. As with Stefano's comment this ref=
ers to both text proposals.
> It regards the last sentence of the text block below:
>=20
> "
> Also, LER/LSR TCs MUST be
>   synchronized to the same master clock (which is the service provider
>   Master clock), which implies that they need to choose one master to
>   which it will synchronize.
> "
>=20
> In general a TC need not be synchronized to a master. It may be so (synto=
nization) for increased accuracy but it is not a requirement per IEEE1588-2=
008. The TC may also be synchronized because the LER/LSR implementation inc=
ludes OC-slave or BC functionality in addition to TC.
>=20
> I suggest changing to
>=20
> Also, LER/LSR TCs MAY be
>   synchronized to the same master clock (which is the service provider
>   Master clock), which implies that they need to choose one master to
>   which it will synchronize.
>=20
>=20
> Best regards,
> Lars
>=20
>=20
>=20
>=20
> -----Original Message-----
> From: tictoc-bounces@ietf.org [mailto:tictoc-bounces@ietf.org] On Behalf =
Of Stefano Ruffini
> Sent: 05 June 2013 20:31
> To: Meyer, Peter; Shahram Davari; tictoc@ietf.org
> Subject: Re: [TICTOC] comments on draft-ietf-tictoc-1588overmpls-04.txt
>=20
> Hi Shahram, Peter
>=20
> There is one point I would disagree with (I am referring to Peter's lates=
t proposal, but the same comment would apply to the previous text):
> "
> An MPLS domain may serve multiple customers.  In these cases the
>   MPLS domain (maintained by a service provider) may provide timing
>   services to multiple customers, each having their own Timing domain.
>   If so, then the LER BCs and TCs may interact with multiple grandmasters=
,
>   and consequently multiple time references.  Also, LER/LSR TCs MUST be
>   synchronized to the same master clock (which is the service provider
>   Master clock), which implies that they need to choose one master to
>   which it will synchronize.
> "
>=20
> My understanding of this statement is that a LER would need to implement =
multiple BC instances (with multiple clocks); this looks too complex.
>=20
> The case of multiple operators, seems to me only practically applicable t=
o figure 3 (LER TC).
>=20
> I would then propose to remove the reference to LER BC in this statement =
.
>=20
> Best regards
> stefano
>=20
>=20
> -----Original Message-----
> From: tictoc-bounces@ietf.org [mailto:tictoc-bounces@ietf.org] On Behalf =
Of Meyer, Peter
> Sent: mercoled=EC 5 giugno 2013 20:01
> To: Shahram Davari; tictoc@ietf.org
> Subject: Re: [TICTOC] comments on draft-ietf-tictoc-1588overmpls-04.txt
>=20
> Hi Shahram,
>=20
> I hope in-line with my comments I have edited the text of draft -04.
>=20
> I'm not sure how the formatting worked out (PC-based, line length, page l=
ength).
>=20
> I modified sections 3, 4, 18, 19 & 20.
>=20
> I include here both original and modified version so you can diff (most o=
f the changes in 3 are due to line length / re-org, not actual text changes=
).
>=20
> File attachment:
> "draft-ietf-tictoc-1588overmpls-04-org.txt" (52 KB) "draft-ietf-tictoc-15=
88overmpls-04-pm.txt" (53 KB)
>=20
>=20
> Regards,
> Peter
>=20
>=20
> -----Original Message-----
> From: Shahram Davari [mailto:davari@broadcom.com]
> Sent: June 4, 2013 7:40 PM
> To: Meyer, Peter; tictoc@ietf.org
> Subject: RE: [TICTOC] comments on draft-ietf-tictoc-1588overmpls-04.txt
>=20
> Hi Peter,
>=20
> Thanks for your god comments. Please see my responses inline. Please let =
me know whether you are satisfied with my responses since I am updating the=
 draft in the next couple of days.
>=20
> Thanks
> Shahram
>=20
> -----Original Message-----
> From: tictoc-bounces@ietf.org [mailto:tictoc-bounces@ietf.org] On Behalf =
Of Meyer, Peter
> Sent: Monday, March 11, 2013 5:49 PM
> To: tictoc@ietf.org
> Subject: Re: [TICTOC] comments on draft-ietf-tictoc-1588overmpls-04.txt
>=20
> Hi Shahram et al,
>=20
> Some comments on draft -04.
>=20
>=20
> 1) Section 3.  "A generic method is defined in this document that does no=
t require deep packet inspection at line rate, and can deterministically id=
entify Timing messages.  The generic method is applicable to MPLS and MPLS-=
TP networks."
>=20
> May want to add that this would apply only to one-step TC (I imagine that=
 is the point of the correction at line rate).  A two-step TC would need to=
 do deep packet inspection as it uses sourcePortIdentity & sequenceId field=
s for Follow_up or Delay_Resp.
>=20
> SD> For 2-step, all that is needed is for an interface to detect the
> Timing message (based on top MPLS Label)  and record the Time along with =
some information from the Timing packet and send them to CPU while forwardi=
ng the Timing message as usual. Then the CPU based on the information recei=
ved generates Follow-up message and injects it in to the LSP.  Therefore it=
 is the job of CPU to look at sourcePortIdentity & sequenceId fields not th=
e Hardware.
>=20
>=20
> 2) Section 4.  "An MPLS domain can serve multiple customers.  This means =
that the MPLS domain (maintained by a service provider) may provide timing =
services to multiple customers, each having their own Timing domain.  There=
fore LER BCs need to interact with multiple grandmasters, and consequently =
multiple time references."
>=20
> This should be re-phrased.  It switches from an optional situation ("may =
provide timing services") to mandatory situation ("LER BCs need to
> interact").   Some words such as "in such a deployment scenario, ...."
> and replace "can" with "may".   We have seen at ITU at least (with
> participation from operators BT, FT, DT, CMCC, AT&T, Sprint, etc.) that t=
his multiple operator domain case was not useful enough to be included in s=
tandardization process for Telecom networks.
>=20
> SD> I rephrased it as following:
>=20
> " An MPLS domain can serve multiple customers.  This means that the
>   MPLS domain (maintained by a service provider) may provide timing
>   services to multiple customers, each having their own Timing domain.
>   Therefore in such deployment scenarios, LER BCs may interact with multi=
ple grandmasters, and consequently multiple time references.  Also, LER/LSR=
 TCs MUST be synchronized to the same master clock (which is the service pr=
ovider Master clock), which implies that they need to choose one master to =
synchronize to."
>=20
>=20
> 3) Section 19.  "For transporting such peer delay measurement messages a =
single-hop LSP SHOULD to be created between the two adjacent LSRs engaged i=
n peer delay measurement to carry peer delay measurement messages. Other me=
thods such as PTP transport over Ethernet MAY be used for transporting peer=
 delay measurement messages if the link between the two routers is Ethernet=
."
>=20
>=20
> This new statement to handle peer-delay (which in earlier drafts did not =
have a communication path listed), also allows a BC to be embedded in an LS=
R with a communication path between BC's as a single-hop LSP (mentioned Mar=
ch 22, 2012 in my feedback to draft -03, subject "[TICTOC] Updated 1588 ove=
r MPLS draf-03").
>=20
> SD> When a single-hop LSP is created then I call the both ends of that
> LSP, LERs and not LSRs.
> Note that a router can act as LSR for some LSPs and LER for other LSPs.
> The point is that we can't
> Terminate a packet in the middle of an LSP (i.e., in an LSR). So BC funct=
ionality can't exist in the middle Of a PTP LSP. So I think it is a matter =
of terminology otherwise I agree that you could have BC in the core (not ed=
ge).=20
>=20
> Architecture diagrams Figure 1 and Figure should be updated to reflect
> the possibility of either BC or TC implementation.   Section 18.2 and
> section 18.3 and section 21 should also be updated to reflect the possibi=
lity of either BC or TC.  I understand the RFC is intended to be generic an=
d not targeted only at TC.
>=20
>=20
>=20
> 4) Section 20.  "When the MPLS network (provider network) serves multiple=
 customers, it is important to maintain and process each customers clock an=
d Timing messages separately from other customers to
> ensure there is no cross- customer effect.   For example if an LER BC is
> synchronized to a specific grandmaster, belonging to customer A, then the=
 LER MUST use that BC clock only for customer A to ensure that customer A c=
annot attack other customers by manipulating its time."
>=20
> This seems much more applicable to the TC LSR and should be stated.
> From section 4 we see the TC uses the primary synchronization domain (tha=
t of the service provide) to correct PTP messages.
>=20
> SD> I don't see how in a TC LSR, one customer timing can affect other
> customer timings?
> Since in a TC, we just update the Timestamp of a packet based on the Serv=
ice provider Time.
> May be I have not understood your point. Could you please clarify with an=
 example.
>=20
>=20
>=20
> 5) Section 20.  "Timing messages (as opposed to regular customer data) SH=
OULD not be encrypted or authenticated on an end-to-end basis."  I think th=
ere is a security draft in parallel being developed that may be relevant to=
 that statement.
>=20
> SD> I have updated the  text as following:
>=20
> " Timing messages MAY be encrypted or authenticated, provided that the LE=
Rs/LSRs that are Timing capable/aware can authenticate/ decrypt the timing =
messages."
>=20
>=20
>=20
>=20
> Regards,
> Peter
>=20
>=20
> -----Original Message-----
> From: tictoc-bounces@ietf.org [mailto:tictoc-bounces@ietf.org] On Behalf =
Of internet-drafts@ietf.org
> Sent: February 23, 2013 2:23 AM
> To: i-d-announce@ietf.org
> Cc: tictoc@ietf.org
> Subject: [TICTOC] I-D Action: draft-ietf-tictoc-1588overmpls-04.txt
>=20
>=20
> A New Internet-Draft is available from the on-line Internet-Drafts direct=
ories.
> This draft is a work item of the Timing over IP Connection and Transfer o=
f Clock Working Group of the IETF.
>=20
>    Title           : Transporting Timing messages over MPLS
> Networks
>    Author(s)       : Shahram Davari
>                          Amit Oren
>                          Manav Bhatia
>                          Peter Roberts
>                          Laurent Montini
>    Filename        : draft-ietf-tictoc-1588overmpls-04.txt
>    Pages           : 36
>    Date            : 2013-02-22
>=20
> Abstract:
>   This document defines the method for transporting Timing messages
>   such as PTP and NTP over an MPLS network.  The method allows for the
>   easy identification of these PDUs at the port level to allow for port
>   level processing of these PDUs in both LERs and LSRs.
>=20
>   The basic idea is to transport Timing messages inside dedicated MPLS
>   LSPs.  These LSPs only carry timing messages and possibly Control and
>   Management packets, but they do not carry customer traffic.
>=20
>   Two methods for transporting Timing messages over MPLS are defined.
>   The first method is to transport Timing messages directly over the
>   dedicated MPLS LSP via UDP/IP encapsulation, which is suitable for
>   MPLS networks.  The second method is to transport Timing messages
>   inside a PW via Ethernet encapsulation, which is suitable for both
>   MPLS and MPLS-TP networks.
>=20
>=20
> The IETF datatracker status page for this draft is:
> https://datatracker.ietf.org/doc/draft-ietf-tictoc-1588overmpls
>=20
> There's also a htmlized version available at:
> http://tools.ietf.org/html/draft-ietf-tictoc-1588overmpls-04
>=20
> A diff from the previous version is available at:
> http://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-tictoc-1588overmpls-04
>=20
>=20
> Internet-Drafts are also available by anonymous FTP at:
> ftp://ftp.ietf.org/internet-drafts/
>=20
> _______________________________________________
> TICTOC mailing list
> TICTOC@ietf.org
> https://www.ietf.org/mailman/listinfo/tictoc
>=20
>=20
> _______________________________________________
> TICTOC mailing list
> TICTOC@ietf.org
> https://www.ietf.org/mailman/listinfo/tictoc
>=20
>=20
>=20
> _______________________________________________
> TICTOC mailing list
> TICTOC@ietf.org
> https://www.ietf.org/mailman/listinfo/tictoc
>=20


From le@vitesse.com  Thu Jun  6 03:39:56 2013
Return-Path: <le@vitesse.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 A3E8321F9950 for <tictoc@ietfa.amsl.com>; Thu,  6 Jun 2013 03:39:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id cTr+v15tR+o8 for <tictoc@ietfa.amsl.com>; Thu,  6 Jun 2013 03:39:51 -0700 (PDT)
Received: from na3sys009aog128.obsmtp.com (na3sys009aog128.obsmtp.com [74.125.149.141]) by ietfa.amsl.com (Postfix) with SMTP id 9F19E21F994D for <tictoc@ietf.org>; Thu,  6 Jun 2013 03:39:51 -0700 (PDT)
Received: from smtp.vitesse.com ([206.169.59.179]) (using TLSv1) by na3sys009aob128.postini.com ([74.125.148.12]) with SMTP ID DSNKUbBm9SlsOrEKHEwbvRGrHI0YjBppKXN0@postini.com; Thu, 06 Jun 2013 03:39:51 PDT
Received: from MBOX-CAM4.vitesse.com ([fe80::51ac:b24e:31d:d2c3]) by cash-cam3.vitesse.com ([::1]) with mapi id 14.02.0283.003; Thu, 6 Jun 2013 03:39:49 -0700
From: Lars Ellegaard <le@vitesse.com>
To: Shahram Davari <davari@broadcom.com>
Thread-Topic: [TICTOC] comments on draft-ietf-tictoc-1588overmpls-04.txt
Thread-Index: AQHOHrvIG9Qp4DAEq0WS7lIAjM8M8JkmuDRwgAE3KqCAAAYJEIAA94OwgAAV4QmAAAP78A==
Date: Thu, 6 Jun 2013 10:39:48 +0000
Message-ID: <785DA01679B0C44F951747BE9CF66E6B017994AC2A@mbox-cam4.vitesse.com>
References: <20130223072233.32735.89371.idtracker@ietfa.amsl.com> <64683B4805156847B0ED373DAB3057CA015E930D@ottsrv0015.microsemi.net> <4A6CE49E6084B141B15C0713B8993F281BE28013@SJEXCHMB12.corp.ad.broadcom.com> <64683B4805156847B0ED373DAB3057CA01B19D5F@ottsrv0015.microsemi.net> <1B5CAFEB4D81154AA0F020783784C3150C775B@ESESSMB301.ericsson.se>, <785DA01679B0C44F951747BE9CF66E6B017994ABA1@mbox-cam4.vitesse.com> <7E018846-4BF7-42C2-9AE8-FA44C765E2F0@broadcom.com>
In-Reply-To: <7E018846-4BF7-42C2-9AE8-FA44C765E2F0@broadcom.com>
Accept-Language: en-GB, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.9.40.66]
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "tictoc@ietf.org" <tictoc@ietf.org>
Subject: Re: [TICTOC] comments on draft-ietf-tictoc-1588overmpls-04.txt
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, 06 Jun 2013 10:39:56 -0000

OK, thx

-----Original Message-----
From: Shahram Davari [mailto:davari@broadcom.com]=20
Sent: 06 June 2013 12:25
To: Lars Ellegaard
Cc: Stefano Ruffini; Meyer, Peter; tictoc@ietf.org
Subject: Re: [TICTOC] comments on draft-ietf-tictoc-1588overmpls-04.txt

Hi Lars,

I have actually removed this paragraph completely for new version.

Regards,
Shahram


On Jun 6, 2013, at 2:23 AM, "Lars Ellegaard" <le@vitesse.com> wrote:

> Hi Shahram, Peter,
>=20
> I noticed a point which I disagree on. As with Stefano's comment this ref=
ers to both text proposals.
> It regards the last sentence of the text block below:
>=20
> "
> Also, LER/LSR TCs MUST be
>   synchronized to the same master clock (which is the service provider
>   Master clock), which implies that they need to choose one master to
>   which it will synchronize.
> "
>=20
> In general a TC need not be synchronized to a master. It may be so (synto=
nization) for increased accuracy but it is not a requirement per IEEE1588-2=
008. The TC may also be synchronized because the LER/LSR implementation inc=
ludes OC-slave or BC functionality in addition to TC.
>=20
> I suggest changing to
>=20
> Also, LER/LSR TCs MAY be
>   synchronized to the same master clock (which is the service provider
>   Master clock), which implies that they need to choose one master to
>   which it will synchronize.
>=20
>=20
> Best regards,
> Lars
>=20
>=20
>=20
>=20
> -----Original Message-----
> From: tictoc-bounces@ietf.org [mailto:tictoc-bounces@ietf.org] On Behalf =
Of Stefano Ruffini
> Sent: 05 June 2013 20:31
> To: Meyer, Peter; Shahram Davari; tictoc@ietf.org
> Subject: Re: [TICTOC] comments on draft-ietf-tictoc-1588overmpls-04.txt
>=20
> Hi Shahram, Peter
>=20
> There is one point I would disagree with (I am referring to Peter's lates=
t proposal, but the same comment would apply to the previous text):
> "
> An MPLS domain may serve multiple customers.  In these cases the
>   MPLS domain (maintained by a service provider) may provide timing
>   services to multiple customers, each having their own Timing domain.
>   If so, then the LER BCs and TCs may interact with multiple grandmasters=
,
>   and consequently multiple time references.  Also, LER/LSR TCs MUST be
>   synchronized to the same master clock (which is the service provider
>   Master clock), which implies that they need to choose one master to
>   which it will synchronize.
> "
>=20
> My understanding of this statement is that a LER would need to implement =
multiple BC instances (with multiple clocks); this looks too complex.
>=20
> The case of multiple operators, seems to me only practically applicable t=
o figure 3 (LER TC).
>=20
> I would then propose to remove the reference to LER BC in this statement =
.
>=20
> Best regards
> stefano
>=20
>=20
> -----Original Message-----
> From: tictoc-bounces@ietf.org [mailto:tictoc-bounces@ietf.org] On Behalf =
Of Meyer, Peter
> Sent: mercoled=EC 5 giugno 2013 20:01
> To: Shahram Davari; tictoc@ietf.org
> Subject: Re: [TICTOC] comments on draft-ietf-tictoc-1588overmpls-04.txt
>=20
> Hi Shahram,
>=20
> I hope in-line with my comments I have edited the text of draft -04.
>=20
> I'm not sure how the formatting worked out (PC-based, line length, page l=
ength).
>=20
> I modified sections 3, 4, 18, 19 & 20.
>=20
> I include here both original and modified version so you can diff (most o=
f the changes in 3 are due to line length / re-org, not actual text changes=
).
>=20
> File attachment:
> "draft-ietf-tictoc-1588overmpls-04-org.txt" (52 KB) "draft-ietf-tictoc-15=
88overmpls-04-pm.txt" (53 KB)
>=20
>=20
> Regards,
> Peter
>=20
>=20
> -----Original Message-----
> From: Shahram Davari [mailto:davari@broadcom.com]
> Sent: June 4, 2013 7:40 PM
> To: Meyer, Peter; tictoc@ietf.org
> Subject: RE: [TICTOC] comments on draft-ietf-tictoc-1588overmpls-04.txt
>=20
> Hi Peter,
>=20
> Thanks for your god comments. Please see my responses inline. Please let =
me know whether you are satisfied with my responses since I am updating the=
 draft in the next couple of days.
>=20
> Thanks
> Shahram
>=20
> -----Original Message-----
> From: tictoc-bounces@ietf.org [mailto:tictoc-bounces@ietf.org] On Behalf =
Of Meyer, Peter
> Sent: Monday, March 11, 2013 5:49 PM
> To: tictoc@ietf.org
> Subject: Re: [TICTOC] comments on draft-ietf-tictoc-1588overmpls-04.txt
>=20
> Hi Shahram et al,
>=20
> Some comments on draft -04.
>=20
>=20
> 1) Section 3.  "A generic method is defined in this document that does no=
t require deep packet inspection at line rate, and can deterministically id=
entify Timing messages.  The generic method is applicable to MPLS and MPLS-=
TP networks."
>=20
> May want to add that this would apply only to one-step TC (I imagine that=
 is the point of the correction at line rate).  A two-step TC would need to=
 do deep packet inspection as it uses sourcePortIdentity & sequenceId field=
s for Follow_up or Delay_Resp.
>=20
> SD> For 2-step, all that is needed is for an interface to detect the
> Timing message (based on top MPLS Label)  and record the Time along with =
some information from the Timing packet and send them to CPU while forwardi=
ng the Timing message as usual. Then the CPU based on the information recei=
ved generates Follow-up message and injects it in to the LSP.  Therefore it=
 is the job of CPU to look at sourcePortIdentity & sequenceId fields not th=
e Hardware.
>=20
>=20
> 2) Section 4.  "An MPLS domain can serve multiple customers.  This means =
that the MPLS domain (maintained by a service provider) may provide timing =
services to multiple customers, each having their own Timing domain.  There=
fore LER BCs need to interact with multiple grandmasters, and consequently =
multiple time references."
>=20
> This should be re-phrased.  It switches from an optional situation ("may =
provide timing services") to mandatory situation ("LER BCs need to
> interact").   Some words such as "in such a deployment scenario, ...."
> and replace "can" with "may".   We have seen at ITU at least (with
> participation from operators BT, FT, DT, CMCC, AT&T, Sprint, etc.) that t=
his multiple operator domain case was not useful enough to be included in s=
tandardization process for Telecom networks.
>=20
> SD> I rephrased it as following:
>=20
> " An MPLS domain can serve multiple customers.  This means that the
>   MPLS domain (maintained by a service provider) may provide timing
>   services to multiple customers, each having their own Timing domain.
>   Therefore in such deployment scenarios, LER BCs may interact with multi=
ple grandmasters, and consequently multiple time references.  Also, LER/LSR=
 TCs MUST be synchronized to the same master clock (which is the service pr=
ovider Master clock), which implies that they need to choose one master to =
synchronize to."
>=20
>=20
> 3) Section 19.  "For transporting such peer delay measurement messages a =
single-hop LSP SHOULD to be created between the two adjacent LSRs engaged i=
n peer delay measurement to carry peer delay measurement messages. Other me=
thods such as PTP transport over Ethernet MAY be used for transporting peer=
 delay measurement messages if the link between the two routers is Ethernet=
."
>=20
>=20
> This new statement to handle peer-delay (which in earlier drafts did not =
have a communication path listed), also allows a BC to be embedded in an LS=
R with a communication path between BC's as a single-hop LSP (mentioned Mar=
ch 22, 2012 in my feedback to draft -03, subject "[TICTOC] Updated 1588 ove=
r MPLS draf-03").
>=20
> SD> When a single-hop LSP is created then I call the both ends of that
> LSP, LERs and not LSRs.
> Note that a router can act as LSR for some LSPs and LER for other LSPs.
> The point is that we can't
> Terminate a packet in the middle of an LSP (i.e., in an LSR). So BC funct=
ionality can't exist in the middle Of a PTP LSP. So I think it is a matter =
of terminology otherwise I agree that you could have BC in the core (not ed=
ge).=20
>=20
> Architecture diagrams Figure 1 and Figure should be updated to reflect
> the possibility of either BC or TC implementation.   Section 18.2 and
> section 18.3 and section 21 should also be updated to reflect the possibi=
lity of either BC or TC.  I understand the RFC is intended to be generic an=
d not targeted only at TC.
>=20
>=20
>=20
> 4) Section 20.  "When the MPLS network (provider network) serves multiple=
 customers, it is important to maintain and process each customers clock an=
d Timing messages separately from other customers to
> ensure there is no cross- customer effect.   For example if an LER BC is
> synchronized to a specific grandmaster, belonging to customer A, then the=
 LER MUST use that BC clock only for customer A to ensure that customer A c=
annot attack other customers by manipulating its time."
>=20
> This seems much more applicable to the TC LSR and should be stated.
> From section 4 we see the TC uses the primary synchronization domain (tha=
t of the service provide) to correct PTP messages.
>=20
> SD> I don't see how in a TC LSR, one customer timing can affect other
> customer timings?
> Since in a TC, we just update the Timestamp of a packet based on the Serv=
ice provider Time.
> May be I have not understood your point. Could you please clarify with an=
 example.
>=20
>=20
>=20
> 5) Section 20.  "Timing messages (as opposed to regular customer data) SH=
OULD not be encrypted or authenticated on an end-to-end basis."  I think th=
ere is a security draft in parallel being developed that may be relevant to=
 that statement.
>=20
> SD> I have updated the  text as following:
>=20
> " Timing messages MAY be encrypted or authenticated, provided that the LE=
Rs/LSRs that are Timing capable/aware can authenticate/ decrypt the timing =
messages."
>=20
>=20
>=20
>=20
> Regards,
> Peter
>=20
>=20
> -----Original Message-----
> From: tictoc-bounces@ietf.org [mailto:tictoc-bounces@ietf.org] On Behalf =
Of internet-drafts@ietf.org
> Sent: February 23, 2013 2:23 AM
> To: i-d-announce@ietf.org
> Cc: tictoc@ietf.org
> Subject: [TICTOC] I-D Action: draft-ietf-tictoc-1588overmpls-04.txt
>=20
>=20
> A New Internet-Draft is available from the on-line Internet-Drafts direct=
ories.
> This draft is a work item of the Timing over IP Connection and Transfer o=
f Clock Working Group of the IETF.
>=20
>    Title           : Transporting Timing messages over MPLS
> Networks
>    Author(s)       : Shahram Davari
>                          Amit Oren
>                          Manav Bhatia
>                          Peter Roberts
>                          Laurent Montini
>    Filename        : draft-ietf-tictoc-1588overmpls-04.txt
>    Pages           : 36
>    Date            : 2013-02-22
>=20
> Abstract:
>   This document defines the method for transporting Timing messages
>   such as PTP and NTP over an MPLS network.  The method allows for the
>   easy identification of these PDUs at the port level to allow for port
>   level processing of these PDUs in both LERs and LSRs.
>=20
>   The basic idea is to transport Timing messages inside dedicated MPLS
>   LSPs.  These LSPs only carry timing messages and possibly Control and
>   Management packets, but they do not carry customer traffic.
>=20
>   Two methods for transporting Timing messages over MPLS are defined.
>   The first method is to transport Timing messages directly over the
>   dedicated MPLS LSP via UDP/IP encapsulation, which is suitable for
>   MPLS networks.  The second method is to transport Timing messages
>   inside a PW via Ethernet encapsulation, which is suitable for both
>   MPLS and MPLS-TP networks.
>=20
>=20
> The IETF datatracker status page for this draft is:
> https://datatracker.ietf.org/doc/draft-ietf-tictoc-1588overmpls
>=20
> There's also a htmlized version available at:
> http://tools.ietf.org/html/draft-ietf-tictoc-1588overmpls-04
>=20
> A diff from the previous version is available at:
> http://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-tictoc-1588overmpls-04
>=20
>=20
> Internet-Drafts are also available by anonymous FTP at:
> ftp://ftp.ietf.org/internet-drafts/
>=20
> _______________________________________________
> TICTOC mailing list
> TICTOC@ietf.org
> https://www.ietf.org/mailman/listinfo/tictoc
>=20
>=20
> _______________________________________________
> TICTOC mailing list
> TICTOC@ietf.org
> https://www.ietf.org/mailman/listinfo/tictoc
>=20
>=20
>=20
> _______________________________________________
> TICTOC mailing list
> TICTOC@ietf.org
> https://www.ietf.org/mailman/listinfo/tictoc
>=20


From prvs=486962002d=gregory.mirsky@ericsson.com  Thu Jun  6 11:23:22 2013
Return-Path: <prvs=486962002d=gregory.mirsky@ericsson.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 A492E21F9954 for <tictoc@ietfa.amsl.com>; Thu,  6 Jun 2013 11:23:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.598
X-Spam-Level: 
X-Spam-Status: No, score=-2.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=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 0gCQxdc+DXj6 for <tictoc@ietfa.amsl.com>; Thu,  6 Jun 2013 11:23:16 -0700 (PDT)
Received: from usevmg21.ericsson.net (usevmg21.ericsson.net [198.24.6.65]) by ietfa.amsl.com (Postfix) with ESMTP id ED5E021F995A for <tictoc@ietf.org>; Thu,  6 Jun 2013 11:23:15 -0700 (PDT)
X-AuditID: c6180641-b7f0e6d0000015f1-4c-51b0d3925fa5
Received: from EUSAAHC005.ericsson.se (Unknown_Domain [147.117.188.87]) by usevmg21.ericsson.net (Symantec Mail Security) with SMTP id F3.8B.05617.293D0B15; Thu,  6 Jun 2013 20:23:14 +0200 (CEST)
Received: from EUSAAMB103.ericsson.se ([147.117.188.120]) by EUSAAHC005.ericsson.se ([147.117.188.87]) with mapi id 14.02.0328.009; Thu, 6 Jun 2013 14:23:14 -0400
From: Gregory Mirsky <gregory.mirsky@ericsson.com>
To: Shahram Davari <davari@broadcom.com>, "amito@broadcom.com" <amito@broadcom.com>, "Bhatia, Manav (Manav)" <manav.bhatia@alcatel-lucent.com>, "Roberts, Peter (Peter)" <peter.roberts@alcatel-lucent.com>, "lmontini@cisco.com" <lmontini@cisco.com>, "tictoc@ietf.org" <tictoc@ietf.org>
Thread-Topic: NTP in draft-ietf-tictoc-1588overmpls-04
Thread-Index: Ac5i4ubOrT57JHkXTgC9GUzpraB4EA==
Date: Thu, 6 Jun 2013 18:23:12 +0000
Message-ID: <7347100B5761DC41A166AC17F22DF1121B4A0754@eusaamb103.ericsson.se>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [147.117.188.134]
Content-Type: multipart/alternative; boundary="_000_7347100B5761DC41A166AC17F22DF1121B4A0754eusaamb103erics_"
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFnrKLMWRmVeSWpSXmKPExsUyuXRPuO6kyxsCDaa9NbfYcznDYn2vp8Xd zy+ZLObcu8dqcXvTU1aLv8097A5sHq3P9rJ6zLp/ls1jyu+NrB5LlvxkCmCJ4rZJSiwpC85M z9O3S+DOWPr4BHvBT9GKnl/HWRoYLwl1MXJySAiYSEyZuJQVwhaTuHBvPVsXIxeHkMBRRok/ Ty6zQjjLGCVervwGVsUmYCTxYmMPO0hCRGAxk8TxaW9YQBLCAoYSPY0z2EBsEQEziYfPNrNA 2HoS9x90MILYLAIqEtsWTAEbxCvgK7Gu4RAziM0ItPr7qTVMIDazgLjErSfzmSBOEpBYsuc8 M4QtKvHy8T+oU5UlljzZzwJRny9xqPs+E8RMQYmTM5+wTGAUmoVk1CwkZbOQlEHEdSQW7P7E BmFrSyxb+JoZxj5z4DETsvgCRvZVjBylxalluelGhpsYgbF0TILNcQfjgk+WhxilOViUxHl1 eBcHCgmkJ5akZqemFqQWxReV5qQWH2Jk4uAEEVxSDYzeGlf1VcUmVk0o3S3CLs4/m+lN3Ok4 iysZKu7bTjXc5f4yy63u6TTvyPluJg/slMQ3NKup5jHnSBdn8nytvR6e/qLTSsxNoGnzZvUV u2/mZVnJbFBWVMuQYQswe/Zh+zKPmDW5r/dvWmM3NdJw/+vr+abaG8x7tB7Gp27f8uebwoHC HM4ri5RYijMSDbWYi4oTAWJb/nx4AgAA
Subject: [TICTOC] NTP in draft-ietf-tictoc-1588overmpls-04
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, 06 Jun 2013 18:23:22 -0000

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

Dear Authors, et al.,
The draft-ietf-tictoc-1588overmpls-04 is currently titled as "Transporting =
Timing messages over MPLS Networks" and states that both timing synchroniza=
tion protocols, PTP and NTP, require use of PTP LSP to transport timing mes=
sages over an MPLS network. After reading RFC 5905 I am not sure that PTP L=
SP, with its constraints and additional complexity, is required to transpor=
t NTPv4 messages over an MPLS network. And first paragraph in Section 3 Pro=
blem Statement of draft-ietf-tictoc-1588overmpls-04 explains motivation for=
 the PTP as
"There is a need to transport Timing messages over MPLS networks while supp=
orting the Transparent Clock (TC), Boundary Clock (BC) and Ordinary Clock (=
OC) functionality in the LER and LSRs in the MPLS network."
 but says nothing of a kind about NTP.

        Regards,
                Greg


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

<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
<meta name=3D"Generator" content=3D"Microsoft Exchange Server">
<!-- converted from rtf -->
<style><!-- .EmailQuote { margin-left: 1pt; padding-left: 4pt; border-left:=
 #800000 2px solid; } --></style>
</head>
<body>
<font face=3D"Arial" size=3D"2"><span style=3D"font-size:10pt;">
<div>Dear Authors, et al.,</div>
<div>The draft-ietf-tictoc-1588overmpls-04 is currently titled as &quot;Tra=
nsporting Timing messages over MPLS Networks&quot; and states that both tim=
ing synchronization protocols, PTP and NTP, require use of PTP LSP to trans=
port timing messages over an MPLS network.
After reading RFC 5905 I am not sure that PTP LSP, with its constraints and=
 additional complexity, is required to transport NTPv4 messages over an MPL=
S network. And first paragraph in Section 3 Problem Statement of draft-ietf=
-tictoc-1588overmpls-04 explains
motivation for the PTP as </div>
<div>&quot;There is a need to transport Timing messages over MPLS networks =
while supporting the Transparent Clock (TC), Boundary Clock (BC) and Ordina=
ry Clock (OC) functionality in the LER and LSRs in the MPLS network.&quot;<=
/div>
<div> but says nothing of a kind about NTP.</div>
<div>&nbsp;</div>
<div>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Regards,</div>
<div>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp; Greg</div>
<div>&nbsp;</div>
</span></font>
</body>
</html>

--_000_7347100B5761DC41A166AC17F22DF1121B4A0754eusaamb103erics_--

From davari@broadcom.com  Thu Jun  6 11:44:54 2013
Return-Path: <davari@broadcom.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 A762F21E80AD for <tictoc@ietfa.amsl.com>; Thu,  6 Jun 2013 11:44:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[AWL=-0.001, BAYES_00=-2.599, 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 UGlvJxgZLDcQ for <tictoc@ietfa.amsl.com>; Thu,  6 Jun 2013 11:44:49 -0700 (PDT)
Received: from mms3.broadcom.com (mms3.broadcom.com [216.31.210.19]) by ietfa.amsl.com (Postfix) with ESMTP id 874F921E80A4 for <tictoc@ietf.org>; Thu,  6 Jun 2013 11:44:49 -0700 (PDT)
Received: from [10.9.208.53] by mms3.broadcom.com with ESMTP (Broadcom SMTP Relay (Email Firewall v6.5)); Thu, 06 Jun 2013 11:35:47 -0700
X-Server-Uuid: B86B6450-0931-4310-942E-F00ED04CA7AF
Received: from SJEXCHCAS06.corp.ad.broadcom.com (10.16.203.14) by IRVEXCHCAS06.corp.ad.broadcom.com (10.9.208.53) with Microsoft SMTP Server (TLS) id 14.1.438.0; Thu, 6 Jun 2013 11:44:42 -0700
Received: from SJEXCHMB12.corp.ad.broadcom.com ( [fe80::bc15:c1e1:c29a:36f7]) by SJEXCHCAS06.corp.ad.broadcom.com ( [::1]) with mapi id 14.01.0438.000; Thu, 6 Jun 2013 11:44:42 -0700
From: "Shahram Davari" <davari@broadcom.com>
To: "Gregory Mirsky" <gregory.mirsky@ericsson.com>, "Amit Oren" <amito@broadcom.com>, "Bhatia, Manav (Manav)" <manav.bhatia@alcatel-lucent.com>, "Roberts, Peter (Peter)" <peter.roberts@alcatel-lucent.com>, "lmontini@cisco.com" <lmontini@cisco.com>, "tictoc@ietf.org" <tictoc@ietf.org>
Thread-Topic: NTP in draft-ietf-tictoc-1588overmpls-04
Thread-Index: Ac5i4ubOrT57JHkXTgC9GUzpraB4EAAAnB2w
Date: Thu, 6 Jun 2013 18:44:41 +0000
Message-ID: <4A6CE49E6084B141B15C0713B8993F281BE31FEA@SJEXCHMB12.corp.ad.broadcom.com>
References: <7347100B5761DC41A166AC17F22DF1121B4A0754@eusaamb103.ericsson.se>
In-Reply-To: <7347100B5761DC41A166AC17F22DF1121B4A0754@eusaamb103.ericsson.se>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.16.203.100]
MIME-Version: 1.0
X-WSS-ID: 7DAE09092L828973314-01-01
Content-Type: multipart/alternative; boundary=_000_4A6CE49E6084B141B15C0713B8993F281BE31FEASJEXCHMB12corpa_
Subject: Re: [TICTOC] NTP in draft-ietf-tictoc-1588overmpls-04
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, 06 Jun 2013 18:44:54 -0000

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

Hi Greg,

Even for NTP, there is a need to detect MPLS encapsulated NTP packets and t=
imestamp them at server nodes.  This draft allows such function. We know th=
at TC is not defined for NTP, but this draft leaves it open for NTP to defi=
ne TC if needed in the future.

Regards,
Shahram

From: Gregory Mirsky [mailto:gregory.mirsky@ericsson.com]
Sent: Thursday, June 06, 2013 11:23 AM
To: Shahram Davari; Amit Oren; Bhatia, Manav (Manav); Roberts, Peter (Peter=
); lmontini@cisco.com; tictoc@ietf.org
Subject: NTP in draft-ietf-tictoc-1588overmpls-04

Dear Authors, et al.,
The draft-ietf-tictoc-1588overmpls-04 is currently titled as "Transporting =
Timing messages over MPLS Networks" and states that both timing synchroniza=
tion protocols, PTP and NTP, require use of PTP LSP to transport timing mes=
sages over an MPLS network. After reading RFC 5905 I am not sure that PTP L=
SP, with its constraints and additional complexity, is required to transpor=
t NTPv4 messages over an MPLS network. And first paragraph in Section 3 Pro=
blem Statement of draft-ietf-tictoc-1588overmpls-04 explains motivation for=
 the PTP as
"There is a need to transport Timing messages over MPLS networks while supp=
orting the Transparent Clock (TC), Boundary Clock (BC) and Ordinary Clock (=
OC) functionality in the LER and LSRs in the MPLS network."
but says nothing of a kind about NTP.

        Regards,
                Greg


--_000_4A6CE49E6084B141B15C0713B8993F281BE31FEASJEXCHMB12corpa_
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)">
<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.emailquote, li.emailquote, div.emailquote
	{mso-style-name:emailquote;
	mso-margin-top-alt:auto;
	margin-right:0in;
	mso-margin-bottom-alt:auto;
	margin-left:1.0pt;
	border:none;
	padding:0in;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";}
span.EmailStyle18
	{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.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">Hi Greg,<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">Even for NTP, there is a =
need to detect MPLS encapsulated NTP packets and timestamp them at server n=
odes. &nbsp;This draft allows such function. We know that TC
 is not defined for NTP, but this draft leaves it open for NTP to define TC=
 if needed in the future.<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">Regards,<br>
Shahram<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;"> Gregory =
Mirsky [mailto:gregory.mirsky@ericsson.com]
<br>
<b>Sent:</b> Thursday, June 06, 2013 11:23 AM<br>
<b>To:</b> Shahram Davari; Amit Oren; Bhatia, Manav (Manav); Roberts, Peter=
 (Peter); lmontini@cisco.com; tictoc@ietf.org<br>
<b>Subject:</b> NTP in draft-ietf-tictoc-1588overmpls-04<o:p></o:p></span><=
/p>
</div>
</div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Ar=
ial&quot;,&quot;sans-serif&quot;">Dear Authors, et al.,<o:p></o:p></span></=
p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Ar=
ial&quot;,&quot;sans-serif&quot;">The draft-ietf-tictoc-1588overmpls-04 is =
currently titled as &quot;Transporting Timing messages over MPLS Networks&q=
uot; and states that both timing synchronization protocols, PTP and
 NTP, require use of PTP LSP to transport timing messages over an MPLS netw=
ork. After reading RFC 5905 I am not sure that PTP LSP, with its constraint=
s and additional complexity, is required to transport NTPv4 messages over a=
n MPLS network. And first paragraph
 in Section 3 Problem Statement of draft-ietf-tictoc-1588overmpls-04 explai=
ns motivation for the PTP as
<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Ar=
ial&quot;,&quot;sans-serif&quot;">&quot;There is a need to transport Timing=
 messages over MPLS networks while supporting the Transparent Clock (TC), B=
oundary Clock (BC) and Ordinary Clock (OC) functionality in the
 LER and LSRs in the MPLS network.&quot;<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Ar=
ial&quot;,&quot;sans-serif&quot;">but says nothing of a kind about NTP.<o:p=
></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Ar=
ial&quot;,&quot;sans-serif&quot;">&nbsp;<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Ar=
ial&quot;,&quot;sans-serif&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
; Regards,<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Ar=
ial&quot;,&quot;sans-serif&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Greg<o:p></o:p></span></p=
>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Ar=
ial&quot;,&quot;sans-serif&quot;">&nbsp;<o:p></o:p></span></p>
</div>
</div>
</body>
</html>

--_000_4A6CE49E6084B141B15C0713B8993F281BE31FEASJEXCHMB12corpa_--


From yaakov_s@rad.com  Fri Jun  7 07:55:03 2013
Return-Path: <yaakov_s@rad.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 7C37921F93B9 for <tictoc@ietfa.amsl.com>; Fri,  7 Jun 2013 07:55:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.597
X-Spam-Level: 
X-Spam-Status: No, score=-102.597 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, UNPARSEABLE_RELAY=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 SisbzsURKtUR for <tictoc@ietfa.amsl.com>; Fri,  7 Jun 2013 07:54:57 -0700 (PDT)
Received: from rad.co.il (mailrelay02-q.rad.co.il [94.188.133.159]) by ietfa.amsl.com (Postfix) with ESMTP id 1187E21F9458 for <tictoc@ietf.org>; Fri,  7 Jun 2013 07:54:53 -0700 (PDT)
Received: from Internal Mail-Server by MailRelay02 (envelope-from yaakov?s@rad.com) with AES128-SHA encrypted SMTP; 7 Jun 2013 17:52:23 +0300
Received: from EXRAD5.ad.rad.co.il ([192.114.24.28]) by EXRAD5.ad.rad.co.il ([192.114.24.28]) with mapi id 14.02.0298.004; Fri, 7 Jun 2013 17:54:46 +0300
From: Yaakov Stein <yaakov_s@rad.com>
To: Gregory Mirsky <gregory.mirsky@ericsson.com>, Shahram Davari <davari@broadcom.com>, "amito@broadcom.com" <amito@broadcom.com>, "Bhatia, Manav (Manav)" <manav.bhatia@alcatel-lucent.com>, "Roberts, Peter (Peter)" <peter.roberts@alcatel-lucent.com>, "lmontini@cisco.com" <lmontini@cisco.com>, "tictoc@ietf.org" <tictoc@ietf.org>
Thread-Topic: NTP in draft-ietf-tictoc-1588overmpls-04
Thread-Index: Ac5i4ubOrT57JHkXTgC9GUzpraB4EAAq9gQA
Date: Fri, 7 Jun 2013 14:54:45 +0000
Message-ID: <07F7D7DED63154409F13298786A2ADC904D6D57C@EXRAD5.ad.rad.co.il>
References: <7347100B5761DC41A166AC17F22DF1121B4A0754@eusaamb103.ericsson.se>
In-Reply-To: <7347100B5761DC41A166AC17F22DF1121B4A0754@eusaamb103.ericsson.se>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [207.232.33.112]
Content-Type: multipart/alternative; boundary="_000_07F7D7DED63154409F13298786A2ADC904D6D57CEXRAD5adradcoil_"
MIME-Version: 1.0
X-Commtouch-Refid: str=0001.0A0C0202.51B1F437.0145,ss=1,fgs=0
Subject: Re: [TICTOC] NTP in draft-ietf-tictoc-1588overmpls-04
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, 07 Jun 2013 14:55:03 -0000

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

Greg

This version makes the mechanism more general so that in future other time-=
sensitive protocols
(NTP, delay measurement OAM, generic header for MPLS) could avail themselve=
s of its timestamping/correction features.

It is true that the only real case so far is 1588.

Y(J)S

From: tictoc-bounces@ietf.org [mailto:tictoc-bounces@ietf.org] On Behalf Of=
 Gregory Mirsky
Sent: 06 June, 2013 21:23
To: Shahram Davari; amito@broadcom.com; Bhatia, Manav (Manav); Roberts, Pet=
er (Peter); lmontini@cisco.com; tictoc@ietf.org
Subject: [TICTOC] NTP in draft-ietf-tictoc-1588overmpls-04

Dear Authors, et al.,
The draft-ietf-tictoc-1588overmpls-04 is currently titled as "Transporting =
Timing messages over MPLS Networks" and states that both timing synchroniza=
tion protocols, PTP and NTP, require use of PTP LSP to transport timing mes=
sages over an MPLS network. After reading RFC 5905 I am not sure that PTP L=
SP, with its constraints and additional complexity, is required to transpor=
t NTPv4 messages over an MPLS network. And first paragraph in Section 3 Pro=
blem Statement of draft-ietf-tictoc-1588overmpls-04 explains motivation for=
 the PTP as
"There is a need to transport Timing messages over MPLS networks while supp=
orting the Transparent Clock (TC), Boundary Clock (BC) and Ordinary Clock (=
OC) functionality in the LER and LSRs in the MPLS network."
but says nothing of a kind about NTP.

        Regards,
                Greg


--_000_07F7D7DED63154409F13298786A2ADC904D6D57CEXRAD5adradcoil_
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 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.emailquote, li.emailquote, div.emailquote
	{mso-style-name:emailquote;
	mso-margin-top-alt:auto;
	margin-right:0in;
	mso-margin-bottom-alt:auto;
	margin-left:1.0pt;
	border:none;
	padding:0in;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";}
span.EmailStyle18
	{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">Greg<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 version makes the me=
chanism more general so that in future other time-sensitive protocols<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">(NTP, delay measurement O=
AM, generic header for MPLS) could avail themselves of its timestamping/cor=
rection features.<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">It is true that the only =
real case so far is 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">Y(J)S<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;"> tictoc-b=
ounces@ietf.org [mailto:tictoc-bounces@ietf.org]
<b>On Behalf Of </b>Gregory Mirsky<br>
<b>Sent:</b> 06 June, 2013 21:23<br>
<b>To:</b> Shahram Davari; amito@broadcom.com; Bhatia, Manav (Manav); Rober=
ts, Peter (Peter); lmontini@cisco.com; tictoc@ietf.org<br>
<b>Subject:</b> [TICTOC] NTP in draft-ietf-tictoc-1588overmpls-04<o:p></o:p=
></span></p>
</div>
</div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Ar=
ial&quot;,&quot;sans-serif&quot;">Dear Authors, et al.,<o:p></o:p></span></=
p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Ar=
ial&quot;,&quot;sans-serif&quot;">The draft-ietf-tictoc-1588overmpls-04 is =
currently titled as &quot;Transporting Timing messages over MPLS Networks&q=
uot; and states that both timing synchronization protocols, PTP and
 NTP, require use of PTP LSP to transport timing messages over an MPLS netw=
ork. After reading RFC 5905 I am not sure that PTP LSP, with its constraint=
s and additional complexity, is required to transport NTPv4 messages over a=
n MPLS network. And first paragraph
 in Section 3 Problem Statement of draft-ietf-tictoc-1588overmpls-04 explai=
ns motivation for the PTP as
<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Ar=
ial&quot;,&quot;sans-serif&quot;">&quot;There is a need to transport Timing=
 messages over MPLS networks while supporting the Transparent Clock (TC), B=
oundary Clock (BC) and Ordinary Clock (OC) functionality in the
 LER and LSRs in the MPLS network.&quot;<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Ar=
ial&quot;,&quot;sans-serif&quot;">but says nothing of a kind about NTP.<o:p=
></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Ar=
ial&quot;,&quot;sans-serif&quot;">&nbsp;<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Ar=
ial&quot;,&quot;sans-serif&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
; Regards,<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Ar=
ial&quot;,&quot;sans-serif&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Greg<o:p></o:p></span></p=
>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Ar=
ial&quot;,&quot;sans-serif&quot;">&nbsp;<o:p></o:p></span></p>
</div>
</div>
</body>
</html>

--_000_07F7D7DED63154409F13298786A2ADC904D6D57CEXRAD5adradcoil_--

From prvs=2870e64481=gregory.mirsky@ericsson.com  Fri Jun  7 08:28:35 2013
Return-Path: <prvs=2870e64481=gregory.mirsky@ericsson.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 47BFD21F8F3E for <tictoc@ietfa.amsl.com>; Fri,  7 Jun 2013 08:28:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.598
X-Spam-Level: 
X-Spam-Status: No, score=-2.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=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 e8phWU46f4h0 for <tictoc@ietfa.amsl.com>; Fri,  7 Jun 2013 08:28:28 -0700 (PDT)
Received: from usevmg20.ericsson.net (usevmg20.ericsson.net [198.24.6.45]) by ietfa.amsl.com (Postfix) with ESMTP id 859BB21F8EFE for <tictoc@ietf.org>; Fri,  7 Jun 2013 08:28:28 -0700 (PDT)
X-AuditID: c618062d-b7f936d000004481-55-51b1fc1b0784
Received: from EUSAAHC004.ericsson.se (Unknown_Domain [147.117.188.84]) by usevmg20.ericsson.net (Symantec Mail Security) with SMTP id F1.F4.17537.B1CF1B15; Fri,  7 Jun 2013 17:28:27 +0200 (CEST)
Received: from EUSAAMB103.ericsson.se ([147.117.188.120]) by EUSAAHC004.ericsson.se ([147.117.188.84]) with mapi id 14.02.0328.009; Fri, 7 Jun 2013 11:28:27 -0400
From: Gregory Mirsky <gregory.mirsky@ericsson.com>
To: Yaakov Stein <yaakov_s@rad.com>, Shahram Davari <davari@broadcom.com>, "amito@broadcom.com" <amito@broadcom.com>, "Bhatia, Manav (Manav)" <manav.bhatia@alcatel-lucent.com>, "Roberts, Peter (Peter)" <peter.roberts@alcatel-lucent.com>, "lmontini@cisco.com" <lmontini@cisco.com>, "tictoc@ietf.org" <tictoc@ietf.org>
Thread-Topic: NTP in draft-ietf-tictoc-1588overmpls-04
Thread-Index: Ac5i4ubOrT57JHkXTgC9GUzpraB4EAAq9gQAAAElPiA=
Date: Fri, 7 Jun 2013 15:28:25 +0000
Message-ID: <7347100B5761DC41A166AC17F22DF1121B4A0CB9@eusaamb103.ericsson.se>
References: <7347100B5761DC41A166AC17F22DF1121B4A0754@eusaamb103.ericsson.se> <07F7D7DED63154409F13298786A2ADC904D6D57C@EXRAD5.ad.rad.co.il>
In-Reply-To: <07F7D7DED63154409F13298786A2ADC904D6D57C@EXRAD5.ad.rad.co.il>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [147.117.188.134]
Content-Type: multipart/alternative; boundary="_000_7347100B5761DC41A166AC17F22DF1121B4A0CB9eusaamb103erics_"
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFmpjkeLIzCtJLcpLzFFi42KZXLonRFf6z8ZAg527rC32XM6wWN/raXH3 80smizn37rFa3N70lNXib3MPu8WHrh+sDuwerc/2snrMun+WzWPK742sHkuW/GTymLQ2LYA1 itsmKbGkLDgzPU/fLoE7Y9/WdvaC/VEVt34kNTDO9O9i5OSQEDCRONHeyA5hi0lcuLeerYuR i0NI4CijxMamxewQzjJGiUtr/rGCVLEJGEm82NgDlhAROMIkcW39W2aQhLCAqcSbezdZQGwR ATOJh882Q9lWEr/OvgRbwSKgIvH/ZB8jiM0r4Ctxbe03JogNfYwSDzu/ghVxCnhLnH4wCWwo I9BN30+tYQKxmQXEJW49mc8EcauAxJI955khbFGJl48hrpMQUJZY8mQ/C0R9vsTu/SfZIJYJ Spyc+YRlAqPILCSjZiEpm4WkDCKuI7Fg9yc2CFtbYtnC18ww9pkDj5mQxRcwsq9i5CgtTi3L TTcy2MQIjMZjEmy6Oxj3vLQ8xCjNwaIkzqvGuzhQSCA9sSQ1OzW1ILUovqg0J7X4ECMTByeI 4JJqYPRZuK0k6u+kQtmNKiuLTvRqqzfujJ20ecd7vdrOjxNPCF1Ovv+Pmyf/PuuHW/b7pf3W 8S5/qzFxXuTO1wIfjvGb9raxlfDWz3j53/X7gumc+y7qXX50436cwy+/bw8FXviHWYkZq5nN yl9QeGsLp8STruSWqy7qmYzTz/rOlUr8+3bhysCN/yOVWIozEg21mIuKEwHdGIkXmQIAAA==
Subject: Re: [TICTOC] NTP in draft-ietf-tictoc-1588overmpls-04
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, 07 Jun 2013 15:28:35 -0000

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

Yaakov,
I'm rather sceptical of using "If you build it, he will come" as protocol d=
evelopment guiding principle. Personally I prefer KISS.

    Regards,
        Greg

________________________________
From: Yaakov Stein [mailto:yaakov_s@rad.com]
Sent: Friday, June 07, 2013 7:55 AM
To: Gregory Mirsky; Shahram Davari; amito@broadcom.com; Bhatia, Manav (Mana=
v); Roberts, Peter (Peter); lmontini@cisco.com; tictoc@ietf.org
Subject: RE: NTP in draft-ietf-tictoc-1588overmpls-04

Greg

This version makes the mechanism more general so that in future other time-=
sensitive protocols
(NTP, delay measurement OAM, generic header for MPLS) could avail themselve=
s of its timestamping/correction features.

It is true that the only real case so far is 1588.

Y(J)S

From: tictoc-bounces@ietf.org [mailto:tictoc-bounces@ietf.org] On Behalf Of=
 Gregory Mirsky
Sent: 06 June, 2013 21:23
To: Shahram Davari; amito@broadcom.com; Bhatia, Manav (Manav); Roberts, Pet=
er (Peter); lmontini@cisco.com; tictoc@ietf.org
Subject: [TICTOC] NTP in draft-ietf-tictoc-1588overmpls-04

Dear Authors, et al.,
The draft-ietf-tictoc-1588overmpls-04 is currently titled as "Transporting =
Timing messages over MPLS Networks" and states that both timing synchroniza=
tion protocols, PTP and NTP, require use of PTP LSP to transport timing mes=
sages over an MPLS network. After reading RFC 5905 I am not sure that PTP L=
SP, with its constraints and additional complexity, is required to transpor=
t NTPv4 messages over an MPLS network. And first paragraph in Section 3 Pro=
blem Statement of draft-ietf-tictoc-1588overmpls-04 explains motivation for=
 the PTP as
"There is a need to transport Timing messages over MPLS networks while supp=
orting the Transparent Clock (TC), Boundary Clock (BC) and Ordinary Clock (=
OC) functionality in the LER and LSRs in the MPLS network."
but says nothing of a kind about NTP.

        Regards,
                Greg


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

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<html xmlns=3D"http://www.w3.org/TR/REC-html40" xmlns:v=3D"urn:schemas-micr=
osoft-com:vml" xmlns:o=3D"urn:schemas-microsoft-com:office:office" xmlns:w=
=3D"urn:schemas-microsoft-com:office:word" xmlns:m=3D"http://schemas.micros=
oft.com/office/2004/12/omml">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
<meta content=3D"MSHTML 6.00.6002.18823" name=3D"GENERATOR">
<style>@font-face {
	font-family: Cambria Math;
}
@font-face {
	font-family: Calibri;
}
@font-face {
	font-family: Tahoma;
}
@page WordSection1 {size: 8.5in 11.0in; margin: 1.0in 1.25in 1.0in 1.25in; =
}
P.MsoNormal {
	FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman","seri=
f"
}
LI.MsoNormal {
	FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman","seri=
f"
}
DIV.MsoNormal {
	FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman","seri=
f"
}
A:link {
	COLOR: blue; TEXT-DECORATION: underline; mso-style-priority: 99
}
SPAN.MsoHyperlink {
	COLOR: blue; TEXT-DECORATION: underline; mso-style-priority: 99
}
A:visited {
	COLOR: purple; TEXT-DECORATION: underline; mso-style-priority: 99
}
SPAN.MsoHyperlinkFollowed {
	COLOR: purple; TEXT-DECORATION: underline; mso-style-priority: 99
}
P.emailquote {
	BORDER-RIGHT: medium none; PADDING-RIGHT: 0in; BORDER-TOP: medium none; PA=
DDING-LEFT: 0in; FONT-SIZE: 12pt; PADDING-BOTTOM: 0in; MARGIN-LEFT: 1pt; BO=
RDER-LEFT: medium none; MARGIN-RIGHT: 0in; PADDING-TOP: 0in; BORDER-BOTTOM:=
 medium none; FONT-FAMILY: "Times New Roman","serif"; mso-style-name: email=
quote; mso-margin-top-alt: auto; mso-margin-bottom-alt: auto
}
LI.emailquote {
	BORDER-RIGHT: medium none; PADDING-RIGHT: 0in; BORDER-TOP: medium none; PA=
DDING-LEFT: 0in; FONT-SIZE: 12pt; PADDING-BOTTOM: 0in; MARGIN-LEFT: 1pt; BO=
RDER-LEFT: medium none; MARGIN-RIGHT: 0in; PADDING-TOP: 0in; BORDER-BOTTOM:=
 medium none; FONT-FAMILY: "Times New Roman","serif"; mso-style-name: email=
quote; mso-margin-top-alt: auto; mso-margin-bottom-alt: auto
}
DIV.emailquote {
	BORDER-RIGHT: medium none; PADDING-RIGHT: 0in; BORDER-TOP: medium none; PA=
DDING-LEFT: 0in; FONT-SIZE: 12pt; PADDING-BOTTOM: 0in; MARGIN-LEFT: 1pt; BO=
RDER-LEFT: medium none; MARGIN-RIGHT: 0in; PADDING-TOP: 0in; BORDER-BOTTOM:=
 medium none; FONT-FAMILY: "Times New Roman","serif"; mso-style-name: email=
quote; mso-margin-top-alt: auto; mso-margin-bottom-alt: auto
}
SPAN.EmailStyle18 {
	COLOR: #1f497d; FONT-FAMILY: "Calibri","sans-serif"; mso-style-type: perso=
nal-reply
}
.MsoChpDefault {
	FONT-SIZE: 10pt; mso-style-type: export-only
}
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" vlink=3D"purple" link=3D"blue">
<div dir=3D"ltr" align=3D"left"><span class=3D"070062615-07062013"><font fa=
ce=3D"Arial" color=3D"#0000ff" size=3D"2">Yaakov,</font></span></div>
<div dir=3D"ltr" align=3D"left"><span class=3D"070062615-07062013"><font fa=
ce=3D"Arial"><font size=3D"2"><font color=3D"#0000ff">I'm rather sceptical =
of using &quot;<span class=3D"st">If you build it, he will come&quot; as pr=
otocol development guiding principle. Personally I prefer
 KISS.</span></font></font></font></span></div>
<div dir=3D"ltr" align=3D"left"><span class=3D"070062615-07062013"><font fa=
ce=3D"Arial"><font size=3D"2"><font color=3D"#0000ff"><span class=3D"st"></=
span></font></font></font></span>&nbsp;</div>
<div dir=3D"ltr" align=3D"left"><span class=3D"070062615-07062013"><font fa=
ce=3D"Arial"><font size=3D"2"><font color=3D"#0000ff"><span class=3D"st">&n=
bsp;&nbsp;&nbsp; Regards,</span></font></font></font></span></div>
<div dir=3D"ltr" align=3D"left"><span class=3D"070062615-07062013"><font fa=
ce=3D"Arial"><font size=3D"2"><font color=3D"#0000ff"><span class=3D"st">&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Greg</span></font></font></font></=
span></div>
<br>
<div class=3D"OutlookMessageHeader" lang=3D"en-us" dir=3D"ltr" align=3D"lef=
t">
<hr tabindex=3D"-1">
<font face=3D"Tahoma" size=3D"2"><b>From:</b> Yaakov Stein [mailto:yaakov_s=
@rad.com] <br>
<b>Sent:</b> Friday, June 07, 2013 7:55 AM<br>
<b>To:</b> Gregory Mirsky; Shahram Davari; amito@broadcom.com; Bhatia, Mana=
v (Manav); Roberts, Peter (Peter); lmontini@cisco.com; tictoc@ietf.org<br>
<b>Subject:</b> RE: NTP in draft-ietf-tictoc-1588overmpls-04<br>
</font><br>
</div>
<div></div>
<div class=3D"WordSection1">
<p class=3D"MsoNormal"><span style=3D"FONT-SIZE: 11pt; COLOR: #1f497d; FONT=
-FAMILY: 'Calibri','sans-serif'">Greg<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"FONT-SIZE: 11pt; COLOR: #1f497d; FONT=
-FAMILY: 'Calibri','sans-serif'"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"FONT-SIZE: 11pt; COLOR: #1f497d; FONT=
-FAMILY: 'Calibri','sans-serif'">This version makes the mechanism more gene=
ral so that in future other time-sensitive protocols<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"FONT-SIZE: 11pt; COLOR: #1f497d; FONT=
-FAMILY: 'Calibri','sans-serif'">(NTP, delay measurement OAM, generic heade=
r for MPLS) could avail themselves of its timestamping/correction features.=
<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"FONT-SIZE: 11pt; COLOR: #1f497d; FONT=
-FAMILY: 'Calibri','sans-serif'"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"FONT-SIZE: 11pt; COLOR: #1f497d; FONT=
-FAMILY: 'Calibri','sans-serif'">It is true that the only real case so far =
is 1588.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"FONT-SIZE: 11pt; COLOR: #1f497d; FONT=
-FAMILY: 'Calibri','sans-serif'"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"FONT-SIZE: 11pt; COLOR: #1f497d; FONT=
-FAMILY: 'Calibri','sans-serif'">Y(J)S<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"FONT-SIZE: 11pt; COLOR: #1f497d; FONT=
-FAMILY: 'Calibri','sans-serif'"><o:p>&nbsp;</o:p></span></p>
<div>
<div style=3D"BORDER-RIGHT: medium none; PADDING-RIGHT: 0in; BORDER-TOP: #b=
5c4df 1pt solid; PADDING-LEFT: 0in; PADDING-BOTTOM: 0in; BORDER-LEFT: mediu=
m none; PADDING-TOP: 3pt; BORDER-BOTTOM: medium none">
<p class=3D"MsoNormal"><b><span style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'Tah=
oma','sans-serif'">From:</span></b><span style=3D"FONT-SIZE: 10pt; FONT-FAM=
ILY: 'Tahoma','sans-serif'"> tictoc-bounces@ietf.org [mailto:tictoc-bounces=
@ietf.org]
<b>On Behalf Of </b>Gregory Mirsky<br>
<b>Sent:</b> 06 June, 2013 21:23<br>
<b>To:</b> Shahram Davari; amito@broadcom.com; Bhatia, Manav (Manav); Rober=
ts, Peter (Peter); lmontini@cisco.com; tictoc@ietf.org<br>
<b>Subject:</b> [TICTOC] NTP in draft-ietf-tictoc-1588overmpls-04<o:p></o:p=
></span></p>
</div>
</div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<div>
<p class=3D"MsoNormal"><span style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'Arial'=
,'sans-serif'">Dear Authors, et al.,<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'Arial'=
,'sans-serif'">The draft-ietf-tictoc-1588overmpls-04 is currently titled as=
 &quot;Transporting Timing messages over MPLS Networks&quot; and states tha=
t both timing synchronization protocols, PTP and
 NTP, require use of PTP LSP to transport timing messages over an MPLS netw=
ork. After reading RFC 5905 I am not sure that PTP LSP, with its constraint=
s and additional complexity, is required to transport NTPv4 messages over a=
n MPLS network. And first paragraph
 in Section 3 Problem Statement of draft-ietf-tictoc-1588overmpls-04 explai=
ns motivation for the PTP as
<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'Arial'=
,'sans-serif'">&quot;There is a need to transport Timing messages over MPLS=
 networks while supporting the Transparent Clock (TC), Boundary Clock (BC) =
and Ordinary Clock (OC) functionality in
 the LER and LSRs in the MPLS network.&quot;<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'Arial'=
,'sans-serif'">but says nothing of a kind about NTP.<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'Arial'=
,'sans-serif'">&nbsp;<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'Arial'=
,'sans-serif'">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Regards,<o:p></o:=
p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'Arial'=
,'sans-serif'">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Greg<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'Arial'=
,'sans-serif'">&nbsp;<o:p></o:p></span></p>
</div>
</div>
</body>
</html>

--_000_7347100B5761DC41A166AC17F22DF1121B4A0CB9eusaamb103erics_--

From davari@broadcom.com  Fri Jun  7 09:01:05 2013
Return-Path: <davari@broadcom.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 7154021F9923 for <tictoc@ietfa.amsl.com>; Fri,  7 Jun 2013 09:00:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.598
X-Spam-Level: 
X-Spam-Status: No, score=-6.598 tagged_above=-999 required=5 tests=[AWL=-0.000, BAYES_00=-2.599, 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 bigciJiIaV5b for <tictoc@ietfa.amsl.com>; Fri,  7 Jun 2013 09:00:48 -0700 (PDT)
Received: from mms3.broadcom.com (mms3.broadcom.com [216.31.210.19]) by ietfa.amsl.com (Postfix) with ESMTP id EA48D21F991E for <tictoc@ietf.org>; Fri,  7 Jun 2013 09:00:44 -0700 (PDT)
Received: from [10.9.208.53] by mms3.broadcom.com with ESMTP (Broadcom SMTP Relay (Email Firewall v6.5)); Fri, 07 Jun 2013 08:51:41 -0700
X-Server-Uuid: B86B6450-0931-4310-942E-F00ED04CA7AF
Received: from SJEXCHCAS07.corp.ad.broadcom.com (10.16.203.16) by IRVEXCHCAS06.corp.ad.broadcom.com (10.9.208.53) with Microsoft SMTP Server (TLS) id 14.1.438.0; Fri, 7 Jun 2013 09:00:36 -0700
Received: from SJEXCHMB12.corp.ad.broadcom.com ( [fe80::bc15:c1e1:c29a:36f7]) by SJEXCHCAS07.corp.ad.broadcom.com ( [::1]) with mapi id 14.01.0438.000; Fri, 7 Jun 2013 09:00:36 -0700
From: "Shahram Davari" <davari@broadcom.com>
To: "Gregory Mirsky" <gregory.mirsky@ericsson.com>
Thread-Topic: NTP in draft-ietf-tictoc-1588overmpls-04
Thread-Index: Ac5i4ubOrT57JHkXTgC9GUzpraB4EAAq9gQAAAElPiAAATQbzw==
Date: Fri, 7 Jun 2013 16:00:33 +0000
Message-ID: <DDB3D38B-6FE8-4A4A-A604-56AB9181C5FE@broadcom.com>
References: <7347100B5761DC41A166AC17F22DF1121B4A0754@eusaamb103.ericsson.se> <07F7D7DED63154409F13298786A2ADC904D6D57C@EXRAD5.ad.rad.co.il>, <7347100B5761DC41A166AC17F22DF1121B4A0CB9@eusaamb103.ericsson.se>
In-Reply-To: <7347100B5761DC41A166AC17F22DF1121B4A0CB9@eusaamb103.ericsson.se>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
MIME-Version: 1.0
X-WSS-ID: 7DACDE062L829491135-01-01
Content-Type: multipart/alternative; boundary=_000_DDB3D38B6FE84A4AA60456AB9181C5FEbroadcomcom_
Cc: "tictoc@ietf.org" <tictoc@ietf.org>
Subject: Re: [TICTOC] NTP in draft-ietf-tictoc-1588overmpls-04
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, 07 Jun 2013 16:01:05 -0000

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

Greg,

This draft was originally only for PTP, however our Area Director asked the=
 draft to be made more generic so that it can apply to any timing protocol.

Regards,
Shahram


On Jun 7, 2013, at 8:28 AM, "Gregory Mirsky" <gregory.mirsky@ericsson.com<m=
ailto:gregory.mirsky@ericsson.com>> wrote:

Yaakov,
I'm rather sceptical of using "If you build it, he will come" as protocol d=
evelopment guiding principle. Personally I prefer KISS.

    Regards,
        Greg

________________________________
From: Yaakov Stein [mailto:yaakov_s@rad.com]
Sent: Friday, June 07, 2013 7:55 AM
To: Gregory Mirsky; Shahram Davari; amito@broadcom.com<mailto:amito@broadco=
m.com>; Bhatia, Manav (Manav); Roberts, Peter (Peter); lmontini@cisco.com<m=
ailto:lmontini@cisco.com>; tictoc@ietf.org<mailto:tictoc@ietf.org>
Subject: RE: NTP in draft-ietf-tictoc-1588overmpls-04

Greg

This version makes the mechanism more general so that in future other time-=
sensitive protocols
(NTP, delay measurement OAM, generic header for MPLS) could avail themselve=
s of its timestamping/correction features.

It is true that the only real case so far is 1588.

Y(J)S

From: tictoc-bounces@ietf.org<mailto:tictoc-bounces@ietf.org> [mailto:ticto=
c-bounces@ietf.org] On Behalf Of Gregory Mirsky
Sent: 06 June, 2013 21:23
To: Shahram Davari; amito@broadcom.com<mailto:amito@broadcom.com>; Bhatia, =
Manav (Manav); Roberts, Peter (Peter); lmontini@cisco.com<mailto:lmontini@c=
isco.com>; tictoc@ietf.org<mailto:tictoc@ietf.org>
Subject: [TICTOC] NTP in draft-ietf-tictoc-1588overmpls-04

Dear Authors, et al.,
The draft-ietf-tictoc-1588overmpls-04 is currently titled as "Transporting =
Timing messages over MPLS Networks" and states that both timing synchroniza=
tion protocols, PTP and NTP, require use of PTP LSP to transport timing mes=
sages over an MPLS network. After reading RFC 5905 I am not sure that PTP L=
SP, with its constraints and additional complexity, is required to transpor=
t NTPv4 messages over an MPLS network. And first paragraph in Section 3 Pro=
blem Statement of draft-ietf-tictoc-1588overmpls-04 explains motivation for=
 the PTP as
"There is a need to transport Timing messages over MPLS networks while supp=
orting the Transparent Clock (TC), Boundary Clock (BC) and Ordinary Clock (=
OC) functionality in the LER and LSRs in the MPLS network."
but says nothing of a kind about NTP.

        Regards,
                Greg


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

<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
</head>
<body dir=3D"auto">
<div>Greg,</div>
<div><br>
</div>
<div>This draft was originally only for PTP, however our Area Director aske=
d the draft to be made more generic so that it can apply to any timing prot=
ocol.<br>
<br>
Regards,
<div>Shahram</div>
<div><br>
</div>
</div>
<div><br>
On Jun 7, 2013, at 8:28 AM, &quot;Gregory Mirsky&quot; &lt;<a href=3D"mailt=
o:gregory.mirsky@ericsson.com">gregory.mirsky@ericsson.com</a>&gt; wrote:<b=
r>
<br>
</div>
<blockquote type=3D"cite">
<div>
<meta content=3D"MSHTML 6.00.6002.18823" name=3D"GENERATOR">
<style>@font-face {
	font-family: Cambria Math;
}
@font-face {
	font-family: Calibri;
}
@font-face {
	font-family: Tahoma;
}
@page WordSection1 {size: 8.5in 11.0in; margin: 1.0in 1.25in 1.0in 1.25in; =
}
P.MsoNormal {
	FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman","seri=
f"
}
LI.MsoNormal {
	FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman","seri=
f"
}
DIV.MsoNormal {
	FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman","seri=
f"
}
A:link {
	COLOR: blue; TEXT-DECORATION: underline; mso-style-priority: 99
}
SPAN.MsoHyperlink {
	COLOR: blue; TEXT-DECORATION: underline; mso-style-priority: 99
}
A:visited {
	COLOR: purple; TEXT-DECORATION: underline; mso-style-priority: 99
}
SPAN.MsoHyperlinkFollowed {
	COLOR: purple; TEXT-DECORATION: underline; mso-style-priority: 99
}
P.emailquote {
	BORDER-RIGHT: medium none; PADDING-RIGHT: 0in; BORDER-TOP: medium none; PA=
DDING-LEFT: 0in; FONT-SIZE: 12pt; PADDING-BOTTOM: 0in; MARGIN-LEFT: 1pt; BO=
RDER-LEFT: medium none; MARGIN-RIGHT: 0in; PADDING-TOP: 0in; BORDER-BOTTOM:=
 medium none; FONT-FAMILY: "Times New Roman","serif"; mso-style-name: email=
quote; mso-margin-top-alt: auto; mso-margin-bottom-alt: auto
}
LI.emailquote {
	BORDER-RIGHT: medium none; PADDING-RIGHT: 0in; BORDER-TOP: medium none; PA=
DDING-LEFT: 0in; FONT-SIZE: 12pt; PADDING-BOTTOM: 0in; MARGIN-LEFT: 1pt; BO=
RDER-LEFT: medium none; MARGIN-RIGHT: 0in; PADDING-TOP: 0in; BORDER-BOTTOM:=
 medium none; FONT-FAMILY: "Times New Roman","serif"; mso-style-name: email=
quote; mso-margin-top-alt: auto; mso-margin-bottom-alt: auto
}
DIV.emailquote {
	BORDER-RIGHT: medium none; PADDING-RIGHT: 0in; BORDER-TOP: medium none; PA=
DDING-LEFT: 0in; FONT-SIZE: 12pt; PADDING-BOTTOM: 0in; MARGIN-LEFT: 1pt; BO=
RDER-LEFT: medium none; MARGIN-RIGHT: 0in; PADDING-TOP: 0in; BORDER-BOTTOM:=
 medium none; FONT-FAMILY: "Times New Roman","serif"; mso-style-name: email=
quote; mso-margin-top-alt: auto; mso-margin-bottom-alt: auto
}
SPAN.EmailStyle18 {
	COLOR: #1f497d; FONT-FAMILY: "Calibri","sans-serif"; mso-style-type: perso=
nal-reply
}
.MsoChpDefault {
	FONT-SIZE: 10pt; mso-style-type: export-only
}
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]-->
<div dir=3D"ltr" align=3D"left"><span class=3D"070062615-07062013"><font fa=
ce=3D"Arial" color=3D"#0000ff" size=3D"2">Yaakov,</font></span></div>
<div dir=3D"ltr" align=3D"left"><span class=3D"070062615-07062013"><font fa=
ce=3D"Arial"><font size=3D"2"><font color=3D"#0000ff">I'm rather sceptical =
of using &quot;<span class=3D"st">If you build it, he will come&quot; as pr=
otocol development guiding principle. Personally I prefer
 KISS.</span></font></font></font></span></div>
<div dir=3D"ltr" align=3D"left"><span class=3D"070062615-07062013"><font fa=
ce=3D"Arial"><font size=3D"2"><font color=3D"#0000ff"><span class=3D"st"></=
span></font></font></font></span>&nbsp;</div>
<div dir=3D"ltr" align=3D"left"><span class=3D"070062615-07062013"><font fa=
ce=3D"Arial"><font size=3D"2"><font color=3D"#0000ff"><span class=3D"st">&n=
bsp;&nbsp;&nbsp; Regards,</span></font></font></font></span></div>
<div dir=3D"ltr" align=3D"left"><span class=3D"070062615-07062013"><font fa=
ce=3D"Arial"><font size=3D"2"><font color=3D"#0000ff"><span class=3D"st">&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Greg</span></font></font></font></=
span></div>
<br>
<div class=3D"OutlookMessageHeader" lang=3D"en-us" dir=3D"ltr" align=3D"lef=
t">
<hr tabindex=3D"-1">
<font face=3D"Tahoma" size=3D"2"><b>From:</b> Yaakov Stein [<a href=3D"mail=
to:yaakov_s@rad.com">mailto:yaakov_s@rad.com</a>]
<br>
<b>Sent:</b> Friday, June 07, 2013 7:55 AM<br>
<b>To:</b> Gregory Mirsky; Shahram Davari; <a href=3D"mailto:amito@broadcom=
.com">amito@broadcom.com</a>; Bhatia, Manav (Manav); Roberts, Peter (Peter)=
;
<a href=3D"mailto:lmontini@cisco.com">lmontini@cisco.com</a>; <a href=3D"ma=
ilto:tictoc@ietf.org">
tictoc@ietf.org</a><br>
<b>Subject:</b> RE: NTP in draft-ietf-tictoc-1588overmpls-04<br>
</font><br>
</div>
<div></div>
<div class=3D"WordSection1">
<p class=3D"MsoNormal"><span style=3D"FONT-SIZE: 11pt; COLOR: #1f497d; FONT=
-FAMILY: 'Calibri','sans-serif'">Greg<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"FONT-SIZE: 11pt; COLOR: #1f497d; FONT=
-FAMILY: 'Calibri','sans-serif'"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"FONT-SIZE: 11pt; COLOR: #1f497d; FONT=
-FAMILY: 'Calibri','sans-serif'">This version makes the mechanism more gene=
ral so that in future other time-sensitive protocols<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"FONT-SIZE: 11pt; COLOR: #1f497d; FONT=
-FAMILY: 'Calibri','sans-serif'">(NTP, delay measurement OAM, generic heade=
r for MPLS) could avail themselves of its timestamping/correction features.=
<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"FONT-SIZE: 11pt; COLOR: #1f497d; FONT=
-FAMILY: 'Calibri','sans-serif'"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"FONT-SIZE: 11pt; COLOR: #1f497d; FONT=
-FAMILY: 'Calibri','sans-serif'">It is true that the only real case so far =
is 1588.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"FONT-SIZE: 11pt; COLOR: #1f497d; FONT=
-FAMILY: 'Calibri','sans-serif'"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"FONT-SIZE: 11pt; COLOR: #1f497d; FONT=
-FAMILY: 'Calibri','sans-serif'">Y(J)S<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"FONT-SIZE: 11pt; COLOR: #1f497d; FONT=
-FAMILY: 'Calibri','sans-serif'"><o:p>&nbsp;</o:p></span></p>
<div>
<div style=3D"BORDER-RIGHT: medium none; PADDING-RIGHT: 0in; BORDER-TOP: #b=
5c4df 1pt solid; PADDING-LEFT: 0in; PADDING-BOTTOM: 0in; BORDER-LEFT: mediu=
m none; PADDING-TOP: 3pt; BORDER-BOTTOM: medium none">
<p class=3D"MsoNormal"><b><span style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'Tah=
oma','sans-serif'">From:</span></b><span style=3D"FONT-SIZE: 10pt; FONT-FAM=
ILY: 'Tahoma','sans-serif'">
<a href=3D"mailto:tictoc-bounces@ietf.org">tictoc-bounces@ietf.org</a> [<a =
href=3D"mailto:tictoc-bounces@ietf.org">mailto:tictoc-bounces@ietf.org</a>]
<b>On Behalf Of </b>Gregory Mirsky<br>
<b>Sent:</b> 06 June, 2013 21:23<br>
<b>To:</b> Shahram Davari; <a href=3D"mailto:amito@broadcom.com">amito@broa=
dcom.com</a>; Bhatia, Manav (Manav); Roberts, Peter (Peter);
<a href=3D"mailto:lmontini@cisco.com">lmontini@cisco.com</a>; <a href=3D"ma=
ilto:tictoc@ietf.org">
tictoc@ietf.org</a><br>
<b>Subject:</b> [TICTOC] NTP in draft-ietf-tictoc-1588overmpls-04<o:p></o:p=
></span></p>
</div>
</div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<div>
<p class=3D"MsoNormal"><span style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'Arial'=
,'sans-serif'">Dear Authors, et al.,<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'Arial'=
,'sans-serif'">The draft-ietf-tictoc-1588overmpls-04 is currently titled as=
 &quot;Transporting Timing messages over MPLS Networks&quot; and states tha=
t both timing synchronization protocols, PTP and
 NTP, require use of PTP LSP to transport timing messages over an MPLS netw=
ork. After reading RFC 5905 I am not sure that PTP LSP, with its constraint=
s and additional complexity, is required to transport NTPv4 messages over a=
n MPLS network. And first paragraph
 in Section 3 Problem Statement of draft-ietf-tictoc-1588overmpls-04 explai=
ns motivation for the PTP as
<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'Arial'=
,'sans-serif'">&quot;There is a need to transport Timing messages over MPLS=
 networks while supporting the Transparent Clock (TC), Boundary Clock (BC) =
and Ordinary Clock (OC) functionality in
 the LER and LSRs in the MPLS network.&quot;<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'Arial'=
,'sans-serif'">but says nothing of a kind about NTP.<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'Arial'=
,'sans-serif'">&nbsp;<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'Arial'=
,'sans-serif'">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Regards,<o:p></o:=
p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'Arial'=
,'sans-serif'">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Greg<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'Arial'=
,'sans-serif'">&nbsp;<o:p></o:p></span></p>
</div>
</div>
</div>
</blockquote>
</body>
</html>

--_000_DDB3D38B6FE84A4AA60456AB9181C5FEbroadcomcom_--


From prvs=7870637af7=gregory.mirsky@ericsson.com  Fri Jun  7 09:07:41 2013
Return-Path: <prvs=7870637af7=gregory.mirsky@ericsson.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 B4DDB21F9458 for <tictoc@ietfa.amsl.com>; Fri,  7 Jun 2013 09:07:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.598
X-Spam-Level: 
X-Spam-Status: No, score=-2.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=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 JiuaJMG3mJwT for <tictoc@ietfa.amsl.com>; Fri,  7 Jun 2013 09:07:29 -0700 (PDT)
Received: from usevmg21.ericsson.net (usevmg21.ericsson.net [198.24.6.65]) by ietfa.amsl.com (Postfix) with ESMTP id 1305621F93D2 for <tictoc@ietf.org>; Fri,  7 Jun 2013 09:07:29 -0700 (PDT)
X-AuditID: c6180641-b7f0e6d0000015f1-15-51b2053fe3f3
Received: from EUSAAHC008.ericsson.se (Unknown_Domain [147.117.188.96]) by usevmg21.ericsson.net (Symantec Mail Security) with SMTP id FF.E4.05617.F3502B15; Fri,  7 Jun 2013 18:07:28 +0200 (CEST)
Received: from EUSAAMB103.ericsson.se ([147.117.188.120]) by EUSAAHC008.ericsson.se ([147.117.188.96]) with mapi id 14.02.0328.009; Fri, 7 Jun 2013 12:07:27 -0400
From: Gregory Mirsky <gregory.mirsky@ericsson.com>
To: Shahram Davari <davari@broadcom.com>
Thread-Topic: NTP in draft-ietf-tictoc-1588overmpls-04
Thread-Index: Ac5i4ubOrT57JHkXTgC9GUzpraB4EAAq9gQAAAElPiAAATQbzwAADGYg
Date: Fri, 7 Jun 2013 16:07:26 +0000
Message-ID: <7347100B5761DC41A166AC17F22DF1121B4A0CEF@eusaamb103.ericsson.se>
References: <7347100B5761DC41A166AC17F22DF1121B4A0754@eusaamb103.ericsson.se> <07F7D7DED63154409F13298786A2ADC904D6D57C@EXRAD5.ad.rad.co.il>, <7347100B5761DC41A166AC17F22DF1121B4A0CB9@eusaamb103.ericsson.se> <DDB3D38B-6FE8-4A4A-A604-56AB9181C5FE@broadcom.com>
In-Reply-To: <DDB3D38B-6FE8-4A4A-A604-56AB9181C5FE@broadcom.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [147.117.188.134]
Content-Type: multipart/alternative; boundary="_000_7347100B5761DC41A166AC17F22DF1121B4A0CEFeusaamb103erics_"
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFprAIsWRmVeSWpSXmKPExsUyuXRPgq4D66ZAgwdfRCz2XM6wWN/raXH3 80smizn37rFa3N70lNXib3MPu8WHrh+sDuwerc/2snrMun+WzWPK742sHkuW/GTymLQ2LYA1 itsmKbGkLDgzPU/fLoE748v8GywF10sqenZmNDA2p3UxcnJICJhIvFrYxgRhi0lcuLeerYuR i0NI4CijxKFH16CcZYwSa6Y/YgWpYhMwknixsYcdxBYR0JA4eOsKM0gRs8BEJokri6eAFQkL mEq8uXeTBaLITOLhs81QtpvEgQW/wZpZBFQkrrw/BFbPK+ArMXtdIzvEtjYmiWWPD4MVcQo4 SMy7cxusiBHovu+n1oDdyiwgLnHryXyouwUkluw5zwxhi0q8fPyPFcJWlljyZD/QYg6g+nyJ 7qYAiF2CEidnPmGZwCg6C8mkWQhVs5BUQZToSCzY/YkNwtaWWLbwNTOMfebAYyZk8QWM7KsY OUqLU8ty040MNzECI/SYBJvjDsYFnywPMUpzsCiJ8+rwLg4UEkhPLEnNTk0tSC2KLyrNSS0+ xMjEwQkiuKQaGNU+3Qls3vK+2mNugnfM+gf6OaY7Jvc1bO86PcPebov5UreeyLtZPF8m/PjR f2jF6uzt0eXWDpma80NrFKQnvjyQXr3bOry/9Pz7y8XzFbJDD/3yNDnQLsD8SPrXORNrK78l Oew/Dj13+n4/++WSyquPtt3R28sgOfPWmY0PHXonhx79V8Y2V06JpTgj0VCLuag4EQBO3Dej owIAAA==
Cc: "tictoc@ietf.org" <tictoc@ietf.org>
Subject: Re: [TICTOC] NTP in draft-ietf-tictoc-1588overmpls-04
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, 07 Jun 2013 16:07:42 -0000

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

Hi Shahram,
and hence are my questions:

  *
Is proposed mechanism required to transport other timing protocols over MPL=
S network
  *
Is use of PTP LSP to transport NTP messages justified or not

    Regards,
        Greg

________________________________
From: Shahram Davari [mailto:davari@broadcom.com]
Sent: Friday, June 07, 2013 9:01 AM
To: Gregory Mirsky
Cc: Yaakov Stein; Amit Oren; Bhatia, Manav (Manav); Roberts, Peter (Peter);=
 lmontini@cisco.com; tictoc@ietf.org
Subject: Re: NTP in draft-ietf-tictoc-1588overmpls-04

Greg,

This draft was originally only for PTP, however our Area Director asked the=
 draft to be made more generic so that it can apply to any timing protocol.

Regards,
Shahram


On Jun 7, 2013, at 8:28 AM, "Gregory Mirsky" <gregory.mirsky@ericsson.com<m=
ailto:gregory.mirsky@ericsson.com>> wrote:

Yaakov,
I'm rather sceptical of using "If you build it, he will come" as protocol d=
evelopment guiding principle. Personally I prefer KISS.

    Regards,
        Greg

________________________________
From: Yaakov Stein [mailto:yaakov_s@rad.com]
Sent: Friday, June 07, 2013 7:55 AM
To: Gregory Mirsky; Shahram Davari; amito@broadcom.com<mailto:amito@broadco=
m.com>; Bhatia, Manav (Manav); Roberts, Peter (Peter); lmontini@cisco.com<m=
ailto:lmontini@cisco.com>; tictoc@ietf.org<mailto:tictoc@ietf.org>
Subject: RE: NTP in draft-ietf-tictoc-1588overmpls-04

Greg
This version makes the mechanism more general so that in future other time-=
sensitive protocols
(NTP, delay measurement OAM, generic header for MPLS) could avail themselve=
s of its timestamping/correction features.
It is true that the only real case so far is 1588.
Y(J)S
From: tictoc-bounces@ietf.org<mailto:tictoc-bounces@ietf.org> [mailto:ticto=
c-bounces@ietf.org] On Behalf Of Gregory Mirsky
Sent: 06 June, 2013 21:23
To: Shahram Davari; amito@broadcom.com<mailto:amito@broadcom.com>; Bhatia, =
Manav (Manav); Roberts, Peter (Peter); lmontini@cisco.com<mailto:lmontini@c=
isco.com>; tictoc@ietf.org<mailto:tictoc@ietf.org>
Subject: [TICTOC] NTP in draft-ietf-tictoc-1588overmpls-04
Dear Authors, et al.,
The draft-ietf-tictoc-1588overmpls-04 is currently titled as "Transporting =
Timing messages over MPLS Networks" and states that both timing synchroniza=
tion protocols, PTP and NTP, require use of PTP LSP to transport timing mes=
sages over an MPLS network. After reading RFC 5905 I am not sure that PTP L=
SP, with its constraints and additional complexity, is required to transpor=
t NTPv4 messages over an MPLS network. And first paragraph in Section 3 Pro=
blem Statement of draft-ietf-tictoc-1588overmpls-04 explains motivation for=
 the PTP as
"There is a need to transport Timing messages over MPLS networks while supp=
orting the Transparent Clock (TC), Boundary Clock (BC) and Ordinary Clock (=
OC) functionality in the LER and LSRs in the MPLS network."
but says nothing of a kind about NTP.
        Regards,
                Greg

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

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
<meta content=3D"MSHTML 6.00.6002.18823" name=3D"GENERATOR">
</head>
<body dir=3D"auto">
<div dir=3D"ltr" align=3D"left"><span class=3D"890560116-07062013"><font fa=
ce=3D"Arial" color=3D"#0000ff" size=3D"2">Hi Shahram,</font></span></div>
<div dir=3D"ltr" align=3D"left"><span class=3D"890560116-07062013"><font fa=
ce=3D"Arial" color=3D"#0000ff" size=3D"2">and hence&nbsp;are my questions:<=
/font></span></div>
<ul dir=3D"ltr">
<li>
<div align=3D"left"><span class=3D"890560116-07062013"><font face=3D"Arial"=
 color=3D"#0000ff" size=3D"2">Is proposed mechanism required to transport o=
ther timing protocols over MPLS network</font></span></div>
</li><li>
<div align=3D"left"><span class=3D"890560116-07062013"><font face=3D"Arial"=
 color=3D"#0000ff" size=3D"2">Is use of PTP LSP to transport NTP messages j=
ustified or not</font></span></div>
</li></ul>
<div dir=3D"ltr" align=3D"left"><span class=3D"890560116-07062013">&nbsp;&n=
bsp;&nbsp; <font face=3D"Arial" color=3D"#0000ff" size=3D"2">
Regards,</font></span></div>
<div dir=3D"ltr" align=3D"left"><span class=3D"890560116-07062013">&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <font face=3D"Arial" color=3D"#0000ff" s=
ize=3D"2">
Greg</font></span></div>
<br>
<div class=3D"OutlookMessageHeader" lang=3D"en-us" dir=3D"ltr" align=3D"lef=
t">
<hr tabindex=3D"-1">
<font face=3D"Tahoma" size=3D"2"><b>From:</b> Shahram Davari [mailto:davari=
@broadcom.com]
<br>
<b>Sent:</b> Friday, June 07, 2013 9:01 AM<br>
<b>To:</b> Gregory Mirsky<br>
<b>Cc:</b> Yaakov Stein; Amit Oren; Bhatia, Manav (Manav); Roberts, Peter (=
Peter); lmontini@cisco.com; tictoc@ietf.org<br>
<b>Subject:</b> Re: NTP in draft-ietf-tictoc-1588overmpls-04<br>
</font><br>
</div>
<div></div>
<div>Greg,</div>
<div><br>
</div>
<div>This draft was originally only for PTP, however our Area Director aske=
d the draft to be made more generic so that it can apply to any timing prot=
ocol.<br>
<br>
Regards,
<div>Shahram</div>
<div><br>
</div>
</div>
<div><br>
On Jun 7, 2013, at 8:28 AM, &quot;Gregory Mirsky&quot; &lt;<a href=3D"mailt=
o:gregory.mirsky@ericsson.com">gregory.mirsky@ericsson.com</a>&gt; wrote:<b=
r>
<br>
</div>
<blockquote type=3D"cite">
<div>
<meta content=3D"MSHTML 6.00.6002.18823" name=3D"GENERATOR">
<style>@font-face {
	font-family: Cambria Math;
}
@font-face {
	font-family: Calibri;
}
@font-face {
	font-family: Tahoma;
}
@page WordSection1 {size: 8.5in 11.0in; margin: 1.0in 1.25in 1.0in 1.25in; =
}
P.MsoNormal {
	FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman","seri=
f"
}
LI.MsoNormal {
	FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman","seri=
f"
}
DIV.MsoNormal {
	FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman","seri=
f"
}
A:link {
	COLOR: blue; TEXT-DECORATION: underline; mso-style-priority: 99
}
SPAN.MsoHyperlink {
	COLOR: blue; TEXT-DECORATION: underline; mso-style-priority: 99
}
A:visited {
	COLOR: purple; TEXT-DECORATION: underline; mso-style-priority: 99
}
SPAN.MsoHyperlinkFollowed {
	COLOR: purple; TEXT-DECORATION: underline; mso-style-priority: 99
}
P.emailquote {
	BORDER-RIGHT: medium none; PADDING-RIGHT: 0in; BORDER-TOP: medium none; PA=
DDING-LEFT: 0in; FONT-SIZE: 12pt; PADDING-BOTTOM: 0in; MARGIN-LEFT: 1pt; BO=
RDER-LEFT: medium none; MARGIN-RIGHT: 0in; PADDING-TOP: 0in; BORDER-BOTTOM:=
 medium none; FONT-FAMILY: "Times New Roman","serif"; mso-style-name: email=
quote; mso-margin-top-alt: auto; mso-margin-bottom-alt: auto
}
LI.emailquote {
	BORDER-RIGHT: medium none; PADDING-RIGHT: 0in; BORDER-TOP: medium none; PA=
DDING-LEFT: 0in; FONT-SIZE: 12pt; PADDING-BOTTOM: 0in; MARGIN-LEFT: 1pt; BO=
RDER-LEFT: medium none; MARGIN-RIGHT: 0in; PADDING-TOP: 0in; BORDER-BOTTOM:=
 medium none; FONT-FAMILY: "Times New Roman","serif"; mso-style-name: email=
quote; mso-margin-top-alt: auto; mso-margin-bottom-alt: auto
}
DIV.emailquote {
	BORDER-RIGHT: medium none; PADDING-RIGHT: 0in; BORDER-TOP: medium none; PA=
DDING-LEFT: 0in; FONT-SIZE: 12pt; PADDING-BOTTOM: 0in; MARGIN-LEFT: 1pt; BO=
RDER-LEFT: medium none; MARGIN-RIGHT: 0in; PADDING-TOP: 0in; BORDER-BOTTOM:=
 medium none; FONT-FAMILY: "Times New Roman","serif"; mso-style-name: email=
quote; mso-margin-top-alt: auto; mso-margin-bottom-alt: auto
}
SPAN.EmailStyle18 {
	COLOR: #1f497d; FONT-FAMILY: "Calibri","sans-serif"; mso-style-type: perso=
nal-reply
}
.MsoChpDefault {
	FONT-SIZE: 10pt; mso-style-type: export-only
}
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]-->
<div dir=3D"ltr" align=3D"left"><span class=3D"070062615-07062013"><font fa=
ce=3D"Arial" color=3D"#0000ff" size=3D"2">Yaakov,</font></span></div>
<div dir=3D"ltr" align=3D"left"><span class=3D"070062615-07062013"><font fa=
ce=3D"Arial"><font size=3D"2"><font color=3D"#0000ff">I'm rather sceptical =
of using &quot;<span class=3D"st">If you build it, he will come&quot; as pr=
otocol development guiding principle. Personally I prefer
 KISS.</span></font></font></font></span></div>
<div dir=3D"ltr" align=3D"left"><span class=3D"070062615-07062013"><font fa=
ce=3D"Arial"><font size=3D"2"><font color=3D"#0000ff"><span class=3D"st"></=
span></font></font></font></span>&nbsp;</div>
<div dir=3D"ltr" align=3D"left"><span class=3D"070062615-07062013"><font fa=
ce=3D"Arial"><font size=3D"2"><font color=3D"#0000ff"><span class=3D"st">&n=
bsp;&nbsp;&nbsp; Regards,</span></font></font></font></span></div>
<div dir=3D"ltr" align=3D"left"><span class=3D"070062615-07062013"><font fa=
ce=3D"Arial"><font size=3D"2"><font color=3D"#0000ff"><span class=3D"st">&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Greg</span></font></font></font></=
span></div>
<br>
<div class=3D"OutlookMessageHeader" lang=3D"en-us" dir=3D"ltr" align=3D"lef=
t">
<hr tabindex=3D"-1">
<font face=3D"Tahoma" size=3D"2"><b>From:</b> Yaakov Stein [<a href=3D"mail=
to:yaakov_s@rad.com">mailto:yaakov_s@rad.com</a>]
<br>
<b>Sent:</b> Friday, June 07, 2013 7:55 AM<br>
<b>To:</b> Gregory Mirsky; Shahram Davari; <a href=3D"mailto:amito@broadcom=
.com">amito@broadcom.com</a>; Bhatia, Manav (Manav); Roberts, Peter (Peter)=
;
<a href=3D"mailto:lmontini@cisco.com">lmontini@cisco.com</a>; <a href=3D"ma=
ilto:tictoc@ietf.org">
tictoc@ietf.org</a><br>
<b>Subject:</b> RE: NTP in draft-ietf-tictoc-1588overmpls-04<br>
</font><br>
</div>
<div></div>
<div class=3D"WordSection1">
<p class=3D"MsoNormal"><span style=3D"FONT-SIZE: 11pt; COLOR: #1f497d; FONT=
-FAMILY: 'Calibri','sans-serif'">Greg<O:P></O:P></span></p>
<p class=3D"MsoNormal"><span style=3D"FONT-SIZE: 11pt; COLOR: #1f497d; FONT=
-FAMILY: 'Calibri','sans-serif'"><O:P></O:P></span></p>
<p class=3D"MsoNormal"><span style=3D"FONT-SIZE: 11pt; COLOR: #1f497d; FONT=
-FAMILY: 'Calibri','sans-serif'">This version makes the mechanism more gene=
ral so that in future other time-sensitive protocols<O:P></O:P></span></p>
<p class=3D"MsoNormal"><span style=3D"FONT-SIZE: 11pt; COLOR: #1f497d; FONT=
-FAMILY: 'Calibri','sans-serif'">(NTP, delay measurement OAM, generic heade=
r for MPLS) could avail themselves of its timestamping/correction features.=
<O:P></O:P></span></p>
<p class=3D"MsoNormal"><span style=3D"FONT-SIZE: 11pt; COLOR: #1f497d; FONT=
-FAMILY: 'Calibri','sans-serif'"><O:P></O:P></span></p>
<p class=3D"MsoNormal"><span style=3D"FONT-SIZE: 11pt; COLOR: #1f497d; FONT=
-FAMILY: 'Calibri','sans-serif'">It is true that the only real case so far =
is 1588.<O:P></O:P></span></p>
<p class=3D"MsoNormal"><span style=3D"FONT-SIZE: 11pt; COLOR: #1f497d; FONT=
-FAMILY: 'Calibri','sans-serif'"><O:P></O:P></span></p>
<p class=3D"MsoNormal"><span style=3D"FONT-SIZE: 11pt; COLOR: #1f497d; FONT=
-FAMILY: 'Calibri','sans-serif'">Y(J)S<O:P></O:P></span></p>
<p class=3D"MsoNormal"><span style=3D"FONT-SIZE: 11pt; COLOR: #1f497d; FONT=
-FAMILY: 'Calibri','sans-serif'"><O:P></O:P></span></p>
<div>
<div style=3D"BORDER-RIGHT: medium none; PADDING-RIGHT: 0in; BORDER-TOP: #b=
5c4df 1pt solid; PADDING-LEFT: 0in; PADDING-BOTTOM: 0in; BORDER-LEFT: mediu=
m none; PADDING-TOP: 3pt; BORDER-BOTTOM: medium none">
<p class=3D"MsoNormal"><b><span style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'Tah=
oma','sans-serif'">From:</span></b><span style=3D"FONT-SIZE: 10pt; FONT-FAM=
ILY: 'Tahoma','sans-serif'">
<a href=3D"mailto:tictoc-bounces@ietf.org">tictoc-bounces@ietf.org</a> [<a =
href=3D"mailto:tictoc-bounces@ietf.org">mailto:tictoc-bounces@ietf.org</a>]
<b>On Behalf Of </b>Gregory Mirsky<br>
<b>Sent:</b> 06 June, 2013 21:23<br>
<b>To:</b> Shahram Davari; <a href=3D"mailto:amito@broadcom.com">amito@broa=
dcom.com</a>; Bhatia, Manav (Manav); Roberts, Peter (Peter);
<a href=3D"mailto:lmontini@cisco.com">lmontini@cisco.com</a>; <a href=3D"ma=
ilto:tictoc@ietf.org">
tictoc@ietf.org</a><br>
<b>Subject:</b> [TICTOC] NTP in draft-ietf-tictoc-1588overmpls-04<O:P></O:P=
></span></p>
</div>
</div>
<p class=3D"MsoNormal"><O:P></O:P></p>
<div>
<p class=3D"MsoNormal"><span style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'Arial'=
,'sans-serif'">Dear Authors, et al.,<O:P></O:P></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'Arial'=
,'sans-serif'">The draft-ietf-tictoc-1588overmpls-04 is currently titled as=
 &quot;Transporting Timing messages over MPLS Networks&quot; and states tha=
t both timing synchronization protocols, PTP and
 NTP, require use of PTP LSP to transport timing messages over an MPLS netw=
ork. After reading RFC 5905 I am not sure that PTP LSP, with its constraint=
s and additional complexity, is required to transport NTPv4 messages over a=
n MPLS network. And first paragraph
 in Section 3 Problem Statement of draft-ietf-tictoc-1588overmpls-04 explai=
ns motivation for the PTP as
<O:P></O:P></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'Arial'=
,'sans-serif'">&quot;There is a need to transport Timing messages over MPLS=
 networks while supporting the Transparent Clock (TC), Boundary Clock (BC) =
and Ordinary Clock (OC) functionality in
 the LER and LSRs in the MPLS network.&quot;<O:P></O:P></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'Arial'=
,'sans-serif'">but says nothing of a kind about NTP.<O:P></O:P></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'Arial'=
,'sans-serif'"><O:P></O:P></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'Arial'=
,'sans-serif'">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Regards,<O:P></O:=
P></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'Arial'=
,'sans-serif'">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Greg<O:P></O:P></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'Arial'=
,'sans-serif'"><O:P></O:P></span></p>
</div>
</div>
</div>
</blockquote>
</body>
</html>

--_000_7347100B5761DC41A166AC17F22DF1121B4A0CEFeusaamb103erics_--

From jdrake@juniper.net  Fri Jun  7 09:11:09 2013
Return-Path: <jdrake@juniper.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 B1B7521F96C6 for <tictoc@ietfa.amsl.com>; Fri,  7 Jun 2013 09:11:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.467
X-Spam-Level: 
X-Spam-Status: No, score=-1.467 tagged_above=-999 required=5 tests=[AWL=-2.001, BAYES_00=-2.599, HTML_MESSAGE=0.001, UNRESOLVED_TEMPLATE=3.132]
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 zuDAc8Magcph for <tictoc@ietfa.amsl.com>; Fri,  7 Jun 2013 09:11:03 -0700 (PDT)
Received: from db8outboundpool.messaging.microsoft.com (mail-db8lp0187.outbound.messaging.microsoft.com [213.199.154.187]) by ietfa.amsl.com (Postfix) with ESMTP id 348F121F963C for <tictoc@ietf.org>; Fri,  7 Jun 2013 09:11:02 -0700 (PDT)
Received: from mail65-db8-R.bigfish.com (10.174.8.229) by DB8EHSOBE001.bigfish.com (10.174.4.64) with Microsoft SMTP Server id 14.1.225.23; Fri, 7 Jun 2013 16:11:01 +0000
Received: from mail65-db8 (localhost [127.0.0.1])	by mail65-db8-R.bigfish.com (Postfix) with ESMTP id 1BEE4BC013E	for <tictoc@ietf.org>; Fri,  7 Jun 2013 16:11:01 +0000 (UTC)
X-Forefront-Antispam-Report: CIP:66.129.224.52; KIP:(null); UIP:(null); IPV:NLI; H:P-EMHUB03-HQ.jnpr.net; RD:none; EFVD:NLI
X-SpamScore: -22
X-BigFish: PS-22(zz98dI9371Ic85fhzz1f42h1ee6h1de0h1fdah1202h1e76h1d1ah1d2ah1fc6hzz1033IL17326ah18c673h1c8fb4h8275bh8275dhz31h2a8h683h839hd25hf0ah1288h12a5h12bdh137ah1441h1504h1537h153bh15d0h162dh1631h1758h18e1h1946h19b5h19ceh1ad9h1b0ah1bceh1d07h1d0ch1d2eh1d3fh1de9h1dfeh1dffh1e1dh1155h)
Received-SPF: softfail (mail65-db8: transitioning domain of juniper.net does not designate 66.129.224.52 as permitted sender) client-ip=66.129.224.52; envelope-from=jdrake@juniper.net; helo=P-EMHUB03-HQ.jnpr.net ; -HQ.jnpr.net ; 
X-Forefront-Antispam-Report-Untrusted: CIP:157.56.240.101; KIP:(null); UIP:(null); (null); H:BL2PRD0510HT001.namprd05.prod.outlook.com; R:internal; EFV:INT
Received: from mail65-db8 (localhost.localdomain [127.0.0.1]) by mail65-db8 (MessageSwitch) id 1370621459400476_7911; Fri,  7 Jun 2013 16:10:59 +0000 (UTC)
Received: from DB8EHSMHS022.bigfish.com (unknown [10.174.8.238])	by mail65-db8.bigfish.com (Postfix) with ESMTP id 5F379B8005B	for <tictoc@ietf.org>; Fri,  7 Jun 2013 16:10:59 +0000 (UTC)
Received: from P-EMHUB03-HQ.jnpr.net (66.129.224.52) by DB8EHSMHS022.bigfish.com (10.174.4.32) with Microsoft SMTP Server (TLS) id 14.1.225.23; Fri, 7 Jun 2013 16:10:58 +0000
Received: from P-CLDFE01-HQ.jnpr.net (172.24.192.59) by P-EMHUB03-HQ.jnpr.net (172.24.192.37) with Microsoft SMTP Server (TLS) id 8.3.213.0; Fri, 7 Jun 2013 09:10:56 -0700
Received: from o365mail.juniper.net (207.17.137.224) by o365mail.juniper.net (172.24.192.59) with Microsoft SMTP Server id 14.1.355.2; Fri, 7 Jun 2013 09:10:56 -0700
Received: from DB8EHSOBE025.bigfish.com (213.199.154.185) by o365mail.juniper.net (207.17.137.224) with Microsoft SMTP Server (TLS) id 14.1.355.2; Fri, 7 Jun 2013 09:22:30 -0700
Received: from mail80-db8-R.bigfish.com (10.174.8.234) by DB8EHSOBE025.bigfish.com (10.174.4.88) with Microsoft SMTP Server id 14.1.225.23; Fri, 7 Jun 2013 16:10:54 +0000
Received: from mail80-db8 (localhost [127.0.0.1])	by mail80-db8-R.bigfish.com (Postfix) with ESMTP id 3FEDA24015B	for <tictoc@ietf.org.FOPE.CONNECTOR.OVERRIDE>; Fri,  7 Jun 2013 16:10:54 +0000 (UTC)
Received: from mail80-db8 (localhost.localdomain [127.0.0.1]) by mail80-db8 (MessageSwitch) id 1370621452235272_679; Fri,  7 Jun 2013 16:10:52 +0000 (UTC)
Received: from DB8EHSMHS008.bigfish.com (unknown [10.174.8.253])	by mail80-db8.bigfish.com (Postfix) with ESMTP id 2D55EAC0053; Fri,  7 Jun 2013 16:10:52 +0000 (UTC)
Received: from BL2PRD0510HT001.namprd05.prod.outlook.com (157.56.240.101) by DB8EHSMHS008.bigfish.com (10.174.4.18) with Microsoft SMTP Server (TLS) id 14.1.225.23; Fri, 7 Jun 2013 16:10:50 +0000
Received: from BL2PRD0510MB349.namprd05.prod.outlook.com ([169.254.1.63]) by BL2PRD0510HT001.namprd05.prod.outlook.com ([10.255.100.36]) with mapi id 14.16.0311.000; Fri, 7 Jun 2013 16:10:45 +0000
From: John E Drake <jdrake@juniper.net>
To: Gregory Mirsky <gregory.mirsky@ericsson.com>, Shahram Davari <davari@broadcom.com>
Thread-Topic: NTP in draft-ietf-tictoc-1588overmpls-04
Thread-Index: Ac5i4ubOrT57JHkXTgC9GUzpraB4EAAq9gQAAAElPiAAATQbzwAADGYgAAA+HtA=
Date: Fri, 7 Jun 2013 16:10:45 +0000
Message-ID: <0182DEA5604B3A44A2EE61F3EE3ED69E1D51BE2D@BL2PRD0510MB349.namprd05.prod.outlook.com>
References: <7347100B5761DC41A166AC17F22DF1121B4A0754@eusaamb103.ericsson.se> <07F7D7DED63154409F13298786A2ADC904D6D57C@EXRAD5.ad.rad.co.il>, <7347100B5761DC41A166AC17F22DF1121B4A0CB9@eusaamb103.ericsson.se> <DDB3D38B-6FE8-4A4A-A604-56AB9181C5FE@broadcom.com> <7347100B5761DC41A166AC17F22DF1121B4A0CEF@eusaamb103.ericsson.se>
In-Reply-To: <7347100B5761DC41A166AC17F22DF1121B4A0CEF@eusaamb103.ericsson.se>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [66.129.224.51]
Content-Type: multipart/alternative; boundary="_000_0182DEA5604B3A44A2EE61F3EE3ED69E1D51BE2DBL2PRD0510MB349_"
MIME-Version: 1.0
X-FOPE-CONNECTOR: Id%0$Dn%*$RO%0$TLS%0$FQDN%$TlsDn%
X-FOPE-CONNECTOR: Id%12219$Dn%ERICSSON.COM$RO%2$TLS%5$FQDN%onpremiseedge-1018244.customer.frontbridge.com$TlsDn%o365mail.juniper.net
X-FOPE-CONNECTOR: Id%12219$Dn%BROADCOM.COM$RO%2$TLS%5$FQDN%onpremiseedge-1018244.customer.frontbridge.com$TlsDn%o365mail.juniper.net
X-FOPE-CONNECTOR: Id%12219$Dn%IETF.ORG$RO%2$TLS%5$FQDN%onpremiseedge-1018244.customer.frontbridge.com$TlsDn%o365mail.juniper.net
X-OriginatorOrg: juniper.net
Cc: "tictoc@ietf.org" <tictoc@ietf.org>
Subject: Re: [TICTOC] NTP in draft-ietf-tictoc-1588overmpls-04
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, 07 Jun 2013 16:11:09 -0000

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

& Do we know to a certainty that the proposed generalizations will support =
all (or any) other current and future timing protocols?

Yours Irrespectively,

John

From: tictoc-bounces@ietf.org [mailto:tictoc-bounces@ietf.org] On Behalf Of=
 Gregory Mirsky
Sent: Friday, June 07, 2013 9:07 AM
To: Shahram Davari
Cc: tictoc@ietf.org
Subject: Re: [TICTOC] NTP in draft-ietf-tictoc-1588overmpls-04

Hi Shahram,
and hence are my questions:

  *   Is proposed mechanism required to transport other timing protocols ov=
er MPLS network
  *   Is use of PTP LSP to transport NTP messages justified or not
    Regards,
        Greg

________________________________
From: Shahram Davari [mailto:davari@broadcom.com]
Sent: Friday, June 07, 2013 9:01 AM
To: Gregory Mirsky
Cc: Yaakov Stein; Amit Oren; Bhatia, Manav (Manav); Roberts, Peter (Peter);=
 lmontini@cisco.com<mailto:lmontini@cisco.com>; tictoc@ietf.org<mailto:tict=
oc@ietf.org>
Subject: Re: NTP in draft-ietf-tictoc-1588overmpls-04
Greg,

This draft was originally only for PTP, however our Area Director asked the=
 draft to be made more generic so that it can apply to any timing protocol.

Regards,
Shahram


On Jun 7, 2013, at 8:28 AM, "Gregory Mirsky" <gregory.mirsky@ericsson.com<m=
ailto:gregory.mirsky@ericsson.com>> wrote:
Yaakov,
I'm rather sceptical of using "If you build it, he will come" as protocol d=
evelopment guiding principle. Personally I prefer KISS.

    Regards,
        Greg

________________________________
From: Yaakov Stein [mailto:yaakov_s@rad.com]
Sent: Friday, June 07, 2013 7:55 AM
To: Gregory Mirsky; Shahram Davari; amito@broadcom.com<mailto:amito@broadco=
m.com>; Bhatia, Manav (Manav); Roberts, Peter (Peter); lmontini@cisco.com<m=
ailto:lmontini@cisco.com>; tictoc@ietf.org<mailto:tictoc@ietf.org>
Subject: RE: NTP in draft-ietf-tictoc-1588overmpls-04
Greg
This version makes the mechanism more general so that in future other time-=
sensitive protocols
(NTP, delay measurement OAM, generic header for MPLS) could avail themselve=
s of its timestamping/correction features.
It is true that the only real case so far is 1588.
Y(J)S
From: tictoc-bounces@ietf.org<mailto:tictoc-bounces@ietf.org> [mailto:ticto=
c-bounces@ietf.org] On Behalf Of Gregory Mirsky
Sent: 06 June, 2013 21:23
To: Shahram Davari; amito@broadcom.com<mailto:amito@broadcom.com>; Bhatia, =
Manav (Manav); Roberts, Peter (Peter); lmontini@cisco.com<mailto:lmontini@c=
isco.com>; tictoc@ietf.org<mailto:tictoc@ietf.org>
Subject: [TICTOC] NTP in draft-ietf-tictoc-1588overmpls-04
Dear Authors, et al.,
The draft-ietf-tictoc-1588overmpls-04 is currently titled as "Transporting =
Timing messages over MPLS Networks" and states that both timing synchroniza=
tion protocols, PTP and NTP, require use of PTP LSP to transport timing mes=
sages over an MPLS network. After reading RFC 5905 I am not sure that PTP L=
SP, with its constraints and additional complexity, is required to transpor=
t NTPv4 messages over an MPLS network. And first paragraph in Section 3 Pro=
blem Statement of draft-ietf-tictoc-1588overmpls-04 explains motivation for=
 the PTP as
"There is a need to transport Timing messages over MPLS networks while supp=
orting the Transparent Clock (TC), Boundary Clock (BC) and Ordinary Clock (=
OC) functionality in the LER and LSRs in the MPLS network."
but says nothing of a kind about NTP.
        Regards,
                Greg

--_000_0182DEA5604B3A44A2EE61F3EE3ED69E1D51BE2DBL2PRD0510MB349_
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 12 (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:Wingdings;
	panose-1:5 0 0 0 0 0 0 0 0 0;}
@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";}
p.emailquote, li.emailquote, div.emailquote
	{mso-style-name:emailquote;
	mso-margin-top-alt:auto;
	margin-right:0in;
	mso-margin-bottom-alt:auto;
	margin-left:1.0pt;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";}
span.EmailStyle18
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
span.st
	{mso-style-name:st;}
span.BalloonTextChar
	{mso-style-name:"Balloon Text Char";
	mso-style-priority:99;
	mso-style-link:"Balloon Text";
	font-family:"Tahoma","sans-serif";}
span.EmailStyle22
	{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;}
/* List Definitions */
@list l0
	{mso-list-id:1742019803;
	mso-list-template-ids:-458480706;}
@list l0:level1
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:.5in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:Symbol;}
ol
	{margin-bottom:0in;}
ul
	{margin-bottom:0in;}
--></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">&amp; Do we know to a cer=
tainty that the proposed generalizations will support all (or any) other cu=
rrent and future timing protocols?<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>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">Yours Irrespectively,<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=
>
</div>
<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-left:solid blue 1.5pt;padding:0in 0in 0in =
4.0pt">
<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;"> tictoc-b=
ounces@ietf.org [mailto:tictoc-bounces@ietf.org]
<b>On Behalf Of </b>Gregory Mirsky<br>
<b>Sent:</b> Friday, June 07, 2013 9:07 AM<br>
<b>To:</b> Shahram Davari<br>
<b>Cc:</b> tictoc@ietf.org<br>
<b>Subject:</b> Re: [TICTOC] NTP in draft-ietf-tictoc-1588overmpls-04<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:10.0pt;font-family:&quot;Ar=
ial&quot;,&quot;sans-serif&quot;;color:blue">Hi Shahram,</span><o:p></o:p><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Ar=
ial&quot;,&quot;sans-serif&quot;;color:blue">and hence&nbsp;are my question=
s:</span><o:p></o:p></p>
<ul type=3D"disc">
<li class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-=
alt:auto;mso-list:l0 level1 lfo1">
<span style=3D"font-size:10.0pt;font-family:&quot;Arial&quot;,&quot;sans-se=
rif&quot;;color:blue">Is proposed mechanism required to transport other tim=
ing protocols over MPLS network</span><o:p></o:p></li><li class=3D"MsoNorma=
l" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l0 =
level1 lfo1">
<span style=3D"font-size:10.0pt;font-family:&quot;Arial&quot;,&quot;sans-se=
rif&quot;;color:blue">Is use of PTP LSP to transport NTP messages justified=
 or not</span><o:p></o:p></li></ul>
<p class=3D"MsoNormal">&nbsp;&nbsp;&nbsp; <span style=3D"font-size:10.0pt;f=
ont-family:&quot;Arial&quot;,&quot;sans-serif&quot;;color:blue">
Regards,</span><o:p></o:p></p>
<p class=3D"MsoNormal">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <span sty=
le=3D"font-size:10.0pt;font-family:&quot;Arial&quot;,&quot;sans-serif&quot;=
;color:blue">
Greg</span><o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<div class=3D"MsoNormal" align=3D"center" style=3D"text-align:center">
<hr size=3D"2" width=3D"100%" align=3D"center">
</div>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt"><b><span style=3D"fon=
t-size:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;">From:<=
/span></b><span style=3D"font-size:10.0pt;font-family:&quot;Tahoma&quot;,&q=
uot;sans-serif&quot;"> Shahram Davari [<a href=3D"mailto:davari@broadcom.co=
m">mailto:davari@broadcom.com</a>]
<br>
<b>Sent:</b> Friday, June 07, 2013 9:01 AM<br>
<b>To:</b> Gregory Mirsky<br>
<b>Cc:</b> Yaakov Stein; Amit Oren; Bhatia, Manav (Manav); Roberts, Peter (=
Peter);
<a href=3D"mailto:lmontini@cisco.com">lmontini@cisco.com</a>; <a href=3D"ma=
ilto:tictoc@ietf.org">
tictoc@ietf.org</a><br>
<b>Subject:</b> Re: NTP in draft-ietf-tictoc-1588overmpls-04</span><o:p></o=
:p></p>
<div>
<p class=3D"MsoNormal">Greg,<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<div>
<p class=3D"MsoNormal">This draft was originally only for PTP, however our =
Area Director asked the draft to be made more generic so that it can apply =
to any timing protocol.<br>
<br>
Regards, <o:p></o:p></p>
<div>
<p class=3D"MsoNormal">Shahram<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt"><br>
On Jun 7, 2013, at 8:28 AM, &quot;Gregory Mirsky&quot; &lt;<a href=3D"mailt=
o:gregory.mirsky@ericsson.com">gregory.mirsky@ericsson.com</a>&gt; wrote:<o=
:p></o:p></p>
</div>
<blockquote style=3D"margin-top:5.0pt;margin-bottom:5.0pt">
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Ar=
ial&quot;,&quot;sans-serif&quot;;color:blue">Yaakov,</span><o:p></o:p></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Ar=
ial&quot;,&quot;sans-serif&quot;;color:blue">I'm rather sceptical of using =
&quot;<span class=3D"st">If you build it, he will come&quot; as protocol de=
velopment guiding principle. Personally I prefer KISS.</span></span><o:p></=
o:p></p>
<p class=3D"MsoNormal">&nbsp;<o:p></o:p></p>
<p class=3D"MsoNormal"><span class=3D"st"><span style=3D"font-size:10.0pt;f=
ont-family:&quot;Arial&quot;,&quot;sans-serif&quot;;color:blue">&nbsp;&nbsp=
;&nbsp; Regards,</span></span><o:p></o:p></p>
<p class=3D"MsoNormal"><span class=3D"st"><span style=3D"font-size:10.0pt;f=
ont-family:&quot;Arial&quot;,&quot;sans-serif&quot;;color:blue">&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Greg</span></span><o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<div class=3D"MsoNormal" align=3D"center" style=3D"text-align:center">
<hr size=3D"2" width=3D"100%" align=3D"center">
</div>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt"><b><span style=3D"fon=
t-size:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;">From:<=
/span></b><span style=3D"font-size:10.0pt;font-family:&quot;Tahoma&quot;,&q=
uot;sans-serif&quot;"> Yaakov Stein [<a href=3D"mailto:yaakov_s@rad.com">ma=
ilto:yaakov_s@rad.com</a>]
<br>
<b>Sent:</b> Friday, June 07, 2013 7:55 AM<br>
<b>To:</b> Gregory Mirsky; Shahram Davari; <a href=3D"mailto:amito@broadcom=
.com">amito@broadcom.com</a>; Bhatia, Manav (Manav); Roberts, Peter (Peter)=
;
<a href=3D"mailto:lmontini@cisco.com">lmontini@cisco.com</a>; <a href=3D"ma=
ilto:tictoc@ietf.org">
tictoc@ietf.org</a><br>
<b>Subject:</b> RE: NTP in draft-ietf-tictoc-1588overmpls-04</span><o:p></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">Greg</span><o:p></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">This version makes the me=
chanism more general so that in future other time-sensitive protocols</span=
><o:p></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">(NTP, delay measurement O=
AM, generic header for MPLS) could avail themselves of its timestamping/cor=
rection features.</span><o:p></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">It is true that the only =
real case so far is 1588.</span><o:p></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">Y(J)S</span><o:p></o:p></=
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;">
<a href=3D"mailto:tictoc-bounces@ietf.org">tictoc-bounces@ietf.org</a> [<a =
href=3D"mailto:tictoc-bounces@ietf.org">mailto:tictoc-bounces@ietf.org</a>]
<b>On Behalf Of </b>Gregory Mirsky<br>
<b>Sent:</b> 06 June, 2013 21:23<br>
<b>To:</b> Shahram Davari; <a href=3D"mailto:amito@broadcom.com">amito@broa=
dcom.com</a>; Bhatia, Manav (Manav); Roberts, Peter (Peter);
<a href=3D"mailto:lmontini@cisco.com">lmontini@cisco.com</a>; <a href=3D"ma=
ilto:tictoc@ietf.org">
tictoc@ietf.org</a><br>
<b>Subject:</b> [TICTOC] NTP in draft-ietf-tictoc-1588overmpls-04</span><o:=
p></o:p></p>
</div>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Ar=
ial&quot;,&quot;sans-serif&quot;">Dear Authors, et al.,</span><o:p></o:p></=
p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Ar=
ial&quot;,&quot;sans-serif&quot;">The draft-ietf-tictoc-1588overmpls-04 is =
currently titled as &quot;Transporting Timing messages over MPLS Networks&q=
uot; and states that both timing synchronization protocols, PTP and
 NTP, require use of PTP LSP to transport timing messages over an MPLS netw=
ork. After reading RFC 5905 I am not sure that PTP LSP, with its constraint=
s and additional complexity, is required to transport NTPv4 messages over a=
n MPLS network. And first paragraph
 in Section 3 Problem Statement of draft-ietf-tictoc-1588overmpls-04 explai=
ns motivation for the PTP as
</span><o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Ar=
ial&quot;,&quot;sans-serif&quot;">&quot;There is a need to transport Timing=
 messages over MPLS networks while supporting the Transparent Clock (TC), B=
oundary Clock (BC) and Ordinary Clock (OC) functionality in the
 LER and LSRs in the MPLS network.&quot;</span><o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Ar=
ial&quot;,&quot;sans-serif&quot;">but says nothing of a kind about NTP.</sp=
an><o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Ar=
ial&quot;,&quot;sans-serif&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
; Regards,</span><o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Ar=
ial&quot;,&quot;sans-serif&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Greg</span><o:p></o:p></p=
>
</div>
</div>
</blockquote>
</div>
</div>
</body>
</html>

--_000_0182DEA5604B3A44A2EE61F3EE3ED69E1D51BE2DBL2PRD0510MB349_--

From davari@broadcom.com  Fri Jun  7 09:25:19 2013
Return-Path: <davari@broadcom.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 3547B21F8FA4 for <tictoc@ietfa.amsl.com>; Fri,  7 Jun 2013 09:25:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.598
X-Spam-Level: 
X-Spam-Status: No, score=-6.598 tagged_above=-999 required=5 tests=[AWL=-0.000, BAYES_00=-2.599, 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 GkyxlzbImAV1 for <tictoc@ietfa.amsl.com>; Fri,  7 Jun 2013 09:25:14 -0700 (PDT)
Received: from mms2.broadcom.com (mms2.broadcom.com [216.31.210.18]) by ietfa.amsl.com (Postfix) with ESMTP id A580021F9923 for <tictoc@ietf.org>; Fri,  7 Jun 2013 09:25:08 -0700 (PDT)
Received: from [10.9.208.53] by mms2.broadcom.com with ESMTP (Broadcom SMTP Relay (Email Firewall v6.5)); Fri, 07 Jun 2013 09:19:17 -0700
X-Server-Uuid: 4500596E-606A-40F9-852D-14843D8201B2
Received: from SJEXCHCAS04.corp.ad.broadcom.com (10.16.203.10) by IRVEXCHCAS06.corp.ad.broadcom.com (10.9.208.53) with Microsoft SMTP Server (TLS) id 14.1.438.0; Fri, 7 Jun 2013 09:24:33 -0700
Received: from SJEXCHMB12.corp.ad.broadcom.com ( [fe80::bc15:c1e1:c29a:36f7]) by SJEXCHCAS04.corp.ad.broadcom.com ( [::1]) with mapi id 14.01.0438.000; Fri, 7 Jun 2013 09:24:33 -0700
From: "Shahram Davari" <davari@broadcom.com>
To: "Gregory Mirsky" <gregory.mirsky@ericsson.com>
Thread-Topic: NTP in draft-ietf-tictoc-1588overmpls-04
Thread-Index: Ac5i4ubOrT57JHkXTgC9GUzpraB4EAAq9gQAAAElPiAAATQbzwAADGYgAADKEKE=
Date: Fri, 7 Jun 2013 16:24:32 +0000
Message-ID: <213EA834-02B4-4ABE-B7A1-C25F3CE68B2E@broadcom.com>
References: <7347100B5761DC41A166AC17F22DF1121B4A0754@eusaamb103.ericsson.se> <07F7D7DED63154409F13298786A2ADC904D6D57C@EXRAD5.ad.rad.co.il>, <7347100B5761DC41A166AC17F22DF1121B4A0CB9@eusaamb103.ericsson.se> <DDB3D38B-6FE8-4A4A-A604-56AB9181C5FE@broadcom.com>, <7347100B5761DC41A166AC17F22DF1121B4A0CEF@eusaamb103.ericsson.se>
In-Reply-To: <7347100B5761DC41A166AC17F22DF1121B4A0CEF@eusaamb103.ericsson.se>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
MIME-Version: 1.0
X-WSS-ID: 7DACD78E1R028001439-15-01
Content-Type: multipart/alternative; boundary=_000_213EA83402B44ABEB7A1C25F3CE68B2Ebroadcomcom_
Cc: "tictoc@ietf.org" <tictoc@ietf.org>
Subject: Re: [TICTOC] NTP in draft-ietf-tictoc-1588overmpls-04
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, 07 Jun 2013 16:25:19 -0000

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

For NTP, It is not required to use this draft for transporting it over MPLS=
. Since NTP has not yet defined Transparent Clock, and  NTP accuracy as of =
now is low and does not require time stamping  in Hardware.

Regards,
Shahram


On Jun 7, 2013, at 9:08 AM, "Gregory Mirsky" <gregory.mirsky@ericsson.com<m=
ailto:gregory.mirsky@ericsson.com>> wrote:

Hi Shahram,
and hence are my questions:

  *
Is proposed mechanism required to transport other timing protocols over MPL=
S network
  *
Is use of PTP LSP to transport NTP messages justified or not

    Regards,
        Greg

________________________________
From: Shahram Davari [mailto:davari@broadcom.com]
Sent: Friday, June 07, 2013 9:01 AM
To: Gregory Mirsky
Cc: Yaakov Stein; Amit Oren; Bhatia, Manav (Manav); Roberts, Peter (Peter);=
 lmontini@cisco.com<mailto:lmontini@cisco.com>; tictoc@ietf.org<mailto:tict=
oc@ietf.org>
Subject: Re: NTP in draft-ietf-tictoc-1588overmpls-04

Greg,

This draft was originally only for PTP, however our Area Director asked the=
 draft to be made more generic so that it can apply to any timing protocol.

Regards,
Shahram


On Jun 7, 2013, at 8:28 AM, "Gregory Mirsky" <gregory.mirsky@ericsson.com<m=
ailto:gregory.mirsky@ericsson.com>> wrote:

Yaakov,
I'm rather sceptical of using "If you build it, he will come" as protocol d=
evelopment guiding principle. Personally I prefer KISS.

    Regards,
        Greg

________________________________
From: Yaakov Stein [mailto:yaakov_s@rad.com]
Sent: Friday, June 07, 2013 7:55 AM
To: Gregory Mirsky; Shahram Davari; amito@broadcom.com<mailto:amito@broadco=
m.com>; Bhatia, Manav (Manav); Roberts, Peter (Peter); lmontini@cisco.com<m=
ailto:lmontini@cisco.com>; tictoc@ietf.org<mailto:tictoc@ietf.org>
Subject: RE: NTP in draft-ietf-tictoc-1588overmpls-04

Greg
This version makes the mechanism more general so that in future other time-=
sensitive protocols
(NTP, delay measurement OAM, generic header for MPLS) could avail themselve=
s of its timestamping/correction features.
It is true that the only real case so far is 1588.
Y(J)S
From: tictoc-bounces@ietf.org<mailto:tictoc-bounces@ietf.org> [mailto:ticto=
c-bounces@ietf.org] On Behalf Of Gregory Mirsky
Sent: 06 June, 2013 21:23
To: Shahram Davari; amito@broadcom.com<mailto:amito@broadcom.com>; Bhatia, =
Manav (Manav); Roberts, Peter (Peter); lmontini@cisco.com<mailto:lmontini@c=
isco.com>; tictoc@ietf.org<mailto:tictoc@ietf.org>
Subject: [TICTOC] NTP in draft-ietf-tictoc-1588overmpls-04
Dear Authors, et al.,
The draft-ietf-tictoc-1588overmpls-04 is currently titled as "Transporting =
Timing messages over MPLS Networks" and states that both timing synchroniza=
tion protocols, PTP and NTP, require use of PTP LSP to transport timing mes=
sages over an MPLS network. After reading RFC 5905 I am not sure that PTP L=
SP, with its constraints and additional complexity, is required to transpor=
t NTPv4 messages over an MPLS network. And first paragraph in Section 3 Pro=
blem Statement of draft-ietf-tictoc-1588overmpls-04 explains motivation for=
 the PTP as
"There is a need to transport Timing messages over MPLS networks while supp=
orting the Transparent Clock (TC), Boundary Clock (BC) and Ordinary Clock (=
OC) functionality in the LER and LSRs in the MPLS network."
but says nothing of a kind about NTP.
        Regards,
                Greg

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

<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
</head>
<body dir=3D"auto">
<div>For NTP, It is not required to use this draft for transporting it over=
 MPLS. Since NTP has not yet defined Transparent Clock, and &nbsp;NTP accur=
acy as of now is low and does not require time stamping &nbsp;in Hardware.<=
br>
<br>
Regards,
<div>Shahram</div>
<div><br>
</div>
</div>
<div><br>
On Jun 7, 2013, at 9:08 AM, &quot;Gregory Mirsky&quot; &lt;<a href=3D"mailt=
o:gregory.mirsky@ericsson.com">gregory.mirsky@ericsson.com</a>&gt; wrote:<b=
r>
<br>
</div>
<blockquote type=3D"cite">
<div>
<meta content=3D"MSHTML 6.00.6002.18823" name=3D"GENERATOR">
<div dir=3D"ltr" align=3D"left"><span class=3D"890560116-07062013"><font fa=
ce=3D"Arial" color=3D"#0000ff" size=3D"2">Hi Shahram,</font></span></div>
<div dir=3D"ltr" align=3D"left"><span class=3D"890560116-07062013"><font fa=
ce=3D"Arial" color=3D"#0000ff" size=3D"2">and hence&nbsp;are my questions:<=
/font></span></div>
<ul dir=3D"ltr">
<li>
<div align=3D"left"><span class=3D"890560116-07062013"><font face=3D"Arial"=
 color=3D"#0000ff" size=3D"2">Is proposed mechanism required to transport o=
ther timing protocols over MPLS network</font></span></div>
</li><li>
<div align=3D"left"><span class=3D"890560116-07062013"><font face=3D"Arial"=
 color=3D"#0000ff" size=3D"2">Is use of PTP LSP to transport NTP messages j=
ustified or not</font></span></div>
</li></ul>
<div dir=3D"ltr" align=3D"left"><span class=3D"890560116-07062013">&nbsp;&n=
bsp;&nbsp; <font face=3D"Arial" color=3D"#0000ff" size=3D"2">
Regards,</font></span></div>
<div dir=3D"ltr" align=3D"left"><span class=3D"890560116-07062013">&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <font face=3D"Arial" color=3D"#0000ff" s=
ize=3D"2">
Greg</font></span></div>
<br>
<div class=3D"OutlookMessageHeader" lang=3D"en-us" dir=3D"ltr" align=3D"lef=
t">
<hr tabindex=3D"-1">
<font face=3D"Tahoma" size=3D"2"><b>From:</b> Shahram Davari [<a href=3D"ma=
ilto:davari@broadcom.com">mailto:davari@broadcom.com</a>]
<br>
<b>Sent:</b> Friday, June 07, 2013 9:01 AM<br>
<b>To:</b> Gregory Mirsky<br>
<b>Cc:</b> Yaakov Stein; Amit Oren; Bhatia, Manav (Manav); Roberts, Peter (=
Peter);
<a href=3D"mailto:lmontini@cisco.com">lmontini@cisco.com</a>; <a href=3D"ma=
ilto:tictoc@ietf.org">
tictoc@ietf.org</a><br>
<b>Subject:</b> Re: NTP in draft-ietf-tictoc-1588overmpls-04<br>
</font><br>
</div>
<div></div>
<div>Greg,</div>
<div><br>
</div>
<div>This draft was originally only for PTP, however our Area Director aske=
d the draft to be made more generic so that it can apply to any timing prot=
ocol.<br>
<br>
Regards,
<div>Shahram</div>
<div><br>
</div>
</div>
<div><br>
On Jun 7, 2013, at 8:28 AM, &quot;Gregory Mirsky&quot; &lt;<a href=3D"mailt=
o:gregory.mirsky@ericsson.com">gregory.mirsky@ericsson.com</a>&gt; wrote:<b=
r>
<br>
</div>
<blockquote type=3D"cite">
<div>
<meta content=3D"MSHTML 6.00.6002.18823" name=3D"GENERATOR">
<style>@font-face {
	font-family: Cambria Math;
}
@font-face {
	font-family: Calibri;
}
@font-face {
	font-family: Tahoma;
}
@page WordSection1 {size: 8.5in 11.0in; margin: 1.0in 1.25in 1.0in 1.25in; =
}
P.MsoNormal {
	FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman","seri=
f"
}
LI.MsoNormal {
	FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman","seri=
f"
}
DIV.MsoNormal {
	FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman","seri=
f"
}
A:link {
	COLOR: blue; TEXT-DECORATION: underline; mso-style-priority: 99
}
SPAN.MsoHyperlink {
	COLOR: blue; TEXT-DECORATION: underline; mso-style-priority: 99
}
A:visited {
	COLOR: purple; TEXT-DECORATION: underline; mso-style-priority: 99
}
SPAN.MsoHyperlinkFollowed {
	COLOR: purple; TEXT-DECORATION: underline; mso-style-priority: 99
}
P.emailquote {
	BORDER-RIGHT: medium none; PADDING-RIGHT: 0in; BORDER-TOP: medium none; PA=
DDING-LEFT: 0in; FONT-SIZE: 12pt; PADDING-BOTTOM: 0in; MARGIN-LEFT: 1pt; BO=
RDER-LEFT: medium none; MARGIN-RIGHT: 0in; PADDING-TOP: 0in; BORDER-BOTTOM:=
 medium none; FONT-FAMILY: "Times New Roman","serif"; mso-style-name: email=
quote; mso-margin-top-alt: auto; mso-margin-bottom-alt: auto
}
LI.emailquote {
	BORDER-RIGHT: medium none; PADDING-RIGHT: 0in; BORDER-TOP: medium none; PA=
DDING-LEFT: 0in; FONT-SIZE: 12pt; PADDING-BOTTOM: 0in; MARGIN-LEFT: 1pt; BO=
RDER-LEFT: medium none; MARGIN-RIGHT: 0in; PADDING-TOP: 0in; BORDER-BOTTOM:=
 medium none; FONT-FAMILY: "Times New Roman","serif"; mso-style-name: email=
quote; mso-margin-top-alt: auto; mso-margin-bottom-alt: auto
}
DIV.emailquote {
	BORDER-RIGHT: medium none; PADDING-RIGHT: 0in; BORDER-TOP: medium none; PA=
DDING-LEFT: 0in; FONT-SIZE: 12pt; PADDING-BOTTOM: 0in; MARGIN-LEFT: 1pt; BO=
RDER-LEFT: medium none; MARGIN-RIGHT: 0in; PADDING-TOP: 0in; BORDER-BOTTOM:=
 medium none; FONT-FAMILY: "Times New Roman","serif"; mso-style-name: email=
quote; mso-margin-top-alt: auto; mso-margin-bottom-alt: auto
}
SPAN.EmailStyle18 {
	COLOR: #1f497d; FONT-FAMILY: "Calibri","sans-serif"; mso-style-type: perso=
nal-reply
}
.MsoChpDefault {
	FONT-SIZE: 10pt; mso-style-type: export-only
}
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]-->
<div dir=3D"ltr" align=3D"left"><span class=3D"070062615-07062013"><font fa=
ce=3D"Arial" color=3D"#0000ff" size=3D"2">Yaakov,</font></span></div>
<div dir=3D"ltr" align=3D"left"><span class=3D"070062615-07062013"><font fa=
ce=3D"Arial"><font size=3D"2"><font color=3D"#0000ff">I'm rather sceptical =
of using &quot;<span class=3D"st">If you build it, he will come&quot; as pr=
otocol development guiding principle. Personally I prefer
 KISS.</span></font></font></font></span></div>
<div dir=3D"ltr" align=3D"left"><span class=3D"070062615-07062013"><font fa=
ce=3D"Arial"><font size=3D"2"><font color=3D"#0000ff"><span class=3D"st"></=
span></font></font></font></span>&nbsp;</div>
<div dir=3D"ltr" align=3D"left"><span class=3D"070062615-07062013"><font fa=
ce=3D"Arial"><font size=3D"2"><font color=3D"#0000ff"><span class=3D"st">&n=
bsp;&nbsp;&nbsp; Regards,</span></font></font></font></span></div>
<div dir=3D"ltr" align=3D"left"><span class=3D"070062615-07062013"><font fa=
ce=3D"Arial"><font size=3D"2"><font color=3D"#0000ff"><span class=3D"st">&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Greg</span></font></font></font></=
span></div>
<br>
<div class=3D"OutlookMessageHeader" lang=3D"en-us" dir=3D"ltr" align=3D"lef=
t">
<hr tabindex=3D"-1">
<font face=3D"Tahoma" size=3D"2"><b>From:</b> Yaakov Stein [<a href=3D"mail=
to:yaakov_s@rad.com">mailto:yaakov_s@rad.com</a>]
<br>
<b>Sent:</b> Friday, June 07, 2013 7:55 AM<br>
<b>To:</b> Gregory Mirsky; Shahram Davari; <a href=3D"mailto:amito@broadcom=
.com">amito@broadcom.com</a>; Bhatia, Manav (Manav); Roberts, Peter (Peter)=
;
<a href=3D"mailto:lmontini@cisco.com">lmontini@cisco.com</a>; <a href=3D"ma=
ilto:tictoc@ietf.org">
tictoc@ietf.org</a><br>
<b>Subject:</b> RE: NTP in draft-ietf-tictoc-1588overmpls-04<br>
</font><br>
</div>
<div></div>
<div class=3D"WordSection1">
<p class=3D"MsoNormal"><span style=3D"FONT-SIZE: 11pt; COLOR: #1f497d; FONT=
-FAMILY: 'Calibri','sans-serif'">Greg<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"FONT-SIZE: 11pt; COLOR: #1f497d; FONT=
-FAMILY: 'Calibri','sans-serif'"><o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"FONT-SIZE: 11pt; COLOR: #1f497d; FONT=
-FAMILY: 'Calibri','sans-serif'">This version makes the mechanism more gene=
ral so that in future other time-sensitive protocols<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"FONT-SIZE: 11pt; COLOR: #1f497d; FONT=
-FAMILY: 'Calibri','sans-serif'">(NTP, delay measurement OAM, generic heade=
r for MPLS) could avail themselves of its timestamping/correction features.=
<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"FONT-SIZE: 11pt; COLOR: #1f497d; FONT=
-FAMILY: 'Calibri','sans-serif'"><o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"FONT-SIZE: 11pt; COLOR: #1f497d; FONT=
-FAMILY: 'Calibri','sans-serif'">It is true that the only real case so far =
is 1588.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"FONT-SIZE: 11pt; COLOR: #1f497d; FONT=
-FAMILY: 'Calibri','sans-serif'"><o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"FONT-SIZE: 11pt; COLOR: #1f497d; FONT=
-FAMILY: 'Calibri','sans-serif'">Y(J)S<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"FONT-SIZE: 11pt; COLOR: #1f497d; FONT=
-FAMILY: 'Calibri','sans-serif'"><o:p></o:p></span></p>
<div>
<div style=3D"BORDER-RIGHT: medium none; PADDING-RIGHT: 0in; BORDER-TOP: #b=
5c4df 1pt solid; PADDING-LEFT: 0in; PADDING-BOTTOM: 0in; BORDER-LEFT: mediu=
m none; PADDING-TOP: 3pt; BORDER-BOTTOM: medium none">
<p class=3D"MsoNormal"><b><span style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'Tah=
oma','sans-serif'">From:</span></b><span style=3D"FONT-SIZE: 10pt; FONT-FAM=
ILY: 'Tahoma','sans-serif'">
<a href=3D"mailto:tictoc-bounces@ietf.org">tictoc-bounces@ietf.org</a> [<a =
href=3D"mailto:tictoc-bounces@ietf.org">mailto:tictoc-bounces@ietf.org</a>]
<b>On Behalf Of </b>Gregory Mirsky<br>
<b>Sent:</b> 06 June, 2013 21:23<br>
<b>To:</b> Shahram Davari; <a href=3D"mailto:amito@broadcom.com">amito@broa=
dcom.com</a>; Bhatia, Manav (Manav); Roberts, Peter (Peter);
<a href=3D"mailto:lmontini@cisco.com">lmontini@cisco.com</a>; <a href=3D"ma=
ilto:tictoc@ietf.org">
tictoc@ietf.org</a><br>
<b>Subject:</b> [TICTOC] NTP in draft-ietf-tictoc-1588overmpls-04<o:p></o:p=
></span></p>
</div>
</div>
<p class=3D"MsoNormal"><o:p></o:p></p>
<div>
<p class=3D"MsoNormal"><span style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'Arial'=
,'sans-serif'">Dear Authors, et al.,<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'Arial'=
,'sans-serif'">The draft-ietf-tictoc-1588overmpls-04 is currently titled as=
 &quot;Transporting Timing messages over MPLS Networks&quot; and states tha=
t both timing synchronization protocols, PTP and
 NTP, require use of PTP LSP to transport timing messages over an MPLS netw=
ork. After reading RFC 5905 I am not sure that PTP LSP, with its constraint=
s and additional complexity, is required to transport NTPv4 messages over a=
n MPLS network. And first paragraph
 in Section 3 Problem Statement of draft-ietf-tictoc-1588overmpls-04 explai=
ns motivation for the PTP as
<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'Arial'=
,'sans-serif'">&quot;There is a need to transport Timing messages over MPLS=
 networks while supporting the Transparent Clock (TC), Boundary Clock (BC) =
and Ordinary Clock (OC) functionality in
 the LER and LSRs in the MPLS network.&quot;<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'Arial'=
,'sans-serif'">but says nothing of a kind about NTP.<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'Arial'=
,'sans-serif'"><o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'Arial'=
,'sans-serif'">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Regards,<o:p></o:=
p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'Arial'=
,'sans-serif'">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Greg<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'Arial'=
,'sans-serif'"><o:p></o:p></span></p>
</div>
</div>
</div>
</blockquote>
</div>
</blockquote>
</body>
</html>

--_000_213EA83402B44ABEB7A1C25F3CE68B2Ebroadcomcom_--


From davari@broadcom.com  Fri Jun  7 13:27:54 2013
Return-Path: <davari@broadcom.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 A5C1321F9928 for <tictoc@ietfa.amsl.com>; Fri,  7 Jun 2013 13:27:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.598
X-Spam-Level: 
X-Spam-Status: No, score=-6.598 tagged_above=-999 required=5 tests=[AWL=-0.000, BAYES_00=-2.599, 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 N2Qq+rwwk624 for <tictoc@ietfa.amsl.com>; Fri,  7 Jun 2013 13:27:49 -0700 (PDT)
Received: from mms2.broadcom.com (mms2.broadcom.com [216.31.210.18]) by ietfa.amsl.com (Postfix) with ESMTP id 750C721F9798 for <tictoc@ietf.org>; Fri,  7 Jun 2013 13:27:49 -0700 (PDT)
Received: from [10.9.208.53] by mms2.broadcom.com with ESMTP (Broadcom SMTP Relay (Email Firewall v6.5)); Fri, 07 Jun 2013 13:21:54 -0700
X-Server-Uuid: 4500596E-606A-40F9-852D-14843D8201B2
Received: from SJEXCHCAS03.corp.ad.broadcom.com (10.16.203.8) by IRVEXCHCAS06.corp.ad.broadcom.com (10.9.208.53) with Microsoft SMTP Server (TLS) id 14.1.438.0; Fri, 7 Jun 2013 13:27:33 -0700
Received: from SJEXCHMB12.corp.ad.broadcom.com ( [fe80::bc15:c1e1:c29a:36f7]) by SJEXCHCAS03.corp.ad.broadcom.com ( [::1]) with mapi id 14.01.0438.000; Fri, 7 Jun 2013 13:27:33 -0700
From: "Shahram Davari" <davari@broadcom.com>
To: "John E Drake" <jdrake@juniper.net>
Thread-Topic: NTP in draft-ietf-tictoc-1588overmpls-04
Thread-Index: Ac5i4ubOrT57JHkXTgC9GUzpraB4EAAq9gQAAAElPiAAATQbzwAADGYgAAA+HtAACQiCcQ==
Date: Fri, 7 Jun 2013 20:27:33 +0000
Message-ID: <7B7DBF6C-72A7-4484-9536-398E5B0770C3@broadcom.com>
References: <7347100B5761DC41A166AC17F22DF1121B4A0754@eusaamb103.ericsson.se> <07F7D7DED63154409F13298786A2ADC904D6D57C@EXRAD5.ad.rad.co.il>, <7347100B5761DC41A166AC17F22DF1121B4A0CB9@eusaamb103.ericsson.se> <DDB3D38B-6FE8-4A4A-A604-56AB9181C5FE@broadcom.com> <7347100B5761DC41A166AC17F22DF1121B4A0CEF@eusaamb103.ericsson.se>, <0182DEA5604B3A44A2EE61F3EE3ED69E1D51BE2D@BL2PRD0510MB349.namprd05.prod.outlook.com>
In-Reply-To: <0182DEA5604B3A44A2EE61F3EE3ED69E1D51BE2D@BL2PRD0510MB349.namprd05.prod.outlook.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
MIME-Version: 1.0
X-WSS-ID: 7DAC9F681R028115074-01-01
Content-Type: multipart/alternative; boundary=_000_7B7DBF6C72A744849536398E5B0770C3broadcomcom_
Cc: "tictoc@ietf.org" <tictoc@ietf.org>
Subject: Re: [TICTOC] NTP in draft-ietf-tictoc-1588overmpls-04
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, 07 Jun 2013 20:27:54 -0000

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

We can never be sure, but we have made it general enough to be used for oth=
er timing protocols if needed.

 This draft really doesn't introduce any new protocol, it just says transpo=
rt Timing over dedicated LSPs. The generalization is in companion drafts th=
at include OSPF and RSVPTE extensions.

Regards,
Shahram


On Jun 7, 2013, at 9:32 AM, "John E Drake" <jdrake@juniper.net<mailto:jdrak=
e@juniper.net>> wrote:

& Do we know to a certainty that the proposed generalizations will support =
all (or any) other current and future timing protocols?

Yours Irrespectively,

John

From: tictoc-bounces@ietf.org<mailto:tictoc-bounces@ietf.org> [mailto:ticto=
c-bounces@ietf.org] On Behalf Of Gregory Mirsky
Sent: Friday, June 07, 2013 9:07 AM
To: Shahram Davari
Cc: tictoc@ietf.org<mailto:tictoc@ietf.org>
Subject: Re: [TICTOC] NTP in draft-ietf-tictoc-1588overmpls-04

Hi Shahram,
and hence are my questions:

  *   Is proposed mechanism required to transport other timing protocols ov=
er MPLS network
  *   Is use of PTP LSP to transport NTP messages justified or not
    Regards,
        Greg

________________________________
From: Shahram Davari [mailto:davari@broadcom.com]
Sent: Friday, June 07, 2013 9:01 AM
To: Gregory Mirsky
Cc: Yaakov Stein; Amit Oren; Bhatia, Manav (Manav); Roberts, Peter (Peter);=
 lmontini@cisco.com<mailto:lmontini@cisco.com>; tictoc@ietf.org<mailto:tict=
oc@ietf.org>
Subject: Re: NTP in draft-ietf-tictoc-1588overmpls-04
Greg,

This draft was originally only for PTP, however our Area Director asked the=
 draft to be made more generic so that it can apply to any timing protocol.

Regards,
Shahram


On Jun 7, 2013, at 8:28 AM, "Gregory Mirsky" <gregory.mirsky@ericsson.com<m=
ailto:gregory.mirsky@ericsson.com>> wrote:
Yaakov,
I'm rather sceptical of using "If you build it, he will come" as protocol d=
evelopment guiding principle. Personally I prefer KISS.

    Regards,
        Greg

________________________________
From: Yaakov Stein [mailto:yaakov_s@rad.com]
Sent: Friday, June 07, 2013 7:55 AM
To: Gregory Mirsky; Shahram Davari; amito@broadcom.com<mailto:amito@broadco=
m.com>; Bhatia, Manav (Manav); Roberts, Peter (Peter); lmontini@cisco.com<m=
ailto:lmontini@cisco.com>; tictoc@ietf.org<mailto:tictoc@ietf.org>
Subject: RE: NTP in draft-ietf-tictoc-1588overmpls-04
Greg
This version makes the mechanism more general so that in future other time-=
sensitive protocols
(NTP, delay measurement OAM, generic header for MPLS) could avail themselve=
s of its timestamping/correction features.
It is true that the only real case so far is 1588.
Y(J)S
From: tictoc-bounces@ietf.org<mailto:tictoc-bounces@ietf.org> [mailto:ticto=
c-bounces@ietf.org] On Behalf Of Gregory Mirsky
Sent: 06 June, 2013 21:23
To: Shahram Davari; amito@broadcom.com<mailto:amito@broadcom.com>; Bhatia, =
Manav (Manav); Roberts, Peter (Peter); lmontini@cisco.com<mailto:lmontini@c=
isco.com>; tictoc@ietf.org<mailto:tictoc@ietf.org>
Subject: [TICTOC] NTP in draft-ietf-tictoc-1588overmpls-04
Dear Authors, et al.,
The draft-ietf-tictoc-1588overmpls-04 is currently titled as "Transporting =
Timing messages over MPLS Networks" and states that both timing synchroniza=
tion protocols, PTP and NTP, require use of PTP LSP to transport timing mes=
sages over an MPLS network. After reading RFC 5905 I am not sure that PTP L=
SP, with its constraints and additional complexity, is required to transpor=
t NTPv4 messages over an MPLS network. And first paragraph in Section 3 Pro=
blem Statement of draft-ietf-tictoc-1588overmpls-04 explains motivation for=
 the PTP as
"There is a need to transport Timing messages over MPLS networks while supp=
orting the Transparent Clock (TC), Boundary Clock (BC) and Ordinary Clock (=
OC) functionality in the LER and LSRs in the MPLS network."
but says nothing of a kind about NTP.
        Regards,
                Greg

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

<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
</head>
<body dir=3D"auto">
<div>We can never be sure, but we have made it general enough to be used fo=
r other timing protocols if needed.</div>
<div><br>
</div>
<div>&nbsp;This draft really doesn't introduce any new protocol, it just sa=
ys transport Timing over dedicated LSPs. The generalization is in companion=
 drafts that include OSPF and RSVPTE extensions.<br>
<br>
Regards,
<div>Shahram</div>
<div><br>
</div>
</div>
<div><br>
On Jun 7, 2013, at 9:32 AM, &quot;John E Drake&quot; &lt;<a href=3D"mailto:=
jdrake@juniper.net">jdrake@juniper.net</a>&gt; wrote:<br>
<br>
</div>
<blockquote type=3D"cite">
<div>
<meta name=3D"Generator" content=3D"Microsoft Word 12 (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:Wingdings;
	panose-1:5 0 0 0 0 0 0 0 0 0;}
@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";}
p.emailquote, li.emailquote, div.emailquote
	{mso-style-name:emailquote;
	mso-margin-top-alt:auto;
	margin-right:0in;
	mso-margin-bottom-alt:auto;
	margin-left:1.0pt;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";}
span.EmailStyle18
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
span.st
	{mso-style-name:st;}
span.BalloonTextChar
	{mso-style-name:"Balloon Text Char";
	mso-style-priority:99;
	mso-style-link:"Balloon Text";
	font-family:"Tahoma","sans-serif";}
span.EmailStyle22
	{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;}
/* List Definitions */
@list l0
	{mso-list-id:1742019803;
	mso-list-template-ids:-458480706;}
@list l0:level1
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:.5in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:Symbol;}
ol
	{margin-bottom:0in;}
ul
	{margin-bottom:0in;}
--></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]-->
<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">&amp; Do we know to a cer=
tainty that the proposed generalizations will support all (or any) other cu=
rrent and future timing protocols?<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>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">Yours Irrespectively,<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=
>
</div>
<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-left:solid blue 1.5pt;padding:0in 0in 0in =
4.0pt">
<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;">
<a href=3D"mailto:tictoc-bounces@ietf.org">tictoc-bounces@ietf.org</a> [<a =
href=3D"mailto:tictoc-bounces@ietf.org">mailto:tictoc-bounces@ietf.org</a>]
<b>On Behalf Of </b>Gregory Mirsky<br>
<b>Sent:</b> Friday, June 07, 2013 9:07 AM<br>
<b>To:</b> Shahram Davari<br>
<b>Cc:</b> <a href=3D"mailto:tictoc@ietf.org">tictoc@ietf.org</a><br>
<b>Subject:</b> Re: [TICTOC] NTP in draft-ietf-tictoc-1588overmpls-04<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:10.0pt;font-family:&quot;Ar=
ial&quot;,&quot;sans-serif&quot;;color:blue">Hi Shahram,</span><o:p></o:p><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Ar=
ial&quot;,&quot;sans-serif&quot;;color:blue">and hence&nbsp;are my question=
s:</span><o:p></o:p></p>
<ul type=3D"disc">
<li class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-=
alt:auto;mso-list:l0 level1 lfo1">
<span style=3D"font-size:10.0pt;font-family:&quot;Arial&quot;,&quot;sans-se=
rif&quot;;color:blue">Is proposed mechanism required to transport other tim=
ing protocols over MPLS network</span><o:p></o:p></li><li class=3D"MsoNorma=
l" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l0 =
level1 lfo1">
<span style=3D"font-size:10.0pt;font-family:&quot;Arial&quot;,&quot;sans-se=
rif&quot;;color:blue">Is use of PTP LSP to transport NTP messages justified=
 or not</span><o:p></o:p></li></ul>
<p class=3D"MsoNormal">&nbsp;&nbsp;&nbsp; <span style=3D"font-size:10.0pt;f=
ont-family:&quot;Arial&quot;,&quot;sans-serif&quot;;color:blue">
Regards,</span><o:p></o:p></p>
<p class=3D"MsoNormal">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <span sty=
le=3D"font-size:10.0pt;font-family:&quot;Arial&quot;,&quot;sans-serif&quot;=
;color:blue">
Greg</span><o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<div class=3D"MsoNormal" align=3D"center" style=3D"text-align:center">
<hr size=3D"2" width=3D"100%" align=3D"center">
</div>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt"><b><span style=3D"fon=
t-size:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;">From:<=
/span></b><span style=3D"font-size:10.0pt;font-family:&quot;Tahoma&quot;,&q=
uot;sans-serif&quot;"> Shahram Davari [<a href=3D"mailto:davari@broadcom.co=
m">mailto:davari@broadcom.com</a>]
<br>
<b>Sent:</b> Friday, June 07, 2013 9:01 AM<br>
<b>To:</b> Gregory Mirsky<br>
<b>Cc:</b> Yaakov Stein; Amit Oren; Bhatia, Manav (Manav); Roberts, Peter (=
Peter);
<a href=3D"mailto:lmontini@cisco.com">lmontini@cisco.com</a>; <a href=3D"ma=
ilto:tictoc@ietf.org">
tictoc@ietf.org</a><br>
<b>Subject:</b> Re: NTP in draft-ietf-tictoc-1588overmpls-04</span><o:p></o=
:p></p>
<div>
<p class=3D"MsoNormal">Greg,<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<div>
<p class=3D"MsoNormal">This draft was originally only for PTP, however our =
Area Director asked the draft to be made more generic so that it can apply =
to any timing protocol.<br>
<br>
Regards, <o:p></o:p></p>
<div>
<p class=3D"MsoNormal">Shahram<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt"><br>
On Jun 7, 2013, at 8:28 AM, &quot;Gregory Mirsky&quot; &lt;<a href=3D"mailt=
o:gregory.mirsky@ericsson.com">gregory.mirsky@ericsson.com</a>&gt; wrote:<o=
:p></o:p></p>
</div>
<blockquote style=3D"margin-top:5.0pt;margin-bottom:5.0pt">
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Ar=
ial&quot;,&quot;sans-serif&quot;;color:blue">Yaakov,</span><o:p></o:p></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Ar=
ial&quot;,&quot;sans-serif&quot;;color:blue">I'm rather sceptical of using =
&quot;<span class=3D"st">If you build it, he will come&quot; as protocol de=
velopment guiding principle. Personally I prefer KISS.</span></span><o:p></=
o:p></p>
<p class=3D"MsoNormal">&nbsp;<o:p></o:p></p>
<p class=3D"MsoNormal"><span class=3D"st"><span style=3D"font-size:10.0pt;f=
ont-family:&quot;Arial&quot;,&quot;sans-serif&quot;;color:blue">&nbsp;&nbsp=
;&nbsp; Regards,</span></span><o:p></o:p></p>
<p class=3D"MsoNormal"><span class=3D"st"><span style=3D"font-size:10.0pt;f=
ont-family:&quot;Arial&quot;,&quot;sans-serif&quot;;color:blue">&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Greg</span></span><o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<div class=3D"MsoNormal" align=3D"center" style=3D"text-align:center">
<hr size=3D"2" width=3D"100%" align=3D"center">
</div>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt"><b><span style=3D"fon=
t-size:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;">From:<=
/span></b><span style=3D"font-size:10.0pt;font-family:&quot;Tahoma&quot;,&q=
uot;sans-serif&quot;"> Yaakov Stein [<a href=3D"mailto:yaakov_s@rad.com">ma=
ilto:yaakov_s@rad.com</a>]
<br>
<b>Sent:</b> Friday, June 07, 2013 7:55 AM<br>
<b>To:</b> Gregory Mirsky; Shahram Davari; <a href=3D"mailto:amito@broadcom=
.com">amito@broadcom.com</a>; Bhatia, Manav (Manav); Roberts, Peter (Peter)=
;
<a href=3D"mailto:lmontini@cisco.com">lmontini@cisco.com</a>; <a href=3D"ma=
ilto:tictoc@ietf.org">
tictoc@ietf.org</a><br>
<b>Subject:</b> RE: NTP in draft-ietf-tictoc-1588overmpls-04</span><o:p></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">Greg</span><o:p></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">This version makes the me=
chanism more general so that in future other time-sensitive protocols</span=
><o:p></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">(NTP, delay measurement O=
AM, generic header for MPLS) could avail themselves of its timestamping/cor=
rection features.</span><o:p></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">It is true that the only =
real case so far is 1588.</span><o:p></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">Y(J)S</span><o:p></o:p></=
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;">
<a href=3D"mailto:tictoc-bounces@ietf.org">tictoc-bounces@ietf.org</a> [<a =
href=3D"mailto:tictoc-bounces@ietf.org">mailto:tictoc-bounces@ietf.org</a>]
<b>On Behalf Of </b>Gregory Mirsky<br>
<b>Sent:</b> 06 June, 2013 21:23<br>
<b>To:</b> Shahram Davari; <a href=3D"mailto:amito@broadcom.com">amito@broa=
dcom.com</a>; Bhatia, Manav (Manav); Roberts, Peter (Peter);
<a href=3D"mailto:lmontini@cisco.com">lmontini@cisco.com</a>; <a href=3D"ma=
ilto:tictoc@ietf.org">
tictoc@ietf.org</a><br>
<b>Subject:</b> [TICTOC] NTP in draft-ietf-tictoc-1588overmpls-04</span><o:=
p></o:p></p>
</div>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Ar=
ial&quot;,&quot;sans-serif&quot;">Dear Authors, et al.,</span><o:p></o:p></=
p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Ar=
ial&quot;,&quot;sans-serif&quot;">The draft-ietf-tictoc-1588overmpls-04 is =
currently titled as &quot;Transporting Timing messages over MPLS Networks&q=
uot; and states that both timing synchronization protocols, PTP and
 NTP, require use of PTP LSP to transport timing messages over an MPLS netw=
ork. After reading RFC 5905 I am not sure that PTP LSP, with its constraint=
s and additional complexity, is required to transport NTPv4 messages over a=
n MPLS network. And first paragraph
 in Section 3 Problem Statement of draft-ietf-tictoc-1588overmpls-04 explai=
ns motivation for the PTP as
</span><o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Ar=
ial&quot;,&quot;sans-serif&quot;">&quot;There is a need to transport Timing=
 messages over MPLS networks while supporting the Transparent Clock (TC), B=
oundary Clock (BC) and Ordinary Clock (OC) functionality in the
 LER and LSRs in the MPLS network.&quot;</span><o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Ar=
ial&quot;,&quot;sans-serif&quot;">but says nothing of a kind about NTP.</sp=
an><o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Ar=
ial&quot;,&quot;sans-serif&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
; Regards,</span><o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Ar=
ial&quot;,&quot;sans-serif&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Greg</span><o:p></o:p></p=
>
</div>
</div>
</blockquote>
</div>
</div>
</div>
</blockquote>
</body>
</html>

--_000_7B7DBF6C72A744849536398E5B0770C3broadcomcom_--


From kevin.gross@avanw.com  Mon Jun 10 10:10:26 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 6F1CD21F9649 for <tictoc@ietfa.amsl.com>; Mon, 10 Jun 2013 10:10:26 -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=[AWL=0.000,  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 1LXnnm534fFt for <tictoc@ietfa.amsl.com>; Mon, 10 Jun 2013 10:10:22 -0700 (PDT)
Received: from qmta06.emeryville.ca.mail.comcast.net (qmta06.emeryville.ca.mail.comcast.net [IPv6:2001:558:fe2d:43:76:96:30:56]) by ietfa.amsl.com (Postfix) with ESMTP id B58FE21F86AE for <tictoc@ietf.org>; Mon, 10 Jun 2013 10:10:21 -0700 (PDT)
Received: from omta01.emeryville.ca.mail.comcast.net ([76.96.30.11]) by qmta06.emeryville.ca.mail.comcast.net with comcast id mebA1l0050EPchoA6hAMiN; Mon, 10 Jun 2013 17:10:21 +0000
Received: from mail-ie0-x234.google.com ([IPv6:2607:f8b0:4001:c03::234]) by omta01.emeryville.ca.mail.comcast.net with comcast id mhAL1l01458t75Q8MhAML5; Mon, 10 Jun 2013 17:10:21 +0000
Received: by mail-ie0-f180.google.com with SMTP id f4so11804071iea.25 for <tictoc@ietf.org>; Mon, 10 Jun 2013 10:10:20 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=xOvyOTHtdsXTZObJj20YA9DCNIH/PibeZJi3CdG9fB0=; b=PUbXPiEVYqCHhj6On5+dISM0+MRFUKVwpygNNfRqzkoqU2bdShAELkt0fBU9z3iRm2 dhvVBgoENMnVdKKbEY9eYqgC66jez2GTg8Ouxu53ugAcy9fC3pWWVzxijBJTESVWLUg+ hplau6fWb+zJQ6QGCfAa7sqa5GxuCBXZiH353ZwSzqX4mIHfCeSNgkHmjoZC7t+sf86c k6Crht8FUnUel3tCvneG8Bnxl5DSEq4uaufBDQSorIqK8Med0GNAofyrVFpymFBUjsQW mwFajRp/LG09/8Qlz9qsEc0DILineq0IvIVRGulM/SXkHQx/Z/jb52D6uOuLFuKi0kmj qrRQ==
MIME-Version: 1.0
X-Received: by 10.50.102.67 with SMTP id fm3mr4569816igb.5.1370884220609; Mon, 10 Jun 2013 10:10:20 -0700 (PDT)
Received: by 10.50.149.199 with HTTP; Mon, 10 Jun 2013 10:10:20 -0700 (PDT)
In-Reply-To: <4A4385BFBA1BC54C863E7394BD1AECB36EB1C82C@SJC-MBX-01.symmetricom.com>
References: <5194FE2F.2060504@isoc.org> <CALw1_Q3DxKFc+oNFj_0iyDPp4m59hNS3--7R+nX_i1OzOaeT-g@mail.gmail.com> <4A4385BFBA1BC54C863E7394BD1AECB36EB1C82C@SJC-MBX-01.symmetricom.com>
Date: Mon, 10 Jun 2013 11:10:20 -0600
Message-ID: <CALw1_Q1D+iCamS4j1C=GEvsehJ1wYTbFz9y34m12nurW7RgfNQ@mail.gmail.com>
From: Kevin Gross <kevin.gross@avanw.com>
To: Tim Frost <tfrost@symmetricom.com>
Content-Type: multipart/alternative; boundary=047d7b10ca13ff806204decfda85
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20121106; t=1370884221; bh=xOvyOTHtdsXTZObJj20YA9DCNIH/PibeZJi3CdG9fB0=; h=Received:Received:Received:MIME-Version:Received:Date:Message-ID: Subject:From:To:Content-Type; b=LTKRkYL+Oz0z5zbTnku46EXsCtV0uwl+9j0qYaeAEdR11Ty23FyuelbM6QpmBSNfT fgV1oZkKsZOi64NQ1UdocgyRPvh1Fl72kc3Van77V2oIn1JEDv14/SC6Vj4PT4Ug9B h2eA0D6MmU74uxhDFpv4fNXNtNozhOB/1hqBrrzG+fHPZ3PJgqCd/tGaqEUHi5siLW TOdFrR8cw+7MGQ2+u4SrWs1N83xAKJkuWuKQ4ztZNLwOOdmI1G6XoHvIhFjFHC1xIT w9NaYwOcDm3mb+3pQzzRKHdwq5LUcmT0op1wA2rQ4zhAzxrH2IStm2VUXpauMe0unc QSbHSZPtPsuHA==
Cc: "tictoc@ietf.org" <tictoc@ietf.org>, Karen ODonoghue <odonoghue@isoc.org>
Subject: Re: [TICTOC] WGLC on draft-ietf-tictoc-ptp-mib-05.txt
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, 10 Jun 2013 17:10:26 -0000

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

Thanks for addressing my comments. It looks like there are two outstanding.

   1. ClockInstanceType and
   2. ClockProfileType

It sounds like you intend to address (1) in a future revision.

With regards to (2), I think you misunderstand how the profileIdentifier
works. Please have a look at Section 19.3.3 of IEEE 1588-2008. This is an
EUI-48, not merely an OUI. Organizations can change the bottom 24 bits to
indicate new profiles or revisions of existing ones. Maintaining our own
enumeration of profiles does not seem like a feasible undertaking.

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


On Fri, May 17, 2013 at 2:33 AM, Tim Frost <tfrost@symmetricom.com> wrote:

>  Hi Kevin,****
>
> ** **
>
> Thank you for taking the time to go through this MIB. We did consider you=
r
> comments, and they were addressed in -05 (the latest version, and the
> subject of the last call).  I=92ve gone through each of your comments bel=
ow;
> it looks like we missed one, and decided against another, but the remaind=
er
> have been done.****
>
> ** **
>
> The change history from the -05 draft reads: ****
>
> ** **
>
> -05       Feb 13 Several changes in response to comments from Alun Luchuk
>              and Kevin Gross:
>              - Modified the use of wellKnownTransportTypes and
>                wellKnownEncapsulationTypes
>              - changed ptpbaseClockPortSyncOneStep to
>                ptpbaseClockPortSyncTwoStep to match IEEE1588
>                semantics
>              - Re-ordered textual conventions to be alphabetic
>              - Changed some types from Integer32 to use defined
>                textual conventions
>              - various minor descriptive text changes****
>
> ** **
>
> In detail:
>
> ****
>
> Abstract: Add a bracketed reference to IEEE 1588-2008 - DONE****
>
> ** **
>
> Section 1: s/defined to monitor, measure the performance/defined to
> monitor and measure the performance - DONE****
>
> ** **
>
> Section 1.1 What in this MIB is profile dependent? I did not identify
> anything in my review. It would be desirable. if possible,  to have a
> profile-independent MIB.****
>
> **-    **TF: Removed erroneous text about Telecom Profile =96 there is
> nothing in this MIB that is particular to that profile. ****
>
> ** **
>
> TEXTUAL-CONVENTION general issues - Consider alphabetizing - DONE****
>
> ** **
>
> ClockInstanceType TEXTUAL-CONVENTION definition - Description requires
> elucidation or a reference. ****
>
> **-    **TF: not done, looks like this one slipped through.****
>
> ** **
>
> ClockProfileType TEXTUAL-CONVENTION definition****
>
> Consider using and OUI instead of an enumeration. IEEE 1588-1588 requires
> an OUI be associated with each profile.****
>
> **-    **TF: OUI would be specific to the organization, not the profile.
> If the ITU (for instance) developed more than one profile, then they woul=
d
> have the same OUI. Therefore it is best (in the authors=92 opinion) to st=
ick
> to using an enumeration****
>
> ** **
>
> OBJECT-TYPE general issues****
>
> Consider being consistent about repeating TEXTUAL-CONVENTION descriptions=
,
> explicitly referencing them or assuming readers will track down the
> reference without reminder.****
>
> **-    **TF: We=92ve tried to be as consistent as we can. Of 17
> TEXTUAL-CONVENTIONS, 13 are directly referenced to IEEE1588 sections. The
> remainder don=92t directly map onto IEEE1588 quantities, but onto associa=
ted
> concepts, and we have tried to explain these in the description. Certainl=
y
> one could do with a better description, as you note above. ****
>
> ** **
>
> ptpDomainClockPortsTotal OBJECT-TYPE****
>
> I assume this is the number of ports for the managed PTP-capable system
> (i.e. a router or switch). Suggest adding "in the system" to the
> description to clarify scope of count. - DONE****
>
> ** **
>
> ptpbaseClockTimePropertiesDSTable OBJECT-TYPE ****
>
> s/clock Timeproperties Datasets for/clock time properties datasets for - =
DONE****
>
> ** **
>
> PtpbaseClockTransDefaultDSEntry SEQUENCE****
>
> Use ClockDomainType textual convention instead of Integer32 for ptpbaseCl=
ockTransDefaultDSPrimaryDomain - DONE****
>
> ** **
>
> PtpbaseClockPortEntry SEQUENCE****
>
> Change ptpbaseClockPortSyncOneStep to ptpbaseClockPortSyncTwoStep to matc=
h 1588 semantics for this Boolean =96 DONE****
>
> ** **
>
> ptpbaseClockPortRunningEncapsulationType OBJECT-TYPE****
>
> Needs a textual convention or description of allowed values and their mea=
nings****
>
> **-    **TF: Now uses an autonomous type instead of Integer32****
>
> ** **
>
> ptpbaseClockPortTransDSlogMinPdelayReqInt OBJECT-TYPE****
>
> Change to ClockIntervalBase2 type DONE****
>
> ** **
>
> Section 5: Copy-paste error: "creation and/or manipulation of tunnels"***=
*
>
> **-    **TF: Section changed since -03, no longer has this phrase.****
>
> ** **
>
> Section 6: To be added - DONE****
>
> ** **
>
> ** **
>
> Best regards,****
>
> Tim Frost****
>
> ** **
>
> *From:* tictoc-bounces@ietf.org [mailto:tictoc-bounces@ietf.org] *On
> Behalf Of *Kevin Gross
> *Sent:* 16 May 2013 18:09
>
> *To:* Karen ODonoghue
> *Cc:* tictoc@ietf.org
> *Subject:* Re: [TICTOC] WGLC on draft-ietf-tictoc-ptp-mib-05.txt****
>
>  ** **
>
> I submitted comments on v03 11 January (
> http://www.ietf.org/mail-archive/web/tictoc/current/msg01331.html). Vinay
> indicated in a short message on 23 January the comments would be addresse=
d
> in the next version (
> http://www.ietf.org/mail-archive/web/tictoc/current/msg01333.html). v04
> was published 31 January. I did not see any notes from the authors
> associated with that revision. A quick check of the v03-v04 diff shows
> evidence that not all my comments were directly addressed. Can I get a
> summary of how my comments were addressed? I'm fine if some of these were
> rejected but I would like to verify that they were given consideration.**=
*
> *
>
>
> ****
>
> Kevin Gross****
>
> +1-303-447-0517****
>
> Media Network Consultant****
>
> AVA Networks - www.AVAnw.com <http://www.avanw.com/>, www.X192.org****
>
> ** **
>
> On Thu, May 16, 2013 at 9:41 AM, Karen O'Donoghue <odonoghue@isoc.org>
> wrote:****
>
> This message initiates a two week TICTOC Working Group Last Call on
> advancing:
>
> Title : Precision Time Protocol Version 2 (PTPv2) Management Information
> Base
> Author(s) : Vinay Shankarkumar, Laurent Montini, Tim Frost, Greg Dowd
> Filename : draft-ietf-tictoc-ptp-mib-05.txt
> Pages : 77
> Date : 2013-02-25
>
> http://datatracker.ietf.org/doc/draft-ietf-tictoc-ptp-mib/?include_text=
=3D1
>
> as a Standards Track RFC. Substantive comments and statements of support
> for advancing this document should be directed to the mailing list.
> Editorial suggestions can be sent directly to the authors. This last call
> will end on 31 May 2013.
>
> _______________________________________________
> TICTOC mailing list
> TICTOC@ietf.org
> https://www.ietf.org/mailman/listinfo/tictoc****
>
> ** **
>

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

<div dir=3D"ltr">Thanks for addressing my comments. It looks like there are=
 two outstanding.<div style><ol style><li style>ClockInstanceType and<br></=
li><li style>ClockProfileType<br></li></ol></div><div style>It sounds like =
you intend to address (1) in a future revision.<br>
</div><div style><br></div><div style>With regards to (2), I think you misu=
nderstand how the profileIdentifier works. Please have a look at Section 19=
.3.3 of IEEE 1588-2008. This is an EUI-48, not merely an OUI. Organizations=
 can change the bottom 24 bits to indicate new profiles or revisions of exi=
sting ones. Maintaining our own enumeration of profiles does not seem like =
a feasible undertaking.</div>
</div><div class=3D"gmail_extra"><br clear=3D"all"><div>Kevin Gross<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>,=
=A0<a href=3D"http://www.X192.org" target=3D"_blank">www.X192.org</a></div>
</div></div>
<br><br><div class=3D"gmail_quote">On Fri, May 17, 2013 at 2:33 AM, Tim Fro=
st <span dir=3D"ltr">&lt;<a href=3D"mailto:tfrost@symmetricom.com" target=
=3D"_blank">tfrost@symmetricom.com</a>&gt;</span> wrote:<br><blockquote cla=
ss=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;pa=
dding-left:1ex">






<div lang=3D"EN-US" 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">Thank you for taking the =
time to go through this MIB. We did consider your comments, and they were a=
ddressed in -05 (the latest version, and the subject of
 the last call).=A0 I=92ve gone through each of your comments below; it loo=
ks like we missed one, and decided against another, but the remainder have =
been done.<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">The change history from t=
he -05 draft reads:
<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">-05=A0=A0=A0=A0=A0=A0 Feb 13 Several changes in resp=
onse to comments from Alun Luchuk<br>
=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 and Kevin Gross:<br>
=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 - Modified the use of wellKnownTranspo=
rtTypes and<br>
=A0=A0=A0=A0=A0=A0=A0 =A0=A0=A0=A0=A0=A0=A0wellKnownEncapsulationTypes<br>
=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 - changed ptpbaseClockPortSyncOneStep =
to<br>
=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 ptpbaseClockPortSyncTwoStep to m=
atch IEEE1588<br>
=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 semantics<br>
=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 - Re-ordered textual conventions to be=
 alphabetic<br>
=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 - Changed some types from Integer32 to=
 use defined<br>
=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 textual conventions<br>
=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 - various minor descriptive text chang=
es<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"><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">In detail:<br>
<br>
<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;">Abstract: Add a bracketed reference to IEEE 1588-2008 - DO=
NE<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;"><u></u>=A0<u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;">Section 1: s/defined to monitor, measure the performance/d=
efined to monitor and measure the performance - DONE<u></u><u></u></span></=
p>

<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;"><u></u>=A0<u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;">Section 1.1 What in this MIB is profile dependent? I did n=
ot identify anything in my review. It would be=A0desirable. if possible,=A0=
=A0to have a profile-independent MIB.<u></u><u></u></span></p>

<p><u></u><span style=3D"font-size:10.0pt;font-family:&quot;Courier New&quo=
t;"><span>-<span style=3D"font:7.0pt &quot;Times New Roman&quot;">=A0=A0=A0
</span></span></span><u></u><span style=3D"font-size:10.0pt;font-family:&qu=
ot;Courier New&quot;">TF: Removed erroneous text about Telecom Profile =96 =
there is nothing in this MIB that is particular to that profile.
<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;"><u></u>=A0<u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;">TEXTUAL-CONVENTION general issues - Consider alphabetizing=
 - DONE<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;"><u></u>=A0<u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;;color:#c00000">ClockInstanceType TEXTUAL-CONVENTION definit=
ion - Description requires elucidation or a reference.
<u></u><u></u></span></p>
<p><u></u><span style=3D"font-size:10.0pt;font-family:&quot;Courier New&quo=
t;;color:#c00000"><span>-<span style=3D"font:7.0pt &quot;Times New Roman&qu=
ot;">=A0=A0=A0
</span></span></span><u></u><span style=3D"font-size:10.0pt;font-family:&qu=
ot;Courier New&quot;;color:#c00000">TF: not done, looks like this one slipp=
ed through.<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;"><u></u>=A0<u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;">ClockProfileType=A0TEXTUAL-CONVENTION definition<u></u><u>=
</u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;">Consider using and OUI instead of an enumeration. IEEE 158=
8-1588 requires an OUI be associated with each profile.<u></u><u></u></span=
></p>

<p><u></u><span style=3D"font-size:10.0pt;font-family:&quot;Courier New&quo=
t;"><span>-<span style=3D"font:7.0pt &quot;Times New Roman&quot;">=A0=A0=A0
</span></span></span><u></u><span style=3D"font-size:10.0pt;font-family:&qu=
ot;Courier New&quot;">TF: OUI would be specific to the organization, not th=
e profile. If the ITU (for instance) developed more than one profile, then =
they would have the same OUI. Therefore it
 is best (in the authors=92 opinion) to stick to using an enumeration<u></u=
><u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;"><u></u>=A0<u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;">OBJECT-TYPE general issues<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;">Consider being consistent about repeating=A0TEXTUAL-CONVEN=
TION descriptions, explicitly referencing them or assuming readers will tra=
ck down the reference without reminder.<u></u><u></u></span></p>

<p><u></u><span style=3D"font-size:10.0pt;font-family:&quot;Courier New&quo=
t;"><span>-<span style=3D"font:7.0pt &quot;Times New Roman&quot;">=A0=A0=A0
</span></span></span><u></u><span style=3D"font-size:10.0pt;font-family:&qu=
ot;Courier New&quot;">TF: We=92ve tried to be as consistent as we can. Of 1=
7 TEXTUAL-CONVENTIONS, 13 are directly referenced to IEEE1588 sections. The=
 remainder don=92t directly map onto IEEE1588
 quantities, but onto associated concepts, and we have tried to explain the=
se in the description. Certainly one could do with a better description, as=
 you note above.
<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;"><u></u>=A0<u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;">ptpDomainClockPortsTotal=A0OBJECT-TYPE<u></u><u></u></span=
></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;">I assume this is the number of ports for the managed PTP-c=
apable system (i.e. a router or switch). Suggest adding &quot;in the system=
&quot; to the description to clarify scope of count. - DONE<u></u><u></u></=
span></p>

<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;"><u></u>=A0<u></u></span></p>
<pre>ptpbaseClockTimePropertiesDSTable OBJECT-TYPE <u></u><u></u></pre>
<pre>s/clock Timeproperties Datasets for/clock time properties datasets for=
 - DONE<u></u><u></u></pre>
<pre><u></u>=A0<u></u></pre>
<pre>PtpbaseClockTransDefaultDSEntry SEQUENCE<u></u><u></u></pre>
<pre>Use ClockDomainType textual convention instead of Integer32 for ptpbas=
eClockTransDefaultDSPrimaryDomain - DONE<u></u><u></u></pre>
<pre><u></u>=A0<u></u></pre>
<pre>PtpbaseClockPortEntry SEQUENCE<u></u><u></u></pre>
<pre>Change ptpbaseClockPortSyncOneStep to ptpbaseClockPortSyncTwoStep to m=
atch 1588 semantics for this Boolean =96 DONE<u></u><u></u></pre>
<pre><u></u>=A0<u></u></pre>
<pre>ptpbaseClockPortRunningEncapsulationType OBJECT-TYPE<u></u><u></u></pr=
e>
<pre>Needs a textual convention or description of allowed values and their =
meanings<u></u><u></u></pre>
<pre style=3D"margin-left:.5in"><u></u><span>-<span style=3D"font:7.0pt &qu=
ot;Times New Roman&quot;">=A0=A0=A0 </span></span><u></u>TF: Now uses an au=
tonomous type instead of Integer32<u></u><u></u></pre>
<pre><u></u>=A0<u></u></pre>
<pre>ptpbaseClockPortTransDSlogMinPdelayReqInt OBJECT-TYPE<u></u><u></u></p=
re>
<pre>Change to ClockIntervalBase2 type DONE<u></u><u></u></pre>
<pre><u></u>=A0<u></u></pre>
<pre>Section 5: Copy-paste error: &quot;creation and/or manipulation of tun=
nels&quot;<u></u><u></u></pre>
<pre style=3D"margin-left:.5in"><u></u><span>-<span style=3D"font:7.0pt &qu=
ot;Times New Roman&quot;">=A0=A0=A0 </span></span><u></u>TF: Section change=
d since -03, no longer has this phrase.<u></u><u></u></pre>
<pre><u></u>=A0<u></u></pre>
<pre>Section 6: To be added - DONE<u></u><u></u></pre>
<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"><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">Best regards,<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">Tim Frost<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>
<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;"> <a href=
=3D"mailto:tictoc-bounces@ietf.org" target=3D"_blank">tictoc-bounces@ietf.o=
rg</a> [mailto:<a href=3D"mailto:tictoc-bounces@ietf.org" target=3D"_blank"=
>tictoc-bounces@ietf.org</a>]
<b>On Behalf Of </b>Kevin Gross<br>
<b>Sent:</b> 16 May 2013 18:09</span></p><div class=3D"im"><br>
<b>To:</b> Karen ODonoghue<br>
<b>Cc:</b> <a href=3D"mailto:tictoc@ietf.org" target=3D"_blank">tictoc@ietf=
.org</a><br>
<b>Subject:</b> Re: [TICTOC] WGLC on draft-ietf-tictoc-ptp-mib-05.txt<u></u=
><u></u></div><p></p>
</div>
<p class=3D"MsoNormal"><u></u>=A0<u></u></p>
<div>
<p class=3D"MsoNormal">I submitted comments on v03 11 January (<a href=3D"h=
ttp://www.ietf.org/mail-archive/web/tictoc/current/msg01331.html" target=3D=
"_blank">http://www.ietf.org/mail-archive/web/tictoc/current/msg01331.html<=
/a>). Vinay indicated in a short message on 23 January
 the comments would be addressed in the next version (<a href=3D"http://www=
.ietf.org/mail-archive/web/tictoc/current/msg01333.html" target=3D"_blank">=
http://www.ietf.org/mail-archive/web/tictoc/current/msg01333.html</a>). v04=
 was published 31 January. I did not see any notes from
 the authors associated with that revision. A quick check of the v03-v04 di=
ff shows evidence that not all my comments were directly addressed. Can I g=
et a summary of how my comments were addressed? I&#39;m fine if some of the=
se were rejected but I would like to
 verify that they were given consideration.<u></u><u></u></p>
</div><div><div class=3D"h5">
<div>
<p class=3D"MsoNormal"><br clear=3D"all">
<u></u><u></u></p>
<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>,=A0<a href=3D"http://www.X192.org" targe=
t=3D"_blank">www.X192.org</a><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 Thu, May 16, 2013 at 9:41 AM, Karen O&#39;Donoghu=
e &lt;<a href=3D"mailto:odonoghue@isoc.org" target=3D"_blank">odonoghue@iso=
c.org</a>&gt; wrote:<u></u><u></u></p>
<p class=3D"MsoNormal">This message initiates a two week TICTOC Working Gro=
up Last Call on advancing:<br>
<br>
Title : Precision Time Protocol Version 2 (PTPv2) Management Information Ba=
se<br>
Author(s) : Vinay Shankarkumar, Laurent Montini, Tim Frost, Greg Dowd<br>
Filename : draft-ietf-tictoc-ptp-mib-05.txt<br>
Pages : 77<br>
Date : 2013-02-25<br>
<br>
<a href=3D"http://datatracker.ietf.org/doc/draft-ietf-tictoc-ptp-mib/?inclu=
de_text=3D1" target=3D"_blank">http://datatracker.ietf.org/doc/draft-ietf-t=
ictoc-ptp-mib/?include_text=3D1</a><br>
<br>
as a Standards Track RFC. Substantive comments and statements of support fo=
r advancing this document should be directed to the mailing list. Editorial=
 suggestions can be sent directly to the authors. This last call will end o=
n 31 May 2013.<br>

<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><u></u><u></u></p>
</div>
<p class=3D"MsoNormal"><u></u>=A0<u></u></p>
</div>
</div></div></div>
</div>

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

--047d7b10ca13ff806204decfda85--

From btv1==87331abdaaf==gdowd@symmetricom.com  Mon Jun 10 11:00:13 2013
Return-Path: <btv1==87331abdaaf==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 0A4C021F9968 for <tictoc@ietfa.amsl.com>; Mon, 10 Jun 2013 11:00:13 -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 JbVE1MHtR1Cn for <tictoc@ietfa.amsl.com>; Mon, 10 Jun 2013 11:00:08 -0700 (PDT)
Received: from mail5.symmetricom.com (mail5.symmetricom.com [69.25.98.10]) by ietfa.amsl.com (Postfix) with ESMTP id 747CF21F9925 for <tictoc@ietf.org>; Mon, 10 Jun 2013 11:00:07 -0700 (PDT)
X-ASG-Debug-ID: 1370887206-05bdbc0700581f0001-4wH9i1
Received: from SJC-HUB-01.symmetricom.com ([192.168.10.171]) by mail5.symmetricom.com with ESMTP id tweeqUJCY80twH6a (version=TLSv1 cipher=AES128-SHA bits=128 verify=NO); Mon, 10 Jun 2013 11:00:06 -0700 (PDT)
X-Barracuda-Envelope-From: gdowd@symmetricom.com
X-ASG-Whitelist: Client
Received: from SJC-MBX-01.symmetricom.com ([169.254.1.186]) by SJC-HUB-01.symmetricom.com ([::1]) with mapi id 14.01.0289.001; Mon, 10 Jun 2013 11:00:05 -0700
From: Greg Dowd <gdowd@symmetricom.com>
To: Kevin Gross <kevin.gross@avanw.com>, Tim Frost <tfrost@symmetricom.com>
Thread-Topic: [TICTOC] WGLC on draft-ietf-tictoc-ptp-mib-05.txt
X-ASG-Orig-Subj: RE: [TICTOC] WGLC on draft-ietf-tictoc-ptp-mib-05.txt
Thread-Index: AQHOUkve8l3OF4TVM0S7AgdJPsfOkpkIgNuAgAECRwCAJkhkAP//l7YQ
Date: Mon, 10 Jun 2013 18:00:05 +0000
Message-ID: <26FBD265CD8D234EAF41115A180F92BB6ECD10CB@SJC-MBX-01.symmetricom.com>
References: <5194FE2F.2060504@isoc.org> <CALw1_Q3DxKFc+oNFj_0iyDPp4m59hNS3--7R+nX_i1OzOaeT-g@mail.gmail.com> <4A4385BFBA1BC54C863E7394BD1AECB36EB1C82C@SJC-MBX-01.symmetricom.com> <CALw1_Q1D+iCamS4j1C=GEvsehJ1wYTbFz9y34m12nurW7RgfNQ@mail.gmail.com>
In-Reply-To: <CALw1_Q1D+iCamS4j1C=GEvsehJ1wYTbFz9y34m12nurW7RgfNQ@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.9]
Content-Type: multipart/alternative; boundary="_000_26FBD265CD8D234EAF41115A180F92BB6ECD10CBSJCMBX01symmetr_"
MIME-Version: 1.0
X-Barracuda-Connect: UNKNOWN[192.168.10.171]
X-Barracuda-Start-Time: 1370887206
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: "tictoc@ietf.org" <tictoc@ietf.org>, Karen ODonoghue <odonoghue@isoc.org>
Subject: Re: [TICTOC] WGLC on draft-ietf-tictoc-ptp-mib-05.txt
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, 10 Jun 2013 18:00:47 -0000

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

I think the confusion was that your comment suggested using an OUI, not a p=
rofile OID (EUI-48).  The OUI would not have been sufficient to distinguish=
 multiple profiles from an organization as Tim noted.  I'll review your com=
ments with the team.  Thanks!

Greg Dowd | Symmetricom(r), Inc.
Staff Scientist
2300 Orchard Parkway, San Jose, CA 95131
Direct:  408.964.7643
gdowd@symmetricom.com<mailto:gdowd@symmetricom.com>  |  www.symmetricom.com=
<http://www.symmetricom.com/>
Symmetricom.  Leading the world in precise time solutions.

From: tictoc-bounces@ietf.org [mailto:tictoc-bounces@ietf.org] On Behalf Of=
 Kevin Gross
Sent: Monday, June 10, 2013 10:10 AM
To: Tim Frost
Cc: tictoc@ietf.org; Karen ODonoghue
Subject: Re: [TICTOC] WGLC on draft-ietf-tictoc-ptp-mib-05.txt

Thanks for addressing my comments. It looks like there are two outstanding.

  1.  ClockInstanceType and
  2.  ClockProfileType
It sounds like you intend to address (1) in a future revision.

With regards to (2), I think you misunderstand how the profileIdentifier wo=
rks. Please have a look at Section 19.3.3 of IEEE 1588-2008. This is an EUI=
-48, not merely an OUI. Organizations can change the bottom 24 bits to indi=
cate new profiles or revisions of existing ones. Maintaining our own enumer=
ation of profiles does not seem like a feasible undertaking.

Kevin Gross
+1-303-447-0517
Media Network Consultant
AVA Networks - www.AVAnw.com<http://www.avanw.com/>, www.X192.org<http://ww=
w.X192.org>

On Fri, May 17, 2013 at 2:33 AM, Tim Frost <tfrost@symmetricom.com<mailto:t=
frost@symmetricom.com>> wrote:
Hi Kevin,

Thank you for taking the time to go through this MIB. We did consider your =
comments, and they were addressed in -05 (the latest version, and the subje=
ct of the last call).  I've gone through each of your comments below; it lo=
oks like we missed one, and decided against another, but the remainder have=
 been done.

The change history from the -05 draft reads:

-05       Feb 13 Several changes in response to comments from Alun Luchuk
             and Kevin Gross:
             - Modified the use of wellKnownTransportTypes and
               wellKnownEncapsulationTypes
             - changed ptpbaseClockPortSyncOneStep to
               ptpbaseClockPortSyncTwoStep to match IEEE1588
               semantics
             - Re-ordered textual conventions to be alphabetic
             - Changed some types from Integer32 to use defined
               textual conventions
             - various minor descriptive text changes

In detail:
Abstract: Add a bracketed reference to IEEE 1588-2008 - DONE

Section 1: s/defined to monitor, measure the performance/defined to monitor=
 and measure the performance - DONE

Section 1.1 What in this MIB is profile dependent? I did not identify anyth=
ing in my review. It would be desirable. if possible,  to have a profile-in=
dependent MIB.

-    TF: Removed erroneous text about Telecom Profile - there is nothing in=
 this MIB that is particular to that profile.

TEXTUAL-CONVENTION general issues - Consider alphabetizing - DONE

ClockInstanceType TEXTUAL-CONVENTION definition - Description requires eluc=
idation or a reference.

-    TF: not done, looks like this one slipped through.

ClockProfileType TEXTUAL-CONVENTION definition
Consider using and OUI instead of an enumeration. IEEE 1588-1588 requires a=
n OUI be associated with each profile.

-    TF: OUI would be specific to the organization, not the profile. If the=
 ITU (for instance) developed more than one profile, then they would have t=
he same OUI. Therefore it is best (in the authors' opinion) to stick to usi=
ng an enumeration

OBJECT-TYPE general issues
Consider being consistent about repeating TEXTUAL-CONVENTION descriptions, =
explicitly referencing them or assuming readers will track down the referen=
ce without reminder.

-    TF: We've tried to be as consistent as we can. Of 17 TEXTUAL-CONVENTIO=
NS, 13 are directly referenced to IEEE1588 sections. The remainder don't di=
rectly map onto IEEE1588 quantities, but onto associated concepts, and we h=
ave tried to explain these in the description. Certainly one could do with =
a better description, as you note above.

ptpDomainClockPortsTotal OBJECT-TYPE
I assume this is the number of ports for the managed PTP-capable system (i.=
e. a router or switch). Suggest adding "in the system" to the description t=
o clarify scope of count. - DONE


ptpbaseClockTimePropertiesDSTable OBJECT-TYPE

s/clock Timeproperties Datasets for/clock time properties datasets for - DO=
NE



PtpbaseClockTransDefaultDSEntry SEQUENCE

Use ClockDomainType textual convention instead of Integer32 for ptpbaseCloc=
kTransDefaultDSPrimaryDomain - DONE



PtpbaseClockPortEntry SEQUENCE

Change ptpbaseClockPortSyncOneStep to ptpbaseClockPortSyncTwoStep to match =
1588 semantics for this Boolean - DONE



ptpbaseClockPortRunningEncapsulationType OBJECT-TYPE

Needs a textual convention or description of allowed values and their meani=
ngs

-    TF: Now uses an autonomous type instead of Integer32



ptpbaseClockPortTransDSlogMinPdelayReqInt OBJECT-TYPE

Change to ClockIntervalBase2 type DONE



Section 5: Copy-paste error: "creation and/or manipulation of tunnels"

-    TF: Section changed since -03, no longer has this phrase.



Section 6: To be added - DONE


Best regards,
Tim Frost

From: tictoc-bounces@ietf.org<mailto:tictoc-bounces@ietf.org> [mailto:ticto=
c-bounces@ietf.org<mailto:tictoc-bounces@ietf.org>] On Behalf Of Kevin Gros=
s
Sent: 16 May 2013 18:09

To: Karen ODonoghue
Cc: tictoc@ietf.org<mailto:tictoc@ietf.org>
Subject: Re: [TICTOC] WGLC on draft-ietf-tictoc-ptp-mib-05.txt

I submitted comments on v03 11 January (http://www.ietf.org/mail-archive/we=
b/tictoc/current/msg01331.html). Vinay indicated in a short message on 23 J=
anuary the comments would be addressed in the next version (http://www.ietf=
.org/mail-archive/web/tictoc/current/msg01333.html). v04 was published 31 J=
anuary. I did not see any notes from the authors associated with that revis=
ion. A quick check of the v03-v04 diff shows evidence that not all my comme=
nts were directly addressed. Can I get a summary of how my comments were ad=
dressed? I'm fine if some of these were rejected but I would like to verify=
 that they were given consideration.

Kevin Gross
+1-303-447-0517<tel:%2B1-303-447-0517>
Media Network Consultant
AVA Networks - www.AVAnw.com<http://www.avanw.com/>, www.X192.org<http://ww=
w.X192.org>

On Thu, May 16, 2013 at 9:41 AM, Karen O'Donoghue <odonoghue@isoc.org<mailt=
o:odonoghue@isoc.org>> wrote:
This message initiates a two week TICTOC Working Group Last Call on advanci=
ng:

Title : Precision Time Protocol Version 2 (PTPv2) Management Information Ba=
se
Author(s) : Vinay Shankarkumar, Laurent Montini, Tim Frost, Greg Dowd
Filename : draft-ietf-tictoc-ptp-mib-05.txt
Pages : 77
Date : 2013-02-25

http://datatracker.ietf.org/doc/draft-ietf-tictoc-ptp-mib/?include_text=3D1

as a Standards Track RFC. Substantive comments and statements of support fo=
r advancing this document should be directed to the mailing list. Editorial=
 suggestions can be sent directly to the authors. This last call will end o=
n 31 May 2013.

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



--_000_26FBD265CD8D234EAF41115A180F92BB6ECD10CBSJCMBX01symmetr_
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: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;}
@font-face
	{font-family:Consolas;
	panose-1:2 11 6 9 2 2 4 3 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
	{mso-style-priority:99;
	mso-margin-top-alt:auto;
	margin-right:0in;
	mso-margin-bottom-alt:auto;
	margin-left:0in;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";}
pre
	{mso-style-priority:99;
	mso-style-link:"HTML Preformatted Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:10.0pt;
	font-family:"Courier New";}
span.HTMLPreformattedChar
	{mso-style-name:"HTML Preformatted Char";
	mso-style-priority:99;
	mso-style-link:"HTML Preformatted";
	font-family:Consolas;}
span.EmailStyle20
	{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;}
 /* List Definitions */
 @list l0
	{mso-list-id:1870675722;
	mso-list-template-ids:841663420;}
ol
	{margin-bottom:0in;}
ul
	{margin-bottom:0in;}
-->
</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">I think the confusion was that your comment suggested using =
an OUI, not a profile OID (EUI-48).&nbsp; The OUI would not have been suffi=
cient to distinguish multiple
 profiles from an organization as Tim noted.&nbsp; I&#8217;ll review your c=
omments with the team.&nbsp; Thanks!<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" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-family:&quot;Calibri&quot;,&quot;sans-serif&qu=
ot;;color:gray">Greg Dowd&nbsp;|&nbsp;</span><b><span style=3D"font-family:=
&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#00B0F0">Symmetricom&reg;,=
 Inc.</span></b><span style=3D"font-size:9.0pt;font-family:&quot;Arial&quot=
;,&quot;sans-serif&quot;;color:black"><o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><i><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;=
,&quot;sans-serif&quot;;color:gray">Staff Scientist&nbsp;</span></i><span s=
tyle=3D"font-size:9.0pt;font-family:&quot;Arial&quot;,&quot;sans-serif&quot=
;;
color:black"><br>
</span><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&quo=
t;sans-serif&quot;;
color:gray">2300 Orchard Parkway, San Jose, CA 95131<br>
Direct:&nbsp; 408.964.7643&nbsp;</span><span style=3D"font-size:9.0pt;font-=
family:
&quot;Arial&quot;,&quot;sans-serif&quot;;color:black"><br>
</span><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&quo=
t;sans-serif&quot;;
color:gray"><a href=3D"mailto:gdowd@symmetricom.com"><span style=3D"color:g=
ray">gdowd@symmetricom.com</span></a>&nbsp;&nbsp;|&nbsp;&nbsp;<a href=3D"ht=
tp://www.symmetricom.com/"><span style=3D"color:gray">www.symmetricom.com</=
span></a><o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><i><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;=
,&quot;sans-serif&quot;;color:#00B0F0">Symmetricom.&nbsp; Leading the world=
 in precise time solutions.</span></i><span style=3D"font-size:
9.0pt;font-family:&quot;Arial&quot;,&quot;sans-serif&quot;;color:black"><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 Gross<br>
<b>Sent:</b> Monday, June 10, 2013 10:10 AM<br>
<b>To:</b> Tim Frost<br>
<b>Cc:</b> tictoc@ietf.org; Karen ODonoghue<br>
<b>Subject:</b> Re: [TICTOC] WGLC on draft-ietf-tictoc-ptp-mib-05.txt<o:p><=
/o:p></span></p>
</div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<div>
<p class=3D"MsoNormal">Thanks for addressing my comments. It looks like the=
re are two outstanding.<o:p></o:p></p>
<div>
<ol start=3D"1" type=3D"1">
<li class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-=
alt:auto;
     mso-list:l0 level1 lfo1">
ClockInstanceType and<o:p></o:p> </li><li class=3D"MsoNormal" style=3D"mso-=
margin-top-alt:auto;mso-margin-bottom-alt:auto;
     mso-list:l0 level1 lfo1">
ClockProfileType<o:p></o:p> </li></ol>
</div>
<div>
<p class=3D"MsoNormal">It sounds like you intend to address (1) in a future=
 revision.<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<div>
<p class=3D"MsoNormal">With regards to (2), I think you misunderstand how t=
he profileIdentifier works. Please have a look at Section 19.3.3 of IEEE 15=
88-2008. This is an EUI-48, not merely an OUI. Organizations can change the=
 bottom 24 bits to indicate new profiles
 or revisions of existing ones. Maintaining our own enumeration of profiles=
 does not seem like a feasible undertaking.<o:p></o:p></p>
</div>
</div>
<div>
<p class=3D"MsoNormal"><br clear=3D"all">
<o:p></o:p></p>
<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>,&nbsp;<a href=3D"http://www.X192.org"=
 target=3D"_blank">www.X192.org</a><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 Fri, May 17, 2013 at 2:33 AM, Tim Frost &lt;<a hr=
ef=3D"mailto:tfrost@symmetricom.com" target=3D"_blank">tfrost@symmetricom.c=
om</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">Hi Kevin,</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">Thank you for taking the time to go thr=
ough this MIB. We did consider your comments, and they were
 addressed in -05 (the latest version, and the subject of the last call).&n=
bsp; I&#8217;ve gone through each of your comments below; it looks like we =
missed one, and decided against another, but the remainder have been done.<=
/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">The change history from the -05 draft r=
eads:
</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">-05&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Feb 13 Several changes in =
response to comments from Alun Luchuk<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; an=
d Kevin Gross:<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; - =
Modified the use of wellKnownTransportTypes and<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;wellKnownEncapsulationTypes<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; - =
changed ptpbaseClockPortSyncOneStep to<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp; ptpbaseClockPortSyncTwoStep to match IEEE1588<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp; semantics<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; - =
Re-ordered textual conventions to be alphabetic<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; - =
Changed some types from Integer32 to use defined<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp; textual conventions<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; - =
various minor descriptive text changes<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;margin-bottom:12.0p=
t"><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sa=
ns-serif&quot;;color:#1F497D">In detail:</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:10.0pt;font-family:&quot;Courier New&quot=
;">Abstract: Add a bracketed reference to IEEE 1588-2008 - DONE</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:10.0pt;font-family:&quot;Courier New&quot=
;">&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:10.0pt;font-family:&quot;Courier New&quot=
;">Section 1: s/defined to monitor, measure the performance/defined to moni=
tor and measure the performance - DONE</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:10.0pt;font-family:&quot;Courier New&quot=
;">&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:10.0pt;font-family:&quot;Courier New&quot=
;">Section 1.1 What in this MIB is profile dependent? I did not identify an=
ything in my review. It would be&nbsp;desirable. if possible,&nbsp;&nbsp;to
 have a profile-independent MIB.</span><o:p></o:p></p>
<p><span style=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;">-</=
span><span style=3D"font-size:7.0pt">&nbsp;&nbsp;&nbsp;
</span><span style=3D"font-size:10.0pt;
font-family:&quot;Courier New&quot;">TF: Removed erroneous text about Telec=
om Profile &#8211; there is nothing in this MIB that is particular to that =
profile.
</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:10.0pt;font-family:&quot;Courier New&quot=
;">&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:10.0pt;font-family:&quot;Courier New&quot=
;">TEXTUAL-CONVENTION general issues - Consider alphabetizing - DONE</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:10.0pt;font-family:&quot;Courier New&quot=
;">&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:10.0pt;font-family:&quot;Courier New&quot=
;;color:#C00000">ClockInstanceType TEXTUAL-CONVENTION definition - Descript=
ion requires elucidation or a reference.
</span><o:p></o:p></p>
<p><span style=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;;colo=
r:#C00000">-</span><span style=3D"font-size:7.0pt;color:#C00000">&nbsp;&nbs=
p;&nbsp;
</span><span style=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;;=
color:#C00000">TF: not done, looks like this one slipped through.</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:10.0pt;font-family:&quot;Courier New&quot=
;">&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:10.0pt;font-family:&quot;Courier New&quot=
;">ClockProfileType&nbsp;TEXTUAL-CONVENTION definition</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:10.0pt;font-family:&quot;Courier New&quot=
;">Consider using and OUI instead of an enumeration. IEEE 1588-1588 require=
s an OUI be associated with each profile.</span><o:p></o:p></p>
<p><span style=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;">-</=
span><span style=3D"font-size:7.0pt">&nbsp;&nbsp;&nbsp;
</span><span style=3D"font-size:10.0pt;
font-family:&quot;Courier New&quot;">TF: OUI would be specific to the organ=
ization, not the profile. If the ITU (for instance) developed more than one=
 profile, then they would have the same OUI. Therefore it is best (in the a=
uthors&#8217;
 opinion) to stick to using an enumeration</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:10.0pt;font-family:&quot;Courier New&quot=
;">&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:10.0pt;font-family:&quot;Courier New&quot=
;">OBJECT-TYPE general issues</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:10.0pt;font-family:&quot;Courier New&quot=
;">Consider being consistent about repeating&nbsp;TEXTUAL-CONVENTION descri=
ptions, explicitly referencing them or assuming readers
 will track down the reference without reminder.</span><o:p></o:p></p>
<p><span style=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;">-</=
span><span style=3D"font-size:7.0pt">&nbsp;&nbsp;&nbsp;
</span><span style=3D"font-size:10.0pt;
font-family:&quot;Courier New&quot;">TF: We&#8217;ve tried to be as consist=
ent as we can. Of 17 TEXTUAL-CONVENTIONS, 13 are directly referenced to IEE=
E1588 sections. The remainder don&#8217;t directly map onto IEEE1588 quanti=
ties, but onto
 associated concepts, and we have tried to explain these in the description=
. Certainly one could do with a better description, as you note above.
</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:10.0pt;font-family:&quot;Courier New&quot=
;">&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:10.0pt;font-family:&quot;Courier New&quot=
;">ptpDomainClockPortsTotal&nbsp;OBJECT-TYPE</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:10.0pt;font-family:&quot;Courier New&quot=
;">I assume this is the number of ports for the managed PTP-capable system =
(i.e. a router or switch). Suggest adding &quot;in the
 system&quot; to the description to clarify scope of count. - DONE</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:10.0pt;font-family:&quot;Courier New&quot=
;">&nbsp;</span><o:p></o:p></p>
<pre>ptpbaseClockTimePropertiesDSTable OBJECT-TYPE <o:p></o:p></pre>
<pre>s/clock Timeproperties Datasets for/clock time properties datasets for=
 - DONE<o:p></o:p></pre>
<pre>&nbsp;<o:p></o:p></pre>
<pre>PtpbaseClockTransDefaultDSEntry SEQUENCE<o:p></o:p></pre>
<pre>Use ClockDomainType textual convention instead of Integer32 for ptpbas=
eClockTransDefaultDSPrimaryDomain - DONE<o:p></o:p></pre>
<pre>&nbsp;<o:p></o:p></pre>
<pre>PtpbaseClockPortEntry SEQUENCE<o:p></o:p></pre>
<pre>Change ptpbaseClockPortSyncOneStep to ptpbaseClockPortSyncTwoStep to m=
atch 1588 semantics for this Boolean &#8211; DONE<o:p></o:p></pre>
<pre>&nbsp;<o:p></o:p></pre>
<pre>ptpbaseClockPortRunningEncapsulationType OBJECT-TYPE<o:p></o:p></pre>
<pre>Needs a textual convention or description of allowed values and their =
meanings<o:p></o:p></pre>
<pre style=3D"margin-left:.5in">-<span style=3D"font-size:7.0pt;font-family=
:&quot;Times New Roman&quot;,&quot;serif&quot;">&nbsp;&nbsp;&nbsp; </span>T=
F: Now uses an autonomous type instead of Integer32<o:p></o:p></pre>
<pre>&nbsp;<o:p></o:p></pre>
<pre>ptpbaseClockPortTransDSlogMinPdelayReqInt OBJECT-TYPE<o:p></o:p></pre>
<pre>Change to ClockIntervalBase2 type DONE<o:p></o:p></pre>
<pre>&nbsp;<o:p></o:p></pre>
<pre>Section 5: Copy-paste error: &quot;creation and/or manipulation of tun=
nels&quot;<o:p></o:p></pre>
<pre style=3D"margin-left:.5in">-<span style=3D"font-size:7.0pt;font-family=
:&quot;Times New Roman&quot;,&quot;serif&quot;">&nbsp;&nbsp;&nbsp; </span>T=
F: Section changed since -03, no longer has this phrase.<o:p></o:p></pre>
<pre>&nbsp;<o:p></o:p></pre>
<pre>Section 6: To be added - DONE<o:p></o:p></pre>
<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">Best 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">Tim Frost</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>
<div style=3D"border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in =
0in 0in">
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><b><span style=3D"font-size:10.0pt;font-family:&quot;Tahoma&quot;,=
&quot;sans-serif&quot;">From:</span></b><span style=3D"font-size:10.0pt;fon=
t-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>Kevin Gross<br>
<b>Sent:</b> 16 May 2013 18:09</span><o:p></o:p></p>
<div>
<p class=3D"MsoNormal"><br>
<b>To:</b> Karen ODonoghue<br>
<b>Cc:</b> <a href=3D"mailto:tictoc@ietf.org" target=3D"_blank">tictoc@ietf=
.org</a><br>
<b>Subject:</b> Re: [TICTOC] WGLC on draft-ietf-tictoc-ptp-mib-05.txt<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>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">I submitted comments on v03 11 January (<a href=3D"http://www.ietf=
.org/mail-archive/web/tictoc/current/msg01331.html" target=3D"_blank">http:=
//www.ietf.org/mail-archive/web/tictoc/current/msg01331.html</a>).
 Vinay indicated in a short message on 23 January the comments would be add=
ressed in the next version (<a href=3D"http://www.ietf.org/mail-archive/web=
/tictoc/current/msg01333.html" target=3D"_blank">http://www.ietf.org/mail-a=
rchive/web/tictoc/current/msg01333.html</a>).
 v04 was published 31 January. I did not see any notes from the authors ass=
ociated with that revision. A quick check of the v03-v04 diff shows evidenc=
e that not all my comments were directly addressed. Can I get a summary of =
how my comments were addressed?
 I'm fine if some of these were rejected but I would like to verify that th=
ey were given consideration.<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 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">Kevin Gross<o:p></o:p></p>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><a href=3D"tel:%2B1-303-447-0517" target=3D"_blank">&#43;1-303-447=
-0517</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">Media Network Consultant<o:p></o:p></p>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">AVA Networks -&nbsp;<a href=3D"http://www.avanw.com/" target=3D"_b=
lank">www.AVAnw.com</a>,&nbsp;<a href=3D"http://www.X192.org" target=3D"_bl=
ank">www.X192.org</a><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 Thu, May 16, 2013 at 9:41 AM, Karen O'Donoghue &lt;<a href=3D"m=
ailto:odonoghue@isoc.org" target=3D"_blank">odonoghue@isoc.org</a>&gt; wrot=
e:<o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">This message initiates a two week TICTOC Working Group Last Call o=
n advancing:<br>
<br>
Title : Precision Time Protocol Version 2 (PTPv2) Management Information Ba=
se<br>
Author(s) : Vinay Shankarkumar, Laurent Montini, Tim Frost, Greg Dowd<br>
Filename : draft-ietf-tictoc-ptp-mib-05.txt<br>
Pages : 77<br>
Date : 2013-02-25<br>
<br>
<a href=3D"http://datatracker.ietf.org/doc/draft-ietf-tictoc-ptp-mib/?inclu=
de_text=3D1" target=3D"_blank">http://datatracker.ietf.org/doc/draft-ietf-t=
ictoc-ptp-mib/?include_text=3D1</a><br>
<br>
as a Standards Track RFC. Substantive comments and statements of support fo=
r advancing this document should be directed to the mailing list. Editorial=
 suggestions can be sent directly to the authors. This last call will end o=
n 31 May 2013.<br>
<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>
<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>
</div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
</div>
</body>
</html>

--_000_26FBD265CD8D234EAF41115A180F92BB6ECD10CBSJCMBX01symmetr_--

From kevin.gross@avanw.com  Mon Jun 10 11:23:58 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 72F6A21F866E for <tictoc@ietfa.amsl.com>; Mon, 10 Jun 2013 11:23:57 -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 jTlyXjeTaGF4 for <tictoc@ietfa.amsl.com>; Mon, 10 Jun 2013 11:23:52 -0700 (PDT)
Received: from qmta09.emeryville.ca.mail.comcast.net (qmta09.emeryville.ca.mail.comcast.net [IPv6:2001:558:fe2d:43:76:96:30:96]) by ietfa.amsl.com (Postfix) with ESMTP id 8370321F8617 for <tictoc@ietf.org>; Mon, 10 Jun 2013 11:23:47 -0700 (PDT)
Received: from omta22.emeryville.ca.mail.comcast.net ([76.96.30.89]) by qmta09.emeryville.ca.mail.comcast.net with comcast id mhGM1l0031vN32cA9iPn4b; Mon, 10 Jun 2013 18:23:47 +0000
Received: from mail-ie0-x229.google.com ([IPv6:2607:f8b0:4001:c03::229]) by omta22.emeryville.ca.mail.comcast.net with comcast id miPm1l0094jVWYZ8iiPmDK; Mon, 10 Jun 2013 18:23:46 +0000
Received: by mail-ie0-f169.google.com with SMTP id 10so3543349ied.14 for <tictoc@ietf.org>; Mon, 10 Jun 2013 11:23:46 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=U9rJ1kfzIjl8UpxJWtOui/9QzFiiPUdkaDGNzudsDwY=; b=pVU5bKhhwzRibp1sq1DLH0r5/BjYuBPZTRIOwrMeP8nC9pV5IwwtE7/hTBrG6Rk4TW zR6h52x3Deth2sp4ChIRvDeev1IWPaWv/rynQhwVteI8tJbVu6kzCKL7VskHPiYiJh2P +ljC9+vGPCUaCN8go5Nq2T3omXNHbt6e0M/aNR6AwXM6e2ahEYC1om4gq3ybU7u0IgDs h59r9rjVO9WI5ZODn5GrOGETBCwrZUA9/HB2nI29t6UUnkmDd8rruSYVto1i1bTlwyYt eTQB9YHaGRJjZaaNI7D+csTPsr8N3rXQE+m5ws4ctfGhjEkovKFNfU74q4ejCM4pLPGp A6uQ==
MIME-Version: 1.0
X-Received: by 10.50.114.131 with SMTP id jg3mr4699970igb.75.1370888626171; Mon, 10 Jun 2013 11:23:46 -0700 (PDT)
Received: by 10.50.149.199 with HTTP; Mon, 10 Jun 2013 11:23:46 -0700 (PDT)
In-Reply-To: <26FBD265CD8D234EAF41115A180F92BB6ECD10CB@SJC-MBX-01.symmetricom.com>
References: <5194FE2F.2060504@isoc.org> <CALw1_Q3DxKFc+oNFj_0iyDPp4m59hNS3--7R+nX_i1OzOaeT-g@mail.gmail.com> <4A4385BFBA1BC54C863E7394BD1AECB36EB1C82C@SJC-MBX-01.symmetricom.com> <CALw1_Q1D+iCamS4j1C=GEvsehJ1wYTbFz9y34m12nurW7RgfNQ@mail.gmail.com> <26FBD265CD8D234EAF41115A180F92BB6ECD10CB@SJC-MBX-01.symmetricom.com>
Date: Mon, 10 Jun 2013 12:23:46 -0600
Message-ID: <CALw1_Q3rETjG-FwRaG9-BfNCwJs_RfXm6CsChv2AA1v=Bqdffw@mail.gmail.com>
From: Kevin Gross <kevin.gross@avanw.com>
To: Greg Dowd <gdowd@symmetricom.com>
Content-Type: multipart/alternative; boundary=089e0122ac4c96f8bd04ded0e165
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20121106; t=1370888627; bh=U9rJ1kfzIjl8UpxJWtOui/9QzFiiPUdkaDGNzudsDwY=; h=Received:Received:Received:MIME-Version:Received:Date:Message-ID: Subject:From:To:Content-Type; b=n1WXiUmMHtAsc/gmnS1x4QrAFS0zl5+d8rvABqsuyJ8PmoAtpQbNcRrKRiXhUvXf7 WjQrFyAdxnIzsjyH1C4+1Sz9kUsns7VMHOeNiSJ6BzgiFyiyS2NPktz7JfnTSoIu0B 7OVXwVqS0MCT+oI2p3/VrHroJ/NRxjYsbKvtGe8bAOcV7XPGNeRQV4j35igja/l3vM uxPpUo9RrYG5962RMGm4p/2gHZJAEZPEdBki58ZGjQ3fA1cIQMA9fFImOB+nyKXseU Dq7e5l1zIZ2lY4Y2i/0ANGNS1UaxIFm61rIwp5uywL6ZizOcDiOAFFfJh2gAAS1K5h d/pfcQqRwr3NA==
Cc: "tictoc@ietf.org" <tictoc@ietf.org>, Karen ODonoghue <odonoghue@isoc.org>
Subject: Re: [TICTOC] WGLC on draft-ietf-tictoc-ptp-mib-05.txt
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, 10 Jun 2013 18:23:59 -0000

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

My original proposal was incorrect. I think we're on the right track now.

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


On Mon, Jun 10, 2013 at 12:00 PM, Greg Dowd <gdowd@symmetricom.com> wrote:

>  I think the confusion was that your comment suggested using an OUI, not
> a profile OID (EUI-48).  The OUI would not have been sufficient to
> distinguish multiple profiles from an organization as Tim noted.  I=92ll
> review your comments with the team.  Thanks!****
>
> ** **
>
> Greg Dowd | *Symmetricom=AE, Inc.*****
>
> *Staff Scientist *
> 2300 Orchard Parkway, San Jose, CA 95131
> Direct:  408.964.7643
> gdowd@symmetricom.com  |  www.symmetricom.com****
>
> *Symmetricom.  Leading the world in precise time solutions.*****
>
> ** **
>
> *From:* tictoc-bounces@ietf.org [mailto:tictoc-bounces@ietf.org] *On
> Behalf Of *Kevin Gross
> *Sent:* Monday, June 10, 2013 10:10 AM
> *To:* Tim Frost
> *Cc:* tictoc@ietf.org; Karen ODonoghue
>
> *Subject:* Re: [TICTOC] WGLC on draft-ietf-tictoc-ptp-mib-05.txt****
>
>  ** **
>
> Thanks for addressing my comments. It looks like there are two outstandin=
g.
> ****
>
>    1. ClockInstanceType and****
>    2. ClockProfileType****
>
>  It sounds like you intend to address (1) in a future revision.****
>
> ** **
>
> With regards to (2), I think you misunderstand how the profileIdentifier
> works. Please have a look at Section 19.3.3 of IEEE 1588-2008. This is an
> EUI-48, not merely an OUI. Organizations can change the bottom 24 bits to
> indicate new profiles or revisions of existing ones. Maintaining our own
> enumeration of profiles does not seem like a feasible undertaking.****
>
>
> ****
>
> Kevin Gross****
>
> +1-303-447-0517****
>
> Media Network Consultant****
>
> AVA Networks - www.AVAnw.com <http://www.avanw.com/>, www.X192.org****
>
> ** **
>
> On Fri, May 17, 2013 at 2:33 AM, Tim Frost <tfrost@symmetricom.com> wrote=
:
> ****
>
> Hi Kevin,****
>
>  ****
>
> Thank you for taking the time to go through this MIB. We did consider you=
r
> comments, and they were addressed in -05 (the latest version, and the
> subject of the last call).  I=92ve gone through each of your comments bel=
ow;
> it looks like we missed one, and decided against another, but the remaind=
er
> have been done.****
>
>  ****
>
> The change history from the -05 draft reads: ****
>
>  ****
>
> -05       Feb 13 Several changes in response to comments from Alun Luchuk
>              and Kevin Gross:
>              - Modified the use of wellKnownTransportTypes and
>                wellKnownEncapsulationTypes
>              - changed ptpbaseClockPortSyncOneStep to
>                ptpbaseClockPortSyncTwoStep to match IEEE1588
>                semantics
>              - Re-ordered textual conventions to be alphabetic
>              - Changed some types from Integer32 to use defined
>                textual conventions
>              - various minor descriptive text changes****
>
>  ****
>
> In detail:****
>
> Abstract: Add a bracketed reference to IEEE 1588-2008 - DONE****
>
>  ****
>
> Section 1: s/defined to monitor, measure the performance/defined to
> monitor and measure the performance - DONE****
>
>  ****
>
> Section 1.1 What in this MIB is profile dependent? I did not identify
> anything in my review. It would be desirable. if possible,  to have a
> profile-independent MIB.****
>
> -    TF: Removed erroneous text about Telecom Profile =96 there is nothin=
g
> in this MIB that is particular to that profile. ****
>
>  ****
>
> TEXTUAL-CONVENTION general issues - Consider alphabetizing - DONE****
>
>  ****
>
> ClockInstanceType TEXTUAL-CONVENTION definition - Description requires
> elucidation or a reference. ****
>
> -    TF: not done, looks like this one slipped through.****
>
>  ****
>
> ClockProfileType TEXTUAL-CONVENTION definition****
>
> Consider using and OUI instead of an enumeration. IEEE 1588-1588 requires
> an OUI be associated with each profile.****
>
> -    TF: OUI would be specific to the organization, not the profile. If
> the ITU (for instance) developed more than one profile, then they would
> have the same OUI. Therefore it is best (in the authors=92 opinion) to st=
ick
> to using an enumeration****
>
>  ****
>
> OBJECT-TYPE general issues****
>
> Consider being consistent about repeating TEXTUAL-CONVENTION descriptions=
,
> explicitly referencing them or assuming readers will track down the
> reference without reminder.****
>
> -    TF: We=92ve tried to be as consistent as we can. Of 17
> TEXTUAL-CONVENTIONS, 13 are directly referenced to IEEE1588 sections. The
> remainder don=92t directly map onto IEEE1588 quantities, but onto associa=
ted
> concepts, and we have tried to explain these in the description. Certainl=
y
> one could do with a better description, as you note above. ****
>
>  ****
>
> ptpDomainClockPortsTotal OBJECT-TYPE****
>
> I assume this is the number of ports for the managed PTP-capable system
> (i.e. a router or switch). Suggest adding "in the system" to the
> description to clarify scope of count. - DONE****
>
>  ****
>
> ptpbaseClockTimePropertiesDSTable OBJECT-TYPE ****
>
> s/clock Timeproperties Datasets for/clock time properties datasets for - =
DONE****
>
>  ****
>
> PtpbaseClockTransDefaultDSEntry SEQUENCE****
>
> Use ClockDomainType textual convention instead of Integer32 for ptpbaseCl=
ockTransDefaultDSPrimaryDomain - DONE****
>
>  ****
>
> PtpbaseClockPortEntry SEQUENCE****
>
> Change ptpbaseClockPortSyncOneStep to ptpbaseClockPortSyncTwoStep to matc=
h 1588 semantics for this Boolean =96 DONE****
>
>  ****
>
> ptpbaseClockPortRunningEncapsulationType OBJECT-TYPE****
>
> Needs a textual convention or description of allowed values and their mea=
nings****
>
> -    TF: Now uses an autonomous type instead of Integer32****
>
>  ****
>
> ptpbaseClockPortTransDSlogMinPdelayReqInt OBJECT-TYPE****
>
> Change to ClockIntervalBase2 type DONE****
>
>  ****
>
> Section 5: Copy-paste error: "creation and/or manipulation of tunnels"***=
*
>
> -    TF: Section changed since -03, no longer has this phrase.****
>
>  ****
>
> Section 6: To be added - DONE****
>
>  ****
>
>  ****
>
> Best regards,****
>
> Tim Frost****
>
>  ****
>
> *From:* tictoc-bounces@ietf.org [mailto:tictoc-bounces@ietf.org] *On
> Behalf Of *Kevin Gross
> *Sent:* 16 May 2013 18:09****
>
>
> *To:* Karen ODonoghue
> *Cc:* tictoc@ietf.org
> *Subject:* Re: [TICTOC] WGLC on draft-ietf-tictoc-ptp-mib-05.txt****
>
>  ****
>
> I submitted comments on v03 11 January (
> http://www.ietf.org/mail-archive/web/tictoc/current/msg01331.html). Vinay
> indicated in a short message on 23 January the comments would be addresse=
d
> in the next version (
> http://www.ietf.org/mail-archive/web/tictoc/current/msg01333.html). v04
> was published 31 January. I did not see any notes from the authors
> associated with that revision. A quick check of the v03-v04 diff shows
> evidence that not all my comments were directly addressed. Can I get a
> summary of how my comments were addressed? I'm fine if some of these were
> rejected but I would like to verify that they were given consideration.**=
*
> *
>
>
> ****
>
> Kevin Gross****
>
> +1-303-447-0517****
>
> Media Network Consultant****
>
> AVA Networks - www.AVAnw.com <http://www.avanw.com/>, www.X192.org****
>
>  ****
>
> On Thu, May 16, 2013 at 9:41 AM, Karen O'Donoghue <odonoghue@isoc.org>
> wrote:****
>
> This message initiates a two week TICTOC Working Group Last Call on
> advancing:
>
> Title : Precision Time Protocol Version 2 (PTPv2) Management Information
> Base
> Author(s) : Vinay Shankarkumar, Laurent Montini, Tim Frost, Greg Dowd
> Filename : draft-ietf-tictoc-ptp-mib-05.txt
> Pages : 77
> Date : 2013-02-25
>
> http://datatracker.ietf.org/doc/draft-ietf-tictoc-ptp-mib/?include_text=
=3D1
>
> as a Standards Track RFC. Substantive comments and statements of support
> for advancing this document should be directed to the mailing list.
> Editorial suggestions can be sent directly to the authors. This last call
> will end on 31 May 2013.
>
> _______________________________________________
> TICTOC mailing list
> TICTOC@ietf.org
> https://www.ietf.org/mailman/listinfo/tictoc****
>
>  ****
>
> ** **
>

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

<div dir=3D"ltr">My original proposal was incorrect. I think we&#39;re on t=
he right track now.</div><div class=3D"gmail_extra"><br clear=3D"all"><div>=
Kevin Gross<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.AV=
Anw.com</a>,=A0<a href=3D"http://www.X192.org" target=3D"_blank">www.X192.o=
rg</a></div></div></div>
<br><br><div class=3D"gmail_quote">On Mon, Jun 10, 2013 at 12:00 PM, Greg D=
owd <span dir=3D"ltr">&lt;<a href=3D"mailto:gdowd@symmetricom.com" target=
=3D"_blank">gdowd@symmetricom.com</a>&gt;</span> wrote:<br><blockquote clas=
s=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;pad=
ding-left:1ex">






<div lang=3D"EN-US" 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">I think the confusion was=
 that your comment suggested using an OUI, not a profile OID (EUI-48).=A0 T=
he OUI would not have been sufficient to distinguish multiple
 profiles from an organization as Tim noted.=A0 I=92ll review your comments=
 with the team.=A0 Thanks!<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-family:&quot;Calibri&quot;,&quot=
;sans-serif&quot;;color:gray">Greg Dowd=A0|=A0</span><b><span style=3D"font=
-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#00b0f0">Symmetric=
om=AE, Inc.</span></b><span style=3D"font-size:9.0pt;font-family:&quot;Aria=
l&quot;,&quot;sans-serif&quot;"><u></u><u></u></span></p>

<p class=3D"MsoNormal"><i><span style=3D"font-size:11.0pt;font-family:&quot=
;Calibri&quot;,&quot;sans-serif&quot;;color:gray">Staff Scientist=A0</span>=
</i><span style=3D"font-size:9.0pt;font-family:&quot;Arial&quot;,&quot;sans=
-serif&quot;"><br>

</span><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&quo=
t;sans-serif&quot;;color:gray">2300 Orchard Parkway, San Jose, CA 95131<br>
Direct:=A0 <a href=3D"tel:408.964.7643" value=3D"+14089647643" target=3D"_b=
lank">408.964.7643</a>=A0</span><span style=3D"font-size:9.0pt;font-family:=
&quot;Arial&quot;,&quot;sans-serif&quot;"><br>
</span><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&quo=
t;sans-serif&quot;;color:gray"><a href=3D"mailto:gdowd@symmetricom.com" tar=
get=3D"_blank"><span style=3D"color:gray">gdowd@symmetricom.com</span></a>=
=A0=A0|=A0=A0<a href=3D"http://www.symmetricom.com/" target=3D"_blank"><spa=
n style=3D"color:gray">www.symmetricom.com</span></a><u></u><u></u></span><=
/p>

<p class=3D"MsoNormal"><i><span style=3D"font-size:11.0pt;font-family:&quot=
;Calibri&quot;,&quot;sans-serif&quot;;color:#00b0f0">Symmetricom.=A0 Leadin=
g the world in precise time solutions.</span></i><span style=3D"font-size:9=
.0pt;font-family:&quot;Arial&quot;,&quot;sans-serif&quot;"><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>
<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;"> <a href=
=3D"mailto:tictoc-bounces@ietf.org" target=3D"_blank">tictoc-bounces@ietf.o=
rg</a> [mailto:<a href=3D"mailto:tictoc-bounces@ietf.org" target=3D"_blank"=
>tictoc-bounces@ietf.org</a>]
<b>On Behalf Of </b>Kevin Gross<br>
<b>Sent:</b> Monday, June 10, 2013 10:10 AM<br>
<b>To:</b> Tim Frost<br>
<b>Cc:</b> <a href=3D"mailto:tictoc@ietf.org" target=3D"_blank">tictoc@ietf=
.org</a>; Karen ODonoghue</span></p><div><div class=3D"h5"><br>
<b>Subject:</b> Re: [TICTOC] WGLC on draft-ietf-tictoc-ptp-mib-05.txt<u></u=
><u></u></div></div><p></p>
</div><div><div class=3D"h5">
<p class=3D"MsoNormal"><u></u>=A0<u></u></p>
<div>
<p class=3D"MsoNormal">Thanks for addressing my comments. It looks like the=
re are two outstanding.<u></u><u></u></p>
<div>
<ol start=3D"1" type=3D"1">
<li class=3D"MsoNormal">
ClockInstanceType and<u></u><u></u> </li><li class=3D"MsoNormal">
ClockProfileType<u></u><u></u> </li></ol>
</div>
<div>
<p class=3D"MsoNormal">It sounds like you intend to address (1) in a future=
 revision.<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><u></u>=A0<u></u></p>
</div>
<div>
<p class=3D"MsoNormal">With regards to (2), I think you misunderstand how t=
he profileIdentifier works. Please have a look at Section 19.3.3 of IEEE 15=
88-2008. This is an EUI-48, not merely an OUI. Organizations can change the=
 bottom 24 bits to indicate new profiles
 or revisions of existing ones. Maintaining our own enumeration of profiles=
 does not seem like a feasible undertaking.<u></u><u></u></p>
</div>
</div>
<div>
<p class=3D"MsoNormal"><br clear=3D"all">
<u></u><u></u></p>
<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>,=A0<a href=3D"http://www.X192.org" targe=
t=3D"_blank">www.X192.org</a><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 Fri, May 17, 2013 at 2:33 AM, Tim Frost &lt;<a hr=
ef=3D"mailto:tfrost@symmetricom.com" target=3D"_blank">tfrost@symmetricom.c=
om</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">Hi Kevin,</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">Thank you for taking the =
time to go through this MIB. We did consider your comments, and they were
 addressed in -05 (the latest version, and the subject of the last call).=
=A0 I=92ve gone through each of your comments below; it looks like we misse=
d one, and decided against another, but the remainder have been done.</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">The change history from t=
he -05 draft reads:
</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">-05=A0=A0=A0=A0=A0=A0 Feb 13 Several changes in resp=
onse to comments from Alun Luchuk<br>
=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 and Kevin Gross:<br>
=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 - Modified the use of wellKnownTranspo=
rtTypes and<br>
=A0=A0=A0=A0=A0=A0=A0 =A0=A0=A0=A0=A0=A0=A0wellKnownEncapsulationTypes<br>
=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 - changed ptpbaseClockPortSyncOneStep =
to<br>
=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 ptpbaseClockPortSyncTwoStep to m=
atch IEEE1588<br>
=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 semantics<br>
=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 - Re-ordered textual conventions to be=
 alphabetic<br>
=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 - Changed some types from Integer32 to=
 use defined<br>
=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 textual conventions<br>
=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 - various minor descriptive text chang=
es<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" style=3D"margin-bottom:12.0pt"><span style=3D"font-s=
ize:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1f=
497d">In detail:</span><u></u><u></u></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;">Abstract: Add a bracketed reference to IEEE 1588-2008 - DO=
NE</span><u></u><u></u></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;">=A0</span><u></u><u></u></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;">Section 1: s/defined to monitor, measure the performance/d=
efined to monitor and measure the performance - DONE</span><u></u><u></u></=
p>

<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;">=A0</span><u></u><u></u></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;">Section 1.1 What in this MIB is profile dependent? I did n=
ot identify anything in my review. It would be=A0desirable. if possible,=A0=
=A0to
 have a profile-independent MIB.</span><u></u><u></u></p>
<p><span style=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;">-</=
span><span style=3D"font-size:7.0pt">=A0=A0=A0
</span><span style=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;"=
>TF: Removed erroneous text about Telecom Profile =96 there is nothing in t=
his MIB that is particular to that profile.
</span><u></u><u></u></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;">=A0</span><u></u><u></u></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;">TEXTUAL-CONVENTION general issues - Consider alphabetizing=
 - DONE</span><u></u><u></u></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;">=A0</span><u></u><u></u></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;;color:#c00000">ClockInstanceType TEXTUAL-CONVENTION definit=
ion - Description requires elucidation or a reference.
</span><u></u><u></u></p>
<p><span style=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;;colo=
r:#c00000">-</span><span style=3D"font-size:7.0pt;color:#c00000">=A0=A0=A0
</span><span style=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;;=
color:#c00000">TF: not done, looks like this one slipped through.</span><u>=
</u><u></u></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;">=A0</span><u></u><u></u></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;">ClockProfileType=A0TEXTUAL-CONVENTION definition</span><u>=
</u><u></u></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;">Consider using and OUI instead of an enumeration. IEEE 158=
8-1588 requires an OUI be associated with each profile.</span><u></u><u></u=
></p>

<p><span style=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;">-</=
span><span style=3D"font-size:7.0pt">=A0=A0=A0
</span><span style=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;"=
>TF: OUI would be specific to the organization, not the profile. If the ITU=
 (for instance) developed more than one profile, then they would have the s=
ame OUI. Therefore it is best (in the authors=92
 opinion) to stick to using an enumeration</span><u></u><u></u></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;">=A0</span><u></u><u></u></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;">OBJECT-TYPE general issues</span><u></u><u></u></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;">Consider being consistent about repeating=A0TEXTUAL-CONVEN=
TION descriptions, explicitly referencing them or assuming readers
 will track down the reference without reminder.</span><u></u><u></u></p>
<p><span style=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;">-</=
span><span style=3D"font-size:7.0pt">=A0=A0=A0
</span><span style=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;"=
>TF: We=92ve tried to be as consistent as we can. Of 17 TEXTUAL-CONVENTIONS=
, 13 are directly referenced to IEEE1588 sections. The remainder don=92t di=
rectly map onto IEEE1588 quantities, but onto
 associated concepts, and we have tried to explain these in the description=
. Certainly one could do with a better description, as you note above.
</span><u></u><u></u></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;">=A0</span><u></u><u></u></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;">ptpDomainClockPortsTotal=A0OBJECT-TYPE</span><u></u><u></u=
></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;">I assume this is the number of ports for the managed PTP-c=
apable system (i.e. a router or switch). Suggest adding &quot;in the
 system&quot; to the description to clarify scope of count. - DONE</span><u=
></u><u></u></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;">=A0</span><u></u><u></u></p>
<pre>ptpbaseClockTimePropertiesDSTable OBJECT-TYPE <u></u><u></u></pre>
<pre>s/clock Timeproperties Datasets for/clock time properties datasets for=
 - DONE<u></u><u></u></pre>
<pre>=A0<u></u><u></u></pre>
<pre>PtpbaseClockTransDefaultDSEntry SEQUENCE<u></u><u></u></pre>
<pre>Use ClockDomainType textual convention instead of Integer32 for ptpbas=
eClockTransDefaultDSPrimaryDomain - DONE<u></u><u></u></pre>
<pre>=A0<u></u><u></u></pre>
<pre>PtpbaseClockPortEntry SEQUENCE<u></u><u></u></pre>
<pre>Change ptpbaseClockPortSyncOneStep to ptpbaseClockPortSyncTwoStep to m=
atch 1588 semantics for this Boolean =96 DONE<u></u><u></u></pre>
<pre>=A0<u></u><u></u></pre>
<pre>ptpbaseClockPortRunningEncapsulationType OBJECT-TYPE<u></u><u></u></pr=
e>
<pre>Needs a textual convention or description of allowed values and their =
meanings<u></u><u></u></pre>
<pre style=3D"margin-left:.5in">-<span style=3D"font-size:7.0pt;font-family=
:&quot;Times New Roman&quot;,&quot;serif&quot;">=A0=A0=A0 </span>TF: Now us=
es an autonomous type instead of Integer32<u></u><u></u></pre>
<pre>=A0<u></u><u></u></pre>
<pre>ptpbaseClockPortTransDSlogMinPdelayReqInt OBJECT-TYPE<u></u><u></u></p=
re>
<pre>Change to ClockIntervalBase2 type DONE<u></u><u></u></pre>
<pre>=A0<u></u><u></u></pre>
<pre>Section 5: Copy-paste error: &quot;creation and/or manipulation of tun=
nels&quot;<u></u><u></u></pre>
<pre style=3D"margin-left:.5in">-<span style=3D"font-size:7.0pt;font-family=
:&quot;Times New Roman&quot;,&quot;serif&quot;">=A0=A0=A0 </span>TF: Sectio=
n changed since -03, no longer has this phrase.<u></u><u></u></pre>
<pre>=A0<u></u><u></u></pre>
<pre>Section 6: To be added - DONE<u></u><u></u></pre>
<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">Best 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">Tim Frost</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>
<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;">
<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>Kevin Gross<br>
<b>Sent:</b> 16 May 2013 18:09</span><u></u><u></u></p>
<div>
<p class=3D"MsoNormal"><br>
<b>To:</b> Karen ODonoghue<br>
<b>Cc:</b> <a href=3D"mailto:tictoc@ietf.org" target=3D"_blank">tictoc@ietf=
.org</a><br>
<b>Subject:</b> Re: [TICTOC] WGLC on draft-ietf-tictoc-ptp-mib-05.txt<u></u=
><u></u></p>
</div>
</div>
<p class=3D"MsoNormal">=A0<u></u><u></u></p>
<div>
<p class=3D"MsoNormal">I submitted comments on v03 11 January (<a href=3D"h=
ttp://www.ietf.org/mail-archive/web/tictoc/current/msg01331.html" target=3D=
"_blank">http://www.ietf.org/mail-archive/web/tictoc/current/msg01331.html<=
/a>).
 Vinay indicated in a short message on 23 January the comments would be add=
ressed in the next version (<a href=3D"http://www.ietf.org/mail-archive/web=
/tictoc/current/msg01333.html" target=3D"_blank">http://www.ietf.org/mail-a=
rchive/web/tictoc/current/msg01333.html</a>).
 v04 was published 31 January. I did not see any notes from the authors ass=
ociated with that revision. A quick check of the v03-v04 diff shows evidenc=
e that not all my comments were directly addressed. Can I get a summary of =
how my comments were addressed?
 I&#39;m fine if some of these were rejected but I would like to verify tha=
t they were given consideration.<u></u><u></u></p>
</div>
<div>
<div>
<div>
<p class=3D"MsoNormal"><br clear=3D"all">
<u></u><u></u></p>
<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" 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>,=A0<a href=3D"http://www.X192.org" targe=
t=3D"_blank">www.X192.org</a><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 Thu, May 16, 2013 at 9:41 AM, Karen O&#39;Donoghu=
e &lt;<a href=3D"mailto:odonoghue@isoc.org" target=3D"_blank">odonoghue@iso=
c.org</a>&gt; wrote:<u></u><u></u></p>
<p class=3D"MsoNormal">This message initiates a two week TICTOC Working Gro=
up Last Call on advancing:<br>
<br>
Title : Precision Time Protocol Version 2 (PTPv2) Management Information Ba=
se<br>
Author(s) : Vinay Shankarkumar, Laurent Montini, Tim Frost, Greg Dowd<br>
Filename : draft-ietf-tictoc-ptp-mib-05.txt<br>
Pages : 77<br>
Date : 2013-02-25<br>
<br>
<a href=3D"http://datatracker.ietf.org/doc/draft-ietf-tictoc-ptp-mib/?inclu=
de_text=3D1" target=3D"_blank">http://datatracker.ietf.org/doc/draft-ietf-t=
ictoc-ptp-mib/?include_text=3D1</a><br>
<br>
as a Standards Track RFC. Substantive comments and statements of support fo=
r advancing this document should be directed to the mailing list. Editorial=
 suggestions can be sent directly to the authors. This last call will end o=
n 31 May 2013.<br>

<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><u></u><u></u></p>
</div>
<p class=3D"MsoNormal">=A0<u></u><u></u></p>
</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>

--089e0122ac4c96f8bd04ded0e165--

From internet-drafts@ietf.org  Fri Jun 14 22:55:39 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 56E4021F9B91; Fri, 14 Jun 2013 22:55:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.495
X-Spam-Level: 
X-Spam-Status: No, score=-102.495 tagged_above=-999 required=5 tests=[AWL=0.105, 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 A3L76RcDCkQF; Fri, 14 Jun 2013 22:55:38 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 7117B21F9B08; Fri, 14 Jun 2013 22:55:38 -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.51.p2
Message-ID: <20130615055538.26376.42640.idtracker@ietfa.amsl.com>
Date: Fri, 14 Jun 2013 22:55:38 -0700
Cc: tictoc@ietf.org
Subject: [TICTOC] I-D Action: draft-ietf-tictoc-1588overmpls-05.txt
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: Sat, 15 Jun 2013 05:55:39 -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           : Transporting Timing messages over MPLS Networks
	Author(s)       : Shahram Davari
                          Amit Oren
                          Manav Bhatia
                          Peter Roberts
                          Laurent Montini
	Filename        : draft-ietf-tictoc-1588overmpls-05.txt
	Pages           : 35
	Date            : 2013-06-14

Abstract:
   This document defines the method for transporting Timing messages
   such as PTP and NTP over an MPLS network.  The method allows for the
   easy identification of these PDUs at the port level to allow for port
   level processing of these PDUs in both LERs and LSRs.

   The basic idea is to transport Timing messages inside dedicated MPLS
   LSPs.  These LSPs only carry Timing messages and possibly Control and
   Management packets, but they do not carry customer traffic.

   Two methods for transporting Timing messages over MPLS are defined.
   The first method is to transport Timing messages directly over the
   dedicated MPLS LSP via UDP/IP encapsulation, which is suitable for
   MPLS networks.  The second method is to transport Timing messages
   inside a PW via Ethernet encapsulation.


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

There's also a htmlized version available at:
http://tools.ietf.org/html/draft-ietf-tictoc-1588overmpls-05

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


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


From manav.bhatia@alcatel-lucent.com  Fri Jun 14 22:59:55 2013
Return-Path: <manav.bhatia@alcatel-lucent.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 7DB4721F861F for <tictoc@ietfa.amsl.com>; Fri, 14 Jun 2013 22:59:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.599
X-Spam-Level: 
X-Spam-Status: No, score=-10.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, 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 UJ+fy2begh+l for <tictoc@ietfa.amsl.com>; Fri, 14 Jun 2013 22:59:49 -0700 (PDT)
Received: from ihemail3.lucent.com (ihemail3.lucent.com [135.245.0.37]) by ietfa.amsl.com (Postfix) with ESMTP id C79D421F8616 for <tictoc@ietf.org>; Fri, 14 Jun 2013 22:59:49 -0700 (PDT)
Received: from us70tusmtp2.zam.alcatel-lucent.com (h135-5-2-64.lucent.com [135.5.2.64]) by ihemail3.lucent.com (8.13.8/IER-o) with ESMTP id r5F5xmCv010134 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Sat, 15 Jun 2013 00:59:48 -0500 (CDT)
Received: from US70UWXCHHUB02.zam.alcatel-lucent.com (us70uwxchhub02.zam.alcatel-lucent.com [135.5.2.49]) by us70tusmtp2.zam.alcatel-lucent.com (GMO) with ESMTP id r5F5xlbf021873 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Sat, 15 Jun 2013 01:59:47 -0400
Received: from SG70XWXCHHUB01.zap.alcatel-lucent.com (135.253.2.46) by US70UWXCHHUB02.zam.alcatel-lucent.com (135.5.2.49) with Microsoft SMTP Server (TLS) id 14.2.247.3; Sat, 15 Jun 2013 01:59:47 -0400
Received: from SG70YWXCHMBA05.zap.alcatel-lucent.com ([169.254.5.102]) by SG70XWXCHHUB01.zap.alcatel-lucent.com ([135.253.2.46]) with mapi id 14.02.0247.003; Sat, 15 Jun 2013 13:59:44 +0800
From: "Bhatia, Manav (Manav)" <manav.bhatia@alcatel-lucent.com>
To: "yaakov_s@rad.com" <yaakov_s@rad.com>, "odonoghue@isoc.org" <odonoghue@isoc.org>
Thread-Topic: [TICTOC] I-D Action: draft-ietf-tictoc-1588overmpls-05.txt
Thread-Index: AQHOaY0V57lbPxj+N0Katp+Ad4FGvZk2R4aQ
Date: Sat, 15 Jun 2013 05:59:43 +0000
Message-ID: <20211F91F544D247976D84C5D778A4C305826C@SG70YWXCHMBA05.zap.alcatel-lucent.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [135.253.19.16]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Scanned-By: MIMEDefang 2.57 on 135.245.2.37
Cc: "tictoc@ietf.org" <tictoc@ietf.org>
Subject: [TICTOC] FW:  I-D Action: draft-ietf-tictoc-1588overmpls-05.txt
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: Sat, 15 Jun 2013 05:59:55 -0000

Hi,

This version incorporates all the feedback that we received from the WG.

I guess its ready for the WG LC now.

Cheers, Manav

-----Original Message-----
From: tictoc-bounces@ietf.org [mailto:tictoc-bounces@ietf.org] On Behalf Of=
 internet-drafts@ietf.org
Sent: Saturday, June 15, 2013 11:26 AM
To: i-d-announce@ietf.org
Cc: tictoc@ietf.org
Subject: [TICTOC] I-D Action: draft-ietf-tictoc-1588overmpls-05.txt


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           : Transporting Timing messages over MPLS Networks
	Author(s)       : Shahram Davari
                          Amit Oren
                          Manav Bhatia
                          Peter Roberts
                          Laurent Montini
	Filename        : draft-ietf-tictoc-1588overmpls-05.txt
	Pages           : 35
	Date            : 2013-06-14

Abstract:
   This document defines the method for transporting Timing messages
   such as PTP and NTP over an MPLS network.  The method allows for the
   easy identification of these PDUs at the port level to allow for port
   level processing of these PDUs in both LERs and LSRs.

   The basic idea is to transport Timing messages inside dedicated MPLS
   LSPs.  These LSPs only carry Timing messages and possibly Control and
   Management packets, but they do not carry customer traffic.

   Two methods for transporting Timing messages over MPLS are defined.
   The first method is to transport Timing messages directly over the
   dedicated MPLS LSP via UDP/IP encapsulation, which is suitable for
   MPLS networks.  The second method is to transport Timing messages
   inside a PW via Ethernet encapsulation.


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

There's also a htmlized version available at:
http://tools.ietf.org/html/draft-ietf-tictoc-1588overmpls-05

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


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

_______________________________________________
TICTOC mailing list
TICTOC@ietf.org
https://www.ietf.org/mailman/listinfo/tictoc

From brian@innovationslab.net  Sat Jun 15 09:34:34 2013
Return-Path: <brian@innovationslab.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 0D33721F9DB3 for <tictoc@ietfa.amsl.com>; Sat, 15 Jun 2013 09:34:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, 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 IaMzCnMZorbi for <tictoc@ietfa.amsl.com>; Sat, 15 Jun 2013 09:34:29 -0700 (PDT)
Received: from uillean.fuaim.com (uillean.fuaim.com [206.197.161.140]) by ietfa.amsl.com (Postfix) with ESMTP id F2B3E21F9DB9 for <tictoc@ietf.org>; Sat, 15 Jun 2013 09:34:28 -0700 (PDT)
Received: from clairseach.fuaim.com (clairseach-high.fuaim.com [206.197.161.158]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by uillean.fuaim.com (Postfix) with ESMTP id 756EB88133 for <tictoc@ietf.org>; Sat, 15 Jun 2013 09:34:28 -0700 (PDT)
Received: from Littlejohn.local (c-69-140-213-249.hsd1.md.comcast.net [69.140.213.249]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by clairseach.fuaim.com (Postfix) with ESMTP id 1409213680CA for <tictoc@ietf.org>; Sat, 15 Jun 2013 09:34:27 -0700 (PDT)
Message-ID: <51BC9792.2000504@innovationslab.net>
Date: Sat, 15 Jun 2013 12:34:26 -0400
From: Brian Haberman <brian@innovationslab.net>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:17.0) Gecko/20130509 Thunderbird/17.0.6
MIME-Version: 1.0
To: tictoc@ietf.org
References: <7347100B5761DC41A166AC17F22DF1121B4A0754@eusaamb103.ericsson.se> <07F7D7DED63154409F13298786A2ADC904D6D57C@EXRAD5.ad.rad.co.il>, <7347100B5761DC41A166AC17F22DF1121B4A0CB9@eusaamb103.ericsson.se> <DDB3D38B-6FE8-4A4A-A604-56AB9181C5FE@broadcom.com>
In-Reply-To: <DDB3D38B-6FE8-4A4A-A604-56AB9181C5FE@broadcom.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [TICTOC] NTP in draft-ietf-tictoc-1588overmpls-04
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: Sat, 15 Jun 2013 16:34:34 -0000

Hi Shahram,

On 6/7/13 12:00 PM, Shahram Davari wrote:
> Greg,
>
> This draft was originally only for PTP, however our Area Director asked the draft to be made more generic so that it can apply to any timing protocol.
>

That is not exactly what *I* said.  I was asked the question of whether 
it was reasonable to go in this direction and my response was "it is 
worth looking into".  It is up to the WG to decide if it is worth doing.

Regards,
Brian

> Regards,
> Shahram
>
>
> On Jun 7, 2013, at 8:28 AM, "Gregory Mirsky" <gregory.mirsky@ericsson.com<mailto:gregory.mirsky@ericsson.com>> wrote:
>
> Yaakov,
> I'm rather sceptical of using "If you build it, he will come" as protocol development guiding principle. Personally I prefer KISS.
>
>      Regards,
>          Greg
>
> ________________________________
> From: Yaakov Stein [mailto:yaakov_s@rad.com]
> Sent: Friday, June 07, 2013 7:55 AM
> To: Gregory Mirsky; Shahram Davari; amito@broadcom.com<mailto:amito@broadcom.com>; Bhatia, Manav (Manav); Roberts, Peter (Peter); lmontini@cisco.com<mailto:lmontini@cisco.com>; tictoc@ietf.org<mailto:tictoc@ietf.org>
> Subject: RE: NTP in draft-ietf-tictoc-1588overmpls-04
>
> Greg
>
> This version makes the mechanism more general so that in future other time-sensitive protocols
> (NTP, delay measurement OAM, generic header for MPLS) could avail themselves of its timestamping/correction features.
>
> It is true that the only real case so far is 1588.
>
> Y(J)S
>
> From: tictoc-bounces@ietf.org<mailto:tictoc-bounces@ietf.org> [mailto:tictoc-bounces@ietf.org] On Behalf Of Gregory Mirsky
> Sent: 06 June, 2013 21:23
> To: Shahram Davari; amito@broadcom.com<mailto:amito@broadcom.com>; Bhatia, Manav (Manav); Roberts, Peter (Peter); lmontini@cisco.com<mailto:lmontini@cisco.com>; tictoc@ietf.org<mailto:tictoc@ietf.org>
> Subject: [TICTOC] NTP in draft-ietf-tictoc-1588overmpls-04
>
> Dear Authors, et al.,
> The draft-ietf-tictoc-1588overmpls-04 is currently titled as "Transporting Timing messages over MPLS Networks" and states that both timing synchronization protocols, PTP and NTP, require use of PTP LSP to transport timing messages over an MPLS network. After reading RFC 5905 I am not sure that PTP LSP, with its constraints and additional complexity, is required to transport NTPv4 messages over an MPLS network. And first paragraph in Section 3 Problem Statement of draft-ietf-tictoc-1588overmpls-04 explains motivation for the PTP as
> "There is a need to transport Timing messages over MPLS networks while supporting the Transparent Clock (TC), Boundary Clock (BC) and Ordinary Clock (OC) functionality in the LER and LSRs in the MPLS network."
> but says nothing of a kind about NTP.
>
>          Regards,
>                  Greg
>
>
>
>
> _______________________________________________
> TICTOC mailing list
> TICTOC@ietf.org
> https://www.ietf.org/mailman/listinfo/tictoc
>


From manav.bhatia@alcatel-lucent.com  Sat Jun 15 16:44:50 2013
Return-Path: <manav.bhatia@alcatel-lucent.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 CF4C221F9433 for <tictoc@ietfa.amsl.com>; Sat, 15 Jun 2013 16:44:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.599
X-Spam-Level: 
X-Spam-Status: No, score=-10.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, 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 FYtZWIH3ab-w for <tictoc@ietfa.amsl.com>; Sat, 15 Jun 2013 16:44:45 -0700 (PDT)
Received: from ihemail4.lucent.com (ihemail4.lucent.com [135.245.0.39]) by ietfa.amsl.com (Postfix) with ESMTP id 1F09F21F9425 for <tictoc@ietf.org>; Sat, 15 Jun 2013 16:44:45 -0700 (PDT)
Received: from us70uusmtp3.zam.alcatel-lucent.com (h135-5-2-65.lucent.com [135.5.2.65]) by ihemail4.lucent.com (8.13.8/IER-o) with ESMTP id r5FNihN8013939 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Sat, 15 Jun 2013 18:44:43 -0500 (CDT)
Received: from US70TWXCHHUB03.zam.alcatel-lucent.com (us70twxchhub03.zam.alcatel-lucent.com [135.5.2.35]) by us70uusmtp3.zam.alcatel-lucent.com (GMO) with ESMTP id r5FNifTp026518 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Sat, 15 Jun 2013 19:44:41 -0400
Received: from SG70XWXCHHUB01.zap.alcatel-lucent.com (135.253.2.46) by US70TWXCHHUB03.zam.alcatel-lucent.com (135.5.2.35) with Microsoft SMTP Server (TLS) id 14.2.247.3; Sat, 15 Jun 2013 19:44:41 -0400
Received: from SG70YWXCHMBA05.zap.alcatel-lucent.com ([169.254.5.102]) by SG70XWXCHHUB01.zap.alcatel-lucent.com ([135.253.2.46]) with mapi id 14.02.0247.003; Sun, 16 Jun 2013 07:44:38 +0800
From: "Bhatia, Manav (Manav)" <manav.bhatia@alcatel-lucent.com>
To: Brian Haberman <brian@innovationslab.net>, "tictoc@ietf.org" <tictoc@ietf.org>
Thread-Topic: [TICTOC] NTP in draft-ietf-tictoc-1588overmpls-04
Thread-Index: Ac5i4ubOrT57JHkXTgC9GUzpraB4EAAq9gQAAAElPiAAATQbzwGCwCkAAB9uCSA=
Date: Sat, 15 Jun 2013 23:44:37 +0000
Message-ID: <20211F91F544D247976D84C5D778A4C30586E4@SG70YWXCHMBA05.zap.alcatel-lucent.com>
References: <7347100B5761DC41A166AC17F22DF1121B4A0754@eusaamb103.ericsson.se> <07F7D7DED63154409F13298786A2ADC904D6D57C@EXRAD5.ad.rad.co.il>, <7347100B5761DC41A166AC17F22DF1121B4A0CB9@eusaamb103.ericsson.se> <DDB3D38B-6FE8-4A4A-A604-56AB9181C5FE@broadcom.com> <51BC9792.2000504@innovationslab.net>
In-Reply-To: <51BC9792.2000504@innovationslab.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [135.253.19.18]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Scanned-By: MIMEDefang 2.57 on 135.245.2.39
Subject: Re: [TICTOC] NTP in draft-ietf-tictoc-1588overmpls-04
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: Sat, 15 Jun 2013 23:44:50 -0000

Hi Brian,

Originally this draft covered just 1588. I believe Stewart Bryant suggested=
 that we change the draft and make it generic to apply to any timing protoc=
ol. Its then that we removed the 1588 specific routing and signaling change=
s from this draft and put them in a separate draft that describes those ext=
ensions (still work in progress btw).

Cheers, Manav

> -----Original Message-----
> From: tictoc-bounces@ietf.org=20
> [mailto:tictoc-bounces@ietf.org] On Behalf Of Brian Haberman
> Sent: Saturday, June 15, 2013 10:04 PM
> To: tictoc@ietf.org
> Subject: Re: [TICTOC] NTP in draft-ietf-tictoc-1588overmpls-04
>=20
> Hi Shahram,
>=20
> On 6/7/13 12:00 PM, Shahram Davari wrote:
> > Greg,
> >
> > This draft was originally only for PTP, however our Area=20
> Director asked the draft to be made more generic so that it=20
> can apply to any timing protocol.
> >
>=20
> That is not exactly what *I* said.  I was asked the question=20
> of whether it was reasonable to go in this direction and my=20
> response was "it is worth looking into".  It is up to the WG=20
> to decide if it is worth doing.
>=20
> Regards,
> Brian
>=20
> > Regards,
> > Shahram
> >
> >
> > On Jun 7, 2013, at 8:28 AM, "Gregory Mirsky"=20
> <gregory.mirsky@ericsson.com<mailto:gregory.mirsky@ericsson.co
> m>> wrote:
> >
> > Yaakov,
> > I'm rather sceptical of using "If you build it, he will=20
> come" as protocol development guiding principle. Personally I=20
> prefer KISS.
> >
> >      Regards,
> >          Greg
> >
> > ________________________________
> > From: Yaakov Stein [mailto:yaakov_s@rad.com]
> > Sent: Friday, June 07, 2013 7:55 AM
> > To: Gregory Mirsky; Shahram Davari;=20
> > amito@broadcom.com<mailto:amito@broadcom.com>; Bhatia,=20
> Manav (Manav);=20
> > Roberts, Peter (Peter);=20
> lmontini@cisco.com<mailto:lmontini@cisco.com>;=20
> > tictoc@ietf.org<mailto:tictoc@ietf.org>
> > Subject: RE: NTP in draft-ietf-tictoc-1588overmpls-04
> >
> > Greg
> >
> > This version makes the mechanism more general so that in=20
> future other=20
> > time-sensitive protocols (NTP, delay measurement OAM,=20
> generic header for MPLS) could avail themselves of its=20
> timestamping/correction features.
> >
> > It is true that the only real case so far is 1588.
> >
> > Y(J)S
> >
> > From: tictoc-bounces@ietf.org<mailto:tictoc-bounces@ietf.org>=20
> > [mailto:tictoc-bounces@ietf.org] On Behalf Of Gregory Mirsky
> > Sent: 06 June, 2013 21:23
> > To: Shahram Davari; amito@broadcom.com<mailto:amito@broadcom.com>;=20
> > Bhatia, Manav (Manav); Roberts, Peter (Peter);=20
> > lmontini@cisco.com<mailto:lmontini@cisco.com>;=20
> > tictoc@ietf.org<mailto:tictoc@ietf.org>
> > Subject: [TICTOC] NTP in draft-ietf-tictoc-1588overmpls-04
> >
> > Dear Authors, et al.,
> > The draft-ietf-tictoc-1588overmpls-04 is currently titled as=20
> > "Transporting Timing messages over MPLS Networks" and=20
> states that both timing synchronization protocols, PTP and=20
> NTP, require use of PTP LSP to transport timing messages over=20
> an MPLS network. After reading RFC 5905 I am not sure that=20
> PTP LSP, with its constraints and additional complexity, is=20
> required to transport NTPv4 messages over an MPLS network.=20
> And first paragraph in Section 3 Problem Statement of=20
> draft-ietf-tictoc-1588overmpls-04 explains motivation for the=20
> PTP as "There is a need to transport Timing messages over=20
> MPLS networks while supporting the Transparent Clock (TC),=20
> Boundary Clock (BC) and Ordinary Clock (OC) functionality in=20
> the LER and LSRs in the MPLS network."
> > but says nothing of a kind about NTP.
> >
> >          Regards,
> >                  Greg
> >
> >
> >
> >
> > _______________________________________________
> > TICTOC mailing list
> > TICTOC@ietf.org
> > https://www.ietf.org/mailman/listinfo/tictoc
> >
>=20
> _______________________________________________
> TICTOC mailing list
> TICTOC@ietf.org
> https://www.ietf.org/mailman/listinfo/tictoc
> =

From yaakov_s@rad.com  Tue Jun 25 23:35:39 2013
Return-Path: <yaakov_s@rad.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 90B3B21E8116 for <tictoc@ietfa.amsl.com>; Tue, 25 Jun 2013 23:35:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.597
X-Spam-Level: 
X-Spam-Status: No, score=-102.597 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, UNPARSEABLE_RELAY=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 nfuFjpGztilu for <tictoc@ietfa.amsl.com>; Tue, 25 Jun 2013 23:35:26 -0700 (PDT)
Received: from rad.co.il (mailrelay02-q.rad.co.il [94.188.133.159]) by ietfa.amsl.com (Postfix) with ESMTP id 0A59C11E813F for <tictoc@ietf.org>; Tue, 25 Jun 2013 23:35:23 -0700 (PDT)
Received: from Internal Mail-Server by MailRelay02 (envelope-from yaakov?s@rad.com) with AES128-SHA encrypted SMTP; 26 Jun 2013 09:34:08 +0300
Received: from EXRAD5.ad.rad.co.il ([192.114.24.28]) by EXRAD5.ad.rad.co.il ([192.114.24.28]) with mapi id 14.03.0146.000; Wed, 26 Jun 2013 09:35:19 +0300
From: Yaakov Stein <yaakov_s@rad.com>
To: "draft-ietf-tictoc-1588overmpls@tools.ietf.org" <draft-ietf-tictoc-1588overmpls@tools.ietf.org>, "tictoc@ietf.org" <tictoc@ietf.org>
Thread-Topic: IPR poll for draft-ietf-tictoc-1588overmpls
Thread-Index: Ac5yN1LBtEAvMVvBTJuZH02+U0VP/g==
Date: Wed, 26 Jun 2013 06:35:18 +0000
Message-ID: <07F7D7DED63154409F13298786A2ADC904E50C22@EXRAD5.ad.rad.co.il>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [172.17.140.37]
Content-Type: multipart/alternative; boundary="_000_07F7D7DED63154409F13298786A2ADC904E50C22EXRAD5adradcoil_"
MIME-Version: 1.0
X-Commtouch-Refid: str=0001.0A090203.51CA8BA8.00C4,ss=1,fgs=0
Subject: [TICTOC] IPR poll for draft-ietf-tictoc-1588overmpls
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: Wed, 26 Jun 2013 06:35:39 -0000

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

TICTOC Working Group and authors of draft-ietf-tictoc-1588overmpls :

We are soon going to be performing a WG LC on this draft.

This email initiates an IPR poll to check whether there is any
IPR relating to this document that needs to be disclosed.

Are any of you aware of any applicable IPR ?

If so, has this IPR been disclosed in compliance with IETF IPR guidelines ?
(see RFCs 3979, 4879, 3669 and 5378 for more details.)

If you are listed as a document author or contributor please send an email =
to
the TICTOC list regardless of whether or not you are aware of any relevant =
IPR.
A simple "I know of no IPR" is sufficient if that is the case.

If you are not an author but know of applicable IPR,
please send an email to the TICTOC list.

Y(J)S


--_000_07F7D7DED63154409F13298786A2ADC904E50C22EXRAD5adradcoil_
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 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: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;}
pre
	{mso-style-priority:99;
	mso-style-link:"HTML Preformatted Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:10.0pt;
	font-family:"Courier New";}
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-compose;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
span.BalloonTextChar
	{mso-style-name:"Balloon Text Char";
	mso-style-priority:99;
	mso-style-link:"Balloon Text";
	font-family:"Tahoma","sans-serif";}
span.HTMLPreformattedChar
	{mso-style-name:"HTML Preformatted Char";
	mso-style-priority:99;
	mso-style-link:"HTML Preformatted";
	font-family:"Courier New";}
.MsoChpDefault
	{mso-style-type:export-only;}
@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:10.0pt;font-family:&quot;Co=
urier New&quot;">TICTOC Working Group and authors of
</span><span style=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;"=
>draft-ietf-tictoc-1588overmpls :<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;">We are soon going to be performing a WG LC on this draft.<=
o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;">This email initiates an IPR poll to check whether there is=
 any<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;">IPR relating to this document that needs to be disclosed.<=
o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;">Are any of you aware of any applicable IPR ?<o:p></o:p></s=
pan></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;">If so, has this IPR been disclosed in compliance with IETF=
 IPR guidelines ?<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;">(see RFCs 3979, 4879, 3669 and 5378 for more details.)<o:p=
></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;">If you are listed as a document author or contributor plea=
se send an email to
<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;">the TICTOC list regardless of whether or not you are aware=
 of any relevant IPR.
<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;">A simple &#8220;I know of no IPR&#8221; is sufficient if t=
hat is the case.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;">If you are not an author but know of applicable IPR,<o:p><=
/o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;">please send an email to the TICTOC list.<o:p></o:p></span>=
</p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;">Y(J)S<o:p></o:p></span></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
</body>
</html>

--_000_07F7D7DED63154409F13298786A2ADC904E50C22EXRAD5adradcoil_--

From manav.bhatia@alcatel-lucent.com  Tue Jun 25 23:39:01 2013
Return-Path: <manav.bhatia@alcatel-lucent.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 3B40521E8119 for <tictoc@ietfa.amsl.com>; Tue, 25 Jun 2013 23:39:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.598
X-Spam-Level: 
X-Spam-Status: No, score=-10.598 tagged_above=-999 required=5 tests=[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 ZNvj7szeDxBT for <tictoc@ietfa.amsl.com>; Tue, 25 Jun 2013 23:38:54 -0700 (PDT)
Received: from ihemail1.lucent.com (ihemail1.lucent.com [135.245.0.33]) by ietfa.amsl.com (Postfix) with ESMTP id 47DB511E810A for <tictoc@ietf.org>; Tue, 25 Jun 2013 23:38:53 -0700 (PDT)
Received: from us70uusmtp4.zam.alcatel-lucent.com (h135-5-2-66.lucent.com [135.5.2.66]) by ihemail1.lucent.com (8.13.8/IER-o) with ESMTP id r5Q6cp6F025983 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Wed, 26 Jun 2013 01:38:52 -0500 (CDT)
Received: from US70UWXCHHUB02.zam.alcatel-lucent.com (us70uwxchhub02.zam.alcatel-lucent.com [135.5.2.49]) by us70uusmtp4.zam.alcatel-lucent.com (GMO) with ESMTP id r5Q6chu6009440 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Wed, 26 Jun 2013 02:38:51 -0400
Received: from SG70YWXCHHUB04.zap.alcatel-lucent.com (135.253.2.38) by US70UWXCHHUB02.zam.alcatel-lucent.com (135.5.2.49) with Microsoft SMTP Server (TLS) id 14.2.247.3; Wed, 26 Jun 2013 02:38:49 -0400
Received: from SG70YWXCHMBA05.zap.alcatel-lucent.com ([169.254.5.102]) by SG70YWXCHHUB04.zap.alcatel-lucent.com ([135.253.2.38]) with mapi id 14.02.0247.003; Wed, 26 Jun 2013 14:38:46 +0800
From: "Bhatia, Manav (Manav)" <manav.bhatia@alcatel-lucent.com>
To: Yaakov Stein <yaakov_s@rad.com>, "draft-ietf-tictoc-1588overmpls@tools.ietf.org" <draft-ietf-tictoc-1588overmpls@tools.ietf.org>, "tictoc@ietf.org" <tictoc@ietf.org>
Thread-Topic: IPR poll for draft-ietf-tictoc-1588overmpls
Thread-Index: Ac5yN1LBtEAvMVvBTJuZH02+U0VP/gAAHQow
Date: Wed, 26 Jun 2013 06:38:44 +0000
Message-ID: <20211F91F544D247976D84C5D778A4C3065A43@SG70YWXCHMBA05.zap.alcatel-lucent.com>
References: <07F7D7DED63154409F13298786A2ADC904E50C22@EXRAD5.ad.rad.co.il>
In-Reply-To: <07F7D7DED63154409F13298786A2ADC904E50C22@EXRAD5.ad.rad.co.il>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [135.253.19.16]
Content-Type: multipart/alternative; boundary="_000_20211F91F544D247976D84C5D778A4C3065A43SG70YWXCHMBA05zap_"
MIME-Version: 1.0
X-Scanned-By: MIMEDefang 2.57 on 135.245.2.33
Subject: Re: [TICTOC] IPR poll for draft-ietf-tictoc-1588overmpls
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: Wed, 26 Jun 2013 06:39:01 -0000

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

None from my side.

Cheers, Manav

________________________________
From: tictoc-bounces@ietf.org [mailto:tictoc-bounces@ietf.org] On Behalf Of=
 Yaakov Stein
Sent: Wednesday, June 26, 2013 12:05 PM
To: draft-ietf-tictoc-1588overmpls@tools.ietf.org; tictoc@ietf.org
Subject: [TICTOC] IPR poll for draft-ietf-tictoc-1588overmpls

TICTOC Working Group and authors of draft-ietf-tictoc-1588overmpls :

We are soon going to be performing a WG LC on this draft.

This email initiates an IPR poll to check whether there is any
IPR relating to this document that needs to be disclosed.

Are any of you aware of any applicable IPR ?

If so, has this IPR been disclosed in compliance with IETF IPR guidelines ?
(see RFCs 3979, 4879, 3669 and 5378 for more details.)

If you are listed as a document author or contributor please send an email =
to
the TICTOC list regardless of whether or not you are aware of any relevant =
IPR.
A simple "I know of no IPR" is sufficient if that is the case.

If you are not an author but know of applicable IPR,
please send an email to the TICTOC list.

Y(J)S


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

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<html xmlns=3D"http://www.w3.org/TR/REC-html40" xmlns:v=3D"urn:schemas-micr=
osoft-com:vml" xmlns:o=3D"urn:schemas-microsoft-com:office:office" xmlns:w=
=3D"urn:schemas-microsoft-com:office:word" xmlns:m=3D"http://schemas.micros=
oft.com/office/2004/12/omml">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
<meta name=3D"GENERATOR" content=3D"MSHTML 8.00.6001.18702">
<style>@font-face {
	font-family: Cambria Math;
}
@font-face {
	font-family: Calibri;
}
@font-face {
	font-family: Tahoma;
}
@page WordSection1 {size: 8.5in 11.0in; margin: 1.0in 1.25in 1.0in 1.25in; =
}
P.MsoNormal {
	MARGIN: 0in 0in 0pt; FONT-FAMILY: "Calibri","sans-serif"; FONT-SIZE: 11pt
}
LI.MsoNormal {
	MARGIN: 0in 0in 0pt; FONT-FAMILY: "Calibri","sans-serif"; FONT-SIZE: 11pt
}
DIV.MsoNormal {
	MARGIN: 0in 0in 0pt; FONT-FAMILY: "Calibri","sans-serif"; FONT-SIZE: 11pt
}
A:link {
	COLOR: blue; TEXT-DECORATION: underline; mso-style-priority: 99
}
SPAN.MsoHyperlink {
	COLOR: blue; TEXT-DECORATION: underline; mso-style-priority: 99
}
A:visited {
	COLOR: purple; TEXT-DECORATION: underline; mso-style-priority: 99
}
SPAN.MsoHyperlinkFollowed {
	COLOR: purple; TEXT-DECORATION: underline; mso-style-priority: 99
}
PRE {
	MARGIN: 0in 0in 0pt; FONT-FAMILY: "Courier New"; FONT-SIZE: 10pt; mso-styl=
e-priority: 99; mso-style-link: "HTML Preformatted Char"
}
P.MsoAcetate {
	MARGIN: 0in 0in 0pt; FONT-FAMILY: "Tahoma","sans-serif"; FONT-SIZE: 8pt; m=
so-style-priority: 99; mso-style-link: "Balloon Text Char"
}
LI.MsoAcetate {
	MARGIN: 0in 0in 0pt; FONT-FAMILY: "Tahoma","sans-serif"; FONT-SIZE: 8pt; m=
so-style-priority: 99; mso-style-link: "Balloon Text Char"
}
DIV.MsoAcetate {
	MARGIN: 0in 0in 0pt; FONT-FAMILY: "Tahoma","sans-serif"; FONT-SIZE: 8pt; m=
so-style-priority: 99; mso-style-link: "Balloon Text Char"
}
SPAN.EmailStyle17 {
	FONT-FAMILY: "Calibri","sans-serif"; COLOR: windowtext; mso-style-type: pe=
rsonal-compose
}
SPAN.BalloonTextChar {
	FONT-FAMILY: "Tahoma","sans-serif"; mso-style-priority: 99; mso-style-link=
: "Balloon Text"; mso-style-name: "Balloon Text Char"
}
SPAN.HTMLPreformattedChar {
	FONT-FAMILY: "Courier New"; mso-style-priority: 99; mso-style-link: "HTML =
Preformatted"; mso-style-name: "HTML Preformatted Char"
}
.MsoChpDefault {
	mso-style-type: export-only
}
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 dir=3D"ltr" align=3D"left"><span class=3D"646323806-26062013"><font co=
lor=3D"#0000ff" size=3D"2" face=3D"Arial">None from&nbsp;my side.</font></s=
pan></div>
<div dir=3D"ltr" align=3D"left"><span class=3D"646323806-26062013"><font co=
lor=3D"#0000ff" size=3D"2" face=3D"Arial"></font></span>&nbsp;</div>
<div dir=3D"ltr" align=3D"left"><span class=3D"646323806-26062013"><font co=
lor=3D"#0000ff" size=3D"2" face=3D"Arial">Cheers, Manav</font></span></div>
<br>
<blockquote style=3D"BORDER-LEFT: #0000ff 2px solid; PADDING-LEFT: 5px; MAR=
GIN-LEFT: 5px; MARGIN-RIGHT: 0px" dir=3D"ltr">
<div dir=3D"ltr" lang=3D"en-us" class=3D"OutlookMessageHeader" align=3D"lef=
t">
<hr tabindex=3D"-1">
<font size=3D"2" face=3D"Tahoma"><b>From:</b> tictoc-bounces@ietf.org [mail=
to:tictoc-bounces@ietf.org]
<b>On Behalf Of </b>Yaakov Stein<br>
<b>Sent:</b> Wednesday, June 26, 2013 12:05 PM<br>
<b>To:</b> draft-ietf-tictoc-1588overmpls@tools.ietf.org; tictoc@ietf.org<b=
r>
<b>Subject:</b> [TICTOC] IPR poll for draft-ietf-tictoc-1588overmpls<br>
</font><br>
</div>
<div></div>
<div class=3D"WordSection1">
<p class=3D"MsoNormal"><span style=3D"FONT-FAMILY: 'Courier New'; FONT-SIZE=
: 10pt">TICTOC Working Group and authors of
</span><span style=3D"FONT-FAMILY: 'Courier New'; FONT-SIZE: 10pt">draft-ie=
tf-tictoc-1588overmpls :<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"FONT-FAMILY: 'Courier New'; FONT-SIZE=
: 10pt"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"FONT-FAMILY: 'Courier New'; FONT-SIZE=
: 10pt">We are soon going to be performing a WG LC on this draft.<o:p></o:p=
></span></p>
<p class=3D"MsoNormal"><span style=3D"FONT-FAMILY: 'Courier New'; FONT-SIZE=
: 10pt"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"FONT-FAMILY: 'Courier New'; FONT-SIZE=
: 10pt">This email initiates an IPR poll to check whether there is any<o:p>=
</o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"FONT-FAMILY: 'Courier New'; FONT-SIZE=
: 10pt">IPR relating to this document that needs to be disclosed.<o:p></o:p=
></span></p>
<p class=3D"MsoNormal"><span style=3D"FONT-FAMILY: 'Courier New'; FONT-SIZE=
: 10pt"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"FONT-FAMILY: 'Courier New'; FONT-SIZE=
: 10pt">Are any of you aware of any applicable IPR ?<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"FONT-FAMILY: 'Courier New'; FONT-SIZE=
: 10pt"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"FONT-FAMILY: 'Courier New'; FONT-SIZE=
: 10pt">If so, has this IPR been disclosed in compliance with IETF IPR guid=
elines ?<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"FONT-FAMILY: 'Courier New'; FONT-SIZE=
: 10pt">(see RFCs 3979, 4879, 3669 and 5378 for more details.)<o:p></o:p></=
span></p>
<p class=3D"MsoNormal"><span style=3D"FONT-FAMILY: 'Courier New'; FONT-SIZE=
: 10pt"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"FONT-FAMILY: 'Courier New'; FONT-SIZE=
: 10pt">If you are listed as a document author or contributor please send a=
n email to
<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"FONT-FAMILY: 'Courier New'; FONT-SIZE=
: 10pt">the TICTOC list regardless of whether or not you are aware of any r=
elevant IPR.
<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"FONT-FAMILY: 'Courier New'; FONT-SIZE=
: 10pt">A simple &#8220;I know of no IPR&#8221; is sufficient if that is th=
e case.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"FONT-FAMILY: 'Courier New'; FONT-SIZE=
: 10pt"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"FONT-FAMILY: 'Courier New'; FONT-SIZE=
: 10pt">If you are not an author but know of applicable IPR,<o:p></o:p></sp=
an></p>
<p class=3D"MsoNormal"><span style=3D"FONT-FAMILY: 'Courier New'; FONT-SIZE=
: 10pt">please send an email to the TICTOC list.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"FONT-FAMILY: 'Courier New'; FONT-SIZE=
: 10pt"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"FONT-FAMILY: 'Courier New'; FONT-SIZE=
: 10pt">Y(J)S<o:p></o:p></span></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
</blockquote>
</body>
</html>

--_000_20211F91F544D247976D84C5D778A4C3065A43SG70YWXCHMBA05zap_--

From davari@broadcom.com  Tue Jun 25 23:57:58 2013
Return-Path: <davari@broadcom.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 A778D21E8095 for <tictoc@ietfa.amsl.com>; Tue, 25 Jun 2013 23:57:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.598
X-Spam-Level: 
X-Spam-Status: No, score=-6.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id qA15OCn6YXAd for <tictoc@ietfa.amsl.com>; Tue, 25 Jun 2013 23:57:38 -0700 (PDT)
Received: from mms1.broadcom.com (mms1.broadcom.com [216.31.210.17]) by ietfa.amsl.com (Postfix) with ESMTP id 4ABB711E80C5 for <tictoc@ietf.org>; Tue, 25 Jun 2013 23:57:38 -0700 (PDT)
Received: from [10.9.208.53] by mms1.broadcom.com with ESMTP (Broadcom SMTP Relay (Email Firewall v6.5)); Tue, 25 Jun 2013 23:53:42 -0700
X-Server-Uuid: 06151B78-6688-425E-9DE2-57CB27892261
Received: from SJEXCHCAS07.corp.ad.broadcom.com (10.16.203.16) by IRVEXCHCAS06.corp.ad.broadcom.com (10.9.208.53) with Microsoft SMTP Server (TLS) id 14.1.438.0; Tue, 25 Jun 2013 23:57:24 -0700
Received: from SJEXCHMB12.corp.ad.broadcom.com ( [fe80::bc15:c1e1:c29a:36f7]) by SJEXCHCAS07.corp.ad.broadcom.com ( [::1]) with mapi id 14.01.0438.000; Tue, 25 Jun 2013 23:57:24 -0700
From: "Shahram Davari" <davari@broadcom.com>
To: "Bhatia, Manav (Manav)" <manav.bhatia@alcatel-lucent.com>
Thread-Topic: [TICTOC] IPR poll for draft-ietf-tictoc-1588overmpls
Thread-Index: AQHOcjpozFY1bpxWBkej/5TAmdOYAg==
Date: Wed, 26 Jun 2013 06:57:23 +0000
Message-ID: <FD4CC7E1-4914-4BFB-8041-048D8D28FE45@broadcom.com>
References: <07F7D7DED63154409F13298786A2ADC904E50C22@EXRAD5.ad.rad.co.il>, <20211F91F544D247976D84C5D778A4C3065A43@SG70YWXCHMBA05.zap.alcatel-lucent.com>
In-Reply-To: <20211F91F544D247976D84C5D778A4C3065A43@SG70YWXCHMBA05.zap.alcatel-lucent.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
MIME-Version: 1.0
X-WSS-ID: 7DD4507C31W41983701-01-01
Content-Type: multipart/alternative; boundary=_000_FD4CC7E149144BFB8041048D8D28FE45broadcomcom_
Cc: "tictoc@ietf.org" <tictoc@ietf.org>, "draft-ietf-tictoc-1588overmpls@tools.ietf.org" <draft-ietf-tictoc-1588overmpls@tools.ietf.org>
Subject: Re: [TICTOC] IPR poll for draft-ietf-tictoc-1588overmpls
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: Wed, 26 Jun 2013 06:57:58 -0000

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

I am not aware of any IPR on this draft.

Regards,
Shahram


On Jun 26, 2013, at 2:39 PM, "Bhatia, Manav (Manav)" <manav.bhatia@alcatel-=
lucent.com<mailto:manav.bhatia@alcatel-lucent.com>> wrote:

None from my side.

Cheers, Manav

________________________________
From: tictoc-bounces@ietf.org<mailto:tictoc-bounces@ietf.org> [mailto:ticto=
c-bounces@ietf.org] On Behalf Of Yaakov Stein
Sent: Wednesday, June 26, 2013 12:05 PM
To: draft-ietf-tictoc-1588overmpls@tools.ietf.org<mailto:draft-ietf-tictoc-=
1588overmpls@tools.ietf.org>; tictoc@ietf.org<mailto:tictoc@ietf.org>
Subject: [TICTOC] IPR poll for draft-ietf-tictoc-1588overmpls

TICTOC Working Group and authors of draft-ietf-tictoc-1588overmpls :

We are soon going to be performing a WG LC on this draft.

This email initiates an IPR poll to check whether there is any
IPR relating to this document that needs to be disclosed.

Are any of you aware of any applicable IPR ?

If so, has this IPR been disclosed in compliance with IETF IPR guidelines ?
(see RFCs 3979, 4879, 3669 and 5378 for more details.)

If you are listed as a document author or contributor please send an email =
to
the TICTOC list regardless of whether or not you are aware of any relevant =
IPR.
A simple =93I know of no IPR=94 is sufficient if that is the case.

If you are not an author but know of applicable IPR,
please send an email to the TICTOC list.

Y(J)S

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

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

<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3DWindows-1=
252">
</head>
<body dir=3D"auto">
<div>I am not aware of any IPR on this draft.<br>
<br>
Regards,
<div>Shahram</div>
<div><br>
</div>
</div>
<div><br>
On Jun 26, 2013, at 2:39 PM, &quot;Bhatia, Manav (Manav)&quot; &lt;<a href=
=3D"mailto:manav.bhatia@alcatel-lucent.com">manav.bhatia@alcatel-lucent.com=
</a>&gt; wrote:<br>
<br>
</div>
<blockquote type=3D"cite">
<div>
<meta name=3D"GENERATOR" content=3D"MSHTML 8.00.6001.18702">
<style>@font-face {
	font-family: Cambria Math;
}
@font-face {
	font-family: Calibri;
}
@font-face {
	font-family: Tahoma;
}
@page WordSection1 {size: 8.5in 11.0in; margin: 1.0in 1.25in 1.0in 1.25in; =
}
P.MsoNormal {
	MARGIN: 0in 0in 0pt; FONT-FAMILY: "Calibri","sans-serif"; FONT-SIZE: 11pt
}
LI.MsoNormal {
	MARGIN: 0in 0in 0pt; FONT-FAMILY: "Calibri","sans-serif"; FONT-SIZE: 11pt
}
DIV.MsoNormal {
	MARGIN: 0in 0in 0pt; FONT-FAMILY: "Calibri","sans-serif"; FONT-SIZE: 11pt
}
A:link {
	COLOR: blue; TEXT-DECORATION: underline; mso-style-priority: 99
}
SPAN.MsoHyperlink {
	COLOR: blue; TEXT-DECORATION: underline; mso-style-priority: 99
}
A:visited {
	COLOR: purple; TEXT-DECORATION: underline; mso-style-priority: 99
}
SPAN.MsoHyperlinkFollowed {
	COLOR: purple; TEXT-DECORATION: underline; mso-style-priority: 99
}
PRE {
	MARGIN: 0in 0in 0pt; FONT-FAMILY: "Courier New"; FONT-SIZE: 10pt; mso-styl=
e-priority: 99; mso-style-link: "HTML Preformatted Char"
}
P.MsoAcetate {
	MARGIN: 0in 0in 0pt; FONT-FAMILY: "Tahoma","sans-serif"; FONT-SIZE: 8pt; m=
so-style-priority: 99; mso-style-link: "Balloon Text Char"
}
LI.MsoAcetate {
	MARGIN: 0in 0in 0pt; FONT-FAMILY: "Tahoma","sans-serif"; FONT-SIZE: 8pt; m=
so-style-priority: 99; mso-style-link: "Balloon Text Char"
}
DIV.MsoAcetate {
	MARGIN: 0in 0in 0pt; FONT-FAMILY: "Tahoma","sans-serif"; FONT-SIZE: 8pt; m=
so-style-priority: 99; mso-style-link: "Balloon Text Char"
}
SPAN.EmailStyle17 {
	FONT-FAMILY: "Calibri","sans-serif"; COLOR: windowtext; mso-style-type: pe=
rsonal-compose
}
SPAN.BalloonTextChar {
	FONT-FAMILY: "Tahoma","sans-serif"; mso-style-priority: 99; mso-style-link=
: "Balloon Text"; mso-style-name: "Balloon Text Char"
}
SPAN.HTMLPreformattedChar {
	FONT-FAMILY: "Courier New"; mso-style-priority: 99; mso-style-link: "HTML =
Preformatted"; mso-style-name: "HTML Preformatted Char"
}
.MsoChpDefault {
	mso-style-type: export-only
}
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]-->
<div dir=3D"ltr" align=3D"left"><span class=3D"646323806-26062013"><font co=
lor=3D"#0000ff" size=3D"2" face=3D"Arial">None from&nbsp;my side.</font></s=
pan></div>
<div dir=3D"ltr" align=3D"left"><span class=3D"646323806-26062013"><font co=
lor=3D"#0000ff" size=3D"2" face=3D"Arial"></font></span>&nbsp;</div>
<div dir=3D"ltr" align=3D"left"><span class=3D"646323806-26062013"><font co=
lor=3D"#0000ff" size=3D"2" face=3D"Arial">Cheers, Manav</font></span></div>
<br>
<blockquote style=3D"BORDER-LEFT: #0000ff 2px solid; PADDING-LEFT: 5px; MAR=
GIN-LEFT: 5px; MARGIN-RIGHT: 0px" dir=3D"ltr">
<div dir=3D"ltr" lang=3D"en-us" class=3D"OutlookMessageHeader" align=3D"lef=
t">
<hr tabindex=3D"-1">
<font size=3D"2" face=3D"Tahoma"><b>From:</b> <a href=3D"mailto:tictoc-boun=
ces@ietf.org">
tictoc-bounces@ietf.org</a> [<a href=3D"mailto:tictoc-bounces@ietf.org">mai=
lto:tictoc-bounces@ietf.org</a>]
<b>On Behalf Of </b>Yaakov Stein<br>
<b>Sent:</b> Wednesday, June 26, 2013 12:05 PM<br>
<b>To:</b> <a href=3D"mailto:draft-ietf-tictoc-1588overmpls@tools.ietf.org"=
>draft-ietf-tictoc-1588overmpls@tools.ietf.org</a>;
<a href=3D"mailto:tictoc@ietf.org">tictoc@ietf.org</a><br>
<b>Subject:</b> [TICTOC] IPR poll for draft-ietf-tictoc-1588overmpls<br>
</font><br>
</div>
<div></div>
<div class=3D"WordSection1">
<p class=3D"MsoNormal"><span style=3D"FONT-FAMILY: 'Courier New'; FONT-SIZE=
: 10pt">TICTOC Working Group and authors of
</span><span style=3D"FONT-FAMILY: 'Courier New'; FONT-SIZE: 10pt">draft-ie=
tf-tictoc-1588overmpls :<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"FONT-FAMILY: 'Courier New'; FONT-SIZE=
: 10pt"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"FONT-FAMILY: 'Courier New'; FONT-SIZE=
: 10pt">We are soon going to be performing a WG LC on this draft.<o:p></o:p=
></span></p>
<p class=3D"MsoNormal"><span style=3D"FONT-FAMILY: 'Courier New'; FONT-SIZE=
: 10pt"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"FONT-FAMILY: 'Courier New'; FONT-SIZE=
: 10pt">This email initiates an IPR poll to check whether there is any<o:p>=
</o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"FONT-FAMILY: 'Courier New'; FONT-SIZE=
: 10pt">IPR relating to this document that needs to be disclosed.<o:p></o:p=
></span></p>
<p class=3D"MsoNormal"><span style=3D"FONT-FAMILY: 'Courier New'; FONT-SIZE=
: 10pt"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"FONT-FAMILY: 'Courier New'; FONT-SIZE=
: 10pt">Are any of you aware of any applicable IPR ?<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"FONT-FAMILY: 'Courier New'; FONT-SIZE=
: 10pt"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"FONT-FAMILY: 'Courier New'; FONT-SIZE=
: 10pt">If so, has this IPR been disclosed in compliance with IETF IPR guid=
elines ?<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"FONT-FAMILY: 'Courier New'; FONT-SIZE=
: 10pt">(see RFCs 3979, 4879, 3669 and 5378 for more details.)<o:p></o:p></=
span></p>
<p class=3D"MsoNormal"><span style=3D"FONT-FAMILY: 'Courier New'; FONT-SIZE=
: 10pt"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"FONT-FAMILY: 'Courier New'; FONT-SIZE=
: 10pt">If you are listed as a document author or contributor please send a=
n email to
<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"FONT-FAMILY: 'Courier New'; FONT-SIZE=
: 10pt">the TICTOC list regardless of whether or not you are aware of any r=
elevant IPR.
<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"FONT-FAMILY: 'Courier New'; FONT-SIZE=
: 10pt">A simple =93I know of no IPR=94 is sufficient if that is the case.<=
o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"FONT-FAMILY: 'Courier New'; FONT-SIZE=
: 10pt"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"FONT-FAMILY: 'Courier New'; FONT-SIZE=
: 10pt">If you are not an author but know of applicable IPR,<o:p></o:p></sp=
an></p>
<p class=3D"MsoNormal"><span style=3D"FONT-FAMILY: 'Courier New'; FONT-SIZE=
: 10pt">please send an email to the TICTOC list.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"FONT-FAMILY: 'Courier New'; FONT-SIZE=
: 10pt"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"FONT-FAMILY: 'Courier New'; FONT-SIZE=
: 10pt">Y(J)S<o:p></o:p></span></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
</blockquote>
</div>
</blockquote>
<blockquote type=3D"cite">
<div><span>_______________________________________________</span><br>
<span>TICTOC mailing list</span><br>
<span><a href=3D"mailto:TICTOC@ietf.org">TICTOC@ietf.org</a></span><br>
<span><a href=3D"https://www.ietf.org/mailman/listinfo/tictoc">https://www.=
ietf.org/mailman/listinfo/tictoc</a></span><br>
</div>
</blockquote>
</body>
</html>

--_000_FD4CC7E149144BFB8041048D8D28FE45broadcomcom_--


From lmontini@cisco.com  Wed Jun 26 01:25:31 2013
Return-Path: <lmontini@cisco.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 C82DB21E811E for <tictoc@ietfa.amsl.com>; Wed, 26 Jun 2013 01:25:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.598
X-Spam-Level: 
X-Spam-Status: No, score=-10.598 tagged_above=-999 required=5 tests=[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 iCDXvZqY11zK for <tictoc@ietfa.amsl.com>; Wed, 26 Jun 2013 01:25:18 -0700 (PDT)
Received: from rcdn-iport-9.cisco.com (rcdn-iport-9.cisco.com [173.37.86.80]) by ietfa.amsl.com (Postfix) with ESMTP id B14EC21E8108 for <tictoc@ietf.org>; Wed, 26 Jun 2013 01:25:02 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=13475; q=dns/txt; s=iport; t=1372235102; x=1373444702; h=from:to:cc:subject:date:message-id:in-reply-to: mime-version; bh=mxNN74LSErCO4LLj3YV1NY2g7YRUXlOUw3F58aP0zN8=; b=FZh5C3N04hCU54p47++H4hDv5F2Age0DdwtBWCEGl4XCRCnc+dcE85x/ Yu1M0S71nXogIIfqJOzEMcRZm5a5Iy0xJ/WI3qKxUOK0NtElTxfOSSzgL VjZkCqjmx+bKkjaSkBotpg5Ldw2l5QE6e+2Y3XbWpbWlSSJkap5/iw4Fw w=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgYFAIGkylGtJXG9/2dsb2JhbABagkVEMUm+d4EGFnSCIwEBAQQBAQEqQQsSAQgRAwEBAQsdLgsUCQgBAQQOBQiIBgy6KQSOCIERBBwNBAYBgwJhA6kIgxGBcTc
X-IronPort-AV: E=Sophos;i="4.87,941,1363132800";  d="scan'208,217";a="224563775"
Received: from rcdn-core2-2.cisco.com ([173.37.113.189]) by rcdn-iport-9.cisco.com with ESMTP; 26 Jun 2013 08:24:56 +0000
Received: from xhc-aln-x10.cisco.com (xhc-aln-x10.cisco.com [173.36.12.84]) by rcdn-core2-2.cisco.com (8.14.5/8.14.5) with ESMTP id r5Q8OuCE004982 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Wed, 26 Jun 2013 08:24:56 GMT
Received: from xmb-rcd-x11.cisco.com ([169.254.1.5]) by xhc-aln-x10.cisco.com ([173.36.12.84]) with mapi id 14.02.0318.004; Wed, 26 Jun 2013 03:24:55 -0500
From: "Laurent Montini (lmontini)" <lmontini@cisco.com>
To: Shahram Davari <davari@broadcom.com>, "Bhatia, Manav (Manav)" <manav.bhatia@alcatel-lucent.com>
Thread-Topic: [TICTOC] IPR poll for draft-ietf-tictoc-1588overmpls
Thread-Index: Ac5yN1LBtEAvMVvBTJuZH02+U0VP/gAAHQowAAsipYAAB0FIgA==
Date: Wed, 26 Jun 2013 08:24:55 +0000
Message-ID: <D5E74087805F86429567D40F1A7BA5EF0F7710D8@xmb-rcd-x11.cisco.com>
In-Reply-To: <FD4CC7E1-4914-4BFB-8041-048D8D28FE45@broadcom.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/14.3.5.130515
x-originating-ip: [10.55.225.226]
Content-Type: multipart/alternative; boundary="_000_D5E74087805F86429567D40F1A7BA5EF0F7710D8xmbrcdx11ciscoc_"
MIME-Version: 1.0
Cc: "tictoc@ietf.org" <tictoc@ietf.org>, "draft-ietf-tictoc-1588overmpls@tools.ietf.org" <draft-ietf-tictoc-1588overmpls@tools.ietf.org>
Subject: Re: [TICTOC] IPR poll for draft-ietf-tictoc-1588overmpls
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: Wed, 26 Jun 2013 08:25:32 -0000

--_000_D5E74087805F86429567D40F1A7BA5EF0F7710D8xmbrcdx11ciscoc_
Content-Type: text/plain; charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable

Me neither.

Thanks,
Laurent

From: Shahram Davari <davari@broadcom.com<mailto:davari@broadcom.com>>
Date: Wednesday, June 26, 2013 8:57 AM
To: Manav Bhatia <manav.bhatia@alcatel-lucent.com<mailto:manav.bhatia@alcat=
el-lucent.com>>
Cc: Yaakov Stein <yaakov_s@rad.com<mailto:yaakov_s@rad.com>>, "draft-ietf-t=
ictoc-1588overmpls@tools.ietf.org<mailto:draft-ietf-tictoc-1588overmpls@too=
ls.ietf.org>" <draft-ietf-tictoc-1588overmpls@tools.ietf.org<mailto:draft-i=
etf-tictoc-1588overmpls@tools.ietf.org>>, "tictoc@ietf.org<mailto:tictoc@ie=
tf.org>" <tictoc@ietf.org<mailto:tictoc@ietf.org>>
Subject: Re: [TICTOC] IPR poll for draft-ietf-tictoc-1588overmpls
Resent-From: <draft-alias-bounces@tools.ietf.org<mailto:draft-alias-bounces=
@tools.ietf.org>>
Resent-To: Amit Oren <amito@broadcom.com<mailto:amito@broadcom.com>>, Shahr=
am Davari <davari@broadcom.com<mailto:davari@broadcom.com>>, lmontini <lmon=
tini@cisco.com<mailto:lmontini@cisco.com>>, Manav Bhatia <manav.bhatia@alca=
tel-lucent.com<mailto:manav.bhatia@alcatel-lucent.com>>, Peter Roberts <pet=
er.roberts@alcatel-lucent.com<mailto:peter.roberts@alcatel-lucent.com>>
Resent-Date: Wednesday, June 26, 2013 8:57 AM

I am not aware of any IPR on this draft.

Regards,
Shahram


On Jun 26, 2013, at 2:39 PM, "Bhatia, Manav (Manav)" <manav.bhatia@alcatel-=
lucent.com<mailto:manav.bhatia@alcatel-lucent.com>> wrote:

None from my side.

Cheers, Manav

________________________________
From: tictoc-bounces@ietf.org<mailto:tictoc-bounces@ietf.org> [mailto:ticto=
c-bounces@ietf.org] On Behalf Of Yaakov Stein
Sent: Wednesday, June 26, 2013 12:05 PM
To: draft-ietf-tictoc-1588overmpls@tools.ietf.org<mailto:draft-ietf-tictoc-=
1588overmpls@tools.ietf.org>; tictoc@ietf.org<mailto:tictoc@ietf.org>
Subject: [TICTOC] IPR poll for draft-ietf-tictoc-1588overmpls

TICTOC Working Group and authors of draft-ietf-tictoc-1588overmpls :

We are soon going to be performing a WG LC on this draft.

This email initiates an IPR poll to check whether there is any
IPR relating to this document that needs to be disclosed.

Are any of you aware of any applicable IPR ?

If so, has this IPR been disclosed in compliance with IETF IPR guidelines ?
(see RFCs 3979, 4879, 3669 and 5378 for more details.)

If you are listed as a document author or contributor please send an email =
to
the TICTOC list regardless of whether or not you are aware of any relevant =
IPR.
A simple =93I know of no IPR=94 is sufficient if that is the case.

If you are not an author but know of applicable IPR,
please send an email to the TICTOC list.

Y(J)S

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

--_000_D5E74087805F86429567D40F1A7BA5EF0F7710D8xmbrcdx11ciscoc_
Content-Type: text/html; charset="Windows-1252"
Content-ID: <C15E315B524B5B49AC784BE127A5E65E@emea.cisco.com>
Content-Transfer-Encoding: quoted-printable

<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3DWindows-1=
252">
</head>
<body style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-lin=
e-break: after-white-space; color: rgb(0, 0, 0); font-size: 14px; font-fami=
ly: Calibri, sans-serif; ">
<div>Me neither.</div>
<div><br>
</div>
<div>Thanks,</div>
<div>Laurent</div>
<div><br>
</div>
<span id=3D"OLK_SRC_BODY_SECTION">
<div style=3D"font-family:Calibri; font-size:11pt; text-align:left; color:b=
lack; BORDER-BOTTOM: medium none; BORDER-LEFT: medium none; PADDING-BOTTOM:=
 0in; PADDING-LEFT: 0in; PADDING-RIGHT: 0in; BORDER-TOP: #b5c4df 1pt solid;=
 BORDER-RIGHT: medium none; PADDING-TOP: 3pt">
<span style=3D"font-weight:bold">From: </span>Shahram Davari &lt;<a href=3D=
"mailto:davari@broadcom.com">davari@broadcom.com</a>&gt;<br>
<span style=3D"font-weight:bold">Date: </span>Wednesday, June 26, 2013 8:57=
 AM<br>
<span style=3D"font-weight:bold">To: </span>Manav Bhatia &lt;<a href=3D"mai=
lto:manav.bhatia@alcatel-lucent.com">manav.bhatia@alcatel-lucent.com</a>&gt=
;<br>
<span style=3D"font-weight:bold">Cc: </span>Yaakov Stein &lt;<a href=3D"mai=
lto:yaakov_s@rad.com">yaakov_s@rad.com</a>&gt;, &quot;<a href=3D"mailto:dra=
ft-ietf-tictoc-1588overmpls@tools.ietf.org">draft-ietf-tictoc-1588overmpls@=
tools.ietf.org</a>&quot; &lt;<a href=3D"mailto:draft-ietf-tictoc-1588overmp=
ls@tools.ietf.org">draft-ietf-tictoc-1588overmpls@tools.ietf.org</a>&gt;,
 &quot;<a href=3D"mailto:tictoc@ietf.org">tictoc@ietf.org</a>&quot; &lt;<a =
href=3D"mailto:tictoc@ietf.org">tictoc@ietf.org</a>&gt;<br>
<span style=3D"font-weight:bold">Subject: </span>Re: [TICTOC] IPR poll for =
draft-ietf-tictoc-1588overmpls<br>
<span style=3D"font-weight:bold">Resent-From: </span>&lt;<a href=3D"mailto:=
draft-alias-bounces@tools.ietf.org">draft-alias-bounces@tools.ietf.org</a>&=
gt;<br>
<span style=3D"font-weight:bold">Resent-To: </span>Amit Oren &lt;<a href=3D=
"mailto:amito@broadcom.com">amito@broadcom.com</a>&gt;, Shahram Davari &lt;=
<a href=3D"mailto:davari@broadcom.com">davari@broadcom.com</a>&gt;, lmontin=
i &lt;<a href=3D"mailto:lmontini@cisco.com">lmontini@cisco.com</a>&gt;,
 Manav Bhatia &lt;<a href=3D"mailto:manav.bhatia@alcatel-lucent.com">manav.=
bhatia@alcatel-lucent.com</a>&gt;, Peter Roberts &lt;<a href=3D"mailto:pete=
r.roberts@alcatel-lucent.com">peter.roberts@alcatel-lucent.com</a>&gt;<br>
<span style=3D"font-weight:bold">Resent-Date: </span>Wednesday, June 26, 20=
13 8:57 AM<br>
</div>
<div><br>
</div>
<div>
<div dir=3D"auto">
<div>I am not aware of any IPR on this draft.<br>
<br>
Regards,
<div>Shahram</div>
<div><br>
</div>
</div>
<div><br>
On Jun 26, 2013, at 2:39 PM, &quot;Bhatia, Manav (Manav)&quot; &lt;<a href=
=3D"mailto:manav.bhatia@alcatel-lucent.com">manav.bhatia@alcatel-lucent.com=
</a>&gt; wrote:<br>
<br>
</div>
<blockquote type=3D"cite">
<div>
<meta name=3D"GENERATOR" content=3D"MSHTML 8.00.6001.18702">
<style>@font-face {
	font-family: Cambria Math;
}
@font-face {
	font-family: Calibri;
}
@font-face {
	font-family: Tahoma;
}
@page WordSection1 {size: 8.5in 11.0in; margin: 1.0in 1.25in 1.0in 1.25in; =
}
P.MsoNormal {
	MARGIN: 0in 0in 0pt; FONT-FAMILY: "Calibri","sans-serif"; FONT-SIZE: 11pt
}
LI.MsoNormal {
	MARGIN: 0in 0in 0pt; FONT-FAMILY: "Calibri","sans-serif"; FONT-SIZE: 11pt
}
DIV.MsoNormal {
	MARGIN: 0in 0in 0pt; FONT-FAMILY: "Calibri","sans-serif"; FONT-SIZE: 11pt
}
A:link {
	COLOR: blue; TEXT-DECORATION: underline; mso-style-priority: 99
}
SPAN.MsoHyperlink {
	COLOR: blue; TEXT-DECORATION: underline; mso-style-priority: 99
}
A:visited {
	COLOR: purple; TEXT-DECORATION: underline; mso-style-priority: 99
}
SPAN.MsoHyperlinkFollowed {
	COLOR: purple; TEXT-DECORATION: underline; mso-style-priority: 99
}
PRE {
	MARGIN: 0in 0in 0pt; FONT-FAMILY: "Courier New"; FONT-SIZE: 10pt; mso-styl=
e-priority: 99; mso-style-link: "HTML Preformatted Char"
}
P.MsoAcetate {
	MARGIN: 0in 0in 0pt; FONT-FAMILY: "Tahoma","sans-serif"; FONT-SIZE: 8pt; m=
so-style-priority: 99; mso-style-link: "Balloon Text Char"
}
LI.MsoAcetate {
	MARGIN: 0in 0in 0pt; FONT-FAMILY: "Tahoma","sans-serif"; FONT-SIZE: 8pt; m=
so-style-priority: 99; mso-style-link: "Balloon Text Char"
}
DIV.MsoAcetate {
	MARGIN: 0in 0in 0pt; FONT-FAMILY: "Tahoma","sans-serif"; FONT-SIZE: 8pt; m=
so-style-priority: 99; mso-style-link: "Balloon Text Char"
}
SPAN.EmailStyle17 {
	FONT-FAMILY: "Calibri","sans-serif"; COLOR: windowtext; mso-style-type: pe=
rsonal-compose
}
SPAN.BalloonTextChar {
	FONT-FAMILY: "Tahoma","sans-serif"; mso-style-priority: 99; mso-style-link=
: "Balloon Text"; mso-style-name: "Balloon Text Char"
}
SPAN.HTMLPreformattedChar {
	FONT-FAMILY: "Courier New"; mso-style-priority: 99; mso-style-link: "HTML =
Preformatted"; mso-style-name: "HTML Preformatted Char"
}
.MsoChpDefault {
	mso-style-type: export-only
}
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]-->
<div dir=3D"ltr" align=3D"left"><span class=3D"646323806-26062013"><font co=
lor=3D"#0000ff" size=3D"2" face=3D"Arial">None from&nbsp;my side.</font></s=
pan></div>
<div dir=3D"ltr" align=3D"left"><span class=3D"646323806-26062013"><font co=
lor=3D"#0000ff" size=3D"2" face=3D"Arial"></font></span>&nbsp;</div>
<div dir=3D"ltr" align=3D"left"><span class=3D"646323806-26062013"><font co=
lor=3D"#0000ff" size=3D"2" face=3D"Arial">Cheers, Manav</font></span></div>
<br>
<blockquote style=3D"BORDER-LEFT: #0000ff 2px solid; PADDING-LEFT: 5px; MAR=
GIN-LEFT: 5px; MARGIN-RIGHT: 0px" dir=3D"ltr">
<div dir=3D"ltr" lang=3D"en-us" class=3D"OutlookMessageHeader" align=3D"lef=
t">
<hr tabindex=3D"-1">
<font size=3D"2" face=3D"Tahoma"><b>From:</b> <a href=3D"mailto:tictoc-boun=
ces@ietf.org">
tictoc-bounces@ietf.org</a> [<a href=3D"mailto:tictoc-bounces@ietf.org">mai=
lto:tictoc-bounces@ietf.org</a>]
<b>On Behalf Of </b>Yaakov Stein<br>
<b>Sent:</b> Wednesday, June 26, 2013 12:05 PM<br>
<b>To:</b> <a href=3D"mailto:draft-ietf-tictoc-1588overmpls@tools.ietf.org"=
>draft-ietf-tictoc-1588overmpls@tools.ietf.org</a>;
<a href=3D"mailto:tictoc@ietf.org">tictoc@ietf.org</a><br>
<b>Subject:</b> [TICTOC] IPR poll for draft-ietf-tictoc-1588overmpls<br>
</font><br>
</div>
<div></div>
<div class=3D"WordSection1">
<p class=3D"MsoNormal"><span style=3D"font-family: 'Courier New'; font-size=
: 10pt; ">TICTOC Working Group and authors of
</span><span style=3D"font-family: 'Courier New'; font-size: 10pt; ">draft-=
ietf-tictoc-1588overmpls :<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-family: 'Courier New'; font-size=
: 10pt; "><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-family: 'Courier New'; font-size=
: 10pt; ">We are soon going to be performing a WG LC on this draft.<o:p></o=
:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-family: 'Courier New'; font-size=
: 10pt; "><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-family: 'Courier New'; font-size=
: 10pt; ">This email initiates an IPR poll to check whether there is any<o:=
p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-family: 'Courier New'; font-size=
: 10pt; ">IPR relating to this document that needs to be disclosed.<o:p></o=
:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-family: 'Courier New'; font-size=
: 10pt; "><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-family: 'Courier New'; font-size=
: 10pt; ">Are any of you aware of any applicable IPR ?<o:p></o:p></span></p=
>
<p class=3D"MsoNormal"><span style=3D"font-family: 'Courier New'; font-size=
: 10pt; "><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-family: 'Courier New'; font-size=
: 10pt; ">If so, has this IPR been disclosed in compliance with IETF IPR gu=
idelines ?<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-family: 'Courier New'; font-size=
: 10pt; ">(see RFCs 3979, 4879, 3669 and 5378 for more details.)<o:p></o:p>=
</span></p>
<p class=3D"MsoNormal"><span style=3D"font-family: 'Courier New'; font-size=
: 10pt; "><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-family: 'Courier New'; font-size=
: 10pt; ">If you are listed as a document author or contributor please send=
 an email to
<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-family: 'Courier New'; font-size=
: 10pt; ">the TICTOC list regardless of whether or not you are aware of any=
 relevant IPR.
<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-family: 'Courier New'; font-size=
: 10pt; ">A simple =93I know of no IPR=94 is sufficient if that is the case=
.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-family: 'Courier New'; font-size=
: 10pt; "><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-family: 'Courier New'; font-size=
: 10pt; ">If you are not an author but know of applicable IPR,<o:p></o:p></=
span></p>
<p class=3D"MsoNormal"><span style=3D"font-family: 'Courier New'; font-size=
: 10pt; ">please send an email to the TICTOC list.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-family: 'Courier New'; font-size=
: 10pt; "><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-family: 'Courier New'; font-size=
: 10pt; ">Y(J)S<o:p></o:p></span></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
</blockquote>
</div>
</blockquote>
<blockquote type=3D"cite">
<div><span>_______________________________________________</span><br>
<span>TICTOC mailing list</span><br>
<span><a href=3D"mailto:TICTOC@ietf.org">TICTOC@ietf.org</a></span><br>
<span><a href=3D"https://www.ietf.org/mailman/listinfo/tictoc">https://www.=
ietf.org/mailman/listinfo/tictoc</a></span><br>
</div>
</blockquote>
</div>
</div>
</span>
</body>
</html>

--_000_D5E74087805F86429567D40F1A7BA5EF0F7710D8xmbrcdx11ciscoc_--
