[ntpwg] [dhcwg] NTP option: IP address and/or FQDN

[David W. Hankins]

On Sat, Dec 08, 2007 at 11:18:42PM -0500, Danny Mayer wrote:
> > As it seems that, after at least two long discussions in the same topic,
> > there is a "common" understanding on how should be advertize servers, it
> > could be useful to capture these conclusions as guidelines in the
> > dhc-option-guidelines draft. This would help a lot other working groups
> > when they will have to design new options for the same usage.

At present it only says one word on the subject; 'late-binding'.

What I thought that "obviously" meant was, "DNS is the obvious right
tool for the job if you want the (IP address or SRV or whatever) to
be discovered at a time much later than DHCP's completion, such as
from user input or at the very start of some alternate chain of
events."

So for example, t'were it me, I'd configure an rfc1035 domain name
for the outbound mail gateway.  This is a function that happens in
a practically random way; whenever the user sends mail.  It isn't
an event that follows from a reconfiguration event, nor something
that is 'always on'.  It's always done after bootstrapping is
fully complete (or else your mailer is stuck in 'offline mode').

It's also something that isn't presently carried by DHCP, nor is it
likely to be preferred to be.


So, it could probably say more.

-- 
Ash bugud-gul durbatuluk agh burzum-ishi krimpatul.
-- 
David W. Hankins	"If you don't do it right the first time,
Software Engineer		     you'll just have to do it again."
Internet Systems Consortium, Inc.		-- Jack T. Hankins
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
Url : https://lists.ntp.org/pipermail/ntpwg/attachments/20071210/2298a7f8/attachment.bin