RFC 5121: Transmission of IPv6 via the IPv6 Convergence Sublayer over IEEE 802.16 Networks
In plain English — editorial summary, not part of the RFC
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. [STANDARDS-TRACK]
Document record
- Document ID
- RFC5121
- Published
- February 2008
- Authors
- B. Patil; F. Xia; B. Sarikaya; JH. Choi; S. Madanapalli
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- int
- Pages
- 22
- Also known as
- —
- Updated by:
- RFC 8064
Topics
Referenced by
One later RFC formally updates or obsoletes part of this document.
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 4429Optimistic Duplicate Address Detection (DAD) for IPv6Updated
April 2006
- RFC 6059Simple Procedures for Detecting Network Attachment in IPv6Current
November 2010
- RFC 4140Hierarchical Mobile IPv6 Mobility Management (HMIPv6)Obsoleted
August 2005
- RFC 7048Neighbor Unreachability Detection Is Too ImpatientCurrent
January 2014
- RFC 7219SEcure Neighbor Discovery (SEND) Source Address Validation Improvement (SAVI)Current
May 2014
- RFC 3684Topology Dissemination Based on Reverse-Path Forwarding (TBRPF)Updated
February 2004
- RFC 6779Definition of Managed Objects for the Neighborhood Discovery ProtocolObsoleted
October 2012
- RFC 6820Address Resolution Problems in Large Data Center NetworksCurrent
January 2013
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?