draft-ietf-httpbis-early-hints-05.txt   draft-ietf-httpbis-early-hints-latest.txt 
HTTP Working Group K. Oku HTTP Working Group K. Oku
Internet-Draft Fastly Internet-Draft Fastly
Intended status: Experimental October 28, 2017 Intended status: Experimental September 24, 2018
Expires: May 1, 2018 Expires: March 28, 2022
An HTTP Status Code for Indicating Hints An HTTP Status Code for Indicating Hints
draft-ietf-httpbis-early-hints-05 draft-ietf-httpbis-early-hints-latest
Abstract Abstract
This memo introduces an informational HTTP status code that can be This memo introduces an informational HTTP status code that can be
used to convey hints that help a client make preparations for used to convey hints that help a client make preparations for
processing the final response. processing the final response.
Note to Readers Note to Readers
Discussion of this draft takes place on the HTTP working group Discussion of this draft takes place on the HTTP working group
skipping to change at page 1, line 42 skipping to change at page 1, line 42
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 May 1, 2018. This Internet-Draft will expire on March 28, 2022.
Copyright Notice Copyright Notice
Copyright (c) 2017 IETF Trust and the persons identified as the Copyright (c) 2018 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 Provisions Relating to IETF Documents
(https://trustee.ietf.org/license-info) in effect on the date of (https://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as the Trust Legal Provisions and are provided without warranty as
skipping to change at page 2, line 27 skipping to change at page 2, line 27
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
1.1. Notational Conventions . . . . . . . . . . . . . . . . . 3 1.1. Notational Conventions . . . . . . . . . . . . . . . . . 3
2. 103 Early Hints . . . . . . . . . . . . . . . . . . . . . . . 3 2. 103 Early Hints . . . . . . . . . . . . . . . . . . . . . . . 3
3. Security Considerations . . . . . . . . . . . . . . . . . . . 5 3. Security Considerations . . . . . . . . . . . . . . . . . . . 5
4. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 6 4. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 6
5. References . . . . . . . . . . . . . . . . . . . . . . . . . 6 5. References . . . . . . . . . . . . . . . . . . . . . . . . . 6
5.1. Normative References . . . . . . . . . . . . . . . . . . 6 5.1. Normative References . . . . . . . . . . . . . . . . . . 6
5.2. Informative References . . . . . . . . . . . . . . . . . 6 5.2. Informative References . . . . . . . . . . . . . . . . . 6
5.3. URIs . . . . . . . . . . . . . . . . . . . . . . . . . . 7 5.3. URIs . . . . . . . . . . . . . . . . . . . . . . . . . . 7
Appendix A. Changes . . . . . . . . . . . . . . . . . . . . . . 7 Appendix A. Changes . . . . . . . . . . . . . . . . . . . . . . 7
A.1. Since draft-ietf-httpbis-early-hints-04 . . . . . . . . . 7 A.1. Since draft-ietf-httpbis-early-hints-05 . . . . . . . . . 7
A.2. Since draft-ietf-httpbis-early-hints-03 . . . . . . . . . 7 A.2. Since draft-ietf-httpbis-early-hints-04 . . . . . . . . . 7
A.3. Since draft-ietf-httpbis-early-hints-02 . . . . . . . . . 7 A.3. Since draft-ietf-httpbis-early-hints-03 . . . . . . . . . 7
A.4. Since draft-ietf-httpbis-early-hints-01 . . . . . . . . . 7 A.4. Since draft-ietf-httpbis-early-hints-02 . . . . . . . . . 7
A.5. Since draft-ietf-httpbis-early-hints-00 . . . . . . . . . 7 A.5. Since draft-ietf-httpbis-early-hints-01 . . . . . . . . . 7
A.6. Since draft-ietf-httpbis-early-hints-00 . . . . . . . . . 8
Appendix B. Acknowledgements . . . . . . . . . . . . . . . . . . 8 Appendix B. Acknowledgements . . . . . . . . . . . . . . . . . . 8
Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 8 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 8
1. Introduction 1. Introduction
It is common for HTTP responses to contain links to external It is common for HTTP responses to contain links to external
resources that need to be fetched prior to their use; for example, resources that need to be fetched prior to their use; for example,
rendering HTML by a Web browser. Having such links available to the rendering HTML by a Web browser. Having such links available to the
client as early as possible helps to minimize perceived latency. client as early as possible helps to minimize perceived latency.
skipping to change at page 7, line 15 skipping to change at page 7, line 15
5.3. URIs 5.3. URIs
[1] https://lists.w3.org/Archives/Public/ietf-http-wg/ [1] https://lists.w3.org/Archives/Public/ietf-http-wg/
[2] https://httpwg.github.io/ [2] https://httpwg.github.io/
[3] https://github.com/httpwg/http-extensions/labels/early-hints [3] https://github.com/httpwg/http-extensions/labels/early-hints
Appendix A. Changes Appendix A. Changes
A.1. Since draft-ietf-httpbis-early-hints-04 A.1. Since draft-ietf-httpbis-early-hints-05
o None yet.
A.2. Since draft-ietf-httpbis-early-hints-04
o Clarified that the server is allowed to add headers not found in a o Clarified that the server is allowed to add headers not found in a
103 response to the final response. 103 response to the final response.
o Clarify client's behavior when it receives more than one 103 o Clarify client's behavior when it receives more than one 103
response. response.
A.2. Since draft-ietf-httpbis-early-hints-03 A.3. Since draft-ietf-httpbis-early-hints-03
o Removed statements that were either redundant or contradictory to o Removed statements that were either redundant or contradictory to
RFC7230-7234. RFC7230-7234.
o Clarified what the server's expected behavior is. o Clarified what the server's expected behavior is.
o Explain that a server might want to send more than one 103 o Explain that a server might want to send more than one 103
response. response.
o Editorial Changes. o Editorial Changes.
A.3. Since draft-ietf-httpbis-early-hints-02 A.4. Since draft-ietf-httpbis-early-hints-02
o Editorial changes. o Editorial changes.
o Added an example. o Added an example.
A.4. Since draft-ietf-httpbis-early-hints-01 A.5. Since draft-ietf-httpbis-early-hints-01
o Editorial changes. o Editorial changes.
A.5. Since draft-ietf-httpbis-early-hints-00 A.6. Since draft-ietf-httpbis-early-hints-00
o Forbid processing the headers of a 103 response as part of the o Forbid processing the headers of a 103 response as part of the
informational response. informational response.
Appendix B. Acknowledgements Appendix B. Acknowledgements
Thanks to Tatsuhiro Tsujikawa for coming up with the idea of sending Thanks to Tatsuhiro Tsujikawa for coming up with the idea of sending
the Link header fields using an informational response. the Link header fields using an informational response.
Author's Address Author's Address
 End of changes. 10 change blocks. 
15 lines changed or deleted 20 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/