From 7b877b61af9c68415dd630d6da59a90e29927f99 Mon Sep 17 00:00:00 2001
From: Emil Lundberg <emil@yubico.com>
Date: Wed, 23 Aug 2023 15:38:51 +0200
Subject: [PATCH] Delete outdated note about checking registration UV with PRF
 extension

---
 index.bs | 2 --
 1 file changed, 2 deletions(-)

diff --git a/index.bs b/index.bs
index 4319fc955..7791214b3 100644
--- a/index.bs
+++ b/index.bs
@@ -6779,8 +6779,6 @@ Note: this extension may be implemented for [=authenticators=] that do not use [
        1. Set {{AuthenticationExtensionsPRFOutputs/enabled}} to the value of `hmac-secret` in the authenticator extensions output. If not present, set {{AuthenticationExtensionsPRFOutputs/enabled}} to [FALSE].
        1. Set {{AuthenticationExtensionsPRFOutputs/results}} to the decrypted PRF result(s), if any.
 
-Note: If PRF results are obtained during [=registration=] then the [=[RP]=] MUST inspect the [=UV=] bit in the [=flags=] of the response in order to determine the correct value of {{PublicKeyCredentialRequestOptions/userVerification}} for future [=assertions=]. Otherwise results from [=assertions=] may be inconsistent with those from the [=registration=].
-
 : Client extension processing ([=authentication extension|authentication=])
 ::
       1. If {{AuthenticationExtensionsPRFInputs/evalByCredential}} is not empty but {{PublicKeyCredentialRequestOptions/allowCredentials}} is empty, return a {{DOMException}} whose name is “{{NotSupportedError}}”.