
From lizhong.jin@zte.com.cn  Fri Jul  1 04:47:22 2011
Return-Path: <lizhong.jin@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 67E1A21F868F; Fri,  1 Jul 2011 04:47:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.838
X-Spam-Level: 
X-Spam-Status: No, score=-101.838 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_DOUBLE_IP_LOOSE=0.76,  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 qM3gjh+8MZ2R; Fri,  1 Jul 2011 04:47:21 -0700 (PDT)
Received: from mx5.zte.com.cn (mx5.zte.com.cn [63.217.80.70]) by ietfa.amsl.com (Postfix) with ESMTP id 400C921F8689; Fri,  1 Jul 2011 04:47:20 -0700 (PDT)
Received: from [10.30.17.99] by mx5.zte.com.cn with surfront esmtp id 48643314101978; Fri, 1 Jul 2011 19:46:14 +0800 (CST)
Received: from [10.30.3.21] by [192.168.168.15] with StormMail ESMTP id 13796.7481467973; Fri, 1 Jul 2011 19:47:12 +0800 (CST)
Received: from notes_smtp.zte.com.cn ([10.30.1.239]) by mse02.zte.com.cn with ESMTP id p61Bl5Dc009505; Fri, 1 Jul 2011 19:47:05 +0800 (GMT-8) (envelope-from lizhong.jin@zte.com.cn)
In-Reply-To: <mailman.19.1294603216.20299.mpls@ietf.org>
To: lamberto.sterling@gmail.com, maillist.ed@gmail.com
MIME-Version: 1.0
X-Mailer: Lotus Notes Release 6.5.6 March 06, 2007
Message-ID: <OF4F84D97A.315FF9D7-ON482578C0.003EF3F1-482578C0.0040BD58@zte.com.cn>
From: lizhong.jin@zte.com.cn
Date: Fri, 1 Jul 2011 19:46:34 +0800
X-MIMETrack: S/MIME Sign by Notes Client on JinLiZhong127666/user/zte_ltd(Release 6.5.6|March 06, 2007) at 2011-07-01 19:47:07, Serialize by Notes Client on JinLiZhong127666/user/zte_ltd(Release 6.5.6|March 06, 2007) at 2011-07-01 19:47:07, Serialize complete at 2011-07-01 19:47:07, S/MIME Sign failed at 2011-07-01 19:47:07: The cryptographic key was not found, Serialize by Router on notes_smtp/zte_ltd(Release 8.5.1FP4|July 25, 2010) at 2011-07-01 19:47:09, Serialize complete at 2011-07-01 19:47:09
Content-Type: multipart/alternative; boundary="=_alternative 0040BD56482578C0_="
X-MAIL: mse02.zte.com.cn p61Bl5Dc009505
Cc: l2vpn@ietf.org, mpls@ietf.org, Ice  <ice@cisco.com>, tictoc@ietf.org, N.Leymann@telekom.de
Subject: Re: [TICTOC] [mpls] Request comments for HSMP LSP
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, 01 Jul 2011 11:47:22 -0000

This is a multipart message in MIME format.
--=_alternative 0040BD56482578C0_=
Content-Type: text/plain; charset="US-ASCII"

Hi Edward, Lamberto and all,
Sorry for the later reply. And no, when apply HSMP LSP to VPLS, the path 
from leaf PE to root PE is exactly the shortest path. mLDP leaf will send 
mapping message to root node, choosing the path with routing table, and 
this path is the shortest path from leaf to root.

We have updated the draft with more clarification of the use cases, and 
added new use case of VPLS application.
You can get the new draft from link: 
http://tools.ietf.org/html/draft-jin-jounay-mpls-mldp-hsmp-03

Thank you.
Lizhong


> 
> ----------------------------------------------------------------------
> 
> Message: 1
> Date: Sun, 9 Jan 2011 02:50:16 +0100
> From: Lamberto Sterling <lamberto.sterling@gmail.com>
> Subject: Re: [mpls] Request comments for HSMP LSP
> To: maillist.ed@gmail.com, lizhong.jin@zte.com.cn
> Cc: l2vpn@ietf.org, mpls@ietf.org, Ice <ice@cisco.com>,
>    tictoc@ietf.org,   N.Leymann@telekom.de
> Message-ID:
>    <AANLkTi=CbhP10iM7=wXcb=e9oV0cqwaTKjY7ArZquoW1@mail.gmail.com>
> Content-Type: text/plain; charset="iso-8859-1"
> 
> Hi guys,
> Sorry for the email subject. Change it now.
> 
> Lamberto
> 
> On Sat, Jan 8, 2011 at 5:19 PM, Lamberto Sterling <
> lamberto.sterling@gmail.com> wrote:
> 
> > Hi Lizhong, Edward,
> > It seems that it is a good idea to apply HSMP LSP to VPLS, and the
> > broadcast/unicast/unknow packet would be optimized. However, the path 
from
> > leaf to root may not be the best path compared with current VPLS using 
P2P
> > LSP, which is not a critical issue.
> >
> > Thanks
> > Lamberto
> >
> >
> >
> >>
> >> ------------------------------
> >>
> >>
> >> Date: Wed, 5 Jan 2011 15:50:45 +0800
> >> From: lizhong.jin@zte.com.cn
> >> Subject: Re: [mpls] Request comments for HSMP LSP
> >> To: Ed <maillist.ed@gmail.com>
> >> Cc: l2vpn@ietf.org, mpls@ietf.org, Ice <ice@cisco.com>,
> >>        N.Leymann@telekom.de,   tictoc@ietf.org
> >> Message-ID:
> >>        <
> >> OF4BA0BF75.A883E04C-ON4825780F.002802E4-4825780F.002B2AB9@zte.com.cn>
> >> Content-Type: text/plain; charset="us-ascii"
> >>
> >> Hi Edward,
> >> Thank you for the comments. I add l2vpn maillist in cc list. I agree 
with
> >> the application you proposed, and in order to improve the scalability 
of
> >> VPLS, P2MP PW multiplexed to HSMP LSP could be used for VPLS. 
Actually
> >> this is a good application case for P2MP PW with reverse path 
(section
> >> 4.4, draft-ietf-pwe3-p2mp-pw-00). We can add some description about 
this
> >> use case.
> >>
> >> Regards
> >> Lizhong
> >>
> >>
> >> Ed <maillist.ed@gmail.com> wrote on 2011-01-05 15:05:30:
> >>
> >> > Hi Lizhong,
> >> >
> >> > I think one possible application for HSMP LSPs is to reduce the
> >> > overall broadcast/multicast utilization on a VPLS. In current VPLS
> >> > implementations with a full mesh of P2P LSPs between PEs, 
broadcast,
> >> > multicast and unknown traffic are not efficiently propagated on the
> >> > physical links between PEs and Ps.
> >> >
> >> > In the VPLS implementation scenario with HSMP LSPs, each PE signals
> >> > a HSMP LSP with itself as a root to all other PEs in the VPLS.
> >> > Thereafter, all broadcast/multicast/unknown traffic from this PE
> >> > will use this HSMP LSP. Unicast traffic from a particular PE (e.g.
> >> > PE1) to another PE (e.g. PE2) will be sent from leaf to root using
> >> > the HSMP LSP where PE2 is the root.
> >> >
> >> > This simplifies the VPLS implementation by:
> >> > -          Reducing traffic utilization from broadcast, multicast
> >> > and unknown traffic
> >> > -          Reducing the total number of LSPs maintained by each PE
> >> > (i.e. instead of requiring a full mesh of LSPs, now only require 
one
> >> > HSMP LSP per PE).
> >> >
> >> > This is similar to the idea expressed in  draft-key-l2vpn-etree-
> >> > frwk-03.txt (in a more general sense).
> >> >
> >> > What do you think? Would HSMP LSP be suitable for this?
> >> >
> >> > Regards,
> >> > Edward
> >> >
> >> >
> >> >
> >> > On Wed, Jan 5, 2011 at 5:24 PM, <lizhong.jin@zte.com.cn> wrote:
> >> >
> >> > Hi all,
> >> > During IETF 79 Beijing, we made a presentation for HSMP LSP at MPLS
> >> session.
> >> > HSMP LSP has several use cases described in the draft, e.g, time
> >> > synchronization in MPLS network, IPTV scenario, or P2MP PW. It 
would
> >> > be appreciated if you could give more scenarios for HSMP LSP. 
Please
> >> > review the draft, and any comments are welcome.
> >> >
> >> > The draft link is: 
http://tools.ietf.org/html/draft-jin-jounay-mpls-
> >> > mldp-hsmp-01
> >> >
> >> > Thank you.
> >> > Authors of draft-hsmp.
> >> > --------------------------------------------------------
> >> >
> >>
> >
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL: <http://www.ietf.org/mail-
> archive/web/mpls/attachments/20110109/e5b476e5/attachment.html>
> 
> ------------------------------
> 
> _______________________________________________
> mpls mailing list
> mpls@ietf.org
> https://www.ietf.org/mailman/listinfo/mpls
> 
> 
> End of mpls Digest, Vol 81, Issue 12
> ************************************
> 


--------------------------------------------------------
ZTE Information Security Notice: The information contained in this mail is solely property of the sender's organization. This mail communication is confidential. Recipients named above are obligated to maintain secrecy and are not permitted to disclose the contents of this communication to others.
This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the originator of the message. Any views expressed in this message are those of the individual sender.
This message has been scanned for viruses and Spam by ZTE Anti-Spam system.

--=_alternative 0040BD56482578C0_=
Content-Type: text/html; charset="US-ASCII"


