Enabling Security/Privacy Addressing On 6LoWPAN Technologies
draft-thaler-6lo-privacy-addrs-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Dave Thaler | ||
| Last updated | 2015-08-20 (Latest revision 2015-02-16) | ||
| 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
It is commonly assumed today that 6LowPAN header compression is incompatible (or at least inefficient) with the notion of using addresses with sufficient entropy to mitigate various security and privacy threats. This draft explores ways one might dispel that notion, and discusses how security/privacy addressing might be used on 6LoWPAN technologies without additional overhead in data packets.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)