RFC 8613: Object Security for Constrained RESTful Environments (OSCORE)
In plain English — editorial summary, not part of the RFC
This document defines Object Security for Constrained RESTful Environments (OSCORE), a method for application-layer protection of the Constrained Application Protocol (CoAP), using CBOR Object Signing and Encryption (COSE). OSCORE provides end-to-end protection between endpoints communicating using CoAP or CoAP-mappable HTTP. OSCORE is designed for constrained nodes and networks supporting a range of proxy operations, including translation between different transport protocols. Although an optional functionality of CoAP, OSCORE alters CoAP options processing and IANA registration. Therefore, this document updates RFC 7252.
Document record
- Document ID
- RFC8613
- Published
- July 2019
- Authors
- G. Selander; J. Mattsson; F. Palombini; L. Seitz
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- wit
- Pages
- 94
- Also known as
- —
- Updates:
- RFC 7252
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 8622A Lower-Effort Per-Hop Behavior (LE PHB) for Differentiated ServicesCurrent
June 2019
- RFC 8587NFS Version 4.0 Trunking UpdateCurrent
May 2019
- RFC 8586Loop Detection in Content Delivery Networks (CDNs)Current
April 2019
- RFC 8673HTTP Random Access and Live ContentCurrent
November 2019
- RFC 8680Forward Error Correction (FEC) Framework Extension to Sliding Window CodesCurrent
January 2020
- RFC 8681Sliding Window Random Linear Code (RLC) Forward Erasure Correction (FEC) Schemes for FECFRAMECurrent
January 2020
- RFC 8682TinyMT32 Pseudorandom Number Generator (PRNG)Current
January 2020
- RFC 8540Stream Control Transmission Protocol: Errata and Issues in RFC 4960Obsoleted
February 2019
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?