<?xml version="1.0" encoding="UTF-8"?>
<reference anchor="I-D.yi-idr-bgp-fs-edge-service-metadata" target="https://datatracker.ietf.org/doc/html/draft-yi-idr-bgp-fs-edge-service-metadata-00">
   <front>
      <title>Distribution of Service Metadata in BGP FlowSpec</title>
      <author initials="X." surname="Yi" fullname="Xinxin Yi">
         <organization>China Unicom</organization>
      </author>
      <author initials="T." surname="He" fullname="Tao He">
         <organization>China Unicom</organization>
      </author>
      <author initials="H." surname="Shi" fullname="Hang Shi">
         <organization>Huawei Technologies</organization>
      </author>
      <author initials="X." surname="Ding" fullname="Xiangfeng Ding">
         <organization>Huawei Technologies</organization>
      </author>
      <author initials="H." surname="Wang" fullname="Haibo Wang">
         <organization>Huawei Technologies</organization>
      </author>
      <date month="February" day="23" year="2023" />
      <abstract>
	 <t>   In edge computing, a service may be deployed on multiple instances
   within one or more sites, called edge service.  The edge service is
   associated with an ANYCAST IP address, and the route of it along with
   service metadata can be collected by a central controller.  The
   controller may process the metadata and distribute the result to
   ingress routers using BGP FlowSpec.  The service metadata can be used
   by ingress routers to make path selections not only based on the
   routing cost but also the running environment of the edge services.
   This document describes a mechanism to distribute the information of
   the service routes and related service metadata using BGP FlowSpec.

	 </t>
      </abstract>
   </front>
   <seriesInfo name="Internet-Draft" value="draft-yi-idr-bgp-fs-edge-service-metadata-00" />
   
</reference>
