default-request-timeout-millis ignored for netconf device

When creating mount point for netconf device according to
https://wiki.opendaylight.org/view/OpenDaylight_Controller:Config:Examples:Netconf#Spawning_Additional_Netconf_Connectors_While_the_Controller_is_Running

then the default value for default-request-timeout-millis is 60k. This can be confirmed in DS/operational.

But if I add following to the input and POST it into DS/config:
<max-connection-attempts xmlns="urn:opendaylight:params:xml:ns:yang:controller:md:sal:connector:netconf">3</max-connection-attempts>
<between-attempts-timeout-millis xmlns="urn:opendaylight:params:xml:ns:yang:controller:md:sal:connector:netconf">2000</between-attempts-timeout-millis>
<connection-timeout-millis xmlns="urn:opendaylight:params:xml:ns:yang:controller:md:sal:connector:netconf">10000</connection-timeout-millis>
<default-request-timeout-millis xmlns="urn:opendaylight:params:xml:ns:yang:controller:md:sal:connector:netconf">10000</default-request-timeout-millis>

then it gets correctly reflected in DS/operational but it still takes 60 seconds till the connection times out and so the whole connection ends up with failure after 205 seconds.

Is this the right parameter to control connection timeout? If not, what is the recommended way of setting up shorter connection timeout?