Great Circle Associates Network-Automation
(April 2005)
 

Indexed By Date: [Previous] [Next] Indexed By Thread: [Previous] [Next]

Subject: Re: available network automation tools
From: "Georg Magschok" <gio @ epygi . de>
Organization: Epygi Labs DE GmbH
Date: Tue, 12 Apr 2005 15:02:04 +0200
To: "'Albert Greenberg'" <albert @ research . att . com>
Cc: <network-automation @ greatcircle . com>
Importance: Normal
In-reply-to: <Pine.SGI.4.56.0504120822590.134141@light.research.att.com>

> > "The semantics of a network model should be defined by the network
> > elements!"

> I think you are right, though the level of abstraction providedd by the
> network elements may be quite low if you want network-wide rather than box
> by box management.  For example, ACLs can provide network-wide perimeter
> defense, with appropriate clauses embedded in the edge routers.  It's all
> there in the routers, but it is not expressed directly as a network-wide
> constraint (which might help manage ACLs).

The node would know well about itself, but not too much about the network
other than it's direct box by box relations or being part of various kinds
of peer groups. 
The network-wide constraints are not solved by the approach I propose, only
supported.

Thank you!
  Gio

Epygi Labs DE GmbH - Georg 'Gio' Magschok 



References:
Indexed By Date Previous: Re: available network automation tools
From: Albert Greenberg <albert@research.att.com>
Next: Re: available network automation tools
From: Kirby Files <ksfiles@gmail.com>
Indexed By Thread Previous: Re: available network automation tools
From: Albert Greenberg <albert@research.att.com>
Next: Re: available network automation tools
From: Andrew Fort <andrew.fort@gmail.com>

Google
 
Search Internet Search www.greatcircle.com