Skip to main content

Key Update for OSCORE (KUDOS)

Document Type Replaced Internet-Draft (individual)
Expired & archived
Authors Rikard Höglund , Marco Tiloca
Last updated 2021-10-25
Replaced by draft-ietf-core-oscore-key-update
RFC stream (None)
Intended RFC status (None)
Stream Stream state (No stream defined)
Consensus boilerplate Unknown
RFC Editor Note (None)
IESG IESG state Replaced by draft-ietf-core-oscore-key-update
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:


Object Security for Constrained RESTful Environments (OSCORE) uses AEAD algorithms to ensure confidentiality and integrity of exchanged messages. Due to known issues allowing forgery attacks against AEAD algorithms, limits should be followed on the number of times a specific key is used for encryption or decryption. This document defines how two OSCORE peers must follow these limits and what steps they must take to preserve the security of their communications. Therefore, this document updates RFC8613. Furthermore, this document specifies Key Update for OSCORE (KUDOS), a lightweight procedure that two peers can use to update their keying material and establish a new OSCORE Security Context.


Rikard Höglund
Marco Tiloca

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