From 9d8f855f2e78e38bae340eeffb33f2dee8e8b5a2 Mon Sep 17 00:00:00 2001
From: Emil Lundberg <emil@yubico.com>
Date: Thu, 22 Sep 2022 17:01:16 +0000
Subject: [PATCH] Merge pull request #1773 from w3c/credential-record

SHA: 6c823f1f8af0c7e63c4a309b141559fcb8990ff5
Reason: push, by @emlun

Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
---
 index.html | 2430 ++++++++++++++++++++++++++++------------------------
 1 file changed, 1308 insertions(+), 1122 deletions(-)

diff --git a/index.html b/index.html
index af91944c1..39f9e4886 100644
--- a/index.html
+++ b/index.html
@@ -6,7 +6,7 @@
   <meta content="ED" name="w3c-status">
   <meta content="Bikeshed version 44af0bf3e, updated Fri Jul 29 17:05:16 2022 -0700" name="generator">
   <link href="https://www.w3.org/TR/webauthn-3/" rel="canonical">
-  <meta content="0bfc0d08a554b38378ed9666640b966236c7ea08" name="document-revision">
+  <meta content="6c823f1f8af0c7e63c4a309b141559fcb8990ff5" name="document-revision">
 <style type="text/css">
 body {
     counter-reset: table;
@@ -381,7 +381,7 @@
   <div class="head">
    <p data-fill-with="logo"><a class="logo" href="https://www.w3.org/"> <img alt="W3C" height="48" src="https://www.w3.org/StyleSheets/TR/2021/logos/W3C" width="72"> </a> </p>
    <h1>Web Authentication:<br>An API for accessing Public Key Credentials<br>Level 3</h1>
-   <p id="w3c-state"><a href="https://www.w3.org/standards/types#ED">Editor’s Draft</a>, <time class="dt-updated" datetime="2022-09-21">21 September 2022</time></p>
+   <p id="w3c-state"><a href="https://www.w3.org/standards/types#ED">Editor’s Draft</a>, <time class="dt-updated" datetime="2022-09-22">22 September 2022</time></p>
    <details open>
     <summary>More details about this document</summary>
     <div data-fill-with="spec-metadata">
@@ -1534,10 +1534,68 @@ <h2 class="heading settled" data-level="4" id="sctn-terminology"><span class="se
     <dt data-md><dfn class="dfn-paneled" data-dfn-type="dfn" data-noexport id="credential-properties">Credential Properties</dfn>
     <dd data-md>
      <p>A <a data-link-type="dfn" href="#credential-properties" id="ref-for-credential-properties①">credential property</a> is some characteristic property of a <a data-link-type="dfn" href="#public-key-credential-source" id="ref-for-public-key-credential-source①②">public key credential source</a>, such as whether it is a <a data-link-type="dfn" href="#client-side-discoverable-credential" id="ref-for-client-side-discoverable-credential③">client-side discoverable credential</a> or a <a data-link-type="dfn" href="#server-side-credential" id="ref-for-server-side-credential①">server-side credential</a>.</p>
+    <dt data-md><dfn class="dfn-paneled" data-dfn-type="dfn" data-noexport id="credential-record">Credential Record</dfn>
+    <dd data-md>
+     <p>In order to implement the algorithms defined in <a href="#sctn-rp-operations">§ 7 WebAuthn Relying Party Operations</a>,
+the <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party④⑦">Relying Party</a> MUST store some properties of registered <a data-link-type="dfn" href="#public-key-credential-source" id="ref-for-public-key-credential-source①③">public key credential sources</a>.
+The <a data-link-type="dfn" href="#credential-record" id="ref-for-credential-record">credential record</a> <a data-link-type="dfn" href="https://infra.spec.whatwg.org/#struct" id="ref-for-struct">struct</a> is an abstraction of these properties stored in a <a data-link-type="dfn" href="#user-account" id="ref-for-user-account">user account</a>.
+A credential record is created during a <a data-link-type="dfn" href="#registration-ceremony" id="ref-for-registration-ceremony①">registration ceremony</a> and used in subsequent <a data-link-type="dfn" href="#authentication-ceremony" id="ref-for-authentication-ceremony③">authentication ceremonies</a>. <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party④⑧">Relying Parties</a> MAY delete credential records as necessary or when requested by users.</p>
+     <p>The following <a data-link-type="dfn" href="https://infra.spec.whatwg.org/#struct-item" id="ref-for-struct-item">items</a> are RECOMMENDED in order to implement all steps of <a href="#sctn-registering-a-new-credential">§ 7.1 Registering a New Credential</a> and <a href="#sctn-verifying-assertion">§ 7.2 Verifying an Authentication Assertion</a> as defined:</p>
+     <dl>
+      <dt data-md><dfn class="dfn-paneled" data-dfn-for="credential record" data-dfn-type="dfn" data-noexport id="credential-record-type">type</dfn>
+      <dd data-md>
+       <p>The <a data-link-type="dfn" href="#public-key-credential-source-type" id="ref-for-public-key-credential-source-type">type</a> of the <a data-link-type="dfn" href="#public-key-credential-source" id="ref-for-public-key-credential-source①④">public key credential source</a>.</p>
+      <dt data-md><dfn class="dfn-paneled" data-dfn-for="credential record" data-dfn-type="dfn" data-noexport id="credential-record-id">id</dfn>
+      <dd data-md>
+       <p>The <a data-link-type="dfn" href="#credential-id" id="ref-for-credential-id①⓪">Credential ID</a> of the <a data-link-type="dfn" href="#public-key-credential-source" id="ref-for-public-key-credential-source①⑤">public key credential source</a>.</p>
+      <dt data-md><dfn class="dfn-paneled" data-dfn-for="credential record" data-dfn-type="dfn" data-noexport id="credential-record-publickey">publicKey</dfn>
+      <dd data-md>
+       <p>The <a data-link-type="dfn" href="#credential-public-key" id="ref-for-credential-public-key⑥">credential public key</a> of the <a data-link-type="dfn" href="#public-key-credential-source" id="ref-for-public-key-credential-source①⑥">public key credential source</a>.</p>
+      <dt data-md><dfn class="dfn-paneled" data-dfn-for="credential record" data-dfn-type="dfn" data-noexport id="credential-record-signcount">signCount</dfn>
+      <dd data-md>
+       <p>The latest value of the <a data-link-type="dfn" href="#authdata-signcount" id="ref-for-authdata-signcount">signature counter</a> in the <a data-link-type="dfn" href="#authenticator-data" id="ref-for-authenticator-data③">authenticator data</a> from any <a data-link-type="dfn" href="#ceremony" id="ref-for-ceremony⑥">ceremony</a> using the <a data-link-type="dfn" href="#public-key-credential-source" id="ref-for-public-key-credential-source①⑦">public key credential source</a>.</p>
+      <dt data-md><dfn class="dfn-paneled" data-dfn-for="credential record" data-dfn-type="dfn" data-noexport id="credential-record-transports">transports</dfn>
+      <dd data-md>
+       <p>The value returned from <code class="idl"><a data-link-type="idl" href="#dom-authenticatorattestationresponse-gettransports" id="ref-for-dom-authenticatorattestationresponse-gettransports">getTransports()</a></code> when the <a data-link-type="dfn" href="#public-key-credential-source" id="ref-for-public-key-credential-source①⑧">public key credential source</a> was <a data-link-type="dfn" href="#registration" id="ref-for-registration①⓪">registered</a>.</p>
+       <p class="note" role="note"><span>Note:</span> Modifying or removing <a data-link-type="dfn" href="https://infra.spec.whatwg.org/#list-item" id="ref-for-list-item">items</a> from the value returned from <code class="idl"><a data-link-type="idl" href="#dom-authenticatorattestationresponse-gettransports" id="ref-for-dom-authenticatorattestationresponse-gettransports①">getTransports()</a></code> could negatively impact user experience, or even prevent use of the corresponding credential.</p>
+      <dt data-md><dfn class="dfn-paneled" data-dfn-for="credential record" data-dfn-type="dfn" data-noexport id="credential-record-be">BE</dfn>
+      <dd data-md>
+       <p>The value of the <a data-link-type="dfn" href="#authdata-flags-be" id="ref-for-authdata-flags-be">BE</a> <a data-link-type="dfn" href="#authdata-flags" id="ref-for-authdata-flags②">flag</a> when the <a data-link-type="dfn" href="#public-key-credential-source" id="ref-for-public-key-credential-source①⑨">public key credential source</a> was created.</p>
+      <dt data-md><dfn class="dfn-paneled" data-dfn-for="credential record" data-dfn-type="dfn" data-noexport id="credential-record-bs">BS</dfn>
+      <dd data-md>
+       <p>The latest value of the <a data-link-type="dfn" href="#authdata-flags-bs" id="ref-for-authdata-flags-bs">BS</a> <a data-link-type="dfn" href="#authdata-flags" id="ref-for-authdata-flags③">flag</a> in the <a data-link-type="dfn" href="#authenticator-data" id="ref-for-authenticator-data④">authenticator data</a> from any <a data-link-type="dfn" href="#ceremony" id="ref-for-ceremony⑦">ceremony</a> using the <a data-link-type="dfn" href="#public-key-credential-source" id="ref-for-public-key-credential-source②⓪">public key credential source</a>.</p>
+     </dl>
+     <p>The following <a data-link-type="dfn" href="https://infra.spec.whatwg.org/#struct-item" id="ref-for-struct-item①">items</a> are OPTIONAL:</p>
+     <dl>
+      <dt data-md><dfn class="dfn-paneled" data-dfn-for="credential record" data-dfn-type="dfn" data-noexport id="credential-record-attestationobject">attestationObject</dfn>
+      <dd data-md>
+       <p>The value of the <code class="idl"><a data-link-type="idl" href="#dom-authenticatorattestationresponse-attestationobject" id="ref-for-dom-authenticatorattestationresponse-attestationobject">attestationObject</a></code> attribute
+when the <a data-link-type="dfn" href="#public-key-credential-source" id="ref-for-public-key-credential-source②①">public key credential source</a> was <a data-link-type="dfn" href="#registration" id="ref-for-registration①①">registered</a>.
+Storing this enables the <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party④⑨">Relying Party</a> to reference the credential’s <a data-link-type="dfn" href="#attestation-statement" id="ref-for-attestation-statement②">attestation statement</a> at a later time.</p>
+      <dt data-md><dfn class="dfn-paneled" data-dfn-for="credential record" data-dfn-type="dfn" data-noexport id="credential-record-attestationclientdatajson">attestationClientDataJSON</dfn>
+      <dd data-md>
+       <p>The value of the <code class="idl"><a data-link-type="idl" href="#dom-authenticatorresponse-clientdatajson" id="ref-for-dom-authenticatorresponse-clientdatajson">clientDataJSON</a></code> attribute
+when the <a data-link-type="dfn" href="#public-key-credential-source" id="ref-for-public-key-credential-source②②">public key credential source</a> was <a data-link-type="dfn" href="#registration" id="ref-for-registration①②">registered</a>.
+Storing this in combination with the above <a data-link-type="dfn" href="#credential-record-attestationobject" id="ref-for-credential-record-attestationobject">attestationObject</a> <a data-link-type="dfn" href="https://infra.spec.whatwg.org/#struct-item" id="ref-for-struct-item②">item</a> enables the <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party⑤⓪">Relying Party</a> to re-verify the <a data-link-type="dfn" href="#attestation-signature" id="ref-for-attestation-signature①">attestation signature</a> at a later time.</p>
+     </dl>
+     <p><a data-link-type="dfn" href="#webauthn-extensions" id="ref-for-webauthn-extensions">WebAuthn extensions</a> MAY define additional <a data-link-type="dfn" href="https://infra.spec.whatwg.org/#struct-item" id="ref-for-struct-item③">items</a> needed to process the extension. <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party⑤①">Relying Parties</a> MAY also include any additional <a data-link-type="dfn" href="https://infra.spec.whatwg.org/#struct-item" id="ref-for-struct-item④">items</a> as needed,
+and MAY omit any <a data-link-type="dfn" href="https://infra.spec.whatwg.org/#struct-item" id="ref-for-struct-item⑤">items</a> not needed for their implementation.</p>
+     <p>The <dfn class="dfn-paneled" data-dfn-type="dfn" data-noexport id="credential-descriptor-for-a-credential-record">credential descriptor for a credential record</dfn> is a <code class="idl"><a data-link-type="idl" href="#dictdef-publickeycredentialdescriptor" id="ref-for-dictdef-publickeycredentialdescriptor">PublicKeyCredentialDescriptor</a></code> value with the contents:</p>
+     <dl>
+      <dt data-md><code class="idl"><a data-link-type="idl" href="#dom-publickeycredentialdescriptor-type" id="ref-for-dom-publickeycredentialdescriptor-type">type</a></code>
+      <dd data-md>
+       <p>The <a data-link-type="dfn" href="#credential-record-type" id="ref-for-credential-record-type">type</a> of the <a data-link-type="dfn" href="#credential-record" id="ref-for-credential-record①">credential record</a>.</p>
+      <dt data-md><code class="idl"><a data-link-type="idl" href="#dom-publickeycredentialdescriptor-id" id="ref-for-dom-publickeycredentialdescriptor-id">id</a></code>
+      <dd data-md>
+       <p>The <a data-link-type="dfn" href="#credential-record-id" id="ref-for-credential-record-id">id</a> of the <a data-link-type="dfn" href="#credential-record" id="ref-for-credential-record②">credential record</a>.</p>
+      <dt data-md><code class="idl"><a data-link-type="idl" href="#dom-publickeycredentialdescriptor-transports" id="ref-for-dom-publickeycredentialdescriptor-transports①">transports</a></code>
+      <dd data-md>
+       <p>The <a data-link-type="dfn" href="#credential-record-transports" id="ref-for-credential-record-transports">transports</a> of the <a data-link-type="dfn" href="#credential-record" id="ref-for-credential-record③">credential record</a>.</p>
+     </dl>
     <dt data-md><dfn class="dfn-paneled" data-dfn-type="dfn" data-noexport id="generating-authenticator">Generating Authenticator</dfn>
     <dd data-md>
      <p>The Generating Authenticator is the authenticator involved in the <a data-link-type="dfn" href="#authenticatormakecredential" id="ref-for-authenticatormakecredential①">authenticatorMakeCredential</a> operation resulting
-in the creation of a given <a data-link-type="dfn" href="#public-key-credential-source" id="ref-for-public-key-credential-source①③">public key credential source</a>. The <a data-link-type="dfn" href="#generating-authenticator" id="ref-for-generating-authenticator②">generating authenticator</a> is the same as the <a data-link-type="dfn" href="#public-key-credential-source-managing-authenticator" id="ref-for-public-key-credential-source-managing-authenticator⑦">managing authenticator</a> for <a data-link-type="dfn" href="#single-device-credential" id="ref-for-single-device-credential">single-device credentials</a>. For <a data-link-type="dfn" href="#multi-device-credential" id="ref-for-multi-device-credential①">multi-device credentials</a>, the generating authenticator may or may not be the same as the
+in the creation of a given <a data-link-type="dfn" href="#public-key-credential-source" id="ref-for-public-key-credential-source②③">public key credential source</a>. The <a data-link-type="dfn" href="#generating-authenticator" id="ref-for-generating-authenticator②">generating authenticator</a> is the same as the <a data-link-type="dfn" href="#public-key-credential-source-managing-authenticator" id="ref-for-public-key-credential-source-managing-authenticator⑦">managing authenticator</a> for <a data-link-type="dfn" href="#single-device-credential" id="ref-for-single-device-credential">single-device credentials</a>. For <a data-link-type="dfn" href="#multi-device-credential" id="ref-for-multi-device-credential①">multi-device credentials</a>, the generating authenticator may or may not be the same as the
 current <a data-link-type="dfn" href="#public-key-credential-source-managing-authenticator" id="ref-for-public-key-credential-source-managing-authenticator⑧">managing authenticator</a> participating in a given <a data-link-type="dfn" href="#authentication" id="ref-for-authentication⑤">authentication</a> operation.</p>
     <dt data-md><dfn class="dfn-paneled" data-dfn-type="dfn" data-noexport id="human-palatability">Human Palatability</dfn>
     <dd data-md>
@@ -1545,11 +1603,11 @@ <h2 class="heading settled" data-level="4" id="sctn-terminology"><span class="se
 users, in contrast to identifiers that are, for example, randomly generated sequences of bits <a data-link-type="biblio" href="#biblio-edupersonobjectclassspec">[EduPersonObjectClassSpec]</a>.</p>
     <dt data-md><dfn class="dfn-paneled" data-dfn-type="dfn" data-noexport id="non-discoverable-credential">Non-Discoverable Credential</dfn>
     <dd data-md>
-     <p>This is a <a data-link-type="dfn" href="https://w3c.github.io/webappsec-credential-management/#concept-credential" id="ref-for-concept-credential②">credential</a> whose <a data-link-type="dfn" href="#credential-id" id="ref-for-credential-id①⓪">credential ID</a> must be provided in <code class="idl"><a data-link-type="idl" href="#dom-publickeycredentialrequestoptions-allowcredentials" id="ref-for-dom-publickeycredentialrequestoptions-allowcredentials②">allowCredentials</a></code> when calling <code class="idl"><a data-link-type="idl" href="https://w3c.github.io/webappsec-credential-management/#dom-credentialscontainer-get" id="ref-for-dom-credentialscontainer-get④">navigator.credentials.get()</a></code> because it is not <a data-link-type="dfn" href="#client-side-discoverable-credential" id="ref-for-client-side-discoverable-credential④">client-side discoverable</a>. See also <a data-link-type="dfn" href="#server-side-credential" id="ref-for-server-side-credential②">server-side credentials</a>.</p>
+     <p>This is a <a data-link-type="dfn" href="https://w3c.github.io/webappsec-credential-management/#concept-credential" id="ref-for-concept-credential②">credential</a> whose <a data-link-type="dfn" href="#credential-id" id="ref-for-credential-id①①">credential ID</a> must be provided in <code class="idl"><a data-link-type="idl" href="#dom-publickeycredentialrequestoptions-allowcredentials" id="ref-for-dom-publickeycredentialrequestoptions-allowcredentials②">allowCredentials</a></code> when calling <code class="idl"><a data-link-type="idl" href="https://w3c.github.io/webappsec-credential-management/#dom-credentialscontainer-get" id="ref-for-dom-credentialscontainer-get④">navigator.credentials.get()</a></code> because it is not <a data-link-type="dfn" href="#client-side-discoverable-credential" id="ref-for-client-side-discoverable-credential④">client-side discoverable</a>. See also <a data-link-type="dfn" href="#server-side-credential" id="ref-for-server-side-credential②">server-side credentials</a>.</p>
     <dt data-md><dfn class="dfn-paneled" data-dfn-type="dfn" data-noexport id="public-key-credential">Public Key Credential</dfn>
     <dd data-md>
-     <p>Generically, a <em>credential</em> is data one entity presents to another in order to <em>authenticate</em> the former to the latter <a data-link-type="biblio" href="#biblio-rfc4949">[RFC4949]</a>. The term <a data-link-type="dfn" href="#public-key-credential" id="ref-for-public-key-credential①③">public key credential</a> refers to one of: a <a data-link-type="dfn" href="#public-key-credential-source" id="ref-for-public-key-credential-source①④">public key credential source</a>, the
-possibly-<a data-link-type="dfn" href="#attestation" id="ref-for-attestation⑤">attested</a> <a data-link-type="dfn" href="#credential-public-key" id="ref-for-credential-public-key⑥">credential public key</a> corresponding to a <a data-link-type="dfn" href="#public-key-credential-source" id="ref-for-public-key-credential-source①⑤">public key credential source</a>, or an <a data-link-type="dfn" href="#authentication-assertion" id="ref-for-authentication-assertion③">authentication assertion</a>. Which one is generally determined by context.</p>
+     <p>Generically, a <em>credential</em> is data one entity presents to another in order to <em>authenticate</em> the former to the latter <a data-link-type="biblio" href="#biblio-rfc4949">[RFC4949]</a>. The term <a data-link-type="dfn" href="#public-key-credential" id="ref-for-public-key-credential①③">public key credential</a> refers to one of: a <a data-link-type="dfn" href="#public-key-credential-source" id="ref-for-public-key-credential-source②④">public key credential source</a>, the
+possibly-<a data-link-type="dfn" href="#attestation" id="ref-for-attestation⑤">attested</a> <a data-link-type="dfn" href="#credential-public-key" id="ref-for-credential-public-key⑦">credential public key</a> corresponding to a <a data-link-type="dfn" href="#public-key-credential-source" id="ref-for-public-key-credential-source②⑤">public key credential source</a>, or an <a data-link-type="dfn" href="#authentication-assertion" id="ref-for-authentication-assertion③">authentication assertion</a>. Which one is generally determined by context.</p>
      <div class="note" role="note">
        Note: This is a <a data-link-type="dfn" href="https://infra.spec.whatwg.org/#willful-violation" id="ref-for-willful-violation">willful violation</a> of <a data-link-type="biblio" href="#biblio-rfc4949">[RFC4949]</a>. In English, a "credential" is both a) the thing presented to prove
     a statement and b) intended to be used multiple times. It’s impossible to achieve both criteria securely with a single
@@ -1559,47 +1617,47 @@ <h2 class="heading settled" data-level="4" id="sctn-terminology"><span class="se
       <dl>
        <dt data-md>"Authentication information" (possibly including a private key)
        <dd data-md>
-        <p><a data-link-type="dfn" href="#public-key-credential-source" id="ref-for-public-key-credential-source①⑥">Public key credential source</a></p>
+        <p><a data-link-type="dfn" href="#public-key-credential-source" id="ref-for-public-key-credential-source②⑥">Public key credential source</a></p>
        <dt data-md>"Signed value"
        <dd data-md>
         <p><a data-link-type="dfn" href="#authentication-assertion" id="ref-for-authentication-assertion④">Authentication assertion</a></p>
        <dt data-md><a data-link-type="biblio" href="#biblio-rfc4949">[RFC4949]</a> "credential"
        <dd data-md>
-        <p><a data-link-type="dfn" href="#credential-public-key" id="ref-for-credential-public-key⑦">Credential public key</a> or <a data-link-type="dfn" href="#attestation-object" id="ref-for-attestation-object②">attestation object</a></p>
+        <p><a data-link-type="dfn" href="#credential-public-key" id="ref-for-credential-public-key⑧">Credential public key</a> or <a data-link-type="dfn" href="#attestation-object" id="ref-for-attestation-object②">attestation object</a></p>
       </dl>
      </div>
-     <p>At <a data-link-type="dfn" href="#registration" id="ref-for-registration①⓪">registration</a> time, the <a data-link-type="dfn" href="#authenticator" id="ref-for-authenticator④⑧">authenticator</a> creates an asymmetric key pair, and stores its <a data-link-type="dfn" href="#credential-private-key" id="ref-for-credential-private-key③">private key portion</a> and information from the <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party④⑦">Relying Party</a> into a <a data-link-type="dfn" href="#public-key-credential-source" id="ref-for-public-key-credential-source①⑦">public key credential source</a>. The <a data-link-type="dfn" href="#credential-public-key" id="ref-for-credential-public-key⑧">public key portion</a> is returned to the <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party④⑧">Relying Party</a>, which then stores it in the active <a data-link-type="dfn" href="#user-account" id="ref-for-user-account">user account</a>.
-Subsequently, only that <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party④⑨">Relying Party</a>, as identified by its <a data-link-type="dfn" href="#rp-id" id="ref-for-rp-id②">RP ID</a>, is able to employ the <a data-link-type="dfn" href="#public-key-credential" id="ref-for-public-key-credential①④">public key credential</a> in <a data-link-type="dfn" href="#authentication" id="ref-for-authentication⑥">authentication ceremonies</a>, via the <code class="idl"><a data-link-type="idl" href="https://w3c.github.io/webappsec-credential-management/#dom-credentialscontainer-get" id="ref-for-dom-credentialscontainer-get⑤">get()</a></code> method. The <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party⑤⓪">Relying Party</a> uses its stored
-copy of the <a data-link-type="dfn" href="#credential-public-key" id="ref-for-credential-public-key⑨">credential public key</a> to verify the resultant <a data-link-type="dfn" href="#authentication-assertion" id="ref-for-authentication-assertion⑤">authentication assertion</a>.</p>
+     <p>At <a data-link-type="dfn" href="#registration" id="ref-for-registration①③">registration</a> time, the <a data-link-type="dfn" href="#authenticator" id="ref-for-authenticator④⑧">authenticator</a> creates an asymmetric key pair, and stores its <a data-link-type="dfn" href="#credential-private-key" id="ref-for-credential-private-key③">private key portion</a> and information from the <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party⑤②">Relying Party</a> into a <a data-link-type="dfn" href="#public-key-credential-source" id="ref-for-public-key-credential-source②⑦">public key credential source</a>. The <a data-link-type="dfn" href="#credential-public-key" id="ref-for-credential-public-key⑨">public key portion</a> is returned to the <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party⑤③">Relying Party</a>, which then stores it in the active <a data-link-type="dfn" href="#user-account" id="ref-for-user-account①">user account</a>.
+Subsequently, only that <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party⑤④">Relying Party</a>, as identified by its <a data-link-type="dfn" href="#rp-id" id="ref-for-rp-id②">RP ID</a>, is able to employ the <a data-link-type="dfn" href="#public-key-credential" id="ref-for-public-key-credential①④">public key credential</a> in <a data-link-type="dfn" href="#authentication" id="ref-for-authentication⑥">authentication ceremonies</a>, via the <code class="idl"><a data-link-type="idl" href="https://w3c.github.io/webappsec-credential-management/#dom-credentialscontainer-get" id="ref-for-dom-credentialscontainer-get⑤">get()</a></code> method. The <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party⑤⑤">Relying Party</a> uses its stored
+copy of the <a data-link-type="dfn" href="#credential-public-key" id="ref-for-credential-public-key①⓪">credential public key</a> to verify the resultant <a data-link-type="dfn" href="#authentication-assertion" id="ref-for-authentication-assertion⑤">authentication assertion</a>.</p>
     <dt data-md><dfn class="dfn-paneled" data-dfn-type="dfn" data-noexport id="public-key-credential-source">Public Key Credential Source</dfn>
     <dd data-md>
-     <p>A <a data-link-type="dfn" href="https://w3c.github.io/webappsec-credential-management/#credential-source" id="ref-for-credential-source">credential source</a> (<a data-link-type="biblio" href="#biblio-credential-management-1">[CREDENTIAL-MANAGEMENT-1]</a>) used by an <a data-link-type="dfn" href="#authenticator" id="ref-for-authenticator④⑨">authenticator</a> to generate <a data-link-type="dfn" href="#authentication-assertion" id="ref-for-authentication-assertion⑥">authentication assertions</a>. A <a data-link-type="dfn" href="#public-key-credential-source" id="ref-for-public-key-credential-source①⑧">public key credential source</a> consists of a <a data-link-type="dfn" href="https://infra.spec.whatwg.org/#struct" id="ref-for-struct">struct</a> with the following <a data-link-type="dfn" href="https://infra.spec.whatwg.org/#struct-item" id="ref-for-struct-item">items</a>:</p>
+     <p>A <a data-link-type="dfn" href="https://w3c.github.io/webappsec-credential-management/#credential-source" id="ref-for-credential-source">credential source</a> (<a data-link-type="biblio" href="#biblio-credential-management-1">[CREDENTIAL-MANAGEMENT-1]</a>) used by an <a data-link-type="dfn" href="#authenticator" id="ref-for-authenticator④⑨">authenticator</a> to generate <a data-link-type="dfn" href="#authentication-assertion" id="ref-for-authentication-assertion⑥">authentication assertions</a>. A <a data-link-type="dfn" href="#public-key-credential-source" id="ref-for-public-key-credential-source②⑧">public key credential source</a> consists of a <a data-link-type="dfn" href="https://infra.spec.whatwg.org/#struct" id="ref-for-struct①">struct</a> with the following <a data-link-type="dfn" href="https://infra.spec.whatwg.org/#struct-item" id="ref-for-struct-item⑥">items</a>:</p>
      <dl>
       <dt data-md><dfn class="dfn-paneled" data-dfn-for="public key credential source" data-dfn-type="dfn" data-noexport id="public-key-credential-source-type">type</dfn>
       <dd data-md>
        <p>whose value is of <code class="idl"><a data-link-type="idl" href="#enumdef-publickeycredentialtype" id="ref-for-enumdef-publickeycredentialtype">PublicKeyCredentialType</a></code>, defaulting to <code class="idl"><a data-link-type="idl" href="#dom-publickeycredentialtype-public-key" id="ref-for-dom-publickeycredentialtype-public-key">public-key</a></code>.</p>
       <dt data-md><dfn class="dfn-paneled" data-dfn-for="public key credential source" data-dfn-type="dfn" data-noexport id="public-key-credential-source-id">id</dfn>
       <dd data-md>
-       <p>A <a data-link-type="dfn" href="#credential-id" id="ref-for-credential-id①①">Credential ID</a>.</p>
+       <p>A <a data-link-type="dfn" href="#credential-id" id="ref-for-credential-id①②">Credential ID</a>.</p>
       <dt data-md><dfn class="dfn-paneled" data-dfn-for="public key credential source" data-dfn-type="dfn" data-noexport id="public-key-credential-source-privatekey">privateKey</dfn>
       <dd data-md>
        <p>The <a data-link-type="dfn" href="#credential-private-key" id="ref-for-credential-private-key④">credential private key</a>.</p>
       <dt data-md><dfn class="dfn-paneled" data-dfn-for="public key credential source" data-dfn-type="dfn" data-noexport id="public-key-credential-source-rpid">rpId</dfn>
       <dd data-md>
-       <p>The <a data-link-type="dfn" href="#relying-party-identifier" id="ref-for-relying-party-identifier">Relying Party Identifier</a>, for the <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party⑤①">Relying Party</a> this <a data-link-type="dfn" href="#public-key-credential-source" id="ref-for-public-key-credential-source①⑨">public key credential source</a> is <a data-link-type="dfn" href="#scope" id="ref-for-scope⑥">scoped</a> to.
+       <p>The <a data-link-type="dfn" href="#relying-party-identifier" id="ref-for-relying-party-identifier">Relying Party Identifier</a>, for the <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party⑤⑥">Relying Party</a> this <a data-link-type="dfn" href="#public-key-credential-source" id="ref-for-public-key-credential-source②⑨">public key credential source</a> is <a data-link-type="dfn" href="#scope" id="ref-for-scope⑥">scoped</a> to.
 This is determined by the <code><code class="idl"><a data-link-type="idl" href="#dom-publickeycredentialcreationoptions-rp" id="ref-for-dom-publickeycredentialcreationoptions-rp">rp</a></code>.<code class="idl"><a data-link-type="idl" href="#dom-publickeycredentialrpentity-id" id="ref-for-dom-publickeycredentialrpentity-id">id</a></code></code> parameter of the <code class="idl"><a data-link-type="idl" href="https://w3c.github.io/webappsec-credential-management/#dom-credentialscontainer-create" id="ref-for-dom-credentialscontainer-create①">create()</a></code> operation.</p>
       <dt data-md><dfn class="dfn-paneled" data-dfn-for="public key credential source" data-dfn-type="dfn" data-noexport id="public-key-credential-source-userhandle">userHandle</dfn>
       <dd data-md>
-       <p>The <a data-link-type="dfn" href="#user-handle" id="ref-for-user-handle①">user handle</a> associated when this <a data-link-type="dfn" href="#public-key-credential-source" id="ref-for-public-key-credential-source②⓪">public key credential source</a> was created. This <a data-link-type="dfn" href="https://infra.spec.whatwg.org/#struct-item" id="ref-for-struct-item①">item</a> is
+       <p>The <a data-link-type="dfn" href="#user-handle" id="ref-for-user-handle①">user handle</a> associated when this <a data-link-type="dfn" href="#public-key-credential-source" id="ref-for-public-key-credential-source③⓪">public key credential source</a> was created. This <a data-link-type="dfn" href="https://infra.spec.whatwg.org/#struct-item" id="ref-for-struct-item⑦">item</a> is
 nullable.</p>
       <dt data-md><dfn class="dfn-paneled" data-dfn-for="public key credential source" data-dfn-type="dfn" data-noexport id="public-key-credential-source-otherui">otherUI</dfn>
       <dd data-md>
-       <p>OPTIONAL other information used by the <a data-link-type="dfn" href="#authenticator" id="ref-for-authenticator⑤⓪">authenticator</a> to inform its UI. For example, this might include the user’s <code class="idl"><a data-link-type="idl" href="#dom-publickeycredentialuserentity-displayname" id="ref-for-dom-publickeycredentialuserentity-displayname">displayName</a></code>. <a data-link-type="dfn" href="#public-key-credential-source-otherui" id="ref-for-public-key-credential-source-otherui">otherUI</a> is a <dfn class="dfn-paneled" data-dfn-for="public key credential source" data-dfn-type="dfn" data-noexport id="public-key-credential-source-mutable-item">mutable item</dfn> and SHOULD NOT be bound to the <a data-link-type="dfn" href="#public-key-credential-source" id="ref-for-public-key-credential-source②①">public key credential source</a> in a way that prevents <a data-link-type="dfn" href="#public-key-credential-source-otherui" id="ref-for-public-key-credential-source-otherui①">otherUI</a> from being updated.</p>
+       <p>OPTIONAL other information used by the <a data-link-type="dfn" href="#authenticator" id="ref-for-authenticator⑤⓪">authenticator</a> to inform its UI. For example, this might include the user’s <code class="idl"><a data-link-type="idl" href="#dom-publickeycredentialuserentity-displayname" id="ref-for-dom-publickeycredentialuserentity-displayname">displayName</a></code>. <a data-link-type="dfn" href="#public-key-credential-source-otherui" id="ref-for-public-key-credential-source-otherui">otherUI</a> is a <dfn class="dfn-paneled" data-dfn-for="public key credential source" data-dfn-type="dfn" data-noexport id="public-key-credential-source-mutable-item">mutable item</dfn> and SHOULD NOT be bound to the <a data-link-type="dfn" href="#public-key-credential-source" id="ref-for-public-key-credential-source③①">public key credential source</a> in a way that prevents <a data-link-type="dfn" href="#public-key-credential-source-otherui" id="ref-for-public-key-credential-source-otherui①">otherUI</a> from being updated.</p>
      </dl>
-     <p>The <a data-link-type="dfn" href="#authenticatormakecredential" id="ref-for-authenticatormakecredential②">authenticatorMakeCredential</a> operation creates a <a data-link-type="dfn" href="#public-key-credential-source" id="ref-for-public-key-credential-source②②">public key credential source</a> <a data-link-type="dfn" href="#bound-credential" id="ref-for-bound-credential⑥">bound</a> to a <dfn class="dfn-paneled" data-dfn-for="public key
-credential source" data-dfn-type="dfn" data-noexport id="public-key-credential-source-managing-authenticator">managing authenticator</dfn> and returns the <a data-link-type="dfn" href="#credential-public-key" id="ref-for-credential-public-key①⓪">credential public key</a> associated with its <a data-link-type="dfn" href="#credential-private-key" id="ref-for-credential-private-key⑤">credential
-private key</a>. The <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party⑤②">Relying Party</a> can use this <a data-link-type="dfn" href="#credential-public-key" id="ref-for-credential-public-key①①">credential public key</a> to verify the <a data-link-type="dfn" href="#authentication-assertion" id="ref-for-authentication-assertion⑦">authentication assertions</a> created by
-this <a data-link-type="dfn" href="#public-key-credential-source" id="ref-for-public-key-credential-source②③">public key credential source</a>.</p>
+     <p>The <a data-link-type="dfn" href="#authenticatormakecredential" id="ref-for-authenticatormakecredential②">authenticatorMakeCredential</a> operation creates a <a data-link-type="dfn" href="#public-key-credential-source" id="ref-for-public-key-credential-source③②">public key credential source</a> <a data-link-type="dfn" href="#bound-credential" id="ref-for-bound-credential⑥">bound</a> to a <dfn class="dfn-paneled" data-dfn-for="public key
+credential source" data-dfn-type="dfn" data-noexport id="public-key-credential-source-managing-authenticator">managing authenticator</dfn> and returns the <a data-link-type="dfn" href="#credential-public-key" id="ref-for-credential-public-key①①">credential public key</a> associated with its <a data-link-type="dfn" href="#credential-private-key" id="ref-for-credential-private-key⑤">credential
+private key</a>. The <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party⑤⑦">Relying Party</a> can use this <a data-link-type="dfn" href="#credential-public-key" id="ref-for-credential-public-key①②">credential public key</a> to verify the <a data-link-type="dfn" href="#authentication-assertion" id="ref-for-authentication-assertion⑦">authentication assertions</a> created by
+this <a data-link-type="dfn" href="#public-key-credential-source" id="ref-for-public-key-credential-source③③">public key credential source</a>.</p>
     <dt data-md><dfn class="dfn-paneled" data-dfn-type="dfn" data-noexport id="rate-limiting">Rate Limiting</dfn>
     <dd data-md>
      <p>The process (also known as throttling) by which an authenticator implements controls against brute force attacks by limiting
@@ -1610,30 +1668,30 @@ <h2 class="heading settled" data-level="4" id="sctn-terminology"><span class="se
     <dt data-md><dfn class="dfn-paneled" data-dfn-type="dfn" data-noexport id="registration">Registration</dfn>
     <dt data-md><dfn class="dfn-paneled" data-dfn-type="dfn" data-noexport id="registration-ceremony">Registration Ceremony</dfn>
     <dd data-md>
-     <p>The <a data-link-type="dfn" href="#ceremony" id="ref-for-ceremony⑥">ceremony</a> where a user, a <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party⑤③">Relying Party</a>, and the user’s <a data-link-type="dfn" href="#client-platform" id="ref-for-client-platform①②">client platform</a> (containing or connected to at least one <a data-link-type="dfn" href="#authenticator" id="ref-for-authenticator⑤①">authenticator</a>) work in concert to create a <a data-link-type="dfn" href="#public-key-credential" id="ref-for-public-key-credential①⑤">public key credential</a> and associate it with a <a data-link-type="dfn" href="#user-account" id="ref-for-user-account①">user account</a>.
+     <p>The <a data-link-type="dfn" href="#ceremony" id="ref-for-ceremony⑧">ceremony</a> where a user, a <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party⑤⑧">Relying Party</a>, and the user’s <a data-link-type="dfn" href="#client-platform" id="ref-for-client-platform①②">client platform</a> (containing or connected to at least one <a data-link-type="dfn" href="#authenticator" id="ref-for-authenticator⑤①">authenticator</a>) work in concert to create a <a data-link-type="dfn" href="#public-key-credential" id="ref-for-public-key-credential①⑤">public key credential</a> and associate it with a <a data-link-type="dfn" href="#user-account" id="ref-for-user-account②">user account</a>.
 Note that this includes employing a <a data-link-type="dfn" href="#test-of-user-presence" id="ref-for-test-of-user-presence②">test of user presence</a> or <a data-link-type="dfn" href="#user-verification" id="ref-for-user-verification④">user verification</a>.
-After a successful <a data-link-type="dfn" href="#registration-ceremony" id="ref-for-registration-ceremony①">registration ceremony</a>, the user can be authenticated by an <a data-link-type="dfn" href="#authentication-ceremony" id="ref-for-authentication-ceremony③">authentication ceremony</a>.</p>
-     <p>The WebAuthn <a data-link-type="dfn" href="#registration-ceremony" id="ref-for-registration-ceremony②">registration ceremony</a> is defined in <a href="#sctn-registering-a-new-credential">§ 7.1 Registering a New Credential</a>,
-and is initiated by the <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party⑤④">Relying Party</a> invoking a <code><code class="idl"><a data-link-type="idl" href="https://w3c.github.io/webappsec-credential-management/#dom-credentialscontainer-create" id="ref-for-dom-credentialscontainer-create②">navigator.credentials.create()</a></code></code> operation
+After a successful <a data-link-type="dfn" href="#registration-ceremony" id="ref-for-registration-ceremony②">registration ceremony</a>, the user can be authenticated by an <a data-link-type="dfn" href="#authentication-ceremony" id="ref-for-authentication-ceremony④">authentication ceremony</a>.</p>
+     <p>The WebAuthn <a data-link-type="dfn" href="#registration-ceremony" id="ref-for-registration-ceremony③">registration ceremony</a> is defined in <a href="#sctn-registering-a-new-credential">§ 7.1 Registering a New Credential</a>,
+and is initiated by the <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party⑤⑨">Relying Party</a> invoking a <code><code class="idl"><a data-link-type="idl" href="https://w3c.github.io/webappsec-credential-management/#dom-credentialscontainer-create" id="ref-for-dom-credentialscontainer-create②">navigator.credentials.create()</a></code></code> operation
 with a <code class="idl"><a data-link-type="idl" href="#dom-credentialcreationoptions-publickey" id="ref-for-dom-credentialcreationoptions-publickey">publicKey</a></code> argument.
 See <a href="#sctn-api">§ 5 Web Authentication API</a> for an introductory overview and <a href="#sctn-sample-registration">§ 1.3.1 Registration</a> for implementation examples.</p>
     <dt data-md><dfn class="dfn-paneled" data-dfn-type="dfn" data-noexport id="relying-party">Relying Party</dfn>
     <dt data-md><dfn class="dfn-paneled" data-dfn-type="dfn" data-noexport id="webauthn-relying-party">WebAuthn Relying Party</dfn>
     <dd data-md>
-     <p>The entity whose <dfn class="dfn-paneled" data-dfn-type="dfn" data-noexport id="web-application">web application</dfn> utilizes the <a href="#sctn-api">Web Authentication API</a> to <a data-link-type="dfn" href="#registration" id="ref-for-registration①①">register</a> and <a data-link-type="dfn" href="#authentication" id="ref-for-authentication⑦">authenticate</a> users.</p>
-     <p>A <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party⑤⑤">Relying Party</a> implementation typically consists of both some client-side script
+     <p>The entity whose <dfn class="dfn-paneled" data-dfn-type="dfn" data-noexport id="web-application">web application</dfn> utilizes the <a href="#sctn-api">Web Authentication API</a> to <a data-link-type="dfn" href="#registration" id="ref-for-registration①④">register</a> and <a data-link-type="dfn" href="#authentication" id="ref-for-authentication⑦">authenticate</a> users.</p>
+     <p>A <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party⑥⓪">Relying Party</a> implementation typically consists of both some client-side script
 that invokes the <a data-link-type="dfn" href="#web-authentication-api" id="ref-for-web-authentication-api⑦">Web Authentication API</a> in the <a data-link-type="dfn" href="#client" id="ref-for-client①④">client</a>,
 and a server-side component that executes the <a href="#sctn-rp-operations">Relying Party operations</a> and other application logic.
 Communication between the two components MUST use HTTPS or equivalent transport security,
 but is otherwise beyond the scope of this specification.</p>
-     <p class="note" role="note"><span>Note:</span> While the term <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party⑤⑥">Relying Party</a> is also often used in other contexts (e.g., X.509 and OAuth), an entity acting as a <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party⑤⑦">Relying Party</a> in one
-    context is not necessarily a <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party⑤⑧">Relying Party</a> in other contexts. In this specification, the term <a data-link-type="dfn" href="#webauthn-relying-party" id="ref-for-webauthn-relying-party⑦">WebAuthn Relying Party</a> is often shortened
-    to be just <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party⑤⑨">Relying Party</a>, and explicitly refers to a <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party⑥⓪">Relying Party</a> in the WebAuthn context. Note that in any concrete instantiation
+     <p class="note" role="note"><span>Note:</span> While the term <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party⑥①">Relying Party</a> is also often used in other contexts (e.g., X.509 and OAuth), an entity acting as a <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party⑥②">Relying Party</a> in one
+    context is not necessarily a <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party⑥③">Relying Party</a> in other contexts. In this specification, the term <a data-link-type="dfn" href="#webauthn-relying-party" id="ref-for-webauthn-relying-party⑦">WebAuthn Relying Party</a> is often shortened
+    to be just <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party⑥④">Relying Party</a>, and explicitly refers to a <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party⑥⑤">Relying Party</a> in the WebAuthn context. Note that in any concrete instantiation
     a WebAuthn context may be embedded in a broader overall context, e.g., one based on OAuth.</p>
     <dt data-md><dfn class="dfn-paneled" data-dfn-type="dfn" data-noexport id="relying-party-identifier">Relying Party Identifier</dfn>
     <dt data-md><dfn class="dfn-paneled" data-dfn-type="dfn" data-noexport id="rp-id">RP ID</dfn>
     <dd data-md>
-     <p>In the context of the <a data-link-type="dfn" href="#web-authentication-api" id="ref-for-web-authentication-api⑧">WebAuthn API</a>, a <a data-link-type="dfn" href="#relying-party-identifier" id="ref-for-relying-party-identifier①">relying party identifier</a> is a <a data-link-type="dfn" href="https://url.spec.whatwg.org/#valid-domain-string" id="ref-for-valid-domain-string">valid domain string</a> identifying the <a data-link-type="dfn" href="#webauthn-relying-party" id="ref-for-webauthn-relying-party⑧">WebAuthn Relying Party</a> on whose behalf a given <a data-link-type="dfn" href="#registration" id="ref-for-registration①②">registration</a> or <a data-link-type="dfn" href="#authentication" id="ref-for-authentication⑧">authentication ceremony</a> is being performed. A <a data-link-type="dfn" href="#public-key-credential" id="ref-for-public-key-credential①⑥">public key credential</a> can only be used for <a data-link-type="dfn" href="#authentication" id="ref-for-authentication⑨">authentication</a> with the same entity (as identified by <a data-link-type="dfn" href="#rp-id" id="ref-for-rp-id③">RP ID</a>) it was registered with.</p>
+     <p>In the context of the <a data-link-type="dfn" href="#web-authentication-api" id="ref-for-web-authentication-api⑧">WebAuthn API</a>, a <a data-link-type="dfn" href="#relying-party-identifier" id="ref-for-relying-party-identifier①">relying party identifier</a> is a <a data-link-type="dfn" href="https://url.spec.whatwg.org/#valid-domain-string" id="ref-for-valid-domain-string">valid domain string</a> identifying the <a data-link-type="dfn" href="#webauthn-relying-party" id="ref-for-webauthn-relying-party⑧">WebAuthn Relying Party</a> on whose behalf a given <a data-link-type="dfn" href="#registration" id="ref-for-registration①⑤">registration</a> or <a data-link-type="dfn" href="#authentication" id="ref-for-authentication⑧">authentication ceremony</a> is being performed. A <a data-link-type="dfn" href="#public-key-credential" id="ref-for-public-key-credential①⑥">public key credential</a> can only be used for <a data-link-type="dfn" href="#authentication" id="ref-for-authentication⑨">authentication</a> with the same entity (as identified by <a data-link-type="dfn" href="#rp-id" id="ref-for-rp-id③">RP ID</a>) it was registered with.</p>
      <p>By default, the <a data-link-type="dfn" href="#rp-id" id="ref-for-rp-id④">RP ID</a> for a
 WebAuthn operation is set to the caller’s <a data-link-type="dfn" href="https://html.spec.whatwg.org/multipage/webappapis.html#concept-settings-object-origin" id="ref-for-concept-settings-object-origin">origin</a>'s <a data-link-type="dfn" href="https://html.spec.whatwg.org/multipage/origin.html#concept-origin-effective-domain" id="ref-for-concept-origin-effective-domain">effective domain</a>. This default MAY be
 overridden by the caller, as long as the caller-specified <a data-link-type="dfn" href="#rp-id" id="ref-for-rp-id⑤">RP ID</a> value <a data-link-type="dfn" href="https://html.spec.whatwg.org/multipage/origin.html#is-a-registrable-domain-suffix-of-or-is-equal-to" id="ref-for-is-a-registrable-domain-suffix-of-or-is-equal-to①">is a registrable domain suffix of or is equal
@@ -1648,7 +1706,7 @@ <h2 class="heading settled" data-level="4" id="sctn-terminology"><span class="se
        <li data-md>
         <p>The <a data-link-type="dfn" href="#determines-the-set-of-origins-on-which-the-public-key-credential-may-be-exercised" id="ref-for-determines-the-set-of-origins-on-which-the-public-key-credential-may-be-exercised③">origin</a>'s <a data-link-type="dfn" href="https://url.spec.whatwg.org#concept-url-port" id="ref-for-concept-url-port①">port</a> is unrestricted.</p>
       </ul>
-      <p>For example, given a <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party⑥①">Relying Party</a> whose origin is <code>https://login.example.com:1337</code>, then the following <a data-link-type="dfn" href="#rp-id" id="ref-for-rp-id⑨">RP ID</a>s are valid: <code>login.example.com</code> (default) and <code>example.com</code>, but not <code>m.login.example.com</code> and not <code>com</code>.</p>
+      <p>For example, given a <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party⑥⑥">Relying Party</a> whose origin is <code>https://login.example.com:1337</code>, then the following <a data-link-type="dfn" href="#rp-id" id="ref-for-rp-id⑨">RP ID</a>s are valid: <code>login.example.com</code> (default) and <code>example.com</code>, but not <code>m.login.example.com</code> and not <code>com</code>.</p>
       <p>This is done in order to match the behavior of pervasively deployed ambient credentials (e.g., cookies, <a data-link-type="biblio" href="#biblio-rfc6265">[RFC6265]</a>).
     Please note that this is a greater relaxation of "same-origin" restrictions than what <a data-link-type="dfn" href="https://html.spec.whatwg.org/multipage/origin.html#dom-document-domain" id="ref-for-dom-document-domain">document.domain</a>'s setter provides.</p>
       <p>These restrictions on origin values apply to <a data-link-type="dfn" href="#webauthn-client" id="ref-for-webauthn-client⑤">WebAuthn Clients</a>.</p>
@@ -1662,12 +1720,12 @@ <h2 class="heading settled" data-level="4" id="sctn-terminology"><span class="se
 For backwards compatibility purposes, the various <a data-link-type="dfn" href="#web-authentication-api" id="ref-for-web-authentication-api①⓪">WebAuthn API</a> and <a data-link-type="dfn" href="#authenticator-model" id="ref-for-authenticator-model①">Authenticator Model</a> components
 with various forms of <code>resident</code> within their names have not been changed.</p>
      <p>A <a data-link-type="dfn" href="#server-side-public-key-credential-source" id="ref-for-server-side-public-key-credential-source①">Server-side Public Key Credential Source</a>, or <a data-link-type="dfn" href="#server-side-credential" id="ref-for-server-side-credential④">Server-side Credential</a> for short,
-is a <a data-link-type="dfn" href="#public-key-credential-source" id="ref-for-public-key-credential-source②④">public key credential source</a> that is only usable in an <a data-link-type="dfn" href="#authentication-ceremony" id="ref-for-authentication-ceremony④">authentication ceremony</a> when the <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party⑥②">Relying Party</a> supplies its <a data-link-type="dfn" href="#credential-id" id="ref-for-credential-id①②">credential ID</a> in <code class="idl"><a data-link-type="idl" href="https://w3c.github.io/webappsec-credential-management/#dom-credentialscontainer-get" id="ref-for-dom-credentialscontainer-get⑥">navigator.credentials.get()</a></code>'s <code class="idl"><a data-link-type="idl" href="#dom-publickeycredentialrequestoptions-allowcredentials" id="ref-for-dom-publickeycredentialrequestoptions-allowcredentials③">allowCredentials</a></code> argument. This means that the <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party⑥③">Relying Party</a> must
+is a <a data-link-type="dfn" href="#public-key-credential-source" id="ref-for-public-key-credential-source③④">public key credential source</a> that is only usable in an <a data-link-type="dfn" href="#authentication-ceremony" id="ref-for-authentication-ceremony⑤">authentication ceremony</a> when the <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party⑥⑦">Relying Party</a> supplies its <a data-link-type="dfn" href="#credential-id" id="ref-for-credential-id①③">credential ID</a> in <code class="idl"><a data-link-type="idl" href="https://w3c.github.io/webappsec-credential-management/#dom-credentialscontainer-get" id="ref-for-dom-credentialscontainer-get⑥">navigator.credentials.get()</a></code>'s <code class="idl"><a data-link-type="idl" href="#dom-publickeycredentialrequestoptions-allowcredentials" id="ref-for-dom-publickeycredentialrequestoptions-allowcredentials③">allowCredentials</a></code> argument. This means that the <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party⑥⑧">Relying Party</a> must
 manage the credential’s storage and discovery, as well as be able to first identify the user in order to
-discover the <a data-link-type="dfn" href="#credential-id" id="ref-for-credential-id①③">credential IDs</a> to supply in the <code class="idl"><a data-link-type="idl" href="https://w3c.github.io/webappsec-credential-management/#dom-credentialscontainer-get" id="ref-for-dom-credentialscontainer-get⑦">navigator.credentials.get()</a></code> call.</p>
-     <p><a data-link-type="dfn" href="#client-side" id="ref-for-client-side①">Client-side</a> storage of the <a data-link-type="dfn" href="#public-key-credential-source" id="ref-for-public-key-credential-source②⑤">public key credential source</a> is not required for a <a data-link-type="dfn" href="#server-side-credential" id="ref-for-server-side-credential⑤">server-side credential</a>.
+discover the <a data-link-type="dfn" href="#credential-id" id="ref-for-credential-id①④">credential IDs</a> to supply in the <code class="idl"><a data-link-type="idl" href="https://w3c.github.io/webappsec-credential-management/#dom-credentialscontainer-get" id="ref-for-dom-credentialscontainer-get⑦">navigator.credentials.get()</a></code> call.</p>
+     <p><a data-link-type="dfn" href="#client-side" id="ref-for-client-side①">Client-side</a> storage of the <a data-link-type="dfn" href="#public-key-credential-source" id="ref-for-public-key-credential-source③⑤">public key credential source</a> is not required for a <a data-link-type="dfn" href="#server-side-credential" id="ref-for-server-side-credential⑤">server-side credential</a>.
 This is in contrast to a <a data-link-type="dfn" href="#client-side-discoverable-credential" id="ref-for-client-side-discoverable-credential⑤">client-side discoverable credential</a>,
-which instead does not require the user to first be identified in order to provide the user’s <a data-link-type="dfn" href="#credential-id" id="ref-for-credential-id①④">credential ID</a>s
+which instead does not require the user to first be identified in order to provide the user’s <a data-link-type="dfn" href="#credential-id" id="ref-for-credential-id①⑤">credential ID</a>s
 to a <code class="idl"><a data-link-type="idl" href="https://w3c.github.io/webappsec-credential-management/#dom-credentialscontainer-get" id="ref-for-dom-credentialscontainer-get⑧">navigator.credentials.get()</a></code> call.</p>
      <p>See also: <a data-link-type="dfn" href="#server-side-credential-storage-modality" id="ref-for-server-side-credential-storage-modality">server-side credential storage modality</a> and <a data-link-type="dfn" href="#non-discoverable-credential" id="ref-for-non-discoverable-credential①">non-discoverable credential</a>.</p>
     <dt data-md><dfn class="dfn-paneled" data-dfn-type="dfn" data-noexport id="test-of-user-presence">Test of User Presence</dfn>
@@ -1680,27 +1738,27 @@ <h2 class="heading settled" data-level="4" id="sctn-terminology"><span class="se
     <dt data-md><dfn class="dfn-paneled" data-dfn-type="dfn" data-noexport id="user-account">User Account</dfn>
     <dd data-md>
      <p>In the context of this specification,
-a <a data-link-type="dfn" href="#user-account" id="ref-for-user-account②">user account</a> denotes the mapping of a set of <a data-link-type="dfn" href="https://w3c.github.io/webappsec-credential-management/#concept-credential" id="ref-for-concept-credential③">credentials</a> <a data-link-type="biblio" href="#biblio-credential-management-1">[CREDENTIAL-MANAGEMENT-1]</a> to a (sub)set of a <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party⑥④">Relying Party</a>'s resources, as maintained and authorized by the <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party⑥⑤">Relying Party</a>.
-The <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party⑥⑥">Relying Party</a> maps a given <a data-link-type="dfn" href="#public-key-credential" id="ref-for-public-key-credential①⑨">public key credential</a> to a <a data-link-type="dfn" href="#user-account" id="ref-for-user-account③">user account</a> by assigning a <a data-link-type="dfn" href="#user-account" id="ref-for-user-account④">user account</a>-specific value to the credential’s <a data-link-type="dfn" href="#user-handle" id="ref-for-user-handle②">user handle</a>.
+a <a data-link-type="dfn" href="#user-account" id="ref-for-user-account③">user account</a> denotes the mapping of a set of <a data-link-type="dfn" href="https://w3c.github.io/webappsec-credential-management/#concept-credential" id="ref-for-concept-credential③">credentials</a> <a data-link-type="biblio" href="#biblio-credential-management-1">[CREDENTIAL-MANAGEMENT-1]</a> to a (sub)set of a <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party⑥⑨">Relying Party</a>'s resources, as maintained and authorized by the <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party⑦⓪">Relying Party</a>.
+The <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party⑦①">Relying Party</a> maps a given <a data-link-type="dfn" href="#public-key-credential" id="ref-for-public-key-credential①⑨">public key credential</a> to a <a data-link-type="dfn" href="#user-account" id="ref-for-user-account④">user account</a> by assigning a <a data-link-type="dfn" href="#user-account" id="ref-for-user-account⑤">user account</a>-specific value to the credential’s <a data-link-type="dfn" href="#user-handle" id="ref-for-user-handle②">user handle</a> and storing a <a data-link-type="dfn" href="#credential-record" id="ref-for-credential-record④">credential record</a> for the credential in the <a data-link-type="dfn" href="#user-account" id="ref-for-user-account⑥">user account</a>.
 This mapping, the set of credentials, and their authorizations, may evolve over time.
-A given <a data-link-type="dfn" href="#user-account" id="ref-for-user-account⑤">user account</a> might be accessed by one or more natural persons (also known as "users"),
-and one natural person might have access to one or more <a data-link-type="dfn" href="#user-account" id="ref-for-user-account⑥">user accounts</a>,
-depending on actions of the user(s) and the <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party⑥⑦">Relying Party</a>.</p>
+A given <a data-link-type="dfn" href="#user-account" id="ref-for-user-account⑦">user account</a> might be accessed by one or more natural persons (also known as "users"),
+and one natural person might have access to one or more <a data-link-type="dfn" href="#user-account" id="ref-for-user-account⑧">user accounts</a>,
+depending on actions of the user(s) and the <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party⑦②">Relying Party</a>.</p>
     <dt data-md><dfn class="dfn-paneled" data-dfn-type="dfn" data-noexport id="user-consent">User Consent</dfn>
     <dd data-md>
      <p>User consent means the user agrees with what they are being asked, i.e., it encompasses reading and understanding prompts.
-An <a data-link-type="dfn" href="#authorization-gesture" id="ref-for-authorization-gesture①①">authorization gesture</a> is a <a data-link-type="dfn" href="#ceremony" id="ref-for-ceremony⑦">ceremony</a> component often employed to indicate <a data-link-type="dfn" href="#user-consent" id="ref-for-user-consent④">user consent</a>.</p>
+An <a data-link-type="dfn" href="#authorization-gesture" id="ref-for-authorization-gesture①①">authorization gesture</a> is a <a data-link-type="dfn" href="#ceremony" id="ref-for-ceremony⑨">ceremony</a> component often employed to indicate <a data-link-type="dfn" href="#user-consent" id="ref-for-user-consent④">user consent</a>.</p>
     <dt data-md><dfn class="dfn-paneled" data-dfn-type="dfn" data-noexport id="user-handle">User Handle</dfn>
     <dd data-md>
-     <p>A user handle is an identifier for a <a data-link-type="dfn" href="#user-account" id="ref-for-user-account⑦">user account</a>, specified by the <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party⑥⑧">Relying Party</a> as <code><code class="idl"><a data-link-type="idl" href="#dom-publickeycredentialcreationoptions-user" id="ref-for-dom-publickeycredentialcreationoptions-user">user</a></code>.<code class="idl"><a data-link-type="idl" href="#dom-publickeycredentialuserentity-id" id="ref-for-dom-publickeycredentialuserentity-id">id</a></code></code> during <a data-link-type="dfn" href="#registration" id="ref-for-registration①③">registration</a>. <a data-link-type="dfn" href="#discoverable-credential" id="ref-for-discoverable-credential②">Discoverable credentials</a> store this identifier and return it as <code><code class="idl"><a data-link-type="idl" href="#dom-publickeycredential-response" id="ref-for-dom-publickeycredential-response">response</a></code>.<code class="idl"><a data-link-type="idl" href="#dom-authenticatorassertionresponse-userhandle" id="ref-for-dom-authenticatorassertionresponse-userhandle①">userHandle</a></code></code> in <a data-link-type="dfn" href="#authentication-ceremony" id="ref-for-authentication-ceremony⑤">authentication ceremonies</a> started with an <a data-link-type="dfn" href="https://infra.spec.whatwg.org/#list-empty" id="ref-for-list-empty">empty</a> <code><code class="idl"><a data-link-type="idl" href="#dom-publickeycredentialrequestoptions-allowcredentials" id="ref-for-dom-publickeycredentialrequestoptions-allowcredentials④">allowCredentials</a></code></code> argument.</p>
-     <p>The main use of the <a data-link-type="dfn" href="#user-handle" id="ref-for-user-handle③">user handle</a> is to identify the <a data-link-type="dfn" href="#user-account" id="ref-for-user-account⑧">user account</a> in such <a data-link-type="dfn" href="#authentication-ceremony" id="ref-for-authentication-ceremony⑥">authentication ceremonies</a>,
-but the <a data-link-type="dfn" href="#credential-id" id="ref-for-credential-id①⑤">credential ID</a> could be used instead.
+     <p>A user handle is an identifier for a <a data-link-type="dfn" href="#user-account" id="ref-for-user-account⑨">user account</a>, specified by the <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party⑦③">Relying Party</a> as <code><code class="idl"><a data-link-type="idl" href="#dom-publickeycredentialcreationoptions-user" id="ref-for-dom-publickeycredentialcreationoptions-user">user</a></code>.<code class="idl"><a data-link-type="idl" href="#dom-publickeycredentialuserentity-id" id="ref-for-dom-publickeycredentialuserentity-id">id</a></code></code> during <a data-link-type="dfn" href="#registration" id="ref-for-registration①⑥">registration</a>. <a data-link-type="dfn" href="#discoverable-credential" id="ref-for-discoverable-credential②">Discoverable credentials</a> store this identifier and return it as <code><code class="idl"><a data-link-type="idl" href="#dom-publickeycredential-response" id="ref-for-dom-publickeycredential-response">response</a></code>.<code class="idl"><a data-link-type="idl" href="#dom-authenticatorassertionresponse-userhandle" id="ref-for-dom-authenticatorassertionresponse-userhandle①">userHandle</a></code></code> in <a data-link-type="dfn" href="#authentication-ceremony" id="ref-for-authentication-ceremony⑥">authentication ceremonies</a> started with an <a data-link-type="dfn" href="https://infra.spec.whatwg.org/#list-empty" id="ref-for-list-empty">empty</a> <code><code class="idl"><a data-link-type="idl" href="#dom-publickeycredentialrequestoptions-allowcredentials" id="ref-for-dom-publickeycredentialrequestoptions-allowcredentials④">allowCredentials</a></code></code> argument.</p>
+     <p>The main use of the <a data-link-type="dfn" href="#user-handle" id="ref-for-user-handle③">user handle</a> is to identify the <a data-link-type="dfn" href="#user-account" id="ref-for-user-account①⓪">user account</a> in such <a data-link-type="dfn" href="#authentication-ceremony" id="ref-for-authentication-ceremony⑦">authentication ceremonies</a>,
+but the <a data-link-type="dfn" href="#credential-id" id="ref-for-credential-id①⑥">credential ID</a> could be used instead.
 The main differences are
-that the <a data-link-type="dfn" href="#credential-id" id="ref-for-credential-id①⑥">credential ID</a> is chosen by the <a data-link-type="dfn" href="#authenticator" id="ref-for-authenticator⑤③">authenticator</a> and unique for each credential,
-while the <a data-link-type="dfn" href="#user-handle" id="ref-for-user-handle④">user handle</a> is chosen by the <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party⑥⑨">Relying Party</a> and ought to be the same
-for all <a data-link-type="dfn" href="https://w3c.github.io/webappsec-credential-management/#concept-credential" id="ref-for-concept-credential④">credentials</a> registered to the same <a data-link-type="dfn" href="#user-account" id="ref-for-user-account⑨">user account</a>.</p>
-     <p><a data-link-type="dfn" href="#authenticator" id="ref-for-authenticator⑤④">Authenticators</a> <a data-link-type="dfn" href="#authenticator-credentials-map" id="ref-for-authenticator-credentials-map">map</a> pairs of <a data-link-type="dfn" href="#rp-id" id="ref-for-rp-id①①">RP ID</a> and <a data-link-type="dfn" href="#user-handle" id="ref-for-user-handle⑤">user handle</a> to <a data-link-type="dfn" href="#public-key-credential-source" id="ref-for-public-key-credential-source②⑥">public key credential sources</a>.
-As a consequence, an authenticator will store at most one <a data-link-type="dfn" href="#discoverable-credential" id="ref-for-discoverable-credential③">discoverable credential</a> per <a data-link-type="dfn" href="#user-handle" id="ref-for-user-handle⑥">user handle</a> per <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party⑦⓪">Relying Party</a>.</p>
+that the <a data-link-type="dfn" href="#credential-id" id="ref-for-credential-id①⑦">credential ID</a> is chosen by the <a data-link-type="dfn" href="#authenticator" id="ref-for-authenticator⑤③">authenticator</a> and unique for each credential,
+while the <a data-link-type="dfn" href="#user-handle" id="ref-for-user-handle④">user handle</a> is chosen by the <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party⑦④">Relying Party</a> and ought to be the same
+for all <a data-link-type="dfn" href="https://w3c.github.io/webappsec-credential-management/#concept-credential" id="ref-for-concept-credential④">credentials</a> registered to the same <a data-link-type="dfn" href="#user-account" id="ref-for-user-account①①">user account</a>.</p>
+     <p><a data-link-type="dfn" href="#authenticator" id="ref-for-authenticator⑤④">Authenticators</a> <a data-link-type="dfn" href="#authenticator-credentials-map" id="ref-for-authenticator-credentials-map">map</a> pairs of <a data-link-type="dfn" href="#rp-id" id="ref-for-rp-id①①">RP ID</a> and <a data-link-type="dfn" href="#user-handle" id="ref-for-user-handle⑤">user handle</a> to <a data-link-type="dfn" href="#public-key-credential-source" id="ref-for-public-key-credential-source③⑥">public key credential sources</a>.
+As a consequence, an authenticator will store at most one <a data-link-type="dfn" href="#discoverable-credential" id="ref-for-discoverable-credential③">discoverable credential</a> per <a data-link-type="dfn" href="#user-handle" id="ref-for-user-handle⑥">user handle</a> per <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party⑦⑤">Relying Party</a>.</p>
      <p>A user handle is an opaque <a data-link-type="dfn" href="https://infra.spec.whatwg.org/#byte-sequence" id="ref-for-byte-sequence①">byte sequence</a> with a maximum size of 64 bytes, and is not meant to be displayed to the user.
 It MUST NOT contain personally identifying information, see <a href="#sctn-user-handle-privacy">§ 14.6.1 User Handle Contents</a>.</p>
     <dt data-md><dfn class="dfn-paneled" data-dfn-type="dfn" data-noexport id="concept-user-present">User Present</dfn>
@@ -1712,7 +1770,7 @@ <h2 class="heading settled" data-level="4" id="sctn-terminology"><span class="se
      <p>The technical process by which an <a data-link-type="dfn" href="#authenticator" id="ref-for-authenticator⑤⑤">authenticator</a> <em>locally authorizes</em> the invocation of the <a data-link-type="dfn" href="#authenticatormakecredential" id="ref-for-authenticatormakecredential③">authenticatorMakeCredential</a> and <a data-link-type="dfn" href="#authenticatorgetassertion" id="ref-for-authenticatorgetassertion①">authenticatorGetAssertion</a> operations. <a data-link-type="dfn" href="#user-verification" id="ref-for-user-verification⑥">User verification</a> MAY be instigated
 through various <a data-link-type="dfn" href="#authorization-gesture" id="ref-for-authorization-gesture①②">authorization gesture</a> modalities; for example, through a touch plus pin code, password entry, or <a data-link-type="dfn" href="#biometric-recognition" id="ref-for-biometric-recognition②">biometric recognition</a> (e.g., presenting a fingerprint) <a data-link-type="biblio" href="#biblio-isobiometricvocabulary">[ISOBiometricVocabulary]</a>. The intent is to
 distinguish individual users.</p>
-     <p>Note that <a data-link-type="dfn" href="#user-verification" id="ref-for-user-verification⑦">user verification</a> does not give the <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party⑦①">Relying Party</a> a concrete identification of the user,
+     <p>Note that <a data-link-type="dfn" href="#user-verification" id="ref-for-user-verification⑦">user verification</a> does not give the <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party⑦⑥">Relying Party</a> a concrete identification of the user,
 but when 2 or more ceremonies with <a data-link-type="dfn" href="#user-verification" id="ref-for-user-verification⑧">user verification</a> have been done with that <a data-link-type="dfn" href="https://w3c.github.io/webappsec-credential-management/#concept-credential" id="ref-for-concept-credential⑤">credential</a> it expresses that it was the same user that performed all of them.
 The same user might not always be the same natural person, however,
 if multiple natural persons share access to the same <a data-link-type="dfn" href="#authenticator" id="ref-for-authenticator⑤⑥">authenticator</a>.</p>
@@ -1720,7 +1778,7 @@ <h2 class="heading settled" data-level="4" id="sctn-terminology"><span class="se
 and <a data-link-type="dfn" href="#authenticator" id="ref-for-authenticator⑤⑦">authenticator</a>'s capabilities.
 For example, some devices are intended to be used by a single individual,
 yet they may allow multiple natural persons to enroll fingerprints or know the same PIN
-and thus access the same <a data-link-type="dfn" href="#user-account" id="ref-for-user-account①⓪">user account</a>(s) using that device.</p>
+and thus access the same <a data-link-type="dfn" href="#user-account" id="ref-for-user-account①②">user account</a>(s) using that device.</p>
      <div class="note" role="note">
        Note: Invocation of the <a data-link-type="dfn" href="#authenticatormakecredential" id="ref-for-authenticatormakecredential④">authenticatorMakeCredential</a> and <a data-link-type="dfn" href="#authenticatorgetassertion" id="ref-for-authenticatorgetassertion②">authenticatorGetAssertion</a> operations
     implies use of key material managed by the authenticator. 
@@ -1733,8 +1791,8 @@ <h2 class="heading settled" data-level="4" id="sctn-terminology"><span class="se
    </dl>
    <h2 class="heading settled" data-level="5" id="sctn-api"><span class="secno">5. </span><span class="content"><dfn class="dfn-paneled" data-dfn-type="dfn" data-noexport id="web-authentication-api">Web Authentication API</dfn></span><a class="self-link" href="#sctn-api"></a></h2>
    <p>This section normatively specifies the API for creating and using <a data-link-type="dfn" href="#public-key-credential" id="ref-for-public-key-credential②⓪">public key credentials</a>. The basic
-idea is that the credentials belong to the user and are <a data-link-type="dfn" href="#public-key-credential-source-managing-authenticator" id="ref-for-public-key-credential-source-managing-authenticator⑨">managed</a> by a <a data-link-type="dfn" href="#webauthn-authenticator" id="ref-for-webauthn-authenticator③">WebAuthn Authenticator</a>, with which the <a data-link-type="dfn" href="#webauthn-relying-party" id="ref-for-webauthn-relying-party⑨">WebAuthn Relying Party</a> interacts through the <a data-link-type="dfn" href="#client-platform" id="ref-for-client-platform①④">client platform</a>. <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party⑦②">Relying Party</a> scripts can (with the <a data-link-type="dfn" href="#user-consent" id="ref-for-user-consent⑤">user’s consent</a>) request the
-browser to create a new credential for future use by the <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party⑦③">Relying Party</a>. See <a href="#fig-registration">Figure <span class="figure-num-following"></span></a>, below.</p>
+idea is that the credentials belong to the user and are <a data-link-type="dfn" href="#public-key-credential-source-managing-authenticator" id="ref-for-public-key-credential-source-managing-authenticator⑨">managed</a> by a <a data-link-type="dfn" href="#webauthn-authenticator" id="ref-for-webauthn-authenticator③">WebAuthn Authenticator</a>, with which the <a data-link-type="dfn" href="#webauthn-relying-party" id="ref-for-webauthn-relying-party⑨">WebAuthn Relying Party</a> interacts through the <a data-link-type="dfn" href="#client-platform" id="ref-for-client-platform①④">client platform</a>. <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party⑦⑦">Relying Party</a> scripts can (with the <a data-link-type="dfn" href="#user-consent" id="ref-for-user-consent⑤">user’s consent</a>) request the
+browser to create a new credential for future use by the <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party⑦⑧">Relying Party</a>. See <a href="#fig-registration">Figure <span class="figure-num-following"></span></a>, below.</p>
    <figure id="fig-registration">
      <img src="images/webauthn-registration-flow-01.svg"> 
     <figcaption>Registration Flow</figcaption>
@@ -1758,12 +1816,12 @@ <h2 class="heading settled" data-level="5" id="sctn-api"><span class="secno">5.
 a different <a data-link-type="dfn" href="https://html.spec.whatwg.org/multipage/origin.html#concept-origin" id="ref-for-concept-origin⑤">origin</a>, by incorporating the <a data-link-type="dfn" href="https://html.spec.whatwg.org/multipage/origin.html#concept-origin" id="ref-for-concept-origin⑥">origin</a> in its responses. Specifically, as defined in <a href="#sctn-authenticator-ops">§ 6.3 Authenticator Operations</a>,
 the full <a data-link-type="dfn" href="https://html.spec.whatwg.org/multipage/origin.html#concept-origin" id="ref-for-concept-origin⑦">origin</a> of the requester is included, and signed over, in the <a data-link-type="dfn" href="#attestation-object" id="ref-for-attestation-object③">attestation object</a> produced when a new credential
 is created as well as in all assertions produced by WebAuthn credentials.</p>
-   <p>Additionally, to maintain user privacy and prevent malicious <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party⑦④">Relying Parties</a> from probing for the presence of <a data-link-type="dfn" href="#public-key-credential" id="ref-for-public-key-credential②①">public key
-credentials</a> belonging to other <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party⑦⑤">Relying Parties</a>, each <a data-link-type="dfn" href="#public-key-credential" id="ref-for-public-key-credential②②">credential</a> is also <a data-link-type="dfn" href="#scope" id="ref-for-scope⑧">scoped</a> to a <a data-link-type="dfn" href="#relying-party-identifier" id="ref-for-relying-party-identifier③">Relying Party
-Identifier</a>, or <a data-link-type="dfn" href="#rp-id" id="ref-for-rp-id①②">RP ID</a>. This <a data-link-type="dfn" href="#rp-id" id="ref-for-rp-id①③">RP ID</a> is provided by the client to the <a data-link-type="dfn" href="#authenticator" id="ref-for-authenticator⑤⑨">authenticator</a> for all operations, and the <a data-link-type="dfn" href="#authenticator" id="ref-for-authenticator⑥⓪">authenticator</a> ensures that <a data-link-type="dfn" href="#public-key-credential" id="ref-for-public-key-credential②③">credentials</a> created by a <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party⑦⑥">Relying Party</a> can only be used in operations
+   <p>Additionally, to maintain user privacy and prevent malicious <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party⑦⑨">Relying Parties</a> from probing for the presence of <a data-link-type="dfn" href="#public-key-credential" id="ref-for-public-key-credential②①">public key
+credentials</a> belonging to other <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party⑧⓪">Relying Parties</a>, each <a data-link-type="dfn" href="#public-key-credential" id="ref-for-public-key-credential②②">credential</a> is also <a data-link-type="dfn" href="#scope" id="ref-for-scope⑧">scoped</a> to a <a data-link-type="dfn" href="#relying-party-identifier" id="ref-for-relying-party-identifier③">Relying Party
+Identifier</a>, or <a data-link-type="dfn" href="#rp-id" id="ref-for-rp-id①②">RP ID</a>. This <a data-link-type="dfn" href="#rp-id" id="ref-for-rp-id①③">RP ID</a> is provided by the client to the <a data-link-type="dfn" href="#authenticator" id="ref-for-authenticator⑤⑨">authenticator</a> for all operations, and the <a data-link-type="dfn" href="#authenticator" id="ref-for-authenticator⑥⓪">authenticator</a> ensures that <a data-link-type="dfn" href="#public-key-credential" id="ref-for-public-key-credential②③">credentials</a> created by a <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party⑧①">Relying Party</a> can only be used in operations
 requested by the same <a data-link-type="dfn" href="#rp-id" id="ref-for-rp-id①④">RP ID</a>. Separating the <a data-link-type="dfn" href="https://html.spec.whatwg.org/multipage/origin.html#concept-origin" id="ref-for-concept-origin⑧">origin</a> from the <a data-link-type="dfn" href="#rp-id" id="ref-for-rp-id①⑤">RP ID</a> in this way allows the API to be used in cases
-where a single <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party⑦⑦">Relying Party</a> maintains multiple <a data-link-type="dfn" href="https://html.spec.whatwg.org/multipage/origin.html#concept-origin" id="ref-for-concept-origin⑨">origins</a>.</p>
-   <p>The client facilitates these security measures by providing the <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party⑦⑧">Relying Party</a>'s <a data-link-type="dfn" href="https://html.spec.whatwg.org/multipage/origin.html#concept-origin" id="ref-for-concept-origin①⓪">origin</a> and <a data-link-type="dfn" href="#rp-id" id="ref-for-rp-id①⑥">RP ID</a> to the <a data-link-type="dfn" href="#authenticator" id="ref-for-authenticator⑥①">authenticator</a> for
+where a single <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party⑧②">Relying Party</a> maintains multiple <a data-link-type="dfn" href="https://html.spec.whatwg.org/multipage/origin.html#concept-origin" id="ref-for-concept-origin⑨">origins</a>.</p>
+   <p>The client facilitates these security measures by providing the <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party⑧③">Relying Party</a>'s <a data-link-type="dfn" href="https://html.spec.whatwg.org/multipage/origin.html#concept-origin" id="ref-for-concept-origin①⓪">origin</a> and <a data-link-type="dfn" href="#rp-id" id="ref-for-rp-id①⑥">RP ID</a> to the <a data-link-type="dfn" href="#authenticator" id="ref-for-authenticator⑥①">authenticator</a> for
 each operation. Since this is an integral part of the WebAuthn security model, user agents only expose this API to callers in <a data-link-type="dfn" href="https://html.spec.whatwg.org/multipage/webappapis.html#secure-context" id="ref-for-secure-context">secure contexts</a>.
 For web contexts in particular,
 this only includes those accessed via a secure transport (e.g., TLS) established without errors.</p>
@@ -1849,11 +1907,11 @@ <h3 class="heading settled" data-level="5.1" id="iface-pkcredential"><span class
     <dt data-md><dfn class="dfn-paneled idl-code" data-dfn-for="PublicKeyCredential" data-dfn-type="attribute" data-export id="dom-publickeycredential-authenticatorattachment"><code>authenticatorAttachment</code></dfn>, <span> of type <a data-link-type="idl-name" href="https://webidl.spec.whatwg.org/#idl-DOMString" id="ref-for-idl-DOMString②">DOMString</a>, readonly, nullable</span>
     <dd data-md>
      <p>This attribute reports the <a data-link-type="dfn" href="#authenticator-attachment-modality" id="ref-for-authenticator-attachment-modality">authenticator attachment modality</a> in effect at the time the <code class="idl"><a data-link-type="idl" href="https://w3c.github.io/webappsec-credential-management/#dom-credentialscontainer-create" id="ref-for-dom-credentialscontainer-create④">navigator.credentials.create()</a></code> or <code class="idl"><a data-link-type="idl" href="https://w3c.github.io/webappsec-credential-management/#dom-credentialscontainer-get" id="ref-for-dom-credentialscontainer-get①⓪">navigator.credentials.get()</a></code> methods successfully complete.
-The attribute’s value SHOULD be a member of <code class="idl"><a data-link-type="idl" href="#enumdef-authenticatorattachment" id="ref-for-enumdef-authenticatorattachment">AuthenticatorAttachment</a></code>. <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party⑦⑨">Relying Parties</a> SHOULD treat unknown values
+The attribute’s value SHOULD be a member of <code class="idl"><a data-link-type="idl" href="#enumdef-authenticatorattachment" id="ref-for-enumdef-authenticatorattachment">AuthenticatorAttachment</a></code>. <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party⑧④">Relying Parties</a> SHOULD treat unknown values
 as if the value were null.</p>
      <div class="note" role="note">
-       Note: If, as the result of a <a data-link-type="dfn" href="#registration-ceremony" id="ref-for-registration-ceremony③">registration</a> or <a data-link-type="dfn" href="#authentication-ceremony" id="ref-for-authentication-ceremony⑦">authentication ceremony</a>, <code class="idl"><a data-link-type="idl" href="#dom-publickeycredential-authenticatorattachment" id="ref-for-dom-publickeycredential-authenticatorattachment①">authenticatorAttachment</a></code>'s value is "cross-platform" and
-concurrently <code class="idl"><a data-link-type="idl" href="#dom-publickeycredential-isuserverifyingplatformauthenticatoravailable" id="ref-for-dom-publickeycredential-isuserverifyingplatformauthenticatoravailable">isUserVerifyingPlatformAuthenticatorAvailable</a></code> returns <code>true</code>, then the user employed a <a data-link-type="dfn" href="#roaming-authenticators" id="ref-for-roaming-authenticators⑥">roaming authenticator</a> for this <a data-link-type="dfn" href="#ceremony" id="ref-for-ceremony⑧">ceremony</a> while there is an available <a data-link-type="dfn" href="#platform-authenticators" id="ref-for-platform-authenticators⑨">platform authenticator</a>. Thus the <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party⑧⓪">Relying Party</a> has the opportunity to prompt the user to register the available <a data-link-type="dfn" href="#platform-authenticators" id="ref-for-platform-authenticators①⓪">platform authenticator</a>, which may enable more streamlined user experience flows. 
+       Note: If, as the result of a <a data-link-type="dfn" href="#registration-ceremony" id="ref-for-registration-ceremony④">registration</a> or <a data-link-type="dfn" href="#authentication-ceremony" id="ref-for-authentication-ceremony⑧">authentication ceremony</a>, <code class="idl"><a data-link-type="idl" href="#dom-publickeycredential-authenticatorattachment" id="ref-for-dom-publickeycredential-authenticatorattachment①">authenticatorAttachment</a></code>'s value is "cross-platform" and
+concurrently <code class="idl"><a data-link-type="idl" href="#dom-publickeycredential-isuserverifyingplatformauthenticatoravailable" id="ref-for-dom-publickeycredential-isuserverifyingplatformauthenticatoravailable">isUserVerifyingPlatformAuthenticatorAvailable</a></code> returns <code>true</code>, then the user employed a <a data-link-type="dfn" href="#roaming-authenticators" id="ref-for-roaming-authenticators⑥">roaming authenticator</a> for this <a data-link-type="dfn" href="#ceremony" id="ref-for-ceremony①⓪">ceremony</a> while there is an available <a data-link-type="dfn" href="#platform-authenticators" id="ref-for-platform-authenticators⑨">platform authenticator</a>. Thus the <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party⑧⑤">Relying Party</a> has the opportunity to prompt the user to register the available <a data-link-type="dfn" href="#platform-authenticators" id="ref-for-platform-authenticators①⓪">platform authenticator</a>, which may enable more streamlined user experience flows. 
       <p>An <a data-link-type="dfn" href="#authenticator" id="ref-for-authenticator⑥③">authenticator’s</a> <a data-link-type="dfn" href="#authenticator-attachment-modality" id="ref-for-authenticator-attachment-modality①">attachment modality</a> could change over time.
 For example, a mobile phone might at one time only support <a data-link-type="dfn" href="#platform-attachment" id="ref-for-platform-attachment">platform attachment</a> but later receive updates to support <a data-link-type="dfn" href="#cross-platform-attachment" id="ref-for-cross-platform-attachment">cross-platform attachment</a> as well.</p>
      </div>
@@ -1886,14 +1944,14 @@ <h3 class="heading settled" data-level="5.1" id="iface-pkcredential"><span class
     <dt data-md><code class="idl"><a data-link-type="idl" href="#dom-publickeycredential-tojson" id="ref-for-dom-publickeycredential-tojson">toJSON()</a></code>
     <dd data-md>
      <p>This operation returns <code class="idl"><a data-link-type="idl" href="#dictdef-registrationresponsejson" id="ref-for-dictdef-registrationresponsejson">RegistrationResponseJSON</a></code> or <code class="idl"><a data-link-type="idl" href="#dictdef-authenticationresponsejson" id="ref-for-dictdef-authenticationresponsejson">AuthenticationResponseJSON</a></code>,
-which are <a data-link-type="dfn" href="https://webidl.spec.whatwg.org/#dfn-json-types" id="ref-for-dfn-json-types">JSON type</a> representations mirroring <code class="idl"><a data-link-type="idl" href="#publickeycredential" id="ref-for-publickeycredential⑦">PublicKeyCredential</a></code>, suitable for submission to a <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party⑧①">Relying Party</a> server as an <code>application/json</code> payload. The <a data-link-type="dfn" href="#client" id="ref-for-client①⑤">client</a> is in charge of <a href="https://webidl.spec.whatwg.org/#idl-tojson-operation">serializing values to JSON types as usual</a>,
+which are <a data-link-type="dfn" href="https://webidl.spec.whatwg.org/#dfn-json-types" id="ref-for-dfn-json-types">JSON type</a> representations mirroring <code class="idl"><a data-link-type="idl" href="#publickeycredential" id="ref-for-publickeycredential⑦">PublicKeyCredential</a></code>, suitable for submission to a <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party⑧⑥">Relying Party</a> server as an <code>application/json</code> payload. The <a data-link-type="dfn" href="#client" id="ref-for-client①⑤">client</a> is in charge of <a href="https://webidl.spec.whatwg.org/#idl-tojson-operation">serializing values to JSON types as usual</a>,
 but MUST take additional steps to first encode any <code class="idl"><a data-link-type="idl" href="https://webidl.spec.whatwg.org/#idl-ArrayBuffer" id="ref-for-idl-ArrayBuffer②">ArrayBuffer</a></code> values to <code class="idl"><a data-link-type="idl" href="https://webidl.spec.whatwg.org/#idl-DOMString" id="ref-for-idl-DOMString③">DOMString</a></code> values
 using <a data-link-type="dfn" href="#base64url-encoding" id="ref-for-base64url-encoding①">base64url encoding</a>.</p>
      <p>The <code class="idl"><a data-link-type="idl" href="#dom-registrationresponsejson-clientextensionresults" id="ref-for-dom-registrationresponsejson-clientextensionresults">RegistrationResponseJSON.clientExtensionResults</a></code> or <code class="idl"><a data-link-type="idl" href="#dom-authenticationresponsejson-clientextensionresults" id="ref-for-dom-authenticationresponsejson-clientextensionresults">AuthenticationResponseJSON.clientExtensionResults</a></code> member MUST be set to the output of <code class="idl"><a data-link-type="idl" href="#dom-publickeycredential-getclientextensionresults" id="ref-for-dom-publickeycredential-getclientextensionresults①">getClientExtensionResults()</a></code>,
 with any <code class="idl"><a data-link-type="idl" href="https://webidl.spec.whatwg.org/#idl-ArrayBuffer" id="ref-for-idl-ArrayBuffer③">ArrayBuffer</a></code> values encoded to <code class="idl"><a data-link-type="idl" href="https://webidl.spec.whatwg.org/#idl-DOMString" id="ref-for-idl-DOMString④">DOMString</a></code> values using <a data-link-type="dfn" href="#base64url-encoding" id="ref-for-base64url-encoding②">base64url encoding</a>. This MAY include <code class="idl"><a data-link-type="idl" href="https://webidl.spec.whatwg.org/#idl-ArrayBuffer" id="ref-for-idl-ArrayBuffer④">ArrayBuffer</a></code> values from extensions registered
 in the IANA "WebAuthn Extension Identifiers" registry <a data-link-type="biblio" href="#biblio-iana-webauthn-registries">[IANA-WebAuthn-Registries]</a> but not
 defined in <a href="#sctn-extensions">§ 9 WebAuthn Extensions</a>.</p>
-     <p>The <code class="idl"><a data-link-type="idl" href="#dom-authenticatorattestationresponsejson-transports" id="ref-for-dom-authenticatorattestationresponsejson-transports">AuthenticatorAttestationResponseJSON.transports</a></code> member MUST be set to the output of <code class="idl"><a data-link-type="idl" href="#dom-authenticatorattestationresponse-gettransports" id="ref-for-dom-authenticatorattestationresponse-gettransports">getTransports()</a></code>.</p>
+     <p>The <code class="idl"><a data-link-type="idl" href="#dom-authenticatorattestationresponsejson-transports" id="ref-for-dom-authenticatorattestationresponsejson-transports">AuthenticatorAttestationResponseJSON.transports</a></code> member MUST be set to the output of <code class="idl"><a data-link-type="idl" href="#dom-authenticatorattestationresponse-gettransports" id="ref-for-dom-authenticatorattestationresponse-gettransports②">getTransports()</a></code>.</p>
    </dl>
 <pre class="idl highlight def"><c- b>typedef</c-> <a class="idl-code" data-link-type="interface" href="https://webidl.spec.whatwg.org/#idl-DOMString" id="ref-for-idl-DOMString⑤"><c- b>DOMString</c-></a> <dfn class="dfn-paneled idl-code" data-dfn-type="typedef" data-export id="typedefdef-base64urlstring"><code><c- g>Base64URLString</c-></code></dfn>;
 <c- b>typedef</c-> (<a data-link-type="idl-name" href="#dictdef-registrationresponsejson" id="ref-for-dictdef-registrationresponsejson①"><c- n>RegistrationResponseJSON</c-></a> <c- b>or</c-> <a data-link-type="idl-name" href="#dictdef-authenticationresponsejson" id="ref-for-dictdef-authenticationresponsejson①"><c- n>AuthenticationResponseJSON</c-></a>) <dfn class="dfn-paneled idl-code" data-dfn-type="typedef" data-export id="typedefdef-publickeycredentialjson"><code><c- g>PublicKeyCredentialJSON</c-></code></dfn>;
@@ -1944,15 +2002,15 @@ <h3 class="heading settled" data-level="5.1" id="iface-pkcredential"><span class
 "<code class="idl"><a data-link-type="idl" href="https://w3c.github.io/webappsec-credential-management/#dom-credential-discovery-remote" id="ref-for-dom-credential-discovery-remote">remote</a></code>".</p>
     <dt data-md><dfn class="dfn-paneled idl-code" data-dfn-for="PublicKeyCredential" data-dfn-type="attribute" data-export id="dom-publickeycredential-identifier-slot"><code>[[identifier]]</code></dfn>
     <dd data-md>
-     <p>This <a data-link-type="dfn" href="https://tc39.github.io/ecma262/#sec-object-internal-methods-and-internal-slots" id="ref-for-sec-object-internal-methods-and-internal-slots④">internal slot</a> contains the <a data-link-type="dfn" href="#credential-id" id="ref-for-credential-id①⑦">credential ID</a>, chosen by the authenticator.
-The <a data-link-type="dfn" href="#credential-id" id="ref-for-credential-id①⑧">credential ID</a> is used to look up credentials for use, and is therefore expected to be globally unique
+     <p>This <a data-link-type="dfn" href="https://tc39.github.io/ecma262/#sec-object-internal-methods-and-internal-slots" id="ref-for-sec-object-internal-methods-and-internal-slots④">internal slot</a> contains the <a data-link-type="dfn" href="#credential-id" id="ref-for-credential-id①⑧">credential ID</a>, chosen by the authenticator.
+The <a data-link-type="dfn" href="#credential-id" id="ref-for-credential-id①⑨">credential ID</a> is used to look up credentials for use, and is therefore expected to be globally unique
 with high probability across all credentials of the same type, across all authenticators.</p>
      <p class="note" role="note"><span>Note:</span> This API does not constrain
 the format or length of this identifier, except that it MUST be sufficient for the <a data-link-type="dfn" href="#authenticator" id="ref-for-authenticator⑥④">authenticator</a> to uniquely select a key.
 For example, an authenticator without on-board storage may create identifiers containing a <a data-link-type="dfn" href="#credential-private-key" id="ref-for-credential-private-key⑦">credential private key</a> wrapped with a symmetric key that is burned into the authenticator.</p>
     <dt data-md><dfn class="dfn-paneled idl-code" data-dfn-for="PublicKeyCredential" data-dfn-type="attribute" data-export id="dom-publickeycredential-clientextensionsresults-slot"><code>[[clientExtensionsResults]]</code></dfn>
     <dd data-md>
-     <p>This <a data-link-type="dfn" href="https://tc39.github.io/ecma262/#sec-object-internal-methods-and-internal-slots" id="ref-for-sec-object-internal-methods-and-internal-slots⑤">internal slot</a> contains the results of processing client extensions requested by the <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party⑧②">Relying Party</a> upon the <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party⑧③">Relying Party</a>'s invocation of either <code class="idl"><a data-link-type="idl" href="https://w3c.github.io/webappsec-credential-management/#dom-credentialscontainer-create" id="ref-for-dom-credentialscontainer-create⑤">navigator.credentials.create()</a></code> or <code class="idl"><a data-link-type="idl" href="https://w3c.github.io/webappsec-credential-management/#dom-credentialscontainer-get" id="ref-for-dom-credentialscontainer-get①①">navigator.credentials.get()</a></code>.</p>
+     <p>This <a data-link-type="dfn" href="https://tc39.github.io/ecma262/#sec-object-internal-methods-and-internal-slots" id="ref-for-sec-object-internal-methods-and-internal-slots⑤">internal slot</a> contains the results of processing client extensions requested by the <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party⑧⑦">Relying Party</a> upon the <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party⑧⑧">Relying Party</a>'s invocation of either <code class="idl"><a data-link-type="idl" href="https://w3c.github.io/webappsec-credential-management/#dom-credentialscontainer-create" id="ref-for-dom-credentialscontainer-create⑤">navigator.credentials.create()</a></code> or <code class="idl"><a data-link-type="idl" href="https://w3c.github.io/webappsec-credential-management/#dom-credentialscontainer-get" id="ref-for-dom-credentialscontainer-get①①">navigator.credentials.get()</a></code>.</p>
    </dl>
    <p><code class="idl"><a data-link-type="idl" href="#publickeycredential" id="ref-for-publickeycredential①⓪">PublicKeyCredential</a></code>'s <a data-link-type="dfn" href="https://webidl.spec.whatwg.org/#dfn-interface-object" id="ref-for-dfn-interface-object②">interface object</a> inherits <code class="idl"><a data-link-type="idl" href="https://w3c.github.io/webappsec-credential-management/#credential" id="ref-for-credential⑥">Credential</a></code>'s implementation of <code class="idl"><a data-link-type="idl" href="https://w3c.github.io/webappsec-credential-management/#collectfromcredentialstore-origin-options-sameoriginwithancestors" id="ref-for-collectfromcredentialstore-origin-options-sameoriginwithancestors">[[CollectFromCredentialStore]](origin, options, sameOriginWithAncestors)</a></code>, and defines its own
 implementation of <code class="idl"><a data-link-type="idl" href="#dom-publickeycredential-create-slot" id="ref-for-dom-publickeycredential-create-slot①">[[Create]](origin, options, sameOriginWithAncestors)</a></code>, <code class="idl"><a data-link-type="idl" href="#dom-publickeycredential-discoverfromexternalsource-slot" id="ref-for-dom-publickeycredential-discoverfromexternalsource-slot①">[[DiscoverFromExternalSource]](origin, options, sameOriginWithAncestors)</a></code>, and <code class="idl"><a data-link-type="idl" href="https://w3c.github.io/webappsec-credential-management/#store-credential-sameoriginwithancestors" id="ref-for-store-credential-sameoriginwithancestors">[[Store]](credential, sameOriginWithAncestors)</a></code>.</p>
@@ -1972,7 +2030,7 @@ <h4 class="heading settled" data-level="5.1.2" id="sctn-credentialrequestoptions
    <h4 class="heading settled" data-level="5.1.3" id="sctn-createCredential"><span class="secno">5.1.3. </span><span class="content">Create a New Credential - PublicKeyCredential’s <code>[[Create]](origin, options, sameOriginWithAncestors)</code> Method</span><a class="self-link" href="#sctn-createCredential"></a></h4>
    <div data-link-for-hint="PublicKeyCredential/[[Create]](origin, options, sameOriginWithAncestors)">
      <code class="idl"><a data-link-type="idl" href="#publickeycredential" id="ref-for-publickeycredential①①">PublicKeyCredential</a></code>'s <a data-link-type="dfn" href="https://webidl.spec.whatwg.org/#dfn-interface-object" id="ref-for-dfn-interface-object③">interface object</a>'s implementation of the <dfn class="dfn-paneled idl-code" data-dfn-for="PublicKeyCredential" data-dfn-type="method" data-export data-lt="[[Create]](origin, options, sameOriginWithAncestors)" id="dom-publickeycredential-create-slot"><code>[[Create]](origin,
-options, sameOriginWithAncestors)</code></dfn> <a data-link-type="dfn" href="https://tc39.github.io/ecma262/#sec-object-internal-methods-and-internal-slots" id="ref-for-sec-object-internal-methods-and-internal-slots⑥">internal method</a> <a data-link-type="biblio" href="#biblio-credential-management-1">[CREDENTIAL-MANAGEMENT-1]</a> allows <a data-link-type="dfn" href="#webauthn-relying-party" id="ref-for-webauthn-relying-party①①">WebAuthn Relying Party</a> scripts to call <code class="idl"><a data-link-type="idl" href="https://w3c.github.io/webappsec-credential-management/#dom-credentialscontainer-create" id="ref-for-dom-credentialscontainer-create⑦">navigator.credentials.create()</a></code> to request the creation of a new <a data-link-type="dfn" href="#public-key-credential-source" id="ref-for-public-key-credential-source②⑦">public key credential source</a>, <a data-link-type="dfn" href="#bound-credential" id="ref-for-bound-credential⑦">bound</a> to an <a data-link-type="dfn" href="#authenticator" id="ref-for-authenticator⑥⑤">authenticator</a>. This <code class="idl"><a data-link-type="idl" href="https://w3c.github.io/webappsec-credential-management/#dom-credentialscontainer-create" id="ref-for-dom-credentialscontainer-create⑧">navigator.credentials.create()</a></code> operation can be aborted by leveraging the <code class="idl"><a data-link-type="idl" href="https://dom.spec.whatwg.org/#abortcontroller" id="ref-for-abortcontroller">AbortController</a></code>;
+options, sameOriginWithAncestors)</code></dfn> <a data-link-type="dfn" href="https://tc39.github.io/ecma262/#sec-object-internal-methods-and-internal-slots" id="ref-for-sec-object-internal-methods-and-internal-slots⑥">internal method</a> <a data-link-type="biblio" href="#biblio-credential-management-1">[CREDENTIAL-MANAGEMENT-1]</a> allows <a data-link-type="dfn" href="#webauthn-relying-party" id="ref-for-webauthn-relying-party①①">WebAuthn Relying Party</a> scripts to call <code class="idl"><a data-link-type="idl" href="https://w3c.github.io/webappsec-credential-management/#dom-credentialscontainer-create" id="ref-for-dom-credentialscontainer-create⑦">navigator.credentials.create()</a></code> to request the creation of a new <a data-link-type="dfn" href="#public-key-credential-source" id="ref-for-public-key-credential-source③⑦">public key credential source</a>, <a data-link-type="dfn" href="#bound-credential" id="ref-for-bound-credential⑦">bound</a> to an <a data-link-type="dfn" href="#authenticator" id="ref-for-authenticator⑥⑤">authenticator</a>. This <code class="idl"><a data-link-type="idl" href="https://w3c.github.io/webappsec-credential-management/#dom-credentialscontainer-create" id="ref-for-dom-credentialscontainer-create⑧">navigator.credentials.create()</a></code> operation can be aborted by leveraging the <code class="idl"><a data-link-type="idl" href="https://dom.spec.whatwg.org/#abortcontroller" id="ref-for-abortcontroller">AbortController</a></code>;
 see <a href="https://dom.spec.whatwg.org/#abortcontroller-api-integration"><cite>DOM</cite> § 3.3 Using AbortController and AbortSignal objects in APIs</a> for detailed instructions. 
     <p>This <a data-link-type="dfn" href="https://tc39.github.io/ecma262/#sec-object-internal-methods-and-internal-slots" id="ref-for-sec-object-internal-methods-and-internal-slots⑦">internal method</a> accepts three arguments:</p>
     <dl>
@@ -2047,7 +2105,7 @@ <h4 class="heading settled" data-level="5.1.3" id="sctn-createCredential"><span
       <p class="note" role="note"><span>Note:</span> <code><var>options</var>.<code class="idl"><a data-link-type="idl" href="#dom-publickeycredentialcreationoptions-rp" id="ref-for-dom-publickeycredentialcreationoptions-rp④">rp</a></code>.<code class="idl"><a data-link-type="idl" href="#dom-publickeycredentialrpentity-id" id="ref-for-dom-publickeycredentialrpentity-id④">id</a></code></code> represents the
         caller’s <a data-link-type="dfn" href="#rp-id" id="ref-for-rp-id①⑦">RP ID</a>. The <a data-link-type="dfn" href="#rp-id" id="ref-for-rp-id①⑧">RP ID</a> defaults to being the caller’s <a data-link-type="dfn" href="https://html.spec.whatwg.org/multipage/webappapis.html#concept-settings-object-origin" id="ref-for-concept-settings-object-origin③">origin</a>'s <a data-link-type="dfn" href="https://html.spec.whatwg.org/multipage/origin.html#concept-origin-effective-domain" id="ref-for-concept-origin-effective-domain⑦">effective domain</a> unless the caller has explicitly set <code><var>options</var>.<code class="idl"><a data-link-type="idl" href="#dom-publickeycredentialcreationoptions-rp" id="ref-for-dom-publickeycredentialcreationoptions-rp⑤">rp</a></code>.<code class="idl"><a data-link-type="idl" href="#dom-publickeycredentialrpentity-id" id="ref-for-dom-publickeycredentialrpentity-id⑤">id</a></code></code> when calling <code class="idl"><a data-link-type="idl" href="https://w3c.github.io/webappsec-credential-management/#dom-credentialscontainer-create" id="ref-for-dom-credentialscontainer-create①①">create()</a></code>.</p>
      <li data-md>
-      <p>Let <var>credTypesAndPubKeyAlgs</var> be a new <a data-link-type="dfn" href="https://infra.spec.whatwg.org/#list" id="ref-for-list">list</a> whose <a data-link-type="dfn" href="https://infra.spec.whatwg.org/#list-item" id="ref-for-list-item">items</a> are pairs of <code class="idl"><a data-link-type="idl" href="#enumdef-publickeycredentialtype" id="ref-for-enumdef-publickeycredentialtype①">PublicKeyCredentialType</a></code> and
+      <p>Let <var>credTypesAndPubKeyAlgs</var> be a new <a data-link-type="dfn" href="https://infra.spec.whatwg.org/#list" id="ref-for-list">list</a> whose <a data-link-type="dfn" href="https://infra.spec.whatwg.org/#list-item" id="ref-for-list-item①">items</a> are pairs of <code class="idl"><a data-link-type="idl" href="#enumdef-publickeycredentialtype" id="ref-for-enumdef-publickeycredentialtype①">PublicKeyCredentialType</a></code> and
 a <code class="idl"><a data-link-type="idl" href="#typedefdef-cosealgorithmidentifier" id="ref-for-typedefdef-cosealgorithmidentifier">COSEAlgorithmIdentifier</a></code>.</p>
      <li data-md>
       <p>If <code><var>options</var>.<code class="idl"><a data-link-type="idl" href="#dom-publickeycredentialcreationoptions-pubkeycredparams" id="ref-for-dom-publickeycredentialcreationoptions-pubkeycredparams">pubKeyCredParams</a></code></code>’s <a data-link-type="dfn" href="https://infra.spec.whatwg.org/#list-size" id="ref-for-list-size">size</a></p>
@@ -2117,7 +2175,7 @@ <h4 class="heading settled" data-level="5.1.3" id="sctn-createCredential"><span
      <li data-md>
       <p>Let <var>issuedRequests</var> be a new <a data-link-type="dfn" href="https://infra.spec.whatwg.org/#ordered-set" id="ref-for-ordered-set">ordered set</a>.</p>
      <li data-md>
-      <p>Let <var>authenticators</var> represent a value which at any given instant is a <a data-link-type="dfn" href="https://infra.spec.whatwg.org/#ordered-set" id="ref-for-ordered-set①">set</a> of <a data-link-type="dfn" href="#client-platform" id="ref-for-client-platform①⑦">client platform</a>-specific handles, where each <a data-link-type="dfn" href="https://infra.spec.whatwg.org/#list-item" id="ref-for-list-item①">item</a> identifies an <a data-link-type="dfn" href="#authenticator" id="ref-for-authenticator⑥⑥">authenticator</a> presently available on this <a data-link-type="dfn" href="#client-platform" id="ref-for-client-platform①⑧">client platform</a> at that instant.</p>
+      <p>Let <var>authenticators</var> represent a value which at any given instant is a <a data-link-type="dfn" href="https://infra.spec.whatwg.org/#ordered-set" id="ref-for-ordered-set①">set</a> of <a data-link-type="dfn" href="#client-platform" id="ref-for-client-platform①⑦">client platform</a>-specific handles, where each <a data-link-type="dfn" href="https://infra.spec.whatwg.org/#list-item" id="ref-for-list-item②">item</a> identifies an <a data-link-type="dfn" href="#authenticator" id="ref-for-authenticator⑥⑥">authenticator</a> presently available on this <a data-link-type="dfn" href="#client-platform" id="ref-for-client-platform①⑧">client platform</a> at that instant.</p>
       <p class="note" role="note"><span>Note:</span> What qualifies an <a data-link-type="dfn" href="#authenticator" id="ref-for-authenticator⑥⑦">authenticator</a> as "available" is intentionally unspecified; this is meant to represent how <a data-link-type="dfn" href="#authenticator" id="ref-for-authenticator⑥⑧">authenticators</a> can be <a href="https://en.wikipedia.org/w/index.php?title=Hot_plug">hot-plugged</a> into (e.g., via USB)
 or discovered (e.g., via NFC or Bluetooth) by the <a data-link-type="dfn" href="#client" id="ref-for-client①⑧">client</a> by various mechanisms, or permanently built into the <a data-link-type="dfn" href="#client" id="ref-for-client①⑨">client</a>.</p>
      <li data-md>
@@ -2230,10 +2288,10 @@ <h4 class="heading settled" data-level="5.1.3" id="sctn-createCredential"><span
           <p><a data-link-type="dfn" href="https://infra.spec.whatwg.org/#list-iterate" id="ref-for-list-iterate⑤">For each</a> credential descriptor <var>C</var> in <code><var>options</var>.<code class="idl"><a data-link-type="idl" href="#dom-publickeycredentialcreationoptions-excludecredentials" id="ref-for-dom-publickeycredentialcreationoptions-excludecredentials">excludeCredentials</a></code></code>:</p>
           <ol>
            <li data-md>
-            <p>If <code><var>C</var>.<code class="idl"><a data-link-type="idl" href="#dom-publickeycredentialdescriptor-transports" id="ref-for-dom-publickeycredentialdescriptor-transports①">transports</a></code></code> <a data-link-type="dfn" href="https://infra.spec.whatwg.org/#list-is-empty" id="ref-for-list-is-empty③">is not empty</a>, and <var>authenticator</var> is connected over a transport not
-mentioned in <code><var>C</var>.<code class="idl"><a data-link-type="idl" href="#dom-publickeycredentialdescriptor-transports" id="ref-for-dom-publickeycredentialdescriptor-transports②">transports</a></code></code>, the client MAY <a data-link-type="dfn" href="https://infra.spec.whatwg.org/#iteration-continue" id="ref-for-iteration-continue⑧">continue</a>.</p>
+            <p>If <code><var>C</var>.<code class="idl"><a data-link-type="idl" href="#dom-publickeycredentialdescriptor-transports" id="ref-for-dom-publickeycredentialdescriptor-transports②">transports</a></code></code> <a data-link-type="dfn" href="https://infra.spec.whatwg.org/#list-is-empty" id="ref-for-list-is-empty③">is not empty</a>, and <var>authenticator</var> is connected over a transport not
+mentioned in <code><var>C</var>.<code class="idl"><a data-link-type="idl" href="#dom-publickeycredentialdescriptor-transports" id="ref-for-dom-publickeycredentialdescriptor-transports③">transports</a></code></code>, the client MAY <a data-link-type="dfn" href="https://infra.spec.whatwg.org/#iteration-continue" id="ref-for-iteration-continue⑧">continue</a>.</p>
             <p class="note" role="note"><span>Note:</span> If the client chooses to <a data-link-type="dfn" href="https://infra.spec.whatwg.org/#iteration-continue" id="ref-for-iteration-continue⑨">continue</a>, this could result in
-inadvertently registering multiple credentials <a data-link-type="dfn" href="#bound-credential" id="ref-for-bound-credential⑧">bound to</a> the same <a data-link-type="dfn" href="#authenticator" id="ref-for-authenticator⑥⑨">authenticator</a> if the transport hints in <code><var>C</var>.<code class="idl"><a data-link-type="idl" href="#dom-publickeycredentialdescriptor-transports" id="ref-for-dom-publickeycredentialdescriptor-transports③">transports</a></code></code> are not accurate.
+inadvertently registering multiple credentials <a data-link-type="dfn" href="#bound-credential" id="ref-for-bound-credential⑧">bound to</a> the same <a data-link-type="dfn" href="#authenticator" id="ref-for-authenticator⑥⑨">authenticator</a> if the transport hints in <code><var>C</var>.<code class="idl"><a data-link-type="idl" href="#dom-publickeycredentialdescriptor-transports" id="ref-for-dom-publickeycredentialdescriptor-transports④">transports</a></code></code> are not accurate.
 For example, stored transport hints could become inaccurate
 as a result of software upgrades adding new connectivity options.</p>
            <li data-md>
@@ -2270,11 +2328,11 @@ <h4 class="heading settled" data-level="5.1.3" id="sctn-createCredential"><span
           <p>Throw an "<code class="idl"><a data-link-type="idl" href="https://webidl.spec.whatwg.org/#invalidstateerror" id="ref-for-invalidstateerror①">InvalidStateError</a></code>" <code class="idl"><a data-link-type="idl" href="https://webidl.spec.whatwg.org/#idl-DOMException" id="ref-for-idl-DOMException⑦">DOMException</a></code>.</p>
         </ol>
         <p class="note" role="note"><span>Note:</span> This error status is handled separately because the <var>authenticator</var> returns it only if <var>excludeCredentialDescriptorList</var> identifies a credential <a data-link-type="dfn" href="#bound-credential" id="ref-for-bound-credential⑨">bound</a> to the <var>authenticator</var> and the user has <a data-link-type="dfn" href="#user-consent" id="ref-for-user-consent⑥">consented</a> to the operation. Given this explicit consent, it is acceptable for this case to be
-distinguishable to the <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party⑧④">Relying Party</a>.</p>
+distinguishable to the <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party⑧⑨">Relying Party</a>.</p>
        <dt data-md>If any <var>authenticator</var> returns an error status not equivalent to "<code class="idl"><a data-link-type="idl" href="https://webidl.spec.whatwg.org/#invalidstateerror" id="ref-for-invalidstateerror②">InvalidStateError</a></code>",
        <dd data-md>
         <p><a data-link-type="dfn" href="https://infra.spec.whatwg.org/#list-remove" id="ref-for-list-remove⑧">Remove</a> <var>authenticator</var> from <var>issuedRequests</var>.</p>
-        <p class="note" role="note"><span>Note:</span> This case does not imply <a data-link-type="dfn" href="#user-consent" id="ref-for-user-consent⑦">user consent</a> for the operation, so details about the error are hidden from the <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party⑧⑤">Relying Party</a> in order to prevent leak of potentially identifying information. See <a href="#sctn-make-credential-privacy">§ 14.5.1 Registration Ceremony Privacy</a> for
+        <p class="note" role="note"><span>Note:</span> This case does not imply <a data-link-type="dfn" href="#user-consent" id="ref-for-user-consent⑦">user consent</a> for the operation, so details about the error are hidden from the <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party⑨⓪">Relying Party</a> in order to prevent leak of potentially identifying information. See <a href="#sctn-make-credential-privacy">§ 14.5.1 Registration Ceremony Privacy</a> for
 details.</p>
        <dt data-md>If any <var>authenticator</var> indicates success,
        <dd data-md>
@@ -2282,7 +2340,7 @@ <h4 class="heading settled" data-level="5.1.3" id="sctn-createCredential"><span
          <li data-md>
           <p><a data-link-type="dfn" href="https://infra.spec.whatwg.org/#list-remove" id="ref-for-list-remove⑨">Remove</a> <var>authenticator</var> from <var>issuedRequests</var>. This authenticator is now the <dfn class="dfn-paneled" data-dfn-for="create" data-dfn-type="dfn" data-noexport id="create-selected-authenticator">selected authenticator</dfn>.</p>
          <li data-md>
-          <p>Let <var>credentialCreationData</var> be a <a data-link-type="dfn" href="https://infra.spec.whatwg.org/#struct" id="ref-for-struct①">struct</a> whose <a data-link-type="dfn" href="https://infra.spec.whatwg.org/#struct-item" id="ref-for-struct-item②">items</a> are:</p>
+          <p>Let <var>credentialCreationData</var> be a <a data-link-type="dfn" href="https://infra.spec.whatwg.org/#struct" id="ref-for-struct②">struct</a> whose <a data-link-type="dfn" href="https://infra.spec.whatwg.org/#struct-item" id="ref-for-struct-item⑧">items</a> are:</p>
           <dl>
            <dt data-md><code><dfn class="dfn-paneled" data-dfn-for="credentialCreationData" data-dfn-type="dfn" data-noexport id="credentialcreationdata-attestationobjectresult">attestationObjectResult</dfn></code>
            <dd data-md>
@@ -2322,11 +2380,11 @@ <h4 class="heading settled" data-level="5.1.3" id="sctn-createCredential"><span
               </ol>
              <dt data-md><code class="idl"><a data-link-type="idl" href="#dom-attestationconveyancepreference-indirect" id="ref-for-dom-attestationconveyancepreference-indirect">indirect</a></code>
              <dd data-md>
-              <p>The client MAY replace the <a data-link-type="dfn" href="#authdata-attestedcredentialdata-aaguid" id="ref-for-authdata-attestedcredentialdata-aaguid③">AAGUID</a> and <a data-link-type="dfn" href="#attestation-statement" id="ref-for-attestation-statement②">attestation statement</a> with a more privacy-friendly
+              <p>The client MAY replace the <a data-link-type="dfn" href="#authdata-attestedcredentialdata-aaguid" id="ref-for-authdata-attestedcredentialdata-aaguid③">AAGUID</a> and <a data-link-type="dfn" href="#attestation-statement" id="ref-for-attestation-statement③">attestation statement</a> with a more privacy-friendly
 and/or more easily verifiable version of the same data (for example, by employing an <a data-link-type="dfn" href="#anonymization-ca" id="ref-for-anonymization-ca">Anonymization CA</a>).</p>
              <dt data-md><code class="idl"><a data-link-type="idl" href="#dom-attestationconveyancepreference-direct" id="ref-for-dom-attestationconveyancepreference-direct">direct</a></code> or <code class="idl"><a data-link-type="idl" href="#dom-attestationconveyancepreference-enterprise" id="ref-for-dom-attestationconveyancepreference-enterprise①">enterprise</a></code>
              <dd data-md>
-              <p>Convey the <a data-link-type="dfn" href="#authenticator" id="ref-for-authenticator⑦①">authenticator</a>'s <a data-link-type="dfn" href="#authdata-attestedcredentialdata-aaguid" id="ref-for-authdata-attestedcredentialdata-aaguid④">AAGUID</a> and <a data-link-type="dfn" href="#attestation-statement" id="ref-for-attestation-statement③">attestation statement</a>, unaltered, to the <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party⑧⑥">Relying Party</a>.</p>
+              <p>Convey the <a data-link-type="dfn" href="#authenticator" id="ref-for-authenticator⑦①">authenticator</a>'s <a data-link-type="dfn" href="#authdata-attestedcredentialdata-aaguid" id="ref-for-authdata-attestedcredentialdata-aaguid④">AAGUID</a> and <a data-link-type="dfn" href="#attestation-statement" id="ref-for-attestation-statement④">attestation statement</a>, unaltered, to the <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party⑨①">Relying Party</a>.</p>
             </dl>
            <li data-md>
             <p>Let <var>attestationObject</var> be a new <code class="idl"><a data-link-type="idl" href="https://webidl.spec.whatwg.org/#idl-ArrayBuffer" id="ref-for-idl-ArrayBuffer⑤">ArrayBuffer</a></code>, created using <var>global</var>’s <a data-link-type="dfn" href="https://tc39.github.io/ecma262/#sec-arraybuffer-constructor" id="ref-for-sec-arraybuffer-constructor①">%ArrayBuffer%</a>, containing the
@@ -2346,16 +2404,16 @@ <h4 class="heading settled" data-level="5.1.3" id="sctn-createCredential"><span
              <dd data-md>
               <p>A new <code class="idl"><a data-link-type="idl" href="#authenticatorattestationresponse" id="ref-for-authenticatorattestationresponse①">AuthenticatorAttestationResponse</a></code> object associated with <var>global</var> whose fields are:</p>
               <dl>
-               <dt data-md><code class="idl"><a data-link-type="idl" href="#dom-authenticatorresponse-clientdatajson" id="ref-for-dom-authenticatorresponse-clientdatajson">clientDataJSON</a></code>
+               <dt data-md><code class="idl"><a data-link-type="idl" href="#dom-authenticatorresponse-clientdatajson" id="ref-for-dom-authenticatorresponse-clientdatajson①">clientDataJSON</a></code>
                <dd data-md>
                 <p>A new <code class="idl"><a data-link-type="idl" href="https://webidl.spec.whatwg.org/#idl-ArrayBuffer" id="ref-for-idl-ArrayBuffer⑥">ArrayBuffer</a></code>, created using <var>global</var>’s <a data-link-type="dfn" href="https://tc39.github.io/ecma262/#sec-arraybuffer-constructor" id="ref-for-sec-arraybuffer-constructor②">%ArrayBuffer%</a>, containing the bytes of <code><var>credentialCreationData</var>.<a data-link-type="dfn" href="#credentialcreationdata-clientdatajsonresult" id="ref-for-credentialcreationdata-clientdatajsonresult">clientDataJSONResult</a></code>.</p>
-               <dt data-md><code class="idl"><a data-link-type="idl" href="#dom-authenticatorattestationresponse-attestationobject" id="ref-for-dom-authenticatorattestationresponse-attestationobject">attestationObject</a></code>
+               <dt data-md><code class="idl"><a data-link-type="idl" href="#dom-authenticatorattestationresponse-attestationobject" id="ref-for-dom-authenticatorattestationresponse-attestationobject①">attestationObject</a></code>
                <dd data-md>
                 <p><var>attestationObject</var></p>
                <dt data-md><code class="idl"><a data-link-type="idl" href="#dom-authenticatorattestationresponse-transports-slot" id="ref-for-dom-authenticatorattestationresponse-transports-slot">[[transports]]</a></code>
                <dd data-md>
                 <p>A sequence of zero or more unique <code class="idl"><a data-link-type="idl" href="https://webidl.spec.whatwg.org/#idl-DOMString" id="ref-for-idl-DOMString①①">DOMString</a></code>s, in lexicographical order, that the <var>authenticator</var> is believed to support. The values SHOULD be members of <code class="idl"><a data-link-type="idl" href="#enumdef-authenticatortransport" id="ref-for-enumdef-authenticatortransport">AuthenticatorTransport</a></code>, but <a data-link-type="dfn" href="#client-platform" id="ref-for-client-platform①⑨">client platforms</a> MUST ignore unknown values.</p>
-                <p>If a user agent does not wish to divulge this information it MAY substitute an arbitrary sequence designed to preserve privacy. This sequence MUST still be valid, i.e. lexicographically sorted and free of duplicates. For example, it may use the empty sequence. Either way, in this case the user agent takes the risk that <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party⑧⑦">Relying Party</a> behavior may be suboptimal.</p>
+                <p>If a user agent does not wish to divulge this information it MAY substitute an arbitrary sequence designed to preserve privacy. This sequence MUST still be valid, i.e. lexicographically sorted and free of duplicates. For example, it may use the empty sequence. Either way, in this case the user agent takes the risk that <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party⑨②">Relying Party</a> behavior may be suboptimal.</p>
                 <p>If the user agent does not have any transport information, it SHOULD set this field to the empty sequence.</p>
                 <p class="note" role="note"><span>Note:</span> How user agents discover transports supported by a given <a data-link-type="dfn" href="#authenticator" id="ref-for-authenticator⑦②">authenticator</a> is outside the scope of this specification, but may include information from an <a data-link-type="dfn" href="#attestation-certificate" id="ref-for-attestation-certificate②">attestation certificate</a> (for example <a data-link-type="biblio" href="#biblio-fido-transports-ext">[FIDO-Transports-Ext]</a>), metadata communicated in an <a data-link-type="dfn" href="#authenticator" id="ref-for-authenticator⑦③">authenticator</a> protocol such as CTAP2, or special-case knowledge about a <a data-link-type="dfn" href="#platform-authenticators" id="ref-for-platform-authenticators①①">platform authenticator</a>.</p>
               </dl>
@@ -2381,16 +2439,16 @@ <h4 class="heading settled" data-level="5.1.3" id="sctn-createCredential"><span
    </div>
    <h4 class="heading settled" data-level="5.1.4" id="sctn-getAssertion"><span class="secno">5.1.4. </span><span class="content">Use an Existing Credential to Make an Assertion - PublicKeyCredential’s <code>[[Get]](options)</code> Method</span><a class="self-link" href="#sctn-getAssertion"></a></h4>
    <p><a data-link-type="dfn" href="#webauthn-relying-party" id="ref-for-webauthn-relying-party①②">WebAuthn Relying Parties</a> call <code><a data-link-type="idl" href="https://w3c.github.io/webappsec-credential-management/#dom-credentialscontainer-get" id="ref-for-dom-credentialscontainer-get①③">navigator.credentials.get({publicKey:..., ...})</a></code> to
-discover and use an existing <a data-link-type="dfn" href="#public-key-credential" id="ref-for-public-key-credential②⑥">public key credential</a>, with the <a data-link-type="dfn" href="#user-consent" id="ref-for-user-consent⑨">user’s consent</a>. <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party⑧⑧">Relying Party</a> script optionally specifies some criteria
-to indicate what <a data-link-type="dfn" href="#public-key-credential-source" id="ref-for-public-key-credential-source②⑧">public key credential sources</a> are acceptable to it. The <a data-link-type="dfn" href="#client-platform" id="ref-for-client-platform②⓪">client platform</a> locates <a data-link-type="dfn" href="#public-key-credential-source" id="ref-for-public-key-credential-source②⑨">public key credential sources</a> matching the specified criteria, and guides the user to pick one that the script will be allowed to use. The user may choose to
-decline the entire interaction even if a <a data-link-type="dfn" href="#public-key-credential-source" id="ref-for-public-key-credential-source③⓪">public key credential source</a> is present, for example to maintain privacy. If the user picks a <a data-link-type="dfn" href="#public-key-credential-source" id="ref-for-public-key-credential-source③①">public key credential source</a>, the user agent then uses <a href="#sctn-op-get-assertion">§ 6.3.3 The authenticatorGetAssertion Operation</a> to sign a <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party⑧⑨">Relying Party</a>-provided challenge and other collected data into an <a data-link-type="dfn" href="#authentication-assertion" id="ref-for-authentication-assertion⑨">authentication assertion</a>, which is used as a <a data-link-type="dfn" href="https://w3c.github.io/webappsec-credential-management/#concept-credential" id="ref-for-concept-credential⑥">credential</a>.</p>
+discover and use an existing <a data-link-type="dfn" href="#public-key-credential" id="ref-for-public-key-credential②⑥">public key credential</a>, with the <a data-link-type="dfn" href="#user-consent" id="ref-for-user-consent⑨">user’s consent</a>. <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party⑨③">Relying Party</a> script optionally specifies some criteria
+to indicate what <a data-link-type="dfn" href="#public-key-credential-source" id="ref-for-public-key-credential-source③⑧">public key credential sources</a> are acceptable to it. The <a data-link-type="dfn" href="#client-platform" id="ref-for-client-platform②⓪">client platform</a> locates <a data-link-type="dfn" href="#public-key-credential-source" id="ref-for-public-key-credential-source③⑨">public key credential sources</a> matching the specified criteria, and guides the user to pick one that the script will be allowed to use. The user may choose to
+decline the entire interaction even if a <a data-link-type="dfn" href="#public-key-credential-source" id="ref-for-public-key-credential-source④⓪">public key credential source</a> is present, for example to maintain privacy. If the user picks a <a data-link-type="dfn" href="#public-key-credential-source" id="ref-for-public-key-credential-source④①">public key credential source</a>, the user agent then uses <a href="#sctn-op-get-assertion">§ 6.3.3 The authenticatorGetAssertion Operation</a> to sign a <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party⑨④">Relying Party</a>-provided challenge and other collected data into an <a data-link-type="dfn" href="#authentication-assertion" id="ref-for-authentication-assertion⑨">authentication assertion</a>, which is used as a <a data-link-type="dfn" href="https://w3c.github.io/webappsec-credential-management/#concept-credential" id="ref-for-concept-credential⑥">credential</a>.</p>
    <p>The <code class="idl"><a data-link-type="idl" href="https://w3c.github.io/webappsec-credential-management/#dom-credentialscontainer-get" id="ref-for-dom-credentialscontainer-get①④">navigator.credentials.get()</a></code> implementation <a data-link-type="biblio" href="#biblio-credential-management-1">[CREDENTIAL-MANAGEMENT-1]</a> calls <code>PublicKeyCredential.<code class="idl"><a data-link-type="idl" href="#dom-publickeycredential-collectfromcredentialstore-slot" id="ref-for-dom-publickeycredential-collectfromcredentialstore-slot">[[CollectFromCredentialStore]]()</a></code></code> to collect any <a data-link-type="dfn" href="https://w3c.github.io/webappsec-credential-management/#concept-credential" id="ref-for-concept-credential⑦">credentials</a> that
 should be available without <a data-link-type="dfn" href="https://w3c.github.io/webappsec-credential-management/#user-mediated" id="ref-for-user-mediated②">user mediation</a> (roughly, this specification’s <a data-link-type="dfn" href="#authorization-gesture" id="ref-for-authorization-gesture①③">authorization gesture</a>), and if it does not find
 exactly one of those, it then calls <code>PublicKeyCredential.<code class="idl"><a data-link-type="idl" href="#dom-publickeycredential-discoverfromexternalsource-slot" id="ref-for-dom-publickeycredential-discoverfromexternalsource-slot②">[[DiscoverFromExternalSource]]()</a></code></code> to have
-the user select a <a data-link-type="dfn" href="#public-key-credential-source" id="ref-for-public-key-credential-source③②">public key credential source</a>.</p>
+the user select a <a data-link-type="dfn" href="#public-key-credential-source" id="ref-for-public-key-credential-source④②">public key credential source</a>.</p>
    <p>Since this specification requires an <a data-link-type="dfn" href="#authorization-gesture" id="ref-for-authorization-gesture①④">authorization gesture</a> to create any <a data-link-type="dfn" href="#assertion" id="ref-for-assertion①">assertions</a>, the <code>PublicKeyCredential.<dfn class="dfn-paneled idl-code" data-dfn-for="PublicKeyCredential" data-dfn-type="method" data-export id="dom-publickeycredential-collectfromcredentialstore-slot"><code>[[CollectFromCredentialStore]](origin, options, sameOriginWithAncestors)</code></dfn></code> <a data-link-type="dfn" href="https://tc39.github.io/ecma262/#sec-object-internal-methods-and-internal-slots" id="ref-for-sec-object-internal-methods-and-internal-slots⑨">internal method</a> inherits the default behavior of <code class="idl"><a data-link-type="idl" href="https://w3c.github.io/webappsec-credential-management/#collectfromcredentialstore-origin-options-sameoriginwithancestors" id="ref-for-collectfromcredentialstore-origin-options-sameoriginwithancestors①">Credential.[[CollectFromCredentialStore]]()</a></code>, of returning an empty set.</p>
    <p>In general, the user agent SHOULD show some UI to the user to guide them in selecting and authorizing an authenticator with which
-to complete the operation. By setting <code><var>options</var>.<code class="idl"><a data-link-type="idl" href="https://w3c.github.io/webappsec-credential-management/#dom-credentialrequestoptions-mediation" id="ref-for-dom-credentialrequestoptions-mediation①">mediation</a></code></code> to <code class="idl"><a data-link-type="idl" href="https://w3c.github.io/webappsec-credential-management/#dom-credentialmediationrequirement-conditional" id="ref-for-dom-credentialmediationrequirement-conditional④">conditional</a></code>, <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party⑨⓪">Relying Parties</a> can indicate that a prominent modal UI should <i>not</i> be shown <i>unless</i> credentials are discovered. <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party⑨①">Relying Party</a> script SHOULD first check that <code class="idl"><a data-link-type="idl" href="#dom-publickeycredential-isconditionalmediationavailable" id="ref-for-dom-publickeycredential-isconditionalmediationavailable①">isConditionalMediationAvailable()</a></code> returns <code>true</code> in order to avoid
+to complete the operation. By setting <code><var>options</var>.<code class="idl"><a data-link-type="idl" href="https://w3c.github.io/webappsec-credential-management/#dom-credentialrequestoptions-mediation" id="ref-for-dom-credentialrequestoptions-mediation①">mediation</a></code></code> to <code class="idl"><a data-link-type="idl" href="https://w3c.github.io/webappsec-credential-management/#dom-credentialmediationrequirement-conditional" id="ref-for-dom-credentialmediationrequirement-conditional④">conditional</a></code>, <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party⑨⑤">Relying Parties</a> can indicate that a prominent modal UI should <i>not</i> be shown <i>unless</i> credentials are discovered. <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party⑨⑥">Relying Party</a> script SHOULD first check that <code class="idl"><a data-link-type="idl" href="#dom-publickeycredential-isconditionalmediationavailable" id="ref-for-dom-publickeycredential-isconditionalmediationavailable①">isConditionalMediationAvailable()</a></code> returns <code>true</code> in order to avoid
 the possibility of causing a user-visible error to be returned if the user agent does not support <code class="idl"><a data-link-type="idl" href="https://w3c.github.io/webappsec-credential-management/#dom-credentialmediationrequirement-conditional" id="ref-for-dom-credentialmediationrequirement-conditional⑤">conditional</a></code> <a data-link-type="dfn" href="https://w3c.github.io/webappsec-credential-management/#user-mediated" id="ref-for-user-mediated③">user mediation</a>.</p>
    <p>This <code class="idl"><a data-link-type="idl" href="https://w3c.github.io/webappsec-credential-management/#dom-credentialscontainer-get" id="ref-for-dom-credentialscontainer-get①⑤">navigator.credentials.get()</a></code> operation can be aborted by leveraging the <code class="idl"><a data-link-type="idl" href="https://dom.spec.whatwg.org/#abortcontroller" id="ref-for-abortcontroller①">AbortController</a></code>;
 see <a href="https://dom.spec.whatwg.org/#abortcontroller-api-integration"><cite>DOM</cite> § 3.3 Using AbortController and AbortSignal objects in APIs</a> for detailed instructions.</p>
@@ -2522,7 +2580,7 @@ <h5 class="heading settled" data-level="5.1.4.1" id="sctn-discover-from-external
      <li data-md>
       <p>Let <var>savedCredentialIds</var> be a new <a data-link-type="dfn" href="https://infra.spec.whatwg.org/#ordered-map" id="ref-for-ordered-map⑤">map</a>.</p>
      <li data-md>
-      <p>Let <var>authenticators</var> represent a value which at any given instant is a <a data-link-type="dfn" href="https://infra.spec.whatwg.org/#ordered-set" id="ref-for-ordered-set③">set</a> of <a data-link-type="dfn" href="#client-platform" id="ref-for-client-platform②②">client platform</a>-specific handles, where each <a data-link-type="dfn" href="https://infra.spec.whatwg.org/#list-item" id="ref-for-list-item②">item</a> identifies an <a data-link-type="dfn" href="#authenticator" id="ref-for-authenticator⑦④">authenticator</a> presently available on this <a data-link-type="dfn" href="#client-platform" id="ref-for-client-platform②③">client platform</a> at that instant.</p>
+      <p>Let <var>authenticators</var> represent a value which at any given instant is a <a data-link-type="dfn" href="https://infra.spec.whatwg.org/#ordered-set" id="ref-for-ordered-set③">set</a> of <a data-link-type="dfn" href="#client-platform" id="ref-for-client-platform②②">client platform</a>-specific handles, where each <a data-link-type="dfn" href="https://infra.spec.whatwg.org/#list-item" id="ref-for-list-item③">item</a> identifies an <a data-link-type="dfn" href="#authenticator" id="ref-for-authenticator⑦④">authenticator</a> presently available on this <a data-link-type="dfn" href="#client-platform" id="ref-for-client-platform②③">client platform</a> at that instant.</p>
       <p class="note" role="note"><span>Note:</span> What qualifies an <a data-link-type="dfn" href="#authenticator" id="ref-for-authenticator⑦⑤">authenticator</a> as "available" is intentionally unspecified; this is meant to represent how <a data-link-type="dfn" href="#authenticator" id="ref-for-authenticator⑦⑥">authenticators</a> can be <a href="https://en.wikipedia.org/w/index.php?title=Hot_plug">hot-plugged</a> into (e.g., via USB)
 or discovered (e.g., via NFC or Bluetooth) by the <a data-link-type="dfn" href="#client" id="ref-for-client②③">client</a> by various mechanisms, or permanently built into the <a data-link-type="dfn" href="#client" id="ref-for-client②④">client</a>.</p>
      <li data-md>
@@ -2562,7 +2620,7 @@ <h5 class="heading settled" data-level="5.1.4.1" id="sctn-discover-from-external
               <p>Let <var>authenticator</var> be the value of <var>silentlyDiscoveredCredentials</var>[<var>credentialMetadata</var>].</p>
              <li data-md>
               <p>Set <code><var>publicKeyOptions</var>.<code class="idl"><a data-link-type="idl" href="#dom-publickeycredentialrequestoptions-allowcredentials" id="ref-for-dom-publickeycredentialrequestoptions-allowcredentials⑥">allowCredentials</a></code></code> to be a <a data-link-type="dfn" href="https://infra.spec.whatwg.org/#list" id="ref-for-list②">list</a> containing a
-single <code class="idl"><a data-link-type="idl" href="#dictdef-publickeycredentialdescriptor" id="ref-for-dictdef-publickeycredentialdescriptor">PublicKeyCredentialDescriptor</a></code> <a data-link-type="dfn" href="https://infra.spec.whatwg.org/#list-item" id="ref-for-list-item③">item</a> whose <code class="idl"><a data-link-type="idl" href="#dom-publickeycredentialdescriptor-id" id="ref-for-dom-publickeycredentialdescriptor-id">id</a></code>'s value is set to <var>credentialMetadata</var>’s <a data-link-type="dfn" href="#discoverablecredentialmetadata-id" id="ref-for-discoverablecredentialmetadata-id">id</a>'s value and whose<code class="idl"><a data-link-type="idl" href="#dom-publickeycredentialdescriptor-id" id="ref-for-dom-publickeycredentialdescriptor-id①">id</a></code> value is set to <var>credentialMetadata</var>’s <a data-link-type="dfn" href="#discoverablecredentialmetadata-type" id="ref-for-discoverablecredentialmetadata-type">type</a>.</p>
+single <code class="idl"><a data-link-type="idl" href="#dictdef-publickeycredentialdescriptor" id="ref-for-dictdef-publickeycredentialdescriptor①">PublicKeyCredentialDescriptor</a></code> <a data-link-type="dfn" href="https://infra.spec.whatwg.org/#list-item" id="ref-for-list-item④">item</a> whose <code class="idl"><a data-link-type="idl" href="#dom-publickeycredentialdescriptor-id" id="ref-for-dom-publickeycredentialdescriptor-id①">id</a></code>'s value is set to <var>credentialMetadata</var>’s <a data-link-type="dfn" href="#discoverablecredentialmetadata-id" id="ref-for-discoverablecredentialmetadata-id">id</a>'s value and whose<code class="idl"><a data-link-type="idl" href="#dom-publickeycredentialdescriptor-id" id="ref-for-dom-publickeycredentialdescriptor-id②">id</a></code> value is set to <var>credentialMetadata</var>’s <a data-link-type="dfn" href="#discoverablecredentialmetadata-type" id="ref-for-discoverablecredentialmetadata-type">type</a>.</p>
              <li data-md>
               <p>Execute the <a data-link-type="dfn" href="#publickeycredential-issuing-a-credential-request-to-an-authenticator" id="ref-for-publickeycredential-issuing-a-credential-request-to-an-authenticator">issuing a credential request to an authenticator</a> algorithm with <var>authenticator</var>, <var>savedCredentialIds</var>, <var>publicKeyOptions</var>, <var>rpId</var>, <var>clientDataHash</var>, and <var>authenticatorExtensions</var>.</p>
               <p>If this returns <code>false</code>, <a data-link-type="dfn" href="https://infra.spec.whatwg.org/#iteration-continue" id="ref-for-iteration-continue①③">continue</a>.</p>
@@ -2575,7 +2633,7 @@ <h5 class="heading settled" data-level="5.1.4.1" id="sctn-discover-from-external
 and no <var>authenticator</var> will become available for any <a data-link-type="dfn" href="#public-key-credential" id="ref-for-public-key-credential②⑧">public key credentials</a> therein,
        <dd data-md>
         <p>Indicate to the user that no eligible credential could be found. When the user acknowledges the dialog, throw a "<code class="idl"><a data-link-type="idl" href="https://webidl.spec.whatwg.org/#notallowederror" id="ref-for-notallowederror⑥">NotAllowedError</a></code>" <code class="idl"><a data-link-type="idl" href="https://webidl.spec.whatwg.org/#idl-DOMException" id="ref-for-idl-DOMException①④">DOMException</a></code>.</p>
-        <p class="note" role="note"><span>Note:</span> One way a <a data-link-type="dfn" href="#client-platform" id="ref-for-client-platform②④">client platform</a> can determine that no <var>authenticator</var> will become available is by examining the <code><code class="idl"><a data-link-type="idl" href="#dom-publickeycredentialdescriptor-transports" id="ref-for-dom-publickeycredentialdescriptor-transports④">transports</a></code></code> members of the present <code><code class="idl"><a data-link-type="idl" href="#dictdef-publickeycredentialdescriptor" id="ref-for-dictdef-publickeycredentialdescriptor①">PublicKeyCredentialDescriptor</a></code></code> <a data-link-type="dfn" href="https://infra.spec.whatwg.org/#list-item" id="ref-for-list-item④">items</a> of <code><var>options</var>.<code class="idl"><a data-link-type="idl" href="#dom-publickeycredentialrequestoptions-allowcredentials" id="ref-for-dom-publickeycredentialrequestoptions-allowcredentials⑧">allowCredentials</a></code></code>, if any. For example, if all <code><code class="idl"><a data-link-type="idl" href="#dictdef-publickeycredentialdescriptor" id="ref-for-dictdef-publickeycredentialdescriptor②">PublicKeyCredentialDescriptor</a></code></code> <a data-link-type="dfn" href="https://infra.spec.whatwg.org/#list-item" id="ref-for-list-item⑤">items</a> list only <code><code class="idl"><a data-link-type="idl" href="#dom-authenticatortransport-internal" id="ref-for-dom-authenticatortransport-internal">internal</a></code></code>, but all <a data-link-type="dfn" href="#platform-authenticators" id="ref-for-platform-authenticators①②">platform</a> <var>authenticator</var>s have been tried, then there is no possibility of satisfying the request. Alternatively, all <code><code class="idl"><a data-link-type="idl" href="#dictdef-publickeycredentialdescriptor" id="ref-for-dictdef-publickeycredentialdescriptor③">PublicKeyCredentialDescriptor</a></code></code> <a data-link-type="dfn" href="https://infra.spec.whatwg.org/#list-item" id="ref-for-list-item⑥">items</a> may list <code><code class="idl"><a data-link-type="idl" href="#dom-publickeycredentialdescriptor-transports" id="ref-for-dom-publickeycredentialdescriptor-transports⑤">transports</a></code></code> that the <a data-link-type="dfn" href="#client-platform" id="ref-for-client-platform②⑤">client platform</a> does not support.</p>
+        <p class="note" role="note"><span>Note:</span> One way a <a data-link-type="dfn" href="#client-platform" id="ref-for-client-platform②④">client platform</a> can determine that no <var>authenticator</var> will become available is by examining the <code><code class="idl"><a data-link-type="idl" href="#dom-publickeycredentialdescriptor-transports" id="ref-for-dom-publickeycredentialdescriptor-transports⑤">transports</a></code></code> members of the present <code><code class="idl"><a data-link-type="idl" href="#dictdef-publickeycredentialdescriptor" id="ref-for-dictdef-publickeycredentialdescriptor②">PublicKeyCredentialDescriptor</a></code></code> <a data-link-type="dfn" href="https://infra.spec.whatwg.org/#list-item" id="ref-for-list-item⑤">items</a> of <code><var>options</var>.<code class="idl"><a data-link-type="idl" href="#dom-publickeycredentialrequestoptions-allowcredentials" id="ref-for-dom-publickeycredentialrequestoptions-allowcredentials⑧">allowCredentials</a></code></code>, if any. For example, if all <code><code class="idl"><a data-link-type="idl" href="#dictdef-publickeycredentialdescriptor" id="ref-for-dictdef-publickeycredentialdescriptor③">PublicKeyCredentialDescriptor</a></code></code> <a data-link-type="dfn" href="https://infra.spec.whatwg.org/#list-item" id="ref-for-list-item⑥">items</a> list only <code><code class="idl"><a data-link-type="idl" href="#dom-authenticatortransport-internal" id="ref-for-dom-authenticatortransport-internal">internal</a></code></code>, but all <a data-link-type="dfn" href="#platform-authenticators" id="ref-for-platform-authenticators①②">platform</a> <var>authenticator</var>s have been tried, then there is no possibility of satisfying the request. Alternatively, all <code><code class="idl"><a data-link-type="idl" href="#dictdef-publickeycredentialdescriptor" id="ref-for-dictdef-publickeycredentialdescriptor④">PublicKeyCredentialDescriptor</a></code></code> <a data-link-type="dfn" href="https://infra.spec.whatwg.org/#list-item" id="ref-for-list-item⑦">items</a> may list <code><code class="idl"><a data-link-type="idl" href="#dom-publickeycredentialdescriptor-transports" id="ref-for-dom-publickeycredentialdescriptor-transports⑥">transports</a></code></code> that the <a data-link-type="dfn" href="#client-platform" id="ref-for-client-platform②⑤">client platform</a> does not support.</p>
        <dt data-md>If an <var>authenticator</var> becomes available on this <a data-link-type="dfn" href="#client-device" id="ref-for-client-device①④">client device</a>,
        <dd data-md>
         <p class="note" role="note"><span>Note:</span> This includes the case where an <var>authenticator</var> was available upon <var>lifetimeTimer</var> initiation.</p>
@@ -2629,18 +2687,18 @@ <h5 class="heading settled" data-level="5.1.4.1" id="sctn-discover-from-external
          <li data-md>
           <p><a data-link-type="dfn" href="https://infra.spec.whatwg.org/#list-remove" id="ref-for-list-remove①⑧">Remove</a> <var>authenticator</var> from <var>issuedRequests</var>.</p>
          <li data-md>
-          <p><span id="assertionCreationDataCreation"></span> Let <var>assertionCreationData</var> be a <a data-link-type="dfn" href="https://infra.spec.whatwg.org/#struct" id="ref-for-struct②">struct</a> whose <a data-link-type="dfn" href="https://infra.spec.whatwg.org/#struct-item" id="ref-for-struct-item③">items</a> are:</p>
+          <p><span id="assertionCreationDataCreation"></span> Let <var>assertionCreationData</var> be a <a data-link-type="dfn" href="https://infra.spec.whatwg.org/#struct" id="ref-for-struct③">struct</a> whose <a data-link-type="dfn" href="https://infra.spec.whatwg.org/#struct-item" id="ref-for-struct-item⑨">items</a> are:</p>
           <dl>
            <dt data-md><code><dfn class="dfn-paneled" data-dfn-for="assertionCreationData" data-dfn-type="dfn" data-noexport id="assertioncreationdata-credentialidresult">credentialIdResult</dfn></code>
            <dd data-md>
             <p>If <code><var>savedCredentialIds</var>[<var>authenticator</var>]</code> exists, set the value of <a data-link-type="dfn" href="#assertioncreationdata-credentialidresult" id="ref-for-assertioncreationdata-credentialidresult">credentialIdResult</a> to be
-the bytes of <code><var>savedCredentialIds</var>[<var>authenticator</var>]</code>. Otherwise, set the value of <a data-link-type="dfn" href="#assertioncreationdata-credentialidresult" id="ref-for-assertioncreationdata-credentialidresult①">credentialIdResult</a> to be the bytes of the <a data-link-type="dfn" href="#credential-id" id="ref-for-credential-id①⑨">credential ID</a> returned from the successful <a data-link-type="dfn" href="#authenticatorgetassertion" id="ref-for-authenticatorgetassertion③">authenticatorGetAssertion</a> operation, as defined in <a href="#sctn-op-get-assertion">§ 6.3.3 The authenticatorGetAssertion Operation</a>.</p>
+the bytes of <code><var>savedCredentialIds</var>[<var>authenticator</var>]</code>. Otherwise, set the value of <a data-link-type="dfn" href="#assertioncreationdata-credentialidresult" id="ref-for-assertioncreationdata-credentialidresult①">credentialIdResult</a> to be the bytes of the <a data-link-type="dfn" href="#credential-id" id="ref-for-credential-id②⓪">credential ID</a> returned from the successful <a data-link-type="dfn" href="#authenticatorgetassertion" id="ref-for-authenticatorgetassertion③">authenticatorGetAssertion</a> operation, as defined in <a href="#sctn-op-get-assertion">§ 6.3.3 The authenticatorGetAssertion Operation</a>.</p>
            <dt data-md><code><dfn class="dfn-paneled" data-dfn-for="assertionCreationData" data-dfn-type="dfn" data-noexport id="assertioncreationdata-clientdatajsonresult">clientDataJSONResult</dfn></code>
            <dd data-md>
             <p>whose value is the bytes of <var>clientDataJSON</var>.</p>
            <dt data-md><code><dfn class="dfn-paneled" data-dfn-for="assertionCreationData" data-dfn-type="dfn" data-noexport id="assertioncreationdata-authenticatordataresult">authenticatorDataResult</dfn></code>
            <dd data-md>
-            <p>whose value is the bytes of the <a data-link-type="dfn" href="#authenticator-data" id="ref-for-authenticator-data③">authenticator data</a> returned by the <a data-link-type="dfn" href="#authenticator" id="ref-for-authenticator⑦⑨">authenticator</a>.</p>
+            <p>whose value is the bytes of the <a data-link-type="dfn" href="#authenticator-data" id="ref-for-authenticator-data⑤">authenticator data</a> returned by the <a data-link-type="dfn" href="#authenticator" id="ref-for-authenticator⑦⑨">authenticator</a>.</p>
            <dt data-md><code><dfn class="dfn-paneled" data-dfn-for="assertionCreationData" data-dfn-type="dfn" data-noexport id="assertioncreationdata-signatureresult">signatureResult</dfn></code>
            <dd data-md>
             <p>whose value is the bytes of the signature value returned by the <a data-link-type="dfn" href="#authenticator" id="ref-for-authenticator⑧⓪">authenticator</a>.</p>
@@ -2668,7 +2726,7 @@ <h5 class="heading settled" data-level="5.1.4.1" id="sctn-discover-from-external
              <dd data-md>
               <p>A new <code class="idl"><a data-link-type="idl" href="#authenticatorassertionresponse" id="ref-for-authenticatorassertionresponse②">AuthenticatorAssertionResponse</a></code> object associated with <var>global</var> whose fields are:</p>
               <dl>
-               <dt data-md><code class="idl"><a data-link-type="idl" href="#dom-authenticatorresponse-clientdatajson" id="ref-for-dom-authenticatorresponse-clientdatajson①">clientDataJSON</a></code>
+               <dt data-md><code class="idl"><a data-link-type="idl" href="#dom-authenticatorresponse-clientdatajson" id="ref-for-dom-authenticatorresponse-clientdatajson②">clientDataJSON</a></code>
                <dd data-md>
                 <p>A new <code class="idl"><a data-link-type="idl" href="https://webidl.spec.whatwg.org/#idl-ArrayBuffer" id="ref-for-idl-ArrayBuffer⑨">ArrayBuffer</a></code>, created using <var>global</var>’s <a data-link-type="dfn" href="https://tc39.github.io/ecma262/#sec-arraybuffer-constructor" id="ref-for-sec-arraybuffer-constructor⑤">%ArrayBuffer%</a>, containing the bytes of <code><var>assertionCreationData</var>.<a data-link-type="dfn" href="#assertioncreationdata-clientdatajsonresult" id="ref-for-assertioncreationdata-clientdatajsonresult">clientDataJSONResult</a></code>.</p>
                <dt data-md><code class="idl"><a data-link-type="idl" href="#dom-authenticatorassertionresponse-authenticatordata" id="ref-for-dom-authenticatorassertionresponse-authenticatordata">authenticatorData</a></code>
@@ -2704,7 +2762,7 @@ <h5 class="heading settled" data-level="5.1.4.1" id="sctn-discover-from-external
    <h5 class="heading settled" data-level="5.1.4.2" id="sctn-issuing-cred-request-to-authenticator"><span class="secno">5.1.4.2. </span><span class="content"><dfn class="dfn-paneled algorithm" data-algorithm="Issuing a credential request to an authenticator" data-dfn-for="PublicKeyCredential" data-dfn-type="dfn" data-noexport id="publickeycredential-issuing-a-credential-request-to-an-authenticator">Issuing a Credential Request to an Authenticator</dfn></span><a class="self-link" href="#sctn-issuing-cred-request-to-authenticator"></a></h5>
    <p>This sub-algorithm of <code class="idl"><a data-link-type="idl" href="#dom-publickeycredential-discoverfromexternalsource-slot" id="ref-for-dom-publickeycredential-discoverfromexternalsource-slot③">[[DiscoverFromExternalSource]]()</a></code> encompasses the specific UI context-independent
 steps necessary for requesting a <a data-link-type="dfn" href="https://w3c.github.io/webappsec-credential-management/#concept-credential" id="ref-for-concept-credential⑧">credential</a> from a given <a data-link-type="dfn" href="#authenticator" id="ref-for-authenticator⑧②">authenticator</a>, using given <code class="idl"><a data-link-type="idl" href="#dictdef-publickeycredentialrequestoptions" id="ref-for-dictdef-publickeycredentialrequestoptions②">PublicKeyCredentialRequestOptions</a></code>.
-It is called by <code class="idl"><a data-link-type="idl" href="#dom-publickeycredential-discoverfromexternalsource-slot" id="ref-for-dom-publickeycredential-discoverfromexternalsource-slot④">[[DiscoverFromExternalSource]]()</a></code> from various points depending on which <a data-link-type="dfn" href="https://w3c.github.io/webappsec-credential-management/#user-mediated" id="ref-for-user-mediated⑤">user mediation</a> the present <a data-link-type="dfn" href="#authentication-ceremony" id="ref-for-authentication-ceremony⑧">authentication ceremony</a> is subject to (e.g.: <code class="idl"><a data-link-type="idl" href="https://w3c.github.io/webappsec-credential-management/#dom-credentialmediationrequirement-conditional" id="ref-for-dom-credentialmediationrequirement-conditional①②">conditional</a></code> mediation).</p>
+It is called by <code class="idl"><a data-link-type="idl" href="#dom-publickeycredential-discoverfromexternalsource-slot" id="ref-for-dom-publickeycredential-discoverfromexternalsource-slot④">[[DiscoverFromExternalSource]]()</a></code> from various points depending on which <a data-link-type="dfn" href="https://w3c.github.io/webappsec-credential-management/#user-mediated" id="ref-for-user-mediated⑤">user mediation</a> the present <a data-link-type="dfn" href="#authentication-ceremony" id="ref-for-authentication-ceremony⑨">authentication ceremony</a> is subject to (e.g.: <code class="idl"><a data-link-type="idl" href="https://w3c.github.io/webappsec-credential-management/#dom-credentialmediationrequirement-conditional" id="ref-for-dom-credentialmediationrequirement-conditional①②">conditional</a></code> mediation).</p>
    <p>This algorithm accepts the following arguments:</p>
    <dl>
     <dt data-md><dfn class="idl-code" data-dfn-for="Issuing a credential request to an authenticator" data-dfn-type="argument" data-export id="dom-issuing-a-credential-request-to-an-authenticator-authenticator"><code>authenticator</code><a class="self-link" href="#dom-issuing-a-credential-request-to-an-authenticator-authenticator"></a></dfn>
@@ -2712,7 +2770,7 @@ <h5 class="heading settled" data-level="5.1.4.2" id="sctn-issuing-cred-request-t
      <p>A <a data-link-type="dfn" href="#client-platform" id="ref-for-client-platform②⑥">client platform</a>-specific handle identifying an <a data-link-type="dfn" href="#authenticator" id="ref-for-authenticator⑧③">authenticator</a> presently available on this <a data-link-type="dfn" href="#client-platform" id="ref-for-client-platform②⑦">client platform</a>.</p>
     <dt data-md><dfn class="idl-code" data-dfn-for="Issuing a credential request to an authenticator" data-dfn-type="argument" data-export id="dom-issuing-a-credential-request-to-an-authenticator-savedcredentialids"><code>savedCredentialIds</code><a class="self-link" href="#dom-issuing-a-credential-request-to-an-authenticator-savedcredentialids"></a></dfn>
     <dd data-md>
-     <p>A <a data-link-type="dfn" href="https://infra.spec.whatwg.org/#ordered-map" id="ref-for-ordered-map⑦">map</a> containing <a data-link-type="dfn" href="#authenticator" id="ref-for-authenticator⑧④">authenticator</a> → <a data-link-type="dfn" href="#credential-id" id="ref-for-credential-id②⓪">credential ID</a>. This argument will be modified in this algorithm.</p>
+     <p>A <a data-link-type="dfn" href="https://infra.spec.whatwg.org/#ordered-map" id="ref-for-ordered-map⑦">map</a> containing <a data-link-type="dfn" href="#authenticator" id="ref-for-authenticator⑧④">authenticator</a> → <a data-link-type="dfn" href="#credential-id" id="ref-for-credential-id②①">credential ID</a>. This argument will be modified in this algorithm.</p>
     <dt data-md><dfn class="idl-code" data-dfn-for="Issuing a credential request to an authenticator" data-dfn-type="argument" data-export id="dom-issuing-a-credential-request-to-an-authenticator-options"><code>options</code><a class="self-link" href="#dom-issuing-a-credential-request-to-an-authenticator-options"></a></dfn>
     <dd data-md>
      <p>This argument is a <code class="idl"><a data-link-type="idl" href="#dictdef-publickeycredentialrequestoptions" id="ref-for-dictdef-publickeycredentialrequestoptions③">PublicKeyCredentialRequestOptions</a></code> object specifying the desired attributes of the <a data-link-type="dfn" href="#public-key-credential" id="ref-for-public-key-credential②⑨">public key credential</a> to discover.</p>
@@ -2764,8 +2822,8 @@ <h5 class="heading settled" data-level="5.1.4.2" id="sctn-issuing-cred-request-t
         <li data-md>
          <p>Let <var>allowCredentialDescriptorList</var> be a new <a data-link-type="dfn" href="https://infra.spec.whatwg.org/#list" id="ref-for-list③">list</a>.</p>
         <li data-md>
-         <p>Execute a <a data-link-type="dfn" href="#client-platform" id="ref-for-client-platform②⑧">client platform</a>-specific procedure to determine which, if any, <a data-link-type="dfn" href="#public-key-credential" id="ref-for-public-key-credential③⓪">public key credentials</a> described by <code><var>options</var>.<code class="idl"><a data-link-type="idl" href="#dom-publickeycredentialrequestoptions-allowcredentials" id="ref-for-dom-publickeycredentialrequestoptions-allowcredentials①⓪">allowCredentials</a></code></code> are <a data-link-type="dfn" href="#bound-credential" id="ref-for-bound-credential①⓪">bound</a> to this <var>authenticator</var>, by matching with <var>rpId</var>, <code><var>options</var>.<code class="idl"><a data-link-type="idl" href="#dom-publickeycredentialrequestoptions-allowcredentials" id="ref-for-dom-publickeycredentialrequestoptions-allowcredentials①①">allowCredentials</a></code>.<code class="idl"><a data-link-type="idl" href="#dom-publickeycredentialdescriptor-id" id="ref-for-dom-publickeycredentialdescriptor-id②">id</a></code></code>,
-and <code><var>options</var>.<code class="idl"><a data-link-type="idl" href="#dom-publickeycredentialrequestoptions-allowcredentials" id="ref-for-dom-publickeycredentialrequestoptions-allowcredentials①②">allowCredentials</a></code>.<code class="idl"><a data-link-type="idl" href="#dom-publickeycredentialdescriptor-type" id="ref-for-dom-publickeycredentialdescriptor-type">type</a></code></code>.
+         <p>Execute a <a data-link-type="dfn" href="#client-platform" id="ref-for-client-platform②⑧">client platform</a>-specific procedure to determine which, if any, <a data-link-type="dfn" href="#public-key-credential" id="ref-for-public-key-credential③⓪">public key credentials</a> described by <code><var>options</var>.<code class="idl"><a data-link-type="idl" href="#dom-publickeycredentialrequestoptions-allowcredentials" id="ref-for-dom-publickeycredentialrequestoptions-allowcredentials①⓪">allowCredentials</a></code></code> are <a data-link-type="dfn" href="#bound-credential" id="ref-for-bound-credential①⓪">bound</a> to this <var>authenticator</var>, by matching with <var>rpId</var>, <code><var>options</var>.<code class="idl"><a data-link-type="idl" href="#dom-publickeycredentialrequestoptions-allowcredentials" id="ref-for-dom-publickeycredentialrequestoptions-allowcredentials①①">allowCredentials</a></code>.<code class="idl"><a data-link-type="idl" href="#dom-publickeycredentialdescriptor-id" id="ref-for-dom-publickeycredentialdescriptor-id③">id</a></code></code>,
+and <code><var>options</var>.<code class="idl"><a data-link-type="idl" href="#dom-publickeycredentialrequestoptions-allowcredentials" id="ref-for-dom-publickeycredentialrequestoptions-allowcredentials①②">allowCredentials</a></code>.<code class="idl"><a data-link-type="idl" href="#dom-publickeycredentialdescriptor-type" id="ref-for-dom-publickeycredentialdescriptor-type①">type</a></code></code>.
 Set <var>allowCredentialDescriptorList</var> to this filtered list.</p>
         <li data-md>
          <p>If <var>allowCredentialDescriptorList</var> <a data-link-type="dfn" href="https://infra.spec.whatwg.org/#list-is-empty" id="ref-for-list-is-empty⑤">is empty</a>, return <code>false</code>.</p>
@@ -2775,8 +2833,8 @@ <h5 class="heading settled" data-level="5.1.4.2" id="sctn-issuing-cred-request-t
          <p>If <var>allowCredentialDescriptorList</var> has exactly one value, set <code><var>savedCredentialIds</var>[<var>authenticator</var>]</code> to <code><var>allowCredentialDescriptorList</var>[0].id</code>’s
 value (see <a href="#authenticatorGetAssertion-return-values">here</a> in <a href="#sctn-op-get-assertion">§ 6.3.3 The authenticatorGetAssertion Operation</a> for more information).</p>
         <li data-md>
-         <p><a data-link-type="dfn" href="https://infra.spec.whatwg.org/#list-iterate" id="ref-for-list-iterate①⑥">For each</a> credential descriptor <var>C</var> in <var>allowCredentialDescriptorList</var>, <a data-link-type="dfn" href="https://infra.spec.whatwg.org/#set-append" id="ref-for-set-append③">append</a> each value, if any, of <code><var>C</var>.<code class="idl"><a data-link-type="idl" href="#dom-publickeycredentialdescriptor-transports" id="ref-for-dom-publickeycredentialdescriptor-transports⑥">transports</a></code></code> to <var>distinctTransports</var>.</p>
-         <p class="note" role="note"><span>Note:</span> This will aggregate only distinct values of <code class="idl"><a data-link-type="idl" href="#dom-publickeycredentialdescriptor-transports" id="ref-for-dom-publickeycredentialdescriptor-transports⑦">transports</a></code> (for this <a data-link-type="dfn" href="#authenticator" id="ref-for-authenticator⑧⑤">authenticator</a>) in <var>distinctTransports</var> due to the properties of <a data-link-type="dfn" href="https://infra.spec.whatwg.org/#ordered-set" id="ref-for-ordered-set⑤">ordered sets</a>.</p>
+         <p><a data-link-type="dfn" href="https://infra.spec.whatwg.org/#list-iterate" id="ref-for-list-iterate①⑥">For each</a> credential descriptor <var>C</var> in <var>allowCredentialDescriptorList</var>, <a data-link-type="dfn" href="https://infra.spec.whatwg.org/#set-append" id="ref-for-set-append③">append</a> each value, if any, of <code><var>C</var>.<code class="idl"><a data-link-type="idl" href="#dom-publickeycredentialdescriptor-transports" id="ref-for-dom-publickeycredentialdescriptor-transports⑦">transports</a></code></code> to <var>distinctTransports</var>.</p>
+         <p class="note" role="note"><span>Note:</span> This will aggregate only distinct values of <code class="idl"><a data-link-type="idl" href="#dom-publickeycredentialdescriptor-transports" id="ref-for-dom-publickeycredentialdescriptor-transports⑧">transports</a></code> (for this <a data-link-type="dfn" href="#authenticator" id="ref-for-authenticator⑧⑤">authenticator</a>) in <var>distinctTransports</var> due to the properties of <a data-link-type="dfn" href="https://infra.spec.whatwg.org/#ordered-set" id="ref-for-ordered-set⑤">ordered sets</a>.</p>
         <li data-md>
          <p>If <var>distinctTransports</var></p>
          <dl class="switch">
@@ -2795,9 +2853,9 @@ <h5 class="heading settled" data-level="5.1.4.2" id="sctn-issuing-cred-request-t
       <dt data-md><a data-link-type="dfn" href="https://infra.spec.whatwg.org/#list-is-empty" id="ref-for-list-is-empty⑧">is empty</a>
       <dd data-md>
        <p>Using local configuration knowledge of the appropriate transport to use with <var>authenticator</var>, invoke the <a data-link-type="dfn" href="#authenticatorgetassertion" id="ref-for-authenticatorgetassertion⑥">authenticatorGetAssertion</a> operation on <var>authenticator</var> with <var>rpId</var>, <var>clientDataHash</var>, <var>userVerification</var> and <var>authenticatorExtensions</var> as parameters.</p>
-       <p class="note" role="note"><span>Note:</span> In this case, the <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party⑨②">Relying Party</a> did not supply a list of acceptable credential descriptors. Thus, the
+       <p class="note" role="note"><span>Note:</span> In this case, the <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party⑨⑦">Relying Party</a> did not supply a list of acceptable credential descriptors. Thus, the
     authenticator is being asked to exercise any credential it may possess that is <a data-link-type="dfn" href="#scope" id="ref-for-scope⑨">scoped</a> to
-    the <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party⑨③">Relying Party</a>, as identified by <var>rpId</var>.</p>
+    the <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party⑨⑧">Relying Party</a>, as identified by <var>rpId</var>.</p>
      </dl>
     <li data-md>
      <p>Return <code>true</code>.</p>
@@ -2835,7 +2893,7 @@ <h4 class="heading settled" data-level="5.1.7" id="sctn-isUserVerifyingPlatformA
 Upon invocation, the <a data-link-type="dfn" href="#client" id="ref-for-client②⑥">client</a> employs a <a data-link-type="dfn" href="#client-platform" id="ref-for-client-platform②⑨">client platform</a>-specific procedure to discover available <a data-link-type="dfn" href="#user-verifying-platform-authenticator" id="ref-for-user-verifying-platform-authenticator④">user-verifying platform authenticators</a>.
 If any are discovered, the promise is resolved with the value of <code>true</code>.
 Otherwise, the promise is resolved with the value of <code>false</code>.
-Based on the result, the <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party⑨④">Relying Party</a> can take further actions to guide the user to create a credential.</p>
+Based on the result, the <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party⑨⑨">Relying Party</a> can take further actions to guide the user to create a credential.</p>
     <p>This method has no arguments and returns a Boolean value.</p>
     <div class="mdn-anno wrapped">
      <button class="mdn-anno-btn"><b class="all-engines-flag" title="This feature is in all current engines.">✔</b><span>MDN</span></button>
@@ -2946,10 +3004,10 @@ <h3 class="heading settled" data-level="5.2" id="iface-authenticatorresponse"><s
      </div>
     </div>
    </div>
-   <p><a data-link-type="dfn" href="#authenticator" id="ref-for-authenticator⑧⑥">Authenticators</a> respond to <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party⑨⑤">Relying Party</a> requests by returning an object derived from the <code class="idl"><a data-link-type="idl" href="#authenticatorresponse" id="ref-for-authenticatorresponse②">AuthenticatorResponse</a></code> interface:</p>
+   <p><a data-link-type="dfn" href="#authenticator" id="ref-for-authenticator⑧⑥">Authenticators</a> respond to <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party①⓪⓪">Relying Party</a> requests by returning an object derived from the <code class="idl"><a data-link-type="idl" href="#authenticatorresponse" id="ref-for-authenticatorresponse②">AuthenticatorResponse</a></code> interface:</p>
 <pre class="idl highlight def">[<a class="idl-code" data-link-type="extended-attribute" href="https://webidl.spec.whatwg.org/#SecureContext" id="ref-for-SecureContext①"><c- g>SecureContext</c-></a>, <a class="idl-code" data-link-type="extended-attribute" href="https://webidl.spec.whatwg.org/#Exposed" id="ref-for-Exposed①"><c- g>Exposed</c-></a>=<c- n>Window</c->]
 <c- b>interface</c-> <a class="idl-code" data-link-type="interface" href="#authenticatorresponse" id="ref-for-authenticatorresponse③"><c- g>AuthenticatorResponse</c-></a> {
-    [<a class="idl-code" data-link-type="extended-attribute" href="https://webidl.spec.whatwg.org/#SameObject" id="ref-for-SameObject③"><c- g>SameObject</c-></a>] <c- b>readonly</c-> <c- b>attribute</c-> <a class="idl-code" data-link-type="interface" href="https://webidl.spec.whatwg.org/#idl-ArrayBuffer" id="ref-for-idl-ArrayBuffer①④"><c- b>ArrayBuffer</c-></a>      <a class="idl-code" data-link-type="attribute" data-readonly data-type="ArrayBuffer" href="#dom-authenticatorresponse-clientdatajson" id="ref-for-dom-authenticatorresponse-clientdatajson②"><c- g>clientDataJSON</c-></a>;
+    [<a class="idl-code" data-link-type="extended-attribute" href="https://webidl.spec.whatwg.org/#SameObject" id="ref-for-SameObject③"><c- g>SameObject</c-></a>] <c- b>readonly</c-> <c- b>attribute</c-> <a class="idl-code" data-link-type="interface" href="https://webidl.spec.whatwg.org/#idl-ArrayBuffer" id="ref-for-idl-ArrayBuffer①④"><c- b>ArrayBuffer</c-></a>      <a class="idl-code" data-link-type="attribute" data-readonly data-type="ArrayBuffer" href="#dom-authenticatorresponse-clientdatajson" id="ref-for-dom-authenticatorresponse-clientdatajson③"><c- g>clientDataJSON</c-></a>;
 };
 </pre>
    <div>
@@ -3015,7 +3073,7 @@ <h4 class="heading settled" data-level="5.2.1" id="iface-authenticatorattestatio
    </div>
 <pre class="idl highlight def">[<a class="idl-code" data-link-type="extended-attribute" href="https://webidl.spec.whatwg.org/#SecureContext" id="ref-for-SecureContext②"><c- g>SecureContext</c-></a>, <a class="idl-code" data-link-type="extended-attribute" href="https://webidl.spec.whatwg.org/#Exposed" id="ref-for-Exposed②"><c- g>Exposed</c-></a>=<c- n>Window</c->]
 <c- b>interface</c-> <a class="idl-code" data-link-type="interface" href="#authenticatorattestationresponse" id="ref-for-authenticatorattestationresponse③"><c- g>AuthenticatorAttestationResponse</c-></a> : <a data-link-type="idl-name" href="#authenticatorresponse" id="ref-for-authenticatorresponse④"><c- n>AuthenticatorResponse</c-></a> {
-    [<a class="idl-code" data-link-type="extended-attribute" href="https://webidl.spec.whatwg.org/#SameObject" id="ref-for-SameObject④"><c- g>SameObject</c-></a>] <c- b>readonly</c-> <c- b>attribute</c-> <a class="idl-code" data-link-type="interface" href="https://webidl.spec.whatwg.org/#idl-ArrayBuffer" id="ref-for-idl-ArrayBuffer①⑥"><c- b>ArrayBuffer</c-></a>      <a class="idl-code" data-link-type="attribute" data-readonly data-type="ArrayBuffer" href="#dom-authenticatorattestationresponse-attestationobject" id="ref-for-dom-authenticatorattestationresponse-attestationobject①"><c- g>attestationObject</c-></a>;
+    [<a class="idl-code" data-link-type="extended-attribute" href="https://webidl.spec.whatwg.org/#SameObject" id="ref-for-SameObject④"><c- g>SameObject</c-></a>] <c- b>readonly</c-> <c- b>attribute</c-> <a class="idl-code" data-link-type="interface" href="https://webidl.spec.whatwg.org/#idl-ArrayBuffer" id="ref-for-idl-ArrayBuffer①⑥"><c- b>ArrayBuffer</c-></a>      <a class="idl-code" data-link-type="attribute" data-readonly data-type="ArrayBuffer" href="#dom-authenticatorattestationresponse-attestationobject" id="ref-for-dom-authenticatorattestationresponse-attestationobject②"><c- g>attestationObject</c-></a>;
     <a data-link-type="dfn" href="https://webidl.spec.whatwg.org/#idl-sequence" id="ref-for-idl-sequence⑤"><c- b>sequence</c-></a>&lt;<a class="idl-code" data-link-type="interface" href="https://webidl.spec.whatwg.org/#idl-DOMString" id="ref-for-idl-DOMString②①"><c- b>DOMString</c-></a>>                              <dfn class="dfn-paneled idl-code" data-dfn-for="AuthenticatorAttestationResponse" data-dfn-type="method" data-export data-lt="getTransports()" id="dom-authenticatorattestationresponse-gettransports"><code><c- g>getTransports</c-></code></dfn>();
     <a class="idl-code" data-link-type="interface" href="https://webidl.spec.whatwg.org/#idl-ArrayBuffer" id="ref-for-idl-ArrayBuffer①⑦"><c- b>ArrayBuffer</c-></a>                                      <dfn class="dfn-paneled idl-code" data-dfn-for="AuthenticatorAttestationResponse" data-dfn-type="method" data-export data-lt="getAuthenticatorData()" id="dom-authenticatorattestationresponse-getauthenticatordata"><code><c- g>getAuthenticatorData</c-></code></dfn>();
     <a class="idl-code" data-link-type="interface" href="https://webidl.spec.whatwg.org/#idl-ArrayBuffer" id="ref-for-idl-ArrayBuffer①⑧"><c- b>ArrayBuffer</c-></a>?                                     <dfn class="dfn-paneled idl-code" data-dfn-for="AuthenticatorAttestationResponse" data-dfn-type="method" data-export data-lt="getPublicKey()" id="dom-authenticatorattestationresponse-getpublickey"><code><c- g>getPublicKey</c-></code></dfn>();
@@ -3024,7 +3082,7 @@ <h4 class="heading settled" data-level="5.2.1" id="iface-authenticatorattestatio
 </pre>
    <div>
     <dl>
-     <dt data-md><code class="idl"><a data-link-type="idl" href="#dom-authenticatorresponse-clientdatajson" id="ref-for-dom-authenticatorresponse-clientdatajson③">clientDataJSON</a></code>
+     <dt data-md><code class="idl"><a data-link-type="idl" href="#dom-authenticatorresponse-clientdatajson" id="ref-for-dom-authenticatorresponse-clientdatajson④">clientDataJSON</a></code>
      <dd data-md>
       <p>This attribute, inherited from <code class="idl"><a data-link-type="idl" href="#authenticatorresponse" id="ref-for-authenticatorresponse⑤">AuthenticatorResponse</a></code>, contains the <a data-link-type="dfn" href="#collectedclientdata-json-compatible-serialization-of-client-data" id="ref-for-collectedclientdata-json-compatible-serialization-of-client-data②">JSON-compatible serialization of client data</a> (see <a href="#sctn-attestation">§ 6.5 Attestation</a>) passed to the authenticator by the client in order to generate this credential. The
 exact JSON serialization MUST be preserved, as the <a data-link-type="dfn" href="#collectedclientdata-hash-of-the-serialized-client-data" id="ref-for-collectedclientdata-hash-of-the-serialized-client-data④">hash of the serialized client data</a> has been computed
@@ -3049,16 +3107,16 @@ <h4 class="heading settled" data-level="5.2.1" id="iface-authenticatorattestatio
       <p><dfn class="dfn-paneled idl-code" data-dfn-for="AuthenticatorAttestationResponse" data-dfn-type="attribute" data-export id="dom-authenticatorattestationresponse-attestationobject"><code>attestationObject</code></dfn>, <span> of type <a data-link-type="idl-name" href="https://webidl.spec.whatwg.org/#idl-ArrayBuffer" id="ref-for-idl-ArrayBuffer①⑨">ArrayBuffer</a>, readonly</span></p>
      <dd data-md>
       <p>This attribute contains an <a data-link-type="dfn" href="#attestation-object" id="ref-for-attestation-object④">attestation object</a>, which is opaque to, and cryptographically protected against
-tampering by, the client. The <a data-link-type="dfn" href="#attestation-object" id="ref-for-attestation-object⑤">attestation object</a> contains both <a data-link-type="dfn" href="#authenticator-data" id="ref-for-authenticator-data④">authenticator data</a> and an <a data-link-type="dfn" href="#attestation-statement" id="ref-for-attestation-statement④">attestation
-statement</a>. The former contains the AAGUID, a unique <a data-link-type="dfn" href="#credential-id" id="ref-for-credential-id②①">credential ID</a>, and the <a data-link-type="dfn" href="#credential-public-key" id="ref-for-credential-public-key①②">credential public key</a>. The
-contents of the <a data-link-type="dfn" href="#attestation-statement" id="ref-for-attestation-statement⑤">attestation statement</a> are determined by the <a data-link-type="dfn" href="#attestation-statement-format" id="ref-for-attestation-statement-format">attestation statement format</a> used by the <a data-link-type="dfn" href="#authenticator" id="ref-for-authenticator⑧⑧">authenticator</a>. It also contains any additional information that the <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party⑨⑥">Relying Party</a>'s server requires to validate the <a data-link-type="dfn" href="#attestation-statement" id="ref-for-attestation-statement⑥">attestation statement</a>, as well as to decode and validate the <a data-link-type="dfn" href="#authenticator-data" id="ref-for-authenticator-data⑤">authenticator data</a> along with the <a data-link-type="dfn" href="#collectedclientdata-json-compatible-serialization-of-client-data" id="ref-for-collectedclientdata-json-compatible-serialization-of-client-data③">JSON-compatible serialization of client data</a>. For more details, see <a href="#sctn-attestation">§ 6.5 Attestation</a>, <a href="#sctn-generating-an-attestation-object">§ 6.5.4 Generating an Attestation Object</a>,
+tampering by, the client. The <a data-link-type="dfn" href="#attestation-object" id="ref-for-attestation-object⑤">attestation object</a> contains both <a data-link-type="dfn" href="#authenticator-data" id="ref-for-authenticator-data⑥">authenticator data</a> and an <a data-link-type="dfn" href="#attestation-statement" id="ref-for-attestation-statement⑤">attestation
+statement</a>. The former contains the AAGUID, a unique <a data-link-type="dfn" href="#credential-id" id="ref-for-credential-id②②">credential ID</a>, and the <a data-link-type="dfn" href="#credential-public-key" id="ref-for-credential-public-key①③">credential public key</a>. The
+contents of the <a data-link-type="dfn" href="#attestation-statement" id="ref-for-attestation-statement⑥">attestation statement</a> are determined by the <a data-link-type="dfn" href="#attestation-statement-format" id="ref-for-attestation-statement-format">attestation statement format</a> used by the <a data-link-type="dfn" href="#authenticator" id="ref-for-authenticator⑧⑧">authenticator</a>. It also contains any additional information that the <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party①⓪①">Relying Party</a>'s server requires to validate the <a data-link-type="dfn" href="#attestation-statement" id="ref-for-attestation-statement⑦">attestation statement</a>, as well as to decode and validate the <a data-link-type="dfn" href="#authenticator-data" id="ref-for-authenticator-data⑦">authenticator data</a> along with the <a data-link-type="dfn" href="#collectedclientdata-json-compatible-serialization-of-client-data" id="ref-for-collectedclientdata-json-compatible-serialization-of-client-data③">JSON-compatible serialization of client data</a>. For more details, see <a href="#sctn-attestation">§ 6.5 Attestation</a>, <a href="#sctn-generating-an-attestation-object">§ 6.5.4 Generating an Attestation Object</a>,
 and <a href="#fig-attStructs">Figure 6</a>.</p>
-     <dt data-md><code class="idl"><a data-link-type="idl" href="#dom-authenticatorattestationresponse-gettransports" id="ref-for-dom-authenticatorattestationresponse-gettransports①">getTransports()</a></code>
+     <dt data-md><code class="idl"><a data-link-type="idl" href="#dom-authenticatorattestationresponse-gettransports" id="ref-for-dom-authenticatorattestationresponse-gettransports③">getTransports()</a></code>
      <dd data-md>
       <p>This operation returns the value of <code class="idl"><a data-link-type="idl" href="#dom-authenticatorattestationresponse-transports-slot" id="ref-for-dom-authenticatorattestationresponse-transports-slot①">[[transports]]</a></code>.</p>
      <dt data-md><code class="idl"><a data-link-type="idl" href="#dom-authenticatorattestationresponse-getauthenticatordata" id="ref-for-dom-authenticatorattestationresponse-getauthenticatordata">getAuthenticatorData()</a></code>
      <dd data-md>
-      <p>This operation returns the <a data-link-type="dfn" href="#authenticator-data" id="ref-for-authenticator-data⑥">authenticator data</a> contained within <code class="idl"><a data-link-type="idl" href="#dom-authenticatorattestationresponse-attestationobject" id="ref-for-dom-authenticatorattestationresponse-attestationobject②">attestationObject</a></code>. See <a href="#sctn-public-key-easy">§ 5.2.1.1 Easily accessing credential data</a>.</p>
+      <p>This operation returns the <a data-link-type="dfn" href="#authenticator-data" id="ref-for-authenticator-data⑧">authenticator data</a> contained within <code class="idl"><a data-link-type="idl" href="#dom-authenticatorattestationresponse-attestationobject" id="ref-for-dom-authenticatorattestationresponse-attestationobject③">attestationObject</a></code>. See <a href="#sctn-public-key-easy">§ 5.2.1.1 Easily accessing credential data</a>.</p>
      <dt data-md><code class="idl"><a data-link-type="idl" href="#dom-authenticatorattestationresponse-getpublickey" id="ref-for-dom-authenticatorattestationresponse-getpublickey">getPublicKey()</a></code>
      <dd data-md>
       <p>This operation returns the DER <a data-link-type="dfn" href="https://tools.ietf.org/html/rfc5280#section-4.1.2.7" id="ref-for-section-4.1.2.7">SubjectPublicKeyInfo</a> of the new credential, or null if this is not available. See <a href="#sctn-public-key-easy">§ 5.2.1.1 Easily accessing credential data</a>.</p>
@@ -3067,14 +3125,14 @@ <h4 class="heading settled" data-level="5.2.1" id="iface-authenticatorattestatio
       <p>This operation returns the <code class="idl"><a data-link-type="idl" href="#typedefdef-cosealgorithmidentifier" id="ref-for-typedefdef-cosealgorithmidentifier③">COSEAlgorithmIdentifier</a></code> of the new credential. See <a href="#sctn-public-key-easy">§ 5.2.1.1 Easily accessing credential data</a>.</p>
      <dt data-md><dfn class="dfn-paneled idl-code" data-dfn-for="AuthenticatorAttestationResponse" data-dfn-type="attribute" data-export id="dom-authenticatorattestationresponse-transports-slot"><code>[[transports]]</code></dfn>
      <dd data-md>
-      <p>This <a data-link-type="dfn" href="https://tc39.github.io/ecma262/#sec-object-internal-methods-and-internal-slots" id="ref-for-sec-object-internal-methods-and-internal-slots①⑤">internal slot</a> contains a sequence of zero or more unique <code class="idl"><a data-link-type="idl" href="https://webidl.spec.whatwg.org/#idl-DOMString" id="ref-for-idl-DOMString②②">DOMString</a></code>s in lexicographical order. These values are the transports that the <a data-link-type="dfn" href="#authenticator" id="ref-for-authenticator⑧⑨">authenticator</a> is believed to support, or an empty sequence if the information is unavailable. The values SHOULD be members of <code class="idl"><a data-link-type="idl" href="#enumdef-authenticatortransport" id="ref-for-enumdef-authenticatortransport①">AuthenticatorTransport</a></code> but <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party⑨⑦">Relying Parties</a> SHOULD accept and store unknown values.</p>
+      <p>This <a data-link-type="dfn" href="https://tc39.github.io/ecma262/#sec-object-internal-methods-and-internal-slots" id="ref-for-sec-object-internal-methods-and-internal-slots①⑤">internal slot</a> contains a sequence of zero or more unique <code class="idl"><a data-link-type="idl" href="https://webidl.spec.whatwg.org/#idl-DOMString" id="ref-for-idl-DOMString②②">DOMString</a></code>s in lexicographical order. These values are the transports that the <a data-link-type="dfn" href="#authenticator" id="ref-for-authenticator⑧⑨">authenticator</a> is believed to support, or an empty sequence if the information is unavailable. The values SHOULD be members of <code class="idl"><a data-link-type="idl" href="#enumdef-authenticatortransport" id="ref-for-enumdef-authenticatortransport①">AuthenticatorTransport</a></code> but <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party①⓪②">Relying Parties</a> SHOULD accept and store unknown values.</p>
     </dl>
    </div>
    <h5 class="heading settled" data-level="5.2.1.1" id="sctn-public-key-easy"><span class="secno">5.2.1.1. </span><span class="content">Easily accessing credential data</span><a class="self-link" href="#sctn-public-key-easy"></a></h5>
-   <p>Every user of the <code class="idl"><a data-link-type="idl" href="#dom-publickeycredential-create-slot" id="ref-for-dom-publickeycredential-create-slot②">[[Create]](origin, options, sameOriginWithAncestors)</a></code> method will need to parse and store the returned <a data-link-type="dfn" href="#credential-public-key" id="ref-for-credential-public-key①③">credential public key</a> in order to verify future <a data-link-type="dfn" href="#authentication-assertion" id="ref-for-authentication-assertion①⓪">authentication assertions</a>. However, the <a data-link-type="dfn" href="#credential-public-key" id="ref-for-credential-public-key①④">credential public key</a> is in <a data-link-type="biblio" href="#biblio-rfc8152">[RFC8152]</a> (COSE) format, inside the <a data-link-type="dfn" href="#authdata-attestedcredentialdata-credentialpublickey" id="ref-for-authdata-attestedcredentialdata-credentialpublickey">credentialPublicKey</a> member of the <a data-link-type="dfn" href="#authdata-attestedcredentialdata" id="ref-for-authdata-attestedcredentialdata①">attestedCredentialData</a>, inside the <a data-link-type="dfn" href="#authenticator-data" id="ref-for-authenticator-data⑦">authenticator data</a>, inside the <a data-link-type="dfn" href="#attestation-object" id="ref-for-attestation-object⑥">attestation object</a> conveyed by <code class="idl"><a data-link-type="idl" href="#authenticatorattestationresponse" id="ref-for-authenticatorattestationresponse④">AuthenticatorAttestationResponse</a></code>.<code class="idl"><a data-link-type="idl" href="#dom-authenticatorattestationresponse-attestationobject" id="ref-for-dom-authenticatorattestationresponse-attestationobject③">attestationObject</a></code>. <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party⑨⑧">Relying Parties</a> wishing to use <a data-link-type="dfn" href="#attestation" id="ref-for-attestation⑥">attestation</a> are obliged to do the work of parsing the <code class="idl"><a data-link-type="idl" href="#dom-authenticatorattestationresponse-attestationobject" id="ref-for-dom-authenticatorattestationresponse-attestationobject④">attestationObject</a></code> and obtaining the <a data-link-type="dfn" href="#credential-public-key" id="ref-for-credential-public-key①⑤">credential public key</a> because that public key copy is the one the <a data-link-type="dfn" href="#authenticator" id="ref-for-authenticator⑨⓪">authenticator</a> <a href="#signing-procedure" id="ref-for-signing-procedure">signed</a>. However, many valid WebAuthn use cases do not require <a data-link-type="dfn" href="#attestation" id="ref-for-attestation⑦">attestation</a>. For those uses, user agents can do the work of parsing, expose the <a data-link-type="dfn" href="#authenticator-data" id="ref-for-authenticator-data⑧">authenticator data</a> directly, and translate the <a data-link-type="dfn" href="#credential-public-key" id="ref-for-credential-public-key①⑥">credential public key</a> into a more convenient format.</p>
-   <p>The <code class="idl"><a data-link-type="idl" href="#dom-authenticatorattestationresponse-getpublickey" id="ref-for-dom-authenticatorattestationresponse-getpublickey①">getPublicKey()</a></code> operation thus returns the <a data-link-type="dfn" href="#credential-public-key" id="ref-for-credential-public-key①⑦">credential public key</a> as a <a data-link-type="dfn" href="https://tools.ietf.org/html/rfc5280#section-4.1.2.7" id="ref-for-section-4.1.2.7①">SubjectPublicKeyInfo</a>. This <code class="idl"><a data-link-type="idl" href="https://webidl.spec.whatwg.org/#idl-ArrayBuffer" id="ref-for-idl-ArrayBuffer②⓪">ArrayBuffer</a></code> can, for example, be passed to Java’s <code>java.security.spec.X509EncodedKeySpec</code>, .NET’s <code>System.Security.Cryptography.ECDsa.ImportSubjectPublicKeyInfo</code>, or Go’s <code>crypto/x509.ParsePKIXPublicKey</code>.</p>
-   <p>Use of <code class="idl"><a data-link-type="idl" href="#dom-authenticatorattestationresponse-getpublickey" id="ref-for-dom-authenticatorattestationresponse-getpublickey②">getPublicKey()</a></code> does impose some limitations: by using <code class="idl"><a data-link-type="idl" href="#dom-publickeycredentialcreationoptions-pubkeycredparams" id="ref-for-dom-publickeycredentialcreationoptions-pubkeycredparams②">pubKeyCredParams</a></code>, a <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party⑨⑨">Relying Party</a> can negotiate with the <a data-link-type="dfn" href="#authenticator" id="ref-for-authenticator⑨①">authenticator</a> to use public key algorithms that the user agent may not understand. However, if the <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party①⓪⓪">Relying Party</a> does so, the user agent will not be able to translate the resulting <a data-link-type="dfn" href="#credential-public-key" id="ref-for-credential-public-key①⑧">credential public key</a> into <a data-link-type="dfn" href="https://tools.ietf.org/html/rfc5280#section-4.1.2.7" id="ref-for-section-4.1.2.7②">SubjectPublicKeyInfo</a> format and the return value of <code class="idl"><a data-link-type="idl" href="#dom-authenticatorattestationresponse-getpublickey" id="ref-for-dom-authenticatorattestationresponse-getpublickey③">getPublicKey()</a></code> will be null.</p>
-   <p>User agents MUST be able to return a non-null value for <code class="idl"><a data-link-type="idl" href="#dom-authenticatorattestationresponse-getpublickey" id="ref-for-dom-authenticatorattestationresponse-getpublickey④">getPublicKey()</a></code> when the <a data-link-type="dfn" href="#credential-public-key" id="ref-for-credential-public-key①⑨">credential public key</a> has a <code class="idl"><a data-link-type="idl" href="#typedefdef-cosealgorithmidentifier" id="ref-for-typedefdef-cosealgorithmidentifier④">COSEAlgorithmIdentifier</a></code> value of:</p>
+   <p>Every user of the <code class="idl"><a data-link-type="idl" href="#dom-publickeycredential-create-slot" id="ref-for-dom-publickeycredential-create-slot②">[[Create]](origin, options, sameOriginWithAncestors)</a></code> method will need to parse and store the returned <a data-link-type="dfn" href="#credential-public-key" id="ref-for-credential-public-key①④">credential public key</a> in order to verify future <a data-link-type="dfn" href="#authentication-assertion" id="ref-for-authentication-assertion①⓪">authentication assertions</a>. However, the <a data-link-type="dfn" href="#credential-public-key" id="ref-for-credential-public-key①⑤">credential public key</a> is in <a data-link-type="biblio" href="#biblio-rfc8152">[RFC8152]</a> (COSE) format, inside the <a data-link-type="dfn" href="#authdata-attestedcredentialdata-credentialpublickey" id="ref-for-authdata-attestedcredentialdata-credentialpublickey">credentialPublicKey</a> member of the <a data-link-type="dfn" href="#authdata-attestedcredentialdata" id="ref-for-authdata-attestedcredentialdata①">attestedCredentialData</a>, inside the <a data-link-type="dfn" href="#authenticator-data" id="ref-for-authenticator-data⑨">authenticator data</a>, inside the <a data-link-type="dfn" href="#attestation-object" id="ref-for-attestation-object⑥">attestation object</a> conveyed by <code class="idl"><a data-link-type="idl" href="#authenticatorattestationresponse" id="ref-for-authenticatorattestationresponse④">AuthenticatorAttestationResponse</a></code>.<code class="idl"><a data-link-type="idl" href="#dom-authenticatorattestationresponse-attestationobject" id="ref-for-dom-authenticatorattestationresponse-attestationobject④">attestationObject</a></code>. <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party①⓪③">Relying Parties</a> wishing to use <a data-link-type="dfn" href="#attestation" id="ref-for-attestation⑥">attestation</a> are obliged to do the work of parsing the <code class="idl"><a data-link-type="idl" href="#dom-authenticatorattestationresponse-attestationobject" id="ref-for-dom-authenticatorattestationresponse-attestationobject⑤">attestationObject</a></code> and obtaining the <a data-link-type="dfn" href="#credential-public-key" id="ref-for-credential-public-key①⑥">credential public key</a> because that public key copy is the one the <a data-link-type="dfn" href="#authenticator" id="ref-for-authenticator⑨⓪">authenticator</a> <a href="#signing-procedure" id="ref-for-signing-procedure">signed</a>. However, many valid WebAuthn use cases do not require <a data-link-type="dfn" href="#attestation" id="ref-for-attestation⑦">attestation</a>. For those uses, user agents can do the work of parsing, expose the <a data-link-type="dfn" href="#authenticator-data" id="ref-for-authenticator-data①⓪">authenticator data</a> directly, and translate the <a data-link-type="dfn" href="#credential-public-key" id="ref-for-credential-public-key①⑦">credential public key</a> into a more convenient format.</p>
+   <p>The <code class="idl"><a data-link-type="idl" href="#dom-authenticatorattestationresponse-getpublickey" id="ref-for-dom-authenticatorattestationresponse-getpublickey①">getPublicKey()</a></code> operation thus returns the <a data-link-type="dfn" href="#credential-public-key" id="ref-for-credential-public-key①⑧">credential public key</a> as a <a data-link-type="dfn" href="https://tools.ietf.org/html/rfc5280#section-4.1.2.7" id="ref-for-section-4.1.2.7①">SubjectPublicKeyInfo</a>. This <code class="idl"><a data-link-type="idl" href="https://webidl.spec.whatwg.org/#idl-ArrayBuffer" id="ref-for-idl-ArrayBuffer②⓪">ArrayBuffer</a></code> can, for example, be passed to Java’s <code>java.security.spec.X509EncodedKeySpec</code>, .NET’s <code>System.Security.Cryptography.ECDsa.ImportSubjectPublicKeyInfo</code>, or Go’s <code>crypto/x509.ParsePKIXPublicKey</code>.</p>
+   <p>Use of <code class="idl"><a data-link-type="idl" href="#dom-authenticatorattestationresponse-getpublickey" id="ref-for-dom-authenticatorattestationresponse-getpublickey②">getPublicKey()</a></code> does impose some limitations: by using <code class="idl"><a data-link-type="idl" href="#dom-publickeycredentialcreationoptions-pubkeycredparams" id="ref-for-dom-publickeycredentialcreationoptions-pubkeycredparams②">pubKeyCredParams</a></code>, a <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party①⓪④">Relying Party</a> can negotiate with the <a data-link-type="dfn" href="#authenticator" id="ref-for-authenticator⑨①">authenticator</a> to use public key algorithms that the user agent may not understand. However, if the <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party①⓪⑤">Relying Party</a> does so, the user agent will not be able to translate the resulting <a data-link-type="dfn" href="#credential-public-key" id="ref-for-credential-public-key①⑨">credential public key</a> into <a data-link-type="dfn" href="https://tools.ietf.org/html/rfc5280#section-4.1.2.7" id="ref-for-section-4.1.2.7②">SubjectPublicKeyInfo</a> format and the return value of <code class="idl"><a data-link-type="idl" href="#dom-authenticatorattestationresponse-getpublickey" id="ref-for-dom-authenticatorattestationresponse-getpublickey③">getPublicKey()</a></code> will be null.</p>
+   <p>User agents MUST be able to return a non-null value for <code class="idl"><a data-link-type="idl" href="#dom-authenticatorattestationresponse-getpublickey" id="ref-for-dom-authenticatorattestationresponse-getpublickey④">getPublicKey()</a></code> when the <a data-link-type="dfn" href="#credential-public-key" id="ref-for-credential-public-key②⓪">credential public key</a> has a <code class="idl"><a data-link-type="idl" href="#typedefdef-cosealgorithmidentifier" id="ref-for-typedefdef-cosealgorithmidentifier④">COSEAlgorithmIdentifier</a></code> value of:</p>
    <ul>
     <li data-md>
      <p>-7 (ES256), where <a data-link-type="dfn" href="https://tools.ietf.org/html/rfc8152#section-7.1" id="ref-for-section-7.1">kty</a> is 2 (with uncompressed points) and <a data-link-type="dfn" href="https://tools.ietf.org/html/rfc8152#section-13.1.1" id="ref-for-section-13.1.1">crv</a> is 1 (P-256).</p>
@@ -3083,9 +3141,9 @@ <h5 class="heading settled" data-level="5.2.1.1" id="sctn-public-key-easy"><span
     <li data-md>
      <p>-8 (EdDSA), where <a data-link-type="dfn" href="https://tools.ietf.org/html/rfc8152#section-13.1.1" id="ref-for-section-13.1.1①">crv</a> is 6 (Ed25519).</p>
    </ul>
-   <p>A <a data-link-type="dfn" href="https://tools.ietf.org/html/rfc5280#section-4.1.2.7" id="ref-for-section-4.1.2.7③">SubjectPublicKeyInfo</a> does not include information about the signing algorithm (for example, which hash function to use) that is included in the COSE public key. To provide this, <code class="idl"><a data-link-type="idl" href="#dom-authenticatorattestationresponse-getpublickeyalgorithm" id="ref-for-dom-authenticatorattestationresponse-getpublickeyalgorithm①">getPublicKeyAlgorithm()</a></code> returns the <code class="idl"><a data-link-type="idl" href="#typedefdef-cosealgorithmidentifier" id="ref-for-typedefdef-cosealgorithmidentifier⑤">COSEAlgorithmIdentifier</a></code> for the <a data-link-type="dfn" href="#credential-public-key" id="ref-for-credential-public-key②⓪">credential public key</a>.</p>
-   <p>To remove the need to parse CBOR at all in many cases, <code class="idl"><a data-link-type="idl" href="#dom-authenticatorattestationresponse-getauthenticatordata" id="ref-for-dom-authenticatorattestationresponse-getauthenticatordata①">getAuthenticatorData()</a></code> returns the <a data-link-type="dfn" href="#authenticator-data" id="ref-for-authenticator-data⑨">authenticator data</a> from <code class="idl"><a data-link-type="idl" href="#dom-authenticatorattestationresponse-attestationobject" id="ref-for-dom-authenticatorattestationresponse-attestationobject⑤">attestationObject</a></code>. The <a data-link-type="dfn" href="#authenticator-data" id="ref-for-authenticator-data①⓪">authenticator data</a> contains other fields that are encoded in a binary format. However, helper functions are not provided to access them because <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party①⓪①">Relying Parties</a> already need to extract those fields when <a href="#sctn-getAssertion">getting an assertion</a>. In contrast to <a href="#sctn-createCredential">credential creation</a>, where signature verification is <a href="#enumdef-attestationconveyancepreference" id="ref-for-enumdef-attestationconveyancepreference">optional</a>, <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party①⓪②">Relying Parties</a> should always be verifying signatures from an assertion and thus must extract fields from the signed <a data-link-type="dfn" href="#authenticator-data" id="ref-for-authenticator-data①①">authenticator data</a>. The same functions used there will also serve during credential creation.</p>
-   <p class="note" role="note"><span>Note:</span> <code class="idl"><a data-link-type="idl" href="#dom-authenticatorattestationresponse-getpublickey" id="ref-for-dom-authenticatorattestationresponse-getpublickey⑤">getPublicKey()</a></code> and <code class="idl"><a data-link-type="idl" href="#dom-authenticatorattestationresponse-getauthenticatordata" id="ref-for-dom-authenticatorattestationresponse-getauthenticatordata②">getAuthenticatorData()</a></code> were only added in level two of this spec. <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party①⓪③">Relying Parties</a> SHOULD use feature detection before using these functions by testing the value of <code>'getPublicKey' in AuthenticatorAttestationResponse.prototype</code>. <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party①⓪④">Relying Parties</a> that require this function to exist may not interoperate with older user-agents.</p>
+   <p>A <a data-link-type="dfn" href="https://tools.ietf.org/html/rfc5280#section-4.1.2.7" id="ref-for-section-4.1.2.7③">SubjectPublicKeyInfo</a> does not include information about the signing algorithm (for example, which hash function to use) that is included in the COSE public key. To provide this, <code class="idl"><a data-link-type="idl" href="#dom-authenticatorattestationresponse-getpublickeyalgorithm" id="ref-for-dom-authenticatorattestationresponse-getpublickeyalgorithm①">getPublicKeyAlgorithm()</a></code> returns the <code class="idl"><a data-link-type="idl" href="#typedefdef-cosealgorithmidentifier" id="ref-for-typedefdef-cosealgorithmidentifier⑤">COSEAlgorithmIdentifier</a></code> for the <a data-link-type="dfn" href="#credential-public-key" id="ref-for-credential-public-key②①">credential public key</a>.</p>
+   <p>To remove the need to parse CBOR at all in many cases, <code class="idl"><a data-link-type="idl" href="#dom-authenticatorattestationresponse-getauthenticatordata" id="ref-for-dom-authenticatorattestationresponse-getauthenticatordata①">getAuthenticatorData()</a></code> returns the <a data-link-type="dfn" href="#authenticator-data" id="ref-for-authenticator-data①①">authenticator data</a> from <code class="idl"><a data-link-type="idl" href="#dom-authenticatorattestationresponse-attestationobject" id="ref-for-dom-authenticatorattestationresponse-attestationobject⑥">attestationObject</a></code>. The <a data-link-type="dfn" href="#authenticator-data" id="ref-for-authenticator-data①②">authenticator data</a> contains other fields that are encoded in a binary format. However, helper functions are not provided to access them because <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party①⓪⑥">Relying Parties</a> already need to extract those fields when <a href="#sctn-getAssertion">getting an assertion</a>. In contrast to <a href="#sctn-createCredential">credential creation</a>, where signature verification is <a href="#enumdef-attestationconveyancepreference" id="ref-for-enumdef-attestationconveyancepreference">optional</a>, <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party①⓪⑦">Relying Parties</a> should always be verifying signatures from an assertion and thus must extract fields from the signed <a data-link-type="dfn" href="#authenticator-data" id="ref-for-authenticator-data①③">authenticator data</a>. The same functions used there will also serve during credential creation.</p>
+   <p class="note" role="note"><span>Note:</span> <code class="idl"><a data-link-type="idl" href="#dom-authenticatorattestationresponse-getpublickey" id="ref-for-dom-authenticatorattestationresponse-getpublickey⑤">getPublicKey()</a></code> and <code class="idl"><a data-link-type="idl" href="#dom-authenticatorattestationresponse-getauthenticatordata" id="ref-for-dom-authenticatorattestationresponse-getauthenticatordata②">getAuthenticatorData()</a></code> were only added in level two of this spec. <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party①⓪⑧">Relying Parties</a> SHOULD use feature detection before using these functions by testing the value of <code>'getPublicKey' in AuthenticatorAttestationResponse.prototype</code>. <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party①⓪⑨">Relying Parties</a> that require this function to exist may not interoperate with older user-agents.</p>
    <h4 class="heading settled" data-level="5.2.2" id="iface-authenticatorassertionresponse"><span class="secno">5.2.2. </span><span class="content">Web Authentication Assertion (interface <dfn class="dfn-paneled idl-code" data-dfn-type="interface" data-export id="authenticatorassertionresponse"><code>AuthenticatorAssertionResponse</code></dfn>)</span><a class="self-link" href="#iface-authenticatorassertionresponse"></a></h4>
    <div class="mdn-anno wrapped after">
     <button class="mdn-anno-btn"><b class="all-engines-flag" title="This feature is in all current engines.">✔</b><span>MDN</span></button>
@@ -3116,7 +3174,7 @@ <h4 class="heading settled" data-level="5.2.2" id="iface-authenticatorassertionr
 </pre>
    <div>
     <dl>
-     <dt data-md><code class="idl"><a data-link-type="idl" href="#dom-authenticatorresponse-clientdatajson" id="ref-for-dom-authenticatorresponse-clientdatajson④">clientDataJSON</a></code>
+     <dt data-md><code class="idl"><a data-link-type="idl" href="#dom-authenticatorresponse-clientdatajson" id="ref-for-dom-authenticatorresponse-clientdatajson⑤">clientDataJSON</a></code>
      <dd data-md>
       <p>This attribute, inherited from <code class="idl"><a data-link-type="idl" href="#authenticatorresponse" id="ref-for-authenticatorresponse⑦">AuthenticatorResponse</a></code>, contains the <a data-link-type="dfn" href="#collectedclientdata-json-compatible-serialization-of-client-data" id="ref-for-collectedclientdata-json-compatible-serialization-of-client-data④">JSON-compatible serialization of client data</a> (see <a href="#dictionary-client-data">§ 5.8.1 Client Data Used in WebAuthn Signatures (dictionary CollectedClientData)</a>) passed to the authenticator by the client in order to generate this assertion. The
 exact JSON serialization MUST be preserved, as the <a data-link-type="dfn" href="#collectedclientdata-hash-of-the-serialized-client-data" id="ref-for-collectedclientdata-hash-of-the-serialized-client-data⑤">hash of the serialized client data</a> has been computed
@@ -3140,7 +3198,7 @@ <h4 class="heading settled" data-level="5.2.2" id="iface-authenticatorassertionr
       </div>
       <p><dfn class="dfn-paneled idl-code" data-dfn-for="AuthenticatorAssertionResponse" data-dfn-type="attribute" data-export id="dom-authenticatorassertionresponse-authenticatordata"><code>authenticatorData</code></dfn>, <span> of type <a data-link-type="idl-name" href="https://webidl.spec.whatwg.org/#idl-ArrayBuffer" id="ref-for-idl-ArrayBuffer②④">ArrayBuffer</a>, readonly</span></p>
      <dd data-md>
-      <p>This attribute contains the <a data-link-type="dfn" href="#authenticator-data" id="ref-for-authenticator-data①②">authenticator data</a> returned by the authenticator. See <a href="#sctn-authenticator-data">§ 6.1 Authenticator Data</a>.</p>
+      <p>This attribute contains the <a data-link-type="dfn" href="#authenticator-data" id="ref-for-authenticator-data①④">authenticator data</a> returned by the authenticator. See <a href="#sctn-authenticator-data">§ 6.1 Authenticator Data</a>.</p>
      <dt data-md>
       <div class="mdn-anno wrapped">
        <button class="mdn-anno-btn"><b class="all-engines-flag" title="This feature is in all current engines.">✔</b><span>MDN</span></button>
@@ -3212,7 +3270,7 @@ <h3 class="heading settled" data-level="5.4" id="dictionary-makecredentialoption
     <c- b>required</c-> <a data-link-type="dfn" href="https://webidl.spec.whatwg.org/#idl-sequence" id="ref-for-idl-sequence⑥"><c- b>sequence</c-></a>&lt;<a data-link-type="idl-name" href="#dictdef-publickeycredentialparameters" id="ref-for-dictdef-publickeycredentialparameters③"><c- n>PublicKeyCredentialParameters</c-></a>>  <a class="idl-code" data-link-type="dict-member" data-type="sequence<PublicKeyCredentialParameters>  " href="#dom-publickeycredentialcreationoptions-pubkeycredparams" id="ref-for-dom-publickeycredentialcreationoptions-pubkeycredparams③"><c- g>pubKeyCredParams</c-></a>;
 
     <a class="idl-code" data-link-type="interface" href="https://webidl.spec.whatwg.org/#idl-unsigned-long" id="ref-for-idl-unsigned-long②"><c- b>unsigned</c-> <c- b>long</c-></a>                                <a class="idl-code" data-link-type="dict-member" data-type="unsigned long                                " href="#dom-publickeycredentialcreationoptions-timeout" id="ref-for-dom-publickeycredentialcreationoptions-timeout③"><c- g>timeout</c-></a>;
-    <a data-link-type="dfn" href="https://webidl.spec.whatwg.org/#idl-sequence" id="ref-for-idl-sequence⑦"><c- b>sequence</c-></a>&lt;<a data-link-type="idl-name" href="#dictdef-publickeycredentialdescriptor" id="ref-for-dictdef-publickeycredentialdescriptor④"><c- n>PublicKeyCredentialDescriptor</c-></a>>      <a class="idl-code" data-default="[]" data-link-type="dict-member" data-type="sequence<PublicKeyCredentialDescriptor>      " href="#dom-publickeycredentialcreationoptions-excludecredentials" id="ref-for-dom-publickeycredentialcreationoptions-excludecredentials①"><c- g>excludeCredentials</c-></a> = [];
+    <a data-link-type="dfn" href="https://webidl.spec.whatwg.org/#idl-sequence" id="ref-for-idl-sequence⑦"><c- b>sequence</c-></a>&lt;<a data-link-type="idl-name" href="#dictdef-publickeycredentialdescriptor" id="ref-for-dictdef-publickeycredentialdescriptor⑤"><c- n>PublicKeyCredentialDescriptor</c-></a>>      <a class="idl-code" data-default="[]" data-link-type="dict-member" data-type="sequence<PublicKeyCredentialDescriptor>      " href="#dom-publickeycredentialcreationoptions-excludecredentials" id="ref-for-dom-publickeycredentialcreationoptions-excludecredentials①"><c- g>excludeCredentials</c-></a> = [];
     <a data-link-type="idl-name" href="#dictdef-authenticatorselectioncriteria" id="ref-for-dictdef-authenticatorselectioncriteria①"><c- n>AuthenticatorSelectionCriteria</c-></a>               <a class="idl-code" data-link-type="dict-member" data-type="AuthenticatorSelectionCriteria               " href="#dom-publickeycredentialcreationoptions-authenticatorselection" id="ref-for-dom-publickeycredentialcreationoptions-authenticatorselection⑨"><c- g>authenticatorSelection</c-></a>;
     <a class="idl-code" data-link-type="interface" href="https://webidl.spec.whatwg.org/#idl-DOMString" id="ref-for-idl-DOMString②⑤"><c- b>DOMString</c-></a>                                    <a class="idl-code" data-default="&quot;none&quot;" data-link-type="dict-member" data-type="DOMString                                    " href="#dom-publickeycredentialcreationoptions-attestation" id="ref-for-dom-publickeycredentialcreationoptions-attestation②"><c- g>attestation</c-></a> = "none";
     <a data-link-type="idl-name" href="#dictdef-authenticationextensionsclientinputs" id="ref-for-dictdef-authenticationextensionsclientinputs"><c- n>AuthenticationExtensionsClientInputs</c-></a>         <a class="idl-code" data-link-type="dict-member" data-type="AuthenticationExtensionsClientInputs         " href="#dom-publickeycredentialcreationoptions-extensions" id="ref-for-dom-publickeycredentialcreationoptions-extensions③"><c- g>extensions</c-></a>;
@@ -3222,7 +3280,7 @@ <h3 class="heading settled" data-level="5.4" id="dictionary-makecredentialoption
     <dl>
      <dt data-md><dfn class="dfn-paneled idl-code" data-dfn-for="PublicKeyCredentialCreationOptions" data-dfn-type="dict-member" data-export id="dom-publickeycredentialcreationoptions-rp"><code>rp</code></dfn>, <span> of type <a data-link-type="idl-name" href="#dictdef-publickeycredentialrpentity" id="ref-for-dictdef-publickeycredentialrpentity②">PublicKeyCredentialRpEntity</a></span>
      <dd data-md>
-      <p>This member contains a name and an identifier for the <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party①⓪⑤">Relying Party</a> responsible for the request.</p>
+      <p>This member contains a name and an identifier for the <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party①①⓪">Relying Party</a> responsible for the request.</p>
       <p>Its value’s <code class="idl"><a data-link-type="idl" href="#dom-publickeycredentialentity-name" id="ref-for-dom-publickeycredentialentity-name①">name</a></code> member is REQUIRED. See <a href="#dictionary-pkcredentialentity">§ 5.4.1 Public Key Entity Description (dictionary PublicKeyCredentialEntity)</a> for further
 details.</p>
       <p>Its value’s <code class="idl"><a data-link-type="idl" href="#dom-publickeycredentialrpentity-id" id="ref-for-dom-publickeycredentialrpentity-id⑦">id</a></code> member specifies the <a data-link-type="dfn" href="#rp-id" id="ref-for-rp-id②②">RP ID</a> the credential
@@ -3230,9 +3288,9 @@ <h3 class="heading settled" data-level="5.4" id="dictionary-makecredentialoption
 settings object</a>'s <a data-link-type="dfn" href="https://html.spec.whatwg.org/multipage/webappapis.html#concept-settings-object-origin" id="ref-for-concept-settings-object-origin⑥">origin</a>'s <a data-link-type="dfn" href="https://html.spec.whatwg.org/multipage/origin.html#concept-origin-effective-domain" id="ref-for-concept-origin-effective-domain①②">effective domain</a>. See <a href="#dictionary-rp-credential-params">§ 5.4.2 Relying Party Parameters for Credential Generation (dictionary PublicKeyCredentialRpEntity)</a> for further details.</p>
      <dt data-md><dfn class="dfn-paneled idl-code" data-dfn-for="PublicKeyCredentialCreationOptions" data-dfn-type="dict-member" data-export id="dom-publickeycredentialcreationoptions-user"><code>user</code></dfn>, <span> of type <a data-link-type="idl-name" href="#dictdef-publickeycredentialuserentity" id="ref-for-dictdef-publickeycredentialuserentity①">PublicKeyCredentialUserEntity</a></span>
      <dd data-md>
-      <p>This member contains names and an identifier for the <a data-link-type="dfn" href="#user-account" id="ref-for-user-account①①">user account</a> performing the <a data-link-type="dfn" href="#registration" id="ref-for-registration①④">registration</a>.</p>
-      <p>Its value’s <code class="idl"><a data-link-type="idl" href="#dom-publickeycredentialentity-name" id="ref-for-dom-publickeycredentialentity-name②">name</a></code>, <code class="idl"><a data-link-type="idl" href="#dom-publickeycredentialuserentity-displayname" id="ref-for-dom-publickeycredentialuserentity-displayname②">displayName</a></code> and <code class="idl"><a data-link-type="idl" href="#dom-publickeycredentialuserentity-id" id="ref-for-dom-publickeycredentialuserentity-id②">id</a></code> members are REQUIRED. <code class="idl"><a data-link-type="idl" href="#dom-publickeycredentialuserentity-id" id="ref-for-dom-publickeycredentialuserentity-id③">id</a></code> can be returned as the <code class="idl"><a data-link-type="idl" href="#dom-authenticatorassertionresponse-userhandle" id="ref-for-dom-authenticatorassertionresponse-userhandle④">userHandle</a></code> in some future <a data-link-type="dfn" href="#authentication-ceremony" id="ref-for-authentication-ceremony⑨">authentication ceremonies</a>,
-and is used to overwrite existing <a data-link-type="dfn" href="#discoverable-credential" id="ref-for-discoverable-credential④">discoverable credentials</a> that have the same <code><code class="idl"><a data-link-type="idl" href="#dom-publickeycredentialcreationoptions-rp" id="ref-for-dom-publickeycredentialcreationoptions-rp⑨">rp</a></code>.<code class="idl"><a data-link-type="idl" href="#dom-publickeycredentialrpentity-id" id="ref-for-dom-publickeycredentialrpentity-id⑧">id</a></code></code> and <code><code class="idl"><a data-link-type="idl" href="#dom-publickeycredentialcreationoptions-user" id="ref-for-dom-publickeycredentialcreationoptions-user④">user</a></code>.<code class="idl"><a data-link-type="idl" href="#dom-publickeycredentialuserentity-id" id="ref-for-dom-publickeycredentialuserentity-id④">id</a></code></code> on the same <a data-link-type="dfn" href="#authenticator" id="ref-for-authenticator⑨③">authenticator</a>. <code class="idl"><a data-link-type="idl" href="#dom-publickeycredentialentity-name" id="ref-for-dom-publickeycredentialentity-name③">name</a></code> and <code class="idl"><a data-link-type="idl" href="#dom-publickeycredentialuserentity-displayname" id="ref-for-dom-publickeycredentialuserentity-displayname③">displayName</a></code> MAY be used by the <a data-link-type="dfn" href="#authenticator" id="ref-for-authenticator⑨④">authenticator</a> and <a data-link-type="dfn" href="#client" id="ref-for-client③③">client</a> in future <a data-link-type="dfn" href="#authentication-ceremony" id="ref-for-authentication-ceremony①⓪">authentication ceremonies</a> to help the user select a <a data-link-type="dfn" href="https://w3c.github.io/webappsec-credential-management/#concept-credential" id="ref-for-concept-credential⑨">credential</a>, but are not returned to the <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party①⓪⑥">Relying Party</a> as a result of future <a data-link-type="dfn" href="#authentication-ceremony" id="ref-for-authentication-ceremony①①">authentication ceremonies</a></p>
+      <p>This member contains names and an identifier for the <a data-link-type="dfn" href="#user-account" id="ref-for-user-account①③">user account</a> performing the <a data-link-type="dfn" href="#registration" id="ref-for-registration①⑦">registration</a>.</p>
+      <p>Its value’s <code class="idl"><a data-link-type="idl" href="#dom-publickeycredentialentity-name" id="ref-for-dom-publickeycredentialentity-name②">name</a></code>, <code class="idl"><a data-link-type="idl" href="#dom-publickeycredentialuserentity-displayname" id="ref-for-dom-publickeycredentialuserentity-displayname②">displayName</a></code> and <code class="idl"><a data-link-type="idl" href="#dom-publickeycredentialuserentity-id" id="ref-for-dom-publickeycredentialuserentity-id②">id</a></code> members are REQUIRED. <code class="idl"><a data-link-type="idl" href="#dom-publickeycredentialuserentity-id" id="ref-for-dom-publickeycredentialuserentity-id③">id</a></code> can be returned as the <code class="idl"><a data-link-type="idl" href="#dom-authenticatorassertionresponse-userhandle" id="ref-for-dom-authenticatorassertionresponse-userhandle④">userHandle</a></code> in some future <a data-link-type="dfn" href="#authentication-ceremony" id="ref-for-authentication-ceremony①⓪">authentication ceremonies</a>,
+and is used to overwrite existing <a data-link-type="dfn" href="#discoverable-credential" id="ref-for-discoverable-credential④">discoverable credentials</a> that have the same <code><code class="idl"><a data-link-type="idl" href="#dom-publickeycredentialcreationoptions-rp" id="ref-for-dom-publickeycredentialcreationoptions-rp⑨">rp</a></code>.<code class="idl"><a data-link-type="idl" href="#dom-publickeycredentialrpentity-id" id="ref-for-dom-publickeycredentialrpentity-id⑧">id</a></code></code> and <code><code class="idl"><a data-link-type="idl" href="#dom-publickeycredentialcreationoptions-user" id="ref-for-dom-publickeycredentialcreationoptions-user④">user</a></code>.<code class="idl"><a data-link-type="idl" href="#dom-publickeycredentialuserentity-id" id="ref-for-dom-publickeycredentialuserentity-id④">id</a></code></code> on the same <a data-link-type="dfn" href="#authenticator" id="ref-for-authenticator⑨③">authenticator</a>. <code class="idl"><a data-link-type="idl" href="#dom-publickeycredentialentity-name" id="ref-for-dom-publickeycredentialentity-name③">name</a></code> and <code class="idl"><a data-link-type="idl" href="#dom-publickeycredentialuserentity-displayname" id="ref-for-dom-publickeycredentialuserentity-displayname③">displayName</a></code> MAY be used by the <a data-link-type="dfn" href="#authenticator" id="ref-for-authenticator⑨④">authenticator</a> and <a data-link-type="dfn" href="#client" id="ref-for-client③③">client</a> in future <a data-link-type="dfn" href="#authentication-ceremony" id="ref-for-authentication-ceremony①①">authentication ceremonies</a> to help the user select a <a data-link-type="dfn" href="https://w3c.github.io/webappsec-credential-management/#concept-credential" id="ref-for-concept-credential⑨">credential</a>, but are not returned to the <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party①①①">Relying Party</a> as a result of future <a data-link-type="dfn" href="#authentication-ceremony" id="ref-for-authentication-ceremony①②">authentication ceremonies</a></p>
       <p>For further details, see <a href="#dictionary-pkcredentialentity">§ 5.4.1 Public Key Entity Description (dictionary PublicKeyCredentialEntity)</a> and <a href="#dictionary-user-credential-params">§ 5.4.3 User Account Parameters for Credential Generation (dictionary PublicKeyCredentialUserEntity)</a>.</p>
      <dt data-md><dfn class="dfn-paneled idl-code" data-dfn-for="PublicKeyCredentialCreationOptions" data-dfn-type="dict-member" data-export id="dom-publickeycredentialcreationoptions-challenge"><code>challenge</code></dfn>, <span> of type <a data-link-type="idl-name" href="https://webidl.spec.whatwg.org/#BufferSource" id="ref-for-BufferSource③">BufferSource</a></span>
      <dd data-md>
@@ -3241,42 +3299,42 @@ <h3 class="heading settled" data-level="5.4" id="dictionary-makecredentialoption
 See the <a href="#sctn-cryptographic-challenges">§ 13.4.3 Cryptographic Challenges</a> security consideration.</p>
      <dt data-md><dfn class="dfn-paneled idl-code" data-dfn-for="PublicKeyCredentialCreationOptions" data-dfn-type="dict-member" data-export id="dom-publickeycredentialcreationoptions-pubkeycredparams"><code>pubKeyCredParams</code></dfn>, <span> of type sequence&lt;<a data-link-type="idl-name" href="#dictdef-publickeycredentialparameters" id="ref-for-dictdef-publickeycredentialparameters④">PublicKeyCredentialParameters</a>></span>
      <dd data-md>
-      <p>This member lists the key types and signature algorithms the <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party①⓪⑦">Relying Party</a> supports,
+      <p>This member lists the key types and signature algorithms the <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party①①②">Relying Party</a> supports,
 ordered from most preferred to least preferred.
 The <a data-link-type="dfn" href="#client" id="ref-for-client③④">client</a> and <a data-link-type="dfn" href="#authenticator" id="ref-for-authenticator⑨⑥">authenticator</a> make a best-effort to create a credential of the most preferred type possible.
 If none of the listed types can be created, the <code class="idl"><a data-link-type="idl" href="https://w3c.github.io/webappsec-credential-management/#dom-credentialscontainer-create" id="ref-for-dom-credentialscontainer-create①④">create()</a></code> operation fails.</p>
      <dt data-md><dfn class="dfn-paneled idl-code" data-dfn-for="PublicKeyCredentialCreationOptions" data-dfn-type="dict-member" data-export id="dom-publickeycredentialcreationoptions-timeout"><code>timeout</code></dfn>, <span> of type <a data-link-type="idl-name" href="https://webidl.spec.whatwg.org/#idl-unsigned-long" id="ref-for-idl-unsigned-long③">unsigned long</a></span>
      <dd data-md>
-      <p>This OPTIONAL member specifies a time, in milliseconds, that the <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party①⓪⑧">Relying Party</a> is willing to wait for the call to complete. This is
+      <p>This OPTIONAL member specifies a time, in milliseconds, that the <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party①①③">Relying Party</a> is willing to wait for the call to complete. This is
 treated as a hint, and MAY be overridden by the <a data-link-type="dfn" href="#client" id="ref-for-client③⑤">client</a>.</p>
-     <dt data-md><dfn class="dfn-paneled idl-code" data-dfn-for="PublicKeyCredentialCreationOptions" data-dfn-type="dict-member" data-export id="dom-publickeycredentialcreationoptions-excludecredentials"><code>excludeCredentials</code></dfn>, <span> of type sequence&lt;<a data-link-type="idl-name" href="#dictdef-publickeycredentialdescriptor" id="ref-for-dictdef-publickeycredentialdescriptor⑤">PublicKeyCredentialDescriptor</a>>, defaulting to <code>[]</code></span>
+     <dt data-md><dfn class="dfn-paneled idl-code" data-dfn-for="PublicKeyCredentialCreationOptions" data-dfn-type="dict-member" data-export id="dom-publickeycredentialcreationoptions-excludecredentials"><code>excludeCredentials</code></dfn>, <span> of type sequence&lt;<a data-link-type="idl-name" href="#dictdef-publickeycredentialdescriptor" id="ref-for-dictdef-publickeycredentialdescriptor⑥">PublicKeyCredentialDescriptor</a>>, defaulting to <code>[]</code></span>
      <dd data-md>
-      <p>The <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party①⓪⑨">Relying Party</a> SHOULD use this OPTIONAL member to list any existing <a data-link-type="dfn" href="https://w3c.github.io/webappsec-credential-management/#concept-credential" id="ref-for-concept-credential①⓪">credentials</a> mapped to this <a data-link-type="dfn" href="#user-account" id="ref-for-user-account①②">user account</a> (as identified by <code class="idl"><a data-link-type="idl" href="#dom-publickeycredentialcreationoptions-user" id="ref-for-dom-publickeycredentialcreationoptions-user⑤">user</a></code>.<code class="idl"><a data-link-type="idl" href="#dom-publickeycredentialuserentity-id" id="ref-for-dom-publickeycredentialuserentity-id⑤">id</a></code>).
-This ensures that the new credential is not <a data-link-type="dfn" href="#created-on" id="ref-for-created-on①">created on</a> an <a data-link-type="dfn" href="#authenticator" id="ref-for-authenticator⑨⑦">authenticator</a> that already <a data-link-type="dfn" href="#contains" id="ref-for-contains①">contains</a> a credential mapped to this <a data-link-type="dfn" href="#user-account" id="ref-for-user-account①③">user account</a>.
+      <p>The <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party①①④">Relying Party</a> SHOULD use this OPTIONAL member to list any existing <a data-link-type="dfn" href="https://w3c.github.io/webappsec-credential-management/#concept-credential" id="ref-for-concept-credential①⓪">credentials</a> mapped to this <a data-link-type="dfn" href="#user-account" id="ref-for-user-account①④">user account</a> (as identified by <code class="idl"><a data-link-type="idl" href="#dom-publickeycredentialcreationoptions-user" id="ref-for-dom-publickeycredentialcreationoptions-user⑤">user</a></code>.<code class="idl"><a data-link-type="idl" href="#dom-publickeycredentialuserentity-id" id="ref-for-dom-publickeycredentialuserentity-id⑤">id</a></code>).
+This ensures that the new credential is not <a data-link-type="dfn" href="#created-on" id="ref-for-created-on①">created on</a> an <a data-link-type="dfn" href="#authenticator" id="ref-for-authenticator⑨⑦">authenticator</a> that already <a data-link-type="dfn" href="#contains" id="ref-for-contains①">contains</a> a credential mapped to this <a data-link-type="dfn" href="#user-account" id="ref-for-user-account①⑤">user account</a>.
 If it would be, the <a data-link-type="dfn" href="#client" id="ref-for-client③⑥">client</a> is requested to instead guide the user to use a different <a data-link-type="dfn" href="#authenticator" id="ref-for-authenticator⑨⑧">authenticator</a>,
 or return an error if that fails.</p>
      <dt data-md><dfn class="dfn-paneled idl-code" data-dfn-for="PublicKeyCredentialCreationOptions" data-dfn-type="dict-member" data-export id="dom-publickeycredentialcreationoptions-authenticatorselection"><code>authenticatorSelection</code></dfn>, <span> of type <a data-link-type="idl-name" href="#dictdef-authenticatorselectioncriteria" id="ref-for-dictdef-authenticatorselectioncriteria②">AuthenticatorSelectionCriteria</a></span>
      <dd data-md>
-      <p>The <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party①①⓪">Relying Party</a> MAY use this OPTIONAL member to specify capabilities and settings
+      <p>The <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party①①⑤">Relying Party</a> MAY use this OPTIONAL member to specify capabilities and settings
 that the <a data-link-type="dfn" href="#authenticator" id="ref-for-authenticator⑨⑨">authenticator</a> MUST or SHOULD satisfy to participate in the <code class="idl"><a data-link-type="idl" href="https://w3c.github.io/webappsec-credential-management/#dom-credentialscontainer-create" id="ref-for-dom-credentialscontainer-create①⑤">create()</a></code> operation.
 See <a href="#dictionary-authenticatorSelection">§ 5.4.4 Authenticator Selection Criteria (dictionary AuthenticatorSelectionCriteria)</a>.</p>
      <dt data-md><dfn class="dfn-paneled idl-code" data-dfn-for="PublicKeyCredentialCreationOptions" data-dfn-type="dict-member" data-export id="dom-publickeycredentialcreationoptions-attestation"><code>attestation</code></dfn>, <span> of type <a data-link-type="idl-name" href="https://webidl.spec.whatwg.org/#idl-DOMString" id="ref-for-idl-DOMString②⑥">DOMString</a>, defaulting to <code>"none"</code></span>
      <dd data-md>
-      <p>The <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party①①①">Relying Party</a> MAY use this OPTIONAL member to specify a preference regarding <a data-link-type="dfn" href="#attestation-conveyance" id="ref-for-attestation-conveyance①">attestation conveyance</a>.
+      <p>The <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party①①⑥">Relying Party</a> MAY use this OPTIONAL member to specify a preference regarding <a data-link-type="dfn" href="#attestation-conveyance" id="ref-for-attestation-conveyance①">attestation conveyance</a>.
 Its value SHOULD be a member of <code class="idl"><a data-link-type="idl" href="#enumdef-attestationconveyancepreference" id="ref-for-enumdef-attestationconveyancepreference④">AttestationConveyancePreference</a></code>. <a data-link-type="dfn" href="#client-platform" id="ref-for-client-platform③①">Client platforms</a> MUST ignore unknown values, treating an unknown value as if the <a data-link-type="dfn" href="https://infra.spec.whatwg.org/#map-exists" id="ref-for-map-exists">member does not exist</a>.</p>
       <p>The default value is <code class="idl"><a data-link-type="idl" href="#dom-attestationconveyancepreference-none" id="ref-for-dom-attestationconveyancepreference-none①">none</a></code>.</p>
      <dt data-md><dfn class="dfn-paneled idl-code" data-dfn-for="PublicKeyCredentialCreationOptions" data-dfn-type="dict-member" data-export id="dom-publickeycredentialcreationoptions-extensions"><code>extensions</code></dfn>, <span> of type <a data-link-type="idl-name" href="#dictdef-authenticationextensionsclientinputs" id="ref-for-dictdef-authenticationextensionsclientinputs①">AuthenticationExtensionsClientInputs</a></span>
      <dd data-md>
-      <p>The <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party①①②">Relying Party</a> MAY use this OPTIONAL member to provide <a data-link-type="dfn" href="#client-extension-input" id="ref-for-client-extension-input②">client extension inputs</a> requesting additional processing by the <a data-link-type="dfn" href="#client" id="ref-for-client③⑦">client</a> and <a data-link-type="dfn" href="#authenticator" id="ref-for-authenticator①⓪⓪">authenticator</a>.
-For example, the <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party①①③">Relying Party</a> may request that the client returns additional information about the <a data-link-type="dfn" href="https://w3c.github.io/webappsec-credential-management/#concept-credential" id="ref-for-concept-credential①①">credential</a> that was created.</p>
+      <p>The <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party①①⑦">Relying Party</a> MAY use this OPTIONAL member to provide <a data-link-type="dfn" href="#client-extension-input" id="ref-for-client-extension-input②">client extension inputs</a> requesting additional processing by the <a data-link-type="dfn" href="#client" id="ref-for-client③⑦">client</a> and <a data-link-type="dfn" href="#authenticator" id="ref-for-authenticator①⓪⓪">authenticator</a>.
+For example, the <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party①①⑧">Relying Party</a> may request that the client returns additional information about the <a data-link-type="dfn" href="https://w3c.github.io/webappsec-credential-management/#concept-credential" id="ref-for-concept-credential①①">credential</a> that was created.</p>
       <p>The extensions framework is defined in <a href="#sctn-extensions">§ 9 WebAuthn Extensions</a>.
 Some extensions are defined in <a href="#sctn-defined-extensions">§ 10 Defined Extensions</a>;
 consult the IANA "WebAuthn Extension Identifiers" registry <a data-link-type="biblio" href="#biblio-iana-webauthn-registries">[IANA-WebAuthn-Registries]</a> established by <a data-link-type="biblio" href="#biblio-rfc8809">[RFC8809]</a> for an up-to-date list
-of registered <a data-link-type="dfn" href="#webauthn-extensions" id="ref-for-webauthn-extensions">WebAuthn Extensions</a>.</p>
+of registered <a data-link-type="dfn" href="#webauthn-extensions" id="ref-for-webauthn-extensions①">WebAuthn Extensions</a>.</p>
     </dl>
    </div>
    <h4 class="heading settled" data-level="5.4.1" id="dictionary-pkcredentialentity"><span class="secno">5.4.1. </span><span class="content">Public Key Entity Description (dictionary <dfn class="dfn-paneled idl-code" data-dfn-type="dictionary" data-export id="dictdef-publickeycredentialentity"><code>PublicKeyCredentialEntity</code></dfn>)</span><a class="self-link" href="#dictionary-pkcredentialentity"></a></h4>
-   <p>The <code class="idl"><a data-link-type="idl" href="#dictdef-publickeycredentialentity" id="ref-for-dictdef-publickeycredentialentity">PublicKeyCredentialEntity</a></code> dictionary describes a <a data-link-type="dfn" href="#user-account" id="ref-for-user-account①④">user account</a>, or a <a data-link-type="dfn" href="#webauthn-relying-party" id="ref-for-webauthn-relying-party①⑧">WebAuthn Relying Party</a>, which a <a data-link-type="dfn" href="#public-key-credential" id="ref-for-public-key-credential③②">public key credential</a> is
+   <p>The <code class="idl"><a data-link-type="idl" href="#dictdef-publickeycredentialentity" id="ref-for-dictdef-publickeycredentialentity">PublicKeyCredentialEntity</a></code> dictionary describes a <a data-link-type="dfn" href="#user-account" id="ref-for-user-account①⑥">user account</a>, or a <a data-link-type="dfn" href="#webauthn-relying-party" id="ref-for-webauthn-relying-party①⑧">WebAuthn Relying Party</a>, which a <a data-link-type="dfn" href="#public-key-credential" id="ref-for-public-key-credential③②">public key credential</a> is
 associated with or <a data-link-type="dfn" href="#scope" id="ref-for-scope①①">scoped</a> to, respectively.</p>
 <pre class="idl highlight def"><c- b>dictionary</c-> <a class="idl-code" data-link-type="dictionary" href="#dictdef-publickeycredentialentity" id="ref-for-dictdef-publickeycredentialentity①"><c- g>PublicKeyCredentialEntity</c-></a> {
     <c- b>required</c-> <a class="idl-code" data-link-type="interface" href="https://webidl.spec.whatwg.org/#idl-DOMString" id="ref-for-idl-DOMString②⑦"><c- b>DOMString</c-></a>    <a class="idl-code" data-link-type="dict-member" data-type="DOMString    " href="#dom-publickeycredentialentity-name" id="ref-for-dom-publickeycredentialentity-name④"><c- g>name</c-></a>;
@@ -3289,31 +3347,31 @@ <h4 class="heading settled" data-level="5.4.1" id="dictionary-pkcredentialentity
       <p>A <a data-link-type="dfn" href="#human-palatability" id="ref-for-human-palatability①">human-palatable</a> name for the entity. Its function depends on what the <code class="idl"><a data-link-type="idl" href="#dictdef-publickeycredentialentity" id="ref-for-dictdef-publickeycredentialentity②">PublicKeyCredentialEntity</a></code> represents:</p>
       <ul>
        <li data-md>
-        <p>When inherited by <code class="idl"><a data-link-type="idl" href="#dictdef-publickeycredentialrpentity" id="ref-for-dictdef-publickeycredentialrpentity③">PublicKeyCredentialRpEntity</a></code> it is a <a data-link-type="dfn" href="#human-palatability" id="ref-for-human-palatability②">human-palatable</a> identifier for the <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party①①④">Relying Party</a>, intended only
+        <p>When inherited by <code class="idl"><a data-link-type="idl" href="#dictdef-publickeycredentialrpentity" id="ref-for-dictdef-publickeycredentialrpentity③">PublicKeyCredentialRpEntity</a></code> it is a <a data-link-type="dfn" href="#human-palatability" id="ref-for-human-palatability②">human-palatable</a> identifier for the <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party①①⑨">Relying Party</a>, intended only
 for display. For example, "ACME Corporation", "Wonderful Widgets, Inc." or "ОАО Примертех".</p>
         <ul>
          <li data-md>
-          <p><a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party①①⑤">Relying Parties</a> SHOULD perform enforcement, as prescribed in Section 2.3 of <a data-link-type="biblio" href="#biblio-rfc8266">[RFC8266]</a> for the Nickname Profile of the PRECIS FreeformClass <a data-link-type="biblio" href="#biblio-rfc8264">[RFC8264]</a>,
+          <p><a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party①②⓪">Relying Parties</a> SHOULD perform enforcement, as prescribed in Section 2.3 of <a data-link-type="biblio" href="#biblio-rfc8266">[RFC8266]</a> for the Nickname Profile of the PRECIS FreeformClass <a data-link-type="biblio" href="#biblio-rfc8264">[RFC8264]</a>,
 when setting <code class="idl"><a data-link-type="idl" href="#dom-publickeycredentialentity-name" id="ref-for-dom-publickeycredentialentity-name⑤">name</a></code>'s value, or displaying the value to the user.</p>
          <li data-md>
-          <p>This string MAY contain language and direction metadata. <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party①①⑥">Relying Parties</a> SHOULD consider providing this information. See <a href="#sctn-strings-langdir">§ 6.4.2 Language and Direction Encoding</a> about how this metadata is encoded.</p>
+          <p>This string MAY contain language and direction metadata. <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party①②①">Relying Parties</a> SHOULD consider providing this information. See <a href="#sctn-strings-langdir">§ 6.4.2 Language and Direction Encoding</a> about how this metadata is encoded.</p>
          <li data-md>
           <p><a data-link-type="dfn" href="#client" id="ref-for-client③⑧">Clients</a> SHOULD perform enforcement, as prescribed in Section 2.3 of <a data-link-type="biblio" href="#biblio-rfc8266">[RFC8266]</a> for the Nickname Profile of the PRECIS FreeformClass <a data-link-type="biblio" href="#biblio-rfc8264">[RFC8264]</a>,
 on <code class="idl"><a data-link-type="idl" href="#dom-publickeycredentialentity-name" id="ref-for-dom-publickeycredentialentity-name⑥">name</a></code>'s value prior to displaying the value to the user or
 including the value as a parameter of the <a data-link-type="dfn" href="#authenticatormakecredential" id="ref-for-authenticatormakecredential⑦">authenticatorMakeCredential</a> operation.</p>
         </ul>
        <li data-md>
-        <p>When inherited by <code class="idl"><a data-link-type="idl" href="#dictdef-publickeycredentialuserentity" id="ref-for-dictdef-publickeycredentialuserentity②">PublicKeyCredentialUserEntity</a></code>, it is a <a data-link-type="dfn" href="#human-palatability" id="ref-for-human-palatability③">human-palatable</a> identifier for a <a data-link-type="dfn" href="#user-account" id="ref-for-user-account①⑤">user account</a>. It is intended only for display, i.e., aiding the user in determining the difference between user
+        <p>When inherited by <code class="idl"><a data-link-type="idl" href="#dictdef-publickeycredentialuserentity" id="ref-for-dictdef-publickeycredentialuserentity②">PublicKeyCredentialUserEntity</a></code>, it is a <a data-link-type="dfn" href="#human-palatability" id="ref-for-human-palatability③">human-palatable</a> identifier for a <a data-link-type="dfn" href="#user-account" id="ref-for-user-account①⑦">user account</a>. It is intended only for display, i.e., aiding the user in determining the difference between user
 accounts with similar <code class="idl"><a data-link-type="idl" href="#dom-publickeycredentialuserentity-displayname" id="ref-for-dom-publickeycredentialuserentity-displayname④">displayName</a></code>s. For example, "alexm", "alex.mueller@example.com"
 or "+14255551234".</p>
         <ul>
          <li data-md>
-          <p>The <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party①①⑦">Relying Party</a> MAY let the user choose this value. The <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party①①⑧">Relying Party</a> SHOULD perform enforcement,
+          <p>The <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party①②②">Relying Party</a> MAY let the user choose this value. The <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party①②③">Relying Party</a> SHOULD perform enforcement,
 as prescribed in Section 3.4.3 of <a data-link-type="biblio" href="#biblio-rfc8265">[RFC8265]</a> for the UsernameCasePreserved Profile of the PRECIS
 IdentifierClass <a data-link-type="biblio" href="#biblio-rfc8264">[RFC8264]</a>, when setting <code class="idl"><a data-link-type="idl" href="#dom-publickeycredentialentity-name" id="ref-for-dom-publickeycredentialentity-name⑦">name</a></code>'s value, or displaying the value
 to the user.</p>
          <li data-md>
-          <p>This string MAY contain language and direction metadata. <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party①①⑨">Relying Parties</a> SHOULD consider providing this information. See <a href="#sctn-strings-langdir">§ 6.4.2 Language and Direction Encoding</a> about how this metadata is encoded.</p>
+          <p>This string MAY contain language and direction metadata. <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party①②④">Relying Parties</a> SHOULD consider providing this information. See <a href="#sctn-strings-langdir">§ 6.4.2 Language and Direction Encoding</a> about how this metadata is encoded.</p>
          <li data-md>
           <p><a data-link-type="dfn" href="#client" id="ref-for-client③⑨">Clients</a> SHOULD perform enforcement, as prescribed in Section 3.4.3 of <a data-link-type="biblio" href="#biblio-rfc8265">[RFC8265]</a> for the UsernameCasePreserved Profile of the PRECIS IdentifierClass <a data-link-type="biblio" href="#biblio-rfc8264">[RFC8264]</a>,
 on <code class="idl"><a data-link-type="idl" href="#dom-publickeycredentialentity-name" id="ref-for-dom-publickeycredentialentity-name⑧">name</a></code>'s value prior to displaying the value to the user or
@@ -3325,7 +3383,7 @@ <h4 class="heading settled" data-level="5.4.1" id="dictionary-pkcredentialentity
     </dl>
    </div>
    <h4 class="heading settled" data-level="5.4.2" id="dictionary-rp-credential-params"><span class="secno">5.4.2. </span><span class="content">Relying Party Parameters for Credential Generation (dictionary <dfn class="dfn-paneled idl-code" data-dfn-type="dictionary" data-export id="dictdef-publickeycredentialrpentity"><code>PublicKeyCredentialRpEntity</code></dfn>)</span><a class="self-link" href="#dictionary-rp-credential-params"></a></h4>
-   <p>The <code class="idl"><a data-link-type="idl" href="#dictdef-publickeycredentialrpentity" id="ref-for-dictdef-publickeycredentialrpentity④">PublicKeyCredentialRpEntity</a></code> dictionary is used to supply additional <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party①②⓪">Relying Party</a> attributes when creating a new credential.</p>
+   <p>The <code class="idl"><a data-link-type="idl" href="#dictdef-publickeycredentialrpentity" id="ref-for-dictdef-publickeycredentialrpentity④">PublicKeyCredentialRpEntity</a></code> dictionary is used to supply additional <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party①②⑤">Relying Party</a> attributes when creating a new credential.</p>
 <pre class="idl highlight def"><c- b>dictionary</c-> <a class="idl-code" data-link-type="dictionary" href="#dictdef-publickeycredentialrpentity" id="ref-for-dictdef-publickeycredentialrpentity⑤"><c- g>PublicKeyCredentialRpEntity</c-></a> : <a data-link-type="idl-name" href="#dictdef-publickeycredentialentity" id="ref-for-dictdef-publickeycredentialentity③"><c- n>PublicKeyCredentialEntity</c-></a> {
     <a class="idl-code" data-link-type="interface" href="https://webidl.spec.whatwg.org/#idl-DOMString" id="ref-for-idl-DOMString②⑨"><c- b>DOMString</c-></a>      <a class="idl-code" data-link-type="dict-member" data-type="DOMString      " href="#dom-publickeycredentialrpentity-id" id="ref-for-dom-publickeycredentialrpentity-id⑨"><c- g>id</c-></a>;
 };
@@ -3334,11 +3392,11 @@ <h4 class="heading settled" data-level="5.4.2" id="dictionary-rp-credential-para
     <dl>
      <dt data-md><dfn class="dfn-paneled idl-code" data-dfn-for="PublicKeyCredentialRpEntity" data-dfn-type="dict-member" data-export id="dom-publickeycredentialrpentity-id"><code>id</code></dfn>, <span> of type <a data-link-type="idl-name" href="https://webidl.spec.whatwg.org/#idl-DOMString" id="ref-for-idl-DOMString③⓪">DOMString</a></span>
      <dd data-md>
-      <p>A unique identifier for the <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party①②①">Relying Party</a> entity, which sets the <a data-link-type="dfn" href="#rp-id" id="ref-for-rp-id②③">RP ID</a>.</p>
+      <p>A unique identifier for the <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party①②⑥">Relying Party</a> entity, which sets the <a data-link-type="dfn" href="#rp-id" id="ref-for-rp-id②③">RP ID</a>.</p>
     </dl>
    </div>
    <h4 class="heading settled" data-level="5.4.3" id="dictionary-user-credential-params"><span class="secno">5.4.3. </span><span class="content">User Account Parameters for Credential Generation (dictionary <dfn class="dfn-paneled idl-code" data-dfn-type="dictionary" data-export id="dictdef-publickeycredentialuserentity"><code>PublicKeyCredentialUserEntity</code></dfn>)</span><a class="self-link" href="#dictionary-user-credential-params"></a></h4>
-   <p>The <code class="idl"><a data-link-type="idl" href="#dictdef-publickeycredentialuserentity" id="ref-for-dictdef-publickeycredentialuserentity③">PublicKeyCredentialUserEntity</a></code> dictionary is used to supply additional <a data-link-type="dfn" href="#user-account" id="ref-for-user-account①⑥">user account</a> attributes when creating a new
+   <p>The <code class="idl"><a data-link-type="idl" href="#dictdef-publickeycredentialuserentity" id="ref-for-dictdef-publickeycredentialuserentity③">PublicKeyCredentialUserEntity</a></code> dictionary is used to supply additional <a data-link-type="dfn" href="#user-account" id="ref-for-user-account①⑧">user account</a> attributes when creating a new
 credential.</p>
 <pre class="idl highlight def"><c- b>dictionary</c-> <a class="idl-code" data-link-type="dictionary" href="#dictdef-publickeycredentialuserentity" id="ref-for-dictdef-publickeycredentialuserentity④"><c- g>PublicKeyCredentialUserEntity</c-></a> : <a data-link-type="idl-name" href="#dictdef-publickeycredentialentity" id="ref-for-dictdef-publickeycredentialentity④"><c- n>PublicKeyCredentialEntity</c-></a> {
     <c- b>required</c-> <a data-link-type="idl-name" href="https://webidl.spec.whatwg.org/#BufferSource" id="ref-for-BufferSource④"><c- n>BufferSource</c-></a>   <a class="idl-code" data-link-type="dict-member" data-type="BufferSource   " href="#dom-publickeycredentialuserentity-id" id="ref-for-dom-publickeycredentialuserentity-id⑥"><c- g>id</c-></a>;
@@ -3349,26 +3407,26 @@ <h4 class="heading settled" data-level="5.4.3" id="dictionary-user-credential-pa
     <dl>
      <dt data-md><dfn class="dfn-paneled idl-code" data-dfn-for="PublicKeyCredentialUserEntity" data-dfn-type="dict-member" data-export id="dom-publickeycredentialuserentity-id"><code>id</code></dfn>, <span> of type <a data-link-type="idl-name" href="https://webidl.spec.whatwg.org/#BufferSource" id="ref-for-BufferSource⑤">BufferSource</a></span>
      <dd data-md>
-      <p>The <a data-link-type="dfn" href="#user-handle" id="ref-for-user-handle①①">user handle</a> of the <a data-link-type="dfn" href="#user-account" id="ref-for-user-account①⑦">user account</a>.
+      <p>The <a data-link-type="dfn" href="#user-handle" id="ref-for-user-handle①①">user handle</a> of the <a data-link-type="dfn" href="#user-account" id="ref-for-user-account①⑨">user account</a>.
 A <a data-link-type="dfn" href="#user-handle" id="ref-for-user-handle①②">user handle</a> is an opaque <a data-link-type="dfn" href="https://infra.spec.whatwg.org/#byte-sequence" id="ref-for-byte-sequence②">byte sequence</a> with a maximum size of 64 bytes,
 and is not meant to be displayed to the user.</p>
       <p>To ensure secure operation, authentication and authorization
 decisions MUST be made on the basis of this <code class="idl"><a data-link-type="idl" href="#dom-publickeycredentialuserentity-id" id="ref-for-dom-publickeycredentialuserentity-id⑦">id</a></code> member,  not the <code class="idl"><a data-link-type="idl" href="#dom-publickeycredentialuserentity-displayname" id="ref-for-dom-publickeycredentialuserentity-displayname⑥">displayName</a></code> nor <code class="idl"><a data-link-type="idl" href="#dom-publickeycredentialentity-name" id="ref-for-dom-publickeycredentialentity-name①①">name</a></code> members. See Section 6.1 of <a data-link-type="biblio" href="#biblio-rfc8266">[RFC8266]</a>.</p>
       <p>The <a data-link-type="dfn" href="#user-handle" id="ref-for-user-handle①③">user handle</a> MUST NOT contain personally identifying information about the user, such as a username or e-mail address;
 see <a href="#sctn-user-handle-privacy">§ 14.6.1 User Handle Contents</a> for details. The <a data-link-type="dfn" href="#user-handle" id="ref-for-user-handle①④">user handle</a> MUST NOT be empty.</p>
-      <p class="note" role="note"><span>Note:</span> the <a data-link-type="dfn" href="#user-handle" id="ref-for-user-handle①⑤">user handle</a> <i>ought not</i> be a constant value across different <a data-link-type="dfn" href="#user-account" id="ref-for-user-account①⑧">user accounts</a>,
+      <p class="note" role="note"><span>Note:</span> the <a data-link-type="dfn" href="#user-handle" id="ref-for-user-handle①⑤">user handle</a> <i>ought not</i> be a constant value across different <a data-link-type="dfn" href="#user-account" id="ref-for-user-account②⓪">user accounts</a>,
 even for <a data-link-type="dfn" href="#non-discoverable-credential" id="ref-for-non-discoverable-credential②">non-discoverable credentials</a>, because some authenticators always create <a data-link-type="dfn" href="#discoverable-credential" id="ref-for-discoverable-credential⑤">discoverable credentials</a>.
 Thus a constant <a data-link-type="dfn" href="#user-handle" id="ref-for-user-handle①⑥">user handle</a> would prevent a user from using such an authenticator
-with more than one <a data-link-type="dfn" href="#user-account" id="ref-for-user-account①⑨">user account</a> at the <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party①②②">Relying Party</a>.</p>
+with more than one <a data-link-type="dfn" href="#user-account" id="ref-for-user-account②①">user account</a> at the <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party①②⑦">Relying Party</a>.</p>
      <dt data-md><dfn class="dfn-paneled idl-code" data-dfn-for="PublicKeyCredentialUserEntity" data-dfn-type="dict-member" data-export id="dom-publickeycredentialuserentity-displayname"><code>displayName</code></dfn>, <span> of type <a data-link-type="idl-name" href="https://webidl.spec.whatwg.org/#idl-DOMString" id="ref-for-idl-DOMString③②">DOMString</a></span>
      <dd data-md>
-      <p>A <a data-link-type="dfn" href="#human-palatability" id="ref-for-human-palatability④">human-palatable</a> name for the <a data-link-type="dfn" href="#user-account" id="ref-for-user-account②⓪">user account</a>, intended only for display. For example, "Alex Müller" or "田中倫". The <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party①②③">Relying Party</a> SHOULD let the user choose this, and SHOULD NOT restrict the choice more than necessary.</p>
+      <p>A <a data-link-type="dfn" href="#human-palatability" id="ref-for-human-palatability④">human-palatable</a> name for the <a data-link-type="dfn" href="#user-account" id="ref-for-user-account②②">user account</a>, intended only for display. For example, "Alex Müller" or "田中倫". The <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party①②⑧">Relying Party</a> SHOULD let the user choose this, and SHOULD NOT restrict the choice more than necessary.</p>
       <ul>
        <li data-md>
-        <p><a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party①②④">Relying Parties</a> SHOULD perform enforcement, as prescribed in Section 2.3 of <a data-link-type="biblio" href="#biblio-rfc8266">[RFC8266]</a> for the Nickname Profile of the PRECIS FreeformClass <a data-link-type="biblio" href="#biblio-rfc8264">[RFC8264]</a>,
+        <p><a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party①②⑨">Relying Parties</a> SHOULD perform enforcement, as prescribed in Section 2.3 of <a data-link-type="biblio" href="#biblio-rfc8266">[RFC8266]</a> for the Nickname Profile of the PRECIS FreeformClass <a data-link-type="biblio" href="#biblio-rfc8264">[RFC8264]</a>,
 when setting <code class="idl"><a data-link-type="idl" href="#dom-publickeycredentialuserentity-displayname" id="ref-for-dom-publickeycredentialuserentity-displayname⑦">displayName</a></code>'s value, or displaying the value to the user.</p>
        <li data-md>
-        <p>This string MAY contain language and direction metadata. <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party①②⑤">Relying Parties</a> SHOULD consider providing this information. See <a href="#sctn-strings-langdir">§ 6.4.2 Language and Direction Encoding</a> about how this metadata is encoded.</p>
+        <p>This string MAY contain language and direction metadata. <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party①③⓪">Relying Parties</a> SHOULD consider providing this information. See <a href="#sctn-strings-langdir">§ 6.4.2 Language and Direction Encoding</a> about how this metadata is encoded.</p>
        <li data-md>
         <p><a data-link-type="dfn" href="#client" id="ref-for-client④①">Clients</a> SHOULD perform enforcement, as prescribed in Section 2.3 of <a data-link-type="biblio" href="#biblio-rfc8266">[RFC8266]</a> for the Nickname Profile of the PRECIS FreeformClass <a data-link-type="biblio" href="#biblio-rfc8264">[RFC8264]</a>,
 on <code class="idl"><a data-link-type="idl" href="#dom-publickeycredentialuserentity-displayname" id="ref-for-dom-publickeycredentialuserentity-displayname⑧">displayName</a></code>'s value prior to displaying the value to the user or
@@ -3401,20 +3459,20 @@ <h4 class="heading settled" data-level="5.4.4" id="dictionary-authenticatorSelec
 in a successful <code class="idl"><a data-link-type="idl" href="https://w3c.github.io/webappsec-credential-management/#dom-credentialscontainer-create" id="ref-for-dom-credentialscontainer-create①⑥">create()</a></code> or <code class="idl"><a data-link-type="idl" href="https://w3c.github.io/webappsec-credential-management/#dom-credentialscontainer-get" id="ref-for-dom-credentialscontainer-get②①">get()</a></code> operation.</p>
      <dt data-md><dfn class="dfn-paneled idl-code" data-dfn-for="AuthenticatorSelectionCriteria" data-dfn-type="dict-member" data-export id="dom-authenticatorselectioncriteria-residentkey"><code>residentKey</code></dfn>, <span> of type <a data-link-type="idl-name" href="https://webidl.spec.whatwg.org/#idl-DOMString" id="ref-for-idl-DOMString③⑦">DOMString</a></span>
      <dd data-md>
-      <p>Specifies the extent to which the <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party①②⑥">Relying Party</a> desires to create a <a data-link-type="dfn" href="#client-side-discoverable-credential" id="ref-for-client-side-discoverable-credential⑥">client-side discoverable credential</a>. For historical reasons the naming retains the deprecated “resident” terminology. The value SHOULD be a member of <code class="idl"><a data-link-type="idl" href="#enumdef-residentkeyrequirement" id="ref-for-enumdef-residentkeyrequirement">ResidentKeyRequirement</a></code> but <a data-link-type="dfn" href="#client-platform" id="ref-for-client-platform③⑤">client platforms</a> MUST ignore unknown values, treating an unknown value as if the <a data-link-type="dfn" href="https://infra.spec.whatwg.org/#map-exists" id="ref-for-map-exists②">member does not exist</a>. If no value is given then the effective value is <code class="idl"><a data-link-type="idl" href="#dom-residentkeyrequirement-required" id="ref-for-dom-residentkeyrequirement-required②">required</a></code> if <code class="idl"><a data-link-type="idl" href="#dom-authenticatorselectioncriteria-requireresidentkey" id="ref-for-dom-authenticatorselectioncriteria-requireresidentkey③">requireResidentKey</a></code> is <code>true</code> or <code class="idl"><a data-link-type="idl" href="#dom-residentkeyrequirement-discouraged" id="ref-for-dom-residentkeyrequirement-discouraged②">discouraged</a></code> if it is <code>false</code> or absent.</p>
+      <p>Specifies the extent to which the <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party①③①">Relying Party</a> desires to create a <a data-link-type="dfn" href="#client-side-discoverable-credential" id="ref-for-client-side-discoverable-credential⑥">client-side discoverable credential</a>. For historical reasons the naming retains the deprecated “resident” terminology. The value SHOULD be a member of <code class="idl"><a data-link-type="idl" href="#enumdef-residentkeyrequirement" id="ref-for-enumdef-residentkeyrequirement">ResidentKeyRequirement</a></code> but <a data-link-type="dfn" href="#client-platform" id="ref-for-client-platform③⑤">client platforms</a> MUST ignore unknown values, treating an unknown value as if the <a data-link-type="dfn" href="https://infra.spec.whatwg.org/#map-exists" id="ref-for-map-exists②">member does not exist</a>. If no value is given then the effective value is <code class="idl"><a data-link-type="idl" href="#dom-residentkeyrequirement-required" id="ref-for-dom-residentkeyrequirement-required②">required</a></code> if <code class="idl"><a data-link-type="idl" href="#dom-authenticatorselectioncriteria-requireresidentkey" id="ref-for-dom-authenticatorselectioncriteria-requireresidentkey③">requireResidentKey</a></code> is <code>true</code> or <code class="idl"><a data-link-type="idl" href="#dom-residentkeyrequirement-discouraged" id="ref-for-dom-residentkeyrequirement-discouraged②">discouraged</a></code> if it is <code>false</code> or absent.</p>
       <p>See <code class="idl"><a data-link-type="idl" href="#enumdef-residentkeyrequirement" id="ref-for-enumdef-residentkeyrequirement①">ResidentKeyRequirement</a></code> for the description of <code class="idl"><a data-link-type="idl" href="#dom-authenticatorselectioncriteria-residentkey" id="ref-for-dom-authenticatorselectioncriteria-residentkey③">residentKey</a></code>'s values and semantics.</p>
      <dt data-md><dfn class="dfn-paneled idl-code" data-dfn-for="AuthenticatorSelectionCriteria" data-dfn-type="dict-member" data-export id="dom-authenticatorselectioncriteria-requireresidentkey"><code>requireResidentKey</code></dfn>, <span> of type <a data-link-type="idl-name" href="https://webidl.spec.whatwg.org/#idl-boolean" id="ref-for-idl-boolean③">boolean</a>, defaulting to <code>false</code></span>
      <dd data-md>
-      <p>This member is retained for backwards compatibility with WebAuthn Level 1 and, for historical reasons, its naming retains the deprecated “resident” terminology for <a data-link-type="dfn" href="#discoverable-credential" id="ref-for-discoverable-credential⑥">discoverable credentials</a>. <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party①②⑦">Relying Parties</a> SHOULD set it to <code>true</code> if, and only if, <code class="idl"><a data-link-type="idl" href="#dom-authenticatorselectioncriteria-residentkey" id="ref-for-dom-authenticatorselectioncriteria-residentkey④">residentKey</a></code> is set to <code class="idl"><a data-link-type="idl" href="#dom-residentkeyrequirement-required" id="ref-for-dom-residentkeyrequirement-required③">required</a></code>.</p>
+      <p>This member is retained for backwards compatibility with WebAuthn Level 1 and, for historical reasons, its naming retains the deprecated “resident” terminology for <a data-link-type="dfn" href="#discoverable-credential" id="ref-for-discoverable-credential⑥">discoverable credentials</a>. <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party①③②">Relying Parties</a> SHOULD set it to <code>true</code> if, and only if, <code class="idl"><a data-link-type="idl" href="#dom-authenticatorselectioncriteria-residentkey" id="ref-for-dom-authenticatorselectioncriteria-residentkey④">residentKey</a></code> is set to <code class="idl"><a data-link-type="idl" href="#dom-residentkeyrequirement-required" id="ref-for-dom-residentkeyrequirement-required③">required</a></code>.</p>
      <dt data-md><dfn class="dfn-paneled idl-code" data-dfn-for="AuthenticatorSelectionCriteria" data-dfn-type="dict-member" data-export id="dom-authenticatorselectioncriteria-userverification"><code>userVerification</code></dfn>, <span> of type <a data-link-type="idl-name" href="https://webidl.spec.whatwg.org/#idl-DOMString" id="ref-for-idl-DOMString③⑧">DOMString</a>, defaulting to <code>"preferred"</code></span>
      <dd data-md>
-      <p>This member specifies the <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party①②⑧">Relying Party</a>'s requirements regarding <a data-link-type="dfn" href="#user-verification" id="ref-for-user-verification①⑧">user verification</a> for the <code class="idl"><a data-link-type="idl" href="https://w3c.github.io/webappsec-credential-management/#dom-credentialscontainer-create" id="ref-for-dom-credentialscontainer-create①⑦">create()</a></code> operation.
+      <p>This member specifies the <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party①③③">Relying Party</a>'s requirements regarding <a data-link-type="dfn" href="#user-verification" id="ref-for-user-verification①⑧">user verification</a> for the <code class="idl"><a data-link-type="idl" href="https://w3c.github.io/webappsec-credential-management/#dom-credentialscontainer-create" id="ref-for-dom-credentialscontainer-create①⑦">create()</a></code> operation.
 The value SHOULD be a member of <code class="idl"><a data-link-type="idl" href="#enumdef-userverificationrequirement" id="ref-for-enumdef-userverificationrequirement">UserVerificationRequirement</a></code> but <a data-link-type="dfn" href="#client-platform" id="ref-for-client-platform③⑥">client platforms</a> MUST ignore unknown values, treating an unknown value as if the <a data-link-type="dfn" href="https://infra.spec.whatwg.org/#map-exists" id="ref-for-map-exists③">member does not exist</a>.</p>
       <p>See <code class="idl"><a data-link-type="idl" href="#enumdef-userverificationrequirement" id="ref-for-enumdef-userverificationrequirement①">UserVerificationRequirement</a></code> for the description of <code class="idl"><a data-link-type="idl" href="#dom-authenticatorselectioncriteria-userverification" id="ref-for-dom-authenticatorselectioncriteria-userverification④">userVerification</a></code>'s values and semantics.</p>
     </dl>
    </div>
    <h4 class="heading settled" data-level="5.4.5" id="enum-attachment"><span class="secno">5.4.5. </span><span class="content">Authenticator Attachment Enumeration (enum <dfn class="dfn-paneled idl-code" data-dfn-type="enum" data-export id="enumdef-authenticatorattachment"><code>AuthenticatorAttachment</code></dfn>)</span><a class="self-link" href="#enum-attachment"></a></h4>
-   <p>This enumeration’s values describe <a data-link-type="dfn" href="#authenticator" id="ref-for-authenticator①⓪⑤">authenticators</a>' <a data-link-type="dfn" href="#authenticator-attachment-modality" id="ref-for-authenticator-attachment-modality⑥">attachment modalities</a>. <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party①②⑨">Relying Parties</a> use this to express a preferred <a data-link-type="dfn" href="#authenticator-attachment-modality" id="ref-for-authenticator-attachment-modality⑦">authenticator attachment modality</a> when calling <code class="idl"><a data-link-type="idl" href="https://w3c.github.io/webappsec-credential-management/#dom-credentialscontainer-create" id="ref-for-dom-credentialscontainer-create①⑧">navigator.credentials.create()</a></code> to <a href="#sctn-createCredential">create a credential</a>, and <a data-link-type="dfn" href="#client" id="ref-for-client④③">clients</a> use this to report the <a data-link-type="dfn" href="#authenticator-attachment-modality" id="ref-for-authenticator-attachment-modality⑧">authenticator attachment modality</a> used to complete a <a data-link-type="dfn" href="#registration-ceremony" id="ref-for-registration-ceremony④">registration</a> or <a data-link-type="dfn" href="#authentication-ceremony" id="ref-for-authentication-ceremony①②">authentication ceremony</a>.</p>
+   <p>This enumeration’s values describe <a data-link-type="dfn" href="#authenticator" id="ref-for-authenticator①⓪⑤">authenticators</a>' <a data-link-type="dfn" href="#authenticator-attachment-modality" id="ref-for-authenticator-attachment-modality⑥">attachment modalities</a>. <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party①③④">Relying Parties</a> use this to express a preferred <a data-link-type="dfn" href="#authenticator-attachment-modality" id="ref-for-authenticator-attachment-modality⑦">authenticator attachment modality</a> when calling <code class="idl"><a data-link-type="idl" href="https://w3c.github.io/webappsec-credential-management/#dom-credentialscontainer-create" id="ref-for-dom-credentialscontainer-create①⑧">navigator.credentials.create()</a></code> to <a href="#sctn-createCredential">create a credential</a>, and <a data-link-type="dfn" href="#client" id="ref-for-client④③">clients</a> use this to report the <a data-link-type="dfn" href="#authenticator-attachment-modality" id="ref-for-authenticator-attachment-modality⑧">authenticator attachment modality</a> used to complete a <a data-link-type="dfn" href="#registration-ceremony" id="ref-for-registration-ceremony⑤">registration</a> or <a data-link-type="dfn" href="#authentication-ceremony" id="ref-for-authentication-ceremony①③">authentication ceremony</a>.</p>
 <pre class="idl highlight def"><c- b>enum</c-> <a class="idl-code" data-link-type="enum" href="#enumdef-authenticatorattachment" id="ref-for-enumdef-authenticatorattachment④"><c- g>AuthenticatorAttachment</c-></a> {
     <a class="idl-code" data-link-type="enum-value" href="#dom-authenticatorattachment-platform" id="ref-for-dom-authenticatorattachment-platform"><c- s>"platform"</c-></a>,
     <a class="idl-code" data-link-type="enum-value" href="#dom-authenticatorattachment-cross-platform" id="ref-for-dom-authenticatorattachment-cross-platform"><c- s>"cross-platform"</c-></a>
@@ -3432,9 +3490,9 @@ <h4 class="heading settled" data-level="5.4.5" id="enum-attachment"><span class=
     </dl>
    </div>
    <p class="note" role="note"><span>Note:</span> An <a data-link-type="dfn" href="#authenticator-attachment-modality" id="ref-for-authenticator-attachment-modality⑨">authenticator attachment modality</a> selection option is available only in the <code class="idl"><a data-link-type="idl" href="#dom-publickeycredential-create-slot" id="ref-for-dom-publickeycredential-create-slot③">[[Create]](origin, options,
-sameOriginWithAncestors)</a></code> operation. The <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party①③⓪">Relying Party</a> may use it to, for example, ensure the user has a <a data-link-type="dfn" href="#roaming-credential" id="ref-for-roaming-credential">roaming credential</a> for
+sameOriginWithAncestors)</a></code> operation. The <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party①③⑤">Relying Party</a> may use it to, for example, ensure the user has a <a data-link-type="dfn" href="#roaming-credential" id="ref-for-roaming-credential">roaming credential</a> for
 authenticating on another <a data-link-type="dfn" href="#client-device" id="ref-for-client-device①⑥">client device</a>; or to specifically register a <a data-link-type="dfn" href="#platform-credential" id="ref-for-platform-credential">platform credential</a> for easier reauthentication using a
-particular <a data-link-type="dfn" href="#client-device" id="ref-for-client-device①⑦">client device</a>. The <code class="idl"><a data-link-type="idl" href="#dom-publickeycredential-discoverfromexternalsource-slot" id="ref-for-dom-publickeycredential-discoverfromexternalsource-slot⑤">[[DiscoverFromExternalSource]](origin, options, sameOriginWithAncestors)</a></code> operation has no <a data-link-type="dfn" href="#authenticator-attachment-modality" id="ref-for-authenticator-attachment-modality①⓪">authenticator attachment modality</a> selection option, so the <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party①③①">Relying Party</a> SHOULD accept any of the user’s registered <a data-link-type="dfn" href="#public-key-credential" id="ref-for-public-key-credential③③">credentials</a>. The <a data-link-type="dfn" href="#client" id="ref-for-client④④">client</a> and user will then use whichever is available and convenient at the time.</p>
+particular <a data-link-type="dfn" href="#client-device" id="ref-for-client-device①⑦">client device</a>. The <code class="idl"><a data-link-type="idl" href="#dom-publickeycredential-discoverfromexternalsource-slot" id="ref-for-dom-publickeycredential-discoverfromexternalsource-slot⑤">[[DiscoverFromExternalSource]](origin, options, sameOriginWithAncestors)</a></code> operation has no <a data-link-type="dfn" href="#authenticator-attachment-modality" id="ref-for-authenticator-attachment-modality①⓪">authenticator attachment modality</a> selection option, so the <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party①③⑥">Relying Party</a> SHOULD accept any of the user’s registered <a data-link-type="dfn" href="#public-key-credential" id="ref-for-public-key-credential③③">credentials</a>. The <a data-link-type="dfn" href="#client" id="ref-for-client④④">client</a> and user will then use whichever is available and convenient at the time.</p>
    <h4 class="heading settled" data-level="5.4.6" id="enum-residentKeyRequirement"><span class="secno">5.4.6. </span><span class="content">Resident Key Requirement Enumeration (enum <dfn class="dfn-paneled idl-code" data-dfn-type="enum" data-export id="enumdef-residentkeyrequirement"><code>ResidentKeyRequirement</code></dfn>)</span><a class="self-link" href="#enum-residentKeyRequirement"></a></h4>
 <pre class="idl highlight def"><c- b>enum</c-> <a class="idl-code" data-link-type="enum" href="#enumdef-residentkeyrequirement" id="ref-for-enumdef-residentkeyrequirement②"><c- g>ResidentKeyRequirement</c-></a> {
     <a class="idl-code" data-link-type="enum-value" href="#dom-residentkeyrequirement-discouraged" id="ref-for-dom-residentkeyrequirement-discouraged③"><c- s>"discouraged"</c-></a>,
@@ -3443,26 +3501,26 @@ <h4 class="heading settled" data-level="5.4.6" id="enum-residentKeyRequirement">
 };
 </pre>
    <p class="note" role="note"><span>Note:</span> The <code class="idl"><a data-link-type="idl" href="#enumdef-residentkeyrequirement" id="ref-for-enumdef-residentkeyrequirement③">ResidentKeyRequirement</a></code> enumeration is deliberately not referenced, see <a href="#sct-domstring-backwards-compatibility">§ 2.1.1 Enumerations as DOMString types</a>.</p>
-   <p>This enumeration’s values describe the <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party①③②">Relying Party</a>'s requirements for <a data-link-type="dfn" href="#client-side-discoverable-credential" id="ref-for-client-side-discoverable-credential⑦">client-side discoverable credentials</a> (formerly known as <a data-link-type="dfn" href="#resident-credential" id="ref-for-resident-credential①">resident credentials</a> or <a data-link-type="dfn" href="#resident-key" id="ref-for-resident-key②">resident keys</a>):</p>
+   <p>This enumeration’s values describe the <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party①③⑦">Relying Party</a>'s requirements for <a data-link-type="dfn" href="#client-side-discoverable-credential" id="ref-for-client-side-discoverable-credential⑦">client-side discoverable credentials</a> (formerly known as <a data-link-type="dfn" href="#resident-credential" id="ref-for-resident-credential①">resident credentials</a> or <a data-link-type="dfn" href="#resident-key" id="ref-for-resident-key②">resident keys</a>):</p>
    <div>
     <dl>
      <dt data-md><dfn class="dfn-paneled idl-code" data-dfn-for="ResidentKeyRequirement" data-dfn-type="enum-value" data-export data-lt="&quot;discouraged&quot;|discouraged" id="dom-residentkeyrequirement-discouraged"><code>discouraged</code></dfn>
      <dd data-md>
-      <p>The <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party①③③">Relying Party</a> prefers creating a <a data-link-type="dfn" href="#server-side-credential" id="ref-for-server-side-credential⑥">server-side credential</a>, but will accept a <a data-link-type="dfn" href="#client-side-discoverable-credential" id="ref-for-client-side-discoverable-credential⑧">client-side discoverable credential</a>.
+      <p>The <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party①③⑧">Relying Party</a> prefers creating a <a data-link-type="dfn" href="#server-side-credential" id="ref-for-server-side-credential⑥">server-side credential</a>, but will accept a <a data-link-type="dfn" href="#client-side-discoverable-credential" id="ref-for-client-side-discoverable-credential⑧">client-side discoverable credential</a>.
 The <a data-link-type="dfn" href="#client" id="ref-for-client④⑤">client</a> and <a data-link-type="dfn" href="#authenticator" id="ref-for-authenticator①⓪⑥">authenticator</a> SHOULD create a <a data-link-type="dfn" href="#server-side-credential" id="ref-for-server-side-credential⑦">server-side credential</a> if possible.</p>
-      <p class="note" role="note"><span>Note:</span> A <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party①③④">Relying Party</a> cannot require that a created credential is a <a data-link-type="dfn" href="#server-side-credential" id="ref-for-server-side-credential⑧">server-side credential</a> and the <a data-link-type="dfn" href="#credprops" id="ref-for-credprops①">Credential Properties Extension</a> may not return a value for the <code class="idl"><a data-link-type="idl" href="#dom-credentialpropertiesoutput-rk" id="ref-for-dom-credentialpropertiesoutput-rk">rk</a></code> property. Because of this, it may be the case that it does not know if a credential is a <a data-link-type="dfn" href="#server-side-credential" id="ref-for-server-side-credential⑨">server-side credential</a> or not and thus does not know whether creating a second credential with the same <a data-link-type="dfn" href="#user-handle" id="ref-for-user-handle①⑦">user handle</a> will evict the first.</p>
+      <p class="note" role="note"><span>Note:</span> A <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party①③⑨">Relying Party</a> cannot require that a created credential is a <a data-link-type="dfn" href="#server-side-credential" id="ref-for-server-side-credential⑧">server-side credential</a> and the <a data-link-type="dfn" href="#credprops" id="ref-for-credprops①">Credential Properties Extension</a> may not return a value for the <code class="idl"><a data-link-type="idl" href="#dom-credentialpropertiesoutput-rk" id="ref-for-dom-credentialpropertiesoutput-rk">rk</a></code> property. Because of this, it may be the case that it does not know if a credential is a <a data-link-type="dfn" href="#server-side-credential" id="ref-for-server-side-credential⑨">server-side credential</a> or not and thus does not know whether creating a second credential with the same <a data-link-type="dfn" href="#user-handle" id="ref-for-user-handle①⑦">user handle</a> will evict the first.</p>
      <dt data-md><dfn class="dfn-paneled idl-code" data-dfn-for="ResidentKeyRequirement" data-dfn-type="enum-value" data-export data-lt="&quot;preferred&quot;|preferred" id="dom-residentkeyrequirement-preferred"><code>preferred</code></dfn>
      <dd data-md>
-      <p>The <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party①③⑤">Relying Party</a> strongly prefers creating a <a data-link-type="dfn" href="#client-side-discoverable-credential" id="ref-for-client-side-discoverable-credential⑨">client-side discoverable credential</a>, but will accept a <a data-link-type="dfn" href="#server-side-credential" id="ref-for-server-side-credential①⓪">server-side credential</a>.
+      <p>The <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party①④⓪">Relying Party</a> strongly prefers creating a <a data-link-type="dfn" href="#client-side-discoverable-credential" id="ref-for-client-side-discoverable-credential⑨">client-side discoverable credential</a>, but will accept a <a data-link-type="dfn" href="#server-side-credential" id="ref-for-server-side-credential①⓪">server-side credential</a>.
 The <a data-link-type="dfn" href="#client" id="ref-for-client④⑥">client</a> and <a data-link-type="dfn" href="#authenticator" id="ref-for-authenticator①⓪⑦">authenticator</a> SHOULD create a <a data-link-type="dfn" href="#discoverable-credential" id="ref-for-discoverable-credential⑦">discoverable credential</a> if possible.
 For example, the <a data-link-type="dfn" href="#client" id="ref-for-client④⑦">client</a> SHOULD guide the user through setting up <a data-link-type="dfn" href="#user-verification" id="ref-for-user-verification①⑨">user verification</a> if needed to create a <a data-link-type="dfn" href="#discoverable-credential" id="ref-for-discoverable-credential⑧">discoverable credential</a>. This takes precedence over the setting of <code class="idl"><a data-link-type="idl" href="#dom-authenticatorselectioncriteria-userverification" id="ref-for-dom-authenticatorselectioncriteria-userverification⑤">userVerification</a></code>.</p>
      <dt data-md><dfn class="dfn-paneled idl-code" data-dfn-for="ResidentKeyRequirement" data-dfn-type="enum-value" data-export data-lt="&quot;required&quot;|required" id="dom-residentkeyrequirement-required"><code>required</code></dfn>
      <dd data-md>
-      <p>The <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party①③⑥">Relying Party</a> requires a <a data-link-type="dfn" href="#client-side-discoverable-credential" id="ref-for-client-side-discoverable-credential①⓪">client-side discoverable credential</a>.
+      <p>The <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party①④①">Relying Party</a> requires a <a data-link-type="dfn" href="#client-side-discoverable-credential" id="ref-for-client-side-discoverable-credential①⓪">client-side discoverable credential</a>.
 The <a data-link-type="dfn" href="#client" id="ref-for-client④⑧">client</a> MUST return an error if a <a data-link-type="dfn" href="#client-side-discoverable-credential" id="ref-for-client-side-discoverable-credential①①">client-side discoverable credential</a> cannot be created.</p>
     </dl>
    </div>
-   <p class="note" role="note"><span>Note:</span> The <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party①③⑦">Relying Party</a> can seek information on whether or not the authenticator created a <a data-link-type="dfn" href="#client-side-discoverable-credential" id="ref-for-client-side-discoverable-credential①②">client-side discoverable credential</a> using the <a data-link-type="dfn" href="#credentialpropertiesoutput-resident-key-credential-property" id="ref-for-credentialpropertiesoutput-resident-key-credential-property">resident key credential property</a> of the <a data-link-type="dfn" href="#credprops" id="ref-for-credprops②">Credential Properties Extension</a>.
+   <p class="note" role="note"><span>Note:</span> The <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party①④②">Relying Party</a> can seek information on whether or not the authenticator created a <a data-link-type="dfn" href="#client-side-discoverable-credential" id="ref-for-client-side-discoverable-credential①②">client-side discoverable credential</a> using the <a data-link-type="dfn" href="#credentialpropertiesoutput-resident-key-credential-property" id="ref-for-credentialpropertiesoutput-resident-key-credential-property">resident key credential property</a> of the <a data-link-type="dfn" href="#credprops" id="ref-for-credprops②">Credential Properties Extension</a>.
 This is useful when values of <code class="idl"><a data-link-type="idl" href="#dom-residentkeyrequirement-discouraged" id="ref-for-dom-residentkeyrequirement-discouraged④">discouraged</a></code> or <code class="idl"><a data-link-type="idl" href="#dom-residentkeyrequirement-preferred" id="ref-for-dom-residentkeyrequirement-preferred③">preferred</a></code> are used for <code><var>options</var>.<code class="idl"><a data-link-type="idl" href="#dom-publickeycredentialcreationoptions-authenticatorselection" id="ref-for-dom-publickeycredentialcreationoptions-authenticatorselection①⓪">authenticatorSelection</a></code>.<code class="idl"><a data-link-type="idl" href="#dom-authenticatorselectioncriteria-residentkey" id="ref-for-dom-authenticatorselectioncriteria-residentkey⑤">residentKey</a></code></code>, because in those cases it is possible for an <a data-link-type="dfn" href="#authenticator" id="ref-for-authenticator①⓪⑧">authenticator</a> to create <em>either</em> a <a data-link-type="dfn" href="#client-side-discoverable-credential" id="ref-for-client-side-discoverable-credential①③">client-side discoverable credential</a> or a <a data-link-type="dfn" href="#server-side-credential" id="ref-for-server-side-credential①①">server-side credential</a>.</p>
    <h4 class="heading settled" data-level="5.4.7" id="enum-attestation-convey"><span class="secno">5.4.7. </span><span class="content"><dfn class="dfn-paneled" data-dfn-type="dfn" data-noexport id="attestation-conveyance">Attestation Conveyance</dfn> Preference Enumeration (enum <dfn class="dfn-paneled idl-code" data-dfn-type="enum" data-export id="enumdef-attestationconveyancepreference"><code>AttestationConveyancePreference</code></dfn>)</span><a class="self-link" href="#enum-attestation-convey"></a></h4>
    <p><a data-link-type="dfn" href="#webauthn-relying-party" id="ref-for-webauthn-relying-party②⓪">WebAuthn Relying Parties</a> may use <code class="idl"><a data-link-type="idl" href="#enumdef-attestationconveyancepreference" id="ref-for-enumdef-attestationconveyancepreference①">AttestationConveyancePreference</a></code> to specify their preference regarding <a data-link-type="dfn" href="#attestation-conveyance" id="ref-for-attestation-conveyance②">attestation conveyance</a> during credential generation.</p>
@@ -3478,27 +3536,27 @@ <h4 class="heading settled" data-level="5.4.7" id="enum-attestation-convey"><spa
     <dl>
      <dt data-md><dfn class="dfn-paneled idl-code" data-dfn-for="AttestationConveyancePreference" data-dfn-type="enum-value" data-export data-lt="&quot;none&quot;|none" id="dom-attestationconveyancepreference-none"><code>none</code></dfn>
      <dd data-md>
-      <p>The <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party①③⑧">Relying Party</a> is not interested in <a data-link-type="dfn" href="#authenticator" id="ref-for-authenticator①⓪⑨">authenticator</a> <a data-link-type="dfn" href="#attestation" id="ref-for-attestation⑧">attestation</a>. For example, in order to
-potentially avoid having to obtain <a data-link-type="dfn" href="#user-consent" id="ref-for-user-consent①②">user consent</a> to relay identifying information to the <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party①③⑨">Relying Party</a>, or to save a
+      <p>The <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party①④③">Relying Party</a> is not interested in <a data-link-type="dfn" href="#authenticator" id="ref-for-authenticator①⓪⑨">authenticator</a> <a data-link-type="dfn" href="#attestation" id="ref-for-attestation⑧">attestation</a>. For example, in order to
+potentially avoid having to obtain <a data-link-type="dfn" href="#user-consent" id="ref-for-user-consent①②">user consent</a> to relay identifying information to the <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party①④④">Relying Party</a>, or to save a
 roundtrip to an <a data-link-type="dfn" href="#attestation-ca" id="ref-for-attestation-ca">Attestation CA</a> or <a data-link-type="dfn" href="#anonymization-ca" id="ref-for-anonymization-ca①">Anonymization CA</a>.
-If the <a data-link-type="dfn" href="#authenticator" id="ref-for-authenticator①①⓪">authenticator</a> generates an <a data-link-type="dfn" href="#attestation-statement" id="ref-for-attestation-statement⑦">attestation statement</a> that is not a <a data-link-type="dfn" href="#self-attestation" id="ref-for-self-attestation⑤">self attestation</a>,
+If the <a data-link-type="dfn" href="#authenticator" id="ref-for-authenticator①①⓪">authenticator</a> generates an <a data-link-type="dfn" href="#attestation-statement" id="ref-for-attestation-statement⑧">attestation statement</a> that is not a <a data-link-type="dfn" href="#self-attestation" id="ref-for-self-attestation⑤">self attestation</a>,
 the <a data-link-type="dfn" href="#client" id="ref-for-client④⑨">client</a> will replace it with a <a data-link-type="dfn" href="#none" id="ref-for-none">None</a> attestation statement.</p>
       <p>This is the default, and unknown values fall back to the behavior of this value.</p>
      <dt data-md><dfn class="dfn-paneled idl-code" data-dfn-for="AttestationConveyancePreference" data-dfn-type="enum-value" data-export data-lt="&quot;indirect&quot;|indirect" id="dom-attestationconveyancepreference-indirect"><code>indirect</code></dfn>
      <dd data-md>
-      <p>The <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party①④⓪">Relying Party</a> wants to receive a verifiable <a data-link-type="dfn" href="#attestation-statement" id="ref-for-attestation-statement⑧">attestation statement</a>,
-but allows the <a data-link-type="dfn" href="#client" id="ref-for-client⑤⓪">client</a> to decide how to obtain such an <a data-link-type="dfn" href="#attestation-statement" id="ref-for-attestation-statement⑨">attestation statement</a>.
-The client MAY replace an authenticator-generated <a data-link-type="dfn" href="#attestation-statement" id="ref-for-attestation-statement①⓪">attestation statement</a> with one generated by an <a data-link-type="dfn" href="#anonymization-ca" id="ref-for-anonymization-ca②">Anonymization CA</a>,
-in order to protect the user’s privacy, or to assist <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party①④①">Relying Parties</a> with attestation verification in a heterogeneous ecosystem.</p>
-      <p class="note" role="note"><span>Note:</span> There is no guarantee that the <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party①④②">Relying Party</a> will obtain a verifiable <a data-link-type="dfn" href="#attestation-statement" id="ref-for-attestation-statement①①">attestation statement</a> in this case.
-For example, in the case that the authenticator employs <a data-link-type="dfn" href="#self-attestation" id="ref-for-self-attestation⑥">self attestation</a> and the <a data-link-type="dfn" href="#client" id="ref-for-client⑤①">client</a> passes the <a data-link-type="dfn" href="#attestation-statement" id="ref-for-attestation-statement①②">attestation statement</a> through unmodified.</p>
+      <p>The <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party①④⑤">Relying Party</a> wants to receive a verifiable <a data-link-type="dfn" href="#attestation-statement" id="ref-for-attestation-statement⑨">attestation statement</a>,
+but allows the <a data-link-type="dfn" href="#client" id="ref-for-client⑤⓪">client</a> to decide how to obtain such an <a data-link-type="dfn" href="#attestation-statement" id="ref-for-attestation-statement①⓪">attestation statement</a>.
+The client MAY replace an authenticator-generated <a data-link-type="dfn" href="#attestation-statement" id="ref-for-attestation-statement①①">attestation statement</a> with one generated by an <a data-link-type="dfn" href="#anonymization-ca" id="ref-for-anonymization-ca②">Anonymization CA</a>,
+in order to protect the user’s privacy, or to assist <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party①④⑥">Relying Parties</a> with attestation verification in a heterogeneous ecosystem.</p>
+      <p class="note" role="note"><span>Note:</span> There is no guarantee that the <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party①④⑦">Relying Party</a> will obtain a verifiable <a data-link-type="dfn" href="#attestation-statement" id="ref-for-attestation-statement①②">attestation statement</a> in this case.
+For example, in the case that the authenticator employs <a data-link-type="dfn" href="#self-attestation" id="ref-for-self-attestation⑥">self attestation</a> and the <a data-link-type="dfn" href="#client" id="ref-for-client⑤①">client</a> passes the <a data-link-type="dfn" href="#attestation-statement" id="ref-for-attestation-statement①③">attestation statement</a> through unmodified.</p>
      <dt data-md><dfn class="dfn-paneled idl-code" data-dfn-for="AttestationConveyancePreference" data-dfn-type="enum-value" data-export data-lt="&quot;direct&quot;|direct" id="dom-attestationconveyancepreference-direct"><code>direct</code></dfn>
      <dd data-md>
-      <p>The <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party①④③">Relying Party</a> wants to receive the <a data-link-type="dfn" href="#attestation-statement" id="ref-for-attestation-statement①③">attestation statement</a> as generated by the <a data-link-type="dfn" href="#authenticator" id="ref-for-authenticator①①①">authenticator</a>.</p>
+      <p>The <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party①④⑧">Relying Party</a> wants to receive the <a data-link-type="dfn" href="#attestation-statement" id="ref-for-attestation-statement①④">attestation statement</a> as generated by the <a data-link-type="dfn" href="#authenticator" id="ref-for-authenticator①①①">authenticator</a>.</p>
      <dt data-md><dfn class="dfn-paneled idl-code" data-dfn-for="AttestationConveyancePreference" data-dfn-type="enum-value" data-export data-lt="&quot;enterprise&quot;|enterprise" id="dom-attestationconveyancepreference-enterprise"><code>enterprise</code></dfn>
      <dd data-md>
-      <p>The <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party①④④">Relying Party</a> wants to receive an <a data-link-type="dfn" href="#attestation-statement" id="ref-for-attestation-statement①④">attestation statement</a> that may include uniquely identifying information. This is intended for controlled deployments within an enterprise where the organization wishes to tie registrations to specific authenticators. User agents MUST NOT provide such an attestation unless the user agent or authenticator configuration permits it for the requested <a data-link-type="dfn" href="#rp-id" id="ref-for-rp-id②④">RP ID</a>.</p>
-      <p>If permitted, the user agent SHOULD signal to the authenticator (at <a href="#CreateCred-InvokeAuthnrMakeCred">invocation time</a>) that enterprise attestation is requested, and convey the resulting <a data-link-type="dfn" href="#authdata-attestedcredentialdata-aaguid" id="ref-for-authdata-attestedcredentialdata-aaguid⑤">AAGUID</a> and <a data-link-type="dfn" href="#attestation-statement" id="ref-for-attestation-statement①⑤">attestation statement</a>, unaltered, to the <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party①④⑤">Relying Party</a>.</p>
+      <p>The <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party①④⑨">Relying Party</a> wants to receive an <a data-link-type="dfn" href="#attestation-statement" id="ref-for-attestation-statement①⑤">attestation statement</a> that may include uniquely identifying information. This is intended for controlled deployments within an enterprise where the organization wishes to tie registrations to specific authenticators. User agents MUST NOT provide such an attestation unless the user agent or authenticator configuration permits it for the requested <a data-link-type="dfn" href="#rp-id" id="ref-for-rp-id②④">RP ID</a>.</p>
+      <p>If permitted, the user agent SHOULD signal to the authenticator (at <a href="#CreateCred-InvokeAuthnrMakeCred">invocation time</a>) that enterprise attestation is requested, and convey the resulting <a data-link-type="dfn" href="#authdata-attestedcredentialdata-aaguid" id="ref-for-authdata-attestedcredentialdata-aaguid⑤">AAGUID</a> and <a data-link-type="dfn" href="#attestation-statement" id="ref-for-attestation-statement①⑥">attestation statement</a>, unaltered, to the <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party①⑤⓪">Relying Party</a>.</p>
     </dl>
    </div>
    <h3 class="heading settled" data-level="5.5" id="dictionary-assertion-options"><span class="secno">5.5. </span><span class="content">Options for Assertion Generation (dictionary <dfn class="dfn-paneled idl-code" data-dfn-type="dictionary" data-export id="dictdef-publickeycredentialrequestoptions"><code>PublicKeyCredentialRequestOptions</code></dfn>)</span><a class="self-link" href="#dictionary-assertion-options"></a></h3>
@@ -3508,7 +3566,7 @@ <h3 class="heading settled" data-level="5.5" id="dictionary-assertion-options"><
     <c- b>required</c-> <a data-link-type="idl-name" href="https://webidl.spec.whatwg.org/#BufferSource" id="ref-for-BufferSource⑥"><c- n>BufferSource</c-></a>                <a class="idl-code" data-link-type="dict-member" data-type="BufferSource                " href="#dom-publickeycredentialrequestoptions-challenge" id="ref-for-dom-publickeycredentialrequestoptions-challenge②"><c- g>challenge</c-></a>;
     <a class="idl-code" data-link-type="interface" href="https://webidl.spec.whatwg.org/#idl-unsigned-long" id="ref-for-idl-unsigned-long④"><c- b>unsigned</c-> <c- b>long</c-></a>                        <a class="idl-code" data-link-type="dict-member" data-type="unsigned long                        " href="#dom-publickeycredentialrequestoptions-timeout" id="ref-for-dom-publickeycredentialrequestoptions-timeout③"><c- g>timeout</c-></a>;
     <a class="idl-code" data-link-type="interface" href="https://webidl.spec.whatwg.org/#idl-USVString" id="ref-for-idl-USVString"><c- b>USVString</c-></a>                            <a class="idl-code" data-link-type="dict-member" data-type="USVString                            " href="#dom-publickeycredentialrequestoptions-rpid" id="ref-for-dom-publickeycredentialrequestoptions-rpid④"><c- g>rpId</c-></a>;
-    <a data-link-type="dfn" href="https://webidl.spec.whatwg.org/#idl-sequence" id="ref-for-idl-sequence⑧"><c- b>sequence</c-></a>&lt;<a data-link-type="idl-name" href="#dictdef-publickeycredentialdescriptor" id="ref-for-dictdef-publickeycredentialdescriptor⑥"><c- n>PublicKeyCredentialDescriptor</c-></a>> <a class="idl-code" data-default="[]" data-link-type="dict-member" data-type="sequence<PublicKeyCredentialDescriptor> " href="#dom-publickeycredentialrequestoptions-allowcredentials" id="ref-for-dom-publickeycredentialrequestoptions-allowcredentials①③"><c- g>allowCredentials</c-></a> = [];
+    <a data-link-type="dfn" href="https://webidl.spec.whatwg.org/#idl-sequence" id="ref-for-idl-sequence⑧"><c- b>sequence</c-></a>&lt;<a data-link-type="idl-name" href="#dictdef-publickeycredentialdescriptor" id="ref-for-dictdef-publickeycredentialdescriptor⑦"><c- n>PublicKeyCredentialDescriptor</c-></a>> <a class="idl-code" data-default="[]" data-link-type="dict-member" data-type="sequence<PublicKeyCredentialDescriptor> " href="#dom-publickeycredentialrequestoptions-allowcredentials" id="ref-for-dom-publickeycredentialrequestoptions-allowcredentials①③"><c- g>allowCredentials</c-></a> = [];
     <a class="idl-code" data-link-type="interface" href="https://webidl.spec.whatwg.org/#idl-DOMString" id="ref-for-idl-DOMString③⑨"><c- b>DOMString</c-></a>                            <a class="idl-code" data-default="&quot;preferred&quot;" data-link-type="dict-member" data-type="DOMString                            " href="#dom-publickeycredentialrequestoptions-userverification" id="ref-for-dom-publickeycredentialrequestoptions-userverification③"><c- g>userVerification</c-></a> = "preferred";
     <a data-link-type="idl-name" href="#dictdef-authenticationextensionsclientinputs" id="ref-for-dictdef-authenticationextensionsclientinputs②"><c- n>AuthenticationExtensionsClientInputs</c-></a> <a class="idl-code" data-link-type="dict-member" data-type="AuthenticationExtensionsClientInputs " href="#dom-publickeycredentialrequestoptions-extensions" id="ref-for-dom-publickeycredentialrequestoptions-extensions③"><c- g>extensions</c-></a>;
 };
@@ -3519,37 +3577,37 @@ <h3 class="heading settled" data-level="5.5" id="dictionary-assertion-options"><
      <p>This member specifies a challenge that the <a data-link-type="dfn" href="#authenticator" id="ref-for-authenticator①①②">authenticator</a> signs, along with other data, when producing an <a data-link-type="dfn" href="#authentication-assertion" id="ref-for-authentication-assertion①②">authentication assertion</a>. See the <a href="#sctn-cryptographic-challenges">§ 13.4.3 Cryptographic Challenges</a> security consideration.</p>
     <dt data-md><dfn class="dfn-paneled idl-code" data-dfn-for="PublicKeyCredentialRequestOptions" data-dfn-type="dict-member" data-export id="dom-publickeycredentialrequestoptions-timeout"><code>timeout</code></dfn>, <span> of type <a data-link-type="idl-name" href="https://webidl.spec.whatwg.org/#idl-unsigned-long" id="ref-for-idl-unsigned-long⑤">unsigned long</a></span>
     <dd data-md>
-     <p>This OPTIONAL member specifies a time, in milliseconds, that the <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party①④⑥">Relying Party</a> is willing to wait for the call to complete.
+     <p>This OPTIONAL member specifies a time, in milliseconds, that the <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party①⑤①">Relying Party</a> is willing to wait for the call to complete.
 The value is treated as a hint, and MAY be overridden by the <a data-link-type="dfn" href="#client" id="ref-for-client⑤②">client</a>.</p>
     <dt data-md><dfn class="dfn-paneled idl-code" data-dfn-for="PublicKeyCredentialRequestOptions" data-dfn-type="dict-member" data-export id="dom-publickeycredentialrequestoptions-rpid"><code>rpId</code></dfn>, <span> of type <a data-link-type="idl-name" href="https://webidl.spec.whatwg.org/#idl-USVString" id="ref-for-idl-USVString①">USVString</a></span>
     <dd data-md>
-     <p>This OPTIONAL member specifies the <a data-link-type="dfn" href="#rp-id" id="ref-for-rp-id②⑤">RP ID</a> claimed by the <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party①④⑦">Relying Party</a>.
-The <a data-link-type="dfn" href="#client" id="ref-for-client⑤③">client</a> MUST verify that the <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party①④⑧">Relying Party</a>'s <a data-link-type="dfn" href="https://html.spec.whatwg.org/multipage/origin.html#concept-origin" id="ref-for-concept-origin①①">origin</a> matches the <a data-link-type="dfn" href="#scope" id="ref-for-scope①②">scope</a> of this <a data-link-type="dfn" href="#rp-id" id="ref-for-rp-id②⑥">RP ID</a>.
+     <p>This OPTIONAL member specifies the <a data-link-type="dfn" href="#rp-id" id="ref-for-rp-id②⑤">RP ID</a> claimed by the <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party①⑤②">Relying Party</a>.
+The <a data-link-type="dfn" href="#client" id="ref-for-client⑤③">client</a> MUST verify that the <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party①⑤③">Relying Party</a>'s <a data-link-type="dfn" href="https://html.spec.whatwg.org/multipage/origin.html#concept-origin" id="ref-for-concept-origin①①">origin</a> matches the <a data-link-type="dfn" href="#scope" id="ref-for-scope①②">scope</a> of this <a data-link-type="dfn" href="#rp-id" id="ref-for-rp-id②⑥">RP ID</a>.
 The <a data-link-type="dfn" href="#authenticator" id="ref-for-authenticator①①③">authenticator</a> MUST verify
-that this <a data-link-type="dfn" href="#rp-id" id="ref-for-rp-id②⑦">RP ID</a> exactly equals the <a data-link-type="dfn" href="#public-key-credential-source-rpid" id="ref-for-public-key-credential-source-rpid">rpId</a> of the <a data-link-type="dfn" href="https://w3c.github.io/webappsec-credential-management/#concept-credential" id="ref-for-concept-credential①②">credential</a> to be used for the <a data-link-type="dfn" href="#authentication-ceremony" id="ref-for-authentication-ceremony①③">authentication ceremony</a>.</p>
+that this <a data-link-type="dfn" href="#rp-id" id="ref-for-rp-id②⑦">RP ID</a> exactly equals the <a data-link-type="dfn" href="#public-key-credential-source-rpid" id="ref-for-public-key-credential-source-rpid">rpId</a> of the <a data-link-type="dfn" href="https://w3c.github.io/webappsec-credential-management/#concept-credential" id="ref-for-concept-credential①②">credential</a> to be used for the <a data-link-type="dfn" href="#authentication-ceremony" id="ref-for-authentication-ceremony①④">authentication ceremony</a>.</p>
      <p>If not specified, its value will
 be the <code class="idl"><a data-link-type="idl" href="https://w3c.github.io/webappsec-credential-management/#credentialscontainer" id="ref-for-credentialscontainer②">CredentialsContainer</a></code> object’s <a data-link-type="dfn" href="https://html.spec.whatwg.org/multipage/webappapis.html#relevant-settings-object" id="ref-for-relevant-settings-object④">relevant settings object</a>'s <a data-link-type="dfn" href="https://html.spec.whatwg.org/multipage/webappapis.html#concept-settings-object-origin" id="ref-for-concept-settings-object-origin⑦">origin</a>'s <a data-link-type="dfn" href="https://html.spec.whatwg.org/multipage/origin.html#concept-origin-effective-domain" id="ref-for-concept-origin-effective-domain①③">effective domain</a>.</p>
-    <dt data-md><dfn class="dfn-paneled idl-code" data-dfn-for="PublicKeyCredentialRequestOptions" data-dfn-type="dict-member" data-export id="dom-publickeycredentialrequestoptions-allowcredentials"><code>allowCredentials</code></dfn>, <span> of type sequence&lt;<a data-link-type="idl-name" href="#dictdef-publickeycredentialdescriptor" id="ref-for-dictdef-publickeycredentialdescriptor⑦">PublicKeyCredentialDescriptor</a>>, defaulting to <code>[]</code></span>
+    <dt data-md><dfn class="dfn-paneled idl-code" data-dfn-for="PublicKeyCredentialRequestOptions" data-dfn-type="dict-member" data-export id="dom-publickeycredentialrequestoptions-allowcredentials"><code>allowCredentials</code></dfn>, <span> of type sequence&lt;<a data-link-type="idl-name" href="#dictdef-publickeycredentialdescriptor" id="ref-for-dictdef-publickeycredentialdescriptor⑧">PublicKeyCredentialDescriptor</a>>, defaulting to <code>[]</code></span>
     <dd data-md>
-     <p>This OPTIONAL member is used by the <a data-link-type="dfn" href="#client" id="ref-for-client⑤④">client</a> to find <a data-link-type="dfn" href="#authenticator" id="ref-for-authenticator①①④">authenticators</a> eligible for this <a data-link-type="dfn" href="#authentication-ceremony" id="ref-for-authentication-ceremony①④">authentication ceremony</a>.
+     <p>This OPTIONAL member is used by the <a data-link-type="dfn" href="#client" id="ref-for-client⑤④">client</a> to find <a data-link-type="dfn" href="#authenticator" id="ref-for-authenticator①①④">authenticators</a> eligible for this <a data-link-type="dfn" href="#authentication-ceremony" id="ref-for-authentication-ceremony①⑤">authentication ceremony</a>.
 It can be used in two ways:</p>
      <ul>
       <li data-md>
-       <p>If the <a data-link-type="dfn" href="#user-account" id="ref-for-user-account②①">user account</a> to authenticate is already identified (e.g., if the user has entered a username),
-then the <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party①④⑨">Relying Party</a> SHOULD use this member to list the <a data-link-type="dfn" href="https://w3c.github.io/webappsec-credential-management/#concept-credential" id="ref-for-concept-credential①③">credentials</a> <a data-link-type="dfn" href="#registration-ceremony" id="ref-for-registration-ceremony⑤">registered</a> to the <a data-link-type="dfn" href="#user-account" id="ref-for-user-account②②">user account</a>.
-This SHOULD usually include all of the <a data-link-type="dfn" href="#user-account" id="ref-for-user-account②③">user account’s</a> credentials.</p>
-       <p>The <a data-link-type="dfn" href="https://infra.spec.whatwg.org/#list-item" id="ref-for-list-item⑦">items</a> SHOULD specify <code class="idl"><a data-link-type="idl" href="#dom-publickeycredentialdescriptor-transports" id="ref-for-dom-publickeycredentialdescriptor-transports⑧">transports</a></code> whenever possible.
+       <p>If the <a data-link-type="dfn" href="#user-account" id="ref-for-user-account②③">user account</a> to authenticate is already identified (e.g., if the user has entered a username),
+then the <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party①⑤④">Relying Party</a> SHOULD use this member to list <a data-link-type="dfn" href="#credential-descriptor-for-a-credential-record" id="ref-for-credential-descriptor-for-a-credential-record">credential descriptors for credential records</a> in the <a data-link-type="dfn" href="#user-account" id="ref-for-user-account②④">user account</a>.
+This SHOULD usually include all <a data-link-type="dfn" href="#credential-record" id="ref-for-credential-record⑤">credential records</a> in the <a data-link-type="dfn" href="#user-account" id="ref-for-user-account②⑤">user account</a>.</p>
+       <p>The <a data-link-type="dfn" href="https://infra.spec.whatwg.org/#list-item" id="ref-for-list-item⑧">items</a> SHOULD specify <code class="idl"><a data-link-type="idl" href="#dom-publickeycredentialdescriptor-transports" id="ref-for-dom-publickeycredentialdescriptor-transports⑨">transports</a></code> whenever possible.
 This helps the <a data-link-type="dfn" href="#client" id="ref-for-client⑤⑤">client</a> optimize the user experience for any given situation.
-Also note that the <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party①⑤⓪">Relying Party</a> does not need to filter the list when requesting <a data-link-type="dfn" href="#user-verification" id="ref-for-user-verification②⓪">user verification</a> —
+Also note that the <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party①⑤⑤">Relying Party</a> does not need to filter the list when requesting <a data-link-type="dfn" href="#user-verification" id="ref-for-user-verification②⓪">user verification</a> —
 the <a data-link-type="dfn" href="#client" id="ref-for-client⑤⑥">client</a> will automatically ignore non-eligible credentials
 if <code class="idl"><a data-link-type="idl" href="#dom-publickeycredentialrequestoptions-userverification" id="ref-for-dom-publickeycredentialrequestoptions-userverification④">userVerification</a></code> is set to <code class="idl"><a data-link-type="idl" href="#dom-userverificationrequirement-required" id="ref-for-dom-userverificationrequirement-required⑥">required</a></code>.</p>
        <p>See also the <a href="#sctn-credential-id-privacy-leak">§ 14.6.3 Privacy leak via credential IDs</a> privacy consideration.</p>
       <li data-md>
-       <p>If the <a data-link-type="dfn" href="#user-account" id="ref-for-user-account②④">user account</a> to authenticate is not already identified,
-then the <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party①⑤①">Relying Party</a> MAY leave this member <a data-link-type="dfn" href="https://infra.spec.whatwg.org/#list-empty" id="ref-for-list-empty③">empty</a> or unspecified.
-In this case, only <a data-link-type="dfn" href="#discoverable-credential" id="ref-for-discoverable-credential⑨">discoverable credentials</a> will be utilized in this <a data-link-type="dfn" href="#authentication-ceremony" id="ref-for-authentication-ceremony①⑤">authentication ceremony</a>,
-and the <a data-link-type="dfn" href="#user-account" id="ref-for-user-account②⑤">user account</a> MAY be identified by the <code class="idl"><a data-link-type="idl" href="#dom-authenticatorassertionresponse-userhandle" id="ref-for-dom-authenticatorassertionresponse-userhandle⑤">userHandle</a></code> of the resulting <code class="idl"><a data-link-type="idl" href="#authenticatorassertionresponse" id="ref-for-authenticatorassertionresponse⑤">AuthenticatorAssertionResponse</a></code>.
-If the available <a data-link-type="dfn" href="#authenticator" id="ref-for-authenticator①①⑤">authenticators</a> <a data-link-type="dfn" href="#contains" id="ref-for-contains②">contain</a> more than one <a data-link-type="dfn" href="#discoverable-credential" id="ref-for-discoverable-credential①⓪">discoverable credential</a> <a data-link-type="dfn" href="#scope" id="ref-for-scope①③">scoped</a> to the <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party①⑤②">Relying Party</a>,
+       <p>If the <a data-link-type="dfn" href="#user-account" id="ref-for-user-account②⑥">user account</a> to authenticate is not already identified,
+then the <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party①⑤⑥">Relying Party</a> MAY leave this member <a data-link-type="dfn" href="https://infra.spec.whatwg.org/#list-empty" id="ref-for-list-empty③">empty</a> or unspecified.
+In this case, only <a data-link-type="dfn" href="#discoverable-credential" id="ref-for-discoverable-credential⑨">discoverable credentials</a> will be utilized in this <a data-link-type="dfn" href="#authentication-ceremony" id="ref-for-authentication-ceremony①⑥">authentication ceremony</a>,
+and the <a data-link-type="dfn" href="#user-account" id="ref-for-user-account②⑦">user account</a> MAY be identified by the <code class="idl"><a data-link-type="idl" href="#dom-authenticatorassertionresponse-userhandle" id="ref-for-dom-authenticatorassertionresponse-userhandle⑤">userHandle</a></code> of the resulting <code class="idl"><a data-link-type="idl" href="#authenticatorassertionresponse" id="ref-for-authenticatorassertionresponse⑤">AuthenticatorAssertionResponse</a></code>.
+If the available <a data-link-type="dfn" href="#authenticator" id="ref-for-authenticator①①⑤">authenticators</a> <a data-link-type="dfn" href="#contains" id="ref-for-contains②">contain</a> more than one <a data-link-type="dfn" href="#discoverable-credential" id="ref-for-discoverable-credential①⓪">discoverable credential</a> <a data-link-type="dfn" href="#scope" id="ref-for-scope①③">scoped</a> to the <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party①⑤⑦">Relying Party</a>,
 the credentials are displayed by the <a data-link-type="dfn" href="#client-platform" id="ref-for-client-platform③⑦">client platform</a> or <a data-link-type="dfn" href="#authenticator" id="ref-for-authenticator①①⑥">authenticator</a> for the user to select from (see step 7 of <a href="#sctn-op-get-assertion">§ 6.3.3 The authenticatorGetAssertion Operation</a>).</p>
      </ul>
      <p>If not <a data-link-type="dfn" href="https://infra.spec.whatwg.org/#list-empty" id="ref-for-list-empty④">empty</a>, the client MUST return an error if none of the listed credentials can be used.</p>
@@ -3557,15 +3615,15 @@ <h3 class="heading settled" data-level="5.5" id="dictionary-assertion-options"><
 preferred credential, and the last is the least preferred.</p>
     <dt data-md><dfn class="dfn-paneled idl-code" data-dfn-for="PublicKeyCredentialRequestOptions" data-dfn-type="dict-member" data-export id="dom-publickeycredentialrequestoptions-userverification"><code>userVerification</code></dfn>, <span> of type <a data-link-type="idl-name" href="https://webidl.spec.whatwg.org/#idl-DOMString" id="ref-for-idl-DOMString④⓪">DOMString</a>, defaulting to <code>"preferred"</code></span>
     <dd data-md>
-     <p>This OPTIONAL member specifies the <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party①⑤③">Relying Party</a>'s requirements regarding <a data-link-type="dfn" href="#user-verification" id="ref-for-user-verification②①">user verification</a> for the <code class="idl"><a data-link-type="idl" href="https://w3c.github.io/webappsec-credential-management/#dom-credentialscontainer-get" id="ref-for-dom-credentialscontainer-get②③">get()</a></code> operation. The value SHOULD be a member of <code class="idl"><a data-link-type="idl" href="#enumdef-userverificationrequirement" id="ref-for-enumdef-userverificationrequirement②">UserVerificationRequirement</a></code> but <a data-link-type="dfn" href="#client-platform" id="ref-for-client-platform③⑧">client platforms</a> MUST ignore unknown values, treating an unknown value as if the <a data-link-type="dfn" href="https://infra.spec.whatwg.org/#map-exists" id="ref-for-map-exists④">member does not exist</a>. Eligible authenticators are filtered to only those capable of satisfying this requirement.</p>
+     <p>This OPTIONAL member specifies the <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party①⑤⑧">Relying Party</a>'s requirements regarding <a data-link-type="dfn" href="#user-verification" id="ref-for-user-verification②①">user verification</a> for the <code class="idl"><a data-link-type="idl" href="https://w3c.github.io/webappsec-credential-management/#dom-credentialscontainer-get" id="ref-for-dom-credentialscontainer-get②③">get()</a></code> operation. The value SHOULD be a member of <code class="idl"><a data-link-type="idl" href="#enumdef-userverificationrequirement" id="ref-for-enumdef-userverificationrequirement②">UserVerificationRequirement</a></code> but <a data-link-type="dfn" href="#client-platform" id="ref-for-client-platform③⑧">client platforms</a> MUST ignore unknown values, treating an unknown value as if the <a data-link-type="dfn" href="https://infra.spec.whatwg.org/#map-exists" id="ref-for-map-exists④">member does not exist</a>. Eligible authenticators are filtered to only those capable of satisfying this requirement.</p>
      <p>See <code class="idl"><a data-link-type="idl" href="#enumdef-userverificationrequirement" id="ref-for-enumdef-userverificationrequirement③">UserVerificationRequirement</a></code> for the description of <code class="idl"><a data-link-type="idl" href="#dom-authenticatorselectioncriteria-userverification" id="ref-for-dom-authenticatorselectioncriteria-userverification⑥">userVerification</a></code>'s values and semantics.</p>
     <dt data-md><dfn class="dfn-paneled idl-code" data-dfn-for="PublicKeyCredentialRequestOptions" data-dfn-type="dict-member" data-export id="dom-publickeycredentialrequestoptions-extensions"><code>extensions</code></dfn>, <span> of type <a data-link-type="idl-name" href="#dictdef-authenticationextensionsclientinputs" id="ref-for-dictdef-authenticationextensionsclientinputs③">AuthenticationExtensionsClientInputs</a></span>
     <dd data-md>
-     <p>The <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party①⑤④">Relying Party</a> MAY use this OPTIONAL member to provide <a data-link-type="dfn" href="#client-extension-input" id="ref-for-client-extension-input③">client extension inputs</a> requesting additional processing by the <a data-link-type="dfn" href="#client" id="ref-for-client⑤⑦">client</a> and <a data-link-type="dfn" href="#authenticator" id="ref-for-authenticator①①⑦">authenticator</a>.</p>
+     <p>The <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party①⑤⑨">Relying Party</a> MAY use this OPTIONAL member to provide <a data-link-type="dfn" href="#client-extension-input" id="ref-for-client-extension-input③">client extension inputs</a> requesting additional processing by the <a data-link-type="dfn" href="#client" id="ref-for-client⑤⑦">client</a> and <a data-link-type="dfn" href="#authenticator" id="ref-for-authenticator①①⑦">authenticator</a>.</p>
      <p>The extensions framework is defined in <a href="#sctn-extensions">§ 9 WebAuthn Extensions</a>.
 Some extensions are defined in <a href="#sctn-defined-extensions">§ 10 Defined Extensions</a>;
 consult the IANA "WebAuthn Extension Identifiers" registry <a data-link-type="biblio" href="#biblio-iana-webauthn-registries">[IANA-WebAuthn-Registries]</a> established by <a data-link-type="biblio" href="#biblio-rfc8809">[RFC8809]</a> for an up-to-date list
-of registered <a data-link-type="dfn" href="#webauthn-extensions" id="ref-for-webauthn-extensions①">WebAuthn Extensions</a>.</p>
+of registered <a data-link-type="dfn" href="#webauthn-extensions" id="ref-for-webauthn-extensions②">WebAuthn Extensions</a>.</p>
    </dl>
    <h3 class="heading settled" data-level="5.6" id="sctn-abortoperation"><span class="secno">5.6. </span><span class="content">Abort Operations with <code>AbortSignal</code></span><a class="self-link" href="#sctn-abortoperation"></a></h3>
    <p>Developers are encouraged to leverage the <code class="idl"><a data-link-type="idl" href="https://dom.spec.whatwg.org/#abortcontroller" id="ref-for-abortcontroller②">AbortController</a></code> to manage the <code class="idl"><a data-link-type="idl" href="#dom-publickeycredential-create-slot" id="ref-for-dom-publickeycredential-create-slot④">[[Create]](origin, options, sameOriginWithAncestors)</a></code> and <code class="idl"><a data-link-type="idl" href="#dom-publickeycredential-discoverfromexternalsource-slot" id="ref-for-dom-publickeycredential-discoverfromexternalsource-slot⑥">[[DiscoverFromExternalSource]](origin, options, sameOriginWithAncestors)</a></code> operations.
@@ -3582,35 +3640,35 @@ <h3 class="heading settled" data-level="5.6" id="sctn-abortoperation"><span clas
     loses focuses. If a hook is provided, the above paragraph will be updated to include the hook.
     See <a href="https://github.com/whatwg/html/issues/2711">WHATWG HTML WG Issue #2711</a> for more details.</p>
    <h3 class="heading settled" data-level="5.7" id="sctn-extensions-inputs-outputs"><span class="secno">5.7. </span><span class="content">WebAuthn Extensions Inputs and Outputs</span><a class="self-link" href="#sctn-extensions-inputs-outputs"></a></h3>
-   <p>The subsections below define the data types used for conveying <a data-link-type="dfn" href="#webauthn-extensions" id="ref-for-webauthn-extensions②">WebAuthn extension</a> inputs and outputs.</p>
-   <p class="note" role="note"><span>Note:</span> <a data-link-type="dfn" href="#authenticator-extension-output" id="ref-for-authenticator-extension-output">Authenticator extension outputs</a> are conveyed as a part of <a data-link-type="dfn" href="#authenticator-data" id="ref-for-authenticator-data①③">Authenticator data</a> (see <a href="#table-authData">Table 1</a>).</p>
+   <p>The subsections below define the data types used for conveying <a data-link-type="dfn" href="#webauthn-extensions" id="ref-for-webauthn-extensions③">WebAuthn extension</a> inputs and outputs.</p>
+   <p class="note" role="note"><span>Note:</span> <a data-link-type="dfn" href="#authenticator-extension-output" id="ref-for-authenticator-extension-output">Authenticator extension outputs</a> are conveyed as a part of <a data-link-type="dfn" href="#authenticator-data" id="ref-for-authenticator-data①⑤">Authenticator data</a> (see <a href="#table-authData">Table 1</a>).</p>
    <p class="note" role="note"><span>Note:</span> The types defined below — <code class="idl"><a data-link-type="idl" href="#dictdef-authenticationextensionsclientinputs" id="ref-for-dictdef-authenticationextensionsclientinputs④">AuthenticationExtensionsClientInputs</a></code> and <code class="idl"><a data-link-type="idl" href="#dictdef-authenticationextensionsclientoutputs" id="ref-for-dictdef-authenticationextensionsclientoutputs③">AuthenticationExtensionsClientOutputs</a></code> — are applicable to both <a data-link-type="dfn" href="#registration-extension" id="ref-for-registration-extension①">registration extensions</a> and <a data-link-type="dfn" href="#authentication-extension" id="ref-for-authentication-extension①">authentication extensions</a>. The "Authentication..." portion of their names should be regarded as meaning "WebAuthentication..."</p>
    <h4 class="heading settled" data-level="5.7.1" id="iface-authentication-extensions-client-inputs"><span class="secno">5.7.1. </span><span class="content">Authentication Extensions Client Inputs (dictionary <code class="idl"><a data-link-type="idl" href="#dictdef-authenticationextensionsclientinputs" id="ref-for-dictdef-authenticationextensionsclientinputs⑤">AuthenticationExtensionsClientInputs</a></code>)</span><a class="self-link" href="#iface-authentication-extensions-client-inputs"></a></h4>
 <pre class="idl highlight def"><c- b>dictionary</c-> <dfn class="dfn-paneled idl-code" data-dfn-type="dictionary" data-export id="dictdef-authenticationextensionsclientinputs"><code><c- g>AuthenticationExtensionsClientInputs</c-></code></dfn> {
 };
 </pre>
-   <p>This is a dictionary containing the <a data-link-type="dfn" href="#client-extension-input" id="ref-for-client-extension-input④">client extension input</a> values for zero or more <a data-link-type="dfn" href="#webauthn-extensions" id="ref-for-webauthn-extensions③">WebAuthn Extensions</a>.</p>
+   <p>This is a dictionary containing the <a data-link-type="dfn" href="#client-extension-input" id="ref-for-client-extension-input④">client extension input</a> values for zero or more <a data-link-type="dfn" href="#webauthn-extensions" id="ref-for-webauthn-extensions④">WebAuthn Extensions</a>.</p>
    <h4 class="heading settled" data-level="5.7.2" id="iface-authentication-extensions-client-outputs"><span class="secno">5.7.2. </span><span class="content">Authentication Extensions Client Outputs (dictionary <code class="idl"><a data-link-type="idl" href="#dictdef-authenticationextensionsclientoutputs" id="ref-for-dictdef-authenticationextensionsclientoutputs④">AuthenticationExtensionsClientOutputs</a></code>)</span><a class="self-link" href="#iface-authentication-extensions-client-outputs"></a></h4>
 <pre class="idl highlight def"><c- b>dictionary</c-> <dfn class="dfn-paneled idl-code" data-dfn-type="dictionary" data-export id="dictdef-authenticationextensionsclientoutputs"><code><c- g>AuthenticationExtensionsClientOutputs</c-></code></dfn> {
 };
 </pre>
-   <p>This is a dictionary containing the <a data-link-type="dfn" href="#client-extension-output" id="ref-for-client-extension-output⑤">client extension output</a> values for zero or more <a data-link-type="dfn" href="#webauthn-extensions" id="ref-for-webauthn-extensions④">WebAuthn Extensions</a>.</p>
+   <p>This is a dictionary containing the <a data-link-type="dfn" href="#client-extension-output" id="ref-for-client-extension-output⑤">client extension output</a> values for zero or more <a data-link-type="dfn" href="#webauthn-extensions" id="ref-for-webauthn-extensions⑤">WebAuthn Extensions</a>.</p>
    <h4 class="heading settled" data-level="5.7.3" id="iface-authentication-extensions-authenticator-inputs"><span class="secno">5.7.3. </span><span class="content">Authentication Extensions Authenticator Inputs (CDDL type <code>AuthenticationExtensionsAuthenticatorInputs</code>)</span><a class="self-link" href="#iface-authentication-extensions-authenticator-inputs"></a></h4>
 <pre>AuthenticationExtensionsAuthenticatorInputs = {
   * $$extensionInput .within ( tstr => any )
 }
 </pre>
    <p>The <a data-link-type="dfn" href="#cddl" id="ref-for-cddl">CDDL</a> type <code>AuthenticationExtensionsAuthenticatorInputs</code> defines a <a data-link-type="dfn" href="#cbor" id="ref-for-cbor⑤">CBOR</a> map
-containing the <a data-link-type="dfn" href="#authenticator-extension-input" id="ref-for-authenticator-extension-input">authenticator extension input</a> values for zero or more <a data-link-type="dfn" href="#webauthn-extensions" id="ref-for-webauthn-extensions⑤">WebAuthn Extensions</a>.
+containing the <a data-link-type="dfn" href="#authenticator-extension-input" id="ref-for-authenticator-extension-input">authenticator extension input</a> values for zero or more <a data-link-type="dfn" href="#webauthn-extensions" id="ref-for-webauthn-extensions⑥">WebAuthn Extensions</a>.
 Extensions can add members as described in <a href="#sctn-extension-request-parameters">§ 9.3 Extending Request Parameters</a>.</p>
-   <p>This type is not exposed to the <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party①⑤⑤">Relying Party</a>, but is used by the <a data-link-type="dfn" href="#client" id="ref-for-client⑤⑧">client</a> and <a data-link-type="dfn" href="#authenticator" id="ref-for-authenticator①①⑧">authenticator</a>.</p>
+   <p>This type is not exposed to the <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party①⑥⓪">Relying Party</a>, but is used by the <a data-link-type="dfn" href="#client" id="ref-for-client⑤⑧">client</a> and <a data-link-type="dfn" href="#authenticator" id="ref-for-authenticator①①⑧">authenticator</a>.</p>
    <h4 class="heading settled" data-level="5.7.4" id="iface-authentication-extensions-authenticator-outputs"><span class="secno">5.7.4. </span><span class="content">Authentication Extensions Authenticator Outputs (CDDL type <code>AuthenticationExtensionsAuthenticatorOutputs</code>)</span><a class="self-link" href="#iface-authentication-extensions-authenticator-outputs"></a></h4>
 <pre>AuthenticationExtensionsAuthenticatorOutputs = {
   * $$extensionOutput .within ( tstr => any )
 }
 </pre>
    <p>The <a data-link-type="dfn" href="#cddl" id="ref-for-cddl①">CDDL</a> type <code>AuthenticationExtensionsAuthenticatorOutputs</code> defines a <a data-link-type="dfn" href="#cbor" id="ref-for-cbor⑥">CBOR</a> map
-containing the <a data-link-type="dfn" href="#authenticator-extension-output" id="ref-for-authenticator-extension-output①">authenticator extension output</a> values for zero or more <a data-link-type="dfn" href="#webauthn-extensions" id="ref-for-webauthn-extensions⑥">WebAuthn Extensions</a>.
+containing the <a data-link-type="dfn" href="#authenticator-extension-output" id="ref-for-authenticator-extension-output①">authenticator extension output</a> values for zero or more <a data-link-type="dfn" href="#webauthn-extensions" id="ref-for-webauthn-extensions⑦">WebAuthn Extensions</a>.
 Extensions can add members as described in <a href="#sctn-extension-request-parameters">§ 9.3 Extending Request Parameters</a>.</p>
    <h3 class="heading settled" data-level="5.8" id="sctn-supporting-data-structures"><span class="secno">5.8. </span><span class="content">Supporting Data Structures</span><a class="self-link" href="#sctn-supporting-data-structures"></a></h3>
    <p>The <a data-link-type="dfn" href="#public-key-credential" id="ref-for-public-key-credential③④">public key credential</a> type uses certain data structures that are specified in supporting specifications. These are as
@@ -3643,7 +3701,7 @@ <h4 class="heading settled" data-level="5.8.1" id="dictionary-client-data"><span
 attacks (where an attacker substitutes one legitimate signature for another).</p>
      <dt data-md><dfn class="dfn-paneled idl-code" data-dfn-for="CollectedClientData" data-dfn-type="dict-member" data-export id="dom-collectedclientdata-challenge"><code>challenge</code></dfn>, <span> of type <a data-link-type="idl-name" href="https://webidl.spec.whatwg.org/#idl-DOMString" id="ref-for-idl-DOMString④⑦">DOMString</a></span>
      <dd data-md>
-      <p>This member contains the base64url encoding of the challenge provided by the <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party①⑤⑥">Relying Party</a>. See the <a href="#sctn-cryptographic-challenges">§ 13.4.3 Cryptographic Challenges</a> security consideration.</p>
+      <p>This member contains the base64url encoding of the challenge provided by the <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party①⑥①">Relying Party</a>. See the <a href="#sctn-cryptographic-challenges">§ 13.4.3 Cryptographic Challenges</a> security consideration.</p>
      <dt data-md><dfn class="dfn-paneled idl-code" data-dfn-for="CollectedClientData" data-dfn-type="dict-member" data-export id="dom-collectedclientdata-origin"><code>origin</code></dfn>, <span> of type <a data-link-type="idl-name" href="https://webidl.spec.whatwg.org/#idl-DOMString" id="ref-for-idl-DOMString④⑧">DOMString</a></span>
      <dd data-md>
       <p>This member contains the fully qualified <a data-link-type="dfn" href="https://html.spec.whatwg.org/multipage/origin.html#concept-origin" id="ref-for-concept-origin①②">origin</a> of the requester, as provided to the authenticator by the client, in
@@ -3655,7 +3713,7 @@ <h4 class="heading settled" data-level="5.8.1" id="dictionary-client-data"><span
      <dt data-md>[RESERVED] <dfn data-dfn-for="CollectedClientData" data-dfn-type="dfn" data-noexport id="collectedclientdata-tokenbinding">tokenBinding<a class="self-link" href="#collectedclientdata-tokenbinding"></a></dfn>
      <dd data-md>
       <p>This OPTIONAL member contains information about the state of the <a data-link-type="dfn" href="https://tools.ietf.org/html/rfc8471#section-1" id="ref-for-section-1">Token Binding</a> protocol <a data-link-type="biblio" href="#biblio-tokenbinding">[TokenBinding]</a> used when communicating
-with the <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party①⑤⑦">Relying Party</a>. Its absence indicates that the client doesn’t support token binding</p>
+with the <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party①⑥②">Relying Party</a>. Its absence indicates that the client doesn’t support token binding</p>
       <p class="note" role="note"><span>Note:</span> While <a data-link-type="dfn" href="https://tools.ietf.org/html/rfc8471#section-1" id="ref-for-section-1①">Token Binding</a> was present in Level 1 and Level 2 of WebAuthn, its use is not expected in Level 3. The <code class="idl"><a data-link-type="idl" href="https://www.w3.org/TR/webauthn/#dom-collectedclientdata-tokenbinding" id="ref-for-dom-collectedclientdata-tokenbinding">tokenBinding</a></code> field is reserved so that it will not be reused for a different purpose.</p>
       <div>
        <dl>
@@ -3666,17 +3724,17 @@ <h4 class="heading settled" data-level="5.8.1" id="dictionary-client-data"><span
           <dl>
            <dt data-md><dfn class="dfn-paneled idl-code" data-dfn-for="TokenBindingStatus" data-dfn-type="enum-value" data-export data-lt="&quot;supported&quot;|supported" id="dom-tokenbindingstatus-supported"><code>supported</code></dfn>
            <dd data-md>
-            <p>Indicates the client supports token binding, but it was not negotiated when communicating with the <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party①⑤⑧">Relying Party</a>.</p>
+            <p>Indicates the client supports token binding, but it was not negotiated when communicating with the <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party①⑥③">Relying Party</a>.</p>
            <dt data-md><dfn class="dfn-paneled idl-code" data-dfn-for="TokenBindingStatus" data-dfn-type="enum-value" data-export data-lt="&quot;present&quot;|present" id="dom-tokenbindingstatus-present"><code>present</code></dfn>
            <dd data-md>
-            <p>Indicates token binding was used when communicating with the <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party①⑤⑨">Relying Party</a>. In this case, the <code class="idl"><a data-link-type="idl" href="#dom-tokenbinding-id" id="ref-for-dom-tokenbinding-id①">id</a></code> member MUST be present.</p>
+            <p>Indicates token binding was used when communicating with the <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party①⑥④">Relying Party</a>. In this case, the <code class="idl"><a data-link-type="idl" href="#dom-tokenbinding-id" id="ref-for-dom-tokenbinding-id①">id</a></code> member MUST be present.</p>
           </dl>
          </div>
          <p class="note" role="note"><span>Note:</span> The <code class="idl"><a data-link-type="idl" href="#enumdef-tokenbindingstatus" id="ref-for-enumdef-tokenbindingstatus①">TokenBindingStatus</a></code> enumeration is deliberately not referenced, see <a href="#sct-domstring-backwards-compatibility">§ 2.1.1 Enumerations as DOMString types</a>.</p>
         <dt data-md><dfn class="dfn-paneled idl-code" data-dfn-for="TokenBinding" data-dfn-type="dict-member" data-export id="dom-tokenbinding-id"><code>id</code></dfn>, <span> of type <a data-link-type="idl-name" href="https://webidl.spec.whatwg.org/#idl-DOMString" id="ref-for-idl-DOMString⑤⓪">DOMString</a></span>
         <dd data-md>
          <p>This member MUST be present if <code class="idl"><a data-link-type="idl" href="#dom-tokenbinding-status" id="ref-for-dom-tokenbinding-status①">status</a></code> is <code class="idl"><a data-link-type="idl" href="#dom-tokenbindingstatus-present" id="ref-for-dom-tokenbindingstatus-present①">present</a></code>, and MUST be a <a data-link-type="dfn" href="#base64url-encoding" id="ref-for-base64url-encoding①⓪">base64url
-encoding</a> of the <a data-link-type="dfn" href="https://tools.ietf.org/html/rfc8471#section-3.2" id="ref-for-section-3.2">Token Binding ID</a> that was used when communicating with the <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party①⑥⓪">Relying Party</a>.</p>
+encoding</a> of the <a data-link-type="dfn" href="https://tools.ietf.org/html/rfc8471#section-3.2" id="ref-for-section-3.2">Token Binding ID</a> that was used when communicating with the <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party①⑥⑤">Relying Party</a>.</p>
        </dl>
       </div>
       <p class="note" role="note"><span>Note:</span> Obtaining a <a data-link-type="dfn" href="https://tools.ietf.org/html/rfc8471#section-3.2" id="ref-for-section-3.2①">Token Binding ID</a> is a <a data-link-type="dfn" href="#client-platform" id="ref-for-client-platform④⓪">client platform</a>-specific operation.</p>
@@ -3782,7 +3840,7 @@ <h5 class="heading settled" data-level="5.8.1.2" id="clientdatajson-verification
      <p>The inputs to the algorithm are:</p>
      <ol>
       <li data-md>
-       <p>A bytestring, <var>clientDataJSON</var>, that contains <code class="idl"><a data-link-type="idl" href="#dom-authenticatorresponse-clientdatajson" id="ref-for-dom-authenticatorresponse-clientdatajson⑤">clientDataJSON</a></code> — the serialized <code class="idl"><a data-link-type="idl" href="#dictdef-collectedclientdata" id="ref-for-dictdef-collectedclientdata①⓪">CollectedClientData</a></code> that is to be verified.</p>
+       <p>A bytestring, <var>clientDataJSON</var>, that contains <code class="idl"><a data-link-type="idl" href="#dom-authenticatorresponse-clientdatajson" id="ref-for-dom-authenticatorresponse-clientdatajson⑥">clientDataJSON</a></code> — the serialized <code class="idl"><a data-link-type="idl" href="#dictdef-collectedclientdata" id="ref-for-dictdef-collectedclientdata①⓪">CollectedClientData</a></code> that is to be verified.</p>
       <li data-md>
        <p>A string, <var>type</var>, that contains the expected <code class="idl"><a data-link-type="idl" href="#dom-collectedclientdata-type" id="ref-for-dom-collectedclientdata-type⑤">type</a></code>.</p>
       <li data-md>
@@ -3856,10 +3914,10 @@ <h4 class="heading settled" data-level="5.8.2" id="enum-credentialType"><span cl
     <p>Currently one credential type is defined, namely "<dfn class="dfn-paneled idl-code" data-dfn-for="PublicKeyCredentialType" data-dfn-type="enum-value" data-export data-lt="&quot;public-key&quot;|public-key" id="dom-publickeycredentialtype-public-key"><code>public-key</code></dfn>".</p>
    </div>
    <h4 class="heading settled" data-level="5.8.3" id="dictionary-credential-descriptor"><span class="secno">5.8.3. </span><span class="content">Credential Descriptor (dictionary <dfn class="dfn-paneled idl-code" data-dfn-type="dictionary" data-export id="dictdef-publickeycredentialdescriptor"><code>PublicKeyCredentialDescriptor</code></dfn>)</span><a class="self-link" href="#dictionary-credential-descriptor"></a></h4>
-<pre class="idl highlight def"><c- b>dictionary</c-> <a class="idl-code" data-link-type="dictionary" href="#dictdef-publickeycredentialdescriptor" id="ref-for-dictdef-publickeycredentialdescriptor⑧"><c- g>PublicKeyCredentialDescriptor</c-></a> {
-    <c- b>required</c-> <a class="idl-code" data-link-type="interface" href="https://webidl.spec.whatwg.org/#idl-DOMString" id="ref-for-idl-DOMString⑤①"><c- b>DOMString</c-></a>                    <a class="idl-code" data-link-type="dict-member" data-type="DOMString                    " href="#dom-publickeycredentialdescriptor-type" id="ref-for-dom-publickeycredentialdescriptor-type①"><c- g>type</c-></a>;
-    <c- b>required</c-> <a data-link-type="idl-name" href="https://webidl.spec.whatwg.org/#BufferSource" id="ref-for-BufferSource⑧"><c- n>BufferSource</c-></a>                 <a class="idl-code" data-link-type="dict-member" data-type="BufferSource                 " href="#dom-publickeycredentialdescriptor-id" id="ref-for-dom-publickeycredentialdescriptor-id③"><c- g>id</c-></a>;
-    <a data-link-type="dfn" href="https://webidl.spec.whatwg.org/#idl-sequence" id="ref-for-idl-sequence⑨"><c- b>sequence</c-></a>&lt;<a class="idl-code" data-link-type="interface" href="https://webidl.spec.whatwg.org/#idl-DOMString" id="ref-for-idl-DOMString⑤②"><c- b>DOMString</c-></a>>                   <a class="idl-code" data-link-type="dict-member" data-type="sequence<DOMString>                   " href="#dom-publickeycredentialdescriptor-transports" id="ref-for-dom-publickeycredentialdescriptor-transports⑨"><c- g>transports</c-></a>;
+<pre class="idl highlight def"><c- b>dictionary</c-> <a class="idl-code" data-link-type="dictionary" href="#dictdef-publickeycredentialdescriptor" id="ref-for-dictdef-publickeycredentialdescriptor⑨"><c- g>PublicKeyCredentialDescriptor</c-></a> {
+    <c- b>required</c-> <a class="idl-code" data-link-type="interface" href="https://webidl.spec.whatwg.org/#idl-DOMString" id="ref-for-idl-DOMString⑤①"><c- b>DOMString</c-></a>                    <a class="idl-code" data-link-type="dict-member" data-type="DOMString                    " href="#dom-publickeycredentialdescriptor-type" id="ref-for-dom-publickeycredentialdescriptor-type②"><c- g>type</c-></a>;
+    <c- b>required</c-> <a data-link-type="idl-name" href="https://webidl.spec.whatwg.org/#BufferSource" id="ref-for-BufferSource⑧"><c- n>BufferSource</c-></a>                 <a class="idl-code" data-link-type="dict-member" data-type="BufferSource                 " href="#dom-publickeycredentialdescriptor-id" id="ref-for-dom-publickeycredentialdescriptor-id④"><c- g>id</c-></a>;
+    <a data-link-type="dfn" href="https://webidl.spec.whatwg.org/#idl-sequence" id="ref-for-idl-sequence⑨"><c- b>sequence</c-></a>&lt;<a class="idl-code" data-link-type="interface" href="https://webidl.spec.whatwg.org/#idl-DOMString" id="ref-for-idl-DOMString⑤②"><c- b>DOMString</c-></a>>                   <a class="idl-code" data-link-type="dict-member" data-type="sequence<DOMString>                   " href="#dom-publickeycredentialdescriptor-transports" id="ref-for-dom-publickeycredentialdescriptor-transports①⓪"><c- g>transports</c-></a>;
 };
 </pre>
    <p>This dictionary identifies a specific <a data-link-type="dfn" href="#public-key-credential" id="ref-for-public-key-credential③⑤">public key credential</a>.
@@ -3870,22 +3928,22 @@ <h4 class="heading settled" data-level="5.8.3" id="dictionary-credential-descrip
     <dl>
      <dt data-md><dfn class="dfn-paneled idl-code" data-dfn-for="PublicKeyCredentialDescriptor" data-dfn-type="dict-member" data-export id="dom-publickeycredentialdescriptor-type"><code>type</code></dfn>, <span> of type <a data-link-type="idl-name" href="https://webidl.spec.whatwg.org/#idl-DOMString" id="ref-for-idl-DOMString⑤③">DOMString</a></span>
      <dd data-md>
-      <p>This member contains the type of the <a data-link-type="dfn" href="#public-key-credential" id="ref-for-public-key-credential③⑥">public key credential</a> the caller is referring to. The value SHOULD be a member of <code class="idl"><a data-link-type="idl" href="#enumdef-publickeycredentialtype" id="ref-for-enumdef-publickeycredentialtype⑦">PublicKeyCredentialType</a></code> but <a data-link-type="dfn" href="#client-platform" id="ref-for-client-platform④①">client platforms</a> MUST ignore any <code class="idl"><a data-link-type="idl" href="#dictdef-publickeycredentialdescriptor" id="ref-for-dictdef-publickeycredentialdescriptor⑨">PublicKeyCredentialDescriptor</a></code> with an unknown <code class="idl"><a data-link-type="idl" href="#dom-publickeycredentialdescriptor-type" id="ref-for-dom-publickeycredentialdescriptor-type②">type</a></code>.</p>
+      <p>This member contains the type of the <a data-link-type="dfn" href="#public-key-credential" id="ref-for-public-key-credential③⑥">public key credential</a> the caller is referring to. The value SHOULD be a member of <code class="idl"><a data-link-type="idl" href="#enumdef-publickeycredentialtype" id="ref-for-enumdef-publickeycredentialtype⑦">PublicKeyCredentialType</a></code> but <a data-link-type="dfn" href="#client-platform" id="ref-for-client-platform④①">client platforms</a> MUST ignore any <code class="idl"><a data-link-type="idl" href="#dictdef-publickeycredentialdescriptor" id="ref-for-dictdef-publickeycredentialdescriptor①⓪">PublicKeyCredentialDescriptor</a></code> with an unknown <code class="idl"><a data-link-type="idl" href="#dom-publickeycredentialdescriptor-type" id="ref-for-dom-publickeycredentialdescriptor-type③">type</a></code>.</p>
       <p>This mirrors the <code class="idl"><a data-link-type="idl" href="https://w3c.github.io/webappsec-credential-management/#dom-credential-type" id="ref-for-dom-credential-type①">type</a></code> field of <code class="idl"><a data-link-type="idl" href="#publickeycredential" id="ref-for-publickeycredential②①">PublicKeyCredential</a></code>.</p>
      <dt data-md><dfn class="dfn-paneled idl-code" data-dfn-for="PublicKeyCredentialDescriptor" data-dfn-type="dict-member" data-export id="dom-publickeycredentialdescriptor-id"><code>id</code></dfn>, <span> of type <a data-link-type="idl-name" href="https://webidl.spec.whatwg.org/#BufferSource" id="ref-for-BufferSource⑨">BufferSource</a></span>
      <dd data-md>
-      <p>This member contains the <a data-link-type="dfn" href="#credential-id" id="ref-for-credential-id②②">credential ID</a> of the <a data-link-type="dfn" href="#public-key-credential" id="ref-for-public-key-credential③⑦">public key credential</a> the caller is referring to.</p>
+      <p>This member contains the <a data-link-type="dfn" href="#credential-id" id="ref-for-credential-id②③">credential ID</a> of the <a data-link-type="dfn" href="#public-key-credential" id="ref-for-public-key-credential③⑦">public key credential</a> the caller is referring to.</p>
       <p>This mirrors the <code class="idl"><a data-link-type="idl" href="#dom-publickeycredential-rawid" id="ref-for-dom-publickeycredential-rawid①">rawId</a></code> field of <code class="idl"><a data-link-type="idl" href="#publickeycredential" id="ref-for-publickeycredential②②">PublicKeyCredential</a></code>.</p>
      <dt data-md><dfn class="dfn-paneled idl-code" data-dfn-for="PublicKeyCredentialDescriptor" data-dfn-type="dict-member" data-export id="dom-publickeycredentialdescriptor-transports"><code>transports</code></dfn>, <span> of type sequence&lt;<a data-link-type="idl-name" href="https://webidl.spec.whatwg.org/#idl-DOMString" id="ref-for-idl-DOMString⑤④">DOMString</a>></span>
      <dd data-md>
       <p>This OPTIONAL member contains a hint as to how the <a data-link-type="dfn" href="#client" id="ref-for-client⑥①">client</a> might communicate with the <a data-link-type="dfn" href="#public-key-credential-source-managing-authenticator" id="ref-for-public-key-credential-source-managing-authenticator①①">managing authenticator</a> of the <a data-link-type="dfn" href="#public-key-credential" id="ref-for-public-key-credential③⑧">public key credential</a> the caller is referring to. The values SHOULD be members of <code class="idl"><a data-link-type="idl" href="#enumdef-authenticatortransport" id="ref-for-enumdef-authenticatortransport②">AuthenticatorTransport</a></code> but <a data-link-type="dfn" href="#client-platform" id="ref-for-client-platform④②">client platforms</a> MUST ignore unknown values.</p>
-      <p>This mirrors the <code><code class="idl"><a data-link-type="idl" href="#dom-publickeycredential-response" id="ref-for-dom-publickeycredential-response④">response</a></code>.<code class="idl"><a data-link-type="idl" href="#dom-authenticatorattestationresponse-gettransports" id="ref-for-dom-authenticatorattestationresponse-gettransports②">getTransports()</a></code></code> method
+      <p>This mirrors the <code><code class="idl"><a data-link-type="idl" href="#dom-publickeycredential-response" id="ref-for-dom-publickeycredential-response④">response</a></code>.<code class="idl"><a data-link-type="idl" href="#dom-authenticatorattestationresponse-gettransports" id="ref-for-dom-authenticatorattestationresponse-gettransports④">getTransports()</a></code></code> method
 of a <code class="idl"><a data-link-type="idl" href="#publickeycredential" id="ref-for-publickeycredential②③">PublicKeyCredential</a></code> structure created by a <code class="idl"><a data-link-type="idl" href="https://w3c.github.io/webappsec-credential-management/#dom-credentialscontainer-create" id="ref-for-dom-credentialscontainer-create②①">create()</a></code> operation.
 When <a href="#sctn-registering-a-new-credential">registering a new credential</a>,
-the <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party①⑥①">Relying Party</a> SHOULD store the value returned from <code class="idl"><a data-link-type="idl" href="#dom-authenticatorattestationresponse-gettransports" id="ref-for-dom-authenticatorattestationresponse-gettransports③">getTransports()</a></code>.
-When creating a <code class="idl"><a data-link-type="idl" href="#dictdef-publickeycredentialdescriptor" id="ref-for-dictdef-publickeycredentialdescriptor①⓪">PublicKeyCredentialDescriptor</a></code> for that credential,
-the <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party①⑥②">Relying Party</a> SHOULD retrieve that stored value
-and set it as the value of the <code class="idl"><a data-link-type="idl" href="#dom-publickeycredentialdescriptor-transports" id="ref-for-dom-publickeycredentialdescriptor-transports①⓪">transports</a></code> member.</p>
+the <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party①⑥⑥">Relying Party</a> SHOULD store the value returned from <code class="idl"><a data-link-type="idl" href="#dom-authenticatorattestationresponse-gettransports" id="ref-for-dom-authenticatorattestationresponse-gettransports⑤">getTransports()</a></code>.
+When creating a <code class="idl"><a data-link-type="idl" href="#dictdef-publickeycredentialdescriptor" id="ref-for-dictdef-publickeycredentialdescriptor①①">PublicKeyCredentialDescriptor</a></code> for that credential,
+the <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party①⑥⑦">Relying Party</a> SHOULD retrieve that stored value
+and set it as the value of the <code class="idl"><a data-link-type="idl" href="#dom-publickeycredentialdescriptor-transports" id="ref-for-dom-publickeycredentialdescriptor-transports①①">transports</a></code> member.</p>
     </dl>
    </div>
    <h4 class="heading settled" data-level="5.8.4" id="enum-transport"><span class="secno">5.8.4. </span><span class="content">Authenticator Transport Enumeration (enum <dfn class="dfn-paneled idl-code" data-dfn-type="enum" data-export id="enumdef-authenticatortransport"><code>AuthenticatorTransport</code></dfn>)</span><a class="self-link" href="#enum-transport"></a></h4>
@@ -3901,7 +3959,7 @@ <h4 class="heading settled" data-level="5.8.4" id="enum-transport"><span class="
    <div>
      <a data-link-type="dfn" href="#authenticator" id="ref-for-authenticator①②⓪">Authenticators</a> may implement various <a href="#enum-transport">transports</a> for communicating with <a data-link-type="dfn" href="#client" id="ref-for-client⑥②">clients</a>. This enumeration
     defines hints as to how clients might communicate with a particular authenticator in order to obtain an assertion for a
-    specific credential. Note that these hints represent the <a data-link-type="dfn" href="#webauthn-relying-party" id="ref-for-webauthn-relying-party②②">WebAuthn Relying Party</a>'s best belief as to how an authenticator may be reached. A <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party①⑥③">Relying Party</a> will typically learn of the supported transports for a <a data-link-type="dfn" href="#public-key-credential" id="ref-for-public-key-credential③⑨">public key credential</a> via <code class="idl"><a data-link-type="idl" href="#dom-authenticatorattestationresponse-gettransports" id="ref-for-dom-authenticatorattestationresponse-gettransports④">getTransports()</a></code>. 
+    specific credential. Note that these hints represent the <a data-link-type="dfn" href="#webauthn-relying-party" id="ref-for-webauthn-relying-party②②">WebAuthn Relying Party</a>'s best belief as to how an authenticator may be reached. A <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party①⑥⑧">Relying Party</a> will typically learn of the supported transports for a <a data-link-type="dfn" href="#public-key-credential" id="ref-for-public-key-credential③⑨">public key credential</a> via <code class="idl"><a data-link-type="idl" href="#dom-authenticatorattestationresponse-gettransports" id="ref-for-dom-authenticatorattestationresponse-gettransports⑥">getTransports()</a></code>. 
     <dl>
      <dt data-md><dfn class="dfn-paneled idl-code" data-dfn-for="AuthenticatorTransport" data-dfn-type="enum-value" data-export data-lt="&quot;usb&quot;|usb" id="dom-authenticatortransport-usb"><code>usb</code></dfn>
      <dd data-md>
@@ -3929,7 +3987,7 @@ <h4 class="heading settled" data-level="5.8.5" id="sctn-alg-identifier"><span cl
      A <code class="idl"><a data-link-type="idl" href="#typedefdef-cosealgorithmidentifier" id="ref-for-typedefdef-cosealgorithmidentifier⑨">COSEAlgorithmIdentifier</a></code>'s value is a number identifying a cryptographic algorithm.
     The algorithm identifiers SHOULD be values registered in the IANA COSE Algorithms registry <a data-link-type="biblio" href="#biblio-iana-cose-algs-reg">[IANA-COSE-ALGS-REG]</a>,
     for instance, <code>-7</code> for "ES256" and <code>-257</code> for "RS256". 
-    <p>The COSE algorithms registry leaves degrees of freedom to be specified by other parameters in a <a data-link-type="dfn" href="https://tools.ietf.org/html/rfc8152#section-7" id="ref-for-section-7">COSE key</a>. In order to promote interoperability, this specification makes the following additional guarantees of <a data-link-type="dfn" href="#credential-public-key" id="ref-for-credential-public-key②①">credential public keys</a>:</p>
+    <p>The COSE algorithms registry leaves degrees of freedom to be specified by other parameters in a <a data-link-type="dfn" href="https://tools.ietf.org/html/rfc8152#section-7" id="ref-for-section-7">COSE key</a>. In order to promote interoperability, this specification makes the following additional guarantees of <a data-link-type="dfn" href="#credential-public-key" id="ref-for-credential-public-key②②">credential public keys</a>:</p>
     <ol>
      <li data-md>
       <p>Keys with algorithm ES256 (-7) MUST specify P-256 (1) as the <a data-link-type="dfn" href="https://tools.ietf.org/html/rfc8152#section-13.1.1" id="ref-for-section-13.1.1②">crv</a> parameter and MUST NOT use the compressed point form.</p>
@@ -3956,16 +4014,16 @@ <h4 class="heading settled" data-level="5.8.6" id="enum-userVerificationRequirem
     <dl>
      <dt data-md><dfn class="dfn-paneled idl-code" data-dfn-for="UserVerificationRequirement" data-dfn-type="enum-value" data-export data-lt="&quot;required&quot;|required" id="dom-userverificationrequirement-required"><code>required</code></dfn>
      <dd data-md>
-      <p>The <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party①⑥④">Relying Party</a> requires <a data-link-type="dfn" href="#user-verification" id="ref-for-user-verification②③">user verification</a> for the operation and will fail the overall <a data-link-type="dfn" href="#ceremony" id="ref-for-ceremony⑨">ceremony</a> if the
-response does not have the <a data-link-type="dfn" href="#authdata-flags-uv" id="ref-for-authdata-flags-uv">UV</a> <a data-link-type="dfn" href="#authdata-flags" id="ref-for-authdata-flags②">flag</a> set.
+      <p>The <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party①⑥⑨">Relying Party</a> requires <a data-link-type="dfn" href="#user-verification" id="ref-for-user-verification②③">user verification</a> for the operation and will fail the overall <a data-link-type="dfn" href="#ceremony" id="ref-for-ceremony①①">ceremony</a> if the
+response does not have the <a data-link-type="dfn" href="#authdata-flags-uv" id="ref-for-authdata-flags-uv">UV</a> <a data-link-type="dfn" href="#authdata-flags" id="ref-for-authdata-flags④">flag</a> set.
 The <a data-link-type="dfn" href="#client" id="ref-for-client⑥③">client</a> MUST return an error if <a data-link-type="dfn" href="#user-verification" id="ref-for-user-verification②④">user verification</a> cannot be performed.</p>
      <dt data-md><dfn class="dfn-paneled idl-code" data-dfn-for="UserVerificationRequirement" data-dfn-type="enum-value" data-export data-lt="&quot;preferred&quot;|preferred" id="dom-userverificationrequirement-preferred"><code>preferred</code></dfn>
      <dd data-md>
-      <p>The <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party①⑥⑤">Relying Party</a> prefers <a data-link-type="dfn" href="#user-verification" id="ref-for-user-verification②⑤">user verification</a> for the operation if possible, but will not fail the
-operation if the response does not have the <a data-link-type="dfn" href="#authdata-flags-uv" id="ref-for-authdata-flags-uv①">UV</a> <a data-link-type="dfn" href="#authdata-flags" id="ref-for-authdata-flags③">flag</a> set.</p>
+      <p>The <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party①⑦⓪">Relying Party</a> prefers <a data-link-type="dfn" href="#user-verification" id="ref-for-user-verification②⑤">user verification</a> for the operation if possible, but will not fail the
+operation if the response does not have the <a data-link-type="dfn" href="#authdata-flags-uv" id="ref-for-authdata-flags-uv①">UV</a> <a data-link-type="dfn" href="#authdata-flags" id="ref-for-authdata-flags⑤">flag</a> set.</p>
      <dt data-md><dfn class="dfn-paneled idl-code" data-dfn-for="UserVerificationRequirement" data-dfn-type="enum-value" data-export data-lt="&quot;discouraged&quot;|discouraged" id="dom-userverificationrequirement-discouraged"><code>discouraged</code></dfn>
      <dd data-md>
-      <p>The <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party①⑥⑥">Relying Party</a> does not want <a data-link-type="dfn" href="#user-verification" id="ref-for-user-verification②⑥">user verification</a> employed during the operation (e.g., in the
+      <p>The <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party①⑦①">Relying Party</a> does not want <a data-link-type="dfn" href="#user-verification" id="ref-for-user-verification②⑥">user verification</a> employed during the operation (e.g., in the
 interest of minimizing disruption to the user interaction flow).</p>
     </dl>
    </div>
@@ -3995,7 +4053,7 @@ <h3 class="heading settled" data-level="5.9" id="sctn-permissions-policy"><span
    <h3 class="heading settled" data-level="5.10" id="sctn-iframe-guidance"><span class="secno">5.10. </span><span class="content">Using Web Authentication within <code>iframe</code> elements</span><a class="self-link" href="#sctn-iframe-guidance"></a></h3>
    <p>The <a data-link-type="dfn" href="#web-authentication-api" id="ref-for-web-authentication-api①③">Web Authentication API</a> is disabled by default in cross-origin <code><a data-link-type="element" href="https://html.spec.whatwg.org/multipage/iframe-embed-object.html#the-iframe-element" id="ref-for-the-iframe-element①">iframe</a></code>s.
 To override this default policy and indicate that a cross-origin <code><a data-link-type="element" href="https://html.spec.whatwg.org/multipage/iframe-embed-object.html#the-iframe-element" id="ref-for-the-iframe-element②">iframe</a></code> is allowed to invoke the <a data-link-type="dfn" href="#web-authentication-api" id="ref-for-web-authentication-api①④">Web Authentication API</a>'s <code class="idl"><a data-link-type="idl" href="#dom-publickeycredential-discoverfromexternalsource-slot" id="ref-for-dom-publickeycredential-discoverfromexternalsource-slot①②">[[DiscoverFromExternalSource]](origin, options, sameOriginWithAncestors)</a></code> method, specify the <code><a data-link-type="element-sub" href="https://html.spec.whatwg.org/multipage/iframe-embed-object.html#attr-iframe-allow" id="ref-for-attr-iframe-allow">allow</a></code> attribute on the <code><a data-link-type="element" href="https://html.spec.whatwg.org/multipage/iframe-embed-object.html#the-iframe-element" id="ref-for-the-iframe-element③">iframe</a></code> element and include the <code><a data-link-type="dfn" href="#publickey-credentials-get-feature" id="ref-for-publickey-credentials-get-feature">publickey-credentials-get</a></code> feature-identifier token in the <code><a data-link-type="element-sub" href="https://html.spec.whatwg.org/multipage/iframe-embed-object.html#attr-iframe-allow" id="ref-for-attr-iframe-allow①">allow</a></code> attribute’s value.</p>
-   <p><a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party①⑥⑦">Relying Parties</a> utilizing the WebAuthn API in an embedded context should review <a href="#sctn-seccons-visibility">§ 13.4.2 Visibility Considerations for Embedded Usage</a> regarding <a data-link-type="dfn" href="#ui-redressing" id="ref-for-ui-redressing">UI redressing</a> and its possible mitigations.</p>
+   <p><a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party①⑦②">Relying Parties</a> utilizing the WebAuthn API in an embedded context should review <a href="#sctn-seccons-visibility">§ 13.4.2 Visibility Considerations for Embedded Usage</a> regarding <a data-link-type="dfn" href="#ui-redressing" id="ref-for-ui-redressing">UI redressing</a> and its possible mitigations.</p>
    <h2 class="heading settled" data-level="6" id="sctn-authenticator-model"><span class="secno">6. </span><span class="content">WebAuthn <dfn class="dfn-paneled" data-dfn-type="dfn" data-noexport id="authenticator-model">Authenticator Model</dfn></span><a class="self-link" href="#sctn-authenticator-model"></a></h2>
    <p><a href="#sctn-api">The Web Authentication API</a> implies a specific abstract functional model for a <a data-link-type="dfn" href="#webauthn-authenticator" id="ref-for-webauthn-authenticator④">WebAuthn Authenticator</a>. This section
 describes that <a data-link-type="dfn" href="#authenticator-model" id="ref-for-authenticator-model②">authenticator model</a>.</p>
@@ -4005,12 +4063,12 @@ <h2 class="heading settled" data-level="6" id="sctn-authenticator-model"><span c
    <p class="note" role="note"><span>Note:</span> <a data-link-type="biblio" href="#biblio-fido-ctap">[FIDO-CTAP]</a> is an example of a concrete instantiation of this model, but it is one in which there are differences in the data it returns and those expected by the <a href="#sctn-api">WebAuthn API</a>'s algorithms. The CTAP2 response messages are CBOR maps constructed using integer keys rather than the string keys defined in this specification for the same objects. The <a data-link-type="dfn" href="#client" id="ref-for-client⑥④">client</a> is expected to perform any needed transformations on such data. The <a data-link-type="biblio" href="#biblio-fido-ctap">[FIDO-CTAP]</a> specification details the mapping between CTAP2 integer keys and WebAuthn string keys, in section <a data-link-type="dfn" href="https://fidoalliance.org/specs/fido-v2.0-ps-20190130/fido-client-to-authenticator-protocol-v2.0-ps-20190130.html#responses" id="ref-for-responses">§6.2. Responses</a>.</p>
    <p>For authenticators, this model defines the logical operations that they MUST support, and the data formats that they expose to
 the client and the <a data-link-type="dfn" href="#webauthn-relying-party" id="ref-for-webauthn-relying-party②④">WebAuthn Relying Party</a>. However, it does not define the details of how authenticators communicate with the <a data-link-type="dfn" href="#client-device" id="ref-for-client-device②⓪">client device</a>,
-unless they are necessary for interoperability with <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party①⑥⑧">Relying Parties</a>. For instance, this abstract model does not define protocols for
+unless they are necessary for interoperability with <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party①⑦③">Relying Parties</a>. For instance, this abstract model does not define protocols for
 connecting authenticators to clients over transports such as USB or NFC. Similarly, this abstract model does not define specific
 error codes or methods of returning them; however, it does define error behavior in terms of the needs of the client. Therefore,
 specific error codes are mentioned as a means of showing which error conditions MUST be distinguishable (or not) from each other
 in order to enable a compliant and secure client implementation.</p>
-   <p><a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party①⑥⑨">Relying Parties</a> may influence authenticator selection, if they deem necessary, by stipulating various authenticator characteristics
+   <p><a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party①⑦④">Relying Parties</a> may influence authenticator selection, if they deem necessary, by stipulating various authenticator characteristics
 when <a href="#sctn-createCredential">creating credentials</a> and/or when <a href="#sctn-getAssertion">generating assertions</a>, through use of <a href="#dictionary-makecredentialoptions">credential creation options</a> or <a href="#dictionary-assertion-options">assertion generation options</a>,
 respectively. The algorithms underlying the <a href="#sctn-api">WebAuthn API</a> marshal these options and pass them to the applicable <a href="#sctn-authenticator-ops">authenticator operations</a> defined below.</p>
    <p>In this abstract model, the authenticator provides key management and cryptographic signatures. It can be embedded in the
@@ -4018,19 +4076,19 @@ <h2 class="heading settled" data-level="6" id="sctn-authenticator-model"><span c
 operates at a higher security level than the rest of the authenticator. This is particularly important for authenticators that
 are embedded in the WebAuthn client, as in those cases this cryptographic module (which may, for example, be a TPM) could be
 considered more trustworthy than the rest of the authenticator.</p>
-   <p>Each authenticator stores a <dfn class="dfn-paneled" data-dfn-for="authenticator" data-dfn-type="dfn" data-noexport id="authenticator-credentials-map">credentials map</dfn>, a <a data-link-type="dfn" href="https://infra.spec.whatwg.org/#ordered-map" id="ref-for-ordered-map⑨">map</a> from (<a data-link-type="dfn" href="#public-key-credential-source-rpid" id="ref-for-public-key-credential-source-rpid①">rpId</a>, <a data-link-type="dfn" href="#public-key-credential-source-userhandle" id="ref-for-public-key-credential-source-userhandle">userHandle</a>) to <a data-link-type="dfn" href="#public-key-credential-source" id="ref-for-public-key-credential-source③③">public key credential source</a>.</p>
+   <p>Each authenticator stores a <dfn class="dfn-paneled" data-dfn-for="authenticator" data-dfn-type="dfn" data-noexport id="authenticator-credentials-map">credentials map</dfn>, a <a data-link-type="dfn" href="https://infra.spec.whatwg.org/#ordered-map" id="ref-for-ordered-map⑨">map</a> from (<a data-link-type="dfn" href="#public-key-credential-source-rpid" id="ref-for-public-key-credential-source-rpid①">rpId</a>, <a data-link-type="dfn" href="#public-key-credential-source-userhandle" id="ref-for-public-key-credential-source-userhandle">userHandle</a>) to <a data-link-type="dfn" href="#public-key-credential-source" id="ref-for-public-key-credential-source④③">public key credential source</a>.</p>
    <p>Additionally, each authenticator has an AAGUID, which is a 128-bit identifier indicating the type (e.g. make and model) of the
 authenticator. The AAGUID MUST be chosen by the manufacturer to be identical across all substantially identical authenticators
 made by that manufacturer, and different (with high probability) from the AAGUIDs of all other types of authenticators.
-The AAGUID for a given type of authenticator SHOULD be randomly generated to ensure this. The <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party①⑦⓪">Relying Party</a> MAY use the AAGUID to infer certain
+The AAGUID for a given type of authenticator SHOULD be randomly generated to ensure this. The <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party①⑦⑤">Relying Party</a> MAY use the AAGUID to infer certain
 properties of the authenticator, such as certification level and strength of key protection, using information from other sources.</p>
    <p>The primary function of the authenticator is to provide <a data-link-type="dfn" href="#webauthn-signature" id="ref-for-webauthn-signature①">WebAuthn signatures</a>, which are bound to various contextual data. These
 data are observed and added at different levels of the stack as a signature request passes from the server to the
 authenticator. In verifying a signature, the server checks these bindings against expected values. These contextual bindings
-are divided in two: Those added by the <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party①⑦①">Relying Party</a> or the client, referred to as <a data-link-type="dfn" href="#client-data" id="ref-for-client-data②">client data</a>; and those added by the authenticator,
-referred to as the <a data-link-type="dfn" href="#authenticator-data" id="ref-for-authenticator-data①④">authenticator data</a>. The authenticator signs over the <a data-link-type="dfn" href="#client-data" id="ref-for-client-data③">client data</a>, but is otherwise not interested in
+are divided in two: Those added by the <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party①⑦⑥">Relying Party</a> or the client, referred to as <a data-link-type="dfn" href="#client-data" id="ref-for-client-data②">client data</a>; and those added by the authenticator,
+referred to as the <a data-link-type="dfn" href="#authenticator-data" id="ref-for-authenticator-data①⑥">authenticator data</a>. The authenticator signs over the <a data-link-type="dfn" href="#client-data" id="ref-for-client-data③">client data</a>, but is otherwise not interested in
 its contents. To save bandwidth and processing requirements on the authenticator, the client hashes the <a data-link-type="dfn" href="#client-data" id="ref-for-client-data④">client data</a> and
-sends only the result to the authenticator. The authenticator signs over the combination of the <a data-link-type="dfn" href="#collectedclientdata-hash-of-the-serialized-client-data" id="ref-for-collectedclientdata-hash-of-the-serialized-client-data⑥">hash of the serialized client data</a>, and its own <a data-link-type="dfn" href="#authenticator-data" id="ref-for-authenticator-data①⑤">authenticator data</a>.</p>
+sends only the result to the authenticator. The authenticator signs over the combination of the <a data-link-type="dfn" href="#collectedclientdata-hash-of-the-serialized-client-data" id="ref-for-collectedclientdata-hash-of-the-serialized-client-data⑥">hash of the serialized client data</a>, and its own <a data-link-type="dfn" href="#authenticator-data" id="ref-for-authenticator-data①⑦">authenticator data</a>.</p>
    <p>The goals of this design can be summarized as follows.</p>
    <ul>
     <li data-md>
@@ -4047,8 +4105,8 @@ <h2 class="heading settled" data-level="6" id="sctn-authenticator-model"><span c
    <p>Authenticators produce cryptographic signatures for two distinct purposes:</p>
    <ol>
     <li data-md>
-     <p>An <dfn class="dfn-paneled" data-dfn-type="dfn" data-noexport id="attestation-signature">attestation signature</dfn> is produced when a new <a data-link-type="dfn" href="#public-key-credential" id="ref-for-public-key-credential④⓪">public key credential</a> is created via an <a data-link-type="dfn" href="#authenticatormakecredential" id="ref-for-authenticatormakecredential①⓪">authenticatorMakeCredential</a> operation. An <a data-link-type="dfn" href="#attestation-signature" id="ref-for-attestation-signature①">attestation signature</a> provides cryptographic
-proof of certain properties of the <a data-link-type="dfn" href="#authenticator" id="ref-for-authenticator①②⑥">authenticator</a> and the credential. For instance, an <a data-link-type="dfn" href="#attestation-signature" id="ref-for-attestation-signature②">attestation signature</a> asserts the <a data-link-type="dfn" href="#authenticator" id="ref-for-authenticator①②⑦">authenticator</a> type (as denoted by its AAGUID) and the <a data-link-type="dfn" href="#credential-public-key" id="ref-for-credential-public-key②②">credential public key</a>. The <a data-link-type="dfn" href="#attestation-signature" id="ref-for-attestation-signature③">attestation
+     <p>An <dfn class="dfn-paneled" data-dfn-type="dfn" data-noexport id="attestation-signature">attestation signature</dfn> is produced when a new <a data-link-type="dfn" href="#public-key-credential" id="ref-for-public-key-credential④⓪">public key credential</a> is created via an <a data-link-type="dfn" href="#authenticatormakecredential" id="ref-for-authenticatormakecredential①⓪">authenticatorMakeCredential</a> operation. An <a data-link-type="dfn" href="#attestation-signature" id="ref-for-attestation-signature②">attestation signature</a> provides cryptographic
+proof of certain properties of the <a data-link-type="dfn" href="#authenticator" id="ref-for-authenticator①②⑥">authenticator</a> and the credential. For instance, an <a data-link-type="dfn" href="#attestation-signature" id="ref-for-attestation-signature③">attestation signature</a> asserts the <a data-link-type="dfn" href="#authenticator" id="ref-for-authenticator①②⑦">authenticator</a> type (as denoted by its AAGUID) and the <a data-link-type="dfn" href="#credential-public-key" id="ref-for-credential-public-key②③">credential public key</a>. The <a data-link-type="dfn" href="#attestation-signature" id="ref-for-attestation-signature④">attestation
 signature</a> is signed by an <a data-link-type="dfn" href="#attestation-private-key" id="ref-for-attestation-private-key">attestation private key</a>, which is chosen depending on the type of <a data-link-type="dfn" href="#attestation" id="ref-for-attestation⑨">attestation</a> desired.
 For more details on <a data-link-type="dfn" href="#attestation" id="ref-for-attestation①⓪">attestation</a>, see <a href="#sctn-attestation">§ 6.5 Attestation</a>.</p>
     <li data-md>
@@ -4059,18 +4117,18 @@ <h2 class="heading settled" data-level="6" id="sctn-authenticator-model"><span c
 information, termed <a data-link-type="dfn" href="#client-data" id="ref-for-client-data⑤">client data</a>, that may be useful to the caller, such as the means by which <a data-link-type="dfn" href="#user-consent" id="ref-for-user-consent①⑤">user consent</a> was
 provided, and the prompt shown to the user by the <a data-link-type="dfn" href="#authenticator" id="ref-for-authenticator①③⓪">authenticator</a>. The <a data-link-type="dfn" href="#assertion-signature" id="ref-for-assertion-signature③">assertion signature</a> format is illustrated in <a href="#fig-signature">Figure 4, below</a>.</p>
    </ol>
-   <p>The term <dfn class="dfn-paneled" data-dfn-type="dfn" data-noexport id="webauthn-signature">WebAuthn signature</dfn> refers to both <a data-link-type="dfn" href="#attestation-signature" id="ref-for-attestation-signature④">attestation signatures</a> and <a data-link-type="dfn" href="#assertion-signature" id="ref-for-assertion-signature④">assertion signatures</a>.
+   <p>The term <dfn class="dfn-paneled" data-dfn-type="dfn" data-noexport id="webauthn-signature">WebAuthn signature</dfn> refers to both <a data-link-type="dfn" href="#attestation-signature" id="ref-for-attestation-signature⑤">attestation signatures</a> and <a data-link-type="dfn" href="#assertion-signature" id="ref-for-assertion-signature④">assertion signatures</a>.
 The formats of these signatures, as well as the procedures for generating them, are specified below.</p>
    <h3 class="heading settled" data-level="6.1" id="sctn-authenticator-data"><span class="secno">6.1. </span><span class="content">Authenticator Data</span><a class="self-link" href="#sctn-authenticator-data"></a></h3>
    <p>The <dfn class="dfn-paneled" data-dfn-type="dfn" data-noexport id="authenticator-data">authenticator data</dfn> structure encodes contextual bindings made by the <a data-link-type="dfn" href="#authenticator" id="ref-for-authenticator①③①">authenticator</a>. These bindings are
 controlled by the authenticator itself, and derive their trust from the <a data-link-type="dfn" href="#webauthn-relying-party" id="ref-for-webauthn-relying-party②⑤">WebAuthn Relying Party</a>'s assessment of the security properties of the
 authenticator. In one extreme case, the authenticator may be embedded in the client, and its bindings may be no more trustworthy
 than the <a data-link-type="dfn" href="#client-data" id="ref-for-client-data⑥">client data</a>. At the other extreme, the authenticator may be a discrete entity with high-security hardware and
-software, connected to the client over a secure channel. In both cases, the <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party①⑦②">Relying Party</a> receives the <a data-link-type="dfn" href="#authenticator-data" id="ref-for-authenticator-data①⑥">authenticator data</a> in the same
+software, connected to the client over a secure channel. In both cases, the <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party①⑦⑦">Relying Party</a> receives the <a data-link-type="dfn" href="#authenticator-data" id="ref-for-authenticator-data①⑧">authenticator data</a> in the same
 format, and uses its knowledge of the authenticator to make trust decisions.</p>
-   <p>The <a data-link-type="dfn" href="#authenticator-data" id="ref-for-authenticator-data①⑦">authenticator data</a> has a compact but extensible encoding. This is desired since authenticators can be devices with
+   <p>The <a data-link-type="dfn" href="#authenticator-data" id="ref-for-authenticator-data①⑨">authenticator data</a> has a compact but extensible encoding. This is desired since authenticators can be devices with
 limited capabilities and low power requirements, with much simpler software stacks than the <a data-link-type="dfn" href="#client-platform" id="ref-for-client-platform④⑤">client platform</a>.</p>
-   <p>The <a data-link-type="dfn" href="#authenticator-data" id="ref-for-authenticator-data①⑧">authenticator data</a> structure is a byte array of 37 bytes or more,
+   <p>The <a data-link-type="dfn" href="#authenticator-data" id="ref-for-authenticator-data②⓪">authenticator data</a> structure is a byte array of 37 bytes or more,
 laid out as shown in <a href="#table-authData">Table <span class="table-ref-following"></span></a>.</p>
    <figure class="table" id="table-authData">
     <table class="complex data longlastcol">
@@ -4111,17 +4169,17 @@ <h3 class="heading settled" data-level="6.1" id="sctn-authenticator-data"><span
           <p>Bit 3: <a data-link-type="dfn" href="#backup-eligibility" id="ref-for-backup-eligibility①">Backup Eligibility</a> (<dfn class="dfn-paneled" data-dfn-for="authData/flags" data-dfn-type="dfn" data-noexport id="authdata-flags-be">BE</dfn>).</p>
           <ul>
            <li data-md>
-            <p><code>1</code> means the <a data-link-type="dfn" href="#public-key-credential-source" id="ref-for-public-key-credential-source③④">public key credential source</a> is <a data-link-type="dfn" href="#backup-eligible" id="ref-for-backup-eligible">backup eligible</a>.</p>
+            <p><code>1</code> means the <a data-link-type="dfn" href="#public-key-credential-source" id="ref-for-public-key-credential-source④④">public key credential source</a> is <a data-link-type="dfn" href="#backup-eligible" id="ref-for-backup-eligible">backup eligible</a>.</p>
            <li data-md>
-            <p><code>0</code> means the <a data-link-type="dfn" href="#public-key-credential-source" id="ref-for-public-key-credential-source③⑤">public key credential source</a> is not <a data-link-type="dfn" href="#backup-eligible" id="ref-for-backup-eligible①">backup eligible</a>.</p>
+            <p><code>0</code> means the <a data-link-type="dfn" href="#public-key-credential-source" id="ref-for-public-key-credential-source④⑤">public key credential source</a> is not <a data-link-type="dfn" href="#backup-eligible" id="ref-for-backup-eligible①">backup eligible</a>.</p>
           </ul>
          <li data-md>
           <p>Bit 4: <a data-link-type="dfn" href="#backup-state" id="ref-for-backup-state①">Backup State</a> (<dfn class="dfn-paneled" data-dfn-for="authData/flags" data-dfn-type="dfn" data-noexport id="authdata-flags-bs">BS</dfn>).</p>
           <ul>
            <li data-md>
-            <p><code>1</code> means the <a data-link-type="dfn" href="#public-key-credential-source" id="ref-for-public-key-credential-source③⑥">public key credential source</a> is currently <a data-link-type="dfn" href="#backed-up" id="ref-for-backed-up①">backed up</a>.</p>
+            <p><code>1</code> means the <a data-link-type="dfn" href="#public-key-credential-source" id="ref-for-public-key-credential-source④⑥">public key credential source</a> is currently <a data-link-type="dfn" href="#backed-up" id="ref-for-backed-up①">backed up</a>.</p>
            <li data-md>
-            <p><code>0</code> means the <a data-link-type="dfn" href="#public-key-credential-source" id="ref-for-public-key-credential-source③⑦">public key credential source</a> is not currently <a data-link-type="dfn" href="#backed-up" id="ref-for-backed-up②">backed up</a>.</p>
+            <p><code>0</code> means the <a data-link-type="dfn" href="#public-key-credential-source" id="ref-for-public-key-credential-source④⑦">public key credential source</a> is not currently <a data-link-type="dfn" href="#backed-up" id="ref-for-backed-up②">backed up</a>.</p>
           </ul>
          <li data-md>
           <p>Bits 5: Reserved for future use (<code>RFU2</code>).</p>
@@ -4135,7 +4193,7 @@ <h3 class="heading settled" data-level="6.1" id="sctn-authenticator-data"><span
           <p>Bit 7: Extension data included (<dfn class="dfn-paneled" data-dfn-for="authData/flags" data-dfn-type="dfn" data-noexport id="authdata-flags-ed">ED</dfn>).</p>
           <ul>
            <li data-md>
-            <p>Indicates if the <a data-link-type="dfn" href="#authenticator-data" id="ref-for-authenticator-data①⑨">authenticator data</a> has <a data-link-type="dfn" href="#authdata-extensions" id="ref-for-authdata-extensions">extensions</a>.</p>
+            <p>Indicates if the <a data-link-type="dfn" href="#authenticator-data" id="ref-for-authenticator-data②①">authenticator data</a> has <a data-link-type="dfn" href="#authdata-extensions" id="ref-for-authdata-extensions">extensions</a>.</p>
           </ul>
         </ul>
       <tr>
@@ -4151,56 +4209,56 @@ <h3 class="heading settled" data-level="6.1" id="sctn-authenticator-data"><span
       <tr>
        <td><dfn class="dfn-paneled" data-dfn-for="authData" data-dfn-type="dfn" data-noexport id="authdata-extensions">extensions</dfn>
        <td>variable (if present)
-       <td> Extension-defined <a data-link-type="dfn" href="#authenticator-data" id="ref-for-authenticator-data②⓪">authenticator data</a>. This is a <a data-link-type="dfn" href="#cbor" id="ref-for-cbor⑦">CBOR</a> <a data-link-type="biblio" href="#biblio-rfc8949">[RFC8949]</a> map with <a data-link-type="dfn" href="#extension-identifier" id="ref-for-extension-identifier④">extension identifiers</a> as keys,
+       <td> Extension-defined <a data-link-type="dfn" href="#authenticator-data" id="ref-for-authenticator-data②②">authenticator data</a>. This is a <a data-link-type="dfn" href="#cbor" id="ref-for-cbor⑦">CBOR</a> <a data-link-type="biblio" href="#biblio-rfc8949">[RFC8949]</a> map with <a data-link-type="dfn" href="#extension-identifier" id="ref-for-extension-identifier④">extension identifiers</a> as keys,
                 and <a data-link-type="dfn" href="#authenticator-extension-output" id="ref-for-authenticator-extension-output②">authenticator extension outputs</a> as values. See <a href="#sctn-extensions">§ 9 WebAuthn Extensions</a> for details. 
     </table>
-    <figcaption> <a data-link-type="dfn" href="#authenticator-data" id="ref-for-authenticator-data②①">Authenticator data</a> layout. The names in the Name column are only for reference within this document, and are not
-        present in the actual representation of the <a data-link-type="dfn" href="#authenticator-data" id="ref-for-authenticator-data②②">authenticator data</a>. </figcaption>
+    <figcaption> <a data-link-type="dfn" href="#authenticator-data" id="ref-for-authenticator-data②③">Authenticator data</a> layout. The names in the Name column are only for reference within this document, and are not
+        present in the actual representation of the <a data-link-type="dfn" href="#authenticator-data" id="ref-for-authenticator-data②④">authenticator data</a>. </figcaption>
    </figure>
    <p>The <a data-link-type="dfn" href="#rp-id" id="ref-for-rp-id②⑨">RP ID</a> is originally received from the <a data-link-type="dfn" href="#client" id="ref-for-client⑥⑥">client</a> when the credential is created, and again when an <a data-link-type="dfn" href="#assertion" id="ref-for-assertion②">assertion</a> is generated.
 However, it differs from other <a data-link-type="dfn" href="#client-data" id="ref-for-client-data⑦">client data</a> in some important ways. First, unlike the <a data-link-type="dfn" href="#client-data" id="ref-for-client-data⑧">client data</a>, the <a data-link-type="dfn" href="#rp-id" id="ref-for-rp-id③⓪">RP ID</a> of a
 credential does not change between operations but instead remains the same for the lifetime of that credential. Secondly, it is
 validated by the authenticator during the <a data-link-type="dfn" href="#authenticatorgetassertion" id="ref-for-authenticatorgetassertion⑧">authenticatorGetAssertion</a> operation, by verifying that the <a data-link-type="dfn" href="#rp-id" id="ref-for-rp-id③①">RP ID</a> that
 the requested <a data-link-type="dfn" href="#public-key-credential" id="ref-for-public-key-credential④③">credential</a> is <a data-link-type="dfn" href="#scope" id="ref-for-scope①⑤">scoped</a> to exactly matches the <a data-link-type="dfn" href="#rp-id" id="ref-for-rp-id③②">RP ID</a> supplied by the <a data-link-type="dfn" href="#client" id="ref-for-client⑥⑦">client</a>.</p>
-   <p><a data-link-type="dfn" href="#authenticator" id="ref-for-authenticator①③②">Authenticators</a> <dfn class="dfn-paneled" data-dfn-for="authenticator data" data-dfn-type="dfn" data-noexport id="authenticator-data-perform-the-following-steps-to-generate-an-authenticator-data-structure">perform the following steps to generate an <a data-link-type="dfn" href="#authenticator-data" id="ref-for-authenticator-data②③">authenticator data</a> structure</dfn>:</p>
+   <p><a data-link-type="dfn" href="#authenticator" id="ref-for-authenticator①③②">Authenticators</a> <dfn class="dfn-paneled" data-dfn-for="authenticator data" data-dfn-type="dfn" data-noexport id="authenticator-data-perform-the-following-steps-to-generate-an-authenticator-data-structure">perform the following steps to generate an <a data-link-type="dfn" href="#authenticator-data" id="ref-for-authenticator-data②⑤">authenticator data</a> structure</dfn>:</p>
    <ul>
     <li data-md>
      <p>Hash <a data-link-type="dfn" href="#rp-id" id="ref-for-rp-id③③">RP ID</a> using SHA-256 to generate the <a data-link-type="dfn" href="#authdata-rpidhash" id="ref-for-authdata-rpidhash">rpIdHash</a>.</p>
     <li data-md>
-     <p>The <a data-link-type="dfn" href="#authdata-flags-up" id="ref-for-authdata-flags-up">UP</a> <a data-link-type="dfn" href="#authdata-flags" id="ref-for-authdata-flags④">flag</a> SHALL be set if and only if the authenticator performed a <a data-link-type="dfn" href="#test-of-user-presence" id="ref-for-test-of-user-presence⑥">test of user presence</a>.
-The <a data-link-type="dfn" href="#authdata-flags-uv" id="ref-for-authdata-flags-uv②">UV</a> <a data-link-type="dfn" href="#authdata-flags" id="ref-for-authdata-flags⑤">flag</a> SHALL be set if and only if the authenticator performed <a data-link-type="dfn" href="#user-verification" id="ref-for-user-verification②⑦">user verification</a>.
+     <p>The <a data-link-type="dfn" href="#authdata-flags-up" id="ref-for-authdata-flags-up">UP</a> <a data-link-type="dfn" href="#authdata-flags" id="ref-for-authdata-flags⑥">flag</a> SHALL be set if and only if the authenticator performed a <a data-link-type="dfn" href="#test-of-user-presence" id="ref-for-test-of-user-presence⑥">test of user presence</a>.
+The <a data-link-type="dfn" href="#authdata-flags-uv" id="ref-for-authdata-flags-uv②">UV</a> <a data-link-type="dfn" href="#authdata-flags" id="ref-for-authdata-flags⑦">flag</a> SHALL be set if and only if the authenticator performed <a data-link-type="dfn" href="#user-verification" id="ref-for-user-verification②⑦">user verification</a>.
 The <code>RFU</code> bits SHALL be set to zero.</p>
      <p class="note" role="note"><span>Note:</span> If the authenticator performed both a <a data-link-type="dfn" href="#test-of-user-presence" id="ref-for-test-of-user-presence⑦">test of user presence</a> and <a data-link-type="dfn" href="#user-verification" id="ref-for-user-verification②⑧">user verification</a>,
 possibly combined in a single <a data-link-type="dfn" href="#authorization-gesture" id="ref-for-authorization-gesture①⑥">authorization gesture</a>,
-then the authenticator will set both the <a data-link-type="dfn" href="#authdata-flags-up" id="ref-for-authdata-flags-up①">UP</a> <a data-link-type="dfn" href="#authdata-flags" id="ref-for-authdata-flags⑥">flag</a> and the <a data-link-type="dfn" href="#authdata-flags-uv" id="ref-for-authdata-flags-uv③">UV</a> <a data-link-type="dfn" href="#authdata-flags" id="ref-for-authdata-flags⑦">flag</a>.</p>
+then the authenticator will set both the <a data-link-type="dfn" href="#authdata-flags-up" id="ref-for-authdata-flags-up①">UP</a> <a data-link-type="dfn" href="#authdata-flags" id="ref-for-authdata-flags⑧">flag</a> and the <a data-link-type="dfn" href="#authdata-flags-uv" id="ref-for-authdata-flags-uv③">UV</a> <a data-link-type="dfn" href="#authdata-flags" id="ref-for-authdata-flags⑨">flag</a>.</p>
     <li data-md>
-     <p>For <a data-link-type="dfn" href="#attestation-signature" id="ref-for-attestation-signature⑤">attestation signatures</a>, the authenticator MUST set the <a data-link-type="dfn" href="#authdata-flags-at" id="ref-for-authdata-flags-at">AT</a> <a data-link-type="dfn" href="#authdata-flags" id="ref-for-authdata-flags⑧">flag</a> and include the <code><a data-link-type="dfn" href="#authdata-attestedcredentialdata" id="ref-for-authdata-attestedcredentialdata②">attestedCredentialData</a></code>.
-For <a data-link-type="dfn" href="#assertion-signature" id="ref-for-assertion-signature⑤">assertion signatures</a>, the <a data-link-type="dfn" href="#authdata-flags-at" id="ref-for-authdata-flags-at①">AT</a> <a data-link-type="dfn" href="#authdata-flags" id="ref-for-authdata-flags⑨">flag</a> MUST NOT be set and the <code><a data-link-type="dfn" href="#authdata-attestedcredentialdata" id="ref-for-authdata-attestedcredentialdata③">attestedCredentialData</a></code> MUST NOT be included.</p>
+     <p>For <a data-link-type="dfn" href="#attestation-signature" id="ref-for-attestation-signature⑥">attestation signatures</a>, the authenticator MUST set the <a data-link-type="dfn" href="#authdata-flags-at" id="ref-for-authdata-flags-at">AT</a> <a data-link-type="dfn" href="#authdata-flags" id="ref-for-authdata-flags①⓪">flag</a> and include the <code><a data-link-type="dfn" href="#authdata-attestedcredentialdata" id="ref-for-authdata-attestedcredentialdata②">attestedCredentialData</a></code>.
+For <a data-link-type="dfn" href="#assertion-signature" id="ref-for-assertion-signature⑤">assertion signatures</a>, the <a data-link-type="dfn" href="#authdata-flags-at" id="ref-for-authdata-flags-at①">AT</a> <a data-link-type="dfn" href="#authdata-flags" id="ref-for-authdata-flags①①">flag</a> MUST NOT be set and the <code><a data-link-type="dfn" href="#authdata-attestedcredentialdata" id="ref-for-authdata-attestedcredentialdata③">attestedCredentialData</a></code> MUST NOT be included.</p>
     <li data-md>
-     <p>If the authenticator does not include any <a data-link-type="dfn" href="#authdata-extensions" id="ref-for-authdata-extensions①">extension data</a>, it MUST set the <a data-link-type="dfn" href="#authdata-flags-ed" id="ref-for-authdata-flags-ed">ED</a> <a data-link-type="dfn" href="#authdata-flags" id="ref-for-authdata-flags①⓪">flag</a> to zero, and to one if <a data-link-type="dfn" href="#authdata-extensions" id="ref-for-authdata-extensions②">extension data</a> is included.</p>
+     <p>If the authenticator does not include any <a data-link-type="dfn" href="#authdata-extensions" id="ref-for-authdata-extensions①">extension data</a>, it MUST set the <a data-link-type="dfn" href="#authdata-flags-ed" id="ref-for-authdata-flags-ed">ED</a> <a data-link-type="dfn" href="#authdata-flags" id="ref-for-authdata-flags①②">flag</a> to zero, and to one if <a data-link-type="dfn" href="#authdata-extensions" id="ref-for-authdata-extensions②">extension data</a> is included.</p>
    </ul>
-   <p><a href="#fig-authData">Figure <span class="figure-num-following"></span></a> shows a visual representation of the <a data-link-type="dfn" href="#authenticator-data" id="ref-for-authenticator-data②④">authenticator data</a> structure.</p>
+   <p><a href="#fig-authData">Figure <span class="figure-num-following"></span></a> shows a visual representation of the <a data-link-type="dfn" href="#authenticator-data" id="ref-for-authenticator-data②⑥">authenticator data</a> structure.</p>
    <figure id="fig-authData">
      <img src="images/fido-signature-formats-figure1.svg"> 
-    <figcaption><a data-link-type="dfn" href="#authenticator-data" id="ref-for-authenticator-data②⑤">Authenticator data</a> layout.</figcaption>
+    <figcaption><a data-link-type="dfn" href="#authenticator-data" id="ref-for-authenticator-data②⑦">Authenticator data</a> layout.</figcaption>
    </figure>
    <div class="note" role="note">
-     Note: <a data-link-type="dfn" href="#authenticator-data" id="ref-for-authenticator-data②⑥">authenticator data</a> describes its own length: If the <a data-link-type="dfn" href="#authdata-flags-at" id="ref-for-authdata-flags-at②">AT</a> and <a data-link-type="dfn" href="#authdata-flags-ed" id="ref-for-authdata-flags-ed①">ED</a> <a data-link-type="dfn" href="#authdata-flags" id="ref-for-authdata-flags①①">flags</a> are not set, it is always 37 bytes long.
-    The <a data-link-type="dfn" href="#attested-credential-data" id="ref-for-attested-credential-data⑤">attested credential data</a> (which is only present if the <a data-link-type="dfn" href="#authdata-flags-at" id="ref-for-authdata-flags-at③">AT</a> <a data-link-type="dfn" href="#authdata-flags" id="ref-for-authdata-flags①②">flag</a> is set) describes its own length. If the <a data-link-type="dfn" href="#authdata-flags-ed" id="ref-for-authdata-flags-ed②">ED</a> <a data-link-type="dfn" href="#authdata-flags" id="ref-for-authdata-flags①③">flag</a> is set, then the total length is 37 bytes plus the length of the <a data-link-type="dfn" href="#attested-credential-data" id="ref-for-attested-credential-data⑥">attested credential data</a> (if the <a data-link-type="dfn" href="#authdata-flags-at" id="ref-for-authdata-flags-at④">AT</a> <a data-link-type="dfn" href="#authdata-flags" id="ref-for-authdata-flags①④">flag</a> is set), plus the length of the <a data-link-type="dfn" href="#authdata-extensions" id="ref-for-authdata-extensions③">extensions</a> output (a <a data-link-type="dfn" href="#cbor" id="ref-for-cbor⑧">CBOR</a> map) that
+     Note: <a data-link-type="dfn" href="#authenticator-data" id="ref-for-authenticator-data②⑧">authenticator data</a> describes its own length: If the <a data-link-type="dfn" href="#authdata-flags-at" id="ref-for-authdata-flags-at②">AT</a> and <a data-link-type="dfn" href="#authdata-flags-ed" id="ref-for-authdata-flags-ed①">ED</a> <a data-link-type="dfn" href="#authdata-flags" id="ref-for-authdata-flags①③">flags</a> are not set, it is always 37 bytes long.
+    The <a data-link-type="dfn" href="#attested-credential-data" id="ref-for-attested-credential-data⑤">attested credential data</a> (which is only present if the <a data-link-type="dfn" href="#authdata-flags-at" id="ref-for-authdata-flags-at③">AT</a> <a data-link-type="dfn" href="#authdata-flags" id="ref-for-authdata-flags①④">flag</a> is set) describes its own length. If the <a data-link-type="dfn" href="#authdata-flags-ed" id="ref-for-authdata-flags-ed②">ED</a> <a data-link-type="dfn" href="#authdata-flags" id="ref-for-authdata-flags①⑤">flag</a> is set, then the total length is 37 bytes plus the length of the <a data-link-type="dfn" href="#attested-credential-data" id="ref-for-attested-credential-data⑥">attested credential data</a> (if the <a data-link-type="dfn" href="#authdata-flags-at" id="ref-for-authdata-flags-at④">AT</a> <a data-link-type="dfn" href="#authdata-flags" id="ref-for-authdata-flags①⑥">flag</a> is set), plus the length of the <a data-link-type="dfn" href="#authdata-extensions" id="ref-for-authdata-extensions③">extensions</a> output (a <a data-link-type="dfn" href="#cbor" id="ref-for-cbor⑧">CBOR</a> map) that
     follows. 
     <p>Determining <a data-link-type="dfn" href="#attested-credential-data" id="ref-for-attested-credential-data⑦">attested credential data</a>'s length, which is variable, involves determining <code><a data-link-type="dfn" href="#authdata-attestedcredentialdata-credentialpublickey" id="ref-for-authdata-attestedcredentialdata-credentialpublickey②">credentialPublicKey</a></code>’s beginning location given the preceding <code><a data-link-type="dfn" href="#authdata-attestedcredentialdata-credentialid" id="ref-for-authdata-attestedcredentialdata-credentialid②">credentialId</a></code>’s <a data-link-type="dfn" href="#authdata-attestedcredentialdata-credentialidlength" id="ref-for-authdata-attestedcredentialdata-credentialidlength①">length</a>, and then determining the <code><a data-link-type="dfn" href="#authdata-attestedcredentialdata-credentialpublickey" id="ref-for-authdata-attestedcredentialdata-credentialpublickey③">credentialPublicKey</a></code>’s length (see also <a data-link-type="dfn" href="https://tools.ietf.org/html/rfc8152#section-7" id="ref-for-section-7①">Section 7</a> of <a data-link-type="biblio" href="#biblio-rfc8152">[RFC8152]</a>).</p>
    </div>
    <h4 class="heading settled" data-level="6.1.1" id="sctn-sign-counter"><span class="secno">6.1.1. </span><span class="content"><dfn class="dfn-paneled" data-dfn-type="dfn" data-noexport id="signature-counter">Signature Counter</dfn> Considerations</span><a class="self-link" href="#sctn-sign-counter"></a></h4>
    <p>Authenticators SHOULD implement a <a data-link-type="dfn" href="#signature-counter" id="ref-for-signature-counter②">signature counter</a> feature. These counters are conceptually stored for each credential
-by the authenticator, or globally for the authenticator as a whole. The initial value of a credential’s <a data-link-type="dfn" href="#signature-counter" id="ref-for-signature-counter③">signature counter</a> is specified in the <code><a data-link-type="dfn" href="#authdata-signcount" id="ref-for-authdata-signcount">signCount</a></code> value of the <a data-link-type="dfn" href="#authenticator-data" id="ref-for-authenticator-data②⑦">authenticator data</a> returned by <a data-link-type="dfn" href="#authenticatormakecredential" id="ref-for-authenticatormakecredential①①">authenticatorMakeCredential</a>. The <a data-link-type="dfn" href="#signature-counter" id="ref-for-signature-counter④">signature counter</a> is incremented for each successful <a data-link-type="dfn" href="#authenticatorgetassertion" id="ref-for-authenticatorgetassertion⑨">authenticatorGetAssertion</a> operation by some positive value, and subsequent values are returned to the <a data-link-type="dfn" href="#webauthn-relying-party" id="ref-for-webauthn-relying-party②⑥">WebAuthn Relying Party</a> within the <a data-link-type="dfn" href="#authenticator-data" id="ref-for-authenticator-data②⑧">authenticator data</a> again. The <a data-link-type="dfn" href="#signature-counter" id="ref-for-signature-counter⑤">signature counter</a>'s purpose is to aid <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party①⑦③">Relying Parties</a> in detecting cloned authenticators. Clone
+by the authenticator, or globally for the authenticator as a whole. The initial value of a credential’s <a data-link-type="dfn" href="#signature-counter" id="ref-for-signature-counter③">signature counter</a> is specified in the <code><a data-link-type="dfn" href="#authdata-signcount" id="ref-for-authdata-signcount①">signCount</a></code> value of the <a data-link-type="dfn" href="#authenticator-data" id="ref-for-authenticator-data②⑨">authenticator data</a> returned by <a data-link-type="dfn" href="#authenticatormakecredential" id="ref-for-authenticatormakecredential①①">authenticatorMakeCredential</a>. The <a data-link-type="dfn" href="#signature-counter" id="ref-for-signature-counter④">signature counter</a> is incremented for each successful <a data-link-type="dfn" href="#authenticatorgetassertion" id="ref-for-authenticatorgetassertion⑨">authenticatorGetAssertion</a> operation by some positive value, and subsequent values are returned to the <a data-link-type="dfn" href="#webauthn-relying-party" id="ref-for-webauthn-relying-party②⑥">WebAuthn Relying Party</a> within the <a data-link-type="dfn" href="#authenticator-data" id="ref-for-authenticator-data③⓪">authenticator data</a> again. The <a data-link-type="dfn" href="#signature-counter" id="ref-for-signature-counter⑤">signature counter</a>'s purpose is to aid <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party①⑦⑧">Relying Parties</a> in detecting cloned authenticators. Clone
 detection is more important for authenticators with limited protection measures.</p>
-   <p>Authenticators that do not implement a <a data-link-type="dfn" href="#signature-counter" id="ref-for-signature-counter⑥">signature counter</a> leave the <code><a data-link-type="dfn" href="#authdata-signcount" id="ref-for-authdata-signcount①">signCount</a></code> in the <a data-link-type="dfn" href="#authenticator-data" id="ref-for-authenticator-data②⑨">authenticator data</a> constant at zero.</p>
-   <p>A <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party①⑦④">Relying Party</a> stores the <a data-link-type="dfn" href="#signature-counter" id="ref-for-signature-counter⑦">signature counter</a> of the most recent <a data-link-type="dfn" href="#authenticatorgetassertion" id="ref-for-authenticatorgetassertion①⓪">authenticatorGetAssertion</a> operation. (Or the counter from the <a data-link-type="dfn" href="#authenticatormakecredential" id="ref-for-authenticatormakecredential①②">authenticatorMakeCredential</a> operation if no <a data-link-type="dfn" href="#authenticatorgetassertion" id="ref-for-authenticatorgetassertion①①">authenticatorGetAssertion</a> has ever been performed on a credential.) In subsequent <a data-link-type="dfn" href="#authenticatorgetassertion" id="ref-for-authenticatorgetassertion①②">authenticatorGetAssertion</a> operations, the <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party①⑦⑤">Relying Party</a> compares the stored <a data-link-type="dfn" href="#signature-counter" id="ref-for-signature-counter⑧">signature counter</a> value with the new <code><a data-link-type="dfn" href="#authdata-signcount" id="ref-for-authdata-signcount②">signCount</a></code> value returned in the assertion’s <a data-link-type="dfn" href="#authenticator-data" id="ref-for-authenticator-data③⓪">authenticator data</a>. If either is non-zero, and the new <code><a data-link-type="dfn" href="#authdata-signcount" id="ref-for-authdata-signcount③">signCount</a></code> value is less than or equal to the stored value, a cloned authenticator may exist, or the authenticator may be malfunctioning.</p>
-   <p>Detecting a <a data-link-type="dfn" href="#signature-counter" id="ref-for-signature-counter⑨">signature counter</a> mismatch does not indicate whether the current operation was performed by a cloned authenticator or the original authenticator. <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party①⑦⑥">Relying Parties</a> should address this situation appropriately relative to their individual situations, i.e., their risk tolerance.</p>
+   <p>Authenticators that do not implement a <a data-link-type="dfn" href="#signature-counter" id="ref-for-signature-counter⑥">signature counter</a> leave the <code><a data-link-type="dfn" href="#authdata-signcount" id="ref-for-authdata-signcount②">signCount</a></code> in the <a data-link-type="dfn" href="#authenticator-data" id="ref-for-authenticator-data③①">authenticator data</a> constant at zero.</p>
+   <p>A <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party①⑦⑨">Relying Party</a> stores the <a data-link-type="dfn" href="#signature-counter" id="ref-for-signature-counter⑦">signature counter</a> of the most recent <a data-link-type="dfn" href="#authenticatorgetassertion" id="ref-for-authenticatorgetassertion①⓪">authenticatorGetAssertion</a> operation. (Or the counter from the <a data-link-type="dfn" href="#authenticatormakecredential" id="ref-for-authenticatormakecredential①②">authenticatorMakeCredential</a> operation if no <a data-link-type="dfn" href="#authenticatorgetassertion" id="ref-for-authenticatorgetassertion①①">authenticatorGetAssertion</a> has ever been performed on a credential.) In subsequent <a data-link-type="dfn" href="#authenticatorgetassertion" id="ref-for-authenticatorgetassertion①②">authenticatorGetAssertion</a> operations, the <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party①⑧⓪">Relying Party</a> compares the stored <a data-link-type="dfn" href="#signature-counter" id="ref-for-signature-counter⑧">signature counter</a> value with the new <code><a data-link-type="dfn" href="#authdata-signcount" id="ref-for-authdata-signcount③">signCount</a></code> value returned in the assertion’s <a data-link-type="dfn" href="#authenticator-data" id="ref-for-authenticator-data③②">authenticator data</a>. If either is non-zero, and the new <code><a data-link-type="dfn" href="#authdata-signcount" id="ref-for-authdata-signcount④">signCount</a></code> value is less than or equal to the stored value, a cloned authenticator may exist, or the authenticator may be malfunctioning.</p>
+   <p>Detecting a <a data-link-type="dfn" href="#signature-counter" id="ref-for-signature-counter⑨">signature counter</a> mismatch does not indicate whether the current operation was performed by a cloned authenticator or the original authenticator. <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party①⑧①">Relying Parties</a> should address this situation appropriately relative to their individual situations, i.e., their risk tolerance.</p>
    <p>Authenticators:</p>
    <ul>
     <li data-md>
-     <p>SHOULD implement per credential <a data-link-type="dfn" href="#signature-counter" id="ref-for-signature-counter①⓪">signature counters</a>.  This prevents the <a data-link-type="dfn" href="#signature-counter" id="ref-for-signature-counter①①">signature counter</a> value from being shared between <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party①⑦⑦">Relying Parties</a> and being possibly employed
+     <p>SHOULD implement per credential <a data-link-type="dfn" href="#signature-counter" id="ref-for-signature-counter①⓪">signature counters</a>.  This prevents the <a data-link-type="dfn" href="#signature-counter" id="ref-for-signature-counter①①">signature counter</a> value from being shared between <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party①⑧②">Relying Parties</a> and being possibly employed
 as a correlation handle for the user. Authenticators MAY implement a global <a data-link-type="dfn" href="#signature-counter" id="ref-for-signature-counter①②">signature counter</a>,
 i.e., on a per-authenticator basis, but this is less privacy-friendly for users.</p>
     <li data-md>
@@ -4208,22 +4266,22 @@ <h4 class="heading settled" data-level="6.1.1" id="sctn-sign-counter"><span clas
 accidentally decrease  (e.g., due to hardware failures).</p>
    </ul>
    <h4 class="heading settled" data-level="6.1.2" id="sctn-fido-u2f-sig-format-compat"><span class="secno">6.1.2. </span><span class="content">FIDO U2F Signature Format Compatibility</span><a class="self-link" href="#sctn-fido-u2f-sig-format-compat"></a></h4>
-   <p>The format for <a data-link-type="dfn" href="#assertion-signature" id="ref-for-assertion-signature⑥">assertion signatures</a>, which sign over the concatenation of an <a data-link-type="dfn" href="#authenticator-data" id="ref-for-authenticator-data③①">authenticator data</a> structure and the <a data-link-type="dfn" href="#collectedclientdata-hash-of-the-serialized-client-data" id="ref-for-collectedclientdata-hash-of-the-serialized-client-data⑦">hash
+   <p>The format for <a data-link-type="dfn" href="#assertion-signature" id="ref-for-assertion-signature⑥">assertion signatures</a>, which sign over the concatenation of an <a data-link-type="dfn" href="#authenticator-data" id="ref-for-authenticator-data③③">authenticator data</a> structure and the <a data-link-type="dfn" href="#collectedclientdata-hash-of-the-serialized-client-data" id="ref-for-collectedclientdata-hash-of-the-serialized-client-data⑦">hash
 of the serialized client data</a>, are compatible with the FIDO U2F authentication signature format (see <a data-link-type="dfn" href="https://fidoalliance.org/specs/fido-u2f-v1.1-id-20160915/fido-u2f-raw-message-formats-v1.1-id-20160915.html#authentication-response-message-success" id="ref-for-authentication-response-message-success">Section 5.4</a> of <a data-link-type="biblio" href="#biblio-fido-u2f-message-formats">[FIDO-U2F-Message-Formats]</a>).</p>
-   <p>This is because the first 37 bytes of the signed data in a FIDO U2F authentication response message constitute a valid <a data-link-type="dfn" href="#authenticator-data" id="ref-for-authenticator-data③②">authenticator data</a> structure, and the remaining 32 bytes are the <a data-link-type="dfn" href="#collectedclientdata-hash-of-the-serialized-client-data" id="ref-for-collectedclientdata-hash-of-the-serialized-client-data⑧">hash of the serialized client data</a>. In this <a data-link-type="dfn" href="#authenticator-data" id="ref-for-authenticator-data③③">authenticator data</a> structure, the <code><a data-link-type="dfn" href="#authdata-rpidhash" id="ref-for-authdata-rpidhash①">rpIdHash</a></code> is the FIDO U2F <a data-link-type="dfn" href="https://fidoalliance.org/specs/fido-u2f-v1.1-id-20160915/fido-u2f-raw-message-formats-v1.1-id-20160915.html#authentication-request-message---u2f_authenticate" id="ref-for-authentication-request-message---u2f_authenticate">application parameter</a>, all <code><a data-link-type="dfn" href="#authdata-flags" id="ref-for-authdata-flags①⑤">flags</a></code> except <code><a data-link-type="dfn" href="#authdata-flags-up" id="ref-for-authdata-flags-up②">UP</a></code> are always zero, and the <code><a data-link-type="dfn" href="#authdata-attestedcredentialdata" id="ref-for-authdata-attestedcredentialdata④">attestedCredentialData</a></code> and <code><a data-link-type="dfn" href="#authdata-extensions" id="ref-for-authdata-extensions④">extensions</a></code> are never present. FIDO U2F authentication signatures can therefore be verified by
+   <p>This is because the first 37 bytes of the signed data in a FIDO U2F authentication response message constitute a valid <a data-link-type="dfn" href="#authenticator-data" id="ref-for-authenticator-data③④">authenticator data</a> structure, and the remaining 32 bytes are the <a data-link-type="dfn" href="#collectedclientdata-hash-of-the-serialized-client-data" id="ref-for-collectedclientdata-hash-of-the-serialized-client-data⑧">hash of the serialized client data</a>. In this <a data-link-type="dfn" href="#authenticator-data" id="ref-for-authenticator-data③⑤">authenticator data</a> structure, the <code><a data-link-type="dfn" href="#authdata-rpidhash" id="ref-for-authdata-rpidhash①">rpIdHash</a></code> is the FIDO U2F <a data-link-type="dfn" href="https://fidoalliance.org/specs/fido-u2f-v1.1-id-20160915/fido-u2f-raw-message-formats-v1.1-id-20160915.html#authentication-request-message---u2f_authenticate" id="ref-for-authentication-request-message---u2f_authenticate">application parameter</a>, all <code><a data-link-type="dfn" href="#authdata-flags" id="ref-for-authdata-flags①⑦">flags</a></code> except <code><a data-link-type="dfn" href="#authdata-flags-up" id="ref-for-authdata-flags-up②">UP</a></code> are always zero, and the <code><a data-link-type="dfn" href="#authdata-attestedcredentialdata" id="ref-for-authdata-attestedcredentialdata④">attestedCredentialData</a></code> and <code><a data-link-type="dfn" href="#authdata-extensions" id="ref-for-authdata-extensions④">extensions</a></code> are never present. FIDO U2F authentication signatures can therefore be verified by
 the same procedure as other <a data-link-type="dfn" href="#assertion-signature" id="ref-for-assertion-signature⑦">assertion signatures</a> generated by the <a data-link-type="dfn" href="#authenticatorgetassertion" id="ref-for-authenticatorgetassertion①③">authenticatorGetAssertion</a> operation.</p>
    <h4 class="heading settled" data-level="6.1.3" id="sctn-credential-backup"><span class="secno">6.1.3. </span><span class="content">Credential Backup State</span><a class="self-link" href="#sctn-credential-backup"></a></h4>
-   <p>Credential <a data-link-type="dfn" href="#backup-eligibility" id="ref-for-backup-eligibility②">backup eligibility</a> and current <a data-link-type="dfn" href="#backup-state" id="ref-for-backup-state②">backup state</a> is conveyed by the <a data-link-type="dfn" href="#authdata-flags-be" id="ref-for-authdata-flags-be">BE</a> and <a data-link-type="dfn" href="#authdata-flags-bs" id="ref-for-authdata-flags-bs">BS</a> <a data-link-type="dfn" href="#authdata-flags" id="ref-for-authdata-flags①⑥">flags</a> in the <a data-link-type="dfn" href="#authenticator-data" id="ref-for-authenticator-data③④">authenticator data</a>, as
+   <p>Credential <a data-link-type="dfn" href="#backup-eligibility" id="ref-for-backup-eligibility②">backup eligibility</a> and current <a data-link-type="dfn" href="#backup-state" id="ref-for-backup-state②">backup state</a> is conveyed by the <a data-link-type="dfn" href="#authdata-flags-be" id="ref-for-authdata-flags-be①">BE</a> and <a data-link-type="dfn" href="#authdata-flags-bs" id="ref-for-authdata-flags-bs①">BS</a> <a data-link-type="dfn" href="#authdata-flags" id="ref-for-authdata-flags①⑧">flags</a> in the <a data-link-type="dfn" href="#authenticator-data" id="ref-for-authenticator-data③⑥">authenticator data</a>, as
 defined in <a href="#table-authData">Table <span class="table-ref-previous"></span></a>.</p>
-   <p>The value of the <a data-link-type="dfn" href="#authdata-flags-be" id="ref-for-authdata-flags-be①">BE</a> <a data-link-type="dfn" href="#authdata-flags" id="ref-for-authdata-flags①⑦">flag</a> is set during <a data-link-type="dfn" href="#authenticatormakecredential" id="ref-for-authenticatormakecredential①③">authenticatorMakeCredential</a> operation and MUST NOT change.</p>
-   <p>The value of the <a data-link-type="dfn" href="#authdata-flags-bs" id="ref-for-authdata-flags-bs①">BS</a> <a data-link-type="dfn" href="#authdata-flags" id="ref-for-authdata-flags①⑧">flag</a> may change over time based on the current state of the <a data-link-type="dfn" href="#public-key-credential-source" id="ref-for-public-key-credential-source③⑧">public key credential source</a>. <a href="#table-backupStates">Table <span class="table-ref-following"></span></a> below defines
+   <p>The value of the <a data-link-type="dfn" href="#authdata-flags-be" id="ref-for-authdata-flags-be②">BE</a> <a data-link-type="dfn" href="#authdata-flags" id="ref-for-authdata-flags①⑨">flag</a> is set during <a data-link-type="dfn" href="#authenticatormakecredential" id="ref-for-authenticatormakecredential①③">authenticatorMakeCredential</a> operation and MUST NOT change.</p>
+   <p>The value of the <a data-link-type="dfn" href="#authdata-flags-bs" id="ref-for-authdata-flags-bs②">BS</a> <a data-link-type="dfn" href="#authdata-flags" id="ref-for-authdata-flags②⓪">flag</a> may change over time based on the current state of the <a data-link-type="dfn" href="#public-key-credential-source" id="ref-for-public-key-credential-source④⑧">public key credential source</a>. <a href="#table-backupStates">Table <span class="table-ref-following"></span></a> below defines
 valid combinations and their meaning.</p>
    <figure class="table" id="table-backupStates">
     <table class="complex data longlastcol">
      <tbody>
       <tr>
-       <th><a data-link-type="dfn" href="#authdata-flags-be" id="ref-for-authdata-flags-be②">BE</a>
-       <th><a data-link-type="dfn" href="#authdata-flags-bs" id="ref-for-authdata-flags-bs②">BS</a>
+       <th><a data-link-type="dfn" href="#authdata-flags-be" id="ref-for-authdata-flags-be③">BE</a>
+       <th><a data-link-type="dfn" href="#authdata-flags-bs" id="ref-for-authdata-flags-bs③">BS</a>
        <th>Description
       <tr>
        <td><code>0</code>
@@ -4242,28 +4300,28 @@ <h4 class="heading settled" data-level="6.1.3" id="sctn-credential-backup"><span
        <td><code>1</code>
        <td> The credential is a <a data-link-type="dfn" href="#multi-device-credential" id="ref-for-multi-device-credential③">multi-device credential</a> and is currently <a data-link-type="dfn" href="#backed-up" id="ref-for-backed-up④">backed up</a>. 
     </table>
-    <figcaption> <a data-link-type="dfn" href="#authdata-flags-be" id="ref-for-authdata-flags-be③">BE</a> and <a data-link-type="dfn" href="#authdata-flags-bs" id="ref-for-authdata-flags-bs③">BS</a> <a data-link-type="dfn" href="#authdata-flags" id="ref-for-authdata-flags①⑨">flag</a> combinations </figcaption>
+    <figcaption> <a data-link-type="dfn" href="#authdata-flags-be" id="ref-for-authdata-flags-be④">BE</a> and <a data-link-type="dfn" href="#authdata-flags-bs" id="ref-for-authdata-flags-bs④">BS</a> <a data-link-type="dfn" href="#authdata-flags" id="ref-for-authdata-flags②①">flag</a> combinations </figcaption>
    </figure>
-   <p>It is RECOMMENDED that <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party①⑦⑧">Relying Parties</a> store the most recent value of these <a data-link-type="dfn" href="#authdata-flags" id="ref-for-authdata-flags②⓪">flags</a> with the <a data-link-type="dfn" href="#user-account" id="ref-for-user-account②⑥">user account</a> for future evaluation.</p>
-   <p>The following is a non-exhaustive list of how <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party①⑦⑨">Relying Parties</a> might use these <a data-link-type="dfn" href="#authdata-flags" id="ref-for-authdata-flags②①">flags</a>:</p>
+   <p>It is RECOMMENDED that <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party①⑧③">Relying Parties</a> store the most recent value of these <a data-link-type="dfn" href="#authdata-flags" id="ref-for-authdata-flags②②">flags</a> with the <a data-link-type="dfn" href="#user-account" id="ref-for-user-account②⑧">user account</a> for future evaluation.</p>
+   <p>The following is a non-exhaustive list of how <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party①⑧④">Relying Parties</a> might use these <a data-link-type="dfn" href="#authdata-flags" id="ref-for-authdata-flags②③">flags</a>:</p>
    <ul>
     <li data-md>
      <p>Requiring additional <a data-link-type="dfn" href="#authenticator" id="ref-for-authenticator①③③">authenticators</a>:</p>
-     <p>When the <a data-link-type="dfn" href="#authdata-flags-be" id="ref-for-authdata-flags-be④">BE</a> <a data-link-type="dfn" href="#authdata-flags" id="ref-for-authdata-flags②②">flag</a> is set to <code>0</code>, the credential is a <a data-link-type="dfn" href="#single-device-credential" id="ref-for-single-device-credential②">single-device credential</a> and the <a data-link-type="dfn" href="#generating-authenticator" id="ref-for-generating-authenticator③">generating authenticator</a> will never
+     <p>When the <a data-link-type="dfn" href="#authdata-flags-be" id="ref-for-authdata-flags-be⑤">BE</a> <a data-link-type="dfn" href="#authdata-flags" id="ref-for-authdata-flags②④">flag</a> is set to <code>0</code>, the credential is a <a data-link-type="dfn" href="#single-device-credential" id="ref-for-single-device-credential②">single-device credential</a> and the <a data-link-type="dfn" href="#generating-authenticator" id="ref-for-generating-authenticator③">generating authenticator</a> will never
 allow the credential to be backed up.</p>
-     <p>A <a data-link-type="dfn" href="#single-device-credential" id="ref-for-single-device-credential③">single-device credential</a> is not resilient to single device loss. <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party①⑧⓪">Relying Parties</a> SHOULD ensure that a <a data-link-type="dfn" href="#user-account" id="ref-for-user-account②⑦">user account</a> has additional <a data-link-type="dfn" href="#authenticator" id="ref-for-authenticator①③④">authenticators</a> <a data-link-type="dfn" href="#registration-ceremony" id="ref-for-registration-ceremony⑥">registered</a> and/or an account recovery process in place.</p>
-     <p>For example, the user could be prompted to set up an additional <a data-link-type="dfn" href="#authenticator" id="ref-for-authenticator①③⑤">authenticator</a>, such as a <a data-link-type="dfn" href="#roaming-authenticators" id="ref-for-roaming-authenticators⑦">roaming authenticator</a> or an <a data-link-type="dfn" href="#authenticator" id="ref-for-authenticator①③⑥">authenticator</a> that is capable of <a data-link-type="dfn" href="#multi-device-credential" id="ref-for-multi-device-credential④">multi-device credentials</a>.</p>
+     <p>A <a data-link-type="dfn" href="#single-device-credential" id="ref-for-single-device-credential③">single-device credential</a> is not resilient to single device loss. <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party①⑧⑤">Relying Parties</a> SHOULD ensure that each <a data-link-type="dfn" href="#user-account" id="ref-for-user-account②⑨">user account</a> has additional <a data-link-type="dfn" href="#authenticator" id="ref-for-authenticator①③④">authenticators</a> <a data-link-type="dfn" href="#registration-ceremony" id="ref-for-registration-ceremony⑥">registered</a> and/or an account recovery process in place.
+For example, the user could be prompted to set up an additional <a data-link-type="dfn" href="#authenticator" id="ref-for-authenticator①③⑤">authenticator</a>, such as a <a data-link-type="dfn" href="#roaming-authenticators" id="ref-for-roaming-authenticators⑦">roaming authenticator</a> or an <a data-link-type="dfn" href="#authenticator" id="ref-for-authenticator①③⑥">authenticator</a> that is capable of <a data-link-type="dfn" href="#multi-device-credential" id="ref-for-multi-device-credential④">multi-device credentials</a>.</p>
     <li data-md>
      <p>Upgrading a user to a password-free account:</p>
-     <p>When the <a data-link-type="dfn" href="#authdata-flags-bs" id="ref-for-authdata-flags-bs④">BS</a> <a data-link-type="dfn" href="#authdata-flags" id="ref-for-authdata-flags②③">flag</a> changes from <code>0</code> to <code>1</code>, the <a data-link-type="dfn" href="#authenticator" id="ref-for-authenticator①③⑦">authenticator</a> is signaling that the <a data-link-type="dfn" href="https://w3c.github.io/webappsec-credential-management/#concept-credential" id="ref-for-concept-credential①④">credential</a> is backed up and is protected from single device loss.</p>
-     <p>A <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party①⑧①">Relying Party</a> may decide to prompt the user to upgrade their account security and remove their password.</p>
+     <p>When the <a data-link-type="dfn" href="#authdata-flags-bs" id="ref-for-authdata-flags-bs⑤">BS</a> <a data-link-type="dfn" href="#authdata-flags" id="ref-for-authdata-flags②⑤">flag</a> changes from <code>0</code> to <code>1</code>, the <a data-link-type="dfn" href="#authenticator" id="ref-for-authenticator①③⑦">authenticator</a> is signaling that the <a data-link-type="dfn" href="https://w3c.github.io/webappsec-credential-management/#concept-credential" id="ref-for-concept-credential①③">credential</a> is backed up and is protected from single device loss.</p>
+     <p>The <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party①⑧⑥">Relying Party</a> MAY choose to prompt the user to upgrade their account security and remove their password.</p>
     <li data-md>
      <p>Adding an additional factor after a state change:</p>
-     <p>When the <a data-link-type="dfn" href="#authdata-flags-bs" id="ref-for-authdata-flags-bs⑤">BS</a> <a data-link-type="dfn" href="#authdata-flags" id="ref-for-authdata-flags②④">flag</a> changes from <code>1</code> to <code>0</code>, the <a data-link-type="dfn" href="#authenticator" id="ref-for-authenticator①③⑧">authenticator</a> is signaling that the <a data-link-type="dfn" href="https://w3c.github.io/webappsec-credential-management/#concept-credential" id="ref-for-concept-credential①⑤">credential</a> is no longer backed up,
+     <p>When the <a data-link-type="dfn" href="#authdata-flags-bs" id="ref-for-authdata-flags-bs⑥">BS</a> <a data-link-type="dfn" href="#authdata-flags" id="ref-for-authdata-flags②⑥">flag</a> changes from <code>1</code> to <code>0</code>, the <a data-link-type="dfn" href="#authenticator" id="ref-for-authenticator①③⑧">authenticator</a> is signaling that the <a data-link-type="dfn" href="https://w3c.github.io/webappsec-credential-management/#concept-credential" id="ref-for-concept-credential①④">credential</a> is no longer backed up,
 and no longer protected from single device loss. This could be the result of the user actions, such as disabling the backup service,
 or errors, such as issues with the backup service.</p>
-     <p>When this transition occurs, the <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party①⑧②">Relying Party</a> SHOULD guide the user through a process to validate their other sign in factors.
-If the user does not have another credential for their account, they SHOULD be guided through adding an additional authentication factor
+     <p>When this transition occurs, the <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party①⑧⑦">Relying Party</a> SHOULD guide the user through a process to validate their other authentication factors.
+If the user does not have another credential for their account, they SHOULD be guided through adding an additional credential
 to ensure they do not lose access to their account. For example, the user could be prompted to set up an additional <a data-link-type="dfn" href="#authenticator" id="ref-for-authenticator①③⑨">authenticator</a>,
 such as a <a data-link-type="dfn" href="#roaming-authenticators" id="ref-for-roaming-authenticators⑧">roaming authenticator</a> or an <a data-link-type="dfn" href="#authenticator" id="ref-for-authenticator①④⓪">authenticator</a> that is capable of <a data-link-type="dfn" href="#multi-device-credential" id="ref-for-multi-device-credential⑤">multi-device credentials</a>.</p>
    </ul>
@@ -4342,7 +4400,7 @@ <h3 class="heading settled" data-level="6.2" id="sctn-authenticator-taxonomy"><s
 these authenticators support <a data-link-type="dfn" href="#user-verification" id="ref-for-user-verification③①">user verification</a> as a second <a data-link-type="dfn" href="https://pages.nist.gov/800-63-3/sp800-63-3.html#af" id="ref-for-af④">authentication factor</a>,
 typically a PIN or <a data-link-type="dfn" href="#biometric-recognition" id="ref-for-biometric-recognition③">biometric recognition</a>.
 The <a data-link-type="dfn" href="#authenticator" id="ref-for-authenticator①④⑤">authenticator</a> can thus act as two kinds of <a data-link-type="dfn" href="https://pages.nist.gov/800-63-3/sp800-63-3.html#af" id="ref-for-af⑤">authentication factor</a>,
-which enables <a data-link-type="dfn" href="https://pages.nist.gov/800-63-3/sp800-63-3.html#af" id="ref-for-af⑥">multi-factor</a> authentication while eliminating the need to share a password with the <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party①⑧③">Relying Party</a>.</p>
+which enables <a data-link-type="dfn" href="https://pages.nist.gov/800-63-3/sp800-63-3.html#af" id="ref-for-af⑥">multi-factor</a> authentication while eliminating the need to share a password with the <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party①⑧⑧">Relying Party</a>.</p>
    <p>The four combinations not named in <a href="#table-authenticatorTypes">Table <span class="table-ref-previous"></span></a> have less distinguished use cases:</p>
    <ul>
     <li data-md>
@@ -4380,7 +4438,7 @@ <h4 class="heading settled" data-level="6.2.1" id="sctn-authenticator-attachment
    <p>The primary use case for <a data-link-type="dfn" href="#platform-authenticators" id="ref-for-platform-authenticators②③">platform authenticators</a> is to register a particular <a data-link-type="dfn" href="#client-device" id="ref-for-client-device③⑥">client device</a> as a "trusted device",
 so the <a data-link-type="dfn" href="#client-device" id="ref-for-client-device③⑦">client device</a> itself acts as a <a data-link-type="dfn" href="https://pages.nist.gov/800-63-3/sp800-63-3.html#af" id="ref-for-af⑨">something you have</a> <a data-link-type="dfn" href="https://pages.nist.gov/800-63-3/sp800-63-3.html#af" id="ref-for-af①⓪">authentication factor</a> for future <a data-link-type="dfn" href="#authentication" id="ref-for-authentication①①">authentication</a>.
 This gives the user the convenience benefit
-of not needing a <a data-link-type="dfn" href="#roaming-authenticators" id="ref-for-roaming-authenticators②①">roaming authenticator</a> for future <a data-link-type="dfn" href="#authentication-ceremony" id="ref-for-authentication-ceremony①⑥">authentication ceremonies</a>, e.g., the user will not have to dig around in
+of not needing a <a data-link-type="dfn" href="#roaming-authenticators" id="ref-for-roaming-authenticators②①">roaming authenticator</a> for future <a data-link-type="dfn" href="#authentication-ceremony" id="ref-for-authentication-ceremony①⑦">authentication ceremonies</a>, e.g., the user will not have to dig around in
 their pocket for their key fob or phone.</p>
    <p>Use cases for <a data-link-type="dfn" href="#roaming-authenticators" id="ref-for-roaming-authenticators②②">roaming authenticators</a> include: <a data-link-type="dfn" href="#authentication" id="ref-for-authentication①②">authenticating</a> on a new <a data-link-type="dfn" href="#client-device" id="ref-for-client-device③⑧">client device</a> for the first time,
 on rarely used <a data-link-type="dfn" href="#client-device" id="ref-for-client-device③⑨">client devices</a>, <a data-link-type="dfn" href="#client-device" id="ref-for-client-device④⓪">client devices</a> shared between multiple users,
@@ -4389,15 +4447,15 @@ <h4 class="heading settled" data-level="6.2.1" id="sctn-authenticator-attachment
 A <a data-link-type="dfn" href="#roaming-authenticators" id="ref-for-roaming-authenticators②③">roaming authenticator</a> can also be used to hold
 backup <a data-link-type="dfn" href="#public-key-credential" id="ref-for-public-key-credential④⑥">credentials</a> in case another <a data-link-type="dfn" href="#authenticator" id="ref-for-authenticator①⑤②">authenticator</a> is lost.</p>
    <h4 class="heading settled" data-level="6.2.2" id="sctn-credential-storage-modality"><span class="secno">6.2.2. </span><span class="content">Credential Storage Modality</span><a class="self-link" href="#sctn-credential-storage-modality"></a></h4>
-   <p>An <a data-link-type="dfn" href="#authenticator" id="ref-for-authenticator①⑤③">authenticator</a> can store a <a data-link-type="dfn" href="#public-key-credential-source" id="ref-for-public-key-credential-source③⑨">public key credential source</a> in one of two ways:</p>
+   <p>An <a data-link-type="dfn" href="#authenticator" id="ref-for-authenticator①⑤③">authenticator</a> can store a <a data-link-type="dfn" href="#public-key-credential-source" id="ref-for-public-key-credential-source④⑨">public key credential source</a> in one of two ways:</p>
    <ol>
     <li data-md>
      <p>In persistent storage embedded in the <a data-link-type="dfn" href="#authenticator" id="ref-for-authenticator①⑤④">authenticator</a>, <a data-link-type="dfn" href="#client" id="ref-for-client⑦④">client</a> or <a data-link-type="dfn" href="#client-device" id="ref-for-client-device④③">client device</a>, e.g., in a secure element.
 This is a technical requirement for a <a data-link-type="dfn" href="#client-side-discoverable-public-key-credential-source" id="ref-for-client-side-discoverable-public-key-credential-source③">client-side discoverable public key credential source</a>.</p>
     <li data-md>
      <p>By encrypting (i.e., wrapping) the <a data-link-type="dfn" href="#credential-private-key" id="ref-for-credential-private-key①②">credential private key</a> such that only this <a data-link-type="dfn" href="#authenticator" id="ref-for-authenticator①⑤⑤">authenticator</a> can decrypt (i.e., unwrap) it and letting the resulting
-ciphertext be the <a data-link-type="dfn" href="#credential-id" id="ref-for-credential-id②③">credential ID</a> for the <a data-link-type="dfn" href="#public-key-credential-source" id="ref-for-public-key-credential-source④⓪">public key credential source</a>. The <a data-link-type="dfn" href="#credential-id" id="ref-for-credential-id②④">credential ID</a> is stored by the <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party①⑧④">Relying Party</a> and returned to the <a data-link-type="dfn" href="#authenticator" id="ref-for-authenticator①⑤⑥">authenticator</a> via the <code class="idl"><a data-link-type="idl" href="#dom-publickeycredentialrequestoptions-allowcredentials" id="ref-for-dom-publickeycredentialrequestoptions-allowcredentials①④">allowCredentials</a></code> option of <code class="idl"><a data-link-type="idl" href="https://w3c.github.io/webappsec-credential-management/#dom-credentialscontainer-get" id="ref-for-dom-credentialscontainer-get②⑦">get()</a></code>, which allows the <a data-link-type="dfn" href="#authenticator" id="ref-for-authenticator①⑤⑦">authenticator</a> to decrypt and use the <a data-link-type="dfn" href="#credential-private-key" id="ref-for-credential-private-key①③">credential private key</a>.</p>
-     <p>This enables the <a data-link-type="dfn" href="#authenticator" id="ref-for-authenticator①⑤⑧">authenticator</a> to have unlimited storage capacity for <a data-link-type="dfn" href="#credential-private-key" id="ref-for-credential-private-key①④">credential private keys</a>, since the encrypted <a data-link-type="dfn" href="#credential-private-key" id="ref-for-credential-private-key①⑤">credential private keys</a> are stored by the <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party①⑧⑤">Relying Party</a> instead of by the <a data-link-type="dfn" href="#authenticator" id="ref-for-authenticator①⑤⑨">authenticator</a> - but it means that a <a data-link-type="dfn" href="https://w3c.github.io/webappsec-credential-management/#concept-credential" id="ref-for-concept-credential①⑥">credential</a> stored in this way must be retrieved from the <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party①⑧⑥">Relying Party</a> before the <a data-link-type="dfn" href="#authenticator" id="ref-for-authenticator①⑥⓪">authenticator</a> can use it.</p>
+ciphertext be the <a data-link-type="dfn" href="#credential-id" id="ref-for-credential-id②④">credential ID</a> for the <a data-link-type="dfn" href="#public-key-credential-source" id="ref-for-public-key-credential-source⑤⓪">public key credential source</a>. The <a data-link-type="dfn" href="#credential-id" id="ref-for-credential-id②⑤">credential ID</a> is stored by the <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party①⑧⑨">Relying Party</a> and returned to the <a data-link-type="dfn" href="#authenticator" id="ref-for-authenticator①⑤⑥">authenticator</a> via the <code class="idl"><a data-link-type="idl" href="#dom-publickeycredentialrequestoptions-allowcredentials" id="ref-for-dom-publickeycredentialrequestoptions-allowcredentials①④">allowCredentials</a></code> option of <code class="idl"><a data-link-type="idl" href="https://w3c.github.io/webappsec-credential-management/#dom-credentialscontainer-get" id="ref-for-dom-credentialscontainer-get②⑦">get()</a></code>, which allows the <a data-link-type="dfn" href="#authenticator" id="ref-for-authenticator①⑤⑦">authenticator</a> to decrypt and use the <a data-link-type="dfn" href="#credential-private-key" id="ref-for-credential-private-key①③">credential private key</a>.</p>
+     <p>This enables the <a data-link-type="dfn" href="#authenticator" id="ref-for-authenticator①⑤⑧">authenticator</a> to have unlimited storage capacity for <a data-link-type="dfn" href="#credential-private-key" id="ref-for-credential-private-key①④">credential private keys</a>, since the encrypted <a data-link-type="dfn" href="#credential-private-key" id="ref-for-credential-private-key①⑤">credential private keys</a> are stored by the <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party①⑨⓪">Relying Party</a> instead of by the <a data-link-type="dfn" href="#authenticator" id="ref-for-authenticator①⑤⑨">authenticator</a> - but it means that a <a data-link-type="dfn" href="https://w3c.github.io/webappsec-credential-management/#concept-credential" id="ref-for-concept-credential①⑤">credential</a> stored in this way must be retrieved from the <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party①⑨①">Relying Party</a> before the <a data-link-type="dfn" href="#authenticator" id="ref-for-authenticator①⑥⓪">authenticator</a> can use it.</p>
    </ol>
    <p>Which of these storage strategies an <a data-link-type="dfn" href="#authenticator" id="ref-for-authenticator①⑥①">authenticator</a> supports defines the <a data-link-type="dfn" href="#authenticator" id="ref-for-authenticator①⑥②">authenticator</a>'s <dfn class="dfn-paneled" data-dfn-type="dfn" data-lt="credential storage modality" data-noexport id="credential-storage-modality">credential storage
 modality</dfn> as follows:</p>
@@ -4408,30 +4466,30 @@ <h4 class="heading settled" data-level="6.2.2" id="sctn-credential-storage-modal
 credential capable</dfn>.</p>
     <li data-md>
      <p>An <a data-link-type="dfn" href="#authenticator" id="ref-for-authenticator①⑥⑤">authenticator</a> has the <dfn class="dfn-paneled" data-dfn-type="dfn" data-noexport id="server-side-credential-storage-modality">server-side credential storage modality</dfn> if it does not have the <a data-link-type="dfn" href="#client-side-credential-storage-modality" id="ref-for-client-side-credential-storage-modality⑤">client-side credential storage
-modality</a>, i.e., it only supports storing <a data-link-type="dfn" href="#credential-private-key" id="ref-for-credential-private-key①⑥">credential private keys</a> as a ciphertext in the <a data-link-type="dfn" href="#credential-id" id="ref-for-credential-id②⑤">credential ID</a>.</p>
+modality</a>, i.e., it only supports storing <a data-link-type="dfn" href="#credential-private-key" id="ref-for-credential-private-key①⑥">credential private keys</a> as a ciphertext in the <a data-link-type="dfn" href="#credential-id" id="ref-for-credential-id②⑥">credential ID</a>.</p>
    </ul>
    <p>Note that a <a data-link-type="dfn" href="#discoverable-credential-capable" id="ref-for-discoverable-credential-capable⑤">discoverable credential capable</a> <a data-link-type="dfn" href="#authenticator" id="ref-for-authenticator①⑥⑥">authenticator</a> MAY support both storage strategies. In this case, the <a data-link-type="dfn" href="#authenticator" id="ref-for-authenticator①⑥⑦">authenticator</a> MAY
 at its discretion use different storage strategies for different <a data-link-type="dfn" href="#public-key-credential" id="ref-for-public-key-credential④⑦">credentials</a>, though subject to the <code class="idl"><a data-link-type="idl" href="#dom-authenticatorselectioncriteria-residentkey" id="ref-for-dom-authenticatorselectioncriteria-residentkey⑥">residentKey</a></code> or <code class="idl"><a data-link-type="idl" href="#dom-authenticatorselectioncriteria-requireresidentkey" id="ref-for-dom-authenticatorselectioncriteria-requireresidentkey④">requireResidentKey</a></code> options of <code class="idl"><a data-link-type="idl" href="https://w3c.github.io/webappsec-credential-management/#dom-credentialscontainer-create" id="ref-for-dom-credentialscontainer-create②②">create()</a></code>.</p>
    <h4 class="heading settled" data-level="6.2.3" id="sctn-authentication-factor-capability"><span class="secno">6.2.3. </span><span class="content"><dfn class="dfn-paneled" data-dfn-type="dfn" data-noexport id="authentication-factor-capability">Authentication Factor Capability</dfn></span><a class="self-link" href="#sctn-authentication-factor-capability"></a></h4>
-   <p>There are three broad classes of <a data-link-type="dfn" href="https://pages.nist.gov/800-63-3/sp800-63-3.html#af" id="ref-for-af①①">authentication factors</a> that can be used to prove an identity during an <a data-link-type="dfn" href="#authentication-ceremony" id="ref-for-authentication-ceremony①⑦">authentication
+   <p>There are three broad classes of <a data-link-type="dfn" href="https://pages.nist.gov/800-63-3/sp800-63-3.html#af" id="ref-for-af①①">authentication factors</a> that can be used to prove an identity during an <a data-link-type="dfn" href="#authentication-ceremony" id="ref-for-authentication-ceremony①⑧">authentication
 ceremony</a>: <a data-link-type="dfn" href="https://pages.nist.gov/800-63-3/sp800-63-3.html#af" id="ref-for-af①②">something you have</a>, <a data-link-type="dfn" href="https://pages.nist.gov/800-63-3/sp800-63-3.html#af" id="ref-for-af①③">something you know</a> and <a data-link-type="dfn" href="https://pages.nist.gov/800-63-3/sp800-63-3.html#af" id="ref-for-af①④">something you are</a>. Examples include a physical key, a password,
 and a fingerprint, respectively.</p>
    <p>All <a data-link-type="dfn" href="#webauthn-authenticator" id="ref-for-webauthn-authenticator⑤">WebAuthn Authenticators</a> belong to the <a data-link-type="dfn" href="https://pages.nist.gov/800-63-3/sp800-63-3.html#af" id="ref-for-af①⑤">something you have</a> class, but an <a data-link-type="dfn" href="#authenticator" id="ref-for-authenticator①⑥⑧">authenticator</a> that supports <a data-link-type="dfn" href="#user-verification" id="ref-for-user-verification③②">user
 verification</a> can also act as one or two additional kinds of <a data-link-type="dfn" href="https://pages.nist.gov/800-63-3/sp800-63-3.html#af" id="ref-for-af①⑥">authentication factor</a>. For example, if the <a data-link-type="dfn" href="#authenticator" id="ref-for-authenticator①⑥⑨">authenticator</a> can
 verify a PIN, the PIN is <a data-link-type="dfn" href="https://pages.nist.gov/800-63-3/sp800-63-3.html#af" id="ref-for-af①⑦">something you know</a>, and a <a data-link-type="dfn" href="#biometric-authenticator" id="ref-for-biometric-authenticator">biometric authenticator</a> can verify <a data-link-type="dfn" href="https://pages.nist.gov/800-63-3/sp800-63-3.html#af" id="ref-for-af①⑧">something you are</a>. Therefore, an <a data-link-type="dfn" href="#authenticator" id="ref-for-authenticator①⑦⓪">authenticator</a> that supports <a data-link-type="dfn" href="#user-verification" id="ref-for-user-verification③③">user verification</a> is <dfn class="dfn-paneled" data-dfn-type="dfn" data-noexport id="multi-factor-capable">multi-factor capable</dfn>. Conversely, an <a data-link-type="dfn" href="#authenticator" id="ref-for-authenticator①⑦①">authenticator</a> that is
 not <a data-link-type="dfn" href="#multi-factor-capable" id="ref-for-multi-factor-capable④">multi-factor capable</a> is <dfn class="dfn-paneled" data-dfn-type="dfn" data-noexport id="single-factor-capable">single-factor capable</dfn>. Note that a single <a data-link-type="dfn" href="#multi-factor-capable" id="ref-for-multi-factor-capable⑤">multi-factor capable</a> <a data-link-type="dfn" href="#authenticator" id="ref-for-authenticator①⑦②">authenticator</a> could support several modes of <a data-link-type="dfn" href="#user-verification" id="ref-for-user-verification③④">user verification</a>, meaning it could act as all three kinds of <a data-link-type="dfn" href="https://pages.nist.gov/800-63-3/sp800-63-3.html#af" id="ref-for-af①⑨">authentication factor</a>.</p>
-   <p>Although <a data-link-type="dfn" href="#user-verification" id="ref-for-user-verification③⑤">user verification</a> is performed locally on the <a data-link-type="dfn" href="#authenticator" id="ref-for-authenticator①⑦③">authenticator</a> and not by the <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party①⑧⑦">Relying Party</a>, the <a data-link-type="dfn" href="#authenticator" id="ref-for-authenticator①⑦④">authenticator</a> indicates if <a data-link-type="dfn" href="#user-verification" id="ref-for-user-verification③⑥">user verification</a> was performed by setting the <a data-link-type="dfn" href="#authdata-flags-uv" id="ref-for-authdata-flags-uv④">UV</a> <a data-link-type="dfn" href="#authdata-flags" id="ref-for-authdata-flags②⑤">flag</a> in the signed response returned to the <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party①⑧⑧">Relying Party</a>.
-The <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party①⑧⑨">Relying Party</a> can therefore use the <a data-link-type="dfn" href="#authdata-flags-uv" id="ref-for-authdata-flags-uv⑤">UV</a> <a data-link-type="dfn" href="#authdata-flags" id="ref-for-authdata-flags②⑥">flag</a> to verify that additional <a data-link-type="dfn" href="https://pages.nist.gov/800-63-3/sp800-63-3.html#af" id="ref-for-af②⓪">authentication factors</a> were used in a <a data-link-type="dfn" href="#registration" id="ref-for-registration①⑤">registration</a> or <a data-link-type="dfn" href="#authentication-ceremony" id="ref-for-authentication-ceremony①⑧">authentication ceremony</a>. The authenticity of the <a data-link-type="dfn" href="#authdata-flags-uv" id="ref-for-authdata-flags-uv⑥">UV</a> <a data-link-type="dfn" href="#authdata-flags" id="ref-for-authdata-flags②⑦">flag</a> can in turn be assessed by inspecting the <a data-link-type="dfn" href="#authenticator" id="ref-for-authenticator①⑦⑤">authenticator</a>'s <a data-link-type="dfn" href="#attestation-statement" id="ref-for-attestation-statement①⑥">attestation statement</a>.</p>
+   <p>Although <a data-link-type="dfn" href="#user-verification" id="ref-for-user-verification③⑤">user verification</a> is performed locally on the <a data-link-type="dfn" href="#authenticator" id="ref-for-authenticator①⑦③">authenticator</a> and not by the <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party①⑨②">Relying Party</a>, the <a data-link-type="dfn" href="#authenticator" id="ref-for-authenticator①⑦④">authenticator</a> indicates if <a data-link-type="dfn" href="#user-verification" id="ref-for-user-verification③⑥">user verification</a> was performed by setting the <a data-link-type="dfn" href="#authdata-flags-uv" id="ref-for-authdata-flags-uv④">UV</a> <a data-link-type="dfn" href="#authdata-flags" id="ref-for-authdata-flags②⑦">flag</a> in the signed response returned to the <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party①⑨③">Relying Party</a>.
+The <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party①⑨④">Relying Party</a> can therefore use the <a data-link-type="dfn" href="#authdata-flags-uv" id="ref-for-authdata-flags-uv⑤">UV</a> <a data-link-type="dfn" href="#authdata-flags" id="ref-for-authdata-flags②⑧">flag</a> to verify that additional <a data-link-type="dfn" href="https://pages.nist.gov/800-63-3/sp800-63-3.html#af" id="ref-for-af②⓪">authentication factors</a> were used in a <a data-link-type="dfn" href="#registration" id="ref-for-registration①⑧">registration</a> or <a data-link-type="dfn" href="#authentication-ceremony" id="ref-for-authentication-ceremony①⑨">authentication ceremony</a>. The authenticity of the <a data-link-type="dfn" href="#authdata-flags-uv" id="ref-for-authdata-flags-uv⑥">UV</a> <a data-link-type="dfn" href="#authdata-flags" id="ref-for-authdata-flags②⑨">flag</a> can in turn be assessed by inspecting the <a data-link-type="dfn" href="#authenticator" id="ref-for-authenticator①⑦⑤">authenticator</a>'s <a data-link-type="dfn" href="#attestation-statement" id="ref-for-attestation-statement①⑦">attestation statement</a>.</p>
    <h3 class="heading settled" data-level="6.3" id="sctn-authenticator-ops"><span class="secno">6.3. </span><span class="content"><dfn class="dfn-paneled" data-dfn-type="dfn" data-noexport id="authenticator-operations">Authenticator Operations</dfn></span><a class="self-link" href="#sctn-authenticator-ops"></a></h3>
    <p>A <a data-link-type="dfn" href="#webauthn-client" id="ref-for-webauthn-client⑥">WebAuthn Client</a> MUST connect to an authenticator in order to invoke any of the operations of that authenticator. This connection
 defines an <dfn class="dfn-paneled" data-dfn-type="dfn" data-noexport id="authenticator-session">authenticator session</dfn>. An authenticator must maintain isolation between sessions. It may do this by only allowing one
 session to exist at any particular time, or by providing more complicated session management.</p>
    <p>The following operations can be invoked by the client in an authenticator session.</p>
    <h4 class="heading settled" data-level="6.3.1" id="sctn-op-lookup-credsource-by-credid"><span class="secno">6.3.1. </span><span class="content">Lookup Credential Source by Credential ID Algorithm</span><a class="self-link" href="#sctn-op-lookup-credsource-by-credid"></a></h4>
-   <p>The result of <dfn class="dfn-paneled" data-dfn-for="credential id" data-dfn-type="dfn" data-noexport id="credential-id-looking-up">looking up</dfn> a <a data-link-type="dfn" href="#credential-id" id="ref-for-credential-id②⑥">credential id</a> <var>credentialId</var> in an <a data-link-type="dfn" href="#authenticator" id="ref-for-authenticator①⑦⑥">authenticator</a> <var>authenticator</var> is the result of the following algorithm:</p>
+   <p>The result of <dfn class="dfn-paneled" data-dfn-for="credential id" data-dfn-type="dfn" data-noexport id="credential-id-looking-up">looking up</dfn> a <a data-link-type="dfn" href="#credential-id" id="ref-for-credential-id②⑦">credential id</a> <var>credentialId</var> in an <a data-link-type="dfn" href="#authenticator" id="ref-for-authenticator①⑦⑥">authenticator</a> <var>authenticator</var> is the result of the following algorithm:</p>
    <ol>
     <li data-md>
-     <p>If <var>authenticator</var> can decrypt <var>credentialId</var> into a <a data-link-type="dfn" href="#public-key-credential-source" id="ref-for-public-key-credential-source④①">public key credential source</a> <var>credSource</var>:</p>
+     <p>If <var>authenticator</var> can decrypt <var>credentialId</var> into a <a data-link-type="dfn" href="#public-key-credential-source" id="ref-for-public-key-credential-source⑤①">public key credential source</a> <var>credSource</var>:</p>
      <ol>
       <li data-md>
        <p>Set <var>credSource</var>.<a data-link-type="dfn" href="#public-key-credential-source-id" id="ref-for-public-key-credential-source-id">id</a> to <var>credentialId</var>.</p>
@@ -4439,7 +4497,7 @@ <h4 class="heading settled" data-level="6.3.1" id="sctn-op-lookup-credsource-by-
        <p>Return <var>credSource</var>.</p>
      </ol>
     <li data-md>
-     <p><a data-link-type="dfn" href="https://infra.spec.whatwg.org/#map-iterate" id="ref-for-map-iterate②">For each</a> <a data-link-type="dfn" href="#public-key-credential-source" id="ref-for-public-key-credential-source④②">public key credential source</a> <var>credSource</var> of <var>authenticator</var>’s <a data-link-type="dfn" href="#authenticator-credentials-map" id="ref-for-authenticator-credentials-map①">credentials map</a>:</p>
+     <p><a data-link-type="dfn" href="https://infra.spec.whatwg.org/#map-iterate" id="ref-for-map-iterate②">For each</a> <a data-link-type="dfn" href="#public-key-credential-source" id="ref-for-public-key-credential-source⑤②">public key credential source</a> <var>credSource</var> of <var>authenticator</var>’s <a data-link-type="dfn" href="#authenticator-credentials-map" id="ref-for-authenticator-credentials-map①">credentials map</a>:</p>
      <ol>
       <li data-md>
        <p>If <var>credSource</var>.<a data-link-type="dfn" href="#public-key-credential-source-id" id="ref-for-public-key-credential-source-id①">id</a> is <var>credentialId</var>, return <var>credSource</var>.</p>
@@ -4455,10 +4513,10 @@ <h4 class="heading settled" data-level="6.3.2" id="sctn-op-make-cred"><span clas
      <p>The <a data-link-type="dfn" href="#collectedclientdata-hash-of-the-serialized-client-data" id="ref-for-collectedclientdata-hash-of-the-serialized-client-data⑨">hash of the serialized client data</a>, provided by the client.</p>
     <dt data-md><var>rpEntity</var>
     <dd data-md>
-     <p>The <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party①⑨⓪">Relying Party</a>'s <code class="idl"><a data-link-type="idl" href="#dictdef-publickeycredentialrpentity" id="ref-for-dictdef-publickeycredentialrpentity⑥">PublicKeyCredentialRpEntity</a></code>.</p>
+     <p>The <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party①⑨⑤">Relying Party</a>'s <code class="idl"><a data-link-type="idl" href="#dictdef-publickeycredentialrpentity" id="ref-for-dictdef-publickeycredentialrpentity⑥">PublicKeyCredentialRpEntity</a></code>.</p>
     <dt data-md><var>userEntity</var>
     <dd data-md>
-     <p>The <a data-link-type="dfn" href="#user-account" id="ref-for-user-account②⑧">user account’s</a> <code class="idl"><a data-link-type="idl" href="#dictdef-publickeycredentialuserentity" id="ref-for-dictdef-publickeycredentialuserentity⑤">PublicKeyCredentialUserEntity</a></code>, containing the <a data-link-type="dfn" href="#user-handle" id="ref-for-user-handle①⑨">user handle</a> given by the <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party①⑨①">Relying Party</a>.</p>
+     <p>The <a data-link-type="dfn" href="#user-account" id="ref-for-user-account③⓪">user account’s</a> <code class="idl"><a data-link-type="idl" href="#dictdef-publickeycredentialuserentity" id="ref-for-dictdef-publickeycredentialuserentity⑤">PublicKeyCredentialUserEntity</a></code>, containing the <a data-link-type="dfn" href="#user-handle" id="ref-for-user-handle①⑨">user handle</a> given by the <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party①⑨⑥">Relying Party</a>.</p>
     <dt data-md><var>requireResidentKey</var>
     <dd data-md>
      <p>The <a data-link-type="dfn" href="#effective-resident-key-requirement-for-credential-creation" id="ref-for-effective-resident-key-requirement-for-credential-creation">effective resident key requirement for credential creation</a>, a Boolean value determined by the <a data-link-type="dfn" href="#client" id="ref-for-client⑦⑤">client</a>.</p>
@@ -4472,11 +4530,11 @@ <h4 class="heading settled" data-level="6.3.2" id="sctn-op-make-cred"><span clas
      <p>The <a data-link-type="dfn" href="#effective-user-verification-requirement-for-credential-creation" id="ref-for-effective-user-verification-requirement-for-credential-creation">effective user verification requirement for credential creation</a>, a Boolean value determined by the <a data-link-type="dfn" href="#client" id="ref-for-client⑦⑥">client</a>.</p>
     <dt data-md><var>credTypesAndPubKeyAlgs</var>
     <dd data-md>
-     <p>A sequence of pairs of <code class="idl"><a data-link-type="idl" href="#enumdef-publickeycredentialtype" id="ref-for-enumdef-publickeycredentialtype⑧">PublicKeyCredentialType</a></code> and public key algorithms (<code class="idl"><a data-link-type="idl" href="#typedefdef-cosealgorithmidentifier" id="ref-for-typedefdef-cosealgorithmidentifier①⓪">COSEAlgorithmIdentifier</a></code>) requested by the <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party①⑨②">Relying Party</a>. This sequence is ordered from most preferred to least preferred. The <a data-link-type="dfn" href="#authenticator" id="ref-for-authenticator①⑦⑦">authenticator</a> makes a best-effort to create the most
+     <p>A sequence of pairs of <code class="idl"><a data-link-type="idl" href="#enumdef-publickeycredentialtype" id="ref-for-enumdef-publickeycredentialtype⑧">PublicKeyCredentialType</a></code> and public key algorithms (<code class="idl"><a data-link-type="idl" href="#typedefdef-cosealgorithmidentifier" id="ref-for-typedefdef-cosealgorithmidentifier①⓪">COSEAlgorithmIdentifier</a></code>) requested by the <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party①⑨⑦">Relying Party</a>. This sequence is ordered from most preferred to least preferred. The <a data-link-type="dfn" href="#authenticator" id="ref-for-authenticator①⑦⑦">authenticator</a> makes a best-effort to create the most
 preferred credential that it can.</p>
     <dt data-md><var>excludeCredentialDescriptorList</var>
     <dd data-md>
-     <p>An OPTIONAL list of <code class="idl"><a data-link-type="idl" href="#dictdef-publickeycredentialdescriptor" id="ref-for-dictdef-publickeycredentialdescriptor①①">PublicKeyCredentialDescriptor</a></code> objects provided by the <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party①⑨③">Relying Party</a> with the intention that, if any of
+     <p>An OPTIONAL list of <code class="idl"><a data-link-type="idl" href="#dictdef-publickeycredentialdescriptor" id="ref-for-dictdef-publickeycredentialdescriptor①②">PublicKeyCredentialDescriptor</a></code> objects provided by the <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party①⑨⑧">Relying Party</a> with the intention that, if any of
 these are known to the authenticator, it SHOULD NOT create a new credential. <var>excludeCredentialDescriptorList</var> contains a
 list of known credentials.</p>
     <dt data-md><var>enterpriseAttestationPossible</var>
@@ -4485,7 +4543,7 @@ <h4 class="heading settled" data-level="6.3.2" id="sctn-op-make-cred"><span clas
     <dt data-md><var>extensions</var>
     <dd data-md>
      <p>A <a data-link-type="dfn" href="#cbor" id="ref-for-cbor⑨">CBOR</a> <a data-link-type="dfn" href="https://infra.spec.whatwg.org/#ordered-map" id="ref-for-ordered-map①⓪">map</a> from <a data-link-type="dfn" href="#extension-identifier" id="ref-for-extension-identifier⑤">extension identifiers</a> to their <a data-link-type="dfn" href="#authenticator-extension-input" id="ref-for-authenticator-extension-input①">authenticator extension inputs</a>, created by the <a data-link-type="dfn" href="#client" id="ref-for-client⑦⑦">client</a> based on
-the extensions requested by the <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party①⑨④">Relying Party</a>, if any.</p>
+the extensions requested by the <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party①⑨⑨">Relying Party</a>, if any.</p>
    </dl>
    <p class="note" role="note"><span>Note:</span> Before performing this operation, all other operations in progress in the <a data-link-type="dfn" href="#authenticator-session" id="ref-for-authenticator-session②">authenticator session</a> MUST be aborted by
 running the <a data-link-type="dfn" href="#authenticatorcancel" id="ref-for-authenticatorcancel①①">authenticatorCancel</a> operation.</p>
@@ -4501,8 +4559,8 @@ <h4 class="heading settled" data-level="6.3.2" id="sctn-op-make-cred"><span clas
      <p><a data-link-type="dfn" href="https://infra.spec.whatwg.org/#list-iterate" id="ref-for-list-iterate①⑦">For each</a> <var>descriptor</var> of <var>excludeCredentialDescriptorList</var>:</p>
      <ol>
       <li data-md>
-       <p>If <a data-link-type="dfn" href="#credential-id-looking-up" id="ref-for-credential-id-looking-up">looking up</a> <code><var>descriptor</var>.<code class="idl"><a data-link-type="idl" href="#dom-publickeycredentialdescriptor-id" id="ref-for-dom-publickeycredentialdescriptor-id④">id</a></code></code> in this authenticator
-returns non-null, and the returned <a data-link-type="dfn" href="https://infra.spec.whatwg.org/#list-item" id="ref-for-list-item⑧">item</a>'s <a data-link-type="dfn" href="#rp-id" id="ref-for-rp-id③④">RP ID</a> and <a data-link-type="dfn" href="#public-key-credential-source-type" id="ref-for-public-key-credential-source-type">type</a> match <code><var>rpEntity</var>.<code class="idl"><a data-link-type="idl" href="#dom-publickeycredentialrpentity-id" id="ref-for-dom-publickeycredentialrpentity-id①⓪">id</a></code></code> and <code><var>excludeCredentialDescriptorList</var>.<code class="idl"><a data-link-type="idl" href="#dom-publickeycredentialdescriptor-type" id="ref-for-dom-publickeycredentialdescriptor-type③">type</a></code></code> respectively,
+       <p>If <a data-link-type="dfn" href="#credential-id-looking-up" id="ref-for-credential-id-looking-up">looking up</a> <code><var>descriptor</var>.<code class="idl"><a data-link-type="idl" href="#dom-publickeycredentialdescriptor-id" id="ref-for-dom-publickeycredentialdescriptor-id⑤">id</a></code></code> in this authenticator
+returns non-null, and the returned <a data-link-type="dfn" href="https://infra.spec.whatwg.org/#list-item" id="ref-for-list-item⑨">item</a>'s <a data-link-type="dfn" href="#rp-id" id="ref-for-rp-id③④">RP ID</a> and <a data-link-type="dfn" href="#public-key-credential-source-type" id="ref-for-public-key-credential-source-type①">type</a> match <code><var>rpEntity</var>.<code class="idl"><a data-link-type="idl" href="#dom-publickeycredentialrpentity-id" id="ref-for-dom-publickeycredentialrpentity-id①⓪">id</a></code></code> and <code><var>excludeCredentialDescriptorList</var>.<code class="idl"><a data-link-type="idl" href="#dom-publickeycredentialdescriptor-type" id="ref-for-dom-publickeycredentialdescriptor-type④">type</a></code></code> respectively,
 then collect an <a data-link-type="dfn" href="#authorization-gesture" id="ref-for-authorization-gesture①⑦">authorization gesture</a> confirming <a data-link-type="dfn" href="#user-consent" id="ref-for-user-consent①⑥">user
 consent</a> for creating a new credential. The <a data-link-type="dfn" href="#authorization-gesture" id="ref-for-authorization-gesture①⑧">authorization gesture</a> MUST include a <a data-link-type="dfn" href="#test-of-user-presence" id="ref-for-test-of-user-presence⑨">test
 of user presence</a>. If the user</p>
@@ -4515,10 +4573,10 @@ <h4 class="heading settled" data-level="6.3.2" id="sctn-op-make-cred"><span clas
          <p>return an error code equivalent to "<code class="idl"><a data-link-type="idl" href="https://webidl.spec.whatwg.org/#notallowederror" id="ref-for-notallowederror⑨">NotAllowedError</a></code>" and terminate the operation.</p>
        </dl>
        <p class="note" role="note"><span>Note:</span> The purpose of this <a data-link-type="dfn" href="#authorization-gesture" id="ref-for-authorization-gesture①⑨">authorization gesture</a> is not to proceed with creating a credential,
-but for privacy reasons to authorize disclosure of the fact that <code><var>descriptor</var>.<code class="idl"><a data-link-type="idl" href="#dom-publickeycredentialdescriptor-id" id="ref-for-dom-publickeycredentialdescriptor-id⑤">id</a></code></code> is <a data-link-type="dfn" href="#bound-credential" id="ref-for-bound-credential①③">bound</a> to this <a data-link-type="dfn" href="#authenticator" id="ref-for-authenticator①⑦⑨">authenticator</a>.
-If the user consents, the <a data-link-type="dfn" href="#client" id="ref-for-client⑦⑧">client</a> and <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party①⑨⑤">Relying Party</a> can detect this and guide the user to use a different <a data-link-type="dfn" href="#authenticator" id="ref-for-authenticator①⑧⓪">authenticator</a>.
+but for privacy reasons to authorize disclosure of the fact that <code><var>descriptor</var>.<code class="idl"><a data-link-type="idl" href="#dom-publickeycredentialdescriptor-id" id="ref-for-dom-publickeycredentialdescriptor-id⑥">id</a></code></code> is <a data-link-type="dfn" href="#bound-credential" id="ref-for-bound-credential①③">bound</a> to this <a data-link-type="dfn" href="#authenticator" id="ref-for-authenticator①⑦⑨">authenticator</a>.
+If the user consents, the <a data-link-type="dfn" href="#client" id="ref-for-client⑦⑧">client</a> and <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party②⓪⓪">Relying Party</a> can detect this and guide the user to use a different <a data-link-type="dfn" href="#authenticator" id="ref-for-authenticator①⑧⓪">authenticator</a>.
 If the user does not consent,
-the <a data-link-type="dfn" href="#authenticator" id="ref-for-authenticator①⑧①">authenticator</a> does not reveal that <code><var>descriptor</var>.<code class="idl"><a data-link-type="idl" href="#dom-publickeycredentialdescriptor-id" id="ref-for-dom-publickeycredentialdescriptor-id⑥">id</a></code></code> is <a data-link-type="dfn" href="#bound-credential" id="ref-for-bound-credential①④">bound</a> to it,
+the <a data-link-type="dfn" href="#authenticator" id="ref-for-authenticator①⑧①">authenticator</a> does not reveal that <code><var>descriptor</var>.<code class="idl"><a data-link-type="idl" href="#dom-publickeycredentialdescriptor-id" id="ref-for-dom-publickeycredentialdescriptor-id⑦">id</a></code></code> is <a data-link-type="dfn" href="#bound-credential" id="ref-for-bound-credential①④">bound</a> to it,
 and responds as if the user simply declined consent to create a credential.</p>
      </ol>
     <li data-md>
@@ -4539,14 +4597,14 @@ <h4 class="heading settled" data-level="6.3.2" id="sctn-op-make-cred"><span clas
      <p>Once the <a data-link-type="dfn" href="#authorization-gesture" id="ref-for-authorization-gesture②④">authorization gesture</a> has been completed and <a data-link-type="dfn" href="#user-consent" id="ref-for-user-consent①⑨">user consent</a> has been obtained, generate a new credential object:</p>
      <ol>
       <li data-md>
-       <p>Let (<var>publicKey</var>, <var>privateKey</var>) be a new pair of cryptographic keys using the combination of <code class="idl"><a data-link-type="idl" href="#enumdef-publickeycredentialtype" id="ref-for-enumdef-publickeycredentialtype①⓪">PublicKeyCredentialType</a></code> and cryptographic parameters represented by the first <a data-link-type="dfn" href="https://infra.spec.whatwg.org/#list-item" id="ref-for-list-item⑨">item</a> in <var>credTypesAndPubKeyAlgs</var> that is supported by
+       <p>Let (<var>publicKey</var>, <var>privateKey</var>) be a new pair of cryptographic keys using the combination of <code class="idl"><a data-link-type="idl" href="#enumdef-publickeycredentialtype" id="ref-for-enumdef-publickeycredentialtype①⓪">PublicKeyCredentialType</a></code> and cryptographic parameters represented by the first <a data-link-type="dfn" href="https://infra.spec.whatwg.org/#list-item" id="ref-for-list-item①⓪">item</a> in <var>credTypesAndPubKeyAlgs</var> that is supported by
 this authenticator.</p>
       <li data-md>
        <p>Let <var>userHandle</var> be <code><var>userEntity</var>.<code class="idl"><a data-link-type="idl" href="#dom-publickeycredentialuserentity-id" id="ref-for-dom-publickeycredentialuserentity-id⑧">id</a></code></code>.</p>
       <li data-md>
-       <p>Let <var>credentialSource</var> be a new <a data-link-type="dfn" href="#public-key-credential-source" id="ref-for-public-key-credential-source④③">public key credential source</a> with the fields:</p>
+       <p>Let <var>credentialSource</var> be a new <a data-link-type="dfn" href="#public-key-credential-source" id="ref-for-public-key-credential-source⑤③">public key credential source</a> with the fields:</p>
        <dl>
-        <dt data-md><a data-link-type="dfn" href="#public-key-credential-source-type" id="ref-for-public-key-credential-source-type①">type</a>
+        <dt data-md><a data-link-type="dfn" href="#public-key-credential-source-type" id="ref-for-public-key-credential-source-type②">type</a>
         <dd data-md>
          <p><code class="idl"><a data-link-type="idl" href="#dom-publickeycredentialtype-public-key" id="ref-for-dom-publickeycredentialtype-public-key④">public-key</a></code>.</p>
         <dt data-md><a data-link-type="dfn" href="#public-key-credential-source-privatekey" id="ref-for-public-key-credential-source-privatekey">privateKey</a>
@@ -4566,7 +4624,7 @@ <h4 class="heading settled" data-level="6.3.2" id="sctn-op-make-cred"><span clas
        <p>If <var>requireResidentKey</var> is <code>true</code> or the authenticator chooses to create a <a data-link-type="dfn" href="#client-side-discoverable-public-key-credential-source" id="ref-for-client-side-discoverable-public-key-credential-source⑥">client-side discoverable public key credential source</a>:</p>
        <ol>
         <li data-md>
-         <p>Let <var>credentialId</var> be a new <a data-link-type="dfn" href="#credential-id" id="ref-for-credential-id②⑦">credential id</a>.</p>
+         <p>Let <var>credentialId</var> be a new <a data-link-type="dfn" href="#credential-id" id="ref-for-credential-id②⑧">credential id</a>.</p>
         <li data-md>
          <p>Set <var>credentialSource</var>.<a data-link-type="dfn" href="#public-key-credential-source-id" id="ref-for-public-key-credential-source-id②">id</a> to <var>credentialId</var>.</p>
         <li data-md>
@@ -4596,7 +4654,7 @@ <h4 class="heading settled" data-level="6.3.2" id="sctn-op-make-cred"><span clas
        <p>let the <a data-link-type="dfn" href="#signature-counter" id="ref-for-signature-counter①④">signature counter</a> value for the new credential be zero. (U2F devices may support signature counters but do not return a counter when making a credential. See <a data-link-type="biblio" href="#biblio-fido-u2f-message-formats">[FIDO-U2F-Message-Formats]</a>.)</p>
       <dt data-md>supports a global <a data-link-type="dfn" href="#signature-counter" id="ref-for-signature-counter①⑤">signature counter</a>
       <dd data-md>
-       <p>Use the global <a data-link-type="dfn" href="#signature-counter" id="ref-for-signature-counter①⑥">signature counter</a>'s actual value when generating <a data-link-type="dfn" href="#authenticator-data" id="ref-for-authenticator-data③⑤">authenticator data</a>.</p>
+       <p>Use the global <a data-link-type="dfn" href="#signature-counter" id="ref-for-signature-counter①⑥">signature counter</a>'s actual value when generating <a data-link-type="dfn" href="#authenticator-data" id="ref-for-authenticator-data③⑦">authenticator data</a>.</p>
       <dt data-md>supports a per credential <a data-link-type="dfn" href="#signature-counter" id="ref-for-signature-counter①⑦">signature counter</a>
       <dd data-md>
        <p>allocate the counter, associate it with the new credential, and initialize the counter value as zero.</p>
@@ -4624,7 +4682,7 @@ <h4 class="heading settled" data-level="6.3.3" id="sctn-op-get-assertion"><span
      <p>The <a data-link-type="dfn" href="#collectedclientdata-hash-of-the-serialized-client-data" id="ref-for-collectedclientdata-hash-of-the-serialized-client-data①⓪">hash of the serialized client data</a>, provided by the client.</p>
     <dt data-md><var>allowCredentialDescriptorList</var>
     <dd data-md>
-     <p>An OPTIONAL <a data-link-type="dfn" href="https://infra.spec.whatwg.org/#list" id="ref-for-list④">list</a> of <code class="idl"><a data-link-type="idl" href="#dictdef-publickeycredentialdescriptor" id="ref-for-dictdef-publickeycredentialdescriptor①②">PublicKeyCredentialDescriptor</a></code>s describing credentials acceptable to the <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party①⑨⑥">Relying Party</a> (possibly filtered
+     <p>An OPTIONAL <a data-link-type="dfn" href="https://infra.spec.whatwg.org/#list" id="ref-for-list④">list</a> of <code class="idl"><a data-link-type="idl" href="#dictdef-publickeycredentialdescriptor" id="ref-for-dictdef-publickeycredentialdescriptor①③">PublicKeyCredentialDescriptor</a></code>s describing credentials acceptable to the <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party②⓪①">Relying Party</a> (possibly filtered
 by the client), if any.</p>
     <dt data-md><var>requireUserPresence</var>
     <dd data-md>
@@ -4637,7 +4695,7 @@ <h4 class="heading settled" data-level="6.3.3" id="sctn-op-get-assertion"><span
     <dt data-md><var>extensions</var>
     <dd data-md>
      <p>A <a data-link-type="dfn" href="#cbor" id="ref-for-cbor①⓪">CBOR</a> <a data-link-type="dfn" href="https://infra.spec.whatwg.org/#ordered-map" id="ref-for-ordered-map①①">map</a> from <a data-link-type="dfn" href="#extension-identifier" id="ref-for-extension-identifier⑦">extension identifiers</a> to their <a data-link-type="dfn" href="#authenticator-extension-input" id="ref-for-authenticator-extension-input③">authenticator extension inputs</a>, created by the client based on
-the extensions requested by the <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party①⑨⑦">Relying Party</a>, if any.</p>
+the extensions requested by the <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party②⓪②">Relying Party</a>, if any.</p>
    </dl>
    <p class="note" role="note"><span>Note:</span> Before performing this operation, all other operations in progress in the <a data-link-type="dfn" href="#authenticator-session" id="ref-for-authenticator-session③">authenticator session</a> MUST be aborted by running the <a data-link-type="dfn" href="#authenticatorcancel" id="ref-for-authenticatorcancel①②">authenticatorCancel</a> operation.</p>
    <p>When this method is invoked, the <a data-link-type="dfn" href="#authenticator" id="ref-for-authenticator①⑧③">authenticator</a> MUST perform the following procedure:</p>
@@ -4646,12 +4704,12 @@ <h4 class="heading settled" data-level="6.3.3" id="sctn-op-get-assertion"><span
      <p>Check if all the supplied parameters are syntactically well-formed and of the correct length. If not, return an error code
 equivalent to "<code class="idl"><a data-link-type="idl" href="https://webidl.spec.whatwg.org/#unknownerror" id="ref-for-unknownerror②">UnknownError</a></code>" and terminate the operation.</p>
     <li data-md>
-     <p>Let <var>credentialOptions</var> be a new empty <a data-link-type="dfn" href="https://infra.spec.whatwg.org/#ordered-set" id="ref-for-ordered-set⑥">set</a> of <a data-link-type="dfn" href="#public-key-credential-source" id="ref-for-public-key-credential-source④④">public key credential sources</a>.</p>
+     <p>Let <var>credentialOptions</var> be a new empty <a data-link-type="dfn" href="https://infra.spec.whatwg.org/#ordered-set" id="ref-for-ordered-set⑥">set</a> of <a data-link-type="dfn" href="#public-key-credential-source" id="ref-for-public-key-credential-source⑤④">public key credential sources</a>.</p>
     <li data-md>
      <p>If <var>allowCredentialDescriptorList</var> was supplied, then <a data-link-type="dfn" href="https://infra.spec.whatwg.org/#list-iterate" id="ref-for-list-iterate①⑧">for each</a> <var>descriptor</var> of <var>allowCredentialDescriptorList</var>:</p>
      <ol>
       <li data-md>
-       <p>Let <var>credSource</var> be the result of <a data-link-type="dfn" href="#credential-id-looking-up" id="ref-for-credential-id-looking-up①">looking up</a> <code><var>descriptor</var>.<code class="idl"><a data-link-type="idl" href="#dom-publickeycredentialdescriptor-id" id="ref-for-dom-publickeycredentialdescriptor-id⑦">id</a></code></code> in this
+       <p>Let <var>credSource</var> be the result of <a data-link-type="dfn" href="#credential-id-looking-up" id="ref-for-credential-id-looking-up①">looking up</a> <code><var>descriptor</var>.<code class="idl"><a data-link-type="idl" href="#dom-publickeycredentialdescriptor-id" id="ref-for-dom-publickeycredentialdescriptor-id⑧">id</a></code></code> in this
 authenticator.</p>
       <li data-md>
        <p>If <var>credSource</var> is not <code>null</code>, <a data-link-type="dfn" href="https://infra.spec.whatwg.org/#set-append" id="ref-for-set-append④">append</a> it to <var>credentialOptions</var>.</p>
@@ -4664,7 +4722,7 @@ <h4 class="heading settled" data-level="6.3.3" id="sctn-op-get-assertion"><span
     <li data-md>
      <p>If <var>credentialOptions</var> is now empty, return an error code equivalent to "<code class="idl"><a data-link-type="idl" href="https://webidl.spec.whatwg.org/#notallowederror" id="ref-for-notallowederror①①">NotAllowedError</a></code>" and terminate the operation.</p>
     <li data-md>
-     <p>Prompt the user to select a <a data-link-type="dfn" href="#public-key-credential-source" id="ref-for-public-key-credential-source④⑤">public key credential source</a> <var>selectedCredential</var> from <var>credentialOptions</var>.
+     <p>Prompt the user to select a <a data-link-type="dfn" href="#public-key-credential-source" id="ref-for-public-key-credential-source⑤⑤">public key credential source</a> <var>selectedCredential</var> from <var>credentialOptions</var>.
 Collect an <a data-link-type="dfn" href="#authorization-gesture" id="ref-for-authorization-gesture②⑤">authorization gesture</a> confirming <a data-link-type="dfn" href="#user-consent" id="ref-for-user-consent②⓪">user consent</a> for using <var>selectedCredential</var>.
 The prompt for the <a data-link-type="dfn" href="#authorization-gesture" id="ref-for-authorization-gesture②⑥">authorization gesture</a> may be shown
 by the <a data-link-type="dfn" href="#authenticator" id="ref-for-authenticator①⑧④">authenticator</a> if it has its own output capability, or by the user agent otherwise.</p>
@@ -4686,7 +4744,7 @@ <h4 class="heading settled" data-level="6.3.3" id="sctn-op-get-assertion"><span
     <li data-md>
      <p>Let <var>signature</var> be the <a data-link-type="dfn" href="#assertion-signature" id="ref-for-assertion-signature⑧">assertion signature</a> of the concatenation <code><var>authenticatorData</var> || <var>hash</var></code> using the <a data-link-type="dfn" href="#public-key-credential-source-privatekey" id="ref-for-public-key-credential-source-privatekey①">privateKey</a> of <var>selectedCredential</var> as shown in <a href="#fig-signature">Figure <span class="figure-num-following"></span></a>, below. A simple,
 undelimited
-concatenation is safe to use here because the <a data-link-type="dfn" href="#authenticator-data" id="ref-for-authenticator-data③⑥">authenticator data</a> describes its own length. The <a data-link-type="dfn" href="#collectedclientdata-hash-of-the-serialized-client-data" id="ref-for-collectedclientdata-hash-of-the-serialized-client-data①①">hash of the serialized
+concatenation is safe to use here because the <a data-link-type="dfn" href="#authenticator-data" id="ref-for-authenticator-data③⑧">authenticator data</a> describes its own length. The <a data-link-type="dfn" href="#collectedclientdata-hash-of-the-serialized-client-data" id="ref-for-collectedclientdata-hash-of-the-serialized-client-data①①">hash of the serialized
 client data</a> (which potentially has a variable length) is always the last element.</p>
      <figure id="fig-signature">
        <img src="images/fido-signature-formats-figure2.svg"> 
@@ -4702,7 +4760,7 @@ <h4 class="heading settled" data-level="6.3.3" id="sctn-op-get-assertion"><span
        <p><var>selectedCredential</var>.<a data-link-type="dfn" href="#public-key-credential-source-id" id="ref-for-public-key-credential-source-id③">id</a>, if either a list of credentials
 (i.e., <var>allowCredentialDescriptorList</var>) of length 2 or greater was
 supplied by the client, or no such list was supplied.</p>
-       <p class="note" role="note"><span>Note:</span> If, within <var>allowCredentialDescriptorList</var>, the client supplied exactly one credential and it was successfully employed, then its <a data-link-type="dfn" href="#credential-id" id="ref-for-credential-id②⑧">credential ID</a> is not returned since the client already knows it. This saves transmitting these bytes over
+       <p class="note" role="note"><span>Note:</span> If, within <var>allowCredentialDescriptorList</var>, the client supplied exactly one credential and it was successfully employed, then its <a data-link-type="dfn" href="#credential-id" id="ref-for-credential-id②⑨">credential ID</a> is not returned since the client already knows it. This saves transmitting these bytes over
         what may be a constrained connection in what is likely a common case.</p>
       <li data-md>
        <p><var>authenticatorData</var></p>
@@ -4713,7 +4771,7 @@ <h4 class="heading settled" data-level="6.3.3" id="sctn-op-get-assertion"><span
        <p class="note" role="note"><span>Note:</span> the returned <a data-link-type="dfn" href="#public-key-credential-source-userhandle" id="ref-for-public-key-credential-source-userhandle③">userHandle</a> value may be <code>null</code>, see: <a data-link-type="dfn" href="#assertioncreationdata-userhandleresult" id="ref-for-assertioncreationdata-userhandleresult④">userHandleResult</a>.</p>
      </ul>
    </ol>
-   <p>If the <a data-link-type="dfn" href="#authenticator" id="ref-for-authenticator①⑧⑦">authenticator</a> cannot find any <a data-link-type="dfn" href="#public-key-credential" id="ref-for-public-key-credential④⑧">credential</a> corresponding to the specified <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party①⑨⑧">Relying Party</a> that
+   <p>If the <a data-link-type="dfn" href="#authenticator" id="ref-for-authenticator①⑧⑦">authenticator</a> cannot find any <a data-link-type="dfn" href="#public-key-credential" id="ref-for-public-key-credential④⑧">credential</a> corresponding to the specified <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party②⓪③">Relying Party</a> that
 matches the specified criteria, it terminates the operation and returns an error.</p>
    <h4 class="heading settled" data-level="6.3.4" id="sctn-op-cancel"><span class="secno">6.3.4. </span><span class="content">The <dfn class="dfn-paneled" data-dfn-type="dfn" data-noexport id="authenticatorcancel">authenticatorCancel</dfn> Operation</span><a class="self-link" href="#sctn-op-cancel"></a></h4>
    <p>This operation takes no input parameters and returns no result.</p>
@@ -4732,14 +4790,14 @@ <h4 class="heading settled" data-level="6.3.5" id="sctn-op-silent-discovery"><sp
    <p>When this operation is invoked, the <a data-link-type="dfn" href="#authenticator" id="ref-for-authenticator①⑧⑧">authenticator</a> MUST perform the following procedure:</p>
    <ol>
     <li data-md>
-     <p>Let <var>collectedDiscoverableCredentialMetadata</var> be a new <a data-link-type="dfn" href="https://infra.spec.whatwg.org/#list" id="ref-for-list⑤">list</a> whose <a data-link-type="dfn" href="https://infra.spec.whatwg.org/#list-item" id="ref-for-list-item①⓪">items</a> are <dfn class="dfn-paneled" data-dfn-type="dfn" data-noexport id="discoverablecredentialmetadata">DiscoverableCredentialMetadata</dfn> <a data-link-type="dfn" href="https://infra.spec.whatwg.org/#struct" id="ref-for-struct③">structs</a> with the following <a data-link-type="dfn" href="https://infra.spec.whatwg.org/#struct-item" id="ref-for-struct-item④">items</a>:</p>
+     <p>Let <var>collectedDiscoverableCredentialMetadata</var> be a new <a data-link-type="dfn" href="https://infra.spec.whatwg.org/#list" id="ref-for-list⑤">list</a> whose <a data-link-type="dfn" href="https://infra.spec.whatwg.org/#list-item" id="ref-for-list-item①①">items</a> are <dfn class="dfn-paneled" data-dfn-type="dfn" data-noexport id="discoverablecredentialmetadata">DiscoverableCredentialMetadata</dfn> <a data-link-type="dfn" href="https://infra.spec.whatwg.org/#struct" id="ref-for-struct④">structs</a> with the following <a data-link-type="dfn" href="https://infra.spec.whatwg.org/#struct-item" id="ref-for-struct-item①⓪">items</a>:</p>
      <dl>
       <dt data-md><dfn class="dfn-paneled" data-dfn-for="DiscoverableCredentialMetadata" data-dfn-type="dfn" data-noexport id="discoverablecredentialmetadata-type">type</dfn>
       <dd data-md>
        <p>A <code class="idl"><a data-link-type="idl" href="#enumdef-publickeycredentialtype" id="ref-for-enumdef-publickeycredentialtype①①">PublicKeyCredentialType</a></code>.</p>
       <dt data-md><dfn class="dfn-paneled" data-dfn-for="DiscoverableCredentialMetadata" data-dfn-type="dfn" data-noexport id="discoverablecredentialmetadata-id">id</dfn>
       <dd data-md>
-       <p>A <a data-link-type="dfn" href="#credential-id" id="ref-for-credential-id②⑨">Credential ID</a>.</p>
+       <p>A <a data-link-type="dfn" href="#credential-id" id="ref-for-credential-id③⓪">Credential ID</a>.</p>
       <dt data-md>rpId
       <dd data-md>
        <p>A <a data-link-type="dfn" href="#relying-party-identifier" id="ref-for-relying-party-identifier④">Relying Party Identifier</a>.</p>
@@ -4751,14 +4809,14 @@ <h4 class="heading settled" data-level="6.3.5" id="sctn-op-silent-discovery"><sp
        <p>Other information used by the <a data-link-type="dfn" href="#authenticator" id="ref-for-authenticator①⑧⑨">authenticator</a> to inform its UI.</p>
      </dl>
     <li data-md>
-     <p><a data-link-type="dfn" href="https://infra.spec.whatwg.org/#map-iterate" id="ref-for-map-iterate⑥">For each</a> <a data-link-type="dfn" href="#public-key-credential-source" id="ref-for-public-key-credential-source④⑥">public key credential source</a> <var>credSource</var> of <var>authenticator</var>’s <a data-link-type="dfn" href="#authenticator-credentials-map" id="ref-for-authenticator-credentials-map④">credentials map</a>:</p>
+     <p><a data-link-type="dfn" href="https://infra.spec.whatwg.org/#map-iterate" id="ref-for-map-iterate⑥">For each</a> <a data-link-type="dfn" href="#public-key-credential-source" id="ref-for-public-key-credential-source⑤⑥">public key credential source</a> <var>credSource</var> of <var>authenticator</var>’s <a data-link-type="dfn" href="#authenticator-credentials-map" id="ref-for-authenticator-credentials-map④">credentials map</a>:</p>
      <ol>
       <li data-md>
        <p>If <var>credSource</var> is not a <a data-link-type="dfn" href="#client-side-discoverable-credential" id="ref-for-client-side-discoverable-credential①④">client-side discoverable credential</a>, <a data-link-type="dfn" href="https://infra.spec.whatwg.org/#iteration-continue" id="ref-for-iteration-continue①⑤">continue</a>.</p>
       <li data-md>
        <p>If <var>credSource</var>.<a data-link-type="dfn" href="#public-key-credential-source-rpid" id="ref-for-public-key-credential-source-rpid④">rpId</a> is not <var>rpId</var>, <a data-link-type="dfn" href="https://infra.spec.whatwg.org/#iteration-continue" id="ref-for-iteration-continue①⑥">continue</a>.</p>
       <li data-md>
-       <p>Let <var>discoveredCredentialMetadata</var> be a new <a data-link-type="dfn" href="#discoverablecredentialmetadata" id="ref-for-discoverablecredentialmetadata②">DiscoverableCredentialMetadata</a> <a data-link-type="dfn" href="https://infra.spec.whatwg.org/#struct" id="ref-for-struct④">struct</a> whose <a data-link-type="dfn" href="https://infra.spec.whatwg.org/#struct-item" id="ref-for-struct-item⑤">items</a> are copies of <var>credSource</var>’s <a data-link-type="dfn" href="#public-key-credential-source-type" id="ref-for-public-key-credential-source-type②">type</a>, <a data-link-type="dfn" href="#public-key-credential-source-id" id="ref-for-public-key-credential-source-id④">id</a>, <a data-link-type="dfn" href="#public-key-credential-source-rpid" id="ref-for-public-key-credential-source-rpid⑤">rpId</a>, <a data-link-type="dfn" href="#public-key-credential-source-userhandle" id="ref-for-public-key-credential-source-userhandle④">userHandle</a> and <a data-link-type="dfn" href="#public-key-credential-source-otherui" id="ref-for-public-key-credential-source-otherui③">otherUI</a>.</p>
+       <p>Let <var>discoveredCredentialMetadata</var> be a new <a data-link-type="dfn" href="#discoverablecredentialmetadata" id="ref-for-discoverablecredentialmetadata②">DiscoverableCredentialMetadata</a> <a data-link-type="dfn" href="https://infra.spec.whatwg.org/#struct" id="ref-for-struct⑤">struct</a> whose <a data-link-type="dfn" href="https://infra.spec.whatwg.org/#struct-item" id="ref-for-struct-item①①">items</a> are copies of <var>credSource</var>’s <a data-link-type="dfn" href="#public-key-credential-source-type" id="ref-for-public-key-credential-source-type③">type</a>, <a data-link-type="dfn" href="#public-key-credential-source-id" id="ref-for-public-key-credential-source-id④">id</a>, <a data-link-type="dfn" href="#public-key-credential-source-rpid" id="ref-for-public-key-credential-source-rpid⑤">rpId</a>, <a data-link-type="dfn" href="#public-key-credential-source-userhandle" id="ref-for-public-key-credential-source-userhandle④">userHandle</a> and <a data-link-type="dfn" href="#public-key-credential-source-otherui" id="ref-for-public-key-credential-source-otherui③">otherUI</a>.</p>
       <li data-md>
        <p><a data-link-type="dfn" href="https://infra.spec.whatwg.org/#list-append" id="ref-for-list-append③">Append</a> <var>discoveredCredentialMetadata</var> to <var>collectedDiscoverableCredentialMetadata</var>.</p>
      </ol>
@@ -4766,7 +4824,7 @@ <h4 class="heading settled" data-level="6.3.5" id="sctn-op-silent-discovery"><sp
      <p>Return <var>collectedDiscoverableCredentialMetadata</var>.</p>
    </ol>
    <h3 class="heading settled" data-level="6.4" id="sctn-strings"><span class="secno">6.4. </span><span class="content">String Handling</span><a class="self-link" href="#sctn-strings"></a></h3>
-   <p>Authenticators may be required to store arbitrary strings chosen by a <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party①⑨⑨">Relying Party</a>, for example the <code class="idl"><a data-link-type="idl" href="#dom-publickeycredentialentity-name" id="ref-for-dom-publickeycredentialentity-name①④">name</a></code> and <code class="idl"><a data-link-type="idl" href="#dom-publickeycredentialuserentity-displayname" id="ref-for-dom-publickeycredentialuserentity-displayname①③">displayName</a></code> in a <code class="idl"><a data-link-type="idl" href="#dictdef-publickeycredentialuserentity" id="ref-for-dictdef-publickeycredentialuserentity⑥">PublicKeyCredentialUserEntity</a></code>. This section discusses some practical consequences of handling arbitrary strings that may be presented to humans.</p>
+   <p>Authenticators may be required to store arbitrary strings chosen by a <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party②⓪④">Relying Party</a>, for example the <code class="idl"><a data-link-type="idl" href="#dom-publickeycredentialentity-name" id="ref-for-dom-publickeycredentialentity-name①④">name</a></code> and <code class="idl"><a data-link-type="idl" href="#dom-publickeycredentialuserentity-displayname" id="ref-for-dom-publickeycredentialuserentity-displayname①③">displayName</a></code> in a <code class="idl"><a data-link-type="idl" href="#dictdef-publickeycredentialuserentity" id="ref-for-dictdef-publickeycredentialuserentity⑥">PublicKeyCredentialUserEntity</a></code>. This section discusses some practical consequences of handling arbitrary strings that may be presented to humans.</p>
    <h4 class="heading settled" data-level="6.4.1" id="sctn-strings-truncation"><span class="secno">6.4.1. </span><span class="content">String Truncation</span><a class="self-link" href="#sctn-strings-truncation"></a></h4>
    <p>Each arbitrary string in the API will have some accommodation for the potentially limited resources available to an <a data-link-type="dfn" href="#authenticator" id="ref-for-authenticator①⑨⓪">authenticator</a>. If string value truncation is the chosen accommodation then authenticators MAY truncate in order to make the string fit within a length equal or greater than the specified minimum supported length. Such truncation SHOULD also respect UTF-8 sequence boundaries or <a data-link-type="dfn" href="https://unicode.org/reports/tr29/#Grapheme_Cluster_Boundaries" id="ref-for-Grapheme_Cluster_Boundaries">grapheme cluster</a> boundaries <a data-link-type="biblio" href="#biblio-utr29">[UTR29]</a>. This defines the maximum truncation permitted and authenticators MUST NOT truncate further.</p>
    <p>For example, in <a href="#fig-stringTruncation">figure <span class="figure-num-following"></span></a> the string is 65 bytes long. If truncating to 64 bytes then the final 0x88 byte must be removed purely because of space reasons. Since that leaves a partial UTF-8 sequence the remainder of that sequence may also be removed. Since that leaves a partial <a data-link-type="dfn" href="https://unicode.org/reports/tr29/#Grapheme_Cluster_Boundaries" id="ref-for-Grapheme_Cluster_Boundaries①">grapheme cluster</a> an authenticator may remove the remainder of that cluster.</p>
@@ -4774,7 +4832,7 @@ <h4 class="heading settled" data-level="6.4.1" id="sctn-strings-truncation"><spa
      <img src="images/string-truncation.svg"> 
     <figcaption>The end of a UTF-8 encoded string showing the positions of different truncation boundaries.</figcaption>
    </figure>
-   <p><a data-link-type="dfn" href="#conforming-user-agent" id="ref-for-conforming-user-agent④">Conforming User Agents</a> are responsible for ensuring that the authenticator behavior observed by <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party②⓪⓪">Relying Parties</a> conforms to this specification with respect to string handling. For example, if an authenticator is known to behave incorrectly when asked to store large strings, the user agent SHOULD perform the truncation for it in order to maintain the model from the point of view of the <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party②⓪①">Relying Party</a>. User-agents that do this SHOULD truncate at <a data-link-type="dfn" href="https://unicode.org/reports/tr29/#Grapheme_Cluster_Boundaries" id="ref-for-Grapheme_Cluster_Boundaries②">grapheme cluster</a> boundaries.</p>
+   <p><a data-link-type="dfn" href="#conforming-user-agent" id="ref-for-conforming-user-agent④">Conforming User Agents</a> are responsible for ensuring that the authenticator behavior observed by <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party②⓪⑤">Relying Parties</a> conforms to this specification with respect to string handling. For example, if an authenticator is known to behave incorrectly when asked to store large strings, the user agent SHOULD perform the truncation for it in order to maintain the model from the point of view of the <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party②⓪⑥">Relying Party</a>. User-agents that do this SHOULD truncate at <a data-link-type="dfn" href="https://unicode.org/reports/tr29/#Grapheme_Cluster_Boundaries" id="ref-for-Grapheme_Cluster_Boundaries②">grapheme cluster</a> boundaries.</p>
    <p>Truncation based on UTF-8 sequences alone may cause a <a data-link-type="dfn" href="https://unicode.org/reports/tr29/#Grapheme_Cluster_Boundaries" id="ref-for-Grapheme_Cluster_Boundaries③">grapheme cluster</a> to be truncated. This could make the grapheme cluster render as a different glyph, potentially changing the meaning of the string, instead of removing the glyph entirely.</p>
    <p>In addition to that, truncating on byte boundaries alone causes a known issue that user agents should be aware of: if the authenticator is using <a data-link-type="biblio" href="#biblio-fido-ctap">[FIDO-CTAP]</a> then future messages from the authenticator may contain invalid CBOR since the value is typed as a CBOR string and thus is required to be valid UTF-8. User agents are tasked with handling this to avoid burdening authenticators with understanding character encodings and Unicode character properties. Thus, when dealing with <a data-link-type="dfn" href="#authenticator" id="ref-for-authenticator①⑨①">authenticators</a>, user agents SHOULD:</p>
    <ol>
@@ -4799,35 +4857,35 @@ <h4 class="heading settled" data-level="6.4.2" id="sctn-strings-langdir"><span c
    <h3 class="heading settled" data-level="6.5" id="sctn-attestation"><span class="secno">6.5. </span><span class="content">Attestation</span><a class="self-link" href="#sctn-attestation"></a></h3>
    <p><a data-link-type="dfn" href="#authenticator" id="ref-for-authenticator①⑨③">Authenticators</a> SHOULD also provide some form of <a data-link-type="dfn" href="#attestation" id="ref-for-attestation①①">attestation</a>, if possible.
 If an authenticator does, the basic requirement is that the <a data-link-type="dfn" href="#authenticator" id="ref-for-authenticator①⑨④">authenticator</a> can
-produce, for each <a data-link-type="dfn" href="#credential-public-key" id="ref-for-credential-public-key②③">credential public key</a>, an <a data-link-type="dfn" href="#attestation-statement" id="ref-for-attestation-statement①⑦">attestation statement</a> verifiable by the <a data-link-type="dfn" href="#webauthn-relying-party" id="ref-for-webauthn-relying-party②⑦">WebAuthn Relying Party</a>. Typically, this <a data-link-type="dfn" href="#attestation-statement" id="ref-for-attestation-statement①⑧">attestation statement</a> contains a signature by an <a data-link-type="dfn" href="#attestation-private-key" id="ref-for-attestation-private-key①">attestation private key</a> over the attested <a data-link-type="dfn" href="#credential-public-key" id="ref-for-credential-public-key②④">credential public key</a> and
+produce, for each <a data-link-type="dfn" href="#credential-public-key" id="ref-for-credential-public-key②④">credential public key</a>, an <a data-link-type="dfn" href="#attestation-statement" id="ref-for-attestation-statement①⑧">attestation statement</a> verifiable by the <a data-link-type="dfn" href="#webauthn-relying-party" id="ref-for-webauthn-relying-party②⑦">WebAuthn Relying Party</a>. Typically, this <a data-link-type="dfn" href="#attestation-statement" id="ref-for-attestation-statement①⑨">attestation statement</a> contains a signature by an <a data-link-type="dfn" href="#attestation-private-key" id="ref-for-attestation-private-key①">attestation private key</a> over the attested <a data-link-type="dfn" href="#credential-public-key" id="ref-for-credential-public-key②⑤">credential public key</a> and
 a challenge, as well as a certificate or similar data providing provenance information for the <a data-link-type="dfn" href="#attestation-public-key" id="ref-for-attestation-public-key">attestation public key</a>,
-enabling the <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party②⓪②">Relying Party</a> to make a trust decision. However, if an <a data-link-type="dfn" href="#attestation-key-pair" id="ref-for-attestation-key-pair②">attestation key pair</a> is not available, then the authenticator
-MAY either perform <a data-link-type="dfn" href="#self-attestation" id="ref-for-self-attestation⑦">self attestation</a> of the <a data-link-type="dfn" href="#credential-public-key" id="ref-for-credential-public-key②⑤">credential public key</a> with the corresponding <a data-link-type="dfn" href="#credential-private-key" id="ref-for-credential-private-key①⑦">credential private key</a>,
+enabling the <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party②⓪⑦">Relying Party</a> to make a trust decision. However, if an <a data-link-type="dfn" href="#attestation-key-pair" id="ref-for-attestation-key-pair②">attestation key pair</a> is not available, then the authenticator
+MAY either perform <a data-link-type="dfn" href="#self-attestation" id="ref-for-self-attestation⑦">self attestation</a> of the <a data-link-type="dfn" href="#credential-public-key" id="ref-for-credential-public-key②⑥">credential public key</a> with the corresponding <a data-link-type="dfn" href="#credential-private-key" id="ref-for-credential-private-key①⑦">credential private key</a>,
 or otherwise perform <a data-link-type="dfn" href="#none" id="ref-for-none①">no attestation</a>. All this
-information is returned by <a data-link-type="dfn" href="#authenticator" id="ref-for-authenticator①⑨⑤">authenticators</a> any time a new <a data-link-type="dfn" href="#public-key-credential" id="ref-for-public-key-credential④⑨">public key credential</a> is generated, in the overall form of an <dfn class="dfn-paneled" data-dfn-type="dfn" data-noexport id="attestation-object">attestation object</dfn>. The relationship of the <a data-link-type="dfn" href="#attestation-object" id="ref-for-attestation-object①⓪">attestation object</a> with <a data-link-type="dfn" href="#authenticator-data" id="ref-for-authenticator-data③⑦">authenticator data</a> (containing <a data-link-type="dfn" href="#attested-credential-data" id="ref-for-attested-credential-data⑨">attested credential data</a>) and the <a data-link-type="dfn" href="#attestation-statement" id="ref-for-attestation-statement①⑨">attestation statement</a> is illustrated in <a href="#fig-attStructs">figure <span class="figure-num-following"></span></a>, below.</p>
+information is returned by <a data-link-type="dfn" href="#authenticator" id="ref-for-authenticator①⑨⑤">authenticators</a> any time a new <a data-link-type="dfn" href="#public-key-credential" id="ref-for-public-key-credential④⑨">public key credential</a> is generated, in the overall form of an <dfn class="dfn-paneled" data-dfn-type="dfn" data-noexport id="attestation-object">attestation object</dfn>. The relationship of the <a data-link-type="dfn" href="#attestation-object" id="ref-for-attestation-object①⓪">attestation object</a> with <a data-link-type="dfn" href="#authenticator-data" id="ref-for-authenticator-data③⑨">authenticator data</a> (containing <a data-link-type="dfn" href="#attested-credential-data" id="ref-for-attested-credential-data⑨">attested credential data</a>) and the <a data-link-type="dfn" href="#attestation-statement" id="ref-for-attestation-statement②⓪">attestation statement</a> is illustrated in <a href="#fig-attStructs">figure <span class="figure-num-following"></span></a>, below.</p>
    <p>If an <a data-link-type="dfn" href="#authenticator" id="ref-for-authenticator①⑨⑥">authenticator</a> employs <a data-link-type="dfn" href="#self-attestation" id="ref-for-self-attestation⑧">self attestation</a> or <a data-link-type="dfn" href="#none" id="ref-for-none②">no attestation</a>, then no provenance information is provided
-for the <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party②⓪③">Relying Party</a> to base a trust decision on.
-In these cases, the <a data-link-type="dfn" href="#authenticator" id="ref-for-authenticator①⑨⑦">authenticator</a> provides no guarantees about its operation to the <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party②⓪④">Relying Party</a>.</p>
+for the <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party②⓪⑧">Relying Party</a> to base a trust decision on.
+In these cases, the <a data-link-type="dfn" href="#authenticator" id="ref-for-authenticator①⑨⑦">authenticator</a> provides no guarantees about its operation to the <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party②⓪⑨">Relying Party</a>.</p>
    <figure id="fig-attStructs">
      <img src="images/fido-attestation-structures.svg"> 
-    <figcaption><a data-link-type="dfn" href="#attestation-object" id="ref-for-attestation-object①①">Attestation object</a> layout illustrating the included <a data-link-type="dfn" href="#authenticator-data" id="ref-for-authenticator-data③⑧">authenticator data</a> (containing <a data-link-type="dfn" href="#attested-credential-data" id="ref-for-attested-credential-data①⓪">attested credential
-    data</a>) and the <a data-link-type="dfn" href="#attestation-statement" id="ref-for-attestation-statement②⓪">attestation statement</a>.</figcaption>
+    <figcaption><a data-link-type="dfn" href="#attestation-object" id="ref-for-attestation-object①①">Attestation object</a> layout illustrating the included <a data-link-type="dfn" href="#authenticator-data" id="ref-for-authenticator-data④⓪">authenticator data</a> (containing <a data-link-type="dfn" href="#attested-credential-data" id="ref-for-attested-credential-data①⓪">attested credential
+    data</a>) and the <a data-link-type="dfn" href="#attestation-statement" id="ref-for-attestation-statement②①">attestation statement</a>.</figcaption>
    </figure>
    <div class="note" role="note"> This figure illustrates only the <code>packed</code> <a data-link-type="dfn" href="#attestation-statement-format" id="ref-for-attestation-statement-format②">attestation statement format</a>. Several additional <a data-link-type="dfn" href="#attestation-statement-format" id="ref-for-attestation-statement-format③">attestation statement
   formats</a> are defined in <a href="#sctn-defined-attestation-formats">§ 8 Defined Attestation Statement Formats</a>. </div>
    <p>An important component of the <a data-link-type="dfn" href="#attestation-object" id="ref-for-attestation-object①②">attestation object</a> is the <dfn class="dfn-paneled" data-dfn-type="dfn" data-noexport id="attestation-statement">attestation statement</dfn>. This is a specific type of signed
 data object, containing statements about a <a data-link-type="dfn" href="#public-key-credential" id="ref-for-public-key-credential⑤⓪">public key credential</a> itself and the <a data-link-type="dfn" href="#authenticator" id="ref-for-authenticator①⑨⑧">authenticator</a> that created it. It
-contains an <a data-link-type="dfn" href="#attestation-signature" id="ref-for-attestation-signature⑥">attestation signature</a> created using the key of the attesting authority (except for the case of <a data-link-type="dfn" href="#self-attestation" id="ref-for-self-attestation⑨">self
-attestation</a>, when it is created using the <a data-link-type="dfn" href="#credential-private-key" id="ref-for-credential-private-key①⑧">credential private key</a>). In order to correctly interpret an <a data-link-type="dfn" href="#attestation-statement" id="ref-for-attestation-statement②①">attestation
-statement</a>, a <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party②⓪⑤">Relying Party</a> needs to understand these two aspects of <a data-link-type="dfn" href="#attestation" id="ref-for-attestation①②">attestation</a>:</p>
+contains an <a data-link-type="dfn" href="#attestation-signature" id="ref-for-attestation-signature⑦">attestation signature</a> created using the key of the attesting authority (except for the case of <a data-link-type="dfn" href="#self-attestation" id="ref-for-self-attestation⑨">self
+attestation</a>, when it is created using the <a data-link-type="dfn" href="#credential-private-key" id="ref-for-credential-private-key①⑧">credential private key</a>). In order to correctly interpret an <a data-link-type="dfn" href="#attestation-statement" id="ref-for-attestation-statement②②">attestation
+statement</a>, a <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party②①⓪">Relying Party</a> needs to understand these two aspects of <a data-link-type="dfn" href="#attestation" id="ref-for-attestation①②">attestation</a>:</p>
    <ol>
     <li data-md>
      <p>The <dfn class="dfn-paneled" data-dfn-type="dfn" data-noexport id="attestation-statement-format">attestation statement format</dfn> is the manner in which the signature is represented and the various contextual
 bindings are incorporated into the attestation statement by the <a data-link-type="dfn" href="#authenticator" id="ref-for-authenticator①⑨⑨">authenticator</a>. In other words, this defines the
 syntax of the statement. Various existing components and OS platforms (such as TPMs and the Android OS) have previously defined <a data-link-type="dfn" href="#attestation-statement-format" id="ref-for-attestation-statement-format④">attestation statement formats</a>. This specification supports a variety of such formats in an extensible way, as defined in <a href="#sctn-attestation-formats">§ 6.5.2 Attestation Statement Formats</a>. The formats themselves are identified by strings, as described in <a href="#sctn-attstn-fmt-ids">§ 8.1 Attestation Statement Format Identifiers</a>.</p>
     <li data-md>
-     <p>The <dfn class="dfn-paneled" data-dfn-type="dfn" data-noexport id="attestation-type">attestation type</dfn> defines the semantics of <a data-link-type="dfn" href="#attestation-statement" id="ref-for-attestation-statement②②">attestation statements</a> and their underlying trust models.
-Specifically, it defines how a <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party②⓪⑥">Relying Party</a> establishes trust in a particular <a data-link-type="dfn" href="#attestation-statement" id="ref-for-attestation-statement②③">attestation statement</a>, after verifying that it
+     <p>The <dfn class="dfn-paneled" data-dfn-type="dfn" data-noexport id="attestation-type">attestation type</dfn> defines the semantics of <a data-link-type="dfn" href="#attestation-statement" id="ref-for-attestation-statement②③">attestation statements</a> and their underlying trust models.
+Specifically, it defines how a <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party②①①">Relying Party</a> establishes trust in a particular <a data-link-type="dfn" href="#attestation-statement" id="ref-for-attestation-statement②④">attestation statement</a>, after verifying that it
 is cryptographically valid. This specification supports a number of <a data-link-type="dfn" href="#attestation-type" id="ref-for-attestation-type">attestation types</a>, as described in <a href="#sctn-attestation-types">§ 6.5.3 Attestation Types</a>.</p>
    </ol>
    <p>In general, there is no simple mapping between <a data-link-type="dfn" href="#attestation-statement-format" id="ref-for-attestation-statement-format⑤">attestation statement formats</a> and <a data-link-type="dfn" href="#attestation-type" id="ref-for-attestation-type①">attestation types</a>. For example, the
@@ -4839,17 +4897,17 @@ <h3 class="heading settled" data-level="6.5" id="sctn-attestation"><span class="
      <p>The <a data-link-type="dfn" href="#attestation-type" id="ref-for-attestation-type③">attestation type</a>, which determines the trust model,</p>
     <li data-md>
      <p>The <a data-link-type="dfn" href="#attestation-statement-format" id="ref-for-attestation-statement-format⑦">attestation statement format</a>, which MAY constrain the strength of the <a data-link-type="dfn" href="#attestation" id="ref-for-attestation①④">attestation</a> by limiting what can be
-expressed in an <a data-link-type="dfn" href="#attestation-statement" id="ref-for-attestation-statement②④">attestation statement</a>, and</p>
+expressed in an <a data-link-type="dfn" href="#attestation-statement" id="ref-for-attestation-statement②⑤">attestation statement</a>, and</p>
     <li data-md>
      <p>The characteristics of the individual <a data-link-type="dfn" href="#authenticator" id="ref-for-authenticator②⓪⓪">authenticator</a>, such as its construction, whether part or all of it runs in a secure
 operating environment, and so on.</p>
    </ul>
-   <p>The <a data-link-type="dfn" href="#attestation-type" id="ref-for-attestation-type④">attestation type</a> and <a data-link-type="dfn" href="#attestation-statement-format" id="ref-for-attestation-statement-format⑧">attestation statement format</a> is chosen by the <a data-link-type="dfn" href="#authenticator" id="ref-for-authenticator②⓪①">authenticator</a>; <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party②⓪⑦">Relying Parties</a> can only signal limited <a data-link-type="dfn" href="#attestation-conveyance" id="ref-for-attestation-conveyance③">attestation conveyance</a> preferences during <a data-link-type="dfn" href="#registration" id="ref-for-registration①⑥">registration</a>.
+   <p>The <a data-link-type="dfn" href="#attestation-type" id="ref-for-attestation-type④">attestation type</a> and <a data-link-type="dfn" href="#attestation-statement-format" id="ref-for-attestation-statement-format⑧">attestation statement format</a> is chosen by the <a data-link-type="dfn" href="#authenticator" id="ref-for-authenticator②⓪①">authenticator</a>; <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party②①②">Relying Parties</a> can only signal limited <a data-link-type="dfn" href="#attestation-conveyance" id="ref-for-attestation-conveyance③">attestation conveyance</a> preferences during <a data-link-type="dfn" href="#registration" id="ref-for-registration①⑨">registration</a>.
 It is expected that most <a data-link-type="dfn" href="#authenticator" id="ref-for-authenticator②⓪②">authenticators</a> will support a small number of <a data-link-type="dfn" href="#attestation-type" id="ref-for-attestation-type⑤">attestation types</a> and <a data-link-type="dfn" href="#attestation-statement-format" id="ref-for-attestation-statement-format⑨">attestation statement
-formats</a>, while <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party②⓪⑧">Relying Parties</a> will decide what <a data-link-type="dfn" href="#attestation-type" id="ref-for-attestation-type⑥">attestation types</a> are acceptable to them by policy. <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party②⓪⑨">Relying Parties</a> will also need to
+formats</a>, while <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party②①③">Relying Parties</a> will decide what <a data-link-type="dfn" href="#attestation-type" id="ref-for-attestation-type⑥">attestation types</a> are acceptable to them by policy. <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party②①④">Relying Parties</a> will also need to
 understand the characteristics of the <a data-link-type="dfn" href="#authenticator" id="ref-for-authenticator②⓪③">authenticators</a> that they trust, based on information they have about these <a data-link-type="dfn" href="#authenticator" id="ref-for-authenticator②⓪④">authenticators</a>. For example, the FIDO Metadata Service <a data-link-type="biblio" href="#biblio-fidometadataservice">[FIDOMetadataService]</a> provides one way to access such information.</p>
    <h4 class="heading settled" data-level="6.5.1" id="sctn-attested-credential-data"><span class="secno">6.5.1. </span><span class="content">Attested Credential Data</span><a class="self-link" href="#sctn-attested-credential-data"></a></h4>
-   <p><dfn class="dfn-paneled" data-dfn-type="dfn" data-noexport id="attested-credential-data">Attested credential data</dfn> is a variable-length byte array added to the <a data-link-type="dfn" href="#authenticator-data" id="ref-for-authenticator-data③⑨">authenticator data</a> when generating an <a data-link-type="dfn" href="#attestation-object" id="ref-for-attestation-object①③">attestation
+   <p><dfn class="dfn-paneled" data-dfn-type="dfn" data-noexport id="attested-credential-data">Attested credential data</dfn> is a variable-length byte array added to the <a data-link-type="dfn" href="#authenticator-data" id="ref-for-authenticator-data④①">authenticator data</a> when generating an <a data-link-type="dfn" href="#attestation-object" id="ref-for-attestation-object①③">attestation
 object</a> for a given credential. Its format is shown in <a href="#table-attestedCredentialData">Table <span class="table-ref-following"></span></a>.</p>
    <figure class="table" id="table-attestedCredentialData">
     <table class="complex data longlastcol">
@@ -4869,15 +4927,15 @@ <h4 class="heading settled" data-level="6.5.1" id="sctn-attested-credential-data
       <tr>
        <td><dfn class="dfn-paneled" data-dfn-for="authData/attestedCredentialData" data-dfn-type="dfn" data-noexport id="authdata-attestedcredentialdata-credentialid">credentialId</dfn>
        <td>L
-       <td><a data-link-type="dfn" href="#credential-id" id="ref-for-credential-id③⓪">Credential ID</a>
+       <td><a data-link-type="dfn" href="#credential-id" id="ref-for-credential-id③①">Credential ID</a>
       <tr>
        <td><dfn class="dfn-paneled" data-dfn-for="authData/attestedCredentialData" data-dfn-type="dfn" data-noexport id="authdata-attestedcredentialdata-credentialpublickey">credentialPublicKey</dfn>
        <td>variable
-       <td> The <a data-link-type="dfn" href="#credential-public-key" id="ref-for-credential-public-key②⑥">credential public key</a> encoded in COSE_Key format,
+       <td> The <a data-link-type="dfn" href="#credential-public-key" id="ref-for-credential-public-key②⑦">credential public key</a> encoded in COSE_Key format,
                 as defined in <a data-link-type="dfn" href="https://tools.ietf.org/html/rfc8152#section-7" id="ref-for-section-7②">Section 7</a> of <a data-link-type="biblio" href="#biblio-rfc8152">[RFC8152]</a>, using the <a data-link-type="dfn" href="https://fidoalliance.org/specs/fido-v2.0-ps-20190130/fido-client-to-authenticator-protocol-v2.0-ps-20190130.html#ctap2-canonical-cbor-encoding-form" id="ref-for-ctap2-canonical-cbor-encoding-form③">CTAP2 canonical CBOR encoding form</a>.
-                The COSE_Key-encoded <a data-link-type="dfn" href="#credential-public-key" id="ref-for-credential-public-key②⑦">credential public key</a> MUST contain the "alg" parameter and MUST NOT
+                The COSE_Key-encoded <a data-link-type="dfn" href="#credential-public-key" id="ref-for-credential-public-key②⑧">credential public key</a> MUST contain the "alg" parameter and MUST NOT
                 contain any other OPTIONAL parameters. The "alg" parameter MUST contain a <code class="idl"><a data-link-type="idl" href="#typedefdef-cosealgorithmidentifier" id="ref-for-typedefdef-cosealgorithmidentifier①①">COSEAlgorithmIdentifier</a></code> value.
-                The encoded <a data-link-type="dfn" href="#credential-public-key" id="ref-for-credential-public-key②⑧">credential public key</a> MUST also contain any additional REQUIRED parameters stipulated by the
+                The encoded <a data-link-type="dfn" href="#credential-public-key" id="ref-for-credential-public-key②⑨">credential public key</a> MUST also contain any additional REQUIRED parameters stipulated by the
                 relevant key type specification, i.e., REQUIRED for the key type "kty" and algorithm "alg" (see Section 8 of <a data-link-type="biblio" href="#biblio-rfc8152">[RFC8152]</a>). 
     </table>
     <figcaption> <a data-link-type="dfn" href="#attested-credential-data" id="ref-for-attested-credential-data①①">Attested credential data</a> layout. The names in the Name column are only for reference within this document, and are not
@@ -4946,20 +5004,20 @@ <h4 class="heading settled" data-level="6.5.2" id="sctn-attestation-formats"><sp
     <li data-md>
      <p><strong>Supported <a data-link-type="dfn" href="#attestation-type" id="ref-for-attestation-type⑦">attestation types</a>:</strong></p>
     <li data-md>
-     <p><strong>Syntax:</strong> The syntax of an <a data-link-type="dfn" href="#attestation-statement" id="ref-for-attestation-statement②⑤">attestation statement</a> produced in this format, defined using CDDL <a data-link-type="biblio" href="#biblio-rfc8610">[RFC8610]</a> for the extension point <code>$attStmtFormat</code> defined in <a href="#sctn-generating-an-attestation-object">§ 6.5.4 Generating an Attestation Object</a>.</p>
+     <p><strong>Syntax:</strong> The syntax of an <a data-link-type="dfn" href="#attestation-statement" id="ref-for-attestation-statement②⑥">attestation statement</a> produced in this format, defined using CDDL <a data-link-type="biblio" href="#biblio-rfc8610">[RFC8610]</a> for the extension point <code>$attStmtFormat</code> defined in <a href="#sctn-generating-an-attestation-object">§ 6.5.4 Generating an Attestation Object</a>.</p>
     <li data-md>
      <p><dfn class="dfn-paneled" data-dfn-type="dfn" data-noexport id="signing-procedure">Signing procedure</dfn>:
-The <a data-link-type="dfn" href="#signing-procedure" id="ref-for-signing-procedure②">signing procedure</a> for computing an <a data-link-type="dfn" href="#attestation-statement" id="ref-for-attestation-statement②⑥">attestation statement</a> in this <a data-link-type="dfn" href="#attestation-statement-format" id="ref-for-attestation-statement-format①②">format</a> given
-the <a data-link-type="dfn" href="#public-key-credential" id="ref-for-public-key-credential⑤①">public key credential</a> to be attested, the <a data-link-type="dfn" href="#authenticator-data" id="ref-for-authenticator-data④⓪">authenticator data</a> structure containing the <dfn class="dfn-paneled" data-dfn-type="dfn" data-lt="authenticator data for the attestation" data-noexport id="authenticator-data-for-the-attestation">authenticator data
+The <a data-link-type="dfn" href="#signing-procedure" id="ref-for-signing-procedure②">signing procedure</a> for computing an <a data-link-type="dfn" href="#attestation-statement" id="ref-for-attestation-statement②⑦">attestation statement</a> in this <a data-link-type="dfn" href="#attestation-statement-format" id="ref-for-attestation-statement-format①②">format</a> given
+the <a data-link-type="dfn" href="#public-key-credential" id="ref-for-public-key-credential⑤①">public key credential</a> to be attested, the <a data-link-type="dfn" href="#authenticator-data" id="ref-for-authenticator-data④②">authenticator data</a> structure containing the <dfn class="dfn-paneled" data-dfn-type="dfn" data-lt="authenticator data for the attestation" data-noexport id="authenticator-data-for-the-attestation">authenticator data
 for the attestation</dfn>, and the <a data-link-type="dfn" href="#collectedclientdata-hash-of-the-serialized-client-data" id="ref-for-collectedclientdata-hash-of-the-serialized-client-data①②">hash of the serialized client data</a>.</p>
     <li data-md>
      <p><dfn class="dfn-paneled" data-dfn-type="dfn" data-noexport id="verification-procedure">Verification procedure</dfn>:
-The procedure for verifying an <a data-link-type="dfn" href="#attestation-statement" id="ref-for-attestation-statement②⑦">attestation statement</a>, which takes the following <dfn class="dfn-paneled" data-dfn-type="dfn" data-noexport id="verification-procedure-inputs">verification procedure inputs</dfn>:</p>
+The procedure for verifying an <a data-link-type="dfn" href="#attestation-statement" id="ref-for-attestation-statement②⑧">attestation statement</a>, which takes the following <dfn class="dfn-paneled" data-dfn-type="dfn" data-noexport id="verification-procedure-inputs">verification procedure inputs</dfn>:</p>
      <ul>
       <li data-md>
-       <p><var>attStmt</var>: The <a data-link-type="dfn" href="#attestation-statement" id="ref-for-attestation-statement②⑧">attestation statement</a> structure</p>
+       <p><var>attStmt</var>: The <a data-link-type="dfn" href="#attestation-statement" id="ref-for-attestation-statement②⑨">attestation statement</a> structure</p>
       <li data-md>
-       <p><var>authenticatorData</var>: The <dfn class="dfn-paneled" data-dfn-type="dfn" data-noexport id="authenticator-data-claimed-to-have-been-used-for-the-attestation"><a data-link-type="dfn" href="#authenticator-data" id="ref-for-authenticator-data④①">authenticator data</a> claimed to have been used for the attestation</dfn></p>
+       <p><var>authenticatorData</var>: The <dfn class="dfn-paneled" data-dfn-type="dfn" data-noexport id="authenticator-data-claimed-to-have-been-used-for-the-attestation"><a data-link-type="dfn" href="#authenticator-data" id="ref-for-authenticator-data④③">authenticator data</a> claimed to have been used for the attestation</dfn></p>
       <li data-md>
        <p><var>clientDataHash</var>: The <a data-link-type="dfn" href="#collectedclientdata-hash-of-the-serialized-client-data" id="ref-for-collectedclientdata-hash-of-the-serialized-client-data①③">hash of the serialized client data</a></p>
      </ul>
@@ -4974,14 +5032,14 @@ <h4 class="heading settled" data-level="6.5.2" id="sctn-attestation-formats"><sp
    </ul>
    <p>The initial list of specified <a data-link-type="dfn" href="#attestation-statement-format" id="ref-for-attestation-statement-format①③">attestation statement formats</a> is in <a href="#sctn-defined-attestation-formats">§ 8 Defined Attestation Statement Formats</a>.</p>
    <h4 class="heading settled" data-level="6.5.3" id="sctn-attestation-types"><span class="secno">6.5.3. </span><span class="content">Attestation Types</span><a class="self-link" href="#sctn-attestation-types"></a></h4>
-   <p>WebAuthn supports several <a data-link-type="dfn" href="#attestation-type" id="ref-for-attestation-type⑨">attestation types</a>, defining the semantics of <a data-link-type="dfn" href="#attestation-statement" id="ref-for-attestation-statement②⑨">attestation statements</a> and their underlying trust
+   <p>WebAuthn supports several <a data-link-type="dfn" href="#attestation-type" id="ref-for-attestation-type⑨">attestation types</a>, defining the semantics of <a data-link-type="dfn" href="#attestation-statement" id="ref-for-attestation-statement③⓪">attestation statements</a> and their underlying trust
 models:</p>
-   <p class="note" role="note"><span>Note:</span> This specification does not define any data structures explicitly expressing the <a data-link-type="dfn" href="#attestation-type" id="ref-for-attestation-type①⓪">attestation types</a> employed by <a data-link-type="dfn" href="#authenticator" id="ref-for-authenticator②⓪⑥">authenticators</a>. <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party②①⓪">Relying Parties</a> engaging in <a data-link-type="dfn" href="#attestation-statement" id="ref-for-attestation-statement③⓪">attestation statement</a> <a data-link-type="dfn" href="#verification-procedure" id="ref-for-verification-procedure">verification</a> — i.e., when
-calling <code class="idl"><a data-link-type="idl" href="https://w3c.github.io/webappsec-credential-management/#dom-credentialscontainer-create" id="ref-for-dom-credentialscontainer-create②③">navigator.credentials.create()</a></code> they select an <a data-link-type="dfn" href="#attestation-conveyance" id="ref-for-attestation-conveyance④">attestation conveyance</a> other than <code class="idl"><a data-link-type="idl" href="#dom-attestationconveyancepreference-none" id="ref-for-dom-attestationconveyancepreference-none③">none</a></code> and verify the received <a data-link-type="dfn" href="#attestation-statement" id="ref-for-attestation-statement③①">attestation statement</a> — will determine the employed <a data-link-type="dfn" href="#attestation-type" id="ref-for-attestation-type①①">attestation type</a> as a part of <a data-link-type="dfn" href="#verification-procedure" id="ref-for-verification-procedure①">verification</a>. See the "Verification procedure" subsections of <a href="#sctn-defined-attestation-formats">§ 8 Defined Attestation Statement Formats</a>. See also <a href="#sctn-attestation-privacy">§ 14.4.1 Attestation Privacy</a>. For all <a data-link-type="dfn" href="#attestation-type" id="ref-for-attestation-type①②">attestation types</a> defined in this
-section other than <a data-link-type="dfn" href="#self-attestation" id="ref-for-self-attestation①①">Self</a> and <a data-link-type="dfn" href="#none" id="ref-for-none③">None</a>, <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party②①①">Relying Party</a> <a data-link-type="dfn" href="#verification-procedure" id="ref-for-verification-procedure②">verification</a> is followed by
+   <p class="note" role="note"><span>Note:</span> This specification does not define any data structures explicitly expressing the <a data-link-type="dfn" href="#attestation-type" id="ref-for-attestation-type①⓪">attestation types</a> employed by <a data-link-type="dfn" href="#authenticator" id="ref-for-authenticator②⓪⑥">authenticators</a>. <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party②①⑤">Relying Parties</a> engaging in <a data-link-type="dfn" href="#attestation-statement" id="ref-for-attestation-statement③①">attestation statement</a> <a data-link-type="dfn" href="#verification-procedure" id="ref-for-verification-procedure">verification</a> — i.e., when
+calling <code class="idl"><a data-link-type="idl" href="https://w3c.github.io/webappsec-credential-management/#dom-credentialscontainer-create" id="ref-for-dom-credentialscontainer-create②③">navigator.credentials.create()</a></code> they select an <a data-link-type="dfn" href="#attestation-conveyance" id="ref-for-attestation-conveyance④">attestation conveyance</a> other than <code class="idl"><a data-link-type="idl" href="#dom-attestationconveyancepreference-none" id="ref-for-dom-attestationconveyancepreference-none③">none</a></code> and verify the received <a data-link-type="dfn" href="#attestation-statement" id="ref-for-attestation-statement③②">attestation statement</a> — will determine the employed <a data-link-type="dfn" href="#attestation-type" id="ref-for-attestation-type①①">attestation type</a> as a part of <a data-link-type="dfn" href="#verification-procedure" id="ref-for-verification-procedure①">verification</a>. See the "Verification procedure" subsections of <a href="#sctn-defined-attestation-formats">§ 8 Defined Attestation Statement Formats</a>. See also <a href="#sctn-attestation-privacy">§ 14.4.1 Attestation Privacy</a>. For all <a data-link-type="dfn" href="#attestation-type" id="ref-for-attestation-type①②">attestation types</a> defined in this
+section other than <a data-link-type="dfn" href="#self-attestation" id="ref-for-self-attestation①①">Self</a> and <a data-link-type="dfn" href="#none" id="ref-for-none③">None</a>, <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party②①⑥">Relying Party</a> <a data-link-type="dfn" href="#verification-procedure" id="ref-for-verification-procedure②">verification</a> is followed by
 matching the <a data-link-type="dfn" href="#attestation-trust-path" id="ref-for-attestation-trust-path①">trust path</a> to an acceptable root certificate per step 20 of <a href="#sctn-registering-a-new-credential">§ 7.1 Registering a New Credential</a>.
 Differentiating these <a data-link-type="dfn" href="#attestation-type" id="ref-for-attestation-type①③">attestation types</a> becomes useful primarily as a means for determining if the <a data-link-type="dfn" href="#attestation" id="ref-for-attestation①⑤">attestation</a> is acceptable
-under <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party②①②">Relying Party</a> policy.</p>
+under <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party②①⑦">Relying Party</a> policy.</p>
    <dl>
     <dt data-md><dfn class="dfn-paneled" data-dfn-type="dfn" data-noexport id="basic-attestation">Basic Attestation</dfn> (<dfn class="dfn-paneled" data-dfn-type="dfn" data-noexport id="basic">Basic</dfn>)
     <dd data-md>
@@ -4991,7 +5049,7 @@ <h4 class="heading settled" data-level="6.5.3" id="sctn-attestation-types"><span
     <dt data-md><dfn class="dfn-paneled" data-dfn-type="dfn" data-noexport id="self-attestation">Self Attestation</dfn> (<dfn class="dfn-paneled" data-dfn-type="dfn" data-noexport id="self">Self</dfn>)
     <dd data-md>
      <p>In the case of <a data-link-type="dfn" href="#self-attestation" id="ref-for-self-attestation①②">self attestation</a>, also known as surrogate basic attestation <a data-link-type="biblio" href="#biblio-uafprotocol">[UAFProtocol]</a>, the Authenticator does not have
-any specific <a data-link-type="dfn" href="#attestation-key-pair" id="ref-for-attestation-key-pair⑤">attestation key pair</a>. Instead it uses the <a data-link-type="dfn" href="#credential-private-key" id="ref-for-credential-private-key①⑨">credential private key</a> to create the <a data-link-type="dfn" href="#attestation-signature" id="ref-for-attestation-signature⑦">attestation signature</a>.
+any specific <a data-link-type="dfn" href="#attestation-key-pair" id="ref-for-attestation-key-pair⑤">attestation key pair</a>. Instead it uses the <a data-link-type="dfn" href="#credential-private-key" id="ref-for-credential-private-key①⑨">credential private key</a> to create the <a data-link-type="dfn" href="#attestation-signature" id="ref-for-attestation-signature⑧">attestation signature</a>.
 Authenticators without meaningful protection measures for an <a data-link-type="dfn" href="#attestation-private-key" id="ref-for-attestation-private-key②">attestation private key</a> typically use this attestation type.</p>
     <dt data-md><dfn class="dfn-paneled" data-dfn-type="dfn" data-noexport id="attestation-ca">Attestation CA</dfn> (<dfn class="dfn-paneled" data-dfn-type="dfn" data-noexport id="attca">AttCA</dfn>)
     <dd data-md>
@@ -4999,16 +5057,16 @@ <h4 class="heading settled" data-level="6.5.3" id="sctn-attestation-types"><span
 "endorsement key" (EK). This key is used to securely communicate with a trusted third party, the <a data-link-type="dfn" href="#attestation-ca" id="ref-for-attestation-ca①">Attestation CA</a> <a data-link-type="biblio" href="#biblio-tcg-cmcprofile-aikcertenroll">[TCG-CMCProfile-AIKCertEnroll]</a> (formerly known as a "Privacy CA"). The <a data-link-type="dfn" href="#authenticator" id="ref-for-authenticator②⓪⑧">authenticator</a> can generate multiple
 attestation identity key pairs (AIK) and requests an <a data-link-type="dfn" href="#attestation-ca" id="ref-for-attestation-ca②">Attestation CA</a> to issue an AIK certificate
 for each. Using this approach, such an <a data-link-type="dfn" href="#authenticator" id="ref-for-authenticator②⓪⑨">authenticator</a> can limit the exposure of the EK (which is a global correlation
-handle) to Attestation CA(s). AIKs can be requested for each <a data-link-type="dfn" href="#authenticator" id="ref-for-authenticator②①⓪">authenticator</a>-generated <a data-link-type="dfn" href="#public-key-credential" id="ref-for-public-key-credential⑤②">public key credential</a> individually, and conveyed to <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party②①③">Relying Parties</a> as <a data-link-type="dfn" href="#attestation-certificate" id="ref-for-attestation-certificate③">attestation certificates</a>.</p>
+handle) to Attestation CA(s). AIKs can be requested for each <a data-link-type="dfn" href="#authenticator" id="ref-for-authenticator②①⓪">authenticator</a>-generated <a data-link-type="dfn" href="#public-key-credential" id="ref-for-public-key-credential⑤②">public key credential</a> individually, and conveyed to <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party②①⑧">Relying Parties</a> as <a data-link-type="dfn" href="#attestation-certificate" id="ref-for-attestation-certificate③">attestation certificates</a>.</p>
      <p class="note" role="note"><span>Note:</span> This concept typically leads to multiple attestation certificates. The attestation certificate requested most recently
     is called "active".</p>
     <dt data-md><dfn class="dfn-paneled" data-dfn-type="dfn" data-noexport id="anonymization-ca">Anonymization CA</dfn> (<dfn class="dfn-paneled" data-dfn-type="dfn" data-noexport id="anonca">AnonCA</dfn>)
     <dd data-md>
-     <p>In this case, the <a data-link-type="dfn" href="#authenticator" id="ref-for-authenticator②①①">authenticator</a> uses an <a data-link-type="dfn" href="#anonymization-ca" id="ref-for-anonymization-ca③">Anonymization CA</a> which dynamically generates per-<a data-link-type="dfn" href="https://w3c.github.io/webappsec-credential-management/#concept-credential" id="ref-for-concept-credential①⑦">credential</a> <a data-link-type="dfn" href="#attestation-certificate" id="ref-for-attestation-certificate④">attestation certificates</a> such that the <a data-link-type="dfn" href="#attestation-statement" id="ref-for-attestation-statement③②">attestation statements</a> presented to <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party②①④">Relying Parties</a> do not provide uniquely identifiable information, e.g., that might be used for tracking purposes.</p>
-     <p class="note" role="note"><span>Note:</span> <a data-link-type="dfn" href="#attestation-statement" id="ref-for-attestation-statement③③">Attestation statements</a> conveying <a data-link-type="dfn" href="#attestation" id="ref-for-attestation①⑥">attestations</a> of <a data-link-type="dfn" href="#attestation-type" id="ref-for-attestation-type①④">type</a> <a data-link-type="dfn" href="#attca" id="ref-for-attca">AttCA</a> or <a data-link-type="dfn" href="#anonca" id="ref-for-anonca">AnonCA</a> use the same data structure
+     <p>In this case, the <a data-link-type="dfn" href="#authenticator" id="ref-for-authenticator②①①">authenticator</a> uses an <a data-link-type="dfn" href="#anonymization-ca" id="ref-for-anonymization-ca③">Anonymization CA</a> which dynamically generates per-<a data-link-type="dfn" href="https://w3c.github.io/webappsec-credential-management/#concept-credential" id="ref-for-concept-credential①⑥">credential</a> <a data-link-type="dfn" href="#attestation-certificate" id="ref-for-attestation-certificate④">attestation certificates</a> such that the <a data-link-type="dfn" href="#attestation-statement" id="ref-for-attestation-statement③③">attestation statements</a> presented to <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party②①⑨">Relying Parties</a> do not provide uniquely identifiable information, e.g., that might be used for tracking purposes.</p>
+     <p class="note" role="note"><span>Note:</span> <a data-link-type="dfn" href="#attestation-statement" id="ref-for-attestation-statement③④">Attestation statements</a> conveying <a data-link-type="dfn" href="#attestation" id="ref-for-attestation①⑥">attestations</a> of <a data-link-type="dfn" href="#attestation-type" id="ref-for-attestation-type①④">type</a> <a data-link-type="dfn" href="#attca" id="ref-for-attca">AttCA</a> or <a data-link-type="dfn" href="#anonca" id="ref-for-anonca">AnonCA</a> use the same data structure
     as those of <a data-link-type="dfn" href="#attestation-type" id="ref-for-attestation-type①⑤">type</a> <a data-link-type="dfn" href="#basic" id="ref-for-basic">Basic</a>, so the three attestation types
     are, in general, distinguishable only with externally provided knowledge regarding the contents of the <a data-link-type="dfn" href="#attestation-certificate" id="ref-for-attestation-certificate⑤">attestation
-    certificates</a> conveyed in the <a data-link-type="dfn" href="#attestation-statement" id="ref-for-attestation-statement③④">attestation statement</a>.</p>
+    certificates</a> conveyed in the <a data-link-type="dfn" href="#attestation-statement" id="ref-for-attestation-statement③⑤">attestation statement</a>.</p>
     <dt data-md>No attestation statement (<dfn class="dfn-paneled" data-dfn-type="dfn" data-noexport id="none">None</dfn>)
     <dd data-md>
      <p>In this case, no attestation information is available. See also <a href="#sctn-none-attestation">§ 8.7 None Attestation Statement Format</a>.</p>
@@ -5021,7 +5079,7 @@ <h4 class="heading settled" data-level="6.5.4" id="sctn-generating-an-attestatio
      <p>An <a data-link-type="dfn" href="#attestation-statement-format" id="ref-for-attestation-statement-format①④">attestation statement format</a>.</p>
     <dt data-md><var>authData</var>
     <dd data-md>
-     <p>A byte array containing <a data-link-type="dfn" href="#authenticator-data" id="ref-for-authenticator-data④②">authenticator data</a>.</p>
+     <p>A byte array containing <a data-link-type="dfn" href="#authenticator-data" id="ref-for-authenticator-data④④">authenticator data</a>.</p>
     <dt data-md><var>hash</var>
     <dd data-md>
      <p>The <a data-link-type="dfn" href="#collectedclientdata-hash-of-the-serialized-client-data" id="ref-for-collectedclientdata-hash-of-the-serialized-client-data①④">hash of the serialized client data</a>.</p>
@@ -5079,17 +5137,17 @@ <h4 class="heading settled" data-level="6.5.5" id="sctn-signature-attestation-ty
 The signature is not ASN.1 wrapped.</p>
    </ul>
    <h2 class="heading settled" data-level="7" id="sctn-rp-operations"><span class="secno">7. </span><span class="content"><a data-link-type="dfn" href="#webauthn-relying-party" id="ref-for-webauthn-relying-party②⑧">WebAuthn Relying Party</a> Operations</span><a class="self-link" href="#sctn-rp-operations"></a></h2>
-   <p>A <a data-link-type="dfn" href="#registration-ceremony" id="ref-for-registration-ceremony⑦">registration</a> or <a data-link-type="dfn" href="#authentication-ceremony" id="ref-for-authentication-ceremony①⑨">authentication ceremony</a> begins with the <a data-link-type="dfn" href="#webauthn-relying-party" id="ref-for-webauthn-relying-party②⑨">WebAuthn Relying Party</a> creating a <code class="idl"><a data-link-type="idl" href="#dictdef-publickeycredentialcreationoptions" id="ref-for-dictdef-publickeycredentialcreationoptions⑧">PublicKeyCredentialCreationOptions</a></code> or <code class="idl"><a data-link-type="idl" href="#dictdef-publickeycredentialrequestoptions" id="ref-for-dictdef-publickeycredentialrequestoptions①①">PublicKeyCredentialRequestOptions</a></code> object, respectively, which encodes the parameters for the <a data-link-type="dfn" href="#ceremony" id="ref-for-ceremony①⓪">ceremony</a>. The <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party②①⑤">Relying Party</a> SHOULD take care to not leak sensitive information during this stage; see <a href="#sctn-username-enumeration">§ 14.6.2 Username Enumeration</a> for details.</p>
-   <p>Upon successful execution of <code class="idl"><a data-link-type="idl" href="https://w3c.github.io/webappsec-credential-management/#dom-credentialscontainer-create" id="ref-for-dom-credentialscontainer-create②④">create()</a></code> or <code class="idl"><a data-link-type="idl" href="https://w3c.github.io/webappsec-credential-management/#dom-credentialscontainer-get" id="ref-for-dom-credentialscontainer-get②⑧">get()</a></code>, the <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party②①⑥">Relying Party</a>'s script receives
+   <p>A <a data-link-type="dfn" href="#registration-ceremony" id="ref-for-registration-ceremony⑦">registration</a> or <a data-link-type="dfn" href="#authentication-ceremony" id="ref-for-authentication-ceremony②⓪">authentication ceremony</a> begins with the <a data-link-type="dfn" href="#webauthn-relying-party" id="ref-for-webauthn-relying-party②⑨">WebAuthn Relying Party</a> creating a <code class="idl"><a data-link-type="idl" href="#dictdef-publickeycredentialcreationoptions" id="ref-for-dictdef-publickeycredentialcreationoptions⑧">PublicKeyCredentialCreationOptions</a></code> or <code class="idl"><a data-link-type="idl" href="#dictdef-publickeycredentialrequestoptions" id="ref-for-dictdef-publickeycredentialrequestoptions①①">PublicKeyCredentialRequestOptions</a></code> object, respectively, which encodes the parameters for the <a data-link-type="dfn" href="#ceremony" id="ref-for-ceremony①②">ceremony</a>. The <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party②②⓪">Relying Party</a> SHOULD take care to not leak sensitive information during this stage; see <a href="#sctn-username-enumeration">§ 14.6.2 Username Enumeration</a> for details.</p>
+   <p>Upon successful execution of <code class="idl"><a data-link-type="idl" href="https://w3c.github.io/webappsec-credential-management/#dom-credentialscontainer-create" id="ref-for-dom-credentialscontainer-create②④">create()</a></code> or <code class="idl"><a data-link-type="idl" href="https://w3c.github.io/webappsec-credential-management/#dom-credentialscontainer-get" id="ref-for-dom-credentialscontainer-get②⑧">get()</a></code>, the <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party②②①">Relying Party</a>'s script receives
 a <code class="idl"><a data-link-type="idl" href="#publickeycredential" id="ref-for-publickeycredential②④">PublicKeyCredential</a></code> containing an <code class="idl"><a data-link-type="idl" href="#authenticatorattestationresponse" id="ref-for-authenticatorattestationresponse⑤">AuthenticatorAttestationResponse</a></code> or <code class="idl"><a data-link-type="idl" href="#authenticatorassertionresponse" id="ref-for-authenticatorassertionresponse⑥">AuthenticatorAssertionResponse</a></code> structure,
-respectively, from the client. It must then deliver the contents of this structure to the <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party②①⑦">Relying Party</a> server, using methods outside
-the scope of this specification. This section describes the operations that the <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party②①⑧">Relying Party</a> must perform upon receipt of these
+respectively, from the client. It must then deliver the contents of this structure to the <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party②②②">Relying Party</a> server, using methods outside
+the scope of this specification. This section describes the operations that the <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party②②③">Relying Party</a> must perform upon receipt of these
 structures.</p>
    <h3 class="heading settled" data-level="7.1" id="sctn-registering-a-new-credential"><span class="secno">7.1. </span><span class="content">Registering a New Credential</span><a class="self-link" href="#sctn-registering-a-new-credential"></a></h3>
-   <p>In order to perform a <a data-link-type="dfn" href="#registration-ceremony" id="ref-for-registration-ceremony⑧">registration ceremony</a>, the <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party②①⑨">Relying Party</a> MUST proceed as follows:</p>
+   <p>In order to perform a <a data-link-type="dfn" href="#registration-ceremony" id="ref-for-registration-ceremony⑧">registration ceremony</a>, the <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party②②④">Relying Party</a> MUST proceed as follows:</p>
    <ol>
     <li data-md>
-     <p>Let <var>options</var> be a new <code class="idl"><a data-link-type="idl" href="#dictdef-publickeycredentialcreationoptions" id="ref-for-dictdef-publickeycredentialcreationoptions⑨">PublicKeyCredentialCreationOptions</a></code> structure configured to the <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party②②⓪">Relying Party</a>'s needs for the ceremony.</p>
+     <p>Let <var>options</var> be a new <code class="idl"><a data-link-type="idl" href="#dictdef-publickeycredentialcreationoptions" id="ref-for-dictdef-publickeycredentialcreationoptions⑨">PublicKeyCredentialCreationOptions</a></code> structure configured to the <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party②②⑤">Relying Party</a>'s needs for the ceremony.</p>
     <li data-md>
      <p>Call <code class="idl"><a data-link-type="idl" href="https://w3c.github.io/webappsec-credential-management/#dom-credentialscontainer-create" id="ref-for-dom-credentialscontainer-create②⑤">navigator.credentials.create()</a></code> and pass <var>options</var> as the <code><code class="idl"><a data-link-type="idl" href="#dom-credentialcreationoptions-publickey" id="ref-for-dom-credentialcreationoptions-publickey④">publicKey</a></code></code> option.
 Let <var>credential</var> be the result of the successfully resolved promise.
@@ -5104,7 +5162,7 @@ <h3 class="heading settled" data-level="7.1" id="sctn-registering-a-new-credenti
      <p>Let <var>clientExtensionResults</var> be the result of calling <code><var>credential</var>.<code class="idl"><a data-link-type="idl" href="#dom-publickeycredential-getclientextensionresults" id="ref-for-dom-publickeycredential-getclientextensionresults②">getClientExtensionResults()</a></code></code>.</p>
     <li data-md>
      <p>Let <var>JSONtext</var> be the result of
-running <a data-link-type="dfn" href="https://encoding.spec.whatwg.org/#utf-8-decode" id="ref-for-utf-8-decode">UTF-8 decode</a> on the value of <code><var>response</var>.<code class="idl"><a data-link-type="idl" href="#dom-authenticatorresponse-clientdatajson" id="ref-for-dom-authenticatorresponse-clientdatajson⑥">clientDataJSON</a></code></code>.</p>
+running <a data-link-type="dfn" href="https://encoding.spec.whatwg.org/#utf-8-decode" id="ref-for-utf-8-decode">UTF-8 decode</a> on the value of <code><var>response</var>.<code class="idl"><a data-link-type="idl" href="#dom-authenticatorresponse-clientdatajson" id="ref-for-dom-authenticatorresponse-clientdatajson⑦">clientDataJSON</a></code></code>.</p>
      <p class="note" role="note"><span>Note:</span> Using any implementation of <a data-link-type="dfn" href="https://encoding.spec.whatwg.org/#utf-8-decode" id="ref-for-utf-8-decode①">UTF-8 decode</a> is acceptable as long as it yields the same result as that yielded by
 the <a data-link-type="dfn" href="https://encoding.spec.whatwg.org/#utf-8-decode" id="ref-for-utf-8-decode②">UTF-8 decode</a> algorithm. In particular, any leading byte order mark (BOM) MUST be stripped.</p>
     <li data-md>
@@ -5118,33 +5176,33 @@ <h3 class="heading settled" data-level="7.1" id="sctn-registering-a-new-credenti
      <p>Verify that the value of <code><var>C</var>.<code class="idl"><a data-link-type="idl" href="#dom-collectedclientdata-challenge" id="ref-for-dom-collectedclientdata-challenge⑥">challenge</a></code></code> equals
 the base64url encoding of <code><var>options</var>.<code class="idl"><a data-link-type="idl" href="#dom-publickeycredentialcreationoptions-challenge" id="ref-for-dom-publickeycredentialcreationoptions-challenge②">challenge</a></code></code>.</p>
     <li data-md>
-     <p>Verify that the value of <code><var>C</var>.<code class="idl"><a data-link-type="idl" href="#dom-collectedclientdata-origin" id="ref-for-dom-collectedclientdata-origin⑦">origin</a></code></code> matches the <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party②②①">Relying Party</a>'s <a data-link-type="dfn" href="https://html.spec.whatwg.org/multipage/origin.html#concept-origin" id="ref-for-concept-origin①③">origin</a>.</p>
+     <p>Verify that the value of <code><var>C</var>.<code class="idl"><a data-link-type="idl" href="#dom-collectedclientdata-origin" id="ref-for-dom-collectedclientdata-origin⑦">origin</a></code></code> matches the <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party②②⑥">Relying Party</a>'s <a data-link-type="dfn" href="https://html.spec.whatwg.org/multipage/origin.html#concept-origin" id="ref-for-concept-origin①③">origin</a>.</p>
     <li data-md>
-     <p>Let <var>hash</var> be the result of computing a hash over <code><var>response</var>.<code class="idl"><a data-link-type="idl" href="#dom-authenticatorresponse-clientdatajson" id="ref-for-dom-authenticatorresponse-clientdatajson⑦">clientDataJSON</a></code></code> using SHA-256.</p>
+     <p>Let <var>hash</var> be the result of computing a hash over <code><var>response</var>.<code class="idl"><a data-link-type="idl" href="#dom-authenticatorresponse-clientdatajson" id="ref-for-dom-authenticatorresponse-clientdatajson⑧">clientDataJSON</a></code></code> using SHA-256.</p>
     <li data-md>
-     <p>Perform CBOR decoding on the <code class="idl"><a data-link-type="idl" href="#dom-authenticatorattestationresponse-attestationobject" id="ref-for-dom-authenticatorattestationresponse-attestationobject⑥">attestationObject</a></code> field of the <code class="idl"><a data-link-type="idl" href="#authenticatorattestationresponse" id="ref-for-authenticatorattestationresponse⑦">AuthenticatorAttestationResponse</a></code> structure to obtain the attestation statement format <var>fmt</var>, the <a data-link-type="dfn" href="#authenticator-data" id="ref-for-authenticator-data④③">authenticator data</a> <var>authData</var>, and the attestation statement <var>attStmt</var>.</p>
+     <p>Perform CBOR decoding on the <code class="idl"><a data-link-type="idl" href="#dom-authenticatorattestationresponse-attestationobject" id="ref-for-dom-authenticatorattestationresponse-attestationobject⑦">attestationObject</a></code> field of the <code class="idl"><a data-link-type="idl" href="#authenticatorattestationresponse" id="ref-for-authenticatorattestationresponse⑦">AuthenticatorAttestationResponse</a></code> structure to obtain the attestation statement format <var>fmt</var>, the <a data-link-type="dfn" href="#authenticator-data" id="ref-for-authenticator-data④⑤">authenticator data</a> <var>authData</var>, and the attestation statement <var>attStmt</var>.</p>
     <li data-md>
-     <p>Verify that the <code><a data-link-type="dfn" href="#authdata-rpidhash" id="ref-for-authdata-rpidhash②">rpIdHash</a></code> in <var>authData</var> is the SHA-256 hash of the <a data-link-type="dfn" href="#rp-id" id="ref-for-rp-id③⑦">RP ID</a> expected by the <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party②②②">Relying Party</a>.</p>
+     <p>Verify that the <code><a data-link-type="dfn" href="#authdata-rpidhash" id="ref-for-authdata-rpidhash②">rpIdHash</a></code> in <var>authData</var> is the SHA-256 hash of the <a data-link-type="dfn" href="#rp-id" id="ref-for-rp-id③⑦">RP ID</a> expected by the <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party②②⑦">Relying Party</a>.</p>
     <li data-md>
-     <p>Verify that the <a data-link-type="dfn" href="#authdata-flags-up" id="ref-for-authdata-flags-up③">UP</a> bit of the <code><a data-link-type="dfn" href="#authdata-flags" id="ref-for-authdata-flags②⑧">flags</a></code> in <var>authData</var> is set.</p>
+     <p>Verify that the <a data-link-type="dfn" href="#authdata-flags-up" id="ref-for-authdata-flags-up③">UP</a> bit of the <code><a data-link-type="dfn" href="#authdata-flags" id="ref-for-authdata-flags③⓪">flags</a></code> in <var>authData</var> is set.</p>
     <li data-md>
-     <p>If the <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party②②③">Relying Party</a> requires <a data-link-type="dfn" href="#user-verification" id="ref-for-user-verification④①">user verification</a> for this registration,
-verify that the <a data-link-type="dfn" href="#authdata-flags-uv" id="ref-for-authdata-flags-uv⑦">UV</a> bit of the <code><a data-link-type="dfn" href="#authdata-flags" id="ref-for-authdata-flags②⑨">flags</a></code> in <var>authData</var> is set.</p>
+     <p>If the <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party②②⑧">Relying Party</a> requires <a data-link-type="dfn" href="#user-verification" id="ref-for-user-verification④①">user verification</a> for this registration,
+verify that the <a data-link-type="dfn" href="#authdata-flags-uv" id="ref-for-authdata-flags-uv⑦">UV</a> bit of the <code><a data-link-type="dfn" href="#authdata-flags" id="ref-for-authdata-flags③①">flags</a></code> in <var>authData</var> is set.</p>
     <li data-md>
-     <p>If the <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party②②④">Relying Party</a> uses the credential’s <a data-link-type="dfn" href="#backup-eligibility" id="ref-for-backup-eligibility③">backup eligibility</a> to inform its user experience flows and/or policies, evaluate the <a data-link-type="dfn" href="#authdata-flags-be" id="ref-for-authdata-flags-be⑤">BE</a> bit of the <code><a data-link-type="dfn" href="#authdata-flags" id="ref-for-authdata-flags③⓪">flags</a></code> in <var>authData</var>.</p>
+     <p>If the <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party②②⑨">Relying Party</a> uses the credential’s <a data-link-type="dfn" href="#backup-eligibility" id="ref-for-backup-eligibility③">backup eligibility</a> to inform its user experience flows and/or policies, evaluate the <a data-link-type="dfn" href="#authdata-flags-be" id="ref-for-authdata-flags-be⑥">BE</a> bit of the <code><a data-link-type="dfn" href="#authdata-flags" id="ref-for-authdata-flags③②">flags</a></code> in <var>authData</var>.</p>
     <li data-md>
-     <p>If the <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party②②⑤">Relying Party</a> uses the credential’s <a data-link-type="dfn" href="#backup-state" id="ref-for-backup-state③">backup state</a> to inform its user experience flows and/or policies, evaluate the <a data-link-type="dfn" href="#authdata-flags-bs" id="ref-for-authdata-flags-bs⑥">BS</a> bit of the <code><a data-link-type="dfn" href="#authdata-flags" id="ref-for-authdata-flags③①">flags</a></code> in <var>authData</var>, and then store the value for evaluation in future <a data-link-type="dfn" href="#authentication-ceremony" id="ref-for-authentication-ceremony②⓪">authentication ceremonies</a>.</p>
+     <p>If the <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party②③⓪">Relying Party</a> uses the credential’s <a data-link-type="dfn" href="#backup-state" id="ref-for-backup-state③">backup state</a> to inform its user experience flows and/or policies, evaluate the <a data-link-type="dfn" href="#authdata-flags-bs" id="ref-for-authdata-flags-bs⑦">BS</a> bit of the <code><a data-link-type="dfn" href="#authdata-flags" id="ref-for-authdata-flags③③">flags</a></code> in <var>authData</var>.</p>
     <li data-md>
-     <p>Verify that the "alg" parameter in the <a data-link-type="dfn" href="#authdata-attestedcredentialdata-credentialpublickey" id="ref-for-authdata-attestedcredentialdata-credentialpublickey⑤">credential public key</a> in <var>authData</var> matches the <code class="idl"><a data-link-type="idl" href="#dom-publickeycredentialparameters-alg" id="ref-for-dom-publickeycredentialparameters-alg②">alg</a></code> attribute of one of the <a data-link-type="dfn" href="https://infra.spec.whatwg.org/#list-item" id="ref-for-list-item①①">items</a> in <code><var>options</var>.<code class="idl"><a data-link-type="idl" href="#dom-publickeycredentialcreationoptions-pubkeycredparams" id="ref-for-dom-publickeycredentialcreationoptions-pubkeycredparams④">pubKeyCredParams</a></code></code>.</p>
+     <p>Verify that the "alg" parameter in the <a data-link-type="dfn" href="#authdata-attestedcredentialdata-credentialpublickey" id="ref-for-authdata-attestedcredentialdata-credentialpublickey⑤">credential public key</a> in <var>authData</var> matches the <code class="idl"><a data-link-type="idl" href="#dom-publickeycredentialparameters-alg" id="ref-for-dom-publickeycredentialparameters-alg②">alg</a></code> attribute of one of the <a data-link-type="dfn" href="https://infra.spec.whatwg.org/#list-item" id="ref-for-list-item①②">items</a> in <code><var>options</var>.<code class="idl"><a data-link-type="idl" href="#dom-publickeycredentialcreationoptions-pubkeycredparams" id="ref-for-dom-publickeycredentialcreationoptions-pubkeycredparams④">pubKeyCredParams</a></code></code>.</p>
     <li data-md>
      <p>Verify that the values of the <a data-link-type="dfn" href="#client-extension-output" id="ref-for-client-extension-output⑥">client extension outputs</a> in <var>clientExtensionResults</var> and the <a data-link-type="dfn" href="#authenticator-extension-output" id="ref-for-authenticator-extension-output③">authenticator extension
 outputs</a> in the <code><a data-link-type="dfn" href="#authdata-extensions" id="ref-for-authdata-extensions⑦">extensions</a></code> in <var>authData</var> are as expected, considering the <a data-link-type="dfn" href="#client-extension-input" id="ref-for-client-extension-input⑤">client
-extension input</a> values that were given in <code><var>options</var>.<code class="idl"><a data-link-type="idl" href="#dom-publickeycredentialcreationoptions-extensions" id="ref-for-dom-publickeycredentialcreationoptions-extensions④">extensions</a></code></code> and any specific policy of the <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party②②⑥">Relying Party</a> regarding unsolicited extensions, i.e., those that were not specified as part of <code><var>options</var>.<code class="idl"><a data-link-type="idl" href="#dom-publickeycredentialcreationoptions-extensions" id="ref-for-dom-publickeycredentialcreationoptions-extensions⑤">extensions</a></code></code>.
-In the general case, the meaning of "are as expected" is specific to the <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party②②⑦">Relying Party</a> and which extensions are in use.</p>
-     <p class="note" role="note"><span>Note:</span> <a data-link-type="dfn" href="#client-platform" id="ref-for-client-platform④⑥">Client platforms</a> MAY enact local policy that sets additional <a data-link-type="dfn" href="#authenticator-extension" id="ref-for-authenticator-extension③">authenticator extensions</a> or <a data-link-type="dfn" href="#client-extension" id="ref-for-client-extension②">client extensions</a> and thus cause values to appear in the <a data-link-type="dfn" href="#authenticator-extension-output" id="ref-for-authenticator-extension-output④">authenticator extension outputs</a> or <a data-link-type="dfn" href="#client-extension-output" id="ref-for-client-extension-output⑦">client extension outputs</a> that were not originally specified as part of <code><var>options</var>.<code class="idl"><a data-link-type="idl" href="#dom-publickeycredentialcreationoptions-extensions" id="ref-for-dom-publickeycredentialcreationoptions-extensions⑥">extensions</a></code></code>. <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party②②⑧">Relying Parties</a> MUST be prepared to handle such
-situations, whether it be to ignore the unsolicited extensions or reject the attestation. The <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party②②⑨">Relying Party</a> can make this
+extension input</a> values that were given in <code><var>options</var>.<code class="idl"><a data-link-type="idl" href="#dom-publickeycredentialcreationoptions-extensions" id="ref-for-dom-publickeycredentialcreationoptions-extensions④">extensions</a></code></code> and any specific policy of the <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party②③①">Relying Party</a> regarding unsolicited extensions, i.e., those that were not specified as part of <code><var>options</var>.<code class="idl"><a data-link-type="idl" href="#dom-publickeycredentialcreationoptions-extensions" id="ref-for-dom-publickeycredentialcreationoptions-extensions⑤">extensions</a></code></code>.
+In the general case, the meaning of "are as expected" is specific to the <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party②③②">Relying Party</a> and which extensions are in use.</p>
+     <p class="note" role="note"><span>Note:</span> <a data-link-type="dfn" href="#client-platform" id="ref-for-client-platform④⑥">Client platforms</a> MAY enact local policy that sets additional <a data-link-type="dfn" href="#authenticator-extension" id="ref-for-authenticator-extension③">authenticator extensions</a> or <a data-link-type="dfn" href="#client-extension" id="ref-for-client-extension②">client extensions</a> and thus cause values to appear in the <a data-link-type="dfn" href="#authenticator-extension-output" id="ref-for-authenticator-extension-output④">authenticator extension outputs</a> or <a data-link-type="dfn" href="#client-extension-output" id="ref-for-client-extension-output⑦">client extension outputs</a> that were not originally specified as part of <code><var>options</var>.<code class="idl"><a data-link-type="idl" href="#dom-publickeycredentialcreationoptions-extensions" id="ref-for-dom-publickeycredentialcreationoptions-extensions⑥">extensions</a></code></code>. <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party②③③">Relying Parties</a> MUST be prepared to handle such
+situations, whether it be to ignore the unsolicited extensions or reject the attestation. The <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party②③④">Relying Party</a> can make this
 decision based on local policy and the extensions in use.</p>
-     <p class="note" role="note"><span>Note:</span> Since all extensions are OPTIONAL for both the <a data-link-type="dfn" href="#client" id="ref-for-client⑧⓪">client</a> and the <a data-link-type="dfn" href="#authenticator" id="ref-for-authenticator②①⑥">authenticator</a>, the <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party②③⓪">Relying Party</a> MUST also be
+     <p class="note" role="note"><span>Note:</span> Since all extensions are OPTIONAL for both the <a data-link-type="dfn" href="#client" id="ref-for-client⑧⓪">client</a> and the <a data-link-type="dfn" href="#authenticator" id="ref-for-authenticator②①⑥">authenticator</a>, the <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party②③⑤">Relying Party</a> MUST also be
 prepared to handle cases where none or not all of the requested extensions were acted upon.</p>
     <li data-md>
      <p>Determine the attestation statement format by performing a USASCII case-sensitive match on <var>fmt</var> against the set of
@@ -5153,7 +5211,7 @@ <h3 class="heading settled" data-level="7.1" id="sctn-registering-a-new-credenti
 is maintained in the
 IANA "WebAuthn Attestation Statement Format Identifiers" registry <a data-link-type="biblio" href="#biblio-iana-webauthn-registries">[IANA-WebAuthn-Registries]</a> established by <a data-link-type="biblio" href="#biblio-rfc8809">[RFC8809]</a>.</p>
     <li data-md>
-     <p>Verify that <var>attStmt</var> is a correct <a data-link-type="dfn" href="#attestation-statement" id="ref-for-attestation-statement③⑤">attestation statement</a>, conveying a valid <a data-link-type="dfn" href="#attestation-signature" id="ref-for-attestation-signature⑧">attestation signature</a>, by using the <a data-link-type="dfn" href="#attestation-statement-format" id="ref-for-attestation-statement-format①⑤">attestation statement format</a> <var>fmt</var>’s <a data-link-type="dfn" href="#verification-procedure" id="ref-for-verification-procedure③">verification procedure</a> given <var>attStmt</var>, <var>authData</var> and <var>hash</var>.</p>
+     <p>Verify that <var>attStmt</var> is a correct <a data-link-type="dfn" href="#attestation-statement" id="ref-for-attestation-statement③⑥">attestation statement</a>, conveying a valid <a data-link-type="dfn" href="#attestation-signature" id="ref-for-attestation-signature⑨">attestation signature</a>, by using the <a data-link-type="dfn" href="#attestation-statement-format" id="ref-for-attestation-statement-format①⑤">attestation statement format</a> <var>fmt</var>’s <a data-link-type="dfn" href="#verification-procedure" id="ref-for-verification-procedure③">verification procedure</a> given <var>attStmt</var>, <var>authData</var> and <var>hash</var>.</p>
      <p class="note" role="note"><span>Note:</span> Each <a data-link-type="dfn" href="#attestation-statement-format" id="ref-for-attestation-statement-format①⑥">attestation statement format</a> specifies its own <a data-link-type="dfn" href="#verification-procedure" id="ref-for-verification-procedure④">verification procedure</a>. See <a href="#sctn-defined-attestation-formats">§ 8 Defined Attestation Statement Formats</a> for
 the initially-defined formats, and <a data-link-type="biblio" href="#biblio-iana-webauthn-registries">[IANA-WebAuthn-Registries]</a> for the up-to-date list.</p>
     <li data-md>
@@ -5164,87 +5222,102 @@ <h3 class="heading settled" data-level="7.1" id="sctn-registering-a-new-credenti
      <p>Assess the attestation trustworthiness using the outputs of the <a data-link-type="dfn" href="#verification-procedure" id="ref-for-verification-procedure⑤">verification procedure</a> in step 19, as follows:</p>
      <ul>
       <li data-md>
-       <p>If <a data-link-type="dfn" href="#none" id="ref-for-none④">no attestation</a> was provided, verify that <a data-link-type="dfn" href="#none" id="ref-for-none⑤">None</a> attestation is acceptable under <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party②③①">Relying Party</a> policy.</p>
+       <p>If <a data-link-type="dfn" href="#none" id="ref-for-none④">no attestation</a> was provided, verify that <a data-link-type="dfn" href="#none" id="ref-for-none⑤">None</a> attestation is acceptable under <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party②③⑥">Relying Party</a> policy.</p>
       <li data-md>
-       <p>If <a data-link-type="dfn" href="#self-attestation" id="ref-for-self-attestation①③">self attestation</a> was used, verify that <a data-link-type="dfn" href="#self-attestation" id="ref-for-self-attestation①④">self attestation</a> is acceptable under <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party②③②">Relying Party</a> policy.</p>
+       <p>If <a data-link-type="dfn" href="#self-attestation" id="ref-for-self-attestation①③">self attestation</a> was used, verify that <a data-link-type="dfn" href="#self-attestation" id="ref-for-self-attestation①④">self attestation</a> is acceptable under <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party②③⑦">Relying Party</a> policy.</p>
       <li data-md>
        <p>Otherwise, use the X.509 certificates returned as the <a data-link-type="dfn" href="#attestation-trust-path" id="ref-for-attestation-trust-path②">attestation trust path</a> from the <a data-link-type="dfn" href="#verification-procedure" id="ref-for-verification-procedure⑥">verification procedure</a> to verify that the attestation public key either correctly chains up to an acceptable root certificate, or is itself an acceptable certificate (i.e., it and the root certificate obtained in Step 19 may be the same).</p>
      </ul>
     <li data-md>
      <p>Verify that the <code><a data-link-type="dfn" href="#authdata-attestedcredentialdata-credentialid" id="ref-for-authdata-attestedcredentialdata-credentialid④">credentialId</a></code> is ≤ 1023 bytes. Credential IDs larger than this many bytes SHOULD cause the RP to fail this <a data-link-type="dfn" href="#registration-ceremony" id="ref-for-registration-ceremony⑨">registration ceremony</a>.</p>
     <li data-md>
-     <p>Verify that the <code><a data-link-type="dfn" href="#authdata-attestedcredentialdata-credentialid" id="ref-for-authdata-attestedcredentialdata-credentialid⑤">credentialId</a></code> is not yet registered for any user. If the <code><a data-link-type="dfn" href="#authdata-attestedcredentialdata-credentialid" id="ref-for-authdata-attestedcredentialdata-credentialid⑥">credentialId</a></code> is already known then the <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party②③③">Relying Party</a> SHOULD fail this <a data-link-type="dfn" href="#registration-ceremony" id="ref-for-registration-ceremony①⓪">registration ceremony</a>.</p>
-     <p class="note" role="note"><span>NOTE:</span> The rationale for <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party②③④">Relying Parties</a> rejecting duplicate <a data-link-type="dfn" href="#credential-id" id="ref-for-credential-id③①">credential IDs</a> is as follows: <a data-link-type="dfn" href="#credential-id" id="ref-for-credential-id③②">credential IDs</a> contain sufficient entropy that accidental duplication is very unlikely. However, <a data-link-type="dfn" href="#attestation-type" id="ref-for-attestation-type①⑥">attestation types</a> other than <a data-link-type="dfn" href="#self-attestation" id="ref-for-self-attestation①⑤">self attestation</a> do not include a self-signature to explicitly prove possession of the <a data-link-type="dfn" href="#credential-private-key" id="ref-for-credential-private-key②⓪">credential private key</a> at <a data-link-type="dfn" href="#registration" id="ref-for-registration①⑦">registration</a> time. Thus an attacker who has managed to obtain a user’s <a data-link-type="dfn" href="#credential-id" id="ref-for-credential-id③③">credential ID</a> and <a data-link-type="dfn" href="#credential-public-key" id="ref-for-credential-public-key②⑨">credential public key</a> for a site (this could be potentially accomplished in various ways), could attempt to register a victim’s credential as their own at that site. If the <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party②③⑤">Relying Party</a> accepts this new registration and replaces the victim’s existing credential registration, and the <a data-link-type="dfn" href="#discoverable-credential" id="ref-for-discoverable-credential①①">credentials are discoverable</a>, then the victim could be forced to sign into the attacker’s account at their next attempt. Data saved to the site by the victim in that state would then be available to the attacker.</p>
+     <p>Verify that the <code><a data-link-type="dfn" href="#authdata-attestedcredentialdata-credentialid" id="ref-for-authdata-attestedcredentialdata-credentialid⑤">credentialId</a></code> is not yet registered for any user. If the <code><a data-link-type="dfn" href="#authdata-attestedcredentialdata-credentialid" id="ref-for-authdata-attestedcredentialdata-credentialid⑥">credentialId</a></code> is already known then the <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party②③⑧">Relying Party</a> SHOULD fail this <a data-link-type="dfn" href="#registration-ceremony" id="ref-for-registration-ceremony①⓪">registration ceremony</a>.</p>
+     <p class="note" role="note"><span>NOTE:</span> The rationale for <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party②③⑨">Relying Parties</a> rejecting duplicate <a data-link-type="dfn" href="#credential-id" id="ref-for-credential-id③②">credential IDs</a> is as follows: <a data-link-type="dfn" href="#credential-id" id="ref-for-credential-id③③">credential IDs</a> contain sufficient entropy that accidental duplication is very unlikely. However, <a data-link-type="dfn" href="#attestation-type" id="ref-for-attestation-type①⑥">attestation types</a> other than <a data-link-type="dfn" href="#self-attestation" id="ref-for-self-attestation①⑤">self attestation</a> do not include a self-signature to explicitly prove possession of the <a data-link-type="dfn" href="#credential-private-key" id="ref-for-credential-private-key②⓪">credential private key</a> at <a data-link-type="dfn" href="#registration" id="ref-for-registration②⓪">registration</a> time. Thus an attacker who has managed to obtain a user’s <a data-link-type="dfn" href="#credential-id" id="ref-for-credential-id③④">credential ID</a> and <a data-link-type="dfn" href="#credential-public-key" id="ref-for-credential-public-key③⓪">credential public key</a> for a site (this could be potentially accomplished in various ways), could attempt to register a victim’s credential as their own at that site. If the <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party②④⓪">Relying Party</a> accepts this new registration and replaces the victim’s existing credential registration, and the <a data-link-type="dfn" href="#discoverable-credential" id="ref-for-discoverable-credential①①">credentials are discoverable</a>, then the victim could be forced to sign into the attacker’s account at their next attempt. Data saved to the site by the victim in that state would then be available to the attacker.</p>
     <li data-md>
-     <p>If the attestation statement <var>attStmt</var> verified successfully and is found to be trustworthy, then register the new
-credential with the <a data-link-type="dfn" href="#user-account" id="ref-for-user-account②⑨">user account</a> that was denoted in <code><var>options</var>.<code class="idl"><a data-link-type="idl" href="#dom-publickeycredentialcreationoptions-user" id="ref-for-dom-publickeycredentialcreationoptions-user⑥">user</a></code></code>:</p>
-     <ul>
-      <li data-md>
-       <p>Associate the <a data-link-type="dfn" href="#user-account" id="ref-for-user-account③⓪">user account</a> with the <code><a data-link-type="dfn" href="#authdata-attestedcredentialdata-credentialid" id="ref-for-authdata-attestedcredentialdata-credentialid⑦">credentialId</a></code> and <code><a data-link-type="dfn" href="#authdata-attestedcredentialdata-credentialpublickey" id="ref-for-authdata-attestedcredentialdata-credentialpublickey⑥">credentialPublicKey</a></code> in <code><var>authData</var>.<a data-link-type="dfn" href="#authdata-attestedcredentialdata" id="ref-for-authdata-attestedcredentialdata⑧">attestedCredentialData</a></code>, as appropriate for the <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party②③⑥">Relying Party</a>'s system.</p>
-      <li data-md>
-       <p>Associate the <code><a data-link-type="dfn" href="#authdata-attestedcredentialdata-credentialid" id="ref-for-authdata-attestedcredentialdata-credentialid⑧">credentialId</a></code> with a new stored <a data-link-type="dfn" href="#signature-counter" id="ref-for-signature-counter②④">signature counter</a> value
-initialized to the value of <code><var>authData</var>.<a data-link-type="dfn" href="#authdata-signcount" id="ref-for-authdata-signcount④">signCount</a></code>.</p>
-     </ul>
-     <p>It is RECOMMENDED to also:</p>
-     <ul>
-      <li data-md>
-       <p>Associate the <code><a data-link-type="dfn" href="#authdata-attestedcredentialdata-credentialid" id="ref-for-authdata-attestedcredentialdata-credentialid⑨">credentialId</a></code> with the transport hints
-returned by calling <code><var>credential</var>.<code class="idl"><a data-link-type="idl" href="#dom-publickeycredential-response" id="ref-for-dom-publickeycredential-response⑥">response</a></code>.<code class="idl"><a data-link-type="idl" href="#dom-authenticatorattestationresponse-gettransports" id="ref-for-dom-authenticatorattestationresponse-gettransports⑤">getTransports()</a></code></code>.
-This value SHOULD NOT be modified before or after storing it.
-It is RECOMMENDED to use this value to populate the <code class="idl"><a data-link-type="idl" href="#dom-publickeycredentialdescriptor-transports" id="ref-for-dom-publickeycredentialdescriptor-transports①①">transports</a></code> of the <code class="idl"><a data-link-type="idl" href="#dom-publickeycredentialrequestoptions-allowcredentials" id="ref-for-dom-publickeycredentialrequestoptions-allowcredentials①⑤">allowCredentials</a></code> option in future <code class="idl"><a data-link-type="idl" href="https://w3c.github.io/webappsec-credential-management/#dom-credentialscontainer-get" id="ref-for-dom-credentialscontainer-get②⑨">get()</a></code> calls
-to help the <a data-link-type="dfn" href="#client" id="ref-for-client⑧①">client</a> know how to find a suitable <a data-link-type="dfn" href="#authenticator" id="ref-for-authenticator②①⑦">authenticator</a>.</p>
-     </ul>
+     <p>If the attestation statement <var>attStmt</var> verified successfully and is found to be trustworthy,
+then create and store a new <a data-link-type="dfn" href="#credential-record" id="ref-for-credential-record⑥">credential record</a> in the <a data-link-type="dfn" href="#user-account" id="ref-for-user-account③①">user account</a> that was denoted in <code><var>options</var>.<code class="idl"><a data-link-type="idl" href="#dom-publickeycredentialcreationoptions-user" id="ref-for-dom-publickeycredentialcreationoptions-user⑥">user</a></code></code>,
+with the following contents:</p>
+     <dl>
+      <dt data-md><a data-link-type="dfn" href="#credential-record-type" id="ref-for-credential-record-type①">type</a>
+      <dd data-md>
+       <p><code><var>credential</var>.<code class="idl"><a data-link-type="idl" href="https://w3c.github.io/webappsec-credential-management/#dom-credential-type" id="ref-for-dom-credential-type②">type</a></code></code>.</p>
+      <dt data-md><a data-link-type="dfn" href="#credential-record-id" id="ref-for-credential-record-id①">id</a>
+      <dd data-md>
+       <p><code><var>credential</var>.<code class="idl"><a data-link-type="idl" href="https://w3c.github.io/webappsec-credential-management/#dom-credential-id" id="ref-for-dom-credential-id①">id</a></code></code> or <code><var>credential</var>.<code class="idl"><a data-link-type="idl" href="#dom-publickeycredential-rawid" id="ref-for-dom-publickeycredential-rawid②">rawId</a></code></code>,
+whichever format is preferred by the <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party②④①">Relying Party</a>.</p>
+      <dt data-md><a data-link-type="dfn" href="#credential-record-publickey" id="ref-for-credential-record-publickey">publicKey</a>
+      <dd data-md>
+       <p>The <a data-link-type="dfn" href="#credential-public-key" id="ref-for-credential-public-key③①">credential public key</a> in <var>authData</var>.</p>
+      <dt data-md><a data-link-type="dfn" href="#credential-record-signcount" id="ref-for-credential-record-signcount">signCount</a>
+      <dd data-md>
+       <p><code><var>authData</var>.<a data-link-type="dfn" href="#authdata-signcount" id="ref-for-authdata-signcount⑤">signCount</a></code>.</p>
+      <dt data-md><a data-link-type="dfn" href="#credential-record-transports" id="ref-for-credential-record-transports①">transports</a>
+      <dd data-md>
+       <p>The value returned from <code><var>response</var>.<code class="idl"><a data-link-type="idl" href="#dom-authenticatorattestationresponse-gettransports" id="ref-for-dom-authenticatorattestationresponse-gettransports⑦">getTransports()</a></code></code>.</p>
+      <dt data-md><a data-link-type="dfn" href="#credential-record-be" id="ref-for-credential-record-be">BE</a>
+      <dd data-md>
+       <p>The value of the <a data-link-type="dfn" href="#authdata-flags-be" id="ref-for-authdata-flags-be⑦">BE</a> <a data-link-type="dfn" href="#authdata-flags" id="ref-for-authdata-flags③④">flag</a> in <var>authData</var>.</p>
+      <dt data-md><a data-link-type="dfn" href="#credential-record-bs" id="ref-for-credential-record-bs">BS</a>
+      <dd data-md>
+       <p>The value of the <a data-link-type="dfn" href="#authdata-flags-bs" id="ref-for-authdata-flags-bs⑧">BS</a> <a data-link-type="dfn" href="#authdata-flags" id="ref-for-authdata-flags③⑤">flag</a> in <var>authData</var>.</p>
+     </dl>
+     <p>The new <a data-link-type="dfn" href="#credential-record" id="ref-for-credential-record⑦">credential record</a> MAY also include the following OPTIONAL contents:</p>
+     <dl>
+      <dt data-md><a data-link-type="dfn" href="#credential-record-attestationobject" id="ref-for-credential-record-attestationobject①">attestationObject</a>
+      <dd data-md>
+       <p><code><var>response</var>.<code class="idl"><a data-link-type="idl" href="#dom-authenticatorattestationresponse-attestationobject" id="ref-for-dom-authenticatorattestationresponse-attestationobject⑧">attestationObject</a></code></code>.</p>
+      <dt data-md><a data-link-type="dfn" href="#credential-record-attestationclientdatajson" id="ref-for-credential-record-attestationclientdatajson">attestationClientDataJSON</a>
+      <dd data-md>
+       <p><code><var>response</var>.<code class="idl"><a data-link-type="idl" href="#dom-authenticatorresponse-clientdatajson" id="ref-for-dom-authenticatorresponse-clientdatajson⑨">clientDataJSON</a></code></code>.</p>
+     </dl>
     <li data-md>
-     <p>If the attestation statement <var>attStmt</var> successfully verified but is not trustworthy per step 20 above, the <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party②③⑦">Relying Party</a> SHOULD fail
+     <p>If the attestation statement <var>attStmt</var> successfully verified but is not trustworthy per step 20 above, the <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party②④②">Relying Party</a> SHOULD fail
 the <a data-link-type="dfn" href="#registration-ceremony" id="ref-for-registration-ceremony①①">registration ceremony</a>.</p>
-     <p class="note" role="note"><span>NOTE:</span> However, if permitted by policy, the <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party②③⑧">Relying Party</a> MAY register the <a data-link-type="dfn" href="#credential-id" id="ref-for-credential-id③④">credential ID</a> and credential public key but treat the
-    credential as one with <a data-link-type="dfn" href="#self-attestation" id="ref-for-self-attestation①⑥">self attestation</a> (see <a href="#sctn-attestation-types">§ 6.5.3 Attestation Types</a>). If doing so, the <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party②③⑨">Relying Party</a> is asserting there
-    is no cryptographic proof that the <a data-link-type="dfn" href="#public-key-credential" id="ref-for-public-key-credential⑤③">public key credential</a> has been generated by a particular <a data-link-type="dfn" href="#authenticator" id="ref-for-authenticator②①⑧">authenticator</a> model.
+     <p class="note" role="note"><span>NOTE:</span> However, if permitted by policy, the <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party②④③">Relying Party</a> MAY register the <a data-link-type="dfn" href="#credential-id" id="ref-for-credential-id③⑤">credential ID</a> and credential public key but treat the
+    credential as one with <a data-link-type="dfn" href="#self-attestation" id="ref-for-self-attestation①⑥">self attestation</a> (see <a href="#sctn-attestation-types">§ 6.5.3 Attestation Types</a>). If doing so, the <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party②④④">Relying Party</a> is asserting there
+    is no cryptographic proof that the <a data-link-type="dfn" href="#public-key-credential" id="ref-for-public-key-credential⑤③">public key credential</a> has been generated by a particular <a data-link-type="dfn" href="#authenticator" id="ref-for-authenticator②①⑦">authenticator</a> model.
     See <a data-link-type="biblio" href="#biblio-fidosecref">[FIDOSecRef]</a> and <a data-link-type="biblio" href="#biblio-uafprotocol">[UAFProtocol]</a> for a more detailed discussion.</p>
    </ol>
-   <p>Verification of <a data-link-type="dfn" href="#attestation-object" id="ref-for-attestation-object①⑥">attestation objects</a> requires that the <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party②④⓪">Relying Party</a> has a trusted method of determining acceptable trust anchors
-in step 19 above. Also, if certificates are being used, the <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party②④①">Relying Party</a> MUST have access to certificate status information for the
-intermediate CA certificates. The <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party②④②">Relying Party</a> MUST also be able to build the attestation certificate chain if the client did not
+   <p>Verification of <a data-link-type="dfn" href="#attestation-object" id="ref-for-attestation-object①⑥">attestation objects</a> requires that the <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party②④⑤">Relying Party</a> has a trusted method of determining acceptable trust anchors
+in step 19 above. Also, if certificates are being used, the <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party②④⑥">Relying Party</a> MUST have access to certificate status information for the
+intermediate CA certificates. The <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party②④⑦">Relying Party</a> MUST also be able to build the attestation certificate chain if the client did not
 provide this chain in the attestation information.</p>
    <h3 class="heading settled" data-level="7.2" id="sctn-verifying-assertion"><span class="secno">7.2. </span><span class="content">Verifying an Authentication Assertion</span><a class="self-link" href="#sctn-verifying-assertion"></a></h3>
-   <p>In order to perform an <a data-link-type="dfn" href="#authentication-ceremony" id="ref-for-authentication-ceremony②①">authentication ceremony</a>, the <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party②④③">Relying Party</a> MUST proceed as follows:</p>
+   <p>In order to perform an <a data-link-type="dfn" href="#authentication-ceremony" id="ref-for-authentication-ceremony②①">authentication ceremony</a>, the <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party②④⑧">Relying Party</a> MUST proceed as follows:</p>
    <ol>
     <li data-md>
-     <p>Let <var>options</var> be a new <code class="idl"><a data-link-type="idl" href="#dictdef-publickeycredentialrequestoptions" id="ref-for-dictdef-publickeycredentialrequestoptions①②">PublicKeyCredentialRequestOptions</a></code> structure configured to the <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party②④④">Relying Party</a>'s needs for the ceremony.</p>
-     <p>If <code><var>options</var>.<code class="idl"><a data-link-type="idl" href="#dom-publickeycredentialrequestoptions-allowcredentials" id="ref-for-dom-publickeycredentialrequestoptions-allowcredentials①⑥">allowCredentials</a></code></code> is present,
-the <code class="idl"><a data-link-type="idl" href="#dom-publickeycredentialdescriptor-transports" id="ref-for-dom-publickeycredentialdescriptor-transports①②">transports</a></code> member of each <a data-link-type="dfn" href="https://infra.spec.whatwg.org/#list-item" id="ref-for-list-item①②">item</a> SHOULD be set to
-the value that was returned by <code><var>credential</var>.<code class="idl"><a data-link-type="idl" href="#dom-publickeycredential-response" id="ref-for-dom-publickeycredential-response⑦">response</a></code>.<code class="idl"><a data-link-type="idl" href="#dom-authenticatorattestationresponse-gettransports" id="ref-for-dom-authenticatorattestationresponse-gettransports⑥">getTransports()</a></code></code> when the corresponding credential was registered.</p>
-     <p class="note" role="note"><span>Note:</span> Modifying or removing <a data-link-type="dfn" href="https://infra.spec.whatwg.org/#list-item" id="ref-for-list-item①③">items</a> from values returned from <code class="idl"><a data-link-type="idl" href="#dom-authenticatorattestationresponse-gettransports" id="ref-for-dom-authenticatorattestationresponse-gettransports⑦">getTransports()</a></code> could negatively impact user experience, or even prevent use of the corresponding credentials.</p>
+     <p>Let <var>options</var> be a new <code class="idl"><a data-link-type="idl" href="#dictdef-publickeycredentialrequestoptions" id="ref-for-dictdef-publickeycredentialrequestoptions①②">PublicKeyCredentialRequestOptions</a></code> structure configured to the <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party②④⑨">Relying Party</a>'s needs for the ceremony.</p>
     <li data-md>
-     <p>Call <code class="idl"><a data-link-type="idl" href="https://w3c.github.io/webappsec-credential-management/#dom-credentialscontainer-get" id="ref-for-dom-credentialscontainer-get③⓪">navigator.credentials.get()</a></code> and pass <var>options</var> as the <code><code class="idl"><a data-link-type="idl" href="#dom-credentialrequestoptions-publickey" id="ref-for-dom-credentialrequestoptions-publickey⑥">publicKey</a></code></code> option.
+     <p>Call <code class="idl"><a data-link-type="idl" href="https://w3c.github.io/webappsec-credential-management/#dom-credentialscontainer-get" id="ref-for-dom-credentialscontainer-get②⑨">navigator.credentials.get()</a></code> and pass <var>options</var> as the <code><code class="idl"><a data-link-type="idl" href="#dom-credentialrequestoptions-publickey" id="ref-for-dom-credentialrequestoptions-publickey⑥">publicKey</a></code></code> option.
 Let <var>credential</var> be the result of the successfully resolved promise.
 If the promise is rejected, abort the ceremony with a user-visible error, or otherwise guide the user experience as might
 be determinable from the context available in the rejected promise. For information on different error contexts and the
 circumstances leading to them, see <a href="#sctn-op-get-assertion">§ 6.3.3 The authenticatorGetAssertion Operation</a>.</p>
     <li data-md>
-     <p>Let <var>response</var> be <code><var>credential</var>.<code class="idl"><a data-link-type="idl" href="#dom-publickeycredential-response" id="ref-for-dom-publickeycredential-response⑧">response</a></code></code>.
+     <p>Let <var>response</var> be <code><var>credential</var>.<code class="idl"><a data-link-type="idl" href="#dom-publickeycredential-response" id="ref-for-dom-publickeycredential-response⑥">response</a></code></code>.
 If <var>response</var> is not an instance of <code class="idl"><a data-link-type="idl" href="#authenticatorassertionresponse" id="ref-for-authenticatorassertionresponse⑦">AuthenticatorAssertionResponse</a></code>, abort the ceremony with a user-visible error.</p>
     <li data-md>
      <p>Let <var>clientExtensionResults</var> be the result of calling <code><var>credential</var>.<code class="idl"><a data-link-type="idl" href="#dom-publickeycredential-getclientextensionresults" id="ref-for-dom-publickeycredential-getclientextensionresults③">getClientExtensionResults()</a></code></code>.</p>
     <li data-md>
-     <p>If <code><var>options</var>.<code class="idl"><a data-link-type="idl" href="#dom-publickeycredentialrequestoptions-allowcredentials" id="ref-for-dom-publickeycredentialrequestoptions-allowcredentials①⑦">allowCredentials</a></code></code> <a data-link-type="dfn" href="https://infra.spec.whatwg.org/#list-is-empty" id="ref-for-list-is-empty⑨">is not empty</a>,
-verify that <code><var>credential</var>.<code class="idl"><a data-link-type="idl" href="https://w3c.github.io/webappsec-credential-management/#dom-credential-id" id="ref-for-dom-credential-id①">id</a></code></code> identifies one of the <a data-link-type="dfn" href="#public-key-credential" id="ref-for-public-key-credential⑤④">public key credentials</a> listed in <code><var>options</var>.<code class="idl"><a data-link-type="idl" href="#dom-publickeycredentialrequestoptions-allowcredentials" id="ref-for-dom-publickeycredentialrequestoptions-allowcredentials①⑧">allowCredentials</a></code></code>.</p>
+     <p>If <code><var>options</var>.<code class="idl"><a data-link-type="idl" href="#dom-publickeycredentialrequestoptions-allowcredentials" id="ref-for-dom-publickeycredentialrequestoptions-allowcredentials①⑤">allowCredentials</a></code></code> <a data-link-type="dfn" href="https://infra.spec.whatwg.org/#list-is-empty" id="ref-for-list-is-empty⑨">is not empty</a>,
+verify that <code><var>credential</var>.<code class="idl"><a data-link-type="idl" href="https://w3c.github.io/webappsec-credential-management/#dom-credential-id" id="ref-for-dom-credential-id②">id</a></code></code> identifies one of the <a data-link-type="dfn" href="#public-key-credential" id="ref-for-public-key-credential⑤④">public key credentials</a> listed in <code><var>options</var>.<code class="idl"><a data-link-type="idl" href="#dom-publickeycredentialrequestoptions-allowcredentials" id="ref-for-dom-publickeycredentialrequestoptions-allowcredentials①⑥">allowCredentials</a></code></code>.</p>
     <li data-md>
-     <p>Identify the user being authenticated and verify that this user is the owner of the <a data-link-type="dfn" href="#public-key-credential-source" id="ref-for-public-key-credential-source④⑦">public key credential source</a> <var>credentialSource</var> identified by <code><var>credential</var>.<code class="idl"><a data-link-type="idl" href="https://w3c.github.io/webappsec-credential-management/#dom-credential-id" id="ref-for-dom-credential-id②">id</a></code></code>:</p>
+     <p>Identify the user being authenticated and let <var>credentialRecord</var> be the <a data-link-type="dfn" href="#credential-record" id="ref-for-credential-record⑧">credential record</a> for the <a data-link-type="dfn" href="https://w3c.github.io/webappsec-credential-management/#concept-credential" id="ref-for-concept-credential①⑦">credential</a>:</p>
      <dl class="switch">
       <dt data-md>If the user was identified before the <a data-link-type="dfn" href="#authentication-ceremony" id="ref-for-authentication-ceremony②②">authentication ceremony</a> was initiated, e.g., via a username or cookie,
       <dd data-md>
-       <p>verify that the identified user is the owner of <var>credentialSource</var>. If <code><var>response</var>.<code class="idl"><a data-link-type="idl" href="#dom-authenticatorassertionresponse-userhandle" id="ref-for-dom-authenticatorassertionresponse-userhandle⑥">userHandle</a></code></code> is present,
-let <var>userHandle</var> be its value. Verify that <var>userHandle</var> also maps to the same user.</p>
+       <p>verify that the identified <a data-link-type="dfn" href="#user-account" id="ref-for-user-account③②">user account</a> contains a <a data-link-type="dfn" href="#credential-record" id="ref-for-credential-record⑨">credential record</a> whose <a data-link-type="dfn" href="#credential-record-id" id="ref-for-credential-record-id②">id</a> equals <code><var>credential</var>.<code class="idl"><a data-link-type="idl" href="#dom-publickeycredential-rawid" id="ref-for-dom-publickeycredential-rawid③">rawId</a></code></code>.
+Let <var>credentialRecord</var> be that <a data-link-type="dfn" href="#credential-record" id="ref-for-credential-record①⓪">credential record</a>.
+If <code><var>response</var>.<code class="idl"><a data-link-type="idl" href="#dom-authenticatorassertionresponse-userhandle" id="ref-for-dom-authenticatorassertionresponse-userhandle⑥">userHandle</a></code></code> is present,
+verify that it equals the <a data-link-type="dfn" href="#user-handle" id="ref-for-user-handle②①">user handle</a> of the <a data-link-type="dfn" href="#user-account" id="ref-for-user-account③③">user account</a>.</p>
       <dt data-md>If the user was not identified before the <a data-link-type="dfn" href="#authentication-ceremony" id="ref-for-authentication-ceremony②③">authentication ceremony</a> was initiated,
       <dd data-md>
-       <p>verify that <code><var>response</var>.<code class="idl"><a data-link-type="idl" href="#dom-authenticatorassertionresponse-userhandle" id="ref-for-dom-authenticatorassertionresponse-userhandle⑦">userHandle</a></code></code> is
-present, and that the user identified by this value is the owner of <var>credentialSource</var>.</p>
+       <p>verify that <code><var>response</var>.<code class="idl"><a data-link-type="idl" href="#dom-authenticatorassertionresponse-userhandle" id="ref-for-dom-authenticatorassertionresponse-userhandle⑦">userHandle</a></code></code> is present.
+Verify that the <a data-link-type="dfn" href="#user-account" id="ref-for-user-account③④">user account</a> identified by <code><var>response</var>.<code class="idl"><a data-link-type="idl" href="#dom-authenticatorassertionresponse-userhandle" id="ref-for-dom-authenticatorassertionresponse-userhandle⑧">userHandle</a></code></code> contains a <a data-link-type="dfn" href="#credential-record" id="ref-for-credential-record①①">credential record</a> whose <a data-link-type="dfn" href="#credential-record-id" id="ref-for-credential-record-id③">id</a> equals <code><var>credential</var>.<code class="idl"><a data-link-type="idl" href="#dom-publickeycredential-rawid" id="ref-for-dom-publickeycredential-rawid④">rawId</a></code></code>.
+Let <var>credentialRecord</var> be that <a data-link-type="dfn" href="#credential-record" id="ref-for-credential-record①②">credential record</a>.</p>
      </dl>
     <li data-md>
-     <p>Using <code><var>credential</var>.<code class="idl"><a data-link-type="idl" href="https://w3c.github.io/webappsec-credential-management/#dom-credential-id" id="ref-for-dom-credential-id③">id</a></code></code> (or <code><var>credential</var>.<code class="idl"><a data-link-type="idl" href="#dom-publickeycredential-rawid" id="ref-for-dom-publickeycredential-rawid②">rawId</a></code></code>, if <a data-link-type="dfn" href="#base64url-encoding" id="ref-for-base64url-encoding①③">base64url encoding</a> is inappropriate for your use case), look up the corresponding <a data-link-type="dfn" href="#credential-public-key" id="ref-for-credential-public-key③⓪">credential public key</a> and let <var>credentialPublicKey</var> be that <a data-link-type="dfn" href="#credential-public-key" id="ref-for-credential-public-key③①">credential public key</a>.</p>
-    <li data-md>
-     <p>Let <var>cData</var>, <var>authData</var> and <var>sig</var> denote the value of <var>response</var>’s <code class="idl"><a data-link-type="idl" href="#dom-authenticatorresponse-clientdatajson" id="ref-for-dom-authenticatorresponse-clientdatajson⑧">clientDataJSON</a></code>, <code class="idl"><a data-link-type="idl" href="#dom-authenticatorassertionresponse-authenticatordata" id="ref-for-dom-authenticatorassertionresponse-authenticatordata②">authenticatorData</a></code>, and <code class="idl"><a data-link-type="idl" href="#dom-authenticatorassertionresponse-signature" id="ref-for-dom-authenticatorassertionresponse-signature②">signature</a></code> respectively.</p>
+     <p>Let <var>cData</var>, <var>authData</var> and <var>sig</var> denote the value of <var>response</var>’s <code class="idl"><a data-link-type="idl" href="#dom-authenticatorresponse-clientdatajson" id="ref-for-dom-authenticatorresponse-clientdatajson①⓪">clientDataJSON</a></code>, <code class="idl"><a data-link-type="idl" href="#dom-authenticatorassertionresponse-authenticatordata" id="ref-for-dom-authenticatorassertionresponse-authenticatordata②">authenticatorData</a></code>, and <code class="idl"><a data-link-type="idl" href="#dom-authenticatorassertionresponse-signature" id="ref-for-dom-authenticatorassertionresponse-signature②">signature</a></code> respectively.</p>
     <li data-md>
      <p>Let <var>JSONtext</var> be the result of running <a data-link-type="dfn" href="https://encoding.spec.whatwg.org/#utf-8-decode" id="ref-for-utf-8-decode③">UTF-8 decode</a> on the value of <var>cData</var>.</p>
      <p class="note" role="note"><span>Note:</span> Using any implementation of <a data-link-type="dfn" href="https://encoding.spec.whatwg.org/#utf-8-decode" id="ref-for-utf-8-decode④">UTF-8 decode</a> is acceptable as long as it yields the same result as that yielded by
@@ -5259,49 +5332,54 @@ <h3 class="heading settled" data-level="7.2" id="sctn-verifying-assertion"><span
     <li data-md>
      <p>Verify that the value of <code><var>C</var>.<code class="idl"><a data-link-type="idl" href="#dom-collectedclientdata-challenge" id="ref-for-dom-collectedclientdata-challenge⑦">challenge</a></code></code> equals
 the base64url encoding of <code><var>options</var>.<code class="idl"><a data-link-type="idl" href="#dom-publickeycredentialrequestoptions-challenge" id="ref-for-dom-publickeycredentialrequestoptions-challenge③">challenge</a></code></code>.</p>
-    <li id="rp-op-verifying-assertion-step-origin"><a class="self-link" href="#rp-op-verifying-assertion-step-origin"></a> Verify that the value of <code><var>C</var>.<code class="idl"><a data-link-type="idl" href="#dom-collectedclientdata-origin" id="ref-for-dom-collectedclientdata-origin⑧">origin</a></code></code> matches the <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party②④⑤">Relying Party</a>'s <a data-link-type="dfn" href="https://html.spec.whatwg.org/multipage/origin.html#concept-origin" id="ref-for-concept-origin①④">origin</a>. 
+    <li id="rp-op-verifying-assertion-step-origin"><a class="self-link" href="#rp-op-verifying-assertion-step-origin"></a> Verify that the value of <code><var>C</var>.<code class="idl"><a data-link-type="idl" href="#dom-collectedclientdata-origin" id="ref-for-dom-collectedclientdata-origin⑧">origin</a></code></code> matches the <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party②⑤⓪">Relying Party</a>'s <a data-link-type="dfn" href="https://html.spec.whatwg.org/multipage/origin.html#concept-origin" id="ref-for-concept-origin①④">origin</a>. 
     <li id="rp-op-verifying-assertion-step-rpid-hash">
-     <a class="self-link" href="#rp-op-verifying-assertion-step-rpid-hash"></a> Verify that the <code><a data-link-type="dfn" href="#authdata-rpidhash" id="ref-for-authdata-rpidhash③">rpIdHash</a></code> in <var>authData</var> is the SHA-256 hash of the <a data-link-type="dfn" href="#rp-id" id="ref-for-rp-id③⑧">RP ID</a> expected by the <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party②④⑥">Relying Party</a>. 
+     <a class="self-link" href="#rp-op-verifying-assertion-step-rpid-hash"></a> Verify that the <code><a data-link-type="dfn" href="#authdata-rpidhash" id="ref-for-authdata-rpidhash③">rpIdHash</a></code> in <var>authData</var> is the SHA-256 hash of the <a data-link-type="dfn" href="#rp-id" id="ref-for-rp-id③⑧">RP ID</a> expected by the <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party②⑤①">Relying Party</a>. 
      <p class="note" role="note"><span>Note:</span> If using the <a data-link-type="dfn" href="#appid" id="ref-for-appid①">appid</a> extension, this step needs some special logic. See <a href="#sctn-appid-extension">§ 10.1.1 FIDO AppID Extension (appid)</a> for details.</p>
     <li data-md>
-     <p>Verify that the <a data-link-type="dfn" href="#authdata-flags-up" id="ref-for-authdata-flags-up④">UP</a> bit of the <code><a data-link-type="dfn" href="#authdata-flags" id="ref-for-authdata-flags③②">flags</a></code> in <var>authData</var> is set.</p>
+     <p>Verify that the <a data-link-type="dfn" href="#authdata-flags-up" id="ref-for-authdata-flags-up④">UP</a> bit of the <code><a data-link-type="dfn" href="#authdata-flags" id="ref-for-authdata-flags③⑥">flags</a></code> in <var>authData</var> is set.</p>
     <li data-md>
-     <p>If the <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party②④⑦">Relying Party</a> requires <a data-link-type="dfn" href="#user-verification" id="ref-for-user-verification④②">user verification</a> for this assertion,
-verify that the <a data-link-type="dfn" href="#authdata-flags-uv" id="ref-for-authdata-flags-uv⑧">UV</a> bit of the <code><a data-link-type="dfn" href="#authdata-flags" id="ref-for-authdata-flags③③">flags</a></code> in <var>authData</var> is set.</p>
+     <p>If the <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party②⑤②">Relying Party</a> requires <a data-link-type="dfn" href="#user-verification" id="ref-for-user-verification④②">user verification</a> for this assertion,
+verify that the <a data-link-type="dfn" href="#authdata-flags-uv" id="ref-for-authdata-flags-uv⑧">UV</a> bit of the <code><a data-link-type="dfn" href="#authdata-flags" id="ref-for-authdata-flags③⑦">flags</a></code> in <var>authData</var> is set.</p>
     <li data-md>
-     <p>If the credential <a data-link-type="dfn" href="#backup-state" id="ref-for-backup-state④">backup state</a> is used as part of <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party②④⑧">Relying Party</a> business logic or policy, compare the previously stored
-value with the <a data-link-type="dfn" href="#authdata-flags-bs" id="ref-for-authdata-flags-bs⑦">BS</a> bit of the <code><a data-link-type="dfn" href="#authdata-flags" id="ref-for-authdata-flags③④">flags</a></code> in <var>authData</var>, perform evaluation, and then store the new value.</p>
+     <p>If the credential <a data-link-type="dfn" href="#backup-state" id="ref-for-backup-state④">backup state</a> is used as part of <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party②⑤③">Relying Party</a> business logic or policy,
+let <var>currentBe</var> and <var>currentBs</var> be the values of the <a data-link-type="dfn" href="#authdata-flags-be" id="ref-for-authdata-flags-be⑧">BE</a> and <a data-link-type="dfn" href="#authdata-flags-bs" id="ref-for-authdata-flags-bs⑨">BS</a> bits, respectively,
+of the <code><a data-link-type="dfn" href="#authdata-flags" id="ref-for-authdata-flags③⑧">flags</a></code> in <var>authData</var>.
+Compare <var>currentBe</var> and <var>currentBs</var> with <code><var>credentialRecord</var>.<a data-link-type="dfn" href="#credential-record-be" id="ref-for-credential-record-be①">BE</a></code> and <code><var>credentialRecord</var>.<a data-link-type="dfn" href="#credential-record-bs" id="ref-for-credential-record-bs①">BS</a></code> and apply <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party②⑤④">Relying Party</a> policy, if any,
+and then update <code><var>credentialRecord</var>.<a data-link-type="dfn" href="#credential-record-bs" id="ref-for-credential-record-bs②">BS</a></code> to the value of <var>currentBs</var>.</p>
+     <p class="note" role="note"><span>Note:</span> See <a href="#sctn-credential-backup">§ 6.1.3 Credential Backup State</a> for examples of how a <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party②⑤⑤">Relying Party</a> might process the <a data-link-type="dfn" href="#authdata-flags-bs" id="ref-for-authdata-flags-bs①⓪">BS</a> <a data-link-type="dfn" href="#authdata-flags" id="ref-for-authdata-flags③⑨">flag</a> values.</p>
     <li data-md>
      <p>Verify that the values of the <a data-link-type="dfn" href="#client-extension-output" id="ref-for-client-extension-output⑧">client extension outputs</a> in <var>clientExtensionResults</var> and the <a data-link-type="dfn" href="#authenticator-extension-output" id="ref-for-authenticator-extension-output⑤">authenticator extension
 outputs</a> in the <code><a data-link-type="dfn" href="#authdata-extensions" id="ref-for-authdata-extensions⑧">extensions</a></code> in <var>authData</var> are as expected, considering the <a data-link-type="dfn" href="#client-extension-input" id="ref-for-client-extension-input⑥">client
-extension input</a> values that were given in <code><var>options</var>.<code class="idl"><a data-link-type="idl" href="#dom-publickeycredentialrequestoptions-extensions" id="ref-for-dom-publickeycredentialrequestoptions-extensions④">extensions</a></code></code> and any specific policy of the <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party②④⑨">Relying Party</a> regarding unsolicited extensions, i.e., those that were not specified as part of <code><var>options</var>.<code class="idl"><a data-link-type="idl" href="#dom-publickeycredentialrequestoptions-extensions" id="ref-for-dom-publickeycredentialrequestoptions-extensions⑤">extensions</a></code></code>.
-In the general case, the meaning of "are as expected" is specific to the <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party②⑤⓪">Relying Party</a> and which extensions are in use.</p>
-     <p class="note" role="note"><span>Note:</span> <a data-link-type="dfn" href="#client-platform" id="ref-for-client-platform④⑦">Client platforms</a> MAY enact local policy that sets additional <a data-link-type="dfn" href="#authenticator-extension" id="ref-for-authenticator-extension④">authenticator extensions</a> or <a data-link-type="dfn" href="#client-extension" id="ref-for-client-extension③">client extensions</a> and thus cause values to appear in the <a data-link-type="dfn" href="#authenticator-extension-output" id="ref-for-authenticator-extension-output⑥">authenticator extension outputs</a> or <a data-link-type="dfn" href="#client-extension-output" id="ref-for-client-extension-output⑨">client extension outputs</a> that were not originally specified as part of <code><var>options</var>.<code class="idl"><a data-link-type="idl" href="#dom-publickeycredentialrequestoptions-extensions" id="ref-for-dom-publickeycredentialrequestoptions-extensions⑥">extensions</a></code></code>. <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party②⑤①">Relying Parties</a> MUST be prepared to handle such
-situations, whether it be to ignore the unsolicited extensions or reject the assertion. The <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party②⑤②">Relying Party</a> can make this
+extension input</a> values that were given in <code><var>options</var>.<code class="idl"><a data-link-type="idl" href="#dom-publickeycredentialrequestoptions-extensions" id="ref-for-dom-publickeycredentialrequestoptions-extensions④">extensions</a></code></code> and any specific policy of the <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party②⑤⑥">Relying Party</a> regarding unsolicited extensions, i.e., those that were not specified as part of <code><var>options</var>.<code class="idl"><a data-link-type="idl" href="#dom-publickeycredentialrequestoptions-extensions" id="ref-for-dom-publickeycredentialrequestoptions-extensions⑤">extensions</a></code></code>.
+In the general case, the meaning of "are as expected" is specific to the <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party②⑤⑦">Relying Party</a> and which extensions are in use.</p>
+     <p class="note" role="note"><span>Note:</span> <a data-link-type="dfn" href="#client-platform" id="ref-for-client-platform④⑦">Client platforms</a> MAY enact local policy that sets additional <a data-link-type="dfn" href="#authenticator-extension" id="ref-for-authenticator-extension④">authenticator extensions</a> or <a data-link-type="dfn" href="#client-extension" id="ref-for-client-extension③">client extensions</a> and thus cause values to appear in the <a data-link-type="dfn" href="#authenticator-extension-output" id="ref-for-authenticator-extension-output⑥">authenticator extension outputs</a> or <a data-link-type="dfn" href="#client-extension-output" id="ref-for-client-extension-output⑨">client extension outputs</a> that were not originally specified as part of <code><var>options</var>.<code class="idl"><a data-link-type="idl" href="#dom-publickeycredentialrequestoptions-extensions" id="ref-for-dom-publickeycredentialrequestoptions-extensions⑥">extensions</a></code></code>. <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party②⑤⑧">Relying Parties</a> MUST be prepared to handle such
+situations, whether it be to ignore the unsolicited extensions or reject the assertion. The <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party②⑤⑨">Relying Party</a> can make this
 decision based on local policy and the extensions in use.</p>
-     <p class="note" role="note"><span>Note:</span> Since all extensions are OPTIONAL for both the <a data-link-type="dfn" href="#client" id="ref-for-client⑧②">client</a> and the <a data-link-type="dfn" href="#authenticator" id="ref-for-authenticator②①⑨">authenticator</a>, the <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party②⑤③">Relying Party</a> MUST also be
+     <p class="note" role="note"><span>Note:</span> Since all extensions are OPTIONAL for both the <a data-link-type="dfn" href="#client" id="ref-for-client⑧①">client</a> and the <a data-link-type="dfn" href="#authenticator" id="ref-for-authenticator②①⑧">authenticator</a>, the <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party②⑥⓪">Relying Party</a> MUST also be
 prepared to handle cases where none or not all of the requested extensions were acted upon.</p>
     <li data-md>
      <p>Let <var>hash</var> be the result of computing a hash over the <var>cData</var> using SHA-256.</p>
     <li data-md>
-     <p>Using <var>credentialPublicKey</var>, verify that <var>sig</var> is a valid signature over the binary concatenation of <var>authData</var> and <var>hash</var>.</p>
+     <p>Using <code><var>credentialRecord</var>.<a data-link-type="dfn" href="#credential-record-publickey" id="ref-for-credential-record-publickey①">publicKey</a></code>,
+verify that <var>sig</var> is a valid signature over the binary concatenation of <var>authData</var> and <var>hash</var>.</p>
      <p class="note" role="note"><span>Note:</span> This verification step is compatible with signatures generated by FIDO U2F authenticators. See <a href="#sctn-fido-u2f-sig-format-compat">§ 6.1.2 FIDO U2F Signature Format Compatibility</a>.</p>
     <li data-md>
-     <p>Let <var>storedSignCount</var> be the stored <a data-link-type="dfn" href="#signature-counter" id="ref-for-signature-counter②⑤">signature counter</a> value associated with <code><var>credential</var>.<code class="idl"><a data-link-type="idl" href="https://w3c.github.io/webappsec-credential-management/#dom-credential-id" id="ref-for-dom-credential-id④">id</a></code></code>.
-If <var>authData</var>.<code><a data-link-type="dfn" href="#authdata-signcount" id="ref-for-authdata-signcount⑤">signCount</a></code> is nonzero or <var>storedSignCount</var> is nonzero,
+     <p>If <var>authData</var>.<code><a data-link-type="dfn" href="#authdata-signcount" id="ref-for-authdata-signcount⑥">signCount</a></code> is nonzero or <code><var>credentialRecord</var>.<a data-link-type="dfn" href="#credential-record-signcount" id="ref-for-credential-record-signcount①">signCount</a></code> is nonzero,
 then run the following sub-step:</p>
      <ul>
       <li data-md>
-       <p>If <var>authData</var>.<code><a data-link-type="dfn" href="#authdata-signcount" id="ref-for-authdata-signcount⑥">signCount</a></code> is</p>
+       <p>If <var>authData</var>.<code><a data-link-type="dfn" href="#authdata-signcount" id="ref-for-authdata-signcount⑦">signCount</a></code> is</p>
        <dl class="switch">
-        <dt>greater than <var>storedSignCount</var>:
-        <dd>Update <var>storedSignCount</var> to be the value of <var>authData</var>.<code><a data-link-type="dfn" href="#authdata-signcount" id="ref-for-authdata-signcount⑦">signCount</a></code>.
-        <dt>less than or equal to <var>storedSignCount</var>:
+        <dt>greater than <code><var>credentialRecord</var>.<a data-link-type="dfn" href="#credential-record-signcount" id="ref-for-credential-record-signcount②">signCount</a></code>:
+        <dd>Update <code><var>credentialRecord</var>.<a data-link-type="dfn" href="#credential-record-signcount" id="ref-for-credential-record-signcount③">signCount</a></code> to be the value of <var>authData</var>.<code><a data-link-type="dfn" href="#authdata-signcount" id="ref-for-authdata-signcount⑧">signCount</a></code>.
+        <dt>less than or equal to <code><var>credentialRecord</var>.<a data-link-type="dfn" href="#credential-record-signcount" id="ref-for-credential-record-signcount④">signCount</a></code>:
         <dd>This is a signal that
           the authenticator may be cloned, i.e. at least
           two copies of the <a data-link-type="dfn" href="#credential-private-key" id="ref-for-credential-private-key②①">credential private key</a> may exist and are
-          being used in parallel. <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party②⑤④">Relying Parties</a> should incorporate this information
-          into their risk scoring.  Whether the <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party②⑤⑤">Relying Party</a> updates <var>storedSignCount</var> in this case, or not, or fails the <a data-link-type="dfn" href="#authentication-ceremony" id="ref-for-authentication-ceremony②④">authentication ceremony</a> or not, is <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party②⑤⑥">Relying Party</a>-specific. 
+          being used in parallel. <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party②⑥①">Relying Parties</a> should incorporate this information
+          into their risk scoring.
+          Whether the <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party②⑥②">Relying Party</a> updates <code><var>credentialRecord</var>.<a data-link-type="dfn" href="#credential-record-signcount" id="ref-for-credential-record-signcount⑤">signCount</a></code> in this case, or not, or fails the <a data-link-type="dfn" href="#authentication-ceremony" id="ref-for-authentication-ceremony②④">authentication ceremony</a> or not, is <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party②⑥③">Relying Party</a>-specific. 
        </dl>
      </ul>
     <li data-md>
@@ -5324,11 +5402,11 @@ <h3 class="heading settled" data-level="8.1" id="sctn-attstn-fmt-ids"><span clas
    <p>Attestation statement formats that may exist in multiple versions SHOULD include a version in their identifier. In effect,
 different versions are thus treated as different formats, e.g., <code>packed2</code> as a new version of the <a href="#sctn-packed-attestation">§ 8.2 Packed Attestation Statement Format</a>.</p>
    <p>The following sections present a set of currently-defined and registered attestation statement formats and their identifiers.
-The up-to-date list of registered <a data-link-type="dfn" href="#webauthn-extensions" id="ref-for-webauthn-extensions⑦">WebAuthn Extensions</a> is maintained in the
+The up-to-date list of registered <a data-link-type="dfn" href="#webauthn-extensions" id="ref-for-webauthn-extensions⑧">WebAuthn Extensions</a> is maintained in the
 IANA "WebAuthn Attestation Statement Format Identifiers" registry <a data-link-type="biblio" href="#biblio-iana-webauthn-registries">[IANA-WebAuthn-Registries]</a> established by <a data-link-type="biblio" href="#biblio-rfc8809">[RFC8809]</a>.</p>
    <h3 class="heading settled" data-level="8.2" id="sctn-packed-attestation"><span class="secno">8.2. </span><span class="content">Packed Attestation Statement Format</span><a class="self-link" href="#sctn-packed-attestation"></a></h3>
    <p>This is a WebAuthn optimized attestation statement format. It uses a very compact but still extensible encoding method. It is
-implementable by <a data-link-type="dfn" href="#authenticator" id="ref-for-authenticator②②⓪">authenticators</a> with limited resources (e.g., secure elements).</p>
+implementable by <a data-link-type="dfn" href="#authenticator" id="ref-for-authenticator②①⑨">authenticators</a> with limited resources (e.g., secure elements).</p>
    <dl>
     <dt data-md>Attestation statement format identifier
     <dd data-md>
@@ -5358,10 +5436,10 @@ <h3 class="heading settled" data-level="8.2" id="sctn-packed-attestation"><span
      <dl>
       <dt data-md>alg
       <dd data-md>
-       <p>A <code class="idl"><a data-link-type="idl" href="#typedefdef-cosealgorithmidentifier" id="ref-for-typedefdef-cosealgorithmidentifier①②">COSEAlgorithmIdentifier</a></code> containing the identifier of the algorithm used to generate the <a data-link-type="dfn" href="#attestation-signature" id="ref-for-attestation-signature⑨">attestation signature</a>.</p>
+       <p>A <code class="idl"><a data-link-type="idl" href="#typedefdef-cosealgorithmidentifier" id="ref-for-typedefdef-cosealgorithmidentifier①②">COSEAlgorithmIdentifier</a></code> containing the identifier of the algorithm used to generate the <a data-link-type="dfn" href="#attestation-signature" id="ref-for-attestation-signature①⓪">attestation signature</a>.</p>
       <dt data-md>sig
       <dd data-md>
-       <p>A byte string containing the <a data-link-type="dfn" href="#attestation-signature" id="ref-for-attestation-signature①⓪">attestation signature</a>.</p>
+       <p>A byte string containing the <a data-link-type="dfn" href="#attestation-signature" id="ref-for-attestation-signature①①">attestation signature</a>.</p>
       <dt data-md>x5c
       <dd data-md>
        <p>The elements of this array contain <var>attestnCert</var> and its certificate chain (if any), each encoded in X.509 format. The attestation
@@ -5416,7 +5494,7 @@ <h3 class="heading settled" data-level="8.2" id="sctn-packed-attestation"><span
        <p>If <var>x5c</var> is not present, <a data-link-type="dfn" href="#self-attestation" id="ref-for-self-attestation①⑧">self attestation</a> is in use.</p>
        <ul>
         <li data-md>
-         <p>Validate that <var>alg</var> matches the algorithm of the <code><a data-link-type="dfn" href="#authdata-attestedcredentialdata-credentialpublickey" id="ref-for-authdata-attestedcredentialdata-credentialpublickey⑦">credentialPublicKey</a></code> in <var>authenticatorData</var>.</p>
+         <p>Validate that <var>alg</var> matches the algorithm of the <code><a data-link-type="dfn" href="#authdata-attestedcredentialdata-credentialpublickey" id="ref-for-authdata-attestedcredentialdata-credentialpublickey⑥">credentialPublicKey</a></code> in <var>authenticatorData</var>.</p>
         <li data-md>
          <p>Verify that <var>sig</var> is a valid signature over the concatenation of <var>authenticatorData</var> and <var>clientDataHash</var> using the
 credential public key with <var>alg</var>.</p>
@@ -5500,7 +5578,7 @@ <h3 class="heading settled" data-level="8.3" id="sctn-tpm-attestation"><span cla
        <p>The version of the TPM specification to which the signature conforms.</p>
       <dt data-md>alg
       <dd data-md>
-       <p>A <code class="idl"><a data-link-type="idl" href="#typedefdef-cosealgorithmidentifier" id="ref-for-typedefdef-cosealgorithmidentifier①③">COSEAlgorithmIdentifier</a></code> containing the identifier of the algorithm used to generate the <a data-link-type="dfn" href="#attestation-signature" id="ref-for-attestation-signature①①">attestation signature</a>.</p>
+       <p>A <code class="idl"><a data-link-type="idl" href="#typedefdef-cosealgorithmidentifier" id="ref-for-typedefdef-cosealgorithmidentifier①③">COSEAlgorithmIdentifier</a></code> containing the identifier of the algorithm used to generate the <a data-link-type="dfn" href="#attestation-signature" id="ref-for-attestation-signature①②">attestation signature</a>.</p>
       <dt data-md>x5c
       <dd data-md>
        <p><var>aikCert</var> followed by its certificate chain, in X.509 encoding.</p>
@@ -5509,7 +5587,7 @@ <h3 class="heading settled" data-level="8.3" id="sctn-tpm-attestation"><span cla
        <p>The AIK certificate used for the attestation, in X.509 encoding.</p>
       <dt data-md>sig
       <dd data-md>
-       <p>The <a data-link-type="dfn" href="#attestation-signature" id="ref-for-attestation-signature①②">attestation signature</a>, in the form of a TPMT_SIGNATURE structure as specified in <a data-link-type="biblio" href="#biblio-tpmv2-part2">[TPMv2-Part2]</a> section 11.3.4.</p>
+       <p>The <a data-link-type="dfn" href="#attestation-signature" id="ref-for-attestation-signature①③">attestation signature</a>, in the form of a TPMT_SIGNATURE structure as specified in <a data-link-type="biblio" href="#biblio-tpmv2-part2">[TPMv2-Part2]</a> section 11.3.4.</p>
       <dt data-md>certInfo
       <dd data-md>
        <p>The TPMS_ATTEST structure over which the above signature was computed, as specified in <a data-link-type="biblio" href="#biblio-tpmv2-part2">[TPMv2-Part2]</a> section 10.12.8.</p>
@@ -5532,7 +5610,7 @@ <h3 class="heading settled" data-level="8.3" id="sctn-tpm-attestation"><span cla
 as follows:</p>
      <p>Verify that <var>attStmt</var> is valid CBOR conforming to the syntax defined above and perform CBOR decoding on it to extract the
 contained fields.</p>
-     <p>Verify that the public key specified by the <code>parameters</code> and <code>unique</code> fields of <var>pubArea</var> is identical to the <code><a data-link-type="dfn" href="#authdata-attestedcredentialdata-credentialpublickey" id="ref-for-authdata-attestedcredentialdata-credentialpublickey⑧">credentialPublicKey</a></code> in the <code><a data-link-type="dfn" href="#authdata-attestedcredentialdata" id="ref-for-authdata-attestedcredentialdata⑨">attestedCredentialData</a></code> in <var>authenticatorData</var>.</p>
+     <p>Verify that the public key specified by the <code>parameters</code> and <code>unique</code> fields of <var>pubArea</var> is identical to the <code><a data-link-type="dfn" href="#authdata-attestedcredentialdata-credentialpublickey" id="ref-for-authdata-attestedcredentialdata-credentialpublickey⑦">credentialPublicKey</a></code> in the <code><a data-link-type="dfn" href="#authdata-attestedcredentialdata" id="ref-for-authdata-attestedcredentialdata⑧">attestedCredentialData</a></code> in <var>authenticatorData</var>.</p>
      <p>Concatenate <var>authenticatorData</var> and <var>clientDataHash</var> to form <var>attToBeSigned</var>.</p>
      <p>Validate that <var>certInfo</var> is valid:</p>
      <ul>
@@ -5583,7 +5661,7 @@ <h4 class="heading settled" data-level="8.3.1" id="sctn-tpm-cert-requirements"><
 See, for example, the FIDO Metadata Service <a data-link-type="biblio" href="#biblio-fidometadataservice">[FIDOMetadataService]</a>.</p>
    </ul>
    <h3 class="heading settled" data-level="8.4" id="sctn-android-key-attestation"><span class="secno">8.4. </span><span class="content">Android Key Attestation Statement Format</span><a class="self-link" href="#sctn-android-key-attestation"></a></h3>
-   <p>When the <a data-link-type="dfn" href="#authenticator" id="ref-for-authenticator②②①">authenticator</a> in question is a <a data-link-type="dfn" href="#platform-authenticators" id="ref-for-platform-authenticators②⑤">platform authenticator</a> on the Android "N" or later platform, the
+   <p>When the <a data-link-type="dfn" href="#authenticator" id="ref-for-authenticator②②⓪">authenticator</a> in question is a <a data-link-type="dfn" href="#platform-authenticators" id="ref-for-platform-authenticators②⑤">platform authenticator</a> on the Android "N" or later platform, the
 attestation statement is based on the <a href="https://source.android.com/security/keystore/attestation">Android key
 attestation</a>. In these cases, the attestation statement
 is produced by a component running in a secure operating environment, but the <a data-link-type="dfn" href="#authenticator-data-for-the-attestation" id="ref-for-authenticator-data-for-the-attestation②">authenticator data for the attestation</a> is
@@ -5632,7 +5710,7 @@ <h3 class="heading settled" data-level="8.4" id="sctn-android-key-attestation"><
        <p>Verify that <var>sig</var> is a valid signature over the concatenation of <var>authenticatorData</var> and <var>clientDataHash</var> using the
 public key in the first certificate in <var>x5c</var> with the algorithm specified in <var>alg</var>.</p>
       <li data-md>
-       <p>Verify that the public key in the first certificate in <var>x5c</var> matches the <code><a data-link-type="dfn" href="#authdata-attestedcredentialdata-credentialpublickey" id="ref-for-authdata-attestedcredentialdata-credentialpublickey⑨">credentialPublicKey</a></code> in the <code><a data-link-type="dfn" href="#authdata-attestedcredentialdata" id="ref-for-authdata-attestedcredentialdata①⓪">attestedCredentialData</a></code> in <var>authenticatorData</var>.</p>
+       <p>Verify that the public key in the first certificate in <var>x5c</var> matches the <code><a data-link-type="dfn" href="#authdata-attestedcredentialdata-credentialpublickey" id="ref-for-authdata-attestedcredentialdata-credentialpublickey⑧">credentialPublicKey</a></code> in the <code><a data-link-type="dfn" href="#authdata-attestedcredentialdata" id="ref-for-authdata-attestedcredentialdata⑨">attestedCredentialData</a></code> in <var>authenticatorData</var>.</p>
       <li data-md>
        <p>Verify that the <code>attestationChallenge</code> field in the <a data-link-type="dfn" href="#attestation-certificate" id="ref-for-attestation-certificate⑦">attestation certificate</a> <a data-link-type="dfn" href="#android-key-attestation-certificate-extension-data" id="ref-for-android-key-attestation-certificate-extension-data">extension data</a> is identical to <var>clientDataHash</var>.</p>
       <li data-md>
@@ -5660,9 +5738,9 @@ <h4 class="heading settled" data-level="8.4.1" id="sctn-key-attstn-cert-requirem
    <p>Android Key Attestation <a data-link-type="dfn" href="#attestation-certificate" id="ref-for-attestation-certificate⑧">attestation certificate</a>'s <dfn class="dfn-paneled" data-dfn-type="dfn" data-lt="android key attestation certificate extension data" data-noexport id="android-key-attestation-certificate-extension-data">android key attestation certificate extension
 data</dfn> is identified by the OID <code>1.3.6.1.4.1.11129.2.1.17</code>, and its schema is defined in the <a href="https://developer.android.com/training/articles/security-key-attestation#certificate_schema">Android developer documentation</a>.</p>
    <h3 class="heading settled" data-level="8.5" id="sctn-android-safetynet-attestation"><span class="secno">8.5. </span><span class="content">Android SafetyNet Attestation Statement Format</span><a class="self-link" href="#sctn-android-safetynet-attestation"></a></h3>
-   <p>When the <a data-link-type="dfn" href="#authenticator" id="ref-for-authenticator②②②">authenticator</a> is a <a data-link-type="dfn" href="#platform-authenticators" id="ref-for-platform-authenticators②⑥">platform authenticator</a> on certain Android platforms, the attestation
+   <p>When the <a data-link-type="dfn" href="#authenticator" id="ref-for-authenticator②②①">authenticator</a> is a <a data-link-type="dfn" href="#platform-authenticators" id="ref-for-platform-authenticators②⑥">platform authenticator</a> on certain Android platforms, the attestation
 statement may be based on the <a href="https://developer.android.com/training/safetynet/attestation#compat-check-response">SafetyNet API</a>. In
-this case the <a data-link-type="dfn" href="#authenticator-data" id="ref-for-authenticator-data④④">authenticator data</a> is completely controlled by the caller of the SafetyNet API (typically an application
+this case the <a data-link-type="dfn" href="#authenticator-data" id="ref-for-authenticator-data④⑥">authenticator data</a> is completely controlled by the caller of the SafetyNet API (typically an application
 running on the Android platform) and the attestation statement  provides some statements about the health of the platform
 and the identity of the calling application
 (see <a href="https://developer.android.com/training/safetynet/attestation.html">SafetyNet Documentation</a> for more details).</p>
@@ -5752,18 +5830,18 @@ <h3 class="heading settled" data-level="8.6" id="sctn-fido-u2f-attestation"><spa
        <p>A single element array containing the attestation certificate in X.509 format.</p>
       <dt data-md>sig
       <dd data-md>
-       <p>The <a data-link-type="dfn" href="#attestation-signature" id="ref-for-attestation-signature①③">attestation signature</a>.
-The signature was calculated over the (raw) U2F registration response message <a data-link-type="biblio" href="#biblio-fido-u2f-message-formats">[FIDO-U2F-Message-Formats]</a> received by the <a data-link-type="dfn" href="#client" id="ref-for-client⑧③">client</a> from the authenticator.</p>
+       <p>The <a data-link-type="dfn" href="#attestation-signature" id="ref-for-attestation-signature①④">attestation signature</a>.
+The signature was calculated over the (raw) U2F registration response message <a data-link-type="biblio" href="#biblio-fido-u2f-message-formats">[FIDO-U2F-Message-Formats]</a> received by the <a data-link-type="dfn" href="#client" id="ref-for-client⑧②">client</a> from the authenticator.</p>
      </dl>
     <dt data-md>Signing procedure
     <dd data-md>
-     <p>If the <a data-link-type="dfn" href="#credential-public-key" id="ref-for-credential-public-key③②">credential public key</a> of the <a data-link-type="dfn" href="#authdata-attestedcredentialdata" id="ref-for-authdata-attestedcredentialdata①①">attested credential</a> is not of algorithm -7 ("ES256"), stop and return an error.
+     <p>If the <a data-link-type="dfn" href="#credential-public-key" id="ref-for-credential-public-key③②">credential public key</a> of the <a data-link-type="dfn" href="#authdata-attestedcredentialdata" id="ref-for-authdata-attestedcredentialdata①⓪">attested credential</a> is not of algorithm -7 ("ES256"), stop and return an error.
 Otherwise, let <var>authenticatorData</var> denote the <a data-link-type="dfn" href="#authenticator-data-for-the-attestation" id="ref-for-authenticator-data-for-the-attestation⑤">authenticator data for the attestation</a>,
 and let <var>clientDataHash</var> denote the <a data-link-type="dfn" href="#collectedclientdata-hash-of-the-serialized-client-data" id="ref-for-collectedclientdata-hash-of-the-serialized-client-data①⑨">hash of the serialized client data</a>. (Since SHA-256 is used to hash the
 serialized <a data-link-type="dfn" href="#client-data" id="ref-for-client-data①①">client data</a>, <var>clientDataHash</var> will be 32 bytes long.)</p>
      <p>Generate a Registration Response Message as specified in <a data-link-type="biblio" href="#biblio-fido-u2f-message-formats">[FIDO-U2F-Message-Formats]</a> <a data-link-type="dfn" href="https://fidoalliance.org/specs/fido-u2f-v1.1-id-20160915/fido-u2f-raw-message-formats-v1.1-id-20160915.html#registration-response-message-success" id="ref-for-registration-response-message-success">Section 4.3</a>, with the application parameter set to the
 SHA-256 hash of the <a data-link-type="dfn" href="#rp-id" id="ref-for-rp-id④⓪">RP ID</a> that the given <a data-link-type="dfn" href="#public-key-credential" id="ref-for-public-key-credential⑤⑤">credential</a> is <a data-link-type="dfn" href="#scope" id="ref-for-scope①⑦">scoped</a> to, the challenge parameter set to <var>clientDataHash</var>, and the key handle
-parameter set to the <a data-link-type="dfn" href="#credential-id" id="ref-for-credential-id③⑤">credential ID</a> of the given credential. Set the raw signature part of this Registration Response Message (i.e., without the <a data-link-type="dfn" href="#user-public-key" id="ref-for-user-public-key①">user public key</a>,
+parameter set to the <a data-link-type="dfn" href="#credential-id" id="ref-for-credential-id③⑥">credential ID</a> of the given credential. Set the raw signature part of this Registration Response Message (i.e., without the <a data-link-type="dfn" href="#user-public-key" id="ref-for-user-public-key①">user public key</a>,
 key handle, and attestation certificates) as <var>sig</var> and set the attestation certificates of
 the attestation public key as <var>x5c</var>.</p>
     <dt data-md>Verification procedure
@@ -5779,7 +5857,7 @@ <h3 class="heading settled" data-level="8.6" id="sctn-fido-u2f-attestation"><spa
 conveyed by <var>attCert</var>. If <var>certificate public key</var> is not an Elliptic Curve (EC) public
 key over the P-256 curve, terminate this algorithm and return an appropriate error.</p>
       <li data-md>
-       <p>Extract the claimed <var>rpIdHash</var> from <var>authenticatorData</var>, and the claimed <var>credentialId</var> and <var>credentialPublicKey</var> from <var>authenticatorData</var>.<code><a data-link-type="dfn" href="#authdata-attestedcredentialdata" id="ref-for-authdata-attestedcredentialdata①②">attestedCredentialData</a></code>.</p>
+       <p>Extract the claimed <var>rpIdHash</var> from <var>authenticatorData</var>, and the claimed <var>credentialId</var> and <var>credentialPublicKey</var> from <var>authenticatorData</var>.<code><a data-link-type="dfn" href="#authdata-attestedcredentialdata" id="ref-for-authdata-attestedcredentialdata①①">attestedCredentialData</a></code>.</p>
       <li data-md>
        <p>Convert the COSE_KEY formatted <var>credentialPublicKey</var> (see <a data-link-type="dfn" href="https://tools.ietf.org/html/rfc8152#section-7" id="ref-for-section-7④">Section 7</a> of <a data-link-type="biblio" href="#biblio-rfc8152">[RFC8152]</a>) to Raw ANSI X9.62 public key
 format (see ALG_KEY_ECC_X962_RAW in <a data-link-type="dfn" href="https://fidoalliance.org/specs/common-specs/fido-registry-v2.1-ps-20191217.html#public-key-representation-formats" id="ref-for-public-key-representation-formats">Section 3.6.2 Public Key Representation Formats</a> of <a data-link-type="biblio" href="#biblio-fido-registry">[FIDO-Registry]</a>).</p>
@@ -5808,9 +5886,9 @@ <h3 class="heading settled" data-level="8.6" id="sctn-fido-u2f-attestation"><spa
      </ol>
    </dl>
    <h3 class="heading settled" data-level="8.7" id="sctn-none-attestation"><span class="secno">8.7. </span><span class="content">None Attestation Statement Format</span><a class="self-link" href="#sctn-none-attestation"></a></h3>
-   <p>The none attestation statement format is used to replace any <a data-link-type="dfn" href="#authenticator" id="ref-for-authenticator②②③">authenticator</a>-provided <a data-link-type="dfn" href="#attestation-statement" id="ref-for-attestation-statement③⑥">attestation statement</a> when a <a data-link-type="dfn" href="#webauthn-relying-party" id="ref-for-webauthn-relying-party③①">WebAuthn Relying Party</a> indicates it does not wish to receive attestation information, see <a href="#enum-attestation-convey">§ 5.4.7 Attestation Conveyance Preference Enumeration (enum AttestationConveyancePreference)</a>.</p>
-   <p>The <a data-link-type="dfn" href="#authenticator" id="ref-for-authenticator②②④">authenticator</a> MAY also directly generate attestation statements of this format
-if the <a data-link-type="dfn" href="#authenticator" id="ref-for-authenticator②②⑤">authenticator</a> does not support <a data-link-type="dfn" href="#attestation" id="ref-for-attestation①⑧">attestation</a>.</p>
+   <p>The none attestation statement format is used to replace any <a data-link-type="dfn" href="#authenticator" id="ref-for-authenticator②②②">authenticator</a>-provided <a data-link-type="dfn" href="#attestation-statement" id="ref-for-attestation-statement③⑦">attestation statement</a> when a <a data-link-type="dfn" href="#webauthn-relying-party" id="ref-for-webauthn-relying-party③①">WebAuthn Relying Party</a> indicates it does not wish to receive attestation information, see <a href="#enum-attestation-convey">§ 5.4.7 Attestation Conveyance Preference Enumeration (enum AttestationConveyancePreference)</a>.</p>
+   <p>The <a data-link-type="dfn" href="#authenticator" id="ref-for-authenticator②②③">authenticator</a> MAY also directly generate attestation statements of this format
+if the <a data-link-type="dfn" href="#authenticator" id="ref-for-authenticator②②④">authenticator</a> does not support <a data-link-type="dfn" href="#attestation" id="ref-for-attestation①⑧">attestation</a>.</p>
    <dl>
     <dt data-md>Attestation statement format identifier
     <dd data-md>
@@ -5907,14 +5985,14 @@ <h2 class="heading settled" data-level="9" id="sctn-extensions"><span class="sec
     <li data-md>
      <p><code class="idl"><a data-link-type="idl" href="https://w3c.github.io/webappsec-credential-management/#dom-credentialscontainer-create" id="ref-for-dom-credentialscontainer-create②⑥">navigator.credentials.create()</a></code> extension request parameters and response values for <a data-link-type="dfn" href="#registration-extension" id="ref-for-registration-extension②">registration extensions</a>.</p>
     <li data-md>
-     <p><code class="idl"><a data-link-type="idl" href="https://w3c.github.io/webappsec-credential-management/#dom-credentialscontainer-get" id="ref-for-dom-credentialscontainer-get③①">navigator.credentials.get()</a></code> extension request parameters and response values for <a data-link-type="dfn" href="#authentication-extension" id="ref-for-authentication-extension②">authentication extensions</a>.</p>
+     <p><code class="idl"><a data-link-type="idl" href="https://w3c.github.io/webappsec-credential-management/#dom-credentialscontainer-get" id="ref-for-dom-credentialscontainer-get③⓪">navigator.credentials.get()</a></code> extension request parameters and response values for <a data-link-type="dfn" href="#authentication-extension" id="ref-for-authentication-extension②">authentication extensions</a>.</p>
     <li data-md>
      <p><a data-link-type="dfn" href="#client-extension-processing" id="ref-for-client-extension-processing⑥">Client extension processing</a> for <a data-link-type="dfn" href="#registration-extension" id="ref-for-registration-extension③">registration extensions</a> and <a data-link-type="dfn" href="#authentication-extension" id="ref-for-authentication-extension③">authentication extensions</a>.</p>
    </ul>
    <p>When creating a <a data-link-type="dfn" href="#public-key-credential" id="ref-for-public-key-credential⑤⑦">public key credential</a> or requesting an <a data-link-type="dfn" href="#authentication-assertion" id="ref-for-authentication-assertion①③">authentication assertion</a>, a <a data-link-type="dfn" href="#webauthn-relying-party" id="ref-for-webauthn-relying-party③②">WebAuthn Relying Party</a> can request the use of a set
-of extensions. These extensions will be invoked during the requested operation if they are supported by the client and/or the <a data-link-type="dfn" href="#webauthn-authenticator" id="ref-for-webauthn-authenticator⑥">WebAuthn Authenticator</a>. The <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party②⑤⑦">Relying Party</a> sends the <a data-link-type="dfn" href="#client-extension-input" id="ref-for-client-extension-input⑦">client extension input</a> for each extension in the <code class="idl"><a data-link-type="idl" href="https://w3c.github.io/webappsec-credential-management/#dom-credentialscontainer-get" id="ref-for-dom-credentialscontainer-get③②">get()</a></code> call
-(for <a data-link-type="dfn" href="#authentication-extension" id="ref-for-authentication-extension④">authentication extensions</a>) or <code class="idl"><a data-link-type="idl" href="https://w3c.github.io/webappsec-credential-management/#dom-credentialscontainer-create" id="ref-for-dom-credentialscontainer-create②⑦">create()</a></code> call (for <a data-link-type="dfn" href="#registration-extension" id="ref-for-registration-extension④">registration extensions</a>) to the <a data-link-type="dfn" href="#client" id="ref-for-client⑧④">client</a>.
-The <a data-link-type="dfn" href="#client" id="ref-for-client⑧⑤">client</a> performs <a data-link-type="dfn" href="#client-extension-processing" id="ref-for-client-extension-processing⑦">client extension processing</a> for each extension that the <a data-link-type="dfn" href="#client-platform" id="ref-for-client-platform④⑧">client platform</a> supports, and augments the <a data-link-type="dfn" href="#client-data" id="ref-for-client-data①③">client data</a> as specified by each extension, by including the <a data-link-type="dfn" href="#extension-identifier" id="ref-for-extension-identifier⑨">extension identifier</a> and <a data-link-type="dfn" href="#client-extension-output" id="ref-for-client-extension-output①⓪">client extension output</a> values.</p>
+of extensions. These extensions will be invoked during the requested operation if they are supported by the client and/or the <a data-link-type="dfn" href="#webauthn-authenticator" id="ref-for-webauthn-authenticator⑥">WebAuthn Authenticator</a>. The <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party②⑥④">Relying Party</a> sends the <a data-link-type="dfn" href="#client-extension-input" id="ref-for-client-extension-input⑦">client extension input</a> for each extension in the <code class="idl"><a data-link-type="idl" href="https://w3c.github.io/webappsec-credential-management/#dom-credentialscontainer-get" id="ref-for-dom-credentialscontainer-get③①">get()</a></code> call
+(for <a data-link-type="dfn" href="#authentication-extension" id="ref-for-authentication-extension④">authentication extensions</a>) or <code class="idl"><a data-link-type="idl" href="https://w3c.github.io/webappsec-credential-management/#dom-credentialscontainer-create" id="ref-for-dom-credentialscontainer-create②⑦">create()</a></code> call (for <a data-link-type="dfn" href="#registration-extension" id="ref-for-registration-extension④">registration extensions</a>) to the <a data-link-type="dfn" href="#client" id="ref-for-client⑧③">client</a>.
+The <a data-link-type="dfn" href="#client" id="ref-for-client⑧④">client</a> performs <a data-link-type="dfn" href="#client-extension-processing" id="ref-for-client-extension-processing⑦">client extension processing</a> for each extension that the <a data-link-type="dfn" href="#client-platform" id="ref-for-client-platform④⑧">client platform</a> supports, and augments the <a data-link-type="dfn" href="#client-data" id="ref-for-client-data①③">client data</a> as specified by each extension, by including the <a data-link-type="dfn" href="#extension-identifier" id="ref-for-extension-identifier⑨">extension identifier</a> and <a data-link-type="dfn" href="#client-extension-output" id="ref-for-client-extension-output①⓪">client extension output</a> values.</p>
    <p>An extension can also be an <dfn class="dfn-paneled" data-dfn-type="dfn" data-noexport id="authenticator-extension">authenticator extension</dfn>, meaning that the extension involves communication with and
 processing by the authenticator. <a data-link-type="dfn" href="#authenticator-extension" id="ref-for-authenticator-extension⑤">Authenticator extensions</a> define the following steps and data:</p>
    <ul>
@@ -5926,22 +6004,22 @@ <h2 class="heading settled" data-level="9" id="sctn-extensions"><span class="sec
      <p><a data-link-type="dfn" href="#authenticator-extension-processing" id="ref-for-authenticator-extension-processing②">Authenticator extension processing</a> for <a data-link-type="dfn" href="#registration-extension" id="ref-for-registration-extension⑥">registration extensions</a> and <a data-link-type="dfn" href="#authentication-extension" id="ref-for-authentication-extension⑥">authentication extensions</a>.</p>
    </ul>
    <p>For <a data-link-type="dfn" href="#authenticator-extension" id="ref-for-authenticator-extension⑥">authenticator extensions</a>, as part of the <a data-link-type="dfn" href="#client-extension-processing" id="ref-for-client-extension-processing⑧">client extension processing</a>, the client also creates the <a data-link-type="dfn" href="#cbor" id="ref-for-cbor①①">CBOR</a> <a data-link-type="dfn" href="#authenticator-extension-input" id="ref-for-authenticator-extension-input⑤">authenticator extension input</a> value for each extension (often based on the corresponding <a data-link-type="dfn" href="#client-extension-input" id="ref-for-client-extension-input⑧">client extension input</a> value),
-and passes them to the authenticator in the <code class="idl"><a data-link-type="idl" href="https://w3c.github.io/webappsec-credential-management/#dom-credentialscontainer-create" id="ref-for-dom-credentialscontainer-create②⑧">create()</a></code> call (for <a data-link-type="dfn" href="#registration-extension" id="ref-for-registration-extension⑦">registration extensions</a>) or the <code class="idl"><a data-link-type="idl" href="https://w3c.github.io/webappsec-credential-management/#dom-credentialscontainer-get" id="ref-for-dom-credentialscontainer-get③③">get()</a></code> call (for <a data-link-type="dfn" href="#authentication-extension" id="ref-for-authentication-extension⑦">authentication extensions</a>). These <a data-link-type="dfn" href="#authenticator-extension-input" id="ref-for-authenticator-extension-input⑥">authenticator extension input</a> values are
+and passes them to the authenticator in the <code class="idl"><a data-link-type="idl" href="https://w3c.github.io/webappsec-credential-management/#dom-credentialscontainer-create" id="ref-for-dom-credentialscontainer-create②⑧">create()</a></code> call (for <a data-link-type="dfn" href="#registration-extension" id="ref-for-registration-extension⑦">registration extensions</a>) or the <code class="idl"><a data-link-type="idl" href="https://w3c.github.io/webappsec-credential-management/#dom-credentialscontainer-get" id="ref-for-dom-credentialscontainer-get③②">get()</a></code> call (for <a data-link-type="dfn" href="#authentication-extension" id="ref-for-authentication-extension⑦">authentication extensions</a>). These <a data-link-type="dfn" href="#authenticator-extension-input" id="ref-for-authenticator-extension-input⑥">authenticator extension input</a> values are
 represented in <a data-link-type="dfn" href="#cbor" id="ref-for-cbor①②">CBOR</a> and passed as name-value pairs, with the <a data-link-type="dfn" href="#extension-identifier" id="ref-for-extension-identifier①⓪">extension identifier</a> as the name, and the corresponding <a data-link-type="dfn" href="#authenticator-extension-input" id="ref-for-authenticator-extension-input⑦">authenticator extension input</a> as the value. The authenticator, in turn, performs additional processing for the extensions
 that it supports, and returns the <a data-link-type="dfn" href="#cbor" id="ref-for-cbor①③">CBOR</a> <a data-link-type="dfn" href="#authenticator-extension-output" id="ref-for-authenticator-extension-output⑦">authenticator extension output</a> for each as specified by the extension. Part of
 the <a data-link-type="dfn" href="#client-extension-processing" id="ref-for-client-extension-processing⑨">client extension processing</a> for <a data-link-type="dfn" href="#authenticator-extension" id="ref-for-authenticator-extension⑦">authenticator extensions</a> is to use the <a data-link-type="dfn" href="#authenticator-extension-output" id="ref-for-authenticator-extension-output⑧">authenticator extension output</a> as an
 input to creating the <a data-link-type="dfn" href="#client-extension-output" id="ref-for-client-extension-output①①">client extension output</a>.</p>
-   <p>All <a data-link-type="dfn" href="#webauthn-extensions" id="ref-for-webauthn-extensions⑧">WebAuthn Extensions</a> are OPTIONAL for both clients and authenticators. Thus, any extensions requested by a <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party②⑤⑧">Relying Party</a> MAY be
+   <p>All <a data-link-type="dfn" href="#webauthn-extensions" id="ref-for-webauthn-extensions⑨">WebAuthn Extensions</a> are OPTIONAL for both clients and authenticators. Thus, any extensions requested by a <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party②⑥⑤">Relying Party</a> MAY be
 ignored by the client browser or OS and not passed to the authenticator at all, or they MAY be ignored by the authenticator.
-Ignoring an extension is never considered a failure in WebAuthn API processing, so when <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party②⑤⑨">Relying Parties</a> include extensions with any
+Ignoring an extension is never considered a failure in WebAuthn API processing, so when <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party②⑥⑥">Relying Parties</a> include extensions with any
 API calls, they MUST be prepared to handle cases where some or all of those extensions are ignored.</p>
-   <p>All <a data-link-type="dfn" href="#webauthn-extensions" id="ref-for-webauthn-extensions⑨">WebAuthn Extensions</a> MUST be defined in such a way that this implementation choice does not endanger the user’s
+   <p>All <a data-link-type="dfn" href="#webauthn-extensions" id="ref-for-webauthn-extensions①⓪">WebAuthn Extensions</a> MUST be defined in such a way that this implementation choice does not endanger the user’s
 security or privacy. For instance, if an extension requires client processing, it could be defined in a manner that ensures such
 a naïve pass-through will produce a semantically invalid <a data-link-type="dfn" href="#authenticator-extension-input" id="ref-for-authenticator-extension-input⑧">authenticator extension input</a> value, resulting in the extension
 being ignored by the authenticator. Since all extensions are OPTIONAL, this will not cause a functional failure in the API
 operation.</p>
    <p>The IANA "WebAuthn Extension Identifiers" registry <a data-link-type="biblio" href="#biblio-iana-webauthn-registries">[IANA-WebAuthn-Registries]</a> established by <a data-link-type="biblio" href="#biblio-rfc8809">[RFC8809]</a> can be consulted
-for an up-to-date list of registered <a data-link-type="dfn" href="#webauthn-extensions" id="ref-for-webauthn-extensions①⓪">WebAuthn Extensions</a>.</p>
+for an up-to-date list of registered <a data-link-type="dfn" href="#webauthn-extensions" id="ref-for-webauthn-extensions①①">WebAuthn Extensions</a>.</p>
    <h3 class="heading settled" data-level="9.1" id="sctn-extension-id"><span class="secno">9.1. </span><span class="content">Extension Identifiers</span><a class="self-link" href="#sctn-extension-id"></a></h3>
    <p>Extensions are identified by a string, called an <dfn class="dfn-paneled" data-dfn-type="dfn" data-noexport id="extension-identifier">extension identifier</dfn>, chosen by the extension author.</p>
    <p>Extension identifiers SHOULD be registered in the
@@ -5957,24 +6035,24 @@ <h3 class="heading settled" data-level="9.1" id="sctn-extension-id"><span class=
 See the IANA "WebAuthn Extension Identifiers" registry <a data-link-type="biblio" href="#biblio-iana-webauthn-registries">[IANA-WebAuthn-Registries]</a> established by <a data-link-type="biblio" href="#biblio-rfc8809">[RFC8809]</a> for an up-to-date list of registered WebAuthn Extension Identifiers.</p>
    <h3 class="heading settled" data-level="9.2" id="sctn-extension-specification"><span class="secno">9.2. </span><span class="content">Defining Extensions</span><a class="self-link" href="#sctn-extension-specification"></a></h3>
    <p>A definition of an extension MUST specify an <a data-link-type="dfn" href="#extension-identifier" id="ref-for-extension-identifier①①">extension identifier</a>, a <a data-link-type="dfn" href="#client-extension-input" id="ref-for-client-extension-input⑨">client extension input</a> argument
-to be sent via the <code class="idl"><a data-link-type="idl" href="https://w3c.github.io/webappsec-credential-management/#dom-credentialscontainer-get" id="ref-for-dom-credentialscontainer-get③④">get()</a></code> or <code class="idl"><a data-link-type="idl" href="https://w3c.github.io/webappsec-credential-management/#dom-credentialscontainer-create" id="ref-for-dom-credentialscontainer-create②⑨">create()</a></code> call,
+to be sent via the <code class="idl"><a data-link-type="idl" href="https://w3c.github.io/webappsec-credential-management/#dom-credentialscontainer-get" id="ref-for-dom-credentialscontainer-get③③">get()</a></code> or <code class="idl"><a data-link-type="idl" href="https://w3c.github.io/webappsec-credential-management/#dom-credentialscontainer-create" id="ref-for-dom-credentialscontainer-create②⑨">create()</a></code> call,
 the <a data-link-type="dfn" href="#client-extension-processing" id="ref-for-client-extension-processing①⓪">client extension processing</a> rules, and a <a data-link-type="dfn" href="#client-extension-output" id="ref-for-client-extension-output①②">client extension output</a> value.
 If the extension communicates with the authenticator (meaning it is an <a data-link-type="dfn" href="#authenticator-extension" id="ref-for-authenticator-extension⑧">authenticator extension</a>),
 it MUST also specify the <a data-link-type="dfn" href="#cbor" id="ref-for-cbor①④">CBOR</a> <a data-link-type="dfn" href="#authenticator-extension-input" id="ref-for-authenticator-extension-input⑨">authenticator extension input</a> argument
 sent via the <a data-link-type="dfn" href="#authenticatorgetassertion" id="ref-for-authenticatorgetassertion①⑦">authenticatorGetAssertion</a> or <a data-link-type="dfn" href="#authenticatormakecredential" id="ref-for-authenticatormakecredential①⑦">authenticatorMakeCredential</a> call,
 the <a data-link-type="dfn" href="#authenticator-extension-processing" id="ref-for-authenticator-extension-processing③">authenticator extension processing</a> rules, and the <a data-link-type="dfn" href="#cbor" id="ref-for-cbor①⑤">CBOR</a> <a data-link-type="dfn" href="#authenticator-extension-output" id="ref-for-authenticator-extension-output⑨">authenticator extension output</a> value.</p>
    <p>Any <a data-link-type="dfn" href="#client-extension" id="ref-for-client-extension⑤">client extension</a> that is processed by the client MUST return a <a data-link-type="dfn" href="#client-extension-output" id="ref-for-client-extension-output①③">client extension output</a> value so that the <a data-link-type="dfn" href="#webauthn-relying-party" id="ref-for-webauthn-relying-party③③">WebAuthn Relying Party</a> knows that the extension was honored by the client. Similarly, any extension that requires authenticator processing MUST return
-an <a data-link-type="dfn" href="#authenticator-extension-output" id="ref-for-authenticator-extension-output①⓪">authenticator extension output</a> to let the <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party②⑥⓪">Relying Party</a> know that the extension was honored by the authenticator. If an
+an <a data-link-type="dfn" href="#authenticator-extension-output" id="ref-for-authenticator-extension-output①⓪">authenticator extension output</a> to let the <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party②⑥⑦">Relying Party</a> know that the extension was honored by the authenticator. If an
 extension does not otherwise require any result values, it SHOULD be defined as returning a JSON Boolean <a data-link-type="dfn" href="#client-extension-output" id="ref-for-client-extension-output①④">client extension
 output</a> result, set to <code>true</code> to signify that the extension was understood and processed. Likewise, any <a data-link-type="dfn" href="#authenticator-extension" id="ref-for-authenticator-extension⑨">authenticator
 extension</a> that does not otherwise require any result values MUST return a value and SHOULD return a CBOR Boolean <a data-link-type="dfn" href="#authenticator-extension-output" id="ref-for-authenticator-extension-output①①">authenticator extension output</a> result, set to <code>true</code> to signify that the extension was understood and processed.</p>
    <h3 class="heading settled" data-level="9.3" id="sctn-extension-request-parameters"><span class="secno">9.3. </span><span class="content">Extending Request Parameters</span><a class="self-link" href="#sctn-extension-request-parameters"></a></h3>
    <p>An extension defines one or two request arguments. The <dfn class="dfn-paneled" data-dfn-type="dfn" data-noexport id="client-extension-input">client extension input</dfn>,
 which is a value that can be encoded in JSON, is passed from the <a data-link-type="dfn" href="#webauthn-relying-party" id="ref-for-webauthn-relying-party③④">WebAuthn Relying Party</a> to the client
-in the <code class="idl"><a data-link-type="idl" href="https://w3c.github.io/webappsec-credential-management/#dom-credentialscontainer-get" id="ref-for-dom-credentialscontainer-get③⑤">get()</a></code> or <code class="idl"><a data-link-type="idl" href="https://w3c.github.io/webappsec-credential-management/#dom-credentialscontainer-create" id="ref-for-dom-credentialscontainer-create③⓪">create()</a></code> call,
+in the <code class="idl"><a data-link-type="idl" href="https://w3c.github.io/webappsec-credential-management/#dom-credentialscontainer-get" id="ref-for-dom-credentialscontainer-get③④">get()</a></code> or <code class="idl"><a data-link-type="idl" href="https://w3c.github.io/webappsec-credential-management/#dom-credentialscontainer-create" id="ref-for-dom-credentialscontainer-create③⓪">create()</a></code> call,
 while the <a data-link-type="dfn" href="#cbor" id="ref-for-cbor①⑥">CBOR</a> <dfn class="dfn-paneled" data-dfn-type="dfn" data-noexport id="authenticator-extension-input">authenticator extension input</dfn> is
 passed from the client to the authenticator for <a data-link-type="dfn" href="#authenticator-extension" id="ref-for-authenticator-extension①⓪">authenticator extensions</a> during the processing of these calls.</p>
-   <p>A <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party②⑥①">Relying Party</a> simultaneously requests the use of an extension and sets its <a data-link-type="dfn" href="#client-extension-input" id="ref-for-client-extension-input①⓪">client extension input</a> by including an entry in the <code class="idl"><a data-link-type="idl" href="#dom-publickeycredentialcreationoptions-extensions" id="ref-for-dom-publickeycredentialcreationoptions-extensions⑦">extensions</a></code> option to the <code class="idl"><a data-link-type="idl" href="https://w3c.github.io/webappsec-credential-management/#dom-credentialscontainer-create" id="ref-for-dom-credentialscontainer-create③①">create()</a></code> or <code class="idl"><a data-link-type="idl" href="https://w3c.github.io/webappsec-credential-management/#dom-credentialscontainer-get" id="ref-for-dom-credentialscontainer-get③⑥">get()</a></code> call.
+   <p>A <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party②⑥⑧">Relying Party</a> simultaneously requests the use of an extension and sets its <a data-link-type="dfn" href="#client-extension-input" id="ref-for-client-extension-input①⓪">client extension input</a> by including an entry in the <code class="idl"><a data-link-type="idl" href="#dom-publickeycredentialcreationoptions-extensions" id="ref-for-dom-publickeycredentialcreationoptions-extensions⑦">extensions</a></code> option to the <code class="idl"><a data-link-type="idl" href="https://w3c.github.io/webappsec-credential-management/#dom-credentialscontainer-create" id="ref-for-dom-credentialscontainer-create③①">create()</a></code> or <code class="idl"><a data-link-type="idl" href="https://w3c.github.io/webappsec-credential-management/#dom-credentialscontainer-get" id="ref-for-dom-credentialscontainer-get③⑤">get()</a></code> call.
 The entry key is the <a data-link-type="dfn" href="#extension-identifier" id="ref-for-extension-identifier①②">extension identifier</a> and the value is the <a data-link-type="dfn" href="#client-extension-input" id="ref-for-client-extension-input①①">client extension input</a>.</p>
    <p class="note" role="note"><span>Note:</span> Other documents have specified extensions where the extension input does not always use the <a data-link-type="dfn" href="#extension-identifier" id="ref-for-extension-identifier①③">extension identifier</a> as the entry key.
 New extensions SHOULD follow the above convention.</p>
@@ -5993,8 +6071,8 @@ <h3 class="heading settled" data-level="9.3" id="sctn-extension-request-paramete
 <c- p>});</c->
 </pre>
    <p>Extension definitions MUST specify the valid values for their <a data-link-type="dfn" href="#client-extension-input" id="ref-for-client-extension-input①②">client extension input</a>. Clients SHOULD ignore extensions with
-an invalid <a data-link-type="dfn" href="#client-extension-input" id="ref-for-client-extension-input①③">client extension input</a>. If an extension does not require any parameters from the <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party②⑥②">Relying Party</a>, it SHOULD be defined
-as taking a Boolean client argument, set to <code>true</code> to signify that the extension is requested by the <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party②⑥③">Relying Party</a>.</p>
+an invalid <a data-link-type="dfn" href="#client-extension-input" id="ref-for-client-extension-input①③">client extension input</a>. If an extension does not require any parameters from the <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party②⑥⑨">Relying Party</a>, it SHOULD be defined
+as taking a Boolean client argument, set to <code>true</code> to signify that the extension is requested by the <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party②⑦⓪">Relying Party</a>.</p>
    <p>Extensions that only affect client processing need not specify <a data-link-type="dfn" href="#authenticator-extension-input" id="ref-for-authenticator-extension-input①⓪">authenticator extension input</a>. Extensions that have
 authenticator processing MUST specify the method of computing the <a data-link-type="dfn" href="#authenticator-extension-input" id="ref-for-authenticator-extension-input①①">authenticator extension input</a> from the <a data-link-type="dfn" href="#client-extension-input" id="ref-for-client-extension-input①④">client extension
 input</a>,
@@ -6014,7 +6092,7 @@ <h3 class="heading settled" data-level="9.3" id="sctn-extension-request-paramete
    <p class="note" role="note"><span>Note:</span> Extensions should aim to define authenticator arguments that are as small as possible. Some authenticators communicate
     over low-bandwidth links such as Bluetooth Low-Energy or NFC.</p>
    <h3 class="heading settled" data-level="9.4" id="sctn-client-extension-processing"><span class="secno">9.4. </span><span class="content"><dfn class="dfn-paneled" data-dfn-type="dfn" data-noexport id="client-extension-processing">Client Extension Processing</dfn></span><a class="self-link" href="#sctn-client-extension-processing"></a></h3>
-   <p>Extensions MAY define additional processing requirements on the <a data-link-type="dfn" href="#client" id="ref-for-client⑧⑥">client</a> during the creation of credentials or the
+   <p>Extensions MAY define additional processing requirements on the <a data-link-type="dfn" href="#client" id="ref-for-client⑧⑤">client</a> during the creation of credentials or the
 generation of an assertion. The <a data-link-type="dfn" href="#client-extension-input" id="ref-for-client-extension-input①⑥">client extension input</a> for the extension is used as an input to this client processing.
 For each supported <a data-link-type="dfn" href="#client-extension" id="ref-for-client-extension⑥">client extension</a>, the client adds an entry to the <var>clientExtensions</var> <a data-link-type="dfn" href="https://infra.spec.whatwg.org/#ordered-map" id="ref-for-ordered-map①②">map</a> with the <a data-link-type="dfn" href="#extension-identifier" id="ref-for-extension-identifier①⑥">extension identifier</a> as the key, and the extension’s <a data-link-type="dfn" href="#client-extension-input" id="ref-for-client-extension-input①⑦">client extension input</a> as the value.</p>
    <p>Likewise, the <a data-link-type="dfn" href="#client-extension-output" id="ref-for-client-extension-output①⑤">client extension outputs</a> are represented as a dictionary in the result of <code class="idl"><a data-link-type="idl" href="#dom-publickeycredential-getclientextensionresults" id="ref-for-dom-publickeycredential-getclientextensionresults④">getClientExtensionResults()</a></code> with <a data-link-type="dfn" href="#extension-identifier" id="ref-for-extension-identifier①⑦">extension identifiers</a> as keys, and the <dfn class="dfn-paneled" data-dfn-type="dfn" data-noexport id="client-extension-output">client extension output</dfn> value of each extension as the value.
@@ -6025,7 +6103,7 @@ <h3 class="heading settled" data-level="9.4" id="sctn-client-extension-processin
 the process by which the <a data-link-type="dfn" href="#cbor" id="ref-for-cbor①⑧">CBOR</a> <a data-link-type="dfn" href="#authenticator-extension-output" id="ref-for-authenticator-extension-output①③">authenticator extension output</a> can be used to determine the <a data-link-type="dfn" href="#client-extension-output" id="ref-for-client-extension-output①⑦">client extension output</a>.</p>
    <h3 class="heading settled" data-level="9.5" id="sctn-authenticator-extension-processing"><span class="secno">9.5. </span><span class="content"><dfn class="dfn-paneled" data-dfn-type="dfn" data-noexport id="authenticator-extension-processing">Authenticator Extension Processing</dfn></span><a class="self-link" href="#sctn-authenticator-extension-processing"></a></h3>
    <p>The <a data-link-type="dfn" href="#cbor" id="ref-for-cbor①⑨">CBOR</a> <a data-link-type="dfn" href="#authenticator-extension-input" id="ref-for-authenticator-extension-input①⑤">authenticator extension input</a> value of each processed <a data-link-type="dfn" href="#authenticator-extension" id="ref-for-authenticator-extension①①">authenticator extension</a> is included in the <var>extensions</var> parameter of the <a data-link-type="dfn" href="#authenticatormakecredential" id="ref-for-authenticatormakecredential①⑧">authenticatorMakeCredential</a> and <a data-link-type="dfn" href="#authenticatorgetassertion" id="ref-for-authenticatorgetassertion①⑧">authenticatorGetAssertion</a> operations. The <var>extensions</var> parameter is a <a data-link-type="dfn" href="#cbor" id="ref-for-cbor②⓪">CBOR</a> map where each key is an <a data-link-type="dfn" href="#extension-identifier" id="ref-for-extension-identifier①⑧">extension identifier</a> and the corresponding value is the <a data-link-type="dfn" href="#authenticator-extension-input" id="ref-for-authenticator-extension-input①⑥">authenticator extension input</a> for that extension.</p>
-   <p>Likewise, the extension output is represented in the <a data-link-type="dfn" href="#authdata-extensions" id="ref-for-authdata-extensions⑨">extensions</a> part of the <a data-link-type="dfn" href="#authenticator-data" id="ref-for-authenticator-data④⑤">authenticator data</a>. The <a data-link-type="dfn" href="#authdata-extensions" id="ref-for-authdata-extensions①⓪">extensions</a> part of the <a data-link-type="dfn" href="#authenticator-data" id="ref-for-authenticator-data④⑥">authenticator data</a> is a CBOR map where each key is an <a data-link-type="dfn" href="#extension-identifier" id="ref-for-extension-identifier①⑨">extension identifier</a> and the corresponding value is the <dfn class="dfn-paneled" data-dfn-type="dfn" data-noexport id="authenticator-extension-output">authenticator extension output</dfn> for that extension.</p>
+   <p>Likewise, the extension output is represented in the <a data-link-type="dfn" href="#authdata-extensions" id="ref-for-authdata-extensions⑨">extensions</a> part of the <a data-link-type="dfn" href="#authenticator-data" id="ref-for-authenticator-data④⑦">authenticator data</a>. The <a data-link-type="dfn" href="#authdata-extensions" id="ref-for-authdata-extensions①⓪">extensions</a> part of the <a data-link-type="dfn" href="#authenticator-data" id="ref-for-authenticator-data④⑧">authenticator data</a> is a CBOR map where each key is an <a data-link-type="dfn" href="#extension-identifier" id="ref-for-extension-identifier①⑨">extension identifier</a> and the corresponding value is the <dfn class="dfn-paneled" data-dfn-type="dfn" data-noexport id="authenticator-extension-output">authenticator extension output</dfn> for that extension.</p>
    <p>For each supported extension, the <a data-link-type="dfn" href="#authenticator-extension-processing" id="ref-for-authenticator-extension-processing④">authenticator extension processing</a> rule for that extension is used create the <a data-link-type="dfn" href="#authenticator-extension-output" id="ref-for-authenticator-extension-output①④">authenticator extension output</a> from the <a data-link-type="dfn" href="#authenticator-extension-input" id="ref-for-authenticator-extension-input①⑦">authenticator extension input</a> and possibly also other inputs.
 There MUST NOT be any values returned for ignored extensions.</p>
    <h2 class="heading settled" data-level="10" id="sctn-defined-extensions"><span class="secno">10. </span><span class="content">Defined Extensions</span><a class="self-link" href="#sctn-defined-extensions"></a></h2>
@@ -6037,23 +6115,23 @@ <h3 class="heading settled" data-level="10.1" id="sctn-defined-client-extensions
    <h4 class="heading settled" data-level="10.1.1" id="sctn-appid-extension"><span class="secno">10.1.1. </span><span class="content">FIDO <dfn class="dfn-paneled" data-dfn-type="dfn" data-noexport id="appid">AppID</dfn> Extension (appid)</span><a class="self-link" href="#sctn-appid-extension"></a></h4>
    <p>This extension allows <a data-link-type="dfn" href="#webauthn-relying-party" id="ref-for-webauthn-relying-party③⑤">WebAuthn Relying Parties</a> that have previously registered a
 credential using the legacy FIDO U2F JavaScript API <a data-link-type="biblio" href="#biblio-fidou2fjavascriptapi">[FIDOU2FJavaScriptAPI]</a> to request an <a data-link-type="dfn" href="#assertion" id="ref-for-assertion③">assertion</a>. The
-FIDO APIs use an alternative identifier for <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party②⑥④">Relying Parties</a> called an <var>AppID</var> <a data-link-type="biblio" href="#biblio-fido-appid">[FIDO-APPID]</a>, and any credentials created using those APIs will be <a data-link-type="dfn" href="#scope" id="ref-for-scope①⑧">scoped</a> to
+FIDO APIs use an alternative identifier for <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party②⑦①">Relying Parties</a> called an <var>AppID</var> <a data-link-type="biblio" href="#biblio-fido-appid">[FIDO-APPID]</a>, and any credentials created using those APIs will be <a data-link-type="dfn" href="#scope" id="ref-for-scope①⑧">scoped</a> to
 that identifier. Without this extension, they would need to be re-registered in
 order to be <a data-link-type="dfn" href="#scope" id="ref-for-scope①⑨">scoped</a> to an <a data-link-type="dfn" href="#rp-id" id="ref-for-rp-id④①">RP ID</a>.</p>
    <p>In addition to setting the <code class="idl"><a data-link-type="idl" href="#dom-authenticationextensionsclientinputs-appid" id="ref-for-dom-authenticationextensionsclientinputs-appid">appid</a></code> extension input,
-using this extension requires some additional processing by the <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party②⑥⑤">Relying Party</a> in order to allow users to <a data-link-type="dfn" href="#authentication" id="ref-for-authentication①③">authenticate</a> using their registered U2F credentials:</p>
+using this extension requires some additional processing by the <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party②⑦②">Relying Party</a> in order to allow users to <a data-link-type="dfn" href="#authentication" id="ref-for-authentication①③">authenticate</a> using their registered U2F credentials:</p>
    <ol>
     <li data-md>
-     <p>List the desired U2F credentials in the <code class="idl"><a data-link-type="idl" href="#dom-publickeycredentialrequestoptions-allowcredentials" id="ref-for-dom-publickeycredentialrequestoptions-allowcredentials①⑨">allowCredentials</a></code> option
- of the <code class="idl"><a data-link-type="idl" href="https://w3c.github.io/webappsec-credential-management/#dom-credentialscontainer-get" id="ref-for-dom-credentialscontainer-get③⑦">get()</a></code> method:</p>
+     <p>List the desired U2F credentials in the <code class="idl"><a data-link-type="idl" href="#dom-publickeycredentialrequestoptions-allowcredentials" id="ref-for-dom-publickeycredentialrequestoptions-allowcredentials①⑦">allowCredentials</a></code> option
+ of the <code class="idl"><a data-link-type="idl" href="https://w3c.github.io/webappsec-credential-management/#dom-credentialscontainer-get" id="ref-for-dom-credentialscontainer-get③⑥">get()</a></code> method:</p>
      <ul>
       <li data-md>
-       <p>Set the <code class="idl"><a data-link-type="idl" href="#dom-publickeycredentialdescriptor-type" id="ref-for-dom-publickeycredentialdescriptor-type④">type</a></code> members to <code class="idl"><a data-link-type="idl" href="#dom-publickeycredentialtype-public-key" id="ref-for-dom-publickeycredentialtype-public-key⑤">public-key</a></code>.</p>
+       <p>Set the <code class="idl"><a data-link-type="idl" href="#dom-publickeycredentialdescriptor-type" id="ref-for-dom-publickeycredentialdescriptor-type⑤">type</a></code> members to <code class="idl"><a data-link-type="idl" href="#dom-publickeycredentialtype-public-key" id="ref-for-dom-publickeycredentialtype-public-key⑤">public-key</a></code>.</p>
       <li data-md>
-       <p>Set the <code class="idl"><a data-link-type="idl" href="#dom-publickeycredentialdescriptor-id" id="ref-for-dom-publickeycredentialdescriptor-id⑧">id</a></code> members to the respective U2F key handles of the desired credentials. Note that U2F key handles commonly use <a data-link-type="dfn" href="#base64url-encoding" id="ref-for-base64url-encoding①④">base64url encoding</a> but must be decoded to their binary form when used in <code class="idl"><a data-link-type="idl" href="#dom-publickeycredentialdescriptor-id" id="ref-for-dom-publickeycredentialdescriptor-id⑨">id</a></code>.</p>
+       <p>Set the <code class="idl"><a data-link-type="idl" href="#dom-publickeycredentialdescriptor-id" id="ref-for-dom-publickeycredentialdescriptor-id⑨">id</a></code> members to the respective U2F key handles of the desired credentials. Note that U2F key handles commonly use <a data-link-type="dfn" href="#base64url-encoding" id="ref-for-base64url-encoding①③">base64url encoding</a> but must be decoded to their binary form when used in <code class="idl"><a data-link-type="idl" href="#dom-publickeycredentialdescriptor-id" id="ref-for-dom-publickeycredentialdescriptor-id①⓪">id</a></code>.</p>
      </ul>
-     <p><code class="idl"><a data-link-type="idl" href="#dom-publickeycredentialrequestoptions-allowcredentials" id="ref-for-dom-publickeycredentialrequestoptions-allowcredentials②⓪">allowCredentials</a></code> MAY contain a mixture
- of both WebAuthn <a data-link-type="dfn" href="#credential-id" id="ref-for-credential-id③⑥">credential IDs</a> and U2F key handles;
+     <p><code class="idl"><a data-link-type="idl" href="#dom-publickeycredentialrequestoptions-allowcredentials" id="ref-for-dom-publickeycredentialrequestoptions-allowcredentials①⑧">allowCredentials</a></code> MAY contain a mixture
+ of both WebAuthn <a data-link-type="dfn" href="#credential-id" id="ref-for-credential-id③⑦">credential IDs</a> and U2F key handles;
  stating the <code class="idl"><a data-link-type="idl" href="#dom-authenticationextensionsclientinputs-appid" id="ref-for-dom-authenticationextensionsclientinputs-appid①">appid</a></code> via this extension
  does not prevent the user from using a WebAuthn-registered credential
  scoped to the <a data-link-type="dfn" href="#rp-id" id="ref-for-rp-id④②">RP ID</a> stated in <code class="idl"><a data-link-type="idl" href="#dom-publickeycredentialrequestoptions-rpid" id="ref-for-dom-publickeycredentialrequestoptions-rpid⑤">rpId</a></code>.</p>
@@ -6064,8 +6142,8 @@ <h4 class="heading settled" data-level="10.1.1" id="sctn-appid-extension"><span
 credentials created with WebAuthn are not backwards compatible with the FIDO
 JavaScript APIs.</p>
    <p class="note" role="note"><span>Note:</span> <code class="idl"><a data-link-type="idl" href="#dom-authenticationextensionsclientinputs-appid" id="ref-for-dom-authenticationextensionsclientinputs-appid②">appid</a></code> should be set to the AppID
-that the <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party②⑥⑥">Relying Party</a> <em>previously</em> used in the legacy FIDO APIs.
-This might not be the same as the result of translating the <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party②⑥⑦">Relying Party</a>'s WebAuthn <a data-link-type="dfn" href="#rp-id" id="ref-for-rp-id④④">RP ID</a> to the AppID format,
+that the <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party②⑦③">Relying Party</a> <em>previously</em> used in the legacy FIDO APIs.
+This might not be the same as the result of translating the <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party②⑦④">Relying Party</a>'s WebAuthn <a data-link-type="dfn" href="#rp-id" id="ref-for-rp-id④④">RP ID</a> to the AppID format,
 e.g., the previously used AppID may have been "https://accounts.example.com"
 but the currently used <a data-link-type="dfn" href="#rp-id" id="ref-for-rp-id④⑤">RP ID</a> might be "example.com".</p>
    <dl>
@@ -6112,7 +6190,7 @@ <h4 class="heading settled" data-level="10.1.1" id="sctn-appid-extension"><span
    <dl>
     <dt data-md>Client extension output
     <dd data-md>
-     <p>Returns the value of <var>output</var>. If true, the <var>AppID</var> was used and thus, when <a href="#rp-op-verifying-assertion-step-rpid-hash">verifying the assertion</a>, the <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party②⑥⑧">Relying Party</a> MUST expect the <code><a data-link-type="dfn" href="#authdata-rpidhash" id="ref-for-authdata-rpidhash⑤">rpIdHash</a></code> to be the hash of the <var>AppID</var>, not the <a data-link-type="dfn" href="#rp-id" id="ref-for-rp-id④⑦">RP ID</a>.</p>
+     <p>Returns the value of <var>output</var>. If true, the <var>AppID</var> was used and thus, when <a href="#rp-op-verifying-assertion-step-rpid-hash">verifying the assertion</a>, the <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party②⑦⑤">Relying Party</a> MUST expect the <code><a data-link-type="dfn" href="#authdata-rpidhash" id="ref-for-authdata-rpidhash⑤">rpIdHash</a></code> to be the hash of the <var>AppID</var>, not the <a data-link-type="dfn" href="#rp-id" id="ref-for-rp-id④⑦">RP ID</a>.</p>
 <pre class="idl highlight def"><c- b>partial</c-> <c- b>dictionary</c-> <a class="idl-code" data-link-type="dictionary" href="#dictdef-authenticationextensionsclientoutputs" id="ref-for-dictdef-authenticationextensionsclientoutputs⑤"><c- g>AuthenticationExtensionsClientOutputs</c-></a> {
   <a class="idl-code" data-link-type="interface" href="https://webidl.spec.whatwg.org/#idl-boolean" id="ref-for-idl-boolean⑥"><c- b>boolean</c-></a> <dfn class="idl-code" data-dfn-for="AuthenticationExtensionsClientOutputs" data-dfn-type="dict-member" data-export data-type="boolean " id="dom-authenticationextensionsclientoutputs-appid"><code><c- g>appid</c-></code><a class="self-link" href="#dom-authenticationextensionsclientoutputs-appid"></a></dfn>;
 };
@@ -6129,7 +6207,7 @@ <h4 class="heading settled" data-level="10.1.1" id="sctn-appid-extension"><span
    </dl>
    <h4 class="heading settled" data-level="10.1.2" id="sctn-appid-exclude-extension"><span class="secno">10.1.2. </span><span class="content">FIDO AppID Exclusion Extension (appidExclude)</span><a class="self-link" href="#sctn-appid-exclude-extension"></a></h4>
    <p>This registration extension allows <a data-link-type="dfn" href="#webauthn-relying-party" id="ref-for-webauthn-relying-party③⑥">WebAuthn Relying Parties</a> to exclude authenticators that contain specified credentials that were created with the legacy FIDO U2F JavaScript API <a data-link-type="biblio" href="#biblio-fidou2fjavascriptapi">[FIDOU2FJavaScriptAPI]</a>.</p>
-   <p>During a transition from the FIDO U2F JavaScript API, a <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party②⑥⑨">Relying Party</a> may have a population of users with legacy credentials already registered. The <a href="#sctn-appid-extension">appid</a> extension allows the sign-in flow to be transitioned smoothly but, when transitioning the registration flow, the <a href="#dom-publickeycredentialcreationoptions-excludecredentials" id="ref-for-dom-publickeycredentialcreationoptions-excludecredentials⑤">excludeCredentials</a> field will not be effective in excluding authenticators with legacy credentials because its contents are taken to be WebAuthn credentials. This extension directs <a data-link-type="dfn" href="#client-platform" id="ref-for-client-platform④⑨">client platforms</a> to consider the contents of <a href="#dom-publickeycredentialcreationoptions-excludecredentials" id="ref-for-dom-publickeycredentialcreationoptions-excludecredentials⑥">excludeCredentials</a> as both WebAuthn and legacy FIDO credentials. Note that U2F key handles commonly use <a data-link-type="dfn" href="#base64url-encoding" id="ref-for-base64url-encoding①⑤">base64url encoding</a> but must be decoded to their binary form when used in <a href="#dom-publickeycredentialcreationoptions-excludecredentials" id="ref-for-dom-publickeycredentialcreationoptions-excludecredentials⑦">excludeCredentials</a>.</p>
+   <p>During a transition from the FIDO U2F JavaScript API, a <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party②⑦⑥">Relying Party</a> may have a population of users with legacy credentials already registered. The <a href="#sctn-appid-extension">appid</a> extension allows the sign-in flow to be transitioned smoothly but, when transitioning the registration flow, the <a href="#dom-publickeycredentialcreationoptions-excludecredentials" id="ref-for-dom-publickeycredentialcreationoptions-excludecredentials⑤">excludeCredentials</a> field will not be effective in excluding authenticators with legacy credentials because its contents are taken to be WebAuthn credentials. This extension directs <a data-link-type="dfn" href="#client-platform" id="ref-for-client-platform④⑨">client platforms</a> to consider the contents of <a href="#dom-publickeycredentialcreationoptions-excludecredentials" id="ref-for-dom-publickeycredentialcreationoptions-excludecredentials⑥">excludeCredentials</a> as both WebAuthn and legacy FIDO credentials. Note that U2F key handles commonly use <a data-link-type="dfn" href="#base64url-encoding" id="ref-for-base64url-encoding①④">base64url encoding</a> but must be decoded to their binary form when used in <a href="#dom-publickeycredentialcreationoptions-excludecredentials" id="ref-for-dom-publickeycredentialcreationoptions-excludecredentials⑦">excludeCredentials</a>.</p>
    <dl>
     <dt data-md>Extension identifier
     <dd data-md>
@@ -6168,7 +6246,7 @@ <h4 class="heading settled" data-level="10.1.2" id="sctn-appid-exclude-extension
        <p>Just prior to <a href="#CreateCred-InvokeAuthnrMakeCred">invoking authenticatorMakeCredential</a> perform these steps:</p>
        <ol>
         <li data-md>
-         <p>If <var>authenticator</var> supports the U2F protocol <a data-link-type="biblio" href="#biblio-fido-u2f-message-formats">[FIDO-U2F-Message-Formats]</a>, then <a data-link-type="dfn" href="https://infra.spec.whatwg.org/#list-iterate" id="ref-for-list-iterate①⑨">for each</a> <a href="#dictdef-publickeycredentialdescriptor" id="ref-for-dictdef-publickeycredentialdescriptor①③">credential descriptor</a> <var>C</var> in <var>excludeCredentialDescriptorList</var>:</p>
+         <p>If <var>authenticator</var> supports the U2F protocol <a data-link-type="biblio" href="#biblio-fido-u2f-message-formats">[FIDO-U2F-Message-Formats]</a>, then <a data-link-type="dfn" href="https://infra.spec.whatwg.org/#list-iterate" id="ref-for-list-iterate①⑨">for each</a> <a href="#dictdef-publickeycredentialdescriptor" id="ref-for-dictdef-publickeycredentialdescriptor①④">credential descriptor</a> <var>C</var> in <var>excludeCredentialDescriptorList</var>:</p>
          <ol>
           <li data-md>
            <p>Check whether <var>C</var> was created using U2F on <var>authenticator</var> by sending a <code>U2F_AUTHENTICATE</code> message to <var>authenticator</var> whose "five parts" are set to the following values:</p>
@@ -6184,10 +6262,10 @@ <h4 class="heading settled" data-level="10.1.2" id="sctn-appid-exclude-extension
              <p>SHA-256 hash of <var>appId</var></p>
             <dt data-md><var>key handle length</var>
             <dd data-md>
-             <p>The length of <code><var>C</var>.<code class="idl"><a data-link-type="idl" href="#dom-publickeycredentialdescriptor-id" id="ref-for-dom-publickeycredentialdescriptor-id①⓪">id</a></code></code> (in bytes)</p>
+             <p>The length of <code><var>C</var>.<code class="idl"><a data-link-type="idl" href="#dom-publickeycredentialdescriptor-id" id="ref-for-dom-publickeycredentialdescriptor-id①①">id</a></code></code> (in bytes)</p>
             <dt data-md><var>key handle</var>
             <dd data-md>
-             <p>The value of <code><var>C</var>.<code class="idl"><a data-link-type="idl" href="#dom-publickeycredentialdescriptor-id" id="ref-for-dom-publickeycredentialdescriptor-id①①">id</a></code></code>, i.e., the <a data-link-type="dfn" href="#credential-id" id="ref-for-credential-id③⑦">credential id</a>.</p>
+             <p>The value of <code><var>C</var>.<code class="idl"><a data-link-type="idl" href="#dom-publickeycredentialdescriptor-id" id="ref-for-dom-publickeycredentialdescriptor-id①②">id</a></code></code>, i.e., the <a data-link-type="dfn" href="#credential-id" id="ref-for-credential-id③⑧">credential id</a>.</p>
            </dl>
           <li data-md>
            <p>If <var>authenticator</var> responds with <code>message:error:test-of-user-presence-required</code> (i.e., success):
@@ -6204,7 +6282,7 @@ <h4 class="heading settled" data-level="10.1.2" id="sctn-appid-exclude-extension
      </ol>
     <dt data-md>Client extension output
     <dd data-md>
-     <p>Returns the value <code>true</code> to indicate to the <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party②⑦⓪">Relying Party</a> that the extension was acted upon.</p>
+     <p>Returns the value <code>true</code> to indicate to the <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party②⑦⑦">Relying Party</a> that the extension was acted upon.</p>
 <pre class="idl highlight def"><c- b>partial</c-> <c- b>dictionary</c-> <a class="idl-code" data-link-type="dictionary" href="#dictdef-authenticationextensionsclientoutputs" id="ref-for-dictdef-authenticationextensionsclientoutputs⑥"><c- g>AuthenticationExtensionsClientOutputs</c-></a> {
   <a class="idl-code" data-link-type="interface" href="https://webidl.spec.whatwg.org/#idl-boolean" id="ref-for-idl-boolean⑦"><c- b>boolean</c-></a> <dfn class="idl-code" data-dfn-for="AuthenticationExtensionsClientOutputs" data-dfn-type="dict-member" data-export data-type="boolean " id="dom-authenticationextensionsclientoutputs-appidexclude"><code><c- g>appidExclude</c-></code><a class="self-link" href="#dom-authenticationextensionsclientoutputs-appidexclude"></a></dfn>;
 };
@@ -6220,7 +6298,7 @@ <h4 class="heading settled" data-level="10.1.2" id="sctn-appid-exclude-extension
      <p>None.</p>
    </dl>
    <h4 class="heading settled" data-level="10.1.3" id="sctn-authenticator-credential-properties-extension"><span class="secno">10.1.3. </span><span class="content">Credential Properties Extension (<dfn class="dfn-paneled" data-dfn-type="dfn" data-noexport id="credprops">credProps</dfn>)</span><a class="self-link" href="#sctn-authenticator-credential-properties-extension"></a></h4>
-   <p>This <a data-link-type="dfn" href="#client-extension" id="ref-for-client-extension⑧">client</a> <a data-link-type="dfn" href="#registration-extension" id="ref-for-registration-extension⑨">registration extension</a> facilitates reporting certain <a data-link-type="dfn" href="#credential-properties" id="ref-for-credential-properties②">credential properties</a> known by the <a data-link-type="dfn" href="#client" id="ref-for-client⑧⑦">client</a> to the requesting <a data-link-type="dfn" href="#webauthn-relying-party" id="ref-for-webauthn-relying-party③⑦">WebAuthn Relying Party</a> upon creation of a <a data-link-type="dfn" href="#public-key-credential-source" id="ref-for-public-key-credential-source④⑧">public key credential source</a> as a result of a <a data-link-type="dfn" href="#registration-ceremony" id="ref-for-registration-ceremony①②">registration ceremony</a>.</p>
+   <p>This <a data-link-type="dfn" href="#client-extension" id="ref-for-client-extension⑧">client</a> <a data-link-type="dfn" href="#registration-extension" id="ref-for-registration-extension⑨">registration extension</a> facilitates reporting certain <a data-link-type="dfn" href="#credential-properties" id="ref-for-credential-properties②">credential properties</a> known by the <a data-link-type="dfn" href="#client" id="ref-for-client⑧⑥">client</a> to the requesting <a data-link-type="dfn" href="#webauthn-relying-party" id="ref-for-webauthn-relying-party③⑦">WebAuthn Relying Party</a> upon creation of a <a data-link-type="dfn" href="#public-key-credential-source" id="ref-for-public-key-credential-source⑤⑦">public key credential source</a> as a result of a <a data-link-type="dfn" href="#registration-ceremony" id="ref-for-registration-ceremony①②">registration ceremony</a>.</p>
    <p>At this time, one <a data-link-type="dfn" href="#credential-properties" id="ref-for-credential-properties③">credential property</a> is defined: the <a data-link-type="dfn" href="#credentialpropertiesoutput-resident-key-credential-property" id="ref-for-credentialpropertiesoutput-resident-key-credential-property①">resident key credential property</a> (i.e., <a data-link-type="dfn" href="#credentialpropertiesoutput-client-side-discoverable-credential-property" id="ref-for-credentialpropertiesoutput-client-side-discoverable-credential-property">client-side discoverable credential property</a>).</p>
    <dl>
     <dt data-md>Extension identifier
@@ -6231,7 +6309,7 @@ <h4 class="heading settled" data-level="10.1.3" id="sctn-authenticator-credentia
      <p><a data-link-type="dfn" href="#registration-extension" id="ref-for-registration-extension①⓪">Registration</a></p>
     <dt data-md>Client extension input
     <dd data-md>
-     <p>The Boolean value <code>true</code> to indicate that this extension is requested by the <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party②⑦①">Relying Party</a>.</p>
+     <p>The Boolean value <code>true</code> to indicate that this extension is requested by the <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party②⑦⑧">Relying Party</a>.</p>
 <pre class="idl highlight def"><c- b>partial</c-> <c- b>dictionary</c-> <a class="idl-code" data-link-type="dictionary" href="#dictdef-authenticationextensionsclientinputs" id="ref-for-dictdef-authenticationextensionsclientinputs⑧"><c- g>AuthenticationExtensionsClientInputs</c-></a> {
     <a class="idl-code" data-link-type="interface" href="https://webidl.spec.whatwg.org/#idl-boolean" id="ref-for-idl-boolean⑧"><c- b>boolean</c-></a> <dfn class="idl-code" data-dfn-for="AuthenticationExtensionsClientInputs" data-dfn-type="dict-member" data-export data-type="boolean " id="dom-authenticationextensionsclientinputs-credprops"><code><c- g>credProps</c-></code><a class="self-link" href="#dom-authenticationextensionsclientinputs-credprops"></a></dfn>;
 };
@@ -6259,7 +6337,7 @@ <h4 class="heading settled" data-level="10.1.3" id="sctn-authenticator-credentia
 If <code class="idl"><a data-link-type="idl" href="#dom-credentialpropertiesoutput-rk" id="ref-for-dom-credentialpropertiesoutput-rk②">rk</a></code> is <code>true</code>, the credential is a <a data-link-type="dfn" href="#discoverable-credential" id="ref-for-discoverable-credential①②">discoverable credential</a>.
 If <code class="idl"><a data-link-type="idl" href="#dom-credentialpropertiesoutput-rk" id="ref-for-dom-credentialpropertiesoutput-rk③">rk</a></code> is <code>false</code>, the credential is a <a data-link-type="dfn" href="#server-side-credential" id="ref-for-server-side-credential①②">server-side credential</a>.
 If <code class="idl"><a data-link-type="idl" href="#dom-credentialpropertiesoutput-rk" id="ref-for-dom-credentialpropertiesoutput-rk④">rk</a></code> is not present, it is not known whether the credential is a <a data-link-type="dfn" href="#discoverable-credential" id="ref-for-discoverable-credential①③">discoverable credential</a> or a <a data-link-type="dfn" href="#server-side-credential" id="ref-for-server-side-credential①③">server-side credential</a>.</p>
-        <p class="note" role="note"><span>Note:</span> some <a data-link-type="dfn" href="#authenticator" id="ref-for-authenticator②②⑥">authenticators</a> create <a data-link-type="dfn" href="#discoverable-credential" id="ref-for-discoverable-credential①④">discoverable credentials</a> even when not requested by the <a data-link-type="dfn" href="#client-platform" id="ref-for-client-platform⑤⓪">client platform</a>. Because of this, <a data-link-type="dfn" href="#client-platform" id="ref-for-client-platform⑤①">client platforms</a> may be forced to omit the <code class="idl"><a data-link-type="idl" href="#dom-credentialpropertiesoutput-rk" id="ref-for-dom-credentialpropertiesoutput-rk⑤">rk</a></code> property because they lack the assurance to be able to set it to <code>false</code>. <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party②⑦②">Relying Parties</a> should assume that, if the <code>credProps</code> extension is supported, then <a data-link-type="dfn" href="#client-platform" id="ref-for-client-platform⑤②">client platforms</a> will endeavour to populate the <code class="idl"><a data-link-type="idl" href="#dom-credentialpropertiesoutput-rk" id="ref-for-dom-credentialpropertiesoutput-rk⑥">rk</a></code> property. Therefore a missing <code class="idl"><a data-link-type="idl" href="#dom-credentialpropertiesoutput-rk" id="ref-for-dom-credentialpropertiesoutput-rk⑦">rk</a></code> indicates that the created credential is most likely a <a data-link-type="dfn" href="#non-discoverable-credential" id="ref-for-non-discoverable-credential③">non-discoverable credential</a>.</p>
+        <p class="note" role="note"><span>Note:</span> some <a data-link-type="dfn" href="#authenticator" id="ref-for-authenticator②②⑤">authenticators</a> create <a data-link-type="dfn" href="#discoverable-credential" id="ref-for-discoverable-credential①④">discoverable credentials</a> even when not requested by the <a data-link-type="dfn" href="#client-platform" id="ref-for-client-platform⑤⓪">client platform</a>. Because of this, <a data-link-type="dfn" href="#client-platform" id="ref-for-client-platform⑤①">client platforms</a> may be forced to omit the <code class="idl"><a data-link-type="idl" href="#dom-credentialpropertiesoutput-rk" id="ref-for-dom-credentialpropertiesoutput-rk⑤">rk</a></code> property because they lack the assurance to be able to set it to <code>false</code>. <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party②⑦⑨">Relying Parties</a> should assume that, if the <code>credProps</code> extension is supported, then <a data-link-type="dfn" href="#client-platform" id="ref-for-client-platform⑤②">client platforms</a> will endeavour to populate the <code class="idl"><a data-link-type="idl" href="#dom-credentialpropertiesoutput-rk" id="ref-for-dom-credentialpropertiesoutput-rk⑥">rk</a></code> property. Therefore a missing <code class="idl"><a data-link-type="idl" href="#dom-credentialpropertiesoutput-rk" id="ref-for-dom-credentialpropertiesoutput-rk⑦">rk</a></code> indicates that the created credential is most likely a <a data-link-type="dfn" href="#non-discoverable-credential" id="ref-for-non-discoverable-credential③">non-discoverable credential</a>.</p>
       </dl>
      </div>
     <dt data-md>Authenticator extension input
@@ -6273,11 +6351,11 @@ <h4 class="heading settled" data-level="10.1.3" id="sctn-authenticator-credentia
      <p>None.</p>
    </dl>
    <h4 class="heading settled" data-level="10.1.4" id="prf-extension"><span class="secno">10.1.4. </span><span class="content">Pseudo-random function extension (<dfn class="dfn-paneled" data-dfn-type="dfn" data-noexport id="prf">prf</dfn>)</span><a class="self-link" href="#prf-extension"></a></h4>
-   <p>This <a data-link-type="dfn" href="#client-extension" id="ref-for-client-extension⑨">client</a> <a data-link-type="dfn" href="#registration-extension" id="ref-for-registration-extension①①">registration extension</a> and <a data-link-type="dfn" href="#authentication-extension" id="ref-for-authentication-extension⑨">authentication extension</a> allows a <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party②⑦③">Relying Party</a> to evaluate outputs from a pseudo-random function (PRF) associated with a <a data-link-type="dfn" href="https://w3c.github.io/webappsec-credential-management/#concept-credential" id="ref-for-concept-credential①⑧">credential</a>. The PRFs provided by this extension map from <code class="idl"><a data-link-type="idl" href="https://webidl.spec.whatwg.org/#idl-USVString" id="ref-for-idl-USVString④">USVString</a></code>s of any length to 32-byte <code class="idl"><a data-link-type="idl" href="https://webidl.spec.whatwg.org/#idl-ArrayBuffer" id="ref-for-idl-ArrayBuffer②⑦">ArrayBuffer</a></code>s.</p>
-   <p>When requested, if a <a data-link-type="dfn" href="https://w3c.github.io/webappsec-credential-management/#concept-credential" id="ref-for-concept-credential①⑨">credential</a> is created on an <a data-link-type="dfn" href="#authenticator" id="ref-for-authenticator②②⑦">authenticator</a> that supports this extension then either one or two freshly-seeded PRFs are associated with it. If two PRFs are associated then, when outputs are requested, one PRF is evaluated if <a data-link-type="dfn" href="#user-verification" id="ref-for-user-verification④③">user verification</a> is performed and the other is evaluated if only a <a data-link-type="dfn" href="#test-of-user-presence" id="ref-for-test-of-user-presence①③">user presence test</a> is performed. It is the responsibility of the <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party②⑦④">Relying Party</a> to set the <code class="idl"><a data-link-type="idl" href="#dom-publickeycredentialrequestoptions-userverification" id="ref-for-dom-publickeycredentialrequestoptions-userverification⑤">userVerification</a></code> parameter accordingly: <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party②⑦⑤">Relying Parties</a> SHOULD <em>consistently</em> use either the <code class="idl"><a data-link-type="idl" href="#dom-userverificationrequirement-required" id="ref-for-dom-userverificationrequirement-required⑧">required</a></code> or <code class="idl"><a data-link-type="idl" href="#dom-userverificationrequirement-discouraged" id="ref-for-dom-userverificationrequirement-discouraged⑤">discouraged</a></code> values of <code class="idl"><a data-link-type="idl" href="#enumdef-userverificationrequirement" id="ref-for-enumdef-userverificationrequirement⑥">UserVerificationRequirement</a></code> when using this extension, otherwise the outputs may vary for a given input. To avoid mistakes, the default value of <code class="idl"><a data-link-type="idl" href="#dom-userverificationrequirement-preferred" id="ref-for-dom-userverificationrequirement-preferred⑤">preferred</a></code> is prohibited when using this extension during <a data-link-type="dfn" href="#assertion" id="ref-for-assertion⑤">assertion</a> because that could cause the PRF used to vary between operations if <a data-link-type="dfn" href="#user-verification" id="ref-for-user-verification④④">user verification</a> is later enabled on an <a data-link-type="dfn" href="#authenticator" id="ref-for-authenticator②②⑧">authenticator</a>.</p>
+   <p>This <a data-link-type="dfn" href="#client-extension" id="ref-for-client-extension⑨">client</a> <a data-link-type="dfn" href="#registration-extension" id="ref-for-registration-extension①①">registration extension</a> and <a data-link-type="dfn" href="#authentication-extension" id="ref-for-authentication-extension⑨">authentication extension</a> allows a <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party②⑧⓪">Relying Party</a> to evaluate outputs from a pseudo-random function (PRF) associated with a <a data-link-type="dfn" href="https://w3c.github.io/webappsec-credential-management/#concept-credential" id="ref-for-concept-credential①⑧">credential</a>. The PRFs provided by this extension map from <code class="idl"><a data-link-type="idl" href="https://webidl.spec.whatwg.org/#idl-USVString" id="ref-for-idl-USVString④">USVString</a></code>s of any length to 32-byte <code class="idl"><a data-link-type="idl" href="https://webidl.spec.whatwg.org/#idl-ArrayBuffer" id="ref-for-idl-ArrayBuffer②⑦">ArrayBuffer</a></code>s.</p>
+   <p>When requested, if a <a data-link-type="dfn" href="https://w3c.github.io/webappsec-credential-management/#concept-credential" id="ref-for-concept-credential①⑨">credential</a> is created on an <a data-link-type="dfn" href="#authenticator" id="ref-for-authenticator②②⑥">authenticator</a> that supports this extension then either one or two freshly-seeded PRFs are associated with it. If two PRFs are associated then, when outputs are requested, one PRF is evaluated if <a data-link-type="dfn" href="#user-verification" id="ref-for-user-verification④③">user verification</a> is performed and the other is evaluated if only a <a data-link-type="dfn" href="#test-of-user-presence" id="ref-for-test-of-user-presence①③">user presence test</a> is performed. It is the responsibility of the <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party②⑧①">Relying Party</a> to set the <code class="idl"><a data-link-type="idl" href="#dom-publickeycredentialrequestoptions-userverification" id="ref-for-dom-publickeycredentialrequestoptions-userverification⑤">userVerification</a></code> parameter accordingly: <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party②⑧②">Relying Parties</a> SHOULD <em>consistently</em> use either the <code class="idl"><a data-link-type="idl" href="#dom-userverificationrequirement-required" id="ref-for-dom-userverificationrequirement-required⑧">required</a></code> or <code class="idl"><a data-link-type="idl" href="#dom-userverificationrequirement-discouraged" id="ref-for-dom-userverificationrequirement-discouraged⑤">discouraged</a></code> values of <code class="idl"><a data-link-type="idl" href="#enumdef-userverificationrequirement" id="ref-for-enumdef-userverificationrequirement⑥">UserVerificationRequirement</a></code> when using this extension, otherwise the outputs may vary for a given input. To avoid mistakes, the default value of <code class="idl"><a data-link-type="idl" href="#dom-userverificationrequirement-preferred" id="ref-for-dom-userverificationrequirement-preferred⑤">preferred</a></code> is prohibited when using this extension during <a data-link-type="dfn" href="#assertion" id="ref-for-assertion⑤">assertion</a> because that could cause the PRF used to vary between operations if <a data-link-type="dfn" href="#user-verification" id="ref-for-user-verification④④">user verification</a> is later enabled on an <a data-link-type="dfn" href="#authenticator" id="ref-for-authenticator②②⑦">authenticator</a>.</p>
    <p>As a motivating example, PRF outputs could be used as symmetric keys to encrypt user data. Such encrypted data would be inaccessible without the ability to get assertions from the associated <a data-link-type="dfn" href="https://w3c.github.io/webappsec-credential-management/#concept-credential" id="ref-for-concept-credential②⓪">credential</a>. By using the provision below to evaluate the PRF at two inputs in a single <a data-link-type="dfn" href="#assertion" id="ref-for-assertion⑥">assertion</a> operation, the encryption key could be periodically rotated during <a data-link-type="dfn" href="#assertion" id="ref-for-assertion⑦">assertions</a> by choosing a fresh, random input and reencrypting under the new output. If the evaluation inputs are unpredictable then even an attacker who could satisfy <a data-link-type="dfn" href="#user-verification" id="ref-for-user-verification④⑤">user verification</a>, and who had time-limited access to the authenticator, could not learn the encryption key without also knowing the correct PRF input.</p>
    <p>This extension is implemented on top of the <a data-link-type="biblio" href="#biblio-fido-ctap">[FIDO-CTAP]</a> <code>hmac-secret</code> extension. It is a separate <a data-link-type="dfn" href="#client-extension" id="ref-for-client-extension①⓪">client extension</a> because <code>hmac-secret</code> requires that inputs and outputs be encrypted in a manner that only the user agent can perform, and to provide separation between uses by WebAuthn and any uses by the underlying platform. This separation is achieved by hashing the provided PRF inputs with a context string to prevent evaluation of the PRFs for arbitrary inputs.</p>
-   <p class="note" role="note"><span>Note:</span> this extension may be implemented for <a data-link-type="dfn" href="#authenticator" id="ref-for-authenticator②②⑨">authenticators</a> that do not use <a data-link-type="biblio" href="#biblio-fido-ctap">[FIDO-CTAP]</a> so long as the behavior observed by a <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party②⑦⑥">Relying Party</a> is identical.</p>
+   <p class="note" role="note"><span>Note:</span> this extension may be implemented for <a data-link-type="dfn" href="#authenticator" id="ref-for-authenticator②②⑧">authenticators</a> that do not use <a data-link-type="biblio" href="#biblio-fido-ctap">[FIDO-CTAP]</a> so long as the behavior observed by a <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party②⑧③">Relying Party</a> is identical.</p>
    <dl>
     <dt data-md>Extension identifier
     <dd data-md>
@@ -6305,10 +6383,10 @@ <h4 class="heading settled" data-level="10.1.4" id="prf-extension"><span class="
       <dl>
        <dt data-md><dfn class="dfn-paneled idl-code" data-dfn-for="AuthenticationExtensionsPRFInputs" data-dfn-type="dict-member" data-export id="dom-authenticationextensionsprfinputs-eval"><code>eval</code></dfn>, <span> of type <a data-link-type="idl-name" href="#dictdef-authenticationextensionsprfvalues" id="ref-for-dictdef-authenticationextensionsprfvalues②">AuthenticationExtensionsPRFValues</a></span>
        <dd data-md>
-        <p>One or two inputs on which to evaluate PRF. Not all <a data-link-type="dfn" href="#authenticator" id="ref-for-authenticator②③⓪">authenticators</a> support evaluating the PRFs during credential creation so outputs may, or may not, be provided. If not, then an <a data-link-type="dfn" href="#assertion" id="ref-for-assertion⑧">assertion</a> is needed in order to obtain the outputs.</p>
+        <p>One or two inputs on which to evaluate PRF. Not all <a data-link-type="dfn" href="#authenticator" id="ref-for-authenticator②②⑨">authenticators</a> support evaluating the PRFs during credential creation so outputs may, or may not, be provided. If not, then an <a data-link-type="dfn" href="#assertion" id="ref-for-assertion⑧">assertion</a> is needed in order to obtain the outputs.</p>
        <dt data-md><dfn class="dfn-paneled idl-code" data-dfn-for="AuthenticationExtensionsPRFInputs" data-dfn-type="dict-member" data-export id="dom-authenticationextensionsprfinputs-evalbycredential"><code>evalByCredential</code></dfn>, <span> of type record&lt;<a data-link-type="idl-name" href="https://webidl.spec.whatwg.org/#idl-USVString" id="ref-for-idl-USVString⑥">USVString</a>, <a data-link-type="idl-name" href="#dictdef-authenticationextensionsprfvalues" id="ref-for-dictdef-authenticationextensionsprfvalues③">AuthenticationExtensionsPRFValues</a>></span>
        <dd data-md>
-        <p>A record mapping <a data-link-type="dfn" href="#base64url-encoding" id="ref-for-base64url-encoding①⑥">base64url encoded</a> <a data-link-type="dfn" href="#credential-id" id="ref-for-credential-id③⑧">credential IDs</a> to PRF inputs to evaluate for that credential. Only applicable during <a data-link-type="dfn" href="#assertion" id="ref-for-assertion⑨">assertions</a> when <code class="idl"><a data-link-type="idl" href="#dom-publickeycredentialrequestoptions-allowcredentials" id="ref-for-dom-publickeycredentialrequestoptions-allowcredentials②①">allowCredentials</a></code> is not empty.</p>
+        <p>A record mapping <a data-link-type="dfn" href="#base64url-encoding" id="ref-for-base64url-encoding①⑤">base64url encoded</a> <a data-link-type="dfn" href="#credential-id" id="ref-for-credential-id③⑨">credential IDs</a> to PRF inputs to evaluate for that credential. Only applicable during <a data-link-type="dfn" href="#assertion" id="ref-for-assertion⑨">assertions</a> when <code class="idl"><a data-link-type="idl" href="#dom-publickeycredentialrequestoptions-allowcredentials" id="ref-for-dom-publickeycredentialrequestoptions-allowcredentials①⑨">allowCredentials</a></code> is not empty.</p>
       </dl>
      </div>
     <dt data-md>Client extension processing (<a data-link-type="dfn" href="#registration-extension" id="ref-for-registration-extension①③">registration</a>)
@@ -6332,7 +6410,7 @@ <h4 class="heading settled" data-level="10.1.4" id="prf-extension"><span class="
        <p>Set <code class="idl"><a data-link-type="idl" href="#dom-authenticationextensionsprfoutputs-results" id="ref-for-dom-authenticationextensionsprfoutputs-results">results</a></code> to the decrypted PRF result(s), if any.</p>
      </ol>
    </dl>
-   <p class="note" role="note"><span>Note:</span> If PRF results are obtained during <a data-link-type="dfn" href="#registration" id="ref-for-registration①⑧">registration</a> then the <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party②⑦⑦">Relying Party</a> MUST inspect the <a data-link-type="dfn" href="#authdata-flags-uv" id="ref-for-authdata-flags-uv⑨">UV</a> bit in the <a data-link-type="dfn" href="#authdata-flags" id="ref-for-authdata-flags③⑤">flags</a> of the response in order to determine the correct value of <code class="idl"><a data-link-type="idl" href="#dom-publickeycredentialrequestoptions-userverification" id="ref-for-dom-publickeycredentialrequestoptions-userverification⑥">userVerification</a></code> for future <a data-link-type="dfn" href="#assertion" id="ref-for-assertion①⓪">assertions</a>. Otherwise results from <a data-link-type="dfn" href="#assertion" id="ref-for-assertion①①">assertions</a> may be inconsistent with those from the <a data-link-type="dfn" href="#registration" id="ref-for-registration①⑨">registration</a>.</p>
+   <p class="note" role="note"><span>Note:</span> If PRF results are obtained during <a data-link-type="dfn" href="#registration" id="ref-for-registration②①">registration</a> then the <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party②⑧④">Relying Party</a> MUST inspect the <a data-link-type="dfn" href="#authdata-flags-uv" id="ref-for-authdata-flags-uv⑨">UV</a> bit in the <a data-link-type="dfn" href="#authdata-flags" id="ref-for-authdata-flags④⓪">flags</a> of the response in order to determine the correct value of <code class="idl"><a data-link-type="idl" href="#dom-publickeycredentialrequestoptions-userverification" id="ref-for-dom-publickeycredentialrequestoptions-userverification⑥">userVerification</a></code> for future <a data-link-type="dfn" href="#assertion" id="ref-for-assertion①⓪">assertions</a>. Otherwise results from <a data-link-type="dfn" href="#assertion" id="ref-for-assertion①①">assertions</a> may be inconsistent with those from the <a data-link-type="dfn" href="#registration" id="ref-for-registration②②">registration</a>.</p>
    <dl>
     <dt data-md>Client extension processing (<a data-link-type="dfn" href="#authentication-extension" id="ref-for-authentication-extension①①">authentication</a>)
     <dd data-md>
@@ -6340,14 +6418,14 @@ <h4 class="heading settled" data-level="10.1.4" id="prf-extension"><span class="
       <li data-md>
        <p>If <code class="idl"><a data-link-type="idl" href="#dom-publickeycredentialrequestoptions-userverification" id="ref-for-dom-publickeycredentialrequestoptions-userverification⑦">userVerification</a></code> has the value <code class="idl"><a data-link-type="idl" href="#dom-userverificationrequirement-preferred" id="ref-for-dom-userverificationrequirement-preferred⑥">preferred</a></code>, return a <code class="idl"><a data-link-type="idl" href="https://webidl.spec.whatwg.org/#idl-DOMException" id="ref-for-idl-DOMException②③">DOMException</a></code> whose name is “<code class="idl"><a data-link-type="idl" href="https://webidl.spec.whatwg.org/#notsupportederror" id="ref-for-notsupportederror⑤">NotSupportedError</a></code>”.</p>
       <li data-md>
-       <p>If <code class="idl"><a data-link-type="idl" href="#dom-authenticationextensionsprfinputs-evalbycredential" id="ref-for-dom-authenticationextensionsprfinputs-evalbycredential②">evalByCredential</a></code> is not empty but <code class="idl"><a data-link-type="idl" href="#dom-publickeycredentialrequestoptions-allowcredentials" id="ref-for-dom-publickeycredentialrequestoptions-allowcredentials②②">allowCredentials</a></code> is empty, return a <code class="idl"><a data-link-type="idl" href="https://webidl.spec.whatwg.org/#idl-DOMException" id="ref-for-idl-DOMException②④">DOMException</a></code> whose name is “<code class="idl"><a data-link-type="idl" href="https://webidl.spec.whatwg.org/#notsupportederror" id="ref-for-notsupportederror⑥">NotSupportedError</a></code>”.</p>
+       <p>If <code class="idl"><a data-link-type="idl" href="#dom-authenticationextensionsprfinputs-evalbycredential" id="ref-for-dom-authenticationextensionsprfinputs-evalbycredential②">evalByCredential</a></code> is not empty but <code class="idl"><a data-link-type="idl" href="#dom-publickeycredentialrequestoptions-allowcredentials" id="ref-for-dom-publickeycredentialrequestoptions-allowcredentials②⓪">allowCredentials</a></code> is empty, return a <code class="idl"><a data-link-type="idl" href="https://webidl.spec.whatwg.org/#idl-DOMException" id="ref-for-idl-DOMException②④">DOMException</a></code> whose name is “<code class="idl"><a data-link-type="idl" href="https://webidl.spec.whatwg.org/#notsupportederror" id="ref-for-notsupportederror⑥">NotSupportedError</a></code>”.</p>
       <li data-md>
        <p>Initialize the <code class="idl"><a data-link-type="idl" href="#dom-authenticationextensionsclientoutputs-prf" id="ref-for-dom-authenticationextensionsclientoutputs-prf">prf</a></code> extension output to an empty dictionary.</p>
       <li data-md>
        <p>Let <var>ev</var> be null, and try to find any applicable PRF input(s):</p>
        <ol>
         <li data-md>
-         <p>If <code class="idl"><a data-link-type="idl" href="#dom-authenticationextensionsprfinputs-evalbycredential" id="ref-for-dom-authenticationextensionsprfinputs-evalbycredential③">evalByCredential</a></code> is present and <a data-link-type="dfn" href="https://infra.spec.whatwg.org/#map-exists" id="ref-for-map-exists⑥">contains</a> an <a data-link-type="dfn" href="https://infra.spec.whatwg.org/#map-entry" id="ref-for-map-entry①">entry</a> whose <a data-link-type="dfn" href="https://infra.spec.whatwg.org/#map-key" id="ref-for-map-key">key</a> is the <a data-link-type="dfn" href="#base64url-encoding" id="ref-for-base64url-encoding①⑦">base64url encoding</a> of the <a data-link-type="dfn" href="#credential-id" id="ref-for-credential-id③⑨">credential ID</a> that will be returned, let <var>ev</var> be the <a data-link-type="dfn" href="https://infra.spec.whatwg.org/#map-value" id="ref-for-map-value">value</a> of that entry.</p>
+         <p>If <code class="idl"><a data-link-type="idl" href="#dom-authenticationextensionsprfinputs-evalbycredential" id="ref-for-dom-authenticationextensionsprfinputs-evalbycredential③">evalByCredential</a></code> is present and <a data-link-type="dfn" href="https://infra.spec.whatwg.org/#map-exists" id="ref-for-map-exists⑥">contains</a> an <a data-link-type="dfn" href="https://infra.spec.whatwg.org/#map-entry" id="ref-for-map-entry①">entry</a> whose <a data-link-type="dfn" href="https://infra.spec.whatwg.org/#map-key" id="ref-for-map-key">key</a> is the <a data-link-type="dfn" href="#base64url-encoding" id="ref-for-base64url-encoding①⑥">base64url encoding</a> of the <a data-link-type="dfn" href="#credential-id" id="ref-for-credential-id④⓪">credential ID</a> that will be returned, let <var>ev</var> be the <a data-link-type="dfn" href="https://infra.spec.whatwg.org/#map-value" id="ref-for-map-value">value</a> of that entry.</p>
         <li data-md>
          <p>If <var>ev</var> is null and <code class="idl"><a data-link-type="idl" href="#dom-authenticationextensionsprfinputs-eval" id="ref-for-dom-authenticationextensionsprfinputs-eval⑤">eval</a></code> is present, then let <var>ev</var> be the value of <code class="idl"><a data-link-type="idl" href="#dom-authenticationextensionsprfinputs-eval" id="ref-for-dom-authenticationextensionsprfinputs-eval⑥">eval</a></code>.</p>
        </ol>
@@ -6359,14 +6437,14 @@ <h4 class="heading settled" data-level="10.1.4" id="prf-extension"><span class="
         <li data-md>
          <p>If <code><var>ev</var>.<code class="idl"><a data-link-type="idl" href="#dom-authenticationextensionsprfvalues-second" id="ref-for-dom-authenticationextensionsprfvalues-second②">second</a></code></code> is present, let <code>salt2</code> be the value of <code>SHA-256(UTF8Encode("WebAuthn PRF") || 0x00 || <var>ev</var>.<code class="idl"><a data-link-type="idl" href="#dom-authenticationextensionsprfvalues-second" id="ref-for-dom-authenticationextensionsprfvalues-second③">second</a></code>)</code>.</p>
         <li data-md>
-         <p>Send an <code>hmac-secret</code> extension to the <a data-link-type="dfn" href="#authenticator" id="ref-for-authenticator②③①">authenticator</a> using the values of <code>salt1</code> and, if set, <code>salt2</code> as the parameters of the same name in that process.</p>
+         <p>Send an <code>hmac-secret</code> extension to the <a data-link-type="dfn" href="#authenticator" id="ref-for-authenticator②③⓪">authenticator</a> using the values of <code>salt1</code> and, if set, <code>salt2</code> as the parameters of the same name in that process.</p>
         <li data-md>
          <p>Decrypt the extension result and set <code class="idl"><a data-link-type="idl" href="#dom-authenticationextensionsprfoutputs-results" id="ref-for-dom-authenticationextensionsprfoutputs-results①">results</a></code> to the PRF result(s), if any.</p>
        </ol>
      </ol>
     <dt data-md>Authenticator extension input / processing / output
     <dd data-md>
-     <p><a data-link-type="dfn" href="#prf" id="ref-for-prf">This extension</a> uses the <a data-link-type="biblio" href="#biblio-fido-ctap">[FIDO-CTAP]</a> <code>hmac-secret</code> extension when communicating with the authenticator. It thus does not specify any direct authenticator interaction for <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party②⑦⑧">Relying Parties</a>.</p>
+     <p><a data-link-type="dfn" href="#prf" id="ref-for-prf">This extension</a> uses the <a data-link-type="biblio" href="#biblio-fido-ctap">[FIDO-CTAP]</a> <code>hmac-secret</code> extension when communicating with the authenticator. It thus does not specify any direct authenticator interaction for <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party②⑧⑤">Relying Parties</a>.</p>
     <dt data-md>Client extension output
     <dd data-md>
 <pre class="idl highlight def"><c- b>dictionary</c-> <dfn class="dfn-paneled idl-code" data-dfn-type="dictionary" data-export id="dictdef-authenticationextensionsprfoutputs"><code><c- g>AuthenticationExtensionsPRFOutputs</c-></code></dfn> {
@@ -6382,22 +6460,22 @@ <h4 class="heading settled" data-level="10.1.4" id="prf-extension"><span class="
       <dl>
        <dt data-md><dfn class="dfn-paneled idl-code" data-dfn-for="AuthenticationExtensionsPRFOutputs" data-dfn-type="dict-member" data-export id="dom-authenticationextensionsprfoutputs-enabled"><code>enabled</code></dfn>, <span> of type <a data-link-type="idl-name" href="https://webidl.spec.whatwg.org/#idl-boolean" id="ref-for-idl-boolean①②">boolean</a></span>
        <dd data-md>
-        <p><code>true</code> if, and only if, the one or two PRFs are available for use with the created credential. This is only reported during <a data-link-type="dfn" href="#registration" id="ref-for-registration②⓪">registration</a> and is not present in the case of <a data-link-type="dfn" href="#authentication" id="ref-for-authentication①④">authentication</a>.</p>
+        <p><code>true</code> if, and only if, the one or two PRFs are available for use with the created credential. This is only reported during <a data-link-type="dfn" href="#registration" id="ref-for-registration②③">registration</a> and is not present in the case of <a data-link-type="dfn" href="#authentication" id="ref-for-authentication①④">authentication</a>.</p>
        <dt data-md><dfn class="dfn-paneled idl-code" data-dfn-for="AuthenticationExtensionsPRFOutputs" data-dfn-type="dict-member" data-export id="dom-authenticationextensionsprfoutputs-results"><code>results</code></dfn>, <span> of type <a data-link-type="idl-name" href="#dictdef-authenticationextensionsprfvalues" id="ref-for-dictdef-authenticationextensionsprfvalues⑤">AuthenticationExtensionsPRFValues</a></span>
        <dd data-md>
-        <p>The results of evaluating the PRF for the inputs given in <code class="idl"><a data-link-type="idl" href="#dom-authenticationextensionsprfinputs-eval" id="ref-for-dom-authenticationextensionsprfinputs-eval⑦">eval</a></code> or <code class="idl"><a data-link-type="idl" href="#dom-authenticationextensionsprfinputs-evalbycredential" id="ref-for-dom-authenticationextensionsprfinputs-evalbycredential④">evalByCredential</a></code>. Outputs may not be available during <a data-link-type="dfn" href="#registration" id="ref-for-registration②①">registration</a>; see comments in <code class="idl"><a data-link-type="idl" href="#dom-authenticationextensionsprfinputs-eval" id="ref-for-dom-authenticationextensionsprfinputs-eval⑧">eval</a></code>.</p>
+        <p>The results of evaluating the PRF for the inputs given in <code class="idl"><a data-link-type="idl" href="#dom-authenticationextensionsprfinputs-eval" id="ref-for-dom-authenticationextensionsprfinputs-eval⑦">eval</a></code> or <code class="idl"><a data-link-type="idl" href="#dom-authenticationextensionsprfinputs-evalbycredential" id="ref-for-dom-authenticationextensionsprfinputs-evalbycredential④">evalByCredential</a></code>. Outputs may not be available during <a data-link-type="dfn" href="#registration" id="ref-for-registration②④">registration</a>; see comments in <code class="idl"><a data-link-type="idl" href="#dom-authenticationextensionsprfinputs-eval" id="ref-for-dom-authenticationextensionsprfinputs-eval⑧">eval</a></code>.</p>
       </dl>
      </div>
    </dl>
    <h4 class="heading settled" data-level="10.1.5" id="sctn-large-blob-extension"><span class="secno">10.1.5. </span><span class="content">Large blob storage extension (<dfn class="dfn-paneled" data-dfn-type="dfn" data-noexport id="largeblob">largeBlob</dfn>)</span><a class="self-link" href="#sctn-large-blob-extension"></a></h4>
-   <p>This <a data-link-type="dfn" href="#client-extension" id="ref-for-client-extension①①">client</a> <a data-link-type="dfn" href="#registration-extension" id="ref-for-registration-extension①④">registration extension</a> and <a data-link-type="dfn" href="#authentication-extension" id="ref-for-authentication-extension①②">authentication extension</a> allows a <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party②⑦⑨">Relying Party</a> to store opaque data associated with a credential. Since <a data-link-type="dfn" href="#authenticator" id="ref-for-authenticator②③②">authenticators</a> can only store small amounts of data, and most <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party②⑧⓪">Relying Parties</a> are online services that can store arbitrary amounts of state for a user, this is only useful in specific cases. For example, the <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party②⑧①">Relying Party</a> might wish to issue certificates rather than run a centralised authentication service.</p>
-   <p class="note" role="note"><span>Note:</span> <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party②⑧②">Relying Parties</a> can assume that the opaque data will be compressed when being written to a space-limited device and so need not compress it themselves.</p>
-   <p>Since a certificate system needs to sign over the public key of the credential, and that public key is only available after creation, this extension does not add an ability to write blobs in the <a data-link-type="dfn" href="#registration-extension" id="ref-for-registration-extension①⑤">registration</a> context. However, <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party②⑧③">Relying Parties</a> SHOULD use the <a data-link-type="dfn" href="#registration-extension" id="ref-for-registration-extension①⑥">registration extension</a> when creating the credential if they wish to later use the <a data-link-type="dfn" href="#authentication-extension" id="ref-for-authentication-extension①③">authentication extension</a>.</p>
+   <p>This <a data-link-type="dfn" href="#client-extension" id="ref-for-client-extension①①">client</a> <a data-link-type="dfn" href="#registration-extension" id="ref-for-registration-extension①④">registration extension</a> and <a data-link-type="dfn" href="#authentication-extension" id="ref-for-authentication-extension①②">authentication extension</a> allows a <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party②⑧⑥">Relying Party</a> to store opaque data associated with a credential. Since <a data-link-type="dfn" href="#authenticator" id="ref-for-authenticator②③①">authenticators</a> can only store small amounts of data, and most <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party②⑧⑦">Relying Parties</a> are online services that can store arbitrary amounts of state for a user, this is only useful in specific cases. For example, the <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party②⑧⑧">Relying Party</a> might wish to issue certificates rather than run a centralised authentication service.</p>
+   <p class="note" role="note"><span>Note:</span> <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party②⑧⑨">Relying Parties</a> can assume that the opaque data will be compressed when being written to a space-limited device and so need not compress it themselves.</p>
+   <p>Since a certificate system needs to sign over the public key of the credential, and that public key is only available after creation, this extension does not add an ability to write blobs in the <a data-link-type="dfn" href="#registration-extension" id="ref-for-registration-extension①⑤">registration</a> context. However, <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party②⑨⓪">Relying Parties</a> SHOULD use the <a data-link-type="dfn" href="#registration-extension" id="ref-for-registration-extension①⑥">registration extension</a> when creating the credential if they wish to later use the <a data-link-type="dfn" href="#authentication-extension" id="ref-for-authentication-extension①③">authentication extension</a>.</p>
    <p>Since certificates are sizable relative to the storage capabilities of typical authenticators, user agents SHOULD consider what indications and confirmations are suitable to best guide the user in allocating this limited resource and prevent abuse.</p>
    <p class="note" role="note"><span>Note:</span> In order to interoperate, user agents storing large blobs on authenticators using <a data-link-type="biblio" href="#biblio-fido-ctap">[FIDO-CTAP]</a> are expected to use the provisions detailed in that specification for storing <a data-link-type="dfn" href="https://fidoalliance.org/specs/fido-v2.0-ps-20190130/fido-client-to-authenticator-protocol-v2.0-ps-20190130.html#large-blob" id="ref-for-large-blob">large, per-credential blobs</a>.</p>
    <p class="note" role="note"><span>Note:</span> <a data-link-type="dfn" href="#roaming-authenticators" id="ref-for-roaming-authenticators②④">Roaming authenticators</a> that use <a data-link-type="biblio" href="#biblio-fido-ctap">[FIDO-CTAP]</a> as their cross-platform transport protocol only support this <a data-link-type="dfn" href="#largeblob" id="ref-for-largeblob">Large Blob</a> extension for <a data-link-type="dfn" href="#discoverable-credential" id="ref-for-discoverable-credential①⑤">discoverable credentials</a>,
 and might return an error unless <code><code class="idl"><a data-link-type="idl" href="#dom-publickeycredentialcreationoptions-authenticatorselection" id="ref-for-dom-publickeycredentialcreationoptions-authenticatorselection①①">authenticatorSelection</a></code>.<code class="idl"><a data-link-type="idl" href="#dom-authenticatorselectioncriteria-residentkey" id="ref-for-dom-authenticatorselectioncriteria-residentkey⑦">residentKey</a></code></code> is set to <code class="idl"><a data-link-type="idl" href="#dom-residentkeyrequirement-preferred" id="ref-for-dom-residentkeyrequirement-preferred④">preferred</a></code> or <code class="idl"><a data-link-type="idl" href="#dom-residentkeyrequirement-required" id="ref-for-dom-residentkeyrequirement-required⑤">required</a></code>.
-However, <a data-link-type="dfn" href="#authenticator" id="ref-for-authenticator②③③">authenticators</a> that do not utilize <a data-link-type="biblio" href="#biblio-fido-ctap">[FIDO-CTAP]</a> do not necessarily restrict this extension to <a data-link-type="dfn" href="#discoverable-credential" id="ref-for-discoverable-credential①⑥">discoverable credentials</a>.</p>
+However, <a data-link-type="dfn" href="#authenticator" id="ref-for-authenticator②③②">authenticators</a> that do not utilize <a data-link-type="biblio" href="#biblio-fido-ctap">[FIDO-CTAP]</a> do not necessarily restrict this extension to <a data-link-type="dfn" href="#discoverable-credential" id="ref-for-discoverable-credential①⑥">discoverable credentials</a>.</p>
    <dl>
     <dt data-md>Extension identifier
     <dd data-md>
@@ -6429,10 +6507,10 @@ <h4 class="heading settled" data-level="10.1.5" id="sctn-large-blob-extension"><
         <p>A DOMString that takes one of the values of <code class="idl"><a data-link-type="idl" href="#enumdef-largeblobsupport" id="ref-for-enumdef-largeblobsupport">LargeBlobSupport</a></code>. (See <a href="#sct-domstring-backwards-compatibility">§ 2.1.1 Enumerations as DOMString types</a>.) Only valid during <a data-link-type="dfn" href="#registration-extension" id="ref-for-registration-extension①⑧">registration</a>.</p>
        <dt data-md><dfn class="dfn-paneled idl-code" data-dfn-for="AuthenticationExtensionsLargeBlobInputs" data-dfn-type="dict-member" data-export id="dom-authenticationextensionslargeblobinputs-read"><code>read</code></dfn>, <span> of type <a data-link-type="idl-name" href="https://webidl.spec.whatwg.org/#idl-boolean" id="ref-for-idl-boolean①④">boolean</a></span>
        <dd data-md>
-        <p>A boolean that indicates that the <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party②⑧④">Relying Party</a> would like to fetch the previously-written blob associated with the asserted credential. Only valid during <a data-link-type="dfn" href="#authentication-extension" id="ref-for-authentication-extension①⑤">authentication</a>.</p>
+        <p>A boolean that indicates that the <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party②⑨①">Relying Party</a> would like to fetch the previously-written blob associated with the asserted credential. Only valid during <a data-link-type="dfn" href="#authentication-extension" id="ref-for-authentication-extension①⑤">authentication</a>.</p>
        <dt data-md><dfn class="dfn-paneled idl-code" data-dfn-for="AuthenticationExtensionsLargeBlobInputs" data-dfn-type="dict-member" data-export id="dom-authenticationextensionslargeblobinputs-write"><code>write</code></dfn>, <span> of type <a data-link-type="idl-name" href="https://webidl.spec.whatwg.org/#BufferSource" id="ref-for-BufferSource①①">BufferSource</a></span>
        <dd data-md>
-        <p>An opaque byte string that the <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party②⑧⑤">Relying Party</a> wishes to store with the existing credential. Only valid during <a data-link-type="dfn" href="#authentication-extension" id="ref-for-authentication-extension①⑥">authentication</a>.</p>
+        <p>An opaque byte string that the <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party②⑨②">Relying Party</a> wishes to store with the existing credential. Only valid during <a data-link-type="dfn" href="#authentication-extension" id="ref-for-authentication-extension①⑥">authentication</a>.</p>
       </dl>
      </div>
     <dt data-md>Client extension processing (<a data-link-type="dfn" href="#registration-extension" id="ref-for-registration-extension①⑨">registration</a>)
@@ -6490,13 +6568,13 @@ <h4 class="heading settled" data-level="10.1.5" id="sctn-large-blob-extension"><
        <p>If <code class="idl"><a data-link-type="idl" href="#dom-authenticationextensionslargeblobinputs-write" id="ref-for-dom-authenticationextensionslargeblobinputs-write③">write</a></code> is present:</p>
        <ol>
         <li data-md>
-         <p>If <code class="idl"><a data-link-type="idl" href="#dom-publickeycredentialrequestoptions-allowcredentials" id="ref-for-dom-publickeycredentialrequestoptions-allowcredentials②③">allowCredentials</a></code> does not contain exactly one element:</p>
+         <p>If <code class="idl"><a data-link-type="idl" href="#dom-publickeycredentialrequestoptions-allowcredentials" id="ref-for-dom-publickeycredentialrequestoptions-allowcredentials②①">allowCredentials</a></code> does not contain exactly one element:</p>
          <ol>
           <li data-md>
            <p>Return a <code class="idl"><a data-link-type="idl" href="https://webidl.spec.whatwg.org/#idl-DOMException" id="ref-for-idl-DOMException②⑧">DOMException</a></code> whose name is “<code class="idl"><a data-link-type="idl" href="https://webidl.spec.whatwg.org/#notsupportederror" id="ref-for-notsupportederror①⓪">NotSupportedError</a></code>”.</p>
          </ol>
         <li data-md>
-         <p>If the <a href="#sctn-getAssertion">assertion</a> operation is successful, attempt to store the contents of <code class="idl"><a data-link-type="idl" href="#dom-authenticationextensionslargeblobinputs-write" id="ref-for-dom-authenticationextensionslargeblobinputs-write④">write</a></code> on the <a data-link-type="dfn" href="#authenticator" id="ref-for-authenticator②③④">authenticator</a>, associated with the indicated credential.</p>
+         <p>If the <a href="#sctn-getAssertion">assertion</a> operation is successful, attempt to store the contents of <code class="idl"><a data-link-type="idl" href="#dom-authenticationextensionslargeblobinputs-write" id="ref-for-dom-authenticationextensionslargeblobinputs-write④">write</a></code> on the <a data-link-type="dfn" href="#authenticator" id="ref-for-authenticator②③③">authenticator</a>, associated with the indicated credential.</p>
         <li data-md>
          <p>Set <code class="idl"><a data-link-type="idl" href="#dom-authenticationextensionslargebloboutputs-written" id="ref-for-dom-authenticationextensionslargebloboutputs-written">written</a></code> to <code>true</code> if successful and <code>false</code> otherwise.</p>
        </ol>
@@ -6520,15 +6598,15 @@ <h4 class="heading settled" data-level="10.1.5" id="sctn-large-blob-extension"><
         <p><code>true</code> if, and only if, the created credential supports storing large blobs. Only present in <a data-link-type="dfn" href="#registration-extension" id="ref-for-registration-extension②⓪">registration</a> outputs.</p>
        <dt data-md><dfn class="dfn-paneled idl-code" data-dfn-for="AuthenticationExtensionsLargeBlobOutputs" data-dfn-type="dict-member" data-export id="dom-authenticationextensionslargebloboutputs-blob"><code>blob</code></dfn>, <span> of type <a data-link-type="idl-name" href="https://webidl.spec.whatwg.org/#idl-ArrayBuffer" id="ref-for-idl-ArrayBuffer③①">ArrayBuffer</a></span>
        <dd data-md>
-        <p>The opaque byte string that was associated with the credential identified by <code class="idl"><a data-link-type="idl" href="#dom-publickeycredential-rawid" id="ref-for-dom-publickeycredential-rawid③">rawId</a></code>. Only valid if <code class="idl"><a data-link-type="idl" href="#dom-authenticationextensionslargeblobinputs-read" id="ref-for-dom-authenticationextensionslargeblobinputs-read④">read</a></code> was <code>true</code>.</p>
+        <p>The opaque byte string that was associated with the credential identified by <code class="idl"><a data-link-type="idl" href="#dom-publickeycredential-rawid" id="ref-for-dom-publickeycredential-rawid⑤">rawId</a></code>. Only valid if <code class="idl"><a data-link-type="idl" href="#dom-authenticationextensionslargeblobinputs-read" id="ref-for-dom-authenticationextensionslargeblobinputs-read④">read</a></code> was <code>true</code>.</p>
        <dt data-md><dfn class="dfn-paneled idl-code" data-dfn-for="AuthenticationExtensionsLargeBlobOutputs" data-dfn-type="dict-member" data-export id="dom-authenticationextensionslargebloboutputs-written"><code>written</code></dfn>, <span> of type <a data-link-type="idl-name" href="https://webidl.spec.whatwg.org/#idl-boolean" id="ref-for-idl-boolean①⑧">boolean</a></span>
        <dd data-md>
-        <p>A boolean that indicates that the contents of <code class="idl"><a data-link-type="idl" href="#dom-authenticationextensionslargeblobinputs-write" id="ref-for-dom-authenticationextensionslargeblobinputs-write⑤">write</a></code> were successfully stored on the <a data-link-type="dfn" href="#authenticator" id="ref-for-authenticator②③⑤">authenticator</a>, associated with the specified credential.</p>
+        <p>A boolean that indicates that the contents of <code class="idl"><a data-link-type="idl" href="#dom-authenticationextensionslargeblobinputs-write" id="ref-for-dom-authenticationextensionslargeblobinputs-write⑤">write</a></code> were successfully stored on the <a data-link-type="dfn" href="#authenticator" id="ref-for-authenticator②③④">authenticator</a>, associated with the specified credential.</p>
       </dl>
      </div>
     <dt data-md>Authenticator extension processing
     <dd data-md>
-     <p><a data-link-type="dfn" href="#largeblob" id="ref-for-largeblob①">This extension</a> directs the user-agent to cause the large blob to be stored on, or retrieved from, the authenticator. It thus does not specify any direct authenticator interaction for <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party②⑧⑥">Relying Parties</a>.</p>
+     <p><a data-link-type="dfn" href="#largeblob" id="ref-for-largeblob①">This extension</a> directs the user-agent to cause the large blob to be stored on, or retrieved from, the authenticator. It thus does not specify any direct authenticator interaction for <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party②⑨③">Relying Parties</a>.</p>
    </dl>
    <h3 class="heading settled" data-level="10.2" id="sctn-defined-authenticator-extensions"><span class="secno">10.2. </span><span class="content">Authenticator Extensions</span><a class="self-link" href="#sctn-defined-authenticator-extensions"></a></h3>
    <p>This section defines extensions that are both <a data-link-type="dfn" href="#client-extension" id="ref-for-client-extension①②">client extensions</a> and <a data-link-type="dfn" href="#authenticator-extension" id="ref-for-authenticator-extension①②">authenticator extensions</a>.</p>
@@ -6543,7 +6621,7 @@ <h4 class="heading settled" data-level="10.2.1" id="sctn-uvm-extension"><span cl
      <p><a data-link-type="dfn" href="#registration-extension" id="ref-for-registration-extension②①">Registration</a> and <a data-link-type="dfn" href="#authentication-extension" id="ref-for-authentication-extension①⑧">Authentication</a></p>
     <dt data-md>Client extension input
     <dd data-md>
-     <p>The Boolean value <code>true</code> to indicate that this extension is requested by the <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party②⑧⑦">Relying Party</a>.</p>
+     <p>The Boolean value <code>true</code> to indicate that this extension is requested by the <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party②⑨④">Relying Party</a>.</p>
 <pre class="idl highlight def"><c- b>partial</c-> <c- b>dictionary</c-> <a class="idl-code" data-link-type="dictionary" href="#dictdef-authenticationextensionsclientinputs" id="ref-for-dictdef-authenticationextensionsclientinputs①①"><c- g>AuthenticationExtensionsClientInputs</c-></a> {
   <a class="idl-code" data-link-type="interface" href="https://webidl.spec.whatwg.org/#idl-boolean" id="ref-for-idl-boolean①⑨"><c- b>boolean</c-></a> <dfn class="idl-code" data-dfn-for="AuthenticationExtensionsClientInputs" data-dfn-type="dict-member" data-export data-type="boolean " id="dom-authenticationextensionsclientinputs-uvm"><code><c- g>uvm</c-></code><a class="self-link" href="#dom-authenticationextensionsclientinputs-uvm"></a></dfn>;
 };
@@ -6570,7 +6648,7 @@ <h4 class="heading settled" data-level="10.2.1" id="sctn-uvm-extension"><span cl
 </pre>
     <dt data-md>Authenticator extension processing
     <dd data-md>
-     <p>The <a data-link-type="dfn" href="#authenticator" id="ref-for-authenticator②③⑥">authenticator</a> sets the <a data-link-type="dfn" href="#authenticator-extension-output" id="ref-for-authenticator-extension-output①⑤">authenticator extension output</a> to be one or more user verification methods indicating the method(s) used
+     <p>The <a data-link-type="dfn" href="#authenticator" id="ref-for-authenticator②③⑤">authenticator</a> sets the <a data-link-type="dfn" href="#authenticator-extension-output" id="ref-for-authenticator-extension-output①⑤">authenticator extension output</a> to be one or more user verification methods indicating the method(s) used
 by the user to authorize the operation, as defined below. This extension can be added to attestation objects and assertions.</p>
     <dt data-md>Authenticator extension output
     <dd data-md>
@@ -6602,7 +6680,7 @@ <h4 class="heading settled" data-level="10.2.1" id="sctn-uvm-extension"><span cl
      </dl>
      <p>If >3 factors can be used in an authentication instance the authenticator vendor MUST select the 3 factors it believes
 will be most relevant to the Server to include in the UVM.</p>
-     <p>Example for <a data-link-type="dfn" href="#authenticator-data" id="ref-for-authenticator-data④⑦">authenticator data</a> containing one UVM extension for a multi-factor authentication instance where 2 factors
+     <p>Example for <a data-link-type="dfn" href="#authenticator-data" id="ref-for-authenticator-data④⑨">authenticator data</a> containing one UVM extension for a multi-factor authentication instance where 2 factors
 were used:</p>
 <pre>...                    -- RP ID hash (32 bytes)
 81                     -- UP and ED set
@@ -6885,7 +6963,7 @@ <h3 class="heading settled" data-level="11.4" id="sctn-automation-remove-virtual
      <p>Return <a data-link-type="dfn" href="https://w3c.github.io/webdriver/#dfn-success" id="ref-for-dfn-success①">success</a>.</p>
    </ol>
    <h3 class="heading settled" data-level="11.5" id="sctn-automation-add-credential"><span class="secno">11.5. </span><span class="content"><dfn class="dfn-paneled" data-dfn-type="dfn" data-noexport id="add-credential">Add Credential</dfn></span><a class="self-link" href="#sctn-automation-add-credential"></a></h3>
-   <p>The <a data-link-type="dfn" href="#add-credential" id="ref-for-add-credential">Add Credential</a> WebDriver <a data-link-type="dfn" href="https://w3c.github.io/webdriver/#dfn-extension-command" id="ref-for-dfn-extension-command⑤">extension command</a> injects a <a data-link-type="dfn" href="#public-key-credential-source" id="ref-for-public-key-credential-source④⑨">Public Key Credential Source</a> into an existing <a data-link-type="dfn" href="#virtual-authenticators" id="ref-for-virtual-authenticators①⑦">Virtual Authenticator</a>. It is defined as follows:</p>
+   <p>The <a data-link-type="dfn" href="#add-credential" id="ref-for-add-credential">Add Credential</a> WebDriver <a data-link-type="dfn" href="https://w3c.github.io/webdriver/#dfn-extension-command" id="ref-for-dfn-extension-command⑤">extension command</a> injects a <a data-link-type="dfn" href="#public-key-credential-source" id="ref-for-public-key-credential-source⑤⑧">Public Key Credential Source</a> into an existing <a data-link-type="dfn" href="#virtual-authenticators" id="ref-for-virtual-authenticators①⑦">Virtual Authenticator</a>. It is defined as follows:</p>
    <figure class="table" id="table-addCredential">
     <table class="data">
      <thead>
@@ -6909,7 +6987,7 @@ <h3 class="heading settled" data-level="11.5" id="sctn-automation-add-credential
      <tbody>
       <tr>
        <td><var>credentialId</var>
-       <td>The <a data-link-type="dfn" href="#public-key-credential-source-id" id="ref-for-public-key-credential-source-id⑤">Credential ID</a> encoded using <a data-link-type="dfn" href="#base64url-encoding" id="ref-for-base64url-encoding①⑧">Base64url Encoding</a>.
+       <td>The <a data-link-type="dfn" href="#public-key-credential-source-id" id="ref-for-public-key-credential-source-id⑤">Credential ID</a> encoded using <a data-link-type="dfn" href="#base64url-encoding" id="ref-for-base64url-encoding①⑦">Base64url Encoding</a>.
        <td>string
       <tr>
        <td><var>isResidentCredential</var>
@@ -6921,19 +6999,19 @@ <h3 class="heading settled" data-level="11.5" id="sctn-automation-add-credential
        <td>string
       <tr>
        <td><var>privateKey</var>
-       <td> An asymmetric key package containing a single <a data-link-type="dfn" href="#public-key-credential-source-privatekey" id="ref-for-public-key-credential-source-privatekey②">private key</a> per <a data-link-type="biblio" href="#biblio-rfc5958">[RFC5958]</a>, encoded using <a data-link-type="dfn" href="#base64url-encoding" id="ref-for-base64url-encoding①⑨">Base64url Encoding</a>. 
+       <td> An asymmetric key package containing a single <a data-link-type="dfn" href="#public-key-credential-source-privatekey" id="ref-for-public-key-credential-source-privatekey②">private key</a> per <a data-link-type="biblio" href="#biblio-rfc5958">[RFC5958]</a>, encoded using <a data-link-type="dfn" href="#base64url-encoding" id="ref-for-base64url-encoding①⑧">Base64url Encoding</a>. 
        <td>string
       <tr>
        <td><var>userHandle</var>
-       <td> The <a data-link-type="dfn" href="#public-key-credential-source-userhandle" id="ref-for-public-key-credential-source-userhandle⑤">userHandle</a> associated to the credential encoded using <a data-link-type="dfn" href="#base64url-encoding" id="ref-for-base64url-encoding②⓪">Base64url Encoding</a>. This property may not be defined. 
+       <td> The <a data-link-type="dfn" href="#public-key-credential-source-userhandle" id="ref-for-public-key-credential-source-userhandle⑤">userHandle</a> associated to the credential encoded using <a data-link-type="dfn" href="#base64url-encoding" id="ref-for-base64url-encoding①⑨">Base64url Encoding</a>. This property may not be defined. 
        <td>string
       <tr>
        <td><var>signCount</var>
-       <td>The initial value for a <a data-link-type="dfn" href="#signature-counter" id="ref-for-signature-counter②⑥">signature counter</a> associated to the <a data-link-type="dfn" href="#public-key-credential-source" id="ref-for-public-key-credential-source⑤⓪">public key credential source</a>.
+       <td>The initial value for a <a data-link-type="dfn" href="#signature-counter" id="ref-for-signature-counter②④">signature counter</a> associated to the <a data-link-type="dfn" href="#public-key-credential-source" id="ref-for-public-key-credential-source⑤⑨">public key credential source</a>.
        <td>number
       <tr>
        <td><var>largeBlob</var>
-       <td> The <a data-link-type="dfn" href="https://fidoalliance.org/specs/fido-v2.0-ps-20190130/fido-client-to-authenticator-protocol-v2.0-ps-20190130.html#large-blob" id="ref-for-large-blob①">large, per-credential blob</a> associated to the <a data-link-type="dfn" href="#public-key-credential-source" id="ref-for-public-key-credential-source⑤①">public key credential source</a>, encoded using <a data-link-type="dfn" href="#base64url-encoding" id="ref-for-base64url-encoding②①">Base64url Encoding</a>.
+       <td> The <a data-link-type="dfn" href="https://fidoalliance.org/specs/fido-v2.0-ps-20190130/fido-client-to-authenticator-protocol-v2.0-ps-20190130.html#large-blob" id="ref-for-large-blob①">large, per-credential blob</a> associated to the <a data-link-type="dfn" href="#public-key-credential-source" id="ref-for-public-key-credential-source⑥⓪">public key credential source</a>, encoded using <a data-link-type="dfn" href="#base64url-encoding" id="ref-for-base64url-encoding②⓪">Base64url Encoding</a>.
                     This property may not be defined. 
        <td>string
     </table>
@@ -6944,7 +7022,7 @@ <h3 class="heading settled" data-level="11.5" id="sctn-automation-add-credential
      <p>If <var>parameters</var> is not a JSON <a data-link-type="dfn" href="https://w3c.github.io/FileAPI/#blob-url-entry-object" id="ref-for-blob-url-entry-object③">Object</a>, return a <a data-link-type="dfn" href="https://w3c.github.io/webdriver/#dfn-error" id="ref-for-dfn-error⑧">WebDriver error</a> with <a data-link-type="dfn" href="https://w3c.github.io/webdriver/#dfn-error-code" id="ref-for-dfn-error-code⑧">WebDriver error code</a> <a data-link-type="dfn" href="https://w3c.github.io/webdriver/#dfn-invalid-argument" id="ref-for-dfn-invalid-argument⑦">invalid argument</a>.</p>
      <p class="note" role="note"><span>Note:</span> <var>parameters</var> is a <a data-link-type="dfn" href="#credential-parameters" id="ref-for-credential-parameters">Credential Parameters</a> object.</p>
     <li data-md>
-     <p>Let <var>credentialId</var> be the result of decoding <a data-link-type="dfn" href="#base64url-encoding" id="ref-for-base64url-encoding②②">Base64url Encoding</a> on the <var>parameters</var>’ <var>credentialId</var> property.</p>
+     <p>Let <var>credentialId</var> be the result of decoding <a data-link-type="dfn" href="#base64url-encoding" id="ref-for-base64url-encoding②①">Base64url Encoding</a> on the <var>parameters</var>’ <var>credentialId</var> property.</p>
     <li data-md>
      <p>If <var>credentialId</var> is failure, return a <a data-link-type="dfn" href="https://w3c.github.io/webdriver/#dfn-error" id="ref-for-dfn-error⑨">WebDriver error</a> with <a data-link-type="dfn" href="https://w3c.github.io/webdriver/#dfn-error-code" id="ref-for-dfn-error-code⑨">WebDriver error code</a> <a data-link-type="dfn" href="https://w3c.github.io/webdriver/#dfn-invalid-argument" id="ref-for-dfn-invalid-argument⑧">invalid argument</a>.</p>
     <li data-md>
@@ -6956,7 +7034,7 @@ <h3 class="heading settled" data-level="11.5" id="sctn-automation-add-credential
     <li data-md>
      <p>If <var>rpId</var> is not a valid <a data-link-type="dfn" href="#rp-id" id="ref-for-rp-id④⑧">RP ID</a>, return a <a data-link-type="dfn" href="https://w3c.github.io/webdriver/#dfn-error" id="ref-for-dfn-error①①">WebDriver error</a> with <a data-link-type="dfn" href="https://w3c.github.io/webdriver/#dfn-error-code" id="ref-for-dfn-error-code①①">WebDriver error code</a> <a data-link-type="dfn" href="https://w3c.github.io/webdriver/#dfn-invalid-argument" id="ref-for-dfn-invalid-argument①⓪">invalid argument</a>.</p>
     <li data-md>
-     <p>Let <var>privateKey</var> be the result of decoding <a data-link-type="dfn" href="#base64url-encoding" id="ref-for-base64url-encoding②③">Base64url Encoding</a> on the <var>parameters</var>’ <var>privateKey</var> property.</p>
+     <p>Let <var>privateKey</var> be the result of decoding <a data-link-type="dfn" href="#base64url-encoding" id="ref-for-base64url-encoding②②">Base64url Encoding</a> on the <var>parameters</var>’ <var>privateKey</var> property.</p>
     <li data-md>
      <p>If <var>privateKey</var> is failure, return a <a data-link-type="dfn" href="https://w3c.github.io/webdriver/#dfn-error" id="ref-for-dfn-error①②">WebDriver error</a> with <a data-link-type="dfn" href="https://w3c.github.io/webdriver/#dfn-error-code" id="ref-for-dfn-error-code①②">WebDriver error code</a> <a data-link-type="dfn" href="https://w3c.github.io/webdriver/#dfn-invalid-argument" id="ref-for-dfn-invalid-argument①①">invalid argument</a>.</p>
     <li data-md>
@@ -6966,7 +7044,7 @@ <h3 class="heading settled" data-level="11.5" id="sctn-automation-add-credential
      <p>If the <var>parameters</var>’ <var>userHandle</var> property is defined:</p>
      <ol>
       <li data-md>
-       <p>Let <var>userHandle</var> be the result of decoding <a data-link-type="dfn" href="#base64url-encoding" id="ref-for-base64url-encoding②④">Base64url Encoding</a> on the <var>parameters</var>’ <var>userHandle</var> property.</p>
+       <p>Let <var>userHandle</var> be the result of decoding <a data-link-type="dfn" href="#base64url-encoding" id="ref-for-base64url-encoding②③">Base64url Encoding</a> on the <var>parameters</var>’ <var>userHandle</var> property.</p>
       <li data-md>
        <p>If <var>userHandle</var> is failure, return a <a data-link-type="dfn" href="https://w3c.github.io/webdriver/#dfn-error" id="ref-for-dfn-error①④">WebDriver error</a> with <a data-link-type="dfn" href="https://w3c.github.io/webdriver/#dfn-error-code" id="ref-for-dfn-error-code①④">WebDriver error code</a> <a data-link-type="dfn" href="https://w3c.github.io/webdriver/#dfn-invalid-argument" id="ref-for-dfn-invalid-argument①③">invalid argument</a>.</p>
      </ol>
@@ -6989,7 +7067,7 @@ <h3 class="heading settled" data-level="11.5" id="sctn-automation-add-credential
      <p>If the <var>authenticator</var> supports the <a data-link-type="dfn" href="#largeblob" id="ref-for-largeblob③">largeBlob</a> extension and the <var>parameters</var>’ <var>largeBlob</var> feature is defined:</p>
      <ol>
       <li data-md>
-       <p>Let <var>largeBlob</var> be the result of decoding <a data-link-type="dfn" href="#base64url-encoding" id="ref-for-base64url-encoding②⑤">Base64url Encoding</a> on the <var>parameters</var>’ <var>largeBlob</var> property.</p>
+       <p>Let <var>largeBlob</var> be the result of decoding <a data-link-type="dfn" href="#base64url-encoding" id="ref-for-base64url-encoding②④">Base64url Encoding</a> on the <var>parameters</var>’ <var>largeBlob</var> property.</p>
       <li data-md>
        <p>If <var>largeBlob</var> is failure, return a <a data-link-type="dfn" href="https://w3c.github.io/webdriver/#dfn-error" id="ref-for-dfn-error①⑧">WebDriver error</a> with <a data-link-type="dfn" href="https://w3c.github.io/webdriver/#dfn-error-code" id="ref-for-dfn-error-code①⑧">WebDriver error code</a> <a data-link-type="dfn" href="https://w3c.github.io/webdriver/#dfn-invalid-argument" id="ref-for-dfn-invalid-argument①⑦">invalid argument</a>.</p>
      </ol>
@@ -7002,7 +7080,7 @@ <h3 class="heading settled" data-level="11.5" id="sctn-automation-add-credential
     <li data-md>
      <p>Let <var>credential</var> be a new <a data-link-type="dfn" href="#client-side-discoverable-public-key-credential-source" id="ref-for-client-side-discoverable-public-key-credential-source⑦">Client-side discoverable Public Key Credential Source</a> if <var>isResidentCredential</var> is <code>true</code> or a <a data-link-type="dfn" href="#server-side-public-key-credential-source" id="ref-for-server-side-public-key-credential-source②">Server-side Public Key Credential Source</a> otherwise whose items are:</p>
      <dl>
-      <dt data-md><a data-link-type="dfn" href="#public-key-credential-source-type" id="ref-for-public-key-credential-source-type③">type</a>
+      <dt data-md><a data-link-type="dfn" href="#public-key-credential-source-type" id="ref-for-public-key-credential-source-type④">type</a>
       <dd data-md>
        <p><code class="idl"><a data-link-type="idl" href="#dom-publickeycredentialtype-public-key" id="ref-for-dom-publickeycredentialtype-public-key⑥">public-key</a></code></p>
       <dt data-md><a data-link-type="dfn" href="#public-key-credential-source-id" id="ref-for-public-key-credential-source-id⑥">id</a>
@@ -7019,7 +7097,7 @@ <h3 class="heading settled" data-level="11.5" id="sctn-automation-add-credential
        <p><var>userHandle</var></p>
      </dl>
     <li data-md>
-     <p>Associate a <a data-link-type="dfn" href="#signature-counter" id="ref-for-signature-counter②⑦">signature counter</a> <var>counter</var> to the <var>credential</var> with a starting value equal to the <var>parameters</var>’ <var>signCount</var> or <code>0</code> if <var>signCount</var> is <code>null</code>.</p>
+     <p>Associate a <a data-link-type="dfn" href="#signature-counter" id="ref-for-signature-counter②⑤">signature counter</a> <var>counter</var> to the <var>credential</var> with a starting value equal to the <var>parameters</var>’ <var>signCount</var> or <code>0</code> if <var>signCount</var> is <code>null</code>.</p>
     <li data-md>
      <p>If <var>largeBlob</var> is not <code>null</code>, set the <a data-link-type="dfn" href="https://fidoalliance.org/specs/fido-v2.0-ps-20190130/fido-client-to-authenticator-protocol-v2.0-ps-20190130.html#large-blob" id="ref-for-large-blob②">large, per-credential blob</a> associated to the <var>credential</var> to <var>largeBlob</var>.</p>
     <li data-md>
@@ -7028,7 +7106,7 @@ <h3 class="heading settled" data-level="11.5" id="sctn-automation-add-credential
      <p>Return <a data-link-type="dfn" href="https://w3c.github.io/webdriver/#dfn-success" id="ref-for-dfn-success②">success</a>.</p>
    </ol>
    <h3 class="heading settled" data-level="11.6" id="sctn-automation-get-credentials"><span class="secno">11.6. </span><span class="content"><dfn class="dfn-paneled" data-dfn-type="dfn" data-noexport id="get-credentials">Get Credentials</dfn></span><a class="self-link" href="#sctn-automation-get-credentials"></a></h3>
-   <p>The <a data-link-type="dfn" href="#get-credentials" id="ref-for-get-credentials">Get Credentials</a> WebDriver <a data-link-type="dfn" href="https://w3c.github.io/webdriver/#dfn-extension-command" id="ref-for-dfn-extension-command⑥">extension command</a> returns one <a data-link-type="dfn" href="#credential-parameters" id="ref-for-credential-parameters①">Credential Parameters</a> object for every <a data-link-type="dfn" href="#public-key-credential-source" id="ref-for-public-key-credential-source⑤②">Public Key Credential Source</a> stored in a <a data-link-type="dfn" href="#virtual-authenticators" id="ref-for-virtual-authenticators②⓪">Virtual Authenticator</a>, regardless of whether they were
+   <p>The <a data-link-type="dfn" href="#get-credentials" id="ref-for-get-credentials">Get Credentials</a> WebDriver <a data-link-type="dfn" href="https://w3c.github.io/webdriver/#dfn-extension-command" id="ref-for-dfn-extension-command⑥">extension command</a> returns one <a data-link-type="dfn" href="#credential-parameters" id="ref-for-credential-parameters①">Credential Parameters</a> object for every <a data-link-type="dfn" href="#public-key-credential-source" id="ref-for-public-key-credential-source⑥①">Public Key Credential Source</a> stored in a <a data-link-type="dfn" href="#virtual-authenticators" id="ref-for-virtual-authenticators②⓪">Virtual Authenticator</a>, regardless of whether they were
 stored using <a data-link-type="dfn" href="#add-credential" id="ref-for-add-credential①">Add Credential</a> or <code class="idl"><a data-link-type="idl" href="https://w3c.github.io/webappsec-credential-management/#dom-credentialscontainer-create" id="ref-for-dom-credentialscontainer-create③②">navigator.credentials.create()</a></code>. It is defined as follows:</p>
    <figure class="table" id="table-getCredentials">
     <table class="data">
@@ -7050,13 +7128,13 @@ <h3 class="heading settled" data-level="11.6" id="sctn-automation-get-credential
     <li data-md>
      <p>Let <var>credentialsArray</var> be an empty array.</p>
     <li data-md>
-     <p>For each <a data-link-type="dfn" href="#public-key-credential-source" id="ref-for-public-key-credential-source⑤③">Public Key Credential Source</a> <var>credential</var>, managed by the authenticator identified by <var>authenticatorId</var>,
+     <p>For each <a data-link-type="dfn" href="#public-key-credential-source" id="ref-for-public-key-credential-source⑥②">Public Key Credential Source</a> <var>credential</var>, managed by the authenticator identified by <var>authenticatorId</var>,
 construct a corresponding <a data-link-type="dfn" href="#credential-parameters" id="ref-for-credential-parameters②">Credential Parameters</a> <a data-link-type="dfn" href="https://w3c.github.io/FileAPI/#blob-url-entry-object" id="ref-for-blob-url-entry-object④">Object</a> and add it to <var>credentialsArray</var>.</p>
     <li data-md>
      <p>Return <a data-link-type="dfn" href="https://w3c.github.io/webdriver/#dfn-success" id="ref-for-dfn-success③">success</a> with data containing <var>credentialsArray</var>.</p>
    </ol>
    <h3 class="heading settled" data-level="11.7" id="sctn-automation-remove-credential"><span class="secno">11.7. </span><span class="content"><dfn class="dfn-paneled" data-dfn-type="dfn" data-noexport id="remove-credential">Remove Credential</dfn></span><a class="self-link" href="#sctn-automation-remove-credential"></a></h3>
-   <p>The <a data-link-type="dfn" href="#remove-credential" id="ref-for-remove-credential">Remove Credential</a> WebDriver <a data-link-type="dfn" href="https://w3c.github.io/webdriver/#dfn-extension-command" id="ref-for-dfn-extension-command⑦">extension command</a> removes a <a data-link-type="dfn" href="#public-key-credential-source" id="ref-for-public-key-credential-source⑤④">Public Key Credential Source</a> stored on a <a data-link-type="dfn" href="#virtual-authenticators" id="ref-for-virtual-authenticators②②">Virtual Authenticator</a>. It is defined as follows:</p>
+   <p>The <a data-link-type="dfn" href="#remove-credential" id="ref-for-remove-credential">Remove Credential</a> WebDriver <a data-link-type="dfn" href="https://w3c.github.io/webdriver/#dfn-extension-command" id="ref-for-dfn-extension-command⑦">extension command</a> removes a <a data-link-type="dfn" href="#public-key-credential-source" id="ref-for-public-key-credential-source⑥③">Public Key Credential Source</a> stored on a <a data-link-type="dfn" href="#virtual-authenticators" id="ref-for-virtual-authenticators②②">Virtual Authenticator</a>. It is defined as follows:</p>
    <figure class="table" id="table-removeCredential">
     <table class="data">
      <thead>
@@ -7077,14 +7155,14 @@ <h3 class="heading settled" data-level="11.7" id="sctn-automation-remove-credent
     <li data-md>
      <p>Let <var>authenticator</var> be the <a data-link-type="dfn" href="#virtual-authenticators" id="ref-for-virtual-authenticators②④">Virtual Authenticator</a> identified by <var>authenticatorId</var>.</p>
     <li data-md>
-     <p>If <var>credentialId</var> does not match any <a data-link-type="dfn" href="#public-key-credential-source" id="ref-for-public-key-credential-source⑤⑤">Public Key Credential Source</a> managed by <var>authenticator</var>, return a <a data-link-type="dfn" href="https://w3c.github.io/webdriver/#dfn-error" id="ref-for-dfn-error②①">WebDriver error</a> with <a data-link-type="dfn" href="https://w3c.github.io/webdriver/#dfn-error-code" id="ref-for-dfn-error-code②①">WebDriver error code</a> <a data-link-type="dfn" href="https://w3c.github.io/webdriver/#dfn-invalid-argument" id="ref-for-dfn-invalid-argument②⓪">invalid argument</a>.</p>
+     <p>If <var>credentialId</var> does not match any <a data-link-type="dfn" href="#public-key-credential-source" id="ref-for-public-key-credential-source⑥④">Public Key Credential Source</a> managed by <var>authenticator</var>, return a <a data-link-type="dfn" href="https://w3c.github.io/webdriver/#dfn-error" id="ref-for-dfn-error②①">WebDriver error</a> with <a data-link-type="dfn" href="https://w3c.github.io/webdriver/#dfn-error-code" id="ref-for-dfn-error-code②①">WebDriver error code</a> <a data-link-type="dfn" href="https://w3c.github.io/webdriver/#dfn-invalid-argument" id="ref-for-dfn-invalid-argument②⓪">invalid argument</a>.</p>
     <li data-md>
-     <p>Remove the <a data-link-type="dfn" href="#public-key-credential-source" id="ref-for-public-key-credential-source⑤⑥">Public Key Credential Source</a> identified by <var>credentialId</var> managed by <var>authenticator</var>.</p>
+     <p>Remove the <a data-link-type="dfn" href="#public-key-credential-source" id="ref-for-public-key-credential-source⑥⑤">Public Key Credential Source</a> identified by <var>credentialId</var> managed by <var>authenticator</var>.</p>
     <li data-md>
      <p>Return <a data-link-type="dfn" href="https://w3c.github.io/webdriver/#dfn-success" id="ref-for-dfn-success④">success</a>.</p>
    </ol>
    <h3 class="heading settled" data-level="11.8" id="sctn-automation-remove-all-credentials"><span class="secno">11.8. </span><span class="content"><dfn class="dfn-paneled" data-dfn-type="dfn" data-noexport id="remove-all-credentials">Remove All Credentials</dfn></span><a class="self-link" href="#sctn-automation-remove-all-credentials"></a></h3>
-   <p>The <a data-link-type="dfn" href="#remove-all-credentials" id="ref-for-remove-all-credentials">Remove All Credentials</a> WebDriver <a data-link-type="dfn" href="https://w3c.github.io/webdriver/#dfn-extension-command" id="ref-for-dfn-extension-command⑧">extension command</a> removes all <a data-link-type="dfn" href="#public-key-credential-source" id="ref-for-public-key-credential-source⑤⑦">Public Key Credential Sources</a> stored on a <a data-link-type="dfn" href="#virtual-authenticators" id="ref-for-virtual-authenticators②⑤">Virtual Authenticator</a>. It is defined as follows:</p>
+   <p>The <a data-link-type="dfn" href="#remove-all-credentials" id="ref-for-remove-all-credentials">Remove All Credentials</a> WebDriver <a data-link-type="dfn" href="https://w3c.github.io/webdriver/#dfn-extension-command" id="ref-for-dfn-extension-command⑧">extension command</a> removes all <a data-link-type="dfn" href="#public-key-credential-source" id="ref-for-public-key-credential-source⑥⑥">Public Key Credential Sources</a> stored on a <a data-link-type="dfn" href="#virtual-authenticators" id="ref-for-virtual-authenticators②⑤">Virtual Authenticator</a>. It is defined as follows:</p>
    <figure class="table" id="table-removeAllCredentials">
     <table class="data">
      <thead>
@@ -7103,7 +7181,7 @@ <h3 class="heading settled" data-level="11.8" id="sctn-automation-remove-all-cre
      <p>If <var>authenticatorId</var> does not match any <a data-link-type="dfn" href="#virtual-authenticators" id="ref-for-virtual-authenticators②⑥">Virtual Authenticator</a> stored in the <a data-link-type="dfn" href="#virtual-authenticator-database" id="ref-for-virtual-authenticator-database⑥">Virtual Authenticator
  Database</a>, return a <a data-link-type="dfn" href="https://w3c.github.io/webdriver/#dfn-error" id="ref-for-dfn-error②②">WebDriver error</a> with <a data-link-type="dfn" href="https://w3c.github.io/webdriver/#dfn-error-code" id="ref-for-dfn-error-code②②">WebDriver error code</a> <a data-link-type="dfn" href="https://w3c.github.io/webdriver/#dfn-invalid-argument" id="ref-for-dfn-invalid-argument②①">invalid argument</a>.</p>
     <li data-md>
-     <p>Remove all <a data-link-type="dfn" href="#public-key-credential-source" id="ref-for-public-key-credential-source⑤⑧">Public Key Credential Sources</a> managed by the <a data-link-type="dfn" href="#virtual-authenticators" id="ref-for-virtual-authenticators②⑦">Virtual Authenticator</a> identified by <var>authenticatorId</var>.</p>
+     <p>Remove all <a data-link-type="dfn" href="#public-key-credential-source" id="ref-for-public-key-credential-source⑥⑦">Public Key Credential Sources</a> managed by the <a data-link-type="dfn" href="#virtual-authenticators" id="ref-for-virtual-authenticators②⑦">Virtual Authenticator</a> identified by <var>authenticatorId</var>.</p>
     <li data-md>
      <p>Return <a data-link-type="dfn" href="https://w3c.github.io/webdriver/#dfn-success" id="ref-for-dfn-success⑤">success</a>.</p>
    </ol>
@@ -7227,188 +7305,188 @@ <h3 class="heading settled" data-level="12.4" id="sctn-extensions-reg"><span cla
      <p>WebAuthn Extension Identifier: credProps</p>
     <li data-md>
      <p>Description: This <a data-link-type="dfn" href="#client-extension" id="ref-for-client-extension①③">client</a> <a data-link-type="dfn" href="#registration-extension" id="ref-for-registration-extension②③">registration extension</a> enables reporting of a newly-created <a data-link-type="dfn" href="https://w3c.github.io/webappsec-credential-management/#concept-credential" id="ref-for-concept-credential②①">credential</a>'s properties,
-as determined by the <a data-link-type="dfn" href="#client" id="ref-for-client⑧⑧">client</a>, to the calling <a data-link-type="dfn" href="#webauthn-relying-party" id="ref-for-webauthn-relying-party④②">WebAuthn Relying Party</a>'s <a data-link-type="dfn" href="#web-application" id="ref-for-web-application⑤">web application</a>.</p>
+as determined by the <a data-link-type="dfn" href="#client" id="ref-for-client⑧⑦">client</a>, to the calling <a data-link-type="dfn" href="#webauthn-relying-party" id="ref-for-webauthn-relying-party④②">WebAuthn Relying Party</a>'s <a data-link-type="dfn" href="#web-application" id="ref-for-web-application⑤">web application</a>.</p>
     <li data-md>
      <p>Specification Document: Section <a href="#sctn-authenticator-credential-properties-extension">§ 10.1.3 Credential Properties Extension (credProps)</a> of this specification <br><br></p>
     <li data-md>
      <p>WebAuthn Extension Identifier: largeBlob</p>
     <li data-md>
-     <p>Description: This <a data-link-type="dfn" href="#client-extension" id="ref-for-client-extension①④">client</a> <a data-link-type="dfn" href="#registration-extension" id="ref-for-registration-extension②④">registration extension</a> and <a data-link-type="dfn" href="#authentication-extension" id="ref-for-authentication-extension②①">authentication extension</a> allows a <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party②⑧⑧">Relying Party</a> to store opaque data associated with a credential.</p>
+     <p>Description: This <a data-link-type="dfn" href="#client-extension" id="ref-for-client-extension①④">client</a> <a data-link-type="dfn" href="#registration-extension" id="ref-for-registration-extension②④">registration extension</a> and <a data-link-type="dfn" href="#authentication-extension" id="ref-for-authentication-extension②①">authentication extension</a> allows a <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party②⑨⑤">Relying Party</a> to store opaque data associated with a credential.</p>
     <li data-md>
      <p>Specification Document: Section <a href="#sctn-large-blob-extension">§ 10.1.5 Large blob storage extension (largeBlob)</a> of this specification</p>
    </ul>
    <h2 class="heading settled" data-level="13" id="sctn-security-considerations"><span class="secno">13. </span><span class="content">Security Considerations</span><a class="self-link" href="#sctn-security-considerations"></a></h2>
    <p>This specification defines a <a href="#sctn-api">Web API</a> and a cryptographic peer-entity authentication protocol.
-The <a data-link-type="dfn" href="#web-authentication-api" id="ref-for-web-authentication-api①⑤">Web Authentication API</a> allows Web developers (i.e., "authors") to utilize the Web Authentication protocol in their <a data-link-type="dfn" href="#registration" id="ref-for-registration②②">registration</a> and <a data-link-type="dfn" href="#authentication" id="ref-for-authentication①⑤">authentication</a> <a data-link-type="dfn" href="#ceremony" id="ref-for-ceremony①①">ceremonies</a>.
+The <a data-link-type="dfn" href="#web-authentication-api" id="ref-for-web-authentication-api①⑤">Web Authentication API</a> allows Web developers (i.e., "authors") to utilize the Web Authentication protocol in their <a data-link-type="dfn" href="#registration" id="ref-for-registration②⑤">registration</a> and <a data-link-type="dfn" href="#authentication" id="ref-for-authentication①⑤">authentication</a> <a data-link-type="dfn" href="#ceremony" id="ref-for-ceremony①③">ceremonies</a>.
 The entities comprising the Web Authentication protocol endpoints are user-controlled <a data-link-type="dfn" href="#webauthn-authenticator" id="ref-for-webauthn-authenticator⑦">WebAuthn Authenticators</a> and a <a data-link-type="dfn" href="#webauthn-relying-party" id="ref-for-webauthn-relying-party④③">WebAuthn Relying Party</a>'s
-computing environment hosting the <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party②⑧⑨">Relying Party</a>'s <a data-link-type="dfn" href="#web-application" id="ref-for-web-application⑥">web application</a>.
-In this model, the user agent, together with the <a data-link-type="dfn" href="#webauthn-client" id="ref-for-webauthn-client⑦">WebAuthn Client</a>, comprise an intermediary between <a data-link-type="dfn" href="#authenticator" id="ref-for-authenticator②③⑦">authenticators</a> and <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party②⑨⓪">Relying Parties</a>.
-Additionally, <a data-link-type="dfn" href="#authenticator" id="ref-for-authenticator②③⑧">authenticators</a> can <a data-link-type="dfn" href="#attestation" id="ref-for-attestation②⓪">attest</a> to <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party②⑨①">Relying Parties</a> as to their provenance.</p>
+computing environment hosting the <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party②⑨⑥">Relying Party</a>'s <a data-link-type="dfn" href="#web-application" id="ref-for-web-application⑥">web application</a>.
+In this model, the user agent, together with the <a data-link-type="dfn" href="#webauthn-client" id="ref-for-webauthn-client⑦">WebAuthn Client</a>, comprise an intermediary between <a data-link-type="dfn" href="#authenticator" id="ref-for-authenticator②③⑥">authenticators</a> and <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party②⑨⑦">Relying Parties</a>.
+Additionally, <a data-link-type="dfn" href="#authenticator" id="ref-for-authenticator②③⑦">authenticators</a> can <a data-link-type="dfn" href="#attestation" id="ref-for-attestation②⓪">attest</a> to <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party②⑨⑧">Relying Parties</a> as to their provenance.</p>
    <p>At this time, this specification does not feature detailed security considerations. However, the <a data-link-type="biblio" href="#biblio-fidosecref">[FIDOSecRef]</a> document provides a security analysis which is overall applicable to this specification.
-Also, the <a data-link-type="biblio" href="#biblio-fidoauthnrsecreqs">[FIDOAuthnrSecReqs]</a> document suite provides useful information about <a data-link-type="dfn" href="#authenticator" id="ref-for-authenticator②③⑨">authenticator</a> security characteristics.</p>
+Also, the <a data-link-type="biblio" href="#biblio-fidoauthnrsecreqs">[FIDOAuthnrSecReqs]</a> document suite provides useful information about <a data-link-type="dfn" href="#authenticator" id="ref-for-authenticator②③⑧">authenticator</a> security characteristics.</p>
    <p>The below subsections comprise the current Web Authentication-specific security considerations.
 They are divided by audience;
 general security considerations are direct subsections of this section,
-while security considerations specifically for <a data-link-type="dfn" href="#authenticator" id="ref-for-authenticator②④⓪">authenticator</a>, <a data-link-type="dfn" href="#client" id="ref-for-client⑧⑨">client</a> and <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party②⑨②">Relying Party</a> implementers
+while security considerations specifically for <a data-link-type="dfn" href="#authenticator" id="ref-for-authenticator②③⑨">authenticator</a>, <a data-link-type="dfn" href="#client" id="ref-for-client⑧⑧">client</a> and <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party②⑨⑨">Relying Party</a> implementers
 are grouped into respective subsections.</p>
    <h3 class="heading settled" data-level="13.1" id="sctn-credentialIdSecurity"><span class="secno">13.1. </span><span class="content">Credential ID Unsigned</span><a class="self-link" href="#sctn-credentialIdSecurity"></a></h3>
-   <p>The <a data-link-type="dfn" href="#credential-id" id="ref-for-credential-id④⓪">credential ID</a> is not signed.
-This is not a problem because all that would happen if an <a data-link-type="dfn" href="#authenticator" id="ref-for-authenticator②④①">authenticator</a> returns
-the wrong <a data-link-type="dfn" href="#credential-id" id="ref-for-credential-id④①">credential ID</a>, or if an attacker intercepts and manipulates the <a data-link-type="dfn" href="#credential-id" id="ref-for-credential-id④②">credential ID</a>, is that the <a data-link-type="dfn" href="#webauthn-relying-party" id="ref-for-webauthn-relying-party④④">WebAuthn Relying Party</a> would not look up the correct <a data-link-type="dfn" href="#credential-public-key" id="ref-for-credential-public-key③⑤">credential public key</a> with which to verify the returned signed <a data-link-type="dfn" href="#authenticator-data" id="ref-for-authenticator-data④⑧">authenticator data</a> (a.k.a., <a data-link-type="dfn" href="#assertion" id="ref-for-assertion①②">assertion</a>), and thus the interaction would end in an error.</p>
+   <p>The <a data-link-type="dfn" href="#credential-id" id="ref-for-credential-id④①">credential ID</a> is not signed.
+This is not a problem because all that would happen if an <a data-link-type="dfn" href="#authenticator" id="ref-for-authenticator②④⓪">authenticator</a> returns
+the wrong <a data-link-type="dfn" href="#credential-id" id="ref-for-credential-id④②">credential ID</a>, or if an attacker intercepts and manipulates the <a data-link-type="dfn" href="#credential-id" id="ref-for-credential-id④③">credential ID</a>, is that the <a data-link-type="dfn" href="#webauthn-relying-party" id="ref-for-webauthn-relying-party④④">WebAuthn Relying Party</a> would not look up the correct <a data-link-type="dfn" href="#credential-public-key" id="ref-for-credential-public-key③⑤">credential public key</a> with which to verify the returned signed <a data-link-type="dfn" href="#authenticator-data" id="ref-for-authenticator-data⑤⓪">authenticator data</a> (a.k.a., <a data-link-type="dfn" href="#assertion" id="ref-for-assertion①②">assertion</a>), and thus the interaction would end in an error.</p>
    <h3 class="heading settled" data-level="13.2" id="sctn-client-authenticator-proximity"><span class="secno">13.2. </span><span class="content">Physical Proximity between Client and Authenticator</span><a class="self-link" href="#sctn-client-authenticator-proximity"></a></h3>
-   <p>In the WebAuthn <a data-link-type="dfn" href="#authenticator-model" id="ref-for-authenticator-model④">authenticator model</a>, it is generally assumed that <a data-link-type="dfn" href="#roaming-authenticators" id="ref-for-roaming-authenticators②⑤">roaming authenticators</a> are physically close to, and communicate directly with, the <a data-link-type="dfn" href="#client" id="ref-for-client⑨⓪">client</a>.
+   <p>In the WebAuthn <a data-link-type="dfn" href="#authenticator-model" id="ref-for-authenticator-model④">authenticator model</a>, it is generally assumed that <a data-link-type="dfn" href="#roaming-authenticators" id="ref-for-roaming-authenticators②⑤">roaming authenticators</a> are physically close to, and communicate directly with, the <a data-link-type="dfn" href="#client" id="ref-for-client⑧⑨">client</a>.
 This arrangement has some important advantages.</p>
-   <p>The promise of physical proximity between <a data-link-type="dfn" href="#client" id="ref-for-client⑨①">client</a> and <a data-link-type="dfn" href="#authenticator" id="ref-for-authenticator②④②">authenticator</a> is a key strength of a <a data-link-type="dfn" href="https://pages.nist.gov/800-63-3/sp800-63-3.html#af" id="ref-for-af②①">something you have</a> <a data-link-type="dfn" href="https://pages.nist.gov/800-63-3/sp800-63-3.html#af" id="ref-for-af②②">authentication factor</a>.
+   <p>The promise of physical proximity between <a data-link-type="dfn" href="#client" id="ref-for-client⑨⓪">client</a> and <a data-link-type="dfn" href="#authenticator" id="ref-for-authenticator②④①">authenticator</a> is a key strength of a <a data-link-type="dfn" href="https://pages.nist.gov/800-63-3/sp800-63-3.html#af" id="ref-for-af②①">something you have</a> <a data-link-type="dfn" href="https://pages.nist.gov/800-63-3/sp800-63-3.html#af" id="ref-for-af②②">authentication factor</a>.
 For example, if a <a data-link-type="dfn" href="#roaming-authenticators" id="ref-for-roaming-authenticators②⑥">roaming authenticator</a> can communicate only via USB or Bluetooth,
 the limited range of these transports ensures that any malicious actor
-must physically be within that range in order to interact with the <a data-link-type="dfn" href="#authenticator" id="ref-for-authenticator②④③">authenticator</a>.
-This is not necessarily true of an <a data-link-type="dfn" href="#authenticator" id="ref-for-authenticator②④④">authenticator</a> that can be invoked remotely —
-even if the <a data-link-type="dfn" href="#authenticator" id="ref-for-authenticator②④⑤">authenticator</a> verifies <a data-link-type="dfn" href="#concept-user-present" id="ref-for-concept-user-present④">user presence</a>,
+must physically be within that range in order to interact with the <a data-link-type="dfn" href="#authenticator" id="ref-for-authenticator②④②">authenticator</a>.
+This is not necessarily true of an <a data-link-type="dfn" href="#authenticator" id="ref-for-authenticator②④③">authenticator</a> that can be invoked remotely —
+even if the <a data-link-type="dfn" href="#authenticator" id="ref-for-authenticator②④④">authenticator</a> verifies <a data-link-type="dfn" href="#concept-user-present" id="ref-for-concept-user-present④">user presence</a>,
 users can be tricked into authorizing remotely initiated malicious requests.</p>
-   <p>Direct communication between <a data-link-type="dfn" href="#client" id="ref-for-client⑨②">client</a> and <a data-link-type="dfn" href="#authenticator" id="ref-for-authenticator②④⑥">authenticator</a> means the <a data-link-type="dfn" href="#client" id="ref-for-client⑨③">client</a> can enforce the <a data-link-type="dfn" href="#scope" id="ref-for-scope②⓪">scope</a> restrictions for <a data-link-type="dfn" href="https://w3c.github.io/webappsec-credential-management/#concept-credential" id="ref-for-concept-credential②②">credentials</a>.
-By contrast, if the communication between <a data-link-type="dfn" href="#client" id="ref-for-client⑨④">client</a> and <a data-link-type="dfn" href="#authenticator" id="ref-for-authenticator②④⑦">authenticator</a> is mediated by some third party,
-then the <a data-link-type="dfn" href="#client" id="ref-for-client⑨⑤">client</a> has to trust the third party to
-enforce the <a data-link-type="dfn" href="#scope" id="ref-for-scope②①">scope</a> restrictions and control access to the <a data-link-type="dfn" href="#authenticator" id="ref-for-authenticator②④⑧">authenticator</a>.
+   <p>Direct communication between <a data-link-type="dfn" href="#client" id="ref-for-client⑨①">client</a> and <a data-link-type="dfn" href="#authenticator" id="ref-for-authenticator②④⑤">authenticator</a> means the <a data-link-type="dfn" href="#client" id="ref-for-client⑨②">client</a> can enforce the <a data-link-type="dfn" href="#scope" id="ref-for-scope②⓪">scope</a> restrictions for <a data-link-type="dfn" href="https://w3c.github.io/webappsec-credential-management/#concept-credential" id="ref-for-concept-credential②②">credentials</a>.
+By contrast, if the communication between <a data-link-type="dfn" href="#client" id="ref-for-client⑨③">client</a> and <a data-link-type="dfn" href="#authenticator" id="ref-for-authenticator②④⑥">authenticator</a> is mediated by some third party,
+then the <a data-link-type="dfn" href="#client" id="ref-for-client⑨④">client</a> has to trust the third party to
+enforce the <a data-link-type="dfn" href="#scope" id="ref-for-scope②①">scope</a> restrictions and control access to the <a data-link-type="dfn" href="#authenticator" id="ref-for-authenticator②④⑦">authenticator</a>.
 Failure to do either could result in
-a malicious <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party②⑨③">Relying Party</a> receiving <a data-link-type="dfn" href="#authentication-assertion" id="ref-for-authentication-assertion①④">authentication assertions</a> valid for other <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party②⑨④">Relying Parties</a>,
+a malicious <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party③⓪⓪">Relying Party</a> receiving <a data-link-type="dfn" href="#authentication-assertion" id="ref-for-authentication-assertion①④">authentication assertions</a> valid for other <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party③⓪①">Relying Parties</a>,
 or in a malicious user gaining access to <a data-link-type="dfn" href="#authentication-assertion" id="ref-for-authentication-assertion①⑤">authentication assertions</a> for other users.</p>
-   <p>If designing a solution where the <a data-link-type="dfn" href="#authenticator" id="ref-for-authenticator②④⑨">authenticator</a> does not need to be physically close to the <a data-link-type="dfn" href="#client" id="ref-for-client⑨⑥">client</a>,
-or where <a data-link-type="dfn" href="#client" id="ref-for-client⑨⑦">client</a> and <a data-link-type="dfn" href="#authenticator" id="ref-for-authenticator②⑤⓪">authenticator</a> do not communicate directly,
+   <p>If designing a solution where the <a data-link-type="dfn" href="#authenticator" id="ref-for-authenticator②④⑧">authenticator</a> does not need to be physically close to the <a data-link-type="dfn" href="#client" id="ref-for-client⑨⑤">client</a>,
+or where <a data-link-type="dfn" href="#client" id="ref-for-client⑨⑥">client</a> and <a data-link-type="dfn" href="#authenticator" id="ref-for-authenticator②④⑨">authenticator</a> do not communicate directly,
 designers SHOULD consider how this affects the enforcement of <a data-link-type="dfn" href="#scope" id="ref-for-scope②②">scope</a> restrictions
-and the strength of the <a data-link-type="dfn" href="#authenticator" id="ref-for-authenticator②⑤①">authenticator</a> as a <a data-link-type="dfn" href="https://pages.nist.gov/800-63-3/sp800-63-3.html#af" id="ref-for-af②③">something you have</a> authentication factor.</p>
-   <h3 class="heading settled" data-level="13.3" id="sctn-security-considerations-authenticator"><span class="secno">13.3. </span><span class="content">Security considerations for <a data-link-type="dfn" href="#authenticator" id="ref-for-authenticator②⑤②">authenticators</a> <span id="sctn-attestation-security-considerations"></span></span><a class="self-link" href="#sctn-security-considerations-authenticator"></a></h3>
+and the strength of the <a data-link-type="dfn" href="#authenticator" id="ref-for-authenticator②⑤⓪">authenticator</a> as a <a data-link-type="dfn" href="https://pages.nist.gov/800-63-3/sp800-63-3.html#af" id="ref-for-af②③">something you have</a> authentication factor.</p>
+   <h3 class="heading settled" data-level="13.3" id="sctn-security-considerations-authenticator"><span class="secno">13.3. </span><span class="content">Security considerations for <a data-link-type="dfn" href="#authenticator" id="ref-for-authenticator②⑤①">authenticators</a> <span id="sctn-attestation-security-considerations"></span></span><a class="self-link" href="#sctn-security-considerations-authenticator"></a></h3>
    <h4 class="heading settled" data-level="13.3.1" id="sctn-cert-hierarchy"><span class="secno">13.3.1. </span><span class="content">Attestation Certificate Hierarchy</span><a class="self-link" href="#sctn-cert-hierarchy"></a></h4>
    <p>A 3-tier hierarchy for attestation certificates is RECOMMENDED (i.e., Attestation Root, Attestation Issuing CA, Attestation
 Certificate). It is also RECOMMENDED that for each <a data-link-type="dfn" href="#webauthn-authenticator" id="ref-for-webauthn-authenticator⑧">WebAuthn Authenticator</a> device line (i.e., model), a separate issuing CA is
 used to help facilitate isolating problems with a specific version of an authenticator model.</p>
    <p>If the attestation root certificate is not dedicated to a single <a data-link-type="dfn" href="#webauthn-authenticator" id="ref-for-webauthn-authenticator⑨">WebAuthn Authenticator</a> device line (i.e., AAGUID), the AAGUID
-SHOULD be specified in the attestation certificate itself, so that it can be verified against the <a data-link-type="dfn" href="#authenticator-data" id="ref-for-authenticator-data④⑨">authenticator data</a>.</p>
+SHOULD be specified in the attestation certificate itself, so that it can be verified against the <a data-link-type="dfn" href="#authenticator-data" id="ref-for-authenticator-data⑤①">authenticator data</a>.</p>
    <h4 class="heading settled" data-level="13.3.2" id="sctn-ca-compromise"><span class="secno">13.3.2. </span><span class="content">Attestation Certificate and Attestation Certificate CA Compromise</span><a class="self-link" href="#sctn-ca-compromise"></a></h4>
    <p>When an intermediate CA or a root CA used for issuing attestation certificates is compromised, <a data-link-type="dfn" href="#webauthn-authenticator" id="ref-for-webauthn-authenticator①⓪">WebAuthn Authenticator</a> <a data-link-type="dfn" href="#attestation-key-pair" id="ref-for-attestation-key-pair⑥">attestation key pairs</a> are still safe although their certificates can no longer be trusted. A <a data-link-type="dfn" href="#webauthn-authenticator" id="ref-for-webauthn-authenticator①①">WebAuthn Authenticator</a> manufacturer that
-has recorded the <a data-link-type="dfn" href="#attestation-public-key" id="ref-for-attestation-public-key①">attestation public keys</a> for their <a data-link-type="dfn" href="#authenticator" id="ref-for-authenticator②⑤③">authenticator</a> models can issue new <a data-link-type="dfn" href="#attestation-certificate" id="ref-for-attestation-certificate⑨">attestation certificates</a> for these keys from a new
+has recorded the <a data-link-type="dfn" href="#attestation-public-key" id="ref-for-attestation-public-key①">attestation public keys</a> for their <a data-link-type="dfn" href="#authenticator" id="ref-for-authenticator②⑤②">authenticator</a> models can issue new <a data-link-type="dfn" href="#attestation-certificate" id="ref-for-attestation-certificate⑨">attestation certificates</a> for these keys from a new
 intermediate CA or from a new root CA. If the root CA changes, the <a data-link-type="dfn" href="#webauthn-relying-party" id="ref-for-webauthn-relying-party④⑤">WebAuthn Relying Parties</a> MUST update their trusted root certificates
 accordingly.</p>
    <p>A <a data-link-type="dfn" href="#webauthn-authenticator" id="ref-for-webauthn-authenticator①②">WebAuthn Authenticator</a> <a data-link-type="dfn" href="#attestation-certificate" id="ref-for-attestation-certificate①⓪">attestation certificate</a> MUST be revoked by the issuing CA if its <a data-link-type="dfn" href="#attestation-private-key" id="ref-for-attestation-private-key④">private key</a> has been compromised. A WebAuthn
 Authenticator manufacturer may need to ship a firmware update and inject new <a data-link-type="dfn" href="#attestation-private-key" id="ref-for-attestation-private-key⑤">attestation private keys</a> and <a data-link-type="dfn" href="#attestation-certificate" id="ref-for-attestation-certificate①①">certificates</a> into already
 manufactured <a data-link-type="dfn" href="#webauthn-authenticator" id="ref-for-webauthn-authenticator①③">WebAuthn Authenticators</a>, if the exposure was due to a firmware flaw. (The process by which this happens is out of
 scope for this specification.) If the <a data-link-type="dfn" href="#webauthn-authenticator" id="ref-for-webauthn-authenticator①④">WebAuthn Authenticator</a> manufacturer does not have this capability, then it may not be
-possible for <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party②⑨⑤">Relying Parties</a> to trust any further <a data-link-type="dfn" href="#attestation-statement" id="ref-for-attestation-statement③⑦">attestation statements</a> from the affected <a data-link-type="dfn" href="#webauthn-authenticator" id="ref-for-webauthn-authenticator①⑤">WebAuthn Authenticators</a>.</p>
-   <p>See also the related security consideration for <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party②⑨⑥">Relying Parties</a> in <a href="#sctn-revoked-attestation-certificates">§ 13.4.5 Revoked Attestation Certificates</a>.</p>
-   <h3 class="heading settled" data-level="13.4" id="sctn-security-considerations-rp"><span class="secno">13.4. </span><span class="content">Security considerations for <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party②⑨⑦">Relying Parties</a></span><a class="self-link" href="#sctn-security-considerations-rp"></a></h3>
+possible for <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party③⓪②">Relying Parties</a> to trust any further <a data-link-type="dfn" href="#attestation-statement" id="ref-for-attestation-statement③⑧">attestation statements</a> from the affected <a data-link-type="dfn" href="#webauthn-authenticator" id="ref-for-webauthn-authenticator①⑤">WebAuthn Authenticators</a>.</p>
+   <p>See also the related security consideration for <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party③⓪③">Relying Parties</a> in <a href="#sctn-revoked-attestation-certificates">§ 13.4.5 Revoked Attestation Certificates</a>.</p>
+   <h3 class="heading settled" data-level="13.4" id="sctn-security-considerations-rp"><span class="secno">13.4. </span><span class="content">Security considerations for <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party③⓪④">Relying Parties</a></span><a class="self-link" href="#sctn-security-considerations-rp"></a></h3>
    <h4 class="heading settled" data-level="13.4.1" id="sctn-rp-benefits"><span class="secno">13.4.1. </span><span class="content">Security Benefits for WebAuthn Relying Parties</span><a class="self-link" href="#sctn-rp-benefits"></a></h4>
    <p>The main benefits offered to <a data-link-type="dfn" href="#webauthn-relying-party" id="ref-for-webauthn-relying-party④⑥">WebAuthn Relying Parties</a> by this specification include:</p>
    <ol>
     <li data-md>
      <p>Users and accounts can be secured using widely compatible, easy-to-use multi-factor authentication.</p>
     <li data-md>
-     <p>The <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party②⑨⑧">Relying Party</a> does not need to provision <a data-link-type="dfn" href="#authenticator" id="ref-for-authenticator②⑤④">authenticator</a> hardware to its users. Instead, each user can independently obtain
-any conforming <a data-link-type="dfn" href="#authenticator" id="ref-for-authenticator②⑤⑤">authenticator</a> and use that same <a data-link-type="dfn" href="#authenticator" id="ref-for-authenticator②⑤⑥">authenticator</a> with any number of <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party②⑨⑨">Relying Parties</a>. The <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party③⓪⓪">Relying Party</a> can optionally
-enforce requirements on <a data-link-type="dfn" href="#authenticator" id="ref-for-authenticator②⑤⑦">authenticators</a>' security properties by inspecting the <a data-link-type="dfn" href="#attestation-statement" id="ref-for-attestation-statement③⑧">attestation statements</a> returned from the <a data-link-type="dfn" href="#authenticator" id="ref-for-authenticator②⑤⑧">authenticators</a>.</p>
+     <p>The <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party③⓪⑤">Relying Party</a> does not need to provision <a data-link-type="dfn" href="#authenticator" id="ref-for-authenticator②⑤③">authenticator</a> hardware to its users. Instead, each user can independently obtain
+any conforming <a data-link-type="dfn" href="#authenticator" id="ref-for-authenticator②⑤④">authenticator</a> and use that same <a data-link-type="dfn" href="#authenticator" id="ref-for-authenticator②⑤⑤">authenticator</a> with any number of <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party③⓪⑥">Relying Parties</a>. The <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party③⓪⑦">Relying Party</a> can optionally
+enforce requirements on <a data-link-type="dfn" href="#authenticator" id="ref-for-authenticator②⑤⑥">authenticators</a>' security properties by inspecting the <a data-link-type="dfn" href="#attestation-statement" id="ref-for-attestation-statement③⑨">attestation statements</a> returned from the <a data-link-type="dfn" href="#authenticator" id="ref-for-authenticator②⑤⑦">authenticators</a>.</p>
     <li data-md>
      <p><a data-link-type="dfn" href="#authentication-ceremony" id="ref-for-authentication-ceremony②⑦">Authentication ceremonies</a> are resistant to <a data-link-type="dfn" href="https://tools.ietf.org/html/rfc4949#page-186" id="ref-for-page-186">man-in-the-middle attacks</a>.
 Regarding <a data-link-type="dfn" href="#registration-ceremony" id="ref-for-registration-ceremony①④">registration ceremonies</a>, see <a href="#sctn-attestation-limitations">§ 13.4.4 Attestation Limitations</a>, below.</p>
     <li data-md>
-     <p>The <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party③⓪①">Relying Party</a> can automatically support multiple types of <a data-link-type="dfn" href="#user-verification" id="ref-for-user-verification④⑨">user verification</a> - for example PIN, biometrics and/or future
-methods - with little or no code change, and can let each user decide which they prefer to use via their choice of <a data-link-type="dfn" href="#authenticator" id="ref-for-authenticator②⑤⑨">authenticator</a>.</p>
+     <p>The <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party③⓪⑧">Relying Party</a> can automatically support multiple types of <a data-link-type="dfn" href="#user-verification" id="ref-for-user-verification④⑨">user verification</a> - for example PIN, biometrics and/or future
+methods - with little or no code change, and can let each user decide which they prefer to use via their choice of <a data-link-type="dfn" href="#authenticator" id="ref-for-authenticator②⑤⑧">authenticator</a>.</p>
     <li data-md>
-     <p>The <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party③⓪②">Relying Party</a> does not need to store additional secrets in order to gain the above benefits.</p>
+     <p>The <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party③⓪⑨">Relying Party</a> does not need to store additional secrets in order to gain the above benefits.</p>
    </ol>
-   <p>As stated in the <a href="#sctn-conforming-relying-parties">Conformance</a> section, the <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party③⓪③">Relying Party</a> MUST behave as described in <a href="#sctn-rp-operations">§ 7 WebAuthn Relying Party Operations</a> to obtain all of the above security benefits. However, one notable use case that departs slightly from this is described below in <a href="#sctn-attestation-limitations">§ 13.4.4 Attestation Limitations</a>.</p>
+   <p>As stated in the <a href="#sctn-conforming-relying-parties">Conformance</a> section, the <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party③①⓪">Relying Party</a> MUST behave as described in <a href="#sctn-rp-operations">§ 7 WebAuthn Relying Party Operations</a> to obtain all of the above security benefits. However, one notable use case that departs slightly from this is described below in <a href="#sctn-attestation-limitations">§ 13.4.4 Attestation Limitations</a>.</p>
    <h4 class="heading settled" data-level="13.4.2" id="sctn-seccons-visibility"><span class="secno">13.4.2. </span><span class="content">Visibility Considerations for Embedded Usage</span><a class="self-link" href="#sctn-seccons-visibility"></a></h4>
-   <p>Simplistic use of WebAuthn in an embedded context, e.g., within <code><a data-link-type="element" href="https://html.spec.whatwg.org/multipage/iframe-embed-object.html#the-iframe-element" id="ref-for-the-iframe-element④">iframe</a></code>s as described in <a href="#sctn-iframe-guidance">§ 5.10 Using Web Authentication within iframe elements</a>, may make users vulnerable to <dfn class="dfn-paneled" data-dfn-type="dfn" data-noexport id="ui-redressing">UI Redressing</dfn> attacks, also known as "<a href="https://en.wikipedia.org/wiki/Clickjacking">Clickjacking</a>". This is where an attacker overlays their own UI on top of a <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party③⓪④">Relying Party</a>'s intended UI and attempts to trick the user into performing unintended actions with the <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party③⓪⑤">Relying Party</a>. For example, using these techniques, an attacker might be able to trick users into purchasing items, transferring money, etc.</p>
-   <p>Even though WebAuthn-specific UI is typically handled by the <a data-link-type="dfn" href="#client-platform" id="ref-for-client-platform⑤③">client platform</a> and thus is not vulnerable to <a data-link-type="dfn" href="#ui-redressing" id="ref-for-ui-redressing①">UI Redressing</a>, it is likely important for an <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party③⓪⑥">Relying Party</a> having embedded WebAuthn-wielding content to ensure that their content’s UI is visible to the user. An emerging means to do so is by observing the status of the experimental <a href="https://w3c.github.io/IntersectionObserver/v2/">Intersection Observer v2</a>'s <code>isVisible</code> attribute. For example, the <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party③⓪⑦">Relying Party</a>'s script running in the embedded context could pre-emptively load itself in a popup window if it detects <code>isVisble</code> being set to <code>false</code>, thus side-stepping any occlusion of their content.</p>
+   <p>Simplistic use of WebAuthn in an embedded context, e.g., within <code><a data-link-type="element" href="https://html.spec.whatwg.org/multipage/iframe-embed-object.html#the-iframe-element" id="ref-for-the-iframe-element④">iframe</a></code>s as described in <a href="#sctn-iframe-guidance">§ 5.10 Using Web Authentication within iframe elements</a>, may make users vulnerable to <dfn class="dfn-paneled" data-dfn-type="dfn" data-noexport id="ui-redressing">UI Redressing</dfn> attacks, also known as "<a href="https://en.wikipedia.org/wiki/Clickjacking">Clickjacking</a>". This is where an attacker overlays their own UI on top of a <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party③①①">Relying Party</a>'s intended UI and attempts to trick the user into performing unintended actions with the <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party③①②">Relying Party</a>. For example, using these techniques, an attacker might be able to trick users into purchasing items, transferring money, etc.</p>
+   <p>Even though WebAuthn-specific UI is typically handled by the <a data-link-type="dfn" href="#client-platform" id="ref-for-client-platform⑤③">client platform</a> and thus is not vulnerable to <a data-link-type="dfn" href="#ui-redressing" id="ref-for-ui-redressing①">UI Redressing</a>, it is likely important for an <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party③①③">Relying Party</a> having embedded WebAuthn-wielding content to ensure that their content’s UI is visible to the user. An emerging means to do so is by observing the status of the experimental <a href="https://w3c.github.io/IntersectionObserver/v2/">Intersection Observer v2</a>'s <code>isVisible</code> attribute. For example, the <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party③①④">Relying Party</a>'s script running in the embedded context could pre-emptively load itself in a popup window if it detects <code>isVisble</code> being set to <code>false</code>, thus side-stepping any occlusion of their content.</p>
    <h4 class="heading settled" data-level="13.4.3" id="sctn-cryptographic-challenges"><span class="secno">13.4.3. </span><span class="content">Cryptographic Challenges</span><a class="self-link" href="#sctn-cryptographic-challenges"></a></h4>
    <p>As a cryptographic protocol, Web Authentication is dependent upon randomized challenges
 to avoid replay attacks. Therefore, the values of both <code class="idl"><a data-link-type="idl" href="#dictdef-publickeycredentialcreationoptions" id="ref-for-dictdef-publickeycredentialcreationoptions①⓪">PublicKeyCredentialCreationOptions</a></code>.<code class="idl"><a data-link-type="idl" href="#dom-publickeycredentialcreationoptions-challenge" id="ref-for-dom-publickeycredentialcreationoptions-challenge③">challenge</a></code> and <code class="idl"><a data-link-type="idl" href="#dictdef-publickeycredentialrequestoptions" id="ref-for-dictdef-publickeycredentialrequestoptions①③">PublicKeyCredentialRequestOptions</a></code>.<code class="idl"><a data-link-type="idl" href="#dom-publickeycredentialrequestoptions-challenge" id="ref-for-dom-publickeycredentialrequestoptions-challenge④">challenge</a></code> MUST be randomly generated
-by <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party③⓪⑧">Relying Parties</a> in an environment they trust (e.g., on the server-side), and the
+by <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party③①⑤">Relying Parties</a> in an environment they trust (e.g., on the server-side), and the
 returned <code class="idl"><a data-link-type="idl" href="#dom-collectedclientdata-challenge" id="ref-for-dom-collectedclientdata-challenge⑧">challenge</a></code> value in the client’s
 response MUST match what was generated. This SHOULD be done in a fashion that does not rely
-upon a client’s behavior, e.g., the <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party③⓪⑨">Relying Party</a> SHOULD store the challenge temporarily
+upon a client’s behavior, e.g., the <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party③①⑥">Relying Party</a> SHOULD store the challenge temporarily
 until the operation is complete. Tolerating a mismatch will compromise the security
 of the protocol.</p>
    <p>In order to prevent replay attacks, the challenges MUST contain enough entropy to make guessing them infeasible. Challenges SHOULD
 therefore be at least 16 bytes long.</p>
    <h4 class="heading settled" data-level="13.4.4" id="sctn-attestation-limitations"><span class="secno">13.4.4. </span><span class="content">Attestation Limitations</span><a class="self-link" href="#sctn-attestation-limitations"></a></h4>
    <p><em>This section is not normative.</em></p>
-   <p>When <a href="#sctn-registering-a-new-credential">registering a new credential</a>, the <a data-link-type="dfn" href="#attestation-statement" id="ref-for-attestation-statement③⑨">attestation statement</a>, if present,
-may allow the <a data-link-type="dfn" href="#webauthn-relying-party" id="ref-for-webauthn-relying-party④⑦">WebAuthn Relying Party</a> to derive assurances about various <a data-link-type="dfn" href="#authenticator" id="ref-for-authenticator②⑥⓪">authenticator</a> qualities.
-For example, the <a data-link-type="dfn" href="#authenticator" id="ref-for-authenticator②⑥①">authenticator</a> model, or how it stores and protects <a data-link-type="dfn" href="#credential-private-key" id="ref-for-credential-private-key②②">credential private keys</a>.
-However, it is important to note that an <a data-link-type="dfn" href="#attestation-statement" id="ref-for-attestation-statement④⓪">attestation statement</a>, on its own,
-provides no means for a <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party③①⓪">Relying Party</a> to verify that an <a data-link-type="dfn" href="#attestation-object" id="ref-for-attestation-object①⑦">attestation object</a> was generated
-by the <a data-link-type="dfn" href="#authenticator" id="ref-for-authenticator②⑥②">authenticator</a> the user intended, and not by a <a data-link-type="dfn" href="https://tools.ietf.org/html/rfc4949#page-186" id="ref-for-page-186①">man-in-the-middle attacker</a>.
-For example, such an attacker could use malicious code injected into <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party③①①">Relying Party</a> script.
-The <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party③①②">Relying Party</a> must therefore rely on other means, e.g., TLS and related technologies,
+   <p>When <a href="#sctn-registering-a-new-credential">registering a new credential</a>, the <a data-link-type="dfn" href="#attestation-statement" id="ref-for-attestation-statement④⓪">attestation statement</a>, if present,
+may allow the <a data-link-type="dfn" href="#webauthn-relying-party" id="ref-for-webauthn-relying-party④⑦">WebAuthn Relying Party</a> to derive assurances about various <a data-link-type="dfn" href="#authenticator" id="ref-for-authenticator②⑤⑨">authenticator</a> qualities.
+For example, the <a data-link-type="dfn" href="#authenticator" id="ref-for-authenticator②⑥⓪">authenticator</a> model, or how it stores and protects <a data-link-type="dfn" href="#credential-private-key" id="ref-for-credential-private-key②②">credential private keys</a>.
+However, it is important to note that an <a data-link-type="dfn" href="#attestation-statement" id="ref-for-attestation-statement④①">attestation statement</a>, on its own,
+provides no means for a <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party③①⑦">Relying Party</a> to verify that an <a data-link-type="dfn" href="#attestation-object" id="ref-for-attestation-object①⑦">attestation object</a> was generated
+by the <a data-link-type="dfn" href="#authenticator" id="ref-for-authenticator②⑥①">authenticator</a> the user intended, and not by a <a data-link-type="dfn" href="https://tools.ietf.org/html/rfc4949#page-186" id="ref-for-page-186①">man-in-the-middle attacker</a>.
+For example, such an attacker could use malicious code injected into <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party③①⑧">Relying Party</a> script.
+The <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party③①⑨">Relying Party</a> must therefore rely on other means, e.g., TLS and related technologies,
 to protect the <a data-link-type="dfn" href="#attestation-object" id="ref-for-attestation-object①⑧">attestation object</a> from <a data-link-type="dfn" href="https://tools.ietf.org/html/rfc4949#page-186" id="ref-for-page-186②">man-in-the-middle attacks</a>.</p>
-   <p>Under the assumption that a <a data-link-type="dfn" href="#registration-ceremony" id="ref-for-registration-ceremony①⑤">registration ceremony</a> is completed securely, and that the <a data-link-type="dfn" href="#authenticator" id="ref-for-authenticator②⑥③">authenticator</a> maintains
+   <p>Under the assumption that a <a data-link-type="dfn" href="#registration-ceremony" id="ref-for-registration-ceremony①⑤">registration ceremony</a> is completed securely, and that the <a data-link-type="dfn" href="#authenticator" id="ref-for-authenticator②⑥②">authenticator</a> maintains
 confidentiality of the <a data-link-type="dfn" href="#credential-private-key" id="ref-for-credential-private-key②③">credential private key</a>, subsequent <a data-link-type="dfn" href="#authentication-ceremony" id="ref-for-authentication-ceremony②⑧">authentication ceremonies</a> using that <a data-link-type="dfn" href="#public-key-credential" id="ref-for-public-key-credential⑤⑧">public key
 credential</a> are resistant to tampering by <a data-link-type="dfn" href="https://tools.ietf.org/html/rfc4949#page-186" id="ref-for-page-186③">man-in-the-middle attacks</a>.</p>
-   <p>The discussion above holds for all <a data-link-type="dfn" href="#attestation-type" id="ref-for-attestation-type②④">attestation types</a>. In all cases it is possible for a <a data-link-type="dfn" href="https://tools.ietf.org/html/rfc4949#page-186" id="ref-for-page-186④">man-in-the-middle attacker</a> to replace the <code class="idl"><a data-link-type="idl" href="#publickeycredential" id="ref-for-publickeycredential②⑥">PublicKeyCredential</a></code> object, including the <a data-link-type="dfn" href="#attestation-statement" id="ref-for-attestation-statement④①">attestation statement</a> and the <a data-link-type="dfn" href="#credential-public-key" id="ref-for-credential-public-key③⑥">credential public key</a> to be registered, and subsequently tamper with future <a data-link-type="dfn" href="#authentication-assertion" id="ref-for-authentication-assertion①⑥">authentication assertions</a> <a data-link-type="dfn" href="#scope" id="ref-for-scope②③">scoped</a> for the
-same <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party③①③">Relying Party</a> and passing through the same attacker.</p>
-   <p>Such an attack would potentially be detectable; since the <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party③①④">Relying Party</a> has registered the attacker’s <a data-link-type="dfn" href="#credential-public-key" id="ref-for-credential-public-key③⑦">credential public key</a> rather
-than the user’s, the attacker must tamper with all subsequent <a data-link-type="dfn" href="#authentication-ceremony" id="ref-for-authentication-ceremony②⑨">authentication ceremonies</a> with that <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party③①⑤">Relying Party</a>: unscathed
+   <p>The discussion above holds for all <a data-link-type="dfn" href="#attestation-type" id="ref-for-attestation-type②④">attestation types</a>. In all cases it is possible for a <a data-link-type="dfn" href="https://tools.ietf.org/html/rfc4949#page-186" id="ref-for-page-186④">man-in-the-middle attacker</a> to replace the <code class="idl"><a data-link-type="idl" href="#publickeycredential" id="ref-for-publickeycredential②⑥">PublicKeyCredential</a></code> object, including the <a data-link-type="dfn" href="#attestation-statement" id="ref-for-attestation-statement④②">attestation statement</a> and the <a data-link-type="dfn" href="#credential-public-key" id="ref-for-credential-public-key③⑥">credential public key</a> to be registered, and subsequently tamper with future <a data-link-type="dfn" href="#authentication-assertion" id="ref-for-authentication-assertion①⑥">authentication assertions</a> <a data-link-type="dfn" href="#scope" id="ref-for-scope②③">scoped</a> for the
+same <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party③②⓪">Relying Party</a> and passing through the same attacker.</p>
+   <p>Such an attack would potentially be detectable; since the <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party③②①">Relying Party</a> has registered the attacker’s <a data-link-type="dfn" href="#credential-public-key" id="ref-for-credential-public-key③⑦">credential public key</a> rather
+than the user’s, the attacker must tamper with all subsequent <a data-link-type="dfn" href="#authentication-ceremony" id="ref-for-authentication-ceremony②⑨">authentication ceremonies</a> with that <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party③②②">Relying Party</a>: unscathed
 ceremonies will fail, potentially revealing the attack.</p>
-   <p><a data-link-type="dfn" href="#attestation-type" id="ref-for-attestation-type②⑤">Attestation types</a> other than <a data-link-type="dfn" href="#self-attestation" id="ref-for-self-attestation①⑨">Self Attestation</a> and <a data-link-type="dfn" href="#none" id="ref-for-none⑧">None</a> can increase the difficulty of such attacks, since <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party③①⑥">Relying Parties</a> can possibly display <a data-link-type="dfn" href="#authenticator" id="ref-for-authenticator②⑥④">authenticator</a> information, e.g., model designation, to the user. An attacker might therefore need to use
-a genuine <a data-link-type="dfn" href="#authenticator" id="ref-for-authenticator②⑥⑤">authenticator</a> of the same model as the user’s <a data-link-type="dfn" href="#authenticator" id="ref-for-authenticator②⑥⑥">authenticator</a>, or the user might notice that the <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party③①⑦">Relying Party</a> reports
-a different <a data-link-type="dfn" href="#authenticator" id="ref-for-authenticator②⑥⑦">authenticator</a> model than the user expects.</p>
+   <p><a data-link-type="dfn" href="#attestation-type" id="ref-for-attestation-type②⑤">Attestation types</a> other than <a data-link-type="dfn" href="#self-attestation" id="ref-for-self-attestation①⑨">Self Attestation</a> and <a data-link-type="dfn" href="#none" id="ref-for-none⑧">None</a> can increase the difficulty of such attacks, since <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party③②③">Relying Parties</a> can possibly display <a data-link-type="dfn" href="#authenticator" id="ref-for-authenticator②⑥③">authenticator</a> information, e.g., model designation, to the user. An attacker might therefore need to use
+a genuine <a data-link-type="dfn" href="#authenticator" id="ref-for-authenticator②⑥④">authenticator</a> of the same model as the user’s <a data-link-type="dfn" href="#authenticator" id="ref-for-authenticator②⑥⑤">authenticator</a>, or the user might notice that the <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party③②④">Relying Party</a> reports
+a different <a data-link-type="dfn" href="#authenticator" id="ref-for-authenticator②⑥⑥">authenticator</a> model than the user expects.</p>
    <p class="note" role="note"><span>Note:</span> All variants of <a data-link-type="dfn" href="https://tools.ietf.org/html/rfc4949#page-186" id="ref-for-page-186⑤">man-in-the-middle attacks</a> described above are more difficult for an attacker to mount
 than a <a data-link-type="dfn" href="https://tools.ietf.org/html/rfc4949#page-186" id="ref-for-page-186⑥">man-in-the-middle attack</a> against conventional password authentication.</p>
    <h4 class="heading settled" data-level="13.4.5" id="sctn-revoked-attestation-certificates"><span class="secno">13.4.5. </span><span class="content">Revoked Attestation Certificates</span><a class="self-link" href="#sctn-revoked-attestation-certificates"></a></h4>
-   <p>If <a data-link-type="dfn" href="#attestation-certificate" id="ref-for-attestation-certificate①②">attestation certificate</a> validation fails due to a revoked intermediate attestation CA certificate, and the <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party③①⑧">Relying Party</a>'s policy
-requires rejecting the registration/authentication request in these situations, then it is RECOMMENDED that the <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party③①⑨">Relying Party</a> also
+   <p>If <a data-link-type="dfn" href="#attestation-certificate" id="ref-for-attestation-certificate①②">attestation certificate</a> validation fails due to a revoked intermediate attestation CA certificate, and the <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party③②⑤">Relying Party</a>'s policy
+requires rejecting the registration/authentication request in these situations, then it is RECOMMENDED that the <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party③②⑥">Relying Party</a> also
 un-registers (or marks with a trust level equivalent to "<a data-link-type="dfn" href="#self-attestation" id="ref-for-self-attestation②⓪">self attestation</a>") <a data-link-type="dfn" href="#public-key-credential" id="ref-for-public-key-credential⑤⑨">public key credentials</a> that were registered
 after the CA compromise date using an <a data-link-type="dfn" href="#attestation-certificate" id="ref-for-attestation-certificate①③">attestation certificate</a> chaining up to the same intermediate CA. It is thus RECOMMENDED
-that <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party③②⓪">Relying Parties</a> remember intermediate attestation CA certificates during <a data-link-type="dfn" href="#registration" id="ref-for-registration②③">registration</a> in order to un-register
-related <a data-link-type="dfn" href="#public-key-credential" id="ref-for-public-key-credential⑥⓪">public key credentials</a> if the <a data-link-type="dfn" href="#registration" id="ref-for-registration②④">registration</a> was performed after revocation of such certificates.</p>
-   <p>See also the related security consideration for <a data-link-type="dfn" href="#authenticator" id="ref-for-authenticator②⑥⑧">authenticators</a> in <a href="#sctn-ca-compromise">§ 13.3.2 Attestation Certificate and Attestation Certificate CA Compromise</a>.</p>
+that <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party③②⑦">Relying Parties</a> remember intermediate attestation CA certificates during <a data-link-type="dfn" href="#registration" id="ref-for-registration②⑥">registration</a> in order to un-register
+related <a data-link-type="dfn" href="#public-key-credential" id="ref-for-public-key-credential⑥⓪">public key credentials</a> if the <a data-link-type="dfn" href="#registration" id="ref-for-registration②⑦">registration</a> was performed after revocation of such certificates.</p>
+   <p>See also the related security consideration for <a data-link-type="dfn" href="#authenticator" id="ref-for-authenticator②⑥⑦">authenticators</a> in <a href="#sctn-ca-compromise">§ 13.3.2 Attestation Certificate and Attestation Certificate CA Compromise</a>.</p>
    <h4 class="heading settled" data-level="13.4.6" id="sctn-credential-loss-key-mobility"><span class="secno">13.4.6. </span><span class="content">Credential Loss and Key Mobility</span><a class="self-link" href="#sctn-credential-loss-key-mobility"></a></h4>
-   <p>This specification defines no protocol for backing up <a data-link-type="dfn" href="#credential-private-key" id="ref-for-credential-private-key②④">credential private keys</a>, or for sharing them between <a data-link-type="dfn" href="#authenticator" id="ref-for-authenticator②⑥⑨">authenticators</a>.
-In general, it is expected that a <a data-link-type="dfn" href="#credential-private-key" id="ref-for-credential-private-key②⑤">credential private key</a> never leaves the <a data-link-type="dfn" href="#authenticator" id="ref-for-authenticator②⑦⓪">authenticator</a> that created it. Losing an <a data-link-type="dfn" href="#authenticator" id="ref-for-authenticator②⑦①">authenticator</a> therefore, in general, means losing all <a data-link-type="dfn" href="#public-key-credential" id="ref-for-public-key-credential⑥①">credentials</a> <a data-link-type="dfn" href="#bound-credential" id="ref-for-bound-credential①⑤">bound</a> to the
-lost <a data-link-type="dfn" href="#authenticator" id="ref-for-authenticator②⑦②">authenticator</a>, which could lock the user out of an account if the user has only one <a data-link-type="dfn" href="#public-key-credential" id="ref-for-public-key-credential⑥②">credential</a> registered with the <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party③②①">Relying Party</a>. Instead of backing up or sharing private keys, the Web Authentication API allows registering
+   <p>This specification defines no protocol for backing up <a data-link-type="dfn" href="#credential-private-key" id="ref-for-credential-private-key②④">credential private keys</a>, or for sharing them between <a data-link-type="dfn" href="#authenticator" id="ref-for-authenticator②⑥⑧">authenticators</a>.
+In general, it is expected that a <a data-link-type="dfn" href="#credential-private-key" id="ref-for-credential-private-key②⑤">credential private key</a> never leaves the <a data-link-type="dfn" href="#authenticator" id="ref-for-authenticator②⑥⑨">authenticator</a> that created it. Losing an <a data-link-type="dfn" href="#authenticator" id="ref-for-authenticator②⑦⓪">authenticator</a> therefore, in general, means losing all <a data-link-type="dfn" href="#public-key-credential" id="ref-for-public-key-credential⑥①">credentials</a> <a data-link-type="dfn" href="#bound-credential" id="ref-for-bound-credential①⑤">bound</a> to the
+lost <a data-link-type="dfn" href="#authenticator" id="ref-for-authenticator②⑦①">authenticator</a>, which could lock the user out of an account if the user has only one <a data-link-type="dfn" href="#public-key-credential" id="ref-for-public-key-credential⑥②">credential</a> registered with the <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party③②⑧">Relying Party</a>. Instead of backing up or sharing private keys, the Web Authentication API allows registering
 multiple <a data-link-type="dfn" href="#public-key-credential" id="ref-for-public-key-credential⑥③">credentials</a> for the same user. For example, a user might register <a data-link-type="dfn" href="#platform-credential" id="ref-for-platform-credential②">platform credentials</a> on
 frequently used <a data-link-type="dfn" href="#client-device" id="ref-for-client-device④④">client devices</a>, and one or more <a data-link-type="dfn" href="#roaming-credential" id="ref-for-roaming-credential①">roaming credentials</a> for use as backup and with new or rarely used <a data-link-type="dfn" href="#client-device" id="ref-for-client-device④⑤">client
 devices</a>.</p>
-   <p><a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party③②②">Relying Parties</a> SHOULD allow and encourage users to register multiple <a data-link-type="dfn" href="#public-key-credential" id="ref-for-public-key-credential⑥④">credentials</a> to the same <a data-link-type="dfn" href="#user-account" id="ref-for-user-account③①">user account</a>. <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party③②③">Relying Parties</a> SHOULD make use of the <code><code class="idl"><a data-link-type="idl" href="#dom-publickeycredentialcreationoptions-excludecredentials" id="ref-for-dom-publickeycredentialcreationoptions-excludecredentials②">excludeCredentials</a></code></code> and <code><code class="idl"><a data-link-type="idl" href="#dom-publickeycredentialcreationoptions-user" id="ref-for-dom-publickeycredentialcreationoptions-user⑦">user</a></code>.<code class="idl"><a data-link-type="idl" href="#dom-publickeycredentialuserentity-id" id="ref-for-dom-publickeycredentialuserentity-id⑨">id</a></code></code> options to ensure that these
-different <a data-link-type="dfn" href="#public-key-credential" id="ref-for-public-key-credential⑥⑤">credentials</a> are <a data-link-type="dfn" href="#bound-credential" id="ref-for-bound-credential①⑥">bound</a> to different <a data-link-type="dfn" href="#authenticator" id="ref-for-authenticator②⑦③">authenticators</a>.</p>
+   <p><a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party③②⑨">Relying Parties</a> SHOULD allow and encourage users to register multiple <a data-link-type="dfn" href="#public-key-credential" id="ref-for-public-key-credential⑥④">credentials</a> to the same <a data-link-type="dfn" href="#user-account" id="ref-for-user-account③⑤">user account</a>. <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party③③⓪">Relying Parties</a> SHOULD make use of the <code><code class="idl"><a data-link-type="idl" href="#dom-publickeycredentialcreationoptions-excludecredentials" id="ref-for-dom-publickeycredentialcreationoptions-excludecredentials②">excludeCredentials</a></code></code> and <code><code class="idl"><a data-link-type="idl" href="#dom-publickeycredentialcreationoptions-user" id="ref-for-dom-publickeycredentialcreationoptions-user⑦">user</a></code>.<code class="idl"><a data-link-type="idl" href="#dom-publickeycredentialuserentity-id" id="ref-for-dom-publickeycredentialuserentity-id⑨">id</a></code></code> options to ensure that these
+different <a data-link-type="dfn" href="#public-key-credential" id="ref-for-public-key-credential⑥⑤">credentials</a> are <a data-link-type="dfn" href="#bound-credential" id="ref-for-bound-credential①⑥">bound</a> to different <a data-link-type="dfn" href="#authenticator" id="ref-for-authenticator②⑦②">authenticators</a>.</p>
    <h4 class="heading settled" data-level="13.4.7" id="sctn-unprotected-account-detection"><span class="secno">13.4.7. </span><span class="content">Unprotected account detection</span><a class="self-link" href="#sctn-unprotected-account-detection"></a></h4>
    <p><em>This section is not normative.</em></p>
-   <p>This security consideration applies to <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party③②④">Relying Parties</a> that support <a data-link-type="dfn" href="#authentication-ceremony" id="ref-for-authentication-ceremony③⓪">authentication ceremonies</a> with a non-<a data-link-type="dfn" href="https://infra.spec.whatwg.org/#list-empty" id="ref-for-list-empty⑤">empty</a> <code class="idl"><a data-link-type="idl" href="#dom-publickeycredentialrequestoptions-allowcredentials" id="ref-for-dom-publickeycredentialrequestoptions-allowcredentials②④">allowCredentials</a></code> argument as the first authentication step.
+   <p>This security consideration applies to <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party③③①">Relying Parties</a> that support <a data-link-type="dfn" href="#authentication-ceremony" id="ref-for-authentication-ceremony③⓪">authentication ceremonies</a> with a non-<a data-link-type="dfn" href="https://infra.spec.whatwg.org/#list-empty" id="ref-for-list-empty⑤">empty</a> <code class="idl"><a data-link-type="idl" href="#dom-publickeycredentialrequestoptions-allowcredentials" id="ref-for-dom-publickeycredentialrequestoptions-allowcredentials②②">allowCredentials</a></code> argument as the first authentication step.
 For example, if using authentication with <a data-link-type="dfn" href="#server-side-credential" id="ref-for-server-side-credential①⑤">server-side credentials</a> as the first authentication step.</p>
-   <p>In this case the <code class="idl"><a data-link-type="idl" href="#dom-publickeycredentialrequestoptions-allowcredentials" id="ref-for-dom-publickeycredentialrequestoptions-allowcredentials②⑤">allowCredentials</a></code> argument risks leaking information
-about which <a data-link-type="dfn" href="#user-account" id="ref-for-user-account③②">user accounts</a> have WebAuthn credentials registered and which do not,
+   <p>In this case the <code class="idl"><a data-link-type="idl" href="#dom-publickeycredentialrequestoptions-allowcredentials" id="ref-for-dom-publickeycredentialrequestoptions-allowcredentials②③">allowCredentials</a></code> argument risks leaking information
+about which <a data-link-type="dfn" href="#user-account" id="ref-for-user-account③⑥">user accounts</a> have WebAuthn credentials registered and which do not,
 which may be a signal of account protection strength.
 For example, say an attacker can initiate an <a data-link-type="dfn" href="#authentication-ceremony" id="ref-for-authentication-ceremony③①">authentication ceremony</a> by providing only a username,
-and the <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party③②⑤">Relying Party</a> responds with a non-empty <code class="idl"><a data-link-type="idl" href="#dom-publickeycredentialrequestoptions-allowcredentials" id="ref-for-dom-publickeycredentialrequestoptions-allowcredentials②⑥">allowCredentials</a></code> for some <a data-link-type="dfn" href="#user-account" id="ref-for-user-account③③">user accounts</a>,
-and with failure or a password challenge for other <a data-link-type="dfn" href="#user-account" id="ref-for-user-account③④">user accounts</a>.
-The attacker can then conclude that the latter <a data-link-type="dfn" href="#user-account" id="ref-for-user-account③⑤">user accounts</a> likely do not require a WebAuthn <a data-link-type="dfn" href="#assertion" id="ref-for-assertion①③">assertion</a> for successful authentication,
+and the <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party③③②">Relying Party</a> responds with a non-empty <code class="idl"><a data-link-type="idl" href="#dom-publickeycredentialrequestoptions-allowcredentials" id="ref-for-dom-publickeycredentialrequestoptions-allowcredentials②④">allowCredentials</a></code> for some <a data-link-type="dfn" href="#user-account" id="ref-for-user-account③⑦">user accounts</a>,
+and with failure or a password challenge for other <a data-link-type="dfn" href="#user-account" id="ref-for-user-account③⑧">user accounts</a>.
+The attacker can then conclude that the latter <a data-link-type="dfn" href="#user-account" id="ref-for-user-account③⑨">user accounts</a> likely do not require a WebAuthn <a data-link-type="dfn" href="#assertion" id="ref-for-assertion①③">assertion</a> for successful authentication,
 and thus focus an attack on those likely weaker accounts.</p>
    <p>This issue is similar to the one described in <a href="#sctn-username-enumeration">§ 14.6.2 Username Enumeration</a> and <a href="#sctn-credential-id-privacy-leak">§ 14.6.3 Privacy leak via credential IDs</a>, and can be mitigated in similar ways.</p>
    <h4 class="heading settled" data-level="13.4.8" id="sctn-code-injection"><span class="secno">13.4.8. </span><span class="content">Code injection attacks</span><a class="self-link" href="#sctn-code-injection"></a></h4>
-   <p>Any malicious code executing on an <a data-link-type="dfn" href="#determines-the-set-of-origins-on-which-the-public-key-credential-may-be-exercised" id="ref-for-determines-the-set-of-origins-on-which-the-public-key-credential-may-be-exercised④">origin</a> within the <a data-link-type="dfn" href="#scope" id="ref-for-scope②④">scope</a> of a <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party③②⑥">Relying Party</a>'s <a data-link-type="dfn" href="#public-key-credential" id="ref-for-public-key-credential⑥⑥">public key credentials</a> has the potential to invalidate any and all security guarantees WebAuthn may provide. <a data-link-type="dfn" href="#webauthn-client" id="ref-for-webauthn-client⑧">WebAuthn Clients</a> only expose the WebAuthn API in <a data-link-type="dfn" href="https://html.spec.whatwg.org/multipage/webappapis.html#secure-context" id="ref-for-secure-context①">secure contexts</a>,
-which mitigates the most basic attacks but SHOULD be combined with additional precautions by <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party③②⑦">Relying Parties</a>.</p>
+   <p>Any malicious code executing on an <a data-link-type="dfn" href="#determines-the-set-of-origins-on-which-the-public-key-credential-may-be-exercised" id="ref-for-determines-the-set-of-origins-on-which-the-public-key-credential-may-be-exercised④">origin</a> within the <a data-link-type="dfn" href="#scope" id="ref-for-scope②④">scope</a> of a <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party③③③">Relying Party</a>'s <a data-link-type="dfn" href="#public-key-credential" id="ref-for-public-key-credential⑥⑥">public key credentials</a> has the potential to invalidate any and all security guarantees WebAuthn may provide. <a data-link-type="dfn" href="#webauthn-client" id="ref-for-webauthn-client⑧">WebAuthn Clients</a> only expose the WebAuthn API in <a data-link-type="dfn" href="https://html.spec.whatwg.org/multipage/webappapis.html#secure-context" id="ref-for-secure-context①">secure contexts</a>,
+which mitigates the most basic attacks but SHOULD be combined with additional precautions by <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party③③④">Relying Parties</a>.</p>
    <p>Code injection can happen in several ways;
 this section attempts to point out some likely scenarios and suggest suitable mitigations,
 but is not an exhaustive list.</p>
    <ul>
     <li data-md>
-     <p>Malicous code could be injected by a third-party script included by the <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party③②⑧">Relying Party</a>,
+     <p>Malicous code could be injected by a third-party script included by the <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party③③⑤">Relying Party</a>,
 either intentionally or due to a security vulnerability in the third party.</p>
-     <p>The <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party③②⑨">Relying Party</a> therefore SHOULD limit the amount of third-party script included on the <a data-link-type="dfn" href="#determines-the-set-of-origins-on-which-the-public-key-credential-may-be-exercised" id="ref-for-determines-the-set-of-origins-on-which-the-public-key-credential-may-be-exercised⑤">origins</a> within the <a data-link-type="dfn" href="#scope" id="ref-for-scope②⑤">scope</a> of its <a data-link-type="dfn" href="https://w3c.github.io/webappsec-credential-management/#concept-credential" id="ref-for-concept-credential②③">credentials</a>.</p>
-     <p>The <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party③③⓪">Relying Party</a> SHOULD use Content Security Policy <a data-link-type="biblio" href="#biblio-csp2">[CSP2]</a>,
+     <p>The <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party③③⑥">Relying Party</a> therefore SHOULD limit the amount of third-party script included on the <a data-link-type="dfn" href="#determines-the-set-of-origins-on-which-the-public-key-credential-may-be-exercised" id="ref-for-determines-the-set-of-origins-on-which-the-public-key-credential-may-be-exercised⑤">origins</a> within the <a data-link-type="dfn" href="#scope" id="ref-for-scope②⑤">scope</a> of its <a data-link-type="dfn" href="https://w3c.github.io/webappsec-credential-management/#concept-credential" id="ref-for-concept-credential②③">credentials</a>.</p>
+     <p>The <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party③③⑦">Relying Party</a> SHOULD use Content Security Policy <a data-link-type="biblio" href="#biblio-csp2">[CSP2]</a>,
 and/or other appropriate technologies available at the time, to limit what script can run on its <a data-link-type="dfn" href="#determines-the-set-of-origins-on-which-the-public-key-credential-may-be-exercised" id="ref-for-determines-the-set-of-origins-on-which-the-public-key-credential-may-be-exercised⑥">origins</a>.</p>
     <li data-md>
      <p>Malicious code could, by the credential <a data-link-type="dfn" href="#scope" id="ref-for-scope②⑥">scope</a> rules, be hosted on a subdomain of the <a data-link-type="dfn" href="#rp-id" id="ref-for-rp-id④⑨">RP ID</a>.
 For example, user-submitted code hosted on <code>usercontent.example.org</code> could exercise any <a data-link-type="dfn" href="https://w3c.github.io/webappsec-credential-management/#concept-credential" id="ref-for-concept-credential②④">credentials</a> <a data-link-type="dfn" href="#scope" id="ref-for-scope②⑦">scoped</a> to the <a data-link-type="dfn" href="#rp-id" id="ref-for-rp-id⑤⓪">RP ID</a> <code>example.org</code>.
-If the <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party③③①">Relying Party</a> allows a subdomain <code class="idl"><a data-link-type="idl" href="#dom-collectedclientdata-origin" id="ref-for-dom-collectedclientdata-origin⑨">origin</a></code> when <a href="#rp-op-verifying-assertion-step-origin">verifying the assertion</a>,
+If the <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party③③⑧">Relying Party</a> allows a subdomain <code class="idl"><a data-link-type="idl" href="#dom-collectedclientdata-origin" id="ref-for-dom-collectedclientdata-origin⑨">origin</a></code> when <a href="#rp-op-verifying-assertion-step-origin">verifying the assertion</a>,
 malicious users could use this to launch a <a data-link-type="dfn" href="https://tools.ietf.org/html/rfc4949#page-186" id="ref-for-page-186⑦">man-in-the-middle attack</a> to obtain valid <a data-link-type="dfn" href="#authentication-assertion" id="ref-for-authentication-assertion①⑦">authentication assertions</a> and impersonate the victims of the attack.</p>
-     <p>Therefore, the <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party③③②">Relying Party</a> by default SHOULD NOT allow a subdomain <code class="idl"><a data-link-type="idl" href="#dom-collectedclientdata-origin" id="ref-for-dom-collectedclientdata-origin①⓪">origin</a></code> when <a href="#rp-op-verifying-assertion-step-origin">verifying the assertion</a>.
-If the <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party③③③">Relying Party</a> needs to allow a subdomain <code class="idl"><a data-link-type="idl" href="#dom-collectedclientdata-origin" id="ref-for-dom-collectedclientdata-origin①①">origin</a></code>,
-then the <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party③③④">Relying Party</a> MUST NOT serve untrusted code on any allowed subdomain of <a data-link-type="dfn" href="#determines-the-set-of-origins-on-which-the-public-key-credential-may-be-exercised" id="ref-for-determines-the-set-of-origins-on-which-the-public-key-credential-may-be-exercised⑦">origins</a> within the <a data-link-type="dfn" href="#scope" id="ref-for-scope②⑧">scope</a> of its <a data-link-type="dfn" href="#public-key-credential" id="ref-for-public-key-credential⑥⑦">public key credentials</a>.</p>
+     <p>Therefore, the <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party③③⑨">Relying Party</a> by default SHOULD NOT allow a subdomain <code class="idl"><a data-link-type="idl" href="#dom-collectedclientdata-origin" id="ref-for-dom-collectedclientdata-origin①⓪">origin</a></code> when <a href="#rp-op-verifying-assertion-step-origin">verifying the assertion</a>.
+If the <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party③④⓪">Relying Party</a> needs to allow a subdomain <code class="idl"><a data-link-type="idl" href="#dom-collectedclientdata-origin" id="ref-for-dom-collectedclientdata-origin①①">origin</a></code>,
+then the <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party③④①">Relying Party</a> MUST NOT serve untrusted code on any allowed subdomain of <a data-link-type="dfn" href="#determines-the-set-of-origins-on-which-the-public-key-credential-may-be-exercised" id="ref-for-determines-the-set-of-origins-on-which-the-public-key-credential-may-be-exercised⑦">origins</a> within the <a data-link-type="dfn" href="#scope" id="ref-for-scope②⑧">scope</a> of its <a data-link-type="dfn" href="#public-key-credential" id="ref-for-public-key-credential⑥⑦">public key credentials</a>.</p>
    </ul>
    <h2 class="heading settled" data-level="14" id="sctn-privacy-considerations"><span class="secno">14. </span><span class="content">Privacy Considerations</span><a class="self-link" href="#sctn-privacy-considerations"></a></h2>
    <p>The privacy principles in <a data-link-type="biblio" href="#biblio-fido-privacy-principles">[FIDO-Privacy-Principles]</a> also apply to this specification.</p>
    <p>This section is divided by audience;
 general privacy considerations are direct subsections of this section,
-while privacy considerations specifically for <a data-link-type="dfn" href="#authenticator" id="ref-for-authenticator②⑦④">authenticator</a>, <a data-link-type="dfn" href="#client" id="ref-for-client⑨⑧">client</a> and <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party③③⑤">Relying Party</a> implementers
+while privacy considerations specifically for <a data-link-type="dfn" href="#authenticator" id="ref-for-authenticator②⑦③">authenticator</a>, <a data-link-type="dfn" href="#client" id="ref-for-client⑨⑦">client</a> and <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party③④②">Relying Party</a> implementers
 are grouped into respective subsections.</p>
    <h3 class="heading settled" data-level="14.1" id="sctn-privacy-attacks"><span class="secno">14.1. </span><span class="content">De-anonymization Prevention Measures</span><a class="self-link" href="#sctn-privacy-attacks"></a></h3>
    <p><em>This section is not normative.</em></p>
@@ -7418,74 +7496,74 @@ <h3 class="heading settled" data-level="14.1" id="sctn-privacy-attacks"><span cl
 form of global identity, the following kinds of potentially correlatable identifiers are used:</p>
    <ul>
     <li data-md>
-     <p>The user’s <a data-link-type="dfn" href="#credential-id" id="ref-for-credential-id④③">credential IDs</a> and <a data-link-type="dfn" href="#credential-public-key" id="ref-for-credential-public-key③⑧">credential public keys</a>.</p>
+     <p>The user’s <a data-link-type="dfn" href="#credential-id" id="ref-for-credential-id④④">credential IDs</a> and <a data-link-type="dfn" href="#credential-public-key" id="ref-for-credential-public-key③⑧">credential public keys</a>.</p>
      <p>These are registered by the <a data-link-type="dfn" href="#webauthn-relying-party" id="ref-for-webauthn-relying-party④⑧">WebAuthn Relying Party</a> and subsequently used by the user to prove possession of the corresponding <a data-link-type="dfn" href="#credential-private-key" id="ref-for-credential-private-key②⑥">credential
-private key</a>. They are also visible to the <a data-link-type="dfn" href="#client" id="ref-for-client⑨⑨">client</a> in the communication with the <a data-link-type="dfn" href="#authenticator" id="ref-for-authenticator②⑦⑤">authenticator</a>.</p>
+private key</a>. They are also visible to the <a data-link-type="dfn" href="#client" id="ref-for-client⑨⑧">client</a> in the communication with the <a data-link-type="dfn" href="#authenticator" id="ref-for-authenticator②⑦④">authenticator</a>.</p>
     <li data-md>
-     <p>The user’s identities specific to each <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party③③⑥">Relying Party</a>, e.g., usernames and <a data-link-type="dfn" href="#user-handle" id="ref-for-user-handle②①">user handles</a>.</p>
-     <p>These identities are obviously used by each <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party③③⑦">Relying Party</a> to identify a user in their system. They are also visible to the <a data-link-type="dfn" href="#client" id="ref-for-client①⓪⓪">client</a> in the communication with the <a data-link-type="dfn" href="#authenticator" id="ref-for-authenticator②⑦⑥">authenticator</a>.</p>
+     <p>The user’s identities specific to each <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party③④③">Relying Party</a>, e.g., usernames and <a data-link-type="dfn" href="#user-handle" id="ref-for-user-handle②②">user handles</a>.</p>
+     <p>These identities are obviously used by each <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party③④④">Relying Party</a> to identify a user in their system. They are also visible to the <a data-link-type="dfn" href="#client" id="ref-for-client⑨⑨">client</a> in the communication with the <a data-link-type="dfn" href="#authenticator" id="ref-for-authenticator②⑦⑤">authenticator</a>.</p>
     <li data-md>
      <p>The user’s biometric characteristic(s), e.g., fingerprints or facial recognition data <a data-link-type="biblio" href="#biblio-isobiometricvocabulary">[ISOBiometricVocabulary]</a>.</p>
-     <p>This is optionally used by the <a data-link-type="dfn" href="#authenticator" id="ref-for-authenticator②⑦⑦">authenticator</a> to perform <a data-link-type="dfn" href="#user-verification" id="ref-for-user-verification⑤⓪">user verification</a>. It is not revealed to the <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party③③⑧">Relying Party</a>, but in
-the case of <a data-link-type="dfn" href="#platform-authenticators" id="ref-for-platform-authenticators③⓪">platform authenticators</a>, it might be visible to the <a data-link-type="dfn" href="#client" id="ref-for-client①⓪①">client</a> depending on the implementation.</p>
+     <p>This is optionally used by the <a data-link-type="dfn" href="#authenticator" id="ref-for-authenticator②⑦⑥">authenticator</a> to perform <a data-link-type="dfn" href="#user-verification" id="ref-for-user-verification⑤⓪">user verification</a>. It is not revealed to the <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party③④⑤">Relying Party</a>, but in
+the case of <a data-link-type="dfn" href="#platform-authenticators" id="ref-for-platform-authenticators③⓪">platform authenticators</a>, it might be visible to the <a data-link-type="dfn" href="#client" id="ref-for-client①⓪⓪">client</a> depending on the implementation.</p>
     <li data-md>
-     <p>The models of the user’s <a data-link-type="dfn" href="#authenticator" id="ref-for-authenticator②⑦⑧">authenticators</a>, e.g., product names.</p>
-     <p>This is exposed in the <a data-link-type="dfn" href="#attestation-statement" id="ref-for-attestation-statement④②">attestation statement</a> provided to the <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party③③⑨">Relying Party</a> during <a data-link-type="dfn" href="#registration" id="ref-for-registration②⑤">registration</a>. It is also visible to the <a data-link-type="dfn" href="#client" id="ref-for-client①⓪②">client</a> in the communication with the <a data-link-type="dfn" href="#authenticator" id="ref-for-authenticator②⑦⑨">authenticator</a>.</p>
+     <p>The models of the user’s <a data-link-type="dfn" href="#authenticator" id="ref-for-authenticator②⑦⑦">authenticators</a>, e.g., product names.</p>
+     <p>This is exposed in the <a data-link-type="dfn" href="#attestation-statement" id="ref-for-attestation-statement④③">attestation statement</a> provided to the <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party③④⑥">Relying Party</a> during <a data-link-type="dfn" href="#registration" id="ref-for-registration②⑧">registration</a>. It is also visible to the <a data-link-type="dfn" href="#client" id="ref-for-client①⓪①">client</a> in the communication with the <a data-link-type="dfn" href="#authenticator" id="ref-for-authenticator②⑦⑧">authenticator</a>.</p>
     <li data-md>
-     <p>The identities of the user’s <a data-link-type="dfn" href="#authenticator" id="ref-for-authenticator②⑧⓪">authenticators</a>, e.g., serial numbers.</p>
-     <p>This is possibly used by the <a data-link-type="dfn" href="#client" id="ref-for-client①⓪③">client</a> to enable communication with the <a data-link-type="dfn" href="#authenticator" id="ref-for-authenticator②⑧①">authenticator</a>, but is not exposed to the <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party③④⓪">Relying Party</a>.</p>
+     <p>The identities of the user’s <a data-link-type="dfn" href="#authenticator" id="ref-for-authenticator②⑦⑨">authenticators</a>, e.g., serial numbers.</p>
+     <p>This is possibly used by the <a data-link-type="dfn" href="#client" id="ref-for-client①⓪②">client</a> to enable communication with the <a data-link-type="dfn" href="#authenticator" id="ref-for-authenticator②⑧⓪">authenticator</a>, but is not exposed to the <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party③④⑦">Relying Party</a>.</p>
    </ul>
-   <p>Some of the above information is necessarily shared with the <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party③④①">Relying Party</a>. The following sections describe the measures taken to
-prevent malicious <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party③④②">Relying Parties</a> from using it to discover a user’s personal identity.</p>
+   <p>Some of the above information is necessarily shared with the <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party③④⑧">Relying Party</a>. The following sections describe the measures taken to
+prevent malicious <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party③④⑨">Relying Parties</a> from using it to discover a user’s personal identity.</p>
    <h3 class="heading settled" data-level="14.2" id="sctn-non-correlatable-credentials"><span class="secno">14.2. </span><span class="content">Anonymous, Scoped, Non-correlatable <a data-link-type="dfn" href="#public-key-credential" id="ref-for-public-key-credential⑥⑧">Public Key Credentials</a></span><a class="self-link" href="#sctn-non-correlatable-credentials"></a></h3>
    <p><em>This section is not normative.</em></p>
-   <p>Although <a data-link-type="dfn" href="#credential-id" id="ref-for-credential-id④④">Credential IDs</a> and <a data-link-type="dfn" href="#credential-public-key" id="ref-for-credential-public-key③⑨">credential public keys</a> are necessarily shared with the <a data-link-type="dfn" href="#webauthn-relying-party" id="ref-for-webauthn-relying-party④⑨">WebAuthn Relying Party</a> to enable strong
-authentication, they are designed to be minimally identifying and not shared between <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party③④③">Relying Parties</a>.</p>
+   <p>Although <a data-link-type="dfn" href="#credential-id" id="ref-for-credential-id④⑤">Credential IDs</a> and <a data-link-type="dfn" href="#credential-public-key" id="ref-for-credential-public-key③⑨">credential public keys</a> are necessarily shared with the <a data-link-type="dfn" href="#webauthn-relying-party" id="ref-for-webauthn-relying-party④⑨">WebAuthn Relying Party</a> to enable strong
+authentication, they are designed to be minimally identifying and not shared between <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party③⑤⓪">Relying Parties</a>.</p>
    <ul>
     <li data-md>
-     <p><a data-link-type="dfn" href="#credential-id" id="ref-for-credential-id④⑤">Credential IDs</a> and <a data-link-type="dfn" href="#credential-public-key" id="ref-for-credential-public-key④⓪">credential public keys</a> are meaningless in isolation, as they only identify <a data-link-type="dfn" href="#credential-key-pair" id="ref-for-credential-key-pair⑤">credential key pairs</a> and not users directly.</p>
+     <p><a data-link-type="dfn" href="#credential-id" id="ref-for-credential-id④⑥">Credential IDs</a> and <a data-link-type="dfn" href="#credential-public-key" id="ref-for-credential-public-key④⓪">credential public keys</a> are meaningless in isolation, as they only identify <a data-link-type="dfn" href="#credential-key-pair" id="ref-for-credential-key-pair⑤">credential key pairs</a> and not users directly.</p>
     <li data-md>
-     <p>Each <a data-link-type="dfn" href="#public-key-credential" id="ref-for-public-key-credential⑥⑨">public key credential</a> is strictly <a data-link-type="dfn" href="#scope" id="ref-for-scope②⑨">scoped</a> to a specific <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party③④④">Relying Party</a>, and the <a data-link-type="dfn" href="#client" id="ref-for-client①⓪④">client</a> ensures that its existence is not
-revealed to other <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party③④⑤">Relying Parties</a>. A malicious <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party③④⑥">Relying Party</a> thus cannot ask the <a data-link-type="dfn" href="#client" id="ref-for-client①⓪⑤">client</a> to reveal a user’s other identities.</p>
+     <p>Each <a data-link-type="dfn" href="#public-key-credential" id="ref-for-public-key-credential⑥⑨">public key credential</a> is strictly <a data-link-type="dfn" href="#scope" id="ref-for-scope②⑨">scoped</a> to a specific <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party③⑤①">Relying Party</a>, and the <a data-link-type="dfn" href="#client" id="ref-for-client①⓪③">client</a> ensures that its existence is not
+revealed to other <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party③⑤②">Relying Parties</a>. A malicious <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party③⑤③">Relying Party</a> thus cannot ask the <a data-link-type="dfn" href="#client" id="ref-for-client①⓪④">client</a> to reveal a user’s other identities.</p>
     <li data-md>
-     <p>The <a data-link-type="dfn" href="#client" id="ref-for-client①⓪⑥">client</a> also ensures that the existence of a <a data-link-type="dfn" href="#public-key-credential" id="ref-for-public-key-credential⑦⓪">public key credential</a> is not revealed to the <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party③④⑦">Relying Party</a> without <a data-link-type="dfn" href="#user-consent" id="ref-for-user-consent②⑥">user
-consent</a>. This is detailed further in <a href="#sctn-make-credential-privacy">§ 14.5.1 Registration Ceremony Privacy</a> and <a href="#sctn-assertion-privacy">§ 14.5.2 Authentication Ceremony Privacy</a>. A malicious <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party③④⑧">Relying Party</a> thus cannot silently identify a user, even if the user has a <a data-link-type="dfn" href="#public-key-credential" id="ref-for-public-key-credential⑦①">public key credential</a> registered and available.</p>
+     <p>The <a data-link-type="dfn" href="#client" id="ref-for-client①⓪⑤">client</a> also ensures that the existence of a <a data-link-type="dfn" href="#public-key-credential" id="ref-for-public-key-credential⑦⓪">public key credential</a> is not revealed to the <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party③⑤④">Relying Party</a> without <a data-link-type="dfn" href="#user-consent" id="ref-for-user-consent②⑥">user
+consent</a>. This is detailed further in <a href="#sctn-make-credential-privacy">§ 14.5.1 Registration Ceremony Privacy</a> and <a href="#sctn-assertion-privacy">§ 14.5.2 Authentication Ceremony Privacy</a>. A malicious <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party③⑤⑤">Relying Party</a> thus cannot silently identify a user, even if the user has a <a data-link-type="dfn" href="#public-key-credential" id="ref-for-public-key-credential⑦①">public key credential</a> registered and available.</p>
     <li data-md>
-     <p><a data-link-type="dfn" href="#authenticator" id="ref-for-authenticator②⑧②">Authenticators</a> ensure that the <a data-link-type="dfn" href="#credential-id" id="ref-for-credential-id④⑥">credential IDs</a> and <a data-link-type="dfn" href="#credential-public-key" id="ref-for-credential-public-key④①">credential public keys</a> of different <a data-link-type="dfn" href="#public-key-credential" id="ref-for-public-key-credential⑦②">public key credentials</a> are
-not correlatable as belonging to the same user. A pair of malicious <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party③④⑨">Relying Parties</a> thus cannot correlate users between their
+     <p><a data-link-type="dfn" href="#authenticator" id="ref-for-authenticator②⑧①">Authenticators</a> ensure that the <a data-link-type="dfn" href="#credential-id" id="ref-for-credential-id④⑦">credential IDs</a> and <a data-link-type="dfn" href="#credential-public-key" id="ref-for-credential-public-key④①">credential public keys</a> of different <a data-link-type="dfn" href="#public-key-credential" id="ref-for-public-key-credential⑦②">public key credentials</a> are
+not correlatable as belonging to the same user. A pair of malicious <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party③⑤⑥">Relying Parties</a> thus cannot correlate users between their
 systems without additional information, e.g., a willfully reused username or e-mail address.</p>
     <li data-md>
-     <p><a data-link-type="dfn" href="#authenticator" id="ref-for-authenticator②⑧③">Authenticators</a> ensure that their <a data-link-type="dfn" href="#attestation-certificate" id="ref-for-attestation-certificate①④">attestation certificates</a> are not unique enough to identify a single <a data-link-type="dfn" href="#authenticator" id="ref-for-authenticator②⑧④">authenticator</a> or a small group of <a data-link-type="dfn" href="#authenticator" id="ref-for-authenticator②⑧⑤">authenticators</a>. This is detailed further in <a href="#sctn-attestation-privacy">§ 14.4.1 Attestation Privacy</a>. A pair of malicious <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party③⑤⓪">Relying Parties</a> thus cannot correlate users between their systems by tracking individual <a data-link-type="dfn" href="#authenticator" id="ref-for-authenticator②⑧⑥">authenticators</a>.</p>
+     <p><a data-link-type="dfn" href="#authenticator" id="ref-for-authenticator②⑧②">Authenticators</a> ensure that their <a data-link-type="dfn" href="#attestation-certificate" id="ref-for-attestation-certificate①④">attestation certificates</a> are not unique enough to identify a single <a data-link-type="dfn" href="#authenticator" id="ref-for-authenticator②⑧③">authenticator</a> or a small group of <a data-link-type="dfn" href="#authenticator" id="ref-for-authenticator②⑧④">authenticators</a>. This is detailed further in <a href="#sctn-attestation-privacy">§ 14.4.1 Attestation Privacy</a>. A pair of malicious <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party③⑤⑦">Relying Parties</a> thus cannot correlate users between their systems by tracking individual <a data-link-type="dfn" href="#authenticator" id="ref-for-authenticator②⑧⑤">authenticators</a>.</p>
    </ul>
-   <p>Additionally, a <a data-link-type="dfn" href="#client-side-discoverable-public-key-credential-source" id="ref-for-client-side-discoverable-public-key-credential-source⑧">client-side discoverable public key credential source</a> can optionally include a <a data-link-type="dfn" href="#user-handle" id="ref-for-user-handle②②">user
-handle</a> specified by the <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party③⑤①">Relying Party</a>. The <a data-link-type="dfn" href="#public-key-credential" id="ref-for-public-key-credential⑦③">credential</a> can then be used to both identify and <a data-link-type="dfn" href="#authentication" id="ref-for-authentication①⑥">authenticate</a> the user.
-This means that a privacy-conscious <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party③⑤②">Relying Party</a> can allow creation of a <a data-link-type="dfn" href="#user-account" id="ref-for-user-account③⑥">user account</a> without a traditional username,
-further improving non-correlatability between <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party③⑤③">Relying Parties</a>.</p>
+   <p>Additionally, a <a data-link-type="dfn" href="#client-side-discoverable-public-key-credential-source" id="ref-for-client-side-discoverable-public-key-credential-source⑧">client-side discoverable public key credential source</a> can optionally include a <a data-link-type="dfn" href="#user-handle" id="ref-for-user-handle②③">user
+handle</a> specified by the <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party③⑤⑧">Relying Party</a>. The <a data-link-type="dfn" href="#public-key-credential" id="ref-for-public-key-credential⑦③">credential</a> can then be used to both identify and <a data-link-type="dfn" href="#authentication" id="ref-for-authentication①⑥">authenticate</a> the user.
+This means that a privacy-conscious <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party③⑤⑨">Relying Party</a> can allow creation of a <a data-link-type="dfn" href="#user-account" id="ref-for-user-account④⓪">user account</a> without a traditional username,
+further improving non-correlatability between <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party③⑥⓪">Relying Parties</a>.</p>
    <h3 class="heading settled" data-level="14.3" id="sctn-biometric-privacy"><span class="secno">14.3. </span><span class="content">Authenticator-local <a data-link-type="dfn" href="#biometric-recognition" id="ref-for-biometric-recognition④">Biometric Recognition</a></span><a class="self-link" href="#sctn-biometric-privacy"></a></h3>
-   <p><a data-link-type="dfn" href="#biometric-authenticator" id="ref-for-biometric-authenticator①">Biometric authenticators</a> perform the <a data-link-type="dfn" href="#biometric-recognition" id="ref-for-biometric-recognition⑤">biometric recognition</a> internally in the <a data-link-type="dfn" href="#authenticator" id="ref-for-authenticator②⑧⑦">authenticator</a> - though for <a data-link-type="dfn" href="#platform-authenticators" id="ref-for-platform-authenticators③①">platform
-authenticators</a> the biometric data might also be visible to the <a data-link-type="dfn" href="#client" id="ref-for-client①⓪⑦">client</a>, depending on the implementation. Biometric data is
-not revealed to the <a data-link-type="dfn" href="#webauthn-relying-party" id="ref-for-webauthn-relying-party⑤⓪">WebAuthn Relying Party</a>; it is used only locally to perform <a data-link-type="dfn" href="#user-verification" id="ref-for-user-verification⑤①">user verification</a> authorizing the creation and <a data-link-type="dfn" href="#registration" id="ref-for-registration②⑥">registration</a> of, or <a data-link-type="dfn" href="#authentication" id="ref-for-authentication①⑦">authentication</a> using, a <a data-link-type="dfn" href="#public-key-credential" id="ref-for-public-key-credential⑦④">public key credential</a>. A malicious <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party③⑤④">Relying Party</a> therefore cannot discover the
-user’s personal identity via biometric data, and a security breach at a <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party③⑤⑤">Relying Party</a> cannot expose biometric data for an attacker to
-use for forging logins at other <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party③⑤⑥">Relying Parties</a>.</p>
-   <p>In the case where a <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party③⑤⑦">Relying Party</a> requires <a data-link-type="dfn" href="#biometric-recognition" id="ref-for-biometric-recognition⑥">biometric recognition</a>, this is performed locally by the <a data-link-type="dfn" href="#biometric-authenticator" id="ref-for-biometric-authenticator②">biometric authenticator</a> perfoming <a data-link-type="dfn" href="#user-verification" id="ref-for-user-verification⑤②">user verification</a> and then signaling the result by setting the <a data-link-type="dfn" href="#authdata-flags-uv" id="ref-for-authdata-flags-uv①⓪">UV</a> <a data-link-type="dfn" href="#authdata-flags" id="ref-for-authdata-flags③⑥">flag</a> in the signed <a data-link-type="dfn" href="#assertion" id="ref-for-assertion①④">assertion</a> response,
-instead of revealing the biometric data itself to the <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party③⑤⑧">Relying Party</a>.</p>
-   <h3 class="heading settled" data-level="14.4" id="sctn-privacy-considerations-authenticator"><span class="secno">14.4. </span><span class="content">Privacy considerations for <a data-link-type="dfn" href="#authenticator" id="ref-for-authenticator②⑧⑧">authenticators</a></span><a class="self-link" href="#sctn-privacy-considerations-authenticator"></a></h3>
+   <p><a data-link-type="dfn" href="#biometric-authenticator" id="ref-for-biometric-authenticator①">Biometric authenticators</a> perform the <a data-link-type="dfn" href="#biometric-recognition" id="ref-for-biometric-recognition⑤">biometric recognition</a> internally in the <a data-link-type="dfn" href="#authenticator" id="ref-for-authenticator②⑧⑥">authenticator</a> - though for <a data-link-type="dfn" href="#platform-authenticators" id="ref-for-platform-authenticators③①">platform
+authenticators</a> the biometric data might also be visible to the <a data-link-type="dfn" href="#client" id="ref-for-client①⓪⑥">client</a>, depending on the implementation. Biometric data is
+not revealed to the <a data-link-type="dfn" href="#webauthn-relying-party" id="ref-for-webauthn-relying-party⑤⓪">WebAuthn Relying Party</a>; it is used only locally to perform <a data-link-type="dfn" href="#user-verification" id="ref-for-user-verification⑤①">user verification</a> authorizing the creation and <a data-link-type="dfn" href="#registration" id="ref-for-registration②⑨">registration</a> of, or <a data-link-type="dfn" href="#authentication" id="ref-for-authentication①⑦">authentication</a> using, a <a data-link-type="dfn" href="#public-key-credential" id="ref-for-public-key-credential⑦④">public key credential</a>. A malicious <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party③⑥①">Relying Party</a> therefore cannot discover the
+user’s personal identity via biometric data, and a security breach at a <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party③⑥②">Relying Party</a> cannot expose biometric data for an attacker to
+use for forging logins at other <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party③⑥③">Relying Parties</a>.</p>
+   <p>In the case where a <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party③⑥④">Relying Party</a> requires <a data-link-type="dfn" href="#biometric-recognition" id="ref-for-biometric-recognition⑥">biometric recognition</a>, this is performed locally by the <a data-link-type="dfn" href="#biometric-authenticator" id="ref-for-biometric-authenticator②">biometric authenticator</a> perfoming <a data-link-type="dfn" href="#user-verification" id="ref-for-user-verification⑤②">user verification</a> and then signaling the result by setting the <a data-link-type="dfn" href="#authdata-flags-uv" id="ref-for-authdata-flags-uv①⓪">UV</a> <a data-link-type="dfn" href="#authdata-flags" id="ref-for-authdata-flags④①">flag</a> in the signed <a data-link-type="dfn" href="#assertion" id="ref-for-assertion①④">assertion</a> response,
+instead of revealing the biometric data itself to the <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party③⑥⑤">Relying Party</a>.</p>
+   <h3 class="heading settled" data-level="14.4" id="sctn-privacy-considerations-authenticator"><span class="secno">14.4. </span><span class="content">Privacy considerations for <a data-link-type="dfn" href="#authenticator" id="ref-for-authenticator②⑧⑦">authenticators</a></span><a class="self-link" href="#sctn-privacy-considerations-authenticator"></a></h3>
    <h4 class="heading settled" data-level="14.4.1" id="sctn-attestation-privacy"><span class="secno">14.4.1. </span><span class="content">Attestation Privacy</span><a class="self-link" href="#sctn-attestation-privacy"></a></h4>
    <p><a data-link-type="dfn" href="#attestation-certificate" id="ref-for-attestation-certificate①⑤">Attestation certificates</a> and <a data-link-type="dfn" href="#attestation-key-pair" id="ref-for-attestation-key-pair⑦">attestation key pairs</a> can be used to track users
 or link various online identities of the same user together.
 This can be mitigated in several ways, including:</p>
    <ul>
     <li data-md>
-     <p>A <a data-link-type="dfn" href="#webauthn-authenticator" id="ref-for-webauthn-authenticator①⑥">WebAuthn Authenticator</a> manufacturer may choose to ship <a data-link-type="dfn" href="#authenticator" id="ref-for-authenticator②⑧⑨">authenticators</a> in batches
-where <a data-link-type="dfn" href="#authenticator" id="ref-for-authenticator②⑨⓪">authenticators</a> in a batch share the same <a data-link-type="dfn" href="#attestation-certificate" id="ref-for-attestation-certificate①⑥">attestation certificate</a> (called <a data-link-type="dfn" href="#basic-attestation" id="ref-for-basic-attestation①">Basic Attestation</a> or <a data-link-type="dfn" href="#batch-attestation" id="ref-for-batch-attestation">batch attestation</a>).
+     <p>A <a data-link-type="dfn" href="#webauthn-authenticator" id="ref-for-webauthn-authenticator①⑥">WebAuthn Authenticator</a> manufacturer may choose to ship <a data-link-type="dfn" href="#authenticator" id="ref-for-authenticator②⑧⑧">authenticators</a> in batches
+where <a data-link-type="dfn" href="#authenticator" id="ref-for-authenticator②⑧⑨">authenticators</a> in a batch share the same <a data-link-type="dfn" href="#attestation-certificate" id="ref-for-attestation-certificate①⑥">attestation certificate</a> (called <a data-link-type="dfn" href="#basic-attestation" id="ref-for-basic-attestation①">Basic Attestation</a> or <a data-link-type="dfn" href="#batch-attestation" id="ref-for-batch-attestation">batch attestation</a>).
 This will anonymize the user at the risk of not being able to revoke a particular <a data-link-type="dfn" href="#attestation-certificate" id="ref-for-attestation-certificate①⑦">attestation certificate</a> if its <a data-link-type="dfn" href="#attestation-private-key" id="ref-for-attestation-private-key⑥">private key</a> is compromised.
-The <a data-link-type="dfn" href="#authenticator" id="ref-for-authenticator②⑨①">authenticator</a> manufacturer SHOULD then ensure that such batches are large enough to provide meaningful anonymization,
+The <a data-link-type="dfn" href="#authenticator" id="ref-for-authenticator②⑨⓪">authenticator</a> manufacturer SHOULD then ensure that such batches are large enough to provide meaningful anonymization,
 while also minimizing the batch size in order to limit the number of affected users
 in case an <a data-link-type="dfn" href="#attestation-private-key" id="ref-for-attestation-private-key⑦">attestation private key</a> is compromised.</p>
-     <p><a data-link-type="biblio" href="#biblio-uafprotocol">[UAFProtocol]</a> requires that at least 100,000 <a data-link-type="dfn" href="#authenticator" id="ref-for-authenticator②⑨②">authenticator</a> devices share the same <a data-link-type="dfn" href="#attestation-certificate" id="ref-for-attestation-certificate①⑧">attestation certificate</a> in order to produce
+     <p><a data-link-type="biblio" href="#biblio-uafprotocol">[UAFProtocol]</a> requires that at least 100,000 <a data-link-type="dfn" href="#authenticator" id="ref-for-authenticator②⑨①">authenticator</a> devices share the same <a data-link-type="dfn" href="#attestation-certificate" id="ref-for-attestation-certificate①⑧">attestation certificate</a> in order to produce
 sufficiently large groups. This may serve as guidance about suitable batch sizes.</p>
     <li data-md>
-     <p>A <a data-link-type="dfn" href="#webauthn-authenticator" id="ref-for-webauthn-authenticator①⑦">WebAuthn Authenticator</a> may be capable of dynamically generating different <a data-link-type="dfn" href="#attestation-key-pair" id="ref-for-attestation-key-pair⑧">attestation key pairs</a> (and requesting related <a data-link-type="dfn" href="#attestation-certificate" id="ref-for-attestation-certificate①⑨">certificates</a>) per-<a data-link-type="dfn" href="https://w3c.github.io/webappsec-credential-management/#concept-credential" id="ref-for-concept-credential②⑤">credential</a> as described in the <a data-link-type="dfn" href="#anonymization-ca" id="ref-for-anonymization-ca⑥">Anonymization CA</a> approach. For example, an <a data-link-type="dfn" href="#authenticator" id="ref-for-authenticator②⑨③">authenticator</a> can ship with a
+     <p>A <a data-link-type="dfn" href="#webauthn-authenticator" id="ref-for-webauthn-authenticator①⑦">WebAuthn Authenticator</a> may be capable of dynamically generating different <a data-link-type="dfn" href="#attestation-key-pair" id="ref-for-attestation-key-pair⑧">attestation key pairs</a> (and requesting related <a data-link-type="dfn" href="#attestation-certificate" id="ref-for-attestation-certificate①⑨">certificates</a>) per-<a data-link-type="dfn" href="https://w3c.github.io/webappsec-credential-management/#concept-credential" id="ref-for-concept-credential②⑤">credential</a> as described in the <a data-link-type="dfn" href="#anonymization-ca" id="ref-for-anonymization-ca⑥">Anonymization CA</a> approach. For example, an <a data-link-type="dfn" href="#authenticator" id="ref-for-authenticator②⑨②">authenticator</a> can ship with a
 main <a data-link-type="dfn" href="#attestation-private-key" id="ref-for-attestation-private-key⑧">attestation private key</a> (and <a data-link-type="dfn" href="#attestation-certificate" id="ref-for-attestation-certificate②⓪">certificate</a>),
 and combined with a cloud-operated <a data-link-type="dfn" href="#anonymization-ca" id="ref-for-anonymization-ca⑦">Anonymization CA</a>,
 can dynamically generate per-<a data-link-type="dfn" href="https://w3c.github.io/webappsec-credential-management/#concept-credential" id="ref-for-concept-credential②⑥">credential</a> <a data-link-type="dfn" href="#attestation-key-pair" id="ref-for-attestation-key-pair⑨">attestation key pairs</a> and <a data-link-type="dfn" href="#attestation-certificate" id="ref-for-attestation-certificate②①">attestation certificates</a>.</p>
@@ -7495,81 +7573,81 @@ <h4 class="heading settled" data-level="14.4.1" id="sctn-attestation-privacy"><s
     confusion in the specific context of this specification.</p>
    </ul>
    <h4 class="heading settled" data-level="14.4.2" id="sctn-pii-privacy"><span class="secno">14.4.2. </span><span class="content">Privacy of personally identifying information Stored in Authenticators</span><a class="self-link" href="#sctn-pii-privacy"></a></h4>
-   <p><a data-link-type="dfn" href="#authenticator" id="ref-for-authenticator②⑨④">Authenticators</a> MAY provide additional information to <a data-link-type="dfn" href="#client" id="ref-for-client①⓪⑧">clients</a> outside what’s defined by this specification, e.g.,
-to enable the <a data-link-type="dfn" href="#client" id="ref-for-client①⓪⑨">client</a> to provide a rich UI with which the user can pick which <a data-link-type="dfn" href="https://w3c.github.io/webappsec-credential-management/#concept-credential" id="ref-for-concept-credential②⑦">credential</a> to use for an <a data-link-type="dfn" href="#authentication-ceremony" id="ref-for-authentication-ceremony③②">authentication
-ceremony</a>. If an <a data-link-type="dfn" href="#authenticator" id="ref-for-authenticator②⑨⑤">authenticator</a> chooses to do so, it SHOULD NOT expose personally identifying information unless successful <a data-link-type="dfn" href="#user-verification" id="ref-for-user-verification⑤③">user verification</a> has been
-performed. If the <a data-link-type="dfn" href="#authenticator" id="ref-for-authenticator②⑨⑥">authenticator</a> supports <a data-link-type="dfn" href="#user-verification" id="ref-for-user-verification⑤④">user verification</a> with more than one concurrently enrolled user, the <a data-link-type="dfn" href="#authenticator" id="ref-for-authenticator②⑨⑦">authenticator</a> SHOULD NOT expose personally identifying information of users other than the currently <a data-link-type="dfn" href="#concept-user-verified" id="ref-for-concept-user-verified④">verified</a> user. Consequently, an <a data-link-type="dfn" href="#authenticator" id="ref-for-authenticator②⑨⑧">authenticator</a> that is not capable of <a data-link-type="dfn" href="#user-verification" id="ref-for-user-verification⑤⑤">user verification</a> SHOULD NOT store personally identifying information.</p>
-   <p>For the purposes of this discussion, the <a data-link-type="dfn" href="#user-handle" id="ref-for-user-handle②③">user handle</a> conveyed as the <code class="idl"><a data-link-type="idl" href="#dom-publickeycredentialuserentity-id" id="ref-for-dom-publickeycredentialuserentity-id①⓪">id</a></code> member of <code class="idl"><a data-link-type="idl" href="#dictdef-publickeycredentialuserentity" id="ref-for-dictdef-publickeycredentialuserentity⑦">PublicKeyCredentialUserEntity</a></code> is not considered personally identifying information; see <a href="#sctn-user-handle-privacy">§ 14.6.1 User Handle Contents</a>.</p>
-   <p>These recommendations serve to prevent an adversary with physical access to an <a data-link-type="dfn" href="#authenticator" id="ref-for-authenticator②⑨⑨">authenticator</a> from extracting personally identifying information about the <a data-link-type="dfn" href="#authenticator" id="ref-for-authenticator③⓪⓪">authenticator</a>'s enrolled user(s).</p>
-   <h3 class="heading settled" data-level="14.5" id="sctn-privacy-considerations-client"><span class="secno">14.5. </span><span class="content">Privacy considerations for <a data-link-type="dfn" href="#client" id="ref-for-client①①⓪">clients</a></span><a class="self-link" href="#sctn-privacy-considerations-client"></a></h3>
+   <p><a data-link-type="dfn" href="#authenticator" id="ref-for-authenticator②⑨③">Authenticators</a> MAY provide additional information to <a data-link-type="dfn" href="#client" id="ref-for-client①⓪⑦">clients</a> outside what’s defined by this specification, e.g.,
+to enable the <a data-link-type="dfn" href="#client" id="ref-for-client①⓪⑧">client</a> to provide a rich UI with which the user can pick which <a data-link-type="dfn" href="https://w3c.github.io/webappsec-credential-management/#concept-credential" id="ref-for-concept-credential②⑦">credential</a> to use for an <a data-link-type="dfn" href="#authentication-ceremony" id="ref-for-authentication-ceremony③②">authentication
+ceremony</a>. If an <a data-link-type="dfn" href="#authenticator" id="ref-for-authenticator②⑨④">authenticator</a> chooses to do so, it SHOULD NOT expose personally identifying information unless successful <a data-link-type="dfn" href="#user-verification" id="ref-for-user-verification⑤③">user verification</a> has been
+performed. If the <a data-link-type="dfn" href="#authenticator" id="ref-for-authenticator②⑨⑤">authenticator</a> supports <a data-link-type="dfn" href="#user-verification" id="ref-for-user-verification⑤④">user verification</a> with more than one concurrently enrolled user, the <a data-link-type="dfn" href="#authenticator" id="ref-for-authenticator②⑨⑥">authenticator</a> SHOULD NOT expose personally identifying information of users other than the currently <a data-link-type="dfn" href="#concept-user-verified" id="ref-for-concept-user-verified④">verified</a> user. Consequently, an <a data-link-type="dfn" href="#authenticator" id="ref-for-authenticator②⑨⑦">authenticator</a> that is not capable of <a data-link-type="dfn" href="#user-verification" id="ref-for-user-verification⑤⑤">user verification</a> SHOULD NOT store personally identifying information.</p>
+   <p>For the purposes of this discussion, the <a data-link-type="dfn" href="#user-handle" id="ref-for-user-handle②④">user handle</a> conveyed as the <code class="idl"><a data-link-type="idl" href="#dom-publickeycredentialuserentity-id" id="ref-for-dom-publickeycredentialuserentity-id①⓪">id</a></code> member of <code class="idl"><a data-link-type="idl" href="#dictdef-publickeycredentialuserentity" id="ref-for-dictdef-publickeycredentialuserentity⑦">PublicKeyCredentialUserEntity</a></code> is not considered personally identifying information; see <a href="#sctn-user-handle-privacy">§ 14.6.1 User Handle Contents</a>.</p>
+   <p>These recommendations serve to prevent an adversary with physical access to an <a data-link-type="dfn" href="#authenticator" id="ref-for-authenticator②⑨⑧">authenticator</a> from extracting personally identifying information about the <a data-link-type="dfn" href="#authenticator" id="ref-for-authenticator②⑨⑨">authenticator</a>'s enrolled user(s).</p>
+   <h3 class="heading settled" data-level="14.5" id="sctn-privacy-considerations-client"><span class="secno">14.5. </span><span class="content">Privacy considerations for <a data-link-type="dfn" href="#client" id="ref-for-client①⓪⑨">clients</a></span><a class="self-link" href="#sctn-privacy-considerations-client"></a></h3>
    <h4 class="heading settled" data-level="14.5.1" id="sctn-make-credential-privacy"><span class="secno">14.5.1. </span><span class="content">Registration Ceremony Privacy</span><a class="self-link" href="#sctn-make-credential-privacy"></a></h4>
    <p>In order to protect users from being identified without <a data-link-type="dfn" href="#user-consent" id="ref-for-user-consent②⑦">consent</a>, implementations of the <code class="idl"><a data-link-type="idl" href="#dom-publickeycredential-create-slot" id="ref-for-dom-publickeycredential-create-slot①①">[[Create]](origin, options, sameOriginWithAncestors)</a></code> method need to take care to not leak information that
-could enable a malicious <a data-link-type="dfn" href="#webauthn-relying-party" id="ref-for-webauthn-relying-party⑤①">WebAuthn Relying Party</a> to distinguish between these cases, where "excluded" means that at least one of the <a data-link-type="dfn" href="#public-key-credential" id="ref-for-public-key-credential⑦⑤">credentials</a> listed by the <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party③⑤⑨">Relying Party</a> in <code class="idl"><a data-link-type="idl" href="#dom-publickeycredentialcreationoptions-excludecredentials" id="ref-for-dom-publickeycredentialcreationoptions-excludecredentials③">excludeCredentials</a></code> is <a data-link-type="dfn" href="#bound-credential" id="ref-for-bound-credential①⑦">bound</a> to the <a data-link-type="dfn" href="#authenticator" id="ref-for-authenticator③⓪①">authenticator</a>:</p>
+could enable a malicious <a data-link-type="dfn" href="#webauthn-relying-party" id="ref-for-webauthn-relying-party⑤①">WebAuthn Relying Party</a> to distinguish between these cases, where "excluded" means that at least one of the <a data-link-type="dfn" href="#public-key-credential" id="ref-for-public-key-credential⑦⑤">credentials</a> listed by the <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party③⑥⑥">Relying Party</a> in <code class="idl"><a data-link-type="idl" href="#dom-publickeycredentialcreationoptions-excludecredentials" id="ref-for-dom-publickeycredentialcreationoptions-excludecredentials③">excludeCredentials</a></code> is <a data-link-type="dfn" href="#bound-credential" id="ref-for-bound-credential①⑦">bound</a> to the <a data-link-type="dfn" href="#authenticator" id="ref-for-authenticator③⓪⓪">authenticator</a>:</p>
    <ul>
     <li data-md>
-     <p>No <a data-link-type="dfn" href="#authenticator" id="ref-for-authenticator③⓪②">authenticators</a> are present.</p>
+     <p>No <a data-link-type="dfn" href="#authenticator" id="ref-for-authenticator③⓪①">authenticators</a> are present.</p>
     <li data-md>
-     <p>At least one <a data-link-type="dfn" href="#authenticator" id="ref-for-authenticator③⓪③">authenticator</a> is present, and at least one present <a data-link-type="dfn" href="#authenticator" id="ref-for-authenticator③⓪④">authenticator</a> is excluded.</p>
+     <p>At least one <a data-link-type="dfn" href="#authenticator" id="ref-for-authenticator③⓪②">authenticator</a> is present, and at least one present <a data-link-type="dfn" href="#authenticator" id="ref-for-authenticator③⓪③">authenticator</a> is excluded.</p>
    </ul>
-   <p>If the above cases are distinguishable, information is leaked by which a malicious <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party③⑥⓪">Relying Party</a> could identify the user by probing for
+   <p>If the above cases are distinguishable, information is leaked by which a malicious <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party③⑥⑦">Relying Party</a> could identify the user by probing for
 which <a data-link-type="dfn" href="#public-key-credential" id="ref-for-public-key-credential⑦⑥">credentials</a> are available. For example, one such information leak is if the client returns a
-failure response as soon as an excluded <a data-link-type="dfn" href="#authenticator" id="ref-for-authenticator③⓪⑤">authenticator</a> becomes available. In this case - especially if the excluded <a data-link-type="dfn" href="#authenticator" id="ref-for-authenticator③⓪⑥">authenticator</a> is a <a data-link-type="dfn" href="#platform-authenticators" id="ref-for-platform-authenticators③②">platform authenticator</a> - the <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party③⑥①">Relying Party</a> could detect that the <a data-link-type="dfn" href="#ceremony" id="ref-for-ceremony①②">ceremony</a> was canceled before the
+failure response as soon as an excluded <a data-link-type="dfn" href="#authenticator" id="ref-for-authenticator③⓪④">authenticator</a> becomes available. In this case - especially if the excluded <a data-link-type="dfn" href="#authenticator" id="ref-for-authenticator③⓪⑤">authenticator</a> is a <a data-link-type="dfn" href="#platform-authenticators" id="ref-for-platform-authenticators③②">platform authenticator</a> - the <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party③⑥⑧">Relying Party</a> could detect that the <a data-link-type="dfn" href="#ceremony" id="ref-for-ceremony①④">ceremony</a> was canceled before the
 timeout and before the user could feasibly have canceled it manually, and thus conclude that at least one of the <a data-link-type="dfn" href="#public-key-credential" id="ref-for-public-key-credential⑦⑦">credentials</a> listed in the <code class="idl"><a data-link-type="idl" href="#dom-publickeycredentialcreationoptions-excludecredentials" id="ref-for-dom-publickeycredentialcreationoptions-excludecredentials④">excludeCredentials</a></code> parameter is available to the user.</p>
    <p>The above is not a concern, however, if the user has <a data-link-type="dfn" href="#user-consent" id="ref-for-user-consent②⑧">consented</a> to create a new credential before a
 distinguishable error is returned, because in this case the user has confirmed intent to share the information that would be
 leaked.</p>
    <h4 class="heading settled" data-level="14.5.2" id="sctn-assertion-privacy"><span class="secno">14.5.2. </span><span class="content">Authentication Ceremony Privacy</span><a class="self-link" href="#sctn-assertion-privacy"></a></h4>
    <p>In order to protect users from being identified without <a data-link-type="dfn" href="#user-consent" id="ref-for-user-consent②⑨">consent</a>, implementations of the <code class="idl"><a data-link-type="idl" href="#dom-publickeycredential-discoverfromexternalsource-slot" id="ref-for-dom-publickeycredential-discoverfromexternalsource-slot①④">[[DiscoverFromExternalSource]](origin, options, sameOriginWithAncestors)</a></code> method need to take care to not
-leak information that could enable a malicious <a data-link-type="dfn" href="#webauthn-relying-party" id="ref-for-webauthn-relying-party⑤②">WebAuthn Relying Party</a> to distinguish between these cases, where "named" means that the <a data-link-type="dfn" href="#public-key-credential" id="ref-for-public-key-credential⑦⑧">credential</a> is listed by the <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party③⑥②">Relying Party</a> in <code class="idl"><a data-link-type="idl" href="#dom-publickeycredentialrequestoptions-allowcredentials" id="ref-for-dom-publickeycredentialrequestoptions-allowcredentials②⑦">allowCredentials</a></code>:</p>
+leak information that could enable a malicious <a data-link-type="dfn" href="#webauthn-relying-party" id="ref-for-webauthn-relying-party⑤②">WebAuthn Relying Party</a> to distinguish between these cases, where "named" means that the <a data-link-type="dfn" href="#public-key-credential" id="ref-for-public-key-credential⑦⑧">credential</a> is listed by the <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party③⑥⑨">Relying Party</a> in <code class="idl"><a data-link-type="idl" href="#dom-publickeycredentialrequestoptions-allowcredentials" id="ref-for-dom-publickeycredentialrequestoptions-allowcredentials②⑤">allowCredentials</a></code>:</p>
    <ul>
     <li data-md>
      <p>A named <a data-link-type="dfn" href="#public-key-credential" id="ref-for-public-key-credential⑦⑨">credential</a> is not available.</p>
     <li data-md>
      <p>A named <a data-link-type="dfn" href="#public-key-credential" id="ref-for-public-key-credential⑧⓪">credential</a> is available, but the user does not <a data-link-type="dfn" href="#user-consent" id="ref-for-user-consent③⓪">consent</a> to use it.</p>
    </ul>
-   <p>If the above cases are distinguishable, information is leaked by which a malicious <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party③⑥③">Relying Party</a> could identify the user by probing
+   <p>If the above cases are distinguishable, information is leaked by which a malicious <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party③⑦⓪">Relying Party</a> could identify the user by probing
 for which <a data-link-type="dfn" href="#public-key-credential" id="ref-for-public-key-credential⑧①">credentials</a> are available. For example, one such information leak is if the client returns a
 failure response as soon as the user denies <a data-link-type="dfn" href="#user-consent" id="ref-for-user-consent③①">consent</a> to proceed with an <a data-link-type="dfn" href="#authentication-ceremony" id="ref-for-authentication-ceremony③③">authentication ceremony</a>. In this
-case the <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party③⑥④">Relying Party</a> could detect that the <a data-link-type="dfn" href="#ceremony" id="ref-for-ceremony①③">ceremony</a> was canceled by the user and not the timeout, and thus conclude that at least
-one of the <a data-link-type="dfn" href="#public-key-credential" id="ref-for-public-key-credential⑧②">credentials</a> listed in the <code class="idl"><a data-link-type="idl" href="#dom-publickeycredentialrequestoptions-allowcredentials" id="ref-for-dom-publickeycredentialrequestoptions-allowcredentials②⑧">allowCredentials</a></code> parameter is
+case the <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party③⑦①">Relying Party</a> could detect that the <a data-link-type="dfn" href="#ceremony" id="ref-for-ceremony①⑤">ceremony</a> was canceled by the user and not the timeout, and thus conclude that at least
+one of the <a data-link-type="dfn" href="#public-key-credential" id="ref-for-public-key-credential⑧②">credentials</a> listed in the <code class="idl"><a data-link-type="idl" href="#dom-publickeycredentialrequestoptions-allowcredentials" id="ref-for-dom-publickeycredentialrequestoptions-allowcredentials②⑥">allowCredentials</a></code> parameter is
 available to the user.</p>
    <h4 class="heading settled" data-level="14.5.3" id="sctn-os-account-privacy"><span class="secno">14.5.3. </span><span class="content">Privacy Between Operating System Accounts</span><a class="self-link" href="#sctn-os-account-privacy"></a></h4>
    <p>If a <a data-link-type="dfn" href="#platform-authenticators" id="ref-for-platform-authenticators③③">platform authenticator</a> is included in a <a data-link-type="dfn" href="#client-device" id="ref-for-client-device④⑥">client device</a> with a multi-user operating system, the <a data-link-type="dfn" href="#platform-authenticators" id="ref-for-platform-authenticators③④">platform
 authenticator</a> and <a data-link-type="dfn" href="#client-device" id="ref-for-client-device④⑦">client device</a> SHOULD work together to ensure that the existence of any <a data-link-type="dfn" href="#platform-credential" id="ref-for-platform-credential③">platform credential</a> is revealed
 only to the operating system user that created that <a data-link-type="dfn" href="#platform-credential" id="ref-for-platform-credential④">platform credential</a>.</p>
-   <h3 class="heading settled" data-level="14.6" id="sctn-privacy-considerations-rp"><span class="secno">14.6. </span><span class="content">Privacy considerations for <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party③⑥⑤">Relying Parties</a></span><a class="self-link" href="#sctn-privacy-considerations-rp"></a></h3>
+   <h3 class="heading settled" data-level="14.6" id="sctn-privacy-considerations-rp"><span class="secno">14.6. </span><span class="content">Privacy considerations for <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party③⑦②">Relying Parties</a></span><a class="self-link" href="#sctn-privacy-considerations-rp"></a></h3>
    <h4 class="heading settled" data-level="14.6.1" id="sctn-user-handle-privacy"><span class="secno">14.6.1. </span><span class="content">User Handle Contents</span><a class="self-link" href="#sctn-user-handle-privacy"></a></h4>
-   <p>Since the <a data-link-type="dfn" href="#user-handle" id="ref-for-user-handle②④">user handle</a> is not considered personally identifying information in <a href="#sctn-pii-privacy">§ 14.4.2 Privacy of personally identifying information Stored in Authenticators</a>,
-and since <a data-link-type="dfn" href="#authenticator" id="ref-for-authenticator③⓪⑦">authenticators</a> MAY reveal <a data-link-type="dfn" href="#user-handle" id="ref-for-user-handle②⑤">user handles</a> without first performing <a data-link-type="dfn" href="#user-verification" id="ref-for-user-verification⑤⑥">user verification</a>,
-the <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party③⑥⑥">Relying Party</a> MUST NOT include personally identifying information, e.g., e-mail
-addresses or usernames, in the <a data-link-type="dfn" href="#user-handle" id="ref-for-user-handle②⑥">user handle</a>. This includes hash values of personally identifying information, unless the hash
-function is <a data-link-type="dfn" href="https://tools.ietf.org/html/rfc4949#page-258" id="ref-for-page-258">salted</a> with <a data-link-type="dfn" href="https://tools.ietf.org/html/rfc4949#page-258" id="ref-for-page-258①">salt</a> values private to the <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party③⑥⑦">Relying Party</a>, since hashing does not prevent probing for guessable input
-values. It is RECOMMENDED to let the <a data-link-type="dfn" href="#user-handle" id="ref-for-user-handle②⑦">user handle</a> be 64 random bytes, and store this value in the <a data-link-type="dfn" href="#user-account" id="ref-for-user-account③⑦">user account</a>.</p>
+   <p>Since the <a data-link-type="dfn" href="#user-handle" id="ref-for-user-handle②⑤">user handle</a> is not considered personally identifying information in <a href="#sctn-pii-privacy">§ 14.4.2 Privacy of personally identifying information Stored in Authenticators</a>,
+and since <a data-link-type="dfn" href="#authenticator" id="ref-for-authenticator③⓪⑥">authenticators</a> MAY reveal <a data-link-type="dfn" href="#user-handle" id="ref-for-user-handle②⑥">user handles</a> without first performing <a data-link-type="dfn" href="#user-verification" id="ref-for-user-verification⑤⑥">user verification</a>,
+the <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party③⑦③">Relying Party</a> MUST NOT include personally identifying information, e.g., e-mail
+addresses or usernames, in the <a data-link-type="dfn" href="#user-handle" id="ref-for-user-handle②⑦">user handle</a>. This includes hash values of personally identifying information, unless the hash
+function is <a data-link-type="dfn" href="https://tools.ietf.org/html/rfc4949#page-258" id="ref-for-page-258">salted</a> with <a data-link-type="dfn" href="https://tools.ietf.org/html/rfc4949#page-258" id="ref-for-page-258①">salt</a> values private to the <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party③⑦④">Relying Party</a>, since hashing does not prevent probing for guessable input
+values. It is RECOMMENDED to let the <a data-link-type="dfn" href="#user-handle" id="ref-for-user-handle②⑧">user handle</a> be 64 random bytes, and store this value in the <a data-link-type="dfn" href="#user-account" id="ref-for-user-account④①">user account</a>.</p>
    <h4 class="heading settled" data-level="14.6.2" id="sctn-username-enumeration"><span class="secno">14.6.2. </span><span class="content">Username Enumeration</span><a class="self-link" href="#sctn-username-enumeration"></a></h4>
    <p>While initiating a <a data-link-type="dfn" href="#registration-ceremony" id="ref-for-registration-ceremony①⑥">registration</a> or <a data-link-type="dfn" href="#authentication-ceremony" id="ref-for-authentication-ceremony③④">authentication ceremony</a>, there is a risk that the <a data-link-type="dfn" href="#webauthn-relying-party" id="ref-for-webauthn-relying-party⑤③">WebAuthn Relying Party</a> might leak sensitive
-information about its registered users. For example, if a <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party③⑥⑧">Relying Party</a> uses e-mail addresses as usernames and an attacker attempts to
-initiate an <a data-link-type="dfn" href="#authentication" id="ref-for-authentication①⑧">authentication</a> <a data-link-type="dfn" href="#ceremony" id="ref-for-ceremony①④">ceremony</a> for "alex.mueller@example.com" and the <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party③⑥⑨">Relying Party</a> responds with a failure, but then
+information about its registered users. For example, if a <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party③⑦⑤">Relying Party</a> uses e-mail addresses as usernames and an attacker attempts to
+initiate an <a data-link-type="dfn" href="#authentication" id="ref-for-authentication①⑧">authentication</a> <a data-link-type="dfn" href="#ceremony" id="ref-for-ceremony①⑥">ceremony</a> for "alex.mueller@example.com" and the <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party③⑦⑥">Relying Party</a> responds with a failure, but then
 successfully initiates an <a data-link-type="dfn" href="#authentication-ceremony" id="ref-for-authentication-ceremony③⑤">authentication ceremony</a> for "j.doe@example.com", then the attacker can conclude that "j.doe@example.com"
-is registered and "alex.mueller@example.com" is not. The <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party③⑦⓪">Relying Party</a> has thus leaked the possibly sensitive information that
-"j.doe@example.com" has a <a data-link-type="dfn" href="#user-account" id="ref-for-user-account③⑧">user account</a> at this <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party③⑦①">Relying Party</a>.</p>
-   <p>The following is a non-normative, non-exhaustive list of measures the <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party③⑦②">Relying Party</a> may implement to mitigate or prevent information
+is registered and "alex.mueller@example.com" is not. The <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party③⑦⑦">Relying Party</a> has thus leaked the possibly sensitive information that
+"j.doe@example.com" has a <a data-link-type="dfn" href="#user-account" id="ref-for-user-account④②">user account</a> at this <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party③⑦⑧">Relying Party</a>.</p>
+   <p>The following is a non-normative, non-exhaustive list of measures the <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party③⑦⑨">Relying Party</a> may implement to mitigate or prevent information
 leakage due to such an attack:</p>
    <ul>
     <li data-md>
      <p>For <a data-link-type="dfn" href="#registration-ceremony" id="ref-for-registration-ceremony①⑦">registration ceremonies</a>:</p>
      <ul>
       <li data-md>
-       <p>If the <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party③⑦③">Relying Party</a> uses <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party③⑦④">Relying Party</a>-specific usernames to identify users:</p>
+       <p>If the <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party③⑧⓪">Relying Party</a> uses <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party③⑧①">Relying Party</a>-specific usernames to identify users:</p>
        <ul>
         <li data-md>
          <p>When initiating a <a data-link-type="dfn" href="#registration-ceremony" id="ref-for-registration-ceremony①⑧">registration ceremony</a>, disallow registration of usernames that are syntactically valid e-mail
 addresses.</p>
-         <p class="note" role="note"><span>Note:</span> The motivation for this suggestion is that in this case the <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party③⑦⑤">Relying Party</a> probably has no choice but to fail the <a data-link-type="dfn" href="#registration-ceremony" id="ref-for-registration-ceremony①⑨">registration ceremony</a> if the user attempts to register a username that is already registered, and an information
+         <p class="note" role="note"><span>Note:</span> The motivation for this suggestion is that in this case the <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party③⑧②">Relying Party</a> probably has no choice but to fail the <a data-link-type="dfn" href="#registration-ceremony" id="ref-for-registration-ceremony①⑨">registration ceremony</a> if the user attempts to register a username that is already registered, and an information
 leak might therefore be unavoidable. By disallowing e-mail addresses as usernames, the impact of the leakage can be
-mitigated since it will be less likely that a user has the same username at this <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party③⑦⑥">Relying Party</a> as at other <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party③⑦⑦">Relying Parties</a>.</p>
+mitigated since it will be less likely that a user has the same username at this <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party③⑧③">Relying Party</a> as at other <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party③⑧④">Relying Parties</a>.</p>
        </ul>
       <li data-md>
-       <p>If the <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party③⑦⑧">Relying Party</a> uses e-mail addresses to identify users:</p>
+       <p>If the <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party③⑧⑤">Relying Party</a> uses e-mail addresses to identify users:</p>
        <ul>
         <li data-md>
          <p>When initiating a <a data-link-type="dfn" href="#registration-ceremony" id="ref-for-registration-ceremony②⓪">registration ceremony</a>, interrupt the user interaction after the e-mail address is supplied and
@@ -7585,54 +7663,54 @@ <h4 class="heading settled" data-level="14.6.2" id="sctn-username-enumeration"><
      <p>For <a data-link-type="dfn" href="#authentication-ceremony" id="ref-for-authentication-ceremony③⑥">authentication ceremonies</a>:</p>
      <ul>
       <li data-md>
-       <p>If, when initiating an <a data-link-type="dfn" href="#authentication-ceremony" id="ref-for-authentication-ceremony③⑦">authentication ceremony</a>, there is no <a data-link-type="dfn" href="#user-account" id="ref-for-user-account③⑨">user account</a> matching the provided username, continue the
-ceremony by invoking <code class="idl"><a data-link-type="idl" href="https://w3c.github.io/webappsec-credential-management/#dom-credentialscontainer-get" id="ref-for-dom-credentialscontainer-get③⑧">navigator.credentials.get()</a></code> using a syntactically valid <code class="idl"><a data-link-type="idl" href="#dictdef-publickeycredentialrequestoptions" id="ref-for-dictdef-publickeycredentialrequestoptions①④">PublicKeyCredentialRequestOptions</a></code> object that is populated with plausible imaginary values.</p>
-       <p>This approach could also be used to mitigate information leakage via <code class="idl"><a data-link-type="idl" href="#dom-publickeycredentialrequestoptions-allowcredentials" id="ref-for-dom-publickeycredentialrequestoptions-allowcredentials②⑨">allowCredentials</a></code>;
+       <p>If, when initiating an <a data-link-type="dfn" href="#authentication-ceremony" id="ref-for-authentication-ceremony③⑦">authentication ceremony</a>, there is no <a data-link-type="dfn" href="#user-account" id="ref-for-user-account④③">user account</a> matching the provided username, continue the
+ceremony by invoking <code class="idl"><a data-link-type="idl" href="https://w3c.github.io/webappsec-credential-management/#dom-credentialscontainer-get" id="ref-for-dom-credentialscontainer-get③⑦">navigator.credentials.get()</a></code> using a syntactically valid <code class="idl"><a data-link-type="idl" href="#dictdef-publickeycredentialrequestoptions" id="ref-for-dictdef-publickeycredentialrequestoptions①④">PublicKeyCredentialRequestOptions</a></code> object that is populated with plausible imaginary values.</p>
+       <p>This approach could also be used to mitigate information leakage via <code class="idl"><a data-link-type="idl" href="#dom-publickeycredentialrequestoptions-allowcredentials" id="ref-for-dom-publickeycredentialrequestoptions-allowcredentials②⑦">allowCredentials</a></code>;
 see <a href="#sctn-unprotected-account-detection">§ 13.4.7 Unprotected account detection</a> and <a href="#sctn-credential-id-privacy-leak">§ 14.6.3 Privacy leak via credential IDs</a>.</p>
-       <p class="note" role="note"><span>Note:</span> The username may be "provided" in various <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party③⑦⑨">Relying Party</a>-specific fashions: login form, session cookie, etc.</p>
+       <p class="note" role="note"><span>Note:</span> The username may be "provided" in various <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party③⑧⑥">Relying Party</a>-specific fashions: login form, session cookie, etc.</p>
        <p class="note" role="note"><span>Note:</span> If returned imaginary values noticeably differ from actual ones, clever attackers may be able to discern them and
     thus be able to test for existence of actual accounts. Examples of noticeably different values include if the values
-    are always the same for all username inputs, or are different in repeated attempts with the same username input. The <code class="idl"><a data-link-type="idl" href="#dom-publickeycredentialrequestoptions-allowcredentials" id="ref-for-dom-publickeycredentialrequestoptions-allowcredentials③⓪">allowCredentials</a></code> member could therefore be populated with pseudo-random values
+    are always the same for all username inputs, or are different in repeated attempts with the same username input. The <code class="idl"><a data-link-type="idl" href="#dom-publickeycredentialrequestoptions-allowcredentials" id="ref-for-dom-publickeycredentialrequestoptions-allowcredentials②⑧">allowCredentials</a></code> member could therefore be populated with pseudo-random values
     derived deterministically from the username, for example.</p>
       <li data-md>
-       <p>When verifying an <code class="idl"><a data-link-type="idl" href="#authenticatorassertionresponse" id="ref-for-authenticatorassertionresponse⑧">AuthenticatorAssertionResponse</a></code> response from the <a data-link-type="dfn" href="#authenticator" id="ref-for-authenticator③⓪⑧">authenticator</a>, make it indistinguishable whether
+       <p>When verifying an <code class="idl"><a data-link-type="idl" href="#authenticatorassertionresponse" id="ref-for-authenticatorassertionresponse⑧">AuthenticatorAssertionResponse</a></code> response from the <a data-link-type="dfn" href="#authenticator" id="ref-for-authenticator③⓪⑦">authenticator</a>, make it indistinguishable whether
   verification failed because the signature is invalid or because no such user or credential is registered.</p>
       <li data-md>
        <p>Perform a multi-step <a data-link-type="dfn" href="#authentication-ceremony" id="ref-for-authentication-ceremony③⑧">authentication ceremony</a>, e.g., beginning with supplying username and password or a session cookie,
-before initiating the WebAuthn <a data-link-type="dfn" href="#ceremony" id="ref-for-ceremony①⑤">ceremony</a> as a subsequent step.
+before initiating the WebAuthn <a data-link-type="dfn" href="#ceremony" id="ref-for-ceremony①⑦">ceremony</a> as a subsequent step.
 This moves the username enumeration problem from the WebAuthn step
 to the preceding authentication step, where it may be easier to solve.</p>
      </ul>
    </ul>
    <h4 class="heading settled" data-level="14.6.3" id="sctn-credential-id-privacy-leak"><span class="secno">14.6.3. </span><span class="content">Privacy leak via credential IDs</span><a class="self-link" href="#sctn-credential-id-privacy-leak"></a></h4>
    <p><em>This section is not normative.</em></p>
-   <p>This privacy consideration applies to <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party③⑧⓪">Relying Parties</a> that support <a data-link-type="dfn" href="#authentication-ceremony" id="ref-for-authentication-ceremony③⑨">authentication ceremonies</a> with a non-<a data-link-type="dfn" href="https://infra.spec.whatwg.org/#list-empty" id="ref-for-list-empty⑥">empty</a> <code class="idl"><a data-link-type="idl" href="#dom-publickeycredentialrequestoptions-allowcredentials" id="ref-for-dom-publickeycredentialrequestoptions-allowcredentials③①">allowCredentials</a></code> argument as the first authentication step.
+   <p>This privacy consideration applies to <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party③⑧⑦">Relying Parties</a> that support <a data-link-type="dfn" href="#authentication-ceremony" id="ref-for-authentication-ceremony③⑨">authentication ceremonies</a> with a non-<a data-link-type="dfn" href="https://infra.spec.whatwg.org/#list-empty" id="ref-for-list-empty⑥">empty</a> <code class="idl"><a data-link-type="idl" href="#dom-publickeycredentialrequestoptions-allowcredentials" id="ref-for-dom-publickeycredentialrequestoptions-allowcredentials②⑨">allowCredentials</a></code> argument as the first authentication step.
 For example, if using authentication with <a data-link-type="dfn" href="#server-side-credential" id="ref-for-server-side-credential①⑥">server-side credentials</a> as the first authentication step.</p>
-   <p>In this case the <code class="idl"><a data-link-type="idl" href="#dom-publickeycredentialrequestoptions-allowcredentials" id="ref-for-dom-publickeycredentialrequestoptions-allowcredentials③②">allowCredentials</a></code> argument risks leaking personally identifying information,
-since it exposes the user’s <a data-link-type="dfn" href="#credential-id" id="ref-for-credential-id④⑦">credential IDs</a> to an unauthenticated caller. <a data-link-type="dfn" href="#credential-id" id="ref-for-credential-id④⑧">Credential IDs</a> are designed to not be correlatable between <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party③⑧①">Relying Parties</a>,
-but the length of a <a data-link-type="dfn" href="#credential-id" id="ref-for-credential-id④⑨">credential ID</a> might be a hint as to what type of <a data-link-type="dfn" href="#authenticator" id="ref-for-authenticator③⓪⑨">authenticator</a> created it.
-It is likely that a user will use the same username and set of <a data-link-type="dfn" href="#authenticator" id="ref-for-authenticator③①⓪">authenticators</a> for several <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party③⑧②">Relying Parties</a>,
-so the number of <a data-link-type="dfn" href="#credential-id" id="ref-for-credential-id⑤⓪">credential IDs</a> in <code class="idl"><a data-link-type="idl" href="#dom-publickeycredentialrequestoptions-allowcredentials" id="ref-for-dom-publickeycredentialrequestoptions-allowcredentials③③">allowCredentials</a></code> and their lengths
+   <p>In this case the <code class="idl"><a data-link-type="idl" href="#dom-publickeycredentialrequestoptions-allowcredentials" id="ref-for-dom-publickeycredentialrequestoptions-allowcredentials③⓪">allowCredentials</a></code> argument risks leaking personally identifying information,
+since it exposes the user’s <a data-link-type="dfn" href="#credential-id" id="ref-for-credential-id④⑧">credential IDs</a> to an unauthenticated caller. <a data-link-type="dfn" href="#credential-id" id="ref-for-credential-id④⑨">Credential IDs</a> are designed to not be correlatable between <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party③⑧⑧">Relying Parties</a>,
+but the length of a <a data-link-type="dfn" href="#credential-id" id="ref-for-credential-id⑤⓪">credential ID</a> might be a hint as to what type of <a data-link-type="dfn" href="#authenticator" id="ref-for-authenticator③⓪⑧">authenticator</a> created it.
+It is likely that a user will use the same username and set of <a data-link-type="dfn" href="#authenticator" id="ref-for-authenticator③⓪⑨">authenticators</a> for several <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party③⑧⑨">Relying Parties</a>,
+so the number of <a data-link-type="dfn" href="#credential-id" id="ref-for-credential-id⑤①">credential IDs</a> in <code class="idl"><a data-link-type="idl" href="#dom-publickeycredentialrequestoptions-allowcredentials" id="ref-for-dom-publickeycredentialrequestoptions-allowcredentials③①">allowCredentials</a></code> and their lengths
 might serve as a global correlation handle to de-anonymize the user.
-Knowing a user’s <a data-link-type="dfn" href="#credential-id" id="ref-for-credential-id⑤①">credential IDs</a> also makes it possible to confirm guesses about the user’s identity
-given only momentary physical access to one of the user’s <a data-link-type="dfn" href="#authenticator" id="ref-for-authenticator③①①">authenticators</a>.</p>
-   <p>In order to prevent such information leakage, the <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party③⑧③">Relying Party</a> could for example:</p>
+Knowing a user’s <a data-link-type="dfn" href="#credential-id" id="ref-for-credential-id⑤②">credential IDs</a> also makes it possible to confirm guesses about the user’s identity
+given only momentary physical access to one of the user’s <a data-link-type="dfn" href="#authenticator" id="ref-for-authenticator③①⓪">authenticators</a>.</p>
+   <p>In order to prevent such information leakage, the <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party③⑨⓪">Relying Party</a> could for example:</p>
    <ul>
     <li data-md>
      <p>Perform a separate authentication step,
 such as username and password authentication or session cookie authentication,
-before initiating the WebAuthn <a data-link-type="dfn" href="#authentication-ceremony" id="ref-for-authentication-ceremony④⓪">authentication ceremony</a> and exposing the user’s <a data-link-type="dfn" href="#credential-id" id="ref-for-credential-id⑤②">credential IDs</a>.</p>
+before initiating the WebAuthn <a data-link-type="dfn" href="#authentication-ceremony" id="ref-for-authentication-ceremony④⓪">authentication ceremony</a> and exposing the user’s <a data-link-type="dfn" href="#credential-id" id="ref-for-credential-id⑤③">credential IDs</a>.</p>
     <li data-md>
      <p>Use <a data-link-type="dfn" href="#client-side-discoverable-credential" id="ref-for-client-side-discoverable-credential①⑧">client-side discoverable credentials</a>,
-so the <code class="idl"><a data-link-type="idl" href="#dom-publickeycredentialrequestoptions-allowcredentials" id="ref-for-dom-publickeycredentialrequestoptions-allowcredentials③④">allowCredentials</a></code> argument is not needed.</p>
+so the <code class="idl"><a data-link-type="idl" href="#dom-publickeycredentialrequestoptions-allowcredentials" id="ref-for-dom-publickeycredentialrequestoptions-allowcredentials③②">allowCredentials</a></code> argument is not needed.</p>
    </ul>
    <p>If the above prevention measures are not available,
-i.e., if <code class="idl"><a data-link-type="idl" href="#dom-publickeycredentialrequestoptions-allowcredentials" id="ref-for-dom-publickeycredentialrequestoptions-allowcredentials③⑤">allowCredentials</a></code> needs to be exposed given only a username,
-the <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party③⑧④">Relying Party</a> could mitigate the privacy leak using the same approach of returning imaginary <a data-link-type="dfn" href="#credential-id" id="ref-for-credential-id⑤③">credential IDs</a> as discussed in <a href="#sctn-username-enumeration">§ 14.6.2 Username Enumeration</a>.</p>
+i.e., if <code class="idl"><a data-link-type="idl" href="#dom-publickeycredentialrequestoptions-allowcredentials" id="ref-for-dom-publickeycredentialrequestoptions-allowcredentials③③">allowCredentials</a></code> needs to be exposed given only a username,
+the <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party③⑨①">Relying Party</a> could mitigate the privacy leak using the same approach of returning imaginary <a data-link-type="dfn" href="#credential-id" id="ref-for-credential-id⑤④">credential IDs</a> as discussed in <a href="#sctn-username-enumeration">§ 14.6.2 Username Enumeration</a>.</p>
    <h2 class="heading settled" data-level="15" id="sctn-accessiblility-considerations"><span class="secno">15. </span><span class="content">Accessibility Considerations</span><a class="self-link" href="#sctn-accessiblility-considerations"></a></h2>
-   <p><a data-link-type="dfn" href="#user-verification" id="ref-for-user-verification⑤⑦">User verification</a>-capable <a data-link-type="dfn" href="#authenticator" id="ref-for-authenticator③①②">authenticators</a>, whether <a data-link-type="dfn" href="#roaming-authenticators" id="ref-for-roaming-authenticators②⑦">roaming</a> or <a data-link-type="dfn" href="#platform-authenticators" id="ref-for-platform-authenticators③⑤">platform</a>, should offer users more than one user verification method.  For example, both fingerprint sensing and PIN entry. This allows for fallback to other user verification means if the selected one is not working for some reason. Note that in the case of <a data-link-type="dfn" href="#roaming-authenticators" id="ref-for-roaming-authenticators②⑧">roaming authenticators</a>, the authenticator and platform might work together to provide a user verification method such as PIN entry <a data-link-type="biblio" href="#biblio-fido-ctap">[FIDO-CTAP]</a>.</p>
-   <p><a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party③⑧⑤">Relying Parties</a>, at <a data-link-type="dfn" href="#registration" id="ref-for-registration②⑦">registration</a> time, SHOULD provide affordances for users to complete future <a data-link-type="dfn" href="#authorization-gesture" id="ref-for-authorization-gesture③⓪">authorization gestures</a> correctly. This could involve naming the authenticator, choosing a picture to associate with the device, or entering freeform text instructions (e.g., as a reminder-to-self).</p>
-   <p><a data-link-type="dfn" href="#ceremony" id="ref-for-ceremony①⑥">Ceremonies</a> relying on timing, e.g., a <a data-link-type="dfn" href="#registration-ceremony" id="ref-for-registration-ceremony②①">registration ceremony</a> (see <code class="idl"><a data-link-type="idl" href="#dom-publickeycredentialcreationoptions-timeout" id="ref-for-dom-publickeycredentialcreationoptions-timeout④">timeout</a></code>) or an <a data-link-type="dfn" href="#authentication-ceremony" id="ref-for-authentication-ceremony④①">authentication ceremony</a> (see <code class="idl"><a data-link-type="idl" href="#dom-publickeycredentialrequestoptions-timeout" id="ref-for-dom-publickeycredentialrequestoptions-timeout④">timeout</a></code>), ought to follow <a data-link-type="biblio" href="#biblio-wcag21">[WCAG21]</a>'s <a href="https://www.w3.org/TR/WCAG21/#enough-time">Guideline 2.2 Enough Time</a>. If a <a data-link-type="dfn" href="#client-platform" id="ref-for-client-platform⑤④">client platform</a> determines that a <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party③⑧⑥">Relying Party</a>-supplied timeout does not appropriately adhere to the latter <a data-link-type="biblio" href="#biblio-wcag21">[WCAG21]</a> guidelines, then the <a data-link-type="dfn" href="#client-platform" id="ref-for-client-platform⑤⑤">client platform</a> MAY adjust the timeout accordingly.</p>
+   <p><a data-link-type="dfn" href="#user-verification" id="ref-for-user-verification⑤⑦">User verification</a>-capable <a data-link-type="dfn" href="#authenticator" id="ref-for-authenticator③①①">authenticators</a>, whether <a data-link-type="dfn" href="#roaming-authenticators" id="ref-for-roaming-authenticators②⑦">roaming</a> or <a data-link-type="dfn" href="#platform-authenticators" id="ref-for-platform-authenticators③⑤">platform</a>, should offer users more than one user verification method.  For example, both fingerprint sensing and PIN entry. This allows for fallback to other user verification means if the selected one is not working for some reason. Note that in the case of <a data-link-type="dfn" href="#roaming-authenticators" id="ref-for-roaming-authenticators②⑧">roaming authenticators</a>, the authenticator and platform might work together to provide a user verification method such as PIN entry <a data-link-type="biblio" href="#biblio-fido-ctap">[FIDO-CTAP]</a>.</p>
+   <p><a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party③⑨②">Relying Parties</a>, at <a data-link-type="dfn" href="#registration" id="ref-for-registration③⓪">registration</a> time, SHOULD provide affordances for users to complete future <a data-link-type="dfn" href="#authorization-gesture" id="ref-for-authorization-gesture③⓪">authorization gestures</a> correctly. This could involve naming the authenticator, choosing a picture to associate with the device, or entering freeform text instructions (e.g., as a reminder-to-self).</p>
+   <p><a data-link-type="dfn" href="#ceremony" id="ref-for-ceremony①⑧">Ceremonies</a> relying on timing, e.g., a <a data-link-type="dfn" href="#registration-ceremony" id="ref-for-registration-ceremony②①">registration ceremony</a> (see <code class="idl"><a data-link-type="idl" href="#dom-publickeycredentialcreationoptions-timeout" id="ref-for-dom-publickeycredentialcreationoptions-timeout④">timeout</a></code>) or an <a data-link-type="dfn" href="#authentication-ceremony" id="ref-for-authentication-ceremony④①">authentication ceremony</a> (see <code class="idl"><a data-link-type="idl" href="#dom-publickeycredentialrequestoptions-timeout" id="ref-for-dom-publickeycredentialrequestoptions-timeout④">timeout</a></code>), ought to follow <a data-link-type="biblio" href="#biblio-wcag21">[WCAG21]</a>'s <a href="https://www.w3.org/TR/WCAG21/#enough-time">Guideline 2.2 Enough Time</a>. If a <a data-link-type="dfn" href="#client-platform" id="ref-for-client-platform⑤④">client platform</a> determines that a <a data-link-type="dfn" href="#relying-party" id="ref-for-relying-party③⑨③">Relying Party</a>-supplied timeout does not appropriately adhere to the latter <a data-link-type="biblio" href="#biblio-wcag21">[WCAG21]</a> guidelines, then the <a data-link-type="dfn" href="#client-platform" id="ref-for-client-platform⑤⑤">client platform</a> MAY adjust the timeout accordingly.</p>
    <h2 class="heading settled" data-level="16" id="sctn-acknowledgements"><span class="secno">16. </span><span class="content">Acknowledgements</span><a class="self-link" href="#sctn-acknowledgements"></a></h2>
     We thank the following people for their reviews of, and contributions to, this specification:
 Yuriy Ackermann,
@@ -7657,7 +7735,7 @@ <h2 class="heading settled" data-level="16" id="sctn-acknowledgements"><span cla
 Johan Verrept,
 and
 Boris Zbarsky. 
-   <p>Thanks to Adam Powers for creating the overall <a data-link-type="dfn" href="#registration" id="ref-for-registration②⑧">registration</a> and <a data-link-type="dfn" href="#authentication" id="ref-for-authentication①⑨">authentication</a> flow diagrams
+   <p>Thanks to Adam Powers for creating the overall <a data-link-type="dfn" href="#registration" id="ref-for-registration③①">registration</a> and <a data-link-type="dfn" href="#authentication" id="ref-for-authentication①⑨">authentication</a> flow diagrams
 (<a href="#fig-registration">Figure 1</a> and <a href="#fig-authentication">Figure 2</a>).</p>
    <p>We thank
 Anthony Nadalin,
@@ -7715,6 +7793,7 @@ <h3 class="no-num no-ref heading settled" id="index-defined-here"><span class="c
     </ul>
    <li><a href="#attestation-ca">Attestation CA</a><span>, in § 6.5.3</span>
    <li><a href="#attestation-certificate">Attestation Certificate</a><span>, in § 4</span>
+   <li><a href="#credential-record-attestationclientdatajson">attestationClientDataJSON</a><span>, in § 4</span>
    <li><a href="#attestation-conveyance">Attestation Conveyance</a><span>, in § 5.4.7</span>
    <li><a href="#enumdef-attestationconveyancepreference">AttestationConveyancePreference</a><span>, in § 5.4.7</span>
    <li><a href="#credentialcreationdata-attestationconveyancepreferenceoption">attestationConveyancePreferenceOption</a><span>, in § 5.1.3</span>
@@ -7724,6 +7803,7 @@ <h3 class="no-num no-ref heading settled" id="index-defined-here"><span class="c
     attestationObject
     <ul>
      <li><a href="#dom-authenticatorattestationresponse-attestationobject">attribute for AuthenticatorAttestationResponse</a><span>, in § 5.2.1</span>
+     <li><a href="#credential-record-attestationobject">dfn for credential record</a><span>, in § 4</span>
      <li><a href="#dom-authenticatorattestationresponsejson-attestationobject">dict-member for AuthenticatorAttestationResponseJSON</a><span>, in § 5.1</span>
     </ul>
    <li><a href="#credentialcreationdata-attestationobjectresult">attestationObjectResult</a><span>, in § 5.1.3</span>
@@ -7810,14 +7890,24 @@ <h3 class="no-num no-ref heading settled" id="index-defined-here"><span class="c
    <li><a href="#basic">Basic</a><span>, in § 6.5.3</span>
    <li><a href="#basic-attestation">Basic Attestation</a><span>, in § 6.5.3</span>
    <li><a href="#batch-attestation">batch attestation</a><span>, in § 6.5.3</span>
-   <li><a href="#authdata-flags-be">BE</a><span>, in § 6.1</span>
+   <li>
+    BE
+    <ul>
+     <li><a href="#authdata-flags-be">dfn for authData/flags</a><span>, in § 6.1</span>
+     <li><a href="#credential-record-be">dfn for credential record</a><span>, in § 4</span>
+    </ul>
    <li><a href="#biometric-authenticator">Biometric Authenticator</a><span>, in § 4</span>
    <li><a href="#biometric-recognition">Biometric Recognition</a><span>, in § 4</span>
    <li><a href="#dom-authenticatortransport-ble">"ble"</a><span>, in § 5.8.4</span>
    <li><a href="#dom-authenticatortransport-ble">ble</a><span>, in § 5.8.4</span>
    <li><a href="#dom-authenticationextensionslargebloboutputs-blob">blob</a><span>, in § 10.1.5</span>
    <li><a href="#bound-credential">Bound credential</a><span>, in § 4</span>
-   <li><a href="#authdata-flags-bs">BS</a><span>, in § 6.1</span>
+   <li>
+    BS
+    <ul>
+     <li><a href="#authdata-flags-bs">dfn for authData/flags</a><span>, in § 6.1</span>
+     <li><a href="#credential-record-bs">dfn for credential record</a><span>, in § 4</span>
+    </ul>
    <li><a href="#create-candidate-authenticator">candidate authenticator</a><span>, in § 5.1.3</span>
    <li><a href="#cbor">CBOR</a><span>, in § 3</span>
    <li><a href="#ccdtostring">CCDToString</a><span>, in § 5.8.1.1</span>
@@ -7874,6 +7964,7 @@ <h3 class="no-num no-ref heading settled" id="index-defined-here"><span class="c
    <li><a href="#typedefdef-cosealgorithmidentifier">COSEAlgorithmIdentifier</a><span>, in § 5.8.5</span>
    <li><a href="#created-on">created on</a><span>, in § 4</span>
    <li><a href="#dom-publickeycredential-create-slot">[[Create]](origin, options, sameOriginWithAncestors)</a><span>, in § 5.1.3</span>
+   <li><a href="#credential-descriptor-for-a-credential-record">credential descriptor for a credential record</a><span>, in § 4</span>
    <li><a href="#credential-id">Credential ID</a><span>, in § 4</span>
    <li><a href="#authdata-attestedcredentialdata-credentialid">credentialId</a><span>, in § 6.5.1</span>
    <li><a href="#authdata-attestedcredentialdata-credentialidlength">credentialIdLength</a><span>, in § 6.5.1</span>
@@ -7885,6 +7976,7 @@ <h3 class="no-num no-ref heading settled" id="index-defined-here"><span class="c
    <li><a href="#dictdef-credentialpropertiesoutput">CredentialPropertiesOutput</a><span>, in § 10.1.3</span>
    <li><a href="#credential-public-key">Credential Public Key</a><span>, in § 4</span>
    <li><a href="#authdata-attestedcredentialdata-credentialpublickey">credentialPublicKey</a><span>, in § 6.5.1</span>
+   <li><a href="#credential-record">Credential Record</a><span>, in § 4</span>
    <li><a href="#authenticator-credentials-map">credentials map</a><span>, in § 6</span>
    <li><a href="#credential-storage-modality">credential storage modality</a><span>, in § 6.2.2</span>
    <li>
@@ -7967,6 +8059,7 @@ <h3 class="no-num no-ref heading settled" id="index-defined-here"><span class="c
     id
     <ul>
      <li><a href="#discoverablecredentialmetadata-id">dfn for DiscoverableCredentialMetadata</a><span>, in § 6.3.5</span>
+     <li><a href="#credential-record-id">dfn for credential record</a><span>, in § 4</span>
      <li><a href="#public-key-credential-source-id">dfn for public key credential source</a><span>, in § 4</span>
      <li><a href="#dom-authenticationresponsejson-id">dict-member for AuthenticationResponseJSON</a><span>, in § 5.1</span>
      <li><a href="#dom-publickeycredentialdescriptor-id">dict-member for PublicKeyCredentialDescriptor</a><span>, in § 5.8.3</span>
@@ -8062,6 +8155,7 @@ <h3 class="no-num no-ref heading settled" id="index-defined-here"><span class="c
    <li>
     publicKey
     <ul>
+     <li><a href="#credential-record-publickey">dfn for credential record</a><span>, in § 4</span>
      <li><a href="#dom-credentialcreationoptions-publickey">dict-member for CredentialCreationOptions</a><span>, in § 5.1.1</span>
      <li><a href="#dom-credentialrequestoptions-publickey">dict-member for CredentialRequestOptions</a><span>, in § 5.1.2</span>
     </ul>
@@ -8164,7 +8258,12 @@ <h3 class="no-num no-ref heading settled" id="index-defined-here"><span class="c
     </ul>
    <li><a href="#signature-counter">Signature Counter</a><span>, in § 6.1.1</span>
    <li><a href="#assertioncreationdata-signatureresult">signatureResult</a><span>, in § 5.1.4.1</span>
-   <li><a href="#authdata-signcount">signCount</a><span>, in § 6.1</span>
+   <li>
+    signCount
+    <ul>
+     <li><a href="#authdata-signcount">dfn for authData</a><span>, in § 6.1</span>
+     <li><a href="#credential-record-signcount">dfn for credential record</a><span>, in § 4</span>
+    </ul>
    <li><a href="#signing-procedure">Signing procedure</a><span>, in § 6.5.2</span>
    <li><a href="#silentcredentialdiscovery">silentCredentialDiscovery</a><span>, in § 6.3.5</span>
    <li><a href="#single-device-credential">single-device credential</a><span>, in § 4</span>
@@ -8196,6 +8295,7 @@ <h3 class="no-num no-ref heading settled" id="index-defined-here"><span class="c
    <li>
     transports
     <ul>
+     <li><a href="#credential-record-transports">dfn for credential record</a><span>, in § 4</span>
      <li><a href="#dom-authenticatorattestationresponsejson-transports">dict-member for AuthenticatorAttestationResponseJSON</a><span>, in § 5.1</span>
      <li><a href="#dom-publickeycredentialdescriptor-transports">dict-member for PublicKeyCredentialDescriptor</a><span>, in § 5.8.3</span>
      <li><a href="#dom-publickeycredentialdescriptorjson-transports">dict-member for PublicKeyCredentialDescriptorJSON</a><span>, in § 5.1.8</span>
@@ -8205,6 +8305,7 @@ <h3 class="no-num no-ref heading settled" id="index-defined-here"><span class="c
     type
     <ul>
      <li><a href="#discoverablecredentialmetadata-type">dfn for DiscoverableCredentialMetadata</a><span>, in § 6.3.5</span>
+     <li><a href="#credential-record-type">dfn for credential record</a><span>, in § 4</span>
      <li><a href="#public-key-credential-source-type">dfn for public key credential source</a><span>, in § 4</span>
      <li><a href="#dom-authenticationresponsejson-type">dict-member for AuthenticationResponseJSON</a><span>, in § 5.1</span>
      <li><a href="#dom-collectedclientdata-type">dict-member for CollectedClientData</a><span>, in § 5.8.1</span>
@@ -8382,10 +8483,11 @@ <h3 class="no-num no-ref heading settled" id="index-defined-here"><span class="c
     <li><a href="#ref-for-concept-credential⑥">5.1.4. Use an Existing Credential to Make an Assertion - PublicKeyCredential’s [[Get]](options) Method</a> <a href="#ref-for-concept-credential⑦">(2)</a>
     <li><a href="#ref-for-concept-credential⑧">5.1.4.2. Issuing a Credential Request to an Authenticator</a>
     <li><a href="#ref-for-concept-credential⑨">5.4. Options for Credential Creation (dictionary PublicKeyCredentialCreationOptions)</a> <a href="#ref-for-concept-credential①⓪">(2)</a> <a href="#ref-for-concept-credential①①">(3)</a>
-    <li><a href="#ref-for-concept-credential①②">5.5. Options for Assertion Generation (dictionary PublicKeyCredentialRequestOptions)</a> <a href="#ref-for-concept-credential①③">(2)</a>
-    <li><a href="#ref-for-concept-credential①④">6.1.3. Credential Backup State</a> <a href="#ref-for-concept-credential①⑤">(2)</a>
-    <li><a href="#ref-for-concept-credential①⑥">6.2.2. Credential Storage Modality</a>
-    <li><a href="#ref-for-concept-credential①⑦">6.5.3. Attestation Types</a>
+    <li><a href="#ref-for-concept-credential①②">5.5. Options for Assertion Generation (dictionary PublicKeyCredentialRequestOptions)</a>
+    <li><a href="#ref-for-concept-credential①③">6.1.3. Credential Backup State</a> <a href="#ref-for-concept-credential①④">(2)</a>
+    <li><a href="#ref-for-concept-credential①⑤">6.2.2. Credential Storage Modality</a>
+    <li><a href="#ref-for-concept-credential①⑥">6.5.3. Attestation Types</a>
+    <li><a href="#ref-for-concept-credential①⑦">7.2. Verifying an Authentication Assertion</a>
     <li><a href="#ref-for-concept-credential①⑧">10.1.4. Pseudo-random function extension (prf)</a> <a href="#ref-for-concept-credential①⑨">(2)</a> <a href="#ref-for-concept-credential②⓪">(3)</a>
     <li><a href="#ref-for-concept-credential②①">12.4. WebAuthn Extension Identifier Registrations</a>
     <li><a href="#ref-for-concept-credential②②">13.2. Physical Proximity between Client and Authenticator</a>
@@ -8417,20 +8519,20 @@ <h3 class="no-num no-ref heading settled" id="index-defined-here"><span class="c
     <li><a href="#ref-for-dom-credentialscontainer-get②⑥">5.9. Permissions Policy integration</a>
     <li><a href="#ref-for-dom-credentialscontainer-get②⑦">6.2.2. Credential Storage Modality</a>
     <li><a href="#ref-for-dom-credentialscontainer-get②⑧">7. WebAuthn Relying Party Operations</a>
-    <li><a href="#ref-for-dom-credentialscontainer-get②⑨">7.1. Registering a New Credential</a>
-    <li><a href="#ref-for-dom-credentialscontainer-get③⓪">7.2. Verifying an Authentication Assertion</a>
-    <li><a href="#ref-for-dom-credentialscontainer-get③①">9. WebAuthn Extensions</a> <a href="#ref-for-dom-credentialscontainer-get③②">(2)</a> <a href="#ref-for-dom-credentialscontainer-get③③">(3)</a>
-    <li><a href="#ref-for-dom-credentialscontainer-get③④">9.2. Defining Extensions</a>
-    <li><a href="#ref-for-dom-credentialscontainer-get③⑤">9.3. Extending Request Parameters</a> <a href="#ref-for-dom-credentialscontainer-get③⑥">(2)</a>
-    <li><a href="#ref-for-dom-credentialscontainer-get③⑦">10.1.1. FIDO AppID Extension (appid)</a>
-    <li><a href="#ref-for-dom-credentialscontainer-get③⑧">14.6.2. Username Enumeration</a>
+    <li><a href="#ref-for-dom-credentialscontainer-get②⑨">7.2. Verifying an Authentication Assertion</a>
+    <li><a href="#ref-for-dom-credentialscontainer-get③⓪">9. WebAuthn Extensions</a> <a href="#ref-for-dom-credentialscontainer-get③①">(2)</a> <a href="#ref-for-dom-credentialscontainer-get③②">(3)</a>
+    <li><a href="#ref-for-dom-credentialscontainer-get③③">9.2. Defining Extensions</a>
+    <li><a href="#ref-for-dom-credentialscontainer-get③④">9.3. Extending Request Parameters</a> <a href="#ref-for-dom-credentialscontainer-get③⑤">(2)</a>
+    <li><a href="#ref-for-dom-credentialscontainer-get③⑥">10.1.1. FIDO AppID Extension (appid)</a>
+    <li><a href="#ref-for-dom-credentialscontainer-get③⑦">14.6.2. Username Enumeration</a>
    </ul>
   </aside>
   <aside class="dfn-panel" data-for="term-for-dom-credential-id">
    <a href="https://w3c.github.io/webappsec-credential-management/#dom-credential-id">https://w3c.github.io/webappsec-credential-management/#dom-credential-id</a><b>Referenced in:</b>
    <ul>
     <li><a href="#ref-for-dom-credential-id">5.1. PublicKeyCredential Interface</a>
-    <li><a href="#ref-for-dom-credential-id①">7.2. Verifying an Authentication Assertion</a> <a href="#ref-for-dom-credential-id②">(2)</a> <a href="#ref-for-dom-credential-id③">(3)</a> <a href="#ref-for-dom-credential-id④">(4)</a>
+    <li><a href="#ref-for-dom-credential-id①">7.1. Registering a New Credential</a>
+    <li><a href="#ref-for-dom-credential-id②">7.2. Verifying an Authentication Assertion</a>
    </ul>
   </aside>
   <aside class="dfn-panel" data-for="term-for-dom-credentialrequestoptions-mediation">
@@ -8472,6 +8574,7 @@ <h3 class="no-num no-ref heading settled" id="index-defined-here"><span class="c
    <ul>
     <li><a href="#ref-for-dom-credential-type">5.1. PublicKeyCredential Interface</a>
     <li><a href="#ref-for-dom-credential-type①">5.8.3. Credential Descriptor (dictionary PublicKeyCredentialDescriptor)</a>
+    <li><a href="#ref-for-dom-credential-type②">7.1. Registering a New Credential</a>
    </ul>
   </aside>
   <aside class="dfn-panel" data-for="term-for-user-mediated">
@@ -8938,10 +9041,10 @@ <h3 class="no-num no-ref heading settled" id="index-defined-here"><span class="c
   <aside class="dfn-panel" data-for="term-for-struct-item">
    <a href="https://infra.spec.whatwg.org/#struct-item">https://infra.spec.whatwg.org/#struct-item</a><b>Referenced in:</b>
    <ul>
-    <li><a href="#ref-for-struct-item">4. Terminology</a> <a href="#ref-for-struct-item①">(2)</a>
-    <li><a href="#ref-for-struct-item②">5.1.3. Create a New Credential - PublicKeyCredential’s [[Create]](origin, options, sameOriginWithAncestors) Method</a>
-    <li><a href="#ref-for-struct-item③">5.1.4.1. PublicKeyCredential’s [[DiscoverFromExternalSource]](origin, options, sameOriginWithAncestors) Method</a>
-    <li><a href="#ref-for-struct-item④">6.3.5. The silentCredentialDiscovery operation</a> <a href="#ref-for-struct-item⑤">(2)</a>
+    <li><a href="#ref-for-struct-item">4. Terminology</a> <a href="#ref-for-struct-item①">(2)</a> <a href="#ref-for-struct-item②">(3)</a> <a href="#ref-for-struct-item③">(4)</a> <a href="#ref-for-struct-item④">(5)</a> <a href="#ref-for-struct-item⑤">(6)</a> <a href="#ref-for-struct-item⑥">(7)</a> <a href="#ref-for-struct-item⑦">(8)</a>
+    <li><a href="#ref-for-struct-item⑧">5.1.3. Create a New Credential - PublicKeyCredential’s [[Create]](origin, options, sameOriginWithAncestors) Method</a>
+    <li><a href="#ref-for-struct-item⑨">5.1.4.1. PublicKeyCredential’s [[DiscoverFromExternalSource]](origin, options, sameOriginWithAncestors) Method</a>
+    <li><a href="#ref-for-struct-item①⓪">6.3.5. The silentCredentialDiscovery operation</a> <a href="#ref-for-struct-item①①">(2)</a>
    </ul>
   </aside>
   <aside class="dfn-panel" data-for="term-for-map-key">
@@ -9014,10 +9117,10 @@ <h3 class="no-num no-ref heading settled" id="index-defined-here"><span class="c
   <aside class="dfn-panel" data-for="term-for-struct">
    <a href="https://infra.spec.whatwg.org/#struct">https://infra.spec.whatwg.org/#struct</a><b>Referenced in:</b>
    <ul>
-    <li><a href="#ref-for-struct">4. Terminology</a>
-    <li><a href="#ref-for-struct①">5.1.3. Create a New Credential - PublicKeyCredential’s [[Create]](origin, options, sameOriginWithAncestors) Method</a>
-    <li><a href="#ref-for-struct②">5.1.4.1. PublicKeyCredential’s [[DiscoverFromExternalSource]](origin, options, sameOriginWithAncestors) Method</a>
-    <li><a href="#ref-for-struct③">6.3.5. The silentCredentialDiscovery operation</a> <a href="#ref-for-struct④">(2)</a>
+    <li><a href="#ref-for-struct">4. Terminology</a> <a href="#ref-for-struct①">(2)</a>
+    <li><a href="#ref-for-struct②">5.1.3. Create a New Credential - PublicKeyCredential’s [[Create]](origin, options, sameOriginWithAncestors) Method</a>
+    <li><a href="#ref-for-struct③">5.1.4.1. PublicKeyCredential’s [[DiscoverFromExternalSource]](origin, options, sameOriginWithAncestors) Method</a>
+    <li><a href="#ref-for-struct④">6.3.5. The silentCredentialDiscovery operation</a> <a href="#ref-for-struct⑤">(2)</a>
    </ul>
   </aside>
   <aside class="dfn-panel" data-for="term-for-map-value">
@@ -10485,11 +10588,10 @@ <h2 class="no-num no-ref heading settled" id="issues-index"><span class="content
     <li><a href="#ref-for-base64url-encoding①⓪">5.8.1. Client Data Used in WebAuthn Signatures (dictionary CollectedClientData)</a>
     <li><a href="#ref-for-base64url-encoding①①">5.8.1.1. Serialization</a>
     <li><a href="#ref-for-base64url-encoding①②">5.8.1.2. Limited Verification Algorithm</a>
-    <li><a href="#ref-for-base64url-encoding①③">7.2. Verifying an Authentication Assertion</a>
-    <li><a href="#ref-for-base64url-encoding①④">10.1.1. FIDO AppID Extension (appid)</a>
-    <li><a href="#ref-for-base64url-encoding①⑤">10.1.2. FIDO AppID Exclusion Extension (appidExclude)</a>
-    <li><a href="#ref-for-base64url-encoding①⑥">10.1.4. Pseudo-random function extension (prf)</a> <a href="#ref-for-base64url-encoding①⑦">(2)</a>
-    <li><a href="#ref-for-base64url-encoding①⑧">11.5. Add Credential</a> <a href="#ref-for-base64url-encoding①⑨">(2)</a> <a href="#ref-for-base64url-encoding②⓪">(3)</a> <a href="#ref-for-base64url-encoding②①">(4)</a> <a href="#ref-for-base64url-encoding②②">(5)</a> <a href="#ref-for-base64url-encoding②③">(6)</a> <a href="#ref-for-base64url-encoding②④">(7)</a> <a href="#ref-for-base64url-encoding②⑤">(8)</a>
+    <li><a href="#ref-for-base64url-encoding①③">10.1.1. FIDO AppID Extension (appid)</a>
+    <li><a href="#ref-for-base64url-encoding①④">10.1.2. FIDO AppID Exclusion Extension (appidExclude)</a>
+    <li><a href="#ref-for-base64url-encoding①⑤">10.1.4. Pseudo-random function extension (prf)</a> <a href="#ref-for-base64url-encoding①⑥">(2)</a>
+    <li><a href="#ref-for-base64url-encoding①⑦">11.5. Add Credential</a> <a href="#ref-for-base64url-encoding①⑧">(2)</a> <a href="#ref-for-base64url-encoding①⑨">(3)</a> <a href="#ref-for-base64url-encoding②⓪">(4)</a> <a href="#ref-for-base64url-encoding②①">(5)</a> <a href="#ref-for-base64url-encoding②②">(6)</a> <a href="#ref-for-base64url-encoding②③">(7)</a> <a href="#ref-for-base64url-encoding②④">(8)</a>
    </ul>
   </aside>
   <aside class="dfn-panel" data-for="cbor">
@@ -10598,16 +10700,15 @@ <h2 class="no-num no-ref heading settled" id="issues-index"><span class="content
   <aside class="dfn-panel" data-for="authentication-ceremony">
    <b><a href="#authentication-ceremony">#authentication-ceremony</a></b><b>Referenced in:</b>
    <ul>
-    <li><a href="#ref-for-authentication-ceremony">4. Terminology</a> <a href="#ref-for-authentication-ceremony①">(2)</a> <a href="#ref-for-authentication-ceremony②">(3)</a> <a href="#ref-for-authentication-ceremony③">(4)</a> <a href="#ref-for-authentication-ceremony④">(5)</a> <a href="#ref-for-authentication-ceremony⑤">(6)</a> <a href="#ref-for-authentication-ceremony⑥">(7)</a>
-    <li><a href="#ref-for-authentication-ceremony⑦">5.1. PublicKeyCredential Interface</a>
-    <li><a href="#ref-for-authentication-ceremony⑧">5.1.4.2. Issuing a Credential Request to an Authenticator</a>
-    <li><a href="#ref-for-authentication-ceremony⑨">5.4. Options for Credential Creation (dictionary PublicKeyCredentialCreationOptions)</a> <a href="#ref-for-authentication-ceremony①⓪">(2)</a> <a href="#ref-for-authentication-ceremony①①">(3)</a>
-    <li><a href="#ref-for-authentication-ceremony①②">5.4.5. Authenticator Attachment Enumeration (enum AuthenticatorAttachment)</a>
-    <li><a href="#ref-for-authentication-ceremony①③">5.5. Options for Assertion Generation (dictionary PublicKeyCredentialRequestOptions)</a> <a href="#ref-for-authentication-ceremony①④">(2)</a> <a href="#ref-for-authentication-ceremony①⑤">(3)</a>
-    <li><a href="#ref-for-authentication-ceremony①⑥">6.2.1. Authenticator Attachment Modality</a>
-    <li><a href="#ref-for-authentication-ceremony①⑦">6.2.3. Authentication Factor Capability</a> <a href="#ref-for-authentication-ceremony①⑧">(2)</a>
-    <li><a href="#ref-for-authentication-ceremony①⑨">7. WebAuthn Relying Party Operations</a>
-    <li><a href="#ref-for-authentication-ceremony②⓪">7.1. Registering a New Credential</a>
+    <li><a href="#ref-for-authentication-ceremony">4. Terminology</a> <a href="#ref-for-authentication-ceremony①">(2)</a> <a href="#ref-for-authentication-ceremony②">(3)</a> <a href="#ref-for-authentication-ceremony③">(4)</a> <a href="#ref-for-authentication-ceremony④">(5)</a> <a href="#ref-for-authentication-ceremony⑤">(6)</a> <a href="#ref-for-authentication-ceremony⑥">(7)</a> <a href="#ref-for-authentication-ceremony⑦">(8)</a>
+    <li><a href="#ref-for-authentication-ceremony⑧">5.1. PublicKeyCredential Interface</a>
+    <li><a href="#ref-for-authentication-ceremony⑨">5.1.4.2. Issuing a Credential Request to an Authenticator</a>
+    <li><a href="#ref-for-authentication-ceremony①⓪">5.4. Options for Credential Creation (dictionary PublicKeyCredentialCreationOptions)</a> <a href="#ref-for-authentication-ceremony①①">(2)</a> <a href="#ref-for-authentication-ceremony①②">(3)</a>
+    <li><a href="#ref-for-authentication-ceremony①③">5.4.5. Authenticator Attachment Enumeration (enum AuthenticatorAttachment)</a>
+    <li><a href="#ref-for-authentication-ceremony①④">5.5. Options for Assertion Generation (dictionary PublicKeyCredentialRequestOptions)</a> <a href="#ref-for-authentication-ceremony①⑤">(2)</a> <a href="#ref-for-authentication-ceremony①⑥">(3)</a>
+    <li><a href="#ref-for-authentication-ceremony①⑦">6.2.1. Authenticator Attachment Modality</a>
+    <li><a href="#ref-for-authentication-ceremony①⑧">6.2.3. Authentication Factor Capability</a> <a href="#ref-for-authentication-ceremony①⑨">(2)</a>
+    <li><a href="#ref-for-authentication-ceremony②⓪">7. WebAuthn Relying Party Operations</a>
     <li><a href="#ref-for-authentication-ceremony②①">7.2. Verifying an Authentication Assertion</a> <a href="#ref-for-authentication-ceremony②②">(2)</a> <a href="#ref-for-authentication-ceremony②③">(3)</a> <a href="#ref-for-authentication-ceremony②④">(4)</a> <a href="#ref-for-authentication-ceremony②⑤">(5)</a> <a href="#ref-for-authentication-ceremony②⑥">(6)</a>
     <li><a href="#ref-for-authentication-ceremony②⑦">13.4.1. Security Benefits for WebAuthn Relying Parties</a>
     <li><a href="#ref-for-authentication-ceremony②⑧">13.4.4. Attestation Limitations</a> <a href="#ref-for-authentication-ceremony②⑨">(2)</a>
@@ -10696,37 +10797,37 @@ <h2 class="no-num no-ref heading settled" id="issues-index"><span class="content
     <li><a href="#ref-for-authenticator②⓪⑥">6.5.3. Attestation Types</a> <a href="#ref-for-authenticator②⓪⑦">(2)</a> <a href="#ref-for-authenticator②⓪⑧">(3)</a> <a href="#ref-for-authenticator②⓪⑨">(4)</a> <a href="#ref-for-authenticator②①⓪">(5)</a> <a href="#ref-for-authenticator②①①">(6)</a>
     <li><a href="#ref-for-authenticator②①②">6.5.4. Generating an Attestation Object</a>
     <li><a href="#ref-for-authenticator②①③">6.5.5. Signature Formats for Packed Attestation, FIDO U2F Attestation, and Assertion Signatures</a> <a href="#ref-for-authenticator②①④">(2)</a>
-    <li><a href="#ref-for-authenticator②①⑤">7.1. Registering a New Credential</a> <a href="#ref-for-authenticator②①⑥">(2)</a> <a href="#ref-for-authenticator②①⑦">(3)</a> <a href="#ref-for-authenticator②①⑧">(4)</a>
-    <li><a href="#ref-for-authenticator②①⑨">7.2. Verifying an Authentication Assertion</a>
-    <li><a href="#ref-for-authenticator②②⓪">8.2. Packed Attestation Statement Format</a>
-    <li><a href="#ref-for-authenticator②②①">8.4. Android Key Attestation Statement Format</a>
-    <li><a href="#ref-for-authenticator②②②">8.5. Android SafetyNet Attestation Statement Format</a>
-    <li><a href="#ref-for-authenticator②②③">8.7. None Attestation Statement Format</a> <a href="#ref-for-authenticator②②④">(2)</a> <a href="#ref-for-authenticator②②⑤">(3)</a>
-    <li><a href="#ref-for-authenticator②②⑥">10.1.3. Credential Properties Extension (credProps)</a>
-    <li><a href="#ref-for-authenticator②②⑦">10.1.4. Pseudo-random function extension (prf)</a> <a href="#ref-for-authenticator②②⑧">(2)</a> <a href="#ref-for-authenticator②②⑨">(3)</a> <a href="#ref-for-authenticator②③⓪">(4)</a> <a href="#ref-for-authenticator②③①">(5)</a>
-    <li><a href="#ref-for-authenticator②③②">10.1.5. Large blob storage extension (largeBlob)</a> <a href="#ref-for-authenticator②③③">(2)</a> <a href="#ref-for-authenticator②③④">(3)</a> <a href="#ref-for-authenticator②③⑤">(4)</a>
-    <li><a href="#ref-for-authenticator②③⑥">10.2.1. User Verification Method Extension (uvm)</a>
-    <li><a href="#ref-for-authenticator②③⑦">13. Security Considerations</a> <a href="#ref-for-authenticator②③⑧">(2)</a> <a href="#ref-for-authenticator②③⑨">(3)</a> <a href="#ref-for-authenticator②④⓪">(4)</a>
-    <li><a href="#ref-for-authenticator②④①">13.1. Credential ID Unsigned</a>
-    <li><a href="#ref-for-authenticator②④②">13.2. Physical Proximity between Client and Authenticator</a> <a href="#ref-for-authenticator②④③">(2)</a> <a href="#ref-for-authenticator②④④">(3)</a> <a href="#ref-for-authenticator②④⑤">(4)</a> <a href="#ref-for-authenticator②④⑥">(5)</a> <a href="#ref-for-authenticator②④⑦">(6)</a> <a href="#ref-for-authenticator②④⑧">(7)</a> <a href="#ref-for-authenticator②④⑨">(8)</a> <a href="#ref-for-authenticator②⑤⓪">(9)</a> <a href="#ref-for-authenticator②⑤①">(10)</a>
-    <li><a href="#ref-for-authenticator②⑤②">13.3. Security considerations for authenticators </a>
-    <li><a href="#ref-for-authenticator②⑤③">13.3.2. Attestation Certificate and Attestation Certificate CA Compromise</a>
-    <li><a href="#ref-for-authenticator②⑤④">13.4.1. Security Benefits for WebAuthn Relying Parties</a> <a href="#ref-for-authenticator②⑤⑤">(2)</a> <a href="#ref-for-authenticator②⑤⑥">(3)</a> <a href="#ref-for-authenticator②⑤⑦">(4)</a> <a href="#ref-for-authenticator②⑤⑧">(5)</a> <a href="#ref-for-authenticator②⑤⑨">(6)</a>
-    <li><a href="#ref-for-authenticator②⑥⓪">13.4.4. Attestation Limitations</a> <a href="#ref-for-authenticator②⑥①">(2)</a> <a href="#ref-for-authenticator②⑥②">(3)</a> <a href="#ref-for-authenticator②⑥③">(4)</a> <a href="#ref-for-authenticator②⑥④">(5)</a> <a href="#ref-for-authenticator②⑥⑤">(6)</a> <a href="#ref-for-authenticator②⑥⑥">(7)</a> <a href="#ref-for-authenticator②⑥⑦">(8)</a>
-    <li><a href="#ref-for-authenticator②⑥⑧">13.4.5. Revoked Attestation Certificates</a>
-    <li><a href="#ref-for-authenticator②⑥⑨">13.4.6. Credential Loss and Key Mobility</a> <a href="#ref-for-authenticator②⑦⓪">(2)</a> <a href="#ref-for-authenticator②⑦①">(3)</a> <a href="#ref-for-authenticator②⑦②">(4)</a> <a href="#ref-for-authenticator②⑦③">(5)</a>
-    <li><a href="#ref-for-authenticator②⑦④">14. Privacy Considerations</a>
-    <li><a href="#ref-for-authenticator②⑦⑤">14.1. De-anonymization Prevention Measures</a> <a href="#ref-for-authenticator②⑦⑥">(2)</a> <a href="#ref-for-authenticator②⑦⑦">(3)</a> <a href="#ref-for-authenticator②⑦⑧">(4)</a> <a href="#ref-for-authenticator②⑦⑨">(5)</a> <a href="#ref-for-authenticator②⑧⓪">(6)</a> <a href="#ref-for-authenticator②⑧①">(7)</a>
-    <li><a href="#ref-for-authenticator②⑧②">14.2. Anonymous, Scoped, Non-correlatable Public Key Credentials</a> <a href="#ref-for-authenticator②⑧③">(2)</a> <a href="#ref-for-authenticator②⑧④">(3)</a> <a href="#ref-for-authenticator②⑧⑤">(4)</a> <a href="#ref-for-authenticator②⑧⑥">(5)</a>
-    <li><a href="#ref-for-authenticator②⑧⑦">14.3. Authenticator-local Biometric Recognition</a>
-    <li><a href="#ref-for-authenticator②⑧⑧">14.4. Privacy considerations for authenticators</a>
-    <li><a href="#ref-for-authenticator②⑧⑨">14.4.1. Attestation Privacy</a> <a href="#ref-for-authenticator②⑨⓪">(2)</a> <a href="#ref-for-authenticator②⑨①">(3)</a> <a href="#ref-for-authenticator②⑨②">(4)</a> <a href="#ref-for-authenticator②⑨③">(5)</a>
-    <li><a href="#ref-for-authenticator②⑨④">14.4.2. Privacy of personally identifying information Stored in Authenticators</a> <a href="#ref-for-authenticator②⑨⑤">(2)</a> <a href="#ref-for-authenticator②⑨⑥">(3)</a> <a href="#ref-for-authenticator②⑨⑦">(4)</a> <a href="#ref-for-authenticator②⑨⑧">(5)</a> <a href="#ref-for-authenticator②⑨⑨">(6)</a> <a href="#ref-for-authenticator③⓪⓪">(7)</a>
-    <li><a href="#ref-for-authenticator③⓪①">14.5.1. Registration Ceremony Privacy</a> <a href="#ref-for-authenticator③⓪②">(2)</a> <a href="#ref-for-authenticator③⓪③">(3)</a> <a href="#ref-for-authenticator③⓪④">(4)</a> <a href="#ref-for-authenticator③⓪⑤">(5)</a> <a href="#ref-for-authenticator③⓪⑥">(6)</a>
-    <li><a href="#ref-for-authenticator③⓪⑦">14.6.1. User Handle Contents</a>
-    <li><a href="#ref-for-authenticator③⓪⑧">14.6.2. Username Enumeration</a>
-    <li><a href="#ref-for-authenticator③⓪⑨">14.6.3. Privacy leak via credential IDs</a> <a href="#ref-for-authenticator③①⓪">(2)</a> <a href="#ref-for-authenticator③①①">(3)</a>
-    <li><a href="#ref-for-authenticator③①②">15. Accessibility Considerations</a>
+    <li><a href="#ref-for-authenticator②①⑤">7.1. Registering a New Credential</a> <a href="#ref-for-authenticator②①⑥">(2)</a> <a href="#ref-for-authenticator②①⑦">(3)</a>
+    <li><a href="#ref-for-authenticator②①⑧">7.2. Verifying an Authentication Assertion</a>
+    <li><a href="#ref-for-authenticator②①⑨">8.2. Packed Attestation Statement Format</a>
+    <li><a href="#ref-for-authenticator②②⓪">8.4. Android Key Attestation Statement Format</a>
+    <li><a href="#ref-for-authenticator②②①">8.5. Android SafetyNet Attestation Statement Format</a>
+    <li><a href="#ref-for-authenticator②②②">8.7. None Attestation Statement Format</a> <a href="#ref-for-authenticator②②③">(2)</a> <a href="#ref-for-authenticator②②④">(3)</a>
+    <li><a href="#ref-for-authenticator②②⑤">10.1.3. Credential Properties Extension (credProps)</a>
+    <li><a href="#ref-for-authenticator②②⑥">10.1.4. Pseudo-random function extension (prf)</a> <a href="#ref-for-authenticator②②⑦">(2)</a> <a href="#ref-for-authenticator②②⑧">(3)</a> <a href="#ref-for-authenticator②②⑨">(4)</a> <a href="#ref-for-authenticator②③⓪">(5)</a>
+    <li><a href="#ref-for-authenticator②③①">10.1.5. Large blob storage extension (largeBlob)</a> <a href="#ref-for-authenticator②③②">(2)</a> <a href="#ref-for-authenticator②③③">(3)</a> <a href="#ref-for-authenticator②③④">(4)</a>
+    <li><a href="#ref-for-authenticator②③⑤">10.2.1. User Verification Method Extension (uvm)</a>
+    <li><a href="#ref-for-authenticator②③⑥">13. Security Considerations</a> <a href="#ref-for-authenticator②③⑦">(2)</a> <a href="#ref-for-authenticator②③⑧">(3)</a> <a href="#ref-for-authenticator②③⑨">(4)</a>
+    <li><a href="#ref-for-authenticator②④⓪">13.1. Credential ID Unsigned</a>
+    <li><a href="#ref-for-authenticator②④①">13.2. Physical Proximity between Client and Authenticator</a> <a href="#ref-for-authenticator②④②">(2)</a> <a href="#ref-for-authenticator②④③">(3)</a> <a href="#ref-for-authenticator②④④">(4)</a> <a href="#ref-for-authenticator②④⑤">(5)</a> <a href="#ref-for-authenticator②④⑥">(6)</a> <a href="#ref-for-authenticator②④⑦">(7)</a> <a href="#ref-for-authenticator②④⑧">(8)</a> <a href="#ref-for-authenticator②④⑨">(9)</a> <a href="#ref-for-authenticator②⑤⓪">(10)</a>
+    <li><a href="#ref-for-authenticator②⑤①">13.3. Security considerations for authenticators </a>
+    <li><a href="#ref-for-authenticator②⑤②">13.3.2. Attestation Certificate and Attestation Certificate CA Compromise</a>
+    <li><a href="#ref-for-authenticator②⑤③">13.4.1. Security Benefits for WebAuthn Relying Parties</a> <a href="#ref-for-authenticator②⑤④">(2)</a> <a href="#ref-for-authenticator②⑤⑤">(3)</a> <a href="#ref-for-authenticator②⑤⑥">(4)</a> <a href="#ref-for-authenticator②⑤⑦">(5)</a> <a href="#ref-for-authenticator②⑤⑧">(6)</a>
+    <li><a href="#ref-for-authenticator②⑤⑨">13.4.4. Attestation Limitations</a> <a href="#ref-for-authenticator②⑥⓪">(2)</a> <a href="#ref-for-authenticator②⑥①">(3)</a> <a href="#ref-for-authenticator②⑥②">(4)</a> <a href="#ref-for-authenticator②⑥③">(5)</a> <a href="#ref-for-authenticator②⑥④">(6)</a> <a href="#ref-for-authenticator②⑥⑤">(7)</a> <a href="#ref-for-authenticator②⑥⑥">(8)</a>
+    <li><a href="#ref-for-authenticator②⑥⑦">13.4.5. Revoked Attestation Certificates</a>
+    <li><a href="#ref-for-authenticator②⑥⑧">13.4.6. Credential Loss and Key Mobility</a> <a href="#ref-for-authenticator②⑥⑨">(2)</a> <a href="#ref-for-authenticator②⑦⓪">(3)</a> <a href="#ref-for-authenticator②⑦①">(4)</a> <a href="#ref-for-authenticator②⑦②">(5)</a>
+    <li><a href="#ref-for-authenticator②⑦③">14. Privacy Considerations</a>
+    <li><a href="#ref-for-authenticator②⑦④">14.1. De-anonymization Prevention Measures</a> <a href="#ref-for-authenticator②⑦⑤">(2)</a> <a href="#ref-for-authenticator②⑦⑥">(3)</a> <a href="#ref-for-authenticator②⑦⑦">(4)</a> <a href="#ref-for-authenticator②⑦⑧">(5)</a> <a href="#ref-for-authenticator②⑦⑨">(6)</a> <a href="#ref-for-authenticator②⑧⓪">(7)</a>
+    <li><a href="#ref-for-authenticator②⑧①">14.2. Anonymous, Scoped, Non-correlatable Public Key Credentials</a> <a href="#ref-for-authenticator②⑧②">(2)</a> <a href="#ref-for-authenticator②⑧③">(3)</a> <a href="#ref-for-authenticator②⑧④">(4)</a> <a href="#ref-for-authenticator②⑧⑤">(5)</a>
+    <li><a href="#ref-for-authenticator②⑧⑥">14.3. Authenticator-local Biometric Recognition</a>
+    <li><a href="#ref-for-authenticator②⑧⑦">14.4. Privacy considerations for authenticators</a>
+    <li><a href="#ref-for-authenticator②⑧⑧">14.4.1. Attestation Privacy</a> <a href="#ref-for-authenticator②⑧⑨">(2)</a> <a href="#ref-for-authenticator②⑨⓪">(3)</a> <a href="#ref-for-authenticator②⑨①">(4)</a> <a href="#ref-for-authenticator②⑨②">(5)</a>
+    <li><a href="#ref-for-authenticator②⑨③">14.4.2. Privacy of personally identifying information Stored in Authenticators</a> <a href="#ref-for-authenticator②⑨④">(2)</a> <a href="#ref-for-authenticator②⑨⑤">(3)</a> <a href="#ref-for-authenticator②⑨⑥">(4)</a> <a href="#ref-for-authenticator②⑨⑦">(5)</a> <a href="#ref-for-authenticator②⑨⑧">(6)</a> <a href="#ref-for-authenticator②⑨⑨">(7)</a>
+    <li><a href="#ref-for-authenticator③⓪⓪">14.5.1. Registration Ceremony Privacy</a> <a href="#ref-for-authenticator③⓪①">(2)</a> <a href="#ref-for-authenticator③⓪②">(3)</a> <a href="#ref-for-authenticator③⓪③">(4)</a> <a href="#ref-for-authenticator③⓪④">(5)</a> <a href="#ref-for-authenticator③⓪⑤">(6)</a>
+    <li><a href="#ref-for-authenticator③⓪⑥">14.6.1. User Handle Contents</a>
+    <li><a href="#ref-for-authenticator③⓪⑦">14.6.2. Username Enumeration</a>
+    <li><a href="#ref-for-authenticator③⓪⑧">14.6.3. Privacy leak via credential IDs</a> <a href="#ref-for-authenticator③⓪⑨">(2)</a> <a href="#ref-for-authenticator③①⓪">(3)</a>
+    <li><a href="#ref-for-authenticator③①①">15. Accessibility Considerations</a>
    </ul>
   </aside>
   <aside class="dfn-panel" data-for="webauthn-authenticator">
@@ -10857,15 +10958,15 @@ <h2 class="no-num no-ref heading settled" id="issues-index"><span class="content
    <b><a href="#ceremony">#ceremony</a></b><b>Referenced in:</b>
    <ul>
     <li><a href="#ref-for-ceremony">1. Introduction</a>
-    <li><a href="#ref-for-ceremony①">4. Terminology</a> <a href="#ref-for-ceremony②">(2)</a> <a href="#ref-for-ceremony③">(3)</a> <a href="#ref-for-ceremony④">(4)</a> <a href="#ref-for-ceremony⑤">(5)</a> <a href="#ref-for-ceremony⑥">(6)</a> <a href="#ref-for-ceremony⑦">(7)</a>
-    <li><a href="#ref-for-ceremony⑧">5.1. PublicKeyCredential Interface</a>
-    <li><a href="#ref-for-ceremony⑨">5.8.6. User Verification Requirement Enumeration (enum UserVerificationRequirement)</a>
-    <li><a href="#ref-for-ceremony①⓪">7. WebAuthn Relying Party Operations</a>
-    <li><a href="#ref-for-ceremony①①">13. Security Considerations</a>
-    <li><a href="#ref-for-ceremony①②">14.5.1. Registration Ceremony Privacy</a>
-    <li><a href="#ref-for-ceremony①③">14.5.2. Authentication Ceremony Privacy</a>
-    <li><a href="#ref-for-ceremony①④">14.6.2. Username Enumeration</a> <a href="#ref-for-ceremony①⑤">(2)</a>
-    <li><a href="#ref-for-ceremony①⑥">15. Accessibility Considerations</a>
+    <li><a href="#ref-for-ceremony①">4. Terminology</a> <a href="#ref-for-ceremony②">(2)</a> <a href="#ref-for-ceremony③">(3)</a> <a href="#ref-for-ceremony④">(4)</a> <a href="#ref-for-ceremony⑤">(5)</a> <a href="#ref-for-ceremony⑥">(6)</a> <a href="#ref-for-ceremony⑦">(7)</a> <a href="#ref-for-ceremony⑧">(8)</a> <a href="#ref-for-ceremony⑨">(9)</a>
+    <li><a href="#ref-for-ceremony①⓪">5.1. PublicKeyCredential Interface</a>
+    <li><a href="#ref-for-ceremony①①">5.8.6. User Verification Requirement Enumeration (enum UserVerificationRequirement)</a>
+    <li><a href="#ref-for-ceremony①②">7. WebAuthn Relying Party Operations</a>
+    <li><a href="#ref-for-ceremony①③">13. Security Considerations</a>
+    <li><a href="#ref-for-ceremony①④">14.5.1. Registration Ceremony Privacy</a>
+    <li><a href="#ref-for-ceremony①⑤">14.5.2. Authentication Ceremony Privacy</a>
+    <li><a href="#ref-for-ceremony①⑥">14.6.2. Username Enumeration</a> <a href="#ref-for-ceremony①⑦">(2)</a>
+    <li><a href="#ref-for-ceremony①⑧">15. Accessibility Considerations</a>
    </ul>
   </aside>
   <aside class="dfn-panel" data-for="client">
@@ -10901,21 +11002,21 @@ <h2 class="no-num no-ref heading settled" id="issues-index"><span class="content
     <li><a href="#ref-for-client⑦④">6.2.2. Credential Storage Modality</a>
     <li><a href="#ref-for-client⑦⑤">6.3.2. The authenticatorMakeCredential Operation</a> <a href="#ref-for-client⑦⑥">(2)</a> <a href="#ref-for-client⑦⑦">(3)</a> <a href="#ref-for-client⑦⑧">(4)</a>
     <li><a href="#ref-for-client⑦⑨">6.3.5. The silentCredentialDiscovery operation</a>
-    <li><a href="#ref-for-client⑧⓪">7.1. Registering a New Credential</a> <a href="#ref-for-client⑧①">(2)</a>
-    <li><a href="#ref-for-client⑧②">7.2. Verifying an Authentication Assertion</a>
-    <li><a href="#ref-for-client⑧③">8.6. FIDO U2F Attestation Statement Format</a>
-    <li><a href="#ref-for-client⑧④">9. WebAuthn Extensions</a> <a href="#ref-for-client⑧⑤">(2)</a>
-    <li><a href="#ref-for-client⑧⑥">9.4. Client Extension Processing</a>
-    <li><a href="#ref-for-client⑧⑦">10.1.3. Credential Properties Extension (credProps)</a>
-    <li><a href="#ref-for-client⑧⑧">12.4. WebAuthn Extension Identifier Registrations</a>
-    <li><a href="#ref-for-client⑧⑨">13. Security Considerations</a>
-    <li><a href="#ref-for-client⑨⓪">13.2. Physical Proximity between Client and Authenticator</a> <a href="#ref-for-client⑨①">(2)</a> <a href="#ref-for-client⑨②">(3)</a> <a href="#ref-for-client⑨③">(4)</a> <a href="#ref-for-client⑨④">(5)</a> <a href="#ref-for-client⑨⑤">(6)</a> <a href="#ref-for-client⑨⑥">(7)</a> <a href="#ref-for-client⑨⑦">(8)</a>
-    <li><a href="#ref-for-client⑨⑧">14. Privacy Considerations</a>
-    <li><a href="#ref-for-client⑨⑨">14.1. De-anonymization Prevention Measures</a> <a href="#ref-for-client①⓪⓪">(2)</a> <a href="#ref-for-client①⓪①">(3)</a> <a href="#ref-for-client①⓪②">(4)</a> <a href="#ref-for-client①⓪③">(5)</a>
-    <li><a href="#ref-for-client①⓪④">14.2. Anonymous, Scoped, Non-correlatable Public Key Credentials</a> <a href="#ref-for-client①⓪⑤">(2)</a> <a href="#ref-for-client①⓪⑥">(3)</a>
-    <li><a href="#ref-for-client①⓪⑦">14.3. Authenticator-local Biometric Recognition</a>
-    <li><a href="#ref-for-client①⓪⑧">14.4.2. Privacy of personally identifying information Stored in Authenticators</a> <a href="#ref-for-client①⓪⑨">(2)</a>
-    <li><a href="#ref-for-client①①⓪">14.5. Privacy considerations for clients</a>
+    <li><a href="#ref-for-client⑧⓪">7.1. Registering a New Credential</a>
+    <li><a href="#ref-for-client⑧①">7.2. Verifying an Authentication Assertion</a>
+    <li><a href="#ref-for-client⑧②">8.6. FIDO U2F Attestation Statement Format</a>
+    <li><a href="#ref-for-client⑧③">9. WebAuthn Extensions</a> <a href="#ref-for-client⑧④">(2)</a>
+    <li><a href="#ref-for-client⑧⑤">9.4. Client Extension Processing</a>
+    <li><a href="#ref-for-client⑧⑥">10.1.3. Credential Properties Extension (credProps)</a>
+    <li><a href="#ref-for-client⑧⑦">12.4. WebAuthn Extension Identifier Registrations</a>
+    <li><a href="#ref-for-client⑧⑧">13. Security Considerations</a>
+    <li><a href="#ref-for-client⑧⑨">13.2. Physical Proximity between Client and Authenticator</a> <a href="#ref-for-client⑨⓪">(2)</a> <a href="#ref-for-client⑨①">(3)</a> <a href="#ref-for-client⑨②">(4)</a> <a href="#ref-for-client⑨③">(5)</a> <a href="#ref-for-client⑨④">(6)</a> <a href="#ref-for-client⑨⑤">(7)</a> <a href="#ref-for-client⑨⑥">(8)</a>
+    <li><a href="#ref-for-client⑨⑦">14. Privacy Considerations</a>
+    <li><a href="#ref-for-client⑨⑧">14.1. De-anonymization Prevention Measures</a> <a href="#ref-for-client⑨⑨">(2)</a> <a href="#ref-for-client①⓪⓪">(3)</a> <a href="#ref-for-client①⓪①">(4)</a> <a href="#ref-for-client①⓪②">(5)</a>
+    <li><a href="#ref-for-client①⓪③">14.2. Anonymous, Scoped, Non-correlatable Public Key Credentials</a> <a href="#ref-for-client①⓪④">(2)</a> <a href="#ref-for-client①⓪⑤">(3)</a>
+    <li><a href="#ref-for-client①⓪⑥">14.3. Authenticator-local Biometric Recognition</a>
+    <li><a href="#ref-for-client①⓪⑦">14.4.2. Privacy of personally identifying information Stored in Authenticators</a> <a href="#ref-for-client①⓪⑧">(2)</a>
+    <li><a href="#ref-for-client①⓪⑨">14.5. Privacy considerations for clients</a>
    </ul>
   </aside>
   <aside class="dfn-panel" data-for="webauthn-client">
@@ -11058,27 +11159,27 @@ <h2 class="no-num no-ref heading settled" id="issues-index"><span class="content
    <ul>
     <li><a href="#ref-for-credential-id">1.3.1. Registration</a>
     <li><a href="#ref-for-credential-id①">1.3.3. Authentication</a> <a href="#ref-for-credential-id②">(2)</a> <a href="#ref-for-credential-id③">(3)</a>
-    <li><a href="#ref-for-credential-id④">4. Terminology</a> <a href="#ref-for-credential-id⑤">(2)</a> <a href="#ref-for-credential-id⑥">(3)</a> <a href="#ref-for-credential-id⑦">(4)</a> <a href="#ref-for-credential-id⑧">(5)</a> <a href="#ref-for-credential-id⑨">(6)</a> <a href="#ref-for-credential-id①⓪">(7)</a> <a href="#ref-for-credential-id①①">(8)</a> <a href="#ref-for-credential-id①②">(9)</a> <a href="#ref-for-credential-id①③">(10)</a> <a href="#ref-for-credential-id①④">(11)</a> <a href="#ref-for-credential-id①⑤">(12)</a> <a href="#ref-for-credential-id①⑥">(13)</a>
-    <li><a href="#ref-for-credential-id①⑦">5.1. PublicKeyCredential Interface</a> <a href="#ref-for-credential-id①⑧">(2)</a>
-    <li><a href="#ref-for-credential-id①⑨">5.1.4.1. PublicKeyCredential’s [[DiscoverFromExternalSource]](origin, options, sameOriginWithAncestors) Method</a>
-    <li><a href="#ref-for-credential-id②⓪">5.1.4.2. Issuing a Credential Request to an Authenticator</a>
-    <li><a href="#ref-for-credential-id②①">5.2.1. Information About Public Key Credential (interface AuthenticatorAttestationResponse)</a>
-    <li><a href="#ref-for-credential-id②②">5.8.3. Credential Descriptor (dictionary PublicKeyCredentialDescriptor)</a>
-    <li><a href="#ref-for-credential-id②③">6.2.2. Credential Storage Modality</a> <a href="#ref-for-credential-id②④">(2)</a> <a href="#ref-for-credential-id②⑤">(3)</a>
-    <li><a href="#ref-for-credential-id②⑥">6.3.1. Lookup Credential Source by Credential ID Algorithm</a>
-    <li><a href="#ref-for-credential-id②⑦">6.3.2. The authenticatorMakeCredential Operation</a>
-    <li><a href="#ref-for-credential-id②⑧">6.3.3. The authenticatorGetAssertion Operation</a>
-    <li><a href="#ref-for-credential-id②⑨">6.3.5. The silentCredentialDiscovery operation</a>
-    <li><a href="#ref-for-credential-id③⓪">6.5.1. Attested Credential Data</a>
-    <li><a href="#ref-for-credential-id③①">7.1. Registering a New Credential</a> <a href="#ref-for-credential-id③②">(2)</a> <a href="#ref-for-credential-id③③">(3)</a> <a href="#ref-for-credential-id③④">(4)</a>
-    <li><a href="#ref-for-credential-id③⑤">8.6. FIDO U2F Attestation Statement Format</a>
-    <li><a href="#ref-for-credential-id③⑥">10.1.1. FIDO AppID Extension (appid)</a>
-    <li><a href="#ref-for-credential-id③⑦">10.1.2. FIDO AppID Exclusion Extension (appidExclude)</a>
-    <li><a href="#ref-for-credential-id③⑧">10.1.4. Pseudo-random function extension (prf)</a> <a href="#ref-for-credential-id③⑨">(2)</a>
-    <li><a href="#ref-for-credential-id④⓪">13.1. Credential ID Unsigned</a> <a href="#ref-for-credential-id④①">(2)</a> <a href="#ref-for-credential-id④②">(3)</a>
-    <li><a href="#ref-for-credential-id④③">14.1. De-anonymization Prevention Measures</a>
-    <li><a href="#ref-for-credential-id④④">14.2. Anonymous, Scoped, Non-correlatable Public Key Credentials</a> <a href="#ref-for-credential-id④⑤">(2)</a> <a href="#ref-for-credential-id④⑥">(3)</a>
-    <li><a href="#ref-for-credential-id④⑦">14.6.3. Privacy leak via credential IDs</a> <a href="#ref-for-credential-id④⑧">(2)</a> <a href="#ref-for-credential-id④⑨">(3)</a> <a href="#ref-for-credential-id⑤⓪">(4)</a> <a href="#ref-for-credential-id⑤①">(5)</a> <a href="#ref-for-credential-id⑤②">(6)</a> <a href="#ref-for-credential-id⑤③">(7)</a>
+    <li><a href="#ref-for-credential-id④">4. Terminology</a> <a href="#ref-for-credential-id⑤">(2)</a> <a href="#ref-for-credential-id⑥">(3)</a> <a href="#ref-for-credential-id⑦">(4)</a> <a href="#ref-for-credential-id⑧">(5)</a> <a href="#ref-for-credential-id⑨">(6)</a> <a href="#ref-for-credential-id①⓪">(7)</a> <a href="#ref-for-credential-id①①">(8)</a> <a href="#ref-for-credential-id①②">(9)</a> <a href="#ref-for-credential-id①③">(10)</a> <a href="#ref-for-credential-id①④">(11)</a> <a href="#ref-for-credential-id①⑤">(12)</a> <a href="#ref-for-credential-id①⑥">(13)</a> <a href="#ref-for-credential-id①⑦">(14)</a>
+    <li><a href="#ref-for-credential-id①⑧">5.1. PublicKeyCredential Interface</a> <a href="#ref-for-credential-id①⑨">(2)</a>
+    <li><a href="#ref-for-credential-id②⓪">5.1.4.1. PublicKeyCredential’s [[DiscoverFromExternalSource]](origin, options, sameOriginWithAncestors) Method</a>
+    <li><a href="#ref-for-credential-id②①">5.1.4.2. Issuing a Credential Request to an Authenticator</a>
+    <li><a href="#ref-for-credential-id②②">5.2.1. Information About Public Key Credential (interface AuthenticatorAttestationResponse)</a>
+    <li><a href="#ref-for-credential-id②③">5.8.3. Credential Descriptor (dictionary PublicKeyCredentialDescriptor)</a>
+    <li><a href="#ref-for-credential-id②④">6.2.2. Credential Storage Modality</a> <a href="#ref-for-credential-id②⑤">(2)</a> <a href="#ref-for-credential-id②⑥">(3)</a>
+    <li><a href="#ref-for-credential-id②⑦">6.3.1. Lookup Credential Source by Credential ID Algorithm</a>
+    <li><a href="#ref-for-credential-id②⑧">6.3.2. The authenticatorMakeCredential Operation</a>
+    <li><a href="#ref-for-credential-id②⑨">6.3.3. The authenticatorGetAssertion Operation</a>
+    <li><a href="#ref-for-credential-id③⓪">6.3.5. The silentCredentialDiscovery operation</a>
+    <li><a href="#ref-for-credential-id③①">6.5.1. Attested Credential Data</a>
+    <li><a href="#ref-for-credential-id③②">7.1. Registering a New Credential</a> <a href="#ref-for-credential-id③③">(2)</a> <a href="#ref-for-credential-id③④">(3)</a> <a href="#ref-for-credential-id③⑤">(4)</a>
+    <li><a href="#ref-for-credential-id③⑥">8.6. FIDO U2F Attestation Statement Format</a>
+    <li><a href="#ref-for-credential-id③⑦">10.1.1. FIDO AppID Extension (appid)</a>
+    <li><a href="#ref-for-credential-id③⑧">10.1.2. FIDO AppID Exclusion Extension (appidExclude)</a>
+    <li><a href="#ref-for-credential-id③⑨">10.1.4. Pseudo-random function extension (prf)</a> <a href="#ref-for-credential-id④⓪">(2)</a>
+    <li><a href="#ref-for-credential-id④①">13.1. Credential ID Unsigned</a> <a href="#ref-for-credential-id④②">(2)</a> <a href="#ref-for-credential-id④③">(3)</a>
+    <li><a href="#ref-for-credential-id④④">14.1. De-anonymization Prevention Measures</a>
+    <li><a href="#ref-for-credential-id④⑤">14.2. Anonymous, Scoped, Non-correlatable Public Key Credentials</a> <a href="#ref-for-credential-id④⑥">(2)</a> <a href="#ref-for-credential-id④⑦">(3)</a>
+    <li><a href="#ref-for-credential-id④⑧">14.6.3. Privacy leak via credential IDs</a> <a href="#ref-for-credential-id④⑨">(2)</a> <a href="#ref-for-credential-id⑤⓪">(3)</a> <a href="#ref-for-credential-id⑤①">(4)</a> <a href="#ref-for-credential-id⑤②">(5)</a> <a href="#ref-for-credential-id⑤③">(6)</a> <a href="#ref-for-credential-id⑤④">(7)</a>
    </ul>
   </aside>
   <aside class="dfn-panel" data-for="credential-key-pair">
@@ -11110,15 +11211,14 @@ <h2 class="no-num no-ref heading settled" id="issues-index"><span class="content
    <b><a href="#credential-public-key">#credential-public-key</a></b><b>Referenced in:</b>
    <ul>
     <li><a href="#ref-for-credential-public-key">1.3.1. Registration</a> <a href="#ref-for-credential-public-key①">(2)</a>
-    <li><a href="#ref-for-credential-public-key②">4. Terminology</a> <a href="#ref-for-credential-public-key③">(2)</a> <a href="#ref-for-credential-public-key④">(3)</a> <a href="#ref-for-credential-public-key⑤">(4)</a> <a href="#ref-for-credential-public-key⑥">(5)</a> <a href="#ref-for-credential-public-key⑦">(6)</a> <a href="#ref-for-credential-public-key⑧">(7)</a> <a href="#ref-for-credential-public-key⑨">(8)</a> <a href="#ref-for-credential-public-key①⓪">(9)</a> <a href="#ref-for-credential-public-key①①">(10)</a>
-    <li><a href="#ref-for-credential-public-key①②">5.2.1. Information About Public Key Credential (interface AuthenticatorAttestationResponse)</a>
-    <li><a href="#ref-for-credential-public-key①③">5.2.1.1. Easily accessing credential data</a> <a href="#ref-for-credential-public-key①④">(2)</a> <a href="#ref-for-credential-public-key①⑤">(3)</a> <a href="#ref-for-credential-public-key①⑥">(4)</a> <a href="#ref-for-credential-public-key①⑦">(5)</a> <a href="#ref-for-credential-public-key①⑧">(6)</a> <a href="#ref-for-credential-public-key①⑨">(7)</a> <a href="#ref-for-credential-public-key②⓪">(8)</a>
-    <li><a href="#ref-for-credential-public-key②①">5.8.5. Cryptographic Algorithm Identifier (typedef COSEAlgorithmIdentifier)</a>
-    <li><a href="#ref-for-credential-public-key②②">6. WebAuthn Authenticator Model</a>
-    <li><a href="#ref-for-credential-public-key②③">6.5. Attestation</a> <a href="#ref-for-credential-public-key②④">(2)</a> <a href="#ref-for-credential-public-key②⑤">(3)</a>
-    <li><a href="#ref-for-credential-public-key②⑥">6.5.1. Attested Credential Data</a> <a href="#ref-for-credential-public-key②⑦">(2)</a> <a href="#ref-for-credential-public-key②⑧">(3)</a>
-    <li><a href="#ref-for-credential-public-key②⑨">7.1. Registering a New Credential</a>
-    <li><a href="#ref-for-credential-public-key③⓪">7.2. Verifying an Authentication Assertion</a> <a href="#ref-for-credential-public-key③①">(2)</a>
+    <li><a href="#ref-for-credential-public-key②">4. Terminology</a> <a href="#ref-for-credential-public-key③">(2)</a> <a href="#ref-for-credential-public-key④">(3)</a> <a href="#ref-for-credential-public-key⑤">(4)</a> <a href="#ref-for-credential-public-key⑥">(5)</a> <a href="#ref-for-credential-public-key⑦">(6)</a> <a href="#ref-for-credential-public-key⑧">(7)</a> <a href="#ref-for-credential-public-key⑨">(8)</a> <a href="#ref-for-credential-public-key①⓪">(9)</a> <a href="#ref-for-credential-public-key①①">(10)</a> <a href="#ref-for-credential-public-key①②">(11)</a>
+    <li><a href="#ref-for-credential-public-key①③">5.2.1. Information About Public Key Credential (interface AuthenticatorAttestationResponse)</a>
+    <li><a href="#ref-for-credential-public-key①④">5.2.1.1. Easily accessing credential data</a> <a href="#ref-for-credential-public-key①⑤">(2)</a> <a href="#ref-for-credential-public-key①⑥">(3)</a> <a href="#ref-for-credential-public-key①⑦">(4)</a> <a href="#ref-for-credential-public-key①⑧">(5)</a> <a href="#ref-for-credential-public-key①⑨">(6)</a> <a href="#ref-for-credential-public-key②⓪">(7)</a> <a href="#ref-for-credential-public-key②①">(8)</a>
+    <li><a href="#ref-for-credential-public-key②②">5.8.5. Cryptographic Algorithm Identifier (typedef COSEAlgorithmIdentifier)</a>
+    <li><a href="#ref-for-credential-public-key②③">6. WebAuthn Authenticator Model</a>
+    <li><a href="#ref-for-credential-public-key②④">6.5. Attestation</a> <a href="#ref-for-credential-public-key②⑤">(2)</a> <a href="#ref-for-credential-public-key②⑥">(3)</a>
+    <li><a href="#ref-for-credential-public-key②⑦">6.5.1. Attested Credential Data</a> <a href="#ref-for-credential-public-key②⑧">(2)</a> <a href="#ref-for-credential-public-key②⑨">(3)</a>
+    <li><a href="#ref-for-credential-public-key③⓪">7.1. Registering a New Credential</a> <a href="#ref-for-credential-public-key③①">(2)</a>
     <li><a href="#ref-for-credential-public-key③②">8.6. FIDO U2F Attestation Statement Format</a>
     <li><a href="#ref-for-credential-public-key③③">8.8. Apple Anonymous Attestation Statement Format</a> <a href="#ref-for-credential-public-key③④">(2)</a>
     <li><a href="#ref-for-credential-public-key③⑤">13.1. Credential ID Unsigned</a>
@@ -11141,6 +11241,84 @@ <h2 class="no-num no-ref heading settled" id="issues-index"><span class="content
     <li><a href="#ref-for-credential-properties②">10.1.3. Credential Properties Extension (credProps)</a> <a href="#ref-for-credential-properties③">(2)</a>
    </ul>
   </aside>
+  <aside class="dfn-panel" data-for="credential-record">
+   <b><a href="#credential-record">#credential-record</a></b><b>Referenced in:</b>
+   <ul>
+    <li><a href="#ref-for-credential-record">4. Terminology</a> <a href="#ref-for-credential-record①">(2)</a> <a href="#ref-for-credential-record②">(3)</a> <a href="#ref-for-credential-record③">(4)</a> <a href="#ref-for-credential-record④">(5)</a>
+    <li><a href="#ref-for-credential-record⑤">5.5. Options for Assertion Generation (dictionary PublicKeyCredentialRequestOptions)</a>
+    <li><a href="#ref-for-credential-record⑥">7.1. Registering a New Credential</a> <a href="#ref-for-credential-record⑦">(2)</a>
+    <li><a href="#ref-for-credential-record⑧">7.2. Verifying an Authentication Assertion</a> <a href="#ref-for-credential-record⑨">(2)</a> <a href="#ref-for-credential-record①⓪">(3)</a> <a href="#ref-for-credential-record①①">(4)</a> <a href="#ref-for-credential-record①②">(5)</a>
+   </ul>
+  </aside>
+  <aside class="dfn-panel" data-for="credential-record-type">
+   <b><a href="#credential-record-type">#credential-record-type</a></b><b>Referenced in:</b>
+   <ul>
+    <li><a href="#ref-for-credential-record-type">4. Terminology</a>
+    <li><a href="#ref-for-credential-record-type①">7.1. Registering a New Credential</a>
+   </ul>
+  </aside>
+  <aside class="dfn-panel" data-for="credential-record-id">
+   <b><a href="#credential-record-id">#credential-record-id</a></b><b>Referenced in:</b>
+   <ul>
+    <li><a href="#ref-for-credential-record-id">4. Terminology</a>
+    <li><a href="#ref-for-credential-record-id①">7.1. Registering a New Credential</a>
+    <li><a href="#ref-for-credential-record-id②">7.2. Verifying an Authentication Assertion</a> <a href="#ref-for-credential-record-id③">(2)</a>
+   </ul>
+  </aside>
+  <aside class="dfn-panel" data-for="credential-record-publickey">
+   <b><a href="#credential-record-publickey">#credential-record-publickey</a></b><b>Referenced in:</b>
+   <ul>
+    <li><a href="#ref-for-credential-record-publickey">7.1. Registering a New Credential</a>
+    <li><a href="#ref-for-credential-record-publickey①">7.2. Verifying an Authentication Assertion</a>
+   </ul>
+  </aside>
+  <aside class="dfn-panel" data-for="credential-record-signcount">
+   <b><a href="#credential-record-signcount">#credential-record-signcount</a></b><b>Referenced in:</b>
+   <ul>
+    <li><a href="#ref-for-credential-record-signcount">7.1. Registering a New Credential</a>
+    <li><a href="#ref-for-credential-record-signcount①">7.2. Verifying an Authentication Assertion</a> <a href="#ref-for-credential-record-signcount②">(2)</a> <a href="#ref-for-credential-record-signcount③">(3)</a> <a href="#ref-for-credential-record-signcount④">(4)</a> <a href="#ref-for-credential-record-signcount⑤">(5)</a>
+   </ul>
+  </aside>
+  <aside class="dfn-panel" data-for="credential-record-transports">
+   <b><a href="#credential-record-transports">#credential-record-transports</a></b><b>Referenced in:</b>
+   <ul>
+    <li><a href="#ref-for-credential-record-transports">4. Terminology</a>
+    <li><a href="#ref-for-credential-record-transports①">7.1. Registering a New Credential</a>
+   </ul>
+  </aside>
+  <aside class="dfn-panel" data-for="credential-record-be">
+   <b><a href="#credential-record-be">#credential-record-be</a></b><b>Referenced in:</b>
+   <ul>
+    <li><a href="#ref-for-credential-record-be">7.1. Registering a New Credential</a>
+    <li><a href="#ref-for-credential-record-be①">7.2. Verifying an Authentication Assertion</a>
+   </ul>
+  </aside>
+  <aside class="dfn-panel" data-for="credential-record-bs">
+   <b><a href="#credential-record-bs">#credential-record-bs</a></b><b>Referenced in:</b>
+   <ul>
+    <li><a href="#ref-for-credential-record-bs">7.1. Registering a New Credential</a>
+    <li><a href="#ref-for-credential-record-bs①">7.2. Verifying an Authentication Assertion</a> <a href="#ref-for-credential-record-bs②">(2)</a>
+   </ul>
+  </aside>
+  <aside class="dfn-panel" data-for="credential-record-attestationobject">
+   <b><a href="#credential-record-attestationobject">#credential-record-attestationobject</a></b><b>Referenced in:</b>
+   <ul>
+    <li><a href="#ref-for-credential-record-attestationobject">4. Terminology</a>
+    <li><a href="#ref-for-credential-record-attestationobject①">7.1. Registering a New Credential</a>
+   </ul>
+  </aside>
+  <aside class="dfn-panel" data-for="credential-record-attestationclientdatajson">
+   <b><a href="#credential-record-attestationclientdatajson">#credential-record-attestationclientdatajson</a></b><b>Referenced in:</b>
+   <ul>
+    <li><a href="#ref-for-credential-record-attestationclientdatajson">7.1. Registering a New Credential</a>
+   </ul>
+  </aside>
+  <aside class="dfn-panel" data-for="credential-descriptor-for-a-credential-record">
+   <b><a href="#credential-descriptor-for-a-credential-record">#credential-descriptor-for-a-credential-record</a></b><b>Referenced in:</b>
+   <ul>
+    <li><a href="#ref-for-credential-descriptor-for-a-credential-record">5.5. Options for Assertion Generation (dictionary PublicKeyCredentialRequestOptions)</a>
+   </ul>
+  </aside>
   <aside class="dfn-panel" data-for="generating-authenticator">
    <b><a href="#generating-authenticator">#generating-authenticator</a></b><b>Referenced in:</b>
    <ul>
@@ -11208,31 +11386,31 @@ <h2 class="no-num no-ref heading settled" id="issues-index"><span class="content
   <aside class="dfn-panel" data-for="public-key-credential-source">
    <b><a href="#public-key-credential-source">#public-key-credential-source</a></b><b>Referenced in:</b>
    <ul>
-    <li><a href="#ref-for-public-key-credential-source">4. Terminology</a> <a href="#ref-for-public-key-credential-source①">(2)</a> <a href="#ref-for-public-key-credential-source②">(3)</a> <a href="#ref-for-public-key-credential-source③">(4)</a> <a href="#ref-for-public-key-credential-source④">(5)</a> <a href="#ref-for-public-key-credential-source⑤">(6)</a> <a href="#ref-for-public-key-credential-source⑥">(7)</a> <a href="#ref-for-public-key-credential-source⑦">(8)</a> <a href="#ref-for-public-key-credential-source⑧">(9)</a> <a href="#ref-for-public-key-credential-source⑨">(10)</a> <a href="#ref-for-public-key-credential-source①⓪">(11)</a> <a href="#ref-for-public-key-credential-source①①">(12)</a> <a href="#ref-for-public-key-credential-source①②">(13)</a> <a href="#ref-for-public-key-credential-source①③">(14)</a> <a href="#ref-for-public-key-credential-source①④">(15)</a> <a href="#ref-for-public-key-credential-source①⑤">(16)</a> <a href="#ref-for-public-key-credential-source①⑥">(17)</a> <a href="#ref-for-public-key-credential-source①⑦">(18)</a> <a href="#ref-for-public-key-credential-source①⑧">(19)</a> <a href="#ref-for-public-key-credential-source①⑨">(20)</a> <a href="#ref-for-public-key-credential-source②⓪">(21)</a> <a href="#ref-for-public-key-credential-source②①">(22)</a> <a href="#ref-for-public-key-credential-source②②">(23)</a> <a href="#ref-for-public-key-credential-source②③">(24)</a> <a href="#ref-for-public-key-credential-source②④">(25)</a> <a href="#ref-for-public-key-credential-source②⑤">(26)</a> <a href="#ref-for-public-key-credential-source②⑥">(27)</a>
-    <li><a href="#ref-for-public-key-credential-source②⑦">5.1.3. Create a New Credential - PublicKeyCredential’s [[Create]](origin, options, sameOriginWithAncestors) Method</a>
-    <li><a href="#ref-for-public-key-credential-source②⑧">5.1.4. Use an Existing Credential to Make an Assertion - PublicKeyCredential’s [[Get]](options) Method</a> <a href="#ref-for-public-key-credential-source②⑨">(2)</a> <a href="#ref-for-public-key-credential-source③⓪">(3)</a> <a href="#ref-for-public-key-credential-source③①">(4)</a> <a href="#ref-for-public-key-credential-source③②">(5)</a>
-    <li><a href="#ref-for-public-key-credential-source③③">6. WebAuthn Authenticator Model</a>
-    <li><a href="#ref-for-public-key-credential-source③④">6.1. Authenticator Data</a> <a href="#ref-for-public-key-credential-source③⑤">(2)</a> <a href="#ref-for-public-key-credential-source③⑥">(3)</a> <a href="#ref-for-public-key-credential-source③⑦">(4)</a>
-    <li><a href="#ref-for-public-key-credential-source③⑧">6.1.3. Credential Backup State</a>
-    <li><a href="#ref-for-public-key-credential-source③⑨">6.2.2. Credential Storage Modality</a> <a href="#ref-for-public-key-credential-source④⓪">(2)</a>
-    <li><a href="#ref-for-public-key-credential-source④①">6.3.1. Lookup Credential Source by Credential ID Algorithm</a> <a href="#ref-for-public-key-credential-source④②">(2)</a>
-    <li><a href="#ref-for-public-key-credential-source④③">6.3.2. The authenticatorMakeCredential Operation</a>
-    <li><a href="#ref-for-public-key-credential-source④④">6.3.3. The authenticatorGetAssertion Operation</a> <a href="#ref-for-public-key-credential-source④⑤">(2)</a>
-    <li><a href="#ref-for-public-key-credential-source④⑥">6.3.5. The silentCredentialDiscovery operation</a>
-    <li><a href="#ref-for-public-key-credential-source④⑦">7.2. Verifying an Authentication Assertion</a>
-    <li><a href="#ref-for-public-key-credential-source④⑧">10.1.3. Credential Properties Extension (credProps)</a>
-    <li><a href="#ref-for-public-key-credential-source④⑨">11.5. Add Credential</a> <a href="#ref-for-public-key-credential-source⑤⓪">(2)</a> <a href="#ref-for-public-key-credential-source⑤①">(3)</a>
-    <li><a href="#ref-for-public-key-credential-source⑤②">11.6. Get Credentials</a> <a href="#ref-for-public-key-credential-source⑤③">(2)</a>
-    <li><a href="#ref-for-public-key-credential-source⑤④">11.7. Remove Credential</a> <a href="#ref-for-public-key-credential-source⑤⑤">(2)</a> <a href="#ref-for-public-key-credential-source⑤⑥">(3)</a>
-    <li><a href="#ref-for-public-key-credential-source⑤⑦">11.8. Remove All Credentials</a> <a href="#ref-for-public-key-credential-source⑤⑧">(2)</a>
+    <li><a href="#ref-for-public-key-credential-source">4. Terminology</a> <a href="#ref-for-public-key-credential-source①">(2)</a> <a href="#ref-for-public-key-credential-source②">(3)</a> <a href="#ref-for-public-key-credential-source③">(4)</a> <a href="#ref-for-public-key-credential-source④">(5)</a> <a href="#ref-for-public-key-credential-source⑤">(6)</a> <a href="#ref-for-public-key-credential-source⑥">(7)</a> <a href="#ref-for-public-key-credential-source⑦">(8)</a> <a href="#ref-for-public-key-credential-source⑧">(9)</a> <a href="#ref-for-public-key-credential-source⑨">(10)</a> <a href="#ref-for-public-key-credential-source①⓪">(11)</a> <a href="#ref-for-public-key-credential-source①①">(12)</a> <a href="#ref-for-public-key-credential-source①②">(13)</a> <a href="#ref-for-public-key-credential-source①③">(14)</a> <a href="#ref-for-public-key-credential-source①④">(15)</a> <a href="#ref-for-public-key-credential-source①⑤">(16)</a> <a href="#ref-for-public-key-credential-source①⑥">(17)</a> <a href="#ref-for-public-key-credential-source①⑦">(18)</a> <a href="#ref-for-public-key-credential-source①⑧">(19)</a> <a href="#ref-for-public-key-credential-source①⑨">(20)</a> <a href="#ref-for-public-key-credential-source②⓪">(21)</a> <a href="#ref-for-public-key-credential-source②①">(22)</a> <a href="#ref-for-public-key-credential-source②②">(23)</a> <a href="#ref-for-public-key-credential-source②③">(24)</a> <a href="#ref-for-public-key-credential-source②④">(25)</a> <a href="#ref-for-public-key-credential-source②⑤">(26)</a> <a href="#ref-for-public-key-credential-source②⑥">(27)</a> <a href="#ref-for-public-key-credential-source②⑦">(28)</a> <a href="#ref-for-public-key-credential-source②⑧">(29)</a> <a href="#ref-for-public-key-credential-source②⑨">(30)</a> <a href="#ref-for-public-key-credential-source③⓪">(31)</a> <a href="#ref-for-public-key-credential-source③①">(32)</a> <a href="#ref-for-public-key-credential-source③②">(33)</a> <a href="#ref-for-public-key-credential-source③③">(34)</a> <a href="#ref-for-public-key-credential-source③④">(35)</a> <a href="#ref-for-public-key-credential-source③⑤">(36)</a> <a href="#ref-for-public-key-credential-source③⑥">(37)</a>
+    <li><a href="#ref-for-public-key-credential-source③⑦">5.1.3. Create a New Credential - PublicKeyCredential’s [[Create]](origin, options, sameOriginWithAncestors) Method</a>
+    <li><a href="#ref-for-public-key-credential-source③⑧">5.1.4. Use an Existing Credential to Make an Assertion - PublicKeyCredential’s [[Get]](options) Method</a> <a href="#ref-for-public-key-credential-source③⑨">(2)</a> <a href="#ref-for-public-key-credential-source④⓪">(3)</a> <a href="#ref-for-public-key-credential-source④①">(4)</a> <a href="#ref-for-public-key-credential-source④②">(5)</a>
+    <li><a href="#ref-for-public-key-credential-source④③">6. WebAuthn Authenticator Model</a>
+    <li><a href="#ref-for-public-key-credential-source④④">6.1. Authenticator Data</a> <a href="#ref-for-public-key-credential-source④⑤">(2)</a> <a href="#ref-for-public-key-credential-source④⑥">(3)</a> <a href="#ref-for-public-key-credential-source④⑦">(4)</a>
+    <li><a href="#ref-for-public-key-credential-source④⑧">6.1.3. Credential Backup State</a>
+    <li><a href="#ref-for-public-key-credential-source④⑨">6.2.2. Credential Storage Modality</a> <a href="#ref-for-public-key-credential-source⑤⓪">(2)</a>
+    <li><a href="#ref-for-public-key-credential-source⑤①">6.3.1. Lookup Credential Source by Credential ID Algorithm</a> <a href="#ref-for-public-key-credential-source⑤②">(2)</a>
+    <li><a href="#ref-for-public-key-credential-source⑤③">6.3.2. The authenticatorMakeCredential Operation</a>
+    <li><a href="#ref-for-public-key-credential-source⑤④">6.3.3. The authenticatorGetAssertion Operation</a> <a href="#ref-for-public-key-credential-source⑤⑤">(2)</a>
+    <li><a href="#ref-for-public-key-credential-source⑤⑥">6.3.5. The silentCredentialDiscovery operation</a>
+    <li><a href="#ref-for-public-key-credential-source⑤⑦">10.1.3. Credential Properties Extension (credProps)</a>
+    <li><a href="#ref-for-public-key-credential-source⑤⑧">11.5. Add Credential</a> <a href="#ref-for-public-key-credential-source⑤⑨">(2)</a> <a href="#ref-for-public-key-credential-source⑥⓪">(3)</a>
+    <li><a href="#ref-for-public-key-credential-source⑥①">11.6. Get Credentials</a> <a href="#ref-for-public-key-credential-source⑥②">(2)</a>
+    <li><a href="#ref-for-public-key-credential-source⑥③">11.7. Remove Credential</a> <a href="#ref-for-public-key-credential-source⑥④">(2)</a> <a href="#ref-for-public-key-credential-source⑥⑤">(3)</a>
+    <li><a href="#ref-for-public-key-credential-source⑥⑥">11.8. Remove All Credentials</a> <a href="#ref-for-public-key-credential-source⑥⑦">(2)</a>
    </ul>
   </aside>
   <aside class="dfn-panel" data-for="public-key-credential-source-type">
    <b><a href="#public-key-credential-source-type">#public-key-credential-source-type</a></b><b>Referenced in:</b>
    <ul>
-    <li><a href="#ref-for-public-key-credential-source-type">6.3.2. The authenticatorMakeCredential Operation</a> <a href="#ref-for-public-key-credential-source-type①">(2)</a>
-    <li><a href="#ref-for-public-key-credential-source-type②">6.3.5. The silentCredentialDiscovery operation</a>
-    <li><a href="#ref-for-public-key-credential-source-type③">11.5. Add Credential</a>
+    <li><a href="#ref-for-public-key-credential-source-type">4. Terminology</a>
+    <li><a href="#ref-for-public-key-credential-source-type①">6.3.2. The authenticatorMakeCredential Operation</a> <a href="#ref-for-public-key-credential-source-type②">(2)</a>
+    <li><a href="#ref-for-public-key-credential-source-type③">6.3.5. The silentCredentialDiscovery operation</a>
+    <li><a href="#ref-for-public-key-credential-source-type④">11.5. Add Credential</a>
    </ul>
   </aside>
   <aside class="dfn-panel" data-for="public-key-credential-source-id">
@@ -11307,27 +11485,26 @@ <h2 class="no-num no-ref heading settled" id="issues-index"><span class="content
    <ul>
     <li><a href="#ref-for-registration">1. Introduction</a> <a href="#ref-for-registration①">(2)</a>
     <li><a href="#ref-for-registration②">1.1. Specification Roadmap</a>
-    <li><a href="#ref-for-registration③">4. Terminology</a> <a href="#ref-for-registration④">(2)</a> <a href="#ref-for-registration⑤">(3)</a> <a href="#ref-for-registration⑥">(4)</a> <a href="#ref-for-registration⑦">(5)</a> <a href="#ref-for-registration⑧">(6)</a> <a href="#ref-for-registration⑨">(7)</a> <a href="#ref-for-registration①⓪">(8)</a> <a href="#ref-for-registration①①">(9)</a> <a href="#ref-for-registration①②">(10)</a> <a href="#ref-for-registration①③">(11)</a>
-    <li><a href="#ref-for-registration①④">5.4. Options for Credential Creation (dictionary PublicKeyCredentialCreationOptions)</a>
-    <li><a href="#ref-for-registration①⑤">6.2.3. Authentication Factor Capability</a>
-    <li><a href="#ref-for-registration①⑥">6.5. Attestation</a>
-    <li><a href="#ref-for-registration①⑦">7.1. Registering a New Credential</a>
-    <li><a href="#ref-for-registration①⑧">10.1.4. Pseudo-random function extension (prf)</a> <a href="#ref-for-registration①⑨">(2)</a> <a href="#ref-for-registration②⓪">(3)</a> <a href="#ref-for-registration②①">(4)</a>
-    <li><a href="#ref-for-registration②②">13. Security Considerations</a>
-    <li><a href="#ref-for-registration②③">13.4.5. Revoked Attestation Certificates</a> <a href="#ref-for-registration②④">(2)</a>
-    <li><a href="#ref-for-registration②⑤">14.1. De-anonymization Prevention Measures</a>
-    <li><a href="#ref-for-registration②⑥">14.3. Authenticator-local Biometric Recognition</a>
-    <li><a href="#ref-for-registration②⑦">15. Accessibility Considerations</a>
-    <li><a href="#ref-for-registration②⑧">16. Acknowledgements</a>
+    <li><a href="#ref-for-registration③">4. Terminology</a> <a href="#ref-for-registration④">(2)</a> <a href="#ref-for-registration⑤">(3)</a> <a href="#ref-for-registration⑥">(4)</a> <a href="#ref-for-registration⑦">(5)</a> <a href="#ref-for-registration⑧">(6)</a> <a href="#ref-for-registration⑨">(7)</a> <a href="#ref-for-registration①⓪">(8)</a> <a href="#ref-for-registration①①">(9)</a> <a href="#ref-for-registration①②">(10)</a> <a href="#ref-for-registration①③">(11)</a> <a href="#ref-for-registration①④">(12)</a> <a href="#ref-for-registration①⑤">(13)</a> <a href="#ref-for-registration①⑥">(14)</a>
+    <li><a href="#ref-for-registration①⑦">5.4. Options for Credential Creation (dictionary PublicKeyCredentialCreationOptions)</a>
+    <li><a href="#ref-for-registration①⑧">6.2.3. Authentication Factor Capability</a>
+    <li><a href="#ref-for-registration①⑨">6.5. Attestation</a>
+    <li><a href="#ref-for-registration②⓪">7.1. Registering a New Credential</a>
+    <li><a href="#ref-for-registration②①">10.1.4. Pseudo-random function extension (prf)</a> <a href="#ref-for-registration②②">(2)</a> <a href="#ref-for-registration②③">(3)</a> <a href="#ref-for-registration②④">(4)</a>
+    <li><a href="#ref-for-registration②⑤">13. Security Considerations</a>
+    <li><a href="#ref-for-registration②⑥">13.4.5. Revoked Attestation Certificates</a> <a href="#ref-for-registration②⑦">(2)</a>
+    <li><a href="#ref-for-registration②⑧">14.1. De-anonymization Prevention Measures</a>
+    <li><a href="#ref-for-registration②⑨">14.3. Authenticator-local Biometric Recognition</a>
+    <li><a href="#ref-for-registration③⓪">15. Accessibility Considerations</a>
+    <li><a href="#ref-for-registration③①">16. Acknowledgements</a>
    </ul>
   </aside>
   <aside class="dfn-panel" data-for="registration-ceremony">
    <b><a href="#registration-ceremony">#registration-ceremony</a></b><b>Referenced in:</b>
    <ul>
-    <li><a href="#ref-for-registration-ceremony">4. Terminology</a> <a href="#ref-for-registration-ceremony①">(2)</a> <a href="#ref-for-registration-ceremony②">(3)</a>
-    <li><a href="#ref-for-registration-ceremony③">5.1. PublicKeyCredential Interface</a>
-    <li><a href="#ref-for-registration-ceremony④">5.4.5. Authenticator Attachment Enumeration (enum AuthenticatorAttachment)</a>
-    <li><a href="#ref-for-registration-ceremony⑤">5.5. Options for Assertion Generation (dictionary PublicKeyCredentialRequestOptions)</a>
+    <li><a href="#ref-for-registration-ceremony">4. Terminology</a> <a href="#ref-for-registration-ceremony①">(2)</a> <a href="#ref-for-registration-ceremony②">(3)</a> <a href="#ref-for-registration-ceremony③">(4)</a>
+    <li><a href="#ref-for-registration-ceremony④">5.1. PublicKeyCredential Interface</a>
+    <li><a href="#ref-for-registration-ceremony⑤">5.4.5. Authenticator Attachment Enumeration (enum AuthenticatorAttachment)</a>
     <li><a href="#ref-for-registration-ceremony⑥">6.1.3. Credential Backup State</a>
     <li><a href="#ref-for-registration-ceremony⑦">7. WebAuthn Relying Party Operations</a>
     <li><a href="#ref-for-registration-ceremony⑧">7.1. Registering a New Credential</a> <a href="#ref-for-registration-ceremony⑨">(2)</a> <a href="#ref-for-registration-ceremony①⓪">(3)</a> <a href="#ref-for-registration-ceremony①①">(4)</a>
@@ -11350,80 +11527,80 @@ <h2 class="no-num no-ref heading settled" id="issues-index"><span class="content
     <li><a href="#ref-for-relying-party②⑤">1.3.3. Authentication</a> <a href="#ref-for-relying-party②⑥">(2)</a> <a href="#ref-for-relying-party②⑦">(3)</a> <a href="#ref-for-relying-party②⑧">(4)</a> <a href="#ref-for-relying-party②⑨">(5)</a>
     <li><a href="#ref-for-relying-party③⓪">1.3.5. Decommissioning</a> <a href="#ref-for-relying-party③①">(2)</a>
     <li><a href="#ref-for-relying-party③②">2.1.1. Enumerations as DOMString types</a>
-    <li><a href="#ref-for-relying-party③③">4. Terminology</a> <a href="#ref-for-relying-party③④">(2)</a> <a href="#ref-for-relying-party③⑤">(3)</a> <a href="#ref-for-relying-party③⑥">(4)</a> <a href="#ref-for-relying-party③⑦">(5)</a> <a href="#ref-for-relying-party③⑧">(6)</a> <a href="#ref-for-relying-party③⑨">(7)</a> <a href="#ref-for-relying-party④⓪">(8)</a> <a href="#ref-for-relying-party④①">(9)</a> <a href="#ref-for-relying-party④②">(10)</a> <a href="#ref-for-relying-party④③">(11)</a> <a href="#ref-for-relying-party④④">(12)</a> <a href="#ref-for-relying-party④⑤">(13)</a> <a href="#ref-for-relying-party④⑥">(14)</a> <a href="#ref-for-relying-party④⑦">(15)</a> <a href="#ref-for-relying-party④⑧">(16)</a> <a href="#ref-for-relying-party④⑨">(17)</a> <a href="#ref-for-relying-party⑤⓪">(18)</a> <a href="#ref-for-relying-party⑤①">(19)</a> <a href="#ref-for-relying-party⑤②">(20)</a> <a href="#ref-for-relying-party⑤③">(21)</a> <a href="#ref-for-relying-party⑤④">(22)</a> <a href="#ref-for-relying-party⑤⑤">(23)</a> <a href="#ref-for-relying-party⑤⑥">(24)</a> <a href="#ref-for-relying-party⑤⑦">(25)</a> <a href="#ref-for-relying-party⑤⑧">(26)</a> <a href="#ref-for-relying-party⑤⑨">(27)</a> <a href="#ref-for-relying-party⑥⓪">(28)</a> <a href="#ref-for-relying-party⑥①">(29)</a> <a href="#ref-for-relying-party⑥②">(30)</a> <a href="#ref-for-relying-party⑥③">(31)</a> <a href="#ref-for-relying-party⑥④">(32)</a> <a href="#ref-for-relying-party⑥⑤">(33)</a> <a href="#ref-for-relying-party⑥⑥">(34)</a> <a href="#ref-for-relying-party⑥⑦">(35)</a> <a href="#ref-for-relying-party⑥⑧">(36)</a> <a href="#ref-for-relying-party⑥⑨">(37)</a> <a href="#ref-for-relying-party⑦⓪">(38)</a> <a href="#ref-for-relying-party⑦①">(39)</a>
-    <li><a href="#ref-for-relying-party⑦②">5. Web Authentication API</a> <a href="#ref-for-relying-party⑦③">(2)</a> <a href="#ref-for-relying-party⑦④">(3)</a> <a href="#ref-for-relying-party⑦⑤">(4)</a> <a href="#ref-for-relying-party⑦⑥">(5)</a> <a href="#ref-for-relying-party⑦⑦">(6)</a> <a href="#ref-for-relying-party⑦⑧">(7)</a>
-    <li><a href="#ref-for-relying-party⑦⑨">5.1. PublicKeyCredential Interface</a> <a href="#ref-for-relying-party⑧⓪">(2)</a> <a href="#ref-for-relying-party⑧①">(3)</a> <a href="#ref-for-relying-party⑧②">(4)</a> <a href="#ref-for-relying-party⑧③">(5)</a>
-    <li><a href="#ref-for-relying-party⑧④">5.1.3. Create a New Credential - PublicKeyCredential’s [[Create]](origin, options, sameOriginWithAncestors) Method</a> <a href="#ref-for-relying-party⑧⑤">(2)</a> <a href="#ref-for-relying-party⑧⑥">(3)</a> <a href="#ref-for-relying-party⑧⑦">(4)</a>
-    <li><a href="#ref-for-relying-party⑧⑧">5.1.4. Use an Existing Credential to Make an Assertion - PublicKeyCredential’s [[Get]](options) Method</a> <a href="#ref-for-relying-party⑧⑨">(2)</a> <a href="#ref-for-relying-party⑨⓪">(3)</a> <a href="#ref-for-relying-party⑨①">(4)</a>
-    <li><a href="#ref-for-relying-party⑨②">5.1.4.2. Issuing a Credential Request to an Authenticator</a> <a href="#ref-for-relying-party⑨③">(2)</a>
-    <li><a href="#ref-for-relying-party⑨④">5.1.7. Availability of User-Verifying Platform Authenticator - PublicKeyCredential’s isUserVerifyingPlatformAuthenticatorAvailable() Method</a>
-    <li><a href="#ref-for-relying-party⑨⑤">5.2. Authenticator Responses (interface AuthenticatorResponse)</a>
-    <li><a href="#ref-for-relying-party⑨⑥">5.2.1. Information About Public Key Credential (interface AuthenticatorAttestationResponse)</a> <a href="#ref-for-relying-party⑨⑦">(2)</a>
-    <li><a href="#ref-for-relying-party⑨⑧">5.2.1.1. Easily accessing credential data</a> <a href="#ref-for-relying-party⑨⑨">(2)</a> <a href="#ref-for-relying-party①⓪⓪">(3)</a> <a href="#ref-for-relying-party①⓪①">(4)</a> <a href="#ref-for-relying-party①⓪②">(5)</a> <a href="#ref-for-relying-party①⓪③">(6)</a> <a href="#ref-for-relying-party①⓪④">(7)</a>
-    <li><a href="#ref-for-relying-party①⓪⑤">5.4. Options for Credential Creation (dictionary PublicKeyCredentialCreationOptions)</a> <a href="#ref-for-relying-party①⓪⑥">(2)</a> <a href="#ref-for-relying-party①⓪⑦">(3)</a> <a href="#ref-for-relying-party①⓪⑧">(4)</a> <a href="#ref-for-relying-party①⓪⑨">(5)</a> <a href="#ref-for-relying-party①①⓪">(6)</a> <a href="#ref-for-relying-party①①①">(7)</a> <a href="#ref-for-relying-party①①②">(8)</a> <a href="#ref-for-relying-party①①③">(9)</a>
-    <li><a href="#ref-for-relying-party①①④">5.4.1. Public Key Entity Description (dictionary PublicKeyCredentialEntity)</a> <a href="#ref-for-relying-party①①⑤">(2)</a> <a href="#ref-for-relying-party①①⑥">(3)</a> <a href="#ref-for-relying-party①①⑦">(4)</a> <a href="#ref-for-relying-party①①⑧">(5)</a> <a href="#ref-for-relying-party①①⑨">(6)</a>
-    <li><a href="#ref-for-relying-party①②⓪">5.4.2. Relying Party Parameters for Credential Generation (dictionary PublicKeyCredentialRpEntity)</a> <a href="#ref-for-relying-party①②①">(2)</a>
-    <li><a href="#ref-for-relying-party①②②">5.4.3. User Account Parameters for Credential Generation (dictionary PublicKeyCredentialUserEntity)</a> <a href="#ref-for-relying-party①②③">(2)</a> <a href="#ref-for-relying-party①②④">(3)</a> <a href="#ref-for-relying-party①②⑤">(4)</a>
-    <li><a href="#ref-for-relying-party①②⑥">5.4.4. Authenticator Selection Criteria (dictionary AuthenticatorSelectionCriteria)</a> <a href="#ref-for-relying-party①②⑦">(2)</a> <a href="#ref-for-relying-party①②⑧">(3)</a>
-    <li><a href="#ref-for-relying-party①②⑨">5.4.5. Authenticator Attachment Enumeration (enum AuthenticatorAttachment)</a> <a href="#ref-for-relying-party①③⓪">(2)</a> <a href="#ref-for-relying-party①③①">(3)</a>
-    <li><a href="#ref-for-relying-party①③②">5.4.6. Resident Key Requirement Enumeration (enum ResidentKeyRequirement)</a> <a href="#ref-for-relying-party①③③">(2)</a> <a href="#ref-for-relying-party①③④">(3)</a> <a href="#ref-for-relying-party①③⑤">(4)</a> <a href="#ref-for-relying-party①③⑥">(5)</a> <a href="#ref-for-relying-party①③⑦">(6)</a>
-    <li><a href="#ref-for-relying-party①③⑧">5.4.7. Attestation Conveyance Preference Enumeration (enum AttestationConveyancePreference)</a> <a href="#ref-for-relying-party①③⑨">(2)</a> <a href="#ref-for-relying-party①④⓪">(3)</a> <a href="#ref-for-relying-party①④①">(4)</a> <a href="#ref-for-relying-party①④②">(5)</a> <a href="#ref-for-relying-party①④③">(6)</a> <a href="#ref-for-relying-party①④④">(7)</a> <a href="#ref-for-relying-party①④⑤">(8)</a>
-    <li><a href="#ref-for-relying-party①④⑥">5.5. Options for Assertion Generation (dictionary PublicKeyCredentialRequestOptions)</a> <a href="#ref-for-relying-party①④⑦">(2)</a> <a href="#ref-for-relying-party①④⑧">(3)</a> <a href="#ref-for-relying-party①④⑨">(4)</a> <a href="#ref-for-relying-party①⑤⓪">(5)</a> <a href="#ref-for-relying-party①⑤①">(6)</a> <a href="#ref-for-relying-party①⑤②">(7)</a> <a href="#ref-for-relying-party①⑤③">(8)</a> <a href="#ref-for-relying-party①⑤④">(9)</a>
-    <li><a href="#ref-for-relying-party①⑤⑤">5.7.3. Authentication Extensions Authenticator Inputs (CDDL type AuthenticationExtensionsAuthenticatorInputs)</a>
-    <li><a href="#ref-for-relying-party①⑤⑥">5.8.1. Client Data Used in WebAuthn Signatures (dictionary CollectedClientData)</a> <a href="#ref-for-relying-party①⑤⑦">(2)</a> <a href="#ref-for-relying-party①⑤⑧">(3)</a> <a href="#ref-for-relying-party①⑤⑨">(4)</a> <a href="#ref-for-relying-party①⑥⓪">(5)</a>
-    <li><a href="#ref-for-relying-party①⑥①">5.8.3. Credential Descriptor (dictionary PublicKeyCredentialDescriptor)</a> <a href="#ref-for-relying-party①⑥②">(2)</a>
-    <li><a href="#ref-for-relying-party①⑥③">5.8.4. Authenticator Transport Enumeration (enum AuthenticatorTransport)</a>
-    <li><a href="#ref-for-relying-party①⑥④">5.8.6. User Verification Requirement Enumeration (enum UserVerificationRequirement)</a> <a href="#ref-for-relying-party①⑥⑤">(2)</a> <a href="#ref-for-relying-party①⑥⑥">(3)</a>
-    <li><a href="#ref-for-relying-party①⑥⑦">5.10. Using Web Authentication within iframe elements</a>
-    <li><a href="#ref-for-relying-party①⑥⑧">6. WebAuthn Authenticator Model</a> <a href="#ref-for-relying-party①⑥⑨">(2)</a> <a href="#ref-for-relying-party①⑦⓪">(3)</a> <a href="#ref-for-relying-party①⑦①">(4)</a>
-    <li><a href="#ref-for-relying-party①⑦②">6.1. Authenticator Data</a>
-    <li><a href="#ref-for-relying-party①⑦③">6.1.1. Signature Counter Considerations</a> <a href="#ref-for-relying-party①⑦④">(2)</a> <a href="#ref-for-relying-party①⑦⑤">(3)</a> <a href="#ref-for-relying-party①⑦⑥">(4)</a> <a href="#ref-for-relying-party①⑦⑦">(5)</a>
-    <li><a href="#ref-for-relying-party①⑦⑧">6.1.3. Credential Backup State</a> <a href="#ref-for-relying-party①⑦⑨">(2)</a> <a href="#ref-for-relying-party①⑧⓪">(3)</a> <a href="#ref-for-relying-party①⑧①">(4)</a> <a href="#ref-for-relying-party①⑧②">(5)</a>
-    <li><a href="#ref-for-relying-party①⑧③">6.2. Authenticator Taxonomy</a>
-    <li><a href="#ref-for-relying-party①⑧④">6.2.2. Credential Storage Modality</a> <a href="#ref-for-relying-party①⑧⑤">(2)</a> <a href="#ref-for-relying-party①⑧⑥">(3)</a>
-    <li><a href="#ref-for-relying-party①⑧⑦">6.2.3. Authentication Factor Capability</a> <a href="#ref-for-relying-party①⑧⑧">(2)</a> <a href="#ref-for-relying-party①⑧⑨">(3)</a>
-    <li><a href="#ref-for-relying-party①⑨⓪">6.3.2. The authenticatorMakeCredential Operation</a> <a href="#ref-for-relying-party①⑨①">(2)</a> <a href="#ref-for-relying-party①⑨②">(3)</a> <a href="#ref-for-relying-party①⑨③">(4)</a> <a href="#ref-for-relying-party①⑨④">(5)</a> <a href="#ref-for-relying-party①⑨⑤">(6)</a>
-    <li><a href="#ref-for-relying-party①⑨⑥">6.3.3. The authenticatorGetAssertion Operation</a> <a href="#ref-for-relying-party①⑨⑦">(2)</a> <a href="#ref-for-relying-party①⑨⑧">(3)</a>
-    <li><a href="#ref-for-relying-party①⑨⑨">6.4. String Handling</a>
-    <li><a href="#ref-for-relying-party②⓪⓪">6.4.1. String Truncation</a> <a href="#ref-for-relying-party②⓪①">(2)</a>
-    <li><a href="#ref-for-relying-party②⓪②">6.5. Attestation</a> <a href="#ref-for-relying-party②⓪③">(2)</a> <a href="#ref-for-relying-party②⓪④">(3)</a> <a href="#ref-for-relying-party②⓪⑤">(4)</a> <a href="#ref-for-relying-party②⓪⑥">(5)</a> <a href="#ref-for-relying-party②⓪⑦">(6)</a> <a href="#ref-for-relying-party②⓪⑧">(7)</a> <a href="#ref-for-relying-party②⓪⑨">(8)</a>
-    <li><a href="#ref-for-relying-party②①⓪">6.5.3. Attestation Types</a> <a href="#ref-for-relying-party②①①">(2)</a> <a href="#ref-for-relying-party②①②">(3)</a> <a href="#ref-for-relying-party②①③">(4)</a> <a href="#ref-for-relying-party②①④">(5)</a>
-    <li><a href="#ref-for-relying-party②①⑤">7. WebAuthn Relying Party Operations</a> <a href="#ref-for-relying-party②①⑥">(2)</a> <a href="#ref-for-relying-party②①⑦">(3)</a> <a href="#ref-for-relying-party②①⑧">(4)</a>
-    <li><a href="#ref-for-relying-party②①⑨">7.1. Registering a New Credential</a> <a href="#ref-for-relying-party②②⓪">(2)</a> <a href="#ref-for-relying-party②②①">(3)</a> <a href="#ref-for-relying-party②②②">(4)</a> <a href="#ref-for-relying-party②②③">(5)</a> <a href="#ref-for-relying-party②②④">(6)</a> <a href="#ref-for-relying-party②②⑤">(7)</a> <a href="#ref-for-relying-party②②⑥">(8)</a> <a href="#ref-for-relying-party②②⑦">(9)</a> <a href="#ref-for-relying-party②②⑧">(10)</a> <a href="#ref-for-relying-party②②⑨">(11)</a> <a href="#ref-for-relying-party②③⓪">(12)</a> <a href="#ref-for-relying-party②③①">(13)</a> <a href="#ref-for-relying-party②③②">(14)</a> <a href="#ref-for-relying-party②③③">(15)</a> <a href="#ref-for-relying-party②③④">(16)</a> <a href="#ref-for-relying-party②③⑤">(17)</a> <a href="#ref-for-relying-party②③⑥">(18)</a> <a href="#ref-for-relying-party②③⑦">(19)</a> <a href="#ref-for-relying-party②③⑧">(20)</a> <a href="#ref-for-relying-party②③⑨">(21)</a> <a href="#ref-for-relying-party②④⓪">(22)</a> <a href="#ref-for-relying-party②④①">(23)</a> <a href="#ref-for-relying-party②④②">(24)</a>
-    <li><a href="#ref-for-relying-party②④③">7.2. Verifying an Authentication Assertion</a> <a href="#ref-for-relying-party②④④">(2)</a> <a href="#ref-for-relying-party②④⑤">(3)</a> <a href="#ref-for-relying-party②④⑥">(4)</a> <a href="#ref-for-relying-party②④⑦">(5)</a> <a href="#ref-for-relying-party②④⑧">(6)</a> <a href="#ref-for-relying-party②④⑨">(7)</a> <a href="#ref-for-relying-party②⑤⓪">(8)</a> <a href="#ref-for-relying-party②⑤①">(9)</a> <a href="#ref-for-relying-party②⑤②">(10)</a> <a href="#ref-for-relying-party②⑤③">(11)</a> <a href="#ref-for-relying-party②⑤④">(12)</a> <a href="#ref-for-relying-party②⑤⑤">(13)</a> <a href="#ref-for-relying-party②⑤⑥">(14)</a>
-    <li><a href="#ref-for-relying-party②⑤⑦">9. WebAuthn Extensions</a> <a href="#ref-for-relying-party②⑤⑧">(2)</a> <a href="#ref-for-relying-party②⑤⑨">(3)</a>
-    <li><a href="#ref-for-relying-party②⑥⓪">9.2. Defining Extensions</a>
-    <li><a href="#ref-for-relying-party②⑥①">9.3. Extending Request Parameters</a> <a href="#ref-for-relying-party②⑥②">(2)</a> <a href="#ref-for-relying-party②⑥③">(3)</a>
-    <li><a href="#ref-for-relying-party②⑥④">10.1.1. FIDO AppID Extension (appid)</a> <a href="#ref-for-relying-party②⑥⑤">(2)</a> <a href="#ref-for-relying-party②⑥⑥">(3)</a> <a href="#ref-for-relying-party②⑥⑦">(4)</a> <a href="#ref-for-relying-party②⑥⑧">(5)</a>
-    <li><a href="#ref-for-relying-party②⑥⑨">10.1.2. FIDO AppID Exclusion Extension (appidExclude)</a> <a href="#ref-for-relying-party②⑦⓪">(2)</a>
-    <li><a href="#ref-for-relying-party②⑦①">10.1.3. Credential Properties Extension (credProps)</a> <a href="#ref-for-relying-party②⑦②">(2)</a>
-    <li><a href="#ref-for-relying-party②⑦③">10.1.4. Pseudo-random function extension (prf)</a> <a href="#ref-for-relying-party②⑦④">(2)</a> <a href="#ref-for-relying-party②⑦⑤">(3)</a> <a href="#ref-for-relying-party②⑦⑥">(4)</a> <a href="#ref-for-relying-party②⑦⑦">(5)</a> <a href="#ref-for-relying-party②⑦⑧">(6)</a>
-    <li><a href="#ref-for-relying-party②⑦⑨">10.1.5. Large blob storage extension (largeBlob)</a> <a href="#ref-for-relying-party②⑧⓪">(2)</a> <a href="#ref-for-relying-party②⑧①">(3)</a> <a href="#ref-for-relying-party②⑧②">(4)</a> <a href="#ref-for-relying-party②⑧③">(5)</a> <a href="#ref-for-relying-party②⑧④">(6)</a> <a href="#ref-for-relying-party②⑧⑤">(7)</a> <a href="#ref-for-relying-party②⑧⑥">(8)</a>
-    <li><a href="#ref-for-relying-party②⑧⑦">10.2.1. User Verification Method Extension (uvm)</a>
-    <li><a href="#ref-for-relying-party②⑧⑧">12.4. WebAuthn Extension Identifier Registrations</a>
-    <li><a href="#ref-for-relying-party②⑧⑨">13. Security Considerations</a> <a href="#ref-for-relying-party②⑨⓪">(2)</a> <a href="#ref-for-relying-party②⑨①">(3)</a> <a href="#ref-for-relying-party②⑨②">(4)</a>
-    <li><a href="#ref-for-relying-party②⑨③">13.2. Physical Proximity between Client and Authenticator</a> <a href="#ref-for-relying-party②⑨④">(2)</a>
-    <li><a href="#ref-for-relying-party②⑨⑤">13.3.2. Attestation Certificate and Attestation Certificate CA Compromise</a> <a href="#ref-for-relying-party②⑨⑥">(2)</a>
-    <li><a href="#ref-for-relying-party②⑨⑦">13.4. Security considerations for Relying Parties</a>
-    <li><a href="#ref-for-relying-party②⑨⑧">13.4.1. Security Benefits for WebAuthn Relying Parties</a> <a href="#ref-for-relying-party②⑨⑨">(2)</a> <a href="#ref-for-relying-party③⓪⓪">(3)</a> <a href="#ref-for-relying-party③⓪①">(4)</a> <a href="#ref-for-relying-party③⓪②">(5)</a> <a href="#ref-for-relying-party③⓪③">(6)</a>
-    <li><a href="#ref-for-relying-party③⓪④">13.4.2. Visibility Considerations for Embedded Usage</a> <a href="#ref-for-relying-party③⓪⑤">(2)</a> <a href="#ref-for-relying-party③⓪⑥">(3)</a> <a href="#ref-for-relying-party③⓪⑦">(4)</a>
-    <li><a href="#ref-for-relying-party③⓪⑧">13.4.3. Cryptographic Challenges</a> <a href="#ref-for-relying-party③⓪⑨">(2)</a>
-    <li><a href="#ref-for-relying-party③①⓪">13.4.4. Attestation Limitations</a> <a href="#ref-for-relying-party③①①">(2)</a> <a href="#ref-for-relying-party③①②">(3)</a> <a href="#ref-for-relying-party③①③">(4)</a> <a href="#ref-for-relying-party③①④">(5)</a> <a href="#ref-for-relying-party③①⑤">(6)</a> <a href="#ref-for-relying-party③①⑥">(7)</a> <a href="#ref-for-relying-party③①⑦">(8)</a>
-    <li><a href="#ref-for-relying-party③①⑧">13.4.5. Revoked Attestation Certificates</a> <a href="#ref-for-relying-party③①⑨">(2)</a> <a href="#ref-for-relying-party③②⓪">(3)</a>
-    <li><a href="#ref-for-relying-party③②①">13.4.6. Credential Loss and Key Mobility</a> <a href="#ref-for-relying-party③②②">(2)</a> <a href="#ref-for-relying-party③②③">(3)</a>
-    <li><a href="#ref-for-relying-party③②④">13.4.7. Unprotected account detection</a> <a href="#ref-for-relying-party③②⑤">(2)</a>
-    <li><a href="#ref-for-relying-party③②⑥">13.4.8. Code injection attacks</a> <a href="#ref-for-relying-party③②⑦">(2)</a> <a href="#ref-for-relying-party③②⑧">(3)</a> <a href="#ref-for-relying-party③②⑨">(4)</a> <a href="#ref-for-relying-party③③⓪">(5)</a> <a href="#ref-for-relying-party③③①">(6)</a> <a href="#ref-for-relying-party③③②">(7)</a> <a href="#ref-for-relying-party③③③">(8)</a> <a href="#ref-for-relying-party③③④">(9)</a>
-    <li><a href="#ref-for-relying-party③③⑤">14. Privacy Considerations</a>
-    <li><a href="#ref-for-relying-party③③⑥">14.1. De-anonymization Prevention Measures</a> <a href="#ref-for-relying-party③③⑦">(2)</a> <a href="#ref-for-relying-party③③⑧">(3)</a> <a href="#ref-for-relying-party③③⑨">(4)</a> <a href="#ref-for-relying-party③④⓪">(5)</a> <a href="#ref-for-relying-party③④①">(6)</a> <a href="#ref-for-relying-party③④②">(7)</a>
-    <li><a href="#ref-for-relying-party③④③">14.2. Anonymous, Scoped, Non-correlatable Public Key Credentials</a> <a href="#ref-for-relying-party③④④">(2)</a> <a href="#ref-for-relying-party③④⑤">(3)</a> <a href="#ref-for-relying-party③④⑥">(4)</a> <a href="#ref-for-relying-party③④⑦">(5)</a> <a href="#ref-for-relying-party③④⑧">(6)</a> <a href="#ref-for-relying-party③④⑨">(7)</a> <a href="#ref-for-relying-party③⑤⓪">(8)</a> <a href="#ref-for-relying-party③⑤①">(9)</a> <a href="#ref-for-relying-party③⑤②">(10)</a> <a href="#ref-for-relying-party③⑤③">(11)</a>
-    <li><a href="#ref-for-relying-party③⑤④">14.3. Authenticator-local Biometric Recognition</a> <a href="#ref-for-relying-party③⑤⑤">(2)</a> <a href="#ref-for-relying-party③⑤⑥">(3)</a> <a href="#ref-for-relying-party③⑤⑦">(4)</a> <a href="#ref-for-relying-party③⑤⑧">(5)</a>
-    <li><a href="#ref-for-relying-party③⑤⑨">14.5.1. Registration Ceremony Privacy</a> <a href="#ref-for-relying-party③⑥⓪">(2)</a> <a href="#ref-for-relying-party③⑥①">(3)</a>
-    <li><a href="#ref-for-relying-party③⑥②">14.5.2. Authentication Ceremony Privacy</a> <a href="#ref-for-relying-party③⑥③">(2)</a> <a href="#ref-for-relying-party③⑥④">(3)</a>
-    <li><a href="#ref-for-relying-party③⑥⑤">14.6. Privacy considerations for Relying Parties</a>
-    <li><a href="#ref-for-relying-party③⑥⑥">14.6.1. User Handle Contents</a> <a href="#ref-for-relying-party③⑥⑦">(2)</a>
-    <li><a href="#ref-for-relying-party③⑥⑧">14.6.2. Username Enumeration</a> <a href="#ref-for-relying-party③⑥⑨">(2)</a> <a href="#ref-for-relying-party③⑦⓪">(3)</a> <a href="#ref-for-relying-party③⑦①">(4)</a> <a href="#ref-for-relying-party③⑦②">(5)</a> <a href="#ref-for-relying-party③⑦③">(6)</a> <a href="#ref-for-relying-party③⑦④">(7)</a> <a href="#ref-for-relying-party③⑦⑤">(8)</a> <a href="#ref-for-relying-party③⑦⑥">(9)</a> <a href="#ref-for-relying-party③⑦⑦">(10)</a> <a href="#ref-for-relying-party③⑦⑧">(11)</a> <a href="#ref-for-relying-party③⑦⑨">(12)</a>
-    <li><a href="#ref-for-relying-party③⑧⓪">14.6.3. Privacy leak via credential IDs</a> <a href="#ref-for-relying-party③⑧①">(2)</a> <a href="#ref-for-relying-party③⑧②">(3)</a> <a href="#ref-for-relying-party③⑧③">(4)</a> <a href="#ref-for-relying-party③⑧④">(5)</a>
-    <li><a href="#ref-for-relying-party③⑧⑤">15. Accessibility Considerations</a> <a href="#ref-for-relying-party③⑧⑥">(2)</a>
+    <li><a href="#ref-for-relying-party③③">4. Terminology</a> <a href="#ref-for-relying-party③④">(2)</a> <a href="#ref-for-relying-party③⑤">(3)</a> <a href="#ref-for-relying-party③⑥">(4)</a> <a href="#ref-for-relying-party③⑦">(5)</a> <a href="#ref-for-relying-party③⑧">(6)</a> <a href="#ref-for-relying-party③⑨">(7)</a> <a href="#ref-for-relying-party④⓪">(8)</a> <a href="#ref-for-relying-party④①">(9)</a> <a href="#ref-for-relying-party④②">(10)</a> <a href="#ref-for-relying-party④③">(11)</a> <a href="#ref-for-relying-party④④">(12)</a> <a href="#ref-for-relying-party④⑤">(13)</a> <a href="#ref-for-relying-party④⑥">(14)</a> <a href="#ref-for-relying-party④⑦">(15)</a> <a href="#ref-for-relying-party④⑧">(16)</a> <a href="#ref-for-relying-party④⑨">(17)</a> <a href="#ref-for-relying-party⑤⓪">(18)</a> <a href="#ref-for-relying-party⑤①">(19)</a> <a href="#ref-for-relying-party⑤②">(20)</a> <a href="#ref-for-relying-party⑤③">(21)</a> <a href="#ref-for-relying-party⑤④">(22)</a> <a href="#ref-for-relying-party⑤⑤">(23)</a> <a href="#ref-for-relying-party⑤⑥">(24)</a> <a href="#ref-for-relying-party⑤⑦">(25)</a> <a href="#ref-for-relying-party⑤⑧">(26)</a> <a href="#ref-for-relying-party⑤⑨">(27)</a> <a href="#ref-for-relying-party⑥⓪">(28)</a> <a href="#ref-for-relying-party⑥①">(29)</a> <a href="#ref-for-relying-party⑥②">(30)</a> <a href="#ref-for-relying-party⑥③">(31)</a> <a href="#ref-for-relying-party⑥④">(32)</a> <a href="#ref-for-relying-party⑥⑤">(33)</a> <a href="#ref-for-relying-party⑥⑥">(34)</a> <a href="#ref-for-relying-party⑥⑦">(35)</a> <a href="#ref-for-relying-party⑥⑧">(36)</a> <a href="#ref-for-relying-party⑥⑨">(37)</a> <a href="#ref-for-relying-party⑦⓪">(38)</a> <a href="#ref-for-relying-party⑦①">(39)</a> <a href="#ref-for-relying-party⑦②">(40)</a> <a href="#ref-for-relying-party⑦③">(41)</a> <a href="#ref-for-relying-party⑦④">(42)</a> <a href="#ref-for-relying-party⑦⑤">(43)</a> <a href="#ref-for-relying-party⑦⑥">(44)</a>
+    <li><a href="#ref-for-relying-party⑦⑦">5. Web Authentication API</a> <a href="#ref-for-relying-party⑦⑧">(2)</a> <a href="#ref-for-relying-party⑦⑨">(3)</a> <a href="#ref-for-relying-party⑧⓪">(4)</a> <a href="#ref-for-relying-party⑧①">(5)</a> <a href="#ref-for-relying-party⑧②">(6)</a> <a href="#ref-for-relying-party⑧③">(7)</a>
+    <li><a href="#ref-for-relying-party⑧④">5.1. PublicKeyCredential Interface</a> <a href="#ref-for-relying-party⑧⑤">(2)</a> <a href="#ref-for-relying-party⑧⑥">(3)</a> <a href="#ref-for-relying-party⑧⑦">(4)</a> <a href="#ref-for-relying-party⑧⑧">(5)</a>
+    <li><a href="#ref-for-relying-party⑧⑨">5.1.3. Create a New Credential - PublicKeyCredential’s [[Create]](origin, options, sameOriginWithAncestors) Method</a> <a href="#ref-for-relying-party⑨⓪">(2)</a> <a href="#ref-for-relying-party⑨①">(3)</a> <a href="#ref-for-relying-party⑨②">(4)</a>
+    <li><a href="#ref-for-relying-party⑨③">5.1.4. Use an Existing Credential to Make an Assertion - PublicKeyCredential’s [[Get]](options) Method</a> <a href="#ref-for-relying-party⑨④">(2)</a> <a href="#ref-for-relying-party⑨⑤">(3)</a> <a href="#ref-for-relying-party⑨⑥">(4)</a>
+    <li><a href="#ref-for-relying-party⑨⑦">5.1.4.2. Issuing a Credential Request to an Authenticator</a> <a href="#ref-for-relying-party⑨⑧">(2)</a>
+    <li><a href="#ref-for-relying-party⑨⑨">5.1.7. Availability of User-Verifying Platform Authenticator - PublicKeyCredential’s isUserVerifyingPlatformAuthenticatorAvailable() Method</a>
+    <li><a href="#ref-for-relying-party①⓪⓪">5.2. Authenticator Responses (interface AuthenticatorResponse)</a>
+    <li><a href="#ref-for-relying-party①⓪①">5.2.1. Information About Public Key Credential (interface AuthenticatorAttestationResponse)</a> <a href="#ref-for-relying-party①⓪②">(2)</a>
+    <li><a href="#ref-for-relying-party①⓪③">5.2.1.1. Easily accessing credential data</a> <a href="#ref-for-relying-party①⓪④">(2)</a> <a href="#ref-for-relying-party①⓪⑤">(3)</a> <a href="#ref-for-relying-party①⓪⑥">(4)</a> <a href="#ref-for-relying-party①⓪⑦">(5)</a> <a href="#ref-for-relying-party①⓪⑧">(6)</a> <a href="#ref-for-relying-party①⓪⑨">(7)</a>
+    <li><a href="#ref-for-relying-party①①⓪">5.4. Options for Credential Creation (dictionary PublicKeyCredentialCreationOptions)</a> <a href="#ref-for-relying-party①①①">(2)</a> <a href="#ref-for-relying-party①①②">(3)</a> <a href="#ref-for-relying-party①①③">(4)</a> <a href="#ref-for-relying-party①①④">(5)</a> <a href="#ref-for-relying-party①①⑤">(6)</a> <a href="#ref-for-relying-party①①⑥">(7)</a> <a href="#ref-for-relying-party①①⑦">(8)</a> <a href="#ref-for-relying-party①①⑧">(9)</a>
+    <li><a href="#ref-for-relying-party①①⑨">5.4.1. Public Key Entity Description (dictionary PublicKeyCredentialEntity)</a> <a href="#ref-for-relying-party①②⓪">(2)</a> <a href="#ref-for-relying-party①②①">(3)</a> <a href="#ref-for-relying-party①②②">(4)</a> <a href="#ref-for-relying-party①②③">(5)</a> <a href="#ref-for-relying-party①②④">(6)</a>
+    <li><a href="#ref-for-relying-party①②⑤">5.4.2. Relying Party Parameters for Credential Generation (dictionary PublicKeyCredentialRpEntity)</a> <a href="#ref-for-relying-party①②⑥">(2)</a>
+    <li><a href="#ref-for-relying-party①②⑦">5.4.3. User Account Parameters for Credential Generation (dictionary PublicKeyCredentialUserEntity)</a> <a href="#ref-for-relying-party①②⑧">(2)</a> <a href="#ref-for-relying-party①②⑨">(3)</a> <a href="#ref-for-relying-party①③⓪">(4)</a>
+    <li><a href="#ref-for-relying-party①③①">5.4.4. Authenticator Selection Criteria (dictionary AuthenticatorSelectionCriteria)</a> <a href="#ref-for-relying-party①③②">(2)</a> <a href="#ref-for-relying-party①③③">(3)</a>
+    <li><a href="#ref-for-relying-party①③④">5.4.5. Authenticator Attachment Enumeration (enum AuthenticatorAttachment)</a> <a href="#ref-for-relying-party①③⑤">(2)</a> <a href="#ref-for-relying-party①③⑥">(3)</a>
+    <li><a href="#ref-for-relying-party①③⑦">5.4.6. Resident Key Requirement Enumeration (enum ResidentKeyRequirement)</a> <a href="#ref-for-relying-party①③⑧">(2)</a> <a href="#ref-for-relying-party①③⑨">(3)</a> <a href="#ref-for-relying-party①④⓪">(4)</a> <a href="#ref-for-relying-party①④①">(5)</a> <a href="#ref-for-relying-party①④②">(6)</a>
+    <li><a href="#ref-for-relying-party①④③">5.4.7. Attestation Conveyance Preference Enumeration (enum AttestationConveyancePreference)</a> <a href="#ref-for-relying-party①④④">(2)</a> <a href="#ref-for-relying-party①④⑤">(3)</a> <a href="#ref-for-relying-party①④⑥">(4)</a> <a href="#ref-for-relying-party①④⑦">(5)</a> <a href="#ref-for-relying-party①④⑧">(6)</a> <a href="#ref-for-relying-party①④⑨">(7)</a> <a href="#ref-for-relying-party①⑤⓪">(8)</a>
+    <li><a href="#ref-for-relying-party①⑤①">5.5. Options for Assertion Generation (dictionary PublicKeyCredentialRequestOptions)</a> <a href="#ref-for-relying-party①⑤②">(2)</a> <a href="#ref-for-relying-party①⑤③">(3)</a> <a href="#ref-for-relying-party①⑤④">(4)</a> <a href="#ref-for-relying-party①⑤⑤">(5)</a> <a href="#ref-for-relying-party①⑤⑥">(6)</a> <a href="#ref-for-relying-party①⑤⑦">(7)</a> <a href="#ref-for-relying-party①⑤⑧">(8)</a> <a href="#ref-for-relying-party①⑤⑨">(9)</a>
+    <li><a href="#ref-for-relying-party①⑥⓪">5.7.3. Authentication Extensions Authenticator Inputs (CDDL type AuthenticationExtensionsAuthenticatorInputs)</a>
+    <li><a href="#ref-for-relying-party①⑥①">5.8.1. Client Data Used in WebAuthn Signatures (dictionary CollectedClientData)</a> <a href="#ref-for-relying-party①⑥②">(2)</a> <a href="#ref-for-relying-party①⑥③">(3)</a> <a href="#ref-for-relying-party①⑥④">(4)</a> <a href="#ref-for-relying-party①⑥⑤">(5)</a>
+    <li><a href="#ref-for-relying-party①⑥⑥">5.8.3. Credential Descriptor (dictionary PublicKeyCredentialDescriptor)</a> <a href="#ref-for-relying-party①⑥⑦">(2)</a>
+    <li><a href="#ref-for-relying-party①⑥⑧">5.8.4. Authenticator Transport Enumeration (enum AuthenticatorTransport)</a>
+    <li><a href="#ref-for-relying-party①⑥⑨">5.8.6. User Verification Requirement Enumeration (enum UserVerificationRequirement)</a> <a href="#ref-for-relying-party①⑦⓪">(2)</a> <a href="#ref-for-relying-party①⑦①">(3)</a>
+    <li><a href="#ref-for-relying-party①⑦②">5.10. Using Web Authentication within iframe elements</a>
+    <li><a href="#ref-for-relying-party①⑦③">6. WebAuthn Authenticator Model</a> <a href="#ref-for-relying-party①⑦④">(2)</a> <a href="#ref-for-relying-party①⑦⑤">(3)</a> <a href="#ref-for-relying-party①⑦⑥">(4)</a>
+    <li><a href="#ref-for-relying-party①⑦⑦">6.1. Authenticator Data</a>
+    <li><a href="#ref-for-relying-party①⑦⑧">6.1.1. Signature Counter Considerations</a> <a href="#ref-for-relying-party①⑦⑨">(2)</a> <a href="#ref-for-relying-party①⑧⓪">(3)</a> <a href="#ref-for-relying-party①⑧①">(4)</a> <a href="#ref-for-relying-party①⑧②">(5)</a>
+    <li><a href="#ref-for-relying-party①⑧③">6.1.3. Credential Backup State</a> <a href="#ref-for-relying-party①⑧④">(2)</a> <a href="#ref-for-relying-party①⑧⑤">(3)</a> <a href="#ref-for-relying-party①⑧⑥">(4)</a> <a href="#ref-for-relying-party①⑧⑦">(5)</a>
+    <li><a href="#ref-for-relying-party①⑧⑧">6.2. Authenticator Taxonomy</a>
+    <li><a href="#ref-for-relying-party①⑧⑨">6.2.2. Credential Storage Modality</a> <a href="#ref-for-relying-party①⑨⓪">(2)</a> <a href="#ref-for-relying-party①⑨①">(3)</a>
+    <li><a href="#ref-for-relying-party①⑨②">6.2.3. Authentication Factor Capability</a> <a href="#ref-for-relying-party①⑨③">(2)</a> <a href="#ref-for-relying-party①⑨④">(3)</a>
+    <li><a href="#ref-for-relying-party①⑨⑤">6.3.2. The authenticatorMakeCredential Operation</a> <a href="#ref-for-relying-party①⑨⑥">(2)</a> <a href="#ref-for-relying-party①⑨⑦">(3)</a> <a href="#ref-for-relying-party①⑨⑧">(4)</a> <a href="#ref-for-relying-party①⑨⑨">(5)</a> <a href="#ref-for-relying-party②⓪⓪">(6)</a>
+    <li><a href="#ref-for-relying-party②⓪①">6.3.3. The authenticatorGetAssertion Operation</a> <a href="#ref-for-relying-party②⓪②">(2)</a> <a href="#ref-for-relying-party②⓪③">(3)</a>
+    <li><a href="#ref-for-relying-party②⓪④">6.4. String Handling</a>
+    <li><a href="#ref-for-relying-party②⓪⑤">6.4.1. String Truncation</a> <a href="#ref-for-relying-party②⓪⑥">(2)</a>
+    <li><a href="#ref-for-relying-party②⓪⑦">6.5. Attestation</a> <a href="#ref-for-relying-party②⓪⑧">(2)</a> <a href="#ref-for-relying-party②⓪⑨">(3)</a> <a href="#ref-for-relying-party②①⓪">(4)</a> <a href="#ref-for-relying-party②①①">(5)</a> <a href="#ref-for-relying-party②①②">(6)</a> <a href="#ref-for-relying-party②①③">(7)</a> <a href="#ref-for-relying-party②①④">(8)</a>
+    <li><a href="#ref-for-relying-party②①⑤">6.5.3. Attestation Types</a> <a href="#ref-for-relying-party②①⑥">(2)</a> <a href="#ref-for-relying-party②①⑦">(3)</a> <a href="#ref-for-relying-party②①⑧">(4)</a> <a href="#ref-for-relying-party②①⑨">(5)</a>
+    <li><a href="#ref-for-relying-party②②⓪">7. WebAuthn Relying Party Operations</a> <a href="#ref-for-relying-party②②①">(2)</a> <a href="#ref-for-relying-party②②②">(3)</a> <a href="#ref-for-relying-party②②③">(4)</a>
+    <li><a href="#ref-for-relying-party②②④">7.1. Registering a New Credential</a> <a href="#ref-for-relying-party②②⑤">(2)</a> <a href="#ref-for-relying-party②②⑥">(3)</a> <a href="#ref-for-relying-party②②⑦">(4)</a> <a href="#ref-for-relying-party②②⑧">(5)</a> <a href="#ref-for-relying-party②②⑨">(6)</a> <a href="#ref-for-relying-party②③⓪">(7)</a> <a href="#ref-for-relying-party②③①">(8)</a> <a href="#ref-for-relying-party②③②">(9)</a> <a href="#ref-for-relying-party②③③">(10)</a> <a href="#ref-for-relying-party②③④">(11)</a> <a href="#ref-for-relying-party②③⑤">(12)</a> <a href="#ref-for-relying-party②③⑥">(13)</a> <a href="#ref-for-relying-party②③⑦">(14)</a> <a href="#ref-for-relying-party②③⑧">(15)</a> <a href="#ref-for-relying-party②③⑨">(16)</a> <a href="#ref-for-relying-party②④⓪">(17)</a> <a href="#ref-for-relying-party②④①">(18)</a> <a href="#ref-for-relying-party②④②">(19)</a> <a href="#ref-for-relying-party②④③">(20)</a> <a href="#ref-for-relying-party②④④">(21)</a> <a href="#ref-for-relying-party②④⑤">(22)</a> <a href="#ref-for-relying-party②④⑥">(23)</a> <a href="#ref-for-relying-party②④⑦">(24)</a>
+    <li><a href="#ref-for-relying-party②④⑧">7.2. Verifying an Authentication Assertion</a> <a href="#ref-for-relying-party②④⑨">(2)</a> <a href="#ref-for-relying-party②⑤⓪">(3)</a> <a href="#ref-for-relying-party②⑤①">(4)</a> <a href="#ref-for-relying-party②⑤②">(5)</a> <a href="#ref-for-relying-party②⑤③">(6)</a> <a href="#ref-for-relying-party②⑤④">(7)</a> <a href="#ref-for-relying-party②⑤⑤">(8)</a> <a href="#ref-for-relying-party②⑤⑥">(9)</a> <a href="#ref-for-relying-party②⑤⑦">(10)</a> <a href="#ref-for-relying-party②⑤⑧">(11)</a> <a href="#ref-for-relying-party②⑤⑨">(12)</a> <a href="#ref-for-relying-party②⑥⓪">(13)</a> <a href="#ref-for-relying-party②⑥①">(14)</a> <a href="#ref-for-relying-party②⑥②">(15)</a> <a href="#ref-for-relying-party②⑥③">(16)</a>
+    <li><a href="#ref-for-relying-party②⑥④">9. WebAuthn Extensions</a> <a href="#ref-for-relying-party②⑥⑤">(2)</a> <a href="#ref-for-relying-party②⑥⑥">(3)</a>
+    <li><a href="#ref-for-relying-party②⑥⑦">9.2. Defining Extensions</a>
+    <li><a href="#ref-for-relying-party②⑥⑧">9.3. Extending Request Parameters</a> <a href="#ref-for-relying-party②⑥⑨">(2)</a> <a href="#ref-for-relying-party②⑦⓪">(3)</a>
+    <li><a href="#ref-for-relying-party②⑦①">10.1.1. FIDO AppID Extension (appid)</a> <a href="#ref-for-relying-party②⑦②">(2)</a> <a href="#ref-for-relying-party②⑦③">(3)</a> <a href="#ref-for-relying-party②⑦④">(4)</a> <a href="#ref-for-relying-party②⑦⑤">(5)</a>
+    <li><a href="#ref-for-relying-party②⑦⑥">10.1.2. FIDO AppID Exclusion Extension (appidExclude)</a> <a href="#ref-for-relying-party②⑦⑦">(2)</a>
+    <li><a href="#ref-for-relying-party②⑦⑧">10.1.3. Credential Properties Extension (credProps)</a> <a href="#ref-for-relying-party②⑦⑨">(2)</a>
+    <li><a href="#ref-for-relying-party②⑧⓪">10.1.4. Pseudo-random function extension (prf)</a> <a href="#ref-for-relying-party②⑧①">(2)</a> <a href="#ref-for-relying-party②⑧②">(3)</a> <a href="#ref-for-relying-party②⑧③">(4)</a> <a href="#ref-for-relying-party②⑧④">(5)</a> <a href="#ref-for-relying-party②⑧⑤">(6)</a>
+    <li><a href="#ref-for-relying-party②⑧⑥">10.1.5. Large blob storage extension (largeBlob)</a> <a href="#ref-for-relying-party②⑧⑦">(2)</a> <a href="#ref-for-relying-party②⑧⑧">(3)</a> <a href="#ref-for-relying-party②⑧⑨">(4)</a> <a href="#ref-for-relying-party②⑨⓪">(5)</a> <a href="#ref-for-relying-party②⑨①">(6)</a> <a href="#ref-for-relying-party②⑨②">(7)</a> <a href="#ref-for-relying-party②⑨③">(8)</a>
+    <li><a href="#ref-for-relying-party②⑨④">10.2.1. User Verification Method Extension (uvm)</a>
+    <li><a href="#ref-for-relying-party②⑨⑤">12.4. WebAuthn Extension Identifier Registrations</a>
+    <li><a href="#ref-for-relying-party②⑨⑥">13. Security Considerations</a> <a href="#ref-for-relying-party②⑨⑦">(2)</a> <a href="#ref-for-relying-party②⑨⑧">(3)</a> <a href="#ref-for-relying-party②⑨⑨">(4)</a>
+    <li><a href="#ref-for-relying-party③⓪⓪">13.2. Physical Proximity between Client and Authenticator</a> <a href="#ref-for-relying-party③⓪①">(2)</a>
+    <li><a href="#ref-for-relying-party③⓪②">13.3.2. Attestation Certificate and Attestation Certificate CA Compromise</a> <a href="#ref-for-relying-party③⓪③">(2)</a>
+    <li><a href="#ref-for-relying-party③⓪④">13.4. Security considerations for Relying Parties</a>
+    <li><a href="#ref-for-relying-party③⓪⑤">13.4.1. Security Benefits for WebAuthn Relying Parties</a> <a href="#ref-for-relying-party③⓪⑥">(2)</a> <a href="#ref-for-relying-party③⓪⑦">(3)</a> <a href="#ref-for-relying-party③⓪⑧">(4)</a> <a href="#ref-for-relying-party③⓪⑨">(5)</a> <a href="#ref-for-relying-party③①⓪">(6)</a>
+    <li><a href="#ref-for-relying-party③①①">13.4.2. Visibility Considerations for Embedded Usage</a> <a href="#ref-for-relying-party③①②">(2)</a> <a href="#ref-for-relying-party③①③">(3)</a> <a href="#ref-for-relying-party③①④">(4)</a>
+    <li><a href="#ref-for-relying-party③①⑤">13.4.3. Cryptographic Challenges</a> <a href="#ref-for-relying-party③①⑥">(2)</a>
+    <li><a href="#ref-for-relying-party③①⑦">13.4.4. Attestation Limitations</a> <a href="#ref-for-relying-party③①⑧">(2)</a> <a href="#ref-for-relying-party③①⑨">(3)</a> <a href="#ref-for-relying-party③②⓪">(4)</a> <a href="#ref-for-relying-party③②①">(5)</a> <a href="#ref-for-relying-party③②②">(6)</a> <a href="#ref-for-relying-party③②③">(7)</a> <a href="#ref-for-relying-party③②④">(8)</a>
+    <li><a href="#ref-for-relying-party③②⑤">13.4.5. Revoked Attestation Certificates</a> <a href="#ref-for-relying-party③②⑥">(2)</a> <a href="#ref-for-relying-party③②⑦">(3)</a>
+    <li><a href="#ref-for-relying-party③②⑧">13.4.6. Credential Loss and Key Mobility</a> <a href="#ref-for-relying-party③②⑨">(2)</a> <a href="#ref-for-relying-party③③⓪">(3)</a>
+    <li><a href="#ref-for-relying-party③③①">13.4.7. Unprotected account detection</a> <a href="#ref-for-relying-party③③②">(2)</a>
+    <li><a href="#ref-for-relying-party③③③">13.4.8. Code injection attacks</a> <a href="#ref-for-relying-party③③④">(2)</a> <a href="#ref-for-relying-party③③⑤">(3)</a> <a href="#ref-for-relying-party③③⑥">(4)</a> <a href="#ref-for-relying-party③③⑦">(5)</a> <a href="#ref-for-relying-party③③⑧">(6)</a> <a href="#ref-for-relying-party③③⑨">(7)</a> <a href="#ref-for-relying-party③④⓪">(8)</a> <a href="#ref-for-relying-party③④①">(9)</a>
+    <li><a href="#ref-for-relying-party③④②">14. Privacy Considerations</a>
+    <li><a href="#ref-for-relying-party③④③">14.1. De-anonymization Prevention Measures</a> <a href="#ref-for-relying-party③④④">(2)</a> <a href="#ref-for-relying-party③④⑤">(3)</a> <a href="#ref-for-relying-party③④⑥">(4)</a> <a href="#ref-for-relying-party③④⑦">(5)</a> <a href="#ref-for-relying-party③④⑧">(6)</a> <a href="#ref-for-relying-party③④⑨">(7)</a>
+    <li><a href="#ref-for-relying-party③⑤⓪">14.2. Anonymous, Scoped, Non-correlatable Public Key Credentials</a> <a href="#ref-for-relying-party③⑤①">(2)</a> <a href="#ref-for-relying-party③⑤②">(3)</a> <a href="#ref-for-relying-party③⑤③">(4)</a> <a href="#ref-for-relying-party③⑤④">(5)</a> <a href="#ref-for-relying-party③⑤⑤">(6)</a> <a href="#ref-for-relying-party③⑤⑥">(7)</a> <a href="#ref-for-relying-party③⑤⑦">(8)</a> <a href="#ref-for-relying-party③⑤⑧">(9)</a> <a href="#ref-for-relying-party③⑤⑨">(10)</a> <a href="#ref-for-relying-party③⑥⓪">(11)</a>
+    <li><a href="#ref-for-relying-party③⑥①">14.3. Authenticator-local Biometric Recognition</a> <a href="#ref-for-relying-party③⑥②">(2)</a> <a href="#ref-for-relying-party③⑥③">(3)</a> <a href="#ref-for-relying-party③⑥④">(4)</a> <a href="#ref-for-relying-party③⑥⑤">(5)</a>
+    <li><a href="#ref-for-relying-party③⑥⑥">14.5.1. Registration Ceremony Privacy</a> <a href="#ref-for-relying-party③⑥⑦">(2)</a> <a href="#ref-for-relying-party③⑥⑧">(3)</a>
+    <li><a href="#ref-for-relying-party③⑥⑨">14.5.2. Authentication Ceremony Privacy</a> <a href="#ref-for-relying-party③⑦⓪">(2)</a> <a href="#ref-for-relying-party③⑦①">(3)</a>
+    <li><a href="#ref-for-relying-party③⑦②">14.6. Privacy considerations for Relying Parties</a>
+    <li><a href="#ref-for-relying-party③⑦③">14.6.1. User Handle Contents</a> <a href="#ref-for-relying-party③⑦④">(2)</a>
+    <li><a href="#ref-for-relying-party③⑦⑤">14.6.2. Username Enumeration</a> <a href="#ref-for-relying-party③⑦⑥">(2)</a> <a href="#ref-for-relying-party③⑦⑦">(3)</a> <a href="#ref-for-relying-party③⑦⑧">(4)</a> <a href="#ref-for-relying-party③⑦⑨">(5)</a> <a href="#ref-for-relying-party③⑧⓪">(6)</a> <a href="#ref-for-relying-party③⑧①">(7)</a> <a href="#ref-for-relying-party③⑧②">(8)</a> <a href="#ref-for-relying-party③⑧③">(9)</a> <a href="#ref-for-relying-party③⑧④">(10)</a> <a href="#ref-for-relying-party③⑧⑤">(11)</a> <a href="#ref-for-relying-party③⑧⑥">(12)</a>
+    <li><a href="#ref-for-relying-party③⑧⑦">14.6.3. Privacy leak via credential IDs</a> <a href="#ref-for-relying-party③⑧⑧">(2)</a> <a href="#ref-for-relying-party③⑧⑨">(3)</a> <a href="#ref-for-relying-party③⑨⓪">(4)</a> <a href="#ref-for-relying-party③⑨①">(5)</a>
+    <li><a href="#ref-for-relying-party③⑨②">15. Accessibility Considerations</a> <a href="#ref-for-relying-party③⑨③">(2)</a>
    </ul>
   </aside>
   <aside class="dfn-panel" data-for="webauthn-relying-party">
@@ -11587,19 +11764,20 @@ <h2 class="no-num no-ref heading settled" id="issues-index"><span class="content
   <aside class="dfn-panel" data-for="user-account">
    <b><a href="#user-account">#user-account</a></b><b>Referenced in:</b>
    <ul>
-    <li><a href="#ref-for-user-account">4. Terminology</a> <a href="#ref-for-user-account①">(2)</a> <a href="#ref-for-user-account②">(3)</a> <a href="#ref-for-user-account③">(4)</a> <a href="#ref-for-user-account④">(5)</a> <a href="#ref-for-user-account⑤">(6)</a> <a href="#ref-for-user-account⑥">(7)</a> <a href="#ref-for-user-account⑦">(8)</a> <a href="#ref-for-user-account⑧">(9)</a> <a href="#ref-for-user-account⑨">(10)</a> <a href="#ref-for-user-account①⓪">(11)</a>
-    <li><a href="#ref-for-user-account①①">5.4. Options for Credential Creation (dictionary PublicKeyCredentialCreationOptions)</a> <a href="#ref-for-user-account①②">(2)</a> <a href="#ref-for-user-account①③">(3)</a>
-    <li><a href="#ref-for-user-account①④">5.4.1. Public Key Entity Description (dictionary PublicKeyCredentialEntity)</a> <a href="#ref-for-user-account①⑤">(2)</a>
-    <li><a href="#ref-for-user-account①⑥">5.4.3. User Account Parameters for Credential Generation (dictionary PublicKeyCredentialUserEntity)</a> <a href="#ref-for-user-account①⑦">(2)</a> <a href="#ref-for-user-account①⑧">(3)</a> <a href="#ref-for-user-account①⑨">(4)</a> <a href="#ref-for-user-account②⓪">(5)</a>
-    <li><a href="#ref-for-user-account②①">5.5. Options for Assertion Generation (dictionary PublicKeyCredentialRequestOptions)</a> <a href="#ref-for-user-account②②">(2)</a> <a href="#ref-for-user-account②③">(3)</a> <a href="#ref-for-user-account②④">(4)</a> <a href="#ref-for-user-account②⑤">(5)</a>
-    <li><a href="#ref-for-user-account②⑥">6.1.3. Credential Backup State</a> <a href="#ref-for-user-account②⑦">(2)</a>
-    <li><a href="#ref-for-user-account②⑧">6.3.2. The authenticatorMakeCredential Operation</a>
-    <li><a href="#ref-for-user-account②⑨">7.1. Registering a New Credential</a> <a href="#ref-for-user-account③⓪">(2)</a>
-    <li><a href="#ref-for-user-account③①">13.4.6. Credential Loss and Key Mobility</a>
-    <li><a href="#ref-for-user-account③②">13.4.7. Unprotected account detection</a> <a href="#ref-for-user-account③③">(2)</a> <a href="#ref-for-user-account③④">(3)</a> <a href="#ref-for-user-account③⑤">(4)</a>
-    <li><a href="#ref-for-user-account③⑥">14.2. Anonymous, Scoped, Non-correlatable Public Key Credentials</a>
-    <li><a href="#ref-for-user-account③⑦">14.6.1. User Handle Contents</a>
-    <li><a href="#ref-for-user-account③⑧">14.6.2. Username Enumeration</a> <a href="#ref-for-user-account③⑨">(2)</a>
+    <li><a href="#ref-for-user-account">4. Terminology</a> <a href="#ref-for-user-account①">(2)</a> <a href="#ref-for-user-account②">(3)</a> <a href="#ref-for-user-account③">(4)</a> <a href="#ref-for-user-account④">(5)</a> <a href="#ref-for-user-account⑤">(6)</a> <a href="#ref-for-user-account⑥">(7)</a> <a href="#ref-for-user-account⑦">(8)</a> <a href="#ref-for-user-account⑧">(9)</a> <a href="#ref-for-user-account⑨">(10)</a> <a href="#ref-for-user-account①⓪">(11)</a> <a href="#ref-for-user-account①①">(12)</a> <a href="#ref-for-user-account①②">(13)</a>
+    <li><a href="#ref-for-user-account①③">5.4. Options for Credential Creation (dictionary PublicKeyCredentialCreationOptions)</a> <a href="#ref-for-user-account①④">(2)</a> <a href="#ref-for-user-account①⑤">(3)</a>
+    <li><a href="#ref-for-user-account①⑥">5.4.1. Public Key Entity Description (dictionary PublicKeyCredentialEntity)</a> <a href="#ref-for-user-account①⑦">(2)</a>
+    <li><a href="#ref-for-user-account①⑧">5.4.3. User Account Parameters for Credential Generation (dictionary PublicKeyCredentialUserEntity)</a> <a href="#ref-for-user-account①⑨">(2)</a> <a href="#ref-for-user-account②⓪">(3)</a> <a href="#ref-for-user-account②①">(4)</a> <a href="#ref-for-user-account②②">(5)</a>
+    <li><a href="#ref-for-user-account②③">5.5. Options for Assertion Generation (dictionary PublicKeyCredentialRequestOptions)</a> <a href="#ref-for-user-account②④">(2)</a> <a href="#ref-for-user-account②⑤">(3)</a> <a href="#ref-for-user-account②⑥">(4)</a> <a href="#ref-for-user-account②⑦">(5)</a>
+    <li><a href="#ref-for-user-account②⑧">6.1.3. Credential Backup State</a> <a href="#ref-for-user-account②⑨">(2)</a>
+    <li><a href="#ref-for-user-account③⓪">6.3.2. The authenticatorMakeCredential Operation</a>
+    <li><a href="#ref-for-user-account③①">7.1. Registering a New Credential</a>
+    <li><a href="#ref-for-user-account③②">7.2. Verifying an Authentication Assertion</a> <a href="#ref-for-user-account③③">(2)</a> <a href="#ref-for-user-account③④">(3)</a>
+    <li><a href="#ref-for-user-account③⑤">13.4.6. Credential Loss and Key Mobility</a>
+    <li><a href="#ref-for-user-account③⑥">13.4.7. Unprotected account detection</a> <a href="#ref-for-user-account③⑦">(2)</a> <a href="#ref-for-user-account③⑧">(3)</a> <a href="#ref-for-user-account③⑨">(4)</a>
+    <li><a href="#ref-for-user-account④⓪">14.2. Anonymous, Scoped, Non-correlatable Public Key Credentials</a>
+    <li><a href="#ref-for-user-account④①">14.6.1. User Handle Contents</a>
+    <li><a href="#ref-for-user-account④②">14.6.2. Username Enumeration</a> <a href="#ref-for-user-account④③">(2)</a>
    </ul>
   </aside>
   <aside class="dfn-panel" data-for="user-consent">
@@ -11635,10 +11813,11 @@ <h2 class="no-num no-ref heading settled" id="issues-index"><span class="content
     <li><a href="#ref-for-user-handle①⑧">6.2. Authenticator Taxonomy</a>
     <li><a href="#ref-for-user-handle①⑨">6.3.2. The authenticatorMakeCredential Operation</a>
     <li><a href="#ref-for-user-handle②⓪">6.3.5. The silentCredentialDiscovery operation</a>
-    <li><a href="#ref-for-user-handle②①">14.1. De-anonymization Prevention Measures</a>
-    <li><a href="#ref-for-user-handle②②">14.2. Anonymous, Scoped, Non-correlatable Public Key Credentials</a>
-    <li><a href="#ref-for-user-handle②③">14.4.2. Privacy of personally identifying information Stored in Authenticators</a>
-    <li><a href="#ref-for-user-handle②④">14.6.1. User Handle Contents</a> <a href="#ref-for-user-handle②⑤">(2)</a> <a href="#ref-for-user-handle②⑥">(3)</a> <a href="#ref-for-user-handle②⑦">(4)</a>
+    <li><a href="#ref-for-user-handle②①">7.2. Verifying an Authentication Assertion</a>
+    <li><a href="#ref-for-user-handle②②">14.1. De-anonymization Prevention Measures</a>
+    <li><a href="#ref-for-user-handle②③">14.2. Anonymous, Scoped, Non-correlatable Public Key Credentials</a>
+    <li><a href="#ref-for-user-handle②④">14.4.2. Privacy of personally identifying information Stored in Authenticators</a>
+    <li><a href="#ref-for-user-handle②⑤">14.6.1. User Handle Contents</a> <a href="#ref-for-user-handle②⑥">(2)</a> <a href="#ref-for-user-handle②⑦">(3)</a> <a href="#ref-for-user-handle②⑧">(4)</a>
    </ul>
   </aside>
   <aside class="dfn-panel" data-for="concept-user-present">
@@ -11719,8 +11898,9 @@ <h2 class="no-num no-ref heading settled" id="issues-index"><span class="content
    <ul>
     <li><a href="#ref-for-dom-publickeycredential-rawid">5.1. PublicKeyCredential Interface</a>
     <li><a href="#ref-for-dom-publickeycredential-rawid①">5.8.3. Credential Descriptor (dictionary PublicKeyCredentialDescriptor)</a>
-    <li><a href="#ref-for-dom-publickeycredential-rawid②">7.2. Verifying an Authentication Assertion</a>
-    <li><a href="#ref-for-dom-publickeycredential-rawid③">10.1.5. Large blob storage extension (largeBlob)</a>
+    <li><a href="#ref-for-dom-publickeycredential-rawid②">7.1. Registering a New Credential</a>
+    <li><a href="#ref-for-dom-publickeycredential-rawid③">7.2. Verifying an Authentication Assertion</a> <a href="#ref-for-dom-publickeycredential-rawid④">(2)</a>
+    <li><a href="#ref-for-dom-publickeycredential-rawid⑤">10.1.5. Large blob storage extension (largeBlob)</a>
    </ul>
   </aside>
   <aside class="dfn-panel" data-for="dom-publickeycredential-getclientextensionresults">
@@ -11753,8 +11933,8 @@ <h2 class="no-num no-ref heading settled" id="issues-index"><span class="content
     <li><a href="#ref-for-dom-publickeycredential-response②">5.1.3. Create a New Credential - PublicKeyCredential’s [[Create]](origin, options, sameOriginWithAncestors) Method</a>
     <li><a href="#ref-for-dom-publickeycredential-response③">5.1.4.1. PublicKeyCredential’s [[DiscoverFromExternalSource]](origin, options, sameOriginWithAncestors) Method</a>
     <li><a href="#ref-for-dom-publickeycredential-response④">5.8.3. Credential Descriptor (dictionary PublicKeyCredentialDescriptor)</a>
-    <li><a href="#ref-for-dom-publickeycredential-response⑤">7.1. Registering a New Credential</a> <a href="#ref-for-dom-publickeycredential-response⑥">(2)</a>
-    <li><a href="#ref-for-dom-publickeycredential-response⑦">7.2. Verifying an Authentication Assertion</a> <a href="#ref-for-dom-publickeycredential-response⑧">(2)</a>
+    <li><a href="#ref-for-dom-publickeycredential-response⑤">7.1. Registering a New Credential</a>
+    <li><a href="#ref-for-dom-publickeycredential-response⑥">7.2. Verifying an Authentication Assertion</a>
    </ul>
   </aside>
   <aside class="dfn-panel" data-for="dom-publickeycredential-authenticatorattachment">
@@ -12078,14 +12258,15 @@ <h2 class="no-num no-ref heading settled" id="issues-index"><span class="content
   <aside class="dfn-panel" data-for="dom-authenticatorresponse-clientdatajson">
    <b><a href="#dom-authenticatorresponse-clientdatajson">#dom-authenticatorresponse-clientdatajson</a></b><b>Referenced in:</b>
    <ul>
-    <li><a href="#ref-for-dom-authenticatorresponse-clientdatajson">5.1.3. Create a New Credential - PublicKeyCredential’s [[Create]](origin, options, sameOriginWithAncestors) Method</a>
-    <li><a href="#ref-for-dom-authenticatorresponse-clientdatajson①">5.1.4.1. PublicKeyCredential’s [[DiscoverFromExternalSource]](origin, options, sameOriginWithAncestors) Method</a>
-    <li><a href="#ref-for-dom-authenticatorresponse-clientdatajson②">5.2. Authenticator Responses (interface AuthenticatorResponse)</a>
-    <li><a href="#ref-for-dom-authenticatorresponse-clientdatajson③">5.2.1. Information About Public Key Credential (interface AuthenticatorAttestationResponse)</a>
-    <li><a href="#ref-for-dom-authenticatorresponse-clientdatajson④">5.2.2. Web Authentication Assertion (interface AuthenticatorAssertionResponse)</a>
-    <li><a href="#ref-for-dom-authenticatorresponse-clientdatajson⑤">5.8.1.2. Limited Verification Algorithm</a>
-    <li><a href="#ref-for-dom-authenticatorresponse-clientdatajson⑥">7.1. Registering a New Credential</a> <a href="#ref-for-dom-authenticatorresponse-clientdatajson⑦">(2)</a>
-    <li><a href="#ref-for-dom-authenticatorresponse-clientdatajson⑧">7.2. Verifying an Authentication Assertion</a>
+    <li><a href="#ref-for-dom-authenticatorresponse-clientdatajson">4. Terminology</a>
+    <li><a href="#ref-for-dom-authenticatorresponse-clientdatajson①">5.1.3. Create a New Credential - PublicKeyCredential’s [[Create]](origin, options, sameOriginWithAncestors) Method</a>
+    <li><a href="#ref-for-dom-authenticatorresponse-clientdatajson②">5.1.4.1. PublicKeyCredential’s [[DiscoverFromExternalSource]](origin, options, sameOriginWithAncestors) Method</a>
+    <li><a href="#ref-for-dom-authenticatorresponse-clientdatajson③">5.2. Authenticator Responses (interface AuthenticatorResponse)</a>
+    <li><a href="#ref-for-dom-authenticatorresponse-clientdatajson④">5.2.1. Information About Public Key Credential (interface AuthenticatorAttestationResponse)</a>
+    <li><a href="#ref-for-dom-authenticatorresponse-clientdatajson⑤">5.2.2. Web Authentication Assertion (interface AuthenticatorAssertionResponse)</a>
+    <li><a href="#ref-for-dom-authenticatorresponse-clientdatajson⑥">5.8.1.2. Limited Verification Algorithm</a>
+    <li><a href="#ref-for-dom-authenticatorresponse-clientdatajson⑦">7.1. Registering a New Credential</a> <a href="#ref-for-dom-authenticatorresponse-clientdatajson⑧">(2)</a> <a href="#ref-for-dom-authenticatorresponse-clientdatajson⑨">(3)</a>
+    <li><a href="#ref-for-dom-authenticatorresponse-clientdatajson①⓪">7.2. Verifying an Authentication Assertion</a>
    </ul>
   </aside>
   <aside class="dfn-panel" data-for="authenticatorattestationresponse">
@@ -12102,12 +12283,12 @@ <h2 class="no-num no-ref heading settled" id="issues-index"><span class="content
   <aside class="dfn-panel" data-for="dom-authenticatorattestationresponse-gettransports">
    <b><a href="#dom-authenticatorattestationresponse-gettransports">#dom-authenticatorattestationresponse-gettransports</a></b><b>Referenced in:</b>
    <ul>
-    <li><a href="#ref-for-dom-authenticatorattestationresponse-gettransports">5.1. PublicKeyCredential Interface</a>
-    <li><a href="#ref-for-dom-authenticatorattestationresponse-gettransports①">5.2.1. Information About Public Key Credential (interface AuthenticatorAttestationResponse)</a>
-    <li><a href="#ref-for-dom-authenticatorattestationresponse-gettransports②">5.8.3. Credential Descriptor (dictionary PublicKeyCredentialDescriptor)</a> <a href="#ref-for-dom-authenticatorattestationresponse-gettransports③">(2)</a>
-    <li><a href="#ref-for-dom-authenticatorattestationresponse-gettransports④">5.8.4. Authenticator Transport Enumeration (enum AuthenticatorTransport)</a>
-    <li><a href="#ref-for-dom-authenticatorattestationresponse-gettransports⑤">7.1. Registering a New Credential</a>
-    <li><a href="#ref-for-dom-authenticatorattestationresponse-gettransports⑥">7.2. Verifying an Authentication Assertion</a> <a href="#ref-for-dom-authenticatorattestationresponse-gettransports⑦">(2)</a>
+    <li><a href="#ref-for-dom-authenticatorattestationresponse-gettransports">4. Terminology</a> <a href="#ref-for-dom-authenticatorattestationresponse-gettransports①">(2)</a>
+    <li><a href="#ref-for-dom-authenticatorattestationresponse-gettransports②">5.1. PublicKeyCredential Interface</a>
+    <li><a href="#ref-for-dom-authenticatorattestationresponse-gettransports③">5.2.1. Information About Public Key Credential (interface AuthenticatorAttestationResponse)</a>
+    <li><a href="#ref-for-dom-authenticatorattestationresponse-gettransports④">5.8.3. Credential Descriptor (dictionary PublicKeyCredentialDescriptor)</a> <a href="#ref-for-dom-authenticatorattestationresponse-gettransports⑤">(2)</a>
+    <li><a href="#ref-for-dom-authenticatorattestationresponse-gettransports⑥">5.8.4. Authenticator Transport Enumeration (enum AuthenticatorTransport)</a>
+    <li><a href="#ref-for-dom-authenticatorattestationresponse-gettransports⑦">7.1. Registering a New Credential</a>
    </ul>
   </aside>
   <aside class="dfn-panel" data-for="dom-authenticatorattestationresponse-getauthenticatordata">
@@ -12134,10 +12315,11 @@ <h2 class="no-num no-ref heading settled" id="issues-index"><span class="content
   <aside class="dfn-panel" data-for="dom-authenticatorattestationresponse-attestationobject">
    <b><a href="#dom-authenticatorattestationresponse-attestationobject">#dom-authenticatorattestationresponse-attestationobject</a></b><b>Referenced in:</b>
    <ul>
-    <li><a href="#ref-for-dom-authenticatorattestationresponse-attestationobject">5.1.3. Create a New Credential - PublicKeyCredential’s [[Create]](origin, options, sameOriginWithAncestors) Method</a>
-    <li><a href="#ref-for-dom-authenticatorattestationresponse-attestationobject①">5.2.1. Information About Public Key Credential (interface AuthenticatorAttestationResponse)</a> <a href="#ref-for-dom-authenticatorattestationresponse-attestationobject②">(2)</a>
-    <li><a href="#ref-for-dom-authenticatorattestationresponse-attestationobject③">5.2.1.1. Easily accessing credential data</a> <a href="#ref-for-dom-authenticatorattestationresponse-attestationobject④">(2)</a> <a href="#ref-for-dom-authenticatorattestationresponse-attestationobject⑤">(3)</a>
-    <li><a href="#ref-for-dom-authenticatorattestationresponse-attestationobject⑥">7.1. Registering a New Credential</a>
+    <li><a href="#ref-for-dom-authenticatorattestationresponse-attestationobject">4. Terminology</a>
+    <li><a href="#ref-for-dom-authenticatorattestationresponse-attestationobject①">5.1.3. Create a New Credential - PublicKeyCredential’s [[Create]](origin, options, sameOriginWithAncestors) Method</a>
+    <li><a href="#ref-for-dom-authenticatorattestationresponse-attestationobject②">5.2.1. Information About Public Key Credential (interface AuthenticatorAttestationResponse)</a> <a href="#ref-for-dom-authenticatorattestationresponse-attestationobject③">(2)</a>
+    <li><a href="#ref-for-dom-authenticatorattestationresponse-attestationobject④">5.2.1.1. Easily accessing credential data</a> <a href="#ref-for-dom-authenticatorattestationresponse-attestationobject⑤">(2)</a> <a href="#ref-for-dom-authenticatorattestationresponse-attestationobject⑥">(3)</a>
+    <li><a href="#ref-for-dom-authenticatorattestationresponse-attestationobject⑦">7.1. Registering a New Credential</a> <a href="#ref-for-dom-authenticatorattestationresponse-attestationobject⑧">(2)</a>
    </ul>
   </aside>
   <aside class="dfn-panel" data-for="dom-authenticatorattestationresponse-transports-slot">
@@ -12185,7 +12367,7 @@ <h2 class="no-num no-ref heading settled" id="issues-index"><span class="content
     <li><a href="#ref-for-dom-authenticatorassertionresponse-userhandle③">5.2.2. Web Authentication Assertion (interface AuthenticatorAssertionResponse)</a>
     <li><a href="#ref-for-dom-authenticatorassertionresponse-userhandle④">5.4. Options for Credential Creation (dictionary PublicKeyCredentialCreationOptions)</a>
     <li><a href="#ref-for-dom-authenticatorassertionresponse-userhandle⑤">5.5. Options for Assertion Generation (dictionary PublicKeyCredentialRequestOptions)</a>
-    <li><a href="#ref-for-dom-authenticatorassertionresponse-userhandle⑥">7.2. Verifying an Authentication Assertion</a> <a href="#ref-for-dom-authenticatorassertionresponse-userhandle⑦">(2)</a>
+    <li><a href="#ref-for-dom-authenticatorassertionresponse-userhandle⑥">7.2. Verifying an Authentication Assertion</a> <a href="#ref-for-dom-authenticatorassertionresponse-userhandle⑦">(2)</a> <a href="#ref-for-dom-authenticatorassertionresponse-userhandle⑧">(3)</a>
    </ul>
   </aside>
   <aside class="dfn-panel" data-for="dictdef-publickeycredentialparameters">
@@ -12570,15 +12752,14 @@ <h2 class="no-num no-ref heading settled" id="issues-index"><span class="content
     <li><a href="#ref-for-dom-publickeycredentialrequestoptions-allowcredentials⑨">5.1.4.2. Issuing a Credential Request to an Authenticator</a> <a href="#ref-for-dom-publickeycredentialrequestoptions-allowcredentials①⓪">(2)</a> <a href="#ref-for-dom-publickeycredentialrequestoptions-allowcredentials①①">(3)</a> <a href="#ref-for-dom-publickeycredentialrequestoptions-allowcredentials①②">(4)</a>
     <li><a href="#ref-for-dom-publickeycredentialrequestoptions-allowcredentials①③">5.5. Options for Assertion Generation (dictionary PublicKeyCredentialRequestOptions)</a>
     <li><a href="#ref-for-dom-publickeycredentialrequestoptions-allowcredentials①④">6.2.2. Credential Storage Modality</a>
-    <li><a href="#ref-for-dom-publickeycredentialrequestoptions-allowcredentials①⑤">7.1. Registering a New Credential</a>
-    <li><a href="#ref-for-dom-publickeycredentialrequestoptions-allowcredentials①⑥">7.2. Verifying an Authentication Assertion</a> <a href="#ref-for-dom-publickeycredentialrequestoptions-allowcredentials①⑦">(2)</a> <a href="#ref-for-dom-publickeycredentialrequestoptions-allowcredentials①⑧">(3)</a>
-    <li><a href="#ref-for-dom-publickeycredentialrequestoptions-allowcredentials①⑨">10.1.1. FIDO AppID Extension (appid)</a> <a href="#ref-for-dom-publickeycredentialrequestoptions-allowcredentials②⓪">(2)</a>
-    <li><a href="#ref-for-dom-publickeycredentialrequestoptions-allowcredentials②①">10.1.4. Pseudo-random function extension (prf)</a> <a href="#ref-for-dom-publickeycredentialrequestoptions-allowcredentials②②">(2)</a>
-    <li><a href="#ref-for-dom-publickeycredentialrequestoptions-allowcredentials②③">10.1.5. Large blob storage extension (largeBlob)</a>
-    <li><a href="#ref-for-dom-publickeycredentialrequestoptions-allowcredentials②④">13.4.7. Unprotected account detection</a> <a href="#ref-for-dom-publickeycredentialrequestoptions-allowcredentials②⑤">(2)</a> <a href="#ref-for-dom-publickeycredentialrequestoptions-allowcredentials②⑥">(3)</a>
-    <li><a href="#ref-for-dom-publickeycredentialrequestoptions-allowcredentials②⑦">14.5.2. Authentication Ceremony Privacy</a> <a href="#ref-for-dom-publickeycredentialrequestoptions-allowcredentials②⑧">(2)</a>
-    <li><a href="#ref-for-dom-publickeycredentialrequestoptions-allowcredentials②⑨">14.6.2. Username Enumeration</a> <a href="#ref-for-dom-publickeycredentialrequestoptions-allowcredentials③⓪">(2)</a>
-    <li><a href="#ref-for-dom-publickeycredentialrequestoptions-allowcredentials③①">14.6.3. Privacy leak via credential IDs</a> <a href="#ref-for-dom-publickeycredentialrequestoptions-allowcredentials③②">(2)</a> <a href="#ref-for-dom-publickeycredentialrequestoptions-allowcredentials③③">(3)</a> <a href="#ref-for-dom-publickeycredentialrequestoptions-allowcredentials③④">(4)</a> <a href="#ref-for-dom-publickeycredentialrequestoptions-allowcredentials③⑤">(5)</a>
+    <li><a href="#ref-for-dom-publickeycredentialrequestoptions-allowcredentials①⑤">7.2. Verifying an Authentication Assertion</a> <a href="#ref-for-dom-publickeycredentialrequestoptions-allowcredentials①⑥">(2)</a>
+    <li><a href="#ref-for-dom-publickeycredentialrequestoptions-allowcredentials①⑦">10.1.1. FIDO AppID Extension (appid)</a> <a href="#ref-for-dom-publickeycredentialrequestoptions-allowcredentials①⑧">(2)</a>
+    <li><a href="#ref-for-dom-publickeycredentialrequestoptions-allowcredentials①⑨">10.1.4. Pseudo-random function extension (prf)</a> <a href="#ref-for-dom-publickeycredentialrequestoptions-allowcredentials②⓪">(2)</a>
+    <li><a href="#ref-for-dom-publickeycredentialrequestoptions-allowcredentials②①">10.1.5. Large blob storage extension (largeBlob)</a>
+    <li><a href="#ref-for-dom-publickeycredentialrequestoptions-allowcredentials②②">13.4.7. Unprotected account detection</a> <a href="#ref-for-dom-publickeycredentialrequestoptions-allowcredentials②③">(2)</a> <a href="#ref-for-dom-publickeycredentialrequestoptions-allowcredentials②④">(3)</a>
+    <li><a href="#ref-for-dom-publickeycredentialrequestoptions-allowcredentials②⑤">14.5.2. Authentication Ceremony Privacy</a> <a href="#ref-for-dom-publickeycredentialrequestoptions-allowcredentials②⑥">(2)</a>
+    <li><a href="#ref-for-dom-publickeycredentialrequestoptions-allowcredentials②⑦">14.6.2. Username Enumeration</a> <a href="#ref-for-dom-publickeycredentialrequestoptions-allowcredentials②⑧">(2)</a>
+    <li><a href="#ref-for-dom-publickeycredentialrequestoptions-allowcredentials②⑨">14.6.3. Privacy leak via credential IDs</a> <a href="#ref-for-dom-publickeycredentialrequestoptions-allowcredentials③⓪">(2)</a> <a href="#ref-for-dom-publickeycredentialrequestoptions-allowcredentials③①">(3)</a> <a href="#ref-for-dom-publickeycredentialrequestoptions-allowcredentials③②">(4)</a> <a href="#ref-for-dom-publickeycredentialrequestoptions-allowcredentials③③">(5)</a>
    </ul>
   </aside>
   <aside class="dfn-panel" data-for="dom-publickeycredentialrequestoptions-userverification">
@@ -12799,47 +12980,49 @@ <h2 class="no-num no-ref heading settled" id="issues-index"><span class="content
   <aside class="dfn-panel" data-for="dictdef-publickeycredentialdescriptor">
    <b><a href="#dictdef-publickeycredentialdescriptor">#dictdef-publickeycredentialdescriptor</a></b><b>Referenced in:</b>
    <ul>
-    <li><a href="#ref-for-dictdef-publickeycredentialdescriptor">5.1.4.1. PublicKeyCredential’s [[DiscoverFromExternalSource]](origin, options, sameOriginWithAncestors) Method</a> <a href="#ref-for-dictdef-publickeycredentialdescriptor①">(2)</a> <a href="#ref-for-dictdef-publickeycredentialdescriptor②">(3)</a> <a href="#ref-for-dictdef-publickeycredentialdescriptor③">(4)</a>
-    <li><a href="#ref-for-dictdef-publickeycredentialdescriptor④">5.4. Options for Credential Creation (dictionary PublicKeyCredentialCreationOptions)</a> <a href="#ref-for-dictdef-publickeycredentialdescriptor⑤">(2)</a>
-    <li><a href="#ref-for-dictdef-publickeycredentialdescriptor⑥">5.5. Options for Assertion Generation (dictionary PublicKeyCredentialRequestOptions)</a> <a href="#ref-for-dictdef-publickeycredentialdescriptor⑦">(2)</a>
-    <li><a href="#ref-for-dictdef-publickeycredentialdescriptor⑧">5.8.3. Credential Descriptor (dictionary PublicKeyCredentialDescriptor)</a> <a href="#ref-for-dictdef-publickeycredentialdescriptor⑨">(2)</a> <a href="#ref-for-dictdef-publickeycredentialdescriptor①⓪">(3)</a>
-    <li><a href="#ref-for-dictdef-publickeycredentialdescriptor①①">6.3.2. The authenticatorMakeCredential Operation</a>
-    <li><a href="#ref-for-dictdef-publickeycredentialdescriptor①②">6.3.3. The authenticatorGetAssertion Operation</a>
+    <li><a href="#ref-for-dictdef-publickeycredentialdescriptor">4. Terminology</a>
+    <li><a href="#ref-for-dictdef-publickeycredentialdescriptor①">5.1.4.1. PublicKeyCredential’s [[DiscoverFromExternalSource]](origin, options, sameOriginWithAncestors) Method</a> <a href="#ref-for-dictdef-publickeycredentialdescriptor②">(2)</a> <a href="#ref-for-dictdef-publickeycredentialdescriptor③">(3)</a> <a href="#ref-for-dictdef-publickeycredentialdescriptor④">(4)</a>
+    <li><a href="#ref-for-dictdef-publickeycredentialdescriptor⑤">5.4. Options for Credential Creation (dictionary PublicKeyCredentialCreationOptions)</a> <a href="#ref-for-dictdef-publickeycredentialdescriptor⑥">(2)</a>
+    <li><a href="#ref-for-dictdef-publickeycredentialdescriptor⑦">5.5. Options for Assertion Generation (dictionary PublicKeyCredentialRequestOptions)</a> <a href="#ref-for-dictdef-publickeycredentialdescriptor⑧">(2)</a>
+    <li><a href="#ref-for-dictdef-publickeycredentialdescriptor⑨">5.8.3. Credential Descriptor (dictionary PublicKeyCredentialDescriptor)</a> <a href="#ref-for-dictdef-publickeycredentialdescriptor①⓪">(2)</a> <a href="#ref-for-dictdef-publickeycredentialdescriptor①①">(3)</a>
+    <li><a href="#ref-for-dictdef-publickeycredentialdescriptor①②">6.3.2. The authenticatorMakeCredential Operation</a>
+    <li><a href="#ref-for-dictdef-publickeycredentialdescriptor①③">6.3.3. The authenticatorGetAssertion Operation</a>
     <li><a href="#ref-for-dictdef-publickeycredentialdescriptor">10.1.2. FIDO AppID Exclusion Extension (appidExclude)</a>
    </ul>
   </aside>
   <aside class="dfn-panel" data-for="dom-publickeycredentialdescriptor-type">
    <b><a href="#dom-publickeycredentialdescriptor-type">#dom-publickeycredentialdescriptor-type</a></b><b>Referenced in:</b>
    <ul>
-    <li><a href="#ref-for-dom-publickeycredentialdescriptor-type">5.1.4.2. Issuing a Credential Request to an Authenticator</a>
-    <li><a href="#ref-for-dom-publickeycredentialdescriptor-type①">5.8.3. Credential Descriptor (dictionary PublicKeyCredentialDescriptor)</a> <a href="#ref-for-dom-publickeycredentialdescriptor-type②">(2)</a>
-    <li><a href="#ref-for-dom-publickeycredentialdescriptor-type③">6.3.2. The authenticatorMakeCredential Operation</a>
-    <li><a href="#ref-for-dom-publickeycredentialdescriptor-type④">10.1.1. FIDO AppID Extension (appid)</a>
+    <li><a href="#ref-for-dom-publickeycredentialdescriptor-type">4. Terminology</a>
+    <li><a href="#ref-for-dom-publickeycredentialdescriptor-type①">5.1.4.2. Issuing a Credential Request to an Authenticator</a>
+    <li><a href="#ref-for-dom-publickeycredentialdescriptor-type②">5.8.3. Credential Descriptor (dictionary PublicKeyCredentialDescriptor)</a> <a href="#ref-for-dom-publickeycredentialdescriptor-type③">(2)</a>
+    <li><a href="#ref-for-dom-publickeycredentialdescriptor-type④">6.3.2. The authenticatorMakeCredential Operation</a>
+    <li><a href="#ref-for-dom-publickeycredentialdescriptor-type⑤">10.1.1. FIDO AppID Extension (appid)</a>
    </ul>
   </aside>
   <aside class="dfn-panel" data-for="dom-publickeycredentialdescriptor-id">
    <b><a href="#dom-publickeycredentialdescriptor-id">#dom-publickeycredentialdescriptor-id</a></b><b>Referenced in:</b>
    <ul>
-    <li><a href="#ref-for-dom-publickeycredentialdescriptor-id">5.1.4.1. PublicKeyCredential’s [[DiscoverFromExternalSource]](origin, options, sameOriginWithAncestors) Method</a> <a href="#ref-for-dom-publickeycredentialdescriptor-id①">(2)</a>
-    <li><a href="#ref-for-dom-publickeycredentialdescriptor-id②">5.1.4.2. Issuing a Credential Request to an Authenticator</a>
-    <li><a href="#ref-for-dom-publickeycredentialdescriptor-id③">5.8.3. Credential Descriptor (dictionary PublicKeyCredentialDescriptor)</a>
-    <li><a href="#ref-for-dom-publickeycredentialdescriptor-id④">6.3.2. The authenticatorMakeCredential Operation</a> <a href="#ref-for-dom-publickeycredentialdescriptor-id⑤">(2)</a> <a href="#ref-for-dom-publickeycredentialdescriptor-id⑥">(3)</a>
-    <li><a href="#ref-for-dom-publickeycredentialdescriptor-id⑦">6.3.3. The authenticatorGetAssertion Operation</a>
-    <li><a href="#ref-for-dom-publickeycredentialdescriptor-id⑧">10.1.1. FIDO AppID Extension (appid)</a> <a href="#ref-for-dom-publickeycredentialdescriptor-id⑨">(2)</a>
-    <li><a href="#ref-for-dom-publickeycredentialdescriptor-id①⓪">10.1.2. FIDO AppID Exclusion Extension (appidExclude)</a> <a href="#ref-for-dom-publickeycredentialdescriptor-id①①">(2)</a>
+    <li><a href="#ref-for-dom-publickeycredentialdescriptor-id">4. Terminology</a>
+    <li><a href="#ref-for-dom-publickeycredentialdescriptor-id①">5.1.4.1. PublicKeyCredential’s [[DiscoverFromExternalSource]](origin, options, sameOriginWithAncestors) Method</a> <a href="#ref-for-dom-publickeycredentialdescriptor-id②">(2)</a>
+    <li><a href="#ref-for-dom-publickeycredentialdescriptor-id③">5.1.4.2. Issuing a Credential Request to an Authenticator</a>
+    <li><a href="#ref-for-dom-publickeycredentialdescriptor-id④">5.8.3. Credential Descriptor (dictionary PublicKeyCredentialDescriptor)</a>
+    <li><a href="#ref-for-dom-publickeycredentialdescriptor-id⑤">6.3.2. The authenticatorMakeCredential Operation</a> <a href="#ref-for-dom-publickeycredentialdescriptor-id⑥">(2)</a> <a href="#ref-for-dom-publickeycredentialdescriptor-id⑦">(3)</a>
+    <li><a href="#ref-for-dom-publickeycredentialdescriptor-id⑧">6.3.3. The authenticatorGetAssertion Operation</a>
+    <li><a href="#ref-for-dom-publickeycredentialdescriptor-id⑨">10.1.1. FIDO AppID Extension (appid)</a> <a href="#ref-for-dom-publickeycredentialdescriptor-id①⓪">(2)</a>
+    <li><a href="#ref-for-dom-publickeycredentialdescriptor-id①①">10.1.2. FIDO AppID Exclusion Extension (appidExclude)</a> <a href="#ref-for-dom-publickeycredentialdescriptor-id①②">(2)</a>
    </ul>
   </aside>
   <aside class="dfn-panel" data-for="dom-publickeycredentialdescriptor-transports">
    <b><a href="#dom-publickeycredentialdescriptor-transports">#dom-publickeycredentialdescriptor-transports</a></b><b>Referenced in:</b>
    <ul>
     <li><a href="#ref-for-dom-publickeycredentialdescriptor-transports">2.1.1. Enumerations as DOMString types</a>
-    <li><a href="#ref-for-dom-publickeycredentialdescriptor-transports①">5.1.3. Create a New Credential - PublicKeyCredential’s [[Create]](origin, options, sameOriginWithAncestors) Method</a> <a href="#ref-for-dom-publickeycredentialdescriptor-transports②">(2)</a> <a href="#ref-for-dom-publickeycredentialdescriptor-transports③">(3)</a>
-    <li><a href="#ref-for-dom-publickeycredentialdescriptor-transports④">5.1.4.1. PublicKeyCredential’s [[DiscoverFromExternalSource]](origin, options, sameOriginWithAncestors) Method</a> <a href="#ref-for-dom-publickeycredentialdescriptor-transports⑤">(2)</a>
-    <li><a href="#ref-for-dom-publickeycredentialdescriptor-transports⑥">5.1.4.2. Issuing a Credential Request to an Authenticator</a> <a href="#ref-for-dom-publickeycredentialdescriptor-transports⑦">(2)</a>
-    <li><a href="#ref-for-dom-publickeycredentialdescriptor-transports⑧">5.5. Options for Assertion Generation (dictionary PublicKeyCredentialRequestOptions)</a>
-    <li><a href="#ref-for-dom-publickeycredentialdescriptor-transports⑨">5.8.3. Credential Descriptor (dictionary PublicKeyCredentialDescriptor)</a> <a href="#ref-for-dom-publickeycredentialdescriptor-transports①⓪">(2)</a>
-    <li><a href="#ref-for-dom-publickeycredentialdescriptor-transports①①">7.1. Registering a New Credential</a>
-    <li><a href="#ref-for-dom-publickeycredentialdescriptor-transports①②">7.2. Verifying an Authentication Assertion</a>
+    <li><a href="#ref-for-dom-publickeycredentialdescriptor-transports①">4. Terminology</a>
+    <li><a href="#ref-for-dom-publickeycredentialdescriptor-transports②">5.1.3. Create a New Credential - PublicKeyCredential’s [[Create]](origin, options, sameOriginWithAncestors) Method</a> <a href="#ref-for-dom-publickeycredentialdescriptor-transports③">(2)</a> <a href="#ref-for-dom-publickeycredentialdescriptor-transports④">(3)</a>
+    <li><a href="#ref-for-dom-publickeycredentialdescriptor-transports⑤">5.1.4.1. PublicKeyCredential’s [[DiscoverFromExternalSource]](origin, options, sameOriginWithAncestors) Method</a> <a href="#ref-for-dom-publickeycredentialdescriptor-transports⑥">(2)</a>
+    <li><a href="#ref-for-dom-publickeycredentialdescriptor-transports⑦">5.1.4.2. Issuing a Credential Request to an Authenticator</a> <a href="#ref-for-dom-publickeycredentialdescriptor-transports⑧">(2)</a>
+    <li><a href="#ref-for-dom-publickeycredentialdescriptor-transports⑨">5.5. Options for Assertion Generation (dictionary PublicKeyCredentialRequestOptions)</a>
+    <li><a href="#ref-for-dom-publickeycredentialdescriptor-transports①⓪">5.8.3. Credential Descriptor (dictionary PublicKeyCredentialDescriptor)</a> <a href="#ref-for-dom-publickeycredentialdescriptor-transports①①">(2)</a>
    </ul>
   </aside>
   <aside class="dfn-panel" data-for="enumdef-authenticatortransport">
@@ -12967,15 +13150,15 @@ <h2 class="no-num no-ref heading settled" id="issues-index"><span class="content
   <aside class="dfn-panel" data-for="attestation-signature">
    <b><a href="#attestation-signature">#attestation-signature</a></b><b>Referenced in:</b>
    <ul>
-    <li><a href="#ref-for-attestation-signature">4. Terminology</a>
-    <li><a href="#ref-for-attestation-signature①">6. WebAuthn Authenticator Model</a> <a href="#ref-for-attestation-signature②">(2)</a> <a href="#ref-for-attestation-signature③">(3)</a> <a href="#ref-for-attestation-signature④">(4)</a>
-    <li><a href="#ref-for-attestation-signature⑤">6.1. Authenticator Data</a>
-    <li><a href="#ref-for-attestation-signature⑥">6.5. Attestation</a>
-    <li><a href="#ref-for-attestation-signature⑦">6.5.3. Attestation Types</a>
-    <li><a href="#ref-for-attestation-signature⑧">7.1. Registering a New Credential</a>
-    <li><a href="#ref-for-attestation-signature⑨">8.2. Packed Attestation Statement Format</a> <a href="#ref-for-attestation-signature①⓪">(2)</a>
-    <li><a href="#ref-for-attestation-signature①①">8.3. TPM Attestation Statement Format</a> <a href="#ref-for-attestation-signature①②">(2)</a>
-    <li><a href="#ref-for-attestation-signature①③">8.6. FIDO U2F Attestation Statement Format</a>
+    <li><a href="#ref-for-attestation-signature">4. Terminology</a> <a href="#ref-for-attestation-signature①">(2)</a>
+    <li><a href="#ref-for-attestation-signature②">6. WebAuthn Authenticator Model</a> <a href="#ref-for-attestation-signature③">(2)</a> <a href="#ref-for-attestation-signature④">(3)</a> <a href="#ref-for-attestation-signature⑤">(4)</a>
+    <li><a href="#ref-for-attestation-signature⑥">6.1. Authenticator Data</a>
+    <li><a href="#ref-for-attestation-signature⑦">6.5. Attestation</a>
+    <li><a href="#ref-for-attestation-signature⑧">6.5.3. Attestation Types</a>
+    <li><a href="#ref-for-attestation-signature⑨">7.1. Registering a New Credential</a>
+    <li><a href="#ref-for-attestation-signature①⓪">8.2. Packed Attestation Statement Format</a> <a href="#ref-for-attestation-signature①①">(2)</a>
+    <li><a href="#ref-for-attestation-signature①②">8.3. TPM Attestation Statement Format</a> <a href="#ref-for-attestation-signature①③">(2)</a>
+    <li><a href="#ref-for-attestation-signature①④">8.6. FIDO U2F Attestation Statement Format</a>
    </ul>
   </aside>
   <aside class="dfn-panel" data-for="assertion-signature">
@@ -13000,29 +13183,29 @@ <h2 class="no-num no-ref heading settled" id="issues-index"><span class="content
    <b><a href="#authenticator-data">#authenticator-data</a></b><b>Referenced in:</b>
    <ul>
     <li><a href="#ref-for-authenticator-data">1.1. Specification Roadmap</a>
-    <li><a href="#ref-for-authenticator-data①">4. Terminology</a> <a href="#ref-for-authenticator-data②">(2)</a>
-    <li><a href="#ref-for-authenticator-data③">5.1.4.1. PublicKeyCredential’s [[DiscoverFromExternalSource]](origin, options, sameOriginWithAncestors) Method</a>
-    <li><a href="#ref-for-authenticator-data④">5.2.1. Information About Public Key Credential (interface AuthenticatorAttestationResponse)</a> <a href="#ref-for-authenticator-data⑤">(2)</a> <a href="#ref-for-authenticator-data⑥">(3)</a>
-    <li><a href="#ref-for-authenticator-data⑦">5.2.1.1. Easily accessing credential data</a> <a href="#ref-for-authenticator-data⑧">(2)</a> <a href="#ref-for-authenticator-data⑨">(3)</a> <a href="#ref-for-authenticator-data①⓪">(4)</a> <a href="#ref-for-authenticator-data①①">(5)</a>
-    <li><a href="#ref-for-authenticator-data①②">5.2.2. Web Authentication Assertion (interface AuthenticatorAssertionResponse)</a>
-    <li><a href="#ref-for-authenticator-data①③">5.7. WebAuthn Extensions Inputs and Outputs</a>
-    <li><a href="#ref-for-authenticator-data①④">6. WebAuthn Authenticator Model</a> <a href="#ref-for-authenticator-data①⑤">(2)</a>
-    <li><a href="#ref-for-authenticator-data①⑥">6.1. Authenticator Data</a> <a href="#ref-for-authenticator-data①⑦">(2)</a> <a href="#ref-for-authenticator-data①⑧">(3)</a> <a href="#ref-for-authenticator-data①⑨">(4)</a> <a href="#ref-for-authenticator-data②⓪">(5)</a> <a href="#ref-for-authenticator-data②①">(6)</a> <a href="#ref-for-authenticator-data②②">(7)</a> <a href="#ref-for-authenticator-data②③">(8)</a> <a href="#ref-for-authenticator-data②④">(9)</a> <a href="#ref-for-authenticator-data②⑤">(10)</a> <a href="#ref-for-authenticator-data②⑥">(11)</a>
-    <li><a href="#ref-for-authenticator-data②⑦">6.1.1. Signature Counter Considerations</a> <a href="#ref-for-authenticator-data②⑧">(2)</a> <a href="#ref-for-authenticator-data②⑨">(3)</a> <a href="#ref-for-authenticator-data③⓪">(4)</a>
-    <li><a href="#ref-for-authenticator-data③①">6.1.2. FIDO U2F Signature Format Compatibility</a> <a href="#ref-for-authenticator-data③②">(2)</a> <a href="#ref-for-authenticator-data③③">(3)</a>
-    <li><a href="#ref-for-authenticator-data③④">6.1.3. Credential Backup State</a>
-    <li><a href="#ref-for-authenticator-data③⑤">6.3.2. The authenticatorMakeCredential Operation</a>
-    <li><a href="#ref-for-authenticator-data③⑥">6.3.3. The authenticatorGetAssertion Operation</a>
-    <li><a href="#ref-for-authenticator-data③⑦">6.5. Attestation</a> <a href="#ref-for-authenticator-data③⑧">(2)</a>
-    <li><a href="#ref-for-authenticator-data③⑨">6.5.1. Attested Credential Data</a>
-    <li><a href="#ref-for-authenticator-data④⓪">6.5.2. Attestation Statement Formats</a> <a href="#ref-for-authenticator-data④①">(2)</a>
-    <li><a href="#ref-for-authenticator-data④②">6.5.4. Generating an Attestation Object</a>
-    <li><a href="#ref-for-authenticator-data④③">7.1. Registering a New Credential</a>
-    <li><a href="#ref-for-authenticator-data④④">8.5. Android SafetyNet Attestation Statement Format</a>
-    <li><a href="#ref-for-authenticator-data④⑤">9.5. Authenticator Extension Processing</a> <a href="#ref-for-authenticator-data④⑥">(2)</a>
-    <li><a href="#ref-for-authenticator-data④⑦">10.2.1. User Verification Method Extension (uvm)</a>
-    <li><a href="#ref-for-authenticator-data④⑧">13.1. Credential ID Unsigned</a>
-    <li><a href="#ref-for-authenticator-data④⑨">13.3.1. Attestation Certificate Hierarchy</a>
+    <li><a href="#ref-for-authenticator-data①">4. Terminology</a> <a href="#ref-for-authenticator-data②">(2)</a> <a href="#ref-for-authenticator-data③">(3)</a> <a href="#ref-for-authenticator-data④">(4)</a>
+    <li><a href="#ref-for-authenticator-data⑤">5.1.4.1. PublicKeyCredential’s [[DiscoverFromExternalSource]](origin, options, sameOriginWithAncestors) Method</a>
+    <li><a href="#ref-for-authenticator-data⑥">5.2.1. Information About Public Key Credential (interface AuthenticatorAttestationResponse)</a> <a href="#ref-for-authenticator-data⑦">(2)</a> <a href="#ref-for-authenticator-data⑧">(3)</a>
+    <li><a href="#ref-for-authenticator-data⑨">5.2.1.1. Easily accessing credential data</a> <a href="#ref-for-authenticator-data①⓪">(2)</a> <a href="#ref-for-authenticator-data①①">(3)</a> <a href="#ref-for-authenticator-data①②">(4)</a> <a href="#ref-for-authenticator-data①③">(5)</a>
+    <li><a href="#ref-for-authenticator-data①④">5.2.2. Web Authentication Assertion (interface AuthenticatorAssertionResponse)</a>
+    <li><a href="#ref-for-authenticator-data①⑤">5.7. WebAuthn Extensions Inputs and Outputs</a>
+    <li><a href="#ref-for-authenticator-data①⑥">6. WebAuthn Authenticator Model</a> <a href="#ref-for-authenticator-data①⑦">(2)</a>
+    <li><a href="#ref-for-authenticator-data①⑧">6.1. Authenticator Data</a> <a href="#ref-for-authenticator-data①⑨">(2)</a> <a href="#ref-for-authenticator-data②⓪">(3)</a> <a href="#ref-for-authenticator-data②①">(4)</a> <a href="#ref-for-authenticator-data②②">(5)</a> <a href="#ref-for-authenticator-data②③">(6)</a> <a href="#ref-for-authenticator-data②④">(7)</a> <a href="#ref-for-authenticator-data②⑤">(8)</a> <a href="#ref-for-authenticator-data②⑥">(9)</a> <a href="#ref-for-authenticator-data②⑦">(10)</a> <a href="#ref-for-authenticator-data②⑧">(11)</a>
+    <li><a href="#ref-for-authenticator-data②⑨">6.1.1. Signature Counter Considerations</a> <a href="#ref-for-authenticator-data③⓪">(2)</a> <a href="#ref-for-authenticator-data③①">(3)</a> <a href="#ref-for-authenticator-data③②">(4)</a>
+    <li><a href="#ref-for-authenticator-data③③">6.1.2. FIDO U2F Signature Format Compatibility</a> <a href="#ref-for-authenticator-data③④">(2)</a> <a href="#ref-for-authenticator-data③⑤">(3)</a>
+    <li><a href="#ref-for-authenticator-data③⑥">6.1.3. Credential Backup State</a>
+    <li><a href="#ref-for-authenticator-data③⑦">6.3.2. The authenticatorMakeCredential Operation</a>
+    <li><a href="#ref-for-authenticator-data③⑧">6.3.3. The authenticatorGetAssertion Operation</a>
+    <li><a href="#ref-for-authenticator-data③⑨">6.5. Attestation</a> <a href="#ref-for-authenticator-data④⓪">(2)</a>
+    <li><a href="#ref-for-authenticator-data④①">6.5.1. Attested Credential Data</a>
+    <li><a href="#ref-for-authenticator-data④②">6.5.2. Attestation Statement Formats</a> <a href="#ref-for-authenticator-data④③">(2)</a>
+    <li><a href="#ref-for-authenticator-data④④">6.5.4. Generating an Attestation Object</a>
+    <li><a href="#ref-for-authenticator-data④⑤">7.1. Registering a New Credential</a>
+    <li><a href="#ref-for-authenticator-data④⑥">8.5. Android SafetyNet Attestation Statement Format</a>
+    <li><a href="#ref-for-authenticator-data④⑦">9.5. Authenticator Extension Processing</a> <a href="#ref-for-authenticator-data④⑧">(2)</a>
+    <li><a href="#ref-for-authenticator-data④⑨">10.2.1. User Verification Method Extension (uvm)</a>
+    <li><a href="#ref-for-authenticator-data⑤⓪">13.1. Credential ID Unsigned</a>
+    <li><a href="#ref-for-authenticator-data⑤①">13.3.1. Attestation Certificate Hierarchy</a>
    </ul>
   </aside>
   <aside class="dfn-panel" data-for="authdata-rpidhash">
@@ -13038,16 +13221,16 @@ <h2 class="no-num no-ref heading settled" id="issues-index"><span class="content
   <aside class="dfn-panel" data-for="authdata-flags">
    <b><a href="#authdata-flags">#authdata-flags</a></b><b>Referenced in:</b>
    <ul>
-    <li><a href="#ref-for-authdata-flags">4. Terminology</a> <a href="#ref-for-authdata-flags①">(2)</a>
-    <li><a href="#ref-for-authdata-flags②">5.8.6. User Verification Requirement Enumeration (enum UserVerificationRequirement)</a> <a href="#ref-for-authdata-flags③">(2)</a>
-    <li><a href="#ref-for-authdata-flags④">6.1. Authenticator Data</a> <a href="#ref-for-authdata-flags⑤">(2)</a> <a href="#ref-for-authdata-flags⑥">(3)</a> <a href="#ref-for-authdata-flags⑦">(4)</a> <a href="#ref-for-authdata-flags⑧">(5)</a> <a href="#ref-for-authdata-flags⑨">(6)</a> <a href="#ref-for-authdata-flags①⓪">(7)</a> <a href="#ref-for-authdata-flags①①">(8)</a> <a href="#ref-for-authdata-flags①②">(9)</a> <a href="#ref-for-authdata-flags①③">(10)</a> <a href="#ref-for-authdata-flags①④">(11)</a>
-    <li><a href="#ref-for-authdata-flags①⑤">6.1.2. FIDO U2F Signature Format Compatibility</a>
-    <li><a href="#ref-for-authdata-flags①⑥">6.1.3. Credential Backup State</a> <a href="#ref-for-authdata-flags①⑦">(2)</a> <a href="#ref-for-authdata-flags①⑧">(3)</a> <a href="#ref-for-authdata-flags①⑨">(4)</a> <a href="#ref-for-authdata-flags②⓪">(5)</a> <a href="#ref-for-authdata-flags②①">(6)</a> <a href="#ref-for-authdata-flags②②">(7)</a> <a href="#ref-for-authdata-flags②③">(8)</a> <a href="#ref-for-authdata-flags②④">(9)</a>
-    <li><a href="#ref-for-authdata-flags②⑤">6.2.3. Authentication Factor Capability</a> <a href="#ref-for-authdata-flags②⑥">(2)</a> <a href="#ref-for-authdata-flags②⑦">(3)</a>
-    <li><a href="#ref-for-authdata-flags②⑧">7.1. Registering a New Credential</a> <a href="#ref-for-authdata-flags②⑨">(2)</a> <a href="#ref-for-authdata-flags③⓪">(3)</a> <a href="#ref-for-authdata-flags③①">(4)</a>
-    <li><a href="#ref-for-authdata-flags③②">7.2. Verifying an Authentication Assertion</a> <a href="#ref-for-authdata-flags③③">(2)</a> <a href="#ref-for-authdata-flags③④">(3)</a>
-    <li><a href="#ref-for-authdata-flags③⑤">10.1.4. Pseudo-random function extension (prf)</a>
-    <li><a href="#ref-for-authdata-flags③⑥">14.3. Authenticator-local Biometric Recognition</a>
+    <li><a href="#ref-for-authdata-flags">4. Terminology</a> <a href="#ref-for-authdata-flags①">(2)</a> <a href="#ref-for-authdata-flags②">(3)</a> <a href="#ref-for-authdata-flags③">(4)</a>
+    <li><a href="#ref-for-authdata-flags④">5.8.6. User Verification Requirement Enumeration (enum UserVerificationRequirement)</a> <a href="#ref-for-authdata-flags⑤">(2)</a>
+    <li><a href="#ref-for-authdata-flags⑥">6.1. Authenticator Data</a> <a href="#ref-for-authdata-flags⑦">(2)</a> <a href="#ref-for-authdata-flags⑧">(3)</a> <a href="#ref-for-authdata-flags⑨">(4)</a> <a href="#ref-for-authdata-flags①⓪">(5)</a> <a href="#ref-for-authdata-flags①①">(6)</a> <a href="#ref-for-authdata-flags①②">(7)</a> <a href="#ref-for-authdata-flags①③">(8)</a> <a href="#ref-for-authdata-flags①④">(9)</a> <a href="#ref-for-authdata-flags①⑤">(10)</a> <a href="#ref-for-authdata-flags①⑥">(11)</a>
+    <li><a href="#ref-for-authdata-flags①⑦">6.1.2. FIDO U2F Signature Format Compatibility</a>
+    <li><a href="#ref-for-authdata-flags①⑧">6.1.3. Credential Backup State</a> <a href="#ref-for-authdata-flags①⑨">(2)</a> <a href="#ref-for-authdata-flags②⓪">(3)</a> <a href="#ref-for-authdata-flags②①">(4)</a> <a href="#ref-for-authdata-flags②②">(5)</a> <a href="#ref-for-authdata-flags②③">(6)</a> <a href="#ref-for-authdata-flags②④">(7)</a> <a href="#ref-for-authdata-flags②⑤">(8)</a> <a href="#ref-for-authdata-flags②⑥">(9)</a>
+    <li><a href="#ref-for-authdata-flags②⑦">6.2.3. Authentication Factor Capability</a> <a href="#ref-for-authdata-flags②⑧">(2)</a> <a href="#ref-for-authdata-flags②⑨">(3)</a>
+    <li><a href="#ref-for-authdata-flags③⓪">7.1. Registering a New Credential</a> <a href="#ref-for-authdata-flags③①">(2)</a> <a href="#ref-for-authdata-flags③②">(3)</a> <a href="#ref-for-authdata-flags③③">(4)</a> <a href="#ref-for-authdata-flags③④">(5)</a> <a href="#ref-for-authdata-flags③⑤">(6)</a>
+    <li><a href="#ref-for-authdata-flags③⑥">7.2. Verifying an Authentication Assertion</a> <a href="#ref-for-authdata-flags③⑦">(2)</a> <a href="#ref-for-authdata-flags③⑧">(3)</a> <a href="#ref-for-authdata-flags③⑨">(4)</a>
+    <li><a href="#ref-for-authdata-flags④⓪">10.1.4. Pseudo-random function extension (prf)</a>
+    <li><a href="#ref-for-authdata-flags④①">14.3. Authenticator-local Biometric Recognition</a>
    </ul>
   </aside>
   <aside class="dfn-panel" data-for="authdata-flags-up">
@@ -13074,16 +13257,19 @@ <h2 class="no-num no-ref heading settled" id="issues-index"><span class="content
   <aside class="dfn-panel" data-for="authdata-flags-be">
    <b><a href="#authdata-flags-be">#authdata-flags-be</a></b><b>Referenced in:</b>
    <ul>
-    <li><a href="#ref-for-authdata-flags-be">6.1.3. Credential Backup State</a> <a href="#ref-for-authdata-flags-be①">(2)</a> <a href="#ref-for-authdata-flags-be②">(3)</a> <a href="#ref-for-authdata-flags-be③">(4)</a> <a href="#ref-for-authdata-flags-be④">(5)</a>
-    <li><a href="#ref-for-authdata-flags-be⑤">7.1. Registering a New Credential</a>
+    <li><a href="#ref-for-authdata-flags-be">4. Terminology</a>
+    <li><a href="#ref-for-authdata-flags-be①">6.1.3. Credential Backup State</a> <a href="#ref-for-authdata-flags-be②">(2)</a> <a href="#ref-for-authdata-flags-be③">(3)</a> <a href="#ref-for-authdata-flags-be④">(4)</a> <a href="#ref-for-authdata-flags-be⑤">(5)</a>
+    <li><a href="#ref-for-authdata-flags-be⑥">7.1. Registering a New Credential</a> <a href="#ref-for-authdata-flags-be⑦">(2)</a>
+    <li><a href="#ref-for-authdata-flags-be⑧">7.2. Verifying an Authentication Assertion</a>
    </ul>
   </aside>
   <aside class="dfn-panel" data-for="authdata-flags-bs">
    <b><a href="#authdata-flags-bs">#authdata-flags-bs</a></b><b>Referenced in:</b>
    <ul>
-    <li><a href="#ref-for-authdata-flags-bs">6.1.3. Credential Backup State</a> <a href="#ref-for-authdata-flags-bs①">(2)</a> <a href="#ref-for-authdata-flags-bs②">(3)</a> <a href="#ref-for-authdata-flags-bs③">(4)</a> <a href="#ref-for-authdata-flags-bs④">(5)</a> <a href="#ref-for-authdata-flags-bs⑤">(6)</a>
-    <li><a href="#ref-for-authdata-flags-bs⑥">7.1. Registering a New Credential</a>
-    <li><a href="#ref-for-authdata-flags-bs⑦">7.2. Verifying an Authentication Assertion</a>
+    <li><a href="#ref-for-authdata-flags-bs">4. Terminology</a>
+    <li><a href="#ref-for-authdata-flags-bs①">6.1.3. Credential Backup State</a> <a href="#ref-for-authdata-flags-bs②">(2)</a> <a href="#ref-for-authdata-flags-bs③">(3)</a> <a href="#ref-for-authdata-flags-bs④">(4)</a> <a href="#ref-for-authdata-flags-bs⑤">(5)</a> <a href="#ref-for-authdata-flags-bs⑥">(6)</a>
+    <li><a href="#ref-for-authdata-flags-bs⑦">7.1. Registering a New Credential</a> <a href="#ref-for-authdata-flags-bs⑧">(2)</a>
+    <li><a href="#ref-for-authdata-flags-bs⑨">7.2. Verifying an Authentication Assertion</a> <a href="#ref-for-authdata-flags-bs①⓪">(2)</a>
    </ul>
   </aside>
   <aside class="dfn-panel" data-for="authdata-flags-at">
@@ -13101,9 +13287,10 @@ <h2 class="no-num no-ref heading settled" id="issues-index"><span class="content
   <aside class="dfn-panel" data-for="authdata-signcount">
    <b><a href="#authdata-signcount">#authdata-signcount</a></b><b>Referenced in:</b>
    <ul>
-    <li><a href="#ref-for-authdata-signcount">6.1.1. Signature Counter Considerations</a> <a href="#ref-for-authdata-signcount①">(2)</a> <a href="#ref-for-authdata-signcount②">(3)</a> <a href="#ref-for-authdata-signcount③">(4)</a>
-    <li><a href="#ref-for-authdata-signcount④">7.1. Registering a New Credential</a>
-    <li><a href="#ref-for-authdata-signcount⑤">7.2. Verifying an Authentication Assertion</a> <a href="#ref-for-authdata-signcount⑥">(2)</a> <a href="#ref-for-authdata-signcount⑦">(3)</a>
+    <li><a href="#ref-for-authdata-signcount">4. Terminology</a>
+    <li><a href="#ref-for-authdata-signcount①">6.1.1. Signature Counter Considerations</a> <a href="#ref-for-authdata-signcount②">(2)</a> <a href="#ref-for-authdata-signcount③">(3)</a> <a href="#ref-for-authdata-signcount④">(4)</a>
+    <li><a href="#ref-for-authdata-signcount⑤">7.1. Registering a New Credential</a>
+    <li><a href="#ref-for-authdata-signcount⑥">7.2. Verifying an Authentication Assertion</a> <a href="#ref-for-authdata-signcount⑦">(2)</a> <a href="#ref-for-authdata-signcount⑧">(3)</a>
    </ul>
   </aside>
   <aside class="dfn-panel" data-for="authdata-attestedcredentialdata">
@@ -13115,10 +13302,10 @@ <h2 class="no-num no-ref heading settled" id="issues-index"><span class="content
     <li><a href="#ref-for-authdata-attestedcredentialdata④">6.1.2. FIDO U2F Signature Format Compatibility</a>
     <li><a href="#ref-for-authdata-attestedcredentialdata⑤">6.3.2. The authenticatorMakeCredential Operation</a>
     <li><a href="#ref-for-authdata-attestedcredentialdata⑥">6.3.3. The authenticatorGetAssertion Operation</a>
-    <li><a href="#ref-for-authdata-attestedcredentialdata⑦">7.1. Registering a New Credential</a> <a href="#ref-for-authdata-attestedcredentialdata⑧">(2)</a>
-    <li><a href="#ref-for-authdata-attestedcredentialdata⑨">8.3. TPM Attestation Statement Format</a>
-    <li><a href="#ref-for-authdata-attestedcredentialdata①⓪">8.4. Android Key Attestation Statement Format</a>
-    <li><a href="#ref-for-authdata-attestedcredentialdata①①">8.6. FIDO U2F Attestation Statement Format</a> <a href="#ref-for-authdata-attestedcredentialdata①②">(2)</a>
+    <li><a href="#ref-for-authdata-attestedcredentialdata⑦">7.1. Registering a New Credential</a>
+    <li><a href="#ref-for-authdata-attestedcredentialdata⑧">8.3. TPM Attestation Statement Format</a>
+    <li><a href="#ref-for-authdata-attestedcredentialdata⑨">8.4. Android Key Attestation Statement Format</a>
+    <li><a href="#ref-for-authdata-attestedcredentialdata①⓪">8.6. FIDO U2F Attestation Statement Format</a> <a href="#ref-for-authdata-attestedcredentialdata①①">(2)</a>
    </ul>
   </aside>
   <aside class="dfn-panel" data-for="authdata-extensions">
@@ -13148,9 +13335,7 @@ <h2 class="no-num no-ref heading settled" id="issues-index"><span class="content
     <li><a href="#ref-for-signature-counter②">6.1.1. Signature Counter Considerations</a> <a href="#ref-for-signature-counter③">(2)</a> <a href="#ref-for-signature-counter④">(3)</a> <a href="#ref-for-signature-counter⑤">(4)</a> <a href="#ref-for-signature-counter⑥">(5)</a> <a href="#ref-for-signature-counter⑦">(6)</a> <a href="#ref-for-signature-counter⑧">(7)</a> <a href="#ref-for-signature-counter⑨">(8)</a> <a href="#ref-for-signature-counter①⓪">(9)</a> <a href="#ref-for-signature-counter①①">(10)</a> <a href="#ref-for-signature-counter①②">(11)</a> <a href="#ref-for-signature-counter①③">(12)</a>
     <li><a href="#ref-for-signature-counter①④">6.3.2. The authenticatorMakeCredential Operation</a> <a href="#ref-for-signature-counter①⑤">(2)</a> <a href="#ref-for-signature-counter①⑥">(3)</a> <a href="#ref-for-signature-counter①⑦">(4)</a> <a href="#ref-for-signature-counter①⑧">(5)</a> <a href="#ref-for-signature-counter①⑨">(6)</a>
     <li><a href="#ref-for-signature-counter②⓪">6.3.3. The authenticatorGetAssertion Operation</a> <a href="#ref-for-signature-counter②①">(2)</a> <a href="#ref-for-signature-counter②②">(3)</a> <a href="#ref-for-signature-counter②③">(4)</a>
-    <li><a href="#ref-for-signature-counter②④">7.1. Registering a New Credential</a>
-    <li><a href="#ref-for-signature-counter②⑤">7.2. Verifying an Authentication Assertion</a>
-    <li><a href="#ref-for-signature-counter②⑥">11.5. Add Credential</a> <a href="#ref-for-signature-counter②⑦">(2)</a>
+    <li><a href="#ref-for-signature-counter②④">11.5. Add Credential</a> <a href="#ref-for-signature-counter②⑤">(2)</a>
    </ul>
   </aside>
   <aside class="dfn-panel" data-for="authenticator-type">
@@ -13438,20 +13623,20 @@ <h2 class="no-num no-ref heading settled" id="issues-index"><span class="content
   <aside class="dfn-panel" data-for="attestation-statement">
    <b><a href="#attestation-statement">#attestation-statement</a></b><b>Referenced in:</b>
    <ul>
-    <li><a href="#ref-for-attestation-statement">4. Terminology</a> <a href="#ref-for-attestation-statement①">(2)</a>
-    <li><a href="#ref-for-attestation-statement②">5.1.3. Create a New Credential - PublicKeyCredential’s [[Create]](origin, options, sameOriginWithAncestors) Method</a> <a href="#ref-for-attestation-statement③">(2)</a>
-    <li><a href="#ref-for-attestation-statement④">5.2.1. Information About Public Key Credential (interface AuthenticatorAttestationResponse)</a> <a href="#ref-for-attestation-statement⑤">(2)</a> <a href="#ref-for-attestation-statement⑥">(3)</a>
-    <li><a href="#ref-for-attestation-statement⑦">5.4.7. Attestation Conveyance Preference Enumeration (enum AttestationConveyancePreference)</a> <a href="#ref-for-attestation-statement⑧">(2)</a> <a href="#ref-for-attestation-statement⑨">(3)</a> <a href="#ref-for-attestation-statement①⓪">(4)</a> <a href="#ref-for-attestation-statement①①">(5)</a> <a href="#ref-for-attestation-statement①②">(6)</a> <a href="#ref-for-attestation-statement①③">(7)</a> <a href="#ref-for-attestation-statement①④">(8)</a> <a href="#ref-for-attestation-statement①⑤">(9)</a>
-    <li><a href="#ref-for-attestation-statement①⑥">6.2.3. Authentication Factor Capability</a>
-    <li><a href="#ref-for-attestation-statement①⑦">6.5. Attestation</a> <a href="#ref-for-attestation-statement①⑧">(2)</a> <a href="#ref-for-attestation-statement①⑨">(3)</a> <a href="#ref-for-attestation-statement②⓪">(4)</a> <a href="#ref-for-attestation-statement②①">(5)</a> <a href="#ref-for-attestation-statement②②">(6)</a> <a href="#ref-for-attestation-statement②③">(7)</a> <a href="#ref-for-attestation-statement②④">(8)</a>
-    <li><a href="#ref-for-attestation-statement②⑤">6.5.2. Attestation Statement Formats</a> <a href="#ref-for-attestation-statement②⑥">(2)</a> <a href="#ref-for-attestation-statement②⑦">(3)</a> <a href="#ref-for-attestation-statement②⑧">(4)</a>
-    <li><a href="#ref-for-attestation-statement②⑨">6.5.3. Attestation Types</a> <a href="#ref-for-attestation-statement③⓪">(2)</a> <a href="#ref-for-attestation-statement③①">(3)</a> <a href="#ref-for-attestation-statement③②">(4)</a> <a href="#ref-for-attestation-statement③③">(5)</a> <a href="#ref-for-attestation-statement③④">(6)</a>
-    <li><a href="#ref-for-attestation-statement③⑤">7.1. Registering a New Credential</a>
-    <li><a href="#ref-for-attestation-statement③⑥">8.7. None Attestation Statement Format</a>
-    <li><a href="#ref-for-attestation-statement③⑦">13.3.2. Attestation Certificate and Attestation Certificate CA Compromise</a>
-    <li><a href="#ref-for-attestation-statement③⑧">13.4.1. Security Benefits for WebAuthn Relying Parties</a>
-    <li><a href="#ref-for-attestation-statement③⑨">13.4.4. Attestation Limitations</a> <a href="#ref-for-attestation-statement④⓪">(2)</a> <a href="#ref-for-attestation-statement④①">(3)</a>
-    <li><a href="#ref-for-attestation-statement④②">14.1. De-anonymization Prevention Measures</a>
+    <li><a href="#ref-for-attestation-statement">4. Terminology</a> <a href="#ref-for-attestation-statement①">(2)</a> <a href="#ref-for-attestation-statement②">(3)</a>
+    <li><a href="#ref-for-attestation-statement③">5.1.3. Create a New Credential - PublicKeyCredential’s [[Create]](origin, options, sameOriginWithAncestors) Method</a> <a href="#ref-for-attestation-statement④">(2)</a>
+    <li><a href="#ref-for-attestation-statement⑤">5.2.1. Information About Public Key Credential (interface AuthenticatorAttestationResponse)</a> <a href="#ref-for-attestation-statement⑥">(2)</a> <a href="#ref-for-attestation-statement⑦">(3)</a>
+    <li><a href="#ref-for-attestation-statement⑧">5.4.7. Attestation Conveyance Preference Enumeration (enum AttestationConveyancePreference)</a> <a href="#ref-for-attestation-statement⑨">(2)</a> <a href="#ref-for-attestation-statement①⓪">(3)</a> <a href="#ref-for-attestation-statement①①">(4)</a> <a href="#ref-for-attestation-statement①②">(5)</a> <a href="#ref-for-attestation-statement①③">(6)</a> <a href="#ref-for-attestation-statement①④">(7)</a> <a href="#ref-for-attestation-statement①⑤">(8)</a> <a href="#ref-for-attestation-statement①⑥">(9)</a>
+    <li><a href="#ref-for-attestation-statement①⑦">6.2.3. Authentication Factor Capability</a>
+    <li><a href="#ref-for-attestation-statement①⑧">6.5. Attestation</a> <a href="#ref-for-attestation-statement①⑨">(2)</a> <a href="#ref-for-attestation-statement②⓪">(3)</a> <a href="#ref-for-attestation-statement②①">(4)</a> <a href="#ref-for-attestation-statement②②">(5)</a> <a href="#ref-for-attestation-statement②③">(6)</a> <a href="#ref-for-attestation-statement②④">(7)</a> <a href="#ref-for-attestation-statement②⑤">(8)</a>
+    <li><a href="#ref-for-attestation-statement②⑥">6.5.2. Attestation Statement Formats</a> <a href="#ref-for-attestation-statement②⑦">(2)</a> <a href="#ref-for-attestation-statement②⑧">(3)</a> <a href="#ref-for-attestation-statement②⑨">(4)</a>
+    <li><a href="#ref-for-attestation-statement③⓪">6.5.3. Attestation Types</a> <a href="#ref-for-attestation-statement③①">(2)</a> <a href="#ref-for-attestation-statement③②">(3)</a> <a href="#ref-for-attestation-statement③③">(4)</a> <a href="#ref-for-attestation-statement③④">(5)</a> <a href="#ref-for-attestation-statement③⑤">(6)</a>
+    <li><a href="#ref-for-attestation-statement③⑥">7.1. Registering a New Credential</a>
+    <li><a href="#ref-for-attestation-statement③⑦">8.7. None Attestation Statement Format</a>
+    <li><a href="#ref-for-attestation-statement③⑧">13.3.2. Attestation Certificate and Attestation Certificate CA Compromise</a>
+    <li><a href="#ref-for-attestation-statement③⑨">13.4.1. Security Benefits for WebAuthn Relying Parties</a>
+    <li><a href="#ref-for-attestation-statement④⓪">13.4.4. Attestation Limitations</a> <a href="#ref-for-attestation-statement④①">(2)</a> <a href="#ref-for-attestation-statement④②">(3)</a>
+    <li><a href="#ref-for-attestation-statement④③">14.1. De-anonymization Prevention Measures</a>
    </ul>
   </aside>
   <aside class="dfn-panel" data-for="attestation-statement-format">
@@ -13515,7 +13700,7 @@ <h2 class="no-num no-ref heading settled" id="issues-index"><span class="content
     <li><a href="#ref-for-authdata-attestedcredentialdata-credentialid">5.1.3. Create a New Credential - PublicKeyCredential’s [[Create]](origin, options, sameOriginWithAncestors) Method</a>
     <li><a href="#ref-for-authdata-attestedcredentialdata-credentialid①">6.1. Authenticator Data</a> <a href="#ref-for-authdata-attestedcredentialdata-credentialid②">(2)</a>
     <li><a href="#ref-for-authdata-attestedcredentialdata-credentialid③">6.5.1. Attested Credential Data</a>
-    <li><a href="#ref-for-authdata-attestedcredentialdata-credentialid④">7.1. Registering a New Credential</a> <a href="#ref-for-authdata-attestedcredentialdata-credentialid⑤">(2)</a> <a href="#ref-for-authdata-attestedcredentialdata-credentialid⑥">(3)</a> <a href="#ref-for-authdata-attestedcredentialdata-credentialid⑦">(4)</a> <a href="#ref-for-authdata-attestedcredentialdata-credentialid⑧">(5)</a> <a href="#ref-for-authdata-attestedcredentialdata-credentialid⑨">(6)</a>
+    <li><a href="#ref-for-authdata-attestedcredentialdata-credentialid④">7.1. Registering a New Credential</a> <a href="#ref-for-authdata-attestedcredentialdata-credentialid⑤">(2)</a> <a href="#ref-for-authdata-attestedcredentialdata-credentialid⑥">(3)</a>
    </ul>
   </aside>
   <aside class="dfn-panel" data-for="authdata-attestedcredentialdata-credentialpublickey">
@@ -13524,10 +13709,10 @@ <h2 class="no-num no-ref heading settled" id="issues-index"><span class="content
     <li><a href="#ref-for-authdata-attestedcredentialdata-credentialpublickey">5.2.1.1. Easily accessing credential data</a>
     <li><a href="#ref-for-authdata-attestedcredentialdata-credentialpublickey①">6.1. Authenticator Data</a> <a href="#ref-for-authdata-attestedcredentialdata-credentialpublickey②">(2)</a> <a href="#ref-for-authdata-attestedcredentialdata-credentialpublickey③">(3)</a>
     <li><a href="#ref-for-authdata-attestedcredentialdata-credentialpublickey④">6.5.1.1. Examples of credentialPublicKey Values Encoded in COSE_Key Format</a>
-    <li><a href="#ref-for-authdata-attestedcredentialdata-credentialpublickey⑤">7.1. Registering a New Credential</a> <a href="#ref-for-authdata-attestedcredentialdata-credentialpublickey⑥">(2)</a>
-    <li><a href="#ref-for-authdata-attestedcredentialdata-credentialpublickey⑦">8.2. Packed Attestation Statement Format</a>
-    <li><a href="#ref-for-authdata-attestedcredentialdata-credentialpublickey⑧">8.3. TPM Attestation Statement Format</a>
-    <li><a href="#ref-for-authdata-attestedcredentialdata-credentialpublickey⑨">8.4. Android Key Attestation Statement Format</a>
+    <li><a href="#ref-for-authdata-attestedcredentialdata-credentialpublickey⑤">7.1. Registering a New Credential</a>
+    <li><a href="#ref-for-authdata-attestedcredentialdata-credentialpublickey⑥">8.2. Packed Attestation Statement Format</a>
+    <li><a href="#ref-for-authdata-attestedcredentialdata-credentialpublickey⑦">8.3. TPM Attestation Statement Format</a>
+    <li><a href="#ref-for-authdata-attestedcredentialdata-credentialpublickey⑧">8.4. Android Key Attestation Statement Format</a>
    </ul>
   </aside>
   <aside class="dfn-panel" data-for="signing-procedure">
@@ -13694,15 +13879,16 @@ <h2 class="no-num no-ref heading settled" id="issues-index"><span class="content
   <aside class="dfn-panel" data-for="webauthn-extensions">
    <b><a href="#webauthn-extensions">#webauthn-extensions</a></b><b>Referenced in:</b>
    <ul>
-    <li><a href="#ref-for-webauthn-extensions">5.4. Options for Credential Creation (dictionary PublicKeyCredentialCreationOptions)</a>
-    <li><a href="#ref-for-webauthn-extensions①">5.5. Options for Assertion Generation (dictionary PublicKeyCredentialRequestOptions)</a>
-    <li><a href="#ref-for-webauthn-extensions②">5.7. WebAuthn Extensions Inputs and Outputs</a>
-    <li><a href="#ref-for-webauthn-extensions③">5.7.1. Authentication Extensions Client Inputs (dictionary AuthenticationExtensionsClientInputs)</a>
-    <li><a href="#ref-for-webauthn-extensions④">5.7.2. Authentication Extensions Client Outputs (dictionary AuthenticationExtensionsClientOutputs)</a>
-    <li><a href="#ref-for-webauthn-extensions⑤">5.7.3. Authentication Extensions Authenticator Inputs (CDDL type AuthenticationExtensionsAuthenticatorInputs)</a>
-    <li><a href="#ref-for-webauthn-extensions⑥">5.7.4. Authentication Extensions Authenticator Outputs (CDDL type AuthenticationExtensionsAuthenticatorOutputs)</a>
-    <li><a href="#ref-for-webauthn-extensions⑦">8.1. Attestation Statement Format Identifiers</a>
-    <li><a href="#ref-for-webauthn-extensions⑧">9. WebAuthn Extensions</a> <a href="#ref-for-webauthn-extensions⑨">(2)</a> <a href="#ref-for-webauthn-extensions①⓪">(3)</a>
+    <li><a href="#ref-for-webauthn-extensions">4. Terminology</a>
+    <li><a href="#ref-for-webauthn-extensions①">5.4. Options for Credential Creation (dictionary PublicKeyCredentialCreationOptions)</a>
+    <li><a href="#ref-for-webauthn-extensions②">5.5. Options for Assertion Generation (dictionary PublicKeyCredentialRequestOptions)</a>
+    <li><a href="#ref-for-webauthn-extensions③">5.7. WebAuthn Extensions Inputs and Outputs</a>
+    <li><a href="#ref-for-webauthn-extensions④">5.7.1. Authentication Extensions Client Inputs (dictionary AuthenticationExtensionsClientInputs)</a>
+    <li><a href="#ref-for-webauthn-extensions⑤">5.7.2. Authentication Extensions Client Outputs (dictionary AuthenticationExtensionsClientOutputs)</a>
+    <li><a href="#ref-for-webauthn-extensions⑥">5.7.3. Authentication Extensions Authenticator Inputs (CDDL type AuthenticationExtensionsAuthenticatorInputs)</a>
+    <li><a href="#ref-for-webauthn-extensions⑦">5.7.4. Authentication Extensions Authenticator Outputs (CDDL type AuthenticationExtensionsAuthenticatorOutputs)</a>
+    <li><a href="#ref-for-webauthn-extensions⑧">8.1. Attestation Statement Format Identifiers</a>
+    <li><a href="#ref-for-webauthn-extensions⑨">9. WebAuthn Extensions</a> <a href="#ref-for-webauthn-extensions①⓪">(2)</a> <a href="#ref-for-webauthn-extensions①①">(3)</a>
    </ul>
   </aside>
   <aside class="dfn-panel" data-for="registration-extension">