< draft-ietf-roll-enrollment-priority-00.txt		draft-ietf-roll-enrollment-priority-01.txt >
	6lo Working Group M. Richardson		ROLL Working Group M. Richardson
	Internet-Draft Sandelman Software Works		Internet-Draft Sandelman Software Works
	Intended status: Informational September 16, 2019		Intended status: Informational March 19, 2020
	Expires: March 19, 2020		Expires: September 20, 2020
	Enabling secure network enrollment in RPL networks		Enabling secure network enrollment in RPL networks
	draft-ietf-roll-enrollment-priority-00		draft-ietf-roll-enrollment-priority-01
	Abstract		Abstract
	[I-D.6tisch-enrollment-enhanced-beacon] defines a method by which a		[I-D.ietf-6tisch-enrollment-enhanced-beacon] defines a method by
	potential [I-D.ietf-6tisch-minimal-security] can announce itself as a		which a potential [I-D.ietf-6tisch-minimal-security] join proxy can
	available for new Pledges to Join a network. The announcement		announce itself as a available for new Pledges to Join a network.
	includes a priority for join. This document provides a mechanism by		The announcement includes a priority for join. This document
	which a RPL DODAG root can disable join announcements, or adjust the		provides a mechanism by which a RPL DODAG root can disable join
	base priority for join operation.		announcements, or adjust the base priority for join operation.
	Status of This Memo		Status of This Memo
	This Internet-Draft is submitted in full conformance with the		This Internet-Draft is submitted in full conformance with the
	provisions of BCP 78 and BCP 79.		provisions of BCP 78 and BCP 79.
	Internet-Drafts are working documents of the Internet Engineering		Internet-Drafts are working documents of the Internet Engineering
	Task Force (IETF). Note that other groups may also distribute		Task Force (IETF). Note that other groups may also distribute
	working documents as Internet-Drafts. The list of current Internet-		working documents as Internet-Drafts. The list of current Internet-
	Drafts is at https://datatracker.ietf.org/drafts/current/.		Drafts is at https://datatracker.ietf.org/drafts/current/.
	Internet-Drafts are draft documents valid for a maximum of six months		Internet-Drafts are draft documents valid for a maximum of six months
	and may be updated, replaced, or obsoleted by other documents at any		and may be updated, replaced, or obsoleted by other documents at any
	time. It is inappropriate to use Internet-Drafts as reference		time. It is inappropriate to use Internet-Drafts as reference
	material or to cite them other than as "work in progress."		material or to cite them other than as "work in progress."
	This Internet-Draft will expire on March 19, 2020.		This Internet-Draft will expire on September 20, 2020.
	Copyright Notice		Copyright Notice
	Copyright (c) 2019 IETF Trust and the persons identified as the		Copyright (c) 2020 IETF Trust and the persons identified as the
	document authors. All rights reserved.		document authors. All rights reserved.
	This document is subject to BCP 78 and the IETF Trust's Legal		This document is subject to BCP 78 and the IETF Trust's Legal
	Provisions Relating to IETF Documents		Provisions Relating to IETF Documents
	(https://trustee.ietf.org/license-info) in effect on the date of		(https://trustee.ietf.org/license-info) in effect on the date of
	publication of this document. Please review these documents		publication of this document. Please review these documents
	carefully, as they describe your rights and restrictions with respect		carefully, as they describe your rights and restrictions with respect
	to this document. Code Components extracted from this document must		to this document. Code Components extracted from this document must
	include Simplified BSD License text as described in Section 4.e of		include Simplified BSD License text as described in Section 4.e of
	the Trust Legal Provisions and are provided without warranty as		the Trust Legal Provisions and are provided without warranty as
	skipping to change at page 2, line 28 ¶		skipping to change at page 2, line 28 ¶
	7.2. Informative References . . . . . . . . . . . . . . . . . 5		7.2. Informative References . . . . . . . . . . . . . . . . . 5
	Appendix A. Change history . . . . . . . . . . . . . . . . . . . 6		Appendix A. Change history . . . . . . . . . . . . . . . . . . . 6
	Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 6		Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 6
	1. Introduction		1. Introduction
	[RFC7554] describes the use of the time-slotted channel hopping		[RFC7554] describes the use of the time-slotted channel hopping
	(TSCH) mode of [ieee802154]. [I-D.ietf-6tisch-minimal-security] and		(TSCH) mode of [ieee802154]. [I-D.ietf-6tisch-minimal-security] and
	[I-D.ietf-6tisch-dtsecurity-secure-join] describe mechanisms by which		[I-D.ietf-6tisch-dtsecurity-secure-join] describe mechanisms by which
	a new node (the "pledge)" can use a friendly router as a Join Proxy.		a new node (the "pledge)" can use a friendly router as a Join Proxy.
	[I-D.6tisch-enrollment-enhanced-beacon] describes an extension to the		[I-D.ietf-6tisch-enrollment-enhanced-beacon] describes an extension
	802.15.4 Enhanced Beacon that is used by a Join Proxy to announce its		to the 802.15.4 Enhanced Beacon that is used by a Join Proxy to
	existence such that Pledges can find them.		announce its existence such that Pledges can find them.
	It has become clear that not every routing member of the mesh ought		It has become clear that not every routing member of the mesh ought
	to announce itself as a Join Proxy. There are a variety of local		to announce itself as a Join Proxy. There are a variety of local
	reasons by which a 6LR might not want to provide the Join Proxy		reasons by which a 6LR might not want to provide the Join Proxy
	function. They include available battery power, already committed		function. They include available battery power, already committed
	network bandwidth, and also total available memory available for Join		network bandwidth, and also total available memory available for Join
	proxy neighbor cache slots.		proxy neighbor cache slots.
	There are other situations where the operator of the network would		There are other situations where the operator of the network would
	like to selective enable or disable the join process in a particular		like to selective enable or disable the join process in a particular
	skipping to change at page 3, line 15 ¶		skipping to change at page 3, line 15 ¶
	This document describes an RPL DIO option that can be used to		This document describes an RPL DIO option that can be used to
	announce a minimum join priority. Each potential Join Proxy would		announce a minimum join priority. Each potential Join Proxy would
	this value as a base on which to add (decreasing likely hood of		this value as a base on which to add (decreasing likely hood of
	attracting traffic) values relating to local conditions.		attracting traffic) values relating to local conditions.
	A network operator can set this value to the maximum value allowed,		A network operator can set this value to the maximum value allowed,
	effectively disable all new join traffic.		effectively disable all new join traffic.
	1.1. Terminology		1.1. Terminology
	In this document, the key words "MUST", "MUST NOT", "REQUIRED",		The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
	"SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY",		"SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and
	and "OPTIONAL" are to be interpreted as described in BCP 14, RFC 2119		"OPTIONAL" in this document are to be interpreted as described in
	[RFC2119] and indicate requirement levels for compliant STuPiD		BCP 14 [RFC2119] [RFC8174] when, and only when, they appear in all
	implementations.		capitals, as shown here.
	In addition, the terminology of [I-D.ietf-6tisch-terminology] and
	from [I-D.ietf-anima-voucher] are used.
	2. Protocol Definition		2. Protocol Definition
	The following option is defined to transmission in the DIO issued by		The following option is defined to transmission in the DIO issued by
	the DODAG root. It may also be added by a router on part of the sub-		the DODAG root. It may also be added by a router on part of the sub-
	tree as a result of some (out of scope for this document) management		tree as a result of some (out of scope for this document) management
	function.		function.
	6LRs that see this DIO Option SHOULD increment the minimum priority		6LRs that see this DIO Option SHOULD increment the minimum priority
	if they observe congestion on the channel used for join traffic.		if they observe congestion on the channel used for join traffic.
	skipping to change at page 5, line 5 ¶		skipping to change at page 4, line 45 ¶
	Options. This entry should be called Minimum Join Priority.		Options. This entry should be called Minimum Join Priority.
	6. Acknowledgements		6. Acknowledgements
	This has been reviewed by Pascal Thubert and Thomas Wattenye.		This has been reviewed by Pascal Thubert and Thomas Wattenye.
	7. References		7. References
	7.1. Normative References		7.1. Normative References
	[I-D.6tisch-enrollment-enhanced-beacon]		[I-D.ietf-6tisch-enrollment-enhanced-beacon]
	Dujovne, D. and M. Richardson, "IEEE802.15.4 Informational		Dujovne, D. and M. Richardson, "IEEE 802.15.4 Information
	Element encapsulation of 6tisch Join and Enrollment		Element encapsulation of 6TiSCH Join and Enrollment
	Information", draft-6tisch-enrollment-enhanced-beacon-00		Information", draft-ietf-6tisch-enrollment-enhanced-
	(work in progress), July 2018.		beacon-14 (work in progress), February 2020.
	[I-D.ietf-6tisch-minimal-security]		[I-D.ietf-6tisch-minimal-security]
	Vucinic, M., Simon, J., Pister, K., and M. Richardson,		Vucinic, M., Simon, J., Pister, K., and M. Richardson,
	"Minimal Security Framework for 6TiSCH", draft-ietf-		"Constrained Join Protocol (CoJP) for 6TiSCH", draft-ietf-
	6tisch-minimal-security-12 (work in progress), July 2019.		6tisch-minimal-security-15 (work in progress), December
			2019.
	[ieee802154]		[ieee802154]
	IEEE standard for Information Technology, ., "IEEE Std.		IEEE standard for Information Technology, ., "IEEE Std.
	802.15.4, Part. 15.4: Wireless Medium Access Control (MAC)		802.15.4, Part. 15.4: Wireless Medium Access Control (MAC)
	and Physical Layer (PHY) Specifications for Low-Rate		and Physical Layer (PHY) Specifications for Low-Rate
	Wireless Personal Area Networks", n.d.,		Wireless Personal Area Networks", n.d.,
	<http://standards.ieee.org/findstds/		<http://standards.ieee.org/findstds/
	standard/802.15.4-2015.html>.		standard/802.15.4-2015.html>.
	[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate		[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
	skipping to change at page 5, line 48 ¶		skipping to change at page 5, line 43 ¶
	the Routing Protocol for Low-Power and Lossy Networks		the Routing Protocol for Low-Power and Lossy Networks
	(RPLs)", RFC 7416, DOI 10.17487/RFC7416, January 2015,		(RPLs)", RFC 7416, DOI 10.17487/RFC7416, January 2015,
	<https://www.rfc-editor.org/info/rfc7416>.		<https://www.rfc-editor.org/info/rfc7416>.
	[RFC7554] Watteyne, T., Ed., Palattella, M., and L. Grieco, "Using		[RFC7554] Watteyne, T., Ed., Palattella, M., and L. Grieco, "Using
	IEEE 802.15.4e Time-Slotted Channel Hopping (TSCH) in the		IEEE 802.15.4e Time-Slotted Channel Hopping (TSCH) in the
	Internet of Things (IoT): Problem Statement", RFC 7554,		Internet of Things (IoT): Problem Statement", RFC 7554,
	DOI 10.17487/RFC7554, May 2015,		DOI 10.17487/RFC7554, May 2015,
	<https://www.rfc-editor.org/info/rfc7554>.		<https://www.rfc-editor.org/info/rfc7554>.
			[RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC
			2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174,
			May 2017, <https://www.rfc-editor.org/info/rfc8174>.
	7.2. Informative References		7.2. Informative References
	[I-D.ietf-6tisch-architecture]		[I-D.ietf-6tisch-architecture]
	Thubert, P., "An Architecture for IPv6 over the TSCH mode		Thubert, P., "An Architecture for IPv6 over the TSCH mode
	of IEEE 802.15.4", draft-ietf-6tisch-architecture-26 (work		of IEEE 802.15.4", draft-ietf-6tisch-architecture-28 (work
	in progress), August 2019.		in progress), October 2019.
	[I-D.ietf-6tisch-dtsecurity-secure-join]		[I-D.ietf-6tisch-dtsecurity-secure-join]
	Richardson, M., "6tisch Secure Join protocol", draft-ietf-		Richardson, M., "6tisch Secure Join protocol", draft-ietf-
	6tisch-dtsecurity-secure-join-01 (work in progress),		6tisch-dtsecurity-secure-join-01 (work in progress),
	February 2017.		February 2017.
	[I-D.ietf-6tisch-terminology]		[I-D.ietf-6tisch-terminology]
	Palattella, M., Thubert, P., Watteyne, T., and Q. Wang,		Palattella, M., Thubert, P., Watteyne, T., and Q. Wang,
	"Terms Used in IPv6 over the TSCH mode of IEEE 802.15.4e",		"Terms Used in IPv6 over the TSCH mode of IEEE 802.15.4e",
	draft-ietf-6tisch-terminology-10 (work in progress), March		draft-ietf-6tisch-terminology-10 (work in progress), March
	2018.		2018.
	[I-D.ietf-anima-voucher]
	Watsen, K., Richardson, M., Pritikin, M., and T. Eckert,
	"Voucher Profile for Bootstrapping Protocols", draft-ietf-
	anima-voucher-07 (work in progress), January 2018.
	[RFC8137] Kivinen, T. and P. Kinney, "IEEE 802.15.4 Information		[RFC8137] Kivinen, T. and P. Kinney, "IEEE 802.15.4 Information
	Element for the IETF", RFC 8137, DOI 10.17487/RFC8137, May		Element for the IETF", RFC 8137, DOI 10.17487/RFC8137, May
	2017, <https://www.rfc-editor.org/info/rfc8137>.		2017, <https://www.rfc-editor.org/info/rfc8137>.
			[RFC8366] Watsen, K., Richardson, M., Pritikin, M., and T. Eckert,
			"A Voucher Artifact for Bootstrapping Protocols",
			RFC 8366, DOI 10.17487/RFC8366, May 2018,
			<https://www.rfc-editor.org/info/rfc8366>.
	Appendix A. Change history		Appendix A. Change history
	version 00.		version 00.
	Author's Address		Author's Address
	Michael Richardson		Michael Richardson
	Sandelman Software Works		Sandelman Software Works
	Email: mcr+ietf@sandelman.ca		Email: mcr+ietf@sandelman.ca
End of changes. 14 change blocks.
	37 lines changed or deleted		39 lines changed or added
This html diff was produced by rfcdiff 1.48. The latest version is available from http://tools.ietf.org/tools/rfcdiff/