Use 'envelope' and 'content' consistently by renaming elements
+Update namespace to urn:xmpp:sce:1
+Fix misspelling of 'whose'
This proposal widens the scope of the security guarantees given by the used encryption mechanism from just the body of the message to all contents of the &content; element. It is intended to serve as a "one size fits all" solution for extension element encryption in XMPP.
+This proposal widens the scope of the security guarantees given by the used encryption mechanism from just the body of the message to various extension elements. It is intended to serve as a "one size fits all" solution for extension element encryption in XMPP.
In order to achieve its goal, Stanza Content Encryption does the following:
In order to prevent certain attacks, different affix elements MAY be added into the &content; element.
+In order to prevent certain attacks, different affix elements MAY be added as direct child elements of the &envelope; element.
Element | Reason | |
---|---|---|
Elements of &xep0334; | -Message Processing Hints are addressed to the server and MUST therefore be accessible in plaintext. A receiving client MUST ignore any message processing hints encountered inside the encrypted &content; element | +Message Processing Hints are addressed to the server and MUST therefore be accessible in plaintext. A receiving client MUST ignore any message processing hints encountered inside the encrypted &envelope; element |
Stanza-ID elements of &xep0359; | -Sending clients MUST NOT include Stanza-ID elements inside the &content; element, as this would prevent the server from filtering it. - A client MUST ignore Stanza-ID elements encountered inside &content; element | +Sending clients MUST NOT include Stanza-ID elements inside the &envelope; element, as this would prevent the server from filtering it. + A client MUST ignore Stanza-ID elements encountered inside the &envelope; element |
Elements of &xep0033; | @@ -373,13 +381,13 @@