Script updating gh-pages from 11494e1. [ci skip]

quicwg · Aug 8, 2019 · 11be570 · 11be570
1 parent ccea4db
commit 11be570
Show file tree

Hide file tree

Showing 16 changed files with 1,100 additions and 33,178 deletions.
diff --git a/draft-ietf-quic-transport.html b/draft-ietf-quic-transport.html
@@ -2938,7 +2938,7 @@ <h2 id="rfc.section.19.5">
 <h2 id="rfc.section.19.6">
 <a href="#rfc.section.19.6">19.6.</a> <a href="#frame-crypto" id="frame-crypto">CRYPTO Frame</a>
 </h2>
-<p id="rfc.section.19.6.p.1">The CRYPTO frame (type=0x06) is used to transmit cryptographic handshake messages. It can be sent in all packet types. The CRYPTO frame offers the cryptographic protocol an in-order stream of bytes.  CRYPTO frames are functionally identical to STREAM frames, except that they do not bear a stream identifier; they are not flow controlled; and they do not carry markers for optional offset, optional length, and the end of the stream.</p>
+<p id="rfc.section.19.6.p.1">The CRYPTO frame (type=0x06) is used to transmit cryptographic handshake messages. It can be sent in all packet types except 0-RTT. The CRYPTO frame offers the cryptographic protocol an in-order stream of bytes.  CRYPTO frames are functionally identical to STREAM frames, except that they do not bear a stream identifier; they are not flow controlled; and they do not carry markers for optional offset, optional length, and the end of the stream.</p>
 <p id="rfc.section.19.6.p.2">The CRYPTO frame is as follows:</p>
 <div id="rfc.figure.19"></div>
 <div id="crypto-format"></div>

diff --git a/draft-ietf-quic-transport.txt b/draft-ietf-quic-transport.txt
@@ -6019,10 +6019,10 @@ Internet-Draft           QUIC Transport Protocol             August 2019
 19.6.  CRYPTO Frame
 
    The CRYPTO frame (type=0x06) is used to transmit cryptographic
-   handshake messages.  It can be sent in all packet types.  The CRYPTO
-   frame offers the cryptographic protocol an in-order stream of bytes.
-   CRYPTO frames are functionally identical to STREAM frames, except
-   that they do not bear a stream identifier; they are not flow
+   handshake messages.  It can be sent in all packet types except 0-RTT.
+   The CRYPTO frame offers the cryptographic protocol an in-order stream
+   of bytes.  CRYPTO frames are functionally identical to STREAM frames,
+   except that they do not bear a stream identifier; they are not flow
    controlled; and they do not carry markers for optional offset,
    optional length, and the end of the stream.