Re: [mpls] Solicit Opinions on Definition of MPLS Global Label

Stewart Bryant <stewart.bryant@gmail.com> Mon, 09 November 2015 13:37 UTC

Return-Path: <stewart.bryant@gmail.com>
X-Original-To: mpls@ietfa.amsl.com
Delivered-To: mpls@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EF0C71B7CC3 for <mpls@ietfa.amsl.com>; Mon, 9 Nov 2015 05:37:33 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=ham
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 ydDJKVaEmlX8 for <mpls@ietfa.amsl.com>; Mon, 9 Nov 2015 05:37:32 -0800 (PST)
Received: from mail-wm0-x22b.google.com (mail-wm0-x22b.google.com [IPv6:2a00:1450:400c:c09::22b]) (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 21C8C1B7CC4 for <mpls@ietf.org>; Mon, 9 Nov 2015 05:37:32 -0800 (PST)
Received: by wmec201 with SMTP id c201so79601778wme.0 for <mpls@ietf.org>; Mon, 09 Nov 2015 05:37:30 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=reply-to:subject:references:to:cc:from:message-id:date:user-agent :mime-version:in-reply-to:content-type; bh=ANJ2iCW1FqT1r3rggDiKq3uP+nH3X3LF9BMofzsQrHE=; b=Y9tD3wYbqShkfbCW+w36LuF1PX1VSv4YbR2fg+VmI4FNpYZD3Cbw6YPLiYDCgX12Ne IxUJDxogEVPZe915RaYnBZxcElYGxvn29kIG6DH0lv0txIAnz9Ndpj3gkJC0wGvidAYN 0cenfvX5zh5SF6y3es+L+HOrzde3YoDckU7197mMpeuyePhof0IpHJTVzEh2XJNFv8EQ JB2A0G98LD0wFYYtvlDHgr30nwS/dUtJ8rpG3Hq9ig/BptsS1PYyXTRam/6keBitDDJe brA+QW+mnNZ7SGyCTE98Q28jVwnYnh3mrgXCeyadG81IwIVegAHvswr+2DSwd4EQYGCv czKg==
X-Received: by 10.194.179.101 with SMTP id df5mr29216954wjc.60.1447076250733; Mon, 09 Nov 2015 05:37:30 -0800 (PST)
Received: from [10.55.98.183] ([173.38.220.51]) by smtp.gmail.com with ESMTPSA id 20sm14375930wmh.8.2015.11.09.05.37.29 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 09 Nov 2015 05:37:29 -0800 (PST)
References: <5A5B4DE12C0DAC44AF501CD9A2B01A8D8CA63EA4@nkgeml506-mbx.china.huawei.com> <6524_1446618416_5639A530_6524_1437_1_53C29892C857584299CBF5D05346208A0F69BE62@OPEXCLILM21.corporate.adroot.infra.ftgroup> <5A5B4DE12C0DAC44AF501CD9A2B01A8D8CA649D5@nkgeml506-mbx.china.huawei.com> <7744_1446734757_563B6BA5_7744_365_1_53C29892C857584299CBF5D05346208A0F6AAABE@OPEXCLILM21.corporate.adroot.infra.ftgroup>
To: Lizhenbin <lizhenbin@huawei.com>
From: Stewart Bryant <stewart.bryant@gmail.com>
Message-ID: <5640A198.1030503@gmail.com>
Date: Mon, 09 Nov 2015 13:37:28 +0000
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:38.0) Gecko/20100101 Thunderbird/38.3.0
MIME-Version: 1.0
In-Reply-To: <7744_1446734757_563B6BA5_7744_365_1_53C29892C857584299CBF5D05346208A0F6AAABE@OPEXCLILM21.corporate.adroot.infra.ftgroup>
Content-Type: multipart/alternative; boundary="------------000109000500050700090400"
Archived-At: <http://mailarchive.ietf.org/arch/msg/mpls/1PSQx0UD09PZMMorGvavqj2HwSU>
Cc: "mpls@ietf.org" <mpls@ietf.org>
Subject: Re: [mpls] Solicit Opinions on Definition of MPLS Global Label
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: Stewart Bryant <stewart.bryant@gmail.com>
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mpls>, <mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mpls/>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 09 Nov 2015 13:37:34 -0000

Robin

Others have made many of the points that I would have made
in this discussion of global labels, and I have yet to see a
compelling case emerge.

I am responding to the following from your slide deck:

BGP VPN LSP is another type of multi-point to point
LSP which faces the challenge of the measurement of
packet loss proposed by [I-D.bryant-mpls-synonymous-
flow-labels].

Firstly SL can be made to work in this environment. One of the
points that I have been making is that the SL label exchange can
be thought of as part of the measurement session establishment
protocol and thus works underneath any existing label
advertizement/exchange protocol without disruption to the
existing protocol.

If your concern is that you want to remain within the BGP VPN
paradigm and have an advertizement only method of operation,
with no session, then the advertizing PE could advertise either
a set of labels it wanted to use to map between either a
source/VPN label pair or as a source identifier. Alternatively
you could take a leaf from the SR book use a virtual global
label set and advertise the PE offset in the VPN advertizement.
This latter approach would mean that a single identity was
distributed, but the labels in the stack were scoped to the
destination in conformance with RFC3031.

I will make one other point, and that is *IF* there is a compelling
case for a tagged network layer with truly global labels, then there are
other stack based designs that could be considered, which are possibly
more powerful than the existing MPLS design.  However it is difficult
to imagine a sufficiently compelling commercial case for their
deployment in the near future.

- Stewart