From 8480980769324535c3e4240e579978a48fe6327d Mon Sep 17 00:00:00 2001 From: Steve Kille Date: Wed, 6 Jun 2018 14:09:04 +0100 Subject: [PATCH] Editorial --- xep-0403.xml | 25 +++++++++++++++++-------- 1 file changed, 17 insertions(+), 8 deletions(-) diff --git a/xep-0403.xml b/xep-0403.xml index 42ab8d8f..3bedfa22 100644 --- a/xep-0403.xml +++ b/xep-0403.xml @@ -38,6 +38,14 @@ MIX-PRESENCE &ksmithisode; &skille; + + 0.2.1 + 2018-06-06 + sek +

+ +

+ 0.2.0 2018-06-05 @@ -48,7 +56,8 @@ Add vCard routing; Add mix information to presence;

- + + 0.1.0 2018-05-21 sek @@ -63,7 +72,7 @@

MIX-CORE shares participant JIDs, which enables messages to be exchange directly. - To facilitate communication between clients IQ stanza messages MAY be routed through a MIX channel. This is needed because many XMPP clients will block IQ stanzas from an unknown JID. Routing IQ stanzas avoids this. + To facilitate communication between clients IQ stanzas MAY be routed through a MIX channel. This is needed because IQ stanzas from an unknown JID may be blocked. Routing IQ stanzas through the channel avoids this.

@@ -76,8 +85,8 @@
  • The mechanism must work cleanly for participants with multiple clients.
  • Standard presence messages must be used to share presence.
  • Nick changes should be visible as changes (and not as a new user).
    • -
  • Where &xep0404; (MIX-ANON) is not used, participants must be able to directly contact other participants.
    • -
  • IQ stanzas, including vCard, can be communicated through a channel.
    • +
  • Where &xep0404; (MIX-ANON) is not used, a mechanism is needed so that participants are able to directly contact other participants.
    • +
  • IQ stanzas, including vCard, can be be sent indirectly through a MIX channel.
    • @@ -87,7 +96,7 @@

    - A MIX channel MAY distribute presence information about channel participants. In order to share JID and Nick information about a participant, this information is encoded in the presence message. This allows full presence information to be shared for each participant without the need for the client to perform any lookup. + A MIX channel implementing this specification MUST be able to distribute presence information about channel participants. In order to share JID and Nick information about a participant, this information is encoded in the presence message. This allows full presence information to be shared for each participant without the need for the client to perform any lookup.

    @@ -98,9 +107,9 @@ Participants in Presence messages and in IQ messages relayed through a channel are identified by an encoded JID of the form are encoded, using the format "<stable-participant-identifier>#<channel>@<mix domain>". This provides a stable JID for each participant. This JID format is used in three places:

      -
    1. The 'from' of presence stanzas generated by the channel.
      2. -
    2. The 'to' of IQ stanzas being sent to the channel.
      3. -
    3. The 'from' of IQ stanzas coming from the channel.
      4. +
    4. The 'from' of presence stanzas generated by the channel, where the from encodes the Stable Participant ID of the participant to which the presence stanza relates.
      5. +
    5. The 'to' of IQ stanzas being addresses to a participant and being sent to the channel for indirect communication.
      6. +
    6. The 'from' of IQ stanzas coming from the channel, to reflect the sending participant where this stanza is being relayed by the channel.

    These JIDs will be used to represent specific JID clients. The resource associated with the encoded JID MUST be the resource value from the associated client JID, except where MIX-ANON is followed.