Re: [Detnet-dp-dt] [EXT] Re: Data Plane Approach - Synchronization Traffic
Jiangyuanlong <jiangyuanlong@huawei.com> Mon, 06 February 2017 12:22 UTC
Return-Path: <jiangyuanlong@huawei.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 E8264129D2F
for <detnet-dp-dt@ietfa.amsl.com>; Mon, 6 Feb 2017 04:22:51 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.222
X-Spam-Level:
X-Spam-Status: No, score=-4.222 tagged_above=-999 required=5
tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01,
RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-0.001, SPF_PASS=-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 T6GunY5V6Pbg for <detnet-dp-dt@ietfa.amsl.com>;
Mon, 6 Feb 2017 04:22:48 -0800 (PST)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17])
(using TLSv1 with cipher RC4-SHA (128/128 bits))
(No client certificate requested)
by ietfa.amsl.com (Postfix) with ESMTPS id 37714129D2C
for <detnet-dp-dt@ietf.org>; Mon, 6 Feb 2017 04:22:47 -0800 (PST)
Received: from 172.18.7.190 (EHLO lhreml706-cah.china.huawei.com)
([172.18.7.190])
by lhrrg01-dlp.huawei.com (MOS 4.3.7-GA FastPath queued)
with ESMTP id DFX52977; Mon, 06 Feb 2017 12:22:44 +0000 (GMT)
Received: from SZXEMA415-HUB.china.huawei.com (10.82.72.33) by
lhreml706-cah.china.huawei.com (10.201.5.182) with Microsoft SMTP Server
(TLS) id 14.3.301.0; Mon, 6 Feb 2017 12:22:40 +0000
Received: from SZXEMA506-MBS.china.huawei.com ([169.254.4.67]) by
SZXEMA415-HUB.china.huawei.com ([10.82.72.33]) with mapi id 14.03.0235.001;
Mon, 6 Feb 2017 20:22:32 +0800
From: Jiangyuanlong <jiangyuanlong@huawei.com>
To: Jouni Korhonen <jouni.korhonen@broadcom.com>,
=?utf-8?B?QmFsw6F6cyBWYXJnYSBB?= <balazs.a.varga@ericsson.com>
Thread-Topic: [Detnet-dp-dt] [EXT] Re: Data Plane Approach - Synchronization
Traffic
Thread-Index: AQHSd6NFAkjR4vgVJkq6sNJ5blMiGKFKkcMAgADZIQCABxyZAIAAA1SAgAlnGJA=
Date: Mon, 6 Feb 2017 12:22:31 +0000
Message-ID: <3B0A1BED22CAD649A1B3E97BE5DDD68BBAB0F5C5@szxema506-mbs.china.huawei.com>
References: <2d23229047a4428684fa1194fd95261c@IL-EXCH01.marvell.com>
<d3d8326e-b22a-df42-a7ed-6d3f1fca1e1c@pi.nu>
<b5ee3b37cec54a97a35ca4fc2853f609@IL-EXCH01.marvell.com>
<34213402-7F69-4B50-AB8A-07B5412D9B09@broadcom.com>
<e8df97c3c3f546af8816182e33dbee11@IL-EXCH01.marvell.com>
<DBXPR07MB12894C922CA3A5B90B610E3AC4A0@DBXPR07MB128.eurprd07.prod.outlook.com>
<12F3AA56-7BDF-471E-8D69-225631B83187@broadcom.com>
In-Reply-To: <12F3AA56-7BDF-471E-8D69-225631B83187@broadcom.com>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.46.110.179]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-CFilter-Loop: Reflected
X-Mirapoint-Virus-RAPID-Raw: score=unknown(0),
refid=str=0001.0A020206.58986A95.006B, ss=1, re=0.000, recu=0.000, reip=0.000,
cl=1, cld=1, fgs=0, ip=169.254.4.67,
so=2013-06-18 04:22:30, dmn=2013-03-21 17:37:32
X-Mirapoint-Loop-Id: 828c27ccc76745e1dccbfd9095486f72
Archived-At: <https://mailarchive.ietf.org/arch/msg/detnet-dp-dt/jnfweeZFWFAkQ40ASMwRDp38NQQ>
Cc: "detnet-dp-dt@ietf.org" <detnet-dp-dt@ietf.org>,
Tal Mizrahi <talmi@marvell.com>, 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: Mon, 06 Feb 2017 12:22:52 -0000
Synchronization traffic can be categorized into two cases: 1. Synchronization as a service, high availability can be an advantage for this kind of service Synchronization service is transported from an ingress PE to an egress PE, replication/elimination can optionally be applied between two PEs (i.e., on S-PEs), while all network nodes including PEs and S-PEs are not aware of the sync message themselves (that is, they don't need to process the PTP messages in the service). And the egress PE will terminate and provide a single copy of each sync packet to a destination CE. 2. Synchronization as an infrastructure Since existing technology including SyncE and IEEE 1588 rely heavily on a tree topology to work properly, replication/elimination must not be used in this case. My 2 cents, Yuanlong > -----Original Message----- > From: Detnet-dp-dt [mailto:detnet-dp-dt-bounces@ietf.org] On Behalf Of > Jouni Korhonen > Sent: Wednesday, February 01, 2017 4:25 AM > To: Balázs Varga A > Cc: Loa Andersson; Tal Mizrahi; detnet-dp-dt@ietf.org > Subject: Re: [Detnet-dp-dt] [EXT] Re: Data Plane Approach - Synchronization > Traffic > > Indeed. Not all traffic will receive the replication/elimination service. That is > based on the configuration. > > - Jouni > > > -- > Jouni Korhonen, Broadcom Ltd. > M: +1-408-391-7160 > > > On Jan 31, 2017, at 12:13 PM, Balázs Varga A > <balazs.a.varga@ericsson.com> wrote: > > > > Hi, > > For sync usually we need hop-by-hop forwarding. > > So it is not clear why to consider replication (and elimination) at all? > > Cheers > > Bala'zs > > > > -----Original Message----- > > From: Detnet-dp-dt [mailto:detnet-dp-dt-bounces@ietf.org] On Behalf Of > > Tal Mizrahi > > Sent: Friday, January 27, 2017 8:37 AM > > To: Jouni Korhonen <jouni.korhonen@broadcom.com> > > Cc: detnet-dp-dt@ietf.org; Loa Andersson <loa@pi.nu> > > Subject: Re: [Detnet-dp-dt] [EXT] Re: Data Plane Approach - > > Synchronization Traffic > > > >> In a path redundancy case would the PTP messages on multiple paths be > >> exact copies a single origin PTP message or different PTP messages? > > > > They would be two different PTP messages. > > This implies that we would not like PTP packets to be subject to replication > and elimination. > > > > Tal. > > > > > >> -----Original Message----- > >> From: Jouni Korhonen [mailto:jouni.korhonen@broadcom.com] > >> Sent: Thursday, January 26, 2017 8:40 PM > >> To: Tal Mizrahi > >> Cc: Loa Andersson; detnet-dp-dt@ietf.org > >> Subject: Re: [Detnet-dp-dt] [EXT] Re: Data Plane Approach - > >> Synchronization Traffic > >> > >> > >> > >>> 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 mailing list > > Detnet-dp-dt@ietf.org > > https://www.ietf.org/mailman/listinfo/detnet-dp-dt > > _______________________________________________ > 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