[Lake] Re: WG Last Call: draft-ietf-lake-authz-08 (Ends 2026-09-22)

[GABRIEL LOPEZ MILLAN <[e-mail]>]

Hi.

I support the adoption of this document.

Just a minor suggestion in case do you it may help.

Section 1:

"ELA enables a low message count by performing authorization and
   enrollment in parallel with authentication" --> this sentence is misleading, better something like "ELA enables a low message count by performing authorization in parallel with authentication during an enrollment process”. Does it make sense?


Best regards, Gabi.



De: Renzo Navas via Datatracker <[e-mail]>
Fecha: martes, 8 de septiembre de 2026 a las 18:58
Para: [e-mail] <[e-mail]>; [e-mail] <[e-mail]>; [e-mail] <[e-mail]>
Asunto: [Lake] WG Last Call: draft-ietf-lake-authz-08 (Ends 2026-09-22)

Dear All,

This message starts a WG Last Call for: draft-ietf-lake-authz-08
as we decided at IETF 126 [0]

This Working Group Last Call ends on 2026-09-22

Abstract:
   Ephemeral Diffie-Hellman Over COSE (EDHOC) is a lightweight
   authenticated key exchange protocol intended for use in constrained
   scenarios.  This document specifies Lightweight Authorization using
   EDHOC (ELA).  The procedure allows authorizing enrollment of new
   devices using the extension point defined in EDHOC.  ELA is
   applicable to zero-touch onboarding of new devices to a constrained
   network leveraging trust anchors installed at manufacture time.

File can be retrieved from:
https://urldefense.com/v3/__https://www.ietf.org/archive/id/draft-ietf-lake-authz-08.txt__;!!D9dNQwwGXtA!U3_P8Qj1WSS5yxByX2U4HBhNmfdSy3P07RYIK0Vvw0fMel67Iscv6-GeqbouVrJoD-XJ7Q2n5mI$

Please review and indicate your support or objection to proceed with the
publication of this document by replying to this email keeping [e-mail]
in copy. Objections should be explained and suggestions to resolve them are
highly appreciated.

Authors, and WG participants in general, are reminded of the Intellectual
Property Rights (IPR) disclosure obligations described in BCP 79 [1].
Appropriate IPR disclosures required for full conformance with the provisions
of BCP 78 [1] and BCP 79 [2] must be filed, if you are aware of any.
Sanctions available for application to violators of IETF IPR Policy can be
found at [3].

Thank you.
Renzo, for the LAKE hairs

[0] https://urldefense.com/v3/__https://datatracker.ietf.org/doc/minutes-126-lake-202607201430/__;!!D9dNQwwGXtA!U3_P8Qj1WSS5yxByX2U4HBhNmfdSy3P07RYIK0Vvw0fMel67Iscv6-GeqbouVrJoD-XJK7RJ2Ic$ ]
[1] https://urldefense.com/v3/__https://datatracker.ietf.org/doc/bcp78/__;!!D9dNQwwGXtA!U3_P8Qj1WSS5yxByX2U4HBhNmfdSy3P07RYIK0Vvw0fMel67Iscv6-GeqbouVrJoD-XJ6AQwDVk$
[2] https://urldefense.com/v3/__https://datatracker.ietf.org/doc/bcp79/__;!!D9dNQwwGXtA!U3_P8Qj1WSS5yxByX2U4HBhNmfdSy3P07RYIK0Vvw0fMel67Iscv6-GeqbouVrJoD-XJNln13JI$
[3] https://urldefense.com/v3/__https://datatracker.ietf.org/doc/rfc6701/__;!!D9dNQwwGXtA!U3_P8Qj1WSS5yxByX2U4HBhNmfdSy3P07RYIK0Vvw0fMel67Iscv6-GeqbouVrJoD-XJzYjU-_E$

The IETF datatracker status page for this Internet-Draft is:
https://urldefense.com/v3/__https://datatracker.ietf.org/doc/draft-ietf-lake-authz/__;!!D9dNQwwGXtA!U3_P8Qj1WSS5yxByX2U4HBhNmfdSy3P07RYIK0Vvw0fMel67Iscv6-GeqbouVrJoD-XJU4bi7WY$

There is also an HTML version available at:
https://urldefense.com/v3/__https://www.ietf.org/archive/id/draft-ietf-lake-authz-08.html__;!!D9dNQwwGXtA!U3_P8Qj1WSS5yxByX2U4HBhNmfdSy3P07RYIK0Vvw0fMel67Iscv6-GeqbouVrJoD-XJzG65EVE$

A diff from the previous version is available at:
https://urldefense.com/v3/__https://author-tools.ietf.org/iddiff?url2=draft-ietf-lake-authz-08__;!!D9dNQwwGXtA!U3_P8Qj1WSS5yxByX2U4HBhNmfdSy3P07RYIK0Vvw0fMel67Iscv6-GeqbouVrJoD-XJy_sj_P0$

--
Lake mailing list -- [e-mail]
To unsubscribe send an email to [e-mail]