RFC 7755: SIIT-DC: Stateless IP/ICMP Translation for IPv6 Data Center Environments
In plain English — editorial summary, not part of the RFC
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.
Document record
- Document ID
- RFC7755
- Published
- February 2016
- Authors
- T. Anderson
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- ops
- Pages
- 24
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 7756Stateless IP/ICMP Translation for IPv6 Internet Data Center Environments (SIIT-DC): Dual Translation ModeCurrent
February 2016
- RFC 7757Explicit Address Mappings for Stateless IP/ICMP TranslationCurrent
February 2016
- RFC 7445Analysis of Failure Cases in IPv6 Roaming ScenariosCurrent
March 2015
- RFC 7341DHCPv4-over-DHCPv6 (DHCP 4o6) TransportCurrent
August 2014
- RFC 7849An IPv6 Profile for 3GPP Mobile DevicesCurrent
May 2016
- RFC 7934Host Address Availability RecommendationsCurrent
July 2016
- RFC 8215Local-Use IPv4/IPv6 Translation PrefixCurrent
August 2017
- RFC 8305Happy Eyeballs Version 2: Better Connectivity Using ConcurrencyCurrent
December 2017
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?