<?xml version="1.0" encoding="UTF-8"?>
<reference anchor="I-D.ietf-core-problem-details" target="https://datatracker.ietf.org/doc/html/draft-ietf-core-problem-details-02">
   <front>
      <title>Concise Problem Details For CoAP APIs</title>
      <author initials="T." surname="Fossati" fullname="Thomas Fossati">
         <organization>arm</organization>
      </author>
      <author initials="C." surname="Bormann" fullname="Carsten Bormann">
         <organization>Universität Bremen TZI</organization>
      </author>
      <date month="April" day="27" year="2022" />
      <abstract>
	 <t>   This document defines a &quot;problem detail&quot; 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.  The format is
   inspired by, but intended to be more concise than, the Problem
   Details for HTTP APIs defined in RFC 7807.

	 </t>
      </abstract>
   </front>
   <seriesInfo name="Internet-Draft" value="draft-ietf-core-problem-details-02" />
   
</reference>
