From 454025bd21816c6a1c85382c14e1c5bec983dcf9 Mon Sep 17 00:00:00 2001 From: Krisztian Litkey Date: Mon, 26 Aug 2024 17:38:45 +0300 Subject: [PATCH] PROTOCOL.md: update message frame maximum data length. Update maximum data length in a message frame and reserved most significant byte to be a reserved most significant bit. Signed-off-by: Krisztian Litkey --- PROTOCOL.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/PROTOCOL.md b/PROTOCOL.md index 12b43f6bd..e3da76614 100644 --- a/PROTOCOL.md +++ b/PROTOCOL.md @@ -42,9 +42,9 @@ use is defined by the message type. The Data Length field represents the number of bytes in the Data field. The total frame size will always be Data Length + 10 bytes. The maximum data length -is 4MB and any larger size should be rejected. Due to the maximum data size -being less than 16MB, the first frame byte should always be zero. This first -byte should be considered reserved for future use. +is limited to the largest positive 32-bit signed integer. Therefore the most +signficant bit should always be zero. This bit should be considered reserved +for future use. The Stream ID must be odd for client initiated streams and even for server initiated streams. Server initiated streams are not currently supported.