idnits 2.17.1 draft-richardson-6lo-ra-in-ie-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 abstract seems to contain references ([I-D.ietf-6tisch-minimal]), which it shouldn't. Please replace those with straight textual mentions of the documents in question. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year -- The document date (October 18, 2016) is 2719 days in the past. Is this intentional? Checking references for intended status: Informational ---------------------------------------------------------------------------- == Unused Reference: 'RFC7228' is defined on line 308, but no explicit reference was found in the text == Unused Reference: 'RFC2460' is defined on line 315, but no explicit reference was found in the text == Unused Reference: 'RFC4191' is defined on line 319, but no explicit reference was found in the text == Unused Reference: 'RFC4443' is defined on line 323, but no explicit reference was found in the text == Unused Reference: 'RFC4655' is defined on line 329, but no explicit reference was found in the text == Unused Reference: 'RFC4861' is defined on line 334, but no explicit reference was found in the text == Unused Reference: 'RFC7554' is defined on line 339, but no explicit reference was found in the text == Outdated reference: A later version (-07) exists of draft-ietf-6lo-dispatch-iana-registry-05 == Outdated reference: A later version (-30) exists of draft-ietf-6tisch-architecture-10 == Outdated reference: A later version (-21) exists of draft-ietf-6tisch-minimal-16 == Outdated reference: A later version (-06) exists of draft-kivinen-802-15-ie-03 ** Obsolete normative reference: RFC 2461 (Obsoleted by RFC 4861) -- Obsolete informational reference (is this intentional?): RFC 2460 (Obsoleted by RFC 8200) Summary: 2 errors (**), 0 flaws (~~), 12 warnings (==), 2 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 6lo Working Group M. Richardson 3 Internet-Draft Sandelman Software Works 4 Intended status: Informational October 18, 2016 5 Expires: April 21, 2017 7 802.15.4 Informational Element encapsulation of ICMPv6 Router 8 Advertisements 9 draft-richardson-6lo-ra-in-ie-00 11 Abstract 13 In TSCH mode of 802.15.4, as described by [I-D.ietf-6tisch-minimal], 14 opportunities for broadcasts are limited to specific times and 15 specific channels. An enhanced beacon must be broadcast periodically 16 by every router to keep all nodes in sync. This document provides a 17 mechanism by which other small ICMPv6 packets, such as Router 18 Advertisements may be carried within the Enhanced Beacon, providing 19 standard IPv6 router/host protocol. 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 April 21, 2017. 38 Copyright Notice 40 Copyright (c) 2016 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 . . . . . . . . . . . . . . . . . . . . . . . . 2 56 1.1. Terminology . . . . . . . . . . . . . . . . . . . . . . . 2 57 1.2. Layer-2 Synchronization . . . . . . . . . . . . . . . . . 2 58 1.3. Layer-3 synchronization IPv6 Router solicitations and 59 advertisements . . . . . . . . . . . . . . . . . . . . . 3 60 2. Protocol Definition . . . . . . . . . . . . . . . . . . . . . 3 61 2.1. Protocol Example . . . . . . . . . . . . . . . . . . . . 4 62 3. Security Considerations . . . . . . . . . . . . . . . . . . . 6 63 4. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 6 64 5. References . . . . . . . . . . . . . . . . . . . . . . . . . 6 65 5.1. Normative References . . . . . . . . . . . . . . . . . . 7 66 5.2. Informative References . . . . . . . . . . . . . . . . . 8 67 Appendix A. appendix . . . . . . . . . . . . . . . . . . . . . . 8 68 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 9 70 1. Introduction 72 [I-D.ietf-6tisch-architecture] describes the use of the time-slotted 73 channel hopping (TSCH) mode of [ieee802154]. As further details in 74 [I-D.ietf-6tisch-minimal], an Extended Beacon is transmitted during a 75 slot designated a broadcast slot. 77 EDNOTE: Explain why broadcasts are rare, and why we need them. What 78 the Enhanced Beacon is, and what Information Elements are, and how 79 the IETF has a subtype for that area. Explain what kind of things 80 could be placed in Information Elements, how big they could be, and 81 how they could be compressed. 83 1.1. Terminology 85 In this document, the key words "MUST", "MUST NOT", "REQUIRED", 86 "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", 87 and "OPTIONAL" are to be interpreted as described in BCP 14, RFC 2119 88 [RFC2119] and indicate requirement levels for compliant STuPiD 89 implementations. 91 1.2. Layer-2 Synchronization 93 As explained in section 6 of [I-D.ietf-6tisch-minimal], the Extended 94 Beacon has a number of purposes: synchronization of ASN and Join 95 Metric, timeslot template identifier, the channel hopping sequence 96 identifier, TSCH SlotFrame and Link IE. 98 The Extended Beacon is used by operating nodes to correct drift to 99 their clock, by nodes on medium length sleeps to resynchronize their 100 ASN, by nodes that have slept through a network rekey to rediscover 101 the network, and by new Joining Nodes (pledges) to learn about the 102 existance of the network. 104 There are a limited number of timeslots designated as a broadcast 105 slot by each router. These slots are rare, and with 10ms slots, with 106 a slot-frame length of 100, there may be only 1 slot/s for the 107 beacon. 109 1.3. Layer-3 synchronization IPv6 Router solicitations and 110 advertisements 112 At layer 3, [RFC2461] defines a mechanism by which nodes learn about 113 routers by listening for multicasted Router Advertisements (RA). If 114 no RA is heard within a set time, then a Router Solicitation (RS) may 115 be multicast, to which an RA will be received, usually unicast. 117 Although [RFC6775] reduces the amount of multicast necessary to do 118 address resolution via Neighbor Solicitation messages, it still 119 requires multicast of either RAs or RS. This is an expensive 120 operation for two reasons: there are few multicast timeslots for 121 unsolicited RAs; if a pledge node does not hear an RA, and decides to 122 send a RS (consuming a broadcast aloha slot with unencrypted 123 traffic), many unicast RS may be sent in response. 125 This is a particularly acute issue for the join process for the 126 following reasons: 128 1. use of a multicast slot by even a non-malicious unauthenticated 129 node for a Router Solicitation may overwhelm that time slot. 131 2. it may require many seconds of on-time before a new pledge hears 132 a Router Soliciation that it can use. 134 3. a new pledge may listen to many Enhanced Beacons before it can 135 pick an appropriate network and/or closest Join Assistant to 136 attach to. If it must listen for a RS as well as find the 137 Enhanced Beacon, then the process may take a very long time. 139 2. Protocol Definition 141 [I-D.kivinen-802-15-ie] creates a registry for new IETF IE subtypes. 142 This document allocates a new subtype TBD-XXX. 144 The base IE subtype structure is as follows. As explained in 145 [I-D.kivinen-802-15-ie] the length of the Sub-Type Content can be 146 calculated. 148 1 2 3 149 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 150 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 151 | TBD-XXX | 6LoRH encoded structure | 152 +-+-+-+-+-+-+-+-+ | 153 ~ Sub-Type Content ~ 154 | | 155 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 157 Inside the Sub-Type content should be placed compressed packets 158 according to [RFC6282] (as updated by 159 [I-D.ietf-6lo-dispatch-iana-registry]. 161 2.1. Protocol Example 163 Typically a Router Advertisement will be placed inside the Sub-Type. 164 The entire structure typically looks like: 166 0 1 2 3 167 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 168 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 169 |Ver 6 | TC = 0 | Flow Label = 0 | 170 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 171 | Payload Length | NH = 58 | Hop Lmt = 1 | 172 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 173 | | 174 + + 175 | | 176 + Source Address + 177 | fe80::LL | 178 + + 179 | | 180 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 181 | | 182 + + 183 | | 184 + Destination Address + 185 | fe02::1 | 186 + + 187 | | 188 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 189 | Type = 134 | Code = 0 | Checksum | 190 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 191 | HL = 0 |0|0| Reserved | Router lifetime = 9000 | 192 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 193 | Reachable Time = 0 XXX | 194 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 195 | Retrans Timer = 0 XXX | 196 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 197 | Type = 1 | Len = 10 | EUI-64 of router | 198 +-+-+-+-+-+-+-+-+-+-+-+---------+ + 199 | EUI-64 of router | 200 + +---------------+---------------+ 201 | EUI-64 of router | Type = TBD-YYY| Len = 18 | 202 +-------------------------------+-------------------------------+ 203 | DODAGID | 204 + | 205 | | 206 + | 207 | | 208 + | 209 | | 210 +---------------------------------------------------------------+ 212 When compressed by [RFC6282], this becomes: 214 +---------------------------------------------------------------+ 215 | 0 | 1 | 1 |TF= 11 |NH |HLIM=01|CID|SAC| SAM | M |DAC| DAM | 0 216 + | | | | 0 | | 0 | 0 | 0 1 + 1 + 0 + 1 1 + 217 +---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+ 218 | NH = 0x58 | dstXX = 0x01 | 4 219 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 220 | Type = 134 | Code = 0 | Checksum | 8 221 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 222 | HL = 0 |0|0| Reserved | Router lifetime = 9000 | 12 223 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 224 | Reachable Time = 0 XXX | 16 225 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 226 | Retrans Timer = 0 XXX | 20 227 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 228 | Type = 1 | Len = 10 | EUI-64 of router | 24 229 +-+-+-+-+-+-+-+-+-+-+-+---------+ + 230 | EUI-64 of router | 28 231 + +---------------+---------------+ 232 | EUI-64 of router | Type = TBD-YYY| Len = 18 | 32 233 +-------------------------------+-------------------------------+ 234 | DODAGID | 36 235 + | 236 | | 40 237 + | 238 | | 44 239 + | 240 | | 48 241 +---------------------------------------------------------------+ 243 The total number of bytes needed is 56 bytes. 245 3. Security Considerations 247 TBD. 249 4. IANA Considerations 251 Allocate a new number TBD-XXX from Registry IETF IE Sub-type ID. 252 This entry should be called 6LoRH-in-IE. 254 Allocate a new number TBD-YYY from Neighbor Discovery Option Types 255 (RFC2461) with the name "Constrained Network Identification". 257 5. References 258 5.1. Normative References 260 [I-D.ietf-6lo-dispatch-iana-registry] 261 Chakrabarti, S., Montenegro, G., Droms, R., and j. 262 woodyatt, "6lowpan ESC Dispatch Code Points and 263 Guidelines", draft-ietf-6lo-dispatch-iana-registry-05 264 (work in progress), September 2016. 266 [I-D.ietf-6tisch-architecture] 267 Thubert, P., "An Architecture for IPv6 over the TSCH mode 268 of IEEE 802.15.4", draft-ietf-6tisch-architecture-10 (work 269 in progress), June 2016. 271 [I-D.ietf-6tisch-minimal] 272 Vilajosana, X. and K. Pister, "Minimal 6TiSCH 273 Configuration", draft-ietf-6tisch-minimal-16 (work in 274 progress), June 2016. 276 [I-D.kivinen-802-15-ie] 277 Kivinen, T. and P. Kinney, "IEEE 802.15.4 Information 278 Element for IETF", draft-kivinen-802-15-ie-03 (work in 279 progress), October 2016. 281 [ieee802154] 282 IEEE Standard, ., "802.15.4-2015 - IEEE Standard for Low- 283 Rate Wireless Personal Area Networks (WPANs)", 2015, 284 . 287 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 288 Requirement Levels", BCP 14, RFC 2119, 289 DOI 10.17487/RFC2119, March 1997, 290 . 292 [RFC2461] Narten, T., Nordmark, E., and W. Simpson, "Neighbor 293 Discovery for IP Version 6 (IPv6)", RFC 2461, 294 DOI 10.17487/RFC2461, December 1998, 295 . 297 [RFC6282] Hui, J., Ed. and P. Thubert, "Compression Format for IPv6 298 Datagrams over IEEE 802.15.4-Based Networks", RFC 6282, 299 DOI 10.17487/RFC6282, September 2011, 300 . 302 [RFC6775] Shelby, Z., Ed., Chakrabarti, S., Nordmark, E., and C. 303 Bormann, "Neighbor Discovery Optimization for IPv6 over 304 Low-Power Wireless Personal Area Networks (6LoWPANs)", 305 RFC 6775, DOI 10.17487/RFC6775, November 2012, 306 . 308 [RFC7228] Bormann, C., Ersue, M., and A. Keranen, "Terminology for 309 Constrained-Node Networks", RFC 7228, 310 DOI 10.17487/RFC7228, May 2014, 311 . 313 5.2. Informative References 315 [RFC2460] Deering, S. and R. Hinden, "Internet Protocol, Version 6 316 (IPv6) Specification", RFC 2460, DOI 10.17487/RFC2460, 317 December 1998, . 319 [RFC4191] Draves, R. and D. Thaler, "Default Router Preferences and 320 More-Specific Routes", RFC 4191, DOI 10.17487/RFC4191, 321 November 2005, . 323 [RFC4443] Conta, A., Deering, S., and M. Gupta, Ed., "Internet 324 Control Message Protocol (ICMPv6) for the Internet 325 Protocol Version 6 (IPv6) Specification", RFC 4443, 326 DOI 10.17487/RFC4443, March 2006, 327 . 329 [RFC4655] Farrel, A., Vasseur, J., and J. Ash, "A Path Computation 330 Element (PCE)-Based Architecture", RFC 4655, 331 DOI 10.17487/RFC4655, August 2006, 332 . 334 [RFC4861] Narten, T., Nordmark, E., Simpson, W., and H. Soliman, 335 "Neighbor Discovery for IP version 6 (IPv6)", RFC 4861, 336 DOI 10.17487/RFC4861, September 2007, 337 . 339 [RFC7554] Watteyne, T., Ed., Palattella, M., and L. Grieco, "Using 340 IEEE 802.15.4e Time-Slotted Channel Hopping (TSCH) in the 341 Internet of Things (IoT): Problem Statement", RFC 7554, 342 DOI 10.17487/RFC7554, May 2015, 343 . 345 Appendix A. appendix 347 insert appendix here 349 Author's Address 351 Michael Richardson 352 Sandelman Software Works 354 Email: mcr+ietf@sandelman.ca