Security Framework and Key Management Protocol Requirements for 6TSCH
draft-ohba-6tsch-security-01
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Stephen Chasko, Subir Das , Rafael Marin-Lopez , Yoshihiro Ohba , Pascal Thubert , Alper E. Yegin | ||
| Last updated | 2014-01-13 (Latest revision 2013-07-12) | ||
| 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
Since 6TSCH forms layer 3 meshes over IPv6, use of key management protocols defined at layer 3 or above matches the target architecture so they can apply for the process by a new device of joining the mesh to extend it. This document details that particular operation within the whole 6TSCH architecture.
Authors
Stephen Chasko
Subir Das
Rafael Marin-Lopez
Yoshihiro Ohba
Pascal Thubert
Alper E. Yegin
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)