Re: [6tisch] 6P and Sf0 issue: Token to identify transactions in 6P

Tero Kivinen <> Mon, 07 March 2016 13:24 UTC

Return-Path: <>
Received: from localhost ( []) by (Postfix) with ESMTP id 1094C1B40CB for <>; Mon, 7 Mar 2016 05:24:28 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: 0.778
X-Spam-Status: No, score=0.778 tagged_above=-999 required=5 tests=[BAYES_20=-0.001, SPF_NEUTRAL=0.779] autolearn=no
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id VWe5L1Vw4HHo for <>; Mon, 7 Mar 2016 05:24:26 -0800 (PST)
Received: from ( []) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 109681B40C9 for <>; Mon, 7 Mar 2016 05:24:25 -0800 (PST)
Received: from (localhost []) by (8.15.2/8.14.8) with ESMTPS id u27DOEFB000742 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Mon, 7 Mar 2016 15:24:14 +0200 (EET)
Received: (from kivinen@localhost) by (8.15.2/8.14.8/Submit) id u27DODM0020807; Mon, 7 Mar 2016 15:24:13 +0200 (EET)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-ID: <>
Date: Mon, 7 Mar 2016 15:24:13 +0200
From: Tero Kivinen <>
To: "Pascal Thubert \(pthubert\)" <>
In-Reply-To: <>
References: <> <> <> <> <>
X-Mailer: VM 8.2.0b under 24.5.1 (x86_64--netbsd)
X-Edit-Time: 3 min
X-Total-Time: 2 min
Archived-At: <>
Cc: "" <>, "Prof. Diego Dujovne" <>, Tengfei Chang <>
Subject: Re: [6tisch] 6P and Sf0 issue: Token to identify transactions in 6P
X-Mailman-Version: 2.1.15
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: Mon, 07 Mar 2016 13:24:28 -0000

Pascal Thubert (pthubert) writes:
> But if the ack is sent and not received then the parent does not
> allocate the cells and the child uses them...

And ACK only tells you that the frame was received, it does NOT mean
that the frame was processed. I.e. the recipient end might send an
ACK, and then send the frame to the upper layer, but if there is not
enough buffer space available there, it might drop it before it
actually reaches the upper layer.

So do not use ACK for anything else than indication that there is no
need to retransmit this frame anymore as other end already received it
(altough it might have dropped it after that, but retransmissions does
not help with that).