[pim] Éric Vyncke's Yes on draft-ietf-pim-3228bis-06: (with COMMENT)

Éric Vyncke via Datatracker <noreply@ietf.org> Mon, 29 July 2024 11:47 UTC

Return-Path: <noreply@ietf.org>
X-Original-To: pim@ietf.org
Delivered-To: pim@ietfa.amsl.com
Received: from [10.244.2.81] (unknown [104.131.183.230]) by ietfa.amsl.com (Postfix) with ESMTP id 53A7FC151075; Mon, 29 Jul 2024 04:47:18 -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>
X-Test-IDTracker: no
X-IETF-IDTracker: 12.19.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <172225363798.1666554.3541353952475217553@dt-datatracker-659f84ff76-9wqgv>
Date: Mon, 29 Jul 2024 04:47:17 -0700
Message-ID-Hash: FBQL36EPYAXAMDMGOJXMKKTHMNN4AITB
X-Message-ID-Hash: FBQL36EPYAXAMDMGOJXMKKTHMNN4AITB
X-MailFrom: noreply@ietf.org
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-pim.ietf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
CC: draft-ietf-pim-3228bis@ietf.org, pim-chairs@ietf.org, pim@ietf.org, dthaler1968@gmail.com
X-Mailman-Version: 3.3.9rc4
Reply-To: Éric Vyncke <evyncke@cisco.com>
Subject: [pim] Éric Vyncke's Yes on draft-ietf-pim-3228bis-06: (with COMMENT)
List-Id: Protocol Independent Multicast <pim.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/pim/aa2o99Q4FtnTFSh9abmyAw2PKKU>
List-Archive: <https://mailarchive.ietf.org/arch/browse/pim>
List-Help: <mailto:pim-request@ietf.org?subject=help>
List-Owner: <mailto:pim-owner@ietf.org>
List-Post: <mailto:pim@ietf.org>
List-Subscribe: <mailto:pim-join@ietf.org>
List-Unsubscribe: <mailto:pim-leave@ietf.org>

Éric Vyncke has entered the following ballot position for
draft-ietf-pim-3228bis-06: Yes

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-pim-3228bis/



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


# Éric Vyncke, INT AD, comments for draft-ietf-avtcore-rtp-scip-05

Thank you for the work put into this document.

Please find below some non-blocking COMMENT points (but replies would be
appreciated even if only for my own education).

Special thanks to Stig Venaas for the shepherd's detailed write-up including
the WG consensus _and_ the justification of the intended status.

Other thanks to Dave Thaler, the Internet directorate reviewer (at my request),
please consider this int-dir review:
https://datatracker.ietf.org/doc/review-ietf-pim-3228bis-06-intdir-telechat-thaler-2024-07-25/

I hope that this review helps to improve the document,

Regards,

-éric

# COMMENTS (non-blocking)

## Section 2.2

A specific version is written for IGMPv3 but not for MLD. Suggest adding also a
specific version for MLD.

## Section 2.1.2

Suggest adding a specific section to the reference to RFC 4443.

## Section 6.2

Should the two -bis IETF drafts be normative ? If only to ensure that thaey are
part of a RFC editor's cluster ?