Re: [Lake] LoRaWAN use case; Re: WGLC for draft-ietf-lake-reqs-01

[[e-mail]]

Hello Göran, all

(not sure anymore how I should write my answer)

>So, the current benchmark and available data points are all compliant with your challenge.
The numbers you provide indeed seem pretty much inline with the challenge I proposed, and I'll keep checking them as the WG progresses.
However, lets not be said that my challenge mandates the solution you propose (3 flights and 1 message per packet at SF12).
In draft-ietf-lake-reqs-02, the justification for 3 flights is Section 2.10.4, which I find kind of hand-wavy. (e.g., one could provide a similarly-hand-wavy counter argument to the 2*60 bytes vs. 3*40 bytes discussion: a shorter frame is less likely to suffer collision).

My point starting this discussion was to mention the 1 hour delay step effect as a transmitter reaches 36 s of air-time, which is not accurately reflected in column G of your spreadsheet and in the requirements draft.

> I think a benchmark should include all messages of the AKE and I would propose that we don’t formulate it in terms of uplink/downlink.
As much as I would love a general benchmark, I think LoRaWAN is very much an asymmetrical network and we need to acknowledge this fact.
I think it would do the LoRaWAN community a real service if we expressed the LAKE benchmark as two distinct cases : device-initiated AKE and infrastructure-initiated AKE. This would make it easier to map results onto real deployment cases.

Best regards,

Dominique

_________________________________________________________________________________________________________________________

Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration,
Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci.

This message and its attachments may contain confidential or privileged information that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and delete this message and its attachments.
As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified.
Thank you.