[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#774928: ITP: libcoap -- library for the CoAP protocol written in C



Package: wnpp
Severity: wishlist
Owner: Carsten Schoenert <c.schoenert@t-online.de>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

* Package name    : libcoap
  Version         : 4.1.1
  Upstream Author : Olaf Bergmann <bergmann@tzi.org>
* URL             : http://sourceforge.net/projects/libcoap/
* License         : GPL2+ and BSD
  Programming Lang: C
  Description     : C Library Implementation of CoAP

The libcoap is basically a C implementation of the IETF CoAP
(Constrained Application Protocol). The CoAP protocol is major
standardized by the IETF in the RFC 7252 and is a application layer
protocol for low power devices for the Internet of Things (IoT) and 
Machine to Machine (M2M) communication.

CoAP is mostly used in 6loWPAN environments. The libcoap library
provides functions to talk to such devices and makes it possible to
interact with low power IPv6 based devices.

There are some other frameworks written in Java, Python or JavaScript
that implement CoAP bindings. As far as I know there is nothing yet
packaged for the use of the CoAP protocol. That's the main reason why
I want to package and maintain the libcoap package.

Currently the upstream source is lacking some minor tweaks like
versioning of the library and also symbol versioning. The build
environment is improvable. I'm in contact with Olaf Bergmann to improve
the situation here. He is willing to take some external hints and work
so after tuning the build process it will be easier to package the 
libcoap.

I don't need a sponsor, happily Guido Guenther is willing to upload the 
package after checking my work.

http://coap.technology/
http://www.ietf.org/rfc/rfc7252.txt
http://6lowapp.net/

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1

iQIcBAEBCAAGBQJUr5JGAAoJEIMBYBQlHR2wlWQQAJVL/LoGm2vUQp4V79mMpiLP
o3Dj3/cv73iAn4FWPDOoXdK7ic7OdA3u36nllYdYhMQGak2pNFtxe+foBGDxmISt
3I7cpolX8qmej+zOLb64aZ0XGRwjolXM5ZppID8aXpRHPWm0JPNEovyOqY83T33C
6qRJ3c96TuDN3Xn+k0oYW9uVRI5WwvtQfyUUk6A27gnPUnxaiq2jBJkYOWaS5mvu
AlRExGj/koouB0k+C2VHfq6HYQd3JoS/suxYjWJC/PIRaO7HRiR87iHFxwsI39xl
VsozSUzHw3WE+FcxC8aPmnrfFSMA65UgYtkjmgdv9JokT4r9hL3xB/n28ZS0XeZK
7Plr7yRYg1SzmYnjb2U4lCVkDwfCo32MQ+e5DdDE2dbDl3XOwnZ9RIXU812CzUoV
nz+zdIvGhnwPSa+lahTXDGDENYGuPkhA46qqd3q7kVlRvEgECOo0XYe/0cjsrAnl
C8ZX11RyAc2cvB+1pOFUb7ZOfmWzJI8L4m9UBkPjFL5kmSDoY1K/tJtOv7uycb9I
xhUv8IsIaJusQSVlNyQeXFQ2Daq7JzilKC9L2Q3A2qRlQXtTAgtaLp5Rqrnoe9iQ
XiQDa2iPpDUOR0j38oaT8wVpbzpgACPpPUIu2oDek3ugGRTWTfpaa5ZoweZ5qZPA
tlH+sxDm9fNoyU3+o2Fp
=cGu7
-----END PGP SIGNATURE-----


Reply to: