<p>If the sender determines that the recipient's client supports the Chat Markers protocol then it MAY send a Chat Marker or markable message to that full JID.</p>
<p>To prevent looping, an entity MUST NOT send a Chat Maker to mark up to a Chat Marker.</p>
<p>To prevent looping, an entity MUST NOT send a Chat Marker to mark up to a Chat Marker.</p>
</section2>
</section1>
@ -211,7 +211,7 @@
@@ -211,7 +211,7 @@
<p>Clients SHOULD use &xep0136; or &xep0313; to support offline updating of Chat Markers. Chat Markers SHOULD be archived, so they can be fetched and set regardless of whether the other users in a chat are online.</p>
<p>Messages MUST have an 'id' to use Chat Markers.</p>
<p>Messages MUST include the 'markable' element to use Chat Markers.</p>
<p>Chat Markers MUST only move forward. If a Chat Maker is received for an earlier message than the current Chat Marker, it MUST be ignored by the client.
<p>Chat Markers MUST only move forward. If a Chat Marker is received for an earlier message than the current Chat Marker, it MUST be ignored by the client.
</p>
<p>Chat Markers for unknown messages MUST be ignored by the client. A client MAY store the Chat Marker incase the associated message is retrieved later.