Skip to main content

Object Security of CoAP (OSCOAP)
draft-selander-ace-object-security-06

Document Type Replaced Internet-Draft (individual)
Expired & archived
Authors Göran Selander , John Preuß Mattsson , Francesca Palombini , Ludwig Seitz
Last updated 2016-10-11
Replaced by RFC 8613
RFC stream (None)
Intended RFC status (None)
Formats
Stream Stream state (No stream defined)
Consensus boilerplate Unknown
RFC Editor Note (None)
IESG IESG state Replaced by draft-ietf-core-object-security
Telechat date (None)
Responsible AD (None)
Send notices to (None)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:

Abstract

This memo defines Object Security of CoAP (OSCOAP), a method for application layer protection of message exchanges with the Constrained Application Protocol (CoAP), using the CBOR Object Signing and Encryption (COSE) format. OSCOAP provides end-to-end encryption, integrity and replay protection to CoAP payload, options, and header fields, as well as a secure binding between CoAP request and response messages. The use of OSCOAP is signaled with the CoAP option Object-Security, also defined in this memo.

Authors

Göran Selander
John Preuß Mattsson
Francesca Palombini
Ludwig Seitz

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)