mirrors/clatd
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Update doc regarding limitations on non-SLAAC nets

Browse Source 
The LIMITATIONS part of the documentation wasn't updated to take into
account the changes in 81f2c61, fix that.

Closes #24.
This commit is contained in:
Tore Anderson
2025-02-02 09:33:38 +01:00
parent cc64d0c6f3
commit 05728771ca
1 changed files with 13 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files

16
README.pod
View File

@@ -382,13 +382,23 @@ unset or 0, there is no default.
=head1 LIMITATIONS =head1 LIMITATIONS
B<clatd> will not be able to acquire an IPv6 address for the CLAT if SLAAC If no IPv6 addresses on the PLAT-facing device are EUI-64-derived (e.g., when
isn't used. I<RFC 6877> suggests DHCPv6 IA_PD should be attempted in this using SLAAC with I<RFC 4941> or I<RFC 7217> privacy addressing or static
case, but this isn't currently implemented. addresses), B<clatd> will generate and use an CLAT IPv6 address using a random
Interface ID from the same subnet prefix (if it is /120 or shorter).
I<RFC 6877> suggests DHCPv6 IA_PD should be attempted in this case instead, but
this isn't currently implemented.
B<clatd> will not attempt to perform Duplicate Address Detection for the IPv6 B<clatd> will not attempt to perform Duplicate Address Detection for the IPv6
address it generates. This is a violation of I<RFC 6877>. address it generates. This is a violation of I<RFC 6877>.
There is no guarantee that the generated CLAT IPv6 address is in fact usable,
as the network might block its use.
If the upstream network is using DHCPv6, B<clatd> will not be able to generate
a CLAT IPv6 address at all, due to the fact that DHCPv6-assigned addresses do
not carry a prefix length.
B<clatd> will not attempt to perform a connectivity check to a discovered PLAT B<clatd> will not attempt to perform a connectivity check to a discovered PLAT
prefix before setting up the CLAT, as I<RFC 7050> suggest it should. prefix before setting up the CLAT, as I<RFC 7050> suggest it should.