Architecture of Dynamic-Anycast in Compute First Networking (CFN- Dyncast)
draft-li-rtgwg-cfn-dyncast-architecture-00
rtgwg Y. Li
Internet-Draft L. Iannone
Intended status: Informational Huawei Technologies
Expires: May 4, 2021 J. He
City University of Hong Kong
L. Geng
P. Liu
China Mobile
Y. Cui
Tsinghua University
October 31, 2020
Architecture of Dynamic-Anycast in Compute First Networking (CFN-
Dyncast)
draft-li-rtgwg-cfn-dyncast-architecture-00
Abstract
Compute First Networking (CFN) Dynamic Anycast refers to in-network
edge computing, where a single service offered by a provider has
multiple instances attached to multiple edge sites. In this
scenario, flows are assigned and consistently forwarded to a specific
instance through an anycast approach based on the network status as
well as the status of the different instance.
This document describes an architecture for the Dynamic Anycast
(Dyncast) in Compute First Networking (CFN). It provides an
overview, a description of the various components, and a workflow
example showing how to provide a balanced multi-edge based service in
terms of both computing and networking resources through dynamic
anycast in real time.
Status of This Memo
This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet-
Drafts is at https://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress."
Li, et al. Expires May 4, 2021 [Page 1]
Internet-Draft CFN-dyncast Architecture October 2020
This Internet-Draft will expire on May 4, 2021.
Copyright Notice
Copyright (c) 2020 IETF Trust and the persons identified as the
document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents
(https://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License.
Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
2. Definition of Terms . . . . . . . . . . . . . . . . . . . . . 3
3. CFN-Dyncast Architecture Overview . . . . . . . . . . . . . . 4
4. Architectural Components and Interactions . . . . . . . . . . 5
4.1. Service Identity and Bindings . . . . . . . . . . . . . . 5
4.2. Service Notification between Instances and CFN node . . . 7
4.3. CFN Dyncast Control Plane . . . . . . . . . . . . . . . . 9
4.4. Service Demand Dispatching . . . . . . . . . . . . . . . 9
4.5. CFN Dispatcher . . . . . . . . . . . . . . . . . . . . . 10
5. Summary of the key elements of CFN Dyncast Architecture . . . 12
6. Conclusion (and call for contributions) . . . . . . . . . . . 13
7. Security Considerations . . . . . . . . . . . . . . . . . . . 13
8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 13
9. Informative References . . . . . . . . . . . . . . . . . . . 14
Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . . 14
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 14
1. Introduction
Dynamic anycast in Compute First Networking (CFN-Dyncast) use cases
and problem statements document
[I-D.geng-rtgwg-cfn-dyncast-ps-usecase] shows the usage scenarios
that require an edge to be dynamically selected from multiple edge
sites to serve an edge computing service demand based on computing
resource available at the site and network status in real time.
Multiple edges provide service equivalency and service dynamism in
CFN. The current network architecture in edge computing provides
Show full document text