Re: [Dyncast] Fw: New Version Notification for draft-liu-dyncast-ps-usecases-00.txt

"Joel M. Halpern" <jmh@joelhalpern.com> Mon, 01 February 2021 14:24 UTC

Return-Path: <jmh@joelhalpern.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 32E413A11C2 for <dyncast@ietfa.amsl.com>; Mon, 1 Feb 2021 06:24:13 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.821
X-Spam-Level:
X-Spam-Status: No, score=-2.821 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, NICE_REPLY_A=-0.001, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=joelhalpern.com
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 YxZzIIn4C6f6 for <dyncast@ietfa.amsl.com>; Mon, 1 Feb 2021 06:24:11 -0800 (PST)
Received: from mailb2.tigertech.net (mailb2.tigertech.net [208.80.4.154]) (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 425FC3A11C1 for <dyncast@ietf.org>; Mon, 1 Feb 2021 06:24:11 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by mailb2.tigertech.net (Postfix) with ESMTP id 4DTqvH0PTmz1pGhN for <dyncast@ietf.org>; Mon, 1 Feb 2021 06:24:11 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=joelhalpern.com; s=2.tigertech; t=1612189451; bh=B07qZgowS43PbhgjAk4qoKgPj52Y/Iaf8JOcmhzzLxs=; h=Subject:To:References:From:Date:In-Reply-To:From; b=eZ7o5ZFbEu8c/cJZgjHXkblxXiPVmWTKPhaXxcrWkpfNAPZqC0sOQt0Gz6C0xiT8G JOwJaQer82DSAvPmagmKeQz4Qa/rLPeRnoOyjn0lB+tQcU0CHtreiIfdDy4XKpP3i7 KZJGOzhhiB2bkzvxhrBMquqlKRAb5MVY7f6SWfVA=
X-Quarantine-ID: <18ryjV4OduuO>
X-Virus-Scanned: Debian amavisd-new at b2.tigertech.net
Received: from [192.168.128.43] (unknown [50.225.209.66]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mailb2.tigertech.net (Postfix) with ESMTPSA id 4DTqvG4Gnvz1nyG3 for <dyncast@ietf.org>; Mon, 1 Feb 2021 06:24:10 -0800 (PST)
To: dyncast <dyncast@ietf.org>
References: <20210201182208896943333@chinamobile.com>
From: "Joel M. Halpern" <jmh@joelhalpern.com>
Message-ID: <30756d58-b445-6407-c7d6-6ea2ee58ba0a@joelhalpern.com>
Date: Mon, 1 Feb 2021 09:24:08 -0500
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101 Thunderbird/78.7.0
MIME-Version: 1.0
In-Reply-To: <20210201182208896943333@chinamobile.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/dyncast/c5bVMplABcwJWfV3h7yxN9BlQcI>
Subject: Re: [Dyncast] Fw: New Version Notification for draft-liu-dyncast-ps-usecases-00.txt
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: Mon, 01 Feb 2021 14:24:13 -0000

This problem statement draft seems to assume a particular approach to 
the solution.

It is not at all obvious, absent the assumptions, that one wants to put 
the information into routing at all.  There are multiple approaches that 
address the problem that do not require the use of anycast addressing or 
injecting the application placement dynamics into the underlying routing 
system.

Yours,
Joel

On 2/1/2021 5:22 AM, 刘鹏 wrote:
> Dear all,
> 
> 
> Welcome all to the mailing list for the problem of and work on dynamic 
> anycast, enabling the consideration of compute and network metrics in 
> the decision to route a flow of packets among more than one service 
> instance. We have now uploaded the use case and problem statement draft, 
> outlining a few pertinent use cases for this work, as well as 
> shortcomings of existing solutions and requirements for a desirable 
> solution. It is the intention to use this draft to frame the discussion 
> towards a possible solution proposal. To this end, we also plan on 
> releasing a first version of an architecture draft soon.
> 
> In the meantime, any comments and discussion on the use case and problem 
> statement draft is highly welcome!
> 
> 
> Best,
> 
> Peng Liu
> 
> 
> Peng Liu | 刘鹏
> China Mobile | 移动研究院
> mobile phone:13810146105
> email: _ liupengyjy@chinamobile.com_
> 
>     发件人: internet-drafts <mailto:internet-drafts@ietf.org>
>     时间: 2021/02/01(星期一)18:15
>     收件人: Dirk Trossen <mailto:dirk.trossen@huawei.com>;Peng Liu
>     <mailto:liupengyjy@chinamobile.com>;Peter Willis
>     <mailto:peter.j.willis@bt.com>;
>     主题: New Version Notification for draft-liu-dyncast-ps-usecases-00.txt
> 
> 
> A new version of I-D, draft-liu-dyncast-ps-usecases-00.txt
> has been successfully submitted by Dirk Trossen and posted to the
> IETF repository.
> 
> Name: draft-liu-dyncast-ps-usecases
> Revision: 00
> Title: Dynamic-Anycast (Dyncast) Use Cases and Problem Statement
> Document date: 2021-02-01
> Group: Individual Submission
> Pages: 14
> URL: https://www.ietf.org/archive/id/draft-liu-dyncast-ps-usecases-00.txt
> Status: https://datatracker.ietf.org/doc/draft-liu-dyncast-ps-usecases/
> Htmlized: 
> https://datatracker.ietf.org/doc/html/draft-liu-dyncast-ps-usecases
> Htmlized: https://tools.ietf.org/html/draft-liu-dyncast-ps-usecases-00
> 
> 
> Abstract:
> Service providers are exploring the edge computing to achieve better
> response time, control over data and carbon energy saving by moving
> the computing services towards the edge of the network in 5G MEC
> (Multi-access Edge Computing) scenarios, virtualized central office,
> and others. Providing services by sharing computing resources from
> multiple edges is an emerging concept that is becoming more useful
> for computationally intensive tasks. Ideally, services should be
> computationally balanced using service-specific metrics instead of
> simply dispatching the service in a static way, e.g., to the
> geographically closest edge since this may cause unbalanced usage of
> computing resources at edges which further degrades user experience
> and system utilization. This draft provides an overview of scenarios
> and problems associated with realizing such scenarios.
> 
> The document identifies several key areas which require more
> investigations in terms of architecture and protocol to achieve
> balanced computing and networking resource utilization among edges
> providing the services.
> 
> 
> 
> 
> Please note that it may take a couple of minutes from the time of submission
> until the htmlized version and diff are available at tools.ietf.org.
> 
> The IETF Secretariat
> 
> 
>