[Detnet] Éric Vyncke's No Objection on draft-ietf-detnet-mpls-over-ip-preof-10: (with COMMENT)
Éric Vyncke via Datatracker <noreply@ietf.org> Wed, 21 February 2024 08:09 UTC
Return-Path: <noreply@ietf.org>
X-Original-To: detnet@ietf.org
Delivered-To: detnet@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 6C4EDC14F709; Wed, 21 Feb 2024 00:09:06 -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-detnet-mpls-over-ip-preof@ietf.org, detnet-chairs@ietf.org, detnet@ietf.org, lberger@labn.net, lberger@labn.net, jinmei@wide.ad.jp
X-Test-IDTracker: no
X-IETF-IDTracker: 12.5.0
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: Éric Vyncke <evyncke@cisco.com>
Message-ID: <170850294642.35478.17473522283889648116@ietfa.amsl.com>
Date: Wed, 21 Feb 2024 00:09:06 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/detnet/wzOe8e0SA3nfNI-UsWFL_crt5h8>
Subject: [Detnet] Éric Vyncke's No Objection on draft-ietf-detnet-mpls-over-ip-preof-10: (with COMMENT)
X-BeenThere: detnet@ietf.org
X-Mailman-Version: 2.1.39
List-Id: Discussions on Deterministic Networking BoF and Proposed WG <detnet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/detnet>, <mailto:detnet-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/detnet/>
List-Post: <mailto:detnet@ietf.org>
List-Help: <mailto:detnet-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/detnet>, <mailto:detnet-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 21 Feb 2024 08:09:06 -0000
Éric Vyncke has entered the following ballot position for draft-ietf-detnet-mpls-over-ip-preof-10: 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/about/groups/iesg/statements/handling-ballot-positions/ for more information about how to handle DISCUSS and COMMENT positions. The document, along with other ballot positions, can be found here: https://datatracker.ietf.org/doc/draft-ietf-detnet-mpls-over-ip-preof/ ---------------------------------------------------------------------- COMMENT: ---------------------------------------------------------------------- # Éric Vyncke, INT AD, comments for draft-ietf-detnet-mpls-over-ip-preof-10 Thank you for the work put into this document. I always find DetNet work interesting and useful. Please find below some non-blocking COMMENT points (but replies would be appreciated even if only for my own education), and some nits. Special thanks to Lou Berger for the shepherd's detailed write-up including the WG consensus and the justification of the intended status (the latter could have been more detailed tough). Other thanks to Tatuya Jinmei, the Internet directorate reviewer (at my request), please consider this int-dir review: https://datatracker.ietf.org/doc/review-ietf-detnet-mpls-over-ip-preof-09-intdir-telechat-jinmei-2024-02-15/ (thanks to Balázs for his reply) I hope that this review helps to improve the document, Regards, -éric # COMMENTS (non-blocking) ## Is MPLS over UDP the only solution ? While using MPLS over UDP is indeed a valid solution for sequencing the packets, I wonder whether RFC 8939 could have been updated/extended to also add ordering, this would probably have less overhead. Was this discussed in the WG? If so, why not adding this justification in the draft ? (note I may have missed something obvious :-O ) ## Section 5 `IPv6 next header field set to "UDP"` seems to ignore the optional extension headers between the IPv6 header and the UDP header. The wording in `IPv6 next header field set to "UDP"` seems to indicate an action "to set" rather than "being equal to" (as suggested by the leading `The information needed to identify individual`). Suggest to clarify. I am most probably missing something obvious here but does this section assumes that the only DetNet flows are UDP ? # NITS (non-blocking / cosmetic) ## Section 1 Unsure whether 'correctly' is sensible in `correctly represented as PREOF`. Unsure whether the reference to a YANG model is useful in the same 1st paragraph.
- [Detnet] Éric Vyncke's No Objection on draft-ietf… Éric Vyncke via Datatracker
- Re: [Detnet] Éric Vyncke's No Objection on draft-… Andrew G. Malis
- Re: [Detnet] Éric Vyncke's No Objection on draft-… Balázs Varga A