IETF Logo Mail Archive

Re: [Idr] On the Calculation of Entropy Labels

Lizhenbin <lizhenbin@huawei.com> Mon, 22 March 2021 03:30 UTC

Return-Path: <lizhenbin@huawei.com>
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 BC65B3A0FE5 for <idr@ietfa.amsl.com>; Sun, 21 Mar 2021 20:30:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.004
X-Spam-Level:
X-Spam-Status: No, score=0.004 tagged_above=-999 required=5 tests=[HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-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 B19WoGsPwiNn for <idr@ietfa.amsl.com>; Sun, 21 Mar 2021 20:30:09 -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 ED58A3A0FDC for <idr@ietf.org>; Sun, 21 Mar 2021 20:30:08 -0700 (PDT)
Received: from fraeml737-chm.china.huawei.com (unknown [172.18.147.200]) by frasgout.his.huawei.com (SkyGuard) with ESMTP id 4F3fsx6MLQz682R0 for <idr@ietf.org>; Mon, 22 Mar 2021 11:21:25 +0800 (CST)
Received: from dggpemm100006.china.huawei.com (7.185.36.196) by fraeml737-chm.china.huawei.com (10.206.15.218) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2106.2; Mon, 22 Mar 2021 04:30:04 +0100
Received: from dggpemm500008.china.huawei.com (7.185.36.136) by dggpemm100006.china.huawei.com (7.185.36.196) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2106.2; Mon, 22 Mar 2021 11:30:02 +0800
Received: from dggpemm500008.china.huawei.com ([7.185.36.136]) by dggpemm500008.china.huawei.com ([7.185.36.136]) with mapi id 15.01.2106.013; Mon, 22 Mar 2021 11:30:02 +0800
From: Lizhenbin <lizhenbin@huawei.com>
To: "liu.yao71@zte.com.cn" <liu.yao71@zte.com.cn>
CC: "idr@ietf.org" <idr@ietf.org>
Thread-Topic: [Idr] On the Calculation of Entropy Labels
Thread-Index: AQHXGYuPARowuf13K0+kZgIusXAUe6qPX3aw
Date: Mon, 22 Mar 2021 03:30:02 +0000
Message-ID: <63e9c5834e9646bda4d0922e0326f47d@huawei.com>
References: <202103151908216203531@zte.com.cn>
In-Reply-To: <202103151908216203531@zte.com.cn>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.108.243.250]
Content-Type: multipart/alternative; boundary="_000_63e9c5834e9646bda4d0922e0326f47dhuaweicom_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/zqqVTfRQJlXnnzX6EPaaw9tIt6c>
Subject: Re: [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, 22 Mar 2021 03:30:14 -0000

Hi Yao,
Sorry for the late reply. The following information is for your reference:
1. The draft is as follows. In the presentation, we proposed the example to calculate the entropy label for the specific prefix and download the entropy label and the VPN label together for better load sharing in the network.
https://tools.ietf.org/html/draft-li-idr-mpls-path-programming-04

2. After the IDR session om which you did the presentation, I thought there is the difference between the idea in the draft and the draft in your draft. The draft is calculate the entropy label for the PREFIX and the idea is to calculate the entropy label position for the SR path.

3. I am a little doubtful about the benefit of calculating the position only. I am not sure about how will the position is calculated. If the fixed position is calculated for the SR path, but the traffic flows with different destination address will be carried by the SR path and the entropy labels is randomly calculated, can the load sharing be improved?


Best Regards,
Robin




From: liu.yao71@zte.com.cn [mailto:liu.yao71@zte.com.cn]
Sent: Monday, March 15, 2021 7:08 PM
To: idr@ietf.org; Lizhenbin <lizhenbin@huawei.com>
Subject: [Idr] On the Calculation of Entropy Labels


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

v2.23.0 | Report a Bug | By Email