[pim] Éric Vyncke's No Objection on draft-ietf-pim-3376bis-11: (with COMMENT)

Éric Vyncke via Datatracker <noreply@ietf.org> Tue, 06 August 2024 07:55 UTC

Return-Path: <noreply@ietf.org>
X-Original-To: pim@ietf.org
Delivered-To: pim@ietfa.amsl.com
Received: from [10.244.2.66] (unknown [104.131.183.230]) by ietfa.amsl.com (Postfix) with ESMTP id 7097CC14F5ED; Tue, 6 Aug 2024 00:55:22 -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.21.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <172293092208.766860.1223435067003047330@dt-datatracker-6dd76c4557-2mkrj>
Date: Tue, 06 Aug 2024 00:55:22 -0700
Message-ID-Hash: KMXQWMMWW36TQ2OHDOUYGBIGR7AKWQC4
X-Message-ID-Hash: KMXQWMMWW36TQ2OHDOUYGBIGR7AKWQC4
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-3376bis@ietf.org, pim-chairs@ietf.org, pim@ietf.org, rthalley@gmail.com
X-Mailman-Version: 3.3.9rc4
Reply-To: Éric Vyncke <evyncke@cisco.com>
Subject: [pim] Éric Vyncke's No Objection on draft-ietf-pim-3376bis-11: (with COMMENT)
List-Id: Protocol Independent Multicast <pim.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/pim/z7FlclSQI9xB7UNsojx9KTiwA3E>
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-3376bis-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/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-3376bis/



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


# Éric Vyncke, INT AD, comments for draft-ietf-pim-3376bis-11

Thank you for the work put into this document. I have mainly reviewed the diff
with RFC 3376:
https://author-tools.ietf.org/iddiff?url1=rfc3376&url2=draft-ietf-pim-3376bis-11&difftype=--html

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

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

Other thanks to Bob Halley, the Internet directorate reviewer (at my request),
please consider this int-dir review:
https://datatracker.ietf.org/doc/review-ietf-pim-3376bis-11-intdir-telechat-halley-2024-07-28/
(just one nit that I have repeated in my ballot)

I hope that this review helps to improve the document,

Regards,

-éric

# COMMENTS (non-blocking)

## Internet Standard ?

Should this document aims at "Internet standard" per RFC 6410 ?

## Sections 4.1.4 and 4.2.3

Should the IANA registry name be used rather than the reference to the RFC
creating that registry ?

Should there be the usual text "unassigned bits in the Flags field MUST be set
to 0 on transmission and MUST be ignored on reception" ?

## Section 4.2.13

Perhaps a little pedantic, but what is a "valid IP address" ? Suggest using
"valid unicast IP address" (and perhaps "non link-local" ?).

# NITS (non-blocking / cosmetic)

## Section 6.4.2

>From Bob Halley's review `6.4.2 paragraph 8 duplicates a word in the text
"Section Section 6.6.3".`