Issue link: https://read.uberflip.com/i/1464683
LoRaWAN ® Fragmented Data Block Transport Specification TS004-2.0.0 ©2022 LoRa Alliance ® Page 5 of 32 The authors reserve the right to change specifications without notice. 1 Conventions 131 132 The keywords "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", 133 "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and "OPTIONAL" 134 in this document are to be interpreted as described in IETF Best Current Practice 14 (BCP14 135 [RFC2119] [RFC8174]) when, and only when, they appear in all capitals, as shown here. 136 137 The tables in this document are normative. The figures and notes in this document are 138 informative. 139 140 Document titles are written as LoRaWAN Link Layer Specification and sections within a 141 document are written as "FPort Assignments". 142 143 Commands are written PackageVersionReq, bits and bit fields are written 144 PackageIdentifier, constants are written RECEIVE_DELAY1, variables are written N. 145 In this document, 146 • The octet order for all multi-octet fields SHALL be little endian. 147 • EUI are 8-octet fields and SHALL be transmitted as little endian. 148 • By default, RFU bits are Reserved for Future Use and SHALL be set to 0 by the 149 transmitter of the packet and SHALL be silently ignored by the receiver. 150