Softwires Network Address Translation (SNAT)
draft-droms-softwires-snat-01
Document | Type |
Replaced Internet-Draft
(individual)
Expired & archived
|
|
---|---|---|---|
Authors | Ralph Droms , Brian Haberman | ||
Last updated | 2008-10-22 (Latest revision 2008-07-14) | ||
Replaced by | draft-durand-softwire-dual-stack-lite | ||
RFC stream | (None) | ||
Intended RFC status | (None) | ||
Formats | |||
Stream | Stream state | (No stream defined) | |
Consensus boilerplate | Unknown | ||
RFC Editor Note | (None) | ||
IESG | IESG state | Replaced by draft-durand-softwire-dual-stack-lite | |
Telechat date | (None) | ||
Responsible AD | (None) | ||
Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
Abstract
Service providers (ISPs) are interested in reducing the use of IPv4 in their internal networks because of the anticipated exhaustion of the IPv4 address space. Softwires Network Address Translation (SNAT) combines IPv4 NAT and IPv4-in-IPv6 softwires to carry IPv4 traffic through the ISP network that uses only IPv6 service. Multiple subscribers are multiplexed through a single external global IPv4 address, reducing the total number of IPv4 addresses in use by the ISP to support Internet traffic to those subscribers.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)