Last Call Review of draft-ietf-core-problem-details-05
review-ietf-core-problem-details-05-genart-lc-mishra-2022-06-13-00
| Request | Review of | draft-ietf-core-problem-details |
|---|---|---|
| Requested revision | No specific revision (document currently at 08) | |
| Type | IETF Last Call Review | |
| Team | General Area Review Team (Gen-ART) (genart) | |
| Deadline | 2022-06-10 | |
| Requested | 2022-05-27 | |
| Authors | Thomas Fossati , Carsten Bormann | |
| I-D last updated | 2022-10-19 (Latest revision 2022-07-06) | |
| Completed reviews |
I18ndir IETF Last Call review of -05
by Harald T. Alvestrand
(diff)
Artart IETF Last Call review of -05 by Harald T. Alvestrand (diff) Opsdir IETF Last Call review of -04 by Joel Jaeggli (diff) Genart IETF Last Call review of -05 by Gyan Mishra (diff) Secdir Telechat review of -05 by Yoav Nir (diff) |
|
| Assignment | Reviewer | Gyan Mishra |
| State | Completed | |
| Request | IETF Last Call review on draft-ietf-core-problem-details by General Area Review Team (Gen-ART) Assigned | |
| Posted at | https://mailarchive.ietf.org/arch/msg/gen-art/7aBXjJEt7iqTjvpIytdLkzToA3Y | |
| Reviewed revision | 05 (document currently at 08) | |
| Result | Ready | |
| Completed | 2022-06-13 |
review-ietf-core-problem-details-05-genart-lc-mishra-2022-06-13-00
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.