Diet-IPsec: Requirements for new IPsec/ESP protocols according to IoT use cases
draft-mglt-ipsecme-diet-esp-requirements-00
| Document | Type | Expired Internet-Draft (individual) | |
|---|---|---|---|
| Authors | Daniel Migault , Tobias Guggemos | ||
| Last updated | 2015-01-03 (Latest revision 2014-07-02) | ||
| Stream | (None) | ||
| Formats |
Expired & archived
plain text
xml
pdf
htmlized
pdfized
bibtex
|
||
| 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 can be found at:
https://www.ietf.org/archive/id/draft-mglt-ipsecme-diet-esp-requirements-00.txt
https://www.ietf.org/archive/id/draft-mglt-ipsecme-diet-esp-requirements-00.txt
Abstract
IPsec/ESP is used to secure end-to-end communications. This document lists the requirements Diet-ESP should meet to design IPsec/ESP for IoT.
Authors
Daniel Migault
Tobias Guggemos
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)