Folks,
First, I agree that it would be a mistake to remove the Router Alert from MLDv2. The V6OPS draft isn't even requesting that.
However, if we are working on an MLDv3, this may present a very good opportunity to remove the dependency on Router Alert.
I wasn't aware that MLDv3 was in the works? Is there a draft that I can read?
Ron
Juniper Business Use Only From: Eric Vyncke (evyncke) <evyncke@xxxxxxxxx>
Sent: Wednesday, July 24, 2024 12:19 AM To: David Lamparter <equinox@xxxxxxxxxx>; Mohamed Boucadair <mohamed.boucadair@xxxxxxxxxx>; Erik Kline <ek.ietf@xxxxxxxxx> Cc: rtg-dir@xxxxxxxx <rtg-dir@xxxxxxxx>; draft-ietf-pim-3810bis.all@xxxxxxxx <draft-ietf-pim-3810bis.all@xxxxxxxx>; last-call@xxxxxxxx <last-call@xxxxxxxx>; pim@xxxxxxxx <pim@xxxxxxxx>; draft-ietf-6man-deprecate-router-alert@xxxxxxxx <draft-ietf-6man-deprecate-router-alert@xxxxxxxx> Subject: Re: [Last-Call] Re: [pim] Rtgdir last call review of draft-ietf-pim-3810bis-10
[External Email. Be cautious of content]
W/o any hat and thank you, David, to bring the elephant in the room topic (no sarcasm here, just a sincere thank you to open the discussion).
Removing the router alert from MLDv2 would be such a drastic change (not even required by the 6MAN draft) that IMHO it cannot be named MLDv2-bis and should be another MLD version (and I know that MLDv3 is in the cooking).
Let’s not overreact here ;-)
Regards
-éric
|
-- last-call mailing list -- last-call@xxxxxxxx To unsubscribe send an email to last-call-leave@xxxxxxxx