draft-ietf-httpbis-bcp56bis-08.txt   draft-ietf-httpbis-bcp56bis-latest.txt 
HTTP Working Group M. Nottingham HTTP Working Group M. Nottingham
Internet-Draft November 9, 2018 Internet-Draft December 5, 2018
Obsoletes: 3205 (if approved) Obsoletes: 3205 (if approved)
Intended status: Best Current Practice Intended status: Best Current Practice
Expires: May 13, 2019 Expires: June 8, 2019
Building Protocols with HTTP Building Protocols with HTTP
draft-ietf-httpbis-bcp56bis-08 draft-ietf-httpbis-bcp56bis-latest
Abstract Abstract
HTTP is often used as a substrate for other application protocols HTTP is often used as a substrate for other application protocols
(a.k.a. HTTP-based APIs). This document specifies best practices (a.k.a. HTTP-based APIs). This document specifies best practices
for such protocols' use of HTTP when they are defined for diverse for such protocols' use of HTTP when they are defined for diverse
implementation and broad deployment (e.g., in standards efforts). implementation and broad deployment (e.g., in standards efforts).
Note to Readers Note to Readers
skipping to change at page 1, line 44 skipping to change at page 1, line 44
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 13, 2019. This Internet-Draft will expire on June 8, 2019.
Copyright Notice Copyright Notice
Copyright (c) 2018 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
skipping to change at page 10, line 32 skipping to change at page 10, line 32
If an application using HTTP has browser compatibility as a goal, If an application using HTTP has browser compatibility as a goal,
client interaction ought to be defined in terms of [FETCH], since client interaction ought to be defined in terms of [FETCH], since
that is the abstraction that browsers use for HTTP; it enforces many that is the abstraction that browsers use for HTTP; it enforces many
of these best practices. of these best practices.
Applications using HTTP MUST NOT require HTTP features that are Applications using HTTP MUST NOT require HTTP features that are
usually negotiated to be supported by clients. For example, usually negotiated to be supported by clients. For example,
requiring that clients support responses with a certain content- requiring that clients support responses with a certain content-
coding ([I-D.ietf-httpbis-semantics], Section 6.2.2) instead of coding ([I-D.ietf-httpbis-semantics], Section 6.2.2) instead of
negotiating for it ({{?I-D.ietf-httpbis-semantics, Section 8.4.4) negotiating for it ([I-D.ietf-httpbis-semantics], Section 8.4.4)
means that otherwise conformant clients cannot interoperate with the means that otherwise conformant clients cannot interoperate with the
application. Applications MAY encourage the implementation of such application. Applications MAY encourage the implementation of such
features, though. features, though.
4.4. HTTP URLs 4.4. HTTP URLs
In HTTP, URLs are opaque identifiers under the control of the server. In HTTP, URLs are opaque identifiers under the control of the server.
As outlined in [RFC7320], standards cannot usurp this space, since it As outlined in [RFC7320], standards cannot usurp this space, since it
might conflict with existing resources, and constrain implementation might conflict with existing resources, and constrain implementation
and deployment. and deployment.
skipping to change at page 28, line 7 skipping to change at page 28, line 7
<https://www.w3.org/TR/2016/WD-CSP3-20160913>. <https://www.w3.org/TR/2016/WD-CSP3-20160913>.
[FETCH] WHATWG, "Fetch - Living Standard", n.d., [FETCH] WHATWG, "Fetch - Living Standard", n.d.,
<https://fetch.spec.whatwg.org>. <https://fetch.spec.whatwg.org>.
[HTML5] WHATWG, "HTML - Living Standard", n.d., [HTML5] WHATWG, "HTML - Living Standard", n.d.,
<https://html.spec.whatwg.org>. <https://html.spec.whatwg.org>.
[I-D.ietf-httpbis-header-structure] [I-D.ietf-httpbis-header-structure]
Nottingham, M. and P. Kamp, "Structured Headers for HTTP", Nottingham, M. and P. Kamp, "Structured Headers for HTTP",
draft-ietf-httpbis-header-structure-08 (work in progress), draft-ietf-httpbis-header-structure-09 (work in progress),
October 2018. December 2018.
[I-D.ietf-httpbis-rfc6265bis] [I-D.ietf-httpbis-rfc6265bis]
Barth, A. and M. West, "Cookies: HTTP State Management Barth, A. and M. West, "Cookies: HTTP State Management
Mechanism", draft-ietf-httpbis-rfc6265bis-02 (work in Mechanism", draft-ietf-httpbis-rfc6265bis-02 (work in
progress), August 2017. progress), August 2017.
[I-D.nottingham-rfc5785bis] [I-D.nottingham-rfc5785bis]
Nottingham, M., "Well-Known Uniform Resource Identifiers Nottingham, M., "Well-Known Uniform Resource Identifiers
(URIs)", draft-nottingham-rfc5785bis-08 (work in (URIs)", draft-nottingham-rfc5785bis-08 (work in
progress), October 2018. progress), October 2018.
 End of changes. 6 change blocks. 
7 lines changed or deleted 7 lines changed or added

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