security architecture for 6top: requirements and structure
draft-richardson-6tisch-security-architecture-02
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Michael Richardson | ||
| Last updated | 2014-11-10 (Latest revision 2014-04-28) | ||
| 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 details security requirements for 6tisch nodes that use 6top in an industrial settings. Layer-2 and a layer-4 authentication and authorization requirements and assumptions are identified. Two approaches to accomplishing these requirements are outlined, with the goal of eventually picking one. This internet-draft is intended for later inclusion into the 6tisch architecture document.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)