PATCH and FETCH Methods for the Constrained Application Protocol
RFC 8132, “PATCH and FETCH Methods for the Constrained Application Protocol”, is a Proposed Standard document published in April 2017 by P. van der Stok, C. Bormann, A. Sehgal. The canonical text is published by the RFC Editor.
Abstract
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.
What “Proposed Standard” means
An entry-level standards-track specification: stable, peer-reviewed and a solid basis for implementation, though it may still evolve before becoming an Internet Standard.
The canonical text of RFC 8132 is hosted at rfc-editor.org. Available in TXT,HTML.
- RFC 8131 RSVP-TE Signaling Procedure for End-to-End GMPLS Restoration and Resource Sharing
- RFC 8133 The Security Evaluated Standardized Password-Authenticated Key Exchange Protocol
- RFC 8130 RTP Payload Format for the Mixed Excitation Linear Prediction Enhanced Codec
- RFC 8134 Management Incident Lightweight Exchange Implementation Report
- RFC 8129 Authentication Indicator in Kerberos Tickets
- RFC 8135 Complex Addressing in IPv6
- RFC 8128 IETF Appointment Procedures for the ICANN Root Zone Evolution Review Committee
- RFC 8136 Additional Transition Functionality for IPv6