1. IPFIX Protocol Specifications IPFIX IETF-62 March 12th, <draft-ietf-ipfix-protocol-09.txt>
Benoit Claise
Stewart Bryant
Ganesh Sadasivan
Simon Leinen
Thomas Dietz
Mark Fullmer

2. Closed Issues in version 07
SCTP section improved
The sections "Template Management" and "The Collecting Process's Side" updated according to the default transport protocol
treat UDP as the exception
Inserted an Enterprise Specific Information Element example
Editorial changes
| Enterprise Number 1.1 |
| Field Type 2 | Field Length 2 |

3. Closed Issues in version 08
TCP section inserted
Sequence Number is now: The total number of IPFIX data records … (and not the number of IPFIX Messages anymore)
Editorial changes
| Enterprise Number 1.1 |
| Field Type 2 | Field Length 2 |

4. Closed Issues in version 09
New sections for the protocol format: now contains generic format and separate examples
Improved readability of the examples
New section specifying the data types encoding
Simplified specific Option Templates, removed ipfixOption
Better clarification of the scope
Consistence of Information Element versus field
Editorial changes
| Enterprise Number 1.1 |
| Field Type 2 | Field Length 2 |

5. Changes in version 10 (results of this week meeting, not yet posted)
Improved text regarding the protocol format (some confusion with the terminology)
Remove the flow expiration section; only kept the one in [IPIFX-ARCH]
Editorial Changes
| Enterprise Number 1.1 |
| Field Type 2 | Field Length 2 |

6. Open Issues, with consensus
| | Contents | |
| Set | Template | Record |
| Data Set | / | Data Record(s) |
| Template Set | Template Record(s) | / |
| Options Template | Options Template | / |
| Set | Record(s) | |
| Enterprise Number 1.1 |
| Field Type 2 | Field Length 2 |
Data Record instead of Flow Data Record or Options Data Record

7. Open Issues
Positive only offset for flowStartDeltaUsec, flowEndDeltaUsec (because unsinged32)
=> this implies the IPFIX Message “Export Time” must be a lower value
Note: By default, “Export Time” is the time at which the IPFIX Message leave the exporter. For a Data Set with Flow Records requiring microsecond precision, the IPFIX Message Header "Export Time" field SHOULD be calculated …
dateTimeMicroSeconds base type: "Its encoding is not defined yet.“
Information Elements for the specific option templates must be first defined in [IPFIX-INFO]
Some s on the mailing list
Anything else to discuss here?
| Enterprise Number 1.1 |
| Field Type 2 | Field Length 2 |

8. IPFIX Protocol Specifications IPFIX IETF-62 March 12th, <draft-ietf-ipfix-protocol-08.txt>
Benoit Claise
Stewart Bryant
Ganesh Sadasivan
Mark Fullmer
Simon Leinen
Thomas Dietz