Re: [mpls] What percentage will carry indicator/ancillary data in the future

Loa Andersson <loa@pi.nu> Tue, 12 October 2021 06:27 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 5F4843A0DDC for <mpls@ietfa.amsl.com>; Mon, 11 Oct 2021 23:27:33 -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, NICE_REPLY_A=-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 Gc9m0CeofQyZ for <mpls@ietfa.amsl.com>; Mon, 11 Oct 2021 23:27: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 5A8303A0824 for <mpls@ietf.org>; Mon, 11 Oct 2021 23:27:26 -0700 (PDT)
Received: from [192.168.1.94] (c-e605e353.020-236-73746f24.bbcust.telenor.se [83.227.5.230]) (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 2B84C34A0C4; Tue, 12 Oct 2021 08:27:23 +0200 (CEST)
To: Kireeti Kompella <kireeti.ietf@gmail.com>
Cc: mpls@ietf.org
References: <f419b94c-b55b-d6b2-ca91-23c8f31f2677@pi.nu> <EA628897-5A23-411D-92FC-438DC76B78D4@gmail.com>
From: Loa Andersson <loa@pi.nu>
Message-ID: <d95caa54-a3bb-fd1f-23a9-83580c0995f6@pi.nu>
Date: Tue, 12 Oct 2021 08:27:21 +0200
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101 Thunderbird/78.14.0
MIME-Version: 1.0
In-Reply-To: <EA628897-5A23-411D-92FC-438DC76B78D4@gmail.com>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Language: en-US
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/mpls/fMi1YEf70QMNvx5GflUFSH9LBPg>
Subject: Re: [mpls] What percentage will carry indicator/ancillary data in the future
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: Tue, 12 Oct 2021 06:27:34 -0000

Kireeti,

I had an off-line very short chat with Stewart on this, and what I took 
away from that discussion is that we probably need to drive the on what 
percentage of MPLS packet that carry indicators + ancillary data based 
on use cases.

I don't think the term ancillary is ambiguous, we have been over it 
several time in the DT and we have agreed every time.

Ancillary data are data data that helps the node take the correct 
forwarding decision. There are three types of ancillary data (if you 
look at how they are positioned in the packet:
- post stack data (PSD)
- in stack data (ISD)
- No data (NoD)

Counting NoD with ISD and PSD as ancillary data, is a bit of a tweak, 
but I think it is good from a descriptive point of view, and also there 
is some implicit data folded in with the indicator.



On 11/10/2021 18:18, Kireeti Kompella wrote:
> Hi Loa,
> 
> The term ancillary data is ambiguous: as I understand, it refers to both ISD and PSD.
> 
> Two points:
> 1. High value traffic will frequently use FAI/ISD/PSD.  Best effort traffic probably will probably do so less often.

   - I tned to agree, but it is kind of unproven and would require real
     measurements to prove

> 2. As we find more use cases for FAI, the percentages for both will go up.

   - this is likely
> 
> For example, mandating CW for L2 PWs (as has been done, and may be reinforced) will mean more post-stack headers.

   - agreed
> 
> The way I understand your question is: how often is the PSD looked at 

Well, yes and no, looking at PSD is part of it and might cost more 
processing than other ancillary data.
(since it potentially creates lots of work for the forwarding engine).

Yes. And that was where I started to think about this.

We should consider the answer to be: very often (for high-value 
traffic), and make sure we handle this case well.  Even if the average 
number is small (lots of best effort traffic with no PSD), it wouldn’t 
serve the community well to only drop a few packets, but all of them 
high-value :)

Yes, I thnk that is a good strategy.

/Loa

> 
> :k
> 
>> On Oct 9, 2021, at 10:43, Loa Andersson <loa@pi.nu> wrote:
>>
>> Design Team,
>>
>> I have one thing that I been thinking about.
>>
>> If we consider future mpls encapsulated packet, what percentage will carry indicators and ancillary data?
>>
>> /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 mailing list
>> mpls@ietf.org
>> https://www.ietf.org/mailman/listinfo/mpls

-- 

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