Instant Messaging
Click on the red underlined text to get to the source
... applications of the core features of XMPP that provide the basic
functionality expected of an instant messaging (IM) and presence
application as defined in RFC 2779 ...
...
For the purposes of this memo, the requirements of a basic instant
messaging and presence application are defined by [IMP-REQS], which
at a high level ...
... IMP-REQS] also stipulates that presence services must be separable
from instant messaging services; i.e., it must be possible to use the
protocol to provide a presence service, an instant messaging service ...
... instant messaging services; i.e., it must be possible to use the
protocol to provide a presence service, an instant messaging service,
or both. Although the text of this memo assumes that implementations
and deployments ...
... or both. Although the text of this memo assumes that implementations
and deployments will want to offer a unified instant messaging and
presence service, there is no requirement ...
... service must offer
both a presence service and an instant messaging service, and the
protocol makes it possible to offer separate and distinct services
...
... protocol makes it possible to offer separate and distinct services
for presence and for instant messaging.
Note: While XMPP ...
... elements, as well as values for the common 'type' attribute, that are
specific to instant messaging and presence applications. Thus,
before addressing particular "use cases" for such applications, we
...
... namespace are used to "push" information to another entity. Common
uses in instant messaging applications include single messages,
messages sent in the context of a chat conversation ...
... specifying an identifier that is used for tracking a conversation
thread (sometimes referred to as an "instant messaging session")
between two entities. The value of the <thread/> element is
...
... subscription model used in the context of XMPP-based instant
messaging and presence applications, refer to Exchanging Presence
Information (Section 5) and Managing Subscriptions (Section 6).
...
... stanza routing within
instant messaging and presence applications, refer to Server Rules
for Handling XML Stanzas (Section 11).
...
...
Most instant messaging and presence applications based on XMPP are
implemented via a client-server architecture ...
... to establish a session on a server in order to engage in the expected
instant messaging and presence activities. However, there are
several pre-conditions that MUST be met before a client can establish
...
... several pre-conditions that MUST be met before a client can establish
an instant messaging and presence session. These are:
...
... client MUST establish a
session if it desires to engage in instant messaging and presence
functionality; it completes this step by sending to the server an IQ
stanza ...
... OPTIONAL.
Note: Before allowing the creation of instant messaging and presence
sessions, a server MAY require prior account provisioning. Possible
...
...
An instant messaging client SHOULD specify an intended recipient for
a message by providing the JID ...
... subscribe". If the subscription request is being
sent to an instant messaging contact, the JID supplied in the 'to'
attribute SHOULD be of the form <contact@example.org> rather than
...
...
In order to protect the privacy of instant messaging users and any
other entities, presence and availability information is disclosed
only to other entities that the user has approved. When a user has
...
... REQUIRED). The value of the 'jid' attribute SHOULD be of the form
<user@domain> if the item is associated with another (human) instant
messaging user.
The state ...
... Some level of integration between roster items and presence
subscriptions is normally expected by an instant messaging user
regarding the user's subscriptions to and from other contacts. This
section describes the level of integration that MUST be supported
...
... section describes the level of integration that MUST be supported
within XMPP instant messaging applications.
There are four primary subscription states:
...
...
Most instant messaging systems have found it necessary to implement
some method for users to block communications from particular other
...
... XMPP-CORE]. This section defines additional rules for
XMPP-compliant instant messaging and presence servers.
...
... one or more resolutions of the form "_im.<proto>.example.com." or
"_pres.<proto>.example.com.", where "<proto>" would be a label
registered in the Instant Messaging SRV Protocol Label registry
or the Presence SRV ...
...
This section summarizes the specific aspects of the Extensible
Messaging and Presence Protocol that MUST be supported by instant
messaging and presence servers and clients in order to be considered
...
... XMPP-CORE]. The text in this section
specifies additional compliance requirements for instant messaging
and presence servers and clients ...
... Note also that a server or client MAY support only presence or
instant messaging, and is not required to support both if only a
presence service or an instant messaging service ...
... instant messaging, and is not required to support both if only a
presence service or an instant messaging service is desired.
...
...
In addition to core server compliance requirements, an instant
messaging and presence server MUST additionally support the following
protocols:
...
... protocols:
o All server-related instant messaging and presence syntax and
semantics defined in this document, including presence broadcast
...
... In addition to core client compliance requirements, an instant
messaging and presence client MUST additionally support the following
protocols:
...
...
o All client-related instant messaging syntax and semantics defined
in this document, including presence subscriptions ...
... XMPP-CORE].
Additional considerations that apply only to instant messaging and
presence applications of XMPP are defined in several places within
...
... Instant Messaging SRV Protocol Label Registration ...
...
Address Resolution for Instant Messaging and Presence [IMP-SRV]
defines an Instant Messaging SRV Protocol ...
... Instant Messaging and Presence [IMP-SRV]
defines an Instant Messaging SRV Protocol Label registry for
protocols that can provide services ...
... Specification: RFC 3921prop
Description: Instant messaging protocol label for the Extensible
Messaging and Presence Protocol (XMPP) as defined by RFC 3921prop ...
... Day, M., Aggarwal, S., Mohr, G., and J. Vincent, "Instant Messaging/Presence Protocol Requirements", RFC 2779 ...
... Peterson, J., "Address Resolution for Instant Messaging and Presence", RFC 3861prop, August 2004. ...
... Day, M., Rosenberg, J., and H. Sugano, "A Model for Presence and Instant Messaging", RFC 2778, February 2000. ...
... XMPP. This section summarizes the differences that relate
specifically to instant messaging and presence applications, while
the corresponding section of [XMPP-CORE] summarizes the differences
...
... base protocol also
included Ryan Eatmon, Peter Millard, Thomas Muldowney, and Dave
Smith. Work specific to instant messaging and presence by the XMPP
Working Group ...