Use cases and requirements for authentication and authorisation in CoAP
draft-greevenbosch-core-authreq-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Bert Greevenbosch | ||
| Last updated | 2014-03-10 (Latest revision 2013-09-06) | ||
| 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 draft describes use cases and requirements for authenticated and authorised CoAP. The draft especially focuses on threats and their prevention. Note Discussion and suggestions for improvement are requested, and should be sent to core@ietf.org.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)