Should link relations define the behaviour of the user agent following a link?

[darrelmiller]

This issue is a based on feedback from a SECDIR review:

If a user follows one of these links, should it replace the page content or
open separately? If it opens separately, should it autoclose when the action
(e.g. "login") completes, and if so how? (This is more ergonomic but creates
risk related to "clickjacking".) Should the page content be reloaded after a
login state change? * What format does "authenticated-as" provide? It seems
like the intent here would be to support a "chip" in the browser chrome showing
the logged-in user's name (and icon/picture?), but this would require
specifying the actual format of the resource, which is not done here.

https://datatracker.ietf.org/doc/review-ietf-httpapi-authentication-link-01-secdir-early-schwartz-2024-06-28/

The general question here is it expected for link relation types to define the behaviour of user agents that follow links?