Statement of intent regarding TLS server name identification (SNI)

[Alex // nytpu]

See §4 of the Gemini Specification:
> Use of the Server Name Indication (SNI) extension to TLS is also
> mandatory, to facilitate name-based virtual hosting.

If your client does not support SNI, then it is in violation of the
specification.

I make a motion that SNI should actually be mandatory to ensure clients
are following the specification (as apparently elpher and other clients
aren't). I don't want a flip-flopped version of tag soup where servers
have to cater to the lowest common denominator of clients even though
they are in clear violation of the specification.

-- 
Alex // nytpu
alex at nytpu.com
GPG Key: https://www.nytpu.com/files/pubkey.asc
Key fingerprint: 43A5 890C EE85 EA1F 8C88 9492 ECCD C07B 337B 8F5B
https://useplaintext.email/
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: not available
URL: <https://lists.orbitalfox.eu/archives/gemini/attachments/20201109/4d4e0409/attachment.sig>