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

Loa Andersson <loa@pi.nu> Tue, 12 October 2021 06:38 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 7DEB23A10BF for <mpls@ietfa.amsl.com>; Mon, 11 Oct 2021 23:38:40 -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 hU8YRdgvScdi for <mpls@ietfa.amsl.com>; Mon, 11 Oct 2021 23:38:35 -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 E030D3A0E90 for <mpls@ietf.org>; Mon, 11 Oct 2021 23:38:22 -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 ED81B34A0C4; Tue, 12 Oct 2021 08:38:19 +0200 (CEST)
To: Kireeti Kompella <kireeti.ietf@gmail.com>, Greg Mirsky <gregimirsky@gmail.com>
Cc: "mpls@ietf.org" <mpls@ietf.org>
References: <f419b94c-b55b-d6b2-ca91-23c8f31f2677@pi.nu> <CA+RyBmW3eaSo2gUi5=KYHp8qAF0E+ykf1=ojaTmSZF0m=eoMHg@mail.gmail.com> <305E9D87-ECCE-4E64-930D-19F9CD104F02@gmail.com> <8406C791-B84E-4F89-8F0D-607C7674D56E@gmail.com>
From: Loa Andersson <loa@pi.nu>
Message-ID: <bf6f65f6-f74e-8c87-0278-02e644c4abe8@pi.nu>
Date: Tue, 12 Oct 2021 08:38:18 +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: <8406C791-B84E-4F89-8F0D-607C7674D56E@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/SGMph6uNGLRq0HMPgYqwdPfRRaQ>
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:38:48 -0000

Kireeti,



On 11/10/2021 20:22, Kireeti Kompella wrote:
> Here’s what I’m thinking for the next iteration of the draft.  We’ll 
> burn two bits for hbh and e2e.  I propose the following encoding:
> 00 — No PSD (go back to sleep)
> 01 — if you are a transit or end node, you SHOULD look at the PSD
> 10 — if you are a transit or end node, you MUST look at the PSD (use 
> with care)
> 11 — if you are a transit node, nothing interesting for you in the PSD; 
> if you are an end node, look at the PSD.  (i.e., no hbh, only e2e PSD).
> 
> Note that in the naive approach:
> 00 — no PSD
> 01 — only hbh PSD
> 10 — only e2e PSD
> 11 — both hbh & e2e PSD

I like the first better than than the second, isn't it true that hbh is 
always treated with LER's as if they were transit nodes?

/Loa
> 
> The action for 01 and 10 is pretty much the same.
> 
> Thoughts?
> 
> Kireeti.
> 
>> On Oct 11, 2021, at 10:48, Kireeti Kompella <kireeti.ietf@gmail.com 
>> <mailto:kireeti.ietf@gmail.com>> wrote:
>>
>> Hi Greg,
>>
>> There were separate indicators for h-by-h and e2e.  The e2e was 
>> removed following discussion in the DT; it will return in the next 
>> revision.
>>
>> Of course, the PSD carried and the processing needed will be different 
>> in the two cases as they carry different types of data.  Processing 
>> h-by-h will also have to deal with traversing a potentially large 
>> label stack (and occurs on many nodes), whereas processing e2e PSD 
>> will deal with a small label stack and just one node (the egress).
>>
>> :k
>>
>>> On Oct 11, 2021, at 09:27, Greg Mirsky <gregimirsky@gmail.com 
>>> <mailto:gregimirsky@gmail.com>> wrote:
>>>
>>> Hi Loa,
>>> I have a clarification question. As I understand it, FAI is to signal 
>>> ancillary data that is processed in hop-by-hop or end-to-end manner 
>>> (John proposed to have a separate indicator for each use case). The 
>>> impact on transit nodes is, likely, different. Do you think we need 
>>> to consider these cases separately?
>>>
>>> Regards,
>>> Greg
>>>
>>> On Sat, Oct 9, 2021 at 10:43 AM Loa Andersson <loa@pi.nu 
>>> <mailto: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
>>>     <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://www.ietf.org/mailman/listinfo/mpls
>>>     <https://www.ietf.org/mailman/listinfo/mpls>
>>>
>>> _______________________________________________
>>> mpls mailing list
>>> mpls@ietf.org <mailto:mpls@ietf.org>
>>> https://www.ietf.org/mailman/listinfo/mpls 
>>> <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