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

Loa Andersson <loa@pi.nu> Sun, 15 January 2017 04:09 UTC

Return-Path: <loa@pi.nu>
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 7718F129426 for <detnet-dp-dt@ietfa.amsl.com>; Sat, 14 Jan 2017 20:09:41 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.099
X-Spam-Level:
X-Spam-Status: No, score=-5.099 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-3.199] 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 5WHZNgD7__oR for <detnet-dp-dt@ietfa.amsl.com>; Sat, 14 Jan 2017 20:09:39 -0800 (PST)
Received: from pipi.pi.nu (pipi.pi.nu [83.168.239.141]) (using TLSv1.1 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2460B1293F9 for <detnet-dp-dt@ietf.org>; Sat, 14 Jan 2017 20:09:38 -0800 (PST)
Received: from [192.168.1.11] (unknown [49.150.98.11]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) (Authenticated sender: loa@pi.nu) by pipi.pi.nu (Postfix) with ESMTPSA id 7350C18013DA; Sun, 15 Jan 2017 05:09:30 +0100 (CET)
To: Jiangyuanlong <jiangyuanlong@huawei.com>, "detnet-dp-dt@ietf.org" <detnet-dp-dt@ietf.org>
References: <6ff03919-9584-0a48-da2e-7ded7d2aacbb@pi.nu> <3B0A1BED22CAD649A1B3E97BE5DDD68BBAB073F9@szxema506-mbs.china.huawei.com>
From: Loa Andersson <loa@pi.nu>
Message-ID: <29e16107-3df9-e0a4-e048-d427681acdb5@pi.nu>
Date: Sun, 15 Jan 2017 12:09:19 +0800
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.6.0
MIME-Version: 1.0
In-Reply-To: <3B0A1BED22CAD649A1B3E97BE5DDD68BBAB073F9@szxema506-mbs.china.huawei.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/detnet-dp-dt/QNDuTKPjdwiyFqSe2GRACmurcG0>
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: Sun, 15 Jan 2017 04:09:41 -0000

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?

> 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".

> 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?

  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?

> 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?

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