Protocol Action: 'Block-wise transfers in CoAP' to Proposed Standard (draft-ietf-core-block-21.txt)
The IESG <email@example.com> Mon, 11 July 2016 15:16 UTC
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id A476F12D1C1; Mon, 11 Jul 2016 08:16:36 -0700 (PDT)
Content-Type: text/plain; charset="us-ascii"
From: The IESG <firstname.lastname@example.org>
To: "IETF-Announce" <email@example.com>
Subject: Protocol Action: 'Block-wise transfers in CoAP' to Proposed Standard (draft-ietf-core-block-21.txt)
Date: Mon, 11 Jul 2016 08:16:36 -0700
Cc: firstname.lastname@example.org, email@example.com, The IESG <firstname.lastname@example.org>, email@example.com, firstname.lastname@example.org, email@example.com, firstname.lastname@example.org
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf-announce>, <mailto:email@example.com?subject=unsubscribe>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:firstname.lastname@example.org?subject=subscribe>
X-List-Received-Date: Mon, 11 Jul 2016 15:16:36 -0000
The IESG has approved the following document: - 'Block-wise transfers in CoAP' (draft-ietf-core-block-21.txt) as Proposed Standard This document is the product of the Constrained RESTful Environments Working Group. The IESG contact persons are Alexey Melnikov, Ben Campbell and Alissa Cooper. A URL of this Internet Draft is: https://datatracker.ietf.org/doc/draft-ietf-core-block/ Technical Summary This specification extends the CoAP protocol (RFC 7252) with a pair of "Block" options to enable the transport of large payloads through multiple request-response pairs. In constrained environments, these blockwise transfers have an advantage over fragmentation at lower layers (e.g., IP), since the server can be truly stateless with no need for a connection setup or other server-side memory of previous block transfers. The specification is intended for standards-track, as it is a widely implemented extension of a standards-track protocol. Review and Consensus The specification was developed along with the base CoAP specification and received significant review by active WG members and implementers. Two major discussions were had and resolved while finding consensus. Several implementations of this final version have completed an interoperability test event with a very good score. Further implementer feedback also was positive. Personnel Matthias Kovatsch is the document shepherd. Alexey Melnikov is the responsible Area Director.