Re: [Dyncast] edge capability feedback

刘鹏 <liupengyjy@chinamobile.com> Thu, 11 March 2021 02:24 UTC

Return-Path: <liupengyjy@chinamobile.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 335183A0CC5 for <dyncast@ietfa.amsl.com>; Wed, 10 Mar 2021 18:24:57 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.6
X-Spam-Level:
X-Spam-Status: No, score=0.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HDRS_MISSP=2.499, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=no 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 vAQGhuIgXvvO for <dyncast@ietfa.amsl.com>; Wed, 10 Mar 2021 18:24:54 -0800 (PST)
Received: from cmccmta1.chinamobile.com (cmccmta1.chinamobile.com [221.176.66.79]) by ietfa.amsl.com (Postfix) with ESMTP id 6FE5B3A0CC4 for <dyncast@ietf.org>; Wed, 10 Mar 2021 18:24:53 -0800 (PST)
Received: from spf.mail.chinamobile.com (unknown[172.16.121.5]) by rmmx-syy-dmz-app01-12001 (RichMail) with SMTP id 2ee160497f685c4-3c956; Thu, 11 Mar 2021 10:24:41 +0800 (CST)
X-RM-TRANSID: 2ee160497f685c4-3c956
X-RM-TagInfo: emlType=0
X-RM-SPAM-FLAG: 00000000
Received: from PENG (unknown[223.69.29.32]) by rmsmtp-syy-appsvr03-12003 (RichMail) with SMTP id 2ee360497f64276-bb30a; Thu, 11 Mar 2021 10:24:41 +0800 (CST)
X-RM-TRANSID: 2ee360497f64276-bb30a
MIME-Version: 1.0
x-PcFlag: 5536bdee-d83a-4bdb-b3c2-89217ade1867_5_47171
X-Mailer: PC_RICHMAIL 2.8.5
Date: Thu, 11 Mar 2021 10:24:35 +0800
From: 刘鹏 <liupengyjy@chinamobile.com>
To: Michael McBride <michael.mcbride@futurewei.com>
Cc: dyncast <dyncast@ietf.org>
Message-ID: <20210311102435132657878@chinamobile.com>
Content-Type: multipart/Alternative; boundary="----=_001_NextPart132657878_=----"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dyncast/0HEMdAd7sYxUOarjBQFnImenakI>
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 02:24:57 -0000


Hi Mike,




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.




Regards,

Peng








Peng Liu | 刘鹏

China Mobile | 移动研究院

mobile phone:13810146105

email:  liupengyjy@chinamobile.com

 



发件人: Michael McBride

时间: 2021/03/11(星期四)05:22

收件人: dyncast;

主题: [Dyncast] edge capability feedback 

 

Hello all, 

  

Thank you for the very informative side meeting.  

  

I have a follow up question on discovery. In one of the slides it explains the need to steer traffic to the best edge. How do we know what that best edge is? Is there some feedback mechanism that edge equipment uses to inform a controller,  or other, of it’s compute, etc load in order for dyncast to dynamically steer traffic to the best edge equipment for a particular task? I ask this as some of us are working on a variety of data discovery use cases and wondering if you already have this feedback  mechanism solved. 

  

Thanks, 

mike