With my chair hat off: Any 'device-centric' model must be composable into a 'network-wide' model, otherwise it's not particularly useful. So yes, +1 and agree with Shane.
with my chair hat on: I believe *this specifically* is in charter. On Thu, Nov 7, 2013 at 11:12 AM, Shane Amante <[email protected]> wrote: > > On Nov 7, 2013, at 9:15 AM, Nikolay Milovanov <[email protected]> wrote: > > In the end to build a network centric info/data model out of this the > network topology manager will have to collect and transform information > gained from many network devices. > > > +1. > > I believe I may be observing a tension between the traditional IETF view of > "how do I make two devices communicate together", i.e.: what's the protocol > that allows that communication to occur robustly, vs. an operator view of > "Sure, I need protocols to make two devices talk to each other, but what's > more critical for my business is to look at the whole network, which is a > collection of devices". A Network Topology Information Model would assist > operators with having a cohesive view of the overall "network as a system", > because that's the foundation upon which _services_ are delivered ... both > within the data-path between various NE's and on top of various NE's. > > So, +1 to network-centric topology IM model. > > -shane > > > > _______________________________________________ > i2rs mailing list > [email protected] > https://www.ietf.org/mailman/listinfo/i2rs > _______________________________________________ i2rs mailing list [email protected] https://www.ietf.org/mailman/listinfo/i2rs
