[Idr] On the Calculation of Entropy Labels

liu.yao71@zte.com.cn Mon, 15 March 2021 11:08 UTC

Return-Path: <liu.yao71@zte.com.cn>
X-Original-To: idr@ietfa.amsl.com
Delivered-To: idr@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6A9983A0CC1 for <idr@ietfa.amsl.com>; Mon, 15 Mar 2021 04:08:41 -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 DBfFmmAxWN1E for <idr@ietfa.amsl.com>; Mon, 15 Mar 2021 04:08:39 -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 76EF53A0CD6 for <idr@ietf.org>; Mon, 15 Mar 2021 04:08:38 -0700 (PDT)
Received: from mse-fl2.zte.com.cn (unknown [10.30.14.239]) by Forcepoint Email with ESMTPS id AC7C0D497D15C6CD7C31; Mon, 15 Mar 2021 19:08:35 +0800 (CST)
Received: from njxapp05.zte.com.cn ([10.41.132.204]) by mse-fl2.zte.com.cn with SMTP id 12FB8LiP000446; Mon, 15 Mar 2021 19:08:21 +0800 (GMT-8) (envelope-from liu.yao71@zte.com.cn)
Received: from mapi (njxapp01[null]) by mapi (Zmail) with MAPI id mid203; Mon, 15 Mar 2021 19:08:21 +0800 (CST)
Date: Mon, 15 Mar 2021 19:08:21 +0800
X-Zmail-TransId: 2af9604f4025b18eaf38
X-Mailer: Zmail v1.0
Message-ID: <202103151908216203531@zte.com.cn>
Mime-Version: 1.0
From: liu.yao71@zte.com.cn
To: idr@ietf.org, lizhenbin@huawei.com
Content-Type: multipart/mixed; boundary="=====_001_next====="
X-MAIL: mse-fl2.zte.com.cn 12FB8LiP000446
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/uhpJ0_b-p1IbOCRfh91ClGMGGP4>
Subject: [Idr] On the Calculation of Entropy Labels
X-BeenThere: idr@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Inter-Domain Routing <idr.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/idr>, <mailto:idr-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/idr/>
List-Post: <mailto:idr@ietf.org>
List-Help: <mailto:idr-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/idr>, <mailto:idr-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 15 Mar 2021 11:08:48 -0000

Hi Robin,

Thanks for your comments on draft-zhou-idr-bgp-srmpls-elp at the IDR meeting last week.

You mentioned that there's a work about calculating both the vlaue and the position of the entropy labels using the controller.

(Sorry I haven't find the draft, I would appreciate it if you could offer the name of the draft.)

Since the entropy label value for each flow may be different, the control needs to calculate the value and the position of ELs per flow, and needs to maintain the state of the label stack per flow.




The solution introduced in draft-zhou-idr-bgp-srmpls-elp is that the controller calculates the position of the ELs for each path. The method for calculating the EL value is unchanged, the ingress router computes a hash based on several fields from a given packet. 

The calculation and state in the controller is per path. This method is applicable to a network with many flows and ingress nodes.




Regards,

Yao