[Dyncast] New Non-WG Mailing List: dyncast

IETF Secretariat <ietf-secretariat@ietf.org> Thu, 28 January 2021 15:18 UTC

Return-Path: <ietf-secretariat@ietf.org>
X-Original-To: dyncast@ietf.org
Delivered-To: dyncast@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 5D5FA3A1594; Thu, 28 Jan 2021 07:18:39 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: IETF Secretariat <ietf-secretariat@ietf.org>
To: "IETF Announcement List" <ietf-announce@ietf.org>
Cc: luigi.iannone@huawei.com, liyizhou@huawei.com, dyncast@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 7.24.0
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: ietf@ietf.org
Message-ID: <161184711930.8310.9647361763324555219@ietfa.amsl.com>
Date: Thu, 28 Jan 2021 07:18:39 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/dyncast/XWQ-tTO93E3NL8qhJuQtq3cHB2M>
Subject: [Dyncast] New Non-WG Mailing List: dyncast
X-BeenThere: dyncast@ietf.org
X-Mailman-Version: 2.1.29
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, 28 Jan 2021 15:18:39 -0000

A new IETF non-working group email list has been created.

List address: dyncast@ietf.org
Archive: https://mailarchive.ietf.org/arch/browse/dyncast/
To subscribe: https://www.ietf.org/mailman/listinfo/dyncast

Purpose:
Service providers are exploring the edge computing to achieve better 
response time and control over data by moving the computing services 
towards the edge of the network. There could be a huge number of edge 
sites, and at the same time each edge site has a limited and very 
dynamic computing capacity and load characteristics. Then the problem 
comes as how to optimally route service demands based on computing and 
network metrics to the best edge. Most current practices uses random or 
round robin way or use geographically closest one to decide the edge to 
handle the service demand. It considers the static characteristics like 
aliveness and geographical distance of edges. Dynamic status like 
computing load and network path status are not taken into account. In 
addition, the practices usually determine the best edge in respect to 
the computing and networking aspects separately rather than jointly. 
Dyncast (dynamic anyast) tries to route the computing service demands 
based on computing and network metrics jointly at the network layer to 
improve the efficiency.

This list belongs to IETF area: RTG

For additional information, please contact the list administrators.