1 / 11

IPv6 Neighbor Discovery over 802.16

IPv6 Neighbor Discovery over 802.16. Syam Madanapalli Samsung ISO. IETF 64 – Vancouver, Canada November 8 th 2005. IPv6 ND over 802.16 – Issues. Multicast Support 802.16 is a connection oriented technology for the last mile Point-to-multipoint , No bidirectional native multicast support

thomasblee
Download Presentation

IPv6 Neighbor Discovery over 802.16

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. IPv6 Neighbor Discovery over 802.16 Syam Madanapalli Samsung ISO IETF 64 – Vancouver, Canada November 8th 2005

  2. IPv6 ND over 802.16 – Issues • Multicast Support • 802.16 is a connection oriented technology for the last mile • Point-to-multipoint , No bidirectional native multicast support • Subnet Model • Unclear • May depend on Convergence Sub Layers (Ethernet CS, IP CS) • Connection ID for IP Signaling • CID for IP Signaling during the Network Entry • Multiple connections may exist between MS and BS • Which connection to use?

  3. Ethernet CS IP Packet Terminates at AR There can be multiple ARs, so multiple Default Routers Requires Router Discovery and Unreachability detection Convergence Sub-layer - Link Link ? Link MS BS AR • IP CS • It is unknown whether the IP packet is terminated at BS or AR • BS routes the packet to AR ? • Tunnels the packet to AR? MS BS AR

  4. 802.16 Supports multicast for the down link May need to define a default DL Multicast Connection (mCID) for RAs All MSs may need to join the mCID Router Advertisements MS1 MS2 BS AR MS3 mCIDn RA DL UL

  5. Who are the neighbors to an MS? Other MSs attached to the same BS? Depends on subnet model MS is always has to have an L2 connection to BS MS may not need the NC and NUD, if BS is the IP neighbor Type of Convergence Sublayer used may affect these NC, Next-Hop and NUD AR1 MS1 MS2 BS AR2 MS3 AR3 Depending on how BS and ARs are connected may complicate these further.

  6. Prefix Discovery • Unique prefix to each MS • Sharing same prefix with multiple MSs • MS tries to resolve the L2 address for the on-link prefixes • Direct Communication between two MSs may not be possible • May be the routers should advertise prefixes with L bit reset

  7. Address Autoconfiguration - Issues • Whether other MSs are my neighbors (Subnet Model) • Whether the prefix is being shared with other MSs • MS cannot multicast the DAD NS

  8. Existing Solutions • Applicability of RFC 2491 – IPv6 Over NBMA • Frame Relay and ATM are end-2-end protocols • 802.16 defines only the last mile • Can we still apply RFC 2491? • 3GPP like model • Assign unique prefix to each MS

  9. A Possible New Solution • A Down-link multicast connection • E.g. for Router Advertisements • All MSs may join this well-known multicast connection • Router advertise the prefixes with L-bit reset • No neighbors except the ARs • Routers proxy for the end nodes (MSs) for Address Autoconfiguration • Setup a default connection between MS and BS that can be used for IP Signaling • Requires only the implementation change for Routers • No Protocol changes are required • MS IPv6 Stack can support multiple interfaces e.g. 802.11, 802.16

  10. Way Forward • Understand WiMAX NWG needs • Understand the implications of 802.16 Convergence Sub-layers • Understand the 802.16 Network Models • Develop Subnet Model • Develop Requirements • Make an I-D for recommendations to WiMAX NWG

More Related