<?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.29 (Ruby 3.2.3) -->
<rfc xmlns:xi="http://www.w3.org/2001/XInclude" ipr="trust200902" docName="draft-han-anima-ai-asa-01" category="std" consensus="true" submissionType="IETF" version="3">
  <!-- xml2rfc v2v3 conversion 3.31.0 -->
  <front>
    <title abbrev="Considerations of AI-powered Autonomic Service Agent Communication">Considerations of AI-powered Autonomic Service Agent Communication</title>
    <seriesInfo name="Internet-Draft" value="draft-han-anima-ai-asa-01"/>
    <author initials="M." surname="Han" fullname="Mengyao Han" role="editor">
      <organization>China Unicom</organization>
      <address>
        <postal>
          <city>Beijing</city>
          <country>China</country>
        </postal>
        <email>hanmy12@chinaunicom.cn</email>
      </address>
    </author>
    <author initials="N." surname="Zhang" fullname="Naihan Zhang" role="editor">
      <organization>China Unicom</organization>
      <address>
        <postal>
          <city>Beijing</city>
          <country>China</country>
        </postal>
        <email>zhangnh12@chinaunicom.cn</email>
      </address>
    </author>
    <author initials="J." surname="Zhao" fullname="Jing Zhao" role="editor">
      <organization>China Unicom</organization>
      <address>
        <postal>
          <city>Beijing</city>
          <country>China</country>
        </postal>
        <email>zhaoj501@chinaunicom.cn</email>
      </address>
    </author>
    <date year="2026" month="January" day="16"/>
    <area>Operations and Management Area</area>
    <workgroup>ANIMA</workgroup>
    <keyword>Internet-Draft</keyword>
    <abstract>
      <?line 54?>

<t>ANIMA defined Autonomic Service Agent to build intelligent management functions into network devices, and could interact with each other through a standard protocol (aka GRASP).With the rapid advancement of Large Language Model (LLM)-driven AI technologies, there is now a potential opportunity to enhance the ASA to be AI-powered, thereby elevating the intelligence of device-built-in management functions to a whole new level.This document analyzes the impact of the AI-powered ASA, mostly from the perspective of the ASA communication protocol.</t>
    </abstract>
  </front>
  <middle>
    <?line 58?>

