From ad114b18cf164a582e0fd30ddc80c458d2366b2f Mon Sep 17 00:00:00 2001 From: Tore Anderson Date: Thu, 23 Jul 2015 13:29:28 +0200 Subject: [PATCH] Update for siit-dc ietf changes - the siit-dc drafts have been adopted by the v6ops wg - host agent renamed to edge relay --- README.pod | 33 ++++++++++++++++----------------- 1 file changed, 16 insertions(+), 17 deletions(-) diff --git a/README.pod b/README.pod index d098eb3..1c51b1b 100644 --- a/README.pod +++ b/README.pod @@ -1,6 +1,6 @@ =head1 NAME -B - a CLAT / SIIT-DC Host Agent implementation for Linux +B - a CLAT / SIIT-DC Edge Relay implementation for Linux =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, or if they are simply not using DNS64). -It may also be used to implement an SIIT-DC Host Agent as defined by -I. In this scenario, the PLAT is a SIIT-DC -Gateway (see I) instead of a Stateful NAT64 (see -I). When used as a SIIT-DC Host Agent, you will probably want to -manually configure the settings I, I, and -I to mirror the SIIT-DC Gateway's configuration. +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. It relies on the software package TAYGA by Nathan Lutchansky for the actual translation of packets between IPv4 and IPv6 (I) 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, there should be no need to change the default. -When using B as an SIIT-DC Host Agent (cf. -I-D.draft-anderson-v6ops-siit-dc-2xlat), you will want to set this to the -IPv4 Service Address configured in the SIIT-DC Gateway. 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. =item B (default: auto-generated) The IPv6 address of the CLAT. Traffic to/from the B will be -translated into this address. When using B as an SIIT-DC Host Agent, -you will want to set this to the IPv6 address in the Static Address Mapping -configured in the SIIT-DC Gateway. +translated into this address. When using B as an SIIT-DC Edge Relay, you +will want to set this to the same IPv6 address in the Explicit Address Mapping +configured in the SIIT-DC Border Relay. By default, B will attempt to figure out which network device will be 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 -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