Credentials Provisioning and Management via EAP (EAP-CPROM)
draft-pala-eap-cprom-00
Document | Type |
Replaced Internet-Draft
(individual)
Expired & archived
|
|
---|---|---|---|
Author | Massimiliano Pala | ||
Last updated | 2019-02-04 | ||
Replaced by | draft-pala-eap-creds | ||
RFC stream | (None) | ||
Intended RFC status | (None) | ||
Formats | |||
Stream | Stream state | (No stream defined) | |
Consensus boilerplate | Unknown | ||
RFC Editor Note | (None) | ||
IESG | IESG state | Replaced by draft-pala-eap-creds | |
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
With the increase number of devices, protocols, and applications that rely on strong credentials (e.g., digital certificates, keys, or tokens) for network access, the need for a standard credentials provisioning layer is paramount. In particular, since EAP is deployed for authentication needs, the authors extend this use-case by including support for provisioning and management of credentials. In particular, this specification defines how to support the provisioning of strong credentials to users and/or devices without the need for providing IP connectivity. The use of EAP not only for provisiong but also for managing network credentials provides a general conduit that can be exploited in different environments (e.g., Wired and WiFi networks credentials management).
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)