> On 24 Mar 2021, at 16:02, Jonas Schäfer (XSF Editor) <[email protected]>
> wrote:
>
> This message constitutes notice of a Last Call for comments on
> XEP-0280.
>
> Title: Message Carbons
> Abstract:
> In order to keep all IM clients for a user engaged in a conversation,
> outbound messages are carbon-copied to all interested resources.
>
> URL: https://xmpp.org/extensions/xep-0280.html
>
> This Last Call begins today and shall end at the close of business on
> 2021-04-06.
>
> Please consider the following questions during this Last Call and send
> your feedback to the [email protected] discussion list:
>
> 1. Is this specification needed to fill gaps in the XMPP protocol
> stack or to clarify an existing protocol?
Yes.
>
> 2. Does the specification solve the problem stated in the introduction
> and requirements?
It’s probably as good as it’s going to get - it’s a (needed) bandaid for our
routing rather than a fix, but I think we all appreciate at this point that a
true fix is not straightforward.
> 3. Do you plan to implement this specification in your code? If not,
> why not?
Yes.
> 4. Do you have any security concerns related to this specification?
I think the private element is a little risky where a remote user can change
routing behaviour without the recipient knowing because the server has to strip
the private element. ("and the receiving server SHOULD remove the <private/>
element before delivering to the recipient.”). I don’t immediately remember why
the removing of private was necessary, and it seems like it’s probably
undesirable?
> 5. Is the specification accurate and clearly written?
It’s probably as good as it’s going to get.
/K
_______________________________________________
Standards mailing list
Info: https://mail.jabber.org/mailman/listinfo/standards
Unsubscribe: [email protected]
_______________________________________________
