Search RFCs

RFC Editor

File formats:

Status:

PROPOSED STANDARD

Obsoletes:

RFC 2543

Updated by:

RFC 7984,RFC 8553

Authors:

J. Rosenberg
H. Schulzrinne

Stream:

IETF

Source:

sip (rai)

Cite this RFC:TXT  | XML  |  BibTeX

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

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

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

Abstract

The Session Initiation Protocol (SIP) uses DNS procedures to allow a client to resolve a SIP Uniform Resource Identifier (URI) into the IP address, port, and transport protocol of the next hop to contact. It also uses DNS to allow a server to send a response to a backup client if the primary client has failed. This document describes those DNS procedures in detail. [STANDARDS-TRACK]

For the definition ofStatus,seeRFC 2026.

For the definition ofStream, seeRFC 8729.