Accept-Any option for CoAP
draft-amsuess-core-accept-any-00
| Document | Type | Expired Internet-Draft (individual) | |
|---|---|---|---|
| Author | Christian Amsüss | ||
| Last updated | 2019-09-26 (Latest revision 2019-03-25) | ||
| Stream | (None) | ||
| Formats |
Expired & archived
plain text
xml
htmlized
pdfized
bibtex
|
||
| 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 can be found at:
https://www.ietf.org/archive/id/draft-amsuess-core-accept-any-00.txt
https://www.ietf.org/archive/id/draft-amsuess-core-accept-any-00.txt
Abstract
This memoy defines the Accept-Any option, which provides a more flexible content negotiation than the one originally specified for the Constrained Application Protocol (CoAP) in [RFC7252]. As this is particularly useful with but ruled out in CoAP observation ([RFC7641]), that is updated to allow it.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)