XMPP
Click on the red underlined text to get to the source
... CPIM specifications, mainly for the purpose of
establishing gateways between XMPP services and non-XMPP services ...
... IMP-REQS]. Such a gateway, referred to herein as an
"XMPP-CPIM gateway", may be established to interpret the protocols of
one service and translate them into the protocols of the other
...
... +-------------+ +-------------+ +------------+
| | | | | |
| XMPP | | XMPP-CPIM | | Non-XMPP ...
... This memo defines a mapping for use by a gateway that translates
between XMPP and a non-XMPP protocol via the CPIM specifications.
...
... gateway that translates
between XMPP and a non-XMPP protocol via the CPIM specifications.
Such a gateway ...
... Such a gateway is not an intermediate hop on a network of non-XMPP
servers (whose native formats may or may not be defined by the CPIM
...
... servers (whose native formats may or may not be defined by the CPIM
specifications), but a dedicated translator between XMPP and a
non-XMPP protocol, where the CPIM ...
... specifications), but a dedicated translator between XMPP and a
non-XMPP protocol, where the CPIM specifications define the common
formats into which the protocols are translated for purposes of
...
... encrypted or signed for end-to-end security.
For information about secure communications to or from an XMPP
service through an XMPP-CPIM gateway ...
...
XMPP and CPIM are distinctly foreign technologies. Therefore, care
must be taken in mapping between XMPP ...
... XMPP and CPIM are distinctly foreign technologies. Therefore, care
must be taken in mapping between XMPP and the abstract syntax defined
by the CPIM specifications.
...
... presence stanzas are two of the core data elements defined in
XMPP and are often used to exchange instant messages and presence
information between IM ...
... semantics of these stanza
types for other purposes). XMPP is not based on [MIME]; instead,
[XMPP-CORE ...
... XML schema.
The approach taken herein is to specify mappings from XMPP elements
and attributes to the headers ...
... Address mapping may be required since the address formats used to
identify XMPP entities (specified in [XMPP-CORE]) are different from
those used to identify instant inboxes (the im: URI scheme ...
... CPP]). In particular, different characters are allowed in im: and
pres: URIs than are allowed in XMPP addresses:
...
... US-ASCII] characters are allowed in im:/pres: URIs
but not in XMPP addresses: #26; (&), #27; ('), and #2f; (/).
o Many non-US-ASCII ...
... US-ASCII (specifically, UTF-8) characters are allowed in
XMPP addresses but not allowed in im:/pres: URIs, since XMPP ...
... XMPP addresses but not allowed in im:/pres: URIs, since XMPP
allows internationalized local-part addresses.
...
... address
6. Prepend with 'im:' scheme (for XMPP <message/> stanzas) or
'pres:' scheme (for XMPP ...
...
This section defines the mapping of syntax primitives from XMPP
message stanzas to "Message/CPIM ...
... Content-type: text/plain; charset=us-ascii". Because XMPP
uses the [UTF-8] character encoding ...
... resource binding as defined in [XMPP-CORE]. Thus
an XMPP-CPIM gateway will receive from the sender's XMPP server a
...
... an XMPP-CPIM gateway will receive from the sender's XMPP server a
message stanza containing a "from" address ...
... address of the form
<user@host/resource>. To map the 'from' attribute of an XMPP message
stanza to the 'From' header ...
... Address Mapping
XMPP 'from' attribute
<message from='juliet@example.com/balcony'>
...
...
... header
of a "Message/CPIM" object. In XMPP, the sender SHOULD include a
'to' attribute on a message stanza ...
... stanza, and MUST include it if the
message is intended for delivery to another user. Thus an XMPP-CPIM
gateway will receive from the sender's XMPP server a message stanza ...
... delivery to another user. Thus an XMPP-CPIM
gateway will receive from the sender's XMPP server a message stanza
containing a "to" address ...
... host> or
<user@host/resource>. To map the 'to' attribute of an XMPP message
stanza to the 'To' header ...
... Address Mapping
XMPP 'to' attribute
<message to='romeo@example.net/orchard'>
...
...
...
An XMPP message stanza MAY possess an 'id' attribute, which is used
by the sending application for the purpose of tracking stanzas ...
... unique identifier such as is defined by the MIME
Content-ID header. Because the XMPP 'id' attribute does not have the
same meaning as the MIME Content-ID header ...
... to that header; however, if the 'id' is known to be unique (e.g., if
it is generated to be unique by the XMPP server and that fact is
known by the XMPP-CPIM gateway), then it SHOULD be so mapped.
...
... it is generated to be unique by the XMPP server and that fact is
known by the XMPP-CPIM gateway), then it SHOULD be so mapped.
...
...
An XMPP message stanza MAY possess a 'type' attribute, which is used
by the sending application to capture ...
... capture the conversational context of
the message. There is no mapping of an XMPP 'type' attribute to a
"Message/CPIM" header ...
... MIME features, or encapsulated text
content. Therefore if an XMPP stanza received by an XMPP-CPIM
gateway possesses a 'type' attribute, the gateway ...
... content. Therefore if an XMPP stanza received by an XMPP-CPIM
gateway possesses a 'type' attribute, the gateway SHOULD ignore the
value provided.
...
... element to
specify the conversation thread in which the message is situated.
There is no mapping of an XMPP <thread/> element to a "Message/CPIM"
...
... MIME features, or encapsulated text content. Therefore
if an XMPP message stanza received by an XMPP-CPIM gateway contains a
...
... if an XMPP message stanza received by an XMPP-CPIM gateway contains a
<thread/> child element, the gateway ...
... CPIM" object, the gateway SHOULD simply map the XML
character data of the XMPP <subject/> element to the value of the
...
...
The <body/> child element of an XMPP message stanza is used to
provide the primary meaning of the message. The XML character data ...
... provide the primary meaning of the message. The XML character data
of the XMPP <body/> element maps to the encapsulated text message ...
... Message Body
XMPP message <body/>
<message>
<body>Wherefore art thou, Romeo?</body>
...
...
As defined in [XMPP-CORE], an XMPP message stanza may contain
"extended" content in any namespace ...
... namespace as defined in [XMPP-E2E],
an XMPP-CPIM gateway SHOULD ignore such information and not pass it
through the gateway to the intended recipient. No mapping for such
...
... those described above, but there is no exact analogue for those
headers in the core XMPP specifications. These include:
o cc -- specifies the address ...
... o Require -- specifies mandatory-to-recognize features
An XMPP-CPIM gateway MAY independently generate such headers based on
its own information (e.g., the datetime ...
... datetime at which it received a
message stanza from an XMPP entity) or based on data encoded in
non-core XMPP ...
... XMPP entity) or based on data encoded in
non-core XMPP extensions, but rules for doing so are out of scope for
this memo.
...
... This section defines the mapping of syntax primitives from
"Message/CPIM" objects with encapsualted text content to XMPP message
stanzas.
...
... header of a "Message/CPIM" object maps to the 'from'
attribute of an XMPP message stanza. To map the CPIM 'From' header ...
... From: Romeo Montague <im:romeo@example.net>
XMPP 'from' attribute
<message from='romeo@example.net'>
...
...
... header of a "Message/CPIM" object maps to the 'to' attribute
of an XMPP message stanza. To map the CPIM 'To' header ...
... gateway possesses knowledge of
the resource identifier in use by the XMPP entity, the gateway MAY
...
... To: Juliet Capulet <im:juliet@example.com>
XMPP 'to' attribute
<message to='juliet@example.com/balcony'>
...
...
...
The core XMPP specification does not include syntax for specifying a
"courtesy copy" (non-primary addressee) for a message stanza ...
... courtesy copy" (non-primary addressee) for a message stanza.
Therefore, if an XMPP-CPIM gateway receives a "Message/CPIM" object
that contains a 'cc' header ...
... header, it SHOULD NOT pass the information
contained in that header on to the XMPP recipient.
...
...
The core XMPP specification does not include syntax for specifying
the datetime at which a message stanza ...
... datetime at which a message stanza was sent. Therefore, if an
XMPP-CPIM gateway receives a "Message/CPIM" object that contains a
'DateTime ...
... header, it SHOULD NOT pass the information contained in
that header on to the XMPP recipient.
...
... header to specify
the namespace of a feature extension. An XMPP-CPIM gateway MUST NOT
pass such headers through to the XMPP ...
... XMPP-CPIM gateway MUST NOT
pass such headers through to the XMPP recipient, and no mapping for
such headers is defined.
...
... specify mandatory-to-recognize features. In general, such a header
would be included by the non-XMPP sending application to (1) insist
that the receiving application needs to understand functionality
...
... order to understand the contents of the message (e.g.,
"Locale.MustRenderKanji"). Because the mandatory-to-recognize
features would be required of the XMPP receiving application rather
than the XMPP-CPIM gateway ...
... XMPP receiving application rather
than the XMPP-CPIM gateway itself, the gateway cannot properly handle
the 'Require' header ...
... the 'Require' header without detailed knowledge about the
capabilities of the XMPP receiving application. Therefore, it seems
appropriate that the XMPP-CPIM gateway ...
... XMPP receiving application. Therefore, it seems
appropriate that the XMPP-CPIM gateway SHOULD return a warning or
error to the non-XMPP sending application if it includes one or more
...
... appropriate that the XMPP-CPIM gateway SHOULD return a warning or
error to the non-XMPP sending application if it includes one or more
'Require' headers in a "Message/CPIM ...
... headers in a "Message/CPIM" object; the exact nature of the
warning or error will depend on the nature of the non-XMPP technology
used by the foreign system, and is not defined herein. Furthermore,
any mapping of the 'Require' header ...
... used by the foreign system, and is not defined herein. Furthermore,
any mapping of the 'Require' header into XMPP or an XMPP extension is
left up to the implementation or to a future specification.
...
... any mapping of the 'Require' header into XMPP or an XMPP extension is
left up to the implementation or to a future specification.
...
... MIME header as
specified in [MIME]. If an XMPP-CPIM gateway receives a MIME object
that includes a Content-ID ...
... Content-ID: <123456789@example.net>
XMPP 'id' attribute (OPTIONAL)
<message id='123456789@example.net'>
...
... text message content maps to the XML character
data of the <body/> child element of an XMPP message stanza.
...
... Wherefore art thou?
XMPP message <body/>
<message id='123456789@example.net'>
...
... If the Content-Type is not "text/plain", the XMPP-CPIM gateway MAY
map the content to an XMPP extension but MUST NOT map it to the
...
... text/plain", the XMPP-CPIM gateway MAY
map the content to an XMPP extension but MUST NOT map it to the
<body/> child of the XMPP message stanza ...
... map the content to an XMPP extension but MUST NOT map it to the
<body/> child of the XMPP message stanza, which is allowed to contain
XML character data ...
...
XMPP specifies the existence of a 'type' attribute for XMPP message
stanzas, which enables the sender ...
... context of the message. There is no exact analogue for this
attribute in CPIM. An XMPP-CPIM gateway MAY independently generate
the 'type' attribute based on its own information, but this is
OPTIONAL and rules for doing so are out of scope for this memo.
...
... This section describes how a gateway SHOULD map presence information
between an XMPP service and a non-XMPP service ...
...
This section defines the mapping of syntax primitives from XMPP
presence stanzas to "Message/CPIM ...
... Content-type: text/plain; charset=us-ascii". Because XMPP
uses the [UTF-8] character encoding ...
... encapsulated MIME
object generated by an XMPP-CPIM gateway for presence information
MUST set the 'Content-type' header ...
... resource binding as defined in [XMPP-CORE]. Thus
an XMPP-CPIM gateway will receive from the sender's XMPP server a
...
... an XMPP-CPIM gateway will receive from the sender's XMPP server a
presence stanza containing a "from" address ...
... address of the form
<user@host/resource>. To map the 'from' attribute of an XMPP
presence stanza to the 'From' header ...
... Address Mapping
XMPP 'from' attribute
<presence from='juliet@example.com/balcony'>
...
...
... From: Juliet Capulet <im:juliet@example.com>
In addition, the 'from' attribute of an XMPP presence stanza maps to
the 'entity ...
... PIDF <presence/> root element. To map
the XMPP 'from' attribute to the PIDF 'entity' attribute, the gateway ...
... XMPP-CPIM gateway SHOULD map the resource identifier of
the XMPP address contained in the XMPP 'from' attribute to the 'id'
...
... the XMPP address contained in the XMPP 'from' attribute to the 'id'
attribute of the PIDF <tuple/> child element ...
... Resource Identifier Mapping
XMPP 'from' attribute
<presence from='juliet@example.com/balcony'>
...
...
... header
of a "Message/CPIM" object. In XMPP, the sender MAY include a 'to'
attribute on a presence stanza ...
... address by
the sender's server). Thus an XMPP-CPIM gateway will receive from
the sender's XMPP ...
... XMPP-CPIM gateway will receive from
the sender's XMPP server a presence stanza containing a "to" address
...
... host> or <user@host/resource>. To map the 'to'
attribute of an XMPP presence stanza to the 'To' header of a
...
... Address Mapping
XMPP 'to' attribute
<presence to='romeo@example.net/orchard'>
...
...
...
An XMPP presence stanza MAY possess an 'id' attribute, which is used
by the sending application for the purpose of tracking stanzas ...
... unique identifier such as is defined by the MIME
Content-ID header. Because the XMPP 'id' attribute does not have the
same meaning as the MIME Content-ID header ...
... to that header; however, if the 'id' is known to be unique (e.g., if
it is generated to be unique by the XMPP server and that fact is
known by the XMPP-CPIM gateway), then it SHOULD be so mapped.
...
... it is generated to be unique by the XMPP server and that fact is
known by the XMPP-CPIM gateway), then it SHOULD be so mapped.
...
...
An XMPP presence stanza MAY possess a 'type' attribute. If no 'type'
attribute is included, the presence stanza ...
... probe for current presence; mappings for these other presence types
are defined under XMPP-CPIM Gateway as Presence Service (Section 6).
...
... Example: Available Presence
XMPP available presence
<presence from='juliet@example.com/balcony'/>
...
... Unavailable Presence
XMPP unavailable presence
<presence from='juliet@example.com/balcony' type='unavailable ...
...
The <show/> child element of an XMPP presence stanza provides
additional information about the sender ...
... additional information about the sender's availability. The XML
character data of the XMPP <show/> element maps to extended <status/>
content in PIDF ...
... extended status states in the 'urn:ietf:params:xml:ns:pidf:im'
namespace, the XMPP values will be mapped to the PIDF values.
...
...
The <status/> child element of an XMPP presence stanza provides a
user-defined, natural-language ...
... priority/>
element is negative, an XMPP-CPIM gateway MUST NOT map the value. The
range of allowable values for the PIDF ...
... priority' attribute is any
decimal number from zero to one inclusive, with a maximum of three
decimal places. If an XMPP-CPIM gateway maps these values, it SHOULD
treat XMPP <priority ...
... decimal places. If an XMPP-CPIM gateway maps these values, it SHOULD
treat XMPP <priority>0</priority> as PIDF ...
... PIDF priority='1', mapping intermediate
values appropriately so that they are unique (e.g., XMPP priority 1
to PIDF ...
... priority 0.992;
note that this is an example only, and that the exact mapping shall
be determined by the XMPP-CPIM gateway).
Example: Presence Priority ...
...
As defined in [XMPP-CORE], an XMPP presence stanza may contain
"extended" content in any namespace ...
... namespace as defined in [XMPP-E2E],
an XMPP-CPIM gateway SHOULD ignore such information and not pass it
through the gateway to the intended recipient. No mapping for such
...
... those described above, but there is no exact analogue for those
headers in the core XMPP specifications. These include:
o cc -- specifies the address ...
... o Require -- specifies mandatory-to-recognize features
An XMPP-CPIM gateway MAY independently generate such headers based on
its own information (e.g., the datetime ...
... datetime at which it received a
presence stanza from an XMPP entity) or based on data encoded in
non-core XMPP ...
... XMPP entity) or based on data encoded in
non-core XMPP extensions, but rules for doing so are out of scope for
this memo.
...
... XML elements in addition to those
described above, but there is no exact analogue for those XML
elements in the core XMPP specifications. These include:
o <contact/> -- specifies an address ...
... URI) at which one may communicate with the presentity; an
XMPP-CPIM gateway MAY include this element, in which case it
SHOULD set its value to the <user@host ...
... this element, in which case it
SHOULD set its value to the <user@host> of the XMPP sender,
prepended by the "im:" Instant Messaging ...
... timestamp/> -- specifies the datetime at which the presence
information was sent; an XMPP-CPIM gateway MAY independently
generate this element based on its own information (e.g., the
...
... datetime at which it received the presence stanza from an XMPP
entity) or based on data encoded in non-core XMPP ...
... XMPP
entity) or based on data encoded in non-core XMPP extensions, but
rules for doing so are out of scope for this memo.
...
... CPIM" object maps to the <user@host>
portion of the 'from' attribute of an XMPP presence stanza, and the
'id' attribute of the PIDF ...
... element maps to the
resource identifier portion XMPP 'from' attribute. Therefore, to map
the CPIM and PIDF ...
... CPIM "Formal-name" (if
provided) in order to generate the <user@host> portion of the XMPP
'from' attribute, then add a '/' character followed by the value of
the PIDF ...
... From: Romeo Montague <im:romeo@example.net>
XMPP 'from' attribute
<presence from='romeo@example.net'>
...
...
... Resource Identifier Mapping
XMPP 'from' attribute
<presence from='juliet@example.com/balcony'>
...
...
... header of a "Message/CPIM" object maps to the 'to' attribute
of an XMPP presence stanza. To map the CPIM 'To' header ...
... presence stanza. To map the CPIM 'To' header to the XMPP
'to' attribute, the gateway MUST remove ...
... gateway possesses knowledge of
the resource identifier in use by the XMPP entity, the gateway MAY
...
... To: Juliet Capulet <im:juliet@example.com>
XMPP 'to' attribute
<presence to='juliet@example.com/balcony'>
...
...
...
The core XMPP specification does not include syntax for specifying a
"courtesy copy" (non-primary addressee) for a presence stanza ...
... courtesy copy" (non-primary addressee) for a presence stanza.
Therefore, if an XMPP-CPIM gateway receives a "Message/CPIM" object
with encapsulated ...
... header, it SHOULD
NOT pass the information contained in that header on to the XMPP
recipient.
...
...
The core XMPP specification does not include syntax for specifying
the datetime at which a presence stanza ...
... datetime at which a presence stanza was sent. Therefore, if an
XMPP-CPIM gateway receives a "Message/CPIM" object with encapsulated
...
... header, it SHOULD NOT pass the
information contained in that header on to the XMPP recipient.
...
... header of a "Message/CPIM" object. Therefore, if an
XMPP-CPIM gateway receives a "Message/CPIM" object with encapsulated
...
... header, it SHOULD NOT pass the
information contained in that header on to the XMPP recipient.
...
... header to specify
the namespace of a feature extension. An XMPP-CPIM gateway MUST NOT
pass such headers through to the XMPP ...
... XMPP-CPIM gateway MUST NOT
pass such headers through to the XMPP recipient, and no mapping for
such headers is defined.
...
... CPIM" objects MAY include an optional 'Require' header to
specify mandatory-to-recognize features. An XMPP-CPIM gateway MUST
NOT pass such headers through to the XMPP ...
... XMPP-CPIM gateway MUST
NOT pass such headers through to the XMPP recipient, and no mapping
for such headers is defined.
...
... MIME header as
specified in [MIME]. If an XMPP-CPIM gateway receives a MIME object
that includes a Content-ID ...
... Content-ID: <123456789@example.net>
XMPP 'id' attribute (OPTIONAL)
<presence id='123456789@example.net'>
...
...
... PIDF are OPEN and CLOSED.
The PIDF basic presence status of OPEN maps to an XMPP presence
stanza that possesses no 'type' attribute (indicating default
availability). The PIDF ...
... availability). The PIDF basic presence status of CLOSED maps to an
XMPP presence stanza that possesses a 'type' attribute with a value
of "unavailable ...
... </presence>
XMPP available presence
<presence from='romeo@example.net/orchard'/>
...
... </presence>
XMPP unavailable presence
<presence from='romeo@example.net/orchard'
...
... PIDF documents may contain extended <status/> content. As of this
writing there are no pre-defined extended status states that can be
mapped to the defined values of the XMPP <show/> element ('away',
'chat', 'dnd', and 'xa'). Once PIDF ...
... presence stanza; an
entity on the non-XMPP side of an XMPP-CPIM gateway SHOULD NOT send
such a PIDF ...
... entity on the non-XMPP side of an XMPP-CPIM gateway SHOULD NOT send
such a PIDF document to an XMPP ...
... XMPP-CPIM gateway SHOULD NOT send
such a PIDF document to an XMPP recipient if possible, and an
XMPP-CPIM gateway MUST NOT map such a PIDF ...
... PIDF document to an XMPP recipient if possible, and an
XMPP-CPIM gateway MUST NOT map such a PIDF document to an XMPP
...
... XMPP-CPIM gateway MUST NOT map such a PIDF document to an XMPP
presence stanza (see Zero Resources (Section 6.3.2)).
...
... tel:, or mailto: URI). The core XMPP specification does not include
syntax for specifying the URI of a contact address ...
... address, since the contact
address is implicit in the 'from' attribute of the XMPP presence
stanza. Therefore, if an XMPP-CPIM gateway receives a "Message/CPIM ...
... address is implicit in the 'from' attribute of the XMPP presence
stanza. Therefore, if an XMPP-CPIM gateway receives a "Message/CPIM"
object with encapsulated ...
... XML character data of the <contact/>
element on to the XMPP recipient. (However, see Inclusion of
Complete PIDF Document (Section 5.2.15) below.)
...
... </presence>
XMPP presence stanza
<presence from='romeo@example.net/orchard'/>
...
... attribute MAY be mapped to the <priority/> child element of an XMPP
presence stanza. An XMPP-CPIM gateway ...
... priority/> element. If an
XMPP-CPIM gateway maps these values, it SHOULD treat PIDF
priority ...
... PIDF priorities between 0.008 and 0.015 to
XMPP priority 2, and so on up through mapping PIDF priorities ...
... PIDF priorities between
0.992 and 0.999 to XMPP priority 126; note that this is an example
only, and that the exact mapping shall be determined by the XMPP-CPIM
gateway ...
... XMPP priority 126; note that this is an example
only, and that the exact mapping shall be determined by the XMPP-CPIM
gateway).
...
...
The core XMPP specification does not include syntax for specifying
the datetime or timestamp ...
... timestamp at which a presence stanza was sent.
Therefore, if an XMPP-CPIM gateway receives a "Message/CPIM" object
with encapsulated ...
... Certain PIDF elements do not map to XMPP presence stanza syntax
(e.g., the XML character data ...
... XML character data of the <contact/> element). However,
an XMPP client may be able to handle such information by parsing a
native PIDF ...
... client may be able to handle such information by parsing a
native PIDF document. To make this possible, an XMPP-CPIM gateway
MAY include the complete PIDF document as a child element ...
... presence stanza, as described in [XMPP-PIDF]. If an XMPP client does
not understand this extended data, it naturally MUST ignore it.
...
... XMPP-CPIM Gateway as Presence Service ...
... semantics for an abstract presence service. An
XMPP-CPIM gateway MAY function as such a presence service, and if so
an XMPP ...
... XMPP-CPIM gateway MAY function as such a presence service, and if so
an XMPP entity can use defined XMPP syntax to interact with the
...
... semantic operations such as subscribe, this section defines only
the XMPP interactions with the presence service offered by an
XMPP-CPIM gateway ...
... XMPP interactions with the presence service offered by an
XMPP-CPIM gateway, not the translation of such XMPP syntax into PIDF.
...
... presence service offered by an
XMPP-CPIM gateway, not the translation of such XMPP syntax into PIDF.
(Note: Detailed information about XMPP ...
... XMPP syntax into PIDF.
(Note: Detailed information about XMPP presence services can be found
in [XMPP-IM ...
... presence services can be found
in [XMPP-IM]; as much as possible, an XMPP-CPIM gateway SHOULD
implement the syntax, semantics, and server business rules ...
... entity wants to subscribe to the presence information of a
non-XMPP presentity through an XMPP-CPIM gateway, it MUST send a
presence stanza ...
... subscribe to the presence information of a
non-XMPP presentity through an XMPP-CPIM gateway, it MUST send a
presence stanza of type "subscribe ...
... syntax mapping is as follows:
o The XMPP 'from' attribute (user@host) MUST be mapped to the CPP
...
... "watcher parameter" field (pres:user@host). The XMPP-CPIM gateway
MUST append the "pres:" Presence URI scheme to the front of the
...
... "target parameter" field (pres:user@host). The XMPP-CPIM gateway
MUST append the "pres:" Presence URI scheme to the front of the
...
... XMPP mapping for the CPP "duration parameter", since
XMPP subscriptions are active until they have been explicitly
"unsubscribed ...
... whatever protocol it uses to interact with the gateway), the
XMPP-CPIM gateway MUST return a presence stanza of type "subscribed"
to the XMPP ...
... XMPP-CPIM gateway MUST return a presence stanza of type "subscribed"
to the XMPP entity and notify the XMPP entity ...
... target presentity denies the subscription request, the
XMPP-CPIM gateway MUST return a presence stanza of type
"unsubscribed ...
... presence stanza of type
"unsubscribed" to the XMPP entity and MUST NOT invoke the notify
operation.
...