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