[159340] in North American Network Operators' Group
Re: OOB core router connectivity wish list
daemon@ATHENA.MIT.EDU (William Herrin)
Wed Jan 9 11:27:40 2013
In-Reply-To: <CAL9jLaYbJe0W7Rf_jUKciC826L++1QiB_WMLtTo2qjGEUqdzUw@mail.gmail.com>
From: William Herrin <bill@herrin.us>
Date: Wed, 9 Jan 2013 11:25:47 -0500
To: Christopher Morrow <morrowc.lists@gmail.com>
Cc: nanog@nanog.org
Errors-To: nanog-bounces+nanog.discuss=bloom-picayune.mit.edu@nanog.org
On Wed, Jan 9, 2013 at 11:21 AM, Christopher Morrow
<morrowc.lists@gmail.com> wrote:
> On Wed, Jan 9, 2013 at 11:18 AM, William Herrin <bill@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.
Sure, but in that scenario you don't *need* a dhcp system, it's merely
a "nice to have." Hence a P2 not a P1.
Regards,
Bill Herrin
--
William D. Herrin ................ herrin@dirtside.com bill@herrin.us
3005 Crane Dr. ...................... Web: <http://bill.herrin.us/>
Falls Church, VA 22042-3004
