network
Click on the red underlined text to get to the source
...
Although XMPP is not wedded to any specific network architecture, to
date it usually has been implemented via a client-server architecture
...
... XMPP and the protocol(s)
used on a foreign (non-XMPP) messaging network
o FN1 = A foreign messaging network ...
... Network ...
...
Because each server is identified by a network address and because
server-to-server communications are a straightforward extension of
...
... the client-to-server protocol, in practice, the system consists of a
network of servers that inter-communicate. Thus, for example,
<juliet@example.com> is able to exchange messages, presence, and
other information with <romeo@example.net>. This pattern is familiar
...
... other information with <romeo@example.net>. This pattern is familiar
from messaging protocols (such as [SMTP]) that make use of network
addressing standards. Communications between any two servers are
...
... network endpoint
(i.e., an ID on the network) and that can communicate using XMPP.
All such entities are uniquely addressable in a form that is
...
... valid JID).
It usually represents the network gateway or "primary" server to
which other entities connect for XML routing ...
... domain identifier for every server or service that will
communicate over a network MAY be an IP address but SHOULD be a fully
qualified domain name (see [DNS ...
... character. It usually represents the entity requesting and using
network access provided by the server or gateway (i.e., a client ...
... XML stream is a container for the
exchange of XML elements between any two entities over a network.
The start of an XML stream ...
... XML stanzas
over the stream to any recipient on the network. When the client
desires to close the stream ...
... ID generated by the receiving server, and a secret known by the
authoritative server's network. The stream ID is security-critical ...
... Receiving Server
in Step 4. Based on this information, as well as shared secret
information within the Authoritative Server's network, the key is
verified. Any verifiable method MAY be used to generate the key. If
...
... information about an entity to which they have subscribed (in this
case, network availability information). In general, a publishing
entity SHOULD send a presence stanza ...
... error type SHOULD be "wait" (note: an
application MUST NOT return this error if doing so would provide
information about the intended recipient's network availability to
an entity that is not authorized to know such information).
...
... authentication and
confidentiality (e.g., on an organization's private network).
Compliant implementations SHOULD support SASL for this purpose.
...