Re: [Detnet-dp-dt] a quick look at the replication/discarding case for detnet flows

Jiangyuanlong <jiangyuanlong@huawei.com> Mon, 16 January 2017 13:05 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 5AB011299E5 for <detnet-dp-dt@ietfa.amsl.com>; Mon, 16 Jan 2017 05:05:20 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.42
X-Spam-Level:
X-Spam-Status: No, score=-7.42 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=-3.199, 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 kjXdN5YuEgEz for <detnet-dp-dt@ietfa.amsl.com>; Mon, 16 Jan 2017 05:05:18 -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 E95B9129479 for <detnet-dp-dt@ietf.org>; Mon, 16 Jan 2017 05:04:45 -0800 (PST)
Received: from 172.18.7.190 (EHLO lhreml704-cah.china.huawei.com) ([172.18.7.190]) by lhrrg02-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id CYW36670; Mon, 16 Jan 2017 13:04:43 +0000 (GMT)
Received: from SZXEMA419-HUB.china.huawei.com (10.82.72.37) by lhreml704-cah.china.huawei.com (10.201.5.130) with Microsoft SMTP Server (TLS) id 14.3.301.0; Mon, 16 Jan 2017 13:04:42 +0000
Received: from SZXEMA506-MBS.china.huawei.com ([169.254.4.67]) by SZXEMA419-HUB.china.huawei.com ([10.82.72.37]) with mapi id 14.03.0235.001; Mon, 16 Jan 2017 21:02:47 +0800
From: Jiangyuanlong <jiangyuanlong@huawei.com>
To: Loa Andersson <loa@pi.nu>, "detnet-dp-dt@ietf.org" <detnet-dp-dt@ietf.org>
Thread-Topic: [Detnet-dp-dt] a quick look at the replication/discarding case for detnet flows
Thread-Index: AQHSblvFkivN1LZA80eVWb/wpvr32KE4Z3WAgAKk9YA=
Date: Mon, 16 Jan 2017 13:02:46 +0000
Message-ID: <3B0A1BED22CAD649A1B3E97BE5DDD68BBAB07B31@szxema506-mbs.china.huawei.com>
References: <6ff03919-9584-0a48-da2e-7ded7d2aacbb@pi.nu> <3B0A1BED22CAD649A1B3E97BE5DDD68BBAB073F9@szxema506-mbs.china.huawei.com> <29e16107-3df9-e0a4-e048-d427681acdb5@pi.nu>
In-Reply-To: <29e16107-3df9-e0a4-e048-d427681acdb5@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-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-CFilter-Loop: Reflected
X-Mirapoint-Virus-RAPID-Raw: score=unknown(0), refid=str=0001.0A090202.587CC4EB.0134, 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: fc3f31507f99c14e4b9aede96e4b7628
Archived-At: <https://mailarchive.ietf.org/arch/msg/detnet-dp-dt/4tpvEbQMW46-Wh2AX2OHQTtJqYg>
Subject: Re: [Detnet-dp-dt] a quick look at the replication/discarding case for detnet flows
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, 16 Jan 2017 13:05:20 -0000

Loa, please see my comments inline.
I also have a question on the availability requirements of the DetNet, do we need to prevent any single point of failure in the whole MPLS network?

Thanks
Yuanlong

-----Original Message-----
From: Loa Andersson [mailto:loa@pi.nu] 
Sent: Sunday, January 15, 2017 12:09 PM
To: Jiangyuanlong; detnet-dp-dt@ietf.org
Subject: Re: [Detnet-dp-dt] a quick look at the replication/discarding case for detnet flows

Yuanlong,


On 2017-01-14 19:45, Jiangyuanlong wrote:
> Loa,
>
> Thank a lot for the slides, a very good start!

Tnx!

> Maybe we just need one layer of PW label,

Currently I dob't see how this would work, can you explain plz?
[YJ] I will prepare a slide to explain the details. It may take a couple of days.

> while redefine the MS-PW paradigm to support DetNet data plane.

This a very tricky approach, we would need to "tweak" the paradigm in a backwards compatibel way.
I tend to think that if we add replication and discarding at merege point this is a big enough "tweak".
[YJ] yes, we need to introduce a new data plane mechanism to support this function.

> The T-PEs as defined in the PWE3 can encapsulate/de-capsulate the 
> DetNet frames,

yes - the PW paradigm allows you to add whatever encapsulation we need.

  and generate the sequence number.

Yes the function is there to guarantee that packets are not re-ordred.

> The S-PEs usually can swap the PW label or terminate the PW 
> completely;

wouldn't terminating the PW make the S-PE into a T-PE, isn't at the core of the definition of S-PE and T-PE?
[YJ] Swapping is normal, and terminating is unnecessary. Though the S-PE may need to look into the PW control word to get the sequence number of the packet.

  we can extend their operations to support replication and filtering based on the sequence number.

I - think yes, that cam be done, but I don't see that filtering on the sequence number is enough, some context (e.g. label) is needed, right?
[YJ] Yes, some lattice PW connectivity such as introduced in draft-ietf-pals-mpls-tp-dual-homing-protection may be needed. These lattice PW can be dynamically established for the DetNet service.

> LSP FECs can work as in the traditional MPLS,

yes they will, but I thought that the consensus in the meeting were that we don't want non-detnet traffic sharing the transport of detnet, right?
[YJ] maybe I got it wrong, but my understanding is: the DetNet PW is exclusively used for DetNet services, though the MPLS network can still carry non-detnet services. Maybe the service providers have more to say on this topic:)

but if any new DetNet mechanism is needed in P nodes in the future, we can also add new FECs quite conveniently.

Yes it can be done, but I think we need from the start to avoid piggy- backing of non-detnet traffic.

/Loa


>
> Thanks,
> Yuanlong
>
>
>
> -----Original Message-----
> From: Detnet-dp-dt [mailto:detnet-dp-dt-bounces@ietf.org] On Behalf Of 
> Loa Andersson
> Sent: Saturday, January 14, 2017 12:29 PM
> To: detnet-dp-dt@ietf.org
> Subject: [Detnet-dp-dt] a quick look at the replication/discarding 
> case for detnet flows
>
> Folks,
>
> I took a quick look at the replication / discarding case we talked about at the meeting this week.
>
> Please remember that so far this is not a proposal, just a demonstration that there is at least one way of doing it.
>
> What is there can bee revised, improved, changed or discarded if we find something better. Take a look a send comments.
>
> /loa
>
> Warning: I have a grave case of dyslexia, so any odd or inventive spelling is pure accident.
>

-- 


Loa Andersson                        email: loa@mail01.huawei.com
Senior MPLS Expert                          loa@pi.nu
Huawei Technologies (consultant)     phone: +46 739 81 21 64