idnits 2.17.1 draft-schinazi-quic-h3-datagram-01.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 (October 21, 2019) is 1642 days in the past. Is this intentional? Checking references for intended status: Experimental ---------------------------------------------------------------------------- == 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-03 Summary: 0 errors (**), 0 flaws (~~), 4 warnings (==), 1 comment (--). 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 October 21, 2019 5 Expires: April 23, 2020 7 Using QUIC Datagrams with HTTP/3 8 draft-schinazi-quic-h3-datagram-01 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 Status of This Memo 22 This Internet-Draft is submitted in full conformance with the 23 provisions of BCP 78 and BCP 79. 25 Internet-Drafts are working documents of the Internet Engineering 26 Task Force (IETF). Note that other groups may also distribute 27 working documents as Internet-Drafts. The list of current Internet- 28 Drafts is at https://datatracker.ietf.org/drafts/current/. 30 Internet-Drafts are draft documents valid for a maximum of six months 31 and may be updated, replaced, or obsoleted by other documents at any 32 time. It is inappropriate to use Internet-Drafts as reference 33 material or to cite them other than as "work in progress." 35 This Internet-Draft will expire on April 23, 2020. 37 Copyright Notice 39 Copyright (c) 2019 IETF Trust and the persons identified as the 40 document authors. All rights reserved. 42 This document is subject to BCP 78 and the IETF Trust's Legal 43 Provisions Relating to IETF Documents 44 (https://trustee.ietf.org/license-info) in effect on the date of 45 publication of this document. Please review these documents 46 carefully, as they describe your rights and restrictions with respect 47 to this document. Code Components extracted from this document must 48 include Simplified BSD License text as described in Section 4.e of 49 the Trust Legal Provisions and are provided without warranty as 50 described in the Simplified BSD License. 52 Table of Contents 54 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 55 1.1. Conventions and Definitions . . . . . . . . . . . . . . . 2 56 2. HTTP/3 DATAGRAM Frame Format . . . . . . . . . . . . . . . . 2 57 2.1. Flow Identifiers . . . . . . . . . . . . . . . . . . . . 3 58 3. Flow Identifier Allocation . . . . . . . . . . . . . . . . . 3 59 4. Security Considerations . . . . . . . . . . . . . . . . . . . 3 60 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 4 61 6. Normative References . . . . . . . . . . . . . . . . . . . . 4 62 Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . . . 4 63 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 4 65 1. Introduction 67 The QUIC DATAGRAM extension [I-D.pauly-quic-datagram] provides 68 application protocols running over QUIC [I-D.ietf-quic-transport] 69 with a mechanism to send unreliable data while leveraging the 70 security and congestion-control properties of QUIC. However, QUIC 71 DATAGRAM frames do not provide a means to demultiplex application 72 contexts. This document defines how to use QUIC DATAGRAM frames when 73 the application protocol running over QUIC is HTTP/3 74 [I-D.ietf-quic-http] by adding an identifier at the start of the 75 frame payload. 77 This design mimics the use of Stream Types in HTTP/3, which provide a 78 demultiplexing identifier at the start of each unidirectional stream. 80 1.1. Conventions and Definitions 82 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 83 "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and 84 "OPTIONAL" in this document are to be interpreted as described in BCP 85 14 [RFC2119] [RFC8174] when, and only when, they appear in all 86 capitals, as shown here. 88 2. HTTP/3 DATAGRAM Frame Format 90 When used with HTTP/3, the Datagram Data field of QUIC DATAGRAM 91 frames uses the following format: 93 0 1 2 3 94 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 95 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 96 | Flow Identifier (i) ... 97 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 98 | HTTP/3 Datagram Payload (*) ... 99 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 101 Figure 1: HTTP/3 DATAGRAM Frame Format 103 Flow Identifier: A variable-length integer indicating the Flow 104 Identifier of the datagram (see Section 2.1). 106 HTTP/3 Datagram Payload: The payload of the datagram, whose 107 semantics are defined by individual applications. 109 2.1. Flow Identifiers 111 Flow identifiers represent bidirectional flows of datagrams within a 112 single QUIC connection. These are effectively equivalent to UDP 113 ports and allow basic demultiplexing of application data. The 114 primary role of flow identifiers is to provide a standard mechanism 115 for demultiplexing application data flows, which may be destined for 116 different processing threads in the application, akin to UDP sockets. 118 Beyond this, a sender SHOULD ensure that DATAGRAM frames within a 119 single flow are transmitted in order relative to one another. If 120 multiple DATAGRAM frames can be packed into a single QUIC packet, the 121 sender SHOULD group them by flow identifier to promote fate-sharing 122 within a specific flow and improve the ability to process batches of 123 datagram messages efficiently on the receiver. 125 3. Flow Identifier Allocation 127 Implementations of HTTP/3 that support the DATAGRAM extension will 128 provide a flow identifier allocation service. That service will 129 allow applications co-located with HTTP/3 to request a unique flow 130 identifier that they can subsequently use for their own purposes. 131 The HTTP/3 implementation will then parse the flow identifier of 132 incoming DATAGRAM frames and use it to deliver the frame to the 133 appropriate application. 135 4. Security Considerations 137 This document currently does not have additional security 138 considerations beyond those defined in [I-D.ietf-quic-transport] and 139 [I-D.pauly-quic-datagram]. 141 5. IANA Considerations 143 This document has no IANA actions. 145 6. Normative References 147 [I-D.ietf-quic-http] 148 Bishop, M., "Hypertext Transfer Protocol Version 3 149 (HTTP/3)", draft-ietf-quic-http-23 (work in progress), 150 September 2019. 152 [I-D.ietf-quic-transport] 153 Iyengar, J. and M. Thomson, "QUIC: A UDP-Based Multiplexed 154 and Secure Transport", draft-ietf-quic-transport-23 (work 155 in progress), September 2019. 157 [I-D.pauly-quic-datagram] 158 Pauly, T., Kinnear, E., and D. Schinazi, "An Unreliable 159 Datagram Extension to QUIC", draft-pauly-quic-datagram-03 160 (work in progress), July 2019. 162 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 163 Requirement Levels", BCP 14, RFC 2119, 164 DOI 10.17487/RFC2119, March 1997, 165 . 167 [RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC 168 2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174, 169 May 2017, . 171 Acknowledgments 173 The DATAGRAM frame identifier was previously part of the DATAGRAM 174 frame definition itself, the author would like to acknowledge the 175 authors of that document and the members of the IETF QUIC working 176 group for their suggestions. 178 Author's Address 180 David Schinazi 181 Google LLC 182 1600 Amphitheatre Parkway 183 Mountain View, California 94043 184 United States of America 186 Email: dschinazi.ietf@gmail.com