EAP-based Authentication Service for CoAP
draft-marin-ace-wg-coap-eap-06
| Document | Type | Expired Internet-Draft (individual) | |
|---|---|---|---|
| Last updated | 2018-04-28 (latest revision 2017-10-25) | ||
| Stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats |
Expired & archived
plain text
pdf
html
bibtex
|
||
| Stream | Stream state | (No stream defined) | |
| Consensus Boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Expired | |
| Telechat date | |||
| 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-marin-ace-wg-coap-eap-06.txt
https://www.ietf.org/archive/id/draft-marin-ace-wg-coap-eap-06.txt
Abstract
This document describes an authentication service that uses EAP transported by means of CoAP messages with two purposes: o Authenticate two CoAP endpoints. o Bootstrap key material to protect CoAP messages exchanged between them.
Authors
Rafael Lopez
(rafa@um.es)
Dan Garcia
(dan.garcia@um.es)
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)