IETF Logo Mail Archive

[httpapi] Last Call: <draft-ietf-httpapi-rfc7807bis-04.txt> (Problem Details for HTTP APIs) to Proposed Standard

The IESG <iesg-secretary@ietf.org> Thu, 20 October 2022 13:24 UTC

Return-Path: <iesg-secretary@ietf.org>
X-Original-To: httpapi@ietf.org
Delivered-To: httpapi@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 10F95C14CE20; Thu, 20 Oct 2022 06:24:06 -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>
X-Test-IDTracker: no
X-IETF-IDTracker: 8.18.0
Auto-Submitted: auto-generated
Precedence: bulk
CC: darrel@tavis.ca, draft-ietf-httpapi-rfc7807bis@ietf.org, httpapi-chairs@ietf.org, httpapi@ietf.org, superuser@gmail.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: <166627224606.10641.5749459667185024591@ietfa.amsl.com>
Date: Thu, 20 Oct 2022 06:24:06 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/httpapi/JbAEVGnwMvOmkwNbAPwY_3xCHsE>
Subject: [httpapi] Last Call: <draft-ietf-httpapi-rfc7807bis-04.txt> (Problem Details for HTTP APIs) to Proposed Standard
X-BeenThere: httpapi@ietf.org
X-Mailman-Version: 2.1.39
List-Id: Building Blocks for HTTP APIs <httpapi.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/httpapi>, <mailto:httpapi-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/httpapi/>
List-Post: <mailto:httpapi@ietf.org>
List-Help: <mailto:httpapi-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/httpapi>, <mailto:httpapi-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 20 Oct 2022 13:24:06 -0000

The IESG has received a request from the Building Blocks for HTTP APIs WG
(httpapi) to consider the following document: - 'Problem Details for HTTP
APIs'
  <draft-ietf-httpapi-rfc7807bis-04.txt> as Proposed Standard

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 2022-11-03. 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


   This document defines a "problem detail" to carry machine-readable
   details of errors in HTTP response content and/or fields to avoid the
   need to define new error response formats for HTTP APIs.

   This document obsoletes RF7807.

Discussion Venues

   This note is to be removed before publishing as an RFC.

   Source for this draft and an issue tracker can be found at
   https://github.com/ietf-wg-httpapi/rfc7807bis.




The file can be obtained via
https://datatracker.ietf.org/doc/draft-ietf-httpapi-rfc7807bis/



No IPR declarations have been submitted directly on this I-D.

v2.23.0 | Report a Bug | By Email