<?xml version='1.0' encoding='utf-8'?>
<!DOCTYPE rfc [
  <!ENTITY nbsp    "&#160;">
  <!ENTITY zwsp   "&#8203;">
  <!ENTITY nbhy   "&#8209;">
  <!ENTITY wj     "&#8288;">
]>
<?xml-stylesheet type="text/xsl" href="rfc2629.xslt" ?>
<!-- generated by https://github.com/cabo/kramdown-rfc version 1.7.43 (Ruby 3.2.3) -->
<rfc xmlns:xi="http://www.w3.org/2001/XInclude" ipr="trust200902" docName="draft-gao-opsawg-flowspec-ipfix-01" category="std" consensus="true" submissionType="IETF" xml:lang="en" version="3">
  <!-- xml2rfc v2v3 conversion 3.35.0 -->
  <front>
    <title abbrev="FlowSpec IPFIX">Export of BGP FlowSpec Treatment Information in IPFIX</title>
    <seriesInfo name="Internet-Draft" value="draft-gao-opsawg-flowspec-ipfix-01"/>
    <author initials="Y." surname="Gao" fullname="Yujia Gao">
      <organization>Zhongguancun Laboratory</organization>
      <address>
        <postal>
          <region>Beijing</region>
          <code>100094</code>
          <country>China</country>
        </postal>
        <phone>+86-185-1028-7458</phone>
        <email>gaoyj@zgclab.edu.cn</email>
      </address>
    </author>
    <author initials="Y." surname="Cui" fullname="Yong Cui">
      <organization>Tsinghua University</organization>
      <address>
        <postal>
          <region>Beijing</region>
          <code>100084</code>
          <country>China</country>
        </postal>
        <email>cuiyong@tsinghua.edu.cn</email>
        <uri>http://www.cuiyong.net/</uri>
      </address>
    </author>
    <date year="2026" month="November" day="16"/>
    <area>Operations and Management</area>
    <workgroup>OPSAWG</workgroup>
    <keyword>BGP Flow Specification</keyword>
    <keyword>IPFIX</keyword>
    <keyword>DDoS mitigation</keyword>
    <abstract>
      <?line 73?>

<t>BGP Flow Specification (FlowSpec) is commonly used to distribute traffic filtering and traffic treatment rules. Operational monitoring of FlowSpec deployments may require information from multiple sources, including BGP control-plane telemetry, operational state, and forwarding-plane observations.</t>
      <t>This document defines IP Flow Information Export (IPFIX) Information Elements that add FlowSpec context to IPFIX Flow Records. The exported information enables a Collector to correlate exported Flow Records with a FlowSpec rule in the scope of an Observation Domain and to identify the action classes reported by the Exporter.</t>
    </abstract>
  </front>
  <middle>
    <?line 79?>

