IETF Logo Mail Archive

Re: [mpls] Update to the bullets on the first page of my review of draft-song-mpls-extension-header-09

Tony Li <tony.li@tony.li> Tue, 06 September 2022 17:58 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 C42E0C157B4B; Tue, 6 Sep 2022 10:58:06 -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.249, 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 ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 3y6QcX_PWaHU; Tue, 6 Sep 2022 10:58:05 -0700 (PDT)
Received: from mail-pf1-x436.google.com (mail-pf1-x436.google.com [IPv6:2607:f8b0:4864:20::436]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 12DF7C157B47; Tue, 6 Sep 2022 10:58:05 -0700 (PDT)
Received: by mail-pf1-x436.google.com with SMTP id 123so2740319pfy.2; Tue, 06 Sep 2022 10:58:05 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=to:references:message-id:content-transfer-encoding:cc:date :in-reply-to:from:subject:mime-version:sender:from:to:cc:subject :date; bh=UPEWqxnlRlaG50junr16Lu1TTWEGR0ArwJ22LpPQ7MU=; b=dpQjATNbVi3nYgdX5Po2qnRz3d+NZ7piVv4+TO6zNkmuWGExnLCF55WrqIushpCLTP 5v1W92P88UXbApXiy9BMWvkaEKXDcPA7955iuhwbxxGB9zVUbW0Cx117OzSMRP3kwkYv i2Ac+oOp+JpEyggoJC1CSypje8dbaQ3WRMzDrkkOi39XBpYTrwp8cgos1qRAcADa0zgN Zn96Mzsxw5AIIWz78oeml22ib93HNx9sw2OccDuNXO18dawMDMW5xyRnIZc/7Tpu8mSu IZb8nMFQH/kb0RMj98dbYN7z9s06TUHINBrAGN86Jf0wxNW4DfhftJK/fyi2c3lSDksj GEcw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=to:references:message-id:content-transfer-encoding:cc:date :in-reply-to:from:subject:mime-version:sender:x-gm-message-state :from:to:cc:subject:date; bh=UPEWqxnlRlaG50junr16Lu1TTWEGR0ArwJ22LpPQ7MU=; b=hXT5WqeRP9xDFkSmHDiD8ETGIXKOi8QckTSxdSWdfbAgEvEfOWrVXonP98lwMrTihK RFBJb65Ot3ZKnJpjWUk3mUsr1ZXWoEuts7ViNom9kkf5/SRh6gO8o/y76GUOSaFJ2MZH CcNsOKDCZA0f9OU+M43TUAElI65fl+BNn5O11QhoRewRLLDC40/WApre665SloMP1nVK QwavM6q9sMo/weMeyfDjN3u3URnyXDLQGO+KxO7Nqm+DYBitloO813/5u1iDyyfU3/qL UlsCVKwl3F1Pr97o3EcvxpGPXYoVA4gp2USzMotJZVtStJ4WnnWXPYJJZgqD57VBPU6z L9LA==
X-Gm-Message-State: ACgBeo29irjE5maD/Nx8+Z5SeUjDaEHbTs/xvxbarsN8TyJ2zWONg0tU oMHuNi+yP87XIZ1YGBPOwj8=
X-Google-Smtp-Source: AA6agR4pDdLacNCKyA4SWYc7FhuiXrCun/2V4jvUJ84cj+IntJ79uE/C62EQjMgXp6KFnbN3K0JiWA==
X-Received: by 2002:a63:1a26:0:b0:42c:ffa:2f0b with SMTP id a38-20020a631a26000000b0042c0ffa2f0bmr38311416pga.138.1662487084004; Tue, 06 Sep 2022 10:58:04 -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 g123-20020a625281000000b0053e483de200sm1314385pfb.73.2022.09.06.10.58.02 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Tue, 06 Sep 2022 10:58:03 -0700 (PDT)
Sender: Tony Li <tony1athome@gmail.com>
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (Mac OS X Mail 15.0 \(3693.60.0.1.1\))
From: Tony Li <tony.li@tony.li>
In-Reply-To: <BY3PR13MB478710246F3C3F4BF7F583669A7E9@BY3PR13MB4787.namprd13.prod.outlook.com>
Date: Tue, 06 Sep 2022 10:58:01 -0700
Cc: Loa Andersson <loa@pi.nu>, Tianran Zhou <zhoutianran@huawei.com>, "mpls@ietf.org" <mpls@ietf.org>, "draft-song-mpls-extension-header@ietf.org" <draft-song-mpls-extension-header@ietf.org>, "mpls-chairs@ietf.org" <mpls-chairs@ietf.org>, "pals-chairs@ietf.org" <pals-chairs@ietf.org>, DetNet Chairs <detnet-chairs@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <2066748F-0459-4301-8DBF-B4AC6448A574@tony.li>
References: <98356ad3-ec52-3a5c-ee31-1ee604d4b5db@pi.nu> <dc03203bf7ee49caafccdb70221edc1a@huawei.com> <b718cd04-c822-b744-0ca2-9c3e47ea2f62@pi.nu> <BY3PR13MB47879BAD2537E77C1D6193F89A799@BY3PR13MB4787.namprd13.prod.outlook.com> <33185189-08e3-71da-123c-2f17fe5ad0bb@pi.nu> <BY3PR13MB47878BDBE64EE739BA4F5DF99A799@BY3PR13MB4787.namprd13.prod.outlook.com> <5A840AB5-7B0F-4C21-B0B0-700194B03A32@tony.li> <BY3PR13MB478797DB5335413F94621C219A799@BY3PR13MB4787.namprd13.prod.outlook.com> <06759C2A-CA9D-4957-8203-D71BAFA1AB67@tony.li> <c5820e62-b4ed-d88a-d738-16ee52088342@pi.nu> <200451CE-9554-4298-BB9C-2EB4B63D843F@tony.li> <BY3PR13MB478738F2A6D4BF357BA15C4C9A7E9@BY3PR13MB4787.namprd13.prod.outlook.com> <0E7CFAAD-DA1F-4621-9F5B-1180B79081AE@tony.li> <BY3PR13MB478710246F3C3F4BF7F583669A7E9@BY3PR13MB4787.namprd13.prod.outlook.com>
To: Haoyu Song <haoyu.song@futurewei.com>
X-Mailer: Apple Mail (2.3693.60.0.1.1)
Archived-At: <https://mailarchive.ietf.org/arch/msg/mpls/mob9hZ5JrBTBIuQK0vGcdBlfHR8>
Subject: Re: [mpls] Update to the bullets on the first page of my review of draft-song-mpls-extension-header-09
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.39
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: Tue, 06 Sep 2022 17:58:06 -0000

Hi Haoyu,

> When you say "scope", do you mean network scope or in-device scope?


Scope is formally defined in the requirements document.


> In my second point, I mean the action scope in a device. For example, IOAM can be configured to collect data from anywhere on the processing pipeline, depending on what's set in the data type bitmap. If it's configured to collect ingress data only, then its scope become "ingress"; similarly, it's can also be configured to be "egress" only or cover the entire pipeline. This is a case that the scope is changeable and controlled by the application itself. If such kind of action has some dependency with other actions, it'll make a fairly complex situation. 


Which is exactly why we would like it specified.


> Fortunately, as a passive data collection mechanism, AFAICS IOAM can be independent with other actions. 
> 
> Then, do we have any solid case that the dependency between actions exist? I can't think of any now. If we have real examples, that would help a lot for the discussion.   


It will necessarily happen.  

We probably have an interesting issue already with the slice identifier and IOAM traceroute.  What address should be recorded in the packet? If you evaluate the slice identifier first, you would probably select an IP address that is restricted to the slice. If you neglect the slice identifier, you might select an IP address that is independent of the slice.

More will happen. Rich semantics imply that we have not created a set of orthogonal, independent actions.

Tony

v2.23.0 | Report a Bug | By Email