[core] Éric Vyncke's No Objection on draft-ietf-core-new-block-11: (with COMMENT)

Éric Vyncke via Datatracker <noreply@ietf.org> Mon, 03 May 2021 12:16 UTC

Return-Path: <noreply@ietf.org>
X-Original-To: core@ietf.org
Delivered-To: core@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id A486A3A0CCD; Mon, 3 May 2021 05:16:50 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: =?utf-8?q?=C3=89ric_Vyncke_via_Datatracker?= <noreply@ietf.org>
To: "The IESG" <iesg@ietf.org>
Cc: draft-ietf-core-new-block@ietf.org, core-chairs@ietf.org, core@ietf.org, marco.tiloca@ri.se, marco.tiloca@ri.se, csp@csperkins.org
X-Test-IDTracker: no
X-IETF-IDTracker: 7.28.0
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: =?utf-8?q?=C3=89ric_Vyncke?= <evyncke@cisco.com>
Message-ID: <162004421064.19511.6477108778521848512@ietfa.amsl.com>
Date: Mon, 03 May 2021 05:16:50 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/core/WcCsONpVstOMNmkdWlQzRApXPBw>
Subject: [core] =?utf-8?q?=C3=89ric_Vyncke=27s_No_Objection_on_draft-ietf?= =?utf-8?q?-core-new-block-11=3A_=28with_COMMENT=29?=
X-BeenThere: core@ietf.org
X-Mailman-Version: 2.1.29
List-Id: "Constrained RESTful Environments \(CoRE\) Working Group list" <core.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/core>, <mailto:core-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/core/>
List-Post: <mailto:core@ietf.org>
List-Help: <mailto:core-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/core>, <mailto:core-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 03 May 2021 12:16:51 -0000

Éric Vyncke has entered the following ballot position for
draft-ietf-core-new-block-11: 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 DISCUSS and COMMENT positions.


The document, along with other ballot positions, can be found here:
https://datatracker.ietf.org/doc/draft-ietf-core-new-block/



----------------------------------------------------------------------
COMMENT:
----------------------------------------------------------------------

Thank you for the work put into this document.

Please find below some non-blocking COMMENT points (but replies would be
appreciated especially on the intended status/lack of public implementations).

I hope that this helps to improve the document,

Regards,

-éric

== COMMENTS ==

!!! I was about to ballot a DISCUSS on this point... In the absence of a
section about existing implementations for such a new transport, I really
wonder whether standard track should be used rather then experimental. Did the
authors/WG run some simulations ?

Happy to have read Colin Perkins' review for the Transport ART, which has
provided me with some confidence in this brand new transport protocol. I am
also trusting the TSV Area Directors on this point.

-- Section 1 --
I had in mind that constrained network are well protected either at layer-2 or
by having an air-gap or firewall at their edges, so, a DoS seems quite
improbable in those deployments. Should this 'use case' really be part of the
introduction? Or is it simply linked to the DOTS use case ? In either case, the
DoS should be more detailed.

-- Section 3 --
Any reason why 'CON' is not expanded/explained on first use ?