Constrained Application Protocol: Difference between revisions

Revision as of 08:01, 27 August 2011

Revision as of 17:07, 1 September 2011

Line 1:

{{context|date=August 2011}}

'''Constrained Application Protocol''' (CoAP), is a RESTful protocol for use with constrained networks and nodes. CoAP easily translates to [[HTTP]] for integration with the web while meeting specialized requirements such as multicast support, very low overhead and simplicity for constrained environments.<ref>Constrained Application Protocol (CoAP) draft-shelby-core-coap-0007 [httphttps://toolsdatatracker.ietf.org/iddoc/draft-shelbyietf-core-coap-00.txt/ httphttps://toolsdatatracker.ietf.org/iddoc/draft-shelbyietf-core-coap-00.txt/]</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 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 Internet of Things([[IoT]]) and M2M applications, various new functionalities have been added.

This protocol is still under development.