Hmm... the multicast to unicast conversion described in there looks fairly weak. It doesn't discuss any problems with IGMPv2/MLDv1 wrt to report suppression and how to deal with that for example. Or the challenge that hosts may not be happy about receiving IP multicast packets with unicast MAC destination address. If an organization has the ability to specify behavior f HNID's (as in 5.2), then it would be a lot better to specify those refinemenet (eg: translate back to L2-multicast in downstream HNID's, L2 unicast IGMp queries to inhibit report suppression o proxy into IGMPv3/MLDv2, etc. pp.)
What interaction does IETF have with that initiative ? Does it make sense / is it possible to engage with these folks ? Anybody hee workin over there ? Seems they are planning to be gone anyhow, so just likley the will create from existing docs some half-baked solution ? http://www.homegatewayinitiative.org/news/PressReleases/PR11_HGI_Conclusion_FINAL.pdf Cheers Toerless On Fri, Aug 07, 2015 at 09:16:27AM +0000, Hartog, F.T.H. (Frank) den wrote: > HGI is requesting Home Gateways to perform Wi-Fi multicast-to-unicast > conversion, see http://www.homegatewayinitiative.org/publis/P_HGI01628R19.pdf > . > > Regards, > > Frank > ________________________________________ > From: homenet [homenet-boun...@ietf.org] on behalf of Juliusz Chroboczek > [j...@pps.univ-paris-diderot.fr] > Sent: Friday, August 07, 2015 10:21 AM > To: Mikael Abrahamsson > Cc: Homenet > Subject: Re: [homenet] 802.11 is just fine for IPv6 [was: Despair] > > > I don't see how you can claim that ISIS can't use multicast on wifi > > because multicast on wifi doesn't work, > > I have never claimed that. Babel uses multicast on wifi. (Once again, > Mikael, I request that you stop misrepresenting my position.) > > I think that the multicast reduction technique used by David in IS-IS and > by Markus in HNCP are a smart idea, and I intend to implement something > similar in a private branch of Babel in order to test how much of an > improvement it gives (the protocol explicitly allows that, so it's merely > an implementation change). I won't merge it into the mainline until I get > a sufficient set of experimental data, which could take some time. > > If you can publish your experimental data before then, that would be helpful. > > -- Juliusz > > _______________________________________________ > homenet mailing list > homenet@ietf.org > https://www.ietf.org/mailman/listinfo/homenet > This message may contain information that is not intended for you. If you are > not the addressee or if this message was sent to you by mistake, you are > requested to inform the sender and delete the message. TNO accepts no > liability for the content of this e-mail, for the manner in which you use it > and for damage of any kind resulting from the risks inherent to the > electronic transmission of messages. > > _______________________________________________ > homenet mailing list > homenet@ietf.org > https://www.ietf.org/mailman/listinfo/homenet -- --- Toerless Eckert, eck...@cisco.com _______________________________________________ homenet mailing list homenet@ietf.org https://www.ietf.org/mailman/listinfo/homenet
