Re: addition of TLV to locator ID or locator ID set

[Erik Nordmark <erik.nordmark@sun.com>]

Paul Jakma wrote:

>  From experience, you can do static NAT at your border for a set of 
> prefixes while routing them internally normally. The NAT is quite 
> invisible within your AS, as it is outside your AS - only your borders 
> know it.

Sure. But that assumes that the hosts know their addresses.

AFAICT in this case a host in the site wouldn't know what IPv6 address 
the shim proxy has assigned to it, and placed in the (external) DNS.

As I understood it, a host would configure its IPv6 address as today 
(stateless, DHCPv6, etc). And the shim proxy would form a HBA parameter 
set (based on the prefixes assigned to the site) for each host and run a 
1:1 NAT. In that case the host doesn't know which IPv6 address the proxy 
has picked for it.

Or where you thinking that the host could only use DHCPv6 and the shim 
proxy and the DHCP server would coordinate things so that the host is 
informed of its shimmed addresses?


> You wouldn't need split DNS for the shim6 site-intermediary case AFAICT, 
> because the locator addresses would never be reachable - only the mapped 
> address would ever be a valid address to try reach.

You mean you assume it is ok to publish unreachable addresses in the DNS?
Even if folks agree on that, the fact that the internal hosts would see 
both the local/internal address, and the shimmed addresses, would mean 
that they might seeming randomly end up using the shimmed addresses, and 
such internal communication ends up going via the proxy.

   Erik