<?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-wang-agent-semantic-routing-00" category="std" consensus="true" submissionType="IETF" version="3">
  <!-- xml2rfc v2v3 conversion 3.35.0 -->
  <front>
    <title abbrev="Service Semantic Routing for IoA">Research on service semantic identification and routing technology for Internet of agents</title>
    <seriesInfo name="Internet-Draft" value="draft-wang-agent-semantic-routing-00"/>
    <author initials="S." surname="Wang" fullname="Shiji Wang">
      <organization>China Unicom</organization>
      <address>
        <email>wangsj7236@chinaunicom.cn</email>
      </address>
    </author>
    <author initials="L." surname="Wang" fullname="Liwen Wang">
      <organization>China Unicom</organization>
      <address>
        <email>wanglw97@chinaunicom.cn</email>
      </address>
    </author>
    <author initials="Y." surname="Zhang" fullname="Yan Zhang">
      <organization>China Unicom</organization>
      <address>
        <email>zhangy1156@chinaunicom.cn</email>
      </address>
    </author>
    <author initials="L." surname="Ma" fullname="Lijun Ma">
      <organization>China Unicom</organization>
      <address>
        <email>malj105@chinaunicom.cn</email>
      </address>
    </author>
    <author initials="Y." surname="Cao" fullname="Yunfei Cao">
      <organization>China Unicom</organization>
      <address>
        <email>caoyf34@chinaunicom.cn</email>
      </address>
    </author>
    <author initials="Y." surname="Liu" fullname="Yongsheng Liu">
      <organization>China Unicom</organization>
      <address>
        <email>liuys170@chinaunicom.cn</email>
      </address>
    </author>
    <date year="2026" month="November" day="16"/>
    <area>Routing</area>
    <keyword>Internet-Draft</keyword>
    <abstract>
      <?line 51?>

<t>With the deep integration of artificial intelligence and network technologies, the Internet of agents has become an important direction for the evolution of the next-generation Internet. The connection paradigm of the traditional Internet centered on “location addressing” can hardly meet the demands of the Internet of agents for “business-driven and service-as-connection”. The service semantic routing technology system, paradigm evolution, core collaboration requirements in the Internet of agents, and the limitations of traditional routing technologies were systematically elucidated. It was clarified that semantic routing was the key to realizing the transformation from “service demand” to “resource matching”. The solutions for four core semantic routing mechanisms in the Internet of agents, namely fuzzy search based on tag matching and flexible adaptation, precision-named DNS (domain name system) for “service-domain name” mapping, business-layer network identification based on Anycast, and URL (uniform resource locator) semantic routing with application-layer semantic encapsulation were analyzed in depth. Finally, the technical characteristics of each solution were summarized and compared, providing an important reference for subsequent research.</t>
    </abstract>
  </front>
  <middle>
    <?line 55?>