<br><tt><font size=2>Hi Edward, Lamberto and all,</font></tt>
<br><tt><font size=2>Sorry for the later reply. And no, when apply HSMP
LSP to VPLS, the path from leaf PE to root PE is exactly the shortest path.
mLDP leaf will send mapping message to root node, choosing the path with
routing table, and this path is the shortest path from leaf to root.</font></tt>
<br>
<br><tt><font size=2>We have updated the draft with more clarification
of the use cases, and added new use case of VPLS application.</font></tt>
<br><tt><font size=2>You can get the new draft from link: http://tools.ietf.org/html/draft-jin-jounay-mpls-mldp-hsmp-03</font></tt>
<br>
<br><tt><font size=2>Thank you.</font></tt>
<br><tt><font size=2>Lizhong</font></tt>
<br>
<br><tt><font size=2><br>
&gt; <br>
&gt; ----------------------------------------------------------------------<br>
&gt; <br>
&gt; Message: 1<br>
&gt; Date: Sun, 9 Jan 2011 02:50:16 +0100<br>
&gt; From: Lamberto Sterling &lt;lamberto.sterling@gmail.com&gt;<br>
&gt; Subject: Re: [mpls] Request comments for HSMP LSP<br>
&gt; To: maillist.ed@gmail.com, lizhong.jin@zte.com.cn<br>
&gt; Cc: l2vpn@ietf.org, mpls@ietf.org, Ice &lt;ice@cisco.com&gt;,<br>
&gt; &nbsp; &nbsp;tictoc@ietf.org, &nbsp; N.Leymann@telekom.de<br>
&gt; Message-ID:<br>
&gt; &nbsp; &nbsp;&lt;AANLkTi=CbhP10iM7=wXcb=e9oV0cqwaTKjY7ArZquoW1@mail.gmail.com&gt;<br>
&gt; Content-Type: text/plain; charset=&quot;iso-8859-1&quot;<br>
&gt; <br>
&gt; Hi guys,<br>
&gt; Sorry for the email subject. Change it now.<br>
&gt; <br>
&gt; Lamberto<br>
&gt; <br>
&gt; On Sat, Jan 8, 2011 at 5:19 PM, Lamberto Sterling &lt;<br>
&gt; lamberto.sterling@gmail.com&gt; wrote:<br>
&gt; <br>
&gt; &gt; Hi Lizhong, Edward,<br>
&gt; &gt; It seems that it is a good idea to apply HSMP LSP to VPLS, and
the<br>
&gt; &gt; broadcast/unicast/unknow packet would be optimized. However,
the path from<br>
&gt; &gt; leaf to root may not be the best path compared with current VPLS
using P2P<br>
&gt; &gt; LSP, which is not a critical issue.<br>
&gt; &gt;<br>
&gt; &gt; Thanks<br>
&gt; &gt; Lamberto<br>
&gt; &gt;<br>
&gt; &gt;<br>
&gt; &gt;<br>
&gt; &gt;&gt;<br>
&gt; &gt;&gt; ------------------------------<br>
&gt; &gt;&gt;<br>
&gt; &gt;&gt;<br>
&gt; &gt;&gt; Date: Wed, 5 Jan 2011 15:50:45 +0800<br>
&gt; &gt;&gt; From: lizhong.jin@zte.com.cn<br>
&gt; &gt;&gt; Subject: Re: [mpls] Request comments for HSMP LSP<br>
&gt; &gt;&gt; To: Ed &lt;maillist.ed@gmail.com&gt;<br>
&gt; &gt;&gt; Cc: l2vpn@ietf.org, mpls@ietf.org, Ice &lt;ice@cisco.com&gt;,<br>
&gt; &gt;&gt; &nbsp; &nbsp; &nbsp; &nbsp;N.Leymann@telekom.de, &nbsp; tictoc@ietf.org<br>
&gt; &gt;&gt; Message-ID:<br>
&gt; &gt;&gt; &nbsp; &nbsp; &nbsp; &nbsp;&lt;<br>
&gt; &gt;&gt; OF4BA0BF75.A883E04C-ON4825780F.002802E4-4825780F.002B2AB9@zte.com.cn&gt;<br>
&gt; &gt;&gt; Content-Type: text/plain; charset=&quot;us-ascii&quot;<br>
&gt; &gt;&gt;<br>
&gt; &gt;&gt; Hi Edward,<br>
&gt; &gt;&gt; Thank you for the comments. I add l2vpn maillist in cc list.
I agree with<br>
&gt; &gt;&gt; the application you proposed, and in order to improve the
scalability of<br>
&gt; &gt;&gt; VPLS, P2MP PW multiplexed to HSMP LSP could be used for VPLS.
Actually<br>
&gt; &gt;&gt; this is a good application case for P2MP PW with reverse
path (section<br>
&gt; &gt;&gt; 4.4, draft-ietf-pwe3-p2mp-pw-00). We can add some description
about this<br>
&gt; &gt;&gt; use case.<br>
&gt; &gt;&gt;<br>
&gt; &gt;&gt; Regards<br>
&gt; &gt;&gt; Lizhong<br>
&gt; &gt;&gt;<br>
&gt; &gt;&gt;<br>
&gt; &gt;&gt; Ed &lt;maillist.ed@gmail.com&gt; wrote on 2011-01-05 15:05:30:<br>
&gt; &gt;&gt;<br>
&gt; &gt;&gt; &gt; Hi Lizhong,<br>
&gt; &gt;&gt; &gt;<br>
&gt; &gt;&gt; &gt; I think one possible application for HSMP LSPs is to
reduce the<br>
&gt; &gt;&gt; &gt; overall broadcast/multicast utilization on a VPLS. In
current VPLS<br>
&gt; &gt;&gt; &gt; implementations with a full mesh of P2P LSPs between
PEs, broadcast,<br>
&gt; &gt;&gt; &gt; multicast and unknown traffic are not efficiently propagated
on the<br>
&gt; &gt;&gt; &gt; physical links between PEs and Ps.<br>
&gt; &gt;&gt; &gt;<br>
&gt; &gt;&gt; &gt; In the VPLS implementation scenario with HSMP LSPs,
each PE signals<br>
&gt; &gt;&gt; &gt; a HSMP LSP with itself as a root to all other PEs in
the VPLS.<br>
&gt; &gt;&gt; &gt; Thereafter, all broadcast/multicast/unknown traffic
from this PE<br>
&gt; &gt;&gt; &gt; will use this HSMP LSP. Unicast traffic from a particular
PE (e.g.<br>
&gt; &gt;&gt; &gt; PE1) to another PE (e.g. PE2) will be sent from leaf
to root using<br>
&gt; &gt;&gt; &gt; the HSMP LSP where PE2 is the root.<br>
&gt; &gt;&gt; &gt;<br>
&gt; &gt;&gt; &gt; This simplifies the VPLS implementation by:<br>
&gt; &gt;&gt; &gt; - &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;Reducing traffic
utilization from broadcast, multicast<br>
&gt; &gt;&gt; &gt; and unknown traffic<br>
&gt; &gt;&gt; &gt; - &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;Reducing the total
number of LSPs maintained by each PE<br>
&gt; &gt;&gt; &gt; (i.e. instead of requiring a full mesh of LSPs, now
only require one<br>
&gt; &gt;&gt; &gt; HSMP LSP per PE).<br>
&gt; &gt;&gt; &gt;<br>
&gt; &gt;&gt; &gt; This is similar to the idea expressed in &nbsp;draft-key-l2vpn-etree-<br>
&gt; &gt;&gt; &gt; frwk-03.txt (in a more general sense).<br>
&gt; &gt;&gt; &gt;<br>
&gt; &gt;&gt; &gt; What do you think? Would HSMP LSP be suitable for this?<br>
&gt; &gt;&gt; &gt;<br>
&gt; &gt;&gt; &gt; Regards,<br>
&gt; &gt;&gt; &gt; Edward<br>
&gt; &gt;&gt; &gt;<br>
&gt; &gt;&gt; &gt;<br>
&gt; &gt;&gt; &gt;<br>
&gt; &gt;&gt; &gt; On Wed, Jan 5, 2011 at 5:24 PM, &lt;lizhong.jin@zte.com.cn&gt;
wrote:<br>
&gt; &gt;&gt; &gt;<br>
&gt; &gt;&gt; &gt; Hi all,<br>
&gt; &gt;&gt; &gt; During IETF 79 Beijing, we made a presentation for HSMP
LSP at MPLS<br>
&gt; &gt;&gt; session.<br>
&gt; &gt;&gt; &gt; HSMP LSP has several use cases described in the draft,
e.g, time<br>
&gt; &gt;&gt; &gt; synchronization in MPLS network, IPTV scenario, or P2MP
PW. It would<br>
&gt; &gt;&gt; &gt; be appreciated if you could give more scenarios for
HSMP LSP. Please<br>
&gt; &gt;&gt; &gt; review the draft, and any comments are welcome.<br>
&gt; &gt;&gt; &gt;<br>
&gt; &gt;&gt; &gt; The draft link is: http://tools.ietf.org/html/draft-jin-jounay-mpls-<br>
&gt; &gt;&gt; &gt; mldp-hsmp-01<br>
&gt; &gt;&gt; &gt;<br>
&gt; &gt;&gt; &gt; Thank you.<br>
&gt; &gt;&gt; &gt; Authors of draft-hsmp.<br>
&gt; &gt;&gt; &gt; --------------------------------------------------------<br>
&gt; &gt;&gt; &gt;<br>
&gt; &gt;&gt;<br>
&gt; &gt;<br>
&gt; -------------- next part --------------<br>
&gt; An HTML attachment was scrubbed...<br>
&gt; URL: &lt;http://www.ietf.org/mail-<br>
&gt; archive/web/mpls/attachments/20110109/e5b476e5/attachment.html&gt;<br>
&gt; <br>
&gt; ------------------------------<br>
&gt; <br>
&gt; _______________________________________________<br>
&gt; mpls mailing list<br>
&gt; mpls@ietf.org<br>
&gt; https://www.ietf.org/mailman/listinfo/mpls<br>
&gt; <br>
&gt; <br>
&gt; End of mpls Digest, Vol 81, Issue 12<br>
&gt; ************************************<br>
&gt; <br>
</font></tt><br><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&nbsp;of&nbsp;the&nbsp;sender's&nbsp;organization.&nbsp;This&nbsp;mail&nbsp;communication&nbsp;is&nbsp;confidential.&nbsp;Recipients&nbsp;named&nbsp;above&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&nbsp;of&nbsp;this&nbsp;communication&nbsp;to&nbsp;others.
This&nbsp;email&nbsp;and&nbsp;any&nbsp;files&nbsp;transmitted&nbsp;with&nbsp;it&nbsp;are&nbsp;confidential&nbsp;and&nbsp;intended&nbsp;solely&nbsp;for&nbsp;the&nbsp;use&nbsp;of&nbsp;the&nbsp;individual&nbsp;or&nbsp;entity&nbsp;to&nbsp;whom&nbsp;they&nbsp;are&nbsp;addressed.&nbsp;If&nbsp;you&nbsp;have&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&nbsp;views&nbsp;expressed&nbsp;in&nbsp;this&nbsp;message&nbsp;are&nbsp;those&nbsp;of&nbsp;the&nbsp;individual&nbsp;sender.
This&nbsp;message&nbsp;has&nbsp;been&nbsp;scanned&nbsp;for&nbsp;viruses&nbsp;and&nbsp;Spam&nbsp;by&nbsp;ZTE&nbsp;Anti-Spam&nbsp;system.
</pre>
--=_alternative 0040BD56482578C0_=--


From talmi@marvell.com  Mon Jul  4 05:01:02 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 2422C1F0C6C for <tictoc@ietfa.amsl.com>; Mon,  4 Jul 2011 05:01:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.854
X-Spam-Level: 
X-Spam-Status: No, score=-3.854 tagged_above=-999 required=5 tests=[AWL=-2.744, BAYES_05=-1.11, 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 c0QQIPpOAKBO for <tictoc@ietfa.amsl.com>; Mon,  4 Jul 2011 05:01:01 -0700 (PDT)
Received: from galiil.marvell.com (galiil.marvell.com [199.203.130.254]) by ietfa.amsl.com (Postfix) with ESMTP id 33AFE1F0C6A for <tictoc@ietf.org>; Mon,  4 Jul 2011 05:01:01 -0700 (PDT)
From: Tal Mizrahi <talmi@marvell.com>
To: "tictoc@ietf.org" <tictoc@ietf.org>, "ntpwg@lists.ntp.org" <ntpwg@lists.ntp.org>
Date: Mon, 4 Jul 2011 15:00:56 +0300
Thread-Topic: [TICTOC] [ntpwg] New draft: draft-mizrahi-tictoc-checksum-trailer-00
Thread-Index: Acw6QVZgcbH3mJzTRZOF+kYbuNTxSA==
Message-ID: <74470498B659FA4687F0B0018C19A89C01223E573C5A@IL-MB01.marvell.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: multipart/alternative; boundary="_000_74470498B659FA4687F0B0018C19A89C01223E573C5AILMB01marve_"
MIME-Version: 1.0
Subject: [TICTOC] [ntpwg] New draft: draft-mizrahi-tictoc-checksum-trailer-00
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, 04 Jul 2011 12:01:02 -0000

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

Hi,

I have posted a new draft that discusses Checksum updates in time synchroni=
zation protocols.
http://tools.ietf.org/html/draft-mizrahi-tictoc-checksum-trailer-00
Comments will be welcome.

Thanks.
Tal.

--_000_74470498B659FA4687F0B0018C19A89C01223E573C5AILMB01marve_
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;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-family:"Calibri","sans-serif";}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.25in 1.0in 1.25in;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]--></head><body lang=3DEN-US link=3Dblue vli=
nk=3Dpurple><div class=3DWordSection1><p class=3DMsoNormal>Hi,<o:p></o:p></=
p><p class=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3DMsoNormal>I have pos=
ted a new draft that discusses Checksum updates in time synchronization pro=
tocols.<o:p></o:p></p><p class=3DMsoNormal><a href=3D"http://tools.ietf.org=
/html/draft-mizrahi-tictoc-checksum-trailer-00">http://tools.ietf.org/html/=
draft-mizrahi-tictoc-checksum-trailer-00</a><o:p></o:p></p><p class=3DMsoNo=
rmal>Comments will be welcome.<o:p></o:p></p><p class=3DMsoNormal><o:p>&nbs=
p;</o:p></p><p class=3DMsoNormal>Thanks.<o:p></o:p></p><p class=3DMsoNormal=
><span style=3D'font-size:10.0pt;font-family:"Arial","sans-serif"'>Tal.</sp=
an><o:p></o:p></p></div></body></html>=

--_000_74470498B659FA4687F0B0018C19A89C01223E573C5AILMB01marve_--

From internet-drafts@ietf.org  Mon Jul  4 06:08:36 2011
Return-Path: <internet-drafts@ietf.org>
X-Original-To: tictoc@ietfa.amsl.com
Delivered-To: tictoc@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EE8F621F86FA; Mon,  4 Jul 2011 06:08:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.591
X-Spam-Level: 
X-Spam-Status: No, score=-102.591 tagged_above=-999 required=5 tests=[AWL=0.008, BAYES_00=-2.599, 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 zjN9u2dK6i9g; Mon,  4 Jul 2011 06:08:35 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8E61421F86EB; Mon,  4 Jul 2011 06:08:35 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
From: internet-drafts@ietf.org
To: i-d-announce@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 3.55
Message-ID: <20110704130835.12882.25836.idtracker@ietfa.amsl.com>
Date: Mon, 04 Jul 2011 06:08:35 -0700
Cc: tictoc@ietf.org
Subject: [TICTOC] I-D Action: draft-ietf-tictoc-ptp-mib-00.txt
X-BeenThere: tictoc@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Timing over IP Connection and Transfer of Clock BOF <tictoc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tictoc>, <mailto:tictoc-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tictoc>
List-Post: <mailto:tictoc@ietf.org>
List-Help: <mailto:tictoc-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tictoc>, <mailto:tictoc-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 04 Jul 2011 13:08:36 -0000

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

	Title           : Precision Time Protocol Version 2 (PTPv2) Management Inf=
ormation Base
	Author(s)       : Vinay Shankarkumar
                          Laurent Montini
                          Tim Frost
                          Greg Dowd
	Filename        : draft-ietf-tictoc-ptp-mib-00.txt
	Pages           : 67
	Date            : 2011-07-04

   This memo defines a portion of the Management Information Base (MIB)
   for use with network management protocols in TCP/IP-based internets.
   In particular, it defines objects for managing networks using
   Precision Time Protocol.

   This memo specifies a MIB module in a manner that is both compliant
   to the SNMPv2 SMI, and semantically identical to the peer SNMPv1
   definitions.


A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-tictoc-ptp-mib-00.txt

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

This Internet-Draft can be retrieved at:
ftp://ftp.ietf.org/internet-drafts/draft-ietf-tictoc-ptp-mib-00.txt

From btv1==17333bec5a8==GDowd@symmetricom.com  Mon Jul 11 08:29:18 2011
Return-Path: <btv1==17333bec5a8==GDowd@symmetricom.com>
X-Original-To: tictoc@ietfa.amsl.com
Delivered-To: tictoc@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 817D121F8D7D for <tictoc@ietfa.amsl.com>; Mon, 11 Jul 2011 08:29:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.264
X-Spam-Level: 
X-Spam-Status: No, score=-2.264 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, IP_NOT_FRIENDLY=0.334]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 84RYuYQzL0q1 for <tictoc@ietfa.amsl.com>; Mon, 11 Jul 2011 08:29:09 -0700 (PDT)
Received: from mail5.symmetricom.com (mail5.symmetricom.com [69.25.98.10]) by ietfa.amsl.com (Postfix) with ESMTP id DEA7621F8D74 for <tictoc@ietf.org>; Mon, 11 Jul 2011 08:29:09 -0700 (PDT)
X-ASG-Debug-ID: 1310398148-11aa0d2b0001-4wH9i1
Received: from SJC-HUB-01.symmetricom.com ([192.168.10.171]) by mail5.symmetricom.com with ESMTP id MjO2N40uRW4W6kbq; Mon, 11 Jul 2011 08:29:08 -0700 (PDT)
X-Barracuda-Envelope-From: GDowd@symmetricom.com
Received: from SJC-MBX-01.symmetricom.com ([169.254.1.52]) by SJC-HUB-01.symmetricom.com ([::1]) with mapi id 14.01.0289.001; Mon, 11 Jul 2011 08:29:08 -0700
From: Greg Dowd <GDowd@symmetricom.com>
To: Tal Mizrahi <talmi@marvell.com>, "tictoc@ietf.org" <tictoc@ietf.org>, "ntpwg@lists.ntp.org" <ntpwg@lists.ntp.org>
Thread-Topic: [TICTOC] [ntpwg] New draft: draft-mizrahi-tictoc-checksum-trailer-00
X-ASG-Orig-Subj: RE: [TICTOC] [ntpwg] New draft: draft-mizrahi-tictoc-checksum-trailer-00
Thread-Index: Acw6QVZgcbH3mJzTRZOF+kYbuNTxSAFnDh3Q
Date: Mon, 11 Jul 2011 15:29:08 +0000
Message-ID: <26FBD265CD8D234EAF41115A180F92BB38AE2BBC@SJC-MBX-01.symmetricom.com>
References: <74470498B659FA4687F0B0018C19A89C01223E573C5A@IL-MB01.marvell.com>
In-Reply-To: <74470498B659FA4687F0B0018C19A89C01223E573C5A@IL-MB01.marvell.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [192.168.3.18]
Content-Type: multipart/alternative; boundary="_000_26FBD265CD8D234EAF41115A180F92BB38AE2BBCSJCMBX01symmetr_"
MIME-Version: 1.0
X-Barracuda-Connect: UNKNOWN[192.168.10.171]
X-Barracuda-Start-Time: 1310398148
X-Barracuda-URL: http://192.168.10.96:80/cgi-mod/mark.cgi
X-Virus-Scanned: by bsmtpd at symmetricom.com
X-Barracuda-Spam-Score: -1002.00
X-Barracuda-Spam-Status: No, SCORE=-1002.00 using global scores of TAG_LEVEL=1000.0 QUARANTINE_LEVEL=1000.0 KILL_LEVEL=1000.0 
Subject: Re: [TICTOC] [ntpwg] New draft: draft-mizrahi-tictoc-checksum-trailer-00
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, 11 Jul 2011 15:29:52 -0000

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

