draft-ietf-httpbis-h3-websockets-00.txt   draft-ietf-httpbis-h3-websockets-latest.txt 
HTTP Working Group R. Hamilton HTTP Working Group R. Hamilton
Internet-Draft Google Internet-Draft Google
Intended status: Informational September 10, 2021 Intended status: Informational September 13, 2021
Expires: March 14, 2022 Expires: March 17, 2022
Bootstrapping WebSockets with HTTP/3 Bootstrapping WebSockets with HTTP/3
draft-ietf-httpbis-h3-websockets-00 draft-ietf-httpbis-h3-websockets-latest
Abstract Abstract
The mechanism for running the WebSocket Protocol over a single stream The mechanism for running the WebSocket Protocol over a single stream
of an HTTP/2 connection is equally applicable to HTTP/3, but needs to of an HTTP/2 connection is equally applicable to HTTP/3, but needs to
be separately registered. This document describes the mechanism for be separately registered. This document describes the mechanism for
HTTP/3. HTTP/3.
Note to Readers Note to Readers
skipping to change at page 1, line 45 skipping to change at page 1, line 45
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at https://datatracker.ietf.org/drafts/current/. Drafts is at https://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
This Internet-Draft will expire on March 14, 2022. This Internet-Draft will expire on March 17, 2022.
Copyright Notice Copyright Notice
Copyright (c) 2021 IETF Trust and the persons identified as the Copyright (c) 2021 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(https://trustee.ietf.org/license-info) in effect on the date of (https://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
skipping to change at page 3, line 15 skipping to change at page 3, line 15
pseudo header fields. It also defines a new HTTP/2 SETTING sent by a pseudo header fields. It also defines a new HTTP/2 SETTING sent by a
server to allow the client to use Extended CONNECT. server to allow the client to use Extended CONNECT.
The HTTP/3 stream closure is also analogous to the TCP connection The HTTP/3 stream closure is also analogous to the TCP connection
closure of [RFC6455]. Orderly TCP-level closures are represented as closure of [RFC6455]. Orderly TCP-level closures are represented as
a FIN bit on the stream (Section 4.2 of [HTTP3]). RST exceptions are a FIN bit on the stream (Section 4.2 of [HTTP3]). RST exceptions are
represented with an stream error (Section 8 of [HTTP3]) of type represented with an stream error (Section 8 of [HTTP3]) of type
H3_REQUEST_CANCELLED (Section 8.1 of [HTTP3]) H3_REQUEST_CANCELLED (Section 8.1 of [HTTP3])
The semantics of the headers and SETTING are identical to those in The semantics of the headers and SETTING are identical to those in
HTTP/2 as defined [RFC8441]. Appendix A.3 of [HTTP3] requires thatt HTTP/2 as defined [RFC8441]. Appendix A.3 of [HTTP3] requires that
HTTP/3 settings be registered separately for HTTP/3. The HTTP/3 settings be registered separately for HTTP/3. The
SETTINGS_ENABLE_CONNECT_PROTOCOL value is 0x08 (decimal 8), as in SETTINGS_ENABLE_CONNECT_PROTOCOL value is 0x08 (decimal 8), as in
HTTP/2. HTTP/2.
4. Security Considerations 4. Security Considerations
This document introduces no new security considerations beyond those This document introduces no new security considerations beyond those
discussed in [RFC8841]. discussed in [RFC8841].
5. IANA Considerations 5. IANA Considerations
 End of changes. 4 change blocks. 
5 lines changed or deleted 5 lines changed or added

This html diff was produced by rfcdiff 1.48. The latest version is available from http://tools.ietf.org/tools/rfcdiff/