<?xml version="1.0" encoding="UTF-8"?>
<reference anchor="I-D.ietf-masque-connect-udp-listen" target="https://datatracker.ietf.org/doc/html/draft-ietf-masque-connect-udp-listen-12">
   <front>
      <title>Proxying Bound UDP in HTTP</title>
      <author initials="D." surname="Schinazi" fullname="David Schinazi">
         <organization>Google LLC</organization>
      </author>
      <author initials="A." surname="Singh" fullname="Abhijit Singh">
         <organization>Google LLC</organization>
      </author>
      <date month="June" day="8" year="2026" />
      <abstract>
	 <t>   The mechanism to proxy UDP in HTTP only allows each UDP proxying
   request to transmit to a specific host and port.  This is well suited
   for UDP client-server protocols such as HTTP/3, but is not sufficient
   for some UDP peer-to-peer protocols like WebRTC.  This document
   defines an extension to UDP proxying in HTTP that enables such use-
   cases.

	 </t>
      </abstract>
   </front>
   <seriesInfo name="Internet-Draft" value="draft-ietf-masque-connect-udp-listen-12" />
   
</reference>
