On Wed, Jan 9, 2013 at 11:18 AM, William Herrin <b...@herrin.us> wrote: > About the only time you'd strictly *need* dynamic configuration in an > OOB is when directly connecting it to a commodity Internet link. If > you're willing to give your poorly secured and rarely updated OOB a > public IP address, you're a braver man than I am. If you are that > "brave" then you'll need a more robust set of dynamic configuration > tools than just the ones you've listed and you'll also need a dynamic > dns client or some other mechanism for the the OOB to let you know > what addresses it ended up on.
it's possible that he's thinking of a world where your dhcp is not 'dynamic' but a management system which can keep all the other bits of information updated (and easily updatable!) for the remote nodes: ip address def-gw dns servers for instance.