Last Call: <draft-ietf-httpbis-bcp56bis-12.txt> (Building Protocols with HTTP) to Best Current Practice

The IESG <iesg-secretary@ietf.org> Sat, 10 July 2021 03:02 UTC

Return-Path: <iesg-secretary@ietf.org>
X-Original-To: ietf-announce@ietf.org
Delivered-To: ietf-announce@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 2E09C3A16A7; Fri, 9 Jul 2021 20:02:46 -0700 (PDT)
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: Last Call: <draft-ietf-httpbis-bcp56bis-12.txt> (Building Protocols with HTTP) to Best Current Practice
X-Test-IDTracker: no
X-IETF-IDTracker: 7.34.0
Auto-Submitted: auto-generated
Precedence: bulk
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
Reply-To: last-call@ietf.org
Sender: <iesg-secretary@ietf.org>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
Message-ID: <162588616610.30089.1126728046480090005@ietfa.amsl.com>
Date: Fri, 09 Jul 2021 20:02:46 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-announce/5KoUIEFR4-LKt9OcEB642cfl1Ng>
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.29
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf-announce/>
List-Post: <mailto:ietf-announce@ietf.org>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 10 Jul 2021 03:02:46 -0000

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))