Re: [mpls] [Bier] [bier] The first nibble issue associated with MPLS encapsulation

Loa Andersson <loa@pi.nu> Fri, 15 April 2016 02:53 UTC

Return-Path: <loa@pi.nu>
X-Original-To: mpls@ietfa.amsl.com
Delivered-To: mpls@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 52B1C12E6DA; Thu, 14 Apr 2016 19:53:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.896
X-Spam-Level:
X-Spam-Status: No, score=-2.896 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.996] 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 XGKEgdpa0p9N; Thu, 14 Apr 2016 19:53:41 -0700 (PDT)
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 40DF312E6D7; Thu, 14 Apr 2016 19:53:41 -0700 (PDT)
Received: from [192.168.1.2] (unknown [122.53.41.246]) (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 0F21A1802AB8; Fri, 15 Apr 2016 04:53:37 +0200 (CEST)
To: Stewart Bryant <stewart.bryant@gmail.com>, "Nagendra Kumar Nainar (naikumar)" <naikumar@cisco.com>, Eric C Rosen <erosen@juniper.net>, Alexander Vainshtein <Alexander.Vainshtein@ecitele.com>
References: <1FEE3F8F5CCDE64C9A8E8F4AD27C19EE0D53871C@NKGEML515-MBX.china.huawei.com> <B664DB14-0A8C-4437-83E3-F9DA6C0DDA61@cisco.com> <mc51yrrf9n0wxbjsrprt9amf.1460143890063@email.android.com> <CA+RyBmXpZ-Kt77TW-=_kPYmahdw_yUHB5xhy8YtYVq2OcRJxbA@mail.gmail.com> <D32DB725.3F57B%cpignata@cisco.com> <CA+RyBmW+qonpScnLOfsGorayCvsS0vrFcn+o5nPvOqCOv9Jc3g@mail.gmail.com> <AM3PR03MB0775C55E5AD3247F373007139D940@AM3PR03MB0775.eurprd03.prod.outlook.com> <570BB266.8090608@juniper.net> <570F6374.6030406@gmail.com> <DB3PR03MB0780B7CE7B96283FB484C2489D970@DB3PR03MB0780.eurprd03.prod.outlook.com> <570F9901.2080406@juniper.net> <D3352203.13D10A%naikumar@cisco.com> <570FB333.5080509@pi.nu> <570FF136.7030600@gmail.com>
From: Loa Andersson <loa@pi.nu>
Message-ID: <571057AE.6090305@pi.nu>
Date: Fri, 15 Apr 2016 10:53:34 +0800
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.7.2
MIME-Version: 1.0
In-Reply-To: <570FF136.7030600@gmail.com>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 8bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/mpls/KLAub4brVsbzFsdLlxfdOD2SCAw>
Cc: "mpls@ietf.org" <mpls@ietf.org>, "bier@ietf.org" <bier@ietf.org>
Subject: Re: [mpls] [Bier] [bier] The first nibble issue associated with MPLS encapsulation
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.17
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: Fri, 15 Apr 2016 02:53:42 -0000

Stewart,

On 2016-04-15 03:36, Stewart Bryant wrote:
>
>
> On 14/04/2016 16:11, Loa Andersson wrote:
>>
>>
>> /Loa
>>
>> On 2016-04-14 22:41, Nagendra Kumar Nainar (naikumar) wrote:
>>> Hi,
>>>
>>> Per IANA registry, 0-1 are ³Reserved² and so is not strictly assigned
>>> with
>>> PW. Something like a modified CW beneath LSE?. Further, BIER is
>>> hop-by-hop
>>> lookup based. So I think we don¹t need to include this always.
>>> Instead, we
>>> could conditionally include this, if the next BFR is tunneled (not
>>> directly connected).
>>>
>>> The receiving node will use the label to identify the payload/FEC. So I
>>> think, the presence of modified CW should not confuse it with PW.
>
> Not quite Loa.
>
> It could be an Ethernet PW with no CW.

Yes - you are right, how much of a problem is this in a P node? Any 
value, except 4 and 6, will stop the P node from doing ECMP/Load
Sharing, right? A P node will never look for the control word.

So an Ethernet PW that carries the same value in the first nibble that
we specify for bier will be treated the same way as a bier packet.
This does not effect the bier packets, and is the right way to treat
the PW.

So where do we have the problem?

BIER would be in the clear, as it will carry any value but 4 or 6
in the first nibble, right?
PWs with control word will have 0 (or 1) and not be effected by a
P node that are doing ECMP/Load Sharing.
Ethernet PWs without control word might have any value in the first
nibble, if there is 4 or 6 a P node might to ECMP/Load Sharing.

It seems to me that specifying the first nibble in a bier packet
would be good, for the time being I don't care if we say 0 or 5.

If there are problems with Ethernet PWs without control word, this
has to be solved in the context of PWs.

/Loa
>
> Stewart