[MBONED] Benjamin Kaduk's Discuss on draft-ietf-mboned-ieee802-mcast-problems-14: (with DISCUSS and COMMENT)

Benjamin Kaduk via Datatracker <noreply@ietf.org> Mon, 19 July 2021 01:45 UTC

Return-Path: <noreply@ietf.org>
X-Original-To: mboned@ietf.org
Delivered-To: mboned@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id A99413A1B28; Sun, 18 Jul 2021 18:45:33 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Benjamin Kaduk via Datatracker <noreply@ietf.org>
To: "The IESG" <iesg@ietf.org>
Cc: draft-ietf-mboned-ieee802-mcast-problems@ietf.org, mboned-chairs@ietf.org, mboned@ietf.org, Jake Holland <jholland@akamai.com>, jholland@akamai.com
X-Test-IDTracker: no
X-IETF-IDTracker: 7.34.0
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: Benjamin Kaduk <kaduk@mit.edu>
Message-ID: <162665913337.13273.5208372625089115371@ietfa.amsl.com>
Date: Sun, 18 Jul 2021 18:45:33 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/mboned/5TLOZytNFL1Qlw4GY9t83h3602A>
Subject: [MBONED] Benjamin Kaduk's Discuss on draft-ietf-mboned-ieee802-mcast-problems-14: (with DISCUSS and COMMENT)
X-BeenThere: mboned@ietf.org
X-Mailman-Version: 2.1.29
List-Id: Mail List for the Mboned Working Group <mboned.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mboned>, <mailto:mboned-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mboned/>
List-Post: <mailto:mboned@ietf.org>
List-Help: <mailto:mboned-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mboned>, <mailto:mboned-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 19 Jul 2021 01:45:34 -0000

Benjamin Kaduk has entered the following ballot position for
draft-ietf-mboned-ieee802-mcast-problems-14: Discuss

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/iesg/statement/discuss-criteria.html
for more information about DISCUSS and COMMENT positions.


The document, along with other ballot positions, can be found here:
https://datatracker.ietf.org/doc/draft-ietf-mboned-ieee802-mcast-problems/



----------------------------------------------------------------------
DISCUSS:
----------------------------------------------------------------------

Many thanks for all the updates from -11 to -14; the preponderance are
good and improve the document.

I especially appreciate the change in section 9 to claim only that the
use of IPsec is specified, rather than mandated, by the referenced
document.  Unfortunately, the reference document was changed as well,
from RFC 4601 to RFC 7761, but RFC 7761 calls out as one of the changes
from RFC 4601 that "authentication using IPsec" was removed.  So the
current claim in the -14, that "[RFC7761] [...] specifies the use of
IPsec to ensure authentication of the link-local messages in [PIM-SM]"
is not correct, though for a different reason than what I noted in my
ballot position on the -11.  It may be most expedient to just restore
the reference to the obsolete document, though of course there are other
possibilities.


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

Section 3.2.1

   o  ARP [RFC5424]

RFC 5424 is "The Syslog Protocol"; while RFC 5494 is only hamming
distance one away and relates to ARP, it seems that the original RFC 826
might actually be a better reference.

Section 8

I'm still a little confused by the first point -- it seems to be
suggesting that some types of multicast traffic might only be sent if
sending over a wired interface and just dropped for wireless interfaces,
which both introduces a layering violation and causes wireless to be a
"second-class citizen".  Presumably there is some more subtlety than
that, but I'm missing it.