Hi all, I support progression of this draft as it addresses current needs for IPFIX applications within Access Networks. The modular way this draft constructs the configuration models will aid to the longevity of the IPFIX protocol as additional use cases are identified.
As a co-author of the draft, I would also like to address some previous comments raised. I acknowledge the draft is long, but the content is necessary. In order to address the shortcomings of the existing RFC 6728 data model in the context of these new applications (see section 1.1 of the draft), the data model was rewritten and restructured. As such, the authors felt it was necessary to obsolete RFC 6728 so that there was no confusion over the existence of the two data model approaches. This meant that most of the content from RFC 6728 was carried over with some necessary changes needed to a) align with the new data models and b) modify how functional descriptions are tied to the data model to conform to the latest RFCs which define YANG data models, e.g. use of tree diagrams instead of class diagrams. As other author noted, splitting the document into smaller parts doesn't really change the amount of text that must be reviewed and actually increases it as some portions will need to be repeated. This opens the door to introduce inconsistencies. As such, I would not be in favor of splitting the draft. I look forward to working with everyone to progress this draft forward. Best regards, Joey
_______________________________________________ OPSAWG mailing list [email protected] https://www.ietf.org/mailman/listinfo/opsawg
