[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
RFC 3217 on Triple-DES and RC2 Key Wrapping
- To: IETF-Announce: ;
- Subject: RFC 3217 on Triple-DES and RC2 Key Wrapping
- From: RFC Editor <rfc-ed@ISI.EDU>
- Date: Fri, 14 Dec 2001 17:27:14 -0800
- Cc: rfc-ed@ISI.EDU, email@example.com
- Delivery-date: Sat, 15 Dec 2001 04:09:00 +0200
- Envelope-to: firstname.lastname@example.org
A new Request for Comments is now available in online RFC libraries.
Title: Triple-DES and RC2 Key Wrapping
Author(s): R. Housley
Date: December 2001
I-D Tag: draft-ietf-smime-key-wrap-01.txt
This document specifies the algorithm for wrapping one Triple-DES
key with another Triple-DES key and the algorithm for wrapping
one RC2 key with another RC2 key. These key wrap algorithms
were originally published in section 12.6 of RFC 2630. They
are republished since these key wrap algorithms have been found to be
useful in contexts beyond those supported by RFC 2630.
This document is a product of the S/MIME Mail Security Working Group
of the IETF.
This memo provides information for the Internet community. It does
not specify an Internet standard of any kind. Distribution of this
memo is unlimited.
This announcement is sent to the IETF list and the RFC-DIST list.
Requests to be added to or deleted from the IETF distribution list
should be sent to IETF-REQUEST@IETF.ORG. Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG.
Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body
help: ways_to_get_rfcs. For example:
Subject: getting rfcs
Requests for special distribution should be addressed to either the
author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG. Unless
specifically noted otherwise on the RFC itself, all RFCs are for
Submissions for Requests for Comments should be sent to
RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC
Authors, for further information.
Joyce K. Reynolds and Sandy Ginoza
USC/Information Sciences Institute
Below is the data which will enable a MIME compliant Mail Reader
implementation to automatically retrieve the ASCII version
of the RFCs.