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

"Joel M. Halpern" <jmh@joelhalpern.com> Tue, 02 February 2021 02:26 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 8BF8A3A1697 for <dyncast@ietfa.amsl.com>; Mon, 1 Feb 2021 18:26:53 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.121
X-Spam-Level:
X-Spam-Status: No, score=-2.121 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_MSPIKE_H4=-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 CEgiCfRyFmnb for <dyncast@ietfa.amsl.com>; Mon, 1 Feb 2021 18:26:51 -0800 (PST)
Received: from maila2.tigertech.net (maila2.tigertech.net [208.80.4.152]) (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 D71063A1696 for <dyncast@ietf.org>; Mon, 1 Feb 2021 18:26:51 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by maila2.tigertech.net (Postfix) with ESMTP id 4DV7x74bYlz6GDyV; Mon, 1 Feb 2021 18:26:51 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=joelhalpern.com; s=2.tigertech; t=1612232811; bh=vdexhR2JHu2uwptuzbhN60hnPbALa5/VKGtVLONo5EI=; h=Subject:To:References:From:Date:In-Reply-To:From; b=SG61x5C61qJvd4i3XylWX+YHjm/MGIkAy8VY84M6G2Nmiw/m9g00cj/X+lEO13CUI t5zFUl/KIMU7noWpOvxA4PLl5Ov3Z1WS2F++kT2uT6NixBk8Hqlm2Ji9KOoFiRVvzP pr3yP4PTu4AST+5huMJutthqGbFSigkAWy3AZVHU=
X-Quarantine-ID: <awnsSYOmEc22>
X-Virus-Scanned: Debian amavisd-new at a2.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 maila2.tigertech.net (Postfix) with ESMTPSA id 4DV7x63g6Lz6GD8D; Mon, 1 Feb 2021 18:26:50 -0800 (PST)
To: liupengyjy <liupengyjy@chinamobile.com>, jmh@joelhalpern.com, dyncast@ietf.org
References: <20210201182208896943333@chinamobile.com> <30756d58-b445-6407-c7d6-6ea2ee58ba0a@joelhalpern.com> <d6155f12-2010-419d-af0b-2d1163e2bea4@email.android.com>
From: "Joel M. Halpern" <jmh@joelhalpern.com>
Message-ID: <1bd95fb9-f84f-8ce1-e68b-9df2e6e5ff82@joelhalpern.com>
Date: Mon, 1 Feb 2021 21:26:48 -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: <d6155f12-2010-419d-af0b-2d1163e2bea4@email.android.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/4OW4HTa9VakW-oolxBRqYmFBMAA>
Subject: Re: [Dyncast] New Version Notification fordraft-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: Tue, 02 Feb 2021 02:26:54 -0000

There are two quite separate issues.
As a new activity, a problem statement can be very useful.  But for it 
to be useful, it needs to avoid presupposing a solution.
So I would strongly recommend that all the solution oriented material be 
removed to a separate draft.

As a second matter, in any solution draft, any proposal that wants to 
make use of anycast and routing state needs to discuss the state and 
information propagation aspects of any such proposals.

Yours,
Joel

On 2/1/2021 9:14 PM, liupengyjy wrote:
> Hi Joel,
> 
> The draft analyzes the gap of existing methods, and does not rule out 
> other methods can be implemented, but the efficiency needs to be verified.
> Moreover, in the edge computing scenario, many native services are 
> deployed by operators, so we think that the method of using anycast is 
> feasible.
> 
> Best,
> Peng Liu
> 
> 
> 
> 
> ------------------------------------------------------------------------
> *发件人:* "JoelM.Halpern" <jmh@joelhalpern.com>
> *发送日期:* Mon Feb 01 22:24:08 GMT+08:00 2021
> *收件人:* dyncast <dyncast@ietf.org>
> *主题:* Re: [Dyncast] Fw: New Version Notification 
> fordraft-liu-dyncast-ps-usecases-00.txt
> 
> 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  <https://www.ietf.org/archive/id/draft-liu-dyncast-ps-usecases-00.txt>
> Status:https://datatracker.ietf.org/doc/draft-liu-dyncast-ps-usecases  <https://datatracker.ietf.org/doc/draft-liu-dyncast-ps-usecases>/
> Htmlized:
> https://datatracker.ietf.org/doc/html/draft-liu-dyncast-ps-usecases  <https://datatracker.ietf.org/doc/html/draft-liu-dyncast-ps-usecases>
> Htmlized:https://tools.ietf.org/html/draft-liu-dyncast-ps-usecases-00  <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 attools.ietf.org  <http://tools.ietf.org>.
> 
> The IETF Secretariat
>