RTGwg participants: https://datatracker.ietf.org/doc/draft-dunbar-rtgwg-5g-edge-metadata-bgp-usage/ (Informational draft) describes the problems in the 5G Edge computing environment and how BGP can be used to propagating additional information, so that the ingress routers in the 5G Local Data Network can make path selection not only based on the routing distance but also the running environment of the destinations.
The draft-dunbar-rtgwg-5g-edge-metadata-bgp-usage is the companion draft to the https://datatracker.ietf.org/doc/draft-ietf-idr-5g-edge-service-metadata/, which describes three new sub-TLVs for egress routers to advertise the Edge Service Metadata of the directly attached edge services (ES). 5g-edge-metadata-bgp-usage was in IDR wg. After some discussion we think RTGwg is a more suitable WG for continue the discussion of draft-dunbar-rtgwg-5g-edge-metadata-bgp-usage as it only focuses on problem space and why/how to BGP. https://datatracker.ietf.org/doc/draft-dunbar-rtgwg-5g-edge-metadata-bgp-usage/ has those sections: 1. Introduction.............................................. 3 1.1. 5G Edge Computing Background......................... 3 1.2. 5G Edge Computing Network Properties................. 4 1.3. Problem of ANYCAST in 5G EC Environment.............. 5 1.4. Problem of Unbalanced Anycast Distribution........... 7 1.5. Problem of Application Server Relocation............. 7 2. Conventions used in this document......................... 8 3. Destination Metadata for 5G Edge Computing................ 9 3.1. Assumptions.......................................... 9 3.2. IP Layer Metrics to Gauge Traffic Load............... 9 3.3. Metadata Constrained Optimal Path Selection......... 10 4. Soft Anchoring of an ANYCAST Flow........................ 11 We would like to hear your thoughts on this. Thank you Linda
_______________________________________________ rtgwg mailing list [email protected] https://www.ietf.org/mailman/listinfo/rtgwg
