Revision as of 22:57, 19 May 2013 edit 84.137.31.204 (talk) →Message Formats: TCP is out, DTLS is in ← Previous edit		Revision as of 23:02, 19 May 2013 edit undo 84.137.31.204 (talk) →Message Formats: CoAP option coding is not like ICMP Next edit →
Line 22: ==Message Formats== CoAP makes use of two message types, requests and responses, using a simple binary base header format. The base header may be followed by options in ~~ICMP-style~~an optimized Type-Length-Value format. CoAP is by default bound to UDP and optionally to [[DTLS]], providing a high level of communications security. Any bytes after the headers in the packet are considered the message body if any. The length of the message body is implied by the datagram length. When bound to UDP the entire message MUST fit within a single datagram. When used with [[6LoWPAN]] as defined in [http://tools.ietf.org/html/rfc4944 RFC 4944], messages SHOULD fit into a single IEEE 802.15.4 frame to minimize fragmentation.

Constrained Application Protocol: Difference between revisions