[6tisch] RFC 8480 on 6TiSCH Operation Sublayer (6top) Protocol (6P)
rfc-editor@rfc-editor.org Mon, 05 November 2018 04:44 UTC
Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: 6tisch@ietfa.amsl.com
Delivered-To: 6tisch@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DDF13130DC5; Sun, 4 Nov 2018 20:44:49 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.201
X-Spam-Level:
X-Spam-Status: No, score=-4.201 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-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 Mv88-ZOy3trL; Sun, 4 Nov 2018 20:44:47 -0800 (PST)
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 8CC74128BCC; Sun, 4 Nov 2018 20:44:47 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 30) id 7DA09B815E3; Sun, 4 Nov 2018 20:44:34 -0800 (PST)
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
Cc: rfc-editor@rfc-editor.org, drafts-update-ref@iana.org, 6tisch@ietf.org
Content-type: text/plain; charset="UTF-8"
Message-Id: <20181105044434.7DA09B815E3@rfc-editor.org>
Date: Sun, 04 Nov 2018 20:44:34 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/6tisch/ukMkDMkc2Q9OO1rQcX-8HYBhwk0>
Subject: [6tisch] RFC 8480 on 6TiSCH Operation Sublayer (6top) Protocol (6P)
X-BeenThere: 6tisch@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Discuss link layer model for Deterministic IPv6 over the TSCH mode of IEEE 802.15.4e, and impacts on RPL and 6LoWPAN such as resource allocation" <6tisch.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/6tisch>, <mailto:6tisch-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/6tisch/>
List-Post: <mailto:6tisch@ietf.org>
List-Help: <mailto:6tisch-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/6tisch>, <mailto:6tisch-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 05 Nov 2018 04:44:50 -0000
A new Request for Comments is now available in online RFC libraries.
RFC 8480
Title: 6TiSCH Operation Sublayer (6top) Protocol (6P)
Author: Q. Wang, Ed.,
X. Vilajosana,
T. Watteyne
Status: Standards Track
Stream: IETF
Date: November 2018
Mailbox: wangqin@ies.ustb.edu.cn,
xvilajosana@uoc.edu,
thomas.watteyne@analog.com
Pages: 50
Characters: 107695
Updates/Obsoletes/SeeAlso: None
I-D Tag: draft-ietf-6tisch-6top-protocol-12.txt
URL: https://www.rfc-editor.org/info/rfc8480
DOI: 10.17487/RFC8480
This document defines the "IPv6 over the TSCH mode of IEEE 802.15.4e"
(6TiSCH) Operation Sublayer (6top) Protocol (6P), which enables
distributed scheduling in 6TiSCH networks. 6P allows neighbor nodes
to add/delete Time-Slotted Channel Hopping (TSCH) cells to/on one
another. 6P is part of the 6TiSCH Operation Sublayer (6top), the
layer just above the IEEE Std 802.15.4 TSCH Medium Access Control
layer. 6top is composed of one or more Scheduling Functions (SFs)
and the 6top Protocol defined in this document. A 6top SF decides
when to add/delete cells, and it triggers 6P Transactions. The
definition of SFs is out of scope for this document; however, this
document provides the requirements for an SF.
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