> -----Original Message----- > From: [email protected] [mailto:[email protected]] On Behalf Of > Alia Atlas > Sent: Wednesday, November 06, 2013 6:23 PM > To: [email protected] > Subject: [i2rs] topology info model - what makes it a "network" model > vs. a "device" model > > I'd really like to start a conversation
...ok...so go ahead. :) > about the differences between a > topology IM model that is network-centric vs. device-centric. > Clearly > the WG has strong and different opinions about it. Are there really differences of opinion about what the difference is between a network model and a device model? A network is a plurality of devices, and a network model is something which deals with a system resulting from the use of more than one device. (ok, yes, a network of one node is a corner case blah blah handwave...). I don't see how there could be any real debate around this, but if there is I'm quite interested in what it might be. It feels like the real question is whether i2rs should have network models in scope. If Yes: ok, cool. But between link properties (that is, at least some kind of topology view), counter dumps, debugs, routing, MPLS, and LAG member rebalancing, show me what's *not* in scope. If Not: what problems arise that would be solved by having a network model, do we need one, and where would it come from if not i2rs? eric > > Since many people are here in Vancouver, focused on IETF and not their > day-jobs, this seems like a good time to get it rolling... > > Alia _______________________________________________ i2rs mailing list [email protected] https://www.ietf.org/mailman/listinfo/i2rs
