Locating Session Initiation Protocol (SIP) Servers in a Dual-Stack IP Network

The information below is for an old version of the document
Document Type Expired Internet-Draft (sipcore WG)
Authors Olle Johansson  , Gonzalo Salgueiro  , Vijay Gurbani 
Last updated 2015-08-06 (latest revision 2015-02-02)
Replaces draft-johansson-sip-dual-stack
Stream Internet Engineering Task Force (IETF)
Expired & archived
pdf htmlized bibtex
Additional Resources
- Mailing list discussion
Stream WG state WG Document
Document shepherd No shepherd assigned
IESG IESG state Expired
Consensus Boilerplate Unknown
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


RFC 3263 defines how a Session Initiation Protocol (SIP) implementation, given a SIP Uniform Resource Identifier (URI), should locate the next hop SIP server using Domain Name System (DNS) procedures. As SIP networks increasingly transition from IPv4-only to dual-stack, a quality user experience must be ensured for dual- stack SIP implementations. This document supplements the DNS procedures described in RFC 3263 for dual-stack SIP implementations and ensures that they properly align to the optimizations detailed by Happy Eyeballs.


Olle Johansson (oej@edvina.net)
Gonzalo Salgueiro (gsalguei@cisco.com)
Vijay Gurbani (vkg@bell-labs.com)

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