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

Tianran Zhou <> Sat, 19 March 2022 13:58 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id D83693A13AA for <>; Sat, 19 Mar 2022 06:58:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -1.906
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 ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id t-CBNuOWOy0R for <>; Sat, 19 Mar 2022 06:58:35 -0700 (PDT)
Received: from ( []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 6EF6A3A13A6 for <>; Sat, 19 Mar 2022 06:58:35 -0700 (PDT)
Received: from (unknown []) by (SkyGuard) with ESMTP id 4KLMqf26Thz67JpL for <>; Sat, 19 Mar 2022 21:56:30 +0800 (CST)
Received: from ( by ( 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 ( by ( 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 ([]) by ([]) with mapi id 15.01.2308.021; Sat, 19 Mar 2022 21:58:29 +0800
From: Tianran Zhou <>
To: "xiao.min2" <>, "" <>
CC: bier <>
Thread-Topic: [Bier] A comment about draft-xzlnp-bier-ioam
Thread-Index: Adg6xfU8UxzNoslpTIerKIi728m8bgAUeF4AACBksSc=
Date: Sat, 19 Mar 2022 13:58:29 +0000
Message-ID: <>
References:, <>
In-Reply-To: <>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
Content-Type: multipart/alternative; boundary="_000_70744d4c01134e39b727bd921c225661huaweicom_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <>
Subject: Re: [Bier] A comment about draft-xzlnp-bier-ioam
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "\"Bit Indexed Explicit Replication discussion list\"" <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-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.



Sent from WeLink
发件人: xiao.min2<<>>
抄送: bier<<>>
主题: 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

日 期 :2022年03月18日 20:56
主 题 :[Bier] A comment about draft-xzlnp-bier-ioam
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, and was mentioned in slide #6 of in IETF112 BIER session.
Juniper Business Use Only
BIER mailing list

BIER mailing list