idnits 2.17.1 draft-ietf-smime-hmac-key-wrap-02.txt: Skipping this file; it looks like a tombstone file to me. -------------------------------------------------------------------------------- 1 A new Request for Comments is now available in online RFC libraries. 3 RFC 3537 5 Title: Wrapping a Hashed Message Authentication Code 6 (HMAC) key with a Triple-Data Encryption Standard 7 (DES) Key or an Advanced Encryption Standard (AES) 8 Key 9 Author(s): J. Schaad, R. Housley 10 Status: Standards Track 11 Date: May 2003 12 Mailbox: jimsch@exmsft.com, housley@vigilsec.com 13 Pages: 9 14 Characters: 16885 15 Updates/Obsoletes/SeeAlso: None 17 I-D Tag: draft-ietf-smime-hmac-key-wrap-02.txt 19 URL: ftp://ftp.rfc-editor.org/in-notes/rfc3537.txt 21 This document defines two methods for wrapping an HMAC (Hashed Message 22 Authentication Code) key. The first method defined uses a Triple DES 23 (Data Encryption Standard) key to encrypt the HMAC key. The second 24 method defined uses an AES (Advanced Encryption Standard) key to 25 encrypt the HMAC key. One place that such an algorithm is used is for 26 the Authenticated Data type in CMS (Cryptographic Message Syntax). 28 This document is a product of the S/MIME Mail Security Working Group of 29 the IETF. 31 This is now a Proposed Standard Protocol. 33 This document specifies an Internet standards track protocol for 34 the Internet community, and requests discussion and suggestions 35 for improvements. Please refer to the current edition of the 36 "Internet Official Protocol Standards" (STD 1) for the 37 standardization state and status of this protocol. Distribution 38 of this memo is unlimited. 40 This announcement is sent to the IETF list and the RFC-DIST list. 41 Requests to be added to or deleted from the IETF distribution list 42 should be sent to IETF-REQUEST@IETF.ORG. Requests to be 43 added to or deleted from the RFC-DIST distribution list should 44 be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG. 46 Details on obtaining RFCs via FTP or EMAIL may be obtained by sending 47 an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body 48 help: ways_to_get_rfcs. For example: 50 To: rfc-info@RFC-EDITOR.ORG 51 Subject: getting rfcs 53 help: ways_to_get_rfcs 55 Requests for special distribution should be addressed to either the 56 author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG. Unless 57 specifically noted otherwise on the RFC itself, all RFCs are for 58 unlimited distribution.echo 59 Submissions for Requests for Comments should be sent to 60 RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC 61 Authors, for further information.