File formats:

Status:

PROPOSED STANDARD

Updates:

RFC 3263

Authors:

O. Johansson
G. Salgueiro
V. Gurbani
D. Worley, Ed.

Stream:

IETF

Source:

sipcore (art)

Cite this RFC: TXT  |  XML  |   BibTeX

DOI:  https://doi.org/10.17487/RFC7984

Discuss this RFC: Send questions or comments to the mailing list sipcore@ietf.org

Other actions: Submit Errata  |  Find IPR Disclosures from the IETF  |  View History of RFC 7984

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 updates the DNS procedures described in RFC 3263 for dual-stack SIP implementations in preparation for forthcoming specifications for applying "Happy Eyeballs" principles to SIP.

For the definition of Status, see RFC 2026.

For the definition of Stream, see RFC 8729.