<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet type="text/xsl" href="webauthn.xsl"?>
<?xml-model href="webauthn.rng" schematypens="http://relaxng.org/ns/structure/1.0" ?>
<registry xmlns="http://www.iana.org/assignments" id="webauthn">
  <title>Web Authentication (WebAuthn)</title>
  <created>2020-06-11</created>
  <updated>2023-09-13</updated>

  <registry id="webauthn-attestation-statement-format-ids">
    <title>WebAuthn Attestation Statement Format Identifiers</title>
    <registration_rule>Specification Required</registration_rule>
    <expert>Mike Jones, Giridhar Mandyam</expert>
    <xref type="rfc" data="rfc8809"/>
    <record date="2020-06-11" updated="2022-04-07">
      <value>packed</value>
      <description>The "packed" attestation statement format is a 
        WebAuthn-optimized format for attestation. It uses a very 
        compact but still extensible encoding method. This format 
        is implementable by authenticators with limited resources 
        (e.g., secure elements).</description>
      <spec><xref type="uri" data="https://www.w3.org/TR/webauthn-2/">Web Authentication</xref> 
        Section §8.2, Packed Attestation Statement Format</spec>
      <controller><xref type="person" data="W3C_Web_Authentication_Working_Group"/></controller>
      <notes/>
    </record>
    <record date="2020-06-11" updated="2022-04-07">
      <value>tpm</value>
      <description>The TPM attestation statement format returns 
        an attestation statement in the same format as the packed 
        attestation statement format, although the rawData and 
        signature fields are computed differently.</description>
      <spec><xref type="uri" data="https://www.w3.org/TR/webauthn-2/">Web Authentication</xref> 
        Section §8.3, TPM Attestation Statement Format</spec>
      <controller><xref type="person" data="W3C_Web_Authentication_Working_Group"/></controller>
      <notes/>
    </record>
    <record date="2020-06-11" updated="2022-04-07">
      <value>android-key</value>
      <description>Platform authenticators on versions "N", 
        and later, may provide this proprietary "hardware 
        attestation" statement.</description>
      <spec><xref type="uri" data="https://www.w3.org/TR/webauthn-2/">Web Authentication</xref> 
        Section §8.4, Android Key Attestation Statement Format</spec>
      <controller><xref type="person" data="W3C_Web_Authentication_Working_Group"/></controller>
      <notes/>
    </record>
    <record date="2020-06-11" updated="2022-04-07">
      <value>android-safetynet</value>
      <description>Android-based platform authenticators 
        MAY produce an attestation statement based on the 
        Android SafetyNet API.</description>
      <spec><xref type="uri" data="https://www.w3.org/TR/webauthn-2/">Web Authentication</xref> 
        Section §8.5, Android SafetyNet Attestation Statement Format</spec>
      <controller><xref type="person" data="W3C_Web_Authentication_Working_Group"/></controller>
      <notes/>
    </record>
    <record date="2020-06-11" updated="2022-04-07">
      <value>fido-u2f</value>
      <description>Used with FIDO U2F authenticators</description>
      <spec><xref type="uri" data="https://www.w3.org/TR/webauthn-2/">Web Authentication</xref> 
        Section §8.6, FIDO U2F Attestation Statement Format</spec>
      <controller><xref type="person" data="W3C_Web_Authentication_Working_Group"/></controller>
      <notes/>
    </record>
    <record date="2022-04-07">
      <value>apple</value>
      <description>Used with Apple devices' platform authenticators</description>
      <spec><xref type="uri" data="https://www.w3.org/TR/webauthn-2/">Web Authentication</xref> 
        Section §8.8, Apple Anonymous Attestation Statement Format</spec>
      <controller><xref type="person" data="W3C_Web_Authentication_Working_Group"/></controller>
      <notes/>
    </record>
    <record date="2022-04-07">
      <value>none</value>
      <description>Used to replace any authenticator-provided 
        attestation statement when a WebAuthn Relying Party 
        indicates it does not wish to receive attestation 
        information.</description>
      <spec><xref type="uri" data="https://www.w3.org/TR/webauthn-2/">Web Authentication</xref> 
        Section §8.7, None Attestation Statement Format</spec>
      <controller><xref type="person" data="W3C_Web_Authentication_Working_Group"/></controller>
      <notes/>
    </record>
  </registry>
  
  <registry id="webauthn-extension-ids">
    <title>WebAuthn Extension Identifiers</title>
    <registration_rule>Specification Required</registration_rule>
    <expert>Mike Jones, Giridhar Mandyam</expert>
    <xref type="rfc" data="rfc8809"/>  
    <record date="2020-06-11" updated="2022-04-07">
      <value>appid</value>
      <description>This authentication extension allows WebAuthn 
        Relying Parties that have previously registered a credential 
        using the legacy FIDO JavaScript APIs to request an assertion.</description>
      <spec><xref type="uri" data="https://www.w3.org/TR/webauthn-2/">Web Authentication</xref> 
        Section §10.1, FIDO AppID Extension (appid)</spec>
      <controller><xref type="person" data="W3C_Web_Authentication_Working_Group"/></controller>
      <notes/>
    </record>
    <record date="2020-06-11">
      <value>txAuthSimple</value>
      <description>This registration extension and authentication 
        extension allows for a simple form of transaction authorization. 
        A WebAuthn Relying Party can specify a prompt string, intended 
        for display on a trusted device on the authenticator</description>
      <spec><xref type="uri" data="https://www.w3.org/TR/2019/REC-webauthn-1-20190304/">Web Authentication</xref> 
        Section §10.2, Simple Transaction Authorization Extension (txAuthSimple)</spec>
      <controller><xref type="person" data="W3C_Web_Authentication_Working_Group"/></controller>
      <notes/>
    </record>
    <record date="2020-06-11">
      <value>txAuthGeneric</value>
      <description>This registration extension and authentication 
        extension allows images to be used as transaction 
        authorization prompts as well. This allows authenticators 
        without a font rendering engine to be used and also 
        supports a richer visual appearance than accomplished with 
        the webauthn.txauth.simple extension.</description>
      <spec><xref type="uri" data="https://www.w3.org/TR/2019/REC-webauthn-1-20190304/">Web Authentication</xref> 
        Section §10.3, Generic Transaction Authorization Extension (txAuthGeneric)</spec>
      <controller><xref type="person" data="W3C_Web_Authentication_Working_Group"/></controller>
      <notes/>
    </record>
    <record date="2020-06-11">
      <value>authnSel</value>
      <description>This registration extension allows a WebAuthn 
        Relying Party to guide the selection of the authenticator 
        that will be leveraged when creating the credential. It is 
        intended primarily for WebAuthn Relying Parties that wish to 
        tightly control the experience around credential creation.</description>
      <spec><xref type="uri" data="https://www.w3.org/TR/2019/REC-webauthn-1-20190304/">Web Authentication</xref> 
        Section §10.4, Authenticator Selection Extension (authnSel)</spec>
      <controller><xref type="person" data="W3C_Web_Authentication_Working_Group"/></controller>
      <notes/>
    </record>
    <record date="2020-06-11">
      <value>exts</value>
      <description>This registration extension enables the WebAuthn 
        Relying Party to determine which extensions the authenticator 
        supports. The extension data is a list (CBOR array) of 
        extension identifiers encoded as UTF-8 Strings. This extension 
        is added automatically by the authenticator. This extension 
        can be added to attestation statements.</description>
      <spec><xref type="uri" data="https://www.w3.org/TR/2019/REC-webauthn-1-20190304/">Web Authentication</xref> 
        Section §10.5, Supported Extensions Extension (exts)</spec>
      <controller><xref type="person" data="W3C_Web_Authentication_Working_Group"/></controller>
      <notes/>
    </record>
    <record date="2020-06-11">
      <value>uvi</value>
      <description>This registration extension and authentication 
        extension enables use of a user verification index. The 
        user verification index is a value uniquely identifying a 
        user verification data record. The UVI data can be used by 
        servers to understand whether an authentication was 
        authorized by the exact same biometric data as the initial 
        key generation. This allows the detection and prevention of 
        "friendly fraud".</description>
      <spec><xref type="uri" data="https://www.w3.org/TR/2019/REC-webauthn-1-20190304/">Web Authentication</xref> 
        Section §10.6, User Verification Index Extension (uvi)</spec>
      <controller><xref type="person" data="W3C_Web_Authentication_Working_Group"/></controller>
      <notes/>
    </record>
    <record date="2020-06-11">
      <value>loc</value>
      <description>The location registration extension and 
        authentication extension provides the client device's 
        current location to the WebAuthn Relying Party, if 
        supported by the client platform and subject to user 
        consent.</description>
      <spec><xref type="uri" data="https://www.w3.org/TR/2019/REC-webauthn-1-20190304/">Web Authentication</xref> 
        Section §10.7, Location Extension (loc)</spec>
      <controller><xref type="person" data="W3C_Web_Authentication_Working_Group"/></controller>
      <notes/>
    </record>
    <record date="2020-06-11" updated="2022-04-07">
      <value>uvm</value>
      <description>This registration extension and authentication 
        extension enables use of a user verification method. The 
        user verification method extension returns to the WebAuthn 
        Relying Party which user verification methods (factors) 
        were used for the WebAuthn operation.</description>
      <spec><xref type="uri" data="https://www.w3.org/TR/webauthn-2/">Web Authentication</xref> 
        Section §10.3, User Verification Method Extension (uvm)</spec>
      <controller><xref type="person" data="W3C_Web_Authentication_Working_Group"/></controller>
      <notes/>
    </record>
    <record date="2022-02-28">
      <value>credProtect</value>
      <description>This registration extension allows relying 
        parties to specify a credential protection policy when 
        creating a credential. Additionally, authenticators may 
        choose to establish a default credential protection 
        policy greater than userVerificationOptional 
        (the lowest level) and unilaterally enforce such policy.</description>
      <spec><xref type="uri" data="https://fidoalliance.org/specs/fido-v2.1-ps-20210615/fido-client-to-authenticator-protocol-v2.1-ps-20210615.html">Client to Authenticator Protocol (CTAP)</xref> 
        Section §12.1 Credential Protection (credProtect)</spec>
      <controller><xref type="person" data="W3C_Web_Authentication_Working_Group"/></controller>
      <notes/>
    </record>
    <record date="2022-02-28">
      <value>credBlob</value>
      <description>This registration extension and authentication 
        extension enables RPs to provide a small amount of extra 
        credential configuration information (the credBlob value) 
        to the authenticator when a credential is made.</description>
      <spec><xref type="uri" data="https://fidoalliance.org/specs/fido-v2.1-ps-20210615/fido-client-to-authenticator-protocol-v2.1-ps-20210615.html">Client to Authenticator Protocol (CTAP)</xref> 
        Section §12.2 Credential Blob (credBlob)</spec>
      <controller><xref type="person" data="W3C_Web_Authentication_Working_Group"/></controller>
      <notes/>
    </record>
    <record date="2022-02-28">
      <value>largeBlobKey</value>
      <description>This client platform-only extension provides 
        for storage and retrieval of a per-credential key that 
        is used by the client platform when writing and reading 
        elements in the large-blob array.</description>
      <spec><xref type="uri" data="https://fidoalliance.org/specs/fido-v2.1-ps-20210615/fido-client-to-authenticator-protocol-v2.1-ps-20210615.html">Client to Authenticator Protocol (CTAP)</xref> 
        Section §12.3 Large Blob Key (largeBlobKey)</spec>
      <controller><xref type="person" data="W3C_Web_Authentication_Working_Group"/></controller>
      <notes/>
    </record>
    <record date="2022-02-28">
      <value>minPinLength</value>
      <description>This registration extension returns the current 
        minimum PIN length value to the Relying Party.</description>
      <spec><xref type="uri" data="https://fidoalliance.org/specs/fido-v2.1-ps-20210615/fido-client-to-authenticator-protocol-v2.1-ps-20210615.html">Client to Authenticator Protocol (CTAP)</xref> 
        Section §12.4 Minimum PIN Length Extension (minPinLength)</spec>
      <controller><xref type="person" data="W3C_Web_Authentication_Working_Group"/></controller>
      <notes/>
    </record>
    <record date="2022-02-28">
      <value>hmac-secret</value>
      <description>This registration extension and authentication
         extension enables the platform to retrieve a symmetric 
         secret scoped to the credential from the authenticator.</description>
      <spec><xref type="uri" data="https://fidoalliance.org/specs/fido-v2.1-ps-20210615/fido-client-to-authenticator-protocol-v2.1-ps-20210615.html">Client to Authenticator Protocol (CTAP)</xref> 
        Section §12.5 HMAC Secret Extension (hmac-secret)</spec>
      <controller><xref type="person" data="W3C_Web_Authentication_Working_Group"/></controller>
      <notes/>
    </record>
    <record date="2022-04-07">
      <value>appidExclude</value>
      <description>This registration extension allows WebAuthn 
        Relying Parties to exclude authenticators that contain 
        specified credentials that were created with the legacy 
        FIDO U2F JavaScript API [FIDOU2FJavaScriptAPI].</description>
      <spec><xref type="uri" data="https://www.w3.org/TR/webauthn-2/">Web Authentication</xref> 
        Section §10.2, FIDO AppID Exclusion Extension (appidExclude)</spec>
      <controller><xref type="person" data="W3C_Web_Authentication_Working_Group"/></controller>
      <notes/>
    </record>
    <record date="2022-04-07">
      <value>credProps</value>
      <description>This client registration extension enables 
        reporting of a newly-created credential's properties, 
        as determined by the client, to the calling WebAuthn 
        Relying Party's web application.</description>
      <spec><xref type="uri" data="https://www.w3.org/TR/webauthn-2/">Web Authentication</xref> 
        Section §10.4, Credential Properties Extension (credProps)</spec>
      <controller><xref type="person" data="W3C_Web_Authentication_Working_Group"/></controller>
      <notes/>
    </record>
    <record date="2022-04-07">
      <value>largeBlob</value>
      <description>This client registration extension and 
        authentication extension allows a Relying Party to 
        store opaque data associated with a credential.</description>
      <spec><xref type="uri" data="https://www.w3.org/TR/webauthn-2/">Web Authentication</xref> 
        Section §10.5, Large blob storage extension (largeBlob)</spec>
      <controller><xref type="person" data="W3C_Web_Authentication_Working_Group"/></controller>
      <notes/>
    </record>
    <record date="2023-09-13">
      <value>payment</value>
      <description>This extension supports the following 
        functionality defined by the Secure Payment Confirmation API: 
        (1) it allows credential creation in a cross-origin iframe 
        (2) it allows a party other than the Relying Party to use 
        the credential to perform an authentication ceremony on 
        behalf of the Relying Party, and (3) it allows the browser 
        to identify and cache Secure Payment Confirmation credentials. 
        For discussion of important ways in which SPC differs from 
        Web Authentication, see in particular 
        <xref type="uri" data="https://w3c.github.io/secure-payment-confirmation/#sctn-security-considerations">Secure Payment Confirmation §10 Security Considerations</xref> and <xref type="uri" data="https://w3c.github.io/secure-payment-confirmation/#sctn-privacy-considerations">Secure Payment Confirmation §11 Privacy Considerations</xref>.
      </description>
      <spec><xref type="uri" data="https://w3c.github.io/secure-payment-confirmation/">Secure Payment Confirmation</xref> 
        Section §5, WebAuthn Extension - "payment"</spec>
      <controller><xref type="person" data="W3C_Web_Payments_Working_Group"/></controller>
      <notes/>
    </record>
  </registry>
  
  <people>
    <person id="W3C_Web_Authentication_Working_Group">
      <name>W3C Web Authentication Working Group</name>
      <uri>mailto:public-webauthn&amp;w3.org</uri>
      <updated>2022-02-28</updated> 
    </person>
    <person id="W3C_Web_Payments_Working_Group">
      <name>W3C Web Payments Working Group</name>
      <uri>mailto:public-payments-wg&amp;w3.org</uri>
      <updated>2023-09-13</updated> 
    </person>
  </people>

</registry>
