github.com/zartbot/goflow@v0.0.0-20221001080520-456f7dfad288/tools/ipfix-information-elements.csv (about) 1 ElementID,Name,Abstract Data Type,Data Type Semantics,Status,Description,Units,Range,References,Requester,Revision,Date 2 0,Reserved,,,,,,,,[RFC5102],,2013-02-18 3 1,octetDeltaCount,unsigned64,deltaCounter,current,"The number of octets since the previous report (if any) 4 in incoming packets for this Flow at the Observation Point. 5 The number of octets includes IP header(s) and IP payload.",octets,,,[RFC5102],0,2013-02-18 6 2,packetDeltaCount,unsigned64,deltaCounter,current,"The number of incoming packets since the previous report 7 (if any) for this Flow at the Observation Point.",packets,,,[RFC5102],0,2013-02-18 8 3,deltaFlowCount,unsigned64,deltaCounter,current,"The conservative count of Original Flows contributing 9 to this Aggregated Flow; may be distributed via any of the methods 10 expressed by the valueDistributionMethod Information Element.",flows,,,[RFC7015],1,2013-06-25 11 4,protocolIdentifier,unsigned8,identifier,current,"The value of the protocol number in the IP packet header. 12 The protocol number identifies the IP packet payload type. 13 Protocol numbers are defined in the IANA Protocol Numbers 14 registry. 15 16 17 18 19 In Internet Protocol version 4 (IPv4), this is carried in the 20 Protocol field. In Internet Protocol version 6 (IPv6), this 21 is carried in the Next Header field in the last extension 22 header of the packet.",,,"See [RFC791] for the specification of the IPv4 23 protocol field. 24 See [RFC8200] for the specification of the 25 IPv6 protocol field. 26 See the list of protocol numbers assigned by IANA at [IANA registry protocol-numbers].",[RFC5102],0,2013-02-18 27 5,ipClassOfService,unsigned8,identifier,current,"For IPv4 packets, this is the value of the TOS field in 28 the IPv4 packet header. For IPv6 packets, this is the 29 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. 30 See [RFC8200] for the definition of the IPv6 31 Traffic Class field.",[RFC5102],0,2013-02-18 32 6,tcpControlBits,unsigned16,flags,current,"TCP control bits observed for the packets of this Flow. 33 This information is encoded as a bit field; for each TCP control 34 bit, there is a bit in this set. The bit is set to 1 if any 35 observed packet of this Flow has the corresponding TCP control bit 36 set to 1. The bit is cleared to 0 otherwise. 37 38 39 40 41 The values of each bit are shown below, per the definition of the 42 bits in the TCP header [RFC793][RFC3168][RFC3540]: 43 44 45 46 MSb LSb 47 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 48 +---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+ 49 | | | N | C | E | U | A | P | R | S | F | 50 | Zero | Future | S | W | C | R | C | S | S | Y | I | 51 | (Data Offset) | Use | | R | E | G | K | H | T | N | N | 52 +---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+ 53 54 bit flag 55 value name description 56 ------+-----+------------------------------------- 57 0x8000 Zero (see tcpHeaderLength) 58 0x4000 Zero (see tcpHeaderLength) 59 0x2000 Zero (see tcpHeaderLength) 60 0x1000 Zero (see tcpHeaderLength) 61 0x0800 Future Use 62 0x0400 Future Use 63 0x0200 Future Use 64 0x0100 NS ECN Nonce Sum 65 0x0080 CWR Congestion Window Reduced 66 0x0040 ECE ECN Echo 67 0x0020 URG Urgent Pointer field significant 68 0x0010 ACK Acknowledgment field significant 69 0x0008 PSH Push Function 70 0x0004 RST Reset the connection 71 0x0002 SYN Synchronize sequence numbers 72 0x0001 FIN No more data from sender 73 74 75 76 As the most significant 4 bits of octets 12 and 13 (counting from 77 zero) of the TCP header [RFC793] are used to encode the TCP data 78 offset (header length), the corresponding bits in this Information 79 Element MUST be exported as zero and MUST be ignored by the 80 collector. Use the tcpHeaderLength Information Element to encode 81 this value. 82 83 84 85 86 Each of the 3 bits (0x800, 0x400, and 0x200), which are reserved 87 for future use in [RFC793], SHOULD be exported as observed in the 88 TCP headers of the packets of this Flow. 89 90 91 92 93 If exported as a single octet with reduced-size encoding, this 94 Information Element covers the low-order octet of this field (i.e, 95 bits 0x80 to 0x01), omitting the ECN Nonce Sum and the three 96 Future Use bits. A collector receiving this Information Element 97 with reduced-size encoding must not assume anything about the 98 content of these four bits. 99 100 101 102 103 Exporting Processes exporting this Information Element on behalf 104 of a Metering Process that is not capable of observing any of the 105 ECN Nonce Sum or Future Use bits SHOULD use reduced-size encoding, 106 and only export the least significant 8 bits of this Information 107 Element. 108 109 110 111 112 Note that previous revisions of this Information Element's 113 definition specified that the CWR and ECE bits must be exported as 114 zero, even if observed. Collectors should therefore not assume 115 that a value of zero for these bits in this Information Element 116 indicates the bits were never set in the observed traffic, 117 especially if these bits are zero in every Flow Record sent by a 118 given exporter.",,,[RFC793][RFC3168][RFC3540],[RFC7125],1,2014-01-03 119 7,sourceTransportPort,unsigned16,identifier,current,"The source port identifier in the transport header. 120 For the transport protocols UDP, TCP, and SCTP, this is the 121 source port number given in the respective header. This 122 field MAY also be used for future transport protocols that 123 have 16-bit source port identifiers.",,,"See [RFC768] for the definition of the UDP 124 source port field. 125 See [RFC793] for the definition of the TCP 126 source port field. 127 See [RFC4960] for the definition of SCTP. 128 129 130 131 132 Additional information on defined UDP and TCP port numbers can be 133 found at [IANA registry service-names-port-numbers].",[RFC5102],0,2013-02-18 134 8,sourceIPv4Address,ipv4Address,default,current,The IPv4 source address in the IP packet header.,,,"See [RFC791] for the definition of the IPv4 135 source address field.",[RFC5102],1,2014-02-03 136 9,sourceIPv4PrefixLength,unsigned8,,current,"The number of contiguous bits that are relevant in the 137 sourceIPv4Prefix Information Element.",bits,0-32,,[RFC5102],0,2013-02-18 138 10,ingressInterface,unsigned32,identifier,current,"The index of the IP interface where packets of this Flow 139 are being received. The value matches the value of managed 140 object 'ifIndex' as defined in [RFC2863]. 141 Note that ifIndex values are not assigned statically to an 142 interface and that the interfaces may be renumbered every 143 time the device's management system is re-initialized, as 144 specified in [RFC2863].",,,"See [RFC2863] for the definition of the 145 ifIndex object.",[RFC5102],0,2013-02-18 146 11,destinationTransportPort,unsigned16,identifier,current,"The destination port identifier in the transport header. 147 For the transport protocols UDP, TCP, and SCTP, this is the 148 destination port number given in the respective header. 149 This field MAY also be used for future transport protocols 150 that have 16-bit destination port identifiers.",,,"See [RFC768] for the definition of the UDP 151 destination port field. 152 See [RFC793] for the definition of the TCP 153 destination port field. 154 See [RFC4960] for the definition of SCTP. 155 156 157 158 159 Additional information on defined UDP and TCP port numbers can be 160 found at [IANA registry service-names-port-numbers].",[RFC5102],0,2013-02-18 161 12,destinationIPv4Address,ipv4Address,default,current,The IPv4 destination address in the IP packet header.,,,"See [RFC791] for the definition of the IPv4 162 destination address field.",[RFC5102],1,2014-02-03 163 13,destinationIPv4PrefixLength,unsigned8,,current,"The number of contiguous bits that are relevant in the 164 destinationIPv4Prefix Information Element.",bits,0-32,,[RFC5102],0,2013-02-18 165 14,egressInterface,unsigned32,identifier,current,"The index of the IP interface where packets of 166 this Flow are being sent. The value matches the value of 167 managed object 'ifIndex' as defined in [RFC2863]. 168 Note that ifIndex values are not assigned statically to an 169 interface and that the interfaces may be renumbered every 170 time the device's management system is re-initialized, as 171 specified in [RFC2863].",,,"See [RFC2863] for the definition of the 172 ifIndex object.",[RFC5102],0,2013-02-18 173 15,ipNextHopIPv4Address,ipv4Address,default,current,The IPv4 address of the next IPv4 hop.,,,,[RFC5102],1,2014-02-03 174 16,bgpSourceAsNumber,unsigned32,identifier,current,"The autonomous system (AS) number of the source IP address. 175 If AS path information for this Flow is only available as 176 an unordered AS set (and not as an ordered AS sequence), 177 then the value of this Information Element is 0.",,,"See [RFC4271] for a description of BGP-4, and 178 see [RFC1930] for the definition of the AS 179 number.",[RFC5102],0,2013-02-18 180 17,bgpDestinationAsNumber,unsigned32,identifier,current,"The autonomous system (AS) number of the destination IP 181 address. If AS path information for this Flow is only 182 available as an unordered AS set (and not as an ordered AS 183 sequence), then the value of this Information Element is 0.",,,"See [RFC4271] for a description of BGP-4, and 184 see [RFC1930] for the definition of the AS 185 number.",[RFC5102],0,2013-02-18 186 18,bgpNextHopIPv4Address,ipv4Address,default,current,The IPv4 address of the next (adjacent) BGP hop.,,,See [RFC4271] for a description of BGP-4.,[RFC5102],1,2014-02-03 187 19,postMCastPacketDeltaCount,unsigned64,deltaCounter,current,"The number of outgoing multicast packets since the 188 previous report (if any) sent for packets of this Flow 189 by a multicast daemon within the Observation Domain. 190 This property cannot necessarily be observed at the 191 Observation Point, but may be retrieved by other means.",packets,,,[RFC5102],0,2013-02-18 192 20,postMCastOctetDeltaCount,unsigned64,deltaCounter,current,"The number of octets since the previous report (if any) 193 in outgoing multicast packets sent for packets of this 194 Flow by a multicast daemon within the Observation Domain. 195 This property cannot necessarily be observed at the 196 Observation Point, but may be retrieved by other means. 197 The number of octets includes IP header(s) and IP payload.",octets,,,[RFC5102],0,2013-02-18 198 21,flowEndSysUpTime,unsigned32,,current,"The relative timestamp of the last packet of this Flow. It indicates the 199 number of milliseconds since the last (re-)initialization of the IPFIX 200 Device (sysUpTime). sysUpTime can be calculated from 201 systemInitTimeMilliseconds.",milliseconds,,,[RFC5102],1,2014-01-11 202 22,flowStartSysUpTime,unsigned32,,current,"The relative timestamp of the first packet of this Flow. It indicates 203 the number of milliseconds since the last (re-)initialization of the 204 IPFIX Device (sysUpTime). sysUpTime can be calculated from 205 systemInitTimeMilliseconds.",milliseconds,,,[RFC5102],1,2014-01-11 206 23,postOctetDeltaCount,unsigned64,deltaCounter,current,"The definition of this Information Element is identical 207 to the definition of Information Element 208 'octetDeltaCount', except that it reports a 209 potentially modified value caused by a middlebox 210 function after the packet passed the Observation Point.",octets,,,[RFC5102],0,2013-02-18 211 24,postPacketDeltaCount,unsigned64,deltaCounter,current,"The definition of this Information Element is identical 212 to the definition of Information Element 213 'packetDeltaCount', except that it reports a 214 potentially modified value caused by a middlebox 215 function after the packet passed the Observation Point.",packets,,,[RFC5102],0,2013-02-18 216 25,minimumIpTotalLength,unsigned64,,current,"Length of the smallest packet observed for this Flow. 217 The packet length includes the IP header(s) length and 218 the IP payload length.",octets,,"See [RFC791] for the specification of the IPv4 219 total length. 220 See [RFC8200] for the specification of the 221 IPv6 payload length. 222 See [RFC2675] for the specification of the 223 IPv6 jumbo payload length.",[RFC5102],0,2013-02-18 224 26,maximumIpTotalLength,unsigned64,,current,"Length of the largest packet observed for this Flow. 225 The packet length includes the IP header(s) length and 226 the IP payload length.",octets,,"See [RFC791] for the specification of the IPv4 227 total length. 228 See [RFC8200] for the specification of the 229 IPv6 payload length. 230 See [RFC2675] for the specification of the 231 IPv6 jumbo payload length.",[RFC5102],0,2013-02-18 232 27,sourceIPv6Address,ipv6Address,default,current,The IPv6 source address in the IP packet header.,,,"See [RFC8200] for the definition of the Source 233 Address field in the IPv6 header.",[RFC5102],1,2014-02-03 234 28,destinationIPv6Address,ipv6Address,default,current,The IPv6 destination address in the IP packet header.,,,"See [RFC8200] for the definition of the 235 Destination Address field in the IPv6 header.",[RFC5102],1,2014-02-03 236 29,sourceIPv6PrefixLength,unsigned8,,current,"The number of contiguous bits that are relevant in the 237 sourceIPv6Prefix Information Element.",bits,0-128,,[RFC5102],0,2013-02-18 238 30,destinationIPv6PrefixLength,unsigned8,,current,"The number of contiguous bits that are relevant in the 239 destinationIPv6Prefix Information Element.",bits,0-128,,[RFC5102],0,2013-02-18 240 31,flowLabelIPv6,unsigned32,identifier,current,The value of the IPv6 Flow Label field in the IP packet header.,,0-0xFFFFF,"See [RFC8200] for the definition of the 241 Flow Label field in the IPv6 packet header.",[RFC5102],1,2014-08-13 242 32,icmpTypeCodeIPv4,unsigned16,identifier,current,"Type and Code of the IPv4 ICMP message. The combination of 243 both values is reported as (ICMP type * 256) + ICMP code.",,,"See [RFC792] for the definition of the IPv4 244 ICMP type and code fields.",[RFC5102],0,2013-02-18 245 33,igmpType,unsigned8,identifier,current,The type field of the IGMP message.,,,"See [RFC3376] for the definition of the IGMP 246 type field.",[RFC5102],0,2013-02-18 247 34,samplingInterval,unsigned32,quantity,deprecated,"Deprecated in favor of 305 samplingPacketInterval. When using 248 sampled NetFlow, the rate at which packets are sampled -- e.g., a 249 value of 100 indicates that one of every 100 packets is sampled.",packets,,,[RFC7270],0,2014-04-04 250 35,samplingAlgorithm,unsigned8,identifier,deprecated,"Deprecated in favor of 304 selectorAlgorithm. The type of 251 algorithm used for sampled NetFlow: 252 253 254 255 256 1 - Deterministic Sampling, 257 2 - Random Sampling. 258 259 260 261 262 The values are not compatible with the selectorAlgorithm IE, where 263 ""Deterministic"" has been replaced by ""Systematic count-based"" (1) 264 or ""Systematic time-based"" (2), and ""Random"" is (3). Conversion 265 is required; see [Packet Sampling (PSAMP) Parameters.]",,,,[RFC7270],0,2014-04-04 266 36,flowActiveTimeout,unsigned16,,current,"The number of seconds after which an active Flow is timed out 267 anyway, even if there is still a continuous flow of packets.",seconds,,,[RFC5102],0,2013-02-18 268 37,flowIdleTimeout,unsigned16,,current,"A Flow is considered to be timed out if no packets belonging 269 to the Flow have been observed for the number of seconds 270 specified by this field.",seconds,,,[RFC5102],0,2013-02-18 271 38,engineType,unsigned8,identifier,deprecated,"Type of flow switching engine in a router/switch: 272 273 274 275 RP = 0, 276 VIP/Line card = 1, 277 PFC/DFC = 2. 278 279 280 281 Reserved for internal use on the Collector.",,,,[RFC7270],0,2014-04-04 282 39,engineId,unsigned8,identifier,deprecated,"Versatile Interface Processor (VIP) or line card slot number of the flow switching engine in a 283 router/switch. Reserved for internal use on the Collector.",,,,[RFC7270],0,2014-04-04 284 40,exportedOctetTotalCount,unsigned64,totalCounter,current,"The total number of octets that the Exporting Process 285 has sent since the Exporting Process (re-)initialization 286 to a particular Collecting Process. 287 The value of this Information Element is calculated by 288 summing up the IPFIX Message Header length values of all 289 IPFIX Messages that were successfully sent to the Collecting 290 Process. The reported number excludes octets in the IPFIX 291 Message that carries the counter value. 292 If this Information Element is sent to a particular 293 Collecting Process, then by default it specifies the number 294 of octets sent to this Collecting Process.",octets,,,[RFC5102],0,2013-02-18 295 41,exportedMessageTotalCount,unsigned64,totalCounter,current,"The total number of IPFIX Messages that the Exporting Process 296 has sent since the Exporting Process (re-)initialization to 297 a particular Collecting Process. 298 The reported number excludes the IPFIX Message that carries 299 the counter value. 300 If this Information Element is sent to a particular 301 Collecting Process, then by default it specifies the number 302 of IPFIX Messages sent to this Collecting Process.",messages,,,[RFC5102],0,2013-02-18 303 42,exportedFlowRecordTotalCount,unsigned64,totalCounter,current,"The total number of Flow Records that the Exporting 304 Process has sent as Data Records since the Exporting 305 Process (re-)initialization to a particular Collecting 306 Process. The reported number excludes Flow Records in 307 the IPFIX Message that carries the counter value. 308 If this Information Element is sent to a particular 309 Collecting Process, then by default it specifies the number 310 of Flow Records sent to this process.",flows,,,[RFC5102],0,2013-02-18 311 43,ipv4RouterSc,ipv4Address,default,deprecated,"This is a platform-specific field for the Catalyst 5000/Catalyst 6000 312 family. It is used to store the address of a router that is being 313 shortcut when performing MultiLayer Switching.",,,[CCO-MLS] describes MultiLayer Switching.,[RFC7270],0,2014-04-04 314 44,sourceIPv4Prefix,ipv4Address,default,current,IPv4 source address prefix.,,,,[RFC5102],0,2013-02-18 315 45,destinationIPv4Prefix,ipv4Address,default,current,IPv4 destination address prefix.,,,,[RFC5102],0,2013-02-18 316 46,mplsTopLabelType,unsigned8,identifier,current,"This field identifies the control protocol that allocated the 317 top-of-stack label. Values for this field are listed in the 318 MPLS label type registry. See 319 [http://www.iana.org/assignments/ipfix/ipfix.xml#ipfix-mpls-label-type]",,,"See [RFC3031] for the MPLS label structure. 320 See [RFC4364] for the association of MPLS 321 labels with Virtual Private Networks (VPNs). 322 See [RFC4271] for BGP and BGP routing. 323 See [RFC5036] for Label Distribution Protocol 324 (LDP). 325 See the list of MPLS label types assigned by IANA at [IANA registry mpls-label-values].",[RFC5102],0,2013-02-18 326 47,mplsTopLabelIPv4Address,ipv4Address,default,current,"The IPv4 address of the system that the MPLS top label will 327 cause this Flow to be forwarded to.",,,"See [RFC3031] for the association between MPLS 328 labels and IP addresses.",[RFC5102],1,2014-02-03 329 48,samplerId,unsigned8,identifier,deprecated,"Deprecated in favor of 302 selectorId. The unique identifier 330 associated with samplerName.",,,,[RFC7270],0,2014-04-04 331 49,samplerMode,unsigned8,identifier,deprecated,"Deprecated in favor of 304 selectorAlgorithm. The values are not 332 compatible: selectorAlgorithm=3 is random sampling. The type of 333 algorithm used for sampling data: 1 - Deterministic, 2 - Random 334 Sampling. Use with samplerRandomInterval.",,,,[RFC7270],0,2014-04-04 335 50,samplerRandomInterval,unsigned32,quantity,deprecated,"Deprecated in favor of 305 samplingPacketInterval. Packet 336 interval at which to sample -- in case of random sampling. Used in 337 connection with the samplerMode 0x02 (random sampling) value.",,,,[RFC7270],0,2014-04-04 338 51,classId,unsigned8,identifier,deprecated,"Deprecated in favor of 302 selectorId. Characterizes the traffic 339 class, i.e., QoS treatment.",,,,[RFC7270],0,2014-04-04 340 52,minimumTTL,unsigned8,,current,Minimum TTL value observed for any packet in this Flow.,hops,,"See [RFC791] for the definition of the IPv4 341 Time to Live field. 342 See [RFC8200] for the definition of the IPv6 343 Hop Limit field.",[RFC5102],0,2013-02-18 344 53,maximumTTL,unsigned8,,current,Maximum TTL value observed for any packet in this Flow.,hops,,"See [RFC791] for the definition of the IPv4 345 Time to Live field. 346 See [RFC8200] for the definition of the IPv6 347 Hop Limit field.",[RFC5102],0,2013-02-18 348 54,fragmentIdentification,unsigned32,identifier,current,"The value of the Identification field 349 in the IPv4 packet header or in the IPv6 Fragment header, 350 respectively. The value is 0 for IPv6 if there is 351 no fragment header.",,,"See [RFC791] for the definition of the IPv4 352 Identification field. 353 See [RFC8200] for the definition of the 354 Identification field in the IPv6 Fragment header.",[RFC5102],0,2013-02-18 355 55,postIpClassOfService,unsigned8,identifier,current,"The definition of this Information Element is identical 356 to the definition of Information Element 357 'ipClassOfService', except that it reports a 358 potentially modified value caused by a middlebox 359 function after the packet passed the Observation Point.",,,"See [RFC791] for the definition of the IPv4 360 TOS field. 361 See [RFC8200] for the definition of the IPv6 362 Traffic Class field. 363 See [RFC3234] for the definition of 364 middleboxes.",[RFC5102],0,2013-02-18 365 56,sourceMacAddress,macAddress,default,current,The IEEE 802 source MAC address field.,,,See IEEE.802-3.2002.,[RFC5102],1,2014-02-03 366 57,postDestinationMacAddress,macAddress,default,current,"The definition of this Information Element is identical 367 to the definition of Information Element 368 'destinationMacAddress', except that it reports a 369 potentially modified value caused by a middlebox 370 function after the packet passed the Observation Point.",,,See IEEE.802-3.2002.,[RFC5102],1,2014-02-03 371 58,vlanId,unsigned16,identifier,current,"Virtual LAN identifier associated with ingress interface. For dot1q vlans, see 243 372 dot1qVlanId.",,,See IEEE.802-1Q.2003.,[RFC5102],0,2013-02-18 373 59,postVlanId,unsigned16,identifier,current,"Virtual LAN identifier associated with egress interface. For postdot1q vlans, see 254, postDot1qVlanId.",,,See IEEE.802-1Q.2003.,[RFC5102],0,2013-02-18 374 60,ipVersion,unsigned8,identifier,current,The IP version field in the IP packet header.,,,"See [RFC791] for the definition of the version 375 field in the IPv4 packet header. 376 See [RFC8200] for the definition of the 377 version field in the IPv6 packet header. 378 Additional information on defined version numbers can be found at 379 [IANA registry version-numbers].",[RFC5102],0,2013-02-18 380 61,flowDirection,unsigned8,identifier,current,"The direction of the Flow observed at the Observation 381 Point. There are only two values defined. 382 383 384 385 0x00: ingress flow 386 0x01: egress flow",,,,[RFC5102],0,2013-02-18 387 62,ipNextHopIPv6Address,ipv6Address,default,current,The IPv6 address of the next IPv6 hop.,,,,[RFC5102],1,2014-02-03 388 63,bgpNextHopIPv6Address,ipv6Address,default,current,The IPv6 address of the next (adjacent) BGP hop.,,,See [RFC4271] for a description of BGP-4.,[RFC5102],1,2014-02-03 389 64,ipv6ExtensionHeaders,unsigned32,flags,current,"IPv6 extension headers observed in packets of this Flow. 390 The information is encoded in a set of bit fields. For 391 each IPv6 option header, there is a bit in this set. 392 The bit is set to 1 if any observed packet of this Flow 393 contains the corresponding IPv6 extension header. 394 Otherwise, if no observed packet of this Flow contained 395 the respective IPv6 extension header, the value of the 396 corresponding bit is 0. 397 398 399 400 0 1 2 3 4 5 6 7 401 +-----+-----+-----+-----+-----+-----+-----+-----+ 402 | DST | HOP | Res | UNK |FRA0 | RH |FRA1 | Res | ... 403 +-----+-----+-----+-----+-----+-----+-----+-----+ 404 405 8 9 10 11 12 13 14 15 406 +-----+-----+-----+-----+-----+-----+-----+-----+ 407 ... | Reserved | MOB | ESP | AH | PAY | ... 408 +-----+-----+-----+-----+-----+-----+-----+-----+ 409 410 16 17 18 19 20 21 22 23 411 +-----+-----+-----+-----+-----+-----+-----+-----+ 412 ... | Reserved | ... 413 +-----+-----+-----+-----+-----+-----+-----+-----+ 414 415 24 25 26 27 28 29 30 31 416 +-----+-----+-----+-----+-----+-----+-----+-----+ 417 ... | Reserved | 418 +-----+-----+-----+-----+-----+-----+-----+-----+ 419 420 Bit IPv6 Option Description 421 422 0, DST 60 Destination option header 423 1, HOP 0 Hop-by-hop option header 424 2, Res Reserved 425 3, UNK Unknown Layer 4 header 426 (compressed, encrypted, not supported) 427 4, FRA0 44 Fragment header - first fragment 428 5, RH 43 Routing header 429 6, FRA1 44 Fragmentation header - not first fragment 430 7, Res Reserved 431 8 to 11 Reserved 432 12, MOB 135 IPv6 mobility [RFC3775] 433 13, ESP 50 Encrypted security payload 434 14, AH 51 Authentication Header 435 15, PAY 108 Payload compression header 436 16 to 31 Reserved",,,"See [RFC8200] for the general definition of 437 IPv6 extension headers and for the specification of the hop-by-hop 438 options header, the routing header, the fragment header, and the 439 destination options header. 440 See [RFC4302] for the specification of the 441 authentication header. 442 See [RFC4303] for the specification of the 443 encapsulating security payload. 444 445 The diagram provided in [RFC5102] is incorrect. 446 The diagram in this registry is taken from Errata 1738. See [RFC Errata 1738]",[RFC5102],0,2013-02-18 447 65-69,Assigned for NetFlow v9 compatibility,,,,,,,[RFC3954],[RFC5102],0,2013-02-18 448 70,mplsTopLabelStackSection,octetArray,default,current,"The Label, Exp, and S fields from the top MPLS label 449 stack entry, i.e., from the last label that was pushed. 450 451 452 453 454 The size of this Information Element is 3 octets. 455 456 457 458 0 1 2 459 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 460 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 461 | Label | Exp |S| 462 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 463 464 Label: Label Value, 20 bits 465 Exp: Experimental Use, 3 bits 466 S: Bottom of Stack, 1 bit",,,See [RFC3032].,[RFC5102],1,2014-02-03 467 71,mplsLabelStackSection2,octetArray,default,current,"The Label, Exp, and S fields from the label stack entry that 468 was pushed immediately before the label stack entry that would 469 be reported by mplsTopLabelStackSection. See the definition of 470 mplsTopLabelStackSection for further details. 471 472 473 474 475 The size of this Information Element is 3 octets.",,,See [RFC3032].,[RFC5102],1,2014-02-03 476 72,mplsLabelStackSection3,octetArray,default,current,"The Label, Exp, and S fields from the label stack entry that 477 was pushed immediately before the label stack entry that would 478 be reported by mplsLabelStackSection2. See the definition of 479 mplsTopLabelStackSection for further details. 480 481 482 483 484 The size of this Information Element is 3 octets.",,,See [RFC3032].,[RFC5102],1,2014-02-03 485 73,mplsLabelStackSection4,octetArray,default,current,"The Label, Exp, and S fields from the label stack entry that 486 was pushed immediately before the label stack entry that would 487 be reported by mplsLabelStackSection3. See the definition of 488 mplsTopLabelStackSection for further details. 489 490 491 492 493 The size of this Information Element is 3 octets.",,,See [RFC3032].,[RFC5102],1,2014-02-03 494 74,mplsLabelStackSection5,octetArray,default,current,"The Label, Exp, and S fields from the label stack entry that 495 was pushed immediately before the label stack entry that would 496 be reported by mplsLabelStackSection4. See the definition of 497 mplsTopLabelStackSection for further details. 498 499 500 501 502 The size of this Information Element is 3 octets.",,,See [RFC3032].,[RFC5102],1,2014-02-03 503 75,mplsLabelStackSection6,octetArray,default,current,"The Label, Exp, and S fields from the label stack entry that 504 was pushed immediately before the label stack entry that would 505 be reported by mplsLabelStackSection5. See the definition of 506 mplsTopLabelStackSection for further details. 507 508 509 510 511 The size of this Information Element is 3 octets.",,,See [RFC3032].,[RFC5102],1,2014-02-03 512 76,mplsLabelStackSection7,octetArray,default,current,"The Label, Exp, and S fields from the label stack entry that 513 was pushed immediately before the label stack entry that would 514 be reported by mplsLabelStackSection6. See the definition of 515 mplsTopLabelStackSection for further details. 516 517 518 519 520 The size of this Information Element is 3 octets.",,,See [RFC3032].,[RFC5102],1,2014-02-03 521 77,mplsLabelStackSection8,octetArray,default,current,"The Label, Exp, and S fields from the label stack entry that 522 was pushed immediately before the label stack entry that would 523 be reported by mplsLabelStackSection7. See the definition of 524 mplsTopLabelStackSection for further details. 525 526 527 528 529 The size of this Information Element is 3 octets.",,,See [RFC3032].,[RFC5102],1,2014-02-03 530 78,mplsLabelStackSection9,octetArray,default,current,"The Label, Exp, and S fields from the label stack entry that 531 was pushed immediately before the label stack entry that would 532 be reported by mplsLabelStackSection8. See the definition of 533 mplsTopLabelStackSection for further details. 534 535 536 537 538 The size of this Information Element is 3 octets.",,,See [RFC3032].,[RFC5102],1,2014-02-03 539 79,mplsLabelStackSection10,octetArray,default,current,"The Label, Exp, and S fields from the label stack entry that 540 was pushed immediately before the label stack entry that would 541 be reported by mplsLabelStackSection9. See the definition of 542 mplsTopLabelStackSection for further details. 543 544 545 546 547 The size of this Information Element is 3 octets.",,,See [RFC3032].,[RFC5102],1,2014-02-03 548 80,destinationMacAddress,macAddress,default,current,The IEEE 802 destination MAC address field.,,,See IEEE.802-3.2002.,[RFC5102],1,2014-02-03 549 81,postSourceMacAddress,macAddress,default,current,"The definition of this Information Element is identical 550 to the definition of Information Element 551 'sourceMacAddress', except that it reports a 552 potentially modified value caused by a middlebox 553 function after the packet passed the Observation Point.",,,See IEEE.802-3.2002.,[RFC5102],1,2014-02-03 554 82,interfaceName,string,default,current,"A short name uniquely describing an interface, eg ""Eth1/0"".",,,See [RFC2863] for the definition of the ifName object.,[ipfix-iana_at_cisco.com],0,2013-02-18 555 83,interfaceDescription,string,default,current,"The description of an interface, eg ""FastEthernet 1/0"" or ""ISP 556 connection"".",,,See [RFC2863] for the definition of the ifDescr object.,[ipfix-iana_at_cisco.com],0,2013-02-18 557 84,samplerName,string,,deprecated,"Deprecated in favor of 335 selectorName. Name of the flow 558 sampler.",,,,[RFC7270],0,2014-04-04 559 85,octetTotalCount,unsigned64,totalCounter,current,"The total number of octets in incoming packets 560 for this Flow at the Observation Point since the Metering 561 Process (re-)initialization for this Observation Point. The 562 number of octets includes IP header(s) and IP payload.",octets,,,[RFC5102],0,2013-02-18 563 86,packetTotalCount,unsigned64,totalCounter,current,"The total number of incoming packets for this Flow 564 at the Observation Point since the Metering Process 565 (re-)initialization for this Observation Point.",packets,,,[RFC5102],0,2013-02-18 566 87,flagsAndSamplerId,unsigned32,identifier,deprecated,"Flow flags and the value of the sampler ID (samplerId) combined in 567 one bitmapped field. Reserved for internal use on the Collector.",,,,[RFC7270],0,2014-04-04 568 88,fragmentOffset,unsigned16,quantity,current,"The value of the IP fragment offset field in the 569 IPv4 packet header or the IPv6 Fragment header, 570 respectively. The value is 0 for IPv6 if there is 571 no fragment header.",,0-0x1FFF,"See [RFC791] for the specification of the 572 fragment offset in the IPv4 header. 573 See [RFC8200] for the specification of the 574 fragment offset in the IPv6 Fragment header.",[RFC5102],1,2014-08-13 575 89,forwardingStatus,unsigned8,identifier,current,"This Information Element describes the forwarding status of the 576 flow and any attached reasons. 577 578 579 580 581 The layout of the encoding is as follows: 582 583 584 585 MSB - 0 1 2 3 4 5 6 7 - LSB 586 +---+---+---+---+---+---+---+---+ 587 | Status| Reason code or flags | 588 +---+---+---+---+---+---+---+---+ 589 590 591 592 See the Forwarding Status sub-registries at [http://www.iana.org/assignments/ipfix/ipfix.xhtml#forwarding-status]. 593 594 595 596 Examples: 597 598 value : 0x40 = 64 599 binary: 01000000 600 decode: 01 -> Forward 601 000000 -> No further information 602 603 value : 0x89 = 137 604 binary: 10001001 605 decode: 10 -> Drop 606 001001 -> Bad TTL",,,"See ""NetFlow Version 9 Flow-Record Format"" [CCO-NF9FMT].",[RFC7270][RFC Errata 5262],2,2018-02-21 607 90,mplsVpnRouteDistinguisher,octetArray,default,current,"The value of the VPN route distinguisher of a corresponding 608 entry in a VPN routing and forwarding table. Route 609 distinguisher ensures that the same address can be used in 610 several different MPLS VPNs and that it is possible for BGP to 611 carry several completely different routes to that address, one 612 for each VPN. According to [RFC4364], the size of 613 mplsVpnRouteDistinguisher is 8 octets. However, in [RFC4382] an 614 octet string with flexible length was chosen for representing a 615 VPN route distinguisher by object MplsL3VpnRouteDistinguisher. 616 This choice was made in order to be open to future changes of 617 the size. This idea was adopted when choosing octetArray as 618 abstract data type for this Information Element. The maximum 619 length of this Information Element is 256 octets.",,,"See [RFC4364] for the specification of the 620 route distinguisher. See [RFC4382] for the 621 specification of the MPLS/BGP Layer 3 Virtual Private Network (VPN) 622 Management Information Base.",[RFC5102],1,2014-02-03 623 91,mplsTopLabelPrefixLength,unsigned8,quantity,current,"The prefix length of the subnet of the mplsTopLabelIPv4Address that 624 the MPLS top label will cause the Flow to be forwarded to.",bits,0-32,"See [RFC3031] for the association between 625 MPLS labels and prefix lengths.",[ipfix-iana_at_cisco.com],1,2014-08-13 626 92,srcTrafficIndex,unsigned32,identifier,current,BGP Policy Accounting Source Traffic Index.,,,BGP policy accounting as described in [CCO-BGPPOL].,[RFC7270],0,2014-04-04 627 93,dstTrafficIndex,unsigned32,identifier,current,BGP Policy Accounting Destination Traffic Index.,,,BGP policy accounting as described in [CCO-BGPPOL].,[RFC7270],0,2014-04-04 628 94,applicationDescription,string,default,current,Specifies the description of an application.,,,,[RFC6759],1,2014-02-03 629 95,applicationId,octetArray,default,current,Specifies an Application ID per [RFC6759].,,,See section 4 of [RFC6759] for the applicationId Information Element Specification.,[RFC6759],1,2014-02-03 630 96,applicationName,string,default,current,Specifies the name of an application.,,,,[RFC6759],0,2013-02-18 631 97,Assigned for NetFlow v9 compatibility,,,,,,,[RFC3954],[RFC5102],0,2013-02-18 632 98,postIpDiffServCodePoint,unsigned8,identifier,current,"The definition of this Information Element is identical to the 633 definition of Information Element 'ipDiffServCodePoint', except 634 that it reports a potentially modified value caused by a 635 middlebox function after the packet passed the Observation 636 Point.",,0-63,"See [RFC3260] for the definition of the Differentiated 637 Services Field. See section 5.3.2 of [RFC1812] and 638 [RFC791] for the definition of the IPv4 TOS field. See 639 [RFC8200] for the definition of the IPv6 Traffic Class 640 field. See the IPFIX Information Model [RFC5102] for the 641 'ipDiffServCodePoint' specification.",[ipfix-iana_at_cisco.com],0,2013-02-18 642 99,multicastReplicationFactor,unsigned32,quantity,current,"The amount of multicast replication that's applied to a traffic 643 stream.",,,"See [RFC1112] for the specification of reserved IPv4 644 multicast addresses. See [RFC4291] for the 645 specification of reserved IPv6 multicast addresses.",[ipfix-iana_at_cisco.com],0,2013-02-18 646 100,className,string,,deprecated,"Deprecated in favor of 335 selectorName. Traffic Class Name, 647 associated with the classId Information Element.",,,,[RFC7270],0,2014-04-04 648 101,classificationEngineId,unsigned8,identifier,current,"A unique identifier for the engine that determined the 649 Selector ID. Thus, the Classification Engine ID defines 650 the context for the Selector ID. The Classification 651 Engine can be considered a specific registry for 652 application assignments. 653 654 655 656 657 Values for this field are listed in the Classification 658 Engine IDs registry. See 659 [http://www.iana.org/assignments/ipfix/ipfix.xml#classification-engine-ids]",,,,[RFC6759],0,2013-02-18 660 102,layer2packetSectionOffset,unsigned16,quantity,deprecated,"Deprecated in favor of 409 sectionOffset. Layer 2 packet 661 section offset. Potentially a generic packet section offset.",,,,[RFC7270],0,2014-04-04 662 103,layer2packetSectionSize,unsigned16,quantity,deprecated,"Deprecated in favor of 312 dataLinkFrameSize. Layer 2 packet 663 section size. Potentially a generic packet section size.",,,,[RFC7270],0,2014-04-04 664 104,layer2packetSectionData,octetArray,,deprecated,"Deprecated in favor of 315 dataLinkFrameSection. Layer 2 packet 665 section data.",,,,[RFC7270],0,2014-04-04 666 105-127,Assigned for NetFlow v9 compatibility,,,,,,,[RFC3954],[RFC5102],0,2013-02-18 667 128,bgpNextAdjacentAsNumber,unsigned32,identifier,current,"The autonomous system (AS) number of the first AS in the AS 668 path to the destination IP address. The path is deduced 669 by looking up the destination IP address of the Flow in the 670 BGP routing information base. If AS path information for 671 this Flow is only available as an unordered AS set (and not 672 as an ordered AS sequence), then the value of this Information 673 Element is 0.",,,"See [RFC4271] for a description of BGP-4, and 674 see [RFC1930] for the definition of the AS 675 number.",[RFC5102],0,2013-02-18 676 129,bgpPrevAdjacentAsNumber,unsigned32,identifier,current,"The autonomous system (AS) number of the last AS in the AS 677 path from the source IP address. The path is deduced 678 by looking up the source IP address of the Flow in the BGP 679 routing information base. If AS path information for this 680 Flow is only available as an unordered AS set (and not as 681 an ordered AS sequence), then the value of this Information 682 Element is 0. In case of BGP asymmetry, the 683 bgpPrevAdjacentAsNumber might not be able to report the correct 684 value.",,,"See [RFC4271] for a description of BGP-4, and 685 see [RFC1930] for the definition of the AS 686 number.",[RFC5102],0,2013-02-18 687 130,exporterIPv4Address,ipv4Address,default,current,"The IPv4 address used by the Exporting Process. This is used 688 by the Collector to identify the Exporter in cases where the 689 identity of the Exporter may have been obscured by the use of 690 a proxy.",,,,[RFC5102],1,2014-02-03 691 131,exporterIPv6Address,ipv6Address,default,current,"The IPv6 address used by the Exporting Process. This is used 692 by the Collector to identify the Exporter in cases where the 693 identity of the Exporter may have been obscured by the use of 694 a proxy.",,,,[RFC5102],1,2014-02-03 695 132,droppedOctetDeltaCount,unsigned64,deltaCounter,current,"The number of octets since the previous report (if any) 696 in packets of this Flow dropped by packet treatment. 697 The number of octets includes IP header(s) and IP payload.",octets,,,[RFC5102],0,2013-02-18 698 133,droppedPacketDeltaCount,unsigned64,deltaCounter,current,"The number of packets since the previous report (if any) 699 of this Flow dropped by packet treatment.",packets,,,[RFC5102],0,2013-02-18 700 134,droppedOctetTotalCount,unsigned64,totalCounter,current,"The total number of octets in packets of this Flow dropped 701 by packet treatment since the Metering Process 702 (re-)initialization for this Observation Point. 703 The number of octets includes IP header(s) and IP payload.",octets,,,[RFC5102],0,2013-02-18 704 135,droppedPacketTotalCount,unsigned64,totalCounter,current,"The number of packets of this Flow dropped by packet 705 treatment since the Metering Process 706 (re-)initialization for this Observation Point.",packets,,,[RFC5102],0,2013-02-18 707 136,flowEndReason,unsigned8,identifier,current,"The reason for Flow termination. The range of values includes 708 the following: 709 710 711 712 0x01: idle timeout 713 The Flow was terminated because it was considered to be 714 idle. 715 716 0x02: active timeout 717 The Flow was terminated for reporting purposes while it was 718 still active, for example, after the maximum lifetime of 719 unreported Flows was reached. 720 721 0x03: end of Flow detected 722 The Flow was terminated because the Metering Process 723 detected signals indicating the end of the Flow, 724 for example, the TCP FIN flag. 725 726 0x04: forced end 727 The Flow was terminated because of some external event, 728 for example, a shutdown of the Metering Process initiated 729 by a network management application. 730 731 0x05: lack of resources 732 The Flow was terminated because of lack of resources 733 available to the Metering Process and/or the Exporting 734 Process.",,,,[RFC5102],0,2013-02-18 735 137,commonPropertiesId,unsigned64,identifier,current,"An identifier of a set of common properties that is 736 unique per Observation Domain and Transport Session. 737 Typically, this Information Element is used to link to 738 information reported in separate Data Records.",,,,[RFC5102],0,2013-02-18 739 138,observationPointId,unsigned64,identifier,current,"An identifier of an Observation Point that is unique per 740 Observation Domain. It is RECOMMENDED that this identifier is 741 also unique per IPFIX Device. Typically, this Information 742 Element is used for limiting the scope of other Information 743 Elements.",,,,[RFC5102][ipfix-iana_at_cisco.com],1,2013-04-11 744 139,icmpTypeCodeIPv6,unsigned16,identifier,current,"Type and Code of the IPv6 ICMP message. The combination of 745 both values is reported as (ICMP type * 256) + ICMP code.",,,"See [RFC4443] for the definition of the IPv6 746 ICMP type and code fields.",[RFC5102],0,2013-02-18 747 140,mplsTopLabelIPv6Address,ipv6Address,default,current,"The IPv6 address of the system that the MPLS top label will 748 cause this Flow to be forwarded to.",,,"See [RFC3031] for the association between MPLS 749 labels and IP addresses.",[RFC5102],1,2014-02-03 750 141,lineCardId,unsigned32,identifier,current,"An identifier of a line card that is unique per IPFIX 751 Device hosting an Observation Point. Typically, this 752 Information Element is used for limiting the scope 753 of other Information Elements.",,,,[RFC5102],0,2013-02-18 754 142,portId,unsigned32,identifier,current,"An identifier of a line port that is unique per IPFIX 755 Device hosting an Observation Point. Typically, this 756 Information Element is used for limiting the scope 757 of other Information Elements.",,,,[RFC5102],0,2013-02-18 758 143,meteringProcessId,unsigned32,identifier,current,"An identifier of a Metering Process that is unique per 759 IPFIX Device. Typically, this Information Element is used 760 for limiting the scope of other Information Elements. 761 Note that process identifiers are typically assigned 762 dynamically. 763 The Metering Process may be re-started with a different ID.",,,,[RFC5102],0,2013-02-18 764 144,exportingProcessId,unsigned32,identifier,current,"An identifier of an Exporting Process that is unique per 765 IPFIX Device. Typically, this Information Element is used 766 for limiting the scope of other Information Elements. 767 Note that process identifiers are typically assigned 768 dynamically. The Exporting Process may be re-started 769 with a different ID.",,,,[RFC5102],0,2013-02-18 770 145,templateId,unsigned16,identifier,current,"An identifier of a Template that is locally unique within a 771 combination of a Transport session and an Observation Domain. 772 773 774 775 776 Template IDs 0-255 are reserved for Template Sets, Options 777 Template Sets, and other reserved Sets yet to be created. 778 Template IDs of Data Sets are numbered from 256 to 65535. 779 780 781 782 783 Typically, this Information Element is used for limiting 784 the scope of other Information Elements. 785 Note that after a re-start of the Exporting Process Template 786 identifiers may be re-assigned.",,,,[RFC5102],0,2013-02-18 787 146,wlanChannelId,unsigned8,identifier,current,The identifier of the 802.11 (Wi-Fi) channel used.,,,See IEEE.802-11.1999.,[RFC5102],0,2013-02-18 788 147,wlanSSID,string,default,current,"The Service Set IDentifier (SSID) identifying an 802.11 789 (Wi-Fi) network used. According to IEEE.802-11.1999, the 790 SSID is encoded into a string of up to 32 characters.",,,See IEEE.802-11.1999.,[RFC5102],0,2013-02-18 791 148,flowId,unsigned64,identifier,current,"An identifier of a Flow that is unique within an Observation 792 Domain. This Information Element can be used to distinguish 793 between different Flows if Flow Keys such as IP addresses and 794 port numbers are not reported or are reported in separate 795 records.",,,,[RFC5102],0,2013-02-18 796 149,observationDomainId,unsigned32,identifier,current,"An identifier of an Observation Domain that is locally 797 unique to an Exporting Process. The Exporting Process uses 798 the Observation Domain ID to uniquely identify to the 799 Collecting Process the Observation Domain where Flows 800 were metered. It is RECOMMENDED that this identifier is 801 also unique per IPFIX Device. 802 803 804 805 806 A value of 0 indicates that no specific Observation Domain 807 is identified by this Information Element. 808 809 810 811 812 Typically, this Information Element is used for limiting 813 the scope of other Information Elements.",,,,[RFC5102],0,2013-02-18 814 150,flowStartSeconds,dateTimeSeconds,default,current,The absolute timestamp of the first packet of this Flow.,seconds,,,[RFC5102],0,2013-02-18 815 151,flowEndSeconds,dateTimeSeconds,default,current,The absolute timestamp of the last packet of this Flow.,seconds,,,[RFC5102],0,2013-02-18 816 152,flowStartMilliseconds,dateTimeMilliseconds,default,current,The absolute timestamp of the first packet of this Flow.,milliseconds,,,[RFC5102],0,2013-02-18 817 153,flowEndMilliseconds,dateTimeMilliseconds,default,current,The absolute timestamp of the last packet of this Flow.,milliseconds,,,[RFC5102],0,2013-02-18 818 154,flowStartMicroseconds,dateTimeMicroseconds,default,current,The absolute timestamp of the first packet of this Flow.,microseconds,,,[RFC5102],0,2013-02-18 819 155,flowEndMicroseconds,dateTimeMicroseconds,default,current,The absolute timestamp of the last packet of this Flow.,microseconds,,,[RFC5102],0,2013-02-18 820 156,flowStartNanoseconds,dateTimeNanoseconds,default,current,The absolute timestamp of the first packet of this Flow.,nanoseconds,,,[RFC5102],0,2013-02-18 821 157,flowEndNanoseconds,dateTimeNanoseconds,default,current,The absolute timestamp of the last packet of this Flow.,nanoseconds,,,[RFC5102],0,2013-02-18 822 158,flowStartDeltaMicroseconds,unsigned32,,current,"This is a relative timestamp only valid within the scope 823 of a single IPFIX Message. It contains the negative time 824 offset of the first observed packet of this Flow relative 825 to the export time specified in the IPFIX Message Header.",microseconds,,"See the [IPFIX protocol 826 specification] for the definition of the IPFIX Message Header.",[RFC5102],0,2013-02-18 827 159,flowEndDeltaMicroseconds,unsigned32,,current,"This is a relative timestamp only valid within the scope 828 of a single IPFIX Message. It contains the negative time 829 offset of the last observed packet of this Flow relative 830 to the export time specified in the IPFIX Message Header.",microseconds,,"See the [IPFIX protocol 831 specification] for the definition of the IPFIX Message Header.",[RFC5102],0,2013-02-18 832 160,systemInitTimeMilliseconds,dateTimeMilliseconds,default,current,"The absolute timestamp of the last (re-)initialization of the 833 IPFIX Device.",milliseconds,,,[RFC5102],0,2013-02-18 834 161,flowDurationMilliseconds,unsigned32,,current,"The difference in time between the first observed packet 835 of this Flow and the last observed packet of this Flow.",milliseconds,,,[RFC5102],0,2013-02-18 836 162,flowDurationMicroseconds,unsigned32,,current,"The difference in time between the first observed packet 837 of this Flow and the last observed packet of this Flow.",microseconds,,,[RFC5102],0,2013-02-18 838 163,observedFlowTotalCount,unsigned64,totalCounter,current,"The total number of Flows observed in the Observation Domain 839 since the Metering Process (re-)initialization for this 840 Observation Point.",flows,,,[RFC5102],0,2013-02-18 841 164,ignoredPacketTotalCount,unsigned64,totalCounter,current,"The total number of observed IP packets that the 842 Metering Process did not process since the 843 (re-)initialization of the Metering Process.",packets,,,[RFC5102],0,2013-02-18 844 165,ignoredOctetTotalCount,unsigned64,totalCounter,current,"The total number of octets in observed IP packets 845 (including the IP header) that the Metering Process 846 did not process since the (re-)initialization of the 847 Metering Process.",octets,,,[RFC5102],0,2013-02-18 848 166,notSentFlowTotalCount,unsigned64,totalCounter,current,"The total number of Flow Records that were generated by the 849 Metering Process and dropped by the Metering Process or 850 by the Exporting Process instead of being sent to the 851 Collecting Process. There are several potential reasons for 852 this including resource shortage and special Flow export 853 policies.",flows,,,[RFC5102],0,2013-02-18 854 167,notSentPacketTotalCount,unsigned64,totalCounter,current,"The total number of packets in Flow Records that were 855 generated by the Metering Process and dropped 856 by the Metering Process or by the Exporting Process 857 instead of being sent to the Collecting Process. 858 There are several potential reasons for this including 859 resource shortage and special Flow export policies.",packets,,,[RFC5102],0,2013-02-18 860 168,notSentOctetTotalCount,unsigned64,totalCounter,current,"The total number of octets in packets in Flow Records 861 that were generated by the Metering Process and 862 dropped by the Metering Process or by the Exporting 863 Process instead of being sent to the Collecting Process. 864 There are several potential reasons for this including 865 resource shortage and special Flow export policies.",octets,,,[RFC5102],0,2013-02-18 866 169,destinationIPv6Prefix,ipv6Address,default,current,IPv6 destination address prefix.,,,,[RFC5102],0,2013-02-18 867 170,sourceIPv6Prefix,ipv6Address,default,current,IPv6 source address prefix.,,,,[RFC5102],0,2013-02-18 868 171,postOctetTotalCount,unsigned64,totalCounter,current,"The definition of this Information Element is identical 869 to the definition of Information Element 870 'octetTotalCount', except that it reports a 871 potentially modified value caused by a middlebox 872 function after the packet passed the Observation Point.",octets,,,[RFC5102],0,2013-02-18 873 172,postPacketTotalCount,unsigned64,totalCounter,current,"The definition of this Information Element is identical 874 to the definition of Information Element 875 'packetTotalCount', except that it reports a 876 potentially modified value caused by a middlebox 877 function after the packet passed the Observation Point.",packets,,,[RFC5102],0,2013-02-18 878 173,flowKeyIndicator,unsigned64,flags,current,"This set of bit fields is used for marking the Information 879 Elements of a Data Record that serve as Flow Key. Each bit 880 represents an Information Element in the Data Record, with 881 the n-th least significant bit representing the n-th Information 882 Element. 883 A bit set to value 1 indicates that the corresponding 884 Information Element is a Flow Key of the reported Flow. 885 A bit set to value 0 indicates that this is not the case. 886 887 888 889 890 If the Data Record contains more than 64 Information Elements, 891 the corresponding Template SHOULD be designed such that all 892 Flow Keys are among the first 64 Information Elements, because 893 the flowKeyIndicator only contains 64 bits. If the Data Record 894 contains less than 64 Information Elements, then the bits in 895 the flowKeyIndicator for which no corresponding Information 896 Element exists MUST have the value 0.",,,,[RFC5102][RFC Errata 4984],1,2017-08-01 897 174,postMCastPacketTotalCount,unsigned64,totalCounter,current,"The total number of outgoing multicast packets sent for 898 packets of this Flow by a multicast daemon within the 899 Observation Domain since the Metering Process 900 (re-)initialization. This property cannot necessarily 901 be observed at the Observation Point, but may be retrieved 902 by other means.",packets,,,[RFC5102],0,2013-02-18 903 175,postMCastOctetTotalCount,unsigned64,totalCounter,current,"The total number of octets in outgoing multicast packets 904 sent for packets of this Flow by a multicast daemon in the 905 Observation Domain since the Metering Process 906 (re-)initialization. This property cannot necessarily be 907 observed at the Observation Point, but may be retrieved by 908 other means. 909 The number of octets includes IP header(s) and IP payload.",octets,,,[RFC5102],0,2013-02-18 910 176,icmpTypeIPv4,unsigned8,identifier,current,Type of the IPv4 ICMP message.,,,"See [RFC792] for the definition of the IPv4 911 ICMP type field.",[RFC5102],0,2013-02-18 912 177,icmpCodeIPv4,unsigned8,identifier,current,Code of the IPv4 ICMP message.,,,"See [RFC792] for the definition of the IPv4 913 ICMP code field.",[RFC5102],0,2013-02-18 914 178,icmpTypeIPv6,unsigned8,identifier,current,Type of the IPv6 ICMP message.,,,"See [RFC4443] for the definition of the IPv6 915 ICMP type field.",[RFC5102],0,2013-02-18 916 179,icmpCodeIPv6,unsigned8,identifier,current,Code of the IPv6 ICMP message.,,,"See [RFC4443] for the definition of the IPv6 917 ICMP code field.",[RFC5102],0,2013-02-18 918 180,udpSourcePort,unsigned16,identifier,current,The source port identifier in the UDP header.,,,"See [RFC768] for the definition of the UDP 919 source port field. 920 Additional information on defined UDP port numbers can be found at 921 [IANA registry service-names-port-numbers].",[RFC5102],0,2013-02-18 922 181,udpDestinationPort,unsigned16,identifier,current,The destination port identifier in the UDP header.,,,"See [RFC768] for the definition of the UDP 923 destination port field. 924 Additional information on defined UDP port numbers can be found at 925 [IANA registry service-names-port-numbers].",[RFC5102],0,2013-02-18 926 182,tcpSourcePort,unsigned16,identifier,current,The source port identifier in the TCP header.,,,"See [RFC793] for the definition of the TCP 927 source port field. 928 Additional information on defined TCP port numbers can be found at 929 [IANA registry service-names-port-numbers].",[RFC5102],0,2013-02-18 930 183,tcpDestinationPort,unsigned16,identifier,current,The destination port identifier in the TCP header.,,,"See [RFC793] for the definition of the TCP 931 destination port field. 932 Additional information on defined TCP port numbers can be found at 933 [IANA registry service-names-port-numbers].",[RFC5102],0,2013-02-18 934 184,tcpSequenceNumber,unsigned32,,current,The sequence number in the TCP header.,,,"See [RFC793] for the definition of the TCP 935 sequence number.",[RFC5102],0,2013-02-18 936 185,tcpAcknowledgementNumber,unsigned32,,current,The acknowledgement number in the TCP header.,,,"See [RFC793] for the definition of the TCP 937 acknowledgement number.",[RFC5102],0,2013-02-18 938 186,tcpWindowSize,unsigned16,,current,"The window field in the TCP header. 939 If the TCP window scale is supported, 940 then TCP window scale must be known 941 to fully interpret the value of this information.",,,"See [RFC793] for the definition of the TCP 942 window field. 943 See [RFC1323] for the definition of the TCP 944 window scale.",[RFC5102],0,2013-02-18 945 187,tcpUrgentPointer,unsigned16,,current,The urgent pointer in the TCP header.,,,"See [RFC793] for the definition of the TCP 946 urgent pointer.",[RFC5102],0,2013-02-18 947 188,tcpHeaderLength,unsigned8,,current,"The length of the TCP header. Note that the value of this 948 Information Element is different from the value of the Data 949 Offset field in the TCP header. The Data Offset field 950 indicates the length of the TCP header in units of 4 octets. 951 This Information Elements specifies the length of the TCP 952 header in units of octets.",octets,,"See [RFC793] for the definition of the TCP 953 header.",[RFC5102],0,2013-02-18 954 189,ipHeaderLength,unsigned8,,current,"The length of the IP header. For IPv6, the value of this 955 Information Element is 40.",octets,,"See [RFC791] for the definition of the IPv4 956 header. 957 See [RFC8200] for the definition of the IPv6 958 header.",[RFC5102],0,2013-02-18 959 190,totalLengthIPv4,unsigned16,,current,The total length of the IPv4 packet.,octets,,"See [RFC791] for the specification of the IPv4 960 total length.",[RFC5102],0,2013-02-18 961 191,payloadLengthIPv6,unsigned16,,current,"This Information Element reports the value of the Payload 962 Length field in the IPv6 header. Note that IPv6 extension 963 headers belong to the payload. Also note that in case of a 964 jumbo payload option the value of the Payload Length field in 965 the IPv6 header is zero and so will be the value reported 966 by this Information Element.",octets,,"See [RFC8200] for the specification of the IPv6 967 payload length. 968 See [RFC2675] for the specification of the IPv6 969 jumbo payload option.",[RFC5102],0,2013-02-18 970 192,ipTTL,unsigned8,,current,"For IPv4, the value of the Information Element matches 971 the value of the Time to Live (TTL) field in the IPv4 packet 972 header. For IPv6, the value of the Information Element 973 matches the value of the Hop Limit field in the IPv6 974 packet header.",hops,,"See [RFC791] for the definition of the IPv4 975 Time to Live field. 976 See [RFC2675] for the definition of the IPv6 977 Hop Limit field.",[RFC5102],0,2013-02-18 978 193,nextHeaderIPv6,unsigned8,,current,"The value of the Next Header field of the IPv6 header. 979 The value identifies the type of the following IPv6 980 extension header or of the following IP payload. 981 Valid values are defined in the IANA 982 Protocol Numbers registry.",,,"See [RFC8200] for the definition of the IPv6 983 Next Header field. 984 See the list of protocol numbers assigned by IANA at [IANA registry protocol-numbers].",[RFC5102],0,2013-02-18 985 194,mplsPayloadLength,unsigned32,,current,The size of the MPLS packet without the label stack.,octets,,"See [RFC3031] for the specification of MPLS 986 packets. 987 See [RFC3032] for the specification of the 988 MPLS label stack.",[RFC5102],0,2013-02-18 989 195,ipDiffServCodePoint,unsigned8,identifier,current,"The value of a Differentiated Services Code Point (DSCP) 990 encoded in the Differentiated Services field. The 991 Differentiated Services field spans the most significant 992 6 bits of the IPv4 TOS field or the IPv6 Traffic Class 993 field, respectively. 994 995 996 997 998 This Information Element encodes only the 6 bits of the 999 Differentiated Services field. Therefore, its value may 1000 range from 0 to 63.",,0-63,"See [RFC3260] for the definition of the 1001 Differentiated Services field. 1002 See [RFC1812] (Section 5.3.2) and [RFC791] for the definition of the IPv4 TOS field. 1003 See [RFC8200] for the definition of the IPv6 1004 Traffic Class field.",[RFC5102],0,2013-02-18 1005 196,ipPrecedence,unsigned8,identifier,current,"The value of the IP Precedence. The IP Precedence value 1006 is encoded in the first 3 bits of the IPv4 TOS field 1007 or the IPv6 Traffic Class field, respectively. 1008 1009 1010 1011 1012 This Information Element encodes only these 3 bits. 1013 Therefore, its value may range from 0 to 7.",,0-7,"See [RFC1812] (Section 5.3.3) and [RFC791] for the definition of the IP Precedence. 1014 See [RFC1812] (Section 5.3.2) and [RFC791] for the definition of the IPv4 TOS field. 1015 See [RFC8200] for the definition of the IPv6 1016 Traffic Class field.",[RFC5102],0,2013-02-18 1017 197,fragmentFlags,unsigned8,flags,current,"Fragmentation properties indicated by flags in the IPv4 1018 packet header or the IPv6 Fragment header, respectively. 1019 1020 1021 1022 1023 Bit 0: (RS) Reserved. 1024 The value of this bit MUST be 0 until specified 1025 otherwise. 1026 1027 Bit 1: (DF) 0 = May Fragment, 1 = Don't Fragment. 1028 Corresponds to the value of the DF flag in the 1029 IPv4 header. Will always be 0 for IPv6 unless 1030 a ""don't fragment"" feature is introduced to IPv6. 1031 1032 Bit 2: (MF) 0 = Last Fragment, 1 = More Fragments. 1033 Corresponds to the MF flag in the IPv4 header 1034 or to the M flag in the IPv6 Fragment header, 1035 respectively. The value is 0 for IPv6 if there 1036 is no fragment header. 1037 1038 Bits 3-7: (DC) Don't Care. 1039 The values of these bits are irrelevant. 1040 1041 0 1 2 3 4 5 6 7 1042 +---+---+---+---+---+---+---+---+ 1043 | R | D | M | D | D | D | D | D | 1044 | S | F | F | C | C | C | C | C | 1045 +---+---+---+---+---+---+---+---+",,,"See [RFC791] for the specification of the IPv4 1046 fragment flags. 1047 See [RFC8200] for the specification of the 1048 IPv6 Fragment header.",[RFC5102],0,2013-02-18 1049 198,octetDeltaSumOfSquares,unsigned64,,current,"The sum of the squared numbers of octets per incoming 1050 packet since the previous report (if any) for this 1051 Flow at the Observation Point. 1052 The number of octets includes IP header(s) and IP payload.",,,,[RFC5102],0,2013-02-18 1053 199,octetTotalSumOfSquares,unsigned64,,current,"The total sum of the squared numbers of octets in incoming 1054 packets for this Flow at the Observation Point since the 1055 Metering Process (re-)initialization for this Observation 1056 Point. The number of octets includes IP header(s) and IP 1057 payload.",octets,,,[RFC5102],0,2013-02-18 1058 200,mplsTopLabelTTL,unsigned8,,current,"The TTL field from the top MPLS label stack entry, 1059 i.e., the last label that was pushed.",hops,,"See [RFC3032] for the specification of the TTL 1060 field.",[RFC5102],0,2013-02-18 1061 201,mplsLabelStackLength,unsigned32,,current,The length of the MPLS label stack in units of octets.,octets,,"See [RFC3032] for the specification of the 1062 MPLS label stack.",[RFC5102],0,2013-02-18 1063 202,mplsLabelStackDepth,unsigned32,,current,The number of labels in the MPLS label stack.,entries,,"See [RFC3032] for the specification of the 1064 MPLS label stack.",[RFC5102],0,2013-02-18 1065 203,mplsTopLabelExp,unsigned8,flags,current,"The Exp field from the top MPLS label stack entry, 1066 i.e., the last label that was pushed. 1067 1068 1069 1070 Bits 0-4: Don't Care, value is irrelevant. 1071 Bits 5-7: MPLS Exp field. 1072 1073 0 1 2 3 4 5 6 7 1074 +---+---+---+---+---+---+---+---+ 1075 | don't care | Exp | 1076 +---+---+---+---+---+---+---+---+",,,"See [RFC3032] for the specification of the 1077 Exp field. 1078 See [RFC3270] for usage of the Exp field.",[RFC5102],0,2013-02-18 1079 204,ipPayloadLength,unsigned32,,current,"The effective length of the IP payload. 1080 1081 1082 1083 1084 For IPv4 packets, the value of this Information Element is 1085 the difference between the total length of the IPv4 packet 1086 (as reported by Information Element totalLengthIPv4) and the 1087 length of the IPv4 header (as reported by Information Element 1088 headerLengthIPv4). 1089 1090 1091 1092 1093 For IPv6, the value of the Payload Length field 1094 in the IPv6 header is reported except in the case that 1095 the value of this field is zero and that there is a valid 1096 jumbo payload option. In this case, the value of the 1097 Jumbo Payload Length field in the jumbo payload option 1098 is reported.",octets,,"See [RFC791] for the specification of IPv4 1099 packets. 1100 See [RFC8200] for the specification of the 1101 IPv6 payload length. 1102 See [RFC2675] for the specification of the 1103 IPv6 jumbo payload length.",[RFC5102],0,2013-02-18 1104 205,udpMessageLength,unsigned16,,current,The value of the Length field in the UDP header.,octets,,"See [RFC768] for the specification of the UDP 1105 header.",[RFC5102],0,2013-02-18 1106 206,isMulticast,unsigned8,flags,current,"If the IP destination address is not a reserved multicast 1107 address, then the value of all bits of the octet (including 1108 the reserved ones) is zero. 1109 1110 1111 1112 1113 The first bit of this octet is set to 1 if the Version 1114 field of the IP header has the value 4 and if the 1115 Destination Address field contains a reserved multicast 1116 address in the range from 224.0.0.0 to 239.255.255.255. 1117 Otherwise, this bit is set to 0. 1118 1119 1120 1121 1122 The second and third bits of this octet are reserved for 1123 future use. 1124 1125 1126 1127 1128 The remaining bits of the octet are only set to values 1129 other than zero if the IP Destination Address is a 1130 reserved IPv6 multicast address. Then the fourth bit 1131 of the octet is set to the value of the T flag in the 1132 IPv6 multicast address and the remaining four bits are 1133 set to the value of the scope field in the IPv6 1134 multicast address. 1135 1136 1137 1138 0 1 2 3 4 5 6 7 1139 +------+------+------+------+------+------+------+------+ 1140 | IPv6 multicast scope | T | RES. | RES. | MCv4 | 1141 +------+------+------+------+------+------+------+------+ 1142 1143 Bits 0-3: set to value of multicast scope if IPv6 multicast 1144 Bit 4: set to value of T flag, if IPv6 multicast 1145 Bits 5-6: reserved for future use 1146 Bit 7: set to 1 if IPv4 multicast",,,"See [RFC1112] for the specification of 1147 reserved IPv4 multicast addresses. 1148 See [RFC4291] for the specification of 1149 reserved IPv6 multicast addresses and the definition of the T flag and 1150 the IPv6 multicast scope. 1151 The diagram provided in [RFC5102] is incorrect. 1152 The diagram in this registry is taken from Errata 1736. See [RFC Errata 1736]",[RFC5102],0,2013-02-18 1153 207,ipv4IHL,unsigned8,,current,"The value of the Internet Header Length (IHL) field in 1154 the IPv4 header. It specifies the length of the header 1155 in units of 4 octets. Please note that its unit is 1156 different from most of the other Information Elements 1157 reporting length values.",4-octet words,,"See [RFC791] for the specification of the IPv4 1158 header.",[RFC5102],0,2013-02-18 1159 208,ipv4Options,unsigned32,flags,current,"IPv4 options in packets of this Flow. 1160 The information is encoded in a set of bit fields. For 1161 each valid IPv4 option type, there is a bit in this set. 1162 The bit is set to 1 if any observed packet of this Flow 1163 contains the corresponding IPv4 option type. Otherwise, 1164 if no observed packet of this Flow contained the 1165 respective IPv4 option type, the value of the 1166 corresponding bit is 0. 1167 1168 1169 1170 1171 The list of valid IPv4 options is maintained by IANA. 1172 Note that for identifying an option not just the 5-bit 1173 Option Number, but all 8 bits of the Option Type need to 1174 match one of the IPv4 options specified at 1175 http://www.iana.org/assignments/ip-parameters. 1176 1177 1178 1179 1180 Options are mapped to bits according to their option numbers. 1181 Option number X is mapped to bit X. 1182 The mapping is illustrated by the figure below. 1183 1184 1185 1186 0 1 2 3 4 5 6 7 1187 +------+------+------+------+------+------+------+------+ 1188 ... | RR |CIPSO |E-SEC | TS | LSR | SEC | NOP | EOOL | 1189 +------+------+------+------+------+------+------+------+ 1190 1191 8 9 10 11 12 13 14 15 1192 +------+------+------+------+------+------+------+------+ 1193 ... |ENCODE| VISA | FINN | MTUR | MTUP | ZSU | SSR | SID | ... 1194 +------+------+------+------+------+------+------+------+ 1195 1196 16 17 18 19 20 21 22 23 1197 +------+------+------+------+------+------+------+------+ 1198 ... | DPS |NSAPA | SDB |RTRALT|ADDEXT| TR | EIP |IMITD | ... 1199 +------+------+------+------+------+------+------+------+ 1200 1201 24 25 26 27 28 29 30 31 1202 +------+------+------+------+------+------+------+------+ 1203 ... | | EXP | to be assigned by IANA | QS | UMP | 1204 +------+------+------+------+------+------+------+------+ 1205 1206 Type Option 1207 Bit Value Name Reference 1208 ---+-----+-------+------------------------------------ 1209 0 7 RR Record Route, RFC 791 1210 1 134 CIPSO Commercial Security 1211 2 133 E-SEC Extended Security, RFC 1108 1212 3 68 TS Time Stamp, RFC 791 1213 4 131 LSR Loose Source Route, RFC791 1214 5 130 SEC Security, RFC 1108 1215 6 1 NOP No Operation, RFC 791 1216 7 0 EOOL End of Options List, RFC 791 1217 8 15 ENCODE 1218 9 142 VISA Experimental Access Control 1219 10 205 FINN Experimental Flow Control 1220 11 12 MTUR (obsoleted) MTU Reply, RFC 1191 1221 12 11 MTUP (obsoleted) MTU Probe, RFC 1191 1222 13 10 ZSU Experimental Measurement 1223 14 137 SSR Strict Source Route, RFC 791 1224 15 136 SID Stream ID, RFC 791 1225 16 151 DPS Dynamic Packet State 1226 17 150 NSAPA NSAP Address 1227 18 149 SDB Selective Directed Broadcast 1228 19 147 ADDEXT Address Extension 1229 20 148 RTRALT Router Alert, RFC 2113 1230 21 82 TR Traceroute, RFC 3193 1231 22 145 EIP Extended Internet Protocol, RFC 1385 1232 23 144 IMITD IMI Traffic Descriptor 1233 25 30 EXP RFC3692-style Experiment 1234 25 94 EXP RFC3692-style Experiment 1235 25 158 EXP RFC3692-style Experiment 1236 25 222 EXP RFC3692-style Experiment 1237 30 25 QS Quick-Start 1238 31 152 UMP Upstream Multicast Pkt. 1239 ... ... ... Further options numbers 1240 may be assigned by IANA",,,"See [RFC791] for the definition of IPv4 1241 options. 1242 See the list of IPv4 option numbers assigned by IANA at [IANA registry ip-parameters]. 1243 The diagram provided in [RFC5102] is incorrect. 1244 The diagram in this registry is taken from Errata 1737. See [RFC Errata 1737]",[RFC5102],0,2013-02-18 1245 209,tcpOptions,unsigned64,flags,current,"TCP options in packets of this Flow. 1246 The information is encoded in a set of bit fields. For 1247 each TCP option, there is a bit in this set. 1248 The bit is set to 1 if any observed packet of this Flow 1249 contains the corresponding TCP option. 1250 Otherwise, if no observed packet of this Flow contained 1251 the respective TCP option, the value of the 1252 corresponding bit is 0. 1253 1254 1255 1256 1257 Options are mapped to bits according to their option 1258 numbers. Option number X is mapped to bit X. 1259 TCP option numbers are maintained by IANA. 1260 1261 1262 1263 0 1 2 3 4 5 6 7 1264 +-----+-----+-----+-----+-----+-----+-----+-----+ 1265 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 | ... 1266 +-----+-----+-----+-----+-----+-----+-----+-----+ 1267 1268 8 9 10 11 12 13 14 15 1269 +-----+-----+-----+-----+-----+-----+-----+-----+ 1270 ... | 15 | 14 | 13 | 12 | 11 | 10 | 9 | 8 |... 1271 +-----+-----+-----+-----+-----+-----+-----+-----+ 1272 1273 16 17 18 19 20 21 22 23 1274 +-----+-----+-----+-----+-----+-----+-----+-----+ 1275 ... | 23 | 22 | 21 | 20 | 19 | 18 | 17 | 16 |... 1276 +-----+-----+-----+-----+-----+-----+-----+-----+ 1277 1278 . . . 1279 1280 56 57 58 59 60 61 62 63 1281 +-----+-----+-----+-----+-----+-----+-----+-----+ 1282 ... | 63 | 62 | 61 | 60 | 59 | 58 | 57 | 56 | 1283 +-----+-----+-----+-----+-----+-----+-----+-----+",,,"See [RFC793] for the definition of TCP 1284 options. 1285 See the list of TCP option numbers assigned by IANA at [IANA registry tcp-parameters]. 1286 The diagram provided in [RFC5102] is incorrect. 1287 The diagram in this registry is taken from Errata 1739. See [RFC Errata 1739]",[RFC5102],0,2013-02-18 1288 210,paddingOctets,octetArray,default,current,"The value of this Information Element is always a sequence of 1289 0x00 values.",,,,[RFC5102],0,2013-02-18 1290 211,collectorIPv4Address,ipv4Address,default,current,"An IPv4 address to which the Exporting Process sends Flow 1291 information.",,,,[RFC5102],1,2014-02-03 1292 212,collectorIPv6Address,ipv6Address,default,current,"An IPv6 address to which the Exporting Process sends Flow 1293 information.",,,,[RFC5102],1,2014-02-03 1294 213,exportInterface,unsigned32,identifier,current,"The index of the interface from which IPFIX Messages sent 1295 by the Exporting Process to a Collector leave the IPFIX 1296 Device. The value matches the value of 1297 managed object 'ifIndex' as defined in [RFC2863]. 1298 Note that ifIndex values are not assigned statically to an 1299 interface and that the interfaces may be renumbered every 1300 time the device's management system is re-initialized, as 1301 specified in [RFC2863].",,,"See [RFC2863] for the definition of the 1302 ifIndex object.",[RFC5102],0,2013-02-18 1303 214,exportProtocolVersion,unsigned8,identifier,current,"The protocol version used by the Exporting Process for 1304 sending Flow information. The protocol version is given 1305 by the value of the Version Number field in the Message 1306 Header. 1307 1308 1309 1310 1311 The protocol version is 10 for IPFIX and 9 for NetFlow 1312 version 9. 1313 A value of 0 indicates that no export protocol is in use.",,,"See the [IPFIX protocol 1314 specification] for the definition of the IPFIX Message Header. 1315 See [RFC3954] for the definition of the 1316 NetFlow version 9 message header.",[RFC5102],0,2013-02-18 1317 215,exportTransportProtocol,unsigned8,identifier,current,"The value of the protocol number used by the Exporting Process 1318 for sending Flow information. 1319 The protocol number identifies the IP packet payload type. 1320 Protocol numbers are defined in the IANA Protocol Numbers 1321 registry. 1322 1323 1324 1325 1326 In Internet Protocol version 4 (IPv4), this is carried in the 1327 Protocol field. In Internet Protocol version 6 (IPv6), this 1328 is carried in the Next Header field in the last extension 1329 header of the packet.",,,"See [RFC791] for the specification of the IPv4 1330 protocol field. 1331 See [RFC8200] for the specification of the 1332 IPv6 protocol field. 1333 See the list of protocol numbers assigned by IANA at [IANA registry protocol-numbers].",[RFC5102],0,2013-02-18 1334 216,collectorTransportPort,unsigned16,identifier,current,"The destination port identifier to which the Exporting 1335 Process sends Flow information. For the transport protocols 1336 UDP, TCP, and SCTP, this is the destination port number. 1337 This field MAY also be used for future transport protocols 1338 that have 16-bit source port identifiers.",,,"See [RFC768] for the definition of the UDP 1339 destination port field. 1340 See [RFC793] for the definition of the TCP 1341 destination port field. 1342 See [RFC4960] for the definition of SCTP. 1343 1344 1345 1346 1347 Additional information on defined UDP and TCP port numbers can be 1348 found at [IANA registry service-names-port-numbers].",[RFC5102],0,2013-02-18 1349 217,exporterTransportPort,unsigned16,identifier,current,"The source port identifier from which the Exporting 1350 Process sends Flow information. For the transport protocols 1351 UDP, TCP, and SCTP, this is the source port number. 1352 This field MAY also be used for future transport protocols 1353 that have 16-bit source port identifiers. This field may 1354 be useful for distinguishing multiple Exporting Processes 1355 that use the same IP address.",,,"See [RFC768] for the definition of the UDP 1356 source port field. 1357 See [RFC793] for the definition of the TCP 1358 source port field. 1359 See [RFC4960] for the definition of SCTP. 1360 1361 1362 1363 1364 Additional information on defined UDP and TCP port numbers can be 1365 found at [IANA registry service-names-port-numbers].",[RFC5102],0,2013-02-18 1366 218,tcpSynTotalCount,unsigned64,totalCounter,current,"The total number of packets of this Flow with 1367 TCP ""Synchronize sequence numbers"" (SYN) flag set.",packets,,"See [RFC793] for the definition of the TCP SYN 1368 flag.",[RFC5102],0,2013-02-18 1369 219,tcpFinTotalCount,unsigned64,totalCounter,current,"The total number of packets of this Flow with 1370 TCP ""No more data from sender"" (FIN) flag set.",packets,,"See [RFC793] for the definition of the TCP FIN 1371 flag.",[RFC5102],0,2013-02-18 1372 220,tcpRstTotalCount,unsigned64,totalCounter,current,"The total number of packets of this Flow with 1373 TCP ""Reset the connection"" (RST) flag set.",packets,,"See [RFC793] for the definition of the TCP RST 1374 flag.",[RFC5102],0,2013-02-18 1375 221,tcpPshTotalCount,unsigned64,totalCounter,current,"The total number of packets of this Flow with 1376 TCP ""Push Function"" (PSH) flag set.",packets,,"See [RFC793] for the definition of the TCP PSH 1377 flag.",[RFC5102],0,2013-02-18 1378 222,tcpAckTotalCount,unsigned64,totalCounter,current,"The total number of packets of this Flow with 1379 TCP ""Acknowledgment field significant"" (ACK) flag set.",packets,,"See [RFC793] for the definition of the TCP ACK 1380 flag.",[RFC5102],0,2013-02-18 1381 223,tcpUrgTotalCount,unsigned64,totalCounter,current,"The total number of packets of this Flow with 1382 TCP ""Urgent Pointer field significant"" (URG) flag set.",packets,,"See [RFC793] for the definition of the TCP URG 1383 flag.",[RFC5102],0,2013-02-18 1384 224,ipTotalLength,unsigned64,,current,The total length of the IP packet.,octets,,"See [RFC791] for the specification of the IPv4 1385 total length. 1386 See [RFC8200] for the specification of the 1387 IPv6 payload length. 1388 See [RFC2675] for the specification of the 1389 IPv6 jumbo payload length.",[RFC5102],0,2013-02-18 1390 225,postNATSourceIPv4Address,ipv4Address,default,current,"The definition of this Information Element is identical to the 1391 definition of Information Element 'sourceIPv4Address', except 1392 that it reports a modified value caused by a NAT middlebox 1393 function after the packet passed the Observation Point.",,,"See [RFC791] for the definition of the IPv4 source 1394 address field. See [RFC3022] for the definition of 1395 NAT. See [RFC3234] for the definition of middleboxes.",[ipfix-iana_at_cisco.com],1,2014-02-03 1396 226,postNATDestinationIPv4Address,ipv4Address,default,current,"The definition of this Information Element is identical to the 1397 definition of Information Element 'destinationIPv4Address', 1398 except that it reports a modified value caused by a NAT 1399 middlebox function after the packet passed the Observation 1400 Point.",,,"See [RFC791] for the definition of the IPv4 destination 1401 address field. See [RFC3022] for the definition of 1402 NAT. See [RFC3234] for the definition of middleboxes.",[ipfix-iana_at_cisco.com],1,2014-02-03 1403 227,postNAPTSourceTransportPort,unsigned16,identifier,current,"The definition of this Information Element is identical to the 1404 definition of Information Element 'sourceTransportPort', except 1405 that it reports a modified value caused by a Network Address 1406 Port Translation (NAPT) middlebox function after the packet 1407 passed the Observation Point.",,,"See [RFC768] for the definition of the UDP source port 1408 field. See [RFC793] for the definition of the TCP 1409 source port field. See [RFC4960] for the definition of 1410 SCTP. 1411 See [RFC3022] for the definition of NAPT. See [RFC3234] for the definition of middleboxes. 1412 Additional information on defined UDP and TCP port numbers can 1413 be found at http://www.iana.org/assignments/port-numbers.",[ipfix-iana_at_cisco.com],0,2013-02-18 1414 228,postNAPTDestinationTransportPort,unsigned16,identifier,current,"The definition of this Information Element is identical to the 1415 definition of Information Element 'destinationTransportPort', 1416 except that it reports a modified value caused by a Network 1417 Address Port Translation (NAPT) middlebox function after the 1418 packet passed the Observation Point.",,,"See [RFC768] for the definition of the UDP source port 1419 field. See [RFC793] for the definition of the TCP 1420 source port field. See [RFC4960] for the definition of 1421 SCTP. 1422 See [RFC3022] for the definition of NAPT. See [RFC3234] for the definition of middleboxes. 1423 Additional information on defined UDP and TCP port numbers can 1424 be found at [IANA registry service-names-port-numbers].",[ipfix-iana_at_cisco.com],0,2013-02-18 1425 229,natOriginatingAddressRealm,unsigned8,identifier,current,"Indicates whether the session was created because traffic 1426 originated in the private or public address realm. 1427 postNATSourceIPv4Address, postNATDestinationIPv4Address, 1428 postNAPTSourceTransportPort, and 1429 postNAPTDestinationTransportPort are qualified with the address 1430 realm in perspective. 1431 1432 1433 1434 1435 The allowed values are: 1436 1437 1438 1439 1440 Private: 1 1441 1442 1443 1444 1445 Public: 2",,1-2,See [RFC3022] for the definition of NAT.,[ipfix-iana_at_cisco.com],1,2014-08-13 1446 230,natEvent,unsigned8,identifier,current,"This Information Element identifies a NAT event. This IE identifies 1447 the type of a NAT event. Examples of NAT events include, but are not 1448 limited to, NAT translation create, NAT translation delete, Threshold 1449 Reached, or Threshold Exceeded, etc. Values for this Information 1450 Element are listed in the ""NAT Event Type"" registry, see 1451 [http://www.iana.org/assignments/ipfix/ipfix.xml#ipfix-nat-event-type]. 1452 New assignments of values will be administered by IANA and are 1453 subject to Expert Review [RFC8126]. Experts 1454 need to check definitions of new values for completeness, accuracy, 1455 and redundancy.",,,"See [RFC3022] for the definition of NAT. See 1456 [RFC3234] for the definition of middleboxes. 1457 See [RFC8158] 1458 for the definitions of values 4-16.",[RFC8158],2,2017-03-15 1459 231,initiatorOctets,unsigned64,deltaCounter,current,"The total number of layer 4 payload bytes in a flow from the 1460 initiator since the previous report. The initiator is the device 1461 which triggered the session creation, and remains the same for 1462 the life of the session.",octets,,"See #298, initiatorPackets.",[ipfix-iana_at_cisco.com],1,2014-08-13 1463 232,responderOctets,unsigned64,deltaCounter,current,"The total number of layer 4 payload bytes in a flow from the 1464 responder since the previous report. The responder is the device 1465 which replies to the initiator, and remains the same for the life 1466 of the session.",octets,,"See #299, responderPackets.",[ipfix-iana_at_cisco.com],1,2014-08-13 1467 233,firewallEvent,unsigned8,,current,"Indicates a firewall event. The allowed values are: 1468 1469 1470 1471 1472 0 - Ignore (invalid) 1473 1474 1475 1476 1477 1 - Flow Created 1478 1479 1480 1481 1482 2 - Flow Deleted 1483 1484 1485 1486 1487 3 - Flow Denied 1488 1489 1490 1491 1492 4 - Flow Alert 1493 1494 1495 1496 1497 5 - Flow Update",,,,[ipfix-iana_at_cisco.com],0,2013-02-18 1498 234,ingressVRFID,unsigned32,,current,"An unique identifier of the VRFname where the packets of this 1499 flow are being received. This identifier is unique per Metering 1500 Process",,,,[ipfix-iana_at_cisco.com],0,2013-02-18 1501 235,egressVRFID,unsigned32,,current,"An unique identifier of the VRFname where the packets of this 1502 flow are being sent. This identifier is unique per Metering 1503 Process",,,,[ipfix-iana_at_cisco.com],0,2013-02-18 1504 236,VRFname,string,default,current,The name of a VPN Routing and Forwarding table (VRF).,,,See [RFC4364] for the definition of VRF.,[ipfix-iana_at_cisco.com],0,2013-02-18 1505 237,postMplsTopLabelExp,unsigned8,flags,current,"The definition of this Information Element is identical to the 1506 definition of Information Element 'mplsTopLabelExp', except 1507 that it reports a potentially modified value caused by a 1508 middlebox function after the packet passed the Observation 1509 Point.",,,"See [RFC3032] for the specification of the Exp 1510 field. 1511 See [RFC3270] for usage of the Exp field.",[RFC5102],0,2013-02-18 1512 238,tcpWindowScale,unsigned16,,current,The scale of the window field in the TCP header.,,,"See [RFC1323] for the definition of the TCP 1513 window scale.",[RFC5102],0,2013-02-18 1514 239,biflowDirection,unsigned8,identifier,current,"A description of the direction assignment method used to 1515 assign the Biflow Source and Destination. This Information Element 1516 MAY be present in a Flow Data Record, or applied to all flows exported 1517 from an Exporting Process or Observation Domain using IPFIX Options. 1518 If this Information Element is not present in a Flow Record or 1519 associated with a Biflow via scope, it is assumed that the 1520 configuration of the direction assignment method is done out-of-band. 1521 Note that when using IPFIX Options to apply this Information Element 1522 to all flows within an Observation Domain or from an Exporting 1523 Process, the Option SHOULD be sent reliably. If reliable transport is 1524 not available (i.e., when using UDP), this Information Element SHOULD 1525 appear in each Flow Record. This field may take the following 1526 values: 1527 1528 1529 +-------+------------------+----------------------------------------+ 1530 | Value | Name | Description | 1531 +-------+------------------+----------------------------------------+ 1532 | 0x00 | arbitrary | Direction was assigned arbitrarily. | 1533 | 0x01 | initiator | The Biflow Source is the flow | 1534 | | | initiator, as determined by the | 1535 | | | Metering Process' best effort to | 1536 | | | detect the initiator. | 1537 | 0x02 | reverseInitiator | The Biflow Destination is the flow | 1538 | | | initiator, as determined by the | 1539 | | | Metering Process' best effort to | 1540 | | | detect the initiator. This value is | 1541 | | | provided for the convenience of | 1542 | | | Exporting Processes to revise an | 1543 | | | initiator estimate without re-encoding | 1544 | | | the Biflow Record. | 1545 | 0x03 | perimeter | The Biflow Source is the endpoint | 1546 | | | outside of a defined perimeter. The | 1547 | | | perimeter's definition is implicit in | 1548 | | | the set of Biflow Source and Biflow | 1549 | | | Destination addresses exported in the | 1550 | | | Biflow Records. | 1551 +-------+------------------+----------------------------------------+",,,,[RFC5103],0,2013-02-18 1552 240,ethernetHeaderLength,unsigned8,quantity,current,"The difference between the length of an Ethernet frame (minus the 1553 FCS) and the length of its MAC Client Data section (including any 1554 padding) as defined in section 3.1 of [IEEE.802-3.2005]. It does 1555 not include the Preamble, SFD and Extension field lengths.",octets,,[IEEE.802-3.2005],[ipfix-iana_at_cisco.com],1,2014-08-13 1556 241,ethernetPayloadLength,unsigned16,quantity,current,"The length of the MAC Client Data section (including any padding) 1557 of a frame as defined in section 3.1 of [IEEE.802-3.2005].",octets,,[IEEE.802-3.2005],[ipfix-iana_at_cisco.com],1,2014-08-13 1558 242,ethernetTotalLength,unsigned16,quantity,current,"The total length of the Ethernet frame (excluding the Preamble, 1559 SFD, Extension and FCS fields) as described in section 3.1 of 1560 [IEEE.802-3.2005].",octets,,[IEEE.802-3.2005],[ipfix-iana_at_cisco.com],1,2014-08-13 1561 243,dot1qVlanId,unsigned16,identifier,current,"The value of the 12-bit VLAN Identifier portion of the Tag Control 1562 Information field of an Ethernet frame. The structure and 1563 semantics within the Tag Control Information field are defined in 1564 [IEEE802.1Q]. In Provider Bridged Networks, it represents the 1565 Service VLAN identifier in the Service VLAN Tag (S-TAG) Tag 1566 Control Information (TCI) field or the Customer VLAN identifier in 1567 the Customer VLAN Tag (C-TAG) Tag Control Information (TCI) field 1568 as described in [IEEE802.1Q]. In Provider Backbone Bridged 1569 Networks, it represents the Backbone VLAN identifier in the 1570 Backbone VLAN Tag (B-TAG) Tag Control Information (TCI) field as 1571 described in [IEEE802.1Q]. In a virtual link between a host 1572 system and EVB bridge, it represents the Service VLAN identifier 1573 indicating S-channel as described in [IEEE802.1Qbg]. 1574 1575 1576 1577 1578 In the case of a multi-tagged frame, it represents the outer tag's 1579 VLAN identifier, except for I-TAG.",,,[IEEE802.1Q][IEEE802.1Qbg],[ipfix-iana_at_cisco.com][RFC7133],2,2014-01-11 1580 244,dot1qPriority,unsigned8,identifier,current,"The value of the 3-bit User Priority portion of the Tag Control 1581 Information field of an Ethernet frame. The structure and 1582 semantics within the Tag Control Information field are defined in 1583 [IEEE802.1Q]. In the case of multi-tagged frame, it represents 1584 the 3-bit Priority Code Point (PCP) portion of the outer tag's Tag 1585 Control Information (TCI) field as described in [IEEE802.1Q], 1586 except for I-TAG.",,,[IEEE802.1Q],[ipfix-iana_at_cisco.com][RFC7133],1,2014-01-11 1587 245,dot1qCustomerVlanId,unsigned16,identifier,current,"The value represents the Customer VLAN identifier in the Customer 1588 VLAN Tag (C-TAG) Tag Control Information (TCI) field as described 1589 in [IEEE802.1Q].",,,[IEEE802.1Q],[ipfix-iana_at_cisco.com][RFC7133],1,2014-01-11 1590 246,dot1qCustomerPriority,unsigned8,identifier,current,"The value represents the 3-bit Priority Code Point (PCP) portion 1591 of the Customer VLAN Tag (C-TAG) Tag Control Information (TCI) 1592 field as described in [IEEE802.1Q].",,,[IEEE802.1Q],[ipfix-iana_at_cisco.com][RFC7133],1,2014-01-11 1593 247,metroEvcId,string,default,current,"The EVC Service Attribute which uniquely identifies the Ethernet 1594 Virtual Connection (EVC) within a Metro Ethernet Network, as 1595 defined in section 6.2 of MEF 10.1. The MetroEVCID is encoded in 1596 a string of up to 100 characters.",,,"MEF 10.1 (Ethernet Services Attributes Phase 2) 1597 MEF16 (Ethernet Local Management Interface)",[ipfix-iana_at_cisco.com],1,2014-02-03 1598 248,metroEvcType,unsigned8,identifier,current,"The 3-bit EVC Service Attribute which identifies the type of 1599 service provided by an EVC.",,,"MEF 10.1 (Ethernet Services Attributes Phase 2) 1600 MEF16 (Ethernet Local Management Interface)",[ipfix-iana_at_cisco.com],0,2013-02-18 1601 249,pseudoWireId,unsigned32,identifier,current,"A 32-bit non-zero connection identifier, which together with the 1602 pseudoWireType, identifies the Pseudo Wire (PW) as defined in [RFC8077].",,,See [RFC8077] for pseudowire definitions.,[ipfix-iana_at_cisco.com],0,2013-02-18 1603 250,pseudoWireType,unsigned16,identifier,current,"The value of this information element identifies the type of MPLS 1604 Pseudo Wire (PW) as defined in [RFC4446].",,,"See [RFC4446] for the pseudowire type definition, and 1605 http://www.iana.org/assignments/pwe3-parameters for the IANA 1606 Pseudowire Types Registry.",[ipfix-iana_at_cisco.com],0,2013-02-18 1607 251,pseudoWireControlWord,unsigned32,identifier,current,"The 32-bit Preferred Pseudo Wire (PW) MPLS Control Word as 1608 defined in Section 3 of [RFC4385].",,,"See [RFC4385] for the Pseudo Wire Control Word 1609 definition.",[ipfix-iana_at_cisco.com],0,2013-02-18 1610 252,ingressPhysicalInterface,unsigned32,identifier,current,"The index of a networking device's physical interface (example, a 1611 switch port) where packets of this flow are being received.",,,See [RFC2863] for the definition of the ifIndex object.,[ipfix-iana_at_cisco.com],0,2013-02-18 1612 253,egressPhysicalInterface,unsigned32,identifier,current,"The index of a networking device's physical interface (example, a 1613 switch port) where packets of this flow are being sent.",,,See [RFC2863] for the definition of the ifIndex object.,[ipfix-iana_at_cisco.com],0,2013-02-18 1614 254,postDot1qVlanId,unsigned16,identifier,current,"The definition of this Information Element is identical to the 1615 definition of Information Element 'dot1qVlanId', except that it 1616 reports a potentially modified value caused by a middlebox 1617 function after the packet passed the Observation Point.",,,"[IEEE.802-3.2005] 1618 [IEEE.802-1ad.2005]",[ipfix-iana_at_cisco.com],0,2013-02-18 1619 255,postDot1qCustomerVlanId,unsigned16,identifier,current,"The definition of this Information Element is identical to the 1620 definition of Information Element 'dot1qCustomerVlanId', except 1621 that it reports a potentially modified value caused by a 1622 middlebox function after the packet passed the Observation Point.",,,"[IEEE.802-1ad.2005] 1623 [IEEE.802-1Q.2003]",[ipfix-iana_at_cisco.com],0,2013-02-18 1624 256,ethernetType,unsigned16,identifier,current,"The Ethernet type field of an Ethernet frame that identifies the 1625 MAC client protocol carried in the payload as defined in 1626 paragraph 1.4.349 of [IEEE.802-3.2005].",,,"[IEEE.802-3.2005] 1627 Ethertype registry available at 1628 [http://standards.ieee.org/regauth/ethertype/eth.txt]",[ipfix-iana_at_cisco.com],0,2013-02-18 1629 257,postIpPrecedence,unsigned8,identifier,current,"The definition of this Information Element is identical to the 1630 definition of Information Element 'ipPrecedence', except that 1631 it reports a potentially modified value caused by a middlebox 1632 function after the packet passed the Observation Point.",,0-7,"See [RFC1812] (Section 5.3.3) and 1633 [RFC791] for the definition of the 1634 IP Precedence. See [RFC1812] 1635 (Section 5.3.2) and [RFC791] for the 1636 definition of the IPv4 TOS field. See 1637 [RFC8200] for the definition of the 1638 IPv6 Traffic Class field.",[ipfix-iana_at_cisco.com],0,2013-02-18 1639 258,collectionTimeMilliseconds,dateTimeMilliseconds,default,current,"The absolute timestamp at which the data within the 1640 scope containing this Information Element was received by a 1641 Collecting Process. This Information Element SHOULD be bound to 1642 its containing IPFIX Message via IPFIX Options and the 1643 messageScope Information Element, as defined below.",milliseconds,,,[RFC5655][RFC Errata 3559],1,2013-03-26 1644 259,exportSctpStreamId,unsigned16,identifier,current,"The value of the SCTP Stream Identifier used by the 1645 Exporting Process for exporting IPFIX Message data. This is 1646 carried in the Stream Identifier field of the header of the SCTP 1647 DATA chunk containing the IPFIX Message(s).",,,,[RFC5655],0,2013-02-18 1648 260,maxExportSeconds,dateTimeSeconds,default,current,"The absolute Export Time of the latest IPFIX Message 1649 within the scope containing this Information Element. This 1650 Information Element SHOULD be bound to its containing IPFIX 1651 Transport Session via IPFIX Options and the sessionScope 1652 Information Element.",seconds,,,[RFC5655],0,2013-02-18 1653 261,maxFlowEndSeconds,dateTimeSeconds,default,current,"The latest absolute timestamp of the last packet 1654 within any Flow within the scope containing this Information 1655 Element, rounded up to the second if necessary. This Information 1656 Element SHOULD be bound to its containing IPFIX Transport Session 1657 via IPFIX Options and the sessionScope Information Element.",seconds,,,[RFC5655],0,2013-02-18 1658 262,messageMD5Checksum,octetArray,default,current,"The MD5 checksum of the IPFIX Message containing this 1659 record. This Information Element SHOULD be bound to its 1660 containing IPFIX Message via an options record and the 1661 messageScope Information Element, as defined below, and SHOULD 1662 appear only once in a given IPFIX Message. To calculate the value 1663 of this Information Element, first buffer the containing IPFIX 1664 Message, setting the value of this Information Element to all 1665 zeroes. Then calculate the MD5 checksum of the resulting buffer 1666 as defined in [RFC1321], place the resulting value in this 1667 Information Element, and export the buffered message. This 1668 Information Element is intended as a simple checksum only; 1669 therefore collision resistance and algorithm agility are not 1670 required, and MD5 is an appropriate message digest. 1671 1672 This Information Element has a fixed length of 16 octets.",,,,[RFC5655][RFC1321],0,2013-02-18 1673 263,messageScope,unsigned8,,current,"The presence of this Information Element as scope in 1674 an Options Template signifies that the options described by the 1675 Template apply to the IPFIX Message that contains them. It is 1676 defined for general purpose message scoping of options, and 1677 proposed specifically to allow the attachment a checksum to a 1678 message via IPFIX Options. The value of this Information Element 1679 MUST be written as 0 by the File Writer or Exporting Process. The 1680 value of this Information Element MUST be ignored by the File 1681 Reader or the Collecting Process.",,0-0,,[RFC5655],0,2013-02-18 1682 264,minExportSeconds,dateTimeSeconds,default,current,"The absolute Export Time of the earliest IPFIX Message 1683 within the scope containing this Information Element. This 1684 Information Element SHOULD be bound to its containing IPFIX 1685 Transport Session via an options record and the sessionScope 1686 Information Element.",seconds,,,[RFC5655],0,2013-02-18 1687 265,minFlowStartSeconds,dateTimeSeconds,default,current,"The earliest absolute timestamp of the first packet 1688 within any Flow within the scope containing this Information 1689 Element, rounded down to the second if necessary. This 1690 Information Element SHOULD be bound to its containing IPFIX 1691 Transport Session via an options record and the sessionScope 1692 Information Element.",seconds,,,[RFC5655],0,2013-02-18 1693 266,opaqueOctets,octetArray,default,current,"This Information Element is used to encapsulate non- 1694 IPFIX data into an IPFIX Message stream, for the purpose of 1695 allowing a non-IPFIX data processor to store a data stream inline 1696 within an IPFIX File. A Collecting Process or File Writer MUST 1697 NOT try to interpret this binary data. This Information Element 1698 differs from paddingOctets as its contents are meaningful in some 1699 non-IPFIX context, while the contents of paddingOctets MUST be 1700 0x00 and are intended only for Information Element alignment.",,,,[RFC5655],0,2013-02-18 1701 267,sessionScope,unsigned8,,current,"The presence of this Information Element as scope in 1702 an Options Template signifies that the options described by the 1703 Template apply to the IPFIX Transport Session that contains them. 1704 Note that as all options are implicitly scoped to Transport 1705 Session and Observation Domain, this Information Element is 1706 equivalent to a ""null"" scope. It is defined for general purpose 1707 session scoping of options, and proposed specifically to allow the 1708 attachment of time window to an IPFIX File via IPFIX Options. The 1709 value of this Information Element MUST be written as 0 by the File 1710 Writer or Exporting Process. The value of this Information 1711 Element MUST be ignored by the File Reader or the Collecting 1712 Process.",,0-0,,[RFC5655],0,2013-02-18 1713 268,maxFlowEndMicroseconds,dateTimeMicroseconds,default,current,"The latest absolute timestamp of the last packet 1714 within any Flow within the scope containing this Information 1715 Element, rounded up to the microsecond if necessary. This 1716 Information Element SHOULD be bound to its containing IPFIX 1717 Transport Session via IPFIX Options and the sessionScope 1718 Information Element. This Information Element SHOULD be used only 1719 in Transport Sessions containing Flow Records with microsecond- 1720 precision (or better) timestamp Information Elements.",microseconds,,,[RFC5655],0,2013-02-18 1721 269,maxFlowEndMilliseconds,dateTimeMilliseconds,default,current,"The latest absolute timestamp of the last packet 1722 within any Flow within the scope containing this Information 1723 Element, rounded up to the millisecond if necessary. This 1724 Information Element SHOULD be bound to its containing IPFIX 1725 Transport Session via IPFIX Options and the sessionScope 1726 Information Element. This Information Element SHOULD be used only 1727 in Transport Sessions containing Flow Records with millisecond- 1728 precision (or better) timestamp Information Elements.",milliseconds,,,[RFC5655],0,2013-02-18 1729 270,maxFlowEndNanoseconds,dateTimeNanoseconds,default,current,"The latest absolute timestamp of the last packet 1730 within any Flow within the scope containing this Information 1731 Element. This Information Element SHOULD be bound to its 1732 containing IPFIX Transport Session via IPFIX Options and the 1733 sessionScope Information Element. This Information Element SHOULD 1734 be used only in Transport Sessions containing Flow Records with 1735 nanosecond-precision timestamp Information Elements.",nanoseconds,,,[RFC5655],0,2013-02-18 1736 271,minFlowStartMicroseconds,dateTimeMicroseconds,default,current,"The earliest absolute timestamp of the first packet 1737 within any Flow within the scope containing this Information 1738 Element, rounded down to the microsecond if necessary. This 1739 Information Element SHOULD be bound to its containing IPFIX 1740 Transport Session via an options record and the sessionScope 1741 Information Element. This Information Element SHOULD be used only 1742 in Transport Sessions containing Flow Records with microsecond- 1743 precision (or better) timestamp Information Elements.",microseconds,,,[RFC5655],0,2013-02-18 1744 272,minFlowStartMilliseconds,dateTimeMilliseconds,default,current,"The earliest absolute timestamp of the first packet 1745 within any Flow within the scope containing this Information 1746 Element, rounded down to the millisecond if necessary. This 1747 Information Element SHOULD be bound to its containing IPFIX 1748 Transport Session via an options record and the sessionScope 1749 Information Element. This Information Element SHOULD be used only 1750 in Transport Sessions containing Flow Records with millisecond- 1751 precision (or better) timestamp Information Elements.",milliseconds,,,[RFC5655],0,2013-02-18 1752 273,minFlowStartNanoseconds,dateTimeNanoseconds,default,current,"The earliest absolute timestamp of the first packet 1753 within any Flow within the scope containing this Information 1754 Element. This Information Element SHOULD be bound to its 1755 containing IPFIX Transport Session via an options record and the 1756 sessionScope Information Element. This Information Element SHOULD 1757 be used only in Transport Sessions containing Flow Records with 1758 nanosecond-precision timestamp Information Elements.",nanoseconds,,,[RFC5655],0,2013-02-18 1759 274,collectorCertificate,octetArray,default,current,"The full X.509 certificate, encoded in ASN.1 DER 1760 format, used by the Collector when IPFIX Messages were transmitted 1761 using TLS or DTLS. This Information Element SHOULD be bound to 1762 its containing IPFIX Transport Session via an options record and 1763 the sessionScope Information Element, or to its containing IPFIX 1764 Message via an options record and the messageScope Information 1765 Element.",,,,[RFC5655],0,2013-02-18 1766 275,exporterCertificate,octetArray,default,current,"The full X.509 certificate, encoded in ASN.1 DER 1767 format, used by the Collector when IPFIX Messages were transmitted 1768 using TLS or DTLS. This Information Element SHOULD be bound to 1769 its containing IPFIX Transport Session via an options record and 1770 the sessionScope Information Element, or to its containing IPFIX 1771 Message via an options record and the messageScope Information 1772 Element.",,,,[RFC5655],0,2013-02-18 1773 276,dataRecordsReliability,boolean,default,current,"The export reliability of Data Records, within this SCTP 1774 stream, for the element(s) in the Options Template 1775 scope. A typical example of an element for which the 1776 export reliability will be reported is the templateID, 1777 as specified in the Data Records Reliability Options 1778 Template. A value of 'True' means that the Exporting 1779 Process MUST send any Data Records associated with the 1780 element(s) reliably within this SCTP stream. A value of 1781 'False' means that the Exporting Process MAY send any 1782 Data Records associated with the element(s) unreliably 1783 within this SCTP stream.",,,,[RFC6526],1,2014-02-03 1784 277,observationPointType,unsigned8,identifier,current,"Type of observation point. Values assigned to date are: 1785 1786 1787 1788 1789 1. Physical port 1790 1791 1792 1793 1794 2. Port channel 1795 1796 1797 1798 1799 3. Vlan.",,,,[ipfix-iana_at_cisco.com],0,2013-02-18 1800 278,newConnectionDeltaCount,unsigned32,deltaCounter,current,"This information element counts the number of TCP or UDP 1801 connections which were opened during the observation period. The 1802 observation period may be specified by the flow start and end timestamps.",,,,[ipfix-iana_at_cisco.com],1,2014-08-13 1803 279,connectionSumDurationSeconds,unsigned64,,current,"This information element aggregates the total time in 1804 seconds for all of the TCP or UDP connections which were in use during 1805 the observation period. For example if there are 5 concurrent 1806 connections each for 10 seconds, the value would be 50 s.",seconds,,,[ipfix-iana_at_cisco.com],1,2013-06-25 1807 280,connectionTransactionId,unsigned64,identifier,current,"This information element identifies a transaction within a 1808 connection. A transaction is a meaningful exchange of application data 1809 between two network devices or a client and server. A transactionId is 1810 assigned the first time a flow is reported, so that later reports for 1811 the same flow will have the same transactionId. A different 1812 transactionId is used for each transaction within a TCP or UDP 1813 connection. The identifiers need not be sequential.",,,,[ipfix-iana_at_cisco.com],0,2013-02-18 1814 281,postNATSourceIPv6Address,ipv6Address,default,current,"The definition of this Information Element is identical to 1815 the definition of Information Element 'sourceIPv6Address', except that 1816 it reports a modified value caused by a NAT64 middlebox function after 1817 the packet passed the Observation Point. 1818 1819 See [RFC8200] for the definition of the Source Address field in the IPv6 1820 header. See [RFC3234] for the definition of middleboxes. See 1821 [RFC6146] for nat64 specification.",,,,[ipfix-iana_at_cisco.com],0,2013-02-18 1822 282,postNATDestinationIPv6Address,ipv6Address,default,current,"The definition of this Information Element is identical to 1823 the definition of Information Element 'destinationIPv6Address', except 1824 that it reports a modified value caused by a NAT64 middlebox function 1825 after the packet passed the Observation Point. 1826 1827 See [RFC8200] for the definition of the Destination Address field in the 1828 IPv6 header. See [RFC3234] for the definition of middleboxes. See 1829 [RFC6146] for nat64 specification.",,,,[ipfix-iana_at_cisco.com],0,2013-02-18 1830 283,natPoolId,unsigned32,identifier,current,Locally unique identifier of a NAT pool.,,,,[ipfix-iana_at_cisco.com],0,2013-02-18 1831 284,natPoolName,string,default,current,The name of a NAT pool identified by a natPoolID.,,,,[ipfix-iana_at_cisco.com],0,2013-02-18 1832 285,anonymizationFlags,unsigned16,flags,current,"A flag word describing specialized modifications to 1833 the anonymization policy in effect for the anonymization technique 1834 applied to a referenced Information Element within a referenced 1835 Template. When flags are clear (0), the normal policy (as 1836 described by anonymizationTechnique) applies without modification. 1837 1838 1839 1840 MSB 14 13 12 11 10 9 8 7 6 5 4 3 2 1 LSB 1841 +---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+ 1842 | Reserved |LOR|PmA| SC | 1843 +---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+ 1844 1845 anonymizationFlags IE 1846 1847 +--------+----------+-----------------------------------------------+ 1848 | bit(s) | name | description | 1849 | (LSB = | | | 1850 | 0) | | | 1851 +--------+----------+-----------------------------------------------+ 1852 | 0-1 | SC | Stability Class: see the Stability Class | 1853 | | | table below, and section Section 5.1. | 1854 | 2 | PmA | Perimeter Anonymization: when set (1), | 1855 | | | source- Information Elements as described in | 1856 | | | [RFC5103] are interpreted as external | 1857 | | | addresses, and destination- Information | 1858 | | | Elements as described in [RFC5103] are | 1859 | | | interpreted as internal addresses, for the | 1860 | | | purposes of associating | 1861 | | | anonymizationTechnique to Information | 1862 | | | Elements only; see Section 7.2.2 for details. | 1863 | | | This bit MUST NOT be set when associated with | 1864 | | | a non-endpoint (i.e., source- or | 1865 | | | destination-) Information Element. SHOULD be | 1866 | | | consistent within a record (i.e., if a | 1867 | | | source- Information Element has this flag | 1868 | | | set, the corresponding destination- element | 1869 | | | SHOULD have this flag set, and vice-versa.) | 1870 | 3 | LOR | Low-Order Unchanged: when set (1), the | 1871 | | | low-order bits of the anonymized Information | 1872 | | | Element contain real data. This modification | 1873 | | | is intended for the anonymization of | 1874 | | | network-level addresses while leaving | 1875 | | | host-level addresses intact in order to | 1876 | | | preserve host level-structure, which could | 1877 | | | otherwise be used to reverse anonymization. | 1878 | | | MUST NOT be set when associated with a | 1879 | | | truncation-based anonymizationTechnique. | 1880 | 4-15 | Reserved | Reserved for future use: SHOULD be cleared | 1881 | | | (0) by the Exporting Process and MUST be | 1882 | | | ignored by the Collecting Process. | 1883 +--------+----------+-----------------------------------------------+ 1884 1885 1886 1887 The Stability Class portion of this flags word describes the 1888 stability class of the anonymization technique applied to a 1889 referenced Information Element within a referenced Template. 1890 Stability classes refer to the stability of the parameters of the 1891 anonymization technique, and therefore the comparability of the 1892 mapping between the real and anonymized values over time. This 1893 determines which anonymized datasets may be compared with each 1894 other. Values are as follows: 1895 1896 1897 1898 +-----+-----+-------------------------------------------------------+ 1899 | Bit | Bit | Description | 1900 | 1 | 0 | | 1901 +-----+-----+-------------------------------------------------------+ 1902 | 0 | 0 | Undefined: the Exporting Process makes no | 1903 | | | representation as to how stable the mapping is, or | 1904 | | | over what time period values of this field will | 1905 | | | remain comparable; while the Collecting Process MAY | 1906 | | | assume Session level stability, Session level | 1907 | | | stability is not guaranteed. Processes SHOULD assume | 1908 | | | this is the case in the absence of stability class | 1909 | | | information; this is the default stability class. | 1910 | 0 | 1 | Session: the Exporting Process will ensure that the | 1911 | | | parameters of the anonymization technique are stable | 1912 | | | during the Transport Session. All the values of the | 1913 | | | described Information Element for each Record | 1914 | | | described by the referenced Template within the | 1915 | | | Transport Session are comparable. The Exporting | 1916 | | | Process SHOULD endeavour to ensure at least this | 1917 | | | stability class. | 1918 | 1 | 0 | Exporter-Collector Pair: the Exporting Process will | 1919 | | | ensure that the parameters of the anonymization | 1920 | | | technique are stable across Transport Sessions over | 1921 | | | time with the given Collecting Process, but may use | 1922 | | | different parameters for different Collecting | 1923 | | | Processes. Data exported to different Collecting | 1924 | | | Processes are not comparable. | 1925 | 1 | 1 | Stable: the Exporting Process will ensure that the | 1926 | | | parameters of the anonymization technique are stable | 1927 | | | across Transport Sessions over time, regardless of | 1928 | | | the Collecting Process to which it is sent. | 1929 +-----+-----+-------------------------------------------------------+",,,,[RFC6235],0,2013-02-18 1930 286,anonymizationTechnique,unsigned16,identifier,current,"A description of the anonymization technique applied 1931 to a referenced Information Element within a referenced Template. 1932 Each technique may be applicable only to certain Information 1933 Elements and recommended only for certain Infomation Elements; 1934 these restrictions are noted in the table below. 1935 1936 1937 1938 +-------+---------------------------+-----------------+-------------+ 1939 | Value | Description | Applicable to | Recommended | 1940 | | | | for | 1941 +-------+---------------------------+-----------------+-------------+ 1942 | 0 | Undefined: the Exporting | all | all | 1943 | | Process makes no | | | 1944 | | representation as to | | | 1945 | | whether the defined field | | | 1946 | | is anonymized or not. | | | 1947 | | While the Collecting | | | 1948 | | Process MAY assume that | | | 1949 | | the field is not | | | 1950 | | anonymized, it is not | | | 1951 | | guaranteed not to be. | | | 1952 | | This is the default | | | 1953 | | anonymization technique. | | | 1954 | 1 | None: the values exported | all | all | 1955 | | are real. | | | 1956 | 2 | Precision | all | all | 1957 | | Degradation/Truncation: | | | 1958 | | the values exported are | | | 1959 | | anonymized using simple | | | 1960 | | precision degradation or | | | 1961 | | truncation. The new | | | 1962 | | precision or number of | | | 1963 | | truncated bits is | | | 1964 | | implicit in the exported | | | 1965 | | data, and can be deduced | | | 1966 | | by the Collecting | | | 1967 | | Process. | | | 1968 | 3 | Binning: the values | all | all | 1969 | | exported are anonymized | | | 1970 | | into bins. | | | 1971 | 4 | Enumeration: the values | all | timestamps | 1972 | | exported are anonymized | | | 1973 | | by enumeration. | | | 1974 | 5 | Permutation: the values | all | identifiers | 1975 | | exported are anonymized | | | 1976 | | by permutation. | | | 1977 | 6 | Structured Permutation: | addresses | | 1978 | | the values exported are | | | 1979 | | anonymized by | | | 1980 | | permutation, preserving | | | 1981 | | bit-level structure as | | | 1982 | | appropriate; this | | | 1983 | | represents | | | 1984 | | prefix-preserving IP | | | 1985 | | address anonymization or | | | 1986 | | structured MAC address | | | 1987 | | anonymization. | | | 1988 | 7 | Reverse Truncation: the | addresses | | 1989 | | values exported are | | | 1990 | | anonymized using reverse | | | 1991 | | truncation. The number | | | 1992 | | of truncated bits is | | | 1993 | | implicit in the exported | | | 1994 | | data, and can be deduced | | | 1995 | | by the Collecting | | | 1996 | | Process. | | | 1997 | 8 | Noise: the values | non-identifiers | counters | 1998 | | exported are anonymized | | | 1999 | | by adding random noise to | | | 2000 | | each value. | | | 2001 | 9 | Offset: the values | all | timestamps | 2002 | | exported are anonymized | | | 2003 | | by adding a single offset | | | 2004 | | to all values. | | | 2005 +-------+---------------------------+-----------------+-------------+",,,,[RFC6235],0,2013-02-18 2006 287,informationElementIndex,unsigned16,identifier,current,"A zero-based index of an Information Element 2007 referenced by informationElementId within a Template referenced by 2008 templateId; used to disambiguate scope for templates containing 2009 multiple identical Information Elements.",,,,[RFC6235],0,2013-02-18 2010 288,p2pTechnology,string,default,current,"Specifies if the Application ID is based on peer-to-peer 2011 technology. 2012 2013 2014 2015 2016 Possible values are: { ""yes"", ""y"", 1 }, 2017 { ""no"", ""n"", 2 } and { ""unassigned"", ""u"", 0 }.",,,,[RFC6759],0,2013-02-18 2018 289,tunnelTechnology,string,default,current,"Specifies if the Application ID is used as a tunnel technology. 2019 2020 2021 2022 2023 Possible values are: { ""yes"", ""y"", 1 }, { ""no"", ""n"", 2 } and 2024 { ""unassigned"", ""u"", 0 }.",,,,[RFC6759],0,2013-02-18 2025 290,encryptedTechnology,string,default,current,"Specifies if the Application ID is an encrypted networking 2026 protocol. 2027 2028 2029 2030 Possible values are: { ""yes"", ""y"", 1 }, 2031 { ""no"", ""n"", 2 } and { ""unassigned"", ""u"", 0 }.",,,,[RFC6759],0,2013-02-18 2032 291,basicList,basicList,list,current,"Specifies a generic Information Element with a basicList abstract 2033 data type. For example, a list of port numbers, a list of 2034 interface indexes, etc.",,,,[RFC6313],0,2013-02-18 2035 292,subTemplateList,subTemplateList,list,current,"Specifies a generic Information Element with a subTemplateList 2036 abstract data type.",,,,[RFC6313],0,2013-02-18 2037 293,subTemplateMultiList,subTemplateMultiList,list,current,"Specifies a generic Information Element with a 2038 subTemplateMultiList abstract data type.",,,,[RFC6313],0,2013-02-18 2039 294,bgpValidityState,unsigned8,identifier,current,"This element describes the ""validity state"" of the BGP route correspondent source or destination IP address. If the ""validity state"" for this Flow is only available, then the value of this Information Element is 255.",,,"See [RFC4271] for a description of BGP-4, 2040 [RFC6811] for the 2041 definition of ""validity states"" and 2042 [draft-ietf-sidr-origin-validation-signaling] 2043 for the encoding of those ""validity states"".",[ipfix-iana_at_cisco.com],0,2013-02-18 2044 295,IPSecSPI,unsigned32,identifier,current,IPSec Security Parameters Index (SPI).,,,See [RFC2401] for the definition of SPI.,[ipfix-iana_at_cisco.com],0,2013-02-18 2045 296,greKey,unsigned32,identifier,current,"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.,[ipfix-iana_at_cisco.com],0,2013-02-18 2046 297,natType,unsigned8,identifier,current,"The type of NAT treatment: 2047 2048 2049 2050 2051 0 unknown 2052 2053 2054 2055 2056 1 NAT44 translated 2057 2058 2059 2060 2061 2 NAT64 translated 2062 2063 2064 2065 2066 3 NAT46 translated 2067 2068 2069 2070 2071 4 IPv4-->IPv4 (no NAT) 2072 2073 2074 2075 2076 5 NAT66 translated 2077 2078 2079 2080 2081 6 IPv6-->IPv6 (no NAT)",,,"See [RFC3022] for the definition of NAT. 2082 See [RFC1631] for the definition of NAT44. 2083 See [RFC6144] for the definition of NAT64. 2084 See [RFC6146] for the definition of NAT46. 2085 See [RFC6296] for the definition of NAT66. 2086 See [RFC791] for the definition of IPv4. 2087 See [RFC8200] for the definition of IPv6.",[ipfix-iana_at_cisco.com],0,2013-02-18 2088 298,initiatorPackets,unsigned64,deltaCounter,current,"The total number of layer 4 packets in a flow from the initiator 2089 since the previous report. The initiator is the device which 2090 triggered the session creation, and remains the same for the life 2091 of the session.",packets,,"See #231, initiatorOctets.",[ipfix-iana_at_cisco.com],1,2014-08-13 2092 299,responderPackets,unsigned64,deltaCounter,current,"The total number of layer 4 packets in a flow from the responder 2093 since the previous report. The responder is the device which 2094 replies to the initiator, and remains the same for the life of the 2095 session.",packets,,"See #232, responderOctets.",[ipfix-iana_at_cisco.com],1,2014-08-13 2096 300,observationDomainName,string,default,current,"The name of an observation domain identified by an 2097 observationDomainId.",,,"See #149, observationDomainId.",[ipfix-iana_at_cisco.com],0,2013-02-18 2098 301,selectionSequenceId,unsigned64,identifier,current,"From all the packets observed at an Observation Point, a subset of 2099 the packets is selected by a sequence of one or more Selectors. 2100 The selectionSequenceId is a unique value per Observation Domain, 2101 specifying the Observation Point and the sequence of Selectors 2102 through which the packets are selected.",,,,[RFC5477],0,2013-02-18 2103 302,selectorId,unsigned64,identifier,current,"The Selector ID is the unique ID identifying a Primitive Selector. 2104 Each Primitive Selector must have a unique ID in the Observation 2105 Domain.",,,,[RFC5477][RFC Errata 2052],0,2013-02-18 2106 303,informationElementId,unsigned16,identifier,current,"This Information Element contains the ID of another Information 2107 Element.",,,,[RFC5477],0,2013-02-18 2108 304,selectorAlgorithm,unsigned16,identifier,current,"This Information Element identifies the packet selection methods 2109 (e.g., Filtering, Sampling) that are applied by the Selection 2110 Process. 2111 2112 2113 2114 2115 Most of these methods have parameters. Further Information 2116 Elements are needed to fully specify packet selection with these 2117 methods and all their parameters. 2118 2119 2120 2121 2122 The methods listed below are defined in [RFC5475]. For their parameters, Information Elements are defined in 2123 the information model document. The names of these Information 2124 Elements are listed for each method identifier. 2125 2126 2127 2128 2129 Further method identifiers may be added to the list below. It 2130 might be necessary to define new Information Elements to specify 2131 their parameters. 2132 2133 2134 2135 2136 The selectorAlgorithm registry is maintained by IANA. New 2137 assignments for the registry will be administered by IANA, and 2138 are subject to Expert Review [RFC8126]. 2139 2140 2141 2142 2143 The registry can be updated when specifications of the new 2144 method(s) and any new Information Elements are provided. 2145 2146 2147 2148 2149 The group of experts must double check the selectorAlgorithm 2150 definitions and Information Elements with already defined 2151 selectorAlgorithms and Information Elements for completeness, 2152 accuracy, and redundancy. Those experts will initially be drawn 2153 from the Working Group Chairs and document editors of the IPFIX 2154 and PSAMP Working Groups. 2155 2156 2157 2158 2159 The following packet selection methods identifiers are defined 2160 here: 2161 2162 2163 2164 2165 [IANA registry psamp-parameters] 2166 2167 2168 2169 2170 There is a broad variety of possible parameters that could be used 2171 for Property match Filtering (5) but currently there are no agreed 2172 parameters specified.",,,,[RFC5477],0,2013-02-18 2173 305,samplingPacketInterval,unsigned32,quantity,current,"This Information Element specifies the number of packets that are 2174 consecutively sampled. A value of 100 means that 100 2175 consecutive packets are sampled. 2176 2177 2178 2179 2180 For example, this Information Element may be used to describe the 2181 configuration of a systematic count-based Sampling Selector.",packets,,,[RFC5477],0,2013-02-18 2182 306,samplingPacketSpace,unsigned32,quantity,current,"This Information Element specifies the number of packets between 2183 two ""samplingPacketInterval""s. A value of 100 means that the next 2184 interval starts 100 packets (which are not sampled) after the 2185 current ""samplingPacketInterval"" is over. 2186 2187 2188 2189 2190 For example, this Information Element may be used to describe the 2191 configuration of a systematic count-based Sampling Selector.",packets,,,[RFC5477],0,2013-02-18 2192 307,samplingTimeInterval,unsigned32,quantity,current,"This Information Element specifies the time interval in 2193 microseconds during which all arriving packets are sampled. 2194 2195 2196 2197 2198 For example, this Information Element may be used to describe the 2199 configuration of a systematic time-based Sampling Selector.",microseconds,,,[RFC5477],0,2013-02-18 2200 308,samplingTimeSpace,unsigned32,quantity,current,"This Information Element specifies the time interval in 2201 microseconds between two ""samplingTimeInterval""s. A value of 100 2202 means that the next interval starts 100 microseconds (during which 2203 no packets are sampled) after the current ""samplingTimeInterval"" 2204 is over. 2205 2206 2207 2208 2209 For example, this Information Element may used to describe the 2210 configuration of a systematic time-based Sampling Selector.",microseconds,,,[RFC5477],0,2013-02-18 2211 309,samplingSize,unsigned32,quantity,current,"This Information Element specifies the number of elements taken 2212 from the parent Population for random Sampling methods. 2213 2214 2215 2216 2217 For example, this Information Element may be used to describe the 2218 configuration of a random n-out-of-N Sampling Selector.",packets,,,[RFC5477],0,2013-02-18 2219 310,samplingPopulation,unsigned32,quantity,current,"This Information Element specifies the number of elements in the 2220 parent Population for random Sampling methods. 2221 2222 2223 2224 2225 For example, this Information Element may be used to describe the 2226 configuration of a random n-out-of-N Sampling Selector.",packets,,,[RFC5477],0,2013-02-18 2227 311,samplingProbability,float64,quantity,current,"This Information Element specifies the probability that a packet 2228 is sampled, expressed as a value between 0 and 1. The probability 2229 is equal for every packet. A value of 0 means no packet was 2230 sampled since the probability is 0. 2231 2232 2233 2234 2235 For example, this Information Element may be used to describe the 2236 configuration of a uniform probabilistic Sampling Selector.",,,,[RFC5477],0,2013-02-18 2237 312,dataLinkFrameSize,unsigned16,quantity,current,"This Information Element specifies the length of the selected data 2238 link frame. 2239 2240 2241 2242 2243 The data link layer is defined in [ISO/IEC.7498-1:1994].",,,[ISO/IEC.7498-1:1994],[RFC7133],1,2014-01-11 2244 313,ipHeaderPacketSection,octetArray,default,current,"This Information Element carries a series of n octets from the IP 2245 header of a sampled packet, starting sectionOffset octets into the 2246 IP header. 2247 2248 2249 2250 2251 However, if no sectionOffset field corresponding to this 2252 Information Element is present, then a sectionOffset of zero 2253 applies, and the octets MUST be from the start of the IP header. 2254 2255 2256 2257 2258 With sufficient length, this element also reports octets from the 2259 IP payload. However, full packet capture of arbitrary packet 2260 streams is explicitly out of scope per the Security Considerations 2261 sections of [RFC5477] and [RFC2804]. 2262 2263 2264 2265 2266 The sectionExportedOctets expresses how much data was exported, 2267 while the remainder is padding. 2268 2269 2270 2271 2272 When the sectionExportedOctets field corresponding to this 2273 Information Element exists, this Information Element MAY have a 2274 fixed length and MAY be padded, or it MAY have a variable length. 2275 2276 2277 2278 2279 When the sectionExportedOctets field corresponding to this 2280 Information Element does not exist, this Information Element 2281 SHOULD have a variable length and MUST NOT be padded. In this 2282 case, the size of the exported section may be constrained due to 2283 limitations in the IPFIX protocol.",,,"[RFC2804] 2284 [RFC5477]",[RFC5477][RFC7133],1,2014-01-11 2285 314,ipPayloadPacketSection,octetArray,default,current,"This Information Element carries a series of n octets from the IP 2286 payload of a sampled packet, starting sectionOffset octets into 2287 the IP payload. 2288 2289 2290 2291 2292 However, if no sectionOffset field corresponding to this 2293 Information Element is present, then a sectionOffset of zero 2294 applies, and the octets MUST be from the start of the IP payload. 2295 2296 2297 2298 2299 The IPv4 payload is that part of the packet that follows the IPv4 2300 header and any options, which [RFC791] refers to as ""data"" or 2301 ""data octets"". For example, see the examples in [RFC791], 2302 Appendix A. 2303 2304 2305 2306 2307 The IPv6 payload is the rest of the packet following the 40-octet 2308 IPv6 header. Note that any extension headers present are 2309 considered part of the payload. See [RFC8200] for the IPv6 2310 specification. 2311 2312 2313 2314 2315 The sectionExportedOctets expresses how much data was observed, 2316 while the remainder is padding. 2317 2318 2319 2320 2321 When the sectionExportedOctets field corresponding to this 2322 Information Element exists, this Information Element MAY have a 2323 fixed length and MAY be padded, or MAY have a variable length. 2324 2325 2326 2327 2328 When the sectionExportedOctets field corresponding to this 2329 Information Element does not exist, this Information Element 2330 SHOULD have a variable length and MUST NOT be padded. In this 2331 case, the size of the exported section may be constrained due to 2332 limitations in the IPFIX protocol.",,,"[RFC791] 2333 [RFC8200]",[RFC5477][RFC7133],1,2014-01-11 2334 315,dataLinkFrameSection,octetArray,default,current,"This Information Element carries n octets from the data link frame 2335 of a selected frame, starting sectionOffset octets into the frame. 2336 2337 2338 2339 2340 However, if no sectionOffset field corresponding to this 2341 Information Element is present, then a sectionOffset of zero 2342 applies, and the octets MUST be from the start of the data link 2343 frame. 2344 2345 2346 2347 2348 The sectionExportedOctets expresses how much data was observed, 2349 while the remainder is padding. 2350 2351 2352 2353 2354 When the sectionExportedOctets field corresponding to this 2355 Information Element exists, this Information Element MAY have a 2356 fixed length and MAY be padded, or MAY have a variable length. 2357 2358 2359 2360 2361 When the sectionExportedOctets field corresponding to this 2362 Information Element does not exist, this Information Element 2363 SHOULD have a variable length and MUST NOT be padded. In this 2364 case, the size of the exported section may be constrained due to 2365 limitations in the IPFIX protocol. 2366 2367 2368 2369 2370 Further Information Elements, i.e., dataLinkFrameType and 2371 dataLinkFrameSize, are needed to specify the data link type and the 2372 size of the data link frame of this Information Element. A set of 2373 these Information Elements MAY be contained in a structured data 2374 type, as expressed in [RFC6313]. Or a set of these Information 2375 Elements MAY be contained in one Flow Record as shown in Appendix 2376 B of [RFC7133]. 2377 2378 2379 2380 2381 The data link layer is defined in [ISO/IEC.7498-1:1994].",,,"[RFC6313] 2382 [RFC7133] 2383 [ISO/IEC.7498-1:1994]",[RFC7133],1,2014-01-11 2384 316,mplsLabelStackSection,octetArray,default,current,"This Information Element carries a series of n octets from the 2385 MPLS label stack of a sampled packet, starting sectionOffset 2386 octets into the MPLS label stack. 2387 2388 2389 2390 2391 However, if no sectionOffset field corresponding to this 2392 Information Element is present, then a sectionOffset of zero 2393 applies, and the octets MUST be from the head of the MPLS label 2394 stack. 2395 2396 2397 2398 2399 With sufficient length, this element also reports octets from the 2400 MPLS payload. However, full packet capture of arbitrary packet 2401 streams is explicitly out of scope per the Security Considerations 2402 sections of [RFC5477] and [RFC2804]. 2403 2404 2405 2406 2407 See [RFC3031] for the specification of MPLS packets. 2408 2409 2410 2411 2412 See [RFC3032] for the specification of the MPLS label stack. 2413 2414 2415 2416 2417 The sectionExportedOctets expresses how much data was observed, 2418 while the remainder is padding. 2419 2420 2421 2422 2423 When the sectionExportedOctets field corresponding to this 2424 Information Element exists, this Information Element MAY have a 2425 fixed length and MAY be padded, or MAY have a variable length. 2426 2427 2428 2429 2430 When the sectionExportedOctets field corresponding to this 2431 Information Element does not exist, this Information Element 2432 SHOULD have a variable length and MUST NOT be padded. In this 2433 case, the size of the exported section may be constrained due to 2434 limitations in the IPFIX protocol.",,,"[RFC2804] 2435 [RFC3031] 2436 [RFC3032] 2437 [RFC5477]",[RFC5477][RFC7133],1,2014-01-11 2438 317,mplsPayloadPacketSection,octetArray,default,current,"The mplsPayloadPacketSection carries a series of n octets from the 2439 MPLS payload of a sampled packet, starting sectionOffset octets 2440 into the MPLS payload, as it is data that follows immediately after 2441 the MPLS label stack. 2442 2443 2444 2445 2446 However, if no sectionOffset field corresponding to this 2447 Information Element is present, then a sectionOffset of zero 2448 applies, and the octets MUST be from the start of the MPLS 2449 payload. 2450 2451 2452 2453 2454 See [RFC3031] for the specification of MPLS packets. 2455 2456 2457 2458 2459 See [RFC3032] for the specification of the MPLS label stack. 2460 2461 2462 2463 2464 The sectionExportedOctets expresses how much data was observed, 2465 while the remainder is padding. 2466 2467 2468 2469 2470 When the sectionExportedOctets field corresponding to this 2471 Information Element exists, this Information Element MAY have a 2472 fixed length and MAY be padded, or it MAY have a variable length. 2473 2474 2475 2476 2477 When the sectionExportedOctets field corresponding to this 2478 Information Element does not exist, this Information Element 2479 SHOULD have a variable length and MUST NOT be padded. In this 2480 case, the size of the exported section may be constrained due to 2481 limitations in the IPFIX protocol.",,,"[RFC3031] 2482 [RFC3032]",[RFC5477][RFC7133],1,2014-01-11 2483 318,selectorIdTotalPktsObserved,unsigned64,totalCounter,current,"This Information Element specifies the total number of packets 2484 observed by a Selector, for a specific value of SelectorId. 2485 2486 2487 2488 2489 This Information Element should be used in an Options Template 2490 scoped to the observation to which it refers. See Section 3.4.2.1 2491 of the IPFIX protocol document [RFC7011].",packets,,,[RFC5477],0,2013-02-18 2492 319,selectorIdTotalPktsSelected,unsigned64,totalCounter,current,"This Information Element specifies the total number of packets 2493 selected by a Selector, for a specific value of SelectorId. 2494 2495 2496 2497 2498 This Information Element should be used in an Options Template 2499 scoped to the observation to which it refers. See Section 3.4.2.1 2500 of the IPFIX protocol document [RFC7011].",packets,,,[RFC5477],0,2013-02-18 2501 320,absoluteError,float64,quantity,current,"This Information Element specifies the maximum possible 2502 measurement error of the reported value for a given Information 2503 Element. The absoluteError has the same unit as the Information 2504 Element with which it is associated. The real value of the metric can 2505 differ by absoluteError (positive or negative) from the measured 2506 value. 2507 2508 2509 2510 2511 This Information Element provides only the error for measured 2512 values. If an Information Element contains an estimated value 2513 (from Sampling), the confidence boundaries and confidence level 2514 have to be provided instead, using the upperCILimit, lowerCILimit, 2515 and confidenceLevel Information Elements. 2516 2517 2518 2519 2520 This Information Element should be used in an Options Template 2521 scoped to the observation to which it refers. See Section 3.4.2.1 2522 of the IPFIX protocol document [RFC7011].",inferred,,,[RFC5477],1,2018-06-13 2523 321,relativeError,float64,quantity,current,"This Information Element specifies the maximum possible positive 2524 or negative error ratio for the reported value for a given 2525 Information Element as percentage of the measured value. The real 2526 value of the metric can differ by relativeError percent (positive 2527 or negative) from the measured value. 2528 2529 2530 2531 2532 This Information Element provides only the error for measured 2533 values. If an Information Element contains an estimated value 2534 (from Sampling), the confidence boundaries and confidence level 2535 have to be provided instead, using the upperCILimit, lowerCILimit, 2536 and confidenceLevel Information Elements. 2537 2538 2539 2540 2541 This Information Element should be used in an Options Template 2542 scoped to the observation to which it refers. See Section 3.4.2.1 2543 of the IPFIX protocol document [RFC7011].",,,,[RFC5477],0,2013-02-18 2544 322,observationTimeSeconds,dateTimeSeconds,default,current,"This Information Element specifies the absolute time in seconds of 2545 an observation.",seconds,,,[RFC5477],1,2014-02-03 2546 323,observationTimeMilliseconds,dateTimeMilliseconds,default,current,"This Information Element specifies the absolute time in 2547 milliseconds of an observation.",milliseconds,,,[RFC5477],1,2014-02-03 2548 324,observationTimeMicroseconds,dateTimeMicroseconds,default,current,"This Information Element specifies the absolute time in 2549 microseconds of an observation.",microseconds,,,[RFC5477],1,2014-02-03 2550 325,observationTimeNanoseconds,dateTimeNanoseconds,default,current,"This Information Element specifies the absolute time in 2551 nanoseconds of an observation.",nanoseconds,,,[RFC5477],1,2014-02-03 2552 326,digestHashValue,unsigned64,quantity,current,"This Information Element specifies the value from the digest hash 2553 function. 2554 2555 See also Sections 6.2, 3.8 and 7.1 of [RFC5475].",,,,[RFC5477],0,2013-02-18 2556 327,hashIPPayloadOffset,unsigned64,quantity,current,"This Information Element specifies the IP payload offset used by a 2557 Hash-based Selection Selector. 2558 2559 See also Sections 6.2, 3.8 and 7.1 of [RFC5475].",,,,[RFC5477],0,2013-02-18 2560 328,hashIPPayloadSize,unsigned64,quantity,current,"This Information Element specifies the IP payload size used by a 2561 Hash-based Selection Selector. See also Sections 6.2, 3.8 and 7.1 of 2562 [RFC5475].",,,,[RFC5477],0,2013-02-18 2563 329,hashOutputRangeMin,unsigned64,quantity,current,"This Information Element specifies the value for the beginning of 2564 a hash function's potential output range. 2565 2566 2567 2568 2569 See also Sections 6.2, 3.8 and 7.1 of [RFC5475].",,,,[RFC5477],0,2013-02-18 2570 330,hashOutputRangeMax,unsigned64,quantity,current,"This Information Element specifies the value for the end of a hash 2571 function's potential output range. 2572 2573 2574 2575 2576 See also Sections 6.2, 3.8 and 7.1 of [RFC5475].",,,,[RFC5477],0,2013-02-18 2577 331,hashSelectedRangeMin,unsigned64,quantity,current,"This Information Element specifies the value for the beginning of 2578 a hash function's selected range. 2579 2580 2581 2582 2583 See also Sections 6.2, 3.8 and 7.1 of [RFC5475].",,,,[RFC5477],0,2013-02-18 2584 332,hashSelectedRangeMax,unsigned64,quantity,current,"This Information Element specifies the value for the end of a hash 2585 function's selected range. 2586 2587 2588 2589 2590 See also Sections 6.2, 3.8 and 7.1 of [RFC5475].",,,,[RFC5477],0,2013-02-18 2591 333,hashDigestOutput,boolean,default,current,"This Information Element contains a boolean value that is TRUE if 2592 the output from this hash Selector has been configured to be 2593 included in the packet report as a packet digest, else FALSE. 2594 2595 2596 2597 2598 See also Sections 6.2, 3.8 and 7.1 of [RFC5475].",,,,[RFC5477],1,2014-02-03 2599 334,hashInitialiserValue,unsigned64,quantity,current,"This Information Element specifies the initialiser value to the 2600 hash function. 2601 2602 2603 2604 2605 See also Sections 6.2, 3.8 and 7.1 of [RFC5475].",,,,[RFC5477],0,2013-02-18 2606 335,selectorName,string,default,current,"The name of a selector identified by a selectorID. Globally 2607 unique per Metering Process.",,,,[ipfix-iana_at_cisco.com],0,2013-02-18 2608 336,upperCILimit,float64,quantity,current,"This Information Element specifies the upper limit of a confidence 2609 interval. It is used to provide an accuracy statement for an 2610 estimated value. The confidence limits define the range in which 2611 the real value is assumed to be with a certain probability p. 2612 Confidence limits always need to be associated with a confidence 2613 level that defines this probability p. Please note that a 2614 confidence interval only provides a probability that the real 2615 value lies within the limits. That means the real value can lie 2616 outside the confidence limits. 2617 2618 2619 2620 2621 The upperCILimit, lowerCILimit, and confidenceLevel Information 2622 Elements should all be used in an Options Template scoped to the 2623 observation to which they refer. See Section 3.4.2.1 of the IPFIX 2624 protocol document [RFC7011]. 2625 2626 2627 2628 2629 Note that the upperCILimit, lowerCILimit, and confidenceLevel are 2630 all required to specify confidence, and should be disregarded 2631 unless all three are specified together.",,,,[RFC5477],0,2013-02-18 2632 337,lowerCILimit,float64,quantity,current,"This Information Element specifies the lower limit of a confidence 2633 interval. For further information, see the description of 2634 upperCILimit. 2635 2636 2637 2638 2639 The upperCILimit, lowerCILimit, and confidenceLevel Information 2640 Elements should all be used in an Options Template scoped to the 2641 observation to which they refer. See Section 3.4.2.1 of the IPFIX 2642 protocol document [RFC7011]. 2643 2644 2645 2646 2647 Note that the upperCILimit, lowerCILimit, and confidenceLevel are 2648 all required to specify confidence, and should be disregarded 2649 unless all three are specified together.",,,,[RFC5477],0,2013-02-18 2650 338,confidenceLevel,float64,quantity,current,"This Information Element specifies the confidence level. It is 2651 used to provide an accuracy statement for estimated values. The 2652 confidence level provides the probability p with which the real 2653 value lies within a given range. A confidence level always needs 2654 to be associated with confidence limits that define the range in 2655 which the real value is assumed to be. 2656 2657 2658 2659 2660 The upperCILimit, lowerCILimit, and confidenceLevel Information 2661 Elements should all be used in an Options Template scoped to the 2662 observation to which they refer. See Section 3.4.2.1 of the IPFIX 2663 protocol document [RFC7011]. 2664 2665 2666 2667 2668 Note that the upperCILimit, lowerCILimit, and confidenceLevel are 2669 all required to specify confidence, and should be disregarded 2670 unless all three are specified together.",,,,[RFC5477],0,2013-02-18 2671 339,informationElementDataType,unsigned8,,current,"A description of the abstract data type of an IPFIX 2672 information element.These are taken from the abstract data types 2673 defined in section 3.1 of the IPFIX Information Model [RFC5102]; 2674 see that section for more information on the types described 2675 in the informationElementDataType sub-registry. 2676 2677 2678 2679 2680 These types are registered in the IANA IPFIX Information Element 2681 Data Type subregistry. This subregistry is intended to assign 2682 numbers for type names, not to provide a mechanism for adding data 2683 types to the IPFIX Protocol, and as such requires a Standards 2684 Action [RFC8126] to modify.",,,,[RFC5610],0,2013-02-18 2685 340,informationElementDescription,string,default,current,"A UTF-8 [RFC3629] encoded Unicode string containing a 2686 human-readable description of an Information Element. The content 2687 of the informationElementDescription MAY be annotated with one or 2688 more language tags [RFC4646], encoded in-line [RFC2482] within the 2689 UTF-8 string, in order to specify the language in which the 2690 description is written. Description text in multiple languages 2691 MAY tag each section with its own language tag; in this case, the 2692 description information in each language SHOULD have equivalent 2693 meaning. In the absence of any language tag, the ""i-default"" 2694 [RFC2277] language SHOULD be assumed. See the Security 2695 Considerations section for notes on string handling for 2696 Information Element type records.",,,,[RFC5610],0,2013-02-18 2697 341,informationElementName,string,default,current,"A UTF-8 [RFC3629] encoded Unicode string containing 2698 the name of an Information Element, intended as a simple 2699 identifier. See the Security Considerations section for notes on 2700 string handling for Information Element type records",,,,[RFC5610],0,2013-02-18 2701 342,informationElementRangeBegin,unsigned64,quantity,current,"Contains the inclusive low end of the range of 2702 acceptable values for an Information Element.",,,,[RFC5610],0,2013-02-18 2703 343,informationElementRangeEnd,unsigned64,quantity,current,"Contains the inclusive high end of the range of 2704 acceptable values for an Information Element.",,,,[RFC5610],0,2013-02-18 2705 344,informationElementSemantics,unsigned8,,current,"A description of the semantics of an IPFIX Information 2706 Element. These are taken from the data type semantics defined in 2707 section 3.2 of the IPFIX Information Model [RFC5102]; see that 2708 section for more information on the types defined in the informationElementSemantics sub-registry. This 2709 field may take the values in Table ; the special value 0x00 2710 (default) is used to note that no semantics apply to the field; it 2711 cannot be manipulated by a Collecting Process or File Reader that 2712 does not understand it a priori. 2713 2714 2715 2716 2717 These semantics are registered in the IANA IPFIX Information 2718 Element Semantics subregistry. This subregistry is intended to 2719 assign numbers for semantics names, not to provide a mechanism for 2720 adding semantics to the IPFIX Protocol, and as such requires a 2721 Standards Action [RFC8126] to modify.",,,,[RFC5610],0,2013-02-18 2722 345,informationElementUnits,unsigned16,,current,"A description of the units of an IPFIX Information 2723 Element. These correspond to the units implicitly defined in the 2724 Information Element definitions in section 5 of the IPFIX 2725 Information Model [RFC5102]; see that section for more information 2726 on the types described in the informationElementsUnits sub-registry. This field may take the values in 2727 Table 3 below; the special value 0x00 (none) is used to note that 2728 the field is unitless. 2729 2730 2731 2732 2733 These types are registered in the IANA IPFIX Information Element 2734 Units subregistry; new types may be added on a First Come First 2735 Served [RFC8126] basis.",,,,[RFC5610],0,2013-02-18 2736 346,privateEnterpriseNumber,unsigned32,identifier,current,"A private enterprise number, as assigned by IANA. 2737 Within the context of an Information Element Type record, this 2738 element can be used along with the informationElementId element to 2739 scope properties to a specific Information Element. To export 2740 type information about an IANA-assigned Information Element, set 2741 the privateEnterpriseNumber to 0, or do not export the 2742 privateEnterpriseNumber in the type record. To export type 2743 information about an enterprise-specific Information Element, 2744 export the enterprise number in privateEnterpriseNumber, and 2745 export the Information Element number with the Enterprise bit 2746 cleared in informationElementId. The Enterprise bit in the 2747 associated informationElementId Information Element MUST be 2748 ignored by the Collecting Process.",,,,[RFC5610],0,2013-02-18 2749 347,virtualStationInterfaceId,octetArray,default,current,"Instance Identifier of the interface to a Virtual Station. A Virtual 2750 Station is an end station instance: it can be a virtual machine or a 2751 physical host.",,,See IEEE 802.1Qbg for the definition of Virtual Station Interface ID.,[ipfix-iana_at_cisco.com],1,2014-02-03 2752 348,virtualStationInterfaceName,string,default,current,"Name of the interface to a Virtual Station. A Virtual Station is an end station 2753 instance: it can be a virtual machine or a physical host.",,,See IEEE 802.1Qbg for the definition of Virtual Station Interface.,[ipfix-iana_at_cisco.com],1,2014-02-03 2754 349,virtualStationUUID,octetArray,default,current,"Unique Identifier of a Virtual Station. A Virtual Station is an end station 2755 instance: it can be a virtual machine or a physical host.",,,See IEEE 802.1Qbg for the definition of Virtual Station.,[ipfix-iana_at_cisco.com],1,2014-02-03 2756 350,virtualStationName,string,default,current,"Name of a Virtual Station. A Virtual Station is an end station 2757 instance: it can be a virtual machine or a physical host.",,,See IEEE 802.1Qbg for the definition of Virtual Station.,[ipfix-iana_at_cisco.com],0,2013-02-18 2758 351,layer2SegmentId,unsigned64,identifier,current,"Identifier of a layer 2 network segment in an overlay network. 2759 The most significant byte identifies the layer 2 network 2760 overlay network encapsulation type: 2761 2762 2763 2764 2765 0x00 reserved 2766 2767 2768 2769 2770 0x01 VxLAN 2771 2772 2773 2774 2775 0x02 NVGRE 2776 2777 2778 2779 2780 The three lowest significant bytes 2781 hold the value of the layer 2 2782 overlay network segment identifier. 2783 2784 2785 2786 2787 For example: 2788 2789 2790 2791 2792 - a 24 bit segment ID VXLAN Network 2793 Identifier (VNI) 2794 2795 2796 2797 2798 - a 24 bit Tenant Network Identifier 2799 (TNI) for NVGRE",,,"See VxLAN RFC at [RFC7348] 2800 2801 2802 2803 2804 See NVGRE RFC at [RFC7637]",[ipfix-iana_at_cisco.com],0,2013-02-18 2805 352,layer2OctetDeltaCount,unsigned64,deltaCounter,current,"The number of layer 2 octets since the previous report (if any) in 2806 incoming packets for this Flow at the Observation Point. The 2807 number of octets includes layer 2 header(s) and layer 2 payload. 2808 # memo: layer 2 version of octetDeltaCount (field #1)",octets,,,[ipfix-iana_at_cisco.com],1,2014-05-02 2809 353,layer2OctetTotalCount,unsigned64,totalCounter,current,"The total number of layer 2 octets in incoming packets for this 2810 Flow at the Observation Point since the Metering Process 2811 (re-)initialization for this Observation Point. The number of 2812 octets includes layer 2 header(s) and layer 2 payload. 2813 # memo: layer 2 version of octetTotalCount (field #85)",octets,,,[ipfix-iana_at_cisco.com],1,2014-05-02 2814 354,ingressUnicastPacketTotalCount,unsigned64,totalCounter,current,"The total number of incoming unicast packets metered at the 2815 Observation Point since the Metering Process (re-)initialization 2816 for this Observation Point.",packets,,,[ipfix-iana_at_cisco.com],0,2013-02-18 2817 355,ingressMulticastPacketTotalCount,unsigned64,totalCounter,current,"The total number of incoming multicast packets metered at the 2818 Observation Point since the Metering Process (re-)initialization 2819 for this Observation Point.",packets,,,[ipfix-iana_at_cisco.com],0,2013-02-18 2820 356,ingressBroadcastPacketTotalCount,unsigned64,totalCounter,current,"The total number of incoming broadcast packets metered at the 2821 Observation Point since the Metering Process (re-)initialization 2822 for this Observation Point.",packets,,,[ipfix-iana_at_cisco.com],0,2013-02-18 2823 357,egressUnicastPacketTotalCount,unsigned64,totalCounter,current,"The total number of incoming unicast packets metered at the 2824 Observation Point since the Metering Process (re-)initialization 2825 for this Observation Point.",packets,,,[ipfix-iana_at_cisco.com],0,2013-02-18 2826 358,egressBroadcastPacketTotalCount,unsigned64,totalCounter,current,"The total number of incoming broadcast packets metered at the 2827 Observation Point since the Metering Process (re-)initialization 2828 for this Observation Point.",packets,,,[ipfix-iana_at_cisco.com],0,2013-02-18 2829 359,monitoringIntervalStartMilliSeconds,dateTimeMilliseconds,default,current,"The absolute timestamp at which the monitoring interval 2830 started. 2831 A Monitoring interval is the period of time during which the Metering 2832 Process is running.",milliseconds,,,[ipfix-iana_at_cisco.com],0,2013-02-18 2833 360,monitoringIntervalEndMilliSeconds,dateTimeMilliseconds,default,current,"The absolute timestamp at which the monitoring interval ended. 2834 A Monitoring interval is the period of time during which the Metering 2835 Process is running.",milliseconds,,,[ipfix-iana_at_cisco.com],0,2013-02-18 2836 361,portRangeStart,unsigned16,identifier,current,"The port number identifying the start of a range of ports. A value 2837 of zero indicates that the range start is not specified, ie the 2838 range is defined in some other way. 2839 2840 2841 2842 2843 Additional information on defined TCP port numbers can be found at 2844 [IANA registry service-names-port-numbers].",,,,[ipfix-iana_at_cisco.com],0,2013-02-18 2845 362,portRangeEnd,unsigned16,identifier,current,"The port number identifying the end of a range of ports. A value 2846 of zero indicates that the range end is not specified, ie the 2847 range is defined in some other way. 2848 2849 2850 2851 2852 Additional information on defined TCP port numbers can be found at 2853 [IANA registry service-names-port-numbers].",,,,[ipfix-iana_at_cisco.com],0,2013-02-18 2854 363,portRangeStepSize,unsigned16,identifier,current,"The step size in a port range. The default step size is 1, 2855 which indicates contiguous ports. A value of zero indicates 2856 that the step size is not specified, ie the range is defined 2857 in some other way.",,,,[ipfix-iana_at_cisco.com],0,2013-02-18 2858 364,portRangeNumPorts,unsigned16,identifier,current,"The number of ports in a port range. A value of zero indicates 2859 that the number of ports is not specified, ie the range is defined 2860 in some other way.",,,,[ipfix-iana_at_cisco.com],0,2013-02-18 2861 365,staMacAddress,macAddress,default,current,The IEEE 802 MAC address of a wireless station (STA).,,,See section 1.4 of [RFC5415] for the definition of STA.,[ipfix-iana_at_cisco.com],1,2014-02-03 2862 366,staIPv4Address,ipv4Address,default,current,The IPv4 address of a wireless station (STA).,,,See section 1.4 of [RFC5415] for the definition of STA.,[ipfix-iana_at_cisco.com],1,2014-02-03 2863 367,wtpMacAddress,macAddress,default,current,The IEEE 802 MAC address of a wireless access point (WTP).,,,See section 1.4 of [RFC5415] for the definition of WTP.,[ipfix-iana_at_cisco.com],1,2014-02-03 2864 368,ingressInterfaceType,unsigned32,identifier,current,"The type of interface where packets of this Flow are being received. 2865 The value matches the value of managed object 'ifType' as defined in 2866 [IANA registry ianaiftype-mib].",,,[IANA registry ianaiftype-mib],[ipfix-iana_at_cisco.com],0,2013-02-18 2867 369,egressInterfaceType,unsigned32,identifier,current,"The type of interface where packets of this Flow are being sent. 2868 The value matches the value of managed object 'ifType' as defined in 2869 [IANA registry ianaiftype-mib].",,,[IANA registry ianaiftype-mib],[ipfix-iana_at_cisco.com],0,2013-02-18 2870 370,rtpSequenceNumber,unsigned16,,current,The RTP sequence number per [RFC3550].,,,[RFC3550],[ipfix-iana_at_cisco.com],0,2013-02-18 2871 371,userName,string,default,current,User name associated with the flow.,,,,[ipfix-iana_at_cisco.com],0,2013-02-18 2872 372,applicationCategoryName,string,default,current,"An attribute that provides a first level categorization for 2873 each Application ID.",,,,[RFC6759],0,2013-02-18 2874 373,applicationSubCategoryName,string,default,current,"An attribute that provides a second level categorization 2875 for each Application ID.",,,,[RFC6759],0,2013-02-18 2876 374,applicationGroupName,string,default,current,"An attribute that groups multiple Application IDs that 2877 belong to the same networking application.",,,,[RFC6759],0,2013-02-18 2878 375,originalFlowsPresent,unsigned64,deltaCounter,current,"The non-conservative count of Original Flows 2879 contributing to this Aggregated Flow. Non-conservative counts 2880 need not sum to the original count on re-aggregation.",flows,,,[RFC7015],1,2013-06-25 2881 376,originalFlowsInitiated,unsigned64,deltaCounter,current,"The conservative count of Original Flows whose first 2882 packet is represented within this Aggregated Flow. Conservative 2883 counts must sum to the original count on re-aggregation.",flows,,,[RFC7015],1,2013-06-25 2884 377,originalFlowsCompleted,unsigned64,deltaCounter,current,"The conservative count of Original Flows whose last 2885 packet is represented within this Aggregated Flow. Conservative 2886 counts must sum to the original count on re-aggregation.",flows,,,[RFC7015],1,2013-06-25 2887 378,distinctCountOfSourceIPAddress,unsigned64,totalCounter,current,"The count of distinct source IP address values for 2888 Original Flows contributing to this Aggregated Flow, without 2889 regard to IP version. This Information Element is preferred to 2890 the IP-version-specific counters, unless it is important to 2891 separate the counts by version.",,,,[RFC7015],0,2013-02-18 2892 379,distinctCountOfDestinationIPAddress,unsigned64,totalCounter,current,"The count of distinct destination IP address values 2893 for Original Flows contributing to this Aggregated Flow, without 2894 regard to IP version. This Information Element is preferred to 2895 the version-specific counters below, unless it is important to 2896 separate the counts by version.",,,,[RFC7015],0,2013-02-18 2897 380,distinctCountOfSourceIPv4Address,unsigned32,totalCounter,current,"The count of distinct source IPv4 address values for 2898 Original Flows contributing to this Aggregated Flow.",,,,[RFC7015],0,2013-02-18 2899 381,distinctCountOfDestinationIPv4Address,unsigned32,totalCounter,current,"The count of distinct destination IPv4 address values 2900 for Original Flows contributing to this Aggregated Flow.",,,,[RFC7015],0,2013-02-18 2901 382,distinctCountOfSourceIPv6Address,unsigned64,totalCounter,current,"The count of distinct source IPv6 address values for 2902 Original Flows contributing to this Aggregated Flow.",,,,[RFC7015],0,2013-02-18 2903 383,distinctCountOfDestinationIPv6Address,unsigned64,totalCounter,current,"The count of distinct destination IPv6 address values 2904 for Original Flows contributing to this Aggregated Flow.",,,,[RFC7015],0,2013-02-18 2905 384,valueDistributionMethod,unsigned8,,current,"A description of the method used to distribute the 2906 counters from Contributing Flows into the Aggregated Flow records 2907 described by an associated scope, generally a Template. The 2908 method is deemed to apply to all the non-key Information Elements 2909 in the referenced scope for which value distribution is a valid 2910 operation; if the originalFlowsInitiated and/or 2911 originalFlowsCompleted Information Elements appear in the 2912 Template, they are not subject to this distribution method, as 2913 they each infer their own distribution method. This is intended 2914 to be a complete set of possible value distribution methods; it is 2915 encoded as follows: 2916 2917 2918 2919 +-------+-----------------------------------------------------------+ 2920 | Value | Description | 2921 +-------+-----------------------------------------------------------+ 2922 | 0 | Unspecified: The counters for an Original Flow are | 2923 | | explicitly not distributed according to any other method | 2924 | | defined for this Information Element; use for arbitrary | 2925 | | distribution, or distribution algorithms not described by | 2926 | | any other codepoint. | 2927 | | --------------------------------------------------------- | 2928 | | | 2929 | 1 | Start Interval: The counters for an Original Flow are | 2930 | | added to the counters of the appropriate Aggregated Flow | 2931 | | containing the start time of the Original Flow. This | 2932 | | should be assumed the default if value distribution | 2933 | | information is not available at a Collecting Process for | 2934 | | an Aggregated Flow. | 2935 | | --------------------------------------------------------- | 2936 | | | 2937 | 2 | End Interval: The counters for an Original Flow are added | 2938 | | to the counters of the appropriate Aggregated Flow | 2939 | | containing the end time of the Original Flow. | 2940 | | --------------------------------------------------------- | 2941 | | | 2942 | 3 | Mid Interval: The counters for an Original Flow are added | 2943 | | to the counters of a single appropriate Aggregated Flow | 2944 | | containing some timestamp between start and end time of | 2945 | | the Original Flow. | 2946 | | --------------------------------------------------------- | 2947 | | | 2948 | 4 | Simple Uniform Distribution: Each counter for an Original | 2949 | | Flow is divided by the number of time intervals the | 2950 | | Original Flow covers (i.e., of appropriate Aggregated | 2951 | | Flows sharing the same Flow Key), and this number is | 2952 | | added to each corresponding counter in each Aggregated | 2953 | | Flow. | 2954 | | --------------------------------------------------------- | 2955 | | | 2956 | 5 | Proportional Uniform Distribution: Each counter for an | 2957 | | Original Flow is divided by the number of time units the | 2958 | | Original Flow covers, to derive a mean count rate. This | 2959 | | mean count rate is then multiplied by the number of time | 2960 | | units in the intersection of the duration of the Original | 2961 | | Flow and the time interval of each Aggregated Flow. This | 2962 | | is like simple uniform distribution, but accounts for the | 2963 | | fractional portions of a time interval covered by an | 2964 | | Original Flow in the first and last time interval. | 2965 | | --------------------------------------------------------- | 2966 | | | 2967 | 6 | Simulated Process: Each counter of the Original Flow is | 2968 | | distributed among the intervals of the Aggregated Flows | 2969 | | according to some function the Intermediate Aggregation | 2970 | | Process uses based upon properties of Flows presumed to | 2971 | | be like the Original Flow. This is essentially an | 2972 | | assertion that the Intermediate Aggregation Process has | 2973 | | no direct packet timing information but is nevertheless | 2974 | | not using one of the other simpler distribution methods. | 2975 | | The Intermediate Aggregation Process specifically makes | 2976 | | no assertion as to the correctness of the simulation. | 2977 | | --------------------------------------------------------- | 2978 | | | 2979 | 7 | Direct: The Intermediate Aggregation Process has access | 2980 | | to the original packet timings from the packets making up | 2981 | | the Original Flow, and uses these to distribute or | 2982 | | recalculate the counters. | 2983 +-------+-----------------------------------------------------------+",,,,[RFC7015],0,2013-02-18 2984 385,rfc3550JitterMilliseconds,unsigned32,quantity,current,"Interarrival jitter as defined in section 6.4.1 of [RFC3550], 2985 measured in milliseconds.",milliseconds,,[RFC3550],[ipfix-iana_at_cisco.com],0,2013-02-18 2986 386,rfc3550JitterMicroseconds,unsigned32,quantity,current,"Interarrival jitter as defined in section 6.4.1 of [RFC3550], 2987 measured in microseconds.",microseconds,,[RFC3550],[ipfix-iana_at_cisco.com],0,2013-02-18 2988 387,rfc3550JitterNanoseconds,unsigned32,quantity,current,"Interarrival jitter as defined in section 6.4.1 of [RFC3550], 2989 measured in nanoseconds.",nanoseconds,,[RFC3550],[ipfix-iana_at_cisco.com],0,2013-02-18 2990 388,dot1qDEI,boolean,default,current,"The value of the 1-bit Drop Eligible Indicator (DEI) field of the VLAN tag as 2991 described in 802.1Q-2011 subclause 9.6. In case of a QinQ frame, it represents 2992 the outer tag's DEI field and in case of an IEEE 802.1ad frame it represents 2993 the DEI field of the S-TAG. Note: in earlier versions of 802.1Q the same bit 2994 field in the incoming packet is occupied by the Canonical Format Indicator 2995 (CFI) field, except for S-TAGs.",,,[802.1Q-2011 subclause 9.6],[Yaakov_J_Stein],1,2014-02-03 2996 389,dot1qCustomerDEI,boolean,default,current,"In case of a QinQ frame, it represents the inner tag's Drop Eligible Indicator 2997 (DEI) field and in case of an IEEE 802.1ad frame it represents the DEI field of 2998 the C-TAG.",,,[802.1Q-2011 subclause 9.6],[Yaakov_J_Stein],1,2014-02-03 2999 390,flowSelectorAlgorithm,unsigned16,identifier,current,"This Information Element identifies the Intermediate Flow 3000 Selection Process technique (e.g., Filtering, Sampling) that is 3001 applied by the Intermediate Flow Selection Process. Most of these 3002 techniques have parameters. Its configuration parameter(s) MUST 3003 be clearly specified. Further Information Elements are needed to 3004 fully specify packet selection with these methods and all their 3005 parameters. Further method identifiers may be added to the 3006 flowSelectorAlgorithm registry. It might be necessary to define new Information Elements 3007 to specify their parameters. The flowSelectorAlgorithm registry 3008 is maintained by IANA. New assignments for the registry will be 3009 administered by IANA, on a First Come First Served basis 3010 [RFC8126], subject to Expert Review [RFC8126]. Please note that 3011 the purpose of the flow selection techniques described in this 3012 document is the improvement of measurement functions as defined in 3013 the Scope (Section 1). Before adding new flow selector algorithms 3014 it should be checked what is their intended purpose and especially 3015 if those contradict with policies defined in [RFC2804]. The 3016 designated expert(s) should consult with the community if a 3017 request is received that runs counter to [RFC2804]. The registry 3018 can be updated when specifications of the new method(s) and any 3019 new Information Elements are provided. The group of experts must 3020 double check the flowSelectorAlgorithm definitions and Information 3021 Elements with already defined flowSelectorAlgorithm and 3022 Information Elements for completeness, accuracy, and redundancy. 3023 Those experts will initially be drawn from the Working Group 3024 Chairs and document editors of the IPFIX and PSAMP Working Groups. 3025 The Intermediate Flow Selection Process Techniques 3026 identifiers are defined at [http://www.iana.org/assignments/ipfix/ipfix.xml#ipfix-flowselectoralgorithm].",,,,[RFC7014],0,2013-06-07 3027 391,flowSelectedOctetDeltaCount,unsigned64,deltaCounter,current,"This Information Element specifies the volume in octets of all 3028 Flows that are selected in the Intermediate Flow Selection Process 3029 since the previous report.",octets,,,[RFC7014],1,2014-08-13 3030 392,flowSelectedPacketDeltaCount,unsigned64,deltaCounter,current,"This Information Element specifies the volume in packets of all 3031 Flows that were selected in the Intermediate Flow Selection 3032 Process since the previous report.",packets,,,[RFC7014],1,2014-08-13 3033 393,flowSelectedFlowDeltaCount,unsigned64,deltaCounter,current,"This Information Element specifies the number of Flows that were 3034 selected in the Intermediate Flow Selection Process since the last 3035 report.",flows,,,[RFC7014],1,2014-08-13 3036 394,selectorIDTotalFlowsObserved,unsigned64,,current,"This Information Element specifies the total number of Flows 3037 observed by a Selector, for a specific value of SelectorId. This 3038 Information Element should be used in an Options Template scoped 3039 to the observation to which it refers. See Section 3.4.2.1 of the 3040 IPFIX protocol document [RFC7011].",flows,,,[RFC7014],0,2013-06-07 3041 395,selectorIDTotalFlowsSelected,unsigned64,,current,"This Information Element specifies the total number of Flows 3042 selected by a Selector, for a specific value of SelectorId. This 3043 Information Element should be used in an Options Template scoped 3044 to the observation to which it refers. See Section 3.4.2.1 of the 3045 IPFIX protocol document [RFC7011].",flows,,,[RFC7014],0,2013-06-07 3046 396,samplingFlowInterval,unsigned64,,current,"This Information Element specifies the number of Flows that are 3047 consecutively sampled. A value of 100 means that 100 consecutive 3048 Flows are sampled. For example, this Information Element may be 3049 used to describe the configuration of a systematic count-based 3050 Sampling Selector.",flows,,,[RFC7014],0,2013-06-07 3051 397,samplingFlowSpacing,unsigned64,,current,"This Information Element specifies the number of Flows between two 3052 ""samplingFlowInterval""s. A value of 100 means that the next 3053 interval starts 100 Flows (which are not sampled) after the 3054 current ""samplingFlowInterval"" is over. For example, this 3055 Information Element may be used to describe the configuration of a 3056 systematic count-based Sampling Selector.",flows,,,[RFC7014],0,2013-06-07 3057 398,flowSamplingTimeInterval,unsigned64,,current,"This Information Element specifies the time interval in 3058 microseconds during which all arriving Flows are sampled. For 3059 example, this Information Element may be used to describe the 3060 configuration of a systematic time-based Sampling Selector.",microseconds,,,[RFC7014],0,2013-06-07 3061 399,flowSamplingTimeSpacing,unsigned64,,current,"This Information Element specifies the time interval in 3062 microseconds between two ""flowSamplingTimeInterval""s. A value of 3063 100 means that the next interval starts 100 microseconds (during 3064 which no Flows are sampled) after the current 3065 ""flowsamplingTimeInterval"" is over. For example, this Information 3066 Element may used to describe the configuration of a systematic 3067 time-based Sampling Selector.",microseconds,,,[RFC7014],0,2013-06-07 3068 400,hashFlowDomain,unsigned16,identifier,current,"This Information Element specifies the Information Elements that 3069 are used by the Hash-based Flow Selector as the Hash Domain.",,,,[RFC7014],0,2013-06-07 3070 401,transportOctetDeltaCount,unsigned64,deltaCounter,current,"The number of octets, excluding IP header(s) and Layer 4 transport 3071 protocol header(s), observed for this Flow at the Observation Point 3072 since the previous report (if any).",octets,,,[Brian_Trammell],0,2013-08-01 3073 402,transportPacketDeltaCount,unsigned64,deltaCounter,current,"The number of packets containing at least one octet beyond the IP header(s) and 3074 Layer 4 transport protocol header(s), observed for this Flow at the Observation 3075 Point since the previous report (if any).",packets,,,[Brian_Trammell],0,2013-08-01 3076 403,originalExporterIPv4Address,ipv4Address,,current,"The IPv4 address used by the Exporting Process on an 3077 Original Exporter, as seen by the Collecting Process on an IPFIX 3078 Mediator. Used to provide information about the Original 3079 Observation Points to a downstream Collector.",,,,[RFC7119],0,2013-12-24 3080 404,originalExporterIPv6Address,ipv6Address,,current,"The IPv6 address used by the Exporting Process on an 3081 Original Exporter, as seen by the Collecting Process on an IPFIX 3082 Mediator. Used to provide information about the Original 3083 Observation Points to a downstream Collector.",,,,[RFC7119],0,2013-12-24 3084 405,originalObservationDomainId,unsigned32,identifier,current,"The Observation Domain ID reported by the Exporting 3085 Process on an Original Exporter, as seen by the Collecting Process 3086 on an IPFIX Mediator. Used to provide information about the 3087 Original Observation Domain to a downstream Collector. When 3088 cascading through multiple Mediators, this identifies the initial 3089 Observation Domain in the cascade.",,,,[RFC7119],0,2013-12-24 3090 406,intermediateProcessId,unsigned32,identifier,current,"Description: An identifier of an Intermediate Process that is 3091 unique per IPFIX Device. Typically, this Information Element is 3092 used for limiting the scope of other Information Elements. Note 3093 that process identifiers may be assigned dynamically; that is, an 3094 Intermediate Process may be restarted with a different ID.",,,,[RFC7119],0,2013-12-24 3095 407,ignoredDataRecordTotalCount,unsigned64,totalCounter,current,"Description: The total number of received Data Records that the 3096 Intermediate Process did not process since the (re-)initialization 3097 of the Intermediate Process; includes only Data Records not 3098 examined or otherwise handled by the Intermediate Process due to 3099 resource constraints, not Data Records that were examined or 3100 otherwise handled by the Intermediate Process but those that 3101 merely do not contribute to any exported Data Record due to the 3102 operations performed by the Intermediate Process.",,,,[RFC7119],0,2013-12-24 3103 408,dataLinkFrameType,unsigned16,flags,current,"This Information Element specifies the type of the selected data 3104 link frame. 3105 3106 3107 3108 3109 The following data link types are defined here: 3110 3111 3112 3113 3114 - 0x01 IEEE802.3 ETHERNET [IEEE802.3] 3115 3116 3117 3118 3119 - 0x02 IEEE802.11 MAC Frame format [IEEE802.11] 3120 3121 3122 3123 3124 Further values may be assigned by IANA. Note that the assigned 3125 values are bits so that multiple observations can be OR'd 3126 together. 3127 3128 3129 3130 3131 The data link layer is defined in [ISO/IEC.7498-1:1994].",,,[IEEE802.3][IEEE802.11][ISO/IEC.7498-1:1994],[RFC7133],0,2014-01-11 3132 409,sectionOffset,unsigned16,quantity,current,"This Information Element specifies the offset of the packet 3133 section (e.g., dataLinkFrameSection, ipHeaderPacketSection, 3134 ipPayloadPacketSection, mplsLabelStackSection, and 3135 mplsPayloadPacketSection). If this Information Element is 3136 omitted, it defaults to zero (i.e., no offset). 3137 3138 3139 3140 3141 If multiple sectionOffset Information Elements are specified 3142 within a single Template, then they apply to the packet section 3143 Information Elements in order: the first sectionOffset applies to 3144 the first packet section, the second to the second, and so on. 3145 Note that the ""closest"" sectionOffset and packet section 3146 Information Elements within a given Template are not necessarily 3147 related. If there are fewer sectionOffset Information Elements 3148 than packet section Information Elements, then subsequent packet 3149 section Information Elements have no offset, i.e., a sectionOffset 3150 of zero applies to those packet section Information Elements. If 3151 there are more sectionOffset Information Elements than the number 3152 of packet section Information Elements, then the additional 3153 sectionOffset Information Elements are meaningless.",,,,[RFC7133],0,2014-01-11 3154 410,sectionExportedOctets,unsigned16,quantity,current,"This Information Element specifies the observed length of the 3155 packet section (e.g., dataLinkFrameSection, ipHeaderPacketSection, 3156 ipPayloadPacketSection, mplsLabelStackSection, and 3157 mplsPayloadPacketSection) when padding is used. 3158 3159 3160 3161 3162 The packet section may be of a fixed size larger than the 3163 sectionExportedOctets. In this case, octets in the packet section 3164 beyond the sectionExportedOctets MUST follow the [RFC7011] rules 3165 for padding (i.e., be composed of zero (0) valued octets).",,,[RFC7011],[RFC7133],0,2014-01-11 3166 411,dot1qServiceInstanceTag,octetArray,default,current,"This Information Element, which is 16 octets long, represents the 3167 Backbone Service Instance Tag (I-TAG) Tag Control Information 3168 (TCI) field of an Ethernet frame as described in [IEEE802.1Q]. It 3169 encodes the Backbone Service Instance Priority Code Point (I-PCP), 3170 Backbone Service Instance Drop Eligible Indicator (I-DEI), Use Customer Addresses (UCAs), 3171 Backbone Service Instance Identifier (I-SID), Encapsulated 3172 Customer Destination Address (C-DA), Encapsulated Customer Source 3173 Address (C-SA), and reserved fields. The structure and semantics 3174 within the Tag Control Information field are defined in 3175 [IEEE802.1Q].",,,[IEEE802.1Q],[RFC7133],1,2014-05-02 3176 412,dot1qServiceInstanceId,unsigned32,identifier,current,"The value of the 24-bit Backbone Service Instance Identifier 3177 (I-SID) portion of the Backbone Service Instance Tag (I-TAG) Tag 3178 Control Information (TCI) field of an Ethernet frame as described 3179 in [IEEE802.1Q].",,0-0xFFFFFF,[IEEE802.1Q],[RFC7133],1,2014-05-02 3180 413,dot1qServiceInstancePriority,unsigned8,identifier,current,"The value of the 3-bit Backbone Service Instance Priority Code 3181 Point (I-PCP) portion of the Backbone Service Instance Tag (I-TAG) 3182 Tag Control Information (TCI) field of an Ethernet frame as 3183 described in [IEEE802.1Q].",,0-7,[IEEE802.1Q],[RFC7133],1,2014-05-02 3184 414,dot1qCustomerSourceMacAddress,macAddress,default,current,"The value of the Encapsulated Customer Source Address (C-SA) 3185 portion of the Backbone Service Instance Tag (I-TAG) Tag Control 3186 Information (TCI) field of an Ethernet frame as described in 3187 [IEEE802.1Q].",,,[IEEE802.1Q],[RFC7133],1,2014-05-02 3188 415,dot1qCustomerDestinationMacAddress,macAddress,default,current,"The value of the Encapsulated Customer Destination Address (C-DA) 3189 portion of the Backbone Service Instance Tag (I-TAG) Tag Control 3190 Information (TCI) field of an Ethernet frame as described in 3191 [IEEE802.1Q].",,,[IEEE802.1Q],[RFC7133],1,2014-05-02 3192 416,,,,deprecated,"Duplicate of Information Element ID 352, layer2OctetDeltaCount.",,,[RFC5477],,2,2014-05-13 3193 417,postLayer2OctetDeltaCount,unsigned64,deltaCounter,current,"The definition of this Information Element is identical to the 3194 definition of the layer2OctetDeltaCount Information Element, 3195 except that it reports a potentially modified value caused by a 3196 middlebox function after the packet passed the Observation Point. 3197 3198 3199 3200 3201 This Information Element is the layer 2 version of 3202 postOctetDeltaCount (ElementId #23).",octets,,[RFC5477],[RFC7133],1,2014-05-02 3203 418,postMCastLayer2OctetDeltaCount,unsigned64,deltaCounter,current,"The number of layer 2 octets since the previous report (if any) in 3204 outgoing multicast packets sent for packets of this Flow by a 3205 multicast daemon within the Observation Domain. This property 3206 cannot necessarily be observed at the Observation Point but may 3207 be retrieved by other means. The number of octets includes layer 3208 2 header(s) and layer 2 payload. 3209 3210 3211 3212 3213 This Information Element is the layer 2 version of 3214 postMCastOctetDeltaCount (ElementId #20).",octets,,[RFC5477],[RFC7133],1,2014-05-02 3215 419,,,,deprecated,"Duplicate of Information Element ID 353, layer2OctetTotalCount.",,,[RFC5477],,2,2014-05-13 3216 420,postLayer2OctetTotalCount,unsigned64,totalCounter,current,"The definition of this Information Element is identical to the 3217 definition of the layer2OctetTotalCount Information Element, 3218 except that it reports a potentially modified value caused by a 3219 middlebox function after the packet passed the Observation Point. 3220 3221 3222 3223 3224 This Information Element is the layer 2 version of 3225 postOctetTotalCount (ElementId #171).",octets,,[RFC5477],[RFC7133],1,2014-05-02 3226 421,postMCastLayer2OctetTotalCount,unsigned64,totalCounter,current,"The total number of layer 2 octets in outgoing multicast packets 3227 sent for packets of this Flow by a multicast daemon in the 3228 Observation Domain since the Metering Process (re-)initialization. 3229 This property cannot necessarily be observed at the Observation 3230 Point but may be retrieved by other means. The number of octets 3231 includes layer 2 header(s) and layer 2 payload. 3232 3233 3234 3235 3236 This Information Element is the layer 2 version of 3237 postMCastOctetTotalCount (ElementId #175).",octets,,[RFC5477],[RFC7133],1,2014-05-02 3238 422,minimumLayer2TotalLength,unsigned64,,current,"Layer 2 length of the smallest packet observed for this Flow. The 3239 packet length includes the length of the layer 2 header(s) and the 3240 length of the layer 2 payload. 3241 3242 3243 3244 3245 This Information Element is the layer 2 version of 3246 minimumIpTotalLength (ElementId #25).",octets,,[RFC5477],[RFC7133],1,2014-05-02 3247 423,maximumLayer2TotalLength,unsigned64,,current,"Layer 2 length of the largest packet observed for this Flow. The 3248 packet length includes the length of the layer 2 header(s) and the length of the layer 3249 2 payload. 3250 3251 3252 3253 3254 This Information Element is the layer 2 version of 3255 maximumIpTotalLength (ElementId #26).",octets,,[RFC5477],[RFC7133],1,2014-05-02 3256 424,droppedLayer2OctetDeltaCount,unsigned64,deltaCounter,current,"The number of layer 2 octets since the previous report (if any) in 3257 packets of this Flow dropped by packet treatment. The number of 3258 octets includes layer 2 header(s) and layer 2 payload. 3259 3260 3261 3262 3263 This Information Element is the layer 2 version of 3264 droppedOctetDeltaCount (ElementId #132).",octets,,[RFC5477],[RFC7133],1,2014-05-02 3265 425,droppedLayer2OctetTotalCount,unsigned64,totalCounter,current,"The total number of octets in observed layer 2 packets (including 3266 the layer 2 header) that were dropped by packet treatment since 3267 the (re-)initialization of the Metering Process. 3268 3269 3270 3271 3272 This Information Element is the layer 2 version of 3273 droppedOctetTotalCount (ElementId #134).",octets,,[RFC5477],[RFC7133],1,2014-05-02 3274 426,ignoredLayer2OctetTotalCount,unsigned64,totalCounter,current,"The total number of octets in observed layer 2 packets (including 3275 the layer 2 header) that the Metering Process did not process 3276 since the (re-)initialization of the Metering Process. 3277 3278 3279 3280 3281 This Information Element is the layer 2 version of 3282 ignoredOctetTotalCount (ElementId #165).",octets,,[RFC5477],[RFC7133],1,2014-05-02 3283 427,notSentLayer2OctetTotalCount,unsigned64,totalCounter,current,"The total number of octets in observed layer 2 packets (including 3284 the layer 2 header) that the Metering Process did not process 3285 since the (re-)initialization of the Metering Process. 3286 3287 3288 3289 3290 This Information Element is the layer 2 version of 3291 notSentOctetTotalCount (ElementId #168).",octets,,[RFC5477],[RFC7133],1,2014-05-02 3292 428,layer2OctetDeltaSumOfSquares,unsigned64,deltaCounter,current,"The sum of the squared numbers of layer 2 octets per incoming 3293 packet since the previous report (if any) for this Flow at the 3294 Observation Point. The number of octets includes layer 2 3295 header(s) and layer 2 payload. 3296 3297 3298 3299 3300 This Information Element is the layer 2 version of 3301 octetDeltaSumOfSquares (ElementId #198).",octets,,[RFC5477],[RFC7133],1,2014-05-02 3302 429,layer2OctetTotalSumOfSquares,unsigned64,totalCounter,current,"The total sum of the squared numbers of layer 2 octets in incoming 3303 packets for this Flow at the Observation Point since the Metering 3304 Process (re-)initialization for this Observation Point. The 3305 number of octets includes layer 2 header(s) and layer 2 payload. 3306 3307 3308 3309 3310 This Information Element is the layer 2 version of 3311 octetTotalSumOfSquares (ElementId #199).",octets,,[RFC5477],[RFC7133],1,2014-05-02 3312 430,layer2FrameDeltaCount,unsigned64,deltaCounter,current,"The number of incoming layer 2 frames since the 3313 previous report (if any) for this Flow at the 3314 Observation Point.",frames,,,[ipfix-iana_at_cisco.com],0,2014-05-02 3315 431,layer2FrameTotalCount,unsigned64,totalCounter,current,"The total number of incoming layer 2 frames 3316 for this Flow at the Observation Point since 3317 the Metering Process (re-)initialization for 3318 this Observation Point.",frames,,,[ipfix-iana_at_cisco.com],0,2014-05-02 3319 432,pseudoWireDestinationIPv4Address,ipv4Address,default,current,The destination IPv4 address of the PSN tunnel carrying the pseudowire.,,,[RFC3985],[ipfix-iana_at_cisco.com],0,2014-05-28 3320 433,ignoredLayer2FrameTotalCount,unsigned64,totalCounter,current,"The total number of observed layer 2 frames that the Metering Process 3321 did not process since the (re-)initialization of the Metering Process. 3322 This Information Element is the layer 2 version of ignoredPacketTotalCount (ElementId #164).",frames,,,[ipfix-iana_at_cisco.com],0,2014-06-27 3323 434,mibObjectValueInteger,signed32,quantity,current,"An IPFIX Information Element that denotes that the 3324 integer value of a MIB object will be exported. The MIB Object 3325 Identifier (""mibObjectIdentifier"") for this field MUST be exported 3326 in a MIB Field Option or via another means. This Information 3327 Element is used for MIB objects with the Base syntax of Integer32 3328 and INTEGER with IPFIX reduced-size encoding used as required. 3329 The value is encoded as per the standard IPFIX Abstract Data Type 3330 of signed32.",,,,[RFC8038],1,2017-04-30 3331 435,mibObjectValueOctetString,octetArray,default,current,"An IPFIX Information Element that denotes that an 3332 Octet String or Opaque value of a MIB object will be exported. 3333 The MIB Object Identifier (""mibObjectIdentifier"") for this field 3334 MUST be exported in a MIB Field Option or via another means. This 3335 Information Element is used for MIB objects with the Base syntax 3336 of OCTET STRING and Opaque. The value is encoded as per the 3337 standard IPFIX Abstract Data Type of octetArray.",,,,[RFC8038],0,2015-12-13 3338 436,mibObjectValueOID,octetArray,default,current,"An IPFIX Information Element that denotes that an 3339 Object Identifier or OID value of a MIB object will be exported. 3340 The MIB Object Identifier (""mibObjectIdentifier"") for this field 3341 MUST be exported in a MIB Field Option or via another means. This 3342 Information Element is used for MIB objects with the Base syntax 3343 of OBJECT IDENTIFIER. Note: In this case, the 3344 ""mibObjectIdentifier"" defines which MIB object is being exported, 3345 and the ""mibObjectValueOID"" field will contain the OID value of 3346 that MIB object. The mibObjectValueOID Information Element is 3347 encoded as ASN.1/BER [X.690] in an octetArray.",,,,[RFC8038],0,2015-12-13 3348 437,mibObjectValueBits,octetArray,flags,current,"An IPFIX Information Element that denotes that a set 3349 of Enumerated flags or bits from a MIB object will be exported. 3350 The MIB Object Identifier (""mibObjectIdentifier"") for this field 3351 MUST be exported in a MIB Field Option or via another means. This 3352 Information Element is used for MIB objects with the Base syntax 3353 of BITS. The flags or bits are encoded as per the standard IPFIX 3354 Abstract Data Type of octetArray, with sufficient length to 3355 accommodate the required number of bits. If the number of bits is 3356 not an integer multiple of octets, then the most significant bits 3357 at the end of the octetArray MUST be set to 0.",,,,[RFC8038],0,2015-12-13 3358 438,mibObjectValueIPAddress,ipv4Address,default,current,"An IPFIX Information Element that denotes that the 3359 IPv4 address value of a MIB object will be exported. The MIB 3360 Object Identifier (""mibObjectIdentifier"") for this field MUST be 3361 exported in a MIB Field Option or via another means. This 3362 Information Element is used for MIB objects with the Base syntax 3363 of IpAddress. The value is encoded as per the standard IPFIX 3364 Abstract Data Type of ipv4Address.",,,,[RFC8038],0,2015-12-13 3365 439,mibObjectValueCounter,unsigned64,snmpCounter,current,"An IPFIX Information Element that denotes that the 3366 counter value of a MIB object will be exported. The MIB Object 3367 Identifier (""mibObjectIdentifier"") for this field MUST be exported 3368 in a MIB Field Option or via another means. This Information 3369 Element is used for MIB objects with the Base syntax of Counter32 3370 or Counter64 with IPFIX reduced-size encoding used as required. 3371 The value is encoded as per the standard IPFIX Abstract Data Type 3372 of unsigned64.",,,,[RFC8038],0,2015-12-13 3373 440,mibObjectValueGauge,unsigned32,snmpGauge,current,"An IPFIX Information Element that denotes that the 3374 Gauge value of a MIB object will be exported. The MIB Object 3375 Identifier (""mibObjectIdentifier"") for this field MUST be exported 3376 in a MIB Field Option or via another means. This Information 3377 Element is used for MIB objects with the Base syntax of Gauge32. 3378 The value is encoded as per the standard IPFIX Abstract Data Type 3379 of unsigned32. This value represents a non-negative integer that 3380 may increase or decrease but that shall never exceed a maximum 3381 value or fall below a minimum value.",,,,[RFC8038],0,2015-12-13 3382 441,mibObjectValueTimeTicks,unsigned32,quantity,current,"An IPFIX Information Element that denotes that the 3383 TimeTicks value of a MIB object will be exported. The MIB Object 3384 Identifier (""mibObjectIdentifier"") for this field MUST be exported 3385 in a MIB Field Option or via another means. This Information 3386 Element is used for MIB objects with the Base syntax of TimeTicks. 3387 The value is encoded as per the standard IPFIX Abstract Data Type 3388 of unsigned32.",,,,[RFC8038],1,2017-04-30 3389 442,mibObjectValueUnsigned,unsigned32,quantity,current,"An IPFIX Information Element that denotes that an 3390 unsigned integer value of a MIB object will be exported. The MIB 3391 Object Identifier (""mibObjectIdentifier"") for this field MUST be 3392 exported in a MIB Field Option or via another means. This 3393 Information Element is used for MIB objects with the Base syntax 3394 of unsigned32 with IPFIX reduced-size encoding used as required. 3395 The value is encoded as per the standard IPFIX Abstract Data Type 3396 of unsigned32.",,,,[RFC8038],1,2017-04-30 3397 443,mibObjectValueTable,subTemplateList,list,current,"An IPFIX Information Element that denotes that a 3398 complete or partial conceptual table will be exported. The MIB 3399 Object Identifier (""mibObjectIdentifier"") for this field MUST be 3400 exported in a MIB Field Option or via another means. This 3401 Information Element is used for MIB objects with a syntax of 3402 SEQUENCE OF. This is encoded as a subTemplateList of mibObjectValue 3403 Information Elements. The Template specified in the 3404 subTemplateList MUST be an Options Template and MUST include all 3405 the objects listed in the INDEX clause as Scope Fields.",,,,[RFC8038],1,2017-04-30 3406 444,mibObjectValueRow,subTemplateList,list,current,"An IPFIX Information Element that denotes that a 3407 single row of a conceptual table will be exported. The MIB Object 3408 Identifier (""mibObjectIdentifier"") for this field MUST be exported 3409 in a MIB Field Option or via another means. This Information 3410 Element is used for MIB objects with a syntax of SEQUENCE. This 3411 is encoded as a subTemplateList of mibObjectValue Information 3412 Elements. The subTemplateList exported MUST contain exactly one 3413 row (i.e., one instance of the subTemplate). The Template 3414 specified in the subTemplateList MUST be an Options Template and 3415 MUST include all the objects listed in the INDEX clause as Scope 3416 Fields.",,,,[RFC8038],0,2015-12-13 3417 445,mibObjectIdentifier,octetArray,default,current,"An IPFIX Information Element that denotes that a MIB 3418 Object Identifier (MIB OID) is exported in the (Options) 3419 Template Record. The mibObjectIdentifier Information Element 3420 contains the OID assigned to the MIB object type definition 3421 encoded as ASN.1/BER [X.690].",,,,[RFC8038],0,2015-12-13 3422 446,mibSubIdentifier,unsigned32,identifier,current,A non-negative sub-identifier of an Object Identifier (OID).,,,,[RFC8038],0,2015-12-13 3423 447,mibIndexIndicator,unsigned64,flags,current,"A set of bit fields that is used for marking the 3424 Information Elements of a Data Record that serve as INDEX MIB 3425 objects for an indexed columnar MIB object. Each bit represents 3426 an Information Element in the Data Record, with the n-th least 3427 significant bit representing the n-th Information Element. A bit 3428 set to 1 indicates that the corresponding Information Element is 3429 an index of the columnar object represented by the mibObjectValue. 3430 A bit set to 0 indicates that this is not the case. 3431 3432 3433 3434 3435 If the Data Record contains more than 64 Information Elements, the 3436 corresponding Template SHOULD be designed such that all index 3437 fields are among the first 64 Information Elements, because the 3438 mibIndexIndicator only contains 64 bits. If the Data Record 3439 contains less than 64 Information Elements, then the extra bits in 3440 the mibIndexIndicator for which no corresponding Information 3441 Element exists MUST have the value 0 and must be disregarded by 3442 the Collector. This Information Element may be exported with 3443 IPFIX reduced-size encoding.",,,,[RFC8038],0,2015-12-13 3444 448,mibCaptureTimeSemantics,unsigned8,identifier,current,"Indicates when in the lifetime of the Flow the MIB 3445 value was retrieved from the MIB for a mibObjectIdentifier. This 3446 is used to indicate if the value exported was collected from the 3447 MIB closer to Flow creation or Flow export time and refers to the 3448 Timestamp fields included in the same Data Record. This field 3449 SHOULD be used when exporting a mibObjectValue that specifies 3450 counters or statistics. 3451 3452 3453 3454 3455 If the MIB value was sampled by SNMP prior to the IPFIX Metering 3456 Process or Exporting Process retrieving the value (i.e., the data 3457 is already stale) and it is important to know the exact sampling 3458 time, then an additional observationTime* element should be paired 3459 with the OID using IPFIX Structured Data [RFC6313]. Similarly, if 3460 different MIB capture times apply to different mibObjectValue elements 3461 within the Data Record, then individual mibCaptureTimeSemantics 3462 Information Elements should be paired with each OID using IPFIX 3463 Structured Data. 3464 3465 3466 3467 3468 Values: 3469 3470 3471 3472 3473 0 undefined 3474 3475 3476 3477 3478 1 begin - The value for the MIB object is captured from the 3479 MIB when the Flow is first observed 3480 3481 3482 3483 3484 2 end - The value for the MIB object is captured from the MIB 3485 when the Flow ends 3486 3487 3488 3489 3490 3 export - The value for the MIB object is captured from the 3491 MIB at export time 3492 3493 3494 3495 3496 4 average - The value for the MIB object is an average of 3497 multiple captures from the MIB over the observed life of the 3498 Flow",,,,[RFC8038],0,2015-12-13 3499 449,mibContextEngineID,octetArray,default,current,"A mibContextEngineID that specifies the SNMP engine 3500 ID for a MIB field being exported over IPFIX. Definition as per 3501 [RFC3411], Section 3.3.",,,,[RFC8038],0,2015-12-13 3502 450,mibContextName,string,default,current,"An Information Element that denotes that a MIB 3503 context name is specified for a MIB field being exported over 3504 IPFIX. Reference [RFC3411], Section 3.3.",,,,[RFC8038],0,2015-12-13 3505 451,mibObjectName,string,default,current,"The name (called a descriptor in [RFC2578] 3506 of an object type definition.",,,,[RFC8038],0,2015-12-13 3507 452,mibObjectDescription,string,default,current,"The value of the DESCRIPTION clause of a MIB object 3508 type definition.",,,,[RFC8038],0,2015-12-13 3509 453,mibObjectSyntax,string,default,current,"The value of the SYNTAX clause of a MIB object type 3510 definition, which may include a textual convention or sub-typing. 3511 See [RFC2578].",,,,[RFC8038],0,2015-12-13 3512 454,mibModuleName,string,default,current,"The textual name of the MIB module that defines a MIB 3513 object.",,,,[RFC8038],0,2015-12-13 3514 455,mobileIMSI,string,default,current,"The International Mobile Subscription Identity (IMSI). The 3515 IMSI is a decimal digit string with up to a maximum of 15 ASCII/UTF-8 3516 encoded digits (0x30 - 0x39).",,,[3GPP TS 23.003] Section 3 and [ITU-T E.164].,[ipfix-iana_at_cisco.com],0,2015-12-15 3517 456,mobileMSISDN,string,default,current,"The Mobile Station International Subscriber Directory Number 3518 (MSISDN). The MSISDN is a decimal digit string with up to a maximum of 15 3519 ASCII/UTF-8 encoded digits (0x30 - 0x39).",,,[3GPP TS 23.003] Section 3 and [ITU-T E.164].,[ipfix-iana_at_cisco.com],0,2015-12-15 3520 457,httpStatusCode,unsigned16,identifier,current,"The HTTP Response Status Code, as defined in 3521 section 6 of [RFC7231], 3522 associated with a flow. Implies that the flow 3523 record represents a flow containing an HTTP 3524 Response.",,0-999,[RFC7231],[Andrew_Feren],0,2016-04-28 3525 458,sourceTransportPortsLimit,unsigned16,quantity,current,"This Information Element contains the maximum 3526 number of IP source transport ports that can be used by an end 3527 user when sending IP packets; each user is associated with one 3528 or more (source) IPv4 or IPv6 addresses. This Information 3529 Element is particularly useful in address-sharing deployments 3530 that adhere to REQ-4 of [RFC6888]. Limiting the number of 3531 ports assigned to each user ensures fairness among users and 3532 mitigates the denial-of-service attack that a user could launch 3533 against other users through the address-sharing device in order 3534 to grab more ports.",ports,1-65535,,[RFC8045][RFC Errata 5009],1,2017-08-01 3535 459,httpRequestMethod,string,,current,"The HTTP request method, as defined in section 4 of 3536 [RFC7231], associated with a 3537 flow. String with up to 8 UTF-8 characters.",,,,[Felix_Erlacher],0,2016-11-15 3538 460,httpRequestHost,string,,current,"The HTTP request host, as defined in section 5.4 of 3539 [RFC7230] or, in the case of 3540 HTTP/2, the content of the :authority pseudo-header 3541 field as defined in section 8.1.2.3 of 3542 [RFC7240]. Encoded in UTF-8.",,,,[Felix_Erlacher],0,2016-11-15 3543 461,httpRequestTarget,string,,current,"The HTTP request target, as defined in section 2 of 3544 [RFC7231] and in section 5.3 of 3545 [RFC7230], associated with a flow. 3546 Or the HTTP/2 "":path"" pseudo-header field as defined in 3547 section 8.1.2.3 of [RFC7240]. 3548 Encoded in UTF-8.",,,,[Felix_Erlacher],0,2016-11-15 3549 462,httpMessageVersion,string,,current,"The version of an HTTP/1.1 message as indicated by the 3550 HTTP-version field, defined in section 2.6 of 3551 [RFC7230], or the version 3552 identification of an HTTP/2 frame as defined in 3553 [RFC7240] section 3.1. The length 3554 of this field is limited to 10 characters, UTF-8 encoded.",,,,[Felix_Erlacher],0,2016-11-15 3555 463,natInstanceID,unsigned32,identifier,current,"This Information Element uniquely identifies an Instance of the NAT 3556 that runs on a NAT middlebox function after the packet passes the 3557 Observation Point. natInstanceID is defined in 3558 [RFC7659].",,,"See [RFC791] for the definition of the IPv4 3559 source address field. See [RFC3022] 3560 for the definition of NAT. See [RFC3234] 3561 for the definition of middleboxes.",[RFC8158],0,2017-03-15 3562 464,internalAddressRealm,octetArray,identifier,current,"This Information Element represents the internal address realm where 3563 the packet is originated from or destined to. By definition, a NAT 3564 mapping can be created from two address realms, one from internal and 3565 one from external. Realms are implementation dependent and can represent 3566 a Virtual Routing and Forwarding (VRF) ID, a VLAN ID, or some unique 3567 identifier. Realms are optional and, when left unspecified, would mean 3568 that the external and internal realms are the same.",,,"See [RFC791] for the definition of the IPv4 3569 source address field. See [RFC3022] 3570 for the definition of NAT. See [RFC3234] 3571 for the definition of middleboxes.",[RFC8158],0,2017-03-15 3572 465,externalAddressRealm,octetArray,identifier,current,"This Information Element represents the external address 3573 realm where the packet is originated from or destined to. The 3574 detailed definition is in the internal address realm as specified 3575 above.",,,"See [RFC791] for the definition of the IPv4 3576 source address field. See [RFC3022] 3577 for the definition of NAT. See [RFC3234] 3578 for the definition of middleboxes.",[RFC8158],0,2017-03-15 3579 466,natQuotaExceededEvent,unsigned32,identifier,current,"This Information Element identifies the type of a NAT Quota Exceeded 3580 event. Values for this Information Element are listed in the ""NAT 3581 Quota Exceeded Event Type"" registry, see 3582 [http://www.iana.org/assignments/ipfix/ipfix.xhtml#ipfix-nat-quota-exceeded-event]. 3583 New assignments of values will be administered by IANA and are subject 3584 to Expert Review [RFC8126]. Experts need to 3585 check definitions of new values for completeness, accuracy, and 3586 redundancy.",,,"See [RFC791] for the definition of the IPv4 3587 source address field. See [RFC3022] 3588 for the definition of NAT. See [RFC3234] 3589 for the definition of middleboxes.",[RFC8158],0,2017-03-15 3590 467,natThresholdEvent,unsigned32,identifier,current,"This Information Element identifies a type of a NAT Threshold event. 3591 Values for this Information Element are listed in the ""NAT Threshold 3592 Event Type"" registry, see 3593 [http://www.iana.org/assignments/ipfix/ipfix.xhtml#ipfix-nat-threshold-event]. 3594 New assignments of values will be administered by IANA and are 3595 subject to Expert Review [RFC8126]. Experts 3596 need to check definitions of new values for completeness, accuracy, 3597 and redundancy.",,,"See [RFC791] for the definition of the IPv4 3598 source address field. See [RFC3022] 3599 for the definition of NAT. See [RFC3234] 3600 for the definition of middleboxes.",[RFC8158],0,2017-03-15 3601 468,httpUserAgent,string,default,current,"The HTTP User-Agent header field as defined in section 5.5.3 of 3602 [RFC7231]. Encoded in UTF-8.",,,[RFC7231],[Andrew_Feren],0,2017-04-19 3603 469,httpContentType,string,default,current,"The HTTP Content-Type header field as defined in section 3.1.1.5 of 3604 [RFC7231]. Encoded in UTF-8.",,,[RFC7231],[Andrew_Feren],0,2017-04-19 3605 470,httpReasonPhrase,string,default,current,"The HTTP reason phrase as defined in section 6.1 of of 3606 [RFC7231].",,,[RFC7231],[Felix_Erlacher],0,2017-06-19 3607 471,maxSessionEntries,unsigned32,identifier,current,"This element represents the maximum session entries that 3608 can be created by the NAT device.",,,"See [RFC3022] for the definition of NAT. 3609 See [RFC3234] for the definition of middleboxes.",[RFC8158],0,2017-12-01 3610 472,maxBIBEntries,unsigned32,identifier,current,"This element represents the maximum BIB entries that can 3611 be created by the NAT device.",,,"See [RFC3022] for the definition of NAT. 3612 See [RFC3234] for the definition of middleboxes.",[RFC8158],0,2017-12-01 3613 473,maxEntriesPerUser,unsigned32,identifier,current,"This element represents the maximum NAT entries that can 3614 be created per user by the NAT device.",,,"See [RFC3022] for the definition of NAT. 3615 See [RFC3234] for the definition of middleboxes.",[RFC8158],0,2017-12-01 3616 474,maxSubscribers,unsigned32,identifier,current,"This element represents the maximum subscribers or 3617 maximum hosts that are allowed by the NAT device.",,,"See [RFC3022] for the definition of NAT. 3618 See [RFC3234] for the definition of middleboxes.",[RFC8158],0,2017-12-01 3619 475,maxFragmentsPendingReassembly,unsigned32,identifier,current,"This element represents the maximum fragments that the 3620 NAT device can store for reassembling the packet.",,,"See [RFC3022] for the definition of NAT. 3621 See [RFC3234] for the definition of middleboxes.",[RFC8158],0,2017-12-01 3622 476,addressPoolHighThreshold,unsigned32,identifier,current,"This element represents the high threshold value of the 3623 number of public IP addresses in the address pool.",,,"See [RFC3022] for the definition of NAT. 3624 See [RFC3234] for the definition of middleboxes.",[RFC8158],0,2017-12-01 3625 477,addressPoolLowThreshold,unsigned32,identifier,current,"This element represents the low threshold value of the 3626 number of public IP addresses in the address pool.",,,"See [RFC3022] for the definition of NAT. 3627 See [RFC3234] for the definition of middleboxes.",[RFC8158],0,2017-12-01 3628 478,addressPortMappingHighThreshold,unsigned32,identifier,current,"This element represents the high threshold value of the 3629 number of address and port mappings.",,,"See [RFC3022] for the definition of NAT. 3630 See [RFC3234] for the definition of middleboxes.",[RFC8158],0,2017-12-01 3631 479,addressPortMappingLowThreshold,unsigned32,identifier,current,"This element represents the low threshold value of the 3632 number of address and port mappings.",,,"See [RFC3022] for the definition of NAT. 3633 See [RFC3234] for the definition of middleboxes.",[RFC8158],0,2017-12-01 3634 480,addressPortMappingPerUserHighThreshold,unsigned32,identifier,current,"This element represents the high threshold value of the 3635 number of address and port mappings that a single user is allowed to 3636 create on a NAT device.",,,"See [RFC3022] for the definition of NAT. 3637 See [RFC3234] for the definition of middleboxes.",[RFC8158],0,2017-12-01 3638 481,globalAddressMappingHighThreshold,unsigned32,identifier,current,"This element represents the high threshold value of the 3639 number of address and port mappings that a single user is allowed to 3640 create on a NAT device in a paired address pooling behavior.",,,"See [RFC3022] for the definition of NAT. 3641 See [RFC3234] for the definition of middleboxes. 3642 See [RFC4787] for the definition of paired 3643 address pooling behavior.",[RFC8158],0,2017-12-01 3644 482,vpnIdentifier,octetArray,default,current,"VPN ID in the format specified by [RFC2685]. 3645 The size of this Information Element is 7 octets.",,,[RFC2685],[ipfix-iana_at_cisco.com],0,2018-07-10 3646 483-32767,Unassigned,,,,,,,,,,