Constrained Application Protocol: Difference between revisions

Revision as of 20:53, 23 July 2012

Revision as of 22:36, 1 August 2012

Line 2:

{{IP stack}}

'''Constrained Application Protocol''' (CoAP) is an [[Application layer]] protocol that is intended for use in resource-constrained internet devices, such as [[WSN]] nodes. CoAP is designed to easily translate to [[HTTP]] for simplified integration with the web, while also meeting specialized requirements such as [[multicast]] support, very low overhead, and simplicity.<ref>[https://datatracker.ietf.org/doc/draft-ietf-core-coap Internet Draft describing Constrained Application Protocol (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> Multicast, low overhead, and simplicity are extremely important for [[Internet of Things]] (IoT) and [[Machine-to-Machine|M2M]] (M2M) devices, which tend to be deeply [[Embedded system|embedded]] and have much less memory and power supply than traditional internet devices have. Therefore, efficiency is very important. CoAP can run on most devices that support [[User Datagram Protocol|UDP]] or a UDP analogue.