wdiff rfc7133iana-reg.txt rfc7133iana-text.txt

243
The value of the 12-bit VLAN Identifier portion of the Tag
Control
Information field of an Ethernet frame. The structure and
semantics within the Tag Control Information field are defined
in
[IEEE802.1Q]. In Provider Bridged Networks, it represents the
Service VLAN identifier in the Service VLAN Tag (S-TAG) Tag
Control Information (TCI) field or the Customer VLAN identifier
in
the Customer VLAN Tag (C-TAG) Tag Control Information (TCI)
field
as described in [IEEE802.1Q]. In Provider Backbone Bridged
Networks, it represents the Backbone VLAN identifier in the
Backbone VLAN Tag (B-TAG) Tag Control Information (TCI) field as
described in [IEEE802.1Q]. In a virtual link between a host
system and EVB bridge, it represents the Service VLAN identifier
indicating S-channel as described in [IEEE802.1Qbg].

In the case of a multi-tagged frame, it represents the outer
tag's
VLAN identifier, except for I-TAG.

In the case of multi-tagged frame, it represents the outer tag's VLAN
identifier except for I-TAG.

244
The value of the 3-bit User Priority portion of the Tag Control
Information field of an Ethernet frame. The structure and
semantics within the Tag Control Information field are defined
in
[IEEE802.1Q]. In the case of a multi-tagged frame, it
represents
the 3-bit Priority Code Point (PCP) portion of the outer tag's
Tag
Control Information (TCI) field as described in [IEEE802.1Q],
except for I-TAG.

245
The value represents the Customer VLAN identifier in the
Customer
VLAN Tag (C-TAG) Tag Control Information (TCI) field as
described
in [IEEE802.1Q].

246
The value represents the 3-bit Priority Code Point (PCP) portion
of the Customer VLAN Tag (C-TAG) Tag Control Information (TCI)
field as described in [IEEE802.1Q].

312
This Information Element specifies the length of the selected
data
link frame.

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

313
This Information Element carries a series of n octets from the
IP
header of a sampled packet, starting sectionOffset octets into
the
IP header.

However, if no sectionOffset field corresponding to this
Information Element is present, then a sectionOffset of zero
applies, and the octets MUST be from the start of the IP header.

With sufficient length, this element also reports octets from
the
IP payload. However, full packet capture of arbitrary packet
streams is explicitly out of scope per the Security
Considerations
sections of [RFC5477] and [RFC2804].

The sectionExportedOctets expresses how much data was exported,
while the remainder is padding.

When the sectionExportedOctets field corresponding to this
Information Element exists, this Information Element MAY have a
fixed length and MAY be padded, or it MAY have a variable
length.

When the sectionExportedOctets field corresponding to this
Information Element does not exist, this Information Element
SHOULD have a variable length and MUST NOT be padded. In this
case, the size of the exported section may be constrained due to
limitations in the IPFIX protocol.

314
This Information Element carries a series of n octets from the
IP
payload of a sampled packet, starting sectionOffset octets into
the IP payload.

However, if no sectionOffset field corresponding to this
Information Element is present, then a sectionOffset of zero
applies, and the octets MUST be from the start of the IP
payload.

The IPv4 payload is that part of the packet that follows the
IPv4
header and any options, which [RFC791] refers to as "data" or
"data octets". For example, see the examples in [RFC791],
Appendix A.

The IPv6 payload is the rest of the packet following the
40-octet
IPv6 header. Note that any extension headers present are
considered part of the payload. See [RFC2460] for the IPv6
specification.

The sectionExportedOctets expresses how much data was observed,
while the remainder is padding.

When the sectionExportedOctets field corresponding to this
Information Element exists, this Information Element MAY have a
fixed length and MAY be padded, or it MAY have a variable
length.

315
This Information Element carries n octets from the data link
frame
of a selected frame, starting sectionOffset octets into the
frame.

However, if no sectionOffset field corresponding to this
Information Element is present, then a sectionOffset of zero
applies, and the octets MUST be from the start of the data link
frame.

The sectionObservedOctets sectionExportedOctets expresses how much data was observed,
while the remainder is padding.

When the sectionObservedOctets sectionExportedOctets field corresponding to this
Information Element exists, this Information Element MAY have a
fixed length and MAY be padded, or it MAY have a variable
length.

