idnits 2.17.1 draft-richardson-6tisch-roll-enrollment-priority-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.richardson-6tisch-join-enhanced-beacon], [I-D.ietf-6tisch-minimal-security]), 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 == Line 133 has weird spacing: '...riority a 7 b...' == The document seems to lack the recommended RFC 2119 boilerplate, even if it appears to use RFC 2119 keywords. (The document does seem to have the reference to RFC 2119 which the ID-Checklist requires). -- The document date (February 02, 2018) is 2274 days in the past. Is this intentional? Checking references for intended status: Informational ---------------------------------------------------------------------------- == Unused Reference: 'I-D.ietf-6tisch-architecture' is defined on line 225, but no explicit reference was found in the text == Unused Reference: 'RFC8137' is defined on line 246, but no explicit reference was found in the text == Outdated reference: A later version (-15) exists of draft-ietf-6tisch-minimal-security-04 == Outdated reference: A later version (-30) exists of draft-ietf-6tisch-architecture-13 == Outdated reference: A later version (-10) exists of draft-ietf-6tisch-terminology-09 Summary: 1 error (**), 0 flaws (~~), 8 warnings (==), 1 comment (--). 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 February 02, 2018 5 Expires: August 6, 2018 7 Enabling secure network enrollment in RPL networks 8 draft-richardson-6tisch-roll-enrollment-priority-00 10 Abstract 12 [I-D.richardson-6tisch-join-enhanced-beacon] defines a method by 13 which a potential [I-D.ietf-6tisch-minimal-security] can announce 14 itself as a available for new Pledges to Join a network. The 15 announcement includes a priority for join. This document provides a 16 mechanism by which a RPL DODAG root can disable join announcements, 17 or adjust the base priority for join operation. 19 Status of This Memo 21 This Internet-Draft is submitted in full conformance with the 22 provisions of BCP 78 and BCP 79. 24 Internet-Drafts are working documents of the Internet Engineering 25 Task Force (IETF). Note that other groups may also distribute 26 working documents as Internet-Drafts. The list of current Internet- 27 Drafts is at https://datatracker.ietf.org/drafts/current/. 29 Internet-Drafts are draft documents valid for a maximum of six months 30 and may be updated, replaced, or obsoleted by other documents at any 31 time. It is inappropriate to use Internet-Drafts as reference 32 material or to cite them other than as "work in progress." 34 This Internet-Draft will expire on August 6, 2018. 36 Copyright Notice 38 Copyright (c) 2018 IETF Trust and the persons identified as the 39 document authors. All rights reserved. 41 This document is subject to BCP 78 and the IETF Trust's Legal 42 Provisions Relating to IETF Documents 43 (https://trustee.ietf.org/license-info) in effect on the date of 44 publication of this document. Please review these documents 45 carefully, as they describe your rights and restrictions with respect 46 to this document. Code Components extracted from this document must 47 include Simplified BSD License text as described in Section 4.e of 48 the Trust Legal Provisions and are provided without warranty as 49 described in the Simplified BSD License. 51 Table of Contents 53 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 54 1.1. Terminology . . . . . . . . . . . . . . . . . . . . . . . 3 55 2. Protocol Definition . . . . . . . . . . . . . . . . . . . . . 3 56 3. Security Considerations . . . . . . . . . . . . . . . . . . . 4 57 4. Privacy Considerations . . . . . . . . . . . . . . . . . . . 4 58 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 4 59 6. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 4 60 7. References . . . . . . . . . . . . . . . . . . . . . . . . . 4 61 7.1. Normative References . . . . . . . . . . . . . . . . . . 4 62 7.2. Informative References . . . . . . . . . . . . . . . . . 5 63 Appendix A. Change history . . . . . . . . . . . . . . . . . . . 6 64 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 6 66 1. Introduction 68 [RFC7554] describes the use of the time-slotted channel hopping 69 (TSCH) mode of [ieee802154]. [I-D.ietf-6tisch-minimal-security] and 70 [I-D.ietf-6tisch-dtsecurity-secure-join] describe mechanisms by which 71 a new node (the "pledge)" can use a friendly router as a Join Proxy. 72 [I-D.richardson-6tisch-join-enhanced-beacon] describes an extension 73 to the 802.15.4 Enhanced Beacon that is used by a Join Proxy to 74 announce its existence such that Pledges can find them. 76 It has become clear that not every routing member of the mesh ought 77 to announce itself as a Join Proxy. There are a variety of local 78 reasons by which a 6LR might not want to provide the Join Proxy 79 function. They include available battery power, already committed 80 network bandwidth, and also total available memory available for Join 81 proxy neighbor cache slots. 83 There are other situations where the operator of the network would 84 like to selective enable or disable the join process in a particular 85 DODAG. 87 As the join process involves permitting unencrypted traffic into the 88 best effort part of a (TSCH) network, it would be better to have the 89 join process off when no new nodes are expected. 91 A network operator might also be able to recognize when certain parts 92 of the network are overloaded and can not accomodate additional join 93 traffic, and it would like to adjust the join priority among all 94 nodes in the subtree of a congested link. 96 This document describes an RPL DIO option that can be used to 97 announce a minimum join priority. 99 1.1. Terminology 101 In this document, the key words "MUST", "MUST NOT", "REQUIRED", 102 "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", 103 and "OPTIONAL" are to be interpreted as described in BCP 14, RFC 2119 104 [RFC2119] and indicate requirement levels for compliant STuPiD 105 implementations. 107 In addition, the terminology of [I-D.ietf-6tisch-terminology] and 108 from [I-D.ietf-anima-voucher] are used. 110 2. Protocol Definition 112 The following option is defined to transmission in the DIO issued by 113 the DODAG root. It may also be added by a router on part of the sub- 114 tree as a result of some (out of scope for this document) management 115 function. 117 6LRs that see this DIO Option SHOULD increment the minimum priority 118 if they observe congestion on the channel used for join traffic. 119 (TODO: how much? Do we need to standardize this?) 121 A 6LR which would otherwise be willing to act as a Join Proxy, will 122 examine the minimum priority field, and to that number, add any 123 additional local consideration (such as upstream congestion). The 124 resulting priority, if less than 0x7f should enable the Join Proxy 125 function. 127 0 1 2 128 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 129 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 130 | Type = TBD01|Opt Length = 1|R| min. priority | 131 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 133 min.priority a 7 bit field which provides a base value for the 134 Enhanced Beacon Join priority. A value of 0x7f (127) disables the 135 Join Proxy function entirely. 137 R a reserved bit that SHOULD be set to 0 by senders, and MUST be 138 ignored by receivers. The reserved bit SHOULD be copied to 139 options created. 141 3. Security Considerations 143 As per [RFC7416], RPL control frames either run over a secured layer 144 2, or use the [RFC6550] Secure DIO methods. This option can be 145 placed into either a "clear" (layer-2 secured) DIO, or a layer-3 146 Secure DIO. As such this option will have both integrity and 147 confidentiality mechanisms applied to it. 149 A malicious node (that was part of the RPL control plane) could see 150 these options and could, based upon the observed minimal join 151 priority signal a confederate that it was a good time to send 152 malicious join traffic. 154 A malicious node (that was part of the RPL control plane) could also 155 send DIOs with a different minimal join priority which would cause 156 downstream mesh routers to change their Join Proxy behaviour. Lower 157 minimal priorities would cause downstream nodes to accept more 158 pledges than the network was expecting, and higher minimal priorities 159 cause the join process to stall. 161 The use of layer-2 or layer-3 security for RPL control messages 162 prevents the above two attacks. 164 4. Privacy Considerations 166 There are no new privacy issues caused by this extension. 168 5. IANA Considerations 170 Allocate a new number TBD01 from Registry RPL Control Message 171 Options. This entry should be called Minimum Join Priority. 173 6. Acknowledgements 175 none so far. 177 7. References 179 7.1. Normative References 181 [I-D.ietf-6tisch-minimal-security] 182 Vucinic, M., Simon, J., Pister, K., and M. Richardson, 183 "Minimal Security Framework for 6TiSCH", draft-ietf- 184 6tisch-minimal-security-04 (work in progress), October 185 2017. 187 [I-D.richardson-6tisch-join-enhanced-beacon] 188 Dujovne, D. and M. Richardson, "IEEE802.15.4 Informational 189 Element encapsulation of 6tisch Join Information", draft- 190 richardson-6tisch-join-enhanced-beacon-03 (work in 191 progress), January 2018. 193 [ieee802154] 194 IEEE Standard, ., "802.15.4-2015 - IEEE Standard for Low- 195 Rate Wireless Personal Area Networks (WPANs)", 2015, 196 . 199 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 200 Requirement Levels", BCP 14, RFC 2119, 201 DOI 10.17487/RFC2119, March 1997, 202 . 204 [RFC6550] Winter, T., Ed., Thubert, P., Ed., Brandt, A., Hui, J., 205 Kelsey, R., Levis, P., Pister, K., Struik, R., Vasseur, 206 JP., and R. Alexander, "RPL: IPv6 Routing Protocol for 207 Low-Power and Lossy Networks", RFC 6550, 208 DOI 10.17487/RFC6550, March 2012, 209 . 211 [RFC7416] Tsao, T., Alexander, R., Dohler, M., Daza, V., Lozano, A., 212 and M. Richardson, Ed., "A Security Threat Analysis for 213 the Routing Protocol for Low-Power and Lossy Networks 214 (RPLs)", RFC 7416, DOI 10.17487/RFC7416, January 2015, 215 . 217 [RFC7554] Watteyne, T., Ed., Palattella, M., and L. Grieco, "Using 218 IEEE 802.15.4e Time-Slotted Channel Hopping (TSCH) in the 219 Internet of Things (IoT): Problem Statement", RFC 7554, 220 DOI 10.17487/RFC7554, May 2015, 221 . 223 7.2. Informative References 225 [I-D.ietf-6tisch-architecture] 226 Thubert, P., "An Architecture for IPv6 over the TSCH mode 227 of IEEE 802.15.4", draft-ietf-6tisch-architecture-13 (work 228 in progress), November 2017. 230 [I-D.ietf-6tisch-dtsecurity-secure-join] 231 Richardson, M., "6tisch Secure Join protocol", draft-ietf- 232 6tisch-dtsecurity-secure-join-01 (work in progress), 233 February 2017. 235 [I-D.ietf-6tisch-terminology] 236 Palattella, M., Thubert, P., Watteyne, T., and Q. Wang, 237 "Terminology in IPv6 over the TSCH mode of IEEE 238 802.15.4e", draft-ietf-6tisch-terminology-09 (work in 239 progress), June 2017. 241 [I-D.ietf-anima-voucher] 242 Watsen, K., Richardson, M., Pritikin, M., and T. Eckert, 243 "Voucher Profile for Bootstrapping Protocols", draft-ietf- 244 anima-voucher-07 (work in progress), January 2018. 246 [RFC8137] Kivinen, T. and P. Kinney, "IEEE 802.15.4 Information 247 Element for the IETF", RFC 8137, DOI 10.17487/RFC8137, May 248 2017, . 250 Appendix A. Change history 252 version 00. 254 Author's Address 256 Michael Richardson 257 Sandelman Software Works 259 Email: mcr+ietf@sandelman.ca