On 22/02/2023 20.00, Marvin W wrote:
I believe we only disagree if a reference to a stanza should also
contain the 'by' attribute. [And probably about our vision if groupchat
messages should be stored in as many archives as possible or just in the
groupchat service's archive. But we should simply allow for both
approaches, it is from a protocol design perspective not an XOR situation.]
- When receiving a message reference: Ignore any "wrong" by-attribute
in message references and just take the value that I implicitly know
must've been used when referencing (following Postel's law).
Following Postel's law in this sense does more harm than good, as you
would not be able to detect implementations that operate under different
assumptions. Instead, we should allow the recipient of a message to
verify that the sender of the message operated under the same
assumptions as the recipient. This is only possible if the reference
contains the 'by' attribute.
This would turn the by-attribute in a message reference into entirely
useless boilerplate that is generated out of thin air by the sender and
ignored by the recipient.
It is not useless boilerplate and certainly not generated out of thin
air. If the recipient does use this information is up to the
implementation, but I would encourage that the recipient verifies it.
- Flow
_______________________________________________
Standards mailing list
Info: https://mail.jabber.org/mailman/listinfo/standards
Unsubscribe: [email protected]
_______________________________________________
