Re: [TICTOC] [mpls] TICTOC WG LC for draft-ietf-tictoc-1588overmpls

Alexander Vainshtein <Alexander.Vainshtein@ecitele.com> Sat, 20 July 2013 14:53 UTC

Return-Path: <Alexander.Vainshtein@ecitele.com>
X-Original-To: tictoc@ietfa.amsl.com
Delivered-To: tictoc@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3413321F9CE7 for <tictoc@ietfa.amsl.com>; Sat, 20 Jul 2013 07:53:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.601
X-Spam-Level:
X-Spam-Status: No, score=-4.601 tagged_above=-999 required=5 tests=[AWL=0.600, BAYES_00=-2.599, HTML_MESSAGE=0.001, MIME_QP_LONG_LINE=1.396, RCVD_IN_DNSWL_MED=-4, UNPARSEABLE_RELAY=0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 9rTGbnC5DDBM for <tictoc@ietfa.amsl.com>; Sat, 20 Jul 2013 07:53:37 -0700 (PDT)
Received: from mail1.bemta14.messagelabs.com (mail1.bemta14.messagelabs.com [193.109.254.106]) by ietfa.amsl.com (Postfix) with ESMTP id D777421F91CA for <tictoc@ietf.org>; Sat, 20 Jul 2013 07:53:34 -0700 (PDT)
Received: from [193.109.254.147:31760] by server-2.bemta-14.messagelabs.com id CC/88-18376-D64AAE15; Sat, 20 Jul 2013 14:53:33 +0000
X-Env-Sender: Alexander.Vainshtein@ecitele.com
X-Msg-Ref: server-14.tower-27.messagelabs.com!1374332006!928814!3
X-Originating-IP: [147.234.242.234]
X-StarScan-Received:
X-StarScan-Version: 6.9.11; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 22316 invoked from network); 20 Jul 2013 14:53:32 -0000
Received: from ilptbmg01-out.ecitele.com (HELO ilptbmg01-out.ecitele.com) (147.234.242.234) by server-14.tower-27.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 20 Jul 2013 14:53:32 -0000
X-AuditID: 93eaf2e7-b7f636d000006656-f9-51eaa46bf2b2
Received: from ILPTWPVEXCA01.ecitele.com ( [172.31.244.224]) by ilptbmg01-out.ecitele.com (Symantec Messaging Gateway) with SMTP id 82.78.26198.B64AAE15; Sat, 20 Jul 2013 17:53:31 +0300 (IDT)
Received: from ILPTWPVEXMB02.ecitele.com ([fe80::5979:ca8d:419f:56df]) by ILPTWPVEXCA01.ecitele.com ([fe80::ac15:43ab:d541:dfa7%12]) with mapi id 14.03.0123.003; Sat, 20 Jul 2013 17:53:31 +0300
From: Alexander Vainshtein <Alexander.Vainshtein@ecitele.com>
To: Kevin Gross <kevin.gross@avanw.com>, Shahram Davari <davari@broadcom.com>
Thread-Topic: [TICTOC] [mpls] TICTOC WG LC for draft-ietf-tictoc-1588overmpls
Thread-Index: AQHOhKZTqlqJIIKddUKix8fzrDoZZ5ltp4jW
Date: Sat, 20 Jul 2013 14:53:31 +0000
Message-ID: <F9336571731ADE42A5397FC831CEAA02150E7E77@ILPTWPVEXMB02.ecitele.com>
References: <07F7D7DED63154409F13298786A2ADC904E58E15@EXRAD5.ad.rad.co.il> <F9336571731ADE42A5397FC831CEAA02150E7717@ILPTWPVEXMB02.ecitele.com> <E806627C-460A-4417-ABD1-929A4BAEC6D9@yahoo.com> <F9336571731ADE42A5397FC831CEAA02150E7CA1@ILPTWPVEXMB02.ecitele.com> <20211F91F544D247976D84C5D778A4C30845D4@SG70YWXCHMBA05.zap.alcatel-lucent.com> <51E915BF.6020308@cisco.com> <1AB8A6CA-414A-4EFB-8704-47B41460CA90@broadcom.com>, <CALw1_Q2Ss2CGEC8mSFAhz_gPdsOjfa_ZV7ru0pbNAA0qP08keg@mail.gmail.com>
In-Reply-To: <CALw1_Q2Ss2CGEC8mSFAhz_gPdsOjfa_ZV7ru0pbNAA0qP08keg@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [147.234.1.2]
Content-Type: multipart/alternative; boundary="_000_F9336571731ADE42A5397FC831CEAA02150E7E77ILPTWPVEXMB02ec_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFlrNKsWRmVeSWpSXmKPExsUy+dWnL7o5S14FGvw6z2xx8HkTo8Xf5h52 ByaPJUt+MnnMmnWYKYApqoHRJjEvL78ksSRVISW1ONlWKaAosywxuVJJITPFVslQSaEgJzE5 NTc1r8RWKbGgIDUvRcmOSwED2ACVZeYppOYl56dk5qXbKnkG++taWJha6hoq2akpGxpbc4Vk ZBYrpOrmJmbmKOSmFhcnpqcqAEUStjBnrNoxlalgg0PF+eurWRsYD5t1MXJySAiYSDRcf8EG YYtJXLi3Hsjm4hASOMgo8XXPTnaQhJDAUUaJF09KQWw2AVuJTavvgjWICPhKNH7Yw9jFyMHB LJAjMatJGMQUFvCR+HFSFcQEqXi0hAOi2EhiZk8PWCOLgKrE8wkXWEFsXoEAiUMnJzJDbP3G LPHo5n2wBKdAoMTiW3PBGhiBTvt+ag0TiM0sIC5x68l8JoiTBSSW7DnPDGGLSrx8/I8VwpaX 2Lz1MStEfb7EjF0QF/MKCEqcnPmEBaJGUuLgihssExjFZiEZOwtJyywkLRBxPYkbU6ewQdja EssWvmaGsHUlZvw7xIIsvoCRfRWjaGZOQUlSbrqBoV5qcmZJak6qXnJ+7iZGSMp5voPx13yV Q4xBwACZyCzFnZwPTFl5JfHGBgZEcpTEeZc3hPsLCaQDk1Z2ampBalF8UWlOavEhRiYOTqkG xvSuKb2eO74+WM/p4tAzZe211TVCC47rf5xnXPLw3fP1G1JMVCefW/dln8lLG5uJ90+0ni5c k2S4e9FD35Oesa35nx8FrXFkrrmRWsv7tyxFwOzaxPyZ7v4xS6yDjx5Ye97R+/a6ZSvU50g8 KGXY8uTGNq/Fc++or/rh0WdSsKzn9RJrpXf1HjOVWIozEg21mIuKEwFO0SAPPgMAAA==
Cc: "mpls@ietf.org" <mpls@ietf.org>, "tictoc@ietf.org" <tictoc@ietf.org>, "S. Davari" <davarish@yahoo.com>
Subject: Re: [TICTOC] [mpls] TICTOC WG LC for draft-ietf-tictoc-1588overmpls
X-BeenThere: tictoc@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Timing over IP Connection and Transfer of Clock BOF <tictoc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tictoc>, <mailto:tictoc-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tictoc>
List-Post: <mailto:tictoc@ietf.org>
List-Help: <mailto:tictoc-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tictoc>, <mailto:tictoc-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 20 Jul 2013 14:53:42 -0000

