CoAP Minimum Request Interval
draft-greevenbosch-core-minimum-request-interval-01
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Bert Greevenbosch | ||
| Last updated | 2013-11-04 (Latest revision 2013-04-26) | ||
| Replaces | draft-greevenbosch-core-block-minimum-time | ||
| 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 defines an "Minimum-Request-Interval" option for CoAP, which can be used to negotiate the minimum time between two subsequent requests within a single client and server pair. It can be used for flow and congestion control, reducing the consumption of server and network resources when needed. Note Discussion and suggestions for improvement are requested, and should be sent to core@ietf.org.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)