Let us suppose that a Romeo receives a message from Juliet:
Forwarded stanzas SHOULD include all relevant child elements of the original stanza by default. However, an implementation MAY omit elements it deems irrelevant and safe to discard. An example would be omitting &xep0085; elements from <message> stanzas which typically do not make sense outside the context of a conversation session. However it should be noted that removing such elements can invalidate any digital signature on a stanza. If preserving a signature is important - in the context this extension is used then child elements SHOULD NOT be removed.
The forwarding entity SHOULD add a <delay/> child to the <forwarded/> element to indicate to the recipient the date/time that the forwarding entity received the original - stanza. The format of this element is described in &xep0203;.
The namespace of the forwarded stanza MUST be preserved (this is typically 'jabber:client'). If no 'xmlns' is set for the stanza then as per XML namespacing rules it would inherit the - 'urn:xmpp:forward:0' namespace, which is wrong.
When this extension is employed simply for a user to forward a given message to a contact, the outer <message/> SHOULD contain a body (even if empty) and a receiving client should pay particular attention to ensure it renders both the sender's text and the forwarded message - unambiguously.
When a forwarded stanza forms part of an encapsulating protocol, the <forwarded/> element SHOULD be a child of a tag of that protocol, and SHOULD NOT be included as a direct child of the - transmitted stanza.
Forwarding stanzas can reveal information about the original sender, including possible presence leaks as well as the stanza payloads themselves. Any extensions using this format must therefore consider the implications of this.
-Forwarding can either be used as-is, or in the context of another specification, with different security considerations:
+Forwarding can either be used as-is, or in the context of another specification, with different security considerations as described below.
Receipt of a forwarded stanza from a third-party does not guarantee that the original stanza was actually received, or that the content has not been modified, by the forwarder. Integrity of the original stanza can only be determined through digital signing mechanisms such as described in &xep0285; and &xep0290;.
Considering the above an end-user client should take special care in its rendering of forwarded stanzas, such as forwarded messages, to ensure that the user cannot mistake it for a message received directly from the original sender.
@@ -146,13 +153,6 @@ xmlns='urn:xmpp:forward:0' elementFormDefault='qualified'> -