RE: [dhcwg] RE: draft-bakke-dhc-snmp-trap-00.txt

[Randy Presuhn <[e-mail]>]

Hi -

> Message-ID: <[e-mail]>
> From: "Wijnen, Bert (Bert)" <[e-mail]>
> To: Mark Bakke <[e-mail]>
> Cc: "'[e-mail]'" <[e-mail]>,
>         "snmpv3@lists. tislabs. com (E-mail)" <[e-mail]>,
>         [e-mail]
> Subject: RE: [dhcwg] RE: draft-bakke-dhc-snmp-trap-00.txt
> Date: Tue, 24 Sep 2002 11:16:07 +0200
...
> > > First question would be: is it a generic problem that people face?
> > Yes.  There are increasingly more solutions that allow hosts,
> > racks of servers, embedded devices, etc. to be booted from
> > the network.  When this fails, the host's normal configuration
> > info (particularly the SNMP notification list) is not available,
> > so there's no good way to tell a management station about it.
> > 
> > I assume that most networks would want to use SNMP for this,
> > but syslog would work as well.
> > 
> 
> Mark's answer is just one answer that seem to support a YES answer
> Any others?
...

There has been some other work in the area of getting out
notifications of "pre-OS" systems, e.g.,
http://www.dmtf.org/standards/documents/ASF/DSP0114.pdf

However, this work does *not* address security, other than
to discourage implementors from providing protocol-level
security and to instead rely on "deployment schemes and
firewalls" (!).

Could information delivered via DHCP be used to accomplish a
"kick start" of the secrets, similar to that in RFC 2786?

 ------------------------------------------------------
 Randy Presuhn          BMC Software, Inc.  SJC-1.3141
 [e-mail]  2141 North First Street
 Tel: [phone]   San José, California 95131  USA
 ------------------------------------------------------
 My opinions and BMC's are independent variables.
 ------------------------------------------------------
_______________________________________________
dhcwg mailing list
[e-mail]
https://www1.ietf.org/mailman/listinfo/dhcwg