Consider alternative to term "whitelist"

[MikeBishop]

Without getting into the current politics and history of the term, there are two instances of this term in SEMANTICS that don't appear to contribute substantial value versus using a less loaded choice.

Section 9.3.6:

There are significant risks in establishing a tunnel to arbitrary servers, particularly when the destination is a well-known or reserved TCP port that is not intended for Web traffic. For example, a CONNECT to "example.com:25" would suggest that the proxy connect to the reserved port for SMTP traffic; if allowed, that could trick the proxy into relaying spam email. Proxies that support CONNECT should restrict its use to a limited set of known ports or a configurable whitelist of safe request targets.

Here, "list" seems sufficient.

Section 17.12

An approach that limits such loss of privacy would be for a user agent to omit the sending of Accept-Language except for sites that have been whitelisted, perhaps via interaction after detecting a Vary header field that indicates language negotiation might be useful.

Perhaps "sites that have been explicitly permitted"?

[royfielding]

Good catch. I thought I already checked for those when I replaced man-in-the-middle.

[annevk]

For a direct replacement both safelist and allowlist have seen some uptake.