[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: 3gpp-analysis document and automatic tunneling


Pekka Savola wrote:
On Thu, 29 May 2003, Fred Templin wrote:

Pekka Savola wrote:


Careful here: you're proposing to extend ISATAP to be used across multiple administrative boundaries -- which is *specifically* has not meant to be (AFAIR)!


Nothing of the sort. The isatap client is within the administrative
domain of the isatap router. The isatap router serves a /64 dhcpv6
prefix delegation to the client. The client uses this prefix to connect
as many additional hosts as it wishes using, e.g., the multi-link subnet
model and RA proxies. It's just like what happens when the GGSN serves a
/64 to a mobile via the IPv6 PDP context; it has nothing at all to do
with multiple administrative boundaries. Again, the main point is that
the isatap client can connect many hosts - not just one.

Could you describe the scenario in more detail?

It seems to me that the approach in above is that ISATAP link-local
addresses would be used between the router and the client.


In the simplest cases, yes.


The client is
in different admin domain as the router
No. The client gets an RA from the router that contains a non-zero router
lifetime and adds it to the default router list. The client is in the same admin
domain as the router.

(tradeoffs of this might be
manageable), as is in a different admin domain as all the other clients
(which would also appear to be on the same link).
All the other clients would also be on the same link as the router. Each client
can request a dhcpv6 prefix delegation, with the dhcpv6 server implemented
on the router as allowed by the specs. Then, each client can connect multiple
additional hosts using the prefix delegation it received from the router.

Fred
ftemplin@iprg.nokia.com