[core] Genart last call review of draft-ietf-core-problem-details-05

Gyan Mishra via Datatracker <noreply@ietf.org> Mon, 13 June 2022 14:13 UTC

MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Gyan Mishra via Datatracker <noreply@ietf.org>
To: gen-art@ietf.org
Cc: core@ietf.org, draft-ietf-core-problem-details.all@ietf.org, last-call@ietf.org
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <165512961019.45433.2445215652270464045@ietfa.amsl.com>
Reply-To: Gyan Mishra <hayabusagsm@gmail.com>
Date: Mon, 13 Jun 2022 07:13:30 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/core/N88zQgh4PSxA_fasA5dVcIjLS7A>
Subject: [core] Genart last call review of draft-ietf-core-problem-details-05

Reviewer: Gyan Mishra
Review result: Ready

I am the assigned Gen-ART reviewer for this draft. The General Area
Review Team (Gen-ART) reviews all IETF documents being processed
by the IESG for the IETF Chair.  Please treat these comments just
like any other last call comments.

For more information, please see the FAQ at

<https://trac.ietf.org/trac/gen/wiki/GenArtfaq>.

Document: draft-ietf-core-problem-details-??
Reviewer: Gyan Mishra
Review Date: 2022-06-13
IETF LC End Date: 2022-06-10
IESG Telechat date: 2022-06-16

Summary:

This document defines a concise "problem detail" as a way to carry
machine-readable details of errors in a REST response to avoid the
need to define new error response formats for REST APIs for
constrained environments.  The format is inspired by, but intended to be more
concise than, the Problem Details for HTTP APIs defined in RFC 7807.

Major issues:
None
Minor issues:
None
Nits/editorial comments:
Should specify exactly which RFC is being replaced or updated by this draft and
not XXX.

[core] Genart last call review of draft-ietf-core… Gyan Mishra via Datatracker
Re: [core] [Last-Call] Genart last call review of… Lars Eggert