<?xml version="1.0" encoding="UTF-8"?>
<reference anchor="I-D.ietf-idr-5g-edge-service-metadata" target="https://datatracker.ietf.org/doc/html/draft-ietf-idr-5g-edge-service-metadata-33">
   <front>
      <title>BGP Extension for 5G Edge Service Metadata</title>
      <author initials="L." surname="Dunbar" fullname="Linda Dunbar">
         <organization>Futurewei</organization>
      </author>
      <author initials="K." surname="Majumdar" fullname="Kausik Majumdar">
         <organization>Oracle</organization>
      </author>
      <author initials="C." surname="Li" fullname="Cheng Li">
         <organization>Huawei Technologies</organization>
      </author>
      <author initials="G. S." surname="Mishra" fullname="Gyan Mishra">
         <organization>Verizon</organization>
      </author>
      <author initials="Z." surname="Du" fullname="Zongpeng Du">
         <organization>China Mobile</organization>
      </author>
      <date month="May" day="29" year="2026" />
      <abstract>
	 <t>   This draft describes a new Edge Metadata Path Attribute and some Sub-
   TLVs for egress routers to advertise the Edge Metadata about the
   attached edge services (ES).  The edge service Metadata can be used
   by the ingress routers in the 5G Local Data Network to make path
   selections not only based on the routing cost but also the running
   environment of the edge services.  The goal is to improve latency and
   performance for 5G edge services.

   The extension enables an edge service at one specific location to be
   more preferred than the others with the same IP address (ANYCAST) to
   receive data flow from a specific source, like a specific User
   Equipment (UE).


	 </t>
      </abstract>
   </front>
   <seriesInfo name="Internet-Draft" value="draft-ietf-idr-5g-edge-service-metadata-33" />
   
</reference>
