You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Part of the work to prototype draft-ietf-dprive-xfr-over-tls
Adds 2 new parameters: xfrd-conn-reuse (default no) and tcp-idle-timeout (default 10)
If xfrd-conn-reuse: yes the secondary will utilise the existing the mechanisms in place (which are currently only used when XFRD_MAX_TCP is exhausted) to re-use connections
It will additionally leave those connections open and idle for tcp-idle-timeout, which is currently a fixed timeout. A later commit will add support for EDNS0 Keepalive, so the server can signal the timeout to use (as described in draft-ietf-dprive-xfr-over-tls)
Tested against BIND for multiple IXFR and AXFR on the same connection, for the same and different zones
NOTE: Encountered an issue with NSD reload behaviour and persistent XFR connections when trying to update the tpkg\long\testplan-axfr.dir test, will send separate email about this.
does not allow new queries to be made, the connection is closed.
Only existing queries and zone transfers are answered, new ones
are rejected by a close of the channel.
Instead of the xfrd-conn-reuse option, I'd like to have this enabled automatically when connecting over TLS (i.e. XoT) or when a KEEPALIVE EDNS0 option is detected with TCP.
So postponing merge until we have looked into that.
I think having the default on would be good, I thought an option might be useful so it could be disabled in case of interop problems (e.g a legacy XFR implementation behind a proxy).
Perhaps it should be configurable per upstream then? For example in the tls-auth: declaration?
It would be good to have tls-cert-bundle configurable per tls-auth: declaration too b.t.w.
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
*** FOR REVIEW ONLY AT THIS TIME***
xfrd-conn-reuse
(default no) andtcp-idle-timeout
(default 10)xfrd-conn-reuse: yes
the secondary will utilise the existing the mechanisms in place (which are currently only used whenXFRD_MAX_TCP
is exhausted) to re-use connectionstcp-idle-timeout
, which is currently a fixed timeout. A later commit will add support for EDNS0 Keepalive, so the server can signal the timeout to use (as described in draft-ietf-dprive-xfr-over-tls)tpkg\long\testplan-axfr.dir
test, will send separate email about this.