"Pending" Responses for the Constrained Application Protocol (CoAP)
draft-hartke-core-pending-02
Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
---|---|---|---|
Authors | Peter Van der Stok , Klaus Hartke | ||
Last updated | 2018-08-30 (Latest revision 2018-02-26) | ||
RFC stream | (None) | ||
Intended RFC status | (None) | ||
Formats | |||
Stream | Stream state | (No stream defined) | |
Consensus boilerplate | Unknown | ||
RFC Editor Note | (None) | ||
IESG | IESG state | Expired | |
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 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
Klaus Hartke
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)