Movatterモバイル変換


[0]ホーム

URL:


Search RFCs

Advanced Search

RFC Editor

RFC 8132

PATCH and FETCH Methods for the Constrained Application Protocol (CoAP),April 2017

File formats:
icon for text fileicon for PDFicon for HTML
Status:
PROPOSED STANDARD
Authors:
P. van der Stok
C. Bormann
A. Sehgal
Stream:
IETF
Source:
core (wit)

Cite this RFC:TXT  | XML  |  BibTeX

DOI:  https://doi.org/10.17487/RFC8132

Discuss this RFC: Send questions or comments to the mailing listcore@ietf.org

Other actions:Submit Errata  | Find IPR Disclosures from the IETF  | View History of RFC 8132


Abstract

The methods defined in RFC 7252 for the Constrained ApplicationProtocol (CoAP) only allow access to a complete resource, not toparts of a resource. In case of resources with larger or complexdata, or in situations where resource continuity is required,replacing or requesting the whole resource is undesirable. Severalapplications using CoAP need to access parts of the resources.

This specification defines the new CoAP methods, FETCH, PATCH, andiPATCH, which are used to access and update parts of a resource.


For the definition ofStatus,seeRFC 2026.

For the definition ofStream, seeRFC 8729.




IABIANAIETFIRTFISEISOCIETF Trust
ReportsPrivacy StatementSite MapContact Us

Advanced Search

[8]ページ先頭

©2009-2026 Movatter.jp