Identification of Communications Services in the Session Initiation Protocol (SIP)

Document Type Expired Internet-Draft (individual)
Author Jonathan Rosenberg 
Last updated 2007-07-08
Stream (None)
Intended RFC status (None)
Expired & archived
plain text html xml htmlized pdfized bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
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


This document considers the problem of service identification in the Session Initiation Protocol (SIP). Service identification is the process of determining the user-level use case that is driving the signaling being utilized by the user agent. While seemingly simple, this process is quite complex, and when not addressed properly, can lead to fraud, interoperability problems, and stifling of innovation. This document discusses these problems and makes recommendations on how to address them.


Jonathan Rosenberg (

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