RFC 9032 on Encapsulation of 6TiSCH Join and Enrollment Information Elements
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 [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B55893A2D9B; Sat, 29 May 2021 21:24:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_BLOCKED=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id yxkf8LJA8KTv; Sat, 29 May 2021 21:24:44 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C17D83A2D2C; Sat, 29 May 2021 21:24:37 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id C6C52F40749; Sat, 29 May 2021 21:24:20 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 9032 on Encapsulation of 6TiSCH Join and Enrollment Information Elements
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: <20210530042420.C6C52F40749@rfc-editor.org>
Date: Sat, 29 May 2021 21:24:20 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-announce/-NiVYzt3sfFs9VbiVX-tHIKcmn4>
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:57 -0000
A new Request for Comments is now available in online RFC libraries. RFC 9032 Title: Encapsulation of 6TiSCH Join and Enrollment Information Elements Author: D. Dujovne, Ed., M. Richardson Status: Standards Track Stream: IETF Date: May 2021 Mailbox: diego.dujovne@mail.udp.cl, mcr+ietf@sandelman.ca Pages: 10 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-6tisch-enrollment-enhanced-beacon-14.txt URL: https://www.rfc-editor.org/info/rfc9032 DOI: 10.17487/RFC9032 In the Time-Slotted Channel Hopping (TSCH) mode of IEEE Std 802.15.4, opportunities for broadcasts are limited to specific times and specific channels. Routers in a TSCH network transmit Enhanced Beacon (EB) frames to announce the presence of the network. This document provides a mechanism by which additional information critical for new nodes (pledges) and long-sleeping nodes may be carried within the EB in order to conserve use of broadcast opportunities. 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 https://www.ietf.org/mailman/listinfo/ietf-announce https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist 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