Softwire Problem Statement

Metadata

Publisher: IETF
Doc Type: Informational
Pages: 23
Abstract: 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.
Publication Date: 2007-07-01
Status Note: Informational
DOI: 10.17487/RFC4925
Link: https://doi.org/10.17487/RFC4925
Author(s): Xing Li
Spencer Dawkins
David Ward
Alain Durand

Latest version of IETF RFC 4925

Document Versions — IETF RFC 4925

▶ IETF RFC 4925 (2007-07-01)

THIS DOC [ACTIVE] [LATEST VERSION]

Normative Reference(s)

IETF RFC 3041 [Superseded*]
IETF RFC 3053 [Active*]
IETF RFC 3056 [Active*]
IETF RFC 3972 [Active*]
IETF RFC 4213 [Active*]

Bibliographic Reference(s)

Johnson, R., "Subnet Allocation Option" , Work in Progress, June 2007. EXTERNAL
Durand, A., "Service Discovery using NAPTR records in DNS", Work in Progress, October 2004. EXTERNAL
Palet, J., "Goals for Tunneling Configuration" , Work in Progress, February 2005. EXTERNAL
Bellovin, S., "Guidelines for Mandating the Use of IPsec", Work in Progress, February 2007. EXTERNAL
Palet, J. and M, "Analysis of IPv6 Tunnel End-point Discovery Mechanisms", Work in Progress, January 2005. EXTERNAL
IETF RFC 2131 [Active*]
IETF RFC 2462 [Superseded*]
IETF RFC 3315 [Superseded*]
IETF RFC 3633 [Superseded*]
IETF RFC 4364 [Active*]
IETF RFC 4365 [Active*]
IETF RFC 4891 [Active*]

Source Data (JSON)

Full registry record with provenance metadata. Open directly: /api/doc/RFC4925.json

Reference Tree

Explore all references and references to this document, as a navigable tree.

Open Reference Tree

Reference this Doc

Plain text (ISO 690 compliant)

Preview:

IETF RFC 4925, Softwire Problem Statement. Available at https://doi.org/10.17487/RFC4925

Snippet:

IETF RFC 4925, Softwire Problem Statement. Available at https://doi.org/10.17487/RFC4925

HTML (ISO 690 compliant)

Preview:

IETF RFC 4925, Softwire Problem Statement. Available at https://doi.org/10.17487/RFC4925

Snippet:

<span class="citation"><cite>IETF RFC 4925</cite>, Softwire Problem Statement. Available at <a href="https://doi.org/10.17487/RFC4925" target="_blank" rel="noopener">https://doi.org/10.17487/RFC4925</a></span>

SMPTE's HTML Pub

Preview:

IETF RFC 4925, Softwire Problem Statement
doi: 10.17487/RFC4925
url: https://doi.org/10.17487/RFC4925

Snippet:

<li>
<cite id="bib-rfc4925">IETF RFC 4925</cite>, Softwire Problem Statement
<span class="doi">10.17487/RFC4925</span>
</li>

Referenced By

IETF RFC 5549 [Superseded*]
IETF RFC 5565 [Active*]
IETF RFC 5571 [Active*]
IETF RFC 5619 [Active*]
IETF RFC 6127 [Active*]