Identification of Communications Services in the Session Initiation Protocol
RFC 5897, “Identification of Communications Services in the Session Initiation Protocol”, is an Informational document published in June 2010 by J. Rosenberg. The canonical text is published by the RFC Editor.
Abstract
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.
What “Informational” means
Published for the general information of the community. It does not define an IETF standard and carries no standards-track status.
The canonical text of RFC 5897 is hosted at rfc-editor.org. Available in TXT,HTML.
- RFC 5896 Generic Security Service Application Program Interface : Delegate if Approved by Policy
- RFC 5898 Connectivity Preconditions for Session Description Protocol Media Streams
- RFC 5895 Mapping Characters for Internationalized Domain Names in Applications 2008
- RFC 5894 Internationalized Domain Names for Applications : Background, Explanation, and Rationale
- RFC 5893 Right-to-Left Scripts for Internationalized Domain Names for Applications
- RFC 5901 Extensions to the IODEF-Document Class for Reporting Phishing
- RFC 5892 The Unicode Code Points and Internationalized Domain Names for Applications
- RFC 5902 IAB Thoughts on IPv6 Network Address Translation