From 660684bf672aea107e64780f6d625b2b5a632233 Mon Sep 17 00:00:00 2001 From: Steve Kille Date: Wed, 6 Jun 2018 10:40:26 +0100 Subject: [PATCH 1/3] Clarify that PMs can be used in JID Visible channels; --- xep-0404.xml | 12 ++++++++++-- 1 file changed, 10 insertions(+), 2 deletions(-) diff --git a/xep-0404.xml b/xep-0404.xml index af387221..09085aad 100644 --- a/xep-0404.xml +++ b/xep-0404.xml @@ -37,6 +37,14 @@ MIX-ANON &ksmithisode; &skille; + + 0.2.1 + 2018-06-06 + sek +

+ Clarify that PMs can be used in JID Visible channels; +

+ 0.2.0 2018-06-05 @@ -75,9 +83,9 @@

- &xep0369; exposes participant JIDs to other participants, and so messages can always be sent directly. When JIDs are hidden this is no longer possible. + &xep0369; exposes participant JIDs to other participants, and so messages MAY be sent directly. When JIDs are hidden this is no longer possible. Private messages MAY be sent to channel participants if allowed by channel policy. Private messages are switched through the channel to hide addressing. - +Private messages MAY be switched through the channel when JIDs are visible. This might be useful. for example where sending messages directly is blocked.

From a169bcf91629225c82b9f732d20276e791acaa35 Mon Sep 17 00:00:00 2001 From: Steve Kille Date: Wed, 6 Jun 2018 10:47:30 +0100 Subject: [PATCH 2/3] Editorial --- xep-0404.xml | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/xep-0404.xml b/xep-0404.xml index 09085aad..66ed92cf 100644 --- a/xep-0404.xml +++ b/xep-0404.xml @@ -119,13 +119,13 @@ Private messages MAY be switched through the channel when JIDs are visible. Thi

- MUC hides real JIDs by using Nicks to identify room occupants. This has problems with Nick changing and with multiple active clients for the same user. MIX identifies channel participants by Stable Participant ID. In &xep0369;, the users JID is in the participants node and is shared in messages and presence. To hide JIDs, this specification makes three key changes + MUC hides real JIDs by using Nicks to identify room occupants. This has problems with Nick changing and with multiple active clients for the same user. MIX identifies channel participants by Stable Participant ID. In &xep0369;, the user's JID is in the participants node and is shared in messages and presence. To hide JIDs, this specification makes three key changes

  1. The requirement to include real JID in the participants list is relaxed for channels that are not "JID Visible". For a "JID Hidden" channel, real JIDs MUST NOT be included in the participants list. For a "JID Maybe Visible" channel, real JIDs will be included in the participants node according to participant preference.
    2. -
  2. JIDs are not shared in messages and presence.
    3. +
  3. JIDs are not shared in messages and presence, unless the recipient has permission to see the JID. Note that in JID Maybe Visible channels, this leads to the creation of two variants of message and presence. The MAM archive MUST hold only the variant without the JID, in order to prevent leaking of this information.
  4. In presence messages, the client resource is anonymized, to prevent leakage of information through the resource.
@@ -136,7 +136,7 @@ This change means that the client will not be able to determine real JID of the

- It is important that MUC owners and administrators are able to see the JIDs of participant. For this reason, a MIX channel following this specification MUST hold a JID Map node, which gives a mapping between Stable Participant ID and JID. + It is important that MUC owners and administrators are able to see the JIDs of participants. For this reason, a MIX channel following this specification MUST hold a JID Map node, which gives a mapping between Stable Participant ID and JID.

From 5c5915167531833b3ff5659ded388c4833b441cf Mon Sep 17 00:00:00 2001 From: Steve Kille Date: Wed, 6 Jun 2018 11:35:14 +0100 Subject: [PATCH 3/3] Editorial --- xep-0404.xml | 14 +++++++------- 1 file changed, 7 insertions(+), 7 deletions(-) diff --git a/xep-0404.xml b/xep-0404.xml index 66ed92cf..ffd97adf 100644 --- a/xep-0404.xml +++ b/xep-0404.xml @@ -152,13 +152,13 @@ This change means that the client will not be able to determine real JID of the

