[dnsdir] Dnsdir last call review of draft-ietf-quic-v2-05

Vladimír Čunát via Datatracker <noreply@ietf.org> Wed, 12 October 2022 15:20 UTC

MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: Vladimír Čunát via Datatracker <noreply@ietf.org>
To: dnsdir@ietf.org
Cc: draft-ietf-quic-v2.all@ietf.org, last-call@ietf.org, quic@ietf.org
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <166558805987.17929.14678450917966646189@ietfa.amsl.com>
Reply-To: Vladimír Čunát <vladimir.cunat+ietf@nic.cz>
Date: Wed, 12 Oct 2022 08:20:59 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsdir/4au5YlD-cP80-UMa5WkioeV9DVk>
Subject: [dnsdir] Dnsdir last call review of draft-ietf-quic-v2-05

Reviewer: Vladimír Čunát
Review result: Ready with Nits

I see nothing in the draft affecting DNS specifically (though DoQ and DoH/3
exist).

I noticed one point that would be nice to clarify.  I see
> QUIC version 2 endpoints MUST implement the QUIC version 1
but on the other hand also
> Endpoints that support version 2 might continue support for version 1

and in my eyes these clash, as on protocol level I don't think it's possible to
implement but not support a version, though I'm not very knowledgeable about
QUIC details in particular.  (On SW level that makes sense, but that's not what
the RFC is about.)

[dnsdir] Dnsdir last call review of draft-ietf-qu… Vladimír Čunát via Datatracker
Re: [dnsdir] Dnsdir last call review of draft-iet… Martin Duke