Re: [Detnet] [mpls] Comments on draft-bocci-mpls-miad-adi-requirements

Tony Li <tony.li@tony.li> Thu, 31 March 2022 22:15 UTC

Return-Path: <tony1athome@gmail.com>
X-Original-To: detnet@ietfa.amsl.com
Delivered-To: detnet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 502D93A1F47; Thu, 31 Mar 2022 15:15:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.511
X-Spam-Level:
X-Spam-Status: No, score=-1.511 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FORGED_FROMDOMAIN=0.248, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.248, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_BLOCKED=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01] 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 PPmzYvTrDfO5; Thu, 31 Mar 2022 15:15:21 -0700 (PDT)
Received: from mail-pl1-x633.google.com (mail-pl1-x633.google.com [IPv6:2607:f8b0:4864:20::633]) (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 DAE6E3A2245; Thu, 31 Mar 2022 15:14:06 -0700 (PDT)
Received: by mail-pl1-x633.google.com with SMTP id p17so822972plo.9; Thu, 31 Mar 2022 15:14:06 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=sender:from:message-id:mime-version:subject:date:in-reply-to:cc:to :references; bh=lUxspgPZh2LLi50Erh+ypAiDJa5VQ7l8F/fDhB4+Y+4=; b=NeYLTiDNpDizHRtd05ot/6ysn7js1cyDCjogY8sIFzpdx5WyqLQs3x3tesl9qXGNBR BNv86GTl9fmJN+skFyLtBBzlnQT7I0KUt4JatO0bjW/85CjC97Bm/TACJ5Zyr32cvunL 06ZevmEICyQuEiVB2tsrEYJbODjtuyxPOiWfEGH7vGl1neuzGvomp8BOB31q0TB/SG/9 DFbdSnwgwSKyg6+kXJ4MfAfFPQ9ALiFw30rmMML7ukSpJOnc/UE0cJJymDBeIzQ4plMN EuAKDXtUB3FPqPRlsSVf+EK6lfXvniCDTx3/mA7kiJbcLlMGuYQlQAdB9kWfCD9TuCPB 67yw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:sender:from:message-id:mime-version:subject:date :in-reply-to:cc:to:references; bh=lUxspgPZh2LLi50Erh+ypAiDJa5VQ7l8F/fDhB4+Y+4=; b=ijW/eTjfgqRNarGr7v4Fb3m98GN8+npo1+jOLLNh8bZLKw+go6eukVUQDzAaKxq0Gw j1AO5K/4qLD/EI9Oiu+ONIbn/ssU8zE5e5WFnzqdx/IqV5mr2OD5eh+wimEPmLH7xmui By5XRCGw90fjBz1YleTU+6O1eD/q1xTkiBrFLHngQ3mNrGsoEH6d5/MuskosR6cauhRv +QilLMCe5TLIfg02lHo/OBVkTRc8+lBr56AJUclNXcxpSAzphH6OjwQZ58rpMh3pGuNm YgR/JcWVYssg+atEvmvsZRStxO009eiE4VF3NW5gsKLDWMJBSTPTVKBZ8Ii9yNNF7biD Np5w==
X-Gm-Message-State: AOAM531HRTQ1wY3YnztvZ5lFY7XAjo72gPPYQWhCZ/9hakx0t089Buo5 MTNAw2Oo2OPkj5kZlrtaz8M=
X-Google-Smtp-Source: ABdhPJz28l5ntmdDGD4PT0mQYzxOj9m+TdUZ2/pirTLad+icDfpJqtKbOrlfPjCA8c+pksg49pRmqw==
X-Received: by 2002:a17:902:d2d1:b0:154:45d2:a05d with SMTP id n17-20020a170902d2d100b0015445d2a05dmr7420374plc.74.1648764845728; Thu, 31 Mar 2022 15:14:05 -0700 (PDT)
Received: from smtpclient.apple (c-67-169-103-239.hsd1.ca.comcast.net. [67.169.103.239]) by smtp.gmail.com with ESMTPSA id b7-20020a056a00114700b004f7be3231d6sm478129pfm.7.2022.03.31.15.14.04 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Thu, 31 Mar 2022 15:14:05 -0700 (PDT)
Sender: Tony Li <tony1athome@gmail.com>
From: Tony Li <tony.li@tony.li>
Message-Id: <4D22C5CD-13D8-4565-BC13-C909450C3377@tony.li>
Content-Type: multipart/alternative; boundary="Apple-Mail=_A6BC86A8-A633-4C5E-AD0F-E447A1235C6E"
Mime-Version: 1.0 (Mac OS X Mail 15.0 \(3693.60.0.1.1\))
Date: Thu, 31 Mar 2022 15:14:04 -0700
In-Reply-To: <CA+RyBmVs_1C6hxesB6qeS8eb59Y69aJoZ7iAVO=NUg-pioZb4Q@mail.gmail.com>
Cc: Haoyu Song <haoyu.song@futurewei.com>, mpls <mpls@ietf.org>, DetNet WG <detnet@ietf.org>, "draft-bocci-mpls-miad-adi-requirements@ietf.org" <draft-bocci-mpls-miad-adi-requirements@ietf.org>, "pals@ietf.org" <pals@ietf.org>
To: Greg Mirsky <gregimirsky@gmail.com>
References: <CA+RyBmUkdm2dJ5+geme44C6i5bJyqWs_XiA4p_vKjuiniZrPew@mail.gmail.com> <VI1PR0701MB6991DE8DCAE47DEFDA462F52EB049@VI1PR0701MB6991.eurprd07.prod.outlook.com> <CA+RyBmWqBDemJ1pmfVzXNGLnvdTZkmhoKT8UX8XYiorxG8isqQ@mail.gmail.com> <VI1PR0701MB6991ADB9D32A049F6F231FBDEBE19@VI1PR0701MB6991.eurprd07.prod.outlook.com> <BY3PR13MB47870582516CFC16CB5D51579AE19@BY3PR13MB4787.namprd13.prod.outlook.com> <CA+RyBmWDD-xOs6DEe46zKg+WrM1ukWXhNJbqhwwCrB4eCw+E+A@mail.gmail.com> <BY3PR13MB47872079F732A48A403CF9BF9AE19@BY3PR13MB4787.namprd13.prod.outlook.com> <CA+RyBmUOa5eTjpF-=PPrAWmLUS7EeBXgpcaf_GEPq_CAyuHGsw@mail.gmail.com> <DE3B7719-7AFB-44D8-B097-4D7935E00E59@tony.li> <CA+RyBmVs_1C6hxesB6qeS8eb59Y69aJoZ7iAVO=NUg-pioZb4Q@mail.gmail.com>
X-Mailer: Apple Mail (2.3693.60.0.1.1)
Archived-At: <https://mailarchive.ietf.org/arch/msg/detnet/AiOKGJFXe7smhqnI4lcFR4uwKes>
Subject: Re: [Detnet] [mpls] Comments on draft-bocci-mpls-miad-adi-requirements
X-BeenThere: detnet@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Discussions on Deterministic Networking BoF and Proposed WG <detnet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/detnet>, <mailto:detnet-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/detnet/>
List-Post: <mailto:detnet@ietf.org>
List-Help: <mailto:detnet-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/detnet>, <mailto:detnet-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 31 Mar 2022 22:15:24 -0000

Greg,

> On Mar 31, 2022, at 1:46 PM, Greg Mirsky <gregimirsky@gmail.com> wrote:
> 
> I think that the situation with an arbitrary LSR imposing ADIs is more nuanced as we must understand where the particular ADI must be disposed of. I am not certain how it, for example, applies to SR-MPLS. I can imagine hierarchical LSP imposed between two adjacent SR nodes. If that is the case, imposed ADIs must be disposed within that segment. Please let me know if I'm missing anything.


As they say in aviation: taking off is optional, landing is mandatory. :)

Yes, while adding ADI can effectively be done anywhere, if you actually want to deliver useful payload, there must be adequate consideration given to where the ADI is removed.  In keeping with a hierarchical nature, I would hope that addition and removal would be coupled operations at either ends of a container LSP.

Tony