Skip to main content

Connected Identity in the Session Initiation Protocol (SIP)

Document Type Replaced Internet-Draft (individual)
Expired & archived
Author John Elwell
Last updated 2008-03-17 (Latest revision 2006-02-22)
Replaced by RFC 4916
RFC stream (None)
Intended RFC status (None)
Stream Stream state (No stream defined)
Consensus boilerplate Unknown
RFC Editor Note (None)
IESG IESG state Replaced by draft-ietf-sip-connected-identity
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:


Because of retargeting of a dialog-forming request, the UAS can have a different identity from that in the To header. This document provides a means for that UA to supply its identity to the peer UA by means of a request in the reverse direction and for that identity to be signed by an authentication service. The same mechanism can be used to indicate a change of identity during a dialog, e.g., because of some action in a PSTN behind a gateway. This work is being discussed on the mailing list.


John Elwell

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