<?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-ye-srv6ops-sfc-deployment-03" category="info" submissionType="IETF" xml:lang="en" version="3">
  <!-- xml2rfc v2v3 conversion 3.35.0 -->
  <front>
    <title abbrev="SRv6 SFC Deployment">SRv6 SFC Deployment Options</title>
    <seriesInfo name="Internet-Draft" value="draft-ye-srv6ops-sfc-deployment-03"/>
    <author initials="J." surname="Ye" fullname="Jiaming Ye">
      <organization>China Mobile</organization>
      <address>
        <postal>
          <country>CN</country>
        </postal>
        <email>yejiaming@chinamobile.com</email>
      </address>
    </author>
    <author initials="C." surname="Lin" fullname="Changwang Lin">
      <organization>New H3C Technologies</organization>
      <address>
        <postal>
          <country>CN</country>
        </postal>
        <email>linchangwang.04414@h3c.com</email>
      </address>
    </author>
    <date year="2026" month="November" day="15"/>
    <area>OPS</area>
    <workgroup>SRv6OPS</workgroup>
    <keyword>SFC</keyword>
    <keyword>SRv6</keyword>
    <keyword/>
    <abstract>
      <?line 63?>

<t>This document outlines the critical factors for deploying Service Function Chaining (SFC) using Segment Routing over IPv6 (SRv6). It addresses deployment architectures, including both SRv6-aware and SRv6-unaware scenarios, and details the end-to-end provisioning lifecycle. Furthermore, it proposes reliability mechanisms and provides strategic recommendations for network operators transitioning from legacy NSH-based SFC to a modern, scalable SRv6 framework.</t>
    </abstract>
  </front>
  <middle>
    <?line 67?>

<section anchor="intro">
      <name>Introduction</name>
      <t>Service Function Chaining (SFC) <xref target="RFC7665"/> is a network architecture that orchestrates traffic through a sequence of service functions—such as firewalls, load balancers, and deep packet inspection (DPI)—to form a logical processing chain. While traditional networks rely on scattered physical or virtual appliances, SFC leverages standardized mechanisms to dynamically steer traffic, significantly enhancing network flexibility and automation.</t>
      <t>Historically, the Network Service Header (NSH) defined in <xref target="RFC8300"/> has been the primary encapsulation protocol for SFC. However, widespread adoption of NSH faces three significant challenges:</t>
      <ul spacing="normal">
        <li>
          <t>Compatibility: Mainstream hardware switches and operating systems often lack native support for NSH, making deployment more demanding in existing networks.</t>
        </li>
        <li>
          <t>Scalability: Per-flow state must be maintained on every Service Function Forwarder (SFF) and Service Function (SF) along the Service Function Path (SFP), creating a management bottleneck as the network scales.</t>
        </li>
        <li>
          <t>Fragmentation: NSH often relies on overlay tunneling (e.g., VXLAN/GRE). This additional layer complicates the integration between the Overlay and Underlay networks.</t>
        </li>
      </ul>
      <t>Segment Routing over IPv6 (SRv6) <xref target="RFC8986"/> offers a robust alternative for SFC. By leveraging IPv6 extension headers, SRv6 enables source-based routing where the path is encoded directly into the packet. This eliminates the need for complex state maintenance on intermediate nodes and provides end-to-end programmability.</t>
      <t>This document focuses on the practical deployment of SRv6 SFC, moving beyond theoretical definitions to provide a comprehensive guide covering architectural choices, operational workflow, reliability, and best practices. It offers recommendations on how to deploy in environments with native SRv6 support versus those requiring legacy compatibility, presents a step-by-step lifecycle from business request to service decommissioning, describes mechanisms to ensure high availability during failures, and provides strategic recommendations for network planners and operators.</t>
      <section anchor="requirements-language">
        <name>Requirements Language</name>
        <t>The key words "<bcp14>MUST</bcp14>", "<bcp14>MUST NOT</bcp14>", "<bcp14>REQUIRED</bcp14>", "<bcp14>SHALL</bcp14>", "<bcp14>SHALL
NOT</bcp14>", "<bcp14>SHOULD</bcp14>", "<bcp14>SHOULD NOT</bcp14>", "<bcp14>RECOMMENDED</bcp14>", "<bcp14>NOT RECOMMENDED</bcp14>",
"<bcp14>MAY</bcp14>", and "<bcp14>OPTIONAL</bcp14>" 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>
        <?line -18?>

