----Next_Part(Thu_Feb_17_06_25_20_2005_823)--
Content-Type: Text/Plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Hmm, does this mean we should add the SEED algorithm (it's defined in
RFC 4009)?

Cheers,
Richard

-----
Please consider sponsoring my work on free software.
See http://www.free.lp.se/sponsoring.html for details.

--
Richard Levitte richard@levitte.org
http://richard.levitte.org/

"When I became a man I put away childish things, including
the fear of childishness and the desire to be very grown up."
-- C.S. Lewis

----Next_Part(Thu_Feb_17_06_25_20_2005_823)--
Content-Type: Message/Rfc822
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

Return-Path:
Received: from boreas.isi.edu (128.9.160.161) by nic.lp.se (MX V5.3 VnHj) with
ESMTP for ; Wed, 16 Feb 2005 04:06:29 +0100
Received: from boreas.isi.edu (localhost [127.0.0.1]) by boreas.isi.edu
(8.11.6p2+0917/8.11.2) with ESMTP id j1G2N1E16297;
Tue, 15 Feb 2005 18:23:01 -0800 (PST)
Received: from ISI.EDU (adma.isi.edu [128.9.160.239]) by boreas.isi.edu
(8.11.6p2+0917/8.11.2) with ESMTP id j1G2MAE16159;
Tue, 15 Feb 2005 18:22:10 -0800 (PST)
Message-ID: <200502160222.j1G2MAE16159@boreas.isi.edu>
To: rfc-dist@rfc-editor.org
From: rfc-editor@rfc-editor.org
MIME-Version: 1.0
Content-Type: Multipart/Mixed; Boundary=NextPart
Date: Tue, 15 Feb 2005 18:22:10 -0800
X-ISI-4-30-3-MailScanner: Found to be clean, Found to be clean
CC: rfc-editor@rfc-editor.org
Subject: [rfc-dist] RFC 4010 on Use of the SEED Encryption Algorithm in
Cryptographic Message Syntax (CMS)
X-BeenThere: rfc-dist@mailman.rfc-editor.org
X-Mailman-Version: 2.1.6b3
Precedence: list
List-Id: RFC Announcements
List-Unsubscribe: ,

List-Archive:
List-Post:
List-Help:
List-Subscribe: ,

Sender: rfc-dist-bounces@mailman.rfc-editor.org
Errors-To: rfc-dist-bounces@mailman.rfc-editor.org
X-MailScanner-From: rfc-dist-bounces@mailman.rfc-editor.org
X-Spam-Checker-Version: SpamAssassin 3.0.2 (2004-11-16) on lapdog
X-Spam-Level:
X-Spam-Status: No, score=-17.4 required=5.0 tests=AWL,BAYES_00,
MIME_BOUND_NEXTPART,NO_REAL_NAME,USER_IN_DEF_WHITE LIST autolearn=no
version=3.0.2


--NextPart


A new Request for Comments is now available in online RFC libraries.


RFC 4010

Title: Use of the SEED Encryption Algorithm
in Cryptographic Message Syntax (CMS)
Author(s): J. Park, S. Lee, J. Kim, J. Lee
Status: Standards Track
Date: February 2005
Mailbox: khopri@kisa.or.kr, sjlee@kisa.or.kr,
jykim@kisa.or.kr, jilee@kisa.or.kr
Pages: 13
Characters: 22403
Updates/Obsoletes/SeeAlso: None

I-D Tag: draft-ietf-smime-cms-seed-02.txt

URL: ftp://ftp.rfc-editor.org/in-notes/rfc4010.txt


This document specifies the conventions for using the SEED
encryption algorithm for encryption with the Cryptographic
Message Syntax (CMS).

SEED is added to the set of optional symmetric encryption algorithms
in CMS by providing two classes of unique object identifiers (OIDs).
One OID class defines the content encryption algorithms and the other
defines the key encryption algorithms.

This documenet is a product of the S/MIME Mail Security Working Group
of the IETF.

This is now a Proposed Standard Protocol.

This document specifies an Internet standards track protocol for
the Internet community, and requests discussion and suggestions
for improvements. Please refer to the current edition of the
"Internet Official Protocol Standards" (STD 1) for the
standardization state and status of this protocol. 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:

To: rfc-info@RFC-EDITOR.ORG
Subject: getting rfcs

help: ways_to_get_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
unlimited distribution.

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.

--NextPart
Content-Type: Multipart/Alternative; Boundary="OtherAccess"

--OtherAccess
Content-Type: Message/External-body; access-type="mail-server";
server="RFC-INFO@RFC-EDITOR.ORG"

Content-Type: text/plain
Content-ID: <050215182027.RFC@RFC-EDITOR.ORG>

RETRIEVE: rfc
DOC-ID: rfc4010

--OtherAccess
Content-Type: Message/External-body; name="rfc4010.txt"; site="ftp.isi.edu";
access-type="anon-ftp"; directory="in-notes"

Content-Type: text/plain
Content-ID: <050215182027.RFC@RFC-EDITOR.ORG>


--OtherAccess--
--NextPart
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
rfc-dist mailing list
rfc-dist@mailman.rfc-editor.org
http://mailman.rfc-editor.org/mailman/listinfo/rfc-dist
http://www.rfc-editor.org

--NextPart--


----Next_Part(Thu_Feb_17_06_25_20_2005_823)----
__________________________________________________ ____________________
OpenSSL Project http://www.openssl.org
Development Mailing List openssl-dev@openssl.org
Automated List Manager majordomo@openssl.org