> -----Original Message----- > From: [email protected] [mailto:[email protected]] On Behalf Of > Christian Huitema
> There are two solutions today: multicast all the way, from the source > to the various destinations; and, unicast all the way. The multicast > solution suffers from very poor performance on the 802.11 network. The > unicast solution prevents bandwidth optimization in the distribution > network. The "best" solution would combine unicast on 802.11 networks > and multicast on the distribution network. That requires protocol > changes, so that an 802.11 node that subscribes to a multicast group > effectively gets unicast delivery from the wireless router, while the > wireless router gets multicast delivery from the network router. That's > what Mark's draft is attempting to define. That seems like a fine > project. Agree. I thought the proposal was to retain the IP header as is, i.e. a Class D destination address, but to use the unique MAC address at layer 2 (RFC 6085). To find the individual MAC address, I thought the plan was to use the source IP in the IGMP join, and then find the MAC the old fashioned way. Seems like a useful workaround. I think it should be in IETF's scope. Bert -------------------------------------------------------------------- IETF IPv6 working group mailing list [email protected] Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6 --------------------------------------------------------------------
