Spinel Host-Controller Protocol
draft-rquattle-spinel-unified-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Robert S. Quattlebaum , james woodyatt | ||
| Last updated | 2017-11-13 (Latest revision 2017-05-09) | ||
| 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 describes the Spinel protocol, which facilitates the control and management of IPv6 network interfaces on devices where general purpose application processors offload network functions at their interfaces to network co-processors (NCP) connected by simple communication links like serial data channels. While initially developed to support Thread(R), Spinel's layered design allows it to be easily adapted to other similar network technologies. This document also describes various Spinel specializations, including support for the Thread(R) low-power mesh network technology.
Authors
Robert S. Quattlebaum
james woodyatt
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)