⌕ Поиск по атласу

IETF · RFC · RFC8132

RFC8132 · PATCH and FETCH Methods for the Constrained Application Protocol (CoAP)

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

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.

Официальная английская аннотация

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.

Связи документа

Официальный источник · 2017-04-01

Полные импортированные сведения карточки
{
  "id": "RFC8132",
  "number": 8132,
  "title_en": "PATCH and FETCH Methods for the Constrained Application Protocol (CoAP)",
  "title_ru": "",
  "summary_ru": "",
  "purpose_ru": "",
  "use_ru": "",
  "full_translation_path": "",
  "full_translation_checked_at": "",
  "full_translation_source_sha256": "",
  "architect_note_ru": "",
  "topics_ru": [],
  "translation_state": "not_prepared",
  "verification_level": "not_prepared",
  "verification_level_ru": "Русская выжимка не подготовлена",
  "verification_note_ru": "",
  "abstract_en": "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.",
  "authors": [
    "P. van der Stok",
    "C. Bormann",
    "A. Sehgal"
  ],
  "organizations": [],
  "publication_date": "2017-04-01",
  "current_status": "PROPOSED STANDARD",
  "current_status_ru": "Предлагаемый стандарт",
  "publication_status": "PROPOSED STANDARD",
  "publication_status_ru": "Предлагаемый стандарт",
  "lifecycle": "active",
  "lifecycle_ru": "Действующий",
  "stream": "IETF",
  "stream_ru": "IETF",
  "area": "wit",
  "area_ru": "Веб и транспорт Интернета",
  "working_group": "core",
  "source_draft": "draft-ietf-core-etch-04",
  "page_count": 21,
  "doi": "10.17487/RFC8132",
  "keywords": [
    "CoAP"
  ],
  "formats": [
    "TXT",
    "HTML"
  ],
  "relations": {
    "obsoletes": [],
    "obsoleted_by": [],
    "updates": [],
    "updated_by": [],
    "is_also": [],
    "see_also": []
  },
  "links": {
    "info": "https://www.rfc-editor.org/info/rfc8132/",
    "html": "https://www.rfc-editor.org/rfc/rfc8132.html",
    "txt": "https://www.rfc-editor.org/rfc/rfc8132.txt",
    "datatracker": "https://datatracker.ietf.org/doc/rfc8132/"
  }
}