Re: [Detnet-dp-dt] [EXT] Re: Data Plane Approach - Synchronization Traffic
Jouni Korhonen <jouni.korhonen@broadcom.com> Thu, 26 January 2017 18:39 UTC
Return-Path: <jouni.korhonen@broadcom.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 E36DD129984
for <detnet-dp-dt@ietfa.amsl.com>; Thu, 26 Jan 2017 10:39:54 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,
DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1,
RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001]
autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key)
header.d=broadcom.com
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 SFahdkfkJb9J for <detnet-dp-dt@ietfa.amsl.com>;
Thu, 26 Jan 2017 10:39:53 -0800 (PST)
Received: from mail-pg0-x234.google.com (mail-pg0-x234.google.com
[IPv6:2607:f8b0:400e:c05::234])
(using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits))
(No client certificate requested)
by ietfa.amsl.com (Postfix) with ESMTPS id 59A96129986
for <detnet-dp-dt@ietf.org>; Thu, 26 Jan 2017 10:39:53 -0800 (PST)
Received: by mail-pg0-x234.google.com with SMTP id 14so74377664pgg.1
for <detnet-dp-dt@ietf.org>; Thu, 26 Jan 2017 10:39:53 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=broadcom.com; s=google;
h=mime-version:subject:from:in-reply-to:date:cc
:content-transfer-encoding:message-id:references:to;
bh=7bYRgonoqe5/GpP96B14cJn3TcKpS//R7JBgduPLZas=;
b=HgYoj+27kEDb1Bk0zKE/g49pbQb7SEkZRgosAbyfqPgc5N9HdlKj3Pc0AE9ZY5cPZx
ijUc8yP1tpcVDrnt2bmMr/w84KOa0/06PPbnzEZzFKeK9lSKGzLzd1nRyp2RIPjuqOSp
THE1MpOcsCRWxnjdxvo4OqBxhD4infFoh+Hmw=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=1e100.net; s=20161025;
h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc
:content-transfer-encoding:message-id:references:to;
bh=7bYRgonoqe5/GpP96B14cJn3TcKpS//R7JBgduPLZas=;
b=HNUnfvt5EmAycMe5gsHw/GCZXuKGwb94s8BD38D1tbvRRJZ43MpJJYSHjBbTb8MRfA
r4vLTGzOSbt7uXGyfik1f6sQL/7VQLOCWunpM0uCbj6FifIIldulmPcw3Ul3SASXPUCG
F8/WPWCKOFyyunt0WBlHDkXkv656JYnRiO2rqkwmvtI96w+xyV/o7Z5/twqpbpfhDjPK
WNl2Iv7q3ZmR/FJLQO6GJCxsLUkADcDM6vy5vFtiPmtjew5DOyt1lYz4TOJ9XgGF4R6D
jVQIyQLQBp0rtzSZoHWo86aF6Iumfe3kRvnjWWfKoWjpxR9GWe7ovcqDEMV6K0YJo8Ve
wZqQ==
X-Gm-Message-State: AIkVDXK29yhtnCUmTFiuWopqPwD0IfxyX2dW+6Zmal22Sal5Tq82+361foDzR61KTQ2o0gm1
X-Received: by 10.99.102.70 with SMTP id a67mr4801000pgc.222.1485455992470;
Thu, 26 Jan 2017 10:39:52 -0800 (PST)
Received: from [192.168.89.94] ([216.31.219.19])
by smtp.gmail.com with ESMTPSA id w125sm5118964pgb.11.2017.01.26.10.39.51
(version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128);
Thu, 26 Jan 2017 10:39:51 -0800 (PST)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 10.2 \(3259\))
From: Jouni Korhonen <jouni.korhonen@broadcom.com>
In-Reply-To: <b5ee3b37cec54a97a35ca4fc2853f609@IL-EXCH01.marvell.com>
Date: Thu, 26 Jan 2017 10:39:50 -0800
Content-Transfer-Encoding: quoted-printable
Message-Id: <34213402-7F69-4B50-AB8A-07B5412D9B09@broadcom.com>
References: <2d23229047a4428684fa1194fd95261c@IL-EXCH01.marvell.com>
<d3d8326e-b22a-df42-a7ed-6d3f1fca1e1c@pi.nu>
<b5ee3b37cec54a97a35ca4fc2853f609@IL-EXCH01.marvell.com>
To: Tal Mizrahi <talmi@marvell.com>
X-Mailer: Apple Mail (2.3259)
Archived-At: <https://mailarchive.ietf.org/arch/msg/detnet-dp-dt/oVoqs3IqL-HzkNK0UC-W_ua1ulc>
Cc: "detnet-dp-dt@ietf.org" <detnet-dp-dt@ietf.org>, Loa Andersson <loa@pi.nu>
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 18:39:55 -0000
> On Jan 25, 2017, at 11:10 PM, Tal Mizrahi <talmi@marvell.com> wrote: > > 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. In a path redundancy case would the PTP messages on multiple paths be exact copies a single origin PTP message or different PTP messages? - JOuni > > 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 > > _______________________________________________ > Detnet-dp-dt mailing list > Detnet-dp-dt@ietf.org > https://www.ietf.org/mailman/listinfo/detnet-dp-dt
- [Detnet-dp-dt] Data Plane Approach - Synchronizat… Tal Mizrahi
- Re: [Detnet-dp-dt] Data Plane Approach - Synchron… Loa Andersson
- Re: [Detnet-dp-dt] [EXT] Re: Data Plane Approach … Tal Mizrahi
- Re: [Detnet-dp-dt] [EXT] Re: Data Plane Approach … Jouni Korhonen
- Re: [Detnet-dp-dt] [EXT] Re: Data Plane Approach … Tal Mizrahi
- Re: [Detnet-dp-dt] [EXT] Re: Data Plane Approach … Balázs Varga A
- Re: [Detnet-dp-dt] [EXT] Re: Data Plane Approach … Jouni Korhonen
- Re: [Detnet-dp-dt] [EXT] Re: Data Plane Approach … Norman Finn
- Re: [Detnet-dp-dt] [EXT] Re: Data Plane Approach … Jiangyuanlong