Re: [mpls] working group adoption poll on draft-bocci-mpls-miad-adi-requirements

Tony Li <tony.li@tony.li> Wed, 20 April 2022 15:17 UTC

Return-Path: <tony1athome@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 257283A0ADE; Wed, 20 Apr 2022 08:17:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.51
X-Spam-Level:
X-Spam-Status: No, score=-1.51 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, RCVD_IN_ZEN_BLOCKED_OPENDNS=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 AZv_31F3KL2F; Wed, 20 Apr 2022 08:17:38 -0700 (PDT)
Received: from mail-pf1-x433.google.com (mail-pf1-x433.google.com [IPv6:2607:f8b0:4864:20::433]) (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 0C6D83A086E; Wed, 20 Apr 2022 08:17:38 -0700 (PDT)
Received: by mail-pf1-x433.google.com with SMTP id j17so2198359pfi.9; Wed, 20 Apr 2022 08:17:38 -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=3IPOaiLz9RhlE0dQ1dmL7ZEZnRXS4hWtI/HFOCj+424=; b=HpBSl6YieVqdt7ILnJIblNAvBw2rYP8yV1lLXN5D60eqR/3Me2W9TdMNttgXP7vB7i yepe75AgPHtHuiKQLznMPI8y35572CM8iPA6Emp1kVR3vwNUajUJHier2TZUmgYSmh0W MnEU3CsFtuKdz0+sgKPAbVh+x/kH6aFEfStTcVx5IAH6Zxga4ysPs7d4WDpv8CvUcm4c 085qhqP7CXghH3pnXeDXAiWE5FYjXF+M/aIHuYhgURbWCXxUPbS7Ovh+VJXS+4rqEMB3 gbit7eGhDF9fd/tTmZRAVpTi0adEfFWIvhizSiZSSYfWoDLyDQQYmh2Cw0eYWa+ARuE8 9CWA==
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=3IPOaiLz9RhlE0dQ1dmL7ZEZnRXS4hWtI/HFOCj+424=; b=ObF0VWcuoYBPFRa7WlGlIjsjvykqHd5tIhHxoI5EHMjIkDuDGeVPgJ4WY2f/t0bmSI 3T22LLLd/4wqTIiYouERzO/HetFlqMeQC7RZh1rPrG22n73HQt7/1ip+BhTSCXEgwBFJ 3TwBl/jQHlEmko2d0BlIE+1/rW4VuGdGLzshfPZuA+AKfMwVX7faZ8vkIFWPMgzqE2hh jhl3HVK5LqdeWqsc5SlI6yvnBRQ/WOkomj3HrgirpGw09d/Bk0kiinjGUe3/cVhuEAmE bxDi+7Gwny5XWqDLPIAVTa6mLZUOwowm9mAWWl2yS33zIMiIQdqY5DqW0HSeYuVdpRYQ u+WQ==
X-Gm-Message-State: AOAM533P3+4up0uTIXZwZkASDVdVbfazyv7azVB8fDO9BF2TsoD22e2m yhtyA20i0EMg1b4WwAYquvOs5Zf60lw=
X-Google-Smtp-Source: ABdhPJzd3Di/UaX4aXSqTKYXy0VXNQnuWJ0oMzY3fnUcYIYai0rlycFMU5AwN2MOb0a4ClZu68FErQ==
X-Received: by 2002:a63:e74b:0:b0:3aa:45e3:2cb2 with SMTP id j11-20020a63e74b000000b003aa45e32cb2mr6647731pgk.249.1650467856674; Wed, 20 Apr 2022 08:17:36 -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 e126-20020a621e84000000b0050567191161sm20521188pfe.210.2022.04.20.08.17.34 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Wed, 20 Apr 2022 08:17:35 -0700 (PDT)
Sender: Tony Li <tony1athome@gmail.com>
From: Tony Li <tony.li@tony.li>
Message-Id: <8B31C84B-1335-4003-8DD5-C4F4E17BF904@tony.li>
Content-Type: multipart/alternative; boundary="Apple-Mail=_4BD8965B-2186-47A0-934B-DEA7AB917BCB"
Mime-Version: 1.0 (Mac OS X Mail 15.0 \(3693.60.0.1.1\))
Date: Wed, 20 Apr 2022 08:17:33 -0700
In-Reply-To: <65206571a25d494f97174c9f7757619a@huawei.com>
Cc: Loa Andersson <loa@pi.nu>, "mpls@ietf.org" <mpls@ietf.org>, "draft-bocci-mpls-miad-adi-requirements@ietf.org" <draft-bocci-mpls-miad-adi-requirements@ietf.org>, "pals-chairs@ietf.org" <pals-chairs@ietf.org>, "mpls-chairs@ietf.org" <mpls-chairs@ietf.org>, DetNet Chairs <detnet-chairs@ietf.org>
To: "Dongjie (Jimmy)" <jie.dong@huawei.com>
References: <402e03c9-9c20-685e-937a-13b5a3ebca59@pi.nu> <3a4ceaeb2acc4eddb587c1e7688cd685@huawei.com> <28C54427-B016-4ED2-A94D-AFE344124851@tony.li> <327126d0ac8c4886ad1a3a0b0c8bc2b2@huawei.com> <2F5F50A2-2250-467D-9C94-5DDAB92FD54B@tony.li> <00722bffcaeb4728869e24771f772baa@huawei.com> <679CBA33-7996-4809-80CA-D8DC31093650@tony.li> <65206571a25d494f97174c9f7757619a@huawei.com>
X-Mailer: Apple Mail (2.3693.60.0.1.1)
Archived-At: <https://mailarchive.ietf.org/arch/msg/mpls/xt-jEptoeOTFR4Flnc4hNXtsp6g>
Subject: Re: [mpls] working group adoption poll on draft-bocci-mpls-miad-adi-requirements
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, 20 Apr 2022 15:17:40 -0000

Hi Jie,



> Please feel free to propose terms and definitions if you feel that they would be helpful. What you’re describing sounds a lot like an NAS to me, but perhaps there’s some nuance that I’m missing.
>  
> [Jie #3] My suggestions would be to keep using ADI for the generic indicator, and could use NAI for the indicator of specific action. I don’think we need to mention NAS here, which is specific to ISD based solution. 


First, NAS is general. Even if all data is pushed to PSD, then we still have a special label. That is a degenerate case of a single LSE NAS.

I welcome the suggestion that NAI be more specific and that we also have a generic term.

ADI does not seem like a good term for a generic indicator. What if there is no ancillary data?

I propose Network Action Sub-stack Indcator (NSI) for this purpose.  Proposed definition:

	An LSE used to indicate the presence of a Network Action Sub-stack.

We should also revise the definition of NAS to use this.



> Please note that in the MPLS-TP requirements RFC 5654, reuse existing mechanism is also one of the general requirements:
>  
> “The MPLS-TP design SHOULD as far as reasonably possible reuse existing MPLS standards.”



SHOULD is very different than MUST.


> [Jie #3] The example I gave is about reusing the IOAM data format in draft-ietf-ippm-ioam-data-17, which was designed to be encapsulated in different data plane. It is not related to the ELI discussion.


The requirement that you wrote is general and not specific to IOAM. As a general requirement, it could and would apply to other situations such as ELI.  I think that is NOT the result that we want, so I disagree with the requirement. 


> [Jie #3] Indeed these are my proposals to this document as an individual IETF participant, and it is good if you agree with them. But I don’t quite follow your reason of not using “MUST”, and what requirement key word in RFC2119 do you think would be appropriate? 


SHOULD would allow us to apply them and consider trade-offs.

Tony