6265bis should not normatively depend on the Public Suffix List

[sleevi]

Within 6265bis, the use of the PSL is currently specified normatively:

http-extensions/draft-ietf-httpbis-rfc6265bis.md

Lines 104 to 106 in 5469d51

	PSL:
	target: https://publicsuffix.org/list/
	title: "Public Suffix List"

Concrete suggestion: Move this to an informative reference, instead, and update the text relying upon it to capture this.

In 6265, this was effectively an informative reference, per Section 5.3's note. This is somewhat related to #1033 which moved it into terminology, instead of Section 5.4.

In terms of "rough consensus and running code", in terms of widely deployed clients, the algorithm specified in the Public Suffix List is not consistently implemented, the algorithm itself is ambiguous for edge cases, and perhaps most importantly, none of the major implementations ship the same version of the Public Suffix List. Several implementations, including Google Chrome, further fork and modify that list to support their implementation needs.

Thus, it's really more of an informative dependency, similar to how 6265 captured this problem. SAC070 similarly called out and acknowledged there may be many static lists used by applications, of differing versions and algorithms.

[sleevi]

@mikewest Also editorial and related to 6265bis

[mikewest]

I don't think it's pedantically "editorial" since it removes a normative reference, but I'm fine with doing so. Do you have a proposal for new text? If not, I'll make something up.