Re: [IPFIX] RFC5101: time first flow dropped and time last flow dropped

Gerhard,

>>> 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?
>
>       From figure 1 and 2, it seems that there is a one to one matching
>
> I'm not sure about the one-to-one relationship between Metering 
> Process and Cache. On purpose, IPFIX-CONF does not make a statement 
> because it is not an architectural document. A Metering Process may 
> have multiple Caches. But I do not think that a Cache would belong to 
> multiple Metering Process. So, there is only one meteringProcessId 
> which is associated with a Cache.

Can you see anywhere in the IPFIX documents which shows the relationship 
between a Metering Process and cache(s) ?

I don't see "cache" in RFC5101 (IPFIX PROTO) or RFC5470 (IPFIX ARCH).

However, Figures 1 and 2 of IPFIX CONF show a Metering Process with only 
one cache.


>
> We do not have selectorId, exportingProcessId, and meteringProcessId 
> in the configuration data model. If we think about adding 
> meteringProcessId, it may be worth thinking about the other IDs as well.

Definitely.


Thanks,
P.


> I do not see a problem if these are defined as state parameters (e.g. 
> read-only).
>
> selectorId is a bit different because the scope is OD, not IPFIX 
> device. Therefore, the same ID value may appear for different 
> Selectors of the same device.
>
> Gerhard

_______________________________________________
IPFIX mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/ipfix