Browse Prior Art Database

Session Initiation Protocol (SIP): Locating SIP Servers (RFC3263)

IP.com Disclosure Number: IPCOM000009208D
Original Publication Date: 2002-Jun-01
Included in the Prior Art Database: 2002-Aug-13
Document File: 18 page(s) / 42K

Publishing Venue

Internet Society Requests For Comment (RFCs)

Related People

J. Rosenberg: AUTHOR [+2]

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.

This text was extracted from an ASCII text file.
This is the abbreviated version, containing approximately 7% of the total text.

Network Working Group� � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � J. Rosenberg

Request for Comments: 3263� � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � dynamicsoft

Obsoletes: 2543� � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � H. Schulzrinne

Category: Standards Track� � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � Columbia U.

� � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � June 2002

� � � � � � � Session Initiation Protocol (SIP): Locating SIP Servers

Status of this Memo

� � 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.

Table of Contents

� � 1� � � � � � � � � Introduction ........................................� � � 2

� � 2� � � � � � � � � Problems DNS is Needed to Solve .....................� � � 2

� � 3� � � � � � � � � Terminology .........................................� � � 5

� � 4� � � � � � � � � Client Usage ........................................� � � 5

� � 4.1� � � � � � � Selecting a Transport Protocol ......................� � � 6

� � 4.2� � � � � � � Determining Port and IP Address .....................� � � 8

� � 4.3� � � � � � � Details of RFC 2782 Process .........................� � � 9

� � 4.4� � � � � � � Consideration for Stateless Proxies .................� � 10

� � 5� � � � � � � � � Server Usage ........................................� � 11

� � 6� � � � � � � � � Constructing SIP URIs ...............................� � 12

� � 7� � � � � � � � � Security Considerations .............................� � 12

� � 8� � � � � � � � � The Transport Determination Application .............� � 13

� � 9� � � � � � � � � IANA Considerations .................................� � 14

� � 10� � � � � � � � Acknowledgements ....................................� � 14

� � 11� � � � � � � � Normative References ................................� � 15

� � 12� � � � � � � � Informative References ..............................� � 15

Rosenberg & Schulzrinne� � � � Standards Track� � � � � � � � � � � � � � � � � � � � [Page 1]

RFC 3263� � � � � � � � � � � � � � SIP: Locating S...