Skip to main content

Locating Session Initiation Protocol (SIP) Servers in a Dual-Stack IP Network
draft-ietf-sipcore-dns-dual-stack-02

The information below is for an old version of the document.
Document Type Expired Internet-Draft (sipcore WG)
Authors Olle E. Johansson , Gonzalo Salgueiro , Vijay K. Gurbani
Last updated 2015-08-06 (Latest revision 2015-02-02)
Replaces draft-johansson-sip-dual-stack
Stream Internet Engineering Task Force (IETF)
Formats
Expired & archived
plain text xml htmlized pdfized bibtex
Reviews
Stream WG state WG Document
Document shepherd (None)
IESG IESG state Expired
Consensus boilerplate Unknown
Telechat date (None)
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-ietf-sipcore-dns-dual-stack-02.txt

Abstract

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.

Authors

Olle E. Johansson
Gonzalo Salgueiro
Vijay K. Gurbani

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