RFC 5181: IPv6 Deployment Scenarios in 802.16 Networks
In plain English — editorial summary, not part of the RFC
This document provides a detailed description of IPv6 deployment and integration methods and scenarios in wireless broadband access networks in coexistence with deployed IPv4 services. In this document, we will discuss the main components of IPv6 IEEE 802.16 access networks and their differences from IPv4 IEEE 802.16 networks and how IPv6 is deployed and integrated in each of the IEEE 802.16 technologies. This memo provides information for the Internet community.
Document record
- Document ID
- RFC5181
- Published
- May 2008
- Authors
- M-K. Shin; Y-H. Han; S-E. Kim; D. Premec
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- ops
- Pages
- 16
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 5180IPv6 Benchmarking Methodology for Network Interconnect DevicesCurrent
May 2008
- RFC 5157IPv6 Implications for Network ScanningObsoleted
March 2008
- RFC 5156Special-Use IPv6 AddressesObsoleted
April 2008
- RFC 5153IP Flow Information Export (IPFIX) Implementation GuidelinesCurrent
April 2008
- RFC 5220Problem Statement for Default Address Selection in Multi-Prefix Environments: Operational Issues of RFC 3484 Default RulesCurrent
July 2008
- RFC 5221Requirements for Address Selection MechanismsCurrent
July 2008
- RFC 5136Defining Network CapacityCurrent
February 2008
- RFC 5132IP Multicast MIBCurrent
December 2007
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?