Re: IPSec MIB

["William Allen Simpson" <wsimpson@greendragon.com>]

> From: Uri Blumenthal <uri@watson.ibm.com>
> Angelos D. Keromytis says:
> > a) this is useful mostly for debugging (-> development)
> > b) why open a potential hole there if it's not going to be used by
> >    your every-day user/admin/whoever
>
> You might be surprised, but most OTHER vendors do have bugs
> in their code, and systems do get misconfigured more often
> than not. Thus, "debugging" isn't only done by the vendor
> quality control - but often by the customers as well.
>
Gentlefolk, in my experience, it has been a long standing policy of the
network management area that protocol debugging and development
variables are _not_ appropriate for MIBs.

I expect that IESG integration of management with operations should make
that even more clear.

WSimpson@UMich.edu
    Key fingerprint =  17 40 5E 67 15 6F 31 26  DD 0D B9 9B 6A 15 2C 32
BSimpson@MorningStar.com
    Key fingerprint =  2E 07 23 03 C5 62 70 D3  59 B1 4F 5E 1D C2 C1 A2

---

• Prev by Date: Re: Slicing and Dicing in new-esp
• Next by Date: RE: Slicing and Dicing in new-esp
• Prev by thread: Re: IPSec MIB
• Next by thread: Re: IPSec MIB
• Index(es):
  • Main
  • Thread