idnits 2.17.1 draft-schinazi-quic-h3-datagram-02.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 (November 04, 2019) is 1632 days in the past. Is this intentional? Checking references for intended status: Experimental ---------------------------------------------------------------------------- -- Looks like a reference, but probably isn't: '1' on line 194 -- Looks like a reference, but probably isn't: '2' on line 196 -- Looks like a reference, but probably isn't: '3' on line 198 -- Looks like a reference, but probably isn't: '4' on line 200 == Outdated reference: A later version (-34) exists of draft-ietf-quic-http-23 == Outdated reference: A later version (-34) exists of draft-ietf-quic-transport-23 == Outdated reference: A later version (-05) exists of draft-pauly-quic-datagram-04 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 November 04, 2019 5 Expires: May 7, 2020 7 Using QUIC Datagrams with HTTP/3 8 draft-schinazi-quic-h3-datagram-02 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 May 7, 2020. 42 Copyright Notice 44 Copyright (c) 2019 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 [I-D.pauly-quic-datagram] provides 75 application protocols running over QUIC [I-D.ietf-quic-transport] 76 with a mechanism to send unreliable data while leveraging the 77 security and congestion-control properties of QUIC. However, QUIC 78 DATAGRAM frames do not provide a means to demultiplex application 79 contexts. This document defines how to use QUIC DATAGRAM frames when 80 the application protocol running over QUIC is HTTP/3 81 [I-D.ietf-quic-http] by adding an identifier at the start of the 82 frame payload. 84 This design mimics the use of Stream Types in HTTP/3, which provide a 85 demultiplexing identifier at the start of each unidirectional stream. 87 Discussion of this work is encouraged to happen on the QUIC IETF 88 mailing list quic@ietf.org [3] or on the GitHub repository which 89 contains the draft: https://github.com/DavidSchinazi/draft- 90 h3-datagram [4]. 92 1.1. Conventions and Definitions 94 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 95 "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and 96 "OPTIONAL" in this document are to be interpreted as described in BCP 97 14 [RFC2119] [RFC8174] when, and only when, they appear in all 98 capitals, as shown here. 100 2. HTTP/3 DATAGRAM Frame Format 102 When used with HTTP/3, the Datagram Data field of QUIC DATAGRAM 103 frames uses the following format: 105 0 1 2 3 106 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 107 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 108 | Flow Identifier (i) ... 109 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 110 | HTTP/3 Datagram Payload (*) ... 111 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 113 Figure 1: HTTP/3 DATAGRAM Frame Format 115 Flow Identifier: A variable-length integer indicating the Flow 116 Identifier of the datagram (see Section 2.1). 118 HTTP/3 Datagram Payload: The payload of the datagram, whose 119 semantics are defined by individual applications. 121 2.1. Flow Identifiers 123 Flow identifiers represent bidirectional flows of datagrams within a 124 single QUIC connection. These are conceptually similar to UDP ports 125 and allow basic demultiplexing of application data. The primary role 126 of flow identifiers is to provide a standard mechanism for 127 demultiplexing application data flows, which may be destined for 128 different processing threads in the application, akin to UDP sockets. 130 Beyond this, a sender SHOULD ensure that DATAGRAM frames within a 131 single flow are transmitted in order relative to one another. If 132 multiple DATAGRAM frames can be packed into a single QUIC packet, the 133 sender SHOULD group them by flow identifier to promote fate-sharing 134 within a specific flow and improve the ability to process batches of 135 datagram messages efficiently on the receiver. 137 3. Flow Identifier Allocation 139 Implementations of HTTP/3 that support the DATAGRAM extension will 140 provide a flow identifier allocation service. That service will 141 allow applications co-located with HTTP/3 to request a unique flow 142 identifier that they can subsequently use for their own purposes. 143 The HTTP/3 implementation will then parse the flow identifier of 144 incoming DATAGRAM frames and use it to deliver the frame to the 145 appropriate application. 147 The flow identifier allocation services on both endpoints in a 148 connection will need to coordinate to agree on the meaning of each 149 flow identifier. This will require signalling, which is currently 150 work in progress. This signalling mechanism will also need a way to 151 flow control the amount of flow identifiers generated by a given 152 endpoint. 154 4. Security Considerations 156 This document currently does not have additional security 157 considerations beyond those defined in [I-D.ietf-quic-transport] and 158 [I-D.pauly-quic-datagram]. 160 5. IANA Considerations 162 This document has no IANA actions. 164 6. References 166 6.1. Normative References 168 [I-D.ietf-quic-http] 169 Bishop, M., "Hypertext Transfer Protocol Version 3 170 (HTTP/3)", draft-ietf-quic-http-23 (work in progress), 171 September 2019. 173 [I-D.ietf-quic-transport] 174 Iyengar, J. and M. Thomson, "QUIC: A UDP-Based Multiplexed 175 and Secure Transport", draft-ietf-quic-transport-23 (work 176 in progress), September 2019. 178 [I-D.pauly-quic-datagram] 179 Pauly, T., Kinnear, E., and D. Schinazi, "An Unreliable 180 Datagram Extension to QUIC", draft-pauly-quic-datagram-04 181 (work in progress), October 2019. 183 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 184 Requirement Levels", BCP 14, RFC 2119, 185 DOI 10.17487/RFC2119, March 1997, 186 . 188 [RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC 189 2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174, 190 May 2017, . 192 6.2. URIs 194 [1] mailto:quic@ietf.org 196 [2] https://github.com/DavidSchinazi/draft-h3-datagram 198 [3] mailto:quic@ietf.org 200 [4] https://github.com/DavidSchinazi/draft-h3-datagram 202 Acknowledgments 204 The DATAGRAM frame identifier was previously part of the DATAGRAM 205 frame definition itself, the author would like to acknowledge the 206 authors of that document and the members of the IETF QUIC working 207 group for their suggestions. 209 Author's Address 211 David Schinazi 212 Google LLC 213 1600 Amphitheatre Parkway 214 Mountain View, California 94043 215 United States of America 217 Email: dschinazi.ietf@gmail.com