<no hats> Dear OPSAWG, We have written a draft that outlines a set of use case and requirements for a bulk data collection system for collecting large amounts of data from network infrastructure. The system is designed to allow for faster / lower overhead access than things like SNMP, and be friendlier than things like screen scraping.
While the document will probably end up in I2RS, we wanted to discuss it here, because we want to make sure that the use cases and requirement capture *operators* input, and because this is a (proposed) new management solution. We have already discussed this idea / concept with a number of operators (including large content type players), at places like NANOG and have incorporated their feedback, but would really appreciate additional review, use cases, discussion, etc. W </no hats> Begin forwarded message: > From: [email protected] > Subject: New Version Notification for > draft-swhyte-i2rs-data-collection-system-00.txt > Date: October 21, 2013 2:11:18 PM EDT > To: Scott Whyte <[email protected]>, Marcus Hines <[email protected]>, Warren > Kumari <[email protected]> > > > A new version of I-D, draft-swhyte-i2rs-data-collection-system-00.txt > has been successfully submitted by Scott Whyte and posted to the > IETF repository. > > Filename: draft-swhyte-i2rs-data-collection-system > Revision: 00 > Title: Bulk Network Data Collection System > Creation date: 2013-10-21 > Group: Individual Submission > Number of pages: 10 > URL: > http://www.ietf.org/internet-drafts/draft-swhyte-i2rs-data-collection-system-00.txt > Status: > http://datatracker.ietf.org/doc/draft-swhyte-i2rs-data-collection-system > Htmlized: > http://tools.ietf.org/html/draft-swhyte-i2rs-data-collection-system-00 > > > Abstract: > Collecting large amounts of data from network infrastructure devices > has never been very easy. Existing methods generate CPU and memory > loads that may be unacceptable, the output varies across > implementations and can be difficult to parse, and these methods are > often difficult to scale. I2RS programmatic interfacing with the > routing system may exacerbate this problem: state needs to be > collected from nodes and fed to consumers participating in the > control plane that may not be physically close to the nodes. This > state includes not only control plane information, but elements of > the data plane that have a direct impact on control plane behavior, > like traffic engineering. > > This document outlines a set of use cases requiring a flexible > framework to collect routing system data, and the features and > functionality needed to make such a framework useful for these use > cases. > > > > > > Please note that it may take a couple of minutes from the time of submission > until the htmlized version and diff are available at tools.ietf.org. > > The IETF Secretariat > -- "I think it would be a good idea." - Mahatma Ghandi, when asked what he thought of Western civilization _______________________________________________ OPSAWG mailing list [email protected] https://www.ietf.org/mailman/listinfo/opsawg
