IETF Logo Mail Archive

Re: [Dyncast] edge capability feedback

Dirk Trossen <dirk.trossen@huawei.com> Thu, 11 March 2021 08:14 UTC

Return-Path: <dirk.trossen@huawei.com>
X-Original-To: dyncast@ietfa.amsl.com
Delivered-To: dyncast@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7991A3A1536 for <dyncast@ietfa.amsl.com>; Thu, 11 Mar 2021 00:14:47 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H2=-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 fK7kTQfhO9fT for <dyncast@ietfa.amsl.com>; Thu, 11 Mar 2021 00:14:45 -0800 (PST)
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 844923A1530 for <dyncast@ietf.org>; Thu, 11 Mar 2021 00:14:45 -0800 (PST)
Received: from fraeml711-chm.china.huawei.com (unknown [172.18.147.200]) by frasgout.his.huawei.com (SkyGuard) with ESMTP id 4Dx1mX0tHJz67xfN; Thu, 11 Mar 2021 16:08:44 +0800 (CST)
Received: from lhreml707-chm.china.huawei.com (10.201.108.56) by fraeml711-chm.china.huawei.com (10.206.15.60) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256) id 15.1.2106.2; Thu, 11 Mar 2021 09:14:43 +0100
Received: from lhreml701-chm.china.huawei.com (10.201.108.50) by lhreml707-chm.china.huawei.com (10.201.108.56) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.2106.2; Thu, 11 Mar 2021 08:14:42 +0000
Received: from lhreml701-chm.china.huawei.com ([10.201.68.196]) by lhreml701-chm.china.huawei.com ([10.201.68.196]) with mapi id 15.01.2106.013; Thu, 11 Mar 2021 08:14:42 +0000
From: Dirk Trossen <dirk.trossen@huawei.com>
To: Barry Greene <bgreene@senki.org>, 刘鹏 <liupengyjy@chinamobile.com>
CC: dyncast <dyncast@ietf.org>, Michael McBride <michael.mcbride@futurewei.com>
Thread-Topic: [Dyncast] edge capability feedback
Thread-Index: AQHXFh3mblcp9VvA7UuJxuHq54sAyap+InaAgABOoFA=
Date: Thu, 11 Mar 2021 08:14:42 +0000
Message-ID: <3a247b594c2e44889cd90fd182ba357a@huawei.com>
References: <20210311102435132657878@chinamobile.com> <9A6BA68B-3916-413E-BD29-62D4096DF1D3@senki.org>
In-Reply-To: <9A6BA68B-3916-413E-BD29-62D4096DF1D3@senki.org>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.47.8.151]
Content-Type: multipart/alternative; boundary="_000_3a247b594c2e44889cd90fd182ba357ahuaweicom_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/dyncast/bR3IkGHNObeptj9Fn6jGC6pPkPI>
Subject: Re: [Dyncast] edge capability feedback
X-BeenThere: dyncast@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: <dyncast.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dyncast>, <mailto:dyncast-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dyncast/>
List-Post: <mailto:dyncast@ietf.org>
List-Help: <mailto:dyncast-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dyncast>, <mailto:dyncast-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 11 Mar 2021 08:14:47 -0000

Hi Barry,

Thanks for the pointers. The use case draft does point to related work but it’s good to extend this  so the pointers are useful for that.

Best,

Dirk

From: Dyncast [mailto:dyncast-bounces@ietf.org] On Behalf Of Barry Greene
Sent: 11 March 2021 04:34
To: 刘鹏 <liupengyjy@chinamobile.com>
Cc: dyncast <dyncast@ietf.org>; Michael McBride <michael.mcbride@futurewei.com>
Subject: Re: [Dyncast] edge capability feedback




On Mar 10, 2021, at 8:24 PM, 刘鹏 <liupengyjy@chinamobile.com<mailto:liupengyjy@chinamobile.com>> wrote:

The edge node could inform it's status to the D-routers based on the metric, such as CPU load or other metrics for the specific instance if defined in the furture, then the D-router could choose a suitable edge considering both network and computing or other specific status. We have some experimental verification and functional implementation.

Have you done the due diligence in past work in this area?

What you described above sounds like the signaling in the DOTS work (shifting load based on DDoS).

It is also should similar to Cisco Distributed Direct Routing Protocol (1997ish), TIDP/TMP (early 2000s), and some other network oriented shifting of edge loads.

What would be helpful is a review of all the past efforts (go back to the ‘90s) and review what worked and what did not work.

v2.23.0 | Report a Bug | By Email