idnits 2.17.1 draft-bishop-httpbis-origin-h3-00.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- No issues found here. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year -- The document date (1 September 2021) is 968 days in the past. Is this intentional? Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) No issues found here. Summary: 0 errors (**), 0 flaws (~~), 1 warning (==), 1 comment (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 HTTPbis M. Bishop 3 Internet-Draft Akamai 4 Intended status: Standards Track 1 September 2021 5 Expires: 5 March 2022 7 The ORIGIN Extension in HTTP/3 8 draft-bishop-httpbis-origin-h3-00 10 Abstract 12 The ORIGIN frame for HTTP/2 is equally applicable to HTTP/3, but 13 needs to be separately registered. This document describes the 14 ORIGIN frame for HTTP/3. 16 Status of This Memo 18 This Internet-Draft is submitted in full conformance with the 19 provisions of BCP 78 and BCP 79. 21 Internet-Drafts are working documents of the Internet Engineering 22 Task Force (IETF). Note that other groups may also distribute 23 working documents as Internet-Drafts. The list of current Internet- 24 Drafts is at https://datatracker.ietf.org/drafts/current/. 26 Internet-Drafts are draft documents valid for a maximum of six months 27 and may be updated, replaced, or obsoleted by other documents at any 28 time. It is inappropriate to use Internet-Drafts as reference 29 material or to cite them other than as "work in progress." 31 This Internet-Draft will expire on 5 March 2022. 33 Copyright Notice 35 Copyright (c) 2021 IETF Trust and the persons identified as the 36 document authors. All rights reserved. 38 This document is subject to BCP 78 and the IETF Trust's Legal 39 Provisions Relating to IETF Documents (https://trustee.ietf.org/ 40 license-info) in effect on the date of publication of this document. 41 Please review these documents carefully, as they describe your rights 42 and restrictions with respect to this document. Code Components 43 extracted from this document must include Simplified BSD License text 44 as described in Section 4.e of the Trust Legal Provisions and are 45 provided without warranty as described in the Simplified BSD License. 47 Table of Contents 49 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 50 2. Basic Mapping Conventions . . . . . . . . . . . . . . . . . . 2 51 3. The ORIGIN HTTP/3 Frame . . . . . . . . . . . . . . . . . . . 2 52 4. Security Considerations . . . . . . . . . . . . . . . . . . . 2 53 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 3 54 6. References . . . . . . . . . . . . . . . . . . . . . . . . . 3 55 6.1. Normative References . . . . . . . . . . . . . . . . . . 3 56 6.2. Informative References . . . . . . . . . . . . . . . . . 3 57 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 3 59 1. Introduction 61 Existing RFCs define extensions to HTTP/2 [HTTP2] which remain useful 62 in HTTP/3. Appendix A.2.3 of [HTTP3] describes the required updates 63 for HTTP/2 frames to be used with HTTP/3. 65 [ORIGIN] defines the HTTP/2 ORIGIN frame, which indicates what 66 origins are available on a given connection. It defines a single 67 HTTP/2 frame type. 69 2. Basic Mapping Conventions 71 3. The ORIGIN HTTP/3 Frame 73 The ORIGIN HTTP/3 frame allows a server to indicate what origin(s) 74 ([RFC6454]) the server would like the client to consider as members 75 of the Origin Set (Section 2.3 of [ORIGIN]) for the connection within 76 which it occurs. 78 Where HTTP/2 reserves Stream 0 for frames related to the state of the 79 connection, HTTP/3 defines a pair of unidirectional streams called 80 "control streams" for this purpose. Where [ORIGIN] indicates that 81 the ORIGIN frame should be sent on Stream 0, this should be 82 interpreted to mean the HTTP/3 control stream. The ORIGIN frame is 83 sent from servers to clients on the server's control stream. 85 The layout and semantics of the frame payload are identical to those 86 of the HTTP/2 frame defined in [ORIGIN]. The ORIGIN frame type is 87 0xc (decimal 12), as in HTTP/2. 89 4. Security Considerations 91 This document introduces no new security considerations beyond those 92 discussed in [ORIGIN] and [HTTP3]. 94 5. IANA Considerations 96 This document registers a frame type in the "HTTP/3 Frame Type" 97 registry ([HTTP3]). 99 +============+=======+===============+ 100 | Frame Type | Value | Specification | 101 +============+=======+===============+ 102 | ORIGIN | 0xc | Section 3 | 103 +------------+-------+---------------+ 105 Table 1: Registered HTTP/3 Frame Types 107 6. References 109 6.1. Normative References 111 [HTTP2] Belshe, M., Peon, R., and M. Thomson, "Hypertext Transfer 112 Protocol Version 2 (HTTP/2)", Work in Progress, Internet- 113 Draft, draft-ietf-httpbis-http2-17, 10 February 2015, 114 . 117 [HTTP3] Bishop, M., "Hypertext Transfer Protocol Version 3 118 (HTTP/3)", Work in Progress, Internet-Draft, draft-ietf- 119 quic-http-34, 2 February 2021, 120 . 123 [ORIGIN] Nottingham, M. and E. Nygren, "The ORIGIN HTTP/2 Frame", 124 RFC 8336, DOI 10.17487/RFC8336, March 2018, 125 . 127 6.2. Informative References 129 [RFC6454] Barth, A., "The Web Origin Concept", RFC 6454, 130 DOI 10.17487/RFC6454, December 2011, 131 . 133 Author's Address 135 Mike Bishop 136 Akamai 138 Email: mbishop@evequefou.be