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

["Lijo Thomas" <[e-mail]>]

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 [mailto:[e-mail]] On Behalf Of Prof. Diego Dujovne
Sent: 03 March 2016 21:11
To: [e-mail]
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

exchange:

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?

Regards,

                                Diego Dujovne


-- 

DIEGO DUJOVNE
Académico Escuela de Ingeniería en Informática y Telecomunicaciones
Facultad de Ingeniería UDP
www.ingenieria.udp.cl <http://www.ingenieria.udp.cl> 
(56 2) 676 8125


-------------------------------------------------------------------------------------------------------------------------------
[ 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.
-------------------------------------------------------------------------------------------------------------------------------