Re: [Bier] A comment about draft-xzlnp-bier-ioam

xiao.min2@zte.com.cn Mon, 21 March 2022 01:30 UTC

Return-Path: <xiao.min2@zte.com.cn>
X-Original-To: bier@ietfa.amsl.com
Delivered-To: bier@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 78B933A1744 for <bier@ietfa.amsl.com>; Sun, 20 Mar 2022 18:30:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.905
X-Spam-Level:
X-Spam-Status: No, score=-1.905 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, CTE_8BIT_MISMATCH=0.001, RCVD_IN_MSPIKE_H5=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, 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 mDtC0eRpsjhr for <bier@ietfa.amsl.com>; Sun, 20 Mar 2022 18:30:40 -0700 (PDT)
Received: from mxhk.zte.com.cn (mxhk.zte.com.cn [63.216.63.40]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4357E3A173D for <bier@ietf.org>; Sun, 20 Mar 2022 18:30:39 -0700 (PDT)
Received: from mse-fl1.zte.com.cn (unknown [10.30.14.238]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mxhk.zte.com.cn (FangMail) with ESMTPS id 4KMHB61d0tzBGB97; Mon, 21 Mar 2022 09:30:38 +0800 (CST)
Received: from njxapp01.zte.com.cn ([10.41.132.200]) by mse-fl1.zte.com.cn with SMTP id 22L1UMNA037425; Mon, 21 Mar 2022 09:30:22 +0800 (GMT-8) (envelope-from xiao.min2@zte.com.cn)
Received: from mapi (njxapp03[null]) by mapi (Zmail) with MAPI id mid201; Mon, 21 Mar 2022 09:30:22 +0800 (CST)
Date: Mon, 21 Mar 2022 09:30:22 +0800
X-Zmail-TransId: 2afb6237d52effffffffac1-31298
X-Mailer: Zmail v1.0
Message-ID: <202203210930225319809@zte.com.cn>
In-Reply-To: <70744d4c01134e39b727bd921c225661@huawei.com>
References: BL0PR05MB56526573902EEC959F7F4072D4139@BL0PR05MB5652.namprd05.prod.outlook.com, 202203191430580019286@zte.com.cn, 70744d4c01134e39b727bd921c225661@huawei.com
Mime-Version: 1.0
From: xiao.min2@zte.com.cn
To: zhoutianran=40huawei.com@dmarc.ietf.org
Cc: zzhang=40juniper.net@dmarc.ietf.org, bier@ietf.org
Content-Type: text/plain; charset="UTF-8"
X-MAIL: mse-fl1.zte.com.cn 22L1UMNA037425
X-Fangmail-Gw-Spam-Type: 0
X-FangMail-Miltered: at cgslv5.04-192.168.250.137.novalocal with ID 6237D53E.000 by FangMail milter!
X-FangMail-Envelope: 1647826238/4KMHB61d0tzBGB97/6237D53E.000/10.30.14.238/[10.30.14.238]/mse-fl1.zte.com.cn/<xiao.min2@zte.com.cn>
X-Fangmail-Anti-Spam-Filtered: true
X-Fangmail-MID-QID: 6237D53E.000/4KMHB61d0tzBGB97
Archived-At: <https://mailarchive.ietf.org/arch/msg/bier/cJF_0F2tmeVkYUyZOG7U1M1Kr-I>
Subject: Re: [Bier] A comment about draft-xzlnp-bier-ioam
X-BeenThere: bier@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "\"Bit Indexed Explicit Replication discussion list\"" <bier.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/bier>, <mailto:bier-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/bier/>
List-Post: <mailto:bier@ietf.org>
List-Help: <mailto:bier-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/bier>, <mailto:bier-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 21 Mar 2022 01:30:46 -0000

Hi Tianran,

Generally speaking that's because they (IPv6, MPLS, BIER) are different layers, as indicated in Jeffrey's GDF draft.
Specifically, my personal criteria is that whether this layer would affect packet forwarding, e.g., SFC NSH layer would, so there is an adopted NSH IOAM draft (draft-ietf-sfc-ioam-nsh), BIER layer is similar. For other layers that wouldn't affect packet forwarding, e.g., Geneve layer, the advantage to have IOAM over it is not clear to me.

Best Regards,
Xiao Min

------------------原始邮件------------------
发件人:TianranZhou
收件人:肖敏10093570;zzhang=40juniper.net;
抄送人:bier;
日 期 :2022年03月19日 21:58
主 题 :Re: [Bier] A comment about draft-xzlnp-bier-ioam
_______________________________________________
BIER mailing list
BIER@ietf.org
https://www.ietf.org/mailman/listinfo/bier

I have concern about so many options for the same functionality.
Especially, there’s already IOAM encapsulation for MPLS and IPv6. Why we need another encapsulation in BIER layer?
As far as I understand, BIER will always be used with MPLS or IPv6.
Tianran
Sent from WeLink
发件人: xiao.min2<xiao.min2@zte.com.cn>
收件人: zzhang=40juniper.net<zzhang=40juniper.net@dmarc.ietf.org>
抄送: bier<bier@ietf.org>
主题: Re: [Bier] A comment about draft-xzlnp-bier-ioam
时间: 2022-03-19 14:33:01
Hi Jeffrey,
Thank you for bringing it up to our attention.
I do agree your GDF draft provides a third option on how to encapsulate IOAM over BIER, which is different from the two options already described and compared in this BIER-IOAM draft.
To my understanding, the initial and main motivation to introduce GDF is to provide a fragmentation header for MPLS/BIER etc, just like IPv6 FH.
With that in mind, one possible way to push this "Encapsulating IOAM in BIER" work forward is to add the third option into BIER-IOAM draft for comparison, that makes it focused and easy to follow.
What's your opinion?
Best Regards,
Xiao Min
------------------原始邮件------------------
发件人:Jeffrey(Zhaohui)Zhang
收件人:'bier@ietf.org';draft-xzlnp-bier-ioam@ietf.org;
日 期 :2022年03月18日 20:56
主 题 :[Bier] A comment about draft-xzlnp-bier-ioam
Hi,
For IOAM data in BIER, I want to point out that we should use a generic header format that can be used for BIER/MPLS/IPv6. The same extension mechanism can be used for other purposes like fragmentation/security, etc.
This was discussed in  https://www.ietf.org/archive/id/draft-zzhang-intarea-generic-delivery-functions-02.txt, and was mentioned in slide #6 of  https://datatracker.ietf.org/meeting/112/materials/slides-112-bier-03-bier-slicing-and-differentiation-00 in IETF112 BIER session.
Thanks.
Jeffrey
Juniper Business Use Only
_______________________________________________
BIER mailing list
BIER@ietf.org
https://www.ietf.org/mailman/listinfo/bier
_______________________________________________
BIER mailing list
BIER@ietf.org
https://www.ietf.org/mailman/listinfo/bier