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