draft-ietf-httpbis-semantics-19.txt   draft-ietf-httpbis-semantics-latest.txt 
HTTP Working Group R. Fielding, Ed. HTTP Working Group R. Fielding, Ed.
Internet-Draft Adobe Internet-Draft Adobe
Obsoletes: 2818, 7230, 7231, 7232, 7233, 7235, M. Nottingham, Ed. Obsoletes: 2818, 7230, 7231, 7232, 7233, 7235, M. Nottingham, Ed.
7538, 7615, 7694 (if approved) Fastly 7538, 7615, 7694 (if approved) Fastly
Updates: 3864 (if approved) J. Reschke, Ed. Updates: 3864 (if approved) J. Reschke, Ed.
Intended status: Standards Track greenbytes Intended status: Standards Track greenbytes
Expires: March 14, 2022 September 10, 2021 Expires: April 30, 2022 October 27, 2021
HTTP Semantics HTTP Semantics
draft-ietf-httpbis-semantics-19 draft-ietf-httpbis-semantics-latest
Abstract Abstract
The Hypertext Transfer Protocol (HTTP) is a stateless application- The Hypertext Transfer Protocol (HTTP) is a stateless application-
level protocol for distributed, collaborative, hypertext information level protocol for distributed, collaborative, hypertext information
systems. This document describes the overall architecture of HTTP, systems. This document describes the overall architecture of HTTP,
establishes common terminology, and defines aspects of the protocol establishes common terminology, and defines aspects of the protocol
that are shared by all versions. In this definition are core that are shared by all versions. In this definition are core
protocol elements, extensibility mechanisms, and the "http" and protocol elements, extensibility mechanisms, and the "http" and
"https" Uniform Resource Identifier (URI) schemes. "https" Uniform Resource Identifier (URI) schemes.
skipping to change at page 1, line 40 skipping to change at page 1, line 40
This note is to be removed before publishing as an RFC. This note is to be removed before publishing as an RFC.
Discussion of this draft takes place on the HTTP working group Discussion of this draft takes place on the HTTP working group
mailing list (ietf-http-wg@w3.org), which is archived at mailing list (ietf-http-wg@w3.org), which is archived at
<https://lists.w3.org/Archives/Public/ietf-http-wg/>. <https://lists.w3.org/Archives/Public/ietf-http-wg/>.
Working Group information can be found at <https://httpwg.org/>; Working Group information can be found at <https://httpwg.org/>;
source code and issues list for this draft can be found at source code and issues list for this draft can be found at
<https://github.com/httpwg/http-core>. <https://github.com/httpwg/http-core>.
The changes in this draft are summarized in Appendix C.20. The changes in this draft are summarized in Appendix C.21.
Status of This Memo Status of This Memo
This Internet-Draft is submitted in full conformance with the This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79. provisions of BCP 78 and BCP 79.
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 March 14, 2022. This Internet-Draft will expire on April 30, 2022.
Copyright Notice Copyright Notice
Copyright (c) 2021 IETF Trust and the persons identified as the Copyright (c) 2021 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 49 skipping to change at page 2, line 49
not be created outside the IETF Standards Process, except to format not be created outside the IETF Standards Process, except to format
it for publication as an RFC or to translate it into languages other it for publication as an RFC or to translate it into languages other
than English. than English.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 9 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 9
1.1. Purpose . . . . . . . . . . . . . . . . . . . . . . . . . 9 1.1. Purpose . . . . . . . . . . . . . . . . . . . . . . . . . 9
1.2. History and Evolution . . . . . . . . . . . . . . . . . . 10 1.2. History and Evolution . . . . . . . . . . . . . . . . . . 10
1.3. Core Semantics . . . . . . . . . . . . . . . . . . . . . 11 1.3. Core Semantics . . . . . . . . . . . . . . . . . . . . . 11
1.4. Specifications Obsoleted by this Document . . . . . . . . 11 1.4. Specifications Obsoleted by this Document . . . . . . . . 12
2. Conformance . . . . . . . . . . . . . . . . . . . . . . . . . 12 2. Conformance . . . . . . . . . . . . . . . . . . . . . . . . . 12
2.1. Syntax Notation . . . . . . . . . . . . . . . . . . . . . 12 2.1. Syntax Notation . . . . . . . . . . . . . . . . . . . . . 12
2.2. Requirements Notation . . . . . . . . . . . . . . . . . . 13 2.2. Requirements Notation . . . . . . . . . . . . . . . . . . 13
2.3. Length Requirements . . . . . . . . . . . . . . . . . . . 14 2.3. Length Requirements . . . . . . . . . . . . . . . . . . . 14
2.4. Error Handling . . . . . . . . . . . . . . . . . . . . . 15 2.4. Error Handling . . . . . . . . . . . . . . . . . . . . . 15
2.5. Protocol Version . . . . . . . . . . . . . . . . . . . . 15 2.5. Protocol Version . . . . . . . . . . . . . . . . . . . . 15
3. Terminology and Core Concepts . . . . . . . . . . . . . . . . 16 3. Terminology and Core Concepts . . . . . . . . . . . . . . . . 16
3.1. Resources . . . . . . . . . . . . . . . . . . . . . . . . 16 3.1. Resources . . . . . . . . . . . . . . . . . . . . . . . . 16
3.2. Representations . . . . . . . . . . . . . . . . . . . . . 17 3.2. Representations . . . . . . . . . . . . . . . . . . . . . 17
3.3. Connections, Clients and Servers . . . . . . . . . . . . 17 3.3. Connections, Clients and Servers . . . . . . . . . . . . 17
skipping to change at page 8, line 47 skipping to change at page 8, line 47
18.1. URI Scheme Registration . . . . . . . . . . . . . . . . 194 18.1. URI Scheme Registration . . . . . . . . . . . . . . . . 194
18.2. Method Registration . . . . . . . . . . . . . . . . . . 194 18.2. Method Registration . . . . . . . . . . . . . . . . . . 194
18.3. Status Code Registration . . . . . . . . . . . . . . . . 194 18.3. Status Code Registration . . . . . . . . . . . . . . . . 194
18.4. Field Name Registration . . . . . . . . . . . . . . . . 196 18.4. Field Name Registration . . . . . . . . . . . . . . . . 196
18.5. Authentication Scheme Registration . . . . . . . . . . . 198 18.5. Authentication Scheme Registration . . . . . . . . . . . 198
18.6. Content Coding Registration . . . . . . . . . . . . . . 198 18.6. Content Coding Registration . . . . . . . . . . . . . . 198
18.7. Range Unit Registration . . . . . . . . . . . . . . . . 198 18.7. Range Unit Registration . . . . . . . . . . . . . . . . 198
18.8. Media Type Registration . . . . . . . . . . . . . . . . 199 18.8. Media Type Registration . . . . . . . . . . . . . . . . 199
18.9. Port Registration . . . . . . . . . . . . . . . . . . . 199 18.9. Port Registration . . . . . . . . . . . . . . . . . . . 199
18.10. Upgrade Token Registration . . . . . . . . . . . . . . . 199 18.10. Upgrade Token Registration . . . . . . . . . . . . . . . 199
19. References . . . . . . . . . . . . . . . . . . . . . . . . . 199 19. References . . . . . . . . . . . . . . . . . . . . . . . . . 200
19.1. Normative References . . . . . . . . . . . . . . . . . . 199 19.1. Normative References . . . . . . . . . . . . . . . . . . 200
19.2. Informative References . . . . . . . . . . . . . . . . . 201 19.2. Informative References . . . . . . . . . . . . . . . . . 202
Appendix A. Collected ABNF . . . . . . . . . . . . . . . . . . . 208 Appendix A. Collected ABNF . . . . . . . . . . . . . . . . . . . 208
Appendix B. Changes from previous RFCs . . . . . . . . . . . . . 212 Appendix B. Changes from previous RFCs . . . . . . . . . . . . . 213
B.1. Changes from RFC 2818 . . . . . . . . . . . . . . . . . . 212 B.1. Changes from RFC 2818 . . . . . . . . . . . . . . . . . . 213
B.2. Changes from RFC 7230 . . . . . . . . . . . . . . . . . . 212 B.2. Changes from RFC 7230 . . . . . . . . . . . . . . . . . . 213
B.3. Changes from RFC 7231 . . . . . . . . . . . . . . . . . . 213 B.3. Changes from RFC 7231 . . . . . . . . . . . . . . . . . . 214
B.4. Changes from RFC 7232 . . . . . . . . . . . . . . . . . . 215 B.4. Changes from RFC 7232 . . . . . . . . . . . . . . . . . . 216
B.5. Changes from RFC 7233 . . . . . . . . . . . . . . . . . . 216 B.5. Changes from RFC 7233 . . . . . . . . . . . . . . . . . . 216
B.6. Changes from RFC 7235 . . . . . . . . . . . . . . . . . . 216 B.6. Changes from RFC 7235 . . . . . . . . . . . . . . . . . . 216
B.7. Changes from RFC 7538 . . . . . . . . . . . . . . . . . . 216 B.7. Changes from RFC 7538 . . . . . . . . . . . . . . . . . . 216
B.8. Changes from RFC 7615 . . . . . . . . . . . . . . . . . . 216 B.8. Changes from RFC 7615 . . . . . . . . . . . . . . . . . . 217
B.9. Changes from RFC 7694 . . . . . . . . . . . . . . . . . . 216 B.9. Changes from RFC 7694 . . . . . . . . . . . . . . . . . . 217
Appendix C. Change Log . . . . . . . . . . . . . . . . . . . . . 216 Appendix C. Change Log . . . . . . . . . . . . . . . . . . . . . 217
C.1. Between RFC723x and draft 00 . . . . . . . . . . . . . . 216 C.1. Between RFC723x and draft 00 . . . . . . . . . . . . . . 217
C.2. Since draft-ietf-httpbis-semantics-00 . . . . . . . . . . 217 C.2. Since draft-ietf-httpbis-semantics-00 . . . . . . . . . . 217
C.3. Since draft-ietf-httpbis-semantics-01 . . . . . . . . . . 217 C.3. Since draft-ietf-httpbis-semantics-01 . . . . . . . . . . 218
C.4. Since draft-ietf-httpbis-semantics-02 . . . . . . . . . . 219 C.4. Since draft-ietf-httpbis-semantics-02 . . . . . . . . . . 219
C.5. Since draft-ietf-httpbis-semantics-03 . . . . . . . . . . 220 C.5. Since draft-ietf-httpbis-semantics-03 . . . . . . . . . . 220
C.6. Since draft-ietf-httpbis-semantics-04 . . . . . . . . . . 220 C.6. Since draft-ietf-httpbis-semantics-04 . . . . . . . . . . 221
C.7. Since draft-ietf-httpbis-semantics-05 . . . . . . . . . . 221 C.7. Since draft-ietf-httpbis-semantics-05 . . . . . . . . . . 221
C.8. Since draft-ietf-httpbis-semantics-06 . . . . . . . . . . 222 C.8. Since draft-ietf-httpbis-semantics-06 . . . . . . . . . . 223
C.9. Since draft-ietf-httpbis-semantics-07 . . . . . . . . . . 224 C.9. Since draft-ietf-httpbis-semantics-07 . . . . . . . . . . 224
C.10. Since draft-ietf-httpbis-semantics-08 . . . . . . . . . . 225 C.10. Since draft-ietf-httpbis-semantics-08 . . . . . . . . . . 225
C.11. Since draft-ietf-httpbis-semantics-09 . . . . . . . . . . 226 C.11. Since draft-ietf-httpbis-semantics-09 . . . . . . . . . . 227
C.12. Since draft-ietf-httpbis-semantics-10 . . . . . . . . . . 226 C.12. Since draft-ietf-httpbis-semantics-10 . . . . . . . . . . 227
C.13. Since draft-ietf-httpbis-semantics-11 . . . . . . . . . . 228 C.13. Since draft-ietf-httpbis-semantics-11 . . . . . . . . . . 228
C.14. Since draft-ietf-httpbis-semantics-12 . . . . . . . . . . 228 C.14. Since draft-ietf-httpbis-semantics-12 . . . . . . . . . . 229
C.15. Since draft-ietf-httpbis-semantics-13 . . . . . . . . . . 230 C.15. Since draft-ietf-httpbis-semantics-13 . . . . . . . . . . 231
C.16. Since draft-ietf-httpbis-semantics-14 . . . . . . . . . . 231 C.16. Since draft-ietf-httpbis-semantics-14 . . . . . . . . . . 231
C.17. Since draft-ietf-httpbis-semantics-15 . . . . . . . . . . 233 C.17. Since draft-ietf-httpbis-semantics-15 . . . . . . . . . . 234
C.18. Since draft-ietf-httpbis-semantics-16 . . . . . . . . . . 234 C.18. Since draft-ietf-httpbis-semantics-16 . . . . . . . . . . 234
C.19. Since draft-ietf-httpbis-semantics-17 . . . . . . . . . . 234 C.19. Since draft-ietf-httpbis-semantics-17 . . . . . . . . . . 235
C.20. Since draft-ietf-httpbis-semantics-18 . . . . . . . . . . 236 C.20. Since draft-ietf-httpbis-semantics-18 . . . . . . . . . . 236
C.21. Since draft-ietf-httpbis-semantics-19 . . . . . . . . . . 237
Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . . 237 Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . . 237
Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 238 Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 238
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 249 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 249
1. Introduction 1. Introduction
1.1. Purpose 1.1. Purpose
The Hypertext Transfer Protocol (HTTP) is a family of stateless, The Hypertext Transfer Protocol (HTTP) is a family of stateless,
application-level, request/response protocols that share a generic application-level, request/response protocols that share a generic
skipping to change at page 176, line 12 skipping to change at page 176, line 12
Registration requests consist of the following information: Registration requests consist of the following information:
Field name: Field name:
The requested field name. It MUST conform to the field-name The requested field name. It MUST conform to the field-name
syntax defined in Section 5.1, and SHOULD be restricted to just syntax defined in Section 5.1, and SHOULD be restricted to just
letters, digits, and hyphen ('-') characters, with the first letters, digits, and hyphen ('-') characters, with the first
character being a letter. character being a letter.
Status: Status:
"permanent" or "provisional". "permanent", "provisional", "deprecated", or "obsoleted"
Specification document(s): Specification document(s):
Reference to the document that specifies the field, preferably Reference to the document that specifies the field, preferably
including a URI that can be used to retrieve a copy of the including a URI that can be used to retrieve a copy of the
document. Optional but encouraged for provisional registrations. document. Optional but encouraged for provisional registrations.
An indication of the relevant section(s) can also be included, but An indication of the relevant section(s) can also be included, but
is not required. is not required.
And, optionally: And, optionally:
skipping to change at page 196, line 13 skipping to change at page 196, line 13
Table 8 Table 8
18.4. Field Name Registration 18.4. Field Name Registration
This specification updates the HTTP related aspects of the existing This specification updates the HTTP related aspects of the existing
registration procedures for message header fields defined in registration procedures for message header fields defined in
[RFC3864]. It replaces the old procedures as they relate to HTTP, by [RFC3864]. It replaces the old procedures as they relate to HTTP, by
defining a new registration procedure and moving HTTP field defining a new registration procedure and moving HTTP field
definitions into a separate registry. definitions into a separate registry.
Please create a new registry as outlined in Section 16.3.1. Please create a new registry as outlined in Section 16.3.1, and let
that registry link to this specification (e.g., "See section
Section 16.3 of [this document] for information on defining and
registering new HTTP Header Fields.").
After creating the registry, all entries in the Permanent and After creating the registry, all entries in the Permanent and
Provisional Message Header Registries with the protocol 'http' are to Provisional Message Header Registries with the protocol 'http' are to
be moved to it, with the following changes applied: be moved to it, with the following changes applied:
1. The 'Applicable Protocol' field is to be omitted. 1. The 'Applicable Protocol' field is to be omitted.
2. Entries with a status of 'standard', 'experimental', 'reserved', 2. Entries with a status of 'standard', 'experimental', 'reserved',
or 'informational' are to have a status of 'permanent'. or 'informational' are to have a status of 'permanent'.
3. Provisional entries without a status are to have a status of 3. Provisional entries without a status are to have a status of
'provisional'. 'provisional'.
4. Permanent entries without a status (after confirmation that the 4. Permanent entries without a status (after confirmation that the
registration document did not define one) will have a status of registration document did not define one) will have a status of
'provisional'. The Expert(s) can choose to update their status 'provisional'. The Expert(s) can choose to update their status
if there is evidence that another is more appropriate. if there is evidence that another is more appropriate.
Please annotate the Permanent and Provisional Message Header Please annotate the Permanent and Provisional Message Header
registries to indicate that HTTP field name registrations have moved, registries to indicate that HTTP field name registrations have moved,
with an appropriate link. with an appropriate link (such as: "HTTP field name registrations
have been moved to <https://www.iana.org/assignments/http-fields> per
[this document].") and furthermore remove the existing note pointing
to [RFC7231] ("See section 8.3.1 of [RFC7231] for information on
registering new HTTP Header Fields.").
After that is complete, please update the new registry with the field After that is complete, please update the new registry with the field
names listed in the following table. names listed in the following table.
+---------------------------+------------+--------+------------+ +---------------------------+------------+--------+------------+
| Field Name | Status | Ref. | Comments | | Field Name | Status | Ref. | Comments |
+---------------------------+------------+--------+------------+ +---------------------------+------------+--------+------------+
| Accept | standard | 12.5.1 | | | Accept | permanent | 12.5.1 | |
| Accept-Charset | deprecated | 12.5.2 | | | Accept-Charset | deprecated | 12.5.2 | |
| Accept-Encoding | standard | 12.5.3 | | | Accept-Encoding | permanent | 12.5.3 | |
| Accept-Language | standard | 12.5.4 | | | Accept-Language | permanent | 12.5.4 | |
| Accept-Ranges | standard | 14.3 | | | Accept-Ranges | permanent | 14.3 | |
| Allow | standard | 10.2.1 | | | Allow | permanent | 10.2.1 | |
| Authentication-Info | standard | 11.6.3 | | | Authentication-Info | permanent | 11.6.3 | |
| Authorization | standard | 11.6.2 | | | Authorization | permanent | 11.6.2 | |
| Connection | standard | 7.6.1 | | | Connection | permanent | 7.6.1 | |
| Content-Encoding | standard | 8.4 | | | Content-Encoding | permanent | 8.4 | |
| Content-Language | standard | 8.5 | | | Content-Language | permanent | 8.5 | |
| Content-Length | standard | 8.6 | | | Content-Length | permanent | 8.6 | |
| Content-Location | standard | 8.7 | | | Content-Location | permanent | 8.7 | |
| Content-Range | standard | 14.4 | | | Content-Range | permanent | 14.4 | |
| Content-Type | standard | 8.3 | | | Content-Type | permanent | 8.3 | |
| Date | standard | 6.6.1 | | | Date | permanent | 6.6.1 | |
| ETag | standard | 8.8.3 | | | ETag | permanent | 8.8.3 | |
| Expect | standard | 10.1.1 | | | Expect | permanent | 10.1.1 | |
| From | standard | 10.1.2 | | | From | permanent | 10.1.2 | |
| Host | standard | 7.2 | | | Host | permanent | 7.2 | |
| If-Match | standard | 13.1.1 | | | If-Match | permanent | 13.1.1 | |
| If-Modified-Since | standard | 13.1.3 | | | If-Modified-Since | permanent | 13.1.3 | |
| If-None-Match | standard | 13.1.2 | | | If-None-Match | permanent | 13.1.2 | |
| If-Range | standard | 13.1.5 | | | If-Range | permanent | 13.1.5 | |
| If-Unmodified-Since | standard | 13.1.4 | | | If-Unmodified-Since | permanent | 13.1.4 | |
| Last-Modified | standard | 8.8.2 | | | Last-Modified | permanent | 8.8.2 | |
| Location | standard | 10.2.2 | | | Location | permanent | 10.2.2 | |
| Max-Forwards | standard | 7.6.2 | | | Max-Forwards | permanent | 7.6.2 | |
| Proxy-Authenticate | standard | 11.7.1 | | | Proxy-Authenticate | permanent | 11.7.1 | |
| Proxy-Authentication-Info | standard | 11.7.3 | | | Proxy-Authentication-Info | permanent | 11.7.3 | |
| Proxy-Authorization | standard | 11.7.2 | | | Proxy-Authorization | permanent | 11.7.2 | |
| Range | standard | 14.2 | | | Range | permanent | 14.2 | |
| Referer | standard | 10.1.3 | | | Referer | permanent | 10.1.3 | |
| Retry-After | standard | 10.2.3 | | | Retry-After | permanent | 10.2.3 | |
| Server | standard | 10.2.4 | | | Server | permanent | 10.2.4 | |
| TE | standard | 10.1.4 | | | TE | permanent | 10.1.4 | |
| Trailer | standard | 6.6.2 | | | Trailer | permanent | 6.6.2 | |
| Upgrade | standard | 7.8 | | | Upgrade | permanent | 7.8 | |
| User-Agent | standard | 10.1.5 | | | User-Agent | permanent | 10.1.5 | |
| Vary | standard | 12.5.5 | | | Vary | permanent | 12.5.5 | |
| Via | standard | 7.6.3 | | | Via | permanent | 7.6.3 | |
| WWW-Authenticate | standard | 11.6.1 | | | WWW-Authenticate | permanent | 11.6.1 | |
| * | standard | 12.5.5 | (reserved) | | * | permanent | 12.5.5 | (reserved) |
+---------------------------+------------+--------+------------+ +---------------------------+------------+--------+------------+
Table 9 Table 9
The field name "*" is reserved, since using that name as an HTTP The field name "*" is reserved, since using that name as an HTTP
header field might conflict with its special semantics in the Vary header field might conflict with its special semantics in the Vary
header field (Section 12.5.5). header field (Section 12.5.5).
Finally, please update the "Content-MD5" entry in the new registry to Finally, please update the "Content-MD5" entry in the new registry to
have a status of 'obsoleted' with references to Section 14.15 of have a status of 'obsoleted' with references to Section 14.15 of
skipping to change at page 199, line 49 skipping to change at page 200, line 11
+------+-------------------+-------------------------+------+ +------+-------------------+-------------------------+------+
Table 12 Table 12
19. References 19. References
19.1. Normative References 19.1. Normative References
[CACHING] Fielding, R., Ed., Nottingham, M., Ed., and J. Reschke, [CACHING] Fielding, R., Ed., Nottingham, M., Ed., and J. Reschke,
Ed., "HTTP Caching", Work in Progress, Internet-Draft, Ed., "HTTP Caching", Work in Progress, Internet-Draft,
draft-ietf-httpbis-cache-latest, September 2021, draft-ietf-httpbis-cache-latest, October 2021,
<https://datatracker.ietf.org/doc/html/draft-ietf-httpbis- <https://datatracker.ietf.org/doc/html/draft-ietf-httpbis-
cache-latest>. cache-latest>.
[RFC1950] Deutsch, L.P. and J-L. Gailly, "ZLIB Compressed Data [RFC1950] Deutsch, L.P. and J-L. Gailly, "ZLIB Compressed Data
Format Specification version 3.3", RFC 1950, Format Specification version 3.3", RFC 1950,
DOI 10.17487/RFC1950, May 1996, DOI 10.17487/RFC1950, May 1996,
<https://www.rfc-editor.org/info/rfc1950>. <https://www.rfc-editor.org/info/rfc1950>.
[RFC1951] Deutsch, P., "DEFLATE Compressed Data Format Specification [RFC1951] Deutsch, P., "DEFLATE Compressed Data Format Specification
version 1.3", RFC 1951, DOI 10.17487/RFC1951, May 1996, version 1.3", RFC 1951, DOI 10.17487/RFC1951, May 1996,
skipping to change at page 203, line 16 skipping to change at page 203, line 27
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>.
[HTTP/1.0] Berners-Lee, T., Fielding, R.T., and H.F. Nielsen, [HTTP/1.0] Berners-Lee, T., Fielding, R.T., and H.F. Nielsen,
"Hypertext Transfer Protocol -- HTTP/1.0", RFC 1945, "Hypertext Transfer Protocol -- HTTP/1.0", RFC 1945,
DOI 10.17487/RFC1945, May 1996, DOI 10.17487/RFC1945, May 1996,
<https://www.rfc-editor.org/info/rfc1945>. <https://www.rfc-editor.org/info/rfc1945>.
[HTTP/1.1] Fielding, R., Ed., Nottingham, M., Ed., and J. Reschke, [HTTP/1.1] Fielding, R., Ed., Nottingham, M., Ed., and J. Reschke,
Ed., "HTTP/1.1", Work in Progress, Internet-Draft, draft- Ed., "HTTP/1.1", Work in Progress, Internet-Draft, draft-
ietf-httpbis-messaging-latest, September 2021, ietf-httpbis-messaging-latest, October 2021,
<https://datatracker.ietf.org/doc/html/draft-ietf-httpbis- <https://datatracker.ietf.org/doc/html/draft-ietf-httpbis-
messaging-latest>. messaging-latest>.
[HTTP/2] Belshe, M., Peon, R., and M. Thomson, Ed., "Hypertext [HTTP/2] 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>.
[HTTP/3] Bishop, M., "Hypertext Transfer Protocol Version 3 [HTTP/3] Bishop, M., "Hypertext Transfer Protocol Version 3
(HTTP/3)", Work in Progress, Internet-Draft, draft-ietf- (HTTP/3)", Work in Progress, Internet-Draft, draft-ietf-
skipping to change at page 237, line 5 skipping to change at page 237, line 14
o In Section 12.2, wordsmith future guidance on reactive negotiation o In Section 12.2, wordsmith future guidance on reactive negotiation
(<https://github.com/httpwg/http-core/pull/975>) (<https://github.com/httpwg/http-core/pull/975>)
o In Section 15.4.2 and Section 15.4.9, improve text about automatic o In Section 15.4.2 and Section 15.4.9, improve text about automatic
link-editing (<https://github.com/httpwg/http-core/pull/976>) link-editing (<https://github.com/httpwg/http-core/pull/976>)
o In Section 17, reference [URI] security considerations o In Section 17, reference [URI] security considerations
(<https://github.com/httpwg/http-core/pull/977>) (<https://github.com/httpwg/http-core/pull/977>)
C.21. Since draft-ietf-httpbis-semantics-19
o In Section 16.3.1, add states 'obsoleted' and 'deprecated'; in
Section 18.4, change status 'standard' to 'permanent'
(<https://github.com/httpwg/http-core/issues/978>)
o In Section 18.4, update IANA instructions based on received
feedback (<https://github.com/httpwg/http-core/issues/982>)
Acknowledgements Acknowledgements
Aside from the current editors, the following individuals deserve Aside from the current editors, the following individuals deserve
special recognition for their contributions to early aspects of HTTP special recognition for their contributions to early aspects of HTTP
and its core specifications: Marc Andreessen, Tim Berners-Lee, Robert and its core specifications: Marc Andreessen, Tim Berners-Lee, Robert
Cailliau, Daniel W. Connolly, Bob Denny, John Franks, Jim Gettys, Cailliau, Daniel W. Connolly, Bob Denny, John Franks, Jim Gettys,
Jean-François Groff, Phillip M. Hallam-Baker, Koen Holtman, Jeffery Jean-François Groff, Phillip M. Hallam-Baker, Koen Holtman, Jeffery
L. Hostetler, Shel Kaphan, Dave Kristol, Yves Lafon, Scott L. Hostetler, Shel Kaphan, Dave Kristol, Yves Lafon, Scott
D. Lawrence, Paul J. Leach, Håkon W. Lie, Ari Luotonen, Larry D. Lawrence, Paul J. Leach, Håkon W. Lie, Ari Luotonen, Larry
Masinter, Rob McCool, Jeffrey C. Mogul, Lou Montulli, David Morris, Masinter, Rob McCool, Jeffrey C. Mogul, Lou Montulli, David Morris,
 End of changes. 24 change blocks. 
73 lines changed or deleted 90 lines changed or added

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