RFC 3853: S/MIME Advanced Encryption Standard (AES) Requirement for the Session Initiation Protocol (SIP)
In plain English — editorial summary, not part of the RFC
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. [STANDARDS-TRACK]
Document record
- Document ID
- RFC3853
- Published
- July 2004
- Authors
- J. Peterson
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- rai
- Pages
- 6
- Also known as
- —
- Updates:
- RFC 3261
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 5393Addressing an Amplification Vulnerability in Session Initiation Protocol (SIP) Forking ProxiesCurrent
December 2008
- RFC 2543SIP: Session Initiation ProtocolObsoleted
March 1999
- RFC 3265Session Initiation Protocol (SIP)-Specific Event NotificationObsoleted
July 2002
- RFC 3263Session Initiation Protocol (SIP): Locating SIP ServersUpdated
July 2002
- RFC 3262Reliability of Provisional Responses in Session Initiation Protocol (SIP)Current
July 2002
- RFC 4916Connected Identity in the Session Initiation Protocol (SIP)Current
June 2007
- RFC 3264An Offer/Answer Model with Session Description Protocol (SDP)Updated
July 2002
- RFC 3842A Message Summary and Message Waiting Indication Event Package for the Session Initiation Protocol (SIP)Current
August 2004
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?