Éric Vyncke's No Objection on draft-ietf-quic-invariants-12: (with COMMENT)

Éric Vyncke via Datatracker <noreply@ietf.org> Tue, 05 January 2021 14:30 UTC

Return-Path: <noreply@ietf.org>
X-Original-To: quic@ietf.org
Delivered-To: quic@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 6C9E33A0F0F; Tue, 5 Jan 2021 06:30:12 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: Éric Vyncke via Datatracker <noreply@ietf.org>
To: The IESG <iesg@ietf.org>
Cc: draft-ietf-quic-invariants@ietf.org, quic-chairs@ietf.org, quic@ietf.org, quic-chairs@ietf.org, mnot@mnot.net
Subject: Éric Vyncke's No Objection on draft-ietf-quic-invariants-12: (with COMMENT)
X-Test-IDTracker: no
X-IETF-IDTracker: 7.24.0
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: Éric Vyncke <evyncke@cisco.com>
Message-ID: <160985701241.15364.12212123898568789044@ietfa.amsl.com>
Date: Tue, 05 Jan 2021 06:30:12 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/tZy5DCVp82ck-cYS2KgZSRitw6A>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.29
List-Id: Main mailing list of the IETF QUIC working group <quic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/quic>, <mailto:quic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/quic/>
List-Post: <mailto:quic@ietf.org>
List-Help: <mailto:quic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/quic>, <mailto:quic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 05 Jan 2021 14:30:12 -0000

Éric Vyncke has entered the following ballot position for
draft-ietf-quic-invariants-12: No Objection

When responding, please keep the subject line intact and reply to all
email addresses included in the To and CC lines. (Feel free to cut this
introductory paragraph, however.)

Please refer to https://www.ietf.org/iesg/statement/discuss-criteria.html
for more information about IESG DISCUSS and COMMENT positions.

The document, along with other ballot positions, can be found here:


Thank you for the work put into this document. I find the idea of having an
'invariant' document interesting.

Please find below some non-blocking COMMENT points (but replies would be

I hope that this helps to improve the document,




Should the use of UDP transport be also an invariant ?

-- Abstract --
I have hard time to reconciliate "...that are expected to remain unchanged..."
with the intended status of standards track... and later with the sentence "A
protocol that does not conform to the properties described in this document is
not QUIC" in section 5.4.

-- Section 1 --
Are we really sure that QUIC will always between TWO endpoints ? I.e., no
multicast at all ?

-- Section 3 --
I second Barry's point, the presence of "This document uses terms and
notational conventions from [QUIC-TRANSPORT]." renders QUIC-TRANSPORT as a
normative reference

-- Section 4 --
Isn't this section somehow redundant as the last paragraph of section 3 states
"This document uses ... notational conventions from [QUIC-TRANSPORT]".