8 Sep 2010 09:16
Re: [IPFIX] Unit of flowActiveTimeout
Gerhard Muenz <muenz <at> net.in.tum.de>
2010-09-08 07:16:07 GMT
2010-09-08 07:16:07 GMT
Dear Shingo, The IE ID is <128, which indicates that this IE has been adopted from NetFlow.v9. So, "second" seems to be historical. At a moment, active/inactive timeout parameters in IPFIX-CONFIG have unit "milliseconds": http://tools.ietf.org/html/draft-ietf-ipfix-configuration-model-07#page-26 Probably, this should be changed to "seconds" for consistency with the IPFIX-MIB? Regards, Gerhard Shingo KASHIMA wrote: > Dear all, > > I have one question about unit of flowActiveTimeout. > > According to RFC 5102, unit of flowActiveTimeout is second. > Why IPFIX doesn't support a timer with a unit smaller than second, e.g. > millisecond or microsecond ? I want to know a history of discussion. > > ---- > 5.11.1. flowActiveTimeout > > Description: > The number of seconds after which an active Flow is timed out > anyway, even if there is still a continuous flow of packets. > Abstract Data Type: unsigned16 > ElementId: 36 > Status: current > Units: seconds > --- > > On the other hand, IEs about flow timestamps and packet timestamps have > various units e.g. second, millisecond, microsecond and nanosecond. > --- > flowStartSeconds > flowEndSeconds > flowStartMilliseconds > flowEndMilliseconds > flowStartMicroseconds > flowEndMicroseconds > flowStartNanoseconds > flowEndNanoseconds > flowStartDeltaMicroseconds > flowEndDeltaMicroseconds > systemInitTimeMilliseconds > flowStartSysUpTime > flowEndSysUpTime > observationTimeSeconds > observationTimeMilliseconds > observationTimeMicroseconds > observationTimeNanoseconds > --- > > Also PSAMP IEs about time-based sampling parameter support a unit of > microsecond. > --- > samplingTimeInterval > samplingTimeSpace > --- > > Best regards.
_______________________________________________ IPFIX mailing list IPFIX <at> ietf.org https://www.ietf.org/mailman/listinfo/ipfix
RSS Feed