W3C home > Mailing lists > Public > public-webauthn@w3.org > February 2020

[webauthn] Addition of a network transport (#1381)

From: Nick Mooney via GitHub <sysbot+gh@w3.org>
Date: Sat, 29 Feb 2020 00:43:34 +0000
To: public-webauthn@w3.org
Message-ID: <issues.opened-573084133-1582937012-sysbot+gh@w3.org>
nickmooney has just created a new issue for https://github.com/w3c/webauthn:

== Addition of a network transport ==
This issue is to track progress on the addition of a network transport, which is mostly happening in FIDO world. Here is a summary of progress so far:

* @arnar, @nicksteele and I discussed the issue at the FIDO plenary in Lisbon
* Google participants are amenable to the addition of a network transport for after-pairing communication, provided that the initial client/authenticator pairing takes place over a channel that ensures proximity

Our current plan is to submit a PR on top of the caBLE v2 PR, fido-alliance/fido-2-specs#724. Since this PR will be on top of Google's branch, we'll also open an issue on the FIDO2 specs repo.

We are currently hammering out some details of how communication will actually happen via the network transport. We are leaning toward, but not settled on, sticking with the caBLE model of a channel established via Noise handshake that then passes CTAP2 messages.

We hope to have a PR submitted in the next month or so, and will certainly be ready to discuss the transport ahead of the member plenary colocated with the FIDO Authenticate conference.

Please let me know if you have any questions!

Please view or discuss this issue at https://github.com/w3c/webauthn/issues/1381 using your GitHub account
Received on Saturday, 29 February 2020 00:43:36 UTC

This archive was generated by hypermail 2.4.0 : Tuesday, 5 July 2022 07:26:39 UTC