This commit changes some of the wording to clarify that the by attribute
for messages tagged by the server should be either the account jid or
the room jid (as opposed to the server jid for example)
To further clarify this the examples (including the disco example) were
all changed to have the same jid/by-attribute. (A room in that example)
The business rules had some wording that an entity would overwrite the
ID in existing 'faked' stanza-ids instead of removing the faked and
re-adding a non-faked one. However that doesn't work for faked messages
that are not archived (don't have a stanza-id).
This commit also makes the XEP explicitly about message stanzas
* Some editing
* Explicitly mention the possible need for rate-limiting of caps
processing in Security Considerations
* Reference UTF-8 and Base64 RFCs
* Reference U+002E properly
* Clarify error condition for Hash Function Input algorithm
* XEP-0369: Minor editing
* Small edit following Georg's edits
* Edits to address Georg's comments
* New Proxy JID format.
* Clarify MAM Archive on Send
* Sort Mechanisms to only share JIDs when users prefer to
* Add examples of Real JID lookup and set version date
* issueing -> issuing
* was -> were (subjunctive mood)
* Add commas around subordinate clause "per XMPP Core"
* Make "for example to increase the privacy" a parenthetical, remove word "the".
* "ordering of children in disco#info... elements does, however, not matter" -> "elements, however, does not matter"
Some XEPs used &rfc3269; as reference which is
Author Guidelines for Reliable Multicast Transport (RMT) Building Blocks
and Protocol Instantiation documents
while they should use RFC 3629 for that.
Simple typo, i.e. transpose of two characters, not
RFC 3269 but
RFC 3629.
