Re: [Detnet-dp-dt] [EXT] DETNET Synchronization Slides

Tal Mizrahi <talmi@marvell.com> Mon, 13 February 2017 09:01 UTC

Return-Path: <talmi@marvell.com>
X-Original-To: detnet-dp-dt@ietfa.amsl.com
Delivered-To: detnet-dp-dt@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5B9DA12944C for <detnet-dp-dt@ietfa.amsl.com>; Mon, 13 Feb 2017 01:01:25 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level:
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id z3xynhmgC2ab for <detnet-dp-dt@ietfa.amsl.com>; Mon, 13 Feb 2017 01:01:23 -0800 (PST)
Received: from mx0b-0016f401.pphosted.com (mx0a-0016f401.pphosted.com [67.231.148.174]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 77EC41293DF for <detnet-dp-dt@ietf.org>; Mon, 13 Feb 2017 01:01:23 -0800 (PST)
Received: from pps.filterd (m0045849.ppops.net [127.0.0.1]) by mx0a-0016f401.pphosted.com (8.16.0.20/8.16.0.20) with SMTP id v1D8tBXP008303; Mon, 13 Feb 2017 01:01:20 -0800
Received: from il-exch02.marvell.com ([199.203.130.102]) by mx0a-0016f401.pphosted.com with ESMTP id 28j0ur91we-2 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-SHA384 bits=256 verify=NOT); Mon, 13 Feb 2017 01:01:13 -0800
Received: from IL-EXCH01.marvell.com (10.4.102.220) by IL-EXCH02.marvell.com (10.4.102.221) with Microsoft SMTP Server (TLS) id 15.0.1210.3; Mon, 13 Feb 2017 11:01:02 +0200
Received: from IL-EXCH01.marvell.com ([fe80::5d63:81cd:31e2:fc36]) by IL-EXCH01.marvell.com ([fe80::5d63:81cd:31e2:fc36%20]) with mapi id 15.00.1210.000; Mon, 13 Feb 2017 11:01:02 +0200
From: Tal Mizrahi <talmi@marvell.com>
To: Jouni Korhonen <jouni.korhonen@broadcom.com>
Thread-Topic: [EXT] [Detnet-dp-dt] DETNET Synchronization Slides
Thread-Index: AQHSgxQK3LDh9bGEKEWZ2Ra6one5aKFmqByA
Date: Mon, 13 Feb 2017 09:01:02 +0000
Message-ID: <a1e0e31c8d8b403994acd3eed848cba6@IL-EXCH01.marvell.com>
References: <b6721061760841cc8e71f2634bc3b1b7@IL-EXCH01.marvell.com> <97CA9DEF-1BD1-4317-AD32-95D0E0D90A5D@broadcom.com> <5399b34b24804c13a2d8e171e1677683@IL-EXCH01.marvell.com> <97AF77D4-8378-4BAA-9B5B-F411C4096B28@broadcom.com>
In-Reply-To: <97AF77D4-8378-4BAA-9B5B-F411C4096B28@broadcom.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator:
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.4.102.210]
Content-Type: multipart/mixed; boundary="_002_a1e0e31c8d8b403994acd3eed848cba6ILEXCH01marvellcom_"
MIME-Version: 1.0
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:, , definitions=2017-02-13_04:, , signatures=0
X-Proofpoint-Details: rule=outbound_notspam policy=outbound score=0 priorityscore=1501 malwarescore=0 suspectscore=0 phishscore=0 bulkscore=0 spamscore=0 clxscore=1015 lowpriorityscore=0 impostorscore=0 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1612050000 definitions=main-1702130090
Archived-At: <https://mailarchive.ietf.org/arch/msg/detnet-dp-dt/2LUVUl1nkvF828NvvANcb2fWc58>
Cc: "detnet-dp-dt@ietf.org" <detnet-dp-dt@ietf.org>
Subject: Re: [Detnet-dp-dt] [EXT] DETNET Synchronization Slides
X-BeenThere: detnet-dp-dt@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: DetNet WG Data Plane Design Team <detnet-dp-dt.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/detnet-dp-dt>, <mailto:detnet-dp-dt-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/detnet-dp-dt/>
List-Post: <mailto:detnet-dp-dt@ietf.org>
List-Help: <mailto:detnet-dp-dt-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/detnet-dp-dt>, <mailto:detnet-dp-dt-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 13 Feb 2017 09:01:25 -0000

