idnits 2.17.1 draft-schinazi-quic-h3-datagram-03.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 : ---------------------------------------------------------------------------- ** The abstract seems to contain references ([2], [1]), which it shouldn't. Please replace those with straight textual mentions of the documents in question. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year -- The document date (March 12, 2020) is 1499 days in the past. Is this intentional? Checking references for intended status: Experimental ---------------------------------------------------------------------------- -- Looks like a reference, but probably isn't: '1' on line 190 -- Looks like a reference, but probably isn't: '2' on line 192 -- Looks like a reference, but probably isn't: '3' on line 194 -- Looks like a reference, but probably isn't: '4' on line 196 == Outdated reference: A later version (-10) exists of draft-ietf-quic-datagram-00 == Outdated reference: A later version (-34) exists of draft-ietf-quic-http-27 == Outdated reference: A later version (-34) exists of draft-ietf-quic-transport-27 Summary: 1 error (**), 0 flaws (~~), 4 warnings (==), 5 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Network Working Group D. Schinazi 3 Internet-Draft Google LLC 4 Intended status: Experimental March 12, 2020 5 Expires: September 13, 2020 7 Using QUIC Datagrams with HTTP/3 8 draft-schinazi-quic-h3-datagram-03 10 Abstract 12 The QUIC DATAGRAM extension provides application protocols running 13 over QUIC with a mechanism to send unreliable data while leveraging 14 the security and congestion-control properties of QUIC. However, 15 QUIC DATAGRAM frames do not provide a means to demultiplex 16 application contexts. This document defines how to use QUIC DATAGRAM 17 frames when the application protocol running over QUIC is HTTP/3 by 18 adding an identifier at the start of the frame payload. 20 Discussion of this work is encouraged to happen on the QUIC IETF 21 mailing list quic@ietf.org [1] or on the GitHub repository which 22 contains the draft: https://github.com/DavidSchinazi/draft- 23 h3-datagram [2]. 25 Status of This Memo 27 This Internet-Draft is submitted in full conformance with the 28 provisions of BCP 78 and BCP 79. 30 Internet-Drafts are working documents of the Internet Engineering 31 Task Force (IETF). Note that other groups may also distribute 32 working documents as Internet-Drafts. The list of current Internet- 33 Drafts is at https://datatracker.ietf.org/drafts/current/. 35 Internet-Drafts are draft documents valid for a maximum of six months 36 and may be updated, replaced, or obsoleted by other documents at any 37 time. It is inappropriate to use Internet-Drafts as reference 38 material or to cite them other than as "work in progress." 40 This Internet-Draft will expire on September 13, 2020. 42 Copyright Notice 44 Copyright (c) 2020 IETF Trust and the persons identified as the 45 document authors. All rights reserved. 47 This document is subject to BCP 78 and the IETF Trust's Legal 48 Provisions Relating to IETF Documents 49 (https://trustee.ietf.org/license-info) in effect on the date of 50 publication of this document. Please review these documents 51 carefully, as they describe your rights and restrictions with respect 52 to this document. Code Components extracted from this document must 53 include Simplified BSD License text as described in Section 4.e of 54 the Trust Legal Provisions and are provided without warranty as 55 described in the Simplified BSD License. 57 Table of Contents 59 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 60 1.1. Conventions and Definitions . . . . . . . . . . . . . . . 2 61 2. HTTP/3 DATAGRAM Frame Format . . . . . . . . . . . . . . . . 3 62 2.1. Flow Identifiers . . . . . . . . . . . . . . . . . . . . 3 63 3. Flow Identifier Allocation . . . . . . . . . . . . . . . . . 3 64 4. Security Considerations . . . . . . . . . . . . . . . . . . . 4 65 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 4 66 6. References . . . . . . . . . . . . . . . . . . . . . . . . . 4 67 6.1. Normative References . . . . . . . . . . . . . . . . . . 4 68 6.2. URIs . . . . . . . . . . . . . . . . . . . . . . . . . . 5 69 Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . . . 5 70 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 5 72 1. Introduction 74 The QUIC DATAGRAM extension [DGRAM] provides application protocols 75 running over QUIC [QUIC] with a mechanism to send unreliable data 76 while leveraging the security and congestion-control properties of 77 QUIC. However, QUIC DATAGRAM frames do not provide a means to 78 demultiplex application contexts. This document defines how to use 79 QUIC DATAGRAM frames when the application protocol running over QUIC 80 is HTTP/3 [H3] by adding an identifier at the start of the frame 81 payload. 83 This design mimics the use of Stream Types in HTTP/3, which provide a 84 demultiplexing identifier at the start of each unidirectional stream. 86 Discussion of this work is encouraged to happen on the QUIC IETF 87 mailing list quic@ietf.org [3] or on the GitHub repository which 88 contains the draft: https://github.com/DavidSchinazi/draft- 89 h3-datagram [4]. 91 1.1. Conventions and Definitions 93 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 94 "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and 95 "OPTIONAL" in this document are to be interpreted as described in BCP 96 14 [RFC2119] [RFC8174] when, and only when, they appear in all 97 capitals, as shown here. 99 2. HTTP/3 DATAGRAM Frame Format 101 When used with HTTP/3, the Datagram Data field of QUIC DATAGRAM 102 frames uses the following format: 104 0 1 2 3 105 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 106 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 107 | Flow Identifier (i) ... 108 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 109 | HTTP/3 Datagram Payload (*) ... 110 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 112 Figure 1: HTTP/3 DATAGRAM Frame Format 114 Flow Identifier: A variable-length integer indicating the Flow 115 Identifier of the datagram (see Section 2.1). 117 HTTP/3 Datagram Payload: The payload of the datagram, whose 118 semantics are defined by individual applications. 120 2.1. Flow Identifiers 122 Flow identifiers represent bidirectional flows of datagrams within a 123 single QUIC connection. These are conceptually similar to UDP ports 124 and allow basic demultiplexing of application data. The primary role 125 of flow identifiers is to provide a standard mechanism for 126 demultiplexing application data flows, which may be destined for 127 different processing threads in the application, akin to UDP sockets. 129 Beyond this, a sender SHOULD ensure that DATAGRAM frames within a 130 single flow are transmitted in order relative to one another. If 131 multiple DATAGRAM frames can be packed into a single QUIC packet, the 132 sender SHOULD group them by flow identifier to promote fate-sharing 133 within a specific flow and improve the ability to process batches of 134 datagram messages efficiently on the receiver. 136 3. Flow Identifier Allocation 138 Implementations of HTTP/3 that support the DATAGRAM extension MUST 139 provide a flow identifier allocation service. That service will 140 allow applications co-located with HTTP/3 to request a unique flow 141 identifier that they can subsequently use for their own purposes. 142 The HTTP/3 implementation will then parse the flow identifier of 143 incoming DATAGRAM frames and use it to deliver the frame to the 144 appropriate application. 146 Even flow identifiers are client-initiated, while odd flow 147 identifiers are server-initiated. This means that an HTTP/3 client 148 implementation of the flow identifier allocation service MUST only 149 provide even identifiers, while a server implementation MUST only 150 provide odd identifiers. Note that, once allocated, any flow 151 identifier can be used by both client and server - only allocation 152 carries separate namespaces to avoid requiring synchronization. 154 4. Security Considerations 156 This document currently does not have additional security 157 considerations beyond those defined in [QUIC] and [DGRAM]. 159 5. IANA Considerations 161 This document has no IANA actions. 163 6. References 165 6.1. Normative References 167 [DGRAM] Pauly, T., Kinnear, E., and D. Schinazi, "An Unreliable 168 Datagram Extension to QUIC", draft-ietf-quic-datagram-00 169 (work in progress), February 2020. 171 [H3] Bishop, M., "Hypertext Transfer Protocol Version 3 172 (HTTP/3)", draft-ietf-quic-http-27 (work in progress), 173 February 2020. 175 [QUIC] Iyengar, J. and M. Thomson, "QUIC: A UDP-Based Multiplexed 176 and Secure Transport", draft-ietf-quic-transport-27 (work 177 in progress), February 2020. 179 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 180 Requirement Levels", BCP 14, RFC 2119, 181 DOI 10.17487/RFC2119, March 1997, 182 . 184 [RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC 185 2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174, 186 May 2017, . 188 6.2. URIs 190 [1] mailto:quic@ietf.org 192 [2] https://github.com/DavidSchinazi/draft-h3-datagram 194 [3] mailto:quic@ietf.org 196 [4] https://github.com/DavidSchinazi/draft-h3-datagram 198 Acknowledgments 200 The DATAGRAM frame identifier was previously part of the DATAGRAM 201 frame definition itself, the author would like to acknowledge the 202 authors of that document and the members of the IETF QUIC working 203 group for their suggestions. 205 Author's Address 207 David Schinazi 208 Google LLC 209 1600 Amphitheatre Parkway 210 Mountain View, California 94043 211 United States of America 213 Email: dschinazi.ietf@gmail.com