Re: [mpls] Comment on draft-gandhi-mpls-ioam-sr-05

xiao.min2@zte.com.cn Mon, 18 January 2021 08:43 UTC

Return-Path: <xiao.min2@zte.com.cn>
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 B85853A0C99 for <mpls@ietfa.amsl.com>; Mon, 18 Jan 2021 00:43:41 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.917
X-Spam-Level:
X-Spam-Status: No, score=-1.917 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H4=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, UNPARSEABLE_RELAY=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 1-7pTLfjn_wv for <mpls@ietfa.amsl.com>; Mon, 18 Jan 2021 00:43:40 -0800 (PST)
Received: from mxhk.zte.com.cn (mxhk.zte.com.cn [63.217.80.70]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 044DF3A0C94 for <mpls@ietf.org>; Mon, 18 Jan 2021 00:43:39 -0800 (PST)
Received: from mse-fl1.zte.com.cn (unknown [10.30.14.238]) by Forcepoint Email with ESMTPS id 53F02A749B7A99CD2A23; Mon, 18 Jan 2021 16:43:37 +0800 (CST)
Received: from njxapp05.zte.com.cn ([10.41.132.204]) by mse-fl1.zte.com.cn with SMTP id 10I8hAZg007965; Mon, 18 Jan 2021 16:43:10 +0800 (GMT-8) (envelope-from xiao.min2@zte.com.cn)
Received: from mapi (njxapp02[null]) by mapi (Zmail) with MAPI id mid201; Mon, 18 Jan 2021 16:43:10 +0800 (CST)
Date: Mon, 18 Jan 2021 16:43:10 +0800
X-Zmail-TransId: 2afa60054a1ec806bc42
X-Mailer: Zmail v1.0
Message-ID: <202101181643101723091@zte.com.cn>
In-Reply-To: <cac1524d-c0e0-3587-6b8e-f5ec39d167b8@pi.nu>
References: 202101181000168475475@zte.com.cn, cac1524d-c0e0-3587-6b8e-f5ec39d167b8@pi.nu
Mime-Version: 1.0
From: xiao.min2@zte.com.cn
To: loa@pi.nu
Cc: mpls@ietf.org
Content-Type: multipart/mixed; boundary="=====_001_next====="
X-MAIL: mse-fl1.zte.com.cn 10I8hAZg007965
Archived-At: <https://mailarchive.ietf.org/arch/msg/mpls/fhHik21vzelzpfwt29aiRK8HpX4>
Subject: Re: [mpls] Comment on draft-gandhi-mpls-ioam-sr-05
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: Mon, 18 Jan 2021 08:43:42 -0000

Hi Loa,

Please see inline my responses with <XM>.

Best Regards,
Xiao Min









原始邮件



发件人:LoaAndersson
收件人:肖敏10093570;
抄送人:mpls@ietf.org;
日 期 :2021年01月18日 16:01
主 题 :Re: [mpls] Comment on draft-gandhi-mpls-ioam-sr-05




Xiao,
 
I have not been active in any OAM work, and not in the iOAM development,  
so I'm on a learning curve. So one more question.
<XM> It's my pleasure if I can help here.


Inline please
 
 
On 18/01/2021 10:00, xiao.min2@zte.com.cn wrote:
> If I understand this correctly that is what is done by Hop-by-Hop IOAM.
> <XM> Per IOAM itself, the Edge-to-Edge IOAM and Hop-by-Hop IOAM are  
> independent of each other, they use different IOAM Option-Type. Per MPLS  
> indicator label, I agree with you that Hop-by-Hop IOAM indicator label  
> can be reused here, but IMHO the current text in this draft is not clear  
> on it.
 
Let us assume that a packet arrive to an egress node with (1) with an
e-2-e iOAM indicator and another packet (2) arrive with the hop-by-hop  
indicator.
 
Is there a difference t0 what the egress node do to (1) and what it does  
to (2)?
<XM> As I understand it, there is no difference. Here the only function of iOAM indicator is for the egress node to know there exists IOAM header below the MPLS label stack, and how to process the IOAM data fields within the IOAM header depends on IOAM Option-Type.


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