]> git.ipfire.org Git - thirdparty/knot-resolver.git/commit
docs: fix padding descriptions
authorVladimír Čunát <vladimir.cunat@nic.cz>
Sun, 13 Aug 2023 15:34:46 +0000 (17:34 +0200)
committerVladimír Čunát <vladimir.cunat@nic.cz>
Thu, 17 Aug 2023 14:01:02 +0000 (16:01 +0200)
commit09dd255d222c6b331c762ff85a5a1d6c37518f18
treeb94b1179a051e346eaae9bad6784e6fc4e135214
parent30efd07c44a75af1c99d8e36fceb602d6f2ef254
docs: fix padding descriptions

Mentioning just answers is misleading.  Padding is very important
for queries as well; for us that applies during forwarding over TLS.

Also describe /tls/auto_discovery as experimental in the
configuration  schema.  It's a rather dead experiment from long ago.
I hope it can't be confused with more recent things like
https://datatracker.ietf.org/doc/draft-ietf-dprive-unilateral-probing/
daemon/bindings/net_tlssrv.rst
doc/config-network-server-tls.rst
manager/knot_resolver_manager/datamodel/network_schema.py