2007-05-10 2026-04-02 has obsoleted . However, references to remain as part of the historical record. Expert Review IE Doctors (Andrew Feren, Brian Trammell, Nevil Brownlee, Paul Aitken) Values 0-127: NFv9-compatible The columns previously titled "References" and "Requester" have been renamed "Additional Information" and "Reference", respectively. The initial values for this registry were provided in . has obsoleted and specifies that the current registry is the normative reference for these Information Elements. Reserved 0 2013-02-18 octetDeltaCount unsigned64 flowCounter deltaCounter 1 data current The number of octets since the previous report (if any) in incoming packets for this Flow at the Observation Point. The number of octets includes IP header(s) and IP payload. octets 0 2013-02-18 packetDeltaCount unsigned64 flowCounter deltaCounter 2 data current The number of incoming packets since the previous report (if any) for this Flow at the Observation Point. packets 0 2013-02-18 deltaFlowCount unsigned64 deltaCounter 3 current The conservative count of Original Flows contributing to this Aggregated Flow; may be distributed via any of the methods expressed by the valueDistributionMethod Information Element. flows 1 2013-06-25 protocolIdentifier unsigned8 ipHeader identifier 4 all current The value of the protocol number in the IP packet header. The protocol number identifies the IP packet payload type. Protocol numbers are defined in the IANA Protocol Numbers registry. In Internet Protocol version 4 (IPv4), this is carried in the Protocol field. In Internet Protocol version 6 (IPv6), this is carried in the Next Header field in the last extension header of the packet. See for the specification of the IPv4 protocol field. See for the specification of the IPv6 protocol field. See the list of protocol numbers assigned by IANA at . 0 2013-02-18 ipClassOfService unsigned8 ipHeader identifier 5 all current For IPv4 packets, this is the value of the TOS field in the IPv4 packet header. For IPv6 packets, this is the value of the Traffic Class field in the IPv6 packet header. See (Section 5.3.2) and for the definition of the IPv4 TOS field. See for the definition of the IPv6 Traffic Class field. 0 2013-02-18 tcpControlBits unsigned16 flags 6 current TCP control bits observed for the packets of this Flow. This information is encoded as a bit field; each TCP control bit has a corresponding bit in that field. A bit is set to 1 if any observed packet of this Flow has the corresponding TCP control bit set to 1. The bit is cleared to 0 otherwise. Per , the assignment of TCP control bits is managed by IANA via the "TCP Header Flags" registry . Implementers can retrieve the current TCP control bits from that registry, which is authoritative for them. As the most significant 4 bits of octets 12 and 13 (counting from zero) of the TCP header are used to encode the TCP data offset (header length), the corresponding bits in this Information Element MUST be reported by the Exporter with a value of zero and MUST be ignored by the Collector. Use the tcpHeaderLength Information Element to encode this value. All TCP control bits (including those unassigned) MUST be exported as observed in the TCP headers of the packets of this Flow. If exported as a single octet with reduced-size encoding (Section 6.2 of ), this Information Element covers the low-order octet of this field (i.e., bit offset positions 8 to 15) . A Collector receiving this Information Element with reduced-size encoding must not assume anything about the content of the four bits with bit offset positions 4 to 7. Exporting Processes exporting this Information Element on behalf of a Metering Process that is not capable of observing any of the flags with bit offset positions 4 to 7 SHOULD use reduced-size encoding, and only export the least significant 8 bits of this Information Element. Note that previous revisions of this Information Element's definition specified that flags with bit offset positions 8 and 9 must be exported as zero, even if observed. Collectors should therefore not assume that a value of zero for these bits in this Information Element indicates the bits were never set in the observed traffic, especially if these bits are zero in every Flow Record sent by a given Exporter. Note also that the "TCP Header Flags" registry indexes the bit offset from the most significant bit of octet 12 to the least significant bit of octet 13 in the TCP header, but the tcpControlBits is encoded as a regular unsigned 16-bit integer. See the assigned TCP control bits in the "TCP Header Flags" registry . 2 2024-01-29 sourceTransportPort unsigned16 transportHeader identifier 7 all current The source port identifier in the transport protocol header. For transport protocols such as UDP, TCP, SCTP, and DCCP, this is the source port number given in the respective header. This field MAY also be used for future transport protocols that have 16-bit source port identifiers. See for the definition of the UDP source port field. See for the definition of the TCP source port field. See for the definition of the SCTP source port number field. See for the definition of the DCCP source port field. See the assigned transport protocol (e.g., UDP, TCP, SCTP, and DCCP) port numbers . 0 2013-02-18 sourceIPv4Address ipv4Address ipHeader default 8 all current The IPv4 source address in the IP packet header. See for the definition of the IPv4 source address field. 1 2014-02-03 sourceIPv4PrefixLength unsigned8 ipHeader 9 option current The number of contiguous bits that are relevant in the sourceIPv4Prefix Information Element. bits 0-32 0 2013-02-18 ingressInterface unsigned32 scope identifier 10 all current The index of the IP interface where packets of this Flow are being received. The value matches the value of managed object 'ifIndex' as defined in . Note that ifIndex values are not assigned statically to an interface and that the interfaces may be renumbered every time the device's management system is re-initialized, as specified in . See for the definition of the ifIndex object. 0 2013-02-18 destinationTransportPort unsigned16 transportHeader identifier 11 all current The destination port identifier in the transport protocol header. For transport protocols such as UDP, TCP, SCTP, and DCCP, this is the destination port number given in the respective header. This field MAY also be used for future transport protocols that have 16-bit destination port identifiers. See for the definition of the UDP destination port field. See for the definition of the TCP destination port field. See for the definition of the SCTP destination port number field. See for the definition of the DCCP destination port field. See the assigned transport protocol (e.g., UDP, TCP, SCTP, and DCCP) port numbers . 0 2013-02-18 destinationIPv4Address ipv4Address ipHeader default 12 all current The IPv4 destination address in the IP packet header. See for the definition of the IPv4 destination address field. 1 2014-02-03 destinationIPv4PrefixLength unsigned8 ipHeader 13 option current The number of contiguous bits that are relevant in the destinationIPv4Prefix Information Element. bits 0-32 0 2013-02-18 egressInterface unsigned32 scope identifier 14 all current The index of the IP interface where packets of this Flow are being sent. The value matches the value of managed object 'ifIndex' as defined in . Note that ifIndex values are not assigned statically to an interface and that the interfaces may be renumbered every time the device's management system is re-initialized, as specified in . See for the definition of the ifIndex object. 0 2013-02-18 ipNextHopIPv4Address ipv4Address derived default 15 data current The IPv4 address of the next IPv4 hop. 1 2014-02-03 bgpSourceAsNumber unsigned32 derived identifier 16 all current The autonomous system (AS) number of the source IP address. If AS path information for this Flow is only available as an unordered AS set (and not as an ordered AS sequence), then the value of this Information Element is 0. See for a description of BGP-4, and see for the definition of the AS number. 0 2013-02-18 bgpDestinationAsNumber unsigned32 derived identifier 17 all current The autonomous system (AS) number of the destination IP address. If AS path information for this Flow is only available as an unordered AS set (and not as an ordered AS sequence), then the value of this Information Element is 0. See for a description of BGP-4, and see for the definition of the AS number. 0 2013-02-18 bgpNextHopIPv4Address ipv4Address derived default 18 all current The IPv4 address of the next (adjacent) BGP hop. See for a description of BGP-4. 1 2014-02-03 postMCastPacketDeltaCount unsigned64 flowCounter deltaCounter 19 data current The number of outgoing multicast packets since the previous report (if any) sent for packets of this Flow by a multicast daemon within the Observation Domain. This property cannot necessarily be observed at the Observation Point, but may be retrieved by other means. packets 0 2013-02-18 postMCastOctetDeltaCount unsigned64 flowCounter deltaCounter 20 data current The number of octets since the previous report (if any) in outgoing multicast packets sent for packets of this Flow by a multicast daemon within the Observation Domain. This property cannot necessarily be observed at the Observation Point, but may be retrieved by other means. The number of octets includes IP header(s) and IP payload. octets 0 2013-02-18 flowEndSysUpTime unsigned32 timestamp 21 data current The relative timestamp of the last packet of this Flow. It indicates the number of milliseconds since the last (re-)initialization of the IPFIX Device (sysUpTime). sysUpTime can be calculated from systemInitTimeMilliseconds. milliseconds 1 2014-01-11 flowStartSysUpTime unsigned32 timestamp 22 data current The relative timestamp of the first packet of this Flow. It indicates the number of milliseconds since the last (re-)initialization of the IPFIX Device (sysUpTime). sysUpTime can be calculated from systemInitTimeMilliseconds. milliseconds 1 2014-01-11 postOctetDeltaCount unsigned64 flowCounter deltaCounter 23 data current The definition of this Information Element is identical to the definition of Information Element 'octetDeltaCount', except that it reports a potentially modified value caused by a middlebox function after the packet passed the Observation Point. octets 0 2013-02-18 postPacketDeltaCount unsigned64 flowCounter deltaCounter 24 data current The definition of this Information Element is identical to the definition of Information Element 'packetDeltaCount', except that it reports a potentially modified value caused by a middlebox function after the packet passed the Observation Point. packets 0 2013-02-18 minimumIpTotalLength unsigned64 minMax 25 all current Length of the smallest packet observed for this Flow. The packet length includes the IP header(s) length and the IP payload length. octets See for the specification of the IPv4 total length. See for the specification of the IPv6 payload length. See for the specification of the IPv6 jumbo payload length. 0 2013-02-18 maximumIpTotalLength unsigned64 minMax 26 all current Length of the largest packet observed for this Flow. The packet length includes the IP header(s) length and the IP payload length. octets See for the specification of the IPv4 total length. See for the specification of the IPv6 payload length. See for the specification of the IPv6 jumbo payload length. 0 2013-02-18 sourceIPv6Address ipv6Address ipHeader default 27 all current The IPv6 source address in the IP packet header. See for the definition of the Source Address field in the IPv6 header. 1 2014-02-03 destinationIPv6Address ipv6Address ipHeader default 28 all current The IPv6 destination address in the IP packet header. See for the definition of the Destination Address field in the IPv6 header. 1 2014-02-03 sourceIPv6PrefixLength unsigned8 ipHeader 29 option current The number of contiguous bits that are relevant in the sourceIPv6Prefix Information Element. bits 0-128 0 2013-02-18 destinationIPv6PrefixLength unsigned8 ipHeader 30 option current The number of contiguous bits that are relevant in the destinationIPv6Prefix Information Element. bits 0-128 0 2013-02-18 flowLabelIPv6 unsigned32 ipHeader identifier 31 all current The value of the IPv6 Flow Label field in the IP packet header. 0-0xFFFFF See for the definition of the Flow Label field in the IPv6 packet header. 1 2014-08-13 icmpTypeCodeIPv4 unsigned16 transportHeader identifier 32 all current Type and Code of the IPv4 ICMP message. The combination of both values is reported as (ICMP type * 256) + ICMP code. See the "ICMP Type Numbers" registry 0 2013-02-18 igmpType unsigned8 transportHeader identifier 33 all current The type field of the IGMP message. See the "IGMP Type Numbers" registry 0 2013-02-18 samplingInterval unsigned32 quantity 34 deprecated Deprecated in favor of 305 samplingPacketInterval. When using sampled NetFlow, the rate at which packets are sampled -- e.g., a value of 100 indicates that one of every 100 packets is sampled. packets 0 2014-04-04 samplingAlgorithm unsigned8 identifier 35 deprecated Deprecated in favor of 304 selectorAlgorithm. The type of algorithm used for sampled NetFlow: 1 - Deterministic Sampling, 2 - Random Sampling. The values are not compatible with the selectorAlgorithm IE, where "Deterministic" has been replaced by "Systematic count-based" (1) or "Systematic time-based" (2), and "Random" is (3). Conversion is required; see Packet Sampling (PSAMP) Parameters. 0 2014-04-04 flowActiveTimeout unsigned16 misc 36 all current The number of seconds after which an active Flow is timed out anyway, even if there is still a continuous flow of packets. seconds 0 2013-02-18 flowIdleTimeout unsigned16 misc 37 all current A Flow is considered to be timed out if no packets belonging to the Flow have been observed for the number of seconds specified by this field. seconds 0 2013-02-18 engineType unsigned8 identifier 38 deprecated Type of flow switching engine in a router/switch: RP = 0, VIP/Line card = 1, PFC/DFC = 2. Reserved for internal use on the Collector. 0 2014-04-04 engineId unsigned8 identifier 39 deprecated Versatile Interface Processor (VIP) or line card slot number of the flow switching engine in a router/switch. Reserved for internal use on the Collector. 0 2014-04-04 exportedOctetTotalCount unsigned64 processCounter totalCounter 40 data current The total number of octets that the Exporting Process has sent since the Exporting Process (re-)initialization to a particular Collecting Process. The value of this Information Element is calculated by summing up the IPFIX Message Header length values of all IPFIX Messages that were successfully sent to the Collecting Process. The reported number excludes octets in the IPFIX Message that carries the counter value. If this Information Element is sent to a particular Collecting Process, then by default it specifies the number of octets sent to this Collecting Process. octets 0 2013-02-18 exportedMessageTotalCount unsigned64 processCounter totalCounter 41 data current The total number of IPFIX Messages that the Exporting Process has sent since the Exporting Process (re-)initialization to a particular Collecting Process. The reported number excludes the IPFIX Message that carries the counter value. If this Information Element is sent to a particular Collecting Process, then by default it specifies the number of IPFIX Messages sent to this Collecting Process. messages 0 2013-02-18 exportedFlowRecordTotalCount unsigned64 processCounter totalCounter 42 data current The total number of Flow Records that the Exporting Process has sent as Data Records since the Exporting Process (re-)initialization to a particular Collecting Process. The reported number excludes Flow Records in the IPFIX Message that carries the counter value. If this Information Element is sent to a particular Collecting Process, then by default it specifies the number of Flow Records sent to this process. flows 0 2013-02-18 ipv4RouterSc ipv4Address default 43 deprecated This is a platform-specific field for the Catalyst 5000/Catalyst 6000 family. It is used to store the address of a router that is being shortcut when performing MultiLayer Switching. CCO-MLS describes MultiLayer Switching. 0 2014-04-04 sourceIPv4Prefix ipv4Address ipHeader default 44 data current IPv4 source address prefix. 0 2013-02-18 destinationIPv4Prefix ipv4Address ipHeader default 45 data current IPv4 destination address prefix. 0 2013-02-18 mplsTopLabelType unsigned8 derived identifier 46 data current This field identifies the control protocol that allocated the top-of-stack label. Values for this field are listed in the MPLS label type registry. See the IPFIX MPLS label type (Value 46) . See for the MPLS label structure. 0 2013-02-18 mplsTopLabelIPv4Address ipv4Address derived default 47 data current The IPv4 address of the system that the MPLS top label will cause this Flow to be forwarded to. See for the association between MPLS labels and IP addresses. 1 2014-02-03 samplerId unsigned8 identifier 48 deprecated Deprecated in favor of 302 selectorId. The unique identifier associated with samplerName. 0 2014-04-04 samplerMode unsigned8 identifier 49 deprecated Deprecated in favor of 304 selectorAlgorithm. The values are not compatible: selectorAlgorithm=3 is random sampling. The type of algorithm used for sampling data: 1 - Deterministic, 2 - Random Sampling. Use with samplerRandomInterval. 0 2014-04-04 samplerRandomInterval unsigned32 quantity 50 deprecated Deprecated in favor of 305 samplingPacketInterval. Packet interval at which to sample -- in case of random sampling. Used in connection with the samplerMode 0x02 (random sampling) value. 0 2014-04-04 classId unsigned8 identifier 51 deprecated Deprecated in favor of 302 selectorId. Characterizes the traffic class, i.e., QoS treatment. 0 2014-04-04 minimumTTL unsigned8 minMax 52 data current Minimum TTL value observed for any packet in this Flow. hops See for the definition of the IPv4 Time to Live field. See for the definition of the IPv6 Hop Limit field. 0 2013-02-18 maximumTTL unsigned8 minMax 53 data current Maximum TTL value observed for any packet in this Flow. hops See for the definition of the IPv4 Time to Live field. See for the definition of the IPv6 Hop Limit field. 0 2013-02-18 fragmentIdentification unsigned32 ipHeader identifier 54 data current The value of the Identification field in the IPv4 packet header or in the IPv6 Fragment header, respectively. The value is 0 for IPv6 if there is no fragment header. See for the definition of the IPv4 Identification field. See for the definition of the Identification field in the IPv6 Fragment header. 0 2013-02-18 postIpClassOfService unsigned8 ipHeader identifier 55 all current The definition of this Information Element is identical to the definition of Information Element 'ipClassOfService', except that it reports a potentially modified value caused by a middlebox function after the packet passed the Observation Point. See for the definition of the IPv4 TOS field. See for the definition of the IPv6 Traffic Class field. See for the definition of middleboxes. 0 2013-02-18 sourceMacAddress macAddress subIpHeader default 56 data current The IEEE 802 source MAC address field. See IEEE.802-3.2002. 1 2014-02-03 postDestinationMacAddress macAddress subIpHeader default 57 data current The definition of this Information Element is identical to the definition of Information Element 'destinationMacAddress', except that it reports a potentially modified value caused by a middlebox function after the packet passed the Observation Point. See IEEE.802-3.2002. 1 2014-02-03 vlanId unsigned16 subIpHeader identifier 58 data current Virtual LAN identifier associated with ingress interface. For dot1q vlans, see 243 dot1qVlanId. See IEEE.802-1Q.2003. 0 2013-02-18 postVlanId unsigned16 subIpHeader identifier 59 data current Virtual LAN identifier associated with egress interface. For postdot1q vlans, see 254, postDot1qVlanId. See IEEE.802-1Q.2003. 0 2013-02-18 ipVersion unsigned8 ipHeader identifier 60 all current The IP version field in the IP packet header. See for the definition of the version field in the IPv4 packet header. See for the definition of the version field in the IPv6 packet header. Additional information on defined version numbers can be found at . 0 2013-02-18 flowDirection unsigned8 misc identifier 61 data current The direction of the Flow observed at the Observation Point. There are only two values defined. 0x00: ingress flow 0x01: egress flow 0 2013-02-18 ipNextHopIPv6Address ipv6Address derived default 62 data current The IPv6 address of the next IPv6 hop. 1 2014-02-03 bgpNextHopIPv6Address ipv6Address derived default 63 all current The IPv6 address of the next (adjacent) BGP hop. See for a description of BGP-4. 1 2014-02-03 ipv6ExtensionHeaders unsigned32 minMax flags 64 all deprecated Deprecated in favor of the ipv6ExtensionHeadersFull IE. This Information Element was initially specified in . has obsoleted and specifies that IANA-IPFIX is the normative reference for this Information Element. The diagram provided in is incorrect; see . 0 2013-02-18 Assigned for NetFlow v9 compatibility 65-69 0 2013-02-18 mplsTopLabelStackSection octetArray subIpHeader default 70 all current The Label, Exp, and S fields from the top MPLS label stack entry, i.e., from the last label that was pushed. The size of this Information Element is 3 octets. 0 1 2 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Label | Exp |S| +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ Label: Label Value, 20 bits Exp: Experimental Use, 3 bits S: Bottom of Stack, 1 bit See . 1 2014-02-03 mplsLabelStackSection2 octetArray subIpHeader default 71 all current The Label, Exp, and S fields from the label stack entry that was pushed immediately before the label stack entry that would be reported by mplsTopLabelStackSection. See the definition of mplsTopLabelStackSection for further details. The size of this Information Element is 3 octets. See . 1 2014-02-03 mplsLabelStackSection3 octetArray subIpHeader default 72 all current The Label, Exp, and S fields from the label stack entry that was pushed immediately before the label stack entry that would be reported by mplsLabelStackSection2. See the definition of mplsTopLabelStackSection for further details. The size of this Information Element is 3 octets. See . 1 2014-02-03 mplsLabelStackSection4 octetArray subIpHeader default 73 all current The Label, Exp, and S fields from the label stack entry that was pushed immediately before the label stack entry that would be reported by mplsLabelStackSection3. See the definition of mplsTopLabelStackSection for further details. The size of this Information Element is 3 octets. See . 1 2014-02-03 mplsLabelStackSection5 octetArray subIpHeader default 74 all current The Label, Exp, and S fields from the label stack entry that was pushed immediately before the label stack entry that would be reported by mplsLabelStackSection4. See the definition of mplsTopLabelStackSection for further details. The size of this Information Element is 3 octets. See . 1 2014-02-03 mplsLabelStackSection6 octetArray subIpHeader default 75 all current The Label, Exp, and S fields from the label stack entry that was pushed immediately before the label stack entry that would be reported by mplsLabelStackSection5. See the definition of mplsTopLabelStackSection for further details. The size of this Information Element is 3 octets. See . 1 2014-02-03 mplsLabelStackSection7 octetArray subIpHeader default 76 all current The Label, Exp, and S fields from the label stack entry that was pushed immediately before the label stack entry that would be reported by mplsLabelStackSection6. See the definition of mplsTopLabelStackSection for further details. The size of this Information Element is 3 octets. See . 1 2014-02-03 mplsLabelStackSection8 octetArray subIpHeader default 77 all current The Label, Exp, and S fields from the label stack entry that was pushed immediately before the label stack entry that would be reported by mplsLabelStackSection7. See the definition of mplsTopLabelStackSection for further details. The size of this Information Element is 3 octets. See . 1 2014-02-03 mplsLabelStackSection9 octetArray subIpHeader default 78 all current The Label, Exp, and S fields from the label stack entry that was pushed immediately before the label stack entry that would be reported by mplsLabelStackSection8. See the definition of mplsTopLabelStackSection for further details. The size of this Information Element is 3 octets. See . 1 2014-02-03 mplsLabelStackSection10 octetArray subIpHeader default 79 all current The Label, Exp, and S fields from the label stack entry that was pushed immediately before the label stack entry that would be reported by mplsLabelStackSection9. See the definition of mplsTopLabelStackSection for further details. The size of this Information Element is 3 octets. See . 1 2014-02-03 destinationMacAddress macAddress subIpHeader default 80 data current The IEEE 802 destination MAC address field. See IEEE.802-3.2002. 1 2014-02-03 postSourceMacAddress macAddress subIpHeader default 81 data current The definition of this Information Element is identical to the definition of Information Element 'sourceMacAddress', except that it reports a potentially modified value caused by a middlebox function after the packet passed the Observation Point. See IEEE.802-3.2002. 1 2014-02-03 interfaceName string default 82 current A short name uniquely describing an interface, eg "Eth1/0". See for the definition of the ifName object. 0 2013-02-18 interfaceDescription string default 83 current The description of an interface, eg "FastEthernet 1/0" or "ISP connection". See for the definition of the ifDescr object. 0 2013-02-18 samplerName string 84 deprecated Deprecated in favor of 335 selectorName. Name of the flow sampler. 0 2014-04-04 octetTotalCount unsigned64 flowCounter totalCounter 85 all current The total number of octets in incoming packets for this Flow at the Observation Point since the Metering Process (re-)initialization for this Observation Point. The number of octets includes IP header(s) and IP payload. octets 0 2013-02-18 packetTotalCount unsigned64 flowCounter totalCounter 86 all current The total number of incoming packets for this Flow at the Observation Point since the Metering Process (re-)initialization for this Observation Point. packets 0 2013-02-18 flagsAndSamplerId unsigned32 identifier 87 deprecated Flow flags and the value of the sampler ID (samplerId) combined in one bitmapped field. Reserved for internal use on the Collector. 0 2014-04-04 fragmentOffset unsigned16 ipHeader quantity 88 all current The value of the IP fragment offset field in the IPv4 packet header or the IPv6 Fragment header, respectively. The value is 0 for IPv6 if there is no fragment header. 0-0x1FFF See for the specification of the fragment offset in the IPv4 header. See for the specification of the fragment offset in the IPv6 Fragment header. 1 2014-08-13 forwardingStatus unsigned32 identifier 89 current This Information Element describes the forwarding status of the flow and any attached reasons. IPFIX reduced-size encoding is used as required. A structure is currently associated with the least-significant byte. Future versions may be defined to associate meanings with the remaining bits. The current version of the Information Element should be exported as unsigned8. The layout of the encoding is as follows: MSB - 0 1 2 3 4 5 6 7 - LSB +---+---+---+---+---+---+---+---+ | Status| Reason code or flags | +---+---+---+---+---+---+---+---+ Examples: value : 0x40 = 64 binary: 01000000 decode: 01 -> Forward 000000 -> No further information value : 0x89 = 137 binary: 10001001 decode: 10 -> Drop 001001 -> Bad TTL See "NetFlow Version 9 Flow-Record Format" CCO-NF9FMT. See the "Forwarding Status (Value 89)" registry . 2 2018-02-21 mplsVpnRouteDistinguisher octetArray derived default 90 all current The value of the VPN route distinguisher of a corresponding entry in a VPN routing and forwarding table. Route distinguisher ensures that the same address can be used in several different MPLS VPNs and that it is possible for BGP to carry several completely different routes to that address, one for each VPN. According to , the size of mplsVpnRouteDistinguisher is 8 octets. However, in an octet string with flexible length was chosen for representing a VPN route distinguisher by object MplsL3VpnRouteDistinguisher. This choice was made in order to be open to future changes of the size. This idea was adopted when choosing octetArray as abstract data type for this Information Element. The maximum length of this Information Element is 256 octets. See for the specification of the route distinguisher. See for the specification of the MPLS/BGP Layer 3 Virtual Private Network (VPN) Management Information Base. 1 2014-02-03 mplsTopLabelPrefixLength unsigned8 quantity 91 current The prefix length of the subnet of the mplsTopLabelIPv4Address or mplsTopLabelIPv6Address that the MPLS top label will cause the Flow to be forwarded to. bits 0-128 See for the association between MPLS labels and prefix lengths. 2 2014-08-13 srcTrafficIndex unsigned32 identifier 92 current BGP Policy Accounting Source Traffic Index. BGP policy accounting as described in CCO-BGPPOL. 0 2014-04-04 dstTrafficIndex unsigned32 identifier 93 current BGP Policy Accounting Destination Traffic Index. BGP policy accounting as described in CCO-BGPPOL. 0 2014-04-04 applicationDescription string default 94 current Specifies the description of an application. 1 2014-02-03 applicationId octetArray default 95 current Specifies an Application ID per . See section 4 of for the applicationId Information Element Specification. 1 2014-02-03 applicationName string default 96 current Specifies the name of an application. 0 2013-02-18 Assigned for NetFlow v9 compatibility 97 0 2013-02-18 postIpDiffServCodePoint unsigned8 identifier 98 current The definition of this Information Element is identical to the definition of Information Element 'ipDiffServCodePoint', except that it reports a potentially modified value caused by a middlebox function after the packet passed the Observation Point. 0-63 See for the definition of the Differentiated Services Field. See section 5.3.2 of and for the definition of the IPv4 TOS field. See for the definition of the IPv6 Traffic Class field. See the IPFIX Information Model for the 'ipDiffServCodePoint' specification. 0 2013-02-18 multicastReplicationFactor unsigned32 quantity 99 current The amount of multicast replication that's applied to a traffic stream. See for the specification of reserved IPv4 multicast addresses. See for the specification of reserved IPv6 multicast addresses. 0 2013-02-18 className string 100 deprecated Deprecated in favor of 335 selectorName. Traffic Class Name, associated with the classId Information Element. 0 2014-04-04 classificationEngineId unsigned8 identifier 101 current A unique identifier for the engine that determined the Selector ID. Thus, the Classification Engine ID defines the context for the Selector ID. The Classification Engine can be considered a specific registry for application assignments. Values for this field are listed in the Classification Engine IDs registry. See the "Classification Engine IDs (Value 101)" registry 0 2013-02-18 layer2packetSectionOffset unsigned16 quantity 102 deprecated Deprecated in favor of 409 sectionOffset. Layer 2 packet section offset. Potentially a generic packet section offset. 0 2014-04-04 layer2packetSectionSize unsigned16 quantity 103 deprecated Deprecated in favor of 312 dataLinkFrameSize. Layer 2 packet section size. Potentially a generic packet section size. 0 2014-04-04 layer2packetSectionData octetArray 104 deprecated Deprecated in favor of 315 dataLinkFrameSection. Layer 2 packet section data. 0 2014-04-04 Assigned for NetFlow v9 compatibility 105-127 0 2013-02-18 bgpNextAdjacentAsNumber unsigned32 derived identifier 128 all current The autonomous system (AS) number of the first AS in the AS path to the destination IP address. The path is deduced by looking up the destination IP address of the Flow in the BGP routing information base. If AS path information for this Flow is only available as an unordered AS set (and not as an ordered AS sequence), then the value of this Information Element is 0. See for a description of BGP-4, and see for the definition of the AS number. 0 2013-02-18 bgpPrevAdjacentAsNumber unsigned32 derived identifier 129 all current The autonomous system (AS) number of the last AS in the AS path from the source IP address. The path is deduced by looking up the source IP address of the Flow in the BGP routing information base. If AS path information for this Flow is only available as an unordered AS set (and not as an ordered AS sequence), then the value of this Information Element is 0. In case of BGP asymmetry, the bgpPrevAdjacentAsNumber might not be able to report the correct value. See for a description of BGP-4, and see for the definition of the AS number. 0 2013-02-18 exporterIPv4Address ipv4Address config default 130 all current The IPv4 address used by the Exporting Process. This is used by the Collector to identify the Exporter in cases where the identity of the Exporter may have been obscured by the use of a proxy. 1 2014-02-03 exporterIPv6Address ipv6Address config default 131 all current The IPv6 address used by the Exporting Process. This is used by the Collector to identify the Exporter in cases where the identity of the Exporter may have been obscured by the use of a proxy. 1 2014-02-03 droppedOctetDeltaCount unsigned64 flowCounter deltaCounter 132 data current The number of octets since the previous report (if any) in packets of this Flow dropped by packet treatment. The number of octets includes IP header(s) and IP payload. octets 0 2013-02-18 droppedPacketDeltaCount unsigned64 flowCounter deltaCounter 133 data current The number of packets since the previous report (if any) of this Flow dropped by packet treatment. packets 0 2013-02-18 droppedOctetTotalCount unsigned64 flowCounter totalCounter 134 data current The total number of octets in packets of this Flow dropped by packet treatment since the Metering Process (re-)initialization for this Observation Point. The number of octets includes IP header(s) and IP payload. octets 0 2013-02-18 droppedPacketTotalCount unsigned64 flowCounter totalCounter 135 data current The number of packets of this Flow dropped by packet treatment since the Metering Process (re-)initialization for this Observation Point. packets 0 2013-02-18 flowEndReason unsigned8 misc identifier 136 data current The reason for Flow termination. Values are listed in the flowEndReason registry. See the "flowEndReason (Value 136)" registry . 0 2013-02-18 commonPropertiesId unsigned64 scope identifier 137 option current An identifier of a set of common properties that is unique per Observation Domain and Transport Session. Typically, this Information Element is used to link to information reported in separate Data Records. 0 2013-02-18 observationPointId unsigned64 scope identifier 138 option current An identifier of an Observation Point that is unique per Observation Domain. It is RECOMMENDED that this identifier is also unique per IPFIX Device. Typically, this Information Element is used for limiting the scope of other Information Elements. 1 2013-04-11 icmpTypeCodeIPv6 unsigned16 transportHeader identifier 139 all current Type and Code of the IPv6 ICMP message. The combination of both values is reported as (ICMP type * 256) + ICMP code. See the "ICMPv6 'type' Numbers" and "ICMPv6 'Code' Fields" registries 0 2013-02-18 mplsTopLabelIPv6Address ipv6Address derived default 140 data current The IPv6 address of the system that the MPLS top label will cause this Flow to be forwarded to. See for the association between MPLS labels and IP addresses. 1 2014-02-03 lineCardId unsigned32 scope identifier 141 option current An identifier of a line card that is unique per IPFIX Device hosting an Observation Point. Typically, this Information Element is used for limiting the scope of other Information Elements. 0 2013-02-18 portId unsigned32 scope identifier 142 option current An identifier of a line port that is unique per IPFIX Device hosting an Observation Point. Typically, this Information Element is used for limiting the scope of other Information Elements. 0 2013-02-18 meteringProcessId unsigned32 scope identifier 143 option current An identifier of a Metering Process that is unique per IPFIX Device. Typically, this Information Element is used for limiting the scope of other Information Elements. Note that process identifiers are typically assigned dynamically. The Metering Process may be re-started with a different ID. 0 2013-02-18 exportingProcessId unsigned32 scope identifier 144 option current An identifier of an Exporting Process that is unique per IPFIX Device. Typically, this Information Element is used for limiting the scope of other Information Elements. Note that process identifiers are typically assigned dynamically. The Exporting Process may be re-started with a different ID. 0 2013-02-18 templateId unsigned16 scope identifier 145 option current An identifier of a Template that is locally unique within a combination of a Transport session and an Observation Domain. Template IDs 0-255 are reserved for Template Sets, Options Template Sets, and other reserved Sets yet to be created. Template IDs of Data Sets are numbered from 256 to 65535. Typically, this Information Element is used for limiting the scope of other Information Elements. Note that after a re-start of the Exporting Process Template identifiers may be re-assigned. 0 2013-02-18 wlanChannelId unsigned8 subIpHeader identifier 146 data current The identifier of the 802.11 (Wi-Fi) channel used. See IEEE.802-11.1999. 0 2013-02-18 wlanSSID string subIpHeader default 147 data current The Service Set IDentifier (SSID) identifying an 802.11 (Wi-Fi) network used. According to IEEE.802-11.1999, the SSID is encoded into a string of up to 32 characters. See IEEE.802-11.1999. 0 2013-02-18 flowId unsigned64 scope identifier 148 option current An identifier of a Flow that is unique within an Observation Domain. This Information Element can be used to distinguish between different Flows if Flow Keys such as IP addresses and port numbers are not reported or are reported in separate records. 0 2013-02-18 observationDomainId unsigned32 scope identifier 149 option current An identifier of an Observation Domain that is locally unique to an Exporting Process. The Exporting Process uses the Observation Domain ID to uniquely identify to the Collecting Process the Observation Domain where Flows were metered. It is RECOMMENDED that this identifier is also unique per IPFIX Device. A value of 0 indicates that no specific Observation Domain is identified by this Information Element. Typically, this Information Element is used for limiting the scope of other Information Elements. 0 2013-02-18 flowStartSeconds dateTimeSeconds timestamp default 150 data current The absolute timestamp of the first packet of this Flow. seconds 0 2013-02-18 flowEndSeconds dateTimeSeconds timestamp default 151 data current The absolute timestamp of the last packet of this Flow. seconds 0 2013-02-18 flowStartMilliseconds dateTimeMilliseconds timestamp default 152 data current The absolute timestamp of the first packet of this Flow. milliseconds 0 2013-02-18 flowEndMilliseconds dateTimeMilliseconds timestamp default 153 data current The absolute timestamp of the last packet of this Flow. milliseconds 0 2013-02-18 flowStartMicroseconds dateTimeMicroseconds timestamp default 154 data current The absolute timestamp of the first packet of this Flow. microseconds 0 2013-02-18 flowEndMicroseconds dateTimeMicroseconds timestamp default 155 data current The absolute timestamp of the last packet of this Flow. microseconds 0 2013-02-18 flowStartNanoseconds dateTimeNanoseconds timestamp default 156 data current The absolute timestamp of the first packet of this Flow. nanoseconds 0 2013-02-18 flowEndNanoseconds dateTimeNanoseconds timestamp default 157 data current The absolute timestamp of the last packet of this Flow. nanoseconds 0 2013-02-18 flowStartDeltaMicroseconds unsigned32 timestamp 158 data current This is a relative timestamp only valid within the scope of a single IPFIX Message. It contains the negative time offset of the first observed packet of this Flow relative to the export time specified in the IPFIX Message Header. microseconds See the IPFIX protocol specification for the definition of the IPFIX Message Header. 0 2013-02-18 flowEndDeltaMicroseconds unsigned32 timestamp 159 data current This is a relative timestamp only valid within the scope of a single IPFIX Message. It contains the negative time offset of the last observed packet of this Flow relative to the export time specified in the IPFIX Message Header. microseconds See the IPFIX protocol specification for the definition of the IPFIX Message Header. 0 2013-02-18 systemInitTimeMilliseconds dateTimeMilliseconds timestamp default 160 data current The absolute timestamp of the last (re-)initialization of the IPFIX Device. milliseconds 0 2013-02-18 flowDurationMilliseconds unsigned32 misc 161 data current The difference in time between the first observed packet of this Flow and the last observed packet of this Flow. milliseconds 0 2013-02-18 flowDurationMicroseconds unsigned32 misc 162 data current The difference in time between the first observed packet of this Flow and the last observed packet of this Flow. microseconds 0 2013-02-18 observedFlowTotalCount unsigned64 processCounter totalCounter 163 data current The total number of Flows observed in the Observation Domain since the Metering Process (re-)initialization for this Observation Point. flows 0 2013-02-18 ignoredPacketTotalCount unsigned64 processCounter totalCounter 164 data current The total number of observed IP packets that the Metering Process did not process since the (re-)initialization of the Metering Process. packets 0 2013-02-18 ignoredOctetTotalCount unsigned64 processCounter totalCounter 165 data current The total number of octets in observed IP packets (including the IP header) that the Metering Process did not process since the (re-)initialization of the Metering Process. octets 0 2013-02-18 notSentFlowTotalCount unsigned64 processCounter totalCounter 166 data current The total number of Flow Records that were generated by the Metering Process and dropped by the Metering Process or by the Exporting Process instead of being sent to the Collecting Process. There are several potential reasons for this including resource shortage and special Flow export policies. flows 0 2013-02-18 notSentPacketTotalCount unsigned64 processCounter totalCounter 167 data current The total number of packets in Flow Records that were generated by the Metering Process and dropped by the Metering Process or by the Exporting Process instead of being sent to the Collecting Process. There are several potential reasons for this including resource shortage and special Flow export policies. packets 0 2013-02-18 notSentOctetTotalCount unsigned64 processCounter totalCounter 168 data current The total number of octets in packets in Flow Records that were generated by the Metering Process and dropped by the Metering Process or by the Exporting Process instead of being sent to the Collecting Process. There are several potential reasons for this including resource shortage and special Flow export policies. octets 0 2013-02-18 destinationIPv6Prefix ipv6Address ipHeader default 169 data current IPv6 destination address prefix. 0 2013-02-18 sourceIPv6Prefix ipv6Address ipHeader default 170 data current IPv6 source address prefix. 0 2013-02-18 postOctetTotalCount unsigned64 flowCounter totalCounter 171 all current The definition of this Information Element is identical to the definition of Information Element 'octetTotalCount', except that it reports a potentially modified value caused by a middlebox function after the packet passed the Observation Point. octets 0 2013-02-18 postPacketTotalCount unsigned64 flowCounter totalCounter 172 all current The definition of this Information Element is identical to the definition of Information Element 'packetTotalCount', except that it reports a potentially modified value caused by a middlebox function after the packet passed the Observation Point. packets 0 2013-02-18 flowKeyIndicator unsigned64 config flags 173 all current This set of bit fields is used for marking the Information Elements of a Data Record that serve as Flow Key. Each bit represents an Information Element in the Data Record, with the n-th least significant bit representing the n-th Information Element. A bit set to value 1 indicates that the corresponding Information Element is a Flow Key of the reported Flow. A bit set to value 0 indicates that this is not the case. If the Data Record contains more than 64 Information Elements, the corresponding Template SHOULD be designed such that all Flow Keys are among the first 64 Information Elements, because the flowKeyIndicator only contains 64 bits. If the Data Record contains less than 64 Information Elements, then the bits in the flowKeyIndicator for which no corresponding Information Element exists MUST have the value 0. 1 2017-08-01 postMCastPacketTotalCount unsigned64 flowCounter totalCounter 174 data current The total number of outgoing multicast packets sent for packets of this Flow by a multicast daemon within the Observation Domain since the Metering Process (re-)initialization. This property cannot necessarily be observed at the Observation Point, but may be retrieved by other means. packets 0 2013-02-18 postMCastOctetTotalCount unsigned64 flowCounter totalCounter 175 data current The total number of octets in outgoing multicast packets sent for packets of this Flow by a multicast daemon in the Observation Domain since the Metering Process (re-)initialization. This property cannot necessarily be observed at the Observation Point, but may be retrieved by other means. The number of octets includes IP header(s) and IP payload. octets 0 2013-02-18 icmpTypeIPv4 unsigned8 transportHeader identifier 176 all current Type of the IPv4 ICMP message. See the "ICMP Type Numbers" registry 0 2013-02-18 icmpCodeIPv4 unsigned8 transportHeader identifier 177 all current Code of the IPv4 ICMP message. See the "ICMP Type Numbers" registry 0 2013-02-18 icmpTypeIPv6 unsigned8 transportHeader identifier 178 all current Type of the IPv6 ICMP message. See the "ICMPv6 'type' Numbers" registry 0 2013-02-18 icmpCodeIPv6 unsigned8 transportHeader identifier 179 all current Code of the IPv6 ICMP message. See the "ICMPv6 'Code' Fields" registry 0 2013-02-18 udpSourcePort unsigned16 transportHeader identifier 180 all current The source port identifier in the UDP header. See for the definition of the UDP source port field. Additional information on defined UDP port numbers can be found at . 0 2013-02-18 udpDestinationPort unsigned16 transportHeader identifier 181 all current The destination port identifier in the UDP header. See for the definition of the UDP destination port field. Additional information on defined UDP port numbers can be found at . 0 2013-02-18 tcpSourcePort unsigned16 transportHeader identifier 182 all current The source port identifier in the TCP header. See for the definition of the TCP source port field. Additional information on defined TCP port numbers can be found at . 0 2013-02-18 tcpDestinationPort unsigned16 transportHeader identifier 183 all current The destination port identifier in the TCP header. See for the definition of the TCP destination port field. Additional information on defined TCP port numbers can be found at . 0 2013-02-18 tcpSequenceNumber unsigned32 transportHeader 184 all current The sequence number in the TCP header. See for the definition of the TCP sequence number. 0 2013-02-18 tcpAcknowledgementNumber unsigned32 transportHeader 185 all current The acknowledgement number in the TCP header. See for the definition of the TCP acknowledgement number. 0 2013-02-18 tcpWindowSize unsigned16 transportHeader 186 all current The window field in the TCP header. If the TCP window scale is supported, then TCP window scale must be known to fully interpret the value of this information. See for the definition of the TCP window field. See for the definition of the TCP window scale. 0 2013-02-18 tcpUrgentPointer unsigned16 transportHeader 187 all current The urgent pointer in the TCP header. See for the definition of the TCP urgent pointer. 0 2013-02-18 tcpHeaderLength unsigned8 transportHeader 188 all current The length of the TCP header. Note that the value of this Information Element is different from the value of the Data Offset field in the TCP header. The Data Offset field indicates the length of the TCP header in units of 4 octets. This Information Elements specifies the length of the TCP header in units of octets. octets See for the definition of the TCP header. 0 2013-02-18 ipHeaderLength unsigned8 ipHeader 189 all current The length of the IP header. For IPv6, the value of this Information Element is 40. octets See for the definition of the IPv4 header. See for the definition of the IPv6 header. 0 2013-02-18 totalLengthIPv4 unsigned16 ipHeader 190 all current The total length of the IPv4 packet. octets See for the specification of the IPv4 total length. 0 2013-02-18 payloadLengthIPv6 unsigned16 ipHeader 191 all current This Information Element reports the value of the Payload Length field in the IPv6 header. Note that IPv6 extension headers belong to the payload. Also note that in case of a jumbo payload option the value of the Payload Length field in the IPv6 header is zero and so will be the value reported by this Information Element. octets See for the specification of the IPv6 payload length. See for the specification of the IPv6 jumbo payload option. 0 2013-02-18 ipTTL unsigned8 ipHeader 192 all current For IPv4, the value of the Information Element matches the value of the Time to Live (TTL) field in the IPv4 packet header. For IPv6, the value of the Information Element matches the value of the Hop Limit field in the IPv6 packet header. hops See for the definition of the IPv4 Time to Live field. See for the definition of the IPv6 Hop Limit field. 0 2013-02-18 nextHeaderIPv6 unsigned8 ipHeader 193 all current The value of the Next Header field of the IPv6 header. The value identifies the type of the following IPv6 extension header or of the following IP payload. Valid values are defined in the IANA Protocol Numbers registry. See for the definition of the IPv6 Next Header field. See the list of protocol numbers assigned by IANA at . 0 2013-02-18 mplsPayloadLength unsigned32 subIpHeader 194 all current The size of the MPLS packet without the label stack. octets See for the specification of MPLS packets. See for the specification of the MPLS label stack. 0 2013-02-18 ipDiffServCodePoint unsigned8 ipHeader identifier 195 all current The value of a Differentiated Services Code Point (DSCP) encoded in the Differentiated Services field. The Differentiated Services field spans the most significant 6 bits of the IPv4 TOS field or the IPv6 Traffic Class field, respectively. This Information Element encodes only the 6 bits of the Differentiated Services field. Therefore, its value may range from 0 to 63. 0-63 See for the definition of the Differentiated Services field. See (Section 5.3.2) and for the definition of the IPv4 TOS field. See for the definition of the IPv6 Traffic Class field. 0 2013-02-18 ipPrecedence unsigned8 ipHeader identifier 196 all current The value of the IP Precedence. The IP Precedence value is encoded in the first 3 bits of the IPv4 TOS field or the IPv6 Traffic Class field, respectively. This Information Element encodes only these 3 bits. Therefore, its value may range from 0 to 7. 0-7 See (Section 5.3.3) and for the definition of the IP Precedence. See (Section 5.3.2) and for the definition of the IPv4 TOS field. See for the definition of the IPv6 Traffic Class field. 0 2013-02-18 fragmentFlags unsigned8 ipHeader flags 197 all current Fragmentation properties indicated by flags in the IPv4 packet header or the IPv6 Fragment header, respectively. Bit 0: (RS) Reserved. The value of this bit MUST be 0 until specified otherwise. Bit 1: (DF) 0 = May Fragment, 1 = Don't Fragment. Corresponds to the value of the DF flag in the IPv4 header. Will always be 0 for IPv6 unless a "don't fragment" feature is introduced to IPv6. Bit 2: (MF) 0 = Last Fragment, 1 = More Fragments. Corresponds to the MF flag in the IPv4 header or to the M flag in the IPv6 Fragment header, respectively. The value is 0 for IPv6 if there is no fragment header. Bits 3-7: (DC) Don't Care. The values of these bits are irrelevant. 0 1 2 3 4 5 6 7 +---+---+---+---+---+---+---+---+ | R | D | M | D | D | D | D | D | | S | F | F | C | C | C | C | C | +---+---+---+---+---+---+---+---+ See for the specification of the IPv4 fragment flags. See for the specification of the IPv6 Fragment header. 0 2013-02-18 octetDeltaSumOfSquares unsigned64 flowCounter 198 data current The sum of the squared numbers of octets per incoming packet since the previous report (if any) for this Flow at the Observation Point. The number of octets includes IP header(s) and IP payload. 0 2013-02-18 octetTotalSumOfSquares unsigned64 flowCounter 199 all current The total sum of the squared numbers of octets in incoming packets for this Flow at the Observation Point since the Metering Process (re-)initialization for this Observation Point. The number of octets includes IP header(s) and IP payload. octets 0 2013-02-18 mplsTopLabelTTL unsigned8 subIpHeader 200 all current The TTL field from the top MPLS label stack entry, i.e., the last label that was pushed. hops See for the specification of the TTL field. 0 2013-02-18 mplsLabelStackLength unsigned32 subIpHeader 201 all current The length of the MPLS label stack in units of octets. octets See for the specification of the MPLS label stack. 0 2013-02-18 mplsLabelStackDepth unsigned32 subIpHeader 202 all current The number of labels in the MPLS label stack. entries See for the specification of the MPLS label stack. 0 2013-02-18 mplsTopLabelExp unsigned8 subIpHeader flags 203 all current The Exp field from the top MPLS label stack entry, i.e., the last label that was pushed. Bits 0-4: Don't Care, value is irrelevant. Bits 5-7: MPLS Exp field. 0 1 2 3 4 5 6 7 +---+---+---+---+---+---+---+---+ | don't care | Exp | +---+---+---+---+---+---+---+---+ See for the specification of the Exp field. See for usage of the Exp field. 0 2013-02-18 ipPayloadLength unsigned32 derived 204 all current The effective length of the IP payload. For IPv4 packets, the value of this Information Element is the difference between the total length of the IPv4 packet (as reported by Information Element totalLengthIPv4) and the length of the IPv4 header (as reported by Information Element headerLengthIPv4). For IPv6, the value of the Payload Length field in the IPv6 header is reported except in the case that the value of this field is zero and that there is a valid jumbo payload option. In this case, the value of the Jumbo Payload Length field in the jumbo payload option is reported. octets See for the specification of IPv4 packets. See for the specification of the IPv6 payload length. See for the specification of the IPv6 jumbo payload length. 0 2013-02-18 udpMessageLength unsigned16 transportHeader 205 all current The value of the Length field in the UDP header. octets See for the specification of the UDP header. 0 2013-02-18 isMulticast unsigned8 ipHeader flags 206 data current If the IP destination address is not a reserved multicast address, then the value of all bits of the octet (including the reserved ones) is zero. The first bit of this octet is set to 1 if the Version field of the IP header has the value 4 and if the Destination Address field contains a reserved multicast address in the range from 224.0.0.0 to 239.255.255.255. Otherwise, this bit is set to 0. The second and third bits of this octet are reserved for future use. The remaining bits of the octet are only set to values other than zero if the IP Destination Address is a reserved IPv6 multicast address. Then the fourth bit of the octet is set to the value of the T flag in the IPv6 multicast address and the remaining four bits are set to the value of the scope field in the IPv6 multicast address. 0 1 2 3 4 5 6 7 +------+------+------+------+------+------+------+------+ | IPv6 multicast scope | T | RES. | RES. | MCv4 | +------+------+------+------+------+------+------+------+ Bits 0-3: set to value of multicast scope if IPv6 multicast Bit 4: set to value of T flag, if IPv6 multicast Bits 5-6: reserved for future use Bit 7: set to 1 if IPv4 multicast See for the specification of reserved IPv4 multicast addresses. See for the specification of reserved IPv6 multicast addresses and the definition of the T flag and the IPv6 multicast scope. The diagram provided in is incorrect. The diagram in this registry is taken from Errata 1736. See . 0 2013-02-18 ipv4IHL unsigned8 ipHeader 207 all current The value of the Internet Header Length (IHL) field in the IPv4 header. It specifies the length of the header in units of 4 octets. Please note that its unit is different from most of the other Information Elements reporting length values. 4-octet words See for the specification of the IPv4 header. 0 2013-02-18 ipv4Options unsigned32 minMax flags 208 all current IPv4 options in packets of this Flow. The information is encoded in a set of bit fields. For each valid IPv4 option type, there is a bit in this set. The bit is set to 1 if any observed packet of this Flow contains the corresponding IPv4 option type. Otherwise, if no observed packet of this Flow contained the respective IPv4 option type, the value of the corresponding bit is 0. The list of valid IPv4 options is maintained by IANA. Note that for identifying an option not just the 5-bit Option Number, but all 8 bits of the Option Type need to match one of the IPv4 options specified at http://www.iana.org/assignments/ip-parameters. Options are mapped to bits according to their option numbers. Option number X is mapped to bit X. The mapping is illustrated by the figure below. 0 1 2 3 4 5 6 7 +------+------+------+------+------+------+------+------+ ... | RR |CIPSO |E-SEC | TS | LSR | SEC | NOP | EOOL | +------+------+------+------+------+------+------+------+ 8 9 10 11 12 13 14 15 +------+------+------+------+------+------+------+------+ ... |ENCODE| VISA | FINN | MTUR | MTUP | ZSU | SSR | SID | ... +------+------+------+------+------+------+------+------+ 16 17 18 19 20 21 22 23 +------+------+------+------+------+------+------+------+ ... | DPS |NSAPA | SDB |RTRALT|ADDEXT| TR | EIP |IMITD | ... +------+------+------+------+------+------+------+------+ 24 25 26 27 28 29 30 31 +------+------+------+------+------+------+------+------+ ... | | EXP | to be assigned by IANA | QS | UMP | +------+------+------+------+------+------+------+------+ Type Option Bit Value Name Reference ---+-----+-------+------------------------------------ 0 7 RR Record Route, RFC 791 1 134 CIPSO Commercial Security 2 133 E-SEC Extended Security, RFC 1108 3 68 TS Time Stamp, RFC 791 4 131 LSR Loose Source Route, RFC791 5 130 SEC Security, RFC 1108 6 1 NOP No Operation, RFC 791 7 0 EOOL End of Options List, RFC 791 8 15 ENCODE 9 142 VISA Experimental Access Control 10 205 FINN Experimental Flow Control 11 12 MTUR (obsoleted) MTU Reply, RFC 1191 12 11 MTUP (obsoleted) MTU Probe, RFC 1191 13 10 ZSU Experimental Measurement 14 137 SSR Strict Source Route, RFC 791 15 136 SID Stream ID, RFC 791 16 151 DPS Dynamic Packet State 17 150 NSAPA NSAP Address 18 149 SDB Selective Directed Broadcast 19 147 ADDEXT Address Extension 20 148 RTRALT Router Alert, RFC 2113 21 82 TR Traceroute, RFC 3193 22 145 EIP Extended Internet Protocol, RFC 1385 23 144 IMITD IMI Traffic Descriptor 25 30 EXP RFC3692-style Experiment 25 94 EXP RFC3692-style Experiment 25 158 EXP RFC3692-style Experiment 25 222 EXP RFC3692-style Experiment 30 25 QS Quick-Start 31 152 UMP Upstream Multicast Pkt. ... ... ... Further options numbers may be assigned by IANA See for the definition of IPv4 options. See the list of IPv4 option numbers assigned by IANA at . The diagram provided in is incorrect. The diagram in this registry is taken from Errata 1737. See . 0 2013-02-18 tcpOptions unsigned64 minMax flags 209 all deprecated Deprecated in favor of the tcpOptionsFull IE. This Information Element was initially specified in . has obsoleted and specifies that IANA-IPFIX is the normative reference for this Information Element. The diagram provided in is incorrect; see . 0 2013-02-18 paddingOctets octetArray padding default 210 option current The value of this Information Element is always a sequence of 0x00 values. 0 2013-02-18 collectorIPv4Address ipv4Address config default 211 all current An IPv4 address to which the Exporting Process sends Flow information. 1 2014-02-03 collectorIPv6Address ipv6Address config default 212 all current An IPv6 address to which the Exporting Process sends Flow information. 1 2014-02-03 exportInterface unsigned32 config identifier 213 all current The index of the interface from which IPFIX Messages sent by the Exporting Process to a Collector leave the IPFIX Device. The value matches the value of managed object 'ifIndex' as defined in . Note that ifIndex values are not assigned statically to an interface and that the interfaces may be renumbered every time the device's management system is re-initialized, as specified in . See for the definition of the ifIndex object. 0 2013-02-18 exportProtocolVersion unsigned8 config identifier 214 all current The protocol version used by the Exporting Process for sending Flow information. The protocol version is given by the value of the Version Number field in the Message Header. The protocol version is 10 for IPFIX and 9 for NetFlow version 9. A value of 0 indicates that no export protocol is in use. See the IPFIX protocol specification for the definition of the IPFIX Message Header. See for the definition of the NetFlow version 9 message header. 0 2013-02-18 exportTransportProtocol unsigned8 config identifier 215 all current The value of the protocol number used by the Exporting Process for sending Flow information. The protocol number identifies the IP packet payload type. Protocol numbers are defined in the IANA Protocol Numbers registry. In Internet Protocol version 4 (IPv4), this is carried in the Protocol field. In Internet Protocol version 6 (IPv6), this is carried in the Next Header field in the last extension header of the packet. See for the specification of the IPv4 protocol field. See for the specification of the IPv6 protocol field. See the list of protocol numbers assigned by IANA at . 0 2013-02-18 collectorTransportPort unsigned16 config identifier 216 all current The destination port identifier to which the Exporting Process sends Flow information. For transport protocols such as UDP, TCP, and SCTP, this is the destination port number. This field MAY also be used for future transport protocols that have 16-bit source port identifiers. See for the definition of the UDP destination port field. See for the definition of the TCP destination port field. See for the definition of the SCTP destination port number field. See the assigned transport protocol (e.g., UDP, TCP, and SCTP) port numbers . 0 2013-02-18 exporterTransportPort unsigned16 config identifier 217 all current The source port identifier from which the Exporting Process sends Flow information. For transport protocols such as UDP, TCP, and SCTP, this is the source port number. This field MAY also be used for future transport protocols that have 16-bit source port identifiers. See for the definition of the UDP source port field. See for the definition of the TCP source port field. See for the definition of the SCTP source port number field. See the assigned transport protocol (e.g., UDP, TCP, and SCTP) port numbers . 0 2013-02-18 tcpSynTotalCount unsigned64 flowCounter totalCounter 218 data current The total number of packets of this Flow with TCP "Synchronize sequence numbers" (SYN) flag set. packets See for the definition of the TCP SYN flag. 0 2013-02-18 tcpFinTotalCount unsigned64 flowCounter totalCounter 219 data current The total number of packets of this Flow with TCP "No more data from sender" (FIN) flag set. packets See for the definition of the TCP FIN flag. 0 2013-02-18 tcpRstTotalCount unsigned64 flowCounter totalCounter 220 data current The total number of packets of this Flow with TCP "Reset the connection" (RST) flag set. packets See for the definition of the TCP RST flag. 0 2013-02-18 tcpPshTotalCount unsigned64 flowCounter totalCounter 221 data current The total number of packets of this Flow with TCP "Push Function" (PSH) flag set. packets See for the definition of the TCP PSH flag. 0 2013-02-18 tcpAckTotalCount unsigned64 flowCounter totalCounter 222 data current The total number of packets of this Flow with TCP "Acknowledgment field significant" (ACK) flag set. packets See for the definition of the TCP ACK flag. 0 2013-02-18 tcpUrgTotalCount unsigned64 flowCounter totalCounter 223 data current The total number of packets of this Flow with TCP "Urgent Pointer field significant" (URG) flag set. packets See for the definition of the TCP URG flag. 0 2013-02-18 ipTotalLength unsigned64 ipHeader 224 all current The total length of the IP packet. octets See for the specification of the IPv4 total length. See for the specification of the IPv6 payload length. See for the specification of the IPv6 jumbo payload length. 0 2013-02-18 postNATSourceIPv4Address ipv4Address default 225 current The definition of this Information Element is identical to the definition of Information Element 'sourceIPv4Address', except that it reports a modified value caused by a NAT middlebox function after the packet passed the Observation Point. See for the definition of the IPv4 source address field. See for the definition of NAT. See for the definition of middleboxes. 1 2014-02-03 postNATDestinationIPv4Address ipv4Address default 226 current The definition of this Information Element is identical to the definition of Information Element 'destinationIPv4Address', except that it reports a modified value caused by a NAT middlebox function after the packet passed the Observation Point. See for the definition of the IPv4 destination address field. See for the definition of NAT. See for the definition of middleboxes. 1 2014-02-03 postNAPTSourceTransportPort unsigned16 identifier 227 current The definition of this Information Element is identical to the definition of Information Element 'sourceTransportPort', except that it reports a modified value caused by a Network Address Port Translation (NAPT) middlebox function after the packet passed the Observation Point. See for the definition of the UDP source port field. See for the definition of the TCP source port field. See for the definition of SCTP. See for the definition of NAPT. See for the definition of middleboxes. See the assigned transport protocol (e.g., UDP, TCP, SCTP, and DCCP) port numbers . 0 2013-02-18 postNAPTDestinationTransportPort unsigned16 identifier 228 current The definition of this Information Element is identical to the definition of Information Element 'destinationTransportPort', except that it reports a modified value caused by a Network Address Port Translation (NAPT) middlebox function after the packet passed the Observation Point. See for the definition of the UDP source port field. See for the definition of the TCP source port field. See for the definition of SCTP. See for the definition of NAPT. See for the definition of middleboxes. See the assigned transport protocol (e.g., UDP, TCP, SCTP, and DCCP) port numbers . 0 2013-02-18 natOriginatingAddressRealm unsigned8 identifier 229 current Indicates whether the session was created because traffic originated in the private or public address realm. postNATSourceIPv4Address, postNATDestinationIPv4Address, postNAPTSourceTransportPort, and postNAPTDestinationTransportPort are qualified with the address realm in perspective. Values are listed in the natOriginatingAddressRealm registry. 1-2 See the "natOriginatingAddressRealm (Value 229)" registry . See for the definition of NAT. 1 2014-08-13 natEvent unsigned8 identifier 230 current This Information Element identifies a NAT event. This IE identifies the type of a NAT event. Examples of NAT events include, but are not limited to, NAT translation create, NAT translation delete, Threshold Reached, or Threshold Exceeded, etc. Values for this Information Element are listed in the "NAT Event Type" registry. See the "NAT Event Type (Value 230)" registry . See for the definition of NAT. See for the definitions of values 4-16. 2 2017-03-15 initiatorOctets unsigned64 deltaCounter 231 current The total number of layer 4 payload bytes in a flow from the initiator since the previous report. The initiator is the device which triggered the session creation, and remains the same for the life of the session. octets See #298, initiatorPackets. 1 2014-08-13 responderOctets unsigned64 deltaCounter 232 current The total number of layer 4 payload bytes in a flow from the responder since the previous report. The responder is the device which replies to the initiator, and remains the same for the life of the session. octets See #299, responderPackets. 1 2014-08-13 firewallEvent unsigned8 233 current Indicates a firewall event. Allowed values are listed in the firewallEvent registry. See the "firewallEvent (Value 233)" registry . 0 2013-02-18 ingressVRFID unsigned32 234 current An unique identifier of the VRFname where the packets of this flow are being received. This identifier is unique per Metering Process 0 2013-02-18 egressVRFID unsigned32 235 current An unique identifier of the VRFname where the packets of this flow are being sent. This identifier is unique per Metering Process 0 2013-02-18 VRFname string default 236 current The name of a VPN Routing and Forwarding table (VRF). See for the definition of VRF. 0 2013-02-18 postMplsTopLabelExp unsigned8 subIpHeader flags 237 all current The definition of this Information Element is identical to the definition of Information Element 'mplsTopLabelExp', except that it reports a potentially modified value caused by a middlebox function after the packet passed the Observation Point. See for the specification of the Exp field. See for usage of the Exp field. 0 2013-02-18 tcpWindowScale unsigned16 transportHeader 238 all current The scale of the window field in the TCP header. See for the definition of the TCP window scale. 0 2013-02-18 biflowDirection unsigned8 misc identifier 239 all current A description of the direction assignment method used to assign the Biflow Source and Destination. This Information Element MAY be present in a Flow Data Record, or applied to all flows exported from an Exporting Process or Observation Domain using IPFIX Options. If this Information Element is not present in a Flow Record or associated with a Biflow via scope, it is assumed that the configuration of the direction assignment method is done out-of-band. Note that when using IPFIX Options to apply this Information Element to all flows within an Observation Domain or from an Exporting Process, the Option SHOULD be sent reliably. If reliable transport is not available (i.e., when using UDP), this Information Element SHOULD appear in each Flow Record. Values are listed in the biflowDirection registry. See the "biflowDirection (Value 239)" registry . 0 2013-02-18 ethernetHeaderLength unsigned8 quantity 240 current The difference between the length of an Ethernet frame (minus the FCS) and the length of its MAC Client Data section (including any padding) as defined in section 3.1 of [IEEE.802-3.2005]. It does not include the Preamble, SFD and Extension field lengths. octets [IEEE.802-3.2005] 1 2014-08-13 ethernetPayloadLength unsigned16 quantity 241 current The length of the MAC Client Data section (including any padding) of a frame as defined in section 3.1 of [IEEE.802-3.2005]. octets [IEEE.802-3.2005] 1 2014-08-13 ethernetTotalLength unsigned16 quantity 242 current The total length of the Ethernet frame (excluding the Preamble, SFD, Extension and FCS fields) as described in section 3.1 of [IEEE.802-3.2005]. octets [IEEE.802-3.2005] 1 2014-08-13 dot1qVlanId unsigned16 identifier 243 current The value of the 12-bit VLAN Identifier portion of the Tag Control Information field of an Ethernet frame. The structure and semantics within the Tag Control Information field are defined in [IEEE802.1Q]. In Provider Bridged Networks, it represents the Service VLAN identifier in the Service VLAN Tag (S-TAG) Tag Control Information (TCI) field or the Customer VLAN identifier in the Customer VLAN Tag (C-TAG) Tag Control Information (TCI) field as described in [IEEE802.1Q]. In Provider Backbone Bridged Networks, it represents the Backbone VLAN identifier in the Backbone VLAN Tag (B-TAG) Tag Control Information (TCI) field as described in [IEEE802.1Q]. In a virtual link between a host system and EVB bridge, it represents the Service VLAN identifier indicating S-channel as described in [IEEE802.1Qbg]. In the case of a multi-tagged frame, it represents the outer tag's VLAN identifier, except for I-TAG. [IEEE802.1Q][IEEE802.1Qbg] 2 2014-01-11 dot1qPriority unsigned8 identifier 244 current The value of the 3-bit User Priority portion of the Tag Control Information field of an Ethernet frame. The structure and semantics within the Tag Control Information field are defined in [IEEE802.1Q]. In the case of multi-tagged frame, it represents the 3-bit Priority Code Point (PCP) portion of the outer tag's Tag Control Information (TCI) field as described in [IEEE802.1Q], except for I-TAG. [IEEE802.1Q] 1 2014-01-11 dot1qCustomerVlanId unsigned16 identifier 245 current The value represents the Customer VLAN identifier in the Customer VLAN Tag (C-TAG) Tag Control Information (TCI) field as described in [IEEE802.1Q]. [IEEE802.1Q] 1 2014-01-11 dot1qCustomerPriority unsigned8 identifier 246 current The value represents the 3-bit Priority Code Point (PCP) portion of the Customer VLAN Tag (C-TAG) Tag Control Information (TCI) field as described in [IEEE802.1Q]. [IEEE802.1Q] 1 2014-01-11 metroEvcId string default 247 current The EVC Service Attribute which uniquely identifies the Ethernet Virtual Connection (EVC) within a Metro Ethernet Network, as defined in section 6.2 of MEF 10.1. The MetroEVCID is encoded in a string of up to 100 characters. MEF 10.1 (Ethernet Services Attributes Phase 2) MEF16 (Ethernet Local Management Interface) 1 2014-02-03 metroEvcType unsigned8 identifier 248 current The 3-bit EVC Service Attribute which identifies the type of service provided by an EVC. MEF 10.1 (Ethernet Services Attributes Phase 2) MEF16 (Ethernet Local Management Interface) 0 2013-02-18 pseudoWireId unsigned32 identifier 249 current A 32-bit non-zero connection identifier, which together with the pseudoWireType, identifies the Pseudo Wire (PW) as defined in . See for pseudowire definitions. 0 2013-02-18 pseudoWireType unsigned16 identifier 250 current The value of this information element identifies the type of MPLS Pseudo Wire (PW) as defined in . See for the pseudowire type definition, and for the IANA Pseudowire Types registry. 0 2013-02-18 pseudoWireControlWord unsigned32 identifier 251 current The 32-bit Preferred Pseudo Wire (PW) MPLS Control Word as defined in Section 3 of . See for the Pseudo Wire Control Word definition. 0 2013-02-18 ingressPhysicalInterface unsigned32 identifier 252 current The index of a networking device's physical interface (example, a switch port) where packets of this flow are being received. See for the definition of the ifIndex object. 0 2013-02-18 egressPhysicalInterface unsigned32 identifier 253 current The index of a networking device's physical interface (example, a switch port) where packets of this flow are being sent. See for the definition of the ifIndex object. 0 2013-02-18 postDot1qVlanId unsigned16 identifier 254 current The definition of this Information Element is identical to the definition of Information Element 'dot1qVlanId', except that it reports a potentially modified value caused by a middlebox function after the packet passed the Observation Point. [IEEE.802-3.2005] [IEEE.802-1ad.2005] 0 2013-02-18 postDot1qCustomerVlanId unsigned16 identifier 255 current The definition of this Information Element is identical to the definition of Information Element 'dot1qCustomerVlanId', except that it reports a potentially modified value caused by a middlebox function after the packet passed the Observation Point. [IEEE.802-1ad.2005] [IEEE.802-1Q.2003] 0 2013-02-18 ethernetType unsigned16 identifier 256 current The Ethernet type field of an Ethernet frame that identifies the MAC client protocol carried in the payload as defined in paragraph 1.4.349 of [IEEE.802-3.2005]. [IEEE.802-3.2005] Ethertype registry available at 0 2013-02-18 postIpPrecedence unsigned8 identifier 257 current The definition of this Information Element is identical to the definition of Information Element 'ipPrecedence', except that it reports a potentially modified value caused by a middlebox function after the packet passed the Observation Point. 0-7 See (Section 5.3.3) and for the definition of the IP Precedence. See (Section 5.3.2) and for the definition of the IPv4 TOS field. See for the definition of the IPv6 Traffic Class field. 0 2013-02-18 collectionTimeMilliseconds dateTimeMilliseconds default 258 current The absolute timestamp at which the data within the scope containing this Information Element was received by a Collecting Process. This Information Element SHOULD be bound to its containing IPFIX Message via IPFIX Options and the messageScope Information Element. milliseconds 1 2013-03-26 exportSctpStreamId unsigned16 identifier 259 current The value of the SCTP Stream Identifier used by the Exporting Process for exporting IPFIX Message data. This is carried in the Stream Identifier field of the header of the SCTP DATA chunk containing the IPFIX Message(s). 0 2013-02-18 maxExportSeconds dateTimeSeconds default 260 current The absolute Export Time of the latest IPFIX Message within the scope containing this Information Element. This Information Element SHOULD be bound to its containing IPFIX Transport Session via IPFIX Options and the sessionScope Information Element. seconds 0 2013-02-18 maxFlowEndSeconds dateTimeSeconds default 261 current The latest absolute timestamp of the last packet within any Flow within the scope containing this Information Element, rounded up to the second if necessary. This Information Element SHOULD be bound to its containing IPFIX Transport Session via IPFIX Options and the sessionScope Information Element. seconds 0 2013-02-18 messageMD5Checksum octetArray default 262 current The MD5 checksum of the IPFIX Message containing this record. This Information Element SHOULD be bound to its containing IPFIX Message via an options record and the messageScope Information Element, and SHOULD appear only once in a given IPFIX Message. To calculate the value of this Information Element, first buffer the containing IPFIX Message, setting the value of this Information Element to all zeroes. Then calculate the MD5 checksum of the resulting buffer as defined in , place the resulting value in this Information Element, and export the buffered message. This Information Element is intended as a simple checksum only; therefore collision resistance and algorithm agility are not required, and MD5 is an appropriate message digest. This Information Element has a fixed length of 16 octets. 0 2013-02-18 messageScope unsigned8 263 current The presence of this Information Element as scope in an Options Template signifies that the options described by the Template apply to the IPFIX Message that contains them. It is defined for general purpose message scoping of options, and proposed specifically to allow the attachment a checksum to a message via IPFIX Options. The value of this Information Element MUST be written as 0 by the File Writer or Exporting Process. The value of this Information Element MUST be ignored by the File Reader or the Collecting Process. 0-0 0 2013-02-18 minExportSeconds dateTimeSeconds default 264 current The absolute Export Time of the earliest IPFIX Message within the scope containing this Information Element. This Information Element SHOULD be bound to its containing IPFIX Transport Session via an options record and the sessionScope Information Element. seconds 0 2013-02-18 minFlowStartSeconds dateTimeSeconds default 265 current The earliest absolute timestamp of the first packet within any Flow within the scope containing this Information Element, rounded down to the second if necessary. This Information Element SHOULD be bound to its containing IPFIX Transport Session via an options record and the sessionScope Information Element. seconds 0 2013-02-18 opaqueOctets octetArray default 266 current This Information Element is used to encapsulate non- IPFIX data into an IPFIX Message stream, for the purpose of allowing a non-IPFIX data processor to store a data stream inline within an IPFIX File. A Collecting Process or File Writer MUST NOT try to interpret this binary data. This Information Element differs from paddingOctets as its contents are meaningful in some non-IPFIX context, while the contents of paddingOctets MUST be 0x00 and are intended only for Information Element alignment. 0 2013-02-18 sessionScope unsigned8 267 current The presence of this Information Element as scope in an Options Template signifies that the options described by the Template apply to the IPFIX Transport Session that contains them. Note that as all options are implicitly scoped to Transport Session and Observation Domain, this Information Element is equivalent to a "null" scope. It is defined for general purpose session scoping of options, and proposed specifically to allow the attachment of time window to an IPFIX File via IPFIX Options. The value of this Information Element MUST be written as 0 by the File Writer or Exporting Process. The value of this Information Element MUST be ignored by the File Reader or the Collecting Process. 0-0 0 2013-02-18 maxFlowEndMicroseconds dateTimeMicroseconds default 268 current The latest absolute timestamp of the last packet within any Flow within the scope containing this Information Element, rounded up to the microsecond if necessary. This Information Element SHOULD be bound to its containing IPFIX Transport Session via IPFIX Options and the sessionScope Information Element. This Information Element SHOULD be used only in Transport Sessions containing Flow Records with microsecond- precision (or better) timestamp Information Elements. microseconds 0 2013-02-18 maxFlowEndMilliseconds dateTimeMilliseconds default 269 current The latest absolute timestamp of the last packet within any Flow within the scope containing this Information Element, rounded up to the millisecond if necessary. This Information Element SHOULD be bound to its containing IPFIX Transport Session via IPFIX Options and the sessionScope Information Element. This Information Element SHOULD be used only in Transport Sessions containing Flow Records with millisecond- precision (or better) timestamp Information Elements. milliseconds 0 2013-02-18 maxFlowEndNanoseconds dateTimeNanoseconds default 270 current The latest absolute timestamp of the last packet within any Flow within the scope containing this Information Element. This Information Element SHOULD be bound to its containing IPFIX Transport Session via IPFIX Options and the sessionScope Information Element. This Information Element SHOULD be used only in Transport Sessions containing Flow Records with nanosecond-precision timestamp Information Elements. nanoseconds 0 2013-02-18 minFlowStartMicroseconds dateTimeMicroseconds default 271 current The earliest absolute timestamp of the first packet within any Flow within the scope containing this Information Element, rounded down to the microsecond if necessary. This Information Element SHOULD be bound to its containing IPFIX Transport Session via an options record and the sessionScope Information Element. This Information Element SHOULD be used only in Transport Sessions containing Flow Records with microsecond- precision (or better) timestamp Information Elements. microseconds 0 2013-02-18 minFlowStartMilliseconds dateTimeMilliseconds default 272 current The earliest absolute timestamp of the first packet within any Flow within the scope containing this Information Element, rounded down to the millisecond if necessary. This Information Element SHOULD be bound to its containing IPFIX Transport Session via an options record and the sessionScope Information Element. This Information Element SHOULD be used only in Transport Sessions containing Flow Records with millisecond- precision (or better) timestamp Information Elements. milliseconds 0 2013-02-18 minFlowStartNanoseconds dateTimeNanoseconds default 273 current The earliest absolute timestamp of the first packet within any Flow within the scope containing this Information Element. This Information Element SHOULD be bound to its containing IPFIX Transport Session via an options record and the sessionScope Information Element. This Information Element SHOULD be used only in Transport Sessions containing Flow Records with nanosecond-precision timestamp Information Elements. nanoseconds 0 2013-02-18 collectorCertificate octetArray default 274 current The full X.509 certificate, encoded in ASN.1 DER format, used by the Collector when IPFIX Messages were transmitted using TLS or DTLS. This Information Element SHOULD be bound to its containing IPFIX Transport Session via an options record and the sessionScope Information Element, or to its containing IPFIX Message via an options record and the messageScope Information Element. 0 2013-02-18 exporterCertificate octetArray default 275 current The full X.509 certificate, encoded in ASN.1 DER format, used by the Collector when IPFIX Messages were transmitted using TLS or DTLS. This Information Element SHOULD be bound to its containing IPFIX Transport Session via an options record and the sessionScope Information Element, or to its containing IPFIX Message via an options record and the messageScope Information Element. 0 2013-02-18 dataRecordsReliability boolean default 276 current The export reliability of Data Records, within this SCTP stream, for the element(s) in the Options Template scope. A typical example of an element for which the export reliability will be reported is the templateID, as specified in the Data Records Reliability Options Template. A value of 'True' means that the Exporting Process MUST send any Data Records associated with the element(s) reliably within this SCTP stream. A value of 'False' means that the Exporting Process MAY send any Data Records associated with the element(s) unreliably within this SCTP stream. 1 2014-02-03 observationPointType unsigned8 identifier 277 current Type of observation point. Values are listed in the observationPointType registry. See the "observationPointType (Value 277)" registry . 0 2013-02-18 newConnectionDeltaCount unsigned32 deltaCounter 278 current This information element counts the number of TCP or UDP connections which were opened during the observation period. The observation period may be specified by the flow start and end timestamps. 1 2014-08-13 connectionSumDurationSeconds unsigned64 279 current This information element aggregates the total time in seconds for all of the TCP or UDP connections which were in use during the observation period. For example if there are 5 concurrent connections each for 10 seconds, the value would be 50 s. seconds 1 2013-06-25 connectionTransactionId unsigned64 identifier 280 current This information element identifies a transaction within a connection. A transaction is a meaningful exchange of application data between two network devices or a client and server. A transactionId is assigned the first time a flow is reported, so that later reports for the same flow will have the same transactionId. A different transactionId is used for each transaction within a TCP or UDP connection. The identifiers need not be sequential. 0 2013-02-18 postNATSourceIPv6Address ipv6Address default 281 current The definition of this Information Element is identical to the definition of Information Element 'sourceIPv6Address', except that it reports a modified value caused by a NAT64 middlebox function after the packet passed the Observation Point. See for the definition of the Source Address field in the IPv6 header. See for the definition of middleboxes. See for nat64 specification. 0 2013-02-18 postNATDestinationIPv6Address ipv6Address default 282 current The definition of this Information Element is identical to the definition of Information Element 'destinationIPv6Address', except that it reports a modified value caused by a NAT64 middlebox function after the packet passed the Observation Point. See for the definition of the Destination Address field in the IPv6 header. See for the definition of middleboxes. See for nat64 specification. 0 2013-02-18 natPoolId unsigned32 identifier 283 current Locally unique identifier of a NAT pool. 0 2013-02-18 natPoolName string default 284 current The name of a NAT pool identified by a natPoolID. 0 2013-02-18 anonymizationFlags unsigned16 flags 285 current A flag word describing specialized modifications to the anonymization policy in effect for the anonymization technique applied to a referenced Information Element within a referenced Template. When flags are clear (0), the normal policy (as described by anonymizationTechnique) applies without modification. MSB 14 13 12 11 10 9 8 7 6 5 4 3 2 1 LSB +---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+ | Reserved |LOR|PmA| SC | +---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+ anonymizationFlags IE +--------+----------+-----------------------------------------------+ | bit(s) | name | description | | (LSB = | | | | 0) | | | +--------+----------+-----------------------------------------------+ | 0-1 | SC | Stability Class: see the Stability Class | | | | table below, and Section 5.1 of [RFC6235]. | | 2 | PmA | Perimeter Anonymization: when set (1), | | | | source Information Elements as described in | | | | [RFC5103] are interpreted as external | | | | addresses, and destination Information | | | | Elements as described in [RFC5103] are | | | | interpreted as internal addresses, for the | | | | purposes of associating | | | | anonymizationTechnique to Information | | | | Elements only; see Section 7.2.2 of [RFC6235] | | | | for details. | | | | This bit MUST NOT be set when associated with | | | | a non-endpoint (i.e., source or | | | | destination) Information Element. SHOULD be | | | | consistent within a record (i.e., if a | | | | source Information Element has this flag | | | | set, the corresponding destination element | | | | SHOULD have this flag set, and vice versa.) | | 3 | LOR | Low-Order Unchanged: when set (1), the | | | | low-order bits of the anonymized Information | | | | Element contain real data. This modification | | | | is intended for the anonymization of | | | | network-level addresses while leaving | | | | host-level addresses intact in order to | | | | preserve host level-structure, which could | | | | otherwise be used to reverse anonymization. | | | | MUST NOT be set when associated with a | | | | truncation-based anonymizationTechnique. | | 4-15 | Reserved | Reserved for future use: SHOULD be cleared | | | | (0) by the Exporting Process and MUST be | | | | ignored by the Collecting Process. | +--------+----------+-----------------------------------------------+ The Stability Class portion of this flags word describes the stability class of the anonymization technique applied to a referenced Information Element within a referenced Template. Stability classes refer to the stability of the parameters of the anonymization technique, and therefore the comparability of the mapping between the real and anonymized values over time. This determines which anonymized datasets may be compared with each other. Values are as follows: +-----+-----+-------------------------------------------------------+ | Bit | Bit | Description | | 1 | 0 | | +-----+-----+-------------------------------------------------------+ | 0 | 0 | Undefined: the Exporting Process makes no | | | | representation as to how stable the mapping is, or | | | | over what time period values of this field will | | | | remain comparable; while the Collecting Process MAY | | | | assume Session level stability, Session level | | | | stability is not guaranteed. Processes SHOULD assume | | | | this is the case in the absence of stability class | | | | information; this is the default stability class. | | 0 | 1 | Session: the Exporting Process will ensure that the | | | | parameters of the anonymization technique are stable | | | | during the Transport Session. All the values of the | | | | described Information Element for each Record | | | | described by the referenced Template within the | | | | Transport Session are comparable. The Exporting | | | | Process SHOULD endeavour to ensure at least this | | | | stability class. | | 1 | 0 | Exporter-Collector Pair: the Exporting Process will | | | | ensure that the parameters of the anonymization | | | | technique are stable across Transport Sessions over | | | | time with the given Collecting Process, but may use | | | | different parameters for different Collecting | | | | Processes. Data exported to different Collecting | | | | Processes are not comparable. | | 1 | 1 | Stable: the Exporting Process will ensure that the | | | | parameters of the anonymization technique are stable | | | | across Transport Sessions over time, regardless of | | | | the Collecting Process to which it is sent. | +-----+-----+-------------------------------------------------------+ 0 2013-02-18 anonymizationTechnique unsigned16 identifier 286 current A description of the anonymization technique applied to a referenced Information Element within a referenced Template. Each technique may be applicable only to certain Information Elements and recommended only for certain Information Elements. Values are listed in the anonymizationTechnique registry. See the "anonymizationTechnique (Value 286)" registry . 0 2013-02-18 informationElementIndex unsigned16 identifier 287 current A zero-based index of an Information Element referenced by informationElementId within a Template referenced by templateId; used to disambiguate scope for templates containing multiple identical Information Elements. 0 2013-02-18 p2pTechnology string default 288 current Specifies if the Application ID is based on peer-to-peer technology. Possible values are: { "yes", "y", 1 }, { "no", "n", 2 } and { "unassigned", "u", 0 }. 0 2013-02-18 tunnelTechnology string default 289 current Specifies if the Application ID is used as a tunnel technology. Possible values are: { "yes", "y", 1 }, { "no", "n", 2 } and { "unassigned", "u", 0 }. 0 2013-02-18 encryptedTechnology string default 290 current Specifies if the Application ID is an encrypted networking protocol. Possible values are: { "yes", "y", 1 }, { "no", "n", 2 } and { "unassigned", "u", 0 }. 0 2013-02-18 basicList basicList list 291 current Specifies a generic Information Element with a basicList abstract data type. For example, a list of port numbers, a list of interface indexes, etc. 0 2013-02-18 subTemplateList subTemplateList list 292 current Specifies a generic Information Element with a subTemplateList abstract data type. 0 2013-02-18 subTemplateMultiList subTemplateMultiList list 293 current Specifies a generic Information Element with a subTemplateMultiList abstract data type. 0 2013-02-18 bgpValidityState unsigned8 identifier 294 current This element describes the "validity state" of the BGP route correspondent source or destination IP address. If the "validity state" for this Flow is only available, then the value of this Information Element is 255. See for a description of BGP-4, for the definition of "validity states" and for the encoding of those "validity states". 0 2013-02-18 IPSecSPI unsigned32 identifier 295 current IPSec Security Parameters Index (SPI). See for the definition of SPI. 0 2013-02-18 greKey unsigned32 identifier 296 current GRE key, which is used for identifying an individual traffic flow within a tunnel. See for the definition of GRE and the GRE Key. 0 2013-02-18 natType unsigned8 identifier 297 current This Information Element identifies the NAT type applied to packets of the Flow. Values are listed in the natType registry. See the "natType (Value 297)" registry . See for the definition of NAT (commonly named NAT44). See for the definition of NAT46. See for the definition of NAT64. See for the definition of NPTv6. See for the definition of IPv4. See for the definition of IPv6. 0 2013-02-18 initiatorPackets unsigned64 deltaCounter 298 current The total number of layer 4 packets in a flow from the initiator since the previous report. The initiator is the device which triggered the session creation, and remains the same for the life of the session. packets See #231, initiatorOctets. 1 2014-08-13 responderPackets unsigned64 deltaCounter 299 current The total number of layer 4 packets in a flow from the responder since the previous report. The responder is the device which replies to the initiator, and remains the same for the life of the session. packets See #232, responderOctets. 1 2014-08-13 observationDomainName string default 300 current The name of an observation domain identified by an observationDomainId. See #149, observationDomainId. 0 2013-02-18 selectionSequenceId unsigned64 identifier 301 current From all the packets observed at an Observation Point, a subset of the packets is selected by a sequence of one or more Selectors. The selectionSequenceId is a unique value per Observation Domain, specifying the Observation Point and the sequence of Selectors through which the packets are selected. 0 2013-02-18 selectorId unsigned64 identifier 302 current The Selector ID is the unique ID identifying a Primitive Selector. Each Primitive Selector must have a unique ID in the Observation Domain. 0 2013-02-18 informationElementId unsigned16 identifier 303 current This Information Element contains the ID of another Information Element. 0 2013-02-18 selectorAlgorithm unsigned16 identifier 304 current This Information Element identifies the packet selection methods (e.g., Filtering, Sampling) that are applied by the Selection Process. Most of these methods have parameters. Further Information Elements are needed to fully specify packet selection with these methods and all of their parameters. For the methods parameters, Information Elements are defined in the IPFIX registry IANA-IPFIX. The names of these Information Elements are listed for each method identifier. Further method identifiers may be added to the list. It might be necessary to define new Information Elements to specify their parameters. There is a broad variety of possible parameters that could be used for Property Match Filtering (5) but currently there are no agreed parameters specified. See the "Packet Sampling (PSAMP) Parameters" registry 0 2013-02-18 samplingPacketInterval unsigned32 quantity 305 current This Information Element specifies the number of packets that are consecutively sampled. A value of 100 means that 100 consecutive packets are sampled. For example, this Information Element may be used to describe the configuration of a systematic count-based Sampling Selector. packets 0 2013-02-18 samplingPacketSpace unsigned32 quantity 306 current This Information Element specifies the number of packets between two "samplingPacketInterval"s. A value of 100 means that the next interval starts 100 packets (which are not sampled) after the current "samplingPacketInterval" is over. For example, this Information Element may be used to describe the configuration of a systematic count-based Sampling Selector. packets 0 2013-02-18 samplingTimeInterval unsigned32 quantity 307 current This Information Element specifies the time interval in microseconds during which all arriving packets are sampled. For example, this Information Element may be used to describe the configuration of a systematic time-based Sampling Selector. microseconds 0 2013-02-18 samplingTimeSpace unsigned32 quantity 308 current This Information Element specifies the time interval in microseconds between two "samplingTimeInterval"s. A value of 100 means that the next interval starts 100 microseconds (during which no packets are sampled) after the current "samplingTimeInterval" is over. For example, this Information Element may used to describe the configuration of a systematic time-based Sampling Selector. microseconds 0 2013-02-18 samplingSize unsigned32 quantity 309 current This Information Element specifies the number of elements taken from the parent Population for random Sampling methods. For example, this Information Element may be used to describe the configuration of a random n-out-of-N Sampling Selector. packets 0 2013-02-18 samplingPopulation unsigned32 quantity 310 current This Information Element specifies the number of elements in the parent Population for random Sampling methods. For example, this Information Element may be used to describe the configuration of a random n-out-of-N Sampling Selector. packets 0 2013-02-18 samplingProbability float64 quantity 311 current This Information Element specifies the probability that a packet is sampled, expressed as a value between 0 and 1. The probability is equal for every packet. A value of 0 means no packet was sampled since the probability is 0. For example, this Information Element may be used to describe the configuration of a uniform probabilistic Sampling Selector. 0 2013-02-18 dataLinkFrameSize unsigned16 quantity 312 current This Information Element specifies the length of the selected data link frame. The data link layer is defined in [ISO/IEC.7498-1:1994]. [ISO/IEC.7498-1:1994] 1 2014-01-11 ipHeaderPacketSection octetArray default 313 current This Information Element carries a series of n octets from the IP header of a sampled packet, starting sectionOffset octets into the IP header. However, if no sectionOffset field corresponding to this Information Element is present, then a sectionOffset of zero applies, and the octets MUST be from the start of the IP header. With sufficient length, this element also reports octets from the IP payload. However, full packet capture of arbitrary packet streams is explicitly out of scope per the Security Considerations sections of and . The sectionExportedOctets expresses how much data was exported, while the remainder is padding. When the sectionExportedOctets field corresponding to this Information Element exists, this Information Element MAY have a fixed length and MAY be padded, or it MAY have a variable length. When the sectionExportedOctets field corresponding to this Information Element does not exist, this Information Element SHOULD have a variable length and MUST NOT be padded. In this case, the size of the exported section may be constrained due to limitations in the IPFIX protocol. 1 2014-01-11 ipPayloadPacketSection octetArray default 314 current This Information Element carries a series of n octets from the IP payload of a sampled packet, starting sectionOffset octets into the IP payload. However, if no sectionOffset field corresponding to this Information Element is present, then a sectionOffset of zero applies, and the octets MUST be from the start of the IP payload. The IPv4 payload is that part of the packet that follows the IPv4 header and any options, which refers to as "data" or "data octets". For example, see the examples in , Appendix A. The IPv6 payload is the rest of the packet following the 40-octet IPv6 header. Note that any extension headers present are considered part of the payload. See for the IPv6 specification. The sectionExportedOctets expresses how much data was observed, while the remainder is padding. When the sectionExportedOctets field corresponding to this Information Element exists, this Information Element MAY have a fixed length and MAY be padded, or MAY have a variable length. When the sectionExportedOctets field corresponding to this Information Element does not exist, this Information Element SHOULD have a variable length and MUST NOT be padded. In this case, the size of the exported section may be constrained due to limitations in the IPFIX protocol. 1 2014-01-11 dataLinkFrameSection octetArray default 315 current This Information Element carries n octets from the data link frame of a selected frame, starting sectionOffset octets into the frame. However, if no sectionOffset field corresponding to this Information Element is present, then a sectionOffset of zero applies, and the octets MUST be from the start of the data link frame. The sectionExportedOctets expresses how much data was observed, while the remainder is padding. When the sectionExportedOctets field corresponding to this Information Element exists, this Information Element MAY have a fixed length and MAY be padded, or MAY have a variable length. When the sectionExportedOctets field corresponding to this Information Element does not exist, this Information Element SHOULD have a variable length and MUST NOT be padded. In this case, the size of the exported section may be constrained due to limitations in the IPFIX protocol. Further Information Elements, i.e., dataLinkFrameType and dataLinkFrameSize, are needed to specify the data link type and the size of the data link frame of this Information Element. A set of these Information Elements MAY be contained in a structured data type, as expressed in . Or a set of these Information Elements MAY be contained in one Flow Record as shown in Appendix B of . The data link layer is defined in [ISO/IEC.7498-1:1994]. [ISO/IEC.7498-1:1994] 1 2014-01-11 mplsLabelStackSection octetArray default 316 current This Information Element carries a series of n octets from the MPLS label stack of a sampled packet, starting sectionOffset octets into the MPLS label stack. However, if no sectionOffset field corresponding to this Information Element is present, then a sectionOffset of zero applies, and the octets MUST be from the head of the MPLS label stack. With sufficient length, this element also reports octets from the MPLS payload. However, full packet capture of arbitrary packet streams is explicitly out of scope per the Security Considerations sections of and . See for the specification of MPLS packets. See for the specification of the MPLS label stack. The sectionExportedOctets expresses how much data was observed, while the remainder is padding. When the sectionExportedOctets field corresponding to this Information Element exists, this Information Element MAY have a fixed length and MAY be padded, or MAY have a variable length. When the sectionExportedOctets field corresponding to this Information Element does not exist, this Information Element SHOULD have a variable length and MUST NOT be padded. In this case, the size of the exported section may be constrained due to limitations in the IPFIX protocol. 1 2014-01-11 mplsPayloadPacketSection octetArray default 317 current The mplsPayloadPacketSection carries a series of n octets from the MPLS payload of a sampled packet, starting sectionOffset octets into the MPLS payload, as it is data that follows immediately after the MPLS label stack. However, if no sectionOffset field corresponding to this Information Element is present, then a sectionOffset of zero applies, and the octets MUST be from the start of the MPLS payload. See for the specification of MPLS packets. See for the specification of the MPLS label stack. The sectionExportedOctets expresses how much data was observed, while the remainder is padding. When the sectionExportedOctets field corresponding to this Information Element exists, this Information Element MAY have a fixed length and MAY be padded, or it MAY have a variable length. When the sectionExportedOctets field corresponding to this Information Element does not exist, this Information Element SHOULD have a variable length and MUST NOT be padded. In this case, the size of the exported section may be constrained due to limitations in the IPFIX protocol. 1 2014-01-11 selectorIdTotalPktsObserved unsigned64 totalCounter 318 current This Information Element specifies the total number of packets observed by a Selector, for a specific value of SelectorId. This Information Element should be used in an Options Template scoped to the observation to which it refers. See Section 3.4.2.1 of the IPFIX protocol document . packets 0 2013-02-18 selectorIdTotalPktsSelected unsigned64 totalCounter 319 current This Information Element specifies the total number of packets selected by a Selector, for a specific value of SelectorId. This Information Element should be used in an Options Template scoped to the observation to which it refers. See Section 3.4.2.1 of the IPFIX protocol document . packets 0 2013-02-18 absoluteError float64 quantity 320 current This Information Element specifies the maximum possible measurement error of the reported value for a given Information Element. The absoluteError has the same unit as the Information Element with which it is associated. The real value of the metric can differ by absoluteError (positive or negative) from the measured value. This Information Element provides only the error for measured values. If an Information Element contains an estimated value (from Sampling), the confidence boundaries and confidence level have to be provided instead, using the upperCILimit, lowerCILimit, and confidenceLevel Information Elements. This Information Element should be used in an Options Template scoped to the observation to which it refers. See Section 3.4.2.1 of the IPFIX protocol document . inferred 1 2018-06-13 relativeError float64 quantity 321 current This Information Element specifies the maximum possible positive or negative error ratio for the reported value for a given Information Element as percentage of the measured value. The real value of the metric can differ by relativeError percent (positive or negative) from the measured value. This Information Element provides only the error for measured values. If an Information Element contains an estimated value (from Sampling), the confidence boundaries and confidence level have to be provided instead, using the upperCILimit, lowerCILimit, and confidenceLevel Information Elements. This Information Element should be used in an Options Template scoped to the observation to which it refers. See Section 3.4.2.1 of the IPFIX protocol document . 0 2013-02-18 observationTimeSeconds dateTimeSeconds default 322 current This Information Element specifies the absolute time in seconds of an observation. seconds 1 2014-02-03 observationTimeMilliseconds dateTimeMilliseconds default 323 current This Information Element specifies the absolute time in milliseconds of an observation. milliseconds 1 2014-02-03 observationTimeMicroseconds dateTimeMicroseconds default 324 current This Information Element specifies the absolute time in microseconds of an observation. microseconds 1 2014-02-03 observationTimeNanoseconds dateTimeNanoseconds default 325 current This Information Element specifies the absolute time in nanoseconds of an observation. nanoseconds 1 2014-02-03 digestHashValue unsigned64 quantity 326 current This Information Element specifies the value from the digest hash function. See also Sections 6.2, 3.8 and 7.1 of . 0 2013-02-18 hashIPPayloadOffset unsigned64 quantity 327 current This Information Element specifies the IP payload offset used by a Hash-based Selection Selector. See also Sections 6.2, 3.8 and 7.1 of . 0 2013-02-18 hashIPPayloadSize unsigned64 quantity 328 current This Information Element specifies the IP payload size used by a Hash-based Selection Selector. See also Sections 6.2, 3.8 and 7.1 of . 0 2013-02-18 hashOutputRangeMin unsigned64 quantity 329 current This Information Element specifies the value for the beginning of a hash function's potential output range. See also Sections 6.2, 3.8 and 7.1 of . 0 2013-02-18 hashOutputRangeMax unsigned64 quantity 330 current This Information Element specifies the value for the end of a hash function's potential output range. See also Sections 6.2, 3.8 and 7.1 of . 0 2013-02-18 hashSelectedRangeMin unsigned64 quantity 331 current This Information Element specifies the value for the beginning of a hash function's selected range. See also Sections 6.2, 3.8 and 7.1 of . 0 2013-02-18 hashSelectedRangeMax unsigned64 quantity 332 current This Information Element specifies the value for the end of a hash function's selected range. See also Sections 6.2, 3.8 and 7.1 of . 0 2013-02-18 hashDigestOutput boolean default 333 current This Information Element contains a boolean value that is TRUE if the output from this hash Selector has been configured to be included in the packet report as a packet digest, else FALSE. See also Sections 6.2, 3.8 and 7.1 of . 1 2014-02-03 hashInitialiserValue unsigned64 quantity 334 current This Information Element specifies the initialiser value to the hash function. See also Sections 6.2, 3.8 and 7.1 of . 0 2013-02-18 selectorName string default 335 current The name of a selector identified by a selectorID. Globally unique per Metering Process. 0 2013-02-18 upperCILimit float64 quantity 336 current This Information Element specifies the upper limit of a confidence interval. It is used to provide an accuracy statement for an estimated value. The confidence limits define the range in which the real value is assumed to be with a certain probability p. Confidence limits always need to be associated with a confidence level that defines this probability p. Please note that a confidence interval only provides a probability that the real value lies within the limits. That means the real value can lie outside the confidence limits. The upperCILimit, lowerCILimit, and confidenceLevel Information Elements should all be used in an Options Template scoped to the observation to which they refer. See Section 3.4.2.1 of the IPFIX protocol document . Note that the upperCILimit, lowerCILimit, and confidenceLevel are all required to specify confidence, and should be disregarded unless all three are specified together. 0 2013-02-18 lowerCILimit float64 quantity 337 current This Information Element specifies the lower limit of a confidence interval. For further information, see the description of upperCILimit. The upperCILimit, lowerCILimit, and confidenceLevel Information Elements should all be used in an Options Template scoped to the observation to which they refer. See Section 3.4.2.1 of the IPFIX protocol document . Note that the upperCILimit, lowerCILimit, and confidenceLevel are all required to specify confidence, and should be disregarded unless all three are specified together. 0 2013-02-18 confidenceLevel float64 quantity 338 current This Information Element specifies the confidence level. It is used to provide an accuracy statement for estimated values. The confidence level provides the probability p with which the real value lies within a given range. A confidence level always needs to be associated with confidence limits that define the range in which the real value is assumed to be. The upperCILimit, lowerCILimit, and confidenceLevel Information Elements should all be used in an Options Template scoped to the observation to which they refer. See Section 3.4.2.1 of the IPFIX protocol document . Note that the upperCILimit, lowerCILimit, and confidenceLevel are all required to specify confidence, and should be disregarded unless all three are specified together. 0 2013-02-18 informationElementDataType unsigned8 339 current A description of the abstract data type of an IPFIX information element. These are taken from the abstract data types defined in Section 3.1 of the IPFIX Information Model ; see that section for more information on the types described in the "IPFIX Information Element Data Types" registry. These types are registered in the "IPFIX Information Element Data Types" registry. The "IPFIX Information Element Data Types" registry is intended to assign numbers for type names, not to provide a mechanism for adding data types to the IPFIX Protocol; as such, modifications require Standards Action . See the "IPFIX Information Element Data Types" registry 0 2013-02-18 informationElementDescription string default 340 current A UTF-8 encoded Unicode string containing a human-readable description of an Information Element. The content of the informationElementDescription MAY be annotated with one or more language tags , encoded in-line within the UTF-8 string, in order to specify the language in which the description is written. Description text in multiple languages MAY tag each section with its own language tag; in this case, the description information in each language SHOULD have equivalent meaning. In the absence of any language tag, the "i-default" language SHOULD be assumed. See Section 4 (Security Considerations) of for notes on string handling for Information Element type records. 0 2013-02-18 informationElementName string default 341 current A UTF-8 encoded Unicode string containing the name of an Information Element, intended as a simple identifier. See the Security Considerations section for notes on string handling for Information Element type records 0 2013-02-18 informationElementRangeBegin unsigned64 quantity 342 current Contains the inclusive low end of the range of acceptable values for an Information Element. 0 2013-02-18 informationElementRangeEnd unsigned64 quantity 343 current Contains the inclusive high end of the range of acceptable values for an Information Element. 0 2013-02-18 informationElementSemantics unsigned8 344 current A description of the semantics of an IPFIX Information Element. These are taken from the data type semantics defined in Section 3.2 of the IPFIX Information Model ; see that section for more information on the types defined in the "IPFIX Information Element Semantics" registry. This field may take the values in the "IPFIX Information Element Semantics" registry. The special value 0x00 (default) is used to note that no semantics apply to the field; it cannot be manipulated by a Collecting Process or File Reader that does not understand it a priori. The "IPFIX Information Element Semantics" registry is intended to assign numbers for semantics names, not to provide a mechanism for adding semantics to the IPFIX Protocol; as such, modifications require Standards Action . See the "IPFIX Information Element Semantics" registry 0 2013-02-18 informationElementUnits unsigned16 345 current A description of the units of an IPFIX Information Element. These correspond to the units implicitly defined in the Information Element definitions in Section 5 of the IPFIX Information Model ; see that section for more information on the types described in the "IPFIX Information Element Units" registry. These types can take the values in the "IPFIX Information Element Units" registry. The special value 0x00 (none) is used to note that the field is unitless. See the "IPFIX Information Element Units" registry 1 2020-10-01 privateEnterpriseNumber unsigned32 identifier 346 current A private enterprise number, as assigned by IANA. Within the context of an Information Element Type record, this element can be used along with the informationElementId element to scope properties to a specific Information Element. To export type information about an IANA-assigned Information Element, set the privateEnterpriseNumber to 0, or do not export the privateEnterpriseNumber in the type record. To export type information about an enterprise-specific Information Element, export the enterprise number in privateEnterpriseNumber, and export the Information Element number with the Enterprise bit cleared in informationElementId. The Enterprise bit in the associated informationElementId Information Element MUST be ignored by the Collecting Process. See the "Private Enterprise Numbers (PENs)" registry 0 2013-02-18 virtualStationInterfaceId octetArray default 347 current Instance Identifier of the interface to a Virtual Station. A Virtual Station is an end station instance: it can be a virtual machine or a physical host. See IEEE 802.1Qbg for the definition of Virtual Station Interface ID. 1 2014-02-03 virtualStationInterfaceName string default 348 current Name of the interface to a Virtual Station. A Virtual Station is an end station instance: it can be a virtual machine or a physical host. See IEEE 802.1Qbg for the definition of Virtual Station Interface. 1 2014-02-03 virtualStationUUID octetArray default 349 current Unique Identifier of a Virtual Station. A Virtual Station is an end station instance: it can be a virtual machine or a physical host. See IEEE 802.1Qbg for the definition of Virtual Station. 1 2014-02-03 virtualStationName string default 350 current Name of a Virtual Station. A Virtual Station is an end station instance: it can be a virtual machine or a physical host. See IEEE 802.1Qbg for the definition of Virtual Station. 0 2013-02-18 layer2SegmentId unsigned64 identifier 351 current Identifier of a layer 2 network segment in an overlay network. The most significant byte identifies the layer 2 network overlay network encapsulation type: 0x00 reserved 0x01 VxLAN 0x02 NVGRE The three lowest significant bytes hold the value of the layer 2 overlay network segment identifier. For example: - a 24 bit segment ID VXLAN Network Identifier (VNI) - a 24 bit Tenant Network Identifier (TNI) for NVGRE See VxLAN RFC at See NVGRE RFC at 0 2013-02-18 layer2OctetDeltaCount unsigned64 deltaCounter 352 current The number of layer 2 octets since the previous report (if any) in incoming packets for this Flow at the Observation Point. The number of octets includes layer 2 header(s) and layer 2 payload. # memo: layer 2 version of octetDeltaCount (field #1) octets 1 2014-05-02 layer2OctetTotalCount unsigned64 totalCounter 353 current The total number of layer 2 octets in incoming packets for this Flow at the Observation Point since the Metering Process (re-)initialization for this Observation Point. The number of octets includes layer 2 header(s) and layer 2 payload. # memo: layer 2 version of octetTotalCount (field #85) octets 1 2014-05-02 ingressUnicastPacketTotalCount unsigned64 totalCounter 354 current The total number of incoming unicast packets metered at the Observation Point since the Metering Process (re-)initialization for this Observation Point. packets 0 2013-02-18 ingressMulticastPacketTotalCount unsigned64 totalCounter 355 current The total number of incoming multicast packets metered at the Observation Point since the Metering Process (re-)initialization for this Observation Point. packets 0 2013-02-18 ingressBroadcastPacketTotalCount unsigned64 totalCounter 356 current The total number of incoming broadcast packets metered at the Observation Point since the Metering Process (re-)initialization for this Observation Point. packets 0 2013-02-18 egressUnicastPacketTotalCount unsigned64 totalCounter 357 current The total number of incoming unicast packets metered at the Observation Point since the Metering Process (re-)initialization for this Observation Point. packets 0 2013-02-18 egressBroadcastPacketTotalCount unsigned64 totalCounter 358 current The total number of incoming broadcast packets metered at the Observation Point since the Metering Process (re-)initialization for this Observation Point. packets 0 2013-02-18 monitoringIntervalStartMilliSeconds dateTimeMilliseconds default 359 current The absolute timestamp at which the monitoring interval started. A Monitoring interval is the period of time during which the Metering Process is running. milliseconds 0 2013-02-18 monitoringIntervalEndMilliSeconds dateTimeMilliseconds default 360 current The absolute timestamp at which the monitoring interval ended. A Monitoring interval is the period of time during which the Metering Process is running. milliseconds 0 2013-02-18 portRangeStart unsigned16 identifier 361 current The port number identifying the start of a range of port numbers. A value of zero indicates that the range start is not specified, i.e., the range is defined in some other way. See the assigned transport protocol (e.g., UDP, TCP, SCTP, and DCCP) port numbers . 0 2013-02-18 portRangeEnd unsigned16 identifier 362 current The port number identifying the end of a range of port numbers. A value of zero indicates that the range end is not specified, i.e., the range is defined in some other way. See the assigned transport protocol (e.g., UDP, TCP, SCTP, and DCCP) port numbers . 0 2013-02-18 portRangeStepSize unsigned16 identifier 363 current The step size in a port range. The default step size is 1, which indicates contiguous ports. A value of zero indicates that the step size is not specified, ie the range is defined in some other way. 0 2013-02-18 portRangeNumPorts unsigned16 identifier 364 current The number of ports in a port range. A value of zero indicates that the number of ports is not specified, ie the range is defined in some other way. 0 2013-02-18 staMacAddress macAddress default 365 current The IEEE 802 MAC address of a wireless station (STA). See section 1.4 of for the definition of STA. 1 2014-02-03 staIPv4Address ipv4Address default 366 current The IPv4 address of a wireless station (STA). See section 1.4 of for the definition of STA. 1 2014-02-03 wtpMacAddress macAddress default 367 current The IEEE 802 MAC address of a wireless access point (WTP). See section 1.4 of for the definition of WTP. 1 2014-02-03 ingressInterfaceType unsigned32 identifier 368 current The type of interface where packets of this Flow are being received. The value matches the value of managed object 'ifType'. See the "IANAifType-MIB" registry . 0 2013-02-18 egressInterfaceType unsigned32 identifier 369 current The type of interface where packets of this Flow are being sent. The value matches the value of managed object 'ifType'. See the "IANAifType-MIB" registry . 0 2013-02-18 rtpSequenceNumber unsigned16 370 current The RTP sequence number per . 0 2013-02-18 userName string default 371 current User name associated with the flow. 0 2013-02-18 applicationCategoryName string default 372 current An attribute that provides a first level categorization for each Application ID. 0 2013-02-18 applicationSubCategoryName string default 373 current An attribute that provides a second level categorization for each Application ID. 0 2013-02-18 applicationGroupName string default 374 current An attribute that groups multiple Application IDs that belong to the same networking application. 0 2013-02-18 originalFlowsPresent unsigned64 deltaCounter 375 current The non-conservative count of Original Flows contributing to this Aggregated Flow. Non-conservative counts need not sum to the original count on re-aggregation. flows 1 2013-06-25 originalFlowsInitiated unsigned64 deltaCounter 376 current The conservative count of Original Flows whose first packet is represented within this Aggregated Flow. Conservative counts must sum to the original count on re-aggregation. flows 1 2013-06-25 originalFlowsCompleted unsigned64 deltaCounter 377 current The conservative count of Original Flows whose last packet is represented within this Aggregated Flow. Conservative counts must sum to the original count on re-aggregation. flows 1 2013-06-25 distinctCountOfSourceIPAddress unsigned64 totalCounter 378 current The count of distinct source IP address values for Original Flows contributing to this Aggregated Flow, without regard to IP version. This Information Element is preferred to the IP-version-specific counters, unless it is important to separate the counts by version. 0 2013-02-18 distinctCountOfDestinationIPAddress unsigned64 totalCounter 379 current The count of distinct destination IP address values for Original Flows contributing to this Aggregated Flow, without regard to IP version. This Information Element is preferred to the version-specific counters, unless it is important to separate the counts by version. 0 2013-02-18 distinctCountOfSourceIPv4Address unsigned32 totalCounter 380 current The count of distinct source IPv4 address values for Original Flows contributing to this Aggregated Flow. 0 2013-02-18 distinctCountOfDestinationIPv4Address unsigned32 totalCounter 381 current The count of distinct destination IPv4 address values for Original Flows contributing to this Aggregated Flow. 0 2013-02-18 distinctCountOfSourceIPv6Address unsigned64 totalCounter 382 current The count of distinct source IPv6 address values for Original Flows contributing to this Aggregated Flow. 0 2013-02-18 distinctCountOfDestinationIPv6Address unsigned64 totalCounter 383 current The count of distinct destination IPv6 address values for Original Flows contributing to this Aggregated Flow. 0 2013-02-18 valueDistributionMethod unsigned8 384 current A description of the method used to distribute the counters from Contributing Flows into the Aggregated Flow records described by an associated scope, generally a Template. The method is deemed to apply to all the non-key Information Elements in the referenced scope for which value distribution is a valid operation; if the originalFlowsInitiated and/or originalFlowsCompleted Information Elements appear in the Template, they are not subject to this distribution method, as they each infer their own distribution method. The "valueDistributionMethod (Value 384)" registry is intended to list a complete set of possible value distribution methods. See the "valueDistributionMethod (Value 384)" registry . 0 2013-02-18 rfc3550JitterMilliseconds unsigned32 quantity 385 current Interarrival jitter as defined in section 6.4.1 of , measured in milliseconds. milliseconds 0 2013-02-18 rfc3550JitterMicroseconds unsigned32 quantity 386 current Interarrival jitter as defined in section 6.4.1 of , measured in microseconds. microseconds 0 2013-02-18 rfc3550JitterNanoseconds unsigned32 quantity 387 current Interarrival jitter as defined in section 6.4.1 of , measured in nanoseconds. nanoseconds 0 2013-02-18 dot1qDEI boolean default 388 current The value of the 1-bit Drop Eligible Indicator (DEI) field of the VLAN tag as described in 802.1Q-2011 subclause 9.6. In case of a QinQ frame, it represents the outer tag's DEI field and in case of an IEEE 802.1ad frame it represents the DEI field of the S-TAG. Note: in earlier versions of 802.1Q the same bit field in the incoming packet is occupied by the Canonical Format Indicator (CFI) field, except for S-TAGs. 802.1Q-2011 subclause 9.6 1 2014-02-03 dot1qCustomerDEI boolean default 389 current In case of a QinQ frame, it represents the inner tag's Drop Eligible Indicator (DEI) field and in case of an IEEE 802.1ad frame it represents the DEI field of the C-TAG. 802.1Q-2011 subclause 9.6 1 2014-02-03 flowSelectorAlgorithm unsigned16 identifier 390 current This Information Element identifies the Intermediate Flow Selection Process technique (e.g., Filtering, Sampling) that is applied by the Intermediate Flow Selection Process. Most of these techniques have parameters. Its configuration parameter(s) MUST be clearly specified. Additional Information Elements are needed to fully specify packet selection with these methods and all of their parameters. Additional method identifiers may be added to the "flowSelectorAlgorithm (Value 390)" registry. It might be necessary to define new Information Elements to specify their parameters. See the "flowSelectorAlgorithm (Value 390)" registry . 0 2013-06-07 flowSelectedOctetDeltaCount unsigned64 deltaCounter 391 current This Information Element specifies the volume in octets of all Flows that are selected in the Intermediate Flow Selection Process since the previous report. octets 1 2014-08-13 flowSelectedPacketDeltaCount unsigned64 deltaCounter 392 current This Information Element specifies the volume in packets of all Flows that were selected in the Intermediate Flow Selection Process since the previous report. packets 1 2014-08-13 flowSelectedFlowDeltaCount unsigned64 deltaCounter 393 current This Information Element specifies the number of Flows that were selected in the Intermediate Flow Selection Process since the last report. flows 1 2014-08-13 selectorIDTotalFlowsObserved unsigned64 394 current This Information Element specifies the total number of Flows observed by a Selector, for a specific value of SelectorId. This Information Element should be used in an Options Template scoped to the observation to which it refers. See Section 3.4.2.1 of the IPFIX protocol document . flows 0 2013-06-07 selectorIDTotalFlowsSelected unsigned64 395 current This Information Element specifies the total number of Flows selected by a Selector, for a specific value of SelectorId. This Information Element should be used in an Options Template scoped to the observation to which it refers. See Section 3.4.2.1 of the IPFIX protocol document . flows 0 2013-06-07 samplingFlowInterval unsigned64 396 current This Information Element specifies the number of Flows that are consecutively sampled. A value of 100 means that 100 consecutive Flows are sampled. For example, this Information Element may be used to describe the configuration of a systematic count-based Sampling Selector. flows 0 2013-06-07 samplingFlowSpacing unsigned64 397 current This Information Element specifies the number of Flows between two "samplingFlowInterval"s. A value of 100 means that the next interval starts 100 Flows (which are not sampled) after the current "samplingFlowInterval" is over. For example, this Information Element may be used to describe the configuration of a systematic count-based Sampling Selector. flows 0 2013-06-07 flowSamplingTimeInterval unsigned64 398 current This Information Element specifies the time interval in microseconds during which all arriving Flows are sampled. For example, this Information Element may be used to describe the configuration of a systematic time-based Sampling Selector. microseconds 0 2013-06-07 flowSamplingTimeSpacing unsigned64 399 current This Information Element specifies the time interval in microseconds between two "flowSamplingTimeInterval"s. A value of 100 means that the next interval starts 100 microseconds (during which no Flows are sampled) after the current "flowsamplingTimeInterval" is over. For example, this Information Element may used to describe the configuration of a systematic time-based Sampling Selector. microseconds 0 2013-06-07 hashFlowDomain unsigned16 identifier 400 current This Information Element specifies the Information Elements that are used by the Hash-based Flow Selector as the Hash Domain. 0 2013-06-07 transportOctetDeltaCount unsigned64 deltaCounter 401 current The number of octets, excluding IP header(s) and Layer 4 transport protocol header(s), observed for this Flow at the Observation Point since the previous report (if any). octets 0 2013-08-01 transportPacketDeltaCount unsigned64 deltaCounter 402 current The number of packets containing at least one octet beyond the IP header(s) and Layer 4 transport protocol header(s), observed for this Flow at the Observation Point since the previous report (if any). packets 0 2013-08-01 originalExporterIPv4Address ipv4Address 403 current The IPv4 address used by the Exporting Process on an Original Exporter, as seen by the Collecting Process on an IPFIX Mediator. Used to provide information about the Original Observation Points to a downstream Collector. 0 2013-12-24 originalExporterIPv6Address ipv6Address 404 current The IPv6 address used by the Exporting Process on an Original Exporter, as seen by the Collecting Process on an IPFIX Mediator. Used to provide information about the Original Observation Points to a downstream Collector. 0 2013-12-24 originalObservationDomainId unsigned32 identifier 405 current The Observation Domain ID reported by the Exporting Process on an Original Exporter, as seen by the Collecting Process on an IPFIX Mediator. Used to provide information about the Original Observation Domain to a downstream Collector. When cascading through multiple Mediators, this identifies the initial Observation Domain in the cascade. 0 2013-12-24 intermediateProcessId unsigned32 identifier 406 current Description: An identifier of an Intermediate Process that is unique per IPFIX Device. Typically, this Information Element is used for limiting the scope of other Information Elements. Note that process identifiers may be assigned dynamically; that is, an Intermediate Process may be restarted with a different ID. 0 2013-12-24 ignoredDataRecordTotalCount unsigned64 totalCounter 407 current Description: The total number of received Data Records that the Intermediate Process did not process since the (re-)initialization of the Intermediate Process; includes only Data Records not examined or otherwise handled by the Intermediate Process due to resource constraints, not Data Records that were examined or otherwise handled by the Intermediate Process but those that merely do not contribute to any exported Data Record due to the operations performed by the Intermediate Process. 0 2013-12-24 dataLinkFrameType unsigned16 flags 408 current This Information Element specifies the type of the selected data link frame. Data link types are defined in the "dataLinkFrameType (Value 408)" registry. Additional values may be assigned by IANA. Note that the assigned values are bits so that multiple observations can be OR'd together. See the "dataLinkFrameType (Value 408)" registry . More information about the data link layer can be found in (IEEE802.3)(IEEE802.11)(ISO/IEC.7498-1:1994). 0 2014-01-11 sectionOffset unsigned16 quantity 409 current This Information Element specifies the offset of the packet section (e.g., dataLinkFrameSection, ipHeaderPacketSection, ipPayloadPacketSection, mplsLabelStackSection, and mplsPayloadPacketSection). If this Information Element is omitted, it defaults to zero (i.e., no offset). If multiple sectionOffset Information Elements are specified within a single Template, then they apply to the packet section Information Elements in order: the first sectionOffset applies to the first packet section, the second to the second, and so on. Note that the "closest" sectionOffset and packet section Information Elements within a given Template are not necessarily related. If there are fewer sectionOffset Information Elements than packet section Information Elements, then subsequent packet section Information Elements have no offset, i.e., a sectionOffset of zero applies to those packet section Information Elements. If there are more sectionOffset Information Elements than the number of packet section Information Elements, then the additional sectionOffset Information Elements are meaningless. 0 2014-01-11 sectionExportedOctets unsigned16 quantity 410 current This Information Element specifies the observed length of the packet section (e.g., dataLinkFrameSection, ipHeaderPacketSection, ipPayloadPacketSection, mplsLabelStackSection, and mplsPayloadPacketSection) when padding is used. The packet section may be of a fixed size larger than the sectionExportedOctets. In this case, octets in the packet section beyond the sectionExportedOctets MUST follow the rules for padding (i.e., be composed of zero (0) valued octets). 0 2014-01-11 dot1qServiceInstanceTag octetArray default 411 current This Information Element, which is 16 octets long, represents the Backbone Service Instance Tag (I-TAG) Tag Control Information (TCI) field of an Ethernet frame as described in [IEEE802.1Q]. It encodes the Backbone Service Instance Priority Code Point (I-PCP), Backbone Service Instance Drop Eligible Indicator (I-DEI), Use Customer Addresses (UCAs), Backbone Service Instance Identifier (I-SID), Encapsulated Customer Destination Address (C-DA), Encapsulated Customer Source Address (C-SA), and reserved fields. The structure and semantics within the Tag Control Information field are defined in [IEEE802.1Q]. [IEEE802.1Q] 1 2014-05-02 dot1qServiceInstanceId unsigned32 identifier 412 current The value of the 24-bit Backbone Service Instance Identifier (I-SID) portion of the Backbone Service Instance Tag (I-TAG) Tag Control Information (TCI) field of an Ethernet frame as described in [IEEE802.1Q]. 0-0xFFFFFF [IEEE802.1Q] 1 2014-05-02 dot1qServiceInstancePriority unsigned8 identifier 413 current The value of the 3-bit Backbone Service Instance Priority Code Point (I-PCP) portion of the Backbone Service Instance Tag (I-TAG) Tag Control Information (TCI) field of an Ethernet frame as described in [IEEE802.1Q]. 0-7 [IEEE802.1Q] 1 2014-05-02 dot1qCustomerSourceMacAddress macAddress default 414 current The value of the Encapsulated Customer Source Address (C-SA) portion of the Backbone Service Instance Tag (I-TAG) Tag Control Information (TCI) field of an Ethernet frame as described in [IEEE802.1Q]. [IEEE802.1Q] 1 2014-05-02 dot1qCustomerDestinationMacAddress macAddress default 415 current The value of the Encapsulated Customer Destination Address (C-DA) portion of the Backbone Service Instance Tag (I-TAG) Tag Control Information (TCI) field of an Ethernet frame as described in [IEEE802.1Q]. [IEEE802.1Q] 1 2014-05-02 416 deprecated Duplicate of Information Element ID 352, layer2OctetDeltaCount. 2 2014-05-13 postLayer2OctetDeltaCount unsigned64 deltaCounter 417 current The definition of this Information Element is identical to the definition of the layer2OctetDeltaCount Information Element, except that it reports a potentially modified value caused by a middlebox function after the packet passed the Observation Point. This Information Element is the layer 2 version of postOctetDeltaCount (ElementId #23). octets 1 2014-05-02 postMCastLayer2OctetDeltaCount unsigned64 deltaCounter 418 current The number of layer 2 octets since the previous report (if any) in outgoing multicast packets sent for packets of this Flow by a multicast daemon within the Observation Domain. This property cannot necessarily be observed at the Observation Point but may be retrieved by other means. The number of octets includes layer 2 header(s) and layer 2 payload. This Information Element is the layer 2 version of postMCastOctetDeltaCount (ElementId #20). octets 1 2014-05-02 419 deprecated Duplicate of Information Element ID 353, layer2OctetTotalCount. 2 2014-05-13 postLayer2OctetTotalCount unsigned64 totalCounter 420 current The definition of this Information Element is identical to the definition of the layer2OctetTotalCount Information Element, except that it reports a potentially modified value caused by a middlebox function after the packet passed the Observation Point. This Information Element is the layer 2 version of postOctetTotalCount (ElementId #171). octets 1 2014-05-02 postMCastLayer2OctetTotalCount unsigned64 totalCounter 421 current The total number of layer 2 octets in outgoing multicast packets sent for packets of this Flow by a multicast daemon in the Observation Domain since the Metering Process (re-)initialization. This property cannot necessarily be observed at the Observation Point but may be retrieved by other means. The number of octets includes layer 2 header(s) and layer 2 payload. This Information Element is the layer 2 version of postMCastOctetTotalCount (ElementId #175). octets 1 2014-05-02 minimumLayer2TotalLength unsigned64 422 current Layer 2 length of the smallest packet observed for this Flow. The packet length includes the length of the layer 2 header(s) and the length of the layer 2 payload. This Information Element is the layer 2 version of minimumIpTotalLength (ElementId #25). octets 1 2014-05-02 maximumLayer2TotalLength unsigned64 423 current Layer 2 length of the largest packet observed for this Flow. The packet length includes the length of the layer 2 header(s) and the length of the layer 2 payload. This Information Element is the layer 2 version of maximumIpTotalLength (ElementId #26). octets 1 2014-05-02 droppedLayer2OctetDeltaCount unsigned64 deltaCounter 424 current The number of layer 2 octets since the previous report (if any) in packets of this Flow dropped by packet treatment. The number of octets includes layer 2 header(s) and layer 2 payload. This Information Element is the layer 2 version of droppedOctetDeltaCount (ElementId #132). octets 1 2014-05-02 droppedLayer2OctetTotalCount unsigned64 totalCounter 425 current The total number of octets in observed layer 2 packets (including the layer 2 header) that were dropped by packet treatment since the (re-)initialization of the Metering Process. This Information Element is the layer 2 version of droppedOctetTotalCount (ElementId #134). octets 1 2014-05-02 ignoredLayer2OctetTotalCount unsigned64 totalCounter 426 current The total number of octets in observed layer 2 packets (including the layer 2 header) that the Metering Process did not process since the (re-)initialization of the Metering Process. This Information Element is the layer 2 version of ignoredOctetTotalCount (ElementId #165). octets 1 2014-05-02 notSentLayer2OctetTotalCount unsigned64 totalCounter 427 current The total number of octets in observed layer 2 packets (including the layer 2 header) that the Metering Process did not process since the (re-)initialization of the Metering Process. This Information Element is the layer 2 version of notSentOctetTotalCount (ElementId #168). octets 1 2014-05-02 layer2OctetDeltaSumOfSquares unsigned64 deltaCounter 428 current The sum of the squared numbers of layer 2 octets per incoming packet since the previous report (if any) for this Flow at the Observation Point. The number of octets includes layer 2 header(s) and layer 2 payload. This Information Element is the layer 2 version of octetDeltaSumOfSquares (ElementId #198). octets 1 2014-05-02 layer2OctetTotalSumOfSquares unsigned64 totalCounter 429 current The total sum of the squared numbers of layer 2 octets in incoming packets for this Flow at the Observation Point since the Metering Process (re-)initialization for this Observation Point. The number of octets includes layer 2 header(s) and layer 2 payload. This Information Element is the layer 2 version of octetTotalSumOfSquares (ElementId #199). octets 1 2014-05-02 layer2FrameDeltaCount unsigned64 deltaCounter 430 current The number of incoming layer 2 frames since the previous report (if any) for this Flow at the Observation Point. frames 0 2014-05-02 layer2FrameTotalCount unsigned64 totalCounter 431 current The total number of incoming layer 2 frames for this Flow at the Observation Point since the Metering Process (re-)initialization for this Observation Point. frames 0 2014-05-02 pseudoWireDestinationIPv4Address ipv4Address default 432 current The destination IPv4 address of the PSN tunnel carrying the pseudowire. 0 2014-05-28 ignoredLayer2FrameTotalCount unsigned64 totalCounter 433 current The total number of observed layer 2 frames that the Metering Process did not process since the (re-)initialization of the Metering Process. This Information Element is the layer 2 version of ignoredPacketTotalCount (ElementId #164). frames 0 2014-06-27 mibObjectValueInteger signed32 quantity 434 current An IPFIX Information Element that denotes that the integer value of a MIB object will be exported. The MIB Object Identifier ("mibObjectIdentifier") for this field MUST be exported in a MIB Field Option or via another means. This Information Element is used for MIB objects with the Base syntax of Integer32 and INTEGER with IPFIX reduced-size encoding used as required. The value is encoded as per the standard IPFIX Abstract Data Type of signed32. 1 2017-04-30 mibObjectValueOctetString octetArray default 435 current An IPFIX Information Element that denotes that an Octet String or Opaque value of a MIB object will be exported. The MIB Object Identifier ("mibObjectIdentifier") for this field MUST be exported in a MIB Field Option or via another means. This Information Element is used for MIB objects with the Base syntax of OCTET STRING and Opaque. The value is encoded as per the standard IPFIX Abstract Data Type of octetArray. 0 2015-12-13 mibObjectValueOID octetArray default 436 current An IPFIX Information Element that denotes that an Object Identifier or OID value of a MIB object will be exported. The MIB Object Identifier ("mibObjectIdentifier") for this field MUST be exported in a MIB Field Option or via another means. This Information Element is used for MIB objects with the Base syntax of OBJECT IDENTIFIER. Note: In this case, the "mibObjectIdentifier" defines which MIB object is being exported, and the "mibObjectValueOID" field will contain the OID value of that MIB object. The mibObjectValueOID Information Element is encoded as ASN.1/BER [X.690] in an octetArray. 0 2015-12-13 mibObjectValueBits octetArray flags 437 current An IPFIX Information Element that denotes that a set of Enumerated flags or bits from a MIB object will be exported. The MIB Object Identifier ("mibObjectIdentifier") for this field MUST be exported in a MIB Field Option or via another means. This Information Element is used for MIB objects with the Base syntax of BITS. The flags or bits are encoded as per the standard IPFIX Abstract Data Type of octetArray, with sufficient length to accommodate the required number of bits. If the number of bits is not an integer multiple of octets, then the most significant bits at the end of the octetArray MUST be set to 0. 0 2015-12-13 mibObjectValueIPAddress ipv4Address default 438 current An IPFIX Information Element that denotes that the IPv4 address value of a MIB object will be exported. The MIB Object Identifier ("mibObjectIdentifier") for this field MUST be exported in a MIB Field Option or via another means. This Information Element is used for MIB objects with the Base syntax of IpAddress. The value is encoded as per the standard IPFIX Abstract Data Type of ipv4Address. 0 2015-12-13 mibObjectValueCounter unsigned64 snmpCounter 439 current An IPFIX Information Element that denotes that the counter value of a MIB object will be exported. The MIB Object Identifier ("mibObjectIdentifier") for this field MUST be exported in a MIB Field Option or via another means. This Information Element is used for MIB objects with the Base syntax of Counter32 or Counter64 with IPFIX reduced-size encoding used as required. The value is encoded as per the standard IPFIX Abstract Data Type of unsigned64. 0 2015-12-13 mibObjectValueGauge unsigned32 snmpGauge 440 current An IPFIX Information Element that denotes that the Gauge value of a MIB object will be exported. The MIB Object Identifier ("mibObjectIdentifier") for this field MUST be exported in a MIB Field Option or via another means. This Information Element is used for MIB objects with the Base syntax of Gauge32. The value is encoded as per the standard IPFIX Abstract Data Type of unsigned32. This value represents a non-negative integer that may increase or decrease but that shall never exceed a maximum value or fall below a minimum value. 0 2015-12-13 mibObjectValueTimeTicks unsigned32 quantity 441 current An IPFIX Information Element that denotes that the TimeTicks value of a MIB object will be exported. The MIB Object Identifier ("mibObjectIdentifier") for this field MUST be exported in a MIB Field Option or via another means. This Information Element is used for MIB objects with the Base syntax of TimeTicks. The value is encoded as per the standard IPFIX Abstract Data Type of unsigned32. 1 2017-04-30 mibObjectValueUnsigned unsigned32 quantity 442 current An IPFIX Information Element that denotes that an unsigned integer value of a MIB object will be exported. The MIB Object Identifier ("mibObjectIdentifier") for this field MUST be exported in a MIB Field Option or via another means. This Information Element is used for MIB objects with the Base syntax of unsigned32 with IPFIX reduced-size encoding used as required. The value is encoded as per the standard IPFIX Abstract Data Type of unsigned32. 1 2017-04-30 mibObjectValueTable subTemplateList list 443 current An IPFIX Information Element that denotes that a complete or partial conceptual table will be exported. The MIB Object Identifier ("mibObjectIdentifier") for this field MUST be exported in a MIB Field Option or via another means. This Information Element is used for MIB objects with a syntax of SEQUENCE OF. This is encoded as a subTemplateList of mibObjectValue Information Elements. The Template specified in the subTemplateList MUST be an Options Template and MUST include all the objects listed in the INDEX clause as Scope Fields. 1 2017-04-30 mibObjectValueRow subTemplateList list 444 current An IPFIX Information Element that denotes that a single row of a conceptual table will be exported. The MIB Object Identifier ("mibObjectIdentifier") for this field MUST be exported in a MIB Field Option or via another means. This Information Element is used for MIB objects with a syntax of SEQUENCE. This is encoded as a subTemplateList of mibObjectValue Information Elements. The subTemplateList exported MUST contain exactly one row (i.e., one instance of the subTemplate). The Template specified in the subTemplateList MUST be an Options Template and MUST include all the objects listed in the INDEX clause as Scope Fields. 0 2015-12-13 mibObjectIdentifier octetArray default 445 current An IPFIX Information Element that denotes that a MIB Object Identifier (MIB OID) is exported in the (Options) Template Record. The mibObjectIdentifier Information Element contains the OID assigned to the MIB object type definition encoded as ASN.1/BER [X.690]. 0 2015-12-13 mibSubIdentifier unsigned32 identifier 446 current A non-negative sub-identifier of an Object Identifier (OID). 0 2015-12-13 mibIndexIndicator unsigned64 flags 447 current A set of bit fields that is used for marking the Information Elements of a Data Record that serve as INDEX MIB objects for an indexed columnar MIB object. Each bit represents an Information Element in the Data Record, with the n-th least significant bit representing the n-th Information Element. A bit set to 1 indicates that the corresponding Information Element is an index of the columnar object represented by the mibObjectValue. A bit set to 0 indicates that this is not the case. If the Data Record contains more than 64 Information Elements, the corresponding Template SHOULD be designed such that all index fields are among the first 64 Information Elements, because the mibIndexIndicator only contains 64 bits. If the Data Record contains less than 64 Information Elements, then the extra bits in the mibIndexIndicator for which no corresponding Information Element exists MUST have the value 0 and must be disregarded by the Collector. This Information Element may be exported with IPFIX reduced-size encoding. 0 2015-12-13 mibCaptureTimeSemantics unsigned8 identifier 448 current Indicates when in the lifetime of the Flow the MIB value was retrieved from the MIB for a mibObjectIdentifier. This is used to indicate if the value exported was collected from the MIB closer to Flow creation or Flow export time and refers to the Timestamp fields included in the same Data Record. This field SHOULD be used when exporting a mibObjectValue that specifies counters or statistics. If the MIB value was sampled by SNMP prior to the IPFIX Metering Process or Exporting Process retrieving the value (i.e., the data is already stale) and it is important to know the exact sampling time, then an additional observationTime* element should be paired with the OID using IPFIX Structured Data . Similarly, if different MIB capture times apply to different mibObjectValue elements within the Data Record, then individual mibCaptureTimeSemantics Information Elements should be paired with each OID using IPFIX Structured Data. Values are listed in the "mibCaptureTimeSemantics (Value 448)" registry. See the "mibCaptureTimeSemantics (Value registry 448)" . 0 2015-12-13 mibContextEngineID octetArray default 449 current A mibContextEngineID that specifies the SNMP engine ID for a MIB field being exported over IPFIX. Definition as per , Section 3.3. 0 2015-12-13 mibContextName string default 450 current An Information Element that denotes that a MIB context name is specified for a MIB field being exported over IPFIX. Reference , Section 3.3. 0 2015-12-13 mibObjectName string default 451 current The name (called a descriptor in of an object type definition. 0 2015-12-13 mibObjectDescription string default 452 current The value of the DESCRIPTION clause of a MIB object type definition. 0 2015-12-13 mibObjectSyntax string default 453 current The value of the SYNTAX clause of a MIB object type definition, which may include a textual convention or sub-typing. See . 0 2015-12-13 mibModuleName string default 454 current The textual name of the MIB module that defines a MIB object. 0 2015-12-13 mobileIMSI string default 455 current The International Mobile Subscription Identity (IMSI). The IMSI is a decimal digit string with up to a maximum of 15 ASCII/UTF-8 encoded digits (0x30 - 0x39). 3GPP TS 23.003 Section 3 and ITU-T E.164. 0 2015-12-15 mobileMSISDN string default 456 current The Mobile Station International Subscriber Directory Number (MSISDN). The MSISDN is a decimal digit string with up to a maximum of 15 ASCII/UTF-8 encoded digits (0x30 - 0x39). 3GPP TS 23.003 Section 3 and ITU-T E.164. 0 2015-12-15 httpStatusCode unsigned16 identifier 457 current The HTTP Response Status Code, as defined in section 6 of , associated with a flow. Implies that the flow record represents a flow containing an HTTP Response. 0-999 0 2016-04-28 sourceTransportPortsLimit unsigned16 quantity 458 current This Information Element contains the maximum number of IP source transport ports that can be used by an end user when sending IP packets; each user is associated with one or more (source) IPv4 or IPv6 addresses. This Information Element is particularly useful in address-sharing deployments that adhere to REQ-4 of . Limiting the number of ports assigned to each user ensures fairness among users and mitigates the denial-of-service attack that a user could launch against other users through the address-sharing device in order to grab more ports. ports 1-65535 1 2017-08-01 httpRequestMethod string 459 current The HTTP request method, as defined in section 4 of , associated with a flow. String with up to 8 UTF-8 characters. 0 2016-11-15 httpRequestHost string 460 current The HTTP request host, as defined in section 5.4 of or, in the case of HTTP/2, the content of the :authority pseudo-header field as defined in section 8.1.2.3 of . Encoded in UTF-8. 0 2016-11-15 httpRequestTarget string 461 current The HTTP request target, as defined in section 2 of and in section 5.3 of , associated with a flow. Or the HTTP/2 ":path" pseudo-header field as defined in section 8.1.2.3 of . Encoded in UTF-8. 0 2016-11-15 httpMessageVersion string 462 current The version of an HTTP/1.1 message as indicated by the HTTP-version field, defined in section 2.6 of , or the version identification of an HTTP/2 frame as defined in section 3.1. The length of this field is limited to 10 characters, UTF-8 encoded. 0 2016-11-15 natInstanceID unsigned32 identifier 463 current This Information Element uniquely identifies an Instance of the NAT that runs on a NAT middlebox function after the packet passes the Observation Point. natInstanceID is defined in . See for the definition of the IPv4 source address field. See for the definition of NAT. See for the definition of middleboxes. 0 2017-03-15 internalAddressRealm octetArray identifier 464 current This Information Element represents the internal address realm where the packet is originated from or destined to. By definition, a NAT mapping can be created from two address realms, one from internal and one from external. Realms are implementation dependent and can represent a Virtual Routing and Forwarding (VRF) ID, a VLAN ID, or some unique identifier. Realms are optional and, when left unspecified, would mean that the external and internal realms are the same. See for the definition of the IPv4 source address field. See for the definition of NAT. See for the definition of middleboxes. 0 2017-03-15 externalAddressRealm octetArray identifier 465 current This Information Element represents the external address realm where the packet is originated from or destined to. See the internalAddressRealm IE for the detailed definition. See for the definition of the IPv4 source address field. See for the definition of NAT. See for the definition of middleboxes. 0 2017-03-15 natQuotaExceededEvent unsigned32 identifier 466 current This Information Element identifies the type of a NAT Quota Exceeded event. Values for this Information Element are listed in the "NAT Quota Exceeded Event Type (Value 466)" registry. See the "NAT Quota Exceeded Event Type (Value 466)" registry . See for the definition of NAT. 0 2017-03-15 natThresholdEvent unsigned32 identifier 467 current This Information Element identifies a type of a NAT Threshold event. Values for this Information Element are listed in the "NAT Threshold Event Type (Value 467)" registry. See the "NAT Threshold Event Type (Value 467)" registry . See for the definition of NAT. 0 2017-03-15 httpUserAgent string default 468 current The HTTP User-Agent header field as defined in section 5.5.3 of . Encoded in UTF-8. 0 2017-04-19 httpContentType string default 469 current The HTTP Content-Type header field as defined in section 3.1.1.5 of . Encoded in UTF-8. 0 2017-04-19 httpReasonPhrase string default 470 current The HTTP reason phrase as defined in section 6.1 of of . 0 2017-06-19 maxSessionEntries unsigned32 identifier 471 current This element represents the maximum session entries that can be created by the NAT device. See for the definition of NAT. See for the definition of middleboxes. 0 2017-12-01 maxBIBEntries unsigned32 identifier 472 current This element represents the maximum BIB entries that can be created by the NAT device. See for the definition of NAT. See for the definition of middleboxes. 0 2017-12-01 maxEntriesPerUser unsigned32 identifier 473 current This element represents the maximum NAT entries that can be created per user by the NAT device. See for the definition of NAT. See for the definition of middleboxes. 0 2017-12-01 maxSubscribers unsigned32 identifier 474 current This element represents the maximum subscribers or maximum hosts that are allowed by the NAT device. See for the definition of NAT. See for the definition of middleboxes. 0 2017-12-01 maxFragmentsPendingReassembly unsigned32 identifier 475 current This element represents the maximum fragments that the NAT device can store for reassembling the packet. See for the definition of NAT. See for the definition of middleboxes. 0 2017-12-01 addressPoolHighThreshold unsigned32 identifier 476 current This element represents the high threshold value of the number of public IP addresses in the address pool. See for the definition of NAT. See for the definition of middleboxes. 0 2017-12-01 addressPoolLowThreshold unsigned32 identifier 477 current This element represents the low threshold value of the number of public IP addresses in the address pool. See for the definition of NAT. See for the definition of middleboxes. 0 2017-12-01 addressPortMappingHighThreshold unsigned32 identifier 478 current This element represents the high threshold value of the number of address and port mappings. See for the definition of NAT. See for the definition of middleboxes. 0 2017-12-01 addressPortMappingLowThreshold unsigned32 identifier 479 current This element represents the low threshold value of the number of address and port mappings. See for the definition of NAT. See for the definition of middleboxes. 0 2017-12-01 addressPortMappingPerUserHighThreshold unsigned32 identifier 480 current This element represents the high threshold value of the number of address and port mappings that a single user is allowed to create on a NAT device. See for the definition of NAT. See for the definition of middleboxes. 0 2017-12-01 globalAddressMappingHighThreshold unsigned32 identifier 481 current This element represents the high threshold value of the number of address and port mappings that a single user is allowed to create on a NAT device in a paired address pooling behavior. See for the definition of NAT. See for the definition of middleboxes. See for the definition of paired address pooling behavior. 0 2017-12-01 vpnIdentifier octetArray default 482 current VPN ID in the format specified by . The size of this Information Element is 7 octets. 0 2018-07-10 bgpCommunity unsigned32 identifier 483 current BGP community as defined in 0 2019-01-18 bgpSourceCommunityList basicList list 484 current basicList of zero or more bgpCommunity IEs, containing the BGP communities corresponding with source IP address of a specific flow 0 2019-01-18 bgpDestinationCommunityList basicList list 485 current basicList of zero or more bgpCommunity IEs, containing the BGP communities corresponding with destination IP address of a specific flow 0 2019-01-18 bgpExtendedCommunity octetArray default 486 current BGP Extended Community as defined in ; the size of this IE MUST be 8 octets 0 2019-01-18 bgpSourceExtendedCommunityList basicList list 487 current basicList of zero or more bgpExtendedCommunity IEs, containing the BGP Extended Communities corresponding with source IP address of a specific flow 0 2019-01-18 bgpDestinationExtendedCommunityList basicList list 488 current basicList of zero or more bgpExtendedCommunity IEs, containing the BGP Extended Communities corresponding with destination IP address of a specific flow 0 2019-01-18 bgpLargeCommunity octetArray default 489 current BGP Large Community as defined in ; the size of this IE MUST be 12 octets. 0 2019-01-18 bgpSourceLargeCommunityList basicList list 490 current basicList of zero or more bgpLargeCommunity IEs, containing the BGP Large Communities corresponding with source IP address of a specific flow 0 2019-01-18 bgpDestinationLargeCommunityList basicList list 491 current basicList of zero or more bgpLargeCommunity IEs, containing the BGP Large Communities corresponding with destination IP address of a specific flow 0 2019-01-18 srhFlagsIPv6 unsigned8 flags 492 current The 8-bit Flags field defined in the SRH (Section 2 of ). Assigned flags and their meanings are provided in the "Segment Routing Header Flags" IANA registry. See the assignments in the "Segment Routing Header Flags" registry at . See also for the SRH specification. 0 2023-06-08 srhTagIPv6 unsigned16 identifier 493 current The 16-bit Tag field defined in the SRH (Section 2 of ). A tag is used to mark a packet as part of a class or group of packets sharing the same set of properties. See Section 2 of for more details about the Tag. 0 2023-06-08 srhSegmentIPv6 ipv6Address default 494 current The 128-bit IPv6 address that represents an SRv6 segment. Specified in Section 1 of and mentioned in "Segment List" in Section 2 of . 0 2023-06-08 srhActiveSegmentIPv6 ipv6Address default 495 current The 128-bit IPv6 address that represents the active SRv6 segment. See Section 2 of for the definition of "active segment". 0 2023-06-08 srhSegmentIPv6BasicList basicList list 496 current The ordered basicList of zero or more 128-bit IPv6 addresses in the SRH that represents the SRv6 Segment List. As specified in Section 2 of , the Segment List is encoded starting from the last segment of the SR Policy. That is, the first element of the Segment List (Segment List[0]) contains the last segment of the SR Policy, the second element contains the penultimate segment of the SR Policy, and so on. See Section 2 of for more details about the SRv6 Segment List. 0 2023-06-08 srhSegmentIPv6ListSection octetArray default 497 current The SRv6 Segment List as defined in Section 2 of as a series of octets in IPFIX. See Section 2 of for more details about the SRv6 Segment List. 0 2023-06-08 srhSegmentsIPv6Left unsigned8 quantity 498 current The 8-bit unsigned integer defining the number of segments remaining to reach the end of the Segment List from the SRH. Specified by the "Segments Left" field in Section 4.4 of and mentioned in Section 2 of . 0 2023-06-08 srhIPv6Section octetArray default 499 current The SRH and its TLVs as defined in Section 2 of as a series of octets in IPFIX. See Section 2 of for more details about the structure of an SRH. 0 2023-06-08 srhIPv6ActiveSegmentType unsigned8 identifier 500 current The designator of the routing protocol or PCEP extension where the active SRv6 segment has been learned from. Values for this Information Element are listed in the "IPFIX IPv6 SRH Segment Type (Value 500)” subregistry; see . See the assigned types in the "IPFIX IPv6 SRH Segment (Value 500)" registry at . 0 2023-06-08 srhSegmentIPv6LocatorLength unsigned8 default 501 current The length of the SRH segment IPv6 locator specified as the number of significant bits. Together with srhSegmentIPv6, it enables the calculation of the SRv6 Locator. See Section 3.1 of for more details about the SID format. 1 2024-01-22 srhSegmentIPv6EndpointBehavior unsigned16 identifier 502 current The 16-bit unsigned integer that represents an SRv6 Endpoint behavior as per Section 4 of . Assigned values and their meanings are provided in the "SRV6 Endpoint Behaviors" registry. See the assigned behaviors in the "SRv6 Endpoint Behaviors" registry at . See Section 4 of for more details about the processing of endpoint behaviors. 0 2023-06-08 transportChecksum unsigned16 default 503 current The checksum in the transport header. For the transport protocols UDP and TCP, this is the checksum given in the respective header. This field MAY also be used for future transport protocols that have 16-bit checksum values. See for the definition of the UDP checksum field. See for the definition of the TCP checksum field. 0 2024-03-27 icmpHeaderPacketSection octetArray default 504 current This Information Element carries a series of n octets from the ICMP header of a sampled packet, starting sectionOffset octets into the ICMP header. However, if no sectionOffset field corresponding to this Information Element is present, then a sectionOffset of zero applies, and the octets MUST be from the start of the ICMP header. With sufficient length, this element also reports octets from the ICMP payload. However, full packet capture of arbitrary packet streams is explicitly out of scope per the Security Considerations sections of and . The sectionExportedOctets expresses how much data was exported, while the remainder is padding. When the sectionExportedOctets field corresponding to this Information Element exists, this Information Element MAY have a fixed length and MAY be padded, or it MAY have a variable length. When the sectionExportedOctets field corresponding to this Information Element does not exist, this Information Element SHOULD have a variable length and MUST NOT be padded. In this case, the size of the exported section may be constrained due to limitations in the IPFIX protocol. See for the definition of the IPv4 ICMP header. See for the definition of the IPv6 ICMP header. 0 2024-03-27 gtpuFlags unsigned8 flags 505 current 8-bit flags field indicating the version of GTP-U protocol, protocol type and presence of extension header, sequence number and N-PDU number defined in Section 5.1 of the 3GPP specification TS.29281. Refer to section 5.1 of the 3GPP specification TS.29281. 0 2024-04-12 gtpuMsgType unsigned8 identifier 506 current 8-bit Message type field indicating the type of GTP-U message defined in section 5.1 of the 3GPP specification TS.29281. Refer to section 5.1 of the 3GPP specification TS.29281. 0 2024-04-12 gtpuTEid unsigned32 identifier 507 current 32-bit tunnel endpoint identifier field defined in section 5.1 of the 3GPP specification TS.29281. This field unambiguously identifies a tunnel endpoint in the receiving GTP-U protocol entity for a given UDP/IP endpoint. The receiving side of a GTP tunnel locally assigns the TEID value the transmitting side has to use. The TEID values are exchanged between tunnel endpoints using control plane messages. Refer to section 5.1 of the 3GPP specification TS.29281. 0 2024-04-12 gtpuSequenceNum unsigned16 identifier 508 current 16-bit sequence number field defined in section 5.1 (Optional Fields) of the 3GPP specification TS.29281. Refer to section 5.1 of the 3GPP specification TS.29281. 0 2024-04-12 gtpuQFI unsigned8 identifier 509 current 6-bit QoS flow identifier field defined in PDU Session Container extension header of GTP-U. This is defined in section 5.5.3.3 of the 3GPP specification TS.38415. This is used to determine the QoS flow and QoS profile which are associated with the received packet. The basic encoding is 8 bits. The layout of basic encoding is as follows: MSB - 0 1 2 3 4 5 6 7 - LSB +----+----+----+----+----+----+----+----+ |Reserved | 6 bit QFI value | +----+----+----+----+----+----+----+----+ Examples: value : 0x08 binary: 00001000 decode: 001000 - QFI value value : 0x3e binary: 00111110 decode: 111110 - QFI value Refer to section 5.5.3.3 of the 3GPP specification TS.38415 and section 5.7.1.1 from 3GPP specification TS.23501 for additional details. 0 2024-04-12 gtpuPduType unsigned8 identifier 510 current 4-bit PDU type field defined in PDU Session Container extension header of GTP-U. This is defined in section 5.5.3 of the 3GPP specification TS.38415. This field indicates the structure of the PDU session user plane frame. The basic encoding is 8 bits. The layout of basic encoding is as follows: MSB - 0 1 2 3 4 5 6 7 - LSB +----+----+----+----+----+----+----+----+ | Reserved | 4 bit PDU Type | +----+----+----+----+----+----+----+----+ Examples: value : 0x01 binary: 00000001 decode: 0001 - PDU Type value Refer to section 5.5.3 of the 3GPP specification TS.38415. 0 2024-04-12 bgpSourceAsPathList basicList list 511 current Ordered basicList of zero or more bgpSourceAsNumber elements, containing the BGP as-path corresponding with the source IP address of a specific flow. See for a description of BGP-4, and see for the definition of the AS number. 0 2024-05-24 bgpDestinationAsPathList basicList list 512 current Ordered basicList of zero or more bgpDestinationAsNumber elements, containing the BGP as-path corresponding with the destination IP address of a specific flow. See for a description of BGP-4, and see for the definition of the AS number. 0 2024-05-24 ipv6ExtensionHeaderType unsigned8 identifier 513 current Type of an IPv6 extension header observed in at least one packet of this Flow. See the "IPv6 Extension Header Types" registry at IANA-EH. See Section 4 of for the general definition of IPv6 extension headers. 0 2024-10-07 ipv6ExtensionHeaderCount unsigned8 totalCounter 514 current The number of consecutive occurrences of the same extension header type in a Flow. This IE is reported, e.g., in the ipv6ExtensionHeaderTypeCountList IE. The type of the extension header is provided in the ipv6ExtensionHeaderType IE. See the "IPv6 Extension Header Types" registry at IANA-EH. See Section 4 of for the general definition of IPv6 extension headers. 0 2024-10-07 ipv6ExtensionHeadersFull unsigned256 flags 515 current IPv6 extension headers observed in packets of this Flow. The information is encoded in a set of bit fields. For each IPv6 extension header, there is a bit in this set. The bit is set to 1 if any observed packet of this Flow contains the corresponding IPv6 extension header. Otherwise, if no observed packet of this Flow contains the respective IPv6 extension header, the value of the corresponding bit is 0. The IPv6 extension header associated with each bit is provided in IANA-IPFIX-IPv6EH. Bit 0 corresponds to the least significant bit (LSB) in the ipv6ExtensionHeadersFull IE, while bit 255 corresponds to the most significant bit (MSB) of the IE. In doing so, few octets will be needed to encode common IPv6 extension headers when observed in a Flow. The "No Next Header" (bit 2) value (Section 4.7 of ) is used if there is no upper-layer header in an IPv6 packet. Even if the value is not considered as an extension header as such, the corresponding bit is set in the ipv6ExtensionHeadersFull IE whenever that value is encountered in the Flow. Extension headers observed in a Flow with varying extension header chains MUST NOT be grouped in the ipv6ExtensionHeadersFull IE if the ipv6ExtensionHeaderChainLengthList IE is also present. If the ipv6ExtensionHeaderChainLengthList IE is not present, then extension headers observed in a Flow with varying extension header chains MAY be grouped in one single ipv6ExtensionHeadersFull IE or be exported in separate ipv6ExtensionHeadersFull IEs, one for each extension header chain. The ipv6ExtensionHeadersFull IE MUST NOT be exported if ipv6ExtensionHeaderTypeCountList IE is also present because of the overlapping scopes of these two IEs. The value of ipv6ExtensionHeadersFull IE may be encoded in fewer octets per the guidelines in Section 6.2 of See the "IPFIX ipv6ExtensionHeaders Bits" registry at IANA-IPFIX-IPv6EH. See the "IPv6 Extension Header Types" registry at IANA-EH. See Section 4 of for the general definition of IPv6 extension headers. The ipv6ExtensionHeadersFull IE deprecates the ipv6ExtensionHeaders IE (64) that was initially defined in . obsoletes and specifies that IANA-IPFIX is the normative reference for the ipv6ExtensionHeaders IE (64). 0 2024-10-07 ipv6ExtensionHeaderTypeCountList subTemplateList list 516 current As per Section 4.1 of , IPv6 nodes must accept and attempt to process extension headers occurring any number of times in the same packet. This IE echoes the order of extension headers and number of onsecutive occurrences of the same extension header type in a Flow. This IE is a subTemplateList of ipv6ExtensionHeaderType and ipv6ExtensionHeaderCount IEs. Each header chain in a Flow with varying extension header chains MUST be exported in a separate IE. The same extension header type may appear several times in an ipv6ExtensionHeaderTypeCountList IE. For example, if an IPv6 packet of a Flow includes a Hop-by-Hop Options header, a Destination Options header, a Fragment header, and a Destination Options header, the ipv6ExtensionHeaderTypeCountList IE will report: * the count of Hop-by-Hop Options headers, * the occurrences of the Destination Options headers that are observed before a Fragment header, * the occurrences of the Fragment headers, and * the occurrences of the Destination Options headers that are observed right after a Fragment header. If an implementation determines that an observed packet of a Flow includes an extension header (including an extension header that it does not support), then the exact observed code of that extension header MUST be echoed in the ipv6ExtensionHeaderTypeCountList IE. How an implementation disambiguates between unknown upper-layer protocols vs. extension headers is not IPFIX-specific. Refer, for example, to Section 2.2 of for a behavior of an intermediate node that encounters an unknown Next Header type. See the "IPv6 Extension Header Types" registry at IANA-EH. See Section 4 of for the general definition of IPv6 extension headers. 0 2024-10-07 ipv6ExtensionHeadersLimit boolean default 517 current When set to "false", this IE indicates that the exported extension header information (e.g., ipv6ExtensionHeadersFull or ipv6ExtensionHeaderTypeCountList) does not match the full enclosed extension headers, but only up to a limit that is typically set by hardware or software. When set to "true", this IE indicates that the exported extension header information matches the full enclosed extension headers. See Section 4 of for the general definition of IPv6 extension headers. See for an example of IPv6 packet processing due to limits on extension headers. 0 2024-10-07 ipv6ExtensionHeadersChainLength unsigned32 identifier 518 current In theory, there are no limits on the number of IPv6 extension headers that may be present in a packet other than the path MTU. However, it was regularly reported that IPv6 packets with extension headers were often dropped in the Internet (e.g., ). As discussed in Section 1.2 of , some hardware devices implement a parsing buffer of a fixed size to process packets, including all the headers. When the aggregate length of headers of an IPv6 packet exceeds that size, the packet will be discarded or deferred to a slow path. The ipv6ExtensionHeadersChainLength IE is used to report, in octets, the length of an extension header chain observed in a Flow. The length is the sum of the lengths of all extension headers of the chain. Exporting such information might help identifying root causes of performance degradation, including packet drops. Each header chain length of a Flow with varying extension header chains MUST be exported in a separate ipv6ExtensionHeadersChainLength IE. See Section 4 of for the general definition of IPv6 extension headers. See for an overview of operational implications of IPv6 packets with extension headers. 0 2024-10-07 ipv6ExtensionHeaderChainLengthList subTemplateList list 519 current This IE is used to report the chains and their lengths as observed in a Flow with varying extension header chains. This IE is a subTemplateList of ipv6ExtensionHeadersFull and ipv6ExtensionHeadersChainLength IEs. If several extension header chains are observed in a Flow, each header chain MUST be exported in a separate ipv6ExtensionHeaderChainLengthList IE. See the "IPv6 Extension Header Types" registry at IANA-EH. See Section 4 of for the general definition of IPv6 extension headers. 0 2024-10-07 tcpOptionsFull unsigned256 flags 520 current TCP options in packets of this Flow. The information is encoded in a set of bit fields. For each TCP option, there is a bit in this set. The bit is set to 1 if any observed packet of this Flow contains the corresponding TCP option. Otherwise, if no observed packet of this Flow contains the respective TCP option, the value of the corresponding bit is 0. Options are mapped to bits according to their option numbers. TCP option Kind 0 corresponds to the least significant bit in the tcpOptionsFull IE, while Kind 255 corresponds to the most significant bit of the IE. This approach allows an observer to export any observed TCP option even if it does not support that option and without requiring updating a mapping table. The value of tcpOptionsFull IE may be encoded in fewer octets per the guidelines in Section 6.2 of . The presence of tcpSharedOptionExID16List or tcpSharedOptionExID32List IEs is an indication that a shared TCP option (Kind=253 or 254) is observed in a Flow. The presence of tcpSharedOptionExID16List or tcpSharedOptionExID32List IEs takes precedence over setting the corresponding bits in the tcpOptionsFull IE for the same Flow. In order to optimize the use of the reduced-size encoding in the presence of tcpSharedOptionExID16List or tcpSharedOptionExID32List IEs, the Exporter MUST NOT set to 1 the shared TCP options (Kind=253 or 254) flags of the tcpOptionsFull IE that is reported for the same Flow. See the "TCP Option Kind Numbers" registry at IANA-TCP. See for the general definition of TCP options. The tcpOptionsFull IE deprecates the tcpOptions IE (209) that was initially defined in . obsoletes and specifies that IANA-IPFIX is the normative reference for the tcpOptions IE (209). 0 2024-10-07 tcpSharedOptionExID16 unsigned16 identifier 521 current Reports an observed 2-byte ExID in a shared TCP option (Kind=253 or 254) in a Flow. A basicList of tcpSharedOptionExID16 is used to report tcpSharedOptionExID16List values. See the "TCP/UDP Experimental Option Experiment Identifiers (TCP/UDP ExIDs)" registry at IANA_TCP-UDP_ExIDs. See for the general definition of TCP options. See for the shared use of experimental TCP Options. 0 2024-10-07 tcpSharedOptionExID32 unsigned32 identifier 522 current Reports an observed 4-byte ExID in a shared TCP option (Kind=253 or 254) in a Flow. A basicList of tcpSharedOptionExID32 is used to report tcpSharedOptionExID32List values. See the "TCP/UDP Experimental Option Experiment Identifiers (TCP/UDP ExIDs)" registry at IANA_TCP-UDP_ExIDs. See for the general definition of TCP options. See for the shared use of experimental TCP Options. 0 2024-10-07 tcpSharedOptionExID16List basicList list 523 current Reports observed 2-byte ExIDs in shared TCP options (Kind=253 or 254) in a Flow. A basicList of tcpSharedOptionExID16 IEs in which each tcpSharedOptionExID16 IE carries an observed 2-byte ExID in a shared option. See the "TCP/UDP Experimental Option Experiment Identifiers (TCP/UDP ExIDs)" registry at IANA_TCP-UDP_ExIDs. See for the general definition of TCP options. See for the shared use of experimental TCP Options. 0 2024-10-07 tcpSharedOptionExID32List basicList list 524 current Reports observed 4-byte ExIDs in shared TCP options (Kind=253 or 254) in a Flow. A basicList of tcpSharedOptionExID32 IEs in which each tcpSharedOptionExID32 IE carries an observed 4-byte ExID in a shared option. See the "TCP/UDP Experimental Option Experiment Identifiers (TCP/UDP ExIDs)" registry at IANA_TCP-UDP_ExIDs. See for the general definition of TCP options. See for the shared use of experimental TCP Options. 0 2024-10-07 udpSafeOptions unsigned256 flags 525 current Observed SAFE UDP options in a Flow. The information is encoded in a set of bit fields. Options are mapped to bits according to their option numbers. UDP option Kind 0 corresponds to the least significant bit in the udpSafeOptions IE, while Kind 191 corresponds to the 65th most significant bit of the IE. The bit is set to 1 if the corresponding SAFE UDP option is observed at least once in the Flow. The bit is set to 0 if the option is never observed in the Flow. The 64 most significant bits MUST be set to 0. The reduced-size encoding per Section 6.2 of is followed whenever fewer octets are needed to report observed SAFE UDP options. For example, if only option Kinds <= 31 are observed, then the value of the udpSafeOptions IE can be encoded as unsigned32, or if only option Kinds <= 63 are observed, then the value of the udpSafeOptions IE can be encoded as unsigned64. The presence of udpSafeExIDList is an indication that the SAFE Experimental Option is observed in a Flow. The presence of udpSafeExIDList takes precedence over setting the corresponding bit in the udpSafeOptions IE for the same Flow. In order to optimize the use of the reduced-size encoding in the presence of udpSafeExIDList IE, the Exporter MUST NOT set the EXP flag of the udpSafeOptions IE that is reported for the same Flow to 1. See the "UDP Option Kind Numbers" registry at UDP_OPTIONS. See for more details about UDP options. 0 2024-10-23 udpUnsafeOptions unsigned64 flags 526 current Observed UNSAFE UDP options in a Flow. The information is encoded in a set of bit fields. Options are mapped to bits according to their option numbers. UDP option Kind 192 corresponds to the least significant bit in the udpUnsafeOptions IE, while Kind 255 corresponds to the most significant bit of the IE. The bit is set to 1 if the corresponding UNSAFE UDP option is observed at least once in the Flow. The bit is set to 0 if the option is never observed in the Flow. The reduced-size encoding per Section 6.2 of is followed whenever fewer octets are needed to report observed UNSAFE UDP options. The presence of udpUnsafeExIDList is an indication that the UNSAFE Experimental Option is observed in a Flow. The presence of udpUnsafeExIDList takes precedence over setting the corresponding bit in the udpUnsafeOptions IE for the same Flow. In order to optimize the use of the reduced-size encoding in the presence of udpUnsafeExIDList IE, the Exporter MUST NOT set the UEXP flag of the udpUnsafeOptions IE that is reported for the same Flow to 1. See the "UDP Option Kind Numbers" registry at UDP_OPTIONS. See for more details about UDP options. 0 2024-10-23 udpExID unsigned16 identifier 527 current Observed ExID in an Experimental (EXP, Kind=127) Option or an UNSAFE Experimental (UEXP, Kind=254) Option. A basicList of udpExID is used to report udpSafeExIDList and udpUnsafeExIDList values. See the "TCP/UDP Experimental Option Experiment Identifiers (TCP/UDP ExIDs)" registry at UDP_ExIDs. See for more details about ExIDs. 0 2024-10-23 udpSafeExIDList basicList list 528 current Observed ExIDs in the Experimental (EXP, Kind=127) Option. A basicList of udpExID Information Elements in which each udpExID Information Element carries the ExID observed in an EXP Option. See the "TCP/UDP Experimental Option Experiment Identifiers (TCP/UDP ExIDs)" registry at UDP_ExIDs. See for more details about ExIDs. 0 2024-10-23 udpUnsafeExIDList basicList list 529 current Observed ExIDs in the UNSAFE Experimental (UEXP, Kind=254) Option. A basicList of udpExID Information Elements in which each udpExID Information Element carries the ExID observed in an UEXP Option. See the "TCP/UDP Experimental Option Experiment Identifiers (TCP/UDP ExIDs)" registry at UDP_ExIDs. See for more details about ExIDs. 0 2024-10-23 pathDelayMeanDeltaMicroseconds unsigned32 deltaCounter 530 current This Information Element identifies the mean path delay of all packets in the Flow, in microseconds, between an OAM header encapsulating node and the local node with the OAM domain (either an OAM header transit node or an OAM header decapsulating node), according to OWDelay_HybridType1_IP_RFC9951_Seconds_Mean in the IANA Performance Metric Registry. OWDelay_HybridType1_IP_RFC9951_Seconds_Mean in the IANA Performance Metric registry. 0 2026-04-02 pathDelayMinDeltaMicroseconds unsigned32 deltaCounter 531 current This Information Element identifies the lowest path delay of all packets in the Flow, in microseconds, between an OAM header encapsulating node and the local node with the OAM domain (either an OAM header transit node or an OAM header decapsulating node), according to the OWDelay_HybridType1_IP_RFC9951_Seconds_Min in the IANA Performance Metric Registry. OWDelay_HybridType1_IP_RFC9951_Seconds_Min in the IANA Performance Metric registry. 0 2026-04-02 pathDelayMaxDeltaMicroseconds unsigned32 deltaCounter 532 current This Information Element identifies the highest path delay of all packets in the Flow, in microseconds, between an OAM header encapsulating node and the local node with the OAM domain (either an OAM header transit node or an OAM header decapsulating node), according to OWDelay_HybridType1_IP_RFC9951_Seconds_Max in the IANA Performance Metric Registry. OWDelay_HybridType1_IP_RFC9951_Seconds_Max in the IANA Performance Metric registry. 0 2026-04-02 pathDelaySumDeltaMicroseconds unsigned64 deltaCounter 533 current This Information Element identifies the sum of the path delay of all packets in the Flow, in microseconds, between an OAM header encapsulating node and the local node with the OAM domain (either an OAM header transit node or an OAM header decapsulating node), according to OWDelay_HybridType1_IP_RFC9951_Seconds_Sum in the IANA Performance Metric Registry. OWDelay_HybridType1_IP_RFC9951_Seconds_Sum in the IANA Performance Metric registry. 0 2026-04-02 Unassigned 534-32767 Expert Review IE Doctors (Andrew Feren, Brian Trammell, Nevil Brownlee, Paul Aitken) 0 Unknown: The MPLS label type is not known. 1 TE-MIDPT: Any TE tunnel mid-point or tail label 2 Pseudowire: Any PWE3 or Cisco AToM based label 3 VPN: Any label associated with VPN 4 BGP: Any label associated with BGP or BGP routing 5 LDP: Any label associated with dynamically assigned labels using LDP 6 Path Computation Element 7 OSPFv2 Segment Routing 8 OSPFv3 Segment Routing 9 IS-IS Segment Routing 10 BGP Segment Routing Prefix-SID 11-255 Unassigned Expert Review IE Doctors (Andrew Feren, Brian Trammell, Nevil Brownlee, Paul Aitken) 00b Unknown 01b Forwarded 10b Dropped 11b Consumed Expert Review IE Doctors (Andrew Feren, Brian Trammell, Nevil Brownlee, Paul Aitken) 0x00-0x3F Unassigned Expert Review IE Doctors (Andrew Feren, Brian Trammell, Nevil Brownlee, Paul Aitken) 01 000000b 0x40 Unknown 01 000001b 0x41 Fragmented 01 000010b 0x42 Not Fragmented 01 000011b 0x43 Tunneled 01 000100b 0x44 ACL Redirect 0x45-0x7F Unassigned Expert Review IE Doctors (Andrew Feren, Brian Trammell, Nevil Brownlee, Paul Aitken) 10 000000b 0x80 Unknown 10 000001b 0x81 ACL deny 10 000010b 0x82 ACL drop 10 000011b 0x83 Unroutable 10 000100b 0x84 Adjacency 10 000101b 0x85 Fragmentation and DF set 10 000110b 0x86 Bad header checksum 10 000111b 0x87 Bad total Length 10 001000b 0x88 Bad header length 10 001001b 0x89 bad TTL 10 001010b 0x8A Policer 10 001011b 0x8B WRED 10 001100b 0x8C RPF 10 001101b 0x8D For us 10 001110b 0x8E Bad output interface 10 001111b 0x8F Hardware 0x90-0xBF Unassigned Expert Review IE Doctors (Andrew Feren, Brian Trammell, Nevil Brownlee, Paul Aitken) 11 000000b 0xC0 Unknown 11 000001b 0xC1 Punt Adjacency 11 000010b 0xC2 Incomplete Adjacency 11 000011b 0xC3 For us 0xC4-0xFF Unassigned Expert Review IE Doctors (Andrew Feren, Brian Trammell, Nevil Brownlee, Paul Aitken) 0 Invalid. 1 IANA-L3: The Assigned Internet Protocol Number (layer 3 (L3)) is exported in the Selector ID. See . 1 2 PANA-L3: Proprietary layer 3 definition. An enterprise can export its own layer 3 protocol numbers. The Selector ID has a global significance for all devices from the same enterprise. 1 3 IANA-L4: The IANA layer 4 (L4) well-known port number is exported in the Selector ID. See . Note: as an IPFIX flow is unidirectional, it contains the destination port in a flow from the client to the server. 2 4 PANA-L4: Proprietary layer 4 definition. An enterprise can export its own layer 4 port numbers. The Selector ID has global significance for devices from the same enterprise. Example: IPFIX had the port 4739 pre-assigned in the IETF draft for years. While waiting for the RFC and its associated IANA registration, the Selector ID 4739 was used with this PANA-L4. 2 5 Reserved 6 USER-Defined: The Selector ID represents applications defined by the user (using CLI, GUI, etc.) based on the methods described in section 2. The Selector ID has a local significance per device. 3 7 Reserved 8 Reserved 9 Reserved 10 Reserved 11 Reserved 12 PANA-L2: Proprietary layer 2 (L2) definition. An enterprise can export its own layer 2 identifiers. The Selector ID represents the enterprise's unique global layer 2 applications. The Selector ID has a global significance for all devices from the same enterprise. Examples include Cisco Subnetwork Access Protocol (SNAP). 5 13 PANA-L7: Proprietary layer 7 definition. The Selector ID represents the enterprise's unique global ID for the layer 7 applications. The Selector ID has a global significance for all devices from the same enterprise. This Classification Engine Id is used when the application registry is owned by the Exporter manufacturer (referred to as the "enterprise" in ). 3 14 Reserved 15 Reserved 16 Reserved 17 Reserved 18 ETHERTYPE: The Selector ID represents the well- known Ethertype. See . Note that the Ethertype is usually expressed in hexadecimal. However, the corresponding decimal value is used in this Selector ID. 2 19 LLC: The Selector ID represents the well-known IEEE 802.2 Link Layer Control (LLC) Destination Service Access Point (DSAP). See . Note that LLC DSAP is usually expressed in hexadecimal. However, the corresponding decimal value is used in this Selector ID. 1 20 PANA-L7-PEN: Proprietary layer 7 definition, including a Private Enterprise Number (PEN) to identify that the application registry being used is not owned by the Exporter manufacturer or to identify the original enterprise in the case of a mediator or 3rd party device. The Selector ID represents the enterprise unique global ID for the layer 7 applications. The Selector ID has a global significance for all devices from the same enterprise. 3 21 The Selector ID contains an application ID from the Qosmos ixEngine. 4 22 The Selector ID contains a protocol from the ntop nDPI engine. 2 23 R&S ipoque DPI PACE2 engine 2 24 R&S ipoque DPI vPACE engine 2 Expert Review IE Doctors (Andrew Feren, Brian Trammell, Nevil Brownlee, Paul Aitken) 0x00 Reserved 0x01 idle timeout The Flow was terminated because it was considered to be idle. 0x02 active timeout The Flow was terminated for reporting purposes while it was still active, for example, after the maximum lifetime of unreported Flows was reached. 0x03 end of Flow detected The Flow was terminated because the Metering Process detected signals indicating the end of the Flow, for example, the TCP FIN flag. 0x04 forced end The Flow was terminated because of some external event, for example, a shutdown of the Metering Process initiated by a network management application. 0x05 lack of resources The Flow was terminated because of lack of resources available to the Metering Process and/or the Exporting Process. 0x06-0xFF Unassigned Expert Review IE Doctors (Andrew Feren, Brian Trammell, Nevil Brownlee, Paul Aitken) 1 Private 2 Private 3-255 Unassigned Expert Review IE Doctors (Andrew Feren, Brian Trammell, Nevil Brownlee, Paul Aitken) 0 Reserved 1 NAT translation create (Historic) 2 NAT translation delete (Historic) 3 NAT Addresses exhausted 4 NAT44 session create 5 NAT44 session delete 6 NAT64 session create 7 NAT64 session delete 8 NAT44 BIB create 9 NAT44 BIB delete 10 NAT64 BIB create 11 NAT64 BIB delete 12 NAT ports exhausted 13 Quota Exceeded 14 Address binding create 15 Address binding delete 16 Port block allocation 17 Port block de-allocation 18 Threshold Reached Expert Review IE Doctors (Andrew Feren, Brian Trammell, Nevil Brownlee, Paul Aitken) 0 Ignore (invalid) 1 Flow Created 2 Flow Deleted 3 Flow Denied 4 Flow Alert 5 Flow Update 6-255 Unassigned Expert Review IE Doctors (Andrew Feren, Brian Trammell, Nevil Brownlee, Paul Aitken) 0x00 arbitrary Direction was assigned arbitrarily. 0x01 initiator The Biflow Source is the flow initiator, as determined by the Metering Process' best effort to detect the initiator. 0x02 reverseInitiator The Biflow Destination is the flow initiator, as determined by the Metering Process' best effort to detect the initiator. This value is provided for the convenience of Exporting Processes to revise an initiator estimate without re-encoding the Biflow Record. 0x03 perimeter The Biflow Source is the endpoint outside of a defined perimeter. The perimeter's definition is implicit in the set of Biflow Source and Biflow Destination addresses exported in the Biflow Records. 0x04-0xFF Unassigned Expert Review IE Doctors (Andrew Feren, Brian Trammell, Nevil Brownlee, Paul Aitken) 1 Physical port 2 Port channel 3 Vlan 4-255 Unassigned Expert Review IE Doctors (Andrew Feren, Brian Trammell, Nevil Brownlee, Paul Aitken) 0 Undefined The Exporting Process makes no representation as to whether the defined field is anonymized or not. While the Collecting Process MAY assume that the field is not anonymized, it is not guaranteed not to be. This is the default anonymization technique. all all 1 None The values exported are real. all all 2 Precision Degradation/Truncation The values exported are anonymized using simple precision degradation or truncation. The new precision or number of truncated bits is implicit in the exported data, and can be deduced by the Collecting Process. all all 3 Binning The values exported are anonymized into bins. all all 4 Enumeration The values exported are anonymized by enumeration. all timestamps 5 Permutation The values exported are anonymized by permutation. all identifiers 6 Structured Permutation The values exported are anonymized by permutation, preserving bit-level structure as appropriate; this represents prefix-preserving IP address anonymization or structured MAC address anonymization. all 7 Reverse Truncation The values exported are anonymized using reverse truncation. The number of truncated bits is implicit in the exported data, and can be deduced by the Collecting Process. all 8 Noise The values exported are anonymized by adding random noise to each value. non-identifiers counters 9 Offset The values exported are anonymized by adding a single offset to all values. all timestamps 10-65535 Unassigned Expert Review IE Doctors (Andrew Feren, Brian Trammell, Nevil Brownlee, Paul Aitken) 0 unknown 1 NAT44 translated 2 NAT64 translated 3 NAT46 translated 4 IPv4-->IPv4 (no NAT) 5 NAT66 translated 6 IPv6-->IPv6 (no NAT) 7-255 Unassigned Expert Review IE Doctors (Andrew Feren, Brian Trammell, Nevil Brownlee, Paul Aitken) 0 Unspecified The counters for an Original Flow are explicitly not distributed according to any other method defined for this Information Element; use for arbitrary distribution, or distribution algorithms not described by any other codepoint. 1 Start Interval The counters for an Original Flow are added to the counters of the appropriate Aggregated Flow containing the start time of the Original Flow. This should be assumed the default if value distribution information is not available at a Collecting Process for an Aggregated Flow. 2 End Interval The counters for an Original Flow are added to the counters of the appropriate Aggregated Flow containing the end time of the Original Flow. 3 Mid Interval The counters for an Original Flow are added to the counters of a single appropriate Aggregated Flow containing some timestamp between start and end time of the Original Flow. 4 Simple Uniform Distribution Each counter for an Original Flow is divided by the number of time intervals the Original Flow covers (i.e., of appropriate Aggregated Flows sharing the same Flow Key), and this number is added to each corresponding counter in each Aggregated Flow. 5 Proportional Uniform Distribution Each counter for an Original Flow is divided by the number of time units the Original Flow covers, to derive a mean count rate. This mean count rate is then multiplied by the number of time units in the intersection of the duration of the Original Flow and the time interval of each Aggregated Flow. This is like simple uniform distribution, but accounts for the fractional portions of a time interval covered by an Original Flow in the first and last time interval. 6 Simulated Process Each counter of the Original Flow is distributed among the intervals of the Aggregated Flows according to some function the Intermediate Aggregation Process uses based upon properties of Flows presumed to be like the Original Flow. This is essentially an assertion that the Intermediate Aggregation Process has no direct packet timing information but is nevertheless not using one of the other simpler distribution methods. The Intermediate Aggregation Process specifically makes no assertion as to the correctness of the simulation. 7 Direct The Intermediate Aggregation Process has access to the original packet timings from the packets making up the Original Flow, and uses these to distribute or recalculate the counters. 8-255 Unassigned Expert Review IE Doctors (Andrew Feren, Brian Trammell, Nevil Brownlee, Paul Aitken) 0 Unassigned 1 Systematic count-based Sampling flowSamplingInterval, flowSamplingSpacing 2 Systematic time-based Sampling flowSamplingTimeInterval, flowSamplingTimeSpacing 3 Random n-out-of-N Sampling samplingSize, samplingPopulation 4 Uniform probabilistic Sampling samplingProbability 5 Property Match Filtering Information Element Value Range 6 Hash-based Filtering using BOB hashInitialiserValue, hashFlowDomain, hashSelectedRangeMin, hashSelectedRangeMax, hashOutputRangeMin, hashOutputRangeMax 7 Hash-based Filtering using IPSX hashInitialiserValue, hashFlowDomain, hashSelectedRangeMin, hashSelectedRangeMax, hashOutputRangeMin, hashOutputRangeMax 8 Hash-based Filtering using CRC hashInitialiserValue, hashFlowDomain, hashSelectedRangeMin, hashSelectedRangeMax, hashOutputRangeMin, hashOutputRangeMax 9 Flow-state Dependent Intermediate Flow Selection Process No agreed Parameters Expert Review IE Doctors (Andrew Feren, Brian Trammell, Nevil Brownlee, Paul Aitken) 0x0001 IEEE802.3 ETHERNET IEEE Std 802.3-2012 0x0002 IEEE802.11 MAC Frame format IEEE Std 802.11-2012 0x0003-0xFFFF Unassigned Expert Review IE Doctors (Andrew Feren, Brian Trammell, Nevil Brownlee, Paul Aitken) 0 undefined 1 begin The value for the MIB object is captured from the MIB when the Flow is first observed 2 end The value for the MIB object is captured from the MIB when the Flow ends 3 export The value for the MIB object is captured from the MIB at export time 4 average The value for the MIB object is an average of multiple captures from the MIB over the observed life of the Flow 5-255 Unassigned Expert Review IE Doctors (Andrew Feren, Brian Trammell, Nevil Brownlee, Paul Aitken) 0 Reserved 1 Maximum session entries 2 Maximum BIB entries 3 Maximum entries per user 4 Maximum active hosts or subscribers 5 Maximum fragments pending reassembly Expert Review IE Doctors (Andrew Feren, Brian Trammell, Nevil Brownlee, Paul Aitken) 0 Reserved 1 Address pool high threshold event 2 Address pool low threshold event 3 Address and port mapping high threshold event 4 Address and port mapping per user high threshold event 5 Global Address mapping high threshold event Expert Review Thomas Graf, Pierre Francois, IE Doctors (Andrew Feren, Brian Trammell, Nevil Brownlee, Paul Aitken) 0 Unknown 1 Segment Routing Policy 2 Path Computation Element 3 OSPFv3 Segment Routing 4 IS-IS Segment Routing 5 BGP Segment Routing Prefix-SID 6-255 Unassigned Standards Action 0 Reserved 1-8 Reserved (historic) 9 Cisco Systems NetFlow Version 9 (historic) 10 IPFIX 11-65535 Unassigned Standards Action 0-1 Not used (historic) 2 Template Set 3 Options Template Set 4-255 Unassigned 256-65535 Reserved for Data Sets Standards Action 0 octetArray 1 unsigned8 2 unsigned16 3 unsigned32 4 unsigned64 5 signed8 6 signed16 7 signed32 8 signed64 9 float32 10 float64 11 boolean 12 macAddress 13 string 14 dateTimeSeconds 15 dateTimeMilliseconds 16 dateTimeMicroseconds 17 dateTimeNanoseconds 18 ipv4Address 19 ipv6Address 20 basicList 21 subTemplateList 22 subTemplateMultiList 23 unsigned256 24-255 Unassigned Standards Action 0 default 1 quantity 2 totalCounter 3 deltaCounter 4 identifier 5 flags 6 list 7 snmpCounter 8 snmpGauge 9-255 Unassigned Expert Review IE Doctors (Andrew Feren, Brian Trammell, Nevil Brownlee, Paul Aitken) 0 none 1 bits 2 octets 3 packets 4 flows 5 seconds 6 milliseconds 7 microseconds 8 nanoseconds 9 4-octet words For example, for IPv4 header length 10 messages For example, for reliability reporting 11 hops For example, for TTL 12 entries For example, for MPLS label stack 13 frames For example, Layer 2 frames 14 ports 15 inferred The units of the inferred Information Element 16-65535 Unassigned Standards Action 0x00 noneOf The "noneOf" structured data type semantic specifies that none of the elements are actual properties of the Data Record. 0x01 exactlyOneOf The "exactlyOneOf" structured data type semantic specifies that only a single element from the structured data is an actual property of the Data Record. This is equivalent to a logical XOR operation. 0x02 oneOrMoreOf The "oneOrMoreOf" structured data type semantic specifies that one or more elements from the list in the structured data are actual properties of the Data Record. This is equivalent to a logical OR operation. 0x03 allOf The "allOf" structured data type semantic specifies that all of the list elements from the structured data are actual properties of the Data Record. 0x04 ordered The "ordered" structured data type semantic specifies that elements from the list in the structured data are ordered. 0x05-0xFE unassigned 0xFF undefined The "undefined" structured data type semantic specifies that the semantic of the list elements is not specified and that, if a semantic exists, then it is up to the Collecting Process to draw its own conclusions. The "undefined" structured data type semantic is the default structured data type semantic. Expert Review Paul Aitken, Jen Linkova 0 DST 60 Destination Options for IPv6 1 HOP 0 IPv6 Hop-by-Hop Options 2 NoNxt 59 No Next Header for IPv6 3 UNK Unknown extension or transport header 4 FRA0 44 Fragment header - first fragment 5 RH 43 Routing header 6 FRA1 44 Fragmentation header - not first fragment 7 MOB 135 Mobility Header 8 ESP 50 Encapsulating Security Payload 9 AH 51 Authentication Header 10 HIP 139 Host Identity Protocol 11 SHIM6 140 Shim6 Protocol 12 253 Use for experimentation and testing 13 254 Use for experimentation and testing 14-255 Unassigned Alfred Nothaft mailto:alfred.nothaft&nokia.com 2018-02-12 Andrew Feren mailto:andrew.feren&plixer.com 2017-04-19 Brian Trammell mailto:brian&trammell.ch 2013-08-01 Felix Erlacher mailto:felix.erlacher&ccs-labs.org 2017-06-19 ipfix-iana at cisco.com mailto:ipfix-iana&cisco.com 2013-04-11 Paul Aitken mailto:paul.aitken&att.com 2018-02-12 Qosmos http://www.qosmos.com 2017-02-21 Sriram Gopalakrishnan mailto:sriragop&cisco.com 2024-07-02 Tim Kittel mailto:tim.kittel&rohde-schwarz.com 2022-02-04 Yaakov (J) Stein mailto:yaakov_s&rad.com 2013-04-11