| rfc9220v2.txt | rfc9220.txt | |||
|---|---|---|---|---|
| Internet Engineering Task Force (IETF) R. Hamilton | Internet Engineering Task Force (IETF) R. Hamilton | |||
| Request for Comments: 9220 Google | Request for Comments: 9220 Google | |||
| Category: Standards Track April 2022 | Category: Standards Track June 2022 | |||
| ISSN: 2070-1721 | ISSN: 2070-1721 | |||
| Bootstrapping WebSockets with HTTP/3 | Bootstrapping WebSockets with HTTP/3 | |||
| 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 the | of an HTTP/2 connection is equally applicable to HTTP/3, but the | |||
| HTTP-version-specific details need to be specified. This document | HTTP-version-specific details need to be specified. This document | |||
| describes how the mechanism is adapted for HTTP/3. | describes how the mechanism is adapted for HTTP/3. | |||
| skipping to change at line 96 ¶ | skipping to change at line 96 ¶ | |||
| If a server advertises support for Extended CONNECT but receives an | If a server advertises support for Extended CONNECT but receives an | |||
| Extended CONNECT request with a ":protocol" value that is unknown or | Extended CONNECT request with a ":protocol" value that is unknown or | |||
| is not supported, the server SHOULD respond to the request with a 501 | is not supported, the server SHOULD respond to the request with a 501 | |||
| (Not Implemented) status code (Section 15.6.2 of [HTTP]). A server | (Not Implemented) status code (Section 15.6.2 of [HTTP]). A server | |||
| MAY provide more information via a "problem details" response | MAY provide more information via a "problem details" response | |||
| [RFC7807]. | [RFC7807]. | |||
| 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 [HTTP/3]). RST exceptions | a FIN bit on the stream (Section 4.4 of [HTTP/3]). RST exceptions | |||
| are represented with a stream error (Section 8 of [HTTP/3]) of type | are represented with a stream error (Section 8 of [HTTP/3]) of type | |||
| H3_REQUEST_CANCELLED (Section 8.1 of [HTTP/3]). | H3_REQUEST_CANCELLED (Section 8.1 of [HTTP/3]). | |||
| 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 [RFC8441]. | discussed in [RFC8441]. | |||
| 5. IANA Considerations | 5. IANA Considerations | |||
| skipping to change at line 121 ¶ | skipping to change at line 121 ¶ | |||
| Setting Name: SETTINGS_ENABLE_CONNECT_PROTOCOL | Setting Name: SETTINGS_ENABLE_CONNECT_PROTOCOL | |||
| Default: 0 | Default: 0 | |||
| Status: permanent | Status: permanent | |||
| Specification: This document | Specification: This document | |||
| Change Controller: IETF | Change Controller: IETF | |||
| Contact: HTTP Working Group (ietf-http-wg@w3.org) | Contact: HTTP Working Group (ietf-http-wg@w3.org) | |||
| 6. Normative References | 6. Normative References | |||
| [HTTP] Fielding, R., Ed., Nottingham, M., Ed., and J. Reschke, | [HTTP] Fielding, R., Ed., Nottingham, M., Ed., and J. Reschke, | |||
| Ed., "HTTP Semantics", RFC 9110, DOI 10.17487/RFC9110, | Ed., "HTTP Semantics", STD 97, RFC 9110, | |||
| April 2022, <https://www.rfc-editor.org/info/rfc9110>. | DOI 10.17487/RFC9110, June 2022, | |||
| <https://www.rfc-editor.org/info/rfc9110>. | ||||
| [HTTP/2] Thomson, M., Ed. and C. Benfield, Ed., "HTTP/2", RFC 9113, | [HTTP/2] Thomson, M., Ed. and C. Benfield, Ed., "HTTP/2", RFC 9113, | |||
| DOI 10.17487/RFC9113, April 2022, | DOI 10.17487/RFC9113, June 2022, | |||
| <https://www.rfc-editor.org/info/rfc9113>. | <https://www.rfc-editor.org/info/rfc9113>. | |||
| [HTTP/3] Bishop, M., Ed., "Hypertext Transfer Protocol Version 3 | [HTTP/3] Bishop, M., Ed., "HTTP/3", RFC 9114, DOI 10.17487/RFC9114, | |||
| (HTTP/3)", RFC 9114, DOI 10.17487/RFC9114, April 2022, | June 2022, <https://www.rfc-editor.org/info/rfc9114>. | |||
| <https://www.rfc-editor.org/info/rfc9114>. | ||||
| [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate | [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate | |||
| Requirement Levels", BCP 14, RFC 2119, | Requirement Levels", BCP 14, RFC 2119, | |||
| DOI 10.17487/RFC2119, March 1997, | DOI 10.17487/RFC2119, March 1997, | |||
| <https://www.rfc-editor.org/info/rfc2119>. | <https://www.rfc-editor.org/info/rfc2119>. | |||
| [RFC6455] Fette, I. and A. Melnikov, "The WebSocket Protocol", | [RFC6455] Fette, I. and A. Melnikov, "The WebSocket Protocol", | |||
| RFC 6455, DOI 10.17487/RFC6455, December 2011, | RFC 6455, DOI 10.17487/RFC6455, December 2011, | |||
| <https://www.rfc-editor.org/info/rfc6455>. | <https://www.rfc-editor.org/info/rfc6455>. | |||
| End of changes. 5 change blocks. | ||||
| 8 lines changed or deleted | 8 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/ | ||||