[rfc-dist] RFC 5692 on Transmission of IP over Ethernet over IEEE 802.16 Networks
rfc-editor at rfc-editor.org
Wed Oct 28 12:19:29 PDT 2009
A new Request for Comments is now available in online RFC libraries.
Title: Transmission of IP over Ethernet
over IEEE 802.16 Networks
Author: H. Jeon, S. Jeong,
Status: Standards Track
Date: October 2009
Mailbox: hongseok.jeon at gmail.com,
sjjeong at etri.re.kr,
maximilian.riegel at nsn.com
I-D Tag: draft-ietf-16ng-ip-over-ethernet-over-802-dot-16-12.txt
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. [STANDARDS TRACK]
This document is a product of the IP over IEEE 802.16 Networks Working Group of the IETF.
This is now a Proposed Standard Protocol.
STANDARDS TRACK: This document specifies an Internet standards track
protocol for the Internet community,and requests discussion and suggestions
for improvements. Please refer to the current edition of the Internet
Official Protocol Standards (STD 1) for the standardization state and
status of this protocol. Distribution of this memo is unlimited.
This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
For searching the RFC series, see http://www.rfc-editor.org/rfcsearch.html.
For downloading RFCs, see http://www.rfc-editor.org/rfc.html.
Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor at rfc-editor.org. Unless
specifically noted otherwise on the RFC itself, all RFCs are for
The RFC Editor Team
USC/Information Sciences Institute
More information about the rfc-dist