Skip to main content

Use of the Camellia Encryption Algorithm in Cryptographic Message Syntax (CMS)
RFC 3657

Approval announcement
Draft of message to be sent after approval:


From: The IESG <>
To: IETF-Announce <>
Cc: Internet Architecture Board <>,
    RFC Editor <>, 
    smime mailing list <>, 
    smime chair <>
Subject: Protocol Action: 'Use of the Camellia Encryption 
         Algorithm in CMS' to Proposed Standard 

The IESG has approved the following document:

- 'Use of the Camellia Encryption Algorithm in CMS '
   <draft-ietf-smime-camellia-06.txt> as a Proposed Standard

This document is the product of the S/MIME Mail Security Working Group. 

The IESG contact persons are Russ Housley and Tim Polk.

A URL of this Internet-Draft is:

Ballot Text

Technical Summary

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

Working Group Summary

    The Working Group came to consensus on this document.

Protocol Quality

    This document was reviewed by Russell Housley for the IESG.

RFC Editor Note

  Please replace the IPR Considerations Section with the following:

     The IETF takes no position regarding the
     validity or scope of any intellectual property
     or other rights that might be claimed to
     pertain to the implementation or use of the
     technology described in this document or the
     extent to which any license under such rights
     might or might not be available; neither does
     it represent that it has made any effort to
     identify any such rights.  Information on the
     IETF's procedures with respect to rights in
     standards-track and standards-related 
     documentation can be found in BCP-11.  Copies
     of claims of rights made available for
     publication and any assurances of licenses to
     be made available, or the result of an attempt
     made to obtain a general license or permission
     for the use of such proprietary rights by
     implementors or users of this specification can
     be obtained from the IETF Secretariat.

     The IETF invites any interested party to bring
     to its attention any copyrights, patents or patent
     applications, or other proprietary rights which
     may cover technology that may be required to
     practice this standard.  Please address the
     information to the IETF Executive Director.

     The IETF has been notified of intellectual
     property rights claimed in regard to some or all
     of the specification contained in this document.
     For more information consult the online list
     of claimed rights.

RFC Editor Note