Sure, Tero;
But this is another discussion entirely. It is about the transaction that associates new timeslots to a bundle and why we need a correlator, or transaction ID. I was explaining that if the parent wait for the ack to allocate a slot that was negotiated, and there is no flow after that, then if the ack is lost the child thinks the slot is allocated and the parent does not. The child may start using it wrongly. The point behind this is that if the transaction does not complete, it must be retried from scratch with the same sequence, or it must time out and roll back. Cheers, Pascal > -----Original Message----- > From: Tero Kivinen [mailto:[email protected]] > Sent: lundi 7 mars 2016 14:24 > To: Pascal Thubert (pthubert) <[email protected]> > Cc: Tengfei Chang <[email protected]>; [email protected]; Prof. Diego > Dujovne <[email protected]> > Subject: Re: [6tisch] 6P and Sf0 issue: Token to identify transactions in 6P > > 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). > -- > [email protected] _______________________________________________ 6tisch mailing list [email protected] https://www.ietf.org/mailman/listinfo/6tisch
