[tsvwg] Éric Vyncke's No Objection on draft-ietf-tsvwg-ecn-l4s-id-28: (with COMMENT)
Éric Vyncke via Datatracker <noreply@ietf.org> Thu, 25 August 2022 13:09 UTC
Return-Path: <noreply@ietf.org>
X-Original-To: tsvwg@ietf.org
Delivered-To: tsvwg@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 3C7D2C152583; Thu, 25 Aug 2022 06:09:38 -0700 (PDT)
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-tsvwg-ecn-l4s-id@ietf.org, tsvwg-chairs@ietf.org, tsvwg@ietf.org, Wesley Eddy <wes@mti-systems.com>, wes@mti-systems.com
X-Test-IDTracker: no
X-IETF-IDTracker: 8.14.0
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: Éric Vyncke <evyncke@cisco.com>
Message-ID: <166143297824.39739.13115862733987449317@ietfa.amsl.com>
Date: Thu, 25 Aug 2022 06:09:38 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/tsvwg/FeILdLGrteuyi2zx7Xer1np-CWY>
Subject: [tsvwg] Éric Vyncke's No Objection on draft-ietf-tsvwg-ecn-l4s-id-28: (with COMMENT)
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.39
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tsvwg/>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 25 Aug 2022 13:09:38 -0000
Éric Vyncke has entered the following ballot position for draft-ietf-tsvwg-ecn-l4s-id-28: 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-tsvwg-ecn-l4s-id/ ---------------------------------------------------------------------- COMMENT: ---------------------------------------------------------------------- # Éric Vyncke, INT AD, comments for draft-ietf-shmoo-hackathon-07 CC @evyncke Thank you for the work put into this document. Like well-written by Paul Wouters in another review, I am not a TSV person... I also appreciate the experimental status with a description of the experiment itself. Please find below some non-blocking COMMENT points (but replies would be appreciated even if only for my own education). Special thanks to Wesley Eddy for the shepherd's detailed write-up including the WG consensus **and** the justification of the intended status. I hope that this review helps to improve the document, Regards, -éric ## COMMENTS ### Update RFC 3168 No need to comment, but it was very smart for the authors of RFC 8511 to allow such experiments ;-) There is some duplicate text in sections 1.3 and 2 on this though... ### Section 1 A lot of the content of this section appears to be identical or similar to the architecture draft. Consider removing some text ? ### BCP 14 Please use the right template for BCP14 in section 1.2. ### Section 5.4.1.1 unresponsive Is `unresponsive traffic` a well-defined term ? ### Section 5.4.1.1 ARP, DNS In the example for low-level traffic, ARP, DNS, I am unsure whether ARP is really routed through an IP network ;-) or are Ethernet switches also covered by this I-D? You may also qualify 'DNS' into 'DNS queries'. ### Section 6.2 ``` ... If a mix of L4S and Classic packets is sent into the same security association (SA) of a virtual private network (VPN), and if the VPN egress is employing the optional anti-replay feature, ... ``` Suggest to used IPsec in tunnel mode as they are many kinds of VPNs. ## Notes This review is in the ["IETF Comments" Markdown format][ICMF], You can use the [`ietf-comments` tool][ICT] to automatically convert this review into individual GitHub issues. [ICMF]: https://github.com/mnot/ietf-comments/blob/main/format.md [ICT]: https://github.com/mnot/ietf-comments
- [tsvwg] Éric Vyncke's No Objection on draft-ietf-… Éric Vyncke via Datatracker
- Re: [tsvwg] Éric Vyncke's No Objection on draft-i… Bob Briscoe