<?xml version="1.0" encoding="UTF-8"?>
<reference anchor="I-D.duke-quic-version-aliasing" target="https://datatracker.ietf.org/doc/html/draft-duke-quic-version-aliasing-04">
   <front>
      <title>QUIC Version Aliasing</title>
      <author initials="M." surname="Duke" fullname="Martin Duke">
         <organization>F5 Networks, Inc.</organization>
      </author>
      <date month="October" day="30" year="2020" />
      <abstract>
	 <t>   The QUIC transport protocol [QUIC-TRANSPORT] preserves its future
   extensibility partly by specifying its version number.  There will be
   a relatively small number of published version numbers for the
   foreseeable future.  This document provides a method for clients and
   servers to negotiate the use of other version numbers in subsequent
   connections and encrypts Initial Packets using secret keys instead of
   standard ones.  If a sizeable subset of QUIC connections use this
   mechanism, this should prevent middlebox ossification around the
   current set of published version numbers and the contents of QUIC
   Initial packets, as well as improving the protocol&#x27;s privacy
   properties.

	 </t>
      </abstract>
   </front>
   <seriesInfo name="Internet-Draft" value="draft-duke-quic-version-aliasing-04" />
   
</reference>
