metasystema.org
UpdatedPROPOSED STANDARDIETF stream

RFC 3263: Session Initiation Protocol (SIP): Locating SIP Servers

Still current, but amended. Parts of this document are changed or extended by RFC 7984, RFC 8553. Read both.

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

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]

Document record

Document ID
RFC3263
Published
July 2002
Authors
J. Rosenberg; H. Schulzrinne
Status
PROPOSED STANDARD
Stream
IETF
Area
rai
Pages
17
Also known as
—
Obsoletes:
RFC 2543
Updated by:
RFC 7984, RFC 8553

Topics

Standards lineage

This document is one revision in a chain of 7 RFCs, each formally replacing the one before it.

  1. RFC 2543 (1999)
  2. RFC 3261 (2002)
  3. RFC 3262 (2002)
  4. RFC 3263 (2002)
  5. RFC 3264 (2002)
  6. RFC 3265 (2002)
  7. RFC 6665 (2012) ✓

Read the full history of SIP-Specific Event Notification →

Referenced by

2 later RFCs formally update or obsolete part of this document.

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/3263-session-initiation-protocol-sip-locating-sip-servers