- From: The IESG <iesg-secretary@ietf.org>
- Date: Fri, 09 Jul 2021 20:02:46 -0700
- To: "IETF-Announce" <ietf-announce@ietf.org>
- CC: Tommy Pauly <tpauly@apple.com>, draft-ietf-httpbis-bcp56bis@ietf.org, francesca.palombini@ericsson.com, httpbis-chairs@ietf.org, ietf-http-wg@w3.org, tpauly@apple.com
The IESG has received a request from the HTTP WG (httpbis) to consider the following document: - 'Building Protocols with HTTP' <draft-ietf-httpbis-bcp56bis-12.txt> as Best Current Practice The IESG plans to make a decision in the next few weeks, and solicits final comments on this action. Please send substantive comments to the last-call@ietf.org mailing lists by 2021-07-23. Exceptionally, comments may be sent to iesg@ietf.org instead. In either case, please retain the beginning of the Subject line to allow automated sorting. Abstract Applications often use HTTP as a substrate to create HTTP-based APIs. This document specifies best practices for writing specifications that use HTTP to define new application protocols. It is written primarily to guide IETF efforts to define application protocols using HTTP for deployment on the Internet, but might be applicable in other situations. The file can be obtained via https://datatracker.ietf.org/doc/draft-ietf-httpbis-bcp56bis/ No IPR declarations have been submitted directly on this I-D. The document contains these normative downward references. See RFC 3967 for additional information: rfc6454: The Web Origin Concept (Proposed Standard - Internet Engineering Task Force (IETF)) rfc7301: Transport Layer Security (TLS) Application-Layer Protocol Negotiation Extension (Proposed Standard - Internet Engineering Task Force (IETF)) rfc8288: Web Linking (Proposed Standard - Internet Engineering Task Force (IETF)) rfc8615: Well-Known Uniform Resource Identifiers (URIs) (Proposed Standard - Internet Engineering Task Force (IETF)) draft-ietf-httpbis-semantics: HTTP Semantics (None - Internet Engineering Task Force (IETF))
Received on Saturday, 10 July 2021 03:03:00 UTC