1. July 10th, 200616ng WG, IETF661 Junghoon Jee, ETRI IP over 802.16 Problem Statement Update draft-jee-16ng-ps-goals Maximilian Riegel Syam Madanapalli Gabriel Montenegro Soohong Daniel Park Jeff Mandin Siemens Samsung Microsoft Samsung Runcom

2. July 10th, 200616ng WG, IETF662 Terminology SS (Subscriber Station) –An end-user equipment that provides connectivity to IEEE 802.16 based network. BS (Base Station) –A layer 2 entity providing connectivity, management, and control of the subscriber station. IP Gateway –A layer 3 entity that acts as a first-hop default router for SSs. IP Subnet –Topological area that uses the same address prefix where that prefix is not further subdivided except into individual addresses. Link –Topological area bounded by routers which decrement the IPv4 TTL or IPv6 Hop Limit when forwarding the packet. Transport Connection –IEEE 802.16 ’ s MAC connection between a SS and BS with a specific QoS attributes. Each transport connection is identified by an unique identifier called connection identifier.

3. July 10th, 200616ng WG, IETF663 IEEE 802.16 PMP Link Layer No native bi-directional multicast support No direct communication between MS/SSs Connection-oriented MAC –Connections always between MS/SS and BS MAC PDUs are transferred according to CID –48-bit MAC addresses are not used for transmission Ethernet CS does not provide Ethernet functionality over the air –Specifies only encapsulation and classification of Ethernet Frames for transmission over CIDs

4. July 10th, 200616ng WG, IETF664 16ng Problem Statement 1.Distinctive feature of 802.16 link No native bi-directional multicast support No direct communication between SSs Connections always between SS and BS 48-bit MAC addresses are not used for transmission 2.Ethernet CS does not provide the Ethernet-like functionality. 3.Air resource consumption from the previous multicast/broadcast based IPv6 NDP and IPv4 ARP 4.Power consumption caused by waking up of dormant terminals 5.No single mandatory CS on the SS. 6.Multilink subnet issues when using IP CS for Ethernet-like deployment model.

5. July 10th, 200616ng WG, IETF665 16ng Goals 1.Work on Ethernet CS should provide interoperability with existing devices that employ Ethernet. 2.Define an enhanced IPv6 NDP under considering scarce air resources. 3.Define enhanced IPv4 ARP under considering scarce air resources. 4.Reduce the power consumption caused by waking up of dormant terminals 5.Resolve the multilink subnet issues when using IP CS for Ethernet-like deployment model. 6.Consider the applicability of the previous security works like SEND. 7.Do not introduce any new security threats.

6. July 10th, 200616ng WG, IETF666 16ng Goals (2) 8.Define the way to negotiate the used convergence sublayers. 9.Define the feasible IP subnet models depending on the CS used.

7. July 10th, 200616ng WG, IETF667 16ng Network Models Baseline is how to constitute an IP subnet over IEEE 802.16 PMP links. Ethernet-like deployment model –IP subnet consists of one IP Gateway and multiple SSs. –Both IP CS and Ethernet CS are applicable. IP CS: Need to resolve the multilink subnet issues. Ethernet CS: Based on the bridging function at BS. 3G-like deployment model –IP Gateway assigns separate IP subnet prefixes for each SS. –IP CS seems more applicable. BS architectural issue –Physical relationship between BS and IP Gateway. –Resolution: Informational texts on deployment model I-D.