Constrained Application Protocol: Difference between revisions

Revision as of 15:57, 16 September 2011

Revision as of 07:30, 5 December 2011

Line 1:

{{context|date=August 2011}}

'''Constrained Application Protocol''' (CoAP), is aan [[RESTfulApplication layer]] protocol that is intended for use within resource-constrained networksinternet anddevices, such as [[WSN]] nodes. CoAP is designed to easily translatestranslate to [[HTTP]] for simplified integration with the web, while also meeting specialized requirements such as [[multicast]] support, very low overhead, and simplicity for constrained environments.<ref>Constrained Application Protocol (CoAP) draft-shelby-core-coap-07 [https://datatracker.ietf.org/doc/draft-ietf-core-coap/ https://datatracker.ietf.org/doc/draft-ietf-core-coap/]</ref><ref>"[http://hinrg.cs.jhu.edu/joomla/images/stories/IPSN_2011_koliti.pdf Integrating Wireless Sensor Networks with the Web]" , Walter, Colitti 2011</ref>. The InternetMulticast, Engineeringlow Taskoverhead, Forceand simplicity are extremely important for Internet of Things([[IETFIoT]]) Constrainedand RESTful[[M2M]] environmentsdevices, which tend to be deeply ([[CoREEmbedded system|embedded]]) Workingand Grouphave hasmuch doneless thememory majorand standardizationpower worksupply forthan thistraditional protocolinternet devices have. In orderTherefore, toefficiency makeis thevery protocolimportant. suitable toCoAP Internetcan ofrun Things([[IoT]])on andmost M2Mdevices applications,that varioussupport new[[UDP]] functionalitiesor havea beenUDP addedanalogue.

The Internet Engineering Task Force ([[IETF]]) Constrained [[RESTful]] environments ([[CoRE]]) Working Group has done the major standardization work for this protocol. In order to make the protocol suitable to IoT and M2M applications, various new functionalities have been added. This protocol is still under development.

This protocol is still under development.

== Features ==