Script updating gh-pages from 633eca9. [ci skip]

draft-ietf-quic-http.html

@@ -1324,6 +1324,7 @@ <h1 id="rfc.section.9">
 <p id="rfc.section.9.p.1">The security considerations of HTTP/3 should be comparable to those of HTTP/2 with TLS.  Note that where HTTP/2 employs PADDING frames and Padding fields in other frames to make a connection more resistant to traffic analysis, HTTP/3 can rely on QUIC PADDING frames or employ the reserved frame and stream types discussed in <a href="#frame-grease" class="xref">Section 4.2.10</a> and <a href="#stream-grease" class="xref">Section 3.2.3</a>.</p>
 <p id="rfc.section.9.p.2">When HTTP Alternative Services is used for discovery for HTTP/3 endpoints, the security considerations of <a href="#ALTSVC" class="xref">[ALTSVC]</a> also apply.</p>
 <p id="rfc.section.9.p.3">Several protocol elements contain nested length elements, typically in the form of frames with an explicit length containing variable-length integers.  This could pose a security risk to an incautious implementer.  An implementation MUST ensure that the length of a frame exactly matches the length of the fields it contains.</p>
+<p id="rfc.section.9.p.4">Certain HTTP implementations use the client address for logging or access-control purposes.  Since a QUIC client&#8217;s address might change during a connection (and future versions might support simultaneous use of multiple addresses), such implementations will need to either actively retrieve the client&#8217;s current address or addresses when they are relevant or explicitly accept that the original address might change.</p>
 <h1 id="rfc.section.10">
 <a href="#rfc.section.10">10.</a> <a href="#iana-considerations" id="iana-considerations">IANA Considerations</a>
 </h1>