https://elvis.hcw.ac.at/wiki/api.php?action=feedcontributions&feedformat=atom&user=Ograsl 2026-09-10T19:42:45Z User contributions MediaWiki 1.41.5 https://elvis.hcw.ac.at/wiki/index.php?title=Constrained_Application_Protocol&diff=1349 2019-04-04T16:36:16Z

<p>Ograsl: </p> <hr /> <div>The '''Constrained Application Protocol''' ('''CoAP''') is a specialized web transfer protocol, as defined in RFC 7252, for use with constrained nodes and constrained networks in the Internet of Things.<br /> The protocol is designed for machine-to-machine (M2M) applications such as smart energy and building automation.<br /> <br /> == Features ==<br /> <br /> The work on Constrained Environments aims at realizing the REST architecture in a suitable form for the most constrained nodes and networks. The nodes usually consist of 8-bit microcontrollers with limited amounts of RAM and ROM.<br /> <br /> <br /> CoAP has the following main features:<br /> <br /> * Web protocol fulfilling M2M requirements in constrained environments<br /> * UDP [RFC0768] binding with optional reliability supporting unicast and multicast requests<br /> * Asynchronous message exchanges<br /> * Low header overhead and parsing complexity<br /> * URI and Content-type support<br /> * Simple proxy and caching capabilities<br /> * Stateless HTTP mapping<br /> * Security binding to Datagram Transport Layer Security (DTLS)<br /> <br /> == The Protocol ==<br /> <br /> CoAP is similar to the client/server model of HTTP. M2M interactions typically result in a CoAP implementation acting in both client and server roles. A request is sent by a client to request an action on a resource (identified by a URI) on a server. The server then sends a response with a response code (equivalent to that of HTTP). Therefore, efficiency is very important, so CoAP uses UDP, a datagram-oriented transport.<br /> <br /> CoAP is however a single protocol, with messaging and request/response as just features of the CoAP header<br /> <br /> +----------------------+<br /> | Application |<br /> +----------------------+<br /> +----------------------+ \<br /> | Requests/Responses | |<br /> |----------------------| | CoAP<br /> | Messages | |<br /> +----------------------+ /<br /> +----------------------+<br /> | UDP |<br /> +----------------------+<br /> <br /> == Message Format ==<br /> <br /> By default, the messages are encoded in a simple binary format and transported over UDP. The message format starts with a fixed-size 4-byte header, followed by a variable-length Token value, which can be between 0 and 8 bytes long. Following the Token value comes a sequence of zero or more CoAP Options in Type-Length-Value (TLV) format, optionally followed by a payload that takes up the rest of the datagram.<br /> <br /> 0 1 2 3<br /> 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1<br /> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<br /> |Ver| T | TKL | Code | Message ID |<br /> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<br /> | Token (if any, TKL bytes) ...<br /> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<br /> | Options (if any) ...<br /> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<br /> |1 1 1 1 1 1 1 1| Payload (if any) ...<br /> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<br /> <br /> ;Version (Ver) (2 bits)<br /> :Indicates the CoAP Version number. This must set this field to 1 (binary 01). Other values are reserved for future versions.<br /> <br /> ;Type (T) (2 bits)<br /> :Indicates if this message is of type Confirmable (0), Non-confirmable (1), Acknowledgement (2), or Reset (3).<br /> <br /> ;Token Length (TKL) (4 bits)<br /> :Indicates the length of the variable-length Token field, which may be 0-8 bytes in length.<br /> <br /> ;CoAP Request/Response Code (8 bits)<br /> :Splits into a 3-bit class and 5-bit detail.<br /> <br /> ;Message ID (16 bits)<br /> :Used to detect message duplication and to match messages of type Acknowledgement/Reset to messages of type Confirmable/Non-confirmable.<br /> <br /> == Security Considerations ==<br /> <br /> This section list some possible threats to the protocol. As CoAP realizes a subset of the features of HTTP/1.1, the security considerations in section 15 of RFC2616 are also pertinent to CoAP.<br /> <br /> ;Parsing the Protocol and Processing URI's<br /> <br /> The URI processing code in CoAP is likely to be a large source of vulnerabilities and should be implemented very carefully. Vulnerabilities include remotely crashing a node and remotely executing arbitrary code. CoAP aims to reduce the risk of these vulnerabilities by reducing parser complexity and moving much of the URI processing to the clients.<br /> <br /> ;Proxying and Caching<br /> <br /> Proxies are man-in-the-middle by their nature. They can break any IPsec or DTLS protection that would otherwise happen between direct CoAP message exchange. Risks include the loss of confidentiality and availability. If the proxies also cache the threat to confidentiality and integrity of request/response data is amplified as CoAP does not implement cache-suppressing Cache-control as in HTTP/1.1.<br /> For caching implementations any access control considerations also need to be applied to the value in the cache. A caching proxy must not make cache values available to requests that have lesser transport-security properties.<br /> <br /> ;Risk of Amplification<br /> <br /> As CoAP server reply to request packets with response packets that may be significantly larger an attacker can use CoAP nodes to generate more traffic and use them in a denial-of-service(DoS) attack. Turning a small attack packet into a larger one is called amplification. The attacker wants to overload a victim but is limited in the amount of traffic can use amplification to generate larger amounts. If a node that enables NoSec access becomes available to an attacker it can access victims on the general internet. UDP provides no way to verify the source address given in the request packet and an attacker can place the IP of the victim in the source address of a request packet to generate a larger packet directed at the victim. The risk is reduced however as constrained networks are only able to generate small amounts of traffic. In contrast the network itself with its limited capacity is a viable victim of an amplification attack. Large amplification factors should not be provided if the request is not authenticated. Also the slicing/blocking modes of CoAP [BLOCK] should be used for large resources.<br /> <br /> <br /> ;IP Address Spoofing<br /> <br /> <br /> <br /> ;Cross-Protocol Attacks<br /> <br /> <br /> <br /> ;Constrained Node Considerations<br /> <br /> Keys should be generated externally and added to the device during manufacturing or commissioning. Due to low processing power constrained nodes are susceptible to timing attacks. Cryptographic principles should be implemented with special care as many nodes are installed in exposed environments and have little resistance to tampering. The scope of credentials assigned to them should be considered carefully. A shared key assigned to a group of nodes may make any single node a target for subverting the entire group.<br /> <br /> == Implementations ==<br /> <br /> Generic implementations are becoming available for a variety of platforms. Implementations for constrained devices are typically written in C. CoAP is also used between them and more powerful systems such as cloud servers, home centrals, smartphones:<br /> <br /> {| class=&quot;wikitable sortable&quot;<br /> |-<br /> ! Name !! Programming Language !! Client/Server !! License !! Link<br /> |-<br /> | Erbium for Contiki || C || Client + Server || 3-clause BSD || http://www.contiki-os.org/<br /> |-<br /> | libcoap || C || Client + Server || BSD/GPL || https://libcoap.net/<br /> |-<br /> | Eclipse tinydtls || C || Client + Server || EPL+EDL || https://projects.eclipse.org/projects/iot.tinydtls<br /> |-<br /> | LibNyoci || C || Client + Server || MIT || https://github.com/darconeous/libnyoci<br /> |-<br /> | microcoap || C || Client + Server || MIT || https://github.com/1248/microcoap<br /> |-<br /> | cantcoap || C++/C || Client + Server || BSD || https://github.com/staropram/cantcoap<br /> |-<br /> | Lobaro CoAP || C || Client + Server || MIT || https://www.lobaro.com/portfolio/lobaro-coap/<br /> |-<br /> | MR-CoAP || Java || || BSD || https://github.com/MR-CoAP/CoAP<br /> |-<br /> | Wakaama || C || Client + Server || EPL+EDL || https://www.eclipse.org/wakaama/index.html<br /> |-<br /> | coap-node || Javascript || Client || MIT || https://github.com/PeterEB/coap-node<br /> |-<br /> | coap-shepherd || Javascript || Server || MIT || https://github.com/PeterEB/coap-shepherd<br /> |-<br /> | Californium || Java || Client + Server || EPL+EDL || https://www.eclipse.org/californium<br /> |-<br /> | nCoap || Java || Client + Server || BSD || https://github.com/okleine/nCoAP<br /> |-<br /> | leshan || Java || Client + Server || EPL+EDL || https://github.com/eclipse/leshan<br /> |-<br /> | CoAP.NET || C# || Client + Server || 3-clause BSD || https://github.com/smeshlink/CoAP.NET<br /> |-<br /> | CoAPSharp || C#, .NET || Client + Server || LGPL || http://www.coapsharp.com<br /> |-<br /> | Waher.Networking.CoAP || C# || Server || || https://github.com/PeterWaher/IoTGateway<br /> |-<br /> | gen_coap || Erlang || Client + Server || MPL v1.1 || https://github.com/gotthardp/gen_coap<br /> |-<br /> | go-coap || Go || Client + Server || MIT || https://github.com/go-ocf/go-coap<br /> |-<br /> | node-coap || Javascript || Client + Server || MIT || https://github.com/mcollina/node-coap<br /> |-<br /> | coap-cli || Javascript || || MIT || https://github.com/mcollina/coap-cli<br /> |-<br /> | txThings || Python (Twisted) || Client + Server || MIT || https://github.com/mwasilak/txThings<br /> |-<br /> | aiocoap || Python 3 || Client + Server || MIT || https://github.com/chrysn/aiocoap<br /> |-<br /> | CoAPthon || Python || Client + Server || MIT || https://github.com/Tanganelli/CoAPthon<br /> |-<br /> | Ruby coap || Ruby || Client || MIT || https://github.com/nning/coap<br /> |-<br /> | Ruby david || Ruby || Server || MIT || https://github.com/nning/david<br /> |-<br /> | coap-rs || Rust || Client + Server || MIT || https://github.com/Covertness/coap-rs<br /> |-<br /> | Copper || JavaScript (Browser Plugin) || Client || BSD || https://github.com/mkovatsc/Copper<br /> |-<br /> | iCoAP || Objective-C || Client || MIT || https://github.com/stuffrabbit/iCoAP<br /> |-<br /> | SwiftCoAP || Swift || Client + Server || MIT || https://github.com/stuffrabbit/SwiftCoAP<br /> |-<br /> | nCoap || Java || Client + Server || BSD || https://github.com/okleine/nCoAP<br /> |-<br /> | txThings || Python (Twisted) || Client + Server || MIT || https://github.com/mwasilak/txThings<br /> |}<br /> <br /> == Courses ==<br /> <br /> * [[Vertiefendes Wahlfach-Projekt]] (2018)<br /> * [[CoAP Chat Application for RIOT OS]]<br /> <br /> == References ==<br /> * RFC 7252: https://tools.ietf.org/html/rfc7252<br /> * RFC 2616: https://www.ietf.org/rfc/rfc2616.txt<br /> * CoAP: RFC 7252 Constrained Application Protocol https://coap.technology/<br /> * Learning Internet of Things: https://www.oreilly.com/library/view/learning-internet-of/9781783553532/<br /> <br /> [[Category:Basic]]</div>

Ograsl https://elvis.hcw.ac.at/wiki/index.php?title=Constrained_Application_Protocol&diff=1348 2019-04-04T16:35:17Z

<p>Ograsl: </p> <hr /> <div>The '''Constrained Application Protocol''' ('''CoAP''') is a specialized web transfer protocol, as defined in RFC 7252, for use with constrained nodes and constrained networks in the Internet of Things.<br /> The protocol is designed for machine-to-machine (M2M) applications such as smart energy and building automation.<br /> <br /> == Features ==<br /> <br /> The work on Constrained Environments aims at realizing the REST architecture in a suitable form for the most constrained nodes and networks. The nodes usually consist of 8-bit microcontrollers with limited amounts of RAM and ROM.<br /> <br /> <br /> CoAP has the following main features:<br /> <br /> * Web protocol fulfilling M2M requirements in constrained environments<br /> * UDP [RFC0768] binding with optional reliability supporting unicast and multicast requests<br /> * Asynchronous message exchanges<br /> * Low header overhead and parsing complexity<br /> * URI and Content-type support<br /> * Simple proxy and caching capabilities<br /> * Stateless HTTP mapping<br /> * Security binding to Datagram Transport Layer Security (DTLS)<br /> <br /> == The Protocol ==<br /> <br /> CoAP is similar to the client/server model of HTTP. M2M interactions typically result in a CoAP implementation acting in both client and server roles. A request is sent by a client to request an action on a resource (identified by a URI) on a server. The server then sends a response with a response code (equivalent to that of HTTP). Therefore, efficiency is very important, so CoAP uses UDP, a datagram-oriented transport.<br /> <br /> CoAP is however a single protocol, with messaging and request/response as just features of the CoAP header<br /> <br /> +----------------------+<br /> | Application |<br /> +----------------------+<br /> +----------------------+ \<br /> | Requests/Responses | |<br /> |----------------------| | CoAP<br /> | Messages | |<br /> +----------------------+ /<br /> +----------------------+<br /> | UDP |<br /> +----------------------+<br /> <br /> == Message Format ==<br /> <br /> By default, the messages are encoded in a simple binary format and transported over UDP. The message format starts with a fixed-size 4-byte header, followed by a variable-length Token value, which can be between 0 and 8 bytes long. Following the Token value comes a sequence of zero or more CoAP Options in Type-Length-Value (TLV) format, optionally followed by a payload that takes up the rest of the datagram.<br /> <br /> 0 1 2 3<br /> 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1<br /> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<br /> |Ver| T | TKL | Code | Message ID |<br /> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<br /> | Token (if any, TKL bytes) ...<br /> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<br /> | Options (if any) ...<br /> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<br /> |1 1 1 1 1 1 1 1| Payload (if any) ...<br /> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<br /> <br /> ;Version (Ver) (2 bits)<br /> :Indicates the CoAP Version number. This must set this field to 1 (binary 01). Other values are reserved for future versions.<br /> <br /> ;Type (T) (2 bits)<br /> :Indicates if this message is of type Confirmable (0), Non-confirmable (1), Acknowledgement (2), or Reset (3).<br /> <br /> ;Token Length (TKL) (4 bits)<br /> :Indicates the length of the variable-length Token field, which may be 0-8 bytes in length.<br /> <br /> ;CoAP Request/Response Code (8 bits)<br /> :Splits into a 3-bit class and 5-bit detail.<br /> <br /> ;Message ID (16 bits)<br /> :Used to detect message duplication and to match messages of type Acknowledgement/Reset to messages of type Confirmable/Non-confirmable.<br /> <br /> == Security Considerations ==<br /> <br /> This section list some possible threats to the protocol. As CoAP realizes a subset of the features of HTTP/1.1, the security considerations in section 15 of RFC2616 are also pertinent to CoAP.<br /> <br /> ;Parsing the Protocol and Processing URI's<br /> <br /> The URI processing code in CoAP is likely to be a large source of vulnerabilities and should be implemented very carefully. Vulnerabilities include remotely crashing a node and remotely executing arbitrary code. CoAP aims to reduce the risk of these vulnerabilities by reducing parser complexity and moving much of the URI processing to the clients.<br /> <br /> ;Proxying and Caching<br /> <br /> Proxies are man-in-the-middle by their nature. They can break any IPsec or DTLS protection that would otherwise happen between direct CoAP message exchange. Risks include the loss of confidentiality and availability. If the proxies also cache the threat to confidentiality and integrity of request/response data is amplified as CoAP does not implement cache-suppressing Cache-control as in HTTP/1.1.<br /> For caching implementations any access control considerations also need to be applied to the value in the cache. A caching proxy must not make cache values available to requests that have lesser transport-security properties.<br /> <br /> ;Risk of Amplification<br /> <br /> As CoAP server reply to request packets with response packets that may be significantly larger an attacker can use CoAP nodes to generate more traffic and use them in a denial-of-service(DoS) attack. Turning a small attack packet into a larger one is called amplification. The attacker wants to overload a victim but is limited in the amount of traffic can use amplification to generate larger amounts. If a node that enables NoSec access becomes available to an attacker it can access victims on the general internet. UDP provides no way to verify the source address given in the request packet and an attacker can place the IP of the victim in the source address of a request packet to generate a larger packet directed at the victim. The risk is reduced however as constrained networks are only able to generate small amounts of traffic. In contrast the network itself with its limited capacity is a viable victim of an amplification attack. Large amplification factors should not be provided if the request is not authenticated. Also the slicing/blocking modes of CoAP [BLOCK] should be used for large resources.<br /> <br /> <br /> ;IP Address Spoofing<br /> <br /> <br /> <br /> ;Cross-Protocol Attacks<br /> <br /> <br /> <br /> ;Constrained Node Considerations<br /> <br /> Keys should be generated externally and added to the device during manufacturing or commissioning. Due to low processing power constrained nodes are susceptible to timing attacks. Cryptographic principles should be implemented with special care as many nodes are installed in exposed environments and have little resistance to tampering. The scope of credentials assigned to them should be considered carefully. A shared key assigned to a group of nodes may make any single node a target for subverting the entire group.<br /> <br /> == Implementations ==<br /> <br /> Generic implementations are becoming available for a variety of platforms. Implementations for constrained devices are typically written in C. CoAP is also used between them and more powerful systems such as cloud servers, home centrals, smartphones:<br /> <br /> {| class=&quot;wikitable sortable&quot;<br /> |-<br /> ! Name !! Programming Language !! Client/Server !! License !! Link<br /> |-<br /> | Erbium for Contiki || C || Client + Server || 3-clause BSD || http://www.contiki-os.org/<br /> |-<br /> | libcoap || C || Client + Server || BSD/GPL || https://libcoap.net/<br /> |-<br /> | Eclipse tinydtls || C || Client + Server || EPL+EDL || https://projects.eclipse.org/projects/iot.tinydtls<br /> |-<br /> | LibNyoci || C || Client + Server || MIT || https://github.com/darconeous/libnyoci<br /> |-<br /> | microcoap || C || Client + Server || MIT || https://github.com/1248/microcoap<br /> |-<br /> | cantcoap || C++/C || Client + Server || BSD || https://github.com/staropram/cantcoap<br /> |-<br /> | Lobaro CoAP || C || Client + Server || MIT || https://www.lobaro.com/portfolio/lobaro-coap/<br /> |-<br /> | MR-CoAP || Java || || BSD || https://github.com/MR-CoAP/CoAP<br /> |-<br /> | Wakaama || C || Client + Server || EPL+EDL || https://www.eclipse.org/wakaama/index.html<br /> |-<br /> | coap-node || Javascript || Client || MIT || https://github.com/PeterEB/coap-node<br /> |-<br /> | coap-shepherd || Javascript || Server || MIT || https://github.com/PeterEB/coap-shepherd<br /> |-<br /> | Californium || Java || Client + Server || EPL+EDL || https://www.eclipse.org/californium<br /> |-<br /> | nCoap || Java || Client + Server || BSD || https://github.com/okleine/nCoAP<br /> |-<br /> | leshan || Java || Client + Server || EPL+EDL || https://github.com/eclipse/leshan<br /> |-<br /> | CoAP.NET || C# || Client + Server || 3-clause BSD || https://github.com/smeshlink/CoAP.NET<br /> |-<br /> | CoAPSharp || C#, .NET || Client + Server || LGPL || http://www.coapsharp.com<br /> |-<br /> | Waher.Networking.CoAP || C# || Server || || https://github.com/PeterWaher/IoTGateway<br /> |-<br /> | gen_coap || Erlang || Client + Server || MPL v1.1 || https://github.com/gotthardp/gen_coap<br /> |-<br /> | go-coap || Go || Client + Server || MIT || https://github.com/go-ocf/go-coap<br /> |-<br /> | node-coap || Javascript || Client + Server || MIT || https://github.com/mcollina/node-coap<br /> |-<br /> | coap-cli || Javascript || || MIT || https://github.com/mcollina/coap-cli<br /> |-<br /> | txThings || Python (Twisted) || Client + Server || MIT || https://github.com/mwasilak/txThings<br /> |-<br /> | aiocoap || Python 3 || Client + Server || MIT || https://github.com/chrysn/aiocoap<br /> |-<br /> | CoAPthon || Python || Client + Server || MIT || https://github.com/Tanganelli/CoAPthon<br /> |-<br /> | Ruby coap || Ruby || Client || MIT || https://github.com/nning/coap<br /> |-<br /> | Ruby david || Ruby || Server || MIT || https://github.com/nning/david<br /> |-<br /> | coap-rs || Rust || Client + Server || MIT || https://github.com/Covertness/coap-rs<br /> |-<br /> | Copper || JavaScript (Browser Plugin) || Client || BSD || https://github.com/mkovatsc/Copper<br /> |-<br /> | iCoAP || Objective-C || Client || MIT || https://github.com/stuffrabbit/iCoAP<br /> |-<br /> | SwiftCoAP || Swift || Client + Server || MIT || https://github.com/stuffrabbit/SwiftCoAP<br /> |-<br /> | nCoap || Java || Client + Server || BSD || https://github.com/okleine/nCoAP<br /> |-<br /> | txThings || Python (Twisted) || Client + Server || MIT || https://github.com/mwasilak/txThings<br /> |}<br /> <br /> == Courses ==<br /> <br /> * [[Vertiefendes Wahlfach-Projekt]] (2018)<br /> * [[CoAP Chat Application for RIOT OS]]<br /> <br /> == References ==<br /> * RFC 7252: https://tools.ietf.org/html/rfc7252<br /> * RFC 2616: https://www.ietf.org/rfc/rfc2616.txt<br /> * CoAP: RFC 7252 Constrained Application Protocol https://coap.technology/<br /> * Learning Internet of Things: https://www.oreilly.com/library/view/learning-internet-of/9781783553532/<br /> <br /> [[Category:Basics]]</div>

Ograsl https://elvis.hcw.ac.at/wiki/index.php?title=Constrained_Application_Protocol&diff=1319 2019-03-18T13:37:57Z

