Re: [mpls] agenda for the design team meeting tonight

Loa Andersson <loa@pi.nu> Thu, 08 April 2021 13:34 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 B54AA3A17D8; Thu, 8 Apr 2021 06:34:19 -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, NICE_REPLY_A=-0.001, RCVD_IN_DNSWL_BLOCKED=0.001, 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 n3QB36Z3HR4L; Thu, 8 Apr 2021 06:34:14 -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 8FF903A17D5; Thu, 8 Apr 2021 06:34:14 -0700 (PDT)
Received: from [192.168.1.11] (unknown [124.104.213.60]) (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 2CCFA324635; Thu, 8 Apr 2021 15:34:11 +0200 (CEST)
To: Alexander Vainshtein <Alexander.Vainshtein@rbbn.com>
Cc: "mpls-chairs@ietf.org" <mpls-chairs@ietf.org>, "mpls@ietf.org" <mpls@ietf.org>
References: <SJ0PR03MB5935AA191258AE821321A5C6F6749@SJ0PR03MB5935.namprd03.prod.outlook.com>
From: Loa Andersson <loa@pi.nu>
Message-ID: <fffc0aae-e33b-fc3d-7f83-a375b7a6543b@pi.nu>
Date: Thu, 8 Apr 2021 21:34:09 +0800
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101 Thunderbird/78.9.0
MIME-Version: 1.0
In-Reply-To: <SJ0PR03MB5935AA191258AE821321A5C6F6749@SJ0PR03MB5935.namprd03.prod.outlook.com>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/mpls/o6kcd1WIb9bzuDwfuUPvi4FUOAg>
Subject: Re: [mpls] agenda for the design team meeting tonight
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: Thu, 08 Apr 2021 13:34:20 -0000

Sasha,

Thanks for answering, the answer is close to what I suspected, would 
that mean that

- if you have info at a depth where you can't reach it in normal 
operation would that mean that as long as executing on it is "optimal" 
it is no big deal

- but if execution is mandatory it is ill-advised to rely on scanning 
the entire stack?

A very different question is how we document these questions and answers.

/Loa


but there are some

On 08/04/2021 21:04, Alexander Vainshtein wrote:
> Loa and all,
> 
> Regarding one of the example questions in the agenda, namely "- does 
> scanning the entire stack have performance impacts".
> 
> AFAIK most (if not all) off-the-shelf-available NPUs have limits on the 
> depth of the label stack in which they, say, can see the <ELI, EL> pair 
> - see also RFC 8662 <https://tools.ietf.org/html/rfc8662> that has 
> introduced the notion of Entropy Readable Label Depth (ERLD).
> 
> To me this means that in most cases scanning the entire label stack 
> requires pushing the packet for slow path handling with the associated 
> performance impact.
> 
> Regards,
> 
> Sasha
> 
> Office: +972-39266302
> 
> Cell:      +972-549266302
> 
> Email:   Alexander.Vainshtein@rbbn.com
> 
> -----Original Message-----
> From: mpls <mpls-bounces@ietf.org> On Behalf Of Loa Andersson
> Sent: Thursday, April 8, 2021 3:37 PM
> To: mpls@ietf.org
> Cc: mpls-chairs@ietf.org
> Subject: [mpls] agenda for the design team meeting tonite
> 
> NOTICE: This email was received from an EXTERNAL sender.
> 
> Tentative agenda for the MPLS WG Open DT on carrying info in an MPLS 
> packet 2021-04-08 
> ===========================================================================
> 
> Calling the meeting
> 
> -------------------
> 
> - Apologies
> 
>     -- Yes, we had problem, and the Webex did go out late
> 
> - The times in the agenda is one hour off from what we said, at the
> 
>     wg chair meeting.
> 
> - Unfortunate collision with the IESG Teleconference
> 
>     Time: 07:00 US/Canada Pacific
> 
>           09:00 US/Canada Central
> 
>           10:00 US/Canada Eastern
> 
>           14:00 UTC
> 
>           15:00 United Kingdom
> 
>           16:00 Germany, France, Belgium
> 
>           17:00 Finland
> 
>     No ADs can participate today.
> 
> Tentative DT Structure
> 
> -------------------
> 
> Coordination: Loa Andersson
> 
> - meeting week 1 (e.g. this week)
> 
> Track 1: J Doe
> 
> - meeting Week 2 and 4
> 
> Track 2: K Doe
> 
> - meeting Week 2 and 5
> 
> DT output / Track output
> 
> ------------------------
> 
> - Document(s) that address general architecture, at BoS architecture and
> 
>     in the SPL architecture
> 
> - Could be a single document or three documents, possibly a BCP with
> 
>     3 RFC
> 
> - DT charter (?) anyone that want to work on it
> 
>     -- The design team will not takc over the solutions documents, but
> 
>        create architectural guidelines that should support the development
> 
>        of the solutions documents
> 
> DT input
> 
> --------
> 
> draft-bryant-mpls-dev-primer (walk through)
> 
> Questions
> 
> ---------
> 
> - What questions do we want answered
> 
>     -- example 1 - would it be beneficial to know already from the
> 
>        top label what to look for
> 
>     -- example 2 - does scanning the entire stack have performance impacts
> 
> - Decisions?
> 
>     -- how to keep track
> 
> - How do we document this
> 
>     -- should we use the wiki?
> 
> /Loa
> 
> --
> 
> Loa Andersson                        email: loa@pi.nu <mailto:loa@pi.nu>
> 
> Senior MPLS Expert loa.pi.nu@gmail.com <mailto:loa.pi.nu@gmail.com>
> 
> Bronze Dragon Consulting             phone: +46 739 81 21 64
> 
> _______________________________________________
> 
> mpls mailing list
> 
> mpls@ietf.org <mailto:mpls@ietf.org>
> 
> https://clicktime.symantec.com/3EHDLWkmGWWE4481kNXVLt36H2?u=https%3A%2F%2Fwww.ietf.org%2Fmailman%2Flistinfo%2Fmpls 
> <https://clicktime.symantec.com/3EHDLWkmGWWE4481kNXVLt36H2?u=https%3A%2F%2Fwww.ietf.org%2Fmailman%2Flistinfo%2Fmpls>
> 
> Notice: This e-mail together with any attachments may contain 
> information of Ribbon Communications Inc. and its Affiliates that is 
> confidential and/or proprietary for the sole use of the intended 
> recipient. Any review, disclosure, reliance or distribution by others or 
> forwarding without express permission is strictly prohibited. If you are 
> not the intended recipient, please notify the sender immediately and 
> then delete all copies, including any attachments.
> 
> 
> Notice: This e-mail together with any attachments may contain 
> information of Ribbon Communications Inc. and its Affiliates that is 
> confidential and/or proprietary for the sole use of the intended 
> recipient. Any review, disclosure, reliance or distribution by others or 
> forwarding without express permission is strictly prohibited. If you are 
> not the intended recipient, please notify the sender immediately and 
> then delete all copies, including any attachments.

-- 

Loa Andersson                        email: loa@pi.nu
Senior MPLS Expert                          loa.pi.nu@gmail.com
Bronze Dragon Consulting             phone: +46 739 81 21 64