Hi Jouni, 

That is a fair point. If only the PW nodes function as TCs, then indeed the accuracy will be lower.
I added a clarification about this in slide 6.

The updated slides are attached.

Thanks,
Tal.

>-----Original Message-----
>From: Jouni Korhonen [mailto:jouni.korhonen@broadcom.com]
>Sent: Thursday, February 09, 2017 10:35 PM
>To: Tal Mizrahi
>Cc: detnet-dp-dt@ietf.org
>Subject: Re: [EXT] [Detnet-dp-dt] DETNET Synchronization Slides
>
>Tal,
>
>I understood that in 2) the TC function would only be in the PW nodes we define
>leaving all intermediate “normal” LSRs between PW nodes as a source of higher
>inaccuracy. If this was not a correct understanding then the value in 2) is likely
>too high.
>
>- Jouni
>
>
>> On 08 Feb 2017, at 23:22, Tal Mizrahi <talmi@marvell.com> wrote:
>>
>> Hi Jouni,
>>
>> Sorry for not explaining the accuracy numbers on slide 6 further. I made some
>changes following the discussion, and also added notes saying that the accuracy
>will depend on the network topology and on the number of hops.
>>
>> Regarding approach 2, I believe sub-microsecond accuracy can certainly be
>achieved using transparent clocks in a real network. There are quite a few
>publications that show this. Here are a couple:
>> - For example, China Mobile have revealed in a keynote lecture in ISPCS 2014
>that they have measured an accuracy of 266 ns over 30 hops of transparent
>clocks. Unfortunately, this presentation is not in the public domain, but a short
>version of it is available  (https://www.ietf.org/mail-
>archive/web/tictoc/current/pdfp9ceHphbcE.pdf).
>> - Another example:
>http://wwwen.zte.com.cn/endata/magazine/ztecommunications/2010Year/no3
>/articles/201009/t20100913_191838.html
>> But again, this entirely depends on the nature of the network.
>>
>> Regarding approach 1, the accuracy will entirely depend on the network
>topology (the number of hops, the physical distance, the type of intermediate
>nodes, the delay variation). Hundreds of microseconds is just an example. Some
>of the research I took part in showed that in a multi-site public cloud network you
>can achieve a precision on the order of hundreds of microseconds using PTP
>without on-path support
>(https://sites.google.com/site/talmizrahihome/files/TaaSInfocomFinal.pdf?attred
>irects=0). But again, this entirely depends on the nature of the network.
>>
>> Please let me know if there are further comments.
>>
>> Thanks,
>> Tal.
>>
>>
>>> -----Original Message-----
>>> From: Jouni Korhonen [mailto:jouni.korhonen@broadcom.com]
>>> Sent: Wednesday, February 08, 2017 8:15 PM
>>> To: Tal Mizrahi
>>> Cc: detnet-dp-dt@ietf.org
>>> Subject: [EXT] Re: [Detnet-dp-dt] DETNET Synchronization Slides
>>>
>>> External Email
>>>
>>> ----------------------------------------------------------------------
>>> Thanks Tal,
>>>
>>> Didn’t we also agree adjusting the slide 6 “typical accuracy” numbers:
>>> 1) <1ms or hundreds of us
>>> 2) <tens of us
>>> 3) <1us
>>>
>>> - Jouni
>>>
>>>
>>> --
>>> Jouni Korhonen, Broadcom Ltd.
>>> M: +1-408-391-7160
>>>
>>>> On Feb 7, 2017, at 10:51 PM, Tal Mizrahi <talmi@marvell.com> wrote:
>>>>
>>>> Hi,
>>>>
>>>> The slides from today’s weekly meeting are attached.
>>>> I slightly updated them after the meeting based on the comments.
>>>>
>>>> Cheers,
>>>> Tal.
>>>> <Synchronization in
>>> DETNET.pptx>_______________________________________________
>>>> Detnet-dp-dt mailing list
>>>> Detnet-dp-dt@ietf.org
>>>> https://www.ietf.org/mailman/listinfo/detnet-dp-dt
>>