RFC 5897: Identification of Communications Services in the Session Initiation Protocol (SIP)
In plain English — editorial summary, not part of the RFC
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 (UA). This document discusses the uses of service identification, and outlines several architectural principles behind the process. It identifies perils when service identification is not done properly -- including fraud, interoperability failures, and stifling of innovation. It then outlines a set of recommended practices for service identification. This document is not an Internet Standards Track specification; it is published for informational purposes.
Document record
- Document ID
- RFC5897
- Published
- June 2010
- Authors
- J. Rosenberg
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- rai
- Pages
- 23
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 5876Updates to Asserted Identity in the Session Initiation Protocol (SIP)Current
April 2010
- RFC 5875An Extensible Markup Language (XML) Configuration Access Protocol (XCAP) Diff Event PackageCurrent
May 2010
- RFC 5874An Extensible Markup Language (XML) Document Format for Indicating a Change in XML Configuration Access Protocol (XCAP) ResourcesCurrent
May 2010
- RFC 5922Domain Certificates in the Session Initiation Protocol (SIP)Current
June 2010
- RFC 5923Connection Reuse in the Session Initiation Protocol (SIP)Current
June 2010
- RFC 5870A Uniform Resource Identifier for Geographic Locations ('geo' URI)Current
June 2010
- RFC 5924Extended Key Usage (EKU) for Session Initiation Protocol (SIP) X.509 CertificatesCurrent
June 2010
- RFC 5853Requirements from Session Initiation Protocol (SIP) Session Border Control (SBC) DeploymentsCurrent
April 2010
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?