70 likes | 238 Views
IPv4 over 802.16 IP CS draft-ietf-16ng-ipv4-over-802-dot-16-ipcs-01. Basavaraj Patil, Nokia On behalf of Authors: Syam Madanapalli, Ordyn Technologies Soohong D. Park, Samsung Samita Chakrabarti, Azaire Networks. 70th IETF - Vancouver, Canada December 2-7, 2007. History.
E N D
IPv4 over 802.16 IP CSdraft-ietf-16ng-ipv4-over-802-dot-16-ipcs-01 Basavaraj Patil, Nokia On behalf of Authors: Syam Madanapalli, Ordyn Technologies Soohong D. Park, Samsung Samita Chakrabarti, Azaire Networks 70th IETF - Vancouver, Canada December 2-7, 2007
History • WG item, presented in the last two IETF meetings • 01 version is available now • Major issue from the last WG meeting is MTU size
Objective of presentation • To update on resolved issues on • MTU • Other minor comments on the mailing list
Point-to-point link between MS and AR No PPP is used A set of IEEE 802.16 MAC connections (CIDs) represent the p2p link Subnet Model MS1 Point-to-point IP link BS1 MS2 To Internet AR MS3 BS2 MS4
Maximum value: 2038 octets Total PDU size (2048) - MAC Header (6) - CRC (4) Minimum value: 576 octets As per RFC 1122 Default: 1440 octets This avoids the fragmentation of packets between BS and AR when using Ethernet as the transport using GRE tunnel (Wimax model) Avoids fragmentation as much as possible between Wimax and other technology networks that use IPSec Tunnels as the link. MTU MS1 GRE Tunnel BS1 MS2 AR To Internet MS3 BS2 MS4
Suggestions from the Mailing List • ARP behavior • Resolution: IPCS works over point-to-point link. But if some legacy IP implementation requires ARP resolution to be performed, it should simulate ARP response internally. (Appendix B) • Adding text for NAT requirement on AR • Resolution: There is no special NAT requirements for IP over IEEE 802.16. But a generic text is added for addressing private IPv4 addresses for the sake of completeness (Appendix D)