Identity Protection within EAP-TLS
draft-urien-badra-eap-tls-identity-protection-01
| Document | Type | Expired Internet-Draft (individual) | |
|---|---|---|---|
| Authors | Pascal Urien , Mohamad Badra | ||
| Last updated | 2006-10-19 | ||
| Stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats |
Expired & archived
plain text
htmlized
pdfized
bibtex
|
||
| 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) |
https://www.ietf.org/archive/id/draft-urien-badra-eap-tls-identity-protection-01.txt
Abstract
This document defines a mechanism that ensures EAP-TLS identity protection. The main idea is to encrypt the client's certificate. Three procedures are proposed in order to determine the certificate encryption mechanism, - Implicit, the client's certificate is encrypted according to a pre-defined algorithm, deduced from the server's certificate. - Notified, the EAP-identity response message, delivered by the client includes information that precise the encryption algorithm to be used. - Negotiated, the client indicates a list of encryption algorithm, the server chooses one of them, and indicates its choice.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)