> -----Original Message----- > From: Erik Nordmark [mailto:[EMAIL PROTECTED] > > IEEE 802.16 also has different support for broadcast and > multicast than > Ethernet (don't you love it when IEEE 802 designs standards > that don't > conform to the IEEE 802.1 LAN service model ;-) > > Folks have talked about two ways of addressing this (so that ARP, > Neighbor Discovery and applications use of IP multicast can > be supported) > - a multicast emulation sublayer > - in addition, figure out ways that Neighbor Discovery can > rely on less > multicast > > Unfortunately, the proposed charter doesn't make it clear what the > approach will be for multicast.
Rather than reinvent the wheel, I wonder if much of the work done in the old ION working group wouldn't also apply here. There were ARP servers and multicast servers, for example. All the same set of problems recur, when the link layer is non-broadcast. RFCs 2022 (multicast support), 2225 (classical IP over ATM), 2332 (next-hop resolution), 2684 (encapsulation for basic non-dynamic ATM links). Plus ca change, plus c'est la meme chose. Bert -------------------------------------------------------------------- IETF IPv6 working group mailing list [email protected] Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6 --------------------------------------------------------------------
