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

xiao.min2@zte.com.cn Tue, 22 March 2022 05:57 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 080653A0819 for <bier@ietfa.amsl.com>; Mon, 21 Mar 2022 22:57:10 -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 iRYi4A3jMqf7 for <bier@ietfa.amsl.com>; Mon, 21 Mar 2022 22:57:05 -0700 (PDT)
Received: from mxhk.zte.com.cn (mxhk.zte.com.cn [63.216.63.35]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D79133A0817 for <bier@ietf.org>; Mon, 21 Mar 2022 22:57:04 -0700 (PDT)
Received: from mse-fl2.zte.com.cn (unknown [10.30.14.239]) (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 4KN1321pFWz7dFRk; Tue, 22 Mar 2022 13:57:02 +0800 (CST)
Received: from njxapp05.zte.com.cn ([10.41.132.204]) by mse-fl2.zte.com.cn with SMTP id 22M5unBa075611; Tue, 22 Mar 2022 13:56:49 +0800 (GMT-8) (envelope-from xiao.min2@zte.com.cn)
Received: from mapi (njxapp03[null]) by mapi (Zmail) with MAPI id mid201; Tue, 22 Mar 2022 13:56:49 +0800 (CST)
Date: Tue, 22 Mar 2022 13:56:49 +0800
X-Zmail-TransId: 2afb62396521507-eff2b
X-Mailer: Zmail v1.0
Message-ID: <202203221356493944935@zte.com.cn>
In-Reply-To: <BL0PR05MB5652ADBDD6DA80DAE36E2B8AD4169@BL0PR05MB5652.namprd05.prod.outlook.com>
References: BL0PR05MB56526573902EEC959F7F4072D4139@BL0PR05MB5652.namprd05.prod.outlook.com, 202203191430580019286@zte.com.cn, BL0PR05MB5652ADBDD6DA80DAE36E2B8AD4169@BL0PR05MB5652.namprd05.prod.outlook.com
Mime-Version: 1.0
From: xiao.min2@zte.com.cn
To: zzhang@juniper.net
Cc: bier@ietf.org
Content-Type: text/plain; charset="UTF-8"
X-MAIL: mse-fl2.zte.com.cn 22M5unBa075611
X-Fangmail-Gw-Spam-Type: 0
X-FangMail-Miltered: at cgslv5.04-192.168.250.138.novalocal with ID 6239652E.000 by FangMail milter!
X-FangMail-Envelope: 1647928622/4KN1321pFWz7dFRk/6239652E.000/10.30.14.239/[10.30.14.239]/mse-fl2.zte.com.cn/<xiao.min2@zte.com.cn>
X-Fangmail-Anti-Spam-Filtered: true
X-Fangmail-MID-QID: 6239652E.000/4KN1321pFWz7dFRk
Archived-At: <https://mailarchive.ietf.org/arch/msg/bier/0XnoybtqpViFay3Qm0LrkKdY9Tw>
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: Tue, 22 Mar 2022 05:57:10 -0000

Hi Jeffrey,

Please see inline with <XM>>>.

Best Regards,
Xiao Min
------------------原始邮件------------------
发件人:Jeffrey(Zhaohui)Zhang
收件人:肖敏10093570;
抄送人:bier@ietf.org;
日 期 :2022年03月22日 02:21
主 题 :RE: Re:[Bier] A comment about draft-xzlnp-bier-ioam
Hi Xiao Min,
The purpose of GDF is to use the same extension header format for functionalities that may be used at different layers. Fragmentation was one example, and IOAM is another.
<XM>>> I see your preference :)
Note that fragmentation is for edge-to-edge, however IOAM is for both edge-to-edge and hop-by-hop, trying to combine them is ambitious and not easy.

For that, it is ideal if IPv6/MPLS/BIER all could use the same extension headers.
<XM>>> Note that IPv6 IOAM draft (draft-ietf-ippm-ioam-ipv6-options) has passed WG LC in IPPM WG.
While this draft is about IOAM, if we talk about BIER extension headers we need to consider it holistically.
Jeffrey
Juniper Business Use Only
-----Original Message-----
From: xiao.min2@zte.com.cn <xiao.min2@zte.com.cn>
Sent: Saturday, March 19, 2022 7:31 AM
To: Jeffrey (Zhaohui) Zhang <zzhang@juniper.net>
Cc: bier@ietf.org
Subject: Re:[Bier] A comment about draft-xzlnp-bier-ioam
[External Email. Be cautious of content]
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://urldefense.com/v3/__https://www.ietf.org/archive/id/draft-zzhang-intarea-generic-delivery-functions-02.txt__;!!NEt6yMaO-gk!Q-3JJzNBtHRy-DGJNrQ4wqe7oXPyU1zkyW42eRc0vbprEoml9zmtJ_tA5MyGUkgy$ , and was mentioned in slide #6 of https://urldefense.com/v3/__https://datatracker.ietf.org/meeting/112/materials/slides-112-bier-03-bier-slicing-and-differentiation-00__;!!NEt6yMaO-gk!Q-3JJzNBtHRy-DGJNrQ4wqe7oXPyU1zkyW42eRc0vbprEoml9zmtJ_tA5F-dbdqg$  in IETF112 BIER session.
Thanks.
Jeffrey
Juniper Business Use Only
_______________________________________________
BIER mailing list
BIER@ietf.org
https://urldefense.com/v3/__https://www.ietf.org/mailman/listinfo/bier__;!!NEt6yMaO-gk!Q-3JJzNBtHRy-DGJNrQ4wqe7oXPyU1zkyW42eRc0vbprEoml9zmtJ_tA5JjrM0gJ$