Re: [Detnet-dp-dt] An optional scheme that can support Detnet with a single layer of PW label
Jiangyuanlong <jiangyuanlong@huawei.com> Wed, 22 February 2017 05:56 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 0CBF512961D
for <detnet-dp-dt@ietfa.amsl.com>; Tue, 21 Feb 2017 21:56:53 -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 o9vjU8AOsfXs for <detnet-dp-dt@ietfa.amsl.com>;
Tue, 21 Feb 2017 21:56:51 -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 D9BCB129619
for <detnet-dp-dt@ietf.org>; Tue, 21 Feb 2017 21:56:50 -0800 (PST)
Received: from 172.18.7.190 (EHLO lhreml702-cah.china.huawei.com)
([172.18.7.190])
by lhrrg01-dlp.huawei.com (MOS 4.3.7-GA FastPath queued)
with ESMTP id DHN62412; Wed, 22 Feb 2017 05:56:48 +0000 (GMT)
Received: from SZXEMA413-HUB.china.huawei.com (10.82.72.72) by
lhreml702-cah.china.huawei.com (10.201.108.43) with Microsoft SMTP Server
(TLS) id 14.3.301.0; Wed, 22 Feb 2017 05:56:47 +0000
Received: from SZXEMA506-MBS.china.huawei.com ([169.254.4.67]) by
SZXEMA413-HUB.china.huawei.com ([10.82.72.72]) with mapi id 14.03.0235.001;
Wed, 22 Feb 2017 13:56:43 +0800
From: Jiangyuanlong <jiangyuanlong@huawei.com>
To: Loa Andersson <loa@pi.nu>, Jouni Korhonen <jouni.korhonen@broadcom.com>
Thread-Topic: [Detnet-dp-dt] An optional scheme that can support Detnet with
a single layer of PW label
Thread-Index: AQHSiU7K/u+vUs2FQ0qQNWO2NCqKMqFvX9+AgAAEJICAAAIRAIAAAZUAgAABjACAAAETgIAAAMAAgAPK73CAAK/ggIAAptZw
Date: Wed, 22 Feb 2017 05:56:42 +0000
Message-ID: <3B0A1BED22CAD649A1B3E97BE5DDD68BBAB14200@szxema506-mbs.china.huawei.com>
References: <BDABA4E9-F3F5-4EA3-BB16-BE877A70F0B6@broadcom.com>
<FBC4D57C-51D4-41A8-95D7-56AF22084852@broadcom.com>
<9E4E59F6-0E62-476B-897F-D2D59E94C6EB@broadcom.com>
<f3bbb70a-0f5d-b515-6c5a-1d31ba5ae5a2@pi.nu>
<6F2B8081-ADB8-4B4F-BACD-78DFB63B8FBE@broadcom.com>
<bbfe82c3-5127-31de-01b7-3e6e820d5142@pi.nu>
<EA2608B3-C11A-444B-B1E8-379B8A195B6D@broadcom.com>
<c9e9931d-6f74-9ae0-2e34-e400c5cf92b4@pi.nu>
<AA485196-3AC7-4D0B-BD3A-A61E07AF23D7@broadcom.com>
<3B0A1BED22CAD649A1B3E97BE5DDD68BBAB13DD5@szxema506-mbs.china.huawei.com>
<8722ba32-1e82-88d4-1cb3-29637762400c@pi.nu>
In-Reply-To: <8722ba32-1e82-88d4-1cb3-29637762400c@pi.nu>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.74.203.119]
Content-Type: text/plain; charset="utf-7"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-CFilter-Loop: Reflected
X-Mirapoint-Virus-RAPID-Raw: score=unknown(0),
refid=str=0001.0A090204.58AD2821.0062, 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: d2b82674505f51e053f0d6d2560fa2cc
Archived-At: <https://mailarchive.ietf.org/arch/msg/detnet-dp-dt/GIYWj-ElDAC7XnoWYmilM3vkqbg>
Cc: "detnet-dp-dt@ietf.org" <detnet-dp-dt@ietf.org>
Subject: Re: [Detnet-dp-dt] An optional scheme that can support Detnet with
a single layer of PW label
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: Wed, 22 Feb 2017 05:56:53 -0000
Loa, please see my comments in line. Thanks, Yuanlong -----Original Message----- From: Detnet-dp-dt [mailto:detnet-dp-dt-bounces@ietf.org] On Behalf Of Loa Andersson Sent: Wednesday, February 22, 2017 11:54 AM To: Jiangyuanlong; Jouni Korhonen Cc: detnet-dp-dt@ietf.org Subject: Re: [Detnet-dp-dt] An optional scheme that can support Detnet with a single layer of PW label Yuanlong, Very interesting, and I think we need to spend some time on this. I think you are right bringing up the ingress and egress single point of failure. The drawback is that the CE's gets more complicated. [YJ] Thanks;) This is still MPLS, but I miss the label stacks to understand the processing. And I have one specific question on slide 8. CE1 sends two identical packets to PE1 and PE2, each PE asdd a sequence number, right? After that PE1 sends it packet to the out port for PW1 and D-PW1 and PE2 send its packet to the out port for PW2 and D-PW2. Before the packets are send out on PW1 and PW2, filtering (elimination) takes place. The sequence number is used for that? How do we make sure that the sequence numbers generated by PE1 and PE2 are the same? [YJ] Yes. If CE is 802.1CB compatible, we can use its sequence number directly. Otherwise, a Sequence Generator is needed on a PE attached with AC, how to generate the same seq on two PEs may pose a challenge. Maybe a hash module which takes a whole frame as an input can merely work. Also the filtering functions on PE1 will handle a pair of packets intended for PW1. One of the packets come from the AC in port and the other from the P-PW1 in port, what is used coordinate the packets? [YJ] there is no coordination, but the encapsulation will be the same (all in Ethernet for Ethernet frame). /Loa On 2017-02-21 17:30, Jiangyuanlong wrote: > Hi all, > > The intention of this slide is to provide an optional scheme that can support Detnet with a single layer of PW label. > For the time being the slide demonstrates that it is possible in the data plane. > Your comments are very welcome. > > Best regards, > Yuanlong > > > -----Original Message----- > From: Detnet-dp-dt [mailto:detnet-dp-dt-bounces@ietf.org] On Behalf Of > Jouni Korhonen > Sent: Sunday, February 19, 2017 3:29 PM > To: Loa Andersson > Cc: detnet-dp-dt@ietf.org > Subject: Re: [Detnet-dp-dt] FRER example.. maybe a way forward? was > Re: quick notes from call 2/14/15 > > Loa, > >> On 18 Feb 2017, at 23:26, Loa Andersson <loa@pi.nu> wrote: >> >> >> >> On 2017-02-19 15:22, Jouni Korhonen wrote: >>> >> <snip> >>>> I don't follow - let us say we have one Ethernet and one TDM PW >>>> crossing the domain, id e use the same d-pw label, how do we know >>>> which one we do Ethernet NSP and which one we do TDM NSP on?? >>> >>> Of course each e2e detnet flow have their own d-pw. Otherwise you cannot make a difference between them. Being the same means an e2e detnet flow would have a single d-pw label throughout the detnet/administrative domain in each x-PE. >>> >> OK . so what you are saying is that replicated packets will have the same d-pw? I agree to that! > > Yes. > > - JOuni > >> >> /Loa >>> - Jouni >> <snip> >> -- >> >> >> 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 > -- 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] quick notes from call 2/14/15 Jouni Korhonen
- [Detnet-dp-dt] FRER example.. maybe a way forward… Jouni Korhonen
- Re: [Detnet-dp-dt] FRER example.. maybe a way for… Loa Andersson
- Re: [Detnet-dp-dt] FRER example.. maybe a way for… Jouni Korhonen
- Re: [Detnet-dp-dt] FRER example.. maybe a way for… Loa Andersson
- Re: [Detnet-dp-dt] FRER example.. maybe a way for… Jouni Korhonen
- Re: [Detnet-dp-dt] FRER example.. maybe a way for… Loa Andersson
- Re: [Detnet-dp-dt] FRER example.. maybe a way for… Jouni Korhonen
- Re: [Detnet-dp-dt] FRER example.. maybe a way for… Loa Andersson
- Re: [Detnet-dp-dt] FRER example.. maybe a way for… Jouni Korhonen
- Re: [Detnet-dp-dt] FRER example.. maybe a way for… Loa Andersson
- Re: [Detnet-dp-dt] FRER example.. maybe a way for… Jouni Korhonen
- Re: [Detnet-dp-dt] FRER example.. maybe a way for… Jouni Korhonen
- Re: [Detnet-dp-dt] FRER example.. maybe a way for… Loa Andersson
- [Detnet-dp-dt] An optional scheme that can suppor… Jiangyuanlong
- Re: [Detnet-dp-dt] An optional scheme that can su… Loa Andersson
- Re: [Detnet-dp-dt] An optional scheme that can su… Jouni Korhonen
- Re: [Detnet-dp-dt] An optional scheme that can su… Jiangyuanlong
- Re: [Detnet-dp-dt] An optional scheme that can su… Jiangyuanlong
- Re: [Detnet-dp-dt] FRER example.. maybe a way for… Jiangyuanlong
- Re: [Detnet-dp-dt] FRER example.. maybe a way for… Loa Andersson
- Re: [Detnet-dp-dt] FRER example.. maybe a way for… Jiangyuanlong
- Re: [Detnet-dp-dt] quick notes from call 2/14/15 Jiangyuanlong