Kevin, Shahram and all,

I do not actively follow the developments in the ITU-T SG 15, but I believe that investigation of partial on-path support for PTP (which would be the case if some LERs on the path were not PTP-aware) has just began there, and it is not clear what (if anything) could be achieved and under what conditions.





Did I miss something important here?



My 2c,

     Sasha

________________________________
From: tictoc-bounces@ietf.org [tictoc-bounces@ietf.org] on behalf of Kevin Gross [kevin.gross@avanw.com]
Sent: Friday, July 19, 2013 7:32 PM
To: Shahram Davari
Cc: mpls@ietf.org; S. Davari; tictoc@ietf.org
Subject: Re: [TICTOC] [mpls] TICTOC WG LC for draft-ietf-tictoc-1588overmpls

You need to specify what you mean by "recover the time correctly." Everytime you pass through a piece of equipment that is not timing aware, you introduce noise into the timing signal. More hops, more noise. Noise reduces synchronization accuracy.

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


On Fri, Jul 19, 2013 at 7:19 AM, Shahram Davari <davari@broadcom.com<mailto:davari@broadcom.com>> wrote:
Hi Stewart,

Not necessarily. It is ok if some of the routers in the path are not timing aware. That is the whole idea. We have tested cases in which 5-7 hops are not   1588 aware and still we can recover the time correctly.

Regards,
Shahram


On Jul 19, 2013, at 3:33 AM, "Stewart Bryant" <stbryant@cisco.com<mailto:stbryant@cisco.com>> wrote:

> On 19/07/2013 09:11, Bhatia, Manav (Manav) wrote:
>> Hi Sasha,
>>
>>> 1) reserved label is not backward compatible with existing routers. One
>>> of the requirements is that routers that are not PTP aware can just
>>> switch the packet normally.  Using a reserved label can't achieve this
>>> requirement, since routers that don't understand it will drop it or
>>> sent it to CPU.
>>> [[Sasha]]  Is not this concern  applicable to any new reserved label?
>>> And routers that use network processors as forwarding engines could
>>> easily overcome this issue by upgrading their microcode.
>>> But I agree that this is a valid concern.
>> This is a huge concern because not all routers use network processors that can be reprogrammed.
>>
>> The current solution works with any router that can set up an MPLS path.
> Really?
>
> Surely the LSR needs to know that on seeing a label in the FEC it needs
> to timestamp the packet.
>
> Stewart
> _______________________________________________
> TICTOC mailing list
> TICTOC@ietf.org<mailto:TICTOC@ietf.org>
> https://www.ietf.org/mailman/listinfo/tictoc
>

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



This e-mail message is intended for the recipient only and contains information which is CONFIDENTIAL and which may be proprietary to ECI Telecom. If you have received this transmission in error, please inform us by e-mail, phone or fax, and then delete the original and all copies thereof.