"Pending" Responses for the Constrained Application Protocol (CoAP)
draft-hartke-core-pending-02

Document Type Expired Internet-Draft (individual)
Last updated 2018-08-30 (latest revision 2018-02-26)
Stream (None)
Intended RFC status (None)
Formats
Expired & archived
plain text pdf html bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state Expired
Telechat date
Responsible AD (None)
Send notices to (None)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft can be found at
https://www.ietf.org/archive/id/draft-hartke-core-pending-02.txt

Abstract

This document proposes a new type of response for the Constrained Application Protocol (CoAP) called a "Pending" response. A CoAP server can use a Pending response to indicate that it has accepted a request but has not yet started processing it or that processing the request will take longer than a client is typically willing to wait for a response.

Authors

Peter Van der Stok (consultancy@vanderstok.org)
Klaus Hartke (hartke@tzi.org)

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)