[core] I-D Action: draft-ietf-core-oscore-key-update-02.txt
internet-drafts@ietf.org Mon, 11 July 2022 13:05 UTC
Return-Path: <internet-drafts@ietf.org>
X-Original-To: core@ietf.org
Delivered-To: core@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 83022C06D829; Mon, 11 Jul 2022 06:05:28 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: internet-drafts@ietf.org
To: i-d-announce@ietf.org
Cc: core@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 8.6.0
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: core@ietf.org
Message-ID: <165754472852.5665.1680962263493453761@ietfa.amsl.com>
Date: Mon, 11 Jul 2022 06:05:28 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/core/mEUweSGwQsruo-nppcZpNrQ9Cv8>
Subject: [core] I-D Action: draft-ietf-core-oscore-key-update-02.txt
X-BeenThere: core@ietf.org
X-Mailman-Version: 2.1.39
List-Id: "Constrained RESTful Environments \(CoRE\) Working Group list" <core.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/core>, <mailto:core-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/core/>
List-Post: <mailto:core@ietf.org>
List-Help: <mailto:core-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/core>, <mailto:core-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 11 Jul 2022 13:05:28 -0000
A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Constrained RESTful Environments WG of the IETF. Title : Key Update for OSCORE (KUDOS) Authors : Rikard Höglund Marco Tiloca Filename : draft-ietf-core-oscore-key-update-02.txt Pages : 50 Date : 2022-07-11 Abstract: 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. Among other reasons, approaching key usage limits requires updating the OSCORE keying material before communications can securely continue. This document defines how two OSCORE peers must follow these key usage limits and what steps they must take to preserve the security of their communications. Also, it 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. Finally, this document specifies a method that two peers can use to update their OSCORE identifiers, as a stand-alone procedure or embedded in a KUDOS execution. Thus, this document updates RFC 8613. The IETF datatracker status page for this draft is: https://datatracker.ietf.org/doc/draft-ietf-core-oscore-key-update/ There is also an HTML version available at: https://www.ietf.org/archive/id/draft-ietf-core-oscore-key-update-02.html A diff from the previous version is available at: https://www.ietf.org/rfcdiff?url2=draft-ietf-core-oscore-key-update-02 Internet-Drafts are also available by rsync at rsync.ietf.org::internet-drafts
- [core] I-D Action: draft-ietf-core-oscore-key-upd… internet-drafts