Thanks Jeff for the text suggestions.
-gabriel
--- Jeff Mandin <[EMAIL PROTECTED]> wrote:
> Daniel,
>
> It's good to see this work moving forward. However, the problem
> statement and characterization of the 802.16 MAC that appears in the
> charter is not correct:
>
> * 802.16 is in fact capable of native multicasting in the downlink
> (see for example 802.16e section 11.9.35)
>
> * 802.16 has a built-in "802.3 Convergence Sublayer" which enables
> the point-to-multipoint network to emulate a large LAN (with the
> option of broadcast filtering). This faciliitates IPv6 operation
> (including ND), but has the (possible) cost of some extra bytes of
> overhead.
>
> Below is an amended third paragraph:
>
> " IEEE 802.16(e) is different from existing wireless access
> technologies such as IEEE 802.11 or 3G. Accordingly, while 802.16
> defines the encapsulation of an IP datagram in an IEEE 802.16 MAC
> payload, complete description of IP operation is not present and can
> benefit from IETF input and specification.
>
> For example: immediately subsequent to network entry an 802.16
> subscriber station has no capability whatsoever for data (as opposed
> to management) connectivity. The criteria by which the Base Station
> (or other headend elements) set up the 802.16 MAC connections for data
> transport is not part of the 802.16 standard and depends on the type
> of data services being offered (ie. the set up of transport
> connections will be different for IPv4 and IPv6 services).
> Additionally - as 802.16 is a point-to-multipoint network - an 802.16
> subscriber station is not capable of broadcasting (eg. for neighbor
> discovery) or direct communication to the other nodes in the network.
> While the built-in LAN emulation feature of 802.16 ("802.3 Convergence
> Sublayer") rectifies this, it may involve additional packet overhead.
> As for fast mobility, the characteristics of IEEE 802.16e link-layer
> operation may require an amendment to the Fast Handover Mobile IPv6
> scheme (RFC 4068), something which may be pursued in the MIPSHOP WG."
>
> Regards,
>
> - Jeff Mandin
_______________________________________________
Int-area mailing list
[email protected]
https://www1.ietf.org/mailman/listinfo/int-area
