RFC 5344: Presence and Instant Messaging Peering Use Cases
In plain English — editorial summary, not part of the RFC
This document describes several use cases of peering of non-VoIP (Voice over IP) services between two or more Service Providers. These Service Providers create a peering relationship between themselves, thus enabling their users to collaborate with users on the other Service Provider network. The target of this document is to drive requirements for peering between domains that provide the non-VoIP based collaboration services with presence and, in particular, Instant Messaging (IM). This memo provides information for the Internet community.
Document record
- Document ID
- RFC5344
- Published
- October 2008
- Authors
- A. Houri; E. Aoki; S. Parameswar
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- rai
- Pages
- 9
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 5438Instant Message Disposition Notification (IMDN)Current
February 2009
- RFC 3428Session Initiation Protocol (SIP) Extension for Instant MessagingUpdated
December 2002
- RFC 6121Extensible Messaging and Presence Protocol (XMPP): Instant Messaging and PresenceCurrent
March 2011
- RFC 3923End-to-End Signing and Object Encryption for the Extensible Messaging and Presence Protocol (XMPP)Current
October 2004
- RFC 3922Mapping the Extensible Messaging and Presence Protocol (XMPP) to Common Presence and Instant Messaging (CPIM)Current
October 2004
- RFC 3921Extensible Messaging and Presence Protocol (XMPP): Instant Messaging and PresenceObsoleted
October 2004
- RFC 3920Extensible Messaging and Presence Protocol (XMPP): CoreObsoleted
October 2004
- RFC 7248Interworking between the Session Initiation Protocol (SIP) and the Extensible Messaging and Presence Protocol (XMPP): PresenceObsoleted
May 2014
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?