Re: [IPFIX] [Sender: [email protected]] RFC5101: time first flow dropped and time last flow dropped
Benoit Claise <[email protected]>
| Newsgroups | gmane.ietf.ipfix |
|---|---|
| Message-ID | <[email protected]> |
On 20/09/2011 22:32, Paul Aitken wrote: > Benoit, > >> 2. if the IPFIX exporter is configured from [IPFIX-CONF], what should >> be the value in meteringProcessId? >> [IPFIX-CONF] doesn't mention the meteringProcessId, but a cache >> name. > > IPFIX-CONF (or any configurer) wouldn't set the process ID; it's > read-only. > > The configurer would create the process (technically, add the config > which causes the process to be created by the OS), then could be told > (or could discover) what the process ID is. > The cache name could be used to relate the given config to the process > ID. Agreed. > > >> From figure 1 and 2, it seems that there is a one to one matching >> between the cache and the metering process. >> If this is the case, a solution could be to add a meteringProcess >> inside the cache in the figure 12 in [IPFIX-CONF] below > > Do you mean, a "meteringProcessId" (IANA #144) as a read-only property? > > And also an "exportingProcessId" (IANA #145) as a read-only property > in the ExportingProcess? That would solve the issue. Regards, Benoit. > > Those seem useful. > > P. _______________________________________________ IPFIX mailing list [email protected] https://www.ietf.org/mailman/listinfo/ipfix