From 622e9b08ba9782c5d56b353bb868e6b895455f40 Mon Sep 17 00:00:00 2001 From: Georg Lukas Date: Mon, 9 Sep 2019 18:09:29 +0200 Subject: [PATCH 1/5] XEP-0280: remove error note, add XEP-0333 --- xep-0280.xml | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/xep-0280.xml b/xep-0280.xml index 47e8ccb4..10916709 100644 --- a/xep-0280.xml +++ b/xep-0280.xml @@ -330,8 +330,8 @@

To properly handle messages exchanged with a MUC (or similar service), the server must be able to identify MUC-related messages. This can be accomplished by tracking the clients' presence in MUCs, or by checking for the <x xmlns="http://jabber.org/protocol/muc#user"> element in messages. The following rules apply to MUC-related messages: From 64f87e1d2ac8c60edd1355bc96ecfda25a603fc8 Mon Sep 17 00:00:00 2001 From: Georg Lukas Date: Wed, 8 Sep 2021 18:58:36 +0200 Subject: [PATCH 2/5] XEP-0280: Remove the removal of the `` element The requirement to strip `` by the sending server was in the XEP from day 1. It was later changed from "MUST" to "SHOULD" and from "sending server" to "receiving server", so that the latter could also prevent normal message routing. As this behavior only ever affected the `` element and not the `` hint (introduced in 2017), which should be treated in a similar but not equal way, and there is a security benefit in letting the receiving client know that message routing was manipulated, it makes sense to remove this requirement. As there is no negative effect of keeping another element in delivered messages, nobody complained about `` not being stripped, and bumping Carbons today would be rather unfortunate, this is done without a namespace bump, despite "breaking" the specification. --- xep-0280.xml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/xep-0280.xml b/xep-0280.xml index 10916709..fff54c11 100644 --- a/xep-0280.xml +++ b/xep-0280.xml @@ -466,9 +466,9 @@

  • The sending client MAY exclude a &MESSAGE; from being forwarded to other Carbons-enabled resources, by adding a <private/> element qualified by the namespace "urn:xmpp:carbons:2" and a <no-copy/> hint as described in &xep0334; as child elements of the &MESSAGE; stanza.
  • The sending server MUST NOT deliver forwarded &MESSAGE;s to the other Carbons-enabled resources of the sender.
  • The receiving server MUST NOT deliver forwarded &MESSAGE;s to the other Carbons-enabled resource of the recipient,
    • -
  • and the receiving server SHOULD remove the <private/> element before delivering to the recipient.
    • +

    Interoperability note: earlier versions of this XEP required or recommended the removal of the <private/> element (albeit not of the <no-copy/> hint) by one of the involved servers, but this behavior was considered as a potential security issue as the sender could silently manipulate the delivery of messages, so that the requirement was lifted. However, clients MUST NOT assume that a message without the element was actually routed to all other resources of the account.

    Note: Use of the private mechanism might lead to partial conversations on other devices. This is the intended effect. If the private &MESSAGE; stanza is addressed to a bare JID, the receiving server still delivers it according to RFC 6121. This might result in a copy being delivered to each resource for the recipient, which effectively negates the behavior of the <private/> element for recipients.

    From 9568fda8c747aaf91a48f8f9030d059fab17e45e Mon Sep 17 00:00:00 2001 From: Georg Lukas Date: Wed, 8 Sep 2021 19:15:17 +0200 Subject: [PATCH 3/5] XEP-0280: Mobile Considerations: replace with CS Mobile link --- xep-0280.xml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/xep-0280.xml b/xep-0280.xml index fff54c11..80371a14 100644 --- a/xep-0280.xml +++ b/xep-0280.xml @@ -529,7 +529,7 @@

    Forwarded inbound messages MUST NOT be auto-replied to unless the client has some way of ensuring no more than one auto-reply is sent from all of its user's resources.

    -

    Enabling this protocol on mobile devices needs to be undertaken with care. This protocol can result in additional bandwidth and power usage, possibly decreasing battery lifetime and increasing monetary costs. Additional mechanisms for controlling the Carbon-copying of individual conversations might need to be added to deal with mobile clients in the future.

    +

    Mobile clients are often connected to the server in parallel to another (desktop) client. Therefore, it is highly recommended for mobile clients to implement this protocol to receive all live traffic, and to generally follow the Mobile Compliance Suite recommendations.

     From f7bd573690a88681addda25cfb3885f48d8fc1e7 Mon Sep 17 00:00:00 2001 From: Georg Lukas Date: Wed, 22 Sep 2021 17:38:28 +0200 Subject: [PATCH 4/5] XEP-0280: use new permalink for "current" Compliance Suite --- xep-0280.xml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/xep-0280.xml b/xep-0280.xml index 80371a14..a2cfa00a 100644 --- a/xep-0280.xml +++ b/xep-0280.xml @@ -529,7 +529,7 @@

    Forwarded inbound messages MUST NOT be auto-replied to unless the client has some way of ensuring no more than one auto-reply is sent from all of its user's resources.

    -

    Mobile clients are often connected to the server in parallel to another (desktop) client. Therefore, it is highly recommended for mobile clients to implement this protocol to receive all live traffic, and to generally follow the Mobile Compliance Suite recommendations.

    +

    Mobile clients are often connected to the server in parallel to another (desktop) client. Therefore, it is highly recommended for mobile clients to implement this protocol to receive all live traffic, and to generally follow the Mobile Compliance Suite recommendations.

         From db6a3c4134edfe0a0808c09094b1ce260d023b09 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Jonas=20Sch=C3=A4fer?= Date: Tue, 28 Sep 2021 22:12:34 +0200 Subject: [PATCH 5/5] XEP-0280: add revision block --- xep-0280.xml | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/xep-0280.xml b/xep-0280.xml index a2cfa00a..6dc2062b 100644 --- a/xep-0280.xml +++ b/xep-0280.xml @@ -53,6 +53,12 @@ georg@op-co.de georg@yax.im + + 0.14.0 + 2021-09-28 + gl +

    Incorporate LC feedback: Remove requirement to remove "private" elements (and add interop note), completely reword mobile considerations to fit modern reality.

     +     0.13.4 2021-05-25