Re: [mpls] On the use of GAL in MPLS-SFC OAM

Stewart Bryant <stewart.bryant@gmail.com> Wed, 10 March 2021 17:52 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 2B4503A1495; Wed, 10 Mar 2021 09:52:32 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.597
X-Spam-Level:
X-Spam-Status: No, score=-0.597 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, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_BLOCKED=0.001, RCVD_IN_SORBS_WEB=1.5, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=no 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 9gkG4dxr1FJk; Wed, 10 Mar 2021 09:52:30 -0800 (PST)
Received: from mail-wm1-x332.google.com (mail-wm1-x332.google.com [IPv6:2a00:1450:4864:20::332]) (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 9C3D43A1491; Wed, 10 Mar 2021 09:52:30 -0800 (PST)
Received: by mail-wm1-x332.google.com with SMTP id f22-20020a7bc8d60000b029010c024a1407so11623034wml.2; Wed, 10 Mar 2021 09:52:30 -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=4KS1XSsxepXgi/1st+CswMeE8un4bEYlDUkXE1NLpRk=; b=UiTmUvP7vyD1Qe0mv5CLHqwM1vwvU3vCP3mMZWE126/f7USGirggS/POuELnVj4Hy4 8ZJHGYyAEalXMYFaw56zlRjHl4pDmQ+pMI0fzXpIAyHgdHlOTjnczC7yLvbx5jUz8ydQ or91qk/qAiqnAJQSxI7hHiKgCso0vCRutcB4Mp8p8QmfSUDa5Py661qyqklkQHp6Qh09 X/QNN0im0os1LHjKB9Cm3+vCo9pgLgImmcbFAZlPuTCdUjkJBcFr+soxO2psrV0nTr4r +JzWStjVpG1GEJ/0mmRwXTldyDA0sUzhgaT1vj5XcnTZ2RAgphgiXVrvW1UDeNCDYGKz Rhqw==
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=4KS1XSsxepXgi/1st+CswMeE8un4bEYlDUkXE1NLpRk=; b=BkXJuzA6RArFDZj4GDDT3zHQ1xLfyN4FSj6zKL0qlRMjaNEtKJWljz3Z1pg5xIDDPf KVUIBwThzsTEDZVfPgEVMTmYf1f8g3ylVvPrfPbF1VX376e/Gwhnn9x4Ta9mRuwFCFmN nK1Ph5FatrLEwMmPL86S/bkNQjlZ0VRbYaQEPLDRE9JVeScSUS7UPUzYIrSBUP3a9Esl dHwudPRmWb32rZ3uPpYOKVyDzIVrd0ZRwixADSU3JfZRK7vrj6bFlQI3blbUknZe9l0I nPf2FsCREEHw6LNSskQpyHJX/esKlr5At9QGaU18GtRGPOp8IlMN0CIaGM/diJb1sLjS VPrw==
X-Gm-Message-State: AOAM531vN/kNvmXnuFiipYocd9w0lv7WOJbVzDzZRydcgWINfvsDO5l6 gJtPkVlIGEDQqVx10/Dcb/U=
X-Google-Smtp-Source: ABdhPJyGU0K7s99IIcHz+1LYVQfGUu8WcdHAyPhM43e0Pxwf6xxM6gchXXA+5sfe5gVS7gmC8TsR8A==
X-Received: by 2002:a7b:cc0c:: with SMTP id f12mr4492034wmh.137.1615398749101; Wed, 10 Mar 2021 09:52:29 -0800 (PST)
Received: from [192.168.8.102] ([185.69.145.254]) by smtp.gmail.com with ESMTPSA id a6sm257555wmm.0.2021.03.10.09.52.27 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Wed, 10 Mar 2021 09:52:28 -0800 (PST)
From: Stewart Bryant <stewart.bryant@gmail.com>
Message-Id: <20076CC8-E662-4EAC-AAE3-BE7FEEDEC6CE@gmail.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_EE697E7E-445D-40CA-AFDB-8A9C6861CCD7"
Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.120.23.2.4\))
Date: Wed, 10 Mar 2021 17:52:27 +0000
In-Reply-To: <33e6a177-b453-d756-a933-d60e06e7c47c@gmail.com>
Cc: Stewart Bryant <stewart.bryant@gmail.com>, Tarek Saad <tsaad=40juniper.net@dmarc.ietf.org>, "adrian@olddog.co.uk" <adrian@olddog.co.uk>, Greg Mirsky <gregimirsky@gmail.com>, mpls <mpls@ietf.org>, "draft-lm-mpls-sfc-path-verification@ietf.org" <draft-lm-mpls-sfc-path-verification@ietf.org>, MPLS Working Group <mpls-chairs@ietf.org>
To: huubatwork@gmail.com
References: <CA+RyBmXf_Nzn3GxW+1Q1LFjcQ8zUpR9YEMBGyQJ0ODJPcBtD3g@mail.gmail.com> <3688C3DB-2583-4A8D-A9F6-1AF2D05875D0@gmail.com> <CA+RyBmViEB0A-EG6x31E8wes+ytzaLosu4SNzFusOKDM+op8+Q@mail.gmail.com> <0a4201d715af$5605f4d0$0211de70$@olddog.co.uk> <E338C962-6BCC-4916-96FB-DC99FFDE6F14@juniper.net> <33e6a177-b453-d756-a933-d60e06e7c47c@gmail.com>
X-Mailer: Apple Mail (2.3608.120.23.2.4)
Archived-At: <https://mailarchive.ietf.org/arch/msg/mpls/mSLJRdaaiR3wOD5T2wXcO1gel0w>
Subject: Re: [mpls] On the use of GAL in MPLS-SFC OAM
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, 10 Mar 2021 17:52:32 -0000

Hi Huub,

> On 10 Mar 2021, at 14:56, Huub van Helvoort <huubatwork@gmail.com> wrote:
> 
> If there is more than one GAL in the stack, then which ACH following
> the BoS belongs to which GAL?


The GAL tells the forwarder  that there is an ACH at BoS. 

My interpretation is that any additional GAL says the same thing, and all of them refer to the same (single) ACH.

We are doing to be discussing this in the PALS Friday meeting, because it is only in the last few months that anyone has suggested that there would be more than one ACH, and we need to understand what the implications of such a change are both in the short term, and for the future of the MPLS protocol.

- Stewart