When the sectionObservedOctets sectionExportedOctets field corresponding to this
Information Element does not exist, this Information Element
SHOULD have a variable length and MUST NOT be padded. In this
case, the size of the exported section may be constrained due to
limitations in the IPFIX protocol.

Further Information Elements, i.e., dataLinkFrameType and dataLinkFrameSize
dataLinkFrameSize, are needed to specify the data link type and
the size of the data link frame of this Information Element. A
set of these Information Elements MAY be contained in a
structured
data type, as expressed in [RFC6313]. Or a set of these
Information Elements MAY be contained in one Flow Record as
shown
in Appendix B of [RFC-ietf-ipfix-data-link-layer-monitoring-08].

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

316
This Information Element carries a series of n octets from the
MPLS label stack of a sampled packet, starting sectionOffset
octets into the MPLS label stack.

However, if no sectionOffset field corresponding to this
Information Element is present, then a sectionOffset of zero
applies, and the octets MUST be from the head of the MPLS label
stack.

With sufficient length, this element also reports octets from
the
MPLS payload. However, full packet capture of arbitrary packet
streams is explicitly out of scope per the Security
Considerations
sections of [RFC5477] and [RFC2804].

See [RFC3031] for the specification of MPLS packets.

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

The sectionExportedOctets expresses how much data was observed,
while the remainder is padding.

When the sectionExportedOctets field corresponding to this
Information Element exists, this Information Element MAY have a
fixed length and MAY be padded, or it MAY have a variable
length.

317
The mplsPayloadPacketSection carries a series of n octets from
the
MPLS payload of a sampled packet, starting sectionOffset octets
into the MPLS payload, as it is data that follows immediately
after the MPLS label stack.

However, if no sectionOffset field corresponding to this
Information Element is present, then a sectionOffset of zero
applies, and the octets MUST be from the start of the MPLS
payload.

See [RFC3031] for the specification of MPLS packets.

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

The sectionExportedOctets expresses how much data was observed,
while the remainder is padding.

When the sectionExportedOctets field corresponding to this
Information Element exists, this Information Element MAY have a
fixed length and MAY be padded, or it MAY have a variable
length.

408
This Information Element specifies the type of the selected data
link frame.

The following data link types are defined here:

- 0x01 IEEE802.3 ETHERNET [IEEE802.3]

- 0x02 IEEE802.11 MAC Frame format [IEEE802.11]

Further values may be assigned by IANA. Note that the assigned
values are bits so that multiple observations can be OR'd
together.

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

