Browse Prior Art Database

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

IP.com Disclosure Number: IPCOM000029953D
Original Publication Date: 2004-Jul-01
Included in the Prior Art Database: 2004-Jul-20
Document File: 7 page(s) / 11K

Publishing Venue

Internet Society Requests For Comment (RFCs)

Related People

J. Peterson: AUTHOR

Abstract

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 text was extracted from an ASCII text file.
This is the abbreviated version, containing approximately 26% of the total text.

Network Working Group                                        J. Peterson

Request for Comments: 3853                                       Neustar

Updates: 3261                                                  July 2004

Category: Standards Track

               S/MIME Advanced Encryption Standard (AES)

         Requirement for the Session Initiation Protocol (SIP)

Status of this Memo

   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.

Copyright Notice

   Copyright (C) The Internet Society (2004).

Abstract

   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.

Table of Contents

   1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . 2

   2. Terminology  . . . . . . . . . . . . . . . . . . . . . . . . . . 3

   3. S/MIME Ciphersuite Requirements for SIP  . . . . . . . . . . . . 3

   4. Security Considerations  . . . . . . . . . . . . . . . . . . . . 3

   5. References . . . . . . . . . . . . . . . . . . . . . . . . . . . 4

      5.1.  Normative References . . . . . . . . . . . . . . . . . . . 4

      5.2.  Informative References . . . . . . . . . . . . . . . . . . 4

   6. Acknowledgments  . . . . . . . . . . . . . . . . . . . . . . . . 4

   7. Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 5

   8. Full Copyright Statement . . . . . . . . . . . . . . . . . . . . 6

Peterson                    Standards Track                     [Page 1]

RFC 3853             S/MIME AES Requirement for SIP            July 2004

1.  Introduction

   The Session Initiation Protocol (SIP) specification (RFC 3261 [1])

   currently details optional support (a normative MAY) for the use of

   secure MIME, or S/MIME (RFC 2633 [8]).  Since RFC 3261 was published,

   the S/MIME specification and the underlying Cryptographic Message

   Syntax (CMS, RFC 3369 [3]) have undergone some revision.  Ongoing

   work has identified AES as a algorithm that might be used for content

   encryption in S/MIME.

   The Advanced Encryption Standard (AES [6]) is widely believed to be

   faster than Triple-DES (3DES, which has previously been mandated for

   usage with S/MIME) and to be comparably secure.  AES is also believed

   to have comparatively low memory re...