Script updating gh-pages from d891e7d. [ci skip]

draft-ietf-quic-transport.html

@@ -5570,27 +5570,32 @@ <h2 id="name-packet-size">
 supports a reasonable Maximum Transmission Unit (MTU).  Padding datagrams also
 helps reduce the amplitude of amplification attacks caused by server responses
 toward an unverified client address; see <a href="#address-validation" class="xref">Section 8</a>.<a href="#section-14-2" class="pilcrow">¶</a></p>
-<p id="section-14-3">Datagrams containing Initial packets MAY exceed 1200 bytes if the client
-believes that the Path Maximum Transmission Unit (PMTU) supports the size that
-it chooses.<a href="#section-14-3" class="pilcrow">¶</a></p>
-<p id="section-14-4">UDP datagrams MUST NOT be fragmented at the IP layer.  In IPv4
-<span>[<a href="#IPv4" class="xref">IPv4</a>]</span>, the DF bit MUST be set to prevent fragmentation on the path.<a href="#section-14-4" class="pilcrow">¶</a></p>
-<p id="section-14-5">A server MUST discard an Initial packet that is carried in a UDP datagram that
-is smaller than 1200 bytes.  A server MAY also immediately close the connection
-by sending a CONNECTION_CLOSE frame with an error code of PROTOCOL_VIOLATION;
-see <a href="#immediate-close-hs" class="xref">Section 10.3.1</a>.<a href="#section-14-5" class="pilcrow">¶</a></p>
-<p id="section-14-6">The server MUST also limit the number of bytes it sends before validating the
-address of the client; see <a href="#address-validation" class="xref">Section 8</a>.<a href="#section-14-6" class="pilcrow">¶</a></p>
+<p id="section-14-3">Enforcement of the max_udp_payload_size transport parameter
+(<a href="#transport-parameter-definitions" class="xref">Section 18.2</a>) might act as an additional limit on
+packet size. Exceeding this limit can be avoided once the value is known.
+However, prior to learning the value of the transport parameter, endpoints risk
+datagrams being lost if they send packets larger than 1200 bytes.<a href="#section-14-3" class="pilcrow">¶</a></p>
+<p id="section-14-4">Datagrams containing Initial packets MAY exceed 1200 bytes if the client
+believes that the network path and peer both support the size that it chooses.<a href="#section-14-4" class="pilcrow">¶</a></p>
+<p id="section-14-5">UDP datagrams MUST NOT be fragmented at the IP layer.  In IPv4
+<span>[<a href="#IPv4" class="xref">IPv4</a>]</span>, the DF bit MUST be set to prevent fragmentation on the path.<a href="#section-14-5" class="pilcrow">¶</a></p>
+<p id="section-14-6">A server MUST discard an Initial packet that is carried in a UDP datagram with
+a payload that is less than 1200 bytes. A server MAY also immediately close the
+connection by sending a CONNECTION_CLOSE frame with an error code of
+PROTOCOL_VIOLATION; see <a href="#immediate-close-hs" class="xref">Section 10.3.1</a>.<a href="#section-14-6" class="pilcrow">¶</a></p>
+<p id="section-14-7">The server MUST also limit the number of bytes it sends before validating the
+address of the client; see <a href="#address-validation" class="xref">Section 8</a>.<a href="#section-14-7" class="pilcrow">¶</a></p>
 <div id="path-maximum-transmission-unit-pmtu">
 <section id="section-14.1">
         <h3 id="name-path-maximum-transmission-u">
 <a href="#section-14.1" class="section-number selfRef">14.1. </a><a href="#name-path-maximum-transmission-u" class="section-name selfRef">Path Maximum Transmission Unit (PMTU)</a>
         </h3>
-<p id="section-14.1-1">The PMTU is the maximum size of the entire IP packet including the IP header,
-UDP header, and UDP payload.  The UDP payload includes the QUIC packet header,
-protected payload, and any authentication fields. The PMTU can depend upon the
-current path characteristics.  Therefore, the current largest UDP payload an
-implementation will send is referred to as the QUIC maximum packet size.<a href="#section-14.1-1" class="pilcrow">¶</a></p>
+<p id="section-14.1-1">The Path Maximum Transmission Unit (PMTU) is the maximum size of the entire IP
+packet including the IP header, UDP header, and UDP payload.  The UDP payload
+includes the QUIC packet header, protected payload, and any authentication
+fields.  The PMTU can depend on path characteristics, and can therefore change
+over time.  The largest UDP payload an endpoint sends at any given time is
+referred to as the endpoint's maximum packet size.<a href="#section-14.1-1" class="pilcrow">¶</a></p>
 <p id="section-14.1-2">QUIC depends on a PMTU of at least 1280 bytes. This is the IPv6 minimum size
 <span>[<a href="#RFC8200" class="xref">RFC8200</a>]</span> and is also supported by most modern IPv4 networks.  All QUIC
 packets (except for PMTU probe packets) SHOULD be sized to fit within the