Hi Erik, Mobileip and NEMO scenarios may benefit from using only site locals, if global addresses in the access networks are unavailable or invalid/off-topology.
In this case, e-to-e global connectivity is available through the mobility management agent, which provides a global address or addresses at the edge of the local mobility domain. It can also be used to enforce localized management policy. (all packets are reverse tunnelled to the mobility management agent). Still, these may not be sufficiently good reasons to place these ideas into discussion. I didn't intend to cloud the waters, but I can't see many other uses for site-local in the mipv6 access network. Greg Erik Nordmark wrote: > > > there's a set of cases where the MN uses Localized mobility management > > such as HMIPv6 and can use only site locals within a set of access > > networks. > > > I'm not sure if this is complete, but I don't see it's that > > problematic. > > Which problem are you trying to solve here to which the solution > is to use site local addresses? > > I don't see why using site local addresses in the context of local mobility > has any benefits, but perhaps I'm missing something. > > The cases when site-local addresses don't offer any benefits and they > don't cause any additional complexity or problems are not interesting to > discuss since it doesn't help folks understand the tradeoffs between > different levels of support for site-locals. > > Erik -------------------------------------------------------------------- IETF IPng Working Group Mailing List IPng Home Page: http://playground.sun.com/ipng FTP archive: ftp://playground.sun.com/pub/ipng Direct all administrative requests to [EMAIL PROTECTED] --------------------------------------------------------------------