Is the use model you envision for NTP to support hardware timestamping at t=
he edge?  In NTP, the addition of an extension field requires the presence =
of the MAC.  This requires the dissemination and maintenance of keys as wel=
l as the defined MAC checking.  How would this model work if the NTP packet=
 did  have the MAC?  This extension field would be covered by the MAC and t=
he authenticator would fail.  Or do you expect this block would have the ke=
y info and update the MAC as well?  And, how would it work if the MAC isn't=
 there.  Would the update not be used?

In PTP, there is a TC protocol function which necessitates the modification=
 of the packet.  In NTP, as it is defined as a UDP protocol, there is not a=
s clear a path to how lower stack layers modify the PDUs.

If you define this simply at the edge, I'm not sure how much value this add=
itional UDP checksum update adds?  Is there a model you have in mind?




From: tictoc-bounces@ietf.org [mailto:tictoc-bounces@ietf.org] On Behalf Of=
 Tal Mizrahi
Sent: Monday, July 04, 2011 5:01 AM
To: tictoc@ietf.org; ntpwg@lists.ntp.org
Subject: [TICTOC] [ntpwg] New draft: draft-mizrahi-tictoc-checksum-trailer-=
00

Hi,

I have posted a new draft that discusses Checksum updates in time synchroni=
zation protocols.
http://tools.ietf.org/html/draft-mizrahi-tictoc-checksum-trailer-00
Comments will be welcome.

Thanks.
Tal.

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

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
<meta name=3D"Generator" content=3D"Microsoft Word 12 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
span.EmailStyle17
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
span.EmailStyle18
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.25in 1.0in 1.25in;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=3D"EN-US" link=3D"blue" vlink=3D"purple">
<div class=3D"WordSection1">
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">Is the use model you e=
nvision for NTP to support hardware timestamping at the edge?&nbsp; In NTP,=
 the addition of an extension field requires the presence of the MAC.&nbsp;=
 This requires the dissemination and maintenance
 of keys as well as the defined MAC checking.&nbsp; How would this model wo=
rk if the NTP packet did &nbsp;have the MAC?&nbsp; This extension field wou=
ld be covered by the MAC and the authenticator would fail.&nbsp; Or do you =
expect this block would have the key info and update
 the MAC as well?&nbsp; And, how would it work if the MAC isn&#8217;t there=
.&nbsp; Would the update not be used?<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">In PTP, there is a TC =
protocol function which necessitates the modification of the packet.&nbsp; =
In NTP, as it is defined as a UDP protocol, there is not as clear a path to=
 how lower stack layers modify the PDUs.
<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">If you define this sim=
ply at the edge, I&#8217;m not sure how much value this additional UDP chec=
ksum update adds?&nbsp; Is there a model you have in mind?<o:p></o:p></span=
></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<div>
<div style=3D"border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in =
0in 0in">
<p class=3D"MsoNormal"><b><span style=3D"font-size:10.0pt;font-family:&quot=
;Tahoma&quot;,&quot;sans-serif&quot;">From:</span></b><span style=3D"font-s=
ize:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;"> tictoc-b=
ounces@ietf.org [mailto:tictoc-bounces@ietf.org]
<b>On Behalf Of </b>Tal Mizrahi<br>
<b>Sent:</b> Monday, July 04, 2011 5:01 AM<br>
<b>To:</b> tictoc@ietf.org; ntpwg@lists.ntp.org<br>
<b>Subject:</b> [TICTOC] [ntpwg] New draft: draft-mizrahi-tictoc-checksum-t=
railer-00<o:p></o:p></span></p>
</div>
</div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Hi,<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">I have posted a new draft that discusses Checksum up=
dates in time synchronization protocols.<o:p></o:p></p>
<p class=3D"MsoNormal"><a href=3D"http://tools.ietf.org/html/draft-mizrahi-=
tictoc-checksum-trailer-00">http://tools.ietf.org/html/draft-mizrahi-tictoc=
-checksum-trailer-00</a><o:p></o:p></p>
<p class=3D"MsoNormal">Comments will be welcome.<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Thanks.<o:p></o:p></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Ar=
ial&quot;,&quot;sans-serif&quot;">Tal.</span><o:p></o:p></p>
</div>
</body>
</html>

--_000_26FBD265CD8D234EAF41115A180F92BB38AE2BBCSJCMBX01symmetr_--

