Protocol Action: 'Building Protocols with HTTP' to Best Current Practice (draft-ietf-httpbis-bcp56bis-15.txt)

The IESG <iesg-secretary@ietf.org> Mon, 30 August 2021 15:11 UTC

MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce <ietf-announce@ietf.org>
Subject: Protocol Action: 'Building Protocols with HTTP' to Best Current Practice (draft-ietf-httpbis-bcp56bis-15.txt)
Auto-Submitted: auto-generated
Precedence: bulk
Cc: The IESG <iesg@ietf.org>, Tommy Pauly <tpauly@apple.com>, draft-ietf-httpbis-bcp56bis@ietf.org, francesca.palombini@ericsson.com, httpbis-chairs@ietf.org, ietf-http-wg@w3.org, rfc-editor@rfc-editor.org, tpauly@apple.com
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
Message-ID: <163033631759.6828.1011890165264284497@ietfa.amsl.com>
Date: Mon, 30 Aug 2021 08:11:57 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-announce/nHuTGxD0aD0rVsfka-VYHnJqM5M>

The IESG has approved the following document:
- 'Building Protocols with HTTP'
(draft-ietf-httpbis-bcp56bis-15.txt) as Best Current Practice

This document is the product of the HTTP Working Group.

The IESG contact persons are Murray Kucherawy and Francesca Palombini.

A URL of this Internet Draft is:
https://datatracker.ietf.org/doc/draft-ietf-httpbis-bcp56bis/

Technical Summary:

This document updates advice to applications on how to use HTTP as a substrate for defining APIs. The previous guidance was from 2002, so this document does a lot to incorporate our learnings over the past 20 years.

Working Group Summary:

This document has been in the working group for quite a while now, as it was held for submission alongside the new HTTP core document revision. In general, there is good consensus. The one discussion point that arose in the WGLC which had a bit rougher consensus was about the level of normative requirement required for two issues: specifically, if use of HTTPS (HTTP with TLS) is RECOMMENDED or a MUST; and whether the use of HTTPS is a MUST for all authentication types. Some WG members do not want to make this more strict, since not all use cases for HTTP need or can use TLS; others believe that the use case addressed by this document (HTTP APIs over the Internet) is specific enough that the security requirement is appropriate.

Document Quality:

The document is well-written and carefully reviewed.

Personnel:

Shepherd: Tommy Pauly
Responsible AD: Francesca Palombini

Protocol Action: 'Building Protocols with HTTP' t… The IESG