RFC 5948: Transmission of IPv4 Packets over the IP Convergence Sublayer of IEEE 802.16
In plain English — editorial summary, not part of the RFC
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 the 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 Media Access Control (MAC) layer. This document specifies the frame format, the Maximum Transmission Unit (MTU), and the address assignment procedures for transmitting IPv4 packets over the IP-specific part of the Packet Convergence Sublayer of IEEE 802.16. [STANDARDS-TRACK]
Document record
- Document ID
- RFC5948
- Published
- August 2010
- Authors
- S. Madanapalli; S. Park; S. Chakrabarti; G. Montenegro
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- int
- Pages
- 13
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 5949Fast Handovers for Proxy Mobile IPv6Current
September 2010
- RFC 5944IP Mobility Support for IPv4, RevisedCurrent
November 2010
- RFC 5952A Recommendation for IPv6 Address Text RepresentationCurrent
August 2010
- RFC 5942IPv6 Subnet Model: The Relationship between Links and Subnet PrefixesCurrent
July 2010
- RFC 5936DNS Zone Transfer Protocol (AXFR)Updated
June 2010
- RFC 5933Use of GOST Signature Algorithms in DNSKEY and RRSIG Resource Records for DNSSECUpdated
July 2010
- RFC 5966DNS Transport over TCP - Implementation RequirementsObsoleted
August 2010
- RFC 5969IPv6 Rapid Deployment on IPv4 Infrastructures (6rd) -- Protocol SpecificationCurrent
August 2010
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?