Hi Randy, Thank you for your pointer. I do not mean to say the SNMP design is problematic. But I think it's not designed for periodically getting operational data, which is one important case for streaming telemetry. Compared with current YANG-Push (https://datatracker.ietf.org/doc/draft-ietf-netconf-yang-push) activity, user can get any data described in existing YANG data store (not only the notifications), and can appoint the period when the data originator pushes the event.
Thanks, Tianran > -----Original Message----- > From: OPSAWG [mailto:[email protected]] On Behalf Of Randy Presuhn > Sent: Thursday, October 18, 2018 8:38 AM > To: [email protected] > Subject: Re: [OPSAWG] Thoughts on draft-song-opsawg-ntf > > Hi - > > On 10/16/2018 8:08 PM, Tianran Zhou wrote: > .... > > 2. no customizable periodical and on-change export. So have to use poll > operation. > > Have you tried RFC 2981 or RFC 3877? > If so, what aspects of their design did you find problematic? > > > 3. need special definition and support, not apply for any mib data. > > I don't understand what this is intended to mean. > > Randy > > _______________________________________________ > OPSAWG mailing list > [email protected] > https://www.ietf.org/mailman/listinfo/opsawg _______________________________________________ OPSAWG mailing list [email protected] https://www.ietf.org/mailman/listinfo/opsawg
