Re: [6tisch] 6P and Sf0 issue: Piggybacking data packet with IE confirmation

"Pascal Thubert (pthubert)" <> Wed, 09 March 2016 17:33 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id B505F12D7EA for <>; Wed, 9 Mar 2016 09:33:25 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -14.521
X-Spam-Status: No, score=-14.521 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: (amavisd-new); dkim=pass (1024-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id IJrVxUh-Dzrm for <>; Wed, 9 Mar 2016 09:33:23 -0800 (PST)
Received: from ( []) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 267B012D5BE for <>; Wed, 9 Mar 2016 09:33:23 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple;;; l=53142; q=dns/txt; s=iport; t=1457544803; x=1458754403; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=fmnF0VVhczosUI1s1/Sl1DnAFdr1t9K2/72rctigRcQ=; b=QLkyY89zqm6Bu+2Zi/9/Kr3d8bO/dZi6Rbj6Sy9DTRcEB8YoYYtruBxI eBGTCJnCn1TZvaDHA4UYEWySiJqRVsdZDKfW9r1w+U/PbD1wILR9uKAHx R1saAUm1wr3y4Dlv2GNF0tIm/hMp82qCI9ImE92jqllpCYt9duJq53Q2y k=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-AV: E=Sophos; i="5.24,311,1454976000"; d="scan'208,217"; a="81269988"
Received: from ([]) by with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 09 Mar 2016 17:33:21 +0000
Received: from ( []) by (8.14.5/8.14.5) with ESMTP id u29HXLt6025068 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Wed, 9 Mar 2016 17:33:21 GMT
Received: from ( by ( with Microsoft SMTP Server (TLS) id 15.0.1104.5; Wed, 9 Mar 2016 11:33:21 -0600
Received: from ([]) by ([]) with mapi id 15.00.1104.009; Wed, 9 Mar 2016 11:33:21 -0600
From: "Pascal Thubert (pthubert)" <>
To: Qin Wang <>
Thread-Topic: [6tisch] 6P and Sf0 issue: Piggybacking data packet with IE confirmation
Thread-Index: AQHReiDuK9fwYa3pDkezL/WAa3lIGZ9RXXCw
Date: Wed, 9 Mar 2016 17:33:18 +0000
Deferred-Delivery: Wed, 9 Mar 2016 17:32:42 +0000
Message-ID: <>
References: <> <>
In-Reply-To: <>
Accept-Language: fr-FR, en-US
Content-Language: en-US
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: []
Content-Type: multipart/alternative; boundary="_000_e1382254e0c6471a8b3b5921c87ccad7XCHRCD001ciscocom_"
MIME-Version: 1.0
Archived-At: <>
Cc: Lijo Thomas <>, "" <>, "Prof. Diego Dujovne" <>
Subject: Re: [6tisch] 6P and Sf0 issue: Piggybacking data packet with IE confirmation
X-Mailman-Version: 2.1.17
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" <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Wed, 09 Mar 2016 17:33:26 -0000

With this method, Qin:

Step 1 is performed once and that’s probably it for life unless the child needs more than 16 cells; Step 2 is really the add/delete flow.

Child says “add 3” and the parent responds with the bitmap with 3 more bits set. If the child does not see the response it may say “add 0” and get the bitmap from the parent perspective, with either no additional bit if the request was lost or the expected 3 more bits if the response was lost.

This approach removes the need for transactionality. The parent may opportunistically / periodically resend the bitmap to the child just to make sure the child has the correct view.



From: Qin Wang []
Sent: mercredi 9 mars 2016 17:30
To: Pascal Thubert (pthubert) <>
Cc: Lijo Thomas <>in>; Prof. Diego Dujovne <>cl>;
Subject: Re: [6tisch] 6P and Sf0 issue: Piggybacking data packet with IE confirmation

Hi Pascal,

I want confirm what I understood.
(1) Both step1 and step2 are extra message besides ADD/DELETE message exchange
(2) Because the step1 and step2, Child will know which cells it can use. Then, when the child wants more cells,  the child selects the cells from those set as UNUSED in the bitmap, as candidates, and send ADD request to parent. And the parent will send Response to confirm. That is 2-stages, instead of 3-stages message exchange.


On Wednesday, March 9, 2016 3:05 AM, Pascal Thubert (pthubert) <<>> wrote:

Hello Qin:

Please consider the message by Tero.

The ack is Mac-layer before upper layer processing and does not guarantee success in the stack.

What we'd really want is suppress the MAC layer ack but not the 6P response.

Another angle (for the sake of making sure we left no stone unturned).

If we think transactionality is too difficult to achieve and that parent/child may lose sync: it is possible to avoid the issues with transactionality by using a bitmap to represent cells like LoRa does with frequencies.

Step 1 the parent provides a list of cells (say 16) that it may allocate to that child in the future. The list may differ per child and may overlap with other children to enable to parent to temporarily give a cell to one child or another.

Step 2 (runtime) the parent sends the bitmap of the cells, bit set if the cell is use child to parent. If this is sent regularly like a frame relay full status, things will eventually sync.

What do you think?


Le 8 mars 2016 à 22:34, Qin Wang <<>> a écrit :
Hi Diego,

I also have question regarding to the third message, i.e. Child acknowledge.

In this case, the Child must accept the selected cells in the Parent's message if it received the message. Right? In another word, if the Parent knows the Child has received the message correctly, the Parent can be sure that the selected cells will be added/deleted into/from the Child's schedule. Since the MAC layer ACK can tell Parent the Child has received its message correctly, I think there is no need for the Child to send back the 6P layer Acknowledgement.

Do I miss something?


On Friday, March 4, 2016 7:51 AM, Lijo Thomas <<>> wrote:

Hi Diego,

Do we really require 3 transactions for 6P operations as mentioned.

The second transaction from the parent contains all the required information  for the task.

In case the 2nd packet is lost, the parent will schedule a RX link which will be unutilized for the time being and can be reallocated depending on the scheduling function.

But if the 3rd transaction is lost, the client will allocate the TX link  and will start transmitting packets.

So can we avoid the ACK packet(3rd transaction) from the client, or is there any added benefit.

Thanks & Regards,
Lijo Thomas

From: 6tisch [] On Behalf Of Prof. Diego Dujovne
Sent: 03 March 2016 21:11
Subject: [6tisch] 6P and Sf0 issue: Piggybacking data packet with IE confirmation

Dear all,
            Given that there is parent preference in cell
selection, a child-initiated transaction triggers a three-step
1- Child sends request to Parent with whitelist/blacklist of slotoffsets
2- Parent selects cells
3- Child acknowledges and finishes the transaction
The main idea is to enable an optional Piggybacking of the IE on a
data packet to reduce the number of transmitted packets, but there
are latency concerns when the (data) traffic is low.
Is it worth to enable this option given the added complexity?
                                Diego Dujovne

Académico Escuela de Ingeniería en Informática y Telecomunicaciones
Facultad de Ingeniería UDP<>
(56 2) 676 8125

[ C-DAC is on Social-Media too. Kindly follow us at:
Facebook: & 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<>

6tisch mailing list<>