Erik, > 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
The *Ethernet compatibility layer* of 802.16 (actually called the Convergence Sublayer) specifies only how Ethernet frames are to be encapsulated over 802.16 wireless connections. This implies that Ethernet CS does not emulate Ethernet like functionality and multicast/broadcast frames can not be processed at the 802.16 MAC layer. These frames are sent to Ethernet Layer, which in turn may send to 802.16 MAC, to send out these multicast/broadcast frames there should be a downlink multicast/broadcast connection to which all MSs listening to. And the basic thing is, even if Ethernet has broadcast support, the layer below does not have efficient mechanism to handle broadcast/multicast packets. To provide a functional emulation of Ethernet, several additional definitions and functional elements are necessary (dealt with 16ng solution) > - in addition, figure out ways that Neighbor Discovery can rely on less > multicast >From the IP CS perspective, the mention above is an applicable concern. I think the text below was trying to indicate that: "....because of the existence of multiple Convergence Sublayers which makes the specification of IP over IEEE 802.16 non-trivial." Let me describe your comments in each deliverable more detail... Daniel (Soohong Daniel Park) Mobile Convergence Laboratory, SAMSUNG Electronics. -------------------------------------------------------------------- IETF IPv6 working group mailing list ipv6@ietf.org Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6 --------------------------------------------------------------------
