Constrained Application Protocol: Difference between revisions

Content deleted Content added
Update status of standardization process
Line 5:
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) 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.
 
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.<ref>[https://datatracker.ietf.org/wg/core/ The CORE WG's IETF Area]</ref> ThisThe protocol has completed IETF last call and is stillin the final stages of processing for Internet underStandards developmentdocuments.
 
== Features ==