Re: [mpls] Concerns about ISD

Tony Li <tony.li@tony.li> Fri, 15 April 2022 18:56 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 706A23A14E8 for <mpls@ietfa.amsl.com>; Fri, 15 Apr 2022 11:56:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.512
X-Spam-Level:
X-Spam-Status: No, score=-6.512 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_HI=-5, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01] 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 wEUs-QhpFloG for <mpls@ietfa.amsl.com>; Fri, 15 Apr 2022 11:56:12 -0700 (PDT)
Received: from mail-pj1-x102f.google.com (mail-pj1-x102f.google.com [IPv6:2607:f8b0:4864:20::102f]) (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 2303F3A145C for <mpls@ietf.org>; Fri, 15 Apr 2022 11:56:12 -0700 (PDT)
Received: by mail-pj1-x102f.google.com with SMTP id bg24so8245451pjb.1 for <mpls@ietf.org>; Fri, 15 Apr 2022 11:56:12 -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=o+RjHT8CmVKSp88wYo90Kt7zCQHteGJUONTXTXFp8Tc=; b=C+ad9g6E/RvHy0ZE4Po/GD+ioMoj3z1afWw+Ydnm0/awh77T7QPdhJp7trC5eWTTYA UlyCk8a5mJGGQaPO9NMfrzZed/8QkLUT9olBJQjbNiqgdelJoim/2bpBEVwCXHrwOHfo 5QgvJdJt9wASSEcTMIdtN8QOVFhNKIZzkP3cSJ9Uf0dO1VSYZ8mkndLCcBBz3GGU0g/6 kqD7agh5JXsQOPKIl2LcIWNl2jU37N81L7Td2BQllR4jqKkadwQIxl8+oM6WxSPTQjUw jMq5c4G5BTEYLOV0uZnt3xBvtxYQv7PQ6FkXST+rW8k6Q0kOpUyW5Xr5TAu3Ln/KtaPR WCvA==
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=o+RjHT8CmVKSp88wYo90Kt7zCQHteGJUONTXTXFp8Tc=; b=bkBADlwY4zj/Z+Op1CiJS9Nx8o+4B+v8kTPTf73rD7VFPP1y6ywEKjNyVmNbL8Ar8w IUPS6hjrM7BKXw5AVTjfTwMISbzdYhJfqtEK9ZpAgfnDM2Lp70HLgqvJr8zImlzfPCob OGKYQzzN869J/5tqMp2AGh5BHfMp5WrN8Uz9rLKzHAHLR9m8tin52F34XESzDHk4u81u 0un2N0lm+LLMGt8J6fze7k3J0s82fuMIgr0+PT6HBKWmUGJe0oRV8/3ZXU6vRoeGL14V mVhs0Xo6rxY9ka6dLO7vHRalNu2eHlEaM3ISz2BPBzTXzmkLe60U8biGVlhrMHPy4k8t RH3Q==
X-Gm-Message-State: AOAM533p1GNqmMqFAxdNE9badS9u/FEYYK5PGKCfhwGnFaExmixBmPkn TOyWCYigEGria0LEzGjmva8=
X-Google-Smtp-Source: ABdhPJwXZ6HWfOcmYp2gPfHqkApSurrxiUduWX4zGonW++mcLs4e1oK2eTf3WtnTpKxyvBAYMefQ8Q==
X-Received: by 2002:a17:90a:f01:b0:1c7:ea40:93e7 with SMTP id 1-20020a17090a0f0100b001c7ea4093e7mr5695638pjy.30.1650048970753; Fri, 15 Apr 2022 11:56:10 -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 g15-20020a056a0023cf00b004e17e11cb17sm3670703pfc.111.2022.04.15.11.56.09 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Fri, 15 Apr 2022 11:56:10 -0700 (PDT)
Sender: Tony Li <tony1athome@gmail.com>
From: Tony Li <tony.li@tony.li>
Message-Id: <602D6128-3BE3-4A2D-B5C2-019AE0FADF09@tony.li>
Content-Type: multipart/alternative; boundary="Apple-Mail=_C6A5383A-4C92-41E2-B64C-C1FB999C01B1"
Mime-Version: 1.0 (Mac OS X Mail 15.0 \(3693.60.0.1.1\))
Date: Fri, 15 Apr 2022 11:56:09 -0700
In-Reply-To: <BY3PR13MB4787752FB6D147281A7150789AEE9@BY3PR13MB4787.namprd13.prod.outlook.com>
Cc: John E Drake <jdrake=40juniper.net@dmarc.ietf.org>, Tianran Zhou <zhoutianran=40huawei.com@dmarc.ietf.org>, "mpls@ietf.org" <mpls@ietf.org>
To: Haoyu Song <haoyu.song@futurewei.com>
References: <6cc272447d2f4c779e85d5c42d3b3c6c@huawei.com> <8623637D-A32E-47A4-B5FC-4D2CF40BEDD1@tony.li> <6199e0e886f9437c95ef9b70719b00ec@huawei.com> <BCFD3F4A-36D6-47C2-B907-FC40B402F97C@tony.li> <3fb1f261ddff48deb0c2ea083cdbd16f@huawei.com> <6B96F21B-9331-4FA8-AD7B-84A4CA8B6FAB@tony.li> <903c57a48280454091495673ec2fe275@huawei.com> <BD5C1BE7-4633-4B51-BAC1-B2AE1C537F36@tony.li> <ad6b8c42b0aa4880b9dee02516f5e46f@huawei.com> <F5BB2CEB-CC8C-4E71-A2E7-B4212878C3B1@tony.li> <aa9c4b913d844410b2af90c8db78c194@huawei.com> <BY3PR05MB8081937B52E657713E8293BFC7ED9@BY3PR05MB8081.namprd05.prod.outlook.com> <a29c96be774845e582a66700d2264f7b@huawei.com> <BY3PR05MB8081870EF67C551727BBE2CFC7EC9@BY3PR05MB8081.namprd05.prod.outlook.com> <d5521b3972dd43e38276afbbdc7c2bda@huawei.com> <BY3PR05MB80813C7CAD7F2C12C36FB513C7EE9@BY3PR05MB8081.namprd05.prod.outlook.com> <BY3PR13MB47879EB8A582437DE936688C9AEE9@BY3PR13MB4787.namprd13.prod.outlook.com> <C493D0B8-4B57-4D19-BC27-70ABD7F50356@tony.li> <BY3PR13MB47878B227A37AAA06625194B9AEE9@BY3PR13MB4787.namprd13.prod.outlook.com> <0318B3A3-2884-4FD6-B5EF-377481D2657B@tony.li> <BY3PR13MB4787752FB6D147281A7150789AEE9@BY3PR13MB4787.namprd13.prod.outlook.com>
X-Mailer: Apple Mail (2.3693.60.0.1.1)
Archived-At: <https://mailarchive.ietf.org/arch/msg/mpls/QfIzB-HUQ3YvMpPIEdTtwb40o7U>
Subject: Re: [mpls] Concerns about ISD
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: Fri, 15 Apr 2022 18:56:18 -0000

Hi Haoyu,

> If you continue to read the indicator draft, you’ll find it may be possible to reach the EHs faster.


I’m sorry, I’m not sure which document you’re referring to.

Yes, I realize that you could store a length of the label stack in the EHI LSE.  That would allow you to index directly to PSD rather than linear parsing for the bottom of stack.  However, that’s not the established MPLS mechanism. :-)  Moreover, it causes a redundancy and inconsistency problem: both the length and the bottom of stack must been coordinated.  What happens if they are inconsistent? Is an implementation supposed to cross-check them? If so, we’re back to linear search for the S bit. And the redundancy seems wasteful of bits.


> Even we don’t use that mechanism, the parsing latency is indeed linear to the label stack depth.


Thank you.  


> But if you check the cost of parsing ISD, this can still be a better choice.


Please explain that.  As previously discussed, parsing the full stack to find the bottom of the stack requires more read/load operations. That would seem to mandate poorer performance.


> Moreover, the stack of stack can help to reduce the label stack depth to reach the EHs.


I’m not following that.  It seems to me that if there is a hierarchical stack, then for an implementation to support all of the network actions, it has to parse all of the hierarchy plus all of the extension headers.


> For the EH encoding efficiency, I appreciate your input. Currently it follows the IPv6 EH type (i.e., using NH + LENGTH to delineate every EH). There could certainly be room for improvement.


Ok.  If I understand your proposal correctly, there are 4 octets of overhead (HEH) at the start. Then, for each network action, there would seem to be at least 3 octets of overhead, plus any associated data, plus alignment.

Let’s suppose that we want to encode NFFRR, entropy, and GISS in one packet.  By my math, the cost is:

EHI: 4 octets
HEH: 4 octets
NFFRR: 4 octets
Entropy: 8 octets
GISS: 8 octets

Total: 28 octets

Do I have that right?

Tony