</section>
    </section>
    <section anchor="terminology">
      <name>Terminology</name>
      <t>SF (Service Function): A network function that performs specific operations on traffic (e.g., firewall, NAT).</t>
      <t>SFC (Service Function Chaining): The process of steering traffic through an ordered sequence of service functions.</t>
      <t>SFC Proxy: A functional entity that translates between SRv6 and non-SRv6 protocols (e.g., stripping NSH or raw IP) to enable legacy SFs to participate in an SRv6 chain.</t>
      <t>SRv6 (Segment Routing over IPv6): A source-routing technology that uses IPv6 extension headers to encode paths.</t>
      <t>SFF (Service Function Forwarder): The node responsible for steering traffic to the appropriate SF and maintaining the chain logic.</t>
      <t>SID (Segment Identifier): An IPv6 address used in SRv6 to identify a specific segment or instruction.</t>
      <t>SRH (Segment Routing Header): The IPv6 extension header carrying the segment list.</t>
      <t>SRv6-Aware SF: An SF capable of natively processing SRv6 packets (parsing SRH).</t>
      <t>SRv6-Unaware SF: An SF that cannot process SRv6 packets and requires a proxy or decapsulation.</t>
    </section>
    <section anchor="deployment-options">
      <name>Deployment Options</name>
      <t>This section provides guidance on selecting between the SRv6-aware and SRv6-unaware SFC architectures, based on an assessment of their characteristics, advantages, and applicability, and further identifies the deployment considerations associated with each model.</t>
      <t>Both architectures are built on the following core components:</t>
      <ul spacing="normal">
        <li>
          <t>Classifier: The entry point of the SFC that identifies and classifies traffic flows based on policies (e.g., 5-tuple) and inserts the initial SRH with the ordered SID list.</t>
        </li>
        <li>
          <t>SFF: The core forwarding element that forwards received SRv6 packets to the next hop based on the active SID, and handles the returned traffic from the SF.</t>
        </li>
        <li>
          <t>SF: The actual application node (e.g., Firewall) that executes the business logic.</t>
        </li>
        <li>
          <t>SFC Proxy (required only in Unaware Mode): It maintains a mapping table between SRH context and the virtual interface to the SF, strips the SRH before forwarding the payload to the SF, and re-encapsulates the returned packet with the correct SRH to continue the chain.</t>
        </li>
      </ul>
      <section anchor="srv6-aware-sfc">
        <name>SRv6-Aware SFC</name>
        <t>In SRv6-aware model, all Service Functions in the chain natively support SRv6. Accordingly, no SFC Proxy is needed, and SRv6 packets are forwarded directly between SFFs and SFs.</t>
        <t>Characteristics: In SRv6-aware SFC, no SFC Proxy is required. The SFF forwards SRv6 packets directly to the SF. The SF parses the SRH, executes its service logic, updates the SRH (if necessary), and forwards it back to the SFF or to the next hop.</t>
        <t>Advantages: SRv6-aware SFC provides the lowest latency, the simplest control plane, and the highest efficiency.</t>
        <t>Applicability: SRv6-aware SFC is suited to new deployments, or to networks in which all SFs have been upgraded to support SRv6.</t>
        <figure anchor="f1">
          <name>SRv6 SFC</name>
          <artwork type="ascii-art" align="center"><![CDATA[
                        +-------+    +-------+
                        | SF 1  |    | SF 2  |
                        |       |    |       |
                        +---+---+    +---+---+
                            |            |
                            |            |
           +--------+   +---+---+    +---+---+
 Source ---+ Classi +---+ SFF 1 +----+ SFF 2 +---- Destination 
           | fier   |   |       |    |       |
           +--------+   +-------+    +-------+

]]></artwork>
        </figure>
      </section>
      <section anchor="srv6-unaware-sfc">
        <name>SRv6-Unaware SFC</name>
        <t>In the SRv6-unaware model, some SFs in the network do not support SRv6. An SFC Proxy is therefore deployed in front of each SRv6-unaware SF to bridge SRv6 and the SF's native packet format. The SRv6 proxy caches the mapping relationship between the SRH and the virtual interface to the SF, which is used to recover SRv6 packets based on the virtual interface when packets return from the SF. SRv6-unaware SFC is designed for networks containing legacy SFs that do not support SRv6.</t>
        <t>Characteristics: An SFC Proxy is deployed immediately adjacent to the SRv6-Unaware SF. The Proxy acts as a translator, converting SRv6 packets to a format the SF can understand (e.g., raw IPv4/IPv6 or NSH) and converting returned packets back.</t>
        <t>Advantages: SRv6-unaware SFC enables the integration of legacy infrastructure without immediate hardware replacement.</t>
        <t>Applicability: SRv6-unaware SFC is suited to incremental upgrades in which replacing all SFs is not feasible.</t>
        <figure anchor="f2">
          <name>SRv6 SFC with SFC Proxy</name>
          <artwork type="ascii-art" align="center"><![CDATA[
                       SRv6 unaware
                        +-------+
                        | SF 1  |
                        |       |
                        +---+---+
                            |
                            |        SRv6 aware
                        +---+---+    +-------+
                        | SFC   |    | SF 2  |
                        | Proxy |    |       |
                        +---+---+    +---+---+
                            |            |
                            |            |
           +--------+   +---+---+    +---+---+
 Source ---+ Classi +---+ SFF 1 +----+ SFF 2 +---- Destination 
           | fier   |   |       |    |       |
           +--------+   +-------+    +-------+
]]></artwork>
        </figure>
        <section anchor="proxy-options">
          <name>Proxy Options</name>
          <t>A proxy may be co-located with the SF or SFF, or deployed on another compute node or device. Several proxy behaviors are defined in <xref target="I-D.draft-ietf-spring-srv6-service-programming-00"/>, and the choice among them is driven by the SF’s capabilities and the constraints each behavior imposes.</t>
          <ul spacing="normal">
            <li>
              <t>Static SR Proxy SFC
  The static proxy removes the SR information before forwarding traffic to the SF, and re-attaches cached SR information to returned traffic based on the receiving interface.The cached SR information is manually configured and bound to a single SID list.  </t>
              <t>
This behavior is suitable for small, stable SFC with infrequent policy changes, because each static proxy segment is bound to one SID list and each receiving interface to one proxy segment.</t>
            </li>
            <li>
              <t>Dynamic SR Proxy SFC
  The dynamic proxy has the ability to learn the SRv6 information from incoming traffic and caches it locally, removing the need for manual CACHE configuration. The cache entry is mapped to the receiving interface (IFACE-IN), so each interface effectively serves one SR service policy; sharing an interface across multiple policies requires careful planning.  </t>
              <t>
This behavior is suitable SFCs whose path change frequently.</t>
            </li>
            <li>
              <t>Masquerading SR Proxy SFC:
  The masquerading proxy forwards the SRv6 packet to the SF without stripping the SRH, but instead sets the destination address to the final SID in the SRH. The SF is expected to process IPv6 packets but not inspect the SRH.  </t>
              <t>
This behavior suits services that only inspect, drop, or perform limited modifications, such as IDS, DPI, and non-NAT firewalls. Services that terminate transport connections or generate new packets require the Caching flavor, and NAT services require the Destination NAT flavor.
  A masquerading proxy segment must not be the last segment in an SR service policy, since replacing the destination would serve no purpose when no further SID remains. Beyond this placement constraint, a masquerading segment can be reused across multiple SRv6 policies, and one interfaces can be bound to multiple masquerading proxy segments.</t>
            </li>
          </ul>
        </section>
      </section>
    </section>
    <section anchor="deployment-lifecycle">
      <name>Deployment Lifecycle</name>
      <t>Deploying SRv6 SFC follows a structured lifecycle comprising six key stages:</t>
      <t><strong>1.Service Request</strong></t>
      <t>Purpose: Translate a business requirement into a defined SFC and its associated Service Level Agreements (SLAs).</t>
      <t>The process begins with a business requirement. 
