One document matched: draft-yourtchenko-cisco-ies-08.xml
<?xml version="1.0" encoding="US-ASCII"?>
<!DOCTYPE rfc SYSTEM "rfc2629.dtd">
<?xml-stylesheet type="text/xsl" href="rfc2629.xml" ?>
<?rfc toc="yes" ?>
<?rfc rfcprocack="yes" ?>
<?rfc symrefs="yes" ?>
<?rfc iprnotified="no" ?>
<?rfc strict="yes" ?>
<?rfc compact="yes" ?>
<?rfc subcompact="yes" ?>
<?rfc sortrefs="yes" ?>
<?rfc colonspace='yes' ?>
<?rfc tocindent='yes' ?>
<rfc category="info" docName="draft-yourtchenko-cisco-ies-08"
ipr="trust200902">
<front>
<title abbrev="Cisco Information Elements">Cisco Specific Information Elements reused in IPFIX</title>
<author fullname="Andrew Yourtchenko" initials="A." surname="Yourtchenko">
<organization abbrev="Cisco Systems, Inc.">Cisco Systems, Inc.</organization>
<address>
<postal>
<street>De Kleetlaan, 7</street>
<city>Brussels</city>
<region>Diegem</region>
<code>B-1831</code>
<country>Belgium</country>
</postal>
<phone>+32 2 704 5494</phone>
<email>ayourtch@cisco.com</email>
</address>
</author>
<author fullname="Paul Aitken" initials="P." surname="Aitken">
<organization abbrev="Cisco Systems, Inc.">Cisco Systems, Inc.</organization>
<address>
<postal>
<street>96 Commercial Quay</street>
<city>Edinburgh</city>
<code>EH6 6LX</code>
<country>Scotland</country>
</postal>
<phone>+44 131 561 3616</phone>
<email>paitken@cisco.com</email>
</address>
</author>
<author fullname="Benoit Claise" initials="B." surname="Claise">
<organization abbrev="Cisco Systems, Inc.">Cisco Systems, Inc.</organization>
<address>
<postal>
<street>De Kleetlaan, 6a b1</street>
<region>Diegem</region>
<code>B-1831</code>
<country>Belgium</country>
</postal>
<phone>+32 2 704 5622</phone>
<email>bclaise@cisco.com</email>
</address>
</author>
<date year="2013" />
<area>Applications</area>
<keyword>IPFIX</keyword>
<abstract>
<t>This document describes some additional Information Elements of Cisco Systems, Inc. that are not listed in RFC3954.</t>
</abstract>
</front>
<middle>
<section title="Introduction">
<t>The section 4 of <xref target="RFC7012"></xref> defines the IPFIX Information Elements in the range of 1-127 to be compatible with the NetFlow version 9 fields, as specified in the <xref target="RFC3954">"Cisco Systems NetFlow Services Export Version 9"</xref>. As <xref target="RFC3954"></xref> was specified in 2004, it does not contain all NetFlow version 9 specific fields in the range 1-127. The question was asked whether IPFIX Devices should exclusively report the <xref target="IPFIX-IANA">IPFIX IANA IEs</xref> ? In other words, when upgrading from a NetFlow metering process to an IPFIX Metering Process, should the IPFIX Devices stop reporting NetFlow version 9 specific IEs that were not registered in <xref target="IPFIX-IANA">IANA</xref> ?</t>
<t>This document is intended to fill the gap in this IE range. That way, IPFIX implementations could export all the IEs specified in IANA, regardless of the range.</t>
</section>
<section title="Terminology">
<t>IPFIX-specific terminology used in this document is defined in Section 2 of <xref target="RFC7011"></xref>. As in <xref target="RFC7011"></xref>, these IPFIX-specific terms have the first letter of a word capitalized when used in this document.</t>
</section>
<section title="Information Elements Overview">
<t>The following Information Elements are discussed in the sections below:</t>
<texttable anchor="ies_overview">
<ttcol align="right">ID</ttcol>
<ttcol align="left">Name</ttcol>
<ttcol align="right">ID</ttcol>
<ttcol align="left">Name</ttcol>
<c></c><c></c><c>84</c><c>samplerName</c>
<c>34</c><c>samplingInterval</c><c>87</c><c>flagsAndSamplerId</c>
<c>35</c><c>samplingAlgorithm</c><c>89</c><c>forwardingStatus</c>
<c>38</c><c>engineType</c><c>92</c><c>srcTrafficIndex</c>
<c>39</c><c>engineId</c><c>93</c><c>dstTrafficIndex</c>
<c>43</c><c>ipv4RouterSc</c><c>100</c><c>className</c>
<c>48</c><c>samplerId</c><c>102</c><c>layer2packetSectionOffset</c>
<c>49</c><c>samplerMode</c><c>103</c><c>layer2packetSectionSize</c>
<c>50</c><c>samplerRandomInterval</c><c>104</c><c>layer2packetSectionData</c>
<c>51</c><c>classId</c><c></c><c></c>
</texttable>
</section>
<section title="Information Elements">
<section title='samplingInterval'>
<t>
<list style="hanging">
<t hangText="Description:"><vspace blankLines="0" />Deprecated in favor of 305 samplingPacketInterval. When using sampled NetFlow, the rate at which packets are sampled - e.g. a value of 100 indicates that one of every 100 packets is sampled. </t>
<t hangText="Abstract Data Type:">unsigned32</t>
<t hangText="ElementId:">34</t>
<t hangText="Semantics:">quantity</t>
<t hangText="Status:">deprecated</t>
<t hangText="Units:">packets</t>
</list>
</t>
</section>
<section title='samplingAlgorithm'>
<t>
<list style="hanging">
<t hangText="Description:"><vspace blankLines="0" />Deprecated in favor of 304 selectorAlgorithm. The type of algorithm used for sampled NetFlow: <vspace blankLines="0" /><list style="empty"><t>1 - Deterministic Sampling; </t><t>2 - Random Sampling.</t></list> The values are not compatible with the selectorAlgorithm IE, where "Deterministic" has been replaced by "Systematic count-based" (1) or "Systematic time-based" (2), and "Random" is (3). Conversion is required, see <xref target='PSAMP-IANA'>PSAMP parameters</xref>.</t>
<t hangText="Abstract Data Type:">unsigned8</t>
<t hangText="ElementId:">35</t>
<t hangText="Semantics:">identifier</t>
<t hangText="Status:">deprecated</t>
</list>
</t>
</section>
<section title='engineType'>
<t>
<list style="hanging">
<t hangText="Description:"><vspace blankLines="0" />Type of flow switching engine in a router/switch: <list style="empty"><t>RP = 0, </t><t>VIP/Line card = 1, </t><t>PFC/DFC = 2. </t></list>Reserved for internal use on the collector.</t>
<t hangText="Abstract Data Type:">unsigned8</t>
<t hangText="ElementId:">38</t>
<t hangText="Semantics:">identifier</t>
<t hangText="Status:">deprecated</t>
</list>
</t>
</section>
<section title='engineId'>
<t>
<list style="hanging">
<t hangText="Description:"><vspace blankLines="0" />VIP or line card slot number of the flow switching engine in a router/switch. Reserved for internal use on the collector.</t>
<t hangText="Abstract Data Type:">unsigned8</t>
<t hangText="ElementId:">39</t>
<t hangText="Semantics:">identifier</t>
<t hangText="Status:">deprecated</t>
</list>
</t>
</section>
<section title='ipv4RouterSc'>
<t>
<list style="hanging">
<t hangText="Description:"><vspace blankLines="0" />This is a platform-specific field for Catalyst 5000/Catalyst 6000 family. It is used to store the address of a router that is being shortcut when performing MultiLayer Switching. </t>
<t hangText="Abstract Data Type:">ipv4Address</t>
<t hangText="ElementId:">43</t>
<t hangText="Semantics:">identifier</t>
<t hangText="Status:">deprecated</t>
<t hangText="Reference:"><xref target="CCO-MLS"></xref> describes the MultiLayer Switching.</t>
</list>
</t>
</section>
<section title='samplerId'>
<t>
<list style="hanging">
<t hangText="Description:"><vspace blankLines="0" />Deprecated in favor of 302 selectorId. The unique identifier associated with samplerName.</t>
<t hangText="Abstract Data Type:">unsigned8</t>
<t hangText="ElementId:">48</t>
<t hangText="Semantics:">identifier</t>
<t hangText="Status:">deprecated</t>
</list>
</t>
</section>
<section title='samplerMode'>
<t>
<list style="hanging">
<t hangText="Description:"><vspace blankLines="0" />Deprecated in favor of 304 selectorAlgorithm. The values are not compatible: selectorAlgorithm=3 is random sampling. The type of algorithm used for sampling data: 1 - deterministic, 2 - random sampling. Use with samplerRandomInterval.</t>
<t hangText="Abstract Data Type:">unsigned8</t>
<t hangText="ElementId:">49</t>
<t hangText="Semantics:">identifier</t>
<t hangText="Status:">deprecated</t>
</list>
</t>
</section>
<section title='samplerRandomInterval'>
<t>
<list style="hanging">
<t hangText="Description:"><vspace blankLines="0" />Deprecated in favour of 305 samplingPacketInterval. Packet interval at which to sample - in case of random sampling. Used in connection with samplerMode 0x02 (random sampling) value.</t>
<t hangText="Abstract Data Type:">unsigned32</t>
<t hangText="ElementId:">50</t>
<t hangText="Semantics:">quantity</t>
<t hangText="Status:">deprecated</t>
</list>
</t>
</section>
<section title='classId'>
<t>
<list style="hanging">
<t hangText="Description:"><vspace blankLines="0" />Deprecated in favour of 302 selectorId. Characterizes the traffic class, i.e. QoS treatment.</t>
<t hangText="Abstract Data Type:">unsigned8</t>
<t hangText="ElementId:">51</t>
<t hangText="Semantics:">identifier</t>
<t hangText="Status:">deprecated</t>
</list>
</t>
</section>
<section title='samplerName'>
<t>
<list style="hanging">
<t hangText="Description:"><vspace blankLines="0" />Deprecated in favor of 335 selectorName. Name of the flow sampler.</t>
<t hangText="Abstract Data Type:">string</t>
<t hangText="ElementId:">84</t>
<t hangText="Status:">deprecated</t>
</list>
</t>
</section>
<section title='flagsAndSamplerId'>
<t>
<list style="hanging">
<t hangText="Description:"><vspace blankLines="0" />Flow flags and the value of the sampler ID (samplerId) combined in one bitmapped field. Reserved for internal use on the collector.</t>
<t hangText="Abstract Data Type:">unsigned32</t>
<t hangText="ElementId:">87</t>
<t hangText="Semantics:">identifier</t>
<t hangText="Status:">deprecated</t>
</list>
</t>
</section>
<section title='forwardingStatus'>
<t>
<list style="hanging">
<t hangText="Description:"><vspace blankLines="0" />This Information Element describes the forwarding status of the flow and any attached reasons. The Reduced Size Encoding rules as per <xref target='RFC7011'></xref> apply.
<figure>
<artwork>
The basic encoding is 8 bits. The future extensions
could add one or three bytes. The layout of the basic
encoding is as follows:
MSB - 0 1 2 3 4 5 6 7 - LSB
+---+---+---+---+---+---+---+---+
| Status| Reason code or flags |
+---+---+---+---+---+---+---+---+
Status:
00b = Unknown
01b = Forwarded
10b = Dropped
11b = Consumed
Reason Code (status = 01b, Forwarded)
01 000000b = 64 = Unknown
01 000001b = 65 = Fragmented
01 000010b = 66 = Not Fragmented
Reason Code (status = 10b, Dropped)
10 000000b = 128 = Unknown
10 000001b = 129 = ACL deny
10 000010b = 130 = ACL drop
10 000011b = 131 = Unroutable
10 000100b = 132 = Adjacency
10 000101b = 133 = Fragmentation and DF set
10 000110b = 134 = Bad header checksum
10 000111b = 135 = Bad total Length
10 001000b = 136 = Bad header length
10 001001b = 137 = bad TTL
10 001010b = 138 = Policer
10 001011b = 139 = WRED
10 001100b = 140 = RPF
10 001101b = 141 = For us
10 001110b = 142 = Bad output interface
10 001111b = 143 = Hardware
Reason Code (status = 11b, Consumed)
11 000000b = 192 = Unknown
11 000001b = 193 = Punt Adjacency
11 000010b = 194 = Incomplete Adjacency
11 000011b = 195 = For us
Examples:
value : 0x40 = 64
binary: 01000000
decode: 01 -> Forward
000000 -> No further information
value : 0x89 = 137
binary: 10001001
decode: 10 -> Drop
001001 -> Fragmentation and DF set
</artwork>
</figure>
</t>
<t hangText="Abstract Data Type:">unsigned32</t>
<t hangText="ElementId:">89</t>
<t hangText="Semantics:">identifier</t>
<t hangText="Status:">current</t>
<t hangText="Reference:"><vspace blankLines="0" />See <xref target='CCO-NF9FMT'></xref> - NetFlow Version 9 Record Format.</t>
</list>
</t>
</section>
<section title='srcTrafficIndex'>
<t>
<list style="hanging">
<t hangText="Description:"><vspace blankLines="0" />BGP Policy Accounting Source Traffic Index</t>
<t hangText="Abstract Data Type:">unsigned32</t>
<t hangText="ElementId:">92</t>
<t hangText="Semantics:">identifier</t>
<t hangText="Status:">current</t>
<t hangText="Reference:"><vspace blankLines="0" />BGP policy accounting as described in <xref target='CCO-BGPPOL'></xref></t>
</list>
</t>
</section>
<section title='dstTrafficIndex'>
<t>
<list style="hanging">
<t hangText="Description:"><vspace blankLines="0" />BGP Policy Accounting Destination Traffic Index</t>
<t hangText="Abstract Data Type:">unsigned32</t>
<t hangText="ElementId:">93</t>
<t hangText="Semantics:">identifier</t>
<t hangText="Status:">current</t>
<t hangText="Reference:"><vspace blankLines="0" />BGP policy accounting as described in <xref target='CCO-BGPPOL'></xref></t>
</list>
</t>
</section>
<section title='className'>
<t>
<list style="hanging">
<t hangText="Description:"><vspace blankLines="0" />Deprecated in favor of 335 selectorName. Traffic Class Name, associated with the classId Information Element.</t>
<t hangText="Abstract Data Type:">string</t>
<t hangText="ElementId:">100</t>
<t hangText="Status:">deprecated</t>
</list>
</t>
</section>
<section title='layer2packetSectionOffset'>
<t>
<list style="hanging">
<t hangText="Description:"><vspace blankLines="0" />Deprecated in favor of sectionOffset (TBD02). Layer 2 packet section offset. Potentially a generic packet section offset.</t>
<t hangText="Abstract Data Type:">unsigned16</t>
<t hangText="ElementId:">102</t>
<t hangText="Semantics:">quantity</t>
<t hangText="Status:">deprecated</t>
<t hangText="EDITOR'S NOTE:"><xref target='I-D.ietf-ipfix-data-link-layer-monitoring'></xref> contains a corresponding field 'sectionOffset' with a better description. "TBD02" needs to be replaced with the assigned value for the 'sectionOffset' in <xref target='I-D.ietf-ipfix-data-link-layer-monitoring'></xref>.</t>
</list>
</t>
</section>
<section title='layer2packetSectionSize'>
<t>
<list style="hanging">
<t hangText="Description:"><vspace blankLines="0" />Deprecated in favor of dataLinkFrameSize(312). Layer 2 packet section size. Potentially a generic packet section size.</t>
<t hangText="Abstract Data Type:">unsigned16</t>
<t hangText="ElementId:">103</t>
<t hangText="Semantics:">quantity</t>
<t hangText="Status:">deprecated</t>
<t hangText="EDITOR'S NOTE:"><xref target='I-D.ietf-ipfix-data-link-layer-monitoring'></xref> contains a corresponding field 'sectionObservedOctets' with a better description. </t>
</list>
</t>
</section>
<section title='layer2packetSectionData'>
<t>
<list style="hanging">
<t hangText="Description:"><vspace blankLines="0" />Deprecated in favor of dataLinkFrameSection (315). Layer 2 packet section data.</t>
<t hangText="Abstract Data Type:">octetArray</t>
<t hangText="ElementId:">104</t>
<t hangText="Status:">deprecated</t>
<t hangText="EDITOR's NOTE:"><xref target='I-D.ietf-ipfix-data-link-layer-monitoring'></xref> contains a corresponding field 'dataLinkFrameSection' with a better description.</t>
</list>
</t>
</section>
</section>
<section title="Other Information Elements">
<section title="Performance Metrics IEs">
<t>ElementId: 65 .. 69</t>
<t>Performance metrics will need a consolidation in the industry, based on RFC6390. Once this consolidation happens, via a separate document the IEs 65-69 will either be assigned in the IANA registry or their status will be deprecated.</t>
</section>
<section title="Application Information IEs">
<t>ElementId: 101</t>
<t>ElementId: 94 .. 97</t>
<t>Please refer to the <xref target="RFC6759">RFC 6759</xref></t>
</section>
<section title="IEs assigned for NetFlow v9 compatibility">
<t>ElementId: 105..126</t>
<t>These element IDs are not covered by this draft and left "as is", i.e. for Netflow v9 compatibility.</t>
</section>
</section>
<section title="IANA Considerations">
<t>This document specifies several new IPFIX Information Elements in the
IPFIX Information Element registry as defined in Section 3 above. The following Information Elements must be assigned:</t>
<t><list style="symbols">
<t>IE Number 34 for the samplingInterval IE</t>
<t>IE Number 35 for the samplingAlgorithm IE</t>
<t>IE Number 38 for the engineType IE</t>
<t>IE Number 39 for the engineId IE</t>
<t>IE Number 43 for the ipv4RouterSc IE</t>
<t>IE Number 48 for the samplerId IE</t>
<t>IE Number 49 for the samplerMode IE</t>
<t>IE Number 50 for the samplerRandomInterval IE</t>
<t>IE Number 51 for the classId IE</t>
<t>IE Number 84 for the samplerName IE</t>
<t>IE Number 87 for the flagsAndSamplerId IE</t>
<t>IE Number 89 for the forwardingStatus IE</t>
<t>IE Number 92 for the srcTrafficIndex IE</t>
<t>IE Number 93 for the dstTrafficIndex IE</t>
<t>IE Number 100 for the className IE</t>
<t>IE Number 102 for the layer2packetSectionOffset IE</t>
<t>IE Number 103 for the layer2packetSectionSize IE</t>
<t>IE Number 104 for the layer2packetSectionData IE</t>
</list></t>
</section>
<section title="Security Considerations">
<t>This document specifies the definitions of several Information Elements and does not alter the security considerations of the base protocol. Please refer to the security considerations sections of <xref target="RFC3954">RFC 3954</xref> and <xref target="RFC7012">RFC 7012</xref>.</t>
<t>However, the export of the sections of the packet payload may unintentionally change the security assumptions of other protocols.</t>
</section>
</middle>
<back>
<references title="Normative References">
<?rfc include='reference.RFC.7011'?>
</references>
<references title="Informative References">
<?rfc include='reference.RFC.3954'?>
<?rfc include='reference.RFC.6759'?>
<?rfc include='reference.RFC.7012'?>
<reference anchor="PSAMP-IANA"
target="http://www.iana.org/assignments/psamp-parameters/psamp-parameters.xml">
<front>
<title>Packet Sampling (PSAMP) Parameters</title>
<author>
<organization>IANA</organization>
</author>
<date year="2013" />
</front>
</reference>
<reference anchor="IPFIX-IANA"
target="http://www.iana.org/assignments/ipfix/ipfix.xml">
<front>
<title>IP Flow Information Export (IPFIX) Entities</title>
<author>
<organization>IANA</organization>
</author>
<date year="2013" />
</front>
</reference>
<?rfc include='reference.I-D.draft-ietf-ipfix-data-link-layer-monitoring-04'?>
<reference anchor="CCO-NF9FMT"
target="http://www.cisco.com/en/US/technologies/tk648/tk362/technologies_white_paper09186a00800a3db9.html">
<front>
<title>NetFlow version 9 Flow-Record format</title>
<author>
<organization>Cisco</organization>
</author>
<date year="2011" />
</front>
</reference>
<reference anchor="CCO-BGPPOL"
target="http://www.cisco.com/en/US/tech/tk365/technologies_tech_note09186a0080094e88.shtml">
<front>
<title>BGP Policy Accounting and BGP Policy Accounting Output Interface Accounting Features</title>
<author>
<organization>Cisco</organization>
</author>
<date year="2005" />
</front>
</reference>
<reference anchor="CCO-MLS"
target="http://www.cisco.com/en/US/products/hw/switches/ps700/products_configuration_example09186a00800ab513.shtml">
<front>
<title>IP MultiLayer Switching Sample Configuration</title>
<author>
<organization>Cisco</organization>
</author>
<date year="2007" />
</front>
</reference>
</references>
<section title="XML Specification of IPFIX Information Elements">
<figure><artwork><![CDATA[
<?xml version="1.0" encoding="UTF-8"?>
<fieldDefinitions xmlns="urn:ietf:params:xml:ns:ipfix-info"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="urn:ietf:params:xml:ns:ipfix-info
ipfix-info.xsd">
<field name="samplingInterval" dataType="unsigned32"
group=""
dataTypeSemantics="quantity"
elementId="34" applicability="flow" status="deprecated">
<description>
<paragraph>
Deprecated in favor of 305 samplingPacketInterval. When using
sampled NetFlow, the rate at which packets are sampled - e.g. a
value of 100 indicates that one of every 100 packets is sampled.
</paragraph>
</description>
</field>
<field name="samplingAlgorithm" dataType="unsigned8"
group=""
dataTypeSemantics="identifier"
elementId="35" applicability="flow" status="deprecated">
<description>
<paragraph>
Deprecated in favor of 304 selectorAlgorithm. The type of
algorithm used for sampled NetFlow: 1 - Deterministic Sampling;
2 - Random Sampling. The values are not compatible with the
selectorAlgorithm IE, where "Deterministic" has been replaced by
"Systematic count-based" (1) or "Systematic time-based" (2), and
"Random" is (3). Conversion is required, see
<REF:PSAMP-IANA>PSAMP parameters.
</paragraph>
</description>
</field>
<field name="engineType" dataType="unsigned8"
group=""
dataTypeSemantics="identifier"
elementId="38" applicability="flow" status="deprecated">
<description>
<paragraph>
Type of flow switching engine in a router/switch: RP = 0,
VIP/Line card = 1, PFC/DFC = 2. Reserved for internal use on the
collector.
</paragraph>
</description>
</field>
<field name="engineId" dataType="unsigned8"
group=""
dataTypeSemantics="identifier"
elementId="39" applicability="flow" status="deprecated">
<description>
<paragraph>
VIP or line card slot number of the flow switching engine in a
router/switch. Reserved for internal use on the collector.
</paragraph>
</description>
</field>
<field name="ipv4RouterSc" dataType="ipv4Address"
group=""
dataTypeSemantics="identifier"
elementId="43" applicability="flow" status="deprecated">
<description>
<paragraph>
This is a platform-specific field for Catalyst 5000/Catalyst
6000 family. It is used to store the address of a router that is
being shortcut when performing MultiLayer Switching.
</paragraph>
</description>
<reference>
http://www
.cisco.com
/en/US/pro
ducts/hw/s
witches/ps
700/products_configuration_example09186a00800ab513.shtml
describes the MultiLayer Switching.
</reference>
</field>
<field name="samplerId" dataType="unsigned8"
group=""
dataTypeSemantics="identifier"
elementId="48" applicability="flow" status="deprecated">
<description>
<paragraph>
Deprecated in favor of 302 selectorId. The unique identifier
associated with samplerName.
</paragraph>
</description>
</field>
<field name="samplerMode" dataType="unsigned8"
group=""
dataTypeSemantics="identifier"
elementId="49" applicability="flow" status="deprecated">
<description>
<paragraph>
Deprecated in favor of 304 selectorAlgorithm. The values are not
compatible: selectorAlgorithm=3 is random sampling. The type of
algorithm used for sampling data: 1 - deterministic, 2 - random
sampling. Use with samplerRandomInterval.
</paragraph>
</description>
</field>
<field name="samplerRandomInterval" dataType="unsigned32"
group=""
dataTypeSemantics="quantity"
elementId="50" applicability="flow" status="deprecated">
<description>
<paragraph>
Deprecated in favour of 305 samplingPacketInterval. Packet
interval at which to sample - in case of random sampling. Used
in connection with samplerMode 0x02 (random sampling) value.
</paragraph>
</description>
</field>
<field name="classId" dataType="unsigned8"
group=""
dataTypeSemantics="identifier"
elementId="51" applicability="flow" status="deprecated">
<description>
<paragraph>
Deprecated in favour of 302 selectorId. Characterizes the
traffic class, i.e. QoS treatment.
</paragraph>
</description>
</field>
<field name="samplerName" dataType="string"
group=""
dataTypeSemantics=""
elementId="84" applicability="flow" status="deprecated">
<description>
<paragraph>
Deprecated in favor of 335 selectorName. Name of the flow
sampler.
</paragraph>
</description>
</field>
<field name="flagsAndSamplerId" dataType="unsigned32"
group=""
dataTypeSemantics="identifier"
elementId="87" applicability="flow" status="deprecated">
<description>
<paragraph>
Flow flags and the value of the sampler ID (samplerId) combined
in one bitmapped field. Reserved for internal use on the
collector.
</paragraph>
</description>
</field>
<field name="forwardingStatus" dataType="unsigned32"
group=""
dataTypeSemantics="identifier"
elementId="89" applicability="flow" status="current">
<description>
<paragraph>
This Information Element describes the forwarding status of the
flow and any attached reasons. The Reduced Size Encoding rules
as per <REF:RFC7011> apply.
</paragraph>
<artwork>
The basic encoding is 8 bits. The future extensions
could add one or three bytes. The layout of the basic
encoding is as follows:
MSB - 0 1 2 3 4 5 6 7 - LSB
+---+---+---+---+---+---+---+---+
| Status| Reason code or flags |
+---+---+---+---+---+---+---+---+
Status:
00b = Unknown
01b = Forwarded
10b = Dropped
11b = Consumed
Reason Code (status = 01b, Forwarded)
01 000000b = 64 = Unknown
01 000001b = 65 = Fragmented
01 000010b = 66 = Not Fragmented
Reason Code (status = 10b, Dropped)
10 000000b = 128 = Unknown
10 000001b = 129 = ACL deny
10 000010b = 130 = ACL drop
10 000011b = 131 = Unroutable
10 000100b = 132 = Adjacency
10 000101b = 133 = Fragmentation and DF set
10 000110b = 134 = Bad header checksum
10 000111b = 135 = Bad total Length
10 001000b = 136 = Bad header length
10 001001b = 137 = bad TTL
10 001010b = 138 = Policer
10 001011b = 139 = WRED
10 001100b = 140 = RPF
10 001101b = 141 = For us
10 001110b = 142 = Bad output interface
10 001111b = 143 = Hardware
Reason Code (status = 11b, Consumed)
11 000000b = 192 = Unknown
11 000001b = 193 = Punt Adjacency
11 000010b = 194 = Incomplete Adjacency
11 000011b = 195 = For us
Examples:
value : 0x40 = 64
binary: 01000000
decode: 01 -> Forward
000000 -> No further information
value : 0x89 = 137
binary: 10001001
decode: 10 -> Drop
001001 -> Fragmentation and DF set
</artwork>
</description>
<reference>
See http:/
/www.cisco
.com/en/US
/technolog
ies/tk648/tk362/technologies_white_paper09186a00800a3db9.html -
NetFlow Version 9 Record Format.
</reference>
</field>
<field name="srcTrafficIndex" dataType="unsigned32"
group=""
dataTypeSemantics="identifier"
elementId="92" applicability="flow" status="current">
<description>
<paragraph>
BGP Policy Accounting Source Traffic Index
</paragraph>
</description>
<reference>
BGP policy accounting as described in
http://www
.cisco.com
/en/US/tech/tk365/technologies_tech_note09186a0080094e88.shtml
</reference>
</field>
<field name="dstTrafficIndex" dataType="unsigned32"
group=""
dataTypeSemantics="identifier"
elementId="93" applicability="flow" status="current">
<description>
<paragraph>
BGP Policy Accounting Destination Traffic Index
</paragraph>
</description>
<reference>
BGP policy accounting as described in
http://www
.cisco.com
/en/US/tech/tk365/technologies_tech_note09186a0080094e88.shtml
</reference>
</field>
<field name="className" dataType="string"
group=""
dataTypeSemantics=""
elementId="100" applicability="flow" status="deprecated">
<description>
<paragraph>
Deprecated in favor of 335 selectorName. Traffic Class Name,
associated with the classId Information Element.
</paragraph>
</description>
</field>
<field name="layer2packetSectionOffset" dataType="unsigned16"
group=""
dataTypeSemantics="quantity"
elementId="102" applicability="flow" status="deprecated">
<description>
<paragraph>
Deprecated in favor of TBD02 sectionOffset.
Layer 2 packet section offset. Potentially a generic packet
section offset.
</paragraph>
</description>
</field>
<field name="layer2packetSectionSize" dataType="unsigned16"
group=""
dataTypeSemantics="quantity"
elementId="103" applicability="flow" status="deprecated">
<description>
<paragraph>
Deprecated in favor of 312 dataLinkFrameSize.
Layer 2 packet section size. Potentially a generic packet
section size.
</paragraph>
</description>
</field>
<field name="layer2packetSectionData" dataType="octetArray"
group=""
dataTypeSemantics=""
elementId="104" applicability="flow" status="deprecated">
<description>
<paragraph>
Deprecated in favor of 315 dataLinkFrameSection.
Layer 2 packet section data.
</paragraph>
</description>
</field>
</fieldDefinitions>
]]></artwork></figure>
<!-- see the http://tools.ietf.org/search/rfc7012#appendix-A -->
</section>
<section title="Changes">
<t>To be removed by RFC Editor before publication</t>
<t>01: initial revision presented at the IETF meeting.</t>
<t>02: removed "flow" from flowSamplerId, flowSamplerMode, and
flowSamplerRandomInterval; updated the related drafts in references; added the "reference" column to the XML definitions; renamed fsFlowEntryTotalCount into deltaFlowCount to keep the naming in sync with draft-trammell-ipfix-a9n. Also minor changes to formatting and added the IE overview table.</t>
<t>03: updated the references to draft-claise-export-application-info-in-ipfix, slightly tweaked the title and removed the unused reference to draft-ietf-ipfix-flow-selection-tech.</t>
<t>04: sync the references.</t>
<t>05: update references to draft-claise-export-application-info-in-ipfix with reference to rfc6759, draft-trammell-ipfix-a9n to draft-ietf-ipfix-a9n, draft-kashima-ipfix-data-link-layer-monitoring to draft-ietf-ipfix-data-link-layer-monitoring.</t>
<t>06: sync the references.</t>
<t>07: Update per comment from Andrew Feren - change semantics of ipv4RouterSc to "identifier" and remove deltaFlowCount
as it made it to IANA. Update references RFC5101 to RFC7011, draft-ietf-ipfix-data-link-layer-monitoring from -03 to -04.</t>
<t>08: restore the 84 samplerName after its accidental deletion from table 1 in -07; mark 101-103 IEs as deprecated, include the paragraph on IE 105..126 that are not discussed in this draft.</t>
</section>
</back>
</rfc>
| PAFTECH AB 2003-2026 | 2026-04-23 09:26:53 |