Issue link: https://read.uberflip.com/i/1467095
LoRaWAN ® IPv6 Adaptation Layer Specification TS010-1.0.0 ©2022 LoRa Alliance ® Page 12 of 15 The authors reserve the right to change specifications without notice. APPENDIX: SCHC REFRESHER 263 This section is not normative, but rather summarizes information from [RFC8724] and 264 [RFC9011] deemed relevant for implementation over LoRaWAN and is provided for the 265 reader's convenience. In case of ambiguity or inconsistency, the information in the RFCs 266 prevail. 267 Table 1 presents the LoRaWAN parameters that are used for the SCHC operation: 268 Parameter Description Usage in SCHC DevEUI Device Extended Unique Identifier; used to identify the end-device. - Used in computing the IPv6 IID. - Used by the SCHC gateway to retrieve the rule set in use for that device. AppSKey Encrypts the LoRaWAN frame payload. - Used in computing the IPv6 IID. FPort Port field; used to specify the application. - Used to carry the RuleID. Table 1: LoRaWAN parameters and fields used in SCHC 269 Table 2 provides a description of general SCHC parameters: 270 Parameter Usage in SCHC Notes on Operation with LoRaWAN RuleID Rule identifier; identifies the compression or fragmentation rule that yielded the SCHC message. - A RuleID that identifies a fragmentation/ reassembly rule always appears in the FPort field of the LoRaWAN frame. - A RuleID that identifies a compression rule appears in the FPort field if no fragmentation/reassembly is applied. Otherwise, the compression RuleID is carried in the first fragment's payload. - Because they appear in the FPort field, RuleIDs used with LoRaWAN are 8 bits wide and are in the range of [1…223], as allowed by [TS001]. IID IPv6 Interface Identifier. - The SCHC implementation needs to have access to the AppSKey in order to generate the IID as mandated by [RFC9011]. This ensures that there is no observable correlation with the hardware identifier (DevEUI). Table 2: General SCHC parameters 271 272