From: Tom H. <sou...@to...> - 2003-07-08 03:06:48
|
All we need to do now is create a format for connections, cableing and support hardware (power supplies, UPS, etc...) -----Original Message----- From: wis...@li... [mailto:wis...@li...] On Behalf Of Tom Haynes Sent: Monday, July 07, 2003 9:58 PM To: wis...@li... Subject: RE: [Wisp-mss-general] Network description language I believe that storing the information in XML is the way to go. Since = SNMP MIB2 already has most of the information we will be needing categorized, = I think we should take the device informatin layout and naming scemes from MIB2. This way, gathering the needed information is fairly straight = forward. =20 -----Original Message----- From: wis...@li... [mailto:wis...@li...] On Behalf Of Tom Haynes Sent: Thursday, July 03, 2003 8:23 PM To: WISP-MSS General List Subject: [Wisp-mss-general] Network description language I think one of the first long-term projects that need to be worked on is = a standardized way to describe a network that a proram can read to = understand how to control, modify, manage and troubleshoot the devices and = connections. Is there any current standard? I think that XML would be a good base to start from. The basic concepts = of WISP-MSS is to allow the services to be run from any where, on any = platform. I would like to see a complete collection of services that can be run = from a central location or as standalone modeules on any network. I we can incorporate a distributed computing format, we can minimize the impact = on any one machine. |