idnits 2.17.1 draft-petrov-lpwan-ipv6-schc-over-lorawan-00.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- ** The document seems to lack an IANA Considerations section. (See Section 2.2 of https://www.ietf.org/id-info/checklist for how to handle the case when there are no actions for IANA.) Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year -- The document date (October 30, 2017) is 2371 days in the past. Is this intentional? Checking references for intended status: Informational ---------------------------------------------------------------------------- == Unused Reference: 'RFC4944' is defined on line 235, but no explicit reference was found in the text == Unused Reference: 'RFC7136' is defined on line 245, but no explicit reference was found in the text == Outdated reference: A later version (-24) exists of draft-ietf-lpwan-ipv6-static-context-hc-07 == Outdated reference: A later version (-10) exists of draft-ietf-lpwan-overview-07 Summary: 1 error (**), 0 flaws (~~), 5 warnings (==), 1 comment (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 lpwan Working Group I. Petrov 3 Internet-Draft Acklio 4 Intended status: Informational A. Yegin 5 Expires: May 3, 2018 Actility 6 October 30, 2017 8 Static Context Header Compression (SCHC) over LoRaWAN 9 draft-petrov-lpwan-ipv6-schc-over-lorawan-00 11 Abstract 13 The Static Context Header Compression (SCHC) specification describes 14 generic header compression and fragmentation techniques for LPWAN 15 (Low Power Wide Area Networks) technologies. SCHC is a generic 16 mechanism designed for great flexibility, so that it can be adapted 17 for any of the LPWAN technologies. 19 This document provides the adaptation of SCHC for use in LoRaWAN 20 networks, and provides elements such as efficient parameterization 21 and modes of operation. 23 Status of This Memo 25 This Internet-Draft is submitted in full conformance with the 26 provisions of BCP 78 and BCP 79. 28 Internet-Drafts are working documents of the Internet Engineering 29 Task Force (IETF). Note that other groups may also distribute 30 working documents as Internet-Drafts. The list of current Internet- 31 Drafts is at https://datatracker.ietf.org/drafts/current/. 33 Internet-Drafts are draft documents valid for a maximum of six months 34 and may be updated, replaced, or obsoleted by other documents at any 35 time. It is inappropriate to use Internet-Drafts as reference 36 material or to cite them other than as "work in progress." 38 This Internet-Draft will expire on May 3, 2018. 40 Copyright Notice 42 Copyright (c) 2017 IETF Trust and the persons identified as the 43 document authors. All rights reserved. 45 This document is subject to BCP 78 and the IETF Trust's Legal 46 Provisions Relating to IETF Documents 47 (https://trustee.ietf.org/license-info) in effect on the date of 48 publication of this document. Please review these documents 49 carefully, as they describe your rights and restrictions with respect 50 to this document. Code Components extracted from this document must 51 include Simplified BSD License text as described in Section 4.e of 52 the Trust Legal Provisions and are provided without warranty as 53 described in the Simplified BSD License. 55 Table of Contents 57 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 58 2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 3 59 3. Static Context Header Compression Overview . . . . . . . . . 3 60 4. LoRaWAN Overview . . . . . . . . . . . . . . . . . . . . . . 4 61 4.1. Device classes (A, B, C) and interactions . . . . . . . . 5 62 4.2. Device addressing . . . . . . . . . . . . . . . . . . . . 5 63 4.3. General Message Types . . . . . . . . . . . . . . . . . . 5 64 4.4. LoRaWAN MAC Frames . . . . . . . . . . . . . . . . . . . 5 65 5. SCHC over LoRaWAN . . . . . . . . . . . . . . . . . . . . . . 5 66 5.1. Rule ID management . . . . . . . . . . . . . . . . . . . 5 67 5.2. IID computation . . . . . . . . . . . . . . . . . . . . . 5 68 5.3. Fragmentation . . . . . . . . . . . . . . . . . . . . . . 5 69 5.3.1. Reliability options . . . . . . . . . . . . . . . . . 5 70 5.3.2. Supporting multiple window sizes . . . . . . . . . . 5 71 5.3.3. Downlink fragment transmission . . . . . . . . . . . 5 72 5.3.4. SCHC behavior for devices in class A, B and C . . . . 5 73 6. Security considerations . . . . . . . . . . . . . . . . . . . 6 74 7. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 6 75 8. References . . . . . . . . . . . . . . . . . . . . . . . . . 6 76 8.1. Normative References . . . . . . . . . . . . . . . . . . 6 77 8.2. Informative References . . . . . . . . . . . . . . . . . 6 78 Appendix A. Examples . . . . . . . . . . . . . . . . . . . . . . 6 79 Appendix B. Note . . . . . . . . . . . . . . . . . . . . . . . . 6 80 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 6 82 1. Introduction 84 The Static Context Header Compression (SCHC) specification 85 [I-D.ietf-lpwan-ipv6-static-context-hc] describes generic header 86 compression and fragmentation techniques that can be used on all 87 LPWAN (Low Power Wide Area Networks) technologies defined in 88 [I-D.ietf-lpwan-overview]. Even though those technologies share a 89 great number of common features like start-oriented topologies, 90 network architecture, devices with mostly quite predictable 91 communications, etc; they do have some slight differences in respect 92 of payload sizes, reactiveness, etc. 94 SCHC gives a generic framework that enables those devices to 95 communicate with other Internet networks. However, for efficient 96 performance, some parameters and modes of operation need to be set 97 appropriately for each of the LPWAN technologies. 99 This document describes the efficient parameters and modes of 100 operation when SCHC is used over LoRaWAN networks. 102 2. Terminology 104 This section defines the terminology and acronyms used in this 105 document. For all other definitions, please look up the SCHC 106 specification [I-D.ietf-lpwan-ipv6-static-context-hc]. 108 o DevEUI: an IEEE EUI-64 identifier used to identify the device 109 during the procedure while joining the network (Join Procedure) 111 o DevAddr: a 32-bit non-unique identifier assigned to a device 112 statically or dynamically after a Join Procedure (depending on the 113 activation mode) 115 o TBD: all significant LoRaWAN-related terms. 117 3. Static Context Header Compression Overview 119 This section contains a short overview of Static Context Header 120 Compression (SCHC). For a detailed description, refer to the full 121 specification [I-D.ietf-lpwan-ipv6-static-context-hc]. 123 Static Context Header Compression (SCHC) avoids context 124 synchronization, which is the most bandwidth-consuming operation in 125 other header compression mechanisms such as RoHC [RFC5795]. Based on 126 the fact that the nature of data flows is highly predictable in LPWAN 127 networks, some static contexts may be stored on the Device (Dev). 128 The contexts must be stored in both ends, and it can either be 129 learned by a provisioning protocol or by out of band means or it can 130 be pre-provisioned, etc. The way the context is learned on both 131 sides is out of the scope of this document. 133 Dev App 134 +--------------+ +--------------+ 135 |APP1 APP2 APP3| |APP1 APP2 APP3| 136 | | | | 137 | UDP | | UDP | 138 | IPv6 | | IPv6 | 139 | | | | 140 | SCHC C/D | | | 141 | (context) | | | 142 +-------+------+ +-------+------+ 143 | +--+ +----+ +---------+ . 144 +~~ |RG| === |NGW | === |SCHC C/D |... Internet .. 145 +--+ +----+ |(context)| 146 +---------+ 148 Figure 1: Architecture 150 Figure 1 represents the architecture for compression/decompression, 151 it is based on [I-D.ietf-lpwan-overview] terminology. The Device is 152 sending applications flows using IPv6 or IPv6/UDP protocols. These 153 flows are compressed by an Static Context Header Compression 154 Compressor/Decompressor (SCHC C/D) to reduce headers size. Resulting 155 information is sent on a layer two (L2) frame to a LPWAN Radio 156 Network (RG) which forwards the frame to a Network Gateway (NGW). 157 The NGW sends the data to a SCHC C/D for decompression which shares 158 the same rules with the Dev. The SCHC C/D can be located on the 159 Network Gateway (NGW) or in another place as long as a tunnel is 160 established between the NGW and the SCHC C/D. The SCHC C/D in both 161 sides must share the same set of Rules. After decompression, the 162 packet can be sent on the Internet to one or several LPWAN 163 Application Servers (App). 165 The SCHC C/D process is bidirectional, so the same principles can be 166 applied in the other direction. 168 In a LoRaWAN network, the RG is called a Gateway, the NGW is Network 169 Server, and the SCHC C/D can be embedded in different places, for 170 example in the Network Server and/or the Application Server. 172 Next steps for this section: detailed overview of the LoRaWAN 173 architecture and its mapping to the SCHC architecture. 175 4. LoRaWAN Overview 176 4.1. Device classes (A, B, C) and interactions 178 TBD 180 4.2. Device addressing 182 TBD 184 4.3. General Message Types 186 TBD 188 4.4. LoRaWAN MAC Frames 190 TBD 192 5. SCHC over LoRaWAN 194 5.1. Rule ID management 196 Rule ID can be stored and transported in the FPort field of the 197 LoRaWAN MAC frame. TBD 199 5.2. IID computation 201 TBD 203 5.3. Fragmentation 205 TBD 207 5.3.1. Reliability options 209 TBD 211 5.3.2. Supporting multiple window sizes 213 TBD 215 5.3.3. Downlink fragment transmission 217 TBD 219 5.3.4. SCHC behavior for devices in class A, B and C 221 TBD 223 6. Security considerations 225 TBD 227 7. Acknowledgements 229 TBD 231 8. References 233 8.1. Normative References 235 [RFC4944] Montenegro, G., Kushalnagar, N., Hui, J., and D. Culler, 236 "Transmission of IPv6 Packets over IEEE 802.15.4 237 Networks", RFC 4944, DOI 10.17487/RFC4944, September 2007, 238 . 240 [RFC5795] Sandlund, K., Pelletier, G., and L-E. Jonsson, "The RObust 241 Header Compression (ROHC) Framework", RFC 5795, 242 DOI 10.17487/RFC5795, March 2010, 243 . 245 [RFC7136] Carpenter, B. and S. Jiang, "Significance of IPv6 246 Interface Identifiers", RFC 7136, DOI 10.17487/RFC7136, 247 February 2014, . 249 8.2. Informative References 251 [I-D.ietf-lpwan-ipv6-static-context-hc] 252 Minaburo, A., Toutain, L., and C. Gomez, "LPWAN Static 253 Context Header Compression (SCHC) and fragmentation for 254 IPv6 and UDP", draft-ietf-lpwan-ipv6-static-context-hc-07 255 (work in progress), October 2017. 257 [I-D.ietf-lpwan-overview] 258 Farrell, S., "LPWAN Overview", draft-ietf-lpwan- 259 overview-07 (work in progress), October 2017. 261 Appendix A. Examples 263 Appendix B. Note 265 Authors' Addresses 266 Ivaylo Petrov 267 Acklio 268 2bis rue de la Chataigneraie 269 35510 Cesson-Sevigne Cedex 270 France 272 Email: ivaylo@ackl.io 274 Alper Yegin 275 Actility 276 . 277 Paris, Paris 278 France 280 Email: alper.yegin@actility.com