When JIDs are being hidden, the resource of the full JIDs stored in the presence node MUST also be anonymized using a similar mechanism. - Where the JID is not being hidden, the resource is simply the resource of the clients full JID. Where the JID is hidden, the resource is replaced with a generated value. For example, 'hag66@shakespeare.example/UUID-a1j/7533' in the channel coven might have an encoded JID of '123456#coven@mix.shakespeare.example/789'. There is no client visible mapping maintained, as this is not needed. The MIX channel will need to maintain a mapping, to support directly addressing clients, such as for client to client disco#info queries. While an encoded JID is held in the presence node, the mapping to real JID MUST NOT be changed. When adding a client to the presence node, the server MAY add the same anonymized JID as used before by that client, or it MAY create a different anonymized JID. + Where the JID is hidden, the resource is replaced with a generated value. For example, 'hag66@shakespeare.example/UUID-a1j/7533' in the channel coven might have an encoded JID of '123456#coven@mix.shakespeare.example/789'. There is no client visible mapping maintained, as this is not needed. The MIX channel will need to maintain a mapping, to support directly addressing clients, such as for client to client disco#info queries. While an encoded JID is held in the presence node, the mapping to real JID MUST NOT be changed. When adding a client to the presence node, the server MAY add the same anonymized JID as used before by that client, or it MAY create a different anonymized JID.

-

This specification defines a JID Map node, so that administrators can see JIDs for JID Hidden channels.

+

This specification defines a JID Map node, so that administrators can see JIDs for JID Hidden channels. This node MUST be present for JID Hidden and JID Maybe Visible channels. This node MAY be present for JID Visible channels. If this node is not present, JIDs will all be available in the participants node.

@@ -170,7 +170,7 @@ This change means that the client will not be able to determine real JID of the

The JID Map node is used to associate a Stable Participant ID to its corresponding bare JID. It is a PubSub node with the 'node' attribute set to 'urn:xmpp:mix:nodes:jidmap'. The JID Map node MUST have one entry for each entry in the Participants node. This value is added when a user joins the channel and is removed when the user leaves the channel. - Each item is identified by Stable Participant ID mapping to the bare JID. This node is used to give administrator access to JIDs. This node MUST NOT be modified directly using pubsub. + Each item is identified by Stable Participant ID mapping to the bare JID. This node is used to give administrator access to JIDs. A MIX server MUST NOT allow this node to be modified directly using pubsub. Only administrators can subscribe to this node. The JID Map node is a permanent node with one item per participant. Information is stored in a <participant/> element qualified by the 'urn:xmpp:mix:anon:0' namespace. The real JID is stored in a <jid/> child element of the <participant/> element.

@@ -357,12 +357,12 @@ This change means that the client will not be able to determine real JID of the

- Private Messages are used to provide communication with another channel participant through the MIX channel, where the initiating user does not know the real JID of the channel participant. A message is addressed to the channel using the encoded JID of the client to which the message is being sent. This is shown in the following example. + Private Messages are used to provide communication with another channel participant through the MIX channel. This may be used where the initiating user does not know the real JID of the channel participant or for other reasons. A message sent through the channel is addressed using the encoded JID of the client to which the message is being sent. Private messages will generally be sent to a bare JID, and this is shown in the following example. Private messages MAY be sent to a full JID.

Private meeting about Macbeth??? @@ -374,13 +374,13 @@ This change means that the client will not be able to determine real JID of the Private meeting about Macbeth??? ]]> -

Private Messages MAY be archived using MAM by the XMPP servers associated with initiator and responder. Private Messages MUST NOT be archived by the MIX channel.

+

Private Messages MUST NOT be archived by the MIX channel. Private Messages MAY be archived using MAM by the XMPP servers associated with initiator and responder.

JID Map'urn:xmpp:mix:nodes:jidmap'For storing a list of Stable Participant IDs from the participants node with a 1:1 mapping to the corresponding JIDs.AutomaticPubSub