Issue link: https://read.uberflip.com/i/1527093
LoRaWAN ® Relay Specification TS011-1.0.1 ©2024 LoRa Alliance ® Page 7 of 62 The authors reserve the right to change specifications without notice. 1 Conventions 248 249 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", 250 "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be 251 interpreted as described in IETF Best Current Practice 14 (BCP14 [RFC2119] [RFC8174]) 252 when, and only when, they appear in all capitals, as shown here. 253 254 The tables in this document are normative. The figures and notes in this document are 255 informative. 256 257 Referenced document titles are written as LoRaWAN Link Layer Specification and referenced 258 section titles within this document are written as "Appendix 2: Security Considerations". 259 260 Commands are written NewChannelReq, bits and bit fields are written CADPeriodicity, 261 constants are written RECEIVE_DELAY1, variables are written N. 262 In this document: 263 • The octet order for all multi-octet fields SHALL be little endian. 264 • EUI are 8-octet fields and SHALL be transmitted as little endian. 265 • An AES key is an array of bytes and has no endianness. As such, it's transported over 266 the air in the same order as it's defined, i.e. index zero value is sent first. 267 • By default, RFU bits are Reserved for Future Use and SHALL be set to 0 by the 268 transmitter of the packet and SHALL be silently ignored by the receiver. 269