Stakeholders define the desired SFC (e.g., "All Web traffic must traverse Firewall -&gt; WAF -&gt; Load Balancer") and specify SLAs for latency, bandwidth, and availability.</t>
      <t><strong>2.Node Deployment</strong></t>
      <t>Purpose: Deploy or activate the required network elements and establish underlay connectivity before SFC logic is applied.</t>
      <t>Physical or virtual network elements (Classifiers, SFFs, SFs, and Proxies) are deployed or activated. The underlay network is configured (IPv6 addressing, IGP/BGP routing) to ensure basic connectivity between all nodes.</t>
      <t><strong>3.SID Allocation</strong></t>
      <t>Purpose: Assign SIDs to each SF and Proxy, and generate the segment list that defines the traversal order.</t>
      <t>One or more SIDs are allocated to each SF and Proxy, and the SIDs assigned to one node must not duplicate those assigned to any others. Allocation may be:</t>
      <ul spacing="normal">
        <li>
          <t>Static Allocation: SIDs are manually configured for stable, small-scale chains.</t>
        </li>
        <li>
          <t>Dynamic Allocation: A controller assigns SIDs on demand based on real-time resource availability.</t>
        </li>
      </ul>
      <t>A complete segment List is then generated, defining the exact traversal order of the SFC.</t>
      <t><strong>4.Configuration Delivery</strong></t>
      <t>Purpose: Push configuration to the data plane and verify that the policies, segment lists or rules, where present on each node, are consistent with the intended service requirement.</t>
      <t>The control plane (SDN Controller or Orchestrator) pushes the configuration to the data plane:</t>
      <ul spacing="normal">
        <li>
          <t>The Classifier receives the policy and the initial Segment List.</t>
        </li>
        <li>
          <t>SFFs receive instructions on how to forward traffic to specific SIDs and handle return traffic.</t>
        </li>
        <li>
          <t>Proxies, if applicable, are configured with the mapping rules between SIDs and local interfaces.</t>
        </li>
      </ul>
      <t>After the configuration is delivered, verification confirms that all nodes have consistent views of the chain.</t>
      <t><strong>5.Network Monitoring</strong></t>
      <t>Purpose: Continuously verify SFC health and SLA compliance once the SFC is active.</t>
      <t>Continuous monitoring covers:</t>
      <ul spacing="normal">
        <li>
          <t>Connectivity: The link between SFF and SF/Proxy is monitored through mechanisms such as Bidirectional Forwarding Detection (BFD).</t>
        </li>
        <li>
          <t>Performance: Metrics such as latency, jitter, and packet loss are tracked to ensure SLA compliance.</t>
        </li>
        <li>
          <t>State Validation: The system verifies that packets are traversing the SFC in the correct order.</t>
        </li>
      </ul>
      <t><strong>6.Service Modification and Teardown</strong></t>
      <t>Purpose: Adjust the SFC as business requirements evolve and release resources when a service is retired.</t>
      <t>Modification: Adding new SFs, changing the order, or updating policies triggers a recalculation of the Segment List and a configuration update.</t>
      <t>Teardown: When a service is retired, resources (SIDs, mappings) are released, and configurations are removed to prevent residual state.</t>
    </section>
    <section anchor="multi-tenancy-considerations">
      <name>Multi-tenancy Considerations</name>
      <t>During deployment, support for multi-tenancy must be considered.</t>
      <t>One approach is for the Service Function (SF) to assign different SRv6 SIDs for each tenant, with the Classifier encapsulating distinct SRv6 SID sequences per tenant. This method allows the SF to identify the tenant based on the SRv6 SID, offering simple implementation. However, its drawback is that assigning individual SRv6 SIDs for each tenant consumes significant SID resources, which must be evaluated against the number of tenants.</t>
      <t>An alternative approach is to carry tenant information within the service packet itself. This avoids the need to allocate separate SRv6 SIDs per tenant but results in a more complex system implementation.</t>
      <t>For instance, as in shown in <xref target="f3"/>, the traffic of tenant A enters vFW through a 3-layer sub-interface with VLAN ‘a’, while tenant B’ s traffic enters through that of VLAN ’b’. With the existence of VLANs and VPN instances, vFW would be able to figure out tenants and select their exclusive vsys instances to supply service. For example, the traffic of tenant A with destined for address X would be dropped by vsys1 instance on vFW, while tenant B’s traffic with destination address Y will be dropped by vsys2 instance.</t>
      <figure anchor="f3">
        <name>Multi-Tenancy Example</name>
        <artwork type="ascii-art" align="center"><![CDATA[
                    +------+
                    |vsys1 |vFW
                   -+vsys2 |
                  / |...   |
                 /  +------+
                /     
               /    +------+
              /     |vsys1 |vIPS
 +--+   +----+      |vsys2 |
 |GW+---+TOR1+------|...   |
 +--+   +----+      |      |
              \     +------+
               \
                \
                 \  +------+
                  \ |vsys1 |vAV
                   -+vsys2 |
                    |...   |
                    |      |
                    +------+
]]></artwork>
      </figure>
      <t><xref target="I-D.draft-lin-spring-srv6-aware-context-indicator-08"/> describes how to use SRv6 SIDs as context indicator for SR-aware services.</t>
    </section>
    <section anchor="reliability-considerations">
      <name>Reliability Considerations</name>
      <t>This section discusses the the reliability and fault detection mechanisms for SRv6 SFC deployment, along with the considerations for selection.</t>
      <section anchor="reliability-options">
        <name>Reliability Options</name>
        <t>In SRv6 SFC deployment, service continuity can be affected by three types of failure: an SFF failure, an SF failure, and links failure between the SFF and the SF. Any of these failures can cause packets to be dropped if no protection is deployed, since the packets can no longer be forwarded along the intended logical order or processed by the intended SF.</t>
        <t>To enhance the reliability of the SRv6 SFC, protection mechanisms can be deployed, individually or in combination:</t>
        <ul spacing="normal">
          <li>
            <t>SF redundancy at a single SFF: A primary SF and a backup SF, or a cluster of SFs, are deployed for the same service and connected to the same SFF. When the primary SF becomes unreachable, traffic is switched to the backup SF; when an SF in the cluster becomes unreachable, traffic is switched to another SF in the cluster. This mode protects against SF failure and SFF-SF link failure, and preserves the SF capability for the service through the backup or another SF in the cluster.</t>
          </li>
          <li>
            <t>SFF redundancy: The SF is dual-homed to a primary SFF and a backup SFF. When the primary SFF fails, or when it detects that the SF or proxy is unreachable, traffic is switched to the backup SFF. The number of backup SFFs may be increased according to service importance and cost considerations. This mode protects against SFF failure and SFF-SF link failure.</t>
          </li>
          <li>
            <t>SF redundancy across SFFs: A primary SF and a backup SF are connected to a primary SFF and a backup SFF, respectively. When the primary SFF fails, or when it detects that the SF or proxy is unreachable (including SF or proxy failure and SFF-SF link failure), traffic is switched to the backup SFF and forwarded to the backup SF. This mode protects against SFF failure, SF failure and SFF-SF link failure.</t>
          </li>
          <li>
            <t>SFF bypass: When the SFF detects all SFs providing the same service are down or unreachable, traffic bypasses the failed service node and is forwarded to the downstream node in the chain. This mode preserve connectivity for the remaining services, but the processing of the skipped SF is lost, which may be unacceptable for security-critical SFC. This mode is, strictly, not a redundancy mechanism.</t>
          </li>
          <li>
            <t>Hybrid protection: When multiple modes are deployed, SF redundancy at a single SFF is attempted first, followed by SFF redundancy and then SF redundancy across SFFs, bypass is used only if all these redundancy mechanisms fail. This provides both multiple SF-level redundancy and a last-resort path, at the cost of more complex configuration and state maintenance.</t>
          </li>
        </ul>
        <t>The table <xref target="t1"/> summarizes the characteristics of these mechanisms and the failures they can handle.</t>
        <table anchor="t1">
          <name>Summary of Protection Modes</name>
          <thead>
            <tr>
              <th>Protection Mode</th>
              <th>SFF Failure</th>
              <th>SF Failure</th>
              <th>SFF-SF Link Failure</th>
              <th>Deployment Characteristics</th>
            </tr>
          </thead>
          <tbody>
            <tr>
              <td>SF redundancy at a single SFF</td>
              <td>×</td>
              <td>√</td>
              <td>√</td>
              <td>primary&amp;backup SF or SF cluster connected to same SFF</td>
            </tr>
            <tr>
              <td>SFS redundancy</td>
              <td>√</td>
              <td>√</td>
              <td>×</td>
              <td>one SF dual-homed to primary&amp;backup SFF</td>
            </tr>
            <tr>
              <td>SF redundancy across SFFs</td>
              <td>√</td>
              <td>√</td>
              <td>√</td>
              <td>primary&amp;backup SF connected to primary&amp;backup SFF, respectively</td>
            </tr>
            <tr>
              <td>SFF Bypass</td>
              <td colspan="3">
        /        <br/>
