[core] RFC 9668 on Using Ephemeral Diffie-Hellman Over COSE (EDHOC) with the Constrained Application Protocol (CoAP) and Object Security for Constrained RESTful Environments (OSCORE)
rfc-editor@rfc-editor.org Mon, 18 November 2024 22:45 UTC
Return-Path: <wwwrun@rfcpa.rfc-editor.org>
X-Original-To: core@ietf.org
Delivered-To: core@ietfa.amsl.com
Received: from rfcpa.rfc-editor.org (unknown [167.172.21.234]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (P-256) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5FC60C14F6BE; Mon, 18 Nov 2024 14:45:40 -0800 (PST)
Received: by rfcpa.rfc-editor.org (Postfix, from userid 461) id C5B6D7FA6A; Mon, 18 Nov 2024 14:45:39 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
From: rfc-editor@rfc-editor.org
Content-type: text/plain; charset="UTF-8"
Message-Id: <20241118224539.C5B6D7FA6A@rfcpa.rfc-editor.org>
Date: Mon, 18 Nov 2024 14:45:39 -0800
Message-ID-Hash: T5U3MUARBPK2GB2BQZESP2TWJVD5ZQ2T
X-Message-ID-Hash: T5U3MUARBPK2GB2BQZESP2TWJVD5ZQ2T
X-MailFrom: wwwrun@rfcpa.rfc-editor.org
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-core.ietf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
CC: rfc-editor@rfc-editor.org, drafts-update-ref@iana.org, core@ietf.org
X-Mailman-Version: 3.3.9rc6
Precedence: list
Subject: [core] RFC 9668 on Using Ephemeral Diffie-Hellman Over COSE (EDHOC) with the Constrained Application Protocol (CoAP) and Object Security for Constrained RESTful Environments (OSCORE)
List-Id: "Constrained RESTful Environments (CoRE) Working Group list" <core.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/core/DNNH8ie3Fz_MQFyLkcxSpLOY12w>
List-Archive: <https://mailarchive.ietf.org/arch/browse/core>
List-Help: <mailto:core-request@ietf.org?subject=help>
List-Owner: <mailto:core-owner@ietf.org>
List-Post: <mailto:core@ietf.org>
List-Subscribe: <mailto:core-join@ietf.org>
List-Unsubscribe: <mailto:core-leave@ietf.org>
A new Request for Comments is now available in online RFC libraries. RFC 9668 Title: Using Ephemeral Diffie-Hellman Over COSE (EDHOC) with the Constrained Application Protocol (CoAP) and Object Security for Constrained RESTful Environments (OSCORE) Author: F. Palombini, M. Tiloca, R. Höglund, S. Hristozov, G. Selander Status: Standards Track Stream: IETF Date: November 2024 Mailbox: francesca.palombini@ericsson.com, marco.tiloca@ri.se, rikard.hoglund@ri.se, stefan.hristozov@eriptic.com, goran.selander@ericsson.com Pages: 23 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-core-oscore-edhoc-11.txt URL: https://www.rfc-editor.org/info/rfc9668 DOI: 10.17487/RFC9668 The lightweight authenticated key exchange protocol Ephemeral Diffie-Hellman Over COSE (EDHOC) can be run over the Constrained Application Protocol (CoAP) and used by two peers to establish a Security Context for the security protocol Object Security for Constrained RESTful Environments (OSCORE). This document details this use of the EDHOC protocol by specifying a number of additional and optional mechanisms, including an optimization approach for combining the execution of EDHOC with the first OSCORE transaction. This combination reduces the number of round trips required to set up an OSCORE Security Context and to complete an OSCORE transaction using that Security Context. This document is a product of the Constrained RESTful Environments Working Group of the IETF. This is now a Proposed Standard. STANDARDS TRACK: This document specifies an Internet Standards Track protocol for the Internet community, and requests discussion and suggestions for improvements. Please refer to the current edition of the Official Internet Protocol Standards (https://www.rfc-editor.org/standards) for the standardization state and status of this protocol. Distribution of this memo is unlimited. This announcement is sent to the IETF-Announce and rfc-dist lists. To subscribe or unsubscribe, see https://www.ietf.org/mailman/listinfo/ietf-announce https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist For searching the RFC series, see https://www.rfc-editor.org/search For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk Requests for special distribution should be addressed to either the author of the RFC in question, or to rfc-editor@rfc-editor.org. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution. The RFC Editor Team Association Management Solutions, LLC