AS1024/clatd
1
0
Fork 0
mirror of https://github.com/toreanderson/clatd synced 2026-09-22 14:41:19 +00:00
Code Issues Packages Projects Releases Wiki Activity

Update for siit-dc ietf changes

Browse Source 
- the siit-dc drafts have been adopted by the v6ops wg
- host agent renamed to edge relay
This commit is contained in:
Tore Anderson
2015-07-23 13:29:28 +02:00
parent c48ad644c0
commit ad114b18cf
1 changed files with 16 additions and 17 deletions
Download Patch File Download Diff File Expand all files Collapse all files

33
README.pod
View File

@@ -1,6 +1,6 @@
=head1 NAME =head1 NAME
B<clatd> - a CLAT / SIIT-DC Host Agent implementation for Linux B<clatd> - a CLAT / SIIT-DC Edge Relay implementation for Linux
=head1 DESCRIPTION =head1 DESCRIPTION
@@ -13,12 +13,12 @@ local applications on the host requires actual IPv4 connectivity or cannot
make use of DNS64 (for example because they use legacy AF_INET socket calls, make use of DNS64 (for example because they use legacy AF_INET socket calls,
or if they are simply not using DNS64). or if they are simply not using DNS64).
It may also be used to implement an SIIT-DC Host Agent as defined by B<clatd> may also be used to implement an SIIT-DC Edge Relay as described in
I<I-D.anderson-v6ops-siit-dc-2xlat>. In this scenario, the PLAT is a SIIT-DC I<I-D.ietf-v6ops-siit-dc-2xlat>. In this scenario, the PLAT is in reality a
Gateway (see I<I-D.anderson-v6ops-siit-dc>) instead of a Stateful NAT64 (see SIIT-DC Border Relay (see I<I-D.ietf-v6ops-siit-dc>) instead of a Stateful
I<RFC6146>). When used as a SIIT-DC Host Agent, you will probably want to NAT64 (see I<RFC6146>). When used as a SIIT-DC Edge Relay, you will probably
manually configure the settings I<clat-v4-addr>, I<clat-v6-addr>, and want to manually configure the settings I<clat-v4-addr>, I<clat-v6-addr>, and
I<plat-prefix> to mirror the SIIT-DC Gateway's configuration. I<plat-prefix> to mirror the SIIT-DC Border Relay's configuration.
It relies on the software package TAYGA by Nathan Lutchansky for the actual It relies on the software package TAYGA by Nathan Lutchansky for the actual
translation of packets between IPv4 and IPv6 (I<RFC 6145>) TAYGA may be translation of packets between IPv4 and IPv6 (I<RFC 6145>) TAYGA may be
@@ -132,21 +132,20 @@ will bind to this address when communicating with external IPv4 destinations.
In a standard 464XLAT environment with a stateful NAT64 serving as the PLAT, In a standard 464XLAT environment with a stateful NAT64 serving as the PLAT,
there should be no need to change the default. there should be no need to change the default.
When using B<clatd> as an SIIT-DC Host Agent (cf. When using B<clatd> as an SIIT-DC Edge Relay (I<I-D.ietf-v6ops-siit-dc-2xlat>),
I-D.draft-anderson-v6ops-siit-dc-2xlat), you will want to set this to the you will want to set this to the IPv4 Service Address configured in the SIIT-DC
IPv4 Service Address configured in the SIIT-DC Gateway. This way, local Border Relay. This way, local applications can correctly identify which public
applications can correctly identify which public address they'll be using on address they'll be using on the IPv4 internet, and will be able to provide
the IPv4 internet, and will be able to provide fully functional references to fully functional references to it in application-level payload, and so on.
it in application-level payload, and so on.
The default address is one from I<RFC 7335>. The default address is one from I<RFC 7335>.
=item B<clat-v6-addr=ipv6-address> (default: auto-generated) =item B<clat-v6-addr=ipv6-address> (default: auto-generated)
The IPv6 address of the CLAT. Traffic to/from the B<clat-v4-addr> will be The IPv6 address of the CLAT. Traffic to/from the B<clat-v4-addr> will be
translated into this address. When using B<clatd> as an SIIT-DC Host Agent, translated into this address. When using B<clatd> as an SIIT-DC Edge Relay, you
you will want to set this to the IPv6 address in the Static Address Mapping will want to set this to the same IPv6 address in the Explicit Address Mapping
configured in the SIIT-DC Gateway. configured in the SIIT-DC Border Relay.
By default, B<clatd> will attempt to figure out which network device will be By default, B<clatd> will attempt to figure out which network device will be
used for traffic towards the PLAT, see if there is any SLAAC-based globally used for traffic towards the PLAT, see if there is any SLAAC-based globally
@@ -343,6 +342,6 @@ ip(8), ip6tables(8), tayga(8), tayga.conf(5)
RFC 6052, RFC 6145, RFC 6146, RFC 6877, RFC 7050, RFC 7335 RFC 6052, RFC 6145, RFC 6146, RFC 6877, RFC 7050, RFC 7335
I-D.anderson-v6ops-siit-dc, I-D.anderson-v6ops-siit-dc-2xlat I-D.ietf-v6ops-siit-dc, I-D.ietf-v6ops-siit-dc-2xlat, I-D.ietf-v6ops-siit-eam
=cut =cut