WG version.
Please incorporate the feedback garnered during the call for adoption.
Thanks,
Peter and Joe
-Original Message-
From: Emu On Behalf Of Peter Yee
Sent: Wednesday, September 07, 2022 9:58 PM
To: emu@ietf.org
Subject: Re: [Emu] Adoption call for EAP-DPP
In retrospect, sending
in the next draft too.
Inline for more.
-Original Message-
From: Emu On Behalf Of Michael Richardson
Sent: Tuesday 13 September 2022 12:13
To: Peter Yee ; emu@ietf.org
Subject: Re: [Emu] Adoption call for EAP-DPP
I have read draft-friel-tls-eap-dpp-05.
I have no objection to the WG
://mailarchive.ietf.org/arch/msg/emu/lboE_o4OfJJtUL_LA6psIpSuHZs/
Regards,
Owen
From: Emu On Behalf Of Dan Harkins
Sent: Friday 9 September 2022 07:29
To: sarik...@ieee.org
Cc: emu@ietf.org
Subject: Re: [Emu] Adoption call for EAP-DPP
Hi Behcet,
On 9/8/22 8:43 AM, Behcet Sarikaya wrote:
Hi Peter, Joe,
We
I have read draft-friel-tls-eap-dpp-05.
I have no objection to the WG working on such a thing, but I think that there
is actually quite a lot of work left to do.
I think that the section 3, which explains the EAP connection (and the
motivation for the work) should probably come before the
Hi Behcet,
On 9/8/22 8:43 AM, Behcet Sarikaya wrote:
Hi Peter, Joe,
We made it clear that DPP R2 has already been published with a name
change:
*Wi-Fi Easy Connect™*
*Specification*
*Version 2.0*
Wi-Fi Easy Connect is the new DPP, which the authors seemingly did not
know about.
Hi Behcet,
On 08.09.22 17:43, Behcet Sarikaya wrote:Hi Peter, Joe,
Also the problem that this draft deals with and also Elliott mentioned
in his mail, Wi-Fi Easy Connect already solves it.
DPP works with wired when L3 connectivity is pre-established. This is
covered in Section 2.3.5 in the
Hi Peter, Joe,
We made it clear that DPP R2 has already been published with a name change:
*Wi-Fi Easy Connect™ *
*Specification *
*Version 2.0 *
Wi-Fi Easy Connect is the new DPP, which the authors seemingly did not
know about.
Also the problem that this draft deals with and also
In favor of reviewing and adoption.
Some small editorial nits...
In section 1.2
The server may have knowledge of multiple BSK public keys
corresponding to multiple devices, and existing TLS mechanisms are
leveraged that enable the server to *identity* a specific bootstrap
public
Peter,
Let me clarify why I think it's important to adopt this work. The Wifi
Alliance has already standardized the public/private key pair as well as
other attributes that can be used to securely onboard a device. They
have also standardized the QR code used to represent this information.
In retrospect, sending the call for adoption at the height of August
vacation season may not have guaranteed the most responses. To be honest,
the level of responses to this call has been a little light, so Joe and I
have decided to extend the call for adoption for one week from today.
We would
On Fri, Aug 19, 2022 at 10:50 AM M Montemurro
wrote:
> Hi Behcet and Dan,
>
> There is a v2 of the DPP specification. The only difference is that Wi-Fi
> Alliance has a adopted the program name for the specification rather than
> DPP. So the reference would be Wi-Fi Easy Connect Specification
Hi Behcet,
On 8/19/22 8:22 AM, Behcet Sarikaya wrote:
Hi Dan,
On Thu, Aug 18, 2022 at 9:54 AM Dan Harkins wrote:
Hi Behcet,
On 8/17/22 2:36 PM, Behcet Sarikaya wrote:
Hi Peter,
I quickly read this short document and have some comments.
In the informative
Hi Behcet and Dan,
There is a v2 of the DPP specification. The only difference is that Wi-Fi
Alliance has a adopted the program name for the specification rather than
DPP. So the reference would be Wi-Fi Easy Connect Specification v2.0.
You can find the document here:
Hi Dan,
On Thu, Aug 18, 2022 at 9:54 AM Dan Harkins wrote:
>
> Hi Behcet,
>
> On 8/17/22 2:36 PM, Behcet Sarikaya wrote:
>
> Hi Peter,
>
> I quickly read this short document and have some comments.
>
> In the informative references section, DPP is listed as Device
> Provisioning Profile
Hi Behcet,
On 8/17/22 2:36 PM, Behcet Sarikaya wrote:
Hi Peter,
I quickly read this short document and have some comments.
In the informative references section, DPP is listed as Device
Provisioning Profile while it should be Device Provisioning Protocol.
Actually, in the acronyms section
I agree with Behcet's comments, but otherwise support the work's adoption.
Eliot
On 17.08.22 23:36, Behcet Sarikaya wrote:
Hi Peter,
I quickly read this short document and have some comments.
In the informative references section, DPP is listed as Device
Provisioning Profile while it should
Hi Peter,
I quickly read this short document and have some comments.
In the informative references section, DPP is listed as Device Provisioning
Profile while it should be Device Provisioning Protocol.
Actually, in the acronyms section the name is correctly given. However, the
DPP acronym is not
Hi Peter,
Thanks. I reviewed the document and I believe EAP-DPP is an appropriate
working group item for EMU.
Cheers,
Mike
On Tue, Aug 16, 2022 at 4:12 PM Peter Yee wrote:
> This is an adoption call for EAP-DPP (draft-friel-tls-eap-dpp-05)[1]. This
> document aligns with the charter item to
This is an adoption call for EAP-DPP (draft-friel-tls-eap-dpp-05)[1]. This
document aligns with the charter item to "Define mechanisms by which EAP
methods can support creation of long-term credentials for the peer based on
initial limited-use credentials." The latest revision incorporates
19 matches
Mail list logo
