metasystema.org
CurrentPROPOSED STANDARDIETF stream

RFC 8132: PATCH and FETCH Methods for the Constrained Application Protocol (CoAP)

In plain English — editorial summary, not part of the RFC

The methods defined in RFC 7252 for the Constrained Application Protocol (CoAP) only allow access to a complete resource, not to parts of a resource. In case of resources with larger or complex data, or in situations where resource continuity is required, replacing or requesting the whole resource is undesirable. Several applications using CoAP need to access parts of the resources. This specification defines the new CoAP methods, FETCH, PATCH, and iPATCH, which are used to access and update parts of a resource.

Document record

Document ID
RFC8132
Published
April 2017
Authors
P. van der Stok; C. Bormann; A. Sehgal
Status
PROPOSED STANDARD
Stream
IETF
Area
wit
Pages
21
Also known as
—

Topics

Related documents

Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.

Also filed under

About this page

The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.

Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.

Data sources · Editorial policy · Report a correction · What is an RFC?

canonical URL: /rfc/8132-patch-and-fetch-methods-for-the-constrained-application-protocol-coap