[mpls] How many flags could be set in an NAI Flag field
Loa Andersson <loa@pi.nu> Wed, 27 April 2022 09:37 UTC
Return-Path: <loa@pi.nu>
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 5A538C07A6DF; Wed, 27 Apr 2022 02:37:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.898
X-Spam-Level:
X-Spam-Status: No, score=-1.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_NONE=0.001] autolearn=ham autolearn_force=no
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 DwbASjehPNXR; Wed, 27 Apr 2022 02:37:32 -0700 (PDT)
Received: from pipi.pi.nu (pipi.pi.nu [83.168.239.141]) (using TLSv1.1 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E3078C180A72; Wed, 27 Apr 2022 02:37:30 -0700 (PDT)
Received: from [192.168.1.98] (unknown [122.2.109.188]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) (Authenticated sender: loa@pi.nu) by pipi.pi.nu (Postfix) with ESMTPSA id 0294336710D; Wed, 27 Apr 2022 11:37:26 +0200 (CEST)
Message-ID: <4476edd6-521c-bfd1-ff3b-0e9c3d5b8c0f@pi.nu>
Date: Wed, 27 Apr 2022 17:37:24 +0800
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:91.0) Gecko/20100101 Thunderbird/91.8.1
Content-Language: en-CA
From: Loa Andersson <loa@pi.nu>
To: "mpls@ietf.org" <mpls@ietf.org>
Cc: "mpls-chairs@ietf.org" <mpls-chairs@ietf.org>, "pals-chairs@ietf.org" <pals-chairs@ietf.org>, DetNet Chairs <detnet-chairs@ietf.org>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/mpls/WLdUU-i1v5SEe6f0UKwOfZjuWag>
Subject: [mpls] How many flags could be set in an NAI Flag field
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.34
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, 27 Apr 2022 09:37:34 -0000
Folks, I've been thinking about "how many flags" will be set? I understand that this is not rocket science, but possible not without importance Assume that we have the possibility to set about 20 Network Action Indicators in a flag field carried in a new bSPL (more than what can be carried in the repurposed TTL and TC fields. I assume the most packet will not carry the bSPL. Of those that does, most will have just one flag. Very few will more than three flags set. Is this an accurate assumption? What will be the balance between "implicit" and "explicit" ancillary data? If it is will it have an impact on our design criteria. Admittedly there might be an increase in these numbers of time, but I doubt that the balance will shift radically. /Loa -- Loa Andersson email: loa@pi.nu Senior MPLS Expert loa.pi.nu@gmail.com Bronze Dragon Consulting phone: +46 739 81 21 64