Session Initiation Protocol : Locating SIP Servers
RFC 3263, “Session Initiation Protocol : Locating SIP Servers”, is a Proposed Standard document published in July 2002 by J. Rosenberg, H. Schulzrinne. It obsoletes RFC 2543. It has since been updated by RFC 7984, RFC 8553. The canonical text is published by the RFC Editor.
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]
What “Proposed Standard” means
An entry-level standards-track specification: stable, peer-reviewed and a solid basis for implementation, though it may still evolve before becoming an Internet Standard.
The canonical text of RFC 3263 is hosted at rfc-editor.org. Available in TXT,HTML.
- RFC 3262 Reliability of Provisional Responses in Session Initiation Protocol
- RFC 3264 An Offer/Answer Model with Session Description Protocol
- RFC 3261 SIP: Session Initiation Protocol
- RFC 3265 Session Initiation Protocol -Specific Event Notification
- RFC 3260 New Terminology and Clarifications for Diffserv
- RFC 3266 Support for IPv6 in Session Description Protocol
- RFC 3259 A Message Bus for Local Coordination
- RFC 3267 Real-Time Transport Protocol Payload Format and File Storage Format for the Adaptive Multi-Rate and Adaptive Multi-Rate Wideband Audio Codecs