Hi Alia, Thanks for starting the conversation :-)
IMO, the lines between 'network-centric' and 'device-centric' are a little blurred. For the sake of argument, let me agree with Joel that the I2RS WG's scope should be limited to a single routing system. Let me ask a few questions then: * Is an OSPF router or an IS-IS router a 'routing system', as defined in the WG charter? If yes, would its LSDB be considered 'topology information' as defined in the WG charter? And if the the answer to the latter question is yes, would reading the LSDB information from the router via a tbd. I2RS protocol be considered 'extraction of information about topology from the network', as defined in the WG charter? * Is a BGP Router Reflector a routing system, as defined in the WG charter of the WG? If yes, would the LSDB information (potentially collected from multiple IGP areas) in RR's BGP-RIB be considered 'topology information' as defined in the WG charter? And if the the answer to the latter question is yes, would reading the LSDB information from the RR be considered 'extraction of information about topology from the network', as defined in the WG charter? And if the BGP RR implements BGP-LS, would extracting the LSDB information from the RR be in scope of the WG? Could BGP-LS actually be considered a candidate for an I2RS protocol that would be 'extracting information about topology from the network'? Thanks, Jan From: Alia Atlas <[email protected]<mailto:[email protected]>> Date: Wednesday, November 6, 2013 6:23 PM To: "[email protected]<mailto:[email protected]>" <[email protected]<mailto:[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 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. 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
