Skip to main content

Applying Loose Routing to Session Initiation Protocol (SIP) User Agents (UA)

Document Type Expired Internet-Draft (individual)
Expired & archived
Author Jonathan Rosenberg
Last updated 2008-01-25
RFC stream (None)
Intended RFC status (None)
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:


A key part of the behavior of the Session Initiation Protocol (SIP) is that SIP proxies rewrite the Request-URI as a request moves throughout the network. Over the years, experience has shown this to be problematic. It makes it difficult to use Request URI for service invocation, complicates emergency services, makes it more complex to support aliases, and so on. Architecturally, it confounds the concepts of address and route. This document proposes to change this through a new mechanism called UA loose routing.


Jonathan Rosenberg

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