Problem Details For CoAP APIs
draft-fossati-core-coap-problem-02
| Document | Type |
Replaced Internet-Draft
(core WG)
Expired & archived
|
|
|---|---|---|---|
| Authors | Thomas Fossati , Jaime Jimenez | ||
| Last updated | 2020-03-30 (Latest revision 2020-03-05) | ||
| Replaced by | draft-ietf-core-problem-details | ||
| RFC stream | Internet Engineering Task Force (IETF) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Additional resources | Mailing list discussion | ||
| Stream | WG state | Candidate for WG Adoption | |
| Document shepherd | (None) | ||
| IESG | IESG state | Replaced by draft-ietf-core-problem-details | |
| Consensus boilerplate | Unknown | ||
| Telechat date | (None) | ||
| Responsible AD | (None) | ||
| Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
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.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)