The application/maybe media type
draft-bormann-core-maybe-00
| Document | Type |
Replaced Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Carsten Bormann | ||
| Last updated | 2018-03-18 | ||
| Replaced by | RFC 8710 | ||
| 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-ietf-core-multipart-ct | |
| 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
Many media types may be used in situations where it may beneficial to indicate that the object represented in this media type is not yet (or no longer) present. The Observe option introduced in Observing Resources in the Constrained Application Protocol (CoAP) (RFC7641) requires sequences of responses (notifications) to carry the same Content-Format. The application/maybe media type provides a way to use a single media type (and thus Content-Format) to express presence or absence of information in a specific media type.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)