[rfc-dist] RFC 9033 on 6TiSCH Minimal Scheduling Function (MSF)
rfc-editor@rfc-editor.org Sun, 30 May 2021 04:25 UTC
Return-Path: <rfc-dist-bounces@rfc-editor.org>
X-Original-To: ietfarch-rfc-dist-archive@ietfa.amsl.com
Delivered-To: ietfarch-rfc-dist-archive@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A1C773A2D9F for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Sat, 29 May 2021 21:25:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.899
X-Spam-Level:
X-Spam-Status: No, score=-2.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, MAILING_LIST_MULTI=-1, 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 4npHZ1aixRWU for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Sat, 29 May 2021 21:25:17 -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 8F96B3A2DDD for <rfc-dist-archive-yuw6Xa6hiena@ietf.org>; Sat, 29 May 2021 21:25:09 -0700 (PDT)
Received: from rfcpa.amsl.com (localhost [IPv6:::1]) by rfc-editor.org (Postfix) with ESMTP id 8A2CFF4073E; Sat, 29 May 2021 21:24:52 -0700 (PDT)
X-Original-To: rfc-dist@rfc-editor.org
Delivered-To: rfc-dist@rfc-editor.org
Received: by rfc-editor.org (Postfix, from userid 30) id 43B96F4073A; Sat, 29 May 2021 21:24:52 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Message-Id: <20210530042452.43B96F4073A@rfc-editor.org>
Date: Sat, 29 May 2021 21:24:52 -0700
Subject: [rfc-dist] RFC 9033 on 6TiSCH Minimal Scheduling Function (MSF)
X-BeenThere: rfc-dist@rfc-editor.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: RFC Announcements <rfc-dist.rfc-editor.org>
List-Unsubscribe: <https://www.rfc-editor.org/mailman/options/rfc-dist>, <mailto:rfc-dist-request@rfc-editor.org?subject=unsubscribe>
List-Archive: <http://www.rfc-editor.org/pipermail/rfc-dist/>
List-Post: <mailto:rfc-dist@rfc-editor.org>
List-Help: <mailto:rfc-dist-request@rfc-editor.org?subject=help>
List-Subscribe: <https://www.rfc-editor.org/mailman/listinfo/rfc-dist>, <mailto:rfc-dist-request@rfc-editor.org?subject=subscribe>
Cc: drafts-update-ref@iana.org, 6tisch@ietf.org, rfc-editor@rfc-editor.org
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
Errors-To: rfc-dist-bounces@rfc-editor.org
Sender: rfc-dist <rfc-dist-bounces@rfc-editor.org>
A new Request for Comments is now available in online RFC libraries.
RFC 9033
Title: 6TiSCH Minimal Scheduling Function (MSF)
Author: T. Chang, Ed.,
M. Vučinić,
X. Vilajosana,
S. Duquennoy,
D. Dujovne
Status: Standards Track
Stream: IETF
Date: May 2021
Mailbox: tengfei.chang@gmail.com,
malisa.vucinic@inria.fr,
xvilajosana@uoc.edu,
simon.duquennoy@gmail.com,
diego.dujovne@mail.udp.cl
Pages: 20
Updates/Obsoletes/SeeAlso: None
I-D Tag: draft-ietf-6tisch-msf-18.txt
URL: https://www.rfc-editor.org/info/rfc9033
DOI: 10.17487/RFC9033
This specification defines the "IPv6 over the TSCH mode of IEEE
802.15.4" (6TiSCH) Minimal Scheduling Function (MSF). This Scheduling
Function describes both the behavior of a node when joining the
network and how the communication schedule is managed in a
distributed fashion. MSF is built upon the 6TiSCH Operation Sublayer
Protocol (6P) and the minimal security framework for 6TiSCH.
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
_______________________________________________
rfc-dist mailing list
rfc-dist@rfc-editor.org
https://www.rfc-editor.org/mailman/listinfo/rfc-dist
http://www.rfc-editor.org