Re:[Bier] Flow Label [was Re: BIER in IPv6 ---draft-zhang-bier-bierin6-04]

zhang.zheng@zte.com.cn Mon, 23 March 2020 06:47 UTC

Return-Path: <zhang.zheng@zte.com.cn>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 95AFD3A0808; Sun, 22 Mar 2020 23:47:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.897
X-Spam-Level:
X-Spam-Status: No, score=-1.897 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, 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 ttBj_Vdiee_K; Sun, 22 Mar 2020 23:47:08 -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 D27883A0805; Sun, 22 Mar 2020 23:47:07 -0700 (PDT)
Received: from mse-fl2.zte.com.cn (unknown [10.30.14.239]) by Forcepoint Email with ESMTPS id AD18215A977041CB5625; Mon, 23 Mar 2020 14:47:03 +0800 (CST)
Received: from njxapp04.zte.com.cn ([10.41.132.203]) by mse-fl2.zte.com.cn with SMTP id 02N6l2mv091742; Mon, 23 Mar 2020 14:47:02 +0800 (GMT-8) (envelope-from zhang.zheng@zte.com.cn)
Received: from mapi (njxapp02[null]) by mapi (Zmail) with MAPI id mid203; Mon, 23 Mar 2020 14:47:01 +0800 (CST)
Date: Mon, 23 Mar 2020 14:47:01 +0800
X-Zmail-TransId: 2afa5e785b6563db8acb
X-Mailer: Zmail v1.0
Message-ID: <202003231447019556464@zte.com.cn>
In-Reply-To: <0369a854-cfde-b0e6-3788-543ab2bea16c@gmail.com>
References: 0aaf9a4e017643af85cd246b04d1858c@huawei.com, 0369a854-cfde-b0e6-3788-543ab2bea16c@gmail.com
Mime-Version: 1.0
From: zhang.zheng@zte.com.cn
To: brian.e.carpenter@gmail.com
Cc: tonysietf@gmail.com, 6man@ietf.org, bier@ietf.org
Subject: Re:[Bier] Flow Label [was Re: BIER in IPv6 ---draft-zhang-bier-bierin6-04]
Content-Type: multipart/mixed; boundary="=====_001_next====="
X-MAIL: mse-fl2.zte.com.cn 02N6l2mv091742
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/BG9lst_hNryhUsJTRnP1T_7qXlQ>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 23 Mar 2020 06:47:14 -0000

Hi Brian,







Thank you very much for your comments!


Please find my answer below with [Sandy].






Thanks,


Sandy







原始邮件



发件人:BrianECarpenter <brian.e.carpenter@gmail.com>
收件人:Tony Przygienda <tonysietf@gmail.com>;张征00007940;
抄送人:6MAN <6man@ietf.org>;BIER WG <bier@ietf.org>;
日 期 :2020年03月23日 12:04
主 题 :[Bier] Flow Label [was Re: BIER in IPv6 ---draft-zhang-bier-bierin6-04]


Hi,

I have not read the whole draft but I did notice this:

>    The Flow-ID in the IPv6 packet SHOULD be copied from the entropy
>    field in the BIER encapsulation.

It's good that the BIER entropy field defined in RFC8296 is 20 bits long, but there are a few issues here:

1. Nit: in RFC 8200 the field is named "Flow Label", not "Flow-ID".
[Sandy]: Thank you for your pointing out this nit, the name of Flow Label will be corrected.




2. The text technically violates RFC8200, which states that the flow label is defined by RFC6437. 
3. RFC6437 recommends the flow label generation procedure to follow a certain rule:

   It is therefore RECOMMENDED
   that source hosts support the flow label by setting the flow label
   field for all packets of a given flow to the same value chosen from
   an approximation to a discrete uniform distribution.

but I didn't find any discussion in RFC8296 of how the BIER entropy value is generated. 

I think you could get round these two points by something like:

   The entropy value used in an IPv6 flow label SHOULD be generated
   by a method compatible with [RFC6437].
[Sandy]: Thank  you for your suggestion, the description will be updated. And you are right, BIER didn't define the generation of entropy field. There are many ways to generate the field for load-balancing or other purposes.





4. Finally, it seems to me that the flow label is useless by definition for link-local traffic; however, it's harmless. (I never really thought about that before.) Of course, it could be relevant for globally-reachable addresses.
[Sandy]: The entropy field takes effect on BIER layer. So yes, it may also be filled in flow label field, we use "SHOULD" here. :-)





Regards
   Brian Carpenter

_______________________________________________
BIER mailing list
BIER@ietf.org
https://www.ietf.org/mailman/listinfo/bier