idnits 2.17.1 draft-authors-lpwan-schc-802154-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 : ---------------------------------------------------------------------------- No issues found here. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year -- The document date (July 16, 2018) is 2082 days in the past. Is this intentional? Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) == Outdated reference: A later version (-24) exists of draft-ietf-lpwan-ipv6-static-context-hc-16 Summary: 0 errors (**), 0 flaws (~~), 2 warnings (==), 1 comment (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Internet Area J. Robert 3 Internet-Draft FAU Erlangen-Nuernberg 4 Intended status: Standards Track C. Perkins 5 Expires: January 17, 2019 Futurewei 6 July 16, 2018 8 SCHC for 802.15.4 lpwan applications 9 draft-authors-lpwan-schc-802154-00 11 Abstract 13 This document provides guidelines for creating Rules for Static 14 Context Header Compression for IEEE 802.15.4. Since 802.15.4 15 provides layer-2 acknowledgements, some complexities that were 16 designed for more general systems can be avoided. 18 Status of This Memo 20 This Internet-Draft is submitted in full conformance with the 21 provisions of BCP 78 and BCP 79. 23 Internet-Drafts are working documents of the Internet Engineering 24 Task Force (IETF). Note that other groups may also distribute 25 working documents as Internet-Drafts. The list of current Internet- 26 Drafts is at https://datatracker.ietf.org/drafts/current/. 28 Internet-Drafts are draft documents valid for a maximum of six months 29 and may be updated, replaced, or obsoleted by other documents at any 30 time. It is inappropriate to use Internet-Drafts as reference 31 material or to cite them other than as "work in progress." 33 This Internet-Draft will expire on January 17, 2019. 35 Copyright Notice 37 Copyright (c) 2018 IETF Trust and the persons identified as the 38 document authors. All rights reserved. 40 This document is subject to BCP 78 and the IETF Trust's Legal 41 Provisions Relating to IETF Documents 42 (https://trustee.ietf.org/license-info) in effect on the date of 43 publication of this document. Please review these documents 44 carefully, as they describe your rights and restrictions with respect 45 to this document. Code Components extracted from this document must 46 include Simplified BSD License text as described in Section 4.e of 47 the Trust Legal Provisions and are provided without warranty as 48 described in the Simplified BSD License. 50 Table of Contents 52 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 53 2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 3 54 3. SCHC parameters . . . . . . . . . . . . . . . . . . . . . . . 4 55 3.1. Size of the Rule ID . . . . . . . . . . . . . . . . . . . 4 56 3.2. Use of Padding . . . . . . . . . . . . . . . . . . . . . 4 57 3.3. Fragmentation Delivery Reliability Option . . . . . . . . 4 58 3.4. MAX_ACK_REQUEST . . . . . . . . . . . . . . . . . . . . . 4 59 3.5. FCN . . . . . . . . . . . . . . . . . . . . . . . . . . . 4 60 3.6. DTag . . . . . . . . . . . . . . . . . . . . . . . . . . 4 61 3.7. L2 CRC . . . . . . . . . . . . . . . . . . . . . . . . . 5 62 3.8. Fragmentation ACK Parameters (not used) . . . . . . . . . 5 63 4. Security Considerations . . . . . . . . . . . . . . . . . . . 5 64 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 5 65 6. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 5 66 7. References . . . . . . . . . . . . . . . . . . . . . . . . . 5 67 7.1. Normative References . . . . . . . . . . . . . . . . . . 5 68 7.2. Informative References . . . . . . . . . . . . . . . . . 6 69 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 6 71 1. Introduction 73 Static Context Header Compression (SCHC) 74 [I-D.ietf-lpwan-ipv6-static-context-hc] is a solution for header 75 compression, highly specialized for very predictable IPv6 packets to 76 and from an lpwan node with significant resource constraints 77 (especially power). This document provides guidelines for creating 78 Rules for Static Context Header Compression (SCHC) for IEEE 802.15.4 79 [dot4]. Since 802.15.4 provides layer-2 acknowledgements, some 80 complexities that were designed for more general systems can be 81 avoided. 83 The Low-Power, Wide-Area IEEE 802.15.4w task group (LPWA) has been 84 chartered to specify modifications to 802.15.4 MAC and PHY parameters 85 that would be needed to make the technology more suitable for lpwan 86 applications [lpwa_par], [lpwa_csd]. Although 801.15.4g [dot4g] and 87 802.15.4k [dot4k] were previously designed for such systems, recent 88 experiments and further experience with new use cases have indicated 89 the need for additional specification and wider applicability. 91 LPWA has listed different use-cases that may be relevant for LPWAN in 92 a study group document [lpwa_use_cases]. The LPWAN use-cases 93 discussed in that document are characterized as follows: 95 o Focusing on uplink data 96 o Typical Payload data length less than 16 bytes 97 o No strict latency requirements 98 The LPWA also determined that it would be useful to produce a 99 document for the IETF lp-wan Working Group to suggest parameters for 100 the use cases. The discussion so far in LPWA has resulted in the 101 document [lpwa_schc]. 103 | 104 +-----+ 105 | | Gateway (default) router 106 | | 107 +-----+ 108 | 109 | 110 +-----+ 111 | | LPWA access point 112 | | 113 +-----+ 114 o 115 o o o o 116 o o o o o 117 o o o o 118 o o o 120 LLN 122 Figure 1: Representative Architecture for 802.15.4w Use Cases 124 A typical 802.15.4w use case is illustrated in Figure 1. The header 125 compression context is statically configured for the transmission and 126 reception of packets between the LPWA access point and the individual 127 low-power devices (indicated as 'o'). Most of the rules follow the 128 recommended practice in [I-D.ietf-lpwan-ipv6-static-context-hc] for 129 compressing the IPv6 addresses and UDP ports; the same rulesets can 130 be used for the possibly thousands of low-power devices, only 131 changing the IPv6 address for the particular device relevant to the 132 context. 134 2. Terminology 136 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 137 "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and 138 "OPTIONAL" in this document are to be interpreted as described in 139 [RFC2119]. 141 This document uses the following definitions: 143 LPWA 144 Low-Power Wide Area 145 PAN 146 Personal Area Network 147 802.15.4w 148 Low-Power Wide Area (LPWA) task group within IEEE 802.15 150 3. SCHC parameters 152 In this section we provide details about parameter selection for a 153 static compression context to be used over 802.15.4, according to the 154 guidelines in [minaburo_email]. The method by which the context is 155 agreed upon by sender and receiver is left unspecified. For the 156 purposes of this document, the rule-ID, rule parameters, and other 157 uncompressed information is to be considered as a normal L2 payload 158 that will be decompressed before delivery to L3. 160 3.1. Size of the Rule ID 162 Size of the Rule ID should be 3, to allow for up to 8 rules. 164 3.2. Use of Padding 166 Pad to a multiple of 8 bits in the L2 payload. 168 3.3. Fragmentation Delivery Reliability Option 170 802.15.4 link acknowledgement should be used, since the static 171 context as defined should be decompressed after delivery over a 172 single link. 174 3.4. MAX_ACK_REQUEST 176 MAX_ACK_REQUEST SHOULD be set to 3, following usual practice in 177 802.15.4. 179 3.5. FCN 181 FCN SHOULD be set to 0, since unfragmented traffic is expected for 182 most use cases under consideration in 802.15.4w. 184 3.6. DTag 186 Similarly, DTag SHOULD be set to 0, since unfragmented traffic is 187 expected for most use cases under consideration in 802.15.4w. 189 3.7. L2 CRC 191 Either CRC-16 or CRC-32 as defined in 802.15.4 could be used. 193 3.8. Fragmentation ACK Parameters (not used) 195 Since acknowledgments SHOULD be handled at Layer 2, no specification 196 is made here for the following: 198 o The timer duration for Fragmentation ACK Always 199 o When to abort in ACK Always 200 o MAX_ATTEMPTS counter size 201 o The timer size between windows in ACK On Error. 202 o The inactivity timer. 204 4. Security Considerations 206 This document does not introduce any security mechanisms, and does 207 not have affect existing security mechanisms or vulnerabilities 208 already present in the base SCHC document. 210 5. IANA Considerations 212 This document does not specify any IANA actions. 214 6. Acknowledgements 216 This document has benefitted from discussions with the following 217 people, in alphabetical order: Pat Kinney 219 7. References 221 7.1. Normative References 223 [I-D.ietf-lpwan-ipv6-static-context-hc] 224 Minaburo, A., Toutain, L., Gomez, C., and D. Barthel, 225 "LPWAN Static Context Header Compression (SCHC) and 226 fragmentation for IPv6 and UDP", draft-ietf-lpwan-ipv6- 227 static-context-hc-16 (work in progress), June 2018. 229 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 230 Requirement Levels", BCP 14, RFC 2119, 231 DOI 10.17487/RFC2119, March 1997, 232 . 234 7.2. Informative References 236 [dot4] P802.15, "Part 15: Wireless LAN Medium Access Control 237 (MAC) and Physical Layer (PHY) Specifications", March 238 2012. 240 [dot4g] P802.15, "Part 15: Wireless LAN Medium Access Control 241 (MAC) and Physical Layer (PHY) Specifications", March 242 2012. 244 [dot4k] P802.15, "Part 15: Wireless LAN Medium Access Control 245 (MAC) and Physical Layer (PHY) Specifications", March 246 2012. 248 [lpwa_csd] 249 P802.15, "Part 15: Wireless LAN Medium Access Control 250 (MAC) and Physical Layer (PHY) Specifications", March 251 2012. 253 [lpwa_par] 254 P802.15, "Part 15: Wireless LAN Medium Access Control 255 (MAC) and Physical Layer (PHY) Specifications", March 256 2012. 258 [lpwa_schc] 259 Joerg Robert, "Discussion on Suitable Parameters for 260 SCHC", May 2018. 262 [lpwa_use_cases] 263 Joerg Robert, "LPWA Use-Cases", Mar 2017. 265 [minaburo_email] 266 Ana Minaburo, "SCHC technology specific parameters", Feb 267 2018. 269 Authors' Addresses 271 Joerg Robert 272 Friedrich-Alexander Universitaet Erlangen-Nuernberg 273 Am Wolfsmantel 33 274 Erlangen 91058 275 Germany 277 Phone: +49-9131-85-25373 278 Email: joerg.robert@fau.de 279 Charles E. Perkins 280 Futurewei Inc. 281 2330 Central Expressway 282 Santa Clara, CA 95050 283 USA 285 Phone: +1-408-330-4586 286 Email: charliep@computer.org