World Library  
Flag as Inappropriate
Email this Article

SIMPLE (instant messaging protocol)

Article Id: WHEBN0000226636
Reproduction Date:

Title: SIMPLE (instant messaging protocol)  
Author: World Heritage Encyclopedia
Language: English
Subject: Instant messaging, Instant Messaging and Presence Protocol, Presence and Instant Messaging, Message Session Relay Protocol, Empathy (software)
Collection: Application Layer Protocols, Instant Messaging Protocols, Working Groups
Publisher: World Heritage Encyclopedia
Publication
Date:
 

SIMPLE (instant messaging protocol)

SIMPLE, the session initiation protocol for instant messaging and presence leveraging extensions, is an instant messaging (IM) and presence protocol suite based on Session Initiation Protocol (SIP) managed by the Internet Engineering Task Force.[1] Contrary to the vast majority of IM and presence protocols used by software deployed today, SIMPLE is an open standard like XMPP.

Contents

  • Purpose 1
  • Technical description 2
    • Presence 2.1
    • IM 2.2
  • See also 3
  • References 4
  • External links 5

Purpose

SIMPLE applies SIP to the problems of:

  • registering for presence information and receiving notifications when such events occur, for example when a user logs in or comes back from lunch;
  • sending short messages, analogous to SMS or two-way paging;
  • managing a session of real-time messages between two or more participants.

Implementations of the SIMPLE based protocols can be found in SIP Softphones and also in SIP Hardphones.

Technical description

Presence

The SIMPLE presence specifications can be broken up into:

  • The core protocol machinery. This provides the actual SIP extensions for subscriptions, notifications and publications. RFC 6665 defines the SUBSCRIBE and NOTIFY methods. SUBSCRIBE allows to subscribe to an event on a server, the server responds with NOTIFY whenever the event come up. RFC 3856 defines how to make use of SUBSCRIBE/NOTIFY for presence. Two models are defined: an end-to-end model in which each User Agent handles presence subscriptions itself; and a centralized model. The latter introduces the concept of a presence server; all subscriptions are handled by this server. The message PUBLISH (RFC 3903) allows User Agents to inform the presence server about their subscription states.
  • Presence documents. The presence information is coded in XML documents, that are carried in the bodies of the respective SIP messages. RFC 3863 and RFC 4479 describe this procedure, RFC 4480 (RPID), RFC 4481, RFC 4482 (CPID) and various drafts describe contents and formats of the presence documents.
  • Privacy, policy and provisioning. If the centralized model is used, the User Agents need a way to define who may subscribe to which amount of their presence information. RFC 4745 and RFC 5025 define a framework for authorization policies controlling access to application-specific data. The XCAP (RFC 4825), carried by HTTP, allows User Agents to communicate their presence rules to a XCAP server, which rules the information exposed by the presence server. RFC 3857 and RFC 3858 define a subscription event "watcher info". User Agents may subscribe to this event to be informed who is subscribing to their presence information.

IM

SIP defines two modes of instant messaging:

  • The Page Mode makes use of the SIP method MESSAGE, as defined in RFC 3428. This mode establishes no sessions.
  • The Session Mode. The Message Session Relay Protocol (RFC 4975, RFC 4976) is a text-based protocol for exchanging arbitrarily-sized content between users, at any time. An MSRP session is set up by exchanging certain information, such as an MSRP URI, within SIP and SDP signalling.

See also

References

  1. ^ SIMPLE Working Group
  • Rosenberg, J. (April 2013). SIMPLE Made Simple: An Overview of the IETF Specifications for Instant Messaging and Presence Using the Session Initiation Protocol (SIP).  

External links

  • SIP for Instant Messaging and Presence Leveraging Extensions (simple) WG - IETF Datatracker
  • Rich Presence - A New User Communications Experience Technology White Paper
This article was sourced from Creative Commons Attribution-ShareAlike License; additional terms may apply. World Heritage Encyclopedia content is assembled from numerous content providers, Open Access Publishing, and in compliance with The Fair Access to Science and Technology Research Act (FASTR), Wikimedia Foundation, Inc., Public Library of Science, The Encyclopedia of Life, Open Book Publishers (OBP), PubMed, U.S. National Library of Medicine, National Center for Biotechnology Information, U.S. National Library of Medicine, National Institutes of Health (NIH), U.S. Department of Health & Human Services, and USA.gov, which sources content from all federal, state, local, tribal, and territorial government publication portals (.gov, .mil, .edu). Funding for USA.gov and content contributors is made possible from the U.S. Congress, E-Government Act of 2002.
 
Crowd sourced content that is contributed to World Heritage Encyclopedia is peer reviewed and edited by our editorial staff to ensure quality scholarly research articles.
 
By using this site, you agree to the Terms of Use and Privacy Policy. World Heritage Encyclopedia™ is a registered trademark of the World Public Library Association, a non-profit organization.
 


Copyright © World Library Foundation. All rights reserved. eBooks from Project Gutenberg are sponsored by the World Library Foundation,
a 501c(4) Member's Support Non-Profit Organization, and is NOT affiliated with any governmental agency or department.