<section anchor="introduction">
      <name>Introduction</name>
      <t>The rapid advancement of the digital economy and artificial intelligence is driving the evolution of the Internet from information interconnection toward intelligent interconnection. Agent technology powered by large language models is precipitating a fundamental transformation in Internet architecture, in which the Internet will evolve into an "Internet of Agents" (IoA) — a network of intelligent entities capable of perception, decision‑making, execution, and interaction. The central requirement of the IoA is service‑driven interconnection: agents must autonomously discover, match, and invoke heterogeneous service resources — including other agents, large models, knowledge bases, and compute nodes — based on high‑level business objectives. In this paradigm, the core interaction unit shifts from hosts or service endpoints to agents, and the mode of accomplishing complex tasks evolves from user‑to‑service access to agent‑to‑agent collaborative service.</t>
      <t>Traditional Internet routing is centered on location‑based addressing, relying on physical identifiers such as IP addresses to establish connectivity between nodes. It cannot directly interpret the business semantics or service requirements of agents, creating an efficiency bottleneck in the demand‑expression‑to‑resource‑matching pipeline for inter‑agent coordination. For example, when an agent requests "a low‑latency Chinese‑language LLM inference service," traditional routing requires multiple layers of adaptation and translation and cannot directly map the request to an appropriate service instance in semantic form, increasing coordination complexity and interaction latency. Building an identification and routing framework that supports semantic understanding and precise matching is therefore a critical enabler for the large‑scale development of the IoA.</t>
      <t>This paper investigates service semantic identification and routing techniques for the IoA. The main topics covered are: the core requirements of the IoA and the semantic identification paradigm; the principles, agent‑oriented designs, and technical details of four categories of semantic routing mechanisms — fuzzy search, DNS‑based precise naming, anycast network identification, and application‑layer URL‑based semantic routing; a comparative analysis of these four approaches; and an outlook on future directions.</t>
    </section>
    <section anchor="routing-requirements-analysis-for-the-internet-of-agents">
      <name>Routing Requirements Analysis for the Internet of Agents</name>
      <t>The Internet of Agents is an emerging Internet paradigm in which highly autonomous AI agents serve as the primary interaction entities, and represents key infrastructure for supporting future large‑scale societal‑level collaboration. Its central objective is to connect agents, data, models, and tools across cloud, edge, and end‑device tiers into an open, extensible, and secure intelligent collaboration network through standardized protocols and open architectures. In this paradigm, agents act as reliable proxies for users, autonomously performing service discovery, task negotiation, and resource scheduling, and accomplishing complex tasks through cross‑domain, cross‑platform collaboration. The core interaction unit shifts from traditional hosts to autonomous agents, and the primary network function advances from supporting human information exchange to driving efficient and precise inter‑agent coordination and value creation. While service discovery and routing have attracted research attention in both academia and industry, a significant gap remains: traditional network technologies lack semantic capability, and AI‑oriented research tends to overlook the underlying network support layer. This section systematically characterizes the core features and requirements of the IoA and analyzes the limitations of traditional routing mechanisms, providing the foundation for subsequent investigation. The evolution path from the traditional Internet to the IoA is illustrated in Figure 1.</t>
      <figure>
        <name>Evolution Path from Traditional Internet to Agent Internet</name>
        <artwork><![CDATA[  
\`\`\`text  
                                        Boundary Expansion  
Human-to-Human Communication & Collaboration  
===========================>              Human-Agent, Agent-Agent Communication &  
Collaboration  
      Human  
      Agent                Agent  
    /  
   /  
  / Traditional Internet \  
Vehicle   /   Agent Internet   \ Laptop  
  \         /  
   \\-------/  
Human                          Human                              Human  
+Agent    Industrial     Agent+Human  
          Robot

]]></artwork>
      </figure>
      <t>```</t>
      <section anchor="core-characteristics-and-requirements-of-the-internet-of-agents">
        <name>Core Characteristics and Requirements of the Internet of Agents</name>
        <t>In the IoA, although agents possess a closed‑loop autonomous cycle of perception, decision‑making, and execution, the realization of genuine value and the completion of complex tasks fundamentally depend on large‑scale, high‑efficiency multi‑agent and multi‑resource coordination. The core of such coordination is precise matching of service demands to resources: starting from the high‑level business service requirements of a user or a leading agent, the network system dynamically discovers and schedules service agents with the corresponding capabilities, ultimately achieving the objective through collaboration. Realizing this coordination process places elevated requirements on network identification and routing:</t>
        <t>First, the IoA requires strong semantic understanding capability, with the primary objective of accommodating agents' potentially imprecise service demands and supporting demand‑to‑resource matching in exploratory inter‑agent collaboration. Second, a unified, human‑readable semantic identifier framework is needed so that the service demand semantics of agents across different domains and types can be effectively recognized, and the service capabilities of various resources can be clearly characterized, enabling interoperability and precise matching between service demands and heterogeneous resources. Third, real‑time awareness of service instance operational state is required to dynamically adapt to changing agent service demands and ensure continuous real‑time alignment between demand and resource state. Finally, extremely low interaction overhead and millisecond‑level response capability are required, primarily to accommodate the high‑frequency, short‑session, massively concurrent service demand interaction patterns characteristic of inter‑agent communication, ensuring rapid resource matching and response following demand initiation.</t>
        <t>Each of these core characteristics imposes specific design requirements on network identification and routing schemes.</t>
      </section>
      <section anchor="limitations-of-traditional-routing">
        <name>Limitations of Traditional Routing</name>
        <t>IP, as the de facto standard for global network communication, identifies network device interfaces by destination IP address and forwards packets end‑to‑end on a shortest‑path‑first basis. It offers broad compatibility and generality for traditional data transfer scenarios. However, its inherent design limitations become apparent when faced with the low‑latency, high‑concurrency, service‑direct‑delivery requirements of the IoA, and it cannot satisfy the core demand‑to‑resource‑matching objective.</t>
        <t>In terms of addressing, the granularity of network‑layer IP addresses does not align with that of application‑layer service interfaces. IP identifies only network device interfaces or the networks to which they belong, and cannot match the service‑invocation granularity driven by agent business logic, preventing routing decisions from precisely addressing business requirements. In terms of scheduling, IP routing defaults to best‑effort forwarding; while optimizations such as Equal‑Cost Multi‑Path (ECMP) and Constrained Shortest Path First (CSPF) improve path selection, IP addresses cannot express complex service requirements, making it difficult to satisfy the differentiated demands of agent workloads for latency, bandwidth, and security isolation, thereby reducing scheduling efficiency. In terms of cross‑domain coordination, networks are partitioned into multiple administrative and technical domains whose routing schemes and semantics differ. IP addresses lack a unified information interpretation framework, and cross‑domain resource scheduling without complex Service Level Agreement (SLA) support is prone to policy inconsistency and performance instability.</t>
        <t>Traditional semantic routing refers to the practice of augmenting IP routing decisions with additional information carried in packets or configured into routers. It can be broadly categorized into overlay‑based semantic routing and intra‑domain semantic routing. Overlay architectures construct an independent overlay network layer on top of the existing IP underlay to carry service semantic routing functions; intra‑domain architectures confine semantic routing to a designated physically isolated network domain, with uniform routing policies applied within the domain and inter‑domain communication handled through tunnels or application gateways for semantic adaptation. However, the "additional information" carried by traditional semantic routing typically consists of general network attributes and does not incorporate service‑specific semantic dimensions, making it unable to support precise mapping from service demands to resource capabilities. Furthermore, traditional semantic routing architectures are designed around data transmission path optimization rather than service resource scheduling, and are not suited to short‑duration, high‑frequency, heterogeneity‑compatible workloads.</t>
        <t>In summary, existing technologies suffer from identifier schemes that lack semantic expressiveness, routing decisions that are not semantics‑driven, and insufficient adaptability and cross‑domain coordination capability. They cannot meet the requirements of the IoA for service heterogeneity, dynamism, and high‑frequency coordination. There is therefore an urgent need to construct a complete identification and routing framework for the IoA that integrates semantic understanding, heterogeneous compatibility, dynamic adaptation, and efficient response, enabling efficient inter‑agent coordination and optimized resource scheduling. The remainder of this paper focuses on this core requirement, analyzing various service semantic identification and routing approaches in depth, and deriving customized service semantic identification and routing schemes for the IoA based on the analysis and the characteristic fit of each approach.</t>
      </section>
    </section>
    <section anchor="state-of-the-art-in-service-semantic-identification-and-routing">
      <name>State of the Art in Service Semantic Identification and Routing</name>
      <section anchor="overview-of-service-semantic-identification-and-routing">
        <name>Overview of Service Semantic Identification and Routing</name>
        <t>Service semantic routing is an evolutionary advancement of traditional semantic routing. Its core innovation is embedding service semantic information — such as service type and QoS requirements — directly into packets, transforming the generic auxiliary information of traditional routing into service‑specific attributes tightly bound to business logic, and encoding service demands as routable identifiers so that the routing system can directly interpret business requirements. This represents a fundamental shift in routing decisions from location‑based addressing to service‑demand‑driven forwarding. The objective is efficient and precise service‑direct delivery; the architecture can be flexibly adapted to deployment requirements and business scenarios, yielding a variety of implementation approaches.</t>
        <t>Service semantic routing constructs a unified semantic identifier framework that standardizes the description of interfaces and quality differences across heterogeneous service resources, enabling one‑request‑multiple‑fit and resolving the core tension between service heterogeneity and coordination efficiency. It relies on dynamic synchronization with a service registry to support resource state awareness and precise instance scheduling, with low parsing and scheduling overhead to meet the millisecond‑level response requirements of short‑duration, high‑frequency interactions.</t>
        <t>The service semantic identifier is the foundational enabler. Its multi‑dimensional semantic properties can precisely encode agent business demands and capability parameters, accommodating the coordination characteristics of agents — imprecise demands, service heterogeneity, and dynamic state — and facilitating dynamic scheduling and cross‑domain coordination in the IoA while reducing the barrier to heterogeneous collaboration. Existing solutions are largely focused on general‑purpose compute scheduling or traditional service scenarios, and a customized technical framework tailored to the IoA has yet to emerge; scenario‑specific development is the key to overcoming current adaptation bottlenecks.</t>
      </section>
      <section anchor="four-representative-categories-of-service-semantic-identification-and-routing">
        <name>Four Representative Categories of Service Semantic Identification and Routing</name>
        <t>Service semantic routing techniques in current industry practice primarily differentiate along the dimension of the carrier and parsing logic for semantic information, covering four major directions: fuzzy search based on resource tag matching, DNS‑based semantic encoding, anycast identification using data plane network IP, and application‑layer URL‑based service semantic identification. Each approach is suited to different business scenarios and precision requirements, together forming a multi‑layer, full‑scenario service semantic routing framework. The four approaches are described in turn below.</t>
        <section anchor="fuzzy-search">
          <name>Fuzzy Search</name>
          <t>Fuzzy search is a service and resource retrieval technique based on tag matching and flexible constraint satisfaction. It does not require users to specify precise parameters; instead, it parses user‑supplied constraints — such as "domestically produced," "throughput ≥ 10 Gbit/s," or "memory ≥ 64 GB" — and performs similarity computation and semantic association against predefined multi‑dimensional resource tags (e.g., vendor, network throughput, memory capacity, storage type) to rapidly filter candidate services or resources from a large heterogeneous pool that satisfy the user's core requirements. In this paper, services are treated as a category of resource, ultimately supporting automated service and resource provisioning decisions in data centers. The core value of fuzzy search lies in lowering the operational barrier for users, accommodating the imprecision of demands and the heterogeneity of resources, and improving resource matching efficiency. The fuzzy search mechanism is illustrated in Figure 2.</t>
          <figure>
            <name>Fuzzy Search Mechanism</name>
            <artwork><![CDATA[  
\`\`\`text  
                                      Fuzzy Search  
                                                                 Information Collection, Crawler  
                                                                       |  
                                                                       v  
+--------+     Query      +----------------------------------------------------------------------------------------+      +-------------+  
|        |---------------->|                                                                                        |---->| Terminal 1 |  
|  User  |                |                                  Fuzzy Search Platform                                 |  
|        |<----------------|                                                                                        |---->| Terminal 2 |  
+--------+    Return URL  |  +----------------+        +-----------------------+        +---------------------+      |  
    ^                     |  | Accept User    |        | Retrieval Algorithm  |        | Registry List       |---->|  
    |                     |  | Request       |------->| Fuzzy Matching       |<-------| List of Content &   |     | Terminal 3 |  
    |                     |  +----------------+        +-----------------------+        | URLs                |  
    |                     |                                                                    +---------------------+  
    |                     +----------------------------------------------------------------------------------------+  
    |                                                                             ^  
    |                                                                             |  
    +-----------------------------------------------------------------------------+  
]]></artwork>
          </figure>
          <t>```</t>
          <t>In the fuzzy search mechanism, the platform first collects multi‑dimensional attributes and access indices — such as URLs and query protocols — from various resources, and constructs a unified information resource repository through normalization. User requests expressed in non‑standardized natural language are then parsed using natural language processing techniques to extract core requirements and constraints, which are mapped to a standard tag vocabulary and transformed into structured queries. Flexible matching is then performed against the resource repository: text attributes are evaluated using semantic similarity algorithms, numerical constraints are handled by range matching, and layered weight scoring is applied to rank and select the top‑N optimal resources. Finally, the access method for the selected resources is returned to the user, while the platform monitors access status, collects feedback, and updates resource attributes and service state to close the fuzzy search routing loop.</t>
        </section>
        <section anchor="dnsbased-precise-naming">
          <name>DNS‑Based Precise Naming</name>
          <t>DNS‑based precise naming is a semantic routing technique that encodes core service semantics — such as service type, functional scenario, QoS requirements, and resource attributes — into standardized domain names. Its defining characteristic is the one‑to‑one correspondence between a domain name and a specific service: the domain name itself carries the business requirements, enabling DNS to go beyond traditional "domain name → IP" location addressing and directly achieve precise mapping from "service demand → target service." The mechanism is illustrated in Figure 3.</t>
          <figure>
            <name>Precise Naming DNS Mechanism</name>
            <artwork><![CDATA[  
\`\`\`text  
                             +---------+  
    +------------------------|   DNS   |<--------------------------+  
    |  http://mypaSERVICE    +---------+                           |  
    |      203.0.113.0          |                                  |  
    |                           |                                  v  
    v                           v                        +------------------+  
+--------+              +-------------+                  | Service Semantic |  
| Client |<------------ | Global Net  |----------------> | Routing          |  
+--------+              +-------------+                  +------------------+

]]></artwork>
          </figure>
          <t>```<br/>
In this approach, the system first establishes a unified semantic encoding rule set, embeds core service semantic fields into domain names to form a standardized semantic domain name scheme, and builds a global semantic domain name‑to‑service mapping table. Service providers register their semantic domain names, service instance IPs, and attribute metadata with the DNS server via Dynamic DNS (DDNS), with automatic updates upon instance changes to maintain dynamic consistency of the mapping. The DNS server, acting as the control plane core, receives a user's semantic domain name query, decomposes and parses the semantic fields in the domain name for validation, performs A/AAAA record lookup to match the optimal target server IP, and returns it to the requester. The user encapsulates the request packet destined for that IP and sends it to the target server, where a web service proxy forwards it to the corresponding service instance for processing; the result is returned along the same path. Access status is collected and fed back to the DNS server to optimize subsequent selection policies, forming a complete closed‑loop workflow.</t>
        </section>
        <section anchor="anycastbased-data-plane-network-identification">
          <name>Anycast‑Based Data Plane Network Identification</name>
          <t>The anycast‑based data plane network identification mechanism, along with the application‑layer URL semantic identification mechanism, is illustrated in Figure 4. Anycast‑based service‑layer network identification is a network identification and routing technique centered on semantic anycast IP addresses. Its core logic is "same service, same IP": services that are functionally equivalent and semantically identical are assigned a single dedicated anycast IP address. This IP serves not only as the unified addressing entry point for anycast routing but also carries explicit business semantics, establishing a strong one‑to‑one mapping of "one IP = one service category." This approach overcomes the limitation of traditional IP, which identifies only physical nodes, elevating IP addresses from location‑oriented to business‑semantics‑oriented. Clients need not be aware of the physical location, real IP, or deployment count of service instances; they simply direct requests to the semantic anycast IP, and the network automatically schedules the request to the optimal service instance via anycast routing. This is applicable to scenarios requiring flexible scheduling of equivalent services, such as compute‑network convergence, cloud services, and distributed systems, as shown by Client 2 in Figure 4.</t>
          <figure>
            <name>Mechanism of Business Plane IP Identifier &amp; Application Layer URL Service Semantic Identifier</name>
            <artwork><![CDATA[
```text
http://IP/ai/chat/       <--------------------------+
Client 1                                            |
    \                                         Service Instance 1
     \ Request                             /
      \                                   /   
       v                                 /
+-------------------------------+       /
|            Control Plane      |     v
|                               |
|  +-----------------------+    |     < ------  Service Instance 2
|  |    Business Logic     |    |
|  | [ ]  *  [ ]  [ ]      |    |        ^
|  +-----------------------+    |         \
|       <------- Response       |          \
+-------------------------------+           \
       ^                                       Service Instance 3
      /                                              |
     /                                               |
Client 2 (IP)                        Business Plane  |
                  <----------------------------------+

]]></artwork>
          </figure>
          <t>```
In the anycast IP‑based service‑layer routing scheme, the system first establishes binding rules between service categories and their dedicated anycast IPs, associating semantically equivalent service clusters with a single anycast IP that carries the business semantics, and constructs a global mapping table. All service instance information associated with each anycast IP is then collected via standardized protocols and synchronized to the service registry, enabling dynamic association between anycast IPs and instances with automatic updates upon instance changes. When the gateway receives a client request, it extracts the destination anycast IP and forwards it to the parsing module, which retrieves service type, compute requirements, and other information and passes them to the scheduling module. The scheduling module queries the registry based on the parsed results, evaluates real‑time QoS metrics and operational status of candidate instances, selects the optimal instance, and generates a scheduling plan containing the real IP and an SRv6 path, which is returned to the gateway. The gateway encapsulates the request packet and forwards it along the specified path; the server‑side gateway parses the packet and delivers it to the target service instance. The service instance executes the task and generates the result, which is returned to the client along the reverse SRv6 path, completing the service loop.</t>
        </section>
        <section anchor="applicationlayer-urlbased-service-semantic-identification">
          <name>Application‑Layer URL‑Based Service Semantic Identification</name>
          <t>Application‑layer URL‑based service semantic routing is an application‑layer routing technique that uses the URL as the semantic carrier and HTTP as the transport protocol. Its core logic is to encode service semantics into a URL field — such as the URL‑PATH or query parameters — and to use HTTP header fields for auxiliary information, so that the URL functions not merely as a resource locator but as a structured description of service requirements. The client sends an HTTP request carrying a semantic URL; the network side parses the semantic information in the URL and the header fields to achieve precise routing from "service demand → target service instance," without relying on underlying IP addresses or network‑layer configuration — semantic‑driven service scheduling is performed entirely at the application layer. Whereas a traditional URL answers only "which resource to access," this technique additionally encodes "what type of service, what functionality, and which version," so that the HTTP request itself carries the information needed for routing decisions, as shown by Client 1 in Figure 4.</t>
          <t>In application‑layer URL‑based service semantic routing, the system predefines a unified encoding rule set that embeds core service semantic fields — service type, compute specifications, version information, etc. — into URLs, establishing a "one service category per dedicated URL" mapping. The control plane collects, via standardized protocols, all service instance information associated with each URL — including real IP, deployment location, resource configuration, QoS capability, and supported semantic tags — and synchronizes this information to the service registry. When the client‑side gateway receives an HTTP request carrying a semantic URL, it first parses the semantic fields in the URL and query parameters to extract core characteristics such as service type, compute requirements, and version constraints, then parses the HTTP header fields, and integrates the results into a structured request. Based on this structured information, the gateway queries the control plane service registry to filter candidate instances that fully match the URL semantics and header constraints, and then evaluates real‑time instance state — load, availability — and QoS metrics — response latency, throughput — to select the optimal service instance, forming the forwarding target. The gateway encapsulates the HTTP request packet and forwards it to the address of the optimal instance. The target instance executes the service task, generates the result, encapsulates the response according to the HTTP protocol with the source address of the original request, and returns it to the client‑side gateway, which verifies response integrity and forwards it to the client.</t>
        </section>
      </section>
    </section>
    <section anchor="service-semantic-identification-and-routing-for-the-internet-of-agents">
      <name>Service Semantic Identification and Routing for the Internet of Agents</name>
      <t>In the collaborative paradigm of the IoA, service semantics refers to the business intent expressed by an agent in order to accomplish a specific task. Its core is the target service the agent seeks to discover and invoke — such as DeepSeek LLM inference or face recognition — with the goal of achieving precise demand‑to‑resource matching. A complete service semantic description comprises two layers: the "functional intent," which identifies the core capability and category of the target service and can be expressed via a service name, model ID, or API identifier; and the "enhancement constraints," which define delivery quality, performance, and contextual requirements such as compute specifications, latency, cost, and session context. Based on the specificity of the description, service semantics can be classified as either precise (with a well‑defined functional intent) or fuzzy (lacking a clear functional intent but carrying certain constraint conditions), a distinction that directly influences the choice of routing mechanism. In technical implementation, service semantics must be transformed into computable, routable identifiers; common representation forms include structured tag sets, key‑value collections, and encoded information embedded in URL fields or dedicated protocol fields. The four routing mechanisms examined in this section differ fundamentally in how they carry service semantic information, the granularity at which it is parsed, and the matching strategy applied.</t>
      <section anchor="fuzzy-search-for-the-internet-of-agents">
        <name>Fuzzy Search for the Internet of Agents</name>
        <t>The fuzzy search approach for the IoA constructs a closed‑loop mechanism of "demand parsing → semantic matching → dynamic binding," enabling efficient and precise mapping of an agent's imprecise business requirements — such as "I need a fast text‑to‑image service that handles Chinese" — to capability‑compatible, state‑compliant agent instances or service chains, without requiring precise technical parameters. This realizes the initial connectivity discovery from business demand to resource entity. The mechanism is illustrated in Figure 5 and proceeds in four steps.</t>
        <figure>
          <name>Fuzzy Search Mechanism for Agent‑Oriented Internet</name>
          <artwork><![CDATA[
```text
+---------------------------+        +---------------------------+
| User Input Agent Query Req|        | Global Agent Resource Pool|
+-------------+-------------+        +-------------+-------------+
              |                                       |
              v                                       v
+---------------------------+        +---------------------------+
| Intent Understanding Mod |        | Capability Tag Vector,    |
+-------------+-------------+        | Trust Domain              |
              |                      +-------------+-------------+
              v                                    |
+---------------------------+                      |
| Structured Query Vector  |                       |
+-------------+-------------+                      |
              |                                    v
              |         +---------------------------+
              +------>  |    Vector Database        |
                        +-------------+-------------+
                                      |
                                      v
+-----------------------------------------------------------+
| Preliminary Filter: Semantic Similarity via Capability   |
| Tags & Trust Domain Compliance                            |
+-------------------------+---------------------------------+
                          |
         +----------------+----------------+
         |                                 |
         v (Complex Intent)                | (Simple Intent)
      +--------------------------------+   |       
      | Refinement & Composition:      |   |                               
      | Auto Compose Service Chain     |   |                               
      +---------------+----------------+   |                              
                       |                   |
                       |                   |
                       v                   |
          +---------------------------+    |
          | Return Agent List         |<---+
          +---------------------------+

]]></artwork>
        </figure>
        <t>```
Step 1: Unified registration of agent semantic identifiers. To enable precise business matching, standardized semantic descriptions must be constructed for all schedulable agents in the network. Agent semantic descriptions and multi‑dimensional attributes are registered actively or collected via crawling through standardized protocols, forming a semantic registry that covers capability attributes (core functionality), performance and state attributes (load rate, response latency), and trust and collaboration attributes (trust domain, communication protocol), constituting a globally maintained, dynamically updated agent resource repository.</t>
        <t>Step 2: Parsing and structured encoding of fuzzy demands. When a leading agent or user submits a fuzzy collaboration request in natural language or similar form, the semantic parsing module performs tokenization, disambiguation, and entity recognition on the raw request to extract core task atoms and implicit constraints. The encoding module then converts these into a structured query vector — encompassing capability requirements, QoS constraints, data formats, and session context — according to predefined service semantic templates, serving as the basis for subsequent matching.</t>
        <t>Step 3: Multi‑dimensional semantic matching and candidate set generation. The matching module retrieves and ranks the global agent resource repository upon receiving the structured query vector. It first applies preliminary filtering based on capability tag semantic similarity, task match degree, and trust domain compliance to form an initial candidate set; for complex requirements, it automatically composes and validates service chains. A multi‑objective scoring model then comprehensively evaluates each candidate's semantic match score, real‑time load, historical success rate, and network overhead, outputting a priority‑ranked optimal match list. For text tag matching, cosine similarity based on bag‑of‑words models such as TF‑IDF, or semantic vector comparison using pretrained language models, is commonly used. For numerical QoS constraints, range matching or threshold filtering algorithms are typically applied. In generating the overall ranking, a common engineering practice is to construct a multi‑attribute weighted scoring function that integrates semantic match score, real‑time load, historical success rate, and network overhead into a final priority‑ranked output.</t>
        <t>Step 4: Result feedback and client‑side dynamic binding. The platform returns to the requester an optimal match list containing access information such as IP:Port and service identifiers. This step constitutes a recommendation rather than mandatory routing; the requester may independently select the target, initiate the connection, and configure communication parameters based on its own policies. The platform additionally provides dynamic binding assistance: if performance degradation of the bound agent is detected during task execution, an alert is triggered and retargeting is recommended, with the final switching decision left to the requester, balancing flexibility with service elasticity and robustness.</t>
        <t>By combining natural language parsing with flexible tag matching, this technique precisely accommodates the fuzzy service demand characteristics of the IoA and provides efficient resource discovery for exploratory inter‑agent collaboration, substantially lowering the barrier to initial coordination among heterogeneous agents. It is best suited to initial collaboration scenarios with imprecise and exploratory business requirements. Its technical characteristics complement those of the anycast approach and the application‑layer URL approach, addressing the problem of resource discovery when the precise service name or address is unknown, and providing the discovery entry point for subsequent high‑efficiency invocation via more precise routing mechanisms.</t>
      </section>
      <section anchor="dnsbased-precise-naming-for-the-internet-of-agents">
        <name>DNS‑Based Precise Naming for the Internet of Agents</name>
        <t>In the IoA, DNS‑based precise naming deeply accommodates the "business‑driven, service‑heterogeneous, dynamically collaborative" characteristics by extending the "one domain name per service" principle into a dynamic scheduling mechanism for "semantic service demand → optimal agent instance." It upgrades traditional "location‑addressing" DNS into a routing hub that integrates "semantic addressing and dynamic scheduling," providing a standardized, high‑throughput semantic addressing entry point for large numbers of heterogeneous agents. The implementation proceeds in four steps.</t>
        <t>Step 1: Semantic encoding rule definition and agent service registration. A network‑wide unified semantic domain name encoding specification is established, defining a standardized mapping from service semantics to domain name fields and specifying encoding formats for core fields such as service capability, QoS requirements, and version information to form structured domain names. When service‑capable agents join the network, they register with the coordination platform via an enhanced DDNS protocol, providing the reachable IP address and semantic attribute metadata including capability descriptions, performance thresholds, and SLA parameters. The global registry establishes precise bindings between "semantic domain name — attribute set — dynamic instance list," with automatic DDNS updates upon instance changes. The semantic domain name encoding rules for agent‑oriented DNS are illustrated in Figure 6.</t>
        <figure>
          <name>Precise Naming DNS Domain Encoding Rule for Agents</name>
          <artwork><![CDATA[
```text
+-----------------------------------------------------------------+
|                                                                 |
|     service‑performance‑version.trust‑domain                    |
|    |------| |----------| |------| |----------|                  |
|     Service   Performance  Version  Trust Domain                |
|    Capability                                                   |
|                                                                 |
|       Example: speech‑tts‑lowlatency‑v2.agent‑net               |
|                                                                 |
+-----------------------------------------------------------------+

]]></artwork>
        </figure>
        <t>```</t>
        <t>Step 2: Request reception and domain name semantic parsing. Users or leading agents can initiate standard DNS query requests carrying semantic domain names representing the desired service, without prior knowledge of instance addresses. The enhanced DNS server, acting as the control plane core, receives the request and decomposes the domain name according to predefined rules, parsing and extracting key constraints such as service type and quality requirements.</t>
        <t>Step 3: Dynamic instance matching and optimal IP selection. After completing semantic parsing, the DNS server queries the global registry to retrieve the list of matching online, normally loaded service instances. Through a built‑in dynamic scheduling module, it integrates real‑time data on instance load, network latency, and historical success rate, applies a scheduling algorithm to select the current optimal instance, and returns the real IP to the requester via a DNS response.</t>
        <t>Step 4: Direct client access and service loop optimization. The requester uses the returned IP as the destination address, encapsulates the service request packet, establishes a network connection, and completes the service invocation with the target agent instance. Data plane interaction is conducted autonomously between the two parties, with no further DNS involvement.</t>
        <t>By providing a unified semantic domain name encoding framework, this technique enables precise matching of agent service demands to resources, accommodating the core IoA requirement for a unified semantic identifier scheme. It provides standardized, highly reliable addressing and scheduling for large‑scale coordination of heterogeneous agents across domains, deeply integrating semantic identification with network scheduling. Its technical characteristics complement those of the anycast approach and the application‑layer URL approach, providing a standardized, high‑performance discovery mechanism for scenarios in which the semantic requirement is known but the instance location is not. It serves as a foundational routing solution for large‑scale service scheduling in the IoA.</t>
      </section>
      <section anchor="anycast-identification-and-routing-for-the-internet-of-agents">
        <name>Anycast Identification and Routing for the Internet of Agents</name>
        <t>The anycast identification and routing approach for the IoA associates equivalent functional agent services through a unified anycast identifier, integrating capability awareness with dynamic scheduling to enable efficient communication, precise discovery, optimal routing, and reliable forwarding among agents. The mechanism is illustrated in Figure 7 and proceeds as follows.</t>
        <figure>
          <name>Anycast Identifier and Routing Method for Agent‑Oriented Internet</name>
          <artwork><![CDATA[
```text
                                                      Receive service instance info
                                                                      |
                                                                      v
+-----------------------------------------------------------------------------------------------------------+
|                                      Control Plane: Agent Service Orchestration                            |
|                                                                                                           |
|  +--------------------------------+                          +----------------------------------------+  |
|  | Agent Demand Management        |                          | Agent Service Identifier                |  |
|  |               v                |                          |                                         |  |
|  |          (Compute)             |<----------------------->| +----------------+  +----------------+ |  |
|  |               v                |                          | |Terminal & Subnet| |Service Instance| |  |
|  |      Service Instance Table    |                          | |Management      | |Management      | |  |
|  |               v                |                          | +----------------+  +----------------+ |  |
|  |          (Compute)             |<----------------------->|                 v                       |  |
|  |               v                |                          |             SID Management               |  |
|  |      Policy Management         |                          |                 v                       |  |
|  +--------------------------------+                          |             Gateway Management           |  |
|           |                                                  +----------------------------------------+  |
|           |                                                            |                                  |
|           |                      Network State Management <-------------+                                  |
+-----------------------------------------------------------------------------------------------------------+
            |
            v
+-----------------------------------------------------------------------------------------------------------+
|                                       Business Plane                                                       |
|                                                                                                           |
| Intelligent Agent ----->  +------------------------+                       +------------------------+        |
|                           | Protocol Gateway       |                       |                        |        |
| Smart Device ---------->  |  +----------------+     |                       | Agent Service Instance/AGENT |
|                           |  | Request Parse |     |                       | Agent Service Instance/Tool |
|                           |  +--------------+     |                       | Agent Service Instance/LLM  |
|                           |                     |                       | Agent Service Instance/Knowledge DB |
|                           |  +----------------+     |                       | Computing Service Instance |
|                           |  | Policy Execute|     |                       | Computing Service Instance |
|                           |  +--------------+     |                       |                        |
|                           +------------------------+                       +------------------------+        |
                                        |                                           ^
                                        v                                           |
                               +------------------------+                           |
                               |    Network Controller   |---------------------------+
                               +------------------------+

]]></artwork>
        </figure>
        <t>```</t>
        <t>Step 1: Anycast identifier definition and assignment. Standardized mapping rules are established, binding semantically equivalent agent service clusters to dedicated anycast IPs, achieving deep integration of service semantics with agent identification.</t>
        <t>Step 2: Agent service instance registration. The system collects and registers the full set of agent instance information associated with each anycast IP via standardized protocols, including real IP, deployment location, compute configuration, response latency, load state, and QoS support capability, enabling dynamic association between anycast IPs and instances. Upon instance scale‑out, migration, deregistration, or upgrade, the system automatically triggers a registry update to ensure that the anycast IP is always associated with valid instances.</t>
        <t>Step 3: Request reception and semantic parsing. The initiating agent directs its request to the corresponding semantic anycast IP without needing to know the target instance location or real IP. The gateway receives the packet, extracts the destination IP, and forwards it to the parsing module. The parsing module decodes the business semantics using the global mapping table, identifies the service type, compute requirements, and request core content, and validates the initiating agent's authorization and QoS requirements.</t>
        <t>Step 4: Network scheduling and optimal instance selection. The scheduling module queries the registry based on the parsed results, first filtering candidate instances that satisfy the semantic, compute, and baseline QoS requirements, then performing comprehensive evaluation of real‑time monitoring data — load rate, latency, bandwidth, and availability — using a weighted algorithm to select the optimal instance (e.g., Instance A) and generate a scheduling plan containing the instance's real IP (IP1(a)) and an SRv6 path.</t>
        <t>Step 5: Path establishment and task forwarding. The initiating gateway processes the packet according to the scheduling plan, embeds the SRv6 path identifier, and forwards it along the specified path. Intermediate routing nodes perform fast forwarding based on the path identifier without re‑parsing the anycast IP. The gateway at the target Instance A resolves the packet via the local Segment Identifier (SID), confirms attribution, and delivers the packet to Instance A.</t>
        <t>Step 6: Result generation and reverse return. Instance A executes the service task — such as data computation or collaborative decision‑making — and generates the response. The gateway maintains path consistency, ensuring that the response is returned accurately and efficiently to the initiating party, completing the full anycast communication loop.</t>
        <t>By leveraging semantic anycast IPs to achieve deep integration of business logic with the network, associating equivalent agent services through dedicated anycast IPs, sensing service instance operational state in real time, and performing dynamic scheduling during data plane packet forwarding to realize agent service semantic routing, this technique belongs to the same IoA semantic routing framework as the approaches in previous sections, and complements them in enriching the range of applicable routing scenarios. Its core role is to support agent coordination at scale under dynamic load conditions, providing reliable routing support for efficient communication among heterogeneous agents.</t>
        <section anchor="applicationlayer-service-semantic-identification-and-routing-based-on-urls-for-the-agent-internet">
          <name>Application‑Layer Service Semantic Identification and Routing Based on URLs for the Agent Internet</name>
          <t>The proposed application‑layer semantic identification scheme for the Agent Internet is designed around two objectives: precise semantic service representation and efficient routing. The scheme accommodates heterogeneous protocols used in agent collaboration environments. Service semantics are embedded into protocol‑native fields or key business fields, enabling a direct mapping between service requirements and computing resources. This approach supports flexible and efficient routing decisions.</t>
          <t>For agent interactions with Large Language Model (LLM) APIs, a two‑level optional identification mechanism can be employed. The URL path serves as the primary identifier, where structured path encoding (e.g., "/agent/model/gpt‑4‑v/v1") conveys core semantic information such as model category and version. Gateways can extract these semantics directly from the URL without inspecting the message payload, making the approach suitable for high‑frequency and low‑latency agent interactions.</t>
          <t>However, URL‑path parsing can represent only coarse‑grained semantics such as model categories and versions. For LLM invocation scenarios that require finer‑grained semantic descriptions, URL‑level information alone is insufficient for accurate service selection. Additional payload‑level semantics are therefore required. One possible enhancement is to use the "model" field in the JavaScript Object Notation (JSON) payload as a secondary identifier. This field can directly represent detailed model attributes such as "llama3‑70b‑fp16". By parsing the model field, gateways can obtain more precise model information and attributes.</t>
          <t>This paper uses a representative Agent‑to‑Agent (A2A) protocol as an example. Under the A2A protocol, URLs remain the primary carrier of service semantics. In addition, session affinity must be considered. Fields such as contextId and taskId can be used to determine whether a request belongs to an existing session or is associated with a previously established task. The application‑layer semantic routing architecture for the Agent Internet is illustrated in Figure 8 and operates as follows.</t>
          <figure>
            <name>Application Layer Service Semantic Routing Architecture for Agent‑Oriented Internet</name>
            <artwork><![CDATA[
```text

                                                        +-------+--------+                                      
                                                        |     Agent      |                                      
                                    +-------------+     +----------------+                                      
                                    |  Controller |          |                                                  
                                    +------+------+          |                                                  
                    /           /          |          \      |    \                                             
                   /           /           |           \     |     \                                            
                  v           v            v            v    v      v                                           
            +----------+  +----------+  +----------+  +----------+  +----------+     -------+--------+          
            |  Router  |  |  Router  |  |  Router  |  |  Router  |  |  Router  |<---|     Agent      |          
            +----------+  +----------+  +----------+  +----------+  +----------+    +----------------+          
                  |           |            |         │  |           |                                           
                  +-----------+------------+---------│--+-----------+                                           
                                    (Cloud Network Fabric)                                                      
                  |                                    |                                                        
                  v                                    v                                                        
            +-------------+                    +-------------+                                                  
            |   Agent     |                    |   Agent     |                                                  
            +-------------+                    +-------------+                                                  
                                                      |                                                         
                             +-----------------------+|+-----------------------+                              
                             |                        |                        |                              
                    +--------+--------+       +--------+--------+      +-------+--------+                      
                    |  Large Model    |       |     Tools        |      | Knowledge Base |                     
                    +-----------------+       +------------------+      +----------------+                     

]]></artwork>
          </figure>
          <t>```</t>
          <t>Step 1: Agent Registration and Mapping Table Construction
Before participating in A2A‑based service interactions, an agent registers its service information with the network system. The registration process primarily involves publishing an AgentCard that contains the agent's service endpoint URL and supported capabilities. Based on the registration information, the network system maintains a mapping table between semantic service identifiers and active agent instances. The mapping table supports dynamic updates and stale‑entry removal to ensure accuracy and timeliness.</t>
          <t>Step 2: Request Reception and Service Requirement Extraction
All service requests initiated by agents are directed to the application‑layer semantic routing gateway. The gateway receives the request, performs protocol‑compliance validation, and parses the message content. Information extracted includes the URL from the HTTP layer and Task and Message objects from the A2A layer. Relevant fields such as contextId and taskId are also extracted for subsequent routing decisions.</t>
          <t>Step 3: Determination of Routing Requirements
Based on the extracted fields, the gateway determines whether the request belongs to an existing stateful interaction, represents a new task, or continues a previously established task. For task‑continuation requests, the gateway uses taskId, contextId, or related identifiers to locate the previously selected backend service instance. In such cases, the request is forwarded directly without invoking a new routing procedure. Otherwise, the full semantic‑routing process is initiated.</t>
          <t>Step 4: Semantic Routing for New Tasks
For stateless requests or newly created tasks that do not require session affinity, the gateway identifies candidate agents according to the service semantics represented by the URL. It then selects the optimal target agent according to predefined routing policies. The request is forwarded to the selected agent, and the mapping between the task and the chosen backend instance is cached to maintain continuity for subsequent requests.</t>
          <t>Step 5: Response Generation and Delivery
After receiving the request, the target service agent executes the requested task and generates a response. The result is encapsulated according to the A2A protocol and returned to the client‑side gateway together with the original source‑address information. After validating response integrity, the gateway forwards the response to the requesting client.</t>
          <t>Using the A2A protocol as an example, this section presents an application‑layer service semantic identification and routing mechanism. Through cooperation between control‑plane functions and data‑plane gateways, an independent semantic‑routing plane is established between the network layer and the application layer. The architecture decouples agent services from network addresses while supporting centralized registration, Layer‑7 (L7) semantic parsing and scheduling, and Quality of Service (QoS) enforcement. As a result, fine‑grained cross‑layer and cross‑domain semantic optimization can be achieved without affecting the agent interaction experience.</t>
          <t>To ensure feasibility and robustness, several engineering considerations must also be addressed. For example, session affinity requires an efficient cache that maintains mappings between context identifiers and service instances. Cache expiration may be implemented through aging mechanisms or integrated with instance health monitoring. In the event of routing conflicts, such as the same session identifier being associated with multiple service instances, predefined arbitration policies (e.g., first‑match or best‑match selection) should be applied. The specific design of these mechanisms depends on the system's reliability, consistency, and performance requirements.</t>
          <t>By embedding service semantics directly into application‑layer protocol fields, the proposed approach enables task‑level semantic scheduling and routing. The routing granularity can be reduced to individual service requests, allowing the architecture to adapt to the highly dynamic nature of Agent Internet services. The scheme is compatible with heterogeneous protocols and provides a flexible and extensible routing framework for high‑frequency and short‑lived agent interactions across distributed computing‑network environments. Using URLs as semantic carriers and leveraging A2A fields such as contextId and taskId for session‑affinity management, the approach achieves deep integration between service semantics and network routing. It complements the mechanisms described in previous sections and can be deployed in combination with them to further enhance routing support in cross‑domain computing‑network collaboration scenarios.</t>
          <t>For other agent interoperability protocols, such as the Agent Network Protocol (ANP) and the Model Context Protocol (MCP), application‑layer semantic identification and routing mechanisms can be defined according to protocol‑specific characteristics while following the same architectural principles. To enable semantic interoperability and coordinated scheduling across vendors and protocols, a unified service‑semantic metadata framework and protocol adaptation gateways may be introduced.Specifically, the control plane may define a common semantic description framework that maps protocol‑specific elements, such as contextId in A2A, session identifiers in ANP, and resource names in MCP, into a common set of abstract service‑routing attributes representing service types, capabilities, and session contexts. Data‑plane gateways can then incorporate protocol‑specific parsing modules to perform semantic extraction and translation during forwarding. This approach ensures that requests originating from different protocols are processed using a consistent semantic model and routing policy framework, thereby enabling accurate service matching and routing while preserving protocol heterogeneity. Detailed implementation mechanisms are outside the scope of this paper.</t>
        </section>
      </section>
    </section>
    <section anchor="security-considerations">
      <name>Security Considerations</name>
      <t>Semantic-routing-enabled agent-to-agent interactions bring new security risks including semantic identifier spoofing, fake service registration, routing hijacking, and service deception. Mechanisms for semantic identifier authentication and integrity validation, trust-domain isolation, and access-control policies are required. Malicious agents may forge service semantic tags to attract requests; registration validation and runtime anomaly detection should be deployed. Privacy-preserving matching techniques are needed to avoid disclosure of agent task intent and capability metadata during routing procedures.</t>
    </section>
    <section anchor="iana-considerations">
      <name>IANA Considerations</name>
      <t>This document does not require any IANA-assigned code points or registry actions.</t>
    </section>
  </middle>
  <back>








  </back>
  <!-- ##markdown-source:
H4sIAAAAAAAAA819W3Mc17Xe+/yKLrjKJsIBKEqyFIOyKiBIyjghJZqg7DqJ
4nJjugdosWd63N0DcFR4cOUhVXk8qfOYPOaP6Zdk3ffafZkZULQrkxyLmOne
17XX9VtrHx0dTdqiLfOT5E3e5Gk9u06qZdLk9U0xy+G/i3TZFrOkyHL477yY
pW0Bv6fLLKmrdVssr5I2n10vq7K62iTzqk7Ol21eL/M2qeZJegVvNZP08rLO
b06SC2n1Qlt9I03Qe9XpJKtmy3QBY8nqdN4e3abLqyNq40gHciS9Hn3yyaS6
bKoyb/PmZLJeZSn9A/9zMoFR5ldVvTlJmjabNOvLRdE0MO63mxU0fv787YtJ
sapPkrZeN+2nn3zyu08+naR1np7oiCa3Vf3uCvpanUze5Rv4KzuxmR09w9FN
Jum6va7qk0mSHCXFsoH5HSd/hiHDF0nC87i4Ln4swpdVfZUui59oDU+Ss+ti
mSbfL4tZtaCfYY5FeZLgtJsfv/z0sy/+0wwfWdMTx7Nl6Ollr6eXxW2+/JCe
ytvffTnaz78eJ//lOu7oX9Ol+26/fn7C5zePH/9264xepdF8flwv9av9elmk
5Y+PP/nttsmcpZWfyno5zwv7cr9eZmm1mX/2+bZeXhZr30sF23mdA5nr9/t1
VBbrTfP4y0+6PR3BkZ0sq3oB798AsU+K5dz+SpLJ+dGz49n1elMcLRc1nJ9C
jhBQLlK1PkJ7cpQtmtlRUaXhgBVI5emMx8aPloUdxAynKA1sNtdl3HZzNK9h
ztrNmxdnv3v85RcwRBhzkl42LTY8mfy5aK+T9jpPsjxfJdjhVc18BXlGTXym
SEv6pSwL6AGYBrIc6SawnCJvptRSn+sk12mTXOawaPhuUixWVd3CFJOsqHOa
HrEdfDm/qcq19o9fLPP37RG0ksuwtPXj5C38OquWS2lhldZpVlwt9MUW/8Rf
YPQ2pFmO/8ozZKw///1/l5Uy0Syrc+BLy6uf//5/gK6WMOQ6KzfJIoe3eH1g
U7JGWx+YJE4B2rxcQzPQ1lFWAxUwfxYefpQ2R2HE0BNPosfhB9h5s2nafDEN
s7SFmsIi1LgSZZleVrJKdf63NaztggZWLEeGPKXB4W9lsShaepVn6NauNxjY
6OQWFlHGBG/N0hKWKi/XswKZfnacnLfA0JpkVqY1UFCOnaRtf4L4DHYPfD1p
Kxh1WhY/UWe8gctGjhNSSF0tcH11tXhDcLvgTfge9q9a1/ADPI/H9Cqsr6wU
b9EcnuIl6w1nAVMEbtAstq4ZshKY7nz900+wLyynL9OGiapNr2wAtLrzMn9f
XJZA+Fm64iWGXQSyL1AKHmFjWfLs24vkQVYBs1lS87K0h0pTSj/uEZz4Il2t
oJ9pYjRXppu8trPZ0RRskKfLzSxtWt7+79+8TB4AS8OVTmwR6WRU9eHAniHH
gI5LaVb6tOeAQ6SrZl1yn0QoKdDR5ifoG8ae5av2+jh5AXwUiIY5BpEWUlEC
6498Ka+LBtoiWsxTWF/dQiG89WIBhIUt4gyAr8CxyDNc1+qmyHjpHZup8zm8
hpwL1xN0kAaOR04/8P4dM1tcFFlW5pPJr3Df6ypb0zmdTJCI6nRVQHfZTQrt
4LlSTgCnEY5OmQB7W1aLDY1ojHEWTYJcQSm8x+yM3IjYTZjAAyQKHLdrq1tg
UK71tvvIcXJKXzsmsqpuifldbhI4mFewyyBM1kDXyaLK8rLB8RFprogZ4DIC
mS+zFOcLc+mcyCJw4wRXsYCu2nWdT/GX2+tidh1P6rYoS5rzTY6DrXCTDvwJ
owE3B8kDUEAPge7/HfpXWoaf/WSRsFvkREBsKR4v+H0F0wfqohOWyQH7+e//
tkjf0SHJ3+cz4Zi4R064iiyBNmtkeIF32r5Up7g2cgyhTeHtnSU/UVGwAF02
AZ0UKaJaN8AtsqKZVTd5PWXuoEO4qd7lyTUoznWFMg6eNWmgR7GhhSiWs3JN
lF3BgGpjRryPvH3T5N2yui3zDL7Bsy78HY/HugVJCg9xY8YIroura5hNmd/k
pTGRpLr8EedzkzfAyJEPIlmI3OEDS+zTLWAC/APY+3UxRzmItHtdNfBPPG0y
nXyZraoCFwc3viN+cPzEYmc42LJoiH3Sv/P3wFObd40QjjS/hmZh4G0F/6M9
wMs4em1ef6Y/vHi8MYkLx/7tkJagrA7m7RUG1RagUV7BoDVMYbvKDW0PaCLX
m4a4mfLfvIZtXcNxAHF3/lpfy2msedMC/cKMTZe5KdoNaEvtbQ4URptG8hSU
kmWlKhNQFC0/nFZWT2zzlA9Hix+pA06UzUDitsIu8zlyLGBT0HnVghkKg3mn
clCF7b/l71c0ZVoFWl+lUzppIvhWxSovYTzEb2mgbiPAgAPmz+fuBfyev09x
n6fAMkhd4tHRmHMkooMUVv4WyRR0CxweaunAuOkb4V8vX75CdilcXqY9PRhU
ZGQx8JSWbQE9JyTBeGFMSDNtIsMrw9/dPQABTMsjY02Yp4FwrKtVXcBwbQfA
HmlTEgHLICqRlSKzxG1omOLD4ij5IzV0+FUiK3GcPF0Xpcm7cb+AmQKih61X
KBoDscD5zWAFYISZ6i2sogRtCg8Dcp58jmc/BdIpSPGDg438tzYNnjgSHkv4
EQkHWEu16jBTPHjMVYBnIxuExSuu0G1wf3dHgUtvvWPjxM1JUWqrFZ4E4rx4
Xmuwyox/dQ+FMnplSmMjUFb4hJ6CfV7OkIqQnQnfqeoC2UYGs2+Kq6UyOtNy
srwFs5I6ZW2UfSQozuCrbWopcm+veE5RdTR+pHsG+iHxpJT1vBF9kEflNDk6
UKjLgUpobXZH8wT3nhQuZqWk2zWFrmCT85ToDIDmljdPuBvQcdZtWVXvkEPO
16gnBPOvOUalS11Qb/zGnGr7tsM9hYEVtP73SLLI2BZ5fYXt2hNmRJmegoIQ
znMQ2cnpuQpzpMg8EUsFthtUz010GlUX4QWtc+SQ9CaaNcCVatiDek2qkSig
dPzoYPJCxGemqYAPg75lkjmy7VAYNKasmKym81mpEDEOD/ZYOjX9gMiwqoD0
0lldNWigVWvQm1Fl4F9z4vJwavEMtiS5VFWrVvkStShgPQ1aNFMxbWdrUQZU
N4tNUXMUXAMFXYEqj1wGdFdS34FI2mpGA4K2sIdIkxxUQGRbUpxlg3K3IAUQ
mnpfCCdA9QCn6zUw4DTIb3HVzYQUpQzNENAxYKhXVVu4w2HmUAOUnK1LOVXZ
VkVFJ0orjItJRtvU/l4B9yZjq7Otb/dSrLxEYyULdyfQbVe1UoLVbQB9fiYu
DzJlpFlHk9frBUoTZ3zk75EBgZiFrtR+UXWhjaTFuKynx27Scp2L1oFT/vN1
Ueb97YiY/HWKp68lf1WemcmGX+HBYzsENBb4ZpaCnlKkIi4zUMJxa9MEmTCx
PRjTFYjsGt166D3ziznk0IKDCTqQsUCyNYoSJDKv7+m5Z/Y2MhhXRtuCkyGW
hxtBIpZ1RO1KFp31DyQAsjF4ezrOlWAY/5Q3QYbNYSXxnAi1jgs0McGbfb09
QeZ4qxpfBvYO59ecds6aDnLc6DlYuKsUdogpeMw5ByvmjC0wFnED0Z+EO/yi
uEI+8xgkxVdz/jcFS35/8Nz6eG19DKr10D6bxPrNwddJMvkKjHXcDfz3D3/F
/9cCj4M/kj0/T2lBgGqfv1+BuogDSSZ/wEN01FZH9I/krFos0G3M6/Zr+Nuz
yGTy+/HP13Fv3DDNY8rT4T96XSSTbieuAfuL3+185Et65BH/l//zaHhhf4Af
/5SDIIXDTI921hm++CF5CZp1taJmfrCepPUffjjizyNduvHl3vGzn+JDm905
cwN0yNgEH8YrgZ83FTASILBHjia+esTkFugDdJVfwXIDBZ513FV40t4MncIB
neV8qdQOzKRsr0lmiGxbVWgeNqhqlRVoYagJVLB4js/PNrO9vB4k1IPng60V
dLOalx+6XKOtxsxZ5QbLNH0mlnDOJ4SujRzENhvIXo2ZqnfBGZZkcZl4wK70
G5O0sX1oMhH1YrSgI5Gi7ipvppAC7T3EDXuWxZmCYchUdC9lRsNekFHbmbQL
tK7BLs1TNpj4OHK8Qng78e8k26Ayzjxc5RvTiagUzuSRzb/VkAxMHMa9qtgo
M+FDmiYuG8wZHdGgZRe5+RSDQmh6SKxmvHFOdnRw+AUFTk8+FFBRUDPIYUlS
Fm1+DZZjDmYntk8mkxdF3ciiIEs3sxvOYUVK2KDt6WWsrYQqMWFy6iwCzVY8
GLR4v4GjQ2oBLXixUPLokgRtQFB5zL0ReTSc7Ys60KrENaxU+R9yLeH6XqAj
OEO1A53qBbqlSaOihtOMdNWeaYn2s9nosCvLPM/Q+KrYYG+vu1Pwfp55UIlJ
qc+KOXlC2oRVT55uu1mRuxSUpRy1N15IWCVYogr0o59wpMH25c480WFHN2ld
IPcJzklpEJhRWnf0FDQs0DnAK4g+TuBVsrnDPgb1eg1tV+wltQGQ2lRnU+Jq
uIMFBhlvwdRnX+a874KhYYgMg69asp2EPDPScd2hJY8QWVaoAhulDQ4RDKM1
heJgY5ZrHqYbFJhHS3KE6DRlK2NLAwfk4iOgi+DBg5GU1W1kGiAruQaKYj4K
6hIsJZKesTJmHo3bxQ26QGyqUzlXRUnRt3Cecs8W5+TcAu49BTsEzgt5XMkD
iL5s+AcREXQMdmDdX5loyCtU2msgyDjOo859f6acMjPlhSXfHUVh+gdUlpCn
O4cDWd2Gcw1tF2LWgfb4HONJ5qzg2GlHjGPkCN2zzQroE7ib+HE+gA0Sl1/k
5N/4VfIy1ru9LqVgl8n566n6GjKYCgyrMpOZFO6rsrp05kpnpYyhNPaEGPO0
wHPi65cotGGqwvWDS5ojllWNsSU0uWfvcphpHlijCPqUSQHaQHsWtG6kE2T3
GFoo2F9dIROCvuoqlRBdW7izzyF9+pM8O24t0GchsSYMLM6AiQDXgVb/UN3m
FEMpKKp9LUyON8cbNYo1WGFcEB4hzzLOPQsyJfIpm7JidEz0HuI95Kkiz0hZ
kIk6YmxJYMfc9Q2MqJlvgsU2LGq889yE3DEriXm9EN90iDZgc1ewQmsMsMMS
ws+y3ebEiwINWYUEAeMhJqSLkHJce8ADGHimEs0xNuioq1qWmy0kJs46BaMg
f7GIIEY3ykqVU1komr6XPTAWjI/JmfKTleAbUDEzC1PZ0GifUXT9BseJ/EKO
oSrG4u0QwUPsXRc1NOO3lh1QugXeDQTLEVqfp6CQ0Swv+VCAgEXLXs4S+U1v
ydlRgaq+EO07RIWe/21NguKsgjP0SnRiMmcfPD979fqQVuoM3oBjAYPMkgs5
f2zzkqqVPDi7eP3ikLQekA1sccMk2aEwjQlCVl3COabfDym9yObfkQxvSbUo
ZjA+nKqnbdM5ipQd34aW4T1CKiiBE7B/zk7dJTx1W2TttXMm4hYXTVWmZrHU
+SUeuGw9U5bKm+BiVvE+xa63SMedBppEWbhCYwC/Jy8DTMqCQmm2ALlBHgj2
c0cefFGsbq9BUHSZfRLrZ7w0x/H6k2PJVMR+qB8De4p7Eb1Qjks8tQEPJZ1u
GJFtqmI9X5JWcHpV5xzcfnDx8vTQnFBkTME64M6uKuAIqOcCOwR+zmE30tjY
iSqRLAxdEkfvBFJ7EQwCYDTq4FmROjBjJX59tZCzGh0oPa6MNsmsab9Qs7Su
efFMVFUI7VmywS4bim1C5xpDRWWVZBIqLRJ3+UmfJYdduhkNfmggrk7DDnSf
OU6+41ZiTzaOi8MAFKtbstVMYTF5XJkpc2DCeKxUsuTvUTXhRWJHYko6Gy7B
ZhxAps7e5kl31L2xzdEF0EeggVooApbOtYa2Sz2ieUACqp+btswARdIQURTK
DZI2Ioc1uCxDUmXRH1zv0wIFPCsJS8aGbbteLhG1UtVehiUYR7xNN8xpbEYh
suv0COz9YJi6Doy8gPe024gbDCt10vJpacSrgvqNrQ56sIvLdSvswQQynrF6
hdajl3ymeVpvGZgQ5FyM+PGagq/EjOUYB5uKsGHi3R/3iEQmHtgd6xoZ7qJC
GM/WaccUlJJqg3RCcVZ0iTo9TjDfLJK8BASFnuAsoIssky7ypR91qXNas2Zd
tGypqUWSrWvh7n2rJRiOwKlIxWNdFNbNpBIwMNS1GFhGVpectyga0KyRkws4
K1juyvZJoYojBgqXuCFrdDrA4Oglm5gKDYMYKVAIu9Z4C1GyU6W3SDtn+pEz
bWPqluJax4IGcwcfiVZwKuZxs+CxdRe878Gr8w54YJmsa9IK0M0hUUvljep4
zPfDM7i4Py+lQpjzMXTDtONJiEwTndwsgmuSbW/rr3am826EH3cEwIT288HQ
Irs7OTiVoQiYa+hzRfiK2bohxVsddzGGYSoxHhyPumnuA6YIEXuDafLMYSgc
8oP+24pHf5+G9Xj4rQp42WsHITDfc+wdmBetAUF1lAQYuCDnjRDtKeowy35i
y3l/ZGZsg02OwvqmyG+xmXu9ezEmdAV1oFEp9Ft2YaNb+KqE9zkOvKxuzNOd
Ly7zLPPh67D4TilChIhaFfoguv5o8H+sLuIDj097RFmlmtQ0gD3Vs0wSDU/G
+j2cFQZBhH5H4ojU5oBcc+KwBQaC3V+S0EATqmPPsWttVkWTN79bQ32RGIzw
ds51apTIPnnUAgdgdCP2H0VlHagjhsRSaB7pbsTS3IIZTKKVMb+AWLfBcmS2
EAE9hoPvXXdFos4KRip5ga2asKDTxc0p3s98VVabhWLwjFawqxAdUa/MNNkU
uWDQiO/k7I4okIvTIvHRMe5yvOXomBxonG203VnOgLaAKVHXWTOri5VSpnNM
4CzQ2CZHghit9D37zndgcR3PB1OJHDiE/EP/jRiO5AprzalbWmSGznTLSlzP
0x2JWIHtOtkRGbotgV5YFKi4ajbLGajFmsokdpObwBWashuvKcYuZ+czjwEd
4jT3uhg1ju5osJ4bNYucAWqeabSnVdHY6qHuaiG79TrvV26OGQI2KpUQZNh0
0AsBusgsVyORpmh75ryi2IUAzpfOf0R8Ke86onxQwDnfEcO0wI1GfE4UvWL6
8HpbPxFCgjyEBrfAlvQ0HdPVSIArjdA+E6we3bzpDEfF/dsjYRN3aZaFxa/F
s2UOGsIjk/FUIwV01a0oWvZcFe2QpJMqIA6TbEjpIU1BDCp0OK9r9M8bsN1T
Xt0RrkIQgVuRHeFVmeDUcUwlLcpKgkE6Scxh2zCKhBCF+RNr1gs2D3gtouwm
PBUwZNakOFTi4MYBcy3BghcIo3yjcoedUGcRUPTjqCsORItbLCNT+FRw1oRY
UeTrS1J05YoPUE6OqmQzIQJiKMIqSKbHprlTI6aM1SUdH+e/SH+EJwNO9GQk
7cp4mc+/isGxPkGpyiJ8bEd5XdNAyXpdlekyxPQpNrMXZnardgxU71VZyiwx
izYEb/uy1nHmopPkB/oaHDGypVVnS42l0QinsHRlSegMbm6L20gPAqseHUCv
2vogYC/Z+wYaxZJ8+rdEukC7tEkXtEmTyQu/ZagdB8SDj3yCDgbUcoN5RkqS
++TVzdQrrsEWzek5b4OXRZaKgaEkBOm8bkzOBdb8hGQeSC8MMxHZQhuSb4Ki
k7xXodMm0rgPgFNiZI39QSvKIcuz6UFyIE4rYFjJz//z/yaPP0m+uSzaRw38
BhR+sMgXiCzAn774PPnm6YHxaXG5AhmA5SgREOZ84ZQHL1eD4GH54Qpd1OQR
yvI5RQ2GZJw/Ok3yID++Op4moIFmVT3tgneh02kiQ0W5NiMZA6y0xiQMNDMO
ybeEUVrk3kUJK4oSM6PEUN13ctkFCAEpyqmkMsXSYlVVpah4LtiAu/GbvgUc
oYVXSPHWH5Jsi7BT1MAJVyVlCZBV6UgiVI1DhyDqakGvDtItwSNxMWP1H41o
ZCGcQdQ4LBMDrRD87w8GaXQFZhndMgMkNI+DKqhI9QDnnhKhmoFwYa+IUEw/
UjPd3EUycuyIXfbdGLvXQYkt+NEbXnQcuvlpH7rp+UTySpv4GLDMqOX9sZyj
n3Nn6iKuUoNqZ3V6i9kvH6EL/tx9vKZuEAIpwMqjh/TVH9cYu6aP/fKxPw+H
2ocvJ3c2x+4rX9/1Bv+RPnfS/NschSKcose0wvB/3yOKL+l1vMdIItp6rWj+
nSOJVuCr7hL881bgUxpKTBhvcpLhmAuOv/Zo46G2NkY1Ox54GNYA//uX4ZHi
/z+dIZpVdsdtxx2OUfSD0xKV4PZ60fldbNyX8J/O5Lnb4TW+45c5g8+9xm/y
Zr9SJii/6/bdcWfASM+qJQIPEXgt/bgl/yzZOYRfsOR3uG/NQJvbe/zln9G9
3tLxP5LtbOn2Qz9/+Ye0qnvzcRfjIaHVd0DXBXY+LLw5ImoJSgzpmrG4G/aQ
dMKakoMN1mOhmeuqGhONsvctJ7tSM78opxFVwB64VPPXB5yC3vXsLIhV1RQE
0dUYMRXnUbT7MbMVyyyW6BxrKUsy5qLstCUm18AkLc2Y1EjEkpFZkIml2HtM
YNQd6xodB+8pjWkg/zRMlIyKqaClsEOM5LJtmAYkINpDCI66RFDUJiQr46oo
msGyDnnNOb6rZlMnr3epdgYqyGI4cHiwt7YnCWlifudrzPQBrZY0Pl4UM0mc
2ZIq38YqKusFRhOw5oezpbAlDfMj5oeyzoI9j9MkYxYBBDnGDcA4rmqNuohx
RhbI8p1YRki7nHNUrWCDv+UYnDN8mk41EqFhsAavq8yiVtyQC9w1jBpGuRkc
RaiXT8UfFh2lBZgHsHiNto6+uDVm4Ovhmud5dpnOBOUjRdTC8nfOmZnu5NLD
CCrmifRPtlr0mD0itjn7RJ6SYf1arN9vKWF4MhlPJla7fcx5xEYae0MbLa8T
uxea0djU1IAq6LMT98S0F63q5GS6JeEKGQ4pS8fXVctp2MdLdjA54OIIozjq
2KVPwEwEQoX8C6oqoC771Dcs/kSH16BpnXhgCz1XtEBBc3GJNXHNhniSFmHA
qkAwpysEFW4qPuHm2jzwjf/8P/5Xcv76IBmoZ8UeYI12ca5IPowSOeggt7HV
Fo1yw3QfH3Bu/W5j77O+sRcTG83uY5h8DyP5t1WqohDHbof070FF4rptVyeP
Hi02q/Ti+Zs/nZ897/W4U8aL5vDpJ58df3L8+DH8b/TMvqrCtkf3aOZGmrnZ
/szwZ2BBH/Zty5HHB9boru+6ZuvorKSgZrw78Ns3jHn/FlMJ+8Yjqu/Cj/yS
fPj4hua7MysQS/GJ90l9pSxPJOrMypSVe8kHQ5wW5q7XlCbUTjnuP8JSodG8
zCRF37M75Bskd9KYJQY4mS82RgCNqQR4C2ww1TSDoRe6hXeUiVAQ/tj2ltOG
0d/K0UeCeeVFPdimi2BZyPH8tcZrlNOjUE7Jq2YwfjzPVKGhTm6KNHkmgSyq
qPYM/vdQwpXixEM0kMjW9YqiWNIZZ7jTwuGgWhyYRsU8ClZCGzJn9oSFMaBL
jn2GmqSNhcRKiSPMCFUHbDDH4kqSSfibZnhXSE2mlM5K0lE0jCLio08EPaGD
ygvoZUWmdefUl3z66BQ+lPoFyiTmqK9XPHVF4auW5AQAJRWoEEa9p0EPuWg+
olRzHjsrQq4UnAxZ6+QwyESSUHJVskCBQIw0qTfotAyNR4OgQkFUg+Y2vzSq
wfIPm5C7Et6Nsyh7RIZdB339iSq9CHH3+l2IcjW4sAhkPCZfhelyVC2KtTmp
SzdHJRbhgDISR6oYDhQomM+gN7S+4WWnLpxjyLg4KRhZ0pxjL6TgSXU/U/Ke
4Xl5TQT4rQayongUB89Te431v4H4VydO5sxGXh47lCMBslG4mGtpVKP4/NjN
LIqzWRcj4yTVdY9craDM+qpfIbYi0UKP43doLQ5sQl8HRCFag4rpBZSzkxCN
MMxnUHsRSgBKIBxWRfVovwy2plGjtYSvYdYdA20TJFoqs5ThjIjwuqMUCBN8
QcTHATFK3xEmpVLIKY1YXQbrBWJUDU+ItqpLBcwY9rypTJ/F9Fgg2HagENk0
CD2mY0kA7mjbKkWAwR7g3zDe3+MzLheVQzakhDopq4H1XnGLLiYNmReb1d08
JqvYRuXWppL4LHj7kLTRRXRZ6Q8HWiO5GFC8+six6Dac2ktbcCmYGxUpNgjt
gXNaadgYBA+wrFm1ZiBhl5s1Tzi/qkH01UbU/uDvED40QNEh89fw6iovif5C
srpn49Keiooeb72hWiwR5QgxqrU+M/i6xbjZGCKjRH0VHuAx9+dET9TUzErB
hMDKhwTJ5Q3CNZZ4GKnekXuNjaNG1ItMdLWGUjCb6+qWssxEK/00YkaTnn1j
xgwO8qkeA2a8QEbnAYv06+TU5Su8NPY4CujI64Ovg3k0+etfyTKaiHly/vpR
WjyCzttHosBus24mMp3HWyyBvsZOxsMPux6zj87kXEnhMRtxP3Qc7cOfR2Lx
7dMfTlkNxG3Gjba8y+X60J6MrKozUeR4O+nDv99Mdllfd5Mh977vjlv4KhF7
p796n07u5Cmjq5ckbuztO37ivyb/LUn+Q8L/pf8JT+h4/rLnePDzg81OSQrv
JmDMnl8FeXjfxeWndTw71k8/vVX5TFp4tP297odp+b5vwWvGBx6cvz4ce6xz
8LW36LPleNpKeXszWJt49NWFH7j3qEIUQ/B3mKOXxdJMz6YHUHU1CkVUFPWg
2kHMU1Aozg/cVXGsXdT10EhUxCorNE6NIW1p0G/mVIxeoEDs145teloOiCkf
S9Cha6Y4Jx2Ewai3PGj6KOS21LQLwNzgJe6icp3Pz9JPHJDHHI9hjTUriKX+
vSxcrLqWMwVJppy3SGdlocDvHKu3FK0GLQxY3YaElqBq+roBwfZS0N+iQuVB
tS8BeuVdJ7DiOfs+X655HO0T2cKN2MILW9mgKXCfUgG++7UGRESdkcBxlJUi
IR62BVEnlABHXNQDfdQLnM/MShhGtUXWnI9sCCjbs6kYe02kQunPU1cjgXz+
fgpolJFnIWVnttZ00o2AXy/e3HxBRqppvP1Yhew+r5CSwi6TvbvRzi5mFzge
AOj3iRE6A+dA47Y+nA/DtSrJCiNmvz+w8a0JRt9c5UoapnqO8RoGy37Logj9
h2lhLQEYrl9RLY2lE5eBuBjLaWT/vnQAUTbJdyB3J5PT+yJM4+SjIft7JGSz
1q1ABTTteJY8gPcPb9++1gco1CjppszshgxhDHgyPL4fCuKiotQpua+i2JAM
B0sgnL79Axo/EjM2kKahI6EVmAEPDlMOEB/H7jAyW4dSlaZRbhCNQNOkE06N
rHM2jtPefQhs+DZsxGpwtZNsMlRDQdB/TFzs3YJtolHrAaNUbjGQdf1hcE8i
q4zO0ZAPMC4gEDbUcH9+aajYTxwICtDfvQJBgVEdWLkBVwHd1bqMDOiq7pUp
0XR9l70mcwq5UAHGbzwQMZ4WsMazw3vWdt1PWlvzz+gypI3zHgFeouaWqn+j
I+BAJZRiYisJ2GItcTRcw+kJaeOWBtLg+zgGzLcLlIDsBr4Nzh7LzODekMEg
XR5EhBkRx0D00O+4lAtDku/loQ3aso87tuz5MM/Yh+VEWqVhjX10oxfUkGDx
HoENpochJUEjrlxIZaqLGB/0vJ0dh+AwIlB6zqiDIRcT0pZTbuHFg9jj3/Xr
cxB/ukUZRB/ph+ieSKLxBRDmFHIeIe8yskKK7mBxML1bv1Ywzj4uRCBwZa5O
d22Y/P1wR5RZp18yv+uK/6Bt7scBSQllc2V39EOZXk9gdNE33QSrYVzCuEqq
9BaBdgI2qAlnOOK94e6Rq65WYkLRiRZZmuPkaVBNi8Y/EdG7V+q9hhuT61BS
YA+qH4yLlplXSfcdaHjIe/O1Ph9NM1oPET/LEeU5JBdaZhpWY4D3btKi1Kw5
pUavauN3ljxo1YR8jgU8QPm1Bv8Z81KGCAvnB2rarUi8HepxRMAjOrIcFK2x
Ju7ersrPHYmYHVZqjTZBuZ2OaLYDCrwsEyYLyMyqMHZlUCF4o/CaznDr4qpY
yvU4uV4e1Y8DDp75aZB07HW3QfFJ0JzXofAdtcfp/vvnu229LUD8J/GVMN3r
46iWW19vjSsZmSeiYPBvABRicTK9yQRYEyw8R/1C4XiPGsIN9Yn/asNEKhfR
kNSezLmkmlaUFaZCtwl5RfpZnq8u4OHO/Sh4C1pKDIAqf5rmZSRwVeHVAnNX
WjbONx2tlHqcnIYwZU+oe0UZnwLei0R6W8kNLIyaOnBgMF5XVDK7cZtWs2l8
cUtKtw2JPQOLKBXnqAaqbRbFKewRjJzLlQnJ+TOKvZy+Pne5xE9MrT7Il9dW
2MFzPh0wK0OWiK+Z51NfSMucV+jTX8cXUDXdwEZP7zHmN6v0UEp5Tm0yEh6h
AUkAEqeO7ssQzVuJV4w7cqSwSfKCfDJKFw/EfXebU46hJpz1tvKQiI8gig+w
VI5EtrF6bP9hsrZMK5jldctZyJbwh8nkRL7NIRbczSiXWC5IQ6nlqjzMy3Uu
4gyFfyX1x3r17qWQnOYEx2UMhlaH7vq6zPvwW0nSo5syhkpUPKHyVoRfDkm+
XFWfLiBEfS/3oh4xvw3V5niXYyEjuU3BspEaVyqjA5Hm4iEcTzebu+Gwomq5
Jgn4R5f7OXARDV7aVCwl/dPfW8D5q50S4fAQGCAcmxwpWdbXY1zFx7RVBsB1
6sg1564PUywzowauNgoFZkhEnLCz6x6ZCD9rMWZfvCbyM8dYjIWPAR6I+axe
UDSjbb42ZvxWvb7iggf2MVBayJdlcMFyFTO/aVxZgEFoaZypes6R6BREAYZy
gVEoVwe15MopG3iQGJPd6NVbB6pfBeYbFdaaskYn3+Gdta3JQlUrXX0pWLMC
qTd4EjQErPMJBzKo9FaaBfH9ZhRjpd8yvkst3CtC3o1OlYaoGBoeTimVtQ/K
9beyKdUsz9kGofMCpvCq2TfbkUjrVG6O+k4RBeGKioG477Yw2860IY4u3XEq
xPkSlWW+JoFzA9/kf3M5VQK85Afe6Cq9rqryrjOKEVDl1oc6obF9c2y6IbXd
YV957uMs3DnLpu+jsvWvqsznop0FpeQtcO0/AS1iOjUNfq91u0ve4oXoyTNG
822d/8i63Wfp91rC7tBH1q/70l1yEWQYExmvx/iO77lI3Zc6f+8zp5vRl7aT
QfyWPPu1vC/TQ+Ad+s7GBth7f6+tGvuMtx5/tp+CXR88AK+x/BAmNsJOviC/
wUmwyS5Cug+q1e4gMC28RQfTr2PqPhMhMcu3DXwb+e2e0rZldEvXT8Pc0tBu
CnMt3yQPzqQg77mowt2HkwcXpG/qA5ORMfWG5MYy0bbekAq+4JzUM8IQk6p8
Esa+a/zW1ukahCS3kZsZfnatnOkebXXnMpj2uqOtsZ0cem30VNzr4SH26B/e
yRf9w3eabc1S1WUrS17Kw31b3oIRuQAVJHl8AlKKLTbx9RkuUh0JvUJZqFZV
Uhkr6amTIRVvJK0gWJLBMjJ9WUIU5AjnUA71IoWtxIMrASK9vnq4aVS7dqWj
1urh5Ls/9boTKhHtwRszLOHA/r9tNxR6JHaIgZgLlUAqfLuP90iE8TzgC9t8
EOgw8gOw7c612Nxr6BHFMrmUORB7PA/FBCJeyk4Ef+OXb4WfsasIo7rKOsXD
KW9V0UpFUAHRkOOXUyLQ6vK3ozDSJLMre3vJoljtD0nx05PktS8WFzQCiw5Z
QRQpWiKBhM4tS4lUP0HY/KKQeoz4Vjx3C5wt++m5aHmwlJIbeKN4QoxZCSkT
bfUu1/J6U7Qp0sUlHDhfIpaMh8irJj4XoDAPmo0CEYxUaKtFoxVYGEjt3Ely
l54ulIxMcEiIbmUUSZMPRBA4EHLDGglabdjMAqEz5FMJpBqHOChc5F35lA7A
Jnoz6GZiP733MbvCQz1zv80XK/JRi0slpMzQDSLdqwXNvyjk9NmJ3ZIwWK8v
KhXl6w+16jYv9Hoxe1SWNaCTyMGdLt/xuARQNkrpjLbi4JZBQ4b3gWpTcUSL
HRV0j5npVByLIZi9Ou7cPrEXqJdcLVeYcoQmy7HIv+cOoaC6alqWIbYMVrNf
qCe0B3qHQEwdRdvBh0c5SpJx5PBdbOCjc1iZdihnqgnc7HAVokZHxjVuK7Hs
ED2ikKgN06dO8cQbTbEKQSaOKF0XWKWKPAjNmtN2mKfigBVdoXUrp3hXMRjG
wgVXdYFp6+jiQHLIM4vdcKdlgRE6vMqczkFcgm5WNVRZP6jFtqmX6RWuxBz+
B7rPGrmm11w0b1/AL+fPXkwTXy1PjjLfwVw0Vq8Oa9jK5SDG6fTeX0pNQl8j
suwGsxFwtCEFv3fa48R7vs0FaP66KjNHniGfnysjWCF8db+hL1XPm1a0usEq
jiUdLM7pVzdojtdr5bn4faTqoN1qbPXB7Q5BSwrkSgDIZYSU7I7b0YrgH5Na
lOnOKTw2QCxES8q5Pj9BPwqml2nGP/OoKGzW8Qcyo7JaAhp062beJXRJc5cy
PVLQynMEz7AS2/nrk9cI6PLVBWKtkAPPMAVTEnKGSOH+5XonrC/oj2Kcb8yz
y8PjAS/Sjb8KAxNNXL0GitxM9fauXCPZS629JWETcbJ1dJoQ+bfzhtoCwmA0
t66zrBGgR5JXm+5WUO4VuzBPkmIe6W/IddMspB6hMKOa1uL6RI9jy3pnxteZ
Ect2t3OiL7fM+TIWoO6rK1ZdOdBKyyHYJ1t0VMgsbMcU2MDffGwVAwQa1Lyf
qIm37wCnmIVUGxYw1JySQF6miI/Q6FpdgSnQoikA9PyU+P4lk1a/CIroUdSc
pfLEzLEDqXLXMoW76KRur3jlI1zaQJFc9dGLX5b3MKrdz3Lb+YSBue15ueOU
VJI21fslo1J9ruJt8EL78v8LhJTG5Q3Z8iF1oGjo6ihXCTS04hXbkChFCxtc
/qSBunmMXWfVNs6b3l1BFvfkNGjpaiNZUoV6WzxEQy9jmZ4hBd4XPL+mPF2g
g4WvPeg241ahQ92LOymdGW1HQSXAcq2X75ZwnKdur7WT0GA3kdHplP3rad19
Y2gY4iUoPYBkiIFxmd7xcir7YBAIZbCl6kqW56uh43Dg0g31opCQ/BERWWyw
RaCHg97+X27QOMmXtpIEj/Mp5atwO9wBCjvgH+ixEhk4UEd6EQU6DoLq2seY
qvCKQ0XHB3g+1itkrjh9XwTFJWMGOjugTGsZkV0jv77sqQNhMN16Kb1pTA8c
icUYP6tN7uBHQw13SZHrnYISdknw0/kIb0AZ1SmmPxpwUq+PeWNj6CWXvzGs
THyRqfcQoaYegLq3qJL0SlV4ogi3M3h0At1UYAlG6DnQ8jsdkOTgXUUhwh7X
ttDYNSkqXMWXV1eGIDaqWC+1Pd8F+Hkw5HCloQFIqVlNHv4dlRkin0U4itRL
8HH9WMVerinHxK1Ahrv72V/LrCoKJ9QmgjrJEixwYe6baYcJ1mgsUeedCz4D
cfbragSYqTM5vestdlmZVSBLdvHytBOhNcPZXGU+58wcjKxdhbSzg0E6IxeD
DRqtebrARE6rgeZQ7RVgusuKosXakRr11nuCBimcs+PIjSkxW8sCx/bRDhqO
FX+xV0UkiYg81+7e4Lm1CHFz73Dwfp+HO5NYd3/upI1A+45QEK3Cp+mY/BHh
ToHxlqTQz52v+HM38u3oaDRYkSSvHdkmf5KjvSXKam1EIawPXZVf8gltPH+f
oiQ4QcYHYhVlTtsQ9uRWXMK40J8eK2mi0vGPGM/HoLjx2IV5jDVXHJ1qKxNb
UemijteWKzwSuCTyGjOIzSxJK6OIR449c1YkwfBmg2WKAljLdM28oXvDQ7KH
oFjIE5Cgjlrm2VXO99AIw3EFRNi1qwz9wyoJ+UQ9zqUzhxwN0derG/HQEl+b
Rje6iJsa/8QrLHydxtEbpvRqncjoCE7bZ11WHTlqVf+jUiUCagNVZE7I9JB0
1910duC76joe+t6VPoT2YQ8v/V5K/d7g61qCvgeLy5VDycpLM+fCNgQTbh0H
jFIqm9XSjcWDKrCkvxaR9undTiR7vURiP1S4ElRAngS0H3VOiS85ShY1H10H
Dq8XfQxnnpqLyaWW9txNDJvFddfAlHNyPePaI5pPyeP0ziXCy/m7IPX6O23e
MhMtR/PcEhCjNGQ+SwPQd5+JF/D5004RNlcopONaYhxz3JazEU1ZE4xxx2zh
wkt8Xt1lReyMXWYcD0X1ZFktQOHHG9BE+aE2byu+nDgXYBwQZDLn2znFvrmp
yhs6YeyL8fbJftq6u1q444nh+G/j8IZ6OuYds2HgStGR241q9sw4zsBq1NaL
vrhyAXlIzJ3TN75KZDhlwZp2bMq5o2BGF12CkpYdLXvEAtObweTK56na5HqS
I47UqS7F+6a5m+6ix3+6F2an8Ro5Ms19EhvvwfcEpGTXuftoeNhaICdyzxCG
m6GZxtqCebisWtpbqUxFCZrRFV1WwUKuhxrYxKHsUPOuCAL4VEsVfFjGyFu3
+HtcoRmhhS2rr/HlLxzWPTpPjaEQwrno9ozKgac+jzewS9yI9AZkUWvgjuAV
jVzn05DroWQwDTWTNeeThYQcOZc0xV5O77vYA0b7ZQyjTdG+KkGnHcDQdjdS
cl90E1+Fos33g9R+mCb8hhWw4bTOj3SNx764vl2fX4b7u79+v6edERVWOhHQ
j1pt39V44ZTClrZ8PoZZs/9na0WnsATjDey9Ew+tshMvzDN2lr5Kl3DEiM/q
kLaMtrOo7uj0ntTe4k8P/ra1t30/A70RQnLd5jE0crRY89d3g9dmDHz3cWZ2
Zxd6/Dq5WF8CL4HvumWp7rqd9epWvSWmubOz7iYPf/VRJvbhq3j/Het+xqDn
H58YL86fDZyc4e5eY4x4M/T4vWh/1+R+CROJe/tGMpQHJ6jd7TOJsc+9edYv
6exeL+/Vm5a+5TvD3Sp91R387u7+uYI07tv/9f+pSO/VwPugzz9fpKOCWJYF
CUsWmTTvr7fQ/hi57H5h+/QwyUKyMfVg6w9jL+z6gRJxFqD4ghJB8igMivNW
Rm6gGu+xo1aIeHt0+s3zb9/unJ+7cwuBwbldmnXP3t7iDZE7O3v4UWaGWfS7
+9r72y09/WfzGj97eu/Z7Z4fC200mHrKyR77JrLxOZem2LVvv6Sve27b2A9b
u/mHnO0t/e035oHPX/Zudd+ESBrBrlbvvT57tUoTV5ksNiDdo9m/38N3+eGD
3RlvenxiXiLnf+xCJqjyOvlcUZPoQxg4PEwXYnnkg6IHx6qhxj5Vq4mKyIeR
EqtWmQPdkcEdFJegCxgKjoWzgzq+jDqE206jQZgvIwaGvA3FvuzuKnYGMYRB
4XpU7KoN/uIPqra6rZzWvgWxtHBGpx5Wv3oQJdpQ/s3U6g1JhawILPLLarUe
J99H0APyYSKKgK5WLq50fFnu150g4AKBigquxTB8wYwyLFcCXox4YL9fQ540
rTAXl7VNS9Aymt6WEJjfDT/E8oajs/2I7FvLy29DFg9X5mgIk9spJ9+9sKN/
/YJGWLGAgfg00dfsYzF9bzNdOU2EEpd0ioKoFiEaq3mrpfJ3FrsVcHGcTIRx
2Wy0irEA+V3UMqpePO2Wv9m3VJnVV6NyOXxP6bSTqdEObNJvGiSv66qWAJ2d
iqHg7ucnxs599NFFdQPJh9gucZOPUJyXk2lCZsJoHTN/jbguvK2dXIEEHWEI
eAAV1rqLEqkbn6iiaSrCg314V27/I6aBQUGtdCaBW2NBl9D/bZFhkVmSNt0y
aEwgach4GIvu9tZc7nU31ev0MKqOu7vAsLb0m8YCwg/OXz9+kB4e9ooOK038
FpP+kK2rKFxoHRMCvoewQY9JWKlgvpmnUy24W8isM3S7Mwt/s0FF4ZN9yxgf
c9RgAXwGV0kDPXRNiBICF1BxMZAOpUZduxonGHQT9hBz45g/pT4bwm0ghVvL
mHGRwCRUQ4VxxYv8ilbceXwfXJw/4zxPODKYtyNoOot6Wxlm1yosc+hXN/cL
S2QJGXXCbrhiMoftj/2QR6vZRaVp6IhI9SRl3XGxNk1sgCVcpFRDSosE9ori
MS4hWlFNZm14c9ztXlOWkbwlaRu1EV8HNZuhJkGpCoiU0VBauVGadMSMYfxN
r2w0qUi66XHyilSSfrpJSlzL9GpEEEaVfIf0QJMxXJPZAAuGPvWV+sfU0RCS
HNFFG+R/y4G7tbrF0PEn5h7IFQW4H7jpQLRS8mTcXVRCkr5OY6U1gDpq9FCl
2gjlcJnjsQ/34tBNTdVp78UAlFD8iUZ6cwqFgwy4oZuLm6gQVwjjS5H6AqG7
dcFICs4LXjIwzF2GE+5skGC7KwwIRpKmxKlmqmkqPtOkZa2SyzDbspLACRXT
PCbAIrnWubROyTHDceJtCS2T8TLo9yniaHXr6O5oDaqzmaLRXA7Ow1QQ7pYN
IiHG0BmMLRlpl9O19J6tmvK4EJNjiavNiUtS6eQ0dCq6RSzC34Skdy/GCR7x
kobrJNZyU/VAZhLQ1U1RV0tJ8rno2X9kkYYicIT943YRJspcNRSFQ7if8Q4t
XGt2T6oXS6l62r0rZOBma/UBuUuX40u8hOKakCo2uGqhrjUQ2QtFYXt8ldi6
Lym74qVmo72i7OIHL1++OsRqjnhCcTuRRoB5lqQwceXBkZvprGrkAm1MzG3F
7UOQDQmRAGDh7CXQvupNpHLwpYUub4DeMyyWKGgHj2hCjyhz99HVChEMnyOo
99HN44NDTvffWNHsgeLvKkQ5ndqqYbp8hmN1KTMoVosRcAGBQDFWO5GyMlqZ
rKovwONX+cyE2QIIhZP+NoxcFLHseSWltileRGFHczJOMPkKR1hWt3Rq+arN
/tbCnv+hus0JHsu1yWkRVY3C6djR44LuswotBXjwSnKjwwQHV0rvt5G1ajhT
msunGvAv4KBISxByx/RLyhzsdtXJn+CBM9lFzpASc62oyHazNroniJxoG06y
BXSsZa3q4lvj8elH4GA+dxfPAwl/hwK1aho6b76WKcuYtVwpfkBLdCA3NQi4
6l/AOrmgaSXfEU9Mvq2E3z34l4vvvj3U8ch9CTmKnvhQCA/gZnHzjObCLmY5
qGp4HTxvk6tpYpUMgQ8u0s9g2l9+cokktXr8xcFx8nSTePWaX6eupqoJ8gGo
LqmsaJTtx093L5wJnR+j2KFKlCtFqqYR17/JDYBENRVZuDw4/RQMLyu0mVIN
9JxB/cdcUY5F0aenLq2HpB+w07RYRtxFb+cYcvhR6r1mNE+tVkc6J3fmJqrN
g5f0Uk2AOFFK6nqcZ2axnVvtXBJF5J1sCRKRI3sjaGpq7ganXdEsqTjrlQ0F
6Lrou5tSU6ZKnymUSYnktyNgx57GhjUWC0y2Ro/XuIQfxqP9R/Fb6OU72/Bo
vYv8egqOajOn3SHdD6H2wTAw9YmPXYc99vngDjmowYvtvvg4HQ6VAhyJf32c
Du8SH5+4i3647+c+M3zYm8rH6vDR8L/9TX7umx9+cYcj/UXz+cF9c68eBzq8
Gfn3wB83Az/cp8OHEc196F/w2XJGYwBIQvwkryUW+yF/IeJl2xn9h8xw2xkd
2MNRRE/44+d//+9bntvxGejSjzAabfgDuox/25PRjHXZ/zw4oxtq1ZX+Ir2s
i9noZZP37nCvJfpg3M2Oszj6uc/xG+9wjyKxe9WR3btDXKdwggZXbY9H7tHh
P32G+38+HKu1vcPRe2rvtt5g+6Hd7YZR7f3Dlu4Cl+8OevSXfZW4wf5gjOwO
YS+IGzX/FzFUTWdCd0nAIKEfbmSi2+fX25SBTXs48svwBPeCcUi1clfxlEHz
7K1i+PWZlhSDnydP2TCmfLtZsWJ/ONgDYIf17j/z/ohpuOQl4B8wpB0eDhZk
1/suIXxNe3SjlaiXGHpFudFkP/hqHe4ukwqyZ5jILPVHJa5BbhcJ4Volp2XG
tUf0iqxw+5ehG6goVnRbSDSu3h0N8UxcYCWNQ9fOQ9jxlLoSY2xic1HAzmUB
WqnRN2kOQ/Vva2kHKaNKqAquuQK2c3WDUQfDQLBHRbxOGIwoCylq1c09fxOh
G9S4e+My3Z5LmjTQkb9e2BLKNeucLwWSnMI6F2dHuHp0L7t28NLWoTzwaahc
6jy9rv6jxP4t8OeuLVNvnmAF0JfgrhLh6ZLBTFeUhOtDzVNIN0vxDLDpt3oZ
6ytpmJ3oTXgBHR5yU+ObvMxv8MKI+R7uCFzHtGwqN6pOlachv7Flo4v3wuJl
aqq77W0m0Xlw/YhbvHUbYe6QxvwhPjV/zCOCobH5uvSsZRq8SZyjfCu3flEs
FKsPrMnntNVbQiUp4V+08fROVBy3M3jOt6Z1nYbVnjJwpmQXiTutMAnC1uRa
r0vHwc5JJHcM1S37mfPkm6JtncHSyiisYG+jsT0sraP+wOB2vqnkziBcEt1c
YpgZHOzj5Dtc9duiEZiUANHsRtHoDa4jZufTQVl6zhukqm+hRyTlhgIPtGul
Flijk07Xm96i17nOab1wNcVJnFV0uaz6irsOuXgrHNAnIFksHbmLfhi4pExI
h3mOHE9KtG25PFH/5ukoh320SISuXlRBcXDrbHBCDNSwv7InDh0xxEHYBKHA
MPF5aTQU4IO4JLNr7kEFjh4J9Gx2z79sjsOkvNGI/jcxcOGZ3NI14YoTcSlf
Y6sOjGGXitGiReAGLWOQDd1EnXaACQxjonJZoYRB1t9p7xZ2ZRq6t1d3L9xs
qyvmRaaB2GV+HIwL1dO8iNfKGyooOHrXubYvpluD1ETAibhwBAVq9FK/780/
H8/NO8YlbK8XTAWuOHxnbf9mqfGEbXfrl9bymFWGWjDilNorGG4iDEK4L5oQ
M2mb2k8aWZhyXWUrbTrIg7g0RFQkLToQofyHStKOnqAyk9zi3r2MQMP1iqDI
MZSDJK62Gy5mvr0ugkpFO4SaE4Eq4rsDpuzlxmBL8uDll4f9uulx0QWB0kpV
GBCxqkE9+GN1cQj0DiTDMScgNzkZdI8lMhwXS6MaDLbHFFOWb6SyhY3DlxTR
cIVgZDKTI8B2XfSyF2jEQpoIQURhNZm8NbVxnqdN4S4bDOVQMcRClY2jMsYa
XUndhQikrlyGEkBSjNmIvReqEZHBRyJgMZAJsmgJardw1SaiXKxJ3VWzB4rZ
nFGDMPFCqB+L81662oPIZrQ2wVV0ekjyWWUbieQYx77O0xL+DhhIvmIPO7uh
OG24hQ9haUDbqJn4u+AbLvXE6+KwdJc5F0iKQ0hUIHpV9rPyCfJisiytLwsz
uESeaRSe4KQELsMqynjte+7+tujrId6rvS4z2k4tef02gAhngiCR+h1N7peM
WUNj1zKSCUXoSsTiCNY8wqY5uJQA8yMY7tONIDw8Fmsgns+FMQc4Z+cCwKko
dgFZw2F8rQ0jmmUca+6CfyOwixkx7mo/OaGwL+uZ1r3NQOxm67RvS9El2tWt
nVvP8nBSWboyOLbUhVHrkOoT51bUI0QBlTVGeBwumC632TFZjaFyokrDaQe+
grVUObreh5KNoiCAqGqkNtRGsiGAi1akQa5M8WiHsOGqb9RBjAliUUux5NRV
QpcgMs/DwQ1RHu9jgZG6xUcT1QiLL1uC7TQGgQgrbvp4xS6KKL5eWidlBHXe
dgF28elCyMUlh3V7+Dy9FgIpj5NG+EEuZx27awharYWXBCPRw8nhu7E8GtqQ
kUrOgmSqOH4etpsUEZE2LvHFc0amZY0WWM7og9NvXx+awsBevzMRBeGhV2ev
D6f3QswN6k5NWEnhrLH1YM4H44rdekesfXCMXc828Xx3wLm0Plcbju4ociio
zpox8kyAkXlUCkpOEMifrKrtDOsK+5JUWswyXB2gpVIdKNS9zkyIl8tgJipK
UY0kPnd8oYVyy1J06LjA34K8CXR5sF2QMHiPchiF6AKrZnDN81KTGPrHmT2d
0wERS/BWICZNJJGC3VwKEX4CEppqpWUbJWd9XTaMKwtLaNiMgOGJqin6fBYY
p/dKDt4403CJtZ7uTfRIhi7QS1WvKsJODS1KnJ5DPg0F9dti5+be4wOF1/yW
vL+CTo7zGDyokdVGBxMTNwFZXyIOQB/nO3PxJDuxQmgkzn7ILPHD9AFXYlqA
UcuOeb6Jy7tB+1jc2zCcXUhZVIhRG+KDSVtUyzXgQuVBGtJ9qc8UpdWpVO2Y
BE4ImiXLlJM24KyyZqRAKsINg4UAQ8PzexZpz2C/y4yPZHhHzAFERB611dGA
rLykLUJnUaPtAtt5pxcsR8h6X3duVVVzsl/m6TtfSdCbQlZbvPiRr7KeRsp1
pq7j43Dbq9xsNNAjplrllBtqtGZWduSspQK6RyJmiqYqnROX6yweGS9RvTaN
YH+vUvzalbhbsO1+1Xcm4YUN7LBs+TgrFT+JQwNhgExA6yUlPqVLGGa5kYsv
SOqZxqyC9xhEUnGTzjZHjtCMHA2tz5PAlD9WE9ObqsioRllZNaLa8f6Tx0Vu
EGdBb/XRjHnL0e05EKmqf3J++u1pj/zoaGfVbE1e/6zKm8ijly439N4R5wiT
TpblXO+9YSeqZLIFMOtk8v8AwQ44w/XzAAA=

-->

</rfc>