Only ensuring remaining services can still be completed when the current SF fails
      </td>
              <td>No backup SF or SFF required</td>
            </tr>
            <tr>
              <td>Hybrid Protection</td>
              <td colspan="3">Depending on the combination</td>
              <td>Depending on the combination</td>
            </tr>
          </tbody>
        </table>
      </section>
      <section anchor="fast-fault-detection">
        <name>Fast Fault Detection</name>
        <t>Fast fault detection determines how quickly protection mechanisms can be triggered when an SF becomes unreachable. It is therefore required between the SFF and the SF, or between the SFF and the SFC Proxy, so that dual-homing or bypass protection can be activated promptly.</t>
        <t>BFD is a typical choice for this purpose. The selection of the detection method should consider the required fault response time and the deployment cost.</t>
      </section>
    </section>
    <section anchor="deployment-recommendations">
      <name>Deployment Recommendations</name>
      <t>Based on the architectural and lifecycle analysis above, the following recommendations are provided for SRv6 SFC deployment:</t>
      <t><strong>1.Prioritize stateless architectures for greenfield deployments.</strong></t>
      <t>For greenfield deployments, adopt Stateless SRv6 SFC exclusively. Avoiding NSH and stateful proxies reduces complexity and maximizes performance.</t>
      <t><strong>2.Use proxies strategically for brownfield upgrades.</strong></t>
      <t>For brownfield upgrades, deploy SFC Proxies to integrate legacy SFs. This enables a phased migration in which SFs can be upgraded to SRv6-aware over time without disrupting existing services.</t>
      <t><strong>3.Plan resources for multi-tenant deployments.</strong></t>
      <t>When supporting multiple tenants, evaluate the trade-off between SID consumption and implementation complexity:</t>
      <ul spacing="normal">
        <li>
          <t>For small-scale multi-tenancy, assigning an unique SID per tenant is straightforward.</t>
        </li>
        <li>
          <t>For large-scale environments, consider embedding tenant identifiers within the packet payload to conserve the SID space, accepting the increased software complexity.</t>
        </li>
      </ul>
      <t><strong>4.Apply tiered high availability.</strong></t>
      <t>Not all services require the same level of redundancy. Protection should be selected according to service importance:</t>
      <ul spacing="normal">
        <li>
          <t>For critical services, redundancy <bcp14>MUST</bcp14> be implemented to avoid service interruption and achieve zero downtime. At a minimum, one protection mechanism must be selected; where conditions permit, hybrid protection <bcp14>SHOULD</bcp14> be implemented to handle SF failure, SFF failure and SFF-SF link failure, with bypass protection as a last resort.</t>
        </li>
        <li>
          <t>For standard services, where temporary loss of specific services or performance degradation, bypass protection <bcp14>MAY</bcp14> be used to ensure the remaining services could be performed when a SF node fails.</t>
        </li>
      </ul>
      <t><strong>5.Automate the deployment lifecycle.</strong></t>
      <t>Manual configuration of SRv6 SFC is error-prone and unscalable. Operators <bcp14>MUST</bcp14> implement SDN controllers or orchestration platforms to automate the lifecycle stages from SID allocation to configuration delivery.</t>
      <t><strong>6.Protect SRH integrity.</strong></t>
      <t>SRH headers should be protected against tampering and validation mechanisms should be implemented to prevent unauthorized modification of the segment list, which could redirect traffic to malicious nodes.</t>
    </section>
    <section anchor="security-considerations">
      <name>Security Considerations</name>
      <t>TBD.</t>
    </section>
    <section anchor="iana-considerations">
      <name>IANA Considerations</name>
      <t>This document has no IANA actions.</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>
      </references>
      <references anchor="sec-informative-references">
        <name>Informative References</name>
        <reference anchor="I-D.draft-ietf-spring-srv6-service-programming-00">
          <front>
            <title>SRv6 Service Programming</title>
            <author initials="A." surname="Abdelsalam, Ed">
              <organization/>
            </author>
            <author initials="C." surname="Filsfils">
              <organization/>
            </author>
            <author initials="D." surname="Bernier">
              <organization/>
            </author>
            <author initials="C." surname="Li">
              <organization/>
            </author>
            <author initials="B." surname="Decraene">
              <organization/>
            </author>
            <date year="2026" month="July"/>
          </front>
          <seriesInfo name="Internet-Draft" value="draft-ietf-spring-srv6-service-programming-00"/>
        </reference>
        <reference anchor="I-D.draft-lin-spring-srv6-aware-context-indicator-08">
          <front>
            <title>SRv6 Context Indicator SIDs for SR-Aware Services</title>
            <author initials="J." surname="Ye">
              <organization/>
            </author>
            <author initials="C." surname="Lin">
              <organization/>
            </author>
            <author initials="D." surname="Lu">
              <organization/>
            </author>
            <author initials="M." surname="Chen">
              <organization/>
            </author>
            <date year="2026" month="July"/>
          </front>
          <seriesInfo name="Internet-Draft" value="draft-lin-spring-srv6-aware-context-indicator-08"/>
        </reference>
        <reference anchor="RFC7665">
          <front>
            <title>Service Function Chaining (SFC) Architecture</title>
            <author fullname="J. Halpern" initials="J." role="editor" surname="Halpern"/>
            <author fullname="C. Pignataro" initials="C." role="editor" surname="Pignataro"/>
            <date month="October" year="2015"/>
            <abstract>
              <t>This document describes an architecture for the specification, creation, and ongoing maintenance of Service Function Chains (SFCs) in a network. It includes architectural concepts, principles, and components used in the construction of composite services through deployment of SFCs, with a focus on those to be standardized in the IETF. This document does not propose solutions, protocols, or extensions to existing protocols.</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="7665"/>
          <seriesInfo name="DOI" value="10.17487/RFC7665"/>
        </reference>
        <reference anchor="RFC8300">
          <front>
            <title>Network Service Header (NSH)</title>
            <author fullname="P. Quinn" initials="P." role="editor" surname="Quinn"/>
            <author fullname="U. Elzur" initials="U." role="editor" surname="Elzur"/>
            <author fullname="C. Pignataro" initials="C." role="editor" surname="Pignataro"/>
            <date month="January" year="2018"/>
            <abstract>
              <t>This document describes a Network Service Header (NSH) imposed on packets or frames to realize Service Function Paths (SFPs). The NSH also provides a mechanism for metadata exchange along the instantiated service paths. The NSH is the Service Function Chaining (SFC) encapsulation required to support the SFC architecture (defined in RFC 7665).</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="8300"/>
          <seriesInfo name="DOI" value="10.17487/RFC8300"/>
        </reference>
        <reference anchor="RFC8986">
          <front>
            <title>Segment Routing over IPv6 (SRv6) Network Programming</title>
            <author fullname="C. Filsfils" initials="C." role="editor" surname="Filsfils"/>
            <author fullname="P. Camarillo" initials="P." role="editor" surname="Camarillo"/>
            <author fullname="J. Leddy" initials="J." surname="Leddy"/>
            <author fullname="D. Voyer" initials="D." surname="Voyer"/>
            <author fullname="S. Matsushima" initials="S." surname="Matsushima"/>
            <author fullname="Z. Li" initials="Z." surname="Li"/>
            <date month="February" year="2021"/>
            <abstract>
              <t>The Segment Routing over IPv6 (SRv6) Network Programming framework enables a network operator or an application to specify a packet processing program by encoding a sequence of instructions in the IPv6 packet header.</t>
              <t>Each instruction is implemented on one or several nodes in the network and identified by an SRv6 Segment Identifier in the packet.</t>
              <t>This document defines the SRv6 Network Programming concept and specifies the base set of SRv6 behaviors that enables the creation of interoperable overlays with underlay optimization.</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="8986"/>
          <seriesInfo name="DOI" value="10.17487/RFC8986"/>
        </reference>
      </references>
    </references>
    <?line 438?>

