Status of This Memo

This is an Internet Standards Track document.¶

This document is a product of the Internet Engineering Task Force (IETF). It represents the consensus of the IETF community. It has received public review and has been approved for publication by the Internet Engineering Steering Group (IESG). Further information on Internet Standards is available in Section 2 of RFC 7841.¶

Information about the current status of this document, any errata, and how to provide feedback on it may be obtained athttps://www.rfc-editor.org/info/rfc9220.¶

Copyright Notice

Copyright (c) 2022 IETF Trust and the persons identified as the document authors. All rights reserved.¶

This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (https://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Revised BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Revised BSD License.¶

Table of Contents

1.Introduction

"Bootstrapping WebSockets with HTTP/2"[RFC8441] defines an extensionto HTTP/2[HTTP/2] that is also useful in HTTP/3[HTTP/3].This extension makes use of an HTTP/2 setting.Appendix A.3 of [HTTP/3]gives some guidance on what changes (if any) are appropriate when portingsettings from HTTP/2 to HTTP/3.¶

2.Conventions and Definitions

The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in BCP 14[RFC2119][RFC8174] when, and only when, they appear in all capitals, as shown here.¶

3.WebSockets Upgrade over HTTP/3

[RFC8441] defines a mechanism for running the WebSocket Protocol[RFC6455] over a single stream of an HTTP/2 connection. It definesan Extended CONNECT method that specifies a new ":protocol"pseudo-header field and new semantics for the ":path" and ":authority"pseudo-header fields. It also defines a new HTTP/2 setting sent by a server toallow the client to use Extended CONNECT.¶

The semantics of the pseudo-header fields and setting are identical to thosein HTTP/2 as defined in[RFC8441].Appendix A.3 of [HTTP/3] requires thatHTTP/3 settings be registered separately for HTTP/3. TheSETTINGS_ENABLE_CONNECT_PROTOCOL value is 0x08 (decimal 8), as in HTTP/2.¶

If a server advertises support for Extended CONNECT but receives anExtended CONNECT request with a ":protocol" value that is unknown or isnot supported, the serverSHOULD respond to the request with a 501 (NotImplemented) status code (Section 15.6.2 of [HTTP]). A serverMAYprovide more information via a "problem details" response[RFC7807].¶

The HTTP/3 stream closure is also analogous to the TCP connectionclosure of[RFC6455]. Orderly TCP-level closures are represented asa FIN bit on the stream (Section 4.4 of [HTTP/3]). RST exceptions arerepresented with a stream error (Section 8 of [HTTP/3]) of typeH3_REQUEST_CANCELLED (Section 8.1 of [HTTP/3]).¶

4.Security Considerations

This document introduces no new security considerations beyond thosediscussed in[RFC8441].¶

5.IANA Considerations

This document registers a new setting in the "HTTP/3 Settings"registry (Section 11.2.2 of [HTTP/3]).¶

Value:

0x08¶

Setting Name:

SETTINGS_ENABLE_CONNECT_PROTOCOL¶

Default:

0¶

Status:

permanent¶

Specification:

This document¶

Change Controller:

IETF¶

Contact:

HTTP Working Group (ietf-http-wg@w3.org)¶

Acknowledgments

This document had reviews and input from many contributors in the IETF HTTPand QUIC Working Groups, with substantive input fromDavid Schinazi,Martin Thomson,Lucas Pardue,Mike Bishop,Dragana Damjanovic,Mark Nottingham, andJulian Reschke.¶

Author's Address