From baff857975b63bec63c23d6ed3f903f78e67f172 Mon Sep 17 00:00:00 2001 From: Sam Whited Date: Sat, 21 Nov 2020 14:41:53 -0500 Subject: [PATCH] XEP-0047: fix incorrect max sequence number Previously the text said that the max sequence number was 65535 (max unsigned 16 bit integer), but also said this was (1<<15)-1, which is actually max signed 16 bit integer or 32767. --- xep-0047.xml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/xep-0047.xml b/xep-0047.xml index f094da03..2e12d38d 100644 --- a/xep-0047.xml +++ b/xep-0047.xml @@ -194,7 +194,7 @@ ]]>

Each chunk of data is included as the XML character data of the <data/> element after being encoded as Base64 as specified in Section 4 of &rfc4648;. Each block MUST be a valid base64 block with padding at the end if needed.

-

The <data/> element MUST possess a 'seq' attribute; this is a 16-bit unsigned integer that acts as a counter for data chunks sent in a particular direction within this session. The 'seq' value starts at 0 (zero) for each sender and MUST be incremented for each packet sent by that entity. Thus, the second chunk sent has a 'seq' value of 1, the third chunk has a 'seq' value of 2, and so on. The counter loops at maximum, so that after value 65535 (215 - 1) the 'seq' MUST start again at 0.

+

The <data/> element MUST possess a 'seq' attribute; this is a 16-bit unsigned integer that acts as a counter for data chunks sent in a particular direction within this session. The 'seq' value starts at 0 (zero) for each sender and MUST be incremented for each packet sent by that entity. Thus, the second chunk sent has a 'seq' value of 1, the third chunk has a 'seq' value of 2, and so on. The counter loops at maximum, so that after value 65535 (216 - 1) the 'seq' MUST start again at 0.

The <data/> element MUST also possess a 'sid' attribute that ties the data chunk to this particular IBB session.

In the case of IQ stanzas, if the packet can be processed then the recipient MUST reply with an IQ stanza of type "result".