RE: wrt all those "FIDO" terms, e.g. "FIDO Credentials" - new names?

I’m getting a little worried that we are now in meaningless territory as “FIDO” had a specific meaning the “ScopedSignatureCredentails” can mean anything. The use of FIDO is just like the use of RSA here.

From: Richard Barnes [mailto:rbarnes@mozilla.com]
Sent: Wednesday, March 9, 2016 1:30 PM
To: Hodges, Jeff <jeff.hodges@paypal.com>
Cc: W3C WebAuthn WG <public-webauthn@w3.org>
Subject: Re: wrt all those "FIDO" terms, e.g. "FIDO Credentials" - new names?



On Wed, Mar 9, 2016 at 4:28 PM, Hodges, Jeff <jeff.hodges@paypal.com<mailto:jeff.hodges@paypal.com>> wrote:
On 3/9/16, 1:20 PM, "Richard Barnes" <rbarnes@mozilla.com<mailto:rbarnes@mozilla.com>> wrote:

"""
API Features in scope are: (1) Requesting generation of an asymmetric key pair within a specific scope (e.g., an origin); (2) Proving that the browser has possession of a specific private key, where the proof can only be done within the scope of the key pair. In other words, authentication should obey the same origin policy.
"""
So this is a credential that provides authentication based on proof of possession of a signing key (i.e., a signature), where that signature is limited to some scope via the signing protocol we will define.
Could people live with "ScopedSignatureCredential"?

so you are suggesting..

enum CredentialType {

    "ScopedSignatureCredential"

};

.. yes?
Precisely.


sure, I can live with that.

=JeffH