* 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.
Squashed commit of the following:
commit e8b5dc6385c523661bd5f335ccb442b8904af1f8
Author: Kevin Smith <git@kismith.co.uk>
Date: Tue Jan 17 09:43:32 2017 +0000
Tidy up some text ready for submission
commit 055b02896f34920cb99879ebb366f757c1af20fb
Author: Kevin Smith <git@kismith.co.uk>
Date: Thu Dec 15 12:21:17 2016 +0000
Add strawman protocol
commit 5b2910208180e9a92a3a757ece6e129d2ffe360f
Author: Kevin Smith <git@kismith.co.uk>
Date: Thu Dec 15 12:03:59 2016 +0000
Advertise support
commit 840808df0f3baf59f9c30570c427c2bca69841b2
Author: Kevin Smith <git@kismith.co.uk>
Date: Mon Dec 12 11:07:36 2016 +0000
Add basic requirements
commit 3ff672b20718c298424f681ca057506978c190a3
Author: Kevin Smith <git@kismith.co.uk>
Date: Fri Dec 9 15:18:13 2016 +0000
Add introduction for bind 2.0
* migration to olm
* moved the gcm auth tag into the OlmMessage
* various clarifications
* prekey messages are now marked with special attribute
Fixes#251
- Made the 'name' attribute optional for existing mechanisms.
- Added a remark about the possibility to hide encrypted messages
following user input.
- Made explicit that this protocol affects any encryption mechanism,
present or future, not only those listed here.
- Display the namespace of the encryption mechanism in the default
messages.
- Remove the second example message, which didn’t add any useful
information.
