[pim] Opsdir last call review of draft-ietf-pim-3376bis-10

Jouni Korhonen via Datatracker <noreply@ietf.org> Tue, 04 June 2024 21:20 UTC

Return-Path: <noreply@ietf.org>
X-Original-To: pim@ietf.org
Delivered-To: pim@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id A9CEBC14F5F4; Tue, 4 Jun 2024 14:20:17 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Jouni Korhonen via Datatracker <noreply@ietf.org>
To: ops-dir@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 12.14.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <171753601767.34898.14128463665449913150@ietfa.amsl.com>
Date: Tue, 04 Jun 2024 14:20:17 -0700
Message-ID-Hash: NSFEXQQ74M2V3AWKZDAOZAEXVRMDQQZU
X-Message-ID-Hash: NSFEXQQ74M2V3AWKZDAOZAEXVRMDQQZU
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.all@ietf.org, last-call@ietf.org, pim@ietf.org
X-Mailman-Version: 3.3.9rc4
Reply-To: Jouni Korhonen <jounikor@gmail.com>
Subject: [pim] Opsdir last call review of draft-ietf-pim-3376bis-10
List-Id: Protocol Independent Multicast <pim.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/pim/zEoH-oy5SzXQr3UmQcDlZY9kL7o>
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>

Reviewer: Jouni Korhonen
Review result: Has Nits

I am an assigned OPS-DIR directorate reviewer for draft-ietf-pim-3376bis-10.

Summary: Ready with nits

Overall I found the document ready for publication.

Editorial nits:
1) There are ~8 occasions where "section Section x.y.z" is used. Remove the extra section word.
  - line 530  s/Section Section 4.1.9/Section 4.1.9
  - line 555  s/section Section 8.1/Section 8.1
  - line 739  s/section Section 4.2.13/Section 4.2.13
  - line 979  s/Section Section 3.2/Section 3.2
  - line 1241 s/section Section 7/Section 7
  - line 1359 s/Section Section 6.4/Section 6.4
  - line 1583 s/Section Section 6.6.3/Section 6.6.3
  - line 1674 s/section Section 7/Section 7

Questions:
1) For example in Section 4.2.13 it states:
  "An SSM-aware host SHOULD NOT send a MODE_IS_EXCLUDE record type
   for multicast addresses that fall within the SSM address range."

  Since this is not "MUST NOT send" what is the occasion when the host
  chooses not to "SHOULD NOT" and sends a MODE_IS_EXCLUDE record type
  for multicast addresses that fall within the SSM address range?

  The case justifying going against "SHOULD NOT" is not described anywhere
  or I just did not find/understand it.

2) Similarly to 1) in Section 6.4 what is the case when the router 
  would not "SHOULD ignore"? The case is not described anywhere or
  I did not find/understand it.

If there is no cases to describe for 1) and 2) the I would use MUST NOT
and MUST accordingly..