Skip to main content

Key Derivation for Authentication, Integrity, and Privacy

Document Type Expired Internet-Draft (individual)
Expired & archived
Author Marc Horowitz
Last updated 1997-03-27 (Latest revision 1998-03-17)
RFC stream (None)
Intended RFC status (None)
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:


Recent advances in cryptography have made it desirable to use longer cryptographic keys, and to make more careful use of these keys. In particular, it is considered unwise by some cryptographers to use the same key for multiple purposes. Since most cryptographic-based systems perform a range of functions, such as authentication, key exchange, integrity, and encryption, it is desirable to use different cryptographic keys for these purposes. This RFC does not define a particular protocol, but defines a set of cryptographic transformations for use with arbitrary network protocols and block cryptographic algorithm.


Marc Horowitz

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)