← Back to the chapter · Previous detail

Technical detail · CoAP Lab: Message Construction

Evidence for block transfers and feature acceptance

CoAP Block2 transfers retrieve a representation, the resource’s encoded value, in numbered response blocks that must assemble into one consistent result.

A transfer planning record calls for payload size, negotiated block size, total block count, retry limit, token (the request-response matching value) and representation ETag (a version tag) or version. Verify assembled length and final checksum as well as block numbers. A model showing progress does not establish firmware or server acceptance; that requires a constrained-link trace and the final checksum.

Feature acceptance notes also call for discovery to list supported resources and content formats, configuration PUT (state-update request) retries to preserve the intended state, and Observe (continuing GET subscription) cancellation to end updates. Each feature needs evidence of its own outcome.

← Back to the chapter · Previous detail