[rfc-dist] RFC 6333 on Dual-Stack Lite Broadband Deployments Following IPv4 Exhaustion

rfc-editor at rfc-editor.org rfc-editor at rfc-editor.org
Mon Aug 8 12:12:32 PDT 2011

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

        RFC 6333

        Title:      Dual-Stack Lite Broadband Deployments Following 
                    IPv4 Exhaustion 
        Author:     A. Durand, R. Droms,
                    J. Woodyatt, Y. Lee
        Status:     Standards Track
        Stream:     IETF
        Date:       August 2011
        Mailbox:    adurand at juniper.net, 
                    rdroms at cisco.com, 
                    jhw at apple.com,  yiu_lee at cable.comcast.com
        Pages:      32
        Characters: 65622
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-softwire-dual-stack-lite-11.txt

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

This document revisits the dual-stack model and introduces the Dual-
Stack Lite technology aimed at better aligning the costs and benefits
of deploying IPv6 in service provider networks.  Dual-Stack Lite
enables a broadband service provider to share IPv4 addresses among
customers by combining two well-known technologies: IP in IP (IPv4-
in-IPv6) and Network Address Translation (NAT).  [STANDARDS-TRACK]

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

This is now a Proposed Standard Protocol.

STANDARDS TRACK: This document specifies an Internet standards track
protocol for the Internet community,and requests discussion and suggestions
for improvements.  Please refer to the current edition of the Internet
Official Protocol Standards (STD 1) for the standardization state and
status of this protocol.  Distribution of this memo is unlimited.

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see

For searching the RFC series, see http://www.rfc-editor.org/rfcsearch.html.
For downloading RFCs, see http://www.rfc-editor.org/rfc.html.

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

The RFC Editor Team
Association Management Solutions, LLC

More information about the rfc-dist mailing list