[Gen-art] Genart last call review of draft-ietf-detnet-data-plane-framework-04

Christer Holmberg via Datatracker <noreply@ietf.org> Sun, 15 March 2020 10:28 UTC

Return-Path: <noreply@ietf.org>
X-Original-To: gen-art@ietf.org
Delivered-To: gen-art@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id BB4633A1399; Sun, 15 Mar 2020 03:28:35 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: Christer Holmberg via Datatracker <noreply@ietf.org>
To: gen-art@ietf.org
Cc: last-call@ietf.org, draft-ietf-detnet-data-plane-framework.all@ietf.org, detnet@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 6.121.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <158426811560.18081.13105223593760493382@ietfa.amsl.com>
Reply-To: Christer Holmberg <christer.holmberg@ericsson.com>
Date: Sun, 15 Mar 2020 03:28:35 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/gen-art/PxMlDVkUIg3KNQRSaKzyboSf6TI>
Subject: [Gen-art] Genart last call review of draft-ietf-detnet-data-plane-framework-04
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.29
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 15 Mar 2020 10:28:39 -0000

Reviewer: Christer Holmberg
Review result: Ready with Nits

I am the assigned Gen-ART reviewer for this draft. The General Area
Review Team (Gen-ART) reviews all IETF documents being processed
by the IESG for the IETF Chair.  Please treat these comments just
like any other last call comments.

For more information, please see the FAQ at

<https://trac.ietf.org/trac/gen/wiki/GenArtfaq>.

Document: draft-ietf-detnet-data-plane-framework-04
Reviewer: Christer Holmberg
Review Date: 2020-03-15
IETF LC End Date: 2020-03-13
IESG Telechat date: Not scheduled for a telechat

Summary: The document is well written, and almost ready for publication. I have
no issues on the technical parts, but I have found some editorial nits in the
Introduction- and Security Considerations sections that I ask the authors to
address.

Major issues: N/A

Minor issues: N/A

Nits/editorial comments:

Q1:

The first line of the Introduction says:

“DetNet (Deterministic Networking) provides a capability…”

Please add a reference to DetNet/RFC8655 on first occurance.

Q2:

The first line of the 2nd paragraph of the Introduction says:

“This document describes the concepts needed by any DetNet data plane
specification…”

What is meant by DetNet data plane specification? The definition of DetNet
flows over a specific network technology? Please clarify, or reference if
already defined elsewhere.

Q3:

The 5th paragraph of the Introduction (“DetNet flows may be carried over
network…”) contains text about network topologies that can be used for DetNet
flows.

Is the text (all, or part of it) in the paragraph somehow specific to this
document, or is it simply repeating things that are defined in RFC 8655? If the
paragraph is only repeating stuff, maybe start with “As defined in RFC8655,
DetNet flows may be carried…”.

Q4:

The 6th paragraph of the Introduction says:

“Different application flows (e.g., Ethernet, IP, etc.)…”

The text may it look like the Ethernet, IP etc is the actual application flow.
I assume you mean application flow carried over Ethernet, IP, etc? If so,
please modify to make it more clear.

Q5:

The Security considerations say:

“Security considerations for DetNet are described in detail in
[I-D.ietf-detnet-security].  General security considerations are
described in [RFC8655].”

The sentence is confusing. General security considerations for what? Doesn’t
RFC 8655 also describe security considerations for DetNet?