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

Hi Benoit,

Getting back to this issue:

On 20.09.2011 16:19, Benoit Claise wrote:
> Thirdly, the section 4.2 doesn't take into account a metering process 
> id. Indeed, what if we have multiple caches on the exporter?

Having another look at RFC5101, I see that this situation is already 
covered in RFC5101!
See the following paragraph which appears in sections 4.1 and 4.2:

    Note that if several Metering Processes are available on the Exporter
    Observation Domain, the Information Element meteringProcessId MUST be
    specified as an additional Scope Field.


If you now want to make meteringProcessId mandatory, you need to remove 
these paragraphs at least.

Gerhard

>
> Here is a proposal for 4.2 and 4.3. The underlined parts are new
>
>
>       4.2. The Metering Process Reliability Statistics Option Template
>
>
>
>     The Metering Process Reliability Option Template specifies the
>     structure of a Data Record for reporting lack of reliability in the
>     Metering Process.  It SHOULD contain the following Information
>     Elements that are defined in [RFC5102  <http://tools.ietf.org/html/rfc5102>]:
>
>     observationDomainId
>                             An identifier of an Observation Domain that
>                             is locally unique to the Exporting Process.
>                             This Information Element MUST be defined as a
>                             Scope Field.
>
>
> _    meteringProcessId (*)
>                             The identifier of the Metering Process for
>                             which lack of reliability is reported.  There
>                             This Information Element MUST be defined as a
>                             Scope Field._
>
>     ignoredPacketTotalCount
>                             The total number of IP packets that the
>                             Metering Process did not process.
>
>     ignoredOctetTotalCount
>                             The total number of octets in observed IP
>                             packets that the Metering Process did not
>                             process.
>
>     time first_packet_ignored
>                             The timestamp of the first IP packet that was
>                             ignored by the Metering Process.  For this
>                             timestamp, any of the "flowStart" timestamp
>                             Information Elements flowStartMilliseconds,
>                             flowStartMicroseconds, flowStartNanoseconds,
>                             and flowStartDeltaMicroseconds can be used.
>
>     time last_packet_ignored
>                             The timestamp of the last IP packet that was
>                             ignored by the Metering Process.  For this
>                             timestamp, any of the "flowEnd" timestamp
>                             Information Elements flowEndMilliseconds,
>                             flowEndMicroseconds, flowEndNanoseconds, and
>                             flowEndDeltaMicroseconds can be used.
>
>

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