[Infrastructures] using IA methodologies to build network element configuration
David Magda
David Magda <dmagda+infra@ee.ryerson.ca>
Sun, 3 Apr 2005 11:46:28 -0400
On Sun, Apr 03, 2005 at 02:56:01PM +0100, Matt S Trout wrote:
> This is why I'm attempting to build an XML-driven transformation
> engine that can be used to build up a common library of transforms
> for various types of devices. It's called BAST, and is still at a
Matt,
You may want to check out the Netconf WG of the IETF:
The Netconf Working Group is chartered to produce a protocol
suitable for network configuration, with the following
characteristics:
- Provides retrieval mechanisms which can differentiate between
configuration data and non-configuration data
- Is extensible enough that vendors will provide access to all
configuration data on the device using a single protocol
- Has a programmatic interface (avoids screen scraping and
formatting-related changes between releases)
- Uses a textual data representation, that can be easily
manipulated using non-specialized text manipulation tools.
- Supports integration with existing user authentication methods
- Supports integration with existing configuration database
systems
- Supports network wide configuration transactions (with
features such as locking and rollback capability)
- Is as transport-independent as possible
- Provides support for asynchronous notifications
http://www.ietf.org/html.charters/netconf-charter.html
The current document describing the protocol (which expires August
19, 2005) can be found at:
http://www.ietf.org/internet-drafts/draft-ietf-netconf-prot-05.txt
There are also drafts for transporting the XML protocol over BEEP,
SOAP, and SSH (through a sub-system like sftp is done now).
--
David Magda <dmagda at ee.ryerson.ca>, http://www.magda.ca/
Because the innovator has for enemies all those who have done well under
the old conditions, and lukewarm defenders in those who may do well
under the new. -- Niccolo Machiavelli, _The Prince_, Chapter VI