[RTG-DIR]Re: [pim] Re: [Last-Call] Re: Rtgdir last call review of draft-ietf-pim-3810bis-10

David 'equinox' Lamparter <equinox@diac24.net> Wed, 24 July 2024 20:27 UTC

Return-Path: <equinox@diac24.net>
X-Original-To: rtg-dir@ietfa.amsl.com
Delivered-To: rtg-dir@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DDB21C14F726; Wed, 24 Jul 2024 13:27:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.91
X-Spam-Level:
X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id BfLTz8vGrPzt; Wed, 24 Jul 2024 13:27:45 -0700 (PDT)
Received: from eidolon.nox.tf (eidolon.nox.tf [IPv6:2a07:2ec0:2185::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 224E7C14F5F1; Wed, 24 Jul 2024 13:27:44 -0700 (PDT)
Received: from equinox by eidolon.nox.tf with local (Exim 4.97.1) (envelope-from <equinox@diac24.net>) id 1sWiaD-00000006kW7-1UtY; Wed, 24 Jul 2024 22:27:34 +0200
Date: Wed, 24 Jul 2024 22:27:33 +0200
From: David 'equinox' Lamparter <equinox@diac24.net>
To: Stig Venaas <stig@venaas.com>
Message-ID: <ZqFjtUJrFPdMQENm@eidolon.nox.tf>
References: <171645303257.23265.13071555183433458489@ietfa.amsl.com> <ZqA4pRrSIHbEChRn@eidolon.nox.tf> <PH0PR11MB4966C2F68694E9F69A7B5380A9AA2@PH0PR11MB4966.namprd11.prod.outlook.com> <ZqCEEDwf101jKN8t@faui48e.informatik.uni-erlangen.de> <CAHANBtJ8c1FUVv145_H7925VTHfS5d362-Ho1GUFnQ3+e8tKhA@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <CAHANBtJ8c1FUVv145_H7925VTHfS5d362-Ho1GUFnQ3+e8tKhA@mail.gmail.com>
Message-ID-Hash: 6XTJDR3XNXF2IKBPTUS753TY4XPDHYZA
X-Message-ID-Hash: 6XTJDR3XNXF2IKBPTUS753TY4XPDHYZA
X-MailFrom: equinox@diac24.net
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-rtg-dir.ietf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
CC: Toerless Eckert <tte@cs.fau.de>, "Eric Vyncke (evyncke)" <evyncke@cisco.com>, Mohamed Boucadair <mohamed.boucadair@orange.com>, Erik Kline <ek.ietf@gmail.com>, "rtg-dir@ietf.org" <rtg-dir@ietf.org>, "draft-ietf-pim-3810bis.all@ietf.org" <draft-ietf-pim-3810bis.all@ietf.org>, "last-call@ietf.org" <last-call@ietf.org>, "pim@ietf.org" <pim@ietf.org>, "draft-ietf-6man-deprecate-router-alert@ietf.org" <draft-ietf-6man-deprecate-router-alert@ietf.org>
X-Mailman-Version: 3.3.9rc4
Precedence: list
Subject: [RTG-DIR]Re: [pim] Re: [Last-Call] Re: Rtgdir last call review of draft-ietf-pim-3810bis-10
List-Id: Routing Area Directorate <rtg-dir.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/rtg-dir/qnFaFgLFBwOhP_HryQTw78Ay5B0>
List-Archive: <https://mailarchive.ietf.org/arch/browse/rtg-dir>
List-Help: <mailto:rtg-dir-request@ietf.org?subject=help>
List-Owner: <mailto:rtg-dir-owner@ietf.org>
List-Post: <mailto:rtg-dir@ietf.org>
List-Subscribe: <mailto:rtg-dir-join@ietf.org>
List-Unsubscribe: <mailto:rtg-dir-leave@ietf.org>

On Tue, Jul 23, 2024 at 10:35:25PM -0700, Stig Venaas wrote:
> The MLDv2 bis document is not defining a new protocol, we are just
> progressing MLDv2 to Internet Standard. We should and cannot make any
> changes that would render existing implementations non-compliant,

Even though I threw in the mail about this, I don't have a strong
preference to making any change here.  The room discussion in 6man on
the RA draft brought up the MLDv2 bis doc and it wasn't clear what's
going on -- and if there is something to be done, it'd be rather poor
timing.

> and also, we want to only have protocol definitions that have multiple
> implementations and known to work well. Removing RA would be a pretty
> big change.

I don't think removing RA is on the table.  If anything, I think it
would be weakening the requirements to check that RA is present, i.e.
allowing receive processing without RA.  It would need to remain a MUST
to include it on send though, as the sender has no idea if the receiver
(be it router or snooping switch) allows this.

> I'm not sure why MLDv2 is defined with RA, might it make a difference
> to snooping switches?

I don't believe it does, AFAIK the same mechanisms filter out e.g.
ICMPv6 RA guard, which doesn't have router alert on it.

Cheers,


equi
(David)


P.S.: our (relatively recent, 2yo) MLD implementation requires RA;  if
anything I'd like to know if I can and/or should remove that check.
https://github.com/FRRouting/frr/blame/bd86964db816ba1ac628f1b1f5099fd35f157ea5/pimd/pim6_mld.c#L1712