<?xml version="1.0" encoding="UTF-8"?>
<reference anchor="I-D.aitken-ipfix-new-infos" target="https://datatracker.ietf.org/doc/html/draft-aitken-ipfix-new-infos-03">
   <front>
      <title>New Information Elements from the IPFIX Information Model</title>
      <author initials="P." surname="Aitken" fullname="Paul Aitken">
         </author>
      <author initials="B." surname="Claise" fullname="Benoît Claise">
         </author>
      <date month="March" day="17" year="2008" />
      <abstract>
	 <t>This document specifies the IPFIX protocol that serves for 
transmitting IP traffic flow information over the network.  In order 

 
 
  Aitken, Claise



Standard Track





  [page 1] 
New Information Elements for the IPFIX Information Model
 March 2008 

to transmit IP traffic flow information from an exporting process to 
an information collecting process, a common representation of flow 
data and a standard means of communicating them is required. This 
document describes how the IPFIX data and templates records are 
carried over a number of transport protocols from an IPFIX exporting 
process to an IPFIX collecting process. 
 
 Conventions used in this document 
  
The key words &quot;MUST&quot;, &quot;MUST NOT&quot;, &quot;REQUIRED&quot;, &quot;SHALL&quot;, &quot;SHALL NOT&quot;, 
&quot;SHOULD&quot;, &quot;SHOULD NOT&quot;, &quot;RECOMMENDED&quot;, &quot;MAY&quot;, and &quot;OPTIONAL&quot; in this 
document are to be interpreted as described in RFC 2119 [RFC2119].
	 </t>
      </abstract>
   </front>
   <seriesInfo name="Internet-Draft" value="draft-aitken-ipfix-new-infos-03" />
   
</reference>
