- From: Poul-Henning Kamp <phk@phk.freebsd.dk>
- Date: Wed, 21 Apr 2021 08:20:40 +0000
- To: Mark Nottingham <mnot@mnot.net>
- cc: "ietf-http-wg@w3.org Group" <ietf-http-wg@w3.org>
-------- Mark Nottingham writes: > [However,] > this BCP is for IETF standards-based HTTP APIs, not all HTTP APIs or all > uses of HTTP. Given that the IETF is focused on internetworking, the > examples of localhost APIs don't seem very applicable here. In the last para before 1.1 that is said quite clearly, but the abstract feels a bit wishy-washy. Proposed abstract: HTTP is often used as a substrate for other application protocols to create HTTP-based APIs. This document specifies best practices for writing specifications that use HTTP to define new application protocols for deployment on the Internet, (e.g., in standards efforts). We should not need to spell out that "other situations" (as the para before 1.1 calls them) would be smart to use them as well. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence.
Received on Wednesday, 21 April 2021 08:21:00 UTC