Profiling of DTLS for CoAP-based IoT Applications
draft-keoh-dice-dtls-profile-iot-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Sye Loong Keoh , Sandeep Kumar , Zach Shelby | ||
| Last updated | 2014-05-09 (Latest revision 2013-11-05) | ||
| 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 collects various implementation challenges of DTLS on embedded systems, and proposes a profile of DTLS for CoAP-based Internet of Things (IoT) applications. Specially, this document investigate the application features and functionality of DTLS protocol, the fragmentation issue of DTLS Handshake protocol, and the complexity of the DTLS Handshake state machine. A RESTful DTLS Handshake which relies on CoAP Block-wise Transfer is proposed to address the fragmentation issue. The next step is to define a DTLS profile for embedded systems.
Authors
Sye Loong Keoh
Sandeep Kumar
Zach Shelby
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)