RFC 4925: Softwire Problem Statement
In plain English — editorial summary, not part of the RFC
This document captures the problem statement for the Softwires Working Group, which is developing standards for the discovery, control, and encapsulation methods for connecting IPv4 networks across IPv6-only networks as well as IPv6 networks across IPv4-only networks. The standards will encourage multiple, inter-operable vendor implementations by identifying, and extending where necessary, existing standard protocols to resolve a selected set of "IPv4/IPv6" and "IPv6/IPv4" transition problems. This document describes the specific problems ("Hubs and Spokes" and "Mesh") that will be solved by the standards developed by the Softwires Working Group. Some requirements (and non-requirements) are also identified to better describe the specific problem scope. This memo provides information for the Internet community.
Document record
- Document ID
- RFC4925
- Published
- July 2007
- Authors
- X. Li; S. Dawkins; D. Ward; A. Durand
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- int
- Pages
- 23
- Also known as
- —
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 4919IPv6 over Low-Power Wireless Personal Area Networks (6LoWPANs): Overview, Assumptions, Problem Statement, and GoalsCurrent
August 2007
- RFC 4917Mobile IPv4 Message String ExtensionCurrent
June 2007
- RFC 4941Privacy Extensions for Stateless Address Autoconfiguration in IPv6Obsoleted
September 2007
- RFC 4944Transmission of IPv6 Packets over IEEE 802.15.4 NetworksUpdated
September 2007
- RFC 4955DNS Security (DNSSEC) ExperimentsCurrent
July 2007
- RFC 4956DNS Security (DNSSEC) Opt-InCurrent
July 2007
- RFC 4957Link-Layer Event Notifications for Detecting Network AttachmentsCurrent
August 2007
- RFC 4889Network Mobility Route Optimization Solution Space AnalysisCurrent
July 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?