On Wed, 2021-04-21 at 23:47 +0000, Wessels, Duane wrote: > > application. Applications must be coded and configured to make use > > of this filter. > > > > While it's good to point out that this feature exists, I do not think > > mandating it makes sense - implementers and operators might have other > > preferences for handling open-but-as-yet-unused TCP connections. (Also > > the lowercase 'must' is confusing.) > > It was not intended as a requirement, but rather to note that the application > needs to do some work to utilize them.
Ah! That makes a lot more sense, yes. > Hows this? > > These features are implemented as low-level socket options. > It is necessary for applications to be specifically coded and > configured to make use of them. To my non-native eyes this still smells like 'you should do this'. How about: These features are implemented as low-level socket options, and they are not activated automatically. If applications wish to use these features, they will need to make specific calls to set the right options, and administrators may need to configure the applications to make these calls. Kind regards, -- Peter van Dijk PowerDNS.COM BV - https://www.powerdns.com/ _______________________________________________ DNSOP mailing list DNSOP@ietf.org https://www.ietf.org/mailman/listinfo/dnsop
