RFC - 3263
Session Initiation Protocol (SIP): Locating SIP Servers
| Original: | ftp://ftp.isi.edu/in-notes/rfc3263.txt |
|---|---|
| Authors: | J. Rosenberg [dynamicsoft], H. Schulzrinne [Columbia U.] |
| Date: | June 2002 |
| Category: | Proposed Standard |
| Obsoletes: | |
|---|---|
| RFC-2543 | SIP: Session Initiation Protocol (Obsoleted by RFC-3261prop, RFC-3263prop, RFC-3262prop, RFC-3265prop, RFC-3264prop) |
| Referred by: | 21 RFC |
| Refers to: | 8 RFC |
Status
This document specifies an Internet standards track protocol for the Internet community, and requests discussion and suggestions for improvements. Please refer to the current edition of the "Internet Official Protocol Standards" (STD 1) for the standardization state and status of this protocol. Distribution of this memo is unlimited.
Copyright Notice
Copyright (C) The Internet Society (2002). All Rights Reserved.
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.
-
prepared by Miloslav Nic
- the founder of Zvon.org and Law-Ref.org
- the head of B.Sc. program Informatics and chemistry [in Czech]
- the founder of Lidem.org - Volby 2006 - parliamentary elections in the Czech Republic [in Czech]
- the chief consultant of the publishing house ICT Press
- and Pavel Srb, a student of B.Sc. program Informatics and chemistry