RFC 4925 on Softwire Problem Statement

rfc-editor@rfc-editor.org Fri, 27 July 2007 20:32 UTC

Return-path: <ietf-announce-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1IEWUJ-0000Ro-KJ; Fri, 27 Jul 2007 16:32:39 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1IEWUH-0000RX-0F; Fri, 27 Jul 2007 16:32:37 -0400
Received: from bosco.isi.edu ([128.9.168.207]) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IEWUG-0006DC-CJ; Fri, 27 Jul 2007 16:32:36 -0400
Received: by bosco.isi.edu (Postfix, from userid 70) id 61DDDDAC12; Fri, 27 Jul 2007 13:30:21 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
From: rfc-editor@rfc-editor.org
Message-Id: <20070727203021.61DDDDAC12@bosco.isi.edu>
Date: Fri, 27 Jul 2007 13:30:21 -0700
X-Spam-Score: -15.0 (---------------)
X-Scan-Signature: 3971661e40967acfc35f708dd5f33760
Cc: softwires@ietf.org, rfc-editor@rfc-editor.org
Subject: RFC 4925 on Softwire Problem Statement
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: ietf-announce.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf-announce@ietf.org>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=subscribe>
Errors-To: ietf-announce-bounces@ietf.org

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@cernet.edu.cn, 

                    spencer@mcsr-labs.org, 

                    dward@cisco.com, alain_durand@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@IETF.ORG.  Requests to be

added to or deleted from the RFC-DIST distribution list should

be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG.



Details on obtaining RFCs via FTP or EMAIL may be obtained by sending

an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body 



help: ways_to_get_rfcs. For example:



        To: rfc-info@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@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@RFC-EDITOR.ORG.  Please consult RFC 2223, Instructions to RFC

Authors, for further information.





The RFC Editor Team

USC/Information Sciences Institute



...





_______________________________________________
IETF-Announce mailing list
IETF-Announce@ietf.org
https://www1.ietf.org/mailman/listinfo/ietf-announce