BGP NLRI App Meta Data for 5G Edge Computing Service
draft-dunbar-idr-5g-edge-compute-app-meta-data-02
Document | Type |
This is an older version of an Internet-Draft whose latest revision state is "Replaced".
Expired & archived
|
|
---|---|---|---|
Authors | Linda Dunbar , Kausik Majumdar , Haibo Wang | ||
Last updated | 2021-09-09 (Latest revision 2021-03-08) | ||
Replaced by | draft-dunbar-idr-5g-edge-service-metadata | ||
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 a new BGP Network Layer Reachability Information (BGP NLRI) Path Attribute, AppMetaData, for egress router to advertise the running status and environment of the directly attached 5G Edge Computing servers. The AppMetaData can be used by the ingress routers in the 5G Local Data Network to make intelligent path selection for flows from UEs. The goal is to improve latency and performance for 5G Edge Computing services. The extension enables a feature, called soft anchoring, which makes one Edge Computing Server at one specific location to be more preferred than others for the same application to receive packets from a specific source (UE).
Authors
Linda Dunbar
Kausik Majumdar
Haibo Wang
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)