idnits 2.17.1 draft-ietf-smime-aes-keywrap-00.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 3394 5 Title: Advanced Encryption Standard (AES) Key Wrap 6 Algorithm 7 Author(s): J. Schaad, R. Housley 8 Status: Informational 9 Date: September 2002 10 Mailbox: jimsch@exmsft.com, rhousley@rsasecurity.com 11 Pages: 40 12 Characters: 73072 13 Updates/Obsoletes/SeeAlso: None 15 I-D Tag: draft-ietf-smime-aes-keywrap-00.txt 17 URL: ftp://ftp.rfc-editor.org/in-notes/rfc3394.txt 19 The purpose of this document is to make the Advanced Encryption 20 Standard (AES) Key Wrap algorithm conveniently available to the 21 Internet community. The United States of America has adopted AES 22 as the new encryption standard. The AES Key Wrap algorithm will 23 probably be adopted by the USA for encryption of AES keys. 24 The authors took most of the text in this document from the draft 25 AES Key Wrap posted by NIST. 27 This document is a product of the S/MIME Mail Security Working Group 28 of the IETF. 30 This memo provides information for the Internet community. It does 31 not specify an Internet standard of any kind. Distribution of this 32 memo is unlimited. 34 This announcement is sent to the IETF list and the RFC-DIST list. 35 Requests to be added to or deleted from the IETF distribution list 36 should be sent to IETF-REQUEST@IETF.ORG. Requests to be 37 added to or deleted from the RFC-DIST distribution list should 38 be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG. 40 Details on obtaining RFCs via FTP or EMAIL may be obtained by sending 41 an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body 42 help: ways_to_get_rfcs. For example: 44 To: rfc-info@RFC-EDITOR.ORG 45 Subject: getting rfcs 47 help: ways_to_get_rfcs 49 Requests for special distribution should be addressed to either the 50 author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG. Unless 51 specifically noted otherwise on the RFC itself, all RFCs are for 52 unlimited distribution.echo 53 Submissions for Requests for Comments should be sent to 54 RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC 55 Authors, for further information.