Skip to main content

Constrained Join Protocol (CoJP) for 6TiSCH
RFC 9031

Revision differences

Document history

Date By Action
2021-06-01
(System) IANA registries were updated to include RFC9031
2021-05-29
(System)
Received changes through RFC Editor sync (created alias RFC 9031, changed abstract to 'This document describes the minimal framework required for a new device, …
Received changes through RFC Editor sync (created alias RFC 9031, changed abstract to 'This document describes the minimal framework required for a new device, called a "pledge", to securely join a 6TiSCH (IPv6 over the Time-Slotted Channel Hopping mode of IEEE 802.15.4) network.  The framework requires that the pledge and the JRC (Join Registrar/Coordinator, a central entity), share a symmetric key.  How this key is provisioned is out of scope of this document.  Through a single CoAP (Constrained Application Protocol) request-response exchange secured by OSCORE (Object Security for Constrained RESTful Environments), the pledge requests admission into the network, and the JRC configures it with link-layer keying material and other parameters.  The JRC may at any time update the parameters through another request-response exchange secured by OSCORE.  This specification defines the Constrained Join Protocol and its CBOR (Concise Binary Object Representation) data structures, and it describes how to configure the rest of the 6TiSCH communication stack for this join process to occur in a secure manner.  Additional security mechanisms may be added on top of this minimal framework.', changed pages to 41, changed standardization level to Proposed Standard, changed state to RFC, added RFC published event at 2021-05-29, changed IESG state to RFC Published)
2021-05-29
(System) RFC published