What is the 'None' value for SameSite cookie attribute, and what security requirement must accompany it?

• A.SameSite=None sends the cookie only on top-level navigations (a Lax-like rule); the HttpOnly attribute must accompany it (enforced by browsers since Chrome 80), since cookies readable by scripts are rejected on cross-site requests, a check that applies to every cookie set with the attribute
• B.SameSite=None explicitly opts out of same-site restrictions, allowing the cookie to be sent on all cross-site requests; the Secure attribute is mandatory alongside it (enforced by browsers since Chrome 80) - SameSite=None without Secure is rejected by modern browsers
• C.SameSite=None blocks the cookie on all cross-site requests (a strict rule); a Domain attribute must accompany it (enforced since Chrome 90), since host-only cookies are rejected when None is set on the response by the server, a requirement that Chrome applies from the first request after the change