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

Jouni Korhonen <jouni.korhonen@broadcom.com> Sat, 25 February 2017 07:23 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 7D675129528 for <detnet-dp-dt@ietfa.amsl.com>; Fri, 24 Feb 2017 23:23:33 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 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, URIBL_BLOCKED=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 Ip2kVwQ7WemW for <detnet-dp-dt@ietfa.amsl.com>; Fri, 24 Feb 2017 23:23:32 -0800 (PST)
Received: from mail-pg0-x22c.google.com (mail-pg0-x22c.google.com [IPv6:2607:f8b0:400e:c05::22c]) (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 E4C11129428 for <detnet-dp-dt@ietf.org>; Fri, 24 Feb 2017 23:23:31 -0800 (PST)
Received: by mail-pg0-x22c.google.com with SMTP id 1so21067157pgi.1 for <detnet-dp-dt@ietf.org>; Fri, 24 Feb 2017 23:23:31 -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=U/78dqDdg92+G4kyQbwdxj+edrdtCrx0o/XIyLf/BLs=; b=PUSwhyANT5VLnnCuHxrWOC2aPUCkYU51uOIG7BbopI9q+Q/xtcv3XU0CPTiJwH15K7 vH+0df9niIYp1dgz06R8RwyRBrM1suovesXa/o4VeXITNzjOgzqJ4Y1u5HvIhm3BGJos Ekxaxo+BRRkNz2VpYFGPxqmZqfyUBgWtCXCnU=
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=U/78dqDdg92+G4kyQbwdxj+edrdtCrx0o/XIyLf/BLs=; b=LZpngmSWDo50RQG/i5F32u2SsITJJrAGEoGXwpf4Y9SDjzgU1BPJSLnF6X7tO+Qr6W aOlNtf8/uAlT9niq6wX4TQGaYcbjWORE4LqM+8mtzqOY/6TPo3RBl7Cv1Y/1JTG4FrQD n4JBKyg/Xs2e0y3SUTbzwhhSIozXjj4m32cyT+ZT9t4oBtzLIbQA36lt4fmryLFE8MEP l10vFYyjU9haYtr5YoHBHaicvcDIuUpY1HBA+ESRBeQ6trNmv1S7hRYo0PeFbNPsjk8M 5jWFJXOlPoL86imRfpweN2ZJ7nhiYan1DTvs3x4M2dm6he8drSBdFHSxah7HXJLrOU04 UMhA==
X-Gm-Message-State: AMke39l/WB0gfwYDeap7K3xVNcrwLncUkYbdefK5wPCMulDj3ailfD3nSguE+HnCpEpktcxb
X-Received: by 10.99.108.74 with SMTP id h71mr8257921pgc.99.1488007411349; Fri, 24 Feb 2017 23:23:31 -0800 (PST)
Received: from ?IPv6:2601:647:4200:e520:7c26:8e92:cc03:79ae? ([2601:647:4200:e520:7c26:8e92:cc03:79ae]) by smtp.gmail.com with ESMTPSA id m3sm18659395pfc.66.2017.02.24.23.23.30 (version=TLS1 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Fri, 24 Feb 2017 23:23:30 -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: <3B0A1BED22CAD649A1B3E97BE5DDD68BBAB150A7@szxema506-mbs.china.huawei.com>
Date: Fri, 24 Feb 2017 23:23:28 -0800
Content-Transfer-Encoding: quoted-printable
Message-Id: <7528644F-0D28-421F-99B7-91A109E04BE1@broadcom.com>
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>
To: Jiangyuanlong <jiangyuanlong@huawei.com>
X-Mailer: Apple Mail (2.2104)
Archived-At: <https://mailarchive.ietf.org/arch/msg/detnet-dp-dt/Sp8_VhTdTr7fzpn6m_RHulCOaEA>
Cc: "detnet-dp-dt@ietf.org" <detnet-dp-dt@ietf.org>, Loa Andersson <loa@pi.nu>
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 07:23:33 -0000

Hi,

> On 24 Feb 2017, at 23:18, Jiangyuanlong <jiangyuanlong@huawei.com> 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.

Ok. Just note that alternative 1 also looks into d-pw label etc. There is no difference regarding FRER logic in that sense. The T-PE or S-PE just has to pop L-Label _within_ the node before it looks into d-pw.

- Jouni


> 
> -----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
> _______________________________________________
> Detnet-dp-dt mailing list
> Detnet-dp-dt@ietf.org
> https://www.ietf.org/mailman/listinfo/detnet-dp-dt