|
|
#
#
#
|
|
| # |
|
|
| Standardization work |
|
# IETF WGs: RFCsDrafts
|
|
|
#
#
|
|
|
#
#
|
|
|
| IETF topics |
|
#
#
|
|
| # |
|
|
#
#
|
|
|
#
#
|
|
|
| 3GPP topics |
|
#
#
|
|
|
#
#
|
|
|
#
#
#
|
|
|
#
#
#
#
|
|
|
#
#
|
|
|
#
#
|
|
|
#
#
#
|
|
|
#
#
#
|
|
|
| ETSI topics |
|
#
|
|
|
| Other topics |
|
#
#
#
|
|
| # |
|
|
|
| # | public access |
| |
| # | private access (full or partial) |
| |
| # |
public access so far, but very likely private access with next version |
|
|
| |
| |
|
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
|
| | |
RFC4968
08/2007
(16 p.)
pdf(2p)
|
S. Madanapalli |
|
Analysis of IPv6 Link Models for IEEE 802.16 Based Networks |
|
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.
|
|
|
| |
| List |
Status: | Informational |
|
| |
| |
| |
|
| | |
RFC5121
02/2008
(22 p.)
pdf(2p)
|
B. Patil
F. Xia
B. Sarikaya
JH. Choi
S. Madanapalli |
|
Transmission of IPv6 via the IPv6 Convergence Sublayer over IEEE 802.16 Networks |
|
IEEE Std 802.16 is an air interface specification for fixed and
mobile Broadband Wireless Access Systems. Service-specific
convergence sublayers to which upper-layer protocols interface are a
part of the IEEE 802.16 MAC (Medium Access Control). The Packet
convergence sublayer (CS) is used for the transport of all packet-based
protocols such as Internet Protocol (IP) and IEEE 802.3 LAN/MAN
CSMA/CD Access Method (Ethernet). IPv6 packets can be sent and
received via the IP-specific part of the Packet CS. This document
specifies the addressing and operation of IPv6 over the IP-specific
part of the Packet CS for hosts served by a network that utilizes the
IEEE Std 802.16 air interface. It recommends the assignment of a
unique prefix (or prefixes) to each host and allows the host to use
multiple identifiers within that prefix, including support for
randomly generated interface identifiers.
|
|
|
| |
| List |
Status: | Proposed Standard |
|
| |
| |
| |
|
| | |
RFC5154
04/2008
(14 p.)
pdf(2p)
|
J. Jee
S. Madanapalli
J. Mandin |
|
IP over IEEE 802.16 Problem Statement and Goals |
|
This document specifies problems in running IP over IEEE 802.16
networks by identifying specific gaps in the IEEE 802.16 Media Access
Control (MAC) for IPv4 and IPv6 support. This document also provides
an overview of IEEE 802.16 network characteristics and convergence
sublayers. Common terminology used for the base guideline while
defining the solution framework is also presented.
|
|
|
| |
| List |
Status: | Informational |
|
| |
| |
| |
|
| | |
RFC5692
10/2009
(21 p.)
pdf(2p)
|
H. Jeon
S. Jeong
M. Riegel |
|
Transmission of IP over Ethernet over IEEE 802.16 Networks |
|
This document describes the transmission of IPv4 over Ethernet, as
well as IPv6 over Ethernet, in an access network deploying the IEEE
802.16 cellular radio transmission technology. The Ethernet on top
of IEEE 802.16 is realized by bridging connections that IEEE 802.16
provides between a base station and its associated subscriber
stations. Due to the resource constraints of radio transmission
systems and the limitations of the IEEE 802.16 Media Access Control
(MAC) functionality for the realization of an Ethernet, the
transmission of IP over Ethernet over IEEE 802.16 may considerably
benefit by adding IP-specific support functions in the Ethernet over
IEEE 802.16 while maintaining full compatibility with standard IP
over Ethernet behavior.
|
|
|
| |
| List |
Status: | Proposed Standard |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
|
| | |
16ng-ipv4-
over-802-dot-16-
ipcs-06
IESG Progress
Jun 14, 2009
(14 p.)
|
S. Madanapalli
S. D. Park
S. Chakrabarti
G. Montenegro |
|
Transmission of IPv4 packets over IEEE 802.16's IP Convergence Sublayer |
IEEE 802.16 is an air interface specification for wireless broadband
access. IEEE 802.16 has specified multiple service specific
Convergence Sublayers for transmitting upper layer protocols. The
packet CS (Packet Convergence Sublayer) is used for the transport of
all packet-based protocols such as Internet Protocol (IP) and IEEE
802.3 (Ethernet). The IP-specific part of the Packet CS enables the
transport of IPv4 packets directly over the IEEE 802.16 MAC.
This document specifies the frame format, the Maximum Transmission
Unit (MTU) and address assignment procedures for transmitting IPv4
packets over the IP-specific part of the Packet Convergence Sublayer
of IEEE 802.16.
|
|
|
| |
| List |
Intended Status: | Proposed Standard |
|
| |
| |
| |
| |
| |
| |
| |
| |
|
| The charter of the 16NG working group
is reported below.
|
| |
|
Broadband Wireless Access Networks address the inadequacies of low
bandwidth wireless communication for user requirements such as high
quality data/voice service, wide coverage, etc. The IEEE 802.16 Working
Group on Broadband Wireless Access Standards develops standards and
recommended practices to support the development and deployment of
Broadband Wireless Metropolitan Area Networks.
A particularity of IEEE 802.16 is that it does not include a rigid upper
edge MAC service interface. Instead, it provides multiple "convergence
sublayers (CS)" with the assumption that the choice and configuration of
the upper edge will be done in accordance with the needs of a specific
deployment environment (which might be DSL replacement, mobile access,
802.11 or CDMA backhaul etc.).
Specifically, immediately subsequent to network entry, an 802.16
subscriber station has no capability whatsoever for data (as opposed to
management) connectivity. Especially, in IP CS case, the criteria by
which the Base Station (or other headend elements) sets up the 802.16
MAC connections for data transport are not part of the 802.16 standard,
and depend on the type of data services being offered (e.g., the set up
of link layer connections will be different for IPv4 and IPv6 services).
Additionally - as IEEE 802.16 is a point-to-multipoint network - an
802.16 subscriber station is not capable of multicasting (e.g., for
neighbor discovery, ARP, IP multicasting services, etc.) or direct
communication to the other nodes attached to the same Base Station
within the same subnet (prefix).
Unlike 3G or xDSL technologies, IEEE 802.16 is not part of an end-to-
end system definition. Currently, the WiMAX Forum, and, in particular,
its NWG (Network Working Group) is defining a network architecture based
on IEEE 802.16.
The principal objective of the 16ng working group is to specify the
operation of IPv4 and IPv6 over IEEE 802.16, taking into account the
IPv4, IPv6 and Ethernet Convergence Sublayers. The working group may
issue recommendations to IEEE 802.16 and WiMax aiming at improving
support for IP.
The scope of this working group is as follows (WG Deliverables);
|
| - |
Produce "16ng Problem Statement, Goal and Requirement" to identify the
specific gaps in the 802.16 MAC for IPv4/IPv6 support, describe possible
network models (ie. point-to-point, broadcast etc.), and provide 16ng
related terminology to be used for the base guideline while defining
solution frameworks. [Informational RFC]
| |
| - |
Produce "IPv6 over IEEE 802.16 Networks in conjunction with IPv6 CS"
to define IPv6 operation including the transmission of IPv6 over IEEE
802.16 link, Neighbor Discovery Protocol, Stateful (DHCPv6) and
Stateless Address Configuration, Broadcast, Multicast, etc. [Proposed
Standard RFC]
| |
| - |
Produce "IPv6 over IEEE 802.16 Networks in conjunction with Ethernet
CS" to define IPv6 operation including the transmission of IPv6 over
IEEE 802.16 link, Neighbor Discovery Protocol, Stateful (DHCPv6) and
Stateless Address Configuration, Broadcast, Multicast, etc. [Proposed
Standard RFC]
| |
| - |
Produce "IPv4 over IEEE 802.16 Networks in conjunction with IPv4 CS"
to define IPv4 operation including the transmission of IPv4 over IEEE
802.16 links, ARP operation, Stateful Address Configuration (DHCPv4),
Broadcast, Multicast, etc [Proposed Standard RFC]
| |
| - |
Produce "IPv4 over IEEE 802.16 Networks in conjunction with Ethernet
CS" to define IPv4 operation including the transmission of IPv4 over
IEEE 802.16 links, ARP operation, Stateful Address Configuration
(DHCPv4), Broadcast, Multicast, etc [Proposed Standard RFC]
| |
| - |
Produce "IP deployment over IEEE 802.16 Networks" to illustrate the IP
deployment scenarios including IP CS and Ethernet CS considerations over
IEEE 802.16 networks based on the WiMAX and WiBro. [Informational RFC]
|
This working group will take dual stack operation into account in its
specifications, and reuse existing specifications whenever reasonable
and possible. The ability to negotiate the used Convergence Sublayer is
required, as no single mandatory CS can be specified for the clients.
Work based on the Ethernet CS needs to take into account
interoperability with existing hosts and other devices that employ
Ethernet, to allow bridging.
16ng will not initially consider other work items than the ones listed
above; however, other related work may occur in other WGs, and 16ng will
participate and help such efforts.
|
| |
| |
|
|
|