<section anchor="introduction">
      <name>Introduction</name>
      <t>BGP Flow Specification (FlowSpec) <xref target="RFC8955"/> <xref target="RFC8956"/> provides a mechanism for distributing traffic filtering and traffic treatment rules using BGP. A FlowSpec rule can identify traffic and request a treatment such as rate limiting (including discard at a zero rate), redirection, or traffic marking.</t>
      <t>When traffic is processed under a FlowSpec rule, operators often need visibility into traffic that matched the rule and was observed by enforcement devices. Control-plane information can describe distribution, validation, or installation of a FlowSpec route, but it does not by itself provide forwarding-plane statistics for traffic observed after FlowSpec processing.</t>
      <t>For example, after a mitigation system installs a FlowSpec rule for traffic toward a victim prefix, an operator may need to collect IPFIX statistics from enforcement devices and determine which exported Flow Records were associated with that rule and which action classes were reported at the Observation Point.</t>
      <t>IP Flow Information Export (IPFIX) <xref target="RFC7011"/> provides a mechanism for exporting Flow Records from Exporters to Collectors. Existing IPFIX Information Elements can describe flow keys, counters, timestamps, interfaces, Observation Points, and other properties of an observed Flow <xref target="RFC7012"/>. This document defines additional IPFIX Information Elements that allow a Flow Record to carry FlowSpec rule correlation and treatment context.</t>
      <t>IPFIX supports enterprise-specific Information Elements, but use of enterprise-specific elements for this information can make cross-vendor collection and analysis difficult. Standard Information Elements allow Collectors to recognize FlowSpec-treated Flow Records in a common way while still relying on existing IPFIX elements for generic flow properties and counters.</t>
      <t>The Information Elements defined in this document are intended to be used together with existing IPFIX Information Elements.</t>
    </section>
    <section anchor="terminology">
      <name>Terminology</name>
      <t>The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in BCP 14 <xref target="RFC2119"/> <xref target="RFC8174"/> when, and only when, they appear in all capitals, as shown here.</t>
      <t>This document uses the IPFIX terminology defined in <xref target="RFC7011"/>.</t>
      <t>The following terms are used in this document:</t>
      <ul spacing="normal">
        <li>
          <t>FlowSpec rule: A BGP FlowSpec route together with its associated traffic treatment information.</t>
        </li>
        <li>
          <t>FlowSpec-treated Flow Record: An IPFIX Flow Record that reports traffic observed after the traffic matched a FlowSpec rule and includes one or more Information Elements defined in this document.</t>
        </li>
        <li>
          <t>FlowSpec rule identifier: A local identifier, scoped to an Observation Domain, that associates a FlowSpec-treated Flow Record with the FlowSpec rule used by the Exporter for correlation.</t>
        </li>
        <li>
          <t>FlowSpec action class: A coarse-grained class of FlowSpec-derived action that the Exporter reports as associated with metered packets at an Observation Point.</t>
        </li>
      </ul>
    </section>
    <section anchor="scope">
      <name>Scope</name>
      <t>This document defines three new IPFIX Information Elements for traffic processed by BGP FlowSpec:</t>
      <ul spacing="normal">
        <li>
          <t>flowSpecRuleIdentifier, which provides a local identifier, scoped to an Observation Domain, for the FlowSpec rule associated with an exported Flow Record.</t>
        </li>
        <li>
          <t>flowSpecActionClassList, which reports the FlowSpec-derived action classes associated with the metered packets, and flowSpecActionClass, which identifies each class in the list.</t>
        </li>
      </ul>
      <t>Used together with existing IPFIX Information Elements for flow keys, counters, timestamps, interfaces, Observation Points, sampling information, and other generic flow properties, these Information Elements enable a Collector to correlate Flow Records with the FlowSpec rule and treatment reported by the Exporter.</t>
      <t>Typical uses include correlating IPFIX Flow Records with FlowSpec rules during DDoS mitigation, accounting for traffic observed under FlowSpec-derived treatment, and troubleshooting whether traffic observed at an Observation Point is associated with a specific FlowSpec rule.</t>
    </section>
    <section anchor="relationship-to-flowspec-monitoring">
      <name>Relationship to FlowSpec Monitoring</name>
      <t>The broader FlowSpec monitoring problem includes route lifecycle information, constrained realization information, enforcement status information, traffic-treatment outcome information, and correlation information across those sources <xref target="draft-cui-idr-flowspec-feedback-roadmap"/>.</t>
      <t>This document addresses only the IPFIX component of that problem: forwarding-plane observations of traffic associated with FlowSpec-derived behavior. BGP route status, FlowSpec validation status, and structured enforcement state are expected to be reported, when needed, by other mechanisms such as BGP control-plane telemetry or YANG-based operational models.</t>
    </section>
    <section anchor="flowspec-data-plane-statistics-export">
      <name>FlowSpec Data-Plane Statistics Export</name>
      <section anchor="export-model">
        <name>Export Model</name>
        <t>A FlowSpec-treated Flow Record extends an ordinary IPFIX Flow Record with FlowSpec-specific Information Elements. For example, an Exporter can combine source and destination addresses, transport ports, protocol information, timestamps, packet and octet counters, a FlowSpec rule identifier, and a list of FlowSpec action classes in one Flow Record.</t>
        <t>This model allows a Collector to process FlowSpec-treated traffic together with other IPFIX Flow Records while retaining the FlowSpec context needed for operational analysis.</t>
      </section>
      <section anchor="correlation-with-flowspec-rules">
        <name>Correlation with FlowSpec Rules</name>
        <t>The FlowSpec rule identifier defined in this document is used to correlate a FlowSpec-treated Flow Record with a FlowSpec rule referenced by the Exporter. The identifier is scoped to the Observation Domain that exports the Flow Record. The identifier is intended only for correlation within the Observation Domain.</t>
        <t>A Flow Record carrying this identifier reports traffic that matched the identified rule. If an Exporter reports multiple rules matched by the same traffic, it MUST use a separate Flow Record for each reported rule. This document does not require an Exporter to report every matching rule.</t>
        <t>The detailed representation of the FlowSpec rule and the mechanism used to distribute the mapping between a FlowSpec rule identifier and a FlowSpec rule are outside the scope of this document. A Collector that requires the complete rule needs to obtain that mapping from the Exporter or from an operational system that maintains the corresponding FlowSpec rule context.</t>
        <t>An Exporter SHOULD keep the association between a FlowSpec rule identifier and a FlowSpec rule stable for as long as Flow Records that use the identifier may be interpreted by a Collector.</t>
        <t>If a FlowSpec rule identifier is derived from an identifier signaled or configured by another mechanism, the Exporter SHOULD preserve the scope and collision properties of that mechanism. If no such identifier is available, the Exporter can assign a local identifier, provided that the identifier is unique within the Observation Domain for the relevant lifetime.</t>
      </section>
      <section anchor="reporting-action-classes">
        <name>Reporting Action Classes</name>
        <t>The FlowSpec action class list defined in this document reports the coarse-grained FlowSpec-derived action classes that the Exporter determines were associated with the metered packets at the Observation Point. It is not a complete encoding of the BGP FlowSpec Traffic Filtering Actions or their parameters, not proof that the requested actions were successfully enforced, and not a replacement for forwarding status or counters.</t>
        <t>Collectors SHOULD interpret this Information Element together with existing IPFIX Information Elements for counters, timestamps, interfaces, Observation Points, forwarding status, and sampling. Reported action classes do not by themselves demonstrate whether a mitigation policy was effective.</t>
        <t>More than one Traffic Filtering Action can be associated with the FlowSpec rule identified in a Flow Record. A Flow Record containing flowSpecActionClassList MUST also contain flowSpecRuleIdentifier. The Exporter MUST report each distinct action class of the identified rule that it determines was associated with at least one metered packet in the Flow Record. The list MUST NOT include action classes from other matching FlowSpec rules. The list does not indicate that every class was associated with every metered packet. The order of list members has no significance and does not report the order in which actions were applied. If the Exporter cannot determine the complete set of associated action classes for the identified rule, it MUST report only unknown (value 0) in the list. An absent list means that action classes were not reported, rather than that they were unknown.</t>
        <t>Action classes identify the signaled FlowSpec actions, not their resulting forwarding outcomes. The traffic-rate-bytes and traffic-rate-packets actions in <xref target="RFC8955"/> are reported as separate classes, including when their rate is zero and the resulting behavior is to discard traffic. The sampling bit of the traffic-action Extended Community is reported as sampling when set. The terminal-action bit controls evaluation of subsequent FlowSpec rules and is not reported as a traffic-treatment class. The redirect class includes the redirect actions in <xref target="RFC8955"/> and <xref target="RFC8956"/>.</t>
      </section>
      <section anchor="relationship-to-existing-ipfix-information-elements">
        <name>Relationship to Existing IPFIX Information Elements</name>
        <t>Existing IPFIX Information Elements are used for generic flow properties and statistics. Examples include IP addresses, transport ports, protocol identifiers, packet and octet counters, flow timestamps, interfaces, and Observation Point information.</t>
        <t>Existing IPFIX Information Elements can also describe forwarding outcomes where they are available from the Exporter. The Information Elements defined in this document add FlowSpec-specific rule correlation and treatment context to those records; they do not replace existing IPFIX Information Elements for counters, forwarding status, metering, or sampling.</t>
      </section>
    </section>
    <section anchor="flowspec-information-elements">
      <name>FlowSpec Information Elements</name>
      <t>This section defines the initial set of IPFIX Information Elements for FlowSpec data-plane statistics export.</t>
      <table>
        <thead>
          <tr>
            <th align="left">ElementID</th>
            <th align="left">Name</th>
            <th align="left">Description</th>
          </tr>
        </thead>
        <tbody>
          <tr>
            <td align="left">TBD1</td>
            <td align="left">flowSpecRuleIdentifier</td>
            <td align="left">Provides a local identifier for the FlowSpec rule associated with the Flow Record.</td>
          </tr>
          <tr>
            <td align="left">TBD2</td>
            <td align="left">flowSpecActionClassList</td>
            <td align="left">Reports the FlowSpec-derived action classes associated with the metered packets.</td>
          </tr>
          <tr>
            <td align="left">TBD3</td>
            <td align="left">flowSpecActionClass</td>
            <td align="left">Identifies an action class within flowSpecActionClassList.</td>
          </tr>
        </tbody>
      </table>
      <section anchor="flowspecruleidentifier">
        <name>flowSpecRuleIdentifier</name>
        <dl>
          <dt>Name:</dt>
          <dd>
            <t>flowSpecRuleIdentifier</t>
          </dd>
          <dt>ElementID:</dt>
          <dd>
            <t>TBD1</t>
          </dd>
          <dt>Description:</dt>
          <dd>
            <t>An identifier assigned or reported by the Exporter for the FlowSpec rule associated with the Flow Record. The identifier is scoped to the Observation Domain that exports the Flow Record. This Information Element is not reversible.</t>
          </dd>
          <dt>Abstract Data Type:</dt>
          <dd>
            <t>unsigned64</t>
          </dd>
          <dt>Data Type Semantics:</dt>
          <dd>
            <t>identifier</t>
          </dd>
          <dt>Units:</dt>
          <dd>
            <t>none</t>
          </dd>
          <dt>Status:</dt>
          <dd>
            <t>current</t>
          </dd>
          <dt>Reference:</dt>
          <dd>
            <t>This document.</t>
          </dd>
        </dl>
      </section>
      <section anchor="flowspecactionclasslist">
        <name>flowSpecActionClassList</name>
        <dl>
          <dt>Name:</dt>
          <dd>
            <t>flowSpecActionClassList</t>
          </dd>
          <dt>ElementID:</dt>
          <dd>
            <t>TBD2</t>
          </dd>
          <dt>Description:</dt>
          <dd>
            <t>A basicList of flowSpecActionClass Information Elements identifying the distinct FlowSpec-derived action classes of the rule identified by flowSpecRuleIdentifier in the same Flow Record that the Exporter determines were associated with at least one metered packet. The list uses the allOf structured data type semantic defined in <xref target="RFC6313"/> when it contains multiple members and the undefined semantic when it contains one member. List members MUST NOT be duplicated, and an exported list MUST contain at least one member. The order of members has no significance. If the complete set cannot be determined, the list MUST contain only unknown (value 0). This Information Element does not encode action parameters or confirm successful enforcement. This Information Element is not reversible.</t>
          </dd>
          <dt>Abstract Data Type:</dt>
          <dd>
            <t>basicList</t>
          </dd>
          <dt>Data Type Semantics:</dt>
          <dd>
            <t>list</t>
          </dd>
          <dt>Units:</dt>
          <dd>
            <t>none</t>
          </dd>
          <dt>Additional Information:</dt>
          <dd>
            <t>The list contains flowSpecActionClass (TBD3) values and is encoded as specified in <xref target="RFC6313"/>.</t>
          </dd>
          <dt>Status:</dt>
          <dd>
            <t>current</t>
          </dd>
          <dt>Reference:</dt>
          <dd>
            <t>This document.</t>
          </dd>
        </dl>
      </section>
      <section anchor="flowspecactionclass">
        <name>flowSpecActionClass</name>
        <dl>
          <dt>Name:</dt>
          <dd>
            <t>flowSpecActionClass</t>
          </dd>
          <dt>ElementID:</dt>
          <dd>
            <t>TBD3</t>
          </dd>
          <dt>Description:</dt>
          <dd>
            <t>A coarse-grained FlowSpec-derived action class reported as a member of flowSpecActionClassList. This Information Element does not encode a complete BGP FlowSpec Traffic Filtering Action or its parameters. This Information Element is not reversible.</t>
          </dd>
          <dt>Abstract Data Type:</dt>
          <dd>
            <t>unsigned8</t>
          </dd>
          <dt>Data Type Semantics:</dt>
          <dd>
            <t>identifier</t>
          </dd>
          <dt>Units:</dt>
          <dd>
            <t>none</t>
          </dd>
          <dt>Range:</dt>
          <dd>
            <t>0..255</t>
          </dd>
          <dt>Additional Information:</dt>
          <dd>
            <t>Values are defined in the "FlowSpec Action Class" subregistry.</t>
          </dd>
          <dt>Status:</dt>
          <dd>
            <t>current</t>
          </dd>
          <dt>Reference:</dt>
          <dd>
            <t>This document.</t>
          </dd>
        </dl>
        <t>The initial values for flowSpecActionClass are defined as follows:</t>
        <table>
          <thead>
            <tr>
              <th align="left">Value</th>
              <th align="left">Action Class</th>
            </tr>
          </thead>
          <tbody>
            <tr>
              <td align="left">0</td>
              <td align="left">unknown</td>
            </tr>
            <tr>
              <td align="left">1</td>
              <td align="left">traffic-rate-bytes</td>
            </tr>
            <tr>
              <td align="left">2</td>
              <td align="left">traffic-rate-packets</td>
            </tr>
            <tr>
              <td align="left">3</td>
              <td align="left">redirect</td>
            </tr>
            <tr>
              <td align="left">4</td>
              <td align="left">traffic-marking</td>
            </tr>
            <tr>
              <td align="left">5</td>
              <td align="left">sampling</td>
            </tr>
            <tr>
              <td align="left">6-255</td>
              <td align="left">Unassigned</td>
            </tr>
          </tbody>
        </table>
      </section>
    </section>
    <section anchor="export-example">
      <name>Export Example</name>
      <t>The following example illustrates a Template for exporting an IPv4 Flow Record for traffic processed by a FlowSpec rule.</t>
      <table>
        <thead>
          <tr>
            <th align="left">Information Element</th>
          </tr>
        </thead>
        <tbody>
          <tr>
            <td align="left">sourceIPv4Address</td>
          </tr>
          <tr>
            <td align="left">destinationIPv4Address</td>
          </tr>
          <tr>
            <td align="left">sourceTransportPort</td>
          </tr>
          <tr>
            <td align="left">destinationTransportPort</td>
          </tr>
          <tr>
            <td align="left">protocolIdentifier</td>
          </tr>
          <tr>
            <td align="left">packetDeltaCount</td>
          </tr>
          <tr>
            <td align="left">octetDeltaCount</td>
          </tr>
          <tr>
            <td align="left">flowStartMilliseconds</td>
          </tr>
          <tr>
            <td align="left">flowEndMilliseconds</td>
          </tr>
          <tr>
            <td align="left">observationPointId</td>
          </tr>
          <tr>
            <td align="left">flowSpecRuleIdentifier</td>
          </tr>
          <tr>
            <td align="left">flowSpecActionClassList</td>
          </tr>
        </tbody>
      </table>
      <t>The existing Information Elements provide the flow keys, statistics, timestamps, and observation context. The FlowSpec-specific Information Elements provide the local FlowSpec rule identifier and the action classes reported for the metered packets. The flowSpecActionClassList field contains flowSpecActionClass values; for example, it can contain traffic-rate-bytes (1) and redirect (3) without implying an order of application.</t>
    </section>
    <section anchor="operational-considerations">
      <name>Operational Considerations</name>
      <t>The interpretation of FlowSpec data-plane statistics depends on the Observation Point and metering behavior of the Exporter. A Collector needs to consider where the traffic was observed and whether the exported counters are affected by aggregation, sampling, filtering, or local implementation behavior.</t>
      <t>The Information Elements defined in this document provide correlation and treatment context for IPFIX Flow Records. They do not by themselves provide the full FlowSpec rule, its control-plane state, or the state of enforcement objects derived from the rule.</t>
      <t>The action class list reports associations for the Flow Record, which may aggregate multiple packets. A reported class need not have been associated with every metered packet. The list does not report action order; the ordered Information Element mechanism discussed in <xref target="draft-claise-opsawg-ipfix-ordered-ie"/> does not define an ordered-list data type for this purpose.</t>
      <t>Separate Flow Records for multiple rules matched by the same traffic may count some of the same packets. A Collector MUST NOT sum their counters as if the records represented disjoint traffic.</t>
      <t>A Collector needs to treat absence of a FlowSpec-specific Information Element differently from an explicit value. For example, a Flow Record without a FlowSpec rule identifier does not necessarily mean that no FlowSpec rule existed; it may mean that the Exporter did not support or did not apply this export.</t>
      <t>When multiple Exporters report records for the same FlowSpec rule, a Collector needs to use the Observation Domain, Observation Point, timestamps, and other IPFIX context to avoid treating independent observations as duplicate or equivalent measurements.</t>
    </section>
    <section anchor="security-considerations">
      <name>Security Considerations</name>
      <t>FlowSpec-treated Flow Records can reveal sensitive information about traffic filtering policy, DDoS mitigation behavior, victim prefixes, attack traffic characteristics, and platform or deployment capabilities. Exporters, Collectors, and transport paths need to protect this information according to the sensitivity of the exported Flow Records.</t>
      <t>Forged, modified, delayed, replayed, or suppressed Flow Records could cause an operator or automated system to draw an incorrect conclusion about whether FlowSpec treatment is active or effective. Deployments need appropriate authentication, integrity protection, confidentiality, access control, and replay or staleness handling for IPFIX export.</t>
      <t>The Security Considerations of <xref target="RFC7011"/> apply, including its guidance on protecting IPFIX export with TLS or DTLS as appropriate for the transport in use.</t>
      <t>High-volume FlowSpec-related export can create load on Exporters, Collectors, and transport paths. Deployments need to consider filtering, aggregation, sampling, rate control, and retention policies that are appropriate for the operational use case.</t>
    </section>
    <section anchor="IANA">
      <name>IANA Considerations</name>
      <t>IANA is requested to allocate flowSpecRuleIdentifier (TBD1), flowSpecActionClassList (TBD2), and flowSpecActionClass (TBD3) in the "IPFIX Information Elements" registry. Their complete definitions are in Section 6. New IPFIX Information Elements are reviewed according to the Expert Review process described in <xref target="RFC7012"/> and <xref target="RFC7013"/>.</t>
      <t>IANA is also requested to create and maintain a new subregistry named "FlowSpec Action Class" under the "IPFIX Information Elements" registry. The initial values are:</t>
      <table>
        <thead>
          <tr>
            <th align="left">Value</th>
            <th align="left">Description</th>
            <th align="left">Reference</th>
          </tr>
        </thead>
        <tbody>
          <tr>
            <td align="left">0</td>
            <td align="left">unknown</td>
            <td align="left">This document</td>
          </tr>
          <tr>
            <td align="left">1</td>
            <td align="left">traffic-rate-bytes</td>
            <td align="left">This document</td>
          </tr>
          <tr>
            <td align="left">2</td>
            <td align="left">traffic-rate-packets</td>
            <td align="left">This document</td>
          </tr>
          <tr>
            <td align="left">3</td>
            <td align="left">redirect</td>
            <td align="left">This document</td>
          </tr>
          <tr>
            <td align="left">4</td>
            <td align="left">traffic-marking</td>
            <td align="left">This document</td>
          </tr>
          <tr>
            <td align="left">5</td>
            <td align="left">sampling</td>
            <td align="left">This document</td>
          </tr>
          <tr>
            <td align="left">6-255</td>
            <td align="left">Unassigned</td>
            <td align="left"> </td>
          </tr>
        </tbody>
      </table>
      <t>New values in the "FlowSpec Action Class" registry are assigned by Expert Review <xref target="RFC8126"/>.</t>
    </section>
  </middle>
  <back>
    <references anchor="sec-combined-references">
      <name>References</name>
      <references anchor="sec-normative-references">
        <name>Normative References</name>
        <reference anchor="RFC2119">
          <front>
            <title>Key words for use in RFCs to Indicate Requirement Levels</title>
            <author fullname="S. Bradner" initials="S." surname="Bradner"/>
            <date month="March" year="1997"/>
            <abstract>
              <t>In many standards track documents several words are used to signify the requirements in the specification. These words are often capitalized. This document defines these words as they should be interpreted in IETF documents. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements.</t>
            </abstract>
          </front>
          <seriesInfo name="BCP" value="14"/>
          <seriesInfo name="RFC" value="2119"/>
          <seriesInfo name="DOI" value="10.17487/RFC2119"/>
        </reference>
        <reference anchor="RFC8174">
          <front>
            <title>Ambiguity of Uppercase vs Lowercase in RFC 2119 Key Words</title>
            <author fullname="B. Leiba" initials="B." surname="Leiba"/>
            <date month="May" year="2017"/>
            <abstract>
              <t>RFC 2119 specifies common key words that may be used in protocol specifications. This document aims to reduce the ambiguity by clarifying that only UPPERCASE usage of the key words have the defined special meanings.</t>
            </abstract>
          </front>
          <seriesInfo name="BCP" value="14"/>
          <seriesInfo name="RFC" value="8174"/>
          <seriesInfo name="DOI" value="10.17487/RFC8174"/>
        </reference>
        <reference anchor="RFC7011">
          <front>
            <title>Specification of the IP Flow Information Export (IPFIX) Protocol for the Exchange of Flow Information</title>
            <author fullname="B. Claise" initials="B." role="editor" surname="Claise"/>
            <author fullname="B. Trammell" initials="B." role="editor" surname="Trammell"/>
            <author fullname="P. Aitken" initials="P." surname="Aitken"/>
            <date month="September" year="2013"/>
            <abstract>
              <t>This document specifies the IP Flow Information Export (IPFIX) protocol, which serves as a means for transmitting Traffic Flow information over the network. In order to transmit Traffic Flow information from an Exporting Process to a Collecting Process, a common representation of flow data and a standard means of communicating them are required. This document describes how the IPFIX Data and Template Records are carried over a number of transport protocols from an IPFIX Exporting Process to an IPFIX Collecting Process. This document obsoletes RFC 5101.</t>
            </abstract>
          </front>
          <seriesInfo name="STD" value="77"/>
          <seriesInfo name="RFC" value="7011"/>
          <seriesInfo name="DOI" value="10.17487/RFC7011"/>
        </reference>
        <reference anchor="RFC7012">
          <front>
            <title>Information Model for IP Flow Information Export (IPFIX)</title>
            <author fullname="B. Claise" initials="B." role="editor" surname="Claise"/>
            <author fullname="B. Trammell" initials="B." role="editor" surname="Trammell"/>
            <date month="September" year="2013"/>
            <abstract>
              <t>This document defines the data types and management policy for the information model for the IP Flow Information Export (IPFIX) protocol. This information model is maintained as the IANA "IPFIX Information Elements" registry, the initial contents of which were defined by RFC 5102. This information model is used by the IPFIX protocol for encoding measured traffic information and information related to the traffic Observation Point, the traffic Metering Process, and the Exporting Process. Although this model was developed for the IPFIX protocol, it is defined in an open way that allows it to be easily used in other protocols, interfaces, and applications. This document obsoletes RFC 5102.</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="7012"/>
          <seriesInfo name="DOI" value="10.17487/RFC7012"/>
        </reference>
        <reference anchor="RFC7013">
          <front>
            <title>Guidelines for Authors and Reviewers of IP Flow Information Export (IPFIX) Information Elements</title>
            <author fullname="B. Trammell" initials="B." surname="Trammell"/>
            <author fullname="B. Claise" initials="B." surname="Claise"/>
            <date month="September" year="2013"/>
            <abstract>
              <t>This document provides guidelines for how to write definitions of new Information Elements for the IP Flow Information Export (IPFIX) protocol. It provides instructions on using the proper conventions for Information Elements to be registered in the IANA IPFIX Information Element registry, and provides guidelines for expert reviewers to evaluate new registrations.</t>
            </abstract>
          </front>
          <seriesInfo name="BCP" value="184"/>
          <seriesInfo name="RFC" value="7013"/>
          <seriesInfo name="DOI" value="10.17487/RFC7013"/>
        </reference>
        <reference anchor="RFC6313">
          <front>
            <title>Export of Structured Data in IP Flow Information Export (IPFIX)</title>
            <author fullname="B. Claise" initials="B." surname="Claise"/>
            <author fullname="G. Dhandapani" initials="G." surname="Dhandapani"/>
            <author fullname="P. Aitken" initials="P." surname="Aitken"/>
            <author fullname="S. Yates" initials="S." surname="Yates"/>
            <date month="July" year="2011"/>
            <abstract>
              <t>This document specifies an extension to the IP Flow Information Export (IPFIX) protocol specification in RFC 5101 and the IPFIX information model specified in RFC 5102 to support hierarchical structured data and lists (sequences) of Information Elements in data records. This extension allows definition of complex data structures such as variable-length lists and specification of hierarchical containment relationships between Templates. Finally, the semantics are provided in order to express the relationship among multiple list elements in a structured data record. [STANDARDS-TRACK]</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="6313"/>
          <seriesInfo name="DOI" value="10.17487/RFC6313"/>
        </reference>
        <reference anchor="RFC8126">
          <front>
            <title>Guidelines for Writing an IANA Considerations Section in RFCs</title>
            <author fullname="M. Cotton" initials="M." surname="Cotton"/>
            <author fullname="B. Leiba" initials="B." surname="Leiba"/>
            <author fullname="T. Narten" initials="T." surname="Narten"/>
            <date month="June" year="2017"/>
            <abstract>
              <t>Many protocols make use of points of extensibility that use constants to identify various protocol parameters. To ensure that the values in these fields do not have conflicting uses and to promote interoperability, their allocations are often coordinated by a central record keeper. For IETF protocols, that role is filled by the Internet Assigned Numbers Authority (IANA).</t>
              <t>To make assignments in a given registry prudently, guidance describing the conditions under which new values should be assigned, as well as when and how modifications to existing values can be made, is needed. This document defines a framework for the documentation of these guidelines by specification authors, in order to assure that the provided guidance for the IANA Considerations is clear and addresses the various issues that are likely in the operation of a registry.</t>
              <t>This is the third edition of this document; it obsoletes RFC 5226.</t>
            </abstract>
          </front>
          <seriesInfo name="BCP" value="26"/>
          <seriesInfo name="RFC" value="8126"/>
          <seriesInfo name="DOI" value="10.17487/RFC8126"/>
        </reference>
        <reference anchor="RFC8955">
          <front>
            <title>Dissemination of Flow Specification Rules</title>
            <author fullname="C. Loibl" initials="C." surname="Loibl"/>
            <author fullname="S. Hares" initials="S." surname="Hares"/>
            <author fullname="R. Raszuk" initials="R." surname="Raszuk"/>
            <author fullname="D. McPherson" initials="D." surname="McPherson"/>
            <author fullname="M. Bacher" initials="M." surname="Bacher"/>
            <date month="December" year="2020"/>
            <abstract>
              <t>This document defines a Border Gateway Protocol Network Layer Reachability Information (BGP NLRI) encoding format that can be used to distribute (intra-domain and inter-domain) traffic Flow Specifications for IPv4 unicast and IPv4 BGP/MPLS VPN services. This allows the routing system to propagate information regarding more specific components of the traffic aggregate defined by an IP destination prefix.</t>
              <t>It also specifies BGP Extended Community encoding formats, which can be used to propagate Traffic Filtering Actions along with the Flow Specification NLRI. Those Traffic Filtering Actions encode actions a routing system can take if the packet matches the Flow Specification.</t>
              <t>This document obsoletes both RFC 5575 and RFC 7674.</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="8955"/>
          <seriesInfo name="DOI" value="10.17487/RFC8955"/>
        </reference>
        <reference anchor="RFC8956">
          <front>
            <title>Dissemination of Flow Specification Rules for IPv6</title>
            <author fullname="C. Loibl" initials="C." role="editor" surname="Loibl"/>
            <author fullname="R. Raszuk" initials="R." role="editor" surname="Raszuk"/>
            <author fullname="S. Hares" initials="S." role="editor" surname="Hares"/>
            <date month="December" year="2020"/>
            <abstract>
              <t>"Dissemination of Flow Specification Rules" (RFC 8955) provides a Border Gateway Protocol (BGP) extension for the propagation of traffic flow information for the purpose of rate limiting or filtering IPv4 protocol data packets.</t>
              <t>This document extends RFC 8955 with IPv6 functionality. It also updates RFC 8955 by changing the IANA Flow Spec Component Types registry.</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="8956"/>
          <seriesInfo name="DOI" value="10.17487/RFC8956"/>
        </reference>
      </references>
      <references anchor="sec-informative-references">
        <name>Informative References</name>
        <reference anchor="draft-cui-idr-flowspec-feedback-roadmap" target="">
          <front>
            <title>Problem Statement and Roadmap for BGP FlowSpec Monitoring</title>
            <author initials="Y." surname="Cui" fullname="Yong Cui">
              <organization/>
            </author>
            <author initials="Y." surname="Gao" fullname="Yujia Gao">
              <organization/>
            </author>
            <author initials="J." surname="Haas" fullname="Jeff Haas">
              <organization/>
            </author>
            <date year="2026" month="July"/>
          </front>
        </reference>
        <reference anchor="draft-claise-opsawg-ipfix-ordered-ie" target="">
          <front>
            <title>Ordered Information Element Export in IP Flow Information Export (IPFIX)</title>
            <author initials="B." surname="Claise" fullname="Benoit Claise">
              <organization/>
            </author>
            <author initials="P." surname="Aitken" fullname="Paul Aitken">
              <organization/>
            </author>
            <author initials="H." surname="Keller" fullname="Holger Keller">
              <organization/>
            </author>
            <author initials="Y." surname="Liu" fullname="Yao Liu">
              <organization/>
            </author>
            <author initials="P." surname="Lucente" fullname="Paolo Lucente">
              <organization/>
            </author>
            <date year="2026" month="October"/>
          </front>
        </reference>
      </references>
    </references>
  </back>
  <!-- ##markdown-source:
