Subject: [lp-wan] SCHC C implementation

From: Bart Moons <[email-masked]>
Date: Sun, 20 Oct 2019 11:47:34 +0200

Dear Hannes,

Recently we published a paper "Using SCHC for an optimzed protocol stack in multimodal LPWAN solutions" ( http://hdl.handle.net/1854/LU-8613162 ) (http://hdl.handle.net/1854/LU-8613162).
It reviews SCHC compression and fragmentation and compares it to other compression and fragmentation techniques.
I made a C implementation for the compression and the fragmentation and briefly describe my approach in the paper.

I was planning to share the library with the community the coming months, but since you are interested, I can maybe speed up the process.
I'll keep you updated.
Kind regards,
Bart

Bart Moons
Ghent University - imec
IDLab

iGent Tower - Department of Information Technology
Technologiepark-Zwijnaarde 15, B-9052 Ghent, Belgium (https://maps.google.com/?q=Technologiepark-Zwijnaarde%2015%2C%20B-9052%20Ghent%2C%20Belgium)

[email-masked] (mailto:[email-masked]) +32 472 42 23 91 (tel:%20+32%20472%2042%2023%2091)
http://IDLab.UGent.be
http://idlab.technology

On Oct 20 2019, at 8:48 am, [email-masked] wrote:
> Send lp-wan mailing list submissions to
> [email-masked]
>
> To subscribe or unsubscribe via the World Wide Web, visit
> https://www.ietf.org/mailman/listinfo/lp-wan
> or, via email, send a message with subject or body 'help' to
> [email-masked]
>
> You can reach the person managing the list at
> [email-masked]
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of lp-wan digest..."
> Today's Topics:
>
> 1. Re: C Implementation of SCHC ? ([email-masked])
>
> Hello Hannes,
>
> Indeed, I agree that the SCHC acronym is kind of a misnomer.
> SCHC&FR would be technically more accurate, but totally un-pronounceable.
> The common part is SC (Static Context). HC (Header Compression) and FR (Fragmentation/Reassembly) are mostly independent, except they share the same RuleID (name)space.
> > as well as support for reliable transmission of packets.
> Actually, it includes support for reliable transmission of fragments. If the packet is compressed but not fragmented, there Is no reliability mechanism added.
> Unless the implementer decides to use the fragmentation mechanics just for the benefit of reliability, even if fragmentation itself is not required.
> Best regards,
>
> Dominique
>
> De : Hannes Tschofenig <[email-masked] (mailto:[email-masked])>
> Date : Saturday 19 October 2019 18:08
> À : Dominique Barthel <[email-masked] (mailto:[email-masked])>
> Cc : lp-wan <[email-masked] (mailto:[email-masked])>
> Objet : RE: [lp-wan] C Implementation of SCHC ?
>
>
> Thanks, Dominique.
>
> Regarding the implementation question I cannot really help because I don’t know what the RIoT guys are trying to accomplish.
>
> I was actually surprised to see that the work on static header compression is actually much more than compression. It includes a protocol for fragmentation and reassembly as well as support for reliable transmission of packets.
>
> Ciao
> Hannes
>
> From: [email-masked] (mailto:[email-masked]) <[email-masked] (mailto:[email-masked])>
> Sent: Freitag, 18. Oktober 2019 18:11
> To: Hannes Tschofenig <[email-masked] (mailto:[email-masked])>
> Cc: lp-wan <[email-masked] (mailto:[email-masked])>
> Subject: Re: [lp-wan] C Implementation of SCHC ?
>
>
>
>
>
> Hello Hannes,
>
>
> I don't know of a SCHC implementation at this time.
>
> The closest I know to an implementation is the RiOT guys intention of adding SCHC to RioT. AFAIK, they were debating whether to rewrite SCHC in C or run micropython over RioT.
>
>
>
> Regarding papers, I'm aware of a paper being submitted by S. Aguilar et al. (IMT Atlantique, Rennes and UPC, Barcelona) but I'm not sure what its status exactly is.
>
> I'll let the authors come out of the wood.
>
> A quick search on ieeeexplore with the keyword "SCHC" returned two relevant papers (published this summer), YMMV.
>
> What performance are you interested in ? Compression, fragmentation, .. ?
>
>
>
> Best regards
>
>
>
> Dominique
>
>
>
> De : lp-wan <[email-masked] (mailto:[email-masked])> on behalf of Hannes Tschofenig <[email-masked] (mailto:[email-masked])>
> Date : Friday 18 October 2019 16:55
> À : lp-wan <[email-masked] (mailto:[email-masked])>
> Objet : [lp-wan] C Implementation of SCHC ?
>
>
>
>
> Hi all,
>
>
> I was searching for a C implementation of SCHC and only found Python and JavaScript implementations. Can someone send me a pointer to a C implementation?
>
> I also recall a paper being distributed about the performance of SCHC but I cannot find that either. A pointer would be great.
>
> Thanks.
>
> Ciao
> Hannes
> IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Thank you.
> _________________________________________________________________________________________________________________________
>
> 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.
>
> IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Thank you.
>
>
> _________________________________________________________________________________________________________________________
>
> 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.
> _______________________________________________
> lp-wan mailing list
> [email-masked]
> https://www.ietf.org/mailman/listinfo/lp-wan
>