<?xml version="1.0" encoding="UTF-8"?>
<reference anchor="I-D.filsfils-6man-structured-flow-label" target="https://datatracker.ietf.org/doc/html/draft-filsfils-6man-structured-flow-label-02">
   <front>
      <title>Structured Flow Label</title>
      <author initials="C." surname="Filsfils" fullname="Clarence Filsfils">
         <organization>Cisco Systems, Inc.</organization>
      </author>
      <author initials="A." surname="Abdelsalam" fullname="Ahmed Abdelsalam">
         <organization>Cisco Systems, Inc.</organization>
      </author>
      <author initials="S." surname="Zadok" fullname="Shay Zadok">
         <organization>Broadcom</organization>
      </author>
      <author initials="X." surname="Xu" fullname="Xiaohu Xu">
         <organization>Capitalonline</organization>
      </author>
      <author initials="W." surname="Cheng" fullname="Weiqiang Cheng">
         <organization>China Mobile</organization>
      </author>
      <author initials="D." surname="Voyer" fullname="Daniel Voyer">
         <organization>Bell Canada</organization>
      </author>
      <author initials="P." surname="Camarillo" fullname="Pablo Camarillo">
         <organization>Cisco Systems, Inc.</organization>
      </author>
      <date month="March" day="7" year="2022" />
      <abstract>
	 <t>   This document defines the IPv6 Structured Flow Label.  The seamless
   nature of the change to [RFC6437] is demonstrated.  Benefits of the
   solution are explained.  Use-cases are illustrated.

	 </t>
      </abstract>
   </front>
   <seriesInfo name="Internet-Draft" value="draft-filsfils-6man-structured-flow-label-02" />
   
</reference>
