RFC 3853 on S/MIME Advanced Encryption Standard (AES) Requirement for the Session Initiation Protocol (SIP)

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

        RFC 3853

        Title:      S/MIME Advanced Encryption Standard (AES)
                    Requirement for the Session Initiation Protocol
                    (SIP)
        Author(s):  J. Peterson
        Status:     Standards Track
        Date:       July 2004
        Mailbox:    jon.peterson@neustar.biz
        Pages:      6
        Characters: 10687
        Updates:    3261

        I-D Tag:    draft-ietf-sip-smime-aes-01.txt

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

RFC 3261 currently specifies 3DES as the mandatory-to-implement
ciphersuite for implementations of S/MIME in the Session Initiation
Protocol (SIP).  This document updates the normative guidance of RFC
3261 to require the Advanced Encryption Standard (AES) for S/MIME.

This document is a product of the Session Initiation Protocol 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.echo 
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.