----- Original Message ----- From: "Linda Dunbar" <[email protected]> To: "Scott Whyte" <[email protected]>; <[email protected]>; <[email protected]> Cc: <[email protected]> Sent: Thursday, April 10, 2014 4:39 PM
Scott, et al, Your draft listed comprehensive requirement on what data you need to pull out of a router. The Section 3 (Use Cases) , I was hoping to see some use cases on how those collected data are used. But Section 3 only listed bunch of data that you need. So Section 3 is really the "Requirement" (instead of use cases). Do you have any examples showing how those data are used? Concrete examples can greatly help router vendors to prioritize the information to be pulled when there is resource contention. Even though the primary objective is "Collecting large data sets with high frequency with minimal impact to device's CPU", very often "large set & high frequency" do need CPU cycles. Both Syslog and IPFIX were intended to export data from devices. What are the limitation of those schemes? <tp> When anyone says 'use cases', I find myself going back to our charter, which calls for us to work on tightly scoped key use cases, listing six. I look at those six to see where this fits. Um, I struggle to see the fit with the charter. Tom Petch Thanks, Linda Dunbar ------------------------------------------------------------------------ -------- > _______________________________________________ > i2rs mailing list > [email protected] > https://www.ietf.org/mailman/listinfo/i2rs > _______________________________________________ i2rs mailing list [email protected] https://www.ietf.org/mailman/listinfo/i2rs
