Hi,
IPFIX has been quite a useful tool for bulk data export. But the configuration 
model has posed quite a bit of a challenge in integrating IPFIX into the 
contemporary Netconf-Yang systems (no interface-ref, lists without keys, etc). 
The model proposed in draft-boydseda-ipfix-psamp-bulk-data-yang-model-03 
effectively addresses these challenges.
Further, by defining a dedicated model for bulk data export, it has ironed out 
the complexities that existed in having to use a model meant for packet 
sampling (most of the fields in the cache node were not applicable/needed for 
bulk data export).
I support this draft being taken into the OPSAWG and hope/believe that it would 
mature into a full-fledged RFC in the near future.


Regards,

Anand Arokiaraj


-----Original Message-----
From: Joe Clarke (jclarke) 
<[email protected]<mailto:[email protected]>>
Date: Sat, 18 Apr 2020 at 22:14
Subject: [OPSAWG] Call for adoption: 
draft-boydseda-ipfix-psamp-bulk-data-yang-model
To: opsawg <[email protected]<mailto:[email protected]>>

As was discussed in the April 7 virtual interim, we are doing a three-week call 
for opsawg adoption for this work.

This draft was an AD-sponsored work with Ignas and has now moved under Rob.  It 
has received a number of reviews (some thorough, some more cursory), and it is 
destined to obsolete 6728 (Configuration Data Model for the IP Flow Information 
Export (IPFIX) and Packet Sampling (PSAMP) Protocols) if ratified.  Because of 
that latter point, making this a WG item seems more appropriate than pushing it 
through as an AD-sponsored document.

To that end, does the WG feel this work is important and wants to take it up?  
In a nutshell, this document breaks up the original YANG module into three for 
the IPFIX collector and exporter functions, the PSAMP functions, and the 
templates for bulk data exports.  While it preserves the SCTP support, SCTP is 
no longer mandatory.  It also adds support for ietf-interfaces and hardware 
management (those did not exist at the time of 6728).

The reason for the three-week call is to give people enough time to read 
through and digest this document.  Please reply with support (or objections) as 
well as comments by May 10, 2020.

Thanks.
Joe
_______________________________________________
OPSAWG mailing list
[email protected]<mailto:[email protected]>
https://www.ietf.org/mailman/listinfo/opsawg
_______________________________________________
OPSAWG mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/opsawg

Reply via email to