SIIT-DC: Stateless IP/ICMP Translation for IPv6 Data Center Environments
RFC 7755
Revision differences
Document history
| Date | By | Action |
|---|---|---|
|
2026-02-02
|
(System) | Received changes through RFC Editor sync (changed standardization level to Proposed Standard) |
|
2026-01-22
|
Morgan Condie | New status of Proposed Standard approved by the IESG https://datatracker.ietf.org/doc/status-change-siit-dc-to-proposed-standard/ |
|
2018-12-20
|
(System) | Received changes through RFC Editor sync (changed abstract to 'This document describes the use of the Stateless IP/ICMP Translation Algorithm (SIIT) in an IPv6 Internet … Received changes through RFC Editor sync (changed abstract to 'This document describes the use of the Stateless IP/ICMP Translation Algorithm (SIIT) in an IPv6 Internet Data Center (IDC). In this deployment model, traffic from legacy IPv4-only clients on the Internet is translated to IPv6 upon reaching the IDC operator's network infrastructure. From that point on, it may be treated the same as traffic from native IPv6 end users. The IPv6 endpoints may be numbered using arbitrary (non-IPv4-translatable) IPv6 addresses. This facilitates a single-stack IPv6-only network infrastructure, as well as efficient utilization of public IPv4 addresses. The primary audience is IDC operators who are deploying IPv6, running out of available IPv4 addresses, and/or feeling that dual stack causes undesirable operational complexity.') |
|
2016-02-17
|
(System) | RFC published |