Hi Xavi,
I observed a small typo in section 4.2.10 instead of node it is written as note
I am bit confused with Consitency description in 4.1
You mean to say that the nodes should keep the count for each ADD/DELETE with
the neighbor, does it create problem when a node has multiple neighbors
Is this used for cross checking the schedules after the cell
allocation/deletion process.
Thanks & Regards,
Lijo Thomas
From: 6tisch [mailto:[email protected]] On Behalf Of Xavier Vilajosana
Sent: 26 July 2016 12:02
To: [email protected]
Subject: [6tisch] Fwd: I-D Action: draft-ietf-6tisch-6top-protocol-02.txt
Dear all,
we have submitted a revision of the 6top draft. It includes most of the changes
proposed in the WG meeting in Berlin.
please send us your comments.
kind regards,
Xavi
---------- Forwarded message ----------
From: < <mailto:[email protected]> [email protected]>
Date: 2016-07-26 8:30 GMT+02:00
Subject: [6tisch] I-D Action: draft-ietf-6tisch-6top-protocol-02.txt
To: <mailto:[email protected]> [email protected]
Cc: <mailto:[email protected]> [email protected]
A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the IPv6 over the TSCH mode of IEEE 802.15.4e of
the IETF.
Title : 6top Protocol (6P)
Authors : Qin Wang
Xavier Vilajosana
Filename : draft-ietf-6tisch-6top-protocol-02.txt
Pages : 28
Date : 2016-07-25
Abstract:
This document defines the 6top Protocol (6P), which enables
distributed scheduling in 6TiSCH networks. 6P allows neighbor nodes
in a 6TiSCH network to add/delete TSCH cells to one another. 6P is
part of the 6TiSCH Operation Sublayer (6top), the next higher layer
of the IEEE802.15.4 TSCH medium access control layer. The 6top
Scheduling Function (SF) decides when to add/delete cells, and
triggers 6P Transactions. Several SFs can be defined, each
identified by a different 6top Scheduling Function Identifier (SFID).
This document lists the requirements for an SF, but leaves the
definition of the SF out of scope. Different SFs are expected to be
defined in future companion specifications.
The IETF datatracker status page for this draft is:
<https://datatracker.ietf.org/doc/draft-ietf-6tisch-6top-protocol/>
https://datatracker.ietf.org/doc/draft-ietf-6tisch-6top-protocol/
There's also a htmlized version available at:
<https://tools.ietf.org/html/draft-ietf-6tisch-6top-protocol-02>
https://tools.ietf.org/html/draft-ietf-6tisch-6top-protocol-02
A diff from the previous version is available at:
<https://www.ietf.org/rfcdiff?url2=draft-ietf-6tisch-6top-protocol-02>
https://www.ietf.org/rfcdiff?url2=draft-ietf-6tisch-6top-protocol-02
Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at <http://tools.ietf.org>
tools.ietf.org.
Internet-Drafts are also available by anonymous FTP at:
<ftp://ftp.ietf.org/internet-drafts/> ftp://ftp.ietf.org/internet-drafts/
_______________________________________________
6tisch mailing list
<mailto:[email protected]> [email protected]
<https://www.ietf.org/mailman/listinfo/6tisch>
https://www.ietf.org/mailman/listinfo/6tisch
-------------------------------------------------------------------------------------------------------------------------------
[ C-DAC is on Social-Media too. Kindly follow us at:
Facebook: https://www.facebook.com/CDACINDIA & Twitter: @cdacindia ]
This e-mail is for the sole use of the intended recipient(s) and may
contain confidential and privileged information. If you are not the
intended recipient, please contact the sender by reply e-mail and destroy
all copies and the original message. Any unauthorized review, use,
disclosure, dissemination, forwarding, printing or copying of this email
is strictly prohibited and appropriate legal action will be taken.
-------------------------------------------------------------------------------------------------------------------------------
_______________________________________________
6tisch mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/6tisch
