Re: [IPFIX] template lifetime
Paul Aitken <[email protected]>
| Newsgroups | gmane.ietf.ipfix |
|---|---|
| Message-ID | <[email protected]> |
Benoit,
>> How does a collector determine the correct lifetime to associate with
>> each Template, and how does it know "the Template refresh timeout
>> configured on the Exporting Process." ?
> Solution 1. Out of band configuration with
> http://tools.ietf.org/html/draft-ietf-ipfix-configuration-model-10.
> Note: I still envision that IPFIX caches might be configured for a
> short period of time on IPFIX exporters, for troubleshooting reasons.
This is not mentioned anywhere in IPFIX. It's a hole.
> Solution 2. CP observes 10 (or 20, or whatever number) template
> refresh and conclude the right value
Packet loss and network jitter make this problematic.
> Solution 3: the CP doesn't bother and take a very high value
That seems reasonable. Why not specify this as the default behaviour?
>>
>> What are the default and acceptable range of lifetime values?
>>
>> Should we have a mechanism which allows an Exporting Process to
>> report Template lifetimes to the Collecting Process?
>> eg, by exporting an option of { scope = templateId, lifetime =
>> lifeTimeUnits }, where lifeTimeUnits = u32 milliseconds - which
>> allows 1ms to 49.7 days, with 0 = infinite?
> This is solution 4.
Then it needs to be written in the protocol so EPs export it and CPs
expect and action it correctly.
P.
_______________________________________________
IPFIX mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/ipfix