Re: [mpls] how does it work if ....

Loa Andersson <loa@pi.nu> Thu, 25 March 2021 04:57 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 15BD03A0E2A for <mpls@ietfa.amsl.com>; Wed, 24 Mar 2021 21:57:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.898
X-Spam-Level:
X-Spam-Status: No, score=-1.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, NICE_REPLY_A=-0.001, SPF_HELO_NONE=0.001, SPF_NONE=0.001, URIBL_BLOCKED=0.001] 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 54-K7E_ns6fg for <mpls@ietfa.amsl.com>; Wed, 24 Mar 2021 21:56:58 -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 2422D3A0E2D for <mpls@ietf.org>; Wed, 24 Mar 2021 21:56:57 -0700 (PDT)
Received: from [192.168.1.11] (unknown [124.104.184.212]) (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 68846325097; Thu, 25 Mar 2021 05:56:55 +0100 (CET)
To: Stewart Bryant <stewart.bryant@gmail.com>
Cc: "mpls@ietf.org" <mpls@ietf.org>, Kireeti Kompella <kireeti.kompella@gmail.com>
References: <1c87c917-5860-8efe-c640-7bd5cd548190@pi.nu> <D1E90F58-1E68-4B0D-8092-6EB5EEA8783C@gmail.com>
From: Loa Andersson <loa@pi.nu>
Message-ID: <a2b22460-39b8-882e-7e88-26c0a8dbb8d8@pi.nu>
Date: Thu, 25 Mar 2021 12:56:51 +0800
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101 Thunderbird/78.8.1
MIME-Version: 1.0
In-Reply-To: <D1E90F58-1E68-4B0D-8092-6EB5EEA8783C@gmail.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/mpls/QfgVSi6w6VMDyzhrCKr-5P_yo20>
Subject: Re: [mpls] how does it work if ....
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.29
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: Thu, 25 Mar 2021 04:57:03 -0000

Stewart,

inline please.

On 18/03/2021 00:34, Stewart Bryant wrote:
> You only pop the label to see the xSPL if you are the destination.

What do you mean by "destination", are you referring to the node that 
will pop the top label with the SPLs encoding information beneath? I we 
disable the PHP, thast would be the PE, right?

So that mean that we can't encode HbH behavior?

And info theat relates to forwarding is also not very useful, since the 
packet reached its destination.
> 
> If you do not know about the xSPL you should not have been sent the packet in the first place. That would be a routing/control plane failure.

So we need some type of mechanism that tells potential ingress LER's 
which of its reachable are capable to extract inf from SPL's?

/Loa
> 
> If you receive it by mistake, and consider that it is for you (unlikely but possible) so you pop the label, you will find an unknown xSPL and presumably drop the packet.
> 
> So I that is safe.
> 
> What is going to be difficult is with one of Kireeti’s reused Els. That will work fine at a P router, but a PE is going to not process the packet properly. This cannot be a PW or Detnet since that has another label as a gatekeeper, so we nee think what happens if it is an IP packet, in which case the ECMP defeat nibble will be found. This should be unexpected, so the packet will be dropped.
> 
> If there is an old P router that does not understand the xSPL it will just swap and forward as before.
> 
> You can always program a P router not to PHP (we did that with MPLS-TP for example). It is more work for the receiving PE, but it needs to be capable of dealing with that or it should not be used in that role with this label stack.
> 
> So assuming that Kireeti and I have the same vision of how this works, it looks safe to me. However we have to look at every corner and strong exception to validate the approach.
> 
> Stewart
> 
> 
> 
>> On 17 Mar 2021, at 14:18, Loa Andersson <loa@pi.nu> wrote:
>>
>> Kireeti,
>>
>> I'm looking at your slides from the joint meeting, in particular slide #3, where you say at thye bottom:
>>
>>   "Corollary: such labels MUST NOT reach the top of stack (by popping
>>    labels above them)"
>>
>> How is that backwards compatible.
>>
>> If you  have an old LSR, that don't know to look at the bSPL or eSPL underneath the top label. I assume that the top label will be swapped and the packet forwarded.
>>
>> What is the pen-ultimate LSR is "old" and just pop the top label, how can the PE sort this out?
>>
>> /Loa
>> -- 
>>
>> Loa Andersson                        email: loa@pi.nu
>> Senior MPLS Expert                          loa.pi.nu@gmail.com
>> Bronze Dragon Consulting             phone: +46 739 81 21 64
>>
>> _______________________________________________
>> mpls mailing list
>> mpls@ietf.org
>> https://www.ietf.org/mailman/listinfo/mpls
> 

-- 

Loa Andersson                        email: loa@pi.nu
Senior MPLS Expert                          loa.pi.nu@gmail.com
Bronze Dragon Consulting             phone: +46 739 81 21 64