Dynamic-Anycast Architecture
draft-li-dyncast-architecture-00
| Document | Type |
This is an older version of an Internet-Draft whose latest revision state is "Expired".
Expired & archived
|
|
|---|---|---|---|
| Authors | Yizhou Li , Luigi Iannone , Dirk Trossen , Peng Liu | ||
| Last updated | 2021-08-19 (Latest revision 2021-02-15) | ||
| RFC stream | (None) | ||
| Formats | |||
| Additional resources | |||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Expired | |
| Telechat date | (None) | ||
| Responsible AD | (None) | ||
| Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
Abstract
This document describes a proposal for an architecture for the Dynamic-Anycast (Dyncast). It includes an architecture overview, main components that shall exist, and the workflow. An example of workflow is provided, focusing on the load-balance multi-edge based service use-case, where load is distributed in terms of both computing and networking resources through the dynamic anycast architecture.
Authors
Yizhou Li
Luigi Iannone
Dirk Trossen
Peng Liu
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)