[httpapi] RFC 9457 on Problem Details for HTTP APIs

rfc-editor@rfc-editor.org Tue, 01 August 2023 04:37 UTC

Return-Path: <wwwrun@rfcpa.amsl.com>
X-Original-To: httpapi@ietfa.amsl.com
Delivered-To: httpapi@ietfa.amsl.com
Received: from localhost (localhost []) by ietfa.amsl.com (Postfix) with ESMTP id EB102C151060; Mon, 31 Jul 2023 21:37:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.865
X-Spam-Status: No, score=-0.865 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.249, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, RDNS_NONE=0.793, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=no autolearn_force=no
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id Zp7YHSMHC6vC; Mon, 31 Jul 2023 21:37:41 -0700 (PDT)
Received: from rfcpa.amsl.com (unknown []) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4DFB4C151553; Mon, 31 Jul 2023 21:37:41 -0700 (PDT)
Received: by rfcpa.amsl.com (Postfix, from userid 499) id 18634119E2; Mon, 31 Jul 2023 21:37:41 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
From: rfc-editor@rfc-editor.org
Cc: rfc-editor@rfc-editor.org, drafts-update-ref@iana.org, httpapi@ietf.org
Content-type: text/plain; charset="UTF-8"
Message-Id: <20230801043741.18634119E2@rfcpa.amsl.com>
Date: Mon, 31 Jul 2023 21:37:41 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/httpapi/AkqT4O7tPw8FT_zzMmT69JM4Z-E>
Subject: [httpapi] RFC 9457 on Problem Details for HTTP APIs
X-BeenThere: httpapi@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
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: Tue, 01 Aug 2023 04:37:45 -0000

A new Request for Comments is now available in online RFC libraries.

        RFC 9457

        Title:      Problem Details for HTTP APIs 
        Author:     M. Nottingham,
                    E. Wilde,
                    S. Dalal
        Status:     Standards Track
        Stream:     IETF
        Date:       July 2023
        Mailbox:    mnot@mnot.net,
        Pages:      16
        Obsoletes:  RFC 7807

        I-D Tag:    draft-ietf-httpapi-rfc7807bis-07.txt

        URL:        https://www.rfc-editor.org/info/rfc9457

        DOI:        10.17487/RFC9457

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

This document obsoletes RFC 7807.

This document is a product of the Building Blocks for HTTP APIs Working Group of the IETF.

This is now a Proposed Standard.

STANDARDS TRACK: This document specifies an Internet Standards Track
protocol for the Internet community, and requests discussion and suggestions
for improvements.  Please refer to the current edition of the Official
Internet Protocol Standards (https://www.rfc-editor.org/standards) for the 
standardization state and status of this protocol.  Distribution of this 
memo is unlimited.

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see

For searching the RFC series, see https://www.rfc-editor.org/search
For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk

Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.

The RFC Editor Team
Association Management Solutions, LLC