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 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
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
Hi Folks,
I realize this call coincided with the end of summer vacation for some. We
need some review of this document before we can move it forward. Can a few
people commit to reviewing?
Thanks,
Joe
On Tue, Aug 16, 2022 at 1:41 PM Joseph Salowey wrote:
> This is the working group last
I've done a re-review of the TEAP section and I think it would be good to
move forward, but I have one question below. The current plan for this
document is to resolve the issue and then submit the document (or revision
if necessary) to the IESG for publication. If you have concerns about
