Re: modules of a mh solution (was RE: New multi6 draft: WIMP)

[Dave Crocker <dhc@dcrocker.net>]

marcelo,

mb> I agree that the mechanism to learn one's own addresses is fundamental, but
mb> i thought that the mechanism to do that would be stateless (or statefull)
mb> address autoconfiguration...

mb> Do you think that we may need something else?

I don't have any particular thoughts about the solution for this.  As
long as it scales at least as well as DHCP it is fine with me.

The one thing that makes this more challenging than DHCP is the problem
of timing and initiative.  DHCP is triggered by the client with an
obvious example being system boot.

For multiaddressing, the easy question is how to supply information
about multiple addresses at system boot.

The harder question is how to get information about the availability of
new addresses to the client system? Offhand, I think this requires a
"push" mechanism from the network, rather than a pull mechanism from the
client, in order to make sure the client learns of the changes in a
timely fashion.


d/
--
 Dave Crocker <dcrocker-at-brandenburg-dot-com>
 Brandenburg InternetWorking <www.brandenburg.com>
 Sunnyvale, CA  USA <tel:+1.408.246.8253>