<section anchor="intro">
      <name>Introduction</name>
      <t>The ANIMA provides a vision of a network that configures, heals, optimizes, and protects itself. An ASA is defined in <xref target="RFC7575"/> as "An agent implemented on an autonomic node that implements an autonomic function, either in part (in the case of a distributed function) or whole.</t>
      <t><xref target="RFC9222"/> proposes guidelines for the design of Autonomic Service Agents for autonomic networks. Autonomic Service Agents, together with the Autonomic Network Infrastructure, the Autonomic Control Plane, and the GeneRic Autonomic Signaling Protocol, constitute the base elements of an autonomic networking ecosystem.</t>
      <t>Large-scale network models have attracted much attention in the field of artificial intelligence in recent years. They integrate the advantages of network technology and LLMs and show great potential in many fields. Especially for network operation and maintenance, it is demonstrating huge enabling potential and providing innovative approaches to solve increasingly complex network operation and maintenance problems.</t>
      <t>AI-ASA can achieve more intelligent management functions. Embedding AI-ASA into network devices can enhance operation and maintenance efficiency with LLMs.</t>
      <t>This draft analyzes AI-ASA vision and potential functions and describes the scenarios of AI-powered ASA Communication between Network Devices and Network Management Systems. The potential new requirements of GRASP are also discussed.</t>
    </section>
    <section anchor="conventions-and-definitions">
      <name>Conventions and Definitions</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>
    </section>
    <section anchor="background">
      <name>Background</name>
      <section anchor="definition-of-asa">
        <name>Definition of ASA</name>
        <t>In <xref target="RFC8993"/>, ASA is a process that makes use of the features provided by the ANI to achieve its own goals, usually including interaction with other ASAs via GRASP <xref target="RFC8990"/> or otherwise.  Of course, it also interacts with the specific targets of its function, using any suitable mechanism. Unless its function is very simple, the ASA will need to handle overlapping asynchronous operations.  It may therefore be a quite complex piece of software in its own right, forming part of the application layer above the ANI.</t>
        <t>Autonomic Service Agents, together with the Autonomic Network Infrastructure, the Autonomic Control Plane, and the GeneRic Autonomic Signaling Protocol, constitute the base elements of an autonomic networking ecosystem.</t>
      </section>
      <section anchor="emergence-of-ai-powered-agent">
        <name>Emergence of AI-powered Agent</name>
        <t><xref target="I-D.rosenberg-ai-protocols"/> Intelligent agent, as an important concept in the field of artificial intelligence, refers to a system that can autonomously perceive the environment, make decisions, and execute actions.  It has basic characteristics such as autonomy, interactivity, reactivity, and adaptability, and can independently complete tasks in complex and changing environments.  Intelligent agents can learn and make decisions.</t>
        <t><xref target="I-D.chuyi-nmrg-ai-agent-network"/> Al Agent, an automated intelligent entity capable of interacting with its environment, acquiring contextual informationreasoning, self-learning, decision-making, executing tasks (autonomously or in collaboration with other Al Agents) to achieve</t>
        <t>There are a few examples of AI Agents.</t>
        <t>A travel AI Agent that can help users search for travel destinations based on preferences, compare flight and hotel costs, make bookings, and adjust plans</t>
        <t>A loan handling agent that can help users take out a loan. The AI Agent can access a user's salary information, credit history, and then interact with the user to identify the right loan for the target use case the customer has in mind</t>
        <t>A shopping agent for clothing that can listen to user preferences and interests, look at prior purchases, and show users different options, ultimately helping a user find the right sports coat for an event</t>
        <t>AI Agent in 3GPP, an automated intelligent entity capable of interacting with its environment, acquiring contextual informationreasoning, self-learning, decision-making, executing tasks autonomously or in collaboration with other AI Agents to achieve a specific goal</t>
      </section>
    </section>
    <section anchor="the-vision-of-ai-powered-asa">
      <name>The Vision of AI-powered ASA</name>
      <t>The AI-powered ASA provides more intelligent operation and management of network devices to achieve the Intention-driven network and Auto-driven network.</t>
    </section>
    <section anchor="scenarios-of-ai-powered-asa-communication-between-network-devices">
      <name>Scenarios of AI-powered ASA Communication between Network Devices</name>
      <section anchor="general">
        <name>General</name>
        <t>The network devices to communicate with other network devices through anima's interface.</t>
      </section>
      <section anchor="possible-examples">
        <name>Possible Examples</name>
        <section anchor="ai-agent-based-router-for-automatic-congestion-relief">
          <name>AI Agent based Router for Automatic Congestion Relief</name>
          <t>In the automatic congestion relief use case, the traditional solution relies on built-in intelligent modules in devices to implement traffic rerouting via traditional protocols (BGP-LS/BGP-RPD). Device interactions are constrained by predefined protocol rules (e.g., policy triggering based on fixed bandwidth thresholds), lacking cross-device historical data sharing and AI model collaboration. Policy generation depends solely on local TOP-N traffic modeling, unable to adaptively optimize based on real-time traffic patterns.</t>
          <t>When AI-powered Agents are introduced into network devices, AI-powered ASA Communication can be established between devices. Devices extend BGP-LS to synchronize real-time link bandwidth and TOP-N traffic characteristics. The AI-powered Agents dynamically define congestion thresholds based on traffic data, replacing manual threshold configuration. Upon detecting congestion, devices use the GRASP protocol to negotiate AI-generated policies (e.g., dynamic adjustment of Multi-Exit Discriminator (MED) values) and route traffic precisely to lightly loaded links via the BGP Routing Process Daemon (BGP RPD). Reinforcement learning is applied to dynamically optimize policy parameters during this process.</t>
        </section>
        <section anchor="ai-agent-based-router-for-automatic-network-ddos-attacks-defense">
          <name>AI Agent based Router for Automatic Network DDoS Attacks Defense</name>
          <t>With the evolution of attack forms, the Distributed Denial of Service (DDoS) Attacks present the features of short-term and high-frequency outbreaks, and the attack peak value keeps rising year by year, imposing an extreme challenge on the defense response speed. In response to the above attack problems, this document innovatively puts forward an edge defense architecture: deploy attack detection functions to end devices, achieve second-level flash defense against DDoS attacks via intelligent service traffic monitoring, and establish an autonomous network DDoS attack defense system. In the meantime, rely on the AI Agent based Router to support the second-level discovery and real-time interception of attack behaviors, so as to strengthen the network security barrier.</t>
        </section>
      </section>
    </section>
    <section anchor="scenarios-of-ai-powered-asa-communication-between-network-management-systems-and-devices">
      <name>Scenarios of AI-powered ASA Communication between Network Management Systems and Devices</name>
      <section anchor="general-1">
        <name>General</name>
        <t>The network controller communicates with other netwok devices by the anima interface or protocol.</t>
      </section>
      <section anchor="possible-examples-1">
        <name>Possible Examples</name>
        <section anchor="coordinated-ipv6-monitoring">
          <name>Coordinated IPv6 Monitoring</name>
          <t>In the current IPv6 end-to-end traffic monitoring scenario, traffic data collection and analysis rely on manual intervention, while the large volume of live network traffic data results in high resource requirements.