409
This Information Element specifies the offset of the packet
section (e.g., dataLinkFrameSection, ipHeaderPacketSection,
ipPayloadPacketSection, mplsLabelStackSection, and
mplsPayloadPacketSection). If this Information Element is
omitted, it defaults to zero (ie, (i.e., no offset).

If multiple sectionOffset Information Elements are specified
within a single Template, then they apply to the packet section
Information Elements in order: the first sectionOffset applies
to
the first packet section, the second to the second, and so on.
Note that the "closest" sectionOffset and packet section
Information Elements within a given Template are not necessarily
related. If there are fewer sectionOffset Information Elements
than packet section Information Elements, then subsequent packet
section Information Elements have no offset, i.e., a
sectionOffset
of zero applies to those packet section Information Elements.
If
there are more sectionOffset Information Elements than the
number
of packet section Information Elements, then the additional
sectionOffset Information Elements are meaningless.

410
This Information Element specifies the observed length of the
packet section (e.g., dataLinkFrameSection,
ipHeaderPacketSection,
ipPayloadPacketSection, mplsLabelStackSection, and
mplsPayloadPacketSection) when padding is used.

The packet section may be of a fixed size larger than the
sectionExportedOctets. In this case, octets in the packet
section
beyond the sectionExportedOctets MUST follow the [RFC7011] rules
for padding (i.e., be composed of zero (0) valued octets).

411
This Information Element, which is 16 octets long, represents
the
Backbone Service Instance Tag (I-TAG) Tag Control Information
(TCI) field of an Ethernet frame as described in [IEEE802.1Q].
It
encodes the Backbone Service Instance Priority Code Point
(I-PCP),
Backbone Service Instance Drop Eligible Indicator (I-DEI), Use
Customer Addresses (UCAs), Backbone Service Instance Identifier
(I-SID), Encapsulated Customer Destination Address (C-DA),
Encapsulated Customer Source Address (C-SA) (C-SA), and reserved
fields.
The structure and semantics within the Tag Control Information
field are defined in [IEEE802.1Q].

412
The value of the 24-bit Backbone Service Instance Identifier
(I-SID) portion of the Backbone Service Instance Tag (I-TAG) Tag
Control Information (TCI) field of an Ethernet frame as
described
in [IEEE802.1Q].

413
The value of the 3-bit Backbone Service Instance Priority Code
Point (I-PCP) portion of the Backbone Service Instance Tag
(I-TAG)
Tag Control Information (TCI) field of an Ethernet frame as
described in [IEEE802.1Q].

414
The value of the Encapsulated Customer Source Address (C-SA)
portion of the Backbone Service Instance Tag (I-TAG) Tag Control
Information (TCI) field of an Ethernet frame as described in
[IEEE802.1Q].

415
The value of the Encapsulated Customer Destination Address
(C-DA)
portion of the Backbone Service Instance Tag (I-TAG) Tag Control
Information (TCI) field of an Ethernet frame as described in
[IEEE802.1Q].

417
The definition of this Information Element is identical to the
definition of the l2OctetDeltaCount layer2OctetDeltaCount Information Element,
except that it reports a potentially modified value caused by a
middlebox function after the packet passed the Observation
Point.

This Information Element is the layer 2 version of
postOctetDeltaCount (ElementId #23).

418
The number of layer 2 octets since the previous report (if any)
in
outgoing multicast packets sent for packets of this Flow by a
multicast daemon within the Observation Domain. This property
cannot necessarily be observed at the Observation Point but may
be
retrieved by other means. The number of octets includes layer 2
header(s) and layer 2 payload.

This Information Element is the layer 2 version of
postMCastOctetDeltaCount (ElementId #20).

420
The definition of this Information Element is identical to the
definition of the l2OctetTotalCount layer2OctetTotalCount Information Element,
except that it reports a potentially modified value caused by a
middlebox function after the packet passed the Observation Point
Point.

This Information Element is the layer 2 version of
postOctetTotalCount (ElementId #171).

421
The total number of layer 2 octets in outgoing multicast packets
sent for packets of this Flow by a multicast daemon in the
Observation Domain since the Metering Process
(re-)initialization.
This property cannot necessarily be observed at the Observation
Point but may be retrieved by other means. The number of octets
includes layer 2 header(s) and layer 2 payload.

This Information Element is the layer 2 version of
postMCastOctetTotalCount (ElementId #175).

422
Layer 2 length of the smallest packet observed for this Flow.
The
packet length includes the length of the layer 2 header(s) and
the
length of the layer 2 payload.

This Information Element is the layer 2 version of
minimumIpTotalLength (ElementId #25).

423

Layer 2 length of the largest packet observed for this Flow.
The
packet length includes the length of the layer 2 header(s) and
the
length of the layer 2 payload.

This Information Element is the layer 2 version of
maximumIpTotalLength (ElementId #26).

424
The number of layer 2 octets since the previous report (if any)
in
packets of this Flow dropped by packet treatment. The number of
octets includes layer 2 header(s) and layer 2 payload.

This Information Element is the layer 2 version of
droppedOctetDeltaCount (ElementId #132).

425
The total number of octets in observed layer 2 packets
(including
the layer 2 header) that were dropped by packet treatment since
the (re-)initialization of the Metering Process.

This Information Element is the layer 2 version of
droppedOctetTotalCount (ElementId #134).

426
The total number of octets in observed layer 2 packets
(including
the layer 2 header) that the Metering Process did not process
since the (re-)initialization of the Metering Process.

This Information Element is the layer 2 version of
ignoredOctetTotalCount (ElementId #165).

427
The total number of octets in observed layer 2 packets
(including
the layer 2 header) that the Metering Process did not process
since the (re-)initialization of the Metering Process.

This Information Element is the layer 2 version of
notSentOctetTotalCount (ElementId #168).

428
The sum of the squared numbers of layer 2 octets per incoming
packet since the previous report (if any) for this Flow at the
Observation Point. The number of octets includes layer 2
header(s) and layer 2 payload.

This Information Element is the layer 2 version of
octetDeltaSumOfSquares (ElementId #198).

429
The total sum of the squared numbers of layer 2 octets in
incoming
packets for this Flow at the Observation Point since the
Metering
Process (re-)initialization for this Observation Point. The
number of octets includes layer 2 header(s) and layer 2 payload.

This Information Element is the layer 2 version of
octetTotalSumOfSquares (ElementId #199).