[Bier] comments on draft-ietf-bier-ipv6-requirements-06

zhang.zheng@zte.com.cn Wed, 29 July 2020 08:12 UTC

Return-Path: <zhang.zheng@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 CEBCD3A10A6 for <bier@ietfa.amsl.com>; Wed, 29 Jul 2020 01:12:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.918
X-Spam-Level:
X-Spam-Status: No, score=-1.918 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] 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 PKfqhxVLh0Db for <bier@ietfa.amsl.com>; Wed, 29 Jul 2020 01:12:47 -0700 (PDT)
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 E5A3D3A10A7 for <bier@ietf.org>; Wed, 29 Jul 2020 01:12:45 -0700 (PDT)
Received: from mse-fl1.zte.com.cn (unknown [10.30.14.238]) by Forcepoint Email with ESMTPS id C76537CB098D67E62FED; Wed, 29 Jul 2020 16:12:42 +0800 (CST)
Received: from njxapp04.zte.com.cn ([10.41.132.203]) by mse-fl1.zte.com.cn with SMTP id 06T8CZlK037460; Wed, 29 Jul 2020 16:12:35 +0800 (GMT-8) (envelope-from zhang.zheng@zte.com.cn)
Received: from mapi (njxapp01[null]) by mapi (Zmail) with MAPI id mid203; Wed, 29 Jul 2020 16:12:35 +0800 (CST)
Date: Wed, 29 Jul 2020 16:12:35 +0800
X-Zmail-TransId: 2af95f212f7307278135
X-Mailer: Zmail v1.0
Message-ID: <202007291612355171564@zte.com.cn>
Mime-Version: 1.0
From: zhang.zheng@zte.com.cn
To: michael.mcbride@futurewei.com, xiejingrong@huawei.com, senthil.dhanaraj@huawei.com, rajiva@cisco.com, zhuyq8@chinatelecom.cn, gyan.s.mishra@verizon.com
Cc: bier@ietf.org
Content-Type: multipart/mixed; boundary="=====_001_next====="
X-MAIL: mse-fl1.zte.com.cn 06T8CZlK037460
Archived-At: <https://mailarchive.ietf.org/arch/msg/bier/iCjQHt-QdHLmyrR2hDLrBbV1MRg>
Subject: [Bier] comments on draft-ietf-bier-ipv6-requirements-06
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: Wed, 29 Jul 2020 08:12:50 -0000

Hi authors,



I have some comments for this draft.





1. In section 2 problem statement, only the situation across non-BFR node (if I understand right, you mean BIER incapable node) is mentioned. 

In fact, some nodes just don't recognize BIER Ethernet type, but can also do BIER forwarding according to BIER header. This situation should also be included.




2. In section 3.1, 

"Reassembly/Re-fragmentation of a packet has to be executed on each

   BFR in such case."

I think the description of "reassembly/re-fragmentation function" is wrong.  

If some packet needs to be fragmented, BFIR does the fragment, and the fragmented packet is BIER payload, it won't be executed in BFR.

And the same with IPSEC ESP. The ESP is also the BIER payload, and the intermediate BFRs will not see it and execute it.

 


3. In section 3.2,

IPv6 extension header is described here. We know there are many IPv6 extension headers, the EHs encapsulation way may be different according to vendor's implementation and operator's deployment. 

And further, there are many options defined in HBH and DOH. In this situation, if BIER header is encoded in any of them, how to locate the BIER header and guarantee the fast forwarding?

If two or more extension header existed, how do we know there is a BIER header existed which must be used for forwarding?

If fragment EH is also carried in the packet, how do we know it need or needn't to be executed?




Thanks,

Sandy