RFC 5763 - Framework for Establishing a Secure Real-time Transport Protocol (SRTP) Security Context Using Datagram Transport Layer Security (DTLS)

Status of This Memo: Standards Track

Published: May 2010

Authors: J. Fischl (Skype, Inc.), H. Tschofenig (Nokia Siemens Networks), E. Rescorla (RTFM, Inc.)

Abstract

This document specifies how to use the Session Initiation Protocol (SIP) to establish a Secure Real-time Transport Protocol (SRTP) security context using the Datagram Transport Layer Security (DTLS) protocol. It describes a mechanism of transporting a fingerprint attribute in the Session Description Protocol (SDP) that identifies the key that will be presented during the DTLS handshake. The key exchange travels along the media path as opposed to the signaling path. The SIP Identity mechanism can be used to protect the integrity of the fingerprint attribute from modification by intermediate proxies.

Contents

• 1. Introduction
• 2. Overview
• 3. Motivation
• 4. Terminology
• 5. Establishing a Secure Channel
• 6. Miscellaneous Considerations
• 7.1. Basic Message Flow with Early Media and SIP Identity
• 7.2. Basic Message Flow with Connected Identity (RFC 4916)
• 7.3. Basic Message Flow with STUN Check for NAT Case
• 8. Security Considerations
• 9. Acknowledgments
• 10.1. Normative References
• 10.2. Informative References
• Appendix A. Requirements Analysis
• Authors' Addresses

Copyright Notice

Copyright (c) 2010 IETF Trust and the persons identified as the document authors. All rights reserved.

This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (http://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Simplified BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Simplified BSD License.

This document may contain material from IETF Documents or IETF Contributions published or made publicly available before November 10, 2008. The person(s) controlling the copyright in some of this material may not have granted the IETF Trust the right to allow modifications of such material outside the IETF Standards Process. Without obtaining an adequate license from the person(s) controlling the copyright in such materials, this document may not be modified outside the IETF Standards Process, and derivative works of it may not be created outside the IETF Standards Process, except to format it for publication as an RFC or to translate it into languages other than English.