Search RFCs

RFC Editor

File formats:

Also available:XML file for editing

 

Status:

PROPOSED STANDARD

Authors:

M. Vučinić, Ed.
J. Simon
K. Pister
M. Richardson

Stream:

IETF

Source:

6tisch (int)

Cite this RFC:TXT  | XML  |  BibTeX

DOI:  https://doi.org/10.17487/RFC9031

Discuss this RFC: Send questions or comments to the mailing list6tisch@ietf.org

Other actions:Submit Errata  | Find IPR Disclosures from the IETF  | View History of RFC 9031

Abstract

This document describes the minimal framework required for a newdevice, called a "pledge", to securely join a 6TiSCH (IPv6 over theTime-Slotted Channel Hopping mode of IEEE 802.15.4) network. Theframework requires that the pledge and the JRC (JoinRegistrar/Coordinator, a central entity), share a symmetric key. Howthis key is provisioned is out of scope of this document. Through asingle CoAP (Constrained Application Protocol) request-responseexchange secured by OSCORE (Object Security for Constrained RESTfulEnvironments), the pledge requests admission into the network, andthe JRC configures it with link-layer keying material and otherparameters. The JRC may at any time update the parameters throughanother request-response exchange secured by OSCORE. Thisspecification defines the Constrained Join Protocol and its CBOR(Concise Binary Object Representation) data structures, and itdescribes how to configure the rest of the 6TiSCH communication stackfor this join process to occur in a secure manner. Additionalsecurity mechanisms may be added on top of this minimal framework.

For the definition ofStatus,seeRFC 2026.

For the definition ofStream, seeRFC 8729.