- From: =JeffH via GitHub <sysbot+gh@w3.org>
- Date: Thu, 16 Mar 2017 16:59:57 +0000
- To: public-webauthn@w3.org
also...
in [[!FIDOEcdaaAlgorithm]], these terms..
DAA-Issuer
DAA-Verify
DAA-Sign
..are actually of the form "ECDAA-foo"
I suggest editing this parag from the {#attestation-formats} section..
>: <dfn>Direct Anonymous Attestation</dfn> (DAA)
:: In this case, the Authenticator receives DAA credentials from a single DAA-Issuer. These DAA credentials are used along with
blinding to sign the [=attestation data=]. The concept of blinding avoids the DAA credentials being misused as global
correlation handle. WebAuthn supports DAA using elliptic curve cryptography and bilinear pairings, called ECDAA (see
[[FIDOEcdaaAlgorithm]]) in this specification.
..to be..
: <dfn>Direct Anonymous Attestation</dfn> (DAA)
:: In this case, an Authenticator receives DAA credentials from a given DAA-Issuer. These DAA credentials are used along with blinding to sign the [=attestation data=]. The concept of blinding avoids the DAA credentials being misused as a global correlation handle. WebAuthn employs the DAA variant based on elliptic curve cryptography and bilinear pairings, known as <dfn>ECDAA</dfn>, the details of which are specified in [[FIDOEcdaaAlgorithm]]. See the latter specification for the detailed definitions of <dfn>ECDAA-Issuer</dfn>, as well as the <dfn>ECDAA-Verify</dfn> and <dfn>ECDAA-Sign</dfn> operations.
..and then have all subsequent occurrences of "DAA-foo" become "[=ECDAA-foo=]", as well as subsequent standalone occurrences of "DAA" become "[=ECDAA=]".
--
GitHub Notification of comment by equalsJeffH
Please view or discuss this issue at https://github.com/w3c/webauthn/pull/381#issuecomment-287123118 using your GitHub account
Received on Thursday, 16 March 2017 17:00:03 UTC