From: Kevin Day Date: Sun, 16 Jul 2023 22:48:54 +0000 (-0500) Subject: Update: FSS-000f specification, adding reasoning and improve the wording. X-Git-Url: https://git.kevux.org/?a=commitdiff_plain;h=df27a783fe8aac80a7844a14856d941cf17a6214;p=fll Update: FSS-000f specification, adding reasoning and improve the wording. Add a simple paragraph about the reason why the size bit includes the Control Block and the Size Block in its size representation. Fix a mistake in the words where the standard has "...of that that...". The back to back use of "that" is confusing and probably a typo. --- diff --git a/specifications/fss-000f.txt b/specifications/fss-000f.txt index ff375a6..685e6a4 100644 --- a/specifications/fss-000f.txt +++ b/specifications/fss-000f.txt @@ -1,7 +1,7 @@ # fss-0002 iki-0000 # # license open-standard-license-1.0 -# version 2023/07/14 +# version 2023/07/16 # # This file (assumed to be named fss-000f.txt) can be more easily read using the following iki_read commands: # iki_read fss-000f.txt +Q -w -WWWW character "'" "'" code '"' '"' italic '"' '"' bold '"' '"' @@ -57,13 +57,15 @@ Featureless Settings Specification: 000f - Simple Packet: The size represents number of bytes in the file. The bold:"Control Block" is 1 byte long and the bold:"Size Block" is 4 bytes long, therefore the maximum available size of the entire bold:"Simple Packet" structure is code:"(2^32)-6". + The reason behind why the size includes both the bold:"Control Block" and the bold:"Size Block" in addition to the bold:"Payload Block" is to avoid the need to perform any calculations for handling the size of the entire packet. The idea here is to optimize the packet for the network hardware transferring the packet. The network device should not need to read the contents of the packet in order to transfer the packet and therefore it only needs the number of the entire packet. Anything that wants to analyze this packet will have to incure the cost of calculating the bold:"Payload Block" size by performing the appropriate subtraction from the size represented in the bold:"Size Block". + Payload Block Structure\: code:" [ Payload Block ] [ size: (2^32)-6 ] " - The bold:"Payload Block" is not defined by this standard of that that it exists and should be in code:"FSS-000e (Payload)" format. + The bold:"Payload Block" is not defined by this standard other than that it exists and should be in code:"FSS-000e (Payload)" format. The code:"FSS-000e (Payload)" may be represented in either italic:"string" format or italic:"binary" format. The code:"FSS-000e (Payload)" may contain multiple italic:"header"(s) but may only contain a single italic:"payload". With this in mind, it is recommended that only a single italic:"header" be supported in the bold:"Payload Block".