Revision as of 20:46, 23 August 2011 edit KuduIO (talk \| contribs) Extended confirmed users, Pending changes reviewers, Rollbackers 4,362 edits Cleanup following AFC creation ← Previous edit		Revision as of 13:15, 24 August 2011 edit undo Scottywong (talk \| contribs) Extended confirmed users 26,031 edits Added {{context}} tag to article Next edit →
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-00[http://tools.ietf.org/id/draft-shelby-core-coap-00.txt http://tools.ietf.org/id/draft-shelby-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.

Constrained Application Protocol: Difference between revisions