TLS sessions in SIP using DNS-based Authentication of Named Entities (DANE) TLSA records
draft-johansson-sipcore-dane-sip-00

Document Type Expired Internet-Draft (individual)
Last updated 2015-04-09 (latest revision 2014-10-06)
Replaces draft-johansson-dispatch-dane-sip
Stream (None)
Intended RFC status (None)
Formats
Expired & archived
plain text pdf html bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state Expired
Telechat date
Responsible AD (None)
Send notices to (None)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft can be found at
https://www.ietf.org/archive/id/draft-johansson-sipcore-dane-sip-00.txt

Abstract

Use of TLS in the SIP protocol is defined in multiple documents, starting with RFC 3261. The actual verification that happens when setting up a SIP TLS connection to a SIP server based on a SIP URI is described in detail in RFC 5922 - SIP Domain Certificates. In this document, an alternative method is defined, using DNS-Based Authentication of Named Entities (DANE). By looking up TLSA DNS records and using DNSsec protection of the required queries, including lookups for NAPTR and SRV records, a SIP Client can verify the identity of the TLS SIP server in a different way, matching on the SRV host name in the X.509 PKIX certificate instead of the SIP domain. This provides more scalability in hosting solutions and make it easier to use standard CA certificates (if needed at all).

Authors

Olle Johansson (oej@edvina.net)

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)