Coordination for Service IP in Multi-access Edge Computing
draft-du-coordination-for-serivce-ip-in-mec-00
This document is an Internet-Draft (I-D).
Anyone may submit an I-D to the IETF.
This I-D is not endorsed by the IETF and has no formal standing in the
IETF standards process.
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Zongpeng Du | ||
| Last updated | 2023-07-25 (Latest revision 2023-01-16) | ||
| RFC stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| 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 coordinatable mechanism for the Service IP in Multi-access Edge Computing. The Service IP means that an IP address is associated with a specific service in the network. For example, the IP address is deployed as an anycast address for Computing Aware Networking (CAN).
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)