[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
requirements
- To: ops-nm-suggestions@ops.ietf.org
- Subject: requirements
- From: Joe Provo <crimson@gweep.net>
- Date: Mon, 25 Jun 2001 17:22:18 -0400
- Delivery-date: Mon, 25 Jun 2001 14:22:20 -0700
- Envelope-to: ops-nm-suggestions-data@psg.com
- Organization: CARNIVORE Bait: anti-The Con Shin Bet spy spy porn Noriega
- Reply-To: crimson@gweep.net
- User-Agent: Mutt/1.2.5i
woody> Suzanne Woolf and I have been tasked with producing a draft
woody> to document operator requirements of infrastructure management
woody> methods.
I'd strongly urge the vendor/operator intersection be polled. Offhand, I
can only think of one company that isn't a device vendor fitting in that
intersection, other than homebrew/rtrmon/rancid, people seem to use
GoldWire's Formulator. I don't want to evangelize something, especially
something I don't use, but they may have experiences that can be shared
without venturing into their proprietary/competative space.
I have always rejected vendors who only hand compiled configurations (older
ascend, proteon). If it couldn't be parsed without being disassembled, it
was useless for me, and would be useless for generic databases &
configurations.
Hrm - I was just forwarded some interesting stuff from ops-nm. Off to join
& participate there.
Cheers,
Joe
--
crimson@sidehack.gweep.net * jprovo@gnu.ai.mit.edu * jzp@rsuc.gweep.net
RSUC / GweepNet / Spunk / FnB / Usenix / SAGE