
From yaakov_s@rad.com  Fri Aug  5 16:22:00 2011
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 DC77B11E807B for <tictoc@ietfa.amsl.com>; Fri,  5 Aug 2011 16:22:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.584
X-Spam-Level: 
X-Spam-Status: No, score=-102.584 tagged_above=-999 required=5 tests=[AWL=-0.585, BAYES_00=-2.599, J_CHICKENPOX_66=0.6, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id m0XHaGh-FpGP for <tictoc@ietfa.amsl.com>; Fri,  5 Aug 2011 16:21:59 -0700 (PDT)
Received: from antivir1.rad.co.il (antivir1.rad.co.il [62.0.23.193]) by ietfa.amsl.com (Postfix) with ESMTP id 486F511E8078 for <tictoc@ietf.org>; Fri,  5 Aug 2011 16:21:57 -0700 (PDT)
Received: from exrad5.ad.rad.co.il ([192.114.24.28]) by antivir1.rad.co.il with ESMTP; 06 Aug 2011 02:22:14 +0300
Received: from EXUS4-DRP.ad.rad.co.il (192.114.24.119) by EXRAD5.ad.rad.co.il (192.114.24.28) with Microsoft SMTP Server (TLS) id 14.1.218.12; Sat, 6 Aug 2011 02:22:03 +0300
Received: from EXRAD5.ad.rad.co.il ([192.114.24.28]) by exus4-drp.ad.rad.co.il ([fe80::5d6f:c2cb:2468:ee2%16]) with mapi id 14.01.0289.001; Sat, 6 Aug 2011 02:22:03 +0300
From: Yaakov Stein <yaakov_s@rad.com>
To: Hal Murray <hmurray@megapathdsl.net>, "tictoc@ietf.org" <tictoc@ietf.org>
Thread-Topic: [TICTOC] The Need for Checksum Extension
Thread-Index: AQHMTiQbRpEJJlrC1kmFT9KOG6ZV95UO7g0Q
Date: Fri, 5 Aug 2011 23:22:02 +0000
Message-ID: <07F7D7DED63154409F13298786A2ADC903E96505@EXRAD5.ad.rad.co.il>
References: Message from tictoc-request@ietf.org of "Thu,	28 Jul 2011 18:08:12 PDT."	<mailman.1669.1311901692.23921.tictoc@ietf.org> <20110729191707.680CD800037@ip-64-139-1-69.sjc.megapath.net>
In-Reply-To: <20110729191707.680CD800037@ip-64-139-1-69.sjc.megapath.net>
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: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: Re: [TICTOC] The Need for Checksum Extension
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, 05 Aug 2011 23:22:01 -0000

Hal

Yes, I know that CRC CAN be updated rather than recomputed,
but it is not as easy as you imply.

The linearity means that if we have computed the CRC on two bit sequences o=
f equal length
and are interested in knowing the result for the xor of those two sequences=
,
then we don't have to work very hard.

However, that is NOT what is needed for an update,=20
as we don't know the CRC of the sequence which contains the header change a=
nd all the zeros
for the entire message.

To perform an update efficiency you have to build M =3D the 32 by 32 bit ma=
trix of the CRC,=20
matrix multiply this matrix by itself enough times to move it to the offset=
 where the field changes
(this can be done off-line), matrix*vector multiply with the original and c=
hanged fields and xor these together,=20
and then xor all of these with the original CRC.

I agree that this is in principle faster than doing the entire CRC.
However, since the offsets of the changes can vary (depending on VLAN tags,=
 etc)
and there are at least two places with changes (the CF and the UDP checksum=
),
it is cumbersome.

Y(J)S

-----Original Message-----
From: tictoc-bounces@ietf.org [mailto:tictoc-bounces@ietf.org] On Behalf Of=
 Hal Murray
Sent: Friday, July 29, 2011 22:17
To: tictoc@ietf.org
Cc: hmurray@megapathdsl.net
Subject: Re: [TICTOC] The Need for Checksum Extension


> CRC can not be readily updated, and so needs to iterate over the entire
> payload, but is still calculated on the fly. So the UDP checksum, which C=
AN
> be readily updated, can certainly be.=20

The CRC can be updated rather than recalculating the CRC of the whole messa=
ge.

I'm rusty on this stuff and it probably doesn't matter since it takes about=
=20
as much hardware/cycles as recomputing the CRC of the whole packet.  It mig=
ht=20
be interesting if you are concerned about corruption while a packet is in=20
memory.

The key idea is linearity:
  CRC(A+B) =3D CRC(A)+CRC(B) where + is XOR.
In this context, A is the original message and B is the XOR of the old and=
=20
new messages.  That's the XOR of the old/new words you are changing padded=
=20
with enough 0s to line up correctly.  You end up computing the CRC of a=20
pseudo message rather than the real message.  (Don't forget to include the=
=20
UDP checksum as well as the slot you are changing.)



--=20
These are my opinions, not necessarily my employer's.  I hate spam.



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

From talmi@marvell.com  Sat Aug  6 10:42:37 2011
Return-Path: <talmi@marvell.com>
X-Original-To: tictoc@ietfa.amsl.com
Delivered-To: tictoc@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2B7C921F84FD for <tictoc@ietfa.amsl.com>; Sat,  6 Aug 2011 10:42:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.281
X-Spam-Level: 
X-Spam-Status: No, score=-3.281 tagged_above=-999 required=5 tests=[AWL=-0.683, BAYES_00=-2.599, HTML_MESSAGE=0.001]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2m6j3Bgz2-rJ for <tictoc@ietfa.amsl.com>; Sat,  6 Aug 2011 10:42:36 -0700 (PDT)
Received: from galiil.marvell.com (galiil.marvell.com [199.203.130.254]) by ietfa.amsl.com (Postfix) with ESMTP id D318C21F8551 for <tictoc@ietf.org>; Sat,  6 Aug 2011 10:42:33 -0700 (PDT)
From: Tal Mizrahi <talmi@marvell.com>
To: Ron Cohen <ronc.ntear@gmail.com>, "tictoc@ietf.org" <tictoc@ietf.org>
Date: Sat, 6 Aug 2011 20:42:45 +0300
Thread-Topic: [TICTOC] The Need for Checksum Extension
Thread-Index: AcxNbfYRtIOvX2NjQVWo8np0NdjaUgG8DezQ
Message-ID: <74470498B659FA4687F0B0018C19A89C0134BF782962@IL-MB01.marvell.com>
References: <CALMYT9TP6WqrZgR2+o_zk7QwYXFE28d4QBo8Q89q+OYJ2cvy1Q@mail.gmail.com>
In-Reply-To: <CALMYT9TP6WqrZgR2+o_zk7QwYXFE28d4QBo8Q89q+OYJ2cvy1Q@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: multipart/alternative; boundary="_000_74470498B659FA4687F0B0018C19A89C0134BF782962ILMB01marve_"
MIME-Version: 1.0
Subject: Re: [TICTOC] The Need for Checksum Extension
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, 06 Aug 2011 17:42:37 -0000

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

Hi,

Sorry for the late reply, I missed this thread.
Ron, your observation is correct.

With that said, from the implementation perspective, there is a benefit to =
have a single procedure (and a single implementation) for updating the UDP =
checksum in a timestamped packet (PTP, NTP, OWAMP, TWAMP). So for PTP the U=
DP Checksum update clearly benefits from the Checksum Trailer. As for NTP a=
nd OWAMP, the benefit of using the Checksum Trailer is from having the same=
 UDP checksum  update flow as the one for PTP.
At the end of the day this draft is about easy implementation - we are tryi=
ng to define the Checksum Trailer in a way that will allow easy implementat=
ion, while not requiring any changes in existing implementations.

Regards,
Tal.
From: tictoc-bounces@ietf.org [mailto:tictoc-bounces@ietf.org] On Behalf Of=
 Ron Cohen
Sent: Friday, July 29, 2011 12:33 AM
To: tictoc@ietf.org
Subject: [TICTOC] The Need for Checksum Extension

Hi,

I'd like to clarify my comment during the meeting.

According to RFC1612 Eqn 3 (incremental checksum update):

HC' =3D ~(C + (-m) + m') =3D ~(~HC + ~m + m')

Where HC' is the updated checksum, HC is the current (message) checksum, m'=
 in the new value that is going to be written instead of the value m in the=
 message.

If I know that value of m is zero, I can calculate the new checksum using t=
he old checksum and the new value alone.

That is, if the NTP/OWAMP/TWAMP CPU sets the transmit timestamp to zero (i.=
e. m =3D 0), the FPGA or switch that measures the transmit timestamp once t=
he first byte of the message is sent on the wire, can update the UDP checks=
um itself incrementally and doesn't need the extension. The extension is ne=
ed only if you have to read the timestamp which appears later in the packet=
 in order to update the checksum.

This is very different from 'real' intermediate devices (i.e. transparent c=
locks) used by PTP.

Best,
Ron

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

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40"><head><meta http-equiv=3DContent-Type content=
=3D"text/html; charset=3Dus-ascii"><meta name=3DGenerator content=3D"Micros=
oft Word 14 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
span.EmailStyle17
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-family:"Calibri","sans-serif";}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.25in 1.0in 1.25in;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]--></head><body lang=3DEN-US link=3Dblue vli=
nk=3Dpurple><div class=3DWordSection1><p class=3DMsoNormal>Hi,<o:p></o:p></=
p><p class=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3DMsoNormal>Sorry for =
the late reply, I missed this thread.<o:p></o:p></p><p class=3DMsoNormal>Ro=
n, your observation is correct.<o:p></o:p></p><p class=3DMsoNormal><o:p>&nb=
sp;</o:p></p><p class=3DMsoNormal>With that said, from the implementation p=
erspective, there is a benefit to have a single procedure (and a single imp=
lementation) for updating the UDP checksum in a timestamped packet (PTP, NT=
P, OWAMP, TWAMP). So for PTP the UDP Checksum update clearly benefits from =
the Checksum Trailer. As for NTP and OWAMP, the benefit of using the Checks=
um Trailer is from having the same UDP checksum &nbsp;update flow as the on=
e for PTP.<o:p></o:p></p><p class=3DMsoNormal>At the end of the day this dr=
aft is about easy implementation - we are trying to define the Checksum Tra=
iler in a way that will allow easy implementation, while not requiring any =
changes in existing implementations.<o:p></o:p></p><p class=3DMsoNormal><o:=
p>&nbsp;</o:p></p><p class=3DMsoNormal>Regards,<span style=3D'font-size:11.=
0pt;font-family:"Calibri","sans-serif"'><o:p></o:p></span></p><p class=3DMs=
oNormal><span style=3D'font-size:10.0pt;font-family:"Arial","sans-serif"'>T=
al.</span><o:p></o:p></p><p class=3DMsoNormal><b><span style=3D'font-size:1=
0.0pt;font-family:"Tahoma","sans-serif"'>From:</span></b><span style=3D'fon=
t-size:10.0pt;font-family:"Tahoma","sans-serif"'> tictoc-bounces@ietf.org [=
mailto:tictoc-bounces@ietf.org] <b>On Behalf Of </b>Ron Cohen<br><b>Sent:</=
b> Friday, July 29, 2011 12:33 AM<br><b>To:</b> tictoc@ietf.org<br><b>Subje=
ct:</b> [TICTOC] The Need for Checksum Extension<o:p></o:p></span></p><p cl=
ass=3DMsoNormal><o:p>&nbsp;</o:p></p><div><p class=3DMsoNormal style=3D'mar=
gin-bottom:12.0pt'>Hi,<br><br>I'd like to clarify my comment during the mee=
ting.<br><br>According to RFC1612 Eqn 3 (incremental checksum update):<br><=
br>HC' =3D ~(C + (-m) + m') =3D ~(~HC + ~m + m')<br><br>Where HC' is the up=
dated checksum, HC is the current (message) checksum, m' in the new value t=
hat is going to be written instead of the value m in the message.<br><br>If=
 I know that value of m is zero, I can calculate the new checksum using the=
 old checksum and the new value alone.<br><br>That is, if the NTP/OWAMP/TWA=
MP CPU sets the transmit timestamp to zero (i.e. m =3D 0), the FPGA or swit=
ch that measures the transmit timestamp once the first byte of the message =
is sent on the wire, can update the UDP checksum itself incrementally and d=
oesn't need the extension. The extension is need only if you have to read t=
he timestamp which appears later in the packet in order to update the check=
sum.<br><br>This is very different from 'real' intermediate devices (i.e. t=
ransparent clocks) used by PTP.<br><br>Best,<br>Ron<o:p></o:p></p></div></d=
iv></body></html>=

--_000_74470498B659FA4687F0B0018C19A89C0134BF782962ILMB01marve_--

From ronc.ntear@gmail.com  Sun Aug  7 00:59:30 2011
Return-Path: <ronc.ntear@gmail.com>
X-Original-To: tictoc@ietfa.amsl.com
Delivered-To: tictoc@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 366C521F869D for <tictoc@ietfa.amsl.com>; Sun,  7 Aug 2011 00:59:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.598
X-Spam-Level: 
X-Spam-Status: No, score=-3.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, 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 EO-jjWMCq6Al for <tictoc@ietfa.amsl.com>; Sun,  7 Aug 2011 00:59:29 -0700 (PDT)
Received: from mail-gx0-f172.google.com (mail-gx0-f172.google.com [209.85.161.172]) by ietfa.amsl.com (Postfix) with ESMTP id 894FF21F85B5 for <tictoc@ietf.org>; Sun,  7 Aug 2011 00:59:29 -0700 (PDT)
Received: by gxk19 with SMTP id 19so428820gxk.31 for <tictoc@ietf.org>; Sun, 07 Aug 2011 00:59:51 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; bh=2GjYdxXQYnelEuYHBOiryheU739Wt/lqGmSPhGJ69uE=; b=X1gtywLa7I3sbrmQm/2R9wKyme2my6xPz+VkZeJ3p2AN1Jt4rNco/yFB5FBJOSLBuV XfLxaqoZ9qRTLNRCP19i50KvT2Qo+ug5llK1wL3/aprHTEzHFKGIAGG0zpwSpkyJZyyt wCgou+eNrkzxvblTIXN2+6HjErR47KWow7W9I=
MIME-Version: 1.0
Received: by 10.236.176.201 with SMTP id b49mr3774932yhm.70.1312703991597; Sun, 07 Aug 2011 00:59:51 -0700 (PDT)
Received: by 10.147.114.4 with HTTP; Sun, 7 Aug 2011 00:59:51 -0700 (PDT)
Date: Sun, 7 Aug 2011 10:59:51 +0300
Message-ID: <CALMYT9Qt7HAWA6mAe7m+58=_jQ68a0bhnNq97KFU22_4yf4xKA@mail.gmail.com>
From: Ron Cohen <ronc.ntear@gmail.com>
To: tictoc@ietf.org
Content-Type: multipart/alternative; boundary=20cf305b0d161d4b8404a9e5b7df
Subject: [TICTOC] DSCP for PTP
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: Sun, 07 Aug 2011 07:59:30 -0000

--20cf305b0d161d4b8404a9e5b7df
Content-Type: text/plain; charset=ISO-8859-1

Hi,

Current standards do not recommend which DSCP values to set on PTP messages.
As a result vendors have chosen different default values, and some vendors
also differentiate between the DSCP set on PTP Event messages (Sync,
Delay_Req, etc.) and PTP General messages (Announce, Follow_Up, Delay_Resp).
I think TICTOC can help clarify the recommended DSCP usage, along the
guidelines of RFC4595, 'Configuration Guidelines for DiffServ Service
Classes'.

In my opinion classifying PTP event and general messages into separate PHBs
is problematic as discard of Follow_Up would render its associated Sync
message useless. Forwarding of Sync messages in a higher priority queue
compared to Follow_Up may lead to Sync message getting ahead of the previous
Follow_Up message which again causes the slave to discard the previous Sync
message. Hence the first order recommendation in my opinion should be to use
the same PHB (and DSCP marking) to all PTP messages.

Choosing one of the existing PHBs as the recommended one for PTP is somewhat
harder. EF is a reasonable choice in my opinion, as per RFC4595 'The intent
of Expedited Forwarding PHB [RFC3246] is to provide a building block for
low-loss, low-delay, and low-jitter services.' TICTOC could in principle
recommend defining a new PHB tailored for PTP and similar services, but I
guess this would be a longer process.

I would appreciate if others will share their insight on the recommended
usage and whether this issue should or should not be addressed by TICTOC.

Here is the relevant text from IEEE1588-2008 Annex D: "For PTP event
messages, the value of the differentiated service (DS) field in the Type of
Service (ToS)
field should be set to the highest traffic class selector codepoint
available." The PTP Telecom profile for frequency distribution, ITU-T
G.8265.1, doesn't specify or recommend DSCP settings.

Best,
Ron

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

<div dir=3D"ltr">Hi,<br><br>Current standards do not recommend which DSCP v=
alues to set on PTP messages. As a result vendors have chosen different def=
ault values, and some vendors also differentiate between the DSCP set on PT=
P Event messages (Sync, Delay_Req, etc.) and PTP General messages (Announce=
, Follow_Up, Delay_Resp). I think TICTOC can help clarify the recommended D=
SCP usage, along the guidelines of RFC4595, &#39;Configuration Guidelines f=
or DiffServ Service Classes&#39;.<br>
<br>In my opinion classifying PTP event and general messages into separate =
PHBs is problematic as discard of Follow_Up would render its associated Syn=
c message useless. Forwarding of Sync messages in a higher priority queue c=
ompared to Follow_Up may lead to Sync message getting ahead of the previous=
 Follow_Up message which again causes the slave to discard the previous Syn=
c message. Hence the first order recommendation in my opinion should be to =
use the same PHB (and DSCP marking) to all PTP messages. <br>
<br>Choosing one of the existing PHBs as the recommended one for PTP is som=
ewhat harder. EF is a reasonable choice in my opinion, as per RFC4595 &#39;=
The intent of Expedited Forwarding PHB [RFC3246] is to provide a   building=
 block for low-loss, low-delay, and low-jitter services.&#39; TICTOC could =
in principle recommend defining a new PHB tailored for PTP and similar serv=
ices, but I guess this would be a longer process.<br>
<br>I would appreciate if others will share their insight on the recommende=
d usage and whether this issue should or should not be addressed by TICTOC.=
 <br><br>Here is the relevant text from IEEE1588-2008 Annex D: &quot;For PT=
P event messages, the value of the differentiated service (DS) field in the=
 Type of Service (ToS)<br>
field should be set to the highest traffic class selector codepoint availab=
le.&quot; The PTP Telecom profile for frequency distribution, ITU-T G.8265.=
1, doesn&#39;t specify or recommend DSCP settings.<br><br>Best,<br>Ron<br>
</div>

--20cf305b0d161d4b8404a9e5b7df--

From zhang.junhui1@zte.com.cn  Mon Aug  8 02:21:27 2011
Return-Path: <zhang.junhui1@zte.com.cn>
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 692AD21F8663 for <tictoc@ietfa.amsl.com>; Mon,  8 Aug 2011 02:21:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -92.79
X-Spam-Level: 
X-Spam-Status: No, score=-92.79 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, CHARSET_FARAWAY_HEADER=3.2, HTML_MESSAGE=0.001, MIME_8BIT_HEADER=0.3, MIME_BASE64_TEXT=1.753, MIME_CHARSET_FARAWAY=2.45, RCVD_DOUBLE_IP_LOOSE=0.76, SARE_SUB_ENC_GB2312=1.345, 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 IYhlqZnnGcsj for <tictoc@ietfa.amsl.com>; Mon,  8 Aug 2011 02:21:26 -0700 (PDT)
Received: from mx5.zte.com.cn (mx6.zte.com.cn [95.130.199.165]) by ietfa.amsl.com (Postfix) with ESMTP id 06CC521F8658 for <tictoc@ietf.org>; Mon,  8 Aug 2011 02:21:24 -0700 (PDT)
Received: from [10.30.17.100] by mx5.zte.com.cn with surfront esmtp id 131321930506506; Mon, 8 Aug 2011 17:11:16 +0800 (CST)
Received: from [10.30.3.21] by [192.168.168.16] with StormMail ESMTP id 60415.1930506506; Mon, 8 Aug 2011 17:21:33 +0800 (CST)
Received: (from root@localhost) by mse02.zte.com.cn id p789LYFU039176 for <tictoc@ietf.org>; Mon, 8 Aug 2011 17:21:34 +0800 (GMT-8) (envelope-from zhang.junhui1@zte.com.cn)
Received: from notes_smtp.zte.com.cn ([10.30.1.239]) by mse02.zte.com.cn with ESMTP id p788urQa096200; Mon, 8 Aug 2011 16:56:54 +0800 (GMT-8) (envelope-from zhang.junhui1@zte.com.cn)
Message-Id: <201108080921.p789LYFU039176@mse02.zte.com.cn>
In-Reply-To: <CALMYT9Qt7HAWA6mAe7m+58=_jQ68a0bhnNq97KFU22_4yf4xKA@mail.gmail.com>
To: Ron Cohen <ronc.ntear@gmail.com>
MIME-Version: 1.0
X-KeepSent: D667CA3B:FB8B0139-482578E6:00291A72; type=4; name=$KeepSent
X-Mailer: Lotus Notes Release 6.5.6 March 06, 2007
From: zhang.junhui1@zte.com.cn
Date: Mon, 8 Aug 2011 16:56:47 +0800
X-MIMETrack: Serialize by Router on notes_smtp/zte_ltd(Release 8.5.1FP4|July 25, 2010) at 2011-08-08 16:56:57, Serialize complete at 2011-08-08 16:56:57
Content-Type: multipart/alternative; boundary="=_alternative 003125E5482578E6_="
X-MAIL: mse02.zte.com.cn p789LYFU039176
X-MSS: AUDITRELEASE@mse02.zte.com.cn
Cc: tictoc@ietf.org, tictoc-bounces@ietf.org
Subject: [TICTOC] =?gb2312?b?tPC4tDogIERTQ1AgZm9yIFBUUA==?=
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, 08 Aug 2011 09:21:27 -0000

This is a multipart message in MIME format.
--=_alternative 003125E5482578E6_=
Content-Type: text/plain; charset="GB2312"
Content-Transfer-Encoding: base64

SGmjrFJvbg0KIA0KICBJIGFncmVlIHRoYXQgY2xhc3NpZnlpbmcgUFRQIGV2ZW50IGFuZCBnZW5l
cmFsIG1lc3NhZ2VzIGludG8gc2VwYXJhdGUgDQpQSEJzIGlzICBwcm9ibGVtYXRpYywNCiAgYW5k
IGl0IGlzIHNob3VsZCBiZSB0byB1c2UgdGhlIHNhbWUgUEhCIHRvIGFsbCBQVFAgbWVzc2FnZXMu
DQogDQogIEluIGFkZGl0aW9uLCBJIHRoaW5rIHRoYXQgaXQgc2hvdWxkIHRha2UgaW50byBjb25z
aWRlcmF0aW9uIHRoZSANCmVuY2Fwc3VsYXRpb24gb2YgUFRQIG1lc3NhZ2WjrA0KICBiZWNhdXNl
IFBUUCBQSEIgaXMgcmVsYXRlZCB3aXRoIFBUUCBtZXNzYWdlIGZvcm1hdHMoZS5nLiB2bGFuIFBS
SSwgaXAgDQpUb3MsIG1wbHMgRVhQKS4NCg0KDQpCZXN0IFJlZ2FyZHMNCkp1bmh1aQ0KIA0KKioq
KioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioNCiAgICBKdW5o
dWkgWmhhbmcgDQogICAgQmVhcmVyIE5ldHdvcmsgUHJvZHVjdCBQcmUtcmVzZWFyY2ggRGVwdC4N
CiAgICBaVEUgQ29ycG9yYXRpb24NCiAgICBOby41MCBSdWFuamlhbiBBdmVudWUsWXVodWF0YWkg
RGlzdHJpY3QsDQogICAgTmFuamluZywgUC5SLkNoaW5hLCAyMTAwMTIgDQogICAgVGVsZXBob25l
ICAgICs4Ni0yNS04ODAxNDIyNw0KICAgIE1vYmlsZSBQaG9uZSArODYtMTM5MTM4NDUyODkNCioq
KioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqDQoNCg0KDQpS
b24gQ29oZW4gPHJvbmMubnRlYXJAZ21haWwuY29tPiANCreivP7IyzogIHRpY3RvYy1ib3VuY2Vz
QGlldGYub3JnDQoyMDExLTA4LTA3IDE1OjU5DQoNCsrVvP7Iyw0KdGljdG9jQGlldGYub3JnDQqz
rcvNDQoNCtb3zOINCltUSUNUT0NdIERTQ1AgZm9yIFBUUA0KDQoNCg0KDQoNCg0KSGksDQoNCkN1
cnJlbnQgc3RhbmRhcmRzIGRvIG5vdCByZWNvbW1lbmQgd2hpY2ggRFNDUCB2YWx1ZXMgdG8gc2V0
IG9uIFBUUCANCm1lc3NhZ2VzLiBBcyBhIHJlc3VsdCB2ZW5kb3JzIGhhdmUgY2hvc2VuIGRpZmZl
cmVudCBkZWZhdWx0IHZhbHVlcywgYW5kIA0Kc29tZSB2ZW5kb3JzIGFsc28gZGlmZmVyZW50aWF0
ZSBiZXR3ZWVuIHRoZSBEU0NQIHNldCBvbiBQVFAgRXZlbnQgbWVzc2FnZXMgDQooU3luYywgRGVs
YXlfUmVxLCBldGMuKSBhbmQgUFRQIEdlbmVyYWwgbWVzc2FnZXMgKEFubm91bmNlLCBGb2xsb3df
VXAsIA0KRGVsYXlfUmVzcCkuIEkgdGhpbmsgVElDVE9DIGNhbiBoZWxwIGNsYXJpZnkgdGhlIHJl
Y29tbWVuZGVkIERTQ1AgdXNhZ2UsIA0KYWxvbmcgdGhlIGd1aWRlbGluZXMgb2YgUkZDNDU5NSwg
J0NvbmZpZ3VyYXRpb24gR3VpZGVsaW5lcyBmb3IgRGlmZlNlcnYgDQpTZXJ2aWNlIENsYXNzZXMn
Lg0KDQpJbiBteSBvcGluaW9uIGNsYXNzaWZ5aW5nIFBUUCBldmVudCBhbmQgZ2VuZXJhbCBtZXNz
YWdlcyBpbnRvIHNlcGFyYXRlIA0KUEhCcyBpcyBwcm9ibGVtYXRpYyBhcyBkaXNjYXJkIG9mIEZv
bGxvd19VcCB3b3VsZCByZW5kZXIgaXRzIGFzc29jaWF0ZWQgDQpTeW5jIG1lc3NhZ2UgdXNlbGVz
cy4gRm9yd2FyZGluZyBvZiBTeW5jIG1lc3NhZ2VzIGluIGEgaGlnaGVyIHByaW9yaXR5IA0KcXVl
dWUgY29tcGFyZWQgdG8gRm9sbG93X1VwIG1heSBsZWFkIHRvIFN5bmMgbWVzc2FnZSBnZXR0aW5n
IGFoZWFkIG9mIHRoZSANCnByZXZpb3VzIEZvbGxvd19VcCBtZXNzYWdlIHdoaWNoIGFnYWluIGNh
dXNlcyB0aGUgc2xhdmUgdG8gZGlzY2FyZCB0aGUgDQpwcmV2aW91cyBTeW5jIG1lc3NhZ2UuIEhl
bmNlIHRoZSBmaXJzdCBvcmRlciByZWNvbW1lbmRhdGlvbiBpbiBteSBvcGluaW9uIA0Kc2hvdWxk
IGJlIHRvIHVzZSB0aGUgc2FtZSBQSEIgKGFuZCBEU0NQIG1hcmtpbmcpIHRvIGFsbCBQVFAgbWVz
c2FnZXMuIA0KDQpDaG9vc2luZyBvbmUgb2YgdGhlIGV4aXN0aW5nIFBIQnMgYXMgdGhlIHJlY29t
bWVuZGVkIG9uZSBmb3IgUFRQIGlzIA0Kc29tZXdoYXQgaGFyZGVyLiBFRiBpcyBhIHJlYXNvbmFi
bGUgY2hvaWNlIGluIG15IG9waW5pb24sIGFzIHBlciBSRkM0NTk1IA0KJ1RoZSBpbnRlbnQgb2Yg
RXhwZWRpdGVkIEZvcndhcmRpbmcgUEhCIFtSRkMzMjQ2XSBpcyB0byBwcm92aWRlIGEgYnVpbGRp
bmcgDQpibG9jayBmb3IgbG93LWxvc3MsIGxvdy1kZWxheSwgYW5kIGxvdy1qaXR0ZXIgc2Vydmlj
ZXMuJyBUSUNUT0MgY291bGQgaW4gDQpwcmluY2lwbGUgcmVjb21tZW5kIGRlZmluaW5nIGEgbmV3
IFBIQiB0YWlsb3JlZCBmb3IgUFRQIGFuZCBzaW1pbGFyIA0Kc2VydmljZXMsIGJ1dCBJIGd1ZXNz
IHRoaXMgd291bGQgYmUgYSBsb25nZXIgcHJvY2Vzcy4NCg0KSSB3b3VsZCBhcHByZWNpYXRlIGlm
IG90aGVycyB3aWxsIHNoYXJlIHRoZWlyIGluc2lnaHQgb24gdGhlIHJlY29tbWVuZGVkIA0KdXNh
Z2UgYW5kIHdoZXRoZXIgdGhpcyBpc3N1ZSBzaG91bGQgb3Igc2hvdWxkIG5vdCBiZSBhZGRyZXNz
ZWQgYnkgVElDVE9DLiANCg0KSGVyZSBpcyB0aGUgcmVsZXZhbnQgdGV4dCBmcm9tIElFRUUxNTg4
LTIwMDggQW5uZXggRDogIkZvciBQVFAgZXZlbnQgDQptZXNzYWdlcywgdGhlIHZhbHVlIG9mIHRo
ZSBkaWZmZXJlbnRpYXRlZCBzZXJ2aWNlIChEUykgZmllbGQgaW4gdGhlIFR5cGUgDQpvZiBTZXJ2
aWNlIChUb1MpDQpmaWVsZCBzaG91bGQgYmUgc2V0IHRvIHRoZSBoaWdoZXN0IHRyYWZmaWMgY2xh
c3Mgc2VsZWN0b3IgY29kZXBvaW50IA0KYXZhaWxhYmxlLiIgVGhlIFBUUCBUZWxlY29tIHByb2Zp
bGUgZm9yIGZyZXF1ZW5jeSBkaXN0cmlidXRpb24sIElUVS1UIA0KRy44MjY1LjEsIGRvZXNuJ3Qg
c3BlY2lmeSBvciByZWNvbW1lbmQgRFNDUCBzZXR0aW5ncy4NCg0KQmVzdCwNClJvbl9fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fDQpUSUNUT0MgbWFpbGluZyBs
aXN0DQpUSUNUT0NAaWV0Zi5vcmcNCmh0dHBzOi8vd3d3LmlldGYub3JnL21haWxtYW4vbGlzdGlu
Zm8vdGljdG9jDQoNCg0KDQoNCi0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tDQpaVEUgSW5mb3JtYXRpb24gU2VjdXJpdHkgTm90aWNlOiBUaGUg
aW5mb3JtYXRpb24gY29udGFpbmVkIGluIHRoaXMgbWFpbCBpcyBzb2xlbHkgcHJvcGVydHkgb2Yg
dGhlIHNlbmRlcidzIG9yZ2FuaXphdGlvbi4gVGhpcyBtYWlsIGNvbW11bmljYXRpb24gaXMgY29u
ZmlkZW50aWFsLiBSZWNpcGllbnRzIG5hbWVkIGFib3ZlIGFyZSBvYmxpZ2F0ZWQgdG8gbWFpbnRh
aW4gc2VjcmVjeSBhbmQgYXJlIG5vdCBwZXJtaXR0ZWQgdG8gZGlzY2xvc2UgdGhlIGNvbnRlbnRz
IG9mIHRoaXMgY29tbXVuaWNhdGlvbiB0byBvdGhlcnMuDQpUaGlzIGVtYWlsIGFuZCBhbnkgZmls
ZXMgdHJhbnNtaXR0ZWQgd2l0aCBpdCBhcmUgY29uZmlkZW50aWFsIGFuZCBpbnRlbmRlZCBzb2xl
bHkgZm9yIHRoZSB1c2Ugb2YgdGhlIGluZGl2aWR1YWwgb3IgZW50aXR5IHRvIHdob20gdGhleSBh
cmUgYWRkcmVzc2VkLiBJZiB5b3UgaGF2ZSByZWNlaXZlZCB0aGlzIGVtYWlsIGluIGVycm9yIHBs
ZWFzZSBub3RpZnkgdGhlIG9yaWdpbmF0b3Igb2YgdGhlIG1lc3NhZ2UuIEFueSB2aWV3cyBleHBy
ZXNzZWQgaW4gdGhpcyBtZXNzYWdlIGFyZSB0aG9zZSBvZiB0aGUgaW5kaXZpZHVhbCBzZW5kZXIu
DQpUaGlzIG1lc3NhZ2UgaGFzIGJlZW4gc2Nhbm5lZCBmb3IgdmlydXNlcyBhbmQgU3BhbSBieSBa
VEUgQW50aS1TcGFtIHN5c3RlbS4NCg==
--=_alternative 003125E5482578E6_=
Content-Type: text/html; charset="GB2312"
Content-Transfer-Encoding: base64

DQo8YnI+PGZvbnQgc2l6ZT0yIGZhY2U9InNhbnMtc2VyaWYiPkhpo6xSb248L2ZvbnQ+DQo8YnI+
PGZvbnQgc2l6ZT0yIGZhY2U9InNhbnMtc2VyaWYiPiZuYnNwOyAmbmJzcDs8L2ZvbnQ+DQo8YnI+
PGZvbnQgc2l6ZT0zPiZuYnNwOyBJIGFncmVlIHRoYXQgY2xhc3NpZnlpbmcgUFRQIGV2ZW50IGFu
ZCBnZW5lcmFsDQptZXNzYWdlcyBpbnRvIHNlcGFyYXRlIFBIQnMgaXMgJm5ic3A7cHJvYmxlbWF0
aWMsPC9mb250Pg0KPGJyPjxmb250IHNpemU9Mz4mbmJzcDsgYW5kIGl0IGlzIHNob3VsZCBiZSB0
byB1c2UgdGhlIHNhbWUgUEhCIHRvIGFsbA0KUFRQIG1lc3NhZ2VzLjwvZm9udD4NCjxicj48Zm9u
dCBzaXplPTM+Jm5ic3A7PC9mb250Pg0KPGJyPjxmb250IHNpemU9Mz4mbmJzcDsgSW4gYWRkaXRp
b24sIEkgdGhpbmsgdGhhdCBpdCBzaG91bGQgdGFrZSBpbnRvIGNvbnNpZGVyYXRpb24NCnRoZSBl
bmNhcHN1bGF0aW9uIG9mIFBUUCBtZXNzYWdlo6w8L2ZvbnQ+DQo8YnI+PGZvbnQgc2l6ZT0zPiZu
YnNwOyBiZWNhdXNlIFBUUCBQSEIgaXMgcmVsYXRlZCB3aXRoIFBUUCBtZXNzYWdlIGZvcm1hdHMo
ZS5nLg0KdmxhbiBQUkksIGlwIFRvcywgbXBscyBFWFApLjwvZm9udD4NCjxicj4NCjxicj4NCjxi
cj48Zm9udCBzaXplPTM+QmVzdCBSZWdhcmRzPC9mb250Pg0KPGJyPjxmb250IHNpemU9Mz5KdW5o
dWk8L2ZvbnQ+DQo8YnI+PGZvbnQgc2l6ZT0zPiZuYnNwOzwvZm9udD48Zm9udCBzaXplPTIgZmFj
ZT0ic2Fucy1zZXJpZiI+PGJyPg0KKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioq
KioqKioqKioqKioqKio8YnI+DQogJm5ic3A7ICZuYnNwO0p1bmh1aSBaaGFuZyAmbmJzcDs8YnI+
DQogJm5ic3A7ICZuYnNwO0JlYXJlciBOZXR3b3JrIFByb2R1Y3QgUHJlLXJlc2VhcmNoIERlcHQu
PGJyPg0KICZuYnNwOyAmbmJzcDtaVEUgQ29ycG9yYXRpb248YnI+DQogJm5ic3A7ICZuYnNwO05v
LjUwIFJ1YW5qaWFuIEF2ZW51ZSxZdWh1YXRhaSBEaXN0cmljdCw8YnI+DQogJm5ic3A7ICZuYnNw
O05hbmppbmcsIFAuUi5DaGluYSwgMjEwMDEyIDxicj4NCiAmbmJzcDsgJm5ic3A7VGVsZXBob25l
ICZuYnNwOyAmbmJzcDsrODYtMjUtODgwMTQyMjc8YnI+DQogJm5ic3A7ICZuYnNwO01vYmlsZSBQ
aG9uZSArODYtMTM5MTM4NDUyODk8YnI+DQoqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioq
KioqKioqKioqKioqKioqKioqKjwvZm9udD4NCjxicj4NCjxicj4NCjxicj4NCjx0YWJsZSB3aWR0
aD0xMDAlPg0KPHRyIHZhbGlnbj10b3A+DQo8dGQgd2lkdGg9MzUlPjxmb250IHNpemU9MSBmYWNl
PSJzYW5zLXNlcmlmIj48Yj5Sb24gQ29oZW4gJmx0O3JvbmMubnRlYXJAZ21haWwuY29tJmd0Ozwv
Yj4NCjwvZm9udD4NCjxicj48Zm9udCBzaXplPTEgZmFjZT0ic2Fucy1zZXJpZiI+t6K8/sjLOiAm
bmJzcDt0aWN0b2MtYm91bmNlc0BpZXRmLm9yZzwvZm9udD4NCjxwPjxmb250IHNpemU9MSBmYWNl
PSJzYW5zLXNlcmlmIj4yMDExLTA4LTA3IDE1OjU5PC9mb250Pg0KPHRkIHdpZHRoPTY0JT4NCjx0
YWJsZSB3aWR0aD0xMDAlPg0KPHRyIHZhbGlnbj10b3A+DQo8dGQ+DQo8ZGl2IGFsaWduPXJpZ2h0
Pjxmb250IHNpemU9MSBmYWNlPSJzYW5zLXNlcmlmIj7K1bz+yMs8L2ZvbnQ+PC9kaXY+DQo8dGQ+
PGZvbnQgc2l6ZT0xIGZhY2U9InNhbnMtc2VyaWYiPnRpY3RvY0BpZXRmLm9yZzwvZm9udD4NCjx0
ciB2YWxpZ249dG9wPg0KPHRkPg0KPGRpdiBhbGlnbj1yaWdodD48Zm9udCBzaXplPTEgZmFjZT0i
c2Fucy1zZXJpZiI+s63LzTwvZm9udD48L2Rpdj4NCjx0ZD4NCjx0ciB2YWxpZ249dG9wPg0KPHRk
Pg0KPGRpdiBhbGlnbj1yaWdodD48Zm9udCBzaXplPTEgZmFjZT0ic2Fucy1zZXJpZiI+1vfM4jwv
Zm9udD48L2Rpdj4NCjx0ZD48Zm9udCBzaXplPTEgZmFjZT0ic2Fucy1zZXJpZiI+W1RJQ1RPQ10g
RFNDUCBmb3IgUFRQPC9mb250PjwvdGFibGU+DQo8YnI+DQo8dGFibGU+DQo8dHIgdmFsaWduPXRv
cD4NCjx0ZD4NCjx0ZD48L3RhYmxlPg0KPGJyPjwvdGFibGU+DQo8YnI+DQo8YnI+DQo8YnI+PGZv
bnQgc2l6ZT0zPkhpLDxicj4NCjxicj4NCkN1cnJlbnQgc3RhbmRhcmRzIGRvIG5vdCByZWNvbW1l
bmQgd2hpY2ggRFNDUCB2YWx1ZXMgdG8gc2V0IG9uIFBUUCBtZXNzYWdlcy4NCkFzIGEgcmVzdWx0
IHZlbmRvcnMgaGF2ZSBjaG9zZW4gZGlmZmVyZW50IGRlZmF1bHQgdmFsdWVzLCBhbmQgc29tZSB2
ZW5kb3JzDQphbHNvIGRpZmZlcmVudGlhdGUgYmV0d2VlbiB0aGUgRFNDUCBzZXQgb24gUFRQIEV2
ZW50IG1lc3NhZ2VzIChTeW5jLCBEZWxheV9SZXEsDQpldGMuKSBhbmQgUFRQIEdlbmVyYWwgbWVz
c2FnZXMgKEFubm91bmNlLCBGb2xsb3dfVXAsIERlbGF5X1Jlc3ApLiBJIHRoaW5rDQpUSUNUT0Mg
Y2FuIGhlbHAgY2xhcmlmeSB0aGUgcmVjb21tZW5kZWQgRFNDUCB1c2FnZSwgYWxvbmcgdGhlIGd1
aWRlbGluZXMNCm9mIFJGQzQ1OTUsICdDb25maWd1cmF0aW9uIEd1aWRlbGluZXMgZm9yIERpZmZT
ZXJ2IFNlcnZpY2UgQ2xhc3NlcycuPGJyPg0KPGJyPg0KSW4gbXkgb3BpbmlvbiBjbGFzc2lmeWlu
ZyBQVFAgZXZlbnQgYW5kIGdlbmVyYWwgbWVzc2FnZXMgaW50byBzZXBhcmF0ZQ0KUEhCcyBpcyBw
cm9ibGVtYXRpYyBhcyBkaXNjYXJkIG9mIEZvbGxvd19VcCB3b3VsZCByZW5kZXIgaXRzIGFzc29j
aWF0ZWQNClN5bmMgbWVzc2FnZSB1c2VsZXNzLiBGb3J3YXJkaW5nIG9mIFN5bmMgbWVzc2FnZXMg
aW4gYSBoaWdoZXIgcHJpb3JpdHkNCnF1ZXVlIGNvbXBhcmVkIHRvIEZvbGxvd19VcCBtYXkgbGVh
ZCB0byBTeW5jIG1lc3NhZ2UgZ2V0dGluZyBhaGVhZCBvZiB0aGUNCnByZXZpb3VzIEZvbGxvd19V
cCBtZXNzYWdlIHdoaWNoIGFnYWluIGNhdXNlcyB0aGUgc2xhdmUgdG8gZGlzY2FyZCB0aGUNCnBy
ZXZpb3VzIFN5bmMgbWVzc2FnZS4gSGVuY2UgdGhlIGZpcnN0IG9yZGVyIHJlY29tbWVuZGF0aW9u
IGluIG15IG9waW5pb24NCnNob3VsZCBiZSB0byB1c2UgdGhlIHNhbWUgUEhCIChhbmQgRFNDUCBt
YXJraW5nKSB0byBhbGwgUFRQIG1lc3NhZ2VzLiA8YnI+DQo8YnI+DQpDaG9vc2luZyBvbmUgb2Yg
dGhlIGV4aXN0aW5nIFBIQnMgYXMgdGhlIHJlY29tbWVuZGVkIG9uZSBmb3IgUFRQIGlzIHNvbWV3
aGF0DQpoYXJkZXIuIEVGIGlzIGEgcmVhc29uYWJsZSBjaG9pY2UgaW4gbXkgb3BpbmlvbiwgYXMg
cGVyIFJGQzQ1OTUgJ1RoZSBpbnRlbnQNCm9mIEV4cGVkaXRlZCBGb3J3YXJkaW5nIFBIQiBbUkZD
MzI0Nl0gaXMgdG8gcHJvdmlkZSBhIGJ1aWxkaW5nIGJsb2NrIGZvcg0KbG93LWxvc3MsIGxvdy1k
ZWxheSwgYW5kIGxvdy1qaXR0ZXIgc2VydmljZXMuJyBUSUNUT0MgY291bGQgaW4gcHJpbmNpcGxl
DQpyZWNvbW1lbmQgZGVmaW5pbmcgYSBuZXcgUEhCIHRhaWxvcmVkIGZvciBQVFAgYW5kIHNpbWls
YXIgc2VydmljZXMsIGJ1dA0KSSBndWVzcyB0aGlzIHdvdWxkIGJlIGEgbG9uZ2VyIHByb2Nlc3Mu
PGJyPg0KPGJyPg0KSSB3b3VsZCBhcHByZWNpYXRlIGlmIG90aGVycyB3aWxsIHNoYXJlIHRoZWly
IGluc2lnaHQgb24gdGhlIHJlY29tbWVuZGVkDQp1c2FnZSBhbmQgd2hldGhlciB0aGlzIGlzc3Vl
IHNob3VsZCBvciBzaG91bGQgbm90IGJlIGFkZHJlc3NlZCBieSBUSUNUT0MuDQo8YnI+DQo8YnI+
DQpIZXJlIGlzIHRoZSByZWxldmFudCB0ZXh0IGZyb20gSUVFRTE1ODgtMjAwOCBBbm5leCBEOiAm
cXVvdDtGb3IgUFRQIGV2ZW50DQptZXNzYWdlcywgdGhlIHZhbHVlIG9mIHRoZSBkaWZmZXJlbnRp
YXRlZCBzZXJ2aWNlIChEUykgZmllbGQgaW4gdGhlIFR5cGUNCm9mIFNlcnZpY2UgKFRvUyk8YnI+
DQpmaWVsZCBzaG91bGQgYmUgc2V0IHRvIHRoZSBoaWdoZXN0IHRyYWZmaWMgY2xhc3Mgc2VsZWN0
b3IgY29kZXBvaW50IGF2YWlsYWJsZS4mcXVvdDsNClRoZSBQVFAgVGVsZWNvbSBwcm9maWxlIGZv
ciBmcmVxdWVuY3kgZGlzdHJpYnV0aW9uLCBJVFUtVCBHLjgyNjUuMSwgZG9lc24ndA0Kc3BlY2lm
eSBvciByZWNvbW1lbmQgRFNDUCBzZXR0aW5ncy48YnI+DQo8YnI+DQpCZXN0LDxicj4NClJvbjwv
Zm9udD48dHQ+PGZvbnQgc2l6ZT0yPl9fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fPGJyPg0KVElDVE9DIG1haWxpbmcgbGlzdDxicj4NClRJQ1RPQ0BpZXRmLm9y
Zzxicj4NCmh0dHBzOi8vd3d3LmlldGYub3JnL21haWxtYW4vbGlzdGluZm8vdGljdG9jPGJyPg0K
PC9mb250PjwvdHQ+DQo8YnI+DQo8YnI+PHByZT4NCi0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tDQpaVEUmbmJzcDtJbmZvcm1hdGlvbiZuYnNw
O1NlY3VyaXR5Jm5ic3A7Tm90aWNlOiZuYnNwO1RoZSZuYnNwO2luZm9ybWF0aW9uJm5ic3A7Y29u
dGFpbmVkJm5ic3A7aW4mbmJzcDt0aGlzJm5ic3A7bWFpbCZuYnNwO2lzJm5ic3A7c29sZWx5Jm5i
c3A7cHJvcGVydHkmbmJzcDtvZiZuYnNwO3RoZSZuYnNwO3NlbmRlcidzJm5ic3A7b3JnYW5pemF0
aW9uLiZuYnNwO1RoaXMmbmJzcDttYWlsJm5ic3A7Y29tbXVuaWNhdGlvbiZuYnNwO2lzJm5ic3A7
Y29uZmlkZW50aWFsLiZuYnNwO1JlY2lwaWVudHMmbmJzcDtuYW1lZCZuYnNwO2Fib3ZlJm5ic3A7
YXJlJm5ic3A7b2JsaWdhdGVkJm5ic3A7dG8mbmJzcDttYWludGFpbiZuYnNwO3NlY3JlY3kmbmJz
cDthbmQmbmJzcDthcmUmbmJzcDtub3QmbmJzcDtwZXJtaXR0ZWQmbmJzcDt0byZuYnNwO2Rpc2Ns
b3NlJm5ic3A7dGhlJm5ic3A7Y29udGVudHMmbmJzcDtvZiZuYnNwO3RoaXMmbmJzcDtjb21tdW5p
Y2F0aW9uJm5ic3A7dG8mbmJzcDtvdGhlcnMuDQpUaGlzJm5ic3A7ZW1haWwmbmJzcDthbmQmbmJz
cDthbnkmbmJzcDtmaWxlcyZuYnNwO3RyYW5zbWl0dGVkJm5ic3A7d2l0aCZuYnNwO2l0Jm5ic3A7
YXJlJm5ic3A7Y29uZmlkZW50aWFsJm5ic3A7YW5kJm5ic3A7aW50ZW5kZWQmbmJzcDtzb2xlbHkm
bmJzcDtmb3ImbmJzcDt0aGUmbmJzcDt1c2UmbmJzcDtvZiZuYnNwO3RoZSZuYnNwO2luZGl2aWR1
YWwmbmJzcDtvciZuYnNwO2VudGl0eSZuYnNwO3RvJm5ic3A7d2hvbSZuYnNwO3RoZXkmbmJzcDth
cmUmbmJzcDthZGRyZXNzZWQuJm5ic3A7SWYmbmJzcDt5b3UmbmJzcDtoYXZlJm5ic3A7cmVjZWl2
ZWQmbmJzcDt0aGlzJm5ic3A7ZW1haWwmbmJzcDtpbiZuYnNwO2Vycm9yJm5ic3A7cGxlYXNlJm5i
c3A7bm90aWZ5Jm5ic3A7dGhlJm5ic3A7b3JpZ2luYXRvciZuYnNwO29mJm5ic3A7dGhlJm5ic3A7
bWVzc2FnZS4mbmJzcDtBbnkmbmJzcDt2aWV3cyZuYnNwO2V4cHJlc3NlZCZuYnNwO2luJm5ic3A7
dGhpcyZuYnNwO21lc3NhZ2UmbmJzcDthcmUmbmJzcDt0aG9zZSZuYnNwO29mJm5ic3A7dGhlJm5i
c3A7aW5kaXZpZHVhbCZuYnNwO3NlbmRlci4NClRoaXMmbmJzcDttZXNzYWdlJm5ic3A7aGFzJm5i
c3A7YmVlbiZuYnNwO3NjYW5uZWQmbmJzcDtmb3ImbmJzcDt2aXJ1c2VzJm5ic3A7YW5kJm5ic3A7
U3BhbSZuYnNwO2J5Jm5ic3A7WlRFJm5ic3A7QW50aS1TcGFtJm5ic3A7c3lzdGVtLg0KPC9wcmU+
--=_alternative 003125E5482578E6_=--


From talmi@marvell.com  Mon Aug  8 06:10:34 2011
Return-Path: <talmi@marvell.com>
X-Original-To: tictoc@ietfa.amsl.com
Delivered-To: tictoc@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 441CB21F899F; Mon,  8 Aug 2011 06:10:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.311
X-Spam-Level: *
X-Spam-Status: No, score=1.311 tagged_above=-999 required=5 tests=[AWL=-5.139,  BAYES_00=-2.599, CHARSET_FARAWAY_HEADER=3.2, HTML_MESSAGE=0.001, MIME_8BIT_HEADER=0.3, MIME_BASE64_TEXT=1.753, MIME_CHARSET_FARAWAY=2.45, SARE_SUB_ENC_GB2312=1.345]
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 qim4JqHa9-51; Mon,  8 Aug 2011 06:10:33 -0700 (PDT)
Received: from galiil.marvell.com (galiil.marvell.com [199.203.130.254]) by ietfa.amsl.com (Postfix) with ESMTP id 56D8E21F86D8; Mon,  8 Aug 2011 06:10:32 -0700 (PDT)
From: Tal Mizrahi <talmi@marvell.com>
To: "zhang.junhui1@zte.com.cn" <zhang.junhui1@zte.com.cn>, Ron Cohen <ronc.ntear@gmail.com>
Date: Mon, 8 Aug 2011 16:10:50 +0300
Thread-Topic: =?gb2312?B?W1RJQ1RPQ10gtPC4tDogIERTQ1AgZm9yIFBUUA==?=
Thread-Index: AcxVrKCEQAk7j8GoS6CwtHktEIIg2wAH3FGg
Message-ID: <74470498B659FA4687F0B0018C19A89C014735063EB4@IL-MB01.marvell.com>
References: <CALMYT9Qt7HAWA6mAe7m+58=_jQ68a0bhnNq97KFU22_4yf4xKA@mail.gmail.com> <201108080921.p789LYFU039176@mse02.zte.com.cn>
In-Reply-To: <201108080921.p789LYFU039176@mse02.zte.com.cn>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: multipart/alternative; boundary="_000_74470498B659FA4687F0B0018C19A89C014735063EB4ILMB01marve_"
MIME-Version: 1.0
Cc: "tictoc@ietf.org" <tictoc@ietf.org>, "tictoc-bounces@ietf.org" <tictoc-bounces@ietf.org>
Subject: Re: [TICTOC] =?gb2312?b?tPC4tDogIERTQ1AgZm9yIFBUUA==?=
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, 08 Aug 2011 13:10:34 -0000

--_000_74470498B659FA4687F0B0018C19A89C014735063EB4ILMB01marve_
Content-Type: text/plain; charset="gb2312"
Content-Transfer-Encoding: base64

SGksDQoNCkFzIGEgcmVmZXJlbmNlOiA4MDIuMUFTIGRlZmluZXMgdGhhdCB0aGUgcHJpb3JpdHkg
b2YgUFRQIGZyYW1lcyBpbiB0aGlzIHByb2ZpbGUgaXMgNi4gVGhpcyBwcmlvcml0eSBpcyBub3Qg
Y29udmV5ZWQgaW4gdGhlIGZyYW1lLCBzaW5jZSB0aGVzZSBtZXNzYWdlcyBhcmUgdW50YWdnZWQu
DQoNClRhbC4NCg0KRnJvbTogdGljdG9jLWJvdW5jZXNAaWV0Zi5vcmcgW21haWx0bzp0aWN0b2Mt
Ym91bmNlc0BpZXRmLm9yZ10gT24gQmVoYWxmIE9mIHpoYW5nLmp1bmh1aTFAenRlLmNvbS5jbg0K
U2VudDogTW9uZGF5LCBBdWd1c3QgMDgsIDIwMTEgMTE6NTcgQU0NClRvOiBSb24gQ29oZW4NCkNj
OiB0aWN0b2NAaWV0Zi5vcmc7IHRpY3RvYy1ib3VuY2VzQGlldGYub3JnDQpTdWJqZWN0OiBbVElD
VE9DXSC08Li0OiBEU0NQIGZvciBQVFANCg0KDQpIaaOsUm9uDQoNCiAgSSBhZ3JlZSB0aGF0IGNs
YXNzaWZ5aW5nIFBUUCBldmVudCBhbmQgZ2VuZXJhbCBtZXNzYWdlcyBpbnRvIHNlcGFyYXRlIFBI
QnMgaXMgIHByb2JsZW1hdGljLA0KICBhbmQgaXQgaXMgc2hvdWxkIGJlIHRvIHVzZSB0aGUgc2Ft
ZSBQSEIgdG8gYWxsIFBUUCBtZXNzYWdlcy4NCg0KICBJbiBhZGRpdGlvbiwgSSB0aGluayB0aGF0
IGl0IHNob3VsZCB0YWtlIGludG8gY29uc2lkZXJhdGlvbiB0aGUgZW5jYXBzdWxhdGlvbiBvZiBQ
VFAgbWVzc2FnZaOsDQogIGJlY2F1c2UgUFRQIFBIQiBpcyByZWxhdGVkIHdpdGggUFRQIG1lc3Nh
Z2UgZm9ybWF0cyhlLmcuIHZsYW4gUFJJLCBpcCBUb3MsIG1wbHMgRVhQKS4NCg0KDQpCZXN0IFJl
Z2FyZHMNCkp1bmh1aQ0KDQoqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioq
KioqKioqKioqKg0KICAgSnVuaHVpIFpoYW5nDQogICBCZWFyZXIgTmV0d29yayBQcm9kdWN0IFBy
ZS1yZXNlYXJjaCBEZXB0Lg0KICAgWlRFIENvcnBvcmF0aW9uDQogICBOby41MCBSdWFuamlhbiBB
dmVudWUsWXVodWF0YWkgRGlzdHJpY3QsDQogICBOYW5qaW5nLCBQLlIuQ2hpbmEsIDIxMDAxMg0K
ICAgVGVsZXBob25lICAgICs4Ni0yNS04ODAxNDIyNw0KICAgTW9iaWxlIFBob25lICs4Ni0xMzkx
Mzg0NTI4OQ0KKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioq
KioNCg0KUm9uIENvaGVuIDxyb25jLm50ZWFyQGdtYWlsLmNvbTxtYWlsdG86cm9uYy5udGVhckBn
bWFpbC5jb20+Pg0Kt6K8/sjLOiAgdGljdG9jLWJvdW5jZXNAaWV0Zi5vcmc8bWFpbHRvOnRpY3Rv
Yy1ib3VuY2VzQGlldGYub3JnPg0KDQoyMDExLTA4LTA3IDE1OjU5DQoNCsrVvP7Iyw0KDQp0aWN0
b2NAaWV0Zi5vcmc8bWFpbHRvOnRpY3RvY0BpZXRmLm9yZz4NCg0Ks63LzQ0KDQrW98ziDQoNCltU
SUNUT0NdIERTQ1AgZm9yIFBUUA0KDQoNCg0KDQoNCg0KDQpIaSwNCg0KQ3VycmVudCBzdGFuZGFy
ZHMgZG8gbm90IHJlY29tbWVuZCB3aGljaCBEU0NQIHZhbHVlcyB0byBzZXQgb24gUFRQIG1lc3Nh
Z2VzLiBBcyBhIHJlc3VsdCB2ZW5kb3JzIGhhdmUgY2hvc2VuIGRpZmZlcmVudCBkZWZhdWx0IHZh
bHVlcywgYW5kIHNvbWUgdmVuZG9ycyBhbHNvIGRpZmZlcmVudGlhdGUgYmV0d2VlbiB0aGUgRFND
UCBzZXQgb24gUFRQIEV2ZW50IG1lc3NhZ2VzIChTeW5jLCBEZWxheV9SZXEsIGV0Yy4pIGFuZCBQ
VFAgR2VuZXJhbCBtZXNzYWdlcyAoQW5ub3VuY2UsIEZvbGxvd19VcCwgRGVsYXlfUmVzcCkuIEkg
dGhpbmsgVElDVE9DIGNhbiBoZWxwIGNsYXJpZnkgdGhlIHJlY29tbWVuZGVkIERTQ1AgdXNhZ2Us
IGFsb25nIHRoZSBndWlkZWxpbmVzIG9mIFJGQzQ1OTUsICdDb25maWd1cmF0aW9uIEd1aWRlbGlu
ZXMgZm9yIERpZmZTZXJ2IFNlcnZpY2UgQ2xhc3NlcycuDQoNCkluIG15IG9waW5pb24gY2xhc3Np
ZnlpbmcgUFRQIGV2ZW50IGFuZCBnZW5lcmFsIG1lc3NhZ2VzIGludG8gc2VwYXJhdGUgUEhCcyBp
cyBwcm9ibGVtYXRpYyBhcyBkaXNjYXJkIG9mIEZvbGxvd19VcCB3b3VsZCByZW5kZXIgaXRzIGFz
c29jaWF0ZWQgU3luYyBtZXNzYWdlIHVzZWxlc3MuIEZvcndhcmRpbmcgb2YgU3luYyBtZXNzYWdl
cyBpbiBhIGhpZ2hlciBwcmlvcml0eSBxdWV1ZSBjb21wYXJlZCB0byBGb2xsb3dfVXAgbWF5IGxl
YWQgdG8gU3luYyBtZXNzYWdlIGdldHRpbmcgYWhlYWQgb2YgdGhlIHByZXZpb3VzIEZvbGxvd19V
cCBtZXNzYWdlIHdoaWNoIGFnYWluIGNhdXNlcyB0aGUgc2xhdmUgdG8gZGlzY2FyZCB0aGUgcHJl
dmlvdXMgU3luYyBtZXNzYWdlLiBIZW5jZSB0aGUgZmlyc3Qgb3JkZXIgcmVjb21tZW5kYXRpb24g
aW4gbXkgb3BpbmlvbiBzaG91bGQgYmUgdG8gdXNlIHRoZSBzYW1lIFBIQiAoYW5kIERTQ1AgbWFy
a2luZykgdG8gYWxsIFBUUCBtZXNzYWdlcy4NCg0KQ2hvb3Npbmcgb25lIG9mIHRoZSBleGlzdGlu
ZyBQSEJzIGFzIHRoZSByZWNvbW1lbmRlZCBvbmUgZm9yIFBUUCBpcyBzb21ld2hhdCBoYXJkZXIu
IEVGIGlzIGEgcmVhc29uYWJsZSBjaG9pY2UgaW4gbXkgb3BpbmlvbiwgYXMgcGVyIFJGQzQ1OTUg
J1RoZSBpbnRlbnQgb2YgRXhwZWRpdGVkIEZvcndhcmRpbmcgUEhCIFtSRkMzMjQ2XSBpcyB0byBw
cm92aWRlIGEgYnVpbGRpbmcgYmxvY2sgZm9yIGxvdy1sb3NzLCBsb3ctZGVsYXksIGFuZCBsb3ct
aml0dGVyIHNlcnZpY2VzLicgVElDVE9DIGNvdWxkIGluIHByaW5jaXBsZSByZWNvbW1lbmQgZGVm
aW5pbmcgYSBuZXcgUEhCIHRhaWxvcmVkIGZvciBQVFAgYW5kIHNpbWlsYXIgc2VydmljZXMsIGJ1
dCBJIGd1ZXNzIHRoaXMgd291bGQgYmUgYSBsb25nZXIgcHJvY2Vzcy4NCg0KSSB3b3VsZCBhcHBy
ZWNpYXRlIGlmIG90aGVycyB3aWxsIHNoYXJlIHRoZWlyIGluc2lnaHQgb24gdGhlIHJlY29tbWVu
ZGVkIHVzYWdlIGFuZCB3aGV0aGVyIHRoaXMgaXNzdWUgc2hvdWxkIG9yIHNob3VsZCBub3QgYmUg
YWRkcmVzc2VkIGJ5IFRJQ1RPQy4NCg0KSGVyZSBpcyB0aGUgcmVsZXZhbnQgdGV4dCBmcm9tIElF
RUUxNTg4LTIwMDggQW5uZXggRDogIkZvciBQVFAgZXZlbnQgbWVzc2FnZXMsIHRoZSB2YWx1ZSBv
ZiB0aGUgZGlmZmVyZW50aWF0ZWQgc2VydmljZSAoRFMpIGZpZWxkIGluIHRoZSBUeXBlIG9mIFNl
cnZpY2UgKFRvUykNCmZpZWxkIHNob3VsZCBiZSBzZXQgdG8gdGhlIGhpZ2hlc3QgdHJhZmZpYyBj
bGFzcyBzZWxlY3RvciBjb2RlcG9pbnQgYXZhaWxhYmxlLiIgVGhlIFBUUCBUZWxlY29tIHByb2Zp
bGUgZm9yIGZyZXF1ZW5jeSBkaXN0cmlidXRpb24sIElUVS1UIEcuODI2NS4xLCBkb2Vzbid0IHNw
ZWNpZnkgb3IgcmVjb21tZW5kIERTQ1Agc2V0dGluZ3MuDQoNCkJlc3QsDQpSb25fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fXw0KVElDVE9DIG1haWxpbmcgbGlz
dA0KVElDVE9DQGlldGYub3JnPG1haWx0bzpUSUNUT0NAaWV0Zi5vcmc+DQpodHRwczovL3d3dy5p
ZXRmLm9yZy9tYWlsbWFuL2xpc3RpbmZvL3RpY3RvYw0KDQoNCg0KDQotLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLQ0KDQpaVEUgSW5mb3JtYXRp
b24gU2VjdXJpdHkgTm90aWNlOiBUaGUgaW5mb3JtYXRpb24gY29udGFpbmVkIGluIHRoaXMgbWFp
bCBpcyBzb2xlbHkgcHJvcGVydHkgb2YgdGhlIHNlbmRlcidzIG9yZ2FuaXphdGlvbi4gVGhpcyBt
YWlsIGNvbW11bmljYXRpb24gaXMgY29uZmlkZW50aWFsLiBSZWNpcGllbnRzIG5hbWVkIGFib3Zl
IGFyZSBvYmxpZ2F0ZWQgdG8gbWFpbnRhaW4gc2VjcmVjeSBhbmQgYXJlIG5vdCBwZXJtaXR0ZWQg
dG8gZGlzY2xvc2UgdGhlIGNvbnRlbnRzIG9mIHRoaXMgY29tbXVuaWNhdGlvbiB0byBvdGhlcnMu
DQoNClRoaXMgZW1haWwgYW5kIGFueSBmaWxlcyB0cmFuc21pdHRlZCB3aXRoIGl0IGFyZSBjb25m
aWRlbnRpYWwgYW5kIGludGVuZGVkIHNvbGVseSBmb3IgdGhlIHVzZSBvZiB0aGUgaW5kaXZpZHVh
bCBvciBlbnRpdHkgdG8gd2hvbSB0aGV5IGFyZSBhZGRyZXNzZWQuIElmIHlvdSBoYXZlIHJlY2Vp
dmVkIHRoaXMgZW1haWwgaW4gZXJyb3IgcGxlYXNlIG5vdGlmeSB0aGUgb3JpZ2luYXRvciBvZiB0
aGUgbWVzc2FnZS4gQW55IHZpZXdzIGV4cHJlc3NlZCBpbiB0aGlzIG1lc3NhZ2UgYXJlIHRob3Nl
IG9mIHRoZSBpbmRpdmlkdWFsIHNlbmRlci4NCg0KVGhpcyBtZXNzYWdlIGhhcyBiZWVuIHNjYW5u
ZWQgZm9yIHZpcnVzZXMgYW5kIFNwYW0gYnkgWlRFIEFudGktU3BhbSBzeXN0ZW0uDQo=

--_000_74470498B659FA4687F0B0018C19A89C014735063EB4ILMB01marve_
Content-Type: text/html; charset="gb2312"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40"><head><meta http-equiv=3DContent-Type content=
=3D"text/html; charset=3Dgb2312"><meta name=3DGenerator content=3D"Microsof=
t Word 14 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
	{font-family:SimSun;
	panose-1:2 1 6 0 3 1 1 1 1 1;}
@font-face
	{font-family:SimSun;
	panose-1:2 1 6 0 3 1 1 1 1 1;}
@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;}
@font-face
	{font-family:"\@SimSun";
	panose-1:2 1 6 0 3 1 1 1 1 1;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:SimSun;
	mso-fareast-language:ZH-CN;}
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:SimSun;
	mso-fareast-language:ZH-CN;}
pre
	{mso-style-priority:99;
	mso-style-link:"HTML Preformatted Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:SimSun;
	mso-fareast-language:ZH-CN;}
tt
	{mso-style-priority:99;
	font-family:SimSun;}
span.HTMLPreformattedChar
	{mso-style-name:"HTML Preformatted Char";
	mso-style-priority:99;
	mso-style-link:"HTML Preformatted";
	font-family:Consolas;
	mso-fareast-language:ZH-CN;}
span.EmailStyle21
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-family:"Calibri","sans-serif";}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.25in 1.0in 1.25in;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]--></head><body lang=3DEN-US link=3Dblue vli=
nk=3Dpurple><div class=3DWordSection1><p class=3DMsoNormal><span style=3D'f=
ont-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Hi,<o:p><=
/o:p></span></p><p class=3DMsoNormal><span style=3D'font-size:11.0pt;font-f=
amily:"Calibri","sans-serif";color:#1F497D'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span style=3D'font-size:11.0pt;font-family:"Calibri","sa=
ns-serif";color:#1F497D'>As a reference: 802.1AS defines that the priority =
of PTP frames in this profile is 6. This priority is not conveyed in the fr=
ame, since these messages are untagged.<o:p></o:p></span></p><p class=3DMso=
Normal><span style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";c=
olor:#1F497D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span style=
=3D'font-size:10.0pt;font-family:"Arial","sans-serif";color:#1F497D;mso-far=
east-language:EN-US'>Tal.<o:p></o:p></span></p><p class=3DMsoNormal><span s=
tyle=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>=
<o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><b><span style=3D'font-siz=
e:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span></b><span style=3D'=
font-size:10.0pt;font-family:"Tahoma","sans-serif"'> tictoc-bounces@ietf.or=
g [mailto:tictoc-bounces@ietf.org] <b>On Behalf Of </b>zhang.junhui1@zte.co=
m.cn<br><b>Sent:</b> Monday, August 08, 2011 11:57 AM<br><b>To:</b> Ron Coh=
en<br><b>Cc:</b> tictoc@ietf.org; tictoc-bounces@ietf.org<br><b>Subject:</b=
> [TICTOC] </span><span lang=3DZH-CN style=3D'font-size:10.0pt'>=B4=F0=B8=
=B4</span><span style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"=
'>: DSCP for PTP<o:p></o:p></span></p><p class=3DMsoNormal><o:p>&nbsp;</o:p=
></p><p class=3DMsoNormal style=3D'margin-bottom:12.0pt'><br><span style=3D=
'font-size:10.0pt;font-family:"Arial","sans-serif"'>Hi</span><span lang=3DZ=
H-CN style=3D'font-size:10.0pt'>=A3=AC</span><span style=3D'font-size:10.0p=
t;font-family:"Arial","sans-serif"'>Ron</span> <br><span style=3D'font-size=
:10.0pt;font-family:"Arial","sans-serif"'>&nbsp; &nbsp;</span> <br>&nbsp; I=
 agree that classifying PTP event and general messages into separate PHBs i=
s &nbsp;problematic, <br>&nbsp; and it is should be to use the same PHB to =
all PTP messages. <br>&nbsp; <br>&nbsp; In addition, I think that it should=
 take into consideration the encapsulation of PTP message<span lang=3DZH-CN=
>=A3=AC</span> <br>&nbsp; because PTP PHB is related with PTP message forma=
ts(e.g. vlan PRI, ip Tos, mpls EXP). <br><br><br>Best Regards <br>Junhui <b=
r>&nbsp;<span style=3D'font-size:10.0pt;font-family:"Arial","sans-serif"'><=
br>**************************************************<br>&nbsp; &nbsp;Junhu=
i Zhang &nbsp;<br>&nbsp; &nbsp;Bearer Network Product Pre-research Dept.<br=
>&nbsp; &nbsp;ZTE Corporation<br>&nbsp; &nbsp;No.50 Ruanjian Avenue,Yuhuata=
i District,<br>&nbsp; &nbsp;Nanjing, P.R.China, 210012 <br>&nbsp; &nbsp;Tel=
ephone &nbsp; &nbsp;+86-25-88014227<br>&nbsp; &nbsp;Mobile Phone +86-139138=
45289<br>**************************************************</span> <br><br>=
<o:p></o:p></p><table class=3DMsoNormalTable border=3D0 cellpadding=3D0 wid=
th=3D"100%" style=3D'width:100.0%'><tr><td width=3D"35%" valign=3Dtop style=
=3D'width:35.0%;padding:.75pt .75pt .75pt .75pt'><p class=3DMsoNormal><b><s=
pan style=3D'font-size:7.5pt;font-family:"Arial","sans-serif"'>Ron Cohen &l=
t;<a href=3D"mailto:ronc.ntear@gmail.com">ronc.ntear@gmail.com</a>&gt;</spa=
n></b><span style=3D'font-size:7.5pt;font-family:"Arial","sans-serif"'> </s=
pan><br><span lang=3DZH-CN style=3D'font-size:7.5pt'>=B7=A2=BC=FE=C8=CB</sp=
an><span style=3D'font-size:7.5pt;font-family:"Arial","sans-serif"'>: &nbsp=
;<a href=3D"mailto:tictoc-bounces@ietf.org">tictoc-bounces@ietf.org</a></sp=
an> <o:p></o:p></p><p><span style=3D'font-size:7.5pt;font-family:"Arial","s=
ans-serif"'>2011-08-07 15:59</span> <o:p></o:p></p></td><td width=3D"64%" v=
align=3Dtop style=3D'width:64.0%;padding:.75pt .75pt .75pt .75pt'><table cl=
ass=3DMsoNormalTable border=3D0 cellpadding=3D0 width=3D"100%" style=3D'wid=
th:100.0%'><tr><td valign=3Dtop style=3D'padding:.75pt .75pt .75pt .75pt'><=
p class=3DMsoNormal align=3Dright style=3D'text-align:right'><span lang=3DZ=
H-CN style=3D'font-size:7.5pt'>=CA=D5=BC=FE=C8=CB</span><o:p></o:p></p></td=
><td valign=3Dtop style=3D'padding:.75pt .75pt .75pt .75pt'><p class=3DMsoN=
ormal><span style=3D'font-size:7.5pt;font-family:"Arial","sans-serif"'><a h=
ref=3D"mailto:tictoc@ietf.org">tictoc@ietf.org</a></span> <o:p></o:p></p></=
td></tr><tr><td valign=3Dtop style=3D'padding:.75pt .75pt .75pt .75pt'><p c=
lass=3DMsoNormal align=3Dright style=3D'text-align:right'><span lang=3DZH-C=
N style=3D'font-size:7.5pt'>=B3=AD=CB=CD</span><o:p></o:p></p></td><td vali=
gn=3Dtop style=3D'padding:.75pt .75pt .75pt .75pt'></td></tr><tr><td valign=
=3Dtop style=3D'padding:.75pt .75pt .75pt .75pt'><p class=3DMsoNormal align=
=3Dright style=3D'text-align:right'><span lang=3DZH-CN style=3D'font-size:7=
.5pt'>=D6=F7=CC=E2</span><o:p></o:p></p></td><td valign=3Dtop style=3D'padd=
ing:.75pt .75pt .75pt .75pt'><p class=3DMsoNormal><span style=3D'font-size:=
7.5pt;font-family:"Arial","sans-serif"'>[TICTOC] DSCP for PTP</span><o:p></=
o:p></p></td></tr></table><p class=3DMsoNormal><o:p>&nbsp;</o:p></p><table =
class=3DMsoNormalTable border=3D0 cellpadding=3D0><tr><td valign=3Dtop styl=
e=3D'padding:.75pt .75pt .75pt .75pt'></td><td valign=3Dtop style=3D'paddin=
g:.75pt .75pt .75pt .75pt'></td></tr></table></td></tr></table><p class=3DM=
soNormal style=3D'margin-bottom:12.0pt'><br><br><br>Hi,<br><br>Current stan=
dards do not recommend which DSCP values to set on PTP messages. As a resul=
t vendors have chosen different default values, and some vendors also diffe=
rentiate between the DSCP set on PTP Event messages (Sync, Delay_Req, etc.)=
 and PTP General messages (Announce, Follow_Up, Delay_Resp). I think TICTOC=
 can help clarify the recommended DSCP usage, along the guidelines of RFC45=
95, 'Configuration Guidelines for DiffServ Service Classes'.<br><br>In my o=
pinion classifying PTP event and general messages into separate PHBs is pro=
blematic as discard of Follow_Up would render its associated Sync message u=
seless. Forwarding of Sync messages in a higher priority queue compared to =
Follow_Up may lead to Sync message getting ahead of the previous Follow_Up =
message which again causes the slave to discard the previous Sync message. =
Hence the first order recommendation in my opinion should be to use the sam=
e PHB (and DSCP marking) to all PTP messages. <br><br>Choosing one of the e=
xisting PHBs as the recommended one for PTP is somewhat harder. EF is a rea=
sonable choice in my opinion, as per RFC4595 'The intent of Expedited Forwa=
rding PHB [RFC3246] is to provide a building block for low-loss, low-delay,=
 and low-jitter services.' TICTOC could in principle recommend defining a n=
ew PHB tailored for PTP and similar services, but I guess this would be a l=
onger process.<br><br>I would appreciate if others will share their insight=
 on the recommended usage and whether this issue should or should not be ad=
dressed by TICTOC. <br><br>Here is the relevant text from IEEE1588-2008 Ann=
ex D: &quot;For PTP event messages, the value of the differentiated service=
 (DS) field in the Type of Service (ToS)<br>field should be set to the high=
est traffic class selector codepoint available.&quot; The PTP Telecom profi=
le for frequency distribution, ITU-T G.8265.1, doesn't specify or recommend=
 DSCP settings.<br><br>Best,<br>Ron<tt><span style=3D'font-size:10.0pt'>___=
____________________________________________</span></tt><span style=3D'font=
-size:10.0pt'><br><tt>TICTOC mailing list</tt><br><tt><a href=3D"mailto:TIC=
TOC@ietf.org">TICTOC@ietf.org</a></tt><br><tt><a href=3D"https://www.ietf.o=
rg/mailman/listinfo/tictoc">https://www.ietf.org/mailman/listinfo/tictoc</a=
></tt><br><br></span><o:p></o:p></p><pre><o:p>&nbsp;</o:p></pre><pre>------=
--------------------------------------------------<o:p></o:p></pre><pre>ZTE=
&nbsp;Information&nbsp;Security&nbsp;Notice:&nbsp;The&nbsp;information&nbsp=
;contained&nbsp;in&nbsp;this&nbsp;mail&nbsp;is&nbsp;solely&nbsp;property&nb=
sp;of&nbsp;the&nbsp;sender's&nbsp;organization.&nbsp;This&nbsp;mail&nbsp;co=
mmunication&nbsp;is&nbsp;confidential.&nbsp;Recipients&nbsp;named&nbsp;abov=
e&nbsp;are&nbsp;obligated&nbsp;to&nbsp;maintain&nbsp;secrecy&nbsp;and&nbsp;=
are&nbsp;not&nbsp;permitted&nbsp;to&nbsp;disclose&nbsp;the&nbsp;contents&nb=
sp;of&nbsp;this&nbsp;communication&nbsp;to&nbsp;others.<o:p></o:p></pre><pr=
e>This&nbsp;email&nbsp;and&nbsp;any&nbsp;files&nbsp;transmitted&nbsp;with&n=
bsp;it&nbsp;are&nbsp;confidential&nbsp;and&nbsp;intended&nbsp;solely&nbsp;f=
or&nbsp;the&nbsp;use&nbsp;of&nbsp;the&nbsp;individual&nbsp;or&nbsp;entity&n=
bsp;to&nbsp;whom&nbsp;they&nbsp;are&nbsp;addressed.&nbsp;If&nbsp;you&nbsp;h=
ave&nbsp;received&nbsp;this&nbsp;email&nbsp;in&nbsp;error&nbsp;please&nbsp;=
notify&nbsp;the&nbsp;originator&nbsp;of&nbsp;the&nbsp;message.&nbsp;Any&nbs=
p;views&nbsp;expressed&nbsp;in&nbsp;this&nbsp;message&nbsp;are&nbsp;those&n=
bsp;of&nbsp;the&nbsp;individual&nbsp;sender.<o:p></o:p></pre><pre>This&nbsp=
;message&nbsp;has&nbsp;been&nbsp;scanned&nbsp;for&nbsp;viruses&nbsp;and&nbs=
p;Spam&nbsp;by&nbsp;ZTE&nbsp;Anti-Spam&nbsp;system.<o:p></o:p></pre></div><=
/body></html>=

--_000_74470498B659FA4687F0B0018C19A89C014735063EB4ILMB01marve_--

From davari@broadcom.com  Mon Aug  8 10:51:47 2011
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 4764521F8B53 for <tictoc@ietfa.amsl.com>; Mon,  8 Aug 2011 10:51:47 -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=[AWL=-0.000, 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 ap8kk4UETvfl for <tictoc@ietfa.amsl.com>; Mon,  8 Aug 2011 10:51:46 -0700 (PDT)
Received: from MMS3.broadcom.com (mms3.broadcom.com [216.31.210.19]) by ietfa.amsl.com (Postfix) with ESMTP id 60EC321F8B3C for <tictoc@ietf.org>; Mon,  8 Aug 2011 10:51:46 -0700 (PDT)
Received: from [10.16.192.232] by MMS3.broadcom.com with ESMTP (Broadcom SMTP Relay (Email Firewall v6.3.2)); Mon, 08 Aug 2011 10:42:08 -0700
X-Server-Uuid: B55A25B1-5D7D-41F8-BC53-C57E7AD3C201
Received: from SJEXCHCCR02.corp.ad.broadcom.com ([10.16.192.130]) by SJEXCHHUB02.corp.ad.broadcom.com ([10.16.192.232]) with mapi; Mon, 8 Aug 2011 10:37:02 -0700
From: "Shahram Davari" <davari@broadcom.com>
To: "Ron Cohen" <ronc.ntear@gmail.com>, "tictoc@ietf.org" <tictoc@ietf.org>
Date: Mon, 8 Aug 2011 10:37:01 -0700
Thread-Topic: [TICTOC] DSCP for PTP
Thread-Index: AcxU2A2F4jm3gGJ2RuKVTcPaDdkHdABGVIOg
Message-ID: <2C2F1EBA8050E74EA81502D5740B4BD6A9327F9E2C@SJEXCHCCR02.corp.ad.broadcom.com>
References: <CALMYT9Qt7HAWA6mAe7m+58=_jQ68a0bhnNq97KFU22_4yf4xKA@mail.gmail.com>
In-Reply-To: <CALMYT9Qt7HAWA6mAe7m+58=_jQ68a0bhnNq97KFU22_4yf4xKA@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
MIME-Version: 1.0
X-WSS-ID: 625EC07A3KO3851689-01-01
Content-Type: multipart/alternative; boundary=_000_2C2F1EBA8050E74EA81502D5740B4BD6A9327F9E2CSJEXCHCCR02co_
Subject: Re: [TICTOC] DSCP for PTP
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, 08 Aug 2011 17:51:47 -0000

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

Ron,

I agree with you that all PTP messages must configured with highest priorit=
y (a.k.a EF PHB) and EF should be the default. In fact I would also think i=
t is best to use L-LSP with EF PHB for 15880MPLS. If this is acceptable by =
the group then we could add this to the 1588oMPLS draft.


Regards,
Shahram

From: tictoc-bounces@ietf.org [mailto:tictoc-bounces@ietf.org] On Behalf Of=
 Ron Cohen
Sent: Sunday, August 07, 2011 1:00 AM
To: tictoc@ietf.org
Subject: [TICTOC] DSCP for PTP

Hi,

Current standards do not recommend which DSCP values to set on PTP messages=
. As a result vendors have chosen different default values, and some vendor=
s also differentiate between the DSCP set on PTP Event messages (Sync, Dela=
y_Req, etc.) and PTP General messages (Announce, Follow_Up, Delay_Resp). I =
think TICTOC can help clarify the recommended DSCP usage, along the guideli=
nes of RFC4595, 'Configuration Guidelines for DiffServ Service Classes'.

In my opinion classifying PTP event and general messages into separate PHBs=
 is problematic as discard of Follow_Up would render its associated Sync me=
ssage useless. Forwarding of Sync messages in a higher priority queue compa=
red to Follow_Up may lead to Sync message getting ahead of the previous Fol=
low_Up message which again causes the slave to discard the previous Sync me=
ssage. Hence the first order recommendation in my opinion should be to use =
the same PHB (and DSCP marking) to all PTP messages.

Choosing one of the existing PHBs as the recommended one for PTP is somewha=
t harder. EF is a reasonable choice in my opinion, as per RFC4595 'The inte=
nt of Expedited Forwarding PHB [RFC3246] is to provide a building block for=
 low-loss, low-delay, and low-jitter services.' TICTOC could in principle r=
ecommend defining a new PHB tailored for PTP and similar services, but I gu=
ess this would be a longer process.

I would appreciate if others will share their insight on the recommended us=
age and whether this issue should or should not be addressed by TICTOC.

Here is the relevant text from IEEE1588-2008 Annex D: "For PTP event messag=
es, the value of the differentiated service (DS) field in the Type of Servi=
ce (ToS)
field should be set to the highest traffic class selector codepoint availab=
le." The PTP Telecom profile for frequency distribution, ITU-T G.8265.1, do=
esn't specify or recommend DSCP settings.

Best,
Ron

--_000_2C2F1EBA8050E74EA81502D5740B4BD6A9327F9E2CSJEXCHCCR02co_
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-EQUI=
V=3D"Content-Type" CONTENT=3D"text/html; charset=3Dus-ascii"><meta name=3DG=
enerator content=3D"Microsoft Word 12 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
span.EmailStyle17
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]--></head><body lang=3DEN-US link=3Dblue vli=
nk=3Dpurple><div class=3DWordSection1><p class=3DMsoNormal><span style=3D'f=
ont-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Ron,<o:p>=
</o:p></span></p><p class=3DMsoNormal><span style=3D'font-size:11.0pt;font-=
family:"Calibri","sans-serif";color:#1F497D'><o:p>&nbsp;</o:p></span></p><p=
 class=3DMsoNormal><span style=3D'font-size:11.0pt;font-family:"Calibri","s=
ans-serif";color:#1F497D'>I agree with you that all PTP messages must confi=
gured with highest priority (a.k.a EF PHB) and EF should be the default. In=
 fact I would also think it is best to use L-LSP with EF PHB for 15880MPLS.=
 If this is acceptable by the group then we could add this to the 1588oMPLS=
 draft.<o:p></o:p></span></p><p class=3DMsoNormal><span style=3D'font-size:=
11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p>&nbsp;</o:p><=
/span></p><p class=3DMsoNormal><span style=3D'font-size:11.0pt;font-family:=
"Calibri","sans-serif";color:#1F497D'><o:p>&nbsp;</o:p></span></p><p class=
=3DMsoNormal><span style=3D'font-size:11.0pt;font-family:"Calibri","sans-se=
rif";color:#1F497D'>Regards,<o:p></o:p></span></p><p class=3DMsoNormal><spa=
n style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>Shahram<o:p></o:p></span></p><p class=3DMsoNormal><span style=3D'font-si=
ze:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p>&nbsp;</o:=
p></span></p><div style=3D'border:none;border-top:solid #B5C4DF 1.0pt;paddi=
ng:3.0pt 0in 0in 0in'><p class=3DMsoNormal><b><span style=3D'font-size:10.0=
pt;font-family:"Tahoma","sans-serif"'>From:</span></b><span style=3D'font-s=
ize:10.0pt;font-family:"Tahoma","sans-serif"'> tictoc-bounces@ietf.org [mai=
lto:tictoc-bounces@ietf.org] <b>On Behalf Of </b>Ron Cohen<br><b>Sent:</b> =
Sunday, August 07, 2011 1:00 AM<br><b>To:</b> tictoc@ietf.org<br><b>Subject=
:</b> [TICTOC] DSCP for PTP<o:p></o:p></span></p></div><p class=3DMsoNormal=
><o:p>&nbsp;</o:p></p><div><p class=3DMsoNormal>Hi,<br><br>Current standard=
s do not recommend which DSCP values to set on PTP messages. As a result ve=
ndors have chosen different default values, and some vendors also different=
iate between the DSCP set on PTP Event messages (Sync, Delay_Req, etc.) and=
 PTP General messages (Announce, Follow_Up, Delay_Resp). I think TICTOC can=
 help clarify the recommended DSCP usage, along the guidelines of RFC4595, =
'Configuration Guidelines for DiffServ Service Classes'.<br><br>In my opini=
on classifying PTP event and general messages into separate PHBs is problem=
atic as discard of Follow_Up would render its associated Sync message usele=
ss. Forwarding of Sync messages in a higher priority queue compared to Foll=
ow_Up may lead to Sync message getting ahead of the previous Follow_Up mess=
age which again causes the slave to discard the previous Sync message. Henc=
e the first order recommendation in my opinion should be to use the same PH=
B (and DSCP marking) to all PTP messages. <br><br>Choosing one of the exist=
ing PHBs as the recommended one for PTP is somewhat harder. EF is a reasona=
ble choice in my opinion, as per RFC4595 'The intent of Expedited Forwardin=
g PHB [RFC3246] is to provide a building block for low-loss, low-delay, and=
 low-jitter services.' TICTOC could in principle recommend defining a new P=
HB tailored for PTP and similar services, but I guess this would be a longe=
r process.<br><br>I would appreciate if others will share their insight on =
the recommended usage and whether this issue should or should not be addres=
sed by TICTOC. <br><br>Here is the relevant text from IEEE1588-2008 Annex D=
: &quot;For PTP event messages, the value of the differentiated service (DS=
) field in the Type of Service (ToS)<br>field should be set to the highest =
traffic class selector codepoint available.&quot; The PTP Telecom profile f=
or frequency distribution, ITU-T G.8265.1, doesn't specify or recommend DSC=
P settings.<br><br>Best,<br>Ron<o:p></o:p></p></div></div></body></html>=

--_000_2C2F1EBA8050E74EA81502D5740B4BD6A9327F9E2CSJEXCHCCR02co_--


From davari@broadcom.com  Mon Aug  8 10:56:54 2011
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 B000F21F8B5C for <tictoc@ietfa.amsl.com>; Mon,  8 Aug 2011 10:56:54 -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=[AWL=-0.000, 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 sX7+xeTOlJ7T for <tictoc@ietfa.amsl.com>; Mon,  8 Aug 2011 10:56:52 -0700 (PDT)
Received: from MMS3.broadcom.com (mms3.broadcom.com [216.31.210.19]) by ietfa.amsl.com (Postfix) with ESMTP id B926C21F8B23 for <tictoc@ietf.org>; Mon,  8 Aug 2011 10:56:52 -0700 (PDT)
Received: from [10.16.192.224] by MMS3.broadcom.com with ESMTP (Broadcom SMTP Relay (Email Firewall v6.3.2)); Mon, 08 Aug 2011 11:02:18 -0700
X-Server-Uuid: B55A25B1-5D7D-41F8-BC53-C57E7AD3C201
Received: from SJEXCHCCR02.corp.ad.broadcom.com ([10.16.192.130]) by SJEXCHHUB01.corp.ad.broadcom.com ([10.16.192.224]) with mapi; Mon, 8 Aug 2011 10:57:11 -0700
From: "Shahram Davari" <davari@broadcom.com>
To: "Tal Mizrahi" <talmi@marvell.com>, "Ron Cohen" <ronc.ntear@gmail.com>, "tictoc@ietf.org" <tictoc@ietf.org>
Date: Mon, 8 Aug 2011 10:57:10 -0700
Thread-Topic: [TICTOC] The Need for Checksum Extension
Thread-Index: AcxNbfYRtIOvX2NjQVWo8np0NdjaUgG8DezQAGV0CfA=
Message-ID: <2C2F1EBA8050E74EA81502D5740B4BD6A9327F9E6E@SJEXCHCCR02.corp.ad.broadcom.com>
References: <CALMYT9TP6WqrZgR2+o_zk7QwYXFE28d4QBo8Q89q+OYJ2cvy1Q@mail.gmail.com> <74470498B659FA4687F0B0018C19A89C0134BF782962@IL-MB01.marvell.com>
In-Reply-To: <74470498B659FA4687F0B0018C19A89C0134BF782962@IL-MB01.marvell.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
MIME-Version: 1.0
X-WSS-ID: 625EFB233KO3857078-01-01
Content-Type: multipart/alternative; boundary=_000_2C2F1EBA8050E74EA81502D5740B4BD6A9327F9E6ESJEXCHCCR02co_
Subject: Re: [TICTOC] The Need for Checksum Extension
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, 08 Aug 2011 17:56:54 -0000

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

Tal,

I don't know about OWAMP but NTP doesn't have the concept of TC (Transparen=
t Clocking). So why is there a need for UDP checksum update for NTP?

Also if any of the timing messages needs to change in a router (such as Res=
idence  time update), the router should be able to fully parse that packet =
including the UDP header. So the router would exactly know the UDP checksum=
 location. Therefore I don't see what is the benefit of such Checksum trail=
er/Extension.

Regards,
Shahram

From: tictoc-bounces@ietf.org [mailto:tictoc-bounces@ietf.org] On Behalf Of=
 Tal Mizrahi
Sent: Saturday, August 06, 2011 10:43 AM
To: Ron Cohen; tictoc@ietf.org
Subject: Re: [TICTOC] The Need for Checksum Extension

Hi,

Sorry for the late reply, I missed this thread.
Ron, your observation is correct.

With that said, from the implementation perspective, there is a benefit to =
have a single procedure (and a single implementation) for updating the UDP =
checksum in a timestamped packet (PTP, NTP, OWAMP, TWAMP). So for PTP the U=
DP Checksum update clearly benefits from the Checksum Trailer. As for NTP a=
nd OWAMP, the benefit of using the Checksum Trailer is from having the same=
 UDP checksum  update flow as the one for PTP.
At the end of the day this draft is about easy implementation - we are tryi=
ng to define the Checksum Trailer in a way that will allow easy implementat=
ion, while not requiring any changes in existing implementations.

Regards,
Tal.
From: tictoc-bounces@ietf.org [mailto:tictoc-bounces@ietf.org] On Behalf Of=
 Ron Cohen
Sent: Friday, July 29, 2011 12:33 AM
To: tictoc@ietf.org
Subject: [TICTOC] The Need for Checksum Extension

Hi,

I'd like to clarify my comment during the meeting.

According to RFC1612 Eqn 3 (incremental checksum update):

HC' =3D ~(C + (-m) + m') =3D ~(~HC + ~m + m')

Where HC' is the updated checksum, HC is the current (message) checksum, m'=
 in the new value that is going to be written instead of the value m in the=
 message.

If I know that value of m is zero, I can calculate the new checksum using t=
he old checksum and the new value alone.

That is, if the NTP/OWAMP/TWAMP CPU sets the transmit timestamp to zero (i.=
e. m =3D 0), the FPGA or switch that measures the transmit timestamp once t=
he first byte of the message is sent on the wire, can update the UDP checks=
um itself incrementally and doesn't need the extension. The extension is ne=
ed only if you have to read the timestamp which appears later in the packet=
 in order to update the checksum.

This is very different from 'real' intermediate devices (i.e. transparent c=
locks) used by PTP.

Best,
Ron

--_000_2C2F1EBA8050E74EA81502D5740B4BD6A9327F9E6ESJEXCHCCR02co_
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-EQUI=
V=3D"Content-Type" CONTENT=3D"text/html; charset=3Dus-ascii"><meta name=3DG=
enerator content=3D"Microsoft Word 12 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
span.EmailStyle17
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
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=3DEN-US link=3Dblue vli=
nk=3Dpurple><div class=3DWordSection1><p class=3DMsoNormal><span style=3D'f=
ont-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Tal,<o:p>=
</o:p></span></p><p class=3DMsoNormal><span style=3D'font-size:11.0pt;font-=
family:"Calibri","sans-serif";color:#1F497D'><o:p>&nbsp;</o:p></span></p><p=
 class=3DMsoNormal><span style=3D'font-size:11.0pt;font-family:"Calibri","s=
ans-serif";color:#1F497D'>I don&#8217;t know about OWAMP but NTP doesn&#821=
7;t have the concept of TC (Transparent Clocking). So why is there a need f=
or UDP checksum update for NTP?<o:p></o:p></span></p><p class=3DMsoNormal><=
span style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F=
497D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span style=3D'font-=
size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Also if any o=
f the timing messages needs to change in a router (such as Residence&nbsp; =
time update), the router should be able to fully parse that packet includin=
g the UDP header. So the router would exactly know the UDP checksum locatio=
n. Therefore I don&#8217;t see what is the benefit of such Checksum trailer=
/Extension.<o:p></o:p></span></p><p class=3DMsoNormal><span style=3D'font-s=
ize:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p>&nbsp;</o=
:p></span></p><p class=3DMsoNormal><span style=3D'font-size:11.0pt;font-fam=
ily:"Calibri","sans-serif";color:#1F497D'>Regards,<o:p></o:p></span></p><p =
class=3DMsoNormal><span style=3D'font-size:11.0pt;font-family:"Calibri","sa=
ns-serif";color:#1F497D'>Shahram<o:p></o:p></span></p><p class=3DMsoNormal>=
<span style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1=
F497D'><o:p>&nbsp;</o:p></span></p><div><div style=3D'border:none;border-to=
p:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in'><p class=3DMsoNormal><b><s=
pan style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</spa=
n></b><span style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'> t=
ictoc-bounces@ietf.org [mailto:tictoc-bounces@ietf.org] <b>On Behalf Of </b=
>Tal Mizrahi<br><b>Sent:</b> Saturday, August 06, 2011 10:43 AM<br><b>To:</=
b> Ron Cohen; tictoc@ietf.org<br><b>Subject:</b> Re: [TICTOC] The Need for =
Checksum Extension<o:p></o:p></span></p></div></div><p class=3DMsoNormal><o=
:p>&nbsp;</o:p></p><p class=3DMsoNormal>Hi,<o:p></o:p></p><p class=3DMsoNor=
mal><o:p>&nbsp;</o:p></p><p class=3DMsoNormal>Sorry for the late reply, I m=
issed this thread.<o:p></o:p></p><p class=3DMsoNormal>Ron, your observation=
 is correct.<o:p></o:p></p><p class=3DMsoNormal><o:p>&nbsp;</o:p></p><p cla=
ss=3DMsoNormal>With that said, from the implementation perspective, there i=
s a benefit to have a single procedure (and a single implementation) for up=
dating the UDP checksum in a timestamped packet (PTP, NTP, OWAMP, TWAMP). S=
o for PTP the UDP Checksum update clearly benefits from the Checksum Traile=
r. As for NTP and OWAMP, the benefit of using the Checksum Trailer is from =
having the same UDP checksum &nbsp;update flow as the one for PTP.<o:p></o:=
p></p><p class=3DMsoNormal>At the end of the day this draft is about easy i=
mplementation - we are trying to define the Checksum Trailer in a way that =
will allow easy implementation, while not requiring any changes in existing=
 implementations.<o:p></o:p></p><p class=3DMsoNormal><o:p>&nbsp;</o:p></p><=
p class=3DMsoNormal>Regards,<span style=3D'font-size:11.0pt;font-family:"Ca=
libri","sans-serif"'><o:p></o:p></span></p><p class=3DMsoNormal><span style=
=3D'font-size:10.0pt;font-family:"Arial","sans-serif"'>Tal.</span><o:p></o:=
p></p><p class=3DMsoNormal><b><span style=3D'font-size:10.0pt;font-family:"=
Tahoma","sans-serif"'>From:</span></b><span style=3D'font-size:10.0pt;font-=
family:"Tahoma","sans-serif"'> tictoc-bounces@ietf.org [mailto:tictoc-bounc=
es@ietf.org] <b>On Behalf Of </b>Ron Cohen<br><b>Sent:</b> Friday, July 29,=
 2011 12:33 AM<br><b>To:</b> tictoc@ietf.org<br><b>Subject:</b> [TICTOC] Th=
e Need for Checksum Extension<o:p></o:p></span></p><p class=3DMsoNormal><o:=
p>&nbsp;</o:p></p><div><p class=3DMsoNormal style=3D'margin-bottom:12.0pt'>=
Hi,<br><br>I'd like to clarify my comment during the meeting.<br><br>Accord=
ing to RFC1612 Eqn 3 (incremental checksum update):<br><br>HC' =3D ~(C + (-=
m) + m') =3D ~(~HC + ~m + m')<br><br>Where HC' is the updated checksum, HC =
is the current (message) checksum, m' in the new value that is going to be =
written instead of the value m in the message.<br><br>If I know that value =
of m is zero, I can calculate the new checksum using the old checksum and t=
he new value alone.<br><br>That is, if the NTP/OWAMP/TWAMP CPU sets the tra=
nsmit timestamp to zero (i.e. m =3D 0), the FPGA or switch that measures th=
e transmit timestamp once the first byte of the message is sent on the wire=
, can update the UDP checksum itself incrementally and doesn't need the ext=
ension. The extension is need only if you have to read the timestamp which =
appears later in the packet in order to update the checksum.<br><br>This is=
 very different from 'real' intermediate devices (i.e. transparent clocks) =
used by PTP.<br><br>Best,<br>Ron<o:p></o:p></p></div></div></body></html>=

--_000_2C2F1EBA8050E74EA81502D5740B4BD6A9327F9E6ESJEXCHCCR02co_--


From ronc.ntear@gmail.com  Mon Aug  8 12:41:05 2011
Return-Path: <ronc.ntear@gmail.com>
X-Original-To: tictoc@ietfa.amsl.com
Delivered-To: tictoc@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 082305E800D for <tictoc@ietfa.amsl.com>; Mon,  8 Aug 2011 12:41:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.598
X-Spam-Level: 
X-Spam-Status: No, score=-3.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, 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 qI8TcUXwjWYM for <tictoc@ietfa.amsl.com>; Mon,  8 Aug 2011 12:41:04 -0700 (PDT)
Received: from mail-gx0-f172.google.com (mail-gx0-f172.google.com [209.85.161.172]) by ietfa.amsl.com (Postfix) with ESMTP id 04CE35E8009 for <tictoc@ietf.org>; Mon,  8 Aug 2011 12:41:03 -0700 (PDT)
Received: by gxk19 with SMTP id 19so1177588gxk.31 for <tictoc@ietf.org>; Mon, 08 Aug 2011 12:41:30 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=RHFMTbc6OlglTROtZZEY1CIryUT77VFoUEjxAavm8uA=; b=a/ezI+36tUA6csBaK7xzxAnS4O7df/ewplf5v5+XsdEPAduiRfpSO2GCQaPNlqVP/b F8tKjsT3sw27lSCOC4oTFa64rUpnd9JHdnryyOWJA17wqdAcvfy+N0s/P7PtY5aG7xdJ /CIHHXL8zE2SB2JDXQTExdbS74Fk5W61DbMNI=
MIME-Version: 1.0
Received: by 10.236.181.229 with SMTP id l65mr7707910yhm.204.1312832490465; Mon, 08 Aug 2011 12:41:30 -0700 (PDT)
Received: by 10.147.114.4 with HTTP; Mon, 8 Aug 2011 12:41:30 -0700 (PDT)
In-Reply-To: <2C2F1EBA8050E74EA81502D5740B4BD6A9327F9E2C@SJEXCHCCR02.corp.ad.broadcom.com>
References: <CALMYT9Qt7HAWA6mAe7m+58=_jQ68a0bhnNq97KFU22_4yf4xKA@mail.gmail.com> <2C2F1EBA8050E74EA81502D5740B4BD6A9327F9E2C@SJEXCHCCR02.corp.ad.broadcom.com>
Date: Mon, 8 Aug 2011 22:41:30 +0300
Message-ID: <CALMYT9Tp9OkCfPZvg=Op03QPhxQZ7d+724XsJLC=hFzMhExXdg@mail.gmail.com>
From: Ron Cohen <ronc.ntear@gmail.com>
To: Shahram Davari <davari@broadcom.com>
Content-Type: multipart/alternative; boundary=20cf305b1be23e67eb04aa03a23e
Cc: "tictoc@ietf.org" <tictoc@ietf.org>
Subject: Re: [TICTOC] DSCP for PTP
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, 08 Aug 2011 19:41:05 -0000

--20cf305b1be23e67eb04aa03a23e
Content-Type: text/plain; charset=ISO-8859-1

Hi Shahram,

One possible drawback for using EF for PTP is that EF is also used by some
video/voice and similar plesio-synchronous applications. The danger is that
the noise introduced by such application might be harder to filter than
'normal' packet based traffic. Therefore, it might be better to use another
PHB, with even higher forwarding priority if possible, or maybe simply a
different PHB altogether. It would be great if someone did a study on this
and can share the results with us.

We should also differentiate between the PTP-aware (TC/BC) or PTP-unaware
cases. In principle a TC doesn't need to send PTP messages with high
forwarding priority as it compensates for the residence time anyhow.

Best,
Ron

On Mon, Aug 8, 2011 at 8:37 PM, Shahram Davari <davari@broadcom.com> wrote:

> Ron,****
>
> ** **
>
> I agree with you that all PTP messages must configured with highest
> priority (a.k.a EF PHB) and EF should be the default. In fact I would also
> think it is best to use L-LSP with EF PHB for 15880MPLS. If this is
> acceptable by the group then we could add this to the 1588oMPLS draft.****
>
> ** **
>
> ** **
>
> Regards,****
>
> Shahram****
>
> ** **
>
> *From:* tictoc-bounces@ietf.org [mailto:tictoc-bounces@ietf.org] *On
> Behalf Of *Ron Cohen
> *Sent:* Sunday, August 07, 2011 1:00 AM
> *To:* tictoc@ietf.org
> *Subject:* [TICTOC] DSCP for PTP****
>
> ** **
>
> Hi,
>
> Current standards do not recommend which DSCP values to set on PTP
> messages. As a result vendors have chosen different default values, and some
> vendors also differentiate between the DSCP set on PTP Event messages (Sync,
> Delay_Req, etc.) and PTP General messages (Announce, Follow_Up, Delay_Resp).
> I think TICTOC can help clarify the recommended DSCP usage, along the
> guidelines of RFC4595, 'Configuration Guidelines for DiffServ Service
> Classes'.
>
> In my opinion classifying PTP event and general messages into separate PHBs
> is problematic as discard of Follow_Up would render its associated Sync
> message useless. Forwarding of Sync messages in a higher priority queue
> compared to Follow_Up may lead to Sync message getting ahead of the previous
> Follow_Up message which again causes the slave to discard the previous Sync
> message. Hence the first order recommendation in my opinion should be to use
> the same PHB (and DSCP marking) to all PTP messages.
>
> Choosing one of the existing PHBs as the recommended one for PTP is
> somewhat harder. EF is a reasonable choice in my opinion, as per RFC4595
> 'The intent of Expedited Forwarding PHB [RFC3246] is to provide a building
> block for low-loss, low-delay, and low-jitter services.' TICTOC could in
> principle recommend defining a new PHB tailored for PTP and similar
> services, but I guess this would be a longer process.
>
> I would appreciate if others will share their insight on the recommended
> usage and whether this issue should or should not be addressed by TICTOC.
>
> Here is the relevant text from IEEE1588-2008 Annex D: "For PTP event
> messages, the value of the differentiated service (DS) field in the Type of
> Service (ToS)
> field should be set to the highest traffic class selector codepoint
> available." The PTP Telecom profile for frequency distribution, ITU-T
> G.8265.1, doesn't specify or recommend DSCP settings.
>
> Best,
> Ron****
>

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

<div dir=3D"ltr">Hi Shahram,<br><br>One possible drawback for using EF for =
PTP is that EF is also used by some video/voice and similar plesio-synchron=
ous applications. The danger is that the noise introduced by such applicati=
on might be harder to filter than &#39;normal&#39; packet based traffic. Th=
erefore, it might be better to use another PHB, with even higher forwarding=
 priority if possible, or maybe simply a different PHB altogether. It would=
 be great if someone did a study on this and can share the results with us.=
 <br>
<br>We should also differentiate between the PTP-aware (TC/BC) or PTP-unawa=
re cases. In principle a TC doesn&#39;t need to send PTP messages with high=
 forwarding priority as it compensates for the residence time anyhow. <br>
<br>Best,<br>Ron=A0 <br><br><div class=3D"gmail_quote">On Mon, Aug 8, 2011 =
at 8:37 PM, Shahram Davari <span dir=3D"ltr">&lt;<a href=3D"mailto:davari@b=
roadcom.com">davari@broadcom.com</a>&gt;</span> wrote:<br><blockquote class=
=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padd=
ing-left:1ex;">
<div link=3D"blue" vlink=3D"purple" lang=3D"EN-US"><div><p class=3D"MsoNorm=
al"><span style=3D"font-size:11.0pt;color:#1F497D">Ron,<u></u><u></u></span=
></p><p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;color:#1F497D">=
<u></u>=A0<u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;color:#1F497D">I agr=
ee with you that all PTP messages must configured with highest priority (a.=
k.a EF PHB) and EF should be the default. In fact I would also think it is =
best to use L-LSP with EF PHB for 15880MPLS. If this is acceptable by the g=
roup then we could add this to the 1588oMPLS draft.<u></u><u></u></span></p=
>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;color:#1F497D"><u></=
u>=A0<u></u></span></p><p class=3D"MsoNormal"><span style=3D"font-size:11.0=
pt;color:#1F497D"><u></u>=A0<u></u></span></p><p class=3D"MsoNormal"><span =
style=3D"font-size:11.0pt;color:#1F497D">Regards,<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;color:#1F497D">Shahr=
am<u></u><u></u></span></p><p class=3D"MsoNormal"><span style=3D"font-size:=
11.0pt;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">From:</span></b>=
<span style=3D"font-size:10.0pt"> <a href=3D"mailto:tictoc-bounces@ietf.org=
" target=3D"_blank">tictoc-bounces@ietf.org</a> [mailto:<a href=3D"mailto:t=
ictoc-bounces@ietf.org" target=3D"_blank">tictoc-bounces@ietf.org</a>] <b>O=
n Behalf Of </b>Ron Cohen<br>
<b>Sent:</b> Sunday, August 07, 2011 1:00 AM<br><b>To:</b> <a href=3D"mailt=
o:tictoc@ietf.org" target=3D"_blank">tictoc@ietf.org</a><br><b>Subject:</b>=
 [TICTOC] DSCP for PTP<u></u><u></u></span></p></div><div><div></div><div c=
lass=3D"h5">
<p class=3D"MsoNormal"><u></u>=A0<u></u></p><div><p class=3D"MsoNormal">Hi,=
<br><br>Current standards do not recommend which DSCP values to set on PTP =
messages. As a result vendors have chosen different default values, and som=
e vendors also differentiate between the DSCP set on PTP Event messages (Sy=
nc, Delay_Req, etc.) and PTP General messages (Announce, Follow_Up, Delay_R=
esp). I think TICTOC can help clarify the recommended DSCP usage, along the=
 guidelines of RFC4595, &#39;Configuration Guidelines for DiffServ Service =
Classes&#39;.<br>
<br>In my opinion classifying PTP event and general messages into separate =
PHBs is problematic as discard of Follow_Up would render its associated Syn=
c message useless. Forwarding of Sync messages in a higher priority queue c=
ompared to Follow_Up may lead to Sync message getting ahead of the previous=
 Follow_Up message which again causes the slave to discard the previous Syn=
c message. Hence the first order recommendation in my opinion should be to =
use the same PHB (and DSCP marking) to all PTP messages. <br>
<br>Choosing one of the existing PHBs as the recommended one for PTP is som=
ewhat harder. EF is a reasonable choice in my opinion, as per RFC4595 &#39;=
The intent of Expedited Forwarding PHB [RFC3246] is to provide a building b=
lock for low-loss, low-delay, and low-jitter services.&#39; TICTOC could in=
 principle recommend defining a new PHB tailored for PTP and similar servic=
es, but I guess this would be a longer process.<br>
<br>I would appreciate if others will share their insight on the recommende=
d usage and whether this issue should or should not be addressed by TICTOC.=
 <br><br>Here is the relevant text from IEEE1588-2008 Annex D: &quot;For PT=
P event messages, the value of the differentiated service (DS) field in the=
 Type of Service (ToS)<br>
field should be set to the highest traffic class selector codepoint availab=
le.&quot; The PTP Telecom profile for frequency distribution, ITU-T G.8265.=
1, doesn&#39;t specify or recommend DSCP settings.<br><br>Best,<br>Ron<u></=
u><u></u></p>
</div></div></div></div></div></blockquote></div><br></div>

--20cf305b1be23e67eb04aa03a23e--

From davari@broadcom.com  Mon Aug  8 13:09:38 2011
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 DC8CB11E8092 for <tictoc@ietfa.amsl.com>; Mon,  8 Aug 2011 13:09:38 -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=[AWL=-0.000, 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 lPQa9SllFsAG for <tictoc@ietfa.amsl.com>; Mon,  8 Aug 2011 13:09:38 -0700 (PDT)
Received: from MMS3.broadcom.com (mms3.broadcom.com [216.31.210.19]) by ietfa.amsl.com (Postfix) with ESMTP id 008BC11E8081 for <tictoc@ietf.org>; Mon,  8 Aug 2011 13:09:37 -0700 (PDT)
Received: from [10.16.192.232] by MMS3.broadcom.com with ESMTP (Broadcom SMTP Relay (Email Firewall v6.3.2)); Mon, 08 Aug 2011 13:08:22 -0700
X-Server-Uuid: B55A25B1-5D7D-41F8-BC53-C57E7AD3C201
Received: from SJEXCHCCR02.corp.ad.broadcom.com ([10.16.192.130]) by SJEXCHHUB02.corp.ad.broadcom.com ([10.16.192.232]) with mapi; Mon, 8 Aug 2011 13:03:16 -0700
From: "Shahram Davari" <davari@broadcom.com>
To: "Ron Cohen" <ronc.ntear@gmail.com>
Date: Mon, 8 Aug 2011 13:03:14 -0700
Thread-Topic: [TICTOC] DSCP for PTP
Thread-Index: AcxWAzTLmUooYv5uR2ew4NWSxV/XvAAApC1w
Message-ID: <2C2F1EBA8050E74EA81502D5740B4BD6A9327F9F90@SJEXCHCCR02.corp.ad.broadcom.com>
References: <CALMYT9Qt7HAWA6mAe7m+58=_jQ68a0bhnNq97KFU22_4yf4xKA@mail.gmail.com> <2C2F1EBA8050E74EA81502D5740B4BD6A9327F9E2C@SJEXCHCCR02.corp.ad.broadcom.com> <CALMYT9Tp9OkCfPZvg=Op03QPhxQZ7d+724XsJLC=hFzMhExXdg@mail.gmail.com>
In-Reply-To: <CALMYT9Tp9OkCfPZvg=Op03QPhxQZ7d+724XsJLC=hFzMhExXdg@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
MIME-Version: 1.0
X-WSS-ID: 625E9DBC3KO3890764-01-01
Content-Type: multipart/alternative; boundary=_000_2C2F1EBA8050E74EA81502D5740B4BD6A9327F9F90SJEXCHCCR02co_
Cc: "tictoc@ietf.org" <tictoc@ietf.org>
Subject: Re: [TICTOC] DSCP for PTP
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, 08 Aug 2011 20:09:39 -0000

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

Ron,

I have to look at this issue that you are raising. Do you have any referenc=
e for this effect?

In I theory one could have 2x EF PHB, with different DSCP code points, wher=
e one has higher priority than the other one.

Thx
Shahram

From: Ron Cohen [mailto:ronc.ntear@gmail.com]
Sent: Monday, August 08, 2011 12:41 PM
To: Shahram Davari
Cc: tictoc@ietf.org; manav.bhatia@alcatel-lucent.com
Subject: Re: [TICTOC] DSCP for PTP

Hi Shahram,

One possible drawback for using EF for PTP is that EF is also used by some =
video/voice and similar plesio-synchronous applications. The danger is that=
 the noise introduced by such application might be harder to filter than 'n=
ormal' packet based traffic. Therefore, it might be better to use another P=
HB, with even higher forwarding priority if possible, or maybe simply a dif=
ferent PHB altogether. It would be great if someone did a study on this and=
 can share the results with us.

We should also differentiate between the PTP-aware (TC/BC) or PTP-unaware c=
ases. In principle a TC doesn't need to send PTP messages with high forward=
ing priority as it compensates for the residence time anyhow.

Best,
Ron
On Mon, Aug 8, 2011 at 8:37 PM, Shahram Davari <davari@broadcom.com<mailto:=
davari@broadcom.com>> wrote:
Ron,

I agree with you that all PTP messages must configured with highest priorit=
y (a.k.a EF PHB) and EF should be the default. In fact I would also think i=
t is best to use L-LSP with EF PHB for 15880MPLS. If this is acceptable by =
the group then we could add this to the 1588oMPLS draft.


Regards,
Shahram

From: tictoc-bounces@ietf.org<mailto:tictoc-bounces@ietf.org> [mailto:ticto=
c-bounces@ietf.org<mailto:tictoc-bounces@ietf.org>] On Behalf Of Ron Cohen
Sent: Sunday, August 07, 2011 1:00 AM
To: tictoc@ietf.org<mailto:tictoc@ietf.org>
Subject: [TICTOC] DSCP for PTP

Hi,

Current standards do not recommend which DSCP values to set on PTP messages=
. As a result vendors have chosen different default values, and some vendor=
s also differentiate between the DSCP set on PTP Event messages (Sync, Dela=
y_Req, etc.) and PTP General messages (Announce, Follow_Up, Delay_Resp). I =
think TICTOC can help clarify the recommended DSCP usage, along the guideli=
nes of RFC4595, 'Configuration Guidelines for DiffServ Service Classes'.

In my opinion classifying PTP event and general messages into separate PHBs=
 is problematic as discard of Follow_Up would render its associated Sync me=
ssage useless. Forwarding of Sync messages in a higher priority queue compa=
red to Follow_Up may lead to Sync message getting ahead of the previous Fol=
low_Up message which again causes the slave to discard the previous Sync me=
ssage. Hence the first order recommendation in my opinion should be to use =
the same PHB (and DSCP marking) to all PTP messages.

Choosing one of the existing PHBs as the recommended one for PTP is somewha=
t harder. EF is a reasonable choice in my opinion, as per RFC4595 'The inte=
nt of Expedited Forwarding PHB [RFC3246] is to provide a building block for=
 low-loss, low-delay, and low-jitter services.' TICTOC could in principle r=
ecommend defining a new PHB tailored for PTP and similar services, but I gu=
ess this would be a longer process.

I would appreciate if others will share their insight on the recommended us=
age and whether this issue should or should not be addressed by TICTOC.

Here is the relevant text from IEEE1588-2008 Annex D: "For PTP event messag=
es, the value of the differentiated service (DS) field in the Type of Servi=
ce (ToS)
field should be set to the highest traffic class selector codepoint availab=
le." The PTP Telecom profile for frequency distribution, ITU-T G.8265.1, do=
esn't specify or recommend DSCP settings.

Best,
Ron


--_000_2C2F1EBA8050E74EA81502D5740B4BD6A9327F9F90SJEXCHCCR02co_
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-EQUI=
V=3D"Content-Type" CONTENT=3D"text/html; charset=3Dus-ascii"><meta name=3DG=
enerator content=3D"Microsoft Word 12 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
span.EmailStyle17
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]--></head><body lang=3DEN-US link=3Dblue vli=
nk=3Dpurple><div class=3DWordSection1><p class=3DMsoNormal><span style=3D'f=
ont-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Ron,<o:p>=
</o:p></span></p><p class=3DMsoNormal><span style=3D'font-size:11.0pt;font-=
family:"Calibri","sans-serif";color:#1F497D'><o:p>&nbsp;</o:p></span></p><p=
 class=3DMsoNormal><span style=3D'font-size:11.0pt;font-family:"Calibri","s=
ans-serif";color:#1F497D'>I have to look at this issue that you are raising=
. Do you have any reference for this effect? <o:p></o:p></span></p><p class=
=3DMsoNormal><span style=3D'font-size:11.0pt;font-family:"Calibri","sans-se=
rif";color:#1F497D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'=
>In I theory one could have 2x EF PHB, with different DSCP code points, whe=
re one has higher priority than the other one.<o:p></o:p></span></p><p clas=
s=3DMsoNormal><span style=3D'font-size:11.0pt;font-family:"Calibri","sans-s=
erif";color:#1F497D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span=
 style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D=
'>Thx<br>Shahram<o:p></o:p></span></p><p class=3DMsoNormal><span style=3D'f=
ont-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p>&nbs=
p;</o:p></span></p><div style=3D'border:none;border-top:solid #B5C4DF 1.0pt=
;padding:3.0pt 0in 0in 0in'><p class=3DMsoNormal><b><span style=3D'font-siz=
e:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span></b><span style=3D'=
font-size:10.0pt;font-family:"Tahoma","sans-serif"'> Ron Cohen [mailto:ronc=
.ntear@gmail.com] <br><b>Sent:</b> Monday, August 08, 2011 12:41 PM<br><b>T=
o:</b> Shahram Davari<br><b>Cc:</b> tictoc@ietf.org; manav.bhatia@alcatel-l=
ucent.com<br><b>Subject:</b> Re: [TICTOC] DSCP for PTP<o:p></o:p></span></p=
></div><p class=3DMsoNormal><o:p>&nbsp;</o:p></p><div><p class=3DMsoNormal =
style=3D'margin-bottom:12.0pt'>Hi Shahram,<br><br>One possible drawback for=
 using EF for PTP is that EF is also used by some video/voice and similar p=
lesio-synchronous applications. The danger is that the noise introduced by =
such application might be harder to filter than 'normal' packet based traff=
ic. Therefore, it might be better to use another PHB, with even higher forw=
arding priority if possible, or maybe simply a different PHB altogether. It=
 would be great if someone did a study on this and can share the results wi=
th us. <br><br>We should also differentiate between the PTP-aware (TC/BC) o=
r PTP-unaware cases. In principle a TC doesn't need to send PTP messages wi=
th high forwarding priority as it compensates for the residence time anyhow=
. <br><br>Best,<br>Ron&nbsp; <o:p></o:p></p><div><p class=3DMsoNormal>On Mo=
n, Aug 8, 2011 at 8:37 PM, Shahram Davari &lt;<a href=3D"mailto:davari@broa=
dcom.com">davari@broadcom.com</a>&gt; wrote:<o:p></o:p></p><div><div><p cla=
ss=3DMsoNormal style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'=
><span style=3D'font-size:11.0pt;color:#1F497D'>Ron,</span><o:p></o:p></p><=
p class=3DMsoNormal style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:=
auto'><span style=3D'font-size:11.0pt;color:#1F497D'>&nbsp;</span><o:p></o:=
p></p><p class=3DMsoNormal style=3D'mso-margin-top-alt:auto;mso-margin-bott=
om-alt:auto'><span style=3D'font-size:11.0pt;color:#1F497D'>I agree with yo=
u that all PTP messages must configured with highest priority (a.k.a EF PHB=
) and EF should be the default. In fact I would also think it is best to us=
e L-LSP with EF PHB for 15880MPLS. If this is acceptable by the group then =
we could add this to the 1588oMPLS draft.</span><o:p></o:p></p><p class=3DM=
soNormal style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span=
 style=3D'font-size:11.0pt;color:#1F497D'>&nbsp;</span><o:p></o:p></p><p cl=
ass=3DMsoNormal style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto=
'><span style=3D'font-size:11.0pt;color:#1F497D'>&nbsp;</span><o:p></o:p></=
p><p class=3DMsoNormal style=3D'mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto'><span style=3D'font-size:11.0pt;color:#1F497D'>Regards,</span><o:p=
></o:p></p><p class=3DMsoNormal style=3D'mso-margin-top-alt:auto;mso-margin=
-bottom-alt:auto'><span style=3D'font-size:11.0pt;color:#1F497D'>Shahram</s=
pan><o:p></o:p></p><p class=3DMsoNormal style=3D'mso-margin-top-alt:auto;ms=
o-margin-bottom-alt:auto'><span style=3D'font-size:11.0pt;color:#1F497D'>&n=
bsp;</span><o:p></o:p></p><div style=3D'border:none;border-top:solid #B5C4D=
F 1.0pt;padding:3.0pt 0in 0in 0in'><p class=3DMsoNormal style=3D'mso-margin=
-top-alt:auto;mso-margin-bottom-alt:auto'><b><span style=3D'font-size:10.0p=
t'>From:</span></b><span style=3D'font-size:10.0pt'> <a href=3D"mailto:tict=
oc-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>Ron Cohen<br><b>Sent:</b> Sunday, August=
 07, 2011 1:00 AM<br><b>To:</b> <a href=3D"mailto:tictoc@ietf.org" target=
=3D"_blank">tictoc@ietf.org</a><br><b>Subject:</b> [TICTOC] DSCP for PTP</s=
pan><o:p></o:p></p></div><div><div><p class=3DMsoNormal style=3D'mso-margin=
-top-alt:auto;mso-margin-bottom-alt:auto'>&nbsp;<o:p></o:p></p><div><p clas=
s=3DMsoNormal style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>=
Hi,<br><br>Current standards do not recommend which DSCP values to set on P=
TP messages. As a result vendors have chosen different default values, and =
some vendors also differentiate between the DSCP set on PTP Event messages =
(Sync, Delay_Req, etc.) and PTP General messages (Announce, Follow_Up, Dela=
y_Resp). I think TICTOC can help clarify the recommended DSCP usage, along =
the guidelines of RFC4595, 'Configuration Guidelines for DiffServ Service C=
lasses'.<br><br>In my opinion classifying PTP event and general messages in=
to separate PHBs is problematic as discard of Follow_Up would render its as=
sociated Sync message useless. Forwarding of Sync messages in a higher prio=
rity queue compared to Follow_Up may lead to Sync message getting ahead of =
the previous Follow_Up message which again causes the slave to discard the =
previous Sync message. Hence the first order recommendation in my opinion s=
hould be to use the same PHB (and DSCP marking) to all PTP messages. <br><b=
r>Choosing one of the existing PHBs as the recommended one for PTP is somew=
hat harder. EF is a reasonable choice in my opinion, as per RFC4595 'The in=
tent of Expedited Forwarding PHB [RFC3246] is to provide a building block f=
or low-loss, low-delay, and low-jitter services.' TICTOC could in principle=
 recommend defining a new PHB tailored for PTP and similar services, but I =
guess this would be a longer process.<br><br>I would appreciate if others w=
ill share their insight on the recommended usage and whether this issue sho=
uld or should not be addressed by TICTOC. <br><br>Here is the relevant text=
 from IEEE1588-2008 Annex D: &quot;For PTP event messages, the value of the=
 differentiated service (DS) field in the Type of Service (ToS)<br>field sh=
ould be set to the highest traffic class selector codepoint available.&quot=
; The PTP Telecom profile for frequency distribution, ITU-T G.8265.1, doesn=
't specify or recommend DSCP settings.<br><br>Best,<br>Ron<o:p></o:p></p></=
div></div></div></div></div></div><p class=3DMsoNormal><o:p>&nbsp;</o:p></p=
></div></div></body></html>=

--_000_2C2F1EBA8050E74EA81502D5740B4BD6A9327F9F90SJEXCHCCR02co_--


From peter.roberts@alcatel-lucent.com  Mon Aug  8 13:23:38 2011
Return-Path: <peter.roberts@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 C235821F8C3D for <tictoc@ietfa.amsl.com>; Mon,  8 Aug 2011 13:23:38 -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 qMGQljLsLQuS for <tictoc@ietfa.amsl.com>; Mon,  8 Aug 2011 13:23:37 -0700 (PDT)
Received: from ihemail2.lucent.com (ihemail2.lucent.com [135.245.0.35]) by ietfa.amsl.com (Postfix) with ESMTP id 9AD2321F8C3C for <tictoc@ietf.org>; Mon,  8 Aug 2011 13:23:37 -0700 (PDT)
Received: from usnavsmail1.ndc.alcatel-lucent.com (usnavsmail1.ndc.alcatel-lucent.com [135.3.39.9]) by ihemail2.lucent.com (8.13.8/IER-o) with ESMTP id p78KO257008567 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Mon, 8 Aug 2011 15:24:02 -0500 (CDT)
Received: from USNAVSXCHHUB03.ndc.alcatel-lucent.com (usnavsxchhub03.ndc.alcatel-lucent.com [135.3.39.112]) by usnavsmail1.ndc.alcatel-lucent.com (8.14.3/8.14.3/GMO) with ESMTP id p78KNuAo026535 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Mon, 8 Aug 2011 15:24:02 -0500
Received: from USNAVSXCHMBSC2.ndc.alcatel-lucent.com ([135.3.39.146]) by USNAVSXCHHUB03.ndc.alcatel-lucent.com ([135.3.39.112]) with mapi; Mon, 8 Aug 2011 15:23:58 -0500
From: "Roberts, Peter (Peter)" <peter.roberts@alcatel-lucent.com>
To: Shahram Davari <davari@broadcom.com>, Ron Cohen <ronc.ntear@gmail.com>
Date: Mon, 8 Aug 2011 15:23:58 -0500
Thread-Topic: [TICTOC] DSCP for PTP
Thread-Index: AcxWAzTLmUooYv5uR2ew4NWSxV/XvAAApC1wAACCDhA=
Message-ID: <CA2959F3E75BA645A43E81C3B071F6320AD2D1423D@USNAVSXCHMBSC2.ndc.alcatel-lucent.com>
References: <CALMYT9Qt7HAWA6mAe7m+58=_jQ68a0bhnNq97KFU22_4yf4xKA@mail.gmail.com> <2C2F1EBA8050E74EA81502D5740B4BD6A9327F9E2C@SJEXCHCCR02.corp.ad.broadcom.com> <CALMYT9Tp9OkCfPZvg=Op03QPhxQZ7d+724XsJLC=hFzMhExXdg@mail.gmail.com> <2C2F1EBA8050E74EA81502D5740B4BD6A9327F9F90@SJEXCHCCR02.corp.ad.broadcom.com>
In-Reply-To: <2C2F1EBA8050E74EA81502D5740B4BD6A9327F9F90@SJEXCHCCR02.corp.ad.broadcom.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: multipart/alternative; boundary="_000_CA2959F3E75BA645A43E81C3B071F6320AD2D1423DUSNAVSXCHMBSC_"
MIME-Version: 1.0
X-Scanned-By: MIMEDefang 2.57 on 135.245.2.35
X-Scanned-By: MIMEDefang 2.64 on 135.3.39.9
Cc: "tictoc@ietf.org" <tictoc@ietf.org>
Subject: Re: [TICTOC] DSCP for PTP
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, 08 Aug 2011 20:23:38 -0000

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

Ron,
The interference effects of the plesiochronous traffic can be mitigated by =
randomizing the generation of the 1588 packets.  Since the actual transmiss=
ion time is recorded in the timestamp, there is no requirement for exact pe=
riodicity to the 1588 packet generation (just the 30% accuracy requirement =
of the standard 7.7.2.1).

I agree with your statement on there being a difference between an environm=
ent with full on path support (every node a port based Timestamping capable=
 TC or BC) and an environment where this full support is not available.   B=
ut I think there will be enough of the second class of deployments to warra=
nt a recommendation on forwarding class.

Peter R.

________________________________
From: tictoc-bounces@ietf.org [mailto:tictoc-bounces@ietf.org] On Behalf Of=
 Shahram Davari
Sent: Monday, August 08, 2011 4:03 PM
To: Ron Cohen
Cc: tictoc@ietf.org
Subject: Re: [TICTOC] DSCP for PTP

Ron,

I have to look at this issue that you are raising. Do you have any referenc=
e for this effect?

In I theory one could have 2x EF PHB, with different DSCP code points, wher=
e one has higher priority than the other one.

Thx
Shahram

From: Ron Cohen [mailto:ronc.ntear@gmail.com]
Sent: Monday, August 08, 2011 12:41 PM
To: Shahram Davari
Cc: tictoc@ietf.org; manav.bhatia@alcatel-lucent.com
Subject: Re: [TICTOC] DSCP for PTP

Hi Shahram,

One possible drawback for using EF for PTP is that EF is also used by some =
video/voice and similar plesio-synchronous applications. The danger is that=
 the noise introduced by such application might be harder to filter than 'n=
ormal' packet based traffic. Therefore, it might be better to use another P=
HB, with even higher forwarding priority if possible, or maybe simply a dif=
ferent PHB altogether. It would be great if someone did a study on this and=
 can share the results with us.

We should also differentiate between the PTP-aware (TC/BC) or PTP-unaware c=
ases. In principle a TC doesn't need to send PTP messages with high forward=
ing priority as it compensates for the residence time anyhow.

Best,
Ron
On Mon, Aug 8, 2011 at 8:37 PM, Shahram Davari <davari@broadcom.com<mailto:=
davari@broadcom.com>> wrote:
Ron,

I agree with you that all PTP messages must configured with highest priorit=
y (a.k.a EF PHB) and EF should be the default. In fact I would also think i=
t is best to use L-LSP with EF PHB for 15880MPLS. If this is acceptable by =
the group then we could add this to the 1588oMPLS draft.


Regards,
Shahram

From: tictoc-bounces@ietf.org<mailto:tictoc-bounces@ietf.org> [mailto:ticto=
c-bounces@ietf.org<mailto:tictoc-bounces@ietf.org>] On Behalf Of Ron Cohen
Sent: Sunday, August 07, 2011 1:00 AM
To: tictoc@ietf.org<mailto:tictoc@ietf.org>
Subject: [TICTOC] DSCP for PTP

Hi,

Current standards do not recommend which DSCP values to set on PTP messages=
. As a result vendors have chosen different default values, and some vendor=
s also differentiate between the DSCP set on PTP Event messages (Sync, Dela=
y_Req, etc.) and PTP General messages (Announce, Follow_Up, Delay_Resp). I =
think TICTOC can help clarify the recommended DSCP usage, along the guideli=
nes of RFC4595, 'Configuration Guidelines for DiffServ Service Classes'.

In my opinion classifying PTP event and general messages into separate PHBs=
 is problematic as discard of Follow_Up would render its associated Sync me=
ssage useless. Forwarding of Sync messages in a higher priority queue compa=
red to Follow_Up may lead to Sync message getting ahead of the previous Fol=
low_Up message which again causes the slave to discard the previous Sync me=
ssage. Hence the first order recommendation in my opinion should be to use =
the same PHB (and DSCP marking) to all PTP messages.

Choosing one of the existing PHBs as the recommended one for PTP is somewha=
t harder. EF is a reasonable choice in my opinion, as per RFC4595 'The inte=
nt of Expedited Forwarding PHB [RFC3246] is to provide a building block for=
 low-loss, low-delay, and low-jitter services.' TICTOC could in principle r=
ecommend defining a new PHB tailored for PTP and similar services, but I gu=
ess this would be a longer process.

I would appreciate if others will share their insight on the recommended us=
age and whether this issue should or should not be addressed by TICTOC.

Here is the relevant text from IEEE1588-2008 Annex D: "For PTP event messag=
es, the value of the differentiated service (DS) field in the Type of Servi=
ce (ToS)
field should be set to the highest traffic class selector codepoint availab=
le." The PTP Telecom profile for frequency distribution, ITU-T G.8265.1, do=
esn't specify or recommend DSCP settings.

Best,
Ron


--_000_CA2959F3E75BA645A43E81C3B071F6320AD2D1423DUSNAVSXCHMBSC_
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:st=3D"&#1;" =
xmlns=3D"http://www.w3.org/TR/REC-html40"
xmlns:ns1=3D"http://schemas.microsoft.com/sharepoint/soap/workflow/"
xmlns:ns2=3D"http://schemas.microsoft.com/office/2006/digsig-setup"
xmlns:ns3=3D"http://schemas.microsoft.com/office/2006/digsig"
xmlns:ns4=3D"http://schemas.openxmlformats.org/package/2006/digital-signatu=
re"
xmlns:ns5=3D"http://schemas.openxmlformats.org/markup-compatibility/2006"
xmlns:ns6=3D"http://schemas.microsoft.com/office/2004/12/omml"
xmlns:ns7=3D"http://schemas.openxmlformats.org/package/2006/relationships"
xmlns:ns8=3D"http://microsoft.com/sharepoint/webpartpages"
xmlns:ns9=3D"http://schemas.microsoft.com/exchange/services/2006/types"
xmlns:ns10=3D"http://schemas.microsoft.com/exchange/services/2006/messages"
xmlns:ns11=3D"http://schemas.microsoft.com/sharepoint/soap/SlideLibrary/"
xmlns:ns12=3D"http://microsoft.com/webservices/SharePointPortalServer/Publi=
shedLinksService"
xmlns:ns13=3D"urn:schemas-microsoft-com:">

<head>
<meta http-equiv=3DContent-Type content=3D"text/html; charset=3Dus-ascii">
<meta name=3DGenerator content=3D"Microsoft Word 11 (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>
<!--a:link
	{mso-style-priority:99;}
span.MSOHYPERLINK
	{mso-style-priority:99;}
a:visited
	{mso-style-priority:99;}
span.MSOHYPERLINKFOLLOWED
	{mso-style-priority:99;}

 /* Font Definitions */
 @font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:"TimesNewRoman\,Bold";
	panose-1:0 0 0 0 0 0 0 0 0 0;}
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman";}
a:link, span.MsoHyperlink
	{color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{color:purple;
	text-decoration:underline;}
span.EmailStyle17
	{mso-style-type:personal;
	font-family:Calibri;
	color:#1F497D;}
span.EmailStyle18
	{mso-style-type:personal-reply;
	font-family:Arial;
	color:navy;}
@page Section1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.Section1
	{page:Section1;}
-->
</style>
<!--[if gte mso 9]><xml>
 <o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
 <o:shapelayout v:ext=3D"edit">
  <o:idmap v:ext=3D"edit" data=3D"1" />
 </o:shapelayout></xml><![endif]-->
</head>

<body lang=3DEN-US link=3Dblue vlink=3Dpurple>

<div class=3DSection1>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span style=
=3D'font-size:
10.0pt;font-family:Arial;color:navy'>Ron,<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span style=
=3D'font-size:
10.0pt;font-family:Arial;color:navy'>The interference effects of the plesio=
chronous
traffic can be mitigated by randomizing the generation of the 1588 packets.=
 &nbsp;Since
the actual transmission time is recorded in the timestamp, there is no
requirement for exact periodicity to the 1588 packet generation (just the 3=
0%
accuracy requirement of the standard </span></font><b><font size=3D2
face=3D"TimesNewRoman,Bold"><span style=3D'font-size:10.0pt;font-family:"Ti=
mesNewRoman\,Bold";
font-weight:bold'>7.7.2.1</span></font></b><font size=3D2 color=3Dnavy face=
=3DArial><span
style=3D'font-size:10.0pt;font-family:Arial;color:navy'>).<o:p></o:p></span=
></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span style=
=3D'font-size:
10.0pt;font-family:Arial;color:navy'><o:p>&nbsp;</o:p></span></font></p>

<div>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span style=
=3D'font-size:
10.0pt;font-family:Arial;color:navy'>I agree with your statement on there b=
eing
a difference between an environment with full on path support (every node a=
 port
based Timestamping capable TC or BC) and an environment where this full sup=
port
is not available. &nbsp;&nbsp;But I think there will be enough of the secon=
d
class of deployments to warrant a recommendation on forwarding class.<o:p><=
/o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span style=
=3D'font-size:
10.0pt;font-family:Arial;color:navy'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span style=
=3D'font-size:
10.0pt;font-family:Arial;color:navy'>Peter R.<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span style=3D=
'font-size:
12.0pt'><o:p>&nbsp;</o:p></span></font></p>

<div class=3DMsoNormal align=3Dcenter style=3D'text-align:center'><font siz=
e=3D3
face=3D"Times New Roman"><span style=3D'font-size:12.0pt'>

<hr size=3D2 width=3D"100%" align=3Dcenter tabindex=3D-1>

</span></font></div>

<p class=3DMsoNormal><b><font size=3D2 face=3DTahoma><span style=3D'font-si=
ze:10.0pt;
font-family:Tahoma;font-weight:bold'>From:</span></font></b><font size=3D2
face=3DTahoma><span style=3D'font-size:10.0pt;font-family:Tahoma'>
tictoc-bounces@ietf.org [mailto:tictoc-bounces@ietf.org] <b><span
style=3D'font-weight:bold'>On Behalf Of </span></b>Shahram Davari<br>
<b><span style=3D'font-weight:bold'>Sent:</span></b> Monday, August 08, 201=
1 4:03
PM<br>
<b><span style=3D'font-weight:bold'>To:</span></b> Ron Cohen<br>
<b><span style=3D'font-weight:bold'>Cc:</span></b> tictoc@ietf.org<br>
<b><span style=3D'font-weight:bold'>Subject:</span></b> Re: [TICTOC] DSCP f=
or PTP</span></font><o:p></o:p></p>

</div>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span style=3D=
'font-size:
12.0pt'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3D"#1f497d" face=3DCalibri><span
style=3D'font-size:11.0pt;font-family:Calibri;color:#1F497D'>Ron,<o:p></o:p=
></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3D"#1f497d" face=3DCalibri><span
style=3D'font-size:11.0pt;font-family:Calibri;color:#1F497D'><o:p>&nbsp;</o=
:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3D"#1f497d" face=3DCalibri><span
style=3D'font-size:11.0pt;font-family:Calibri;color:#1F497D'>I have to look=
 at
this issue that you are raising. Do you have any reference for this effect?=
 <o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3D"#1f497d" face=3DCalibri><span
style=3D'font-size:11.0pt;font-family:Calibri;color:#1F497D'><o:p>&nbsp;</o=
:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3D"#1f497d" face=3DCalibri><span
style=3D'font-size:11.0pt;font-family:Calibri;color:#1F497D'>In I theory on=
e
could have 2x EF PHB, with different DSCP code points, where one has higher
priority than the other one.<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3D"#1f497d" face=3DCalibri><span
style=3D'font-size:11.0pt;font-family:Calibri;color:#1F497D'><o:p>&nbsp;</o=
:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3D"#1f497d" face=3DCalibri><span
style=3D'font-size:11.0pt;font-family:Calibri;color:#1F497D'>Thx<br>
Shahram<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3D"#1f497d" face=3DCalibri><span
style=3D'font-size:11.0pt;font-family:Calibri;color:#1F497D'><o:p>&nbsp;</o=
:p></span></font></p>

<div style=3D'border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in =
0in 0in'>

<p class=3DMsoNormal><b><font size=3D2 face=3DTahoma><span style=3D'font-si=
ze:10.0pt;
font-family:Tahoma;font-weight:bold'>From:</span></font></b><font size=3D2
face=3DTahoma><span style=3D'font-size:10.0pt;font-family:Tahoma'> Ron Cohe=
n
[mailto:ronc.ntear@gmail.com] <br>
<b><span style=3D'font-weight:bold'>Sent:</span></b> Monday, August 08, 201=
1
12:41 PM<br>
<b><span style=3D'font-weight:bold'>To:</span></b> Shahram Davari<br>
<b><span style=3D'font-weight:bold'>Cc:</span></b> tictoc@ietf.org;
manav.bhatia@alcatel-lucent.com<br>
<b><span style=3D'font-weight:bold'>Subject:</span></b> Re: [TICTOC] DSCP f=
or PTP<o:p></o:p></span></font></p>

</div>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span style=3D=
'font-size:
12.0pt'><o:p>&nbsp;</o:p></span></font></p>

<div>

<p class=3DMsoNormal style=3D'margin-bottom:12.0pt'><font size=3D3
face=3D"Times New Roman"><span style=3D'font-size:12.0pt'>Hi Shahram,<br>
<br>
One possible drawback for using EF for PTP is that EF is also used by some
video/voice and similar plesio-synchronous applications. The danger is that=
 the
noise introduced by such application might be harder to filter than 'normal=
'
packet based traffic. Therefore, it might be better to use another PHB, wit=
h
even higher forwarding priority if possible, or maybe simply a different PH=
B
altogether. It would be great if someone did a study on this and can share =
the
results with us. <br>
<br>
We should also differentiate between the PTP-aware (TC/BC) or PTP-unaware
cases. In principle a TC doesn't need to send PTP messages with high forwar=
ding
priority as it compensates for the residence time anyhow. <br>
<br>
Best,<br>
Ron&nbsp; <o:p></o:p></span></font></p>

<div>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span style=3D=
'font-size:
12.0pt'>On Mon, Aug 8, 2011 at 8:37 PM, Shahram Davari &lt;<a
href=3D"mailto:davari@broadcom.com">davari@broadcom.com</a>&gt; wrote:<o:p>=
</o:p></span></font></p>

<div>

<div>

<p class=3DMsoNormal style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt=
:auto'><font
size=3D2 color=3D"#1f497d" face=3D"Times New Roman"><span style=3D'font-siz=
e:11.0pt;
color:#1F497D'>Ron,</span></font><o:p></o:p></p>

<p class=3DMsoNormal style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt=
:auto'><font
size=3D2 color=3D"#1f497d" face=3D"Times New Roman"><span style=3D'font-siz=
e:11.0pt;
color:#1F497D'>&nbsp;</span></font><o:p></o:p></p>

<p class=3DMsoNormal style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt=
:auto'><font
size=3D2 color=3D"#1f497d" face=3D"Times New Roman"><span style=3D'font-siz=
e:11.0pt;
color:#1F497D'>I agree with you that all PTP messages must configured with
highest priority (a.k.a EF PHB) and EF should be the default. In fact I wou=
ld
also think it is best to use L-LSP with EF PHB for 15880MPLS. If this is
acceptable by the group then we could add this to the 1588oMPLS draft.</spa=
n></font><o:p></o:p></p>

<p class=3DMsoNormal style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt=
:auto'><font
size=3D2 color=3D"#1f497d" face=3D"Times New Roman"><span style=3D'font-siz=
e:11.0pt;
color:#1F497D'>&nbsp;</span></font><o:p></o:p></p>

<p class=3DMsoNormal style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt=
:auto'><font
size=3D2 color=3D"#1f497d" face=3D"Times New Roman"><span style=3D'font-siz=
e:11.0pt;
color:#1F497D'>&nbsp;</span></font><o:p></o:p></p>

<p class=3DMsoNormal style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt=
:auto'><font
size=3D2 color=3D"#1f497d" face=3D"Times New Roman"><span style=3D'font-siz=
e:11.0pt;
color:#1F497D'>Regards,</span></font><o:p></o:p></p>

<p class=3DMsoNormal style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt=
:auto'><font
size=3D2 color=3D"#1f497d" face=3D"Times New Roman"><span style=3D'font-siz=
e:11.0pt;
color:#1F497D'>Shahram</span></font><o:p></o:p></p>

<p class=3DMsoNormal style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt=
:auto'><font
size=3D2 color=3D"#1f497d" face=3D"Times New Roman"><span style=3D'font-siz=
e:11.0pt;
color:#1F497D'>&nbsp;</span></font><o:p></o:p></p>

<div style=3D'border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in =
0in 0in'>

<p class=3DMsoNormal style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt=
:auto'><b><font
size=3D2 face=3D"Times New Roman"><span style=3D'font-size:10.0pt;font-weig=
ht:bold'>From:</span></font></b><font
size=3D2><span style=3D'font-size:10.0pt'> <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@ie=
tf.org</a>]
<b><span style=3D'font-weight:bold'>On Behalf Of </span></b>Ron Cohen<br>
<b><span style=3D'font-weight:bold'>Sent:</span></b> Sunday, August 07, 201=
1 1:00
AM<br>
<b><span style=3D'font-weight:bold'>To:</span></b> <a
href=3D"mailto:tictoc@ietf.org" target=3D"_blank">tictoc@ietf.org</a><br>
<b><span style=3D'font-weight:bold'>Subject:</span></b> [TICTOC] DSCP for P=
TP</span></font><o:p></o:p></p>

</div>

<div>

<div>

<p class=3DMsoNormal style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt=
:auto'><font
size=3D3 face=3D"Times New Roman"><span style=3D'font-size:12.0pt'>&nbsp;<o=
:p></o:p></span></font></p>

<div>

<p class=3DMsoNormal style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt=
:auto'><font
size=3D3 face=3D"Times New Roman"><span style=3D'font-size:12.0pt'>Hi,<br>
<br>
Current standards do not recommend which DSCP values to set on PTP messages=
. As
a result vendors have chosen different default values, and some vendors als=
o
differentiate between the DSCP set on PTP Event messages (Sync, Delay_Req,
etc.) and PTP General messages (Announce, Follow_Up, Delay_Resp). I think
TICTOC can help clarify the recommended DSCP usage, along the guidelines of
RFC4595, 'Configuration Guidelines for DiffServ Service Classes'.<br>
<br>
In my opinion classifying PTP event and general messages into separate PHBs=
 is
problematic as discard of Follow_Up would render its associated Sync messag=
e
useless. Forwarding of Sync messages in a higher priority queue compared to
Follow_Up may lead to Sync message getting ahead of the previous Follow_Up
message which again causes the slave to discard the previous Sync message.
Hence the first order recommendation in my opinion should be to use the sam=
e
PHB (and DSCP marking) to all PTP messages. <br>
<br>
Choosing one of the existing PHBs as the recommended one for PTP is somewha=
t
harder. EF is a reasonable choice in my opinion, as per RFC4595 'The intent=
 of
Expedited Forwarding PHB [RFC3246] is to provide a building block for low-l=
oss,
low-delay, and low-jitter services.' TICTOC could in principle recommend
defining a new PHB tailored for PTP and similar services, but I guess this
would be a longer process.<br>
<br>
I would appreciate if others will share their insight on the recommended us=
age
and whether this issue should or should not be addressed by TICTOC. <br>
<br>
Here is the relevant text from IEEE1588-2008 Annex D: &quot;For PTP event
messages, the value of the differentiated service (DS) field in the Type of
Service (ToS)<br>
field should be set to the highest traffic class selector codepoint
available.&quot; The PTP Telecom profile for frequency distribution, ITU-T
G.8265.1, doesn't specify or recommend DSCP settings.<br>
<br>
Best,<br>
Ron<o:p></o:p></span></font></p>

</div>

</div>

</div>

</div>

</div>

</div>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span style=3D=
'font-size:
12.0pt'><o:p>&nbsp;</o:p></span></font></p>

</div>

</div>

</body>

</html>

--_000_CA2959F3E75BA645A43E81C3B071F6320AD2D1423DUSNAVSXCHMBSC_--

From ronc.ntear@gmail.com  Mon Aug  8 14:02:54 2011
Return-Path: <ronc.ntear@gmail.com>
X-Original-To: tictoc@ietfa.amsl.com
Delivered-To: tictoc@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 15F6911E80AE for <tictoc@ietfa.amsl.com>; Mon,  8 Aug 2011 14:02:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.598
X-Spam-Level: 
X-Spam-Status: No, score=-3.598 tagged_above=-999 required=5 tests=[AWL=-0.000, BAYES_00=-2.599, HTML_MESSAGE=0.001, 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 46RjlhydFrMj for <tictoc@ietfa.amsl.com>; Mon,  8 Aug 2011 14:02:53 -0700 (PDT)
Received: from mail-gx0-f172.google.com (mail-gx0-f172.google.com [209.85.161.172]) by ietfa.amsl.com (Postfix) with ESMTP id BABB621F8C0C for <tictoc@ietf.org>; Mon,  8 Aug 2011 14:02:52 -0700 (PDT)
Received: by gxk19 with SMTP id 19so1231164gxk.31 for <tictoc@ietf.org>; Mon, 08 Aug 2011 14:03:18 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=CqGJJvl3eeTtzf851o4rsrfDoPZ/xh1W3vjDMFIBYbo=; b=izFt8yhKi1rL5bna6KiM9VLJotBFN8YwWX+voaBPmI06ClBXWSCmgudJDJ2nHijNUw 52tymECgzlmnsBaHKCJBPNYp4B9Fzv7+N4njExPg32smWinSlSZvHHGfGTfoyx5iQe+b B3LMTVEfzJgqw20CqdFFb1a5XHnfbdBwHuDIc=
MIME-Version: 1.0
Received: by 10.147.136.19 with SMTP id o19mr3387601yan.38.1312837398023; Mon, 08 Aug 2011 14:03:18 -0700 (PDT)
Received: by 10.147.114.4 with HTTP; Mon, 8 Aug 2011 14:03:17 -0700 (PDT)
In-Reply-To: <CA2959F3E75BA645A43E81C3B071F6320AD2D1423D@USNAVSXCHMBSC2.ndc.alcatel-lucent.com>
References: <CALMYT9Qt7HAWA6mAe7m+58=_jQ68a0bhnNq97KFU22_4yf4xKA@mail.gmail.com> <2C2F1EBA8050E74EA81502D5740B4BD6A9327F9E2C@SJEXCHCCR02.corp.ad.broadcom.com> <CALMYT9Tp9OkCfPZvg=Op03QPhxQZ7d+724XsJLC=hFzMhExXdg@mail.gmail.com> <2C2F1EBA8050E74EA81502D5740B4BD6A9327F9F90@SJEXCHCCR02.corp.ad.broadcom.com> <CA2959F3E75BA645A43E81C3B071F6320AD2D1423D@USNAVSXCHMBSC2.ndc.alcatel-lucent.com>
Date: Tue, 9 Aug 2011 00:03:17 +0300
Message-ID: <CALMYT9TN3GokVKqHJfYKT0_FgU-+Nm+hjo_OS_7u=7QHRRj4pQ@mail.gmail.com>
From: Ron Cohen <ronc.ntear@gmail.com>
To: "Roberts, Peter (Peter)" <peter.roberts@alcatel-lucent.com>
Content-Type: multipart/alternative; boundary=20cf3054a0fdc1d06f04aa04c647
Cc: "tictoc@ietf.org" <tictoc@ietf.org>
Subject: Re: [TICTOC] DSCP for PTP
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, 08 Aug 2011 21:02:54 -0000

--20cf3054a0fdc1d06f04aa04c647
Content-Type: text/plain; charset=ISO-8859-1

Hi Peter,

You are right that randomization should take care of this effect, at least
theoretically. However I looked carefully at IEEE1588-2008 and the standard
does not require randomization of Sync messages, rather it requires
randomization of Delay_Req messages (which makes sense when working in
multicast). ITU-T G.8265.1 doesn't add any randomization requirement. Hence
randomization of Sync messages is a good option to implement, but not a
standard one. Note also that wide-enough randomization (e.g. uniform
distribution half-interval wide) may not be that easy to implement in
masters that support multiple (sometimes hundreds) of slaves.

Best,
Ron



On Mon, Aug 8, 2011 at 11:23 PM, Roberts, Peter (Peter) <
peter.roberts@alcatel-lucent.com> wrote:

>  Ron,****
>
> The interference effects of the plesiochronous traffic can be mitigated by
> randomizing the generation of the 1588 packets.  Since the actual
> transmission time is recorded in the timestamp, there is no requirement for
> exact periodicity to the 1588 packet generation (just the 30% accuracy
> requirement of the standard *7.7.2.1*).****
>
> ** **
>
> I agree with your statement on there being a difference between an
> environment with full on path support (every node a port based Timestamping
> capable TC or BC) and an environment where this full support is not
> available.   But I think there will be enough of the second class of
> deployments to warrant a recommendation on forwarding class.****
>
> ** **
>
> Peter R.****
>
> ** **
>  ------------------------------
>
> *From:* tictoc-bounces@ietf.org [mailto:tictoc-bounces@ietf.org] *On
> Behalf Of *Shahram Davari
> *Sent:* Monday, August 08, 2011 4:03 PM
>
> *To:* Ron Cohen
> *Cc:* tictoc@ietf.org
> *Subject:* Re: [TICTOC] DSCP for PTP
> ****
>
>  ** **
>
> Ron,****
>
> ** **
>
> I have to look at this issue that you are raising. Do you have any
> reference for this effect? ****
>
> ** **
>
> In I theory one could have 2x EF PHB, with different DSCP code points,
> where one has higher priority than the other one.****
>
> ** **
>
> Thx
> Shahram****
>
> ** **
>
> *From:* Ron Cohen [mailto:ronc.ntear@gmail.com]
> *Sent:* Monday, August 08, 2011 12:41 PM
> *To:* Shahram Davari
> *Cc:* tictoc@ietf.org; manav.bhatia@alcatel-lucent.com
> *Subject:* Re: [TICTOC] DSCP for PTP****
>
> ** **
>
> Hi Shahram,
>
> One possible drawback for using EF for PTP is that EF is also used by some
> video/voice and similar plesio-synchronous applications. The danger is that
> the noise introduced by such application might be harder to filter than
> 'normal' packet based traffic. Therefore, it might be better to use another
> PHB, with even higher forwarding priority if possible, or maybe simply a
> different PHB altogether. It would be great if someone did a study on this
> and can share the results with us.
>
> We should also differentiate between the PTP-aware (TC/BC) or PTP-unaware
> cases. In principle a TC doesn't need to send PTP messages with high
> forwarding priority as it compensates for the residence time anyhow.
>
> Best,
> Ron  ****
>
> On Mon, Aug 8, 2011 at 8:37 PM, Shahram Davari <davari@broadcom.com>
> wrote:****
>
> Ron,****
>
>  ****
>
> I agree with you that all PTP messages must configured with highest
> priority (a.k.a EF PHB) and EF should be the default. In fact I would also
> think it is best to use L-LSP with EF PHB for 15880MPLS. If this is
> acceptable by the group then we could add this to the 1588oMPLS draft.****
>
>  ****
>
>  ****
>
> Regards,****
>
> Shahram****
>
>  ****
>
> *From:* tictoc-bounces@ietf.org [mailto:tictoc-bounces@ietf.org] *On
> Behalf Of *Ron Cohen
> *Sent:* Sunday, August 07, 2011 1:00 AM
> *To:* tictoc@ietf.org
> *Subject:* [TICTOC] DSCP for PTP****
>
>  ****
>
> Hi,
>
> Current standards do not recommend which DSCP values to set on PTP
> messages. As a result vendors have chosen different default values, and some
> vendors also differentiate between the DSCP set on PTP Event messages (Sync,
> Delay_Req, etc.) and PTP General messages (Announce, Follow_Up, Delay_Resp).
> I think TICTOC can help clarify the recommended DSCP usage, along the
> guidelines of RFC4595, 'Configuration Guidelines for DiffServ Service
> Classes'.
>
> In my opinion classifying PTP event and general messages into separate PHBs
> is problematic as discard of Follow_Up would render its associated Sync
> message useless. Forwarding of Sync messages in a higher priority queue
> compared to Follow_Up may lead to Sync message getting ahead of the previous
> Follow_Up message which again causes the slave to discard the previous Sync
> message. Hence the first order recommendation in my opinion should be to use
> the same PHB (and DSCP marking) to all PTP messages.
>
> Choosing one of the existing PHBs as the recommended one for PTP is
> somewhat harder. EF is a reasonable choice in my opinion, as per RFC4595
> 'The intent of Expedited Forwarding PHB [RFC3246] is to provide a building
> block for low-loss, low-delay, and low-jitter services.' TICTOC could in
> principle recommend defining a new PHB tailored for PTP and similar
> services, but I guess this would be a longer process.
>
> I would appreciate if others will share their insight on the recommended
> usage and whether this issue should or should not be addressed by TICTOC.
>
> Here is the relevant text from IEEE1588-2008 Annex D: "For PTP event
> messages, the value of the differentiated service (DS) field in the Type of
> Service (ToS)
> field should be set to the highest traffic class selector codepoint
> available." The PTP Telecom profile for frequency distribution, ITU-T
> G.8265.1, doesn't specify or recommend DSCP settings.
>
> Best,
> Ron****
>
> ** **
>

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

<div dir=3D"ltr">Hi Peter,<br><br>You are right that randomization should t=
ake care of this effect, at least theoretically. However I looked carefully=
 at IEEE1588-2008 and the standard does not require randomization of Sync m=
essages, rather it requires randomization of Delay_Req messages (which make=
s sense when working in multicast). ITU-T G.8265.1 doesn&#39;t add any rand=
omization requirement. Hence randomization of Sync messages is a good optio=
n to implement, but not a standard one. Note also that wide-enough randomiz=
ation (e.g. uniform distribution half-interval wide) may not be that easy t=
o implement in masters that support multiple (sometimes hundreds) of slaves=
.<br>
<br>Best,<br>Ron<br><br><br><br><div class=3D"gmail_quote">On Mon, Aug 8, 2=
011 at 11:23 PM, Roberts, Peter (Peter) <span dir=3D"ltr">&lt;<a href=3D"ma=
ilto:peter.roberts@alcatel-lucent.com">peter.roberts@alcatel-lucent.com</a>=
&gt;</span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex;">









<div link=3D"blue" vlink=3D"purple" lang=3D"EN-US">

<div>

<p class=3D"MsoNormal"><font size=3D"2" color=3D"navy" face=3D"Arial"><span=
 style=3D"font-size:10.0pt;font-family:Arial;color:navy">Ron,<u></u><u></u>=
</span></font></p>

<p class=3D"MsoNormal"><font size=3D"2" color=3D"navy" face=3D"Arial"><span=
 style=3D"font-size:10.0pt;font-family:Arial;color:navy">The interference e=
ffects of the plesiochronous
traffic can be mitigated by randomizing the generation of the 1588 packets.=
 =A0Since
the actual transmission time is recorded in the timestamp, there is no
requirement for exact periodicity to the 1588 packet generation (just the 3=
0%
accuracy requirement of the standard </span></font><b><font size=3D"2" face=
=3D"TimesNewRoman,Bold"><span style=3D"font-size:10.0pt;font-weight:bold">7=
.7.2.1</span></font></b><font size=3D"2" color=3D"navy" face=3D"Arial"><spa=
n style=3D"font-size:10.0pt;font-family:Arial;color:navy">).<u></u><u></u><=
/span></font></p>


<p class=3D"MsoNormal"><font size=3D"2" color=3D"navy" face=3D"Arial"><span=
 style=3D"font-size:10.0pt;font-family:Arial;color:navy"><u></u>=A0<u></u><=
/span></font></p>

<div>

<p class=3D"MsoNormal"><font size=3D"2" color=3D"navy" face=3D"Arial"><span=
 style=3D"font-size:10.0pt;font-family:Arial;color:navy">I agree with your =
statement on there being
a difference between an environment with full on path support (every node a=
 port
based Timestamping capable TC or BC) and an environment where this full sup=
port
is not available. =A0=A0But I think there will be enough of the second
class of deployments to warrant a recommendation on forwarding class.<u></u=
><u></u></span></font></p>

<p class=3D"MsoNormal"><font size=3D"2" color=3D"navy" face=3D"Arial"><span=
 style=3D"font-size:10.0pt;font-family:Arial;color:navy"><u></u>=A0<u></u><=
/span></font></p>

<p class=3D"MsoNormal"><font size=3D"2" color=3D"navy" face=3D"Arial"><span=
 style=3D"font-size:10.0pt;font-family:Arial;color:navy">Peter R.<u></u><u>=
</u></span></font></p>

<p class=3D"MsoNormal"><font size=3D"3" face=3D"Times New Roman"><span styl=
e=3D"font-size:12.0pt"><u></u>=A0<u></u></span></font></p>

<div class=3D"MsoNormal" style=3D"text-align:center" align=3D"center"><font=
 size=3D"3" face=3D"Times New Roman"><span style=3D"font-size:12.0pt">

<hr size=3D"2" width=3D"100%" align=3D"center">

</span></font></div>

<p class=3D"MsoNormal"><b><font size=3D"2" face=3D"Tahoma"><span style=3D"f=
ont-size:10.0pt;font-family:Tahoma;font-weight:bold">From:</span></font></b=
><font size=3D"2" face=3D"Tahoma"><span style=3D"font-size:10.0pt;font-fami=
ly:Tahoma">
<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><span style=3D"font-weight:bold">On=
 Behalf Of </span></b>Shahram Davari<br>

<b><span style=3D"font-weight:bold">Sent:</span></b> Monday, August 08, 201=
1 4:03
PM</span></font></p><div class=3D"im"><font size=3D"2" face=3D"Tahoma"><br>
<b><span style=3D"font-weight:bold">To:</span></b> Ron Cohen<br>
<b><span style=3D"font-weight:bold">Cc:</span></b> <a href=3D"mailto:tictoc=
@ietf.org" target=3D"_blank">tictoc@ietf.org</a><br>
</font></div><div><div><font size=3D"2" face=3D"Tahoma"></font></div><div c=
lass=3D"h5"><font size=3D"2" face=3D"Tahoma"><b><span style=3D"font-weight:=
bold">Subject:</span></b> Re: [TICTOC] DSCP for PTP</font></div></div><u></=
u><u></u><p>
</p>

</div><div><div></div><div class=3D"h5">

<p class=3D"MsoNormal"><font size=3D"3" face=3D"Times New Roman"><span styl=
e=3D"font-size:12.0pt"><u></u>=A0<u></u></span></font></p>

<p class=3D"MsoNormal"><font size=3D"2" color=3D"#1f497d" face=3D"Calibri">=
<span style=3D"font-size:11.0pt;font-family:Calibri;color:#1F497D">Ron,<u><=
/u><u></u></span></font></p>

<p class=3D"MsoNormal"><font size=3D"2" color=3D"#1f497d" face=3D"Calibri">=
<span style=3D"font-size:11.0pt;font-family:Calibri;color:#1F497D"><u></u>=
=A0<u></u></span></font></p>

<p class=3D"MsoNormal"><font size=3D"2" color=3D"#1f497d" face=3D"Calibri">=
<span style=3D"font-size:11.0pt;font-family:Calibri;color:#1F497D">I have t=
o look at
this issue that you are raising. Do you have any reference for this effect?=
 <u></u><u></u></span></font></p>

<p class=3D"MsoNormal"><font size=3D"2" color=3D"#1f497d" face=3D"Calibri">=
<span style=3D"font-size:11.0pt;font-family:Calibri;color:#1F497D"><u></u>=
=A0<u></u></span></font></p>

<p class=3D"MsoNormal"><font size=3D"2" color=3D"#1f497d" face=3D"Calibri">=
<span style=3D"font-size:11.0pt;font-family:Calibri;color:#1F497D">In I the=
ory one
could have 2x EF PHB, with different DSCP code points, where one has higher
priority than the other one.<u></u><u></u></span></font></p>

<p class=3D"MsoNormal"><font size=3D"2" color=3D"#1f497d" face=3D"Calibri">=
<span style=3D"font-size:11.0pt;font-family:Calibri;color:#1F497D"><u></u>=
=A0<u></u></span></font></p>

<p class=3D"MsoNormal"><font size=3D"2" color=3D"#1f497d" face=3D"Calibri">=
<span style=3D"font-size:11.0pt;font-family:Calibri;color:#1F497D">Thx<br>
Shahram<u></u><u></u></span></font></p>

<p class=3D"MsoNormal"><font size=3D"2" color=3D"#1f497d" face=3D"Calibri">=
<span style=3D"font-size:11.0pt;font-family:Calibri;color:#1F497D"><u></u>=
=A0<u></u></span></font></p>

<div style=3D"border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in =
0in 0in">

<p class=3D"MsoNormal"><b><font size=3D"2" face=3D"Tahoma"><span style=3D"f=
ont-size:10.0pt;font-family:Tahoma;font-weight:bold">From:</span></font></b=
><font size=3D"2" face=3D"Tahoma"><span style=3D"font-size:10.0pt;font-fami=
ly:Tahoma"> Ron Cohen
[mailto:<a href=3D"mailto:ronc.ntear@gmail.com" target=3D"_blank">ronc.ntea=
r@gmail.com</a>] <br>
<b><span style=3D"font-weight:bold">Sent:</span></b> Monday, August 08, 201=
1
12:41 PM<br>
<b><span style=3D"font-weight:bold">To:</span></b> Shahram Davari<br>
<b><span style=3D"font-weight:bold">Cc:</span></b> <a href=3D"mailto:tictoc=
@ietf.org" target=3D"_blank">tictoc@ietf.org</a>;
<a href=3D"mailto:manav.bhatia@alcatel-lucent.com" target=3D"_blank">manav.=
bhatia@alcatel-lucent.com</a><br>
<b><span style=3D"font-weight:bold">Subject:</span></b> Re: [TICTOC] DSCP f=
or PTP<u></u><u></u></span></font></p>

</div>

<p class=3D"MsoNormal"><font size=3D"3" face=3D"Times New Roman"><span styl=
e=3D"font-size:12.0pt"><u></u>=A0<u></u></span></font></p>

<div>

<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt"><font size=3D"3" face=
=3D"Times New Roman"><span style=3D"font-size:12.0pt">Hi Shahram,<br>
<br>
One possible drawback for using EF for PTP is that EF is also used by some
video/voice and similar plesio-synchronous applications. The danger is that=
 the
noise introduced by such application might be harder to filter than &#39;no=
rmal&#39;
packet based traffic. Therefore, it might be better to use another PHB, wit=
h
even higher forwarding priority if possible, or maybe simply a different PH=
B
altogether. It would be great if someone did a study on this and can share =
the
results with us. <br>
<br>
We should also differentiate between the PTP-aware (TC/BC) or PTP-unaware
cases. In principle a TC doesn&#39;t need to send PTP messages with high fo=
rwarding
priority as it compensates for the residence time anyhow. <br>
<br>
Best,<br>
Ron=A0 <u></u><u></u></span></font></p>

<div>

<p class=3D"MsoNormal"><font size=3D"3" face=3D"Times New Roman"><span styl=
e=3D"font-size:12.0pt">On Mon, Aug 8, 2011 at 8:37 PM, Shahram Davari &lt;<=
a href=3D"mailto:davari@broadcom.com" target=3D"_blank">davari@broadcom.com=
</a>&gt; wrote:<u></u><u></u></span></font></p>


<div>

<div>

<p class=3D"MsoNormal"><font size=3D"2" color=3D"#1f497d" face=3D"Times New=
 Roman"><span style=3D"font-size:11.0pt;color:#1F497D">Ron,</span></font><u=
></u><u></u></p>

<p class=3D"MsoNormal"><font size=3D"2" color=3D"#1f497d" face=3D"Times New=
 Roman"><span style=3D"font-size:11.0pt;color:#1F497D">=A0</span></font><u>=
</u><u></u></p>

<p class=3D"MsoNormal"><font size=3D"2" color=3D"#1f497d" face=3D"Times New=
 Roman"><span style=3D"font-size:11.0pt;color:#1F497D">I agree with you tha=
t all PTP messages must configured with
highest priority (a.k.a EF PHB) and EF should be the default. In fact I wou=
ld
also think it is best to use L-LSP with EF PHB for 15880MPLS. If this is
acceptable by the group then we could add this to the 1588oMPLS draft.</spa=
n></font><u></u><u></u></p>

<p class=3D"MsoNormal"><font size=3D"2" color=3D"#1f497d" face=3D"Times New=
 Roman"><span style=3D"font-size:11.0pt;color:#1F497D">=A0</span></font><u>=
</u><u></u></p>

<p class=3D"MsoNormal"><font size=3D"2" color=3D"#1f497d" face=3D"Times New=
 Roman"><span style=3D"font-size:11.0pt;color:#1F497D">=A0</span></font><u>=
</u><u></u></p>

<p class=3D"MsoNormal"><font size=3D"2" color=3D"#1f497d" face=3D"Times New=
 Roman"><span style=3D"font-size:11.0pt;color:#1F497D">Regards,</span></fon=
t><u></u><u></u></p>

<p class=3D"MsoNormal"><font size=3D"2" color=3D"#1f497d" face=3D"Times New=
 Roman"><span style=3D"font-size:11.0pt;color:#1F497D">Shahram</span></font=
><u></u><u></u></p>

<p class=3D"MsoNormal"><font size=3D"2" color=3D"#1f497d" face=3D"Times New=
 Roman"><span style=3D"font-size:11.0pt;color:#1F497D">=A0</span></font><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><font size=3D"2" face=3D"Times New Roman"><span s=
tyle=3D"font-size:10.0pt;font-weight:bold">From:</span></font></b><font siz=
e=3D"2"><span style=3D"font-size:10.0pt"> <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><span style=3D"font-weight:bold">On Behalf Of </span></b>Ron Cohen<br>
<b><span style=3D"font-weight:bold">Sent:</span></b> Sunday, August 07, 201=
1 1:00
AM<br>
<b><span style=3D"font-weight:bold">To:</span></b> <a href=3D"mailto:tictoc=
@ietf.org" target=3D"_blank">tictoc@ietf.org</a><br>
<b><span style=3D"font-weight:bold">Subject:</span></b> [TICTOC] DSCP for P=
TP</span></font><u></u><u></u></p>

</div>

<div>

<div>

<p class=3D"MsoNormal"><font size=3D"3" face=3D"Times New Roman"><span styl=
e=3D"font-size:12.0pt">=A0<u></u><u></u></span></font></p>

<div>

<p class=3D"MsoNormal"><font size=3D"3" face=3D"Times New Roman"><span styl=
e=3D"font-size:12.0pt">Hi,<br>
<br>
Current standards do not recommend which DSCP values to set on PTP messages=
. As
a result vendors have chosen different default values, and some vendors als=
o
differentiate between the DSCP set on PTP Event messages (Sync, Delay_Req,
etc.) and PTP General messages (Announce, Follow_Up, Delay_Resp). I think
TICTOC can help clarify the recommended DSCP usage, along the guidelines of
RFC4595, &#39;Configuration Guidelines for DiffServ Service Classes&#39;.<b=
r>
<br>
In my opinion classifying PTP event and general messages into separate PHBs=
 is
problematic as discard of Follow_Up would render its associated Sync messag=
e
useless. Forwarding of Sync messages in a higher priority queue compared to
Follow_Up may lead to Sync message getting ahead of the previous Follow_Up
message which again causes the slave to discard the previous Sync message.
Hence the first order recommendation in my opinion should be to use the sam=
e
PHB (and DSCP marking) to all PTP messages. <br>
<br>
Choosing one of the existing PHBs as the recommended one for PTP is somewha=
t
harder. EF is a reasonable choice in my opinion, as per RFC4595 &#39;The in=
tent of
Expedited Forwarding PHB [RFC3246] is to provide a building block for low-l=
oss,
low-delay, and low-jitter services.&#39; TICTOC could in principle recommen=
d
defining a new PHB tailored for PTP and similar services, but I guess this
would be a longer process.<br>
<br>
I would appreciate if others will share their insight on the recommended us=
age
and whether this issue should or should not be addressed by TICTOC. <br>
<br>
Here is the relevant text from IEEE1588-2008 Annex D: &quot;For PTP event
messages, the value of the differentiated service (DS) field in the Type of
Service (ToS)<br>
field should be set to the highest traffic class selector codepoint
available.&quot; The PTP Telecom profile for frequency distribution, ITU-T
G.8265.1, doesn&#39;t specify or recommend DSCP settings.<br>
<br>
Best,<br>
Ron<u></u><u></u></span></font></p>

</div>

</div>

</div>

</div>

</div>

</div>

<p class=3D"MsoNormal"><font size=3D"3" face=3D"Times New Roman"><span styl=
e=3D"font-size:12.0pt"><u></u>=A0<u></u></span></font></p>

</div>

</div></div></div>

</div>


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

--20cf3054a0fdc1d06f04aa04c647--

From zhang.junhui1@zte.com.cn  Mon Aug  8 20:48:03 2011
Return-Path: <zhang.junhui1@zte.com.cn>
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 6117011E808F for <tictoc@ietfa.amsl.com>; Mon,  8 Aug 2011 20:48:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -91.677
X-Spam-Level: 
X-Spam-Status: No, score=-91.677 tagged_above=-999 required=5 tests=[AWL=-0.371, BAYES_00=-2.599, CHARSET_FARAWAY_HEADER=3.2, HTML_FONT_FACE_BAD=0.884, HTML_MESSAGE=0.001, J_CHICKENPOX_82=0.6, MIME_8BIT_HEADER=0.3, MIME_BASE64_TEXT=1.753, MIME_CHARSET_FARAWAY=2.45, RCVD_DOUBLE_IP_LOOSE=0.76, SARE_SUB_ENC_GB2312=1.345, 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 WoHb+167QxPU for <tictoc@ietfa.amsl.com>; Mon,  8 Aug 2011 20:48:02 -0700 (PDT)
Received: from mx5.zte.com.cn (mx6.zte.com.cn [95.130.199.165]) by ietfa.amsl.com (Postfix) with ESMTP id D192811E808A for <tictoc@ietf.org>; Mon,  8 Aug 2011 20:48:01 -0700 (PDT)
Received: from [10.30.17.99] by mx5.zte.com.cn with surfront esmtp id 131321930506506; Tue, 9 Aug 2011 11:37:51 +0800 (CST)
Received: from [10.30.3.20] by [192.168.168.15] with StormMail ESMTP id 22013.1930506506; Tue, 9 Aug 2011 11:48:20 +0800 (CST)
Received: (from root@localhost) by mse01.zte.com.cn id p793mIog043644 for <tictoc@ietf.org>; Tue, 9 Aug 2011 11:48:18 +0800 (GMT-8) (envelope-from zhang.junhui1@zte.com.cn)
Received: from notes_smtp.zte.com.cn ([10.30.1.239]) by mse01.zte.com.cn with ESMTP id p793V2Zb025978; Tue, 9 Aug 2011 11:31:02 +0800 (GMT-8) (envelope-from zhang.junhui1@zte.com.cn)
Message-Id: <201108090348.p793mIog043644@mse01.zte.com.cn>
In-Reply-To: <2C2F1EBA8050E74EA81502D5740B4BD6A9327F9E2C@SJEXCHCCR02.corp.ad.broadcom.com>
To: "Shahram Davari" <davari@broadcom.com>
MIME-Version: 1.0
X-KeepSent: 23B46B15:05186391-482578E7:000A0DCE; type=4; name=$KeepSent
X-Mailer: Lotus Notes Release 6.5.6 March 06, 2007
From: zhang.junhui1@zte.com.cn
Date: Tue, 9 Aug 2011 11:30:57 +0800
X-MIMETrack: Serialize by Router on notes_smtp/zte_ltd(Release 8.5.1FP4|July 25, 2010) at 2011-08-09 11:31:04, Serialize complete at 2011-08-09 11:31:04
Content-Type: multipart/alternative; boundary="=_alternative 00135209482578E7_="
X-MAIL: mse01.zte.com.cn p793mIog043644
X-MSS: AUDITRELEASE@mse01.zte.com.cn
Cc: tictoc-bounces@ietf.org, "tictoc@ietf.org" <tictoc@ietf.org>
Subject: [TICTOC] =?gb2312?b?tPC4tDogUmU6ICBEU0NQIGZvciBQVFA=?=
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, 09 Aug 2011 03:48:03 -0000

This is a multipart message in MIME format.
--=_alternative 00135209482578E7_=
Content-Type: text/plain; charset="GB2312"
Content-Transfer-Encoding: base64

U2hhaHJhbSwNCg0KICBUaGVyZSBhcmUgbWFueSBmYWN0b3JzICAgaW50cm9kdWNlICBQRFYgbm9p
c2Ugd2hpY2ggaGFzIGEgc2lnbmlmaWNhbnQgDQppbXBhY3Qgb24gdGhlIHN5bmNocm9uaXphdGlv
biBwZXJmb3JtYW5jZSAsIA0KICBleGNlcHQgIHRoZSBwcmlvcml0eSBvZiBQVFAgbWVzc2FnZXMu
IA0KIA0KICBJIHRoaW5rICB0aGUgUERWIG1ldHJpY3Mgc2hvdWxkIGJlIGNvbnNpZGVyZWQgaW4g
UFRQIExTUCANClNldHVwLFByb3RlY3Rpb24gYW5kIFJlZHVuZGFuY3kgLiANCiAgVGhhdCBpcywg
IGV4Y2VwdCBmb3IgVEMtY2FwYWJpbGl0eSBhbmQgdGhlIHByaW9yaXR5IG9mIFBUUCBtZXNzYWdl
cywgdGhlIA0KY2FwYWJpbGl0eSBvZiByZXNlcnZpbmcgYmFuZHdpZHRoIHNob3VsZCBiZSBjb25z
aWRlcmVkIA0KICBpbiBQVFAgTFNQIFNldHVwLCBiZWNhdXNlIHNvbWUgb2YgdGhlIG5ldHdvcmsg
bm9kZXMgZG9uoa90IHN1cHBvcnQgdGhlIA0KY2FwYWJpbGl0eSBvZiByZXNlcnZpbmcgYmFuZHdp
ZHRoIGR1ZSB0byB0aGUgY29tcGxleGl0eSANCiAgb2YgaW1wbGVtZW50YXRpb24gYW5kIHRoZSBj
b3N0IG9mIEhXLg0KDQogIEluIGFkZGl0aW9uLGl0IGlzIHBvc3NpYmxlIHRoYXQgYSBtb3JlIGVm
ZmljaWVudCBwYXRoIGZvciB0aGUgUFRQIA0KYmVjb21lcyBhdmFpbGFibGUsIGZvciBleGFtcGxl
LCB0aGUgZGVwbG95bWVudCANCiAgb2YgbmV3IDE1ODgtYXdhcmUgTFNScywgYW5kIHNvIG9uLiBJ
biBvcmRlciB0byBpbXByb3ZlIHRoZSANCnN5bmNocm9uaXphdGlvbiBwZXJmb3JtYW5jZSwgdGhl
IGhlYWQtZW5kIHJlLXJvdXRlIHRoZQ0KICBQVFAgb250byB0aGUgbmV3IHBhdGguDQogDQogIFNp
bmNlIGFuIG9jY2FzaW9uYWwgY29ubmVjdGlvbiBmYWlsdXJlIGlzIGluc2lnbmlmaWNhbnQgdG8g
dGhlIA0Kc3luY2hyb25pemF0aW9uIHBlcmZvcm1hbmNlLiBIb3dldmVyLCB0aGUgUERWIG5vaXNl
DQogIGJ5IHRoZSBwYWNrZXQgdGltaW5nIHNpZ25hbCBhcyBpdCB0cmF2ZXJzZXMgdGhlIG5ldHdv
cmsgZnJvbSB0aGUgMTU4OCANCk1hc3RlciB0byB0aGUgMTU4OCBTbGF2ZSBpcyBjcml0aWNhbCB0
byB0aGUNCiAgc3luY2hyb25pemF0aW9uIHBlcmZvcm1hbmNlLlNvLCBpdCBpcyByZWFzb25hYmxl
IHRvIHJlY292ZXIgdGhlIA0Kc3luY2hyb25pemF0aW9uIGFwcGxpY2F0aW9uIGJhc2VkIG9uIHRo
ZSBQRFYgDQogIG1ldHJpY3MuDQogDQogIEkgd291bGQgbGlrZSB0byBoZWFyIGFueSBzdWdnZXN0
aW9ucyBmcm9tIHlvdSBhbmQgZXZlcnlib2R5LiAgVGhhbmtzLg0KDQoNCg0KICBCZXN0IFJlZ2Fy
ZHMNCiAgSnVuaHVpDQoNCg0KDQoNCg0KIlNoYWhyYW0gRGF2YXJpIiA8ZGF2YXJpQGJyb2FkY29t
LmNvbT4gDQq3orz+yMs6ICB0aWN0b2MtYm91bmNlc0BpZXRmLm9yZw0KMjAxMS0wOC0wOSAwMToz
Nw0KDQrK1bz+yMsNCiJSb24gQ29oZW4iIDxyb25jLm50ZWFyQGdtYWlsLmNvbT4sICJ0aWN0b2NA
aWV0Zi5vcmciIDx0aWN0b2NAaWV0Zi5vcmc+DQqzrcvNDQoNCtb3zOINClJlOiBbVElDVE9DXSBE
U0NQIGZvciBQVFANCg0KDQoNCg0KDQoNClJvbiwNCiANCkkgYWdyZWUgd2l0aCB5b3UgdGhhdCBh
bGwgUFRQIG1lc3NhZ2VzIG11c3QgY29uZmlndXJlZCB3aXRoIGhpZ2hlc3QgDQpwcmlvcml0eSAo
YS5rLmEgRUYgUEhCKSBhbmQgRUYgc2hvdWxkIGJlIHRoZSBkZWZhdWx0LiBJbiBmYWN0IEkgd291
bGQgYWxzbyANCnRoaW5rIGl0IGlzIGJlc3QgdG8gdXNlIEwtTFNQIHdpdGggRUYgUEhCIGZvciAx
NTg4ME1QTFMuIElmIHRoaXMgaXMgDQphY2NlcHRhYmxlIGJ5IHRoZSBncm91cCB0aGVuIHdlIGNv
dWxkIGFkZCB0aGlzIHRvIHRoZSAxNTg4b01QTFMgZHJhZnQuDQogDQogDQpSZWdhcmRzLA0KU2hh
aHJhbQ0KIA0KRnJvbTogdGljdG9jLWJvdW5jZXNAaWV0Zi5vcmcgW21haWx0bzp0aWN0b2MtYm91
bmNlc0BpZXRmLm9yZ10gT24gQmVoYWxmIA0KT2YgUm9uIENvaGVuDQpTZW50OiBTdW5kYXksIEF1
Z3VzdCAwNywgMjAxMSAxOjAwIEFNDQpUbzogdGljdG9jQGlldGYub3JnDQpTdWJqZWN0OiBbVElD
VE9DXSBEU0NQIGZvciBQVFANCiANCkhpLA0KDQpDdXJyZW50IHN0YW5kYXJkcyBkbyBub3QgcmVj
b21tZW5kIHdoaWNoIERTQ1AgdmFsdWVzIHRvIHNldCBvbiBQVFAgDQptZXNzYWdlcy4gQXMgYSBy
ZXN1bHQgdmVuZG9ycyBoYXZlIGNob3NlbiBkaWZmZXJlbnQgZGVmYXVsdCB2YWx1ZXMsIGFuZCAN
CnNvbWUgdmVuZG9ycyBhbHNvIGRpZmZlcmVudGlhdGUgYmV0d2VlbiB0aGUgRFNDUCBzZXQgb24g
UFRQIEV2ZW50IG1lc3NhZ2VzIA0KKFN5bmMsIERlbGF5X1JlcSwgZXRjLikgYW5kIFBUUCBHZW5l
cmFsIG1lc3NhZ2VzIChBbm5vdW5jZSwgRm9sbG93X1VwLCANCkRlbGF5X1Jlc3ApLiBJIHRoaW5r
IFRJQ1RPQyBjYW4gaGVscCBjbGFyaWZ5IHRoZSByZWNvbW1lbmRlZCBEU0NQIHVzYWdlLCANCmFs
b25nIHRoZSBndWlkZWxpbmVzIG9mIFJGQzQ1OTUsICdDb25maWd1cmF0aW9uIEd1aWRlbGluZXMg
Zm9yIERpZmZTZXJ2IA0KU2VydmljZSBDbGFzc2VzJy4NCg0KSW4gbXkgb3BpbmlvbiBjbGFzc2lm
eWluZyBQVFAgZXZlbnQgYW5kIGdlbmVyYWwgbWVzc2FnZXMgaW50byBzZXBhcmF0ZSANClBIQnMg
aXMgcHJvYmxlbWF0aWMgYXMgZGlzY2FyZCBvZiBGb2xsb3dfVXAgd291bGQgcmVuZGVyIGl0cyBh
c3NvY2lhdGVkIA0KU3luYyBtZXNzYWdlIHVzZWxlc3MuIEZvcndhcmRpbmcgb2YgU3luYyBtZXNz
YWdlcyBpbiBhIGhpZ2hlciBwcmlvcml0eSANCnF1ZXVlIGNvbXBhcmVkIHRvIEZvbGxvd19VcCBt
YXkgbGVhZCB0byBTeW5jIG1lc3NhZ2UgZ2V0dGluZyBhaGVhZCBvZiB0aGUgDQpwcmV2aW91cyBG
b2xsb3dfVXAgbWVzc2FnZSB3aGljaCBhZ2FpbiBjYXVzZXMgdGhlIHNsYXZlIHRvIGRpc2NhcmQg
dGhlIA0KcHJldmlvdXMgU3luYyBtZXNzYWdlLiBIZW5jZSB0aGUgZmlyc3Qgb3JkZXIgcmVjb21t
ZW5kYXRpb24gaW4gbXkgb3BpbmlvbiANCnNob3VsZCBiZSB0byB1c2UgdGhlIHNhbWUgUEhCIChh
bmQgRFNDUCBtYXJraW5nKSB0byBhbGwgUFRQIG1lc3NhZ2VzLiANCg0KQ2hvb3Npbmcgb25lIG9m
IHRoZSBleGlzdGluZyBQSEJzIGFzIHRoZSByZWNvbW1lbmRlZCBvbmUgZm9yIFBUUCBpcyANCnNv
bWV3aGF0IGhhcmRlci4gRUYgaXMgYSByZWFzb25hYmxlIGNob2ljZSBpbiBteSBvcGluaW9uLCBh
cyBwZXIgUkZDNDU5NSANCidUaGUgaW50ZW50IG9mIEV4cGVkaXRlZCBGb3J3YXJkaW5nIFBIQiBb
UkZDMzI0Nl0gaXMgdG8gcHJvdmlkZSBhIGJ1aWxkaW5nIA0KYmxvY2sgZm9yIGxvdy1sb3NzLCBs
b3ctZGVsYXksIGFuZCBsb3ctaml0dGVyIHNlcnZpY2VzLicgVElDVE9DIGNvdWxkIGluIA0KcHJp
bmNpcGxlIHJlY29tbWVuZCBkZWZpbmluZyBhIG5ldyBQSEIgdGFpbG9yZWQgZm9yIFBUUCBhbmQg
c2ltaWxhciANCnNlcnZpY2VzLCBidXQgSSBndWVzcyB0aGlzIHdvdWxkIGJlIGEgbG9uZ2VyIHBy
b2Nlc3MuDQoNCkkgd291bGQgYXBwcmVjaWF0ZSBpZiBvdGhlcnMgd2lsbCBzaGFyZSB0aGVpciBp
bnNpZ2h0IG9uIHRoZSByZWNvbW1lbmRlZCANCnVzYWdlIGFuZCB3aGV0aGVyIHRoaXMgaXNzdWUg
c2hvdWxkIG9yIHNob3VsZCBub3QgYmUgYWRkcmVzc2VkIGJ5IFRJQ1RPQy4gDQoNCkhlcmUgaXMg
dGhlIHJlbGV2YW50IHRleHQgZnJvbSBJRUVFMTU4OC0yMDA4IEFubmV4IEQ6ICJGb3IgUFRQIGV2
ZW50IA0KbWVzc2FnZXMsIHRoZSB2YWx1ZSBvZiB0aGUgZGlmZmVyZW50aWF0ZWQgc2VydmljZSAo
RFMpIGZpZWxkIGluIHRoZSBUeXBlIA0Kb2YgU2VydmljZSAoVG9TKQ0KZmllbGQgc2hvdWxkIGJl
IHNldCB0byB0aGUgaGlnaGVzdCB0cmFmZmljIGNsYXNzIHNlbGVjdG9yIGNvZGVwb2ludCANCmF2
YWlsYWJsZS4iIFRoZSBQVFAgVGVsZWNvbSBwcm9maWxlIGZvciBmcmVxdWVuY3kgZGlzdHJpYnV0
aW9uLCBJVFUtVCANCkcuODI2NS4xLCBkb2Vzbid0IHNwZWNpZnkgb3IgcmVjb21tZW5kIERTQ1Ag
c2V0dGluZ3MuDQoNCkJlc3QsDQpSb25fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fXw0KVElDVE9DIG1haWxpbmcgbGlzdA0KVElDVE9DQGlldGYub3JnDQpodHRw
czovL3d3dy5pZXRmLm9yZy9tYWlsbWFuL2xpc3RpbmZvL3RpY3RvYw0KDQoNCg0KDQotLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLQ0KWlRFIElu
Zm9ybWF0aW9uIFNlY3VyaXR5IE5vdGljZTogVGhlIGluZm9ybWF0aW9uIGNvbnRhaW5lZCBpbiB0
aGlzIG1haWwgaXMgc29sZWx5IHByb3BlcnR5IG9mIHRoZSBzZW5kZXIncyBvcmdhbml6YXRpb24u
IFRoaXMgbWFpbCBjb21tdW5pY2F0aW9uIGlzIGNvbmZpZGVudGlhbC4gUmVjaXBpZW50cyBuYW1l
ZCBhYm92ZSBhcmUgb2JsaWdhdGVkIHRvIG1haW50YWluIHNlY3JlY3kgYW5kIGFyZSBub3QgcGVy
bWl0dGVkIHRvIGRpc2Nsb3NlIHRoZSBjb250ZW50cyBvZiB0aGlzIGNvbW11bmljYXRpb24gdG8g
b3RoZXJzLg0KVGhpcyBlbWFpbCBhbmQgYW55IGZpbGVzIHRyYW5zbWl0dGVkIHdpdGggaXQgYXJl
IGNvbmZpZGVudGlhbCBhbmQgaW50ZW5kZWQgc29sZWx5IGZvciB0aGUgdXNlIG9mIHRoZSBpbmRp
dmlkdWFsIG9yIGVudGl0eSB0byB3aG9tIHRoZXkgYXJlIGFkZHJlc3NlZC4gSWYgeW91IGhhdmUg
cmVjZWl2ZWQgdGhpcyBlbWFpbCBpbiBlcnJvciBwbGVhc2Ugbm90aWZ5IHRoZSBvcmlnaW5hdG9y
IG9mIHRoZSBtZXNzYWdlLiBBbnkgdmlld3MgZXhwcmVzc2VkIGluIHRoaXMgbWVzc2FnZSBhcmUg
dGhvc2Ugb2YgdGhlIGluZGl2aWR1YWwgc2VuZGVyLg0KVGhpcyBtZXNzYWdlIGhhcyBiZWVuIHNj
YW5uZWQgZm9yIHZpcnVzZXMgYW5kIFNwYW0gYnkgWlRFIEFudGktU3BhbSBzeXN0ZW0uDQo=
--=_alternative 00135209482578E7_=
Content-Type: text/html; charset="GB2312"
Content-Transfer-Encoding: base64

DQo8YnI+PGZvbnQgc2l6ZT0zIGZhY2U9IsvOzOUiPlNoYWhyYW0sPC9mb250Pg0KPGJyPg0KPGJy
Pjxmb250IHNpemU9MyBmYWNlPSLLzszlIj4mbmJzcDsgVGhlcmUgYXJlIG1hbnkgZmFjdG9ycyAm
bmJzcDsgaW50cm9kdWNlDQombmJzcDtQRFYgbm9pc2Ugd2hpY2ggaGFzIGEgc2lnbmlmaWNhbnQg
aW1wYWN0IG9uIHRoZSBzeW5jaHJvbml6YXRpb24gcGVyZm9ybWFuY2UNCiwgPC9mb250Pg0KPGJy
Pjxmb250IHNpemU9MyBmYWNlPSLLzszlIj4mbmJzcDsgZXhjZXB0ICZuYnNwO3RoZSBwcmlvcml0
eSBvZiBQVFANCm1lc3NhZ2VzLiAmbmJzcDs8L2ZvbnQ+DQo8YnI+PGZvbnQgc2l6ZT0zIGZhY2U9
IsvOzOUiPiZuYnNwOyAmbmJzcDsgPC9mb250Pg0KPGJyPjxmb250IHNpemU9MyBmYWNlPSLLzszl
Ij4mbmJzcDsgSSB0aGluayAmbmJzcDt0aGUgUERWIG1ldHJpY3Mgc2hvdWxkDQpiZSBjb25zaWRl
cmVkIGluIFBUUCBMU1AgU2V0dXAsUHJvdGVjdGlvbiBhbmQgUmVkdW5kYW5jeSAuIDwvZm9udD4N
Cjxicj48Zm9udCBzaXplPTMgZmFjZT0iy87M5SI+Jm5ic3A7IFRoYXQgaXMsICZuYnNwO2V4Y2Vw
dCBmb3IgVEMtY2FwYWJpbGl0eQ0KYW5kIHRoZSBwcmlvcml0eSBvZiBQVFAgbWVzc2FnZXMsIHRo
ZSBjYXBhYmlsaXR5IG9mIHJlc2VydmluZyBiYW5kd2lkdGgNCnNob3VsZCBiZSBjb25zaWRlcmVk
IDwvZm9udD4NCjxicj48Zm9udCBzaXplPTMgZmFjZT0iy87M5SI+Jm5ic3A7IGluIFBUUCBMU1Ag
U2V0dXAsIGJlY2F1c2Ugc29tZSBvZg0KdGhlIG5ldHdvcmsgbm9kZXMgZG9uoa90IHN1cHBvcnQg
dGhlIGNhcGFiaWxpdHkgb2YgcmVzZXJ2aW5nIGJhbmR3aWR0aA0KZHVlIHRvIHRoZSBjb21wbGV4
aXR5IDwvZm9udD4NCjxicj48Zm9udCBzaXplPTMgZmFjZT0iy87M5SI+Jm5ic3A7IG9mIGltcGxl
bWVudGF0aW9uIGFuZCB0aGUgY29zdCBvZg0KSFcuPC9mb250Pg0KPGJyPg0KPGJyPjxmb250IHNp
emU9MyBmYWNlPSLLzszlIj4mbmJzcDsgSW4gYWRkaXRpb24saXQgaXMgcG9zc2libGUgdGhhdCBh
DQptb3JlIGVmZmljaWVudCBwYXRoIGZvciB0aGUgUFRQIGJlY29tZXMgYXZhaWxhYmxlLCBmb3Ig
ZXhhbXBsZSwgdGhlIGRlcGxveW1lbnQNCjwvZm9udD4NCjxicj48Zm9udCBzaXplPTMgZmFjZT0i
y87M5SI+Jm5ic3A7IG9mIG5ldyAxNTg4LWF3YXJlIExTUnMsIGFuZCBzbyBvbi4NCkluIG9yZGVy
IHRvIGltcHJvdmUgdGhlIHN5bmNocm9uaXphdGlvbiBwZXJmb3JtYW5jZSwgdGhlIGhlYWQtZW5k
IHJlLXJvdXRlDQp0aGU8L2ZvbnQ+DQo8YnI+PGZvbnQgc2l6ZT0zIGZhY2U9IsvOzOUiPiZuYnNw
OyBQVFAgb250byB0aGUgbmV3IHBhdGguPC9mb250Pg0KPGJyPjxmb250IHNpemU9MyBmYWNlPSLL
zszlIj4mbmJzcDsgPC9mb250Pg0KPGJyPjxmb250IHNpemU9MyBmYWNlPSLLzszlIj4mbmJzcDsg
U2luY2UgYW4gb2NjYXNpb25hbCBjb25uZWN0aW9uIGZhaWx1cmUNCmlzIGluc2lnbmlmaWNhbnQg
dG8gdGhlIHN5bmNocm9uaXphdGlvbiBwZXJmb3JtYW5jZS4gSG93ZXZlciwgdGhlIFBEViBub2lz
ZTwvZm9udD4NCjxicj48Zm9udCBzaXplPTMgZmFjZT0iy87M5SI+Jm5ic3A7IGJ5IHRoZSBwYWNr
ZXQgdGltaW5nIHNpZ25hbCBhcyBpdA0KdHJhdmVyc2VzIHRoZSBuZXR3b3JrIGZyb20gdGhlIDE1
ODggTWFzdGVyIHRvIHRoZSAxNTg4IFNsYXZlIGlzIGNyaXRpY2FsDQp0byB0aGU8L2ZvbnQ+DQo8
YnI+PGZvbnQgc2l6ZT0zIGZhY2U9IsvOzOUiPiZuYnNwOyBzeW5jaHJvbml6YXRpb24gcGVyZm9y
bWFuY2UuU28sIGl0DQppcyByZWFzb25hYmxlIHRvIHJlY292ZXIgdGhlIHN5bmNocm9uaXphdGlv
biBhcHBsaWNhdGlvbiBiYXNlZCBvbiB0aGUgUERWDQo8L2ZvbnQ+DQo8YnI+PGZvbnQgc2l6ZT0z
IGZhY2U9IsvOzOUiPiZuYnNwOyBtZXRyaWNzLjwvZm9udD4NCjxicj48Zm9udCBzaXplPTMgZmFj
ZT0iy87M5SI+Jm5ic3A7IDwvZm9udD4NCjxicj48Zm9udCBzaXplPTMgZmFjZT0iy87M5SI+Jm5i
c3A7IEkgd291bGQgbGlrZSB0byBoZWFyIGFueSBzdWdnZXN0aW9ucw0KZnJvbSB5b3UgYW5kIGV2
ZXJ5Ym9keS4gJm5ic3A7VGhhbmtzLjwvZm9udD4NCjxicj4NCjxicj4NCjxicj4NCjxicj48Zm9u
dCBzaXplPTIgZmFjZT0ic2Fucy1zZXJpZiI+Jm5ic3A7IEJlc3QgUmVnYXJkczxicj4NCiAmbmJz
cDtKdW5odWk8YnI+DQo8YnI+DQo8L2ZvbnQ+DQo8YnI+DQo8YnI+DQo8YnI+DQo8dGFibGUgd2lk
dGg9MTAwJT4NCjx0ciB2YWxpZ249dG9wPg0KPHRkIHdpZHRoPTM1JT48Zm9udCBzaXplPTEgZmFj
ZT0ic2Fucy1zZXJpZiI+PGI+JnF1b3Q7U2hhaHJhbSBEYXZhcmkmcXVvdDsNCiZsdDtkYXZhcmlA
YnJvYWRjb20uY29tJmd0OzwvYj4gPC9mb250Pg0KPGJyPjxmb250IHNpemU9MSBmYWNlPSJzYW5z
LXNlcmlmIj63orz+yMs6ICZuYnNwO3RpY3RvYy1ib3VuY2VzQGlldGYub3JnPC9mb250Pg0KPHA+
PGZvbnQgc2l6ZT0xIGZhY2U9InNhbnMtc2VyaWYiPjIwMTEtMDgtMDkgMDE6Mzc8L2ZvbnQ+DQo8
dGQgd2lkdGg9NjQlPg0KPHRhYmxlIHdpZHRoPTEwMCU+DQo8dHIgdmFsaWduPXRvcD4NCjx0ZD4N
CjxkaXYgYWxpZ249cmlnaHQ+PGZvbnQgc2l6ZT0xIGZhY2U9InNhbnMtc2VyaWYiPsrVvP7Iyzwv
Zm9udD48L2Rpdj4NCjx0ZD48Zm9udCBzaXplPTEgZmFjZT0ic2Fucy1zZXJpZiI+JnF1b3Q7Um9u
IENvaGVuJnF1b3Q7ICZsdDtyb25jLm50ZWFyQGdtYWlsLmNvbSZndDssDQomcXVvdDt0aWN0b2NA
aWV0Zi5vcmcmcXVvdDsgJmx0O3RpY3RvY0BpZXRmLm9yZyZndDs8L2ZvbnQ+DQo8dHIgdmFsaWdu
PXRvcD4NCjx0ZD4NCjxkaXYgYWxpZ249cmlnaHQ+PGZvbnQgc2l6ZT0xIGZhY2U9InNhbnMtc2Vy
aWYiPrOty808L2ZvbnQ+PC9kaXY+DQo8dGQ+DQo8dHIgdmFsaWduPXRvcD4NCjx0ZD4NCjxkaXYg
YWxpZ249cmlnaHQ+PGZvbnQgc2l6ZT0xIGZhY2U9InNhbnMtc2VyaWYiPtb3zOI8L2ZvbnQ+PC9k
aXY+DQo8dGQ+PGZvbnQgc2l6ZT0xIGZhY2U9InNhbnMtc2VyaWYiPlJlOiBbVElDVE9DXSBEU0NQ
IGZvciBQVFA8L2ZvbnQ+PC90YWJsZT4NCjxicj4NCjx0YWJsZT4NCjx0ciB2YWxpZ249dG9wPg0K
PHRkPg0KPHRkPjwvdGFibGU+DQo8YnI+PC90YWJsZT4NCjxicj4NCjxicj4NCjxicj48Zm9udCBz
aXplPTIgY29sb3I9IzFmNDk3ZCBmYWNlPSJDYWxpYnJpIj5Sb24sPC9mb250Pg0KPGJyPjxmb250
IHNpemU9MiBjb2xvcj0jMWY0OTdkIGZhY2U9IkNhbGlicmkiPiZuYnNwOzwvZm9udD4NCjxicj48
Zm9udCBzaXplPTIgY29sb3I9IzFmNDk3ZCBmYWNlPSJDYWxpYnJpIj5JIGFncmVlIHdpdGggeW91
IHRoYXQgYWxsDQpQVFAgbWVzc2FnZXMgbXVzdCBjb25maWd1cmVkIHdpdGggaGlnaGVzdCBwcmlv
cml0eSAoYS5rLmEgRUYgUEhCKSBhbmQgRUYNCnNob3VsZCBiZSB0aGUgZGVmYXVsdC4gSW4gZmFj
dCBJIHdvdWxkIGFsc28gdGhpbmsgaXQgaXMgYmVzdCB0byB1c2UgTC1MU1ANCndpdGggRUYgUEhC
IGZvciAxNTg4ME1QTFMuIElmIHRoaXMgaXMgYWNjZXB0YWJsZSBieSB0aGUgZ3JvdXAgdGhlbiB3
ZSBjb3VsZA0KYWRkIHRoaXMgdG8gdGhlIDE1ODhvTVBMUyBkcmFmdC48L2ZvbnQ+DQo8YnI+PGZv
bnQgc2l6ZT0yIGNvbG9yPSMxZjQ5N2QgZmFjZT0iQ2FsaWJyaSI+Jm5ic3A7PC9mb250Pg0KPGJy
Pjxmb250IHNpemU9MiBjb2xvcj0jMWY0OTdkIGZhY2U9IkNhbGlicmkiPiZuYnNwOzwvZm9udD4N
Cjxicj48Zm9udCBzaXplPTIgY29sb3I9IzFmNDk3ZCBmYWNlPSJDYWxpYnJpIj5SZWdhcmRzLDwv
Zm9udD4NCjxicj48Zm9udCBzaXplPTIgY29sb3I9IzFmNDk3ZCBmYWNlPSJDYWxpYnJpIj5TaGFo
cmFtPC9mb250Pg0KPGJyPjxmb250IHNpemU9MiBjb2xvcj0jMWY0OTdkIGZhY2U9IkNhbGlicmki
PiZuYnNwOzwvZm9udD4NCjxicj48Zm9udCBzaXplPTIgZmFjZT0iVGFob21hIj48Yj5Gcm9tOjwv
Yj4gdGljdG9jLWJvdW5jZXNAaWV0Zi5vcmcgW21haWx0bzp0aWN0b2MtYm91bmNlc0BpZXRmLm9y
Z10NCjxiPk9uIEJlaGFsZiBPZiA8L2I+Um9uIENvaGVuPGI+PGJyPg0KU2VudDo8L2I+IFN1bmRh
eSwgQXVndXN0IDA3LCAyMDExIDE6MDAgQU08Yj48YnI+DQpUbzo8L2I+IHRpY3RvY0BpZXRmLm9y
ZzxiPjxicj4NClN1YmplY3Q6PC9iPiBbVElDVE9DXSBEU0NQIGZvciBQVFA8L2ZvbnQ+DQo8YnI+
PGZvbnQgc2l6ZT0zIGZhY2U9IlRpbWVzIE5ldyBSb21hbiI+Jm5ic3A7PC9mb250Pg0KPGJyPjxm
b250IHNpemU9MyBmYWNlPSJUaW1lcyBOZXcgUm9tYW4iPkhpLDxicj4NCjxicj4NCkN1cnJlbnQg
c3RhbmRhcmRzIGRvIG5vdCByZWNvbW1lbmQgd2hpY2ggRFNDUCB2YWx1ZXMgdG8gc2V0IG9uIFBU
UCBtZXNzYWdlcy4NCkFzIGEgcmVzdWx0IHZlbmRvcnMgaGF2ZSBjaG9zZW4gZGlmZmVyZW50IGRl
ZmF1bHQgdmFsdWVzLCBhbmQgc29tZSB2ZW5kb3JzDQphbHNvIGRpZmZlcmVudGlhdGUgYmV0d2Vl
biB0aGUgRFNDUCBzZXQgb24gUFRQIEV2ZW50IG1lc3NhZ2VzIChTeW5jLCBEZWxheV9SZXEsDQpl
dGMuKSBhbmQgUFRQIEdlbmVyYWwgbWVzc2FnZXMgKEFubm91bmNlLCBGb2xsb3dfVXAsIERlbGF5
X1Jlc3ApLiBJIHRoaW5rDQpUSUNUT0MgY2FuIGhlbHAgY2xhcmlmeSB0aGUgcmVjb21tZW5kZWQg
RFNDUCB1c2FnZSwgYWxvbmcgdGhlIGd1aWRlbGluZXMNCm9mIFJGQzQ1OTUsICdDb25maWd1cmF0
aW9uIEd1aWRlbGluZXMgZm9yIERpZmZTZXJ2IFNlcnZpY2UgQ2xhc3NlcycuPGJyPg0KPGJyPg0K
SW4gbXkgb3BpbmlvbiBjbGFzc2lmeWluZyBQVFAgZXZlbnQgYW5kIGdlbmVyYWwgbWVzc2FnZXMg
aW50byBzZXBhcmF0ZQ0KUEhCcyBpcyBwcm9ibGVtYXRpYyBhcyBkaXNjYXJkIG9mIEZvbGxvd19V
cCB3b3VsZCByZW5kZXIgaXRzIGFzc29jaWF0ZWQNClN5bmMgbWVzc2FnZSB1c2VsZXNzLiBGb3J3
YXJkaW5nIG9mIFN5bmMgbWVzc2FnZXMgaW4gYSBoaWdoZXIgcHJpb3JpdHkNCnF1ZXVlIGNvbXBh
cmVkIHRvIEZvbGxvd19VcCBtYXkgbGVhZCB0byBTeW5jIG1lc3NhZ2UgZ2V0dGluZyBhaGVhZCBv
ZiB0aGUNCnByZXZpb3VzIEZvbGxvd19VcCBtZXNzYWdlIHdoaWNoIGFnYWluIGNhdXNlcyB0aGUg
c2xhdmUgdG8gZGlzY2FyZCB0aGUNCnByZXZpb3VzIFN5bmMgbWVzc2FnZS4gSGVuY2UgdGhlIGZp
cnN0IG9yZGVyIHJlY29tbWVuZGF0aW9uIGluIG15IG9waW5pb24NCnNob3VsZCBiZSB0byB1c2Ug
dGhlIHNhbWUgUEhCIChhbmQgRFNDUCBtYXJraW5nKSB0byBhbGwgUFRQIG1lc3NhZ2VzLiA8YnI+
DQo8YnI+DQpDaG9vc2luZyBvbmUgb2YgdGhlIGV4aXN0aW5nIFBIQnMgYXMgdGhlIHJlY29tbWVu
ZGVkIG9uZSBmb3IgUFRQIGlzIHNvbWV3aGF0DQpoYXJkZXIuIEVGIGlzIGEgcmVhc29uYWJsZSBj
aG9pY2UgaW4gbXkgb3BpbmlvbiwgYXMgcGVyIFJGQzQ1OTUgJ1RoZSBpbnRlbnQNCm9mIEV4cGVk
aXRlZCBGb3J3YXJkaW5nIFBIQiBbUkZDMzI0Nl0gaXMgdG8gcHJvdmlkZSBhIGJ1aWxkaW5nIGJs
b2NrIGZvcg0KbG93LWxvc3MsIGxvdy1kZWxheSwgYW5kIGxvdy1qaXR0ZXIgc2VydmljZXMuJyBU
SUNUT0MgY291bGQgaW4gcHJpbmNpcGxlDQpyZWNvbW1lbmQgZGVmaW5pbmcgYSBuZXcgUEhCIHRh
aWxvcmVkIGZvciBQVFAgYW5kIHNpbWlsYXIgc2VydmljZXMsIGJ1dA0KSSBndWVzcyB0aGlzIHdv
dWxkIGJlIGEgbG9uZ2VyIHByb2Nlc3MuPGJyPg0KPGJyPg0KSSB3b3VsZCBhcHByZWNpYXRlIGlm
IG90aGVycyB3aWxsIHNoYXJlIHRoZWlyIGluc2lnaHQgb24gdGhlIHJlY29tbWVuZGVkDQp1c2Fn
ZSBhbmQgd2hldGhlciB0aGlzIGlzc3VlIHNob3VsZCBvciBzaG91bGQgbm90IGJlIGFkZHJlc3Nl
ZCBieSBUSUNUT0MuDQo8YnI+DQo8YnI+DQpIZXJlIGlzIHRoZSByZWxldmFudCB0ZXh0IGZyb20g
SUVFRTE1ODgtMjAwOCBBbm5leCBEOiAmcXVvdDtGb3IgUFRQIGV2ZW50DQptZXNzYWdlcywgdGhl
IHZhbHVlIG9mIHRoZSBkaWZmZXJlbnRpYXRlZCBzZXJ2aWNlIChEUykgZmllbGQgaW4gdGhlIFR5
cGUNCm9mIFNlcnZpY2UgKFRvUyk8YnI+DQpmaWVsZCBzaG91bGQgYmUgc2V0IHRvIHRoZSBoaWdo
ZXN0IHRyYWZmaWMgY2xhc3Mgc2VsZWN0b3IgY29kZXBvaW50IGF2YWlsYWJsZS4mcXVvdDsNClRo
ZSBQVFAgVGVsZWNvbSBwcm9maWxlIGZvciBmcmVxdWVuY3kgZGlzdHJpYnV0aW9uLCBJVFUtVCBH
LjgyNjUuMSwgZG9lc24ndA0Kc3BlY2lmeSBvciByZWNvbW1lbmQgRFNDUCBzZXR0aW5ncy48YnI+
DQo8YnI+DQpCZXN0LDxicj4NClJvbjwvZm9udD48dHQ+PGZvbnQgc2l6ZT0yPl9fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fPGJyPg0KVElDVE9DIG1haWxpbmcg
bGlzdDxicj4NClRJQ1RPQ0BpZXRmLm9yZzxicj4NCmh0dHBzOi8vd3d3LmlldGYub3JnL21haWxt
YW4vbGlzdGluZm8vdGljdG9jPGJyPg0KPC9mb250PjwvdHQ+DQo8YnI+DQo8YnI+PHByZT4NCi0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tDQpa
VEUmbmJzcDtJbmZvcm1hdGlvbiZuYnNwO1NlY3VyaXR5Jm5ic3A7Tm90aWNlOiZuYnNwO1RoZSZu
YnNwO2luZm9ybWF0aW9uJm5ic3A7Y29udGFpbmVkJm5ic3A7aW4mbmJzcDt0aGlzJm5ic3A7bWFp
bCZuYnNwO2lzJm5ic3A7c29sZWx5Jm5ic3A7cHJvcGVydHkmbmJzcDtvZiZuYnNwO3RoZSZuYnNw
O3NlbmRlcidzJm5ic3A7b3JnYW5pemF0aW9uLiZuYnNwO1RoaXMmbmJzcDttYWlsJm5ic3A7Y29t
bXVuaWNhdGlvbiZuYnNwO2lzJm5ic3A7Y29uZmlkZW50aWFsLiZuYnNwO1JlY2lwaWVudHMmbmJz
cDtuYW1lZCZuYnNwO2Fib3ZlJm5ic3A7YXJlJm5ic3A7b2JsaWdhdGVkJm5ic3A7dG8mbmJzcDtt
YWludGFpbiZuYnNwO3NlY3JlY3kmbmJzcDthbmQmbmJzcDthcmUmbmJzcDtub3QmbmJzcDtwZXJt
aXR0ZWQmbmJzcDt0byZuYnNwO2Rpc2Nsb3NlJm5ic3A7dGhlJm5ic3A7Y29udGVudHMmbmJzcDtv
ZiZuYnNwO3RoaXMmbmJzcDtjb21tdW5pY2F0aW9uJm5ic3A7dG8mbmJzcDtvdGhlcnMuDQpUaGlz
Jm5ic3A7ZW1haWwmbmJzcDthbmQmbmJzcDthbnkmbmJzcDtmaWxlcyZuYnNwO3RyYW5zbWl0dGVk
Jm5ic3A7d2l0aCZuYnNwO2l0Jm5ic3A7YXJlJm5ic3A7Y29uZmlkZW50aWFsJm5ic3A7YW5kJm5i
c3A7aW50ZW5kZWQmbmJzcDtzb2xlbHkmbmJzcDtmb3ImbmJzcDt0aGUmbmJzcDt1c2UmbmJzcDtv
ZiZuYnNwO3RoZSZuYnNwO2luZGl2aWR1YWwmbmJzcDtvciZuYnNwO2VudGl0eSZuYnNwO3RvJm5i
c3A7d2hvbSZuYnNwO3RoZXkmbmJzcDthcmUmbmJzcDthZGRyZXNzZWQuJm5ic3A7SWYmbmJzcDt5
b3UmbmJzcDtoYXZlJm5ic3A7cmVjZWl2ZWQmbmJzcDt0aGlzJm5ic3A7ZW1haWwmbmJzcDtpbiZu
YnNwO2Vycm9yJm5ic3A7cGxlYXNlJm5ic3A7bm90aWZ5Jm5ic3A7dGhlJm5ic3A7b3JpZ2luYXRv
ciZuYnNwO29mJm5ic3A7dGhlJm5ic3A7bWVzc2FnZS4mbmJzcDtBbnkmbmJzcDt2aWV3cyZuYnNw
O2V4cHJlc3NlZCZuYnNwO2luJm5ic3A7dGhpcyZuYnNwO21lc3NhZ2UmbmJzcDthcmUmbmJzcDt0
aG9zZSZuYnNwO29mJm5ic3A7dGhlJm5ic3A7aW5kaXZpZHVhbCZuYnNwO3NlbmRlci4NClRoaXMm
bmJzcDttZXNzYWdlJm5ic3A7aGFzJm5ic3A7YmVlbiZuYnNwO3NjYW5uZWQmbmJzcDtmb3ImbmJz
cDt2aXJ1c2VzJm5ic3A7YW5kJm5ic3A7U3BhbSZuYnNwO2J5Jm5ic3A7WlRFJm5ic3A7QW50aS1T
cGFtJm5ic3A7c3lzdGVtLg0KPC9wcmU+
--=_alternative 00135209482578E7_=--


From talmi@marvell.com  Mon Aug  8 22:07:28 2011
Return-Path: <talmi@marvell.com>
X-Original-To: tictoc@ietfa.amsl.com
Delivered-To: tictoc@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 08C6021F89CC for <tictoc@ietfa.amsl.com>; Mon,  8 Aug 2011 22:07:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.746
X-Spam-Level: 
X-Spam-Status: No, score=-2.746 tagged_above=-999 required=5 tests=[AWL=-0.148, 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 ZRTVbfRQ6P9b for <tictoc@ietfa.amsl.com>; Mon,  8 Aug 2011 22:07:26 -0700 (PDT)
Received: from galiil.marvell.com (galiil.marvell.com [199.203.130.254]) by ietfa.amsl.com (Postfix) with ESMTP id 0CE2D21F8841 for <tictoc@ietf.org>; Mon,  8 Aug 2011 22:07:25 -0700 (PDT)
From: Tal Mizrahi <talmi@marvell.com>
To: Shahram Davari <davari@broadcom.com>, Ron Cohen <ronc.ntear@gmail.com>, "tictoc@ietf.org" <tictoc@ietf.org>
Date: Tue, 9 Aug 2011 08:07:46 +0300
Thread-Topic: [TICTOC] The Need for Checksum Extension
Thread-Index: AcxNbfYRtIOvX2NjQVWo8np0NdjaUgG8DezQAGV0CfAAF4P2AA==
Message-ID: <74470498B659FA4687F0B0018C19A89C014735063F73@IL-MB01.marvell.com>
References: <CALMYT9TP6WqrZgR2+o_zk7QwYXFE28d4QBo8Q89q+OYJ2cvy1Q@mail.gmail.com> <74470498B659FA4687F0B0018C19A89C0134BF782962@IL-MB01.marvell.com> <2C2F1EBA8050E74EA81502D5740B4BD6A9327F9E6E@SJEXCHCCR02.corp.ad.broadcom.com>
In-Reply-To: <2C2F1EBA8050E74EA81502D5740B4BD6A9327F9E6E@SJEXCHCCR02.corp.ad.broadcom.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: multipart/alternative; boundary="_000_74470498B659FA4687F0B0018C19A89C014735063F73ILMB01marve_"
MIME-Version: 1.0
Subject: Re: [TICTOC] The Need for Checksum Extension
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, 09 Aug 2011 05:07:28 -0000

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

Hi Shahram,

Please see the presentation from the last TICTOC meeting:
http://www.ietf.org/proceedings/81/slides/tictoc-1.ppt

Regards,
Tal.

From: Shahram Davari [mailto:davari@broadcom.com]
Sent: Monday, August 08, 2011 8:57 PM
To: Tal Mizrahi; Ron Cohen; tictoc@ietf.org
Subject: RE: [TICTOC] The Need for Checksum Extension

Tal,

I don't know about OWAMP but NTP doesn't have the concept of TC (Transparen=
t Clocking). So why is there a need for UDP checksum update for NTP?

Also if any of the timing messages needs to change in a router (such as Res=
idence  time update), the router should be able to fully parse that packet =
including the UDP header. So the router would exactly know the UDP checksum=
 location. Therefore I don't see what is the benefit of such Checksum trail=
er/Extension.

Regards,
Shahram

From: tictoc-bounces@ietf.org [mailto:tictoc-bounces@ietf.org] On Behalf Of=
 Tal Mizrahi
Sent: Saturday, August 06, 2011 10:43 AM
To: Ron Cohen; tictoc@ietf.org
Subject: Re: [TICTOC] The Need for Checksum Extension

Hi,

Sorry for the late reply, I missed this thread.
Ron, your observation is correct.

With that said, from the implementation perspective, there is a benefit to =
have a single procedure (and a single implementation) for updating the UDP =
checksum in a timestamped packet (PTP, NTP, OWAMP, TWAMP). So for PTP the U=
DP Checksum update clearly benefits from the Checksum Trailer. As for NTP a=
nd OWAMP, the benefit of using the Checksum Trailer is from having the same=
 UDP checksum  update flow as the one for PTP.
At the end of the day this draft is about easy implementation - we are tryi=
ng to define the Checksum Trailer in a way that will allow easy implementat=
ion, while not requiring any changes in existing implementations.

Regards,
Tal.
From: tictoc-bounces@ietf.org [mailto:tictoc-bounces@ietf.org] On Behalf Of=
 Ron Cohen
Sent: Friday, July 29, 2011 12:33 AM
To: tictoc@ietf.org
Subject: [TICTOC] The Need for Checksum Extension

Hi,

I'd like to clarify my comment during the meeting.

According to RFC1612 Eqn 3 (incremental checksum update):

HC' =3D ~(C + (-m) + m') =3D ~(~HC + ~m + m')

Where HC' is the updated checksum, HC is the current (message) checksum, m'=
 in the new value that is going to be written instead of the value m in the=
 message.

If I know that value of m is zero, I can calculate the new checksum using t=
he old checksum and the new value alone.

That is, if the NTP/OWAMP/TWAMP CPU sets the transmit timestamp to zero (i.=
e. m =3D 0), the FPGA or switch that measures the transmit timestamp once t=
he first byte of the message is sent on the wire, can update the UDP checks=
um itself incrementally and doesn't need the extension. The extension is ne=
ed only if you have to read the timestamp which appears later in the packet=
 in order to update the checksum.

This is very different from 'real' intermediate devices (i.e. transparent c=
locks) used by PTP.

Best,
Ron

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

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40"><head><META HTTP-EQUIV=3D"Content-Type" CONTENT=
=3D"text/html; charset=3Dus-ascii"><meta name=3DGenerator content=3D"Micros=
oft Word 14 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
	{mso-style-priority:99;
	mso-style-link:"Balloon Text Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:8.0pt;
	font-family:"Tahoma","sans-serif";}
span.EmailStyle17
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
span.EmailStyle18
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
span.BalloonTextChar
	{mso-style-name:"Balloon Text Char";
	mso-style-priority:99;
	mso-style-link:"Balloon Text";
	font-family:"Tahoma","sans-serif";}
span.EmailStyle21
	{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=3DEN-US link=3Dblue vli=
nk=3Dpurple><div class=3DWordSection1><p class=3DMsoNormal><span style=3D'f=
ont-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Hi Shahra=
m,<o:p></o:p></span></p><p class=3DMsoNormal><span style=3D'font-size:11.0p=
t;font-family:"Calibri","sans-serif";color:#1F497D'><o:p>&nbsp;</o:p></span=
></p><p class=3DMsoNormal><span style=3D'font-size:11.0pt;font-family:"Cali=
bri","sans-serif";color:#1F497D'>Please see the presentation from the last =
TICTOC meeting:<o:p></o:p></span></p><p class=3DMsoNormal><span style=3D'fo=
nt-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><a href=3D=
"http://www.ietf.org/proceedings/81/slides/tictoc-1.ppt">http://www.ietf.or=
g/proceedings/81/slides/tictoc-1.ppt</a><o:p></o:p></span></p><p class=3DMs=
oNormal><span style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";=
color:#1F497D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span style=
=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Rega=
rds,<o:p></o:p></span></p><p class=3DMsoNormal><span style=3D'font-size:10.=
0pt;font-family:"Arial","sans-serif";color:#1F497D'>Tal.<o:p></o:p></span><=
/p><p class=3DMsoNormal><span style=3D'font-size:11.0pt;font-family:"Calibr=
i","sans-serif";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=3DMsoNormal><b><span style=3D'font-size:10.0pt;font-family:"Tahoma"=
,"sans-serif"'>From:</span></b><span style=3D'font-size:10.0pt;font-family:=
"Tahoma","sans-serif"'> Shahram Davari [mailto:davari@broadcom.com] <br><b>=
Sent:</b> Monday, August 08, 2011 8:57 PM<br><b>To:</b> Tal Mizrahi; Ron Co=
hen; tictoc@ietf.org<br><b>Subject:</b> RE: [TICTOC] The Need for Checksum =
Extension<o:p></o:p></span></p></div></div><p class=3DMsoNormal><o:p>&nbsp;=
</o:p></p><p class=3DMsoNormal><span style=3D'font-size:11.0pt;font-family:=
"Calibri","sans-serif";color:#1F497D'>Tal,<o:p></o:p></span></p><p class=3D=
MsoNormal><span style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif=
";color:#1F497D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span sty=
le=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>I =
don&#8217;t know about OWAMP but NTP doesn&#8217;t have the concept of TC (=
Transparent Clocking). So why is there a need for UDP checksum update for N=
TP?<o:p></o:p></span></p><p class=3DMsoNormal><span style=3D'font-size:11.0=
pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p>&nbsp;</o:p></spa=
n></p><p class=3DMsoNormal><span style=3D'font-size:11.0pt;font-family:"Cal=
ibri","sans-serif";color:#1F497D'>Also if any of the timing messages needs =
to change in a router (such as Residence&nbsp; time update), the router sho=
uld be able to fully parse that packet including the UDP header. So the rou=
ter would exactly know the UDP checksum location. Therefore I don&#8217;t s=
ee what is the benefit of such Checksum trailer/Extension.<o:p></o:p></span=
></p><p class=3DMsoNormal><span style=3D'font-size:11.0pt;font-family:"Cali=
bri","sans-serif";color:#1F497D'><o:p>&nbsp;</o:p></span></p><p class=3DMso=
Normal><span style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";c=
olor:#1F497D'>Regards,<o:p></o:p></span></p><p class=3DMsoNormal><span styl=
e=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Sha=
hram<o:p></o:p></span></p><p class=3DMsoNormal><span style=3D'font-size:11.=
0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p>&nbsp;</o:p></sp=
an></p><div><div style=3D'border:none;border-top:solid #B5C4DF 1.0pt;paddin=
g:3.0pt 0in 0in 0in'><p class=3DMsoNormal><b><span style=3D'font-size:10.0p=
t;font-family:"Tahoma","sans-serif"'>From:</span></b><span style=3D'font-si=
ze:10.0pt;font-family:"Tahoma","sans-serif"'> tictoc-bounces@ietf.org [mail=
to:tictoc-bounces@ietf.org] <b>On Behalf Of </b>Tal Mizrahi<br><b>Sent:</b>=
 Saturday, August 06, 2011 10:43 AM<br><b>To:</b> Ron Cohen; tictoc@ietf.or=
g<br><b>Subject:</b> Re: [TICTOC] The Need for Checksum Extension<o:p></o:p=
></span></p></div></div><p class=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=
=3DMsoNormal>Hi,<o:p></o:p></p><p class=3DMsoNormal><o:p>&nbsp;</o:p></p><p=
 class=3DMsoNormal>Sorry for the late reply, I missed this thread.<o:p></o:=
p></p><p class=3DMsoNormal>Ron, your observation is correct.<o:p></o:p></p>=
<p class=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3DMsoNormal>With that sa=
id, from the implementation perspective, there is a benefit to have a singl=
e procedure (and a single implementation) for updating the UDP checksum in =
a timestamped packet (PTP, NTP, OWAMP, TWAMP). So for PTP the UDP Checksum =
update clearly benefits from the Checksum Trailer. As for NTP and OWAMP, th=
e benefit of using the Checksum Trailer is from having the same UDP checksu=
m &nbsp;update flow as the one for PTP.<o:p></o:p></p><p class=3DMsoNormal>=
At the end of the day this draft is about easy implementation - we are tryi=
ng to define the Checksum Trailer in a way that will allow easy implementat=
ion, while not requiring any changes in existing implementations.<o:p></o:p=
></p><p class=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3DMsoNormal>Regards=
,<span style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p><=
/o:p></span></p><p class=3DMsoNormal><span style=3D'font-size:10.0pt;font-f=
amily:"Arial","sans-serif"'>Tal.</span><o:p></o:p></p><p class=3DMsoNormal>=
<b><span style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:=
</span></b><span style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif=
"'> tictoc-bounces@ietf.org [mailto:tictoc-bounces@ietf.org] <b>On Behalf O=
f </b>Ron Cohen<br><b>Sent:</b> Friday, July 29, 2011 12:33 AM<br><b>To:</b=
> tictoc@ietf.org<br><b>Subject:</b> [TICTOC] The Need for Checksum Extensi=
on<o:p></o:p></span></p><p class=3DMsoNormal><o:p>&nbsp;</o:p></p><div><p c=
lass=3DMsoNormal style=3D'margin-bottom:12.0pt'>Hi,<br><br>I'd like to clar=
ify my comment during the meeting.<br><br>According to RFC1612 Eqn 3 (incre=
mental checksum update):<br><br>HC' =3D ~(C + (-m) + m') =3D ~(~HC + ~m + m=
')<br><br>Where HC' is the updated checksum, HC is the current (message) ch=
ecksum, m' in the new value that is going to be written instead of the valu=
e m in the message.<br><br>If I know that value of m is zero, I can calcula=
te the new checksum using the old checksum and the new value alone.<br><br>=
That is, if the NTP/OWAMP/TWAMP CPU sets the transmit timestamp to zero (i.=
e. m =3D 0), the FPGA or switch that measures the transmit timestamp once t=
he first byte of the message is sent on the wire, can update the UDP checks=
um itself incrementally and doesn't need the extension. The extension is ne=
ed only if you have to read the timestamp which appears later in the packet=
 in order to update the checksum.<br><br>This is very different from 'real'=
 intermediate devices (i.e. transparent clocks) used by PTP.<br><br>Best,<b=
r>Ron<o:p></o:p></p></div></div></body></html>=

--_000_74470498B659FA4687F0B0018C19A89C014735063F73ILMB01marve_--

From david.marlow@navy.mil  Mon Aug 15 13:10:32 2011
Return-Path: <david.marlow@navy.mil>
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 EB9B821F8D23 for <tictoc@ietfa.amsl.com>; Mon, 15 Aug 2011 13:10:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.082
X-Spam-Level: 
X-Spam-Status: No, score=-1.082 tagged_above=-999 required=5 tests=[AWL=-0.897, BAYES_40=-0.185]
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 mxRrRIoYMQxt for <tictoc@ietfa.amsl.com>; Mon, 15 Aug 2011 13:10:31 -0700 (PDT)
Received: from naeanrfkax11o.nmci.navy.mil (naeanrfkax11o.nmci.navy.mil [138.162.5.156]) by ietfa.amsl.com (Postfix) with ESMTP id 3931021F8D19 for <tictoc@ietf.org>; Mon, 15 Aug 2011 13:10:30 -0700 (PDT)
X-AuditID: 8aa2059b-b7b5aae000007cc3-6d-4e497d4bb10a
Received: from naeanrfkeg01v.nadsusea.nads.navy.mil (gate5-norfolk.nmci.navy.mil [138.162.0.45]) by  (Symantec Mail Security) with SMTP id CD.BE.31939.B4D794E4; Mon, 15 Aug 2011 20:10:51 +0000 (GMT)
Received: from naeanrfkeb04v.nadsusea.nads.navy.mil ([10.16.20.107]) by naeanrfkeg01v.nadsusea.nads.navy.mil with Microsoft SMTPSVC(6.0.3790.4675); Mon, 15 Aug 2011 16:10:50 -0400
Received: from naeanrfkeb01v.nadsusea.nads.navy.mil ([10.16.20.105]) by naeanrfkeb04v.nadsusea.nads.navy.mil with Microsoft SMTPSVC(6.0.3790.4675); Mon, 15 Aug 2011 16:10:50 -0400
Received: from naeamillez04v.nadsusea.nads.navy.mil ([10.16.20.64]) by naeanrfkeb01v.nadsusea.nads.navy.mil with Microsoft SMTPSVC(6.0.3790.4675); Mon, 15 Aug 2011 16:10:49 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Mon, 15 Aug 2011 16:10:49 -0400
Content-Type: multipart/signed; protocol="application/x-pkcs7-signature"; micalg=SHA1; boundary="----=_NextPart_000_01C7_01CC5B65.E59C44F0"
Message-ID: <A3E5B6E9262F674FA0C82876819BBD041042BF@naeamillez04v.nadsusea.nads.navy.mil>
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator: 
Thread-Topic: Hardware time-stamps based on programmable packet network sequences
Thread-Index: Acxbh2yFTz4yQZ96R5SfrcmptuDCjA==
From: "Marlow, David T CIV NSWCDD, W64" <david.marlow@navy.mil>
To: "Greg Dowd" <GDowd@symmetricom.com>
X-OriginalArrivalTime: 15 Aug 2011 20:10:49.0876 (UTC) FILETIME=[6D439540:01CC5B87]
X-Brightmail-Tracker: AAAAAA==
Cc: tictoc@ietf.org
Subject: [TICTOC] Hardware time-stamps based on programmable packet network sequences
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, 15 Aug 2011 20:10:32 -0000

This is a multi-part message in MIME format.

------=_NextPart_000_01C7_01CC5B65.E59C44F0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit

Greg,
   During my discussion of "Network Time Mechanisms for Improving Computer Clock Accuracy" at the Quebec City TicToc meeting you mentioned that there are products today that can provide a hardware time stamp based on a programmable sequence off a packet data network that is not tied to IEEE 1588.  I would appreciate any references you could provide on this.  In particular are there any products that work with PCs over gigabit Ethernet networks?

  Dave

------=_NextPart_000_01C7_01CC5B65.E59C44F0
Content-Type: application/x-pkcs7-signature;
	name="smime.p7s"
Content-Transfer-Encoding: base64
Content-Disposition: attachment;
	filename="smime.p7s"

MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIIRXzCCA3Aw
ggJYoAMCAQICAQUwDQYJKoZIhvcNAQEFBQAwWzELMAkGA1UEBhMCVVMxGDAWBgNVBAoTD1UuUy4g
R292ZXJubWVudDEMMAoGA1UECxMDRG9EMQwwCgYDVQQLEwNQS0kxFjAUBgNVBAMTDURvRCBSb290
IENBIDIwHhcNMDQxMjEzMTUwMDEwWhcNMjkxMjA1MTUwMDEwWjBbMQswCQYDVQQGEwJVUzEYMBYG
A1UEChMPVS5TLiBHb3Zlcm5tZW50MQwwCgYDVQQLEwNEb0QxDDAKBgNVBAsTA1BLSTEWMBQGA1UE
AxMNRG9EIFJvb3QgQ0EgMjCCASIwDQYJKoZIhvcNAQEBBQADggEPADCCAQoCggEBAMAswfaNO6z/
PzzWcb64dCIH7HBBFfyrQOMHqsHD2J/+2kw6vz/I2Ch7SzYBwKxFJcPSDgqPhRhkED0aE3Aqb47X
3I2Ts0EPOCHNravCPSoF01cRNw3NjFH5k+PMRkkhjhS0zcsUPjjNcjHuqxLyZeo0LlZd/+5jdctt
upE0/J7z9C0cvlDEQt9ZiP9qs/qobD3LVnFxBZa7n4DlgEVZZ0Gw68OtYKSAdQYXnA70Q+CZDhv7
f/WzzLKBgrH9MsG4vkGkZLVgOlpRMIzO3kEsGUdcSRBkuXSph0GvfW66wbihv2UxOgRn+bW7jpKK
AGO4seaMOF+D/1DVO6Jda7IQzGMCAwEAAaM/MD0wHQYDVR0OBBYEFEl0uwxeunr+AlTve6DGlcYJ
gHCWMAsGA1UdDwQEAwIBhjAPBgNVHRMBAf8EBTADAQH/MA0GCSqGSIb3DQEBBQUAA4IBAQCYkY0/
ici79cBpcyk7Nay6swh2PXAJkumERCEBfRR2G+5RbB2NFTctezFp9JpEuK9GzDT6I8sDJxnSgyF1
K+fgG5km3IRAleio0sz2WFxm7z9KlxCCHboKot1bBiudp2RO6y4BNaS0PxOtVeTVc6hpmxHxmPIx
Hm9A1Ph4n46RoG9wBJBmqgYrzuF6krV94eDRluehOi3MsZ0fBUTth5nTTRpwOcEEDOV+2fGv1yAO
8SJ6JaRzmcw/pAcnlqiile2CuRbTnguHwsHyiPVi32jfx7xpUe2xXNxUVCkPCTmarAPB2wxNrm8K
ehZJ8b+R0jiU0/aVLLdsyUK2jcqQjYXZMIIEJzCCAw+gAwIBAgICYqkwDQYJKoZIhvcNAQEFBQAw
XTELMAkGA1UEBhMCVVMxGDAWBgNVBAoTD1UuUy4gR292ZXJubWVudDEMMAoGA1UECxMDRG9EMQww
CgYDVQQLEwNQS0kxGDAWBgNVBAMTD0RPRCBFTUFJTCBDQS0yMDAeFw0wODA4MjUwMDAwMDBaFw0x
MTA4MjQyMzU5NTlaMHUxCzAJBgNVBAYTAlVTMRgwFgYDVQQKEw9VLlMuIEdvdmVybm1lbnQxDDAK
BgNVBAsTA0RvRDEMMAoGA1UECxMDUEtJMQwwCgYDVQQLEwNVU04xIjAgBgNVBAMTGU1BUkxPVy5E
QVZJRC5ULjEyMjk1MTc3NDcwgZ8wDQYJKoZIhvcNAQEBBQADgY0AMIGJAoGBAKclyw8dyfR6AlaS
3GZgN6qGyFKyleGJtluaEG+wZOtzChGYY9om5legIH2gE3Mx7AdV9QhT06JfvB058x9WC6eNgUOf
z29hPSYjvOGnwd2t1bN3mLZhui/EGzycxOGrcZBc7LwlJTmtTp9bUR8mwzzZQ8XATYQ2VAJh9vLB
lbcJAgMBAAGjggFbMIIBVzAfBgNVHSMEGDAWgBSyv24AbblASS9gCvR41XmEJakxujA/BgNVHR8E
ODA2MDSgMqAwhi5odHRwOi8vY3JsLmRpc2EubWlsL2dldGNybD9ET0QlMjBFTUFJTCUyMENBLTIw
MA4GA1UdDwEB/wQEAwIFIDAWBgNVHSAEDzANMAsGCWCGSAFlAgELCTAdBgNVHQ4EFgQUblIt3o8n
zT4ODrEDtpIbcG6z6wswbQYIKwYBBQUHAQEEYTBfMDsGCCsGAQUFBzAChi9odHRwOi8vY3JsLmRp
c2EubWlsL2dldHNpZ24/RE9EJTIwRU1BSUwlMjBDQS0yMDAgBggrBgEFBQcwAYYUaHR0cDovL29j
c3AuZGlzYS5taWwwIAYDVR0RBBkwF4EVZGF2aWQubWFybG93QG5hdnkubWlsMBsGA1UdCQQUMBIw
EAYIKwYBBQUHCQQxBBMCVVMwDQYJKoZIhvcNAQEFBQADggEBAGij5yb7+ORwjGR///efjMjXEt69
mlC2WYd8yURLdQh8sFoL7vnenaVP/grCJRYx3dZ6orUgsy3fuFns+aScoaJOI9POcpq3+biScx8j
yF+45Egm3cCa7mOsGHVxMFhVsQKyaBjpIhVHCW8UDr5uy4I3m2tTseSzjdHaKnOav2SuS6gRqWsu
2oM4PpnxKDPoUgAqrFvwL8EchHHhJjRdrTuRY5cB8U76DERyjbSKfaTkRxQbZhgZz6qe5fIb5pVU
CXEhD7T2/BabUyVvLwQzitKu50Vy2y/hl51qNxswb80jOuZvjCHo/wxbcITUjIsb6SWZLUU3l9d5
kOh5n/0tDP4wggRyMIIDWqADAgECAgJiqzANBgkqhkiG9w0BAQUFADBdMQswCQYDVQQGEwJVUzEY
MBYGA1UEChMPVS5TLiBHb3Zlcm5tZW50MQwwCgYDVQQLEwNEb0QxDDAKBgNVBAsTA1BLSTEYMBYG
A1UEAxMPRE9EIEVNQUlMIENBLTIwMB4XDTA4MDgyNTAwMDAwMFoXDTExMDgyNDIzNTk1OVowdTEL
MAkGA1UEBhMCVVMxGDAWBgNVBAoTD1UuUy4gR292ZXJubWVudDEMMAoGA1UECxMDRG9EMQwwCgYD
VQQLEwNQS0kxDDAKBgNVBAsTA1VTTjEiMCAGA1UEAxMZTUFSTE9XLkRBVklELlQuMTIyOTUxNzc0
NzCBnzANBgkqhkiG9w0BAQEFAAOBjQAwgYkCgYEAzuIvWfvM234NwZA61e6685cHFdkujDC+EFap
1z8+KB3R6Qy9kCdDoT82xq3o3kkWPlCNGE+UmzkQPqzFjOs1Su7FvVoHOHD/ia61BdaeprPpD5Ue
KdEFxWJWK7zpRo6+7p3rGD/MqVMKYwhi0nJx8LKkCFJJcUh9n3MWHzidzL0CAwEAAaOCAaYwggGi
MB8GA1UdIwQYMBaAFLK/bgBtuUBJL2AK9HjVeYQlqTG6MD8GA1UdHwQ4MDYwNKAyoDCGLmh0dHA6
Ly9jcmwuZGlzYS5taWwvZ2V0Y3JsP0RPRCUyMEVNQUlMJTIwQ0EtMjAwDgYDVR0PAQH/BAQDAgbA
MBYGA1UdIAQPMA0wCwYJYIZIAWUCAQsJMB0GA1UdDgQWBBTR+wwqoLEgNDHCcAt/4eWAd2VFeTBt
BggrBgEFBQcBAQRhMF8wOwYIKwYBBQUHMAKGL2h0dHA6Ly9jcmwuZGlzYS5taWwvZ2V0c2lnbj9E
T0QlMjBFTUFJTCUyMENBLTIwMCAGCCsGAQUFBzABhhRodHRwOi8vb2NzcC5kaXNhLm1pbDBABgNV
HREEOTA3gRVkYXZpZC5tYXJsb3dAbmF2eS5taWygHgYKKwYBBAGCNxQCA6AQDA4xMjI5NTE3NzQ3
QG1pbDAbBgNVHQkEFDASMBAGCCsGAQUFBwkEMQQTAlVTMCkGA1UdJQQiMCAGCisGAQQBgjcUAgIG
CCsGAQUFBwMCBggrBgEFBQcDBDANBgkqhkiG9w0BAQUFAAOCAQEAXB5mROeOH5MmltAiRLZ+EXfu
S8Y/ljoxdylHrnvT+YY6KPg99DHB3p75lFXZaOK/7pi/lSYev7W0d28LQoJSHPyfgA5DQFNyt18U
t+6VA157uMdyGw4dzQl0az9qevKX3Ssqa3vm0dR1kI46DVNRfHjZLsTyiOSfI6daOhOvUXyQ8Fok
kmy3KxFloxGUyMFsI6rxMZps0YUwzOETZCQ9RU3lQy0aemB52q7tONA6KeRL+fKdeprlyh3cWOZL
3XBSNUDmws5NbQVkCUuJvR6rvDBmGm4KHAB+Y8yiouKKEyNIqNf+HGybMpw+CP2ygeV/qCSc4y+8
KGA2vqYcx2Kr4DCCBUYwggQuoAMCAQICASswDQYJKoZIhvcNAQEFBQAwWzELMAkGA1UEBhMCVVMx
GDAWBgNVBAoTD1UuUy4gR292ZXJubWVudDEMMAoGA1UECxMDRG9EMQwwCgYDVQQLEwNQS0kxFjAU
BgNVBAMTDURvRCBSb290IENBIDIwHhcNMDgwNDIzMjEwODU2WhcNMTQwNDIzMjAwODU2WjBdMQsw
CQYDVQQGEwJVUzEYMBYGA1UEChMPVS5TLiBHb3Zlcm5tZW50MQwwCgYDVQQLEwNEb0QxDDAKBgNV
BAsTA1BLSTEYMBYGA1UEAxMPRE9EIEVNQUlMIENBLTIwMIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8A
MIIBCgKCAQEAtxqQiRyAC9uhuiXsLqP2LQGIVeYW0U+dyVOcpin5iEHx3Z0yJp8HMyG2R0ECIDyl
0krLu8uBT2FB0PbI7mimxvd4erQsUB3+izK2WjJ5kTBR8CFKmKkS0y50mU/m+tW4J4j4ySGgxbN9
t1aqe5dDnCA0ToGJOo48FhKMu6izjGDXebzv4Su0fJEEJ45zTkg0AuX7rrTOg53YleQU+DPfNqxO
+OlSOddW5DLCTW5IN2/15UY3EmMyScJPi/40mcjs+Obfroagfz1IIGOkSS1BPv6dQnyBRuYdkuN0
0gIIVIhgK2UxqXOA+pf4ajbUgytk8M1hYeHCWJS2yuIxstkaYQIDAQABo4ICETCCAg0wDgYDVR0P
AQH/BAQDAgGGMB8GA1UdIwQYMBaAFEl0uwxeunr+AlTve6DGlcYJgHCWMB0GA1UdDgQWBBSyv24A
bblASS9gCvR41XmEJakxujAMBgNVHSQEBTADgAEAMBIGA1UdEwEB/wQIMAYBAf8CAQAwVwYDVR0g
BFAwTjALBglghkgBZQIBCwUwCwYJYIZIAWUCAQsJMAsGCWCGSAFlAgELCjALBglghkgBZQIBCxIw
CwYJYIZIAWUCAQsTMAsGCWCGSAFlAgELFDA/BgNVHR8EODA2MDSgMqAwhi5odHRwOi8vY3JsLmRp
c2EubWlsL2dldGNybD9Eb0QlMjBSb290JTIwQ0ElMjAyMIH+BggrBgEFBQcBAQSB8TCB7jA/Bggr
BgEFBQcwAoYzaHR0cDovL2NybC5kaXNhLm1pbC9nZXRJc3N1ZWRUbz9Eb0QlMjBSb290JTIwQ0El
MjAyMCAGCCsGAQUFBzABhhRodHRwOi8vb2NzcC5kaXNhLm1pbDCBiAYIKwYBBQUHMAKGfGxkYXA6
Ly9jcmwuZ2RzLmRpc2EubWlsL2NuJTNkRG9EJTIwUm9vdCUyMENBJTIwMiUyY291JTNkUEtJJTJj
b3UlM2REb0QlMmNvJTNkVS5TLiUyMEdvdmVybm1lbnQlMmNjJTNkVVM/Y0FDZXJ0aWZpY2F0ZTti
aW5hcnkwDQYJKoZIhvcNAQEFBQADggEBAG0FZT/B2dXxsgbWCM2O5Yug5kYCfaWmZJsvExK0AZih
9Yw6gUsFI6btzeuwBStEMU4E121DHdopUav5wa+WdOFoHkhPTly8yrAkQ6LsQCsRAtsII1yVvDV2
NdBisXby2Tn/wLXYqNuuoWn6pf5d9D4FtQyF98w+0MKwRFsJw+aDXM4uS3UoqfjtWCyWS50mBr12
ho03JCRUHc/MF1EI8IaSfEe/t+37OF0Ubi7qU9Oq4a77JpD0+vTvWWt1by8oWZsfHr7Xnd6uVV0r
FJ8WmgtwhvORQtMjaKLyvzY3rxS6gG9hRzK+h0x3eW6oWczEFxQ5I72uIZz9ubr4c9zgpxoxggKu
MIICqgIBATBjMF0xCzAJBgNVBAYTAlVTMRgwFgYDVQQKEw9VLlMuIEdvdmVybm1lbnQxDDAKBgNV
BAsTA0RvRDEMMAoGA1UECxMDUEtJMRgwFgYDVQQDEw9ET0QgRU1BSUwgQ0EtMjACAmKrMAkGBSsO
AwIaBQCgggGhMBgGCSqGSIb3DQEJAzELBgkqhkiG9w0BBwEwHAYJKoZIhvcNAQkFMQ8XDTExMDgx
NTIwMTA0OFowIwYJKoZIhvcNAQkEMRYEFGMSbDN4EDae8VYAY6JEEgQb6tRHMFgGCSqGSIb3DQEJ
DzFLMEkwCgYIKoZIhvcNAwcwDgYIKoZIhvcNAwICAgCAMAcGBSsOAwIHMA0GCCqGSIb3DQMCAgEo
MAcGBSsOAwIaMAoGCCqGSIb3DQIFMHIGCSsGAQQBgjcQBDFlMGMwXTELMAkGA1UEBhMCVVMxGDAW
BgNVBAoTD1UuUy4gR292ZXJubWVudDEMMAoGA1UECxMDRG9EMQwwCgYDVQQLEwNQS0kxGDAWBgNV
BAMTD0RPRCBFTUFJTCBDQS0yMAICYqkwdAYLKoZIhvcNAQkQAgsxZaBjMF0xCzAJBgNVBAYTAlVT
MRgwFgYDVQQKEw9VLlMuIEdvdmVybm1lbnQxDDAKBgNVBAsTA0RvRDEMMAoGA1UECxMDUEtJMRgw
FgYDVQQDEw9ET0QgRU1BSUwgQ0EtMjACAmKpMA0GCSqGSIb3DQEBAQUABIGAqugD0pF6t0ABl7XH
wPoKaS9aG/X6oX6Ah7WQc2uYkpEXoT7dtD8ZQ9iPpwfuSWqmT6rGHqH+S9DHDxmINY+wz41Xmh0P
ylVkRjAz/Wrsff/OJgJu9WYRZfCLaXFB2IDQMmPYbJWprYz4XCPS8TDO68MUThX9S2vomL6X8bAP
4n4AAAAAAAA=

------=_NextPart_000_01C7_01CC5B65.E59C44F0--

From odonoghue@isoc.org  Mon Aug 15 16:29:06 2011
Return-Path: <odonoghue@isoc.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 5463311E8091 for <tictoc@ietfa.amsl.com>; Mon, 15 Aug 2011 16:29:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.196
X-Spam-Level: 
X-Spam-Status: No, score=-102.196 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, DATE_IN_PAST_06_12=1.069, IP_NOT_FRIENDLY=0.334, RCVD_IN_DNSWL_LOW=-1, 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 gfO6NeAtSlt1 for <tictoc@ietfa.amsl.com>; Mon, 15 Aug 2011 16:29:05 -0700 (PDT)
Received: from smtp115.dfw.emailsrvr.com (smtp115.dfw.emailsrvr.com [67.192.241.115]) by ietfa.amsl.com (Postfix) with ESMTP id 58FD711E8070 for <tictoc@ietf.org>; Mon, 15 Aug 2011 16:29:05 -0700 (PDT)
Received: from localhost (localhost.localdomain [127.0.0.1]) by smtp21.relay.dfw1a.emailsrvr.com (SMTP Server) with ESMTP id 062972405EF for <tictoc@ietf.org>; Mon, 15 Aug 2011 19:29:52 -0400 (EDT)
X-Virus-Scanned: OK
Received: by smtp21.relay.dfw1a.emailsrvr.com (Authenticated sender: odonoghue-AT-isoc.org) with ESMTPSA id 8D1BE240613 for <tictoc@ietf.org>; Mon, 15 Aug 2011 19:29:51 -0400 (EDT)
Message-ID: <4E492C75.9020507@isoc.org>
Date: Mon, 15 Aug 2011 10:25:57 -0400
From: Karen O'Donoghue <odonoghue@isoc.org>
Organization: ISOC
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.2.18) Gecko/20110616 Thunderbird/3.1.11
MIME-Version: 1.0
To: tictoc@ietf.org
Content-Type: multipart/mixed; boundary="------------020501060109070004010108"
Subject: [TICTOC] draft minutes of tictoc meeting at IETF 81
X-BeenThere: tictoc@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: odonoghue@isoc.org
List-Id: Timing over IP Connection and Transfer of Clock BOF <tictoc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tictoc>, <mailto:tictoc-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tictoc>
List-Post: <mailto:tictoc@ietf.org>
List-Help: <mailto:tictoc-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tictoc>, <mailto:tictoc-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 15 Aug 2011 23:29:06 -0000

This is a multi-part message in MIME format.
--------------020501060109070004010108
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

Folks,

Below are the draft minutes for the recent tictoc meeting. Thanks to 
Dave Marlow for the timely production of the minutes. Please review and 
submit any comments or changes as soon as possible.

Regards,
Karen



--------------020501060109070004010108
Content-Type: text/plain;
 name="tictoc81 draft minutes_15aug11.txt"
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
 filename="tictoc81 draft minutes_15aug11.txt"

Minutes for TICTOC meeting @ IETF-80
28 July 2011, 15:20 EDT (19:20 UTC) 

The meeting started at 15:20 EDT.  Karen O'Donoghue and Yaakov Stein chaired the meeting
Dave Marlow took minutes.  Karen was jabber scribe.

Karen bashed the agenda and the blue sheets were distributed.  Karen provided the status 
for the Working group since the last meeting: 3 working group drafts, 3 individual 
submissions, and no interim meetings. 

Stefano Ruffino provided slides for an ITU-T SG15/Q13 update which Yaakov presented.  
SG15/Q13 had an interim meeting in May 2011.  There were two primary topics of 
interest to TICTOC: (1) Packet timing performance aspects for frequency (G.826x series);
and (2)Time Sync in packet networks (G.827x series).  The frequency work is maturing
while the time/phase work has its requirements document (G.8271) updated and other
documents are identified and being started.  SG15/Q13 is also working on a definition 
and terminology document for both frequency and time of day (G.8260).


Yang Cui provided a Security Requirements discussion based on IPsec security for packet 
based synchronization, draft-xu-tictoc-ipsec-security-for-synchronization-01.  As described
by its Abstract, this document analyses the need for security methods for synchronization 
messages distributed over the Internet and gives a solution on how to mark the 
synchronization message when IPSec is implemented in end to end frequency synchronization.
It was pointed out that the Introduction has requirements language (i.e. SHALLs) and 
these will need to be taken out of this section.   There was considerable discussion on
the IEEE 1588 PTP use case across the Internet where Yaakov and Greg Dowd pointed out you 
cannot have transparent clocks you must tunnel.  On a discussion of whether to encrypt 
packets across 3GPP, someone from the jabber room pointed out that with 3GPP you must 
encrypt.  Yaakov asked whether the authors have talked with anyone in the closing IPsec 
WG about this draft and Yang indicated that he has and they do not have any questions.  
Karen asked whether the Working Group thought this work should be pursued, but got little 
feedback.  Peter Lothberg said that in some use cases this could be useful but this 
provides no value for the Internet use case.  Yang said that the femtocell is getting 
greater use and there is no protection in the femtocell.  Greg Dowd said that femtocells 
are meant to provide telephone calls and that they can be stopped by dropping all data.  
He said we needed to clarify the threat models we are building the security for.

Karen discussed time synchronization protocol security requirements.  The expired 
TICTOC Requirements draft had recently been resubmitted 
(draft-ietf-tictoc-requirements-01).  This draft identifies three security mechanisms to
consider.  Karen went over a survey that was done at the beginning of the TICTOC work 
where four questions were identified that cover the different aspects for possible 
security services.  Karen said that a volunteer editor has been identified to work on 
general time synchronization security requirements.  The goal is to have a draft by the 
next meeting.

Greg Dowd provided a PTPv2 MIB discussion based on draft-ietf-tictoc-ptp-mib-00.  This 
MIB goes beyond the earlier drafts that only covered the PTPv2 telecom profile.  This 
MIB covers all the PTPv2 devices.  The current draft is in its third version and
Greg felt it was now semantically correct.  Asked whether this MIB has been deployed, 
Greg said that it has.  Measuring the performance of a PTPv2 node is outside the 
present scope, but this could be added later.  Yaakov asked whether there was
commonality between this MIB and the NTPv4 MIB (RFC 5907), Greg said that this 
MIB was PTPv2 specific with little commonality to the NTP MIB.  Dave Marlow said 
that he had read the draft and found little commonality with the NTP MIB but was 
very supportive of this draft which appears very thorough.  The Chairs said that 
there needs to be MIB Doctor review (which they would pursue) and review by
TICTOC participants for this draft to progress.

Yaakov lead a discussion on Transporting PTP messages (IEEE 1588) over MPLS Networks, 
draft-ietf-tictoc-1588overmpls-01.  He said that the draft very mature with three 
individual drafts and now one TICTOC version.  There has been considerable discussion
on the list.  Yaakov asked what was needed before this goes to WGLC?  Luca Martini 
said that there are some text formatting issues and that some sections have given a
a wrong impression.  Of particular concern were the two modes (IP over MPLS and 
Pseudowire), Pseudowire is not needed if timing is a service of the network and there
is only one clock over the network.  Pseudowire is needed if PTP is used directly over
Ethernet, and Yaakov pointed out that in many parts of the world there are many clocks 
that a carrier transports separately.  There were some concerns from the MPLS 
community, George Swallow pointed out an issue with fast reroute to address a fault.  
There were concerns whether the draft was ready for last call or not, and what 
procedure should be taken to get comments from the MPLS community.  George suggested 
to at least announce to the MPLS list about a WGLC in TICTOC.
 
Tal Mizrahi briefed UDP Checksum Trailer in Timing Protocols, 
draft-mizrahi-tictoc-checksum-trailer-00.  This draft proposes a Checksum Trailer 
extension to NTP, OWAMP and TWAMP that allows intermediate nodes to reflect the 
checksum modification in the last 2 octets of the packet rather than in the UDP 
checksum field.  This is to bring a capability already in IEEE 1588 into these other 
protocols.  Yaakov asked why this is being brought into OWAMP and TWAMP.  Tal said 
these are performance protocols that transfer time and could be benefited as well.  
An issue related to the NTP extension field had been raised and discussed on the 
mailing list.  This proposed technique requires an extension field without 
authentication (i.e. without a MAC) to be practical; however, the NTPv4 spec 
(i.e. RFC 5905) REQUIRES all extension fields to include authentication.  
Discussion on the list included opinions that the RFC was wrong and this is not 
a requirement for NTPv4.  Additional effort is needed to determine if NTPv4 spec 
should be changed or not.  Yaakov pointed out that both OWAMP and TWAMP have 
authenticated modes.  This draft is intended for non authenticated packets only.  
Yaakov said that in the case of OWAMP this is very limiting because its default is 
to be authenticated.  In addition Yaakov said that OWAMP and TWAMP would require 
an extension to their control protocols.  OWAMP and TWAMP are IPPM protocols, the 
Chairs took an action to send this draft to the IPPM chairs.  Tal was asked 
whether the mechanisms discussed in the draft had been implemented and he 
said the mechanisms had not yet been implemented.  

Dave Marlow discussed Network Time Mechanisms for Improving Computer Clock Accuracy, 
draft-marlow-tictoc-computer-clock-accuracy-00.  This draft had not been updated 
since the last meeting but Dave briefed the discussion that had been on the list.  
Vladimir Smotlacha provided to the list, references to his papers describing NTP 
servers which use OCXO oscillators to achieve much higher synchronization accuracy 
than the experimental results described in this draft.  The use case in the draft 
covers client accuracy and thus is outside the Vladimir's use case which addresses 
server accuracy.  In June, Karen had forwarded a note from Dave Mills to the list 
which mentioned that additional experimental results with NTP Interleave are in his 
book.  Dave Mill's book provides experimental results for both an unloaded scenario 
(which is a very similar to the experiment described in the draft) and a loaded
scenario.  Dave Mills, in his email, pointed out that Interleave showed greater 
improvement in the loaded scenarios and with digest computations (e.g. Autokey).  
Dave Marlow and Tim Plunkett are looking at the experimental results in the book and
comparing this to their results.  Tim Frost provided a paper on Minimum Time-Dispersion
Metrics  to the list. Dave indicated that this provides direction towards identifying 
a common set of metrics for network time synchronization experiments.  A common set of
metrics or perhaps a benchmarking draft could be a candidate for future TICTOC work. 
Greg Dowd said that there are products on the market that can provide a hardware time 
stamp based on a programmable sequence off of a packet data network, this provides a
direction for the second mechanism outlined in the draft.  Yaakov mentioned that
his company tried NTP interleave on their highly optimized products and did not
see a significant difference in performance.   Dave said he and Tim Plunkett would 
like to update their draft with the new information.  He solicited comments and 
contributions on mechanisms to achieve greater client accuracy.  

Karen led an additional NTP discussion.  The NTP control protocol which is an
appendix of RFC 1305 (NTPv3) is not in a current standard since RFC 1305 was deprecated.
Volunteers are needed to get this important work documented and standardized.  Brian 
Haberman (along with Karen, co-chair of the NTP working group) suggested in line with 
Dave Hart to get rid of mode 7 and just document mode 6.  Harlan Stenn, via jabber
requested that mode 7 be documented as well.  Dave Hart, via jabber, said that mode 7 
is fragile and vendor specific, so that there is no use in standardizing it.  Harlan
volunteered to document the NTP control protocol.  It was pointed out that RFC 5905 needs 
to be redone since mode 6 is identified for future use; however, if this is an IANA 
controlled field then just a change by IANA is needed.  Karen asked for volunteers to
document the NTP interleave extensions.  There has been email on list discussing Autokey
bugs/vulnerabilities being found by PTB (Germany's Standards Organization).  There were
no details discussed at this meeting but this is a concern that must be followed.  There
was a short discussion on what work would be carried out in the NTP WG and what should 
be done in the TICTOC WG.  Brian said that all NTP control protocol work should be done 
in the NTP WG but he had no opinion at this time as to where Interleave work should be 
done.  All co-chairs agreed that email on any NTP topic should be sent to both lists.

The meeting adjourned at 17:20 EDT (21:20 UTC). 






--------------020501060109070004010108--

From kevin.gross@comcast.net  Mon Aug 15 20:46:20 2011
Return-Path: <kevin.gross@comcast.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 422FE21F8B12 for <tictoc@ietfa.amsl.com>; Mon, 15 Aug 2011 20:46:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.598
X-Spam-Level: 
X-Spam-Status: No, score=-102.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=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 Ih1MgJqs+JPr for <tictoc@ietfa.amsl.com>; Mon, 15 Aug 2011 20:46:17 -0700 (PDT)
Received: from qmta11.emeryville.ca.mail.comcast.net (qmta11.emeryville.ca.mail.comcast.net [76.96.27.211]) by ietfa.amsl.com (Postfix) with ESMTP id 8A90121F8B03 for <tictoc@ietf.org>; Mon, 15 Aug 2011 20:46:17 -0700 (PDT)
Received: from omta06.emeryville.ca.mail.comcast.net ([76.96.30.51]) by qmta11.emeryville.ca.mail.comcast.net with comcast id Lrmv1h00316AWCUABrn08G; Tue, 16 Aug 2011 03:47:00 +0000
Received: from AVADesk2 ([98.245.120.114]) by omta06.emeryville.ca.mail.comcast.net with comcast id Lrn21h00Q2UBLVN8Srn32V; Tue, 16 Aug 2011 03:47:03 +0000
From: "Kevin Gross" <kevin.gross@comcast.net>
To: <tictoc@ietf.org>
References: <CALMYT9Qt7HAWA6mAe7m+58=_jQ68a0bhnNq97KFU22_4yf4xKA@mail.gmail.com> <2C2F1EBA8050E74EA81502D5740B4BD6A9327F9E2C@SJEXCHCCR02.corp.ad.broadcom.com>
In-Reply-To: <2C2F1EBA8050E74EA81502D5740B4BD6A9327F9E2C@SJEXCHCCR02.corp.ad.broadcom.com>
Date: Mon, 15 Aug 2011 21:47:04 -0600
Organization: AVA Networks
Message-ID: <038101cc5bc7$2a7bd5c0$7f738140$@comcast.net>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_0382_01CC5B94.DFE3AFB0"
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQIoVun+ZbdmKC1YaryAp7Gc/q4xuwFB78EhlFx3fmA=
Content-Language: en-us
X-Mailman-Approved-At: Mon, 15 Aug 2011 23:04:27 -0700
Subject: Re: [TICTOC] DSCP for PTP
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, 16 Aug 2011 03:46:20 -0000

This is a multipart message in MIME format.

------=_NextPart_000_0382_01CC5B94.DFE3AFB0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit

I'm new to TICTOC. I've worked on the AVB standards and am working on other
high-performance media networking systems and standards that would benefit
from improvements in clock distribution. I know a lot about Ethernet and IP
but I'm not an MPLS expert. Here's my contribution on the topic of QoS:

 

RFC 4596 specifically recommends using EF for NTP messaging. EF is also
routinely used for VoIP payloads. Although it would seem to fit nicely here,
Ideally we'd want 1588 to take precedence over both of these. Unfortunately
and by design, there's no standard service level higher than EF. Network
administrators are free to define custom service levels above EF and if
there's any chance of a warm reception for such a recommendation, I think it
should be made.

 

As allowed by the other DiffServ RFCs and implementation by vendors, there's
no magic to the DSCP numbers. Best practice is for edge network devices to
ignore incoming DSCP values and re-mark traffic based on characteristics
such as protocol identifier, destination address and port number. 

 

The DCSP numbers used within a network are, in the end, enterprise specific.
In this context you can appreciate that a 1588 QoS recommendation can be
descriptive and loose and may not need to conform strictly to RFC 4596
recommendations.

 

1588 prioritization under AVB is a largely irrelevant benchmark as no PTP
packets are ever bridged so there are never any queuing delays for QoS to
address.

 

Kevin Gross

AVA Networks

 

From: tictoc-bounces@ietf.org [mailto:tictoc-bounces@ietf.org] On Behalf Of
Shahram Davari
Sent: Monday, August 08, 2011 11:37 AM
To: Ron Cohen; tictoc@ietf.org
Subject: Re: [TICTOC] DSCP for PTP

 

Ron,

 

I agree with you that all PTP messages must configured with highest priority
(a.k.a EF PHB) and EF should be the default. In fact I would also think it
is best to use L-LSP with EF PHB for 15880MPLS. If this is acceptable by the
group then we could add this to the 1588oMPLS draft.

 

 

Regards,

Shahram

 

From: tictoc-bounces@ietf.org [mailto:tictoc-bounces@ietf.org] On Behalf Of
Ron Cohen
Sent: Sunday, August 07, 2011 1:00 AM
To: tictoc@ietf.org
Subject: [TICTOC] DSCP for PTP

 

Hi,

Current standards do not recommend which DSCP values to set on PTP messages.
As a result vendors have chosen different default values, and some vendors
also differentiate between the DSCP set on PTP Event messages (Sync,
Delay_Req, etc.) and PTP General messages (Announce, Follow_Up, Delay_Resp).
I think TICTOC can help clarify the recommended DSCP usage, along the
guidelines of RFC4595, 'Configuration Guidelines for DiffServ Service
Classes'.

In my opinion classifying PTP event and general messages into separate PHBs
is problematic as discard of Follow_Up would render its associated Sync
message useless. Forwarding of Sync messages in a higher priority queue
compared to Follow_Up may lead to Sync message getting ahead of the previous
Follow_Up message which again causes the slave to discard the previous Sync
message. Hence the first order recommendation in my opinion should be to use
the same PHB (and DSCP marking) to all PTP messages. 

Choosing one of the existing PHBs as the recommended one for PTP is somewhat
harder. EF is a reasonable choice in my opinion, as per RFC4595 'The intent
of Expedited Forwarding PHB [RFC3246] is to provide a building block for
low-loss, low-delay, and low-jitter services.' TICTOC could in principle
recommend defining a new PHB tailored for PTP and similar services, but I
guess this would be a longer process.

I would appreciate if others will share their insight on the recommended
usage and whether this issue should or should not be addressed by TICTOC. 

Here is the relevant text from IEEE1588-2008 Annex D: "For PTP event
messages, the value of the differentiated service (DS) field in the Type of
Service (ToS)
field should be set to the highest traffic class selector codepoint
available." The PTP Telecom profile for frequency distribution, ITU-T
G.8265.1, doesn't specify or recommend DSCP settings.

Best,
Ron


------=_NextPart_000_0382_01CC5B94.DFE3AFB0
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-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" =
xmlns=3D"http://www.w3.org/TR/REC-html40"><head><meta =
http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii"><meta name=3DGenerator content=3D"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.MsoAcetate, li.MsoAcetate, div.MsoAcetate
	{mso-style-priority:99;
	mso-style-link:"Balloon Text Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:8.0pt;
	font-family:"Tahoma","sans-serif";}
span.BalloonTextChar
	{mso-style-name:"Balloon Text Char";
	mso-style-priority:99;
	mso-style-link:"Balloon Text";
	font-family:"Tahoma","sans-serif";}
span.EmailStyle19
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
span.EmailStyle20
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.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=3DEN-US link=3Dblue =
vlink=3Dpurple><div class=3DWordSection1><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>I&#8217;m new to TICTOC. I&#8217;ve worked on the AVB standards and =
am working on other high-performance media networking systems and =
standards that would benefit from improvements in clock distribution. I =
know a lot about Ethernet and IP but I&#8217;m not an MPLS expert. =
Here&#8217;s my contribution on the topic of =
QoS:<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>RFC 4596 specifically recommends using EF for NTP messaging. EF is =
also routinely used for VoIP payloads. Although it would seem to fit =
nicely here, Ideally we&#8217;d want 1588 to take precedence over both =
of these. Unfortunately and by design, there&#8217;s no standard service =
level higher than EF. Network administrators are free to define custom =
service levels above EF and if there&#8217;s any chance of a warm =
reception for such a recommendation, I think it should be =
made.<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>As allowed by the other DiffServ RFCs and implementation by vendors, =
there&#8217;s no magic to the DSCP numbers. Best practice is for edge =
network devices to ignore incoming DSCP values and re-mark traffic based =
on characteristics such as protocol identifier, destination address and =
port number. <o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>The DCSP numbers used within a network are, in the end, enterprise =
specific. In this context you can appreciate that a 1588 QoS =
recommendation can be descriptive and loose and may not need to conform =
strictly to RFC 4596 recommendations.<o:p></o:p></span></p><p =
class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>1588 prioritization under AVB is a largely irrelevant benchmark as no =
PTP packets are ever bridged so there are never any queuing delays for =
QoS to address.<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>Kevin Gross<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>AVA Networks<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><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=3DMsoNormal><b><span =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span>=
</b><span style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'> =
tictoc-bounces@ietf.org [mailto:tictoc-bounces@ietf.org] <b>On Behalf Of =
</b>Shahram Davari<br><b>Sent:</b> Monday, August 08, 2011 11:37 =
AM<br><b>To:</b> Ron Cohen; tictoc@ietf.org<br><b>Subject:</b> Re: =
[TICTOC] DSCP for PTP<o:p></o:p></span></p></div></div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>Ron,<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>I agree with you that all PTP messages must configured with highest =
priority (a.k.a EF PHB) and EF should be the default. In fact I would =
also think it is best to use L-LSP with EF PHB for 15880MPLS. If this is =
acceptable by the group then we could add this to the 1588oMPLS =
draft.<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>Regards,<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>Shahram<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><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=3DMsoNormal><b><span =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span>=
</b><span style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'> =
<a href=3D"mailto:tictoc-bounces@ietf.org">tictoc-bounces@ietf.org</a> =
<a =
href=3D"mailto:[mailto:tictoc-bounces@ietf.org]">[mailto:tictoc-bounces@i=
etf.org]</a> <b>On Behalf Of </b>Ron Cohen<br><b>Sent:</b> Sunday, =
August 07, 2011 1:00 AM<br><b>To:</b> <a =
href=3D"mailto:tictoc@ietf.org">tictoc@ietf.org</a><br><b>Subject:</b> =
[TICTOC] DSCP for PTP<o:p></o:p></span></p></div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><div><p =
class=3DMsoNormal>Hi,<br><br>Current standards do not recommend which =
DSCP values to set on PTP messages. As a result vendors have chosen =
different default values, and some vendors also differentiate between =
the DSCP set on PTP Event messages (Sync, Delay_Req, etc.) and PTP =
General messages (Announce, Follow_Up, Delay_Resp). I think TICTOC can =
help clarify the recommended DSCP usage, along the guidelines of =
RFC4595, 'Configuration Guidelines for DiffServ Service =
Classes'.<br><br>In my opinion classifying PTP event and general =
messages into separate PHBs is problematic as discard of Follow_Up would =
render its associated Sync message useless. Forwarding of Sync messages =
in a higher priority queue compared to Follow_Up may lead to Sync =
message getting ahead of the previous Follow_Up message which again =
causes the slave to discard the previous Sync message. Hence the first =
order recommendation in my opinion should be to use the same PHB (and =
DSCP marking) to all PTP messages. <br><br>Choosing one of the existing =
PHBs as the recommended one for PTP is somewhat harder. EF is a =
reasonable choice in my opinion, as per RFC4595 'The intent of Expedited =
Forwarding PHB [RFC3246] is to provide a building block for low-loss, =
low-delay, and low-jitter services.' TICTOC could in principle recommend =
defining a new PHB tailored for PTP and similar services, but I guess =
this would be a longer process.<br><br>I would appreciate if others will =
share their insight on the recommended usage and whether this issue =
should or should not be addressed by TICTOC. <br><br>Here is the =
relevant text from IEEE1588-2008 Annex D: &quot;For PTP event messages, =
the value of the differentiated service (DS) field in the Type of =
Service (ToS)<br>field should be set to the highest traffic class =
selector codepoint available.&quot; The PTP Telecom profile for =
frequency distribution, ITU-T G.8265.1, doesn't specify or recommend =
DSCP =
settings.<br><br>Best,<br>Ron<o:p></o:p></p></div></div></body></html>
------=_NextPart_000_0382_01CC5B94.DFE3AFB0--


From kodonog@gmail.com  Tue Aug 16 12:04:47 2011
Return-Path: <kodonog@gmail.com>
X-Original-To: tictoc@ietfa.amsl.com
Delivered-To: tictoc@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 582F911E80A4 for <tictoc@ietfa.amsl.com>; Tue, 16 Aug 2011 12:04:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.598
X-Spam-Level: 
X-Spam-Status: No, score=-103.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1, 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 yd18xf9YvqMC for <tictoc@ietfa.amsl.com>; Tue, 16 Aug 2011 12:04:45 -0700 (PDT)
Received: from mail-vx0-f172.google.com (mail-vx0-f172.google.com [209.85.220.172]) by ietfa.amsl.com (Postfix) with ESMTP id 3C7F911E8082 for <tictoc@ietf.org>; Tue, 16 Aug 2011 12:04:45 -0700 (PDT)
Received: by vxi29 with SMTP id 29so230730vxi.31 for <tictoc@ietf.org>; Tue, 16 Aug 2011 12:05:34 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=sender:message-id:date:from:reply-to:user-agent:mime-version:to :subject:references:in-reply-to:content-type; bh=Su0L5bXcduMJN5sFi8v/J4g6wvABHBxSob6ZdRY6BaE=; b=f0v0NWGdl8F6cYKGp/ikDP2xBy2I1l2l4rPisz8rihJ9d4pVtbfsczkFmCsekHgtRV QMDxXEym130+oyoY986+D5LzJTfuLlDCP0N2WfevkB/WcRye3ZEhCTSUsAwXDbt4z59V 4jpBL6wxSXR2IPpTjiqqmR1ABd/c1OkxPCEKQ=
Received: by 10.52.70.47 with SMTP id j15mr60646vdu.482.1313521534014; Tue, 16 Aug 2011 12:05:34 -0700 (PDT)
Received: from kodonog-mac.local (c-24-22-42-251.hsd1.or.comcast.net [24.22.42.251]) by mx.google.com with ESMTPS id p11sm223044vcu.3.2011.08.16.12.05.28 (version=SSLv3 cipher=OTHER); Tue, 16 Aug 2011 12:05:31 -0700 (PDT)
Sender: Karen ODonoghue <kodonog@gmail.com>
Message-ID: <4E4ABF79.7090702@pobox.com>
Date: Tue, 16 Aug 2011 15:05:29 -0400
From: Karen O'Donoghue <kodonog@pobox.com>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.2.18) Gecko/20110616 Thunderbird/3.1.11
MIME-Version: 1.0
To: tictoc@ietf.org
References: <4E492C75.9020507@isoc.org>
In-Reply-To: <4E492C75.9020507@isoc.org>
Content-Type: multipart/alternative; boundary="------------040302020808060807030702"
Subject: Re: [TICTOC] draft minutes of tictoc meeting at IETF 81
X-BeenThere: tictoc@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: kodonog@pobox.com
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, 16 Aug 2011 19:04:47 -0000

This is a multi-part message in MIME format.
--------------040302020808060807030702
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

Folks,

I've heard that my .txt file attachment was stripped off on some 
systems. Here are the minutes in line for your review...

Karen

DRAFT (15 Aug 2011)
Minutes for TICTOC meeting @ IETF-80
28 July 2011, 15:20 EDT (19:20 UTC)

The meeting started at 15:20 EDT.  Karen O'Donoghue and Yaakov Stein 
chaired the meeting
Dave Marlow took minutes.  Karen was jabber scribe.

Karen bashed the agenda and the blue sheets were distributed.  Karen 
provided the status
for the Working group since the last meeting: 3 working group drafts, 3 
individual
submissions, and no interim meetings.

Stefano Ruffino provided slides for an ITU-T SG15/Q13 update which 
Yaakov presented.
SG15/Q13 had an interim meeting in May 2011.  There were two primary 
topics of
interest to TICTOC: (1) Packet timing performance aspects for frequency 
(G.826x series);
and (2)Time Sync in packet networks (G.827x series).  The frequency work 
is maturing
while the time/phase work has its requirements document (G.8271) updated 
and other
documents are identified and being started.  SG15/Q13 is also working on 
a definition
and terminology document for both frequency and time of day (G.8260).


Yang Cui provided a Security Requirements discussion based on IPsec 
security for packet
based synchronization, 
draft-xu-tictoc-ipsec-security-for-synchronization-01.  As described
by its Abstract, this document analyses the need for security methods 
for synchronization
messages distributed over the Internet and gives a solution on how to 
mark the
synchronization message when IPSec is implemented in end to end 
frequency synchronization.
It was pointed out that the Introduction has requirements language (i.e. 
SHALLs) and
these will need to be taken out of this section.   There was 
considerable discussion on
the IEEE 1588 PTP use case across the Internet where Yaakov and Greg 
Dowd pointed out you
cannot have transparent clocks you must tunnel.  On a discussion of 
whether to encrypt
packets across 3GPP, someone from the jabber room pointed out that with 
3GPP you must
encrypt.  Yaakov asked whether the authors have talked with anyone in 
the closing IPsec
WG about this draft and Yang indicated that he has and they do not have 
any questions.
Karen asked whether the Working Group thought this work should be 
pursued, but got little
feedback.  Peter Lothberg said that in some use cases this could be 
useful but this
provides no value for the Internet use case.  Yang said that the 
femtocell is getting
greater use and there is no protection in the femtocell.  Greg Dowd said 
that femtocells
are meant to provide telephone calls and that they can be stopped by 
dropping all data.
He said we needed to clarify the threat models we are building the 
security for.

Karen discussed time synchronization protocol security requirements.  
The expired
TICTOC Requirements draft had recently been resubmitted
(draft-ietf-tictoc-requirements-01).  This draft identifies three 
security mechanisms to
consider.  Karen went over a survey that was done at the beginning of 
the TICTOC work
where four questions were identified that cover the different aspects 
for possible
security services.  Karen said that a volunteer editor has been 
identified to work on
general time synchronization security requirements.  The goal is to have 
a draft by the
next meeting.

Greg Dowd provided a PTPv2 MIB discussion based on 
draft-ietf-tictoc-ptp-mib-00.  This
MIB goes beyond the earlier drafts that only covered the PTPv2 telecom 
profile.  This
MIB covers all the PTPv2 devices.  The current draft is in its third 
version and
Greg felt it was now semantically correct.  Asked whether this MIB has 
been deployed,
Greg said that it has.  Measuring the performance of a PTPv2 node is 
outside the
present scope, but this could be added later.  Yaakov asked whether 
there was
commonality between this MIB and the NTPv4 MIB (RFC 5907), Greg said 
that this
MIB was PTPv2 specific with little commonality to the NTP MIB.  Dave 
Marlow said
that he had read the draft and found little commonality with the NTP MIB 
but was
very supportive of this draft which appears very thorough.  The Chairs 
said that
there needs to be MIB Doctor review (which they would pursue) and review by
TICTOC participants for this draft to progress.

Yaakov lead a discussion on Transporting PTP messages (IEEE 1588) over 
MPLS Networks,
draft-ietf-tictoc-1588overmpls-01.  He said that the draft very mature 
with three
individual drafts and now one TICTOC version.  There has been 
considerable discussion
on the list.  Yaakov asked what was needed before this goes to WGLC?  
Luca Martini
said that there are some text formatting issues and that some sections 
have given a
a wrong impression.  Of particular concern were the two modes (IP over 
MPLS and
Pseudowire), Pseudowire is not needed if timing is a service of the 
network and there
is only one clock over the network.  Pseudowire is needed if PTP is used 
directly over
Ethernet, and Yaakov pointed out that in many parts of the world there 
are many clocks
that a carrier transports separately.  There were some concerns from the 
MPLS
community, George Swallow pointed out an issue with fast reroute to 
address a fault.
There were concerns whether the draft was ready for last call or not, 
and what
procedure should be taken to get comments from the MPLS community.  
George suggested
to at least announce to the MPLS list about a WGLC in TICTOC.

Tal Mizrahi briefed UDP Checksum Trailer in Timing Protocols,
draft-mizrahi-tictoc-checksum-trailer-00.  This draft proposes a 
Checksum Trailer
extension to NTP, OWAMP and TWAMP that allows intermediate nodes to 
reflect the
checksum modification in the last 2 octets of the packet rather than in 
the UDP
checksum field.  This is to bring a capability already in IEEE 1588 into 
these other
protocols.  Yaakov asked why this is being brought into OWAMP and 
TWAMP.  Tal said
these are performance protocols that transfer time and could be 
benefited as well.
An issue related to the NTP extension field had been raised and 
discussed on the
mailing list.  This proposed technique requires an extension field without
authentication (i.e. without a MAC) to be practical; however, the NTPv4 
spec
(i.e. RFC 5905) REQUIRES all extension fields to include authentication.
Discussion on the list included opinions that the RFC was wrong and this 
is not
a requirement for NTPv4.  Additional effort is needed to determine if 
NTPv4 spec
should be changed or not.  Yaakov pointed out that both OWAMP and TWAMP 
have
authenticated modes.  This draft is intended for non authenticated 
packets only.
Yaakov said that in the case of OWAMP this is very limiting because its 
default is
to be authenticated.  In addition Yaakov said that OWAMP and TWAMP would 
require
an extension to their control protocols.  OWAMP and TWAMP are IPPM 
protocols, the
Chairs took an action to send this draft to the IPPM chairs.  Tal was asked
whether the mechanisms discussed in the draft had been implemented and he
said the mechanisms had not yet been implemented.

Dave Marlow discussed Network Time Mechanisms for Improving Computer 
Clock Accuracy,
draft-marlow-tictoc-computer-clock-accuracy-00.  This draft had not been 
updated
since the last meeting but Dave briefed the discussion that had been on 
the list.
Vladimir Smotlacha provided to the list, references to his papers 
describing NTP
servers which use OCXO oscillators to achieve much higher 
synchronization accuracy
than the experimental results described in this draft.  The use case in 
the draft
covers client accuracy and thus is outside the Vladimir's use case which 
addresses
server accuracy.  In June, Karen had forwarded a note from Dave Mills to 
the list
which mentioned that additional experimental results with NTP Interleave 
are in his
book.  Dave Mill's book provides experimental results for both an 
unloaded scenario
(which is a very similar to the experiment described in the draft) and a 
loaded
scenario.  Dave Mills, in his email, pointed out that Interleave showed 
greater
improvement in the loaded scenarios and with digest computations (e.g. 
Autokey).
Dave Marlow and Tim Plunkett are looking at the experimental results in 
the book and
comparing this to their results.  Tim Frost provided a paper on Minimum 
Time-Dispersion
Metrics  to the list. Dave indicated that this provides direction 
towards identifying
a common set of metrics for network time synchronization experiments.  A 
common set of
metrics or perhaps a benchmarking draft could be a candidate for future 
TICTOC work.
Greg Dowd said that there are products on the market that can provide a 
hardware time
stamp based on a programmable sequence off of a packet data network, 
this provides a
direction for the second mechanism outlined in the draft.  Yaakov 
mentioned that
his company tried NTP interleave on their highly optimized products and 
did not
see a significant difference in performance.   Dave said he and Tim 
Plunkett would
like to update their draft with the new information.  He solicited 
comments and
contributions on mechanisms to achieve greater client accuracy.

Karen led an additional NTP discussion.  The NTP control protocol which 
is an
appendix of RFC 1305 (NTPv3) is not in a current standard since RFC 1305 
was deprecated.
Volunteers are needed to get this important work documented and 
standardized.  Brian
Haberman (along with Karen, co-chair of the NTP working group) suggested 
in line with
Dave Hart to get rid of mode 7 and just document mode 6.  Harlan Stenn, 
via jabber
requested that mode 7 be documented as well.  Dave Hart, via jabber, 
said that mode 7
is fragile and vendor specific, so that there is no use in standardizing 
it.  Harlan
volunteered to document the NTP control protocol.  It was pointed out 
that RFC 5905 needs
to be redone since mode 6 is identified for future use; however, if this 
is an IANA
controlled field then just a change by IANA is needed.  Karen asked for 
volunteers to
document the NTP interleave extensions.  There has been email on list 
discussing Autokey
bugs/vulnerabilities being found by PTB (Germany's Standards 
Organization).  There were
no details discussed at this meeting but this is a concern that must be 
followed.  There
was a short discussion on what work would be carried out in the NTP WG 
and what should
be done in the TICTOC WG.  Brian said that all NTP control protocol work 
should be done
in the NTP WG but he had no opinion at this time as to where Interleave 
work should be
done.  All co-chairs agreed that email on any NTP topic should be sent 
to both lists.

The meeting adjourned at 17:20 EDT (21:20 UTC).





On 8/15/11 10:25 AM, Karen O'Donoghue wrote:
> Folks,
>
> Below are the draft minutes for the recent tictoc meeting. Thanks to 
> Dave Marlow for the timely production of the minutes. Please review 
> and submit any comments or changes as soon as possible.
>
> Regards,
> Karen
>
>
>
> _______________________________________________
> TICTOC mailing list
> TICTOC@ietf.org
> https://www.ietf.org/mailman/listinfo/tictoc


--------------040302020808060807030702
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
  <head>
    <meta content="text/html; charset=ISO-8859-1"
      http-equiv="Content-Type">
    <title></title>
  </head>
  <body bgcolor="#ffffff" text="#000000">
    Folks,<br>
    <br>
    I've heard that my .txt file attachment was stripped off on some
    systems. Here are the minutes in line for your review...<br>
    <br>
    Karen<br>
    <br>
    DRAFT (15 Aug 2011)<br>
    Minutes for TICTOC meeting @ IETF-80<br>
    28 July 2011, 15:20 EDT (19:20 UTC) <br>
    <br>
    The meeting started at 15:20 EDT.&nbsp; Karen O'Donoghue and Yaakov Stein
    chaired the meeting<br>
    Dave Marlow took minutes.&nbsp; Karen was jabber scribe.<br>
    <br>
    Karen bashed the agenda and the blue sheets were distributed.&nbsp; Karen
    provided the status <br>
    for the Working group since the last meeting: 3 working group
    drafts, 3 individual <br>
    submissions, and no interim meetings. <br>
    <br>
    Stefano Ruffino provided slides for an ITU-T SG15/Q13 update which
    Yaakov presented.&nbsp; <br>
    SG15/Q13 had an interim meeting in May 2011.&nbsp; There were two primary
    topics of <br>
    interest to TICTOC: (1) Packet timing performance aspects for
    frequency (G.826x series);<br>
    and (2)Time Sync in packet networks (G.827x series).&nbsp; The frequency
    work is maturing<br>
    while the time/phase work has its requirements document (G.8271)
    updated and other<br>
    documents are identified and being started.&nbsp; SG15/Q13 is also
    working on a definition <br>
    and terminology document for both frequency and time of day
    (G.8260).<br>
    <br>
    <br>
    Yang Cui provided a Security Requirements discussion based on IPsec
    security for packet <br>
    based synchronization,
    draft-xu-tictoc-ipsec-security-for-synchronization-01.&nbsp; As described<br>
    by its Abstract, this document analyses the need for security
    methods for synchronization <br>
    messages distributed over the Internet and gives a solution on how
    to mark the <br>
    synchronization message when IPSec is implemented in end to end
    frequency synchronization.<br>
    It was pointed out that the Introduction has requirements language
    (i.e. SHALLs) and <br>
    these will need to be taken out of this section.&nbsp;&nbsp; There was
    considerable discussion on<br>
    the IEEE 1588 PTP use case across the Internet where Yaakov and Greg
    Dowd pointed out you <br>
    cannot have transparent clocks you must tunnel.&nbsp; On a discussion of
    whether to encrypt <br>
    packets across 3GPP, someone from the jabber room pointed out that
    with 3GPP you must <br>
    encrypt.&nbsp; Yaakov asked whether the authors have talked with anyone
    in the closing IPsec <br>
    WG about this draft and Yang indicated that he has and they do not
    have any questions.&nbsp; <br>
    Karen asked whether the Working Group thought this work should be
    pursued, but got little <br>
    feedback.&nbsp; Peter Lothberg said that in some use cases this could be
    useful but this <br>
    provides no value for the Internet use case.&nbsp; Yang said that the
    femtocell is getting <br>
    greater use and there is no protection in the femtocell.&nbsp; Greg Dowd
    said that femtocells <br>
    are meant to provide telephone calls and that they can be stopped by
    dropping all data.&nbsp; <br>
    He said we needed to clarify the threat models we are building the
    security for.<br>
    <br>
    Karen discussed time synchronization protocol security
    requirements.&nbsp; The expired <br>
    TICTOC Requirements draft had recently been resubmitted <br>
    (draft-ietf-tictoc-requirements-01).&nbsp; This draft identifies three
    security mechanisms to<br>
    consider.&nbsp; Karen went over a survey that was done at the beginning
    of the TICTOC work <br>
    where four questions were identified that cover the different
    aspects for possible <br>
    security services.&nbsp; Karen said that a volunteer editor has been
    identified to work on <br>
    general time synchronization security requirements.&nbsp; The goal is to
    have a draft by the <br>
    next meeting.<br>
    <br>
    Greg Dowd provided a PTPv2 MIB discussion based on
    draft-ietf-tictoc-ptp-mib-00.&nbsp; This <br>
    MIB goes beyond the earlier drafts that only covered the PTPv2
    telecom profile.&nbsp; This <br>
    MIB covers all the PTPv2 devices.&nbsp; The current draft is in its third
    version and<br>
    Greg felt it was now semantically correct.&nbsp; Asked whether this MIB
    has been deployed, <br>
    Greg said that it has.&nbsp; Measuring the performance of a PTPv2 node is
    outside the <br>
    present scope, but this could be added later.&nbsp; Yaakov asked whether
    there was<br>
    commonality between this MIB and the NTPv4 MIB (RFC 5907), Greg said
    that this <br>
    MIB was PTPv2 specific with little commonality to the NTP MIB.&nbsp; Dave
    Marlow said <br>
    that he had read the draft and found little commonality with the NTP
    MIB but was <br>
    very supportive of this draft which appears very thorough.&nbsp; The
    Chairs said that <br>
    there needs to be MIB Doctor review (which they would pursue) and
    review by<br>
    TICTOC participants for this draft to progress.<br>
    <br>
    Yaakov lead a discussion on Transporting PTP messages (IEEE 1588)
    over MPLS Networks, <br>
    draft-ietf-tictoc-1588overmpls-01.&nbsp; He said that the draft very
    mature with three <br>
    individual drafts and now one TICTOC version.&nbsp; There has been
    considerable discussion<br>
    on the list.&nbsp; Yaakov asked what was needed before this goes to
    WGLC?&nbsp; Luca Martini <br>
    said that there are some text formatting issues and that some
    sections have given a<br>
    a wrong impression.&nbsp; Of particular concern were the two modes (IP
    over MPLS and <br>
    Pseudowire), Pseudowire is not needed if timing is a service of the
    network and there<br>
    is only one clock over the network.&nbsp; Pseudowire is needed if PTP is
    used directly over<br>
    Ethernet, and Yaakov pointed out that in many parts of the world
    there are many clocks <br>
    that a carrier transports separately.&nbsp; There were some concerns from
    the MPLS <br>
    community, George Swallow pointed out an issue with fast reroute to
    address a fault.&nbsp; <br>
    There were concerns whether the draft was ready for last call or
    not, and what <br>
    procedure should be taken to get comments from the MPLS community.&nbsp;
    George suggested <br>
    to at least announce to the MPLS list about a WGLC in TICTOC.<br>
    &nbsp;<br>
    Tal Mizrahi briefed UDP Checksum Trailer in Timing Protocols, <br>
    draft-mizrahi-tictoc-checksum-trailer-00.&nbsp; This draft proposes a
    Checksum Trailer <br>
    extension to NTP, OWAMP and TWAMP that allows intermediate nodes to
    reflect the <br>
    checksum modification in the last 2 octets of the packet rather than
    in the UDP <br>
    checksum field.&nbsp; This is to bring a capability already in IEEE 1588
    into these other <br>
    protocols.&nbsp; Yaakov asked why this is being brought into OWAMP and
    TWAMP.&nbsp; Tal said <br>
    these are performance protocols that transfer time and could be
    benefited as well.&nbsp; <br>
    An issue related to the NTP extension field had been raised and
    discussed on the <br>
    mailing list.&nbsp; This proposed technique requires an extension field
    without <br>
    authentication (i.e. without a MAC) to be practical; however, the
    NTPv4 spec <br>
    (i.e. RFC 5905) REQUIRES all extension fields to include
    authentication.&nbsp; <br>
    Discussion on the list included opinions that the RFC was wrong and
    this is not <br>
    a requirement for NTPv4.&nbsp; Additional effort is needed to determine
    if NTPv4 spec <br>
    should be changed or not.&nbsp; Yaakov pointed out that both OWAMP and
    TWAMP have <br>
    authenticated modes.&nbsp; This draft is intended for non authenticated
    packets only.&nbsp; <br>
    Yaakov said that in the case of OWAMP this is very limiting because
    its default is <br>
    to be authenticated.&nbsp; In addition Yaakov said that OWAMP and TWAMP
    would require <br>
    an extension to their control protocols.&nbsp; OWAMP and TWAMP are IPPM
    protocols, the <br>
    Chairs took an action to send this draft to the IPPM chairs.&nbsp; Tal
    was asked <br>
    whether the mechanisms discussed in the draft had been implemented
    and he <br>
    said the mechanisms had not yet been implemented.&nbsp; <br>
    <br>
    Dave Marlow discussed Network Time Mechanisms for Improving Computer
    Clock Accuracy, <br>
    draft-marlow-tictoc-computer-clock-accuracy-00.&nbsp; This draft had not
    been updated <br>
    since the last meeting but Dave briefed the discussion that had been
    on the list.&nbsp; <br>
    Vladimir Smotlacha provided to the list, references to his papers
    describing NTP <br>
    servers which use OCXO oscillators to achieve much higher
    synchronization accuracy <br>
    than the experimental results described in this draft.&nbsp; The use case
    in the draft <br>
    covers client accuracy and thus is outside the Vladimir's use case
    which addresses <br>
    server accuracy.&nbsp; In June, Karen had forwarded a note from Dave
    Mills to the list <br>
    which mentioned that additional experimental results with NTP
    Interleave are in his <br>
    book.&nbsp; Dave Mill's book provides experimental results for both an
    unloaded scenario <br>
    (which is a very similar to the experiment described in the draft)
    and a loaded<br>
    scenario.&nbsp; Dave Mills, in his email, pointed out that Interleave
    showed greater <br>
    improvement in the loaded scenarios and with digest computations
    (e.g. Autokey).&nbsp; <br>
    Dave Marlow and Tim Plunkett are looking at the experimental results
    in the book and<br>
    comparing this to their results.&nbsp; Tim Frost provided a paper on
    Minimum Time-Dispersion<br>
    Metrics&nbsp; to the list. Dave indicated that this provides direction
    towards identifying <br>
    a common set of metrics for network time synchronization
    experiments.&nbsp; A common set of<br>
    metrics or perhaps a benchmarking draft could be a candidate for
    future TICTOC work. <br>
    Greg Dowd said that there are products on the market that can
    provide a hardware time <br>
    stamp based on a programmable sequence off of a packet data network,
    this provides a<br>
    direction for the second mechanism outlined in the draft.&nbsp; Yaakov
    mentioned that<br>
    his company tried NTP interleave on their highly optimized products
    and did not<br>
    see a significant difference in performance.&nbsp;&nbsp; Dave said he and Tim
    Plunkett would <br>
    like to update their draft with the new information.&nbsp; He solicited
    comments and <br>
    contributions on mechanisms to achieve greater client accuracy.&nbsp; <br>
    <br>
    Karen led an additional NTP discussion.&nbsp; The NTP control protocol
    which is an<br>
    appendix of RFC 1305 (NTPv3) is not in a current standard since RFC
    1305 was deprecated.<br>
    Volunteers are needed to get this important work documented and
    standardized.&nbsp; Brian <br>
    Haberman (along with Karen, co-chair of the NTP working group)
    suggested in line with <br>
    Dave Hart to get rid of mode 7 and just document mode 6.&nbsp; Harlan
    Stenn, via jabber<br>
    requested that mode 7 be documented as well.&nbsp; Dave Hart, via jabber,
    said that mode 7 <br>
    is fragile and vendor specific, so that there is no use in
    standardizing it.&nbsp; Harlan<br>
    volunteered to document the NTP control protocol.&nbsp; It was pointed
    out that RFC 5905 needs <br>
    to be redone since mode 6 is identified for future use; however, if
    this is an IANA <br>
    controlled field then just a change by IANA is needed.&nbsp; Karen asked
    for volunteers to<br>
    document the NTP interleave extensions.&nbsp; There has been email on
    list discussing Autokey<br>
    bugs/vulnerabilities being found by PTB (Germany's Standards
    Organization).&nbsp; There were<br>
    no details discussed at this meeting but this is a concern that must
    be followed.&nbsp; There<br>
    was a short discussion on what work would be carried out in the NTP
    WG and what should <br>
    be done in the TICTOC WG.&nbsp; Brian said that all NTP control protocol
    work should be done <br>
    in the NTP WG but he had no opinion at this time as to where
    Interleave work should be <br>
    done.&nbsp; All co-chairs agreed that email on any NTP topic should be
    sent to both lists.<br>
    <br>
    The meeting adjourned at 17:20 EDT (21:20 UTC). <br>
    <br>
    <br>
    <br>
    <br>
    <br>
    On 8/15/11 10:25 AM, Karen O'Donoghue wrote:
    <blockquote cite="mid:4E492C75.9020507@isoc.org" type="cite">Folks,
      <br>
      <br>
      Below are the draft minutes for the recent tictoc meeting. Thanks
      to Dave Marlow for the timely production of the minutes. Please
      review and submit any comments or changes as soon as possible.
      <br>
      <br>
      Regards,
      <br>
      Karen
      <br>
      <br>
      <br>
      <pre wrap="">
<fieldset class="mimeAttachmentHeader"></fieldset>
_______________________________________________
TICTOC mailing list
<a class="moz-txt-link-abbreviated" href="mailto:TICTOC@ietf.org">TICTOC@ietf.org</a>
<a class="moz-txt-link-freetext" href="https://www.ietf.org/mailman/listinfo/tictoc">https://www.ietf.org/mailman/listinfo/tictoc</a>
</pre>
    </blockquote>
    <br>
  </body>
</html>

--------------040302020808060807030702--

From kevin.gross@avanw.com  Tue Aug 16 16:49:48 2011
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 4923811E8104 for <tictoc@ietfa.amsl.com>; Tue, 16 Aug 2011 16:49:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.494
X-Spam-Level: 
X-Spam-Status: No, score=-0.494 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_COM=0.553,  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 JgP7cja6Ft5Y for <tictoc@ietfa.amsl.com>; Tue, 16 Aug 2011 16:49:44 -0700 (PDT)
Received: from oproxy9.bluehost.com (oproxy9.bluehost.com [IPv6:2605:dc00:100:2::a2]) by ietfa.amsl.com (Postfix) with SMTP id 8FD1211E80FC for <tictoc@ietf.org>; Tue, 16 Aug 2011 16:49:44 -0700 (PDT)
Received: (qmail 26716 invoked by uid 0); 15 Aug 2011 22:50:33 -0000
Received: from unknown (HELO host291.hostmonster.com) (74.220.215.91) by oproxy9.bluehost.com with SMTP; 15 Aug 2011 22:50:33 -0000
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=avanw.com; s=default;  h=Content-Type:MIME-Version:Message-ID:Date:Subject:In-Reply-To:References:To:From; bh=Yy4PTnL2X5NqkNG+63d4/bocIHsdQ8pOrSVfjM8v8Hk=;  b=Mygovpt1LvIz9m9UXGtVbo80Hgdb2rp15yO/ppiiqOTremIL3JReKSV2w5cvd8uNrsh2U5GVe9Kb3cNQkB+v7+GKXhAHgxKnzTDQrqwTROr5VeLAhka7gsnQ6zughvi4;
Received: from c-98-245-120-114.hsd1.co.comcast.net ([98.245.120.114] helo=AVADesk2) by host291.hostmonster.com with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.76) (envelope-from <kevin.gross@avanw.com>) id 1Qt5zM-0004Sw-M4 for tictoc@ietf.org; Mon, 15 Aug 2011 16:50:32 -0600
From: "Kevin Gross" <kevin.gross@avanw.com>
To: <tictoc@ietf.org>
References: <CALMYT9Qt7HAWA6mAe7m+58=_jQ68a0bhnNq97KFU22_4yf4xKA@mail.gmail.com> <2C2F1EBA8050E74EA81502D5740B4BD6A9327F9E2C@SJEXCHCCR02.corp.ad.broadcom.com>
In-Reply-To: <2C2F1EBA8050E74EA81502D5740B4BD6A9327F9E2C@SJEXCHCCR02.corp.ad.broadcom.com>
Date: Mon, 15 Aug 2011 16:50:33 -0600
Organization: AVA Networks
Message-ID: <032e01cc5b9d$be4d45b0$3ae7d110$@avanw.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_032F_01CC5B6B.73B48360"
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQIoVun+ZbdmKC1YaryAp7Gc/q4xuwFB78EhlFx3fmA=
Content-Language: en-us
X-Identified-User: {1416:host291.hostmonster.com:avanwcom:avanw.com} {sentby:smtp auth 98.245.120.114 authed with kevin.gross@avanw.com}
Subject: Re: [TICTOC] DSCP for PTP
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, 16 Aug 2011 23:49:48 -0000

This is a multipart message in MIME format.

------=_NextPart_000_032F_01CC5B6B.73B48360
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit

I'm new to TICTOC. I've worked on the AVB standards and am working on other
high-performance media networking systems and standards that would benefit
from improvements in clock distribution. I know a lot about Ethernet and IP
but I'm not an MPLS expert. Here's my contribution on the topic of QoS:

 

RFC 4596 specifically recommends using EF for NTP messaging. EF is also
routinely used for VoIP payloads. Ideally we'd want 1588 to take precedence
over both of these but there's no standard service level higher than EF.
Network administrators are free to define custom service levels above EF and
if there's any chance of a warm reception for such a recommendation, I think
it should be made.

 

As allowed by the other DiffServ RFCs and implementation by many vendors,
there's no magic to the DSCP numbers. Best practice is for edge network
devices to ignore incoming DSCP values and re-mark traffic based on
characteristics such as protocol identifier, destination address and port
number. 

 

The DCSP numbers used internally are then enterprise specific. In this
context you can appreciate that a 1588 QoS recommendation can be descriptive
and may not need to conform strictly to RFC 4596 recommendations.

 

1588 prioritization under AVB is largely irrelevant as no PTP packets are
ever bridged so there are never any queuing delays for QoS to address.

 

Kevin Gross

AVA Networks

 

From: tictoc-bounces@ietf.org [mailto:tictoc-bounces@ietf.org] On Behalf Of
Shahram Davari
Sent: Monday, August 08, 2011 11:37 AM
To: Ron Cohen; tictoc@ietf.org
Subject: Re: [TICTOC] DSCP for PTP

 

Ron,

 

I agree with you that all PTP messages must configured with highest priority
(a.k.a EF PHB) and EF should be the default. In fact I would also think it
is best to use L-LSP with EF PHB for 15880MPLS. If this is acceptable by the
group then we could add this to the 1588oMPLS draft.

 

 

Regards,

Shahram

 

From: tictoc-bounces@ietf.org [mailto:tictoc-bounces@ietf.org] On Behalf Of
Ron Cohen
Sent: Sunday, August 07, 2011 1:00 AM
To: tictoc@ietf.org
Subject: [TICTOC] DSCP for PTP

 

Hi,

Current standards do not recommend which DSCP values to set on PTP messages.
As a result vendors have chosen different default values, and some vendors
also differentiate between the DSCP set on PTP Event messages (Sync,
Delay_Req, etc.) and PTP General messages (Announce, Follow_Up, Delay_Resp).
I think TICTOC can help clarify the recommended DSCP usage, along the
guidelines of RFC4595, 'Configuration Guidelines for DiffServ Service
Classes'.

In my opinion classifying PTP event and general messages into separate PHBs
is problematic as discard of Follow_Up would render its associated Sync
message useless. Forwarding of Sync messages in a higher priority queue
compared to Follow_Up may lead to Sync message getting ahead of the previous
Follow_Up message which again causes the slave to discard the previous Sync
message. Hence the first order recommendation in my opinion should be to use
the same PHB (and DSCP marking) to all PTP messages. 

Choosing one of the existing PHBs as the recommended one for PTP is somewhat
harder. EF is a reasonable choice in my opinion, as per RFC4595 'The intent
of Expedited Forwarding PHB [RFC3246] is to provide a building block for
low-loss, low-delay, and low-jitter services.' TICTOC could in principle
recommend defining a new PHB tailored for PTP and similar services, but I
guess this would be a longer process.

I would appreciate if others will share their insight on the recommended
usage and whether this issue should or should not be addressed by TICTOC. 

Here is the relevant text from IEEE1588-2008 Annex D: "For PTP event
messages, the value of the differentiated service (DS) field in the Type of
Service (ToS)
field should be set to the highest traffic class selector codepoint
available." The PTP Telecom profile for frequency distribution, ITU-T
G.8265.1, doesn't specify or recommend DSCP settings.

Best,
Ron


------=_NextPart_000_032F_01CC5B6B.73B48360
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-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" =
xmlns=3D"http://www.w3.org/TR/REC-html40"><head><meta =
http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii"><meta name=3DGenerator content=3D"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.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;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
span.BalloonTextChar
	{mso-style-name:"Balloon Text Char";
	mso-style-priority:99;
	mso-style-link:"Balloon Text";
	font-family:"Tahoma","sans-serif";}
span.EmailStyle20
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.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=3DEN-US link=3Dblue =
vlink=3Dpurple><div class=3DWordSection1><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>I&#8217;m new to TICTOC. I&#8217;ve worked on the AVB standards and =
am working on other high-performance media networking systems and =
standards that would benefit from improvements in clock distribution. I =
know a lot about Ethernet and IP but I&#8217;m not an MPLS expert. =
Here&#8217;s my contribution on the topic of =
QoS:<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>RFC 4596 specifically recommends using EF for NTP messaging. EF is =
also routinely used for VoIP payloads. Ideally we&#8217;d want 1588 to =
take precedence over both of these but there&#8217;s no standard service =
level higher than EF. Network administrators are free to define custom =
service levels above EF and if there&#8217;s any chance of a warm =
reception for such a recommendation, I think it should be =
made.<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>As allowed by the other DiffServ RFCs and implementation by many =
vendors, there&#8217;s no magic to the DSCP numbers. Best practice is =
for edge network devices to ignore incoming DSCP values and re-mark =
traffic based on characteristics such as protocol identifier, =
destination address and port number. <o:p></o:p></span></p><p =
class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>The DCSP numbers used internally are then enterprise specific. In =
this context you can appreciate that a 1588 QoS recommendation can be =
descriptive and may not need to conform strictly to RFC 4596 =
recommendations.<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>1588 prioritization under AVB is largely irrelevant as no PTP packets =
are ever bridged so there are never any queuing delays for QoS to =
address.<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>Kevin Gross<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>AVA Networks<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><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=3DMsoNormal><b><span =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span>=
</b><span style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'> =
tictoc-bounces@ietf.org [mailto:tictoc-bounces@ietf.org] <b>On Behalf Of =
</b>Shahram Davari<br><b>Sent:</b> Monday, August 08, 2011 11:37 =
AM<br><b>To:</b> Ron Cohen; tictoc@ietf.org<br><b>Subject:</b> Re: =
[TICTOC] DSCP for PTP<o:p></o:p></span></p></div></div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>Ron,<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>I agree with you that all PTP messages must configured with highest =
priority (a.k.a EF PHB) and EF should be the default. In fact I would =
also think it is best to use L-LSP with EF PHB for 15880MPLS. If this is =
acceptable by the group then we could add this to the 1588oMPLS =
draft.<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>Regards,<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>Shahram<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><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=3DMsoNormal><b><span =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span>=
</b><span style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'> =
<a href=3D"mailto:tictoc-bounces@ietf.org">tictoc-bounces@ietf.org</a> =
<a =
href=3D"mailto:[mailto:tictoc-bounces@ietf.org]">[mailto:tictoc-bounces@i=
etf.org]</a> <b>On Behalf Of </b>Ron Cohen<br><b>Sent:</b> Sunday, =
August 07, 2011 1:00 AM<br><b>To:</b> <a =
href=3D"mailto:tictoc@ietf.org">tictoc@ietf.org</a><br><b>Subject:</b> =
[TICTOC] DSCP for PTP<o:p></o:p></span></p></div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><div><p =
class=3DMsoNormal>Hi,<br><br>Current standards do not recommend which =
DSCP values to set on PTP messages. As a result vendors have chosen =
different default values, and some vendors also differentiate between =
the DSCP set on PTP Event messages (Sync, Delay_Req, etc.) and PTP =
General messages (Announce, Follow_Up, Delay_Resp). I think TICTOC can =
help clarify the recommended DSCP usage, along the guidelines of =
RFC4595, 'Configuration Guidelines for DiffServ Service =
Classes'.<br><br>In my opinion classifying PTP event and general =
messages into separate PHBs is problematic as discard of Follow_Up would =
render its associated Sync message useless. Forwarding of Sync messages =
in a higher priority queue compared to Follow_Up may lead to Sync =
message getting ahead of the previous Follow_Up message which again =
causes the slave to discard the previous Sync message. Hence the first =
order recommendation in my opinion should be to use the same PHB (and =
DSCP marking) to all PTP messages. <br><br>Choosing one of the existing =
PHBs as the recommended one for PTP is somewhat harder. EF is a =
reasonable choice in my opinion, as per RFC4595 'The intent of Expedited =
Forwarding PHB [RFC3246] is to provide a building block for low-loss, =
low-delay, and low-jitter services.' TICTOC could in principle recommend =
defining a new PHB tailored for PTP and similar services, but I guess =
this would be a longer process.<br><br>I would appreciate if others will =
share their insight on the recommended usage and whether this issue =
should or should not be addressed by TICTOC. <br><br>Here is the =
relevant text from IEEE1588-2008 Annex D: &quot;For PTP event messages, =
the value of the differentiated service (DS) field in the Type of =
Service (ToS)<br>field should be set to the highest traffic class =
selector codepoint available.&quot; The PTP Telecom profile for =
frequency distribution, ITU-T G.8265.1, doesn't specify or recommend =
DSCP =
settings.<br><br>Best,<br>Ron<o:p></o:p></p></div></div></body></html>
------=_NextPart_000_032F_01CC5B6B.73B48360--


From david.marlow@navy.mil  Wed Aug 24 13:51:28 2011
Return-Path: <david.marlow@navy.mil>
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 216BF21F8D0C for <tictoc@ietfa.amsl.com>; Wed, 24 Aug 2011 13:51:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.065
X-Spam-Level: 
X-Spam-Status: No, score=-2.065 tagged_above=-999 required=5 tests=[AWL=0.534,  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 QfRKu8SSgjKV for <tictoc@ietfa.amsl.com>; Wed, 24 Aug 2011 13:51:25 -0700 (PDT)
Received: from naeanrfkax01o.nmci.navy.mil (naeanrfkax01o.nmci.navy.mil [138.162.5.136]) by ietfa.amsl.com (Postfix) with ESMTP id 8AF2121F8C20 for <tictoc@ietf.org>; Wed, 24 Aug 2011 13:51:24 -0700 (PDT)
X-AuditID: 8aa20587-b7bbaae0000030ac-dd-4e55648e9a73
Received: from naeanrfkeg03v.nadsusea.nads.navy.mil (gate4-norfolk.nmci.navy.mil [138.162.0.44]) by  (Symantec Mail Security) with SMTP id EB.47.12460.E84655E4; Wed, 24 Aug 2011 20:52:30 +0000 (GMT)
Received: from naeanrfkeb10v.nadsusea.nads.navy.mil ([10.16.20.113]) by naeanrfkeg03v.nadsusea.nads.navy.mil with Microsoft SMTPSVC(6.0.3790.4675); Wed, 24 Aug 2011 16:52:29 -0400
Received: from naeanrfkeb06v.nadsusea.nads.navy.mil ([10.16.20.109]) by naeanrfkeb10v.nadsusea.nads.navy.mil with Microsoft SMTPSVC(6.0.3790.4675); Wed, 24 Aug 2011 16:52:28 -0400
Received: from naeamillez04v.nadsusea.nads.navy.mil ([10.16.20.64]) by naeanrfkeb06v.nadsusea.nads.navy.mil with Microsoft SMTPSVC(6.0.3790.4675); Wed, 24 Aug 2011 16:52:29 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Wed, 24 Aug 2011 16:52:33 -0400
Content-Type: multipart/signed; protocol="application/x-pkcs7-signature"; micalg=SHA1; boundary="----=_NextPart_000_0FE7_01CC627E.315CFA00"
Message-ID: <A3E5B6E9262F674FA0C82876819BBD0460D7EA@naeamillez04v.nadsusea.nads.navy.mil>
In-reply-to: <4DF03979.5070204@pobox.com>
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator: 
Thread-Topic: Renamed: Interleave Questions  
Thread-Index: AcwmUsY9UPxXTbGcT5iOrRftdLttwg7e4w4w
References: <4DF03979.5070204@pobox.com>
From: "Marlow, David T CIV NSWCDD, W64" <david.marlow@navy.mil>
To: <mills@udel.edu>
X-OriginalArrivalTime: 24 Aug 2011 20:52:29.0102 (UTC) FILETIME=[BCA2F4E0:01CC629F]
X-Brightmail-Tracker: AAAAAA==
Cc: ntpwg@lists.ntp.org, tictoc@ietf.org
Subject: [TICTOC] Renamed: Interleave Questions
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, 24 Aug 2011 20:51:28 -0000

This is a multi-part message in MIME format.

------=_NextPart_000_0FE7_01CC627E.315CFA00
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit

Dave,
   A while back in an email thread you pointed out that our ID (draft-marlow-tictoc-computer-clock-accuracy-00.txt) only addressed interleaved broadcast and did not include interleaved symmetric mode and that a lot of the detail information is in your book.  We bought the book and have learned a lot particularly in section 16.6 where you have measurement data for interleave mode operation.  Your Backroom LAN example is similar to the experiments we ran.  We had some questions:

1) In your Backroom LAN example the GPS clock server ran in client/server mode with clients Macabre and Mort.  Would you expect better accuracy if client/server mode is used (as you did) versus if interleave broadcast mode were used between this server and these two clients?  

2)Similar in your Campus LAN example you used client/server mode in some of the operations versus using interleave broadcast, where is client/server mode better than interleave broadcast to use?

3) In your Backroom LAN example, Macabre and Mort ran interleaved symmetric mode between each other.  Would not the dominant synchronization factor come from the GPS clock server, given its lower stratum number?  Is the interleaved symmetric mode exchanges providing a secondary effect to keep these two together?

  Dave 


-----Original Message-----
From: tictoc-bounces@ietf.org [mailto:tictoc-bounces@ietf.org] On Behalf Of Karen O'Donoghue
Sent: Wednesday, June 08, 2011 23:10
To: NTP Working Group; tictoc@ietf.org
Subject: [TICTOC] Fwd: Re: [ntpwg] Fwd: reminder for remote participation in today's tictoc meeting

Folks,

This came to me personally, and I neglected to send it on to the ntp and tictoc wg lists. My apologies for the delay. The question before us is whether or not the interleave capability should be properly documented and where the resources will come from to complete the effort. 

Karen

-------- Original Message -------- 
Subject: 	Re: [ntpwg] Fwd: [TICTOC] reminder for remote participation in today's tictoc meeting	 
Date: 	Tue, 12 Apr 2011 18:18:43 +0000	 
From: 	David L. Mills <mills@udel.edu> <mailto:mills@udel.edu> 	 
To: 	kodonog@pobox.com	 


Karen,

The following is in response to the ID you distributed. I offer it as a candidate for distribution to th eWG members.

Dave

This internet draft describes experiments using the interleaved broadcast mode recently incorporated in the NTP reference implementation. The experiments do not include the interleaved symmetric mode, which provides similar functionality in peer-to-peer configurations. For reference, these modes, their relevance to PTP and related information are discussed in detail in Chapters 15 through 17 of the book "Network Time Synchronization - the Network Time Protocol on Earth and in Space, Second Edition, CRC Press 2011, as cited on my web page www.eedis.udel.edu/~mills <http://www.eedis.udel.edu/%7Emills> . However, most of the information relevant to the followings discussion can be found in the white papers at www.eecis.udel.edu/~mills/ntp.html <http://www.eecis.udel.edu/%7Emills/ntp.html> . Of particular interest are the documents "Analysis and Simulation of the NTP On-Wire Protocol" and "Security Analysis of the NTP Protocol." Both of these documents represent an update since t
 he book was published late last year.

Readers may wonder why these documents have not been published as an update to the protocol specification RFC-5905, which would have been the expectation several years ago in the adolescent Internet. However, the effort necessary to publish an ID with figures, tables and equations is nowadays simply unacceptable. My experience with RFC-5905 and RFC-5906 over the last five years of publishing effort is not sustainable. Thus, unless some collaboration, perhaps the TICTOC working group, chose to publish them as IDs, I will not commit that adventure myself.

First some nomenclature that may help in the following discussion. Timestamps captured for the clock discipline are classed as hardstamps, drivestamps and softstamps. Softstamps are captured during the course of user-space processing; they may be corrupted by operating system and device latencies, as well as transmission delays. Drivestamps are captured during the packet interrupt routines, so are much less affected by operating system scheduling and competition with other programs. Hardstamps are captured by dedicated hardware means, typically in the PHY layer of the network interface card (NIC). While the details vary, the typical intercept point is the media independent interface (MII), which monitors the frame level interface on a character by character basis. The capture means is usuallt a field-programmable gate array (FPGA) that parses the packeet, inserts timestamp data and recomputes the UDP checksum.

The interleaved capability was originally not intended for NTP, but for the Proximity-1 protocol specified by the Consultive Committee on Space Data systems (CCSDS). The Proximity-1 protocol is designed for communication between spacecraft in the vicinity of Mars and for future missions in the vicinity of the Moon. Space data links are often operated at very low data rates compared to typical Ethernet links. Typical rates range from 1 kb/s to 256 kb/s with very different data rates in each direction. Due to various queuing and transmission operations, the output delay can reach 30 s, so it is imparities that timestamps be captured close to the PHY layer. In the Proximity-1 desing, hardstamps are captured upon the passage of the ASM code combination at the beginning of each transmitted frame..

Queuing and transmission delays are not the only contributors to space data link delay. Reed-Solomon and convolutional encoding delays can be a large contribution to the link delay; however, these delays are a constant contribution to the lightwave transmission delay. These contributions - up to many seconds - can dwarf the lightwave transmission delays.

In the NTP interleaved design, drivestamps are captured in the device interrupt routine - on input immediately after the frame has been received and before copying to an input buffer; on output shortly after the frame has been transmitted and before the buffer is released for the following input or output frame. This can become rather awkward in the case of NICs of the PCNET architecture, as data are copied directly from user space to device buffers directed by DMA descriptors. Drivestamps have been used on input for many years, but for output this is possible only using the interleaved modes. The result avoids the latencies due to the message digest computation, Autokey protocol data units, output queuing and frame transmissions, typically some 10-40 microseconds.

It should be obvious from the documents that a primary motivation for the NTP interleaved design was protection from network errors and intruder attack. The detailed analysis and simulation are designed to demonstrate resistance to common corruptions such as dropped or duplicate packets and possible bogus attacks. The NTP design includes a four-level security model, the lower two levels might be considered for a PTP application. This is one of the most important difference between the PTP and NTP protocol designs; however, the NTP design might be considered overkill in a sheltered, isolated Ethernet network.

Careful observers may notice an interesting anomaly with the interleaved broadcast mode. The preliminary volley intended to measure the roundtrip time uses basic mode, not interleaved mode. The reason for this requires some explanation. In times of old, the dominant concern was the 6-bone, an international consortium of multicast application developers. In that context with historic multicast configurations, including DVMRP and PIM, the multicast spanning tree was far different than the unicast spanning tree. Therefore, the preliminary volley was important to estimate the offset of the multicast server to the multicast client and thus the apparent one-way delay. In principle, with adroit protocolmanship, it would be possible to change the protocol to measure the interleaved roundtrip delay, which would be more appropriate for modern high-speed Ethernet networks.

Karen O'Donoghue wrote:




	-------- Original Message -------- 
Subject: 	[TICTOC] reminder for remote participation in today's tictoc meeting	 
Date: 	Thu, 31 Mar 2011 09:56:35 +0200	 
From: 	Karen O'Donoghue <odonoghue@isoc.org> <mailto:odonoghue@isoc.org> 	 
Reply-To: 	odonoghue@isoc.org	 
Organization: 	ISOC	 
To: 	tictoc@ietf.org, NTP Working Group <ntpwg@lists.ntp.org> <mailto:ntpwg@lists.ntp.org> 	 


	Folks,
	
	This is a reminder that the tictoc working group will meet today from 
	17:40 - 19:40 CEST (15:40 - 17:40 UTC). The tools agenda for the IETF 
	meeting (http://tools.ietf.org/agenda/80/) has links for the drafts, 
	presentations, jabber chat room, and audio streaming to facilitate 
	remote participation.
	
	Regards,
	Karen
	
	_______________________________________________
	TICTOC mailing list
	TICTOC@ietf.org
	https://www.ietf.org/mailman/listinfo/tictoc
	  
	
________________________________


	_______________________________________________
	ntpwg mailing list
	ntpwg@lists.ntp.org
	http://lists.ntp.org/listinfo/ntpwg



------=_NextPart_000_0FE7_01CC627E.315CFA00
Content-Type: application/x-pkcs7-signature;
	name="smime.p7s"
Content-Transfer-Encoding: base64
Content-Disposition: attachment;
	filename="smime.p7s"

MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIISuDCCA3Aw
ggJYoAMCAQICAQUwDQYJKoZIhvcNAQEFBQAwWzELMAkGA1UEBhMCVVMxGDAWBgNVBAoTD1UuUy4g
R292ZXJubWVudDEMMAoGA1UECxMDRG9EMQwwCgYDVQQLEwNQS0kxFjAUBgNVBAMTDURvRCBSb290
IENBIDIwHhcNMDQxMjEzMTUwMDEwWhcNMjkxMjA1MTUwMDEwWjBbMQswCQYDVQQGEwJVUzEYMBYG
A1UEChMPVS5TLiBHb3Zlcm5tZW50MQwwCgYDVQQLEwNEb0QxDDAKBgNVBAsTA1BLSTEWMBQGA1UE
AxMNRG9EIFJvb3QgQ0EgMjCCASIwDQYJKoZIhvcNAQEBBQADggEPADCCAQoCggEBAMAswfaNO6z/
PzzWcb64dCIH7HBBFfyrQOMHqsHD2J/+2kw6vz/I2Ch7SzYBwKxFJcPSDgqPhRhkED0aE3Aqb47X
3I2Ts0EPOCHNravCPSoF01cRNw3NjFH5k+PMRkkhjhS0zcsUPjjNcjHuqxLyZeo0LlZd/+5jdctt
upE0/J7z9C0cvlDEQt9ZiP9qs/qobD3LVnFxBZa7n4DlgEVZZ0Gw68OtYKSAdQYXnA70Q+CZDhv7
f/WzzLKBgrH9MsG4vkGkZLVgOlpRMIzO3kEsGUdcSRBkuXSph0GvfW66wbihv2UxOgRn+bW7jpKK
AGO4seaMOF+D/1DVO6Jda7IQzGMCAwEAAaM/MD0wHQYDVR0OBBYEFEl0uwxeunr+AlTve6DGlcYJ
gHCWMAsGA1UdDwQEAwIBhjAPBgNVHRMBAf8EBTADAQH/MA0GCSqGSIb3DQEBBQUAA4IBAQCYkY0/
ici79cBpcyk7Nay6swh2PXAJkumERCEBfRR2G+5RbB2NFTctezFp9JpEuK9GzDT6I8sDJxnSgyF1
K+fgG5km3IRAleio0sz2WFxm7z9KlxCCHboKot1bBiudp2RO6y4BNaS0PxOtVeTVc6hpmxHxmPIx
Hm9A1Ph4n46RoG9wBJBmqgYrzuF6krV94eDRluehOi3MsZ0fBUTth5nTTRpwOcEEDOV+2fGv1yAO
8SJ6JaRzmcw/pAcnlqiile2CuRbTnguHwsHyiPVi32jfx7xpUe2xXNxUVCkPCTmarAPB2wxNrm8K
ehZJ8b+R0jiU0/aVLLdsyUK2jcqQjYXZMIIErzCCA5egAwIBAgIDKnOPMA0GCSqGSIb3DQEBBQUA
MF0xCzAJBgNVBAYTAlVTMRgwFgYDVQQKEw9VLlMuIEdvdmVybm1lbnQxDDAKBgNVBAsTA0RvRDEM
MAoGA1UECxMDUEtJMRgwFgYDVQQDEw9ET0QgRU1BSUwgQ0EtMjMwHhcNMTEwODE2MDAwMDAwWhcN
MTQwODE1MjM1OTU5WjB1MQswCQYDVQQGEwJVUzEYMBYGA1UEChMPVS5TLiBHb3Zlcm5tZW50MQww
CgYDVQQLEwNEb0QxDDAKBgNVBAsTA1BLSTEMMAoGA1UECxMDVVNOMSIwIAYDVQQDExlNQVJMT1cu
REFWSUQuVC4xMjI5NTE3NzQ3MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEA1hUT+J59
rmaSpQBhjLIa9nYG4fJ5ByHukGxpBFu1iy1apXJgyMZlgP5d0AflQTVCC2BCTTt35DN8Cl4vQax2
klkF3v6s40QHq1TOwnmZxy+0GbQYVIbQaCzh1VTZJmH5pzWMUQcON9v/9yOQPJuj9xMWhWN3/plA
thMIA+ngwtU67lO8yYAfNrnDQmGob/ARQtnvLzIxM5l7J+r37rwmEnRUSt+wKc7fw4AOx8/jr0DF
3XzBSZ2Yp/k8WiOtZlnbFs6WMJ1b/qfg/lzNiA5S1FMU9ruZ3onQ4bZVQIWz3Get2razmnAgvC2f
QSMGLyVOO7qNSlfGzXPXwEQIq42HUwIDAQABo4IBXjCCAVowHwYDVR0jBBgwFoAUW5YtMaXh9ppq
XF6BUTZhHpYkGdEwOgYDVR0fBDMwMTAvoC2gK4YpaHR0cDovL2NybC5kaXNhLm1pbC9jcmwvRE9E
RU1BSUxDQV8yMy5jcmwwDgYDVR0PAQH/BAQDAgUgMCMGA1UdIAQcMBowCwYJYIZIAWUCAQsJMAsG
CWCGSAFlAgELEzAdBgNVHQ4EFgQUOx867pREXtQ5X7SlZIb9zZs6mNIwaAYIKwYBBQUHAQEEXDBa
MDYGCCsGAQUFBzAChipodHRwOi8vY3JsLmRpc2EubWlsL3NpZ24vRE9ERU1BSUxDQV8yMy5jZXIw
IAYIKwYBBQUHMAGGFGh0dHA6Ly9vY3NwLmRpc2EubWlsMCAGA1UdEQQZMBeBFWRhdmlkLm1hcmxv
d0BuYXZ5Lm1pbDAbBgNVHQkEFDASMBAGCCsGAQUFBwkEMQQTAlVTMA0GCSqGSIb3DQEBBQUAA4IB
AQCdB6W990/yk7O3DGDHbsEVmGUE9EZytv41BfekZ8MCL+dgJRL2Rym94HrXvqg7Kipammw9qoVc
5COR6Sgy98i6eVpmxNiSiOsSgRJFoo05AK4fI0JDx85PxELINmiW6k7e9TH1MXHjMWl+QthSAOrY
QNIItUsAlDBEzyy9bEoSRw86NNDoB05Qyb3m4whuBJw85WHQwh2hIVgT8lYXS8B1G2byoQG+GZid
TEAit6LJd7M6A5DoDF/8pTdzZzZW/r5xNEJOCHUkelTZsm0ghiK8t29YGmikX33rMMkkXGY8IZWJ
+J2cF98X7ShYog4gVtEA/SwKlOFqMZXOcA6Q0jVLMIIE+jCCA+KgAwIBAgIDKnOOMA0GCSqGSIb3
DQEBBQUAMF0xCzAJBgNVBAYTAlVTMRgwFgYDVQQKEw9VLlMuIEdvdmVybm1lbnQxDDAKBgNVBAsT
A0RvRDEMMAoGA1UECxMDUEtJMRgwFgYDVQQDEw9ET0QgRU1BSUwgQ0EtMjMwHhcNMTEwODE2MDAw
MDAwWhcNMTQwODE1MjM1OTU5WjB1MQswCQYDVQQGEwJVUzEYMBYGA1UEChMPVS5TLiBHb3Zlcm5t
ZW50MQwwCgYDVQQLEwNEb0QxDDAKBgNVBAsTA1BLSTEMMAoGA1UECxMDVVNOMSIwIAYDVQQDExlN
QVJMT1cuREFWSUQuVC4xMjI5NTE3NzQ3MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEA
2y1AK/aiN3PY41xnuEAMRepXNeX1oiy61HRX9M0iP0D8kBLt1IAHmeJHnhS1Nm3T8vV8/bfp3Pwb
m2cGMLk9bTp1uimq9Vj6okF4wskAp9LBi9VkeC1q1t03XaiLdeclry/10fuzZfbR9PmsLPgJwTQ6
H/qw63p29faXMbgkVAJqPp3WQPGuZhPZGG+CVUyetesBg1jA9DHONqv9YXH7xUFZoEEm07uAElds
rwz4w/7wdzD8d2VX1B+Ux8k1PQCiIsKzIzqwxYIz0+6JeMy0xh/hldjK/PJsUC+gHXTA7617Ymqt
QDeT1xyMDIbMPGqh/LkDlIz3sVtxNGj/BnzOnQIDAQABo4IBqTCCAaUwHwYDVR0jBBgwFoAUW5Yt
MaXh9ppqXF6BUTZhHpYkGdEwOgYDVR0fBDMwMTAvoC2gK4YpaHR0cDovL2NybC5kaXNhLm1pbC9j
cmwvRE9ERU1BSUxDQV8yMy5jcmwwDgYDVR0PAQH/BAQDAgbAMCMGA1UdIAQcMBowCwYJYIZIAWUC
AQsJMAsGCWCGSAFlAgELEzAdBgNVHQ4EFgQUEpX7sw4yaww2Xb0+z1Q8mNkmr/UwaAYIKwYBBQUH
AQEEXDBaMDYGCCsGAQUFBzAChipodHRwOi8vY3JsLmRpc2EubWlsL3NpZ24vRE9ERU1BSUxDQV8y
My5jZXIwIAYIKwYBBQUHMAGGFGh0dHA6Ly9vY3NwLmRpc2EubWlsMEAGA1UdEQQ5MDeBFWRhdmlk
Lm1hcmxvd0BuYXZ5Lm1pbKAeBgorBgEEAYI3FAIDoBAMDjEyMjk1MTc3NDdAbWlsMBsGA1UdCQQU
MBIwEAYIKwYBBQUHCQQxBBMCVVMwKQYDVR0lBCIwIAYKKwYBBAGCNxQCAgYIKwYBBQUHAwIGCCsG
AQUFBwMEMA0GCSqGSIb3DQEBBQUAA4IBAQBNIsaVvCpUVHf1ebSv+qKDPvvkV1890lMCx9W0ohbw
KxlFcwxLs5R1JN5jrXThLQW25dZp8m+6Z/UeT4LyJeRdlxebOqPckz1na+dmcLTwY9ec6Uos46zU
qOLFP+mmPAuie+YUQnRNk2V2ixexwhRlfdOYteIf8Kt0aFlOOqFRrIz29EedSV6D3Y6F5DMIGixq
RkdudhF0lKzauuAHwkmHgFVdPBnktqOBjiyLvrHjn1vtPBtxNbuHwd2fbECsGvrhAvPSza9DZ7MD
kx6alzPemLFSlwjcPCzeznZn6/t8Jjh5YiZ33mm6jT+vhnFqmFM1k2TLxkihFfwIWUc5PZGnMIIF
jzCCBHegAwIBAgIBSTANBgkqhkiG9w0BAQUFADBbMQswCQYDVQQGEwJVUzEYMBYGA1UEChMPVS5T
LiBHb3Zlcm5tZW50MQwwCgYDVQQLEwNEb0QxDDAKBgNVBAsTA1BLSTEWMBQGA1UEAxMNRG9EIFJv
b3QgQ0EgMjAeFw0wOTAxMjYxNjQzMjVaFw0xNTAxMjUxNjQzMjVaMF0xCzAJBgNVBAYTAlVTMRgw
FgYDVQQKEw9VLlMuIEdvdmVybm1lbnQxDDAKBgNVBAsTA0RvRDEMMAoGA1UECxMDUEtJMRgwFgYD
VQQDEw9ET0QgRU1BSUwgQ0EtMjMwggEiMA0GCSqGSIb3DQEBAQUAA4IBDwAwggEKAoIBAQC99ClN
V5NEAweNBh+u+jw0VjRA57EYf2wlbheFBQUj6fbFUCVPgeQjMEJxaer3uJ73b6zeXar81uCNvGvu
fZmVIjuzWMaxUhyyqL8xQCIG/o0o0qlQVWoeB3D4pkjJbf2u7L6AbD3PkNQHok6RFAO/V1kS9XTe
Q5ZaWrnPuUfof9COsPjY6Us0XsxLF44C8BK/8gRsHRO/qxzeDQnsy5tW7dmQ55alfyZlYcHEm2gk
pc3SeSNvwzzBhR5I+T5QcWKgQbpyRKVD46Vybs3Oq9rLhNIavx9uchE/LZkfbbD7BTDO5uwjKmVH
H3icDZ9MJHVsdtLVOxdEFrKKKEjXuQ2vAgMBAAGjggJaMIICVjAOBgNVHQ8BAf8EBAMCAYYwHwYD
VR0jBBgwFoAUSXS7DF66ev4CVO97oMaVxgmAcJYwHQYDVR0OBBYEFFuWLTGl4faaalxegVE2YR6W
JBnRMAwGA1UdJAQFMAOAAQAwEgYDVR0TAQH/BAgwBgEB/wIBADCBnwYDVR0gBIGXMIGUMAsGCWCG
SAFlAgELBTALBglghkgBZQIBCwkwCwYJYIZIAWUCAQsKMAsGCWCGSAFlAgELEjALBglghkgBZQIB
CxMwCwYJYIZIAWUCAQsUMAwGCmCGSAFlAwIBAwYwDAYKYIZIAWUDAgEDBzAMBgpghkgBZQMCAQMI
MAwGCmCGSAFlAwIBAw0wDAYKYIZIAWUDAgEDETA/BgNVHR8EODA2MDSgMqAwhi5odHRwOi8vY3Js
LmRpc2EubWlsL2dldGNybD9Eb0QlMjBSb290JTIwQ0ElMjAyMIH+BggrBgEFBQcBAQSB8TCB7jA/
BggrBgEFBQcwAoYzaHR0cDovL2NybC5kaXNhLm1pbC9nZXRJc3N1ZWRUbz9Eb0QlMjBSb290JTIw
Q0ElMjAyMCAGCCsGAQUFBzABhhRodHRwOi8vb2NzcC5kaXNhLm1pbDCBiAYIKwYBBQUHMAKGfGxk
YXA6Ly9jcmwuZ2RzLmRpc2EubWlsL2NuJTNkRG9EJTIwUm9vdCUyMENBJTIwMiUyY291JTNkUEtJ
JTJjb3UlM2REb0QlMmNvJTNkVS5TLiUyMEdvdmVybm1lbnQlMmNjJTNkVVM/Y0FDZXJ0aWZpY2F0
ZTtiaW5hcnkwDQYJKoZIhvcNAQEFBQADggEBAD729uQP1FfNvu3pxEVS2kVbGKY2OTAKtn7r9on8
p2Iusz+DfeESGobTY5T0dPTOcZfq+8RqOl3imaesw+I2+Oh49NjEUO6KgVX6ioNlDMXyTczpH497
Rt0DCpzq4qxjdwfLMlTbCFWyWAB9XKa5FjxfZW0vBc5aP5rbScuSo6HZb1HU9cAIwaM5W9BBY4HE
lGVkYylMXfBfcYdqnZaS5ceC/S101wJsyuLboLPbcdUOhj4+F4m9bkIXG7T2OfkaveYuLJsONzsQ
X0T+e7WUWNZxJeU50SO6NADBQ2249A6Xq7Iw9oinjo6KEAOEdNyuTfnlmXQaqaIKbQsHFZTFP2Mx
ggMyMIIDLgIBATBkMF0xCzAJBgNVBAYTAlVTMRgwFgYDVQQKEw9VLlMuIEdvdmVybm1lbnQxDDAK
BgNVBAsTA0RvRDEMMAoGA1UECxMDUEtJMRgwFgYDVQQDEw9ET0QgRU1BSUwgQ0EtMjMCAypzjjAJ
BgUrDgMCGgUAoIIBozAYBgkqhkiG9w0BCQMxCwYJKoZIhvcNAQcBMBwGCSqGSIb3DQEJBTEPFw0x
MTA4MjQyMDUyMjJaMCMGCSqGSIb3DQEJBDEWBBQumeO+Ak7FI2VOs78Z44AegFw92jBYBgkqhkiG
9w0BCQ8xSzBJMAoGCCqGSIb3DQMHMA4GCCqGSIb3DQMCAgIAgDAHBgUrDgMCBzANBggqhkiG9w0D
AgIBKDAHBgUrDgMCGjAKBggqhkiG9w0CBTBzBgkrBgEEAYI3EAQxZjBkMF0xCzAJBgNVBAYTAlVT
MRgwFgYDVQQKEw9VLlMuIEdvdmVybm1lbnQxDDAKBgNVBAsTA0RvRDEMMAoGA1UECxMDUEtJMRgw
FgYDVQQDEw9ET0QgRU1BSUwgQ0EtMjMCAypzjzB1BgsqhkiG9w0BCRACCzFmoGQwXTELMAkGA1UE
BhMCVVMxGDAWBgNVBAoTD1UuUy4gR292ZXJubWVudDEMMAoGA1UECxMDRG9EMQwwCgYDVQQLEwNQ
S0kxGDAWBgNVBAMTD0RPRCBFTUFJTCBDQS0yMwIDKnOPMA0GCSqGSIb3DQEBAQUABIIBADzapFU0
xfwMS2F87ylu0Lzn+XfXZ0Flivor8sikxEN/h2Mi3xEtcstNhDF6PkFjSb24yN7GzlXA8lQdTyFQ
KQMI8zME4Qbf2n8KrdyGO60K1fRBUArbdglUIKxdFj7rGr2YvfUx283vBdsnhmSbDmD7wvDtUhxl
IYDdrdmtvbwg7vbLDTYuj7J70NuD2fGevI/ZuM3q+gJoydRJRs1s/26Ui9a8HWHQ0fTnxPfKYO3k
zVt8Hp49vlGjBF5OyoYp4fDQQRA+xIyZDLBH3LmrJbZPEhihFJKWuIDssP852bRsmh2GWtjA0w5Y
TlIUpFWF2JfLhDfjkttbVhi5IT+aTVcAAAAAAAA=

------=_NextPart_000_0FE7_01CC627E.315CFA00--

From mills@udel.edu  Fri Aug 26 10:59:04 2011
Return-Path: <mills@udel.edu>
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 D67BE21F86CA for <tictoc@ietfa.amsl.com>; Fri, 26 Aug 2011 10:59:04 -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 dwuZ4tar7g6G for <tictoc@ietfa.amsl.com>; Fri, 26 Aug 2011 10:59:03 -0700 (PDT)
Received: from mail.eecis.udel.edu (louie.udel.edu [128.4.40.12]) by ietfa.amsl.com (Postfix) with ESMTP id 4EE3821F8593 for <tictoc@ietf.org>; Fri, 26 Aug 2011 10:59:03 -0700 (PDT)
Received: from [192.168.1.2] (pool-173-75-253-165.phlapa.fios.verizon.net [173.75.253.165]) (Authenticated sender: mills@mail.eecis.udel.edu) by mail.eecis.udel.edu (Postfix) with ESMTP id BF6AD3EE; Fri, 26 Aug 2011 14:00:15 -0400 (EDT)
Message-ID: <4E57DF0B.3010407@udel.edu>
Date: Fri, 26 Aug 2011 17:59:39 +0000
From: "David L. Mills" <mills@udel.edu>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.7.2) Gecko/20040804 Netscape/7.2 (ax)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: "Marlow, David T CIV NSWCDD, W64" <david.marlow@navy.mil>
References: <4DF03979.5070204@pobox.com> <A3E5B6E9262F674FA0C82876819BBD0460D7EA@naeamillez04v.nadsusea.nads.navy.mil>
In-Reply-To: <A3E5B6E9262F674FA0C82876819BBD0460D7EA@naeamillez04v.nadsusea.nads.navy.mil>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: quoted-printable
Cc: ntpwg@lists.ntp.org, tictoc@ietf.org
Subject: Re: [TICTOC] Renamed: Interleave Questions
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, 26 Aug 2011 17:59:05 -0000

David,

The campus and backroom experiments were designed to measure the=20
magnitude of the queuing and transmission components of the roundtrip=20
delay and only secondarily to maintain synchronization.. In any case,=20
measurement of these delays in client/server mode is not possible, as=20
the server keeps no state. The GPS receivers used in the experiments do=20
not support either broadcast mode or symmetric mode in either the basic=20
or interleaved variants.

While measurement of the output queuing and transmission delays is=20
possible in interleaved modes, it is not possible to measure the input=20
processing delay, which is significant in the Solaris operating system=20
implementation. I suspect this can be determined using the Solaris=20
DTrace  measurement tools, but so far this has not been done.

Dave,,

David T CIV NSWCDD, W64 wrote:

>Dave,
>   A while back in an email thread you pointed out that our ID (draft-ma=
rlow-tictoc-computer-clock-accuracy-00.txt) only addressed interleaved br=
oadcast and did not include interleaved symmetric mode and that a lot of =
the detail information is in your book.  We bought the book and have lear=
ned a lot particularly in section 16.6 where you have measurement data fo=
r interleave mode operation.  Your Backroom LAN example is similar to the=
 experiments we ran.  We had some questions:
>
>1) In your Backroom LAN example the GPS clock server ran in client/serve=
r mode with clients Macabre and Mort.  Would you expect better accuracy i=
f client/server mode is used (as you did) versus if interleave broadcast =
mode were used between this server and these two clients? =20
>
>2)Similar in your Campus LAN example you used client/server mode in some=
 of the operations versus using interleave broadcast, where is client/ser=
ver mode better than interleave broadcast to use?
>
>3) In your Backroom LAN example, Macabre and Mort ran interleaved symmet=
ric mode between each other.  Would not the dominant synchronization fact=
or come from the GPS clock server, given its lower stratum number?  Is th=
e interleaved symmetric mode exchanges providing a secondary effect to ke=
ep these two together?
>
>  Dave=20
>
>
>-----Original Message-----
>From: tictoc-bounces@ietf.org [mailto:tictoc-bounces@ietf.org] On Behalf=
 Of Karen O'Donoghue
>Sent: Wednesday, June 08, 2011 23:10
>To: NTP Working Group; tictoc@ietf.org
>Subject: [TICTOC] Fwd: Re: [ntpwg] Fwd: reminder for remote participatio=
n in today's tictoc meeting
>
>Folks,
>
>This came to me personally, and I neglected to send it on to the ntp and=
 tictoc wg lists. My apologies for the delay. The question before us is w=
hether or not the interleave capability should be properly documented and=
 where the resources will come from to complete the effort.=20
>
>Karen
>
>-------- Original Message --------=20
>Subject: 	Re: [ntpwg] Fwd: [TICTOC] reminder for remote participation in=
 today's tictoc meeting	=20
>Date: 	Tue, 12 Apr 2011 18:18:43 +0000	=20
>From: 	David L. Mills <mills@udel.edu> <mailto:mills@udel.edu> 	=20
>To: 	kodonog@pobox.com	=20
>
>
>Karen,
>
>The following is in response to the ID you distributed. I offer it as a =
candidate for distribution to th eWG members.
>
>Dave
>
>This internet draft describes experiments using the interleaved broadcas=
t mode recently incorporated in the NTP reference implementation. The exp=
eriments do not include the interleaved symmetric mode, which provides si=
milar functionality in peer-to-peer configurations. For reference, these =
modes, their relevance to PTP and related information are discussed in de=
tail in Chapters 15 through 17 of the book "Network Time Synchronization =
- the Network Time Protocol on Earth and in Space, Second Edition, CRC Pr=
ess 2011, as cited on my web page www.eedis.udel.edu/~mills <http://www.e=
edis.udel.edu/%7Emills> . However, most of the information relevant to th=
e followings discussion can be found in the white papers at www.eecis.ude=
l.edu/~mills/ntp.html <http://www.eecis.udel.edu/%7Emills/ntp.html> . Of =
particular interest are the documents "Analysis and Simulation of the NTP=
 On-Wire Protocol" and "Security Analysis of the NTP Protocol." Both of t=
hese documents represent an update since th!
>!
>e book was published late last year.
>
>Readers may wonder why these documents have not been published as an upd=
ate to the protocol specification RFC-5905, which would have been the exp=
ectation several years ago in the adolescent Internet. However, the effor=
t necessary to publish an ID with figures, tables and equations is nowada=
ys simply unacceptable. My experience with RFC-5905 and RFC-5906 over the=
 last five years of publishing effort is not sustainable. Thus, unless so=
me collaboration, perhaps the TICTOC working group, chose to publish them=
 as IDs, I will not commit that adventure myself.
>
>First some nomenclature that may help in the following discussion. Times=
tamps captured for the clock discipline are classed as hardstamps, drives=
tamps and softstamps. Softstamps are captured during the course of user-s=
pace processing; they may be corrupted by operating system and device lat=
encies, as well as transmission delays. Drivestamps are captured during t=
he packet interrupt routines, so are much less affected by operating syst=
em scheduling and competition with other programs. Hardstamps are capture=
d by dedicated hardware means, typically in the PHY layer of the network =
interface card (NIC). While the details vary, the typical intercept point=
 is the media independent interface (MII), which monitors the frame level=
 interface on a character by character basis. The capture means is usuall=
t a field-programmable gate array (FPGA) that parses the packeet, inserts=
 timestamp data and recomputes the UDP checksum.
>
>The interleaved capability was originally not intended for NTP, but for =
the Proximity-1 protocol specified by the Consultive Committee on Space D=
ata systems (CCSDS). The Proximity-1 protocol is designed for communicati=
on between spacecraft in the vicinity of Mars and for future missions in =
the vicinity of the Moon. Space data links are often operated at very low=
 data rates compared to typical Ethernet links. Typical rates range from =
1 kb/s to 256 kb/s with very different data rates in each direction. Due =
to various queuing and transmission operations, the output delay can reac=
h 30 s, so it is imparities that timestamps be captured close to the PHY =
layer. In the Proximity-1 desing, hardstamps are captured upon the passag=
e of the ASM code combination at the beginning of each transmitted frame.=
=2E
>
>Queuing and transmission delays are not the only contributors to space d=
ata link delay. Reed-Solomon and convolutional encoding delays can be a l=
arge contribution to the link delay; however, these delays are a constant=
 contribution to the lightwave transmission delay. These contributions - =
up to many seconds - can dwarf the lightwave transmission delays.
>
>In the NTP interleaved design, drivestamps are captured in the device in=
terrupt routine - on input immediately after the frame has been received =
and before copying to an input buffer; on output shortly after the frame =
has been transmitted and before the buffer is released for the following =
input or output frame. This can become rather awkward in the case of NICs=
 of the PCNET architecture, as data are copied directly from user space t=
o device buffers directed by DMA descriptors. Drivestamps have been used =
on input for many years, but for output this is possible only using the i=
nterleaved modes. The result avoids the latencies due to the message dige=
st computation, Autokey protocol data units, output queuing and frame tra=
nsmissions, typically some 10-40 microseconds.
>
>It should be obvious from the documents that a primary motivation for th=
e NTP interleaved design was protection from network errors and intruder =
attack. The detailed analysis and simulation are designed to demonstrate =
resistance to common corruptions such as dropped or duplicate packets and=
 possible bogus attacks. The NTP design includes a four-level security mo=
del, the lower two levels might be considered for a PTP application. This=
 is one of the most important difference between the PTP and NTP protocol=
 designs; however, the NTP design might be considered overkill in a shelt=
ered, isolated Ethernet network.
>
>Careful observers may notice an interesting anomaly with the interleaved=
 broadcast mode. The preliminary volley intended to measure the roundtrip=
 time uses basic mode, not interleaved mode. The reason for this requires=
 some explanation. In times of old, the dominant concern was the 6-bone, =
an international consortium of multicast application developers. In that =
context with historic multicast configurations, including DVMRP and PIM, =
the multicast spanning tree was far different than the unicast spanning t=
ree. Therefore, the preliminary volley was important to estimate the offs=
et of the multicast server to the multicast client and thus the apparent =
one-way delay. In principle, with adroit protocolmanship, it would be pos=
sible to change the protocol to measure the interleaved roundtrip delay, =
which would be more appropriate for modern high-speed Ethernet networks.
>
>Karen O'Donoghue wrote:
>
>
>
>
>	-------- Original Message --------=20
>Subject: 	[TICTOC] reminder for remote participation in today's tictoc m=
eeting	=20
>Date: 	Thu, 31 Mar 2011 09:56:35 +0200	=20
>From: 	Karen O'Donoghue <odonoghue@isoc.org> <mailto:odonoghue@isoc.org>=
 	=20
>Reply-To: 	odonoghue@isoc.org	=20
>Organization: 	ISOC	=20
>To: 	tictoc@ietf.org, NTP Working Group <ntpwg@lists.ntp.org> <mailto:nt=
pwg@lists.ntp.org> 	=20
>
>
>	Folks,
>=09
>	This is a reminder that the tictoc working group will meet today from=20
>	17:40 - 19:40 CEST (15:40 - 17:40 UTC). The tools agenda for the IETF=20
>	meeting (http://tools.ietf.org/agenda/80/) has links for the drafts,=20
>	presentations, jabber chat room, and audio streaming to facilitate=20
>	remote participation.
>=09
>	Regards,
>	Karen
>=09
>	_______________________________________________
>	TICTOC mailing list
>	TICTOC@ietf.org
>	https://www.ietf.org/mailman/listinfo/tictoc
>	 =20
>=09
>________________________________
>
>
>	_______________________________________________
>	ntpwg mailing list
>	ntpwg@lists.ntp.org
>	http://lists.ntp.org/listinfo/ntpwg
>
>
> =20
>


