Re: [mpls] MPLS-RT Review of draft-gandhi-mpls-ioam-sr-04

Stewart Bryant <stewart.bryant@gmail.com> Mon, 04 January 2021 16:31 UTC

Return-Path: <stewart.bryant@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 197E53A0E0A; Mon, 4 Jan 2021 08:31:00 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.197
X-Spam-Level:
X-Spam-Status: No, score=-0.197 tagged_above=-999 required=5 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=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 q5Y9BWGeU8U3; Mon, 4 Jan 2021 08:30:58 -0800 (PST)
Received: from mail-wm1-x331.google.com (mail-wm1-x331.google.com [IPv6:2a00:1450:4864:20::331]) (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 7ECA43A0E4A; Mon, 4 Jan 2021 08:30:58 -0800 (PST)
Received: by mail-wm1-x331.google.com with SMTP id 190so19020945wmz.0; Mon, 04 Jan 2021 08:30:58 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=from:message-id:mime-version:subject:date:in-reply-to:cc:to :references; bh=XgdNB3P4uKQMQfhWHU9phbjlTeAnGncXFPj3Wn8SyEA=; b=FD9UStAWbPS8VTumeHxfZdzSVzx4UsqkYEneP+293rcjrik2m2LxUuyh0SCGFMbYDT 5RTz0Qfo/QAr6RZrdIlmuhD1r2owVz9QJg+CmkNPs4Qom3Qyqwu2x9uxF7gJ8gTTCMLp J42/zrD5TS2ge8omSBpOxIfq+m9JpWTBM8XpSUH8cGp/6HzDIxISpDK6fbxb7uA9ZDS5 WPdBAHCFPU8n1pTiysx/ULZkakQQwwZvzG1mGfKNkHbKjaOS6ClmiMjXRHbRfHmqMm6r M8iMESY6yc/ECb9GgILAYogiG63z+HDXuWCS3VIlixVQOHYbpt95blmxejhQ77LkR8Kc ttnA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:message-id:mime-version:subject:date :in-reply-to:cc:to:references; bh=XgdNB3P4uKQMQfhWHU9phbjlTeAnGncXFPj3Wn8SyEA=; b=Nu0PIFfehtHK2XxQPAYLMBC9g1VZap22T3YZsh31wX6oYRLBfnJRIzO4Pfvg+q4g77 yHtLJU7mY+trQwqs9jf++ZeE8KwAChRZr1XuH+xb1DNji1o6mz54oEgLPSVEINTK3Kvp SAV0zwpRIuEQ0udyVKe4IWuyz7IPGumTz9V+niahPvXJXZ9eNP9L+7KlERlgW39dZ4ft yJe9WekCymt/Eqc2qtiDAFMPtHOsyDfuJ6SdWUGLqVtqL3mVyR7KLXPBseTi5xick4kr cb7CvLgJvLnzXDecWYVK0Ni4tRncV5lnATvJKCebjNHj7Kc2jvZKheOctvFq9yPRCt4H ZxNA==
X-Gm-Message-State: AOAM533YKzDQj8e8npSWqkou/VgrcXVYSmZxEnV6rekap1edS//T89Cj hKnGULh6l5uv/7/nF4JuXe8=
X-Google-Smtp-Source: ABdhPJyDykwz3BipwrAKoNevI4LDeNe2/ULAAXPQL1MKMk3hA0pImf3saElFLt0i9Vr6r7dfkc8Vww==
X-Received: by 2002:a7b:c45a:: with SMTP id l26mr27773647wmi.91.1609777856711; Mon, 04 Jan 2021 08:30:56 -0800 (PST)
Received: from broadband.bt.com ([2a00:23c5:3395:c901:74b0:5eb3:4899:b38d]) by smtp.gmail.com with ESMTPSA id y7sm33714965wmb.37.2021.01.04.08.30.55 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Mon, 04 Jan 2021 08:30:56 -0800 (PST)
From: Stewart Bryant <stewart.bryant@gmail.com>
Message-Id: <E683497C-449B-4756-90CA-F01A8D7983E8@gmail.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_2759F0B9-710C-4D4A-9F8B-C21EE31848CD"
Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.120.23.2.4\))
Date: Mon, 04 Jan 2021 16:30:51 +0000
In-Reply-To: <DM6PR11MB3115122E45D5D9734E2A7023BFD20@DM6PR11MB3115.namprd11.prod.outlook.com>
Cc: Stewart Bryant <stewart.bryant@gmail.com>, Mach Chen <mach.chen@huawei.com>, mpls <mpls@ietf.org>, mpls-chairs <mpls-chairs@ietf.org>, "draft-gandhi-mpls-ioam-sr@ietf.org" <draft-gandhi-mpls-ioam-sr@ietf.org>
To: "Rakesh Gandhi (rgandhi)" <rgandhi=40cisco.com@dmarc.ietf.org>
References: <CAA=duU21PHQoJP0cEX6o1K=EwUFqeH19YvcDPNJVKE9c2szS6w@mail.gmail.com> <F73A3CB31E8BE34FA1BBE3C8F0CB2AE2980ACEB1@dggeml530-mbs.china.huawei.com> <DM6PR11MB3115122E45D5D9734E2A7023BFD20@DM6PR11MB3115.namprd11.prod.outlook.com>
X-Mailer: Apple Mail (2.3608.120.23.2.4)
Archived-At: <https://mailarchive.ietf.org/arch/msg/mpls/J9h47U2rc7pbllr1Kn7hHHCVh6I>
Subject: Re: [mpls] MPLS-RT Review of draft-gandhi-mpls-ioam-sr-04
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: Mon, 04 Jan 2021 16:31:00 -0000


> On 4 Jan 2021, at 14:38, Rakesh Gandhi (rgandhi) <rgandhi=40cisco.com@dmarc.ietf.org> wrote:
> 
> <RG> Yes, this is similar to the entropy label where a mid-point node needs to scan the label stack to find the indicator label. We can add some text to clarify this. There is already an optimization to use a different indicator label for HbH compared to E2E case to unnecessarily avoid parsing the IOAM data fields.

The EL is entirely optional to process. It is no more than a hint to use in ECMP and there is no architectural requirement to find it to operate correctly.

If iOAM is purely a option then you could scan the stack and hope that you can reach down far enough to find it. Though there is a fight to see who gets to be the lowest label in range of the forwarding parser.

If you want to be sure that iOAM is processed HxH then you really need to run it on a new FEC with that behaviour built into the FEC. That would be the architected way of doing this in MPLS.

- Stewart