IPv6 Solution for 5G Edge Computing Sticky Service
draft-dunbar-6man-5g-edge-compute-sticky-service-04
Document | Type |
This is an older version of an Internet-Draft whose latest revision state is "Expired".
Expired & archived
|
|
---|---|---|---|
Authors | Linda Dunbar , John Kaippallimalil | ||
Last updated | 2021-10-03 (Latest revision 2021-04-01) | ||
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 draft describes the IPv6-based solutions that can stick an application flow originated from a mobile device to the same ANYCAST server location when the mobile device moves from one 5G cell site to another. The proposed solution expands the Application-aware ID and Service-Para options specified by [APN6] by including the ANYCAST Sticky Service location information in the IPv6 Hop-by- Hop or Destination Optional Header.
Authors
Linda Dunbar
John Kaippallimalil
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)