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.

The number of incoming packets since the previous report (if any) for this Flow at the Observation Point.

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.

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 [RFC791] for the specification of the IPv4 protocol field. See [RFC8200] for the specification of the IPv6 protocol field. See the list of protocol numbers assigned by IANA at [https://www.iana.org/assignments/protocol-numbers].

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 [RFC1812] (Section 5.3.2) and [RFC791] for the definition of the IPv4 TOS field. See [RFC8200] for the definition of the IPv6 Traffic Class field.

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 [RFC9293], the assignment of TCP control bits is managed by IANA via the "TCP Header Flags" registry [https://www.iana.org/assignments/tcp-parameters/tcp-parameters.xhtml#tcp-header-flags]. 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 [RFC9293] 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 [RFC7011]), this Information Element covers the low-order octet of this field (i.e., bit offset positions 8 to 15) [https://www.iana.org/assignments/tcp-parameters/tcp-parameters.xhtml#tcp-header-flags]. 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 [https://www.iana.org/assignments/tcp-parameters/tcp-parameters.xhtml#tcp-header-flags] 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 [https://www.iana.org/assignments/tcp-parameters/tcp-parameters.xhtml#tcp-header-flags].

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 [RFC768] for the definition of the UDP source port field. See [RFC9293] for the definition of the TCP source port field. See [RFC9260] for the definition of the SCTP source port number field. See [RFC4340] for the definition of the DCCP source port field.

See the assigned transport protocol (e.g., UDP, TCP, SCTP, and DCCP) port numbers at [https://www.iana.org/assignments/service-names-port-numbers].

The IPv4 source address in the IP packet header.

See [RFC791] for the definition of the IPv4 source address field.

The number of contiguous bits that are relevant in the sourceIPv4Prefix Information Element.

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 [RFC2863]. 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 [RFC2863].

See [RFC2863] for the definition of the ifIndex object.

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 [RFC768] for the definition of the UDP destination port field. See [RFC9293] for the definition of the TCP destination port field. See [RFC9260] for the definition of the SCTP destination port number field. See [RFC4340] for the definition of the DCCP destination port field.

See the assigned transport protocol (e.g., UDP, TCP, SCTP, and DCCP) port numbers at [https://www.iana.org/assignments/service-names-port-numbers].

The IPv4 destination address in the IP packet header.

See [RFC791] for the definition of the IPv4 destination address field.

The number of contiguous bits that are relevant in the destinationIPv4Prefix Information Element.

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 [RFC2863]. 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 [RFC2863].

See [RFC2863] for the definition of the ifIndex object.

The IPv4 address of the next IPv4 hop.

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 [RFC4271] for a description of BGP-4, and see [RFC1930] for the definition of the AS number.

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 [RFC4271] for a description of BGP-4, and see [RFC1930] for the definition of the AS number.

The IPv4 address of the next (adjacent) BGP hop.

See [RFC4271] for a description of BGP-4.

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.

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.

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.

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.

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.

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.

Length of the smallest packet observed for this Flow. The packet length includes the IP header(s) length and the IP payload length.

See [RFC791] for the specification of the IPv4 total length. See [RFC8200] for the specification of the IPv6 payload length. See [RFC2675] for the specification of the IPv6 jumbo payload length.

Length of the largest packet observed for this Flow. The packet length includes the IP header(s) length and the IP payload length.

See [RFC791] for the specification of the IPv4 total length. See [RFC8200] for the specification of the IPv6 payload length. See [RFC2675] for the specification of the IPv6 jumbo payload length.

The IPv6 source address in the IP packet header.

See [RFC8200] for the definition of the Source Address field in the IPv6 header.

The IPv6 destination address in the IP packet header.

See [RFC8200] for the definition of the Destination Address field in the IPv6 header.

The number of contiguous bits that are relevant in the sourceIPv6Prefix Information Element.

The number of contiguous bits that are relevant in the destinationIPv6Prefix Information Element.

The value of the IPv6 Flow Label field in the IP packet header.

See [RFC8200] for the definition of the Flow Label field in the IPv6 packet header.

Type and Code of the IPv4 ICMP message. The combination of both values is reported as (ICMP type * 256) + ICMP code.

See the assigned ICMP types at [https://www.iana.org/assignments/icmp-parameters]

The type field of the IGMP message.

See the assigned IGMP type numbers at [https://www.iana.org/assignments/igmp-type-numbers/igmp-type-numbers.xhtml#igmp-type-numbers-1]

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.

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.]

The number of seconds after which an active Flow is timed out anyway, even if there is still a continuous flow of packets.

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.

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.

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.

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.

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.

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.

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.

IPv4 source address prefix.

IPv4 destination address prefix.

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 registry [https://www.iana.org/assignments/mpls-label-values]. See [RFC3031] for the MPLS label structure.

The IPv4 address of the system that the MPLS top label will cause this Flow to be forwarded to.

See [RFC3031] for the association between MPLS labels and IP addresses.

Deprecated in favor of 302 selectorId. The unique identifier associated with samplerName.

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.

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.

Deprecated in favor of 302 selectorId. Characterizes the traffic class, i.e., QoS treatment.

Minimum TTL value observed for any packet in this Flow.

See [RFC791] for the definition of the IPv4 Time to Live field. See [RFC8200] for the definition of the IPv6 Hop Limit field.

Maximum TTL value observed for any packet in this Flow.

See [RFC791] for the definition of the IPv4 Time to Live field. See [RFC8200] for the definition of the IPv6 Hop Limit field.

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 [RFC791] for the definition of the IPv4 Identification field. See [RFC8200] for the definition of the Identification field in the IPv6 Fragment header.

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 [RFC791] for the definition of the IPv4 TOS field. See [RFC8200] for the definition of the IPv6 Traffic Class field. See [RFC3234] for the definition of middleboxes.

The IEEE 802 source MAC address field.

See IEEE.802-3.2002.

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.

Virtual LAN identifier associated with ingress interface. For dot1q vlans, see 243 dot1qVlanId.

See IEEE.802-1Q.2003.

Virtual LAN identifier associated with egress interface. For postdot1q vlans, see 254, postDot1qVlanId.

See IEEE.802-1Q.2003.

The IP version field in the IP packet header.

See [RFC791] for the definition of the version field in the IPv4 packet header. See [RFC8200] for the definition of the version field in the IPv6 packet header. Additional information on defined version numbers can be found at [https://www.iana.org/assignments/version-numbers].

The direction of the Flow observed at the Observation Point. There are only two values defined.

0x00: ingress flow
0x01: egress flow

The IPv6 address of the next IPv6 hop.

The IPv6 address of the next (adjacent) BGP hop.

See [RFC4271] for a description of BGP-4.

Deprecated in favor of the ipv6ExtensionHeadersFull IE.

This Information Element was initially specified in [RFC5102]. [RFC7012] has obsoleted [RFC5102] and specifies that [IANA-IPFIX] is the normative reference for this Information Element. The diagram provided in [RFC5102] is incorrect; see [RFC Errata 1738].

[RFC3954]

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 [RFC3032].

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 [RFC3032].

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 [RFC3032].

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 [RFC3032].

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 [RFC3032].

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 [RFC3032].

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 [RFC3032].

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 [RFC3032].

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 [RFC3032].

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 [RFC3032].

The IEEE 802 destination MAC address field.

See IEEE.802-3.2002.

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.

A short name uniquely describing an interface, eg "Eth1/0".

See [RFC2863] for the definition of the ifName object.

The description of an interface, eg "FastEthernet 1/0" or "ISP connection".

See [RFC2863] for the definition of the ifDescr object.

Deprecated in favor of 335 selectorName. Name of the flow sampler.

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.

The total number of incoming packets for this Flow at the Observation Point since the Metering Process (re-)initialization for this Observation Point.

Flow flags and the value of the sampler ID (samplerId) combined in one bitmapped field. Reserved for internal use on the Collector.

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.

See [RFC791] for the specification of the fragment offset in the IPv4 header. See [RFC8200] for the specification of the fragment offset in the IPv6 Fragment header.

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 sub-registries at [https://www.iana.org/assignments/ipfix/ipfix.xhtml#forwarding-status].

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 [RFC4364], the size of mplsVpnRouteDistinguisher is 8 octets. However, in [RFC4382] 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 [RFC4364] for the specification of the route distinguisher. See [RFC4382] for the specification of the MPLS/BGP Layer 3 Virtual Private Network (VPN) Management Information Base.

The prefix length of the subnet of the mplsTopLabelIPv4Address or mplsTopLabelIPv6Address that the MPLS top label will cause the Flow to be forwarded to.

See [RFC3031] for the association between MPLS labels and prefix lengths.

BGP Policy Accounting Source Traffic Index.

BGP policy accounting as described in [CCO-BGPPOL].

BGP Policy Accounting Destination Traffic Index.

BGP policy accounting as described in [CCO-BGPPOL].

Specifies the description of an application.

Specifies an Application ID per [RFC6759].

See section 4 of [RFC6759] for the applicationId Information Element Specification.

Specifies the name of an application.

[RFC3954]

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.

See [RFC3260] for the definition of the Differentiated Services Field. See section 5.3.2 of [RFC1812] and [RFC791] for the definition of the IPv4 TOS field. See [RFC8200] for the definition of the IPv6 Traffic Class field. See the IPFIX Information Model [RFC5102] for the 'ipDiffServCodePoint' specification.

The amount of multicast replication that's applied to a traffic stream.

See [RFC1112] for the specification of reserved IPv4 multicast addresses. See [RFC4291] for the specification of reserved IPv6 multicast addresses.

Deprecated in favor of 335 selectorName. Traffic Class Name, associated with the classId Information Element.

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 registry [https://www.iana.org/assignments/ipfix/ipfix.xhtml#classification-engine-ids]

Deprecated in favor of 409 sectionOffset. Layer 2 packet section offset. Potentially a generic packet section offset.

Deprecated in favor of 312 dataLinkFrameSize. Layer 2 packet section size. Potentially a generic packet section size.

Deprecated in favor of 315 dataLinkFrameSection. Layer 2 packet section data.

[RFC3954]

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 [RFC4271] for a description of BGP-4, and see [RFC1930] for the definition of the AS number.

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 [RFC4271] for a description of BGP-4, and see [RFC1930] for the definition of the AS number.

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.

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.

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.

The number of packets since the previous report (if any) of this Flow dropped by packet treatment.

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.

The number of packets of this Flow dropped by packet treatment since the Metering Process (re-)initialization for this Observation Point.

The reason for Flow termination. Values are listed in the flowEndReason registry.

See the flowEndReason registry [https://www.iana.org/assignments/ipfix/ipfix.xhtml#ipfix-flow-end-reason].

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.

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.

Type and Code of the IPv6 ICMP message. The combination of both values is reported as (ICMP type * 256) + ICMP code.

See the assigned ICMPv6 types and codes at [https://www.iana.org/assignments/icmpv6-parameters]

The IPv6 address of the system that the MPLS top label will cause this Flow to be forwarded to.

See [RFC3031] for the association between MPLS labels and IP addresses.

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.

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.

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.

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.

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.

The identifier of the 802.11 (Wi-Fi) channel used.

See IEEE.802-11.1999.

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.

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.

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.

The absolute timestamp of the first packet of this Flow.

The absolute timestamp of the last packet of this Flow.

The absolute timestamp of the first packet of this Flow.

The absolute timestamp of the last packet of this Flow.

The absolute timestamp of the first packet of this Flow.

The absolute timestamp of the last packet of this Flow.

The absolute timestamp of the first packet of this Flow.

The absolute timestamp of the last packet of this Flow.

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.

See the [IPFIX protocol specification] for the definition of the IPFIX Message Header.

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.

See the [IPFIX protocol specification] for the definition of the IPFIX Message Header.

The absolute timestamp of the last (re-)initialization of the IPFIX Device.

The difference in time between the first observed packet of this Flow and the last observed packet of this Flow.

The difference in time between the first observed packet of this Flow and the last observed packet of this Flow.

The total number of Flows observed in the Observation Domain since the Metering Process (re-)initialization for this Observation Point.

The total number of observed IP packets that the Metering Process did not process since the (re-)initialization of the Metering Process.

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.

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.

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.

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.

IPv6 destination address prefix.

IPv6 source address prefix.

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.

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.

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.

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.

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.

Type of the IPv4 ICMP message.

See the assigned ICMP types at [https://www.iana.org/assignments/icmp-parameters/icmp-parameters.xhtml#icmp-parameters-types]

Code of the IPv4 ICMP message.

See the assigned ICMP codes at [https://www.iana.org/assignments/icmp-parameters/icmp-parameters.xhtml#icmp-parameters-codes]

Type of the IPv6 ICMP message.

See the assigned ICMPv6 types at [https://www.iana.org/assignments/icmpv6-parameters/icmpv6-parameters.xhtml#icmpv6-parameters-2]

Code of the IPv6 ICMP message.

See the assigned ICMPv6 codes at [https://www.iana.org/assignments/icmpv6-parameters/icmpv6-parameters.xhtml#icmpv6-parameters-3]

The source port identifier in the UDP header.

See [RFC768] for the definition of the UDP source port field. Additional information on defined UDP port numbers can be found at [https://www.iana.org/assignments/service-names-port-numbers].

The destination port identifier in the UDP header.

See [RFC768] for the definition of the UDP destination port field. Additional information on defined UDP port numbers can be found at [https://www.iana.org/assignments/service-names-port-numbers].

The source port identifier in the TCP header.

See [RFC9293] for the definition of the TCP source port field. Additional information on defined TCP port numbers can be found at [https://www.iana.org/assignments/service-names-port-numbers].

The destination port identifier in the TCP header.

See [RFC9293] for the definition of the TCP destination port field. Additional information on defined TCP port numbers can be found at [https://www.iana.org/assignments/service-names-port-numbers].

The sequence number in the TCP header.

See [RFC9293] for the definition of the TCP sequence number.

The acknowledgement number in the TCP header.

See [RFC9293] for the definition of the TCP acknowledgement number.

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 [RFC9293] for the definition of the TCP window field. See [RFC1323] for the definition of the TCP window scale.

The urgent pointer in the TCP header.

See [RFC9293] for the definition of the TCP urgent pointer.

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.

See [RFC9293] for the definition of the TCP header.

The length of the IP header. For IPv6, the value of this Information Element is 40.

See [RFC791] for the definition of the IPv4 header. See [RFC8200] for the definition of the IPv6 header.

The total length of the IPv4 packet.

See [RFC791] for the specification of the IPv4 total length.

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.

See [RFC8200] for the specification of the IPv6 payload length. See [RFC2675] for the specification of the IPv6 jumbo payload option.

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.

See [RFC791] for the definition of the IPv4 Time to Live field. See [RFC2675] for the definition of the IPv6 Hop Limit field.

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 [RFC8200] for the definition of the IPv6 Next Header field. See the list of protocol numbers assigned by IANA at [https://www.iana.org/assignments/protocol-numbers].

The size of the MPLS packet without the label stack.

See [RFC3031] for the specification of MPLS packets. See [RFC3032] for the specification of the MPLS label stack.

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.

See [RFC3260] for the definition of the Differentiated Services field. See [RFC1812] (Section 5.3.2) and [RFC791] for the definition of the IPv4 TOS field. See [RFC8200] for the definition of the IPv6 Traffic Class field.

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.

See [RFC1812] (Section 5.3.3) and [RFC791] for the definition of the IP Precedence. See [RFC1812] (Section 5.3.2) and [RFC791] for the definition of the IPv4 TOS field. See [RFC8200] for the definition of the IPv6 Traffic Class field.

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 [RFC791] for the specification of the IPv4 fragment flags. See [RFC8200] for the specification of the IPv6 Fragment header.

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.

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.

The TTL field from the top MPLS label stack entry, i.e., the last label that was pushed.

See [RFC3032] for the specification of the TTL field.

The length of the MPLS label stack in units of octets.

See [RFC3032] for the specification of the MPLS label stack.

The number of labels in the MPLS label stack.

See [RFC3032] for the specification of the MPLS label stack.

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 [RFC3032] for the specification of the Exp field. See [RFC3270] for usage of the Exp field.

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.

See [RFC791] for the specification of IPv4 packets. See [RFC8200] for the specification of the IPv6 payload length. See [RFC2675] for the specification of the IPv6 jumbo payload length.

The value of the Length field in the UDP header.

See [RFC768] for the specification of the UDP header.

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 [RFC1112] for the specification of reserved IPv4 multicast addresses. See [RFC4291] for the specification of reserved IPv6 multicast addresses and the definition of the T flag and the IPv6 multicast scope. The diagram provided in [RFC5102] is incorrect. The diagram in this registry is taken from Errata 1736. See [RFC Errata 1736].

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.

See [RFC791] for the specification of the IPv4 header.

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 [RFC791] for the definition of IPv4 options. See the list of IPv4 option numbers assigned by IANA at [https://www.iana.org/assignments/ip-parameters]. The diagram provided in [RFC5102] is incorrect. The diagram in this registry is taken from Errata 1737. See [RFC Errata 1737] .

Deprecated in favor of the tcpOptionsFull IE.

This Information Element was initially specified in [RFC5102]. [RFC7012] has obsoleted [RFC5102] and specifies that [IANA-IPFIX] is the normative reference for this Information Element. The diagram provided in [RFC5102] is incorrect; see [RFC Errata 1739].

The value of this Information Element is always a sequence of 0x00 values.

An IPv4 address to which the Exporting Process sends Flow information.

An IPv6 address to which the Exporting Process sends Flow information.

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 [RFC2863]. 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 [RFC2863].

See [RFC2863] for the definition of the ifIndex object.

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 [RFC3954] for the definition of the NetFlow version 9 message header.

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 [RFC791] for the specification of the IPv4 protocol field. See [RFC8200] for the specification of the IPv6 protocol field. See the list of protocol numbers assigned by IANA at [https://www.iana.org/assignments/protocol-numbers].

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 [RFC768] for the definition of the UDP destination port field. See [RFC9293] for the definition of the TCP destination port field. See [RFC9260] for the definition of the SCTP destination port number field.

See the assigned transport protocol (e.g., UDP, TCP, and SCTP) port numbers at [https://www.iana.org/assignments/service-names-port-numbers].

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 [RFC768] for the definition of the UDP source port field. See [RFC9293] for the definition of the TCP source port field. See [RFC9260] for the definition of the SCTP source port number field.

See the assigned transport protocol (e.g., UDP, TCP, and SCTP) port numbers at [https://www.iana.org/assignments/service-names-port-numbers].

The total number of packets of this Flow with TCP "Synchronize sequence numbers" (SYN) flag set.

See [RFC9293] for the definition of the TCP SYN flag.

The total number of packets of this Flow with TCP "No more data from sender" (FIN) flag set.

See [RFC9293] for the definition of the TCP FIN flag.

The total number of packets of this Flow with TCP "Reset the connection" (RST) flag set.

See [RFC9293] for the definition of the TCP RST flag.

The total number of packets of this Flow with TCP "Push Function" (PSH) flag set.

See [RFC9293] for the definition of the TCP PSH flag.

The total number of packets of this Flow with TCP "Acknowledgment field significant" (ACK) flag set.

See [RFC9293] for the definition of the TCP ACK flag.

The total number of packets of this Flow with TCP "Urgent Pointer field significant" (URG) flag set.

See [RFC9293] for the definition of the TCP URG flag.

The total length of the IP packet.

See [RFC791] for the specification of the IPv4 total length. See [RFC8200] for the specification of the IPv6 payload length. See [RFC2675] for the specification of the IPv6 jumbo payload length.

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 [RFC791] for the definition of the IPv4 source address field. See [RFC3022] for the definition of NAT. See [RFC3234] for the definition of middleboxes.

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 [RFC791] for the definition of the IPv4 destination address field. See [RFC3022] for the definition of NAT. See [RFC3234] for the definition of middleboxes.

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 [RFC768] for the definition of the UDP source port field. See [RFC9293] for the definition of the TCP source port field. See [RFC9260] for the definition of SCTP. See [RFC3022] for the definition of NAPT. See [RFC3234] for the definition of middleboxes. See the assigned transport protocol (e.g., UDP, TCP, SCTP, and DCCP) port numbers at [https://www.iana.org/assignments/service-names-port-numbers].

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 [RFC768] for the definition of the UDP source port field. See [RFC9293] for the definition of the TCP source port field. See [RFC9260] for the definition of SCTP. See [RFC3022] for the definition of NAPT. See [RFC3234] for the definition of middleboxes. See the assigned transport protocol (e.g., UDP, TCP, SCTP, and DCCP) port numbers at [https://www.iana.org/assignments/service-names-port-numbers].

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.

See the natOriginatingAddressRealm registry [https://www.iana.org/assignments/ipfix/ipfix.xhtml#ipfix-nat-originating-address-realm]. See [RFC3022] for the definition of NAT.

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 registry [https://www.iana.org/assignments/ipfix/ipfix.xhtml#ipfix-nat-event-type]. See [RFC3022] for the definition of NAT. See [RFC8158] for the definitions of values 4-16.

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.

See #298, initiatorPackets.

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.

See #299, responderPackets.

Indicates a firewall event. Allowed values are listed in the firewallEvent registry.

See the firewallEvent registry [https://www.iana.org/assignments/ipfix/ipfix.xhtml#ipfix-firewall-event].

An unique identifier of the VRFname where the packets of this flow are being received. This identifier is unique per Metering Process

An unique identifier of the VRFname where the packets of this flow are being sent. This identifier is unique per Metering Process

The name of a VPN Routing and Forwarding table (VRF).

See [RFC4364] for the definition of VRF.

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 [RFC3032] for the specification of the Exp field. See [RFC3270] for usage of the Exp field.

The scale of the window field in the TCP header.

See [RFC1323] for the definition of the TCP window scale.

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 registry [https://www.iana.org/assignments/ipfix/ipfix.xhtml#ipfix-biflow-direction].

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.

[IEEE.802-3.2005]

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].

[IEEE.802-3.2005]

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].

[IEEE.802-3.2005]

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]

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]

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]

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]

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)

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)

A 32-bit non-zero connection identifier, which together with the pseudoWireType, identifies the Pseudo Wire (PW) as defined in [RFC8077].

See [RFC8077] for pseudowire definitions.

The value of this information element identifies the type of MPLS Pseudo Wire (PW) as defined in [RFC4446].

See [RFC4446] for the pseudowire type definition, and [https://www.iana.org/assignments/pwe3-parameters] for the IANA Pseudowire Types registry.

The 32-bit Preferred Pseudo Wire (PW) MPLS Control Word as defined in Section 3 of [RFC4385].

See [RFC4385] for the Pseudo Wire Control Word definition.

The index of a networking device's physical interface (example, a switch port) where packets of this flow are being received.

See [RFC2863] for the definition of the ifIndex object.

The index of a networking device's physical interface (example, a switch port) where packets of this flow are being sent.

See [RFC2863] for the definition of the ifIndex object.

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]

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]

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 [http://standards.ieee.org/regauth/ethertype/eth.txt]

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.

See [RFC1812] (Section 5.3.3) and [RFC791] for the definition of the IP Precedence. See [RFC1812] (Section 5.3.2) and [RFC791] for the definition of the IPv4 TOS field. See [RFC8200] for the definition of the IPv6 Traffic Class field.

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.

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).

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.

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.

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 lement, 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 [RFC1321], 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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

Type of observation point. Values are listed in the observationPointType registry.

See the observationPointType registry [https://www.iana.org/assignments/ipfix/ipfix.xhtml#ipfix-observation-point-type].

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.

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.

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.

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 [RFC8200] for the definition of the Source Address field in the IPv6 header. See [RFC3234] for the definition of middleboxes. See [RFC6146] for nat64 specification.

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 [RFC8200] for the definition of the Destination Address field in the IPv6 header. See [RFC3234] for the definition of middleboxes. See [RFC6146] for nat64 specification.

Locally unique identifier of a NAT pool.

The name of a NAT pool identified by a natPoolID.

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.           |
+-----+-----+-------------------------------------------------------+

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 registry [https://www.iana.org/assignments/ipfix/ipfix.xhtml#ipfix-anonymization-technique].

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.

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 }.

Specifies if the Application ID is used as a tunnel technology.

Possible values are: { "yes", "y", 1 }, { "no", "n", 2 } and { "unassigned", "u", 0 }.

Specifies if the Application ID is an encrypted networking protocol.

Possible values are: { "yes", "y", 1 }, { "no", "n", 2 } and { "unassigned", "u", 0 }.

Specifies a generic Information Element with a basicList abstract data type. For example, a list of port numbers, a list of interface indexes, etc.

Specifies a generic Information Element with a subTemplateList abstract data type.

Specifies a generic Information Element with a subTemplateMultiList abstract data type.

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 [RFC4271] for a description of BGP-4, [RFC6811] for the definition of "validity states" and [draft-ietf-sidr-origin-validation-signaling] for the encoding of those "validity states".

IPSec Security Parameters Index (SPI).

See [RFC2401] for the definition of SPI.

GRE key, which is used for identifying an individual traffic flow within a tunnel.

See [RFC1701] for the definition of GRE and the GRE Key.

This Information Element identifies the NAT type applied to packets of the Flow. Values are listed in the natType registry.

See the natType registry [https://www.iana.org/assignments/ipfix/ipfix.xhtml#ipfix-nat-type]. See [RFC3022] for the definition of NAT (commonly named NAT44). See [RFC6144] for the definition of NAT46. See [RFC6146] for the definition of NAT64. See [RFC6296] for the definition of NPTv6. See [RFC791] for the definition of IPv4. See [RFC8200] for the definition of IPv6.

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.

See #231, initiatorOctets.

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.

See #232, responderOctets.

The name of an observation domain identified by an observationDomainId.

See #149, observationDomainId.

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.

The Selector ID is the unique ID identifying a Primitive Selector. Each Primitive Selector must have a unique ID in the Observation Domain.

This Information Element contains the ID of another Information Element.

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 their parameters. For the methods parameters, Information Elements are defined in the IPFIX IANA registry [IANA-IPFIX]. he 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 [https://www.iana.org/assignments/psamp-parameters]

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.

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.

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.

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.

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.

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.

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.

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]

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 [RFC5477] and [RFC2804].

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.

[RFC2804] [RFC5477]

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 [RFC791] refers to as "data" or "data octets". For example, see the examples in [RFC791], 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 [RFC8200] 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.

[RFC791] [RFC8200]

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 [RFC6313]. Or a set of these Information Elements MAY be contained in one Flow Record as shown in Appendix B of [RFC7133].

The data link layer is defined in [ISO/IEC.7498-1:1994].

[RFC6313] [RFC7133] [ISO/IEC.7498-1:1994]

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 [RFC5477] and [RFC2804].

See [RFC3031] for the specification of MPLS packets.

See [RFC3032] 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.

[RFC2804] [RFC3031] [RFC3032] [RFC5477]

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 [RFC3031] for the specification of MPLS packets.

See [RFC3032] 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.

[RFC3031] [RFC3032]

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 [RFC7011].

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 [RFC7011].

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 [RFC7011].

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 [RFC7011].

This Information Element specifies the absolute time in seconds of an observation.

This Information Element specifies the absolute time in milliseconds of an observation.

This Information Element specifies the absolute time in microseconds of an observation.

This Information Element specifies the absolute time in nanoseconds of an observation.

This Information Element specifies the value from the digest hash function. See also Sections 6.2, 3.8 and 7.1 of [RFC5475].

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 [RFC5475].

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 [RFC5475].

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 [RFC5475].

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 [RFC5475].

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 [RFC5475].

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 [RFC5475].

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 [RFC5475].

This Information Element specifies the initialiser value to the hash function.

See also Sections 6.2, 3.8 and 7.1 of [RFC5475].

The name of a selector identified by a selectorID. Globally unique per Metering Process.

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 [RFC7011].

Note that the upperCILimit, lowerCILimit, and confidenceLevel are all required to specify confidence, and should be disregarded unless all three are specified together.

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 [RFC7011].

Note that the upperCILimit, lowerCILimit, and confidenceLevel are all required to specify confidence, and should be disregarded unless all three are specified together.

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 [RFC7011].

Note that the upperCILimit, lowerCILimit, and confidenceLevel are all required to specify confidence, and should be disregarded unless all three are specified together.

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 [RFC5102]; see that section for more information on the types described in the [informationElementDataType] subregistry. These types are registered in the IANA IPFIX Information Element Data Type subregistry.

The [informationElementDataType] subregistry is intended to assign numbers for type names, not to provide a mechanism for adding data types to the IPFIX Protocol, and as such requires a Standards Action [RFC8126] to modify.

See the IPFIX Information Element Data Types registry [https://www.iana.org/assignments/ipfix/ipfix.xhtml#ipfix-information-element-data-types]

A UTF-8 [RFC3629] 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 [RFC4646], encoded in-line [RFC2482] 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 ownlanguage tag; in this case, the description information in each language SHOULD have equivalent meaning. In the absence of any language tag, the "i-default" [RFC2277] language SHOULD be assumed. See the Security Considerations Section of [RFC5610] for notes on string handling for Information Element type records.

A UTF-8 [RFC3629] 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

Contains the inclusive low end of the range of acceptable values for an Information Element.

Contains the inclusive high end of the range of acceptable values for an Information Element.

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 [RFC5102]; see that section for more information on the types defined in the [IPFIX Information Element Semantics] subregistry. This field may take the values in the [IPFIX Information Element Semantics] subregistry. 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] subregistry is intended to assign numbers for semantics names, not to provide a mechanism for adding semantics to the IPFIX Protocol, and as such requires a Standards Action [RFC8126] to modify.

See the IP Flow Information Export (IPFIX) Entities registry [https://www.iana.org/assignments/ipfix/ipfix.xhtml#ipfix-information-element-semantic]

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 [RFC5102]; see that section for more information on the types described in the informationElementsUnits subregistry. These types can take the values in the [IANA IPFIX Information Element Units] subregistry. The special value 0x00 (none) is used to note that the field is unitless.

These types are registered in the [IANA IPFIX Information Element Units] subregistry.

See the IPFIX Information Element Units registry [https://www.iana.org/assignments/ipfix/ipfix.xhtml#ipfix-information-element-units]

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 registered PENs at [https://www.iana.org/assignments/enterprise-numbers/enterprise-numbers]

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.

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.

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.

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.

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 [RFC7348]

See NVGRE RFC at [RFC7637]

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)

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)

The total number of incoming unicast packets metered at the Observation Point since the Metering Process (re-)initialization for this Observation Point.

The total number of incoming multicast packets metered at the Observation Point since the Metering Process (re-)initialization for this Observation Point.

The total number of incoming broadcast packets metered at the Observation Point since the Metering Process (re-)initialization for this Observation Point.

The total number of incoming unicast packets metered at the Observation Point since the Metering Process (re-)initialization for this Observation Point.

The total number of incoming broadcast packets metered at the Observation Point since the Metering Process (re-)initialization for this Observation Point.

The absolute timestamp at which the monitoring interval started. A Monitoring interval is the period of time during which the Metering Process is running.

The absolute timestamp at which the monitoring interval ended. A Monitoring interval is the period of time during which the Metering Process is running.

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 at [https://www.iana.org/assignments/service-names-port-numbers].

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 at [https://www.iana.org/assignments/service-names-port-numbers].

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.

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.

The IEEE 802 MAC address of a wireless station (STA).

See section 1.4 of [RFC5415] for the definition of STA.

The IPv4 address of a wireless station (STA).

See section 1.4 of [RFC5415] for the definition of STA.

The IEEE 802 MAC address of a wireless access point (WTP).

See section 1.4 of [RFC5415] for the definition of WTP.

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 [https://www.iana.org/assignments/ianaiftype-mib]

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 [https://www.iana.org/assignments/ianaiftype-mib]

The RTP sequence number per [RFC3550].

[RFC3550]

User name associated with the flow.

An attribute that provides a first level categorization for each Application ID.

An attribute that provides a second level categorization for each Application ID.

An attribute that groups multiple Application IDs that belong to the same networking application.

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.

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.

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.

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.

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.

The count of distinct source IPv4 address values for Original Flows contributing to this Aggregated Flow.

The count of distinct destination IPv4 address values for Original Flows contributing to this Aggregated Flow.

The count of distinct source IPv6 address values for Original Flows contributing to this Aggregated Flow.

The count of distinct destination IPv6 address values for Original Flows contributing to this Aggregated Flow.

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 registry is intended to list a complete set of possible value distribution methods.

See the valueDistributionMethod registry [https://www.iana.org/assignments/ipfix/ipfix.xhtml#ipfix-value-distribution-method].

Interarrival jitter as defined in section 6.4.1 of [RFC3550], measured in milliseconds.

[RFC3550]

Interarrival jitter as defined in section 6.4.1 of [RFC3550], measured in microseconds.

[RFC3550]

Interarrival jitter as defined in section 6.4.1 of [RFC3550], measured in nanoseconds.

[RFC3550]

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]

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]

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. Further Information Elements are needed to fully specify packet selection with these methods and all their parameters. Further method identifiers may be added to the flowSelectorAlgorithm registry. It might be necessary to define new Information Elements to specify their parameters.

See the flowSelectorAlgorithm registry [https://www.iana.org/assignments/ipfix/ipfix.xhtml#ipfix-flowselectoralgorithm].

This Information Element specifies the volume in octets of all Flows that are selected in the Intermediate Flow Selection Process since the previous report.

This Information Element specifies the volume in packets of all Flows that were selected in the Intermediate Flow Selection Process since the previous report.

This Information Element specifies the number of Flows that were selected in the Intermediate Flow Selection Process since the last report.

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 [RFC7011].

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 [RFC7011].

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.

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.

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.

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.

This Information Element specifies the Information Elements that are used by the Hash-based Flow Selector as the Hash Domain.

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).

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).

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.

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.

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.

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.

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.

This Information Element specifies the type of the selected data link frame. Data link types are defined in the dataLinkFrameType registry.

Further 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 registry [https://www.iana.org/assignments/ipfix/ipfix.xhtml#ipfix-data-link-frame-type].

More information about the data link layer can be found in (IEEE802.3)(IEEE802.11)(ISO/IEC.7498-1:1994).