Stateless translation: SIIT and address mapping
Explain stateless IP/ICMP translation (SIIT) between IPv4 and IPv6 (RFC 7915). Build IPv4-embedded IPv6 addresses with the RFC 6052 algorithm. Deploy SIIT with explicit address mappings (RFC 7757) for a published server.
Take the quiz · pass mark 70% · 9 questions
Explanation
Translation converts packets between IPv4 and IPv6 rather than tunnelling one inside the other. SIIT (Stateless IP/ICMP Translation, RFC 7915) rewrites the IP and ICMP headers on a per-packet basis with no per-flow state, so it scales and can be spread across devices. It is the engine inside NAT64 (L6.04) and the CLAT in 464XLAT (L6.05), and it can also be used on its own to publish an IPv6-only server to IPv4 clients.
How the address mapping works (RFC 6052)
Because SIIT is stateless, the IPv4 address must be carried inside the IPv6 address so the translator can recover it without a table. RFC 6052 defines how an IPv4 address is embedded in an IPv4-embedded IPv6 address using a translation prefix of length /32, /40, /48, /56, /64 or /96:
- With a /96 prefix the 32 bits of IPv4 occupy the last 32 bits (bits 96-127). This is the common case, including the well-known prefix 64:ff9b::/96.
- With the shorter lengths the 32 IPv4 bits are split around bits 64-71, which are reserved (the "u" octet) and must be zero.
So to translate, the device reads the IPv4 out of the IPv6 destination (IPv6 to IPv4) or writes it into the IPv6 source/destination (IPv4 to IPv6). No connection table is needed.
Explicit Address Mappings (RFC 7757)
Pure algorithmic mapping assumes a clean 1:1 relationship. Real deployments often need arbitrary IPv4 to IPv6 pairings — publishing one specific IPv6-only server behind one specific public IPv4, without a /96 of public IPv4. RFC 7757 defines Explicit Address Mappings (EAM): a table of IPv4-prefix to IPv6-prefix rules the SIIT device applies instead of (or alongside) the algorithmic prefix. EAM is how you say "public IPv4 198.51.100.10 is this IPv6-only server at 2001:db8:…" cleanly.
Limits
SIIT translates the header, so it shares the IPv4/IPv6 translation caveats: anything that carries an IP address in the payload (FTP active mode, SIP, IPv4 or IPv6 literals in application data) will not be fixed by a header translator, and DNS is handled separately (DNS64, L6.04). Translation also changes the header size, which has MTU consequences. Use it where the application is address-agnostic.
ictNetworks scenario
ictNetworks publishes an internal IPv6-only monitoring portal to a handful of legacy IPv4-only partners using SIIT with an RFC 7757 EAM: the partner reaches public IPv4 198.51.100.10, the SIIT box maps it to the portal's IPv6 address, and no per-flow state or extra public IPv4 block is needed. It documents that address-carrying protocols are out of scope and keeps SIIT for the clean HTTP/HTTPS case.
Drawing diagram…
Worked examples
Example 1: Embedding into the well-known /96
Embed IPv4 192.0.2.33 into 64:ff9b::/96. With a /96 the IPv4 goes in the last 32 bits: 192.0.2.33 = hex c0 00 02 21, so the address is 64:ff9b::c000:221. (192.0.2.33 is a documentation address, used only to show the embedding format; per RFC 6052 §3.1 the well-known prefix must not represent non-global IPv4 — real well-known-prefix translation uses globally unique IPv4, or a network-specific prefix such as 2001:db8:64::/96 for non-global ranges.)
Example 2: Embedding into a /64 translation prefix
Embed IPv4 198.51.100.10 into the translation prefix 2001:db8:122::/64. With a /64 prefix bits 64-71 are the reserved zero octet and the 32 IPv4 bits (c6 33 64 0a) occupy bits 72-103, giving 2001:db8:122:0:c6:3364:a00:0.
Example 3: Why the header grows
Translating an IPv4 packet (20-byte header) to IPv6 (40-byte header, no options) adds 20 bytes of header. The translator must account for this in MTU handling so it does not create packets the next hop cannot carry.
Lab
Goal: Publish an IPv6-only server to IPv4 clients through SIIT.
You need: a namespace/containerlab topology with an IPv4-only client, a SIIT translator (for example Jool in SIIT mode) and an IPv6-only web server; curl, ping/ping6 and tcpdump. (Jool flags and syntax vary by version — check the version's docs.)
- Give the server an IPv6 address and confirm it serves over IPv6 only.
- Configure SIIT with a translation prefix and verify algorithmic mapping by building the IPv4-embedded address with RFC 6052 by hand and pinging it.
- Add an RFC 7757 EAM mapping public IPv4 198.51.100.10 to the server's IPv6 address.
- From the IPv4-only client,
curlhttp://198.51.100.10/ and confirm it reaches the IPv6-only server; capture both sides to see the stateless header rewrite. - Test an address-carrying case (e.g. an IPv4 literal in the page) and document why SIIT does not fix it.
What to submit: the SIIT/EAM configuration, your hand-computed RFC 6052 address, the client-side success, the captures, and the note on translation limits.
Summary
- SIIT (RFC 7915) rewrites IPv4/IPv6 headers statelessly, so it scales and underpins NAT64 and CLAT.
- RFC 6052 embeds the IPv4 address inside the IPv6 address; with a /96 it is the last 32 bits, with shorter prefixes it is split around the reserved bits 64-71.
- RFC 7757 Explicit Address Mappings give arbitrary IPv4-to-IPv6 pairings for publishing specific servers.
- Translation does not fix addresses carried in payloads and changes header size (MTU).
- Next lesson (L6.04): NAT64 and DNS64.
Quiz imported · 9 questions · pass mark 70%. Lab questions are not auto-marked.