Re: [mpls] MPLS-RT Review of draft-gandhi-mpls-ioam-sr-04

Loa Andersson <loa@pi.nu> Thu, 07 January 2021 03:20 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 3DA0A3A149B; Wed, 6 Jan 2021 19:20:30 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.159
X-Spam-Level:
X-Spam-Status: No, score=-2.159 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, NICE_REPLY_A=-0.262, SPF_HELO_NONE=0.001, SPF_NONE=0.001, URIBL_BLOCKED=0.001] autolearn=unavailable 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 9YbtddR6QyFW; Wed, 6 Jan 2021 19:20:27 -0800 (PST)
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 3056E3A1498; Wed, 6 Jan 2021 19:20:26 -0800 (PST)
Received: from [192.168.1.11] (unknown [124.104.17.232]) (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 DF88D328239; Thu, 7 Jan 2021 04:20:23 +0100 (CET)
To: Stewart Bryant <stewart.bryant@gmail.com>, "Rakesh Gandhi (rgandhi)" <rgandhi=40cisco.com@dmarc.ietf.org>
Cc: "draft-gandhi-mpls-ioam-sr@ietf.org" <draft-gandhi-mpls-ioam-sr@ietf.org>, mpls-chairs <mpls-chairs@ietf.org>, mpls <mpls@ietf.org>
References: <CAA=duU21PHQoJP0cEX6o1K=EwUFqeH19YvcDPNJVKE9c2szS6w@mail.gmail.com> <F73A3CB31E8BE34FA1BBE3C8F0CB2AE2980ACEB1@dggeml530-mbs.china.huawei.com> <DM6PR11MB3115122E45D5D9734E2A7023BFD20@DM6PR11MB3115.namprd11.prod.outlook.com> <E683497C-449B-4756-90CA-F01A8D7983E8@gmail.com>
From: Loa Andersson <loa@pi.nu>
Message-ID: <bb8796b9-b4c9-1c04-c348-3a8624ddecaa@pi.nu>
Date: Thu, 07 Jan 2021 11:20:19 +0800
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101 Thunderbird/78.6.0
MIME-Version: 1.0
In-Reply-To: <E683497C-449B-4756-90CA-F01A8D7983E8@gmail.com>
Content-Type: text/plain; charset="windows-1252"; format="flowed"
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/mpls/cFDIH57NOZnWPteC7pAfpjzGvkg>
Subject: Re: [mpls] MPLS-RT Review of draft-gandhi-mpls-ioam-sr-04
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, 07 Jan 2021 03:20:30 -0000

Stewart,

If we want to make sure that packets are processed at evey node, is the 
new FEC complementary to the ACH-header or an alternative?

/Loa

On 05/01/2021 00:30, Stewart Bryant wrote:
> 
> 
>> On 4 Jan 2021, at 14:38, Rakesh Gandhi (rgandhi) 
>> <rgandhi=40cisco.com@dmarc.ietf.org 
>> <mailto:rgandhi=40cisco.com@dmarc.ietf.org>> wrote:
>>
>> <RG> Yes, this is similar to the entropy label where a mid-point node 
>> needs to scan the label stack to find the indicator label. We can add 
>> some text to clarify this. There is already an optimization to use a 
>> different indicator label for HbH compared to E2E case to 
>> unnecessarily avoid parsing the IOAM data fields.
> 
> The EL is entirely optional to process. It is no more than a hint to use 
> in ECMP and there is no architectural requirement to find it to operate 
> correctly.
> 
> If iOAM is purely a option then you could scan the stack and hope that 
> you can reach down far enough to find it. Though there is a fight to see 
> who gets to be the lowest label in range of the forwarding parser.
> 
> If you want to be sure that iOAM is processed HxH then you really need 
> to run it on a new FEC with that behaviour built into the FEC. That 
> would be the architected way of doing this in MPLS.
> 
> - Stewart
> 
> 
> 
> _______________________________________________
> 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