Last Call: <draft-ietf-core-oscore-edhoc-09.txt> (Using EDHOC with CoAP and OSCORE) to Proposed Standard

The IESG <iesg-secretary@ietf.org> Mon, 23 October 2023 13:17 UTC

MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce <ietf-announce@ietf.org>
Subject: Last Call: <draft-ietf-core-oscore-edhoc-09.txt> (Using EDHOC with CoAP and OSCORE) to Proposed Standard
Auto-Submitted: auto-generated
Precedence: bulk
CC: cabo@tzi.org, core-chairs@ietf.org, core@ietf.org, draft-ietf-core-oscore-edhoc@ietf.org, paul.wouters@aiven.io
Reply-To: last-call@ietf.org
Sender: iesg-secretary@ietf.org
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
Message-ID: <169806702480.34140.7805690422541214894@ietfa.amsl.com>
Date: Mon, 23 Oct 2023 06:17:04 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-announce/Li2syOYKBSr_u-HocdiF4RKlCMM>

The IESG has received a request from the Constrained RESTful Environments WG
(core) to consider the following document: - 'Using EDHOC with CoAP and
OSCORE'
<draft-ietf-core-oscore-edhoc-09.txt> as Proposed Standard

The IESG plans to make a decision in the next few weeks, and solicits final
comments on this action. Please send substantive comments to the
last-call@ietf.org mailing lists by 2023-11-13. Exceptionally, comments may
be sent to iesg@ietf.org instead. In either case, please retain the beginning
of the Subject line to allow automated sorting.

Abstract

The lightweight authenticated key exchange protocol EDHOC can be run
over CoAP and used by two peers to establish an OSCORE Security
Context. This document details this use of the EDHOC protocol, by
specifying a number of additional and optional mechanisms. These
especially include 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.

The file can be obtained via
https://datatracker.ietf.org/doc/draft-ietf-core-oscore-edhoc/

No IPR declarations have been submitted directly on this I-D.

The document contains these normative downward references.
See RFC 3967 for additional information:
draft-ietf-core-target-attr: CoRE Target Attributes Registry (None - Internet Engineering Task Force (IETF))

Last Call: <draft-ietf-core-oscore-edhoc-09.txt> … The IESG