TAG review comments on eTLD+1 #58
Comments
vijaybh
added a commit
that referenced
this issue
May 7, 2016
Fixes #58 by adding verbiage in the API section about the two layers in the WebAuthn security model. This discussion is ongoing with the TAG, so we will open a new issue if there are follow-ups. Fixes #20, #21, #23 by removing mentions of native apps and APIs, as these are out of scope for this specification.
vijaybh
pushed a commit
that referenced
this issue
Jun 1, 2016
) * Clarify that RP ID is globally unique Fixes #38, #16. * Clarify that extensions are optional Fixes #74 * Clarify credential type Fixes #15 * Make method parameters consistent between API and authenticator model sections Fixes #30 * Clarify attestation model vs. attestation type Fixes #27, #28 * Use case: user can use WebAuthn credential when creating account, avoiding passwords entirely Fixes #10 * Clarify security model and remove vestiges of "native API" language Fixes #58 by adding verbiage in the API section about the two layers in the WebAuthn security model. This discussion is ongoing with the TAG, so we will open a new issue if there are follow-ups. Fixes #20, #21, #23 by removing mentions of native apps and APIs, as these are out of scope for this specification. * JsonWebKey is a dictionary not an interface Fixed sloppy terminology usage * Remove unnecessary ref WebCrypto is not a reference for byte arrays * abstract clarifications/polishing * abstract edits * polish abstract,intro,terminology sections, and move terminology to front of spec * publishing diff * remove Makefile dependency on biblio.json travis CI was failing... * address Vijay's comments * addresses Vijay's comments other than wrt credential definition * address vijay's comments #3 - minor tweaks * address vijay's comments #4 - fix bikeshed errors * fix UAF spec link * fix spelling and reference * refine 'scoped credential' definition
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
w3ctag/design-reviews#97
The text was updated successfully, but these errors were encountered: