Problem Details For CoAP APIs
draft-ietf-core-problem-details-01
| Document | Type | Expired Internet-Draft (core WG) | |
|---|---|---|---|
| Authors | Thomas Fossati , Jaime Jimenez , Klaus Hartke | ||
| Last updated | 2021-01-14 (Latest revision 2020-07-13) | ||
| Replaces | draft-fossati-core-coap-problem | ||
| Stream | Internet Engineering Task Force (IETF) | ||
| Formats |
Expired & archived
plain text
html
xml
htmlized
pdfized
bibtex
|
||
| Stream | WG state | WG Document | |
| Document shepherd | (None) | ||
| IESG | IESG state | Expired | |
| Consensus boilerplate | Unknown | ||
| Telechat date | (None) | ||
| Responsible AD | (None) | ||
| Send notices to | (None) |
https://www.ietf.org/archive/id/draft-ietf-core-problem-details-01.txt
Abstract
This document defines a "problem detail" as a way to carry machine- readable details of errors in a CoAP response to avoid the need to define new error response formats for CoAP APIs. The proposed format is inspired by the Problem Details for HTTP APIs defined in RFC 7807. 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/core-wg/core-problem-details (https://github.com/ core-wg/core-problem-details).
Authors
Thomas Fossati
Jaime Jimenez
Klaus Hartke
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)