Applying Loose Routing to Session Initiation Protocol (SIP) User Agents (UA)
draft-rosenberg-sip-ua-loose-route-02

Document Type Expired Internet-Draft (individual)
Last updated 2008-01-25
Stream (None)
Intended RFC status (None)
Formats
Expired & archived
plain text pdf html
Stream Stream state (No stream defined)
Document shepherd No shepherd assigned
IESG IESG state Expired
Telechat date
Responsible AD (None)
Send notices to (None)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft can be found at
https://www.ietf.org/archive/id/draft-rosenberg-sip-ua-loose-route-02.txt

Abstract

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.

Authors

Jonathan Rosenberg (jdrosen@cisco.com)

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