IETF Logo Mail Archive

Re: [Detnet-dp-dt] [EXT] Re: Data Plane Approach - Synchronization Traffic

Tal Mizrahi <talmi@marvell.com> Thu, 26 January 2017 07:10 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 05DED12946F for <detnet-dp-dt@ietfa.amsl.com>; Wed, 25 Jan 2017 23:10:19 -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 1DtRSDKQVk_q for <detnet-dp-dt@ietfa.amsl.com>; Wed, 25 Jan 2017 23:10:17 -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 E3ADC12940A for <detnet-dp-dt@ietf.org>; Wed, 25 Jan 2017 23:10:17 -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 v0Q75GKt001343; Wed, 25 Jan 2017 23:10:17 -0800
Received: from il-exch01.marvell.com ([199.203.130.101]) by mx0a-0016f401.pphosted.com with ESMTP id 285nn31pxv-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-SHA384 bits=256 verify=NOT); Wed, 25 Jan 2017 23:10:17 -0800
Received: from IL-EXCH01.marvell.com (10.4.102.220) by IL-EXCH01.marvell.com (10.4.102.220) with Microsoft SMTP Server (TLS) id 15.0.1210.3; Thu, 26 Jan 2017 09:10:13 +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; Thu, 26 Jan 2017 09:10:13 +0200
From: Tal Mizrahi <talmi@marvell.com>
To: Loa Andersson <loa@pi.nu>, "detnet-dp-dt@ietf.org" <detnet-dp-dt@ietf.org>
Thread-Topic: [EXT] Re: [Detnet-dp-dt] Data Plane Approach - Synchronization Traffic
Thread-Index: AdJ3nXRCQSE7c1/1Shu53w5dO/RES///53eA///eBUA=
Date: Thu, 26 Jan 2017 07:10:12 +0000
Message-ID: <b5ee3b37cec54a97a35ca4fc2853f609@IL-EXCH01.marvell.com>
References: <2d23229047a4428684fa1194fd95261c@IL-EXCH01.marvell.com> <d3d8326e-b22a-df42-a7ed-6d3f1fca1e1c@pi.nu>
In-Reply-To: <d3d8326e-b22a-df42-a7ed-6d3f1fca1e1c@pi.nu>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.4.102.210]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:, , definitions=2017-01-26_05:, , 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=1011 lowpriorityscore=0 impostorscore=0 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1612050000 definitions=main-1701260074
Archived-At: <https://mailarchive.ietf.org/arch/msg/detnet-dp-dt/yvs5fPWA8dCT71gkt1iZX-p1rbk>
Subject: Re: [Detnet-dp-dt] [EXT] Re: Data Plane Approach - Synchronization Traffic
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: Thu, 26 Jan 2017 07:10:19 -0000

Hi Loa,


>> - If the answer is yes: not sure replication and elimination makes sense for PTP.
>
>Why is that?

In order for PTP to work well, PTP packets have to be consistently sent over the same path. If packets are intermittently sent through two different paths (with two different delays) the PTP slave will not be able to synchronize in a stable way.
However, it *does* make sense for PTP to be sent through two different paths *without* elimination at the end. Such path redundancy allows the slave to always receive the sync information through both paths, which actually allows more robust synchronization than over a single path.

So path redundancy is good for PTP, but elimination - not so good. 

Cheers,
Tal.


>-----Original Message-----
>From: Loa Andersson [mailto:loa@pi.nu]
>Sent: Thursday, January 26, 2017 9:01 AM
>To: Tal Mizrahi; detnet-dp-dt@ietf.org
>Subject: [EXT] Re: [Detnet-dp-dt] Data Plane Approach - Synchronization Traffic
>
>External Email
>
>----------------------------------------------------------------------
>Tal,
>
>On 2017-01-26 14:44, Tal Mizrahi wrote:
>> Hi,
>>
>> I realize this is a bit off-topic, but one of the things I am wondering about is how
>synchronization traffic (PTP) is forwarded in the context of the data plane
>approaches we have been considering.
>> Is PTP transported as a DETNET flow?
>> - If the answer is no: does that mean we are assuming that synchronization is
>achieved at a different layer, possibly requiring dedicated communication
>between the customer and provider?
>> - If the answer is yes: not sure replication and elimination makes sense for PTP.
>
>Why is that?
>
>/Loa
>>
>> Will be happy to hear your thoughts, and apologies if this has already been
>discussed elsewhere and I am not aware.
>>
>> Cheers,
>> Tal.
>> _______________________________________________
>> Detnet-dp-dt mailing list
>> Detnet-dp-dt@ietf.org
>> https://www.ietf.org/mailman/listinfo/detnet-dp-dt
>>
>
>--
>
>
>Loa Andersson                        email: loa@mail01.huawei.com
>Senior MPLS Expert                          loa@pi.nu
>Huawei Technologies (consultant)     phone: +46 739 81 21 64

v2.8.7 | Report a Bug | By Email