Internet-Draft ORIGIN in HTTP/3 July 2022
Bishop Expires 28 January 2023 [Page]
Workgroup:
HTTPbis
Internet-Draft:
draft-ietf-httpbis-origin-h3-latest
Published:
Intended Status:
Standards Track
Expires:
Author:
M. Bishop
Akamai

The ORIGIN Extension in HTTP/3

Abstract

The ORIGIN frame for HTTP/2 is equally applicable to HTTP/3, but needs to be separately registered. This document describes the ORIGIN frame for HTTP/3.

Status of This Memo

This Internet-Draft is submitted in full conformance with the provisions of BCP 78 and BCP 79.

Internet-Drafts are working documents of the Internet Engineering Task Force (IETF). Note that other groups may also distribute working documents as Internet-Drafts. The list of current Internet-Drafts is at https://datatracker.ietf.org/drafts/current/.

Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress."

This Internet-Draft will expire on 28 January 2023.

Table of Contents

1. Introduction

Existing RFCs define extensions to HTTP/2 [HTTP2] which remain useful in HTTP/3. Appendix A.2.3 of [HTTP3] describes the required updates for HTTP/2 frames to be used with HTTP/3.

[ORIGIN] defines the HTTP/2 ORIGIN frame, which indicates what origins are available on a given connection. It defines a single HTTP/2 frame type.

2. The ORIGIN HTTP/3 Frame

The ORIGIN HTTP/3 frame allows a server to indicate what origin(s) ([RFC6454]) the server would like the client to consider as members of the Origin Set (Section 2.3 of [ORIGIN]) for the connection within which it occurs.

Where HTTP/2 reserves Stream 0 for frames related to the state of the connection, HTTP/3 defines a pair of unidirectional streams called "control streams" for this purpose. Where [ORIGIN] indicates that the ORIGIN frame should be sent on Stream 0, this should be interpreted to mean the HTTP/3 control stream. The ORIGIN frame is sent from servers to clients on the server's control stream.

The layout and semantics of the frame payload are identical to those of the HTTP/2 frame defined in [ORIGIN]. The ORIGIN frame type is 0xc (decimal 12), as in HTTP/2.

3. Security Considerations

This document introduces no new security considerations beyond those discussed in [ORIGIN] and [HTTP3].

4. IANA Considerations

This document registers a frame type in the "HTTP/3 Frame Type" registry ([HTTP3]).

Table 1: Registered HTTP/3 Frame Types
Frame Type Value Specification
ORIGIN 0xc Section 2

5. References

5.1. Normative References

[HTTP2]
Thomson, M., Ed. and C. Benfield, Ed., "HTTP/2", RFC 9113, DOI 10.17487/RFC9113, , <https://www.rfc-editor.org/rfc/rfc9113>.
[HTTP3]
Bishop, M., Ed., "HTTP/3", RFC 9114, DOI 10.17487/RFC9114, , <https://www.rfc-editor.org/rfc/rfc9114>.
[ORIGIN]
Nottingham, M. and E. Nygren, "The ORIGIN HTTP/2 Frame", RFC 8336, DOI 10.17487/RFC8336, , <https://www.rfc-editor.org/rfc/rfc8336>.

5.2. Informative References

[RFC6454]
Barth, A., "The Web Origin Concept", RFC 6454, DOI 10.17487/RFC6454, , <https://www.rfc-editor.org/rfc/rfc6454>.

Author's Address

Mike Bishop
Akamai