2 Jan 2011 21:01
Re: [IPFIX] review of YANG module ietf-ipfix-psamp <at> 2010-10-25
Gerhard Muenz <muenz <at> net.in.tum.de>
2011-01-02 20:01:53 GMT
2011-01-02 20:01:53 GMT
Hi Lada, >>> My main concern is the size of the module. I believe that splitting the >>> data model into smaller coherent modules makes it more understandable >>> and manageable - also in terms of the standardisation process. It >>> seems that the present module could relatively easily be divided into >>> two modules, one describing the collector subsystem and the other >>> dealing with the remaining functionality. As a matter of fact, flow >>> collectors are in most cases implemented in a separate device, so >>> their configuration won't be mixed with configurations of the other >>> parts. This change would also remove one level of containment in the >>> schema, at a very reasonable price of adding one more namespace. >> >> With the upcoming IPFIX mediators, we will have devices implementing >> Collecting Processes, Intermediate Processes, and Exporting Processes. >> Therefore, I think that keeping the configuration data of all IPFIX >> processes in one module makes sense. > > All functions could be combined anyway, even if they are defined in > different modules, by advertising all modules that apply in the hello > message rather than having just one module and using various > combinations of features. By way of analogy, entire router configuration > could also be specified in one module and various routing protocols > selected by means of features - I just don't think this is the right > approach. There are groupings which are used in Exporter and Collector configurations (e.g. TransportSession, TransportLayerSecurity).(Continue reading)
RSS Feed