commit 1abcec1285585ede73b937b4082828755ee9c61c Author: Tore Anderson Date: Thu Jan 28 13:40:05 2016 +0100 Minor documentation fixes diff --git a/README.pod b/README.pod index 3fb6af0..41591c8 100644 --- a/README.pod +++ b/README.pod @@ -159,7 +159,7 @@ example: B -=item B (no default) +=item B (no default) This works exactly the same as B, only that this script is run right after TAYGA has exited, before the clean-up process of restoring any settings @@ -354,7 +354,7 @@ If you enable B while at the same time disabling B, B will remove any pre-existing IPv4 default routes but not add any of its own. -Setting B to Iwill disable the IPv4 connectivity +Setting B to I will disable the IPv4 connectivity check. =item B (default: I<2048>) commit 18dca086c2c4279195bad9a38991b0b2360ca449 Author: Tore Anderson Date: Mon Mar 28 08:38:56 2016 +0200 Update siit-dc/eam I-D references to RFC numbers The three I-Ds that describe SIIT-DC and SIIT-EAM have been published as RFCs, so update the references accordingly. Also update once occurrence of old terminology ("Host Agent") with the new and final one ("Edge Relay"). diff --git a/README.pod b/README.pod index 41591c8..0cd227d 100644 --- a/README.pod +++ b/README.pod @@ -14,11 +14,11 @@ make use of DNS64 (for example because they use legacy AF_INET socket calls, or if they are simply not using DNS64). B may also be used to implement an SIIT-DC Edge Relay as described in -I. In this scenario, the PLAT is in reality a -SIIT-DC Border Relay (see I) instead of a Stateful -NAT64 (see I). When used as a SIIT-DC Edge Relay, you will probably -want to manually configure the settings I, I, and -I to mirror the SIIT-DC Border Relay's configuration. +I. In this scenario, the PLAT is in reality a SIIT-DC Border Relay +(see I) instead of a Stateful NAT64 (see I). When used as a +SIIT-DC Edge Relay, you will probably want to manually configure the settings +I, I, and I to mirror the SIIT-DC +Border Relay's configuration. It relies on the software package TAYGA by Nathan Lutchansky for the actual translation of packets between IPv4 and IPv6 (I) TAYGA may be @@ -183,11 +183,11 @@ will bind to this address when communicating with external IPv4 destinations. In a standard 464XLAT environment with a stateful NAT64 serving as the PLAT, there should be no need to change the default. -When using B as an SIIT-DC Edge Relay (I), -you will want to set this to the IPv4 Service Address configured in the SIIT-DC -Border Relay. This way, local applications can correctly identify which public -address they'll be using on the IPv4 internet, and will be able to provide -fully functional references to it in application-level payload, and so on. +When using B as an SIIT-DC Edge Relay (I), you will want to +set this to the IPv4 Service Address configured in the SIIT-DC Border Relay. +This way, local applications can correctly identify which public address +they'll be using on the IPv4 internet, and will be able to provide fully +functional references to it in application-level payload, and so on. The default address is one from I. @@ -436,8 +436,7 @@ SOFTWARE. ip(8), ip6tables(8), tayga(8), tayga.conf(5) -RFC 6052, RFC 6145, RFC 6146, RFC 6877, RFC 7050, RFC 7335 - -I-D.ietf-v6ops-siit-dc, I-D.ietf-v6ops-siit-dc-2xlat, I-D.ietf-v6ops-siit-eam +RFC 6052, RFC 6145, RFC 6146, RFC 6877, RFC 7050, RFC 7335 RFC 7755, RFC 7756, +RFC 7757 =cut diff --git a/clatd b/clatd index 9831d57..8af83ad 100755 --- a/clatd +++ b/clatd @@ -665,8 +665,8 @@ for (my $i = 0; $i < @ARGV;) { next; } elsif($ARGV[$i] =~ /^(-h|--help)$/) { print <<"EOF"; -clatd v$VERSION - a 464XLAT (RFC 6877) CLAT and SIIT-DC Host Agent - (I-D.anderson-v6ops-siit-dc-2xlat) implementation for Linux +clatd v$VERSION - a 464XLAT (RFC 6877) CLAT and SIIT-DC Edge Relay + (RFC 7756) implementation for Linux EOF print "\n"; print " Usage: clatd [-q] [-d [-d]] [-c config-file] ",