Last Call: <draft-ietf-ace-wg-coap-eap-10.txt> (EAP-based Authentication Service for CoAP) to Proposed Standard

The IESG <iesg-secretary@ietf.org> Thu, 05 September 2024 13:42 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-ace-wg-coap-eap-10.txt> (EAP-based Authentication Service for CoAP) to Proposed Standard
Auto-Submitted: auto-generated
Precedence: bulk
Sender: iesg-secretary@ietf.org
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
Message-ID: <172554375520.1890495.7074984909657513388@dt-datatracker-68b7b78cf9-q8rsp>
Date: Thu, 05 Sep 2024 06:42:35 -0700
Message-ID-Hash: CZNFFMMK5CMK7HIL2TKYSYHLHGAXRQYX
CC: ace-chairs@ietf.org, ace@ietf.org, draft-ietf-ace-wg-coap-eap@ietf.org, loganaden@gmail.com, paul.wouters@aiven.io
Reply-To: last-call@ietf.org
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-announce/kj4n-gd3SeDnNFwZMjAbD4B48EM>

The IESG has received a request from the Authentication and Authorization for
Constrained Environments WG (ace) to consider the following document: -
'EAP-based Authentication Service for CoAP'
  <draft-ietf-ace-wg-coap-eap-10.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 2024-09-19. 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


   This document specifies an authentication service that uses the
   Extensible Authentication Protocol (EAP) transported employing
   Constrained Application Protocol (CoAP) messages.  As such, it
   defines an EAP lower layer based on CoAP called CoAP-EAP.  One of the
   main goals is to authenticate a CoAP-enabled IoT device (EAP peer)
   that intends to join a security domain managed by a Controller (EAP
   authenticator).  Secondly, it allows deriving key material to protect
   CoAP messages exchanged between them based on Object Security for
   Constrained RESTful Environments (OSCORE), enabling the establishment
   of a security association between them.




The file can be obtained via
https://datatracker.ietf.org/doc/draft-ietf-ace-wg-coap-eap/



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

Last Call: <draft-ietf-ace-wg-coap-eap-10.txt> (E… The IESG