List Info

Thread: RFC 4925 on Softwire Problem Statement




RFC 4925 on Softwire Problem Statement
country flaguser name
United States
2007-07-27 15:30:21
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:    xingcernet.edu.cn, 
                    spencermcsr-labs.org, 
                    dwardcisco.com, alain_durandcable.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-REQUESTIETF.ORG.  Requests to be
added to or deleted from the RFC-DIST distribution list
should
be sent to RFC-DIST-REQUESTRFC-EDITOR.ORG.

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

help: ways_to_get_rfcs. For example:

        To: rfc-infoRFC-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-ManagerRFC-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-EDITORRFC-EDITOR.ORG.  Please consult RFC 2223,
Instructions to RFC
Authors, for further information.


The RFC Editor Team
USC/Information Sciences Institute

...


_______________________________________________
rfc-dist mailing list
rfc-distmailman.rfc-editor.org
http://mailman.rfc-editor.org/mailman/listinfo/rfc-dist
http://www.rfc-editor.org

[1]

about | contact  Other archives ( Real Estate discussion Medical topics )