A Survey of Authentication Mechanisms
draft-rescorla-auth-mech-01
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Eric Rescorla | ||
| Last updated | 2003-03-06 | ||
| RFC stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| 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) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
Abstract
Authentication is perhaps the most basic security problem for design- ers of network protocols. Even the early Internet protocols such as TELNET and FTP, which provided no other security services, made pro- vision for user authentication. Unfortunately, these early authenti- cation systems were wholly inadequate for the Internet Threat Model [REF] and a vast array of other authentication mechanisms have been introduced in an attempt to close these holes. The most striking thing about these security mechanisms is how many of them are essentially similar. There are only 7 basic classes of authentication protocol but there are a large number of slightly dif- ferent protocols with essentially the same security properties. This memo surveys the space of authentication mechanisms, describes the basic classes and provides examples of protocols which fit into each class.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)