When AI-powered Agents are deployed in network controllers and devices, AI-powered ASA communication can be established between IDC controllers and edge devices to enable hierarchical collaboration.</t>
          <t>The controller's AI-powered Agent module discovers network devices via the GRASP protocol, initiates multi-threaded real-time collection and monitoring of IPv6/IP traffic data, and performs preliminary analysis including flow pattern recognition and IPv6/IPv4 traffic ratio trending. 
Concurrently, the device-side AI-powered Agent collects customer traffic data, decomposes traffic distribution characteristics to identify high-value business scenarios, and synchronizes these insights to the controller via the GRASP protocol. The controller's AI-powered Agent integrates provincial-level traffic ingress/egress data to construct regional traffic matrices and uploads preliminary analysis results (e.g., internal IDC traffic distribution, inter-provincial link utilization) to the IPv6 end-to-end monitoring platform.</t>
          <t>The IPv6 end-to-end monitoring platform leverages multi-dimensional data models to conduct in-depth analysis on the uploaded traffic data and preliminary results, generating final operational decisions such as inter-provincial link bandwidth expansion plans and CDN node deployment recommendations. These decisions are then disseminated to the controller, which issues configuration instructions to the device-side AI-powered Agents via the GRASP API. Upon receiving the instructions, the device's intelligent module invokes relevant interfaces to adjust server resources and verifies operational effectiveness through self-monitoring threads.</t>
        </section>
      </section>
    </section>
    <section anchor="potential-new-requirements-of-grasp">
      <name>Potential New Requirements of GRASP</name>
      <t>TBD</t>
      <section anchor="the-interface-and-model-extension-for-prompt-with-ai-agent">
        <name>The interface and model extension for Prompt with AI agent</name>
        <t>TBD</t>
      </section>
      <section anchor="defination-of-option-for-ai-asa">
        <name>Defination of Option for AI-ASA</name>
        <t>TBD</t>
      </section>
    </section>
    <section anchor="security-considerations">
      <name>Security Considerations</name>
      <t>Uncertainty of Current AI Technologies.</t>
    </section>
    <section anchor="iana-considerations">
      <name>IANA Considerations</name>
      <t>TBD</t>
    </section>
  </middle>
  <back>
    <references anchor="sec-combined-references">
      <name>References</name>
      <references anchor="sec-normative-references">
        <name>Normative References</name>
        <reference anchor="RFC2119" target="https://www.rfc-editor.org/info/rfc2119" xml:base="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.2119.xml">
          <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" target="https://www.rfc-editor.org/info/rfc8174" xml:base="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.8174.xml">
          <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="RFC8993" target="https://www.rfc-editor.org/info/rfc8993" xml:base="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.8993.xml">
          <front>
            <title>A Reference Model for Autonomic Networking</title>
            <author fullname="M. Behringer" initials="M." role="editor" surname="Behringer"/>
            <author fullname="B. Carpenter" initials="B." surname="Carpenter"/>
            <author fullname="T. Eckert" initials="T." surname="Eckert"/>
            <author fullname="L. Ciavaglia" initials="L." surname="Ciavaglia"/>
            <author fullname="J. Nobre" initials="J." surname="Nobre"/>
            <date month="May" year="2021"/>
            <abstract>
              <t>This document describes a reference model for Autonomic Networking for managed networks. It defines the behavior of an autonomic node, how the various elements in an autonomic context work together, and how autonomic services can use the infrastructure.</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="8993"/>
          <seriesInfo name="DOI" value="10.17487/RFC8993"/>
        </reference>
        <reference anchor="RFC7575" target="https://www.rfc-editor.org/info/rfc7575" xml:base="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.7575.xml">
          <front>
            <title>Autonomic Networking: Definitions and Design Goals</title>
            <author fullname="M. Behringer" initials="M." surname="Behringer"/>
            <author fullname="M. Pritikin" initials="M." surname="Pritikin"/>
            <author fullname="S. Bjarnason" initials="S." surname="Bjarnason"/>
            <author fullname="A. Clemm" initials="A." surname="Clemm"/>
            <author fullname="B. Carpenter" initials="B." surname="Carpenter"/>
            <author fullname="S. Jiang" initials="S." surname="Jiang"/>
            <author fullname="L. Ciavaglia" initials="L." surname="Ciavaglia"/>
            <date month="June" year="2015"/>
            <abstract>
              <t>Autonomic systems were first described in 2001. The fundamental goal is self-management, including self-configuration, self-optimization, self-healing, and self-protection. This is achieved by an autonomic function having minimal dependencies on human administrators or centralized management systems. It usually implies distribution across network elements.</t>
              <t>This document defines common language and outlines design goals (and what are not design goals) for autonomic functions. A high-level reference model illustrates how functional elements in an Autonomic Network interact. This document is a product of the IRTF's Network Management Research Group.</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="7575"/>
          <seriesInfo name="DOI" value="10.17487/RFC7575"/>
        </reference>
        <reference anchor="RFC8990" target="https://www.rfc-editor.org/info/rfc8990" xml:base="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.8990.xml">
          <front>
            <title>GeneRic Autonomic Signaling Protocol (GRASP)</title>
            <author fullname="C. Bormann" initials="C." surname="Bormann"/>
            <author fullname="B. Carpenter" initials="B." role="editor" surname="Carpenter"/>
            <author fullname="B. Liu" initials="B." role="editor" surname="Liu"/>
            <date month="May" year="2021"/>
            <abstract>
              <t>This document specifies the GeneRic Autonomic Signaling Protocol (GRASP), which enables autonomic nodes and Autonomic Service Agents to dynamically discover peers, to synchronize state with each other, and to negotiate parameter settings with each other. GRASP depends on an external security environment that is described elsewhere. The technical objectives and parameters for specific application scenarios are to be described in separate documents. Appendices briefly discuss requirements for the protocol and existing protocols with comparable features.</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="8990"/>
          <seriesInfo name="DOI" value="10.17487/RFC8990"/>
        </reference>
        <reference anchor="RFC9222" target="https://www.rfc-editor.org/info/rfc9222" xml:base="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.9222.xml">
          <front>
            <title>Guidelines for Autonomic Service Agents</title>
            <author fullname="B. Carpenter" initials="B." surname="Carpenter"/>
            <author fullname="L. Ciavaglia" initials="L." surname="Ciavaglia"/>
            <author fullname="S. Jiang" initials="S." surname="Jiang"/>
            <author fullname="P. Peloso" initials="P." surname="Peloso"/>
            <date month="March" year="2022"/>
            <abstract>
              <t>This document proposes guidelines for the design of Autonomic Service Agents for autonomic networks. Autonomic Service Agents, together with the Autonomic Network Infrastructure, the Autonomic Control Plane, and the GeneRic Autonomic Signaling Protocol, constitute base elements of an autonomic networking ecosystem.</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="9222"/>
          <seriesInfo name="DOI" value="10.17487/RFC9222"/>
        </reference>
        <reference anchor="I-D.rosenberg-ai-protocols" target="https://datatracker.ietf.org/doc/html/draft-rosenberg-ai-protocols-00" xml:base="https://bib.ietf.org/public/rfc/bibxml3/reference.I-D.rosenberg-ai-protocols.xml">
          <front>
            <title>Framework, Use Cases and Requirements for AI Agent Protocols</title>
            <author fullname="Jonathan Rosenberg" initials="J." surname="Rosenberg">
              <organization>Five9</organization>
            </author>
            <author fullname="Cullen Fluffy Jennings" initials="C. F." surname="Jennings">
              <organization>Cisco</organization>
            </author>
            <date day="5" month="May" year="2025"/>
            <abstract>
              <t>AI Agents are software applications that utilize Large Language Models (LLM)s to interact with humans (or other AI Agents) for purposes of performing tasks. AI Agents can make use of resources - including APIs and documents - to perform those tasks, and are capable of reasoning about which resources to use. To facilitate AI agent operation, AI agents need to communicate with users, and then interact with other resources over the Internet, including APIs and other AI agents. This document describes a framework for AI Agent communications on the Internet, identifying the various protocols that come into play. It introduces use cases that motivate features and functions that need to be present in those protocols. It also provides a brief survey of existing work in standardizing AI agent protocols, including the Model Context Protocol (MCP), the Agent to Agent Protocol (A2A) and the Agntcy Framework, and describes how those works fit into this framework. The primary objective of this document is to set the stage for possible standards activity at the IETF in this space.</t>
            </abstract>
          </front>
          <seriesInfo name="Internet-Draft" value="draft-rosenberg-ai-protocols-00"/>
        </reference>
        <reference anchor="I-D.chuyi-nmrg-ai-agent-network" target="https://datatracker.ietf.org/doc/html/draft-chuyi-nmrg-ai-agent-network-02" xml:base="https://bib.ietf.org/public/rfc/bibxml3/reference.I-D.chuyi-nmrg-ai-agent-network.xml">
          <front>
            <title>Large Model based Agents for Network Operation and Maintenance</title>
            <author fullname="Chuyi Guo" initials="C." surname="Guo">
              <organization>China Mobile</organization>
            </author>
            <date day="20" month="October" year="2025"/>
            <abstract>
              <t>Current advancements in AI technologies, particularly large models, have demonstrated immense potential in content generation, reasoning, analysis and so on, providing robust technical support for network automation and self-intelligence. However, in practical network operations, challenges such as system isolation and fragmented data lead to extensive manual, repetitive, and inefficient tasks, the improvement of intelligence level is very necessary. This document identifies typical scenarios requiring enhanced intelligence, and explains how AI Agents and large model technologies can empower networks to address operational pain points, reduce manual efforts, and explore impacts on network data, system architectures, and interfaces correspondingly. It further explores and summarizes standardization efforts in implementation.</t>
            </abstract>
          </front>
          <seriesInfo name="Internet-Draft" value="draft-chuyi-nmrg-ai-agent-network-02"/>
        </reference>
      </references>
    </references>
  </back>
  <!-- ##markdown-source:
