draft-ietf-quic-http-31.txt   draft-ietf-quic-http-32.txt 
QUIC M. Bishop, Ed. QUIC M. Bishop, Ed.
Internet-Draft Akamai Internet-Draft Akamai
Intended status: Standards Track 25 September 2020 Intended status: Standards Track 20 October 2020
Expires: 29 March 2021 Expires: 23 April 2021
Hypertext Transfer Protocol Version 3 (HTTP/3) Hypertext Transfer Protocol Version 3 (HTTP/3)
draft-ietf-quic-http-31 draft-ietf-quic-http-32
Abstract Abstract
The QUIC transport protocol has several features that are desirable The QUIC transport protocol has several features that are desirable
in a transport for HTTP, such as stream multiplexing, per-stream flow in a transport for HTTP, such as stream multiplexing, per-stream flow
control, and low-latency connection establishment. This document control, and low-latency connection establishment. This document
describes a mapping of HTTP semantics over QUIC. This document also describes a mapping of HTTP semantics over QUIC. This document also
identifies HTTP/2 features that are subsumed by QUIC, and describes identifies HTTP/2 features that are subsumed by QUIC, and describes
how HTTP/2 extensions can be ported to HTTP/3. how HTTP/2 extensions can be ported to HTTP/3.
skipping to change at page 1, line 45 skipping to change at page 1, line 45
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at https://datatracker.ietf.org/drafts/current/. Drafts is at https://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
This Internet-Draft will expire on 29 March 2021. This Internet-Draft will expire on 23 April 2021.
Copyright Notice Copyright Notice
Copyright (c) 2020 IETF Trust and the persons identified as the Copyright (c) 2020 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents (https://trustee.ietf.org/ Provisions Relating to IETF Documents (https://trustee.ietf.org/
license-info) in effect on the date of publication of this document. license-info) in effect on the date of publication of this document.
Please review these documents carefully, as they describe your rights Please review these documents carefully, as they describe your rights
skipping to change at page 2, line 30 skipping to change at page 2, line 30
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 4 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 4
1.1. Prior versions of HTTP . . . . . . . . . . . . . . . . . 5 1.1. Prior versions of HTTP . . . . . . . . . . . . . . . . . 5
1.2. Delegation to QUIC . . . . . . . . . . . . . . . . . . . 5 1.2. Delegation to QUIC . . . . . . . . . . . . . . . . . . . 5
2. HTTP/3 Protocol Overview . . . . . . . . . . . . . . . . . . 5 2. HTTP/3 Protocol Overview . . . . . . . . . . . . . . . . . . 5
2.1. Document Organization . . . . . . . . . . . . . . . . . . 6 2.1. Document Organization . . . . . . . . . . . . . . . . . . 6
2.2. Conventions and Terminology . . . . . . . . . . . . . . . 7 2.2. Conventions and Terminology . . . . . . . . . . . . . . . 7
3. Connection Setup and Management . . . . . . . . . . . . . . . 8 3. Connection Setup and Management . . . . . . . . . . . . . . . 8
3.1. Draft Version Identification . . . . . . . . . . . . . . 8 3.1. Draft Version Identification . . . . . . . . . . . . . . 8
3.2. Discovering an HTTP/3 Endpoint . . . . . . . . . . . . . 9 3.2. Discovering an HTTP/3 Endpoint . . . . . . . . . . . . . 9
3.2.1. HTTP Alternative Services . . . . . . . . . . . . . . 9 3.2.1. HTTP Alternative Services . . . . . . . . . . . . . . 10
3.2.2. Other Schemes . . . . . . . . . . . . . . . . . . . . 10 3.2.2. Other Schemes . . . . . . . . . . . . . . . . . . . . 10
3.3. Connection Establishment . . . . . . . . . . . . . . . . 10 3.3. Connection Establishment . . . . . . . . . . . . . . . . 10
3.4. Connection Reuse . . . . . . . . . . . . . . . . . . . . 11 3.4. Connection Reuse . . . . . . . . . . . . . . . . . . . . 11
4. HTTP Request Lifecycle . . . . . . . . . . . . . . . . . . . 12 4. HTTP Request Lifecycle . . . . . . . . . . . . . . . . . . . 12
4.1. HTTP Message Exchanges . . . . . . . . . . . . . . . . . 12 4.1. HTTP Message Exchanges . . . . . . . . . . . . . . . . . 12
4.1.1. Field Formatting and Compression . . . . . . . . . . 14 4.1.1. Field Formatting and Compression . . . . . . . . . . 14
4.1.2. Request Cancellation and Rejection . . . . . . . . . 17 4.1.2. Request Cancellation and Rejection . . . . . . . . . 17
4.1.3. Malformed Requests and Responses . . . . . . . . . . 18 4.1.3. Malformed Requests and Responses . . . . . . . . . . 18
4.2. The CONNECT Method . . . . . . . . . . . . . . . . . . . 19 4.2. The CONNECT Method . . . . . . . . . . . . . . . . . . . 19
4.3. HTTP Upgrade . . . . . . . . . . . . . . . . . . . . . . 20 4.3. HTTP Upgrade . . . . . . . . . . . . . . . . . . . . . . 20
4.4. Server Push . . . . . . . . . . . . . . . . . . . . . . . 20 4.4. Server Push . . . . . . . . . . . . . . . . . . . . . . . 21
5. Connection Closure . . . . . . . . . . . . . . . . . . . . . 22 5. Connection Closure . . . . . . . . . . . . . . . . . . . . . 23
5.1. Idle Connections . . . . . . . . . . . . . . . . . . . . 22 5.1. Idle Connections . . . . . . . . . . . . . . . . . . . . 23
5.2. Connection Shutdown . . . . . . . . . . . . . . . . . . . 23 5.2. Connection Shutdown . . . . . . . . . . . . . . . . . . . 23
5.3. Immediate Application Closure . . . . . . . . . . . . . . 25 5.3. Immediate Application Closure . . . . . . . . . . . . . . 25
5.4. Transport Closure . . . . . . . . . . . . . . . . . . . . 25 5.4. Transport Closure . . . . . . . . . . . . . . . . . . . . 26
6. Stream Mapping and Usage . . . . . . . . . . . . . . . . . . 25 6. Stream Mapping and Usage . . . . . . . . . . . . . . . . . . 26
6.1. Bidirectional Streams . . . . . . . . . . . . . . . . . . 26 6.1. Bidirectional Streams . . . . . . . . . . . . . . . . . . 26
6.2. Unidirectional Streams . . . . . . . . . . . . . . . . . 26 6.2. Unidirectional Streams . . . . . . . . . . . . . . . . . 27
6.2.1. Control Streams . . . . . . . . . . . . . . . . . . . 28 6.2.1. Control Streams . . . . . . . . . . . . . . . . . . . 28
6.2.2. Push Streams . . . . . . . . . . . . . . . . . . . . 28 6.2.2. Push Streams . . . . . . . . . . . . . . . . . . . . 29
6.2.3. Reserved Stream Types . . . . . . . . . . . . . . . . 29 6.2.3. Reserved Stream Types . . . . . . . . . . . . . . . . 29
7. HTTP Framing Layer . . . . . . . . . . . . . . . . . . . . . 29 7. HTTP Framing Layer . . . . . . . . . . . . . . . . . . . . . 30
7.1. Frame Layout . . . . . . . . . . . . . . . . . . . . . . 30 7.1. Frame Layout . . . . . . . . . . . . . . . . . . . . . . 31
7.2. Frame Definitions . . . . . . . . . . . . . . . . . . . . 31 7.2. Frame Definitions . . . . . . . . . . . . . . . . . . . . 31
7.2.1. DATA . . . . . . . . . . . . . . . . . . . . . . . . 31 7.2.1. DATA . . . . . . . . . . . . . . . . . . . . . . . . 31
7.2.2. HEADERS . . . . . . . . . . . . . . . . . . . . . . . 31 7.2.2. HEADERS . . . . . . . . . . . . . . . . . . . . . . . 32
7.2.3. CANCEL_PUSH . . . . . . . . . . . . . . . . . . . . . 32 7.2.3. CANCEL_PUSH . . . . . . . . . . . . . . . . . . . . . 32
7.2.4. SETTINGS . . . . . . . . . . . . . . . . . . . . . . 33 7.2.4. SETTINGS . . . . . . . . . . . . . . . . . . . . . . 34
7.2.5. PUSH_PROMISE . . . . . . . . . . . . . . . . . . . . 36 7.2.5. PUSH_PROMISE . . . . . . . . . . . . . . . . . . . . 37
7.2.6. GOAWAY . . . . . . . . . . . . . . . . . . . . . . . 38 7.2.6. GOAWAY . . . . . . . . . . . . . . . . . . . . . . . 38
7.2.7. MAX_PUSH_ID . . . . . . . . . . . . . . . . . . . . . 38 7.2.7. MAX_PUSH_ID . . . . . . . . . . . . . . . . . . . . . 39
7.2.8. Reserved Frame Types . . . . . . . . . . . . . . . . 39 7.2.8. Reserved Frame Types . . . . . . . . . . . . . . . . 40
8. Error Handling . . . . . . . . . . . . . . . . . . . . . . . 39 8. Error Handling . . . . . . . . . . . . . . . . . . . . . . . 40
8.1. HTTP/3 Error Codes . . . . . . . . . . . . . . . . . . . 40 8.1. HTTP/3 Error Codes . . . . . . . . . . . . . . . . . . . 40
9. Extensions to HTTP/3 . . . . . . . . . . . . . . . . . . . . 41 9. Extensions to HTTP/3 . . . . . . . . . . . . . . . . . . . . 42
10. Security Considerations . . . . . . . . . . . . . . . . . . . 42 10. Security Considerations . . . . . . . . . . . . . . . . . . . 43
10.1. Server Authority . . . . . . . . . . . . . . . . . . . . 42 10.1. Server Authority . . . . . . . . . . . . . . . . . . . . 43
10.2. Cross-Protocol Attacks . . . . . . . . . . . . . . . . . 42 10.2. Cross-Protocol Attacks . . . . . . . . . . . . . . . . . 43
10.3. Intermediary Encapsulation Attacks . . . . . . . . . . . 43 10.3. Intermediary Encapsulation Attacks . . . . . . . . . . . 43
10.4. Cacheability of Pushed Responses . . . . . . . . . . . . 43 10.4. Cacheability of Pushed Responses . . . . . . . . . . . . 44
10.5. Denial-of-Service Considerations . . . . . . . . . . . . 43 10.5. Denial-of-Service Considerations . . . . . . . . . . . . 44
10.5.1. Limits on Field Section Size . . . . . . . . . . . . 44 10.5.1. Limits on Field Section Size . . . . . . . . . . . . 45
10.5.2. CONNECT Issues . . . . . . . . . . . . . . . . . . . 45 10.5.2. CONNECT Issues . . . . . . . . . . . . . . . . . . . 45
10.6. Use of Compression . . . . . . . . . . . . . . . . . . . 45 10.6. Use of Compression . . . . . . . . . . . . . . . . . . . 46
10.7. Padding and Traffic Analysis . . . . . . . . . . . . . . 46 10.7. Padding and Traffic Analysis . . . . . . . . . . . . . . 46
10.8. Frame Parsing . . . . . . . . . . . . . . . . . . . . . 46 10.8. Frame Parsing . . . . . . . . . . . . . . . . . . . . . 47
10.9. Early Data . . . . . . . . . . . . . . . . . . . . . . . 46 10.9. Early Data . . . . . . . . . . . . . . . . . . . . . . . 47
10.10. Migration . . . . . . . . . . . . . . . . . . . . . . . 47 10.10. Migration . . . . . . . . . . . . . . . . . . . . . . . 47
10.11. Privacy Considerations . . . . . . . . . . . . . . . . . 47 10.11. Privacy Considerations . . . . . . . . . . . . . . . . . 47
11. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 47 11. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 48
11.1. Registration of HTTP/3 Identification String . . . . . . 47 11.1. Registration of HTTP/3 Identification String . . . . . . 48
11.2. New Registries . . . . . . . . . . . . . . . . . . . . . 48 11.2. New Registries . . . . . . . . . . . . . . . . . . . . . 48
11.2.1. Frame Types . . . . . . . . . . . . . . . . . . . . 48 11.2.1. Frame Types . . . . . . . . . . . . . . . . . . . . 48
11.2.2. Settings Parameters . . . . . . . . . . . . . . . . 49 11.2.2. Settings Parameters . . . . . . . . . . . . . . . . 50
11.2.3. Error Codes . . . . . . . . . . . . . . . . . . . . 50 11.2.3. Error Codes . . . . . . . . . . . . . . . . . . . . 51
11.2.4. Stream Types . . . . . . . . . . . . . . . . . . . . 53 11.2.4. Stream Types . . . . . . . . . . . . . . . . . . . . 53
12. References . . . . . . . . . . . . . . . . . . . . . . . . . 53 12. References . . . . . . . . . . . . . . . . . . . . . . . . . 54
12.1. Normative References . . . . . . . . . . . . . . . . . . 53 12.1. Normative References . . . . . . . . . . . . . . . . . . 54
12.2. Informative References . . . . . . . . . . . . . . . . . 55 12.2. Informative References . . . . . . . . . . . . . . . . . 55
Appendix A. Considerations for Transitioning from HTTP/2 . . . . 56 Appendix A. Considerations for Transitioning from HTTP/2 . . . . 56
A.1. Streams . . . . . . . . . . . . . . . . . . . . . . . . . 56 A.1. Streams . . . . . . . . . . . . . . . . . . . . . . . . . 57
A.2. HTTP Frame Types . . . . . . . . . . . . . . . . . . . . 57 A.2. HTTP Frame Types . . . . . . . . . . . . . . . . . . . . 57
A.2.1. Prioritization Differences . . . . . . . . . . . . . 57 A.2.1. Prioritization Differences . . . . . . . . . . . . . 58
A.2.2. Field Compression Differences . . . . . . . . . . . . 58 A.2.2. Field Compression Differences . . . . . . . . . . . . 58
A.2.3. Flow Control Differences . . . . . . . . . . . . . . 58 A.2.3. Flow Control Differences . . . . . . . . . . . . . . 59
A.2.4. Guidance for New Frame Type Definitions . . . . . . . 58 A.2.4. Guidance for New Frame Type Definitions . . . . . . . 59
A.2.5. Mapping Between HTTP/2 and HTTP/3 Frame Types . . . . 59 A.2.5. Mapping Between HTTP/2 and HTTP/3 Frame Types . . . . 59
A.3. HTTP/2 SETTINGS Parameters . . . . . . . . . . . . . . . 60 A.3. HTTP/2 SETTINGS Parameters . . . . . . . . . . . . . . . 60
A.4. HTTP/2 Error Codes . . . . . . . . . . . . . . . . . . . 61 A.4. HTTP/2 Error Codes . . . . . . . . . . . . . . . . . . . 61
A.4.1. Mapping Between HTTP/2 and HTTP/3 Errors . . . . . . 62 A.4.1. Mapping Between HTTP/2 and HTTP/3 Errors . . . . . . 62
Appendix B. Change Log . . . . . . . . . . . . . . . . . . . . . 63 Appendix B. Change Log . . . . . . . . . . . . . . . . . . . . . 63
B.1. Since draft-ietf-quic-http-30 . . . . . . . . . . . . . . 63 B.1. Since draft-ietf-quic-http-31 . . . . . . . . . . . . . . 63
B.2. Since draft-ietf-quic-http-29 . . . . . . . . . . . . . . 63 B.2. Since draft-ietf-quic-http-30 . . . . . . . . . . . . . . 63
B.3. Since draft-ietf-quic-http-28 . . . . . . . . . . . . . . 63 B.3. Since draft-ietf-quic-http-29 . . . . . . . . . . . . . . 63
B.4. Since draft-ietf-quic-http-27 . . . . . . . . . . . . . . 63 B.4. Since draft-ietf-quic-http-28 . . . . . . . . . . . . . . 63
B.5. Since draft-ietf-quic-http-26 . . . . . . . . . . . . . . 63 B.5. Since draft-ietf-quic-http-27 . . . . . . . . . . . . . . 64
B.6. Since draft-ietf-quic-http-25 . . . . . . . . . . . . . . 63 B.6. Since draft-ietf-quic-http-26 . . . . . . . . . . . . . . 64
B.7. Since draft-ietf-quic-http-24 . . . . . . . . . . . . . . 64 B.7. Since draft-ietf-quic-http-25 . . . . . . . . . . . . . . 64
B.8. Since draft-ietf-quic-http-23 . . . . . . . . . . . . . . 64 B.8. Since draft-ietf-quic-http-24 . . . . . . . . . . . . . . 64
B.9. Since draft-ietf-quic-http-22 . . . . . . . . . . . . . . 64 B.9. Since draft-ietf-quic-http-23 . . . . . . . . . . . . . . 64
B.10. Since draft-ietf-quic-http-21 . . . . . . . . . . . . . . 65 B.10. Since draft-ietf-quic-http-22 . . . . . . . . . . . . . . 65
B.11. Since draft-ietf-quic-http-20 . . . . . . . . . . . . . . 65 B.11. Since draft-ietf-quic-http-21 . . . . . . . . . . . . . . 65
B.12. Since draft-ietf-quic-http-19 . . . . . . . . . . . . . . 66 B.12. Since draft-ietf-quic-http-20 . . . . . . . . . . . . . . 65
B.13. Since draft-ietf-quic-http-18 . . . . . . . . . . . . . . 66 B.13. Since draft-ietf-quic-http-19 . . . . . . . . . . . . . . 66
B.14. Since draft-ietf-quic-http-17 . . . . . . . . . . . . . . 66 B.14. Since draft-ietf-quic-http-18 . . . . . . . . . . . . . . 67
B.15. Since draft-ietf-quic-http-16 . . . . . . . . . . . . . . 67 B.15. Since draft-ietf-quic-http-17 . . . . . . . . . . . . . . 67
B.16. Since draft-ietf-quic-http-15 . . . . . . . . . . . . . . 67 B.16. Since draft-ietf-quic-http-16 . . . . . . . . . . . . . . 67
B.17. Since draft-ietf-quic-http-14 . . . . . . . . . . . . . . 67 B.17. Since draft-ietf-quic-http-15 . . . . . . . . . . . . . . 68
B.18. Since draft-ietf-quic-http-13 . . . . . . . . . . . . . . 67 B.18. Since draft-ietf-quic-http-14 . . . . . . . . . . . . . . 68
B.19. Since draft-ietf-quic-http-12 . . . . . . . . . . . . . . 68 B.19. Since draft-ietf-quic-http-13 . . . . . . . . . . . . . . 68
B.20. Since draft-ietf-quic-http-11 . . . . . . . . . . . . . . 68 B.20. Since draft-ietf-quic-http-12 . . . . . . . . . . . . . . 68
B.21. Since draft-ietf-quic-http-10 . . . . . . . . . . . . . . 68 B.21. Since draft-ietf-quic-http-11 . . . . . . . . . . . . . . 69
B.22. Since draft-ietf-quic-http-09 . . . . . . . . . . . . . . 68 B.22. Since draft-ietf-quic-http-10 . . . . . . . . . . . . . . 69
B.23. Since draft-ietf-quic-http-08 . . . . . . . . . . . . . . 69 B.23. Since draft-ietf-quic-http-09 . . . . . . . . . . . . . . 69
B.24. Since draft-ietf-quic-http-07 . . . . . . . . . . . . . . 69 B.24. Since draft-ietf-quic-http-08 . . . . . . . . . . . . . . 69
B.25. Since draft-ietf-quic-http-06 . . . . . . . . . . . . . . 69 B.25. Since draft-ietf-quic-http-07 . . . . . . . . . . . . . . 69
B.26. Since draft-ietf-quic-http-05 . . . . . . . . . . . . . . 69 B.26. Since draft-ietf-quic-http-06 . . . . . . . . . . . . . . 69
B.27. Since draft-ietf-quic-http-04 . . . . . . . . . . . . . . 69 B.27. Since draft-ietf-quic-http-05 . . . . . . . . . . . . . . 69
B.28. Since draft-ietf-quic-http-03 . . . . . . . . . . . . . . 69 B.28. Since draft-ietf-quic-http-04 . . . . . . . . . . . . . . 70
B.29. Since draft-ietf-quic-http-02 . . . . . . . . . . . . . . 70 B.29. Since draft-ietf-quic-http-03 . . . . . . . . . . . . . . 70
B.30. Since draft-ietf-quic-http-01 . . . . . . . . . . . . . . 70 B.30. Since draft-ietf-quic-http-02 . . . . . . . . . . . . . . 70
B.31. Since draft-ietf-quic-http-00 . . . . . . . . . . . . . . 70 B.31. Since draft-ietf-quic-http-01 . . . . . . . . . . . . . . 70
B.32. Since draft-shade-quic-http2-mapping-00 . . . . . . . . . 71 B.32. Since draft-ietf-quic-http-00 . . . . . . . . . . . . . . 71
B.33. Since draft-shade-quic-http2-mapping-00 . . . . . . . . . 71
Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . . 71 Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . . 71
Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 72 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 72
1. Introduction 1. Introduction
HTTP semantics ([SEMANTICS]) are used for a broad range of services HTTP semantics ([SEMANTICS]) are used for a broad range of services
on the Internet. These semantics have most commonly been used with on the Internet. These semantics have most commonly been used with
HTTP/1.1, over a variety of transport and session layers, and with HTTP/1.1, over a variety of transport and session layers, and with
HTTP/2 over TLS. HTTP/3 supports the same semantics over a new HTTP/2 over TLS. HTTP/3 supports the same semantics over a new
transport protocol, QUIC. transport protocol, QUIC.
skipping to change at page 5, line 28 skipping to change at page 5, line 28
because the parallel nature of HTTP/2's multiplexing is not visible because the parallel nature of HTTP/2's multiplexing is not visible
to TCP's loss recovery mechanisms, a lost or reordered packet causes to TCP's loss recovery mechanisms, a lost or reordered packet causes
all active transactions to experience a stall regardless of whether all active transactions to experience a stall regardless of whether
that transaction was directly impacted by the lost packet. that transaction was directly impacted by the lost packet.
1.2. Delegation to QUIC 1.2. Delegation to QUIC
The QUIC transport protocol incorporates stream multiplexing and per- The QUIC transport protocol incorporates stream multiplexing and per-
stream flow control, similar to that provided by the HTTP/2 framing stream flow control, similar to that provided by the HTTP/2 framing
layer. By providing reliability at the stream level and congestion layer. By providing reliability at the stream level and congestion
control across the entire connection, it has the capability to control across the entire connection, QUIC has the capability to
improve the performance of HTTP compared to a TCP mapping. QUIC also improve the performance of HTTP compared to a TCP mapping. QUIC also
incorporates TLS 1.3 ([TLS13]) at the transport layer, offering incorporates TLS 1.3 ([TLS13]) at the transport layer, offering
comparable security to running TLS over TCP, with the improved comparable security to running TLS over TCP, with the improved
connection setup latency of TCP Fast Open ([TFO]). connection setup latency of TCP Fast Open ([TFO]).
This document defines a mapping of HTTP semantics over the QUIC This document defines a mapping of HTTP semantics over the QUIC
transport protocol, drawing heavily on the design of HTTP/2. While transport protocol, drawing heavily on the design of HTTP/2. While
delegating stream lifetime and flow control issues to QUIC, a similar delegating stream lifetime and flow control issues to QUIC, a similar
binary framing is used on each stream. Some HTTP/2 features are binary framing is used on each stream. Some HTTP/2 features are
subsumed by QUIC, while other features are implemented atop QUIC. subsumed by QUIC, while other features are implemented atop QUIC.
skipping to change at page 6, line 33 skipping to change at page 6, line 33
As in HTTP/2, request and response fields are compressed for As in HTTP/2, request and response fields are compressed for
transmission. Because HPACK ([HPACK]) relies on in-order transmission. Because HPACK ([HPACK]) relies on in-order
transmission of compressed field sections (a guarantee not provided transmission of compressed field sections (a guarantee not provided
by QUIC), HTTP/3 replaces HPACK with QPACK ([QPACK]). QPACK uses by QUIC), HTTP/3 replaces HPACK with QPACK ([QPACK]). QPACK uses
separate unidirectional streams to modify and track field table separate unidirectional streams to modify and track field table
state, while encoded field sections refer to the state of the table state, while encoded field sections refer to the state of the table
without modifying it. without modifying it.
2.1. Document Organization 2.1. Document Organization
The following sections provide a detailed overview of the connection The following sections provide a detailed overview of the lifecycle
lifecycle and key concepts: of an HTTP/3 connection:
* Connection Setup and Management (Section 3) covers how an HTTP/3 * Connection Setup and Management (Section 3) covers how an HTTP/3
endpoint is discovered and a connection is established. endpoint is discovered and an HTTP/3 connection is established.
* HTTP Request Lifecycle (Section 4) describes how HTTP semantics * HTTP Request Lifecycle (Section 4) describes how HTTP semantics
are expressed using frames. are expressed using frames.
* Connection Closure (Section 5) describes how connections are * Connection Closure (Section 5) describes how HTTP/3 connections
terminated, either gracefully or abruptly. are terminated, either gracefully or abruptly.
The details of the wire protocol and interactions with the transport The details of the wire protocol and interactions with the transport
are described in subsequent sections: are described in subsequent sections:
* Stream Mapping and Usage (Section 6) describes the way QUIC * Stream Mapping and Usage (Section 6) describes the way QUIC
streams are used. streams are used.
* HTTP Framing Layer (Section 7) describes the frames used on most * HTTP Framing Layer (Section 7) describes the frames used on most
streams. streams.
skipping to change at page 8, line 5 skipping to change at page 8, line 5
frame: The smallest unit of communication on a stream in HTTP/3, frame: The smallest unit of communication on a stream in HTTP/3,
consisting of a header and a variable-length sequence of bytes consisting of a header and a variable-length sequence of bytes
structured according to the frame type. Protocol elements called structured according to the frame type. Protocol elements called
"frames" exist in both this document and [QUIC-TRANSPORT]. Where "frames" exist in both this document and [QUIC-TRANSPORT]. Where
frames from [QUIC-TRANSPORT] are referenced, the frame name will frames from [QUIC-TRANSPORT] are referenced, the frame name will
be prefaced with "QUIC." For example, "QUIC CONNECTION_CLOSE be prefaced with "QUIC." For example, "QUIC CONNECTION_CLOSE
frames." References without this preface refer to frames defined frames." References without this preface refer to frames defined
in Section 7.2. in Section 7.2.
HTTP/3 connection: A QUIC connection where the negotiated
application protocol is HTTP/3.
peer: An endpoint. When discussing a particular endpoint, "peer" peer: An endpoint. When discussing a particular endpoint, "peer"
refers to the endpoint that is remote to the primary subject of refers to the endpoint that is remote to the primary subject of
discussion. discussion.
receiver: An endpoint that is receiving frames. receiver: An endpoint that is receiving frames.
sender: An endpoint that is transmitting frames. sender: An endpoint that is transmitting frames.
server: The endpoint that accepts an HTTP/3 connection. Servers server: The endpoint that accepts an HTTP/3 connection. Servers
receive HTTP requests and send HTTP responses. receive HTTP requests and send HTTP responses.
stream: A bidirectional or unidirectional bytestream provided by the stream: A bidirectional or unidirectional bytestream provided by the
QUIC transport. QUIC transport.
stream error: An error on the individual HTTP/3 stream. stream error: An error on the individual HTTP/3 stream.
The term "payload body" is defined in Section 7.3.3 of [SEMANTICS]. The term "payload body" is defined in Section 5.5.4 of [SEMANTICS].
Finally, the terms "gateway", "intermediary", "proxy", and "tunnel" Finally, the terms "gateway", "intermediary", "proxy", and "tunnel"
are defined in Section 2.2 of [SEMANTICS]. Intermediaries act as are defined in Section 3.7 of [SEMANTICS]. Intermediaries act as
both client and server at different times. both client and server at different times.
Packet diagrams in this document use the format defined in Packet diagrams in this document use the format defined in
Section 1.3 of [QUIC-TRANSPORT] to illustrate the order and size of Section 1.3 of [QUIC-TRANSPORT] to illustrate the order and size of
fields. fields.
3. Connection Setup and Management 3. Connection Setup and Management
3.1. Draft Version Identification 3.1. Draft Version Identification
skipping to change at page 9, line 10 skipping to change at page 9, line 15
Draft versions MUST use the corresponding draft transport version as Draft versions MUST use the corresponding draft transport version as
their transport. For example, the application protocol defined in their transport. For example, the application protocol defined in
draft-ietf-quic-http-25 uses the transport defined in draft-ietf- draft-ietf-quic-http-25 uses the transport defined in draft-ietf-
quic-transport-25. quic-transport-25.
Non-compatible experiments that are based on these draft versions Non-compatible experiments that are based on these draft versions
MUST append the string "-" and an experiment name to the identifier. MUST append the string "-" and an experiment name to the identifier.
For example, an experimental implementation based on draft-ietf-quic- For example, an experimental implementation based on draft-ietf-quic-
http-09 that reserves an extra stream for unsolicited transmission of http-09 that reserves an extra stream for unsolicited transmission of
1980s pop music might identify itself as "h3-09-rickroll". Note that 1980s pop music might identify itself as "h3-09-rickroll". Note that
any label MUST conform to the "token" syntax defined in any label MUST conform to the "token" syntax defined in Section 5.7.2
Section 5.4.1.1 of [SEMANTICS]. Experimenters are encouraged to of [SEMANTICS]. Experimenters are encouraged to coordinate their
coordinate their experiments on the quic@ietf.org mailing list. experiments on the quic@ietf.org mailing list.
3.2. Discovering an HTTP/3 Endpoint 3.2. Discovering an HTTP/3 Endpoint
HTTP relies on the notion of an authoritative response: a response HTTP relies on the notion of an authoritative response: a response
that has been determined to be the most appropriate response for that that has been determined to be the most appropriate response for that
request given the state of the target resource at the time of request given the state of the target resource at the time of
response message origination by (or at the direction of) the origin response message origination by (or at the direction of) the origin
server identified within the target URI. Locating an authoritative server identified within the target URI. Locating an authoritative
server for an HTTP URL is discussed in Section 6.4 of [SEMANTICS]. server for an HTTP URL is discussed in Section 4.3 of [SEMANTICS].
The "https" scheme associates authority with possession of a The "https" scheme associates authority with possession of a
certificate that the client considers to be trustworthy for the host certificate that the client considers to be trustworthy for the host
identified by the authority component of the URL. If a server identified by the authority component of the URL. If a server
presents a certificate and proof that it controls the corresponding presents a certificate and proof that it controls the corresponding
private key, then a client will accept a secured connection to that private key, then a client will accept a secured TLS session with
server as being authoritative for all origins with the "https" scheme that server as being authoritative for all origins with the "https"
and a host identified in the certificate. scheme and a host identified in the certificate.
A client MAY attempt access to a resource with an "https" URI by A client MAY attempt access to a resource with an "https" URI by
resolving the host identifier to an IP address, establishing a QUIC resolving the host identifier to an IP address, establishing a QUIC
connection to that address on the indicated port, and sending an connection to that address on the indicated port, and sending an
HTTP/3 request message targeting the URI to the server over that HTTP/3 request message targeting the URI to the server over that
secured connection. secured connection. Unless some other mechanism is used to select
HTTP/3, the token "h3" is used in the Application Layer Protocol
Negotiation (ALPN; see [RFC7301]) extension during the TLS handshake.
Connectivity problems (e.g., blocking UDP) can result in QUIC Connectivity problems (e.g., blocking UDP) can result in QUIC
connection establishment failure; clients SHOULD attempt to use TCP- connection establishment failure; clients SHOULD attempt to use TCP-
based versions of HTTP in this case. based versions of HTTP in this case.
Servers MAY serve HTTP/3 on any UDP port; an alternative service Servers MAY serve HTTP/3 on any UDP port; an alternative service
advertisement always includes an explicit port, and URLs contain advertisement always includes an explicit port, and URLs contain
either an explicit port or a default port associated with the scheme. either an explicit port or a default port associated with the scheme.
3.2.1. HTTP Alternative Services 3.2.1. HTTP Alternative Services
An HTTP origin advertises the availability of an equivalent HTTP/3 An HTTP origin advertises the availability of an equivalent HTTP/3
endpoint via the Alt-Svc HTTP response header field or the HTTP/2 endpoint via the Alt-Svc HTTP response header field or the HTTP/2
ALTSVC frame ([ALTSVC]), using the Application Layer Protocol ALTSVC frame ([ALTSVC]), using the "h3" ALPN token.
Negotiation (ALPN; see [RFC7301]) token defined in Section 3.3.
For example, an origin could indicate in an HTTP response that HTTP/3 For example, an origin could indicate in an HTTP response that HTTP/3
was available on UDP port 50781 at the same hostname by including the was available on UDP port 50781 at the same hostname by including the
following header field: following header field:
Alt-Svc: h3=":50781" Alt-Svc: h3=":50781"
On receipt of an Alt-Svc record indicating HTTP/3 support, a client On receipt of an Alt-Svc record indicating HTTP/3 support, a client
MAY attempt to establish a QUIC connection to the indicated host and MAY attempt to establish a QUIC connection to the indicated host and
port; if this connection is successful, the client can send HTTP port; if this connection is successful, the client can send HTTP
skipping to change at page 10, line 30 skipping to change at page 10, line 36
connections on the indicated port of whatever host is identified connections on the indicated port of whatever host is identified
within the authority component. Because HTTP/3 does not use TCP, within the authority component. Because HTTP/3 does not use TCP,
HTTP/3 cannot be used for direct access to the authoritative server HTTP/3 cannot be used for direct access to the authoritative server
for a resource identified by an "http" URI. However, protocol for a resource identified by an "http" URI. However, protocol
extensions such as [ALTSVC] permit the authoritative server to extensions such as [ALTSVC] permit the authoritative server to
identify other services that are also authoritative and that might be identify other services that are also authoritative and that might be
reachable over HTTP/3. reachable over HTTP/3.
Prior to making requests for an origin whose scheme is not "https", Prior to making requests for an origin whose scheme is not "https",
the client MUST ensure the server is willing to serve that scheme. the client MUST ensure the server is willing to serve that scheme.
If the client intends to make requests for an origin whose scheme is For origins whose scheme is "http", an experimental method to
"http", this means that it MUST obtain a valid "http-opportunistic" accomplish this is described in [RFC8164]. Other mechanisms might be
response for the origin as described in [RFC8164] prior to making any defined for various schemes in the future.
such requests. Other schemes might define other mechanisms.
3.3. Connection Establishment 3.3. Connection Establishment
HTTP/3 relies on QUIC version 1 as the underlying transport. The use HTTP/3 relies on QUIC version 1 as the underlying transport. The use
of other QUIC transport versions with HTTP/3 MAY be defined by future of other QUIC transport versions with HTTP/3 MAY be defined by future
specifications. specifications.
QUIC version 1 uses TLS version 1.3 or greater as its handshake QUIC version 1 uses TLS version 1.3 or greater as its handshake
protocol. HTTP/3 clients MUST support a mechanism to indicate the protocol. HTTP/3 clients MUST support a mechanism to indicate the
target host to the server during the TLS handshake. If the server is target host to the server during the TLS handshake. If the server is
skipping to change at page 11, line 31 skipping to change at page 11, line 37
reused for requests with multiple different URI authority components. reused for requests with multiple different URI authority components.
In general, a server is considered authoritative for all URIs with In general, a server is considered authoritative for all URIs with
the "https" scheme for which the hostname in the URI is present in the "https" scheme for which the hostname in the URI is present in
the authenticated certificate provided by the server, either as the the authenticated certificate provided by the server, either as the
CN field of the certificate subject or as a dNSName in the CN field of the certificate subject or as a dNSName in the
subjectAltName field of the certificate; see [RFC6125]. For a host subjectAltName field of the certificate; see [RFC6125]. For a host
that is an IP address, the client MUST verify that the address that is an IP address, the client MUST verify that the address
appears as an iPAddress in the subjectAltName field of the appears as an iPAddress in the subjectAltName field of the
certificate. If the hostname or address is not present in the certificate. If the hostname or address is not present in the
certificate, the client MUST NOT consider the server authoritative certificate, the client MUST NOT consider the server authoritative
for origins containing that hostname or address. See Section 6.4 of for origins containing that hostname or address. See Section 4.3 of
[SEMANTICS] for more detail on authoritative access. [SEMANTICS] for more detail on authoritative access.
Clients SHOULD NOT open more than one HTTP/3 connection to a given Clients SHOULD NOT open more than one HTTP/3 connection to a given
host and port pair, where the host is derived from a URI, a selected host and port pair, where the host is derived from a URI, a selected
alternative service ([ALTSVC]), or a configured proxy. A client MAY alternative service ([ALTSVC]), or a configured proxy. A client MAY
open multiple connections to the same IP address and UDP port using open multiple HTTP/3 connections to the same IP address and UDP port
different transport or TLS configurations but SHOULD avoid creating using different transport or TLS configurations but SHOULD avoid
multiple connections with the same configuration. creating multiple connections with the same configuration.
Servers are encouraged to maintain open connections for as long as Servers are encouraged to maintain open HTTP/3 connections for as
possible but are permitted to terminate idle connections if long as possible but are permitted to terminate idle connections if
necessary. When either endpoint chooses to close the HTTP/3 necessary. When either endpoint chooses to close the HTTP/3
connection, the terminating endpoint SHOULD first send a GOAWAY frame connection, the terminating endpoint SHOULD first send a GOAWAY frame
(Section 5.2) so that both endpoints can reliably determine whether (Section 5.2) so that both endpoints can reliably determine whether
previously sent frames have been processed and gracefully complete or previously sent frames have been processed and gracefully complete or
terminate any necessary remaining tasks. terminate any necessary remaining tasks.
A server that does not wish clients to reuse connections for a A server that does not wish clients to reuse HTTP/3 connections for a
particular origin can indicate that it is not authoritative for a particular origin can indicate that it is not authoritative for a
request by sending a 421 (Misdirected Request) status code in request by sending a 421 (Misdirected Request) status code in
response to the request; see Section 9.1.2 of [HTTP2]. response to the request; see Section 9.1.2 of [HTTP2].
4. HTTP Request Lifecycle 4. HTTP Request Lifecycle
4.1. HTTP Message Exchanges 4.1. HTTP Message Exchanges
A client sends an HTTP request on a client-initiated bidirectional A client sends an HTTP request on a client-initiated bidirectional
QUIC stream. A client MUST send only a single request on a given QUIC stream. A client MUST send only a single request on a given
stream. A server sends zero or more interim HTTP responses on the stream. A server sends zero or more interim HTTP responses on the
same stream as the request, followed by a single final HTTP response, same stream as the request, followed by a single final HTTP response,
as detailed below. See Section 10 of [SEMANTICS] for a description as detailed below. See Section 14 of [SEMANTICS] for a description
of interim and final HTTP responses. of interim and final HTTP responses.
Pushed responses are sent on a server-initiated unidirectional QUIC Pushed responses are sent on a server-initiated unidirectional QUIC
stream; see Section 6.2.2. A server sends zero or more interim HTTP stream; see Section 6.2.2. A server sends zero or more interim HTTP
responses, followed by a single final HTTP response, in the same responses, followed by a single final HTTP response, in the same
manner as a standard response. Push is described in more detail in manner as a standard response. Push is described in more detail in
Section 4.4. Section 4.4.
On a given stream, receipt of multiple requests or receipt of an On a given stream, receipt of multiple requests or receipt of an
additional HTTP response following a final HTTP response MUST be additional HTTP response following a final HTTP response MUST be
skipping to change at page 12, line 37 skipping to change at page 12, line 50
1. the header field section, sent as a single HEADERS frame (see 1. the header field section, sent as a single HEADERS frame (see
Section 7.2.2), Section 7.2.2),
2. optionally, the payload body, if present, sent as a series of 2. optionally, the payload body, if present, sent as a series of
DATA frames (see Section 7.2.1), and DATA frames (see Section 7.2.1), and
3. optionally, the trailer field section, if present, sent as a 3. optionally, the trailer field section, if present, sent as a
single HEADERS frame. single HEADERS frame.
Header and trailer field sections are described in Section 5 of Header and trailer field sections are described in Sections 5.4 and
[SEMANTICS]; the payload body is described in Section 7.3.3 of 5.6 of [SEMANTICS]; the payload body is described in Section 5.5.4 of
[SEMANTICS]. [SEMANTICS].
Receipt of an invalid sequence of frames MUST be treated as a Receipt of an invalid sequence of frames MUST be treated as a
connection error of type H3_FRAME_UNEXPECTED (Section 8). In connection error of type H3_FRAME_UNEXPECTED (Section 8). In
particular, a DATA frame before any HEADERS frame, or a HEADERS or particular, a DATA frame before any HEADERS frame, or a HEADERS or
DATA frame after the trailing HEADERS frame is considered invalid. DATA frame after the trailing HEADERS frame is considered invalid.
Other frame types, especially unknown frame types, might be permitted
subject to their own rules; see Section 9.
A server MAY send one or more PUSH_PROMISE frames (Section 7.2.5) A server MAY send one or more PUSH_PROMISE frames (Section 7.2.5)
before, after, or interleaved with the frames of a response message. before, after, or interleaved with the frames of a response message.
These PUSH_PROMISE frames are not part of the response; see These PUSH_PROMISE frames are not part of the response; see
Section 4.4 for more details. These frames are not permitted in Section 4.4 for more details. PUSH_PROMISE frames are not permitted
pushed responses; a pushed response that includes PUSH_PROMISE frames on push streams; a pushed response that includes PUSH_PROMISE frames
MUST be treated as a connection error of type H3_FRAME_UNEXPECTED. MUST be treated as a connection error of type H3_FRAME_UNEXPECTED.
Frames of unknown types (Section 9), including reserved frames Frames of unknown types (Section 9), including reserved frames
(Section 7.2.8) MAY be sent on a request or push stream before, (Section 7.2.8) MAY be sent on a request or push stream before,
after, or interleaved with other frames described in this section. after, or interleaved with other frames described in this section.
The HEADERS and PUSH_PROMISE frames might reference updates to the The HEADERS and PUSH_PROMISE frames might reference updates to the
QPACK dynamic table. While these updates are not directly part of QPACK dynamic table. While these updates are not directly part of
the message exchange, they must be received and processed before the the message exchange, they must be received and processed before the
message can be consumed. See Section 4.1.1 for more details. message can be consumed. See Section 4.1.1 for more details.
The "chunked" transfer encoding defined in Section 7.1 of [HTTP11] The "chunked" transfer encoding defined in Section 7.1 of [HTTP11]
MUST NOT be used. MUST NOT be used.
A response MAY consist of multiple messages when and only when one or A response MAY consist of multiple messages when and only when one or
more interim responses (1xx; see Section 10.2 of [SEMANTICS]) precede more interim responses (1xx; see Section 14.2 of [SEMANTICS]) precede
a final response to the same request. Interim responses do not a final response to the same request. Interim responses do not
contain a payload body or trailers. contain a payload body or trailers.
An HTTP request/response exchange fully consumes a client-initiated An HTTP request/response exchange fully consumes a client-initiated
bidirectional QUIC stream. After sending a request, a client MUST bidirectional QUIC stream. After sending a request, a client MUST
close the stream for sending. Unless using the CONNECT method (see close the stream for sending. Unless using the CONNECT method (see
Section 4.2), clients MUST NOT make stream closure dependent on Section 4.2), clients MUST NOT make stream closure dependent on
receiving a response to their request. After sending a final receiving a response to their request. After sending a final
response, the server MUST close the stream for sending. At this response, the server MUST close the stream for sending. At this
point, the QUIC stream is fully closed. point, the QUIC stream is fully closed.
skipping to change at page 14, line 12 skipping to change at page 14, line 26
reading the request, clients SHOULD continue sending the body of the reading the request, clients SHOULD continue sending the body of the
request and close the stream normally. request and close the stream normally.
4.1.1. Field Formatting and Compression 4.1.1. Field Formatting and Compression
HTTP messages carry metadata as a series of key-value pairs, called HTTP messages carry metadata as a series of key-value pairs, called
HTTP fields. For a listing of registered HTTP fields, see the HTTP fields. For a listing of registered HTTP fields, see the
"Hypertext Transfer Protocol (HTTP) Field Name Registry" maintained "Hypertext Transfer Protocol (HTTP) Field Name Registry" maintained
at https://www.iana.org/assignments/http-fields/. at https://www.iana.org/assignments/http-fields/.
*Note:* This registry will not exist until [SEMANTICS] is
approved. *RFC Editor*, please remove this note prior to
publication.
As in previous versions of HTTP, field names are strings containing a As in previous versions of HTTP, field names are strings containing a
subset of ASCII characters that are compared in a case-insensitive subset of ASCII characters that are compared in a case-insensitive
fashion. Properties of HTTP field names and values are discussed in fashion. Properties of HTTP field names and values are discussed in
more detail in Section 5.3 of [SEMANTICS]. As in HTTP/2, characters more detail in Section 5.4.3 of [SEMANTICS]. As in HTTP/2,
in field names MUST be converted to lowercase prior to their characters in field names MUST be converted to lowercase prior to
encoding. A request or response containing uppercase characters in their encoding. A request or response containing uppercase
field names MUST be treated as malformed (Section 4.1.3). characters in field names MUST be treated as malformed
(Section 4.1.3).
Like HTTP/2, HTTP/3 does not use the Connection header field to Like HTTP/2, HTTP/3 does not use the Connection header field to
indicate connection-specific fields; in this protocol, connection- indicate connection-specific fields; in this protocol, connection-
specific metadata is conveyed by other means. An endpoint MUST NOT specific metadata is conveyed by other means. An endpoint MUST NOT
generate an HTTP/3 field section containing connection-specific generate an HTTP/3 field section containing connection-specific
fields; any message containing connection-specific fields MUST be fields; any message containing connection-specific fields MUST be
treated as malformed (Section 4.1.3). treated as malformed (Section 4.1.3).
The only exception to this is the TE header field, which MAY be The only exception to this is the TE header field, which MAY be
present in an HTTP/3 request header; when it is, it MUST NOT contain present in an HTTP/3 request header; when it is, it MUST NOT contain
skipping to change at page 14, line 47 skipping to change at page 15, line 17
4.1.1.1. Pseudo-Header Fields 4.1.1.1. Pseudo-Header Fields
Like HTTP/2, HTTP/3 employs a series of pseudo-header fields where Like HTTP/2, HTTP/3 employs a series of pseudo-header fields where
the field name begins with the ':' character (ASCII 0x3a). These the field name begins with the ':' character (ASCII 0x3a). These
pseudo-header fields convey the target URI, the method of the pseudo-header fields convey the target URI, the method of the
request, and the status code for the response. request, and the status code for the response.
Pseudo-header fields are not HTTP fields. Endpoints MUST NOT Pseudo-header fields are not HTTP fields. Endpoints MUST NOT
generate pseudo-header fields other than those defined in this generate pseudo-header fields other than those defined in this
document, except as negotiated via an extension; see Section 9. document; however, an extension could negotiate a modification of
this restriction; see Section 9.
Pseudo-header fields are only valid in the context in which they are Pseudo-header fields are only valid in the context in which they are
defined. Pseudo-header fields defined for requests MUST NOT appear defined. Pseudo-header fields defined for requests MUST NOT appear
in responses; pseudo-header fields defined for responses MUST NOT in responses; pseudo-header fields defined for responses MUST NOT
appear in requests. Pseudo-header fields MUST NOT appear in appear in requests. Pseudo-header fields MUST NOT appear in
trailers. Endpoints MUST treat a request or response that contains trailers. Endpoints MUST treat a request or response that contains
undefined or invalid pseudo-header fields as malformed undefined or invalid pseudo-header fields as malformed
(Section 4.1.3). (Section 4.1.3).
All pseudo-header fields MUST appear in the header field section All pseudo-header fields MUST appear in the header field section
skipping to change at page 16, line 26 skipping to change at page 16, line 47
":authority" pseudo-header or "Host" header fields. ":authority" pseudo-header or "Host" header fields.
An HTTP request that omits mandatory pseudo-header fields or contains An HTTP request that omits mandatory pseudo-header fields or contains
invalid values for those pseudo-header fields is malformed invalid values for those pseudo-header fields is malformed
(Section 4.1.3). (Section 4.1.3).
HTTP/3 does not define a way to carry the version identifier that is HTTP/3 does not define a way to carry the version identifier that is
included in the HTTP/1.1 request line. included in the HTTP/1.1 request line.
For responses, a single ":status" pseudo-header field is defined that For responses, a single ":status" pseudo-header field is defined that
carries the HTTP status code; see Section 10 of [SEMANTICS]. This carries the HTTP status code; see Section 14 of [SEMANTICS]. This
pseudo-header field MUST be included in all responses; otherwise, the pseudo-header field MUST be included in all responses; otherwise, the
response is malformed (Section 4.1.3). response is malformed (Section 4.1.3).
HTTP/3 does not define a way to carry the version or reason phrase HTTP/3 does not define a way to carry the version or reason phrase
that is included in an HTTP/1.1 status line. that is included in an HTTP/1.1 status line.
4.1.1.2. Field Compression 4.1.1.2. Field Compression
HTTP/3 uses QPACK field compression as described in [QPACK], a HTTP/3 uses QPACK field compression as described in [QPACK], a
variation of HPACK that allows the flexibility to avoid compression- variation of HPACK that allows the flexibility to avoid compression-
skipping to change at page 18, line 33 skipping to change at page 19, line 4
* the presence of prohibited fields or pseudo-header fields, * the presence of prohibited fields or pseudo-header fields,
* the absence of mandatory pseudo-header fields, * the absence of mandatory pseudo-header fields,
* invalid values for pseudo-header fields, * invalid values for pseudo-header fields,
* pseudo-header fields after fields, * pseudo-header fields after fields,
* an invalid sequence of HTTP messages, * an invalid sequence of HTTP messages,
* the inclusion of uppercase field names, or * the inclusion of uppercase field names, or
* the inclusion of invalid characters in field names or values * the inclusion of invalid characters in field names or values
A request or response that includes a payload body can include a A request or response that includes a payload body can include a
Content-Length header field. A request or response is also malformed Content-Length header field. A request or response is also malformed
if the value of a content-length header field does not equal the sum if the value of a content-length header field does not equal the sum
of the DATA frame payload lengths that form the body. A response of the DATA frame payload lengths that form the body. A response
that is defined to have no payload, as described in Section 7.3.3 of that is defined to have no payload, as described in Section 5.5.4 of
[SEMANTICS] can have a non-zero content-length field, even though no [SEMANTICS], can have a non-zero content-length field, even though no
content is included in DATA frames. content is included in DATA frames.
Intermediaries that process HTTP requests or responses (i.e., any Intermediaries that process HTTP requests or responses (i.e., any
intermediary not acting as a tunnel) MUST NOT forward a malformed intermediary not acting as a tunnel) MUST NOT forward a malformed
request or response. Malformed requests or responses that are request or response. Malformed requests or responses that are
detected MUST be treated as a stream error (Section 8) of type detected MUST be treated as a stream error (Section 8) of type
H3_GENERAL_PROTOCOL_ERROR. H3_GENERAL_PROTOCOL_ERROR.
For malformed requests, a server MAY send an HTTP response indicating For malformed requests, a server MAY send an HTTP response indicating
the error prior to closing or resetting the stream. Clients MUST NOT the error prior to closing or resetting the stream. Clients MUST NOT
skipping to change at page 19, line 42 skipping to change at page 20, line 13
of CONNECT requests; see Section 3.2.3 of [HTTP11]) of CONNECT requests; see Section 3.2.3 of [HTTP11])
The request stream remains open at the end of the request to carry The request stream remains open at the end of the request to carry
the data to be transferred. A CONNECT request that does not conform the data to be transferred. A CONNECT request that does not conform
to these restrictions is malformed; see Section 4.1.3. to these restrictions is malformed; see Section 4.1.3.
A proxy that supports CONNECT establishes a TCP connection A proxy that supports CONNECT establishes a TCP connection
([RFC0793]) to the server identified in the ":authority" pseudo- ([RFC0793]) to the server identified in the ":authority" pseudo-
header field. Once this connection is successfully established, the header field. Once this connection is successfully established, the
proxy sends a HEADERS frame containing a 2xx series status code to proxy sends a HEADERS frame containing a 2xx series status code to
the client, as defined in Section 10.3 of [SEMANTICS]. the client, as defined in Section 14.3 of [SEMANTICS].
All DATA frames on the stream correspond to data sent or received on All DATA frames on the stream correspond to data sent or received on
the TCP connection. The payload of any DATA frame sent by the client the TCP connection. The payload of any DATA frame sent by the client
is transmitted by the proxy to the TCP server; data received from the is transmitted by the proxy to the TCP server; data received from the
TCP server is packaged into DATA frames by the proxy. Note that the TCP server is packaged into DATA frames by the proxy. Note that the
size and number of TCP segments is not guaranteed to map predictably size and number of TCP segments is not guaranteed to map predictably
to the size and number of HTTP DATA or QUIC STREAM frames. to the size and number of HTTP DATA or QUIC STREAM frames.
Once the CONNECT method has completed, only DATA frames are permitted Once the CONNECT method has completed, only DATA frames are permitted
to be sent on the stream. Extension frames MAY be used if to be sent on the stream. Extension frames MAY be used if
skipping to change at page 20, line 31 skipping to change at page 20, line 48
A TCP connection error is signaled by abruptly terminating the A TCP connection error is signaled by abruptly terminating the
stream. A proxy treats any error in the TCP connection, which stream. A proxy treats any error in the TCP connection, which
includes receiving a TCP segment with the RST bit set, as a stream includes receiving a TCP segment with the RST bit set, as a stream
error of type H3_CONNECT_ERROR (Section 8.1). Correspondingly, if a error of type H3_CONNECT_ERROR (Section 8.1). Correspondingly, if a
proxy detects an error with the stream or the QUIC connection, it proxy detects an error with the stream or the QUIC connection, it
MUST close the TCP connection. If the underlying TCP implementation MUST close the TCP connection. If the underlying TCP implementation
permits it, the proxy SHOULD send a TCP segment with the RST bit set. permits it, the proxy SHOULD send a TCP segment with the RST bit set.
4.3. HTTP Upgrade 4.3. HTTP Upgrade
HTTP/3 does not support the HTTP Upgrade mechanism (Section 6.7 of HTTP/3 does not support the HTTP Upgrade mechanism (Section 6.6 of
{{!SEMANTICS}) or 101 (Switching Protocols) informational status code [SEMANTICS]) or 101 (Switching Protocols) informational status code
(Section 10.2.2 of [SEMANTICS]). (Section 14.2.2 of [SEMANTICS]).
4.4. Server Push 4.4. Server Push
Server push is an interaction mode that permits a server to push a Server push is an interaction mode that permits a server to push a
request-response exchange to a client in anticipation of the client request-response exchange to a client in anticipation of the client
making the indicated request. This trades off network usage against making the indicated request. This trades off network usage against
a potential latency gain. HTTP/3 server push is similar to what is a potential latency gain. HTTP/3 server push is similar to what is
described in Section 8.2 of [HTTP2], but uses different mechanisms. described in Section 8.2 of [HTTP2], but uses different mechanisms.
Each server push is assigned a unique Push ID by the server. The Each server push is assigned a unique Push ID by the server. The
Push ID is used to refer to the push in various contexts throughout Push ID is used to refer to the push in various contexts throughout
the lifetime of the connection. the lifetime of the HTTP/3 connection.
The Push ID space begins at zero, and ends at a maximum value set by The Push ID space begins at zero, and ends at a maximum value set by
the MAX_PUSH_ID frame; see Section 7.2.7. In particular, a server is the MAX_PUSH_ID frame; see Section 7.2.7. In particular, a server is
not able to push until after the client sends a MAX_PUSH_ID frame. A not able to push until after the client sends a MAX_PUSH_ID frame. A
client sends MAX_PUSH_ID frames to control the number of pushes that client sends MAX_PUSH_ID frames to control the number of pushes that
a server can promise. A server SHOULD use Push IDs sequentially, a server can promise. A server SHOULD use Push IDs sequentially,
beginning from zero. A client MUST treat receipt of a push stream as beginning from zero. A client MUST treat receipt of a push stream as
a connection error of type H3_ID_ERROR when no MAX_PUSH_ID frame has a connection error of type H3_ID_ERROR when no MAX_PUSH_ID frame has
been sent or when the stream references a Push ID that is greater been sent or when the stream references a Push ID that is greater
than the maximum Push ID. than the maximum Push ID.
skipping to change at page 22, line 45 skipping to change at page 23, line 18
5. Connection Closure 5. Connection Closure
Once established, an HTTP/3 connection can be used for many requests Once established, an HTTP/3 connection can be used for many requests
and responses over time until the connection is closed. Connection and responses over time until the connection is closed. Connection
closure can happen in any of several different ways. closure can happen in any of several different ways.
5.1. Idle Connections 5.1. Idle Connections
Each QUIC endpoint declares an idle timeout during the handshake. If Each QUIC endpoint declares an idle timeout during the handshake. If
the connection remains idle (no packets received) for longer than the QUIC connection remains idle (no packets received) for longer
this duration, the peer will assume that the connection has been than this duration, the peer will assume that the connection has been
closed. HTTP/3 implementations will need to open a new connection closed. HTTP/3 implementations will need to open a new HTTP/3
for new requests if the existing connection has been idle for longer connection for new requests if the existing connection has been idle
than the server's advertised idle timeout, and SHOULD do so if for longer than the server's advertised idle timeout, and SHOULD do
approaching the idle timeout. so if approaching the idle timeout.
HTTP clients are expected to request that the transport keep HTTP clients are expected to request that the transport keep
connections open while there are responses outstanding for requests connections open while there are responses outstanding for requests
or server pushes, as described in Section 10.1.2 of [QUIC-TRANSPORT]. or server pushes, as described in Section 10.1.2 of [QUIC-TRANSPORT].
If the client is not expecting a response from the server, allowing If the client is not expecting a response from the server, allowing
an idle connection to time out is preferred over expending effort an idle connection to time out is preferred over expending effort
maintaining a connection that might not be needed. A gateway MAY maintaining a connection that might not be needed. A gateway MAY
maintain connections in anticipation of need rather than incur the maintain connections in anticipation of need rather than incur the
latency cost of connection establishment to servers. Servers SHOULD latency cost of connection establishment to servers. Servers SHOULD
NOT actively keep connections open. NOT actively keep connections open.
5.2. Connection Shutdown 5.2. Connection Shutdown
Even when a connection is not idle, either endpoint can decide to Even when a connection is not idle, either endpoint can decide to
stop using the connection and initiate a graceful connection close. stop using the connection and initiate a graceful connection close.
Endpoints initiate the graceful shutdown of a connection by sending a Endpoints initiate the graceful shutdown of an HTTP/3 connection by
GOAWAY frame (Section 7.2.6). The GOAWAY frame contains an sending a GOAWAY frame (Section 7.2.6). The GOAWAY frame contains an
identifier that indicates to the receiver the range of requests or identifier that indicates to the receiver the range of requests or
pushes that were or might be processed in this connection. The pushes that were or might be processed in this connection. The
server sends a client-initiated bidirectional Stream ID; the client server sends a client-initiated bidirectional Stream ID; the client
sends a Push ID (Section 4.4). Requests or pushes with the indicated sends a Push ID (Section 4.4). Requests or pushes with the indicated
identifier or greater are rejected (Section 4.1.2) by the sender of identifier or greater are rejected (Section 4.1.2) by the sender of
the GOAWAY. This identifier MAY be zero if no requests or pushes the GOAWAY. This identifier MAY be zero if no requests or pushes
were processed. were processed.
The information in the GOAWAY frame enables a client and server to The information in the GOAWAY frame enables a client and server to
agree on which requests or pushes were accepted prior to the agree on which requests or pushes were accepted prior to the shutdown
connection shutdown. Upon sending a GOAWAY frame, the endpoint of the HTTP/3 connection. Upon sending a GOAWAY frame, the endpoint
SHOULD explicitly cancel (see Section 4.1.2 and Section 7.2.3) any SHOULD explicitly cancel (see Section 4.1.2 and Section 7.2.3) any
requests or pushes that have identifiers greater than or equal to requests or pushes that have identifiers greater than or equal to
that indicated, in order to clean up transport state for the affected that indicated, in order to clean up transport state for the affected
streams. The endpoint SHOULD continue to do so as more requests or streams. The endpoint SHOULD continue to do so as more requests or
pushes arrive. pushes arrive.
Endpoints MUST NOT initiate new requests or promise new pushes on the Endpoints MUST NOT initiate new requests or promise new pushes on the
connection after receipt of a GOAWAY frame from the peer. Clients connection after receipt of a GOAWAY frame from the peer. Clients
MAY establish a new connection to send additional requests. MAY establish a new connection to send additional requests.
Some requests or pushes might already be in transit: Some requests or pushes might already be in transit:
* Upon receipt of a GOAWAY frame, if the client has already sent * Upon receipt of a GOAWAY frame, if the client has already sent
requests with a Stream ID greater than or equal to the identifier requests with a Stream ID greater than or equal to the identifier
contained in the GOAWAY frame, those requests will not be contained in the GOAWAY frame, those requests will not be
processed. Clients can safely retry unprocessed requests on a processed. Clients can safely retry unprocessed requests on a
different connection. A client that is unable to retry requests different HTTP connection. A client that is unable to retry
loses all requests that are in flight when the server closes the requests loses all requests that are in flight when the server
connection. closes the connection.
Requests on Stream IDs less than the Stream ID in a GOAWAY frame Requests on Stream IDs less than the Stream ID in a GOAWAY frame
from the server might have been processed; their status cannot be from the server might have been processed; their status cannot be
known until a response is received, the stream is reset known until a response is received, the stream is reset
individually, another GOAWAY is received, or the connection individually, another GOAWAY is received, or the connection
terminates. terminates.
Servers MAY reject individual requests on streams below the Servers MAY reject individual requests on streams below the
indicated ID if these requests were not processed. indicated ID if these requests were not processed.
skipping to change at page 24, line 29 skipping to change at page 24, line 47
is known in advance, even if the advance notice is small, so that the is known in advance, even if the advance notice is small, so that the
remote peer can know whether a request has been partially processed remote peer can know whether a request has been partially processed
or not. For example, if an HTTP client sends a POST at the same time or not. For example, if an HTTP client sends a POST at the same time
that a server closes a QUIC connection, the client cannot know if the that a server closes a QUIC connection, the client cannot know if the
server started to process that POST request if the server does not server started to process that POST request if the server does not
send a GOAWAY frame to indicate what streams it might have acted on. send a GOAWAY frame to indicate what streams it might have acted on.
An endpoint MAY send multiple GOAWAY frames indicating different An endpoint MAY send multiple GOAWAY frames indicating different
identifiers, but the identifier in each frame MUST NOT be greater identifiers, but the identifier in each frame MUST NOT be greater
than the identifier in any previous frame, since clients might than the identifier in any previous frame, since clients might
already have retried unprocessed requests on another connection. already have retried unprocessed requests on another HTTP connection.
Receiving a GOAWAY containing a larger identifier than previously Receiving a GOAWAY containing a larger identifier than previously
received MUST be treated as a connection error of type H3_ID_ERROR. received MUST be treated as a connection error of type H3_ID_ERROR.
An endpoint that is attempting to gracefully shut down a connection An endpoint that is attempting to gracefully shut down a connection
can send a GOAWAY frame with a value set to the maximum possible can send a GOAWAY frame with a value set to the maximum possible
value (2^62-4 for servers, 2^62-1 for clients). This ensures that value (2^62-4 for servers, 2^62-1 for clients). This ensures that
the peer stops creating new requests or pushes. After allowing time the peer stops creating new requests or pushes. After allowing time
for any in-flight requests or pushes to arrive, the endpoint can send for any in-flight requests or pushes to arrive, the endpoint can send
another GOAWAY frame indicating which requests or pushes it might another GOAWAY frame indicating which requests or pushes it might
accept before the end of the connection. This ensures that a accept before the end of the connection. This ensures that a
skipping to change at page 26, line 4 skipping to change at page 26, line 24
might have been processed. might have been processed.
6. Stream Mapping and Usage 6. Stream Mapping and Usage
A QUIC stream provides reliable in-order delivery of bytes, but makes A QUIC stream provides reliable in-order delivery of bytes, but makes
no guarantees about order of delivery with regard to bytes on other no guarantees about order of delivery with regard to bytes on other
streams. On the wire, data is framed into QUIC STREAM frames, but streams. On the wire, data is framed into QUIC STREAM frames, but
this framing is invisible to the HTTP framing layer. The transport this framing is invisible to the HTTP framing layer. The transport
layer buffers and orders received QUIC STREAM frames, exposing the layer buffers and orders received QUIC STREAM frames, exposing the
data contained within as a reliable byte stream to the application. data contained within as a reliable byte stream to the application.
Although QUIC permits out-of-order delivery within a stream, HTTP/3 Although QUIC permits out-of-order delivery within a stream, HTTP/3
does not make use of this feature. does not make use of this feature.
QUIC streams can be either unidirectional, carrying data only from QUIC streams can be either unidirectional, carrying data only from
initiator to receiver, or bidirectional. Streams can be initiated by initiator to receiver, or bidirectional. Streams can be initiated by
either the client or the server. For more detail on QUIC streams, either the client or the server. For more detail on QUIC streams,
see Section 2 of [QUIC-TRANSPORT]. see Section 2 of [QUIC-TRANSPORT].
When HTTP fields and data are sent over QUIC, the QUIC layer handles When HTTP fields and data are sent over QUIC, the QUIC layer handles
most of the stream management. HTTP does not need to do any separate most of the stream management. HTTP does not need to do any separate
multiplexing when using QUIC - data sent over a QUIC stream always multiplexing when using QUIC - data sent over a QUIC stream always
maps to a particular HTTP transaction or connection context. maps to a particular HTTP transaction or to the entire HTTP/3
connection context.
6.1. Bidirectional Streams 6.1. Bidirectional Streams
All client-initiated bidirectional streams are used for HTTP requests All client-initiated bidirectional streams are used for HTTP requests
and responses. A bidirectional stream ensures that the response can and responses. A bidirectional stream ensures that the response can
be readily correlated with the request. This means that the client's be readily correlated with the request. This means that the client's
first request occurs on QUIC stream 0, with subsequent requests on first request occurs on QUIC stream 0, with subsequent requests on
stream 4, 8, and so on. In order to permit these streams to open, an stream 4, 8, and so on. In order to permit these streams to open, an
HTTP/3 server SHOULD configure non-zero minimum values for the number HTTP/3 server SHOULD configure non-zero minimum values for the number
of permitted streams and the initial stream flow control window. So of permitted streams and the initial stream flow control window. So
skipping to change at page 28, line 24 skipping to change at page 28, line 49
H3_MISSING_SETTINGS. Only one control stream per peer is permitted; H3_MISSING_SETTINGS. Only one control stream per peer is permitted;
receipt of a second stream claiming to be a control stream MUST be receipt of a second stream claiming to be a control stream MUST be
treated as a connection error of type H3_STREAM_CREATION_ERROR. The treated as a connection error of type H3_STREAM_CREATION_ERROR. The
sender MUST NOT close the control stream, and the receiver MUST NOT sender MUST NOT close the control stream, and the receiver MUST NOT
request that the sender close the control stream. If either control request that the sender close the control stream. If either control
stream is closed at any point, this MUST be treated as a connection stream is closed at any point, this MUST be treated as a connection
error of type H3_CLOSED_CRITICAL_STREAM. error of type H3_CLOSED_CRITICAL_STREAM.
A pair of unidirectional streams is used rather than a single A pair of unidirectional streams is used rather than a single
bidirectional stream. This allows either peer to send data as soon bidirectional stream. This allows either peer to send data as soon
as it is able. Depending on whether 0-RTT is enabled on the as it is able. Depending on whether 0-RTT is enabled on the QUIC
connection, either client or server might be able to send stream data connection, either client or server might be able to send stream data
first after the cryptographic handshake completes. first after the cryptographic handshake completes.
6.2.2. Push Streams 6.2.2. Push Streams
Server push is an optional feature introduced in HTTP/2 that allows a Server push is an optional feature introduced in HTTP/2 that allows a
server to initiate a response before a request has been made. See server to initiate a response before a request has been made. See
Section 4.4 for more details. Section 4.4 for more details.
A push stream is indicated by a stream type of 0x01, followed by the A push stream is indicated by a stream type of 0x01, followed by the
skipping to change at page 32, line 34 skipping to change at page 33, line 5
When a client sends CANCEL_PUSH, it is indicating that it does not When a client sends CANCEL_PUSH, it is indicating that it does not
wish to receive the promised resource. The server SHOULD abort wish to receive the promised resource. The server SHOULD abort
sending the resource, but the mechanism to do so depends on the state sending the resource, but the mechanism to do so depends on the state
of the corresponding push stream. If the server has not yet created of the corresponding push stream. If the server has not yet created
a push stream, it does not create one. If the push stream is open, a push stream, it does not create one. If the push stream is open,
the server SHOULD abruptly terminate that stream. If the push stream the server SHOULD abruptly terminate that stream. If the push stream
has already ended, the server MAY still abruptly terminate the stream has already ended, the server MAY still abruptly terminate the stream
or MAY take no action. or MAY take no action.
When a server sends CANCEL_PUSH, it is indicating that it will not be A server sends CANCEL_PUSH to indicate that it will not be fulfilling
fulfilling a promise. The client cannot expect the corresponding a promise which was previously sent. The client cannot expect the
promise to be fulfilled, unless it has already received and processed corresponding promise to be fulfilled, unless it has already received
the promised response. A server SHOULD send a CANCEL_PUSH frame even and processed the promised response. Regardless of whether a push
if it has opened the corresponding stream. stream has been opened, a server SHOULD send a CANCEL_PUSH frame when
it determines that promise will not be fulfilled. If a stream has
already been opened, the server can abort sending on the stream with
an error code of H3_REQUEST_CANCELLED.
Sending a CANCEL_PUSH frame has no direct effect on the state of Sending a CANCEL_PUSH frame has no direct effect on the state of
existing push streams. A client SHOULD NOT send a CANCEL_PUSH frame existing push streams. A client SHOULD NOT send a CANCEL_PUSH frame
when it has already received a corresponding push stream. A push when it has already received a corresponding push stream. A push
stream could arrive after a client has sent a CANCEL_PUSH frame, stream could arrive after a client has sent a CANCEL_PUSH frame,
because a server might not have processed the CANCEL_PUSH. The because a server might not have processed the CANCEL_PUSH. The
client SHOULD abort reading the stream with an error code of client SHOULD abort reading the stream with an error code of
H3_REQUEST_CANCELLED. H3_REQUEST_CANCELLED.
A CANCEL_PUSH frame is sent on the control stream. Receiving a A CANCEL_PUSH frame is sent on the control stream. Receiving a
skipping to change at page 33, line 35 skipping to change at page 34, line 14
7.2.4. SETTINGS 7.2.4. SETTINGS
The SETTINGS frame (type=0x4) conveys configuration parameters that The SETTINGS frame (type=0x4) conveys configuration parameters that
affect how endpoints communicate, such as preferences and constraints affect how endpoints communicate, such as preferences and constraints
on peer behavior. Individually, a SETTINGS parameter can also be on peer behavior. Individually, a SETTINGS parameter can also be
referred to as a "setting"; the identifier and value of each setting referred to as a "setting"; the identifier and value of each setting
parameter can be referred to as a "setting identifier" and a "setting parameter can be referred to as a "setting identifier" and a "setting
value". value".
SETTINGS frames always apply to a connection, never a single stream. SETTINGS frames always apply to an entire HTTP/3 connection, never a
A SETTINGS frame MUST be sent as the first frame of each control single stream. A SETTINGS frame MUST be sent as the first frame of
stream (see Section 6.2.1) by each peer, and MUST NOT be sent each control stream (see Section 6.2.1) by each peer, and MUST NOT be
subsequently. If an endpoint receives a second SETTINGS frame on the sent subsequently. If an endpoint receives a second SETTINGS frame
control stream, the endpoint MUST respond with a connection error of on the control stream, the endpoint MUST respond with a connection
type H3_FRAME_UNEXPECTED. error of type H3_FRAME_UNEXPECTED.
SETTINGS frames MUST NOT be sent on any stream other than the control SETTINGS frames MUST NOT be sent on any stream other than the control
stream. If an endpoint receives a SETTINGS frame on a different stream. If an endpoint receives a SETTINGS frame on a different
stream, the endpoint MUST respond with a connection error of type stream, the endpoint MUST respond with a connection error of type
H3_FRAME_UNEXPECTED. H3_FRAME_UNEXPECTED.
SETTINGS parameters are not negotiated; they describe characteristics SETTINGS parameters are not negotiated; they describe characteristics
of the sending peer that can be used by the receiving peer. However, of the sending peer that can be used by the receiving peer. However,
a negotiation can be implied by the use of SETTINGS - each peer uses a negotiation can be implied by the use of SETTINGS - each peer uses
SETTINGS to advertise a set of supported values. The definition of SETTINGS to advertise a set of supported values. The definition of
skipping to change at page 34, line 47 skipping to change at page 35, line 26
Figure 7: SETTINGS Frame Figure 7: SETTINGS Frame
An implementation MUST ignore the contents for any SETTINGS An implementation MUST ignore the contents for any SETTINGS
identifier it does not understand. identifier it does not understand.
7.2.4.1. Defined SETTINGS Parameters 7.2.4.1. Defined SETTINGS Parameters
The following settings are defined in HTTP/3: The following settings are defined in HTTP/3:
SETTINGS_MAX_FIELD_SECTION_SIZE (0x6): The default value is SETTINGS_MAX_FIELD_SECTION_SIZE (0x6): The default value is
unlimited. See Section 4.1.1 for usage. unlimited. See Section 4.1.1.3 for usage.
Setting identifiers of the format "0x1f * N + 0x21" for non-negative Setting identifiers of the format "0x1f * N + 0x21" for non-negative
integer values of N are reserved to exercise the requirement that integer values of N are reserved to exercise the requirement that
unknown identifiers be ignored. Such settings have no defined unknown identifiers be ignored. Such settings have no defined
meaning. Endpoints SHOULD include at least one such setting in their meaning. Endpoints SHOULD include at least one such setting in their
SETTINGS frame. Endpoints MUST NOT consider such settings to have SETTINGS frame. Endpoints MUST NOT consider such settings to have
any meaning upon receipt. any meaning upon receipt.
Because the setting has no defined meaning, the value of the setting Because the setting has no defined meaning, the value of the setting
can be any value the implementation selects. can be any value the implementation selects.
skipping to change at page 35, line 52 skipping to change at page 36, line 29
For clients using a 1-RTT QUIC connection, the initial value of each For clients using a 1-RTT QUIC connection, the initial value of each
server setting is the default value. 1-RTT keys will always become server setting is the default value. 1-RTT keys will always become
available prior to the packet containing SETTINGS being processed by available prior to the packet containing SETTINGS being processed by
QUIC, even if the server sends SETTINGS immediately. Clients SHOULD QUIC, even if the server sends SETTINGS immediately. Clients SHOULD
NOT wait indefinitely for SETTINGS to arrive before sending requests, NOT wait indefinitely for SETTINGS to arrive before sending requests,
but SHOULD process received datagrams in order to increase the but SHOULD process received datagrams in order to increase the
likelihood of processing SETTINGS before sending the first request. likelihood of processing SETTINGS before sending the first request.
When a 0-RTT QUIC connection is being used, the initial value of each When a 0-RTT QUIC connection is being used, the initial value of each
server setting is the value used in the previous session. Clients server setting is the value used in the previous session. Clients
SHOULD store the settings the server provided in the connection where SHOULD store the settings the server provided in the HTTP/3
resumption information was provided, but MAY opt not to store connection where resumption information was provided, but MAY opt not
settings in certain cases (e.g., if the session ticket is received to store settings in certain cases (e.g., if the session ticket is
before the SETTINGS frame). A client MUST comply with stored received before the SETTINGS frame). A client MUST comply with
settings - or default values, if no values are stored - when stored settings - or default values, if no values are stored - when
attempting 0-RTT. Once a server has provided new settings, clients attempting 0-RTT. Once a server has provided new settings, clients
MUST comply with those values. MUST comply with those values.
A server can remember the settings that it advertised, or store an A server can remember the settings that it advertised, or store an
integrity-protected copy of the values in the ticket and recover the integrity-protected copy of the values in the ticket and recover the
information when accepting 0-RTT data. A server uses the HTTP/3 information when accepting 0-RTT data. A server uses the HTTP/3
settings values in determining whether to accept 0-RTT data. If the settings values in determining whether to accept 0-RTT data. If the
server cannot determine that the settings remembered by a client are server cannot determine that the settings remembered by a client are
compatible with its current settings, it MUST NOT accept 0-RTT data. compatible with its current settings, it MUST NOT accept 0-RTT data.
Remembered settings are compatible if a client complying with those Remembered settings are compatible if a client complying with those
skipping to change at page 38, line 8 skipping to change at page 38, line 27
A client MUST NOT send a PUSH_PROMISE frame. A server MUST treat the A client MUST NOT send a PUSH_PROMISE frame. A server MUST treat the
receipt of a PUSH_PROMISE frame as a connection error of type receipt of a PUSH_PROMISE frame as a connection error of type
H3_FRAME_UNEXPECTED. H3_FRAME_UNEXPECTED.
See Section 4.4 for a description of the overall server push See Section 4.4 for a description of the overall server push
mechanism. mechanism.
7.2.6. GOAWAY 7.2.6. GOAWAY
The GOAWAY frame (type=0x7) is used to initiate graceful shutdown of The GOAWAY frame (type=0x7) is used to initiate graceful shutdown of
a connection by either endpoint. GOAWAY allows an endpoint to stop an HTTP/3 connection by either endpoint. GOAWAY allows an endpoint
accepting new requests or pushes while still finishing processing of to stop accepting new requests or pushes while still finishing
previously received requests and pushes. This enables administrative processing of previously received requests and pushes. This enables
actions, like server maintenance. GOAWAY by itself does not close a administrative actions, like server maintenance. GOAWAY by itself
connection. does not close a connection.
GOAWAY Frame { GOAWAY Frame {
Type (i) = 0x7, Type (i) = 0x7,
Length (i), Length (i),
Stream ID/Push ID (..), Stream ID/Push ID (..),
} }
Figure 9: GOAWAY Frame Figure 9: GOAWAY Frame
The GOAWAY frame is always sent on the control stream. In the server The GOAWAY frame is always sent on the control stream. In the server
to client direction, it carries a QUIC Stream ID for a client- to client direction, it carries a QUIC Stream ID for a client-
initiated bidirectional stream encoded as a variable-length integer. initiated bidirectional stream encoded as a variable-length integer.
A client MUST treat receipt of a GOAWAY frame containing a Stream ID A client MUST treat receipt of a GOAWAY frame containing a Stream ID
of any other type as a connection error of type H3_ID_ERROR. of any other type as a connection error of type H3_ID_ERROR.
In the client to server direction, the GOAWAY frame carries a Push ID In the client to server direction, the GOAWAY frame carries a Push ID
encoded as a variable-length integer. encoded as a variable-length integer.
The GOAWAY frame applies to the connection, not a specific stream. A The GOAWAY frame applies to the entire connection, not a specific
client MUST treat a GOAWAY frame on a stream other than the control stream. A client MUST treat a GOAWAY frame on a stream other than
stream as a connection error (Section 8) of type H3_FRAME_UNEXPECTED. the control stream as a connection error (Section 8) of type
H3_FRAME_UNEXPECTED.
See Section 5.2 for more information on the use of the GOAWAY frame. See Section 5.2 for more information on the use of the GOAWAY frame.
7.2.7. MAX_PUSH_ID 7.2.7. MAX_PUSH_ID
The MAX_PUSH_ID frame (type=0xd) is used by clients to control the The MAX_PUSH_ID frame (type=0xd) is used by clients to control the
number of server pushes that the server can initiate. This sets the number of server pushes that the server can initiate. This sets the
maximum value for a Push ID that the server can use in PUSH_PROMISE maximum value for a Push ID that the server can use in PUSH_PROMISE
and CANCEL_PUSH frames. Consequently, this also limits the number of and CANCEL_PUSH frames. Consequently, this also limits the number of
push streams that the server can initiate in addition to the limit push streams that the server can initiate in addition to the limit
maintained by the QUIC transport. maintained by the QUIC transport.
The MAX_PUSH_ID frame is always sent on the control stream. Receipt The MAX_PUSH_ID frame is always sent on the control stream. Receipt
of a MAX_PUSH_ID frame on any other stream MUST be treated as a of a MAX_PUSH_ID frame on any other stream MUST be treated as a
connection error of type H3_FRAME_UNEXPECTED. connection error of type H3_FRAME_UNEXPECTED.
A server MUST NOT send a MAX_PUSH_ID frame. A client MUST treat the A server MUST NOT send a MAX_PUSH_ID frame. A client MUST treat the
receipt of a MAX_PUSH_ID frame as a connection error of type receipt of a MAX_PUSH_ID frame as a connection error of type
H3_FRAME_UNEXPECTED. H3_FRAME_UNEXPECTED.
The maximum Push ID is unset when a connection is created, meaning The maximum Push ID is unset when an HTTP/3 connection is created,
that a server cannot push until it receives a MAX_PUSH_ID frame. A meaning that a server cannot push until it receives a MAX_PUSH_ID
client that wishes to manage the number of promised server pushes can frame. A client that wishes to manage the number of promised server
increase the maximum Push ID by sending MAX_PUSH_ID frames as the pushes can increase the maximum Push ID by sending MAX_PUSH_ID frames
server fulfills or cancels server pushes. as the server fulfills or cancels server pushes.
MAX_PUSH_ID Frame { MAX_PUSH_ID Frame {
Type (i) = 0xd, Type (i) = 0xd,
Length (i), Length (i),
Push ID (i), Push ID (i),
} }
Figure 10: MAX_PUSH_ID Frame Figure 10: MAX_PUSH_ID Frame
The MAX_PUSH_ID frame carries a single variable-length integer that The MAX_PUSH_ID frame carries a single variable-length integer that
skipping to change at page 39, line 31 skipping to change at page 40, line 10
see Section 4.4. A MAX_PUSH_ID frame cannot reduce the maximum Push see Section 4.4. A MAX_PUSH_ID frame cannot reduce the maximum Push
ID; receipt of a MAX_PUSH_ID frame that contains a smaller value than ID; receipt of a MAX_PUSH_ID frame that contains a smaller value than
previously received MUST be treated as a connection error of type previously received MUST be treated as a connection error of type
H3_ID_ERROR. H3_ID_ERROR.
7.2.8. Reserved Frame Types 7.2.8. Reserved Frame Types
Frame types of the format "0x1f * N + 0x21" for non-negative integer Frame types of the format "0x1f * N + 0x21" for non-negative integer
values of N are reserved to exercise the requirement that unknown values of N are reserved to exercise the requirement that unknown
types be ignored (Section 9). These frames have no semantics, and types be ignored (Section 9). These frames have no semantics, and
can be sent on any open stream when application-layer padding is MAY be sent on any stream where frames are allowed to be sent. This
desired. They MAY also be sent on connections where no data is enables their use for application-layer padding. Endpoints MUST NOT
currently being transferred. Endpoints MUST NOT consider these consider these frames to have any meaning upon receipt.
frames to have any meaning upon receipt.
The payload and length of the frames are selected in any manner the The payload and length of the frames are selected in any manner the
implementation chooses. implementation chooses.
Frame types that were used in HTTP/2 where there is no corresponding Frame types that were used in HTTP/2 where there is no corresponding
HTTP/3 frame have also been reserved (Section 11.2.1). These frame HTTP/3 frame have also been reserved (Section 11.2.1). These frame
types MUST NOT be sent, and their receipt MUST be treated as a types MUST NOT be sent, and their receipt MUST be treated as a
connection error of type H3_FRAME_UNEXPECTED. connection error of type H3_FRAME_UNEXPECTED.
8. Error Handling 8. Error Handling
skipping to change at page 40, line 22 skipping to change at page 40, line 49
H3_NO_ERROR. However, closing a stream can have other effects H3_NO_ERROR. However, closing a stream can have other effects
regardless of the error code; for example, see Section 4.1. regardless of the error code; for example, see Section 4.1.
This section describes HTTP/3-specific error codes that can be used This section describes HTTP/3-specific error codes that can be used
to express the cause of a connection or stream error. to express the cause of a connection or stream error.
8.1. HTTP/3 Error Codes 8.1. HTTP/3 Error Codes
The following error codes are defined for use when abruptly The following error codes are defined for use when abruptly
terminating streams, aborting reading of streams, or immediately terminating streams, aborting reading of streams, or immediately
closing connections. closing HTTP/3 connections.
H3_NO_ERROR (0x100): No error. This is used when the connection or H3_NO_ERROR (0x100): No error. This is used when the connection or
stream needs to be closed, but there is no error to signal. stream needs to be closed, but there is no error to signal.
H3_GENERAL_PROTOCOL_ERROR (0x101): Peer violated protocol H3_GENERAL_PROTOCOL_ERROR (0x101): Peer violated protocol
requirements in a way that does not match a more specific error requirements in a way that does not match a more specific error
code, or endpoint declines to use the more specific error code. code, or endpoint declines to use the more specific error code.
H3_INTERNAL_ERROR (0x102): An internal error has occurred in the H3_INTERNAL_ERROR (0x102): An internal error has occurred in the
HTTP stack. HTTP stack.
H3_STREAM_CREATION_ERROR (0x103): The endpoint detected that its H3_STREAM_CREATION_ERROR (0x103): The endpoint detected that its
peer created a stream that it will not accept. peer created a stream that it will not accept.
H3_CLOSED_CRITICAL_STREAM (0x104): A stream required by the H3_CLOSED_CRITICAL_STREAM (0x104): A stream required by the HTTP/3
connection was closed or reset. connection was closed or reset.
H3_FRAME_UNEXPECTED (0x105): A frame was received that was not H3_FRAME_UNEXPECTED (0x105): A frame was received that was not
permitted in the current state or on the current stream. permitted in the current state or on the current stream.
H3_FRAME_ERROR (0x106): A frame that fails to satisfy layout H3_FRAME_ERROR (0x106): A frame that fails to satisfy layout
requirements or with an invalid size was received. requirements or with an invalid size was received.
H3_EXCESSIVE_LOAD (0x107): The endpoint detected that its peer is H3_EXCESSIVE_LOAD (0x107): The endpoint detected that its peer is
exhibiting a behavior that might be generating excessive load. exhibiting a behavior that might be generating excessive load.
skipping to change at page 41, line 18 skipping to change at page 41, line 45
H3_REQUEST_REJECTED (0x10b): A server rejected a request without H3_REQUEST_REJECTED (0x10b): A server rejected a request without
performing any application processing. performing any application processing.
H3_REQUEST_CANCELLED (0x10c): The request or its response (including H3_REQUEST_CANCELLED (0x10c): The request or its response (including
pushed response) is cancelled. pushed response) is cancelled.
H3_REQUEST_INCOMPLETE (0x10d): The client's stream terminated H3_REQUEST_INCOMPLETE (0x10d): The client's stream terminated
without containing a fully-formed request. without containing a fully-formed request.
H3_CONNECT_ERROR (0x10f): The connection established in response to H3_CONNECT_ERROR (0x10f): The TCP connection established in response
a CONNECT request was reset or abnormally closed. to a CONNECT request was reset or abnormally closed.
H3_VERSION_FALLBACK (0x110): The requested operation cannot be H3_VERSION_FALLBACK (0x110): The requested operation cannot be
served over HTTP/3. The peer should retry over HTTP/1.1. served over HTTP/3. The peer should retry over HTTP/1.1.
Error codes of the format "0x1f * N + 0x21" for non-negative integer Error codes of the format "0x1f * N + 0x21" for non-negative integer
values of N are reserved to exercise the requirement that unknown values of N are reserved to exercise the requirement that unknown
error codes be treated as equivalent to H3_NO_ERROR (Section 9). error codes be treated as equivalent to H3_NO_ERROR (Section 9).
Implementations SHOULD select an error code from this space with some Implementations SHOULD select an error code from this space with some
probability when they would have sent H3_NO_ERROR. probability when they would have sent H3_NO_ERROR.
skipping to change at page 42, line 37 skipping to change at page 43, line 24
The security considerations of HTTP/3 should be comparable to those The security considerations of HTTP/3 should be comparable to those
of HTTP/2 with TLS. However, many of the considerations from of HTTP/2 with TLS. However, many of the considerations from
Section 10 of [HTTP2] apply to [QUIC-TRANSPORT] and are discussed in Section 10 of [HTTP2] apply to [QUIC-TRANSPORT] and are discussed in
that document. that document.
10.1. Server Authority 10.1. Server Authority
HTTP/3 relies on the HTTP definition of authority. The security HTTP/3 relies on the HTTP definition of authority. The security
considerations of establishing authority are discussed in considerations of establishing authority are discussed in
Section 12.1 of [SEMANTICS]. Section 16.1 of [SEMANTICS].
10.2. Cross-Protocol Attacks 10.2. Cross-Protocol Attacks
The use of ALPN in the TLS and QUIC handshakes establishes the target The use of ALPN in the TLS and QUIC handshakes establishes the target
application protocol before application-layer bytes are processed. application protocol before application-layer bytes are processed.
Because all QUIC packets are encrypted, it is difficult for an Because all QUIC packets are encrypted, it is difficult for an
attacker to control the plaintext bytes of an HTTP/3 connection, attacker to control the plaintext bytes of an HTTP/3 connection,
which could be used in a cross-protocol attack on a plaintext which could be used in a cross-protocol attack on a plaintext
protocol. protocol.
10.3. Intermediary Encapsulation Attacks 10.3. Intermediary Encapsulation Attacks
The HTTP/3 field encoding allows the expression of names that are not The HTTP/3 field encoding allows the expression of names that are not
valid field names in the syntax used by HTTP (Section 5.3 of valid field names in the syntax used by HTTP (Section 5.4.3 of
[SEMANTICS]). Requests or responses containing invalid field names [SEMANTICS]). Requests or responses containing invalid field names
MUST be treated as malformed (Section 4.1.3). An intermediary MUST be treated as malformed (Section 4.1.3). An intermediary
therefore cannot translate an HTTP/3 request or response containing therefore cannot translate an HTTP/3 request or response containing
an invalid field name into an HTTP/1.1 message. an invalid field name into an HTTP/1.1 message.
Similarly, HTTP/3 can transport field values that are not valid. Similarly, HTTP/3 can transport field values that are not valid.
While most values that can be encoded will not alter field parsing, While most values that can be encoded will not alter field parsing,
carriage return (CR, ASCII 0xd), line feed (LF, ASCII 0xa), and the carriage return (CR, ASCII 0xd), line feed (LF, ASCII 0xa), and the
zero character (NUL, ASCII 0x0) might be exploited by an attacker if zero character (NUL, ASCII 0x0) might be exploited by an attacker if
they are translated verbatim. Any request or response that contains they are translated verbatim. Any request or response that contains
a character not permitted in a field value MUST be treated as a character not permitted in a field value MUST be treated as
malformed (Section 4.1.3). Valid characters are defined by the malformed (Section 4.1.3). Valid characters are defined by the
"field-content" ABNF rule in Section 5.4 of [SEMANTICS]. "field-content" ABNF rule in Section 5.4.4 of [SEMANTICS].
10.4. Cacheability of Pushed Responses 10.4. Cacheability of Pushed Responses
Pushed responses do not have an explicit request from the client; the Pushed responses do not have an explicit request from the client; the
request is provided by the server in the PUSH_PROMISE frame. request is provided by the server in the PUSH_PROMISE frame.
Caching responses that are pushed is possible based on the guidance Caching responses that are pushed is possible based on the guidance
provided by the origin server in the Cache-Control header field. provided by the origin server in the Cache-Control header field.
However, this can cause issues if a single server hosts more than one However, this can cause issues if a single server hosts more than one
tenant. For example, a server might offer multiple users each a tenant. For example, a server might offer multiple users each a
skipping to change at page 44, line 52 skipping to change at page 45, line 33
correctness, mean that an endpoint likely needs to buffer the entire correctness, mean that an endpoint likely needs to buffer the entire
header field section. Since there is no hard limit to the size of a header field section. Since there is no hard limit to the size of a
field section, some endpoints could be forced to commit a large field section, some endpoints could be forced to commit a large
amount of available memory for header fields. amount of available memory for header fields.
An endpoint can use the SETTINGS_MAX_FIELD_SECTION_SIZE An endpoint can use the SETTINGS_MAX_FIELD_SECTION_SIZE
(Section 4.1.1.3) setting to advise peers of limits that might apply (Section 4.1.1.3) setting to advise peers of limits that might apply
on the size of field sections. This setting is only advisory, so on the size of field sections. This setting is only advisory, so
endpoints MAY choose to send field sections that exceed this limit endpoints MAY choose to send field sections that exceed this limit
and risk having the request or response being treated as malformed. and risk having the request or response being treated as malformed.
This setting is specific to a connection, so any request or response This setting is specific to an HTTP/3 connection, so any request or
could encounter a hop with a lower, unknown limit. An intermediary response could encounter a hop with a lower, unknown limit. An
can attempt to avoid this problem by passing on values presented by intermediary can attempt to avoid this problem by passing on values
different peers, but they are not obligated to do so. presented by different peers, but they are not obligated to do so.
A server that receives a larger field section than it is willing to A server that receives a larger field section than it is willing to
handle can send an HTTP 431 (Request Header Fields Too Large) status handle can send an HTTP 431 (Request Header Fields Too Large) status
code ([RFC6585]). A client can discard responses that it cannot code ([RFC6585]). A client can discard responses that it cannot
process. process.
10.5.2. CONNECT Issues 10.5.2. CONNECT Issues
The CONNECT method can be used to create disproportionate load on a The CONNECT method can be used to create disproportionate load on a
proxy, since stream creation is relatively inexpensive when compared proxy, since stream creation is relatively inexpensive when compared
skipping to change at page 45, line 30 skipping to change at page 46, line 11
TCP connection remains in the TIME_WAIT state. Therefore, a proxy TCP connection remains in the TIME_WAIT state. Therefore, a proxy
cannot rely on QUIC stream limits alone to control the resources cannot rely on QUIC stream limits alone to control the resources
consumed by CONNECT requests. consumed by CONNECT requests.
10.6. Use of Compression 10.6. Use of Compression
Compression can allow an attacker to recover secret data when it is Compression can allow an attacker to recover secret data when it is
compressed in the same context as data under attacker control. compressed in the same context as data under attacker control.
HTTP/3 enables compression of fields (Section 4.1.1); the following HTTP/3 enables compression of fields (Section 4.1.1); the following
concerns also apply to the use of HTTP compressed content-codings; concerns also apply to the use of HTTP compressed content-codings;
see Section 7.1.2 of [SEMANTICS]. see Section 7.5.1 of [SEMANTICS].
There are demonstrable attacks on compression that exploit the There are demonstrable attacks on compression that exploit the
characteristics of the web (e.g., [BREACH]). The attacker induces characteristics of the web (e.g., [BREACH]). The attacker induces
multiple requests containing varying plaintext, observing the length multiple requests containing varying plaintext, observing the length
of the resulting ciphertext in each, which reveals a shorter length of the resulting ciphertext in each, which reveals a shorter length
when a guess about the secret is correct. when a guess about the secret is correct.
Implementations communicating on a secure channel MUST NOT compress Implementations communicating on a secure channel MUST NOT compress
content that includes both confidential and attacker-controlled data content that includes both confidential and attacker-controlled data
unless separate compression contexts are used for each source of unless separate compression contexts are used for each source of
skipping to change at page 46, line 20 skipping to change at page 46, line 43
plaintext and secret data (e.g., [BREACH]). plaintext and secret data (e.g., [BREACH]).
Where HTTP/2 employs PADDING frames and Padding fields in other Where HTTP/2 employs PADDING frames and Padding fields in other
frames to make a connection more resistant to traffic analysis, frames to make a connection more resistant to traffic analysis,
HTTP/3 can either rely on transport-layer padding or employ the HTTP/3 can either rely on transport-layer padding or employ the
reserved frame and stream types discussed in Section 7.2.8 and reserved frame and stream types discussed in Section 7.2.8 and
Section 6.2.3. These methods of padding produce different results in Section 6.2.3. These methods of padding produce different results in
terms of the granularity of padding, how padding is arranged in terms of the granularity of padding, how padding is arranged in
relation to the information that is being protected, whether padding relation to the information that is being protected, whether padding
is applied in the case of packet loss, and how an implementation is applied in the case of packet loss, and how an implementation
might control padding. Redundant padding could even be might control padding.
counterproductive.
Reserved stream types can be used to give the appearance of sending
traffic even when the connection is idle. Because HTTP traffic often
occurs in bursts, apparent traffic can be used to obscure the timing
or duration of such bursts, even to the point of appearing to send a
constant stream of data. However, as such traffic is still flow
controlled by the receiver, a failure to promptly drain such streams
and provide additional flow control credit can limit the sender's
ability to send real traffic.
To mitigate attacks that rely on compression, disabling or limiting To mitigate attacks that rely on compression, disabling or limiting
compression might be preferable to padding as a countermeasure. compression might be preferable to padding as a countermeasure.
Use of padding can result in less protection than might seem Use of padding can result in less protection than might seem
immediately obvious. At best, padding only makes it more difficult immediately obvious. Redundant padding could even be
for an attacker to infer length information by increasing the number counterproductive. At best, padding only makes it more difficult for
of frames an attacker has to observe. Incorrectly implemented an attacker to infer length information by increasing the number of
padding schemes can be easily defeated. In particular, randomized frames an attacker has to observe. Incorrectly implemented padding
padding with a predictable distribution provides very little schemes can be easily defeated. In particular, randomized padding
protection; similarly, padding payloads to a fixed size exposes with a predictable distribution provides very little protection;
information as payload sizes cross the fixed-sized boundary, which similarly, padding payloads to a fixed size exposes information as
could be possible if an attacker can control plaintext. payload sizes cross the fixed-sized boundary, which could be possible
if an attacker can control plaintext.
10.8. Frame Parsing 10.8. Frame Parsing
Several protocol elements contain nested length elements, typically Several protocol elements contain nested length elements, typically
in the form of frames with an explicit length containing variable- in the form of frames with an explicit length containing variable-
length integers. This could pose a security risk to an incautious length integers. This could pose a security risk to an incautious
implementer. An implementation MUST ensure that the length of a implementer. An implementation MUST ensure that the length of a
frame exactly matches the length of the fields it contains. frame exactly matches the length of the fields it contains.
10.9. Early Data 10.9. Early Data
skipping to change at page 48, line 13 skipping to change at page 48, line 42
Specification: This document Specification: This document
11.2. New Registries 11.2. New Registries
New registries created in this document operate under the QUIC New registries created in this document operate under the QUIC
registration policy documented in Section 22.1 of [QUIC-TRANSPORT]. registration policy documented in Section 22.1 of [QUIC-TRANSPORT].
These registries all include the common set of fields listed in These registries all include the common set of fields listed in
Section 22.1.1 of [QUIC-TRANSPORT]. Section 22.1.1 of [QUIC-TRANSPORT].
The initial allocations in these registries created in this document The initial allocations in these registries created in this document
are all assigned permanent status and list as contact both the IESG are all assigned permanent status and list a change controller of the
(iesg@ietf.org) and the HTTP working group (ietf-http-wg@w3.org). IETF and a contact of the HTTP working group (ietf-http-wg@w3.org).
11.2.1. Frame Types 11.2.1. Frame Types
This document establishes a registry for HTTP/3 frame type codes. This document establishes a registry for HTTP/3 frame type codes.
The "HTTP/3 Frame Type" registry governs a 62-bit space. This The "HTTP/3 Frame Type" registry governs a 62-bit space. This
registry follows the QUIC registry policy; see Section 11.2. registry follows the QUIC registry policy; see Section 11.2.
Permanent registrations in this registry are assigned using the Permanent registrations in this registry are assigned using the
Specification Required policy ([RFC8126]), except for values between Specification Required policy ([RFC8126]), except for values between
0x00 and 0x3f (in hexadecimal; inclusive), which are assigned using 0x00 and 0x3f (in hexadecimal; inclusive), which are assigned using
Standards Action or IESG Approval as defined in Section 4.9 and 4.10 Standards Action or IESG Approval as defined in Section 4.9 and 4.10
skipping to change at page 51, line 4 skipping to change at page 51, line 24
registrations in this registry are assigned using the Specification registrations in this registry are assigned using the Specification
Required policy ([RFC8126]), except for values between 0x00 and 0x3f Required policy ([RFC8126]), except for values between 0x00 and 0x3f
(in hexadecimal; inclusive), which are assigned using Standards (in hexadecimal; inclusive), which are assigned using Standards
Action or IESG Approval as defined in Section 4.9 and 4.10 of Action or IESG Approval as defined in Section 4.9 and 4.10 of
[RFC8126]. [RFC8126].
Registrations for error codes are required to include a description Registrations for error codes are required to include a description
of the error code. An expert reviewer is advised to examine new of the error code. An expert reviewer is advised to examine new
registrations for possible duplication with existing error codes. registrations for possible duplication with existing error codes.
Use of existing registrations is to be encouraged, but not mandated. Use of existing registrations is to be encouraged, but not mandated.
Use of values that are registered in the "HTTP/2 Error Code" registry
is discouraged.
In addition to common fields as described in Section 11.2, this In addition to common fields as described in Section 11.2, this
registry includes two additional fields. Permanent registrations in registry includes two additional fields. Permanent registrations in
this registry MUST include the following field: this registry MUST include the following field:
Name: A name for the error code. Name: A name for the error code.
Description: A brief description of the error code semantics. Description: A brief description of the error code semantics.
The entries in Table 4 are registered by this document. The entries in Table 4 are registered by this document. These error
codes were selected from the range that operates on a Specification
Required policy to avoid collisions with HTTP/2 error codes.
+===========================+========+==============+===============+ +===========================+========+==============+===============+
| Name | Value | Description | Specification | | Name | Value | Description | Specification |
+===========================+========+==============+===============+ +===========================+========+==============+===============+
| H3_NO_ERROR | 0x0100 | No error | Section 8.1 | | H3_NO_ERROR | 0x0100 | No error | Section 8.1 |
+---------------------------+--------+--------------+---------------+ +---------------------------+--------+--------------+---------------+
| H3_GENERAL_PROTOCOL_ERROR | 0x0101 | General | Section 8.1 | | H3_GENERAL_PROTOCOL_ERROR | 0x0101 | General | Section 8.1 |
| | | protocol | | | | | protocol | |
| | | error | | | | | error | |
+---------------------------+--------+--------------+---------------+ +---------------------------+--------+--------------+---------------+
skipping to change at page 53, line 21 skipping to change at page 53, line 35
Specification Required policy ([RFC8126]), except for values between Specification Required policy ([RFC8126]), except for values between
0x00 and 0x3f (in hexadecimal; inclusive), which are assigned using 0x00 and 0x3f (in hexadecimal; inclusive), which are assigned using
Standards Action or IESG Approval as defined in Section 4.9 and 4.10 Standards Action or IESG Approval as defined in Section 4.9 and 4.10
of [RFC8126]. of [RFC8126].
In addition to common fields as described in Section 11.2, permanent In addition to common fields as described in Section 11.2, permanent
registrations in this registry MUST include the following fields: registrations in this registry MUST include the following fields:
Stream Type: A name or label for the stream type. Stream Type: A name or label for the stream type.
Sender: Which endpoint on a connection may initiate a stream of this Sender: Which endpoint on an HTTP/3 connection may initiate a stream
type. Values are "Client", "Server", or "Both". of this type. Values are "Client", "Server", or "Both".
Specifications for permanent registrations MUST include a description Specifications for permanent registrations MUST include a description
of the stream type, including the layout and semantics of the stream of the stream type, including the layout and semantics of the stream
contents. contents.
The entries in the following table are registered by this document. The entries in the following table are registered by this document.
+================+=======+===============+========+ +================+=======+===============+========+
| Stream Type | Value | Specification | Sender | | Stream Type | Value | Specification | Sender |
+================+=======+===============+========+ +================+=======+===============+========+
skipping to change at page 54, line 7 skipping to change at page 54, line 29
12. References 12. References
12.1. Normative References 12.1. Normative References
[ALTSVC] Nottingham, M., McManus, P., and J. Reschke, "HTTP [ALTSVC] Nottingham, M., McManus, P., and J. Reschke, "HTTP
Alternative Services", RFC 7838, DOI 10.17487/RFC7838, Alternative Services", RFC 7838, DOI 10.17487/RFC7838,
April 2016, <https://www.rfc-editor.org/info/rfc7838>. April 2016, <https://www.rfc-editor.org/info/rfc7838>.
[CACHING] Fielding, R., Nottingham, M., and J. Reschke, "HTTP [CACHING] Fielding, R., Nottingham, M., and J. Reschke, "HTTP
Caching", Work in Progress, Internet-Draft, draft-ietf- Caching", Work in Progress, Internet-Draft, draft-ietf-
httpbis-cache-11, 27 August 2020, <http://www.ietf.org/ httpbis-cache-12, 2 October 2020, <http://www.ietf.org/
internet-drafts/draft-ietf-httpbis-cache-11.txt>. internet-drafts/draft-ietf-httpbis-cache-12.txt>.
[HTTP-REPLAY] [HTTP-REPLAY]
Thomson, M., Nottingham, M., and W. Tarreau, "Using Early Thomson, M., Nottingham, M., and W. Tarreau, "Using Early
Data in HTTP", RFC 8470, DOI 10.17487/RFC8470, September Data in HTTP", RFC 8470, DOI 10.17487/RFC8470, September
2018, <https://www.rfc-editor.org/info/rfc8470>. 2018, <https://www.rfc-editor.org/info/rfc8470>.
[QPACK] Krasic, C., Bishop, M., and A. Frindell, Ed., "QPACK: [QPACK] Krasic, C., Bishop, M., and A. Frindell, Ed., "QPACK:
Header Compression for HTTP over QUIC", Work in Progress, Header Compression for HTTP over QUIC", Work in Progress,
Internet-Draft, draft-ietf-quic-qpack-18, 25 September Internet-Draft, draft-ietf-quic-qpack-19, 20 October 2020,
2020, <https://tools.ietf.org/html/draft-ietf-quic-qpack-19>.
<https://tools.ietf.org/html/draft-ietf-quic-qpack-18>.
[QUIC-TRANSPORT] [QUIC-TRANSPORT]
Iyengar, J., Ed. and M. Thomson, Ed., "QUIC: A UDP-Based Iyengar, J., Ed. and M. Thomson, Ed., "QUIC: A UDP-Based
Multiplexed and Secure Transport", Work in Progress, Multiplexed and Secure Transport", Work in Progress,
Internet-Draft, draft-ietf-quic-transport-31, 25 September Internet-Draft, draft-ietf-quic-transport-31, 20 October
2020, <https://tools.ietf.org/html/draft-ietf-quic- 2020, <https://tools.ietf.org/html/draft-ietf-quic-
transport-31>. transport-31>.
[RFC0793] Postel, J., "Transmission Control Protocol", STD 7, [RFC0793] Postel, J., "Transmission Control Protocol", STD 7,
RFC 793, DOI 10.17487/RFC0793, September 1981, RFC 793, DOI 10.17487/RFC0793, September 1981,
<https://www.rfc-editor.org/info/rfc793>. <https://www.rfc-editor.org/info/rfc793>.
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, Requirement Levels", BCP 14, RFC 2119,
DOI 10.17487/RFC2119, March 1997, DOI 10.17487/RFC2119, March 1997,
skipping to change at page 55, line 15 skipping to change at page 55, line 36
[RFC7301] Friedl, S., Popov, A., Langley, A., and E. Stephan, [RFC7301] Friedl, S., Popov, A., Langley, A., and E. Stephan,
"Transport Layer Security (TLS) Application-Layer Protocol "Transport Layer Security (TLS) Application-Layer Protocol
Negotiation Extension", RFC 7301, DOI 10.17487/RFC7301, Negotiation Extension", RFC 7301, DOI 10.17487/RFC7301,
July 2014, <https://www.rfc-editor.org/info/rfc7301>. July 2014, <https://www.rfc-editor.org/info/rfc7301>.
[RFC8126] Cotton, M., Leiba, B., and T. Narten, "Guidelines for [RFC8126] Cotton, M., Leiba, B., and T. Narten, "Guidelines for
Writing an IANA Considerations Section in RFCs", BCP 26, Writing an IANA Considerations Section in RFCs", BCP 26,
RFC 8126, DOI 10.17487/RFC8126, June 2017, RFC 8126, DOI 10.17487/RFC8126, June 2017,
<https://www.rfc-editor.org/info/rfc8126>. <https://www.rfc-editor.org/info/rfc8126>.
[RFC8164] Nottingham, M. and M. Thomson, "Opportunistic Security for
HTTP/2", RFC 8164, DOI 10.17487/RFC8164, May 2017,
<https://www.rfc-editor.org/info/rfc8164>.
[RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC [RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC
2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174, 2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174,
May 2017, <https://www.rfc-editor.org/info/rfc8174>. May 2017, <https://www.rfc-editor.org/info/rfc8174>.
[SEMANTICS] [SEMANTICS]
Fielding, R., Nottingham, M., and J. Reschke, "HTTP Fielding, R., Nottingham, M., and J. Reschke, "HTTP
Semantics", Work in Progress, Internet-Draft, draft-ietf- Semantics", Work in Progress, Internet-Draft, draft-ietf-
httpbis-semantics-11, 27 August 2020, httpbis-semantics-12, 2 October 2020,
<http://www.ietf.org/internet-drafts/draft-ietf-httpbis- <http://www.ietf.org/internet-drafts/draft-ietf-httpbis-
semantics-11.txt>. semantics-12.txt>.
[URI] Berners-Lee, T., Fielding, R., and L. Masinter, "Uniform [URI] Berners-Lee, T., Fielding, R., and L. Masinter, "Uniform
Resource Identifier (URI): Generic Syntax", STD 66, Resource Identifier (URI): Generic Syntax", STD 66,
RFC 3986, DOI 10.17487/RFC3986, January 2005, RFC 3986, DOI 10.17487/RFC3986, January 2005,
<https://www.rfc-editor.org/info/rfc3986>. <https://www.rfc-editor.org/info/rfc3986>.
12.2. Informative References 12.2. Informative References
[BREACH] Gluck, Y., Harris, N., and A. Prado, "BREACH: Reviving the [BREACH] Gluck, Y., Harris, N., and A. Prado, "BREACH: Reviving the
CRIME Attack", July 2013, CRIME Attack", July 2013,
<http://breachattack.com/resources/ <http://breachattack.com/resources/
BREACH%20-%20SSL,%20gone%20in%2030%20seconds.pdf>. BREACH%20-%20SSL,%20gone%20in%2030%20seconds.pdf>.
[HPACK] Peon, R. and H. Ruellan, "HPACK: Header Compression for [HPACK] Peon, R. and H. Ruellan, "HPACK: Header Compression for
HTTP/2", RFC 7541, DOI 10.17487/RFC7541, May 2015, HTTP/2", RFC 7541, DOI 10.17487/RFC7541, May 2015,
<https://www.rfc-editor.org/info/rfc7541>. <https://www.rfc-editor.org/info/rfc7541>.
[HTTP11] Fielding, R., Nottingham, M., and J. Reschke, "HTTP/1.1 [HTTP11] Fielding, R., Nottingham, M., and J. Reschke, "HTTP/1.1
Messaging", Work in Progress, Internet-Draft, draft-ietf- Messaging", Work in Progress, Internet-Draft, draft-ietf-
httpbis-messaging-11, 27 August 2020, httpbis-messaging-12, 2 October 2020,
<http://www.ietf.org/internet-drafts/draft-ietf-httpbis- <http://www.ietf.org/internet-drafts/draft-ietf-httpbis-
messaging-11.txt>. messaging-12.txt>.
[HTTP2] Belshe, M., Peon, R., and M. Thomson, Ed., "Hypertext [HTTP2] Belshe, M., Peon, R., and M. Thomson, Ed., "Hypertext
Transfer Protocol Version 2 (HTTP/2)", RFC 7540, Transfer Protocol Version 2 (HTTP/2)", RFC 7540,
DOI 10.17487/RFC7540, May 2015, DOI 10.17487/RFC7540, May 2015,
<https://www.rfc-editor.org/info/rfc7540>. <https://www.rfc-editor.org/info/rfc7540>.
[RFC6585] Nottingham, M. and R. Fielding, "Additional HTTP Status [RFC6585] Nottingham, M. and R. Fielding, "Additional HTTP Status
Codes", RFC 6585, DOI 10.17487/RFC6585, April 2012, Codes", RFC 6585, DOI 10.17487/RFC6585, April 2012,
<https://www.rfc-editor.org/info/rfc6585>. <https://www.rfc-editor.org/info/rfc6585>.
[RFC8164] Nottingham, M. and M. Thomson, "Opportunistic Security for
HTTP/2", RFC 8164, DOI 10.17487/RFC8164, May 2017,
<https://www.rfc-editor.org/info/rfc8164>.
[TFO] Cheng, Y., Chu, J., Radhakrishnan, S., and A. Jain, "TCP [TFO] Cheng, Y., Chu, J., Radhakrishnan, S., and A. Jain, "TCP
Fast Open", RFC 7413, DOI 10.17487/RFC7413, December 2014, Fast Open", RFC 7413, DOI 10.17487/RFC7413, December 2014,
<https://www.rfc-editor.org/info/rfc7413>. <https://www.rfc-editor.org/info/rfc7413>.
[TLS13] Rescorla, E., "The Transport Layer Security (TLS) Protocol [TLS13] Rescorla, E., "The Transport Layer Security (TLS) Protocol
Version 1.3", RFC 8446, DOI 10.17487/RFC8446, August 2018, Version 1.3", RFC 8446, DOI 10.17487/RFC8446, August 2018,
<https://www.rfc-editor.org/info/rfc8446>. <https://www.rfc-editor.org/info/rfc8446>.
Appendix A. Considerations for Transitioning from HTTP/2 Appendix A. Considerations for Transitioning from HTTP/2
skipping to change at page 62, line 51 skipping to change at page 63, line 26
take the action it deems most appropriate. In the reverse direction, take the action it deems most appropriate. In the reverse direction,
the intermediary might deem it beneficial to pass on client request the intermediary might deem it beneficial to pass on client request
cancellations that are indicated by terminating a stream with cancellations that are indicated by terminating a stream with
H3_REQUEST_CANCELLED; see Section 4.1.2. H3_REQUEST_CANCELLED; see Section 4.1.2.
Conversion between errors is described in the logical mapping. The Conversion between errors is described in the logical mapping. The
error codes are defined in non-overlapping spaces in order to protect error codes are defined in non-overlapping spaces in order to protect
against accidental conversion that could result in the use of against accidental conversion that could result in the use of
inappropriate or unknown error codes for the target version. An inappropriate or unknown error codes for the target version. An
intermediary is permitted to promote stream errors to connection intermediary is permitted to promote stream errors to connection
errors but they should be aware of the cost to the connection for errors but they should be aware of the cost to the HTTP/3 connection
what might be a temporary or intermittent error. for what might be a temporary or intermittent error.
Appendix B. Change Log Appendix B. Change Log
*RFC Editor's Note:* Please remove this section prior to *RFC Editor's Note:* Please remove this section prior to
publication of a final version of this document. publication of a final version of this document.
B.1. Since draft-ietf-quic-http-30 B.1. Since draft-ietf-quic-http-31
Editorial changes only. Editorial changes only.
B.2. Since draft-ietf-quic-http-29 B.2. Since draft-ietf-quic-http-30
Editorial changes only.
B.3. Since draft-ietf-quic-http-29
* Require a connection error if a reserved frame type that * Require a connection error if a reserved frame type that
corresponds to a frame in HTTP/2 is received (#3991, #3993) corresponds to a frame in HTTP/2 is received (#3991, #3993)
* Require a connection error if a reserved setting that corresponds * Require a connection error if a reserved setting that corresponds
to a setting in HTTP/2 is received (#3954, #3955) to a setting in HTTP/2 is received (#3954, #3955)
B.3. Since draft-ietf-quic-http-28 B.4. Since draft-ietf-quic-http-28
* CANCEL_PUSH is recommended even when the stream is reset (#3698, * CANCEL_PUSH is recommended even when the stream is reset (#3698,
#3700) #3700)
* Use H3_ID_ERROR when GOAWAY contains a larger identifier (#3631, * Use H3_ID_ERROR when GOAWAY contains a larger identifier (#3631,
#3634) #3634)
B.4. Since draft-ietf-quic-http-27 B.5. Since draft-ietf-quic-http-27
* Updated text to refer to latest HTTP revisions * Updated text to refer to latest HTTP revisions
* Use the HTTP definition of authority for establishing and * Use the HTTP definition of authority for establishing and
coalescing connections (#253, #2223, #3558) coalescing connections (#253, #2223, #3558)
* Define use of GOAWAY from both endpoints (#2632, #3129) * Define use of GOAWAY from both endpoints (#2632, #3129)
* Require either :authority or Host if the URI scheme has a * Require either :authority or Host if the URI scheme has a
mandatory authority component (#3408, #3475) mandatory authority component (#3408, #3475)
B.5. Since draft-ietf-quic-http-26 B.6. Since draft-ietf-quic-http-26
* No changes * No changes
B.6. Since draft-ietf-quic-http-25 B.7. Since draft-ietf-quic-http-25
* Require QUICv1 for HTTP/3 (#3117, #3323) * Require QUICv1 for HTTP/3 (#3117, #3323)
* Remove DUPLICATE_PUSH and allow duplicate PUSH_PROMISE (#3275, * Remove DUPLICATE_PUSH and allow duplicate PUSH_PROMISE (#3275,
#3309) #3309)
* Clarify the definition of "malformed" (#3352, #3345) * Clarify the definition of "malformed" (#3352, #3345)
B.7. Since draft-ietf-quic-http-24 B.8. Since draft-ietf-quic-http-24
* Removed H3_EARLY_RESPONSE error code; H3_NO_ERROR is recommended * Removed H3_EARLY_RESPONSE error code; H3_NO_ERROR is recommended
instead (#3130,#3208) instead (#3130,#3208)
* Unknown error codes are equivalent to H3_NO_ERROR (#3276,#3331) * Unknown error codes are equivalent to H3_NO_ERROR (#3276,#3331)
* Some error codes are reserved for greasing (#3325,#3360) * Some error codes are reserved for greasing (#3325,#3360)
B.8. Since draft-ietf-quic-http-23 B.9. Since draft-ietf-quic-http-23
* Removed "quic" Alt-Svc parameter (#3061,#3118) * Removed "quic" Alt-Svc parameter (#3061,#3118)
* Clients need not persist unknown settings for use in 0-RTT * Clients need not persist unknown settings for use in 0-RTT
(#3110,#3113) (#3110,#3113)
* Clarify error cases around CANCEL_PUSH (#2819,#3083) * Clarify error cases around CANCEL_PUSH (#2819,#3083)
B.9. Since draft-ietf-quic-http-22 B.10. Since draft-ietf-quic-http-22
* Removed priority signaling (#2922,#2924) * Removed priority signaling (#2922,#2924)
* Further changes to error codes (#2662,#2551): * Further changes to error codes (#2662,#2551):
- Error codes renumbered - Error codes renumbered
- HTTP_MALFORMED_FRAME replaced by HTTP_FRAME_ERROR, - HTTP_MALFORMED_FRAME replaced by HTTP_FRAME_ERROR,
HTTP_ID_ERROR, and others HTTP_ID_ERROR, and others
skipping to change at page 65, line 20 skipping to change at page 65, line 47
* Clarify that Upgrade and the 101 status code are prohibited * Clarify that Upgrade and the 101 status code are prohibited
(#2898,#2889) (#2898,#2889)
* Clarify that frame types reserved for greasing can occur on any * Clarify that frame types reserved for greasing can occur on any
stream, but frame types reserved due to HTTP/2 correspondence are stream, but frame types reserved due to HTTP/2 correspondence are
prohibited (#2997,#2692,#2693) prohibited (#2997,#2692,#2693)
* Unknown error codes cannot be treated as errors (#2998,#2816) * Unknown error codes cannot be treated as errors (#2998,#2816)
B.10. Since draft-ietf-quic-http-21 B.11. Since draft-ietf-quic-http-21
No changes No changes
B.11. Since draft-ietf-quic-http-20 B.12. Since draft-ietf-quic-http-20
* Prohibit closing the control stream (#2509, #2666) * Prohibit closing the control stream (#2509, #2666)
* Change default priority to use an orphan node (#2502, #2690) * Change default priority to use an orphan node (#2502, #2690)
* Exclusive priorities are restored (#2754, #2781) * Exclusive priorities are restored (#2754, #2781)
* Restrict use of frames when using CONNECT (#2229, #2702) * Restrict use of frames when using CONNECT (#2229, #2702)
* Close and maybe reset streams if a connection error occurs for * Close and maybe reset streams if a connection error occurs for
CONNECT (#2228, #2703) CONNECT (#2228, #2703)
skipping to change at page 66, line 19 skipping to change at page 66, line 45
- Specified error code for receiving DATA before HEADERS (#2715) - Specified error code for receiving DATA before HEADERS (#2715)
- Describe malformed messages and their handling (#2410, #2764) - Describe malformed messages and their handling (#2410, #2764)
- Remove HTTP_PUSH_ALREADY_IN_CACHE error (#2812, #2813) - Remove HTTP_PUSH_ALREADY_IN_CACHE error (#2812, #2813)
- Refactor Push ID related errors (#2818, #2820) - Refactor Push ID related errors (#2818, #2820)
- Rationalize HTTP/3 stream creation errors (#2821, #2822) - Rationalize HTTP/3 stream creation errors (#2821, #2822)
B.12. Since draft-ietf-quic-http-19 B.13. Since draft-ietf-quic-http-19
* SETTINGS_NUM_PLACEHOLDERS is 0x9 (#2443,#2530) * SETTINGS_NUM_PLACEHOLDERS is 0x9 (#2443,#2530)
* Non-zero bits in the Empty field of the PRIORITY frame MAY be * Non-zero bits in the Empty field of the PRIORITY frame MAY be
treated as an error (#2501) treated as an error (#2501)
B.13. Since draft-ietf-quic-http-18 B.14. Since draft-ietf-quic-http-18
* Resetting streams following a GOAWAY is recommended, but not * Resetting streams following a GOAWAY is recommended, but not
required (#2256,#2457) required (#2256,#2457)
* Use variable-length integers throughout (#2437,#2233,#2253,#2275) * Use variable-length integers throughout (#2437,#2233,#2253,#2275)
- Variable-length frame types, stream types, and settings - Variable-length frame types, stream types, and settings
identifiers identifiers
- Renumbered stream type assignments - Renumbered stream type assignments
- Modified associated reserved values - Modified associated reserved values
* Frame layout switched from Length-Type-Value to Type-Length-Value * Frame layout switched from Length-Type-Value to Type-Length-Value
(#2395,#2235) (#2395,#2235)
* Specified error code for servers receiving DUPLICATE_PUSH (#2497) * Specified error code for servers receiving DUPLICATE_PUSH (#2497)
* Use connection error for invalid PRIORITY (#2507, #2508) * Use connection error for invalid PRIORITY (#2507, #2508)
B.14. Since draft-ietf-quic-http-17 B.15. Since draft-ietf-quic-http-17
* HTTP_REQUEST_REJECTED is used to indicate a request can be retried * HTTP_REQUEST_REJECTED is used to indicate a request can be retried
(#2106, #2325) (#2106, #2325)
* Changed error code for GOAWAY on the wrong stream (#2231, #2343) * Changed error code for GOAWAY on the wrong stream (#2231, #2343)
B.15. Since draft-ietf-quic-http-16 B.16. Since draft-ietf-quic-http-16
* Rename "HTTP/QUIC" to "HTTP/3" (#1973) * Rename "HTTP/QUIC" to "HTTP/3" (#1973)
* Changes to PRIORITY frame (#1865, #2075) * Changes to PRIORITY frame (#1865, #2075)
- Permitted as first frame of request streams - Permitted as first frame of request streams
- Remove exclusive reprioritization - Remove exclusive reprioritization
- Changes to Prioritized Element Type bits - Changes to Prioritized Element Type bits
skipping to change at page 67, line 31 skipping to change at page 68, line 10
(#1809, #1846, #2038) (#1809, #1846, #2038)
* Clarify message processing rules for streams that aren't closed * Clarify message processing rules for streams that aren't closed
(#1972, #2003) (#1972, #2003)
* Removed reservation of error code 0 and moved HTTP_NO_ERROR to * Removed reservation of error code 0 and moved HTTP_NO_ERROR to
this value (#1922) this value (#1922)
* Removed prohibition of zero-length DATA frames (#2098) * Removed prohibition of zero-length DATA frames (#2098)
B.16. Since draft-ietf-quic-http-15 B.17. Since draft-ietf-quic-http-15
Substantial editorial reorganization; no technical changes. Substantial editorial reorganization; no technical changes.
B.17. Since draft-ietf-quic-http-14 B.18. Since draft-ietf-quic-http-14
* Recommend sensible values for QUIC transport parameters * Recommend sensible values for QUIC transport parameters
(#1720,#1806) (#1720,#1806)
* Define error for missing SETTINGS frame (#1697,#1808) * Define error for missing SETTINGS frame (#1697,#1808)
* Setting values are variable-length integers (#1556,#1807) and do * Setting values are variable-length integers (#1556,#1807) and do
not have separate maximum values (#1820) not have separate maximum values (#1820)
* Expanded discussion of connection closure (#1599,#1717,#1712) * Expanded discussion of connection closure (#1599,#1717,#1712)
* HTTP_VERSION_FALLBACK falls back to HTTP/1.1 (#1677,#1685) * HTTP_VERSION_FALLBACK falls back to HTTP/1.1 (#1677,#1685)
B.18. Since draft-ietf-quic-http-13 B.19. Since draft-ietf-quic-http-13
* Reserved some frame types for grease (#1333, #1446) * Reserved some frame types for grease (#1333, #1446)
* Unknown unidirectional stream types are tolerated, not errors; * Unknown unidirectional stream types are tolerated, not errors;
some reserved for grease (#1490, #1525) some reserved for grease (#1490, #1525)
* Require settings to be remembered for 0-RTT, prohibit reductions * Require settings to be remembered for 0-RTT, prohibit reductions
(#1541, #1641) (#1541, #1641)
* Specify behavior for truncated requests (#1596, #1643) * Specify behavior for truncated requests (#1596, #1643)
B.19. Since draft-ietf-quic-http-12 B.20. Since draft-ietf-quic-http-12
* TLS SNI extension isn't mandatory if an alternative method is used * TLS SNI extension isn't mandatory if an alternative method is used
(#1459, #1462, #1466) (#1459, #1462, #1466)
* Removed flags from HTTP/3 frames (#1388, #1398) * Removed flags from HTTP/3 frames (#1388, #1398)
* Reserved frame types and settings for use in preserving * Reserved frame types and settings for use in preserving
extensibility (#1333, #1446) extensibility (#1333, #1446)
* Added general error code (#1391, #1397) * Added general error code (#1391, #1397)
skipping to change at page 68, line 23 skipping to change at page 69, line 4
* TLS SNI extension isn't mandatory if an alternative method is used * TLS SNI extension isn't mandatory if an alternative method is used
(#1459, #1462, #1466) (#1459, #1462, #1466)
* Removed flags from HTTP/3 frames (#1388, #1398) * Removed flags from HTTP/3 frames (#1388, #1398)
* Reserved frame types and settings for use in preserving * Reserved frame types and settings for use in preserving
extensibility (#1333, #1446) extensibility (#1333, #1446)
* Added general error code (#1391, #1397) * Added general error code (#1391, #1397)
* Unidirectional streams carry a type byte and are extensible * Unidirectional streams carry a type byte and are extensible
(#910,#1359) (#910,#1359)
* Priority mechanism now uses explicit placeholders to enable * Priority mechanism now uses explicit placeholders to enable
persistent structure in the tree (#441,#1421,#1422) persistent structure in the tree (#441,#1421,#1422)
B.20. Since draft-ietf-quic-http-11 B.21. Since draft-ietf-quic-http-11
* Moved QPACK table updates and acknowledgments to dedicated streams * Moved QPACK table updates and acknowledgments to dedicated streams
(#1121, #1122, #1238) (#1121, #1122, #1238)
B.21. Since draft-ietf-quic-http-10 B.22. Since draft-ietf-quic-http-10
* Settings need to be remembered when attempting and accepting 0-RTT * Settings need to be remembered when attempting and accepting 0-RTT
(#1157, #1207) (#1157, #1207)
B.22. Since draft-ietf-quic-http-09 B.23. Since draft-ietf-quic-http-09
* Selected QCRAM for header compression (#228, #1117) * Selected QCRAM for header compression (#228, #1117)
* The server_name TLS extension is now mandatory (#296, #495) * The server_name TLS extension is now mandatory (#296, #495)
* Specified handling of unsupported versions in Alt-Svc (#1093, * Specified handling of unsupported versions in Alt-Svc (#1093,
#1097) #1097)
B.23. Since draft-ietf-quic-http-08 B.24. Since draft-ietf-quic-http-08
* Clarified connection coalescing rules (#940, #1024) * Clarified connection coalescing rules (#940, #1024)
B.24. Since draft-ietf-quic-http-07 B.25. Since draft-ietf-quic-http-07
* Changes for integer encodings in QUIC (#595,#905) * Changes for integer encodings in QUIC (#595,#905)
* Use unidirectional streams as appropriate (#515, #240, #281, #886) * Use unidirectional streams as appropriate (#515, #240, #281, #886)
* Improvement to the description of GOAWAY (#604, #898) * Improvement to the description of GOAWAY (#604, #898)
* Improve description of server push usage (#947, #950, #957) * Improve description of server push usage (#947, #950, #957)
B.25. Since draft-ietf-quic-http-06 B.26. Since draft-ietf-quic-http-06
* Track changes in QUIC error code usage (#485) * Track changes in QUIC error code usage (#485)
B.26. Since draft-ietf-quic-http-05 B.27. Since draft-ietf-quic-http-05
* Made push ID sequential, add MAX_PUSH_ID, remove * Made push ID sequential, add MAX_PUSH_ID, remove
SETTINGS_ENABLE_PUSH (#709) SETTINGS_ENABLE_PUSH (#709)
* Guidance about keep-alive and QUIC PINGs (#729) * Guidance about keep-alive and QUIC PINGs (#729)
* Expanded text on GOAWAY and cancellation (#757) * Expanded text on GOAWAY and cancellation (#757)
B.27. Since draft-ietf-quic-http-04 B.28. Since draft-ietf-quic-http-04
* Cite RFC 5234 (#404) * Cite RFC 5234 (#404)
* Return to a single stream per request (#245,#557) * Return to a single stream per request (#245,#557)
* Use separate frame type and settings registries from HTTP/2 (#81) * Use separate frame type and settings registries from HTTP/2 (#81)
* SETTINGS_ENABLE_PUSH instead of SETTINGS_DISABLE_PUSH (#477) * SETTINGS_ENABLE_PUSH instead of SETTINGS_DISABLE_PUSH (#477)
* Restored GOAWAY (#696) * Restored GOAWAY (#696)
* Identify server push using Push ID rather than a stream ID * Identify server push using Push ID rather than a stream ID
(#702,#281) (#702,#281)
* DATA frames cannot be empty (#700) * DATA frames cannot be empty (#700)
B.28. Since draft-ietf-quic-http-03 B.29. Since draft-ietf-quic-http-03
None. None.
B.29. Since draft-ietf-quic-http-02 B.30. Since draft-ietf-quic-http-02
* Track changes in transport draft * Track changes in transport draft
B.30. Since draft-ietf-quic-http-01 B.31. Since draft-ietf-quic-http-01
* SETTINGS changes (#181): * SETTINGS changes (#181):
- SETTINGS can be sent only once at the start of a connection; no - SETTINGS can be sent only once at the start of a connection; no
changes thereafter changes thereafter
- SETTINGS_ACK removed - SETTINGS_ACK removed
- Settings can only occur in the SETTINGS frame a single time - Settings can only occur in the SETTINGS frame a single time
skipping to change at page 70, line 35 skipping to change at page 71, line 12
* Closing the connection control stream or any message control * Closing the connection control stream or any message control
stream is a fatal error (#176) stream is a fatal error (#176)
* HPACK Sequence counter can wrap (#173) * HPACK Sequence counter can wrap (#173)
* 0-RTT guidance added * 0-RTT guidance added
* Guide to differences from HTTP/2 and porting HTTP/2 extensions * Guide to differences from HTTP/2 and porting HTTP/2 extensions
added (#127,#242) added (#127,#242)
B.31. Since draft-ietf-quic-http-00 B.32. Since draft-ietf-quic-http-00
* Changed "HTTP/2-over-QUIC" to "HTTP/QUIC" throughout (#11,#29) * Changed "HTTP/2-over-QUIC" to "HTTP/QUIC" throughout (#11,#29)
* Changed from using HTTP/2 framing within Stream 3 to new framing * Changed from using HTTP/2 framing within Stream 3 to new framing
format and two-stream-per-request model (#71,#72,#73) format and two-stream-per-request model (#71,#72,#73)
* Adopted SETTINGS format from draft-bishop-httpbis-extended- * Adopted SETTINGS format from draft-bishop-httpbis-extended-
settings-01 settings-01
* Reworked SETTINGS_ACK to account for indeterminate inter-stream * Reworked SETTINGS_ACK to account for indeterminate inter-stream
order (#75) order (#75)
* Described CONNECT pseudo-method (#95) * Described CONNECT pseudo-method (#95)
* Updated ALPN token and Alt-Svc guidance (#13,#87) * Updated ALPN token and Alt-Svc guidance (#13,#87)
* Application-layer-defined error codes (#19,#74) * Application-layer-defined error codes (#19,#74)
B.32. Since draft-shade-quic-http2-mapping-00 B.33. Since draft-shade-quic-http2-mapping-00
* Adopted as base for draft-ietf-quic-http * Adopted as base for draft-ietf-quic-http
* Updated authors/editors list * Updated authors/editors list
Acknowledgements Acknowledgements
The original authors of this specification were Robbie Shade and Mike The original authors of this specification were Robbie Shade and Mike
Warres. Warres.
skipping to change at page 71, line 27 skipping to change at page 72, line 4
from many people. Among others, the following people provided from many people. Among others, the following people provided
substantial contributions to this document: substantial contributions to this document:
* Bence Beky * Bence Beky
* Daan De Meyer * Daan De Meyer
* Martin Duke * Martin Duke
* Roy Fielding * Roy Fielding
* Alan Frindell * Alan Frindell
* Alessandro Ghedini * Alessandro Ghedini
* Nick Harper * Nick Harper
* Ryan Hamilton * Ryan Hamilton
* Christian Huitema * Christian Huitema
* Subodh Iyengar * Subodh Iyengar
* Robin Marx * Robin Marx
* Patrick McManus * Patrick McManus
* Luca Nicco * Luca Niccolini
* 奥 一穂 (Kazuho Oku) * 奥 一穂 (Kazuho Oku)
* Lucas Pardue * Lucas Pardue
* Roberto Peon * Roberto Peon
* Julian Reschke * Julian Reschke
* Eric Rescorla * Eric Rescorla
* Martin Seemann * Martin Seemann
* Ben Schwartz * Ben Schwartz
* Ian Swett * Ian Swett
* Willy Taureau * Willy Taureau
 End of changes. 131 change blocks. 
252 lines changed or deleted 280 lines changed or added

This html diff was produced by rfcdiff 1.45. The latest version is available from http://tools.ietf.org/tools/rfcdiff/