Download presentation
Presentation is loading. Please wait.
Published byFlora Young Modified over 6 years ago
1
IP over 802.16 Problem Statement draft-jee-16ng-ps-goals-00.txt
Junghoon Jee, ETRI Syam Madanapalli Jeff Mandin Gabriel Montenegro Soohong Daniel Park Maximilian Riegel Samsung Runcom Microsoft Siemens March 22nd, 2006 16ng BoF, IETF65
2
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 March 22nd, 2006 16ng BoF, IETF65
3
IP Subnet Model over 802.16 IP Subnet Link
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. March 22nd, 2006 16ng BoF, IETF65
4
IP Subnet Model over 802.16 (2) IP Subnet model for 802.16’s PMP links
3G like Subnet Model SSs do not share the same global address prefix. Only the IP Gateway is neighbor. Ethernet like Subnet Model SSs share the same global address prefix. All SSs under an IP Gateway are neighbors. March 22nd, 2006 16ng BoF, IETF65
5
Next Hop Determination & Address Resolution
IP CS No need of address resolution, “IP to MAC”. ARP might need to be blocked (driver impl.). However, NDP is performed at IP level. Blocking=> Different IPv6 stacks for Redundantly Perform=> Unnecessary signaling March 22nd, 2006 16ng BoF, IETF65
6
Next Hop Determination & Address Resolution (2)
Ethernet CS 3G like Subnet Model Next-hop needs to be always IP Gateway. No way to force the SS’s next hop because it is internal IP stack’s decision based on the destination prefix. Ethernet like Subnet Model Can expect not requiring the change of “IP over Ethernet”. Requires multicast emulation over connection-oriented MAC. March 22nd, 2006 16ng BoF, IETF65
7
Stateless Autoconfiguration and DAD
48-bit MAC address can be used. 3G like Subnet model DAD is trivial only between SS and IP Gateway. Ethernet like Subnet model DAD for LLA might not guarantee the IID’s uniqueness. March 22nd, 2006 16ng BoF, IETF65
8
Gap Analysis 3GPP recommendation: RFC 3314 IP over Ethernet: RFC 894
Uses PPP to assign unique IID. No CS for classification of PPP frames. Direct transfer of PPP frames is not possible. IP over Ethernet: RFC 894 Ethernet CS does not provide Ethernet functionality over the air. Requires multicast emulation over connection-oriented MAC. Need to specify “IP over ”! March 22nd, 2006 16ng BoF, IETF65
Similar presentations
© 2024 SlidePlayer.com. Inc.
All rights reserved.