nsd users - Dec 2018 - NSD and RFC 8482 (ANY queries)

Internet Draft draft-ietf-dnsop-refuse-any-07, soon RFC 8482, claims
that "An implementation of the subset-mode response to ANY queries was
implemented in NSD 4.1 in 2016." It is not clear to me how it is
implemented. I see in the code:

	if(q->qtype == TYPE_ANY && nsd->options->refuse_any &&
!q->tcp) {
		TC_SET(q->packet);
		return query_error(q, NSD_RC_OK);
	}

and in the documentation:

.B refuse\-any:\fR <yes or no>
Refuse queries of type ANY.  This is useful to stop query floods trying
to get large responses.  Note that rrl ratelimiting also has type ANY as
a ratelimiting type.  It sends truncation in response to UDP type ANY queries,
and it allows TCP type ANY queries like normal.
The default is no.

Code and documentation seem to agree. But sending TC is not one of the
three possibilities accepted by the RFC when you don't like ANY (the
future RFC says the opposite: "the TC bit SHOULD NOT be set on the
response"). Am I right in this assesment? Is there a plan to adapt NSD
to the RFC?

Hi,

I posted a (very simple) patch implementing draft-00 spec (answers subset
of available RRsets) to nsd-users maling list in 2016. But it was not
included to mainline.

  https://open.nlnetlabs.nl/pipermail/nsd-users/2016-February/002234.html

I don?t know whether ?NSD implementation? noted in draft-07 correnponds to
my patch.

Stephane Bortzmeyer <bortzmeyer at nic.fr>:
> Internet Draft draft-ietf-dnsop-refuse-any-07, soon RFC 8482, claims
> that "An implementation of the subset-mode response to ANY queries was
> implemented in NSD 4.1 in 2016." It is not clear to me how it is
> implemented. I see in the code
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.nlnetlabs.nl/pipermail/nsd-users/attachments/20181220/9150a1cb/attachment.htm>