Security Framework and Key Management Protocol Requirements for 6TiSCH
draft-ohba-6tisch-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-09-23 (Latest revision 2014-03-22) | ||
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
6TiSCH is enabling IPv6 over the TSCH mode of the IEEE802.15.4e standard that allows the IEEE 802.15.4e TSCH wireless networks and nodes to connect to the backbone network via layer 3 meshes over IPv6. In this operation of network architecture, understanding the security framework and requirements for key management protocols are critical. This document discusses such security framework and key management protocol requirements by highlighting different phases of key management in which a new node can securely join the network under the purview of overall 6TiSCH 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.)