
From lizhong.jin@zte.com.cn  Tue Jan  4 22:24:03 2011
Return-Path: <lizhong.jin@zte.com.cn>
X-Original-To: tictoc@core3.amsl.com
Delivered-To: tictoc@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id DCF6A3A6992; Tue,  4 Jan 2011 22:24:01 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.475
X-Spam-Level: 
X-Spam-Status: No, score=-101.475 tagged_above=-999 required=5 tests=[AWL=0.363, 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.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id QKGNRbHmTpBL; Tue,  4 Jan 2011 22:23:58 -0800 (PST)
Received: from mx5.zte.com.cn (mx5.zte.com.cn [63.217.80.70]) by core3.amsl.com (Postfix) with ESMTP id 2A8A03A6A77; Tue,  4 Jan 2011 22:23:56 -0800 (PST)
Received: from [10.30.17.99] by mx5.zte.com.cn with surfront esmtp id 205952736992880; Wed, 5 Jan 2011 14:21:56 +0800 (CST)
Received: from [10.32.0.74] by [192.168.168.15] with StormMail ESMTP id 68277.4874703856; Wed, 5 Jan 2011 14:26:00 +0800 (CST)
Received: from notes_smtp.zte.com.cn ([10.30.1.239]) by mse3.zte.com.cn with ESMTP id p056PvxR076684; Wed, 5 Jan 2011 14:25:57 +0800 (CST) (envelope-from lizhong.jin@zte.com.cn)
To: mpls@ietf.org, tictoc@ietf.org
MIME-Version: 1.0
X-Mailer: Lotus Notes Release 6.5.6 March 06, 2007
Message-ID: <OF8F7BE6CC.1A981E0B-ON4825780F.0021047C-4825780F.00234FC6@zte.com.cn>
From: lizhong.jin@zte.com.cn
Date: Wed, 5 Jan 2011 14:24:57 +0800
X-MIMETrack: S/MIME Sign by Notes Client on JinLiZhong127666/user/zte_ltd(Release 6.5.6|March 06, 2007) at 2011-01-05 14:25:41, Serialize by Notes Client on JinLiZhong127666/user/zte_ltd(Release 6.5.6|March 06, 2007) at 2011-01-05 14:25:41, Serialize complete at 2011-01-05 14:25:41, S/MIME Sign failed at 2011-01-05 14:25:41: The cryptographic key was not found, Serialize by Router on notes_smtp/zte_ltd(Release 8.5.1FP4|July 25, 2010) at 2011-01-05 14:25:46, Serialize complete at 2011-01-05 14:25:46
Content-Type: multipart/alternative; boundary="=_alternative 00234FC14825780F_="
X-MAIL: mse3.zte.com.cn p056PvxR076684
Cc: Ice  <ice@cisco.com>, N.Leymann@telekom.de
Subject: [TICTOC] Request comments for HSMP LSP
X-BeenThere: tictoc@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Timing over IP Connection and Transfer of Clock BOF <tictoc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/tictoc>, <mailto:tictoc-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tictoc>
List-Post: <mailto:tictoc@ietf.org>
List-Help: <mailto:tictoc-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tictoc>, <mailto:tictoc-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 05 Jan 2011 06:24:03 -0000

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

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.

--------------------------------------------------------
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 00234FC14825780F_=
Content-Type: text/html; charset="US-ASCII"


<br><font size=2 face="sans-serif">Hi all,</font>
<br><font size=2 face="sans-serif">During IETF 79 Beijing, we made a presentation
for HSMP LSP at MPLS session.</font>
<br><font size=2 face="sans-serif">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.</font>
<br>
<br><font size=2 face="sans-serif">The draft link is: http://tools.ietf.org/html/draft-jin-jounay-mpls-mldp-hsmp-01</font>
<br><font size=1 face="Arial">&nbsp;</font>
<br><font size=2 face="sans-serif">Thank you.</font>
<br><font size=2 face="sans-serif">Authors of draft-hsmp.</font><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 00234FC14825780F_=--


From lizhong.jin@zte.com.cn  Tue Jan  4 23:52:35 2011
Return-Path: <lizhong.jin@zte.com.cn>
X-Original-To: tictoc@core3.amsl.com
Delivered-To: tictoc@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id BB0483A6B83; Tue,  4 Jan 2011 23:52:35 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.497
X-Spam-Level: 
X-Spam-Status: No, score=-101.497 tagged_above=-999 required=5 tests=[AWL=0.341, 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.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id bJHLcLBaOW5o; Tue,  4 Jan 2011 23:52:34 -0800 (PST)
Received: from mx5.zte.com.cn (mx5.zte.com.cn [63.217.80.70]) by core3.amsl.com (Postfix) with ESMTP id A6A4E3A6A2C; Tue,  4 Jan 2011 23:52:33 -0800 (PST)
Received: from [10.30.17.99] by mx5.zte.com.cn with surfront esmtp id 205953314101978; Wed, 5 Jan 2011 15:50:20 +0800 (CST)
Received: from [10.30.3.19] by [192.168.168.15] with StormMail ESMTP id 68277.7391410851; Wed, 5 Jan 2011 15:51:46 +0800 (CST)
Received: from notes_smtp.zte.com.cn ([10.30.1.239]) by mse2.zte.com.cn with ESMTP id p057plgj095486; Wed, 5 Jan 2011 15:51:47 +0800 (CST) (envelope-from lizhong.jin@zte.com.cn)
In-Reply-To: <AANLkTinRCSGz6Bgu058c+HSHeH3OanCt_WMTnn-bNH6X@mail.gmail.com>
To: Ed <maillist.ed@gmail.com>
MIME-Version: 1.0
X-Mailer: Lotus Notes Release 6.5.6 March 06, 2007
Message-ID: <OF4BA0BF75.A883E04C-ON4825780F.002802E4-4825780F.002B2AB9@zte.com.cn>
From: lizhong.jin@zte.com.cn
Date: Wed, 5 Jan 2011 15:50:45 +0800
X-MIMETrack: S/MIME Sign by Notes Client on JinLiZhong127666/user/zte_ltd(Release 6.5.6|March 06, 2007) at 2011-01-05 15:51:29, Serialize by Notes Client on JinLiZhong127666/user/zte_ltd(Release 6.5.6|March 06, 2007) at 2011-01-05 15:51:29, Serialize complete at 2011-01-05 15:51:29, S/MIME Sign failed at 2011-01-05 15:51:29: The cryptographic key was not found, Serialize by Router on notes_smtp/zte_ltd(Release 8.5.1FP4|July 25, 2010) at 2011-01-05 15:51:33, Serialize complete at 2011-01-05 15:51:33
Content-Type: multipart/alternative; boundary="=_alternative 002B2AB74825780F_="
X-MAIL: mse2.zte.com.cn p057plgj095486
Cc: l2vpn@ietf.org, mpls@ietf.org, Ice <ice@cisco.com>, N.Leymann@telekom.de, tictoc@ietf.org
Subject: Re: [TICTOC] [mpls] Request comments for HSMP LSP
X-BeenThere: tictoc@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Timing over IP Connection and Transfer of Clock BOF <tictoc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/tictoc>, <mailto:tictoc-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tictoc>
List-Post: <mailto:tictoc@ietf.org>
List-Help: <mailto:tictoc-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tictoc>, <mailto:tictoc-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 05 Jan 2011 07:52:35 -0000

This is a multipart message in MIME format.
--=_alternative 002B2AB74825780F_=
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.
> --------------------------------------------------------
> 
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.
> 
> _______________________________________________
> mpls mailing list
> mpls@ietf.org
> https://www.ietf.org/mailman/listinfo/mpls


--------------------------------------------------------
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 002B2AB74825780F_=
Content-Type: text/html; charset="US-ASCII"


<br><font size=2 face="sans-serif">Hi Edward,</font>
<br><font size=2 face="sans-serif">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.</font>
<br>
<br><font size=2 face="sans-serif">Regards</font>
<br><font size=2 face="sans-serif">Lizhong</font>
<br><font size=1 face="Arial">&nbsp;</font>
<br>
<br><tt><font size=2>Ed &lt;maillist.ed@gmail.com&gt; wrote on 2011-01-05
15:05:30:<br>
<br>
&gt; Hi Lizhong,</font></tt>
<br><tt><font size=2>&gt; &nbsp;</font></tt>
<br><tt><font size=2>&gt; I think one possible application for HSMP LSPs
is to reduce the <br>
&gt; overall broadcast/multicast utilization on a VPLS. In current VPLS
<br>
&gt; implementations with a full mesh of P2P LSPs between PEs, broadcast,<br>
&gt; multicast and unknown traffic are not efficiently propagated on the
<br>
&gt; physical links between PEs and Ps.</font></tt>
<br><tt><font size=2>&gt; &nbsp;</font></tt>
<br><tt><font size=2>&gt; In the VPLS implementation scenario with HSMP
LSPs, each PE signals <br>
&gt; a HSMP LSP with itself as a root to all other PEs in the VPLS. <br>
&gt; Thereafter, all broadcast/multicast/unknown traffic from this PE <br>
&gt; will use this HSMP LSP. Unicast traffic from a particular PE (e.g.
<br>
&gt; PE1) to another PE (e.g. PE2) will be sent from leaf to root using
<br>
&gt; the HSMP LSP where PE2 is the root.</font></tt>
<br><tt><font size=2>&gt; &nbsp;</font></tt>
<br><tt><font size=2>&gt; This simplifies the VPLS implementation by:</font></tt>
<br><tt><font size=2>&gt; -&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
Reducing traffic utilization from broadcast, multicast <br>
&gt; and unknown traffic</font></tt>
<br><tt><font size=2>&gt; -&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
Reducing the total number of LSPs maintained by each PE <br>
&gt; (i.e. instead of requiring a full mesh of LSPs, now only require one<br>
&gt; HSMP LSP per PE).</font></tt>
<br><tt><font size=2>&gt; &nbsp;</font></tt>
<br><tt><font size=2>&gt; This is similar to the idea expressed in&nbsp;
draft-key-l2vpn-etree-<br>
&gt; frwk-03.txt (in a more general sense).</font></tt>
<br><tt><font size=2>&gt; &nbsp;</font></tt>
<br><tt><font size=2>&gt; What do you think? Would HSMP LSP be suitable
for this?</font></tt>
<br><tt><font size=2>&gt; <br>
&gt; Regards,</font></tt>
<br><tt><font size=2>&gt; Edward</font></tt>
<br><tt><font size=2>&gt; &nbsp;</font></tt>
<br><tt><font size=2>&gt; &nbsp;</font></tt>
<br><tt><font size=2>&gt; &nbsp;</font></tt>
<br><tt><font size=2>&gt; On Wed, Jan 5, 2011 at 5:24 PM, &lt;lizhong.jin@zte.com.cn&gt;
wrote:</font></tt>
<br><tt><font size=2>&gt; <br>
&gt; Hi all, <br>
&gt; During IETF 79 Beijing, we made a presentation for HSMP LSP at MPLS
session. <br>
&gt; HSMP LSP has several use cases described in the draft, e.g, time <br>
&gt; synchronization in MPLS network, IPTV scenario, or P2MP PW. It would<br>
&gt; be appreciated if you could give more scenarios for HSMP LSP. Please<br>
&gt; review the draft, and any comments are welcome. <br>
&gt; <br>
&gt; The draft link is: http://tools.ietf.org/html/draft-jin-jounay-mpls-<br>
&gt; mldp-hsmp-01 <br>
&gt; &nbsp; <br>
&gt; Thank you. <br>
&gt; Authors of draft-hsmp.</font></tt>
<br><tt><font size=2>&gt; --------------------------------------------------------<br>
&gt; ZTE&nbsp;Information&nbsp;Security&nbsp;Notice:&nbsp;The&nbsp;information&nbsp;contained&nbsp;in&nbsp;this&nbsp;mail&nbsp;is&nbsp;solely&nbsp;</font></tt>
<br><tt><font size=2>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.<br>
&gt; 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.<br>
&gt; 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.<br>
&gt; <br>
&gt; _______________________________________________<br>
&gt; mpls mailing list<br>
&gt; mpls@ietf.org<br>
&gt; https://www.ietf.org/mailman/listinfo/mpls<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 002B2AB74825780F_=--


From maillist.ed@gmail.com  Tue Jan  4 23:03:32 2011
Return-Path: <maillist.ed@gmail.com>
X-Original-To: tictoc@core3.amsl.com
Delivered-To: tictoc@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 3892E3A6B83; Tue,  4 Jan 2011 23:03:32 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.098
X-Spam-Level: 
X-Spam-Status: No, score=-3.098 tagged_above=-999 required=5 tests=[AWL=0.500,  BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id T1ZE6+wX2DGX; Tue,  4 Jan 2011 23:03:26 -0800 (PST)
Received: from mail-ww0-f44.google.com (mail-ww0-f44.google.com [74.125.82.44]) by core3.amsl.com (Postfix) with ESMTP id E99B73A6B45; Tue,  4 Jan 2011 23:03:25 -0800 (PST)
Received: by wwa36 with SMTP id 36so15091145wwa.13 for <multiple recipients>; Tue, 04 Jan 2011 23:05:32 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:cc:content-type; bh=AiW3EnKOwTOhU5+l7PWdMpkL1Ha8mzFYUxQA267jyrE=; b=uKdwI6aVGLT2BpirWmO/xT4wUKqc2PSRTTWgTh0VrTqmOYPsaoGnwOtVKWMDDQsp8N nYosft4Y0P03VvZNb441A4mwI/DTUpABG4KQQhvfZQqeMEz6McYCM9QFs+npGZjzUckZ HVaPfXv/4ypn2ZARuvpSjz4ksScZNMwQQ7psc=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=HG2F49H2Kw6+mcMlUiVRknpa1mEpb/wTXXiNExCtnqVgM4k/60HbbK+/gH8JlB6aAV 3ID+MOfDIDfHPXMe768ak5pnEUUUROBBDeDcluQxEy6UE+ejRmWoYNKFioM51GBjKO5m UvQaOBpXzIQMJV5D4bOlJVavg8b2zNqNqwdkw=
MIME-Version: 1.0
Received: by 10.227.96.212 with SMTP id i20mr12894823wbn.157.1294211130936; Tue, 04 Jan 2011 23:05:30 -0800 (PST)
Received: by 10.227.144.68 with HTTP; Tue, 4 Jan 2011 23:05:30 -0800 (PST)
In-Reply-To: <OF8F7BE6CC.1A981E0B-ON4825780F.0021047C-4825780F.00234FC6@zte.com.cn>
References: <OF8F7BE6CC.1A981E0B-ON4825780F.0021047C-4825780F.00234FC6@zte.com.cn>
Date: Wed, 5 Jan 2011 18:05:30 +1100
Message-ID: <AANLkTinRCSGz6Bgu058c+HSHeH3OanCt_WMTnn-bNH6X@mail.gmail.com>
From: Ed <maillist.ed@gmail.com>
To: lizhong.jin@zte.com.cn
Content-Type: multipart/alternative; boundary=000e0cd2e7d4b94e6e0499140252
X-Mailman-Approved-At: Wed, 05 Jan 2011 00:29:59 -0800
Cc: 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.9
Precedence: list
List-Id: Timing over IP Connection and Transfer of Clock BOF <tictoc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/tictoc>, <mailto:tictoc-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tictoc>
List-Post: <mailto:tictoc@ietf.org>
List-Help: <mailto:tictoc-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tictoc>, <mailto:tictoc-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 05 Jan 2011 07:03:32 -0000

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

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 an=
d
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.
>
> --------------------------------------------------------
> ZTE Information Security Notice: The information contained in this mail i=
s 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 intende=
d 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 individua=
l sender.
> This message has been scanned for viruses and Spam by ZTE Anti-Spam syste=
m.
>
>
> _______________________________________________
> mpls mailing list
> mpls@ietf.org
> https://www.ietf.org/mailman/listinfo/mpls
>
>

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

<div class=3D"gmail_quote">
<p style=3D"MARGIN: 0cm 0cm 0pt" class=3D"MsoNormal"><span style=3D"COLOR: =
black; mso-fareast-font-family: &#39;Times New Roman&#39;"><font size=3D"3"=
><font face=3D"Times New Roman">Hi Lizhong,</font></font></span></p>
<p style=3D"MARGIN: 0cm 0cm 0pt" class=3D"MsoNormal"><span style=3D"COLOR: =
#1f497d; mso-themecolor: dark2; mso-fareast-font-family: &#39;Times New Rom=
an&#39;"><font size=3D"3" face=3D"Times New Roman">=A0</font></span></p>
<p style=3D"MARGIN: 0cm 0cm 0pt" class=3D"MsoNormal"><span style=3D"COLOR: =
black; mso-fareast-font-family: &#39;Times New Roman&#39;"><font size=3D"3"=
><font face=3D"Times New Roman">I think one possible application for HSMP L=
SPs is to reduce the overall broadcast/multicast utilization on a VPLS. In =
current VPLS implementations with a full mesh of P2P LSPs between PEs, broa=
dcast, multicast and unknown traffic are not efficiently propagated on the =
physical links between PEs and Ps.</font></font></span></p>

<p style=3D"MARGIN: 0cm 0cm 0pt" class=3D"MsoNormal"><span style=3D"COLOR: =
#1f497d; mso-themecolor: dark2; mso-fareast-font-family: &#39;Times New Rom=
an&#39;"><font size=3D"3" face=3D"Times New Roman">=A0</font></span></p>
<p style=3D"MARGIN: 0cm 0cm 0pt" class=3D"MsoNormal"><span style=3D"COLOR: =
black; mso-fareast-font-family: &#39;Times New Roman&#39;"><font size=3D"3"=
><font face=3D"Times New Roman">In the VPLS implementation scenario with HS=
MP 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.</font></font></span></p>

<p style=3D"MARGIN: 0cm 0cm 0pt" class=3D"MsoNormal"><span style=3D"COLOR: =
#1f497d; mso-themecolor: dark2; mso-fareast-font-family: &#39;Times New Rom=
an&#39;"><font size=3D"3" face=3D"Times New Roman">=A0</font></span></p>
<p style=3D"MARGIN: 0cm 0cm 0pt" class=3D"MsoNormal"><span style=3D"COLOR: =
black; mso-fareast-font-family: &#39;Times New Roman&#39;"><font size=3D"3"=
><font face=3D"Times New Roman">This simplifies the VPLS implementation by:=
</font></font></span></p>

<p style=3D"TEXT-INDENT: -18pt; MARGIN: 0cm 0cm 0pt 60pt" class=3D"MsoNorma=
l"><font face=3D"Times New Roman"><span style=3D"mso-fareast-font-family: &=
#39;Times New Roman&#39;"><font size=3D"3">-</font></span><span style=3D"FO=
NT-SIZE: 7pt; mso-fareast-font-family: &#39;Times New Roman&#39;">=A0=A0=A0=
=A0=A0=A0=A0=A0=A0 </span><span style=3D"mso-fareast-font-family: &#39;Time=
s New Roman&#39;"><font size=3D"3">Reducing traffic utilization from broadc=
ast, multicast and unknown traffic</font></span></font></p>

<p style=3D"TEXT-INDENT: -18pt; MARGIN: 0cm 0cm 0pt 60pt" class=3D"MsoNorma=
l"><font face=3D"Times New Roman"><span style=3D"mso-fareast-font-family: &=
#39;Times New Roman&#39;"><font size=3D"3">-</font></span><span style=3D"FO=
NT-SIZE: 7pt; mso-fareast-font-family: &#39;Times New Roman&#39;">=A0=A0=A0=
=A0=A0=A0=A0=A0=A0 </span><span style=3D"mso-fareast-font-family: &#39;Time=
s New Roman&#39;"><font size=3D"3">Reducing the total number of LSPs mainta=
ined by each PE (i.e. instead of requiring a full mesh of LSPs, now only re=
quire one HSMP LSP per PE).</font></span></font></p>

<p style=3D"MARGIN: 0cm 0cm 0pt" class=3D"MsoNormal"><span style=3D"mso-far=
east-font-family: &#39;Times New Roman&#39;"><font size=3D"3" face=3D"Times=
 New Roman">=A0</font></span></p>
<p style=3D"MARGIN: 0cm 0cm 0pt" class=3D"MsoNormal"><font size=3D"3"><font=
 face=3D"Times New Roman"><span style=3D"COLOR: black; mso-fareast-font-fam=
ily: &#39;Times New Roman&#39;">This is similar to the idea expressed in<sp=
an style=3D"mso-spacerun: yes">=A0 </span>draft-key-l2vpn-etree-frwk-03.txt=
 (in a more general sense).</span><span style=3D"mso-fareast-font-family: &=
#39;Times New Roman&#39;"></span></font></font></p>

<p style=3D"MARGIN: 0cm 0cm 0pt" class=3D"MsoNormal"><font size=3D"3"><font=
 face=3D"Times New Roman"><span style=3D"COLOR: black; mso-fareast-font-fam=
ily: &#39;Times New Roman&#39;">=A0</span><span style=3D"COLOR: #1f497d; ms=
o-themecolor: dark2; mso-fareast-font-family: &#39;Times New Roman&#39;"></=
span></font></font></p>

<p style=3D"MARGIN: 0cm 0cm 0pt" class=3D"MsoNormal"><span style=3D"FONT-FA=
MILY: &#39;Calibri&#39;,&#39;sans-serif&#39;; COLOR: black; FONT-SIZE: 11pt=
; mso-fareast-font-family: &#39;Times New Roman&#39;; mso-ascii-theme-font:=
 minor-latin; mso-hansi-theme-font: minor-latin; mso-bidi-font-family: &#39=
;Times New Roman&#39;; mso-bidi-theme-font: minor-bidi">What do you think? =
Would HSMP LSP be suitable for this?</span></p>

<p style=3D"MARGIN: 0cm 0cm 0pt" class=3D"MsoNormal"><span style=3D"FONT-FA=
MILY: &#39;Calibri&#39;,&#39;sans-serif&#39;; COLOR: #1f497d; FONT-SIZE: 11=
pt; mso-themecolor: dark2; mso-fareast-font-family: &#39;Times New Roman&#3=
9;; mso-ascii-theme-font: minor-latin; mso-hansi-theme-font: minor-latin; m=
so-bidi-font-family: &#39;Times New Roman&#39;; mso-bidi-theme-font: minor-=
bidi"><br>
</span><span style=3D"FONT-FAMILY: &#39;Calibri&#39;,&#39;sans-serif&#39;; =
COLOR: black; FONT-SIZE: 11pt; mso-fareast-font-family: &#39;Times New Roma=
n&#39;; mso-ascii-theme-font: minor-latin; mso-hansi-theme-font: minor-lati=
n; mso-bidi-font-family: &#39;Times New Roman&#39;; mso-bidi-theme-font: mi=
nor-bidi">Regards,</span></p>

<p style=3D"MARGIN: 0cm 0cm 0pt" class=3D"MsoNormal"><span style=3D"FONT-FA=
MILY: &#39;Calibri&#39;,&#39;sans-serif&#39;; COLOR: black; FONT-SIZE: 11pt=
; mso-fareast-font-family: &#39;Times New Roman&#39;; mso-ascii-theme-font:=
 minor-latin; mso-hansi-theme-font: minor-latin; mso-bidi-font-family: &#39=
;Times New Roman&#39;; mso-bidi-theme-font: minor-bidi">Edward</span></p>

<p style=3D"MARGIN: 0cm 0cm 0pt" class=3D"MsoNormal"><span style=3D"FONT-FA=
MILY: &#39;Calibri&#39;,&#39;sans-serif&#39;; COLOR: black; FONT-SIZE: 11pt=
; mso-fareast-font-family: &#39;Times New Roman&#39;; mso-ascii-theme-font:=
 minor-latin; mso-hansi-theme-font: minor-latin; mso-bidi-font-family: &#39=
;Times New Roman&#39;; mso-bidi-theme-font: minor-bidi"></span>=A0</p>

<p style=3D"MARGIN: 0cm 0cm 0pt" class=3D"MsoNormal"><span style=3D"FONT-FA=
MILY: &#39;Calibri&#39;,&#39;sans-serif&#39;; COLOR: black; FONT-SIZE: 11pt=
; mso-fareast-font-family: &#39;Times New Roman&#39;; mso-ascii-theme-font:=
 minor-latin; mso-hansi-theme-font: minor-latin; mso-bidi-font-family: &#39=
;Times New Roman&#39;; mso-bidi-theme-font: minor-bidi"></span>=A0</p>
</div>
<div class=3D"gmail_quote">=A0</div>
<div class=3D"gmail_quote">On Wed, Jan 5, 2011 at 5:24 PM, <span dir=3D"ltr=
">&lt;<a href=3D"mailto:lizhong.jin@zte.com.cn">lizhong.jin@zte.com.cn</a>&=
gt;</span> wrote:<br>
<blockquote style=3D"BORDER-LEFT: #ccc 1px solid; MARGIN: 0px 0px 0px 0.8ex=
; PADDING-LEFT: 1ex" class=3D"gmail_quote"><br><font size=3D"2" face=3D"san=
s-serif">Hi all,</font> <br><font size=3D"2" face=3D"sans-serif">During IET=
F 79 Beijing, we made a presentation for HSMP LSP at MPLS session.</font> <=
br>
<font size=3D"2" face=3D"sans-serif">HSMP LSP has several use cases describ=
ed 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 HS=
MP LSP. Please review the draft, and any comments are welcome.</font> <br>
<br><font size=3D"2" face=3D"sans-serif">The draft link is: <a href=3D"http=
://tools.ietf.org/html/draft-jin-jounay-mpls-mldp-hsmp-01" target=3D"_blank=
">http://tools.ietf.org/html/draft-jin-jounay-mpls-mldp-hsmp-01</a></font> =
<br>
<font size=3D"1" face=3D"Arial">=A0</font> <br><font size=3D"2" face=3D"san=
s-serif">Thank you.</font> <br><font size=3D"2" face=3D"sans-serif">Authors=
 of draft-hsmp.</font><br><pre>--------------------------------------------=
------------
ZTE=A0Information=A0Security=A0Notice:=A0The=A0information=A0contained=A0in=
=A0this=A0mail=A0is=A0solely=A0property=A0of=A0the=A0sender&#39;s=A0organiz=
ation.=A0This=A0mail=A0communication=A0is=A0confidential.=A0Recipients=A0na=
med=A0above=A0are=A0obligated=A0to=A0maintain=A0secrecy=A0and=A0are=A0not=
=A0permitted=A0to=A0disclose=A0the=A0contents=A0of=A0this=A0communication=
=A0to=A0others.
This=A0email=A0and=A0any=A0files=A0transmitted=A0with=A0it=A0are=A0confiden=
tial=A0and=A0intended=A0solely=A0for=A0the=A0use=A0of=A0the=A0individual=A0=
or=A0entity=A0to=A0whom=A0they=A0are=A0addressed.=A0If=A0you=A0have=A0recei=
ved=A0this=A0email=A0in=A0error=A0please=A0notify=A0the=A0originator=A0of=
=A0the=A0message.=A0Any=A0views=A0expressed=A0in=A0this=A0message=A0are=A0t=
hose=A0of=A0the=A0individual=A0sender.
This=A0message=A0has=A0been=A0scanned=A0for=A0viruses=A0and=A0Spam=A0by=A0Z=
TE=A0Anti-Spam=A0system.
</pre><br>_______________________________________________<br>mpls mailing l=
ist<br><a href=3D"mailto:mpls@ietf.org">mpls@ietf.org</a><br><a href=3D"htt=
ps://www.ietf.org/mailman/listinfo/mpls" target=3D"_blank">https://www.ietf=
.org/mailman/listinfo/mpls</a><br>
<br></blockquote></div><br>

--000e0cd2e7d4b94e6e0499140252--

From lamberto.sterling@gmail.com  Sat Jan  8 08:17:36 2011
Return-Path: <lamberto.sterling@gmail.com>
X-Original-To: tictoc@core3.amsl.com
Delivered-To: tictoc@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 175F128C15D; Sat,  8 Jan 2011 08:17:36 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.098
X-Spam-Level: 
X-Spam-Status: No, score=-3.098 tagged_above=-999 required=5 tests=[AWL=0.500,  BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Ade8vFNuEYDu; Sat,  8 Jan 2011 08:17:35 -0800 (PST)
Received: from mail-bw0-f44.google.com (mail-bw0-f44.google.com [209.85.214.44]) by core3.amsl.com (Postfix) with ESMTP id 43F6A28C12F; Sat,  8 Jan 2011 08:17:32 -0800 (PST)
Received: by mail-bw0-f44.google.com with SMTP id 12so17996019bwz.31 for <multiple recipients>; Sat, 08 Jan 2011 08:19:40 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:cc:content-type; bh=nNTLDKsCY60mvWe8iOKe6vpGtFWI7JNpuZ0M8VgWtfk=; b=l6UwYNF3eFnwLLLSqvMIsocjsyhplojA1IAb6E94blboZdx2KPNRwlCidpN+H+qQOW GUSWRN+CAjKECAIrfuJpJR3QHys/sIfjzVSk8UXOuxXxAI2on8ZhrtiK547MQXe154J5 qTVJ2MUwQXWJUH9Rj3599I677ncwdR6499r2k=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=W6OvOfLzmWw3IYW/bLCcfUAVD2UgW8BEm82WilG7q5c/s9+46oSHnxgZf9Q36Xrjyj PpBjXwTL87G+MqPqfZPA8q6IF++o/k/lC/qROc+zoYUMd+Yig2L1CisGGJVA7lMLedsW Mgb2FueGLqYO8mZgIBT9xBH4b/JlC8Kc7ywCA=
MIME-Version: 1.0
Received: by 10.204.52.134 with SMTP id i6mr20080302bkg.36.1294503579241; Sat, 08 Jan 2011 08:19:39 -0800 (PST)
Received: by 10.204.98.204 with HTTP; Sat, 8 Jan 2011 08:19:39 -0800 (PST)
In-Reply-To: <mailman.334.1294213956.4673.mpls@ietf.org>
References: <mailman.334.1294213956.4673.mpls@ietf.org>
Date: Sun, 9 Jan 2011 00:19:39 +0800
Message-ID: <AANLkTiktvw6reKYETjkr6NXPhxNPWL5HaT2yEARkEjH4@mail.gmail.com>
From: Lamberto Sterling <lamberto.sterling@gmail.com>
To: maillist.ed@gmail.com, lizhong.jin@zte.com.cn
Content-Type: multipart/alternative; boundary=001636c5bfdd004dd00499581a94
X-Mailman-Approved-At: Sat, 08 Jan 2011 23:06:56 -0800
Cc: l2vpn@ietf.org, mpls@ietf.org, Ice <ice@cisco.com>, tictoc@ietf.org, N.Leymann@telekom.de
Subject: Re: [TICTOC] mpls Digest, Vol 81, Issue 4
X-BeenThere: tictoc@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Timing over IP Connection and Transfer of Clock BOF <tictoc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/tictoc>, <mailto:tictoc-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tictoc>
List-Post: <mailto:tictoc@ietf.org>
List-Help: <mailto:tictoc-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tictoc>, <mailto:tictoc-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 08 Jan 2011 16:17:36 -0000

--001636c5bfdd004dd00499581a94
Content-Type: text/plain; charset=ISO-8859-1

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.
> > --------------------------------------------------------
> >

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

<div>Hi Lizhong, Edward,</div>
<div>It seems that it is a good idea to apply HSMP LSP to VPLS, and the bro=
adcast/unicast/unknow packet would be optimized.=A0However, the path from l=
eaf to root may not be the best path compared with current VPLS using P2P L=
SP, which is not a critical issue.</div>

<div>=A0</div>
<div>Thanks</div>
<div>Lamberto</div>
<div><br>=A0</div>
<div class=3D"gmail_quote">
<blockquote style=3D"BORDER-LEFT: #ccc 1px solid; MARGIN: 0px 0px 0px 0.8ex=
; PADDING-LEFT: 1ex" class=3D"gmail_quote"><br>----------------------------=
--<br><br>Date: Wed, 5 Jan 2011 15:50:45 +0800<br>From: <a href=3D"mailto:l=
izhong.jin@zte.com.cn">lizhong.jin@zte.com.cn</a><br>
Subject: Re: [mpls] Request comments for HSMP LSP<br>To: Ed &lt;<a href=3D"=
mailto:maillist.ed@gmail.com">maillist.ed@gmail.com</a>&gt;<br>Cc: <a href=
=3D"mailto:l2vpn@ietf.org">l2vpn@ietf.org</a>, <a href=3D"mailto:mpls@ietf.=
org">mpls@ietf.org</a>, Ice &lt;<a href=3D"mailto:ice@cisco.com">ice@cisco.=
com</a>&gt;,<br>
=A0 =A0 =A0 =A0<a href=3D"mailto:N.Leymann@telekom.de">N.Leymann@telekom.de=
</a>, =A0 <a href=3D"mailto:tictoc@ietf.org">tictoc@ietf.org</a><br>Message=
-ID:<br>=A0 =A0 =A0 =A0&lt;<a href=3D"mailto:OF4BA0BF75.A883E04C-ON4825780F=
.002802E4-4825780F.002B2AB9@zte.com.cn">OF4BA0BF75.A883E04C-ON4825780F.0028=
02E4-4825780F.002B2AB9@zte.com.cn</a>&gt;<br>
Content-Type: text/plain; charset=3D&quot;us-ascii&quot;<br><br>Hi Edward,<=
br>Thank you for the comments. I add l2vpn maillist in cc list. I agree wit=
h<br>the application you proposed, and in order to improve the scalability =
of<br>
VPLS, P2MP PW multiplexed to HSMP LSP could be used for VPLS. Actually<br>t=
his is a good application case for P2MP PW with reverse path (section<br>4.=
4, draft-ietf-pwe3-p2mp-pw-00). We can add some description about this<br>
use case.<br><br>Regards<br>Lizhong<br><br><br>Ed &lt;<a href=3D"mailto:mai=
llist.ed@gmail.com">maillist.ed@gmail.com</a>&gt; wrote on 2011-01-05 15:05=
:30:<br><br>&gt; Hi Lizhong,<br>&gt;<br>&gt; I think one possible applicati=
on for HSMP LSPs is to reduce the<br>
&gt; overall broadcast/multicast utilization on a VPLS. In current VPLS<br>=
&gt; implementations with a full mesh of P2P LSPs between PEs, broadcast,<b=
r>&gt; multicast and unknown traffic are not efficiently propagated on the<=
br>
&gt; physical links between PEs and Ps.<br>&gt;<br>&gt; In the VPLS impleme=
ntation scenario with HSMP LSPs, each PE signals<br>&gt; a HSMP LSP with it=
self as a root to all other PEs in the VPLS.<br>&gt; Thereafter, all broadc=
ast/multicast/unknown traffic from this PE<br>
&gt; will use this HSMP LSP. Unicast traffic from a particular PE (e.g.<br>=
&gt; PE1) to another PE (e.g. PE2) will be sent from leaf to root using<br>=
&gt; the HSMP LSP where PE2 is the root.<br>&gt;<br>&gt; This simplifies th=
e VPLS implementation by:<br>
&gt; - =A0 =A0 =A0 =A0 =A0Reducing traffic utilization from broadcast, mult=
icast<br>&gt; and unknown traffic<br>&gt; - =A0 =A0 =A0 =A0 =A0Reducing the=
 total number of LSPs maintained by each PE<br>&gt; (i.e. instead of requir=
ing a full mesh of LSPs, now only require one<br>
&gt; HSMP LSP per PE).<br>&gt;<br>&gt; This is similar to the idea expresse=
d in =A0draft-key-l2vpn-etree-<br>&gt; frwk-03.txt (in a more general sense=
).<br>&gt;<br>&gt; What do you think? Would HSMP LSP be suitable for this?<=
br>
&gt;<br>&gt; Regards,<br>&gt; Edward<br>&gt;<br>&gt;<br>&gt;<br>&gt; On Wed=
, Jan 5, 2011 at 5:24 PM, &lt;<a href=3D"mailto:lizhong.jin@zte.com.cn">liz=
hong.jin@zte.com.cn</a>&gt; wrote:<br>&gt;<br>&gt; Hi all,<br>&gt; During I=
ETF 79 Beijing, we made a presentation for HSMP LSP at MPLS<br>
session.<br>&gt; HSMP LSP has several use cases described in the draft, e.g=
, time<br>&gt; synchronization in MPLS network, IPTV scenario, or P2MP PW. =
It would<br>&gt; be appreciated if you could give more scenarios for HSMP L=
SP. Please<br>
&gt; review the draft, and any comments are welcome.<br>&gt;<br>&gt; The dr=
aft link is: <a href=3D"http://tools.ietf.org/html/draft-jin-jounay-mpls-" =
target=3D"_blank">http://tools.ietf.org/html/draft-jin-jounay-mpls-</a><br>
&gt; mldp-hsmp-01<br>&gt;<br>&gt; Thank you.<br>&gt; Authors of draft-hsmp.=
<br>&gt; --------------------------------------------------------<br>&gt;</=
blockquote></div>

--001636c5bfdd004dd00499581a94--

From lamberto.sterling@gmail.com  Sat Jan  8 17:48:10 2011
Return-Path: <lamberto.sterling@gmail.com>
X-Original-To: tictoc@core3.amsl.com
Delivered-To: tictoc@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id E58F428C15D; Sat,  8 Jan 2011 17:48:10 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.348
X-Spam-Level: 
X-Spam-Status: No, score=-3.348 tagged_above=-999 required=5 tests=[AWL=0.250,  BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 7x6leYb-F+Y3; Sat,  8 Jan 2011 17:48:09 -0800 (PST)
Received: from mail-bw0-f44.google.com (mail-bw0-f44.google.com [209.85.214.44]) by core3.amsl.com (Postfix) with ESMTP id EBEC528C0D8; Sat,  8 Jan 2011 17:48:08 -0800 (PST)
Received: by bwz12 with SMTP id 12so18199798bwz.31 for <multiple recipients>; Sat, 08 Jan 2011 17:50:17 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:date:message-id :subject:from:to:cc:content-type; bh=ob5OHdIsb9uPtEvDPOOL3plPHbURByl61wsfe0Sc+bE=; b=TNlC2LWNEMHsAm5x0kQmiE4tEZDOSOwm+XYnObvr7oXld9dNAjbUzeImf3+wBsru8O ZzOuU5jJ4xOYHbCzFULBILtJ6MaZDgwjLegDa5g62pVSrnAb1RrhoascUa05kzbO5gBF OOFe/ysAwqpmJjQxwzNSQiTtUj0KG7JazKaeY=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:cc:content-type; b=AKLqyLvtRexiOv8+JCsHAyTGx4KnIZm+6DQUXHgxov1n9bSldFrTsBe8rzhSHuAul7 w1tUyECrjT4LM958iqdRnSpmyBOGG6vmzPePpPK1EuPOqdyYZHAww1jMjhB6fN720WgH 66XgGIrCRL0QQclk4wlAM5b9OWNP/NnsPrZmE=
MIME-Version: 1.0
Received: by 10.204.100.136 with SMTP id y8mr20327205bkn.171.1294537816129; Sat, 08 Jan 2011 17:50:16 -0800 (PST)
Received: by 10.204.98.204 with HTTP; Sat, 8 Jan 2011 17:50:16 -0800 (PST)
Date: Sun, 9 Jan 2011 02:50:16 +0100
Message-ID: <AANLkTi=CbhP10iM7=wXcb=e9oV0cqwaTKjY7ArZquoW1@mail.gmail.com>
From: Lamberto Sterling <lamberto.sterling@gmail.com>
To: maillist.ed@gmail.com, lizhong.jin@zte.com.cn
Content-Type: multipart/alternative; boundary=001485f6d050adc09f0499601258
X-Mailman-Approved-At: Sat, 08 Jan 2011 23:06:57 -0800
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.9
Precedence: list
List-Id: Timing over IP Connection and Transfer of Clock BOF <tictoc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/tictoc>, <mailto:tictoc-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tictoc>
List-Post: <mailto:tictoc@ietf.org>
List-Help: <mailto:tictoc-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tictoc>, <mailto:tictoc-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 09 Jan 2011 01:48:11 -0000

--001485f6d050adc09f0499601258
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.
>> > --------------------------------------------------------
>> >
>>
>

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

<div>Hi guys,</div>
<div>Sorry for the email subject. Change it now.</div>
<div>=A0</div>
<div>Lamberto<br><br></div>
<div class=3D"gmail_quote">On Sat, Jan 8, 2011 at 5:19 PM, Lamberto Sterlin=
g <span dir=3D"ltr">&lt;<a href=3D"mailto:lamberto.sterling@gmail.com">lamb=
erto.sterling@gmail.com</a>&gt;</span> wrote:<br>
<blockquote style=3D"BORDER-LEFT: #ccc 1px solid; MARGIN: 0px 0px 0px 0.8ex=
; PADDING-LEFT: 1ex" class=3D"gmail_quote">
<div>Hi Lizhong, Edward,</div>
<div>It seems that it is a good idea to apply HSMP LSP to VPLS, and the bro=
adcast/unicast/unknow packet would be optimized.=A0However, the path from l=
eaf to root may not be the best path compared with current VPLS using P2P L=
SP, which is not a critical issue.</div>

<div>=A0</div>
<div>Thanks</div>
<div>Lamberto</div>
<div><br>=A0</div>
<div class=3D"gmail_quote">
<blockquote style=3D"BORDER-LEFT: #ccc 1px solid; MARGIN: 0px 0px 0px 0.8ex=
; PADDING-LEFT: 1ex" class=3D"gmail_quote"><br>----------------------------=
--=20
<div>
<div></div>
<div class=3D"h5"><br><br>Date: Wed, 5 Jan 2011 15:50:45 +0800<br>From: <a =
href=3D"mailto:lizhong.jin@zte.com.cn" target=3D"_blank">lizhong.jin@zte.co=
m.cn</a><br>Subject: Re: [mpls] Request comments for HSMP LSP<br>To: Ed &lt=
;<a href=3D"mailto:maillist.ed@gmail.com" target=3D"_blank">maillist.ed@gma=
il.com</a>&gt;<br>
Cc: <a href=3D"mailto:l2vpn@ietf.org" target=3D"_blank">l2vpn@ietf.org</a>,=
 <a href=3D"mailto:mpls@ietf.org" target=3D"_blank">mpls@ietf.org</a>, Ice =
&lt;<a href=3D"mailto:ice@cisco.com" target=3D"_blank">ice@cisco.com</a>&gt=
;,<br>=A0 =A0 =A0 =A0<a href=3D"mailto:N.Leymann@telekom.de" target=3D"_bla=
nk">N.Leymann@telekom.de</a>, =A0 <a href=3D"mailto:tictoc@ietf.org" target=
=3D"_blank">tictoc@ietf.org</a><br>
Message-ID:<br>=A0 =A0 =A0 =A0&lt;<a href=3D"mailto:OF4BA0BF75.A883E04C-ON4=
825780F.002802E4-4825780F.002B2AB9@zte.com.cn" target=3D"_blank">OF4BA0BF75=
.A883E04C-ON4825780F.002802E4-4825780F.002B2AB9@zte.com.cn</a>&gt;<br>Conte=
nt-Type: text/plain; charset=3D&quot;us-ascii&quot;<br>
<br>Hi Edward,<br>Thank you for the comments. I add l2vpn maillist in cc li=
st. I agree with<br>the application you proposed, and in order to improve t=
he scalability of<br>VPLS, P2MP PW multiplexed to HSMP LSP could be used fo=
r VPLS. Actually<br>
this is a good application case for P2MP PW with reverse path (section<br>4=
.4, draft-ietf-pwe3-p2mp-pw-00). We can add some description about this<br>=
use case.<br><br>Regards<br>Lizhong<br><br><br>Ed &lt;<a href=3D"mailto:mai=
llist.ed@gmail.com" target=3D"_blank">maillist.ed@gmail.com</a>&gt; wrote o=
n 2011-01-05 15:05:30:<br>
<br>&gt; Hi Lizhong,<br>&gt;<br>&gt; I think one possible application for H=
SMP LSPs is to reduce the<br>&gt; overall broadcast/multicast utilization o=
n a VPLS. In current VPLS<br>&gt; implementations with a full mesh of P2P L=
SPs between PEs, broadcast,<br>
&gt; multicast and unknown traffic are not efficiently propagated on the<br=
>&gt; physical links between PEs and Ps.<br>&gt;<br>&gt; In the VPLS implem=
entation scenario with HSMP LSPs, each PE signals<br>&gt; a HSMP LSP with i=
tself as a root to all other PEs in the VPLS.<br>
&gt; Thereafter, all broadcast/multicast/unknown traffic from this PE<br>&g=
t; will use this HSMP LSP. Unicast traffic from a particular PE (e.g.<br>&g=
t; PE1) to another PE (e.g. PE2) will be sent from leaf to root using<br>
&gt; the HSMP LSP where PE2 is the root.<br>&gt;<br>&gt; This simplifies th=
e VPLS implementation by:<br>&gt; - =A0 =A0 =A0 =A0 =A0Reducing traffic uti=
lization from broadcast, multicast<br>&gt; and unknown traffic<br>&gt; - =
=A0 =A0 =A0 =A0 =A0Reducing the total number of LSPs maintained by each PE<=
br>
&gt; (i.e. instead of requiring a full mesh of LSPs, now only require one<b=
r>&gt; HSMP LSP per PE).<br>&gt;<br>&gt; This is similar to the idea expres=
sed in =A0draft-key-l2vpn-etree-<br>&gt; frwk-03.txt (in a more general sen=
se).<br>
&gt;<br>&gt; What do you think? Would HSMP LSP be suitable for this?<br>&gt=
;<br>&gt; Regards,<br>&gt; Edward<br>&gt;<br>&gt;<br>&gt;<br>&gt; On Wed, J=
an 5, 2011 at 5:24 PM, &lt;<a href=3D"mailto:lizhong.jin@zte.com.cn" target=
=3D"_blank">lizhong.jin@zte.com.cn</a>&gt; wrote:<br>
&gt;<br>&gt; Hi all,<br>&gt; During IETF 79 Beijing, we made a presentation=
 for HSMP LSP at MPLS<br>session.<br>&gt; HSMP LSP has several use cases de=
scribed in the draft, e.g, time<br>&gt; synchronization in MPLS network, IP=
TV scenario, or P2MP PW. It would<br>
&gt; be appreciated if you could give more scenarios for HSMP LSP. Please<b=
r>&gt; review the draft, and any comments are welcome.<br>&gt;<br>&gt; The =
draft link is: <a href=3D"http://tools.ietf.org/html/draft-jin-jounay-mpls-=
" target=3D"_blank">http://tools.ietf.org/html/draft-jin-jounay-mpls-</a><b=
r>
&gt; mldp-hsmp-01<br>&gt;<br>&gt; Thank you.<br>&gt; Authors of draft-hsmp.=
<br>&gt; --------------------------------------------------------<br>&gt;</=
div></div></blockquote></div></blockquote></div><br>

--001485f6d050adc09f0499601258--

From odonoghue@isoc.org  Tue Jan 11 20:49:54 2011
Return-Path: <odonoghue@isoc.org>
X-Original-To: tictoc@core3.amsl.com
Delivered-To: tictoc@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 3FD283A690C for <tictoc@core3.amsl.com>; Tue, 11 Jan 2011 20:49:54 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -104.831
X-Spam-Level: 
X-Spam-Status: No, score=-104.831 tagged_above=-999 required=5 tests=[AWL=0.767, BAYES_00=-2.599, GB_I_INVITATION=-2, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id KzgbGVaZnY48 for <tictoc@core3.amsl.com>; Tue, 11 Jan 2011 20:49:52 -0800 (PST)
Received: from smtp135.iad.emailsrvr.com (smtp135.iad.emailsrvr.com [207.97.245.135]) by core3.amsl.com (Postfix) with ESMTP id 8E4A73A6906 for <tictoc@ietf.org>; Tue, 11 Jan 2011 20:49:52 -0800 (PST)
Received: from localhost (localhost.localdomain [127.0.0.1]) by smtp53.relay.iad1a.emailsrvr.com (SMTP Server) with ESMTP id CA41B58EA7 for <tictoc@ietf.org>; Tue, 11 Jan 2011 23:52:10 -0500 (EST)
X-Virus-Scanned: OK
Received: by smtp53.relay.iad1a.emailsrvr.com (Authenticated sender: odonoghue-AT-isoc.org) with ESMTPSA id 65FBD58EA5 for <tictoc@ietf.org>; Tue, 11 Jan 2011 23:52:10 -0500 (EST)
Message-ID: <4D2D337A.2090500@isoc.org>
Date: Tue, 11 Jan 2011 23:52:10 -0500
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.13) Gecko/20101207 Thunderbird/3.1.7
MIME-Version: 1.0
To: tictoc@ietf.org
Content-Type: multipart/alternative; boundary="------------030301060709040909060304"
Subject: [TICTOC] Fwd: Meeting invitation: tictoc
X-BeenThere: tictoc@ietf.org
X-Mailman-Version: 2.1.9
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/listinfo/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, 12 Jan 2011 04:49:54 -0000

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

Folks,

At the Beijing IETF, we decided to continue our monthly teleconferences 
to progress our work efforts. As a result, we will meet next Tuesday, 18 
Jan, at 8:00 am PST / 11:00 EST / 16:00 UTC. The agenda will focus on 
the three current work areas. Below are the Webex details for the 
meeting. If you have any questions, feel free to contact us.

Regards,
Karen

-------- Original Message --------
Subject: 	Meeting invitation: tictoc
Date: 	Thu, 6 Jan 2011 21:34:18 +0000 (GMT)
From: 	IETF Secretariat <messenger@webex.com>
Reply-To: 	amorris@amsl.com
To: 	odonoghue@isoc.org




Hello ,

IETF Secretariat invites you to attend this online meeting.

Topic: tictoc
Date: Tuesday, January 18, 2011
Time: 8:00 am, Pacific Standard Time (San Francisco, GMT-08:00)
Meeting Number: 963 546 302
Meeting Password: (This meeting does not require a password.)


-------------------------------------------------------
To join the online meeting (Now from mobile devices!)
-------------------------------------------------------
1. Go to 
https://workgreen.webex.com/workgreen/j.php?ED=149931342&UID=1197483697&RT=MiM0 
<https://workgreen.webex.com/workgreen/j.php?ED=149931342&UID=1197483697&RT=MiM0> 

2. If requested, enter your name and email address.
3. If a password is required, enter the meeting password: (This meeting 
does not require a password.)
4. Click "Join".

To view in other time zones or languages, please click the link:
https://workgreen.webex.com/workgreen/j.php?ED=149931342&UID=1197483697&ORT=MiM0 
<https://workgreen.webex.com/workgreen/j.php?ED=149931342&UID=1197483697&ORT=MiM0> 


-------------------------------------------------------
To join the audio conference only
-------------------------------------------------------
To receive a call back, provide your phone number when you join the 
meeting, or call the number below and enter the access code.
Call-in toll number (US/Canada): 1-408-792-6300
Global call-in numbers: 
https://workgreen.webex.com/workgreen/globalcallin.php?serviceType=MC&ED=149931342&tollFree=0 
<https://workgreen.webex.com/workgreen/globalcallin.php?serviceType=MC&ED=149931342&tollFree=0> 


Access code:963 546 302

-------------------------------------------------------
For assistance
-------------------------------------------------------
1. Go to https://workgreen.webex.com/workgreen/mc
2. On the left navigation bar, click "Support".

You can contact me at:
amorris@amsl.com <mailto:amorris@amsl.com>
1-510-492-4081

To add this meeting to your calendar program (for example Microsoft 
Outlook), click this link:
https://workgreen.webex.com/workgreen/j.php?ED=149931342&UID=1197483697&ICS=MI&LD=1&RD=2&ST=1&SHA2=/4W4JnAD5wgD6xxoOAY7MeZESknC4JrUPXmtHEYZc7g=&RT=MiM0 
<https://workgreen.webex.com/workgreen/j.php?ED=149931342&UID=1197483697&ICS=MI&LD=1&RD=2&ST=1&SHA2=/4W4JnAD5wgD6xxoOAY7MeZESknC4JrUPXmtHEYZc7g=&RT=MiM0> 


The playback of UCF (Universal Communications Format) rich media files 
requires appropriate players. To view this type of rich media files in 
the meeting, please check whether you have the players installed on your 
computer by going to 
https://workgreen.webex.com/workgreen/systemdiagnosis.php

Sign up for a free trial of WebEx
http://www.webex.com/go/mcemfreetrial

http://www.webex.com

CCP:+14087926300x963546302#

IMPORTANT NOTICE: This WebEx service includes a feature that allows 
audio and any documents and other materials exchanged or viewed during 
the session to be recorded. By joining this session, you automatically 
consent to such recordings. If you do not consent to the recording, 
discuss your concerns with the meeting host prior to the start of the 
recording or do not join the session. Please note that any such 
recordings may be subject to discovery in the event of litigation.


--------------030301060709040909060304
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: 7bit

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
  <head>

    <meta http-equiv="content-type" content="text/html; charset=UTF-8">
  </head>
  <body bgcolor="#ffffff" text="#000000">
    Folks,<br>
    <br>
    At the Beijing IETF, we decided to continue our monthly
    teleconferences to progress our work efforts. As a result, we will
    meet next Tuesday, 18 Jan, at 8:00 am PST / 11:00 EST / 16:00 UTC.
    The agenda will focus on the three current work areas. Below are the
    Webex details for the meeting. If you have any questions, feel free
    to contact us. <br>
    <br>
    Regards,<br>
    Karen<br>
    <br>
    -------- Original Message --------
    <table class="moz-email-headers-table" border="0" cellpadding="0"
      cellspacing="0">
      <tbody>
        <tr>
          <th align="RIGHT" nowrap="nowrap" valign="BASELINE">Subject: </th>
          <td>Meeting invitation: tictoc</td>
        </tr>
        <tr>
          <th align="RIGHT" nowrap="nowrap" valign="BASELINE">Date: </th>
          <td>Thu, 6 Jan 2011 21:34:18 +0000 (GMT)</td>
        </tr>
        <tr>
          <th align="RIGHT" nowrap="nowrap" valign="BASELINE">From: </th>
          <td>IETF Secretariat <a class="moz-txt-link-rfc2396E" href="mailto:messenger@webex.com">&lt;messenger@webex.com&gt;</a></td>
        </tr>
        <tr>
          <th align="RIGHT" nowrap="nowrap" valign="BASELINE">Reply-To:
          </th>
          <td><a class="moz-txt-link-abbreviated" href="mailto:amorris@amsl.com">amorris@amsl.com</a></td>
        </tr>
        <tr>
          <th align="RIGHT" nowrap="nowrap" valign="BASELINE">To: </th>
          <td><a class="moz-txt-link-abbreviated" href="mailto:odonoghue@isoc.org">odonoghue@isoc.org</a></td>
        </tr>
      </tbody>
    </table>
    <br>
    <br>
    <font face="Tahoma, Arial, sans-serif, Helvetica, Geneva" size="2"><br>
      Hello , <br>
      <br>
      IETF Secretariat invites you to attend this online meeting. <br>
      <br>
      Topic: tictoc <br>
      Date: Tuesday, January 18, 2011 <br>
      Time: 8:00 am, Pacific Standard Time (San Francisco, GMT-08:00) <br>
      Meeting Number: 963 546 302 <br>
      Meeting Password: (This meeting does not require a password.) <br>
      <br>
      <br>
      ------------------------------------------------------- <br>
      To join the online meeting (Now from mobile devices!) <br>
      ------------------------------------------------------- <br>
      1. Go to <a moz-do-not-send="true"
href="https://workgreen.webex.com/workgreen/j.php?ED=149931342&amp;UID=1197483697&amp;RT=MiM0"
        target="_blank">https://workgreen.webex.com/workgreen/j.php?ED=149931342&amp;UID=1197483697&amp;RT=MiM0</a>
      <br>
      2. If requested, enter your name and email address. <br>
      3. If a password is required, enter the meeting password: (This
      meeting does not require a password.) <br>
      4. Click "Join". <br>
      <br>
      To view in other time zones or languages, please click the link: <br>
      <a moz-do-not-send="true"
href="https://workgreen.webex.com/workgreen/j.php?ED=149931342&amp;UID=1197483697&amp;ORT=MiM0"
        target="_blank">https://workgreen.webex.com/workgreen/j.php?ED=149931342&amp;UID=1197483697&amp;ORT=MiM0</a>
      <br>
      <br>
      ------------------------------------------------------- <br>
      To join the audio conference only <br>
      ------------------------------------------------------- <br>
      To receive a call back, provide your phone number when you join
      the meeting, or call the number below and enter the access code. <br>
      Call-in toll number (US/Canada): 1-408-792-6300 <br>
      Global call-in numbers: <a moz-do-not-send="true"
href="https://workgreen.webex.com/workgreen/globalcallin.php?serviceType=MC&amp;ED=149931342&amp;tollFree=0"
        target="_blank">https://workgreen.webex.com/workgreen/globalcallin.php?serviceType=MC&amp;ED=149931342&amp;tollFree=0</a>
      <br>
      <br>
      Access code:963 546 302 <br>
      <br>
      ------------------------------------------------------- <br>
      For assistance <br>
      ------------------------------------------------------- <br>
      1. Go to <a moz-do-not-send="true"
        href="https://workgreen.webex.com/workgreen/mc" target="_blank">https://workgreen.webex.com/workgreen/mc</a>
      <br>
      2. On the left navigation bar, click "Support". <br>
      <br>
      You can contact me at: <br>
      <a moz-do-not-send="true" href="mailto:amorris@amsl.com">amorris@amsl.com</a>
      <br>
      1-510-492-4081 <br>
      <br>
      To add this meeting to your calendar program (for example
      Microsoft Outlook), click this link: <br>
      <a moz-do-not-send="true"
href="https://workgreen.webex.com/workgreen/j.php?ED=149931342&amp;UID=1197483697&amp;ICS=MI&amp;LD=1&amp;RD=2&amp;ST=1&amp;SHA2=/4W4JnAD5wgD6xxoOAY7MeZESknC4JrUPXmtHEYZc7g=&amp;RT=MiM0"
        target="_blank">https://workgreen.webex.com/workgreen/j.php?ED=149931342&amp;UID=1197483697&amp;ICS=MI&amp;LD=1&amp;RD=2&amp;ST=1&amp;SHA2=/4W4JnAD5wgD6xxoOAY7MeZESknC4JrUPXmtHEYZc7g=&amp;RT=MiM0</a>
      <br>
      <br>
      The playback of UCF (Universal Communications Format) rich media
      files requires appropriate players. To view this type of rich
      media files in the meeting, please check whether you have the
      players installed on your computer by going to <a
        moz-do-not-send="true"
        href="https://workgreen.webex.com/workgreen/systemdiagnosis.php"
        target="_blank">https://workgreen.webex.com/workgreen/systemdiagnosis.php</a>
      <br>
      <br>
      Sign up for a free trial of WebEx <br>
      <a moz-do-not-send="true"
        href="http://www.webex.com/go/mcemfreetrial" target="_blank">http://www.webex.com/go/mcemfreetrial</a>
      <br>
      <br>
      <a moz-do-not-send="true" href="http://www.webex.com"
        target="_blank">http://www.webex.com</a> <br>
      <br>
      CCP:+14087926300x963546302# <br>
      <br>
      IMPORTANT NOTICE: This WebEx service includes a feature that
      allows audio and any documents and other materials exchanged or
      viewed during the session to be recorded. By joining this session,
      you automatically consent to such recordings. If you do not
      consent to the recording, discuss your concerns with the meeting
      host prior to the start of the recording or do not join the
      session. Please note that any such recordings may be subject to
      discovery in the event of litigation. <br>
    </font><br>
  </body>
</html>

--------------030301060709040909060304--

From manav.bhatia@alcatel-lucent.com  Sat Jan 15 02:53:38 2011
Return-Path: <manav.bhatia@alcatel-lucent.com>
X-Original-To: tictoc@core3.amsl.com
Delivered-To: tictoc@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id E38DB3A6D36 for <tictoc@core3.amsl.com>; Sat, 15 Jan 2011 02:53:38 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.889
X-Spam-Level: 
X-Spam-Status: No, score=-5.889 tagged_above=-999 required=5 tests=[AWL=0.710,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id PNPbaW8Kac02 for <tictoc@core3.amsl.com>; Sat, 15 Jan 2011 02:53:37 -0800 (PST)
Received: from ihemail4.lucent.com (ihemail4.lucent.com [135.245.0.39]) by core3.amsl.com (Postfix) with ESMTP id C9E7E3A6CEE for <tictoc@ietf.org>; Sat, 15 Jan 2011 02:53:37 -0800 (PST)
Received: from inbansmailrelay2.in.alcatel-lucent.com (h135-250-11-33.lucent.com [135.250.11.33]) by ihemail4.lucent.com (8.13.8/IER-o) with ESMTP id p0FAu0GH006978 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL) for <tictoc@ietf.org>; Sat, 15 Jan 2011 04:56:03 -0600 (CST)
Received: from INBANSXCHHUB03.in.alcatel-lucent.com (inbansxchhub03.in.alcatel-lucent.com [135.250.12.80]) by inbansmailrelay2.in.alcatel-lucent.com (8.14.3/8.14.3/GMO) with ESMTP id p0FAtxWm011371 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT) for <tictoc@ietf.org>; Sat, 15 Jan 2011 16:26:00 +0530
Received: from INBANSXCHMBSA1.in.alcatel-lucent.com ([135.250.12.56]) by INBANSXCHHUB03.in.alcatel-lucent.com ([135.250.12.80]) with mapi; Sat, 15 Jan 2011 16:25:59 +0530
From: "Bhatia, Manav (Manav)" <manav.bhatia@alcatel-lucent.com>
To: "tictoc@ietf.org" <tictoc@ietf.org>
Date: Sat, 15 Jan 2011 16:25:59 +0530
Thread-Topic: Transporting PTP messages (1588) over MPLS Networks
Thread-Index: Acu0ostDa6CYok1lRYSvUt8QtgvK+Q==
Message-ID: <7C362EEF9C7896468B36C9B79200D8350CFB0DF1AE@INBANSXCHMBSA1.in.alcatel-lucent.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Scanned-By: MIMEDefang 2.57 on 135.245.2.39
X-Scanned-By: MIMEDefang 2.64 on 135.250.11.33
Subject: [TICTOC] Transporting PTP messages (1588) over MPLS Networks
X-BeenThere: tictoc@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Timing over IP Connection and Transfer of Clock BOF <tictoc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/tictoc>, <mailto:tictoc-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tictoc>
List-Post: <mailto:tictoc@ietf.org>
List-Help: <mailto:tictoc-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tictoc>, <mailto:tictoc-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 15 Jan 2011 10:53:39 -0000

Hi,

We have posted a revised version of draft-davari-tictoc-1588overmpls-01 and=
 would appreciate a feedback from the WG.

The draft is available here:
http://www.ietf.org/id/draft-davari-tictoc-1588overmpls-01.txt

Cheers, Manav

--
Manav Bhatia,
IP Division, Alcatel-Lucent,
Bangalore - India

 =

From swmike@swm.pp.se  Sat Jan 15 03:27:59 2011
Return-Path: <swmike@swm.pp.se>
X-Original-To: tictoc@core3.amsl.com
Delivered-To: tictoc@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 6D8613A6B65 for <tictoc@core3.amsl.com>; Sat, 15 Jan 2011 03:27:59 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.408
X-Spam-Level: 
X-Spam-Status: No, score=-2.408 tagged_above=-999 required=5 tests=[AWL=0.191,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id mPeWA8GusDab for <tictoc@core3.amsl.com>; Sat, 15 Jan 2011 03:27:58 -0800 (PST)
Received: from uplift.swm.pp.se (ipv6.swm.pp.se [IPv6:2a00:801::f]) by core3.amsl.com (Postfix) with ESMTP id 6F26C3A6D29 for <tictoc@ietf.org>; Sat, 15 Jan 2011 03:27:58 -0800 (PST)
Received: by uplift.swm.pp.se (Postfix, from userid 501) id 4D6D39C; Sat, 15 Jan 2011 12:30:24 +0100 (CET)
Received: from localhost (localhost [127.0.0.1]) by uplift.swm.pp.se (Postfix) with ESMTP id 4CC619A; Sat, 15 Jan 2011 12:30:24 +0100 (CET)
Date: Sat, 15 Jan 2011 12:30:24 +0100 (CET)
From: Mikael Abrahamsson <swmike@swm.pp.se>
To: "Bhatia, Manav (Manav)" <manav.bhatia@alcatel-lucent.com>
In-Reply-To: <7C362EEF9C7896468B36C9B79200D8350CFB0DF1AE@INBANSXCHMBSA1.in.alcatel-lucent.com>
Message-ID: <alpine.DEB.1.10.1101151217360.13151@uplift.swm.pp.se>
References: <7C362EEF9C7896468B36C9B79200D8350CFB0DF1AE@INBANSXCHMBSA1.in.alcatel-lucent.com>
User-Agent: Alpine 1.10 (DEB 962 2008-03-14)
Organization: People's Front Against WWW
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
Cc: "tictoc@ietf.org" <tictoc@ietf.org>
Subject: Re: [TICTOC] Transporting PTP messages (1588) over MPLS Networks
X-BeenThere: tictoc@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Timing over IP Connection and Transfer of Clock BOF <tictoc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/tictoc>, <mailto:tictoc-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tictoc>
List-Post: <mailto:tictoc@ietf.org>
List-Help: <mailto:tictoc-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tictoc>, <mailto:tictoc-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 15 Jan 2011 11:27:59 -0000

On Sat, 15 Jan 2011, Bhatia, Manav (Manav) wrote:

> Hi,
>
> We have posted a revised version of draft-davari-tictoc-1588overmpls-01 and would appreciate a feedback from the WG.
>
> The draft is available here:
> http://www.ietf.org/id/draft-davari-tictoc-1588overmpls-01.txt

I am confused by:

"Note that the PTP LSPs MUST only carry PTP messages and MAY carry
    MPLS/MPLS-TP control and management messages such as BFD and LSP-
    Ping."

If it is only allowed to carry PTP messages, how can it be allowed to 
carry other traffic as well? Perhaps rephrasing is in order? "MUST NOT 
carry any traffic other than PTP messages or MPLS control and management 
messages..." ?

In section 10, I think it should be treated as control plane traffic with 
higher priority than what mostly is used for EF? Or is EF (which might 
carry a lot of voice traffic as well) enough?

In section 12-13 there is RSVP-TE and OSPF, what about ISIS?

In 14.3, is "Non-155-aware LSRs" a typo and should be "non-1588-aware" ?

-- 
Mikael Abrahamsson    email: swmike@swm.pp.se

From manav.bhatia@alcatel-lucent.com  Sat Jan 15 15:23:59 2011
Return-Path: <manav.bhatia@alcatel-lucent.com>
X-Original-To: tictoc@core3.amsl.com
Delivered-To: tictoc@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 512E83A6B8A for <tictoc@core3.amsl.com>; Sat, 15 Jan 2011 15:23:59 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.916
X-Spam-Level: 
X-Spam-Status: No, score=-5.916 tagged_above=-999 required=5 tests=[AWL=0.683,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id PQJykdd7oYIl for <tictoc@core3.amsl.com>; Sat, 15 Jan 2011 15:23:58 -0800 (PST)
Received: from ihemail2.lucent.com (ihemail2.lucent.com [135.245.0.35]) by core3.amsl.com (Postfix) with ESMTP id 4CA1B3A6B69 for <tictoc@ietf.org>; Sat, 15 Jan 2011 15:23:57 -0800 (PST)
Received: from inbansmailrelay1.in.alcatel-lucent.com (h135-250-11-31.lucent.com [135.250.11.31]) by ihemail2.lucent.com (8.13.8/IER-o) with ESMTP id p0FNQNcu018575 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Sat, 15 Jan 2011 17:26:26 -0600 (CST)
Received: from INBANSXCHHUB02.in.alcatel-lucent.com (inbansxchhub02.in.alcatel-lucent.com [135.250.12.35]) by inbansmailrelay1.in.alcatel-lucent.com (8.14.3/8.14.3/GMO) with ESMTP id p0FNQGAj030114 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Sun, 16 Jan 2011 04:56:18 +0530
Received: from INBANSXCHMBSA1.in.alcatel-lucent.com ([135.250.12.56]) by INBANSXCHHUB02.in.alcatel-lucent.com ([135.250.12.35]) with mapi; Sun, 16 Jan 2011 04:56:16 +0530
From: "Bhatia, Manav (Manav)" <manav.bhatia@alcatel-lucent.com>
To: Mikael Abrahamsson <swmike@swm.pp.se>
Date: Sun, 16 Jan 2011 04:56:15 +0530
Thread-Topic: [TICTOC] Transporting PTP messages (1588) over MPLS Networks
Thread-Index: Acu0p6EcYROudUk1ROKN1s0tBAi9vQAYv4tw
Message-ID: <7C362EEF9C7896468B36C9B79200D8350CFB0DF1C3@INBANSXCHMBSA1.in.alcatel-lucent.com>
References: <7C362EEF9C7896468B36C9B79200D8350CFB0DF1AE@INBANSXCHMBSA1.in.alcatel-lucent.com> <alpine.DEB.1.10.1101151217360.13151@uplift.swm.pp.se>
In-Reply-To: <alpine.DEB.1.10.1101151217360.13151@uplift.swm.pp.se>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Scanned-By: MIMEDefang 2.57 on 135.245.2.35
X-Scanned-By: MIMEDefang 2.64 on 135.250.11.31
Cc: "tictoc@ietf.org" <tictoc@ietf.org>
Subject: Re: [TICTOC] Transporting PTP messages (1588) over MPLS Networks
X-BeenThere: tictoc@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Timing over IP Connection and Transfer of Clock BOF <tictoc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/tictoc>, <mailto:tictoc-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tictoc>
List-Post: <mailto:tictoc@ietf.org>
List-Help: <mailto:tictoc-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tictoc>, <mailto:tictoc-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 15 Jan 2011 23:23:59 -0000

Hi Mikael,

Thanks for the comments.
=20
> I am confused by:
>=20
> "Note that the PTP LSPs MUST only carry PTP messages and MAY carry
>     MPLS/MPLS-TP control and management messages such as BFD and LSP-
>     Ping."
>=20
> If it is only allowed to carry PTP messages, how can it be allowed to=20
> carry other traffic as well? Perhaps rephrasing is in order?=20
> "MUST NOT=20
> carry any traffic other than PTP messages or MPLS control and=20
> management=20
> messages..." ?

We do explain this in section 9 that one MAY need to carry some OAM and man=
agement messages to manage these PTP LSPs and PTP PWs.=20

>=20
> In section 10, I think it should be treated as control plane=20
> traffic with=20
> higher priority than what mostly is used for EF? Or is EF=20
> (which might=20
> carry a lot of voice traffic as well) enough?

EF is better than the default. I don't think we can mandate AF since that w=
ould require operators to provide assurance of delivery as long as the traf=
fic is not exceeding certain rate. Now, how does define that rate?

>=20
> In section 12-13 there is RSVP-TE and OSPF, what about ISIS?

Changes are similar to IS-IS and will get into the next version.

>=20
> In 14.3, is "Non-155-aware LSRs" a typo and should be=20
> "non-1588-aware" ?

Thanks for catching this. Again, will get into the next version.

Cheers, Manav

From swmike@swm.pp.se  Sat Jan 15 22:02:55 2011
Return-Path: <swmike@swm.pp.se>
X-Original-To: tictoc@core3.amsl.com
Delivered-To: tictoc@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 9C96C3A6D05 for <tictoc@core3.amsl.com>; Sat, 15 Jan 2011 22:02:55 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.411
X-Spam-Level: 
X-Spam-Status: No, score=-2.411 tagged_above=-999 required=5 tests=[AWL=0.188,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 0BJnc-FxAAwz for <tictoc@core3.amsl.com>; Sat, 15 Jan 2011 22:02:54 -0800 (PST)
Received: from uplift.swm.pp.se (ipv6.swm.pp.se [IPv6:2a00:801::f]) by core3.amsl.com (Postfix) with ESMTP id 4A7EB3A6C47 for <tictoc@ietf.org>; Sat, 15 Jan 2011 22:02:53 -0800 (PST)
Received: by uplift.swm.pp.se (Postfix, from userid 501) id 7DDF39C; Sun, 16 Jan 2011 07:05:22 +0100 (CET)
Received: from localhost (localhost [127.0.0.1]) by uplift.swm.pp.se (Postfix) with ESMTP id 79F2F9A; Sun, 16 Jan 2011 07:05:22 +0100 (CET)
Date: Sun, 16 Jan 2011 07:05:22 +0100 (CET)
From: Mikael Abrahamsson <swmike@swm.pp.se>
To: "Bhatia, Manav (Manav)" <manav.bhatia@alcatel-lucent.com>
In-Reply-To: <7C362EEF9C7896468B36C9B79200D8350CFB0DF1C3@INBANSXCHMBSA1.in.alcatel-lucent.com>
Message-ID: <alpine.DEB.1.10.1101160659310.13151@uplift.swm.pp.se>
References: <7C362EEF9C7896468B36C9B79200D8350CFB0DF1AE@INBANSXCHMBSA1.in.alcatel-lucent.com> <alpine.DEB.1.10.1101151217360.13151@uplift.swm.pp.se> <7C362EEF9C7896468B36C9B79200D8350CFB0DF1C3@INBANSXCHMBSA1.in.alcatel-lucent.com>
User-Agent: Alpine 1.10 (DEB 962 2008-03-14)
Organization: People's Front Against WWW
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
Cc: "tictoc@ietf.org" <tictoc@ietf.org>
Subject: Re: [TICTOC] Transporting PTP messages (1588) over MPLS Networks
X-BeenThere: tictoc@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Timing over IP Connection and Transfer of Clock BOF <tictoc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/tictoc>, <mailto:tictoc-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tictoc>
List-Post: <mailto:tictoc@ietf.org>
List-Help: <mailto:tictoc-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tictoc>, <mailto:tictoc-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 16 Jan 2011 06:02:55 -0000

On Sun, 16 Jan 2011, Bhatia, Manav (Manav) wrote:

> We do explain this in section 9 that one MAY need to carry some OAM and 
> management messages to manage these PTP LSPs and PTP PWs.

Yes, I noticed. I still think that saying "X MUST be 4 (but it may also be 
3)" is a weird thing to say.

>> In section 10, I think it should be treated as control plane traffic 
>> with higher priority than what mostly is used for EF? Or is EF (which 
>> might carry a lot of voice traffic as well) enough?
>
> EF is better than the default. I don't think we can mandate AF since 
> that would require operators to provide assurance of delivery as long as 
> the traffic is not exceeding certain rate. Now, how does define that 
> rate?

I think you misunderstood.

In my world, control plane traffic (originated by the router itself) may 
have higher outgoing QoS priority than EF. AF is definitely further down 
the list of priorities, both when it comes to jitter and packet loss 
handling.

On Cisco for instance, people usually use the MQC "priority" command for 
EF, which means it's a low latency queue which is always emptied first, 
then there might be some round robin handling of other queues. Is this 
queue enough, or is it better to just handle it with low drop probability 
and just make sure the time information in the packet is accurate and the 
delay of the packet is of little importance?

-- 
Mikael Abrahamsson    email: swmike@swm.pp.se

From manav.bhatia@alcatel-lucent.com  Sun Jan 16 03:29:13 2011
Return-Path: <manav.bhatia@alcatel-lucent.com>
X-Original-To: tictoc@core3.amsl.com
Delivered-To: tictoc@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id ED23A3A6E49 for <tictoc@core3.amsl.com>; Sun, 16 Jan 2011 03:29:12 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.941
X-Spam-Level: 
X-Spam-Status: No, score=-5.941 tagged_above=-999 required=5 tests=[AWL=0.658,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id vBcXY1naFg6I for <tictoc@core3.amsl.com>; Sun, 16 Jan 2011 03:29:11 -0800 (PST)
Received: from ihemail4.lucent.com (ihemail4.lucent.com [135.245.0.39]) by core3.amsl.com (Postfix) with ESMTP id 7EFA73A6D2B for <tictoc@ietf.org>; Sun, 16 Jan 2011 03:29:11 -0800 (PST)
Received: from inbansmailrelay2.in.alcatel-lucent.com (h135-250-11-33.lucent.com [135.250.11.33]) by ihemail4.lucent.com (8.13.8/IER-o) with ESMTP id p0GBVbID023155 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Sun, 16 Jan 2011 05:31:40 -0600 (CST)
Received: from INBANSXCHHUB03.in.alcatel-lucent.com (inbansxchhub03.in.alcatel-lucent.com [135.250.12.80]) by inbansmailrelay2.in.alcatel-lucent.com (8.14.3/8.14.3/GMO) with ESMTP id p0GBVaLc009075 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Sun, 16 Jan 2011 17:01:36 +0530
Received: from INBANSXCHMBSA1.in.alcatel-lucent.com ([135.250.12.56]) by INBANSXCHHUB03.in.alcatel-lucent.com ([135.250.12.80]) with mapi; Sun, 16 Jan 2011 17:01:36 +0530
From: "Bhatia, Manav (Manav)" <manav.bhatia@alcatel-lucent.com>
To: Mikael Abrahamsson <swmike@swm.pp.se>
Date: Sun, 16 Jan 2011 17:01:33 +0530
Thread-Topic: [TICTOC] Transporting PTP messages (1588) over MPLS Networks
Thread-Index: Acu1Q2IWY7px9AQKRu+wEAlWnFxG6AALMeww
Message-ID: <7C362EEF9C7896468B36C9B79200D8350CFB0DF1DA@INBANSXCHMBSA1.in.alcatel-lucent.com>
References: <7C362EEF9C7896468B36C9B79200D8350CFB0DF1AE@INBANSXCHMBSA1.in.alcatel-lucent.com> <alpine.DEB.1.10.1101151217360.13151@uplift.swm.pp.se> <7C362EEF9C7896468B36C9B79200D8350CFB0DF1C3@INBANSXCHMBSA1.in.alcatel-lucent.com> <alpine.DEB.1.10.1101160659310.13151@uplift.swm.pp.se>
In-Reply-To: <alpine.DEB.1.10.1101160659310.13151@uplift.swm.pp.se>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Scanned-By: MIMEDefang 2.57 on 135.245.2.39
X-Scanned-By: MIMEDefang 2.64 on 135.250.11.33
Cc: "tictoc@ietf.org" <tictoc@ietf.org>
Subject: Re: [TICTOC] Transporting PTP messages (1588) over MPLS Networks
X-BeenThere: tictoc@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Timing over IP Connection and Transfer of Clock BOF <tictoc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/tictoc>, <mailto:tictoc-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tictoc>
List-Post: <mailto:tictoc@ietf.org>
List-Help: <mailto:tictoc-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tictoc>, <mailto:tictoc-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 16 Jan 2011 11:29:13 -0000

Hi Mikael,

>=20
> Yes, I noticed. I still think that saying "X MUST be 4 (but=20
> it may also be=20
> 3)" is a weird thing to say.

Would it work if we rephrase the text in section 4 as follows:

Old:

Note that the PTP LSPs MUST only carry PTP messages and MAY carry MPLS/MPLS=
-TP control and management messages such as BFD and LSP-Ping.

New:

We should be selective about the kind of traffic that flows over PTP LSPs. =
All PTP messages MUST only be sent on the PTP LSP. It MAY, in addition to t=
his also carry MPLS/MPLS-TP control and management messages such as BFD and=
 LSP-Ping.

>=20
> >> In section 10, I think it should be treated as control=20
> plane traffic=20
> >> with higher priority than what mostly is used for EF? Or=20
> is EF (which=20
> >> might carry a lot of voice traffic as well) enough?
> >
> > EF is better than the default. I don't think we can mandate=20
> AF since=20
> > that would require operators to provide assurance of=20
> delivery as long as=20
> > the traffic is not exceeding certain rate. Now, how does=20
> define that=20
> > rate?
>=20
> I think you misunderstood.
>=20
> In my world, control plane traffic (originated by the router=20
> itself) may=20
> have higher outgoing QoS priority than EF. AF is definitely=20

Yes, its probably NC.

> further down=20
> the list of priorities, both when it comes to jitter and packet loss=20
> handling.
>=20
> On Cisco for instance, people usually use the MQC "priority"=20
> command for=20
> EF, which means it's a low latency queue which is always=20
> emptied first,=20
> then there might be some round robin handling of other=20
> queues. Is this=20
> queue enough, or is it better to just handle it with low drop=20
> probability=20
> and just make sure the time information in the packet is=20
> accurate and the=20
> delay of the packet is of little importance?

I am still not sure if I understood your point. Are you suggesting that all=
 such packets be marked as NC?=20

Cheers, Manav

>=20
> --=20
> Mikael Abrahamsson    email: swmike@swm.pp.se
> =

From swmike@swm.pp.se  Sun Jan 16 03:49:22 2011
Return-Path: <swmike@swm.pp.se>
X-Original-To: tictoc@core3.amsl.com
Delivered-To: tictoc@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id C6DDD3A6E4C for <tictoc@core3.amsl.com>; Sun, 16 Jan 2011 03:49:22 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.413
X-Spam-Level: 
X-Spam-Status: No, score=-2.413 tagged_above=-999 required=5 tests=[AWL=0.186,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id tSaWU2F-PRfg for <tictoc@core3.amsl.com>; Sun, 16 Jan 2011 03:49:21 -0800 (PST)
Received: from uplift.swm.pp.se (ipv6.swm.pp.se [IPv6:2a00:801::f]) by core3.amsl.com (Postfix) with ESMTP id 0D9FF3A6CAA for <tictoc@ietf.org>; Sun, 16 Jan 2011 03:49:20 -0800 (PST)
Received: by uplift.swm.pp.se (Postfix, from userid 501) id 7CF9F9C; Sun, 16 Jan 2011 12:51:50 +0100 (CET)
Received: from localhost (localhost [127.0.0.1]) by uplift.swm.pp.se (Postfix) with ESMTP id 7A0EB9A; Sun, 16 Jan 2011 12:51:50 +0100 (CET)
Date: Sun, 16 Jan 2011 12:51:50 +0100 (CET)
From: Mikael Abrahamsson <swmike@swm.pp.se>
To: "Bhatia, Manav (Manav)" <manav.bhatia@alcatel-lucent.com>
In-Reply-To: <7C362EEF9C7896468B36C9B79200D8350CFB0DF1DA@INBANSXCHMBSA1.in.alcatel-lucent.com>
Message-ID: <alpine.DEB.1.10.1101161244010.13151@uplift.swm.pp.se>
References: <7C362EEF9C7896468B36C9B79200D8350CFB0DF1AE@INBANSXCHMBSA1.in.alcatel-lucent.com> <alpine.DEB.1.10.1101151217360.13151@uplift.swm.pp.se> <7C362EEF9C7896468B36C9B79200D8350CFB0DF1C3@INBANSXCHMBSA1.in.alcatel-lucent.com> <alpine.DEB.1.10.1101160659310.13151@uplift.swm.pp.se> <7C362EEF9C7896468B36C9B79200D8350CFB0DF1DA@INBANSXCHMBSA1.in.alcatel-lucent.com>
User-Agent: Alpine 1.10 (DEB 962 2008-03-14)
Organization: People's Front Against WWW
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
Cc: "tictoc@ietf.org" <tictoc@ietf.org>
Subject: Re: [TICTOC] Transporting PTP messages (1588) over MPLS Networks
X-BeenThere: tictoc@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Timing over IP Connection and Transfer of Clock BOF <tictoc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/tictoc>, <mailto:tictoc-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tictoc>
List-Post: <mailto:tictoc@ietf.org>
List-Help: <mailto:tictoc-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tictoc>, <mailto:tictoc-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 16 Jan 2011 11:49:22 -0000

On Sun, 16 Jan 2011, Bhatia, Manav (Manav) wrote:

> "We should be selective about the kind of traffic that flows over PTP 
> LSPs. All PTP messages MUST only be sent on the PTP LSP. It MAY, in 
> addition to this also carry MPLS/MPLS-TP control and management messages 
> such as BFD and LSP-Ping."

Suggestion:

"We should be selective about the kind of traffic that flows over PTP LSPs 
as these will be handled as a special case by the LSR. The only LSP user 
plane traffic MUST be PTP, but the LSP MAY also carry essential 
MPLS/MPLS-TP control plane traffic such as BFD and LSP-Ping."

Your suggestion above is fine as well, I don't have any major objections 
to it.

> I am still not sure if I understood your point. Are you suggesting that 
> all such packets be marked as NC?

I'm not talking marking at all.

When the LSR wants to send out the PTP message, should it go into the 
normal output queuing mechanism or should it just be sent out first thing, 
regardless of what the queuing configuration is (in that case, it'll beat 
EF when it comes to "importance" for output queuing).

-- 
Mikael Abrahamsson    email: swmike@swm.pp.se

From manav.bhatia@alcatel-lucent.com  Sun Jan 16 03:56:35 2011
Return-Path: <manav.bhatia@alcatel-lucent.com>
X-Original-To: tictoc@core3.amsl.com
Delivered-To: tictoc@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 7701B3A6E49 for <tictoc@core3.amsl.com>; Sun, 16 Jan 2011 03:56:35 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.965
X-Spam-Level: 
X-Spam-Status: No, score=-5.965 tagged_above=-999 required=5 tests=[AWL=0.634,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id rS7H0ZBNLT7s for <tictoc@core3.amsl.com>; Sun, 16 Jan 2011 03:56:34 -0800 (PST)
Received: from ihemail3.lucent.com (ihemail3.lucent.com [135.245.0.37]) by core3.amsl.com (Postfix) with ESMTP id 967303A6CAA for <tictoc@ietf.org>; Sun, 16 Jan 2011 03:56:34 -0800 (PST)
Received: from inbansmailrelay2.in.alcatel-lucent.com (h135-250-11-33.lucent.com [135.250.11.33]) by ihemail3.lucent.com (8.13.8/IER-o) with ESMTP id p0GBx1RJ008022 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Sun, 16 Jan 2011 05:59:04 -0600 (CST)
Received: from INBANSXCHHUB03.in.alcatel-lucent.com (inbansxchhub03.in.alcatel-lucent.com [135.250.12.80]) by inbansmailrelay2.in.alcatel-lucent.com (8.14.3/8.14.3/GMO) with ESMTP id p0GBx05G009606 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Sun, 16 Jan 2011 17:29:00 +0530
Received: from INBANSXCHMBSA1.in.alcatel-lucent.com ([135.250.12.56]) by INBANSXCHHUB03.in.alcatel-lucent.com ([135.250.12.80]) with mapi; Sun, 16 Jan 2011 17:29:00 +0530
From: "Bhatia, Manav (Manav)" <manav.bhatia@alcatel-lucent.com>
To: Mikael Abrahamsson <swmike@swm.pp.se>
Date: Sun, 16 Jan 2011 17:28:57 +0530
Thread-Topic: [TICTOC] Transporting PTP messages (1588) over MPLS Networks
Thread-Index: Acu1c8ievd2+XtldR/yZmEc9juhm1gAACjTA
Message-ID: <7C362EEF9C7896468B36C9B79200D8350CFB0DF1DD@INBANSXCHMBSA1.in.alcatel-lucent.com>
References: <7C362EEF9C7896468B36C9B79200D8350CFB0DF1AE@INBANSXCHMBSA1.in.alcatel-lucent.com> <alpine.DEB.1.10.1101151217360.13151@uplift.swm.pp.se> <7C362EEF9C7896468B36C9B79200D8350CFB0DF1C3@INBANSXCHMBSA1.in.alcatel-lucent.com> <alpine.DEB.1.10.1101160659310.13151@uplift.swm.pp.se> <7C362EEF9C7896468B36C9B79200D8350CFB0DF1DA@INBANSXCHMBSA1.in.alcatel-lucent.com> <alpine.DEB.1.10.1101161244010.13151@uplift.swm.pp.se>
In-Reply-To: <alpine.DEB.1.10.1101161244010.13151@uplift.swm.pp.se>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Scanned-By: MIMEDefang 2.57 on 135.245.2.37
X-Scanned-By: MIMEDefang 2.64 on 135.250.11.33
Cc: "tictoc@ietf.org" <tictoc@ietf.org>
Subject: Re: [TICTOC] Transporting PTP messages (1588) over MPLS Networks
X-BeenThere: tictoc@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Timing over IP Connection and Transfer of Clock BOF <tictoc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/tictoc>, <mailto:tictoc-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tictoc>
List-Post: <mailto:tictoc@ietf.org>
List-Help: <mailto:tictoc-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tictoc>, <mailto:tictoc-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 16 Jan 2011 11:56:35 -0000

>=20
> "We should be selective about the kind of traffic that flows=20
> over PTP LSPs=20
> as these will be handled as a special case by the LSR. The=20
> only LSP user=20
> plane traffic MUST be PTP, but the LSP MAY also carry essential=20
> MPLS/MPLS-TP control plane traffic such as BFD and LSP-Ping."
>=20
> Your suggestion above is fine as well, I don't have any major=20
> objections=20
> to it.

And neither do I with your text.=20

Will update the next revision with the above.

>=20
> > I am still not sure if I understood your point. Are you=20
> suggesting that=20
> > all such packets be marked as NC?
>=20
> I'm not talking marking at all.
>=20
> When the LSR wants to send out the PTP message, should it go into the=20
> normal output queuing mechanism or should it just be sent out=20
> first thing,=20
> regardless of what the queuing configuration is (in that=20
> case, it'll beat=20
> EF when it comes to "importance" for output queuing).

Ok, I think I understand what youre alluding to. You will like implementati=
ons to send out the PTP message using the highest priority queue that's ava=
ilable at the egress. Is this correct?

If this is what you want, then I would disagree. While I understand the urg=
ency to send out these packets, its way to less than all the other control =
traffic that needs to be sent (like BFD, LACP, EFM, etc) out.=20

Cheers, Manav

>=20
> --=20
> Mikael Abrahamsson    email: swmike@swm.pp.se
> =

From tommy.cook@calnexsol.com  Mon Jan 17 03:23:12 2011
Return-Path: <tommy.cook@calnexsol.com>
X-Original-To: tictoc@core3.amsl.com
Delivered-To: tictoc@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id A2B0A3A6E71 for <tictoc@core3.amsl.com>; Mon, 17 Jan 2011 03:23:12 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.8
X-Spam-Level: 
X-Spam-Status: No, score=-0.8 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_DE=0.35, MSGID_MULTIPLE_AT=1.449]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Y9dshqHf3JJy for <tictoc@core3.amsl.com>; Mon, 17 Jan 2011 03:23:11 -0800 (PST)
Received: from moutng.kundenserver.de (moutng.kundenserver.de [212.227.17.9]) by core3.amsl.com (Postfix) with ESMTP id 6765B3A6D44 for <tictoc@ietf.org>; Mon, 17 Jan 2011 03:23:11 -0800 (PST)
Received: from TommyCookPC (easypleasy-adsl.demon.co.uk [62.49.5.153]) by mrelayeu.kundenserver.de (node=mrbap1) with ESMTP (Nemesis) id 0MK3ZF-1Pdxjc2A7x-001ADV; Mon, 17 Jan 2011 12:25:41 +0100
From: "Tommy Cook" <tommy.cook@calnexsol.com>
To: "'Bhatia, Manav \(Manav\)'" <manav.bhatia@alcatel-lucent.com>
References: <7C362EEF9C7896468B36C9B79200D8350CFB0DF1AE@INBANSXCHMBSA1.in.alcatel-lucent.com>
In-Reply-To: <7C362EEF9C7896468B36C9B79200D8350CFB0DF1AE@INBANSXCHMBSA1.in.alcatel-lucent.com>
Date: Mon, 17 Jan 2011 11:25:40 -0000
Message-ID: <003001cbb639$461a4930$d24edb90$@cook@calnexsol.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: Acu0ostDa6CYok1lRYSvUt8QtgvK+QBlbpeA
Content-Language: en-gb
X-Provags-ID: V02:K0:Ua+SZ5QeqLyz/BHL0Ta3x5bEQ/biVcN6dQfKHj4eCxG Hq0KDP6TMHAbe/fCoQQnAh6een7abnD43Qttwe1APg879ORBie Z0cEITDVJiIR2NdxSK6Le6CRQsObO1SjFIa5Eb/vNdykr2urrL hu70otAR6kPfme2Uw9OTBPZ1Ppy4VLRpIS22yfHLsy0Hgx0Baw kphU3mjQsuv8TBBEyxIzeHm17SiDs3/kiK4Y9OlnRM=
Cc: tictoc@ietf.org
Subject: Re: [TICTOC] Transporting PTP messages (1588) over MPLS Networks
X-BeenThere: tictoc@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Timing over IP Connection and Transfer of Clock BOF <tictoc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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, 17 Jan 2011 11:23:12 -0000

Hi Manav,

In the Terminology section, you list "BC: Border Clock, is a .....".  In
IEEE1588 what you describe is, I believe, referred to as a Boundary =
Clock.
Did you use a different term for a specific reason or is it simply the
terminology needs to be completely aligned?

Regards,
Tommy


=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D
Tommy Cook
CEO=20
Calnex Solutions Ltd
Tel.:=A0=A0 +44 (0) 1506-671-416
Mob.:=A0+44 (0) 770-4894-128
email:=A0=A0=A0 tommy.cook@calnexsol.com
website: www.calnexsol.com
=A0
Calnex Solutions Limited is registered in Scotland: SC299625



-----Original Message-----
From: tictoc-bounces@ietf.org [mailto:tictoc-bounces@ietf.org] On Behalf =
Of
Bhatia, Manav (Manav)
Sent: 15 January 2011 10:56
To: tictoc@ietf.org
Subject: [TICTOC] Transporting PTP messages (1588) over MPLS Networks

Hi,

We have posted a revised version of draft-davari-tictoc-1588overmpls-01 =
and
would appreciate a feedback from the WG.

The draft is available here:
http://www.ietf.org/id/draft-davari-tictoc-1588overmpls-01.txt

Cheers, Manav

--
Manav Bhatia,
IP Division, Alcatel-Lucent,
Bangalore - India

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


From manav.bhatia@alcatel-lucent.com  Mon Jan 17 04:32:39 2011
Return-Path: <manav.bhatia@alcatel-lucent.com>
X-Original-To: tictoc@core3.amsl.com
Delivered-To: tictoc@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id BA3E83A6ED5 for <tictoc@core3.amsl.com>; Mon, 17 Jan 2011 04:32:39 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.987
X-Spam-Level: 
X-Spam-Status: No, score=-5.987 tagged_above=-999 required=5 tests=[AWL=0.612,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id LWP1fwV4AOwa for <tictoc@core3.amsl.com>; Mon, 17 Jan 2011 04:32:38 -0800 (PST)
Received: from ihemail3.lucent.com (ihemail3.lucent.com [135.245.0.37]) by core3.amsl.com (Postfix) with ESMTP id 75FE43A6E98 for <tictoc@ietf.org>; Mon, 17 Jan 2011 04:32:37 -0800 (PST)
Received: from inbansmailrelay1.in.alcatel-lucent.com (h135-250-11-31.lucent.com [135.250.11.31]) by ihemail3.lucent.com (8.13.8/IER-o) with ESMTP id p0HCZ5bM010110 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Mon, 17 Jan 2011 06:35:08 -0600 (CST)
Received: from INBANSXCHHUB02.in.alcatel-lucent.com (inbansxchhub02.in.alcatel-lucent.com [135.250.12.35]) by inbansmailrelay1.in.alcatel-lucent.com (8.14.3/8.14.3/GMO) with ESMTP id p0HCZ3ph003729 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Mon, 17 Jan 2011 18:05:04 +0530
Received: from INBANSXCHMBSA1.in.alcatel-lucent.com ([135.250.12.56]) by INBANSXCHHUB02.in.alcatel-lucent.com ([135.250.12.35]) with mapi; Mon, 17 Jan 2011 18:05:04 +0530
From: "Bhatia, Manav (Manav)" <manav.bhatia@alcatel-lucent.com>
To: Tommy Cook <tommy.cook@calnexsol.com>
Date: Mon, 17 Jan 2011 18:05:02 +0530
Thread-Topic: [TICTOC] Transporting PTP messages (1588) over MPLS Networks
Thread-Index: Acu0ostDa6CYok1lRYSvUt8QtgvK+QBlbpeAAAKX1hA=
Message-ID: <7C362EEF9C7896468B36C9B79200D8350CFB0DF467@INBANSXCHMBSA1.in.alcatel-lucent.com>
References: <7C362EEF9C7896468B36C9B79200D8350CFB0DF1AE@INBANSXCHMBSA1.in.alcatel-lucent.com> <003001cbb639$461a4930$d24edb90$@cook@calnexsol.com>
In-Reply-To: <003001cbb639$461a4930$d24edb90$@cook@calnexsol.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Scanned-By: MIMEDefang 2.57 on 135.245.2.37
X-Scanned-By: MIMEDefang 2.64 on 135.250.11.31
Cc: "tictoc@ietf.org" <tictoc@ietf.org>
Subject: Re: [TICTOC] Transporting PTP messages (1588) over MPLS Networks
X-BeenThere: tictoc@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Timing over IP Connection and Transfer of Clock BOF <tictoc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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, 17 Jan 2011 12:32:39 -0000

Hi Tommy,

This is a typo and will be fixed in the next revision.

Cheers, Manav=20

> -----Original Message-----
> From: Tommy Cook [mailto:tommy.cook@calnexsol.com]=20
> Sent: Monday, January 17, 2011 4.56 PM
> To: Bhatia, Manav (Manav)
> Cc: tictoc@ietf.org
> Subject: RE: [TICTOC] Transporting PTP messages (1588) over=20
> MPLS Networks
>=20
> Hi Manav,
>=20
> In the Terminology section, you list "BC: Border Clock, is a=20
> .....".  In
> IEEE1588 what you describe is, I believe, referred to as a=20
> Boundary Clock.
> Did you use a different term for a specific reason or is it simply the
> terminology needs to be completely aligned?
>=20
> Regards,
> Tommy
>=20
>=20
> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
> Tommy Cook
> CEO=20
> Calnex Solutions Ltd
> Tel.:=A0=A0 +44 (0) 1506-671-416
> Mob.:=A0+44 (0) 770-4894-128
> email:=A0=A0=A0 tommy.cook@calnexsol.com
> website: www.calnexsol.com
> =A0
> Calnex Solutions Limited is registered in Scotland: SC299625
>=20
>=20
>=20
> -----Original Message-----
> From: tictoc-bounces@ietf.org=20
> [mailto:tictoc-bounces@ietf.org] On Behalf Of
> Bhatia, Manav (Manav)
> Sent: 15 January 2011 10:56
> To: tictoc@ietf.org
> Subject: [TICTOC] Transporting PTP messages (1588) over MPLS Networks
>=20
> Hi,
>=20
> We have posted a revised version of=20
> draft-davari-tictoc-1588overmpls-01 and
> would appreciate a feedback from the WG.
>=20
> The draft is available here:
> http://www.ietf.org/id/draft-davari-tictoc-1588overmpls-01.txt
>=20
> Cheers, Manav
>=20
> --
> Manav Bhatia,
> IP Division, Alcatel-Lucent,
> Bangalore - India
>=20
> =20
> _______________________________________________
> TICTOC mailing list
> TICTOC@ietf.org
> https://www.ietf.org/mailman/listinfo/tictoc
>=20
> =

From le@vitesse.com  Mon Jan 17 07:42:20 2011
Return-Path: <le@vitesse.com>
X-Original-To: tictoc@core3.amsl.com
Delivered-To: tictoc@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id B55FB28C0D8 for <tictoc@core3.amsl.com>; Mon, 17 Jan 2011 07:42:20 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.995
X-Spam-Level: 
X-Spam-Status: No, score=-1.995 tagged_above=-999 required=5 tests=[AWL=0.604,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id p0jf1iBaQMRY for <tictoc@core3.amsl.com>; Mon, 17 Jan 2011 07:42:19 -0800 (PST)
Received: from mx-dk.vsc.vitesse.com (mx-dk.vsc.vitesse.com [87.116.30.226]) by core3.amsl.com (Postfix) with ESMTP id F047228C0D7 for <tictoc@ietf.org>; Mon, 17 Jan 2011 07:42:17 -0800 (PST)
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.4325
Content-Class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Date: Mon, 17 Jan 2011 16:44:50 +0100
Message-ID: <8FE79B2EAF8B394E8392372D5EC5C55C01B41184@mx-dk.vsc.vitesse.com>
In-Reply-To: <7C362EEF9C7896468B36C9B79200D8350CFB0DF467@INBANSXCHMBSA1.in.alcatel-lucent.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [TICTOC] Transporting PTP messages (1588) over MPLS Networks
thread-index: Acu0ostDa6CYok1lRYSvUt8QtgvK+QBlbpeAAAKX1hAAA7UEoA==
References: <7C362EEF9C7896468B36C9B79200D8350CFB0DF1AE@INBANSXCHMBSA1.in.alcatel-lucent.com><003001cbb639$461a4930$d24edb90$@cook@calnexsol.com> <7C362EEF9C7896468B36C9B79200D8350CFB0DF467@INBANSXCHMBSA1.in.alcatel-lucent.com>
From: "Lars Ellegaard" <le@vitesse.com>
To: "Bhatia, Manav \(Manav\)" <manav.bhatia@alcatel-lucent.com>
Cc: tictoc@ietf.org
Subject: Re: [TICTOC] Transporting PTP messages (1588) over MPLS Networks
X-BeenThere: tictoc@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Timing over IP Connection and Transfer of Clock BOF <tictoc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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, 17 Jan 2011 15:42:20 -0000

Hi Manav et al.
A few comments/questions:

Section 2. Terminology:

* TC: Transparent Clocking --> Transparent Clock
* PTP PW:=20
	Should the text read: A PW within a PTP LSP that is dedicated to carry =
PTP messages ?
	That at least is my understanding of the PTP PW.
  Put another way, can you have an Ethernet PW that is sometimes =
carrying PTP, sometimes "data"?
  More general, mustn't all labels in the stack (apart from reserved =
labels) be PTP labels?
* CW: duplicate

Section 5
* Figure 1+2: should top label read "PTP label", ref. section 4?

* For my understanding: the range of PTP reserved labels, is that =
defined by the operator?

Section 15
* last paragraph says:
"The use of Penultimate Hop Pop (PHP) is acceptable as long as either
   the PHP label is the bottom of stack label (applicable only to UDP/IP
   encapsulation) or the label below the PHP label is a PTP label."
This implies that the PHP-label is also a PTP label, right?


A more general comment: would you agree that there is a general class of =
tunnel technologies=20
(PBB, MPLS, IPoverIP) that share the problem you have described here, =
and to which you found a solution for MPLS?

Thanks,
Lars


=20



-----Original Message-----
From: tictoc-bounces@ietf.org [mailto:tictoc-bounces@ietf.org] On Behalf =
Of Bhatia, Manav (Manav)
Sent: 17 January 2011 13:35
To: Tommy Cook
Cc: tictoc@ietf.org
Subject: Re: [TICTOC] Transporting PTP messages (1588) over MPLS =
Networks

Hi Tommy,

This is a typo and will be fixed in the next revision.

Cheers, Manav=20

> -----Original Message-----
> From: Tommy Cook [mailto:tommy.cook@calnexsol.com]=20
> Sent: Monday, January 17, 2011 4.56 PM
> To: Bhatia, Manav (Manav)
> Cc: tictoc@ietf.org
> Subject: RE: [TICTOC] Transporting PTP messages (1588) over=20
> MPLS Networks
>=20
> Hi Manav,
>=20
> In the Terminology section, you list "BC: Border Clock, is a=20
> .....".  In
> IEEE1588 what you describe is, I believe, referred to as a=20
> Boundary Clock.
> Did you use a different term for a specific reason or is it simply the
> terminology needs to be completely aligned?
>=20
> Regards,
> Tommy
>=20
>=20
> =
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D
> Tommy Cook
> CEO=20
> Calnex Solutions Ltd
> Tel.:=A0=A0 +44 (0) 1506-671-416
> Mob.:=A0+44 (0) 770-4894-128
> email:=A0=A0=A0 tommy.cook@calnexsol.com
> website: www.calnexsol.com
> =A0
> Calnex Solutions Limited is registered in Scotland: SC299625
>=20
>=20
>=20
> -----Original Message-----
> From: tictoc-bounces@ietf.org=20
> [mailto:tictoc-bounces@ietf.org] On Behalf Of
> Bhatia, Manav (Manav)
> Sent: 15 January 2011 10:56
> To: tictoc@ietf.org
> Subject: [TICTOC] Transporting PTP messages (1588) over MPLS Networks
>=20
> Hi,
>=20
> We have posted a revised version of=20
> draft-davari-tictoc-1588overmpls-01 and
> would appreciate a feedback from the WG.
>=20
> The draft is available here:
> http://www.ietf.org/id/draft-davari-tictoc-1588overmpls-01.txt
>=20
> Cheers, Manav
>=20
> --
> Manav Bhatia,
> IP Division, Alcatel-Lucent,
> Bangalore - India
>=20
> =20
> _______________________________________________
> TICTOC mailing list
> TICTOC@ietf.org
> https://www.ietf.org/mailman/listinfo/tictoc
>=20
>=20
_______________________________________________
TICTOC mailing list
TICTOC@ietf.org
https://www.ietf.org/mailman/listinfo/tictoc
CONFIDENTIALITY NOTICE: This e-mail message, including any attachments, =
is for the sole use of the intended recipient(s) and may contain =
confidential and privileged information. Any unauthorized review, use, =
disclosure or distribution is prohibited. If you are not the intended =
recipient, please contact the sender by reply e-mail and destroy all =
copies of the original message.

From manav.bhatia@alcatel-lucent.com  Mon Jan 17 08:13:48 2011
Return-Path: <manav.bhatia@alcatel-lucent.com>
X-Original-To: tictoc@core3.amsl.com
Delivered-To: tictoc@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id C38BB28C0F1 for <tictoc@core3.amsl.com>; Mon, 17 Jan 2011 08:13:48 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.007
X-Spam-Level: 
X-Spam-Status: No, score=-6.007 tagged_above=-999 required=5 tests=[AWL=0.592,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id l43cCzlx2DMb for <tictoc@core3.amsl.com>; Mon, 17 Jan 2011 08:13:47 -0800 (PST)
Received: from ihemail3.lucent.com (ihemail3.lucent.com [135.245.0.37]) by core3.amsl.com (Postfix) with ESMTP id 89F3628C0F0 for <tictoc@ietf.org>; Mon, 17 Jan 2011 08:13:47 -0800 (PST)
Received: from inbansmailrelay1.in.alcatel-lucent.com (h135-250-11-31.lucent.com [135.250.11.31]) by ihemail3.lucent.com (8.13.8/IER-o) with ESMTP id p0HGGGpF019663 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Mon, 17 Jan 2011 10:16:19 -0600 (CST)
Received: from INBANSXCHHUB01.in.alcatel-lucent.com (inbansxchhub01.in.alcatel-lucent.com [135.250.12.32]) by inbansmailrelay1.in.alcatel-lucent.com (8.14.3/8.14.3/GMO) with ESMTP id p0HGGFYc015073 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Mon, 17 Jan 2011 21:46:16 +0530
Received: from INBANSXCHMBSA1.in.alcatel-lucent.com ([135.250.12.56]) by INBANSXCHHUB01.in.alcatel-lucent.com ([135.250.12.32]) with mapi; Mon, 17 Jan 2011 21:46:15 +0530
From: "Bhatia, Manav (Manav)" <manav.bhatia@alcatel-lucent.com>
To: Lars Ellegaard <le@vitesse.com>
Date: Mon, 17 Jan 2011 21:46:13 +0530
Thread-Topic: [TICTOC] Transporting PTP messages (1588) over MPLS Networks
Thread-Index: Acu0ostDa6CYok1lRYSvUt8QtgvK+QBlbpeAAAKX1hAAA7UEoAADn9wQ
Message-ID: <7C362EEF9C7896468B36C9B79200D8350CFB0DF4C0@INBANSXCHMBSA1.in.alcatel-lucent.com>
References: <7C362EEF9C7896468B36C9B79200D8350CFB0DF1AE@INBANSXCHMBSA1.in.alcatel-lucent.com><003001cbb639$461a4930$d24edb90$@cook@calnexsol.com> <7C362EEF9C7896468B36C9B79200D8350CFB0DF467@INBANSXCHMBSA1.in.alcatel-lucent.com> <8FE79B2EAF8B394E8392372D5EC5C55C01B41184@mx-dk.vsc.vitesse.com>
In-Reply-To: <8FE79B2EAF8B394E8392372D5EC5C55C01B41184@mx-dk.vsc.vitesse.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Scanned-By: MIMEDefang 2.57 on 135.245.2.37
X-Scanned-By: MIMEDefang 2.64 on 135.250.11.31
Cc: "tictoc@ietf.org" <tictoc@ietf.org>
Subject: Re: [TICTOC] Transporting PTP messages (1588) over MPLS Networks
X-BeenThere: tictoc@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Timing over IP Connection and Transfer of Clock BOF <tictoc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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, 17 Jan 2011 16:13:48 -0000

Hi Lars,
=20
> * TC: Transparent Clocking --> Transparent Clock
> * PTP PW:=20
> 	Should the text read: A PW within a PTP LSP that is=20
> dedicated to carry PTP messages ?
> 	That at least is my understanding of the PTP PW.
>   Put another way, can you have an Ethernet PW that is=20
> sometimes carrying PTP, sometimes "data"?
>   More general, mustn't all labels in the stack (apart from=20
> reserved labels) be PTP labels?
> * CW: duplicate

Will do.

>=20
> Section 5
> * Figure 1+2: should top label read "PTP label", ref. section 4?

The current text looks ok to me. Its called PTP Tunnel Label to explicitly =
indicate that it's the outermost label that LSRs would use to switch the pa=
ckets on.

>=20
> * For my understanding: the range of PTP reserved labels, is=20
> that defined by the operator?

I am not sure I understand the reserved labels that you are referring to.
=20
> Section 15
> * last paragraph says:
> "The use of Penultimate Hop Pop (PHP) is acceptable as long as either
>    the PHP label is the bottom of stack label (applicable=20
> only to UDP/IP
>    encapsulation) or the label below the PHP label is a PTP label."
> This implies that the PHP-label is also a PTP label, right?
>=20
>=20
> A more general comment: would you agree that there is a=20
> general class of tunnel technologies=20
> (PBB, MPLS, IPoverIP) that share the problem you have=20
> described here, and to which you found a solution for MPLS?

I think Yes.

Cheers, Manav=

From hingkam16@gmail.com  Mon Jan 17 16:07:27 2011
Return-Path: <hingkam16@gmail.com>
X-Original-To: tictoc@core3.amsl.com
Delivered-To: tictoc@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 0DA8B28C1DA for <tictoc@core3.amsl.com>; Mon, 17 Jan 2011 16:07:27 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.273
X-Spam-Level: 
X-Spam-Status: No, score=-3.273 tagged_above=-999 required=5 tests=[AWL=0.326,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id RATUlNS4vS2M for <tictoc@core3.amsl.com>; Mon, 17 Jan 2011 16:07:26 -0800 (PST)
Received: from mail-iy0-f172.google.com (mail-iy0-f172.google.com [209.85.210.172]) by core3.amsl.com (Postfix) with ESMTP id 52BD428C1CB for <tictoc@ietf.org>; Mon, 17 Jan 2011 16:07:26 -0800 (PST)
Received: by iyi42 with SMTP id 42so5609610iyi.31 for <tictoc@ietf.org>; Mon, 17 Jan 2011 16:10:01 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=Tbz7p/+5Gpp65au0V7o3/ZHqy5r0kP0iv0/G0aVoQ5s=; b=ZB3ZDN2Jco3spwkjKAvOXRsdfT9f6p7Q1/d01b9Y1ZJnM1Zw4HnGIAN8STiovTUsKl fZZgpSKXnRm0HjWBhhAo5NE3pDug6A6pXXUTvjY8AAu6ywVLl98sjZ5i0NcB3hKa7yi0 bQZlZ5y/G/6xlIlZYIuROMTNiKAs64xaazIgQ=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=Q8cdkZp/vxkZCsEwlJs5FDSHOJlcDvXIVtaL/IbClwvNT5g/GvMx6bPuUtZNv4IKBf dpYz4xDvOJTz46BflSxWdHUoHFpJ3jgQqyS005keRS6W5U/M7ipW7GOrd+JS6S0O1/Vm z4x70Biv68f88HyotAq37V45pYzCknYpQcmZA=
MIME-Version: 1.0
Received: by 10.231.31.203 with SMTP id z11mr996673ibc.28.1295309401634; Mon, 17 Jan 2011 16:10:01 -0800 (PST)
Received: by 10.231.14.141 with HTTP; Mon, 17 Jan 2011 16:10:01 -0800 (PST)
In-Reply-To: <7C362EEF9C7896468B36C9B79200D8350CFB0DF4C0@INBANSXCHMBSA1.in.alcatel-lucent.com>
References: <7C362EEF9C7896468B36C9B79200D8350CFB0DF1AE@INBANSXCHMBSA1.in.alcatel-lucent.com> <7C362EEF9C7896468B36C9B79200D8350CFB0DF467@INBANSXCHMBSA1.in.alcatel-lucent.com> <8FE79B2EAF8B394E8392372D5EC5C55C01B41184@mx-dk.vsc.vitesse.com> <7C362EEF9C7896468B36C9B79200D8350CFB0DF4C0@INBANSXCHMBSA1.in.alcatel-lucent.com>
Date: Tue, 18 Jan 2011 05:40:01 +0530
Message-ID: <AANLkTimKSGJFPbXfX+qt_0PqmnSPGS-WLoXQ-7ttjUW9@mail.gmail.com>
From: "Hing-Kam (Kam) Lam" <hingkam16@gmail.com>
To: "Bhatia, Manav (Manav)" <manav.bhatia@alcatel-lucent.com>
Content-Type: text/plain; charset=ISO-8859-1
Cc: "tictoc@ietf.org" <tictoc@ietf.org>
Subject: Re: [TICTOC] Transporting PTP messages (1588) over MPLS Networks
X-BeenThere: tictoc@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Timing over IP Connection and Transfer of Clock BOF <tictoc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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, 18 Jan 2011 00:07:27 -0000

There are a few minor nits which can be fixed in the next revision.
Otherwise, i appreciate this work and would like to see this
progressed further in the WG. Are we accepting this as a WG document
yet?

Kam

From le@vitesse.com  Mon Jan 17 23:41:45 2011
Return-Path: <le@vitesse.com>
X-Original-To: tictoc@core3.amsl.com
Delivered-To: tictoc@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 8A2C23A6DA4 for <tictoc@core3.amsl.com>; Mon, 17 Jan 2011 23:41:45 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.196
X-Spam-Level: 
X-Spam-Status: No, score=-2.196 tagged_above=-999 required=5 tests=[AWL=0.403,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id mDGkY8H2JHHM for <tictoc@core3.amsl.com>; Mon, 17 Jan 2011 23:41:44 -0800 (PST)
Received: from mx-dk.vsc.vitesse.com (mx-dk.vsc.vitesse.com [87.116.30.226]) by core3.amsl.com (Postfix) with ESMTP id 499633A6D07 for <tictoc@ietf.org>; Mon, 17 Jan 2011 23:41:44 -0800 (PST)
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.4325
Content-Class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable
Date: Tue, 18 Jan 2011 08:44:17 +0100
Message-ID: <8FE79B2EAF8B394E8392372D5EC5C55C01B411AB@mx-dk.vsc.vitesse.com>
In-Reply-To: <7C362EEF9C7896468B36C9B79200D8350CFB0DF4C0@INBANSXCHMBSA1.in.alcatel-lucent.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [TICTOC] Transporting PTP messages (1588) over MPLS Networks
thread-index: Acu0ostDa6CYok1lRYSvUt8QtgvK+QBlbpeAAAKX1hAAA7UEoAADn9wQACBeQPA=
References: <7C362EEF9C7896468B36C9B79200D8350CFB0DF1AE@INBANSXCHMBSA1.in.alcatel-lucent.com><003001cbb639$461a4930$d24edb90$@cook@calnexsol.com> <7C362EEF9C7896468B36C9B79200D8350CFB0DF467@INBANSXCHMBSA1.in.alcatel-lucent.com> <8FE79B2EAF8B394E8392372D5EC5C55C01B41184@mx-dk.vsc.vitesse.com> <7C362EEF9C7896468B36C9B79200D8350CFB0DF4C0@INBANSXCHMBSA1.in.alcatel-lucent.com>
From: "Lars Ellegaard" <le@vitesse.com>
To: "Bhatia, Manav \(Manav\)" <manav.bhatia@alcatel-lucent.com>
Cc: tictoc@ietf.org
Subject: Re: [TICTOC] Transporting PTP messages (1588) over MPLS Networks
X-BeenThere: tictoc@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Timing over IP Connection and Transfer of Clock BOF <tictoc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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, 18 Jan 2011 07:41:45 -0000

Thanks, Manev.

Wrt.
>=20
> * For my understanding: the range of PTP reserved labels, is=20
> that defined by the operator?

I am not sure I understand the reserved labels that you are referring
to.

[LE] I was confused by a sentence towards the end in section 5.2: "In
such cases, the PW label SHOULD be chosen from the PTP Label range."
Looking at section 13+14 on I now understand that the binding of PTP LSP
and label is achieved via the RSVP-TE Object.

Rgds,
Lars


-----Original Message-----
From: Bhatia, Manav (Manav) [mailto:manav.bhatia@alcatel-lucent.com]=20
Sent: 17 January 2011 17:16
To: Lars Ellegaard
Cc: tictoc@ietf.org
Subject: RE: [TICTOC] Transporting PTP messages (1588) over MPLS
Networks

Hi Lars,
=20
> * TC: Transparent Clocking --> Transparent Clock
> * PTP PW:=20
> 	Should the text read: A PW within a PTP LSP that is=20
> dedicated to carry PTP messages ?
> 	That at least is my understanding of the PTP PW.
>   Put another way, can you have an Ethernet PW that is=20
> sometimes carrying PTP, sometimes "data"?
>   More general, mustn't all labels in the stack (apart from=20
> reserved labels) be PTP labels?
> * CW: duplicate

Will do.

>=20
> Section 5
> * Figure 1+2: should top label read "PTP label", ref. section 4?

The current text looks ok to me. Its called PTP Tunnel Label to
explicitly indicate that it's the outermost label that LSRs would use to
switch the packets on.

>=20
> * For my understanding: the range of PTP reserved labels, is=20
> that defined by the operator?

I am not sure I understand the reserved labels that you are referring
to.
=20
> Section 15
> * last paragraph says:
> "The use of Penultimate Hop Pop (PHP) is acceptable as long as either
>    the PHP label is the bottom of stack label (applicable=20
> only to UDP/IP
>    encapsulation) or the label below the PHP label is a PTP label."
> This implies that the PHP-label is also a PTP label, right?
>=20
>=20
> A more general comment: would you agree that there is a=20
> general class of tunnel technologies=20
> (PBB, MPLS, IPoverIP) that share the problem you have=20
> described here, and to which you found a solution for MPLS?

I think Yes.

Cheers, Manav
CONFIDENTIALITY NOTICE: This e-mail message, including any attachments, =
is for the sole use of the intended recipient(s) and may contain =
confidential and privileged information. Any unauthorized review, use, =
disclosure or distribution is prohibited. If you are not the intended =
recipient, please contact the sender by reply e-mail and destroy all =
copies of the original message.

From manav.bhatia@alcatel-lucent.com  Tue Jan 18 01:07:26 2011
Return-Path: <manav.bhatia@alcatel-lucent.com>
X-Original-To: tictoc@core3.amsl.com
Delivered-To: tictoc@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 8AADD3A6E95 for <tictoc@core3.amsl.com>; Tue, 18 Jan 2011 01:07:26 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.026
X-Spam-Level: 
X-Spam-Status: No, score=-6.026 tagged_above=-999 required=5 tests=[AWL=0.573,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id XPgImA-hR24A for <tictoc@core3.amsl.com>; Tue, 18 Jan 2011 01:07:25 -0800 (PST)
Received: from ihemail4.lucent.com (ihemail4.lucent.com [135.245.0.39]) by core3.amsl.com (Postfix) with ESMTP id 9F0393A6E74 for <tictoc@ietf.org>; Tue, 18 Jan 2011 01:07:24 -0800 (PST)
Received: from inbansmailrelay2.in.alcatel-lucent.com (h135-250-11-33.lucent.com [135.250.11.33]) by ihemail4.lucent.com (8.13.8/IER-o) with ESMTP id p0I99sYf016570 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Tue, 18 Jan 2011 03:09:58 -0600 (CST)
Received: from INBANSXCHHUB02.in.alcatel-lucent.com (inbansxchhub02.in.alcatel-lucent.com [135.250.12.35]) by inbansmailrelay2.in.alcatel-lucent.com (8.14.3/8.14.3/GMO) with ESMTP id p0I99qg5009576 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Tue, 18 Jan 2011 14:39:52 +0530
Received: from [135.250.26.32] (135.250.19.8) by INBANSXCHHUB02.in.alcatel-lucent.com (135.250.12.35) with Microsoft SMTP Server (TLS) id 8.3.106.1; Tue, 18 Jan 2011 14:39:52 +0530
Message-ID: <4D3558D2.7070906@alcatel-lucent.com>
Date: Tue, 18 Jan 2011 14:39:38 +0530
From: Manav Bhatia <manav.bhatia@alcatel-lucent.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2.13) Gecko/20101207 Lightning/1.0b2 Thunderbird/3.1.7 ThunderBrowse/3.3.4
MIME-Version: 1.0
To: Lars Ellegaard <le@vitesse.com>
References: <7C362EEF9C7896468B36C9B79200D8350CFB0DF1AE@INBANSXCHMBSA1.in.alcatel-lucent.com><003001cbb639$461a4930$d24edb90$@cook@calnexsol.com> <7C362EEF9C7896468B36C9B79200D8350CFB0DF467@INBANSXCHMBSA1.in.alcatel-lucent.com> <8FE79B2EAF8B394E8392372D5EC5C55C01B41184@mx-dk.vsc.vitesse.com> <7C362EEF9C7896468B36C9B79200D8350CFB0DF4C0@INBANSXCHMBSA1.in.alcatel-lucent.com> <8FE79B2EAF8B394E8392372D5EC5C55C01B411AB@mx-dk.vsc.vitesse.com>
In-Reply-To: <8FE79B2EAF8B394E8392372D5EC5C55C01B411AB@mx-dk.vsc.vitesse.com>
Content-Type: text/plain; charset="ISO-8859-1"; format=flowed
Content-Transfer-Encoding: 7bit
X-Scanned-By: MIMEDefang 2.57 on 135.245.2.39
X-Scanned-By: MIMEDefang 2.64 on 135.250.11.33
Cc: "tictoc@ietf.org" <tictoc@ietf.org>
Subject: Re: [TICTOC] Transporting PTP messages (1588) over MPLS Networks
X-BeenThere: tictoc@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Timing over IP Connection and Transfer of Clock BOF <tictoc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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, 18 Jan 2011 09:07:26 -0000

Yup, thats correct!

Cheers, Manav

On 1/18/2011 1:14 PM, Lars Ellegaard wrote:
> Thanks, Manev.
>
> Wrt.
>>
>> * For my understanding: the range of PTP reserved labels, is
>> that defined by the operator?
>
> I am not sure I understand the reserved labels that you are referring
> to.
>
> [LE] I was confused by a sentence towards the end in section 5.2: "In
> such cases, the PW label SHOULD be chosen from the PTP Label range."
> Looking at section 13+14 on I now understand that the binding of PTP LSP
> and label is achieved via the RSVP-TE Object.
>
> Rgds,
> Lars
>
>
> -----Original Message-----
> From: Bhatia, Manav (Manav) [mailto:manav.bhatia@alcatel-lucent.com]
> Sent: 17 January 2011 17:16
> To: Lars Ellegaard
> Cc: tictoc@ietf.org
> Subject: RE: [TICTOC] Transporting PTP messages (1588) over MPLS
> Networks
>
> Hi Lars,
>
>> * TC: Transparent Clocking -->  Transparent Clock
>> * PTP PW:
>> 	Should the text read: A PW within a PTP LSP that is
>> dedicated to carry PTP messages ?
>> 	That at least is my understanding of the PTP PW.
>>    Put another way, can you have an Ethernet PW that is
>> sometimes carrying PTP, sometimes "data"?
>>    More general, mustn't all labels in the stack (apart from
>> reserved labels) be PTP labels?
>> * CW: duplicate
>
> Will do.
>
>>
>> Section 5
>> * Figure 1+2: should top label read "PTP label", ref. section 4?
>
> The current text looks ok to me. Its called PTP Tunnel Label to
> explicitly indicate that it's the outermost label that LSRs would use to
> switch the packets on.
>
>>
>> * For my understanding: the range of PTP reserved labels, is
>> that defined by the operator?
>
> I am not sure I understand the reserved labels that you are referring
> to.
>
>> Section 15
>> * last paragraph says:
>> "The use of Penultimate Hop Pop (PHP) is acceptable as long as either
>>     the PHP label is the bottom of stack label (applicable
>> only to UDP/IP
>>     encapsulation) or the label below the PHP label is a PTP label."
>> This implies that the PHP-label is also a PTP label, right?
>>
>>
>> A more general comment: would you agree that there is a
>> general class of tunnel technologies
>> (PBB, MPLS, IPoverIP) that share the problem you have
>> described here, and to which you found a solution for MPLS?
>
> I think Yes.
>
> Cheers, Manav
> CONFIDENTIALITY NOTICE: This e-mail message, including any attachments, is for the sole use of the intended recipient(s) and may contain confidential and privileged information. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the original message.

From stbryant@cisco.com  Tue Jan 18 02:29:18 2011
Return-Path: <stbryant@cisco.com>
X-Original-To: tictoc@core3.amsl.com
Delivered-To: tictoc@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 1B53C3A6FCF for <tictoc@core3.amsl.com>; Tue, 18 Jan 2011 02:29:18 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.548
X-Spam-Level: 
X-Spam-Status: No, score=-110.548 tagged_above=-999 required=5 tests=[AWL=0.051, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id rUn19Okzj5s7 for <tictoc@core3.amsl.com>; Tue, 18 Jan 2011 02:29:17 -0800 (PST)
Received: from rtp-iport-1.cisco.com (rtp-iport-1.cisco.com [64.102.122.148]) by core3.amsl.com (Postfix) with ESMTP id 246593A6FCB for <tictoc@ietf.org>; Tue, 18 Jan 2011 02:29:17 -0800 (PST)
Authentication-Results: rtp-iport-1.cisco.com; dkim=neutral (message not signed) header.i=none
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AskFAGf7NE1AZnwM/2dsb2JhbACWPo4Yc6huglIOAZcSgniCWASLHg
Received: from rtp-core-1.cisco.com ([64.102.124.12]) by rtp-iport-1.cisco.com with ESMTP; 18 Jan 2011 10:31:49 +0000
Received: from cisco.com (mrwint.cisco.com [64.103.71.48]) by rtp-core-1.cisco.com (8.13.8/8.14.3) with ESMTP id p0IAVnLY015421 for <tictoc@ietf.org>; Tue, 18 Jan 2011 10:31:49 GMT
Received: from stbryant-mac2.lan (localhost [127.0.0.1]) by cisco.com (8.11.7p3+Sun/8.8.8) with ESMTP id p0IAVl826353; Tue, 18 Jan 2011 10:31:47 GMT
Message-ID: <4D356C13.6080705@cisco.com>
Date: Tue, 18 Jan 2011 10:31:47 +0000
From: Stewart Bryant <stbryant@cisco.com>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.2.13) Gecko/20101207 Lightning/1.0b2 Thunderbird/3.1.7
MIME-Version: 1.0
To: tictoc@ietf.org
References: <7C362EEF9C7896468B36C9B79200D8350CFB0DF1AE@INBANSXCHMBSA1.in.alcatel-lucent.com>	<alpine.DEB.1.10.1101151217360.13151@uplift.swm.pp.se>	<7C362EEF9C7896468B36C9B79200D8350CFB0DF1C3@INBANSXCHMBSA1.in.alcatel-lucent.com>	<alpine.DEB.1.10.1101160659310.13151@uplift.swm.pp.se>	<7C362EEF9C7896468B36C9B79200D8350CFB0DF1DA@INBANSXCHMBSA1.in.alcatel-lucent.com>	<alpine.DEB.1.10.1101161244010.13151@uplift.swm.pp.se> <7C362EEF9C7896468B36C9B79200D8350CFB0DF1DD@INBANSXCHMBSA1.in.alcatel-lucent.com>
In-Reply-To: <7C362EEF9C7896468B36C9B79200D8350CFB0DF1DD@INBANSXCHMBSA1.in.alcatel-lucent.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [TICTOC] Transporting PTP messages (1588) over MPLS Networks
X-BeenThere: tictoc@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: stbryant@cisco.com
List-Id: Timing over IP Connection and Transfer of Clock BOF <tictoc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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, 18 Jan 2011 10:29:18 -0000

On 16/01/2011 11:58, Bhatia, Manav (Manav) wrote:
>
> Ok, I think I understand what youre alluding to. You will like implementations to send out the PTP message using the highest priority queue that's available at the egress. Is this correct?
>
> If this is what you want, then I would disagree. While I understand the urgency to send out these packets, its way to less than all the other control traffic that needs to be sent (like BFD, LACP, EFM, etc) out.

I am not at all convinced that PTP traffic is in any way urgent.

What is important is that the timestamp is correct at egress and 
immediate on ingress.

The point of this draft is that PTP goes in it's own label group so that 
the h/w can identify and timestamp the PTP traffic.

Stewart

From manav.bhatia@alcatel-lucent.com  Tue Jan 18 04:09:33 2011
Return-Path: <manav.bhatia@alcatel-lucent.com>
X-Original-To: tictoc@core3.amsl.com
Delivered-To: tictoc@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 347213A6F78 for <tictoc@core3.amsl.com>; Tue, 18 Jan 2011 04:09:33 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.044
X-Spam-Level: 
X-Spam-Status: No, score=-6.044 tagged_above=-999 required=5 tests=[AWL=0.555,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Q7ZfyHdyQfDA for <tictoc@core3.amsl.com>; Tue, 18 Jan 2011 04:09:32 -0800 (PST)
Received: from ihemail1.lucent.com (ihemail1.lucent.com [135.245.0.33]) by core3.amsl.com (Postfix) with ESMTP id 626473A6ED4 for <tictoc@ietf.org>; Tue, 18 Jan 2011 04:09:32 -0800 (PST)
Received: from inbansmailrelay1.in.alcatel-lucent.com (h135-250-11-31.lucent.com [135.250.11.31]) by ihemail1.lucent.com (8.13.8/IER-o) with ESMTP id p0ICC59r017802 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Tue, 18 Jan 2011 06:12:07 -0600 (CST)
Received: from INBANSXCHHUB02.in.alcatel-lucent.com (inbansxchhub02.in.alcatel-lucent.com [135.250.12.35]) by inbansmailrelay1.in.alcatel-lucent.com (8.14.3/8.14.3/GMO) with ESMTP id p0ICC49N032175 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Tue, 18 Jan 2011 17:42:04 +0530
Received: from INBANSXCHMBSA1.in.alcatel-lucent.com ([135.250.12.56]) by INBANSXCHHUB02.in.alcatel-lucent.com ([135.250.12.35]) with mapi; Tue, 18 Jan 2011 17:42:04 +0530
From: "Bhatia, Manav (Manav)" <manav.bhatia@alcatel-lucent.com>
To: "stbryant@cisco.com" <stbryant@cisco.com>, "tictoc@ietf.org" <tictoc@ietf.org>
Date: Tue, 18 Jan 2011 17:42:01 +0530
Thread-Topic: [TICTOC] Transporting PTP messages (1588) over MPLS Networks
Thread-Index: Acu2+wc/Bx6xZKPLSKmyh2gfADiATQADYQOA
Message-ID: <7C362EEF9C7896468B36C9B79200D8350CFB0DF77C@INBANSXCHMBSA1.in.alcatel-lucent.com>
References: <7C362EEF9C7896468B36C9B79200D8350CFB0DF1AE@INBANSXCHMBSA1.in.alcatel-lucent.com> <alpine.DEB.1.10.1101151217360.13151@uplift.swm.pp.se> <7C362EEF9C7896468B36C9B79200D8350CFB0DF1C3@INBANSXCHMBSA1.in.alcatel-lucent.com> <alpine.DEB.1.10.1101160659310.13151@uplift.swm.pp.se> <7C362EEF9C7896468B36C9B79200D8350CFB0DF1DA@INBANSXCHMBSA1.in.alcatel-lucent.com> <alpine.DEB.1.10.1101161244010.13151@uplift.swm.pp.se> <7C362EEF9C7896468B36C9B79200D8350CFB0DF1DD@INBANSXCHMBSA1.in.alcatel-lucent.com> <4D356C13.6080705@cisco.com>
In-Reply-To: <4D356C13.6080705@cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Scanned-By: MIMEDefang 2.57 on 135.245.2.33
X-Scanned-By: MIMEDefang 2.64 on 135.250.11.31
Subject: Re: [TICTOC] Transporting PTP messages (1588) over MPLS Networks
X-BeenThere: tictoc@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Timing over IP Connection and Transfer of Clock BOF <tictoc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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, 18 Jan 2011 12:09:33 -0000

>=20
> I am not at all convinced that PTP traffic is in any way urgent.
>=20
> What is important is that the timestamp is correct at egress and=20
> immediate on ingress.
>=20
> The point of this draft is that PTP goes in it's own label=20
> group so that=20
> the h/w can identify and timestamp the PTP traffic.

Yes, that's correct. In addition to this, it also enables boxes that cant d=
o 1588 processing to expedite processing of these packets.

Cheers, Manav

>=20
> Stewart
> _______________________________________________
> TICTOC mailing list
> TICTOC@ietf.org
> https://www.ietf.org/mailman/listinfo/tictoc
> =

From lizhong.jin@zte.com.cn  Tue Jan 18 04:31:11 2011
Return-Path: <lizhong.jin@zte.com.cn>
X-Original-To: tictoc@core3.amsl.com
Delivered-To: tictoc@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 6FB0D3A6F30 for <tictoc@core3.amsl.com>; Tue, 18 Jan 2011 04:31:11 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.551
X-Spam-Level: 
X-Spam-Status: No, score=-101.551 tagged_above=-999 required=5 tests=[AWL=0.287, 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.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id JG-RdqWmIMZp for <tictoc@core3.amsl.com>; Tue, 18 Jan 2011 04:31:10 -0800 (PST)
Received: from mx5.zte.com.cn (mx5.zte.com.cn [63.217.80.70]) by core3.amsl.com (Postfix) with ESMTP id C78AD3A6F2B for <tictoc@ietf.org>; Tue, 18 Jan 2011 04:31:09 -0800 (PST)
Received: from [10.30.17.99] by mx5.zte.com.cn with surfront esmtp id 205951930506506; Tue, 18 Jan 2011 20:29:04 +0800 (CST)
Received: from [10.30.3.20] by [192.168.168.15] with StormMail ESMTP id 96520.3711756443; Tue, 18 Jan 2011 20:33:38 +0800 (CST)
Received: from notes_smtp.zte.com.cn ([10.30.1.239]) by mse01.zte.com.cn with ESMTP id p0ICXZUJ003474; Tue, 18 Jan 2011 20:33:35 +0800 (GMT-8) (envelope-from lizhong.jin@zte.com.cn)
In-Reply-To: <mailman.1779.1295088820.4689.tictoc@ietf.org>
To: manav.bhatia@alcatel-lucent.com
MIME-Version: 1.0
X-Mailer: Lotus Notes Release 6.5.6 March 06, 2007
Message-ID: <OFA596765B.570CE6DC-ON4825781C.004262BC-4825781C.0044FEEC@zte.com.cn>
From: lizhong.jin@zte.com.cn
Date: Tue, 18 Jan 2011 20:32:49 +0800
X-MIMETrack: S/MIME Sign by Notes Client on JinLiZhong127666/user/zte_ltd(Release 6.5.6|March 06, 2007) at 2011-01-18 20:33:37, Serialize by Notes Client on JinLiZhong127666/user/zte_ltd(Release 6.5.6|March 06, 2007) at 2011-01-18 20:33:37, Serialize complete at 2011-01-18 20:33:37, S/MIME Sign failed at 2011-01-18 20:33:37: The cryptographic key was not found, Serialize by Router on notes_smtp/zte_ltd(Release 8.5.1FP4|July 25, 2010) at 2011-01-18 20:33:37
Content-Type: multipart/alternative; boundary="=_alternative 0044FEE94825781C_="
X-MAIL: mse01.zte.com.cn p0ICXZUJ003474
Cc: tictoc@ietf.org
Subject: Re: [TICTOC] Transporting PTP messages (1588) over MPLS Networks
X-BeenThere: tictoc@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Timing over IP Connection and Transfer of Clock BOF <tictoc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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, 18 Jan 2011 12:31:11 -0000

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

Hi Manav,
In section 8 ECMP, since it is said PTP LSPs and PWs MUST NOT be subject 
to ECMP, why in section 5.2 the encapsulation of figure 2 has entroy 
label? I am a bit confused.

Regards
Lizhong


> ----------------------------------------------------------------------
> 
> Message: 1
> Date: Sat, 15 Jan 2011 16:25:59 +0530
> From: "Bhatia, Manav (Manav)" <manav.bhatia@alcatel-lucent.com>
> Subject: [TICTOC] Transporting PTP messages (1588) over MPLS Networks
> To: "tictoc@ietf.org" <tictoc@ietf.org>
> Message-ID:
>    <7C362EEF9C7896468B36C9B79200D8350CFB0DF1AE@INBANSXCHMBSA1.in.
> alcatel-lucent.com>
> 
> Content-Type: text/plain; charset="us-ascii"
> 
> Hi,
> 
> We have posted a revised version of draft-davari-
> tictoc-1588overmpls-01 and would appreciate a feedback from the WG.
> 
> The draft is available here:
> http://www.ietf.org/id/draft-davari-tictoc-1588overmpls-01.txt
> 
> Cheers, Manav
> 
> --
> Manav Bhatia,
> IP Division, Alcatel-Lucent,
> Bangalore - India
> 
> 
> 

--------------------------------------------------------
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 0044FEE94825781C_=
Content-Type: text/html; charset="US-ASCII"


<br><tt><font size=2>Hi Manav,</font></tt>
<br><tt><font size=2>In section 8 ECMP, since it is said PTP LSPs and PWs
MUST NOT be subject to ECMP, why in section 5.2 the encapsulation of figure
2 has entroy label? I am a bit confused.</font></tt>
<br>
<br><tt><font size=2>Regards</font></tt>
<br><tt><font size=2>Lizhong</font></tt>
<br>
<br><tt><font size=2><br>
&gt; ----------------------------------------------------------------------<br>
&gt; <br>
&gt; Message: 1<br>
&gt; Date: Sat, 15 Jan 2011 16:25:59 +0530<br>
&gt; From: &quot;Bhatia, Manav (Manav)&quot; &lt;manav.bhatia@alcatel-lucent.com&gt;<br>
&gt; Subject: [TICTOC] Transporting PTP messages (1588) over MPLS Networks<br>
&gt; To: &quot;tictoc@ietf.org&quot; &lt;tictoc@ietf.org&gt;<br>
&gt; Message-ID:<br>
&gt; &nbsp; &nbsp;&lt;7C362EEF9C7896468B36C9B79200D8350CFB0DF1AE@INBANSXCHMBSA1.in.<br>
&gt; alcatel-lucent.com&gt;<br>
&gt; &nbsp; &nbsp;<br>
&gt; Content-Type: text/plain; charset=&quot;us-ascii&quot;<br>
&gt; <br>
&gt; Hi,<br>
&gt; <br>
&gt; We have posted a revised version of draft-davari-<br>
&gt; tictoc-1588overmpls-01 and would appreciate a feedback from the WG.<br>
&gt; <br>
&gt; The draft is available here:<br>
&gt; http://www.ietf.org/id/draft-davari-tictoc-1588overmpls-01.txt<br>
&gt; <br>
&gt; Cheers, Manav<br>
&gt; <br>
&gt; --<br>
&gt; Manav Bhatia,<br>
&gt; IP Division, Alcatel-Lucent,<br>
&gt; Bangalore - India<br>
&gt; <br>
&gt; &nbsp;<br>
&gt; </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 0044FEE94825781C_=--


From talmi@marvell.com  Tue Jan 18 06:04:55 2011
Return-Path: <talmi@marvell.com>
X-Original-To: tictoc@core3.amsl.com
Delivered-To: tictoc@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 7B62F3A6FE4 for <tictoc@core3.amsl.com>; Tue, 18 Jan 2011 06:04:55 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id YLsQKfnwGFPN for <tictoc@core3.amsl.com>; Tue, 18 Jan 2011 06:04:54 -0800 (PST)
Received: from na3sys009aog111.obsmtp.com (na3sys009aog111.obsmtp.com [74.125.149.205]) by core3.amsl.com (Postfix) with SMTP id 59CEF3A6F16 for <tictoc@ietf.org>; Tue, 18 Jan 2011 06:04:53 -0800 (PST)
Received: from source ([65.219.4.129]) (using TLSv1) by na3sys009aob111.postini.com ([74.125.148.12]) with SMTP ID DSNKTTWeorJ6+neb7pRRBzNfGtGxkS2L3wb0@postini.com; Tue, 18 Jan 2011 06:07:31 PST
Received: from YK-HUB02.marvell.com (10.4.102.52) by sc-owa01.marvell.com (10.93.76.21) with Microsoft SMTP Server (TLS) id 8.2.213.0; Tue, 18 Jan 2011 06:04:21 -0800
Received: from IL-MB01.marvell.com ([10.4.102.53]) by YK-HUB02.marvell.com ([10.4.102.52]) with mapi; Tue, 18 Jan 2011 16:04:18 +0200
From: Tal Mizrahi <talmi@marvell.com>
To: "Bhatia, Manav (Manav)" <manav.bhatia@alcatel-lucent.com>, "tictoc@ietf.org" <tictoc@ietf.org>
Date: Tue, 18 Jan 2011 16:04:21 +0200
Thread-Topic: Transporting PTP messages (1588) over MPLS Networks
Thread-Index: Acu0ostDa6CYok1lRYSvUt8QtgvK+QCdFs+g
Message-ID: <74470498B659FA4687F0B0018C19A89CFCDC0EB8AA@IL-MB01.marvell.com>
References: <7C362EEF9C7896468B36C9B79200D8350CFB0DF1AE@INBANSXCHMBSA1.in.alcatel-lucent.com>
In-Reply-To: <7C362EEF9C7896468B36C9B79200D8350CFB0DF1AE@INBANSXCHMBSA1.in.alcatel-lucent.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: Re: [TICTOC] Transporting PTP messages (1588) over MPLS Networks
X-BeenThere: tictoc@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Timing over IP Connection and Transfer of Clock BOF <tictoc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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, 18 Jan 2011 14:04:55 -0000

Hi Manav,

A few comments below.

Section 3. Problem Statement says that "The defined method is applicable to=
 both MPLS and MPLS-TP networks."
- however, Section 9. OAM, Control and Management does not mention MPLS-TP =
OAM. Furthermore, section 5.1. 1588 over LSP Encapsulation shows an encapsu=
lation with a single label, and does not show that an optional GAL is possi=
ble.

6.  1588 Message Transport
"If Two Step Transparent clocks are present, then the FOLLOW_UP and DELAY_R=
ESP messages must also be transported over the PTP LSPs."=20
- for P2P TCs you also need the PDelay_Resp_Follow_Up.

10.  QoS Considerations
- I am not sure I understand why this is a MUST. This draft defines an enca=
psulation, while the QoS requirements are typically be derived from the app=
lication, which is defined elsewhere.

11.  FCS Recalculation
"FCS retention described in [RFC4720] MUST not be used"=20
- that makes sense, but seems to contradict the first half of the sentence =
"Ethernet FCS MUST be recalculated at every LSR". In my understanding if re=
tention is not used, only the LERs have to recompute the FCS. LSRs may alte=
r the CF, but do not need to bother with the FCS.

Tal.

-----Original Message-----
From: tictoc-bounces@ietf.org [mailto:tictoc-bounces@ietf.org] On Behalf Of=
 Bhatia, Manav (Manav)
Sent: Saturday, January 15, 2011 12:56 PM
To: tictoc@ietf.org
Subject: [TICTOC] Transporting PTP messages (1588) over MPLS Networks

Hi,

We have posted a revised version of draft-davari-tictoc-1588overmpls-01 and=
 would appreciate a feedback from the WG.

The draft is available here:
http://www.ietf.org/id/draft-davari-tictoc-1588overmpls-01.txt

Cheers, Manav

--
Manav Bhatia,
IP Division, Alcatel-Lucent,
Bangalore - India

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

From yaakov_s@rad.com  Tue Jan 18 07:43:22 2011
Return-Path: <yaakov_s@rad.com>
X-Original-To: tictoc@core3.amsl.com
Delivered-To: tictoc@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id AC04F28C1B7 for <tictoc@core3.amsl.com>; Tue, 18 Jan 2011 07:43:22 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.492
X-Spam-Level: 
X-Spam-Status: No, score=-102.492 tagged_above=-999 required=5 tests=[AWL=0.107, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id X2F3fWZ2Jbkt for <tictoc@core3.amsl.com>; Tue, 18 Jan 2011 07:43:21 -0800 (PST)
Received: from antivir1.rad.co.il (mx1-q.rad.co.il [80.74.100.136]) by core3.amsl.com (Postfix) with ESMTP id 6057228C1AD for <tictoc@ietf.org>; Tue, 18 Jan 2011 07:43:19 -0800 (PST)
Received: from unknown (HELO EXRAD5.ad.rad.co.il) ([192.114.24.28]) by antivir1.rad.co.il with ESMTP; 18 Jan 2011 17:45:55 +0200
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; Tue, 18 Jan 2011 17:45:14 +0200
Received: from EXRAD5.ad.rad.co.il ([fe80::ec3e:feb5:8bef:e3ba]) by exus4-drp.ad.rad.co.il ([fe80::5d6f:c2cb:2468:ee2%16]) with mapi id 14.01.0270.001; Tue, 18 Jan 2011 17:45:14 +0200
From: Yaakov Stein <yaakov_s@rad.com>
To: "Bhatia, Manav (Manav)" <manav.bhatia@alcatel-lucent.com>, "tictoc@ietf.org" <tictoc@ietf.org>
Thread-Topic: Transporting PTP messages (1588) over MPLS Networks
Thread-Index: Acu0ostDa6CYok1lRYSvUt8QtgvK+QCglNPw
Date: Tue, 18 Jan 2011 15:45:13 +0000
Message-ID: <07F7D7DED63154409F13298786A2ADC903CD4A65@EXRAD5.ad.rad.co.il>
References: <7C362EEF9C7896468B36C9B79200D8350CFB0DF1AE@INBANSXCHMBSA1.in.alcatel-lucent.com>
In-Reply-To: <7C362EEF9C7896468B36C9B79200D8350CFB0DF1AE@INBANSXCHMBSA1.in.alcatel-lucent.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [192.115.243.62]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: Re: [TICTOC] Transporting PTP messages (1588) over MPLS Networks
X-BeenThere: tictoc@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Timing over IP Connection and Transfer of Clock BOF <tictoc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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, 18 Jan 2011 15:43:22 -0000

Manav and co-authors,=20

I just started reading the document, and have a few comments.

First, as we have stated a few times already, TICTOC is looking for a unifi=
ed solution
for carrying timing flows over MPLS, not just 1588. Although this doesn't n=
ecessarily
mean that a single document explains both, if we have two separate document=
s,
or worse, only a 1588 document, we will not accomplish what we are intendin=
g.

Second, the following wording is not going to fly in the IETF.
   This document requires that MLPS nodes (LSRs) SHOULD be able to support =
TC, ...
   Such an LSR is referred to as a "1588-aware LSR" in this document.
As written this means that if this document becomes a proposed standard RFC=
,=20
then every LSR manufactured will have to support identification of timing f=
lows
(remember SHOULD means MUST unless there is a very good reason no to).
This, of course, means that almost every LSR will need to be "1588-aware"=20
and there is no need to define the term.

I believe that what you mean to says is something like this.
   This document defines a "1588-aware LSR" that is able to identify 1588 t=
iming flows
   carried over MPLS.

Third, and more controversially, I believe we should be more modest in our =
MUSTs here.
I would prefer that a "1588-aware" LSR MUST to be able to identify for prio=
ritization,
and MAY be able to correct the correction field.

I have a few more minor comments (e.g., you speak of correcting FCS for the=
 PW FCS retention mode=20
of Ethernet PWS, but don't discuss correcting the UDP checksum (which in IP=
v6 is mandatory),
but prefer to clear up the major items first.

Y(J)S


-----Original Message-----
From: tictoc-bounces@ietf.org [mailto:tictoc-bounces@ietf.org] On Behalf Of=
 Bhatia, Manav (Manav)
Sent: Saturday, January 15, 2011 12:56
To: tictoc@ietf.org
Subject: [TICTOC] Transporting PTP messages (1588) over MPLS Networks

Hi,

We have posted a revised version of draft-davari-tictoc-1588overmpls-01 and=
 would appreciate a feedback from the WG.

The draft is available here:
http://www.ietf.org/id/draft-davari-tictoc-1588overmpls-01.txt

Cheers, Manav

--
Manav Bhatia,
IP Division, Alcatel-Lucent,
Bangalore - India

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

From Alexander.Vainshtein@ecitele.com  Tue Jan 18 08:03:07 2011
Return-Path: <Alexander.Vainshtein@ecitele.com>
X-Original-To: tictoc@core3.amsl.com
Delivered-To: tictoc@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 97F3A28C102 for <tictoc@core3.amsl.com>; Tue, 18 Jan 2011 08:03:07 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.381
X-Spam-Level: 
X-Spam-Status: No, score=-2.381 tagged_above=-999 required=5 tests=[AWL=0.218,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id juGS9YW5OSZC for <tictoc@core3.amsl.com>; Tue, 18 Jan 2011 08:03:06 -0800 (PST)
Received: from ilptbmg01.ecitele.com (ilptbmg01-out.ecitele.com [147.234.242.234]) by core3.amsl.com (Postfix) with ESMTP id 143CC28C1B2 for <tictoc@ietf.org>; Tue, 18 Jan 2011 08:03:05 -0800 (PST)
X-AuditID: 93eaf2e7-b7cabae00000475f-b2-4d35ba5800be
Received: from ILPTEXCH02.ecitele.com ( [147.234.245.181]) by ilptbmg01.ecitele.com (Symantec Brightmail Gateway) with SMTP id 33.25.18271.85AB53D4; Tue, 18 Jan 2011 18:05:44 +0200 (IST)
Received: from ILPTMAIL02.ecitele.com ([147.234.244.212]) by ILPTEXCH02.ecitele.com ([147.234.245.181]) with mapi; Tue, 18 Jan 2011 18:07:29 +0200
From: Alexander Vainshtein <Alexander.Vainshtein@ecitele.com>
To: Yaakov Stein <yaakov_s@rad.com>
Date: Tue, 18 Jan 2011 18:05:38 +0200
Thread-Topic: Transporting PTP messages (1588) over MPLS Networks
Thread-Index: Acu0ostDa6CYok1lRYSvUt8QtgvK+QCglNPwAAB/C+A=
Message-ID: <A3C5DF08D38B6049839A6F553B331C76D6B87EA3C6@ILPTMAIL02.ecitele.com>
References: <7C362EEF9C7896468B36C9B79200D8350CFB0DF1AE@INBANSXCHMBSA1.in.alcatel-lucent.com> <07F7D7DED63154409F13298786A2ADC903CD4A65@EXRAD5.ad.rad.co.il>
In-Reply-To: <07F7D7DED63154409F13298786A2ADC903CD4A65@EXRAD5.ad.rad.co.il>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-CFilter-Loop: Reflected
X-Brightmail-Tracker: AAAAAA==
Cc: "tictoc@ietf.org" <tictoc@ietf.org>
Subject: Re: [TICTOC] Transporting PTP messages (1588) over MPLS Networks
X-BeenThere: tictoc@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Timing over IP Connection and Transfer of Clock BOF <tictoc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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, 18 Jan 2011 16:03:07 -0000

Yaakov,=20
You've said:
=09
	I believe we should be more modest in our MUSTs here.
	I would prefer that a "1588-aware" LSR MUST to be able to identify [PTP tr=
affic - Sasha]=20
	for prioritization, and MAY be able to correct the correction field.

I concur with you regarding the level of requirements.=20
Editorially, I think that "to correct the correction field" is an pleonasm =
that SHOULD be corrected.


Regards,
     Sasha

-----Original Message-----
From: tictoc-bounces@ietf.org [mailto:tictoc-bounces@ietf.org] On Behalf Of=
 Yaakov Stein
Sent: Tuesday, January 18, 2011 5:45 PM
To: Bhatia, Manav (Manav); tictoc@ietf.org
Subject: Re: [TICTOC] Transporting PTP messages (1588) over MPLS Networks

Manav and co-authors,=20

I just started reading the document, and have a few comments.

First, as we have stated a few times already, TICTOC is looking for a unifi=
ed solution
for carrying timing flows over MPLS, not just 1588. Although this doesn't n=
ecessarily
mean that a single document explains both, if we have two separate document=
s,
or worse, only a 1588 document, we will not accomplish what we are intendin=
g.

Second, the following wording is not going to fly in the IETF.
   This document requires that MLPS nodes (LSRs) SHOULD be able to support =
TC, ...
   Such an LSR is referred to as a "1588-aware LSR" in this document.
As written this means that if this document becomes a proposed standard RFC=
,=20
then every LSR manufactured will have to support identification of timing f=
lows
(remember SHOULD means MUST unless there is a very good reason no to).
This, of course, means that almost every LSR will need to be "1588-aware"=20
and there is no need to define the term.

I believe that what you mean to says is something like this.
   This document defines a "1588-aware LSR" that is able to identify 1588 t=
iming flows
   carried over MPLS.

Third, and more controversially, I believe we should be more modest in our =
MUSTs here.
I would prefer that a "1588-aware" LSR MUST to be able to identify for prio=
ritization,
and MAY be able to correct the correction field.

I have a few more minor comments (e.g., you speak of correcting FCS for the=
 PW FCS retention mode=20
of Ethernet PWS, but don't discuss correcting the UDP checksum (which in IP=
v6 is mandatory),
but prefer to clear up the major items first.

Y(J)S


-----Original Message-----
From: tictoc-bounces@ietf.org [mailto:tictoc-bounces@ietf.org] On Behalf Of=
 Bhatia, Manav (Manav)
Sent: Saturday, January 15, 2011 12:56
To: tictoc@ietf.org
Subject: [TICTOC] Transporting PTP messages (1588) over MPLS Networks

Hi,

We have posted a revised version of draft-davari-tictoc-1588overmpls-01 and=
 would appreciate a feedback from the WG.

The draft is available here:
http://www.ietf.org/id/draft-davari-tictoc-1588overmpls-01.txt

Cheers, Manav

--
Manav Bhatia,
IP Division, Alcatel-Lucent,
Bangalore - India

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

From ronc.ntear@gmail.com  Tue Jan 18 08:04:18 2011
Return-Path: <ronc.ntear@gmail.com>
X-Original-To: tictoc@core3.amsl.com
Delivered-To: tictoc@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id A8BF228C102 for <tictoc@core3.amsl.com>; Tue, 18 Jan 2011 08:04:18 -0800 (PST)
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.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id o616WbcwJUVw for <tictoc@core3.amsl.com>; Tue, 18 Jan 2011 08:04:17 -0800 (PST)
Received: from mail-wy0-f172.google.com (mail-wy0-f172.google.com [74.125.82.172]) by core3.amsl.com (Postfix) with ESMTP id 19EAE3A6F49 for <tictoc@ietf.org>; Tue, 18 Jan 2011 08:04:16 -0800 (PST)
Received: by wyf23 with SMTP id 23so6635079wyf.31 for <tictoc@ietf.org>; Tue, 18 Jan 2011 08:06:54 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=VdU3f6lFjaFsOinEiN5lWd4/D4CzUGwPIMcBfxUNiHk=; b=k++eu68fNymivnOyptyC19WIwtYR83jYt2Bc4Cw6GEgn6A8xDp/IC0sj2X7FF+dBwU bjQIDQHNQCfy3On7sYcOVCooumVmaFwlDf1S7cK8ZHltr4k7PWOwpYIJuhcerRwroXGt Qxr4NpFdlYnvc6BRePcMvEf23Gmkk7hkLf5rc=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=iJOXI2jxcXbJlZufBw1yxuTN8dyZcyVmmcON8SUvGiZC2Q+DRomjbzb7CJBngAeqg0 yWCY5N28i8FSuz+SooRfkTgzQDw+58MAyqewEHkTo5/WSlFc5ejo2WDp1uEnNCM9hyLn EQpgLSDtqAHeKXbDOZ7RTou+f8HIlXJtzptdY=
MIME-Version: 1.0
Received: by 10.216.160.129 with SMTP id u1mr1295560wek.88.1295366813925; Tue, 18 Jan 2011 08:06:53 -0800 (PST)
Received: by 10.216.167.69 with HTTP; Tue, 18 Jan 2011 08:06:53 -0800 (PST)
In-Reply-To: <07F7D7DED63154409F13298786A2ADC903CD4A65@EXRAD5.ad.rad.co.il>
References: <7C362EEF9C7896468B36C9B79200D8350CFB0DF1AE@INBANSXCHMBSA1.in.alcatel-lucent.com> <07F7D7DED63154409F13298786A2ADC903CD4A65@EXRAD5.ad.rad.co.il>
Date: Tue, 18 Jan 2011 18:06:53 +0200
Message-ID: <AANLkTin39NE0t-mz3HN0NOvcRbPY+=L91oV4H-Yq=vw=@mail.gmail.com>
From: Ron Cohen <ronc.ntear@gmail.com>
To: Yaakov Stein <yaakov_s@rad.com>
Content-Type: multipart/alternative; boundary=0016e64985b0cc41b4049a2116d5
Cc: "tictoc@ietf.org" <tictoc@ietf.org>
Subject: Re: [TICTOC] Transporting PTP messages (1588) over MPLS Networks
X-BeenThere: tictoc@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Timing over IP Connection and Transfer of Clock BOF <tictoc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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, 18 Jan 2011 16:04:18 -0000

--0016e64985b0cc41b4049a2116d5
Content-Type: text/plain; charset=ISO-8859-1

A quick question: I assume that there will be LSRs which have some ports
with PTP support and some ports which are not. I think we should address
this as well. Best, Ron

On Tue, Jan 18, 2011 at 5:45 PM, Yaakov Stein <yaakov_s@rad.com> wrote:

> Manav and co-authors,
>
> I just started reading the document, and have a few comments.
>
> First, as we have stated a few times already, TICTOC is looking for a
> unified solution
> for carrying timing flows over MPLS, not just 1588. Although this doesn't
> necessarily
> mean that a single document explains both, if we have two separate
> documents,
> or worse, only a 1588 document, we will not accomplish what we are
> intending.
>
> Second, the following wording is not going to fly in the IETF.
>   This document requires that MLPS nodes (LSRs) SHOULD be able to support
> TC, ...
>   Such an LSR is referred to as a "1588-aware LSR" in this document.
> As written this means that if this document becomes a proposed standard
> RFC,
> then every LSR manufactured will have to support identification of timing
> flows
> (remember SHOULD means MUST unless there is a very good reason no to).
> This, of course, means that almost every LSR will need to be "1588-aware"
> and there is no need to define the term.
>
> I believe that what you mean to says is something like this.
>   This document defines a "1588-aware LSR" that is able to identify 1588
> timing flows
>   carried over MPLS.
>
> Third, and more controversially, I believe we should be more modest in our
> MUSTs here.
> I would prefer that a "1588-aware" LSR MUST to be able to identify for
> prioritization,
> and MAY be able to correct the correction field.
>
> I have a few more minor comments (e.g., you speak of correcting FCS for the
> PW FCS retention mode
> of Ethernet PWS, but don't discuss correcting the UDP checksum (which in
> IPv6 is mandatory),
> but prefer to clear up the major items first.
>
> Y(J)S
>
>
> -----Original Message-----
> From: tictoc-bounces@ietf.org [mailto:tictoc-bounces@ietf.org] On Behalf
> Of Bhatia, Manav (Manav)
> Sent: Saturday, January 15, 2011 12:56
> To: tictoc@ietf.org
> Subject: [TICTOC] Transporting PTP messages (1588) over MPLS Networks
>
> Hi,
>
> We have posted a revised version of draft-davari-tictoc-1588overmpls-01 and
> would appreciate a feedback from the WG.
>
> The draft is available here:
> http://www.ietf.org/id/draft-davari-tictoc-1588overmpls-01.txt
>
> Cheers, Manav
>
> --
> Manav Bhatia,
> IP Division, Alcatel-Lucent,
> Bangalore - India
>
>
> _______________________________________________
> TICTOC mailing list
> TICTOC@ietf.org
> https://www.ietf.org/mailman/listinfo/tictoc
> _______________________________________________
> TICTOC mailing list
> TICTOC@ietf.org
> https://www.ietf.org/mailman/listinfo/tictoc
>

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

<div dir=3D"ltr">A quick question: I assume that there will be LSRs which h=
ave some ports with PTP support and some ports which are not. I think we sh=
ould address this as well. Best, Ron<br><br><div class=3D"gmail_quote">On T=
ue, Jan 18, 2011 at 5:45 PM, Yaakov Stein <span dir=3D"ltr">&lt;<a href=3D"=
mailto:yaakov_s@rad.com" target=3D"_blank">yaakov_s@rad.com</a>&gt;</span> =
wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin: 0pt 0pt 0pt 0.8ex; borde=
r-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
Manav and co-authors,<br>
<br>
I just started reading the document, and have a few comments.<br>
<br>
First, as we have stated a few times already, TICTOC is looking for a unifi=
ed solution<br>
for carrying timing flows over MPLS, not just 1588. Although this doesn&#39=
;t necessarily<br>
mean that a single document explains both, if we have two separate document=
s,<br>
or worse, only a 1588 document, we will not accomplish what we are intendin=
g.<br>
<br>
Second, the following wording is not going to fly in the IETF.<br>
 =A0 This document requires that MLPS nodes (LSRs) SHOULD be able to suppor=
t TC, ...<br>
 =A0 Such an LSR is referred to as a &quot;1588-aware LSR&quot; in this doc=
ument.<br>
As written this means that if this document becomes a proposed standard RFC=
,<br>
then every LSR manufactured will have to support identification of timing f=
lows<br>
(remember SHOULD means MUST unless there is a very good reason no to).<br>
This, of course, means that almost every LSR will need to be &quot;1588-awa=
re&quot;<br>
and there is no need to define the term.<br>
<br>
I believe that what you mean to says is something like this.<br>
 =A0 This document defines a &quot;1588-aware LSR&quot; that is able to ide=
ntify 1588 timing flows<br>
 =A0 carried over MPLS.<br>
<br>
Third, and more controversially, I believe we should be more modest in our =
MUSTs here.<br>
I would prefer that a &quot;1588-aware&quot; LSR MUST to be able to identif=
y for prioritization,<br>
and MAY be able to correct the correction field.<br>
<br>
I have a few more minor comments (e.g., you speak of correcting FCS for the=
 PW FCS retention mode<br>
of Ethernet PWS, but don&#39;t discuss correcting the UDP checksum (which i=
n IPv6 is mandatory),<br>
but prefer to clear up the major items first.<br>
<br>
Y(J)S<br>
<div><br>
<br>
-----Original Message-----<br>
From: <a href=3D"mailto:tictoc-bounces@ietf.org" target=3D"_blank">tictoc-b=
ounces@ietf.org</a> [mailto:<a href=3D"mailto:tictoc-bounces@ietf.org" targ=
et=3D"_blank">tictoc-bounces@ietf.org</a>] On Behalf Of Bhatia, Manav (Mana=
v)<br>

Sent: Saturday, January 15, 2011 12:56<br>
</div><div>To: <a href=3D"mailto:tictoc@ietf.org" target=3D"_blank">tictoc@=
ietf.org</a><br>
Subject: [TICTOC] Transporting PTP messages (1588) over MPLS Networks<br>
<br>
</div><div><div></div><div>Hi,<br>
<br>
We have posted a revised version of draft-davari-tictoc-1588overmpls-01 and=
 would appreciate a feedback from the WG.<br>
<br>
The draft is available here:<br>
<a href=3D"http://www.ietf.org/id/draft-davari-tictoc-1588overmpls-01.txt" =
target=3D"_blank">http://www.ietf.org/id/draft-davari-tictoc-1588overmpls-0=
1.txt</a><br>
<br>
Cheers, Manav<br>
<br>
--<br>
Manav Bhatia,<br>
IP Division, Alcatel-Lucent,<br>
Bangalore - India<br>
<br>
<br>
_______________________________________________<br>
TICTOC mailing list<br>
<a href=3D"mailto:TICTOC@ietf.org" target=3D"_blank">TICTOC@ietf.org</a><br=
>
<a href=3D"https://www.ietf.org/mailman/listinfo/tictoc" target=3D"_blank">=
https://www.ietf.org/mailman/listinfo/tictoc</a><br>
_______________________________________________<br>
TICTOC mailing list<br>
<a href=3D"mailto:TICTOC@ietf.org" target=3D"_blank">TICTOC@ietf.org</a><br=
>
<a href=3D"https://www.ietf.org/mailman/listinfo/tictoc" target=3D"_blank">=
https://www.ietf.org/mailman/listinfo/tictoc</a><br>
</div></div></blockquote></div><br><div style=3D"padding: 0px; margin-left:=
 0px; margin-top: 0px; overflow: hidden; word-wrap: break-word; color: blac=
k; font-size: 10px; text-align: left; line-height: 130%;">
</div><div style=3D"visibility: hidden; left: -5000px; position: absolute; =
z-index: 9999; padding: 0px; margin-left: 0px; margin-top: 0px; overflow: h=
idden; word-wrap: break-word; color: black; font-size: 10px; text-align: le=
ft; line-height: 130%;" id=3D"avg_ls_inline_popup">
</div></div>

--0016e64985b0cc41b4049a2116d5--

From yaakov_s@rad.com  Tue Jan 18 09:42:33 2011
Return-Path: <yaakov_s@rad.com>
X-Original-To: tictoc@core3.amsl.com
Delivered-To: tictoc@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id D8FED3A6E78 for <tictoc@core3.amsl.com>; Tue, 18 Jan 2011 09:42:33 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.194
X-Spam-Level: 
X-Spam-Status: No, score=-102.194 tagged_above=-999 required=5 tests=[AWL=-0.196, BAYES_00=-2.599, HTML_MESSAGE=0.001, J_CHICKENPOX_33=0.6, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ZTI6GZikscQv for <tictoc@core3.amsl.com>; Tue, 18 Jan 2011 09:42:32 -0800 (PST)
Received: from antivir2.rad.co.il (mx2-q.rad.co.il [80.74.100.144]) by core3.amsl.com (Postfix) with ESMTP id 5527528C0FA for <tictoc@ietf.org>; Tue, 18 Jan 2011 09:42:29 -0800 (PST)
Received: from unknown (HELO EXRAD5.ad.rad.co.il) ([192.114.24.28]) by antivir2.rad.co.il with ESMTP; 18 Jan 2011 19:44:52 +0200
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; Tue, 18 Jan 2011 19:44:35 +0200
Received: from EXRAD5.ad.rad.co.il ([fe80::ec3e:feb5:8bef:e3ba]) by exus4-drp.ad.rad.co.il ([fe80::5d6f:c2cb:2468:ee2%16]) with mapi id 14.01.0270.001; Tue, 18 Jan 2011 19:44:35 +0200
From: Yaakov Stein <yaakov_s@rad.com>
To: "tictoc@ietf.org" <tictoc@ietf.org>
Thread-Topic: minutes of TICTOC conference call - Jan 18, 2011
Thread-Index: Acu3N10fvrNNbaKTRqCEJBiGn8t8bA==
Date: Tue, 18 Jan 2011 17:44:34 +0000
Message-ID: <07F7D7DED63154409F13298786A2ADC903CD4B30@EXRAD5.ad.rad.co.il>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-cr-puzzleid: {2E76B909-CB3E-4D9F-B538-2B5B3CB481F6}
x-cr-hashedpuzzle: ATtq AxdF BOjy BR5J Bi/c CnJP C2y/ DxVO Eami FFmh FQAA G906 HnoH IOn2 IYOO J4Yj; 1; dABpAGMAdABvAGMAQABpAGUAdABmAC4AbwByAGcA; Sosha1_v1; 7; {2E76B909-CB3E-4D9F-B538-2B5B3CB481F6}; eQBhAGEAawBvAHYAXwBzAEAAcgBhAGQALgBjAG8AbQA=; Tue, 18 Jan 2011 17:44:32 GMT; bQBpAG4AdQB0AGUAcwAgAG8AZgAgAFQASQBDAFQATwBDACAAYwBvAG4AZgBlAHIAZQBuAGMAZQAgAGMAYQBsAGwAIAAtACAASgBhAG4AIAAxADgALAAgADIAMAAxADEA
x-originating-ip: [192.115.243.62]
Content-Type: multipart/alternative; boundary="_000_07F7D7DED63154409F13298786A2ADC903CD4B30EXRAD5adradcoil_"
MIME-Version: 1.0
Subject: [TICTOC] minutes of TICTOC conference call - Jan 18, 2011
X-BeenThere: tictoc@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Timing over IP Connection and Transfer of Clock BOF <tictoc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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, 18 Jan 2011 17:42:34 -0000

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

TICTOC conference call
18 January, 2011
Participating :
Karen (hosted WebEx), Yaakov (minutes scribe), Shahram, Stefano, Manav, Gre=
g, Ron Cohen, Tal Mizrahi, Peter Roberts

Karen opened the call, stating that the main item for discussion was the ne=
w version of the 1588overmpls draft,
with management and security issues after that if time allowed.

Yaakov mentioned the main problems he identified with the draft :
1) a wording issue regarding whether the LSR support was mandatory (Shahram=
 said it wasn't)
2) whether NTP would be covered in the same draft
3) why only OSPF and RSVP were covered, and not IS-IS and LDP.

Shahram said that NTP and IS-IS were not covered due to lack of expertise.
Manav said that IS-IS could certainly be added.
Shahram said that LDP of the PWE3 control protocol needed to be added due t=
o the possibility of PHP'ing the tunnel label.

Yaakov asked whether the wording on page 10 "the top label" was intentional=
,
and Shahram explained that it was! There needed to be only a single PW per =
tunnel,
and if there were multiple labels in the stack, the top one needed to be si=
gnaled.
This saves DPI (but Yaakov stated that there was still a lot of deep correc=
tion).

Ron asked whether the draft could be extended to handle LSRs that did not s=
upport TC correction on ALL ports,
but only on those needed for the timing flow. This would require additional=
 port capabilities description.
Manav said that this could be done in OSPF-TE.
Ron stressed the importance of this feature.

Stefano asked why this draft was limited to PTP and not (for example) NTP.
Ron said that the entire idea was to support the TC correction field,
and that prioritization could be accomplished without a new draft.
Yaakov said that prioritization (e.g., EF) could indeed be covered in a BCP=
 rather than a PS RFC,
but if BC was required for PTP or NTP, then the techniques defined here wer=
e still needed.
Manav suggested that NTP was so different that it should be handled in a se=
parate draft.
Karen said that it was preferable to have a single draft to ensure consiste=
ncy.
Shahram proposed that Yaakov write a problem statement for NTP, and afterwa=
rds it could be decided
if this could be added to this draft, or if a separate document was needed.

Ron stated that the encapsulation was general enough to support a pure MPLS=
 mode (without UDP/IP or Ethernet).
Shahram said that he preferred to avoid this, as it would require further I=
EEE and IETF work.
Ron said that the IEEE already granted authority to the IETF to devise such=
 an encapsulation.
Yaakov said that only a simple PWE3 draft would be needed to define a new P=
W type.
It was decided that this needed to be discussed further.

Ron and Yaakov raised the point of UDP checksum correction
(FCS correction for retention mode is mentioned in the draft, but not UDP c=
hecksum).
Shahram asked if checksum is mandatory.
Yaakov replied that it is optional in IPv4, but mandatory in IPv6.
Shahram asked whether the checksum could be corrected rather than recalcula=
ted.
Yaakov said yes.
Shahram said that since the UDP mode over IPv6 is supported by the availabl=
e chipsets,
apparently they already do the correction.

Ron asked how the OAM packets that are carried in the same tunnel are ident=
ified.
Yaakov asked if it is always in a VCCV channel.
Shahram said that for the Ethernet PW approach it was VCCV (either BFD or L=
SP ping)
while for the UDP/IP it was via UDP port number.
Ron asked for clear text to be added, so that later on new packet types cou=
ld be added.

Karen said that we want to advance this draft to WG draft before the next m=
eeting.
We don't need to finalize all the open items first.
Shahram and Manav reiterated that this draft has been a long time in maturi=
ng,
and that its handling should be expedited.

At this point there were only 5 minutes left, and there was no time to star=
t a new topic.

Karen announced that the next conference call would be the third Tuesday in=
 Feb (Feb 15th).
Stefano said that this would fall during the ITU-T meeting.
Yaakov said that this could still work if interested Q13 participants joine=
d after the sessions.
Stefano said that this would require the call being 1 hour later (18:00 Gen=
eva time),
and only if there were no late joint meetings planned.

Action items :
1) Yaakov will send a mail to the list with an explanation of what was need=
ed for NTP
2) Shahram and Manav will respin the draft as a WG draft as soon as permiss=
ion is given.
3) Needed changes:
   a) fix wording on mandatory nature of 1588 support
   b) add IS-IS text, or at least a place-holder for such text
   c) add LDP-4447 text, or at least a place holder for such text
   d) fix up the IANA considerations section
   e) add text regarding per-port support, or an editor's note that this ne=
eds to be covered
   f) add text on UDP checksum correction
   g) add text explaining how OAM packets are separated from PTP ones (ASCI=
I art? pseudocode?)
   h) fixes mentioned on list (border clock, transparent clocking, ...)
4) Stefano will check whether Feb 15th at 18:00 Geneva time is suitable.
5) Karen will set up another meeting accordingly.


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

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:x=3D"urn:schemas-microsoft-com:office:excel" xmlns:p=3D"urn:schemas-m=
icrosoft-com:office:powerpoint" xmlns:a=3D"urn:schemas-microsoft-com:office=
:access" xmlns:dt=3D"uuid:C2F41010-65B3-11d1-A29F-00AA00C14882" xmlns:s=3D"=
uuid:BDC6E3F0-6DA3-11d1-A2A3-00AA00C14882" xmlns:rs=3D"urn:schemas-microsof=
t-com:rowset" xmlns:z=3D"#RowsetSchema" xmlns:b=3D"urn:schemas-microsoft-co=
m:office:publisher" xmlns:ss=3D"urn:schemas-microsoft-com:office:spreadshee=
t" xmlns:c=3D"urn:schemas-microsoft-com:office:component:spreadsheet" xmlns=
:odc=3D"urn:schemas-microsoft-com:office:odc" xmlns:oa=3D"urn:schemas-micro=
soft-com:office:activation" xmlns:html=3D"http://www.w3.org/TR/REC-html40" =
xmlns:q=3D"http://schemas.xmlsoap.org/soap/envelope/" xmlns:rtc=3D"http://m=
icrosoft.com/officenet/conferencing" xmlns:D=3D"DAV:" xmlns:Repl=3D"http://=
schemas.microsoft.com/repl/" xmlns:mt=3D"http://schemas.microsoft.com/share=
point/soap/meetings/" xmlns:x2=3D"http://schemas.microsoft.com/office/excel=
/2003/xml" xmlns:ppda=3D"http://www.passport.com/NameSpace.xsd" xmlns:ois=
=3D"http://schemas.microsoft.com/sharepoint/soap/ois/" xmlns:dir=3D"http://=
schemas.microsoft.com/sharepoint/soap/directory/" xmlns:ds=3D"http://www.w3=
.org/2000/09/xmldsig#" xmlns:dsp=3D"http://schemas.microsoft.com/sharepoint=
/dsp" xmlns:udc=3D"http://schemas.microsoft.com/data/udc" xmlns:xsd=3D"http=
://www.w3.org/2001/XMLSchema" xmlns:sub=3D"http://schemas.microsoft.com/sha=
repoint/soap/2002/1/alerts/" xmlns:ec=3D"http://www.w3.org/2001/04/xmlenc#"=
 xmlns:sp=3D"http://schemas.microsoft.com/sharepoint/" xmlns:sps=3D"http://=
schemas.microsoft.com/sharepoint/soap/" xmlns:xsi=3D"http://www.w3.org/2001=
/XMLSchema-instance" xmlns:udcs=3D"http://schemas.microsoft.com/data/udc/so=
ap" xmlns:udcxf=3D"http://schemas.microsoft.com/data/udc/xmlfile" xmlns:udc=
p2p=3D"http://schemas.microsoft.com/data/udc/parttopart" xmlns:wf=3D"http:/=
/schemas.microsoft.com/sharepoint/soap/workflow/" xmlns:dsss=3D"http://sche=
mas.microsoft.com/office/2006/digsig-setup" xmlns:dssi=3D"http://schemas.mi=
crosoft.com/office/2006/digsig" xmlns:mdssi=3D"http://schemas.openxmlformat=
s.org/package/2006/digital-signature" xmlns:mver=3D"http://schemas.openxmlf=
ormats.org/markup-compatibility/2006" xmlns:m=3D"http://schemas.microsoft.c=
om/office/2004/12/omml" xmlns:mrels=3D"http://schemas.openxmlformats.org/pa=
ckage/2006/relationships" xmlns:spwp=3D"http://microsoft.com/sharepoint/web=
partpages" xmlns:ex12t=3D"http://schemas.microsoft.com/exchange/services/20=
06/types" xmlns:ex12m=3D"http://schemas.microsoft.com/exchange/services/200=
6/messages" xmlns:pptsl=3D"http://schemas.microsoft.com/sharepoint/soap/Sli=
deLibrary/" xmlns:spsl=3D"http://microsoft.com/webservices/SharePointPortal=
Server/PublishedLinksService" xmlns:Z=3D"urn:schemas-microsoft-com:" xmlns:=
st=3D"&#1;" xmlns=3D"http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
<meta name=3D"Generator" content=3D"Microsoft Word 12 (filtered medium)">
<style>
<!--
 /* Font Definitions */
 @font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	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;}
@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">TICTOC conference call<o:p></o:p></p>
<p class=3D"MsoNormal">18 January, 2011<o:p></o:p></p>
<p class=3D"MsoNormal">Participating :<o:p></o:p></p>
<p class=3D"MsoNormal">Karen (hosted WebEx), Yaakov (minutes scribe), Shahr=
am, Stefano, Manav, Greg, Ron Cohen, Tal Mizrahi, Peter Roberts<o:p></o:p><=
/p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Karen opened the call, stating that the main item fo=
r discussion was the new version of the 1588overmpls draft,<o:p></o:p></p>
<p class=3D"MsoNormal">with management and security issues after that if ti=
me allowed.<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Yaakov mentioned the main problems he identified wit=
h the draft :<o:p></o:p></p>
<p class=3D"MsoNormal">1) a wording issue regarding whether the LSR support=
 was mandatory (Shahram said it wasn't)<o:p></o:p></p>
<p class=3D"MsoNormal">2) whether NTP would be covered in the same draft<o:=
p></o:p></p>
<p class=3D"MsoNormal">3) why only OSPF and RSVP were covered, and not IS-I=
S and LDP.<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Shahram said that NTP and IS-IS were not covered due=
 to lack of expertise.<o:p></o:p></p>
<p class=3D"MsoNormal">Manav said that IS-IS could certainly be added.<o:p>=
</o:p></p>
<p class=3D"MsoNormal">Shahram said that LDP of the PWE3 control protocol n=
eeded to be added due to the possibility of PHP'ing the tunnel label.<o:p><=
/o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Yaakov asked whether the wording on page 10 &quot;th=
e top label&quot; was intentional,<o:p></o:p></p>
<p class=3D"MsoNormal">and Shahram explained that it was! There needed to b=
e only a single PW per tunnel,<o:p></o:p></p>
<p class=3D"MsoNormal">and if there were multiple labels in the stack, the =
top one needed to be signaled.<o:p></o:p></p>
<p class=3D"MsoNormal">This saves DPI (but Yaakov stated that there was sti=
ll a lot of deep correction).<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Ron asked whether the draft could be extended to han=
dle LSRs that did not support TC correction on ALL ports,
<o:p></o:p></p>
<p class=3D"MsoNormal">but only on those needed for the timing flow. This w=
ould require additional port capabilities description.
<o:p></o:p></p>
<p class=3D"MsoNormal">Manav said that this could be done in OSPF-TE.<o:p><=
/o:p></p>
<p class=3D"MsoNormal">Ron stressed the importance of this feature.<o:p></o=
:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Stefano asked why this draft was limited to PTP and =
not (for example) NTP.<o:p></o:p></p>
<p class=3D"MsoNormal">Ron said that the entire idea was to support the TC =
correction field,
<o:p></o:p></p>
<p class=3D"MsoNormal">and that prioritization could be accomplished withou=
t a new draft.<o:p></o:p></p>
<p class=3D"MsoNormal">Yaakov said that prioritization (e.g., EF) could ind=
eed be covered in a BCP rather than a PS RFC,<o:p></o:p></p>
<p class=3D"MsoNormal">but if BC was required for PTP or NTP, then the tech=
niques defined here were still needed.
<o:p></o:p></p>
<p class=3D"MsoNormal">Manav suggested that NTP was so different that it sh=
ould be handled in a separate draft.<o:p></o:p></p>
<p class=3D"MsoNormal">Karen said that it was preferable to have a single d=
raft to ensure consistency.<o:p></o:p></p>
<p class=3D"MsoNormal">Shahram proposed that Yaakov write a problem stateme=
nt for NTP, and afterwards it could be decided<o:p></o:p></p>
<p class=3D"MsoNormal">if this could be added to this draft, or if a separa=
te document was needed.<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Ron stated that the encapsulation was general enough=
 to support a pure MPLS mode (without UDP/IP or Ethernet).
<o:p></o:p></p>
<p class=3D"MsoNormal">Shahram said that he preferred to avoid this, as it =
would require further IEEE and IETF work.<o:p></o:p></p>
<p class=3D"MsoNormal">Ron said that the IEEE already granted authority to =
the IETF to devise such an encapsulation.<o:p></o:p></p>
<p class=3D"MsoNormal">Yaakov said that only a simple PWE3 draft would be n=
eeded to define a new PW type.<o:p></o:p></p>
<p class=3D"MsoNormal">It was decided that this needed to be discussed furt=
her.<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Ron and Yaakov raised the point of UDP checksum corr=
ection <o:p>
</o:p></p>
<p class=3D"MsoNormal">(FCS correction for retention mode is mentioned in t=
he draft, but not UDP checksum).
<o:p></o:p></p>
<p class=3D"MsoNormal">Shahram asked if checksum is mandatory.<o:p></o:p></=
p>
<p class=3D"MsoNormal">Yaakov replied that it is optional in IPv4, but mand=
atory in IPv6.<o:p></o:p></p>
<p class=3D"MsoNormal">Shahram asked whether the checksum could be correcte=
d rather than recalculated.
<o:p></o:p></p>
<p class=3D"MsoNormal">Yaakov said yes.<o:p></o:p></p>
<p class=3D"MsoNormal">Shahram said that since the UDP mode over IPv6 is su=
pported by the available chipsets,<o:p></o:p></p>
<p class=3D"MsoNormal">apparently they already do the correction.<o:p></o:p=
></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Ron asked how the OAM packets that are carried in th=
e same tunnel are identified.<o:p></o:p></p>
<p class=3D"MsoNormal">Yaakov asked if it is always in a VCCV channel.<o:p>=
</o:p></p>
<p class=3D"MsoNormal">Shahram said that for the Ethernet PW approach it wa=
s VCCV (either BFD or LSP ping)<o:p></o:p></p>
<p class=3D"MsoNormal">while for the UDP/IP it was via UDP port number.<o:p=
></o:p></p>
<p class=3D"MsoNormal">Ron asked for clear text to be added, so that later =
on new packet types could be added.<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Karen said that we want to advance this draft to WG =
draft before the next meeting.<o:p></o:p></p>
<p class=3D"MsoNormal">We don't need to finalize all the open items first.<=
o:p></o:p></p>
<p class=3D"MsoNormal">Shahram and Manav reiterated that this draft has bee=
n a long time in maturing,<o:p></o:p></p>
<p class=3D"MsoNormal">and that its handling should be expedited.<o:p></o:p=
></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">At this point there were only 5 minutes left, and th=
ere was no time to start a new topic.<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Karen announced that the next conference call would =
be the third Tuesday in Feb (Feb 15th).<o:p></o:p></p>
<p class=3D"MsoNormal">Stefano said that this would fall during the ITU-T m=
eeting. <o:p>
</o:p></p>
<p class=3D"MsoNormal">Yaakov said that this could still work if interested=
 Q13 participants joined after the sessions.
<o:p></o:p></p>
<p class=3D"MsoNormal">Stefano said that this would require the call being =
1 hour later (18:00 Geneva time),
<o:p></o:p></p>
<p class=3D"MsoNormal">and only if there were no late joint meetings planne=
d.<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Action items :<o:p></o:p></p>
<p class=3D"MsoNormal">1) Yaakov will send a mail to the list with an expla=
nation of what was needed for NTP<o:p></o:p></p>
<p class=3D"MsoNormal">2) Shahram and Manav will respin the draft as a WG d=
raft as soon as permission is given.<o:p></o:p></p>
<p class=3D"MsoNormal">3) Needed changes:<o:p></o:p></p>
<p class=3D"MsoNormal">&nbsp;&nbsp; a) fix wording on mandatory nature of 1=
588 support<o:p></o:p></p>
<p class=3D"MsoNormal">&nbsp;&nbsp; b) add IS-IS text, or at least a place-=
holder for such text<o:p></o:p></p>
<p class=3D"MsoNormal">&nbsp;&nbsp; c) add LDP-4447 text, or at least a pla=
ce holder for such text<o:p></o:p></p>
<p class=3D"MsoNormal">&nbsp;&nbsp; d) fix up the IANA considerations secti=
on<o:p></o:p></p>
<p class=3D"MsoNormal">&nbsp;&nbsp; e) add text regarding per-port support,=
 or an editor's note that this needs to be covered<o:p></o:p></p>
<p class=3D"MsoNormal">&nbsp;&nbsp; f) add text on UDP checksum correction<=
o:p></o:p></p>
<p class=3D"MsoNormal">&nbsp;&nbsp; g) add text explaining how OAM packets =
are separated from PTP ones (ASCII art? pseudocode?)<o:p></o:p></p>
<p class=3D"MsoNormal">&nbsp;&nbsp; h) fixes mentioned on list (border cloc=
k, transparent clocking, ...)<o:p></o:p></p>
<p class=3D"MsoNormal">4) Stefano will check whether Feb 15th at 18:00 Gene=
va time is suitable.<o:p></o:p></p>
<p class=3D"MsoNormal">5) Karen will set up another meeting accordingly.<o:=
p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
</body>
</html>

--_000_07F7D7DED63154409F13298786A2ADC903CD4B30EXRAD5adradcoil_--

From hingkam16@gmail.com  Tue Jan 18 15:56:07 2011
Return-Path: <hingkam16@gmail.com>
X-Original-To: tictoc@core3.amsl.com
Delivered-To: tictoc@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 97F0E28C0E5 for <tictoc@core3.amsl.com>; Tue, 18 Jan 2011 15:56:07 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.003
X-Spam-Level: 
X-Spam-Status: No, score=-3.003 tagged_above=-999 required=5 tests=[AWL=-0.004, BAYES_00=-2.599, J_CHICKENPOX_33=0.6, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Wi2iYrxMCTh2 for <tictoc@core3.amsl.com>; Tue, 18 Jan 2011 15:56:06 -0800 (PST)
Received: from mail-iw0-f172.google.com (mail-iw0-f172.google.com [209.85.214.172]) by core3.amsl.com (Postfix) with ESMTP id A8F3528C0CF for <tictoc@ietf.org>; Tue, 18 Jan 2011 15:56:06 -0800 (PST)
Received: by iwn40 with SMTP id 40so225662iwn.31 for <tictoc@ietf.org>; Tue, 18 Jan 2011 15:58:45 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=vJtgFead/XOQtgcg0vZy+4CK9HyjgIFBOfGsdrCH/cU=; b=o6OgJBWDmExCbCmRa6XlHbX+gWasL7UJWJXdIBPDiFi+FCJQA12s+ceygUuzJtiBrZ uyPPtFPL8m4Qo04tU2xOP0NJdWOwhPAXnL26RBNj6iZBy9DvaULfU7OouaDaCv1g5Mhq w/EuPWsfc9300pN74BRVO/fqbE7XiU+2Oxgpk=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=rMfEpVUX48Xp/ELZCSkylcbR9ZfMEn+qIEZ48CXMKHPNwc8GYX+qfxAgOctF64JBCp T1p43CbdNqB7NMl62A0uG4ekt4qTOpGOAZaf07SsycI7yFxgPZAsOeLEzieRAuKzWLNQ Emtm0eN0bLFc92TlB1PGtjoRtGOF+MwZFY8s0=
MIME-Version: 1.0
Received: by 10.231.30.71 with SMTP id t7mr7139915ibc.153.1295395125018; Tue, 18 Jan 2011 15:58:45 -0800 (PST)
Received: by 10.231.14.141 with HTTP; Tue, 18 Jan 2011 15:58:44 -0800 (PST)
In-Reply-To: <07F7D7DED63154409F13298786A2ADC903CD4B30@EXRAD5.ad.rad.co.il>
References: <07F7D7DED63154409F13298786A2ADC903CD4B30@EXRAD5.ad.rad.co.il>
Date: Wed, 19 Jan 2011 05:28:44 +0530
Message-ID: <AANLkTim8JSyrhaLbQRfg58iwh12-y6JFEHebziYutMtx@mail.gmail.com>
From: "Hing-Kam (Kam) Lam" <hingkam16@gmail.com>
To: Yaakov Stein <yaakov_s@rad.com>
Content-Type: text/plain; charset=ISO-8859-1
Cc: "tictoc@ietf.org" <tictoc@ietf.org>
Subject: Re: [TICTOC] minutes of TICTOC conference call - Jan 18, 2011
X-BeenThere: tictoc@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Timing over IP Connection and Transfer of Clock BOF <tictoc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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, 18 Jan 2011 23:56:07 -0000

Hi Yaakov,

Thanks for the minutes.

I have a few questions.

> Shahram said that NTP and IS-IS were not covered due to lack of expertise.
>
> Manav said that IS-IS could certainly be added.
>
> Shahram said that LDP of the PWE3 control protocol needed to be added due to
> the possibility of PHP'ing the tunnel label.

I did not understand this point.

> Ron asked whether the draft could be extended to handle LSRs that did not
> support TC correction on ALL ports,
>
> but only on those needed for the timing flow. This would require additional
> port capabilities description.

I would like to understand the utility of such a description. Either
the box is capable of doing TC correction, or it cant. I dont believe
this capability is required per port. Would appreciate if someone can
explain us why?

>
> Manav said that this could be done in OSPF-TE.
>
> Ron stressed the importance of this feature.

Would love to know why.

> Stefano asked why this draft was limited to PTP and not (for example) NTP.
>
> Ron said that the entire idea was to support the TC correction field,
>
> and that prioritization could be accomplished without a new draft.
>
> Yaakov said that prioritization (e.g., EF) could indeed be covered in a BCP
> rather than a PS RFC,

Is this by using the EXP bits?

>
> but if BC was required for PTP or NTP, then the techniques defined here were
> still needed.

You would also require this draft if you did TC.

>
> Ron stated that the encapsulation was general enough to support a pure MPLS
> mode (without UDP/IP or Ethernet).
>
> Shahram said that he preferred to avoid this, as it would require further
> IEEE and IETF work.

Isnt the draft already supporting all encapsulations? In Fig 2 UDP, IP
are all optional. I assumed that it meant that we support all
encapsulations. Also the fact that RSVP was signalling the start of
the PTP packet (which is neat!) indicated that we support everything.
I seem to be missing something here.

>
> Ron said that the IEEE already granted authority to the IETF to devise such
> an encapsulation.
>
> Yaakov said that only a simple PWE3 draft would be needed to define a new PW
> type.
>
> It was decided that this needed to be discussed further.
>
> Ron and Yaakov raised the point of UDP checksum correction

This is only for TC right?

>
> (FCS correction for retention mode is mentioned in the draft, but not UDP
> checksum).
>
> Shahram asked if checksum is mandatory.
>
> Yaakov replied that it is optional in IPv4, but mandatory in IPv6.
>
> Shahram asked whether the checksum could be corrected rather than
> recalculated.
>
> Yaakov said yes.
>
> Shahram said that since the UDP mode over IPv6 is supported by the available
> chipsets,
>
> apparently they already do the correction.
>
>
> Karen said that we want to advance this draft to WG draft before the next
> meeting.
>
> We don't need to finalize all the open items first.

I agree.

Kam

From lizhong.jin@zte.com.cn  Tue Jan 18 17:25:40 2011
Return-Path: <lizhong.jin@zte.com.cn>
X-Original-To: tictoc@core3.amsl.com
Delivered-To: tictoc@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id F28753A6F73 for <tictoc@core3.amsl.com>; Tue, 18 Jan 2011 17:25:39 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.279
X-Spam-Level: 
X-Spam-Status: No, score=-101.279 tagged_above=-999 required=5 tests=[AWL=-0.041, BAYES_00=-2.599, HTML_MESSAGE=0.001, J_CHICKENPOX_33=0.6, RCVD_DOUBLE_IP_LOOSE=0.76, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id S-YBo1gMlSIn for <tictoc@core3.amsl.com>; Tue, 18 Jan 2011 17:25:38 -0800 (PST)
Received: from mx5.zte.com.cn (mx5.zte.com.cn [63.217.80.70]) by core3.amsl.com (Postfix) with ESMTP id BE7E63A6F34 for <tictoc@ietf.org>; Tue, 18 Jan 2011 17:25:37 -0800 (PST)
Received: from [10.30.17.100] by mx5.zte.com.cn with surfront esmtp id 205951930506506; Wed, 19 Jan 2011 09:23:55 +0800 (CST)
Received: from [10.30.3.20] by [192.168.168.16] with StormMail ESMTP id 7288.3461523519; Wed, 19 Jan 2011 09:21:00 +0800 (CST)
Received: from notes_smtp.zte.com.cn ([10.30.1.239]) by mse01.zte.com.cn with ESMTP id p0J1SAYx067915; Wed, 19 Jan 2011 09:28:10 +0800 (GMT-8) (envelope-from lizhong.jin@zte.com.cn)
In-Reply-To: <mailman.2274.1295372554.4689.tictoc@ietf.org>
To: yaakov_s@rad.com
MIME-Version: 1.0
X-Mailer: Lotus Notes Release 6.5.6 March 06, 2007
Message-ID: <OF34B61E44.399CF170-ON4825781D.0007A305-4825781D.00081218@zte.com.cn>
From: lizhong.jin@zte.com.cn
Date: Wed, 19 Jan 2011 09:27:19 +0800
X-MIMETrack: S/MIME Sign by Notes Client on JinLiZhong127666/user/zte_ltd(Release 6.5.6|March 06, 2007) at 2011-01-19 09:28:09, Serialize by Notes Client on JinLiZhong127666/user/zte_ltd(Release 6.5.6|March 06, 2007) at 2011-01-19 09:28:09, Serialize complete at 2011-01-19 09:28:09, S/MIME Sign failed at 2011-01-19 09:28:09: The cryptographic key was not found, Serialize by Router on notes_smtp/zte_ltd(Release 8.5.1FP4|July 25, 2010) at 2011-01-19 09:28:11, Serialize complete at 2011-01-19 09:28:11
Content-Type: multipart/alternative; boundary="=_alternative 000812154825781D_="
X-MAIL: mse01.zte.com.cn p0J1SAYx067915
Cc: tictoc@ietf.org
Subject: Re: [TICTOC] minutes of TICTOC conference call - Jan 18, 2011
X-BeenThere: tictoc@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Timing over IP Connection and Transfer of Clock BOF <tictoc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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, 19 Jan 2011 01:25:40 -0000

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

Hi Yaakov and all,
Because of a trip, I can not attend this conference call. I tend to agree 
that there was still a lot of deep correction, and the encapsulation can 
be a pure MPLS mode (without UDP/IP or Ethernet). Such kind of 
encapsulation would be more effective.

What's more, as I posted on this list, the fat label in PWE3 encapsulation 
should be not be used in this draft.

Regards
Lizhong


> ----------------------------------------------------------------------
> 
> Message: 1
> Date: Tue, 18 Jan 2011 17:44:34 +0000
> From: Yaakov Stein <yaakov_s@rad.com>
> Subject: [TICTOC] minutes of TICTOC conference call - Jan 18, 2011
> To: "tictoc@ietf.org" <tictoc@ietf.org>
> Message-ID:
>    <07F7D7DED63154409F13298786A2ADC903CD4B30@EXRAD5.ad.rad.co.il>
> Content-Type: text/plain; charset="us-ascii"
> 
> TICTOC conference call
> 18 January, 2011
> Participating :
> Karen (hosted WebEx), Yaakov (minutes scribe), Shahram, Stefano, 
> Manav, Greg, Ron Cohen, Tal Mizrahi, Peter Roberts
> 
> Karen opened the call, stating that the main item for discussion was
> the new version of the 1588overmpls draft,
> with management and security issues after that if time allowed.
> 
> Yaakov mentioned the main problems he identified with the draft :
> 1) a wording issue regarding whether the LSR support was mandatory 
> (Shahram said it wasn't)
> 2) whether NTP would be covered in the same draft
> 3) why only OSPF and RSVP were covered, and not IS-IS and LDP.
> 
> Shahram said that NTP and IS-IS were not covered due to lack of 
expertise.
> Manav said that IS-IS could certainly be added.
> Shahram said that LDP of the PWE3 control protocol needed to be 
> added due to the possibility of PHP'ing the tunnel label.
> 
> Yaakov asked whether the wording on page 10 "the top label" was 
intentional,
> and Shahram explained that it was! There needed to be only a single 
> PW per tunnel,
> and if there were multiple labels in the stack, the top one needed 
> to be signaled.
> This saves DPI (but Yaakov stated that there was still a lot of deep
> correction).
> 
> Ron asked whether the draft could be extended to handle LSRs that 
> did not support TC correction on ALL ports,
> but only on those needed for the timing flow. This would require 
> additional port capabilities description.
> Manav said that this could be done in OSPF-TE.
> Ron stressed the importance of this feature.
> 
> Stefano asked why this draft was limited to PTP and not (for example) 
NTP.
> Ron said that the entire idea was to support the TC correction field,
> and that prioritization could be accomplished without a new draft.
> Yaakov said that prioritization (e.g., EF) could indeed be covered 
> in a BCP rather than a PS RFC,
> but if BC was required for PTP or NTP, then the techniques defined 
> here were still needed.
> Manav suggested that NTP was so different that it should be handled 
> in a separate draft.
> Karen said that it was preferable to have a single draft to ensure 
> consistency.
> Shahram proposed that Yaakov write a problem statement for NTP, and 
> afterwards it could be decided
> if this could be added to this draft, or if a separate document was 
needed.
> 
> Ron stated that the encapsulation was general enough to support a 
> pure MPLS mode (without UDP/IP or Ethernet).
> Shahram said that he preferred to avoid this, as it would require 
> further IEEE and IETF work.
> Ron said that the IEEE already granted authority to the IETF to 
> devise such an encapsulation.
> Yaakov said that only a simple PWE3 draft would be needed to define 
> a new PW type.
> It was decided that this needed to be discussed further.
> 
> Ron and Yaakov raised the point of UDP checksum correction
> (FCS correction for retention mode is mentioned in the draft, but 
> not UDP checksum).
> Shahram asked if checksum is mandatory.
> Yaakov replied that it is optional in IPv4, but mandatory in IPv6.
> Shahram asked whether the checksum could be corrected rather than 
> recalculated.
> Yaakov said yes.
> Shahram said that since the UDP mode over IPv6 is supported by the 
> available chipsets,
> apparently they already do the correction.
> 
> Ron asked how the OAM packets that are carried in the same tunnel 
> are identified.
> Yaakov asked if it is always in a VCCV channel.
> Shahram said that for the Ethernet PW approach it was VCCV (either 
> BFD or LSP ping)
> while for the UDP/IP it was via UDP port number.
> Ron asked for clear text to be added, so that later on new packet 
> types could be added.
> 
> Karen said that we want to advance this draft to WG draft before the
> next meeting.
> We don't need to finalize all the open items first.
> Shahram and Manav reiterated that this draft has been a long time 
inmaturing,
> and that its handling should be expedited.
> 
> At this point there were only 5 minutes left, and there was no time 
> to start a new topic.
> 
> Karen announced that the next conference call would be the third 
> Tuesday in Feb (Feb 15th).
> Stefano said that this would fall during the ITU-T meeting.
> Yaakov said that this could still work if interested Q13 
> participants joined after the sessions.
> Stefano said that this would require the call being 1 hour later 
> (18:00 Geneva time),
> and only if there were no late joint meetings planned.
> 
> Action items :
> 1) Yaakov will send a mail to the list with an explanation of what 
> was needed for NTP
> 2) Shahram and Manav will respin the draft as a WG draft as soon as 
> permission is given.
> 3) Needed changes:
>    a) fix wording on mandatory nature of 1588 support
>    b) add IS-IS text, or at least a place-holder for such text
>    c) add LDP-4447 text, or at least a place holder for such text
>    d) fix up the IANA considerations section
>    e) add text regarding per-port support, or an editor's note that 
> this needs to be covered
>    f) add text on UDP checksum correction
>    g) add text explaining how OAM packets are separated from PTP 
> ones (ASCII art? pseudocode?)
>    h) fixes mentioned on list (border clock, transparent clocking, ...)
> 4) Stefano will check whether Feb 15th at 18:00 Geneva time is suitable.
> 5) Karen will set up another meeting accordingly.
> 
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL: <http://www.ietf.org/mail-
> archive/web/tictoc/attachments/20110118/9893cfab/attachment.htm>
> 
> ------------------------------
> 
> _______________________________________________
> TICTOC mailing list
> TICTOC@ietf.org
> https://www.ietf.org/mailman/listinfo/tictoc
> 
> 
> End of TICTOC Digest, Vol 50, Issue 28
> **************************************
> 


--------------------------------------------------------
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 000812154825781D_=
Content-Type: text/html; charset="US-ASCII"


<br><font size=2 face="sans-serif">Hi Yaakov and all,</font>
<br><font size=2 face="sans-serif">Because of a trip, I can not attend
this conference call. I tend to agree that there was still a lot of deep
correction, and the encapsulation can be a pure MPLS mode (without UDP/IP
or Ethernet). Such kind of encapsulation would be more effective.</font>
<br>
<br><font size=2 face="sans-serif">What's more, as I posted on this list,
the fat label in PWE3 encapsulation should be not be used in this draft.</font>
<br>
<br><font size=2 face="sans-serif">Regards</font>
<br><font size=2 face="sans-serif">Lizhong</font>
<br><font size=2 face="sans-serif"><br>
</font><tt><font size=2><br>
&gt; ----------------------------------------------------------------------<br>
&gt; <br>
&gt; Message: 1<br>
&gt; Date: Tue, 18 Jan 2011 17:44:34 +0000<br>
&gt; From: Yaakov Stein &lt;yaakov_s@rad.com&gt;<br>
&gt; Subject: [TICTOC] minutes of TICTOC conference call - Jan 18, 2011<br>
&gt; To: &quot;tictoc@ietf.org&quot; &lt;tictoc@ietf.org&gt;<br>
&gt; Message-ID:<br>
&gt; &nbsp; &nbsp;&lt;07F7D7DED63154409F13298786A2ADC903CD4B30@EXRAD5.ad.rad.co.il&gt;<br>
&gt; Content-Type: text/plain; charset=&quot;us-ascii&quot;<br>
&gt; <br>
&gt; TICTOC conference call<br>
&gt; 18 January, 2011<br>
&gt; Participating :<br>
&gt; Karen (hosted WebEx), Yaakov (minutes scribe), Shahram, Stefano, <br>
&gt; Manav, Greg, Ron Cohen, Tal Mizrahi, Peter Roberts<br>
&gt; <br>
&gt; Karen opened the call, stating that the main item for discussion was<br>
&gt; the new version of the 1588overmpls draft,<br>
&gt; with management and security issues after that if time allowed.<br>
&gt; <br>
&gt; Yaakov mentioned the main problems he identified with the draft :<br>
&gt; 1) a wording issue regarding whether the LSR support was mandatory
<br>
&gt; (Shahram said it wasn't)<br>
&gt; 2) whether NTP would be covered in the same draft<br>
&gt; 3) why only OSPF and RSVP were covered, and not IS-IS and LDP.<br>
&gt; <br>
&gt; Shahram said that NTP and IS-IS were not covered due to lack of expertise.<br>
&gt; Manav said that IS-IS could certainly be added.<br>
&gt; Shahram said that LDP of the PWE3 control protocol needed to be <br>
&gt; added due to the possibility of PHP'ing the tunnel label.<br>
&gt; <br>
&gt; Yaakov asked whether the wording on page 10 &quot;the top label&quot;
was intentional,<br>
&gt; and Shahram explained that it was! There needed to be only a single
<br>
&gt; PW per tunnel,<br>
&gt; and if there were multiple labels in the stack, the top one needed
<br>
&gt; to be signaled.<br>
&gt; This saves DPI (but Yaakov stated that there was still a lot of deep<br>
&gt; correction).<br>
&gt; <br>
&gt; Ron asked whether the draft could be extended to handle LSRs that
<br>
&gt; did not support TC correction on ALL ports,<br>
&gt; but only on those needed for the timing flow. This would require <br>
&gt; additional port capabilities description.<br>
&gt; Manav said that this could be done in OSPF-TE.<br>
&gt; Ron stressed the importance of this feature.<br>
&gt; <br>
&gt; Stefano asked why this draft was limited to PTP and not (for example)
NTP.<br>
&gt; Ron said that the entire idea was to support the TC correction field,<br>
&gt; and that prioritization could be accomplished without a new draft.<br>
&gt; Yaakov said that prioritization (e.g., EF) could indeed be covered
<br>
&gt; in a BCP rather than a PS RFC,<br>
&gt; but if BC was required for PTP or NTP, then the techniques defined
<br>
&gt; here were still needed.<br>
&gt; Manav suggested that NTP was so different that it should be handled
<br>
&gt; in a separate draft.<br>
&gt; Karen said that it was preferable to have a single draft to ensure
<br>
&gt; consistency.<br>
&gt; Shahram proposed that Yaakov write a problem statement for NTP, and
<br>
&gt; afterwards it could be decided<br>
&gt; if this could be added to this draft, or if a separate document was
needed.<br>
&gt; <br>
&gt; Ron stated that the encapsulation was general enough to support a
<br>
&gt; pure MPLS mode (without UDP/IP or Ethernet).<br>
&gt; Shahram said that he preferred to avoid this, as it would require
<br>
&gt; further IEEE and IETF work.<br>
&gt; Ron said that the IEEE already granted authority to the IETF to <br>
&gt; devise such an encapsulation.<br>
&gt; Yaakov said that only a simple PWE3 draft would be needed to define
<br>
&gt; a new PW type.<br>
&gt; It was decided that this needed to be discussed further.<br>
&gt; <br>
&gt; Ron and Yaakov raised the point of UDP checksum correction<br>
&gt; (FCS correction for retention mode is mentioned in the draft, but
<br>
&gt; not UDP checksum).<br>
&gt; Shahram asked if checksum is mandatory.<br>
&gt; Yaakov replied that it is optional in IPv4, but mandatory in IPv6.<br>
&gt; Shahram asked whether the checksum could be corrected rather than
<br>
&gt; recalculated.<br>
&gt; Yaakov said yes.<br>
&gt; Shahram said that since the UDP mode over IPv6 is supported by the
<br>
&gt; available chipsets,<br>
&gt; apparently they already do the correction.<br>
&gt; <br>
&gt; Ron asked how the OAM packets that are carried in the same tunnel
<br>
&gt; are identified.<br>
&gt; Yaakov asked if it is always in a VCCV channel.<br>
&gt; Shahram said that for the Ethernet PW approach it was VCCV (either
<br>
&gt; BFD or LSP ping)<br>
&gt; while for the UDP/IP it was via UDP port number.<br>
&gt; Ron asked for clear text to be added, so that later on new packet
<br>
&gt; types could be added.<br>
&gt; <br>
&gt; Karen said that we want to advance this draft to WG draft before the<br>
&gt; next meeting.<br>
&gt; We don't need to finalize all the open items first.<br>
&gt; Shahram and Manav reiterated that this draft has been a long time
inmaturing,<br>
&gt; and that its handling should be expedited.<br>
&gt; <br>
&gt; At this point there were only 5 minutes left, and there was no time
<br>
&gt; to start a new topic.<br>
&gt; <br>
&gt; Karen announced that the next conference call would be the third <br>
&gt; Tuesday in Feb (Feb 15th).<br>
&gt; Stefano said that this would fall during the ITU-T meeting.<br>
&gt; Yaakov said that this could still work if interested Q13 <br>
&gt; participants joined after the sessions.<br>
&gt; Stefano said that this would require the call being 1 hour later <br>
&gt; (18:00 Geneva time),<br>
&gt; and only if there were no late joint meetings planned.<br>
&gt; <br>
&gt; Action items :<br>
&gt; 1) Yaakov will send a mail to the list with an explanation of what
<br>
&gt; was needed for NTP<br>
&gt; 2) Shahram and Manav will respin the draft as a WG draft as soon as
<br>
&gt; permission is given.<br>
&gt; 3) Needed changes:<br>
&gt; &nbsp; &nbsp;a) fix wording on mandatory nature of 1588 support<br>
&gt; &nbsp; &nbsp;b) add IS-IS text, or at least a place-holder for such
text<br>
&gt; &nbsp; &nbsp;c) add LDP-4447 text, or at least a place holder for
such text<br>
&gt; &nbsp; &nbsp;d) fix up the IANA considerations section<br>
&gt; &nbsp; &nbsp;e) add text regarding per-port support, or an editor's
note that <br>
&gt; this needs to be covered<br>
&gt; &nbsp; &nbsp;f) add text on UDP checksum correction<br>
&gt; &nbsp; &nbsp;g) add text explaining how OAM packets are separated
from PTP <br>
&gt; ones (ASCII art? pseudocode?)<br>
&gt; &nbsp; &nbsp;h) fixes mentioned on list (border clock, transparent
clocking, ...)<br>
&gt; 4) Stefano will check whether Feb 15th at 18:00 Geneva time is suitable.<br>
&gt; 5) Karen will set up another meeting accordingly.<br>
&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/tictoc/attachments/20110118/9893cfab/attachment.htm&gt;<br>
&gt; <br>
&gt; ------------------------------<br>
&gt; <br>
&gt; _______________________________________________<br>
&gt; TICTOC mailing list<br>
&gt; TICTOC@ietf.org<br>
&gt; https://www.ietf.org/mailman/listinfo/tictoc<br>
&gt; <br>
&gt; <br>
&gt; End of TICTOC Digest, Vol 50, Issue 28<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 000812154825781D_=--


From yaakov_s@rad.com  Wed Jan 19 09:34:51 2011
Return-Path: <yaakov_s@rad.com>
X-Original-To: tictoc@core3.amsl.com
Delivered-To: tictoc@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 5C10E28C0D8 for <tictoc@core3.amsl.com>; Wed, 19 Jan 2011 09:34:51 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.19
X-Spam-Level: 
X-Spam-Status: No, score=-102.19 tagged_above=-999 required=5 tests=[AWL=-0.191, BAYES_00=-2.599, J_CHICKENPOX_33=0.6, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 25TQrxBB9mBl for <tictoc@core3.amsl.com>; Wed, 19 Jan 2011 09:34:50 -0800 (PST)
Received: from antivir1.rad.co.il (mx1-q.rad.co.il [80.74.100.136]) by core3.amsl.com (Postfix) with ESMTP id 351C53A7046 for <tictoc@ietf.org>; Wed, 19 Jan 2011 09:34:48 -0800 (PST)
Received: from exrad5.ad.rad.co.il ([192.114.24.28]) by antivir1.rad.co.il with ESMTP; 19 Jan 2011 19:37:27 +0200
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; Wed, 19 Jan 2011 19:37:15 +0200
Received: from EXRAD5.ad.rad.co.il ([fe80::ec3e:feb5:8bef:e3ba]) by exus4-drp.ad.rad.co.il ([fe80::5d6f:c2cb:2468:ee2%16]) with mapi id 14.01.0270.001; Wed, 19 Jan 2011 19:37:15 +0200
From: Yaakov Stein <yaakov_s@rad.com>
To: "Hing-Kam (Kam) Lam" <hingkam16@gmail.com>
Thread-Topic: [TICTOC] minutes of TICTOC conference call - Jan 18, 2011
Thread-Index: Acu3N10fvrNNbaKTRqCEJBiGn8t8bAAI4KsAACjlrEA=
Date: Wed, 19 Jan 2011 17:37:13 +0000
Message-ID: <07F7D7DED63154409F13298786A2ADC903CD573E@EXRAD5.ad.rad.co.il>
References: <07F7D7DED63154409F13298786A2ADC903CD4B30@EXRAD5.ad.rad.co.il> <AANLkTim8JSyrhaLbQRfg58iwh12-y6JFEHebziYutMtx@mail.gmail.com>
In-Reply-To: <AANLkTim8JSyrhaLbQRfg58iwh12-y6JFEHebziYutMtx@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [172.17.170.37]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "tictoc@ietf.org" <tictoc@ietf.org>
Subject: Re: [TICTOC] minutes of TICTOC conference call - Jan 18, 2011
X-BeenThere: tictoc@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Timing over IP Connection and Transfer of Clock BOF <tictoc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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, 19 Jan 2011 17:34:51 -0000

Kam,=20

I snipped out your questions and answer them below.

Y(J)S



>> Shahram said that LDP of the PWE3 control protocol needed to be added du=
e to
>> the possibility of PHP'ing the tunnel label.

> I did not understand this point.

If the tunnel label is PHP'ed, then the packet arrives with only a PW label=
.
We now have to know if this label indicates a timing flow.

>> Ron asked whether the draft could be extended to handle LSRs that did no=
t
>> support TC correction on ALL ports,
>>
>> but only on those needed for the timing flow. This would require additio=
nal
>> port capabilities description.

> I would like to understand the utility of such a description. Either
> the box is capable of doing TC correction, or it cant. I dont believe
> this capability is required per port. Would appreciate if someone can
> explain us why?

Why do you think that a box must be capable of handling timing packets
on every port ?  Frequently ports are on modules that can be inserted,
and if only a small fraction of the network needs timing support,
there is little reason to upgrade all the modules.

However, I'll let Ron argue this point.

>> Ron stressed the importance of this feature.

> Would love to know why.

Explained above. As far as I see, it is simpley a matter of economics.

>> Yaakov said that prioritization (e.g., EF) could indeed be covered in a =
BCP
>> rather than a PS RFC,

> Is this by using the EXP bits?

Yes, for E-LSPs. But it could be by label.

>> but if BC was required for PTP or NTP, then the techniques defined here =
were
>> still needed.

> You would also require this draft if you did TC.

That is what "still" means.  You ALWAYS need this draft (or something else)
for TC, but you would still need it for BC, and may need it for prioritizat=
ion.

>> Shahram said that he preferred to avoid this, as it would require furthe=
r
>> IEEE and IETF work.

> Isnt the draft already supporting all encapsulations? In Fig 2 UDP, IP
> are all optional. I assumed that it meant that we support all
> encapsulations. Also the fact that RSVP was signalling the start of
> the PTP packet (which is neat!) indicated that we support everything.
> I seem to be missing something here.

Look carefully. There is a figure for UDP/IP , and one for a PW
with either pure Ethernet or UDP/IP over Ethernet.
There is no pure MPLS (without either Ethernet or IP).

>> Ron and Yaakov raised the point of UDP checksum correction

> This is only for TC right?

Right.


From ronc.ntear@gmail.com  Wed Jan 19 12:32:37 2011
Return-Path: <ronc.ntear@gmail.com>
X-Original-To: tictoc@core3.amsl.com
Delivered-To: tictoc@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id AC1DC28C0EB for <tictoc@core3.amsl.com>; Wed, 19 Jan 2011 12:32:37 -0800 (PST)
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.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id seLIO6OcftYs for <tictoc@core3.amsl.com>; Wed, 19 Jan 2011 12:32:36 -0800 (PST)
Received: from mail-yw0-f44.google.com (mail-yw0-f44.google.com [209.85.213.44]) by core3.amsl.com (Postfix) with ESMTP id 67C9528C0E7 for <tictoc@ietf.org>; Wed, 19 Jan 2011 12:32:36 -0800 (PST)
Received: by ywk9 with SMTP id 9so565090ywk.31 for <tictoc@ietf.org>; Wed, 19 Jan 2011 12:35:17 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:date:message-id:subject:from:to :content-type; bh=JPCj857CTD3L7tQnyWpQq6yVIrWoxNgZDxH7VaBl3Xg=; b=X6Z2w0Al3LNKWwXVF243uqTTRpABzerpv9tZ6fkRfKiVhjunawiO3cOzBH/R9Ep5vp 3v4hyJZuVedlDIOW7OmuJe620Zc3L0SdhBKM0DIpuRoqbpk0+q9BWnFVbxXi6Yaj9n/N 4/vB28iwV1LSq9196/A8Ikw7e5qMIVAvoypiY=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; b=hB33tyWanQkTfLbpAHfV0GFqPpIIEa1jMesmfRrZRgbnQjjzk6A5ip7N8uqdI0kv6a 3Zw986BaKFh1aG2CEzx9r8kc4WqkJMP7zJR3vzDjMCSS7T8X8Hmk6BvHMEgc/i/uPj5P MsO3+8A/T7mNV8OvH1YG49wbmViq0tqvgJ5GA=
MIME-Version: 1.0
Received: by 10.216.65.16 with SMTP id e16mr1105618wed.73.1295469316289; Wed, 19 Jan 2011 12:35:16 -0800 (PST)
Received: by 10.216.167.69 with HTTP; Wed, 19 Jan 2011 12:35:16 -0800 (PST)
Date: Wed, 19 Jan 2011 22:35:16 +0200
Message-ID: <AANLkTik-_UZq7Sjav0X-wpnrovvo_rK5D_Za-HA9OX93@mail.gmail.com>
From: Ron Cohen <ronc.ntear@gmail.com>
To: tictoc@ietf.org
Content-Type: multipart/alternative; boundary=000e0ce0424a6a35ca049a38f479
Subject: [TICTOC] Port vs. LSR 1588-awareness
X-BeenThere: tictoc@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Timing over IP Connection and Transfer of Clock BOF <tictoc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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, 19 Jan 2011 20:32:37 -0000

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

Hi,

The 01 version of 1588overMPLS draft defines a 1588-aware node capability
advertised by OSPF. The issue raised in the conference is the need to
support LSRs that do not support PTP on all ports. For example, assume the
LSR is build out of a chassis with 2 switching cards and 8 networking cards.
If all cards are upgraded to support PTP timestamping, the LSR can advertise
itself as a 1588-aware node. However, there isn't any real need to upgrade
all cards in order to support PTP LSPs. For example, upgrading the 2
switching cards and 2 of the network cards should still suffice to support
TC functionality for any LSP whose ingress port and egress port reside on
the upgraded cards. However, if we can only advertise 1588-awareness
capability on the node level, we would either not be able to support such
LSRs, or advertise false information (i.e. advertise 1588-awareness also on
non-1588-aware ports).

A similar approach is taken in Synchronous Ethernet (SyncE). Not all
Ethernet ports on a node need to support SyncE in order for the node to be
part of the SyncE synchronization chain.

In the example described previously, The LSR TC implementation supports LSP
whose ingress port is on the 1588-aware network card A and whose egress port
is on the 1588-aware card-B because either both cards have access to the
same time reference and can pass the ingress timestamp across the fabric, or
if TC functionality is implemented on the switching cards as well, or in
another ingenious way. However, I do not think that we should mandate that
TC LSR implementation must be able to support cross-card (i.e. any port to
any port) TC functionality, rather we should be able to use TC
implementations that support also only intra-card TC implementations.

It shouldn't be too difficult to accommodate for the above. Instead of
per-node 1588-awareness capability, the capability should be a per-port. In
addition we can introduce a concept of a TC-port-group. A TC that can
implement TC functionality between every 1588-aware port will associate all
ports with one TC-port-group. A TC that can support TC functionality only
between subsets of ports will associate each such subset of ports to a
different TC group. Each 1588-aware port will therefore advertise its
awareness capability and the TC-port-group it belongs to. The PTP LSP will
be setup (e.g. by RSVP-TE) through ports in LSR that are 1588-aware, and
where the ingress and egress ports within each LSR belong to the same
TC-port-group.

Comments are welcome.

Best,
Ron








The proposal is to advertise 1588-awareness capability on a port level.
There are two




There are several options here in terms of how to do that

That is, advertise 1588-awareness only thro

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

<div dir=3D"ltr">Hi,<br><br>The 01 version of 1588overMPLS draft defines a =
1588-aware node capability advertised by OSPF. The issue raised in the conf=
erence is the need to support LSRs that do not support PTP on all ports. Fo=
r example, assume the LSR is build out of a chassis with 2 switching cards =
and 8 networking cards. If all cards are upgraded to support PTP timestampi=
ng, the LSR can advertise itself as a 1588-aware node. However, there isn&#=
39;t any real need to upgrade all cards in order to support PTP LSPs. For e=
xample, upgrading the 2 switching cards and 2 of the network cards should s=
till suffice to support TC functionality for any LSP whose ingress port and=
 egress port reside on the upgraded cards. However, if we can only advertis=
e 1588-awareness capability on the node level, we would either not be able =
to support such LSRs, or advertise false information (i.e. advertise 1588-a=
wareness also on non-1588-aware ports).<br>
<br>A similar approach is taken in Synchronous Ethernet (SyncE). Not all Et=
hernet ports on a node need to support SyncE in order for the node to be pa=
rt of the SyncE synchronization chain. <br><br>In the example described pre=
viously, The LSR TC implementation supports LSP whose ingress port is on th=
e 1588-aware network card A and whose egress port is on the 1588-aware card=
-B because either both cards have access to the same time reference and can=
 pass the ingress timestamp across the fabric, or if TC functionality is im=
plemented on the switching cards as well, or in another ingenious way. Howe=
ver, I do not think that we should mandate that TC LSR implementation must =
be able to support cross-card (i.e. any port to any port) TC functionality,=
 rather we should be able to use TC implementations that support also only =
intra-card TC implementations.<br>
<br>It shouldn&#39;t be too difficult to accommodate for the above. Instead=
 of per-node 1588-awareness capability, the capability should be a per-port=
. In addition we can introduce a concept of a TC-port-group. A TC that can =
implement TC functionality between every 1588-aware port will associate all=
 ports with one TC-port-group. A TC that can support TC functionality only =
between subsets of ports will associate each such subset of ports to a diff=
erent TC group. Each 1588-aware port will therefore advertise its awareness=
 capability and the TC-port-group it belongs to. The PTP LSP will be setup =
(e.g. by RSVP-TE) through ports in LSR that are 1588-aware, and where the i=
ngress and egress ports within each LSR belong to the same TC-port-group.<b=
r>
<br>Comments are welcome. <br><br>Best,<br>Ron<br><br>=A0<br><br><br><br><b=
r><br><br>The proposal is to advertise 1588-awareness capability on a port =
level. There are two<br><br><br><br><br>There are several options here in t=
erms of how to do that<br>
<br>That is, advertise 1588-awareness only thro<br><br><br><br><br><div sty=
le=3D"visibility: hidden; left: -5000px; position: absolute; z-index: 9999;=
 padding: 0px; margin-left: 0px; margin-top: 0px; overflow: hidden; word-wr=
ap: break-word; color: black; font-size: 10px; text-align: left; line-heigh=
t: 130%;" id=3D"avg_ls_inline_popup">
</div></div>

--000e0ce0424a6a35ca049a38f479--

From manav.bhatia@alcatel-lucent.com  Thu Jan 20 15:12:54 2011
Return-Path: <manav.bhatia@alcatel-lucent.com>
X-Original-To: tictoc@core3.amsl.com
Delivered-To: tictoc@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id B847C3A6880 for <tictoc@core3.amsl.com>; Thu, 20 Jan 2011 15:12:54 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.213
X-Spam-Level: 
X-Spam-Status: No, score=-6.213 tagged_above=-999 required=5 tests=[AWL=0.386,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id QxffsKFdFYOh for <tictoc@core3.amsl.com>; Thu, 20 Jan 2011 15:12:54 -0800 (PST)
Received: from ihemail1.lucent.com (ihemail1.lucent.com [135.245.0.33]) by core3.amsl.com (Postfix) with ESMTP id F049A3A6881 for <tictoc@ietf.org>; Thu, 20 Jan 2011 15:12:53 -0800 (PST)
Received: from inbansmailrelay2.in.alcatel-lucent.com (h135-250-11-33.lucent.com [135.250.11.33]) by ihemail1.lucent.com (8.13.8/IER-o) with ESMTP id p0KNFYqd024941 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL) for <tictoc@ietf.org>; Thu, 20 Jan 2011 17:15:37 -0600 (CST)
Received: from INBANSXCHHUB01.in.alcatel-lucent.com (inbansxchhub01.in.alcatel-lucent.com [135.250.12.32]) by inbansmailrelay2.in.alcatel-lucent.com (8.14.3/8.14.3/GMO) with ESMTP id p0KNFXba008717 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT) for <tictoc@ietf.org>; Fri, 21 Jan 2011 04:45:34 +0530
Received: from INBANSXCHMBSA1.in.alcatel-lucent.com ([135.250.12.56]) by INBANSXCHHUB01.in.alcatel-lucent.com ([135.250.12.32]) with mapi; Fri, 21 Jan 2011 04:45:33 +0530
From: "Bhatia, Manav (Manav)" <manav.bhatia@alcatel-lucent.com>
To: "tictoc@ietf.org" <tictoc@ietf.org>
Date: Fri, 21 Jan 2011 04:45:33 +0530
Thread-Topic: UDP checksum
Thread-Index: Acu49+/VHCD95rNISYmauhcQo/vaHw==
Message-ID: <7C362EEF9C7896468B36C9B79200D8350CFB0DFDA7@INBANSXCHMBSA1.in.alcatel-lucent.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Scanned-By: MIMEDefang 2.57 on 135.245.2.33
X-Scanned-By: MIMEDefang 2.64 on 135.250.11.33
Subject: [TICTOC] UDP checksum
X-BeenThere: tictoc@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Timing over IP Connection and Transfer of Clock BOF <tictoc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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, 20 Jan 2011 23:12:54 -0000

Hi,

Are the LSRs acting as TCs expected to verify the checksum before they upda=
te the correction field? If no, then there is no point in these LSRs in upd=
ating the UDP checksum as they will "correct" the checksum when its recompu=
ted after modifying the CF field. In this case wouldn't it make more sense =
to just update the checksum at the MPLS terminating point?

I also think that updating the UDP checksum may be redundant as the LSRs ar=
e anyways verifying the outer ethernet checksum before accepting any packet=
s. Any thoughts here?

Cheers, Manav

--
Manav Bhatia,
IP Division, Alcatel-Lucent,
Bangalore - India

 =

From davari@broadcom.com  Thu Jan 20 15:26:40 2011
Return-Path: <davari@broadcom.com>
X-Original-To: tictoc@core3.amsl.com
Delivered-To: tictoc@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 083E83A6877 for <tictoc@core3.amsl.com>; Thu, 20 Jan 2011 15:26:40 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.991
X-Spam-Level: 
X-Spam-Status: No, score=-0.991 tagged_above=-999 required=5 tests=[AWL=1.608,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 9uzbm-7iUcY4 for <tictoc@core3.amsl.com>; Thu, 20 Jan 2011 15:26:39 -0800 (PST)
Received: from MMS3.broadcom.com (mms3.broadcom.com [216.31.210.19]) by core3.amsl.com (Postfix) with ESMTP id 5DE9E3A6872 for <tictoc@ietf.org>; Thu, 20 Jan 2011 15:26:38 -0800 (PST)
Received: from [10.16.192.232] by MMS3.broadcom.com with ESMTP (Broadcom SMTP Relay (Email Firewall v6.3.2)); Thu, 20 Jan 2011 15:30:30 -0800
X-Server-Uuid: B55A25B1-5D7D-41F8-BC53-C57E7AD3C201
Received: from SJEXCHCCR02.corp.ad.broadcom.com ([10.16.192.130]) by SJEXCHHUB02.corp.ad.broadcom.com ([10.16.192.232]) with mapi; Thu, 20 Jan 2011 15:29:07 -0800
From: "Shahram Davari" <davari@broadcom.com>
To: "Bhatia, Manav (Manav)" <manav.bhatia@alcatel-lucent.com>, "tictoc@ietf.org" <tictoc@ietf.org>
Date: Thu, 20 Jan 2011 15:29:06 -0800
Thread-Topic: UDP checksum
Thread-Index: Acu49+/VHCD95rNISYmauhcQo/vaHwAADWEw
Message-ID: <2C2F1EBA8050E74EA81502D5740B4BD6941B04CC39@SJEXCHCCR02.corp.ad.broadcom.com>
References: <7C362EEF9C7896468B36C9B79200D8350CFB0DFDA7@INBANSXCHMBSA1.in.alcatel-lucent.com>
In-Reply-To: <7C362EEF9C7896468B36C9B79200D8350CFB0DFDA7@INBANSXCHMBSA1.in.alcatel-lucent.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
MIME-Version: 1.0
X-WSS-ID: 61261A1C1VG9423110-01-01
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Subject: Re: [TICTOC] UDP checksum
X-BeenThere: tictoc@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Timing over IP Connection and Transfer of Clock BOF <tictoc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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, 20 Jan 2011 23:26:40 -0000

Hi Manav,

UDP checksum is usually not verified before updating the CF. After CF updat=
e it is incrementally recalculated. The end host will then verify the check=
sum for correctness.

Regards,
Shahram

-----Original Message-----
From: tictoc-bounces@ietf.org [mailto:tictoc-bounces@ietf.org] On Behalf Of=
 Bhatia, Manav (Manav)
Sent: Thursday, January 20, 2011 3:16 PM
To: tictoc@ietf.org
Subject: [TICTOC] UDP checksum

Hi,

Are the LSRs acting as TCs expected to verify the checksum before they upda=
te the correction field? If no, then there is no point in these LSRs in upd=
ating the UDP checksum as they will "correct" the checksum when its recompu=
ted after modifying the CF field. In this case wouldn't it make more sense =
to just update the checksum at the MPLS terminating point?

I also think that updating the UDP checksum may be redundant as the LSRs ar=
e anyways verifying the outer ethernet checksum before accepting any packet=
s. Any thoughts here?

Cheers, Manav

--
Manav Bhatia,
IP Division, Alcatel-Lucent,
Bangalore - India

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



From manav.bhatia@alcatel-lucent.com  Thu Jan 20 15:30:41 2011
Return-Path: <manav.bhatia@alcatel-lucent.com>
X-Original-To: tictoc@core3.amsl.com
Delivered-To: tictoc@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 0B1BF3A687F for <tictoc@core3.amsl.com>; Thu, 20 Jan 2011 15:30:41 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.221
X-Spam-Level: 
X-Spam-Status: No, score=-6.221 tagged_above=-999 required=5 tests=[AWL=0.378,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id AdQjjnGfIaUL for <tictoc@core3.amsl.com>; Thu, 20 Jan 2011 15:30:40 -0800 (PST)
Received: from ihemail4.lucent.com (ihemail4.lucent.com [135.245.0.39]) by core3.amsl.com (Postfix) with ESMTP id DE9E53A687D for <tictoc@ietf.org>; Thu, 20 Jan 2011 15:30:39 -0800 (PST)
Received: from inbansmailrelay1.in.alcatel-lucent.com (h135-250-11-31.lucent.com [135.250.11.31]) by ihemail4.lucent.com (8.13.8/IER-o) with ESMTP id p0KNXDVa010480 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Thu, 20 Jan 2011 17:33:16 -0600 (CST)
Received: from INBANSXCHHUB02.in.alcatel-lucent.com (inbansxchhub02.in.alcatel-lucent.com [135.250.12.35]) by inbansmailrelay1.in.alcatel-lucent.com (8.14.3/8.14.3/GMO) with ESMTP id p0KNXCNO019517 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Fri, 21 Jan 2011 05:03:13 +0530
Received: from INBANSXCHMBSA1.in.alcatel-lucent.com ([135.250.12.56]) by INBANSXCHHUB02.in.alcatel-lucent.com ([135.250.12.35]) with mapi; Fri, 21 Jan 2011 05:03:12 +0530
From: "Bhatia, Manav (Manav)" <manav.bhatia@alcatel-lucent.com>
To: Shahram Davari <davari@broadcom.com>, "tictoc@ietf.org" <tictoc@ietf.org>
Date: Fri, 21 Jan 2011 05:03:12 +0530
Thread-Topic: UDP checksum
Thread-Index: Acu49+/VHCD95rNISYmauhcQo/vaHwAADWEwAAB6V/A=
Message-ID: <7C362EEF9C7896468B36C9B79200D8350CFB0DFDAA@INBANSXCHMBSA1.in.alcatel-lucent.com>
References: <7C362EEF9C7896468B36C9B79200D8350CFB0DFDA7@INBANSXCHMBSA1.in.alcatel-lucent.com> <2C2F1EBA8050E74EA81502D5740B4BD6941B04CC39@SJEXCHCCR02.corp.ad.broadcom.com>
In-Reply-To: <2C2F1EBA8050E74EA81502D5740B4BD6941B04CC39@SJEXCHCCR02.corp.ad.broadcom.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Scanned-By: MIMEDefang 2.57 on 135.245.2.39
X-Scanned-By: MIMEDefang 2.64 on 135.250.11.31
Subject: Re: [TICTOC] UDP checksum
X-BeenThere: tictoc@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Timing over IP Connection and Transfer of Clock BOF <tictoc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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, 20 Jan 2011 23:30:41 -0000

Hi Shahram,

It may be ok as long as the HWs are incrementally recalculating it. However=
, if its being done afresh then we have an issue. I don't see how the HW be=
havior can be mandated in a spec.=20

Cheers, Manav

> -----Original Message-----
> From: Shahram Davari [mailto:davari@broadcom.com]=20
> Sent: Friday, January 21, 2011 4.59 AM
> To: Bhatia, Manav (Manav); tictoc@ietf.org
> Subject: RE: UDP checksum
>=20
> Hi Manav,
>=20
> UDP checksum is usually not verified before updating the CF.=20
> After CF update it is incrementally recalculated. The end=20
> host will then verify the checksum for correctness.
>=20
> Regards,
> Shahram
>=20
> -----Original Message-----
> From: tictoc-bounces@ietf.org=20
> [mailto:tictoc-bounces@ietf.org] On Behalf Of Bhatia, Manav (Manav)
> Sent: Thursday, January 20, 2011 3:16 PM
> To: tictoc@ietf.org
> Subject: [TICTOC] UDP checksum
>=20
> Hi,
>=20
> Are the LSRs acting as TCs expected to verify the checksum=20
> before they update the correction field? If no, then there is=20
> no point in these LSRs in updating the UDP checksum as they=20
> will "correct" the checksum when its recomputed after=20
> modifying the CF field. In this case wouldn't it make more=20
> sense to just update the checksum at the MPLS terminating point?
>=20
> I also think that updating the UDP checksum may be redundant=20
> as the LSRs are anyways verifying the outer ethernet checksum=20
> before accepting any packets. Any thoughts here?
>=20
> Cheers, Manav
>=20
> --
> Manav Bhatia,
> IP Division, Alcatel-Lucent,
> Bangalore - India
>=20
> =20
> _______________________________________________
> TICTOC mailing list
> TICTOC@ietf.org
> https://www.ietf.org/mailman/listinfo/tictoc
>=20
>=20
> =

From davari@broadcom.com  Thu Jan 20 15:49:44 2011
Return-Path: <davari@broadcom.com>
X-Original-To: tictoc@core3.amsl.com
Delivered-To: tictoc@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 492E13A687D for <tictoc@core3.amsl.com>; Thu, 20 Jan 2011 15:49:44 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.393
X-Spam-Level: 
X-Spam-Status: No, score=-1.393 tagged_above=-999 required=5 tests=[AWL=1.206,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id SfFJ+QfPnRxZ for <tictoc@core3.amsl.com>; Thu, 20 Jan 2011 15:49:43 -0800 (PST)
Received: from MMS3.broadcom.com (mms3.broadcom.com [216.31.210.19]) by core3.amsl.com (Postfix) with ESMTP id 79F3B3A6877 for <tictoc@ietf.org>; Thu, 20 Jan 2011 15:49:43 -0800 (PST)
Received: from [10.16.192.224] by MMS3.broadcom.com with ESMTP (Broadcom SMTP Relay (Email Firewall v6.3.2)); Thu, 20 Jan 2011 15:53:38 -0800
X-Server-Uuid: B55A25B1-5D7D-41F8-BC53-C57E7AD3C201
Received: from SJEXCHCCR02.corp.ad.broadcom.com ([10.16.192.130]) by SJEXCHHUB01.corp.ad.broadcom.com ([10.16.192.224]) with mapi; Thu, 20 Jan 2011 15:52:15 -0800
From: "Shahram Davari" <davari@broadcom.com>
To: "Bhatia, Manav (Manav)" <manav.bhatia@alcatel-lucent.com>, "tictoc@ietf.org" <tictoc@ietf.org>
Date: Thu, 20 Jan 2011 15:52:14 -0800
Thread-Topic: UDP checksum
Thread-Index: Acu49+/VHCD95rNISYmauhcQo/vaHwAADWEwAAB6V/AAAEvoYA==
Message-ID: <2C2F1EBA8050E74EA81502D5740B4BD6941B04CC6D@SJEXCHCCR02.corp.ad.broadcom.com>
References: <7C362EEF9C7896468B36C9B79200D8350CFB0DFDA7@INBANSXCHMBSA1.in.alcatel-lucent.com> <2C2F1EBA8050E74EA81502D5740B4BD6941B04CC39@SJEXCHCCR02.corp.ad.broadcom.com> <7C362EEF9C7896468B36C9B79200D8350CFB0DFDAA@INBANSXCHMBSA1.in.alcatel-lucent.com>
In-Reply-To: <7C362EEF9C7896468B36C9B79200D8350CFB0DFDAA@INBANSXCHMBSA1.in.alcatel-lucent.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
MIME-Version: 1.0
X-WSS-ID: 612614881VG9431861-01-01
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Subject: Re: [TICTOC] UDP checksum
X-BeenThere: tictoc@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Timing over IP Connection and Transfer of Clock BOF <tictoc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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, 20 Jan 2011 23:49:44 -0000

Hi Manav,

The minimum requirement is to do UDP checksum incremental update on transmi=
ssion. If full update is done then UDP checksum must be verified on recepti=
on as well.

Thx
Shahram

-----Original Message-----
From: Bhatia, Manav (Manav) [mailto:manav.bhatia@alcatel-lucent.com]=20
Sent: Thursday, January 20, 2011 3:33 PM
To: Shahram Davari; tictoc@ietf.org
Subject: RE: UDP checksum

Hi Shahram,

It may be ok as long as the HWs are incrementally recalculating it. However=
, if its being done afresh then we have an issue. I don't see how the HW be=
havior can be mandated in a spec.=20

Cheers, Manav

> -----Original Message-----
> From: Shahram Davari [mailto:davari@broadcom.com]=20
> Sent: Friday, January 21, 2011 4.59 AM
> To: Bhatia, Manav (Manav); tictoc@ietf.org
> Subject: RE: UDP checksum
>=20
> Hi Manav,
>=20
> UDP checksum is usually not verified before updating the CF.=20
> After CF update it is incrementally recalculated. The end=20
> host will then verify the checksum for correctness.
>=20
> Regards,
> Shahram
>=20
> -----Original Message-----
> From: tictoc-bounces@ietf.org=20
> [mailto:tictoc-bounces@ietf.org] On Behalf Of Bhatia, Manav (Manav)
> Sent: Thursday, January 20, 2011 3:16 PM
> To: tictoc@ietf.org
> Subject: [TICTOC] UDP checksum
>=20
> Hi,
>=20
> Are the LSRs acting as TCs expected to verify the checksum=20
> before they update the correction field? If no, then there is=20
> no point in these LSRs in updating the UDP checksum as they=20
> will "correct" the checksum when its recomputed after=20
> modifying the CF field. In this case wouldn't it make more=20
> sense to just update the checksum at the MPLS terminating point?
>=20
> I also think that updating the UDP checksum may be redundant=20
> as the LSRs are anyways verifying the outer ethernet checksum=20
> before accepting any packets. Any thoughts here?
>=20
> Cheers, Manav
>=20
> --
> Manav Bhatia,
> IP Division, Alcatel-Lucent,
> Bangalore - India
>=20
> =20
> _______________________________________________
> TICTOC mailing list
> TICTOC@ietf.org
> https://www.ietf.org/mailman/listinfo/tictoc
>=20
>=20
>=20


From stbryant@cisco.com  Fri Jan 21 12:25:00 2011
Return-Path: <stbryant@cisco.com>
X-Original-To: tictoc@core3.amsl.com
Delivered-To: tictoc@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id B6B063A67F6 for <tictoc@core3.amsl.com>; Fri, 21 Jan 2011 12:25:00 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.549
X-Spam-Level: 
X-Spam-Status: No, score=-110.549 tagged_above=-999 required=5 tests=[AWL=0.050, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id frWYrV5hwcFs for <tictoc@core3.amsl.com>; Fri, 21 Jan 2011 12:24:45 -0800 (PST)
Received: from rtp-iport-1.cisco.com (rtp-iport-1.cisco.com [64.102.122.148]) by core3.amsl.com (Postfix) with ESMTP id CB9163A67F8 for <tictoc@ietf.org>; Fri, 21 Jan 2011 12:24:45 -0800 (PST)
Authentication-Results: rtp-iport-1.cisco.com; dkim=neutral (message not signed) header.i=none
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgcFAJZ7OU1AZnwN/2dsb2JhbACWTI4dc6FvglMOAZgyhVAEix8
Received: from rtp-core-2.cisco.com ([64.102.124.13]) by rtp-iport-1.cisco.com with ESMTP; 21 Jan 2011 20:27:32 +0000
Received: from cisco.com (mrwint.cisco.com [64.103.71.48]) by rtp-core-2.cisco.com (8.13.8/8.14.3) with ESMTP id p0LKRVTu013812 for <tictoc@ietf.org>; Fri, 21 Jan 2011 20:27:31 GMT
Received: from stbryant-mac2.lan (localhost [127.0.0.1]) by cisco.com (8.11.7p3+Sun/8.8.8) with ESMTP id p0LKRT817454; Fri, 21 Jan 2011 20:27:30 GMT
Message-ID: <4D39EC31.10602@cisco.com>
Date: Fri, 21 Jan 2011 20:27:29 +0000
From: Stewart Bryant <stbryant@cisco.com>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.2.13) Gecko/20101207 Lightning/1.0b2 Thunderbird/3.1.7
MIME-Version: 1.0
To: tictoc@ietf.org
References: <7C362EEF9C7896468B36C9B79200D8350CFB0DFDA7@INBANSXCHMBSA1.in.alcatel-lucent.com>	<2C2F1EBA8050E74EA81502D5740B4BD6941B04CC39@SJEXCHCCR02.corp.ad.broadcom.com>	<7C362EEF9C7896468B36C9B79200D8350CFB0DFDAA@INBANSXCHMBSA1.in.alcatel-lucent.com> <2C2F1EBA8050E74EA81502D5740B4BD6941B04CC6D@SJEXCHCCR02.corp.ad.broadcom.com>
In-Reply-To: <2C2F1EBA8050E74EA81502D5740B4BD6941B04CC6D@SJEXCHCCR02.corp.ad.broadcom.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [TICTOC] UDP checksum
X-BeenThere: tictoc@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: stbryant@cisco.com
List-Id: Timing over IP Connection and Transfer of Clock BOF <tictoc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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, 21 Jan 2011 20:25:00 -0000

Presumably this is a v6 discussion. I can't see any point in using the 
c/s in v4.

WRT v6 there is a movement to make this optional (the debate is 
happening in 6lowlan, and I think that we should be pushing to turn it 
off for PTP.

The worst that can happen is that we receive a corrupt pkt and either 
junk it, or put it in the timing servo whereupon it gets rejected as an 
outlier.

- Stewart



On 20/01/2011 23:52, Shahram Davari wrote:
> Hi Manav,
>
> The minimum requirement is to do UDP checksum incremental update on transmission. If full update is done then UDP checksum must be verified on reception as well.
>
> Thx
> Shahram
>
> -----Original Message-----
> From: Bhatia, Manav (Manav) [mailto:manav.bhatia@alcatel-lucent.com]
> Sent: Thursday, January 20, 2011 3:33 PM
> To: Shahram Davari; tictoc@ietf.org
> Subject: RE: UDP checksum
>
> Hi Shahram,
>
> It may be ok as long as the HWs are incrementally recalculating it. However, if its being done afresh then we have an issue. I don't see how the HW behavior can be mandated in a spec.
>
> Cheers, Manav
>
>> -----Original Message-----
>> From: Shahram Davari [mailto:davari@broadcom.com]
>> Sent: Friday, January 21, 2011 4.59 AM
>> To: Bhatia, Manav (Manav); tictoc@ietf.org
>> Subject: RE: UDP checksum
>>
>> Hi Manav,
>>
>> UDP checksum is usually not verified before updating the CF.
>> After CF update it is incrementally recalculated. The end
>> host will then verify the checksum for correctness.
>>
>> Regards,
>> Shahram
>>
>> -----Original Message-----
>> From: tictoc-bounces@ietf.org
>> [mailto:tictoc-bounces@ietf.org] On Behalf Of Bhatia, Manav (Manav)
>> Sent: Thursday, January 20, 2011 3:16 PM
>> To: tictoc@ietf.org
>> Subject: [TICTOC] UDP checksum
>>
>> Hi,
>>
>> Are the LSRs acting as TCs expected to verify the checksum
>> before they update the correction field? If no, then there is
>> no point in these LSRs in updating the UDP checksum as they
>> will "correct" the checksum when its recomputed after
>> modifying the CF field. In this case wouldn't it make more
>> sense to just update the checksum at the MPLS terminating point?
>>
>> I also think that updating the UDP checksum may be redundant
>> as the LSRs are anyways verifying the outer ethernet checksum
>> before accepting any packets. Any thoughts here?
>>
>> Cheers, Manav
>>
>> --
>> Manav Bhatia,
>> IP Division, Alcatel-Lucent,
>> Bangalore - India
>>
>>
>> _______________________________________________
>> TICTOC mailing list
>> TICTOC@ietf.org
>> https://www.ietf.org/mailman/listinfo/tictoc
>>
>>
>>
> _______________________________________________
> TICTOC mailing list
> TICTOC@ietf.org
> https://www.ietf.org/mailman/listinfo/tictoc
>


-- 
For corporate legal information go to:

http://www.cisco.com/web/about/doing_business/legal/cri/index.html



From tme@americafree.tv  Fri Jan 21 12:36:27 2011
Return-Path: <tme@americafree.tv>
X-Original-To: tictoc@core3.amsl.com
Delivered-To: tictoc@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 0B9233A67F6 for <tictoc@core3.amsl.com>; Fri, 21 Jan 2011 12:36:27 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.277
X-Spam-Level: 
X-Spam-Status: No, score=-102.277 tagged_above=-999 required=5 tests=[AWL=0.322, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id K-Wo80ZlOxBr for <tictoc@core3.amsl.com>; Fri, 21 Jan 2011 12:36:26 -0800 (PST)
Received: from mail.americafree.tv (rossini.americafree.tv [63.105.122.34]) by core3.amsl.com (Postfix) with ESMTP id C687F3A67F5 for <tictoc@ietf.org>; Fri, 21 Jan 2011 12:36:25 -0800 (PST)
Received: from [IPv6:::1] (rossini.americafree.tv [63.105.122.34]) by mail.americafree.tv (Postfix) with ESMTP id 6B8BE9B5366D; Fri, 21 Jan 2011 15:39:12 -0500 (EST)
Mime-Version: 1.0 (Apple Message framework v1081)
Content-Type: text/plain; charset=us-ascii
From: Marshall Eubanks <tme@americafree.tv>
In-Reply-To: <4D39EC31.10602@cisco.com>
Date: Fri, 21 Jan 2011 15:39:08 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <01E54480-7D98-46F8-B82A-21A178044512@americafree.tv>
References: <7C362EEF9C7896468B36C9B79200D8350CFB0DFDA7@INBANSXCHMBSA1.in.alcatel-lucent.com>	<2C2F1EBA8050E74EA81502D5740B4BD6941B04CC39@SJEXCHCCR02.corp.ad.broadcom.com>	<7C362EEF9C7896468B36C9B79200D8350CFB0DFDAA@INBANSXCHMBSA1.in.alcatel-lucent.com> <2C2F1EBA8050E74EA81502D5740B4BD6941B04CC6D@SJEXCHCCR02.corp.ad.broadcom.com> <4D39EC31.10602@cisco.com>
To: stbryant@cisco.com
X-Mailer: Apple Mail (2.1081)
Cc: tictoc@ietf.org
Subject: Re: [TICTOC] UDP checksum
X-BeenThere: tictoc@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Timing over IP Connection and Transfer of Clock BOF <tictoc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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, 21 Jan 2011 20:36:27 -0000

On Jan 21, 2011, at 3:27 PM, Stewart Bryant wrote:

> Presumably this is a v6 discussion. I can't see any point in using the =
c/s in v4.
>=20
> WRT v6 there is a movement to make this optional (the debate is =
happening in 6lowlan, and I think that we should be pushing to turn it =
off for PTP.
>=20
> The worst that can happen is that we receive a corrupt pkt and either =
junk it, or put it in the timing servo whereupon it gets rejected as an =
outlier.
>=20

I think you are referring to this=20

which is (will be shortly) in 6man

http://tools.ietf.org/html/draft-eubanks-chimento-6man-01

This is for the case where there is an "inner" packet with a header and =
checksum, so that the "outer" packet doesn't need protection.

Regards
Marshall

> - Stewart
>=20
>=20
>=20
> On 20/01/2011 23:52, Shahram Davari wrote:
>> Hi Manav,
>>=20
>> The minimum requirement is to do UDP checksum incremental update on =
transmission. If full update is done then UDP checksum must be verified =
on reception as well.
>>=20
>> Thx
>> Shahram
>>=20
>> -----Original Message-----
>> From: Bhatia, Manav (Manav) [mailto:manav.bhatia@alcatel-lucent.com]
>> Sent: Thursday, January 20, 2011 3:33 PM
>> To: Shahram Davari; tictoc@ietf.org
>> Subject: RE: UDP checksum
>>=20
>> Hi Shahram,
>>=20
>> It may be ok as long as the HWs are incrementally recalculating it. =
However, if its being done afresh then we have an issue. I don't see how =
the HW behavior can be mandated in a spec.
>>=20
>> Cheers, Manav
>>=20
>>> -----Original Message-----
>>> From: Shahram Davari [mailto:davari@broadcom.com]
>>> Sent: Friday, January 21, 2011 4.59 AM
>>> To: Bhatia, Manav (Manav); tictoc@ietf.org
>>> Subject: RE: UDP checksum
>>>=20
>>> Hi Manav,
>>>=20
>>> UDP checksum is usually not verified before updating the CF.
>>> After CF update it is incrementally recalculated. The end
>>> host will then verify the checksum for correctness.
>>>=20
>>> Regards,
>>> Shahram
>>>=20
>>> -----Original Message-----
>>> From: tictoc-bounces@ietf.org
>>> [mailto:tictoc-bounces@ietf.org] On Behalf Of Bhatia, Manav (Manav)
>>> Sent: Thursday, January 20, 2011 3:16 PM
>>> To: tictoc@ietf.org
>>> Subject: [TICTOC] UDP checksum
>>>=20
>>> Hi,
>>>=20
>>> Are the LSRs acting as TCs expected to verify the checksum
>>> before they update the correction field? If no, then there is
>>> no point in these LSRs in updating the UDP checksum as they
>>> will "correct" the checksum when its recomputed after
>>> modifying the CF field. In this case wouldn't it make more
>>> sense to just update the checksum at the MPLS terminating point?
>>>=20
>>> I also think that updating the UDP checksum may be redundant
>>> as the LSRs are anyways verifying the outer ethernet checksum
>>> before accepting any packets. Any thoughts here?
>>>=20
>>> Cheers, Manav
>>>=20
>>> --
>>> Manav Bhatia,
>>> IP Division, Alcatel-Lucent,
>>> Bangalore - India
>>>=20
>>>=20
>>> _______________________________________________
>>> TICTOC mailing list
>>> TICTOC@ietf.org
>>> https://www.ietf.org/mailman/listinfo/tictoc
>>>=20
>>>=20
>>>=20
>> _______________________________________________
>> TICTOC mailing list
>> TICTOC@ietf.org
>> https://www.ietf.org/mailman/listinfo/tictoc
>>=20
>=20
>=20
> --=20
> For corporate legal information go to:
>=20
> http://www.cisco.com/web/about/doing_business/legal/cri/index.html
>=20
>=20
> _______________________________________________
> TICTOC mailing list
> TICTOC@ietf.org
> https://www.ietf.org/mailman/listinfo/tictoc
>=20


From michel.ouellette@huawei.com  Fri Jan 21 13:32:26 2011
Return-Path: <michel.ouellette@huawei.com>
X-Original-To: tictoc@core3.amsl.com
Delivered-To: tictoc@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id BBD333A6AA8 for <tictoc@core3.amsl.com>; Fri, 21 Jan 2011 13:32:26 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id JCsg1VsbXujl for <tictoc@core3.amsl.com>; Fri, 21 Jan 2011 13:32:24 -0800 (PST)
Received: from usaga04-in.huawei.com (usaga04-in.huawei.com [206.16.17.180]) by core3.amsl.com (Postfix) with ESMTP id C206E3A6823 for <tictoc@ietf.org>; Fri, 21 Jan 2011 13:32:24 -0800 (PST)
Received: from huawei.com (usaga04-in [172.18.4.101]) by usaga04-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0LFE00DRQ6MN2K@usaga04-in.huawei.com> for tictoc@ietf.org; Fri, 21 Jan 2011 15:35:11 -0600 (CST)
Received: from dfweml201-edg.china.huawei.com ([172.18.9.107]) by usaga04-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug  8 2006)) with ESMTPS id <0LFE00CDM6MM7Y@usaga04-in.huawei.com> for tictoc@ietf.org; Fri, 21 Jan 2011 15:35:11 -0600 (CST)
Received: from DFWEML402-HUB.china.huawei.com (10.193.5.102) by dfweml201-edg.china.huawei.com (172.18.9.107) with Microsoft SMTP Server (TLS) id 14.1.270.1; Fri, 21 Jan 2011 13:35:01 -0800
Received: from DFWEML502-MBX.china.huawei.com ([fe80::1086:4a1f:19fa:9025]) by DFWEML402-HUB.china.huawei.com ([::1]) with mapi id 14.01.0270.001; Fri, 21 Jan 2011 13:35:10 -0800
Date: Fri, 21 Jan 2011 21:34:09 +0000
From: michel ouellette <michel.ouellette@huawei.com>
In-reply-to: <4D39EC31.10602@cisco.com>
X-Originating-IP: [10.193.60.111]
To: "tictoc@ietf.org" <tictoc@ietf.org>
Message-id: <1D61EBB3487E574AAAB0D3373BAB812D4FCE4F@dfweml502-mbx.china.huawei.com>
MIME-version: 1.0
Content-type: text/plain; charset=us-ascii
Content-language: en-US
Content-transfer-encoding: 7BIT
Deferred-delivery: Fri, 21 Jan 2011 21:33:00 +0000
Accept-Language: en-CA, en-US
Thread-topic: [TICTOC] UDP checksum
Thread-index: AQHLuam1MK0rfXfuUEW3m4OCHcDGYpPb7hag
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
References: <7C362EEF9C7896468B36C9B79200D8350CFB0DFDA7@INBANSXCHMBSA1.in.alcatel-lucent.com> <2C2F1EBA8050E74EA81502D5740B4BD6941B04CC39@SJEXCHCCR02.corp.ad.broadcom.com> <7C362EEF9C7896468B36C9B79200D8350CFB0DFDAA@INBANSXCHMBSA1.in.alcatel-lucent.com> <2C2F1EBA8050E74EA81502D5740B4BD6941B04CC6D@SJEXCHCCR02.corp.ad.broadcom.com> <4D39EC31.10602@cisco.com>
Subject: Re: [TICTOC] UDP checksum
X-BeenThere: tictoc@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Timing over IP Connection and Transfer of Clock BOF <tictoc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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, 21 Jan 2011 21:32:26 -0000

PTP GM and OC are allowed to set the UDP checksum to 0 (according to the standard - UDP/IPv4 encap). In such case no action on the updating the UDP checksum would be required by the TCs.  The TC itself can also set the UDP checksum to 0 (according to the standard any intermediate node can do so).

This would also apply to the case where you have TCs interconnected by two BCs.



- Michel



-----Original Message-----
From: tictoc-bounces@ietf.org [mailto:tictoc-bounces@ietf.org] On Behalf Of Stewart Bryant
Sent: January 21, 2011 03:27 PM
To: tictoc@ietf.org
Subject: Re: [TICTOC] UDP checksum

Presumably this is a v6 discussion. I can't see any point in using the 
c/s in v4.

WRT v6 there is a movement to make this optional (the debate is 
happening in 6lowlan, and I think that we should be pushing to turn it 
off for PTP.

The worst that can happen is that we receive a corrupt pkt and either 
junk it, or put it in the timing servo whereupon it gets rejected as an 
outlier.

- Stewart



On 20/01/2011 23:52, Shahram Davari wrote:
> Hi Manav,
>
> The minimum requirement is to do UDP checksum incremental update on transmission. If full update is done then UDP checksum must be verified on reception as well.
>
> Thx
> Shahram
>
> -----Original Message-----
> From: Bhatia, Manav (Manav) [mailto:manav.bhatia@alcatel-lucent.com]
> Sent: Thursday, January 20, 2011 3:33 PM
> To: Shahram Davari; tictoc@ietf.org
> Subject: RE: UDP checksum
>
> Hi Shahram,
>
> It may be ok as long as the HWs are incrementally recalculating it. However, if its being done afresh then we have an issue. I don't see how the HW behavior can be mandated in a spec.
>
> Cheers, Manav
>
>> -----Original Message-----
>> From: Shahram Davari [mailto:davari@broadcom.com]
>> Sent: Friday, January 21, 2011 4.59 AM
>> To: Bhatia, Manav (Manav); tictoc@ietf.org
>> Subject: RE: UDP checksum
>>
>> Hi Manav,
>>
>> UDP checksum is usually not verified before updating the CF.
>> After CF update it is incrementally recalculated. The end
>> host will then verify the checksum for correctness.
>>
>> Regards,
>> Shahram
>>
>> -----Original Message-----
>> From: tictoc-bounces@ietf.org
>> [mailto:tictoc-bounces@ietf.org] On Behalf Of Bhatia, Manav (Manav)
>> Sent: Thursday, January 20, 2011 3:16 PM
>> To: tictoc@ietf.org
>> Subject: [TICTOC] UDP checksum
>>
>> Hi,
>>
>> Are the LSRs acting as TCs expected to verify the checksum
>> before they update the correction field? If no, then there is
>> no point in these LSRs in updating the UDP checksum as they
>> will "correct" the checksum when its recomputed after
>> modifying the CF field. In this case wouldn't it make more
>> sense to just update the checksum at the MPLS terminating point?
>>
>> I also think that updating the UDP checksum may be redundant
>> as the LSRs are anyways verifying the outer ethernet checksum
>> before accepting any packets. Any thoughts here?
>>
>> Cheers, Manav
>>
>> --
>> Manav Bhatia,
>> IP Division, Alcatel-Lucent,
>> Bangalore - India
>>
>>
>> _______________________________________________
>> TICTOC mailing list
>> TICTOC@ietf.org
>> https://www.ietf.org/mailman/listinfo/tictoc
>>
>>
>>
> _______________________________________________
> TICTOC mailing list
> TICTOC@ietf.org
> https://www.ietf.org/mailman/listinfo/tictoc
>


-- 
For corporate legal information go to:

http://www.cisco.com/web/about/doing_business/legal/cri/index.html


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

From manav.bhatia@alcatel-lucent.com  Fri Jan 21 17:12:03 2011
Return-Path: <manav.bhatia@alcatel-lucent.com>
X-Original-To: tictoc@core3.amsl.com
Delivered-To: tictoc@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 51B7528C0D6 for <tictoc@core3.amsl.com>; Fri, 21 Jan 2011 17:12:03 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.229
X-Spam-Level: 
X-Spam-Status: No, score=-6.229 tagged_above=-999 required=5 tests=[AWL=0.370,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Rf7ffB52DjON for <tictoc@core3.amsl.com>; Fri, 21 Jan 2011 17:12:02 -0800 (PST)
Received: from ihemail4.lucent.com (ihemail4.lucent.com [135.245.0.39]) by core3.amsl.com (Postfix) with ESMTP id DD6753A688A for <tictoc@ietf.org>; Fri, 21 Jan 2011 17:12:01 -0800 (PST)
Received: from inbansmailrelay2.in.alcatel-lucent.com (h135-250-11-33.lucent.com [135.250.11.33]) by ihemail4.lucent.com (8.13.8/IER-o) with ESMTP id p0M1Ed2f008889 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Fri, 21 Jan 2011 19:14:42 -0600 (CST)
Received: from INBANSXCHHUB01.in.alcatel-lucent.com (inbansxchhub01.in.alcatel-lucent.com [135.250.12.32]) by inbansmailrelay2.in.alcatel-lucent.com (8.14.3/8.14.3/GMO) with ESMTP id p0M1Ectt032672 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Sat, 22 Jan 2011 06:44:38 +0530
Received: from INBANSXCHMBSA1.in.alcatel-lucent.com ([135.250.12.56]) by INBANSXCHHUB01.in.alcatel-lucent.com ([135.250.12.32]) with mapi; Sat, 22 Jan 2011 06:44:38 +0530
From: "Bhatia, Manav (Manav)" <manav.bhatia@alcatel-lucent.com>
To: michel ouellette <michel.ouellette@huawei.com>, "tictoc@ietf.org" <tictoc@ietf.org>
Date: Sat, 22 Jan 2011 06:44:37 +0530
Thread-Topic: [TICTOC] UDP checksum
Thread-Index: AQHLuam1MK0rfXfuUEW3m4OCHcDGYpPb7haggAA/3IA=
Message-ID: <7C362EEF9C7896468B36C9B79200D8350CFB18AE4A@INBANSXCHMBSA1.in.alcatel-lucent.com>
References: <7C362EEF9C7896468B36C9B79200D8350CFB0DFDA7@INBANSXCHMBSA1.in.alcatel-lucent.com> <2C2F1EBA8050E74EA81502D5740B4BD6941B04CC39@SJEXCHCCR02.corp.ad.broadcom.com> <7C362EEF9C7896468B36C9B79200D8350CFB0DFDAA@INBANSXCHMBSA1.in.alcatel-lucent.com> <2C2F1EBA8050E74EA81502D5740B4BD6941B04CC6D@SJEXCHCCR02.corp.ad.broadcom.com> <4D39EC31.10602@cisco.com> <1D61EBB3487E574AAAB0D3373BAB812D4FCE4F@dfweml502-mbx.china.huawei.com>
In-Reply-To: <1D61EBB3487E574AAAB0D3373BAB812D4FCE4F@dfweml502-mbx.china.huawei.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Scanned-By: MIMEDefang 2.57 on 135.245.2.39
X-Scanned-By: MIMEDefang 2.64 on 135.250.11.33
Subject: Re: [TICTOC] UDP checksum
X-BeenThere: tictoc@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Timing over IP Connection and Transfer of Clock BOF <tictoc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/tictoc>, <mailto:tictoc-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tictoc>
List-Post: <mailto:tictoc@ietf.org>
List-Help: <mailto:tictoc-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tictoc>, <mailto:tictoc-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 22 Jan 2011 01:12:03 -0000

Michel,

The standard only allows the TCs to reset the checksum to 0 when transporti=
ng PTP over UDP/IPv4.

My original question was wrt IPv6 - I find correcting the checksum onerous =
when devices are adding the residence time in the correctionField in HW and=
 I think we should do away with this because if a fresh checksum is being c=
omputed then it defeats the whole purpose of having a checksum in the first=
 place. Assume an LSR receives a corrupted MPLS packet. We now change the C=
F and will end up updating the checksum based on the contents of the corrup=
ted packet.

Cheers, Manav

> -----Original Message-----
> From: tictoc-bounces@ietf.org=20
> [mailto:tictoc-bounces@ietf.org] On Behalf Of michel ouellette
> Sent: Saturday, January 22, 2011 3.04 AM
> To: tictoc@ietf.org
> Subject: Re: [TICTOC] UDP checksum
>=20
>=20
>=20
> PTP GM and OC are allowed to set the UDP checksum to 0=20
> (according to the standard - UDP/IPv4 encap). In such case no=20
> action on the updating the UDP checksum would be required by=20
> the TCs.  The TC itself can also set the UDP checksum to 0=20
> (according to the standard any intermediate node can do so).
>=20
> This would also apply to the case where you have TCs=20
> interconnected by two BCs.
>=20
>=20
>=20
> - Michel
>=20
>=20
>=20
> -----Original Message-----
> From: tictoc-bounces@ietf.org=20
> [mailto:tictoc-bounces@ietf.org] On Behalf Of Stewart Bryant
> Sent: January 21, 2011 03:27 PM
> To: tictoc@ietf.org
> Subject: Re: [TICTOC] UDP checksum
>=20
> Presumably this is a v6 discussion. I can't see any point in=20
> using the=20
> c/s in v4.
>=20
> WRT v6 there is a movement to make this optional (the debate is=20
> happening in 6lowlan, and I think that we should be pushing=20
> to turn it=20
> off for PTP.
>=20
> The worst that can happen is that we receive a corrupt pkt and either=20
> junk it, or put it in the timing servo whereupon it gets=20
> rejected as an=20
> outlier.
>=20
> - Stewart
>=20
>=20
>=20
> On 20/01/2011 23:52, Shahram Davari wrote:
> > Hi Manav,
> >
> > The minimum requirement is to do UDP checksum incremental=20
> update on transmission. If full update is done then UDP=20
> checksum must be verified on reception as well.
> >
> > Thx
> > Shahram
> >
> > -----Original Message-----
> > From: Bhatia, Manav (Manav) [mailto:manav.bhatia@alcatel-lucent.com]
> > Sent: Thursday, January 20, 2011 3:33 PM
> > To: Shahram Davari; tictoc@ietf.org
> > Subject: RE: UDP checksum
> >
> > Hi Shahram,
> >
> > It may be ok as long as the HWs are incrementally=20
> recalculating it. However, if its being done afresh then we=20
> have an issue. I don't see how the HW behavior can be=20
> mandated in a spec.
> >
> > Cheers, Manav
> >
> >> -----Original Message-----
> >> From: Shahram Davari [mailto:davari@broadcom.com]
> >> Sent: Friday, January 21, 2011 4.59 AM
> >> To: Bhatia, Manav (Manav); tictoc@ietf.org
> >> Subject: RE: UDP checksum
> >>
> >> Hi Manav,
> >>
> >> UDP checksum is usually not verified before updating the CF.
> >> After CF update it is incrementally recalculated. The end
> >> host will then verify the checksum for correctness.
> >>
> >> Regards,
> >> Shahram
> >>
> >> -----Original Message-----
> >> From: tictoc-bounces@ietf.org
> >> [mailto:tictoc-bounces@ietf.org] On Behalf Of Bhatia, Manav (Manav)
> >> Sent: Thursday, January 20, 2011 3:16 PM
> >> To: tictoc@ietf.org
> >> Subject: [TICTOC] UDP checksum
> >>
> >> Hi,
> >>
> >> Are the LSRs acting as TCs expected to verify the checksum
> >> before they update the correction field? If no, then there is
> >> no point in these LSRs in updating the UDP checksum as they
> >> will "correct" the checksum when its recomputed after
> >> modifying the CF field. In this case wouldn't it make more
> >> sense to just update the checksum at the MPLS terminating point?
> >>
> >> I also think that updating the UDP checksum may be redundant
> >> as the LSRs are anyways verifying the outer ethernet checksum
> >> before accepting any packets. Any thoughts here?
> >>
> >> Cheers, Manav
> >>
> >> --
> >> Manav Bhatia,
> >> IP Division, Alcatel-Lucent,
> >> Bangalore - India
> >>
> >>
> >> _______________________________________________
> >> TICTOC mailing list
> >> TICTOC@ietf.org
> >> https://www.ietf.org/mailman/listinfo/tictoc
> >>
> >>
> >>
> > _______________________________________________
> > TICTOC mailing list
> > TICTOC@ietf.org
> > https://www.ietf.org/mailman/listinfo/tictoc
> >
>=20
>=20
> --=20
> For corporate legal information go to:
>=20
> http://www.cisco.com/web/about/doing_business/legal/cri/index.html
>=20
>=20
> _______________________________________________
> TICTOC mailing list
> TICTOC@ietf.org
> https://www.ietf.org/mailman/listinfo/tictoc
> _______________________________________________
> TICTOC mailing list
> TICTOC@ietf.org
> https://www.ietf.org/mailman/listinfo/tictoc
> =

From talmi@marvell.com  Sat Jan 22 23:05:01 2011
Return-Path: <talmi@marvell.com>
X-Original-To: tictoc@core3.amsl.com
Delivered-To: tictoc@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 119113A6964 for <tictoc@core3.amsl.com>; Sat, 22 Jan 2011 23:05:01 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.392
X-Spam-Level: 
X-Spam-Status: No, score=-5.392 tagged_above=-999 required=5 tests=[AWL=-1.208, BAYES_40=-0.185, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id T1w0WzZi4c11 for <tictoc@core3.amsl.com>; Sat, 22 Jan 2011 23:04:57 -0800 (PST)
Received: from na3sys009aog111.obsmtp.com (na3sys009aog111.obsmtp.com [74.125.149.205]) by core3.amsl.com (Postfix) with SMTP id 507B53A68D0 for <tictoc@ietf.org>; Sat, 22 Jan 2011 23:04:56 -0800 (PST)
Received: from source ([65.219.4.129]) (using TLSv1) by na3sys009aob111.postini.com ([74.125.148.12]) with SMTP ID DSNKTTvTw7FFPd2EHUW/jazcQfvGVElRLXi6@postini.com; Sat, 22 Jan 2011 23:07:48 PST
Received: from YK-HUB01.marvell.com (10.4.102.51) by sc-owa01.marvell.com (10.93.76.21) with Microsoft SMTP Server (TLS) id 8.2.213.0; Sat, 22 Jan 2011 23:07:40 -0800
Received: from IL-MB01.marvell.com ([10.4.102.53]) by YK-HUB01.marvell.com ([10.4.102.51]) with mapi; Sun, 23 Jan 2011 09:07:37 +0200
From: Tal Mizrahi <talmi@marvell.com>
To: "Bhatia, Manav (Manav)" <manav.bhatia@alcatel-lucent.com>, "tictoc@ietf.org" <tictoc@ietf.org>
Date: Sun, 23 Jan 2011 09:07:37 +0200
Thread-Topic: [TICTOC] 1588 over PW - MAC SA Modification
Thread-Index: Acu6zDcTfu03WsueQMS9oTtt+Ewbug==
Message-ID: <74470498B659FA4687F0B0018C19A89CFCDC146995@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_74470498B659FA4687F0B0018C19A89CFCDC146995ILMB01marvell_"
MIME-Version: 1.0
Subject: [TICTOC]  1588 over PW - MAC SA Modification
X-BeenThere: tictoc@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Timing over IP Connection and Transfer of Clock BOF <tictoc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/tictoc>, <mailto:tictoc-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tictoc>
List-Post: <mailto:tictoc@ietf.org>
List-Help: <mailto:tictoc-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tictoc>, <mailto:tictoc-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 23 Jan 2011 07:05:01 -0000

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

Hi Manav et al,

When using 1588-over-Ethernet, each TC that modifies the CF also updates th=
e Ethernet MAC SA to the address of the TC. This is because an 802.1 bridge=
 that modifies a packet must update its source address to the bridge's addr=
ess.

In draft-davari-tictoc-1588overmpls-01, when using 1588-over-PW, the LSR TC=
s update the CF in the passenger Ethernet packet. I am wondering whether th=
e MAC SA of the passenger Ethernet packet must be updated in this case.
This issue applies also to 1588-over-IP-over-Ethernet-over-PW.

Regards,
Tal.



--_000_74470498B659FA4687F0B0018C19A89CFCDC146995ILMB01marvell_
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=3D"http://www.w3.org/TR/REC-html40">

<head>
<meta http-equiv=3DContent-Type content=3D"text/html; charset=3Dus-ascii">
<meta name=3DGenerator content=3D"Microsoft Word 11 (filtered medium)">
<style>
<!--
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman";}
a:link, span.MsoHyperlink
	{color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{color:purple;
	text-decoration:underline;}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:Arial;
	color:windowtext;}
@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 lang=3DEN-US link=3Dblue vlink=3Dpurple>

<div class=3DSection1>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span style=3D'font-size:1=
0.0pt;
font-family:Arial'>Hi Manav et al,<o:p></o:p></span></font></p>

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

<p class=3DMsoNormal><font size=3D2 face=3DArial><span style=3D'font-size:1=
0.0pt;
font-family:Arial'>When using 1588-over-Ethernet, each TC that modifies the=
 CF also
updates the Ethernet MAC SA to the address of the TC. This is because an 80=
2.1
bridge that modifies a packet must update its source address to the bridge&=
#8217;s
address.<o:p></o:p></span></font></p>

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

<p class=3DMsoNormal><font size=3D2 face=3DArial><span style=3D'font-size:1=
0.0pt;
font-family:Arial'>In draft-davari-tictoc-1588overmpls-01, when using 1588-=
over-PW,
the LSR TCs update the CF in the passenger Ethernet packet. I am wondering
whether the MAC SA of the passenger Ethernet packet must be updated in this
case.<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span style=3D'font-size:1=
0.0pt;
font-family:Arial'>This issue applies also to 1588-over-IP-over-Ethernet-ov=
er-PW.<o:p></o:p></span></font></p>

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

<p class=3DMsoNormal><font size=3D2 face=3DArial><span style=3D'font-size:1=
0.0pt;
font-family:Arial'>Regards,<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span style=3D'font-size:1=
0.0pt;
font-family:Arial'>Tal. &nbsp;<o:p></o:p></span></font></p>

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

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

</div>

</body>

</html>

--_000_74470498B659FA4687F0B0018C19A89CFCDC146995ILMB01marvell_--

From ronc.ntear@gmail.com  Sun Jan 23 07:43:46 2011
Return-Path: <ronc.ntear@gmail.com>
X-Original-To: tictoc@core3.amsl.com
Delivered-To: tictoc@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 586643A6900 for <tictoc@core3.amsl.com>; Sun, 23 Jan 2011 07:43:46 -0800 (PST)
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.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 66A7YwcUnaK8 for <tictoc@core3.amsl.com>; Sun, 23 Jan 2011 07:43:45 -0800 (PST)
Received: from mail-wy0-f172.google.com (mail-wy0-f172.google.com [74.125.82.172]) by core3.amsl.com (Postfix) with ESMTP id 0FE113A68FF for <tictoc@ietf.org>; Sun, 23 Jan 2011 07:43:44 -0800 (PST)
Received: by wyf23 with SMTP id 23so3472447wyf.31 for <tictoc@ietf.org>; Sun, 23 Jan 2011 07:46:36 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=k4liSIJ3cSuS0l1iK5NUXkHhY3E8FTuDhTECg1QfM6Y=; b=ND9q6F7W7xAzoXJ8bR9NHgNhcEeLnSO27joj9uJIyGy9OUIg0Slu7RXQPAWpzyg84/ /qlGux3FDjpK0imuqTIfg+D9D+uuAOOp1AqfaR94x03cJblzihxU6uTYp7rrqrTbIWcM azT1noX9SVBNgVGNP+9/2+pynImkAqXonhYuQ=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=fML3247c1/e7Q1mAXz5SKabYifH7cWTHACFFXbPnKf/WDOWyI9u4pVsaklq9FR47J0 5AU/OJa7O6ZQCpzYjbDJD7uJBYiav6gY823nsCJnruER8Y6txlvX7wXrjzSfN0mGg4Z4 5ejy6bDWQSfG6SPMzpopSQjkJ/Kc+ye0U/yhc=
MIME-Version: 1.0
Received: by 10.216.177.72 with SMTP id c50mr2557941wem.72.1295797595069; Sun, 23 Jan 2011 07:46:35 -0800 (PST)
Received: by 10.216.167.69 with HTTP; Sun, 23 Jan 2011 07:46:35 -0800 (PST)
In-Reply-To: <74470498B659FA4687F0B0018C19A89CFCDC146995@IL-MB01.marvell.com>
References: <74470498B659FA4687F0B0018C19A89CFCDC146995@IL-MB01.marvell.com>
Date: Sun, 23 Jan 2011 17:46:35 +0200
Message-ID: <AANLkTi=J2a2xQMKhVhn-iZ-zBu5osaH8Ob=+D7Zw8ES5@mail.gmail.com>
From: Ron Cohen <ronc.ntear@gmail.com>
To: Tal Mizrahi <talmi@marvell.com>
Content-Type: multipart/alternative; boundary=0016e65a09385adf07049a85638f
Cc: "tictoc@ietf.org" <tictoc@ietf.org>
Subject: Re: [TICTOC] 1588 over PW - MAC SA Modification
X-BeenThere: tictoc@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Timing over IP Connection and Transfer of Clock BOF <tictoc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/tictoc>, <mailto:tictoc-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tictoc>
List-Post: <mailto:tictoc@ietf.org>
List-Help: <mailto:tictoc-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tictoc>, <mailto:tictoc-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 23 Jan 2011 15:43:46 -0000

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

Hi Tal,

In my opinion since the LSR is not an 802.1 bridge it doesn't need to chang=
e
source MAC addresses while performing TC functions.

Best,
Ron

On Sun, Jan 23, 2011 at 9:07 AM, Tal Mizrahi <talmi@marvell.com> wrote:

>  Hi Manav et al,
>
>
>
> When using 1588-over-Ethernet, each TC that modifies the CF also updates
> the Ethernet MAC SA to the address of the TC. This is because an 802.1
> bridge that modifies a packet must update its source address to the bridg=
e=92s
> address.
>
>
>
> In draft-davari-tictoc-1588overmpls-01, when using 1588-over-PW, the LSR
> TCs update the CF in the passenger Ethernet packet. I am wondering whethe=
r
> the MAC SA of the passenger Ethernet packet must be updated in this case.
>
> This issue applies also to 1588-over-IP-over-Ethernet-over-PW.
>
>
>
> Regards,
>
> Tal.
>
>
>
>
>
> _______________________________________________
> TICTOC mailing list
> TICTOC@ietf.org
> https://www.ietf.org/mailman/listinfo/tictoc
>
>

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

<div dir=3D"ltr">Hi Tal,<br><br>In my opinion since the LSR is not an 802.1=
 bridge it doesn&#39;t need to change source MAC addresses while performing=
 TC functions.<br><br>Best,<br>Ron<br><br><div class=3D"gmail_quote">On Sun=
, Jan 23, 2011 at 9:07 AM, Tal Mizrahi <span dir=3D"ltr">&lt;<a href=3D"mai=
lto:talmi@marvell.com">talmi@marvell.com</a>&gt;</span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin: 0pt 0pt 0pt 0.8ex; borde=
r-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">








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

<div>

<p class=3D"MsoNormal"><font face=3D"Arial" size=3D"2"><span style=3D"font-=
size: 10pt; font-family: Arial;">Hi Manav et al,</span></font></p>

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

<p class=3D"MsoNormal"><font face=3D"Arial" size=3D"2"><span style=3D"font-=
size: 10pt; font-family: Arial;">When using 1588-over-Ethernet, each TC tha=
t modifies the CF also
updates the Ethernet MAC SA to the address of the TC. This is because an 80=
2.1
bridge that modifies a packet must update its source address to the bridge=
=92s
address.</span></font></p>

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

<p class=3D"MsoNormal"><font face=3D"Arial" size=3D"2"><span style=3D"font-=
size: 10pt; font-family: Arial;">In draft-davari-tictoc-1588overmpls-01, wh=
en using 1588-over-PW,
the LSR TCs update the CF in the passenger Ethernet packet. I am wondering
whether the MAC SA of the passenger Ethernet packet must be updated in this
case.</span></font></p>

<p class=3D"MsoNormal"><font face=3D"Arial" size=3D"2"><span style=3D"font-=
size: 10pt; font-family: Arial;">This issue applies also to 1588-over-IP-ov=
er-Ethernet-over-PW.</span></font></p>

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

<p class=3D"MsoNormal"><font face=3D"Arial" size=3D"2"><span style=3D"font-=
size: 10pt; font-family: Arial;">Regards,</span></font></p>

<p class=3D"MsoNormal"><font face=3D"Arial" size=3D"2"><span style=3D"font-=
size: 10pt; font-family: Arial;">Tal. =A0</span></font></p>

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

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

</div>

</div>


<br>_______________________________________________<br>
TICTOC mailing list<br>
<a href=3D"mailto:TICTOC@ietf.org">TICTOC@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/tictoc" target=3D"_blank">=
https://www.ietf.org/mailman/listinfo/tictoc</a><br>
<br></blockquote></div><br><div style=3D"visibility: hidden; left: -5000px;=
 position: absolute; z-index: 9999; padding: 0px; margin-left: 0px; margin-=
top: 0px; overflow: hidden; word-wrap: break-word; color: black; font-size:=
 10px; text-align: left; line-height: 130%;" id=3D"avg_ls_inline_popup">
</div></div>

--0016e65a09385adf07049a85638f--

From yaakov_s@rad.com  Wed Jan 26 00:47:50 2011
Return-Path: <yaakov_s@rad.com>
X-Original-To: tictoc@core3.amsl.com
Delivered-To: tictoc@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id B7A1C3A6960 for <tictoc@core3.amsl.com>; Wed, 26 Jan 2011 00:47:50 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.484
X-Spam-Level: 
X-Spam-Status: No, score=-102.484 tagged_above=-999 required=5 tests=[AWL=0.114, BAYES_00=-2.599, HTML_MESSAGE=0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id FESRQV7vE5if for <tictoc@core3.amsl.com>; Wed, 26 Jan 2011 00:47:46 -0800 (PST)
Received: from antivir1.rad.co.il (mx1-q.rad.co.il [80.74.100.136]) by core3.amsl.com (Postfix) with ESMTP id C7AB63A690E for <tictoc@ietf.org>; Wed, 26 Jan 2011 00:47:42 -0800 (PST)
Received: from exrad5.ad.rad.co.il ([192.114.24.28]) by antivir1.rad.co.il with ESMTP; 26 Jan 2011 10:50:41 +0200
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; Wed, 26 Jan 2011 10:50:41 +0200
Received: from EXRAD5.ad.rad.co.il ([fe80::ec3e:feb5:8bef:e3ba]) by exus4-drp.ad.rad.co.il ([fe80::5d6f:c2cb:2468:ee2%16]) with mapi id 14.01.0270.001; Wed, 26 Jan 2011 10:50:41 +0200
From: Yaakov Stein <yaakov_s@rad.com>
To: Ron Cohen <ronc.ntear@gmail.com>, Tal Mizrahi <talmi@marvell.com>
Thread-Topic: [TICTOC] 1588 over PW - MAC SA Modification
Thread-Index: AQHLuxS+KU5u+yWHG06QrXMkvswREZPi9Fvg
Date: Wed, 26 Jan 2011 08:50:39 +0000
Message-ID: <07F7D7DED63154409F13298786A2ADC903CD8C2A@EXRAD5.ad.rad.co.il>
References: <74470498B659FA4687F0B0018C19A89CFCDC146995@IL-MB01.marvell.com> <AANLkTi=J2a2xQMKhVhn-iZ-zBu5osaH8Ob=+D7Zw8ES5@mail.gmail.com>
In-Reply-To: <AANLkTi=J2a2xQMKhVhn-iZ-zBu5osaH8Ob=+D7Zw8ES5@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [192.115.243.62]
Content-Type: multipart/alternative; boundary="_000_07F7D7DED63154409F13298786A2ADC903CD8C2AEXRAD5adradcoil_"
MIME-Version: 1.0
Cc: "tictoc@ietf.org" <tictoc@ietf.org>
Subject: Re: [TICTOC] 1588 over PW - MAC SA Modification
X-BeenThere: tictoc@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Timing over IP Connection and Transfer of Clock BOF <tictoc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/tictoc>, <mailto:tictoc-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tictoc>
List-Post: <mailto:tictoc@ietf.org>
List-Help: <mailto:tictoc-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tictoc>, <mailto:tictoc-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 26 Jan 2011 08:47:50 -0000

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

Yet another layer violation problem, and yet another reason for preferring =
a pure-MLPS encap.

If we are talking about an Ethernet PW, there is no NSP defined for interme=
diate LSRs,
(even if we think of a PW with TC as a sequence of S-PEs there is no NSP th=
ere)
and so technically no way to do any Ethernet level processing.

Y(J)S

From: tictoc-bounces@ietf.org [mailto:tictoc-bounces@ietf.org] On Behalf Of=
 Ron Cohen
Sent: Sunday, January 23, 2011 17:47
To: Tal Mizrahi
Cc: tictoc@ietf.org
Subject: Re: [TICTOC] 1588 over PW - MAC SA Modification

Hi Tal,

In my opinion since the LSR is not an 802.1 bridge it doesn't need to chang=
e source MAC addresses while performing TC functions.

Best,
Ron
On Sun, Jan 23, 2011 at 9:07 AM, Tal Mizrahi <talmi@marvell.com<mailto:talm=
i@marvell.com>> wrote:
Hi Manav et al,

When using 1588-over-Ethernet, each TC that modifies the CF also updates th=
e Ethernet MAC SA to the address of the TC. This is because an 802.1 bridge=
 that modifies a packet must update its source address to the bridge's addr=
ess.

In draft-davari-tictoc-1588overmpls-01, when using 1588-over-PW, the LSR TC=
s update the CF in the passenger Ethernet packet. I am wondering whether th=
e MAC SA of the passenger Ethernet packet must be updated in this case.
This issue applies also to 1588-over-IP-over-Ethernet-over-PW.

Regards,
Tal.



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


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

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:x=3D"urn:schemas-microsoft-com:office:excel" xmlns:p=3D"urn:schemas-m=
icrosoft-com:office:powerpoint" xmlns:a=3D"urn:schemas-microsoft-com:office=
:access" xmlns:dt=3D"uuid:C2F41010-65B3-11d1-A29F-00AA00C14882" xmlns:s=3D"=
uuid:BDC6E3F0-6DA3-11d1-A2A3-00AA00C14882" xmlns:rs=3D"urn:schemas-microsof=
t-com:rowset" xmlns:z=3D"#RowsetSchema" xmlns:b=3D"urn:schemas-microsoft-co=
m:office:publisher" xmlns:ss=3D"urn:schemas-microsoft-com:office:spreadshee=
t" xmlns:c=3D"urn:schemas-microsoft-com:office:component:spreadsheet" xmlns=
:odc=3D"urn:schemas-microsoft-com:office:odc" xmlns:oa=3D"urn:schemas-micro=
soft-com:office:activation" xmlns:html=3D"http://www.w3.org/TR/REC-html40" =
xmlns:q=3D"http://schemas.xmlsoap.org/soap/envelope/" xmlns:rtc=3D"http://m=
icrosoft.com/officenet/conferencing" xmlns:D=3D"DAV:" xmlns:Repl=3D"http://=
schemas.microsoft.com/repl/" xmlns:mt=3D"http://schemas.microsoft.com/share=
point/soap/meetings/" xmlns:x2=3D"http://schemas.microsoft.com/office/excel=
/2003/xml" xmlns:ppda=3D"http://www.passport.com/NameSpace.xsd" xmlns:ois=
=3D"http://schemas.microsoft.com/sharepoint/soap/ois/" xmlns:dir=3D"http://=
schemas.microsoft.com/sharepoint/soap/directory/" xmlns:ds=3D"http://www.w3=
.org/2000/09/xmldsig#" xmlns:dsp=3D"http://schemas.microsoft.com/sharepoint=
/dsp" xmlns:udc=3D"http://schemas.microsoft.com/data/udc" xmlns:xsd=3D"http=
://www.w3.org/2001/XMLSchema" xmlns:sub=3D"http://schemas.microsoft.com/sha=
repoint/soap/2002/1/alerts/" xmlns:ec=3D"http://www.w3.org/2001/04/xmlenc#"=
 xmlns:sp=3D"http://schemas.microsoft.com/sharepoint/" xmlns:sps=3D"http://=
schemas.microsoft.com/sharepoint/soap/" xmlns:xsi=3D"http://www.w3.org/2001=
/XMLSchema-instance" xmlns:udcs=3D"http://schemas.microsoft.com/data/udc/so=
ap" xmlns:udcxf=3D"http://schemas.microsoft.com/data/udc/xmlfile" xmlns:udc=
p2p=3D"http://schemas.microsoft.com/data/udc/parttopart" xmlns:wf=3D"http:/=
/schemas.microsoft.com/sharepoint/soap/workflow/" xmlns:dsss=3D"http://sche=
mas.microsoft.com/office/2006/digsig-setup" xmlns:dssi=3D"http://schemas.mi=
crosoft.com/office/2006/digsig" xmlns:mdssi=3D"http://schemas.openxmlformat=
s.org/package/2006/digital-signature" xmlns:mver=3D"http://schemas.openxmlf=
ormats.org/markup-compatibility/2006" xmlns:m=3D"http://schemas.microsoft.c=
om/office/2004/12/omml" xmlns:mrels=3D"http://schemas.openxmlformats.org/pa=
ckage/2006/relationships" xmlns:spwp=3D"http://microsoft.com/sharepoint/web=
partpages" xmlns:ex12t=3D"http://schemas.microsoft.com/exchange/services/20=
06/types" xmlns:ex12m=3D"http://schemas.microsoft.com/exchange/services/200=
6/messages" xmlns:pptsl=3D"http://schemas.microsoft.com/sharepoint/soap/Sli=
deLibrary/" xmlns:spsl=3D"http://microsoft.com/webservices/SharePointPortal=
Server/PublishedLinksService" xmlns:Z=3D"urn:schemas-microsoft-com:" xmlns:=
st=3D"&#1;" xmlns=3D"http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
<meta name=3D"Generator" content=3D"Microsoft Word 12 (filtered medium)">
<style>
<!--
 /* Font Definitions */
 @font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
 /* 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">Yet another layer violation problem, and yet another reason =
for preferring a pure-MLPS encap.<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">If we are talking about an Ethernet PW, there is no NSP defi=
ned for intermediate LSRs,<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">(even if we think of a PW with TC as a sequence of S-PEs the=
re is no NSP there)<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;
color:#1F497D">and so technically no way to do any Ethernet level processin=
g.<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> Sunday, January 23, 2011 17:47<br>
<b>To:</b> Tal Mizrahi<br>
<b>Cc:</b> tictoc@ietf.org<br>
<b>Subject:</b> Re: [TICTOC] 1588 over PW - MAC SA Modification<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 Tal,<br>
<br>
In my opinion since the LSR is not an 802.1 bridge it doesn't need to chang=
e source MAC addresses while performing TC functions.<br>
<br>
Best,<br>
Ron<o:p></o:p></p>
<div>
<p class=3D"MsoNormal">On Sun, Jan 23, 2011 at 9:07 AM, Tal Mizrahi &lt;<a =
href=3D"mailto:talmi@marvell.com">talmi@marvell.com</a>&gt; wrote:<o:p></o:=
p></p>
<div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:10.0pt;font-family:&quot;Arial&quot;,&quo=
t;sans-serif&quot;">Hi Manav et al,</span><o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:10.0pt;font-family:&quot;Arial&quot;,&quo=
t;sans-serif&quot;">&nbsp;</span><o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:10.0pt;font-family:&quot;Arial&quot;,&quo=
t;sans-serif&quot;">When using 1588-over-Ethernet, each TC that modifies th=
e CF also updates the Ethernet MAC SA to the address of the
 TC. This is because an 802.1 bridge that modifies a packet must update its=
 source address to the bridge&#8217;s address.</span><o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:10.0pt;font-family:&quot;Arial&quot;,&quo=
t;sans-serif&quot;">&nbsp;</span><o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:10.0pt;font-family:&quot;Arial&quot;,&quo=
t;sans-serif&quot;">In draft-davari-tictoc-1588overmpls-01, when using 1588=
-over-PW, the LSR TCs update the CF in the passenger Ethernet
 packet. I am wondering whether the MAC SA of the passenger Ethernet packet=
 must be updated in this case.</span><o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:10.0pt;font-family:&quot;Arial&quot;,&quo=
t;sans-serif&quot;">This issue applies also to 1588-over-IP-over-Ethernet-o=
ver-PW.</span><o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:10.0pt;font-family:&quot;Arial&quot;,&quo=
t;sans-serif&quot;">&nbsp;</span><o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:10.0pt;font-family:&quot;Arial&quot;,&quo=
t;sans-serif&quot;">Regards,</span><o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:10.0pt;font-family:&quot;Arial&quot;,&quo=
t;sans-serif&quot;">Tal. &nbsp;</span><o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">&nbsp;<o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">&nbsp;<o:p></o:p></p>
</div>
</div>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt"><br>
_______________________________________________<br>
TICTOC mailing list<br>
<a href=3D"mailto:TICTOC@ietf.org">TICTOC@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/tictoc" target=3D"_blank">=
https://www.ietf.org/mailman/listinfo/tictoc</a><o:p></o:p></p>
</div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
</div>
</body>
</html>

--_000_07F7D7DED63154409F13298786A2ADC903CD8C2AEXRAD5adradcoil_--

From Internet-Drafts@ietf.org  Wed Jan 26 08:00:03 2011
Return-Path: <Internet-Drafts@ietf.org>
X-Original-To: tictoc@core3.amsl.com
Delivered-To: tictoc@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id D93633A67A1; Wed, 26 Jan 2011 08:00:02 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.488
X-Spam-Level: 
X-Spam-Status: No, score=-102.488 tagged_above=-999 required=5 tests=[AWL=0.111, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id sMo+zNvNKswj; Wed, 26 Jan 2011 08:00:01 -0800 (PST)
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id D2A343A6784; Wed, 26 Jan 2011 08:00:01 -0800 (PST)
MIME-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
From: Internet-Drafts@ietf.org
To: i-d-announce@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 3.10
Message-ID: <20110126160001.24022.38892.idtracker@localhost>
Date: Wed, 26 Jan 2011 08:00:01 -0800
Cc: tictoc@ietf.org
Subject: [TICTOC] I-D Action:draft-ietf-tictoc-1588overmpls-00.txt
X-BeenThere: tictoc@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Timing over IP Connection and Transfer of Clock BOF <tictoc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/tictoc>, <mailto:tictoc-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tictoc>
List-Post: <mailto:tictoc@ietf.org>
List-Help: <mailto:tictoc-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tictoc>, <mailto:tictoc-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 26 Jan 2011 16:00:03 -0000

--NextPart

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


	Title           : Transporting PTP messages (1588) over MPLS Networks
	Author(s)       : S. Davari, et al.
	Filename        : draft-ietf-tictoc-1588overmpls-00.txt
	Pages           : 35
	Date            : 2011-01-26

This document defines the method for transporting PTP messages (PDUs)
over an MPLS network to enable a proper handling of these packets
(e.g. implementation of Transparent Clocks (TC)) in LSRs.

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

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

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

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

Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.

--NextPart
Content-Type: Message/External-body;
	name="draft-ietf-tictoc-1588overmpls-00.txt";
	site="ftp.ietf.org"; access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID: <2011-01-26075534.I-D@ietf.org>


--NextPart--

From manav.bhatia@alcatel-lucent.com  Wed Jan 26 08:18:10 2011
Return-Path: <manav.bhatia@alcatel-lucent.com>
X-Original-To: tictoc@core3.amsl.com
Delivered-To: tictoc@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 6A2273A67E5 for <tictoc@core3.amsl.com>; Wed, 26 Jan 2011 08:18:10 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.243
X-Spam-Level: 
X-Spam-Status: No, score=-6.243 tagged_above=-999 required=5 tests=[AWL=0.356,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id JZ1qDDT8ynd7 for <tictoc@core3.amsl.com>; Wed, 26 Jan 2011 08:18:09 -0800 (PST)
Received: from ihemail4.lucent.com (ihemail4.lucent.com [135.245.0.39]) by core3.amsl.com (Postfix) with ESMTP id 57DC33A67CC for <tictoc@ietf.org>; Wed, 26 Jan 2011 08:18:09 -0800 (PST)
Received: from inbansmailrelay2.in.alcatel-lucent.com (h135-250-11-33.lucent.com [135.250.11.33]) by ihemail4.lucent.com (8.13.8/IER-o) with ESMTP id p0QGL3E1020419 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL) for <tictoc@ietf.org>; Wed, 26 Jan 2011 10:21:06 -0600 (CST)
Received: from INBANSXCHHUB03.in.alcatel-lucent.com (inbansxchhub03.in.alcatel-lucent.com [135.250.12.80]) by inbansmailrelay2.in.alcatel-lucent.com (8.14.3/8.14.3/GMO) with ESMTP id p0QGL1K0010811 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT) for <tictoc@ietf.org>; Wed, 26 Jan 2011 21:51:02 +0530
Received: from INBANSXCHMBSA1.in.alcatel-lucent.com ([135.250.12.56]) by INBANSXCHHUB03.in.alcatel-lucent.com ([135.250.12.80]) with mapi; Wed, 26 Jan 2011 21:51:01 +0530
From: "Bhatia, Manav (Manav)" <manav.bhatia@alcatel-lucent.com>
To: "tictoc@ietf.org" <tictoc@ietf.org>
Date: Wed, 26 Jan 2011 21:50:58 +0530
Thread-Topic: draft-ietf-tictoc-1588overmpls-00.txt
Thread-Index: Acu9coxc/9UfybtDQZKjfH/8vLRwSgAAJIwA
Message-ID: <7C362EEF9C7896468B36C9B79200D8350CFB18B515@INBANSXCHMBSA1.in.alcatel-lucent.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: multipart/mixed; boundary="_002_7C362EEF9C7896468B36C9B79200D8350CFB18B515INBANSXCHMBSA_"
MIME-Version: 1.0
X-Scanned-By: MIMEDefang 2.57 on 135.245.2.39
X-Scanned-By: MIMEDefang 2.64 on 135.250.11.33
Subject: [TICTOC] draft-ietf-tictoc-1588overmpls-00.txt
X-BeenThere: tictoc@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Timing over IP Connection and Transfer of Clock BOF <tictoc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/tictoc>, <mailto:tictoc-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tictoc>
List-Post: <mailto:tictoc@ietf.org>
List-Help: <mailto:tictoc-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tictoc>, <mailto:tictoc-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 26 Jan 2011 16:18:10 -0000

--_002_7C362EEF9C7896468B36C9B79200D8350CFB18B515INBANSXCHMBSA_
Content-Type: text/plain; name="warning1.txt"
Content-Disposition: inline; filename="warning1.txt"
Content-Transfer-Encoding: 7bit
MIME-Version: 1.0
X-Mailer: MIME-tools 5.427 (Entity 5.427)

WARNING: This e-mail has been altered by some SMTP protection software.  Following this
paragraph are indications of the actual changes made.  For more information, contact
Alcatel-Lucent Postmaster <postmaster@alcatel-lucent.com>.

An attachment of type message/external-body, named draft-ietf-tictoc-1588overmpls-00.url was removed from this message as it
constituted a security hazard.  If you require this document, please contact
the sender and arrange an alternate means of receiving it.


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

Hi,

We've tried incorporating most of the comments that we received on the list=
. Please ping me if you think we have missed some.

Would be great if the WG can go through this and provide feedback on the sa=
me.

The draft is available here:
http://www.ietf.org/internet-drafts/draft-ietf-tictoc-1588overmpls-00.txt

Cheers, Manav

> -----Original Message-----
> From: tictoc-bounces@ietf.org=20
> [mailto:tictoc-bounces@ietf.org] On Behalf Of Internet-Drafts@ietf.org
> Sent: Wednesday, January 26, 2011 9.30 PM
> To: i-d-announce@ietf.org
> Cc: tictoc@ietf.org
> Subject: [TICTOC] I-D Action:draft-ietf-tictoc-1588overmpls-00.txt
>=20
> A New Internet-Draft is available from the on-line=20
> Internet-Drafts directories.
> This draft is a work item of the Timing over IP Connection=20
> and Transfer of Clock Working Group of the IETF.
>=20
>=20
> 	Title           : Transporting PTP messages (1588) over=20
> MPLS Networks
> 	Author(s)       : S. Davari, et al.
> 	Filename        : draft-ietf-tictoc-1588overmpls-00.txt
> 	Pages           : 35
> 	Date            : 2011-01-26
>=20
> This document defines the method for transporting PTP messages (PDUs)
> over an MPLS network to enable a proper handling of these packets
> (e.g. implementation of Transparent Clocks (TC)) in LSRs.
>=20
> The basic idea is to transport PTP messages inside dedicated MPLS
> LSPs.  These LSPs only carry PTP messages and possibly Control and
> Management packets, but they do not carry customer traffic.
>=20
> Two methods for transporting 1588 over MPLS are defined.  The first
> method is to transport PTP messages directly over the dedicated MPLS
> LSP via UDP/IP encapsulation, which is suitable for IP/MPLS networks.
> The second method is to transport PTP messages inside a PW via
> Ethernet encapsulation, which is more suitable for MPLS-TP networks.
>=20
> A URL for this Internet-Draft is:
> http://www.ietf.org/internet-drafts/draft-ietf-tictoc-1588over
> mpls-00.txt
>=20
> Internet-Drafts are also available by anonymous FTP at:
> ftp://ftp.ietf.org/internet-drafts/
>=20
> Below is the data which will enable a MIME compliant mail reader
> implementation to automatically retrieve the ASCII version of the
> Internet-Draft.
>=20=

--_002_7C362EEF9C7896468B36C9B79200D8350CFB18B515INBANSXCHMBSA_--

From manav.bhatia@alcatel-lucent.com  Wed Jan 26 08:19:45 2011
Return-Path: <manav.bhatia@alcatel-lucent.com>
X-Original-To: tictoc@core3.amsl.com
Delivered-To: tictoc@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 407E03A67D6 for <tictoc@core3.amsl.com>; Wed, 26 Jan 2011 08:19:45 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.249
X-Spam-Level: 
X-Spam-Status: No, score=-6.249 tagged_above=-999 required=5 tests=[AWL=0.350,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id VtuAgCVlBgSm for <tictoc@core3.amsl.com>; Wed, 26 Jan 2011 08:19:44 -0800 (PST)
Received: from ihemail3.lucent.com (ihemail3.lucent.com [135.245.0.37]) by core3.amsl.com (Postfix) with ESMTP id 45C2D3A67D2 for <tictoc@ietf.org>; Wed, 26 Jan 2011 08:19:44 -0800 (PST)
Received: from inbansmailrelay1.in.alcatel-lucent.com (h135-250-11-31.lucent.com [135.250.11.31]) by ihemail3.lucent.com (8.13.8/IER-o) with ESMTP id p0QGMe6T029372 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL) for <tictoc@ietf.org>; Wed, 26 Jan 2011 10:22:44 -0600 (CST)
Received: from INBANSXCHHUB02.in.alcatel-lucent.com (inbansxchhub02.in.alcatel-lucent.com [135.250.12.35]) by inbansmailrelay1.in.alcatel-lucent.com (8.14.3/8.14.3/GMO) with ESMTP id p0QGMdRC003740 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT) for <tictoc@ietf.org>; Wed, 26 Jan 2011 21:52:40 +0530
Received: from INBANSXCHMBSA1.in.alcatel-lucent.com ([135.250.12.56]) by INBANSXCHHUB02.in.alcatel-lucent.com ([135.250.12.35]) with mapi; Wed, 26 Jan 2011 21:52:39 +0530
From: "Bhatia, Manav (Manav)" <manav.bhatia@alcatel-lucent.com>
To: "tictoc@ietf.org" <tictoc@ietf.org>
Date: Wed, 26 Jan 2011 21:52:38 +0530
Thread-Topic: draft-ietf-tictoc-1588overmpls-00.txt
Thread-Index: Acu9dT9PcmArb8UPQoKPAFsSH0yDlg==
Message-ID: <7C362EEF9C7896468B36C9B79200D8350CFB18B516@INBANSXCHMBSA1.in.alcatel-lucent.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Scanned-By: MIMEDefang 2.57 on 135.245.2.37
X-Scanned-By: MIMEDefang 2.64 on 135.250.11.31
Subject: [TICTOC] draft-ietf-tictoc-1588overmpls-00.txt
X-BeenThere: tictoc@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Timing over IP Connection and Transfer of Clock BOF <tictoc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/tictoc>, <mailto:tictoc-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tictoc>
List-Post: <mailto:tictoc@ietf.org>
List-Help: <mailto:tictoc-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tictoc>, <mailto:tictoc-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 26 Jan 2011 16:19:45 -0000

Hi,

We've tried incorporating most of the comments that we received on the list=
. Please ping me if you think we have missed some.

Would be great if the WG can go through this and provide feedback on the sa=
me.

The draft is available here:
http://www.ietf.org/internet-drafts/draft-ietf-tictoc-1588overmpls-00.txt

Cheers, Manav

> -----Original Message-----
> From: tictoc-bounces@ietf.org=20
> [mailto:tictoc-bounces@ietf.org] On Behalf Of Internet-Drafts@ietf.org
> Sent: Wednesday, January 26, 2011 9.30 PM
> To: i-d-announce@ietf.org
> Cc: tictoc@ietf.org
> Subject: [TICTOC] I-D Action:draft-ietf-tictoc-1588overmpls-00.txt
>=20
> A New Internet-Draft is available from the on-line=20
> Internet-Drafts directories.
> This draft is a work item of the Timing over IP Connection=20
> and Transfer of Clock Working Group of the IETF.
>=20
>=20
> 	Title           : Transporting PTP messages (1588) over=20
> MPLS Networks
> 	Author(s)       : S. Davari, et al.
> 	Filename        : draft-ietf-tictoc-1588overmpls-00.txt
> 	Pages           : 35
> 	Date            : 2011-01-26
>=20
> This document defines the method for transporting PTP messages (PDUs)
> over an MPLS network to enable a proper handling of these packets
> (e.g. implementation of Transparent Clocks (TC)) in LSRs.
>=20

Cheers, Manav

--
Manav Bhatia,
IP Division, Alcatel-Lucent,
Bangalore - India

 =

From talmi@marvell.com  Wed Jan 26 08:32:09 2011
Return-Path: <talmi@marvell.com>
X-Original-To: tictoc@core3.amsl.com
Delivered-To: tictoc@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 57EAB3A67AD for <tictoc@core3.amsl.com>; Wed, 26 Jan 2011 08:32:09 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.049
X-Spam-Level: 
X-Spam-Status: No, score=-6.049 tagged_above=-999 required=5 tests=[AWL=0.550,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id DH3k1+vFsZeQ for <tictoc@core3.amsl.com>; Wed, 26 Jan 2011 08:32:08 -0800 (PST)
Received: from na3sys009aog111.obsmtp.com (na3sys009aog111.obsmtp.com [74.125.149.205]) by core3.amsl.com (Postfix) with SMTP id DF4463A67A4 for <tictoc@ietf.org>; Wed, 26 Jan 2011 08:32:07 -0800 (PST)
Received: from source ([65.219.4.130]) (using TLSv1) by na3sys009aob111.postini.com ([74.125.148.12]) with SMTP ID DSNKTUBNPBQ3ggzftvOlTW6BWG0G0EIap/1Z@postini.com; Wed, 26 Jan 2011 08:35:09 PST
Received: from YK-HUB02.marvell.com (10.4.102.52) by sc-owa02.marvell.com (10.93.76.22) with Microsoft SMTP Server (TLS) id 8.2.213.0; Wed, 26 Jan 2011 08:33:34 -0800
Received: from IL-MB01.marvell.com ([10.4.102.53]) by YK-HUB02.marvell.com ([10.4.102.52]) with mapi; Wed, 26 Jan 2011 18:33:32 +0200
From: Tal Mizrahi <talmi@marvell.com>
To: "Bhatia, Manav (Manav)" <manav.bhatia@alcatel-lucent.com>, "tictoc@ietf.org" <tictoc@ietf.org>
Date: Wed, 26 Jan 2011 18:33:28 +0200
Thread-Topic: draft-ietf-tictoc-1588overmpls-00.txt
Thread-Index: Acu9dT9PcmArb8UPQoKPAFsSH0yDlgAAWvEQ
Message-ID: <74470498B659FA4687F0B0018C19A89CFCDC14719A@IL-MB01.marvell.com>
References: <7C362EEF9C7896468B36C9B79200D8350CFB18B516@INBANSXCHMBSA1.in.alcatel-lucent.com>
In-Reply-To: <7C362EEF9C7896468B36C9B79200D8350CFB18B516@INBANSXCHMBSA1.in.alcatel-lucent.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: Re: [TICTOC] draft-ietf-tictoc-1588overmpls-00.txt
X-BeenThere: tictoc@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Timing over IP Connection and Transfer of Clock BOF <tictoc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/tictoc>, <mailto:tictoc-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tictoc>
List-Post: <mailto:tictoc@ietf.org>
List-Help: <mailto:tictoc-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tictoc>, <mailto:tictoc-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 26 Jan 2011 16:32:09 -0000

Hi Manav,

I think you must have missed the comments I sent on Jan 18th, as none of th=
em was addressed. Please let me know if you disagree with some of them.

Thanks.
Tal.

-----Original Message-----
From: tictoc-bounces@ietf.org [mailto:tictoc-bounces@ietf.org] On Behalf Of=
 Bhatia, Manav (Manav)
Sent: Wednesday, January 26, 2011 6:23 PM
To: tictoc@ietf.org
Subject: [TICTOC] draft-ietf-tictoc-1588overmpls-00.txt

Hi,

We've tried incorporating most of the comments that we received on the list=
. Please ping me if you think we have missed some.

Would be great if the WG can go through this and provide feedback on the sa=
me.

The draft is available here:
http://www.ietf.org/internet-drafts/draft-ietf-tictoc-1588overmpls-00.txt

Cheers, Manav

> -----Original Message-----
> From: tictoc-bounces@ietf.org=20
> [mailto:tictoc-bounces@ietf.org] On Behalf Of Internet-Drafts@ietf.org
> Sent: Wednesday, January 26, 2011 9.30 PM
> To: i-d-announce@ietf.org
> Cc: tictoc@ietf.org
> Subject: [TICTOC] I-D Action:draft-ietf-tictoc-1588overmpls-00.txt
>=20
> A New Internet-Draft is available from the on-line=20
> Internet-Drafts directories.
> This draft is a work item of the Timing over IP Connection=20
> and Transfer of Clock Working Group of the IETF.
>=20
>=20
> 	Title           : Transporting PTP messages (1588) over=20
> MPLS Networks
> 	Author(s)       : S. Davari, et al.
> 	Filename        : draft-ietf-tictoc-1588overmpls-00.txt
> 	Pages           : 35
> 	Date            : 2011-01-26
>=20
> This document defines the method for transporting PTP messages (PDUs)
> over an MPLS network to enable a proper handling of these packets
> (e.g. implementation of Transparent Clocks (TC)) in LSRs.
>=20

Cheers, Manav

--
Manav Bhatia,
IP Division, Alcatel-Lucent,
Bangalore - India

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

From davari@broadcom.com  Wed Jan 26 08:45:53 2011
Return-Path: <davari@broadcom.com>
X-Original-To: tictoc@core3.amsl.com
Delivered-To: tictoc@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 0F90A3A6905 for <tictoc@core3.amsl.com>; Wed, 26 Jan 2011 08:45:53 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.634
X-Spam-Level: 
X-Spam-Status: No, score=-1.634 tagged_above=-999 required=5 tests=[AWL=0.965,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Gi2PrEhk8190 for <tictoc@core3.amsl.com>; Wed, 26 Jan 2011 08:45:52 -0800 (PST)
Received: from MMS3.broadcom.com (mms3.broadcom.com [216.31.210.19]) by core3.amsl.com (Postfix) with ESMTP id DBA503A68E6 for <tictoc@ietf.org>; Wed, 26 Jan 2011 08:45:51 -0800 (PST)
Received: from [10.16.192.232] by MMS3.broadcom.com with ESMTP (Broadcom SMTP Relay (Email Firewall v6.3.2)); Wed, 26 Jan 2011 08:50:10 -0800
X-Server-Uuid: B55A25B1-5D7D-41F8-BC53-C57E7AD3C201
Received: from SJEXCHCCR02.corp.ad.broadcom.com ([10.16.192.130]) by SJEXCHHUB02.corp.ad.broadcom.com ([10.16.192.232]) with mapi; Wed, 26 Jan 2011 08:48:41 -0800
From: "Shahram Davari" <davari@broadcom.com>
To: "Tal Mizrahi" <talmi@marvell.com>, "Bhatia, Manav (Manav)" <manav.bhatia@alcatel-lucent.com>, "tictoc@ietf.org" <tictoc@ietf.org>
Date: Wed, 26 Jan 2011 08:48:39 -0800
Thread-Topic: Transporting PTP messages (1588) over MPLS Networks
Thread-Index: Acu0ostDa6CYok1lRYSvUt8QtgvK+QCdFs+gAZgKujA=
Message-ID: <2C2F1EBA8050E74EA81502D5740B4BD6941B2F8A0A@SJEXCHCCR02.corp.ad.broadcom.com>
References: <7C362EEF9C7896468B36C9B79200D8350CFB0DF1AE@INBANSXCHMBSA1.in.alcatel-lucent.com> <74470498B659FA4687F0B0018C19A89CFCDC0EB8AA@IL-MB01.marvell.com>
In-Reply-To: <74470498B659FA4687F0B0018C19A89CFCDC0EB8AA@IL-MB01.marvell.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
MIME-Version: 1.0
X-WSS-ID: 615E8F481VG12794668-01-01
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Subject: Re: [TICTOC] Transporting PTP messages (1588) over MPLS Networks
X-BeenThere: tictoc@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Timing over IP Connection and Transfer of Clock BOF <tictoc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/tictoc>, <mailto:tictoc-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tictoc>
List-Post: <mailto:tictoc@ietf.org>
List-Help: <mailto:tictoc-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tictoc>, <mailto:tictoc-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 26 Jan 2011 16:45:53 -0000

Hi Tal,

Please find my comments inline.

-----Original Message-----
From: tictoc-bounces@ietf.org [mailto:tictoc-bounces@ietf.org] On Behalf Of=
 Tal Mizrahi
Sent: Tuesday, January 18, 2011 6:04 AM
To: Bhatia, Manav (Manav); tictoc@ietf.org
Subject: Re: [TICTOC] Transporting PTP messages (1588) over MPLS Networks

Hi Manav,

A few comments below.

Section 3. Problem Statement says that "The defined method is applicable to=
 both MPLS and MPLS-TP networks."
- however, Section 9. OAM, Control and Management does not mention MPLS-TP =
OAM. Furthermore, section 5.1. 1588 over LSP Encapsulation shows an encapsu=
lation with a single label, and does not show that an optional GAL is possi=
ble.

SD> We could add the MPLS-TP OAM to the text. Regarding GAL, this is explic=
itly not allowed to be in the stack when the encapsulated data is PTP messa=
ge. So GAL is not optional.

6.  1588 Message Transport
"If Two Step Transparent clocks are present, then the FOLLOW_UP and DELAY_R=
ESP messages must also be transported over the PTP LSPs."=20
- for P2P TCs you also need the PDelay_Resp_Follow_Up.

SD> AFAIK These messages don't require time stamping and therefore don't ha=
ve to be transported over PTP LSP.

10.  QoS Considerations
- I am not sure I understand why this is a MUST. This draft defines an enca=
psulation, while the QoS requirements are typically be derived from the app=
lication, which is defined elsewhere.

SD> The application is PTP, which requires low delay. Are you suggesting we=
 make it a should?=20

11.  FCS Recalculation
"FCS retention described in [RFC4720] MUST not be used"=20
- that makes sense, but seems to contradict the first half of the sentence =
"Ethernet FCS MUST be recalculated at every LSR". In my understanding if re=
tention is not used, only the LERs have to recompute the FCS. LSRs may alte=
r the CF, but do not need to bother with the FCS.

SD> I think your understanding is not correct.=20

Tal.

-----Original Message-----
From: tictoc-bounces@ietf.org [mailto:tictoc-bounces@ietf.org] On Behalf Of=
 Bhatia, Manav (Manav)
Sent: Saturday, January 15, 2011 12:56 PM
To: tictoc@ietf.org
Subject: [TICTOC] Transporting PTP messages (1588) over MPLS Networks

Hi,

We have posted a revised version of draft-davari-tictoc-1588overmpls-01 and=
 would appreciate a feedback from the WG.

The draft is available here:
http://www.ietf.org/id/draft-davari-tictoc-1588overmpls-01.txt

Cheers, Manav

--
Manav Bhatia,
IP Division, Alcatel-Lucent,
Bangalore - India

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



From manav.bhatia@alcatel-lucent.com  Wed Jan 26 08:51:27 2011
Return-Path: <manav.bhatia@alcatel-lucent.com>
X-Original-To: tictoc@core3.amsl.com
Delivered-To: tictoc@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 410673A69C5 for <tictoc@core3.amsl.com>; Wed, 26 Jan 2011 08:51:27 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.256
X-Spam-Level: 
X-Spam-Status: No, score=-6.256 tagged_above=-999 required=5 tests=[AWL=0.343,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id hn1yPiyZ--lV for <tictoc@core3.amsl.com>; Wed, 26 Jan 2011 08:51:26 -0800 (PST)
Received: from ihemail3.lucent.com (ihemail3.lucent.com [135.245.0.37]) by core3.amsl.com (Postfix) with ESMTP id 1FBDE3A67D6 for <tictoc@ietf.org>; Wed, 26 Jan 2011 08:51:26 -0800 (PST)
Received: from inbansmailrelay1.in.alcatel-lucent.com (h135-250-11-31.lucent.com [135.250.11.31]) by ihemail3.lucent.com (8.13.8/IER-o) with ESMTP id p0QGsM1W017080 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Wed, 26 Jan 2011 10:54:25 -0600 (CST)
Received: from INBANSXCHHUB02.in.alcatel-lucent.com (inbansxchhub02.in.alcatel-lucent.com [135.250.12.35]) by inbansmailrelay1.in.alcatel-lucent.com (8.14.3/8.14.3/GMO) with ESMTP id p0QGsKkA004736 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Wed, 26 Jan 2011 22:24:21 +0530
Received: from INBANSXCHMBSA1.in.alcatel-lucent.com ([135.250.12.56]) by INBANSXCHHUB02.in.alcatel-lucent.com ([135.250.12.35]) with mapi; Wed, 26 Jan 2011 22:24:20 +0530
From: "Bhatia, Manav (Manav)" <manav.bhatia@alcatel-lucent.com>
To: Shahram Davari <davari@broadcom.com>, Tal Mizrahi <talmi@marvell.com>, "tictoc@ietf.org" <tictoc@ietf.org>
Date: Wed, 26 Jan 2011 22:24:18 +0530
Thread-Topic: Transporting PTP messages (1588) over MPLS Networks
Thread-Index: Acu0ostDa6CYok1lRYSvUt8QtgvK+QCdFs+gAZgKujAAAHn1AA==
Message-ID: <7C362EEF9C7896468B36C9B79200D8350CFB18B518@INBANSXCHMBSA1.in.alcatel-lucent.com>
References: <7C362EEF9C7896468B36C9B79200D8350CFB0DF1AE@INBANSXCHMBSA1.in.alcatel-lucent.com> <74470498B659FA4687F0B0018C19A89CFCDC0EB8AA@IL-MB01.marvell.com> <2C2F1EBA8050E74EA81502D5740B4BD6941B2F8A0A@SJEXCHCCR02.corp.ad.broadcom.com>
In-Reply-To: <2C2F1EBA8050E74EA81502D5740B4BD6941B2F8A0A@SJEXCHCCR02.corp.ad.broadcom.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Scanned-By: MIMEDefang 2.57 on 135.245.2.37
X-Scanned-By: MIMEDefang 2.64 on 135.250.11.31
Subject: Re: [TICTOC] Transporting PTP messages (1588) over MPLS Networks
X-BeenThere: tictoc@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Timing over IP Connection and Transfer of Clock BOF <tictoc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/tictoc>, <mailto:tictoc-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tictoc>
List-Post: <mailto:tictoc@ietf.org>
List-Help: <mailto:tictoc-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tictoc>, <mailto:tictoc-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 26 Jan 2011 16:51:27 -0000

Hi Tal,

In addition to what Shahram has said:

> 6.  1588 Message Transport
> "If Two Step Transparent clocks are present, then the=20
> FOLLOW_UP and DELAY_RESP messages must also be transported=20
> over the PTP LSPs."=20
> - for P2P TCs you also need the PDelay_Resp_Follow_Up.
>=20
> SD> AFAIK These messages don't require time stamping and=20
> therefore don't have to be transported over PTP LSP.

The PDelay_Resp_Follow_Up message will never go through a TC and will never=
 have its CF modified.  In the case of a non-TC PTP LSR, it is only the PDe=
lay_Req and PDelay-Resp message that are time sensitive.  So the PDelay_Res=
p_Follow_Up can be sent outside of the PTP LSP.

>=20
> 10.  QoS Considerations
> - I am not sure I understand why this is a MUST. This draft=20
> defines an encapsulation, while the QoS requirements are=20
> typically be derived from the application, which is defined elsewhere.
>=20
> SD> The application is PTP, which requires low delay. Are you=20
> suggesting we make it a should?=20

The current text does not use a MUST. Does that look ok?

Cheers, Manav=

From talmi@marvell.com  Wed Jan 26 09:10:13 2011
Return-Path: <talmi@marvell.com>
X-Original-To: tictoc@core3.amsl.com
Delivered-To: tictoc@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 18DC23A684A for <tictoc@core3.amsl.com>; Wed, 26 Jan 2011 09:10:13 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.187
X-Spam-Level: 
X-Spam-Status: No, score=-6.187 tagged_above=-999 required=5 tests=[AWL=0.413,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id fNm7XFPNie6F for <tictoc@core3.amsl.com>; Wed, 26 Jan 2011 09:10:12 -0800 (PST)
Received: from na3sys009aog101.obsmtp.com (na3sys009aog101.obsmtp.com [74.125.149.67]) by core3.amsl.com (Postfix) with SMTP id 235823A6824 for <tictoc@ietf.org>; Wed, 26 Jan 2011 09:10:11 -0800 (PST)
Received: from source ([65.219.4.129]) (using TLSv1) by na3sys009aob101.postini.com ([74.125.148.12]) with SMTP ID DSNKTUBWKDVgA0rWBTC36p7qMHy9nYcuNJZl@postini.com; Wed, 26 Jan 2011 09:13:13 PST
Received: from YK-HUB02.marvell.com (10.4.102.52) by sc-owa01.marvell.com (10.93.76.21) with Microsoft SMTP Server (TLS) id 8.2.213.0; Wed, 26 Jan 2011 09:13:08 -0800
Received: from IL-MB01.marvell.com ([10.4.102.53]) by YK-HUB02.marvell.com ([10.4.102.52]) with mapi; Wed, 26 Jan 2011 19:13:05 +0200
From: Tal Mizrahi <talmi@marvell.com>
To: "Bhatia, Manav (Manav)" <manav.bhatia@alcatel-lucent.com>, Shahram Davari <davari@broadcom.com>, "tictoc@ietf.org" <tictoc@ietf.org>
Date: Wed, 26 Jan 2011 19:13:06 +0200
Thread-Topic: Transporting PTP messages (1588) over MPLS Networks
Thread-Index: Acu0ostDa6CYok1lRYSvUt8QtgvK+QCdFs+gAZgKujAAAHn1AAAAlHjQ
Message-ID: <74470498B659FA4687F0B0018C19A89CFCDC1471A1@IL-MB01.marvell.com>
References: <7C362EEF9C7896468B36C9B79200D8350CFB0DF1AE@INBANSXCHMBSA1.in.alcatel-lucent.com> <74470498B659FA4687F0B0018C19A89CFCDC0EB8AA@IL-MB01.marvell.com> <2C2F1EBA8050E74EA81502D5740B4BD6941B2F8A0A@SJEXCHCCR02.corp.ad.broadcom.com> <7C362EEF9C7896468B36C9B79200D8350CFB18B518@INBANSXCHMBSA1.in.alcatel-lucent.com>
In-Reply-To: <7C362EEF9C7896468B36C9B79200D8350CFB18B518@INBANSXCHMBSA1.in.alcatel-lucent.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: Re: [TICTOC] Transporting PTP messages (1588) over MPLS Networks
X-BeenThere: tictoc@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Timing over IP Connection and Transfer of Clock BOF <tictoc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/tictoc>, <mailto:tictoc-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tictoc>
List-Post: <mailto:tictoc@ietf.org>
List-Help: <mailto:tictoc-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tictoc>, <mailto:tictoc-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 26 Jan 2011 17:10:13 -0000

Hi Manav, Shahram,

>=20
> 10.  QoS Considerations
> - I am not sure I understand why this is a MUST. This draft=20
> defines an encapsulation, while the QoS requirements are=20
> typically be derived from the application, which is defined elsewhere.
>=20
> SD> The application is PTP, which requires low delay. Are you=20
> suggesting we make it a should?=20
>
>The current text does not use a MUST. Does that look ok?

The current wording is "The PTP messages are time critical and must be trea=
ted with the highest priority.",=20
while the IEEE 1588 states in the informative Annex A that "PTP event messa=
ges should be sent with high priority compared with other data whenever pos=
sible."
Of course it makes sense that PTP is high priority, but the current wording=
 seems a bit too stringent.

Thanks.=20
Tal.

-----Original Message-----
From: Bhatia, Manav (Manav) [mailto:manav.bhatia@alcatel-lucent.com]=20
Sent: Wednesday, January 26, 2011 6:54 PM
To: Shahram Davari; Tal Mizrahi; tictoc@ietf.org
Subject: RE: Transporting PTP messages (1588) over MPLS Networks

Hi Tal,

In addition to what Shahram has said:

> 6.  1588 Message Transport
> "If Two Step Transparent clocks are present, then the=20
> FOLLOW_UP and DELAY_RESP messages must also be transported=20
> over the PTP LSPs."=20
> - for P2P TCs you also need the PDelay_Resp_Follow_Up.
>=20
> SD> AFAIK These messages don't require time stamping and=20
> therefore don't have to be transported over PTP LSP.

The PDelay_Resp_Follow_Up message will never go through a TC and will never=
 have its CF modified.  In the case of a non-TC PTP LSR, it is only the PDe=
lay_Req and PDelay-Resp message that are time sensitive.  So the PDelay_Res=
p_Follow_Up can be sent outside of the PTP LSP.

>=20
> 10.  QoS Considerations
> - I am not sure I understand why this is a MUST. This draft=20
> defines an encapsulation, while the QoS requirements are=20
> typically be derived from the application, which is defined elsewhere.
>=20
> SD> The application is PTP, which requires low delay. Are you=20
> suggesting we make it a should?=20

The current text does not use a MUST. Does that look ok?

Cheers, Manav

From davari@broadcom.com  Wed Jan 26 09:13:06 2011
Return-Path: <davari@broadcom.com>
X-Original-To: tictoc@core3.amsl.com
Delivered-To: tictoc@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id A26783A6824 for <tictoc@core3.amsl.com>; Wed, 26 Jan 2011 09:13:06 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.795
X-Spam-Level: 
X-Spam-Status: No, score=-1.795 tagged_above=-999 required=5 tests=[AWL=0.804,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id FOZgFwf3+i5u for <tictoc@core3.amsl.com>; Wed, 26 Jan 2011 09:13:05 -0800 (PST)
Received: from MMS3.broadcom.com (mms3.broadcom.com [216.31.210.19]) by core3.amsl.com (Postfix) with ESMTP id C14DA3A681A for <tictoc@ietf.org>; Wed, 26 Jan 2011 09:13:05 -0800 (PST)
Received: from [10.16.192.224] by MMS3.broadcom.com with ESMTP (Broadcom SMTP Relay (Email Firewall v6.3.2)); Wed, 26 Jan 2011 09:17:22 -0800
X-Server-Uuid: B55A25B1-5D7D-41F8-BC53-C57E7AD3C201
Received: from SJEXCHCCR02.corp.ad.broadcom.com ([10.16.192.130]) by SJEXCHHUB01.corp.ad.broadcom.com ([10.16.192.224]) with mapi; Wed, 26 Jan 2011 09:15:52 -0800
From: "Shahram Davari" <davari@broadcom.com>
To: "Tal Mizrahi" <talmi@marvell.com>, "Bhatia, Manav (Manav)" <manav.bhatia@alcatel-lucent.com>, "tictoc@ietf.org" <tictoc@ietf.org>
Date: Wed, 26 Jan 2011 09:15:51 -0800
Thread-Topic: Transporting PTP messages (1588) over MPLS Networks
Thread-Index: Acu0ostDa6CYok1lRYSvUt8QtgvK+QCdFs+gAZgKujAAAHn1AAAAlHjQAAA4rNA=
Message-ID: <2C2F1EBA8050E74EA81502D5740B4BD6941B2F8A43@SJEXCHCCR02.corp.ad.broadcom.com>
References: <7C362EEF9C7896468B36C9B79200D8350CFB0DF1AE@INBANSXCHMBSA1.in.alcatel-lucent.com> <74470498B659FA4687F0B0018C19A89CFCDC0EB8AA@IL-MB01.marvell.com> <2C2F1EBA8050E74EA81502D5740B4BD6941B2F8A0A@SJEXCHCCR02.corp.ad.broadcom.com> <7C362EEF9C7896468B36C9B79200D8350CFB18B518@INBANSXCHMBSA1.in.alcatel-lucent.com> <74470498B659FA4687F0B0018C19A89CFCDC1471A1@IL-MB01.marvell.com>
In-Reply-To: <74470498B659FA4687F0B0018C19A89CFCDC1471A1@IL-MB01.marvell.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
MIME-Version: 1.0
X-WSS-ID: 615E88A81VG12809764-01-01
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Subject: Re: [TICTOC] Transporting PTP messages (1588) over MPLS Networks
X-BeenThere: tictoc@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Timing over IP Connection and Transfer of Clock BOF <tictoc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/tictoc>, <mailto:tictoc-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tictoc>
List-Post: <mailto:tictoc@ietf.org>
List-Help: <mailto:tictoc-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tictoc>, <mailto:tictoc-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 26 Jan 2011 17:13:06 -0000

Tal,

It is lower case "must" which is not a normative requirement. It is informa=
tive.

Thx
Shahram

-----Original Message-----
From: Tal Mizrahi [mailto:talmi@marvell.com]=20
Sent: Wednesday, January 26, 2011 9:13 AM
To: Bhatia, Manav (Manav); Shahram Davari; tictoc@ietf.org
Subject: RE: Transporting PTP messages (1588) over MPLS Networks

Hi Manav, Shahram,

>=20
> 10.  QoS Considerations
> - I am not sure I understand why this is a MUST. This draft=20
> defines an encapsulation, while the QoS requirements are=20
> typically be derived from the application, which is defined elsewhere.
>=20
> SD> The application is PTP, which requires low delay. Are you=20
> suggesting we make it a should?=20
>
>The current text does not use a MUST. Does that look ok?

The current wording is "The PTP messages are time critical and must be trea=
ted with the highest priority.",=20
while the IEEE 1588 states in the informative Annex A that "PTP event messa=
ges should be sent with high priority compared with other data whenever pos=
sible."
Of course it makes sense that PTP is high priority, but the current wording=
 seems a bit too stringent.

Thanks.=20
Tal.

-----Original Message-----
From: Bhatia, Manav (Manav) [mailto:manav.bhatia@alcatel-lucent.com]=20
Sent: Wednesday, January 26, 2011 6:54 PM
To: Shahram Davari; Tal Mizrahi; tictoc@ietf.org
Subject: RE: Transporting PTP messages (1588) over MPLS Networks

Hi Tal,

In addition to what Shahram has said:

> 6.  1588 Message Transport
> "If Two Step Transparent clocks are present, then the=20
> FOLLOW_UP and DELAY_RESP messages must also be transported=20
> over the PTP LSPs."=20
> - for P2P TCs you also need the PDelay_Resp_Follow_Up.
>=20
> SD> AFAIK These messages don't require time stamping and=20
> therefore don't have to be transported over PTP LSP.

The PDelay_Resp_Follow_Up message will never go through a TC and will never=
 have its CF modified.  In the case of a non-TC PTP LSR, it is only the PDe=
lay_Req and PDelay-Resp message that are time sensitive.  So the PDelay_Res=
p_Follow_Up can be sent outside of the PTP LSP.

>=20
> 10.  QoS Considerations
> - I am not sure I understand why this is a MUST. This draft=20
> defines an encapsulation, while the QoS requirements are=20
> typically be derived from the application, which is defined elsewhere.
>=20
> SD> The application is PTP, which requires low delay. Are you=20
> suggesting we make it a should?=20

The current text does not use a MUST. Does that look ok?

Cheers, Manav



From manav.bhatia@alcatel-lucent.com  Wed Jan 26 09:18:19 2011
Return-Path: <manav.bhatia@alcatel-lucent.com>
X-Original-To: tictoc@core3.amsl.com
Delivered-To: tictoc@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 583863A681A for <tictoc@core3.amsl.com>; Wed, 26 Jan 2011 09:18:19 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.262
X-Spam-Level: 
X-Spam-Status: No, score=-6.262 tagged_above=-999 required=5 tests=[AWL=0.337,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2Q-aGc9AgVCa for <tictoc@core3.amsl.com>; Wed, 26 Jan 2011 09:18:18 -0800 (PST)
Received: from ihemail4.lucent.com (ihemail4.lucent.com [135.245.0.39]) by core3.amsl.com (Postfix) with ESMTP id 563313A6826 for <tictoc@ietf.org>; Wed, 26 Jan 2011 09:18:18 -0800 (PST)
Received: from inbansmailrelay2.in.alcatel-lucent.com (h135-250-11-33.lucent.com [135.250.11.33]) by ihemail4.lucent.com (8.13.8/IER-o) with ESMTP id p0QHLC7C013345 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Wed, 26 Jan 2011 11:21:14 -0600 (CST)
Received: from INBANSXCHHUB02.in.alcatel-lucent.com (inbansxchhub02.in.alcatel-lucent.com [135.250.12.35]) by inbansmailrelay2.in.alcatel-lucent.com (8.14.3/8.14.3/GMO) with ESMTP id p0QHLAWw012356 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Wed, 26 Jan 2011 22:51:11 +0530
Received: from INBANSXCHMBSA1.in.alcatel-lucent.com ([135.250.12.56]) by INBANSXCHHUB02.in.alcatel-lucent.com ([135.250.12.35]) with mapi; Wed, 26 Jan 2011 22:51:10 +0530
From: "Bhatia, Manav (Manav)" <manav.bhatia@alcatel-lucent.com>
To: Tal Mizrahi <talmi@marvell.com>, Shahram Davari <davari@broadcom.com>, "tictoc@ietf.org" <tictoc@ietf.org>
Date: Wed, 26 Jan 2011 22:51:09 +0530
Thread-Topic: Transporting PTP messages (1588) over MPLS Networks
Thread-Index: Acu0ostDa6CYok1lRYSvUt8QtgvK+QCdFs+gAZgKujAAAHn1AAAAlHjQAABykUA=
Message-ID: <7C362EEF9C7896468B36C9B79200D8350CFB18B51A@INBANSXCHMBSA1.in.alcatel-lucent.com>
References: <7C362EEF9C7896468B36C9B79200D8350CFB0DF1AE@INBANSXCHMBSA1.in.alcatel-lucent.com> <74470498B659FA4687F0B0018C19A89CFCDC0EB8AA@IL-MB01.marvell.com> <2C2F1EBA8050E74EA81502D5740B4BD6941B2F8A0A@SJEXCHCCR02.corp.ad.broadcom.com> <7C362EEF9C7896468B36C9B79200D8350CFB18B518@INBANSXCHMBSA1.in.alcatel-lucent.com> <74470498B659FA4687F0B0018C19A89CFCDC1471A1@IL-MB01.marvell.com>
In-Reply-To: <74470498B659FA4687F0B0018C19A89CFCDC1471A1@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: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Scanned-By: MIMEDefang 2.57 on 135.245.2.39
X-Scanned-By: MIMEDefang 2.64 on 135.250.11.33
Subject: Re: [TICTOC] Transporting PTP messages (1588) over MPLS Networks
X-BeenThere: tictoc@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Timing over IP Connection and Transfer of Clock BOF <tictoc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/tictoc>, <mailto:tictoc-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tictoc>
List-Post: <mailto:tictoc@ietf.org>
List-Help: <mailto:tictoc-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tictoc>, <mailto:tictoc-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 26 Jan 2011 17:18:19 -0000

This can be easily fixed by replacing "highest" with "high" in the current =
text. Would that work?

Cheers, Manav=20

> -----Original Message-----
> From: Tal Mizrahi [mailto:talmi@marvell.com]=20
> Sent: Wednesday, January 26, 2011 10.43 PM
> To: Bhatia, Manav (Manav); Shahram Davari; tictoc@ietf.org
> Subject: RE: Transporting PTP messages (1588) over MPLS Networks
>=20
> Hi Manav, Shahram,
>=20
> >=20
> > 10.  QoS Considerations
> > - I am not sure I understand why this is a MUST. This draft=20
> > defines an encapsulation, while the QoS requirements are=20
> > typically be derived from the application, which is defined=20
> elsewhere.
> >=20
> > SD> The application is PTP, which requires low delay. Are you=20
> > suggesting we make it a should?=20
> >
> >The current text does not use a MUST. Does that look ok?
>=20
> The current wording is "The PTP messages are time critical=20
> and must be treated with the highest priority.",=20
> while the IEEE 1588 states in the informative Annex A that=20
> "PTP event messages should be sent with high priority=20
> compared with other data whenever possible."
> Of course it makes sense that PTP is high priority, but the=20
> current wording seems a bit too stringent.
>=20
> Thanks.=20
> Tal.
>=20
> -----Original Message-----
> From: Bhatia, Manav (Manav) [mailto:manav.bhatia@alcatel-lucent.com]=20
> Sent: Wednesday, January 26, 2011 6:54 PM
> To: Shahram Davari; Tal Mizrahi; tictoc@ietf.org
> Subject: RE: Transporting PTP messages (1588) over MPLS Networks
>=20
> Hi Tal,
>=20
> In addition to what Shahram has said:
>=20
> > 6.  1588 Message Transport
> > "If Two Step Transparent clocks are present, then the=20
> > FOLLOW_UP and DELAY_RESP messages must also be transported=20
> > over the PTP LSPs."=20
> > - for P2P TCs you also need the PDelay_Resp_Follow_Up.
> >=20
> > SD> AFAIK These messages don't require time stamping and=20
> > therefore don't have to be transported over PTP LSP.
>=20
> The PDelay_Resp_Follow_Up message will never go through a TC=20
> and will never have its CF modified.  In the case of a non-TC=20
> PTP LSR, it is only the PDelay_Req and PDelay-Resp message=20
> that are time sensitive.  So the PDelay_Resp_Follow_Up can be=20
> sent outside of the PTP LSP.
>=20
> >=20
> > 10.  QoS Considerations
> > - I am not sure I understand why this is a MUST. This draft=20
> > defines an encapsulation, while the QoS requirements are=20
> > typically be derived from the application, which is defined=20
> elsewhere.
> >=20
> > SD> The application is PTP, which requires low delay. Are you=20
> > suggesting we make it a should?=20
>=20
> The current text does not use a MUST. Does that look ok?
>=20
> Cheers, Manav
> =

From manav.bhatia@alcatel-lucent.com  Wed Jan 26 09:25:59 2011
Return-Path: <manav.bhatia@alcatel-lucent.com>
X-Original-To: tictoc@core3.amsl.com
Delivered-To: tictoc@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 9FC053A688C for <tictoc@core3.amsl.com>; Wed, 26 Jan 2011 09:25:59 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.267
X-Spam-Level: 
X-Spam-Status: No, score=-6.267 tagged_above=-999 required=5 tests=[AWL=0.331,  BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id WbCs7toDHYIg for <tictoc@core3.amsl.com>; Wed, 26 Jan 2011 09:25:58 -0800 (PST)
Received: from ihemail3.lucent.com (ihemail3.lucent.com [135.245.0.37]) by core3.amsl.com (Postfix) with ESMTP id 3E17A3A684B for <tictoc@ietf.org>; Wed, 26 Jan 2011 09:25:58 -0800 (PST)
Received: from inbansmailrelay1.in.alcatel-lucent.com (h135-250-11-31.lucent.com [135.250.11.31]) by ihemail3.lucent.com (8.13.8/IER-o) with ESMTP id p0QHSpjW022777 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Wed, 26 Jan 2011 11:28:54 -0600 (CST)
Received: from INBANSXCHHUB01.in.alcatel-lucent.com (inbansxchhub01.in.alcatel-lucent.com [135.250.12.32]) by inbansmailrelay1.in.alcatel-lucent.com (8.14.3/8.14.3/GMO) with ESMTP id p0QHSo0T005689 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Wed, 26 Jan 2011 22:58:50 +0530
Received: from INBANSXCHMBSA1.in.alcatel-lucent.com ([135.250.12.56]) by INBANSXCHHUB01.in.alcatel-lucent.com ([135.250.12.32]) with mapi; Wed, 26 Jan 2011 22:58:50 +0530
From: "Bhatia, Manav (Manav)" <manav.bhatia@alcatel-lucent.com>
To: "lizhong.jin@zte.com.cn" <lizhong.jin@zte.com.cn>
Date: Wed, 26 Jan 2011 22:58:48 +0530
Thread-Topic: [TICTOC] Transporting PTP messages (1588) over MPLS Networks
Thread-Index: Acu3DAAqcDWytEm/RB+ZuMJTcsv5ugGci/9g
Message-ID: <7C362EEF9C7896468B36C9B79200D8350CFB18B51E@INBANSXCHMBSA1.in.alcatel-lucent.com>
References: <mailman.1779.1295088820.4689.tictoc@ietf.org> <OFA596765B.570CE6DC-ON4825781C.004262BC-4825781C.0044FEEC@zte.com.cn>
In-Reply-To: <OFA596765B.570CE6DC-ON4825781C.004262BC-4825781C.0044FEEC@zte.com.cn>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: multipart/alternative; boundary="_000_7C362EEF9C7896468B36C9B79200D8350CFB18B51EINBANSXCHMBSA_"
MIME-Version: 1.0
X-Scanned-By: MIMEDefang 2.57 on 135.245.2.37
X-Scanned-By: MIMEDefang 2.64 on 135.250.11.31
Cc: "tictoc@ietf.org" <tictoc@ietf.org>
Subject: Re: [TICTOC] Transporting PTP messages (1588) over MPLS Networks
X-BeenThere: tictoc@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Timing over IP Connection and Transfer of Clock BOF <tictoc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/tictoc>, <mailto:tictoc-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tictoc>
List-Post: <mailto:tictoc@ietf.org>
List-Help: <mailto:tictoc-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tictoc>, <mailto:tictoc-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 26 Jan 2011 17:25:59 -0000

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

Hi Lizhong,

You can only ensure that 1588aware LSRs will not do ECMP on PTP LSPs. What =
if we have a non-1588aware LSR in the path? The head end when setting up th=
e RSVP path would know this (by inspecting the IS-IS or OSPF TE info) and c=
ould in such cases make use of the Entropy label to ensure that all PTP pac=
kets follow the same path. This is one scenario where i think we may want t=
o use Entropy labels.

Cheers, Manav

________________________________
From: lizhong.jin@zte.com.cn [mailto:lizhong.jin@zte.com.cn]
Sent: Tuesday, January 18, 2011 6.03 PM
To: Bhatia, Manav (Manav)
Cc: tictoc@ietf.org
Subject: Re: [TICTOC] Transporting PTP messages (1588) over MPLS Networks


Hi Manav,
In section 8 ECMP, since it is said PTP LSPs and PWs MUST NOT be subject to=
 ECMP, why in section 5.2 the encapsulation of figure 2 has entroy label? I=
 am a bit confused.

Regards
Lizhong


> ----------------------------------------------------------------------
>
> Message: 1
> Date: Sat, 15 Jan 2011 16:25:59 +0530
> From: "Bhatia, Manav (Manav)" <manav.bhatia@alcatel-lucent.com>
> Subject: [TICTOC] Transporting PTP messages (1588) over MPLS Networks
> To: "tictoc@ietf.org" <tictoc@ietf.org>
> Message-ID:
>    <7C362EEF9C7896468B36C9B79200D8350CFB0DF1AE@INBANSXCHMBSA1.in.
> alcatel-lucent.com>
>
> Content-Type: text/plain; charset=3D"us-ascii"
>
> Hi,
>
> We have posted a revised version of draft-davari-
> tictoc-1588overmpls-01 and would appreciate a feedback from the WG.
>
> The draft is available here:
> http://www.ietf.org/id/draft-davari-tictoc-1588overmpls-01.txt
>
> Cheers, Manav
>
> --
> Manav Bhatia,
> IP Division, Alcatel-Lucent,
> Bangalore - India
>
>
>

--------------------------------------------------------
ZTE Information Security Notice: The information contained in this mail is =
solely property of the sender's organization. This mail communication is co=
nfidential. Recipients named above are obligated to maintain secrecy and ar=
e 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 th=
e 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.


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

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; charset=3Dus-ascii">
<META content=3D"MSHTML 6.00.2900.6036" name=3DGENERATOR></HEAD>
<BODY>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D185382617-26012011><FONT face=3DA=
rial=20
color=3D#0000ff size=3D2>Hi Lizhong,</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D185382617-26012011><SPAN=20
style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: 'Arial','sans-serif'"><=
/SPAN></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D185382617-26012011><SPAN=20
style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: 'Arial','sans-serif'">Y=
ou can=20
only ensure that 1588aware LSRs will not do ECMP on PTP LSPs.=20
</SPAN></SPAN><SPAN class=3D185382617-26012011><SPAN=20
style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: 'Arial','sans-serif'">W=
hat if=20
we have a non-1588aware LSR in the path? The head end when setting up the R=
SVP=20
path would know this (by inspecting the IS-IS or OSPF TE info) and could in=
 such=20
cases make use of the Entropy label to ensure that all PTP packets follow t=
he=20
same path. This is one scenario where i think we may want to use Entropy=20
labels.</SPAN></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D185382617-26012011><SPAN=20
style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: 'Arial','sans-serif'"><=
/SPAN></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D185382617-26012011><SPAN=20
style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: 'Arial','sans-serif'">C=
heers,=20
Manav</SPAN></SPAN><SPAN class=3D185382617-26012011></DIV></SPAN><BR>
<BLOCKQUOTE dir=3Dltr=20
style=3D"PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #0000ff 2px soli=
d; MARGIN-RIGHT: 0px">
  <DIV class=3DOutlookMessageHeader lang=3Den-us dir=3Dltr align=3Dleft>
  <HR tabIndex=3D-1>
  <FONT face=3DTahoma size=3D2><B>From:</B> lizhong.jin@zte.com.cn=20
  [mailto:lizhong.jin@zte.com.cn] <BR><B>Sent:</B> Tuesday, January 18, 201=
1=20
  6.03 PM<BR><B>To:</B> Bhatia, Manav (Manav)<BR><B>Cc:</B>=20
  tictoc@ietf.org<BR><B>Subject:</B> Re: [TICTOC] Transporting PTP messages=
=20
  (1588) over MPLS Networks<BR></FONT><BR></DIV>
  <DIV></DIV><BR><TT><FONT size=3D2>Hi Manav,</FONT></TT> <BR><TT><FONT siz=
e=3D2>In=20
  section 8 ECMP, since it is said PTP LSPs and PWs MUST NOT be subject to =
ECMP,=20
  why in section 5.2 the encapsulation of figure 2 has entroy label? I am a=
 bit=20
  confused.</FONT></TT> <BR><BR><TT><FONT size=3D2>Regards</FONT></TT>=20
  <BR><TT><FONT size=3D2>Lizhong</FONT></TT> <BR><BR><TT><FONT size=3D2><BR=
>&gt;=20
  ----------------------------------------------------------------------<BR=
>&gt;=20
  <BR>&gt; Message: 1<BR>&gt; Date: Sat, 15 Jan 2011 16:25:59 +0530<BR>&gt;=
=20
  From: "Bhatia, Manav (Manav)" &lt;manav.bhatia@alcatel-lucent.com&gt;<BR>=
&gt;=20
  Subject: [TICTOC] Transporting PTP messages (1588) over MPLS Networks<BR>=
&gt;=20
  To: "tictoc@ietf.org" &lt;tictoc@ietf.org&gt;<BR>&gt; Message-ID:<BR>&gt;=
=20
  &nbsp;=20
  &nbsp;&lt;7C362EEF9C7896468B36C9B79200D8350CFB0DF1AE@INBANSXCHMBSA1.in.<B=
R>&gt;=20
  alcatel-lucent.com&gt;<BR>&gt; &nbsp; &nbsp;<BR>&gt; Content-Type: text/p=
lain;=20
  charset=3D"us-ascii"<BR>&gt; <BR>&gt; Hi,<BR>&gt; <BR>&gt; We have posted=
 a=20
  revised version of draft-davari-<BR>&gt; tictoc-1588overmpls-01 and would=
=20
  appreciate a feedback from the WG.<BR>&gt; <BR>&gt; The draft is availabl=
e=20
  here:<BR>&gt;=20
  http://www.ietf.org/id/draft-davari-tictoc-1588overmpls-01.txt<BR>&gt;=20
  <BR>&gt; Cheers, Manav<BR>&gt; <BR>&gt; --<BR>&gt; Manav Bhatia,<BR>&gt; =
IP=20
  Division, Alcatel-Lucent,<BR>&gt; Bangalore - India<BR>&gt; <BR>&gt;=20
  &nbsp;<BR>&gt; </FONT></TT><BR><PRE>-------------------------------------=
-------------------
ZTE&nbsp;Information&nbsp;Security&nbsp;Notice:&nbsp;The&nbsp;information&n=
bsp;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;a=
bove&nbsp;are&nbsp;obligated&nbsp;to&nbsp;maintain&nbsp;secrecy&nbsp;and&nb=
sp;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&nbs=
p;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&nbs=
p;to&nbsp;whom&nbsp;they&nbsp;are&nbsp;addressed.&nbsp;If&nbsp;you&nbsp;hav=
e&nbsp;received&nbsp;this&nbsp;email&nbsp;in&nbsp;error&nbsp;please&nbsp;no=
tify&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&nbs=
p;of&nbsp;the&nbsp;individual&nbsp;sender.
This&nbsp;message&nbsp;has&nbsp;been&nbsp;scanned&nbsp;for&nbsp;viruses&nbs=
p;and&nbsp;Spam&nbsp;by&nbsp;ZTE&nbsp;Anti-Spam&nbsp;system.
</PRE></BLOCKQUOTE></BODY></HTML>

--_000_7C362EEF9C7896468B36C9B79200D8350CFB18B51EINBANSXCHMBSA_--

From yaakov_s@rad.com  Wed Jan 26 09:43:55 2011
Return-Path: <yaakov_s@rad.com>
X-Original-To: tictoc@core3.amsl.com
Delivered-To: tictoc@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 0A9223A681E for <tictoc@core3.amsl.com>; Wed, 26 Jan 2011 09:43:55 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.487
X-Spam-Level: 
X-Spam-Status: No, score=-102.487 tagged_above=-999 required=5 tests=[AWL=0.112, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id fsFpLA91cPZi for <tictoc@core3.amsl.com>; Wed, 26 Jan 2011 09:43:54 -0800 (PST)
Received: from antivir1.rad.co.il (antivir1.rad.co.il [62.0.23.193]) by core3.amsl.com (Postfix) with ESMTP id D1D483A67EF for <tictoc@ietf.org>; Wed, 26 Jan 2011 09:43:52 -0800 (PST)
Received: from exrad5.ad.rad.co.il ([192.114.24.28]) by antivir1.rad.co.il with ESMTP; 26 Jan 2011 19:46:51 +0200
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; Wed, 26 Jan 2011 19:46:51 +0200
Received: from EXRAD5.ad.rad.co.il ([fe80::ec3e:feb5:8bef:e3ba]) by exus4-drp.ad.rad.co.il ([fe80::5d6f:c2cb:2468:ee2%16]) with mapi id 14.01.0270.001; Wed, 26 Jan 2011 19:46:51 +0200
From: Yaakov Stein <yaakov_s@rad.com>
To: Marshall Eubanks <tme@americafree.tv>
Thread-Topic: [TICTOC] UDP checksum
Thread-Index: Acu49+/VHCD95rNISYmauhcQo/vaHwAADWEwAAB6V/AAAEvoYAAnZ3SAAABoKQAA+YxzQA==
Date: Wed, 26 Jan 2011 17:46:50 +0000
Message-ID: <07F7D7DED63154409F13298786A2ADC903CD929B@EXRAD5.ad.rad.co.il>
References: <7C362EEF9C7896468B36C9B79200D8350CFB0DFDA7@INBANSXCHMBSA1.in.alcatel-lucent.com> <2C2F1EBA8050E74EA81502D5740B4BD6941B04CC39@SJEXCHCCR02.corp.ad.broadcom.com> <7C362EEF9C7896468B36C9B79200D8350CFB0DFDAA@INBANSXCHMBSA1.in.alcatel-lucent.com> <2C2F1EBA8050E74EA81502D5740B4BD6941B04CC6D@SJEXCHCCR02.corp.ad.broadcom.com> <4D39EC31.10602@cisco.com> <01E54480-7D98-46F8-B82A-21A178044512@americafree.tv>
In-Reply-To: <01E54480-7D98-46F8-B82A-21A178044512@americafree.tv>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [192.115.243.62]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "tictoc@ietf.org" <tictoc@ietf.org>
Subject: Re: [TICTOC] UDP checksum
X-BeenThere: tictoc@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Timing over IP Connection and Transfer of Clock BOF <tictoc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/tictoc>, <mailto:tictoc-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tictoc>
List-Post: <mailto:tictoc@ietf.org>
List-Help: <mailto:tictoc-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tictoc>, <mailto:tictoc-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 26 Jan 2011 17:43:55 -0000

Marshall

> I think you are referring to this=20
> which is (will be shortly) in 6man
> http://tools.ietf.org/html/draft-eubanks-chimento-6man-01
>
> This is for the case where there is an "inner" packet with a header and c=
hecksum,=20
> so that the "outer" packet doesn't need protection.


Actually, I think Stewart was referring to http://tools.ietf.org/html/draft=
-ietf-6lowpan-hc-13 .

If there are several proposals on the table, albeit for special cases,
to make the UDP checksum optional, then we can propose that operation too.

Y(J)S


From manav.bhatia@alcatel-lucent.com  Wed Jan 26 16:52:23 2011
Return-Path: <manav.bhatia@alcatel-lucent.com>
X-Original-To: tictoc@core3.amsl.com
Delivered-To: tictoc@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 8F98B28C0D7 for <tictoc@core3.amsl.com>; Wed, 26 Jan 2011 16:52:23 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.274
X-Spam-Level: 
X-Spam-Status: No, score=-6.274 tagged_above=-999 required=5 tests=[AWL=0.325,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id QjlINckmJrqN for <tictoc@core3.amsl.com>; Wed, 26 Jan 2011 16:52:22 -0800 (PST)
Received: from ihemail4.lucent.com (ihemail4.lucent.com [135.245.0.39]) by core3.amsl.com (Postfix) with ESMTP id B839028C0D0 for <tictoc@ietf.org>; Wed, 26 Jan 2011 16:52:22 -0800 (PST)
Received: from inbansmailrelay2.in.alcatel-lucent.com (h135-250-11-33.lucent.com [135.250.11.33]) by ihemail4.lucent.com (8.13.8/IER-o) with ESMTP id p0R0sJaf002146 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Wed, 26 Jan 2011 18:54:22 -0600 (CST)
Received: from INBANSXCHHUB01.in.alcatel-lucent.com (inbansxchhub01.in.alcatel-lucent.com [135.250.12.32]) by inbansmailrelay2.in.alcatel-lucent.com (8.14.3/8.14.3/GMO) with ESMTP id p0R0sIVX026550 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Thu, 27 Jan 2011 06:24:18 +0530
Received: from INBANSXCHMBSA1.in.alcatel-lucent.com ([135.250.12.56]) by INBANSXCHHUB01.in.alcatel-lucent.com ([135.250.12.32]) with mapi; Thu, 27 Jan 2011 06:24:18 +0530
From: "Bhatia, Manav (Manav)" <manav.bhatia@alcatel-lucent.com>
To: Yaakov Stein <yaakov_s@rad.com>, Marshall Eubanks <tme@americafree.tv>
Date: Thu, 27 Jan 2011 06:24:15 +0530
Thread-Topic: [TICTOC] UDP checksum
Thread-Index: Acu49+/VHCD95rNISYmauhcQo/vaHwAADWEwAAB6V/AAAEvoYAAnZ3SAAABoKQAA+YxzQAAOkDDQ
Message-ID: <7C362EEF9C7896468B36C9B79200D8350CFB18B54D@INBANSXCHMBSA1.in.alcatel-lucent.com>
References: <7C362EEF9C7896468B36C9B79200D8350CFB0DFDA7@INBANSXCHMBSA1.in.alcatel-lucent.com> <2C2F1EBA8050E74EA81502D5740B4BD6941B04CC39@SJEXCHCCR02.corp.ad.broadcom.com> <7C362EEF9C7896468B36C9B79200D8350CFB0DFDAA@INBANSXCHMBSA1.in.alcatel-lucent.com> <2C2F1EBA8050E74EA81502D5740B4BD6941B04CC6D@SJEXCHCCR02.corp.ad.broadcom.com> <4D39EC31.10602@cisco.com> <01E54480-7D98-46F8-B82A-21A178044512@americafree.tv> <07F7D7DED63154409F13298786A2ADC903CD929B@EXRAD5.ad.rad.co.il>
In-Reply-To: <07F7D7DED63154409F13298786A2ADC903CD929B@EXRAD5.ad.rad.co.il>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Scanned-By: MIMEDefang 2.57 on 135.245.2.39
X-Scanned-By: MIMEDefang 2.64 on 135.250.11.33
Cc: "tictoc@ietf.org" <tictoc@ietf.org>
Subject: Re: [TICTOC] UDP checksum
X-BeenThere: tictoc@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Timing over IP Connection and Transfer of Clock BOF <tictoc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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, 27 Jan 2011 00:52:23 -0000

Yakov,=20

> Actually, I think Stewart was referring to=20
> http://tools.ietf.org/html/draft-ietf-6lowpan-hc-13 .
>=20
> If there are several proposals on the table, albeit for special cases,
> to make the UDP checksum optional, then we can propose that=20
> operation too.

Alternatively, we could just keep this within our WG and add the following =
to the 1588oMPLS draft:

LSRs that adjust the CF field MAY not update the UDP checksum in case of IP=
v6. The node that terminates the tunnel MUST recompute the UDP checksum aft=
er MPLS decapsulation and before any further processing.

This way the 1588aware LSRs only need to update the CF field at the line ra=
te in the HW and need not worry about the correcting/recomputing the UDP ch=
ecksum. The tunnel terminating node after stripping off the MPLS labels can=
 recompute the UDP checksum and pass it on to the PTP layer above where it =
will be processed.

Cheers, Manav

>=20
> Y(J)S
>=20
> _______________________________________________
> TICTOC mailing list
> TICTOC@ietf.org
> https://www.ietf.org/mailman/listinfo/tictoc
> =

From lizhong.jin@zte.com.cn  Wed Jan 26 19:22:15 2011
Return-Path: <lizhong.jin@zte.com.cn>
X-Original-To: tictoc@core3.amsl.com
Delivered-To: tictoc@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 7061328C0F3 for <tictoc@core3.amsl.com>; Wed, 26 Jan 2011 19:22:15 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.702
X-Spam-Level: 
X-Spam-Status: No, score=-101.702 tagged_above=-999 required=5 tests=[AWL=0.136, 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.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id OCXs-lNNGIhk for <tictoc@core3.amsl.com>; Wed, 26 Jan 2011 19:22:12 -0800 (PST)
Received: from mx5.zte.com.cn (mx6.zte.com.cn [63.218.89.70]) by core3.amsl.com (Postfix) with ESMTP id CB13E28C0F5 for <tictoc@ietf.org>; Wed, 26 Jan 2011 19:22:11 -0800 (PST)
Received: from [10.34.0.130] by mx5.zte.com.cn with surfront esmtp id 35101930506506; Thu, 27 Jan 2011 11:23:12 +0800 (CST)
Received: from [10.30.3.21] by [192.168.168.16] with StormMail ESMTP id 69943.3711756443; Thu, 27 Jan 2011 11:17:31 +0800 (CST)
Received: from notes_smtp.zte.com.cn ([10.30.1.239]) by mse02.zte.com.cn with ESMTP id p0R3Owxi086888; Thu, 27 Jan 2011 11:24:58 +0800 (GMT-8) (envelope-from lizhong.jin@zte.com.cn)
In-Reply-To: <7C362EEF9C7896468B36C9B79200D8350CFB18B51E@INBANSXCHMBSA1.in.alcatel-lucent.com>
To: "Bhatia, Manav (Manav)" <manav.bhatia@alcatel-lucent.com>
MIME-Version: 1.0
X-Mailer: Lotus Notes Release 6.5.6 March 06, 2007
Message-ID: <OF5AD05F9B.BC5D2BE6-ON48257825.0005DD7F-48257825.0012C43D@zte.com.cn>
From: lizhong.jin@zte.com.cn
Date: Thu, 27 Jan 2011 11:24:36 +0800
X-MIMETrack: S/MIME Sign by Notes Client on JinLiZhong127666/user/zte_ltd(Release 6.5.6|March 06, 2007) at 2011-01-27 11:24:58, Serialize by Notes Client on JinLiZhong127666/user/zte_ltd(Release 6.5.6|March 06, 2007) at 2011-01-27 11:24:58, Serialize complete at 2011-01-27 11:24:58, S/MIME Sign failed at 2011-01-27 11:24:58: The cryptographic key was not found, Serialize by Router on notes_smtp/zte_ltd(Release 8.5.1FP4|July 25, 2010) at 2011-01-27 11:24:59, Serialize complete at 2011-01-27 11:24:59
Content-Type: multipart/alternative; boundary="=_alternative 0012C43D48257825_="
X-MAIL: mse02.zte.com.cn p0R3Owxi086888
Cc: "tictoc@ietf.org" <tictoc@ietf.org>
Subject: Re: [TICTOC] Transporting PTP messages (1588) over MPLS Networks
X-BeenThere: tictoc@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Timing over IP Connection and Transfer of Clock BOF <tictoc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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, 27 Jan 2011 03:22:15 -0000

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

Hi Manav,
I don't think I fully understand and need some clarification. See in line.

Thanks.
Lizhong
 

"Bhatia, Manav (Manav)" <manav.bhatia@alcatel-lucent.com> wrote on 
2011-01-27 01:28:48:

> Hi Lizhong,
> 
> You can only ensure that 1588aware LSRs will not do ECMP on PTP 
> LSPs. What if we have a non-1588aware LSR in the path? 
[Lizhong] All the LSRs and LERs along PTP LSP MUST be 1588aware, right?

>The head end 
> when setting up the RSVP path would know this (by inspecting the IS-
> IS or OSPF TE info) and could in such cases make use of the Entropy 
> label to ensure that all PTP packets follow the same path. 
[Lizhong] How to use entropy label to ensure all PTP packets follow the 
same path? If there is entropy label, it is possible that the forward and 
reverse path would be different.

>This is 
> one scenario where i think we may want to use Entropy labels.
> 
> Cheers, Manav
> 
> From: lizhong.jin@zte.com.cn [mailto:lizhong.jin@zte.com.cn] 
> Sent: Tuesday, January 18, 2011 6.03 PM
> To: Bhatia, Manav (Manav)
> Cc: tictoc@ietf.org
> Subject: Re: [TICTOC] Transporting PTP messages (1588) over MPLS 
Networks

> 
> Hi Manav, 
> In section 8 ECMP, since it is said PTP LSPs and PWs MUST NOT be 
> subject to ECMP, why in section 5.2 the encapsulation of figure 2 
> has entroy label? I am a bit confused. 
> 
> Regards 
> Lizhong 
> 
> 
> > ----------------------------------------------------------------------
> > 
> > Message: 1
> > Date: Sat, 15 Jan 2011 16:25:59 +0530
> > From: "Bhatia, Manav (Manav)" <manav.bhatia@alcatel-lucent.com>
> > Subject: [TICTOC] Transporting PTP messages (1588) over MPLS Networks
> > To: "tictoc@ietf.org" <tictoc@ietf.org>
> > Message-ID:
> >    <7C362EEF9C7896468B36C9B79200D8350CFB0DF1AE@INBANSXCHMBSA1.in.
> > alcatel-lucent.com>
> > 
> > Content-Type: text/plain; charset="us-ascii"
> > 
> > Hi,
> > 
> > We have posted a revised version of draft-davari-
> > tictoc-1588overmpls-01 and would appreciate a feedback from the WG.
> > 
> > The draft is available here:
> > http://www.ietf.org/id/draft-davari-tictoc-1588overmpls-01.txt
> > 
> > Cheers, Manav
> > 
> > --
> > Manav Bhatia,
> > IP Division, Alcatel-Lucent,
> > Bangalore - India
> > 
> > 
> > 
> --------------------------------------------------------
> 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.


--------------------------------------------------------
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 0012C43D48257825_=
Content-Type: text/html; charset="US-ASCII"


<br><font size=2 face="sans-serif">Hi Manav,</font>
<br><font size=2 face="sans-serif">I don't think I fully understand and
need some clarification. See in line.</font>
<br>
<br><tt><font size=2>Thanks.</font></tt>
<br><tt><font size=2>Lizhong</font></tt>
<br><font size=1 face="Arial">&nbsp;</font>
<br>
<br><tt><font size=2>&quot;Bhatia, Manav (Manav)&quot; &lt;manav.bhatia@alcatel-lucent.com&gt;
wrote on 2011-01-27 01:28:48:<br>
<br>
&gt; Hi Lizhong,</font></tt>
<br><tt><font size=2>&gt; &nbsp;</font></tt>
<br><tt><font size=2>&gt; You can only ensure that 1588aware LSRs will
not do ECMP on PTP <br>
&gt; LSPs. What if we have a non-1588aware LSR in the path? </font></tt>
<br><tt><font size=2>[Lizhong] </font></tt><font size=2 face="sans-serif">All
the LSRs and LERs along PTP LSP MUST be </font><tt><font size=2>1588aware</font></tt><font size=2 face="sans-serif">,
right?</font>
<br>
<br><tt><font size=2>&gt;The head end <br>
&gt; when setting up the RSVP path would know this (by inspecting the IS-<br>
&gt; IS or OSPF TE info) and could in such cases make use of the Entropy
<br>
&gt; label to ensure that all PTP packets follow the same path. </font></tt>
<br><tt><font size=2>[Lizhong] </font></tt><font size=2 face="sans-serif">How
to use entropy label to </font><tt><font size=2>ensure all PTP packets
follow the same path? If there is entropy label, it is possible that the
forward and reverse path would be different.</font></tt>
<br>
<br><tt><font size=2>&gt;This is <br>
&gt; one scenario where i think we may want to use Entropy labels.</font></tt>
<br><tt><font size=2>&gt; &nbsp;</font></tt>
<br><tt><font size=2>&gt; Cheers, Manav</font></tt>
<br><tt><font size=2>&gt; <br>
&gt; From: lizhong.jin@zte.com.cn [mailto:lizhong.jin@zte.com.cn] <br>
&gt; Sent: Tuesday, January 18, 2011 6.03 PM<br>
&gt; To: Bhatia, Manav (Manav)<br>
&gt; Cc: tictoc@ietf.org<br>
&gt; Subject: Re: [TICTOC] Transporting PTP messages (1588) over MPLS Networks<br>
</font></tt>
<br><tt><font size=2>&gt; <br>
&gt; Hi Manav, <br>
&gt; In section 8 ECMP, since it is said PTP LSPs and PWs MUST NOT be <br>
&gt; subject to ECMP, why in section 5.2 the encapsulation of figure 2
<br>
&gt; has entroy label? I am a bit confused. <br>
&gt; <br>
&gt; Regards <br>
&gt; Lizhong <br>
&gt; <br>
&gt; <br>
&gt; &gt; ----------------------------------------------------------------------<br>
&gt; &gt; <br>
&gt; &gt; Message: 1<br>
&gt; &gt; Date: Sat, 15 Jan 2011 16:25:59 +0530<br>
&gt; &gt; From: &quot;Bhatia, Manav (Manav)&quot; &lt;manav.bhatia@alcatel-lucent.com&gt;<br>
&gt; &gt; Subject: [TICTOC] Transporting PTP messages (1588) over MPLS
Networks<br>
&gt; &gt; To: &quot;tictoc@ietf.org&quot; &lt;tictoc@ietf.org&gt;<br>
&gt; &gt; Message-ID:<br>
&gt; &gt; &nbsp; &nbsp;&lt;7C362EEF9C7896468B36C9B79200D8350CFB0DF1AE@INBANSXCHMBSA1.in.<br>
&gt; &gt; alcatel-lucent.com&gt;<br>
&gt; &gt; &nbsp; &nbsp;<br>
&gt; &gt; Content-Type: text/plain; charset=&quot;us-ascii&quot;<br>
&gt; &gt; <br>
&gt; &gt; Hi,<br>
&gt; &gt; <br>
&gt; &gt; We have posted a revised version of draft-davari-<br>
&gt; &gt; tictoc-1588overmpls-01 and would appreciate a feedback from the
WG.<br>
&gt; &gt; <br>
&gt; &gt; The draft is available here:<br>
&gt; &gt; http://www.ietf.org/id/draft-davari-tictoc-1588overmpls-01.txt<br>
&gt; &gt; <br>
&gt; &gt; Cheers, Manav<br>
&gt; &gt; <br>
&gt; &gt; --<br>
&gt; &gt; Manav Bhatia,<br>
&gt; &gt; IP Division, Alcatel-Lucent,<br>
&gt; &gt; Bangalore - India<br>
&gt; &gt; <br>
&gt; &gt; &nbsp;<br>
&gt; &gt; </font></tt>
<br><tt><font size=2>&gt; --------------------------------------------------------<br>
&gt; ZTE Information Security Notice: The information contained in this
<br>
&gt; mail is solely property of the sender's organization. This mail <br>
&gt; communication is confidential. Recipients named above are obligated
<br>
&gt; to maintain secrecy and are not permitted to disclose the contents
<br>
&gt; of this communication to others.<br>
&gt; This email and any files transmitted with it are confidential and
<br>
&gt; intended solely for the use of the individual or entity to whom they<br>
&gt; are addressed. If you have received this email in error please <br>
&gt; notify the originator of the message. Any views expressed in this
<br>
&gt; message are those of the individual sender.<br>
&gt; This message has been scanned for viruses and Spam by ZTE Anti-Spam
system.<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 0012C43D48257825_=--


From manav.bhatia@alcatel-lucent.com  Wed Jan 26 19:57:07 2011
Return-Path: <manav.bhatia@alcatel-lucent.com>
X-Original-To: tictoc@core3.amsl.com
Delivered-To: tictoc@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 81E9028C104 for <tictoc@core3.amsl.com>; Wed, 26 Jan 2011 19:57:07 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.279
X-Spam-Level: 
X-Spam-Status: No, score=-6.279 tagged_above=-999 required=5 tests=[AWL=0.320,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id bxTTPdN2qAX6 for <tictoc@core3.amsl.com>; Wed, 26 Jan 2011 19:57:06 -0800 (PST)
Received: from ihemail3.lucent.com (ihemail3.lucent.com [135.245.0.37]) by core3.amsl.com (Postfix) with ESMTP id 386B228C101 for <tictoc@ietf.org>; Wed, 26 Jan 2011 19:57:05 -0800 (PST)
Received: from inbansmailrelay1.in.alcatel-lucent.com (h135-250-11-31.lucent.com [135.250.11.31]) by ihemail3.lucent.com (8.13.8/IER-o) with ESMTP id p0R3xvV5019145 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Wed, 26 Jan 2011 22:00:01 -0600 (CST)
Received: from INBANSXCHHUB01.in.alcatel-lucent.com (inbansxchhub01.in.alcatel-lucent.com [135.250.12.32]) by inbansmailrelay1.in.alcatel-lucent.com (8.14.3/8.14.3/GMO) with ESMTP id p0R3xuDT032562 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Thu, 27 Jan 2011 09:29:56 +0530
Received: from [135.250.26.32] (135.250.19.8) by INBANSXCHHUB01.in.alcatel-lucent.com (135.250.12.32) with Microsoft SMTP Server (TLS) id 8.3.106.1; Thu, 27 Jan 2011 09:29:56 +0530
Message-ID: <4D40EDAA.3050702@alcatel-lucent.com>
Date: Thu, 27 Jan 2011 09:29:38 +0530
From: Manav Bhatia <manav.bhatia@alcatel-lucent.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2.13) Gecko/20101207 Lightning/1.0b2 Thunderbird/3.1.7 ThunderBrowse/3.3.4
MIME-Version: 1.0
To: "lizhong.jin@zte.com.cn" <lizhong.jin@zte.com.cn>
References: <OF5AD05F9B.BC5D2BE6-ON48257825.0005DD7F-48257825.0012C43D@zte.com.cn>
In-Reply-To: <OF5AD05F9B.BC5D2BE6-ON48257825.0005DD7F-48257825.0012C43D@zte.com.cn>
Content-Type: text/plain; charset="ISO-8859-1"; format=flowed
Content-Transfer-Encoding: 7bit
X-Scanned-By: MIMEDefang 2.57 on 135.245.2.37
X-Scanned-By: MIMEDefang 2.64 on 135.250.11.31
Cc: "tictoc@ietf.org" <tictoc@ietf.org>
Subject: Re: [TICTOC] Transporting PTP messages (1588) over MPLS Networks
X-BeenThere: tictoc@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Timing over IP Connection and Transfer of Clock BOF <tictoc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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, 27 Jan 2011 03:57:07 -0000

Hi Lizhong,

>  >
>  > You can only ensure that 1588aware LSRs will not do ECMP on PTP
>  > LSPs. What if we have a non-1588aware LSR in the path?
> [Lizhong] All the LSRs and LERs along PTP LSP MUST be 1588aware, right?

In an ideal world Yes, all routers would be 1588aware. However, this 
being far from an ideal world, you can always have some LSRs that are 
not draft-ietf-tictoc-1588overmpls aware. You will note that this draft 
also has some text on the non 1588aware LSRs. These LSRs could be doing 
ECMP and without an entropy label, may cause PTP messages to be load 
distributed across different paths.

>
>  >The head end
>  > when setting up the RSVP path would know this (by inspecting the IS-
>  > IS or OSPF TE info) and could in such cases make use of the Entropy
>  > label to ensure that all PTP packets follow the same path.
> [Lizhong] How to use entropy label to ensure all PTP packets follow the
> same path?

Using an entropy label will ensure that all PTP packets in one direction 
follow the same path.

> If there is entropy label, it is possible that the forward
> and reverse path would be different.

Since LSPs are unidirectional there is no guarantee that the two paths 
would be symmetrical. So this really is an issue orthogonal to the use 
of entropy labels for carrying PTP traffic.

We should probably add some text in the draft that says that the two 
paths must be symmetrical.

Cheers, Manav

>
>  >This is
>  > one scenario where i think we may want to use Entropy labels.
>  >
>  > Cheers, Manav
>  >
>  > From: lizhong.jin@zte.com.cn [mailto:lizhong.jin@zte.com.cn]
>  > Sent: Tuesday, January 18, 2011 6.03 PM
>  > To: Bhatia, Manav (Manav)
>  > Cc: tictoc@ietf.org
>  > Subject: Re: [TICTOC] Transporting PTP messages (1588) over MPLS Networks
>
>  >
>  > Hi Manav,
>  > In section 8 ECMP, since it is said PTP LSPs and PWs MUST NOT be
>  > subject to ECMP, why in section 5.2 the encapsulation of figure 2
>  > has entroy label? I am a bit confused.
>  >
>  > Regards
>  > Lizhong
>  >
>  >
>  > > ----------------------------------------------------------------------
>  > >
>  > > Message: 1
>  > > Date: Sat, 15 Jan 2011 16:25:59 +0530
>  > > From: "Bhatia, Manav (Manav)" <manav.bhatia@alcatel-lucent.com>
>  > > Subject: [TICTOC] Transporting PTP messages (1588) over MPLS Networks
>  > > To: "tictoc@ietf.org" <tictoc@ietf.org>
>  > > Message-ID:
>  > > <7C362EEF9C7896468B36C9B79200D8350CFB0DF1AE@INBANSXCHMBSA1.in.
>  > > alcatel-lucent.com>
>  > >
>  > > Content-Type: text/plain; charset="us-ascii"
>  > >
>  > > Hi,
>  > >
>  > > We have posted a revised version of draft-davari-
>  > > tictoc-1588overmpls-01 and would appreciate a feedback from the WG.
>  > >
>  > > The draft is available here:
>  > > http://www.ietf.org/id/draft-davari-tictoc-1588overmpls-01.txt
>  > >
>  > > Cheers, Manav
>  > >
>  > > --
>  > > Manav Bhatia,
>  > > IP Division, Alcatel-Lucent,
>  > > Bangalore - India
>  > >
>  > >
>  > >
>  > --------------------------------------------------------
>  > 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.
>
> --------------------------------------------------------
> 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.

From lizhong.jin@zte.com.cn  Wed Jan 26 23:19:30 2011
Return-Path: <lizhong.jin@zte.com.cn>
X-Original-To: tictoc@core3.amsl.com
Delivered-To: tictoc@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 34C4F3A6955 for <tictoc@core3.amsl.com>; Wed, 26 Jan 2011 23:19:30 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.577
X-Spam-Level: 
X-Spam-Status: No, score=-101.577 tagged_above=-999 required=5 tests=[AWL=0.261, 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.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Zbx9GVKn1dgq for <tictoc@core3.amsl.com>; Wed, 26 Jan 2011 23:19:28 -0800 (PST)
Received: from mx5.zte.com.cn (mx5.zte.com.cn [63.217.80.70]) by core3.amsl.com (Postfix) with ESMTP id A91983A6941 for <tictoc@ietf.org>; Wed, 26 Jan 2011 23:19:27 -0800 (PST)
Received: from [10.30.17.100] by mx5.zte.com.cn with surfront esmtp id 205951930506506; Thu, 27 Jan 2011 15:16:51 +0800 (CST)
Received: from [10.30.3.21] by [192.168.168.16] with StormMail ESMTP id 69943.3711756443; Thu, 27 Jan 2011 15:14:44 +0800 (CST)
Received: from notes_smtp.zte.com.cn ([10.30.1.239]) by mse02.zte.com.cn with ESMTP id p0R7M9DA070637; Thu, 27 Jan 2011 15:22:09 +0800 (GMT-8) (envelope-from lizhong.jin@zte.com.cn)
In-Reply-To: <4D40EDAA.3050702@alcatel-lucent.com>
To: Manav Bhatia <manav.bhatia@alcatel-lucent.com>
MIME-Version: 1.0
X-Mailer: Lotus Notes Release 6.5.6 March 06, 2007
Message-ID: <OF17C81FDB.C027296E-ON48257825.0024E099-48257825.00287B7B@zte.com.cn>
From: lizhong.jin@zte.com.cn
Date: Thu, 27 Jan 2011 15:21:47 +0800
X-MIMETrack: S/MIME Sign by Notes Client on JinLiZhong127666/user/zte_ltd(Release 6.5.6|March 06, 2007) at 2011-01-27 15:22:10, Serialize by Notes Client on JinLiZhong127666/user/zte_ltd(Release 6.5.6|March 06, 2007) at 2011-01-27 15:22:10, Serialize complete at 2011-01-27 15:22:10, S/MIME Sign failed at 2011-01-27 15:22:10: The cryptographic key was not found, Serialize by Router on notes_smtp/zte_ltd(Release 8.5.1FP4|July 25, 2010) at 2011-01-27 15:22:11, Serialize complete at 2011-01-27 15:22:11
Content-Type: multipart/alternative; boundary="=_alternative 00287B7B48257825_="
X-MAIL: mse02.zte.com.cn p0R7M9DA070637
Cc: "tictoc@ietf.org" <tictoc@ietf.org>
Subject: Re: [TICTOC] Transporting PTP messages (1588) over MPLS Networks
X-BeenThere: tictoc@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Timing over IP Connection and Transfer of Clock BOF <tictoc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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, 27 Jan 2011 07:19:30 -0000

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

Hi Manav,
See my comments in line.

Thanks
Lizhong
 

Manav Bhatia <manav.bhatia@alcatel-lucent.com> wrote on 2011-01-27 
11:59:38:

> Hi Lizhong,
> 
> >  >
> >  > You can only ensure that 1588aware LSRs will not do ECMP on PTP
> >  > LSPs. What if we have a non-1588aware LSR in the path?
> > [Lizhong] All the LSRs and LERs along PTP LSP MUST be 1588aware, 
right?
> 
> In an ideal world Yes, all routers would be 1588aware. However, this 
> being far from an ideal world, you can always have some LSRs that are 
> not draft-ietf-tictoc-1588overmpls aware. You will note that this draft 
> also has some text on the non 1588aware LSRs. These LSRs could be doing 
> ECMP and without an entropy label, may cause PTP messages to be load 
> distributed across different paths.
[Lizhong] then in section 13, it is said: "This capability MUST then be 
taken into account during path computation to prefer nodes that advertise 
themselves as 1588-aware, so that the PTP LSPs can be properly handled." 
How to understand "prefer nodes"? If there is a shortest path with some 
non 1588aware LSRs, and a less optimal path with all 1588aware LSRs, which 
path the ingress LER should take?

> 
> >
> >  >The head end
> >  > when setting up the RSVP path would know this (by inspecting the 
IS-
> >  > IS or OSPF TE info) and could in such cases make use of the Entropy
> >  > label to ensure that all PTP packets follow the same path.
> > [Lizhong] How to use entropy label to ensure all PTP packets follow 
the
> > same path?
> 
> Using an entropy label will ensure that all PTP packets in one direction 

> follow the same path.
[Lizhong] since control word is required for 1588 over PW encapsulation, 
if without entropy label, all PTP packets in one direction will also 
follow the same path.

> 
> > If there is entropy label, it is possible that the forward
> > and reverse path would be different.
> 
> Since LSPs are unidirectional there is no guarantee that the two paths 
> would be symmetrical. So this really is an issue orthogonal to the use 
> of entropy labels for carrying PTP traffic.
> 
> We should probably add some text in the draft that says that the two 
> paths must be symmetrical.
[Lizhong] If there is a boundled interface between two LSRs, the control 
plane will only see one logical interface. Then it is still possible the 
forward and reverse path be different at the physical level in ECMP case.

> 
> Cheers, Manav
> 
> >
> >  >This is
> >  > one scenario where i think we may want to use Entropy labels.
> >  >
> >  > Cheers, Manav
> >  >
> >  > From: lizhong.jin@zte.com.cn [mailto:lizhong.jin@zte.com.cn]
> >  > Sent: Tuesday, January 18, 2011 6.03 PM
> >  > To: Bhatia, Manav (Manav)
> >  > Cc: tictoc@ietf.org
> >  > Subject: Re: [TICTOC] Transporting PTP messages (1588) over MPLS 
Networks
> >
> >  >
> >  > Hi Manav,
> >  > In section 8 ECMP, since it is said PTP LSPs and PWs MUST NOT be
> >  > subject to ECMP, why in section 5.2 the encapsulation of figure 2
> >  > has entroy label? I am a bit confused.
> >  >
> >  > Regards
> >  > Lizhong
> >  >
> >  >
> >  > > 
----------------------------------------------------------------------
> >  > >
> >  > > Message: 1
> >  > > Date: Sat, 15 Jan 2011 16:25:59 +0530
> >  > > From: "Bhatia, Manav (Manav)" <manav.bhatia@alcatel-lucent.com>
> >  > > Subject: [TICTOC] Transporting PTP messages (1588) over MPLS 
Networks
> >  > > To: "tictoc@ietf.org" <tictoc@ietf.org>
> >  > > Message-ID:
> >  > > <7C362EEF9C7896468B36C9B79200D8350CFB0DF1AE@INBANSXCHMBSA1.in.
> >  > > alcatel-lucent.com>
> >  > >
> >  > > Content-Type: text/plain; charset="us-ascii"
> >  > >
> >  > > Hi,
> >  > >
> >  > > We have posted a revised version of draft-davari-
> >  > > tictoc-1588overmpls-01 and would appreciate a feedback from the 
WG.
> >  > >
> >  > > The draft is available here:
> >  > > http://www.ietf.org/id/draft-davari-tictoc-1588overmpls-01.txt
> >  > >
> >  > > Cheers, Manav
> >  > >
> >  > > --
> >  > > Manav Bhatia,
> >  > > IP Division, Alcatel-Lucent,
> >  > > Bangalore - India
> >  > >
> >  > >
> >  > >
> >  > --------------------------------------------------------
> >  > 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.
> >
> > --------------------------------------------------------
> > 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.
> 


--------------------------------------------------------
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 00287B7B48257825_=
Content-Type: text/html; charset="US-ASCII"


<br><font size=2 face="sans-serif">Hi Manav,</font>
<br><font size=2 face="sans-serif">See my comments in line.</font>
<br>
<br><font size=2 face="sans-serif">Thanks</font>
<br><font size=2 face="sans-serif">Lizhong</font>
<br><font size=1 face="Arial">&nbsp;</font>
<br>
<br><tt><font size=2>Manav Bhatia &lt;manav.bhatia@alcatel-lucent.com&gt;
wrote on 2011-01-27 11:59:38:<br>
<br>
&gt; Hi Lizhong,<br>
&gt; <br>
&gt; &gt; &nbsp;&gt;<br>
&gt; &gt; &nbsp;&gt; You can only ensure that 1588aware LSRs will not do
ECMP on PTP<br>
&gt; &gt; &nbsp;&gt; LSPs. What if we have a non-1588aware LSR in the path?<br>
&gt; &gt; [Lizhong] All the LSRs and LERs along PTP LSP MUST be 1588aware,
right?<br>
&gt; <br>
&gt; In an ideal world Yes, all routers would be 1588aware. However, this
<br>
&gt; being far from an ideal world, you can always have some LSRs that
are <br>
&gt; not draft-ietf-tictoc-1588overmpls aware. You will note that this
draft <br>
&gt; also has some text on the non 1588aware LSRs. These LSRs could be
doing <br>
&gt; ECMP and without an entropy label, may cause PTP messages to be load
<br>
&gt; distributed across different paths.</font></tt>
<br><tt><font size=2>[Lizhong] then in section 13, it is said: &quot;This
capability MUST then be taken into account during path computation to prefer
nodes that advertise themselves as 1588-aware, so that the PTP LSPs can
be properly handled.&quot; How to understand &quot;prefer nodes&quot;?
If there is a shortest path with some non 1588aware LSRs, and a less optimal
path with all 1588aware LSRs, which path the ingress LER should take?</font></tt>
<br><tt><font size=2><br>
&gt; <br>
&gt; &gt;<br>
&gt; &gt; &nbsp;&gt;The head end<br>
&gt; &gt; &nbsp;&gt; when setting up the RSVP path would know this (by
inspecting the IS-<br>
&gt; &gt; &nbsp;&gt; IS or OSPF TE info) and could in such cases make use
of the Entropy<br>
&gt; &gt; &nbsp;&gt; label to ensure that all PTP packets follow the same
path.<br>
&gt; &gt; [Lizhong] How to use entropy label to ensure all PTP packets
follow the<br>
&gt; &gt; same path?<br>
&gt; <br>
&gt; Using an entropy label will ensure that all PTP packets in one direction
<br>
&gt; follow the same path.</font></tt>
<br><tt><font size=2>[Lizhong] since control word is required for 1588
over PW encapsulation, if without entropy label, all PTP packets in one
direction will also follow the same path.</font></tt>
<br><tt><font size=2><br>
&gt; <br>
&gt; &gt; If there is entropy label, it is possible that the forward<br>
&gt; &gt; and reverse path would be different.<br>
&gt; <br>
&gt; Since LSPs are unidirectional there is no guarantee that the two paths
<br>
&gt; would be symmetrical. So this really is an issue orthogonal to the
use <br>
&gt; of entropy labels for carrying PTP traffic.<br>
&gt; <br>
&gt; We should probably add some text in the draft that says that the two
<br>
&gt; paths must be symmetrical.</font></tt>
<br><tt><font size=2>[Lizhong] If there is a boundled interface between
two LSRs, the control plane will only see one logical interface. Then it
is still possible the forward and reverse path be different at the physical
level in ECMP case.</font></tt>
<br><tt><font size=2><br>
&gt; <br>
&gt; Cheers, Manav<br>
&gt; <br>
&gt; &gt;<br>
&gt; &gt; &nbsp;&gt;This is<br>
&gt; &gt; &nbsp;&gt; one scenario where i think we may want to use Entropy
labels.<br>
&gt; &gt; &nbsp;&gt;<br>
&gt; &gt; &nbsp;&gt; Cheers, Manav<br>
&gt; &gt; &nbsp;&gt;<br>
&gt; &gt; &nbsp;&gt; From: lizhong.jin@zte.com.cn [mailto:lizhong.jin@zte.com.cn]<br>
&gt; &gt; &nbsp;&gt; Sent: Tuesday, January 18, 2011 6.03 PM<br>
&gt; &gt; &nbsp;&gt; To: Bhatia, Manav (Manav)<br>
&gt; &gt; &nbsp;&gt; Cc: tictoc@ietf.org<br>
&gt; &gt; &nbsp;&gt; Subject: Re: [TICTOC] Transporting PTP messages (1588)
over MPLS Networks<br>
&gt; &gt;<br>
&gt; &gt; &nbsp;&gt;<br>
&gt; &gt; &nbsp;&gt; Hi Manav,<br>
&gt; &gt; &nbsp;&gt; In section 8 ECMP, since it is said PTP LSPs and PWs
MUST NOT be<br>
&gt; &gt; &nbsp;&gt; subject to ECMP, why in section 5.2 the encapsulation
of figure 2<br>
&gt; &gt; &nbsp;&gt; has entroy label? I am a bit confused.<br>
&gt; &gt; &nbsp;&gt;<br>
&gt; &gt; &nbsp;&gt; Regards<br>
&gt; &gt; &nbsp;&gt; Lizhong<br>
&gt; &gt; &nbsp;&gt;<br>
&gt; &gt; &nbsp;&gt;<br>
&gt; &gt; &nbsp;&gt; &gt; ----------------------------------------------------------------------<br>
&gt; &gt; &nbsp;&gt; &gt;<br>
&gt; &gt; &nbsp;&gt; &gt; Message: 1<br>
&gt; &gt; &nbsp;&gt; &gt; Date: Sat, 15 Jan 2011 16:25:59 +0530<br>
&gt; &gt; &nbsp;&gt; &gt; From: &quot;Bhatia, Manav (Manav)&quot; &lt;manav.bhatia@alcatel-lucent.com&gt;<br>
&gt; &gt; &nbsp;&gt; &gt; Subject: [TICTOC] Transporting PTP messages (1588)
over MPLS Networks<br>
&gt; &gt; &nbsp;&gt; &gt; To: &quot;tictoc@ietf.org&quot; &lt;tictoc@ietf.org&gt;<br>
&gt; &gt; &nbsp;&gt; &gt; Message-ID:<br>
&gt; &gt; &nbsp;&gt; &gt; &lt;7C362EEF9C7896468B36C9B79200D8350CFB0DF1AE@INBANSXCHMBSA1.in.<br>
&gt; &gt; &nbsp;&gt; &gt; alcatel-lucent.com&gt;<br>
&gt; &gt; &nbsp;&gt; &gt;<br>
&gt; &gt; &nbsp;&gt; &gt; Content-Type: text/plain; charset=&quot;us-ascii&quot;<br>
&gt; &gt; &nbsp;&gt; &gt;<br>
&gt; &gt; &nbsp;&gt; &gt; Hi,<br>
&gt; &gt; &nbsp;&gt; &gt;<br>
&gt; &gt; &nbsp;&gt; &gt; We have posted a revised version of draft-davari-<br>
&gt; &gt; &nbsp;&gt; &gt; tictoc-1588overmpls-01 and would appreciate a
feedback from the WG.<br>
&gt; &gt; &nbsp;&gt; &gt;<br>
&gt; &gt; &nbsp;&gt; &gt; The draft is available here:<br>
&gt; &gt; &nbsp;&gt; &gt; http://www.ietf.org/id/draft-davari-tictoc-1588overmpls-01.txt<br>
&gt; &gt; &nbsp;&gt; &gt;<br>
&gt; &gt; &nbsp;&gt; &gt; Cheers, Manav<br>
&gt; &gt; &nbsp;&gt; &gt;<br>
&gt; &gt; &nbsp;&gt; &gt; --<br>
&gt; &gt; &nbsp;&gt; &gt; Manav Bhatia,<br>
&gt; &gt; &nbsp;&gt; &gt; IP Division, Alcatel-Lucent,<br>
&gt; &gt; &nbsp;&gt; &gt; Bangalore - India<br>
&gt; &gt; &nbsp;&gt; &gt;<br>
&gt; &gt; &nbsp;&gt; &gt;<br>
&gt; &gt; &nbsp;&gt; &gt;<br>
&gt; &gt; &nbsp;&gt; --------------------------------------------------------<br>
&gt; &gt; &nbsp;&gt; ZTE Information Security Notice: The information contained
in this<br>
&gt; &gt; &nbsp;&gt; mail is solely property of the sender's organization.
This mail<br>
&gt; &gt; &nbsp;&gt; communication is confidential. Recipients named above
are obligated<br>
&gt; &gt; &nbsp;&gt; to maintain secrecy and are not permitted to disclose
the contents<br>
&gt; &gt; &nbsp;&gt; of this communication to others.<br>
&gt; &gt; &nbsp;&gt; This email and any files transmitted with it are confidential
and<br>
&gt; &gt; &nbsp;&gt; intended solely for the use of the individual or entity
to whom they<br>
&gt; &gt; &nbsp;&gt; are addressed. If you have received this email in
error please<br>
&gt; &gt; &nbsp;&gt; notify the originator of the message. Any views expressed
in this<br>
&gt; &gt; &nbsp;&gt; message are those of the individual sender.<br>
&gt; &gt; &nbsp;&gt; This message has been scanned for viruses and Spam
by ZTE Anti-Spam<br>
&gt; &gt; system.<br>
&gt; &gt;<br>
&gt; &gt; --------------------------------------------------------<br>
&gt; &gt; ZTE &nbsp;Information &nbsp;Security &nbsp;Notice: &nbsp;The
&nbsp;information &nbsp;contained &nbsp;<br>
&gt; in &nbsp;this &nbsp;mail &nbsp;is &nbsp;solely &nbsp;property &nbsp;of
&nbsp;the &nbsp;sender's &nbsp;<br>
&gt; organization. &nbsp;This &nbsp;mail &nbsp;communication &nbsp;is &nbsp;confidential.
&nbsp;<br>
&gt; Recipients &nbsp;named &nbsp;above &nbsp;are &nbsp;obligated &nbsp;to
&nbsp;maintain &nbsp;secrecy &nbsp;and<br>
&gt; are &nbsp;not &nbsp;permitted &nbsp;to &nbsp;disclose &nbsp;the &nbsp;contents
&nbsp;of &nbsp;this &nbsp;<br>
&gt; communication &nbsp;to &nbsp;others.<br>
&gt; &gt; This &nbsp;email &nbsp;and &nbsp;any &nbsp;files &nbsp;transmitted
&nbsp;with &nbsp;it &nbsp;are &nbsp;<br>
&gt; confidential &nbsp;and &nbsp;intended &nbsp;solely &nbsp;for &nbsp;the
&nbsp;use &nbsp;of &nbsp;the &nbsp;<br>
&gt; individual &nbsp;or &nbsp;entity &nbsp;to &nbsp;whom &nbsp;they &nbsp;are
&nbsp;addressed. &nbsp;If &nbsp;you &nbsp;<br>
&gt; have &nbsp;received &nbsp;this &nbsp;email &nbsp;in &nbsp;error &nbsp;please
&nbsp;notify &nbsp;the &nbsp;<br>
&gt; originator &nbsp;of &nbsp;the &nbsp;message. &nbsp;Any &nbsp;views
&nbsp;expressed &nbsp;in &nbsp;this &nbsp;<br>
&gt; message &nbsp;are &nbsp;those &nbsp;of &nbsp;the &nbsp;individual
&nbsp;sender.<br>
&gt; &gt; This &nbsp;message &nbsp;has &nbsp;been &nbsp;scanned &nbsp;for
&nbsp;viruses &nbsp;and &nbsp;Spam &nbsp;by &nbsp;<br>
&gt; ZTE &nbsp;Anti-Spam &nbsp;system.<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 00287B7B48257825_=--


From talmi@marvell.com  Wed Jan 26 23:42:40 2011
Return-Path: <talmi@marvell.com>
X-Original-To: tictoc@core3.amsl.com
Delivered-To: tictoc@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 24C953A6933 for <tictoc@core3.amsl.com>; Wed, 26 Jan 2011 23:42:40 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.269
X-Spam-Level: 
X-Spam-Status: No, score=-6.269 tagged_above=-999 required=5 tests=[AWL=0.330,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id flNSitjReCVg for <tictoc@core3.amsl.com>; Wed, 26 Jan 2011 23:42:39 -0800 (PST)
Received: from na3sys009aog112.obsmtp.com (na3sys009aog112.obsmtp.com [74.125.149.207]) by core3.amsl.com (Postfix) with SMTP id 4661C3A692F for <tictoc@ietf.org>; Wed, 26 Jan 2011 23:42:38 -0800 (PST)
Received: from source ([65.219.4.130]) (using TLSv1) by na3sys009aob112.postini.com ([74.125.148.12]) with SMTP ID DSNKTUEipPPI3SkdgXHFdhJFLOys0SC88In+@postini.com; Wed, 26 Jan 2011 23:45:42 PST
Received: from YK-HUB01.marvell.com (10.4.102.51) by sc-owa02.marvell.com (10.93.76.22) with Microsoft SMTP Server (TLS) id 8.2.213.0; Wed, 26 Jan 2011 23:43:47 -0800
Received: from IL-MB01.marvell.com ([10.4.102.53]) by YK-HUB01.marvell.com ([10.4.102.51]) with mapi; Thu, 27 Jan 2011 09:43:46 +0200
From: Tal Mizrahi <talmi@marvell.com>
To: "Bhatia, Manav (Manav)" <manav.bhatia@alcatel-lucent.com>, Shahram Davari <davari@broadcom.com>, "tictoc@ietf.org" <tictoc@ietf.org>
Date: Thu, 27 Jan 2011 09:43:47 +0200
Thread-Topic: Transporting PTP messages (1588) over MPLS Networks
Thread-Index: Acu0ostDa6CYok1lRYSvUt8QtgvK+QCdFs+gAZgKujAAAHn1AAAAlHjQAABykUAAHhljYA==
Message-ID: <74470498B659FA4687F0B0018C19A89CFCDC147214@IL-MB01.marvell.com>
References: <7C362EEF9C7896468B36C9B79200D8350CFB0DF1AE@INBANSXCHMBSA1.in.alcatel-lucent.com> <74470498B659FA4687F0B0018C19A89CFCDC0EB8AA@IL-MB01.marvell.com> <2C2F1EBA8050E74EA81502D5740B4BD6941B2F8A0A@SJEXCHCCR02.corp.ad.broadcom.com> <7C362EEF9C7896468B36C9B79200D8350CFB18B518@INBANSXCHMBSA1.in.alcatel-lucent.com> <74470498B659FA4687F0B0018C19A89CFCDC1471A1@IL-MB01.marvell.com> <7C362EEF9C7896468B36C9B79200D8350CFB18B51A@INBANSXCHMBSA1.in.alcatel-lucent.com>
In-Reply-To: <7C362EEF9C7896468B36C9B79200D8350CFB18B51A@INBANSXCHMBSA1.in.alcatel-lucent.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: Re: [TICTOC] Transporting PTP messages (1588) over MPLS Networks
X-BeenThere: tictoc@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Timing over IP Connection and Transfer of Clock BOF <tictoc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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, 27 Jan 2011 07:42:40 -0000

>This can be easily fixed by replacing "highest" with "high" in the current=
 >text. Would that work?
Sounds okay.

Regards,
Tal.

-----Original Message-----
From: Bhatia, Manav (Manav) [mailto:manav.bhatia@alcatel-lucent.com]=20
Sent: Wednesday, January 26, 2011 7:21 PM
To: Tal Mizrahi; Shahram Davari; tictoc@ietf.org
Subject: RE: Transporting PTP messages (1588) over MPLS Networks

This can be easily fixed by replacing "highest" with "high" in the current =
text. Would that work?

Cheers, Manav=20

> -----Original Message-----
> From: Tal Mizrahi [mailto:talmi@marvell.com]=20
> Sent: Wednesday, January 26, 2011 10.43 PM
> To: Bhatia, Manav (Manav); Shahram Davari; tictoc@ietf.org
> Subject: RE: Transporting PTP messages (1588) over MPLS Networks
>=20
> Hi Manav, Shahram,
>=20
> >=20
> > 10.  QoS Considerations
> > - I am not sure I understand why this is a MUST. This draft=20
> > defines an encapsulation, while the QoS requirements are=20
> > typically be derived from the application, which is defined=20
> elsewhere.
> >=20
> > SD> The application is PTP, which requires low delay. Are you=20
> > suggesting we make it a should?=20
> >
> >The current text does not use a MUST. Does that look ok?
>=20
> The current wording is "The PTP messages are time critical=20
> and must be treated with the highest priority.",=20
> while the IEEE 1588 states in the informative Annex A that=20
> "PTP event messages should be sent with high priority=20
> compared with other data whenever possible."
> Of course it makes sense that PTP is high priority, but the=20
> current wording seems a bit too stringent.
>=20
> Thanks.=20
> Tal.
>=20
> -----Original Message-----
> From: Bhatia, Manav (Manav) [mailto:manav.bhatia@alcatel-lucent.com]=20
> Sent: Wednesday, January 26, 2011 6:54 PM
> To: Shahram Davari; Tal Mizrahi; tictoc@ietf.org
> Subject: RE: Transporting PTP messages (1588) over MPLS Networks
>=20
> Hi Tal,
>=20
> In addition to what Shahram has said:
>=20
> > 6.  1588 Message Transport
> > "If Two Step Transparent clocks are present, then the=20
> > FOLLOW_UP and DELAY_RESP messages must also be transported=20
> > over the PTP LSPs."=20
> > - for P2P TCs you also need the PDelay_Resp_Follow_Up.
> >=20
> > SD> AFAIK These messages don't require time stamping and=20
> > therefore don't have to be transported over PTP LSP.
>=20
> The PDelay_Resp_Follow_Up message will never go through a TC=20
> and will never have its CF modified.  In the case of a non-TC=20
> PTP LSR, it is only the PDelay_Req and PDelay-Resp message=20
> that are time sensitive.  So the PDelay_Resp_Follow_Up can be=20
> sent outside of the PTP LSP.
>=20
> >=20
> > 10.  QoS Considerations
> > - I am not sure I understand why this is a MUST. This draft=20
> > defines an encapsulation, while the QoS requirements are=20
> > typically be derived from the application, which is defined=20
> elsewhere.
> >=20
> > SD> The application is PTP, which requires low delay. Are you=20
> > suggesting we make it a should?=20
>=20
> The current text does not use a MUST. Does that look ok?
>=20
> Cheers, Manav
>=20

From talmi@marvell.com  Wed Jan 26 23:59:22 2011
Return-Path: <talmi@marvell.com>
X-Original-To: tictoc@core3.amsl.com
Delivered-To: tictoc@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 071223A6956 for <tictoc@core3.amsl.com>; Wed, 26 Jan 2011 23:59:22 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.324
X-Spam-Level: 
X-Spam-Status: No, score=-6.324 tagged_above=-999 required=5 tests=[AWL=0.275,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id f3MzKyjVkG9L for <tictoc@core3.amsl.com>; Wed, 26 Jan 2011 23:59:21 -0800 (PST)
Received: from na3sys009aog111.obsmtp.com (na3sys009aog111.obsmtp.com [74.125.149.205]) by core3.amsl.com (Postfix) with SMTP id B74763A6938 for <tictoc@ietf.org>; Wed, 26 Jan 2011 23:59:20 -0800 (PST)
Received: from source ([65.219.4.130]) (using TLSv1) by na3sys009aob111.postini.com ([74.125.148.12]) with SMTP ID DSNKTUEmj6ZjmiDaj+mRQPg/T4r4CdEJ1EC1@postini.com; Thu, 27 Jan 2011 00:02:24 PST
Received: from YK-HUB01.marvell.com (10.4.102.51) by sc-owa02.marvell.com (10.93.76.22) with Microsoft SMTP Server (TLS) id 8.2.213.0; Thu, 27 Jan 2011 00:00:00 -0800
Received: from IL-MB01.marvell.com ([10.4.102.53]) by YK-HUB01.marvell.com ([10.4.102.51]) with mapi; Thu, 27 Jan 2011 09:59:57 +0200
From: Tal Mizrahi <talmi@marvell.com>
To: Shahram Davari <davari@broadcom.com>, "tictoc@ietf.org" <tictoc@ietf.org>
Date: Thu, 27 Jan 2011 09:59:57 +0200
Thread-Topic: Transporting PTP messages (1588) over MPLS Networks
Thread-Index: Acu0ostDa6CYok1lRYSvUt8QtgvK+QCdFs+gAZgKujAAH2+KEA==
Message-ID: <74470498B659FA4687F0B0018C19A89CFCDC147239@IL-MB01.marvell.com>
References: <7C362EEF9C7896468B36C9B79200D8350CFB0DF1AE@INBANSXCHMBSA1.in.alcatel-lucent.com> <74470498B659FA4687F0B0018C19A89CFCDC0EB8AA@IL-MB01.marvell.com> <2C2F1EBA8050E74EA81502D5740B4BD6941B2F8A0A@SJEXCHCCR02.corp.ad.broadcom.com>
In-Reply-To: <2C2F1EBA8050E74EA81502D5740B4BD6941B2F8A0A@SJEXCHCCR02.corp.ad.broadcom.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: Re: [TICTOC] Transporting PTP messages (1588) over MPLS Networks
X-BeenThere: tictoc@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Timing over IP Connection and Transfer of Clock BOF <tictoc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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, 27 Jan 2011 07:59:22 -0000

Hi Shahram,

>11.  FCS Recalculation
>"FCS retention described in [RFC4720] MUST not be used"=20
>- that makes sense, but seems to contradict the first half of the sentence=
 >"Ethernet FCS MUST be recalculated at every LSR". In my understanding if =
>retention is not used, only the LERs have to recompute the FCS. LSRs may >=
alter the CF, but do not need to bother with the FCS.
>
>SD> I think your understanding is not correct.

I guess I am missing something - I will appreciate if you can elaborate why=
 an intermediate LSR must recalculate the FCS in the absence of FCS retenti=
on.

In the absence of FCS retention, we would have according to RFC4448:
"The ingress Native Service Processing (NSP) function strips the preamble a=
nd frame check sequence (FCS) from the Ethernet frame and transports the fr=
ame in its entirety across the PW.  This is done regardless of the presence=
 of the 802.1Q tag in the frame. The egress NSP function receives the Ether=
net frame from the PW and regenerates the preamble or FCS"

Thanks.
Tal.

-----Original Message-----
From: Shahram Davari [mailto:davari@broadcom.com]=20
Sent: Wednesday, January 26, 2011 6:49 PM
To: Tal Mizrahi; Bhatia, Manav (Manav); tictoc@ietf.org
Subject: RE: Transporting PTP messages (1588) over MPLS Networks

Hi Tal,

Please find my comments inline.

-----Original Message-----
From: tictoc-bounces@ietf.org [mailto:tictoc-bounces@ietf.org] On Behalf Of=
 Tal Mizrahi
Sent: Tuesday, January 18, 2011 6:04 AM
To: Bhatia, Manav (Manav); tictoc@ietf.org
Subject: Re: [TICTOC] Transporting PTP messages (1588) over MPLS Networks

Hi Manav,

A few comments below.

Section 3. Problem Statement says that "The defined method is applicable to=
 both MPLS and MPLS-TP networks."
- however, Section 9. OAM, Control and Management does not mention MPLS-TP =
OAM. Furthermore, section 5.1. 1588 over LSP Encapsulation shows an encapsu=
lation with a single label, and does not show that an optional GAL is possi=
ble.

SD> We could add the MPLS-TP OAM to the text. Regarding GAL, this is explic=
itly not allowed to be in the stack when the encapsulated data is PTP messa=
ge. So GAL is not optional.

6.  1588 Message Transport
"If Two Step Transparent clocks are present, then the FOLLOW_UP and DELAY_R=
ESP messages must also be transported over the PTP LSPs."=20
- for P2P TCs you also need the PDelay_Resp_Follow_Up.

SD> AFAIK These messages don't require time stamping and therefore don't ha=
ve to be transported over PTP LSP.

10.  QoS Considerations
- I am not sure I understand why this is a MUST. This draft defines an enca=
psulation, while the QoS requirements are typically be derived from the app=
lication, which is defined elsewhere.

SD> The application is PTP, which requires low delay. Are you suggesting we=
 make it a should?=20

11.  FCS Recalculation
"FCS retention described in [RFC4720] MUST not be used"=20
- that makes sense, but seems to contradict the first half of the sentence =
"Ethernet FCS MUST be recalculated at every LSR". In my understanding if re=
tention is not used, only the LERs have to recompute the FCS. LSRs may alte=
r the CF, but do not need to bother with the FCS.

SD> I think your understanding is not correct.=20

Tal.

-----Original Message-----
From: tictoc-bounces@ietf.org [mailto:tictoc-bounces@ietf.org] On Behalf Of=
 Bhatia, Manav (Manav)
Sent: Saturday, January 15, 2011 12:56 PM
To: tictoc@ietf.org
Subject: [TICTOC] Transporting PTP messages (1588) over MPLS Networks

Hi,

We have posted a revised version of draft-davari-tictoc-1588overmpls-01 and=
 would appreciate a feedback from the WG.

The draft is available here:
http://www.ietf.org/id/draft-davari-tictoc-1588overmpls-01.txt

Cheers, Manav

--
Manav Bhatia,
IP Division, Alcatel-Lucent,
Bangalore - India

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



From manav.bhatia@alcatel-lucent.com  Thu Jan 27 02:30:25 2011
Return-Path: <manav.bhatia@alcatel-lucent.com>
X-Original-To: tictoc@core3.amsl.com
Delivered-To: tictoc@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 3EDEC3A6977 for <tictoc@core3.amsl.com>; Thu, 27 Jan 2011 02:30:25 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.284
X-Spam-Level: 
X-Spam-Status: No, score=-6.284 tagged_above=-999 required=5 tests=[AWL=0.314,  BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id yZkrlY-MyF7h for <tictoc@core3.amsl.com>; Thu, 27 Jan 2011 02:30:24 -0800 (PST)
Received: from ihemail1.lucent.com (ihemail1.lucent.com [135.245.0.33]) by core3.amsl.com (Postfix) with ESMTP id 098013A6990 for <tictoc@ietf.org>; Thu, 27 Jan 2011 02:30:23 -0800 (PST)
Received: from inbansmailrelay1.in.alcatel-lucent.com (h135-250-11-31.lucent.com [135.250.11.31]) by ihemail1.lucent.com (8.13.8/IER-o) with ESMTP id p0RAXJCo012985 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Thu, 27 Jan 2011 04:33:22 -0600 (CST)
Received: from INBANSXCHHUB02.in.alcatel-lucent.com (inbansxchhub02.in.alcatel-lucent.com [135.250.12.35]) by inbansmailrelay1.in.alcatel-lucent.com (8.14.3/8.14.3/GMO) with ESMTP id p0RAXIwD012264 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Thu, 27 Jan 2011 16:03:18 +0530
Received: from INBANSXCHMBSA1.in.alcatel-lucent.com ([135.250.12.56]) by INBANSXCHHUB02.in.alcatel-lucent.com ([135.250.12.35]) with mapi; Thu, 27 Jan 2011 16:03:18 +0530
From: "Bhatia, Manav (Manav)" <manav.bhatia@alcatel-lucent.com>
To: "lizhong.jin@zte.com.cn" <lizhong.jin@zte.com.cn>
Date: Thu, 27 Jan 2011 16:03:17 +0530
Thread-Topic: [TICTOC] Transporting PTP messages (1588) over MPLS Networks
Thread-Index: Acu98ygt5LUYMgmNQZCw6Z5AWC5+rQAF6Jew
Message-ID: <7C362EEF9C7896468B36C9B79200D8350CFB18B739@INBANSXCHMBSA1.in.alcatel-lucent.com>
References: <4D40EDAA.3050702@alcatel-lucent.com> <OF17C81FDB.C027296E-ON48257825.0024E099-48257825.00287B7B@zte.com.cn>
In-Reply-To: <OF17C81FDB.C027296E-ON48257825.0024E099-48257825.00287B7B@zte.com.cn>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: multipart/alternative; boundary="_000_7C362EEF9C7896468B36C9B79200D8350CFB18B739INBANSXCHMBSA_"
MIME-Version: 1.0
X-Scanned-By: MIMEDefang 2.57 on 135.245.2.33
X-Scanned-By: MIMEDefang 2.64 on 135.250.11.31
Cc: "tictoc@ietf.org" <tictoc@ietf.org>
Subject: Re: [TICTOC] Transporting PTP messages (1588) over MPLS Networks
X-BeenThere: tictoc@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Timing over IP Connection and Transfer of Clock BOF <tictoc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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, 27 Jan 2011 10:30:25 -0000

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

Hi Lizhong,

> not draft-ietf-tictoc-1588overmpls aware. You will note that this draft
> also has some text on the non 1588aware LSRs. These LSRs could be doing
> ECMP and without an entropy label, may cause PTP messages to be load
> distributed across different paths.
[Lizhong] then in section 13, it is said: "This capability MUST then be tak=
en into account during path computation to prefer nodes that advertise them=
selves as 1588-aware, so that the PTP LSPs can be properly handled." How to=
 understand "prefer nodes"? If there is a shortest path with some non 1588a=
ware LSRs, and a less optimal path with all 1588aware LSRs, which path the =
ingress LER should take?

[Manav] There is nothing new here and it happens all the time while computi=
ng CSPF. You pick the path which satisfies your contraints. Now, if you wan=
t a path with all 1588aware LSRs then thats precisely what CSPF will return=
 you. If you want to insist on a shorter path then you need to add other co=
nstraints in addition to this.

>
> >
> >  >The head end
> >  > when setting up the RSVP path would know this (by inspecting the IS-
> >  > IS or OSPF TE info) and could in such cases make use of the Entropy
> >  > label to ensure that all PTP packets follow the same path.
> > [Lizhong] How to use entropy label to ensure all PTP packets follow the
> > same path?
>
> Using an entropy label will ensure that all PTP packets in one direction
> follow the same path.
[Lizhong] since control word is required for 1588 over PW encapsulation, if=
 without entropy label, all PTP packets in one direction will also follow t=
he same path.

[Manav] I think we must use a stronger language in Sec 5.2 regarding using =
control word. I think i will concur with you here that if CW is being used =
then we may not need an entropy label. However, i dont see a strong reason =
why we should restrict it. The current draft says that control word usage i=
s optional and i dont find any issue with that. Do you?

>
> > If there is entropy label, it is possible that the forward
> > and reverse path would be different.
>
> Since LSPs are unidirectional there is no guarantee that the two paths
> would be symmetrical. So this really is an issue orthogonal to the use
> of entropy labels for carrying PTP traffic.
>
> We should probably add some text in the draft that says that the two
> paths must be symmetrical.
[Lizhong] If there is a boundled interface between two LSRs, the control pl=
ane will only see one logical interface. Then it is still possible the forw=
ard and reverse path be different at the physical level in ECMP case.

[Manav] Is the assumption that the two ends of LAG could be connected to tw=
o different systems, something like a multi-chassis lag? I am not sure if t=
here is much that we can do about this except add a note against such a for=
m of load distribution in the document.

Cheers, Manav

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

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; charset=3Dus-ascii">
<META content=3D"MSHTML 6.00.2900.6036" name=3DGENERATOR></HEAD>
<BODY>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D750061310-27012011><FONT face=3DA=
rial=20
color=3D#0000ff size=3D2>Hi Lizhong,</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D750061310-27012011><FONT face=3DA=
rial=20
color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><TT><FONT size=3D2>&gt; not draft-ietf-tictoc-1=
588overmpls=20
aware. You will note that this draft <BR>&gt; also has some text on the non=
=20
1588aware LSRs. These LSRs could be doing <BR>&gt; ECMP and without an entr=
opy=20
label, may cause PTP messages to be load <BR>&gt; distributed across differ=
ent=20
paths.</FONT></TT> <BR><TT><FONT size=3D2>[Lizhong] then in section 13, it =
is=20
said: "This capability MUST then be taken into account during path computat=
ion=20
to prefer nodes that advertise themselves as 1588-aware, so that the PTP LS=
Ps=20
can be properly handled." How to understand "prefer nodes"? If there is a=20
shortest path with some non 1588aware LSRs, and a less optimal path with al=
l=20
1588aware LSRs, which path the ingress LER should take?</FONT></TT>&nbsp;<S=
PAN=20
class=3D750061310-27012011><FONT face=3DArial color=3D#0000ff=20
size=3D2>&nbsp;</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D750061310-27012011><FONT face=3DA=
rial=20
color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D750061310-27012011><FONT face=3DA=
rial=20
color=3D#0000ff size=3D2>[Manav] There is nothing&nbsp;new here and it happ=
ens all=20
the time while computing CSPF. You pick the path which satisfies your=20
contraints. Now, if you want a path with all 1588aware LSRs then thats prec=
isely=20
what CSPF will return you.</FONT>&nbsp;<FONT face=3DArial color=3D#0000ff s=
ize=3D2>If=20
you want to insist on a shorter path then you need to add other constraints=
 in=20
addition to this.</FONT></SPAN><BR><TT><FONT size=3D2><BR>&gt; <BR>&gt;=20
&gt;<BR>&gt; &gt; &nbsp;&gt;The head end<BR>&gt; &gt; &nbsp;&gt; when setti=
ng up=20
the RSVP path would know this (by inspecting the IS-<BR>&gt; &gt; &nbsp;&gt=
; IS=20
or OSPF TE info) and could in such cases make use of the Entropy<BR>&gt; &g=
t;=20
&nbsp;&gt; label to ensure that all PTP packets follow the same path.<BR>&g=
t;=20
&gt; [Lizhong] How to use entropy label to ensure all PTP packets follow=20
the<BR>&gt; &gt; same path?<BR>&gt; <BR>&gt; Using an entropy label will en=
sure=20
that all PTP packets in one direction <BR>&gt; follow the same path.</FONT>=
</TT>=20
<BR><TT><FONT size=3D2>[Lizhong] since control word is required for 1588 ov=
er PW=20
encapsulation, if without entropy label, all PTP packets in one direction w=
ill=20
also follow the same path.</FONT></TT>&nbsp;<SPAN class=3D750061310-2701201=
1><FONT=20
face=3DArial color=3D#0000ff size=3D2>&nbsp;</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D750061310-27012011><FONT face=3DA=
rial=20
color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D750061310-27012011><FONT face=3DA=
rial=20
color=3D#0000ff size=3D2>[Manav] I think we must&nbsp;use a stronger=20
language&nbsp;in Sec 5.2 regarding using control word. I think&nbsp;i will=
=20
concur with you here that if CW is being used then we may not need an entro=
py=20
label.</FONT>&nbsp;<FONT face=3DArial color=3D#0000ff size=3D2>However, i d=
ont see a=20
strong reason why we should restrict it. The current draft says that contro=
l=20
word usage is optional and i dont find any issue with that. Do=20
you?</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D750061310-27012011></SPAN><SPAN=20
class=3D750061310-27012011><FONT face=3DArial color=3D#0000ff=20
size=3D2>&nbsp;</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><TT><FONT size=3D2>&gt; <BR>&gt; &gt; If there =
is entropy=20
label, it is possible that the forward<BR>&gt; &gt; and reverse path would =
be=20
different.<BR>&gt; <BR>&gt; Since LSPs are unidirectional there is no guara=
ntee=20
that the two paths <BR>&gt; would be symmetrical. So this really is an issu=
e=20
orthogonal to the use <BR>&gt; of entropy labels for carrying PTP=20
traffic.<BR>&gt; <BR>&gt; We should probably add some text in the draft tha=
t=20
says that the two <BR>&gt; paths must be symmetrical.</FONT></TT> <BR><TT><=
FONT=20
size=3D2>[Lizhong] If there is a boundled interface between two LSRs, the c=
ontrol=20
plane will only see one logical interface. Then it is still possible the fo=
rward=20
and reverse path be different at the physical level in ECMP=20
case.</FONT></TT>&nbsp;<BR><TT><FONT size=3D2><SPAN class=3D750061310-27012=
011><FONT=20
face=3DArial color=3D#0000ff>&nbsp;</FONT></SPAN></FONT></TT></DIV>
<DIV dir=3Dltr align=3Dleft><TT><FONT size=3D2><SPAN class=3D750061310-2701=
2011><FONT=20
face=3DArial color=3D#0000ff>[Manav] Is the assumption that the two ends of=
 LAG=20
could be connected to two different systems, something like a multi-chassis=
 lag?=20
I am not sure if there is much that we can do about this except add a note=
=20
against such a form of load distribution in the=20
document.</FONT></SPAN></FONT></TT></DIV>
<DIV dir=3Dltr align=3Dleft><TT><SPAN class=3D750061310-27012011><FONT face=
=3DArial=20
color=3D#0000ff></FONT></SPAN><BR><SPAN class=3D750061310-27012011><FONT=20
size=3D2>Cheers, Manav</FONT></SPAN></TT></DIV></BODY></HTML>

--_000_7C362EEF9C7896468B36C9B79200D8350CFB18B739INBANSXCHMBSA_--

From lizhong.jin@zte.com.cn  Thu Jan 27 08:15:21 2011
Return-Path: <lizhong.jin@zte.com.cn>
X-Original-To: tictoc@core3.amsl.com
Delivered-To: tictoc@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 658803A67D3 for <tictoc@core3.amsl.com>; Thu, 27 Jan 2011 08:15:21 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.588
X-Spam-Level: 
X-Spam-Status: No, score=-101.588 tagged_above=-999 required=5 tests=[AWL=0.250, 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.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id M89QdYzwTTqg for <tictoc@core3.amsl.com>; Thu, 27 Jan 2011 08:15:20 -0800 (PST)
Received: from mx5.zte.com.cn (mx5.zte.com.cn [63.217.80.70]) by core3.amsl.com (Postfix) with ESMTP id 7F7803A67E2 for <tictoc@ietf.org>; Thu, 27 Jan 2011 08:15:19 -0800 (PST)
Received: from [10.30.17.100] by mx5.zte.com.cn with surfront esmtp id 205951930506506; Fri, 28 Jan 2011 00:13:49 +0800 (CST)
Received: from [10.30.3.20] by [192.168.168.16] with StormMail ESMTP id 69943.3711756443; Fri, 28 Jan 2011 00:10:39 +0800 (CST)
Received: from notes_smtp.zte.com.cn ([10.30.1.239]) by mse01.zte.com.cn with ESMTP id p0RGIBVL070193; Fri, 28 Jan 2011 00:18:11 +0800 (GMT-8) (envelope-from lizhong.jin@zte.com.cn)
In-Reply-To: <7C362EEF9C7896468B36C9B79200D8350CFB18B739@INBANSXCHMBSA1.in.alcatel-lucent.com>
To: "Bhatia, Manav (Manav)" <manav.bhatia@alcatel-lucent.com>
MIME-Version: 1.0
X-Mailer: Lotus Notes Release 6.5.6 March 06, 2007
Message-ID: <OF38C7CAD6.A42B741E-ON48257825.0056C504-48257825.00598F25@zte.com.cn>
From: lizhong.jin@zte.com.cn
Date: Fri, 28 Jan 2011 00:17:48 +0800
X-MIMETrack: S/MIME Sign by Notes Client on JinLiZhong127666/user/zte_ltd(Release 6.5.6|March 06, 2007) at 2011-01-28 00:18:13, Serialize by Notes Client on JinLiZhong127666/user/zte_ltd(Release 6.5.6|March 06, 2007) at 2011-01-28 00:18:13, Serialize complete at 2011-01-28 00:18:13, S/MIME Sign failed at 2011-01-28 00:18:13: The cryptographic key was not found, Serialize by Router on notes_smtp/zte_ltd(Release 8.5.1FP4|July 25, 2010) at 2011-01-28 00:18:13
Content-Type: multipart/alternative; boundary="=_alternative 00598F2448257825_="
X-MAIL: mse01.zte.com.cn p0RGIBVL070193
Cc: "tictoc@ietf.org" <tictoc@ietf.org>
Subject: Re: [TICTOC] Transporting PTP messages (1588) over MPLS Networks
X-BeenThere: tictoc@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Timing over IP Connection and Transfer of Clock BOF <tictoc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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, 27 Jan 2011 16:15:21 -0000

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

Manav,
See comments in line.

Lizhong
 

"Bhatia, Manav (Manav)" <manav.bhatia@alcatel-lucent.com> wrote on 
2011-01-27 18:33:17:

> Hi Lizhong,
> 
> > not draft-ietf-tictoc-1588overmpls aware. You will note that this 
draft 
> > also has some text on the non 1588aware LSRs. These LSRs could be 
doing 
> > ECMP and without an entropy label, may cause PTP messages to be load 
> > distributed across different paths. 
> [Lizhong] then in section 13, it is said: "This capability MUST then
> be taken into account during path computation to prefer nodes that 
> advertise themselves as 1588-aware, so that the PTP LSPs can be 
> properly handled." How to understand "prefer nodes"? If there is a 
> shortest path with some non 1588aware LSRs, and a less optimal path 
> with all 1588aware LSRs, which path the ingress LER should take? 
> 
> [Manav] There is nothing new here and it happens all the time while 
> computing CSPF. You pick the path which satisfies your contraints. 
> Now, if you want a path with all 1588aware LSRs then thats precisely
> what CSPF will return you. If you want to insist on a shorter path 
> then you need to add other constraints in addition to this.
[Lizhong] OK, I see. Actually my first impression is that it is a bit 
difficult to define such policy for CSPF, in order to fullfill the timing 
accuracy.

> 
> > 
> > >
> > >  >The head end
> > >  > when setting up the RSVP path would know this (by inspecting the 
IS-
> > >  > IS or OSPF TE info) and could in such cases make use of the 
Entropy
> > >  > label to ensure that all PTP packets follow the same path.
> > > [Lizhong] How to use entropy label to ensure all PTP packets follow 
the
> > > same path?
> > 
> > Using an entropy label will ensure that all PTP packets in one 
direction 
> > follow the same path. 
> [Lizhong] since control word is required for 1588 over PW 
> encapsulation, if without entropy label, all PTP packets in one 
> direction will also follow the same path. 
> 
> [Manav] I think we must use a stronger language in Sec 5.2 regarding
> using control word. I think i will concur with you here that if CW 
> is being used then we may not need an entropy label. However, i dont
> see a strong reason why we should restrict it. The current draft 
> says that control word usage is optional and i dont find any issue 
> with that. Do you?
[Lizhong] the current draft says control word SHOULD be used. And yes, 
stronger language is welcome.

> 
> > 
> > > If there is entropy label, it is possible that the forward
> > > and reverse path would be different.
> > 
> > Since LSPs are unidirectional there is no guarantee that the two paths 

> > would be symmetrical. So this really is an issue orthogonal to the use 

> > of entropy labels for carrying PTP traffic.
> > 
> > We should probably add some text in the draft that says that the two 
> > paths must be symmetrical. 
> [Lizhong] If there is a boundled interface between two LSRs, the 
> control plane will only see one logical interface. Then it is still 
> possible the forward and reverse path be different at the physical 
> level in ECMP case. 
> 
> [Manav] Is the assumption that the two ends of LAG could be 
> connected to two different systems, something like a multi-chassis 
> lag? I am not sure if there is much that we can do about this except
> add a note against such a form of load distribution in the document.
[Lizhong] I mean the LAG between two end-points, not MC-LAG. E.g, one LAG 
interface with physical link A & B between two end-points, it is possible 
that the forward path will go through A, and backward path will go through 
B, then the physical path is not symmetric. If I understand correctly, you 
just assume the transport delay on link A & B are the same, but this is 
not always true, especially for the composite link defined in RTGWG (
draft-ietf-rtgwg-cl-requirement).

> 
> Cheers, Manav

--------------------------------------------------------
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 00598F2448257825_=
Content-Type: text/html; charset="US-ASCII"


<br><font size=2 face="sans-serif">Manav,</font>
<br><font size=2 face="sans-serif">See comments in line.</font>
<br>
<br><font size=2 face="sans-serif">Lizhong</font>
<br><font size=1 face="Arial">&nbsp;</font>
<br>
<br><tt><font size=2>&quot;Bhatia, Manav (Manav)&quot; &lt;manav.bhatia@alcatel-lucent.com&gt;
wrote on 2011-01-27 18:33:17:<br>
<br>
&gt; Hi Lizhong,</font></tt>
<br><tt><font size=2>&gt; &nbsp;</font></tt>
<br><tt><font size=2>&gt; &gt; not draft-ietf-tictoc-1588overmpls aware.
You will note that this draft <br>
&gt; &gt; also has some text on the non 1588aware LSRs. These LSRs could
be doing <br>
&gt; &gt; ECMP and without an entropy label, may cause PTP messages to
be load <br>
&gt; &gt; distributed across different paths. <br>
&gt; [Lizhong] then in section 13, it is said: &quot;This capability MUST
then<br>
&gt; be taken into account during path computation to prefer nodes that
<br>
&gt; advertise themselves as 1588-aware, so that the PTP LSPs can be <br>
&gt; properly handled.&quot; How to understand &quot;prefer nodes&quot;?
If there is a <br>
&gt; shortest path with some non 1588aware LSRs, and a less optimal path
<br>
&gt; with all 1588aware LSRs, which path the ingress LER should take? &nbsp;</font></tt>
<br><tt><font size=2>&gt; &nbsp;</font></tt>
<br><tt><font size=2>&gt; [Manav] There is nothing new here and it happens
all the time while <br>
&gt; computing CSPF. You pick the path which satisfies your contraints.
<br>
&gt; Now, if you want a path with all 1588aware LSRs then thats precisely<br>
&gt; what CSPF will return you. If you want to insist on a shorter path
<br>
&gt; then you need to add other constraints in addition to this.</font></tt>
<br><tt><font size=2>[Lizhong] OK, I see. Actually my first impression
is that it is a bit difficult to define such policy for CSPF, in order
to fullfill the timing accuracy.</font></tt>
<br><tt><font size=2><br>
&gt; <br>
&gt; &gt; <br>
&gt; &gt; &gt;<br>
&gt; &gt; &gt; &nbsp;&gt;The head end<br>
&gt; &gt; &gt; &nbsp;&gt; when setting up the RSVP path would know this
(by inspecting the IS-<br>
&gt; &gt; &gt; &nbsp;&gt; IS or OSPF TE info) and could in such cases make
use of the Entropy<br>
&gt; &gt; &gt; &nbsp;&gt; label to ensure that all PTP packets follow the
same path.<br>
&gt; &gt; &gt; [Lizhong] How to use entropy label to ensure all PTP packets
follow the<br>
&gt; &gt; &gt; same path?<br>
&gt; &gt; <br>
&gt; &gt; Using an entropy label will ensure that all PTP packets in one
direction <br>
&gt; &gt; follow the same path. <br>
&gt; [Lizhong] since control word is required for 1588 over PW <br>
&gt; encapsulation, if without entropy label, all PTP packets in one <br>
&gt; direction will also follow the same path. &nbsp;</font></tt>
<br><tt><font size=2>&gt; &nbsp;</font></tt>
<br><tt><font size=2>&gt; [Manav] I think we must use a stronger language
in Sec 5.2 regarding<br>
&gt; using control word. I think i will concur with you here that if CW
<br>
&gt; is being used then we may not need an entropy label. However, i dont<br>
&gt; see a strong reason why we should restrict it. The current draft <br>
&gt; says that control word usage is optional and i dont find any issue
<br>
&gt; with that. Do you?</font></tt>
<br><tt><font size=2>[Lizhong] the current draft says control word SHOULD
be used. And yes, stronger language is welcome.</font></tt>
<br>
<br><tt><font size=2>&gt; &nbsp;</font></tt>
<br><tt><font size=2>&gt; &gt; <br>
&gt; &gt; &gt; If there is entropy label, it is possible that the forward<br>
&gt; &gt; &gt; and reverse path would be different.<br>
&gt; &gt; <br>
&gt; &gt; Since LSPs are unidirectional there is no guarantee that the
two paths <br>
&gt; &gt; would be symmetrical. So this really is an issue orthogonal to
the use <br>
&gt; &gt; of entropy labels for carrying PTP traffic.<br>
&gt; &gt; <br>
&gt; &gt; We should probably add some text in the draft that says that
the two <br>
&gt; &gt; paths must be symmetrical. <br>
&gt; [Lizhong] If there is a boundled interface between two LSRs, the <br>
&gt; control plane will only see one logical interface. Then it is still
<br>
&gt; possible the forward and reverse path be different at the physical
<br>
&gt; level in ECMP case. <br>
&gt; &nbsp;</font></tt>
<br><tt><font size=2>&gt; [Manav] Is the assumption that the two ends of
LAG could be <br>
&gt; connected to two different systems, something like a multi-chassis
<br>
&gt; lag? I am not sure if there is much that we can do about this except<br>
&gt; add a note against such a form of load distribution in the document.</font></tt>
<br><tt><font size=2>[Lizhong] I mean the LAG between two end-points, not
MC-LAG. E.g, one LAG interface with physical link A &amp; B between two
end-points, it is possible that the forward path will go through A, and
backward path will go through B, then the physical path is not symmetric.
If I understand correctly, you just assume the transport delay on link
A &amp; B are the same, but this is not always true, especially for the
composite link defined in RTGWG (draft-ietf-rtgwg-cl-requirement).</font></tt>
<br>
<br><tt><font size=2>&gt; <br>
&gt; Cheers, Manav</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 00598F2448257825_=--


From manav.bhatia@alcatel-lucent.com  Thu Jan 27 16:07:03 2011
Return-Path: <manav.bhatia@alcatel-lucent.com>
X-Original-To: tictoc@core3.amsl.com
Delivered-To: tictoc@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 06ABD3A6AED for <tictoc@core3.amsl.com>; Thu, 27 Jan 2011 16:07:03 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.29
X-Spam-Level: 
X-Spam-Status: No, score=-6.29 tagged_above=-999 required=5 tests=[AWL=0.309,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id wi0KTzdEyJ9t for <tictoc@core3.amsl.com>; Thu, 27 Jan 2011 16:07:02 -0800 (PST)
Received: from ihemail1.lucent.com (ihemail1.lucent.com [135.245.0.33]) by core3.amsl.com (Postfix) with ESMTP id 2F2943A6AEB for <tictoc@ietf.org>; Thu, 27 Jan 2011 16:06:58 -0800 (PST)
Received: from inbansmailrelay1.in.alcatel-lucent.com (h135-250-11-31.lucent.com [135.250.11.31]) by ihemail1.lucent.com (8.13.8/IER-o) with ESMTP id p0S09tax018502 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Thu, 27 Jan 2011 18:09:58 -0600 (CST)
Received: from INBANSXCHHUB01.in.alcatel-lucent.com (inbansxchhub01.in.alcatel-lucent.com [135.250.12.32]) by inbansmailrelay1.in.alcatel-lucent.com (8.14.3/8.14.3/GMO) with ESMTP id p0S09sRP020014 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Fri, 28 Jan 2011 05:39:55 +0530
Received: from INBANSXCHMBSA1.in.alcatel-lucent.com ([135.250.12.56]) by INBANSXCHHUB01.in.alcatel-lucent.com ([135.250.12.32]) with mapi; Fri, 28 Jan 2011 05:39:54 +0530
From: "Bhatia, Manav (Manav)" <manav.bhatia@alcatel-lucent.com>
To: "lizhong.jin@zte.com.cn" <lizhong.jin@zte.com.cn>
Date: Fri, 28 Jan 2011 05:39:50 +0530
Thread-Topic: [TICTOC] Transporting PTP messages (1588) over MPLS Networks
Thread-Index: Acu+PdUC7kONJSDySYqAJav1yRP/fQAP4qjw
Message-ID: <7C362EEF9C7896468B36C9B79200D8350CFB18B851@INBANSXCHMBSA1.in.alcatel-lucent.com>
References: <7C362EEF9C7896468B36C9B79200D8350CFB18B739@INBANSXCHMBSA1.in.alcatel-lucent.com> <OF38C7CAD6.A42B741E-ON48257825.0056C504-48257825.00598F25@zte.com.cn>
In-Reply-To: <OF38C7CAD6.A42B741E-ON48257825.0056C504-48257825.00598F25@zte.com.cn>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Scanned-By: MIMEDefang 2.57 on 135.245.2.33
X-Scanned-By: MIMEDefang 2.64 on 135.250.11.31
Cc: "tictoc@ietf.org" <tictoc@ietf.org>
Subject: Re: [TICTOC] Transporting PTP messages (1588) over MPLS Networks
X-BeenThere: tictoc@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Timing over IP Connection and Transfer of Clock BOF <tictoc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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, 28 Jan 2011 00:07:03 -0000

Lizhong,
=20
> [Lizhong] I mean the LAG between two end-points,=20
> not MC-LAG. E.g, one LAG interface with physical link=20
> A & B between two end-points, it is possible that the forward=20
> path will go through A, and backward path will go through B,=20
> then the physical path is not symmetric. If I understand correctly,=20
> you just assume the transport delay on link A & B are the=20

On an ordinary lag, unless it's a MC-LAG this can be assumed to be more or =
less the same.

> same, but this is not always true, especially for the composite=20
> link defined in RTGWG (draft-ietf-rtgwg-cl-requirement).=20

I quickly glanced through this draft and these can imo be easily avoided by=
 defining a new link type - Composite link, in the link type sub-TLV of Lin=
k TLV in OSPF [RFC3630]. Such links MUST be avoided for setting up the PTP =
LSPs. Similarly the extended IS reachability TLV could be extended for IS-I=
S to avoid composite links.

One could also use coloring to avoid these links, but this would entail man=
ual configuration which may not be desirable.

Cheers, Manav

From kohn.jack@gmail.com  Thu Jan 27 18:25:54 2011
Return-Path: <kohn.jack@gmail.com>
X-Original-To: tictoc@core3.amsl.com
Delivered-To: tictoc@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 04D2C3A6B72 for <tictoc@core3.amsl.com>; Thu, 27 Jan 2011 18:25:54 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.226
X-Spam-Level: 
X-Spam-Status: No, score=-3.226 tagged_above=-999 required=5 tests=[AWL=0.373,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id UU5Z+qOoQkfd for <tictoc@core3.amsl.com>; Thu, 27 Jan 2011 18:25:52 -0800 (PST)
Received: from mail-iw0-f172.google.com (mail-iw0-f172.google.com [209.85.214.172]) by core3.amsl.com (Postfix) with ESMTP id 324953A6B6F for <tictoc@ietf.org>; Thu, 27 Jan 2011 18:25:52 -0800 (PST)
Received: by iwn40 with SMTP id 40so2875448iwn.31 for <tictoc@ietf.org>; Thu, 27 Jan 2011 18:28:57 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=dei26hEaKyLQCm+2q61Y3fIqjN4WvMe2nn35kV+UXSU=; b=MmcM+LfW4mdQEeloAgi6vVkO//Kk8W/p45urOL0h+b6BwjIdhHoGGJipwekTFK34k2 mo4C+gxovXiYJUda8rRkVZmhJYhRMuJ/JAdjGdzDxoGeVEBJoogOnu07WeynlQZC7KqA /TW0U8RCEQypqcmGwn6KOiuWGTDjNt4Z6fRVc=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=Q6TZIz4gf7iQcPjzsZGy3FOnADgo1gQXDWFJjHnwKMI+PRfbU6ZMW4TaeDzYHK9AKM CnmFY86SpORmJPay6FImvDF5zhi6YUrDRO/xXFd+cH9bqjhcqEWym4eEGpYWMkqKfoUQ Cx5/owE6Gcu4F04kkjJI4Ufn7utw5nXhOfBSo=
MIME-Version: 1.0
Received: by 10.231.153.195 with SMTP id l3mr1930970ibw.150.1296181737071; Thu, 27 Jan 2011 18:28:57 -0800 (PST)
Received: by 10.231.200.148 with HTTP; Thu, 27 Jan 2011 18:28:56 -0800 (PST)
In-Reply-To: <7C362EEF9C7896468B36C9B79200D8350CFB18B54D@INBANSXCHMBSA1.in.alcatel-lucent.com>
References: <7C362EEF9C7896468B36C9B79200D8350CFB0DFDA7@INBANSXCHMBSA1.in.alcatel-lucent.com> <2C2F1EBA8050E74EA81502D5740B4BD6941B04CC39@SJEXCHCCR02.corp.ad.broadcom.com> <7C362EEF9C7896468B36C9B79200D8350CFB0DFDAA@INBANSXCHMBSA1.in.alcatel-lucent.com> <2C2F1EBA8050E74EA81502D5740B4BD6941B04CC6D@SJEXCHCCR02.corp.ad.broadcom.com> <4D39EC31.10602@cisco.com> <01E54480-7D98-46F8-B82A-21A178044512@americafree.tv> <07F7D7DED63154409F13298786A2ADC903CD929B@EXRAD5.ad.rad.co.il> <7C362EEF9C7896468B36C9B79200D8350CFB18B54D@INBANSXCHMBSA1.in.alcatel-lucent.com>
Date: Fri, 28 Jan 2011 07:58:56 +0530
Message-ID: <AANLkTinidte6enZ_ZYqpPcabdnCzRH5yeK_MoagKJbNv@mail.gmail.com>
From: Jack Kohn <kohn.jack@gmail.com>
To: "Bhatia, Manav (Manav)" <manav.bhatia@alcatel-lucent.com>
Content-Type: text/plain; charset=ISO-8859-1
Cc: "tictoc@ietf.org" <tictoc@ietf.org>
Subject: Re: [TICTOC] UDP checksum
X-BeenThere: tictoc@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Timing over IP Connection and Transfer of Clock BOF <tictoc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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, 28 Jan 2011 02:25:54 -0000

On Thu, Jan 27, 2011 at 6:24 AM, Bhatia, Manav (Manav)
<manav.bhatia@alcatel-lucent.com> wrote:
> Yakov,
>
>> Actually, I think Stewart was referring to
>> http://tools.ietf.org/html/draft-ietf-6lowpan-hc-13 .
>>
>> If there are several proposals on the table, albeit for special cases,
>> to make the UDP checksum optional, then we can propose that
>> operation too.
>
> Alternatively, we could just keep this within our WG and add the following to the 1588oMPLS draft:
>
> LSRs that adjust the CF field MAY not update the UDP checksum in case of IPv6. The node that terminates the tunnel MUST recompute the UDP checksum after MPLS decapsulation and before any further processing.

I would prefer this over a proposal for deprecating UDP checksum for IPv6.

Each 1588aware LSR that updates the CF is anyways updating the
ethernet FCS, which should be good enough to verify the basic
integrity of the packet.

My 0.02$

Jack

From ronc.ntear@gmail.com  Fri Jan 28 01:22:01 2011
Return-Path: <ronc.ntear@gmail.com>
X-Original-To: tictoc@core3.amsl.com
Delivered-To: tictoc@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 7C95A3A6B07 for <tictoc@core3.amsl.com>; Fri, 28 Jan 2011 01:22:01 -0800 (PST)
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.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id f7TIlC+yiR2Q for <tictoc@core3.amsl.com>; Fri, 28 Jan 2011 01:21:58 -0800 (PST)
Received: from mail-ww0-f44.google.com (mail-ww0-f44.google.com [74.125.82.44]) by core3.amsl.com (Postfix) with ESMTP id 93AF13A6AE0 for <tictoc@ietf.org>; Fri, 28 Jan 2011 01:21:57 -0800 (PST)
Received: by wwa36 with SMTP id 36so3461064wwa.13 for <tictoc@ietf.org>; Fri, 28 Jan 2011 01:25:02 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=uq3rQ0YemLK9YOGpjpoxnbEC8+VFhY7Qc8DJ1KPdI7c=; b=mVj/H50fJ1N39sTlxmH6xyY2HJqkSg7V/XTT3dp9kJ5TjfRLk4pZasEboIPvIFR0qB 8QzMG+acNWvIAKKvC5Dp7dBFcNyKNJBTODZeWCT5fdwE2oJOyzRv2jFrlXpnPp8MAc8U +VXJdRWydV9nITbKXJRwlz1B2Xlun6heEen9c=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=e0z2Ws0YTsaiuN/tNRgk5k+HWY4eug1lpSO5GH6TbsvVNQHUD3cWIYnlhHU1fHshcF Ght/rbKBH9UFXzVBQnX+Td4R/giv20KovC8zRkAtIwLiUTwk8cQBXfDcrO//NruMnr+W zhgTtLya7IaSH7XxpWimguPuQUCuXQOUQWEZI=
MIME-Version: 1.0
Received: by 10.216.65.16 with SMTP id e16mr2770528wed.73.1296206702374; Fri, 28 Jan 2011 01:25:02 -0800 (PST)
Received: by 10.216.167.69 with HTTP; Fri, 28 Jan 2011 01:25:02 -0800 (PST)
In-Reply-To: <AANLkTinidte6enZ_ZYqpPcabdnCzRH5yeK_MoagKJbNv@mail.gmail.com>
References: <7C362EEF9C7896468B36C9B79200D8350CFB0DFDA7@INBANSXCHMBSA1.in.alcatel-lucent.com> <2C2F1EBA8050E74EA81502D5740B4BD6941B04CC39@SJEXCHCCR02.corp.ad.broadcom.com> <7C362EEF9C7896468B36C9B79200D8350CFB0DFDAA@INBANSXCHMBSA1.in.alcatel-lucent.com> <2C2F1EBA8050E74EA81502D5740B4BD6941B04CC6D@SJEXCHCCR02.corp.ad.broadcom.com> <4D39EC31.10602@cisco.com> <01E54480-7D98-46F8-B82A-21A178044512@americafree.tv> <07F7D7DED63154409F13298786A2ADC903CD929B@EXRAD5.ad.rad.co.il> <7C362EEF9C7896468B36C9B79200D8350CFB18B54D@INBANSXCHMBSA1.in.alcatel-lucent.com> <AANLkTinidte6enZ_ZYqpPcabdnCzRH5yeK_MoagKJbNv@mail.gmail.com>
Date: Fri, 28 Jan 2011 11:25:02 +0200
Message-ID: <AANLkTikXN=xA82pyNH+7mkwEhYrOV+J+OR8Kicc401z5@mail.gmail.com>
From: Ron Cohen <ronc.ntear@gmail.com>
To: Jack Kohn <kohn.jack@gmail.com>
Content-Type: multipart/alternative; boundary=000e0ce0424a0cf01b049ae4a411
Cc: "tictoc@ietf.org" <tictoc@ietf.org>
Subject: Re: [TICTOC] UDP checksum
X-BeenThere: tictoc@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Timing over IP Connection and Transfer of Clock BOF <tictoc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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, 28 Jan 2011 09:22:01 -0000

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

Hi Jack,

I don't think it is a good idea. In my opinion we should not / can not
specify that packets with wrong UDP checksum will be sent on the wire.

Best,
Ron

On Fri, Jan 28, 2011 at 4:28 AM, Jack Kohn <kohn.jack@gmail.com> wrote:

> On Thu, Jan 27, 2011 at 6:24 AM, Bhatia, Manav (Manav)
> <manav.bhatia@alcatel-lucent.com> wrote:
> > Yakov,
> >
> >> Actually, I think Stewart was referring to
> >> http://tools.ietf.org/html/draft-ietf-6lowpan-hc-13 .
> >>
> >> If there are several proposals on the table, albeit for special cases,
> >> to make the UDP checksum optional, then we can propose that
> >> operation too.
> >
> > Alternatively, we could just keep this within our WG and add the
> following to the 1588oMPLS draft:
> >
> > LSRs that adjust the CF field MAY not update the UDP checksum in case of
> IPv6. The node that terminates the tunnel MUST recompute the UDP checksum
> after MPLS decapsulation and before any further processing.
>
> I would prefer this over a proposal for deprecating UDP checksum for IPv6.
>
> Each 1588aware LSR that updates the CF is anyways updating the
> ethernet FCS, which should be good enough to verify the basic
> integrity of the packet.
>
> My 0.02$
>
> Jack
> _______________________________________________
> TICTOC mailing list
> TICTOC@ietf.org
> https://www.ietf.org/mailman/listinfo/tictoc
>

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

<div dir=3D"ltr">Hi Jack,<br><br>I don&#39;t think it is a good idea. In my=
 opinion we should not / can not specify that packets with wrong UDP checks=
um will be sent on the wire. <br><br>Best,<br>Ron <br><br><div class=3D"gma=
il_quote">
On Fri, Jan 28, 2011 at 4:28 AM, Jack Kohn <span dir=3D"ltr">&lt;<a href=3D=
"mailto:kohn.jack@gmail.com">kohn.jack@gmail.com</a>&gt;</span> wrote:<br><=
blockquote class=3D"gmail_quote" style=3D"margin: 0pt 0pt 0pt 0.8ex; border=
-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<div class=3D"im">On Thu, Jan 27, 2011 at 6:24 AM, Bhatia, Manav (Manav)<br=
>
&lt;<a href=3D"mailto:manav.bhatia@alcatel-lucent.com">manav.bhatia@alcatel=
-lucent.com</a>&gt; wrote:<br>
&gt; Yakov,<br>
&gt;<br>
&gt;&gt; Actually, I think Stewart was referring to<br>
&gt;&gt; <a href=3D"http://tools.ietf.org/html/draft-ietf-6lowpan-hc-13" ta=
rget=3D"_blank">http://tools.ietf.org/html/draft-ietf-6lowpan-hc-13</a> .<b=
r>
&gt;&gt;<br>
&gt;&gt; If there are several proposals on the table, albeit for special ca=
ses,<br>
&gt;&gt; to make the UDP checksum optional, then we can propose that<br>
&gt;&gt; operation too.<br>
&gt;<br>
&gt; Alternatively, we could just keep this within our WG and add the follo=
wing to the 1588oMPLS draft:<br>
&gt;<br>
&gt; LSRs that adjust the CF field MAY not update the UDP checksum in case =
of IPv6. The node that terminates the tunnel MUST recompute the UDP checksu=
m after MPLS decapsulation and before any further processing.<br>
<br>
</div>I would prefer this over a proposal for deprecating UDP checksum for =
IPv6.<br>
<br>
Each 1588aware LSR that updates the CF is anyways updating the<br>
ethernet FCS, which should be good enough to verify the basic<br>
integrity of the packet.<br>
<br>
My 0.02$<br>
<font color=3D"#888888"><br>
Jack<br>
</font><div><div></div><div class=3D"h5">__________________________________=
_____________<br>
TICTOC mailing list<br>
<a href=3D"mailto:TICTOC@ietf.org">TICTOC@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/tictoc" target=3D"_blank">=
https://www.ietf.org/mailman/listinfo/tictoc</a><br>
</div></div></blockquote></div><br><div style=3D"visibility: hidden; left: =
-5000px; position: absolute; z-index: 9999; padding: 0px; margin-left: 0px;=
 margin-top: 0px; overflow: hidden; word-wrap: break-word; color: black; fo=
nt-size: 10px; text-align: left; line-height: 130%;" id=3D"avg_ls_inline_po=
pup">
</div></div>

--000e0ce0424a0cf01b049ae4a411--

From talmi@marvell.com  Fri Jan 28 04:26:38 2011
Return-Path: <talmi@marvell.com>
X-Original-To: tictoc@core3.amsl.com
Delivered-To: tictoc@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 10ACB3A67A6 for <tictoc@core3.amsl.com>; Fri, 28 Jan 2011 04:26:38 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.363
X-Spam-Level: 
X-Spam-Status: No, score=-6.363 tagged_above=-999 required=5 tests=[AWL=0.235,  BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id pjhHGeOED-O2 for <tictoc@core3.amsl.com>; Fri, 28 Jan 2011 04:26:36 -0800 (PST)
Received: from na3sys009aog106.obsmtp.com (na3sys009aog106.obsmtp.com [74.125.149.77]) by core3.amsl.com (Postfix) with ESMTP id 2D64D3A672F for <tictoc@ietf.org>; Fri, 28 Jan 2011 04:26:34 -0800 (PST)
Received: from source ([65.219.4.130]) (using TLSv1) by na3sys009aob106.postini.com ([74.125.148.12]) with SMTP ID DSNKTUK2tFuscWd9U2Pt30anvVFHcBw6HMA+@postini.com; Fri, 28 Jan 2011 04:29:43 PST
Received: from YK-HUB02.marvell.com (10.4.102.52) by sc-owa02.marvell.com (10.93.76.22) with Microsoft SMTP Server (TLS) id 8.2.213.0; Fri, 28 Jan 2011 04:27:55 -0800
Received: from IL-MB01.marvell.com ([10.4.102.53]) by YK-HUB02.marvell.com ([10.4.102.52]) with mapi; Fri, 28 Jan 2011 14:27:52 +0200
From: Tal Mizrahi <talmi@marvell.com>
To: Ron Cohen <ronc.ntear@gmail.com>, Jack Kohn <kohn.jack@gmail.com>, "tictoc@ietf.org" <tictoc@ietf.org>
Date: Fri, 28 Jan 2011 14:22:59 +0200
Thread-Topic: [TICTOC] UDP checksum
Thread-Index: Acu+zUVscx+8X411RfSdphKl8mjviQAGNS1x
Message-ID: <74470498B659FA4687F0B0018C19A89CFCDC097408@IL-MB01.marvell.com>
References: <7C362EEF9C7896468B36C9B79200D8350CFB0DFDA7@INBANSXCHMBSA1.in.alcatel-lucent.com> <2C2F1EBA8050E74EA81502D5740B4BD6941B04CC39@SJEXCHCCR02.corp.ad.broadcom.com> <7C362EEF9C7896468B36C9B79200D8350CFB0DFDAA@INBANSXCHMBSA1.in.alcatel-lucent.com> <2C2F1EBA8050E74EA81502D5740B4BD6941B04CC6D@SJEXCHCCR02.corp.ad.broadcom.com> <4D39EC31.10602@cisco.com> <01E54480-7D98-46F8-B82A-21A178044512@americafree.tv> <07F7D7DED63154409F13298786A2ADC903CD929B@EXRAD5.ad.rad.co.il> <7C362EEF9C7896468B36C9B79200D8350CFB18B54D@INBANSXCHMBSA1.in.alcatel-lucent.com> <AANLkTinidte6enZ_ZYqpPcabdnCzRH5yeK_MoagKJbNv@mail.gmail.com>, <AANLkTikXN=xA82pyNH+7mkwEhYrOV+J+OR8Kicc401z5@mail.gmail.com>
In-Reply-To: <AANLkTikXN=xA82pyNH+7mkwEhYrOV+J+OR8Kicc401z5@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: multipart/alternative; boundary="_000_74470498B659FA4687F0B0018C19A89CFCDC097408ILMB01marvell_"
MIME-Version: 1.0
Subject: Re: [TICTOC] UDP checksum
X-BeenThere: tictoc@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Timing over IP Connection and Transfer of Clock BOF <tictoc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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, 28 Jan 2011 12:26:38 -0000

--_000_74470498B659FA4687F0B0018C19A89CFCDC097408ILMB01marvell_
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable


On Friday, January 28, 2011 11:25 AM, Ron Cohen [ronc.ntear@gmail.com] wrot=
e:
> I don't think it is a good idea. In my opinion we should not / can not sp=
ecify that packets with wrong UDP
> checksum will be sent on the wire.

I agree with Ron.
Furthermore: one of the main goals of the current draft is "a generic metho=
d is defined in this document that does not require deep packet inspection =
at line rate".
The suggestion to have the tunnel termination point recompute the UDP check=
sum requires complex line rate processing at the egress LER, which may be a=
 TC itslef.
I believe an incremental checksum update at every LSR is far simpler than r=
ecomputing the checksum at the LER.

A fair alternative is to update rfc2460, and to allow UDP checksum=3D0 (i.e=
., no checksum) for IPv6, very similar to UDP over IPv4.
Of course this goes beyond the scope of TICTOC, but is probably the best al=
ternative.

Regards,
Tal.

________________________________
From: tictoc-bounces@ietf.org [tictoc-bounces@ietf.org] On Behalf Of Ron Co=
hen [ronc.ntear@gmail.com]
Sent: Friday, January 28, 2011 11:25 AM
To: Jack Kohn
Cc: tictoc@ietf.org
Subject: Re: [TICTOC] UDP checksum

Hi Jack,

I don't think it is a good idea. In my opinion we should not / can not spec=
ify that packets with wrong UDP checksum will be sent on the wire.

Best,
Ron

On Fri, Jan 28, 2011 at 4:28 AM, Jack Kohn <kohn.jack@gmail.com<mailto:kohn=
.jack@gmail.com>> wrote:
On Thu, Jan 27, 2011 at 6:24 AM, Bhatia, Manav (Manav)
<manav.bhatia@alcatel-lucent.com<mailto:manav.bhatia@alcatel-lucent.com>> w=
rote:
> Yakov,
>
>> Actually, I think Stewart was referring to
>> http://tools.ietf.org/html/draft-ietf-6lowpan-hc-13 .
>>
>> If there are several proposals on the table, albeit for special cases,
>> to make the UDP checksum optional, then we can propose that
>> operation too.
>
> Alternatively, we could just keep this within our WG and add the followin=
g to the 1588oMPLS draft:
>
> LSRs that adjust the CF field MAY not update the UDP checksum in case of =
IPv6. The node that terminates the tunnel MUST recompute the UDP checksum a=
fter MPLS decapsulation and before any further processing.

I would prefer this over a proposal for deprecating UDP checksum for IPv6.

Each 1588aware LSR that updates the CF is anyways updating the
ethernet FCS, which should be good enough to verify the basic
integrity of the packet.

My 0.02$

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


--_000_74470498B659FA4687F0B0018C19A89CFCDC097408ILMB01marvell_
Content-Type: text/html; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<html dir=3D"ltr"><head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Diso-8859-=
1">
<meta name=3D"GENERATOR" content=3D"MSHTML 8.00.7600.16700">
<style title=3D"owaParaStyle">P {
	MARGIN-TOP: 0px; MARGIN-BOTTOM: 0px
}
</style>
</head>
<body ocsi=3D"x">
<div dir=3D"ltr"><font color=3D"#000000" size=3D"2" face=3D"Tahoma"></font>=
&nbsp;</div>
<div dir=3D"ltr"><font face=3D"Tahoma"><font size=3D"2">On Friday, January =
28, 2011 11:25 AM, Ron Cohen [ronc.ntear@gmail.com] wrote:<br>
<font color=3D"#000000">&gt; I don't think it is a good idea. In my opinion=
 we should not / can not specify that packets with wrong UDP</font></font><=
/font></div>
<div dir=3D"ltr"><font color=3D"#000000" size=3D"2" face=3D"Tahoma">&gt;&nb=
sp;checksum will be sent on the wire.</font></div>
<div dir=3D"ltr"><font size=3D"2" face=3D"Tahoma"></font>&nbsp;</div>
<div dir=3D"ltr"><font color=3D"#000000" size=3D"2" face=3D"Tahoma">I agree=
 with Ron.<br>
Furthermore: one of the main goals of the current draft is &quot;a generic =
method is defined in this document that does not require deep packet inspec=
tion at line rate&quot;.<br>
The suggestion to have the tunnel termination point recompute the UDP check=
sum requires complex line rate&nbsp;processing at the egress LER, which may=
 be a TC itslef.<br>
I believe an incremental checksum update at every LSR is far simpler than r=
ecomputing the checksum at the LER.</font></div>
<div dir=3D"ltr"><font size=3D"2" face=3D"tahoma"></font>&nbsp;</div>
<div dir=3D"ltr"><font color=3D"#000000" size=3D"2" face=3D"Tahoma">A fair =
alternative is to update rfc2460, and to allow UDP checksum=3D0 (i.e., no c=
hecksum)&nbsp;for IPv6, very similar to UDP over IPv4.<br>
Of course this goes beyond the scope of TICTOC, but is probably the best al=
ternative.</font></div>
<div dir=3D"ltr"><font size=3D"2" face=3D"Tahoma"></font>&nbsp;</div>
<font size=3D"2" face=3D"Tahoma">
<div dir=3D"ltr">Regards,<br>
Tal.</div>
<div dir=3D"ltr"></font>&nbsp;</div>
<div style=3D"DIRECTION: ltr" id=3D"divRpF443342">
<hr tabindex=3D"-1">
<font size=3D"2" face=3D"Tahoma"><b>From:</b> tictoc-bounces@ietf.org [tict=
oc-bounces@ietf.org] On Behalf Of Ron Cohen [ronc.ntear@gmail.com]<br>
<b>Sent:</b> Friday, January 28, 2011 11:25 AM<br>
<b>To:</b> Jack Kohn<br>
<b>Cc:</b> tictoc@ietf.org<br>
<b>Subject:</b> Re: [TICTOC] UDP checksum<br>
</font><br>
</div>
<div></div>
<div>
<div dir=3D"ltr">Hi Jack,<br>
<br>
I don't think it is a good idea. In my opinion we should not / can not spec=
ify that packets with wrong UDP checksum will be sent on the wire.
<br>
<br>
Best,<br>
Ron <br>
<br>
<div class=3D"gmail_quote">On Fri, Jan 28, 2011 at 4:28 AM, Jack Kohn <span=
 dir=3D"ltr">
&lt;<a href=3D"mailto:kohn.jack@gmail.com">kohn.jack@gmail.com</a>&gt;</spa=
n> wrote:<br>
<blockquote style=3D"BORDER-LEFT: rgb(204,204,204) 1px solid; MARGIN: 0pt 0=
pt 0pt 0.8ex; PADDING-LEFT: 1ex" class=3D"gmail_quote">
<div class=3D"im">On Thu, Jan 27, 2011 at 6:24 AM, Bhatia, Manav (Manav)<br=
>
&lt;<a href=3D"mailto:manav.bhatia@alcatel-lucent.com">manav.bhatia@alcatel=
-lucent.com</a>&gt; wrote:<br>
&gt; Yakov,<br>
&gt;<br>
&gt;&gt; Actually, I think Stewart was referring to<br>
&gt;&gt; <a href=3D"http://tools.ietf.org/html/draft-ietf-6lowpan-hc-13" ta=
rget=3D"_blank">
http://tools.ietf.org/html/draft-ietf-6lowpan-hc-13</a> .<br>
&gt;&gt;<br>
&gt;&gt; If there are several proposals on the table, albeit for special ca=
ses,<br>
&gt;&gt; to make the UDP checksum optional, then we can propose that<br>
&gt;&gt; operation too.<br>
&gt;<br>
&gt; Alternatively, we could just keep this within our WG and add the follo=
wing to the 1588oMPLS draft:<br>
&gt;<br>
&gt; LSRs that adjust the CF field MAY not update the UDP checksum in case =
of IPv6. The node that terminates the tunnel MUST recompute the UDP checksu=
m after MPLS decapsulation and before any further processing.<br>
<br>
</div>
I would prefer this over a proposal for deprecating UDP checksum for IPv6.<=
br>
<br>
Each 1588aware LSR that updates the CF is anyways updating the<br>
ethernet FCS, which should be good enough to verify the basic<br>
integrity of the packet.<br>
<br>
My 0.02$<br>
<font color=3D"#888888"><br>
Jack<br>
</font>
<div>
<div></div>
<div class=3D"h5">_______________________________________________<br>
TICTOC mailing list<br>
<a href=3D"mailto:TICTOC@ietf.org">TICTOC@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/tictoc" target=3D"_blank">=
https://www.ietf.org/mailman/listinfo/tictoc</a><br>
</div>
</div>
</blockquote>
</div>
<br>
<div style=3D"Z-INDEX: 9999; POSITION: absolute; TEXT-ALIGN: left; PADDING-=
BOTTOM: 0px; LINE-HEIGHT: 130%; MARGIN-TOP: 0px; PADDING-LEFT: 0px; PADDING=
-RIGHT: 0px; WORD-WRAP: break-word; VISIBILITY: hidden; COLOR: black; MARGI=
N-LEFT: 0px; FONT-SIZE: 10px; OVERFLOW: hidden; PADDING-TOP: 0px; LEFT: -50=
00px" id=3D"avg_ls_inline_popup">
</div>
</div>
</div>
</body>
</html>

--_000_74470498B659FA4687F0B0018C19A89CFCDC097408ILMB01marvell_--

From lizhong.jin@zte.com.cn  Sun Jan 30 16:37:25 2011
Return-Path: <lizhong.jin@zte.com.cn>
X-Original-To: tictoc@core3.amsl.com
Delivered-To: tictoc@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 75B9F3A68EA for <tictoc@core3.amsl.com>; Sun, 30 Jan 2011 16:37:25 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.598
X-Spam-Level: 
X-Spam-Status: No, score=-101.598 tagged_above=-999 required=5 tests=[AWL=0.240, 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.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id qYPGJbHn6D0m for <tictoc@core3.amsl.com>; Sun, 30 Jan 2011 16:37:23 -0800 (PST)
Received: from mx5.zte.com.cn (mx5.zte.com.cn [63.217.80.70]) by core3.amsl.com (Postfix) with ESMTP id 4A96C3A68BF for <tictoc@ietf.org>; Sun, 30 Jan 2011 16:37:23 -0800 (PST)
Received: from [10.30.17.99] by mx5.zte.com.cn with surfront esmtp id 205951930506506; Mon, 31 Jan 2011 08:35:58 +0800 (CST)
Received: from [10.30.3.20] by [192.168.168.15] with StormMail ESMTP id 96520.3711756443; Mon, 31 Jan 2011 08:40:30 +0800 (CST)
Received: from notes_smtp.zte.com.cn ([10.30.1.239]) by mse01.zte.com.cn with ESMTP id p0V0eQu5003225; Mon, 31 Jan 2011 08:40:26 +0800 (GMT-8) (envelope-from lizhong.jin@zte.com.cn)
In-Reply-To: <7C362EEF9C7896468B36C9B79200D8350CFB18B851@INBANSXCHMBSA1.in.alcatel-lucent.com>
To: "Bhatia, Manav (Manav)" <manav.bhatia@alcatel-lucent.com>
MIME-Version: 1.0
X-Mailer: Lotus Notes Release 6.5.6 March 06, 2007
Message-ID: <OF0D6CBFC6.7105F2FD-ON48257829.00038FF3-48257829.0003B340@zte.com.cn>
From: lizhong.jin@zte.com.cn
Date: Mon, 31 Jan 2011 08:39:46 +0800
X-MIMETrack: S/MIME Sign by Notes Client on JinLiZhong127666/user/zte_ltd(Release 6.5.6|March 06, 2007) at 2011-01-31 08:40:24, Serialize by Notes Client on JinLiZhong127666/user/zte_ltd(Release 6.5.6|March 06, 2007) at 2011-01-31 08:40:24, Serialize complete at 2011-01-31 08:40:24, S/MIME Sign failed at 2011-01-31 08:40:25: The cryptographic key was not found, Serialize by Router on notes_smtp/zte_ltd(Release 8.5.1FP4|July 25, 2010) at 2011-01-31 08:40:25, Serialize complete at 2011-01-31 08:40:25
Content-Type: multipart/alternative; boundary="=_alternative 0003B33D48257829_="
X-MAIL: mse01.zte.com.cn p0V0eQu5003225
Cc: "tictoc@ietf.org" <tictoc@ietf.org>
Subject: Re: [TICTOC] Transporting PTP messages (1588) over MPLS Networks
X-BeenThere: tictoc@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Timing over IP Connection and Transfer of Clock BOF <tictoc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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, 31 Jan 2011 00:37:25 -0000

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

Hi Manav,
I see the discussion at RTGWG, it is good.
Share within TICTOC: 
http://www.ietf.org/mail-archive/web/rtgwg/current/msg03181.html

Thanks
Lizhong
 

"Bhatia, Manav (Manav)" <manav.bhatia@alcatel-lucent.com> wrote on 
2011-01-28 08:09:50:

> Lizhong,
> 
> > [Lizhong] I mean the LAG between two end-points, 
> > not MC-LAG. E.g, one LAG interface with physical link 
> > A & B between two end-points, it is possible that the forward 
> > path will go through A, and backward path will go through B, 
> > then the physical path is not symmetric. If I understand correctly, 
> > you just assume the transport delay on link A & B are the 
> 
> On an ordinary lag, unless it's a MC-LAG this can be assumed to be 
> more or less the same.
> 
> > same, but this is not always true, especially for the composite 
> > link defined in RTGWG (draft-ietf-rtgwg-cl-requirement). 
> 
> I quickly glanced through this draft and these can imo be easily 
> avoided by defining a new link type - Composite link, in the link 
> type sub-TLV of Link TLV in OSPF [RFC3630]. Such links MUST be 
> avoided for setting up the PTP LSPs. Similarly the extended IS 
> reachability TLV could be extended for IS-IS to avoid composite links.
> 
> One could also use coloring to avoid these links, but this would 
> entail manual configuration which may not be desirable.
> 
> Cheers, Manav
> 


--------------------------------------------------------
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 0003B33D48257829_=
Content-Type: text/html; charset="US-ASCII"


<br><font size=2 face="sans-serif">Hi Manav,</font>
<br><font size=2 face="sans-serif">I see the discussion at RTGWG, it is
good.</font>
<br><font size=2 face="sans-serif">Share within TICTOC: http://www.ietf.org/mail-archive/web/rtgwg/current/msg03181.html</font>
<br>
<br><font size=2 face="sans-serif">Thanks</font>
<br><font size=2 face="sans-serif">Lizhong</font>
<br><font size=1 face="Arial">&nbsp;</font>
<br>
<br><tt><font size=2>&quot;Bhatia, Manav (Manav)&quot; &lt;manav.bhatia@alcatel-lucent.com&gt;
wrote on 2011-01-28 08:09:50:<br>
<br>
&gt; Lizhong,<br>
&gt; &nbsp;<br>
&gt; &gt; [Lizhong] I mean the LAG between two end-points, <br>
&gt; &gt; not MC-LAG. E.g, one LAG interface with physical link <br>
&gt; &gt; A &amp; B between two end-points, it is possible that the forward
<br>
&gt; &gt; path will go through A, and backward path will go through B,
<br>
&gt; &gt; then the physical path is not symmetric. If I understand correctly,
<br>
&gt; &gt; you just assume the transport delay on link A &amp; B are the
<br>
&gt; <br>
&gt; On an ordinary lag, unless it's a MC-LAG this can be assumed to be
<br>
&gt; more or less the same.<br>
&gt; <br>
&gt; &gt; same, but this is not always true, especially for the composite
<br>
&gt; &gt; link defined in RTGWG (draft-ietf-rtgwg-cl-requirement). <br>
&gt; <br>
&gt; I quickly glanced through this draft and these can imo be easily <br>
&gt; avoided by defining a new link type - Composite link, in the link
<br>
&gt; type sub-TLV of Link TLV in OSPF [RFC3630]. Such links MUST be <br>
&gt; avoided for setting up the PTP LSPs. Similarly the extended IS <br>
&gt; reachability TLV could be extended for IS-IS to avoid composite links.<br>
&gt; <br>
&gt; One could also use coloring to avoid these links, but this would <br>
&gt; entail manual configuration which may not be desirable.<br>
&gt; <br>
&gt; Cheers, Manav<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 0003B33D48257829_=--


From manav.bhatia@alcatel-lucent.com  Sun Jan 30 18:04:59 2011
Return-Path: <manav.bhatia@alcatel-lucent.com>
X-Original-To: tictoc@core3.amsl.com
Delivered-To: tictoc@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 9DEBD3A6B5A for <tictoc@core3.amsl.com>; Sun, 30 Jan 2011 18:04:59 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.296
X-Spam-Level: 
X-Spam-Status: No, score=-6.296 tagged_above=-999 required=5 tests=[AWL=0.302,  BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8O4kFZCdqJPu for <tictoc@core3.amsl.com>; Sun, 30 Jan 2011 18:04:58 -0800 (PST)
Received: from ihemail1.lucent.com (ihemail1.lucent.com [135.245.0.33]) by core3.amsl.com (Postfix) with ESMTP id 42F453A6A79 for <tictoc@ietf.org>; Sun, 30 Jan 2011 18:04:57 -0800 (PST)
Received: from inbansmailrelay2.in.alcatel-lucent.com (h135-250-11-33.lucent.com [135.250.11.33]) by ihemail1.lucent.com (8.13.8/IER-o) with ESMTP id p0V281Po020234 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Sun, 30 Jan 2011 20:08:04 -0600 (CST)
Received: from INBANSXCHHUB01.in.alcatel-lucent.com (inbansxchhub01.in.alcatel-lucent.com [135.250.12.32]) by inbansmailrelay2.in.alcatel-lucent.com (8.14.3/8.14.3/GMO) with ESMTP id p0V27wkC025158 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Mon, 31 Jan 2011 07:38:01 +0530
Received: from INBANSXCHMBSA1.in.alcatel-lucent.com ([135.250.12.56]) by INBANSXCHHUB01.in.alcatel-lucent.com ([135.250.12.32]) with mapi; Mon, 31 Jan 2011 07:37:58 +0530
From: "Bhatia, Manav (Manav)" <manav.bhatia@alcatel-lucent.com>
To: "lizhong.jin@zte.com.cn" <lizhong.jin@zte.com.cn>
Date: Mon, 31 Jan 2011 07:37:55 +0530
Thread-Topic: [TICTOC] Transporting PTP messages (1588) over MPLS Networks
Thread-Index: AcvA34Abj614MnXFST6TOmU7SK6fNAAC7RbQ
Message-ID: <7C362EEF9C7896468B36C9B79200D8350CFB18BB93@INBANSXCHMBSA1.in.alcatel-lucent.com>
References: <7C362EEF9C7896468B36C9B79200D8350CFB18B851@INBANSXCHMBSA1.in.alcatel-lucent.com> <OF0D6CBFC6.7105F2FD-ON48257829.00038FF3-48257829.0003B340@zte.com.cn>
In-Reply-To: <OF0D6CBFC6.7105F2FD-ON48257829.00038FF3-48257829.0003B340@zte.com.cn>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: multipart/alternative; boundary="_000_7C362EEF9C7896468B36C9B79200D8350CFB18BB93INBANSXCHMBSA_"
MIME-Version: 1.0
X-Scanned-By: MIMEDefang 2.57 on 135.245.2.33
X-Scanned-By: MIMEDefang 2.64 on 135.250.11.33
Cc: "tictoc@ietf.org" <tictoc@ietf.org>
Subject: Re: [TICTOC] Transporting PTP messages (1588) over MPLS Networks
X-BeenThere: tictoc@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Timing over IP Connection and Transfer of Clock BOF <tictoc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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, 31 Jan 2011 02:04:59 -0000

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

Hi Lizhong,

As a result of this discussion the RTGWG will add another requirement where=
 the solution should be able to indicate to a composite link that both the =
directions of a bidirectional LSP must be bound to the same component link.

This is indeed what we want for 1588. We will also include a pointer to thi=
s in the next revision.

Cheers, Manav

________________________________
From: lizhong.jin@zte.com.cn [mailto:lizhong.jin@zte.com.cn]
Sent: Monday, January 31, 2011 6.10 AM
To: Bhatia, Manav (Manav)
Cc: tictoc@ietf.org
Subject: RE: [TICTOC] Transporting PTP messages (1588) over MPLS Networks


Hi Manav,
I see the discussion at RTGWG, it is good.
Share within TICTOC: http://www.ietf.org/mail-archive/web/rtgwg/current/msg=
03181.html

Thanks
Lizhong


"Bhatia, Manav (Manav)" <manav.bhatia@alcatel-lucent.com> wrote on 2011-01-=
28 08:09:50:

> Lizhong,
>
> > [Lizhong] I mean the LAG between two end-points,
> > not MC-LAG. E.g, one LAG interface with physical link
> > A & B between two end-points, it is possible that the forward
> > path will go through A, and backward path will go through B,
> > then the physical path is not symmetric. If I understand correctly,
> > you just assume the transport delay on link A & B are the
>
> On an ordinary lag, unless it's a MC-LAG this can be assumed to be
> more or less the same.
>
> > same, but this is not always true, especially for the composite
> > link defined in RTGWG (draft-ietf-rtgwg-cl-requirement).
>
> I quickly glanced through this draft and these can imo be easily
> avoided by defining a new link type - Composite link, in the link
> type sub-TLV of Link TLV in OSPF [RFC3630]. Such links MUST be
> avoided for setting up the PTP LSPs. Similarly the extended IS
> reachability TLV could be extended for IS-IS to avoid composite links.
>
> One could also use coloring to avoid these links, but this would
> entail manual configuration which may not be desirable.
>
> Cheers, Manav
>


--------------------------------------------------------
ZTE Information Security Notice: The information contained in this mail is =
solely property of the sender's organization. This mail communication is co=
nfidential. Recipients named above are obligated to maintain secrecy and ar=
e 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 th=
e 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.


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

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; charset=3Dus-ascii">
<META content=3D"MSHTML 6.00.2900.6049" name=3DGENERATOR></HEAD>
<BODY>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D034340402-31012011><FONT face=3DA=
rial=20
color=3D#0000ff size=3D2>Hi Lizhong,</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D034340402-31012011><FONT face=3DA=
rial=20
color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D034340402-31012011><FONT face=3DA=
rial=20
color=3D#0000ff size=3D2>As a result of this discussion the RTGWG will add =
another=20
requirement where the solution should be able to indicate to a composite li=
nk=20
that both the directions of a bidirectional LSP must be bound to the same=20
component link. </FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D034340402-31012011><FONT face=3DA=
rial=20
color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D034340402-31012011><FONT face=3DA=
rial=20
color=3D#0000ff size=3D2>This is indeed what we want for 1588.&nbsp;We will=
 also=20
include a pointer to this in the next revision.</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D034340402-31012011><FONT face=3DA=
rial=20
color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D034340402-31012011><FONT face=3DA=
rial=20
color=3D#0000ff size=3D2>Cheers, Manav</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D034340402-31012011><FONT face=3DA=
rial=20
color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft>
<HR tabIndex=3D-1>
</DIV>
<DIV dir=3Dltr align=3Dleft><FONT face=3DTahoma size=3D2><B>From:</B>=20
lizhong.jin@zte.com.cn [mailto:lizhong.jin@zte.com.cn] <BR><B>Sent:</B> Mon=
day,=20
January 31, 2011 6.10 AM<BR><B>To:</B> Bhatia, Manav (Manav)<BR><B>Cc:</B>=
=20
tictoc@ietf.org<BR><B>Subject:</B> RE: [TICTOC] Transporting PTP messages (=
1588)=20
over MPLS Networks<BR></FONT><BR></DIV>
<BLOCKQUOTE dir=3Dltr=20
style=3D"PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #0000ff 2px soli=
d; MARGIN-RIGHT: 0px">
  <DIV></DIV><BR><FONT face=3Dsans-serif size=3D2>Hi Manav,</FONT> <BR><FON=
T=20
  face=3Dsans-serif size=3D2>I see the discussion at RTGWG, it is good.</FO=
NT>=20
  <BR><FONT face=3Dsans-serif size=3D2>Share within TICTOC:=20
  http://www.ietf.org/mail-archive/web/rtgwg/current/msg03181.html</FONT>=20
  <BR><BR><FONT face=3Dsans-serif size=3D2>Thanks</FONT> <BR><FONT face=3Ds=
ans-serif=20
  size=3D2>Lizhong</FONT> <BR><FONT face=3DArial size=3D1>&nbsp;</FONT>=20
  <BR><BR><TT><FONT size=3D2>"Bhatia, Manav (Manav)"=20
  &lt;manav.bhatia@alcatel-lucent.com&gt; wrote on 2011-01-28=20
  08:09:50:<BR><BR>&gt; Lizhong,<BR>&gt; &nbsp;<BR>&gt; &gt; [Lizhong] I me=
an=20
  the LAG between two end-points, <BR>&gt; &gt; not MC-LAG. E.g, one LAG=20
  interface with physical link <BR>&gt; &gt; A &amp; B between two end-poin=
ts,=20
  it is possible that the forward <BR>&gt; &gt; path will go through A, and=
=20
  backward path will go through B, <BR>&gt; &gt; then the physical path is =
not=20
  symmetric. If I understand correctly, <BR>&gt; &gt; you just assume the=20
  transport delay on link A &amp; B are the <BR>&gt; <BR>&gt; On an ordinar=
y=20
  lag, unless it's a MC-LAG this can be assumed to be <BR>&gt; more or less=
 the=20
  same.<BR>&gt; <BR>&gt; &gt; same, but this is not always true, especially=
 for=20
  the composite <BR>&gt; &gt; link defined in RTGWG=20
  (draft-ietf-rtgwg-cl-requirement). <BR>&gt; <BR>&gt; I quickly glanced th=
rough=20
  this draft and these can imo be easily <BR>&gt; avoided by defining a new=
 link=20
  type - Composite link, in the link <BR>&gt; type sub-TLV of Link TLV in O=
SPF=20
  [RFC3630]. Such links MUST be <BR>&gt; avoided for setting up the PTP LSP=
s.=20
  Similarly the extended IS <BR>&gt; reachability TLV could be extended for=
=20
  IS-IS to avoid composite links.<BR>&gt; <BR>&gt; One could also use color=
ing=20
  to avoid these links, but this would <BR>&gt; entail manual configuration=
=20
  which may not be desirable.<BR>&gt; <BR>&gt; Cheers, Manav<BR>&gt;=20
  <BR></FONT></TT><BR><PRE>------------------------------------------------=
--------
ZTE&nbsp;Information&nbsp;Security&nbsp;Notice:&nbsp;The&nbsp;information&n=
bsp;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;a=
bove&nbsp;are&nbsp;obligated&nbsp;to&nbsp;maintain&nbsp;secrecy&nbsp;and&nb=
sp;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&nbs=
p;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&nbs=
p;to&nbsp;whom&nbsp;they&nbsp;are&nbsp;addressed.&nbsp;If&nbsp;you&nbsp;hav=
e&nbsp;received&nbsp;this&nbsp;email&nbsp;in&nbsp;error&nbsp;please&nbsp;no=
tify&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&nbs=
p;of&nbsp;the&nbsp;individual&nbsp;sender.
This&nbsp;message&nbsp;has&nbsp;been&nbsp;scanned&nbsp;for&nbsp;viruses&nbs=
p;and&nbsp;Spam&nbsp;by&nbsp;ZTE&nbsp;Anti-Spam&nbsp;system.
</PRE></BLOCKQUOTE></BODY></HTML>

--_000_7C362EEF9C7896468B36C9B79200D8350CFB18BB93INBANSXCHMBSA_--

From tony.li@tony.li  Sun Jan 30 19:23:06 2011
Return-Path: <tony.li@tony.li>
X-Original-To: tictoc@core3.amsl.com
Delivered-To: tictoc@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 788FF3A6B69 for <tictoc@core3.amsl.com>; Sun, 30 Jan 2011 19:23:06 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.466
X-Spam-Level: 
X-Spam-Status: No, score=-102.466 tagged_above=-999 required=5 tests=[AWL=0.133, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id pgYgdMK6ZmgZ for <tictoc@core3.amsl.com>; Sun, 30 Jan 2011 19:23:05 -0800 (PST)
Received: from qmta14.westchester.pa.mail.comcast.net (qmta14.westchester.pa.mail.comcast.net [76.96.59.212]) by core3.amsl.com (Postfix) with ESMTP id 2376B3A69E2 for <tictoc@ietf.org>; Sun, 30 Jan 2011 19:23:05 -0800 (PST)
Received: from omta14.westchester.pa.mail.comcast.net ([76.96.62.60]) by qmta14.westchester.pa.mail.comcast.net with comcast id 23PX1g0061HzFnQ5E3SKMx; Mon, 31 Jan 2011 03:26:19 +0000
Received: from sjc-vpn4-840.cisco.com ([128.107.239.233]) by omta14.westchester.pa.mail.comcast.net with comcast id 23S41g00V52qHCY3a3S7Uo; Mon, 31 Jan 2011 03:26:16 +0000
Mime-Version: 1.0 (Apple Message framework v1082)
Content-Type: text/plain; charset=us-ascii
From: Tony Li <tony.li@tony.li>
In-Reply-To: <7C362EEF9C7896468B36C9B79200D8350CFB18BB93@INBANSXCHMBSA1.in.alcatel-lucent.com>
Date: Sun, 30 Jan 2011 19:26:03 -0800
Content-Transfer-Encoding: quoted-printable
Message-Id: <0C0E1926-74B5-4F3C-93F0-D63CDD2B7FBE@tony.li>
References: <7C362EEF9C7896468B36C9B79200D8350CFB18B851@INBANSXCHMBSA1.in.alcatel-lucent.com> <OF0D6CBFC6.7105F2FD-ON48257829.00038FF3-48257829.0003B340@zte.com.cn> <7C362EEF9C7896468B36C9B79200D8350CFB18BB93@INBANSXCHMBSA1.in.alcatel-lucent.com>
To: "Bhatia, Manav (Manav)" <manav.bhatia@alcatel-lucent.com>
X-Mailer: Apple Mail (2.1082)
Cc: "lizhong.jin@zte.com.cn" <lizhong.jin@zte.com.cn>, "tictoc@ietf.org" <tictoc@ietf.org>
Subject: Re: [TICTOC] Transporting PTP messages (1588) over MPLS Networks
X-BeenThere: tictoc@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Timing over IP Connection and Transfer of Clock BOF <tictoc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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, 31 Jan 2011 03:23:06 -0000

Hi,

I'd go further and suggest that we should recommend bidirectional LSPs =
as the preferred approach, regardless of composite links.

Tony


On Jan 30, 2011, at 6:07 PM, Bhatia, Manav (Manav) wrote:

> Hi Lizhong,
> =20
> As a result of this discussion the RTGWG will add another requirement =
where the solution should be able to indicate to a composite link that =
both the directions of a bidirectional LSP must be bound to the same =
component link.
> =20
> This is indeed what we want for 1588. We will also include a pointer =
to this in the next revision.
> =20
> Cheers, Manav
> =20
> From: lizhong.jin@zte.com.cn [mailto:lizhong.jin@zte.com.cn]=20
> Sent: Monday, January 31, 2011 6.10 AM
> To: Bhatia, Manav (Manav)
> Cc: tictoc@ietf.org
> Subject: RE: [TICTOC] Transporting PTP messages (1588) over MPLS =
Networks
>=20
>=20
> Hi Manav,=20
> I see the discussion at RTGWG, it is good.=20
> Share within TICTOC: =
http://www.ietf.org/mail-archive/web/rtgwg/current/msg03181.html=20
>=20
> Thanks=20
> Lizhong=20
>  =20
>=20
> "Bhatia, Manav (Manav)" <manav.bhatia@alcatel-lucent.com> wrote on =
2011-01-28 08:09:50:
>=20
> > Lizhong,
> > =20
> > > [Lizhong] I mean the LAG between two end-points,=20
> > > not MC-LAG. E.g, one LAG interface with physical link=20
> > > A & B between two end-points, it is possible that the forward=20
> > > path will go through A, and backward path will go through B,=20
> > > then the physical path is not symmetric. If I understand =
correctly,=20
> > > you just assume the transport delay on link A & B are the=20
> >=20
> > On an ordinary lag, unless it's a MC-LAG this can be assumed to be=20=

> > more or less the same.
> >=20
> > > same, but this is not always true, especially for the composite=20
> > > link defined in RTGWG (draft-ietf-rtgwg-cl-requirement).=20
> >=20
> > I quickly glanced through this draft and these can imo be easily=20
> > avoided by defining a new link type - Composite link, in the link=20
> > type sub-TLV of Link TLV in OSPF [RFC3630]. Such links MUST be=20
> > avoided for setting up the PTP LSPs. Similarly the extended IS=20
> > reachability TLV could be extended for IS-IS to avoid composite =
links.
> >=20
> > One could also use coloring to avoid these links, but this would=20
> > entail manual configuration which may not be desirable.
> >=20
> > Cheers, Manav
> >=20
>=20
> --------------------------------------------------------
> 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.
>=20
> _______________________________________________
> TICTOC mailing list
> TICTOC@ietf.org
> https://www.ietf.org/mailman/listinfo/tictoc


From yaakov_s@rad.com  Mon Jan 31 05:10:00 2011
Return-Path: <yaakov_s@rad.com>
X-Original-To: tictoc@core3.amsl.com
Delivered-To: tictoc@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 7339D3A6C08 for <tictoc@core3.amsl.com>; Mon, 31 Jan 2011 05:10:00 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.493
X-Spam-Level: 
X-Spam-Status: No, score=-102.493 tagged_above=-999 required=5 tests=[AWL=0.106, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ZLkwOUGnbwqG for <tictoc@core3.amsl.com>; Mon, 31 Jan 2011 05:09:59 -0800 (PST)
Received: from antivir1.rad.co.il (antivir1.rad.co.il [62.0.23.193]) by core3.amsl.com (Postfix) with ESMTP id 15C5F3A6BEC for <tictoc@ietf.org>; Mon, 31 Jan 2011 05:09:57 -0800 (PST)
Received: from exrad5.ad.rad.co.il ([192.114.24.28]) by antivir1.rad.co.il with ESMTP; 31 Jan 2011 15:13:09 +0200
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; Mon, 31 Jan 2011 15:13:08 +0200
Received: from EXRAD5.ad.rad.co.il ([fe80::ec3e:feb5:8bef:e3ba]) by exus4-drp.ad.rad.co.il ([fe80::5d6f:c2cb:2468:ee2%16]) with mapi id 14.01.0270.001; Mon, 31 Jan 2011 15:13:08 +0200
From: Yaakov Stein <yaakov_s@rad.com>
To: "tictoc@ietf.org" <tictoc@ietf.org>
Thread-Topic: [TICTOC] Transporting PTP messages (1588) over MPLS Networks
Thread-Index: AQHLtwvRa6CYok1lRYSvUt8QtgvK+ZPjbVwAgACmdwCAAAnKAIAAOHqAgAA1goCAAGBBAIAAg+MAgAS/WwCAABihgIAAFdWAgAC9NVA=
Date: Mon, 31 Jan 2011 13:13:08 +0000
Message-ID: <07F7D7DED63154409F13298786A2ADC903CDB949@EXRAD5.ad.rad.co.il>
References: <7C362EEF9C7896468B36C9B79200D8350CFB18B851@INBANSXCHMBSA1.in.alcatel-lucent.com> <OF0D6CBFC6.7105F2FD-ON48257829.00038FF3-48257829.0003B340@zte.com.cn> <7C362EEF9C7896468B36C9B79200D8350CFB18BB93@INBANSXCHMBSA1.in.alcatel-lucent.com> <0C0E1926-74B5-4F3C-93F0-D63CDD2B7FBE@tony.li>
In-Reply-To: <0C0E1926-74B5-4F3C-93F0-D63CDD2B7FBE@tony.li>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [172.17.170.37]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: Re: [TICTOC] Transporting PTP messages (1588) over MPLS Networks
X-BeenThere: tictoc@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Timing over IP Connection and Transfer of Clock BOF <tictoc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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, 31 Jan 2011 13:10:00 -0000

Hi all,=20

The issue of ensuring a bidirectional co-routed path is what I wanted to ex=
plain regarding NTP.

I was discussing this last week with the routing ADs,=20
and was told that co-routing is a standard feature of GMPLS (RFC 3471 secti=
on 4).
Since the control plane of MPLS-TP will be GMPLS, this is a good fit.

I looked up some experiments I performed a few years ago using NTP with HW =
timestamps.
For Internet paths, the fraction of the inaccuracy resulting from asymmetry
was about three times that resulting from PDV.=20
Thus asymmetry reduction is often a more important goal than TC.
Of course if we are speaking of full peer-to-peer TC asymmetry doesn't matt=
er,
but if we had that we don't need 1588 either - just sending a timestamp is =
enough.

I realize that this is not relevant for a well-engineered network
where one could use management to configure a co-routed bidirectional path.

Setting up a co-routed bidirectional path using standard RSVP-TE=20
is equally useful for NTP and 1588,
and leads me to return to my original request for a single mechanism for bo=
th.

I am thus led to reiterate my proposal for completely generic MPLS mechanis=
m for TC,=20
a method that eliminates all the FCS and UDP checksum problems that we have=
 recently discussed.

We need only to define a new PW type with an extended control word that car=
ries a CF.=20
The payload could be anything - NTP, 1588, RFC-868, one-way delay OAM, etc.
We can use the label-range idea from the present draft, and similar routing=
 extensions
to signal the TC capability.

Y(J)S




From kohn.jack@gmail.com  Mon Jan 31 05:22:51 2011
Return-Path: <kohn.jack@gmail.com>
X-Original-To: tictoc@core3.amsl.com
Delivered-To: tictoc@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 837BB3A6BED for <tictoc@core3.amsl.com>; Mon, 31 Jan 2011 05:22:51 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.309
X-Spam-Level: 
X-Spam-Status: No, score=-3.309 tagged_above=-999 required=5 tests=[AWL=0.290,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id r4i9Me5hIXKs for <tictoc@core3.amsl.com>; Mon, 31 Jan 2011 05:22:47 -0800 (PST)
Received: from mail-iw0-f172.google.com (mail-iw0-f172.google.com [209.85.214.172]) by core3.amsl.com (Postfix) with ESMTP id 2CC4A3A6C0C for <tictoc@ietf.org>; Mon, 31 Jan 2011 05:22:47 -0800 (PST)
Received: by iwn40 with SMTP id 40so5896083iwn.31 for <tictoc@ietf.org>; Mon, 31 Jan 2011 05:26:01 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=0HzYzkMvsK/XlWy7ebOra6q/Re3pdCz4Pf/T0wMrcgU=; b=OyJBYVlyz2JQbkQQOJMowqvQ8gRw563oZtKkeiBA2b1CKv50AF929z+v8dbqWTkK3+ uHSQAcgNVLGXxkUDjUaBdc+0BkJlGLq1DdJvgdPYOEO+kDEwGljgoXc37BI7065hMPmN aX8/1n1/JLoDzEeBNaAkDgGVUe7MifeEuTzLg=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=f6QWehiRpP3PBebp+wZg/ZWnw6xRAMC+ZYlNY/ixFAhSpJUd1xkk+09Dt1inn40KQ5 gshY/WQEzNgSo0ZLUsif5LSKCch8hmpFFNUzZy67SMNq+jHm2UCoIQk1cj9ZUa7JP8HZ mFeMa9lYt8xQX4kts1gE66PgOt24/R6PpmJyI=
MIME-Version: 1.0
Received: by 10.231.206.206 with SMTP id fv14mr6608783ibb.75.1296480361245; Mon, 31 Jan 2011 05:26:01 -0800 (PST)
Received: by 10.231.200.148 with HTTP; Mon, 31 Jan 2011 05:26:01 -0800 (PST)
In-Reply-To: <07F7D7DED63154409F13298786A2ADC903CDB949@EXRAD5.ad.rad.co.il>
References: <7C362EEF9C7896468B36C9B79200D8350CFB18B851@INBANSXCHMBSA1.in.alcatel-lucent.com> <OF0D6CBFC6.7105F2FD-ON48257829.00038FF3-48257829.0003B340@zte.com.cn> <7C362EEF9C7896468B36C9B79200D8350CFB18BB93@INBANSXCHMBSA1.in.alcatel-lucent.com> <0C0E1926-74B5-4F3C-93F0-D63CDD2B7FBE@tony.li> <07F7D7DED63154409F13298786A2ADC903CDB949@EXRAD5.ad.rad.co.il>
Date: Mon, 31 Jan 2011 18:56:01 +0530
Message-ID: <AANLkTimVQvukTkWiy8urq_JYHsqjvw+_gtvSvxKfxB0T@mail.gmail.com>
From: Jack Kohn <kohn.jack@gmail.com>
To: Yaakov Stein <yaakov_s@rad.com>
Content-Type: text/plain; charset=ISO-8859-1
Cc: "tictoc@ietf.org" <tictoc@ietf.org>
Subject: Re: [TICTOC] Transporting PTP messages (1588) over MPLS Networks
X-BeenThere: tictoc@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Timing over IP Connection and Transfer of Clock BOF <tictoc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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, 31 Jan 2011 13:22:51 -0000

Yakov,

> I am thus led to reiterate my proposal for completely generic MPLS mechanism for TC,
> a method that eliminates all the FCS and UDP checksum problems that we have recently discussed.
>
> We need only to define a new PW type with an extended control word that carries a CF.
> The payload could be anything - NTP, 1588, RFC-868, one-way delay OAM, etc.
> We can use the label-range idea from the present draft, and similar routing extensions

What label range are you referring to? AFAIK there isnt any label
range defined in this document. The label that 1588 uses is signalled
by RSVP to all the other nodes.

Also, what prevents the same mechanism to be used for NTP? If its NTP
that we are supporting then one does not need to provide the offset in
the RSVP object. The routing extensions remain the same and it NTP
also works. Thus the mechanism defined in this draft will work for NTP
as well.

Jack

> to signal the TC capability.
>
> Y(J)S
>
>
>
> _______________________________________________
> TICTOC mailing list
> TICTOC@ietf.org
> https://www.ietf.org/mailman/listinfo/tictoc
>

From yaakov_s@rad.com  Mon Jan 31 09:16:31 2011
Return-Path: <yaakov_s@rad.com>
X-Original-To: tictoc@core3.amsl.com
Delivered-To: tictoc@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 521B23A699E for <tictoc@core3.amsl.com>; Mon, 31 Jan 2011 09:16:31 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.496
X-Spam-Level: 
X-Spam-Status: No, score=-102.496 tagged_above=-999 required=5 tests=[AWL=0.103, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Mo82u2Ancq23 for <tictoc@core3.amsl.com>; Mon, 31 Jan 2011 09:16:30 -0800 (PST)
Received: from antivir1.rad.co.il (antivir1.rad.co.il [62.0.23.193]) by core3.amsl.com (Postfix) with ESMTP id 35E203A6ADF for <tictoc@ietf.org>; Mon, 31 Jan 2011 09:16:28 -0800 (PST)
Received: from exrad5.ad.rad.co.il ([192.114.24.28]) by antivir1.rad.co.il with ESMTP; 31 Jan 2011 19:19:41 +0200
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; Mon, 31 Jan 2011 19:19:40 +0200
Received: from EXRAD5.ad.rad.co.il ([fe80::ec3e:feb5:8bef:e3ba]) by exus4-drp.ad.rad.co.il ([fe80::5d6f:c2cb:2468:ee2%16]) with mapi id 14.01.0270.001; Mon, 31 Jan 2011 19:19:40 +0200
From: Yaakov Stein <yaakov_s@rad.com>
To: Jack Kohn <kohn.jack@gmail.com>
Thread-Topic: [TICTOC] Transporting PTP messages (1588) over MPLS Networks
Thread-Index: AQHLtwvRa6CYok1lRYSvUt8QtgvK+ZPjbVwAgACmdwCAAAnKAIAAOHqAgAA1goCAAGBBAIAAg+MAgAS/WwCAABihgIAAFdWAgAC9NVD//+psgIAAYkwg
Date: Mon, 31 Jan 2011 17:19:39 +0000
Message-ID: <07F7D7DED63154409F13298786A2ADC903CDBBEC@EXRAD5.ad.rad.co.il>
References: <7C362EEF9C7896468B36C9B79200D8350CFB18B851@INBANSXCHMBSA1.in.alcatel-lucent.com> <OF0D6CBFC6.7105F2FD-ON48257829.00038FF3-48257829.0003B340@zte.com.cn> <7C362EEF9C7896468B36C9B79200D8350CFB18BB93@INBANSXCHMBSA1.in.alcatel-lucent.com> <0C0E1926-74B5-4F3C-93F0-D63CDD2B7FBE@tony.li> <07F7D7DED63154409F13298786A2ADC903CDB949@EXRAD5.ad.rad.co.il> <AANLkTimVQvukTkWiy8urq_JYHsqjvw+_gtvSvxKfxB0T@mail.gmail.com>
In-Reply-To: <AANLkTimVQvukTkWiy8urq_JYHsqjvw+_gtvSvxKfxB0T@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [172.17.170.37]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "tictoc@ietf.org" <tictoc@ietf.org>
Subject: Re: [TICTOC] Transporting PTP messages (1588) over MPLS Networks
X-BeenThere: tictoc@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Timing over IP Connection and Transfer of Clock BOF <tictoc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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, 31 Jan 2011 17:16:31 -0000

Jack

There was a long discussion at the conference call and on the list,
with the draft authors and others maintaining that this method
is not applicable to NTP (mainly because its sole purpose is to identify
LSRs that can perform TC correction to 1588 packets).

By label range I mean the method used to identify the timing packets
in transit, whatever that method is.

Y(J)S

-----Original Message-----
From: Jack Kohn [mailto:kohn.jack@gmail.com]=20
Sent: Monday, January 31, 2011 15:26
To: Yaakov Stein
Cc: tictoc@ietf.org
Subject: Re: [TICTOC] Transporting PTP messages (1588) over MPLS Networks

Yakov,

> I am thus led to reiterate my proposal for completely generic MPLS mechan=
ism for TC,
> a method that eliminates all the FCS and UDP checksum problems that we ha=
ve recently discussed.
>
> We need only to define a new PW type with an extended control word that c=
arries a CF.
> The payload could be anything - NTP, 1588, RFC-868, one-way delay OAM, et=
c.
> We can use the label-range idea from the present draft, and similar routi=
ng extensions

What label range are you referring to? AFAIK there isnt any label
range defined in this document. The label that 1588 uses is signalled
by RSVP to all the other nodes.

Also, what prevents the same mechanism to be used for NTP? If its NTP
that we are supporting then one does not need to provide the offset in
the RSVP object. The routing extensions remain the same and it NTP
also works. Thus the mechanism defined in this draft will work for NTP
as well.

Jack

> to signal the TC capability.
>
> Y(J)S
>
>
>
> _______________________________________________
> TICTOC mailing list
> TICTOC@ietf.org
> https://www.ietf.org/mailman/listinfo/tictoc
>

From davari@broadcom.com  Mon Jan 31 10:36:41 2011
Return-Path: <davari@broadcom.com>
X-Original-To: tictoc@core3.amsl.com
Delivered-To: tictoc@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 53E423A6A6F for <tictoc@core3.amsl.com>; Mon, 31 Jan 2011 10:36:41 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.91
X-Spam-Level: 
X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[AWL=0.689,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Z-LNf7BEmfMn for <tictoc@core3.amsl.com>; Mon, 31 Jan 2011 10:36:40 -0800 (PST)
Received: from mms1.broadcom.com (mms1.broadcom.com [216.31.210.17]) by core3.amsl.com (Postfix) with ESMTP id 73D103A6977 for <tictoc@ietf.org>; Mon, 31 Jan 2011 10:36:40 -0800 (PST)
Received: from [10.16.192.232] by mms1.broadcom.com with ESMTP (Broadcom SMTP Relay (Email Firewall v6.3.2)); Mon, 31 Jan 2011 10:41:25 -0800
X-Server-Uuid: 02CED230-5797-4B57-9875-D5D2FEE4708A
Received: from SJEXCHCCR02.corp.ad.broadcom.com ([10.16.192.130]) by SJEXCHHUB02.corp.ad.broadcom.com ([10.16.192.232]) with mapi; Mon, 31 Jan 2011 10:39:44 -0800
From: "Shahram Davari" <davari@broadcom.com>
To: "Yaakov Stein" <yaakov_s@rad.com>, "tictoc@ietf.org" <tictoc@ietf.org>
Date: Mon, 31 Jan 2011 10:39:43 -0800
Thread-Topic: [TICTOC] Transporting PTP messages (1588) over MPLS Networks
Thread-Index: AQHLtwvRa6CYok1lRYSvUt8QtgvK+ZPjbVwAgACmdwCAAAnKAIAAOHqAgAA1goCAAGBBAIAAg+MAgAS/WwCAABihgIAAFdWAgAC9NVCAAGJEYA==
Message-ID: <2C2F1EBA8050E74EA81502D5740B4BD6941B652516@SJEXCHCCR02.corp.ad.broadcom.com>
References: <7C362EEF9C7896468B36C9B79200D8350CFB18B851@INBANSXCHMBSA1.in.alcatel-lucent.com> <OF0D6CBFC6.7105F2FD-ON48257829.00038FF3-48257829.0003B340@zte.com.cn> <7C362EEF9C7896468B36C9B79200D8350CFB18BB93@INBANSXCHMBSA1.in.alcatel-lucent.com> <0C0E1926-74B5-4F3C-93F0-D63CDD2B7FBE@tony.li> <07F7D7DED63154409F13298786A2ADC903CDB949@EXRAD5.ad.rad.co.il>
In-Reply-To: <07F7D7DED63154409F13298786A2ADC903CDB949@EXRAD5.ad.rad.co.il>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
MIME-Version: 1.0
X-WSS-ID: 6159DDDF3P068261470-01-01
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Subject: Re: [TICTOC] Transporting PTP messages (1588) over MPLS Networks
X-BeenThere: tictoc@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Timing over IP Connection and Transfer of Clock BOF <tictoc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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, 31 Jan 2011 18:36:41 -0000

Hi Yaakov,

I agree that we need co-routed LSPs, but I don't understand why we need a c=
omplete new method of carrying CF. I think we have to reuse what exists tod=
ay and our draft really doesn't change the encapsulation, and therefore Min=
 HW change is required to support it. On the other hand defining a new CW a=
nd PW is going to be very painful since it has major HW impact.

So I don't support such change. I think if needed we could accommodate the =
NTP as well, we just need a requirements document to evaluate.

Thx
Shahram

-----Original Message-----
From: tictoc-bounces@ietf.org [mailto:tictoc-bounces@ietf.org] On Behalf Of=
 Yaakov Stein
Sent: Monday, January 31, 2011 5:13 AM
To: tictoc@ietf.org
Subject: Re: [TICTOC] Transporting PTP messages (1588) over MPLS Networks

Hi all,=20

The issue of ensuring a bidirectional co-routed path is what I wanted to ex=
plain regarding NTP.

I was discussing this last week with the routing ADs,=20
and was told that co-routing is a standard feature of GMPLS (RFC 3471 secti=
on 4).
Since the control plane of MPLS-TP will be GMPLS, this is a good fit.

I looked up some experiments I performed a few years ago using NTP with HW =
timestamps.
For Internet paths, the fraction of the inaccuracy resulting from asymmetry
was about three times that resulting from PDV.=20
Thus asymmetry reduction is often a more important goal than TC.
Of course if we are speaking of full peer-to-peer TC asymmetry doesn't matt=
er,
but if we had that we don't need 1588 either - just sending a timestamp is =
enough.

I realize that this is not relevant for a well-engineered network
where one could use management to configure a co-routed bidirectional path.

Setting up a co-routed bidirectional path using standard RSVP-TE=20
is equally useful for NTP and 1588,
and leads me to return to my original request for a single mechanism for bo=
th.

I am thus led to reiterate my proposal for completely generic MPLS mechanis=
m for TC,=20
a method that eliminates all the FCS and UDP checksum problems that we have=
 recently discussed.

We need only to define a new PW type with an extended control word that car=
ries a CF.=20
The payload could be anything - NTP, 1588, RFC-868, one-way delay OAM, etc.
We can use the label-range idea from the present draft, and similar routing=
 extensions
to signal the TC capability.

Y(J)S



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



From manav.bhatia@alcatel-lucent.com  Mon Jan 31 16:06:49 2011
Return-Path: <manav.bhatia@alcatel-lucent.com>
X-Original-To: tictoc@core3.amsl.com
Delivered-To: tictoc@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 8BBD33A6CAD for <tictoc@core3.amsl.com>; Mon, 31 Jan 2011 16:06:49 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.301
X-Spam-Level: 
X-Spam-Status: No, score=-6.301 tagged_above=-999 required=5 tests=[AWL=0.298,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id K5oy8epBg00e for <tictoc@core3.amsl.com>; Mon, 31 Jan 2011 16:06:48 -0800 (PST)
Received: from ihemail3.lucent.com (ihemail3.lucent.com [135.245.0.37]) by core3.amsl.com (Postfix) with ESMTP id 880433A6C97 for <tictoc@ietf.org>; Mon, 31 Jan 2011 16:06:48 -0800 (PST)
Received: from inbansmailrelay2.in.alcatel-lucent.com (h135-250-11-33.lucent.com [135.250.11.33]) by ihemail3.lucent.com (8.13.8/IER-o) with ESMTP id p1109wMq017740 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Mon, 31 Jan 2011 18:10:01 -0600 (CST)
Received: from INBANSXCHHUB02.in.alcatel-lucent.com (inbansxchhub02.in.alcatel-lucent.com [135.250.12.35]) by inbansmailrelay2.in.alcatel-lucent.com (8.14.3/8.14.3/GMO) with ESMTP id p1109vjH012826 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Tue, 1 Feb 2011 05:39:58 +0530
Received: from INBANSXCHMBSA1.in.alcatel-lucent.com ([135.250.12.56]) by INBANSXCHHUB02.in.alcatel-lucent.com ([135.250.12.35]) with mapi; Tue, 1 Feb 2011 05:39:57 +0530
From: "Bhatia, Manav (Manav)" <manav.bhatia@alcatel-lucent.com>
To: Yaakov Stein <yaakov_s@rad.com>, Jack Kohn <kohn.jack@gmail.com>
Date: Tue, 1 Feb 2011 05:39:55 +0530
Thread-Topic: [TICTOC] Transporting PTP messages (1588) over MPLS Networks
Thread-Index: AQHLtwvRa6CYok1lRYSvUt8QtgvK+ZPjbVwAgACmdwCAAAnKAIAAOHqAgAA1goCAAGBBAIAAg+MAgAS/WwCAABihgIAAFdWAgAC9NVD//+psgIAAYkwggABuCbA=
Message-ID: <7C362EEF9C7896468B36C9B79200D8350CFB23DEB9@INBANSXCHMBSA1.in.alcatel-lucent.com>
References: <7C362EEF9C7896468B36C9B79200D8350CFB18B851@INBANSXCHMBSA1.in.alcatel-lucent.com> <OF0D6CBFC6.7105F2FD-ON48257829.00038FF3-48257829.0003B340@zte.com.cn> <7C362EEF9C7896468B36C9B79200D8350CFB18BB93@INBANSXCHMBSA1.in.alcatel-lucent.com> <0C0E1926-74B5-4F3C-93F0-D63CDD2B7FBE@tony.li> <07F7D7DED63154409F13298786A2ADC903CDB949@EXRAD5.ad.rad.co.il> <AANLkTimVQvukTkWiy8urq_JYHsqjvw+_gtvSvxKfxB0T@mail.gmail.com> <07F7D7DED63154409F13298786A2ADC903CDBBEC@EXRAD5.ad.rad.co.il>
In-Reply-To: <07F7D7DED63154409F13298786A2ADC903CDBBEC@EXRAD5.ad.rad.co.il>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Scanned-By: MIMEDefang 2.57 on 135.245.2.37
X-Scanned-By: MIMEDefang 2.64 on 135.250.11.33
Cc: "tictoc@ietf.org" <tictoc@ietf.org>
Subject: Re: [TICTOC] Transporting PTP messages (1588) over MPLS Networks
X-BeenThere: tictoc@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Timing over IP Connection and Transfer of Clock BOF <tictoc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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, 01 Feb 2011 00:06:49 -0000

Hi Yaakov,
=20
I am not sure if I understand why you think that the method described in th=
is draft will not work for NTP? I agree that we have been concentrating on =
1588, but that's ok for a draft that's called "Transporting PTP messages (1=
588) over MPLS Networks". We would require some very minimal changes to als=
o accommodate NTP.

The draft states that a subset of PTP messages MUST be transported over som=
e dedicated LSPs, lets call them timing LSPs for now. When setting up the R=
SVP tunnel we had also given a pointer to the start of the packet, thus it =
is trivial for implementations to note whether the incoming packet is 1588 =
or some other. If its 1588 event messages then they may want to compensate =
for residence time by updating the PTP packet Correction Field. At the very=
 least such packets should be given some sort of priority over the others.=
=20

Now this draft can be easily extended to carry NTP as well. All we need to =
say is that NTP packets MUST be transported over the timing LSPs. We will n=
eed to change section 13 where we have described routing extensions to now =
indicate the protocol (1588 or NTP) that the router supports. Additionally,=
 it can also indicate that if its 1588, then is it capable of updating the =
CF. Similarly, we may need some minor changes in the RSVP section as well.

The section on ECMP and QoS will remain as is without any changes. There ca=
n be a subsection for 1588 where we discuss the UDP checksum, etc.

So I don't see why you think that this draft precludes the possibility of s=
upporting NTP.

Cheers, Manav

> -----Original Message-----
> From: tictoc-bounces@ietf.org=20
> [mailto:tictoc-bounces@ietf.org] On Behalf Of Yaakov Stein
> Sent: Monday, January 31, 2011 10.50 PM
> To: Jack Kohn
> Cc: tictoc@ietf.org
> Subject: Re: [TICTOC] Transporting PTP messages (1588) over=20
> MPLS Networks
>=20
> Jack
>=20
> There was a long discussion at the conference call and on the list,
> with the draft authors and others maintaining that this method
> is not applicable to NTP (mainly because its sole purpose is=20
> to identify
> LSRs that can perform TC correction to 1588 packets).
>=20
> By label range I mean the method used to identify the timing packets
> in transit, whatever that method is.
>=20
> Y(J)S
>=20
> -----Original Message-----
> From: Jack Kohn [mailto:kohn.jack@gmail.com]=20
> Sent: Monday, January 31, 2011 15:26
> To: Yaakov Stein
> Cc: tictoc@ietf.org
> Subject: Re: [TICTOC] Transporting PTP messages (1588) over=20
> MPLS Networks
>=20
> Yakov,
>=20
> > I am thus led to reiterate my proposal for completely=20
> generic MPLS mechanism for TC,
> > a method that eliminates all the FCS and UDP checksum=20
> problems that we have recently discussed.
> >
> > We need only to define a new PW type with an extended=20
> control word that carries a CF.
> > The payload could be anything - NTP, 1588, RFC-868, one-way=20
> delay OAM, etc.
> > We can use the label-range idea from the present draft, and=20
> similar routing extensions
>=20
> What label range are you referring to? AFAIK there isnt any label
> range defined in this document. The label that 1588 uses is signalled
> by RSVP to all the other nodes.
>=20
> Also, what prevents the same mechanism to be used for NTP? If its NTP
> that we are supporting then one does not need to provide the offset in
> the RSVP object. The routing extensions remain the same and it NTP
> also works. Thus the mechanism defined in this draft will work for NTP
> as well.
>=20
> Jack
>=20
> > to signal the TC capability.
> >
> > Y(J)S
> >
> >
> >
> > _______________________________________________
> > TICTOC mailing list
> > TICTOC@ietf.org
> > https://www.ietf.org/mailman/listinfo/tictoc
> >
> _______________________________________________
> TICTOC mailing list
> TICTOC@ietf.org
> https://www.ietf.org/mailman/listinfo/tictoc
> =
