Security Framework and Key Management Protocol Requirements for 6TSCH
draft-ohba-6tsch-security-01
| Document | Type | Expired Internet-Draft (individual) | |
|---|---|---|---|
| Last updated | 2014-01-13 (latest revision 2013-07-12) | ||
| Stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats |
Expired & archived
plain text
pdf
html
bibtex
|
||
| Stream | Stream state | (No stream defined) | |
| Consensus Boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Expired | |
| Telechat date | |||
| Responsible AD | (None) | ||
| Send notices to | (None) | ||
https://www.ietf.org/archive/id/draft-ohba-6tsch-security-01.txt
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
(stephen.chasko@landisgyr.com)
Subir Das
(sdas@appcomsci.com)
Rafael Lopez
(rafa@um.es)
Yoshihiro Ohba
(yoshihiro.ohba@toshiba.co.jp)
Pascal Thubert
(pthubert@cisco.com)
Alper Yegin
(alper.yegin@yegin.org)
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)