Re: [IPFIX] Fwd: New Version Notification for draft-claise-ipfix-information-model-rfc5102bis-00.txt

Concerning these elements:

3.1.17. dateTimeMicroseconds

The type "dateTimeMicroseconds" represents a time value in units of
microseconds based on coordinated universal time (UTC). The choice
of an epoch, for example, 00:00 UTC, January 1, 1970, is left to
corresponding encoding specifications for this type, for example, the
IPFIX protocol specification. Leap seconds are excluded. Note that
transformation of values might be required between different
encodings if different epoch values are used.

3.1.18. dateTimeNanoseconds

The type "dateTimeNanoseconds" represents a time value in units of
nanoseconds based on coordinated universal time (UTC). The choice of
an epoch, for example, 00:00 UTC, January 1, 1970, is left to
corresponding encoding specifications for this type, for example, the
IPFIX protocol specification. Leap seconds are excluded. Note that
transformation of values might be required between different
encodings if different epoch values are used.

I recently added support for these fields in the Lancope
collector, and the format I assumed was NTP. Now I read
here that these can come down in epoch time. Is there
anything in the IPFIX protocol that denotes the format
being used or the epoch time being used in these time
values? I see also that the same Note exists at the end of each defined time element. Perhaps this could be solved with an options template.

Thanks,

Danny Llewallyn

Lancope Inc.

-----Original Message-----

From: Benoit Claise

Sent: Oct 10, 2011 7:52 AM

To: "[email protected]"

Subject: [IPFIX] Fwd: New Version Notification for draft-claise-ipfix-information-model-rfc5102bis-00.txt

Dear all,

Here is new draft, for our new charter proposal:
http://tools.ietf.org/html/draft-claise-ipfix-information-model-rfc5102bis-00

The diffs with RFC5102 are at
http://tools.ietf.org/rfcdiff?url2=draft-claise-ipfix-information-model-rfc5102bis-00.txt

Your feedback is welcome.

Regards, Benoit.

-------- Original Message --------

Subject:
New Version Notification for
draft-claise-ipfix-information-model-rfc5102bis-00.txt

Date:
Mon, 10 Oct 2011 03:00:52 -0700

From:
[email protected]

To:
[email protected]

CC:
[email protected] , [email protected] , [email protected] ,
[email protected] , [email protected]

A new version of I-D, draft-claise-ipfix-information-model-rfc5102bis-00.txt has been successfully submitted by Benoit Claise and posted to the IETF repository.

Filename: draft-claise-ipfix-information-model-rfc5102bis
Revision: 00
Title: Information Model for IP Flow Information eXport (IPFIX)
Creation date: 2011-10-10
WG ID: Individual Submission
Number of pages: 172

Abstract:
This memo defines an information model for the IP Flow Information
eXport (IPFIX) protocol. It is used by the IPFIX protocol for encoding
measured traffic information and information related to the traffic
Observation Point, the traffic Metering Process, and the Exporting
Process. Although developed for the IPFIX protocol, the model is
defined in an open way that easily allows using it in other protocols,
interfaces, and applications. This document obsoletes RFC 5102.

The IETF Secretariat

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