Wrapping a Hashed Message Authentication Code key with a Triple-Data Encryption Standard Key or an Advanced Encryption Standard Key
RFC 3537, “Wrapping a Hashed Message Authentication Code key with a Triple-Data Encryption Standard Key or an Advanced Encryption Standard Key”, is a Proposed Standard document published in May 2003 by J. Schaad, R. Housley. The canonical text is published by the RFC Editor.
Abstract
This document defines two methods for wrapping an HMAC (Hashed Message Authentication Code) key. The first method defined uses a Triple DES (Data Encryption Standard) key to encrypt the HMAC key. The second method defined uses an AES (Advanced Encryption Standard) key to encrypt the HMAC key. One place that such an algorithm is used is for the Authenticated Data type in CMS (Cryptographic Message Syntax). [PROPOSED STANDARD]
What “Proposed Standard” means
An entry-level standards-track specification: stable, peer-reviewed and a solid basis for implementation, though it may still evolve before becoming an Internet Standard.
The canonical text of RFC 3537 is hosted at rfc-editor.org. Available in TXT,HTML.
- RFC 3536 Terminology Used in Internationalization in the IETF
- RFC 3538 Secure Electronic Transaction Supplement for the v1.0 Internet Open Trading Protocol
- RFC 3535 Overview of the 2002 IAB Network Management Workshop
- RFC 3539 Authentication, Authorization and Accounting Transport Profile
- RFC 3534 The application/ogg Media Type
- RFC 3540 Robust Explicit Congestion Notification Signaling with Nonces
- RFC 3533 The Ogg Encapsulation Format Version 0
- RFC 3541 A Uniform Resource Name Namespace for the Web3D Consortium