On Nov 9, 2009, at 6:16 PM, Pascal Thubert (pthubert) wrote:
I think that Ralph answered clearly on the DHCP question.
For memory (Ralph correct me please if I fail to word that correctly):
We still do stateless autoconf and the node comes up with its address
and publishes it.
DHCP has a different model whereby the address is owned and
delegated by
the server.
It would be good to get Ralph's expert opinion again and written down
this time so that we can lay this issue to rest.
I'd argue that the original purpose of stateless autoconf is claim and
defend - no centralized state is maintained anywhere. 6lowpan-nd
advertises a "claim and publish" model, which is slightly different.
But it's further arguable whether "claim and publish" is even valid
since the whiteboard may generate/assign addresses for individual
interfaces.
It would help a lot if we could identify the real *functional*
differences between the DHCP and whiteboard models for use in managing
addresses of 6lowpan interfaces.
--
Jonathan Hui
_______________________________________________
6lowpan mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/6lowpan
