RFC 6216: Example Call Flows Using Session Initiation Protocol (SIP) Security Mechanisms
In plain English — editorial summary, not part of the RFC
This document shows example call flows demonstrating the use of Transport Layer Security (TLS), and Secure/Multipurpose Internet Mail Extensions (S/MIME) in Session Initiation Protocol (SIP). It also provides information that helps implementers build interoperable SIP software. To help facilitate interoperability testing, it includes certificates used in the example call flows and processes to create certificates for testing. This document is not an Internet Standards Track specification; it is published for informational purposes.
Document record
- Document ID
- RFC6216
- Published
- April 2011
- Authors
- C. Jennings; K. Ono; R. Sparks; B. Hibbard
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- art
- Pages
- 67
- Also known as
- —
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 6223Indication of Support for Keep-AliveCurrent
April 2011
- RFC 6228Session Initiation Protocol (SIP) Response Code for Indication of Terminated DialogCurrent
May 2011
- RFC 6197Location-to-Service Translation (LoST) Service List Boundary ExtensionCurrent
April 2011
- RFC 6236Negotiation of Generic Image Attributes in the Session Description Protocol (SDP)Current
May 2011
- RFC 6190RTP Payload Format for Scalable Video CodingCurrent
May 2011
- RFC 6262RTP Payload Format for IP-MR Speech CodecCurrent
August 2011
- RFC 6141Re-INVITE and Target-Refresh Request Handling in the Session Initiation Protocol (SIP)Current
March 2011
- RFC 6295RTP Payload Format for MIDICurrent
June 2011
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?