Re: [Detnet-dp-dt] Using MS-PW concept for the d-pw

Loa Andersson <loa@pi.nu> Sat, 25 February 2017 10:30 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 62CFD129CFC for <detnet-dp-dt@ietfa.amsl.com>; Sat, 25 Feb 2017 02:30:12 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.001, URIBL_BLOCKED=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 RPspx4qcEBEI for <detnet-dp-dt@ietfa.amsl.com>; Sat, 25 Feb 2017 02:30:10 -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 2F33B129CB0 for <detnet-dp-dt@ietf.org>; Sat, 25 Feb 2017 02:30:10 -0800 (PST)
Received: from [192.168.1.11] (unknown [122.52.25.23]) (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 38E8A1801590 for <detnet-dp-dt@ietf.org>; Sat, 25 Feb 2017 11:30:07 +0100 (CET)
To: detnet-dp-dt@ietf.org
References: <DBXPR07MB128EDEE38C28B6C894DE489AC500@DBXPR07MB128.eurprd07.prod.outlook.com> <7FF14334-F3A3-4051-BAFF-750C6F70FE1A@broadcom.com> <DBXPR07MB128C5BF67FE7AC3266D868BAC530@DBXPR07MB128.eurprd07.prod.outlook.com> <3B0A1BED22CAD649A1B3E97BE5DDD68BBAB149ED@szxema506-mbs.china.huawei.com> <7F3B3F19-4929-485C-9434-86D6E7FDB915@broadcom.com> <3B0A1BED22CAD649A1B3E97BE5DDD68BBAB14A38@szxema506-mbs.china.huawei.com> <a27bcbab-5410-3209-fead-a178c03f89cb@pi.nu> <3B0A1BED22CAD649A1B3E97BE5DDD68BBAB14AA3@szxema506-mbs.china.huawei.com> <a9cc73c9-0cd4-71d3-c302-8b4c01d40c10@pi.nu> <11302639-28CA-469B-A7B1-AB891C14218D@broadcom.com> <3B0A1BED22CAD649A1B3E97BE5DDD68BBAB15004@szxema506-mbs.china.huawei.com> <3A2B8D75-265B-4D7F-8F20-1F9692F326C0@broadcom.com> <3B0A1BED22CAD649A1B3E97BE5DDD68BBAB150A7@szxema506-mbs.china.huawei.com> <bbebda63-fe68-5073-6cb6-0c099c7a6d21@pi.nu> <3B0A1BED22CAD649A1B3E97BE5DDD68BBAB1519F@szxema506-mbs.china.huawei.com>
From: Loa Andersson <loa@pi.nu>
Message-ID: <bdffadb9-6885-c20a-ced1-9366104e931e@pi.nu>
Date: Sat, 25 Feb 2017 18:30:04 +0800
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.7.1
MIME-Version: 1.0
In-Reply-To: <3B0A1BED22CAD649A1B3E97BE5DDD68BBAB1519F@szxema506-mbs.china.huawei.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/detnet-dp-dt/T4PzsGshuQAf1fYSrEQ_21Xx1RA>
Subject: Re: [Detnet-dp-dt] Using MS-PW concept for the d-pw
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: Sat, 25 Feb 2017 10:30:12 -0000

Yuanlong,


On 2017-02-25 18:02, Jiangyuanlong wrote:
> Loa,
>
> -----Original Message-----
> From: Loa Andersson [mailto:loa@pi.nu]
> Sent: Saturday, February 25, 2017 3:34 PM
> To: Jiangyuanlong; Jouni Korhonen
> Cc: detnet-dp-dt@ietf.org
> Subject: Re: [Detnet-dp-dt] Using MS-PW concept for the d-pw
>
> Yuanlong,
>
> The L-laabel is ther to make the the intermediate not (S-PE) know what to do whit the packet, the d-pw label was not allocated by the S-PE, so it does not ahve any knowledge what it means.
> [YJ] d-pw can be allocated by the S-PE in MS-PW, just as you would like to allocate the L-labels. Very similarly, I think the same T-LDP protocol can be used.

If you do that the S-PE will swap the d-pw, packets will come in from
two different directions with differnt d-pws to the egress, and there
is no way for the egress to identify packets to eliminate.

/Loa
and the egress will have no way

> [YJ] As I said in the previous email, using PW to trigger FRER will be cleaner

compared with using L-label since CW is inspected.
>
> If you let the S-PEs allocate and swap d-pw's, the next S-PE or a T-PE can't coordinate for the same packet coming in on from tow different nodes.
> [YJ] It's like the 1+1 PW protection case, though the operations of elimination and replication in the S-PE and the T-PE need to be specified.
> [YJ]Take VPLS as an example, several PWs can be directed into the same VSI in a PE and PW packets are processed there (for detnet, the processing is FRER now).
>
> But I feel like we are going in circles, can we agree on the corner stones first?
>
> Do we want all possible/conceivable control mechanism be within scope?
> [YJ] maybe we can take LDP as a first step. It seems the difficulty is how to decide the S-PEs for a detnet flow (a routing protocol may be needed for automatic selection).
> [YJ] if all T-PEs and S-PEs are determined for a detnet flow, it is quite easy to set up PW segments and LSPs respectively with the help of LDP protocol.
> Cheers,
> Yuanlong
>
> /Loa
>
>
> On 2017-02-25 15:18, Jiangyuanlong wrote:
>> I agreed to alternative 2. L-label is not needed, S-PE must look into the PW label (further, extract sequence number in the CW) of a packet, and all FRER semantics can be coupled with the PW label.
>>
>> -----Original Message-----
>> From: Jouni Korhonen [mailto:jouni.korhonen@broadcom.com]
>> Sent: Saturday, February 25, 2017 3:07 PM
>> To: Jiangyuanlong
>> Cc: detnet-dp-dt@ietf.org; Loa Andersson
>> Subject: Re: [Detnet-dp-dt] Using MS-PW concept for the d-pw
>>
>> Hi,
>>
>>> [YJ] I regard the L-Labels and T-labels are the same LSP layer. If we look into the full MPLS label stack of a packet in a PW, normally there is an LSP label at the top (unless PHP is enabled for the last hop).
>>> Not sure what is the L-Label in your picture, is it different from LSP label?
>>
>> L-labels have been so far in the discussion between MS-PW PEs.
>> T-labels are between any LSR. L-labels are not PHPed i.e., even if PHP
>> is enable the L-Label stays and the label above it gets popped (that
>> we have been referring as T-Labels). T- and L-labels are just a naming
>> convention. IF you don’t have “between MS-PW PEs” semantic associated
>> with the L-Label, it is the same as T-Label ;)
>>
>>
>>
>> case L-labels are present.. (alternative 1)
>>
>>                      PHP
>>                    -------->
>> +------------+                  +------------+
>> |  T-labels  |                  |  L-label   |
>> +------------+                  +------------+
>> |  L-label   |                  | d-pw label |
>> +------------+                  +------------+
>> | d-pw label |                  |            |
>> +------------+                  |  Payload   |
>> |            |                  |            |
>> |  Payload   |                  +------------+
>> |            |
>> +------------+
>>
>> case no L-labels.. (alternative 2.. and also alternative 3 if you
>> think T- and L-labels are the same)
>>
>>                      PHP
>>                    -------->
>> +------------+                  +------------+
>> |  T-labels  |                  | d-pw label |
>> +------------+                  +------------+
>> | d-pw label |                  |            |
>> +------------+                  |  Payload   |
>> |            |                  |            |
>> |  Payload   |                  +------------+
>> |            |
>> +------------+
>>
>>
>>
>>
>>
>> - Jouni
>>
>

-- 


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