[dnssd] Re: WGLC for draft-ietf-dnssd-multi-qtypes

[Florian Obser <[e-mail]>]

Hi there,

the WGLC is now closed, apologies for closing it late[1].

The chairs see consensus that the document can progress.

The chairs also see consensus that the two issues raised by Tommy Jensen
in
https://mailarchive.ietf.org/arch/msg/dnssd/bQkA2274kKrzNcpFRlLoQif2u1M/
need to be addressed:

| (1) It seems to go without saying, but Section 3.3 for Client Response
| Processing never actually says that clients MUST/SHOULD NOT cache record
| types it receives that it didn't request. Should we? It seems like an attack
| vector if we are treating this response as the set as if every type was the
| QTYPE. This is expected for meta types, but in the case of querying for
| {AAAA, SVCB}, no client would expect A records to come back which could be
| cache poisoning for a name that was intended to be IPv6-only.
|
| (2) The security considerations section acknowledges the amplification attack
| this could enable, but it does not mention what Section 3.3's first bullet
| says about the server choosing to not process a request because it had too
| many types. I think it should in the spirit of giving obvious advice to
| implementors as it is currently implied but not stated. In fact, Section
| 3.2.2's normatives don't leave much room for an RFC novice to read "but you
| can also choose to defend against complex queries" from it.

Thanks,
Florian (for the chairs)

[1] Entirely my faul, I was a bit unclear on the process. Our AD Éric
explained to me that the document need not be perfect, we can still
close the WGLC.

On 2025-06-01 02:53 +02, Florian Obser <[e-mail]> wrote:
> Hi DNSSD people,
>
> As requested by the working group during IETF 122 in Bangkok, we are
> starting a Working Group Last Call (WGLC) for
> draft-ietf-dnssd-multi-qtypes.
>
> At the IETF 122 hackathon we had people working on implementing
> the draft and testing interoperability:
> https://mailarchive.ietf.org/arch/msg/dnssd/4Emt2GaVVL3zUD54eg2UJnVHAHo/
>
> This WGLC will last for two weeks until 2025-06-16 at 23:59 UTC. We
> are interested in hearing whether people have read this document and
> think it is ready for publication. We are also interested in hearing
> from people who think the document is not ready, or who see issues that
> need to be resolved before publication.
>
> The latest draft is available here:
> https://datatracker.ietf.org/doc/draft-ietf-dnssd-multi-qtypes/
>
> Please send responses to the DNSSD list as replies to this email
> before 2025-06-16 at 23:59 UTC.
>
> Thanks,
> Florian and Chris
>
> _______________________________________________
> dnssd mailing list -- [e-mail]
> To unsubscribe send an email to [e-mail]

-- 
In my defence, I have been left unsupervised.