
datatracker.ietf.org/doc/html/rfc7959
Preview meta tags from the datatracker.ietf.org website.
Linked Hostnames
6- 44 links todatatracker.ietf.org
- 16 links towww.rfc-editor.org
- 1 link togithub.com
- 1 link tomailarchive.ietf.org
- 1 link totrustee.ietf.org
- 1 link towww.ics.uci.edu
Thumbnail

Search Engine Appearance
https://datatracker.ietf.org/doc/html/rfc7959
RFC 7959: Block-Wise Transfers in the Constrained Application Protocol (CoAP)
Block-Wise Transfers in the Constrained Application Protocol (CoAP) (RFC 7959, )
Bing
RFC 7959: Block-Wise Transfers in the Constrained Application Protocol (CoAP)
https://datatracker.ietf.org/doc/html/rfc7959
Block-Wise Transfers in the Constrained Application Protocol (CoAP) (RFC 7959, )
DuckDuckGo

RFC 7959: Block-Wise Transfers in the Constrained Application Protocol (CoAP)
Block-Wise Transfers in the Constrained Application Protocol (CoAP) (RFC 7959, )
General Meta Tags
10- titleRFC 7959 - Block-Wise Transfers in the Constrained Application Protocol (CoAP)
- charsetutf-8
- X-UA-CompatibleIE=edge
- viewportwidth=device-width, initial-scale=1
- descriptionBlock-Wise Transfers in the Constrained Application Protocol (CoAP) (RFC 7959, )
Open Graph Meta Tags
10- og:titleRFC 7959: Block-Wise Transfers in the Constrained Application Protocol (CoAP)
- og:urlhttps://datatracker.ietf.org/doc/html/rfc7959
- og:site_nameIETF Datatracker
- og:descriptionThe Constrained Application Protocol (CoAP) is a RESTful transfer protocol for constrained nodes and networks. Basic CoAP messages work well for small payloads from sensors and actuators; however, applications will need to transfer larger payloads occasionally -- for instance, for firmware updates. In contrast to HTTP, where TCP does the grunt work of segmenting and resequencing, CoAP is based on datagram transports such as UDP or Datagram Transport Layer Security (DTLS). These transports only offer fragmentation, which is even more problematic in constrained nodes and networks, limiting the maximum size of resource representations that can practically be transferred. Instead of relying on IP fragmentation, this specification extends basic CoAP with a pair of "Block" options for transferring multiple blocks of information from a resource representation in multiple request-response pairs. In many important cases, the Block options enable a server to be truly stateless: the server can handle each block transfer separately, with no need for a connection setup or other server-side memory of previous block transfers. Essentially, the Block options provide a minimal way to transfer larger representations in a block-wise fashion. A CoAP implementation that does not support these options generally is limited in the size of the representations that can be exchanged, so there is an expectation that the Block options will be widely used in CoAP implementations. Therefore, this specification updates RFC 7252.
- og:typearticle
Twitter Meta Tags
1- twitter:cardsummary_large_image
Link Tags
12- alternate/feed/document-changes/rfc7959/
- apple-touch-iconhttps://static.ietf.org/dt/12.45.0/ietf/images/ietf-logo-nor-180.png
- canonicalhttps://datatracker.ietf.org/doc/html/rfc7959
- iconhttps://static.ietf.org/dt/12.45.0/ietf/images/ietf-logo-nor-32.png
- iconhttps://static.ietf.org/dt/12.45.0/ietf/images/ietf-logo-nor-16.png
Emails
3- cabo%40tzi.org
- zach.shelby%40arm.com
- [email protected]?subject=rfc7959
Links
64- http://trustee.ietf.org/license-info
- http://www.ics.uci.edu/~fielding/pubs/dissertation/fielding_dissertation.pdf
- http://www.rfc-editor.org/info/rfc2119
- http://www.rfc-editor.org/info/rfc4919
- http://www.rfc-editor.org/info/rfc4944