From ea1f090ed3707793f8a9b0d1ff26de4205190a05 Mon Sep 17 00:00:00 2001 From: Mickael Remond Date: Fri, 7 Aug 2015 12:47:31 +0200 Subject: [PATCH] Improve wording based on feedback from @Flowdalic --- xep-0033.xml | 27 +++++++++++++-------------- 1 file changed, 13 insertions(+), 14 deletions(-) diff --git a/xep-0033.xml b/xep-0033.xml index 4cda3526..0b932ecc 100644 --- a/xep-0033.xml +++ b/xep-0033.xml @@ -286,20 +286,19 @@ -

To ensure that entities that have received directed - presence through a multicast service will get the unvailable - presence when the originating client closes the its session, - the multicast service should also relay unvailable presence - stanzas.

-

When transferring an extended addressing presence stanza, - the multicast service MUST keep track of the entities that - have received the individual directed presence packets.

-

When the multicast service receive an unavailable presence - stanza without extended addresses, it MUST broadcast the - updated presence to all the entities that have received a - directed presence previously (if the multicast service has not - yet sent unavailable presence to a precise entity through a - previous extended stanza presence).

+ +

The multicast service MUST keep track of the entities it + sent a presence with an absent 'type' attribute (i.e. an + 'available' presence) to and the originating entity of that + presence. If the multicast service receives an unavailable + presence from one of the tracked originating entities, it MUST + broadcast this presence to all tracked entities which have not + yet received an unavailable presence from the originating + entity, even if the presence does not contain explicit + broadcast addresses. Thus the multicast service ensures that + all entities, which have received an (directed) 'available' + presence over it, receive the related 'unavailable' + presence.