Request-Tag option
draft-amsuess-core-request-tag-00
| Document | Type | Replaced Internet-Draft (individual) | |
|---|---|---|---|
| Last updated | 2017-03-27 | ||
| Replaced by | draft-amsuess-core-repeat-request-tag | ||
| Stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats |
Expired & archived
pdf
htmlized
bibtex
|
||
| Stream | Stream state | (No stream defined) | |
| Consensus Boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Replaced by draft-amsuess-core-repeat-request-tag | |
| Telechat date | |||
| Responsible AD | (None) | ||
| Send notices to | (None) | ||
https://www.ietf.org/archive/id/draft-amsuess-core-request-tag-00.txt
Abstract
This memo describes an optional extension to the Constrained Application Protocol (CoAP, [RFC7252] and [RFC7959]) that allows matching of request blocks. This primarily serves to transfer the security properties that Object Security of CoAP (OSCOAP, [I-D.ietf-core-object-security]) provides for single requests to blockwise transfers. The security of blockwise transfer in OSCOAP is reflected on in a dedicated section.
Authors
Christian Amsüss (c.amsuess@energyharvesting.at)
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)