CoAP Minimum Block Time
draft-greevenbosch-core-block-minimum-time-00
| Document | Type |
Replaced Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Bert Greevenbosch | ||
| Last updated | 2012-10-08 (Latest revision 2012-07-08) | ||
| Replaced by | draft-greevenbosch-core-minimum-request-interval | ||
| RFC stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Replaced by draft-greevenbosch-core-minimum-request-interval | |
| 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 "MinimumBlockTime" option for CoAP, which can be used to negotiate the minimum time between two subsequent block requests. It can be used for overload and congestion control. 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.)