RFC 3263

Session Initiation Protocol (SIP): Locating SIP Servers, June 2002

File formats:
icon for text file icon for PDF icon for HTML
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

DOI:  10.17487/RFC3263

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

Other actions: Submit Errata  |  Find IPR Disclosures from the IETF


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 of Status, see RFC 2026.

For the definition of Stream, see RFC 4844.


Download PDF Reader