Issue link: https://read.uberflip.com/i/1464686
LoRaWAN ® Multi-Package Access Protocol Specification TS007-1.0.0 ©2022 LoRa Alliance ® Page 4 of 15 The authors reserve the right to change specifications without notice. 1 Conventions 102 103 The keywords "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", 104 "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and "OPTIONAL" 105 in this document are to be interpreted as described in IETF Best Current Practice 14 (BCP14 106 [RFC2119] [RFC8174]) when, and only when, they appear in all capitals, as shown here. 107 108 The tables in this document are normative. The figures and notes in this document are 109 informative. 110 111 Document titles are written as LoRaWAN Link Layer Specification and sections within a 112 document are written as "Frequency-Hopping Beacon Transmission". 113 114 Commands are written PackageVersionReq, bits and bit fields are written 115 PackageIdentifier, constants are written RECEIVE_DELAY1, variables are written N. 116 In this document: 117 • The octet order for all multi-octet fields SHALL be little endian. 118 • EUI are 8-octet fields and SHALL be transmitted as little endian. 119 • By default, RFU bits are Reserved for Future Use and SHALL be set to 0 by the 120 transmitter of the packet and SHALL be silently ignored by the receiver. 121 122