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

Loa Andersson <loa.pi.nu@gmail.com> Wed, 17 March 2021 18:32 UTC

Return-Path: <loa.pi.nu@gmail.com>
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 598FD3A1073 for <mpls@ietfa.amsl.com>; Wed, 17 Mar 2021 11:32:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.098
X-Spam-Level:
X-Spam-Status: No, score=-2.098 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 CMpARYeQD3tS for <mpls@ietfa.amsl.com>; Wed, 17 Mar 2021 11:32:16 -0700 (PDT)
Received: from mail-pj1-x1033.google.com (mail-pj1-x1033.google.com [IPv6:2607:f8b0:4864:20::1033]) (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 A49873A1072 for <mpls@ietf.org>; Wed, 17 Mar 2021 11:32:16 -0700 (PDT)
Received: by mail-pj1-x1033.google.com with SMTP id ot17-20020a17090b3b51b0290109c9ac3c34so1440895pjb.4 for <mpls@ietf.org>; Wed, 17 Mar 2021 11:32:16 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=content-transfer-encoding:from:mime-version:subject:date:message-id :references:cc:in-reply-to:to; bh=qcvLS1fKECgfb2I4e71evdB9dZkSEW4TwRowyYYaP8Y=; b=FPjNTXVkexwGMaQ3ZU7gHX9pDIhUB6hmcxaUGkzyWoAPVr1ZJkMcVpAa1xUrhmg/pD LFSU1kMYukKYmdVnjs9Ptc59opzQNsRJBEBqKTl88u8HQrXQNBrulFkCBwMtxuQdrSV7 thpDBYCxxFNebEqxtBPtF2ZZ2Tan992EHp3JidxnKJZ7YJfFQrpY18drrlnYnpYSMFa0 d6mL2KN9/UlT88+rrrNkd7Rs8x1B4LYLJBbNOmRtWCC/nvVsGLt3g9G8TGWjv+ozZrWd L4eCQuR3Kvq3okJ0GiRXVdKo+Im6IyQ/ZPJlt2fyuaAtsfyOhIEf/n2YWq0sE3Uf4OYs QUMg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:content-transfer-encoding:from:mime-version :subject:date:message-id:references:cc:in-reply-to:to; bh=qcvLS1fKECgfb2I4e71evdB9dZkSEW4TwRowyYYaP8Y=; b=KxKtiT7JGTlV1uc/MbG66jXUzd0ESUdchPa8DOA/XrxMM2R8l4IQU5W0jkgKVxVPdo qTLBv9f5t8GZvfRIlceUmdL6HdFGvDYjv1PLBRPGpsOL5Vqk9GTnxogZuIpPrwlUACmQ cuoIvU+6Wzpe+4vW9KPxDvE9QRqVKWUhofPojiDckNCbjRpfaJdlQAmoSxayb4n1QZE9 59rbedYNVEPyqP1FGPs4GykNQolKAgUK3JimLrz6Rtn8U2N0Kiczjim08+fW72WtCgaY +LAfNKMQYKXQIjOsw5j7CMK/6qltQSNzeWw+VTnnXqmbbnnxgNNG/VLS5noYrKPnnTKF /1aQ==
X-Gm-Message-State: AOAM533me1yfFoCw2EBfUwi+oCv8q9LVSXELH54KA6YVRr4u5nfkpHDi SKXnI6p/l3I6YZPPcgDrCIFOU5RBOgY=
X-Google-Smtp-Source: ABdhPJwk3NDQD13oTvnXbm3FjDNm4seMaRoBSlrVVifj3s7DhhoYe7NrQCPhp8VwOeXwwrWHso8GOA==
X-Received: by 2002:a17:90a:be09:: with SMTP id a9mr140851pjs.219.1616005935168; Wed, 17 Mar 2021 11:32:15 -0700 (PDT)
Received: from [192.168.1.42] ([124.104.184.212]) by smtp.gmail.com with ESMTPSA id g26sm19784771pfi.38.2021.03.17.11.32.13 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Wed, 17 Mar 2021 11:32:14 -0700 (PDT)
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
From: Loa Andersson <loa.pi.nu@gmail.com>
Mime-Version: 1.0 (1.0)
Date: Thu, 18 Mar 2021 02:32:10 +0800
Message-Id: <478A51B3-62CD-4FEB-816E-0BE1686F7F36@gmail.com>
References: <D1E90F58-1E68-4B0D-8092-6EB5EEA8783C@gmail.com>
Cc: loa Andersson <loa@pi.nu>, mpls@ietf.org
In-Reply-To: <D1E90F58-1E68-4B0D-8092-6EB5EEA8783C@gmail.com>
To: Stewart Bryant <stewart.bryant@gmail.com>
X-Mailer: iPad Mail (18C66)
Archived-At: <https://mailarchive.ietf.org/arch/msg/mpls/JR6YF7aEu0WDYFBFb8dRWv_I2Uk>
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: Wed, 17 Mar 2021 18:32:18 -0000

Stewart,

Sent from my iPad

> On 18 Mar 2021, at 00:35, Stewart Bryant <stewart.bryant@gmail.com> wrote:
> 
> You only pop the label to see the xSPL if you are the destination.

So HbH iOAM does not work?

/Loa
> 
> 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.
> 
> 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
> 
> _______________________________________________
> mpls mailing list
> mpls@ietf.org
> https://www.ietf.org/mailman/listinfo/mpls