Intdir telechat review of draft-ietf-quic-transport-33

Bernie Volz via Datatracker <> Mon, 04 January 2021 18:57 UTC

Return-Path: <>
Received: from (localhost [IPv6:::1]) by (Postfix) with ESMTP id DAFDA3A0FD7; Mon, 4 Jan 2021 10:57:12 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: Bernie Volz via Datatracker <>
Subject: Intdir telechat review of draft-ietf-quic-transport-33
X-Test-IDTracker: no
X-IETF-IDTracker: 7.24.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <>
Reply-To: Bernie Volz <>
Date: Mon, 04 Jan 2021 10:57:12 -0800
Archived-At: <>
X-Mailman-Version: 2.1.29
List-Id: Main mailing list of the IETF QUIC working group <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Mon, 04 Jan 2021 18:57:13 -0000

Reviewer: Bernie Volz
Review result: Ready

I am an assigned INT directorate reviewer for draft-ietf-quic-transport-33.
These comments were written primarily for the benefit of the Internet Area
Directors. Document editors and shepherd(s) should treat these comments just
like they would treat comments from any other IETF contributors and resolve
them along with any other Last Call comments that have been received. For more
details on the INT Directorate, see

Based on my review, if I was on the IESG I would ballot this document as NO

There is a lot here and the document seems well put together and thorough.

I didn’t notice any major or even minor issues with the document – it looks
like it has had lots of careful review to date. (The one minor typo is
“version” is misspelled as “verion” in the “DO NOT DEPLOY THIS VERSION OF QUIC”
text, which will be removed anyway.)

I also reviewed the document for the items listed at and the document fully
supports IPv6 (it support both IPv4 and IPv6 equally), deal with MTU and
fragmentation properly, and has no other issues listed at this link.

Therefore, I think this document is ready to advance.

-       Bernie Volz