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

Loa Andersson <loa@pi.nu> Wed, 04 November 2015 08:52 UTC

Return-Path: <loa@pi.nu>
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 EF1221B2A79 for <mpls@ietfa.amsl.com>; Wed, 4 Nov 2015 00:52:57 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.91
X-Spam-Level:
X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, T_RP_MATCHES_RCVD=-0.01] 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 OimSaeIoXQJX for <mpls@ietfa.amsl.com>; Wed, 4 Nov 2015 00:52:55 -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 94EA41B2A5C for <mpls@ietf.org>; Wed, 4 Nov 2015 00:52:55 -0800 (PST)
Received: from [133.93.24.128] (unknown [133.93.24.128]) (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 400451801556; Wed, 4 Nov 2015 09:52:52 +0100 (CET)
To: Lizhenbin <lizhenbin@huawei.com>, "mpls@ietf.org" <mpls@ietf.org>
References: <5A5B4DE12C0DAC44AF501CD9A2B01A8D8CA63EA4@nkgeml506-mbx.china.huawei.com>
From: Loa Andersson <loa@pi.nu>
Message-ID: <5639C761.2030802@pi.nu>
Date: Wed, 04 Nov 2015 17:52:49 +0900
User-Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.3.0
MIME-Version: 1.0
In-Reply-To: <5A5B4DE12C0DAC44AF501CD9A2B01A8D8CA63EA4@nkgeml506-mbx.china.huawei.com>
Content-Type: text/plain; charset="windows-1252"; format="flowed"
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/mpls/y80mJsvs7Jf6GJm57-5fzkuZGA8>
Subject: Re: [mpls] Solicit Opinions on Definition of MPLS Global Label
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
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: Wed, 04 Nov 2015 08:52:58 -0000

Robin,

One of the label types you list as "global" in your draft is the
Entropy Label. To me it seems that the Entropy Label is scoped by
the label stack and the node(s) doing the hashing on it. WHy do you
think it is "global"?

/Loa



On 2015-11-04 14:26, Lizhenbin wrote:
> Hi MPLSers,
>
> As the development of MPLS technologies, many new label concepts beyond
> RFC3031 are proposed. And in segment routing MPLS label can be
>
> allocated and flooded in the network which means the meaning of the
> lablel can be understood by all nodes in the network. It is totally
> different from
>
> the label distribution behavior of LDP, RSVP-TE, and MP-BGP. From my
> point of view we need not argue if it is global label or global ID. In
> fact, the
>
> possible persons who read the drafts of protocol extensions for segment
> routing which incorporate the label allocation may be confused that MPLS
> WG as
>
> the base of MPLS work seems to have nothing with the work. But the
> challenge of definition of global label truly exists which has been
> proposed in the draft
>
> https://www.ietf.org/id/draft-li-mpls-global-label-usecases-03.txt. Hope
> you can refer to Section 4 of the draft.
>
> The debates on MPLS global label have lasted for a long time. The
> opinions can be classified as following:
>
> Opinion 1: Segment Routing has nothing with global label and please do
> not make it bother MPLS WG. But it seems a little hard to convince some
> MPLSers.
>
> Opinion 2: The usecase truly exists. But the concept of global label is
> too big. It is hard to allocate a label which is unique spanning
> multiple domains or
>
> as IP address which is unique all over world since it is not a scalable
> way or it is hard to achieve the goal. Then maybe it is a better way to
> narrow the
>
> scope to rename the global label as Domain-wide label, Network-wide
> label, etc.
>
> Opinion 3: The global label can be kept to cover more label concepts
> which label behaviors in the control plane and forward plane are
> different form the
>
> traditional LDP/RSVP-TE/MP-BGP.
>
> Since I could not get more time in my presentation to collect your
> opinions, if convenient please help feedback your opinion in your
> mailing list. Hope through
>
> the discussion we can make some consensus.
>
> Best Regards,
>
> Zhenbin(Robin)
>
>
>
> _______________________________________________
> mpls mailing list
> mpls@ietf.org
> https://www.ietf.org/mailman/listinfo/mpls
>