metasystema.org
CurrentPROPOSED STANDARDIETF stream

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

In plain English — editorial summary, not part of the RFC

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.

Document record

Document ID
RFC7984
Published
September 2016
Authors
O. Johansson; G. Salgueiro; V. Gurbani; D. Worley
Status
PROPOSED STANDARD
Stream
IETF
Area
art
Pages
10
Also known as
—
Updates:
RFC 3263

Topics

Related documents

Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.

Also filed under

About this page

The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.

Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.

Data sources · Editorial policy · Report a correction · What is an RFC?

canonical URL: /rfc/7984-locating-session-initiation-protocol-sip-servers-in-a-dual-stack-ip-network