EAP-based Authentication Service for CoAP
draft-marin-ace-wg-coap-eap-04
| Document | Type |
This is an older version of an Internet-Draft whose latest revision state is "Expired".
Expired & archived
|
|
|---|---|---|---|
| Authors | Rafael Marin-Lopez , Dan Garcia-Carrillo | ||
| Last updated | 2017-04-24 (Latest revision 2016-10-21) | ||
| RFC stream | (None) | ||
| Formats | |||
| Additional resources | |||
| Stream | Stream state | (No stream defined) | |
| Associated None milestones |
|
||
| 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 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 Marin-Lopez
Dan Garcia-Carrillo
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)