idnits 2.17.1 draft-ietf-6lowpan-hc-10.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 draft header indicates that this document updates RFC4944, but the abstract doesn't seem to mention this, which it should. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year == The document seems to use 'NOT RECOMMENDED' as an RFC 2119 keyword, but does not include the phrase in its RFC 2119 key words list. (Using the creation date from RFC4944, updated by this document, for RFC5378 checks: 2005-07-13) -- The document seems to lack a disclaimer for pre-RFC5378 work, but may have content which was first submitted before 10 November 2008. If you have contacted all the original authors and they are all willing to grant the BCP78 rights to the IETF Trust, then this is fine, and you can ignore this comment. If not, you may need to add the pre-RFC5378 disclaimer. (See the Legal Provisions document at https://trustee.ietf.org/license-info for more information.) -- The document date (August 31, 2010) is 4980 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) == Missing Reference: 'RFCthis' is mentioned on line 791, but not defined ** Obsolete normative reference: RFC 2460 (Obsoleted by RFC 8200) ** Obsolete normative reference: RFC 3775 (Obsoleted by RFC 6275) ** Obsolete normative reference: RFC 5226 (Obsoleted by RFC 8126) -- Obsolete informational reference (is this intentional?): RFC 3315 (Obsoleted by RFC 8415) Summary: 3 errors (**), 0 flaws (~~), 3 warnings (==), 4 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Network Working Group J. Hui, Ed. 3 Internet-Draft Arch Rock Corporation 4 Updates: 4944 (if approved) P. Thubert 5 Intended status: Standards Track Cisco 6 Expires: March 4, 2011 August 31, 2010 8 Compression Format for IPv6 Datagrams in 6LoWPAN Networks 9 draft-ietf-6lowpan-hc-10 11 Abstract 13 This document specifies an IPv6 header compression format for IPv6 14 packet delivery in 6LoWPAN networks. The compression format relies 15 on shared context to allow compression of arbitrary prefixes. How 16 the information is maintained in that shared context is out of scope. 17 This document specifies compression of multicast addresses and a 18 framework for compressing next headers. UDP header compression is 19 specified within this framework. 21 Status of this Memo 23 This Internet-Draft is submitted in full conformance with the 24 provisions of BCP 78 and BCP 79. 26 Internet-Drafts are working documents of the Internet Engineering 27 Task Force (IETF). Note that other groups may also distribute 28 working documents as Internet-Drafts. The list of current Internet- 29 Drafts is at http://datatracker.ietf.org/drafts/current/. 31 Internet-Drafts are draft documents valid for a maximum of six months 32 and may be updated, replaced, or obsoleted by other documents at any 33 time. It is inappropriate to use Internet-Drafts as reference 34 material or to cite them other than as "work in progress." 36 This Internet-Draft will expire on March 4, 2011. 38 Copyright Notice 40 Copyright (c) 2010 IETF Trust and the persons identified as the 41 document authors. All rights reserved. 43 This document is subject to BCP 78 and the IETF Trust's Legal 44 Provisions Relating to IETF Documents 45 (http://trustee.ietf.org/license-info) in effect on the date of 46 publication of this document. Please review these documents 47 carefully, as they describe your rights and restrictions with respect 48 to this document. Code Components extracted from this document must 49 include Simplified BSD License text as described in Section 4.e of 50 the Trust Legal Provisions and are provided without warranty as 51 described in the Simplified BSD License. 53 Table of Contents 55 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 56 1.1. Requirements Language . . . . . . . . . . . . . . . . . . 4 57 2. Specific Updates to RFC 4944 . . . . . . . . . . . . . . . . . 4 58 3. IPv6 Header Compression . . . . . . . . . . . . . . . . . . . 5 59 3.1. LOWPAN_IPHC Encoding Format . . . . . . . . . . . . . . . 6 60 3.1.1. Base Format . . . . . . . . . . . . . . . . . . . . . 6 61 3.1.2. Context Identifier Extension . . . . . . . . . . . . . 9 62 3.2. IPv6 Header Encoding . . . . . . . . . . . . . . . . . . . 9 63 3.2.1. Traffic Class and Flow Label Compression . . . . . . . 10 64 3.2.2. Deriving IIDs from the Encapsulating Header . . . . . 11 65 3.2.3. Stateless Multicast Address Compression . . . . . . . 12 66 3.2.4. Stateful Multicast Address Compression . . . . . . . . 13 67 4. IPv6 Next Header Compression . . . . . . . . . . . . . . . . . 13 68 4.1. LOWPAN_NHC Format . . . . . . . . . . . . . . . . . . . . 14 69 4.2. IPv6 Extension Header Compression . . . . . . . . . . . . 14 70 4.3. UDP Header Compression . . . . . . . . . . . . . . . . . . 16 71 4.3.1. Compressing UDP ports . . . . . . . . . . . . . . . . 16 72 4.3.2. Compressing UDP checksum . . . . . . . . . . . . . . . 16 73 4.3.3. UDP LOWPAN_NHC Format . . . . . . . . . . . . . . . . 17 74 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 18 75 6. Security Considerations . . . . . . . . . . . . . . . . . . . 19 76 7. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 19 77 8. Changes . . . . . . . . . . . . . . . . . . . . . . . . . . . 19 78 9. References . . . . . . . . . . . . . . . . . . . . . . . . . . 21 79 9.1. Normative References . . . . . . . . . . . . . . . . . . . 21 80 9.2. Informative References . . . . . . . . . . . . . . . . . . 22 81 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 22 83 1. Introduction 85 The [IEEE 802.15.4] standard specifies an MTU of 127 bytes, yielding 86 about 80 octets of actual MAC payload with security enabled, on a 87 wireless link with a link throughput of 250 kbps or less. The 88 6LoWPAN adaptation format [RFC4944] was specified to carry IPv6 89 datagrams over such constrained links, taking into account limited 90 bandwidth, memory, or energy resources that are expected in 91 applications such as wireless sensor networks. [RFC4944] defines a 92 Mesh Addressing header to support sub-IP forwarding, a Fragmentation 93 header to support the IPv6 minimum MTU requirement [RFC2460], and 94 stateless header compression for IPv6 datagrams (LOWPAN_HC1 and 95 LOWPAN_HC2) to reduce the relatively large IPv6 and UDP headers down 96 to (in the best case) several bytes. 98 LOWPAN_HC1 and LOWPAN_HC2 are insufficient for most practical uses of 99 6LoWPAN networks. LOWPAN_HC1 is most effective for link-local 100 unicast communication, where IPv6 addresses carry the link-local 101 prefix and an Interface Identifier (IID) directly derived from IEEE 102 802.15.4 addresses. In this case, both addresses may be completely 103 elided. However, though link-local addresses are commonly used for 104 local protocol interactions such as IPv6 ND [RFC4861], DHCPv6 105 [RFC3315] or routing protocols, they are usually not used for 106 application-layer data traffic, so the actual value of this 107 compression mechanism is limited. 109 Routable addresses must be used when communicating with devices 110 external to the LoWPAN or in a route-over configuration where IP 111 forwarding occurs within the LoWPAN. For routable addresses, 112 LOWPAN_HC1 requires both IPv6 source and destination addresses to 113 carry the prefix in-line. In cases where the Mesh Addressing header 114 is not used, the IID of a routable address must be carried in-line. 115 However, LOWPAN_HC1 requires 64-bits for the IID when carried in-line 116 and cannot be shortened even when it is derived from the IEEE 117 802.15.4 16-bit short address. When the destination is an IPv6 118 multicast address, LOWPAN_HC1 requires the full 128-bit address to be 119 carried in-line. 121 As a result, this document defines an encoding format, LOWPAN_IPHC, 122 for effective compression of Unique Local, Global, and multicast IPv6 123 Addresses based on shared state within contexts. In addition, this 124 document also introduces a number of additional improvements over the 125 header compression format defined in [RFC4944]. 127 LOWPAN_IPHC allows for compression of some commonly-used IPv6 Hop 128 Limit values. If the LoWPAN is a mesh-under stub, a Hop Limit of 1 129 for inbound and a default value such as 64 for outbound are usually 130 enough for application layer data traffic. Additionally, a hop-limit 131 value of 255 is often used to verify that a communication occurs over 132 a single-hop. This specification enables compression of the IPv6 Hop 133 Limit field in those common cases, whereas LOWPAN_HC1 does not. 135 This document also defines LOWPAN_NHC, an encoding format for 136 arbitrary next headers. LOWPAN_IPHC indicates whether the following 137 header is encoded using LOWPAN_NHC. If so, the bits immediately 138 following the compressed IPv6 header start the LOWPAN_NHC encoding. 139 In contrast, LOWPAN_HC1 could be extended to support compression of 140 next headers using LOWPAN_HC2, but only for UDP, TCP, and ICMPv6. 141 Furthermore, the LOWPAN_HC2 octet sits between the LOWPAN_HC1 octet 142 and uncompressed IPv6 header fields. This specification moves the 143 next header encoding bits to follow all IPv6-related bits, allowing 144 for a properly layered structure and direct support for IPv6 145 extension headers. 147 Using LOWPAN_NHC, this document defines a compression mechanism for 148 UDP. While [RFC4944] defines a compression mechanism for UDP, that 149 mechanism does not enable checksum compression when rendered possible 150 by additional upper layer mechanisms such as upper layer Message 151 Integrity Check (MIC). This specification adds the capability to 152 elide the UDP checksum over the LoWPAN, which enables saving of a 153 further two octets. 155 Also using LOWPAN_NHC, this document defines encoding formats for 156 IPv6-in-IPv6 encapsulation as well as IPv6 Extension Headers. With 157 LOWPAN_HC1 and LOWPAN_HC2, chains of next headers cannot be encoded 158 efficiently. 160 1.1. Requirements Language 162 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 163 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 164 document are to be interpreted as described in RFC 2119 [RFC2119]. 166 2. Specific Updates to RFC 4944 168 This document specifies a header compression format that is intended 169 to replace that defined in Section 10 of [RFC4944]. Implementation 170 of Section 10 of [RFC4944] is now NOT RECOMMENDED. New 171 implementations MAY implement compression according to Section 10 of 172 [RFC4944], but SHOULD NOT send packets compressed according to 173 Section 10 of [RFC4944]. 175 A compliant implementation of [RFC4944] as updated by this document 176 MUST be able to properly process a packet received that makes use of 177 the provisions of this document. A compliant implementation MAY 178 implement additional LOWPAN_NHC types (Section 4) that may be 179 registered (Section 5) in the future. It is out of scope of this 180 document how a compressor learns that a decompressor has additional 181 capabilities. 183 Section 5.3 of [RFC4944] also defines how to fragment compressed IPv6 184 datagrams that do not fit within a single link frame. Section 5.3 of 185 [RFC4944] defines the fragment header's datagram_size and 186 datagram_offset values as the size and offset of the IPv6 datagram 187 before compression. As a result, all fragment payload outside the 188 first fragment must carry their respective portions of the IPv6 189 datagram before compression. This document does not change that 190 requirement. When using the fragmentation mechanism described in 191 Section 5.3 of [RFC4944], any header that cannot fit within the first 192 fragment MUST NOT be compressed. 194 The header compression format defined in this document preempts the 195 ESC dispatch value defined in Section 5.1 of [RFC4944]. Instead, the 196 value of 01 000000 is reserved as a replacement value for ESC, to be 197 finally assigned with the first assignment of extension bytes. 199 3. IPv6 Header Compression 201 In this section, we define the LOWPAN_IPHC encoding format for 202 compressing the IPv6 header. To enable effective compression 203 LOWPAN_IPHC relies on information pertaining to the entire 6LoWPAN 204 network. LOWPAN_IPHC assumes the following will be the common case 205 for 6LoWPAN communication: Version is 6; Traffic Class and Flow Label 206 are both zero; Payload Length can be inferred from lower layers from 207 either the 6LoWPAN Fragmentation header or the IEEE 802.15.4 header; 208 Hop Limit will be set to a well-known value by the source; addresses 209 assigned to 6LoWPAN interfaces will be formed using the link-local 210 prefix or a small set of routable prefixes assigned to the entire 211 6LoWPAN network; addresses assigned to 6LoWPAN interfaces are formed 212 with an IID derived directly from either the 64-bit extended or 16- 213 bit short IEEE 802.15.4 addresses. 215 +-------------------------------------+---------------------------- 216 | Dispatch + LOWPAN_IPHC (2-3 octets) | In-line IPv6 Header Fields 217 +-------------------------------------+---------------------------- 219 Figure 1: LOWPAN_IPHC Header 221 The LOWPAN_IPHC encoding utilizes 13 bits, 5 of which are taken from 222 the rightmost bit of the dispatch type. The encoding may be extended 223 by another octet to support additional contexts. Any information 224 from the uncompressed IPv6 header fields carried in-line follow the 225 LOWPAN_IPHC encoding, as shown in Figure 1. In the best case, the 226 LOWPAN_IPHC can compress the IPv6 header down to two octets (the 227 dispatch octet and the LOWPAN_IPHC encoding) with link-local 228 communication. 230 When routing over multiple IP hops, LOWPAN_IPHC can compress the IPv6 231 header down to 7 octets (1-octet dispatch, 1-octet LOWPAN_IPHC, 232 1-octet Hop Limit, 2-octet Source Address, and 2-octet Destination 233 Address). The Hop Limit may not be compressed because it needs to 234 decremented at each hop and may take any value. Stateful address 235 compression must be applied to the source and destination IPv6 236 addresses because they do not statelessly match the source and 237 destination link layer addresses on intermediate hops. 239 3.1. LOWPAN_IPHC Encoding Format 241 This section specifies the format of the LOWPAN_IPHC encoding that 242 describes how an IPv6 header is compressed. The encoding can be 2 243 octets long for the base encoding or 3 octets long when an additional 244 context encoding is present. The IPv6 header fields that are not 245 fully elided are placed immediately after the LOWPAN_IPHC, either in 246 a compressed form if the field is partially elided, or literally. 248 3.1.1. Base Format 250 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 251 +---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+ 252 | 0 | 1 | 1 | TF |NH | HLIM |CID|SAC| SAM | M |DAC| DAM | 253 +---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+ 255 Figure 2: LOWPAN_IPHC base Encoding 257 TF: Traffic Class, Flow Label: 258 00: ECN + DSCP + 4-bit Pad + Flow Label (4 bytes) 259 01: ECN + 2-bit Pad + Flow Label (3 bytes), DSCP is elided 260 10: ECN + DSCP (1 byte), Flow Label is elided 261 11: Traffic Class and Flow Label are elided. 263 NH: Next Header: 264 0: Full 8 bits for Next Header are carried in-line. 266 1: The Next Header field is compressed and the next header is 267 encoded using LOWPAN_NHC, which is discussed in Section 4. 269 HLIM: Hop Limit: 270 00: The Hop Limit field is carried in-line. 271 01: The Hop Limit field is compressed and the hop limit is 1. 272 10: The Hop Limit field is compressed and the hop limit is 64. 273 11: The Hop Limit field is compressed and the hop limit is 255. 275 CID: Context Identifier Extension: 276 0: No additional 8-bit Context Identifier Extension is used. If 277 context-based compression is specified in either SAC or DAC, 278 context 0 is used. 279 1: An additional 8-bit Context Identifier Extension field 280 immediately follows the DAM field. 282 SAC: Source Address Compression 283 0: Source address compression uses stateless compression. 284 1: Source address compression uses stateful, context-based 285 compression. 287 SAM: Source Address Mode: 288 If SAC=0: 289 00: 128 bits. The full address is carried in-line. 290 01: 64 bits. The first 64-bits of the address are elided. 291 The value of those bits is the link-local prefix padded with 292 zeros. The remaining 64 bits are carried in-line. 293 10: 16 bits. The first 112 bits of the address are elided. 294 The value of the first 64 bits is the link-local prefix 295 padded with zeros. The following 64 bits are 0000:00ff: 296 fe00:XXXX, where XXXX are the 16 bits carried in-line. 297 11: 0 bits. The address is fully elided. The first 64 bits 298 of the address are the link-local prefix padded with zeros. 299 The remaining 64 bits are computed from the encapsulating 300 header (e.g. 802.15.4 or IPv6 source address) as specified 301 in Section 3.2.2. 302 If SAC=1: 303 00: The UNSPECIFIED address, :: 304 01: 64 bits. The address is derived using context information 305 and the 64 bits carried in-line. 306 10: 16 bits. The address is derived using context information 307 and the 16 bits carried in-line. 308 11: 0 bits. The address is fully elided. The prefix is 309 derived using context information. Any of the remaining 64 310 bits not covered by the context information are computed 311 from the encapsulating header (e.g. 802.15.4 or IPv6 source 312 address) as specified in Section 3.2.2. 314 M: Multicast Compression 315 0: Destination address is not a multicast address. 316 1: Destination address is a multicast address. 318 DAC: Destination Address Compression 319 0: Destination address compression uses stateless compression. 320 1: Destination address compression uses stateful, context-based 321 compression. 323 DAM: Destination Address Mode: 324 If M=0 and DAC=0 This case matches SAC=0 but for the destination 325 address: 326 00: 128 bits. The full address is carried in-line. 327 01: 64 bits. The first 64-bits of the address are elided. 328 The value of those bits is the link-local prefix padded with 329 zeros. The remaining 64 bits are carried in-line. 330 10: 16 bits. The first 112 bits of the address are elided. 331 The value of the first 64 bits is the link-local prefix 332 padded with zeros. The following 64 bits are 0000:00ff: 333 fe00:XXXX, where XXXX are the 16 bits carried in-line. 334 11: 0 bits. The address is fully elided. The first 64 bits 335 of the address are the link-local prefix padded with zeros. 336 The remaining 64 bits are computed from the encapsulating 337 header (e.g. 802.15.4 or IPv6 destination address) as 338 specified in Section 3.2.2. 339 If M=0 and DAC=1: 340 00: Reserved. 341 01: 64 bits. The address is derived using context information 342 and the 64 bits carried in-line. 343 10: 16 bits. The address is derived using context information 344 and the 16 bits carried in-line. 345 11: 0 bits. The address is fully elided. The prefix is 346 derived using context information. Any of the remaining 64 347 bits not covered by the context information are computed 348 from the encapsulating header (e.g. 802.15.4 or IPv6 349 destination address) as specified in Section 3.2.2. 350 If M=1 and DAC=0: 351 00: 128 bits. The full address is carried in-line. 352 01: 48 bits. The address takes the form FFXX::00XX:XXXX:XXXX. 353 10: 32 bits. The address takes the form FFXX::00XX:XXXX. 354 11: 8 bits. The address takes the form FF02::00XX. 355 If M=1 and DAC=1: 356 00: 48 bits. This format is designed to match Unicast-Prefix- 357 based IPv6 Multicast Addresses as defined in [RFC3306] and 358 [RFC3956]. The multicast address takes the form FFXX:XXLL: 359 PPPP:PPPP:PPPP:PPPP:XXXX:XXXX. where the X are the nibbles 360 that are carried in-line, in the order in which they appear 361 in this format. P denotes nibbles used to encode the prefix 362 itself. L denotes nibbles used to encode the prefix length. 363 The prefix information P and L is taken from the specified 364 context. 365 01: reserved 366 10: reserved 367 11: reserved 369 3.1.2. Context Identifier Extension 371 This specification expects that a conceptual context is shared 372 between the node that compresses a packet and the node(s) that need 373 to expand it. How the contexts are shared and maintained is out of 374 scope. What information is contained within a context information is 375 out of scope. Actions in response to unknown and/or invalid contexts 376 are out of scope. The specification enables a node to use up to 16 377 contexts. The context used to encode the source address does not 378 have to be the same as the context used to encode the destination 379 address. 381 If the CID field is set to '1' in the LOWPAN_IPHC encoding, then an 382 additional octet extends the LOWPAN_IPHC encoding following the DAM 383 bits but before the IPv6 header fields that are carried in-line. The 384 additional octet identifies the pair of contexts to be used when the 385 IPv6 source and/or destination address is compressed. The context 386 identifier is 4 bits for each address, supporting up to 16 contexts. 387 Context 0 is the default context. The encoding is shown in Figure 3. 389 0 1 2 3 4 5 6 7 390 +---+---+---+---+---+---+---+---+ 391 | SCI | DCI | 392 +---+---+---+---+---+---+---+---+ 394 Figure 3: LOWPAN_IPHC Encoding 396 SCI: Source Context Identifier Identifies the prefix that is used 397 when the IPv6 source address is statefully compressed. 398 DCI: Destination Context Identifier Identifies the prefix that is 399 used when the IPv6 destination address is statefully compressed. 401 3.2. IPv6 Header Encoding 403 Fields carried in-line (in part or in whole) appear in the same order 404 as they do in the IPv6 header format [RFC2460]. The Version field is 405 always elided. Unicast IPv6 addresses may be compressed to 64 or 16 406 bits or completely elided. Multicast IPv6 addresses may be 407 compressed to 8, 32, or 48 bits. The IPv6 Payload Length field MUST 408 always be elided and inferred from lower layers using the 6LoWPAN 409 Fragmentation header or the IEEE 802.15.4 header. 411 3.2.1. Traffic Class and Flow Label Compression 413 The Traffic Class field in the IPv6 header comprises 6 bits of 414 diffserv extension [RFC2474] and 2 bits of Explicit Congestion 415 Notification (ECN) [RFC3168]. The TF field in the LOWPAN_IPHC 416 encoding indicates whether the Traffic Class and Flow Label are 417 carried in-line in the compressed IPv6 header. When Flow Label is 418 included while the Traffic Class is compressed, an additional 4 bits 419 are included to maintain byte-alignment. Two of the 4 bits contain 420 the ECN bits from the Traffic Class field. 422 To ensure that the ECN bits appear in the same location for all 423 encodings that include them, the Traffic Class field is rotated right 424 by 2 bits in the compressed IPv6 header. The encodings are shown 425 below: 427 1 2 3 428 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 429 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 430 |ECN| DSCP | rsv | Flow Label | 431 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 433 TF = 00: Traffic Class and Flow Label carried in-line. 435 1 2 436 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 437 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 438 |ECN|rsv| Flow Label | 439 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 441 TF = 01: Flow Label carried in-line. 443 0 1 2 3 4 5 6 7 444 +-+-+-+-+-+-+-+-+ 445 |ECN| DSCP | 446 +-+-+-+-+-+-+-+-+ 448 TF = 10: Traffic Class carried in-line. 450 3.2.2. Deriving IIDs from the Encapsulating Header 452 LOWPAN_IPHC elides the IIDs of source or destination addresses when 453 SAM = 3 or DAM = 3, respectively. In this mode, the IID is derived 454 from the encapsulating header. When the encapsulating header carries 455 IPv6 addresses, bits for the source and destination addresses are 456 copied verbatim from the source and destination addresses of the 457 encapsulating IPv6 header. 459 The remainder of this section defines the mapping from IEEE 802.15.4 460 link-layer addresses to IIDs for both short and extended IEEE 461 802.15.4 addresses. IID bits not covered by the context information 462 MAY be elided if they match the link-layer address mapping and MUST 463 NOT be elided if they do not. 465 An extended IEEE 802.15.4 address takes the form of an IEEE EUI-64 466 address. Generating an IID from an extended address is identical to 467 that defined in Appendix A of [RFC4291]. The only change needed to 468 transform an IEEE EUI-64 identifier to an interface identifier is to 469 invert the universal/local bit. 471 A short IEEE 802.15.4 address is 16 bits in length. Short addresses 472 are mapped into the restricted space of IEEE EUI-64 addresses by 473 setting the middle 16 bits to 0xfffe, the bottom 16 bits to the short 474 address, and all other bits to zero. As a result, an IID generated 475 from a short address has the form: 477 0000:00ff:fe00:XXXX 479 where XXXX carries the short address. The universal/local bit is 480 zero to indicate local scope. 482 This mapping for non-EUI-64 identifiers differs from that presented 483 in Appendix A of [RFC4291]. Using the restricted space ensures no 484 overlap with IIDs generated from unrestricted IEEE EUI-64 addresses. 485 Also, including 0xfffe in the middle of the IID helps avoid overlap 486 with other locally managed IIDs. 488 This mapping from a short IEEE 802.15.4 address to 64-bit IIDs is 489 also used to reconstruct any part of an IID not covered by context 490 information when only 16 bits are carried in-line (SAC/DAC=10). 492 3.2.3. Stateless Multicast Address Compression 494 LOWPAN_IPHC supports stateless compression of multicast addresses 495 when M = 1 and DAC = 0. An IPv6 multicast address may be compressed 496 down to 48, 32, or 8 bits using stateless compression. The format 497 supports compression of the Solicited-Node Multicast Address (FF02:: 498 1:FFXX:XXXX) as well as any IPv6 multicast address where the upper 499 bits of the multicast group identifier are zero. The 8-bit 500 compressed form only carries the least-significant bits of the 501 multicast group identifier. The 48 and 32-bit compressed forms carry 502 the multicast scope and flags in-line, in addition to the least- 503 significant bits of the multicast group identifier. 505 1 2 3 506 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 507 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 508 | Flags | Scope | Group Identifier | 509 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 510 | Group Identifier | 511 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 513 DAM = 01. 48-bit Compressed Multicast Address (FFfs::00gg:gggg:gggg) 515 1 2 3 516 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 517 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 518 | Flags | Scope | Group Identifier | 519 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 521 DAM = 10. 32-bit Compressed Multicast Address (FFfs::00gg:gggg). 523 0 1 2 3 4 5 6 7 524 +-+-+-+-+-+-+-+-+ 525 | Group ID | 526 +-+-+-+-+-+-+-+-+ 528 DAM = 11. 8-bit Compressed Multicast Address (FF02::gg). 530 3.2.4. Stateful Multicast Address Compression 532 LOWPAN_IPHC supports stateful compression of multicast addresses when 533 M = 1 and DAC = 1. This document currently defines DAM = 00: 534 context-based compression of Unicast-Prefix-based IPv6 Multicast 535 Addresses [RFC3306][RFC3956]. In particular, the Prefix Length and 536 Network Prefix can be taken from a context. As a result, LOWPAN_IPHC 537 can compress a Unicast-Prefix-based IPv6 Multicast Address down to 6 538 octets by only carrying the 4-bit Flags, 4-bit Scope, 8-bit RIID, and 539 32-bit Group Identifier in-line. 541 1 2 3 542 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 543 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 544 | Flags | Scope | Rsvd / RIID | Group Identifier | 545 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 546 | Group Identifier | 547 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 549 DAM = 01. Unicast-Prefix-based IPv6 Multicast Address Compression 551 Note that the Reserved field MUST carry the reserved bits from the 552 multicast address format as described in [RFC3306]. When a 553 Rendezvous Point is encoded in the multicast address as described in 554 [RFC3956], the Reserved field carries the RIID bits in-line. 556 4. IPv6 Next Header Compression 558 LOWPAN_IPHC elides the IPv6 Next Header field when the NH bit is set 559 to 1. This also indicates the use of 6LoWPAN next header 560 compression, LOWPAN_NHC. The value of IPv6 Next Header is recovered 561 from the first bits in the LOWPAN_NHC encoding. The following bits 562 are specific to the IPv6 Next Header value. Figure 4 shows the 563 structure of an IPv6 datagram compressed using LOWPAN_IPHC and 564 LOWPAN_NHC. 566 +-------------+-------------+-------------+-----------------+-------- 567 | LOWPAN_IPHC | In-line | LOWPAN_NHC | In-line Next | Payload 568 | Encoding | IP Fields | Encoding | Header Fields | 569 +-------------+-------------+-------------+-----------------+-------- 571 Figure 4: Typical LOWPAN_IPHC/LOWPAN_NHC Header Configuration 573 4.1. LOWPAN_NHC Format 575 Compression formats for different next headers are identified by a 576 variable-length bit-pattern immediately following the LOWPAN_IPHC 577 compressed header. When defining a next header compression format, 578 the number of bits used SHOULD be determined by the perceived 579 frequency of using that format. However, the number of bits and any 580 remaining encoding bits SHOULD respect octet alignment. The 581 following bits are specific to the next header compression format. 582 This document defines a compression format for IPv6 Extension and UDP 583 headers. 585 +----------------+--------------------------- 586 | var-len NHC ID | compressed next header... 587 +----------------+--------------------------- 589 Figure 5: LOWPAN_NHC Encoding 591 4.2. IPv6 Extension Header Compression 593 A necessary property of encoding headers using LOWPAN_NHC is that the 594 immediately preceding header must either be encoded using LOWPAN_IPHC 595 or LOWPAN_NHC. In other words, all headers encoded using the 6LoWPAN 596 encoding format defined in this document must be contiguous. As a 597 result, this document defines a set of LOWPAN_NHC encodings for 598 selected IPv6 Extension Headers such that the UDP Header Compression 599 defined in Section 4.3 may be used in the presence of those extension 600 headers. 602 The LOWPAN_NHC encodings for IPv6 Extension Headers are composed of a 603 single LOWPAN_NHC octet followed by the IPv6 Extension Header. The 604 format of the LOWPAN_NHC octet is shown in Figure 6. The first 7 605 bits serve as an identifier for the IPv6 Extension Header immediately 606 following the LOWPAN_NHC octet. The remaining bit indicates whether 607 or not the following header utilizes LOWPAN_NHC encoding. 609 0 1 2 3 4 5 6 7 610 +---+---+---+---+---+---+---+---+ 611 | 1 | 1 | 1 | 0 | EID |NH | 612 +---+---+---+---+---+---+---+---+ 614 Figure 6: IPv6 Extension Header Encoding 616 EID: IPv6 Extension Header ID: 617 0: IPv6 Hop-by-Hop Options Header[RFC2460] 618 1: IPv6 Routing Header[RFC2460] 619 2: IPv6 Fragment Header[RFC2460] 620 3: IPv6 Destination Options Header[RFC2460] 621 4: IPv6 Mobility Header [RFC3775] 622 5: Reserved 623 6: Reserved 624 7: IPv6 Header 626 NH: Next Header: 627 0: Full 8 bits for Next Header are carried in-line. 628 1: The Next Header field is elided and the next header is encoded 629 using LOWPAN_NHC, which is discussed in Section 4. 631 For the most part, the IPv6 Extension Header is carried verbatim in 632 the bytes immediately following the LOWPAN_NHC octet, with two 633 important exceptions: Length Field and Next Header Field. 635 The Next Header Field contained in IPv6 Extension Headers is elided 636 when the NH bit is set in the LOWPAN_NHC encoding octet. Note that 637 doing so allows LOWPAN_NHC to utilize no more overhead than the non- 638 encoded IPv6 Extension Header. 640 The Length Field contained in a compressed IPv6 Extension Header 641 indicates the number of octets that pertain to the (compressed) 642 extension header following the Length Field. Note that this changes 643 the Length Field definition in [RFC2460] from indicating the header 644 size in 8-octet units, not including the first 8 octets. Changing 645 the Length Field to be in units of octets removes wasteful internal 646 fragmentation. 648 IPv6 Hop-by-Hop and Destination Options Headers may use a trailing 649 Pad1 or PadN to achieve 8-octet alignment. When there is a single 650 trailing Pad1 or PadN option of 7 octets or less and the containing 651 header is a multiple of 8 octets, the trailing Pad1 or PadN option 652 MAY be elided by the compressor. A decompressor MUST ensure that the 653 containing header is padded out to a multiple of 8 octets in length, 654 using a Pad1 or PadN option if necessary. Note that Pad1 and PadN 655 options that appear in locations other than the end MUST be carried 656 in-line as they are used to align subsequent options. 658 Note that specifying units in octets means that LOWPAN_NHC MUST NOT 659 be used to encode IPv6 Extension Headers that have more than 255 660 octets following the Length Field after compression. 662 When the identified next header is an IPv6 Header (EID=7), the NH bit 663 of the LOWPAN_NHC encoding is unused and MUST be set to zero. The 664 following bytes MUST be encoded using LOWPAN_IPHC as defined in 665 Section 3. 667 4.3. UDP Header Compression 669 This document defines a compression format for UDP headers using 670 LOWPAN_NHC. The UDP compression format is shown in Figure 7. Bits 0 671 through 4 represent the NHC ID and '11110' indicates the specific UDP 672 header compression encoding defined in this section. 674 4.3.1. Compressing UDP ports 676 This specification introduces a range of well-known ports (0xF0Bx) 677 that can be compressed to 4 bits. Considering that this represents 678 only 16 contiguous ports, it can be expected that many incompatible 679 applications will use the same port numbers for their own end-to-end 680 needs. 682 The overloading of the 0xF0Bx ports increases the risk of getting the 683 wrong type of payload and misinterpreting the content compared to 684 ports that are reserved at IANA. As a result, it is recommended that 685 the use of those ports be associated with a mechanism such as a 686 Transport Layer Security (TLS) Message Integrity Check (MIC) that 687 validates that the content is expected and checked for integrity. 689 4.3.2. Compressing UDP checksum 691 The UDP checksum operation is mandatory with IPv6 [RFC2460] for all 692 packets. For that reason [RFC4944] disallows the compression of the 693 UDP checksum. 695 With this specification, a compressor in the source transport 696 endpoint MAY elide the UDP checksum if it is authorized by the Upper 697 Layer. The compressor SHOULD NOT set the C bit unless it has 698 received such authorization. The Upper Layer SHOULD only provide the 699 authorization in the following cases: 701 Tunneling: In this case, 6LoWPAN is deployed as a wireless pseudo- 702 fieldbus by tunneling existing field protocols over UDP. If the 703 tunneled PDU possesses its own addressing, security and integrity 704 check, the tunneling mechanism MAY authorize to elide the UDP 705 checksum in order to save on the encapsulation overhead. 706 Upper Layer Message Integrity Check: In this case, there is some 707 other form of integrity check in the UDP payload that covers at 708 least the same information as the UDP checksum (pseudo-header, 709 data) and has at least the same strength. 711 A forwarding node MAY imply authorization from an incoming packet if 712 the C bit is set. A forwarding node that cannot unambiguously derive 713 such authorization SHOULD NOT elide the UDP checksum when performing 714 6LoWPAN compression. The forwarding node that expands a 6LoWPAN 715 packet with the C bit on MUST compute the UDP checksum on behalf of 716 the source node and place that checksum in the restored UDP header as 717 specified in the incumbent standards [RFC0768], [RFC2460]. 719 If a 6LoWPAN termination is also the transport endpoint and it 720 receives a compressed packet with the C bit set, then it is entitled 721 to ignore the UDP checksum process completely. If the C bit is not 722 set, the packet might have been forwarded by an edge router, so this 723 is not an indication that the MIC is not present. If the terminating 724 node knows that the message integrity will be validated by the upper 725 layer by some state associated to the Service Access Point, it is 726 entitled to ignore the checksum operation as if the C bit was set. 728 4.3.3. UDP LOWPAN_NHC Format 730 0 1 2 3 4 5 6 7 731 +---+---+---+---+---+---+---+---+ 732 | 1 | 1 | 1 | 1 | 0 | C | P | 733 +---+---+---+---+---+---+---+---+ 735 Figure 7: UDP Header Encoding 737 C: Checksum: 738 0: All 16 bits of Checksum are carried in-line. 739 1: All 16 bits of Checksum are elided. The Checksum is recovered 740 by recomputing it on the 6LoWPAN termination point. 742 P: Ports: 743 00: All 16 bits for both Source Port and Destination Port are 744 carried in-line. 745 01: All 16 bits for Source Port are carried in-line. First 8 746 bits of Destination Port is 0xF0 and elided. The remaining 8 747 bits of Destination Port are carried in-line. 748 10: First 8 bits of Source Port are 0xF0 and elided. The 749 remaining 8 bits of Source Port are carried in-line. All 16 750 bits for Destination Port are carried in-line. 751 11: First 12 bits of both Source Port and Destination Port are 752 0xF0B and elided. The remaining 4 bits for each are carried 753 in-line. 755 Fields carried in-line (in part or in whole) appear in the same order 756 as they do in the UDP header format [RFC0768]. The UDP Length field 757 MUST always be elided and is inferred from lower layers using the 758 6LoWPAN Fragmentation header or the IEEE 802.15.4 header. 760 5. IANA Considerations 762 This document defines a new IPv6 header compression format for 763 6LoWPAN networks. The document allocates the following 32 Dispatch 764 type field values for LOWPAN_IPHC: 766 01 100000 767 through 768 01 111111 770 This assignment preempts the assignment of 01 111111 for ESC 771 [RFC4944], which is possible as no extension bytes have been 772 allocated yet that would enable the use of ESC. Instead, the value: 774 01 000000 776 is reserved as a replacement value for ESC, to be finally assigned 777 with the first assignment of extension bytes. 779 This document also creates a new IANA registry for the LOWPAN_NHC 780 header type, with the following initial content: 782 00000000 to 11011111: (unassigned) 783 1110000N: IPv6 Hop-by-Hop Options Header [RFCthis] 784 1110001N: IPv6 Routing Header [RFCthis] 785 1110010N: IPv6 Fragment Header [RFCthis] 786 1110011N: IPv6 Destination Options Header [RFCthis] 787 1110100N: IPv6 Mobility Header [RFCthis] 788 1110101N: (Reserved for future extension headers) 789 1110110N: (Reserved for future extension headers) 790 1110111N: IPv6 Header [RFCthis] 791 11110CPP: UDP Header [RFCthis] 792 11111000 to 11111110: (unassigned) 793 11111111: (unassigned, reserved for extensions) 795 Capital letters in bit positions represent class-specific bit 796 assignments. N indicates whether or not additional LOWPAN_NHC 797 encodings follow, as defined in Section 4.2. CPP represents 798 variables specific to UDP header compression defined in Section 4.3. 800 The policy for this registry [RFC5226] is IETF Review. In this 801 process, new values SHOULD be assigned in a way that preserves the 802 NHC ID abstraction of Section 4 (i.e., k one-bits followed by one 803 zero-bit identify the general class of NHC, followed by class- 804 specific bit assignments). 806 6. Security Considerations 808 The definition of LOWPAN_IPHC permits the compression of header 809 information on communication that could take place in its absence, 810 albeit in a less efficient form. It recognizes that a IEEE 802.15.4 811 PAN may have associated with it a number of prefixes through shared 812 context. How the shared context is assigned and managed is beyond 813 the scope of this document. 815 The overloading of the 0xF0Bx ports increases the risk of getting the 816 wrong type of payload and misinterpreting the content compared to 817 ports that reserved at IANA. It is thus recommended that the use of 818 those ports be associated with a mechanism such as a Transport Layer 819 Security (TLS) Message Integrity Check (MIC) that validates that the 820 content is expected and checked for integrity. 822 7. Acknowledgements 824 Thanks to Julien Abeille, Robert Assimiti, Dominique Barthel, Carsten 825 Bormann, Robert Cragie, Stephen Dawson-Haggerty, Mathilde Durvy, Erik 826 Nordmark, Christos Polyzois, Shoichi Sakane, Zach Shelby, Dario 827 Tedeschi, Tony Viscardi, and Jay Werb for useful design consideration 828 and implementation feedback. 830 8. Changes 832 (This section to be removed by the RFC editor.) 834 Draft 10: 835 - Specify that the IID has the form 0000:00ff:fe00:XXXX when SAC/ 836 DAC=0 and SAM/DAM=10. 838 Draft 09: 839 - Indicate that a mechanism to learn decompressor's capabilities 840 to decode additional (future) NHCs is out of scope. 841 - Clarify how to derive IID bits not covered by the context when 842 only 16 bits are carried inline. 843 - Clarify the value of the Length field for compressed extension 844 headers. 845 - Added an IANA registry for LOWPAN_NHC types. 847 Draft 08: 849 - Clarified that the lower bits of an IPv6 address may be derived 850 from an IPv6 header, not just an 802.15.4 header. Change text 851 from "derived from link-layer header" to "derived from 852 encapsulating header". 854 Draft 07: 855 - Added section on mapping link-layer addresses to IIDs. 856 - Added text on restricting compressed headers to first fragment 857 when using fragment headers defined in Section 5.3 of [RFC4944]. 858 - Minor editorial edits. 860 Draft 06: 861 - Reworked introduction. 862 - Added section on updates to [RFC4944]. 863 - Fixed description of number of bits used for IPHC encoding. 864 - Specify M=0 only for non-multicast addresses and M=1 only for 865 multicast addresses. 866 - Move 128-bit multicast encoding to DAC=0. 867 - Redefined ESC dispatch value to 01 000000. 868 - Many detailed edits. 870 Draft 05: 871 - Added LOWPAN_NHC encodings for IPv6 Extension Headers. 872 - Specify use of context 0 when CID is 0. 873 - Indicate that first 64-bits is link-local prefix padded with 874 zeros when link-local prefix is elided. 875 - Made prefix-based multicast encoding format more explicit for 876 clarity. 877 - Changed wording around stateful compression to allow for using 878 the in-line bits as an additional index to identify the compressed 879 address. 880 - Removed support for compressing unspecified address. 881 - Full 128-bit addr in-line only in stateless encoding. 883 Draft 04: 884 - Fixed typos leftover from the changes in 03. 885 - Gave more details on UDP checksum compression. 886 - Clarify that the context information is out of scope. 887 - Added security concern on 0xF0Bx port overloading. 889 Draft 03: 890 - Decoupled meaning of SAM bits from the destination address. 891 - Have separate bit to indicate multicast address compression. 892 - More extensive support for multicast address compression, 893 including Unicast-Prefix-based Multicast Addresses. 895 Draft 02: 897 - Updated wording with compression mode to clarify that a 898 compression mode does not enforce what kind of destination address 899 is being used. Specifically changed Destination Dependent Field 900 to Compression Mode. 901 - Specify that the configuration and management of contexts is out 902 of scope of this document. 904 Draft 01: 905 - HC back to 1 byte by default by stealing a few bits from the 906 dispatch field. 907 - Added better support for multicast address compression. 908 - Fixed alignment for UDP port compression. 909 - Better support for Traffic Class and Flow Label compression. 910 - Pascal joined as an author. 912 9. References 914 9.1. Normative References 916 [RFC0768] Postel, J., "User Datagram Protocol", STD 6, RFC 768, 917 August 1980. 919 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 920 Requirement Levels", BCP 14, RFC 2119, March 1997. 922 [RFC2460] Deering, S. and R. Hinden, "Internet Protocol, Version 6 923 (IPv6) Specification", RFC 2460, December 1998. 925 [RFC2474] Nichols, K., Blake, S., Baker, F., and D. Black, 926 "Definition of the Differentiated Services Field (DS 927 Field) in the IPv4 and IPv6 Headers", RFC 2474, 928 December 1998. 930 [RFC3168] Ramakrishnan, K., Floyd, S., and D. Black, "The Addition 931 of Explicit Congestion Notification (ECN) to IP", 932 RFC 3168, September 2001. 934 [RFC3775] Johnson, D., Perkins, C., and J. Arkko, "Mobility Support 935 in IPv6", RFC 3775, June 2004. 937 [RFC4291] Hinden, R. and S. Deering, "IP Version 6 Addressing 938 Architecture", RFC 4291, February 2006. 940 [RFC4944] Montenegro, G., Kushalnagar, N., Hui, J., and D. Culler, 941 "Transmission of IPv6 Packets over IEEE 802.15.4 942 Networks", RFC 4944, September 2007. 944 [RFC5226] Narten, T. and H. Alvestrand, "Guidelines for Writing an 945 IANA Considerations Section in RFCs", BCP 26, RFC 5226, 946 May 2008. 948 9.2. Informative References 950 [IEEE 802.15.4] 951 IEEE Computer Society, "IEEE Std. 802.15.4-2006", 952 October 2006. 954 [RFC3306] Haberman, B. and D. Thaler, "Unicast-Prefix-based IPv6 955 Multicast Addresses", RFC 3306, August 2002. 957 [RFC3315] Droms, R., Bound, J., Volz, B., Lemon, T., Perkins, C., 958 and M. Carney, "Dynamic Host Configuration Protocol for 959 IPv6 (DHCPv6)", RFC 3315, July 2003. 961 [RFC3956] Savola, P. and B. Haberman, "Embedding the Rendezvous 962 Point (RP) Address in an IPv6 Multicast Address", 963 RFC 3956, November 2004. 965 [RFC4861] Narten, T., Nordmark, E., Simpson, W., and H. Soliman, 966 "Neighbor Discovery for IP version 6 (IPv6)", RFC 4861, 967 September 2007. 969 Authors' Addresses 971 Jonathan W. Hui (editor) 972 Arch Rock Corporation 973 501 2nd St. Ste. 410 974 San Francisco, California 94107 975 USA 977 Phone: +415 692 0828 978 Email: jhui@archrock.com 979 Pascal Thubert 980 Cisco Systems 981 Village d'Entreprises Green Side 982 400, Avenue de Roumanille 983 Batiment T3 984 Biot - Sophia Antipolis 06410 985 FRANCE 987 Phone: +33 4 97 23 26 34 988 Email: pthubert@cisco.com