<?xml version="1.0" encoding="UTF-8"?>
<reference anchor="I-D.ietf-quic-multipath" target="https://datatracker.ietf.org/doc/html/draft-ietf-quic-multipath-21">
   <front>
      <title>Managing multiple paths for a QUIC connection</title>
      <author initials="Y." surname="Liu" fullname="Yanmei Liu">
         <organization>Alibaba Inc.</organization>
      </author>
      <author initials="Y." surname="Ma" fullname="Yunfei Ma">
         <organization>Uber Technologies Inc.</organization>
      </author>
      <author initials="Q." surname="De Coninck" fullname="Quentin De Coninck">
         <organization>University of Mons (UMONS)</organization>
      </author>
      <author initials="O." surname="Bonaventure" fullname="Olivier Bonaventure">
         <organization>UCLouvain and WELRI</organization>
      </author>
      <author initials="C." surname="Huitema" fullname="Christian Huitema">
         <organization>Private Octopus Inc.</organization>
      </author>
      <author initials="M." surname="Kühlewind" fullname="Mirja Kühlewind">
         <organization>Ericsson</organization>
      </author>
      <date month="March" day="17" year="2026" />
      <abstract>
	 <t>   This document specifies a multipath extension for the QUIC protocol
   to enable the simultaneous usage of multiple paths for a single
   connection.  It introduces explicit path identifiers to create,
   delete, and manage multiple paths.  This document does not specify
   address discovery or management, nor how applications using QUIC
   schedule traffic over multiple paths.

	 </t>
      </abstract>
   </front>
   <seriesInfo name="Internet-Draft" value="draft-ietf-quic-multipath-21" />
   
</reference>
