Analysis of IPv6 Link Models for 802.16 Based Networks
RFC 4968

 
Document Type RFC - Informational (August 2007; Errata)
Last updated 2013-03-02
Stream IETF
Formats plain text pdf html
Stream WG state (None)
Consensus Unknown
Document shepherd No shepherd assigned
IESG IESG state RFC 4968 (Informational)
Telechat date
Responsible AD Jari Arkko
Send notices to 16ng-chairs@ietf.org,smadanapalli@gmail.com

Email authors IPR References Referenced by Nits Search lists

Network Working Group                                S. Madanapalli, Ed.
Request for Comments: 4968                            Ordyn Technologies
Category: Informational                                      August 2007

      Analysis of IPv6 Link Models for IEEE 802.16 Based Networks

Status of This Memo

   This memo provides information for the Internet community.  It does
   not specify an Internet standard of any kind.  Distribution of this
   memo is unlimited.

Copyright Notice

   Copyright (C) The IETF Trust (2007).

Abstract

   This document provides different IPv6 link models that are suitable
   for IEEE 802.16 based networks and provides analysis of various
   considerations for each link model and the applicability of each link
   model under different deployment scenarios.  This document is the
   result of a design team (DT) that was formed to analyze the IPv6 link
   models for IEEE 802.16 based networks.

Madanapalli                  Informational                      [Page 1]
RFC 4968            IPv6 Link Models for IEEE 802.16         August 2007

Table of Contents

   1.  Introduction . . . . . . . . . . . . . . . . . . . . . . . . .  2
   2.  Terminology  . . . . . . . . . . . . . . . . . . . . . . . . .  3
   3.  IPv6 Link Models for IEEE 802.16 Based Networks  . . . . . . .  3
     3.1.  Shared IPv6 Prefix Link Model  . . . . . . . . . . . . . .  3
       3.1.1.  Prefix Assignment  . . . . . . . . . . . . . . . . . .  5
       3.1.2.  Address Autoconfiguration  . . . . . . . . . . . . . .  5
       3.1.3.  Duplicate Address Detection  . . . . . . . . . . . . .  5
       3.1.4.  Considerations . . . . . . . . . . . . . . . . . . . .  6
       3.1.5.  Applicability  . . . . . . . . . . . . . . . . . . . .  7
     3.2.  Point-to-Point Link Model  . . . . . . . . . . . . . . . .  7
       3.2.1.  Prefix Assignment  . . . . . . . . . . . . . . . . . .  8
       3.2.2.  Address Autoconfiguration  . . . . . . . . . . . . . .  8
       3.2.3.  Considerations . . . . . . . . . . . . . . . . . . . .  8
       3.2.4.  Applicability  . . . . . . . . . . . . . . . . . . . .  9
     3.3.  Ethernet-Like Link Model . . . . . . . . . . . . . . . . . 10
       3.3.1.  Prefix Assignment  . . . . . . . . . . . . . . . . . . 10
       3.3.2.  Address Autoconfiguration  . . . . . . . . . . . . . . 10
       3.3.3.  Duplicate Address Detection  . . . . . . . . . . . . . 10
       3.3.4.  Considerations . . . . . . . . . . . . . . . . . . . . 11
       3.3.5.  Applicability  . . . . . . . . . . . . . . . . . . . . 11
   4.  Renumbering  . . . . . . . . . . . . . . . . . . . . . . . . . 11
   5.  Effect on Dormant Mode . . . . . . . . . . . . . . . . . . . . 12
   6.  Effect on Routing  . . . . . . . . . . . . . . . . . . . . . . 12
   7.  Conclusions and Relevant Link Models . . . . . . . . . . . . . 13
   8.  Security Considerations  . . . . . . . . . . . . . . . . . . . 13
   9.  Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 13
   10. Contributors . . . . . . . . . . . . . . . . . . . . . . . . . 14
   11. References . . . . . . . . . . . . . . . . . . . . . . . . . . 14
     11.1. Normative References . . . . . . . . . . . . . . . . . . . 14
     11.2. Informative References . . . . . . . . . . . . . . . . . . 14

1.  Introduction

   IEEE 802.16 [4] [5] is a point-to-multipoint, connection-oriented
   access technology for the last mile without bi-directional native
   multicast support.  IEEE 802.16 has defined only downlink multicast
   support.  This leads to two methods for running IP protocols that
   traditionally assume the availability of multicast at the link layer.
   One method is to use bridging, e.g., IEEE 802.1D [6], to support bi-
   directional multicast.  Another method is to treat the IEEE 802.16
   MAC (Message Authentication Code) transport connections between an MS
   (Mobile Station) and BS (Base Station) as point-to-point IP links so
   that the IP protocols (e.g., ARP (Address Resolution Protocol), IPv6
   Neighbor Discovery) can be run without any problems.

Madanapalli                  Informational                      [Page 2]
RFC 4968            IPv6 Link Models for IEEE 802.16         August 2007

   This is further complicated by the definition of commercial network
   models like WiMAX, which defines the WiMAX transport connection that
   extends the IEEE 802.16 MAC transport connection all the way to an
   access router by using a tunnel between the base station and the
   access router [14].  This leads to multiple ways of deploying IP over
   IEEE 802.16 based networks.

   This document looks at various considerations in selecting a link
   model for IEEE 802.16 based networks and provides an analysis of the
   various possible link models.  And finally, this document provides a
Show full document text