[mpls] where to find the indicator that yoou need to look after the Bos for information
Loa Andersson <loa@pi.nu> Wed, 17 March 2021 14:01 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 914983A0C6C for <mpls@ietfa.amsl.com>; Wed, 17 Mar 2021 07:01:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.897
X-Spam-Level:
X-Spam-Status: No, score=-1.897 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_NONE=0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
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 VXOmhw2X2rzL for <mpls@ietfa.amsl.com>; Wed, 17 Mar 2021 07:01:27 -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 9AFE13A0C62 for <mpls@ietf.org>; Wed, 17 Mar 2021 07:01:27 -0700 (PDT)
Received: from [192.168.1.11] (unknown [124.104.184.212]) (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 70E6A32A1F0 for <mpls@ietf.org>; Wed, 17 Mar 2021 15:01:25 +0100 (CET)
To: "mpls@ietf.org" <mpls@ietf.org>
From: Loa Andersson <loa@pi.nu>
Message-ID: <0132ffdc-b8e4-601b-d971-429ec19d8909@pi.nu>
Date: Wed, 17 Mar 2021 22:01:23 +0800
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101 Thunderbird/78.8.1
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/mpls/Seozn2ZpJzUUIgwSbhOvo_iypWY>
Subject: [mpls] where to find the indicator that yoou need to look after the Bos for information
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, 17 Mar 2021 14:01:30 -0000
Working group, One thing that I'm a bit concerned about is that there earlier have been some discussion about how deep a label stack can be and still be "scanned", e.g. to find indicator to go look after the BoS to find information that is needed. The figures on the maximum stack depth, that will allow this are pretty old, but we should agree on whether it is a real problem or not. If it is I think we should primarily look at solutions that give us that information in one of the label stack entries near the top of the stack. /Loa -- Loa Andersson email: loa@pi.nu Senior MPLS Expert loa.pi.nu@gmail.com Bronze Dragon Consulting phone: +46 739 81 21 64
- [mpls] where to find the indicator that yoou need… Loa Andersson