RFC 5692: Transmission of IP over Ethernet over IEEE 802.16 Networks
In plain English — editorial summary, not part of the RFC
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]
Document record
- Document ID
- RFC5692
- Published
- October 2009
- Authors
- H. Jeon; S. Jeong; M. Riegel
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- int
- Pages
- 21
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 5154IP over IEEE 802.16 Problem Statement and GoalsCurrent
April 2008
- RFC 4968Analysis of IPv6 Link Models for 802.16 Based NetworksCurrent
August 2007
- RFC 6464A Real-time Transport Protocol (RTP) Header Extension for Client-to-Mixer Audio Level IndicationCurrent
December 2011
- RFC 6465A Real-time Transport Protocol (RTP) Header Extension for Mixer-to-Client Audio Level IndicationCurrent
December 2011
- RFC 4416Goals for Internet Messaging to Support Diverse Service EnvironmentsCurrent
February 2006
- RFC 3322Signaling Compression (SigComp) Requirements & AssumptionsCurrent
January 2003
- RFC 9071RTP-Mixer Formatting of Multiparty Real-Time TextCurrent
July 2021
- RFC 5702Use of SHA-2 Algorithms with RSA in DNSKEY and RRSIG Resource Records for DNSSECUpdated
October 2009
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?