RFC 6333 - Dual-Stack Lite Broadband Deployments Following IPv4 Exhaustion

Document Information

• RFC Number: 6333
• Title: Dual-Stack Lite Broadband Deployments Following IPv4 Exhaustion
• Authors: A. Durand, R. Droms, J. Woodyatt, Y. Lee
• Date: August 2011
• Category: Standards Track
• ISSN: 2070-1721

Abstract

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).

Status of This Memo

This is an Internet Standards Track document.

This document is a product of the Internet Engineering Task Force (IETF). It represents the consensus of the IETF community. It has received public review and has been approved for publication by the Internet Engineering Steering Group (IESG). Further information on Internet Standards is available in Section 2 of RFC 5741.

Information about the current status of this document, any errata, and how to provide feedback on it may be obtained at http://www.rfc-editor.org/info/rfc6333.

Copyright Notice

Copyright (c) 2011 IETF Trust and the persons identified as the document authors. All rights reserved.

This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (http://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Simplified BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Simplified BSD License.

Contents

• 1. Introduction
• 2. Requirements Language
• 3. Terminology
• 4. Deployment Scenarios
  • 4.1. Access Model
  • 4.2. CPE
  • 4.3. Directly Connected Device
• 5. B4 Element
  • 5.1. Definition
  • 5.2. Encapsulation
  • 5.3. Fragmentation and Reassembly
  • 5.4. AFTR Discovery
  • 5.5. DNS
  • 5.6. Interface Initialization
  • 5.7. Well-Known IPv4 Address
• 6. AFTR Element
  • 6.1. Definition
  • 6.2. Encapsulation
  • 6.3. Fragmentation and Reassembly
  • 6.4. DNS
  • 6.5. Well-Known IPv4 Address
  • 6.6. Extended Binding Table
• 7. Network Considerations
  • 7.1. Tunneling
  • 7.2. Multicast Considerations
• 8. NAT Considerations
  • 8.1. NAT Pool
  • 8.2. NAT Conformance
  • 8.3. Application Level Gateways (ALGs)
  • 8.4. Sharing Global IPv4 Addresses
  • 8.5. Port Forwarding / Keep Alive
• 9. Acknowledgements
• 10. IANA Considerations
• 11. Security Considerations
• 12. References
  • 12.1. Normative References
  • 12.2. Informative References
• Appendix A. Deployment Considerations
  • A.1. AFTR Service Distribution and Horizontal Scaling
  • A.2. Horizontal Scaling
  • A.3. High Availability
  • A.4. Logging
• Appendix B. Examples
  • B.1. Gateway-Based Architecture
  • B.1.1. Example Message Flow
  • B.1.2. Translation Details
  • B.2. Host-Based Architecture
  • B.2.1. Example Message Flow
  • B.2.2. Translation Details
• Authors' Addresses