<p>Ograsl: /* Implementations */</p> <hr /> <div>The '''Constrained Application Protocol''' ('''CoAP''') is a specialized web transfer protocol, as defined in RFC 7252, for use with constrained nodes and constrained networks in the Internet of Things.<br /> The protocol is designed for machine-to-machine (M2M) applications such as smart energy and building automation.<br /> <br /> == Features ==<br /> <br /> The work on Constrained Environments aims at realizing the REST architecture in a suitable form for the most constrained nodes and networks. The nodes usually consist of 8-bit microcontrollers with limited amounts of RAM and ROM.<br /> <br /> <br /> CoAP has the following main features:<br /> <br /> * Web protocol fulfilling M2M requirements in constrained environments<br /> * UDP [RFC0768] binding with optional reliability supporting unicast and multicast requests<br /> * Asynchronous message exchanges<br /> * Low header overhead and parsing complexity<br /> * URI and Content-type support<br /> * Simple proxy and caching capabilities<br /> * Stateless HTTP mapping<br /> * Security binding to Datagram Transport Layer Security (DTLS)<br /> <br /> == The Protocol ==<br /> <br /> CoAP is similar to the client/server model of HTTP. M2M interactions typically result in a CoAP implementation acting in both client and server roles. A request is sent by a client to request an action on a resource (identified by a URI) on a server. The server then sends a response with a response code (equivalent to that of HTTP). Therefore, efficiency is very important, so CoAP uses UDP, a datagram-oriented transport.<br /> <br /> CoAP is however a single protocol, with messaging and request/response as just features of the CoAP header<br /> <br /> +----------------------+<br /> | Application |<br /> +----------------------+<br /> +----------------------+ \<br /> | Requests/Responses | |<br /> |----------------------| | CoAP<br /> | Messages | |<br /> +----------------------+ /<br /> +----------------------+<br /> | UDP |<br /> +----------------------+<br /> <br /> == Message Format ==<br /> <br /> By default, the messages are encoded in a simple binary format and transported over UDP. The message format starts with a fixed-size 4-byte header, followed by a variable-length Token value, which can be between 0 and 8 bytes long. Following the Token value comes a sequence of zero or more CoAP Options in Type-Length-Value (TLV) format, optionally followed by a payload that takes up the rest of the datagram.<br /> <br /> 0 1 2 3<br /> 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1<br /> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<br /> |Ver| T | TKL | Code | Message ID |<br /> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<br /> | Token (if any, TKL bytes) ...<br /> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<br /> | Options (if any) ...<br /> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<br /> |1 1 1 1 1 1 1 1| Payload (if any) ...<br /> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<br /> <br /> ;Version (Ver) (2 bits)<br /> :Indicates the CoAP Version number. This must set this field to 1 (binary 01). Other values are reserved for future versions.<br /> <br /> ;Type (T) (2 bits)<br /> :Indicates if this message is of type Confirmable (0), Non-confirmable (1), Acknowledgement (2), or Reset (3).<br /> <br /> ;Token Length (TKL) (4 bits)<br /> :Indicates the length of the variable-length Token field, which may be 0-8 bytes in length.<br /> <br /> ;CoAP Request/Response Code (8 bits)<br /> :Splits into a 3-bit class and 5-bit detail.<br /> <br /> ;Message ID (16 bits)<br /> :Used to detect message duplication and to match messages of type Acknowledgement/Reset to messages of type Confirmable/Non-confirmable.<br /> <br /> == Implementations ==<br /> <br /> Generic implementations are becoming available for a variety of platforms. Implementations for constrained devices are typically written in C. CoAP is also used between them and more powerful systems such as cloud servers, home centrals, smartphones:<br /> <br /> {| class=&quot;wikitable sortable&quot;<br /> |-<br /> ! Name !! Programming Language !! Client/Server !! License !! Link<br /> |-<br /> | Erbium for Contiki || C || Client + Server || 3-clause BSD || http://www.contiki-os.org/<br /> |-<br /> | libcoap || C || Client + Server || BSD/GPL || https://libcoap.net/<br /> |-<br /> | Eclipse tinydtls || C || Client + Server || EPL+EDL || https://projects.eclipse.org/projects/iot.tinydtls<br /> |-<br /> | LibNyoci || C || Client + Server || MIT || https://github.com/darconeous/libnyoci<br /> |-<br /> | microcoap || C || Client + Server || MIT || https://github.com/1248/microcoap<br /> |-<br /> | cantcoap || C++/C || Client + Server || BSD || https://github.com/staropram/cantcoap<br /> |-<br /> | Lobaro CoAP || C || Client + Server || MIT || https://www.lobaro.com/portfolio/lobaro-coap/<br /> |-<br /> | MR-CoAP || Java || || BSD || https://github.com/MR-CoAP/CoAP<br /> |-<br /> | Wakaama || C || Client + Server || EPL+EDL || https://www.eclipse.org/wakaama/index.html<br /> |-<br /> | coap-node || Javascript || Client || MIT || https://github.com/PeterEB/coap-node<br /> |-<br /> | coap-shepherd || Javascript || Server || MIT || https://github.com/PeterEB/coap-shepherd<br /> |-<br /> | Californium || Java || Client + Server || EPL+EDL || https://www.eclipse.org/californium<br /> |-<br /> | nCoap || Java || Client + Server || BSD || https://github.com/okleine/nCoAP<br /> |-<br /> | leshan || Java || Client + Server || EPL+EDL || https://github.com/eclipse/leshan<br /> |-<br /> | CoAP.NET || C# || Client + Server || 3-clause BSD || https://github.com/smeshlink/CoAP.NET<br /> |-<br /> | CoAPSharp || C#, .NET || Client + Server || LGPL || http://www.coapsharp.com<br /> |-<br /> | Waher.Networking.CoAP || C# || Server || || https://github.com/PeterWaher/IoTGateway<br /> |-<br /> | gen_coap || Erlang || Client + Server || MPL v1.1 || https://github.com/gotthardp/gen_coap<br /> |-<br /> | go-coap || Go || Client + Server || MIT || https://github.com/go-ocf/go-coap<br /> |-<br /> | node-coap || Javascript || Client + Server || MIT || https://github.com/mcollina/node-coap<br /> |-<br /> | coap-cli || Javascript || || MIT || https://github.com/mcollina/coap-cli<br /> |-<br /> | txThings || Python (Twisted) || Client + Server || MIT || https://github.com/mwasilak/txThings<br /> |-<br /> | aiocoap || Python 3 || Client + Server || MIT || https://github.com/chrysn/aiocoap<br /> |-<br /> | CoAPthon || Python || Client + Server || MIT || https://github.com/Tanganelli/CoAPthon<br /> |-<br /> | Ruby coap || Ruby || Client || MIT || https://github.com/nning/coap<br /> |-<br /> | Ruby david || Ruby || Server || MIT || https://github.com/nning/david<br /> |-<br /> | coap-rs || Rust || Client + Server || MIT || https://github.com/Covertness/coap-rs<br /> |-<br /> | Copper || JavaScript (Browser Plugin) || Client || BSD || https://github.com/mkovatsc/Copper<br /> |-<br /> | iCoAP || Objective-C || Client || MIT || https://github.com/stuffrabbit/iCoAP<br /> |-<br /> | SwiftCoAP || Swift || Client + Server || MIT || https://github.com/stuffrabbit/SwiftCoAP<br /> |-<br /> | nCoap || Java || Client + Server || BSD || https://github.com/okleine/nCoAP<br /> |-<br /> | txThings || Python (Twisted) || Client + Server || MIT || https://github.com/mwasilak/txThings<br /> |}<br /> <br /> == Courses ==<br /> <br /> * [[Vertiefendes Wahlfach-Projekt]] (2018)<br /> <br /> == References ==<br /> * RFC 7252: https://tools.ietf.org/html/rfc7252<br /> * CoAP: RFC 7252 Constrained Application Protocol https://coap.technology/<br /> * Learning Internet of Things: https://www.oreilly.com/library/view/learning-internet-of/9781783553532/<br /> <br /> [[Category:Documentation]]</div>

Ograsl https://elvis.hcw.ac.at/wiki/index.php?title=Constrained_Application_Protocol&diff=1318 2019-03-15T06:50:15Z

<p>Ograsl: /* Tools */</p> <hr /> <div>The '''Constrained Application Protocol''' ('''CoAP''') is a specialized web transfer protocol, as defined in RFC 7252, for use with constrained nodes and constrained networks in the Internet of Things.<br /> The protocol is designed for machine-to-machine (M2M) applications such as smart energy and building automation.<br /> <br /> == Features ==<br /> <br /> The work on Constrained Environments aims at realizing the REST architecture in a suitable form for the most constrained nodes and networks. The nodes usually consist of 8-bit microcontrollers with limited amounts of RAM and ROM.<br /> <br /> <br /> CoAP has the following main features:<br /> <br /> * Web protocol fulfilling M2M requirements in constrained environments<br /> * UDP [RFC0768] binding with optional reliability supporting unicast and multicast requests<br /> * Asynchronous message exchanges<br /> * Low header overhead and parsing complexity<br /> * URI and Content-type support<br /> * Simple proxy and caching capabilities<br /> * Stateless HTTP mapping<br /> * Security binding to Datagram Transport Layer Security (DTLS)<br /> <br /> == The Protocol ==<br /> <br /> CoAP is similar to the client/server model of HTTP. M2M interactions typically result in a CoAP implementation acting in both client and server roles. A request is sent by a client to request an action on a resource (identified by a URI) on a server. The server then sends a response with a response code (equivalent to that of HTTP). Therefore, efficiency is very important, so CoAP uses UDP, a datagram-oriented transport.<br /> <br /> CoAP is however a single protocol, with messaging and request/response as just features of the CoAP header<br /> <br /> +----------------------+<br /> | Application |<br /> +----------------------+<br /> +----------------------+ \<br /> | Requests/Responses | |<br /> |----------------------| | CoAP<br /> | Messages | |<br /> +----------------------+ /<br /> +----------------------+<br /> | UDP |<br /> +----------------------+<br /> <br /> == Message Format ==<br /> <br /> By default, the messages are encoded in a simple binary format and transported over UDP. The message format starts with a fixed-size 4-byte header, followed by a variable-length Token value, which can be between 0 and 8 bytes long. Following the Token value comes a sequence of zero or more CoAP Options in Type-Length-Value (TLV) format, optionally followed by a payload that takes up the rest of the datagram.<br /> <br /> 0 1 2 3<br /> 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1<br /> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<br /> |Ver| T | TKL | Code | Message ID |<br /> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<br /> | Token (if any, TKL bytes) ...<br /> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<br /> | Options (if any) ...<br /> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<br /> |1 1 1 1 1 1 1 1| Payload (if any) ...<br /> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<br /> <br /> ;Version (Ver) (2 bits)<br /> :Indicates the CoAP Version number. This must set this field to 1 (binary 01). Other values are reserved for future versions.<br /> <br /> ;Type (T) (2 bits)<br /> :Indicates if this message is of type Confirmable (0), Non-confirmable (1), Acknowledgement (2), or Reset (3).<br /> <br /> ;Token Length (TKL) (4 bits)<br /> :Indicates the length of the variable-length Token field, which may be 0-8 bytes in length.<br /> <br /> ;CoAP Request/Response Code (8 bits)<br /> :Splits into a 3-bit class and 5-bit detail.<br /> <br /> ;Message ID (16 bits)<br /> :Used to detect message duplication and to match messages of type Acknowledgement/Reset to messages of type Confirmable/Non-confirmable.<br /> <br /> == Implementations ==<br /> <br /> Generic implementations are becoming availible for a variety of platforms. Implementations for constrained devices are typically written in C. CoAP is also used between them and more powerful systems such as cloud servers, home centrals, smartphones:<br /> <br /> {| class=&quot;wikitable sortable&quot;<br /> |-<br /> ! Name !! Programming Language !! Client/Server !! License !! Link<br /> |-<br /> | Erbium for Contiki || C || Client + Server || 3-clause BSD || http://www.contiki-os.org/<br /> |-<br /> | libcoap || C || Client + Server || BSD/GPL || https://libcoap.net/<br /> |-<br /> | Eclipse tinydtls || C || Client + Server || EPL+EDL || https://projects.eclipse.org/projects/iot.tinydtls<br /> |-<br /> | LibNyoci || C || Client + Server || MIT || https://github.com/darconeous/libnyoci<br /> |-<br /> | microcoap || C || Client + Server || MIT || https://github.com/1248/microcoap<br /> |-<br /> | cantcoap || C++/C || Client + Server || BSD || https://github.com/staropram/cantcoap<br /> |-<br /> | Lobaro CoAP || C || Client + Server || MIT || https://www.lobaro.com/portfolio/lobaro-coap/<br /> |-<br /> | MR-CoAP || Java || || BSD || https://github.com/MR-CoAP/CoAP<br /> |-<br /> | Wakaama || C || Client + Server || EPL+EDL || https://www.eclipse.org/wakaama/index.html<br /> |-<br /> | coap-node || Javascript || Client || MIT || https://github.com/PeterEB/coap-node<br /> |-<br /> | coap-shepherd || Javascript || Server || MIT || https://github.com/PeterEB/coap-shepherd<br /> |-<br /> | Californium || Java || Client + Server || EPL+EDL || https://www.eclipse.org/californium<br /> |-<br /> | nCoap || Java || Client + Server || BSD || https://github.com/okleine/nCoAP<br /> |-<br /> | leshan || Java || Client + Server || EPL+EDL || https://github.com/eclipse/leshan<br /> |-<br /> | CoAP.NET || C# || Client + Server || 3-clause BSD || https://github.com/smeshlink/CoAP.NET<br /> |-<br /> | CoAPSharp || C#, .NET || Client + Server || LGPL || http://www.coapsharp.com<br /> |-<br /> | Waher.Networking.CoAP || C# || Server || || https://github.com/PeterWaher/IoTGateway<br /> |-<br /> | gen_coap || Erlang || Client + Server || MPL v1.1 || https://github.com/gotthardp/gen_coap<br /> |-<br /> | go-coap || Go || Client + Server || MIT || https://github.com/go-ocf/go-coap<br /> |-<br /> | node-coap || Javascript || Client + Server || MIT || https://github.com/mcollina/node-coap<br /> |-<br /> | coap-cli || Javascript || || MIT || https://github.com/mcollina/coap-cli<br /> |-<br /> | txThings || Python (Twisted) || Client + Server || MIT || https://github.com/mwasilak/txThings<br /> |-<br /> | aiocoap || Python 3 || Client + Server || MIT || https://github.com/chrysn/aiocoap<br /> |-<br /> | CoAPthon || Python || Client + Server || MIT || https://github.com/Tanganelli/CoAPthon<br /> |-<br /> | Ruby coap || Ruby || Client || MIT || https://github.com/nning/coap<br /> |-<br /> | Ruby david || Ruby || Server || MIT || https://github.com/nning/david<br /> |-<br /> | coap-rs || Rust || Client + Server || MIT || https://github.com/Covertness/coap-rs<br /> |-<br /> | Copper || JavaScript (Browser Plugin) || Client || BSD || https://github.com/mkovatsc/Copper<br /> |-<br /> | iCoAP || Objective-C || Client || MIT || https://github.com/stuffrabbit/iCoAP<br /> |-<br /> | SwiftCoAP || Swift || Client + Server || MIT || https://github.com/stuffrabbit/SwiftCoAP<br /> |-<br /> | nCoap || Java || Client + Server || BSD || https://github.com/okleine/nCoAP<br /> |-<br /> | txThings || Python (Twisted) || Client + Server || MIT || https://github.com/mwasilak/txThings<br /> |}<br /> <br /> == Courses ==<br /> <br /> * [[Vertiefendes Wahlfach-Projekt]] (2018)<br /> <br /> == References ==<br /> * RFC 7252: https://tools.ietf.org/html/rfc7252<br /> * CoAP: RFC 7252 Constrained Application Protocol https://coap.technology/<br /> * Learning Internet of Things: https://www.oreilly.com/library/view/learning-internet-of/9781783553532/<br /> <br /> [[Category:Documentation]]</div>

Ograsl https://elvis.hcw.ac.at/wiki/index.php?title=Constrained_Application_Protocol&diff=1306 2019-03-11T22:59:41Z

<p>Ograsl: /* Implementations */</p> <hr /> <div>The '''Constrained Application Protocol''' ('''CoAP''') is a specialized web transfer protocol, as defined in RFC 7252, for use with constrained nodes and constrained networks in the Internet of Things.<br /> The protocol is designed for machine-to-machine (M2M) applications such as smart energy and building automation.<br /> <br /> == Features ==<br /> <br /> The work on Constrained Environments aims at realizing the REST architecture in a suitable form for the most constrained nodes and networks. The nodes usually consist of 8-bit microcontrollers with limited amounts of RAM and ROM.<br /> <br /> <br /> CoAP has the following main features:<br /> <br /> * Web protocol fulfilling M2M requirements in constrained environments<br /> * UDP [RFC0768] binding with optional reliability supporting unicast and multicast requests<br /> * Asynchronous message exchanges<br /> * Low header overhead and parsing complexity<br /> * URI and Content-type support<br /> * Simple proxy and caching capabilities<br /> * Stateless HTTP mapping<br /> * Security binding to Datagram Transport Layer Security (DTLS)<br /> <br /> == The Protocol ==<br /> <br /> CoAP is similar to the client/server model of HTTP. M2M interactions typically result in a CoAP implementation acting in both client and server roles. A request is sent by a client to request an action on a resource (identified by a URI) on a server. The server then sends a response with a response code (equivalent to that of HTTP). Therefore, efficiency is very important, so CoAP uses UDP, a datagram-oriented transport.<br /> <br /> CoAP is however a single protocol, with messaging and request/response as just features of the CoAP header<br /> <br /> +----------------------+<br /> | Application |<br /> +----------------------+<br /> +----------------------+ \<br /> | Requests/Responses | |<br /> |----------------------| | CoAP<br /> | Messages | |<br /> +----------------------+ /<br /> +----------------------+<br /> | UDP |<br /> +----------------------+<br /> <br /> == Message Format ==<br /> <br /> By default, the messages are encoded in a simple binary format and transported over UDP. The message format starts with a fixed-size 4-byte header, followed by a variable-length Token value, which can be between 0 and 8 bytes long. Following the Token value comes a sequence of zero or more CoAP Options in Type-Length-Value (TLV) format, optionally followed by a payload that takes up the rest of the datagram.<br /> <br /> 0 1 2 3<br /> 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1<br /> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<br /> |Ver| T | TKL | Code | Message ID |<br /> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<br /> | Token (if any, TKL bytes) ...<br /> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<br /> | Options (if any) ...<br /> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<br /> |1 1 1 1 1 1 1 1| Payload (if any) ...<br /> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<br /> <br /> ;Version (Ver) (2 bits)<br /> :Indicates the CoAP Version number. This must set this field to 1 (binary 01). Other values are reserved for future versions.<br /> <br /> ;Type (T) (2 bits)<br /> :Indicates if this message is of type Confirmable (0), Non-confirmable (1), Acknowledgement (2), or Reset (3).<br /> <br /> ;Token Length (TKL) (4 bits)<br /> :Indicates the length of the variable-length Token field, which may be 0-8 bytes in length.<br /> <br /> ;CoAP Request/Response Code (8 bits)<br /> :Splits into a 3-bit class and 5-bit detail.<br /> <br /> ;Message ID (16 bits)<br /> :Used to detect message duplication and to match messages of type Acknowledgement/Reset to messages of type Confirmable/Non-confirmable.<br /> <br /> == Implementations ==<br /> <br /> Generic implementations are becoming availible for a variety of platforms. Implementations for constrained devices are typically written in C. CoAP is also used between them and more powerful systems such as cloud servers, home centrals, smartphones:<br /> <br /> {| class=&quot;wikitable sortable&quot;<br /> |-<br /> ! Name !! Programming Language !! Client/Server !! License !! Link<br /> |-<br /> | Erbium for Contiki || C || Client + Server || 3-clause BSD || http://www.contiki-os.org/<br /> |-<br /> | libcoap || C || Client + Server || BSD/GPL || https://libcoap.net/<br /> |-<br /> | Eclipse tinydtls || C || Client + Server || EPL+EDL || https://projects.eclipse.org/projects/iot.tinydtls<br /> |-<br /> | LibNyoci || C || Client + Server || MIT || https://github.com/darconeous/libnyoci<br /> |-<br /> | microcoap || C || Client + Server || MIT || https://github.com/1248/microcoap<br /> |-<br /> | cantcoap || C++/C || Client + Server || BSD || https://github.com/staropram/cantcoap<br /> |-<br /> | Lobaro CoAP || C || Client + Server || MIT || https://www.lobaro.com/portfolio/lobaro-coap/<br /> |-<br /> | MR-CoAP || Java || || BSD || https://github.com/MR-CoAP/CoAP<br /> |-<br /> | Wakaama || C || Client + Server || EPL+EDL || https://www.eclipse.org/wakaama/index.html<br /> |-<br /> | coap-node || Javascript || Client || MIT || https://github.com/PeterEB/coap-node<br /> |-<br /> | coap-shepherd || Javascript || Server || MIT || https://github.com/PeterEB/coap-shepherd<br /> |-<br /> | Californium || Java || Client + Server || EPL+EDL || https://www.eclipse.org/californium<br /> |-<br /> | nCoap || Java || Client + Server || BSD || https://github.com/okleine/nCoAP<br /> |-<br /> | leshan || Java || Client + Server || EPL+EDL || https://github.com/eclipse/leshan<br /> |-<br /> | CoAP.NET || C# || Client + Server || 3-clause BSD || https://github.com/smeshlink/CoAP.NET<br /> |-<br /> | CoAPSharp || C#, .NET || Client + Server || LGPL || http://www.coapsharp.com<br /> |-<br /> | Waher.Networking.CoAP || C# || Server || || https://github.com/PeterWaher/IoTGateway<br /> |-<br /> | gen_coap || Erlang || Client + Server || MPL v1.1 || https://github.com/gotthardp/gen_coap<br /> |-<br /> | go-coap || Go || Client + Server || MIT || https://github.com/go-ocf/go-coap<br /> |-<br /> | node-coap || Javascript || Client + Server || MIT || https://github.com/mcollina/node-coap<br /> |-<br /> | coap-cli || Javascript || || MIT || https://github.com/mcollina/coap-cli<br /> |-<br /> | txThings || Python (Twisted) || Client + Server || MIT || https://github.com/mwasilak/txThings<br /> |-<br /> | aiocoap || Python 3 || Client + Server || MIT || https://github.com/chrysn/aiocoap<br /> |-<br /> | CoAPthon || Python || Client + Server || MIT || https://github.com/Tanganelli/CoAPthon<br /> |-<br /> | Ruby coap || Ruby || Client || MIT || https://github.com/nning/coap<br /> |-<br /> | Ruby david || Ruby || Server || MIT || https://github.com/nning/david<br /> |-<br /> | coap-rs || Rust || Client + Server || MIT || https://github.com/Covertness/coap-rs<br /> |-<br /> | Copper || JavaScript (Browser Plugin) || Client || BSD || https://github.com/mkovatsc/Copper<br /> |-<br /> | iCoAP || Objective-C || Client || MIT || https://github.com/stuffrabbit/iCoAP<br /> |-<br /> | SwiftCoAP || Swift || Client + Server || MIT || https://github.com/stuffrabbit/SwiftCoAP<br /> |-<br /> | nCoap || Java || Client + Server || BSD || https://github.com/okleine/nCoAP<br /> |-<br /> | txThings || Python (Twisted) || Client + Server || MIT || https://github.com/mwasilak/txThings<br /> |}<br /> <br /> == Tools ==<br /> <br /> <br /> <br /> == Courses ==<br /> <br /> * [[Vertiefendes Wahlfach-Projekt]] (2018)<br /> <br /> == References ==<br /> * RFC 7252: https://tools.ietf.org/html/rfc7252<br /> * CoAP: RFC 7252 Constrained Application Protocol https://coap.technology/<br /> * Learning Internet of Things: https://www.oreilly.com/library/view/learning-internet-of/9781783553532/<br /> <br /> [[Category:Documentation]]</div>

Ograsl https://elvis.hcw.ac.at/wiki/index.php?title=Constrained_Application_Protocol&diff=1305 2019-03-11T22:59:02Z

<p>Ograsl: </p> <hr /> <div>The '''Constrained Application Protocol''' ('''CoAP''') is a specialized web transfer protocol, as defined in RFC 7252, for use with constrained nodes and constrained networks in the Internet of Things.<br /> The protocol is designed for machine-to-machine (M2M) applications such as smart energy and building automation.<br /> <br /> == Features ==<br /> <br /> The work on Constrained Environments aims at realizing the REST architecture in a suitable form for the most constrained nodes and networks. The nodes usually consist of 8-bit microcontrollers with limited amounts of RAM and ROM.<br /> <br /> <br /> CoAP has the following main features:<br /> <br /> * Web protocol fulfilling M2M requirements in constrained environments<br /> * UDP [RFC0768] binding with optional reliability supporting unicast and multicast requests<br /> * Asynchronous message exchanges<br /> * Low header overhead and parsing complexity<br /> * URI and Content-type support<br /> * Simple proxy and caching capabilities<br /> * Stateless HTTP mapping<br /> * Security binding to Datagram Transport Layer Security (DTLS)<br /> <br /> == The Protocol ==<br /> <br /> CoAP is similar to the client/server model of HTTP. M2M interactions typically result in a CoAP implementation acting in both client and server roles. A request is sent by a client to request an action on a resource (identified by a URI) on a server. The server then sends a response with a response code (equivalent to that of HTTP). Therefore, efficiency is very important, so CoAP uses UDP, a datagram-oriented transport.<br /> <br /> CoAP is however a single protocol, with messaging and request/response as just features of the CoAP header<br /> <br /> +----------------------+<br /> | Application |<br /> +----------------------+<br /> +----------------------+ \<br /> | Requests/Responses | |<br /> |----------------------| | CoAP<br /> | Messages | |<br /> +----------------------+ /<br /> +----------------------+<br /> | UDP |<br /> +----------------------+<br /> <br /> == Message Format ==<br /> <br /> By default, the messages are encoded in a simple binary format and transported over UDP. The message format starts with a fixed-size 4-byte header, followed by a variable-length Token value, which can be between 0 and 8 bytes long. Following the Token value comes a sequence of zero or more CoAP Options in Type-Length-Value (TLV) format, optionally followed by a payload that takes up the rest of the datagram.<br /> <br /> 0 1 2 3<br /> 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1<br /> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<br /> |Ver| T | TKL | Code | Message ID |<br /> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<br /> | Token (if any, TKL bytes) ...<br /> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<br /> | Options (if any) ...<br /> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<br /> |1 1 1 1 1 1 1 1| Payload (if any) ...<br /> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<br /> <br /> ;Version (Ver) (2 bits)<br /> :Indicates the CoAP Version number. This must set this field to 1 (binary 01). Other values are reserved for future versions.<br /> <br /> ;Type (T) (2 bits)<br /> :Indicates if this message is of type Confirmable (0), Non-confirmable (1), Acknowledgement (2), or Reset (3).<br /> <br /> ;Token Length (TKL) (4 bits)<br /> :Indicates the length of the variable-length Token field, which may be 0-8 bytes in length.<br /> <br /> ;CoAP Request/Response Code (8 bits)<br /> :Splits into a 3-bit class and 5-bit detail.<br /> <br /> ;Message ID (16 bits)<br /> :Used to detect message duplication and to match messages of type Acknowledgement/Reset to messages of type Confirmable/Non-confirmable.<br /> <br /> == Implementations ==<br /> <br /> Generic implementations are becoming availible for a variety of platforms. Implementations for constrained devices are typically written in C. CoAP is also used between them and more powerful systems such as cloud servers, home centrals, smartphones:<br /> <br /> {| class=&quot;wikitable sortable&quot;<br /> |-<br /> ! Name !! Programming Language !! Client/Server !! License !! Link<br /> |-<br /> | Erbium for Contiki || C || Client + Server || 3-clause BSD || http://www.contiki-os.org/<br /> |-<br /> | libcoap || C || Client + Server || BSD/GPL || https://libcoap.net/<br /> |-<br /> | Eclipse tinydtls || C || Client + Server || EPL+EDL || https://projects.eclipse.org/projects/iot.tinydtls<br /> |-<br /> | LibNyoci || C || Client + Server || MIT || https://github.com/darconeous/libnyoci<br /> |-<br /> | microcoap || C || Client + Server || MIT || https://github.com/1248/microcoap<br /> |-<br /> | cantcoap || C++/C || Client + Server || BSD || https://github.com/staropram/cantcoap<br /> |-<br /> | Lobaro CoAP || C || Client + Server || MIT || https://www.lobaro.com/portfolio/lobaro-coap/<br /> |-<br /> | MR-CoAP || Java || || BSD || https://github.com/MR-CoAP/CoAP<br /> |-<br /> | Wakaama || C || Client + Server || EPL+EDL || https://www.eclipse.org/wakaama/index.html<br /> |-<br /> | coap-node || Javascript || Client || MIT || https://github.com/PeterEB/coap-node<br /> |-<br /> | coap-shepherd || Javascript || Server || MIT || https://github.com/PeterEB/coap-shepherd<br /> |-<br /> | Californium || Java || Client + Server || EPL+EDL || https://www.eclipse.org/californium<br /> |-<br /> | nCoap || Java || Client + Server || BSD || https://github.com/okleine/nCoAP<br /> |-<br /> | leshan || Java || Client + Server || EPL+EDL || https://github.com/eclipse/leshan<br /> |-<br /> | CoAP.NET || C# || Client + Server || 3-clause BSD || https://github.com/smeshlink/CoAP.NET<br /> |-<br /> | CoAPSharp || C#, .NET || Client + Server || LGPL || http://www.coapsharp.com<br /> |-<br /> | Waher.Networking.CoAP || C# || Server || || https://github.com/PeterWaher/IoTGateway/tree/master/Networking/Waher.Networking.CoAP<br /> |-<br /> | gen_coap || Erlang || Client + Server || MPL v1.1 || https://github.com/gotthardp/gen_coap<br /> |-<br /> | go-coap || Go || Client + Server || MIT || https://github.com/go-ocf/go-coap<br /> |-<br /> | node-coap || Javascript || Client + Server || MIT || https://github.com/mcollina/node-coap<br /> |-<br /> | coap-cli || Javascript || || MIT || https://github.com/mcollina/coap-cli<br /> |-<br /> | txThings || Python (Twisted) || Client + Server || MIT || https://github.com/mwasilak/txThings<br /> |-<br /> | aiocoap || Python 3 || Client + Server || MIT || https://github.com/chrysn/aiocoap<br /> |-<br /> | CoAPthon || Python || Client + Server || MIT || https://github.com/Tanganelli/CoAPthon<br /> |-<br /> | Ruby coap || Ruby || Client || MIT || https://github.com/nning/coap<br /> |-<br /> | Ruby david || Ruby || Server || MIT || https://github.com/nning/david<br /> |-<br /> | coap-rs || Rust || Client + Server || MIT || https://github.com/Covertness/coap-rs<br /> |-<br /> | Copper || JavaScript (Browser Plugin) || Client || BSD || https://github.com/mkovatsc/Copper<br /> |-<br /> | iCoAP || Objective-C || Client || MIT || https://github.com/stuffrabbit/iCoAP<br /> |-<br /> | SwiftCoAP || Swift || Client + Server || MIT || https://github.com/stuffrabbit/SwiftCoAP<br /> |-<br /> | nCoap || Java || Client + Server || BSD || https://github.com/okleine/nCoAP<br /> |-<br /> | txThings || Python (Twisted) || Client + Server || MIT || https://github.com/mwasilak/txThings<br /> |}<br /> <br /> == Tools ==<br /> <br /> <br /> <br /> == Courses ==<br /> <br /> * [[Vertiefendes Wahlfach-Projekt]] (2018)<br /> <br /> == References ==<br /> * RFC 7252: https://tools.ietf.org/html/rfc7252<br /> * CoAP: RFC 7252 Constrained Application Protocol https://coap.technology/<br /> * Learning Internet of Things: https://www.oreilly.com/library/view/learning-internet-of/9781783553532/<br /> <br /> [[Category:Documentation]]</div>

Ograsl https://elvis.hcw.ac.at/wiki/index.php?title=Constrained_Application_Protocol&diff=1304 2019-03-11T22:54:30Z

<p>Ograsl: /* The Protocol */</p> <hr /> <div>The '''Constrained Application Protocol''' ('''CoAP''') is a specialized web transfer protocol, as defined in RFC 7252, for use with constrained nodes and constrained networks in the Internet of Things.<br /> The protocol is designed for machine-to-machine (M2M) applications such as smart energy and building automation.<br /> <br /> == Features ==<br /> <br /> The work on Constrained Environments aims at realizing the REST architecture in a suitable form for the most constrained nodes and networks. The nodes usually consist of 8-bit microcontrollers with limited amounts of RAM and ROM.<br /> <br /> <br /> CoAP has the following main features:<br /> <br /> * Web protocol fulfilling M2M requirements in constrained environments<br /> * UDP [RFC0768] binding with optional reliability supporting unicast and multicast requests<br /> * Asynchronous message exchanges<br /> * Low header overhead and parsing complexity<br /> * URI and Content-type support<br /> * Simple proxy and caching capabilities<br /> * Stateless HTTP mapping<br /> * Security binding to Datagram Transport Layer Security (DTLS)<br /> <br /> == The Protocol ==<br /> <br /> CoAP is similar to the client/server model of HTTP. M2M interactions typically result in a CoAP implementation acting in both client and server roles. A request is sent by a client to request an action on a resource (identified by a URI) on a server. The server then sends a response with a response code (equivalent to that of HTTP). Therefore, efficiency is very important, so CoAP uses UDP, a datagram-oriented transport.<br /> <br /> CoAP is however a single protocol, with messaging and request/response as just features of the CoAP header<br /> <br /> +----------------------+<br /> | Application |<br /> +----------------------+<br /> +----------------------+ \<br /> | Requests/Responses | |<br /> |----------------------| | CoAP<br /> | Messages | |<br /> +----------------------+ /<br /> +----------------------+<br /> | UDP |<br /> +----------------------+<br /> <br /> == Message Format ==<br /> <br /> By default, the messages are encoded in a simple binary format and transported over UDP. The message format starts with a fixed-size 4-byte header, followed by a variable-length Token value, which can be between 0 and 8 bytes long. Following the Token value comes a sequence of zero or more CoAP Options in Type-Length-Value (TLV) format, optionally followed by a payload that takes up the rest of the datagram.<br /> <br /> 0 1 2 3<br /> 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1<br /> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<br /> |Ver| T | TKL | Code | Message ID |<br /> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<br /> | Token (if any, TKL bytes) ...<br /> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<br /> | Options (if any) ...<br /> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<br /> |1 1 1 1 1 1 1 1| Payload (if any) ...<br /> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<br /> <br /> ;Version (Ver) (2 bits)<br /> :Indicates the CoAP Version number. This must set this field to 1 (binary 01). Other values are reserved for future versions.<br /> <br /> ;Type (T) (2 bits)<br /> :Indicates if this message is of type Confirmable (0), Non-confirmable (1), Acknowledgement (2), or Reset (3).<br /> <br /> ;Token Length (TKL) (4 bits)<br /> :Indicates the length of the variable-length Token field, which may be 0-8 bytes in length.<br /> <br /> ;CoAP Request/Response Code (8 bits)<br /> :Splits into a 3-bit class and 5-bit detail.<br /> <br /> ;Message ID (16 bits)<br /> :Used to detect message duplication and to match messages of type Acknowledgement/Reset to messages of type Confirmable/Non-confirmable.<br /> <br /> == Implementations ==<br /> <br /> Generic implementations are becoming availible for a variety of platforms. Implementations for constrained devices are typically written in C. CoAP is also used between them and more powerful systems such as cloud servers, home centrals, smartphones:<br /> <br /> {| class=&quot;wikitable sortable&quot;<br /> |-<br /> ! Name !! Programming Language !! Client/Server !! License !! Link<br /> |-<br /> | Erbium for Contiki || C || Client + Server || 3-clause BSD || http://www.contiki-os.org/<br /> |-<br /> | libcoap || C || Client + Server || BSD/GPL || https://libcoap.net/<br /> |-<br /> | Eclipse tinydtls || C || Client + Server || EPL+EDL || https://projects.eclipse.org/projects/iot.tinydtls<br /> |-<br /> | LibNyoci || C || Client + Server || MIT || https://github.com/darconeous/libnyoci<br /> |-<br /> | microcoap || C || Client + Server || MIT || https://github.com/1248/microcoap<br /> |-<br /> | cantcoap || C++/C || Client + Server || BSD || https://github.com/staropram/cantcoap<br /> |-<br /> | Lobaro CoAP || C || Client + Server || MIT || https://www.lobaro.com/portfolio/lobaro-coap/<br /> |-<br /> | MR-CoAP || Java || || BSD || https://github.com/MR-CoAP/CoAP<br /> |-<br /> | Wakaama || C || Client + Server || EPL+EDL || https://www.eclipse.org/wakaama/index.html<br /> |-<br /> | coap-node || Javascript || Client || MIT || https://github.com/PeterEB/coap-node<br /> |-<br /> | coap-shepherd || Javascript || Server || MIT || https://github.com/PeterEB/coap-shepherd<br /> |-<br /> | Californium || Java || Client + Server || EPL+EDL || https://www.eclipse.org/californium<br /> |-<br /> | nCoap || Java || Client + Server || BSD || https://github.com/okleine/nCoAP<br /> |-<br /> | leshan || Java || Client + Server || EPL+EDL || https://github.com/eclipse/leshan<br /> |-<br /> | CoAP.NET || C# || Client + Server || 3-clause BSD || https://github.com/smeshlink/CoAP.NET<br /> |-<br /> | CoAPSharp || C#, .NET || Client + Server || LGPL || http://www.coapsharp.com<br /> |-<br /> | Waher.Networking.CoAP || C# || Server || || https://github.com/PeterWaher/IoTGateway/tree/master/Networking/Waher.Networking.CoAP<br /> |-<br /> | gen_coap || Erlang || Client + Server || MPL v1.1 || https://github.com/gotthardp/gen_coap<br /> |-<br /> | go-coap || Go || Client + Server || MIT || https://github.com/go-ocf/go-coap<br /> |-<br /> | node-coap || Javascript || Client + Server || MIT || https://github.com/mcollina/node-coap<br /> |-<br /> | coap-cli || Javascript || || MIT || https://github.com/mcollina/coap-cli<br /> |-<br /> | txThings || Python (Twisted) || Client + Server || MIT || https://github.com/mwasilak/txThings<br /> |-<br /> | aiocoap || Python 3 || Client + Server || MIT || https://github.com/chrysn/aiocoap<br /> |-<br /> | CoAPthon || Python || Client + Server || MIT || https://github.com/Tanganelli/CoAPthon<br /> |-<br /> | Ruby coap || Ruby || Client || MIT || https://github.com/nning/coap<br /> |-<br /> | Ruby david || Ruby || Server || MIT || https://github.com/nning/david<br /> |-<br /> | coap-rs || Rust || Client + Server || MIT || https://github.com/Covertness/coap-rs<br /> |-<br /> | Copper || JavaScript (Browser Plugin) || Client || BSD || https://github.com/mkovatsc/Copper<br /> |-<br /> | iCoAP || Objective-C || Client || MIT || https://github.com/stuffrabbit/iCoAP<br /> |-<br /> | SwiftCoAP || Swift || Client + Server || MIT || https://github.com/stuffrabbit/SwiftCoAP<br /> |-<br /> | nCoap || Java || Client + Server || BSD || https://github.com/okleine/nCoAP<br /> |-<br /> | txThings || Python (Twisted) || Client + Server || MIT || https://github.com/mwasilak/txThings<br /> |}<br /> <br /> == Courses ==<br /> <br /> * [[Vertiefendes Wahlfach-Projekt]] (2018)<br /> <br /> == References ==<br /> * RFC 7252: https://tools.ietf.org/html/rfc7252<br /> * CoAP: RFC 7252 Constrained Application Protocol https://coap.technology/<br /> * Learning Internet of Things: https://www.oreilly.com/library/view/learning-internet-of/9781783553532/<br /> <br /> [[Category:Documentation]]</div>

Ograsl https://elvis.hcw.ac.at/wiki/index.php?title=Constrained_Application_Protocol&diff=1303 2019-03-11T22:54:01Z

<p>Ograsl: /* The Protocol */</p> <hr /> <div>The '''Constrained Application Protocol''' ('''CoAP''') is a specialized web transfer protocol, as defined in RFC 7252, for use with constrained nodes and constrained networks in the Internet of Things.<br /> The protocol is designed for machine-to-machine (M2M) applications such as smart energy and building automation.<br /> <br /> == Features ==<br /> <br /> The work on Constrained Environments aims at realizing the REST architecture in a suitable form for the most constrained nodes and networks. The nodes usually consist of 8-bit microcontrollers with limited amounts of RAM and ROM.<br /> <br /> <br /> CoAP has the following main features:<br /> <br /> * Web protocol fulfilling M2M requirements in constrained environments<br /> * UDP [RFC0768] binding with optional reliability supporting unicast and multicast requests<br /> * Asynchronous message exchanges<br /> * Low header overhead and parsing complexity<br /> * URI and Content-type support<br /> * Simple proxy and caching capabilities<br /> * Stateless HTTP mapping<br /> * Security binding to Datagram Transport Layer Security (DTLS)<br /> <br /> == The Protocol ==<br /> <br /> CoAP is similar to the client/server model of HTTP. M2M interactions typically result in a CoAP implementation acting in both client and server roles. A request is sent by a client to request an action on a resource (identified by a URI) on a server. The server then sends a response with a response code (equivalent to that of HTTP). Therefore, efficiency is very important, so CoAP uses UDP, a datagram-oriented transport.<br /> <br /> CoAP is however a single protocol, with messaging and request/response as just features of the CoAP header<br /> <br /> +----------------------+<br /> | Application |<br /> +----------------------+<br /> +----------------------+ \<br /> | Requests/Responses | |<br /> |----------------------| | CoAP<br /> | Messages | |<br /> +----------------------+ /<br /> +----------------------+<br /> | UDP |<br /> +----------------------+<br /> <br /> == Message Format ==<br /> <br /> By default, the messages are encoded in a simple binary format and transported over UDP. The message format starts with a fixed-size 4-byte header, followed by a variable-length Token value, which can be between 0 and 8 bytes long. Following the Token value comes a sequence of zero or more CoAP Options in Type-Length-Value (TLV) format, optionally followed by a payload that takes up the rest of the datagram.<br /> <br /> 0 1 2 3<br /> 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1<br /> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<br /> |Ver| T | TKL | Code | Message ID |<br /> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<br /> | Token (if any, TKL bytes) ...<br /> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<br /> | Options (if any) ...<br /> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<br /> |1 1 1 1 1 1 1 1| Payload (if any) ...<br /> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<br /> <br /> ;Version (Ver) (2 bits)<br /> :Indicates the CoAP Version number. This must set this field to 1 (binary 01). Other values are reserved for future versions.<br /> <br /> ;Type (T) (2 bits)<br /> :Indicates if this message is of type Confirmable (0), Non-confirmable (1), Acknowledgement (2), or Reset (3).<br /> <br /> ;Token Length (TKL) (4 bits)<br /> :Indicates the length of the variable-length Token field, which may be 0-8 bytes in length.<br /> <br /> ;CoAP Request/Response Code (8 bits)<br /> :Splits into a 3-bit class and 5-bit detail.<br /> <br /> ;Message ID (16 bits)<br /> :Used to detect message duplication and to match messages of type Acknowledgement/Reset to messages of type Confirmable/Non-confirmable.<br /> <br /> == Implementations ==<br /> <br /> Generic implementations are becoming availible for a variety of platforms. Implementations for constrained devices are typically written in C. CoAP is also used between them and more powerful systems such as cloud servers, home centrals, smartphones:<br /> <br /> {| class=&quot;wikitable sortable&quot;<br /> |-<br /> ! Name !! Programming Language !! Client/Server !! License !! Link<br /> |-<br /> | Erbium for Contiki || C || Client + Server || 3-clause BSD || http://www.contiki-os.org/<br /> |-<br /> | libcoap || C || Client + Server || BSD/GPL || https://libcoap.net/<br /> |-<br /> | Eclipse tinydtls || C || Client + Server || EPL+EDL || https://projects.eclipse.org/projects/iot.tinydtls<br /> |-<br /> | LibNyoci || C || Client + Server || MIT || https://github.com/darconeous/libnyoci<br /> |-<br /> | microcoap || C || Client + Server || MIT || https://github.com/1248/microcoap<br /> |-<br /> | cantcoap || C++/C || Client + Server || BSD || https://github.com/staropram/cantcoap<br /> |-<br /> | Lobaro CoAP || C || Client + Server || MIT || https://www.lobaro.com/portfolio/lobaro-coap/<br /> |-<br /> | MR-CoAP || Java || || BSD || https://github.com/MR-CoAP/CoAP<br /> |-<br /> | Wakaama || C || Client + Server || EPL+EDL || https://www.eclipse.org/wakaama/index.html<br /> |-<br /> | coap-node || Javascript || Client || MIT || https://github.com/PeterEB/coap-node<br /> |-<br /> | coap-shepherd || Javascript || Server || MIT || https://github.com/PeterEB/coap-shepherd<br /> |-<br /> | Californium || Java || Client + Server || EPL+EDL || https://www.eclipse.org/californium<br /> |-<br /> | nCoap || Java || Client + Server || BSD || https://github.com/okleine/nCoAP<br /> |-<br /> | leshan || Java || Client + Server || EPL+EDL || https://github.com/eclipse/leshan<br /> |-<br /> | CoAP.NET || C# || Client + Server || 3-clause BSD || https://github.com/smeshlink/CoAP.NET<br /> |-<br /> | CoAPSharp || C#, .NET || Client + Server || LGPL || http://www.coapsharp.com<br /> |-<br /> | Waher.Networking.CoAP || C# || Server || || https://github.com/PeterWaher/IoTGateway/tree/master/Networking/Waher.Networking.CoAP<br /> |-<br /> | gen_coap || Erlang || Client + Server || MPL v1.1 || https://github.com/gotthardp/gen_coap<br /> |-<br /> | go-coap || Go || Client + Server || MIT || https://github.com/go-ocf/go-coap<br /> |-<br /> | node-coap || Javascript || Client + Server || MIT || https://github.com/mcollina/node-coap<br /> |-<br /> | coap-cli || Javascript || || MIT || https://github.com/mcollina/coap-cli<br /> |-<br /> | txThings || Python (Twisted) || Client + Server || MIT || https://github.com/mwasilak/txThings<br /> |-<br /> | aiocoap || Python 3 || Client + Server || MIT || https://github.com/chrysn/aiocoap<br /> |-<br /> | CoAPthon || Python || Client + Server || MIT || https://github.com/Tanganelli/CoAPthon<br /> |-<br /> | Ruby coap || Ruby || Client || MIT || https://github.com/nning/coap<br /> |-<br /> | Ruby david || Ruby || Server || MIT || https://github.com/nning/david<br /> |-<br /> | coap-rs || Rust || Client + Server || MIT || https://github.com/Covertness/coap-rs<br /> |-<br /> | Copper || JavaScript (Browser Plugin) || Client || BSD || https://github.com/mkovatsc/Copper<br /> |-<br /> | iCoAP || Objective-C || Client || MIT || https://github.com/stuffrabbit/iCoAP<br /> |-<br /> | SwiftCoAP || Swift || Client + Server || MIT || https://github.com/stuffrabbit/SwiftCoAP<br /> |-<br /> | nCoap || Java || Client + Server || BSD || https://github.com/okleine/nCoAP<br /> |-<br /> | txThings || Python (Twisted) || Client + Server || MIT || https://github.com/mwasilak/txThings<br /> |}<br /> <br /> == Courses ==<br /> <br /> * [[Vertiefendes Wahlfach-Projekt]] (2018)<br /> <br /> == References ==<br /> * RFC 7252: https://tools.ietf.org/html/rfc7252<br /> * CoAP: RFC 7252 Constrained Application Protocol https://coap.technology/<br /> * Learning Internet of Things: https://www.oreilly.com/library/view/learning-internet-of/9781783553532/<br /> <br /> [[Category:Documentation]]</div>

Ograsl https://elvis.hcw.ac.at/wiki/index.php?title=Constrained_Application_Protocol&diff=1302 2019-03-11T22:53:46Z

<p>Ograsl: /* Implementations */</p> <hr /> <div>The '''Constrained Application Protocol''' ('''CoAP''') is a specialized web transfer protocol, as defined in RFC 7252, for use with constrained nodes and constrained networks in the Internet of Things.<br /> The protocol is designed for machine-to-machine (M2M) applications such as smart energy and building automation.<br /> <br /> == Features ==<br /> <br /> The work on Constrained Environments aims at realizing the REST architecture in a suitable form for the most constrained nodes and networks. The nodes usually consist of 8-bit microcontrollers with limited amounts of RAM and ROM.<br /> <br /> <br /> CoAP has the following main features:<br /> <br /> * Web protocol fulfilling M2M requirements in constrained environments<br /> * UDP [RFC0768] binding with optional reliability supporting unicast and multicast requests<br /> * Asynchronous message exchanges<br /> * Low header overhead and parsing complexity<br /> * URI and Content-type support<br /> * Simple proxy and caching capabilities<br /> * Stateless HTTP mapping<br /> * Security binding to Datagram Transport Layer Security (DTLS)<br /> <br /> == The Protocol ==<br /> <br /> CoAP is similar to the client/server model of HTTP. M2M interactions typically result in a CoAP implementation acting in both client and server roles. A request is sent by a client to request an action on a resource (identified by a URI) on a server. The server then sends a response with a response code (equivalent to that of HTTP). Therefore, efficiency is very important, so CoAP uses UDP, a datagram-oriented transport.<br /> <br /> CoAP is however a single protocol, with messaging and request/response as just features of the CoAP header<br /> <br /> +----------------------+<br /> | Application |<br /> +----------------------+<br /> +----------------------+ \<br /> | Requests/Responses | |<br /> |----------------------| | CoAP<br /> | Messages | |<br /> +----------------------+ /<br /> +----------------------+<br /> | UDP |<br /> +----------------------+<br /> <br /> [[File:Abstract_Layering_of_CoAP.JPG]]<br /> <br /> == Message Format ==<br /> <br /> By default, the messages are encoded in a simple binary format and transported over UDP. The message format starts with a fixed-size 4-byte header, followed by a variable-length Token value, which can be between 0 and 8 bytes long. Following the Token value comes a sequence of zero or more CoAP Options in Type-Length-Value (TLV) format, optionally followed by a payload that takes up the rest of the datagram.<br /> <br /> 0 1 2 3<br /> 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1<br /> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<br /> |Ver| T | TKL | Code | Message ID |<br /> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<br /> | Token (if any, TKL bytes) ...<br /> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<br /> | Options (if any) ...<br /> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<br /> |1 1 1 1 1 1 1 1| Payload (if any) ...<br /> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<br /> <br /> ;Version (Ver) (2 bits)<br /> :Indicates the CoAP Version number. This must set this field to 1 (binary 01). Other values are reserved for future versions.<br /> <br /> ;Type (T) (2 bits)<br /> :Indicates if this message is of type Confirmable (0), Non-confirmable (1), Acknowledgement (2), or Reset (3).<br /> <br /> ;Token Length (TKL) (4 bits)<br /> :Indicates the length of the variable-length Token field, which may be 0-8 bytes in length.<br /> <br /> ;CoAP Request/Response Code (8 bits)<br /> :Splits into a 3-bit class and 5-bit detail.<br /> <br /> ;Message ID (16 bits)<br /> :Used to detect message duplication and to match messages of type Acknowledgement/Reset to messages of type Confirmable/Non-confirmable.<br /> <br /> == Implementations ==<br /> <br /> Generic implementations are becoming availible for a variety of platforms. Implementations for constrained devices are typically written in C. CoAP is also used between them and more powerful systems such as cloud servers, home centrals, smartphones:<br /> <br /> {| class=&quot;wikitable sortable&quot;<br /> |-<br /> ! Name !! Programming Language !! Client/Server !! License !! Link<br /> |-<br /> | Erbium for Contiki || C || Client + Server || 3-clause BSD || http://www.contiki-os.org/<br /> |-<br /> | libcoap || C || Client + Server || BSD/GPL || https://libcoap.net/<br /> |-<br /> | Eclipse tinydtls || C || Client + Server || EPL+EDL || https://projects.eclipse.org/projects/iot.tinydtls<br /> |-<br /> | LibNyoci || C || Client + Server || MIT || https://github.com/darconeous/libnyoci<br /> |-<br /> | microcoap || C || Client + Server || MIT || https://github.com/1248/microcoap<br /> |-<br /> | cantcoap || C++/C || Client + Server || BSD || https://github.com/staropram/cantcoap<br /> |-<br /> | Lobaro CoAP || C || Client + Server || MIT || https://www.lobaro.com/portfolio/lobaro-coap/<br /> |-<br /> | MR-CoAP || Java || || BSD || https://github.com/MR-CoAP/CoAP<br /> |-<br /> | Wakaama || C || Client + Server || EPL+EDL || https://www.eclipse.org/wakaama/index.html<br /> |-<br /> | coap-node || Javascript || Client || MIT || https://github.com/PeterEB/coap-node<br /> |-<br /> | coap-shepherd || Javascript || Server || MIT || https://github.com/PeterEB/coap-shepherd<br /> |-<br /> | Californium || Java || Client + Server || EPL+EDL || https://www.eclipse.org/californium<br /> |-<br /> | nCoap || Java || Client + Server || BSD || https://github.com/okleine/nCoAP<br /> |-<br /> | leshan || Java || Client + Server || EPL+EDL || https://github.com/eclipse/leshan<br /> |-<br /> | CoAP.NET || C# || Client + Server || 3-clause BSD || https://github.com/smeshlink/CoAP.NET<br /> |-<br /> | CoAPSharp || C#, .NET || Client + Server || LGPL || http://www.coapsharp.com<br /> |-<br /> | Waher.Networking.CoAP || C# || Server || || https://github.com/PeterWaher/IoTGateway/tree/master/Networking/Waher.Networking.CoAP<br /> |-<br /> | gen_coap || Erlang || Client + Server || MPL v1.1 || https://github.com/gotthardp/gen_coap<br /> |-<br /> | go-coap || Go || Client + Server || MIT || https://github.com/go-ocf/go-coap<br /> |-<br /> | node-coap || Javascript || Client + Server || MIT || https://github.com/mcollina/node-coap<br /> |-<br /> | coap-cli || Javascript || || MIT || https://github.com/mcollina/coap-cli<br /> |-<br /> | txThings || Python (Twisted) || Client + Server || MIT || https://github.com/mwasilak/txThings<br /> |-<br /> | aiocoap || Python 3 || Client + Server || MIT || https://github.com/chrysn/aiocoap<br /> |-<br /> | CoAPthon || Python || Client + Server || MIT || https://github.com/Tanganelli/CoAPthon<br /> |-<br /> | Ruby coap || Ruby || Client || MIT || https://github.com/nning/coap<br /> |-<br /> | Ruby david || Ruby || Server || MIT || https://github.com/nning/david<br /> |-<br /> | coap-rs || Rust || Client + Server || MIT || https://github.com/Covertness/coap-rs<br /> |-<br /> | Copper || JavaScript (Browser Plugin) || Client || BSD || https://github.com/mkovatsc/Copper<br /> |-<br /> | iCoAP || Objective-C || Client || MIT || https://github.com/stuffrabbit/iCoAP<br /> |-<br /> | SwiftCoAP || Swift || Client + Server || MIT || https://github.com/stuffrabbit/SwiftCoAP<br /> |-<br /> | nCoap || Java || Client + Server || BSD || https://github.com/okleine/nCoAP<br /> |-<br /> | txThings || Python (Twisted) || Client + Server || MIT || https://github.com/mwasilak/txThings<br /> |}<br /> <br /> == Courses ==<br /> <br /> * [[Vertiefendes Wahlfach-Projekt]] (2018)<br /> <br /> == References ==<br /> * RFC 7252: https://tools.ietf.org/html/rfc7252<br /> * CoAP: RFC 7252 Constrained Application Protocol https://coap.technology/<br /> * Learning Internet of Things: https://www.oreilly.com/library/view/learning-internet-of/9781783553532/<br /> <br /> [[Category:Documentation]]</div>

Ograsl https://elvis.hcw.ac.at/wiki/index.php?title=Constrained_Application_Protocol&diff=1301 2019-03-11T22:52:48Z

<p>Ograsl: /* Implementations */</p> <hr /> <div>The '''Constrained Application Protocol''' ('''CoAP''') is a specialized web transfer protocol, as defined in RFC 7252, for use with constrained nodes and constrained networks in the Internet of Things.<br /> The protocol is designed for machine-to-machine (M2M) applications such as smart energy and building automation.<br /> <br /> == Features ==<br /> <br /> The work on Constrained Environments aims at realizing the REST architecture in a suitable form for the most constrained nodes and networks. The nodes usually consist of 8-bit microcontrollers with limited amounts of RAM and ROM.<br /> <br /> <br /> CoAP has the following main features:<br /> <br /> * Web protocol fulfilling M2M requirements in constrained environments<br /> * UDP [RFC0768] binding with optional reliability supporting unicast and multicast requests<br /> * Asynchronous message exchanges<br /> * Low header overhead and parsing complexity<br /> * URI and Content-type support<br /> * Simple proxy and caching capabilities<br /> * Stateless HTTP mapping<br /> * Security binding to Datagram Transport Layer Security (DTLS)<br /> <br /> == The Protocol ==<br /> <br /> CoAP is similar to the client/server model of HTTP. M2M interactions typically result in a CoAP implementation acting in both client and server roles. A request is sent by a client to request an action on a resource (identified by a URI) on a server. The server then sends a response with a response code (equivalent to that of HTTP). Therefore, efficiency is very important, so CoAP uses UDP, a datagram-oriented transport.<br /> <br /> CoAP is however a single protocol, with messaging and request/response as just features of the CoAP header<br /> <br /> +----------------------+<br /> | Application |<br /> +----------------------+<br /> +----------------------+ \<br /> | Requests/Responses | |<br /> |----------------------| | CoAP<br /> | Messages | |<br /> +----------------------+ /<br /> +----------------------+<br /> | UDP |<br /> +----------------------+<br /> <br /> [[File:Abstract_Layering_of_CoAP.JPG]]<br /> <br /> == Message Format ==<br /> <br /> By default, the messages are encoded in a simple binary format and transported over UDP. The message format starts with a fixed-size 4-byte header, followed by a variable-length Token value, which can be between 0 and 8 bytes long. Following the Token value comes a sequence of zero or more CoAP Options in Type-Length-Value (TLV) format, optionally followed by a payload that takes up the rest of the datagram.<br /> <br /> 0 1 2 3<br /> 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1<br /> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<br /> |Ver| T | TKL | Code | Message ID |<br /> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<br /> | Token (if any, TKL bytes) ...<br /> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<br /> | Options (if any) ...<br /> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<br /> |1 1 1 1 1 1 1 1| Payload (if any) ...<br /> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<br /> <br /> ;Version (Ver) (2 bits)<br /> :Indicates the CoAP Version number. This must set this field to 1 (binary 01). Other values are reserved for future versions.<br /> <br /> ;Type (T) (2 bits)<br /> :Indicates if this message is of type Confirmable (0), Non-confirmable (1), Acknowledgement (2), or Reset (3).<br /> <br /> ;Token Length (TKL) (4 bits)<br /> :Indicates the length of the variable-length Token field, which may be 0-8 bytes in length.<br /> <br /> ;CoAP Request/Response Code (8 bits)<br /> :Splits into a 3-bit class and 5-bit detail.<br /> <br /> ;Message ID (16 bits)<br /> :Used to detect message duplication and to match messages of type Acknowledgement/Reset to messages of type Confirmable/Non-confirmable.<br /> <br /> == Implementations ==<br /> <br /> Generic implementations are becoming availible for a variety of platforms.<br /> <br /> {| class=&quot;wikitable sortable&quot;<br /> |-<br /> ! Name !! Programming Language !! Client/Server !! License !! Link<br /> |-<br /> | Erbium for Contiki || C || Client + Server || 3-clause BSD || http://www.contiki-os.org/<br /> |-<br /> | libcoap || C || Client + Server || BSD/GPL || https://libcoap.net/<br /> |-<br /> | Eclipse tinydtls || C || Client + Server || EPL+EDL || https://projects.eclipse.org/projects/iot.tinydtls<br /> |-<br /> | LibNyoci || C || Client + Server || MIT || https://github.com/darconeous/libnyoci<br /> |-<br /> | microcoap || C || Client + Server || MIT || https://github.com/1248/microcoap<br /> |-<br /> | cantcoap || C++/C || Client + Server || BSD || https://github.com/staropram/cantcoap<br /> |-<br /> | Lobaro CoAP || C || Client + Server || MIT || https://www.lobaro.com/portfolio/lobaro-coap/<br /> |-<br /> | MR-CoAP || Java || || BSD || https://github.com/MR-CoAP/CoAP<br /> |-<br /> | Wakaama || C || Client + Server || EPL+EDL || https://www.eclipse.org/wakaama/index.html<br /> |-<br /> | coap-node || Javascript || Client || MIT || https://github.com/PeterEB/coap-node<br /> |-<br /> | coap-shepherd || Javascript || Server || MIT || https://github.com/PeterEB/coap-shepherd<br /> |-<br /> | Californium || Java || Client + Server || EPL+EDL || https://www.eclipse.org/californium<br /> |-<br /> | nCoap || Java || Client + Server || BSD || https://github.com/okleine/nCoAP<br /> |-<br /> | leshan || Java || Client + Server || EPL+EDL || https://github.com/eclipse/leshan<br /> |-<br /> | CoAP.NET || C# || Client + Server || 3-clause BSD || https://github.com/smeshlink/CoAP.NET<br /> |-<br /> | CoAPSharp || C#, .NET || Client + Server || LGPL || http://www.coapsharp.com<br /> |-<br /> | Waher.Networking.CoAP || C# || Server || || https://github.com/PeterWaher/IoTGateway/tree/master/Networking/Waher.Networking.CoAP<br /> |-<br /> | gen_coap || Erlang || Client + Server || MPL v1.1 || https://github.com/gotthardp/gen_coap<br /> |-<br /> | go-coap || Go || Client + Server || MIT || https://github.com/go-ocf/go-coap<br /> |-<br /> | node-coap || Javascript || Client + Server || MIT || https://github.com/mcollina/node-coap<br /> |-<br /> | coap-cli || Javascript || || MIT || https://github.com/mcollina/coap-cli<br /> |-<br /> | txThings || Python (Twisted) || Client + Server || MIT || https://github.com/mwasilak/txThings<br /> |-<br /> | aiocoap || Python 3 || Client + Server || MIT || https://github.com/chrysn/aiocoap<br /> |-<br /> | CoAPthon || Python || Client + Server || MIT || https://github.com/Tanganelli/CoAPthon<br /> |-<br /> | Ruby coap || Ruby || Client || MIT || https://github.com/nning/coap<br /> |-<br /> | Ruby david || Ruby || Server || MIT || https://github.com/nning/david<br /> |-<br /> | coap-rs || Rust || Client + Server || MIT || https://github.com/Covertness/coap-rs<br /> |-<br /> | Copper || JavaScript (Browser Plugin) || Client || BSD || https://github.com/mkovatsc/Copper<br /> |-<br /> | iCoAP || Objective-C || Client || MIT || https://github.com/stuffrabbit/iCoAP<br /> |-<br /> | SwiftCoAP || Swift || Client + Server || MIT || https://github.com/stuffrabbit/SwiftCoAP<br /> |-<br /> | nCoap || Java || Client + Server || BSD || https://github.com/okleine/nCoAP<br /> |-<br /> | txThings || Python (Twisted) || Client + Server || MIT || https://github.com/mwasilak/txThings<br /> |}<br /> <br /> == Courses ==<br /> <br /> * [[Vertiefendes Wahlfach-Projekt]] (2018)<br /> <br /> == References ==<br /> * RFC 7252: https://tools.ietf.org/html/rfc7252<br /> * CoAP: RFC 7252 Constrained Application Protocol https://coap.technology/<br /> * Learning Internet of Things: https://www.oreilly.com/library/view/learning-internet-of/9781783553532/<br /> <br /> [[Category:Documentation]]</div>

Ograsl https://elvis.hcw.ac.at/wiki/index.php?title=Constrained_Application_Protocol&diff=1300 2019-03-11T22:52:17Z

<p>Ograsl: /* Constrained Devices */</p> <hr /> <div>The '''Constrained Application Protocol''' ('''CoAP''') is a specialized web transfer protocol, as defined in RFC 7252, for use with constrained nodes and constrained networks in the Internet of Things.<br /> The protocol is designed for machine-to-machine (M2M) applications such as smart energy and building automation.<br /> <br /> == Features ==<br /> <br /> The work on Constrained Environments aims at realizing the REST architecture in a suitable form for the most constrained nodes and networks. The nodes usually consist of 8-bit microcontrollers with limited amounts of RAM and ROM.<br /> <br /> <br /> CoAP has the following main features:<br /> <br /> * Web protocol fulfilling M2M requirements in constrained environments<br /> * UDP [RFC0768] binding with optional reliability supporting unicast and multicast requests<br /> * Asynchronous message exchanges<br /> * Low header overhead and parsing complexity<br /> * URI and Content-type support<br /> * Simple proxy and caching capabilities<br /> * Stateless HTTP mapping<br /> * Security binding to Datagram Transport Layer Security (DTLS)<br /> <br /> == The Protocol ==<br /> <br /> CoAP is similar to the client/server model of HTTP. M2M interactions typically result in a CoAP implementation acting in both client and server roles. A request is sent by a client to request an action on a resource (identified by a URI) on a server. The server then sends a response with a response code (equivalent to that of HTTP). Therefore, efficiency is very important, so CoAP uses UDP, a datagram-oriented transport.<br /> <br /> CoAP is however a single protocol, with messaging and request/response as just features of the CoAP header<br /> <br /> +----------------------+<br /> | Application |<br /> +----------------------+<br /> +----------------------+ \<br /> | Requests/Responses | |<br /> |----------------------| | CoAP<br /> | Messages | |<br /> +----------------------+ /<br /> +----------------------+<br /> | UDP |<br /> +----------------------+<br /> <br /> [[File:Abstract_Layering_of_CoAP.JPG]]<br /> <br /> == Message Format ==<br /> <br /> By default, the messages are encoded in a simple binary format and transported over UDP. The message format starts with a fixed-size 4-byte header, followed by a variable-length Token value, which can be between 0 and 8 bytes long. Following the Token value comes a sequence of zero or more CoAP Options in Type-Length-Value (TLV) format, optionally followed by a payload that takes up the rest of the datagram.<br /> <br /> 0 1 2 3<br /> 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1<br /> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<br /> |Ver| T | TKL | Code | Message ID |<br /> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<br /> | Token (if any, TKL bytes) ...<br /> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<br /> | Options (if any) ...<br /> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<br /> |1 1 1 1 1 1 1 1| Payload (if any) ...<br /> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<br /> <br /> ;Version (Ver) (2 bits)<br /> :Indicates the CoAP Version number. This must set this field to 1 (binary 01). Other values are reserved for future versions.<br /> <br /> ;Type (T) (2 bits)<br /> :Indicates if this message is of type Confirmable (0), Non-confirmable (1), Acknowledgement (2), or Reset (3).<br /> <br /> ;Token Length (TKL) (4 bits)<br /> :Indicates the length of the variable-length Token field, which may be 0-8 bytes in length.<br /> <br /> ;CoAP Request/Response Code (8 bits)<br /> :Splits into a 3-bit class and 5-bit detail.<br /> <br /> ;Message ID (16 bits)<br /> :Used to detect message duplication and to match messages of type Acknowledgement/Reset to messages of type Confirmable/Non-confirmable.<br /> <br /> == Implementations ==<br /> <br /> Generic implementations are becoming availible for a variety of platforms.<br /> <br /> === Constrained Devices ===<br /> <br /> {| class=&quot;wikitable sortable&quot;<br /> |-<br /> ! Name !! Programming Language !! Client/Server !! License !! Link<br /> |-<br /> | Erbium for Contiki || C || Client + Server || 3-clause BSD || http://www.contiki-os.org/<br /> |-<br /> | libcoap || C || Client + Server || BSD/GPL || https://libcoap.net/<br /> |-<br /> | Eclipse tinydtls || C || Client + Server || EPL+EDL || https://projects.eclipse.org/projects/iot.tinydtls<br /> |-<br /> | LibNyoci || C || Client + Server || MIT || https://github.com/darconeous/libnyoci<br /> |-<br /> | microcoap || C || Client + Server || MIT || https://github.com/1248/microcoap<br /> |-<br /> | cantcoap || C++/C || Client + Server || BSD || https://github.com/staropram/cantcoap<br /> |-<br /> | Lobaro CoAP || C || Client + Server || MIT || https://www.lobaro.com/portfolio/lobaro-coap/<br /> |-<br /> | MR-CoAP || Java || || BSD || https://github.com/MR-CoAP/CoAP<br /> |-<br /> | Wakaama || C || Client + Server || EPL+EDL || https://www.eclipse.org/wakaama/index.html<br /> |-<br /> | coap-node || Javascript || Client || MIT || https://github.com/PeterEB/coap-node<br /> |-<br /> | coap-shepherd || Javascript || Server || MIT || https://github.com/PeterEB/coap-shepherd<br /> |-<br /> | Californium || Java || Client + Server || EPL+EDL || https://www.eclipse.org/californium<br /> |-<br /> | nCoap || Java || Client + Server || BSD || https://github.com/okleine/nCoAP<br /> |-<br /> | leshan || Java || Client + Server || EPL+EDL || https://github.com/eclipse/leshan<br /> |-<br /> | CoAP.NET || C# || Client + Server || 3-clause BSD || https://github.com/smeshlink/CoAP.NET<br /> |-<br /> | CoAPSharp || C#, .NET || Client + Server || LGPL || http://www.coapsharp.com<br /> |-<br /> | Waher.Networking.CoAP || C# || Server || || https://github.com/PeterWaher/IoTGateway/tree/master/Networking/Waher.Networking.CoAP<br /> |-<br /> | gen_coap || Erlang || Client + Server || MPL v1.1 || https://github.com/gotthardp/gen_coap<br /> |-<br /> | go-coap || Go || Client + Server || MIT || https://github.com/go-ocf/go-coap<br /> |-<br /> | node-coap || Javascript || Client + Server || MIT || https://github.com/mcollina/node-coap<br /> |-<br /> | coap-cli || Javascript || || MIT || https://github.com/mcollina/coap-cli<br /> |-<br /> | txThings || Python (Twisted) || Client + Server || MIT || https://github.com/mwasilak/txThings<br /> |-<br /> | aiocoap || Python 3 || Client + Server || MIT || https://github.com/chrysn/aiocoap<br /> |-<br /> | CoAPthon || Python || Client + Server || MIT || https://github.com/Tanganelli/CoAPthon<br /> |-<br /> | Ruby coap || Ruby || Client || MIT || https://github.com/nning/coap<br /> |-<br /> | Ruby david || Ruby || Server || MIT || https://github.com/nning/david<br /> |-<br /> | coap-rs || Rust || Client + Server || MIT || https://github.com/Covertness/coap-rs<br /> |-<br /> | Copper || JavaScript (Browser Plugin) || Client || BSD || https://github.com/mkovatsc/Copper<br /> |-<br /> | iCoAP || Objective-C || Client || MIT || https://github.com/stuffrabbit/iCoAP<br /> |-<br /> | SwiftCoAP || Swift || Client + Server || MIT || https://github.com/stuffrabbit/SwiftCoAP<br /> |-<br /> | nCoap || Java || Client + Server || BSD || https://github.com/okleine/nCoAP<br /> |-<br /> | txThings || Python (Twisted) || Client + Server || MIT || https://github.com/mwasilak/txThings<br /> |}<br /> <br /> == Courses ==<br /> <br /> * [[Vertiefendes Wahlfach-Projekt]] (2018)<br /> <br /> == References ==<br /> * RFC 7252: https://tools.ietf.org/html/rfc7252<br /> * CoAP: RFC 7252 Constrained Application Protocol https://coap.technology/<br /> * Learning Internet of Things: https://www.oreilly.com/library/view/learning-internet-of/9781783553532/<br /> <br /> [[Category:Documentation]]</div>

Ograsl https://elvis.hcw.ac.at/wiki/index.php?title=Constrained_Application_Protocol&diff=1299 2019-03-11T22:51:01Z

<p>Ograsl: /* Constrained Devices */</p> <hr /> <div>The '''Constrained Application Protocol''' ('''CoAP''') is a specialized web transfer protocol, as defined in RFC 7252, for use with constrained nodes and constrained networks in the Internet of Things.<br /> The protocol is designed for machine-to-machine (M2M) applications such as smart energy and building automation.<br /> <br /> == Features ==<br /> <br /> The work on Constrained Environments aims at realizing the REST architecture in a suitable form for the most constrained nodes and networks. The nodes usually consist of 8-bit microcontrollers with limited amounts of RAM and ROM.<br /> <br /> <br /> CoAP has the following main features:<br /> <br /> * Web protocol fulfilling M2M requirements in constrained environments<br /> * UDP [RFC0768] binding with optional reliability supporting unicast and multicast requests<br /> * Asynchronous message exchanges<br /> * Low header overhead and parsing complexity<br /> * URI and Content-type support<br /> * Simple proxy and caching capabilities<br /> * Stateless HTTP mapping<br /> * Security binding to Datagram Transport Layer Security (DTLS)<br /> <br /> == The Protocol ==<br /> <br /> CoAP is similar to the client/server model of HTTP. M2M interactions typically result in a CoAP implementation acting in both client and server roles. A request is sent by a client to request an action on a resource (identified by a URI) on a server. The server then sends a response with a response code (equivalent to that of HTTP). Therefore, efficiency is very important, so CoAP uses UDP, a datagram-oriented transport.<br /> <br /> CoAP is however a single protocol, with messaging and request/response as just features of the CoAP header<br /> <br /> +----------------------+<br /> | Application |<br /> +----------------------+<br /> +----------------------+ \<br /> | Requests/Responses | |<br /> |----------------------| | CoAP<br /> | Messages | |<br /> +----------------------+ /<br /> +----------------------+<br /> | UDP |<br /> +----------------------+<br /> <br /> [[File:Abstract_Layering_of_CoAP.JPG]]<br /> <br /> == Message Format ==<br /> <br /> By default, the messages are encoded in a simple binary format and transported over UDP. The message format starts with a fixed-size 4-byte header, followed by a variable-length Token value, which can be between 0 and 8 bytes long. Following the Token value comes a sequence of zero or more CoAP Options in Type-Length-Value (TLV) format, optionally followed by a payload that takes up the rest of the datagram.<br /> <br /> 0 1 2 3<br /> 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1<br /> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<br /> |Ver| T | TKL | Code | Message ID |<br /> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<br /> | Token (if any, TKL bytes) ...<br /> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<br /> | Options (if any) ...<br /> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<br /> |1 1 1 1 1 1 1 1| Payload (if any) ...<br /> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<br /> <br /> ;Version (Ver) (2 bits)<br /> :Indicates the CoAP Version number. This must set this field to 1 (binary 01). Other values are reserved for future versions.<br /> <br /> ;Type (T) (2 bits)<br /> :Indicates if this message is of type Confirmable (0), Non-confirmable (1), Acknowledgement (2), or Reset (3).<br /> <br /> ;Token Length (TKL) (4 bits)<br /> :Indicates the length of the variable-length Token field, which may be 0-8 bytes in length.<br /> <br /> ;CoAP Request/Response Code (8 bits)<br /> :Splits into a 3-bit class and 5-bit detail.<br /> <br /> ;Message ID (16 bits)<br /> :Used to detect message duplication and to match messages of type Acknowledgement/Reset to messages of type Confirmable/Non-confirmable.<br /> <br /> == Implementations ==<br /> <br /> Generic implementations are becoming availible for a variety of platforms.<br /> <br /> === Constrained Devices ===<br /> <br /> {| class=&quot;wikitable sortable&quot;<br /> |-<br /> ! Name !! Programming Language !! Client/Server !! License !! Link<br /> |-<br /> | Erbium for Contiki || C || Client + Server || 3-clause BSD || http://www.contiki-os.org/<br /> |-<br /> | libcoap || C || Client + Server || BSD/GPL || https://libcoap.net/<br /> |-<br /> | Eclipse tinydtls || C || Client + Server || EPL+EDL || https://projects.eclipse.org/projects/iot.tinydtls<br /> |-<br /> | LibNyoci || C || Client + Server || MIT || https://github.com/darconeous/libnyoci<br /> |-<br /> | microcoap || C || Client + Server || MIT || https://github.com/1248/microcoap<br /> |-<br /> | cantcoap || C++/C || Client + Server || BSD || https://github.com/staropram/cantcoap<br /> |-<br /> | Lobaro CoAP || C || Client + Server || MIT || https://www.lobaro.com/portfolio/lobaro-coap/<br /> |-<br /> | MR-CoAP || Java || || BSD || https://github.com/MR-CoAP/CoAP<br /> |-<br /> | Wakaama || C || Client + Server || EPL+EDL || https://www.eclipse.org/wakaama/index.html<br /> |-<br /> | coap-node || Javascript || Client || MIT || https://github.com/PeterEB/coap-node<br /> |-<br /> | coap-shepherd || Javascript || Server || MIT || https://github.com/PeterEB/coap-shepherd<br /> |-<br /> | Californium || Java || Client + Server || EPL+EDL || https://www.eclipse.org/californium<br /> |-<br /> | nCoap || Java || Client + Server || BSD || https://github.com/okleine/nCoAP<br /> |-<br /> | leshan || Java || Client + Server || EPL+EDL || https://github.com/eclipse/leshan<br /> |-<br /> | CoAP.NET || C# || Client + Server || 3-clause BSD || https://github.com/smeshlink/CoAP.NET<br /> |-<br /> | CoAPSharp || C#, .NET || Client + Server || LGPL || http://www.coapsharp.com<br /> |-<br /> | Waher.Networking.CoAP || C# || Server || || https://github.com/PeterWaher/IoTGateway/tree/master/Networking/Waher.Networking.CoAP<br /> |-<br /> | gen_coap || Erlang || Client + Server || MPL v1.1 || https://github.com/gotthardp/gen_coap<br /> |-<br /> | go-coap || Go || Client + Server || MIT || https://github.com/go-ocf/go-coap<br /> |-<br /> | node-coap || Javascript || Client + Server || MIT || https://github.com/mcollina/node-coap<br /> |-<br /> | coap-cli || Javascript || || MIT || https://github.com/mcollina/coap-cli<br /> |-<br /> | txThings || Python (Twisted) || Client + Server || MIT || https://github.com/mwasilak/txThings<br /> |-<br /> | aiocoap || Python 3 || Client + Server || MIT || https://github.com/chrysn/aiocoap<br /> |-<br /> | CoAPthon || Python || Client + Server || MIT || https://github.com/Tanganelli/CoAPthon<br /> |-<br /> | Ruby coap || Ruby || Client || MIT || https://github.com/nning/coap<br /> |-<br /> | Ruby david || Ruby || Server || MIT || https://github.com/nning/david<br /> |-<br /> | coap-rs || Rust || Client + Server || MIT || https://github.com/Covertness/coap-rs<br /> |-<br /> | Copper || JavaScript (Browser Plugin) || Client || BSD || https://github.com/mkovatsc/Copper<br /> |-<br /> | iCoAP || Objective-C || Client || MIT || https://github.com/stuffrabbit/iCoAP<br /> |-<br /> | SwiftCoAP || Swift | Client + Server || MIT || https://github.com/stuffrabbit/SwiftCoAP<br /> |-<br /> | nCoap || Java || Client + Server || BSD || https://github.com/okleine/nCoAP<br /> |-<br /> | txThings || Python (Twisted) || Client + Server || MIT || https://github.com/mwasilak/txThings<br /> |}<br /> <br /> == Courses ==<br /> <br /> * [[Vertiefendes Wahlfach-Projekt]] (2018)<br /> <br /> == References ==<br /> * RFC 7252: https://tools.ietf.org/html/rfc7252<br /> * CoAP: RFC 7252 Constrained Application Protocol https://coap.technology/<br /> * Learning Internet of Things: https://www.oreilly.com/library/view/learning-internet-of/9781783553532/<br /> <br /> [[Category:Documentation]]</div>

Ograsl https://elvis.hcw.ac.at/wiki/index.php?title=Constrained_Application_Protocol&diff=1298 2019-03-11T22:48:52Z

<p>Ograsl: /* Implementations */</p> <hr /> <div>The '''Constrained Application Protocol''' ('''CoAP''') is a specialized web transfer protocol, as defined in RFC 7252, for use with constrained nodes and constrained networks in the Internet of Things.<br /> The protocol is designed for machine-to-machine (M2M) applications such as smart energy and building automation.<br /> <br /> == Features ==<br /> <br /> The work on Constrained Environments aims at realizing the REST architecture in a suitable form for the most constrained nodes and networks. The nodes usually consist of 8-bit microcontrollers with limited amounts of RAM and ROM.<br /> <br /> <br /> CoAP has the following main features:<br /> <br /> * Web protocol fulfilling M2M requirements in constrained environments<br /> * UDP [RFC0768] binding with optional reliability supporting unicast and multicast requests<br /> * Asynchronous message exchanges<br /> * Low header overhead and parsing complexity<br /> * URI and Content-type support<br /> * Simple proxy and caching capabilities<br /> * Stateless HTTP mapping<br /> * Security binding to Datagram Transport Layer Security (DTLS)<br /> <br /> == The Protocol ==<br /> <br /> CoAP is similar to the client/server model of HTTP. M2M interactions typically result in a CoAP implementation acting in both client and server roles. A request is sent by a client to request an action on a resource (identified by a URI) on a server. The server then sends a response with a response code (equivalent to that of HTTP). Therefore, efficiency is very important, so CoAP uses UDP, a datagram-oriented transport.<br /> <br /> CoAP is however a single protocol, with messaging and request/response as just features of the CoAP header<br /> <br /> +----------------------+<br /> | Application |<br /> +----------------------+<br /> +----------------------+ \<br /> | Requests/Responses | |<br /> |----------------------| | CoAP<br /> | Messages | |<br /> +----------------------+ /<br /> +----------------------+<br /> | UDP |<br /> +----------------------+<br /> <br /> [[File:Abstract_Layering_of_CoAP.JPG]]<br /> <br /> == Message Format ==<br /> <br /> By default, the messages are encoded in a simple binary format and transported over UDP. The message format starts with a fixed-size 4-byte header, followed by a variable-length Token value, which can be between 0 and 8 bytes long. Following the Token value comes a sequence of zero or more CoAP Options in Type-Length-Value (TLV) format, optionally followed by a payload that takes up the rest of the datagram.<br /> <br /> 0 1 2 3<br /> 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1<br /> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<br /> |Ver| T | TKL | Code | Message ID |<br /> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<br /> | Token (if any, TKL bytes) ...<br /> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<br /> | Options (if any) ...<br /> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<br /> |1 1 1 1 1 1 1 1| Payload (if any) ...<br /> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<br /> <br /> ;Version (Ver) (2 bits)<br /> :Indicates the CoAP Version number. This must set this field to 1 (binary 01). Other values are reserved for future versions.<br /> <br /> ;Type (T) (2 bits)<br /> :Indicates if this message is of type Confirmable (0), Non-confirmable (1), Acknowledgement (2), or Reset (3).<br /> <br /> ;Token Length (TKL) (4 bits)<br /> :Indicates the length of the variable-length Token field, which may be 0-8 bytes in length.<br /> <br /> ;CoAP Request/Response Code (8 bits)<br /> :Splits into a 3-bit class and 5-bit detail.<br /> <br /> ;Message ID (16 bits)<br /> :Used to detect message duplication and to match messages of type Acknowledgement/Reset to messages of type Confirmable/Non-confirmable.<br /> <br /> == Implementations ==<br /> <br /> Generic implementations are becoming availible for a variety of platforms.<br /> <br /> === Constrained Devices ===<br /> <br /> {| class=&quot;wikitable sortable&quot;<br /> |-<br /> ! Name !! Programming Language !! Client/Server !! License !! Link<br /> |-<br /> | Erbium for Contiki || C || Client + Server || 3-clause BSD || http://www.contiki-os.org/<br /> |-<br /> | libcoap || C || Client + Server || BSD/GPL || https://libcoap.net/<br /> |-<br /> | Eclipse tinydtls || Client + Server || EPL+EDL || https://projects.eclipse.org/projects/iot.tinydtls<br /> |-<br /> | LibNyoci || C || Client + Server || MIT || https://github.com/darconeous/libnyoci<br /> |-<br /> | microcoap || C || Client + Server || MIT || https://github.com/1248/microcoap<br /> |-<br /> | cantcoap || C++/C || Client + Server || BSD || https://github.com/staropram/cantcoap<br /> |-<br /> | Lobaro CoAP || C || Client + Server || MIT || https://www.lobaro.com/portfolio/lobaro-coap/<br /> |-<br /> | MR-CoAP || Java || || BSD || https://github.com/MR-CoAP/CoAP<br /> |-<br /> | Wakaama || C || Client + Server || EPL+EDL || https://www.eclipse.org/wakaama/index.html<br /> |-<br /> | coap-node || Javascript || Client || MIT || https://github.com/PeterEB/coap-node<br /> |-<br /> | coap-shepherd || Javascript || Server || MIT || https://github.com/PeterEB/coap-shepherd<br /> |-<br /> | Californium || Java || Client + Server || EPL+EDL || https://www.eclipse.org/californium<br /> |-<br /> | nCoap || Java || Client + Server || BSD || https://github.com/okleine/nCoAP<br /> |-<br /> | leshan || Java || Client + Server || EPL+EDL || https://github.com/eclipse/leshan<br /> |-<br /> | CoAP.NET || C# || Client + Server || 3-clause BSD || https://github.com/smeshlink/CoAP.NET<br /> |-<br /> | CoAPSharp || C#, .NET || Client + Server || LGPL || http://www.coapsharp.com<br /> |-<br /> | Waher.Networking.CoAP || C# || Server || || https://github.com/PeterWaher/IoTGateway/tree/master/Networking/Waher.Networking.CoAP<br /> |-<br /> | gen_coap || Erlang || Client + Server || MPL v1.1 || https://github.com/gotthardp/gen_coap<br /> |-<br /> | go-coap || Go || Client + Server || MIT || https://github.com/go-ocf/go-coap<br /> |-<br /> | node-coap || Javascript || Client + Server || MIT || https://github.com/mcollina/node-coap<br /> |-<br /> | coap-cli || Javascript || || MIT || https://github.com/mcollina/coap-cli<br /> |-<br /> | txThings || Python (Twisted) || Client + Server || MIT || https://github.com/mwasilak/txThings<br /> |-<br /> | aiocoap || Python 3 || Client + Server || MIT || https://github.com/chrysn/aiocoap<br /> |-<br /> | CoAPthon || Python || Client + Server || MIT || https://github.com/Tanganelli/CoAPthon<br /> |-<br /> | Ruby coap || Ruby || Client || MIT || https://github.com/nning/coap<br /> |-<br /> | Ruby david || Ruby || Server || MIT || https://github.com/nning/david<br /> |-<br /> | coap-rs || Rust || Client + Server || MIT || https://github.com/Covertness/coap-rs<br /> |-<br /> | Copper || JavaScript (Browser Plugin) || Client || BSD || https://github.com/mkovatsc/Copper<br /> |-<br /> | iCoAP || Objective-C || Client || MIT || https://github.com/stuffrabbit/iCoAP<br /> |-<br /> | SwiftCoAP || Swift | Client + Server || MIT || https://github.com/stuffrabbit/SwiftCoAP<br /> |-<br /> | nCoap || Java || Client + Server || BSD || https://github.com/okleine/nCoAP<br /> |-<br /> | txThings || Python (Twisted) || Client + Server || MIT || https://github.com/mwasilak/txThings<br /> |}<br /> <br /> == Courses ==<br /> <br /> * [[Vertiefendes Wahlfach-Projekt]] (2018)<br /> <br /> == References ==<br /> * RFC 7252: https://tools.ietf.org/html/rfc7252<br /> * CoAP: RFC 7252 Constrained Application Protocol https://coap.technology/<br /> * Learning Internet of Things: https://www.oreilly.com/library/view/learning-internet-of/9781783553532/<br /> <br /> [[Category:Documentation]]</div>

Ograsl https://elvis.hcw.ac.at/wiki/index.php?title=Constrained_Application_Protocol&diff=1297 2019-03-11T22:39:29Z

<p>Ograsl: /* Server-side */</p> <hr /> <div>The '''Constrained Application Protocol''' ('''CoAP''') is a specialized web transfer protocol, as defined in RFC 7252, for use with constrained nodes and constrained networks in the Internet of Things.<br /> The protocol is designed for machine-to-machine (M2M) applications such as smart energy and building automation.<br /> <br /> == Features ==<br /> <br /> The work on Constrained Environments aims at realizing the REST architecture in a suitable form for the most constrained nodes and networks. The nodes usually consist of 8-bit microcontrollers with limited amounts of RAM and ROM.<br /> <br /> <br /> CoAP has the following main features:<br /> <br /> * Web protocol fulfilling M2M requirements in constrained environments<br /> * UDP [RFC0768] binding with optional reliability supporting unicast and multicast requests<br /> * Asynchronous message exchanges<br /> * Low header overhead and parsing complexity<br /> * URI and Content-type support<br /> * Simple proxy and caching capabilities<br /> * Stateless HTTP mapping<br /> * Security binding to Datagram Transport Layer Security (DTLS)<br /> <br /> == The Protocol ==<br /> <br /> CoAP is similar to the client/server model of HTTP. M2M interactions typically result in a CoAP implementation acting in both client and server roles. A request is sent by a client to request an action on a resource (identified by a URI) on a server. The server then sends a response with a response code (equivalent to that of HTTP). Therefore, efficiency is very important, so CoAP uses UDP, a datagram-oriented transport.<br /> <br /> CoAP is however a single protocol, with messaging and request/response as just features of the CoAP header<br /> <br /> +----------------------+<br /> | Application |<br /> +----------------------+<br /> +----------------------+ \<br /> | Requests/Responses | |<br /> |----------------------| | CoAP<br /> | Messages | |<br /> +----------------------+ /<br /> +----------------------+<br /> | UDP |<br /> +----------------------+<br /> <br /> [[File:Abstract_Layering_of_CoAP.JPG]]<br /> <br /> == Message Format ==<br /> <br /> By default, the messages are encoded in a simple binary format and transported over UDP. The message format starts with a fixed-size 4-byte header, followed by a variable-length Token value, which can be between 0 and 8 bytes long. Following the Token value comes a sequence of zero or more CoAP Options in Type-Length-Value (TLV) format, optionally followed by a payload that takes up the rest of the datagram.<br /> <br /> 0 1 2 3<br /> 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1<br /> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<br /> |Ver| T | TKL | Code | Message ID |<br /> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<br /> | Token (if any, TKL bytes) ...<br /> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<br /> | Options (if any) ...<br /> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<br /> |1 1 1 1 1 1 1 1| Payload (if any) ...<br /> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<br /> <br /> ;Version (Ver) (2 bits)<br /> :Indicates the CoAP Version number. This must set this field to 1 (binary 01). Other values are reserved for future versions.<br /> <br /> ;Type (T) (2 bits)<br /> :Indicates if this message is of type Confirmable (0), Non-confirmable (1), Acknowledgement (2), or Reset (3).<br /> <br /> ;Token Length (TKL) (4 bits)<br /> :Indicates the length of the variable-length Token field, which may be 0-8 bytes in length.<br /> <br /> ;CoAP Request/Response Code (8 bits)<br /> :Splits into a 3-bit class and 5-bit detail.<br /> <br /> ;Message ID (16 bits)<br /> :Used to detect message duplication and to match messages of type Acknowledgement/Reset to messages of type Confirmable/Non-confirmable.<br /> <br /> == Implementations ==<br /> <br /> Generic implementations are becoming availible for a variety of platforms.<br /> <br /> === Constrained Devices ===<br /> <br /> {| class=&quot;wikitable sortable&quot;<br /> |-<br /> ! Name !! Programming Language !! Client/Server !! License !! Link<br /> |-<br /> | Erbium for Contiki || C || Client + Server || 3-clause BSD || http://www.contiki-os.org/<br /> |-<br /> | libcoap || C || Client + Server || BSD/GPL || https://libcoap.net/<br /> |-<br /> | Eclipse tinydtls || Client + Server || EPL+EDL || https://projects.eclipse.org/projects/iot.tinydtls<br /> |-<br /> | LibNyoci || C || Client + Server || MIT || https://github.com/darconeous/libnyoci<br /> |-<br /> | microcoap || C || Client + Server || MIT || https://github.com/1248/microcoap<br /> |-<br /> | cantcoap || C++/C || Client + Server || BSD || https://github.com/staropram/cantcoap<br /> |-<br /> | Lobaro CoAP || C || Client + Server || MIT || https://www.lobaro.com/portfolio/lobaro-coap/<br /> |-<br /> | MR-CoAP || Java || || BSD || https://github.com/MR-CoAP/CoAP<br /> |-<br /> | Wakaama || C || Client + Server || EPL+EDL || https://www.eclipse.org/wakaama/index.html<br /> |-<br /> | coap-node || Javascript || Client || MIT || https://github.com/PeterEB/coap-node<br /> |-<br /> | coap-shepherd || Javascript || Server || MIT || https://github.com/PeterEB/coap-shepherd<br /> |}<br /> <br /> === Server-side ===<br /> <br /> CoAP is not only used between constrained devices, but also between them and more powerful systems such as cloud servers, home centrals, smartphones:<br /> <br /> {| class=&quot;wikitable sortable&quot;<br /> |-<br /> ! Name !! Programming Language !! Client/Server !! License !! Link<br /> |-<br /> | Californium || Java || Client + Server || EPL+EDL || https://www.eclipse.org/californium<br /> |-<br /> | nCoap || Java || Client + Server || BSD || https://github.com/okleine/nCoAP<br /> |-<br /> | leshan || Java || Client + Server || EPL+EDL || https://github.com/eclipse/leshan<br /> |-<br /> | CoAP.NET || C# || Client + Server || 3-clause BSD || https://github.com/smeshlink/CoAP.NET<br /> |-<br /> | CoAPSharp || C#, .NET || Client + Server || LGPL || http://www.coapsharp.com<br /> |-<br /> | Waher.Networking.CoAP || C# || Server || || https://github.com/PeterWaher/IoTGateway/tree/master/Networking/Waher.Networking.CoAP<br /> |-<br /> | gen_coap || Erlang || Client + Server || MPL v1.1 || https://github.com/gotthardp/gen_coap<br /> |-<br /> | go-coap || Go || Client + Server || MIT || https://github.com/go-ocf/go-coap<br /> |-<br /> | node-coap || Javascript || Client + Server || MIT || https://github.com/mcollina/node-coap<br /> |-<br /> | coap-cli || Javascript || || MIT || https://github.com/mcollina/coap-cli<br /> |-<br /> | txThings || Python (Twisted) || Client + Server || MIT || https://github.com/mwasilak/txThings<br /> |-<br /> | aiocoap || Python 3 || Client + Server || MIT || https://github.com/chrysn/aiocoap<br /> |-<br /> | CoAPthon || Python || Client + Server || MIT || https://github.com/Tanganelli/CoAPthon<br /> |-<br /> | Ruby coap || Ruby || Client || MIT || https://github.com/nning/coap<br /> |-<br /> | Ruby david || Ruby || Server || MIT || https://github.com/nning/david<br /> |-<br /> | coap-rs || Rust || Client + Server || MIT || https://github.com/Covertness/coap-rs<br /> |-<br /> <br /> |-<br /> <br /> |-<br /> <br /> |-<br /> <br /> |-<br /> <br /> |-<br /> <br /> |-<br /> <br /> |-<br /> <br /> |-<br /> <br /> <br /> <br /> <br /> <br /> | aiocoap || Python 3 || RFC 7252 || Client + Server || MIT || https://pypi.python.org/pypi/aiocoap<br /> |-<br /> | Californium || Java || RFC 7252 || Client + Server || Observe, Blockwise Transfers, DTLS || EPL+EDL || https://www.eclipse.org/californium<br /> |-<br /> | cantcoap || C++/C || RFC 7252 || Client + Server || || BSD || https://github.com/staropram/cantcoap<br /> |-<br /> | Canopus || [[Go (programming language)|Go]] || RFC 7252 || Client + Server || Core || Apache License 2.0 || https://github.com/zubairhamed/canopus<br /> |-<br /> | CoAP implementation for Go || [[Go (programming language)|Go]] || RFC 7252 || Client + Server || Core + Draft Subscribe || MIT || https://github.com/dustin/go-coap<br /> |-<br /> | CoAP.NET || C# || RFC 7252, coap-13, coap-08, coap-03 || Client + Server || Core, Observe, Blockwise Transfers || 3-clause BSD || https://github.com/smeshlink/CoAP.NET<br /> |-<br /> | CoAPSharp || C#, .NET || RFC 7252 || Client + Server || Core, Observe, Block, RD || LGPL || http://www.coapsharp.com<br /> |-<br /> | CoAPthon || Python || RFC 7252 || Client + Server + Forward Proxy + Reverse Proxy || Observe, Multicast server discovery, CoRE Link Format parsing, Block-wise || MIT || https://github.com/Tanganelli/CoAPthon<br /> |-<br /> | CoAP Shell || Java || RFC 7252 || Client || Observe, Blockwise Transfers, DTLS || Apache License 2.0 || https://github.com/tzolov/coap-shell <br /> |-<br /> | Copper || JavaScript (Browser Plugin) || RFC 7252 || Client || Observe, Blockwise Transfers || 3-clause BSD || https://github.com/mkovatsc/Copper https://addons.mozilla.org/firefox/addon/copper-270430/<br /> |-<br /> | eCoAP || C || RFC 7252 || Client + Server || Core || MIT || https://gitlab.com/jobol/ecoap<br /> |-<br /> | Erbium for Contiki || C || RFC 7252 || Client + Server || Observe, Blockwise Transfers || 3-clause BSD || http://www.contiki-os.org/ (er-rest-example)<br /> |-<br /> | iCoAP || Objective-C || RFC 7252 || Client || Core, Observe, Blockwise Transfers || MIT || https://github.com/stuffrabbit/iCoAP<br /> |-<br /> | jCoAP || Java || RFC 7252 || Client + Server || Observe, Blockwise Transfers || Apache License 2.0 || https://code.google.com/p/jcoap/<br /> |-<br /> |-<br /> |-<br /> | lobaro-coap || C || RFC 7252 || Client + Server ||Observe, Blockwise Transfers || MIT || http://www.lobaro.com/lobaro-coap<br /> |-<br /> |-<br /> | nCoap || Java || RFC 7252 || Client + Server || Observe, Blockwise Transfers, CoRE Link Format, [https://tools.ietf.org/html/draft-kleine-core-coap-endpoint-id-01 Endpoint-ID-Draft] || BSD || https://github.com/okleine/nCoAP<br /> |-<br /> | node-coap || Javascript || RFC 7252 || Client + Server || Core, Observe, Block || MIT || https://github.com/mcollina/node-coap<br /> |-<br /> |-<br /> | Sensinode C Device Library || C || RFC 7252 || Client + Server || Core, Observe, Block, RD || Commercial || https://silver.arm.com/browse/SEN00<br /> |-<br /> | Sensinode Java Device Library || Java SE || RFC 7252 || Client + Server || Core, Observe, Block, RD || Commercial || https://silver.arm.com/browse/SEN00<br /> |-<br /> | Sensinode NanoService Platform || Java SE || RFC 7252 || Cloud Server || Core, Observe, Block, RD || Commercial || https://silver.arm.com/browse/SEN00<br /> |-<br /> | SwiftCoAP || Swift || RFC 7252 || Client + Server || Core, Observe, Blockwise Transfers || MIT || https://github.com/stuffrabbit/SwiftCoAP<br /> |-<br /> | TinyOS CoapBlip || nesC/C || coap-13 || Client + Server || Observe, Blockwise Transfers || BSD || http://docs.tinyos.net/tinywiki/index.php/CoAP<br /> |-<br /> | txThings || Python (Twisted) || RFC 7252 || Client + Server || Blockwise Transfers, Observe (partial) || MIT || https://github.com/mwasilak/txThings/<br /> |-<br /> | FreeCoAP || C || RFC 7252 || Client + Server + HTTP/CoAP Proxy ||Core, DTLS, Blockwise Transfers || BSD || https://github.com/keith-cullen/FreeCoAP<br /> |-<br /> | coap-rs || Rust || RFC 7252 || Client + Server || || MIT || https://github.com/Covertness/coap-rs<br /> |-<br /> |YaCoAP<br /> |C<br /> |<br /> |<br /> |<br /> |MIT<br /> |https://github.com/RIOT-Makers/YaCoAP<br /> |}<br /> <br /> == Courses ==<br /> <br /> * [[Vertiefendes Wahlfach-Projekt]] (2018)<br /> <br /> == References ==<br /> * RFC 7252: https://tools.ietf.org/html/rfc7252<br /> * CoAP: RFC 7252 Constrained Application Protocol https://coap.technology/<br /> * Learning Internet of Things: https://www.oreilly.com/library/view/learning-internet-of/9781783553532/<br /> <br /> [[Category:Documentation]]</div>

Ograsl https://elvis.hcw.ac.at/wiki/index.php?title=Constrained_Application_Protocol&diff=1296 2019-03-11T22:39:01Z

<p>Ograsl: /* Server-side */</p> <hr /> <div>The '''Constrained Application Protocol''' ('''CoAP''') is a specialized web transfer protocol, as defined in RFC 7252, for use with constrained nodes and constrained networks in the Internet of Things.<br /> The protocol is designed for machine-to-machine (M2M) applications such as smart energy and building automation.<br /> <br /> == Features ==<br /> <br /> The work on Constrained Environments aims at realizing the REST architecture in a suitable form for the most constrained nodes and networks. The nodes usually consist of 8-bit microcontrollers with limited amounts of RAM and ROM.<br /> <br /> <br /> CoAP has the following main features:<br /> <br /> * Web protocol fulfilling M2M requirements in constrained environments<br /> * UDP [RFC0768] binding with optional reliability supporting unicast and multicast requests<br /> * Asynchronous message exchanges<br /> * Low header overhead and parsing complexity<br /> * URI and Content-type support<br /> * Simple proxy and caching capabilities<br /> * Stateless HTTP mapping<br /> * Security binding to Datagram Transport Layer Security (DTLS)<br /> <br /> == The Protocol ==<br /> <br /> CoAP is similar to the client/server model of HTTP. M2M interactions typically result in a CoAP implementation acting in both client and server roles. A request is sent by a client to request an action on a resource (identified by a URI) on a server. The server then sends a response with a response code (equivalent to that of HTTP). Therefore, efficiency is very important, so CoAP uses UDP, a datagram-oriented transport.<br /> <br /> CoAP is however a single protocol, with messaging and request/response as just features of the CoAP header<br /> <br /> +----------------------+<br /> | Application |<br /> +----------------------+<br /> +----------------------+ \<br /> | Requests/Responses | |<br /> |----------------------| | CoAP<br /> | Messages | |<br /> +----------------------+ /<br /> +----------------------+<br /> | UDP |<br /> +----------------------+<br /> <br /> [[File:Abstract_Layering_of_CoAP.JPG]]<br /> <br /> == Message Format ==<br /> <br /> By default, the messages are encoded in a simple binary format and transported over UDP. The message format starts with a fixed-size 4-byte header, followed by a variable-length Token value, which can be between 0 and 8 bytes long. Following the Token value comes a sequence of zero or more CoAP Options in Type-Length-Value (TLV) format, optionally followed by a payload that takes up the rest of the datagram.<br /> <br /> 0 1 2 3<br /> 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1<br /> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<br /> |Ver| T | TKL | Code | Message ID |<br /> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<br /> | Token (if any, TKL bytes) ...<br /> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<br /> | Options (if any) ...<br /> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<br /> |1 1 1 1 1 1 1 1| Payload (if any) ...<br /> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<br /> <br /> ;Version (Ver) (2 bits)<br /> :Indicates the CoAP Version number. This must set this field to 1 (binary 01). Other values are reserved for future versions.<br /> <br /> ;Type (T) (2 bits)<br /> :Indicates if this message is of type Confirmable (0), Non-confirmable (1), Acknowledgement (2), or Reset (3).<br /> <br /> ;Token Length (TKL) (4 bits)<br /> :Indicates the length of the variable-length Token field, which may be 0-8 bytes in length.<br /> <br /> ;CoAP Request/Response Code (8 bits)<br /> :Splits into a 3-bit class and 5-bit detail.<br /> <br /> ;Message ID (16 bits)<br /> :Used to detect message duplication and to match messages of type Acknowledgement/Reset to messages of type Confirmable/Non-confirmable.<br /> <br /> == Implementations ==<br /> <br /> Generic implementations are becoming availible for a variety of platforms.<br /> <br /> === Constrained Devices ===<br /> <br /> {| class=&quot;wikitable sortable&quot;<br /> |-<br /> ! Name !! Programming Language !! Client/Server !! License !! Link<br /> |-<br /> | Erbium for Contiki || C || Client + Server || 3-clause BSD || http://www.contiki-os.org/<br /> |-<br /> | libcoap || C || Client + Server || BSD/GPL || https://libcoap.net/<br /> |-<br /> | Eclipse tinydtls || Client + Server || EPL+EDL || https://projects.eclipse.org/projects/iot.tinydtls<br /> |-<br /> | LibNyoci || C || Client + Server || MIT || https://github.com/darconeous/libnyoci<br /> |-<br /> | microcoap || C || Client + Server || MIT || https://github.com/1248/microcoap<br /> |-<br /> | cantcoap || C++/C || Client + Server || BSD || https://github.com/staropram/cantcoap<br /> |-<br /> | Lobaro CoAP || C || Client + Server || MIT || https://www.lobaro.com/portfolio/lobaro-coap/<br /> |-<br /> | MR-CoAP || Java || || BSD || https://github.com/MR-CoAP/CoAP<br /> |-<br /> | Wakaama || C || Client + Server || EPL+EDL || https://www.eclipse.org/wakaama/index.html<br /> |-<br /> | coap-node || Javascript || Client || MIT || https://github.com/PeterEB/coap-node<br /> |-<br /> | coap-shepherd || Javascript || Server || MIT || https://github.com/PeterEB/coap-shepherd<br /> |}<br /> <br /> === Server-side ===<br /> <br /> CoAP is not only used between constrained devices, but also between them and more powerful systems such as cloud servers, home centrals, smartphones:<br /> <br /> {| class=&quot;wikitable sortable&quot;<br /> |-<br /> ! Name !! Programming Language !! Implemented CoAP version !! Client/Server !! License !! Link<br /> |-<br /> | Californium || Java || Client + Server || EPL+EDL || https://www.eclipse.org/californium<br /> |-<br /> | nCoap || Java || Client + Server || BSD || https://github.com/okleine/nCoAP<br /> |-<br /> | leshan || Java || Client + Server || EPL+EDL || https://github.com/eclipse/leshan<br /> |-<br /> | CoAP.NET || C# || Client + Server || 3-clause BSD || https://github.com/smeshlink/CoAP.NET<br /> |-<br /> | CoAPSharp || C#, .NET || Client + Server || LGPL || http://www.coapsharp.com<br /> |-<br /> | Waher.Networking.CoAP || C# || Server || || https://github.com/PeterWaher/IoTGateway/tree/master/Networking/Waher.Networking.CoAP<br /> |-<br /> | gen_coap || Erlang || Client + Server || MPL v1.1 || https://github.com/gotthardp/gen_coap<br /> |-<br /> | go-coap || Go || Client + Server || MIT || https://github.com/go-ocf/go-coap<br /> |-<br /> | node-coap || Javascript || Client + Server || MIT || https://github.com/mcollina/node-coap<br /> |-<br /> | coap-cli || Javascript || || MIT || https://github.com/mcollina/coap-cli<br /> |-<br /> | txThings || Python (Twisted) || Client + Server || MIT || https://github.com/mwasilak/txThings<br /> |-<br /> | aiocoap || Python 3 || Client + Server || MIT || https://github.com/chrysn/aiocoap<br /> |-<br /> | CoAPthon || Python || Client + Server || MIT || https://github.com/Tanganelli/CoAPthon<br /> |-<br /> | Ruby coap || Ruby || Client || MIT || https://github.com/nning/coap<br /> |-<br /> | Ruby david || Ruby || Server || MIT || https://github.com/nning/david<br /> |-<br /> | coap-rs || Rust || Client + Server || MIT || https://github.com/Covertness/coap-rs<br /> |-<br /> <br /> |-<br /> <br /> |-<br /> <br /> |-<br /> <br /> |-<br /> <br /> |-<br /> <br /> |-<br /> <br /> |-<br /> <br /> |-<br /> <br /> <br /> <br /> <br /> <br /> | aiocoap || Python 3 || RFC 7252 || Client + Server || MIT || https://pypi.python.org/pypi/aiocoap<br /> |-<br /> | Californium || Java || RFC 7252 || Client + Server || Observe, Blockwise Transfers, DTLS || EPL+EDL || https://www.eclipse.org/californium<br /> |-<br /> | cantcoap || C++/C || RFC 7252 || Client + Server || || BSD || https://github.com/staropram/cantcoap<br /> |-<br /> | Canopus || [[Go (programming language)|Go]] || RFC 7252 || Client + Server || Core || Apache License 2.0 || https://github.com/zubairhamed/canopus<br /> |-<br /> | CoAP implementation for Go || [[Go (programming language)|Go]] || RFC 7252 || Client + Server || Core + Draft Subscribe || MIT || https://github.com/dustin/go-coap<br /> |-<br /> | CoAP.NET || C# || RFC 7252, coap-13, coap-08, coap-03 || Client + Server || Core, Observe, Blockwise Transfers || 3-clause BSD || https://github.com/smeshlink/CoAP.NET<br /> |-<br /> | CoAPSharp || C#, .NET || RFC 7252 || Client + Server || Core, Observe, Block, RD || LGPL || http://www.coapsharp.com<br /> |-<br /> | CoAPthon || Python || RFC 7252 || Client + Server + Forward Proxy + Reverse Proxy || Observe, Multicast server discovery, CoRE Link Format parsing, Block-wise || MIT || https://github.com/Tanganelli/CoAPthon<br /> |-<br /> | CoAP Shell || Java || RFC 7252 || Client || Observe, Blockwise Transfers, DTLS || Apache License 2.0 || https://github.com/tzolov/coap-shell <br /> |-<br /> | Copper || JavaScript (Browser Plugin) || RFC 7252 || Client || Observe, Blockwise Transfers || 3-clause BSD || https://github.com/mkovatsc/Copper https://addons.mozilla.org/firefox/addon/copper-270430/<br /> |-<br /> | eCoAP || C || RFC 7252 || Client + Server || Core || MIT || https://gitlab.com/jobol/ecoap<br /> |-<br /> | Erbium for Contiki || C || RFC 7252 || Client + Server || Observe, Blockwise Transfers || 3-clause BSD || http://www.contiki-os.org/ (er-rest-example)<br /> |-<br /> | iCoAP || Objective-C || RFC 7252 || Client || Core, Observe, Blockwise Transfers || MIT || https://github.com/stuffrabbit/iCoAP<br /> |-<br /> | jCoAP || Java || RFC 7252 || Client + Server || Observe, Blockwise Transfers || Apache License 2.0 || https://code.google.com/p/jcoap/<br /> |-<br /> |-<br /> |-<br /> | lobaro-coap || C || RFC 7252 || Client + Server ||Observe, Blockwise Transfers || MIT || http://www.lobaro.com/lobaro-coap<br /> |-<br /> |-<br /> | nCoap || Java || RFC 7252 || Client + Server || Observe, Blockwise Transfers, CoRE Link Format, [https://tools.ietf.org/html/draft-kleine-core-coap-endpoint-id-01 Endpoint-ID-Draft] || BSD || https://github.com/okleine/nCoAP<br /> |-<br /> | node-coap || Javascript || RFC 7252 || Client + Server || Core, Observe, Block || MIT || https://github.com/mcollina/node-coap<br /> |-<br /> |-<br /> | Sensinode C Device Library || C || RFC 7252 || Client + Server || Core, Observe, Block, RD || Commercial || https://silver.arm.com/browse/SEN00<br /> |-<br /> | Sensinode Java Device Library || Java SE || RFC 7252 || Client + Server || Core, Observe, Block, RD || Commercial || https://silver.arm.com/browse/SEN00<br /> |-<br /> | Sensinode NanoService Platform || Java SE || RFC 7252 || Cloud Server || Core, Observe, Block, RD || Commercial || https://silver.arm.com/browse/SEN00<br /> |-<br /> | SwiftCoAP || Swift || RFC 7252 || Client + Server || Core, Observe, Blockwise Transfers || MIT || https://github.com/stuffrabbit/SwiftCoAP<br /> |-<br /> | TinyOS CoapBlip || nesC/C || coap-13 || Client + Server || Observe, Blockwise Transfers || BSD || http://docs.tinyos.net/tinywiki/index.php/CoAP<br /> |-<br /> | txThings || Python (Twisted) || RFC 7252 || Client + Server || Blockwise Transfers, Observe (partial) || MIT || https://github.com/mwasilak/txThings/<br /> |-<br /> | FreeCoAP || C || RFC 7252 || Client + Server + HTTP/CoAP Proxy ||Core, DTLS, Blockwise Transfers || BSD || https://github.com/keith-cullen/FreeCoAP<br /> |-<br /> | coap-rs || Rust || RFC 7252 || Client + Server || || MIT || https://github.com/Covertness/coap-rs<br /> |-<br /> |YaCoAP<br /> |C<br /> |<br /> |<br /> |<br /> |MIT<br /> |https://github.com/RIOT-Makers/YaCoAP<br /> |}<br /> <br /> == Courses ==<br /> <br /> * [[Vertiefendes Wahlfach-Projekt]] (2018)<br /> <br /> == References ==<br /> * RFC 7252: https://tools.ietf.org/html/rfc7252<br /> * CoAP: RFC 7252 Constrained Application Protocol https://coap.technology/<br /> * Learning Internet of Things: https://www.oreilly.com/library/view/learning-internet-of/9781783553532/<br /> <br /> [[Category:Documentation]]</div>

Ograsl https://elvis.hcw.ac.at/wiki/index.php?title=Constrained_Application_Protocol&diff=1295 2019-03-11T22:38:41Z

<p>Ograsl: /* Server-side */</p> <hr /> <div>The '''Constrained Application Protocol''' ('''CoAP''') is a specialized web transfer protocol, as defined in RFC 7252, for use with constrained nodes and constrained networks in the Internet of Things.<br /> The protocol is designed for machine-to-machine (M2M) applications such as smart energy and building automation.<br /> <br /> == Features ==<br /> <br /> The work on Constrained Environments aims at realizing the REST architecture in a suitable form for the most constrained nodes and networks. The nodes usually consist of 8-bit microcontrollers with limited amounts of RAM and ROM.<br /> <br /> <br /> CoAP has the following main features:<br /> <br /> * Web protocol fulfilling M2M requirements in constrained environments<br /> * UDP [RFC0768] binding with optional reliability supporting unicast and multicast requests<br /> * Asynchronous message exchanges<br /> * Low header overhead and parsing complexity<br /> * URI and Content-type support<br /> * Simple proxy and caching capabilities<br /> * Stateless HTTP mapping<br /> * Security binding to Datagram Transport Layer Security (DTLS)<br /> <br /> == The Protocol ==<br /> <br /> CoAP is similar to the client/server model of HTTP. M2M interactions typically result in a CoAP implementation acting in both client and server roles. A request is sent by a client to request an action on a resource (identified by a URI) on a server. The server then sends a response with a response code (equivalent to that of HTTP). Therefore, efficiency is very important, so CoAP uses UDP, a datagram-oriented transport.<br /> <br /> CoAP is however a single protocol, with messaging and request/response as just features of the CoAP header<br /> <br /> +----------------------+<br /> | Application |<br /> +----------------------+<br /> +----------------------+ \<br /> | Requests/Responses | |<br /> |----------------------| | CoAP<br /> | Messages | |<br /> +----------------------+ /<br /> +----------------------+<br /> | UDP |<br /> +----------------------+<br /> <br /> [[File:Abstract_Layering_of_CoAP.JPG]]<br /> <br /> == Message Format ==<br /> <br /> By default, the messages are encoded in a simple binary format and transported over UDP. The message format starts with a fixed-size 4-byte header, followed by a variable-length Token value, which can be between 0 and 8 bytes long. Following the Token value comes a sequence of zero or more CoAP Options in Type-Length-Value (TLV) format, optionally followed by a payload that takes up the rest of the datagram.<br /> <br /> 0 1 2 3<br /> 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1<br /> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<br /> |Ver| T | TKL | Code | Message ID |<br /> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<br /> | Token (if any, TKL bytes) ...<br /> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<br /> | Options (if any) ...<br /> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<br /> |1 1 1 1 1 1 1 1| Payload (if any) ...<br /> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<br /> <br /> ;Version (Ver) (2 bits)<br /> :Indicates the CoAP Version number. This must set this field to 1 (binary 01). Other values are reserved for future versions.<br /> <br /> ;Type (T) (2 bits)<br /> :Indicates if this message is of type Confirmable (0), Non-confirmable (1), Acknowledgement (2), or Reset (3).<br /> <br /> ;Token Length (TKL) (4 bits)<br /> :Indicates the length of the variable-length Token field, which may be 0-8 bytes in length.<br /> <br /> ;CoAP Request/Response Code (8 bits)<br /> :Splits into a 3-bit class and 5-bit detail.<br /> <br /> ;Message ID (16 bits)<br /> :Used to detect message duplication and to match messages of type Acknowledgement/Reset to messages of type Confirmable/Non-confirmable.<br /> <br /> == Implementations ==<br /> <br /> Generic implementations are becoming availible for a variety of platforms.<br /> <br /> === Constrained Devices ===<br /> <br /> {| class=&quot;wikitable sortable&quot;<br /> |-<br /> ! Name !! Programming Language !! Client/Server !! License !! Link<br /> |-<br /> | Erbium for Contiki || C || Client + Server || 3-clause BSD || http://www.contiki-os.org/<br /> |-<br /> | libcoap || C || Client + Server || BSD/GPL || https://libcoap.net/<br /> |-<br /> | Eclipse tinydtls || Client + Server || EPL+EDL || https://projects.eclipse.org/projects/iot.tinydtls<br /> |-<br /> | LibNyoci || C || Client + Server || MIT || https://github.com/darconeous/libnyoci<br /> |-<br /> | microcoap || C || Client + Server || MIT || https://github.com/1248/microcoap<br /> |-<br /> | cantcoap || C++/C || Client + Server || BSD || https://github.com/staropram/cantcoap<br /> |-<br /> | Lobaro CoAP || C || Client + Server || MIT || https://www.lobaro.com/portfolio/lobaro-coap/<br /> |-<br /> | MR-CoAP || Java || || BSD || https://github.com/MR-CoAP/CoAP<br /> |-<br /> | Wakaama || C || Client + Server || EPL+EDL || https://www.eclipse.org/wakaama/index.html<br /> |-<br /> | coap-node || Javascript || Client || MIT || https://github.com/PeterEB/coap-node<br /> |-<br /> | coap-shepherd || Javascript || Server || MIT || https://github.com/PeterEB/coap-shepherd<br /> |}<br /> <br /> === Server-side ===<br /> <br /> CoAP is not only used between constrained devices, but also between them and more powerful systems such as cloud servers, home centrals, smartphones:<br /> <br /> {| class=&quot;wikitable sortable&quot;<br /> |-<br /> ! Name !! Programming Language !! Implemented CoAP version !! Client/Server !! License !! Link<br /> |-<br /> | Californium || Java || RFC 7252 || Client + Server || EPL+EDL || https://www.eclipse.org/californium<br /> |-<br /> | nCoap || Java || RFC 7252 || Client + Server || BSD || https://github.com/okleine/nCoAP<br /> |-<br /> | leshan || Java || RFC 7252 || Client + Server || EPL+EDL || https://github.com/eclipse/leshan<br /> |-<br /> | CoAP.NET || C# || Client + Server || 3-clause BSD || https://github.com/smeshlink/CoAP.NET<br /> |-<br /> | CoAPSharp || C#, .NET || Client + Server || LGPL || http://www.coapsharp.com<br /> |-<br /> | Waher.Networking.CoAP || C# || Server || || https://github.com/PeterWaher/IoTGateway/tree/master/Networking/Waher.Networking.CoAP<br /> |-<br /> | gen_coap || Erlang || Client + Server || MPL v1.1 || https://github.com/gotthardp/gen_coap<br /> |-<br /> | go-coap || Go || Client + Server || MIT || https://github.com/go-ocf/go-coap<br /> |-<br /> | node-coap || Javascript || Client + Server || MIT || https://github.com/mcollina/node-coap<br /> |-<br /> | coap-cli || Javascript || || MIT || https://github.com/mcollina/coap-cli<br /> |-<br /> | txThings || Python (Twisted) || Client + Server || MIT || https://github.com/mwasilak/txThings<br /> |-<br /> | aiocoap || Python 3 || Client + Server || MIT || https://github.com/chrysn/aiocoap<br /> |-<br /> | CoAPthon || Python || Client + Server || MIT || https://github.com/Tanganelli/CoAPthon<br /> |-<br /> | Ruby coap || Ruby || Client || MIT || https://github.com/nning/coap<br /> |-<br /> | Ruby david || Ruby || Server || MIT || https://github.com/nning/david<br /> |-<br /> | coap-rs || Rust || Client + Server || MIT || https://github.com/Covertness/coap-rs<br /> |-<br /> <br /> |-<br /> <br /> |-<br /> <br /> |-<br /> <br /> |-<br /> <br /> |-<br /> <br /> |-<br /> <br /> |-<br /> <br /> |-<br /> <br /> <br /> <br /> <br /> <br /> | aiocoap || Python 3 || RFC 7252 || Client + Server || MIT || https://pypi.python.org/pypi/aiocoap<br /> |-<br /> | Californium || Java || RFC 7252 || Client + Server || Observe, Blockwise Transfers, DTLS || EPL+EDL || https://www.eclipse.org/californium<br /> |-<br /> | cantcoap || C++/C || RFC 7252 || Client + Server || || BSD || https://github.com/staropram/cantcoap<br /> |-<br /> | Canopus || [[Go (programming language)|Go]] || RFC 7252 || Client + Server || Core || Apache License 2.0 || https://github.com/zubairhamed/canopus<br /> |-<br /> | CoAP implementation for Go || [[Go (programming language)|Go]] || RFC 7252 || Client + Server || Core + Draft Subscribe || MIT || https://github.com/dustin/go-coap<br /> |-<br /> | CoAP.NET || C# || RFC 7252, coap-13, coap-08, coap-03 || Client + Server || Core, Observe, Blockwise Transfers || 3-clause BSD || https://github.com/smeshlink/CoAP.NET<br /> |-<br /> | CoAPSharp || C#, .NET || RFC 7252 || Client + Server || Core, Observe, Block, RD || LGPL || http://www.coapsharp.com<br /> |-<br /> | CoAPthon || Python || RFC 7252 || Client + Server + Forward Proxy + Reverse Proxy || Observe, Multicast server discovery, CoRE Link Format parsing, Block-wise || MIT || https://github.com/Tanganelli/CoAPthon<br /> |-<br /> | CoAP Shell || Java || RFC 7252 || Client || Observe, Blockwise Transfers, DTLS || Apache License 2.0 || https://github.com/tzolov/coap-shell <br /> |-<br /> | Copper || JavaScript (Browser Plugin) || RFC 7252 || Client || Observe, Blockwise Transfers || 3-clause BSD || https://github.com/mkovatsc/Copper https://addons.mozilla.org/firefox/addon/copper-270430/<br /> |-<br /> | eCoAP || C || RFC 7252 || Client + Server || Core || MIT || https://gitlab.com/jobol/ecoap<br /> |-<br /> | Erbium for Contiki || C || RFC 7252 || Client + Server || Observe, Blockwise Transfers || 3-clause BSD || http://www.contiki-os.org/ (er-rest-example)<br /> |-<br /> | iCoAP || Objective-C || RFC 7252 || Client || Core, Observe, Blockwise Transfers || MIT || https://github.com/stuffrabbit/iCoAP<br /> |-<br /> | jCoAP || Java || RFC 7252 || Client + Server || Observe, Blockwise Transfers || Apache License 2.0 || https://code.google.com/p/jcoap/<br /> |-<br /> |-<br /> |-<br /> | lobaro-coap || C || RFC 7252 || Client + Server ||Observe, Blockwise Transfers || MIT || http://www.lobaro.com/lobaro-coap<br /> |-<br /> |-<br /> | nCoap || Java || RFC 7252 || Client + Server || Observe, Blockwise Transfers, CoRE Link Format, [https://tools.ietf.org/html/draft-kleine-core-coap-endpoint-id-01 Endpoint-ID-Draft] || BSD || https://github.com/okleine/nCoAP<br /> |-<br /> | node-coap || Javascript || RFC 7252 || Client + Server || Core, Observe, Block || MIT || https://github.com/mcollina/node-coap<br /> |-<br /> |-<br /> | Sensinode C Device Library || C || RFC 7252 || Client + Server || Core, Observe, Block, RD || Commercial || https://silver.arm.com/browse/SEN00<br /> |-<br /> | Sensinode Java Device Library || Java SE || RFC 7252 || Client + Server || Core, Observe, Block, RD || Commercial || https://silver.arm.com/browse/SEN00<br /> |-<br /> | Sensinode NanoService Platform || Java SE || RFC 7252 || Cloud Server || Core, Observe, Block, RD || Commercial || https://silver.arm.com/browse/SEN00<br /> |-<br /> | SwiftCoAP || Swift || RFC 7252 || Client + Server || Core, Observe, Blockwise Transfers || MIT || https://github.com/stuffrabbit/SwiftCoAP<br /> |-<br /> | TinyOS CoapBlip || nesC/C || coap-13 || Client + Server || Observe, Blockwise Transfers || BSD || http://docs.tinyos.net/tinywiki/index.php/CoAP<br /> |-<br /> | txThings || Python (Twisted) || RFC 7252 || Client + Server || Blockwise Transfers, Observe (partial) || MIT || https://github.com/mwasilak/txThings/<br /> |-<br /> | FreeCoAP || C || RFC 7252 || Client + Server + HTTP/CoAP Proxy ||Core, DTLS, Blockwise Transfers || BSD || https://github.com/keith-cullen/FreeCoAP<br /> |-<br /> | coap-rs || Rust || RFC 7252 || Client + Server || || MIT || https://github.com/Covertness/coap-rs<br /> |-<br /> |YaCoAP<br /> |C<br /> |<br /> |<br /> |<br /> |MIT<br /> |https://github.com/RIOT-Makers/YaCoAP<br /> |}<br /> <br /> == Courses ==<br /> <br /> * [[Vertiefendes Wahlfach-Projekt]] (2018)<br /> <br /> == References ==<br /> * RFC 7252: https://tools.ietf.org/html/rfc7252<br /> * CoAP: RFC 7252 Constrained Application Protocol https://coap.technology/<br /> * Learning Internet of Things: https://www.oreilly.com/library/view/learning-internet-of/9781783553532/<br /> <br /> [[Category:Documentation]]</div>

Ograsl https://elvis.hcw.ac.at/wiki/index.php?title=Constrained_Application_Protocol&diff=1294 2019-03-11T22:18:02Z

<p>Ograsl: /* Constrained Devices */</p> <hr /> <div>The '''Constrained Application Protocol''' ('''CoAP''') is a specialized web transfer protocol, as defined in RFC 7252, for use with constrained nodes and constrained networks in the Internet of Things.<br /> The protocol is designed for machine-to-machine (M2M) applications such as smart energy and building automation.<br /> <br /> == Features ==<br /> <br /> The work on Constrained Environments aims at realizing the REST architecture in a suitable form for the most constrained nodes and networks. The nodes usually consist of 8-bit microcontrollers with limited amounts of RAM and ROM.<br /> <br /> <br /> CoAP has the following main features:<br /> <br /> * Web protocol fulfilling M2M requirements in constrained environments<br /> * UDP [RFC0768] binding with optional reliability supporting unicast and multicast requests<br /> * Asynchronous message exchanges<br /> * Low header overhead and parsing complexity<br /> * URI and Content-type support<br /> * Simple proxy and caching capabilities<br /> * Stateless HTTP mapping<br /> * Security binding to Datagram Transport Layer Security (DTLS)<br /> <br /> == The Protocol ==<br /> <br /> CoAP is similar to the client/server model of HTTP. M2M interactions typically result in a CoAP implementation acting in both client and server roles. A request is sent by a client to request an action on a resource (identified by a URI) on a server. The server then sends a response with a response code (equivalent to that of HTTP). Therefore, efficiency is very important, so CoAP uses UDP, a datagram-oriented transport.<br /> <br /> CoAP is however a single protocol, with messaging and request/response as just features of the CoAP header<br /> <br /> +----------------------+<br /> | Application |<br /> +----------------------+<br /> +----------------------+ \<br /> | Requests/Responses | |<br /> |----------------------| | CoAP<br /> | Messages | |<br /> +----------------------+ /<br /> +----------------------+<br /> | UDP |<br /> +----------------------+<br /> <br /> [[File:Abstract_Layering_of_CoAP.JPG]]<br /> <br /> == Message Format ==<br /> <br /> By default, the messages are encoded in a simple binary format and transported over UDP. The message format starts with a fixed-size 4-byte header, followed by a variable-length Token value, which can be between 0 and 8 bytes long. Following the Token value comes a sequence of zero or more CoAP Options in Type-Length-Value (TLV) format, optionally followed by a payload that takes up the rest of the datagram.<br /> <br /> 0 1 2 3<br /> 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1<br /> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<br /> |Ver| T | TKL | Code | Message ID |<br /> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<br /> | Token (if any, TKL bytes) ...<br /> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<br /> | Options (if any) ...<br /> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<br /> |1 1 1 1 1 1 1 1| Payload (if any) ...<br /> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<br /> <br /> ;Version (Ver) (2 bits)<br /> :Indicates the CoAP Version number. This must set this field to 1 (binary 01). Other values are reserved for future versions.<br /> <br /> ;Type (T) (2 bits)<br /> :Indicates if this message is of type Confirmable (0), Non-confirmable (1), Acknowledgement (2), or Reset (3).<br /> <br /> ;Token Length (TKL) (4 bits)<br /> :Indicates the length of the variable-length Token field, which may be 0-8 bytes in length.<br /> <br /> ;CoAP Request/Response Code (8 bits)<br /> :Splits into a 3-bit class and 5-bit detail.<br /> <br /> ;Message ID (16 bits)<br /> :Used to detect message duplication and to match messages of type Acknowledgement/Reset to messages of type Confirmable/Non-confirmable.<br /> <br /> == Implementations ==<br /> <br /> Generic implementations are becoming availible for a variety of platforms.<br /> <br /> === Constrained Devices ===<br /> <br /> {| class=&quot;wikitable sortable&quot;<br /> |-<br /> ! Name !! Programming Language !! Client/Server !! License !! Link<br /> |-<br /> | Erbium for Contiki || C || Client + Server || 3-clause BSD || http://www.contiki-os.org/<br /> |-<br /> | libcoap || C || Client + Server || BSD/GPL || https://libcoap.net/<br /> |-<br /> | Eclipse tinydtls || Client + Server || EPL+EDL || https://projects.eclipse.org/projects/iot.tinydtls<br /> |-<br /> | LibNyoci || C || Client + Server || MIT || https://github.com/darconeous/libnyoci<br /> |-<br /> | microcoap || C || Client + Server || MIT || https://github.com/1248/microcoap<br /> |-<br /> | cantcoap || C++/C || Client + Server || BSD || https://github.com/staropram/cantcoap<br /> |-<br /> | Lobaro CoAP || C || Client + Server || MIT || https://www.lobaro.com/portfolio/lobaro-coap/<br /> |-<br /> | MR-CoAP || Java || || BSD || https://github.com/MR-CoAP/CoAP<br /> |-<br /> | Wakaama || C || Client + Server || EPL+EDL || https://www.eclipse.org/wakaama/index.html<br /> |-<br /> | coap-node || Javascript || Client || MIT || https://github.com/PeterEB/coap-node<br /> |-<br /> | coap-shepherd || Javascript || Server || MIT || https://github.com/PeterEB/coap-shepherd<br /> |}<br /> <br /> === Server-side ===<br /> <br /> CoAP is not only used between constrained devices, but also between them and more powerful systems such as cloud servers, home centrals, smartphones:<br /> <br /> {| class=&quot;wikitable sortable&quot;<br /> |-<br /> ! Name !! Programming Language !! Implemented CoAP version !! Client/Server !! License !! Link<br /> |-<br /> | Californium || Java || RFC 7252 || Client + Server || EPL+EDL || https://www.eclipse.org/californium<br /> |-<br /> | nCoap || Java || RFC 7252 || Client + Server || BSD || https://github.com/okleine/nCoAP<br /> |-<br /> | leshan || Java || RFC 7252 || Client + Server || EPL+EDL || https://github.com/eclipse/leshan<br /> <br /> <br /> <br /> <br /> <br /> <br /> <br /> <br /> | aiocoap || Python 3 || RFC 7252 || Client + Server || MIT || https://pypi.python.org/pypi/aiocoap<br /> |-<br /> | Californium || Java || RFC 7252 || Client + Server || Observe, Blockwise Transfers, DTLS || EPL+EDL || https://www.eclipse.org/californium<br /> |-<br /> | cantcoap || C++/C || RFC 7252 || Client + Server || || BSD || https://github.com/staropram/cantcoap<br /> |-<br /> | Canopus || [[Go (programming language)|Go]] || RFC 7252 || Client + Server || Core || Apache License 2.0 || https://github.com/zubairhamed/canopus<br /> |-<br /> | CoAP implementation for Go || [[Go (programming language)|Go]] || RFC 7252 || Client + Server || Core + Draft Subscribe || MIT || https://github.com/dustin/go-coap<br /> |-<br /> | CoAP.NET || C# || RFC 7252, coap-13, coap-08, coap-03 || Client + Server || Core, Observe, Blockwise Transfers || 3-clause BSD || https://github.com/smeshlink/CoAP.NET<br /> |-<br /> | CoAPSharp || C#, .NET || RFC 7252 || Client + Server || Core, Observe, Block, RD || LGPL || http://www.coapsharp.com<br /> |-<br /> | CoAPthon || Python || RFC 7252 || Client + Server + Forward Proxy + Reverse Proxy || Observe, Multicast server discovery, CoRE Link Format parsing, Block-wise || MIT || https://github.com/Tanganelli/CoAPthon<br /> |-<br /> | CoAP Shell || Java || RFC 7252 || Client || Observe, Blockwise Transfers, DTLS || Apache License 2.0 || https://github.com/tzolov/coap-shell <br /> |-<br /> | Copper || JavaScript (Browser Plugin) || RFC 7252 || Client || Observe, Blockwise Transfers || 3-clause BSD || https://github.com/mkovatsc/Copper https://addons.mozilla.org/firefox/addon/copper-270430/<br /> |-<br /> | eCoAP || C || RFC 7252 || Client + Server || Core || MIT || https://gitlab.com/jobol/ecoap<br /> |-<br /> | Erbium for Contiki || C || RFC 7252 || Client + Server || Observe, Blockwise Transfers || 3-clause BSD || http://www.contiki-os.org/ (er-rest-example)<br /> |-<br /> | iCoAP || Objective-C || RFC 7252 || Client || Core, Observe, Blockwise Transfers || MIT || https://github.com/stuffrabbit/iCoAP<br /> |-<br /> | jCoAP || Java || RFC 7252 || Client + Server || Observe, Blockwise Transfers || Apache License 2.0 || https://code.google.com/p/jcoap/<br /> |-<br /> |-<br /> |-<br /> | lobaro-coap || C || RFC 7252 || Client + Server ||Observe, Blockwise Transfers || MIT || http://www.lobaro.com/lobaro-coap<br /> |-<br /> |-<br /> | nCoap || Java || RFC 7252 || Client + Server || Observe, Blockwise Transfers, CoRE Link Format, [https://tools.ietf.org/html/draft-kleine-core-coap-endpoint-id-01 Endpoint-ID-Draft] || BSD || https://github.com/okleine/nCoAP<br /> |-<br /> | node-coap || Javascript || RFC 7252 || Client + Server || Core, Observe, Block || MIT || https://github.com/mcollina/node-coap<br /> |-<br /> | Ruby coap || Ruby || RFC 7252 || Client + Server (david) || Core, Observe, Block, RD || MIT, GPL || https://github.com/nning/coap&lt;br/&gt;https://github.com/nning/david<br /> |-<br /> | Sensinode C Device Library || C || RFC 7252 || Client + Server || Core, Observe, Block, RD || Commercial || https://silver.arm.com/browse/SEN00<br /> |-<br /> | Sensinode Java Device Library || Java SE || RFC 7252 || Client + Server || Core, Observe, Block, RD || Commercial || https://silver.arm.com/browse/SEN00<br /> |-<br /> | Sensinode NanoService Platform || Java SE || RFC 7252 || Cloud Server || Core, Observe, Block, RD || Commercial || https://silver.arm.com/browse/SEN00<br /> |-<br /> | SwiftCoAP || Swift || RFC 7252 || Client + Server || Core, Observe, Blockwise Transfers || MIT || https://github.com/stuffrabbit/SwiftCoAP<br /> |-<br /> | TinyOS CoapBlip || nesC/C || coap-13 || Client + Server || Observe, Blockwise Transfers || BSD || http://docs.tinyos.net/tinywiki/index.php/CoAP<br /> |-<br /> | txThings || Python (Twisted) || RFC 7252 || Client + Server || Blockwise Transfers, Observe (partial) || MIT || https://github.com/mwasilak/txThings/<br /> |-<br /> | FreeCoAP || C || RFC 7252 || Client + Server + HTTP/CoAP Proxy ||Core, DTLS, Blockwise Transfers || BSD || https://github.com/keith-cullen/FreeCoAP<br /> |-<br /> | coap-rs || Rust || RFC 7252 || Client + Server || || MIT || https://github.com/Covertness/coap-rs<br /> |-<br /> |YaCoAP<br /> |C<br /> |<br /> |<br /> |<br /> |MIT<br /> |https://github.com/RIOT-Makers/YaCoAP<br /> |}<br /> <br /> == Courses ==<br /> <br /> * [[Vertiefendes Wahlfach-Projekt]] (2018)<br /> <br /> == References ==<br /> * RFC 7252: https://tools.ietf.org/html/rfc7252<br /> * CoAP: RFC 7252 Constrained Application Protocol https://coap.technology/<br /> * Learning Internet of Things: https://www.oreilly.com/library/view/learning-internet-of/9781783553532/<br /> <br /> [[Category:Documentation]]</div>

Ograsl https://elvis.hcw.ac.at/wiki/index.php?title=Constrained_Application_Protocol&diff=1293 2019-03-11T22:17:19Z

<p>Ograsl: /* Constrained Devices */</p> <hr /> <div>The '''Constrained Application Protocol''' ('''CoAP''') is a specialized web transfer protocol, as defined in RFC 7252, for use with constrained nodes and constrained networks in the Internet of Things.<br /> The protocol is designed for machine-to-machine (M2M) applications such as smart energy and building automation.<br /> <br /> == Features ==<br /> <br /> The work on Constrained Environments aims at realizing the REST architecture in a suitable form for the most constrained nodes and networks. The nodes usually consist of 8-bit microcontrollers with limited amounts of RAM and ROM.<br /> <br /> <br /> CoAP has the following main features:<br /> <br /> * Web protocol fulfilling M2M requirements in constrained environments<br /> * UDP [RFC0768] binding with optional reliability supporting unicast and multicast requests<br /> * Asynchronous message exchanges<br /> * Low header overhead and parsing complexity<br /> * URI and Content-type support<br /> * Simple proxy and caching capabilities<br /> * Stateless HTTP mapping<br /> * Security binding to Datagram Transport Layer Security (DTLS)<br /> <br /> == The Protocol ==<br /> <br /> CoAP is similar to the client/server model of HTTP. M2M interactions typically result in a CoAP implementation acting in both client and server roles. A request is sent by a client to request an action on a resource (identified by a URI) on a server. The server then sends a response with a response code (equivalent to that of HTTP). Therefore, efficiency is very important, so CoAP uses UDP, a datagram-oriented transport.<br /> <br /> CoAP is however a single protocol, with messaging and request/response as just features of the CoAP header<br /> <br /> +----------------------+<br /> | Application |<br /> +----------------------+<br /> +----------------------+ \<br /> | Requests/Responses | |<br /> |----------------------| | CoAP<br /> | Messages | |<br /> +----------------------+ /<br /> +----------------------+<br /> | UDP |<br /> +----------------------+<br /> <br /> [[File:Abstract_Layering_of_CoAP.JPG]]<br /> <br /> == Message Format ==<br /> <br /> By default, the messages are encoded in a simple binary format and transported over UDP. The message format starts with a fixed-size 4-byte header, followed by a variable-length Token value, which can be between 0 and 8 bytes long. Following the Token value comes a sequence of zero or more CoAP Options in Type-Length-Value (TLV) format, optionally followed by a payload that takes up the rest of the datagram.<br /> <br /> 0 1 2 3<br /> 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1<br /> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<br /> |Ver| T | TKL | Code | Message ID |<br /> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<br /> | Token (if any, TKL bytes) ...<br /> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<br /> | Options (if any) ...<br /> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<br /> |1 1 1 1 1 1 1 1| Payload (if any) ...<br /> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<br /> <br /> ;Version (Ver) (2 bits)<br /> :Indicates the CoAP Version number. This must set this field to 1 (binary 01). Other values are reserved for future versions.<br /> <br /> ;Type (T) (2 bits)<br /> :Indicates if this message is of type Confirmable (0), Non-confirmable (1), Acknowledgement (2), or Reset (3).<br /> <br /> ;Token Length (TKL) (4 bits)<br /> :Indicates the length of the variable-length Token field, which may be 0-8 bytes in length.<br /> <br /> ;CoAP Request/Response Code (8 bits)<br /> :Splits into a 3-bit class and 5-bit detail.<br /> <br /> ;Message ID (16 bits)<br /> :Used to detect message duplication and to match messages of type Acknowledgement/Reset to messages of type Confirmable/Non-confirmable.<br /> <br /> == Implementations ==<br /> <br /> Generic implementations are becoming availible for a variety of platforms.<br /> <br /> === Constrained Devices ===<br /> <br /> {| class=&quot;wikitable sortable&quot;<br /> |-<br /> ! Name !! Programming Language !! Implemented CoAP version !! Client/Server !! License !! Link<br /> |-<br /> | Erbium for Contiki || C || RFC 7252 || Client + Server || 3-clause BSD || http://www.contiki-os.org/<br /> |-<br /> | libcoap || C || RFC 7252 || Client + Server || BSD/GPL || https://libcoap.net/<br /> |-<br /> | Eclipse tinydtls || C || RFC 7252 || Client + Server || EPL+EDL || https://projects.eclipse.org/projects/iot.tinydtls<br /> |-<br /> | LibNyoci || C || RFC 7252 || Client + Server || MIT || https://github.com/darconeous/libnyoci<br /> |-<br /> | microcoap || C || RFC 7252 || Client + Server || MIT || https://github.com/1248/microcoap<br /> |-<br /> | cantcoap || C++/C || RFC 7252 || Client + Server || BSD || https://github.com/staropram/cantcoap<br /> |-<br /> | Lobaro CoAP || C || RFC 7252 || Client + Server || MIT || https://www.lobaro.com/portfolio/lobaro-coap/<br /> |-<br /> | MR-CoAP || Java || RFC 7252 || || BSD || https://github.com/MR-CoAP/CoAP<br /> |-<br /> | Wakaama || C || || Client + Server || EPL+EDL || https://www.eclipse.org/wakaama/index.html<br /> |-<br /> | coap-node || Javascript || RFC 7252 || Client || MIT || https://github.com/PeterEB/coap-node<br /> |-<br /> | coap-shepherd || Javascript || RFC 7252 || Server || MIT || https://github.com/PeterEB/coap-shepherd<br /> |}<br /> <br /> === Server-side ===<br /> <br /> CoAP is not only used between constrained devices, but also between them and more powerful systems such as cloud servers, home centrals, smartphones:<br /> <br /> {| class=&quot;wikitable sortable&quot;<br /> |-<br /> ! Name !! Programming Language !! Implemented CoAP version !! Client/Server !! License !! Link<br /> |-<br /> | Californium || Java || RFC 7252 || Client + Server || EPL+EDL || https://www.eclipse.org/californium<br /> |-<br /> | nCoap || Java || RFC 7252 || Client + Server || BSD || https://github.com/okleine/nCoAP<br /> |-<br /> | leshan || Java || RFC 7252 || Client + Server || EPL+EDL || https://github.com/eclipse/leshan<br /> <br /> <br /> <br /> <br /> <br /> <br /> <br /> <br /> | aiocoap || Python 3 || RFC 7252 || Client + Server || MIT || https://pypi.python.org/pypi/aiocoap<br /> |-<br /> | Californium || Java || RFC 7252 || Client + Server || Observe, Blockwise Transfers, DTLS || EPL+EDL || https://www.eclipse.org/californium<br /> |-<br /> | cantcoap || C++/C || RFC 7252 || Client + Server || || BSD || https://github.com/staropram/cantcoap<br /> |-<br /> | Canopus || [[Go (programming language)|Go]] || RFC 7252 || Client + Server || Core || Apache License 2.0 || https://github.com/zubairhamed/canopus<br /> |-<br /> | CoAP implementation for Go || [[Go (programming language)|Go]] || RFC 7252 || Client + Server || Core + Draft Subscribe || MIT || https://github.com/dustin/go-coap<br /> |-<br /> | CoAP.NET || C# || RFC 7252, coap-13, coap-08, coap-03 || Client + Server || Core, Observe, Blockwise Transfers || 3-clause BSD || https://github.com/smeshlink/CoAP.NET<br /> |-<br /> | CoAPSharp || C#, .NET || RFC 7252 || Client + Server || Core, Observe, Block, RD || LGPL || http://www.coapsharp.com<br /> |-<br /> | CoAPthon || Python || RFC 7252 || Client + Server + Forward Proxy + Reverse Proxy || Observe, Multicast server discovery, CoRE Link Format parsing, Block-wise || MIT || https://github.com/Tanganelli/CoAPthon<br /> |-<br /> | CoAP Shell || Java || RFC 7252 || Client || Observe, Blockwise Transfers, DTLS || Apache License 2.0 || https://github.com/tzolov/coap-shell <br /> |-<br /> | Copper || JavaScript (Browser Plugin) || RFC 7252 || Client || Observe, Blockwise Transfers || 3-clause BSD || https://github.com/mkovatsc/Copper https://addons.mozilla.org/firefox/addon/copper-270430/<br /> |-<br /> | eCoAP || C || RFC 7252 || Client + Server || Core || MIT || https://gitlab.com/jobol/ecoap<br /> |-<br /> | Erbium for Contiki || C || RFC 7252 || Client + Server || Observe, Blockwise Transfers || 3-clause BSD || http://www.contiki-os.org/ (er-rest-example)<br /> |-<br /> | iCoAP || Objective-C || RFC 7252 || Client || Core, Observe, Blockwise Transfers || MIT || https://github.com/stuffrabbit/iCoAP<br /> |-<br /> | jCoAP || Java || RFC 7252 || Client + Server || Observe, Blockwise Transfers || Apache License 2.0 || https://code.google.com/p/jcoap/<br /> |-<br /> |-<br /> |-<br /> | lobaro-coap || C || RFC 7252 || Client + Server ||Observe, Blockwise Transfers || MIT || http://www.lobaro.com/lobaro-coap<br /> |-<br /> |-<br /> | nCoap || Java || RFC 7252 || Client + Server || Observe, Blockwise Transfers, CoRE Link Format, [https://tools.ietf.org/html/draft-kleine-core-coap-endpoint-id-01 Endpoint-ID-Draft] || BSD || https://github.com/okleine/nCoAP<br /> |-<br /> | node-coap || Javascript || RFC 7252 || Client + Server || Core, Observe, Block || MIT || https://github.com/mcollina/node-coap<br /> |-<br /> | Ruby coap || Ruby || RFC 7252 || Client + Server (david) || Core, Observe, Block, RD || MIT, GPL || https://github.com/nning/coap&lt;br/&gt;https://github.com/nning/david<br /> |-<br /> | Sensinode C Device Library || C || RFC 7252 || Client + Server || Core, Observe, Block, RD || Commercial || https://silver.arm.com/browse/SEN00<br /> |-<br /> | Sensinode Java Device Library || Java SE || RFC 7252 || Client + Server || Core, Observe, Block, RD || Commercial || https://silver.arm.com/browse/SEN00<br /> |-<br /> | Sensinode NanoService Platform || Java SE || RFC 7252 || Cloud Server || Core, Observe, Block, RD || Commercial || https://silver.arm.com/browse/SEN00<br /> |-<br /> | SwiftCoAP || Swift || RFC 7252 || Client + Server || Core, Observe, Blockwise Transfers || MIT || https://github.com/stuffrabbit/SwiftCoAP<br /> |-<br /> | TinyOS CoapBlip || nesC/C || coap-13 || Client + Server || Observe, Blockwise Transfers || BSD || http://docs.tinyos.net/tinywiki/index.php/CoAP<br /> |-<br /> | txThings || Python (Twisted) || RFC 7252 || Client + Server || Blockwise Transfers, Observe (partial) || MIT || https://github.com/mwasilak/txThings/<br /> |-<br /> | FreeCoAP || C || RFC 7252 || Client + Server + HTTP/CoAP Proxy ||Core, DTLS, Blockwise Transfers || BSD || https://github.com/keith-cullen/FreeCoAP<br /> |-<br /> | coap-rs || Rust || RFC 7252 || Client + Server || || MIT || https://github.com/Covertness/coap-rs<br /> |-<br /> |YaCoAP<br /> |C<br /> |<br /> |<br /> |<br /> |MIT<br /> |https://github.com/RIOT-Makers/YaCoAP<br /> |}<br /> <br /> == Courses ==<br /> <br /> * [[Vertiefendes Wahlfach-Projekt]] (2018)<br /> <br /> == References ==<br /> * RFC 7252: https://tools.ietf.org/html/rfc7252<br /> * CoAP: RFC 7252 Constrained Application Protocol https://coap.technology/<br /> * Learning Internet of Things: https://www.oreilly.com/library/view/learning-internet-of/9781783553532/<br /> <br /> [[Category:Documentation]]</div>

Ograsl https://elvis.hcw.ac.at/wiki/index.php?title=Constrained_Application_Protocol&diff=1292 2019-03-11T22:16:23Z

<p>Ograsl: /* Constrained Devices */</p> <hr /> <div>The '''Constrained Application Protocol''' ('''CoAP''') is a specialized web transfer protocol, as defined in RFC 7252, for use with constrained nodes and constrained networks in the Internet of Things.<br /> The protocol is designed for machine-to-machine (M2M) applications such as smart energy and building automation.<br /> <br /> == Features ==<br /> <br /> The work on Constrained Environments aims at realizing the REST architecture in a suitable form for the most constrained nodes and networks. The nodes usually consist of 8-bit microcontrollers with limited amounts of RAM and ROM.<br /> <br /> <br /> CoAP has the following main features:<br /> <br /> * Web protocol fulfilling M2M requirements in constrained environments<br /> * UDP [RFC0768] binding with optional reliability supporting unicast and multicast requests<br /> * Asynchronous message exchanges<br /> * Low header overhead and parsing complexity<br /> * URI and Content-type support<br /> * Simple proxy and caching capabilities<br /> * Stateless HTTP mapping<br /> * Security binding to Datagram Transport Layer Security (DTLS)<br /> <br /> == The Protocol ==<br /> <br /> CoAP is similar to the client/server model of HTTP. M2M interactions typically result in a CoAP implementation acting in both client and server roles. A request is sent by a client to request an action on a resource (identified by a URI) on a server. The server then sends a response with a response code (equivalent to that of HTTP). Therefore, efficiency is very important, so CoAP uses UDP, a datagram-oriented transport.<br /> <br /> CoAP is however a single protocol, with messaging and request/response as just features of the CoAP header<br /> <br /> +----------------------+<br /> | Application |<br /> +----------------------+<br /> +----------------------+ \<br /> | Requests/Responses | |<br /> |----------------------| | CoAP<br /> | Messages | |<br /> +----------------------+ /<br /> +----------------------+<br /> | UDP |<br /> +----------------------+<br /> <br /> [[File:Abstract_Layering_of_CoAP.JPG]]<br /> <br /> == Message Format ==<br /> <br /> By default, the messages are encoded in a simple binary format and transported over UDP. The message format starts with a fixed-size 4-byte header, followed by a variable-length Token value, which can be between 0 and 8 bytes long. Following the Token value comes a sequence of zero or more CoAP Options in Type-Length-Value (TLV) format, optionally followed by a payload that takes up the rest of the datagram.<br /> <br /> 0 1 2 3<br /> 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1<br /> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<br /> |Ver| T | TKL | Code | Message ID |<br /> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<br /> | Token (if any, TKL bytes) ...<br /> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<br /> | Options (if any) ...<br /> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<br /> |1 1 1 1 1 1 1 1| Payload (if any) ...<br /> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<br /> <br /> ;Version (Ver) (2 bits)<br /> :Indicates the CoAP Version number. This must set this field to 1 (binary 01). Other values are reserved for future versions.<br /> <br /> ;Type (T) (2 bits)<br /> :Indicates if this message is of type Confirmable (0), Non-confirmable (1), Acknowledgement (2), or Reset (3).<br /> <br /> ;Token Length (TKL) (4 bits)<br /> :Indicates the length of the variable-length Token field, which may be 0-8 bytes in length.<br /> <br /> ;CoAP Request/Response Code (8 bits)<br /> :Splits into a 3-bit class and 5-bit detail.<br /> <br /> ;Message ID (16 bits)<br /> :Used to detect message duplication and to match messages of type Acknowledgement/Reset to messages of type Confirmable/Non-confirmable.<br /> <br /> == Implementations ==<br /> <br /> Generic implementations are becoming availible for a variety of platforms.<br /> <br /> === Constrained Devices ===<br /> <br /> {| class=&quot;wikitable sortable&quot;<br /> |-<br /> ! Name !! Programming Language !! Implemented CoAP version !! Client/Server !! License !! Link<br /> |-<br /> | Erbium for Contiki || C || RFC 7252 || Client + Server || 3-clause BSD || http://www.contiki-os.org/<br /> |-<br /> | libcoap || C || RFC 7252 || Client + Server || BSD/GPL || https://libcoap.net/<br /> |-<br /> | Eclipse tinydtls || C || RFC 7252 || Client + Server || EPL+EDL || https://projects.eclipse.org/projects/iot.tinydtls<br /> |-<br /> | LibNyoci || C || RFC 7252 || Client + Server || MIT || https://github.com/darconeous/libnyoci<br /> |-<br /> | microcoap || C || RFC 7252 || Client + Server || MIT || https://github.com/1248/microcoap<br /> |-<br /> | cantcoap || C++/C || RFC 7252 || Client + Server || BSD || https://github.com/staropram/cantcoap<br /> |-<br /> | Lobaro CoAP || C || RFC 7252 || Client + Server || MIT || https://www.lobaro.com/portfolio/lobaro-coap/<br /> |-<br /> | MR-CoAP || Java || RFC 7252 || || BSD || https://github.com/MR-CoAP/CoAP<br /> |-<br /> | Wakaama || C || || Client + Server || EPL+EDL || https://www.eclipse.org/wakaama/index.html<br /> |-<br /> | coap-node || Javascript || RFC 7252 || Client || MIT || https://github.com/PeterEB/coap-node<br /> |-<br /> | coap-shepherd || Javascript || RFC 7252 || Server || MIT || https://github.com/PeterEB/coap-shepherd<br /> <br /> === Server-side ===<br /> <br /> CoAP is not only used between constrained devices, but also between them and more powerful systems such as cloud servers, home centrals, smartphones:<br /> <br /> {| class=&quot;wikitable sortable&quot;<br /> |-<br /> ! Name !! Programming Language !! Implemented CoAP version !! Client/Server !! License !! Link<br /> |-<br /> | Californium || Java || RFC 7252 || Client + Server || EPL+EDL || https://www.eclipse.org/californium<br /> |-<br /> | nCoap || Java || RFC 7252 || Client + Server || BSD || https://github.com/okleine/nCoAP<br /> |-<br /> | leshan || Java || RFC 7252 || Client + Server || EPL+EDL || https://github.com/eclipse/leshan<br /> <br /> <br /> <br /> <br /> <br /> <br /> <br /> <br /> | aiocoap || Python 3 || RFC 7252 || Client + Server || MIT || https://pypi.python.org/pypi/aiocoap<br /> |-<br /> | Californium || Java || RFC 7252 || Client + Server || Observe, Blockwise Transfers, DTLS || EPL+EDL || https://www.eclipse.org/californium<br /> |-<br /> | cantcoap || C++/C || RFC 7252 || Client + Server || || BSD || https://github.com/staropram/cantcoap<br /> |-<br /> | Canopus || [[Go (programming language)|Go]] || RFC 7252 || Client + Server || Core || Apache License 2.0 || https://github.com/zubairhamed/canopus<br /> |-<br /> | CoAP implementation for Go || [[Go (programming language)|Go]] || RFC 7252 || Client + Server || Core + Draft Subscribe || MIT || https://github.com/dustin/go-coap<br /> |-<br /> | CoAP.NET || C# || RFC 7252, coap-13, coap-08, coap-03 || Client + Server || Core, Observe, Blockwise Transfers || 3-clause BSD || https://github.com/smeshlink/CoAP.NET<br /> |-<br /> | CoAPSharp || C#, .NET || RFC 7252 || Client + Server || Core, Observe, Block, RD || LGPL || http://www.coapsharp.com<br /> |-<br /> | CoAPthon || Python || RFC 7252 || Client + Server + Forward Proxy + Reverse Proxy || Observe, Multicast server discovery, CoRE Link Format parsing, Block-wise || MIT || https://github.com/Tanganelli/CoAPthon<br /> |-<br /> | CoAP Shell || Java || RFC 7252 || Client || Observe, Blockwise Transfers, DTLS || Apache License 2.0 || https://github.com/tzolov/coap-shell <br /> |-<br /> | Copper || JavaScript (Browser Plugin) || RFC 7252 || Client || Observe, Blockwise Transfers || 3-clause BSD || https://github.com/mkovatsc/Copper https://addons.mozilla.org/firefox/addon/copper-270430/<br /> |-<br /> | eCoAP || C || RFC 7252 || Client + Server || Core || MIT || https://gitlab.com/jobol/ecoap<br /> |-<br /> | Erbium for Contiki || C || RFC 7252 || Client + Server || Observe, Blockwise Transfers || 3-clause BSD || http://www.contiki-os.org/ (er-rest-example)<br /> |-<br /> | iCoAP || Objective-C || RFC 7252 || Client || Core, Observe, Blockwise Transfers || MIT || https://github.com/stuffrabbit/iCoAP<br /> |-<br /> | jCoAP || Java || RFC 7252 || Client + Server || Observe, Blockwise Transfers || Apache License 2.0 || https://code.google.com/p/jcoap/<br /> |-<br /> |-<br /> |-<br /> | lobaro-coap || C || RFC 7252 || Client + Server ||Observe, Blockwise Transfers || MIT || http://www.lobaro.com/lobaro-coap<br /> |-<br /> |-<br /> | nCoap || Java || RFC 7252 || Client + Server || Observe, Blockwise Transfers, CoRE Link Format, [https://tools.ietf.org/html/draft-kleine-core-coap-endpoint-id-01 Endpoint-ID-Draft] || BSD || https://github.com/okleine/nCoAP<br /> |-<br /> | node-coap || Javascript || RFC 7252 || Client + Server || Core, Observe, Block || MIT || https://github.com/mcollina/node-coap<br /> |-<br /> | Ruby coap || Ruby || RFC 7252 || Client + Server (david) || Core, Observe, Block, RD || MIT, GPL || https://github.com/nning/coap&lt;br/&gt;https://github.com/nning/david<br /> |-<br /> | Sensinode C Device Library || C || RFC 7252 || Client + Server || Core, Observe, Block, RD || Commercial || https://silver.arm.com/browse/SEN00<br /> |-<br /> | Sensinode Java Device Library || Java SE || RFC 7252 || Client + Server || Core, Observe, Block, RD || Commercial || https://silver.arm.com/browse/SEN00<br /> |-<br /> | Sensinode NanoService Platform || Java SE || RFC 7252 || Cloud Server || Core, Observe, Block, RD || Commercial || https://silver.arm.com/browse/SEN00<br /> |-<br /> | SwiftCoAP || Swift || RFC 7252 || Client + Server || Core, Observe, Blockwise Transfers || MIT || https://github.com/stuffrabbit/SwiftCoAP<br /> |-<br /> | TinyOS CoapBlip || nesC/C || coap-13 || Client + Server || Observe, Blockwise Transfers || BSD || http://docs.tinyos.net/tinywiki/index.php/CoAP<br /> |-<br /> | txThings || Python (Twisted) || RFC 7252 || Client + Server || Blockwise Transfers, Observe (partial) || MIT || https://github.com/mwasilak/txThings/<br /> |-<br /> | FreeCoAP || C || RFC 7252 || Client + Server + HTTP/CoAP Proxy ||Core, DTLS, Blockwise Transfers || BSD || https://github.com/keith-cullen/FreeCoAP<br /> |-<br /> | coap-rs || Rust || RFC 7252 || Client + Server || || MIT || https://github.com/Covertness/coap-rs<br /> |-<br /> |YaCoAP<br /> |C<br /> |<br /> |<br /> |<br /> |MIT<br /> |https://github.com/RIOT-Makers/YaCoAP<br /> |}<br /> <br /> == Courses ==<br /> <br /> * [[Vertiefendes Wahlfach-Projekt]] (2018)<br /> <br /> == References ==<br /> * RFC 7252: https://tools.ietf.org/html/rfc7252<br /> * CoAP: RFC 7252 Constrained Application Protocol https://coap.technology/<br /> * Learning Internet of Things: https://www.oreilly.com/library/view/learning-internet-of/9781783553532/<br /> <br /> [[Category:Documentation]]</div>

Ograsl https://elvis.hcw.ac.at/wiki/index.php?title=Constrained_Application_Protocol&diff=1291 2019-03-11T20:50:29Z

<p>Ograsl: /* Implementations */</p> <hr /> <div>The '''Constrained Application Protocol''' ('''CoAP''') is a specialized web transfer protocol, as defined in RFC 7252, for use with constrained nodes and constrained networks in the Internet of Things.<br /> The protocol is designed for machine-to-machine (M2M) applications such as smart energy and building automation.<br /> <br /> == Features ==<br /> <br /> The work on Constrained Environments aims at realizing the REST architecture in a suitable form for the most constrained nodes and networks. The nodes usually consist of 8-bit microcontrollers with limited amounts of RAM and ROM.<br /> <br /> <br /> CoAP has the following main features:<br /> <br /> * Web protocol fulfilling M2M requirements in constrained environments<br /> * UDP [RFC0768] binding with optional reliability supporting unicast and multicast requests<br /> * Asynchronous message exchanges<br /> * Low header overhead and parsing complexity<br /> * URI and Content-type support<br /> * Simple proxy and caching capabilities<br /> * Stateless HTTP mapping<br /> * Security binding to Datagram Transport Layer Security (DTLS)<br /> <br /> == The Protocol ==<br /> <br /> CoAP is similar to the client/server model of HTTP. M2M interactions typically result in a CoAP implementation acting in both client and server roles. A request is sent by a client to request an action on a resource (identified by a URI) on a server. The server then sends a response with a response code (equivalent to that of HTTP). Therefore, efficiency is very important, so CoAP uses UDP, a datagram-oriented transport.<br /> <br /> CoAP is however a single protocol, with messaging and request/response as just features of the CoAP header<br /> <br /> +----------------------+<br /> | Application |<br /> +----------------------+<br /> +----------------------+ \<br /> | Requests/Responses | |<br /> |----------------------| | CoAP<br /> | Messages | |<br /> +----------------------+ /<br /> +----------------------+<br /> | UDP |<br /> +----------------------+<br /> <br /> [[File:Abstract_Layering_of_CoAP.JPG]]<br /> <br /> == Message Format ==<br /> <br /> By default, the messages are encoded in a simple binary format and transported over UDP. The message format starts with a fixed-size 4-byte header, followed by a variable-length Token value, which can be between 0 and 8 bytes long. Following the Token value comes a sequence of zero or more CoAP Options in Type-Length-Value (TLV) format, optionally followed by a payload that takes up the rest of the datagram.<br /> <br /> 0 1 2 3<br /> 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1<br /> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<br /> |Ver| T | TKL | Code | Message ID |<br /> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<br /> | Token (if any, TKL bytes) ...<br /> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<br /> | Options (if any) ...<br /> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<br /> |1 1 1 1 1 1 1 1| Payload (if any) ...<br /> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<br /> <br /> ;Version (Ver) (2 bits)<br /> :Indicates the CoAP Version number. This must set this field to 1 (binary 01). Other values are reserved for future versions.<br /> <br /> ;Type (T) (2 bits)<br /> :Indicates if this message is of type Confirmable (0), Non-confirmable (1), Acknowledgement (2), or Reset (3).<br /> <br /> ;Token Length (TKL) (4 bits)<br /> :Indicates the length of the variable-length Token field, which may be 0-8 bytes in length.<br /> <br /> ;CoAP Request/Response Code (8 bits)<br /> :Splits into a 3-bit class and 5-bit detail.<br /> <br /> ;Message ID (16 bits)<br /> :Used to detect message duplication and to match messages of type Acknowledgement/Reset to messages of type Confirmable/Non-confirmable.<br /> <br /> == Implementations ==<br /> <br /> Generic implementations are becoming availible for a variety of platforms.<br /> <br /> === Constrained Devices ===<br /> <br /> {| class=&quot;wikitable sortable&quot;<br /> |-<br /> ! Name !! Programming Language !! Implemented CoAP version !! Client/Server !! License !! Link<br /> |-<br /> | Erbium for Contiki || C || RFC 7252 || Client + Server || 3-clause BSD || http://www.contiki-os.org/<br /> |-<br /> | libcoap || C || RFC 7252 || Client + Server || BSD/GPL || https://libcoap.net/<br /> |-<br /> | Eclipse tinydtls || C || Client + Server || EPL+EDL || https://projects.eclipse.org/projects/iot.tinydtls<br /> |-<br /> | LibNyoci || C || RFC 7252 || Client + Server || MIT || https://github.com/darconeous/libnyoci<br /> |-<br /> | microcoap || C || RFC 7252 || Client + Server || MIT || https://github.com/1248/microcoap<br /> |-<br /> | cantcoap || C++/C || RFC 7252 || Client + Server || BSD || https://github.com/staropram/cantcoap<br /> |-<br /> | Lobaro CoAP || C || RFC 7252 || Client + Server || MIT || https://www.lobaro.com/portfolio/lobaro-coap/<br /> |-<br /> | MR-CoAP || Java || RFC 7252 || || BSD || https://github.com/MR-CoAP/CoAP<br /> <br /> <br /> <br /> | aiocoap || Python 3 || RFC 7252 || Client + Server || MIT || https://pypi.python.org/pypi/aiocoap<br /> |-<br /> | Californium || Java || RFC 7252 || Client + Server || Observe, Blockwise Transfers, DTLS || EPL+EDL || https://www.eclipse.org/californium<br /> |-<br /> | cantcoap || C++/C || RFC 7252 || Client + Server || || BSD || https://github.com/staropram/cantcoap<br /> |-<br /> | Canopus || [[Go (programming language)|Go]] || RFC 7252 || Client + Server || Core || Apache License 2.0 || https://github.com/zubairhamed/canopus<br /> |-<br /> | CoAP implementation for Go || [[Go (programming language)|Go]] || RFC 7252 || Client + Server || Core + Draft Subscribe || MIT || https://github.com/dustin/go-coap<br /> |-<br /> | CoAP.NET || C# || RFC 7252, coap-13, coap-08, coap-03 || Client + Server || Core, Observe, Blockwise Transfers || 3-clause BSD || https://github.com/smeshlink/CoAP.NET<br /> |-<br /> | CoAPSharp || C#, .NET || RFC 7252 || Client + Server || Core, Observe, Block, RD || LGPL || http://www.coapsharp.com<br /> |-<br /> | CoAPthon || Python || RFC 7252 || Client + Server + Forward Proxy + Reverse Proxy || Observe, Multicast server discovery, CoRE Link Format parsing, Block-wise || MIT || https://github.com/Tanganelli/CoAPthon<br /> |-<br /> | CoAP Shell || Java || RFC 7252 || Client || Observe, Blockwise Transfers, DTLS || Apache License 2.0 || https://github.com/tzolov/coap-shell <br /> |-<br /> | Copper || JavaScript (Browser Plugin) || RFC 7252 || Client || Observe, Blockwise Transfers || 3-clause BSD || https://github.com/mkovatsc/Copper https://addons.mozilla.org/firefox/addon/copper-270430/<br /> |-<br /> | eCoAP || C || RFC 7252 || Client + Server || Core || MIT || https://gitlab.com/jobol/ecoap<br /> |-<br /> | Erbium for Contiki || C || RFC 7252 || Client + Server || Observe, Blockwise Transfers || 3-clause BSD || http://www.contiki-os.org/ (er-rest-example)<br /> |-<br /> | iCoAP || Objective-C || RFC 7252 || Client || Core, Observe, Blockwise Transfers || MIT || https://github.com/stuffrabbit/iCoAP<br /> |-<br /> | jCoAP || Java || RFC 7252 || Client + Server || Observe, Blockwise Transfers || Apache License 2.0 || https://code.google.com/p/jcoap/<br /> |-<br /> |-<br /> |-<br /> | lobaro-coap || C || RFC 7252 || Client + Server ||Observe, Blockwise Transfers || MIT || http://www.lobaro.com/lobaro-coap<br /> |-<br /> |-<br /> | nCoap || Java || RFC 7252 || Client + Server || Observe, Blockwise Transfers, CoRE Link Format, [https://tools.ietf.org/html/draft-kleine-core-coap-endpoint-id-01 Endpoint-ID-Draft] || BSD || https://github.com/okleine/nCoAP<br /> |-<br /> | node-coap || Javascript || RFC 7252 || Client + Server || Core, Observe, Block || MIT || https://github.com/mcollina/node-coap<br /> |-<br /> | Ruby coap || Ruby || RFC 7252 || Client + Server (david) || Core, Observe, Block, RD || MIT, GPL || https://github.com/nning/coap&lt;br/&gt;https://github.com/nning/david<br /> |-<br /> | Sensinode C Device Library || C || RFC 7252 || Client + Server || Core, Observe, Block, RD || Commercial || https://silver.arm.com/browse/SEN00<br /> |-<br /> | Sensinode Java Device Library || Java SE || RFC 7252 || Client + Server || Core, Observe, Block, RD || Commercial || https://silver.arm.com/browse/SEN00<br /> |-<br /> | Sensinode NanoService Platform || Java SE || RFC 7252 || Cloud Server || Core, Observe, Block, RD || Commercial || https://silver.arm.com/browse/SEN00<br /> |-<br /> | SwiftCoAP || Swift || RFC 7252 || Client + Server || Core, Observe, Blockwise Transfers || MIT || https://github.com/stuffrabbit/SwiftCoAP<br /> |-<br /> | TinyOS CoapBlip || nesC/C || coap-13 || Client + Server || Observe, Blockwise Transfers || BSD || http://docs.tinyos.net/tinywiki/index.php/CoAP<br /> |-<br /> | txThings || Python (Twisted) || RFC 7252 || Client + Server || Blockwise Transfers, Observe (partial) || MIT || https://github.com/mwasilak/txThings/<br /> |-<br /> | FreeCoAP || C || RFC 7252 || Client + Server + HTTP/CoAP Proxy ||Core, DTLS, Blockwise Transfers || BSD || https://github.com/keith-cullen/FreeCoAP<br /> |-<br /> | coap-rs || Rust || RFC 7252 || Client + Server || || MIT || https://github.com/Covertness/coap-rs<br /> |-<br /> |YaCoAP<br /> |C<br /> |<br /> |<br /> |<br /> |MIT<br /> |https://github.com/RIOT-Makers/YaCoAP<br /> |}<br /> <br /> == Courses ==<br /> <br /> * [[Vertiefendes Wahlfach-Projekt]] (2018)<br /> <br /> == References ==<br /> * RFC 7252: https://tools.ietf.org/html/rfc7252<br /> * CoAP: RFC 7252 Constrained Application Protocol https://coap.technology/<br /> * Learning Internet of Things: https://www.oreilly.com/library/view/learning-internet-of/9781783553532/<br /> <br /> [[Category:Documentation]]</div>

Ograsl https://elvis.hcw.ac.at/wiki/index.php?title=Constrained_Application_Protocol&diff=1290 2019-03-11T19:07:08Z

<p>Ograsl: /* Implementations */</p> <hr /> <div>The '''Constrained Application Protocol''' ('''CoAP''') is a specialized web transfer protocol, as defined in RFC 7252, for use with constrained nodes and constrained networks in the Internet of Things.<br /> The protocol is designed for machine-to-machine (M2M) applications such as smart energy and building automation.<br /> <br /> == Features ==<br /> <br /> The work on Constrained Environments aims at realizing the REST architecture in a suitable form for the most constrained nodes and networks. The nodes usually consist of 8-bit microcontrollers with limited amounts of RAM and ROM.<br /> <br /> <br /> CoAP has the following main features:<br /> <br /> * Web protocol fulfilling M2M requirements in constrained environments<br /> * UDP [RFC0768] binding with optional reliability supporting unicast and multicast requests<br /> * Asynchronous message exchanges<br /> * Low header overhead and parsing complexity<br /> * URI and Content-type support<br /> * Simple proxy and caching capabilities<br /> * Stateless HTTP mapping<br /> * Security binding to Datagram Transport Layer Security (DTLS)<br /> <br /> == The Protocol ==<br /> <br /> CoAP is similar to the client/server model of HTTP. M2M interactions typically result in a CoAP implementation acting in both client and server roles. A request is sent by a client to request an action on a resource (identified by a URI) on a server. The server then sends a response with a response code (equivalent to that of HTTP). Therefore, efficiency is very important, so CoAP uses UDP, a datagram-oriented transport.<br /> <br /> CoAP is however a single protocol, with messaging and request/response as just features of the CoAP header<br /> <br /> +----------------------+<br /> | Application |<br /> +----------------------+<br /> +----------------------+ \<br /> | Requests/Responses | |<br /> |----------------------| | CoAP<br /> | Messages | |<br /> +----------------------+ /<br /> +----------------------+<br /> | UDP |<br /> +----------------------+<br /> <br /> [[File:Abstract_Layering_of_CoAP.JPG]]<br /> <br /> == Message Format ==<br /> <br /> By default, the messages are encoded in a simple binary format and transported over UDP. The message format starts with a fixed-size 4-byte header, followed by a variable-length Token value, which can be between 0 and 8 bytes long. Following the Token value comes a sequence of zero or more CoAP Options in Type-Length-Value (TLV) format, optionally followed by a payload that takes up the rest of the datagram.<br /> <br /> 0 1 2 3<br /> 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1<br /> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<br /> |Ver| T | TKL | Code | Message ID |<br /> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<br /> | Token (if any, TKL bytes) ...<br /> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<br /> | Options (if any) ...<br /> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<br /> |1 1 1 1 1 1 1 1| Payload (if any) ...<br /> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<br /> <br /> ;Version (Ver) (2 bits)<br /> :Indicates the CoAP Version number. This must set this field to 1 (binary 01). Other values are reserved for future versions.<br /> <br /> ;Type (T) (2 bits)<br /> :Indicates if this message is of type Confirmable (0), Non-confirmable (1), Acknowledgement (2), or Reset (3).<br /> <br /> ;Token Length (TKL) (4 bits)<br /> :Indicates the length of the variable-length Token field, which may be 0-8 bytes in length.<br /> <br /> ;CoAP Request/Response Code (8 bits)<br /> :Splits into a 3-bit class and 5-bit detail.<br /> <br /> ;Message ID (16 bits)<br /> :Used to detect message duplication and to match messages of type Acknowledgement/Reset to messages of type Confirmable/Non-confirmable.<br /> <br /> == Implementations ==<br /> <br /> === Constrained Devices ===<br /> <br /> {| class=&quot;wikitable sortable&quot;<br /> |-<br /> ! Name !! Programming Language !! Implemented CoAP version !! Client/Server !! Implemented CoAP features !! License !! Link<br /> |-<br /> | aiocoap || Python 3 || RFC 7252 || Client + Server || Blockwise Transfers, Observe (partial) || MIT || https://pypi.python.org/pypi/aiocoap<br /> |-<br /> | Californium || Java || RFC 7252 || Client + Server || Observe, Blockwise Transfers, DTLS || EPL+EDL || https://www.eclipse.org/californium<br /> |-<br /> | cantcoap || C++/C || RFC 7252 || Client + Server || || BSD || https://github.com/staropram/cantcoap<br /> |-<br /> | Canopus || [[Go (programming language)|Go]] || RFC 7252 || Client + Server || Core || Apache License 2.0 || https://github.com/zubairhamed/canopus<br /> |-<br /> | CoAP implementation for Go || [[Go (programming language)|Go]] || RFC 7252 || Client + Server || Core + Draft Subscribe || MIT || https://github.com/dustin/go-coap<br /> |-<br /> | CoAP.NET || C# || RFC 7252, coap-13, coap-08, coap-03 || Client + Server || Core, Observe, Blockwise Transfers || 3-clause BSD || https://github.com/smeshlink/CoAP.NET<br /> |-<br /> | CoAPSharp || C#, .NET || RFC 7252 || Client + Server || Core, Observe, Block, RD || LGPL || http://www.coapsharp.com<br /> |-<br /> | CoAPthon || Python || RFC 7252 || Client + Server + Forward Proxy + Reverse Proxy || Observe, Multicast server discovery, CoRE Link Format parsing, Block-wise || MIT || https://github.com/Tanganelli/CoAPthon<br /> |-<br /> | CoAP Shell || Java || RFC 7252 || Client || Observe, Blockwise Transfers, DTLS || Apache License 2.0 || https://github.com/tzolov/coap-shell <br /> |-<br /> | Copper || JavaScript (Browser Plugin) || RFC 7252 || Client || Observe, Blockwise Transfers || 3-clause BSD || https://github.com/mkovatsc/Copper https://addons.mozilla.org/firefox/addon/copper-270430/<br /> |-<br /> | eCoAP || C || RFC 7252 || Client + Server || Core || MIT || https://gitlab.com/jobol/ecoap<br /> |-<br /> | Erbium for Contiki || C || RFC 7252 || Client + Server || Observe, Blockwise Transfers || 3-clause BSD || http://www.contiki-os.org/ (er-rest-example)<br /> |-<br /> | iCoAP || Objective-C || RFC 7252 || Client || Core, Observe, Blockwise Transfers || MIT || https://github.com/stuffrabbit/iCoAP<br /> |-<br /> | jCoAP || Java || RFC 7252 || Client + Server || Observe, Blockwise Transfers || Apache License 2.0 || https://code.google.com/p/jcoap/<br /> |-<br /> | libcoap || C || RFC 7252 || Client + Server ||Observe, Blockwise Transfers, DTLS || BSD/GPL || https://github.com/obgm/libcoap<br /> |-<br /> | LibNyoci || C || RFC 7252 || Client + Server || Core, Observe, Block, DTLS || MIT || https://github.com/darconeous/libnyoci<br /> |-<br /> | lobaro-coap || C || RFC 7252 || Client + Server ||Observe, Blockwise Transfers || MIT || http://www.lobaro.com/lobaro-coap<br /> |-<br /> | microcoap || C || RFC 7252 || Client + Server || || MIT || https://github.com/1248/microcoap<br /> |-<br /> | nCoap || Java || RFC 7252 || Client + Server || Observe, Blockwise Transfers, CoRE Link Format, [https://tools.ietf.org/html/draft-kleine-core-coap-endpoint-id-01 Endpoint-ID-Draft] || BSD || https://github.com/okleine/nCoAP<br /> |-<br /> | node-coap || Javascript || RFC 7252 || Client + Server || Core, Observe, Block || MIT || https://github.com/mcollina/node-coap<br /> |-<br /> | Ruby coap || Ruby || RFC 7252 || Client + Server (david) || Core, Observe, Block, RD || MIT, GPL || https://github.com/nning/coap&lt;br/&gt;https://github.com/nning/david<br /> |-<br /> | Sensinode C Device Library || C || RFC 7252 || Client + Server || Core, Observe, Block, RD || Commercial || https://silver.arm.com/browse/SEN00<br /> |-<br /> | Sensinode Java Device Library || Java SE || RFC 7252 || Client + Server || Core, Observe, Block, RD || Commercial || https://silver.arm.com/browse/SEN00<br /> |-<br /> | Sensinode NanoService Platform || Java SE || RFC 7252 || Cloud Server || Core, Observe, Block, RD || Commercial || https://silver.arm.com/browse/SEN00<br /> |-<br /> | SwiftCoAP || Swift || RFC 7252 || Client + Server || Core, Observe, Blockwise Transfers || MIT || https://github.com/stuffrabbit/SwiftCoAP<br /> |-<br /> | TinyOS CoapBlip || nesC/C || coap-13 || Client + Server || Observe, Blockwise Transfers || BSD || http://docs.tinyos.net/tinywiki/index.php/CoAP<br /> |-<br /> | txThings || Python (Twisted) || RFC 7252 || Client + Server || Blockwise Transfers, Observe (partial) || MIT || https://github.com/mwasilak/txThings/<br /> |-<br /> | FreeCoAP || C || RFC 7252 || Client + Server + HTTP/CoAP Proxy ||Core, DTLS, Blockwise Transfers || BSD || https://github.com/keith-cullen/FreeCoAP<br /> |-<br /> | coap-rs || Rust || RFC 7252 || Client + Server || || MIT || https://github.com/Covertness/coap-rs<br /> |-<br /> |YaCoAP<br /> |C<br /> |<br /> |<br /> |<br /> |MIT<br /> |https://github.com/RIOT-Makers/YaCoAP<br /> |}<br /> <br /> == Courses ==<br /> <br /> * [[Vertiefendes Wahlfach-Projekt]] (2018)<br /> <br /> == References ==<br /> * RFC 7252: https://tools.ietf.org/html/rfc7252<br /> * CoAP: RFC 7252 Constrained Application Protocol https://coap.technology/<br /> * Learning Internet of Things: https://www.oreilly.com/library/view/learning-internet-of/9781783553532/<br /> <br /> [[Category:Documentation]]</div>

Ograsl https://elvis.hcw.ac.at/wiki/index.php?title=Constrained_Application_Protocol&diff=1289 2019-03-11T18:38:58Z

<p>Ograsl: </p> <hr /> <div>The '''Constrained Application Protocol''' ('''CoAP''') is a specialized web transfer protocol, as defined in RFC 7252, for use with constrained nodes and constrained networks in the Internet of Things.<br /> The protocol is designed for machine-to-machine (M2M) applications such as smart energy and building automation.<br /> <br /> == Features ==<br /> <br /> The work on Constrained Environments aims at realizing the REST architecture in a suitable form for the most constrained nodes and networks. The nodes usually consist of 8-bit microcontrollers with limited amounts of RAM and ROM.<br /> <br /> <br /> CoAP has the following main features:<br /> <br /> * Web protocol fulfilling M2M requirements in constrained environments<br /> * UDP [RFC0768] binding with optional reliability supporting unicast and multicast requests<br /> * Asynchronous message exchanges<br /> * Low header overhead and parsing complexity<br /> * URI and Content-type support<br /> * Simple proxy and caching capabilities<br /> * Stateless HTTP mapping<br /> * Security binding to Datagram Transport Layer Security (DTLS)<br /> <br /> == The Protocol ==<br /> <br /> CoAP is similar to the client/server model of HTTP. M2M interactions typically result in a CoAP implementation acting in both client and server roles. A request is sent by a client to request an action on a resource (identified by a URI) on a server. The server then sends a response with a response code (equivalent to that of HTTP). Therefore, efficiency is very important, so CoAP uses UDP, a datagram-oriented transport.<br /> <br /> CoAP is however a single protocol, with messaging and request/response as just features of the CoAP header<br /> <br /> +----------------------+<br /> | Application |<br /> +----------------------+<br /> +----------------------+ \<br /> | Requests/Responses | |<br /> |----------------------| | CoAP<br /> | Messages | |<br /> +----------------------+ /<br /> +----------------------+<br /> | UDP |<br /> +----------------------+<br /> <br /> [[File:Abstract_Layering_of_CoAP.JPG]]<br /> <br /> == Message Format ==<br /> <br /> By default, the messages are encoded in a simple binary format and transported over UDP. The message format starts with a fixed-size 4-byte header, followed by a variable-length Token value, which can be between 0 and 8 bytes long. Following the Token value comes a sequence of zero or more CoAP Options in Type-Length-Value (TLV) format, optionally followed by a payload that takes up the rest of the datagram.<br /> <br /> 0 1 2 3<br /> 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1<br /> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<br /> |Ver| T | TKL | Code | Message ID |<br /> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<br /> | Token (if any, TKL bytes) ...<br /> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<br /> | Options (if any) ...<br /> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<br /> |1 1 1 1 1 1 1 1| Payload (if any) ...<br /> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<br /> <br /> ;Version (Ver) (2 bits)<br /> :Indicates the CoAP Version number. This must set this field to 1 (binary 01). Other values are reserved for future versions.<br /> <br /> ;Type (T) (2 bits)<br /> :Indicates if this message is of type Confirmable (0), Non-confirmable (1), Acknowledgement (2), or Reset (3).<br /> <br /> ;Token Length (TKL) (4 bits)<br /> :Indicates the length of the variable-length Token field, which may be 0-8 bytes in length.<br /> <br /> ;CoAP Request/Response Code (8 bits)<br /> :Splits into a 3-bit class and 5-bit detail.<br /> <br /> ;Message ID (16 bits)<br /> :Used to detect message duplication and to match messages of type Acknowledgement/Reset to messages of type Confirmable/Non-confirmable.<br /> <br /> == Implementations ==<br /> <br /> {| class=&quot;wikitable sortable&quot;<br /> |-<br /> ! Name !! Programming Language !! Implemented CoAP version !! Client/Server !! Implemented CoAP features !! License !! Link<br /> |-<br /> | aiocoap || Python 3 || RFC 7252 || Client + Server || Blockwise Transfers, Observe (partial) || MIT || https://pypi.python.org/pypi/aiocoap<br /> |-<br /> | Californium || Java || RFC 7252 || Client + Server || Observe, Blockwise Transfers, DTLS || EPL+EDL || https://www.eclipse.org/californium<br /> |-<br /> | cantcoap || C++/C || RFC 7252 || Client + Server || || BSD || https://github.com/staropram/cantcoap<br /> |-<br /> | Canopus || [[Go (programming language)|Go]] || RFC 7252 || Client + Server || Core || Apache License 2.0 || https://github.com/zubairhamed/canopus<br /> |-<br /> | CoAP implementation for Go || [[Go (programming language)|Go]] || RFC 7252 || Client + Server || Core + Draft Subscribe || MIT || https://github.com/dustin/go-coap<br /> |-<br /> | CoAP.NET || C# || RFC 7252, coap-13, coap-08, coap-03 || Client + Server || Core, Observe, Blockwise Transfers || 3-clause BSD || https://github.com/smeshlink/CoAP.NET<br /> |-<br /> | CoAPSharp || C#, .NET || RFC 7252 || Client + Server || Core, Observe, Block, RD || LGPL || http://www.coapsharp.com<br /> |-<br /> | CoAPthon || Python || RFC 7252 || Client + Server + Forward Proxy + Reverse Proxy || Observe, Multicast server discovery, CoRE Link Format parsing, Block-wise || MIT || https://github.com/Tanganelli/CoAPthon<br /> |-<br /> | CoAP Shell || Java || RFC 7252 || Client || Observe, Blockwise Transfers, DTLS || Apache License 2.0 || https://github.com/tzolov/coap-shell <br /> |-<br /> | Copper || JavaScript (Browser Plugin) || RFC 7252 || Client || Observe, Blockwise Transfers || 3-clause BSD || https://github.com/mkovatsc/Copper https://addons.mozilla.org/firefox/addon/copper-270430/<br /> |-<br /> | eCoAP || C || RFC 7252 || Client + Server || Core || MIT || https://gitlab.com/jobol/ecoap<br /> |-<br /> | Erbium for Contiki || C || RFC 7252 || Client + Server || Observe, Blockwise Transfers || 3-clause BSD || http://www.contiki-os.org/ (er-rest-example)<br /> |-<br /> | iCoAP || Objective-C || RFC 7252 || Client || Core, Observe, Blockwise Transfers || MIT || https://github.com/stuffrabbit/iCoAP<br /> |-<br /> | jCoAP || Java || RFC 7252 || Client + Server || Observe, Blockwise Transfers || Apache License 2.0 || https://code.google.com/p/jcoap/<br /> |-<br /> | libcoap || C || RFC 7252 || Client + Server ||Observe, Blockwise Transfers, DTLS || BSD/GPL || https://github.com/obgm/libcoap<br /> |-<br /> | LibNyoci || C || RFC 7252 || Client + Server || Core, Observe, Block, DTLS || MIT || https://github.com/darconeous/libnyoci<br /> |-<br /> | lobaro-coap || C || RFC 7252 || Client + Server ||Observe, Blockwise Transfers || MIT || http://www.lobaro.com/lobaro-coap<br /> |-<br /> | microcoap || C || RFC 7252 || Client + Server || || MIT || https://github.com/1248/microcoap<br /> |-<br /> | nCoap || Java || RFC 7252 || Client + Server || Observe, Blockwise Transfers, CoRE Link Format, [https://tools.ietf.org/html/draft-kleine-core-coap-endpoint-id-01 Endpoint-ID-Draft] || BSD || https://github.com/okleine/nCoAP<br /> |-<br /> | node-coap || Javascript || RFC 7252 || Client + Server || Core, Observe, Block || MIT || https://github.com/mcollina/node-coap<br /> |-<br /> | Ruby coap || Ruby || RFC 7252 || Client + Server (david) || Core, Observe, Block, RD || MIT, GPL || https://github.com/nning/coap&lt;br/&gt;https://github.com/nning/david<br /> |-<br /> | Sensinode C Device Library || C || RFC 7252 || Client + Server || Core, Observe, Block, RD || Commercial || https://silver.arm.com/browse/SEN00<br /> |-<br /> | Sensinode Java Device Library || Java SE || RFC 7252 || Client + Server || Core, Observe, Block, RD || Commercial || https://silver.arm.com/browse/SEN00<br /> |-<br /> | Sensinode NanoService Platform || Java SE || RFC 7252 || Cloud Server || Core, Observe, Block, RD || Commercial || https://silver.arm.com/browse/SEN00<br /> |-<br /> | SwiftCoAP || Swift || RFC 7252 || Client + Server || Core, Observe, Blockwise Transfers || MIT || https://github.com/stuffrabbit/SwiftCoAP<br /> |-<br /> | TinyOS CoapBlip || nesC/C || coap-13 || Client + Server || Observe, Blockwise Transfers || BSD || http://docs.tinyos.net/tinywiki/index.php/CoAP<br /> |-<br /> | txThings || Python (Twisted) || RFC 7252 || Client + Server || Blockwise Transfers, Observe (partial) || MIT || https://github.com/mwasilak/txThings/<br /> |-<br /> | FreeCoAP || C || RFC 7252 || Client + Server + HTTP/CoAP Proxy ||Core, DTLS, Blockwise Transfers || BSD || https://github.com/keith-cullen/FreeCoAP<br /> |-<br /> | coap-rs || Rust || RFC 7252 || Client + Server || || MIT || https://github.com/Covertness/coap-rs<br /> |-<br /> |YaCoAP<br /> |C<br /> |<br /> |<br /> |<br /> |MIT<br /> |https://github.com/RIOT-Makers/YaCoAP<br /> |}<br /> <br /> <br /> == Courses ==<br /> <br /> * [[Vertiefendes Wahlfach-Projekt]] (2018)<br /> <br /> == References ==<br /> * RFC 7252: https://tools.ietf.org/html/rfc7252<br /> * CoAP: RFC 7252 Constrained Application Protocol https://coap.technology/<br /> * Learning Internet of Things: https://www.oreilly.com/library/view/learning-internet-of/9781783553532/<br /> <br /> [[Category:Documentation]]</div>

Ograsl https://elvis.hcw.ac.at/wiki/index.php?title=Constrained_Application_Protocol&diff=1288 2019-03-11T18:35:43Z

<p>Ograsl: /* Message Format */</p> <hr /> <div>The '''Constrained Application Protocol''' ('''CoAP''') is a specialized web transfer protocol, as defined in RFC 7252, for use with constrained nodes and constrained networks in the Internet of Things.<br /> The protocol is designed for machine-to-machine (M2M) applications such as smart energy and building automation.<br /> <br /> == Features ==<br /> <br /> The work on Constrained Environments aims at realizing the REST architecture in a suitable form for the most constrained nodes and networks. The nodes usually consist of 8-bit microcontrollers with limited amounts of RAM and ROM.<br /> <br /> <br /> CoAP has the following main features:<br /> <br /> * Web protocol fulfilling M2M requirements in constrained environments<br /> * UDP [RFC0768] binding with optional reliability supporting unicast and multicast requests<br /> * Asynchronous message exchanges<br /> * Low header overhead and parsing complexity<br /> * URI and Content-type support<br /> * Simple proxy and caching capabilities<br /> * Stateless HTTP mapping<br /> * Security binding to Datagram Transport Layer Security (DTLS)<br /> <br /> == The Protocol ==<br /> <br /> CoAP is similar to the client/server model of HTTP. M2M interactions typically result in a CoAP implementation acting in both client and server roles. A request is sent by a client to request an action on a resource (identified by a URI) on a server. The server then sends a response with a response code (equivalent to that of HTTP). Therefore, efficiency is very important, so CoAP uses UDP, a datagram-oriented transport.<br /> <br /> CoAP is however a single protocol, with messaging and request/response as just features of the CoAP header<br /> <br /> +----------------------+<br /> | Application |<br /> +----------------------+<br /> +----------------------+ \<br /> | Requests/Responses | |<br /> |----------------------| | CoAP<br /> | Messages | |<br /> +----------------------+ /<br /> +----------------------+<br /> | UDP |<br /> +----------------------+<br /> <br /> [[File:Abstract_Layering_of_CoAP.JPG]]<br /> <br /> == Message Format ==<br /> <br /> By default, the messages are encoded in a simple binary format and transported over UDP. The message format starts with a fixed-size 4-byte header, followed by a variable-length Token value, which can be between 0 and 8 bytes long. Following the Token value comes a sequence of zero or more CoAP Options in Type-Length-Value (TLV) format, optionally followed by a payload that takes up the rest of the datagram.<br /> <br /> 0 1 2 3<br /> 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1<br /> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<br /> |Ver| T | TKL | Code | Message ID |<br /> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<br /> | Token (if any, TKL bytes) ...<br /> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<br /> | Options (if any) ...<br /> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<br /> |1 1 1 1 1 1 1 1| Payload (if any) ...<br /> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<br /> <br /> ;Version (Ver) (2 bits)<br /> :Indicates the CoAP Version number. This must set this field to 1 (binary 01). Other values are reserved for future versions.<br /> <br /> ;Type (T) (2 bits)<br /> :Indicates if this message is of type Confirmable (0), Non-confirmable (1), Acknowledgement (2), or Reset (3).<br /> <br /> ;Token Length (TKL) (4 bits)<br /> :Indicates the length of the variable-length Token field, which may be 0-8 bytes in length.<br /> <br /> ;CoAP Request/Response Code (8 bits)<br /> :Splits into a 3-bit class and 5-bit detail.<br /> <br /> ;Message ID (16 bits)<br /> :Used to detect message duplication and to match messages of type Acknowledgement/Reset to messages of type Confirmable/Non-confirmable.<br /> <br /> == Courses ==<br /> <br /> * [[Vertiefendes Wahlfach-Projekt]] (2018)<br /> <br /> == References ==<br /> * RFC 7252: https://tools.ietf.org/html/rfc7252<br /> * CoAP: RFC 7252 Constrained Application Protocol https://coap.technology/<br /> * Learning Internet of Things: https://www.oreilly.com/library/view/learning-internet-of/9781783553532/<br /> <br /> [[Category:Documentation]]</div>

Ograsl https://elvis.hcw.ac.at/wiki/index.php?title=Constrained_Application_Protocol&diff=1280 2019-03-11T14:28:46Z

<p>Ograsl: /* The Protocol */</p> <hr /> <div>The '''Constrained Application Protocol''' ('''CoAP''') is a specialized web transfer protocol, as defined in RFC 7252, for use with constrained nodes and constrained networks in the Internet of Things.<br /> The protocol is designed for machine-to-machine (M2M) applications such as smart energy and building automation.<br /> <br /> == Features ==<br /> <br /> The work on Constrained Environments aims at realizing the REST architecture in a suitable form for the most constrained nodes and networks. The nodes usually consist of 8-bit microcontrollers with limited amounts of RAM and ROM.<br /> <br /> <br /> CoAP has the following main features:<br /> <br /> * Web protocol fulfilling M2M requirements in constrained environments<br /> * UDP [RFC0768] binding with optional reliability supporting unicast and multicast requests<br /> * Asynchronous message exchanges<br /> * Low header overhead and parsing complexity<br /> * URI and Content-type support<br /> * Simple proxy and caching capabilities<br /> * Stateless HTTP mapping<br /> * Security binding to Datagram Transport Layer Security (DTLS)<br /> <br /> == The Protocol ==<br /> <br /> CoAP is similar to the client/server model of HTTP. M2M interactions typically result in a CoAP implementation acting in both client and server roles. A request is sent by a client to request an action on a resource (identified by a URI) on a server. The server then sends a response with a response code (equivalent to that of HTTP). Therefore, efficiency is very important, so CoAP uses UDP, a datagram-oriented transport.<br /> <br /> CoAP is however a single protocol, with messaging and request/response as just features of the CoAP header<br /> <br /> +----------------------+<br /> | Application |<br /> +----------------------+<br /> +----------------------+ \<br /> | Requests/Responses | |<br /> |----------------------| | CoAP<br /> | Messages | |<br /> +----------------------+ /<br /> +----------------------+<br /> | UDP |<br /> +----------------------+<br /> <br /> [[File:Abstract_Layering_of_CoAP.JPG]]<br /> <br /> == Message Format ==<br /> <br /> By default, the messages are encoded in a simple binary format and transported over UDP. The message format starts with a fixed-size 4-byte header, followed by a variable-length Token value, which can be between 0 and 8 bytes long. Following the Token value comes a sequence of zero or more CoAP Options in Type-Length-Value (TLV) format, optionally followed by a payload that takes up the rest of the datagram.<br /> <br /> 0 1 2 3<br /> 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1<br /> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<br /> |Ver| T | TKL | Code | Message ID |<br /> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<br /> | Token (if any, TKL bytes) ...<br /> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<br /> | Options (if any) ...<br /> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<br /> |1 1 1 1 1 1 1 1| Payload (if any) ...<br /> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<br /> <br /> '''Version (Ver) (2 bits)''' Indicates the CoAP Version number. This must set this field to 1 (binary 01). Other values are reserved for future versions.<br /> <br /> '''Type (T) (2 bits)''' Indicates if this message is of type Confirmable (0), Non-confirmable (1), Acknowledgement (2), or Reset (3).<br /> <br /> '''Token Length (TKL) (4 bits)''' Indicates the length of the variable-length Token field, which may be 0-8 bytes in length.<br /> <br /> '''CoAP Request/Response Code (8 bits)''' Splits into a 3-bit class and 5-bit detail.<br /> <br /> ''' Message ID (16 bits)''' Used to detect message duplication and to match messages of type Acknowledgement/Reset to messages of type Confirmable/Non-confirmable.<br /> <br /> == Courses ==<br /> <br /> * [[Vertiefendes Wahlfach-Projekt]] (2018)<br /> <br /> == References ==<br /> * RFC 7252: https://tools.ietf.org/html/rfc7252<br /> * CoAP: RFC 7252 Constrained Application Protocol https://coap.technology/<br /> * Learning Internet of Things: https://www.oreilly.com/library/view/learning-internet-of/9781783553532/<br /> <br /> [[Category:Documentation]]</div>

Ograsl https://elvis.hcw.ac.at/wiki/index.php?title=Constrained_Application_Protocol&diff=1279 2019-03-11T14:27:53Z

<p>Ograsl: /* Message Format */</p> <hr /> <div>The '''Constrained Application Protocol''' ('''CoAP''') is a specialized web transfer protocol, as defined in RFC 7252, for use with constrained nodes and constrained networks in the Internet of Things.<br /> The protocol is designed for machine-to-machine (M2M) applications such as smart energy and building automation.<br /> <br /> == Features ==<br /> <br /> The work on Constrained Environments aims at realizing the REST architecture in a suitable form for the most constrained nodes and networks. The nodes usually consist of 8-bit microcontrollers with limited amounts of RAM and ROM.<br /> <br /> <br /> CoAP has the following main features:<br /> <br /> * Web protocol fulfilling M2M requirements in constrained environments<br /> * UDP [RFC0768] binding with optional reliability supporting unicast and multicast requests<br /> * Asynchronous message exchanges<br /> * Low header overhead and parsing complexity<br /> * URI and Content-type support<br /> * Simple proxy and caching capabilities<br /> * Stateless HTTP mapping<br /> * Security binding to Datagram Transport Layer Security (DTLS)<br /> <br /> == The Protocol ==<br /> <br /> CoAP is similar to the client/server model of HTTP. M2M interactions typically result in a CoAP implementation acting in both client and server roles. A request is sent by a client to request an action on a resource (identified by a URI) on a server. The server then sends a response with a response code (equivalent to that of HTTP). Therefore, efficiency is very important, so CoAP uses UDP, a datagram-oriented transport.<br /> <br /> CoAP is however a single protocol, with messaging and request/response as just features of the CoAP header<br /> <br /> <br /> +----------------------+<br /> | Application |<br /> +----------------------+<br /> +----------------------+ \<br /> | Requests/Responses | |<br /> |----------------------| | CoAP<br /> | Messages | |<br /> +----------------------+ /<br /> +----------------------+<br /> | UDP |<br /> +----------------------+<br /> <br /> [[File:Abstract_Layering_of_CoAP.JPG]]<br /> <br /> == Message Format ==<br /> <br /> By default, the messages are encoded in a simple binary format and transported over UDP. The message format starts with a fixed-size 4-byte header, followed by a variable-length Token value, which can be between 0 and 8 bytes long. Following the Token value comes a sequence of zero or more CoAP Options in Type-Length-Value (TLV) format, optionally followed by a payload that takes up the rest of the datagram.<br /> <br /> 0 1 2 3<br /> 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1<br /> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<br /> |Ver| T | TKL | Code | Message ID |<br /> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<br /> | Token (if any, TKL bytes) ...<br /> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<br /> | Options (if any) ...<br /> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<br /> |1 1 1 1 1 1 1 1| Payload (if any) ...<br /> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<br /> <br /> '''Version (Ver) (2 bits)''' Indicates the CoAP Version number. This must set this field to 1 (binary 01). Other values are reserved for future versions.<br /> <br /> '''Type (T) (2 bits)''' Indicates if this message is of type Confirmable (0), Non-confirmable (1), Acknowledgement (2), or Reset (3).<br /> <br /> '''Token Length (TKL) (4 bits)''' Indicates the length of the variable-length Token field, which may be 0-8 bytes in length.<br /> <br /> '''CoAP Request/Response Code (8 bits)''' Splits into a 3-bit class and 5-bit detail.<br /> <br /> ''' Message ID (16 bits)''' Used to detect message duplication and to match messages of type Acknowledgement/Reset to messages of type Confirmable/Non-confirmable.<br /> <br /> == Courses ==<br /> <br /> * [[Vertiefendes Wahlfach-Projekt]] (2018)<br /> <br /> == References ==<br /> * RFC 7252: https://tools.ietf.org/html/rfc7252<br /> * CoAP: RFC 7252 Constrained Application Protocol https://coap.technology/<br /> * Learning Internet of Things: https://www.oreilly.com/library/view/learning-internet-of/9781783553532/<br /> <br /> [[Category:Documentation]]</div>

Ograsl https://elvis.hcw.ac.at/wiki/index.php?title=Constrained_Application_Protocol&diff=1278 2019-03-11T14:13:10Z

<p>Ograsl: /* Message Format */</p> <hr /> <div>The '''Constrained Application Protocol''' ('''CoAP''') is a specialized web transfer protocol, as defined in RFC 7252, for use with constrained nodes and constrained networks in the Internet of Things.<br /> The protocol is designed for machine-to-machine (M2M) applications such as smart energy and building automation.<br /> <br /> == Features ==<br /> <br /> The work on Constrained Environments aims at realizing the REST architecture in a suitable form for the most constrained nodes and networks. The nodes usually consist of 8-bit microcontrollers with limited amounts of RAM and ROM.<br /> <br /> <br /> CoAP has the following main features:<br /> <br /> * Web protocol fulfilling M2M requirements in constrained environments<br /> * UDP [RFC0768] binding with optional reliability supporting unicast and multicast requests<br /> * Asynchronous message exchanges<br /> * Low header overhead and parsing complexity<br /> * URI and Content-type support<br /> * Simple proxy and caching capabilities<br /> * Stateless HTTP mapping<br /> * Security binding to Datagram Transport Layer Security (DTLS)<br /> <br /> == The Protocol ==<br /> <br /> CoAP is similar to the client/server model of HTTP. M2M interactions typically result in a CoAP implementation acting in both client and server roles. A request is sent by a client to request an action on a resource (identified by a URI) on a server. The server then sends a response with a response code (equivalent to that of HTTP). Therefore, efficiency is very important, so CoAP uses UDP, a datagram-oriented transport.<br /> <br /> CoAP is however a single protocol, with messaging and request/response as just features of the CoAP header<br /> <br /> <br /> +----------------------+<br /> | Application |<br /> +----------------------+<br /> +----------------------+ \<br /> | Requests/Responses | |<br /> |----------------------| | CoAP<br /> | Messages | |<br /> +----------------------+ /<br /> +----------------------+<br /> | UDP |<br /> +----------------------+<br /> <br /> [[File:Abstract_Layering_of_CoAP.JPG]]<br /> <br /> == Message Format ==<br /> <br /> By default, the messages are encoded in a simple binary format and transported over UDP. The message format starts with a fixed-size 4-byte header, followed by a variable-length Token value, which can be between 0 and 8 bytes long. Following the Token value comes a sqeu<br /> <br /> 0 1 2 3<br /> 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1<br /> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<br /> |Ver| T | TKL | Code | Message ID |<br /> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<br /> | Token (if any, TKL bytes) ...<br /> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<br /> | Options (if any) ...<br /> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<br /> |1 1 1 1 1 1 1 1| Payload (if any) ...<br /> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<br /> <br /> '''Version (Ver) (2 bits)''' Indicates the CoAP Version number. This must set this field to 1 (binary 01). Other values are reserved for future versions.<br /> <br /> '''Type (T) (2 bits)''' Indicates if this message is of type Confirmable (0), Non-confirmable (1), Acknowledgement (2), or Reset (3).<br /> <br /> '''Token Length (TKL) (4 bits)''' Indicates the length of the variable-length Token field, which may be 0-8 bytes in length.<br /> <br /> '''CoAP Request/Response Code (8 bits)''' Splits into a 3-bit class and 5-bit detail.<br /> <br /> ''' Message ID (16 bits)''' Used to detect message duplication and to match messages of type Acknowledgement/Reset to messages of type Confirmable/Non-confirmable.<br /> <br /> == Courses ==<br /> <br /> * [[Vertiefendes Wahlfach-Projekt]] (2018)<br /> <br /> == References ==<br /> * RFC 7252: https://tools.ietf.org/html/rfc7252<br /> * CoAP: RFC 7252 Constrained Application Protocol https://coap.technology/<br /> * Learning Internet of Things: https://www.oreilly.com/library/view/learning-internet-of/9781783553532/<br /> <br /> [[Category:Documentation]]</div>

Ograsl https://elvis.hcw.ac.at/wiki/index.php?title=Constrained_Application_Protocol&diff=1277 2019-03-11T13:41:48Z

<p>Ograsl: /* Message Format */</p> <hr /> <div>The '''Constrained Application Protocol''' ('''CoAP''') is a specialized web transfer protocol, as defined in RFC 7252, for use with constrained nodes and constrained networks in the Internet of Things.<br /> The protocol is designed for machine-to-machine (M2M) applications such as smart energy and building automation.<br /> <br /> == Features ==<br /> <br /> The work on Constrained Environments aims at realizing the REST architecture in a suitable form for the most constrained nodes and networks. The nodes usually consist of 8-bit microcontrollers with limited amounts of RAM and ROM.<br /> <br /> <br /> CoAP has the following main features:<br /> <br /> * Web protocol fulfilling M2M requirements in constrained environments<br /> * UDP [RFC0768] binding with optional reliability supporting unicast and multicast requests<br /> * Asynchronous message exchanges<br /> * Low header overhead and parsing complexity<br /> * URI and Content-type support<br /> * Simple proxy and caching capabilities<br /> * Stateless HTTP mapping<br /> * Security binding to Datagram Transport Layer Security (DTLS)<br /> <br /> == The Protocol ==<br /> <br /> CoAP is similar to the client/server model of HTTP. M2M interactions typically result in a CoAP implementation acting in both client and server roles. A request is sent by a client to request an action on a resource (identified by a URI) on a server. The server then sends a response with a response code (equivalent to that of HTTP). Therefore, efficiency is very important, so CoAP uses UDP, a datagram-oriented transport.<br /> <br /> CoAP is however a single protocol, with messaging and request/response as just features of the CoAP header<br /> <br /> <br /> +----------------------+<br /> | Application |<br /> +----------------------+<br /> +----------------------+ \<br /> | Requests/Responses | |<br /> |----------------------| | CoAP<br /> | Messages | |<br /> +----------------------+ /<br /> +----------------------+<br /> | UDP |<br /> +----------------------+<br /> <br /> [[File:Abstract_Layering_of_CoAP.JPG]]<br /> <br /> == Message Format ==<br /> <br /> By default, the messages are encoded in a simple binary format and transported over UDP. The message format starts with a fixed-size 4-byte header, followed by a variable-length Token value, which can be between 0 and 8 bytes long. Following the Token value comes a sqeu<br /> <br /> 0 1 2 3<br /> 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1<br /> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<br /> |Ver| T | TKL | Code | Message ID |<br /> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<br /> | Token (if any, TKL bytes) ...<br /> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<br /> | Options (if any) ...<br /> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<br /> |1 1 1 1 1 1 1 1| Payload (if any) ...<br /> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<br /> <br /> '''Version (Ver) (2 bits)'''<br /> Indicates the CoAP Version number<br /> <br /> == Courses ==<br /> <br /> * [[Vertiefendes Wahlfach-Projekt]] (2018)<br /> <br /> == References ==<br /> * RFC 7252: https://tools.ietf.org/html/rfc7252<br /> * CoAP: RFC 7252 Constrained Application Protocol https://coap.technology/<br /> * Learning Internet of Things: https://www.oreilly.com/library/view/learning-internet-of/9781783553532/<br /> <br /> [[Category:Documentation]]</div>

Ograsl https://elvis.hcw.ac.at/wiki/index.php?title=Constrained_Application_Protocol&diff=1276 2019-03-11T13:38:21Z

<p>Ograsl: </p> <hr /> <div>The '''Constrained Application Protocol''' ('''CoAP''') is a specialized web transfer protocol, as defined in RFC 7252, for use with constrained nodes and constrained networks in the Internet of Things.<br /> The protocol is designed for machine-to-machine (M2M) applications such as smart energy and building automation.<br /> <br /> == Features ==<br /> <br /> The work on Constrained Environments aims at realizing the REST architecture in a suitable form for the most constrained nodes and networks. The nodes usually consist of 8-bit microcontrollers with limited amounts of RAM and ROM.<br /> <br /> <br /> CoAP has the following main features:<br /> <br /> * Web protocol fulfilling M2M requirements in constrained environments<br /> * UDP [RFC0768] binding with optional reliability supporting unicast and multicast requests<br /> * Asynchronous message exchanges<br /> * Low header overhead and parsing complexity<br /> * URI and Content-type support<br /> * Simple proxy and caching capabilities<br /> * Stateless HTTP mapping<br /> * Security binding to Datagram Transport Layer Security (DTLS)<br /> <br /> == The Protocol ==<br /> <br /> CoAP is similar to the client/server model of HTTP. M2M interactions typically result in a CoAP implementation acting in both client and server roles. A request is sent by a client to request an action on a resource (identified by a URI) on a server. The server then sends a response with a response code (equivalent to that of HTTP). Therefore, efficiency is very important, so CoAP uses UDP, a datagram-oriented transport.<br /> <br /> CoAP is however a single protocol, with messaging and request/response as just features of the CoAP header<br /> <br /> <br /> +----------------------+<br /> | Application |<br /> +----------------------+<br /> +----------------------+ \<br /> | Requests/Responses | |<br /> |----------------------| | CoAP<br /> | Messages | |<br /> +----------------------+ /<br /> +----------------------+<br /> | UDP |<br /> +----------------------+<br /> <br /> [[File:Abstract_Layering_of_CoAP.JPG]]<br /> <br /> == Message Format ==<br /> <br /> By default, the messages are encoded in a simple binary format and transported over UDP. The messages are encoded in a simple binary format<br /> <br /> 0 1 2 3<br /> 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1<br /> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<br /> |Ver| T | TKL | Code | Message ID |<br /> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<br /> | Token (if any, TKL bytes) ...<br /> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<br /> | Options (if any) ...<br /> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<br /> |1 1 1 1 1 1 1 1| Payload (if any) ...<br /> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<br /> <br /> == Courses ==<br /> <br /> * [[Vertiefendes Wahlfach-Projekt]] (2018)<br /> <br /> == References ==<br /> * RFC 7252: https://tools.ietf.org/html/rfc7252<br /> * CoAP: RFC 7252 Constrained Application Protocol https://coap.technology/<br /> * Learning Internet of Things: https://www.oreilly.com/library/view/learning-internet-of/9781783553532/<br /> <br /> [[Category:Documentation]]</div>

Ograsl https://elvis.hcw.ac.at/wiki/index.php?title=Constrained_Application_Protocol&diff=1275 2019-03-11T13:10:34Z

<p>Ograsl: </p> <hr /> <div>The '''Constrained Application Protocol''' ('''CoAP''') is a specialized web transfer protocol, as defined in RFC 7252, for use with constrained nodes and constrained networks in the Internet of Things.<br /> The protocol is designed for machine-to-machine (M2M) applications such as smart energy and building automation.<br /> <br /> == Features ==<br /> <br /> The work on Constrained Environments aims at realizing the REST architecture in a suitable form for the most constrained nodes and networks. The nodes usually consist of 8-bit microcontrollers with limited amounts of RAM and ROM.<br /> <br /> <br /> CoAP has the following main features:<br /> <br /> * Web protocol fulfilling M2M requirements in constrained environments<br /> * UDP [RFC0768] binding with optional reliability supporting unicast and multicast requests<br /> * Asynchronous message exchanges<br /> * Low header overhead and parsing complexity<br /> * URI and Content-type support<br /> * Simple proxy and caching capabilities<br /> * Stateless HTTP mapping<br /> * Security binding to Datagram Transport Layer Security (DTLS)<br /> <br /> == The Protocol ==<br /> <br /> <br /> [[File:Abstract_Layering_of_CoAP.jpg]]<br /> <br /> == Courses ==<br /> <br /> * [[Vertiefendes Wahlfach-Projekt]] (2018)<br /> <br /> == References ==<br /> * RFC 7252: https://tools.ietf.org/html/rfc7252<br /> * CoAP: RFC 7252 Constrained Application Protocol https://coap.technology/<br /> * Learning Internet of Things: https://www.oreilly.com/library/view/learning-internet-of/9781783553532/<br /> <br /> [[Category:Documentation]]</div>

Ograsl https://elvis.hcw.ac.at/wiki/index.php?title=File:Abstract_Layering_of_CoAP.JPG&diff=1274 2019-03-11T13:09:29Z

<p>Ograsl: </p> <hr /> <div></div>

Ograsl https://elvis.hcw.ac.at/wiki/index.php?title=Constrained_Application_Protocol&diff=1273 2019-03-11T13:00:39Z

<p>Ograsl: </p> <hr /> <div>The '''Constrained Application Protocol''' ('''CoAP''') is a specialized web transfer protocol, as defined in RFC 7252, for use with constrained nodes and constrained networks in the Internet of Things.<br /> The protocol is designed for machine-to-machine (M2M) applications such as smart energy and building automation.<br /> <br /> == Features ==<br /> <br /> The work on Constrained Environments aims at realizing the REST architecture in a suitable form for the most constrained nodes and networks. The nodes usually consist of 8-bit microcontrollers with limited amounts of RAM and ROM.<br /> <br /> <br /> CoAP has the following main features:<br /> <br /> * Web protocol fulfilling M2M requirements in constrained environments<br /> * UDP [RFC0768] binding with optional reliability supporting unicast and multicast requests<br /> * Asynchronous message exchanges<br /> * Low header overhead and parsing complexity<br /> * URI and Content-type support<br /> * Simple proxy and caching capabilities<br /> * Stateless HTTP mapping<br /> * Security binding to Datagram Transport Layer Security (DTLS)<br /> <br /> == Message Formats ==<br /> <br /> <br /> == Courses ==<br /> <br /> * [[Vertiefendes Wahlfach-Projekt]] (2018)<br /> <br /> == References ==<br /> * RFC 7252: https://tools.ietf.org/html/rfc7252<br /> * CoAP: RFC 7252 Constrained Application Protocol https://coap.technology/<br /> * Learning Internet of Things: https://www.oreilly.com/library/view/learning-internet-of/9781783553532/<br /> <br /> [[Category:Documentation]]</div>

Ograsl https://elvis.hcw.ac.at/wiki/index.php?title=Constrained_Application_Protocol&diff=1272 2019-03-11T12:20:11Z

<p>Ograsl: </p> <hr /> <div>The '''Constrained Application Protocol''' ('''CoAP''') is a specialized web transfer protocol for use with constrained nodes and constrained networks in the Internet of Things. <br /> The protocol is designed for machine-to-machine (M2M) applications such as smart energy and building automation.<br /> <br /> <br /> <br /> Das '''Constrained Application Protocol''' ('''CoAP''') ist ein spezielles Übertragungsprotokoll zur Verwendung auf Constrained-Nodes und Constrained-Devices im Internet der Dinge (engl. Internet of Things, IoT) . Das Protokoll ist für Maschine-to-Maschine- (M2M) Anwendungen wie intelligente Energie- und Gebäudeautomation ausgelegt und im RFC 7252 dolumentiert. Wie auch HTTP, basiert CoAP auf Representational State Transfer (REST), dem Architekturmodell für Webservices, bei dem Ressourcen von Servern durch einen Anwendungsprozess kontrolliert und über die Uniform Resource Identifiers (URI) identifiziert werden.<br /> <br /> <br /> == Courses ==<br /> <br /> * [[Vertiefendes Wahlfach-Projekt]] (2018)<br /> <br /> == References ==<br /> * RFC 7252: https://tools.ietf.org/html/rfc7252<br /> * CoAP: RFC 7252 Constrained Application Protocol https://coap.technology/<br /> * Learning Internet of Things: https://www.oreilly.com/library/view/learning-internet-of/9781783553532/<br /> <br /> [[Category:Documentation]]</div>

Ograsl https://elvis.hcw.ac.at/wiki/index.php?title=Constrained_Application_Protocol&diff=1271 2019-03-11T12:19:35Z

<p>Ograsl: </p> <hr /> <div>The Constrained Application Protocol (CoAP) is a specialized web transfer protocol for use with constrained nodes and constrained networks in the Internet of Things. <br /> The protocol is designed for machine-to-machine (M2M) applications such as smart energy and building automation.<br /> <br /> <br /> <br /> Das '''Constrained Application Protocol''' ('''CoAP''') ist ein spezielles Übertragungsprotokoll zur Verwendung auf Constrained-Nodes und Constrained-Devices im Internet der Dinge (engl. Internet of Things, IoT) . Das Protokoll ist für Maschine-to-Maschine- (M2M) Anwendungen wie intelligente Energie- und Gebäudeautomation ausgelegt und im RFC 7252 dolumentiert. Wie auch HTTP, basiert CoAP auf Representational State Transfer (REST), dem Architekturmodell für Webservices, bei dem Ressourcen von Servern durch einen Anwendungsprozess kontrolliert und über die Uniform Resource Identifiers (URI) identifiziert werden.<br /> <br /> <br /> == Courses ==<br /> <br /> * [[Vertiefendes Wahlfach-Projekt]] (2018)<br /> <br /> == References ==<br /> * RFC 7252: https://tools.ietf.org/html/rfc7252<br /> * CoAP: RFC 7252 Constrained Application Protocol https://coap.technology/<br /> * Learning Internet of Things: https://www.oreilly.com/library/view/learning-internet-of/9781783553532/<br /> <br /> [[Category:Documentation]]</div>

Ograsl https://elvis.hcw.ac.at/wiki/index.php?title=Constrained_Application_Protocol&diff=1270 2019-03-11T10:01:33Z

<p>Ograsl: </p> <hr /> <div>Das '''Constrained Application Protocol''' ('''CoAP''') ist ein spezielles Übertragungsprotokoll zur Verwendung auf Constrained-Nodes und Constrained-Devices im Internet der Dinge (engl. Internet of Things, IoT) . Das Protokoll ist für Maschine-to-Maschine- (M2M) Anwendungen wie intelligente Energie- und Gebäudeautomation ausgelegt und im RFC 7252 dolumentiert. Wie auch HTTP, basiert CoAP auf Representational State Transfer (REST), dem Architekturmodell für Webservices, bei dem Ressourcen von Servern durch einen Anwendungsprozess kontrolliert und über die Uniform Resource Identifiers (URI) identifiziert werden.</div>

Ograsl https://elvis.hcw.ac.at/wiki/index.php?title=Constrained_Application_Protocol&diff=1269 2019-03-11T10:01:21Z

<p>Ograsl: </p> <hr /> <div>Das '''Constrained Application Protocol''' ('''CoAP''') ist ein spezielles Übertragungsprotokoll zur Verwendung auf Constrained-Nodes und Constrained-Devices im Internet der Dinge (engl. Internet of Things, IoT) . Das Protokoll ist für Maschine-to-Maschine- (M2M) Anwendungen wie intelligente Energie- und Gebäudeautomation ausgelegt und im RFD 7252 dolumentiert. Wie auch HTTP, basiert CoAP auf Representational State Transfer (REST), dem Architekturmodell für Webservices, bei dem Ressourcen von Servern durch einen Anwendungsprozess kontrolliert und über die Uniform Resource Identifiers (URI) identifiziert werden.</div>

Ograsl https://elvis.hcw.ac.at/wiki/index.php?title=Constrained_Application_Protocol&diff=1268 2019-03-11T09:54:09Z

<p>Ograsl: Created page with &quot;Das &#039;&#039;&#039;Constrained Application Protocol&#039;&#039;&#039; (&#039;&#039;&#039;CoAP&#039;&#039;&#039;) ist ein spezielles Übertrangungsprotokoll zur Verwendung auf constrained (engl. &quot;eingeschränkt&quot;)&quot;</p> <hr /> <div>Das '''Constrained Application Protocol''' ('''CoAP''') ist ein spezielles Übertrangungsprotokoll zur Verwendung auf constrained (engl. &quot;eingeschränkt&quot;)</div>

Ograsl