RFC 6193: Media Description for the Internet Key Exchange Protocol (IKE) in the Session Description Protocol (SDP)
In plain English — editorial summary, not part of the RFC
This document specifies how to establish a media session that represents a virtual private network using the Session Initiation Protocol for the purpose of on-demand media/application sharing between peers. It extends the protocol identifier of the Session Description Protocol (SDP) so that it can negotiate use of the Internet Key Exchange Protocol (IKE) for media sessions in the SDP offer/answer model. It also specifies a method to boot up IKE and generate IPsec security associations using a self-signed certificate. This document is not an Internet Standards Track specification; it is published for informational purposes.
Document record
- Document ID
- RFC6193
- Published
- April 2011
- Authors
- M. Saito; D. Wing; M. Toyama
- Status
- INFORMATIONAL
- Stream
- INDEPENDENT
- Area
- —
- Pages
- 22
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 4555IKEv2 Mobility and Multihoming Protocol (MOBIKE)Current
June 2006
- RFC 4301Security Architecture for the Internet ProtocolUpdated
December 2005
- RFC 8994An Autonomic Control Plane (ACP)Current
May 2021
- RFC 2401Security Architecture for the Internet ProtocolObsoleted
November 1998
- RFC 5379Guidelines for Using the Privacy Mechanism for SIPCurrent
February 2010
- RFC 5022Media Server Control Markup Language (MSCML) and ProtocolCurrent
September 2007
- RFC 4722Media Server Control Markup Language (MSCML) and ProtocolObsoleted
November 2006
- RFC 7836Guidelines on the Cryptographic Algorithms to Accompany the Usage of Standards GOST R 34.10-2012 and GOST R 34.11-2012Current
March 2016
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?