From talmi@marvell.com  Tue Jul 12 07:44:14 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 3E45321F8C72 for <tictoc@ietfa.amsl.com>; Tue, 12 Jul 2011 07:44:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.683
X-Spam-Level: 
X-Spam-Status: No, score=-3.683 tagged_above=-999 required=5 tests=[AWL=-1.085, 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 SkErjVooJtjN for <tictoc@ietfa.amsl.com>; Tue, 12 Jul 2011 07:44:12 -0700 (PDT)
Received: from galiil.marvell.com (galiil.marvell.com [199.203.130.254]) by ietfa.amsl.com (Postfix) with ESMTP id BB04721F8C70 for <tictoc@ietf.org>; Tue, 12 Jul 2011 07:44:10 -0700 (PDT)
From: Tal Mizrahi <talmi@marvell.com>
To: Greg Dowd <GDowd@symmetricom.com>, "tictoc@ietf.org" <tictoc@ietf.org>, "ntpwg@lists.ntp.org" <ntpwg@lists.ntp.org>
Date: Tue, 12 Jul 2011 17:44:02 +0300
Thread-Topic: [TICTOC] [ntpwg] New draft: draft-mizrahi-tictoc-checksum-trailer-00
Thread-Index: Acw6QVZgcbH3mJzTRZOF+kYbuNTxSAFnDh3QAC/MAoA=
Message-ID: <74470498B659FA4687F0B0018C19A89C01223E5F470F@IL-MB01.marvell.com>
References: <74470498B659FA4687F0B0018C19A89C01223E573C5A@IL-MB01.marvell.com> <26FBD265CD8D234EAF41115A180F92BB38AE2BBC@SJC-MBX-01.symmetricom.com>
In-Reply-To: <26FBD265CD8D234EAF41115A180F92BB38AE2BBC@SJC-MBX-01.symmetricom.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_74470498B659FA4687F0B0018C19A89C01223E5F470FILMB01marve_"
MIME-Version: 1.0
Subject: Re: [TICTOC] [ntpwg] New draft: draft-mizrahi-tictoc-checksum-trailer-00
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, 12 Jul 2011 14:44:14 -0000

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

Hi Greg,

Thanks for your feedback.

> In NTP, the addition of an extension field requires the presence of the M=
AC.
[TM] According to RFC5905 "The extension fields are used to add optional ca=
pabilities, for example, the Autokey security protocol". So indeed, the onl=
y extension field currently defined is for security purposes, but the curre=
nt draft proposes to use a newly defined extension field, independent of th=
e MAC usage.

> How would this model work if the NTP packet did  have the MAC?
[TM] The current draft is more useful for cases where the MAC is not used, =
since this draft is about simplifying the implementation of intermediate no=
des. When the MAC is used, it would mean that the intermediate node would h=
ave to compute the MAC, and only then to perform the Checksum update.

> If you define this simply at the edge, I'm not sure how much value this a=
dditional UDP checksum update adds?  Is there a model you have in mind?
[TM] The idea is that the intermediate node (an ASIC/FPGA) assigns the pack=
et's timestamp field, significantly improving the accuracy. The benefit of =
this improvement is negligible if the path between the NTP nodes consists o=
f a large number of hops, BUT when there is a small number of hops this imp=
rovement is significant. An example use-case I have in mind is in the wirel=
ess backhaul, where the RBS and RNC synchronize over a CES, either using PT=
P or NTP. When NTP is used in this case, high precision is required, and ca=
n benefit from timestamping at the intermediate node.

Regards,
Tal.

From: Greg Dowd [mailto:GDowd@symmetricom.com]
Sent: Monday, July 11, 2011 6:29 PM
To: Tal Mizrahi; tictoc@ietf.org; ntpwg@lists.ntp.org
Subject: RE: [TICTOC] [ntpwg] New draft: draft-mizrahi-tictoc-checksum-trai=
ler-00

Is the use model you envision for NTP to support hardware timestamping at t=
he edge?  In NTP, the addition of an extension field requires the presence =
of the MAC.  This requires the dissemination and maintenance of keys as wel=
l as the defined MAC checking.  How would this model work if the NTP packet=
 did  have the MAC?  This extension field would be covered by the MAC and t=
he authenticator would fail.  Or do you expect this block would have the ke=
y info and update the MAC as well?  And, how would it work if the MAC isn't=
 there.  Would the update not be used?

In PTP, there is a TC protocol function which necessitates the modification=
 of the packet.  In NTP, as it is defined as a UDP protocol, there is not a=
s clear a path to how lower stack layers modify the PDUs.

If you define this simply at the edge, I'm not sure how much value this add=
itional UDP checksum update adds?  Is there a model you have in mind?




From: tictoc-bounces@ietf.org [mailto:tictoc-bounces@ietf.org] On Behalf Of=
 Tal Mizrahi
Sent: Monday, July 04, 2011 5:01 AM
To: tictoc@ietf.org; ntpwg@lists.ntp.org
Subject: [TICTOC] [ntpwg] New draft: draft-mizrahi-tictoc-checksum-trailer-=
00

Hi,

I have posted a new draft that discusses Checksum updates in time synchroni=
zation protocols.
http://tools.ietf.org/html/draft-mizrahi-tictoc-checksum-trailer-00
Comments will be welcome.

Thanks.
Tal.

--_000_74470498B659FA4687F0B0018C19A89C01223E5F470FILMB01marve_
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:11.0pt;
	font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
	{mso-style-priority:99;
	mso-style-link:"Balloon Text Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:8.0pt;
	font-family:"Tahoma","sans-serif";}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
	{mso-style-priority:34;
	margin-top:0in;
	margin-right:0in;
	margin-bottom:0in;
	margin-left:.5in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
span.EmailStyle17
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
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'c=
olor:#1F497D'>Hi Greg,<o:p></o:p></span></p><p class=3DMsoNormal><span styl=
e=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
style=3D'color:#1F497D'>Thanks for your feedback.<o:p></o:p></span></p><p c=
lass=3DMsoNormal><span style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p>=
<p class=3DMsoNormal><span style=3D'color:#1F497D'>&gt;</span><span style=
=3D'color:#1F497D'> In NTP, the addition of an extension field requires the=
 presence of the MAC.<o:p></o:p></span></p><p class=3DMsoNormal><span style=
=3D'color:#1F497D'>[TM] </span><span style=3D'color:#1F497D'>According to R=
FC5905 &#8220;The extension fields are used to add optional capabilities, f=
or example, the Autokey security protocol&#8221;. So indeed, the only exten=
sion field currently defined is for security purposes, but the current draf=
t proposes to use a newly defined extension field, independent of the MAC u=
sage.<o:p></o:p></span></p><p class=3DMsoNormal><span style=3D'color:#1F497=
D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span style=3D'color:#1=
F497D'>&gt;</span><span style=3D'color:#1F497D'> How would this model work =
if the NTP packet did &nbsp;have the MAC?&nbsp;<o:p></o:p></span></p><p cla=
ss=3DMsoNormal><span style=3D'color:#1F497D'>[TM] The current draft is more=
 useful for cases where the MAC is not used, since this draft is about simp=
lifying the implementation of intermediate nodes. When the MAC is used, it =
would mean that the intermediate node would have to compute the MAC, and on=
ly then to perform the Checksum update.<o:p></o:p></span></p><p class=3DMso=
Normal><span style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><p class=
=3DMsoNormal><span style=3D'color:#1F497D'>&gt; </span><span style=3D'color=
:#1F497D'>If you define this simply at the edge, I&#8217;m not sure how muc=
h value this additional UDP checksum update adds?&nbsp; Is there a model yo=
u have in mind?<o:p></o:p></span></p><p class=3DMsoNormal><span style=3D'co=
lor:#1F497D'>[TM] The idea is that the intermediate node (an ASIC/FPGA) ass=
igns the packet&#8217;s timestamp field, significantly improving the accura=
cy. The benefit of this improvement is negligible if the path between the N=
TP nodes consists of a large number of hops, BUT when there is a small numb=
er of hops this improvement is significant. An example use-case I have in m=
ind is in the wireless backhaul, where the RBS and RNC synchronize over a C=
ES, either using PTP or NTP. When NTP is used in this case, high precision =
is required, and can benefit from timestamping at the intermediate node.</s=
pan><span style=3D'color:#1F497D'><o:p></o:p></span></p><p class=3DMsoNorma=
l><span style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoN=
ormal><span style=3D'color:#1F497D'>Regards,<o:p></o:p></span></p><p class=
=3DMsoNormal><span style=3D'font-size:10.0pt;font-family:"Arial","sans-seri=
f";color:#1F497D'>Tal.<o:p></o:p></span></p><p class=3DMsoNormal><span styl=
e=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><div><div style=3D'border:n=
one;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in'><p class=3DMs=
oNormal><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","sa=
ns-serif"'> Greg Dowd [mailto:GDowd@symmetricom.com] <br><b>Sent:</b> Monda=
y, July 11, 2011 6:29 PM<br><b>To:</b> Tal Mizrahi; tictoc@ietf.org; ntpwg@=
lists.ntp.org<br><b>Subject:</b> RE: [TICTOC] [ntpwg] New draft: draft-mizr=
ahi-tictoc-checksum-trailer-00<o:p></o:p></span></p></div></div><p class=3D=
MsoNormal><o:p>&nbsp;</o:p></p><p class=3DMsoNormal><span style=3D'color:#1=
F497D'>Is the use model you envision for NTP to support hardware timestampi=
ng at the edge?&nbsp; In NTP, the addition of an extension field requires t=
he presence of the MAC.&nbsp; This requires the dissemination and maintenan=
ce of keys as well as the defined MAC checking.&nbsp; How would this model =
work if the NTP packet did &nbsp;have the MAC?&nbsp; This extension field w=
ould be covered by the MAC and the authenticator would fail.&nbsp; Or do yo=
u expect this block would have the key info and update the MAC as well?&nbs=
p; And, how would it work if the MAC isn&#8217;t there.&nbsp; Would the upd=
ate not be used?<o:p></o:p></span></p><p class=3DMsoNormal><span style=3D'c=
olor:#1F497D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span style=
=3D'color:#1F497D'>In PTP, there is a TC protocol function which necessitat=
es the modification of the packet.&nbsp; In NTP, as it is defined as a UDP =
protocol, there is not as clear a path to how lower stack layers modify the=
 PDUs. <o:p></o:p></span></p><p class=3DMsoNormal><span style=3D'color:#1F4=
97D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span style=3D'color:=
#1F497D'>If you define this simply at the edge, I&#8217;m not sure how much=
 value this additional UDP checksum update adds?&nbsp; Is there a model you=
 have in mind?<o:p></o:p></span></p><p class=3DMsoNormal><span style=3D'col=
or:#1F497D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span style=3D=
'color:#1F497D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span styl=
e=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><div><div style=3D'bord=
er: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>Tal Mizrahi<br><b>Sent:</b> Monday, July 04, 2011 5:01 A=
M<br><b>To:</b> tictoc@ietf.org; ntpwg@lists.ntp.org<br><b>Subject:</b> [TI=
CTOC] [ntpwg] New draft: draft-mizrahi-tictoc-checksum-trailer-00<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>I have posted a new draft that discusses Checksum update=
s in time synchronization protocols.<o:p></o:p></p><p class=3DMsoNormal><a =
href=3D"http://tools.ietf.org/html/draft-mizrahi-tictoc-checksum-trailer-00=
">http://tools.ietf.org/html/draft-mizrahi-tictoc-checksum-trailer-00</a><o=
:p></o:p></p><p class=3DMsoNormal>Comments will be welcome.<o:p></o:p></p><=
p class=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3DMsoNormal>Thanks.<o:p><=
/o:p></p><p class=3DMsoNormal><span style=3D'font-size:10.0pt;font-family:"=
Arial","sans-serif"'>Tal.</span><o:p></o:p></p></div></body></html>=

--_000_74470498B659FA4687F0B0018C19A89C01223E5F470FILMB01marve_--

From btv1==1743a3f939d==GDowd@symmetricom.com  Tue Jul 12 09:51:25 2011
Return-Path: <btv1==1743a3f939d==GDowd@symmetricom.com>
X-Original-To: tictoc@ietfa.amsl.com
Delivered-To: tictoc@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DC69E21F8E48 for <tictoc@ietfa.amsl.com>; Tue, 12 Jul 2011 09:51:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.926
X-Spam-Level: 
X-Spam-Status: No, score=-2.926 tagged_above=-999 required=5 tests=[AWL=-0.662, BAYES_00=-2.599, HTML_MESSAGE=0.001, IP_NOT_FRIENDLY=0.334]
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 e5ldXVrDu5s8 for <tictoc@ietfa.amsl.com>; Tue, 12 Jul 2011 09:51:20 -0700 (PDT)
Received: from mail5.symmetricom.com (mail5.symmetricom.com [69.25.98.10]) by ietfa.amsl.com (Postfix) with ESMTP id B00A021F8E42 for <tictoc@ietf.org>; Tue, 12 Jul 2011 09:51:20 -0700 (PDT)
X-ASG-Debug-ID: 1310489479-11aa29700001-4wH9i1
Received: from SJC-HUB-01.symmetricom.com ([192.168.10.171]) by mail5.symmetricom.com with ESMTP id YLpjE2QpzMr7Xa9d; Tue, 12 Jul 2011 09:51:19 -0700 (PDT)
X-Barracuda-Envelope-From: GDowd@symmetricom.com
Received: from SJC-MBX-01.symmetricom.com ([169.254.1.52]) by SJC-HUB-01.symmetricom.com ([::1]) with mapi id 14.01.0289.001; Tue, 12 Jul 2011 09:51:19 -0700
From: Greg Dowd <GDowd@symmetricom.com>
To: Tal Mizrahi <talmi@marvell.com>, "tictoc@ietf.org" <tictoc@ietf.org>, "ntpwg@lists.ntp.org" <ntpwg@lists.ntp.org>
Thread-Topic: [TICTOC] [ntpwg] New draft: draft-mizrahi-tictoc-checksum-trailer-00
X-ASG-Orig-Subj: RE: [TICTOC] [ntpwg] New draft: draft-mizrahi-tictoc-checksum-trailer-00
Thread-Index: Acw6QVZgcbH3mJzTRZOF+kYbuNTxSAFnDh3QAC/MAoAABZq3IA==
Date: Tue, 12 Jul 2011 16:51:19 +0000
Message-ID: <26FBD265CD8D234EAF41115A180F92BB38AE37CD@SJC-MBX-01.symmetricom.com>
References: <74470498B659FA4687F0B0018C19A89C01223E573C5A@IL-MB01.marvell.com> <26FBD265CD8D234EAF41115A180F92BB38AE2BBC@SJC-MBX-01.symmetricom.com> <74470498B659FA4687F0B0018C19A89C01223E5F470F@IL-MB01.marvell.com>
In-Reply-To: <74470498B659FA4687F0B0018C19A89C01223E5F470F@IL-MB01.marvell.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [192.168.3.18]
Content-Type: multipart/alternative; boundary="_000_26FBD265CD8D234EAF41115A180F92BB38AE37CDSJCMBX01symmetr_"
MIME-Version: 1.0
X-Barracuda-Connect: UNKNOWN[192.168.10.171]
X-Barracuda-Start-Time: 1310489479
X-Barracuda-URL: http://192.168.10.96:80/cgi-mod/mark.cgi
X-Virus-Scanned: by bsmtpd at symmetricom.com
X-Barracuda-Spam-Score: -1002.00
X-Barracuda-Spam-Status: No, SCORE=-1002.00 using global scores of TAG_LEVEL=1000.0 QUARANTINE_LEVEL=1000.0 KILL_LEVEL=1000.0 
Subject: Re: [TICTOC] [ntpwg] New draft: draft-mizrahi-tictoc-checksum-trailer-00
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, 12 Jul 2011 16:52:17 -0000

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

Hi Tal,
                The MAC is a necessary component in the current protocol wh=
en extensions are present.  The parsing of incoming packets uses frame size=
 as mechanism for determining the code path to take in addition to its obvi=
ous utility value in autokey.  The relevant section in 5905 is the first se=
ntence in the NTP Extension Field Format section 7.5.
In NTPv4, one or more extension fields can be inserted after the
   header and before the MAC, which is always present when an extension
   field is present.


From: Tal Mizrahi [mailto:talmi@marvell.com]
Sent: Tuesday, July 12, 2011 7:44 AM
To: Greg Dowd; tictoc@ietf.org; ntpwg@lists.ntp.org
Subject: RE: [TICTOC] [ntpwg] New draft: draft-mizrahi-tictoc-checksum-trai=
ler-00

Hi Greg,

Thanks for your feedback.

> In NTP, the addition of an extension field requires the presence of the M=
AC.
[TM] According to RFC5905 "The extension fields are used to add optional ca=
pabilities, for example, the Autokey security protocol". So indeed, the onl=
y extension field currently defined is for security purposes, but the curre=
nt draft proposes to use a newly defined extension field, independent of th=
e MAC usage.

> How would this model work if the NTP packet did  have the MAC?
[TM] The current draft is more useful for cases where the MAC is not used, =
since this draft is about simplifying the implementation of intermediate no=
des. When the MAC is used, it would mean that the intermediate node would h=
ave to compute the MAC, and only then to perform the Checksum update.

> If you define this simply at the edge, I'm not sure how much value this a=
dditional UDP checksum update adds?  Is there a model you have in mind?
[TM] The idea is that the intermediate node (an ASIC/FPGA) assigns the pack=
et's timestamp field, significantly improving the accuracy. The benefit of =
this improvement is negligible if the path between the NTP nodes consists o=
f a large number of hops, BUT when there is a small number of hops this imp=
rovement is significant. An example use-case I have in mind is in the wirel=
ess backhaul, where the RBS and RNC synchronize over a CES, either using PT=
P or NTP. When NTP is used in this case, high precision is required, and ca=
n benefit from timestamping at the intermediate node.

Regards,
Tal.

From: Greg Dowd [mailto:GDowd@symmetricom.com]
Sent: Monday, July 11, 2011 6:29 PM
To: Tal Mizrahi; tictoc@ietf.org; ntpwg@lists.ntp.org
Subject: RE: [TICTOC] [ntpwg] New draft: draft-mizrahi-tictoc-checksum-trai=
ler-00

Is the use model you envision for NTP to support hardware timestamping at t=
he edge?  In NTP, the addition of an extension field requires the presence =
of the MAC.  This requires the dissemination and maintenance of keys as wel=
l as the defined MAC checking.  How would this model work if the NTP packet=
 did  have the MAC?  This extension field would be covered by the MAC and t=
he authenticator would fail.  Or do you expect this block would have the ke=
y info and update the MAC as well?  And, how would it work if the MAC isn't=
 there.  Would the update not be used?

In PTP, there is a TC protocol function which necessitates the modification=
 of the packet.  In NTP, as it is defined as a UDP protocol, there is not a=
s clear a path to how lower stack layers modify the PDUs.

If you define this simply at the edge, I'm not sure how much value this add=
itional UDP checksum update adds?  Is there a model you have in mind?




From: tictoc-bounces@ietf.org [mailto:tictoc-bounces@ietf.org] On Behalf Of=
 Tal Mizrahi
Sent: Monday, July 04, 2011 5:01 AM
To: tictoc@ietf.org; ntpwg@lists.ntp.org
Subject: [TICTOC] [ntpwg] New draft: draft-mizrahi-tictoc-checksum-trailer-=
00

Hi,

I have posted a new draft that discusses Checksum updates in time synchroni=
zation protocols.
http://tools.ietf.org/html/draft-mizrahi-tictoc-checksum-trailer-00
Comments will be welcome.

Thanks.
Tal.

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

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:x=3D"urn:schemas-microsoft-com:office:excel" xmlns:p=3D"urn:schemas-m=
icrosoft-com:office:powerpoint" xmlns:a=3D"urn:schemas-microsoft-com:office=
:access" xmlns:dt=3D"uuid:C2F41010-65B3-11d1-A29F-00AA00C14882" xmlns:s=3D"=
uuid:BDC6E3F0-6DA3-11d1-A2A3-00AA00C14882" xmlns:rs=3D"urn:schemas-microsof=
t-com:rowset" xmlns:z=3D"#RowsetSchema" xmlns:b=3D"urn:schemas-microsoft-co=
m:office:publisher" xmlns:ss=3D"urn:schemas-microsoft-com:office:spreadshee=
t" xmlns:c=3D"urn:schemas-microsoft-com:office:component:spreadsheet" xmlns=
:odc=3D"urn:schemas-microsoft-com:office:odc" xmlns:oa=3D"urn:schemas-micro=
soft-com:office:activation" xmlns:html=3D"http://www.w3.org/TR/REC-html40" =
xmlns:q=3D"http://schemas.xmlsoap.org/soap/envelope/" xmlns:rtc=3D"http://m=
icrosoft.com/officenet/conferencing" xmlns:D=3D"DAV:" xmlns:Repl=3D"http://=
schemas.microsoft.com/repl/" xmlns:mt=3D"http://schemas.microsoft.com/share=
point/soap/meetings/" xmlns:x2=3D"http://schemas.microsoft.com/office/excel=
/2003/xml" xmlns:ppda=3D"http://www.passport.com/NameSpace.xsd" xmlns:ois=
=3D"http://schemas.microsoft.com/sharepoint/soap/ois/" xmlns:dir=3D"http://=
schemas.microsoft.com/sharepoint/soap/directory/" xmlns:ds=3D"http://www.w3=
.org/2000/09/xmldsig#" xmlns:dsp=3D"http://schemas.microsoft.com/sharepoint=
/dsp" xmlns:udc=3D"http://schemas.microsoft.com/data/udc" xmlns:xsd=3D"http=
://www.w3.org/2001/XMLSchema" xmlns:sub=3D"http://schemas.microsoft.com/sha=
repoint/soap/2002/1/alerts/" xmlns:ec=3D"http://www.w3.org/2001/04/xmlenc#"=
 xmlns:sp=3D"http://schemas.microsoft.com/sharepoint/" xmlns:sps=3D"http://=
schemas.microsoft.com/sharepoint/soap/" xmlns:xsi=3D"http://www.w3.org/2001=
/XMLSchema-instance" xmlns:udcs=3D"http://schemas.microsoft.com/data/udc/so=
ap" xmlns:udcxf=3D"http://schemas.microsoft.com/data/udc/xmlfile" xmlns:udc=
p2p=3D"http://schemas.microsoft.com/data/udc/parttopart" xmlns:wf=3D"http:/=
/schemas.microsoft.com/sharepoint/soap/workflow/" xmlns:dsss=3D"http://sche=
mas.microsoft.com/office/2006/digsig-setup" xmlns:dssi=3D"http://schemas.mi=
crosoft.com/office/2006/digsig" xmlns:mdssi=3D"http://schemas.openxmlformat=
s.org/package/2006/digital-signature" xmlns:mver=3D"http://schemas.openxmlf=
ormats.org/markup-compatibility/2006" xmlns:m=3D"http://schemas.microsoft.c=
om/office/2004/12/omml" xmlns:mrels=3D"http://schemas.openxmlformats.org/pa=
ckage/2006/relationships" xmlns:spwp=3D"http://microsoft.com/sharepoint/web=
partpages" xmlns:ex12t=3D"http://schemas.microsoft.com/exchange/services/20=
06/types" xmlns:ex12m=3D"http://schemas.microsoft.com/exchange/services/200=
6/messages" xmlns:pptsl=3D"http://schemas.microsoft.com/sharepoint/soap/Sli=
deLibrary/" xmlns:spsl=3D"http://microsoft.com/webservices/SharePointPortal=
Server/PublishedLinksService" xmlns:Z=3D"urn:schemas-microsoft-com:" xmlns:=
st=3D"&#1;" xmlns=3D"http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
<meta name=3D"Generator" content=3D"Microsoft Word 12 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
pre
	{mso-style-priority:99;
	mso-style-link:"HTML Preformatted Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:10.0pt;
	font-family:"Courier New";}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
	{mso-style-priority:99;
	mso-style-link:"Balloon Text Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:8.0pt;
	font-family:"Tahoma","sans-serif";}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
	{mso-style-priority:34;
	margin-top:0in;
	margin-right:0in;
	margin-bottom:0in;
	margin-left:.5in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","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.EmailStyle20
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
span.EmailStyle21
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
span.EmailStyle22
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
span.EmailStyle23
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
span.HTMLPreformattedChar
	{mso-style-name:"HTML Preformatted Char";
	mso-style-priority:99;
	mso-style-link:"HTML Preformatted";
	font-family:"Courier New";}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.25in 1.0in 1.25in;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=3D"EN-US" link=3D"blue" vlink=3D"purple">
<div class=3D"WordSection1">
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">Hi Tal,<o:p></o:p></sp=
an></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; The MA=
C is a necessary component in the current protocol when extensions are pres=
ent.&nbsp; The parsing of incoming packets uses frame size as mechanism for=
 determining the code path to take in addition
 to its obvious utility value in autokey.&nbsp; The relevant section in 590=
5 is the first sentence in the NTP Extension Field Format section 7.5.<o:p>=
</o:p></span></p>
<p class=3D"MsoNormal" style=3D"page-break-before:always"><span style=3D"fo=
nt-size:12.0pt;font-family:&quot;Courier New&quot;;color:black">In NTPv4, o=
ne or more extension fields can be inserted after the<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"page-break-before:always"><span style=3D"fo=
nt-size:12.0pt;font-family:&quot;Courier New&quot;;color:black">&nbsp;&nbsp=
; header and before the MAC, which is always present when an extension<o:p>=
</o:p></span></p>
<p class=3D"MsoNormal" style=3D"page-break-before:always"><span style=3D"fo=
nt-size:12.0pt;font-family:&quot;Courier New&quot;;color:black">&nbsp;&nbsp=
; field is present.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<div>
<div style=3D"border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in =
0in 0in">
<p class=3D"MsoNormal"><b><span style=3D"font-size:10.0pt;font-family:&quot=
;Tahoma&quot;,&quot;sans-serif&quot;">From:</span></b><span style=3D"font-s=
ize:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;"> Tal Mizr=
ahi [mailto:talmi@marvell.com]
<br>
<b>Sent:</b> Tuesday, July 12, 2011 7:44 AM<br>
<b>To:</b> Greg Dowd; tictoc@ietf.org; ntpwg@lists.ntp.org<br>
<b>Subject:</b> RE: [TICTOC] [ntpwg] New draft: draft-mizrahi-tictoc-checks=
um-trailer-00<o:p></o:p></span></p>
</div>
</div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">Hi Greg,<o:p></o:p></s=
pan></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">Thanks for your feedba=
ck.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">&gt; In NTP, the addit=
ion of an extension field requires the presence of the MAC.<o:p></o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">[TM] According to RFC5=
905 &#8220;The extension fields are used to add optional capabilities, for =
example, the Autokey security protocol&#8221;. So indeed, the only extensio=
n field currently defined is for security purposes,
 but the current draft proposes to use a newly defined extension field, ind=
ependent of the MAC usage.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">&gt; How would this mo=
del work if the NTP packet did &nbsp;have the MAC?&nbsp;<o:p></o:p></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">[TM] The current draft=
 is more useful for cases where the MAC is not used, since this draft is ab=
out simplifying the implementation of intermediate nodes. When the MAC is u=
sed, it would mean that the intermediate
 node would have to compute the MAC, and only then to perform the Checksum =
update.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">&gt; If you define thi=
s simply at the edge, I&#8217;m not sure how much value this additional UDP=
 checksum update adds?&nbsp; Is there a model you have in mind?<o:p></o:p><=
/span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">[TM] The idea is that =
the intermediate node (an ASIC/FPGA) assigns the packet&#8217;s timestamp f=
ield, significantly improving the accuracy. The benefit of this improvement=
 is negligible if the path between the NTP
 nodes consists of a large number of hops, BUT when there is a small number=
 of hops this improvement is significant. An example use-case I have in min=
d is in the wireless backhaul, where the RBS and RNC synchronize over a CES=
, either using PTP or NTP. When
 NTP is used in this case, high precision is required, and can benefit from=
 timestamping at the intermediate node.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">Regards,<o:p></o:p></s=
pan></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Ar=
ial&quot;,&quot;sans-serif&quot;;color:#1F497D">Tal.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<div>
<div style=3D"border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in =
0in 0in">
<p class=3D"MsoNormal"><b><span style=3D"font-size:10.0pt;font-family:&quot=
;Tahoma&quot;,&quot;sans-serif&quot;">From:</span></b><span style=3D"font-s=
ize:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;"> Greg Dow=
d [mailto:GDowd@symmetricom.com]
<br>
<b>Sent:</b> Monday, July 11, 2011 6:29 PM<br>
<b>To:</b> Tal Mizrahi; tictoc@ietf.org; ntpwg@lists.ntp.org<br>
<b>Subject:</b> RE: [TICTOC] [ntpwg] New draft: draft-mizrahi-tictoc-checks=
um-trailer-00<o:p></o:p></span></p>
</div>
</div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">Is the use model you e=
nvision for NTP to support hardware timestamping at the edge?&nbsp; In NTP,=
 the addition of an extension field requires the presence of the MAC.&nbsp;=
 This requires the dissemination and maintenance
 of keys as well as the defined MAC checking.&nbsp; How would this model wo=
rk if the NTP packet did &nbsp;have the MAC?&nbsp; This extension field wou=
ld be covered by the MAC and the authenticator would fail.&nbsp; Or do you =
expect this block would have the key info and update
 the MAC as well?&nbsp; And, how would it work if the MAC isn&#8217;t there=
.&nbsp; Would the update not be used?<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">In PTP, there is a TC =
protocol function which necessitates the modification of the packet.&nbsp; =
In NTP, as it is defined as a UDP protocol, there is not as clear a path to=
 how lower stack layers modify the PDUs.
<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">If you define this sim=
ply at the edge, I&#8217;m not sure how much value this additional UDP chec=
ksum update adds?&nbsp; Is there a model you have in mind?<o:p></o:p></span=
></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<div>
<div style=3D"border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in =
0in 0in">
<p class=3D"MsoNormal"><b><span style=3D"font-size:10.0pt;font-family:&quot=
;Tahoma&quot;,&quot;sans-serif&quot;">From:</span></b><span style=3D"font-s=
ize:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;"> tictoc-b=
ounces@ietf.org [mailto:tictoc-bounces@ietf.org]
<b>On Behalf Of </b>Tal Mizrahi<br>
<b>Sent:</b> Monday, July 04, 2011 5:01 AM<br>
<b>To:</b> tictoc@ietf.org; ntpwg@lists.ntp.org<br>
<b>Subject:</b> [TICTOC] [ntpwg] New draft: draft-mizrahi-tictoc-checksum-t=
railer-00<o:p></o:p></span></p>
</div>
</div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Hi,<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">I have posted a new draft that discusses Checksum up=
dates in time synchronization protocols.<o:p></o:p></p>
<p class=3D"MsoNormal"><a href=3D"http://tools.ietf.org/html/draft-mizrahi-=
tictoc-checksum-trailer-00">http://tools.ietf.org/html/draft-mizrahi-tictoc=
-checksum-trailer-00</a><o:p></o:p></p>
<p class=3D"MsoNormal">Comments will be welcome.<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Thanks.<o:p></o:p></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Ar=
ial&quot;,&quot;sans-serif&quot;">Tal.</span><o:p></o:p></p>
</div>
</body>
</html>

--_000_26FBD265CD8D234EAF41115A180F92BB38AE37CDSJCMBX01symmetr_--

From mills@udel.edu  Wed Jul 13 10:54:01 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 C1F5411E80AF for <tictoc@ietfa.amsl.com>; Wed, 13 Jul 2011 10:54:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.598
X-Spam-Level: 
X-Spam-Status: No, score=-6.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id xvnShhPqKB+U for <tictoc@ietfa.amsl.com>; Wed, 13 Jul 2011 10:54:00 -0700 (PDT)
Received: from mail.eecis.udel.edu (louie.udel.edu [128.4.40.12]) by ietfa.amsl.com (Postfix) with ESMTP id 0667A11E80A7 for <tictoc@ietf.org>; Wed, 13 Jul 2011 10:53:59 -0700 (PDT)
Received: from [192.168.1.3] (pool-74-109-5-222.phlapa.fios.verizon.net [74.109.5.222]) (Authenticated sender: mills@mail.eecis.udel.edu) by mail.eecis.udel.edu (Postfix) with ESMTP id 95719736; Wed, 13 Jul 2011 13:53:58 -0400 (EDT)
Message-ID: <4E1DDBB6.3020302@udel.edu>
Date: Wed, 13 Jul 2011 17:53:58 +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: Greg Dowd <GDowd@symmetricom.com>
References: <74470498B659FA4687F0B0018C19A89C01223E573C5A@IL-MB01.marvell.com> <26FBD265CD8D234EAF41115A180F92BB38AE2BBC@SJC-MBX-01.symmetricom.com>
In-Reply-To: <26FBD265CD8D234EAF41115A180F92BB38AE2BBC@SJC-MBX-01.symmetricom.com>
Content-Type: multipart/alternative; boundary="------------080605000408080406050408"
Cc: "ntpwg@lists.ntp.org" <ntpwg@lists.ntp.org>, "tictoc@ietf.org" <tictoc@ietf.org>
Subject: Re: [TICTOC] [ntpwg] New draft: draft-mizrahi-tictoc-checksum-trailer-00
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, 13 Jul 2011 17:54:01 -0000

This is a multi-part message in MIME format.
--------------080605000408080406050408
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit

Greg,

The MAC is intended to protect against a message modification attack, 
which surely is not the object here. In principle, the MAC can be 
omitted and an extension field can be used in much the same way as a 
transparent bridge in PTP.

Dave

Greg Dowd wrote:

> Is the use model you envision for NTP to support hardware timestamping 
> at the edge?  In NTP, the addition of an extension field requires the 
> presence of the MAC.  This requires the dissemination and maintenance 
> of keys as well as the defined MAC checking.  How would this model 
> work if the NTP packet did  have the MAC?  This extension field would 
> be covered by the MAC and the authenticator would fail.  Or do you 
> expect this block would have the key info and update the MAC as well?  
> And, how would it work if the MAC isn't there.  Would the update not 
> be used?
>
>  
>
> In PTP, there is a TC protocol function which necessitates the 
> modification of the packet.  In NTP, as it is defined as a UDP 
> protocol, there is not as clear a path to how lower stack layers 
> modify the PDUs.
>
>  
>
> If you define this simply at the edge, I'm not sure how much value 
> this additional UDP checksum update adds?  Is there a model you have 
> in mind?
>
>  
>
>  
>
>  
>
>  
>
> From: tictoc-bounces@ietf.org [mailto:tictoc-bounces@ietf.org] On 
> Behalf Of Tal Mizrahi
> Sent: Monday, July 04, 2011 5:01 AM
> To: tictoc@ietf.org; ntpwg@lists.ntp.org
> Subject: [TICTOC] [ntpwg] New draft: 
> draft-mizrahi-tictoc-checksum-trailer-00
>
>  
>
> Hi,
>
>  
>
> I have posted a new draft that discusses Checksum updates in time 
> synchronization protocols.
>
> http://tools.ietf.org/html/draft-mizrahi-tictoc-checksum-trailer-00
>
> Comments will be welcome.
>
>  
>
> Thanks.
>
> Tal.
>
>------------------------------------------------------------------------
>
>_______________________________________________
>ntpwg mailing list
>ntpwg@lists.ntp.org
>http://lists.ntp.org/listinfo/ntpwg
>


--------------080605000408080406050408
Content-Type: text/html; charset=us-ascii
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">
Greg,<br>
<br>
The MAC is intended to protect against a message modification attack,
which surely is not the object here. In principle, the MAC can be
omitted and an extension field can be used in much the same way as a
transparent bridge in PTP. <br>
<br>
Dave<br>
<br>
Greg Dowd wrote:<br>
<blockquote
 cite="mid26FBD265CD8D234EAF41115A180F92BB38AE2BBC@SJC-MBX-01.symmetricom.com"
 type="cite">
  <meta http-equiv="Content-Type" content="text/html; ">
  <meta name="Generator" content="Microsoft Word 12 (filtered medium)">
  <style><!--
/* Font Definitions */
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
span.EmailStyle17
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
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="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
  <div class="WordSection1">
  <p class="MsoNormal"><span style="color: rgb(31, 73, 125);">Is the
use model you envision for NTP to support hardware timestamping at the
edge?&nbsp; In NTP, the addition of an extension field requires the presence
of the MAC.&nbsp; This requires the dissemination and maintenance of keys as
well as the defined MAC checking.&nbsp; How would this model work if the NTP
packet did &nbsp;have the MAC?&nbsp; This extension field would be covered by the
MAC and the authenticator would fail.&nbsp; Or do you expect this block
would have the key info and update the MAC as well?&nbsp; And, how would it
work if the MAC isn&#8217;t there.&nbsp; Would the update not be used?<o:p></o:p></span></p>
  <p class="MsoNormal"><span style="color: rgb(31, 73, 125);"><o:p>&nbsp;</o:p></span></p>
  <p class="MsoNormal"><span style="color: rgb(31, 73, 125);">In PTP,
there is a TC protocol function which necessitates the modification of
the packet.&nbsp; In NTP, as it is defined as a UDP protocol, there is not
as clear a path to how lower stack layers modify the PDUs.
  <o:p></o:p></span></p>
  <p class="MsoNormal"><span style="color: rgb(31, 73, 125);"><o:p>&nbsp;</o:p></span></p>
  <p class="MsoNormal"><span style="color: rgb(31, 73, 125);">If you
define this simply at the edge, I&#8217;m not sure how much value this
additional UDP checksum update adds?&nbsp; Is there a model you have in mind?<o:p></o:p></span></p>
  <p class="MsoNormal"><span style="color: rgb(31, 73, 125);"><o:p>&nbsp;</o:p></span></p>
  <p class="MsoNormal"><span style="color: rgb(31, 73, 125);"><o:p>&nbsp;</o:p></span></p>
  <p class="MsoNormal"><span style="color: rgb(31, 73, 125);"><o:p>&nbsp;</o:p></span></p>
  <p class="MsoNormal"><span style="color: rgb(31, 73, 125);"><o:p>&nbsp;</o:p></span></p>
  <div>
  <div
 style="border-style: solid none none; border-color: rgb(181, 196, 223) -moz-use-text-color -moz-use-text-color; border-width: 1pt medium medium; padding: 3pt 0in 0in;">
  <p class="MsoNormal"><b><span
 style="font-size: 10pt; font-family: &quot;Tahoma&quot;,&quot;sans-serif&quot;;">From:</span></b><span
 style="font-size: 10pt; font-family: &quot;Tahoma&quot;,&quot;sans-serif&quot;;">
<a class="moz-txt-link-abbreviated" href="mailto:tictoc-bounces@ietf.org">tictoc-bounces@ietf.org</a> [<a class="moz-txt-link-freetext" href="mailto:tictoc-bounces@ietf.org">mailto:tictoc-bounces@ietf.org</a>]
  <b>On Behalf Of </b>Tal Mizrahi<br>
  <b>Sent:</b> Monday, July 04, 2011 5:01 AM<br>
  <b>To:</b> <a class="moz-txt-link-abbreviated" href="mailto:tictoc@ietf.org">tictoc@ietf.org</a>; <a class="moz-txt-link-abbreviated" href="mailto:ntpwg@lists.ntp.org">ntpwg@lists.ntp.org</a><br>
  <b>Subject:</b> [TICTOC] [ntpwg] New draft:
draft-mizrahi-tictoc-checksum-trailer-00<o:p></o:p></span></p>
  </div>
  </div>
  <p class="MsoNormal"><o:p>&nbsp;</o:p></p>
  <p class="MsoNormal">Hi,<o:p></o:p></p>
  <p class="MsoNormal"><o:p>&nbsp;</o:p></p>
  <p class="MsoNormal">I have posted a new draft that discusses
Checksum updates in time synchronization protocols.<o:p></o:p></p>
  <p class="MsoNormal"><a
 href="http://tools.ietf.org/html/draft-mizrahi-tictoc-checksum-trailer-00">http://tools.ietf.org/html/draft-mizrahi-tictoc-checksum-trailer-00</a><o:p></o:p></p>
  <p class="MsoNormal">Comments will be welcome.<o:p></o:p></p>
  <p class="MsoNormal"><o:p>&nbsp;</o:p></p>
  <p class="MsoNormal">Thanks.<o:p></o:p></p>
  <p class="MsoNormal"><span
 style="font-size: 10pt; font-family: &quot;Arial&quot;,&quot;sans-serif&quot;;">Tal.</span><o:p></o:p></p>
  </div>
  <pre wrap="">
<hr size="4" width="90%">
_______________________________________________
ntpwg mailing list
<a class="moz-txt-link-abbreviated" href="mailto:ntpwg@lists.ntp.org">ntpwg@lists.ntp.org</a>
<a class="moz-txt-link-freetext" href="http://lists.ntp.org/listinfo/ntpwg">http://lists.ntp.org/listinfo/ntpwg</a></pre>
</blockquote>
<br>
</body>
</html>

--------------080605000408080406050408--

From btv1==175cd238c05==GDowd@symmetricom.com  Wed Jul 13 11:22:31 2011
Return-Path: <btv1==175cd238c05==GDowd@symmetricom.com>
X-Original-To: tictoc@ietfa.amsl.com
Delivered-To: tictoc@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F276521F8C1C for <tictoc@ietfa.amsl.com>; Wed, 13 Jul 2011 11:22:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.931
X-Spam-Level: 
X-Spam-Status: No, score=-2.931 tagged_above=-999 required=5 tests=[AWL=-0.667, BAYES_00=-2.599, HTML_MESSAGE=0.001, IP_NOT_FRIENDLY=0.334]
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 OpJ-+KFITvyO for <tictoc@ietfa.amsl.com>; Wed, 13 Jul 2011 11:22:28 -0700 (PDT)
Received: from mail5.symmetricom.com (mail5.symmetricom.com [69.25.98.10]) by ietfa.amsl.com (Postfix) with ESMTP id 6FDA021F8C1A for <tictoc@ietf.org>; Wed, 13 Jul 2011 11:22:25 -0700 (PDT)
X-ASG-Debug-ID: 1310581343-11aa455c0001-4wH9i1
Received: from SJC-HUB-01.symmetricom.com ([192.168.10.171]) by mail5.symmetricom.com with ESMTP id lzTyRT7mQcfJcpN6; Wed, 13 Jul 2011 11:22:23 -0700 (PDT)
X-Barracuda-Envelope-From: GDowd@symmetricom.com
Received: from SJC-MBX-01.symmetricom.com ([169.254.1.52]) by SJC-HUB-01.symmetricom.com ([::1]) with mapi id 14.01.0289.001; Wed, 13 Jul 2011 11:22:23 -0700
From: Greg Dowd <GDowd@symmetricom.com>
To: "David L. Mills" <mills@udel.edu>
Thread-Topic: [ntpwg] [TICTOC] New draft: draft-mizrahi-tictoc-checksum-trailer-00
X-ASG-Orig-Subj: RE: [ntpwg] [TICTOC] New draft: draft-mizrahi-tictoc-checksum-trailer-00
Thread-Index: AQHMQYXYEZ8XM4eYrkOcQ+bAz02RfpTqi38w
Date: Wed, 13 Jul 2011 18:22:23 +0000
Message-ID: <26FBD265CD8D234EAF41115A180F92BB38AE4838@SJC-MBX-01.symmetricom.com>
References: <74470498B659FA4687F0B0018C19A89C01223E573C5A@IL-MB01.marvell.com> <26FBD265CD8D234EAF41115A180F92BB38AE2BBC@SJC-MBX-01.symmetricom.com> <4E1DDBB6.3020302@udel.edu>
In-Reply-To: <4E1DDBB6.3020302@udel.edu>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [192.168.3.42]
Content-Type: multipart/alternative; boundary="_000_26FBD265CD8D234EAF41115A180F92BB38AE4838SJCMBX01symmetr_"
MIME-Version: 1.0
X-Barracuda-Connect: UNKNOWN[192.168.10.171]
X-Barracuda-Start-Time: 1310581343
X-Barracuda-URL: http://192.168.10.96:80/cgi-mod/mark.cgi
X-Virus-Scanned: by bsmtpd at symmetricom.com
X-Barracuda-Spam-Score: -1002.00
X-Barracuda-Spam-Status: No, SCORE=-1002.00 using global scores of TAG_LEVEL=1000.0 QUARANTINE_LEVEL=1000.0 KILL_LEVEL=1000.0 
Cc: "ntpwg@lists.ntp.org" <ntpwg@lists.ntp.org>, "tictoc@ietf.org" <tictoc@ietf.org>
Subject: Re: [TICTOC] [ntpwg] New draft: draft-mizrahi-tictoc-checksum-trailer-00
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, 13 Jul 2011 18:22:44 -0000

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

The NTPv4 protocol, and the implementation, currently don't have the abilit=
y to distinguish an extension from a MAC uniquely.  I would rather see a "N=
OOP" MAC (with keyid 0 or -1) function defined which would let nodes proces=
s and drop the frame with auth failure and not a malformed packet.

Looking beyond the protocol state machine, how could we include some indica=
tor in the frame that it had been modified?  Perhaps we could make some ext=
ension mandatory?  One issue with the way TCs work in PTP is that they are =
all doing a read-modify-write against the correction field.  It is not poss=
ible to distinguish either the number or the timing characteristics of the =
elements modifying the time.  In a closed point-to-point protocol like tele=
com style PTP this is not an issue as the links, and the capabilities of th=
e TC elements, are well-defined and managed.  In NTP, it would be useful to=
 develop a "profile" which would define this NTP application over a control=
led or managed network.  It could specifically call out the usage of hardwa=
re timestamps where available, the format and/or requirement to generate an=
 extension, the restrictions on use of authenticators or autokey, the impac=
t on the utility value of the dispersion/root distance fields, etc.



Greg Dowd
gdowd at symmetricom dot com (antispam format)
Symmetricom, Inc.
www.symmetricom.com<http://www.symmetricom.com>
"Everything should be made as simple as possible, but no simpler" Albert Ei=
nstein
From: David L. Mills [mailto:mills@udel.edu]
Sent: Wednesday, July 13, 2011 10:54 AM
To: Greg Dowd
Cc: Tal Mizrahi; tictoc@ietf.org; ntpwg@lists.ntp.org
Subject: Re: [ntpwg] [TICTOC] New draft: draft-mizrahi-tictoc-checksum-trai=
ler-00

Greg,

The MAC is intended to protect against a message modification attack, which=
 surely is not the object here. In principle, the MAC can be omitted and an=
 extension field can be used in much the same way as a transparent bridge i=
n PTP.

Dave

Greg Dowd wrote:

Is the use model you envision for NTP to support hardware timestamping at t=
he edge?  In NTP, the addition of an extension field requires the presence =
of the MAC.  This requires the dissemination and maintenance of keys as wel=
l as the defined MAC checking.  How would this model work if the NTP packet=
 did  have the MAC?  This extension field would be covered by the MAC and t=
he authenticator would fail.  Or do you expect this block would have the ke=
y info and update the MAC as well?  And, how would it work if the MAC isn't=
 there.  Would the update not be used?

In PTP, there is a TC protocol function which necessitates the modification=
 of the packet.  In NTP, as it is defined as a UDP protocol, there is not a=
s clear a path to how lower stack layers modify the PDUs.

If you define this simply at the edge, I'm not sure how much value this add=
itional UDP checksum update adds?  Is there a model you have in mind?




From: tictoc-bounces@ietf.org<mailto:tictoc-bounces@ietf.org> [mailto:ticto=
c-bounces@ietf.org] On Behalf Of Tal Mizrahi
Sent: Monday, July 04, 2011 5:01 AM
To: tictoc@ietf.org<mailto:tictoc@ietf.org>; ntpwg@lists.ntp.org<mailto:ntp=
wg@lists.ntp.org>
Subject: [TICTOC] [ntpwg] New draft: draft-mizrahi-tictoc-checksum-trailer-=
00

Hi,

I have posted a new draft that discusses Checksum updates in time synchroni=
zation protocols.
http://tools.ietf.org/html/draft-mizrahi-tictoc-checksum-trailer-00
Comments will be welcome.

Thanks.
Tal.






________________________________






_______________________________________________

ntpwg mailing list

ntpwg@lists.ntp.org<mailto:ntpwg@lists.ntp.org>

http://lists.ntp.org/listinfo/ntpwg


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

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:x=3D"urn:schemas-microsoft-com:office:excel" xmlns:p=3D"urn:schemas-m=
icrosoft-com:office:powerpoint" xmlns:a=3D"urn:schemas-microsoft-com:office=
:access" xmlns:dt=3D"uuid:C2F41010-65B3-11d1-A29F-00AA00C14882" xmlns:s=3D"=
uuid:BDC6E3F0-6DA3-11d1-A2A3-00AA00C14882" xmlns:rs=3D"urn:schemas-microsof=
t-com:rowset" xmlns:z=3D"#RowsetSchema" xmlns:b=3D"urn:schemas-microsoft-co=
m:office:publisher" xmlns:ss=3D"urn:schemas-microsoft-com:office:spreadshee=
t" xmlns:c=3D"urn:schemas-microsoft-com:office:component:spreadsheet" xmlns=
:odc=3D"urn:schemas-microsoft-com:office:odc" xmlns:oa=3D"urn:schemas-micro=
soft-com:office:activation" xmlns:html=3D"http://www.w3.org/TR/REC-html40" =
xmlns:q=3D"http://schemas.xmlsoap.org/soap/envelope/" xmlns:rtc=3D"http://m=
icrosoft.com/officenet/conferencing" xmlns:D=3D"DAV:" xmlns:Repl=3D"http://=
schemas.microsoft.com/repl/" xmlns:mt=3D"http://schemas.microsoft.com/share=
point/soap/meetings/" xmlns:x2=3D"http://schemas.microsoft.com/office/excel=
/2003/xml" xmlns:ppda=3D"http://www.passport.com/NameSpace.xsd" xmlns:ois=
=3D"http://schemas.microsoft.com/sharepoint/soap/ois/" xmlns:dir=3D"http://=
schemas.microsoft.com/sharepoint/soap/directory/" xmlns:ds=3D"http://www.w3=
.org/2000/09/xmldsig#" xmlns:dsp=3D"http://schemas.microsoft.com/sharepoint=
/dsp" xmlns:udc=3D"http://schemas.microsoft.com/data/udc" xmlns:xsd=3D"http=
://www.w3.org/2001/XMLSchema" xmlns:sub=3D"http://schemas.microsoft.com/sha=
repoint/soap/2002/1/alerts/" xmlns:ec=3D"http://www.w3.org/2001/04/xmlenc#"=
 xmlns:sp=3D"http://schemas.microsoft.com/sharepoint/" xmlns:sps=3D"http://=
schemas.microsoft.com/sharepoint/soap/" xmlns:xsi=3D"http://www.w3.org/2001=
/XMLSchema-instance" xmlns:udcs=3D"http://schemas.microsoft.com/data/udc/so=
ap" xmlns:udcxf=3D"http://schemas.microsoft.com/data/udc/xmlfile" xmlns:udc=
p2p=3D"http://schemas.microsoft.com/data/udc/parttopart" xmlns:wf=3D"http:/=
/schemas.microsoft.com/sharepoint/soap/workflow/" xmlns:dsss=3D"http://sche=
mas.microsoft.com/office/2006/digsig-setup" xmlns:dssi=3D"http://schemas.mi=
crosoft.com/office/2006/digsig" xmlns:mdssi=3D"http://schemas.openxmlformat=
s.org/package/2006/digital-signature" xmlns:mver=3D"http://schemas.openxmlf=
ormats.org/markup-compatibility/2006" xmlns:m=3D"http://schemas.microsoft.c=
om/office/2004/12/omml" xmlns:mrels=3D"http://schemas.openxmlformats.org/pa=
ckage/2006/relationships" xmlns:spwp=3D"http://microsoft.com/sharepoint/web=
partpages" xmlns:ex12t=3D"http://schemas.microsoft.com/exchange/services/20=
06/types" xmlns:ex12m=3D"http://schemas.microsoft.com/exchange/services/200=
6/messages" xmlns:pptsl=3D"http://schemas.microsoft.com/sharepoint/soap/Sli=
deLibrary/" xmlns:spsl=3D"http://microsoft.com/webservices/SharePointPortal=
Server/PublishedLinksService" xmlns:Z=3D"urn:schemas-microsoft-com:" xmlns:=
st=3D"&#1;" xmlns=3D"http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
<meta name=3D"Generator" content=3D"Microsoft Word 12 (filtered medium)">
<!--[if !mso]>
<style>
v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style>
<![endif]--><style>
<!--
 /* Font Definitions */
 @font-face
	{font-family:"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;}
@font-face
	{font-family:Consolas;
	panose-1:2 11 6 9 2 2 4 3 2 4;}
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";
	color:black;}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
pre
	{mso-style-priority:99;
	mso-style-link:"HTML Preformatted Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:10.0pt;
	font-family:"Courier New";
	color:black;}
span.EmailStyle17
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
span.EmailStyle18
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
span.HTMLPreformattedChar
	{mso-style-name:"HTML Preformatted Char";
	mso-style-priority:99;
	mso-style-link:"HTML Preformatted";
	font-family:Consolas;
	color:black;}
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 Section1
	{size:8.5in 11.0in;
	margin:1.0in 1.25in 1.0in 1.25in;}
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 bgcolor=3D"white" lang=3D"EN-US" link=3D"blue" vlink=3D"purple">
<div class=3D"Section1">
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">The NTPv4 protocol, an=
d the implementation, currently don&#8217;t have the ability to distinguish=
 an extension from a MAC uniquely.&nbsp; I would rather see a &#8220;NOOP&#=
8221; MAC (with keyid 0 or -1) function defined which would
 let nodes process and drop the frame with auth failure and not a malformed=
 packet.&nbsp;
<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">Looking beyond the pro=
tocol state machine, how could we include some indicator in the frame that =
it had been modified?&nbsp; Perhaps we could make some extension mandatory?=
&nbsp; One issue with the way TCs work in PTP
 is that they are all doing a read-modify-write against the correction fiel=
d.&nbsp; It is not possible to distinguish either the number or the timing =
characteristics of the elements modifying the time.&nbsp; In a closed point=
-to-point protocol like telecom style PTP
 this is not an issue as the links, and the capabilities of the TC elements=
, are well-defined and managed.&nbsp; In NTP, it would be useful to develop=
 a &#8220;profile&#8221; which would define this NTP application over a con=
trolled or managed network.&nbsp; It could specifically
 call out the usage of hardware timestamps where available, the format and/=
or requirement to generate an extension, the restrictions on use of authent=
icators or autokey, the impact on the utility value of the dispersion/root =
distance fields, etc.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Ar=
ial&quot;,&quot;sans-serif&quot;;
color:#1F497D">Greg Dowd</span><span style=3D"font-size:12.0pt;font-family:=
&quot;Times New Roman&quot;,&quot;serif&quot;;
color:#1F497D"><o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Ar=
ial&quot;,&quot;sans-serif&quot;;
color:#1F497D">gdowd at symmetricom dot com (antispam format)</span><span s=
tyle=3D"font-size:12.0pt;font-family:&quot;Times New Roman&quot;,&quot;seri=
f&quot;;color:#1F497D"><o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Ar=
ial&quot;,&quot;sans-serif&quot;;
color:#1F497D">Symmetricom, Inc.</span><span style=3D"font-size:12.0pt;
font-family:&quot;Times New Roman&quot;,&quot;serif&quot;;color:#1F497D"><o=
:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Ar=
ial&quot;,&quot;sans-serif&quot;;
color:#1F497D"><a href=3D"http://www.symmetricom.com">www.symmetricom.com</=
a></span><span style=3D"font-size:12.0pt;font-family:&quot;Times New Roman&=
quot;,&quot;serif&quot;;color:#1F497D"><o:p></o:p></span></p>
</div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Ar=
ial&quot;,&quot;sans-serif&quot;;
color:#1F497D">&quot;Everything should be made as simple as possible, but n=
o simpler&quot; Albert Einstein</span><span style=3D"color:#1F497D"><o:p></=
o:p></span></p>
<div>
<div style=3D"border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in =
0in 0in">
<p class=3D"MsoNormal"><b><span style=3D"font-size:10.0pt;font-family:&quot=
;Tahoma&quot;,&quot;sans-serif&quot;;
color:windowtext">From:</span></b><span style=3D"font-size:10.0pt;font-fami=
ly:
&quot;Tahoma&quot;,&quot;sans-serif&quot;;color:windowtext"> David L. Mills=
 [mailto:mills@udel.edu]
<br>
<b>Sent:</b> Wednesday, July 13, 2011 10:54 AM<br>
<b>To:</b> Greg Dowd<br>
<b>Cc:</b> Tal Mizrahi; tictoc@ietf.org; ntpwg@lists.ntp.org<br>
<b>Subject:</b> Re: [ntpwg] [TICTOC] New draft: draft-mizrahi-tictoc-checks=
um-trailer-00<o:p></o:p></span></p>
</div>
</div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Greg,<br>
<br>
The MAC is intended to protect against a message modification attack, which=
 surely is not the object here. In principle, the MAC can be omitted and an=
 extension field can be used in much the same way as a transparent bridge i=
n PTP.
<br>
<br>
Dave<br>
<br>
Greg Dowd wrote:<br>
<br>
<o:p></o:p></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">Is the use model you e=
nvision for NTP to support hardware timestamping at the edge?&nbsp; In NTP,=
 the addition of an extension field requires the presence of the MAC.&nbsp;=
 This requires the dissemination and maintenance
 of keys as well as the defined MAC checking.&nbsp; How would this model wo=
rk if the NTP packet did &nbsp;have the MAC?&nbsp; This extension field wou=
ld be covered by the MAC and the authenticator would fail.&nbsp; Or do you =
expect this block would have the key info and update
 the MAC as well?&nbsp; And, how would it work if the MAC isn&#8217;t there=
.&nbsp; Would the update not be used?</span><o:p></o:p></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">&nbsp;</span><o:p></o:=
p></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">In PTP, there is a TC =
protocol function which necessitates the modification of the packet.&nbsp; =
In NTP, as it is defined as a UDP protocol, there is not as clear a path to=
 how lower stack layers modify the PDUs.
</span><o:p></o:p></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">&nbsp;</span><o:p></o:=
p></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">If you define this sim=
ply at the edge, I&#8217;m not sure how much value this additional UDP chec=
ksum update adds?&nbsp; Is there a model you have in mind?</span><o:p></o:p=
></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">&nbsp;</span><o:p></o:=
p></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">&nbsp;</span><o:p></o:=
p></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">&nbsp;</span><o:p></o:=
p></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">&nbsp;</span><o:p></o:=
p></p>
<div>
<div style=3D"border:none;border-top:solid windowtext 1.0pt;padding:3.0pt 0=
in 0in 0in;
border-color:-moz-use-text-color -moz-use-text-color">
<p class=3D"MsoNormal"><b><span style=3D"font-size:10.0pt;font-family:&quot=
;Tahoma&quot;,&quot;sans-serif&quot;">From:</span></b><span style=3D"font-s=
ize:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;">
<a href=3D"mailto:tictoc-bounces@ietf.org">tictoc-bounces@ietf.org</a> [<a =
href=3D"mailto:tictoc-bounces@ietf.org">mailto:tictoc-bounces@ietf.org</a>]
<b>On Behalf Of </b>Tal Mizrahi<br>
<b>Sent:</b> Monday, July 04, 2011 5:01 AM<br>
<b>To:</b> <a href=3D"mailto:tictoc@ietf.org">tictoc@ietf.org</a>; <a href=
=3D"mailto:ntpwg@lists.ntp.org">
ntpwg@lists.ntp.org</a><br>
<b>Subject:</b> [TICTOC] [ntpwg] New draft: draft-mizrahi-tictoc-checksum-t=
railer-00</span><o:p></o:p></p>
</div>
</div>
<p class=3D"MsoNormal">&nbsp;<o:p></o:p></p>
<p class=3D"MsoNormal">Hi,<o:p></o:p></p>
<p class=3D"MsoNormal">&nbsp;<o:p></o:p></p>
<p class=3D"MsoNormal">I have posted a new draft that discusses Checksum up=
dates in time synchronization protocols.<o:p></o:p></p>
<p class=3D"MsoNormal"><a href=3D"http://tools.ietf.org/html/draft-mizrahi-=
tictoc-checksum-trailer-00">http://tools.ietf.org/html/draft-mizrahi-tictoc=
-checksum-trailer-00</a><o:p></o:p></p>
<p class=3D"MsoNormal">Comments will be welcome.<o:p></o:p></p>
<p class=3D"MsoNormal">&nbsp;<o:p></o:p></p>
<p class=3D"MsoNormal">Thanks.<o:p></o:p></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Ar=
ial&quot;,&quot;sans-serif&quot;">Tal.</span><o:p></o:p></p>
<pre><o:p>&nbsp;</o:p></pre>
<pre style=3D"text-align:center">

<hr size=3D"4" width=3D"90%" align=3D"center">

</pre>
<pre><o:p>&nbsp;</o:p></pre>
<pre>_______________________________________________<o:p></o:p></pre>
<pre>ntpwg mailing list<o:p></o:p></pre>
<pre><a href=3D"mailto:ntpwg@lists.ntp.org">ntpwg@lists.ntp.org</a><o:p></o=
:p></pre>
<pre><a href=3D"http://lists.ntp.org/listinfo/ntpwg">http://lists.ntp.org/l=
istinfo/ntpwg</a><o:p></o:p></pre>
<p class=3D"MsoNormal"><span style=3D"font-size:12.0pt;font-family:&quot;Ti=
mes New Roman&quot;,&quot;serif&quot;"><o:p>&nbsp;</o:p></span></p>
</div>
</body>
</html>

--_000_26FBD265CD8D234EAF41115A180F92BB38AE4838SJCMBX01symmetr_--

From kodonog@gmail.com  Thu Jul 14 08:50:15 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 4D91521F8C6D for <tictoc@ietfa.amsl.com>; Thu, 14 Jul 2011 08:50:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.599
X-Spam-Level: 
X-Spam-Status: No, score=-103.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, 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 wqAj6PL16EDn for <tictoc@ietfa.amsl.com>; Thu, 14 Jul 2011 08:50:14 -0700 (PDT)
Received: from mail-vw0-f44.google.com (mail-vw0-f44.google.com [209.85.212.44]) by ietfa.amsl.com (Postfix) with ESMTP id A850321F8CA3 for <tictoc@ietf.org>; Thu, 14 Jul 2011 08:50:14 -0700 (PDT)
Received: by vws12 with SMTP id 12so398385vws.31 for <tictoc@ietf.org>; Thu, 14 Jul 2011 08:50:13 -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:cc :subject:content-type:content-transfer-encoding; bh=wLUDSiHdaD+euC8a4ZhNFWvl0TBWDUU7RzpVMgy0Fu4=; b=KCAkXH8HhitqcvrzXRe2l0wzJXzVgQ3mnocmJWZVFnOiwVEXVSS6Vjq3uwodhDzEZn N0F3GUGHJAwqGVivi5kpY15L/k0ducI8vzKRmCEQWx9GKcJGatuBaR8lrjPkJhEdr3hp IMqmGsPri1Ll2ViWrFbCoN2OO2U+QCG5v7Fjc=
Received: by 10.52.90.106 with SMTP id bv10mr2493245vdb.142.1310658613795; Thu, 14 Jul 2011 08:50:13 -0700 (PDT)
Received: from kodonog-mac.local (d-74-214-49-212.cpe.metrocast.net [74.214.49.212]) by mx.google.com with ESMTPS id es2sm238933vbb.19.2011.07.14.08.50.12 (version=SSLv3 cipher=OTHER); Thu, 14 Jul 2011 08:50:12 -0700 (PDT)
Sender: Karen ODonoghue <kodonog@gmail.com>
Message-ID: <4E1F1033.3000308@pobox.com>
Date: Thu, 14 Jul 2011 11:50:11 -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, NTP Working Group <ntpwg@lists.ntp.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: [TICTOC] draft agenda for ietf81 tictoc meeting
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: Thu, 14 Jul 2011 15:50:15 -0000

Folks,

Below is a draft agenda for the upcoming tictoc meeting. Please send 
Yaakov and I any changes and additions as soon as possible.

Regards,
Karen

IETF-81 TICTOC WG Agenda
========================

Thursday, 28 July 2011, 1520-1720 EDT
(1940 - 2140 UTC / 1220 - 1420 PDT)

1.   Administrivia and Agenda Bashing

2.   ITU-T SG15/Q13 update

3.   IPsec security for packet based synchronization
      draft-xu-tictoc-ipsec-security-for-synchronization-01

4.   Time Synchronization Protocol Security Requirements

5.   Precision Time Protocol Version 2 (PTPv2) Management Information Base
      draft-ietf-tictoc-ptp-mib-00

6.   Transporting PTP messages (1588) over MPLS Networks
      draft-ietf-tictoc-1588overmpls-01

7.   UDP Checksum Trailer in Timing Protocols
      draft-mizrahi-tictoc-checksum-trailer-00.txt

8.   Network Time Mechanisms for Improving Computer Clock Accuracy
      draft-marlow-tictoc-computer-clock-accuracy-00

9.   Additional NTP Discussion Topics

10.  Wrap-up / Way Forward


From odonoghue@isoc.org  Thu Jul 28 07:51:47 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 510CC21F8A62 for <tictoc@ietfa.amsl.com>; Thu, 28 Jul 2011 07:51:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.516
X-Spam-Level: 
X-Spam-Status: No, score=-103.516 tagged_above=-999 required=5 tests=[AWL=0.083, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, 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 gt4+EuyQ7IIT for <tictoc@ietfa.amsl.com>; Thu, 28 Jul 2011 07:51:46 -0700 (PDT)
Received: from smtp135.iad.emailsrvr.com (smtp135.iad.emailsrvr.com [207.97.245.135]) by ietfa.amsl.com (Postfix) with ESMTP id D3EC221F86A5 for <tictoc@ietf.org>; Thu, 28 Jul 2011 07:51:46 -0700 (PDT)
Received: from localhost (localhost.localdomain [127.0.0.1]) by smtp43.relay.iad1a.emailsrvr.com (SMTP Server) with ESMTP id 65A352D0211; Thu, 28 Jul 2011 10:51:46 -0400 (EDT)
X-Virus-Scanned: OK
Received: by smtp43.relay.iad1a.emailsrvr.com (Authenticated sender: odonoghue-AT-isoc.org) with ESMTPSA id 3B7E32D016A;  Thu, 28 Jul 2011 10:51:46 -0400 (EDT)
Message-ID: <4E317781.3010708@isoc.org>
Date: Thu, 28 Jul 2011 10:51:45 -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, NTP Working Group <ntpwg@lists.ntp.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: [TICTOC] reminder and remote participation information for today's meeting
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: Thu, 28 Jul 2011 14:51:47 -0000

Folks,

As previously discussed, there will be a face to face meeting of the 
tictoc wg here at IETF 81. Note that I am cross-posting this to the ntp 
wg as well as there is related discussions there.

For remote participation, there is an audio stream to listen and a 
jabber channel for submitting comments/questions. The easiest way to 
directly access the information is: http://tools.ietf.org/agenda/81/
General information is available at: 
http://www.ietf.org/meeting/81/remote-participation.html


IETF-81 TICTOC WG Agenda
========================

Thursday, 28 July 2011, 1520-1720 EDT
(1940 - 2140 UTC / 1220 - 1420 PDT)

1.   Administrivia and Agenda Bashing

2.   ITU-T SG15/Q13 update

3.   IPsec security for packet based synchronization
      draft-xu-tictoc-ipsec-security-for-synchronization-01

4.   Time Synchronization Protocol Security Requirements

5.   Precision Time Protocol Version 2 (PTPv2) Management Information Base
      draft-ietf-tictoc-ptp-mib-00

6.   Transporting PTP messages (1588) over MPLS Networks
      draft-ietf-tictoc-1588overmpls-01

7.   UDP Checksum Trailer in Timing Protocols
      draft-mizrahi-tictoc-checksum-trailer-00.txt

8.   Network Time Mechanisms for Improving Computer Clock Accuracy
      draft-marlow-tictoc-computer-clock-accuracy-00

9.   Additional NTP Discussion Topics

10.  Wrap-up / Way Forward


From ronc.ntear@gmail.com  Thu Jul 28 14:33:10 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 20F9021F89C2 for <tictoc@ietfa.amsl.com>; Thu, 28 Jul 2011 14:33:10 -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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ssINgLMpj0-U for <tictoc@ietfa.amsl.com>; Thu, 28 Jul 2011 14:33:09 -0700 (PDT)
Received: from mail-yx0-f172.google.com (mail-yx0-f172.google.com [209.85.213.172]) by ietfa.amsl.com (Postfix) with ESMTP id 85B2221F89BA for <tictoc@ietf.org>; Thu, 28 Jul 2011 14:33:09 -0700 (PDT)
Received: by yxp4 with SMTP id 4so2371823yxp.31 for <tictoc@ietf.org>; Thu, 28 Jul 2011 14:33:09 -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=wPc+QK75O00mpG4jIGPJ3p6wo8c8pHgKPqPJqcHF5rI=; b=v+Ol9lLSu/ZtE2sST2NPvwOrXsFpHk9KmrRfFtmQqf3tCuGTnO5w/bGfb7QM13F79T qXTUQTmEhjpEqIu8zoHbr3HsnpaqDKwu5X93vWuN2Nk/jkAqlGqFSDktnuJ3D06q8Amn 3C+NocMKeCrhbKbiVAhI5xMLQVngKYwCz5zfM=
MIME-Version: 1.0
Received: by 10.147.142.8 with SMTP id u8mr327008yan.37.1311888788932; Thu, 28 Jul 2011 14:33:08 -0700 (PDT)
Received: by 10.146.167.16 with HTTP; Thu, 28 Jul 2011 14:33:08 -0700 (PDT)
Date: Fri, 29 Jul 2011 00:33:08 +0300
Message-ID: <CALMYT9TP6WqrZgR2+o_zk7QwYXFE28d4QBo8Q89q+OYJ2cvy1Q@mail.gmail.com>
From: Ron Cohen <ronc.ntear@gmail.com>
To: tictoc@ietf.org
Content-Type: multipart/alternative; boundary=000e0cd2ea043fc8c104a927e99e
Subject: [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: Thu, 28 Jul 2011 21:33:10 -0000

--000e0cd2ea043fc8c104a927e99e
Content-Type: text/plain; charset=ISO-8859-1

Hi,

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

According to RFC1612 Eqn 3 (incremental checksum update):

HC' = ~(C + (-m) + m') = ~(~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
the old checksum and the new value alone.

That is, if the NTP/OWAMP/TWAMP CPU sets the transmit timestamp to zero
(i.e. m = 0), the FPGA or switch 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 doesn't need the extension. The extension
is need 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
clocks) used by PTP.

Best,
Ron

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

<div dir=3D"ltr">Hi,<br><br>I&#39;d like to clarify my comment during the m=
eeting.<br><br>According to RFC1612 Eqn 3 (incremental checksum update):<br=
><br>HC&#39; =3D ~(C + (-m) + m&#39;) =3D ~(~HC + ~m + m&#39;)<br><br>Where=
 HC&#39; is the updated checksum, HC is the current (message) checksum, m&#=
39;=20
in the new value that is going to be written instead of the value m=20
in the message.<br><br>If I know that value of m is zero, I can calculate t=
he 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 the f=
irst byte of the message is sent on the wire, can update the UDP checksum i=
tself incrementally and doesn&#39;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 &#39;real&#39; intermediate devices (i.e. t=
ransparent clocks) used by PTP.<br><br>Best,<br>Ron<br>
<br></div>

--000e0cd2ea043fc8c104a927e99e--

From yaakov_s@rad.com  Thu Jul 28 18:08:11 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 E064D11E8092 for <tictoc@ietfa.amsl.com>; Thu, 28 Jul 2011 18:08:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.931
X-Spam-Level: 
X-Spam-Status: No, score=-102.931 tagged_above=-999 required=5 tests=[AWL=-0.333, BAYES_00=-2.599, HTML_MESSAGE=0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6qnVC62Ie-YA for <tictoc@ietfa.amsl.com>; Thu, 28 Jul 2011 18:08:10 -0700 (PDT)
Received: from antivir2.rad.co.il (antivir2.rad.co.il [62.0.23.221]) by ietfa.amsl.com (Postfix) with ESMTP id 0243811E8073 for <tictoc@ietf.org>; Thu, 28 Jul 2011 18:08:08 -0700 (PDT)
Received: from exrad5.ad.rad.co.il ([192.114.24.28]) by antivir2.rad.co.il with ESMTP; 29 Jul 2011 04:08:07 +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; Fri, 29 Jul 2011 04:08:06 +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; Fri, 29 Jul 2011 04:08:06 +0300
From: Yaakov Stein <yaakov_s@rad.com>
To: Ron Cohen <ronc.ntear@gmail.com>, "tictoc@ietf.org" <tictoc@ietf.org>
Thread-Topic: [TICTOC] The Need for Checksum Extension
Thread-Index: AQHMTW4ERpEJJlrC1kmFT9KOG6ZV95UCesVA
Date: Fri, 29 Jul 2011 01:08:05 +0000
Message-ID: <07F7D7DED63154409F13298786A2ADC903E8FDCC@EXRAD5.ad.rad.co.il>
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: 
x-originating-ip: [207.232.33.112]
Content-Type: multipart/alternative; boundary="_000_07F7D7DED63154409F13298786A2ADC903E8FDCCEXRAD5adradcoil_"
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, 29 Jul 2011 01:08:12 -0000

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

I agree.

and assuming that the NTP or xWAMP IP is carried over Ethernet
I would like to ask what the authors are not concerned about the FCS ?

CRC can not be readily updated, and so needs to iterate over the entire pay=
load, but is still calculated on the fly.
So the UDP checksum, which CAN be readily updated, can certainly be.

I realize practical reasoning that there are already hardware implementatio=
ns for calculating the CRC.
Yet I think that we need a very strong reason to do standardization work
simply to avoid building a very small simple hardware module for the checks=
um.

Y(J)S

From: tictoc-bounces@ietf.org [mailto:tictoc-bounces@ietf.org] On Behalf Of=
 Ron Cohen
Sent: Friday, July 29, 2011 00:33
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_07F7D7DED63154409F13298786A2ADC903E8FDCCEXRAD5adradcoil_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
<meta name=3D"Generator" content=3D"Microsoft Word 12 (filtered medium)">
<style>
<!--
 /* Font Definitions */
 @font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
span.EmailStyle17
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;}
@page Section1
	{size:612.0pt 792.0pt;
	margin:72.0pt 90.0pt 72.0pt 90.0pt;}
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=3D"EN-US" link=3D"blue" vlink=3D"purple">
<div class=3D"Section1">
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;
color:#1F497D">I agree.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;
color:#1F497D"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;
color:#1F497D">and assuming that the NTP or xWAMP IP is carried over Ethern=
et
<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;
color:#1F497D">I would like to ask what the authors are not concerned about=
 the FCS ?<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;
color:#1F497D"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;
color:#1F497D">CRC can not be readily updated, and so needs to iterate over=
 the entire payload, but is still calculated on the fly.
<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;
color:#1F497D">So the UDP checksum, which CAN be readily updated, can certa=
inly be.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;
color:#1F497D"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;
color:#1F497D">I realize practical reasoning that there are already hardwar=
e implementations for calculating the CRC.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;
color:#1F497D">Yet I think that we need a very strong reason to do standard=
ization work
<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;
color:#1F497D">simply to avoid building a very small simple hardware module=
 for the checksum.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;
color:#1F497D"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;
color:#1F497D">Y(J)S<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;
color:#1F497D"><o:p>&nbsp;</o:p></span></p>
<div style=3D"border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm =
0cm 0cm">
<p class=3D"MsoNormal"><b><span style=3D"font-size:10.0pt;font-family:&quot=
;Tahoma&quot;,&quot;sans-serif&quot;">From:</span></b><span style=3D"font-s=
ize:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;"> tictoc-b=
ounces@ietf.org [mailto:tictoc-bounces@ietf.org]
<b>On Behalf Of </b>Ron Cohen<br>
<b>Sent:</b> Friday, July 29, 2011 00:33<br>
<b>To:</b> tictoc@ietf.org<br>
<b>Subject:</b> [TICTOC] The Need for Checksum Extension<o:p></o:p></span><=
/p>
</div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<div>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt">Hi,<br>
<br>
I'd like to clarify my comment during the meeting.<br>
<br>
According to RFC1612 Eqn 3 (incremental checksum update):<br>
<br>
HC' =3D ~(C &#43; (-m) &#43; m') =3D ~(~HC &#43; ~m &#43; 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 t=
he 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 need only if you have to read the tim=
estamp which appears later in the packet in order to update the checksum.<b=
r>
<br>
This is very different from 'real' intermediate devices (i.e. transparent c=
locks) used by PTP.<br>
<br>
Best,<br>
Ron<o:p></o:p></p>
</div>
</div>
</body>
</html>

--_000_07F7D7DED63154409F13298786A2ADC903E8FDCCEXRAD5adradcoil_--

From hmurray@megapathdsl.net  Fri Jul 29 12:17:09 2011
Return-Path: <hmurray@megapathdsl.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 0013A21F8B3E for <tictoc@ietfa.amsl.com>; Fri, 29 Jul 2011 12:17:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 4.288
X-Spam-Level: ****
X-Spam-Status: No, score=4.288 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FH_HELO_EQ_D_D_D_D=1.597, FH_HOST_EQ_D_D_D_D=0.765, FM_DDDD_TIMES_2=1.999, HELO_DYNAMIC_IPADDR=2.426, RDNS_DYNAMIC=0.1]
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 VRuzMKRPFFJv for <tictoc@ietfa.amsl.com>; Fri, 29 Jul 2011 12:17:08 -0700 (PDT)
Received: from ip-64-139-1-69.sjc.megapath.net (ip-64-139-1-69.sjc.megapath.net [64.139.1.69]) by ietfa.amsl.com (Postfix) with ESMTP id D68B621F8B73 for <tictoc@ietf.org>; Fri, 29 Jul 2011 12:17:07 -0700 (PDT)
Received: from shuksan (localhost [127.0.0.1]) by ip-64-139-1-69.sjc.megapath.net (Postfix) with ESMTP id 680CD800037;  Fri, 29 Jul 2011 12:17:07 -0700 (PDT)
X-Mailer: exmh version 2.7.2 01/07/2005 with nmh-1.3
To: tictoc@ietf.org
From: Hal Murray <hmurray@megapathdsl.net>
In-Reply-To: Message from tictoc-request@ietf.org of "Thu, 28 Jul 2011 18:08:12 PDT." <mailman.1669.1311901692.23921.tictoc@ietf.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Fri, 29 Jul 2011 12:17:07 -0700
Message-Id: <20110729191707.680CD800037@ip-64-139-1-69.sjc.megapath.net>
Cc: hmurray@megapathdsl.net
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, 29 Jul 2011 19:17:09 -0000

> 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 CAN
> be readily updated, can certainly be. 

The CRC can be updated rather than recalculating the CRC of the whole message.

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

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



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