H4sIAAAAAAAAA7Vc23fbNpp/51+Bk7wku5Jqu0maui/j2EnjXSfx2M7Mdl/2
QCQkoaEIDUHaUZv87/tdABAgKcXxduecOZVJEJfv+vsuyHQ6zWwjq+J/ZGkq
dSyaulWZ3tT0yzZHBwc/HxxluWyOhW2KzLbztbZWm6rZbmD4+eubN5mslTwW
Hzaqlg28sQLmE+9kJZdqraomu1vC28vrk3/+mmWFySu5hi+LWi6a6VKaqdlY
ebecLkpzZzcqn+rNQn+eHhxmWaObEoa+/rwxdSPMQrz69VK8gXHXME7cwLIN
LiDOq4Wp17S40JU4v3xz/l+ZnM9rdXvcjefHpaxgO6rKPt0dZ0JMw5wCB+mF
zmkeesVf4K+zM3Mt1rrRS34r22Zl6uNsCuvZY/HbTPwqDYzks/3W/q6le2Jq
WO6/V6ZaLltZ5W0lLuTcAKVMvYXXtqmVanAnuW62+N9aLWGFY/FK6d91tcQ3
poBJDw+AF8/oz7Zq6u2xOF3pSsKDzYpY9+8vX0wPXz6fHh4cvZz+9Oz5S3il
1lKXxwLIvP39b38s81LOZ6poZ3mVRXs/bXW3d9ipe0Bbv7GwiVUrxcdK36ra
wi6/e9sv92y722Te6i0s/rfGreg3KkRb62OxaprN8Q8/3N3dzdzIWaWaH7Ks
Yt7f0lxXb06PDg9/dj9fHv70zP386eDwsPt51P380f188WP4+fLw6IX/+fPz
591PeJppL2y8IMsx7Giqi7oT4oVSxVzmn6a1kcVabnCoEE6gL2szL9VaXDey
IRUhjbnikQKmTwX9nak0iAtTVQgve/h7OuRa9DASw+7pf6jFQryV0vKOZL0E
RopHj+jPAjZ0LI4Ojl5MD37qTldKbZVXVNZPUxeqVsVUq+RoH/hxopKvSz6k
02PSUFa5ZBS/fUJK93TnSV+pyuhGnNKWkjeXsi3FiW4+qSp5/taUS1WL/1Rl
qeqUQNKIC932ZjElPG1z2LH6BokOD0CLplMh56APMm+ybNyYiCeel0+FtqAJ
67Wpyq1oLVCqMaLQ8L2et40CqysX8JlY6LJRyHISDf+0CSavbktlZ53RlaVY
BzFBUxmkp1Cb0mzxIyvWcguK+q9W10roiPaL2qzFui0bvSmVsKatc2UnMCQv
2wInxHPlYPRrU043YEJhowq5Cgo9ESbahEWRntCmYfo7WePn7hMzt6q+ZR8x
y7KbFdAC/EFLByrUQlfK3kM0xmTLimYlQY2Kojs47ld9bpDA9CHPe6VyEF0g
3c1KCUUTAxNiYqhKgnaCFxOnBkQmB5riHPBZrUo4XfdVPKG4080KvgnLI4dQ
1htYx+ZAI+SKrMSHjgrizIDpq5jFRugCTqIXW/oExAlHgOpZC5uplVtzzq+Z
JKqesQSudVGUKsseA3GASUVLX99HHv/801m5r1/D7xfwe1ObW9gQkmGt8pWs
tF2TaQrCinLxXeIK8u5kaSZOeoTKgTLd+d33OBeKq7LA2mg22+ZAaiAKcqPU
6Jdh3ieduMIecxA9gSIh/lC1oaFPJzBbAbJPxAG5rcNKa1l/gg+Bmv9cqSo8
BgEFOoAuoKK2FZi2Poe99JvaAn8b+LYCyy9utdVzXYJvBBEA1gaKoJSCnOUr
1HzgIx0ez3kH52EFYSYrlMhcOd241Tmq+2migrHQIv2AWzlwRkUswmPeylIX
MhwZnH4jy5I/Q5GMDmRaVF74UICJLQywrDIN7kY3VpULLxRD1Ua1h0V1bklG
/HHDgcCLAO3CQo6oTPE38IH6LNcbpCYPlBHWEnZrwUv6fduBjsULNuaO+A4M
ACavYSEwK5/RHgU+kREkJpFSk4Y7AxGfAi3iCA+IV4WCTa7BXIm7lQZR3GEQ
wBGClFqTa4kvyUCQAHRMp897qk7fBX2H4SgnsdW4NCBTQLh7mErSaIQ++zSa
t496k+yfSODtjEVqBXsIovj6M1IKvmHSjdrkRCgRGolPagt+haAgzDkB1LAG
5Qbek7eBZwtJnmdwXMs+xQAtajwJMLPRyjqbGuSMDuAPffT1K5r5MS8DjkI7
j7Vn/+xTSpxTxrQhyZF1ve0bMecicBK2g95iOV9ETCNJazdIVysQZdSbGuGV
dSZ6dC+slQAY8MRjHym/aVIHPHTfPKzlJ9hibayd3qqqgGFO+v12IWIrtxbJ
pVGZAA7MEKJWBarUKIGYNp1YIGHAvJplpf9QgThTokNfPdDvOSgExm+LuoDY
o9FlCXOUW8Ix4I1TOUuOuVQVOJ2cRSsSCjyMlzECGmp8+ywNBXvpWEwk4SOw
5gWbCRBfh9UACaIEki6rb6vATKBPviFrAbhyueXdgBqIO6LCo3cfr28eTfi/
4v0H+n31+u8fz69en+Hv67cnFxfhhx9x/fbDx4uz7lf35emHd+9evz/jj+Gp
6D16d/LbI9alRx8ub84/vD+5eDROAD63ZllTZItsUGci2qvTS3H4jPUNo64A
ISDsgt934Eqd2iLa5T+BfFshNxslaxIB4HYuNxpMO6q4FXZl7ioBNFYDiNii
dURjyPRuOqrGnIxMnuP9wqCYElyBTywdjtjZPzZEd/+WqvQxAJUkFiMX2ZMD
jZrQ2fkh+ok0cRatMKYXsGA1hKvObSi2GTu8K1KmwzMMMfq+EpnBMAltJ2Jy
8Iem/k79mPXJ5KGbVjVSrDQ5GNbu2YQBMKnSKAKeOFPriRg7+TEqeV+qetsg
rvYQMlmKyDInm49dL+48N7IGq7qsJR2cnsfR1BQgoCaS84e07WQ1zyRpB75/
jbAB/tjI/JPCIU2fGt6zPxbXSLBdMVKzqpUCDHO3z3nFsKgDsUCcWJ5J4hfu
jysg4XnENEYnEWx4AF/ZG/X51KeMrEYx1Cze3QlR/BQ5cgF2128vKEW0SJ9L
HlkNwZjqM8WFrsM1/Xrh9OC7JfzNIuLivBI2Bpv++CBfQbT6P6Mki0AaF4qM
ToyddvhMMsx2hx3giHh3QDyMg0dYnuChPeFsdrPdaJQzMvfOWHUKHEg4XDRZ
ENSmpYC0l7oFWuREWXw3GqtwnDeQpbD5iTuLaTFNsDKGpgLvRvQdGudxLcfY
cqAGIsC55CyMIq6cAbMrvUH6j+UHyd/NMecYh1tRZmjjUo/BCbBDK/VC5du8
VKnYAGzFzBbZQjh+qf/wSfZoUBwlYQTV2vS9o8i04z4sCcBPDUU0BtAxfJUE
W0FSjA3pKXD098y9OiCQ4JuiqBXZBIImHaiAfW3AL1ZUbiDr7ih2vD+fRcN9
2qLH1oEozdVK3mpTz8gWMweYcpOOaV3YHt4hiYAfbd60aLL6hFeEbMCQgooG
3Oo1bUL4iwJf/AP0ju1BCAVtSKvsSfYhXvjt5P2v07lEG2eS9GOhSkvOK5zh
TDZyeklTXHexNSs7DHzsw9V3+G2Wnex3+hBAASK3FPAhHyTsZwiVUpLvDapm
Is09VJ0bx4AJZGGOQT4LnIv80Yo7ofQyRCJeWToJOaMJCk1jILzqaUJkx9nf
sGEGdjWRuR8kESOHS3Ea+ZkkydtzdOCOENylrpQ0gLjEcdsgw+lQwpAJXXYl
dmksP2PGmCI5CBnAcBDqjp2Bz8qyIJIFjqXIx6DoCEA+TiODkNp4BCuW7d0u
au2O77QNuffOi90HcvZZU6sFoIcqH/FklGCONgNrdmipn9JxiWAyOIyEOkTj
OTgyYYhRyYr1gC7t2AGT4Vozr27+fJTQYHbhzN06/bBjkMMMYwvnrc4XiS75
CUKBgf2zn8IRDoBLiF8mmH+kiBgzHuAW1UbWPaTBqSsZIGBYvYeZfRbT1z3i
nVG6gvRW3SqwJrQlpAHNxNJVoByX5AAhDLYwZ0id7kA5hCp9gm2sxoMDIATG
heaquVOq2qPzTuV768BBwG1YTMYmBYY0ToOIJtJwjiGJCixd6OxKwL88J2ok
ZXDMvAnC6PdJycAk0EGwig9DatUVgDhb6z4GAYX/+9VANMFKVoVPNcaZM58f
O4nY43Ibn5TacE3EOVYk/wMJB+Z37nLG4OlKLJtKm5ov2jrKXZPqG+aNewkR
EN3IhiJMO1/s2xHyxmEAT7vordVLoCBqM+pxtdBLcvO4SNVz1pOUF45QJJ8A
OiORYFRVgsNAoqWJU+aRn5LUtjKMAtI9y1vQAKRbb1l0ksAT2PZocOgix6KL
ktNp20r/q1X7zVQIIMGqqVsJCo1QFR3pjBzElfK5a47VxCm7wJ5niP0je8+d
viEOKHvpgG/Fl8NsQKgU7CwHDCLQ3Rl/cU6eC42Z7HQXvI8pXNEXv+v1yLDN
fhPqc0wmK5isuhZoWWkLgDxwauCalw2mO9XfwmHdQUBKECss2rIMtaqC4Qnv
D8hYSgdOKbAN6NkHCSTlIUkbJZGdNAdFYwaNdRQ8LMZ+WGA9OIDD4y7enjlR
HEpFYXwVDba6tqq8xYdqzbFVo0LomFS9NqbU+ZbKgmqxwCz9LYr8O0zWAXMY
4O1iL2nmfFzcdhinghPyCeDoAQRTeUS3IyfDLluW1vjBO3JLjGWCltBn3hGj
Ry+IkXmT6q0T8B7cYFHFemWkayPZNxhUKom4uerrnE/fDNBWGQ6FmXSfi+jx
lyy5s88eP6SpiGiyAEc0uMFcNm77DD/4mGObd/Ak2TXPSn04SBqafq3WcyzW
raQlWw6mmar+lY9fOjRE1G7CDECCuBrp7dUGhFsV5Bv6ph+n6SqhCZ6wisKT
6BR9mjmr3uNlh/vc/rhNpvpUYVHgCYTE4C8OnibpNkyYyzniMk8CWfnS3Uhh
tTs82ivQP0raoEJ5k7flgW5VhCS94Cpu0wg+u+dqnDFlEwtuGaEvJ5y8EXFJ
ECccPkmCBmE63zauipU8Dg7CccgXO1z3hkzKxrYDzW7jcT8P5QLc5nAI2Fdq
k/D4tduxz1XgEIax1FnhNsabDznHuW68lvqdOx68/uwilVOzXoPjx8YIm27X
T0J7s16+Wb5k6SfCJVxyAiwjSkSA47YFMQBvBZLQSwVS2cMmvKcE/UhuiojF
S/tmkZDjdSmzJn63ixmwYtRO48FKmsG7Rw09y+5TaA8VrW9VRbsOB6zgU96j
y7GeX94zpxHs+P48Bm1gl4vFD0aSonGl7F5HJwyKHqdrNBjqGMoU+U2sPaJZ
84B2GNcw67+zXBy1nXUZp/u1BHA2APOaNccfv/A2HWpwMOoB2GYEr5D/gAfU
BxSAS5KxG5dBCqmtaxXoqlAYDAFiwaiPDf43Ntf1JGJecNA5xIkP2M8X/9n5
mfgi3mNi4Is4I/5uaNYv2Zdp978vyX/8Q5jl5tXZIXw5jkHgxeXu0tY9C1cD
1OCWPYqW7YOkLw4p/mU1q7Dqj+OrwtPzrmqF+hKjKhd+7dgtzo2ma5yGWYbM
Oc6Od74PjMRByI8sixiJD0+SGJjDSY6BdxWJHsqb/4eE3I64JPga6pifUy7p
xDUJU1Jc3OD1CTh9W/F5XzwDwvgX4lqtIdQFncAhOiLnR9A3elgBis2ya1Js
/Dtvwc5UTZZd+YwkETyt2seM7PF5yMnBgD4rj4asFHNpdX7hstNjojhqGzyi
8sniAP+/pRwOa/QjGZCXHTrv+3HRpAz6K74rct8TTkRwP7SsyLL8sIiLN2gC
BV6iAdvJzB40seCNBNdGIxzqoWRayKN6tO9RG1YueYow5+Bj3i5+NxMXccgQ
whxsIG3BNWB04kL6uD7fxUQ+xuuRgudOYpM9YUkILZLgwYUXc9XxoZgEzJ8u
Px4j7NHOEARR6iTEc10iJCTg6nWU6IjrbX+J7gdl2an6Jb3sKf1J1LvYrc/q
7ugTuD2mgk/QUzwVRKgAjZkUDMQZwAwEcfZX2Zu9tmZoZ34csTPfk5jrQX6W
xR32iV3e/SWnk9p7pd2o/xoMXidqf6kTefkQH3IlqyXNcjCbHT1/vk++/uFE
plYpFlbiUTh6nIZ9hCEZXgyDTW8fID43EcJ04up7ZPpCHe9JWtfyB0sBMKJd
AwaKdxYhyBQ2euh4AB94m4J/I44cidHx1VH/lY/T8SVCshAr4oNn0Wh364Ce
P4fnIQTGBy+mwA14+LEKmAihmC+Zu+it3+HoitlCl2XL6UWU+RsFDzHOT9u9
JbYa3j4bVNVG28Z6ZQ2C6WNim2LzlKpcScc1TzjQpJNGRfX+K/7gxoeil3jy
3ifDlz5QjbE+Pia2nKmykacYJdFDill7z0i+Glk37zQWToAu2HXg37yuisHz
qBOE4tjzoptoJPDI9gQHzNAu3BvDS/4aBmpe1DDWhVJpZpti8wjb+mKbiEsk
+zslkiU5Vtpbdtt3g8mj90EUc+OOM0YXmLks9vs1thC/OBl3PR26ca0cjBVG
VPjJ4VN30chp6RNwjgjxDF6DgVm2TlUCmqGkaO6TFI+TS3inpsKirLsJ7U2Y
K2SETNU3AuFCbajRxQyrYpwmwf36YL7L0JlFL5MRV39DdTd3O+xyIkHfkztI
fD/FNbXFd+V8ioEzKVSbcBZiuQRj73pdvC2bdHfDKO3gAm3kzjrU0kND1EOa
9b1ofjvVgpKx4yrgdrxMk2haW/akfkLOPG2VchcgnYxzWxZd2eh6tcz8d6BZ
rxTs4xhHgmHBsmssDkVwm0TC7jy+URXL1Z4jqosZgraddBrJq9CdKCQB8EIB
S1T1HWWItLjhsvfSgx446S9drUGNXw/ueiYwydxa6xHofS4hQ5wUVmdJCSoL
73l3IeIKV2Q2bb0xFml+PdJhwuS9f9cKkZy0A/zWWnl9pCER2TudDCGXbdcu
G98pF4TFLrp1mwn9Jxg9avs7WQKfh8dunhFlJx3g8kiu0tt+ew0+XQFCYNZg
X5FrVQALAHYPLCpZ2n7z3KBZCu3nnl6IwK5KIciQtS63VLzhYLwyvU/JJari
FzTpSOhuaBq3axZid8NKmO4R2u0tMz6kGum6Z2Bxd9vNSXAdCUKSOIhsgBwj
vO8fGeuJH9jzEXcd9dZFiWJ5a7QzbNzizZ6CjUrUjIoXdXwIjxTAph9gGmuZ
tG3t+h/ppoECMI71mL7r2n99C70qhiaU/IUPsT6d9uzOUQCGF4S5sD3p92UH
HzBJ725SraBpQH3CXGAmMAaC6RzYQYohvsXFieHhyjveLZJ0EVcrKnk4/k6i
S2u+nzuUO2SzsuGGKIJJRAWDK3XYRs7pdZc+9GRAWjrVH70Yyldel5jQWJuC
Iu0JbLmUW6pIYsKffmGOHoS4ZgSeEt+0iIYkdcdFV1uxq6ltQMxwTd+JZfBf
cbijXqOKfGROHjGHAKHjk/f0Qbaj20tccbxlSQq9COIs+ocFiFqgX7XZ1Jqa
KVuYDsNPBwcQAy1JzBxBtesvX7BJkHhXmnrzEfo7lzpxwAwpQuRoUIZxADiK
ovQd/O5moFdpdEc7hBr5El+JJYsQ10XRny9bXVDBnBumaLPd/UOOvsgb3lxc
467O8L+YWoiO7+1FJ1XgyVryNG/1cjW9NWUbWZIpt6AWfnqCrKR1gJcktnd+
h+iOcCaGfREc2wHYuGicsqBBJvm2FO17nSS3CAyOHTcEoozmko7+WJyfvD/p
8+TPx/j0a5bRS6oK+5YjNHklIsZG7QqmMJt1+HSyM3DA90dPd17r8dkwn8fY
XcF6JEImAxEP+WqX+yHAoZ3ppaujKID09YuZeL//nhaX7W+1uqO8Vc+oANsV
MPaKBoQO7eQWZnTduSs74z9sQyk7T1SqkSaUdQJGsYRr1ARfhrfKoqwN/aso
xc78Dt+V+T7K9VM6QIAkT5MU+kRIEO1M2XzpJRmS1E2vG3hfKmdk6O7Uzsjg
NNUzMmA09TMyLk0FjQwYSw1h5gAlzRH1G3m5wF7JpQ2eBDBtKm/uNu8RdzDg
PzSC92qy/wX4dP82NkwAAA==

-->

</rfc>
