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

Jouni Korhonen <jouni.korhonen@broadcom.com> Sun, 26 February 2017 05:10 UTC

Return-Path: <jouni.korhonen@broadcom.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 175C71296B1 for <detnet-dp-dt@ietfa.amsl.com>; Sat, 25 Feb 2017 21:10:37 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.001
X-Spam-Level:
X-Spam-Status: No, score=-2.001 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=broadcom.com
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 AnX0evdqBy-K for <detnet-dp-dt@ietfa.amsl.com>; Sat, 25 Feb 2017 21:10:33 -0800 (PST)
Received: from mail-pg0-x231.google.com (mail-pg0-x231.google.com [IPv6:2607:f8b0:400e:c05::231]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id CA81B1295F8 for <detnet-dp-dt@ietf.org>; Sat, 25 Feb 2017 21:10:33 -0800 (PST)
Received: by mail-pg0-x231.google.com with SMTP id q66so3396030pga.0 for <detnet-dp-dt@ietf.org>; Sat, 25 Feb 2017 21:10:33 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=broadcom.com; s=google; h=mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=D7CDTJNOlJGhmh5TVyW6wCuPv8IPWuu++MYXHkCSNIE=; b=aYnqV3zILP8sUC4e2DoXSJyPRV70q3F4XYyMqQq8xynOErHNU6Tl8UL3f2Rg34R+0/ 7JrglcWVxKsGXk9pWZ9eGuNJfOPrBewcRrxlVfUPW376d6BtCigwxjiiZPp1hVInNPul PuRWsKegCpA2fZSqGu4QlQF539NVb5x5f1rgs=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=D7CDTJNOlJGhmh5TVyW6wCuPv8IPWuu++MYXHkCSNIE=; b=jW+J4ZaTS1iuQVhwgnae1FYexGMsqp+cWVBRxrxkFiZwD0PnrEC25M+ntikZegttQb DEmg/tffK06uwn9DCxTW2byMyKroB9Q5OFS7inAMwWJYNQNf82xw44j5FqdXXO0j+SHD TjJe8UmgvLCeYHBWA6wh5Lf4ko9MHRUTUYmeRonirSzvkMdbVmr0rRC4lrAi3kalR0Rj 3pbU3j1PhzayU80n6/A/AiZIx1cisx5WRI7T+kEKdbQ6C7APuRN6Sk0xivjFu9Ys8elN iVR3DpOg/RrVVhyFmc5gcbVSxom1mvzy9yBx26aWQXrIzIt9OBsHntRePUp0amc7y8dh om9Q==
X-Gm-Message-State: AMke39mjv0T1P80jAKbD4tIp7WzwPLRpTzL+BDGWB5cEVgKGSSYwumAf/SuNCPvgJrodLVGW
X-Received: by 10.99.104.198 with SMTP id d189mr13457194pgc.55.1488085833158; Sat, 25 Feb 2017 21:10:33 -0800 (PST)
Received: from ?IPv6:2601:647:4200:e520:34a1:c08d:943c:5932? ([2601:647:4200:e520:34a1:c08d:943c:5932]) by smtp.gmail.com with ESMTPSA id v15sm22937555pfk.99.2017.02.25.21.10.31 (version=TLS1 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Sat, 25 Feb 2017 21:10:31 -0800 (PST)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2104\))
From: Jouni Korhonen <jouni.korhonen@broadcom.com>
In-Reply-To: <eafc40d2-cbeb-2171-e649-377035e5f2d6@pi.nu>
Date: Sat, 25 Feb 2017 21:10:30 -0800
Content-Transfer-Encoding: quoted-printable
Message-Id: <0EBFFCEF-2651-4F1B-A5D8-F36E93EDBA62@broadcom.com>
References: <DBXPR07MB128EDEE38C28B6C894DE489AC500@DBXPR07MB128.eurprd07.prod.outlook.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> <79ABE102-4006-4189-8F20-8A20014C497A@broadcom.com> <eafc40d2-cbeb-2171-e649-377035e5f2d6@pi.nu>
To: Loa Andersson <loa@pi.nu>
X-Mailer: Apple Mail (2.2104)
Archived-At: <https://mailarchive.ietf.org/arch/msg/detnet-dp-dt/W20DFu3oEEQBI5JAB9m23U3b0ds>
Cc: detnet-dp-dt@ietf.org
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: Sun, 26 Feb 2017 05:10:37 -0000

Loa,

Ok. Point taken. Global is bad wording. I try to remember to use e2e from now on.

- Jouni

> On 25 Feb 2017, at 21:05, Loa Andersson <loa@pi.nu> wrote:
> 
> Jouni,
> 
> On 2017-02-26 12:36, Jouni Korhonen wrote:
>> Yuanlong,
>> 
>> 
>>> On 25 Feb 2017, at 02:02, Jiangyuanlong <jiangyuanlong@huawei.com> 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.
>>> [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.
>> 
>> I think you are still getting it wrong what was intended with L-labels. They were specifically thought in the context of detnet global d-pw labels.
> 
> hmmmm -yes, but not in the sense that the mpls wg use "global", the
> special purpose labels are global, they mean the same thing where ever
> you find them. Here we have end-to-end labels, labels that stays the
> same all through the forwarding process in the network.
> 
> /Loa
> 
>> 
>> L-labels connected MS-PW nodes over the network topology. All FRER “triggering” etc is still and has always been tied to the d-pw. Within a S- or T-PE you need to pop the L-label and then inspect the top of stack d-pw label..
>> 
>>                                                 within
>>    LSR                         |------------- S- or T-PE -------------|
>>                    PHP                            POP
>>                  -------->                     -------->
>> +------------+                  +------------+            +------------+
>> |  T-labels  |                  |  L-label   |            | d-pw label |
>> +------------+                  +------------+            +------------+
>> |  L-label   |                  | d-pw label |            |            |
>> +------------+                  +------------+            |  Payload   |
>> | d-pw label |                  |            |            |            |
>> +------------+                  |  Payload   |            +------------+
>> |            |                  |            |
>> |  Payload   |                  +------------+
>> |            |
>> +------------+
>> 
>> 
>> This allowed also bypassing S-PE easily for some L-labels.. instead of an L-label pop one would do a swap and just forward after that.
>> 
>> 
>> - Jouni
>> 
>> 
>>> 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
>>> _______________________________________________
>>> 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
>> 
> 
> -- 
> 
> 
> 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