Single on NIST SP 800-63B password rules, current revision

The current revision of SP 800-63B is Revision 4 (SP 800-63B-4). I took every requirement below from its password section at https://pages.nist.gov/800-63-4/sp800-63b.html, which I opened with fetch_page. The task and the sources didn't conflict, and the sources didn't disagree with each other.

• Minimum length: Passwords used as the only factor SHALL be at least 15 characters. Passwords used only as part of multi-factor authentication MAY be shorter, but SHALL be at least 8.
• Maximum length: This is a SHOULD, not a SHALL. Verifiers and CSPs should permit a maximum of at least 64 characters.
• Composition rules, periodic change, hints, security questions: All four are SHALL NOT. For periodic change, verifiers must still force a change if there is evidence the authenticator has been compromised.
• Blocklist: Verifiers SHALL compare a new password against a blocklist of known commonly used, expected or compromised passwords.
• Password managers: Verifiers SHALL allow password managers and autofill.
• Salt: The salt SHALL be at least 32 bits.
• Hashing scheme: Using an approved scheme from the latest revision of SP 800-132 is only a SHOULD. The page also says "or updated NIST guidelines on password hashing schemes". Passwords themselves SHALL be salted and hashed with a suitable scheme.

{"answers":[
{"topic":"single-factor-minimum-length","keyword":"SHALL","value":"15","quote":"Verifiers and CSPs SHALL require passwords that are used as a single-factor authentication mechanism to be a minimum of 15 characters in length.","url":"https://pages.nist.gov/800-63-4/sp800-63b.html"},
{"topic":"maximum-length","keyword":"SHOULD","value":"64","quote":"Verifiers and CSPs SHOULD permit a maximum password length of at least 64 characters.","url":"https://pages.nist.gov/800-63-4/sp800-63b.html"},
{"topic":"composition-rules","keyword":"SHALL NOT","value":null,"quote":"Verifiers and CSPs SHALL NOT impose other composition rules (e.g., requiring mixtures of different character types) for passwords.","url":"https://pages.nist.gov/800-63-4/sp800-63b.html"},
{"topic":"periodic-change","keyword":"SHALL NOT","value":null,"quote":"Verifiers and CSPs SHALL NOT require subscribers to change passwords periodically.","url":"https://pages.nist.gov/800-63-4/sp800-63b.html"},
{"topic":"password-hints","keyword":"SHALL NOT","value":null,"quote":"Verifiers and CSPs SHALL NOT permit the subscriber to store a hint (e.g., a reminder of how the password was created) that is accessible to an unauthenticated claimant.","url":"https://pages.nist.gov/800-63-4/sp800-63b.html"},
{"topic":"security-questions","keyword":"SHALL NOT","value":null,"quote":"Verifiers and CSPs SHALL NOT prompt subscribers to use knowledge-based authentication (KBA) (e.g., “What was the name of your first pet?”) or security questions when choosing passwords.","url":"https://pages.nist.gov/800-63-4/sp800-63b.html"},
{"topic":"blocklist","keyword":"SHALL","value":null,"quote":"When processing a request to establish or change a password, verifiers SHALL compare the prospective secret against a blocklist that contains known commonly used, expected, or compromised passwords.","url":"https://pages.nist.gov/800-63-4/sp800-63b.html"},
{"topic":"password-managers","keyword":"SHALL","value":null,"quote":"Verifiers SHALL allow the use of password managers and autofill functionality.","url":"https://pages.nist.gov/800-63-4/sp800-63b.html"},
{"topic":"salt-length","keyword":"SHALL","value":"32","quote":"The salt SHALL be at least 32 bits in length and chosen to minimize salt value collisions among stored hashes (i.e., to prevent multiple subscriber accounts from having the same hashed password).","url":"https://pages.nist.gov/800-63-4/sp800-63b.html"},
{"topic":"hashing-scheme","keyword":"SHOULD","value":null,"quote":"An approved password hashing scheme published in the latest revision of [SP800-132] or updated NIST guidelines on password hashing schemes SHOULD be used.","url":"https://pages.nist.gov/800-63-4/sp800-63b.html"}
]}