Sorry about the notes left at the bottom.
Enviado desde mi iPhone
> El 31 oct 2018, a las 10:01, Dan García Carrillo escribió:
>
> Hi Tuomas,
>
> This is an interesting work.
>
> We have been investigating how to send EAP over the CoAP protocol
> specifically thinking of IoT devices
> (htt
-NOOB implementation in Contiki?
Thank you in advance.
Best Regards.
Dan and Rafa.
--
Firma Correo
=
*Dan Garcia Carrillo, Ph.D.
Doctorado Industrial (MINECO)
E-mail: dgar...@odins.es
***
Odin Solutions, S.L
Dear all,
I support the adoption of this document.
This is interesting work because it takes the process of deployment a
step further and makes it easier by allowing bootstrapping of devices
that don't have any credentials programmed into them.
Furthermore, there are current efforts to widen
Dear EMU,
We have submitted a draft with an idea about an EAP-EDHOC method.
There is still work to do.
https://datatracker.ietf.org/doc/draft-ingles-eap-edhoc/
Any comments are welcome.
Best Regards,
Dan.
___
Emu mailing list
Emu@ietf.org
https://
Hello all,
I have read the draft and I think it is useful tool to have within the
EAP framework. I support its publication.
Regards,
Dan
El 03/12/2020 a las 9:22, Aleksi Peltonen escribió:
I think the draft is ready. I was involved in the formal modeling of
the protocol with both ProVerif
_
From: Ace mailto:ace-boun...@ietf.org>> on
behalf of Dan Garcia mailto:dan.gar...@um.es>>
Sent: Thursday, December 3, 2020 6:10 AM
To: a...@ietf.org <mailto:a...@ietf.org> <mailto:a...@ietf.org>>
Subject: [Ace] Proposed charter for ACE (EAP over CoA
Hi Michael,
EAP can be used in the context of IoT for authentication. To transport
EAP from the IoT device we need a light EAP lower-layer. This would be
CoAP. Morover, according to EAP key management framework, keys are
exported to protect the link and the EAP lower-layer itself. So yes,
OS
evere
constrains in the network or any other reason?
That is why I believe the flexibility EAP gives you is worth considering.
Best Regards,
Dan.
On 9/12/20 19:55, Michael Richardson wrote:
Dan Garcia wrote:
> EAP can be used in the context of IoT for authentication.
But, to
Vučinić escribió:
Hi Dan,
Could you be more specific on the point below, what deficiencies do
you have in mind?
Mališa
*From: *core on behalf of Dan Garcia
*Date: *Thursday 10 December 2020 at 10:06
*To: *Michael Richardson , EMU WG
, "c...@ietf.org WG (c...@ietf.org)" ,
&quo
-marin-ace-wg-coap-eap-06
spans 3 pages and consumes 2 round trips just to get things started!
Surely, we can do better?
Yes, we will submit an updated version of the draft.
Best Regards,
Dan
Mališa
*From: *Dan Garcia Carrillo
*Date: *Friday 11 December 2020 at 18:41
*To: *Mališa Vučinić
Dear EMU WG members,
We thought this document may be of interest to the working group.
https://datatracker.ietf.org/doc/html/draft-ietf-ace-wg-coap-eap-03
"CoAP-EAP" defines an EAP lower layer based on CoAP.
We would appreciate feedback or reviews on it.
Thank you,
Best Regards.
___
Dear ACE and EMU WG members,
In the last exchange of CoAP-EAP we intended to run OSCORE to achieve
key confirmation, a protected EAP success and the establishment of the
OSCORE security association. It was our understanding that only
integrity protection was possible but it is not the case aft
Dear Christian,
Thank you for your detailed review. You are raising indeed very
interesting points.
Just came back from vacation and we will respond as soon as possible.
Best Regards.
On 16/8/21 16:40, Christian Amsüss wrote:
Hello CoAP-EAP authors and involved groups,
(CC'ing core@ as this
Dear Christian,
Thank you very much for your detailed revision,
Please see inline our comments.
On 16/8/21 16:40, Christian Amsüss wrote:
Hello CoAP-EAP authors and involved groups,
(CC'ing core@ as this is a review on CoAP usage),
I've read the -03 draft and accumulated a few comments; l
I-D, draft-ietf-ace-wg-coap-eap-04.txt
has been successfully submitted by Dan Garcia-Carrillo and posted to the
IETF repository.
Name: draft-ietf-ace-wg-coap-eap
Revision: 04
Title: EAP-based Authentication Service for CoAP
Document date: 2021-10-25
Group: ace
and EAP peer cannot be verified.
For example, a man-in-the-middle could replace cipher suites in
either message which would not be noticed if the protocol is ended
after step 2.
Best regards
Göran
*From: *Ace on behalf of John Mattsson
*Date: *Monday, 25 October
ipher suite, the exchange of cipher suites
between EAP authenticator and EAP peer cannot be verified. For
example, a man-in-the-middle could replace cipher suites in either
message which would not be noticed if the protocol is ended after step 2.
Best regards
Göran
*From: *Ace on behalf of
is limitation should be
clearly stated.
- Probably good if the labels have “CoAP-EAP” in all the labels to
guarantee that they do not collide with anything else.
Cheers,
John
*From: *Emu on behalf of Dan Garcia Carrillo
*Date: *Monday, 25 October 2021 at 13:27
*To: *a...@ietf.org , EMU W
uthors] We agree. that this consideration applies. We will add that to
the DTLS annex.
- Probably good if the labels have “CoAP-EAP” in all the labels to
guarantee that they do not collide with anything else.
[authors] Thank you for this point. We will apply this change when using
label
ation will follow until the end cipher suite negotiation can be
verified. We think it is simpler and we can get rid of a bad request.
Does it sound reasonable?
Best regards
Göran
*From: *Ace on behalf of John Mattsson
*Date: *Monday, 25 October 2021 at 17:03
*To: *Dan Garcia Carrillo , a..
-eap-05.txt
has been successfully submitted by Dan Garcia-Carrillo and posted to the
IETF repository.
Name: draft-ietf-ace-wg-coap-eap
Revision: 05
Title: EAP-based Authentication Service for CoAP
Document date: 2021-12-05
Group: ace
Pages: 31
URL
regards
Göran
*From: *Dan Garcia Carrillo
"The communication with the last resource (e.g. '/a/w') from this
point MUST be protected with OSCORE except during a new
(re)authentication (see Section 3.3)."
I don't understand why there is an exception. OSCOR
hoc-02.txt
has been successfully submitted by Dan Garcia-Carrillo and posted to the
IETF repository.
Name: draft-ingles-eap-edhoc
Revision: 02
Title: Using the Extensible Authentication Protocol with Ephemeral
Diffie-Hellman over COSE (EDHOC)
Document date: 2022-0
Hi Eliot,
Thank you very much for your time to review the document.
On 5/7/23 10:09, Eliot Lear via Datatracker wrote:
Reviewer: Eliot Lear
Review result: On the Right Track
This draft provides a means for EAP authentication via CoAP. This is
an evolution on top of EAPoL/EAP so as to not req
Hi Alan,
Thank you very much for your time to review the document and for the
clarifications.
On 5/7/23 15:36, Alan DeKok wrote:
On Jul 5, 2023, at 4:09 AM, Eliot Lear via Datatracker wrote:
3. The terminology is a problem. On the one hand, some people like
to use the terms "IoT Device"
Dear Heikki,
Thank you for your comments.
Please see some notes inline.
El 27/7/23 a las 16:07, Heikki Vatiainen escribió:
On Wed, 19 Jul 2023 at 11:45, Dan Garcia Carrillo
wrote:
On 5/7/23 15:36, Alan DeKok wrote:
> Given that the EAP packets can be forced to be no more t
Hi Hannes,
Thank you for your time to review the document.
Regarding your question, in the annex there are different use cases
about the usage of CoAP-EAP.
If you think there is some additional use case that should be
considered, please, let us know.
Best Regards.
El 13/10/23 a las 10:2
Authentication and Authorization for Constrained Environments
(ACE) WG of the IETF.
Title: EAP-based Authentication Service for CoAP
Authors: Rafa Marin-Lopez
Dan Garcia-Carrillo
Name:draft-ietf-ace-wg-coap-eap-09.txt
Pages: 38
Dates: 2023-10-23
Abstract
.
If I understand the write-up correctly, then you are defining a new
version of PANA. The main difference is that PANA uses UDP to carry EAP
and this document uses CoAP over UDP to carry EAP.
Do I understand the use cases correctly?
Ciao
Hannes
Am 16.10.2023 um 11:37 schrieb Dan Garcia
Dear Peter,
We would like to request time for EAP-EDHOC.
Thank you.
Dan.
El 7/10/24 a las 23:54, Peter Yee escribió:
Please let the chairs know if you have any agenda items for the EMU
session at IETF 121. As a reminder, EMU is shown in the preliminary agenda as
meeting on Tuesda
Dear Peter,
15 minutes would be fine I think.
Thank you
Best regards.
Dan
> El 15 oct 2024, a las 14:59, Peter Yee escribió:
>
> That would be great, Dan. How much time would you like?
>
>-Peter
>
> On 10/15/24, 2:51 PM, "Dan Garcia Carrillo&quo
Hi Marco,
Thank you very much for the review.
Please, see comments inline.
Best regards.
El 26/9/24 a las 13:51, Marco Tiloca escribió:
Hi all,
Please see below some comments about this document. Hope it helps!
Best,
/Marco
---
[General]
* The title can incl
Dear Francisco,
Thank you very much for the time to review the document and the
comments. We will integrate them in the next version of the draft.
Best regards.
El 2/12/24 a las 12:10, FRANCISCO LOPEZ GOMEZ escribió:
Hi all,
See below some comments about draft-ietf-emu-eap-edhoc-02. While
Dear Josh,
Thank you for confirming comment about ordering.
We will incorporate the changes in the next version of the draft.
Best regards.
El 2/12/24 a las 12:27, josh.howl...@gmail.com escribió:
Re the text about the EAP Session Identifier
* "In EAP, fragments that are lost or damaged in
Hi Alexander,
We will update the implementation and clarify the use of channel binding
in EAP-EDHOC in the next version of the draft.
Thank you.
Best regards,
Dan.
El 15/7/25 a las 7:37, Alexander Clouter escribió:
Hello,
On Mon, 14 Jul 2025, at 10:28, FRANCISCO LOPEZ GOMEZ wrote:
Our im
35 matches
Mail list logo
