| draft-ietf-httpbis-p3-payload-17.txt |  | draft-ietf-httpbis-p3-payload-18.txt |
--- | --- | --- | --- | ---
| HTTPbis Working Group R. Fielding, Ed. |  | HTTPbis Working Group R. Fielding, Ed. |
| Internet-Draft Adobe |  | Internet-Draft Adobe |
| Obsoletes: 2616 (if approved) J. Gettys |  | Obsoletes: 2616 (if approved) J. Gettys |
| Intended status: Standards Track Alcatel-Lucent |  | Intended status: Standards Track Alcatel-Lucent |
| Expires: May 3, 2012 J. Mogul |  | Expires: July 7, 2012 J. Mogul |
| HP |  | HP |
| H. Frystyk |  | H. Frystyk |
| Microsoft |  | Microsoft |
| L. Masinter |  | L. Masinter |
| Adobe |  | Adobe |
| P. Leach |  | P. Leach |
| Microsoft |  | Microsoft |
| T. Berners-Lee |  | T. Berners-Lee |
| W3C/MIT |  | W3C/MIT |
| Y. Lafon, Ed. |  | Y. Lafon, Ed. |
| W3C |  | W3C |
| J. Reschke, Ed. |  | J. Reschke, Ed. |
| greenbytes |  | greenbytes |
| October 31, 2011 |  | January 4, 2012 |
| HTTP/1.1, part 3: Message Payload and Content Negotiation |  | HTTP/1.1, part 3: Message Payload and Content Negotiation |
| draft-ietf-httpbis-p3-payload-17 |  | draft-ietf-httpbis-p3-payload-18 |
| Abstract |  | Abstract |
| The Hypertext Transfer Protocol (HTTP) is an application-level |  | The Hypertext Transfer Protocol (HTTP) is an application-level |
| protocol for distributed, collaborative, hypertext information |  | protocol for distributed, collaborative, hypertext information |
| systems. HTTP has been in use by the World Wide Web global |  | systems. HTTP has been in use by the World Wide Web global |
| information initiative since 1990. This document is Part 3 of the |  | information initiative since 1990. This document is Part 3 of the |
| seven-part specification that defines the protocol referred to as |  | seven-part specification that defines the protocol referred to as |
| "HTTP/1.1" and, taken together, obsoletes RFC 2616. |  | "HTTP/1.1" and, taken together, obsoletes RFC 2616. |
| skipping to change at page 1, line 49 |  | skipping to change at page 1, line 49 |
| Discussion of this draft should take place on the HTTPBIS working |  | Discussion of this draft should take place on the HTTPBIS working |
| group mailing list (ietf-http-wg@w3.org), which is archived at |  | group mailing list (ietf-http-wg@w3.org), which is archived at |
| <http://lists.w3.org/Archives/Public/ietf-http-wg/>. |  | <http://lists.w3.org/Archives/Public/ietf-http-wg/>. |
| The current issues list is at |  | The current issues list is at |
| <http://tools.ietf.org/wg/httpbis/trac/report/3> and related |  | <http://tools.ietf.org/wg/httpbis/trac/report/3> and related |
| documents (including fancy diffs) can be found at |  | documents (including fancy diffs) can be found at |
| <http://tools.ietf.org/wg/httpbis/>. |  | <http://tools.ietf.org/wg/httpbis/>. |
| The changes in this draft are summarized in Appendix E.18. |  | The changes in this draft are summarized in Appendix E.19. |
| 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 http://datatracker.ietf.org/drafts/current/. |  | Drafts is at http://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 3, 2012. |  | This Internet-Draft will expire on July 7, 2012. |
| Copyright Notice |  | Copyright Notice |
| Copyright (c) 2011 IETF Trust and the persons identified as the |  | Copyright (c) 2012 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 |
| (http://trustee.ietf.org/license-info) in effect on the date of |  | (http://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 3, line 43 |  | skipping to change at page 3, line 43 |
| 6.7. Content-Location . . . . . . . . . . . . . . . . . . . . . 23 |  | 6.7. Content-Location . . . . . . . . . . . . . . . . . . . . . 23 |
| 6.8. Content-Type . . . . . . . . . . . . . . . . . . . . . . . 25 |  | 6.8. Content-Type . . . . . . . . . . . . . . . . . . . . . . . 25 |
| 7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 25 |  | 7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 25 |
| 7.1. Header Field Registration . . . . . . . . . . . . . . . . 25 |  | 7.1. Header Field Registration . . . . . . . . . . . . . . . . 25 |
| 7.2. Content Coding Registry . . . . . . . . . . . . . . . . . 25 |  | 7.2. Content Coding Registry . . . . . . . . . . . . . . . . . 25 |
| 8. Security Considerations . . . . . . . . . . . . . . . . . . . 26 |  | 8. Security Considerations . . . . . . . . . . . . . . . . . . . 26 |
| 8.1. Privacy Issues Connected to Accept Header Fields . . . . . 26 |  | 8.1. Privacy Issues Connected to Accept Header Fields . . . . . 26 |
| 9. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 27 |  | 9. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 27 |
| 10. References . . . . . . . . . . . . . . . . . . . . . . . . . . 27 |  | 10. References . . . . . . . . . . . . . . . . . . . . . . . . . . 27 |
| 10.1. Normative References . . . . . . . . . . . . . . . . . . . 27 |  | 10.1. Normative References . . . . . . . . . . . . . . . . . . . 27 |
| 10.2. Informative References . . . . . . . . . . . . . . . . . . 29 |  | 10.2. Informative References . . . . . . . . . . . . . . . . . . 28 |
| Appendix A. Differences between HTTP and MIME . . . . . . . . . . 30 |  | Appendix A. Differences between HTTP and MIME . . . . . . . . . . 29 |
| A.1. MIME-Version . . . . . . . . . . . . . . . . . . . . . . . 30 |  | A.1. MIME-Version . . . . . . . . . . . . . . . . . . . . . . . 30 |
| A.2. Conversion to Canonical Form . . . . . . . . . . . . . . . 31 |  | A.2. Conversion to Canonical Form . . . . . . . . . . . . . . . 30 |
| A.3. Conversion of Date Formats . . . . . . . . . . . . . . . . 31 |  | A.3. Conversion of Date Formats . . . . . . . . . . . . . . . . 31 |
| A.4. Introduction of Content-Encoding . . . . . . . . . . . . . 31 |  | A.4. Introduction of Content-Encoding . . . . . . . . . . . . . 31 |
| A.5. No Content-Transfer-Encoding . . . . . . . . . . . . . . . 32 |  | A.5. No Content-Transfer-Encoding . . . . . . . . . . . . . . . 31 |
| A.6. Introduction of Transfer-Encoding . . . . . . . . . . . . 32 |  | A.6. Introduction of Transfer-Encoding . . . . . . . . . . . . 32 |
| A.7. MHTML and Line Length Limitations . . . . . . . . . . . . 32 |  | A.7. MHTML and Line Length Limitations . . . . . . . . . . . . 32 |
| Appendix B. Additional Features . . . . . . . . . . . . . . . . . 32 |  | Appendix B. Additional Features . . . . . . . . . . . . . . . . . 32 |
| Appendix C. Changes from RFC 2616 . . . . . . . . . . . . . . . . 33 |  | Appendix C. Changes from RFC 2616 . . . . . . . . . . . . . . . . 32 |
| Appendix D. Collected ABNF . . . . . . . . . . . . . . . . . . . 33 |  | Appendix D. Collected ABNF . . . . . . . . . . . . . . . . . . . 33 |
| Appendix E. Change Log (to be removed by RFC Editor before |  | Appendix E. Change Log (to be removed by RFC Editor before |
| publication) . . . . . . . . . . . . . . . . . . . . 35 |  | publication) . . . . . . . . . . . . . . . . . . . . 34 |
| E.1. Since RFC 2616 . . . . . . . . . . . . . . . . . . . . . . 35 |  | E.1. Since RFC 2616 . . . . . . . . . . . . . . . . . . . . . . 34 |
| E.2. Since draft-ietf-httpbis-p3-payload-00 . . . . . . . . . . 35 |  | E.2. Since draft-ietf-httpbis-p3-payload-00 . . . . . . . . . . 34 |
| E.3. Since draft-ietf-httpbis-p3-payload-01 . . . . . . . . . . 36 |  | E.3. Since draft-ietf-httpbis-p3-payload-01 . . . . . . . . . . 35 |
| E.4. Since draft-ietf-httpbis-p3-payload-02 . . . . . . . . . . 36 |  | E.4. Since draft-ietf-httpbis-p3-payload-02 . . . . . . . . . . 35 |
| E.5. Since draft-ietf-httpbis-p3-payload-03 . . . . . . . . . . 36 |  | E.5. Since draft-ietf-httpbis-p3-payload-03 . . . . . . . . . . 36 |
| E.6. Since draft-ietf-httpbis-p3-payload-04 . . . . . . . . . . 37 |  | E.6. Since draft-ietf-httpbis-p3-payload-04 . . . . . . . . . . 36 |
| E.7. Since draft-ietf-httpbis-p3-payload-05 . . . . . . . . . . 37 |  | E.7. Since draft-ietf-httpbis-p3-payload-05 . . . . . . . . . . 36 |
| E.8. Since draft-ietf-httpbis-p3-payload-06 . . . . . . . . . . 37 |  | E.8. Since draft-ietf-httpbis-p3-payload-06 . . . . . . . . . . 37 |
| E.9. Since draft-ietf-httpbis-p3-payload-07 . . . . . . . . . . 38 |  | E.9. Since draft-ietf-httpbis-p3-payload-07 . . . . . . . . . . 37 |
| E.10. Since draft-ietf-httpbis-p3-payload-08 . . . . . . . . . . 38 |  | E.10. Since draft-ietf-httpbis-p3-payload-08 . . . . . . . . . . 38 |
| E.11. Since draft-ietf-httpbis-p3-payload-09 . . . . . . . . . . 38 |  | E.11. Since draft-ietf-httpbis-p3-payload-09 . . . . . . . . . . 38 |
| E.12. Since draft-ietf-httpbis-p3-payload-10 . . . . . . . . . . 39 |  | E.12. Since draft-ietf-httpbis-p3-payload-10 . . . . . . . . . . 38 |
| E.13. Since draft-ietf-httpbis-p3-payload-11 . . . . . . . . . . 40 |  | E.13. Since draft-ietf-httpbis-p3-payload-11 . . . . . . . . . . 39 |
| E.14. Since draft-ietf-httpbis-p3-payload-12 . . . . . . . . . . 40 |  | E.14. Since draft-ietf-httpbis-p3-payload-12 . . . . . . . . . . 39 |
| E.15. Since draft-ietf-httpbis-p3-payload-13 . . . . . . . . . . 40 |  | E.15. Since draft-ietf-httpbis-p3-payload-13 . . . . . . . . . . 39 |
| E.16. Since draft-ietf-httpbis-p3-payload-14 . . . . . . . . . . 40 |  | E.16. Since draft-ietf-httpbis-p3-payload-14 . . . . . . . . . . 40 |
| E.17. Since draft-ietf-httpbis-p3-payload-15 . . . . . . . . . . 40 |  | E.17. Since draft-ietf-httpbis-p3-payload-15 . . . . . . . . . . 40 |
| E.18. Since draft-ietf-httpbis-p3-payload-16 . . . . . . . . . . 41 |  | E.18. Since draft-ietf-httpbis-p3-payload-16 . . . . . . . . . . 40 |
| Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41 |  | E.19. Since draft-ietf-httpbis-p3-payload-17 . . . . . . . . . . 40 |
|  |  | Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40 |
| 1. Introduction |  | 1. Introduction |
| This document defines HTTP/1.1 message payloads (a.k.a., content), |  | This document defines HTTP/1.1 message payloads (a.k.a., content), |
| the associated metadata header fields that define how the payload is |  | the associated metadata header fields that define how the payload is |
| intended to be interpreted by a recipient, the request header fields |  | intended to be interpreted by a recipient, the request header fields |
| that might influence content selection, and the various selection |  | that might influence content selection, and the various selection |
| algorithms that are collectively referred to as HTTP content |  | algorithms that are collectively referred to as HTTP content |
| negotiation. |  | negotiation. |
| skipping to change at page 27, line 29 |  | skipping to change at page 27, line 29 |
| See Section 11 of [Part1]. |  | See Section 11 of [Part1]. |
| 10. References |  | 10. References |
| 10.1. Normative References |  | 10.1. Normative References |
| [Part1] Fielding, R., Ed., Gettys, J., Mogul, J., Frystyk, H., |  | [Part1] Fielding, R., Ed., Gettys, J., Mogul, J., Frystyk, H., |
| Masinter, L., Leach, P., Berners-Lee, T., Lafon, Y., Ed., |  | Masinter, L., Leach, P., Berners-Lee, T., Lafon, Y., Ed., |
| and J. Reschke, Ed., "HTTP/1.1, part 1: URIs, Connections, |  | and J. Reschke, Ed., "HTTP/1.1, part 1: URIs, Connections, |
| and Message Parsing", draft-ietf-httpbis-p1-messaging-17 |  | and Message Parsing", draft-ietf-httpbis-p1-messaging-18 |
| (work in progress), October 2011. |  | (work in progress), January 2012. |
| [Part2] Fielding, R., Ed., Gettys, J., Mogul, J., Frystyk, H., |  | [Part2] Fielding, R., Ed., Gettys, J., Mogul, J., Frystyk, H., |
| Masinter, L., Leach, P., Berners-Lee, T., Lafon, Y., Ed., |  | Masinter, L., Leach, P., Berners-Lee, T., Lafon, Y., Ed., |
| and J. Reschke, Ed., "HTTP/1.1, part 2: Message |  | and J. Reschke, Ed., "HTTP/1.1, part 2: Message |
| Semantics", draft-ietf-httpbis-p2-semantics-17 (work in |  | Semantics", draft-ietf-httpbis-p2-semantics-18 (work in |
| progress), October 2011. |  | progress), January 2012. |
| [Part4] Fielding, R., Ed., Gettys, J., Mogul, J., Frystyk, H., |  | [Part4] Fielding, R., Ed., Gettys, J., Mogul, J., Frystyk, H., |
| Masinter, L., Leach, P., Berners-Lee, T., Lafon, Y., Ed., |  | Masinter, L., Leach, P., Berners-Lee, T., Lafon, Y., Ed., |
| and J. Reschke, Ed., "HTTP/1.1, part 4: Conditional |  | and J. Reschke, Ed., "HTTP/1.1, part 4: Conditional |
| Requests", draft-ietf-httpbis-p4-conditional-17 (work in |  | Requests", draft-ietf-httpbis-p4-conditional-18 (work in |
| progress), October 2011. |  | progress), January 2012. |
| [Part5] Fielding, R., Ed., Gettys, J., Mogul, J., Frystyk, H., |  | [Part5] Fielding, R., Ed., Gettys, J., Mogul, J., Frystyk, H., |
| Masinter, L., Leach, P., Berners-Lee, T., Lafon, Y., Ed., |  | Masinter, L., Leach, P., Berners-Lee, T., Lafon, Y., Ed., |
| and J. Reschke, Ed., "HTTP/1.1, part 5: Range Requests and |  | and J. Reschke, Ed., "HTTP/1.1, part 5: Range Requests and |
| Partial Responses", draft-ietf-httpbis-p5-range-17 (work |  | Partial Responses", draft-ietf-httpbis-p5-range-18 (work |
| in progress), October 2011. |  | in progress), January 2012. |
| [Part6] Fielding, R., Ed., Gettys, J., Mogul, J., Frystyk, H., |  | [Part6] Fielding, R., Ed., Gettys, J., Mogul, J., Frystyk, H., |
| Masinter, L., Leach, P., Berners-Lee, T., Lafon, Y., Ed., |  | Masinter, L., Leach, P., Berners-Lee, T., Lafon, Y., Ed., |
| Nottingham, M., Ed., and J. Reschke, Ed., "HTTP/1.1, part |  | Nottingham, M., Ed., and J. Reschke, Ed., "HTTP/1.1, part |
| 6: Caching", draft-ietf-httpbis-p6-cache-17 (work in |  | 6: Caching", draft-ietf-httpbis-p6-cache-18 (work in |
| progress), October 2011. |  | progress), January 2012. |
| [RFC1950] Deutsch, L. and J-L. Gailly, "ZLIB Compressed Data Format |  | [RFC1950] Deutsch, L. and J-L. Gailly, "ZLIB Compressed Data Format |
| Specification version 3.3", RFC 1950, May 1996. |  | Specification version 3.3", RFC 1950, May 1996. |
| RFC 1950 is an Informational RFC, thus it might be less |  |  |
| stable than this specification. On the other hand, this |  |  |
| downward reference was present since the publication of |  |  |
| RFC 2068 in 1997, therefore it is unlikely to cause |  |  |
| problems in practice. See also [BCP97]. |  |  |
| [RFC1951] Deutsch, P., "DEFLATE Compressed Data Format Specification |  | [RFC1951] Deutsch, P., "DEFLATE Compressed Data Format Specification |
| version 1.3", RFC 1951, May 1996. |  | version 1.3", RFC 1951, May 1996. |
| RFC 1951 is an Informational RFC, thus it might be less |  |  |
| stable than this specification. On the other hand, this |  |  |
| downward reference was present since the publication of |  |  |
| RFC 2068 in 1997, therefore it is unlikely to cause |  |  |
| problems in practice. See also [BCP97]. |  |  |
| [RFC1952] Deutsch, P., Gailly, J-L., Adler, M., Deutsch, L., and G. |  | [RFC1952] Deutsch, P., Gailly, J-L., Adler, M., Deutsch, L., and G. |
| Randers-Pehrson, "GZIP file format specification version |  | Randers-Pehrson, "GZIP file format specification version |
| 4.3", RFC 1952, May 1996. |  | 4.3", RFC 1952, May 1996. |
| RFC 1952 is an Informational RFC, thus it might be less |  |  |
| stable than this specification. On the other hand, this |  |  |
| downward reference was present since the publication of |  |  |
| RFC 2068 in 1997, therefore it is unlikely to cause |  |  |
| problems in practice. See also [BCP97]. |  |  |
| [RFC2045] Freed, N. and N. Borenstein, "Multipurpose Internet Mail |  | [RFC2045] Freed, N. and N. Borenstein, "Multipurpose Internet Mail |
| Extensions (MIME) Part One: Format of Internet Message |  | Extensions (MIME) Part One: Format of Internet Message |
| Bodies", RFC 2045, November 1996. |  | Bodies", RFC 2045, November 1996. |
| [RFC2046] Freed, N. and N. Borenstein, "Multipurpose Internet Mail |  | [RFC2046] Freed, N. and N. Borenstein, "Multipurpose Internet Mail |
| Extensions (MIME) Part Two: Media Types", RFC 2046, |  | Extensions (MIME) Part Two: Media Types", RFC 2046, |
| November 1996. |  | November 1996. |
| [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, March 1997. |  | Requirement Levels", BCP 14, RFC 2119, March 1997. |
| skipping to change at page 29, line 10 |  | skipping to change at page 28, line 40 |
| Tags", BCP 47, RFC 4647, September 2006. |  | Tags", BCP 47, RFC 4647, September 2006. |
| [RFC5234] Crocker, D., Ed. and P. Overell, "Augmented BNF for Syntax |  | [RFC5234] Crocker, D., Ed. and P. Overell, "Augmented BNF for Syntax |
| Specifications: ABNF", STD 68, RFC 5234, January 2008. |  | Specifications: ABNF", STD 68, RFC 5234, January 2008. |
| [RFC5646] Phillips, A., Ed. and M. Davis, Ed., "Tags for Identifying |  | [RFC5646] Phillips, A., Ed. and M. Davis, Ed., "Tags for Identifying |
| Languages", BCP 47, RFC 5646, September 2009. |  | Languages", BCP 47, RFC 5646, September 2009. |
| 10.2. Informative References |  | 10.2. Informative References |
| [BCP97] Klensin, J. and S. Hartman, "Handling Normative References |  |  |
| to Standards-Track Documents", BCP 97, RFC 4897, |  |  |
| June 2007. |  |  |
| [RFC1945] Berners-Lee, T., Fielding, R., and H. Nielsen, "Hypertext |  | [RFC1945] Berners-Lee, T., Fielding, R., and H. Nielsen, "Hypertext |
| Transfer Protocol -- HTTP/1.0", RFC 1945, May 1996. |  | Transfer Protocol -- HTTP/1.0", RFC 1945, May 1996. |
| [RFC2049] Freed, N. and N. Borenstein, "Multipurpose Internet Mail |  | [RFC2049] Freed, N. and N. Borenstein, "Multipurpose Internet Mail |
| Extensions (MIME) Part Five: Conformance Criteria and |  | Extensions (MIME) Part Five: Conformance Criteria and |
| Examples", RFC 2049, November 1996. |  | Examples", RFC 2049, November 1996. |
| [RFC2068] Fielding, R., Gettys, J., Mogul, J., Nielsen, H., and T. |  | [RFC2068] Fielding, R., Gettys, J., Mogul, J., Nielsen, H., and T. |
| Berners-Lee, "Hypertext Transfer Protocol -- HTTP/1.1", |  | Berners-Lee, "Hypertext Transfer Protocol -- HTTP/1.1", |
| RFC 2068, January 1997. |  | RFC 2068, January 1997. |
| skipping to change at page 36, line 49 |  | skipping to change at page 36, line 28 |
| o <http://tools.ietf.org/wg/httpbis/trac/ticket/113>: "language tag |  | o <http://tools.ietf.org/wg/httpbis/trac/ticket/113>: "language tag |
| matching (Accept-Language) vs RFC4647" |  | matching (Accept-Language) vs RFC4647" |
| o <http://tools.ietf.org/wg/httpbis/trac/ticket/121>: "RFC 1806 has |  | o <http://tools.ietf.org/wg/httpbis/trac/ticket/121>: "RFC 1806 has |
| been replaced by RFC2183" |  | been replaced by RFC2183" |
| Other changes: |  | Other changes: |
| o <http://tools.ietf.org/wg/httpbis/trac/ticket/68>: "Encoding |  | o <http://tools.ietf.org/wg/httpbis/trac/ticket/68>: "Encoding |
| References Normative" -- rephrase the annotation and reference |  | References Normative" -- rephrase the annotation and reference |
| [BCP97]. |  | BCP97. |
| E.6. Since draft-ietf-httpbis-p3-payload-04 |  | E.6. Since draft-ietf-httpbis-p3-payload-04 |
| Closed issues: |  | Closed issues: |
| o <http://tools.ietf.org/wg/httpbis/trac/ticket/132>: "RFC 2822 is |  | o <http://tools.ietf.org/wg/httpbis/trac/ticket/132>: "RFC 2822 is |
| updated by RFC 5322" |  | updated by RFC 5322" |
| Ongoing work on ABNF conversion |  | Ongoing work on ABNF conversion |
| (<http://tools.ietf.org/wg/httpbis/trac/ticket/36>): |  | (<http://tools.ietf.org/wg/httpbis/trac/ticket/36>): |
| skipping to change at page 41, line 12 |  | skipping to change at page 40, line 35 |
| o <http://tools.ietf.org/wg/httpbis/trac/ticket/285>: "Strength of |  | o <http://tools.ietf.org/wg/httpbis/trac/ticket/285>: "Strength of |
| requirements on Accept re: 406" |  | requirements on Accept re: 406" |
| E.18. Since draft-ietf-httpbis-p3-payload-16 |  | E.18. Since draft-ietf-httpbis-p3-payload-16 |
| Closed issues: |  | Closed issues: |
| o <http://tools.ietf.org/wg/httpbis/trac/ticket/186>: "Document |  | o <http://tools.ietf.org/wg/httpbis/trac/ticket/186>: "Document |
| HTTP's error-handling philosophy" |  | HTTP's error-handling philosophy" |
|  |  | E.19. Since draft-ietf-httpbis-p3-payload-17 |
|  |  | Closed issues: |
|  |  | o <http://tools.ietf.org/wg/httpbis/trac/ticket/323>: "intended |
|  |  | maturity level vs normative references" |
| Index |  | Index |
| A |  | A |
| Accept header field 16 |  | Accept header field 16 |
| Accept-Charset header field 18 |  | Accept-Charset header field 18 |
| Accept-Encoding header field 19 |  | Accept-Encoding header field 19 |
| Accept-Language header field 20 |  | Accept-Language header field 20 |
| C |  | C |
| Coding Format |  | Coding Format |
End of changes. 26 change blocks.
| 58 lines changed or deleted |  | 44 lines changed or added |
This html diff was produced by rfcdiff 1.38. The latest version is available from http://tools.ietf.org/tools/rfcdiff/