Bug#1098490: ITP: clatd -- CLAT and SIIT-DC ER with many XLAT engines
Package: wnpp
Severity: wishlist
Owner: Daniel Gröber <dxld@darkboxed.org>
X-Debbugs-Cc: debian-devel@lists.debian.org, dxld@darkboxed.org, Tore Anderson <tore@fud.no>
Hi d-devel,
I'm working on a movement to make IPv6 sexy again ([ANN] pending). As
part of that we need support for a shopping list of IPv6 RFCs in Linux
distros. CLAT is one of these. Debian is first to benefit from this
(NLnet funded) work :D.
* Package name : clatd
Version : 2.0.0
Upstream Contact: Tore Anderson <tore@fud.no>
* URL : https://github.com/toreanderson/clatd
* License : MIT
Programming Lang: Perl
Description : CLAT and SIIT-DC ER with many XLAT engines
The clatd script makes it easy to set up packet translation between IPv6
and IPv4 networks.
.
Supported deployment models include:
.
- IPv6-only/IPv6-mostly LANs (RFCs pending),
- ISPs using 464XLAT (RFC 6877) and
- Data centers using SIIT-DC (RFC 7755).
.
An RFC for the LAN deployment is currently in the works, see "6mops" IETF
draft.
.
When used on a LAN it is currently advisable to run clatd (or another CLAT
implementation) on all end-user computers. While the DNS64 (RFC 6147)
mechanism can help to make this less necessary and instead rely on the
network-wide NAT64 (RFC 6146) translation service this is considered at
best a transitory hack. Even if DNS64 is technically acceptable it is
challanging because some applications may use "address literals" directly
instead of relying on DNS to resolve names to addressess.
I'll maintain clatd myself. Co-maintainers welcome as always
#LowThresholdNMU. Going into Debian/ on Salsa.
--Daniel
Reply to: