OSCORE Implementation Guidance
draft-amsuess-lwig-oscore-00

Document Type Expired Internet-Draft (individual)
Author Christian Amsüss 
Last updated 2020-10-31 (latest revision 2020-04-29)
Stream (None)
Intended RFC status (None)
Formats
Expired & archived
pdf htmlized (tools) htmlized bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state Expired
Telechat date
Responsible AD (None)
Send notices to (None)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft can be found at
https://www.ietf.org/archive/id/draft-amsuess-lwig-oscore-00.txt

Abstract

Object Security for Constrained RESTful Environments (OSCORE) is a means of end-to-end protection of short request/response exchanges for tiny devices, typically transported using the Constrained Application Protocol (CoAP). This document aims to assist implementers in leveraging the optimizations catered for by the combination of CoAP and OSCORE, and by generally providing experience from earlier implementations.

Authors

Christian Amsüss (christian@amsuess.com)

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