[rfc-dist] RFC 4925 on Softwire Problem Statement

rfc-editor@rfc-editor.org rfc-editor at rfc-editor.org
Fri Jul 27 13:30:21 PDT 2007

A new Request for Comments is now available in online RFC libraries.

        RFC 4925

        Title:      Softwire Problem Statement 
        Author:     X. Li, Ed.,
                    S. Dawkins, Ed.,
                    D. Ward, Ed.,
                    A. Durand, Ed.
        Status:     Informational
        Date:       July 2007
        Mailbox:    xing at cernet.edu.cn, 
                    spencer at mcsr-labs.org, 
                    dward at cisco.com, alain_durand at cable.comcast.com
        Pages:      23
        Characters: 49298
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-softwire-problem-statement-03.txt

        URL:        http://www.rfc-editor.org/rfc/rfc4925.txt

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.

This document is a product of the Softwires
Working Group of the IETF.

INFORMATIONAL: This memo provides information for the Internet community. 
It does not specify an Internet standard of any kind. Distribution
of this memo is unlimited.

This announcement is sent to the IETF list and the RFC-DIST list.
Requests to be added to or deleted from the IETF distribution list
should be sent to IETF-REQUEST at IETF.ORG.  Requests to be
added to or deleted from the RFC-DIST distribution list should

Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to rfc-info at RFC-EDITOR.ORG with the message body 

help: ways_to_get_rfcs. For example:

        To: rfc-info at RFC-EDITOR.ORG
        Subject: getting rfcs

        help: ways_to_get_rfcs

Requests for special distribution should be addressed to either the
author of the RFC in question, or to RFC-Manager at RFC-EDITOR.ORG.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.

Submissions for Requests for Comments should be sent to
RFC-EDITOR at RFC-EDITOR.ORG.  Please consult RFC 2223, Instructions to RFC
Authors, for further information.

The RFC Editor Team
USC/Information Sciences Institute


More information about the rfc-dist mailing list