Skip to main content

URI Leasing in the Session Initiation Protocol (SIP)
draft-rosenberg-sipping-lease-00

Document Type Expired Internet-Draft (individual)
Expired & archived
Author Jonathan Rosenberg
Last updated 2003-02-12
RFC stream (None)
Intended RFC status (None)
Formats
Stream Stream state (No stream defined)
Consensus boilerplate Unknown
RFC Editor Note (None)
IESG IESG state Expired
Telechat date (None)
Responsible AD (None)
Send notices to (None)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:

Abstract

Several applications of the Session Initiation Protocol (SIP) require a user agent (UA) to construct and distribute a URI which can be used by anyone on the Internet to route a call to that specific UA instance. An example of such an application is call transfer, based on the REFER method. To date, a variety of techniques have been proposed for the contruction of such URI. All of them have fatal drawbacks. This document proposes that the problem is actually one of URI leasing - a feature whereby a UA can dynamically request the creation of an address-of-record (AOR) within a domain. Requirements for a URI leasing mechanism are outlined.

Authors

Jonathan Rosenberg

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)