H4sIAAAAAAAAA91aXXPbNhZ994z/AyZ5aDwjqUnabhs/rRK7qTvxx9rOdnbf
IBKS0JAAlyClKJ389z3nAvyQ7aTptC+7D4kpEgQu7se5515wOp0eHjS2Kcyx
euVdsLmpdWNxpfxSzc+mld+a2uRq3jbe+dJm6sbUG5sZNV8Z1+ClsmydzeSl
wwO9WNRm89fMlfvM6RKC5bVeNtO1dlPtbKmn2k510NOnzw4P/CL4wjQmHB8e
tFWu4xX/4g8mMitf745VaPLDg9AuShsC5r7dVZj27PT2x8ODwwNb1ceqqdvQ
PH/69MXT59hFbfSxuqx6+bXL1bl2emVKCjrH88ODra/frWrfVsdqfnF2Pj88
eGd2uJljateY2plmekLRuYhum7WvIRT0rawLx+p89pPGLlXc47lxq532Kt7z
9Qpb/SCrQ5lr67R6C834Eg9NqW1xrKCPcvfs+d8zPm3l4Szjy7WnNU1uG1/j
Z2YbaOClsb9at+Jv37qGSpFpRwJdzP6NOVe9SBfa4rfqbn6JTB841q3/Sql+
plS+F+pnDKdIXn25SP7X754++9MSHR44X5dYa0PfUtc/vnr+7NmLdPnDs++/
PRZncss7o3548eKbdPn9d99/N9x9mi5fPH/+nJdn05NZ7YNxC1Ov6ORV7Ruf
+SJ0T7N1u7NTV8bHmkEzhZfREWXx6XSq9CI0tc7E6cQtVW6W1n0m7BqvFq0t
cui7MUVh5WY5ePuydVkMAwzwKi2IaTlHmEhwQFlpAq6ttrZZK6OztfLN2tSq
WSNOVmulEYkYrutcdZtTT/Q7rV5fz2+ujma/8D28oWpd2VzpfKNdFqUAhLzR
9crgf7dqIZs697nB62/enB9N8xoKdwAZ1Zhs7XzhV5aycXWjbFDOb7F65RvM
ZXWhfFX5uoE7NDsqwLg1V5K15zdz0YkZYVaaabFTpjAbmBdeyLGDyvAyRIxK
mVKfzdS6h9WIybXaruF+UOZWYUJTzG7XkBKQ18pgvFbsPpgQFykrKhXTi3gj
IL2ZT1TpQ1Ps1LL2pTwHaoXKZPTA/hXsKBuDa6/9Wec2pc3zwvDXY6JX7fNW
pFW/Pbb8+ZGPbjmX+BTe3wDfgYxqYwmpXEr3vtGsdYMV3dKu2pp2WBtd4I+v
GlvaD53XUApICsdqgimWMzV3Iis1kZwWOvzttxQ6Hz8qHdQjDBLXp14K0S3G
QQJgle5d3ME5ohj9qLA/orPHRBkrToqlKl036gkuqLVMBxO3lVvElF20XKh7
7QjoE40oOhQhGckQEtuqEMdBrVroqMA+ggIqyKTQmV2Jtj4RjnHoaCNRpWH2
yRfgm35lZAvbLn6GsRfJJGduWWtsA2aFSSZ3RiFfw8iFuiq0M9E4HPDaOHON
x6OlIb0u6P5XyYUmNHQAh4B65KUF9WY6nVOB7v5+OIPJfNiFxpSiQYnuaci0
hEUUumSIB6Q6+LJuBNdggrIFsOAnQxl2T+ZaWgMI4nJ1Y5c2Y5TvhSfG1Saj
4+yMrqFQuPNOhqyQ56PsgjgN3EsE7925w5SdaAaIEylBWANVViADzQhZYtTv
ojxY5ZTRiAeMUVi2m9N37EJmQq6CHI4YNEE0xAgoqdc6gs26BeJhwEJ0P6yW
wgjByPvWOb+R5KN0hdtAYCN4A5a0oQYyCBswEsIAEBAY739fIM6/gDmDmAnw
I3BCoyKlArtgpdr8bvKAIsqFyUXMNMdD6UQm7tD40yKZJS0Ms+6iz9MkswhR
VB1Z14ChabkEVKKxXn8DKvM+ojNDoCfcDXAWXVt/j79isj2uilzRbA3yTxds
J2kznLO7N+KPN+L10QNHsjAZ1OY/ra2H2JHECJeGQYvgiURZG4LJZxGqEbeb
GAZxsRPCppXfHWCDlCqyUiDn+dub20eT+FddXMr19ek/3p5dn57w+uan+Zs3
/UU34uany7dvToar4c1Xl+fnpxcn8WXcVXdunc//9SiCyaPLq9uzy4v5m0cx
XPdyHTYX863wh6o2DHIdemtIFnj56ko9+zYmAxIv4Kxck3nhers2Li7lHZw7
/mwY4AgEhDunQAzCvSrbSC7CAoxfp5jYZyrq86XOhNO7XH4/HilUnOBmzvtn
KSmR2n38OOlylmakwOwhJp5Sv4MLtKFPw0sABdNhlz1zBT7RxJwqpCDFk6Xp
IdjKi6BtaAU9EL1Fm8I88ixKJe4fWRbECPDyxKZ6EZ9CPQAeGbO1AXtVl0sy
tjpEsBHP6uYMQxIR4EKcqYbQHP2Rsg2ZsyWWKKJdaKFWoIQqgZUg5aGcgYoX
VMb4FappY2qMl7Q86enJ1hYMAOgEisAEICPKY2QB88kaYecysEjn2zDgAkJI
nVHTu8jPlkQiOJJWiCJAeodxlTWRnwW/bLZa4KpXc21X62ZCcC4FW8kBksWw
eNHFeKF30LFeQKrOaBEQ/7/TMmLgtERB0jHcMQ5yn5H8fLp2gfOdjVKDMDcJ
PiwPHwAJR8KlrJmpmi/N5RPg5BI8N1LpKG0incOu4CmIGrhKZmyymXEbCx8q
RQbGJzAmk7SQGKl5bzIqTGcj91pDWmgPWoJrCwepQQhtBgARJhK6FXeTITQ3
qCwo5nDN+XWuK8SJLfo7FNi63FQG/7mmT8y0mg7vWHT1bizjWWKLmYa9iJx3
lRxTaQHs69LneLsR8KLhPlNWwnrzIhp60jkMqluzXywyA6GOArYKBBAmOjVA
UPF+Btue9nXGRMfnsH1j3jet2DhVz96RqHiH5xPF2mAqG5Gf3R6m2JHciEaT
kkw09mTPAXwdVVgUiN1EJ8agmbYXjsYQnJIn0y7/Abq3WEbTDIkNpLciBCjQ
NBRx/e3BF9emqJgD4KsBO4C7SCUQhyPBQezUY2J8Sh1TiW/TzcNETE8RlgVR
Sgy5BmFAIkPZF5ITL7ynJkLnY7+2AYwUmBGidIWnJARVgdJPSthwMt9iGXkl
8pN+T5HySX7T8sJX2JMudL0b2w0i1+ypKOT4xte7HrXcnfYA45GzUO2Wrm+X
MRsKHkeZu6opJiDJpVKVSXmGTXogk4QnSbeNSXvOtJ6ShsjNSbIC1o5Fe9p2
AfEgExYXIUZKF4FFViMqLqBdRYoPKoiBLYwIGZKypQSI2svtUqZopMwVSGkL
1LsIF7gh1SwyxfXAKvLRbgOBEBHrdZSXJHiT0LU3ADb5zeurq/+dQPxDcdhF
1DgM9cBBSIYiR6NT/rNvOuzz8r5Lsc/W+3bFvVLlbonRc/RR+deVJiPBaDki
rlDvrvvUjedMTM137ifKfvNnq4qUlUkC6qgT7vgBYYeWjxlr+t7IrjnH5vpX
IbrMUmemy/9XPgRLfzpNCBjvPx6gIWLXNaCDrg1Lz6N7RgqzIsxhP9emsGaZ
CLTQq35UNoyqZVQf65ESATBzYeHwTdSy7TAyEDL7ftteFerzlnCN2yOl9O0g
zskqEtNg/+K15M7jlXoSo568fH01fXPzNf9cX50czZIxxlQ8SK7IYtEuzSvQ
e+BK18rqO561iPXEzFazCco/MEwAH3BgZSQM+0SwtO85Cdxpa3NBTCDS2hd5
OAIqoVKRoAXtCtO4wYS5sDhyi24QPeArkaHnNJa0U/ZDcAbrigArcSfRayQj
gYomcpH7ek55e3k1vejVJpNJ2LdO0IbhQXoDn+dbqdU3bAdAUkxx0/RTVGzi
1C4m0V/W0sDdZ5dRpzY1JCPaPdCC/mwYEe1RE8C92D0Ja+o0RVaaYNYX7IA/
bF1Fa0vjJJUd3MmwAez73cgwVO++cu4QxS6T3t1cvnO6pLmgsOgm40gY7D0o
sVuA5iW9RJbPaGEgF3G7f6XvviYrv63EsGy3JqhPq0z64GhTYo3VY++tou+V
byxhBFtIjkKHpufYwZXTbhIB6VD0nElwevoelODEsqAvSXmAEU/OT0+O1EYX
rQH5og4ZhyPvqJlf6EsQQegPLkELWDjTALHWpcQwl4BPqn+Eopxo9s8kcFWM
2GsjWS2dJ3RpTAp3lnmx9BxbpHfhFKMgYrqECpnr2zqyCRu6on/2R1Cxh/QT
f6PmTYNgDuw1GBekCd8fhJhNh3ashmSgVKrxbIMa7TvTJ8bJycayL0SfcPqj
fn4oNETqN+pFsCheg3xMIWQZ+SVUPV2yESX9NYi/gOe/C0P9meSocDfaT70z
pgrgMtIPYHuV2Me/EynyUpuA4cXeFsOjKAxcUFxa2uKydTg0mBAvkPdNPkOO
HW7BOrK4VOCdCKk1ObnTUxoaoSwB29hV3/LciVLkq2FFcnLLsIA2jgl9hd91
s6d4IRSPD2+MdAq706/ECALKZpdP5TAHbF2H9bDECukAjFyMrZMx6LvjbBWS
zQZ4dTyYFICVyrSDL7VX4fZYOJq8XziV8Sql29Kg1AZ8ETcirjdjfr/nroS+
Vs7IYitovDs2Ib10cSRoe1SUXMgyft9dF2atN6DOUFbwrJY5N/zAraQqaEbk
BcsgsMBgF7quran/NGW633RNbdIvYFJZbL4U0MaISYV7VGpgUqmdJ0RqoFFk
vnvnbZ+jVK+8r3MCJLZ3drX5mzrv/WBEnKAlKTRkBNxxCrJJr7zvPH0Te7KX
OoQEJN+WmpG98oAI6jwj5RPZROowT9R2bYuYIwo5iiU2lVJmFOyw9Mcl44UQ
vkgAwsIILPztUUKZvU737LPpPwZlbAPfN07XuX+YCmRfSgXOTl7dmzQBRc8d
TSQ6CPhaYIOkaJ9NdT40zPRVuLerxEz7OAr3KHmX2PZTMbtLVvIwChnJqkz3
kg+HILxj2JEnwEz0l6/Pru6wCDkRga8yrTBJFJKiJbyTVwyt52WBejfxNh6n
+VXqjnOSNP3m24FbUy2Kwc632XRCPZC8t9hNEvbLmTm/F7qvqrSdMJT7+7Kj
BvVlPG3tH3Q5USx+p2M3bjZIoov5a8FONmlDf+aTyvuB/smZUCDKBXKR0OWj
EUw8bLZI/j7vEf0pZDoccGx5Jrjt9gUFInjC10b+xOiSKs/F/jHMsYp1Sw8D
GoroOhptRe70CQN3UZqYnIQ9Z2JUPKTXNGQ6CBs5MR4W6YOco05Bd0Fq5JJg
rw3dro+bLxgr30vUckQbgyCH27sQdy5KSafGUTf8jgHCokKqhKmnDafkF5Vi
8n3Mioeqg5qSdiZ9kcRAsE4+I0lFE9fueqt9W/hhHQ11g3lfaZE8Nutk3Vcn
F/HjhYh6kroYZyWu8u7Q41Y8cVhQjtAIoLBRMGXKH/ccVBAcomFQy6PWcYlA
vxY36ljO74XmXZSaX52lMoOn7HYzfCIzzDsO+NRp2K/WcWvjeWxWy3c2KTIk
jcb+S+xtkiwh3rpcEjWHO3YpDYGRUcxyGb+FcfFcLrY6pJE18q2Io4nCIzl3
J7IXZouy4YETWfHXlycpm9+mL4Fiuo+wy0pbqkmxL9k/KpOySs1PkC7dnZ4M
88hho+7o02UkUlI4yAn2eDA4fqJK+59a8uFbl5m64Wn5jvO8SmQBa96OPo5K
mz2bX8wfmAPrHPwX8cBrwR0qAAA=

-->

</rfc>
