IETF Logo Mail Archive

Re: [mpls] [EXTERNAL] Indicators in the stack and ancillary data after the BoS

Loa Andersson <loa@pi.nu> Thu, 17 June 2021 15:03 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 A1AF13A237B for <mpls@ietfa.amsl.com>; Thu, 17 Jun 2021 08:03:57 -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 7KN72GZm3kow for <mpls@ietfa.amsl.com>; Thu, 17 Jun 2021 08:03:52 -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 51F8B3A236B for <mpls@ietf.org>; Thu, 17 Jun 2021 08:03:52 -0700 (PDT)
Received: from [192.168.0.3] (c83-250-139-108.bredband.tele2.se [83.250.139.108]) (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 D464B34894A; Thu, 17 Jun 2021 17:03:50 +0200 (CEST)
To: John E Drake <jdrake@juniper.net>, Alexander Vainshtein <Alexander.Vainshtein@rbbn.com>, Stewart Bryant <stewart.bryant@gmail.com>
Cc: "mpls@ietf.org" <mpls@ietf.org>
References: <c7d696de-4d83-6e3b-7d10-dc787fdabc73@pi.nu,> <MW4PR03MB639576D1C4B872AA0F5A8553F6309@MW4PR03MB6395.namprd03.prod.outlook.com> <202106170323552620410@zte.com.cn> <MW4PR03MB6395DE6E57E7CBF041ABE8E2F60E9@MW4PR03MB6395.namprd03.prod.outlook.com> <E512176A-02D5-4F74-8644-EAC4E3938AEF@gmail.com> <MW4PR03MB6395DA0A79E5882ECAC2B7E4F60E9@MW4PR03MB6395.namprd03.prod.outlook.com> <BY3PR05MB80812F41AD9D8DF461407922C70E9@BY3PR05MB8081.namprd05.prod.outlook.com> <f6801e0a-7971-4fae-5ae2-03ed02be1436@pi.nu> <BY3PR05MB8081C22B286FC6878E16E459C70E9@BY3PR05MB8081.namprd05.prod.outlook.com>
From: Loa Andersson <loa@pi.nu>
Message-ID: <05f6b1f7-71ca-9a57-75f1-7f4389f4fb43@pi.nu>
Date: Thu, 17 Jun 2021 17:03:49 +0200
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101 Thunderbird/78.11.0
MIME-Version: 1.0
In-Reply-To: <BY3PR05MB8081C22B286FC6878E16E459C70E9@BY3PR05MB8081.namprd05.prod.outlook.com>
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/S-XGbKEL5s5y9SpoozaCdssy6BI>
Subject: Re: [mpls] [EXTERNAL] Indicators in the stack and ancillary data after the BoS
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, 17 Jun 2021 15:03:58 -0000

John,

I might have missed something, but I have not seen that defined 
anywhere; if we want a stand alone bit set in the FAI to be ancillary 
data, what is a bit that points to data after the BoS? In my mind any 
bit in the FAI is anindicator, that is why it named FAI.

But I'm willing to changed my mind about the naming as long as we have 
an agreement.

/Loa

On 17/06/2021 16:55, John E Drake wrote:
> Loa,
> 
> I thought the FAI proposal put ancillary data in the stack.
> 
> Yours Irrespectively,
> 
> John
> 
> 
> Juniper Business Use Only
> 
>> -----Original Message-----
>> From: Loa Andersson <loa@pi.nu>
>> Sent: Thursday, June 17, 2021 10:54 AM
>> To: John E Drake <jdrake@juniper.net>; Alexander Vainshtein
>> <Alexander.Vainshtein@rbbn.com>; Stewart Bryant
>> <stewart.bryant@gmail.com>
>> Cc: mpls@ietf.org
>> Subject: Re: [mpls] [EXTERNAL] Indicators in the stack and ancillary data after
>> the BoS
>>
>> [External Email. Be cautious of content]
>>
>>
>> DT,
>>
>> Quick comments on John's mail:
>>
>> On 17/06/2021 16:44, John E Drake wrote:
>>> *//*
>>>
>>> */[JD] As we start to add all sorts of nifty functions both within the
>>> stack and after it, we need to add these functions in such a way that
>>> a transit LSR that does not understand one or more of them still will
>>> be able to forward a packet containing them.
>>
>> Yes, we must have an architecture that supports that.
>>
>>> For example, if we were to
>>> add ancillary data in the label stack, it needs to be done in such a
>>> way as to allow a transit router to skip over the ancillary data that
>>> it doesn't understand./*
>>
>> Ancillary "data in the stack"?  Does not all ancillary data go after the BoS?
>>
>> /Loa
>>>
>>> *//*
>>>
>>> */I.e., incremental deployment is a fact of life and we have to live
>>> with it./*
>>>
>>
>> --
>>
>> Loa Andersson                        email: loa@pi.nu
>> Senior MPLS Expert                          loa.pi.nu@gmail.com
>> Bronze Dragon Consulting             phone: +46 739 81 21 64

-- 

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

v2.23.0 | Report a Bug | By Email