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

Tianran Zhou <zhoutianran@huawei.com> Sat, 19 March 2022 13:58 UTC

Return-Path: <zhoutianran@huawei.com>
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 D83693A13AA for <bier@ietfa.amsl.com>; Sat, 19 Mar 2022 06:58:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.906
X-Spam-Level:
X-Spam-Status: No, score=-1.906 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=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, 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 t-CBNuOWOy0R for <bier@ietfa.amsl.com>; Sat, 19 Mar 2022 06:58:35 -0700 (PDT)
Received: from frasgout.his.huawei.com (frasgout.his.huawei.com [185.176.79.56]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6EF6A3A13A6 for <bier@ietf.org>; Sat, 19 Mar 2022 06:58:35 -0700 (PDT)
Received: from fraeml706-chm.china.huawei.com (unknown [172.18.147.201]) by frasgout.his.huawei.com (SkyGuard) with ESMTP id 4KLMqf26Thz67JpL for <bier@ietf.org>; Sat, 19 Mar 2022 21:56:30 +0800 (CST)
Received: from kwepeml500002.china.huawei.com (7.221.188.128) by fraeml706-chm.china.huawei.com (10.206.15.55) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.2375.24; Sat, 19 Mar 2022 14:58:30 +0100
Received: from kwepeml500004.china.huawei.com (7.221.188.141) by kwepeml500002.china.huawei.com (7.221.188.128) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2308.21; Sat, 19 Mar 2022 21:58:29 +0800
Received: from kwepeml500004.china.huawei.com ([7.221.188.141]) by kwepeml500004.china.huawei.com ([7.221.188.141]) with mapi id 15.01.2308.021; Sat, 19 Mar 2022 21:58:29 +0800
From: Tianran Zhou <zhoutianran@huawei.com>
To: "xiao.min2" <xiao.min2@zte.com.cn>, "zzhang=40juniper.net" <zzhang=40juniper.net@dmarc.ietf.org>
CC: bier <bier@ietf.org>
Thread-Topic: [Bier] A comment about draft-xzlnp-bier-ioam
Thread-Index: Adg6xfU8UxzNoslpTIerKIi728m8bgAUeF4AACBksSc=
Date: Sat, 19 Mar 2022 13:58:29 +0000
Message-ID: <70744d4c01134e39b727bd921c225661@huawei.com>
References: BL0PR05MB56526573902EEC959F7F4072D4139@BL0PR05MB5652.namprd05.prod.outlook.com, <202203191430580019286@zte.com.cn>
In-Reply-To: <202203191430580019286@zte.com.cn>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Content-Type: multipart/alternative; boundary="_000_70744d4c01134e39b727bd921c225661huaweicom_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/bier/JbUetxX-z9j9wT-lDJEe36qP0e0>
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: Sat, 19 Mar 2022 13:58:40 -0000

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<mailto:xiao.min2@zte.com.cn>>
收件人: zzhang=40juniper.net<zzhang=40juniper.net@dmarc.ietf.org<mailto:zzhang=40juniper.net@dmarc.ietf.org>>
抄送: bier<bier@ietf.org<mailto: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