RFC 9031 on Constrained Join Protocol (CoJP) for 6TiSCH

rfc-editor@rfc-editor.org Sun, 30 May 2021 04:24 UTC

Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: ietf-announce@ietfa.amsl.com
Delivered-To: ietf-announce@ietfa.amsl.com
Received: from localhost (localhost []) by ietfa.amsl.com (Postfix) with ESMTP id DAA873A2D70; Sat, 29 May 2021 21:24:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.901
X-Spam-Status: No, score=-0.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, CTE_8BIT_MISMATCH=0.998, RCVD_IN_DNSWL_BLOCKED=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id UGhxH8seKQDh; Sat, 29 May 2021 21:24:23 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A7BBF3A2D47; Sat, 29 May 2021 21:24:21 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 9AF32F40725; Sat, 29 May 2021 21:24:04 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 9031 on Constrained Join Protocol (CoJP) for 6TiSCH
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Cc: rfc-editor@rfc-editor.org, drafts-update-ref@iana.org, 6tisch@ietf.org
Content-type: text/plain; charset="UTF-8"
Message-Id: <20210530042404.9AF32F40725@rfc-editor.org>
Date: Sat, 29 May 2021 21:24:04 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-announce/28XYT9tWXgaT4Ts-ofbrr5cTysI>
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf-announce/>
List-Post: <mailto:ietf-announce@ietf.org>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 30 May 2021 04:24:34 -0000

A new Request for Comments is now available in online RFC libraries.

        RFC 9031

        Title:      Constrained Join Protocol (CoJP) for 
        Author:     M. Vučinić, Ed.,
                    J. Simon,
                    K. Pister,
                    M. Richardson
        Status:     Standards Track
        Stream:     IETF
        Date:       May 2021
        Mailbox:    malisa.vucinic@inria.fr,
        Pages:      41
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-6tisch-minimal-security-15.txt

        URL:        https://www.rfc-editor.org/info/rfc9031

        DOI:        10.17487/RFC9031

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.

This document is a product of the IPv6 over the TSCH mode of IEEE 802.15.4e Working Group of the IETF.

This is now a Proposed Standard.

STANDARDS TRACK: This document specifies an Internet Standards Track
protocol for the Internet community, and requests discussion and suggestions
for improvements.  Please refer to the current edition of the Official
Internet Protocol Standards (https://www.rfc-editor.org/standards) for the 
standardization state and status of this protocol.  Distribution of this 
memo is unlimited.

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see

For searching the RFC series, see https://www.rfc-editor.org/search
For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk

Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.

The RFC Editor Team
Association Management Solutions, LLC