idnits 2.17.00 (12 Aug 2021) /tmp/idnits16277/draft-lagos-lpwan-icmpv6-static-context-hc-01.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 a Security Considerations section. ** 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 (March 5, 2018) is 1538 days in the past. Is this intentional? Checking references for intended status: Informational ---------------------------------------------------------------------------- == Missing Reference: 'I-D.toutain-lpwan-ipv6-static-context-hc' is mentioned on line 440, but not defined == Missing Reference: 'RFC4443' is mentioned on line 424, but not defined -- Looks like a reference, but probably isn't: '16' on line 173 == Missing Reference: 'RFC4861' is mentioned on line 432, but not defined -- Looks like a reference, but probably isn't: '48' on line 346 -- Looks like a reference, but probably isn't: '64' on line 388 -- Looks like a reference, but probably isn't: '128' on line 390 Summary: 2 errors (**), 0 flaws (~~), 4 warnings (==), 5 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 LPWAN T. Lagos, Ed. 3 Internet-Draft D. Dujovne 4 Intended status: Informational Universidad Diego Portales 5 Expires: September 6, 2018 March 5, 2018 7 LPWAN Static Context Header Compression (SCHC) for ICMPv6 8 draft-lagos-lpwan-icmpv6-static-context-hc-01 10 Abstract 12 This document provides the implementation of the LPWAN static context 13 header compression (SCHC) for the Internet Control Message Protocol 14 version 6 (ICMPv6) on networks with star topology. SCHC is a header 15 compression technique which uses RoHC concepts and the flexibility of 16 6LoWPAN to avoid fields that are known by all network devices and 17 compress the remaining header fields. The ICMPv6 messages considered 18 in this draft are Echo Request, Echo Reply and Neighbor Discovery. 20 Requirements Language 22 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 23 "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and 24 "OPTIONAL" in this document are to be interpreted as described in RFC 25 2119 [RFC2119]. 27 Status of This Memo 29 This Internet-Draft is submitted in full conformance with the 30 provisions of BCP 78 and BCP 79. 32 Internet-Drafts are working documents of the Internet Engineering 33 Task Force (IETF). Note that other groups may also distribute 34 working documents as Internet-Drafts. The list of current Internet- 35 Drafts is at https://datatracker.ietf.org/drafts/current/. 37 Internet-Drafts are draft documents valid for a maximum of six months 38 and may be updated, replaced, or obsoleted by other documents at any 39 time. It is inappropriate to use Internet-Drafts as reference 40 material or to cite them other than as "work in progress." 42 This Internet-Draft will expire on September 6, 2018. 44 Copyright Notice 46 Copyright (c) 2018 IETF Trust and the persons identified as the 47 document authors. All rights reserved. 49 This document is subject to BCP 78 and the IETF Trust's Legal 50 Provisions Relating to IETF Documents 51 (https://trustee.ietf.org/license-info) in effect on the date of 52 publication of this document. Please review these documents 53 carefully, as they describe your rights and restrictions with respect 54 to this document. Code Components extracted from this document must 55 include Simplified BSD License text as described in Section 4.e of 56 the Trust Legal Provisions and are provided without warranty as 57 described in the Simplified BSD License. 59 Table of Contents 61 1. TEMPORARY EDITORIAL NOTES . . . . . . . . . . . . . . . . . . 2 62 2. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3 63 3. LoRa networks using ICMPv6 message . . . . . . . . . . . . . 3 64 4. SCHC compression over Echo Request - Echo Reply . . . . . . . 4 65 5. Router Solicitation SCHC compression . . . . . . . . . . . . 4 66 6. Router Advertisement SCHC compression . . . . . . . . . . . . 5 67 7. SCHC compression over Neighbor Solicitation . . . . . . . . . 7 68 8. SCHC compression over Neighbor Advertisement . . . . . . . . 8 69 9. LoRa Gateway tables . . . . . . . . . . . . . . . . . . . . . 9 70 10. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 9 71 11. References . . . . . . . . . . . . . . . . . . . . . . . . . 9 72 11.1. Normative References . . . . . . . . . . . . . . . . . . 9 73 11.2. Internet Control Message Protocol (ICMPv6) for the 74 Internet Protocol Version 6 (IPv6) Specification . . . . 10 75 11.3. Neighbor Discovery for IP version 6 (IPv6) . . . . . . . 10 76 11.4. LPWAN Static Context Header Compression (SCHC) and 77 fragmentation for IPv6 and UDP . . . . . . . . . . . . . 10 78 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 10 80 1. TEMPORARY EDITORIAL NOTES 82 This document is an Internet Draft, so it is work-in-progress by 83 nature. It contains the following work-in-progress elements: 85 o "TODO" statements are elements which have not yet been written by 86 the authors for some reason (lack of time, ongoing discussions 87 with no clear consensus, etc). The statement does indicate that 88 the text will be written at some time. 89 o "TEMPORARY" appendices are there to capture current ongoing 90 discussions, or the changelog of the document. These 91 appendiceswill be removed in the final text. 92 o "IANA_" identifiers are placeholders for numbers assigned by IANA. 93 These placeholders are to be replaced by the actual values they 94 represent after their assignment by IANA. 96 o The string "REMARK" is put before a remark (questions, suggestion, 97 etc) from an author, editor of contributor. These are on-going 98 discussions at the time to writing, NOT part of the final text. 99 o This section will be removed in the final text. 101 2. Introduction 103 LPWANs are networks where low power consumption, high delay and 104 extremely small packets characterize the traffic. The nodes are 105 tipically connected in a star topology, with a central gateway that 106 connects the network to the Internet. Most IP-based networks require 107 ICMP services to enable network configuration and testing, such as 108 neighbor node detection and round trip time calculation. Because 109 ICMPv6 has redundant information in header fields, SCHC can be 110 deployed efficiently, especially for LPWA devices that are 111 constrained by a small available bandwidth and power limitations. 113 This document describes ICMPv6 message compression using SCHC 114 compression defined on [I-D.toutain-lpwan-ipv6-static-context-hc] to 115 reduce to the minimum the required LPWAN packet size. 117 3. LoRa networks using ICMPv6 message 119 High coverage and low power communication technologies - LoRa 120 networks - allow the construction of data capture systems with the 121 goal of covering a large area with a low bandwidth. This technology 122 is characterized by the transmission of short packets and their 123 direct sequence spread spectrum - DSSS. 125 To maintain communications between the nodes and the outer is 126 necessary the implementation of a neighbor discovery protocol. The 127 internet layer will be composed by the ICMPv6 protocol. 129 The use of SCHC in LoRa messages is fundamental in the ICMPv6 130 comunication. This is because the IPv6 header consist in 40 Bytes 131 and the ICMPv6 header in the worst esenario can be reach lenght over 132 the 36 Bytes. For a LoRa escenario the field checksum of a ICMPv6 133 message will be avoided how is shown in the next chapters. This is 134 because LoRa message posses CRC so it is not necesassary to send it. 136 The fields link layer and target address (only link local) in a 137 ICMPv6 message are going be sended ones as they will be saved in the 138 memory of the LoRa Gateway. For more datails see Section 9 140 4. SCHC compression over Echo Request - Echo Reply 142 Echo Request and Echo Reply are composed by the same fields: 144 o Type: Message type. In case it is Echo Request the value will be 145 0x80. If it is Echo Reply will be 0x81. 146 o Code: Always 0. 147 o Checksum: This field is composed by 2 Bytes where the values are 148 calculated as defined on RFC 4443 [RFC4443]. 149 o Identifier: It is the ID of the package. 150 o Sequence: It is the sequence number of the transmitted packet. 152 For a SCHC compression it is necessary to identify which fields stay 153 static to build the context. 155 The fields Code and checksum can be elided because Code is always 156 zero and Checksum can be calculated after the decompression of the 157 packet. In the case of Type, this field can be represented in the 158 SCHC rule. The Identifier and Sequence fields will be sent after the 159 SCHC rule. 161 +------------+----+-----+----------+------------------+---+----------+ 162 | Field | FP | DI | Match | Comp Decomp | | Sent | 163 | | | | Opera. | Action | | [bits] | 164 +------------+----+-----+----------+------------------+---+----------+ 165 | Type | 1 | Bi | equal | not sent | | | 166 | | | | | | | | 167 | Code | 1 | Bi | equal | not sent | | | 168 | | | | | | | | 169 | Checksum | 1 | Bi | ignore | compute-checksum | | | 170 | | | | | | | | 171 | Identifier | 1 | Bi | equal | sent | | [16] | 172 | | | | | | | | 173 | Sequence | 1 | Bi | ignore | sent | | [16] | 174 +------------+----+-----+----------+------------------+---+----------+ 176 5. Router Solicitation SCHC compression 178 The Router Solicitation packet header is composed by: 180 o Type: Type of message. Value: 0x85. 181 o Code: Always 0. 182 o Checksum: This field is composed by 2 Bytes where the values are 183 caculated as defined on RFC 4443 [RFC4443] 184 o Reserved: These 4 bytes have a 0 value. 185 o Option: This field corresponds to the MAC address. 187 The most significant field is the MAC address of the network host. 188 As mentioned on RFC 4861 [RFC4861], Router Solicitation should have a 189 Link-Local Source Address and a Router Multicast Address which can be 190 integrated after the packet decompression. 192 +-------------+----+-----+---------+------------------+---+----------+ 193 | Field | FP | DI | Match | Comp Decomp | | Sent | 194 | | | | Opera. | Action | | [bits] | 195 +-------------+----+-----+---------+------------------+---+----------+ 196 | Type | 1 | Bi | equal | not sent | | | 197 | | | | | | | | 198 | Code | 1 | Bi | equal | not sent | | | 199 | | | | | | | | 200 | Checksum | 1 | Bi | ignore | compute-checksum | | | 201 | | | | | | | | 202 | Reserved | 1 | Bi | equal | not sent | | | 203 | | | | | | | | 204 | Option - | 1 | Bi | equal | not sent | | | 205 | type | | | | | | | 206 | | | | | | | | 207 | Option - | 1 | Bi | ignore | compute-length | | | 208 | length | | | | | | | 209 | | | | | | | | 210 | Option - | 1 | Bi | ignore | sent | | [48] | 211 | link-layer | | | | | | | 212 +-------------+----+-----+---------+------------------+---+----------+ 214 6. Router Advertisement SCHC compression 216 The Router Advertisement packet header is composed by: 218 o Type: Type of message. Value: 0x86. 219 o Code: Always 0. 220 o Checksum: This field is composed by 2 Bytes where they values are 221 caculated as it is explained on RFC 4443 [RFC4443]. 222 o Current Hop Limit: Because this is a star topology, the value MUST 223 be set to 255. 224 o Autoconfig Flags: Depending on the router configuration, it will 225 advertise if DHCP is allowed or not. 226 o Router Lifetime: This field indicates the time that the Router 227 keeps the condition of default device. 228 o Reachable Time: Indicates to the host how much time a neighbour is 229 considered reachable. 230 o Retransmission Timer: Indicates the delay that the host should 231 have before transmission. 232 o Options: This field contains the MAC Address, MTU and the IPv6 233 Prefix of the network. 235 The SCHC compression for Router Advertisement is designed to send the 236 MAC address of the packet. Like the Echo message, the Type field can 237 be represented in the SCHC rule. 239 The Current Hop Limit, Autoconfig Flags, Lifetime Router, Reachable 240 Time, and Retransmission Timer fields can be deleted if the host 241 knows these values. The MTU of this packet can be elided and the 242 IPv6 prefix helps the SCHC compression of the global address, 243 omitting the first 8 bytes of the address. 245 +----------------+----+----+--------+------------------+---+---------+ 246 | Field | FP | DI | Match | Comp Decomp | | Sent | 247 | | | | Opera. | Action | | [bits] | 248 +----------------+----+----+--------+------------------+---+---------+ 249 | Type | 1 | Bi | equal | not sent | | | 250 | | | | | | | | 251 | Code | 1 | Bi | equal | not sent | | | 252 | | | | | | | | 253 | Checksum | 1 | Bi | ignore | compute-checksum | | | 254 | | | | | | | | 255 | Current Hop | 1 | Bi | ignore | not sent | | | 256 | Limit | | | | | | | 257 | | | | | | | | 258 | Autoconfig | 1 | Bi | ignore | not sent | | | 259 | Flags | | | | | | | 260 | | | | | | | | 261 | Router | 1 | Bi | ignore | not sent | | | 262 | Lifetime | | | | | | | 263 | | | | | | | | 264 | Reachable Time | 1 | Bi | ignore | not sent | | | 265 | | | | | | | | 266 | Retransmission | 1 | Bi | ignore | not sent | | | 267 | Timer | | | | | | | 268 | | | | | | | | 269 | Option - type | 1 | Bi | equal | not sent | | | 270 | | | | | | | | 271 | Option - | 1 | Bi | ignore | compute-length | | | 272 | length | | | | | | | 273 | | | | | | | | 274 | Option - link- | 1 | Bi | ignore | sent | | [48] | 275 | layer | | | | | | | 276 | | | | | | | | 277 | Option - type | 1 | Bi | equal | not sent | | | 278 | | | | | | | | 279 | Option - | 1 | Bi | ignore | not sent | | | 280 | length | | | | | | | 281 | | | | | | | | 282 | Option - | 1 | Bi | equal | not sent | | | 283 | reserved | | | | | | | 284 | | | | | | | | 285 | Option - MTU | 1 | Bi | ignore | not sent | | | 286 | | | | | | | | 287 | Option - type | 1 | Bi | equal | not sent | | | 288 | | | | | | | | 289 | Option - | 1 | Bi | equal | not sent | | | 290 | length | | | | | | | 291 | | | | | | | | 292 | Option - Flag | 1 | Bi | ignore | not sent | | | 293 | | | | | | | | 294 | Option - Valid | 1 | Bi | ignore | not sent | | | 295 | lifetime | | | | | | | 296 | | | | | | | | 297 | Option - | 1 | Bi | ignore | not sent | | | 298 | Preferred | | | | | | | 299 | lifetime | | | | | | | 300 | | | | | | | | 301 | Option - | 1 | Bi | equal | not sent | | | 302 | reserved | | | | | | | 303 | | | | | | | | 304 | Option - | 1 | Bi | ignore | not sent | | | 305 | prefix | | | | | | | 306 +----------------+----+----+--------+------------------+---+---------+ 308 7. SCHC compression over Neighbor Solicitation 310 The Neighbor Solicitation packet header is composed by: 312 o Type: Type of message. Value: 0x87. 313 o Code: Always 0. 314 o Checksum: This field is composed by 2 Bytes where the values are 315 caculated as it is specified on RFC 4443 [RFC4443]. 316 o Target Address: It contains the address to be resolved. 317 o Options: This field contains the MAC Address from the host. 319 For SCHC compression over Neighbor Solicitation, the MAC address and 320 the Target Address are the minimal fields for the transmision. If 321 the Target address has a Link-Local value, the last 8 Bytes of the 322 address are sent, otherwise, the full 16 Bytes are sent. The type 323 field can be represented in the SCHC rule. 325 +------------+----+----+---------+------------------+---+------------+ 326 | Field | FP | DI | Match | Comp Decomp | | Sent | 327 | | | | Opera. | Action | | [bits] | 328 +------------+----+----+---------+------------------+---+------------+ 329 | Type | 1 | Bi | equal | not sent | | | 330 | | | | | | | | 331 | Code | 1 | Bi | equal | not sent | | | 332 | | | | | | | | 333 | Checksum | 1 | Bi | ignore | compute-checksum | | | 334 | | | | | | | | 335 | Target | 1 | Bi | match- | sent | | link-local | 336 | Address | | | mapping | | | [64] | 337 | | | | | | | global | 338 | | | | | | | [128] | 339 | | | | | | | | 340 | Option - | 1 | Bi | equal | not sent | | | 341 | type | | | | | | | 342 | | | | | | | | 343 | Option - | 1 | Bi | ignore | compute-length | | | 344 | length | | | | | | | 345 | | | | | | | | 346 | Option - | 1 | Bi | ignore | sent | | [48] | 347 | link-layer | | | | | | | 348 +------------+----+----+---------+------------------+---+------------+ 350 8. SCHC compression over Neighbor Advertisement 352 A Neighbor Advertisement is composed by: 354 o Type: Type of message. Value: 0x88. 355 o Code: Is always 0. 356 o Checksum: This field is composed by 2 Bytes where the values are 357 caculated as it is specified on RFC 4443 [RFC4443]. 358 o Flags: Describes first if the device sending the packet is a 359 router or a node, second if the packet is sent because it is a 360 neighbor search response and third, if the receiver has to rewrite 361 the host information. 362 o Target Address: If it is a reply of a Neighbor Solicitation 363 request, it contains the same Target address, otherwise it will 364 contain the address to be resolved. 365 o Options: If the packet source is a Multicast Neighbor Solicitation 366 reply, the MAC is sent, otherwise it is elided. 368 For the compression of SCHC in Neighbor Advertisement, the MAC 369 address is sent if it is a Multicast neighborhood request response. 370 If the Target address has a Link-Local value, the last 8 Bytes of the 371 address will be sent, otherwise, the full 16 Bytes will be 372 transmitted. If the Flags field is known by the host, it can be 373 deleted. The Type field can be represented in the SCHC rule. 375 +------------+----+----+---------+------------------+---+------------+ 376 | Field | FP | DI | Match | Comp Decomp | | Sent | 377 | | | | Opera. | Action | | [bits] | 378 +------------+----+----+---------+------------------+---+------------+ 379 | Type | 1 | Bi | equal | not sent | | | 380 | | | | | | | | 381 | Code | 1 | Bi | equal | not sent | | | 382 | | | | | | | | 383 | Checksum | 1 | Bi | ignore | compute-checksum | | | 384 | | | | | | | | 385 | Flags | 1 | Bi | equal | not sent | | | 386 | | | | | | | | 387 | Target | 1 | Bi | match- | sent | | link-local | 388 | Address | | | mapping | | | [64] | 389 | | | | | | | global | 390 | | | | | | | [128] | 391 | | | | | | | | 392 | Option - | 1 | Bi | equal | not sent | | | 393 | type | | | | | | | 394 | | | | | | | | 395 | Option - | 1 | Bi | ignore | not sent | | | 396 | length | | | | | | | 397 | | | | | | | | 398 | Option - | 1 | Bi | ignore | not sent | | | 399 | link-layer | | | | | | | 400 +------------+----+----+---------+------------------+---+------------+ 402 9. LoRa Gateway tables 404 (TODO) 406 10. Acknowledgments 408 This work is partially supported by 16STIC-08 STIC-AmSud PEACH 409 Research Project. We would also like to thank the Red Snapper 410 project for their support. 412 11. References 414 11.1. Normative References 416 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 417 Requirement Levels", BCP 14, RFC 2119, 418 DOI 10.17487/RFC2119, March 1997, 419 . 421 11.2. Internet Control Message Protocol (ICMPv6) for the Internet 422 Protocol Version 6 (IPv6) Specification 424 [RFC4443] Conta, A., Deering, S., and M. Gupta, Ed., "Internet 425 Control Message Protocol (ICMPv6) for the Internet 426 Protocol Version 6 (IPv6) Specification", STD 89, 427 RFC 4443, DOI 10.17487/RFC4443, March 2006, 428 . 430 11.3. Neighbor Discovery for IP version 6 (IPv6) 432 [RFC4861] Narten, T., Nordmark, E., Simpson, W., and H. Soliman, 433 "Neighbor Discovery for IP version 6 (IPv6)", RFC 4861, 434 DOI 10.17487/RFC4861, September 2007, 435 . 437 11.4. LPWAN Static Context Header Compression (SCHC) and fragmentation 438 for IPv6 and UDP 440 [I-D.toutain-lpwan-ipv6-static-context-hc] 441 Minaburo, A. and L. Toutain, "LPWAN Static Context Header 442 Compression (SCHC) for IPv6 and UDP", draft-toutain-lpwan- 443 ipv6-static-context-hc-00 (work in progress), September 444 2016. 446 Authors' Addresses 448 Tomas Lagos (editor) 449 Universidad Diego Portales 450 Escuela de Informatica y Telecomunicaciones 451 Av. Ejercito 441 452 Santiago, Region Metropolitana 453 Chile 455 Phone: +56 (97) 697-6404 456 Email: tomas.lagos@mail.udp.cl 458 Diego Dujovne 459 Universidad Diego Portales 460 Escuela de Informatica y Telecomunicaciones 461 Av. Ejercito 441 462 Santiago, Region Metropolitana 463 Chile 465 Phone: +56 (2) 676-8121 466 Email: diego.dujovne@mail.udp.cl