<section numbered="false" anchor="acknowledgements">
      <name>Acknowledgements</name>
    </section>
    <section numbered="false" anchor="contributors">
      <name>Contributors</name>
    </section>
  </back>
  <!-- ##markdown-source:
H4sIAAAAAAAAA+1c23IbR3q+x1N06KpElAHouF4vV9YuRAoWtyiKEWV7XdlU
ajDTIMYazGCnZ0jBtrZ8mQdIVbK50rMob+InyfcfuqcHACl5U3sXV7Ii5tCH
//j9h57RaDRwTVJm/5YUVWkPTFO3dpAmjb2o6vWByct5NXDtbJk7l1flq/UK
zxw/fTUd5Kuan3bN/bt3f3P3/qBIyosDY8vBIKltcmBenJ0PrnDl/OXlZ/T3
oMmbwspvcz49NEd2VVTrpS0b82LVYHQ3SGaz2l7ufGaQVWmZLDFAVifzZrS2
I1dfflat3MjN01EWHhzdfTCoZq4qbGPdwaBdZQn/8YmhPw7M/bv374/u0v+Z
0YivmdyZeV4UNsN+TdI21TJp8jQpirWZrc2bZXG/nqcmn5uyasxFfolNvr46
GBgzokXKv1gx/zHA+4uqxt0RfuelOzB/GJtvLX7I8v+QJ8u8vJBLVX2RlPn3
CW3/wBwu8jIxz6tZXtDNtGrLhrhweIpfdpnkxYFZ2+9kgN+n9PSSHx6n1dIM
oikPx+YkL8Ochwsw5wr/r1f7057aK/PswaF5ZdNFWRXVRW7dddMXeZn6wcZ3
Hz689/D3iwcpzT8YDMqqJspd2oPBgCQn/DLmeHQ0FsbltpmP3KrGFpiDI2fr
yzy1o1VdXdTJkvY2unuXXjJGZWZPBEIeNGfdg3v8VCA5/zcSEkzGZjLLbOGS
IlkOzdNs3L8PEk3zwoHxrn/jaGye2LrMbb31wknev/RkDAlN68SWlm8ECfts
dPfXfAWbAzWJGH55x2WD0W0zOiJyeHH+SKoMeqQEM3rvJFdQvVFaYYY3GLLM
IMRNVY/ufr6DmofyGNajj5nz4yMoAv3xcjShoTzF3Q1k9sK9Sahyi6gnbf/S
8zHk0pb/R8J9PA0GgxEUPpm5pk7SZjB4tYDew6q0bIKqtsFQ1plmYU1a52wA
zBxPVrVQRUwMqa4XxGlbpqRCpF95SXduwR7sm9bJUxc88ksMTb+rS1ub4zOQ
/hYxYH9sjhuTZFltncO8nQUzSQ3dbmzatLg3BLXSos1oiFnVLNjUyDYNDLf8
bEu54FJbJnVe4S26l9kGWit7smU2aqoR/jGQqcuc7DmNWeRzm65TGBHsp8aT
9bKqLWZt6LlVRWurbZEnMDR5szZLSwYgd0vHU/BYGZ4hssJt5CmehjnARjK2
L0I88O2qql+bamXrhEmKx0uXN7qKeQ0LVtiLJF2b0/Nno1niYI7JBTSVScyy
ysD7IfYHbZ4VVjzEHIphadix8HaZZxksJ0w9ZKWusla488MnOf18Oxh8iHE/
/PC7l9PDX3/22a/eviWvkIR1xywBORMIDK5Y2TRvZj7H1ptFXbUXC7zo7J9b
W2Kuam5Ul81cp3U///Qfrk3xGDme2l7B1YBjRZVkZoYN4rU6cNCuzCpJX9uG
tGZlZd23js6O9zEKiENmFvOR2SaJBT+gsCyAKW1ubL5ZwEPQCjOmNp7RTTFf
1wbDgawNlAsUXy3WjscBzy7zumnxZ7Jagf1YFNZEHCksJDm5YJ5jjUmd5d/j
1UgwsKxsDdejTtQ1FqKvNAIT84syx19J2eCmLfFWSuv1tJ4X9k2u0kY08B65
KsHnZ7mD+MjAQxbsU33NM/eZTSAs5hbEaB/0m0Or2bELcz9/cPcumLsA6WfW
ljwCzMcyqWkpabJybcFzESWbKq0KMYlTWLVn1RVtfWiuSOJXgDlYXFYxeCE+
Y0ayGGxEamvjjRIzgDDKC4Iig9uwvssVppFdHrx/9xysgjDZZIml1Zko81Xe
kIwxEURxiExuDXqCyNW8wfoLyAa8PPlZ49rVqqobXjDWMjTL5DW9EZkW0m38
XmJIugOygNauicjvxrS+c1Y0v7ozW4/mRXVFDAdeWgL1gXoYHoqVMH1BACLN
ets2Tqsau2GOnE+n+2KzNh/CLdwBBL1ghmzdP0tg+PDQ2f4QxtkKIWAWkhJy
yBuDaYRzKy2okYjB8+JENsPKrqYQW3pagM/7d8QwISNZOFCa+IhtFMnaNG1Z
4iLZBju+GA/N1388mZze+fLlU1hu9h2w3V6j8AI2CLMHTUnFImAFoI69qEWa
ZliNl7cXOgWR4qsykx8R+T/kObwo/+bzzyDK1XwOcwFq1NWMGJMU5CdFIoLo
Pll7taUBeSz4R1uSFzAL1hjSbrKq8CCwsFDuqq0BQMQS17qUK/gHK0pDLAEV
oDQwzrBUMGQpKTR2XekTZLaUWCAlMEwgTWnxCq2OaWbfeMkiicIC2HCWTMB6
abOc7pVVZjd8Tt+nMU5SoR1v+vc5/nDCYVF5eHY2dJFyQIV95AHdwRzkcu26
wvB4B5rj34BNycW3Yau6GjCA9lLbBVEVtL9o6WpKzGNp7TwIxkgXVc4GVfWa
pYj4T2o2jB2u+IEZXI1fNISZoIPyfdPbEj+hqWSCeWes4yVseVXSJh2MFxin
8sHb9WYDC3UtsQc+H8P+uc154eqV09hiDbEW63i4hMz7ajRbj+jfDk6IS58R
FoI/4vFoD1iXd4cZr1wiS0w0xAUH5IWtbvgSEJTc7iInz3oJROOxSNbyCue4
JFDpb0AkK/jbkhUoWFnAE8jPJ5+Yl0wEK3Q7QcjTwtyQZFnz2q6JX5kze8+/
On+1N5R/zekL/vvl03/+6vjl0yP6+/zZ5OQk/DHQJ86fvfjq5Kj7q3vz8MXz
509Pj+RlXDW9S4O955Nv92Srey/OXh2/OJ2c7BGXm57AkwcB7WZihmrwq4HK
JW7gqcxO8cnh2ft39x7CovwDLMr9e/d+A4siPz6/9+uH+AGNL2W2qoR2y0+o
w3oAXGCTmmPmAhKdrPImIRwD++sggmRXakt291+IMv96YB7N0tW9h4/1Am24
d9HTrHeRabZ9ZetlIeKOSzumCdTsXd+gdH+9k297vz3do4uPfkfxgxnd+/x3
jweEQV/BdOUcT69h0qew3RtebR8eaNKhHu/rGF1CDgnYgZKAfIQhOkMhNkwB
p/omjyKH5nTyap9cCHDa1oQB7tLMr9gKMlhkjEoYjZRpC8rCJZL7hrzciGl1
UgTnb9a8MX8Hhg3ySOrKO2PcX7Aj8D6RrRBJWFmVI/7hsZfzG4Qu56sVrY99
dm3q5ApubF/MA4cEaqfOp2KVkxqmMl9xfqekXfDAgomx1JfsTa9ztMIa9YDe
9zU+P6I7YX+y25XKssgxsp8U4uwQgQ4deZaQl4O9ciuQNKdtka3aZo54WGgg
QrSa3SMkjEjoMVmuUIo3LNEBLeL4qNv1cUZ8mecy+aSUvWhESrtjC8GUwny5
PL0mg+9l0ulIFVkBsEgCLibvs23qCjD3G91JOFiRul77tfvhCyBU5ZlPTExl
xdg07A6zHzIpTg1GKgqCRJwYiUCYIBV69dm+H/ErjZ2jMZm9gO2U7/M60huI
KC0ekiAJPfNmbThHEEUQ5EN2ZTmNQBOnsVzwVwQYPPJxtqDbDEA64HhT6E/K
t5E4EOhWsfQnlGRwHuZgsLwm2SBEAdFCBJCS5c4uEatQaCcWnyO/tAdE5pIj
8OKQK56LUFRKkpsFY4WJq5QkNBPkYRMEvhTPF6DPE0po9FbNfmvW5kXjodq8
KoCJOKCl4IVwSFWSR5ZAqsAELMQH5hWnORpEIasqDxuVLAJxNFozbSX1r3bx
O6Ev19FtVWH7dF+t0K9GTQu0KkEMJN7WjUf6wIMwdCT3vEu66M0mKZ2KMAKr
6VQVgHczF/2n3YHjTD9eql5neGch1Flf/lT/S0rgLapVt2K2Cqlgu+MjYRmQ
VFYon4AC2poCtrBjQmlCpbGRBer6MEyI/lMJYtg4KS2m6nL2ZcH2jU1bj+4D
6vN257YJvsHcUsVRQAET4zXwOYbfPyBs662Y4yBPDH/Dat75jGdGs3y8SZrW
JywY8FAg7ul0PlUP4lSNnmGc+Qb9JWRZcxYmek9UfdTlBjYpqdmZwHbwlSIh
ngXj0CLzsrWdNR7DAgBc9szZIa4dl7GCs4oMGVpteg0naM8b92D2PJCnUcZm
kmIltDNKlJRVxAEYH4q/bDYMZqSzbB1R4qAukH06FeWBmwVfD/sWBLzr7YED
qc2pPfvHrK/kFoOw91YS5g7M8G+Qc3c28HLYCV/euIBMWPaGRgtAgfG3qI5j
yaQn9XpfjZpfQN5AldLX3ZRTsuob2kZ6MgmWEtrS33Fn0OklGBQKe0huylQz
Vi6nmNexqWzqquAYxA6DHFOgQ7ctaWhO74HUk9gWb09KDqXNycpitaW9iiwy
RZm1XNa8H4TmapFTApKkCxxdJJdW8mHtCmF0JsP05Gkw+OEAz+cX5Rd7qSUN
28OCEcfWX+zN7+HvmgcfNeuV/WIvcWmej3BtT6oOX+z5yHrv7WDwl7/8ZaBZ
/e3/Ph3Jf5/2flz7+I8kEPfoX//jPv694fHo3/DjxsV8Gi/m0xsXEw/6gZFv
ftTvmye+bhHnjE8N3xE/KHdZbu/JGPLjvvwAGqFcnxjzQW8h5EF1RR8m0dbq
dvCLmdwZug5lqakLeMYDGDV4rlpalkm1cT4+yiouv27YuLJvWwiaiGEX8RcI
Cx8naICxxwZq4iC5zrML28Uhovv/5HyaRE28VDTVCmmYgnnThLO09JL3VbUV
COgW+WoDwT37OHcl+pkrDscNymFQeNKzkT2/vz0eBevhWXFYfYe/hSApg2Ap
b63puWAyyFRpWBEHWuT6d3Fm2zUQtobV8tx6/y53EZOWmuWDuU+y75KUgVDV
CUknPkJ+4TjGJ4AJkOCjyqoe0lJBqGYL/XMlSXioBCCMb1rKwHIlw0MbiS0v
H97hGEWS6YL5oqE3/L9jxzHe5Rli+vrk6mZ6GMKpZM3LeZ1ILEVJL4IViJ86
CnX1gRrUA6XIxF/nHzZY23mIvEwlrwV5UZMfuQUZmbOW6iAIMoDHc5twVHqz
N7j/8d5AYFOQCu8crrGX/Jbu6cP+48Mu48Ne4sOO4WYD/3HmXwzPB3f16baV
vX5ooukv8IqiUP/vFf/OXtE7xU+U4D4nMJioM1kmBLZhaEZFlXZRs9orLudM
hya0I/j4vuKgnGLjVksl8gwhYZh5Lv0UOsXMAu7lVINP2FFGFdJf3Kbz9m0H
W6WmYZKllvGW7E1q6peiPirZws8//dVJzoYMlQ/FJW6iFBIFfk4ctV8nbB+3
IUgcScW7FBqjBJQGLMNOwck92SXMG/ylx/0m9CNxLW4r9uvn1aK4L2kace/s
5bPNodgxb4TUPacs8bvUWtUtjzn63zkcCLZMypar5qDHPL9oKVDmClDVlpn4
MEphFbbLKxgzUBrkLqKa2PskJBGXnCB2ciXYXvI3nNdtJN2xNtzgxfkjmyaA
H8KNHnF9Zo7m8+uqym5JvGJ+bcf+/cO9oZi5R9I0sJu72lGgry20yutLQRiz
sEnd4coeXRn0wOdVy5jb7NGFuwj8SN+4qYAlx2cEQqFS+GIOJ4fPngbeSJ7P
BIZq+onZuFrZkEjYRYVbx9PJ4dPR8ek+gV6hVncXsZ9NfVwP1ePSJUuyj2+F
W781DoCAXXUZvZ6kdeWwirZocsSaXSYrZC1TKP+8ldiTYN34QzIEXjjgAyoO
cu1XxMR46SnWkj96njj8pm4Txl8dIw8CJ5fxI8LOEIEH9inmDhoZkFBXCgjx
/6zl7piGGjKcbXxKsrPqPqmto8HiUbIOwpoHWB6SC1SsfkONNsI+n/9lLBiw
HiYkPKQtOd0Yu4hIFAxpCcXMmvrit4cwktWKjbqWfQwVy2l+xETcQMJOAmKi
TUPHR+dDc3R2PAxVk9PJq66VaBwa97TkwpUowo4MkxmlQ4JLq9kkTHxhS8rY
Wk4ddBEDywrv7jChftMLMy+SSwLZNDFNGrYVPxw7VF4ZvyQNmJNd7Pf2hDtL
iLAzGQjuu+mMjZZxNjSAGoooa96B1k3uX1VtkYkWUTZq1dbkTyQ6wm+f0iZ5
qKnPtXTUAqp1f3AywOzIRw05MxltxK+SQooZrYYDt009FNFWZfRlVdsprvPv
B7MaXr2ebG6z0nDii/CDwVHXteghtyTUpXKvYUYW1e25iyHnMonL33Ch20k8
A/W+fW/ss5EvpaJ/+/ZgcCYUPTCvfHEPg/dK/1pFl+aQJIAOLlpQLr3pFQr8
FCfALYWZXNRWa/C3zk8mbn8sJXivmTN7QZli9ma7p4VeAje8touq4OqcTO/l
hHPRXDCV8G9vgqDnGzsLfoKlEj+oQcKGxLcZPTbfTKb0zwnljJ9o596ehIpS
JIPlw4rZgYQU4Ay3r/KsWWiRJepoIC94+/74lPBbx88eieUy6Szn+VmrFzZk
VUO+RMsJgq8se/3cLSTapX4jbwAuyXsqIuLuPkqbcvMjBZQ2w5LOdjQFbk1z
q6vEcJ/glP9XZZycAAR+XxGnR67dHjQb3G50Q9E6Ihx0K65QcsvI8Zdnd558
eeb7k/ajdhHAMGxkY5uSiSHucTsR0/vBmDQfTK/E0PbIPXGUDZHe6Ea9tJZa
2bPJ/oL53CxbaoaE5U3cksoRUxObxQpelAzWuTWP5+H6XuHx//WzstfhF5ym
bBRZMf4PtjRrtStNW3vip5MSokTWDyavo4BGIQcR4O5uUm7Br3IXWJWCNUGG
oWDOEXfgSbHC9XBeb9CJT4cXsMWyRifbw4KkZbGD1rVNilGTL7lWLgHfhh5N
tLWsse/feY6cgCOceGrI9HumZUNt6VLXYd8kabPJp6iYyELzcHwYY0CoZZFT
A2RPeM5aaFwPK3oEkiVNIml/5iT1iM19g8TCRh4iFib21HVb0HVpxNMuLG6/
JBkhxg+ZM1yFBSIqo8oU99ZlNgsONDaRYlN7FQmY26NTPiigXMH0L0Lbc1Xv
w5U6n/r8wDZZljDD+3ednXj/Tqubrtv0Okh2qKlGzPMlVBdejRsP4uY3BZRx
ZBfaFkR8Q2XUZ0b1UZ5DDdaQTv34KnjRkdbLeiBtSPwSd7pqmZ+IY4vIy5N8
zhtqit6iHKdFWZZIMFkwfPmVH6SmIJaTYMSkehMx/DK3V84LrO94uX37V2Pf
Kv28Am0rihp64noopcqqddBoFUlyCQsoG/lWKvudqF7l2qmQ2lBjJ5/BIQtl
f8NQsGt+MmmG9A3QnV3WgnORl6/jQqPWGe+E7L6ORJZLm5OiPkGPjZ/kUjiU
zqNpF+Mf2cZ3zz+ZHu0LmwVv016oCdsitEi7oYLH/i6n9nhtL5S4pCBYxz12
NV3IIsfTp1HIWljzdVLkmTd3nLDgVm5lskfrcSVWjVAIdojKZa/K7J3I7duf
BWT2PIoaeM2vEBln1VXPs8HgZt8xsNGBqSN+B3ZCNHRZFZdWEyIIsl1ndJ2A
6CRYFK7vNlzeHQzidfB8mfSZXwkw4ADSb433wTEQF2wZ4/qYFVy5uNAeZwtF
Sn2LvrfJkYUQSLWhU1IDJhOnhMBqvrlu4cNod7dIg4deuxW/KBG0et6byekD
lHrS6BEQFkvDkHlGuIn7nBmvPydgP5Ju5zXpQ9Q1A9wura1dFXfYa+9f9l72
Dfm+9YbglOAK7hBLpJJE7zW7uuu5+57AgGAdMG2OMcpGQwZ/LIw9DE/ZDDvL
15nz+PwELZ3PFaTdKKF/0FGcqyNpe/jSAptkjHqunI/4464zhk78Rj+/5gcf
Sj+0RC3k9w3/b+j2j05vULCR1ckVV/pzb01575KhyWCVmFnX7p8p3S6pyTg6
4yEBpMqOL+F53tjLpGgZ0CUXfNhD0kvtcqbgggd23FxQ9pr4Yx5SQwm1yPl1
xEkuYolahxAh68mhxtli7o8tXFZ5FnXhE+MVbOK9VcI4ttt5xyrOemB/ED2u
FSUCWUMHvxizDbIPBlPtDiRjyM3BeFX6gznlPH9AOWRFxuyqAzHMxHBpyZnL
6TddQ6p5MJLzFq6djaJiJ0nk1yeTU/PzT/+V/PzTX5kDRRCbJ7hkulYvHdmP
KlmZuR/grzP8/9h846WcT8n43ld6Rvz612enYW/gOC1Tkg0zykwWnOoUrEAH
DD2PJT7kDj/txLNv0qLlUwOXIGM3pO/C0CQgJ/OJnoCoRObr6cbEkByIQnKf
Avtjt0JKO1GScrbmae+FeUm5sJcdBOzoF83Qz7F9i1uAJtvj3w/j31w+fPDh
8qHYzldq/p4KNW4qHn56U8HsR9n9j9jyrvujT2X1u6pWd8yP4/F4sxLk710/
7R3+383Ld25Y6p3+Uo/Pzgf0aKg1fRrthdf645ffcN3r1YuX93TMbq273tR/
Nub9k7lhUeZPWzvbvkJD3ED/P3Wbmnz9S+lvbqC/uXZP8l9YEwlNXPv6+DPF
b99Gh1Y08qCKSWc+ExfaFMOL/pC1ntnVDCqDgpfRSdtNSNDrGoZ3TVvnu+Ak
A9S9yk1tCZSEjgDrGxFWlvk1HRhDDDmCF7Uy9lp5ObKXxmTpbu6vN9QytQlw
a3TvlbQlkt7RbGfC1Q4xFXJ2kjSfYxg93HPAuV9qFpTfQ/kd/8w4gnD+Ur/v
RsMJ3/gyobwHo0dwy58f4tVIySvqGYkMGX8Cgg8nKE2jHhafhpY2UnmbxsML
RFS4q1ncWdkddgxRuT/Cq/mG2ic4PVmiR7EFyEOlh2e3+e+BcTjNFq05kgOl
freFDvsUa+nqJ/c+UxMv+aApZsraMmPTS8gp1COn0wMzCadpNV+VcGNMu+Ki
KvkhQ66uEdAjCcI4J+hBqkuWHYxRnF2Gokx4AnPSCeeNg7yYekZHvsDStqwJ
t0n07n0X6ZEcrg2jhUX+VkMali4fbOmKf8mgvia/NYpHvHw4RNjiAibsJFqj
3+kIlzgy7kk6J37qUN+ediX1dUdCpV4HccI2iQ/Xrk9zLBGbD6LaGAnHaAEy
aDG6o/kWv3ezRnYoTalM6txbKV+uCr0OKx/5/2IuaptYB6+7O873WHAPVCJV
Gm2Vjo8nUtdBLXBI5M9tnm34ACc/yMrxDn2SehEt82Zd8pmoTiduZgVHtStf
Uv57MMbc6j5UET/1ASLsfyRD40btHfc/lhfDj1CxoAGz9Qpx4UFHLLroSeJb
46TdO5xZ6tktsmwU6VBaY5cIywSqxTR7lJzlJD4Xx9z2vmlU/V4APxcfCOiT
QuxEvw7iLYRUO6V6KSBEaulNV13jY3HiTdzrnL2g2IEC+hBiXFGotoQi2VXU
cmLTtsaEo/BBFT6M3i0vd3Iwg/r8h1ysSGJtCK6KOfJsTX26kStTxnQVUjkh
Xsce7UZ3xSnLBlHrinRonte0JSmPitPtm0GPIMrrlXaoLA2du1Lon7O0CNrY
tT8BLUqZcH6AP/fSlY6no4LroRsLSrhKPqLEQ91wa8bQqLKyzQL3enF6PzXG
oejm2XstBggjf/ihuQec69ol7ET+vU/399t7OzC18X0YL9iMr/BDIJ8k3jHN
I5nDx37Nvb3HwOqP6LNVj895RgYzZx18oUNC7tEdfoIebejk4GMG+I+a+rEi
fVx+vPHSozu4Ft0m3k5lZdu3rr/D1uKErMU1j0R1+I0e6O5J/MVLpSu6/EfN
rMrWOzaSPb5RhjFEFj/8P/+5eeXnf//vj7ikfuAfOw/DzYYB+/R8jcde3SB+
RzsWfx6t/m9b2/aeuBdqugFGtrbwceu7RpX/tqV+FGV7tNxedd9Xf9QepuYJ
252NuQ2doV4l5Rd7D/b8ZWPuPJrVj1+U/PEdJ3nmbU/AegqxlVSOr6VmggzY
ArS1JIkVN/hZN3Z/WpkNkZqGZoWP2Joa/U6Xb9ohVM/Kh20qXyUJwcvmuj7u
2UhRRT3xB1msxxz9Tqk9acpxdqguDQZ8dTP6pr+oC0vzBNh/+lpOKl8fl2nd
wxNdQpIdMQh/DqR3+iV0g1wfAzPMu/72oW80cJX2MKiqMcVq7+ai9ftQ3nd0
0D041oKK8U+mR/I9LYT1jAO0V1iACPk8qUoJag85Bo884iQG1wncgnOYHo73
O2CE9HqGHlSkLgG/sd45Za4n9zunXva/FIKV907W9r7hIhkH3zaVlEmxdrTJ
WXWpmdnu6PLmF0gSLt6zn8+uS8dov9VZnVcEn76XBmfQhiuP8ZlpGoCapODY
bZHFR//GVPKbXnt7KN+vev/uPIzsF/L+XUhKU7wwoaqB//5CAA3cQCqlcrai
bDcEZ/g01DJ5ky8ZNqy6Yqv2OX3lbHg9fK2Fcw+0o1kNkCtL9kdUwnZ23Bvq
xrpDRhj2/Ts+7CIHbeJvRPjPEul5HARPC+b0MvdHcsJpGAL5Ktzx6cjoACYf
zGI5802qWe7qdsV1sPCBrSjRR01HZ0VSRqXGjapes8VFxrpaA6ThAjDUqsIw
lJh8VSCzo2o+j7sRtG61CtCvX62JeMe5nqlvG9cWnl7VcRjVzPgYVf7nVjrA
o5JRLozNLxaNxjBjHbdI6gur48bfJxp2Wm0RvEvN2I8Wvljh4mqXVrmiw9s0
BIc92iJl4CK4+sTxSR4ybz4B4Kp5c5V0INm34j0cT7j40uRshre+QMSMOa2k
GWNnKywjJcHtMGYd0hjHmFbN2cybvg+nJAJ7QmTVRXARnOHv7MyiWqimCkiZ
u1Gp/sLSqkJBrb5Ysfne1hVHmiTaMAEEPGH/82W7HPoO/i3vFQqefiu/1V4l
8CTTr2atyBUi1FpsRnRGv9mzvWRt1TnvBfIfkSzjXPa2s+JDg9xdLHGTl0r/
RcOInPrJM0u0p3CEOz/oCzjdV1CU710DN2eNMjI6YvCH20t4/+755Fu2Ka7X
PbI7Lqev8YqE6AwBFBBJOAXAIEwbfSbyyUS76fO6j32S4D6XIw39gDD6CBq3
wtd1VdOhH+1Ua0v/Dc6xeRE+5slyFjhmqG2sa+ZjwnSfy+RvnhRJI983ImmM
F9s5VGk6lqMbpMJJ154oGh4tWjum1toIo6rFp23F+HtdpSv+Gz2d1ilX4tp8
slzpd9uoPS807vQ6jsL7G7Lqmz7aUj6ZK5/HjJtyfEYlau7zuRRhNHSYu5ji
/jUY4jzNqaXK965+Ys41w7JdLHpyxA8cT04nuytJ4UthdJSmrOTJJHzMiQ7G
EXCnQSbp67K6KmwmH1t0gx8OJLNqsy/25knhuPaKB7lXMJ+1JBTXPPS/+FT/
d3NcAAA=

-->

</rfc>
