EAP defaults for devices that need to onboard
draft-richardson-emu-eap-onboarding-05
| Document | Type |
Replaced Internet-Draft
(emu WG)
Expired & archived
|
|
|---|---|---|---|
| Authors | Alan DeKok , Michael Richardson | ||
| Last updated | 2026-02-02 (Latest revision 2026-01-01) | ||
| Replaced by | draft-ietf-emu-eap-onboarding | ||
| RFC stream | Internet Engineering Task Force (IETF) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Additional resources | Mailing list discussion | ||
| Stream | WG state | Adopted by a WG | |
| Document shepherd | (None) | ||
| IESG | IESG state | Replaced by draft-ietf-emu-eap-onboarding | |
| Consensus boilerplate | Unknown | ||
| 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 a method by which an unconfigured device can use EAP-TLS to join a network on which further device onboarding, network attestation or other remediation can be done. While RFC 5216 supports EAP-TLS without a client certificate, that document defines no method by which unauthenticated EAP-TLS can be used. This draft addresses that issue.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)