[core] I-D Action: draft-ietf-core-oscore-id-update-00.txt
internet-drafts@ietf.org Tue, 05 March 2024 09:30 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 C0495C14F5E5; Tue, 5 Mar 2024 01:30:17 -0800 (PST)
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: 12.6.1
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: core@ietf.org
Message-ID: <170963101767.39905.8022632431938082008@ietfa.amsl.com>
Date: Tue, 05 Mar 2024 01:30:17 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/core/xUESwmag-LGmqI9JGvVXv3QKWSc>
Subject: [core] I-D Action: draft-ietf-core-oscore-id-update-00.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: Tue, 05 Mar 2024 09:30:18 -0000
Internet-Draft draft-ietf-core-oscore-id-update-00.txt is now available. It is a work item of the Constrained RESTful Environments (CORE) WG of the IETF. Title: Identifier Update for OSCORE Authors: Rikard Höglund Marco Tiloca Name: draft-ietf-core-oscore-id-update-00.txt Pages: 24 Dates: 2024-03-04 Abstract: Two peers that communicate with the CoAP protocol can use the Object Security for Constrained RESTful Environments (OSCORE) protocol to protect their message exchanges end-to-end. To this end, the two peers share an OSCORE Security Context and a number of related identifiers. In particular, each of the two peers stores a Sender ID that identifies its own Sender Context within the Security Context, and a Recipient ID that identifies the Recipient Context associated with the other peer within the same Security Context. These identifiers are sent in plaintext within OSCORE-protected messages. Hence, they can be used to correlate messages exchanged between peers and track those peers, with consequent privacy implications. This document defines an OSCORE ID update procedure that two peers can use to update their OSCORE identifiers. This procedure can be run stand- alone or seamlessly integrated in an execution of the Key Update for OSCORE (KUDOS) procedure. The IETF datatracker status page for this Internet-Draft is: https://datatracker.ietf.org/doc/draft-ietf-core-oscore-id-update/ There is also an HTML version available at: https://www.ietf.org/archive/id/draft-ietf-core-oscore-id-update-00.html Internet-Drafts are also available by rsync at: rsync.ietf.org::internet-drafts
- [core] I-D Action: draft-ietf-core-oscore-id-upda… internet-drafts