Requirements for CoAP End-To-End Security
draft-hartke-core-e2e-security-reqs-02
| Document | Type |
This is an older version of an Internet-Draft whose latest revision state is "Expired".
Expired & archived
|
|
|---|---|---|---|
| Authors | Göran Selander , Francesca Palombini , Klaus Hartke | ||
| Last updated | 2017-07-17 (Latest revision 2017-01-06) | ||
| RFC stream | (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 analyses threats to CoAP message exchanges traversing proxies and derives the security requirements for mitigating those threats.
Authors
Göran Selander
Francesca Palombini
Klaus Hartke
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)