<?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.4.12) -->
<rfc xmlns:xi="http://www.w3.org/2001/XInclude" ipr="trust200902" docName="draft-mcw-opsawg-icon-requirements-04" category="info" consensus="true" submissionType="IETF" tocInclude="true" sortRefs="true" symRefs="true" version="3">
  <!-- xml2rfc v2v3 conversion 3.35.0 -->
  <front>
    <title abbrev="icon requirements">Architecture and Requirements for Autonomous Agent Observability, Control and Intervention</title>
    <seriesInfo name="Internet-Draft" value="draft-mcw-opsawg-icon-requirements-04"/>
    <author fullname="Qin Wu">
      <organization>Huawei</organization>
      <address>
        <email>bill.wu@huawei.com</email>
      </address>
    </author>
    <author fullname="Daniele Ceccarelli">
      <organization>Cisco</organization>
      <address>
        <email>dceccare@cisco.com</email>
      </address>
    </author>
    <author fullname="Luis. M. Contreras">
      <organization>Telefonica</organization>
      <address>
        <email>luismiguel.contrerasmurillo@telefonica.com</email>
      </address>
    </author>
    <author fullname="Daniel King">
      <organization>Lancaster University</organization>
      <address>
        <email>d.king@lancaster.ac.uk</email>
      </address>
    </author>
    <author fullname="Giuseppe Fioccola">
      <organization>Huawei</organization>
      <address>
        <email>giuseppe.fioccola@huawei.com</email>
      </address>
    </author>
    <author fullname="Cheng Zhou">
      <organization>CMCC</organization>
      <address>
        <email>zhouchengyjy@chinamobile.com</email>
      </address>
    </author>
    <date year="2026" month="November" day="16"/>
    <keyword>Autonomous Agents</keyword>
    <keyword>Network Management Agent</keyword>
    <keyword>Observability</keyword>
    <keyword>Control</keyword>
    <keyword>Intervention</keyword>
    <abstract>
      <?line 65?>

<t>This document defines architecture and a set of requirements for Observability, Control,
and Intervention for Autonomous Agents. The Autonomous Agents can be any Agents such as Network management
Agents or Security Agents.</t>
      <t>It identifies gaps in existing mechanisms and specifies required interaction capabilities
between Agent supervision systems and Autonomous Agents (such as Network Management Agents) across multi-vendor
environments, specifically observability, control, and runtime intervention. The
requirements aim to guarantee comprehensive, lifecycle control over Autonomous Agents and enable
observation, constraint, intervention, and correction to ensure network operational
resilience and continuity.</t>
    </abstract>
    <note removeInRFC="true">
      <name>Discussion Venues</name>
      <t>Source for this draft and an issue tracker can be found at
    <eref target="https://github.com/QiufangMa/Agent-Control-and-Intervention-Requirements"/>.</t>
    </note>
  </front>
  <middle>
    <?line 79?>

<section anchor="introduction">
      <name>Introduction</name>
      <t>Autonomous Agents are increasingly deployed for network management tasks <xref target="I-D.wmz-nmrg-agent-ndt-arch"/>
— including service provisioning and network configuration change, service assurance and automated
incident diagnosis and resolution. While the introduction of agents significantly improves the
efficiency for network management, it also inevitably brings challenges such as hallucination
and execution unreliability.</t>
      <t>Existing mechanisms for agent assurance typically rely on static guardrails (e.g., input/output
validation, operation allowlists/blocklists, pre-action approval), while assuming that all agent
failure modes can be predefined. Unlike deterministic software systems, however, LLM-based agents
exhibit emergent behaviors that cannot be fully anticipated or encoded in static rules. When
agentic systems produce novel actions or reasoning paths that fall outside predefined static
boundaries, it might lead to risks such as unintended configuration changes, policy violations,
or cascading failures in the network.</t>
      <t>The operational problems, architectural challenges, and technical gaps regarding the observability,
control, and intervention of autonomous agents are thoroughly detailed in
<xref target="I-D.wnd-opsawg-icon-ps"/>.</t>
      <t>This document builds upon those identified gaps to specify a set of essential requirements that
supervisors need when deploying agents in real networks for agent observability, control, and
intervention. Furthermore, it also defines an architecure for ICON — Intervention, Control, and
Observability for Autonomous Agents.</t>
      <t>This document specifies the architecture and communication requirements between the agent and
the supervision system. It does not standardize the internal LLM architecture, planning
algorithms, or training methodologies of the Autonomous Agents themselves.</t>
      <t>This document does not specify a particular protocol, data model, or implementation API.
Those topics are orthogonal to the operational requirements defined here, which are
intended to be solution-neutral.</t>
      <section anchor="observability-control-and-intervention-workflow-of-autonomous-agents">
        <name>Observability, Control and Intervention Workflow of Autonomous Agents</name>
        <t>When AIOPS Assistant exchanges the user intent with an untrusted Autonomous Agent
or an Autonomous Agent (e.g., Network management Agent) with lowest trust score, the Agent Observability process and
Evaluation process will be intitialized to collect and evaluate Agent behavior information.
In case of high risk operation or agent deviating from what Agents are expected to do, the
decision will be escalated to the human. Human operation will use Intervention signal or
control signal to provide guardrail protection for Agent behavior.</t>
        <figure anchor="flow">
          <name>Sample Workflow</name>
          <artwork align="center"><![CDATA[
                           +---------------+
  +------------------+     | Human Operator|
  |                  |     |               |
  |  AIOPS Asssitant |     +----+----+-----+
  |                  |          |    |
  +--------^---------+      +---V----V-----+
           |    +-----------|              |
           |    |  |--------| AI Guardrail |
           |Control|        +-----^--------+
           |Signal |              |Report
   Intent  |    |  |        +--------------+
  Request  |    | Intervene |   Agent      |
 /Response |    |  |Signal  | Evaluation   |
           |    |  |        |   Process    |
           |    |  |        +-----^--------+
           |    |  |              |Report
  +--------V----V--V-+      +-----|-------+
  |Network Management|      |    Agent    |
  |     Agent        +------>Observability|
  +------------------+      |   Process   |
                            +-------------+
                   Observability
                 Signal interface

]]></artwork>
        </figure>
      </section>
    </section>
    <section anchor="conventions-and-definitions">
      <name>Conventions and Definitions</name>
      <t>The key words "<bcp14>MUST</bcp14>", "<bcp14>MUST NOT</bcp14>", "<bcp14>REQUIRED</bcp14>", "<bcp14>SHALL</bcp14>", "<bcp14>SHALL
NOT</bcp14>", "<bcp14>SHOULD</bcp14>", "<bcp14>SHOULD NOT</bcp14>", "<bcp14>RECOMMENDED</bcp14>", "<bcp14>NOT RECOMMENDED</bcp14>",
"<bcp14>MAY</bcp14>", and "<bcp14>OPTIONAL</bcp14>" in this document are to be interpreted as
described in BCP 14 <xref target="RFC2119"/> <xref target="RFC8174"/> when, and only when, they
appear in all capitals, as shown here.</t>
      <?line -18?>

<t>This document uses the following terms defined in <xref target="I-D.wnd-opsawg-icon-ps"/>:</t>
      <ul spacing="normal">
        <li>
          <t>Observability</t>
        </li>
        <li>
          <t>Intervention</t>
        </li>
        <li>
          <t>Control</t>
        </li>
        <li>
          <t>Human Oversight</t>
        </li>
      </ul>
      <t>This document defines the following terms:</t>
      <dl>
        <dt>context:</dt>
        <dd>
          <t>The network operational data, interaction history, and situational network parameters
that allow Autonomous Agents to remember the history of a specific interaction over multiple
turns.</t>
        </dd>
      </dl>
    </section>
    <section anchor="existing-mechanisms-for-agent-observability-control-and-intervention">
      <name>Existing Mechanisms for Agent Observability, Control, and Intervention</name>
      <t>After receiving a user request, agents will perform a chain-of-thought (CoT) reasoning process,
then it will autonomously decide whether to break down the task into subtasks, or dynamically
decide to invoke multiple external tools, retrieve vector databases (RAG), or request more
information from the supervisor.</t>
      <t>Existing telemetry mechanisms are excellent for tracking traditional network infrastructure
or software which are built for deterministic systems. However, as analyzed in <xref target="I-D.wnd-opsawg-icon-ps"/>,
they are facing severe limitations when applied to Autonomous Agents. For example, existing logging practices
only record what action was taken, completely missing why it was taken, including the agent's internal
reasoning provenance and confidence scores. Existing tracing mechanism designed for static and linear
execution path also cannot capture the complex and dynamic execution trajectories of Autonomous Agents.</t>
      <t>Existing AI guardrails primarily operate at static boundaries, such as input/output validation and
pre-action checks. These mechanisms are designed to constrain Autonomous Agents within predefined operational
and compliance boundaries, but they assume that all possible violations can be anticipated and encoded
in static rules. As AI systems increasingly operate in non‑deterministic environments, these static
measures are proving insufficient as they cannot detect, interrupt, and recover from unanticipated
behaviors.</t>
      <t>Although there are some modern agent systems that provide interrupt or kill switch capabilities, they
remain framework-specific, insufficient, or proprietary.</t>
      <t>These gaps motivate the architectural framework and requirements for agent observability, control,
and intervention defined in <xref target="architecture"/> and <xref target="requirements"/>, respectively.</t>
    </section>
    <section anchor="architecture">
      <name>Architectural Framework for ICON</name>
      <t>This section describes the reference architecture for ICON. The architecture defined in <xref target="arch"/>
serves as the structural foundation to derive the requirements specified in <xref target="requirements"/>.</t>
      <figure anchor="arch">
        <name>ICON Architecture</name>
        <artwork align="center"><![CDATA[
   +-----------------------------------------------------+
   |                    Human Oversight                  |
   +--------------------------^--------------------------+
                              |
                              |
   +--------------------------v--------------------------+
   |   Agent Supervisory Plane                            |
   |                                                     |
   |   +-------------+    +-------+    +------------+    |
   |   |Observability|    |Control|    |Intervention|    |
   |   +-------^-----+    +---|---+    +-----^------+    |
   +-----------|--------------|--------------|-----------+
      Agent    |         Agent Control       | Agent
 Observability |           Signals           | Intervention
  Data Streaming              |              |    Signal
   +-----------|--------------v--------------V-----------+
   |  Agent Enforcement Plane                            |
   |  +-----------+    +-----------+       +-----------+ |
   |  |           |    |           |       |           | |
   |  |  Agent 1  <---->  Agent 2  <--...-->  Agent n  | |
   |  |           |    |           |       |           | |
   |  +-----^-----+    +-----^-----+       +-----^-----+ |
   |        |                |                   |       |
   |  +-----v----------------v-------------------v-----+ |
   |  |              Function Modules & Tools          | |
   |  +------------------------------------------------+ |
   +--------------------------^--------------------------+
]]></artwork>
      </figure>
      <section anchor="human-oversight">
        <name>Human Oversight</name>
        <t>Human oversight represents the top-level authority of the agent management. It provides the
post-execution feedback, injects global policies, reviews agent escalation requests, and issues
high-level intervention commands during crises or anomalies.</t>
        <ul spacing="normal">
          <li>
            <dl>
              <dt>Policy and Constraint Injection:</dt>
              <dd>
                <t>Human operators could express high-level operational constraints or boundaries. These intents
 are translated into machine-readable policies by ICON client and sent to the policy enforcement
 component.</t>
              </dd>
            </dl>
          </li>
          <li>
            <dl>
              <dt>Escalation Handling:</dt>
              <dd>
                <t>When an active agent encounters an ambiguous scenario, a conflict between different policies,
 or a decision whose confidence score falls below a predefined threshold, the enforcement plane
 suspends the task and escalates it to operators. A human operator could either approve, reject,
 or modify the agent's pending action sequence.</t>
              </dd>
            </dl>
          </li>
          <li>
            <dl>
              <dt>Emergency Intervention Trigger:</dt>
              <dd>
                <t>In case of an unforeseen and deviated agent behavior (e.g., an agent entering an
 infinite inference loop or executing based on outdated data or incorrect assumption), human
 oversight allows immediate, manual injection of high-priority override instructions (e.g.,
 global kill switches or behavior corrections).</t>
              </dd>
            </dl>
          </li>
          <li>
            <dl>
              <dt>Post-Execution Feedback:</dt>
              <dd>
                <t>Beyond runtime intervention, human operators could also provide a critical retrospective evaluation
 feedback. Following an incident, anomaly, or successful resolution, human operators may inject
 multi-dimensional feedback (e.g., assessing the agent’s reasoning paths, correcting intermediate
 planning errors, or evaluating the quality of tool selection). This retrospective feedback could
 be used to update the prompt templates or refine downstream guardrail policies, preventing the
 recurrence of similar behavioral drifts.</t>
              </dd>
            </dl>
          </li>
        </ul>
        <t>It is worth mentioning that human operators rarely send raw agent control or intervention protocol
payloads directly. They could use more flexible and human-friendly formatting such as natural
language which is relayed to the agent supervisory plane to translate into structured control or
intervention signals for normalization and distribution.</t>
      </section>
      <section anchor="agent-supervisory-plane">
        <name>Agent Supervisory Plane</name>
        <t>Agent supervisory plane is the Agent assurance capabilities which are used to manage, monitor, and
regulate autonomous agents on behalf of human operators. It is logically decoupled from the
agent enforcement plane. Note that agent supervisory plane might include other technical and
operational pillars such as agent lifecycle management, which are out of the scope of this draft.</t>
        <ul spacing="normal">
          <li>
            <dl>
              <dt>Observability:</dt>
              <dd>
                <t>It receives observation streams transmitted from downstream agent enforcement plane. It provides
human operators with comprehensive agent behavioral visibility and the ability to identify
operational anomalies or performance drifts.</t>
              </dd>
            </dl>
          </li>
          <li>
            <dl>
              <dt>Policy Control:</dt>
              <dd>
                <t>It acts as the centralized Policy Decision Point (PDP) <xref target="RFC3198"/> that translates human
operator intent or operational guidelines into agent behavioral boundaries, guardrails, or
operational constraints. It  dynamically pushes a set of structured rules or policy
constraints down to agent enforcement plane.</t>
              </dd>
            </dl>
          </li>
          <li>
            <dl>
              <dt>Emergency Intervention:</dt>
              <dd>
                <t>It hosts the emergency orchestration logic required to reactively instruct agents in
response to boundary violations, anomalies, failures, or operational risks. Upon
detecting critical policy violations or receiving manual override commands from human
oversight, it generates specific instructions (such as pause or terminate) and pushes
them down to the enforcement component. In addition, it also receives upstream messages
initiated by agents, such as escalation requests that proactively require human
intervention.</t>
              </dd>
            </dl>
          </li>
        </ul>
        <t>In practical deployments, the agent supervisory plane may be embedded within network management
systems/OSS, an external Agent supervision or management platform, or even an upper-layer
supervisor Agent.</t>
      </section>
      <section anchor="agent-enforcement-plane">
        <name>Agent Enforcement Plane</name>
        <t>The Agent Enfocement Plane is the runtime environment in which Autonomous Agents operate, perform
reasoning and planning, collaborate with other agents, and invoke capabilities exposed through
the Function Modules &amp; Tools layer described in <xref target="functions"/>. Through that layer, agents
obtain network information and translate their reasoning outcomes into operations on the
network infrastructure.</t>
        <t>The Agent Enforcement Plane receives high-level intents originating from network operators or
upstream agents and executes the corresponding tasks step by step. An agent may delegate
parts of a task to other agents. Each execution step may involve invoking tools, function
calls, APIs, knowledge retrieval interfaces, or reusable agent skills exposed through the
Function Modules &amp; Tools layer.</t>
        <t>During and after task execution, the Agent Enforcement Plane collects execution status,
operational logs, tool invocation records, and resulting network observations. It provides
the corresponding agent observability data to the Agent supervisory Plane for supervision.</t>
        <t>The Agent Enfocement Plane supports policy enforcement at critical points throughout task
execution, including before task processing, before tool invocation or network actions,
and before delivering a final response. It also accepts and applies Agent Control and
Intervention Signals received from the Agent supervisory Plane.</t>
        <section anchor="functions">
          <name>Function Modules &amp; Tools</name>
          <t>As depicted in <xref target="arch"/>, agents in the Agent Enforcement Plane act on the network
infrastructure via the Function Modules &amp; Tools layer rather than interacting with
network devices directly. Agents invoke this layer to translate their reasoning
decisions into concrete operational actions on the underlying network.</t>
          <t>Although represented as a single functional block in <xref target="arch"/>, this layer could
abstract a richer and heterogeneous set of functions and tools. It may encompass,
for example, the tool and function-calling interfaces exposed to agents, network
management protocol adapters and clients (e.g., NETCONF <xref target="RFC6241"/>, RESTCONF
<xref target="RFC8040"/>), API gateways, retrieval and knowledge access components (e.g.,
RAG or vector-database lookups), reusable agent skills, and automation scripts.</t>
          <t>The internal composition, interfaces, and orchestration are implementation specific.
A detailed decomposition of this layer is outside the scope of this document, which
focuses on the requirements of observability, control, and intervention interactions
between the Agent supervisory Plane and the Agent Enforcement Plane. Consequently, this
layer is intentionally treated as an abstract entity in this framework.</t>
        </section>
      </section>
    </section>
    <section anchor="requirements">
      <name>Requirements</name>
      <section anchor="observability-requirements">
        <name>Observability Requirements</name>
        <t>The observability requirements are organized into the following categories:</t>
        <ul spacing="normal">
          <li>
            <t>Execution Trajectory and Decision Logic (<xref target="obs-trace"/>)</t>
          </li>
          <li>
            <t>Data Governance, Accountability (<xref target="obs-governance"/>)</t>
          </li>
          <li>
            <t>Observability Infrastructure Requirements (<xref target="obs-infrastructure"/>)</t>
          </li>
          <li>
            <t>Agent Metrics Collection (<xref target="obs-metrics"/>)</t>
          </li>
        </ul>
        <section anchor="obs-trace">
          <name>Execution Trajectory and Decision Logic</name>
          <dl>
            <dt>OBS-1: Step-by-Step CoT and Execution Trajectory Capture</dt>
            <dd>
              <t>The framework must support visibility into complete agent
execution trajectories, including reasoning CoT, actions planning,
executed steps, and network observations.  In a network change
scenario, e.g., it must include capturing the specific mapping
from the agents' reasoning chain and action planning to the
generated network configuration diffs (e.g., CLI changes, Yang patches)
and the subsequent network state observations, enabling end-to-end
traceability from thinking to network effect.</t>
            </dd>
            <dt>OBS-2: Reasoning and Knowledge Provenance</dt>
            <dd>
              <t>The framework must support visibility into reasoning provenance,
including intent understanding, inference, confidence scores, and
evidence chains justifying why a specific network operation
decision was made. It must also track external knowledge sources,
version numbers, and matching weights retrieved and referenced by
the agent during decision-making and enable traceability of how
external information influenced the agent's reasoning steps.</t>
            </dd>
            <dt>OBS-3: Tool Invocation Capture</dt>
            <dd>
              <t>The framework must capture the complete input/output of
all tools (Skills, APIs, CLIs, scripts) invoked by the agent, including
tool selection logic and parameter bindings, and execution results.</t>
            </dd>
            <dt>OBS-4: Human-on-the-Loop and Multi-Agent Delegation</dt>
            <dd>
              <t>It must capture human expert interventions (e.g., kill switch, pause, rollback),
escalation handling, and feedback signals on agent actions in the workflows.
In case of multi-agent collaboration, the framework must track inter-agent
communication messages, task delegation paths, anddynamic collaboration.</t>
            </dd>
          </dl>
        </section>
        <section anchor="obs-governance">
          <name>Data Governance and Accountability</name>
          <dl>
            <dt>OBS-5: Telemetry Integrity and Completeness Protection</dt>
            <dd>
              <t>The framework must support tamper-evident mechanisms (e.g.,
cryptographic hashing) to prevent unauthorized alteration or omission
of execution trajectories.
This ensures the integrity and completeness of observability data.</t>
            </dd>
            <dt>OBS-6: Privacy Protection</dt>
            <dd>
              <t>The framework must apply dynamic redaction to sensitive data,
including prompt text, network topology information, Personally
Identifiable Information (PII), and credentials before telemetry
data is persisted or exported. The redaction process must be
context-aware and must not impede the diagnostic value of the
telemetry for authorized operators.</t>
            </dd>
            <dt>OBS-7: Accountability</dt>
            <dd>
              <t>The framework must support immutable audit logging of agent
execution, enabling attribution of network outcomes (e.g., service
degradation, configuration drift, new alarms) to specific intent
interpretations, LLM inferences, tool/skill invocations, and
actions for post-incident audit and compliance review. The
framework must support reverse tracing from network operational
state or newly raised alarms to the specific historical reasoning
or tool/API invocation action that triggered it.</t>
            </dd>
          </dl>
        </section>
        <section anchor="obs-infrastructure">
          <name>Observability Infrastructure Requirements</name>
          <dl>
            <dt>OBS-8: Authoritative Clock Synchronization &amp; Event Ordering</dt>
            <dd>
              <t>The framework must provide an authoritative clock source and a
causal event-ordering model (Event-Ordering Model) across all
distributed components. This ensures that agent reasoning steps,
tool invocations, and network state changes are associated
with a globally consistent timestamp baseline across distributed
environments.</t>
            </dd>
            <dt>OBS-9: Telemetry Pipeline Resilience</dt>
            <dd>
              <t>The observability pipeline must support adaptive backpressure,
dynamic sampling, and retention policies to prevent
telemetry storms from overwhelming collectors caused by, e.g.,
intensive agent Chain-of-Thought (CoT) reasoning logs or
high-frequency tool invocation traces. The pipeline should
additionally support self-health monitoring capabilities to
detect data loss, transmission latency, or connectivity
disruptions at telemetry collectors in real time.</t>
            </dd>
          </dl>
        </section>
        <section anchor="obs-metrics">
          <name>Agent Metrics Collection</name>
          <dl>
            <dt>OBS-10: Operational Health, Resource, and Efficiency Metrics</dt>
            <dd>
              <t>The framework must support the collection of metrics characterizing
agent operational health, cost, and efficiency. This includes, but is
not limited to failed tool/API invocation rates, action execution
latency, configuration rollback rates, token consumption, reasoning
latency including Time to First Token (TTFT) and Time Per Output
Token (TPOT), task completion rates and Mean Time To Repair (MTTR).</t>
            </dd>
          </dl>
        </section>
      </section>
      <section anchor="control-requirements">
        <name>Control Requirements</name>
        <t>The control requirements are organized into the following categories:</t>
        <ul spacing="normal">
          <li>
            <t>Agent Execution Guardrails and Risk Control (<xref target="ctl-execution"/>)</t>
          </li>
          <li>
            <t>Authorization and Access Control (<xref target="ctl-acl"/>)</t>
          </li>
          <li>
            <t>Policy Precedence and Concurrency Control (<xref target="ctl-concurrency"/>)</t>
          </li>
          <li>
            <t>Agent Control Resilience (<xref target="ctl-resilience"/>)</t>
          </li>
        </ul>
        <section anchor="ctl-execution">
          <name>Agent Execution Guardrails and Risk Control</name>
          <t>CTL-1: Action Risk Classification
    : The framework must require an agent to classify the risk level of any
      action (e.g., Low, Medium, High, Critical) prior to execution. The
      classification must consider the operation type, target device roles,
      and potential impact on network stability. Downstream policy engines
      must consume this risk level to enforce differentiated approval
      workflows and constraints.</t>
          <t>CTL-2: Maximum Blast Radius Limits
      : The framework must enforce a configurable maximum blast radius for
      each agent action, restricting potential impact across device counts,
      link counts, service impact, customer scope, and traffic volume. The
      agent must evaluate the blast radius before execution and abort any
      action exceeding configured thresholds unless explicitly overridden by
      a human operator.</t>
          <t>CTL-3: Rate Limiting and Concurrency Control
      : The framework must enforce rate limits and concurrency controls on
      agent actions to prevent automation storms from overwhelming network
      devices or the management plane. Agents must comply with per-device,
      per-operator, and global rate limits, as well as maximum concurrent
      task thresholds. Exceeded actions must be queued or rejected with
      explicit feedback.</t>
          <t>CTL-4: Action Cancellation Semantics
    : The framework must define and support explicit cancellation semantics
      across three action states: Queued (remove without side effects),
      Executing (gracefully terminate and rollback where feasible), and
      Completed (interpret as a rollback request invoking inverse workflows).
      All cancellation results must be logged for accountability.</t>
          <t>CTL-5: Temporal and Contextual Validity
    : The framework must ensure that agents operate strictly within
      authorized network maintenance time windows. Additionally, agents
      must validate the freshness, integrity, and temporal validity of
      context, network state, and configuration data before acting upon it.</t>
        </section>
        <section anchor="ctl-acl">
          <name>Authorization and Access Control</name>
          <t>CTL-6: Separation of Duties
    : The framework must enforce strict separation among five operational
      roles: Read-Only, Propose, Validate, Approve, and Execute. Each role
      <bcp14>MUST</bcp14> be tied to distinct credentials and permissions. A single agent or
      operator must not possess end-to-end capabilities across all roles
      without explicit supervisory authorization. This separation must be
      enforceable at both agent and orchestrator levels.</t>
          <t>CTL-7: Fine-Grained Access and Permissions
     : The framework must provide mechanisms to define and enforce
       fine-grained operational boundaries. This <bcp14>MUST</bcp14> include restricting
       an agent's scope to specific network domains, device sets, protocols,
       and tools, as well as YANG node-level access control specifying permitted
      datastores, YANG data nodes, and RPCs for read or modification.</t>
          <t>CTL-8: Authorization and Approval Escalation
    : The framework must support designating specific high-risk network
      operations as requiring explicit human approval before execution. It
      <bcp14>SHOULD</bcp14> support configurable escalation chains and communication channels
      to route approval requests sequentially to designated personnel.</t>
          <t>CTL-9: Progressive Authorization Upgrade and Downgrade
    : The framework must support a progressive authorization mechanism for
      Autonomous Agents during the deployment (e.g., from read-only,
      to restricted write, to autonomous execution), and the ability to
      downgrade authorization levels during operation based on assessment
      results.</t>
        </section>
        <section anchor="ctl-concurrency">
          <name>Policy Precedence and Concurrency Control</name>
          <t>CTL-10: Change Attribution and Distributed Locking
    : The framework must support change attribution tracking and distributed
      locking mechanisms for concurrent multi-agent or human-agent operations.
      An agent <bcp14>MUST</bcp14> acquire a lock (containing owner identity, target scope,
      and expiration time) on target resources prior to initiating changes.
      Conflicting requests <bcp14>MUST</bcp14> be queued or rejected with clear conflict
      notifications.</t>
          <t>CTL-11: Cross-Domain Policy Conflict Resolution
      : The framework must implement deterministic cross-domain policy conflict
      resolution. When an action spans multiple policy domains (e.g., routing,
      security, QoS, multi-vendor domains) and generates conflicts, the
      framework <bcp14>MUST</bcp14> resolve them using configurable priority models (e.g.,
      security policies take precedence over routing policies). Actions <bcp14>MUST</bcp14>
      be halted until conflicts are resolved or overridden by a human supervisor.</t>
          <t>CTL-12: Deterministic Authority Precedence
      : The framework must enforce a deterministic hierarchy across four control
      sources: Human Operators (highest precedence), Supervisor Agents,
      Orchestrators, and Autonomous Agents. When conflicting instructions are
      received, higher-precedence sources <bcp14>MUST</bcp14> preempt lower-precedence ones,
      and lower-precedence sources <bcp14>MUST</bcp14> receive preemption notifications.</t>
          <t>CTL-13: Intent Validation and Alignment
      : The framework must ensure agents validate high-level network intents
      received from operators or upstream agents before execution. Agents <bcp14>MUST</bcp14>
      verify that generated configuration syntax and semantics strictly align
      with network intents and operational constraints.</t>
        </section>
        <section anchor="ctl-resilience">
          <name>Agent Control Resilience</name>
          <t>CTL-14: Degraded Behavior on Control Plane Unreachability
    : The framework must define deterministic degradation behaviors when an
      agent loses connectivity with the ICON control/management plane. Agents
      <bcp14>MUST</bcp14> support at least one configurable fallback mode: (a) Fail-Safe
      (abort active/pending actions and enter read-only state), (b) Fail-Hold
      (complete current action but reject new requests), or (c) Fail-Local
      (continue execution using local cached authorizations).</t>
          <t>CTL-15: Management Plane High Availability and Geographic Isolation
      : The framework must support high availability and geographically isolated
      deployments for ICON management plane components across multiple availability
      zones with automated failover. Active operations <bcp14>MUST</bcp14> be safely recovered
      or re-evaluated by the backup primary control plane without duplicate
      executions or data loss.</t>
          <t>CTL-16: Intended vs. Actual State Reconciliation
      : The framework must support continuous reconciliation between intended
      network state and actual state derived from telemetry. When state drift
      is detected, agents <bcp14>MUST</bcp14> trigger idempotent automated remediation
      workflows unless explicitly disabled by operators.</t>
          <t>CTL-17: Dynamic Boundary Adaptation
      : The framework must support the injection of global coordination policies
      across multi-agent environments and enable dynamic adjustment of
      operational boundaries (e.g., tightening permissions from read-write to
      read-only) based on real-time network operational health and threat levels.</t>
        </section>
      </section>
      <section anchor="intervention-requirements">
        <name>Intervention Requirements</name>
        <t>The intervention requirements are organized into the following categories:</t>
        <ul spacing="normal">
          <li>
            <t>Runtime Execution Intervention (<xref target="int-execution"/>)</t>
          </li>
          <li>
            <t>Post-execution Rollback (<xref target="int-rollback"/>)</t>
          </li>
          <li>
            <t>Escalation (<xref target="int-escalation"/>)</t>
          </li>
          <li>
            <t>Correction (<xref target="int-correction"/>)</t>
          </li>
        </ul>
        <section anchor="int-execution">
          <name>Runtime Execution Intervention</name>
          <dl>
            <dt>INT-1: Execution Interruption</dt>
            <dd>
              <t>The supervisor must be able to immediately stop or redirect or isolate or report a running
 agent's runtime execution.</t>
            </dd>
          </dl>
          <ul spacing="normal">
            <li>
              <dl>
                <dt>Pause and Stop</dt>
                <dd>
                  <t>The framework must support a temporary operational pause that preserves the execution
state (e.g., giving human operators time to analyze before  deciding on further action),
as well as a hard stop that terminates execution with or without instant configuration
rollback when an agent is actively causing network instability.</t>
                </dd>
              </dl>
            </li>
            <li>
              <dl>
                <dt>Emergency Intervention</dt>
                <dd>
                  <t>Emergency intervention operations (e.g., pausing, terminating) must be executed
independently of the agent's internal LLM reasoning state or responsiveness or
other agent's runtime execution, i.e., the framework <bcp14>MUST</bcp14> support out-of-band
emergency pause or kill-switch signals in cases where an agent encounters a major
failure (e.g., infinite reasoning loops, deadlocks) or becomes totally unresponsive
without affecting the other agent's runtime execution.</t>
                </dd>
              </dl>
            </li>
            <li>
              <t>Verification and reporting
：The framework must support explicit acknowledgement and effect reporting for
intervention commands (e.g., termination, pause, stop), distinguishing between
"command accepted" and "command applied". The agent enforcement plane must return
the state of the intervention target before and after the command, the intervention
result (completed, partially completed, failed, unknown), and the failure reason,
and should support timeout reporting and retry semantics.</t>
            </li>
          </ul>
        </section>
        <section anchor="int-rollback">
          <name>Post-execution Rollback</name>
          <dl>
            <dt>INT-2: Rollback and Recovery</dt>
            <dd>
              <t>The supervisor must be able to reverse actions already taken by an
agent. The framework <bcp14>MUST</bcp14> support multiple granularities of action rollback.
Based on the severity and impact of the failure, the rollback granularities
<bcp14>SHOULD</bcp14> include:</t>
            </dd>
          </dl>
          <ul spacing="normal">
            <li>
              <dl>
                <dt>Agent Workflow Level</dt>
                <dd>
                  <t>Reverts a specific step or a subset of execution steps within the agent's
 execution chain, without canceling the overall task. This is applicable
 for localized errors. For example, When an agent is onboarding a network
 device, the supervisor rolls back only a failed post-configuration script
 execution step while keeping the successfully downloaded boot image.</t>
                </dd>
              </dl>
            </li>
            <li>
              <dl>
                <dt>Agent Task Level</dt>
                <dd>
                  <t>Reverts an entire task execution, performing a comprehensive rollback of all
 network operations introduced since the initiation of the task. This is used as
 an emergency mechanism for severe failures where the agent's entire execution is
 failed. For example, when an agent fails to provision a network service, the
 supervisor triggers a full task rollback to wipe out the entire provisioning
 attempts across all affected nodes.</t>
                </dd>
              </dl>
            </li>
            <li>
              <dl>
                <dt>Agent Context Level</dt>
                <dd>
                  <t>Reverts all network operations across multiple related tasks bound by the
 same context. This acts as an ultimate rollback mechanism to reset the entire
 multi-turn interaction or back to its original historical baseline. For example,
 during a multi-turn network troubleshooting conversation, an agent executes three
 tasks under the same context to mitigate an anomaly. If supervisor realizes the
 entire investigation pathway was flawed, they may select context level rollback
 to comprehensively wipe out all configuration changes made across all three tasks
 in this specific context.</t>
                </dd>
              </dl>
            </li>
          </ul>
        </section>
        <section anchor="int-escalation">
          <name>Escalation</name>
          <dl>
            <dt>INT-3: Escalation</dt>
            <dd>
              <t>The framework must support the mechanism to allow the agent to route operational
decisions, anomalies, and conflicts to a higher authority. An escalation is used
when the current level (operator or agent) cannot or should not resolve the
situation without supervision. During an escalation event, the framework must
preserve the agent's runtime context and its full reasoning provenance trail
to enable a seamless handover.</t>
            </dd>
          </dl>
        </section>
        <section anchor="int-correction">
          <name>Correction</name>
          <dl>
            <dt>INT-4: Correction</dt>
            <dd>
              <t>The supervisor <bcp14>MUST</bcp14> be able to correct an autonomous agent failure through
any of the following mechanisms:</t>
            </dd>
          </dl>
          <ul spacing="normal">
            <li>
              <dl>
                <dt>Providing Refined Intent</dt>
                <dd>
                  <t>Clarifying or refining the high-level intent when the agent misinterprets
 the operational goal.</t>
                </dd>
              </dl>
            </li>
            <li>
              <dl>
                <dt>Injecting Additional Operational Constraints</dt>
                <dd>
                  <t>Appending runtime network constraints or specific limits.</t>
                </dd>
              </dl>
            </li>
            <li>
              <dl>
                <dt>Providing Missing or Correcting network context</dt>
                <dd>
                  <t>supplying missing, updated or corrected network knowledge, telemetry data,
 or topological information that the agent relied on during its reasoning loop.</t>
                </dd>
              </dl>
            </li>
            <li>
              <dl>
                <dt>Modifying Pending Actions or Planned Configuration Changes</dt>
                <dd>
                  <t>Adjusting the agent's generating configuration, tool selections, parameters,
 or execution order before they are applied to the network.</t>
                </dd>
              </dl>
            </li>
          </ul>
        </section>
      </section>
    </section>
    <section anchor="security-considerations">
      <name>Security Considerations</name>
      <t>This document defines a set of functional requirements for observability, control,
and intervention of Autonomous Agents in the context of network management.</t>
      <t>The requirements themselves do not introduce additional security vulnerabilities.
Rather, this document requirements some security safeguards such as access control,
identity authentication, and integrity guarantees that should be enforced by the
implementation and deployed systems.</t>
    </section>
    <section anchor="iana-considerations">
      <name>IANA Considerations</name>
      <t>This document has no IANA actions.</t>
    </section>
  </middle>
  <back>
    <references anchor="sec-combined-references">
      <name>References</name>
      <references anchor="sec-normative-references">
        <name>Normative References</name>
        <reference anchor="I-D.wnd-opsawg-icon-ps">
          <front>
            <title>Problem Statement for Autonomous Agent Observability, Intervention and Control (I&amp;C) in Multi-Agent Autonomous Networks</title>
            <author fullname="Qin Wu" initials="Q." surname="Wu">
              <organization>Huawei</organization>
            </author>
            <author fullname="Daniele Ceccarelli" initials="D." surname="Ceccarelli">
              <organization>Cisco</organization>
            </author>
            <author fullname="Zhenqiang Li" initials="Z." surname="Li">
              <organization>CMCC</organization>
            </author>
            <author fullname="Luis M. Contreras" initials="L. M." surname="Contreras">
              <organization>Telefonica</organization>
            </author>
            <author fullname="Daniel King" initials="D." surname="King">
              <organization>Lancaster University</organization>
            </author>
            <date day="16" month="November" year="2026"/>
            <abstract>
              <t>   This document provides an overview of the issues associated with the
   deployment of the observability, intervention, and control of
   autonomous agent pipelines in large-scale heterogeneous network
   environments.  The term "Observability, Intervention and Control" is
   used to describe a set of automated and human-initiated mechanisms
   that guarantee the capability to observe, evaluate, constrain,
   correct, and terminate Autonomous agents at any point, for any
   reason, irrespective of their level of autonomy under which it
   operates, to ensure resilience, recovery, and operational continuity.

   The set of enabled observability, intervention and control reflects
   operator service offerings to ensure that autonomous network
   operations can be stopped, or safely redirected when required and is
   designed in conjunction with agent to agent, agent to tools, agent to
   human interaction and service and network policy.

   This document also identifies several key areas that the Agent
   Observability, Intervention and Control group will investigate to
   guide its architectural and protocol work and associated documents.

              </t>
            </abstract>
          </front>
          <seriesInfo name="Internet-Draft" value="draft-wnd-opsawg-icon-ps-02"/>
        </reference>
        <reference anchor="RFC2119">
          <front>
            <title>Key words for use in RFCs to Indicate Requirement Levels</title>
            <author fullname="S. Bradner" initials="S." surname="Bradner"/>
            <date month="March" year="1997"/>
            <abstract>
              <t>In many standards track documents several words are used to signify the requirements in the specification. These words are often capitalized. This document defines these words as they should be interpreted in IETF documents. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements.</t>
            </abstract>
          </front>
          <seriesInfo name="BCP" value="14"/>
          <seriesInfo name="RFC" value="2119"/>
          <seriesInfo name="DOI" value="10.17487/RFC2119"/>
        </reference>
        <reference anchor="RFC8174">
          <front>
            <title>Ambiguity of Uppercase vs Lowercase in RFC 2119 Key Words</title>
            <author fullname="B. Leiba" initials="B." surname="Leiba"/>
            <date month="May" year="2017"/>
            <abstract>
              <t>RFC 2119 specifies common key words that may be used in protocol specifications. This document aims to reduce the ambiguity by clarifying that only UPPERCASE usage of the key words have the defined special meanings.</t>
            </abstract>
          </front>
          <seriesInfo name="BCP" value="14"/>
          <seriesInfo name="RFC" value="8174"/>
          <seriesInfo name="DOI" value="10.17487/RFC8174"/>
        </reference>
      </references>
      <references anchor="sec-informative-references">
        <name>Informative References</name>
        <reference anchor="I-D.wmz-nmrg-agent-ndt-arch">
          <front>
            <title>Network Digital Twin and Agentic AI based Architecture for AI-driven Network Operations</title>
            <author fullname="Qin Wu" initials="Q." surname="Wu">
              <organization>Huawei</organization>
            </author>
            <author fullname="Cheng Zhou" initials="C." surname="Zhou">
              <organization>China Mobile</organization>
            </author>
            <author fullname="Luis M. Contreras" initials="L. M." surname="Contreras">
              <organization>Telefonica</organization>
            </author>
            <author fullname="Sai Han" initials="S." surname="Han">
              <organization>China Unicom</organization>
            </author>
            <author fullname="Yong-Geun Hong" initials="Y." surname="Hong">
              <organization>Daejeon University</organization>
            </author>
            <date day="28" month="August" year="2026"/>
            <abstract>
              <t>   A Network Digital Twin (NDT) provides a network emulation tool usable
   for different purposes such as scenario planning, impact analysis,
   and change management.  Agentic AI enables dynamic goal-driven
   execution and adaptive behavior and closed-loop autonomy.  By
   integrating a NDT into network management together with the Agentic
   AI, it allows the network management activities to take user intent
   or service requirements as input, automatically assess, model, and
   refine optimization strategies under realistic conditions but in a
   risk-free environment.  Such environment that operates to meet these
   types of requirements is said to have AI-driven network operations.

   AI-driven network operations brings together existing technologies
   such as Agentic AI and NDT which may be seen as the use of a toolbox
   of existing components enhanced with a few new elements.

   This document describes an architecture for AI-driven network
   operations and shows how these components work together with NDT and
   Agentic AI capabilities.

              </t>
            </abstract>
          </front>
          <seriesInfo name="Internet-Draft" value="draft-wmz-nmrg-agent-ndt-arch-06"/>
        </reference>
        <reference anchor="RFC3198">
          <front>
            <title>Terminology for Policy-Based Management</title>
            <author fullname="A. Westerinen" initials="A." surname="Westerinen"/>
            <author fullname="J. Schnizlein" initials="J." surname="Schnizlein"/>
            <author fullname="J. Strassner" initials="J." surname="Strassner"/>
            <author fullname="M. Scherling" initials="M." surname="Scherling"/>
            <author fullname="B. Quinn" initials="B." surname="Quinn"/>
            <author fullname="S. Herzog" initials="S." surname="Herzog"/>
            <author fullname="A. Huynh" initials="A." surname="Huynh"/>
            <author fullname="M. Carlson" initials="M." surname="Carlson"/>
            <author fullname="J. Perry" initials="J." surname="Perry"/>
            <author fullname="S. Waldbusser" initials="S." surname="Waldbusser"/>
            <date month="November" year="2001"/>
            <abstract>
              <t>This document is a glossary of policy-related terms. It provides abbreviations, explanations, and recommendations for use of these terms. The intent is to improve the comprehensibility and consistency of writing that deals with network policy, particularly Internet Standards documents (ISDs). This memo provides information for the Internet community.</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="3198"/>
          <seriesInfo name="DOI" value="10.17487/RFC3198"/>
        </reference>
        <reference anchor="RFC6241">
          <front>
            <title>Network Configuration Protocol (NETCONF)</title>
            <author fullname="R. Enns" initials="R." role="editor" surname="Enns"/>
            <author fullname="M. Bjorklund" initials="M." role="editor" surname="Bjorklund"/>
            <author fullname="J. Schoenwaelder" initials="J." role="editor" surname="Schoenwaelder"/>
            <author fullname="A. Bierman" initials="A." role="editor" surname="Bierman"/>
            <date month="June" year="2011"/>
            <abstract>
              <t>The Network Configuration Protocol (NETCONF) defined in this document provides mechanisms to install, manipulate, and delete the configuration of network devices. It uses an Extensible Markup Language (XML)-based data encoding for the configuration data as well as the protocol messages. The NETCONF protocol operations are realized as remote procedure calls (RPCs). This document obsoletes RFC 4741. [STANDARDS-TRACK]</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="6241"/>
          <seriesInfo name="DOI" value="10.17487/RFC6241"/>
        </reference>
        <reference anchor="RFC8040">
          <front>
            <title>RESTCONF Protocol</title>
            <author fullname="A. Bierman" initials="A." surname="Bierman"/>
            <author fullname="M. Bjorklund" initials="M." surname="Bjorklund"/>
            <author fullname="K. Watsen" initials="K." surname="Watsen"/>
            <date month="January" year="2017"/>
            <abstract>
              <t>This document describes an HTTP-based protocol that provides a programmatic interface for accessing data defined in YANG, using the datastore concepts defined in the Network Configuration Protocol (NETCONF).</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="8040"/>
          <seriesInfo name="DOI" value="10.17487/RFC8040"/>
        </reference>
      </references>
    </references>
    <?line 730?>

<section numbered="false" anchor="acknowledgments">
      <name>Acknowledgments</name>
      <t>The authors of this document would also like to thank Benoit Claise, Swamynathan B, Laurent Ciavaglia,
Parisa Foroughi, Reza Rokui, Luis M. Contreras, Oscar Gonzalez de Dios, ZhenQiang Li, Cheng Zhou,
Daniele Ceccarelli, Dan Voyer, Thomas Graf, Alex Huang Feng, Yuanyuan Yang for review and comments.</t>
    </section>
    <section anchor="contributors" numbered="false" toc="include" removeInRFC="false">
      <name>Contributors</name>
      <contact fullname="Daniel Voyer">
        <organization>Cisco</organization>
        <address>
          <email>davoyer@cisco.com</email>
        </address>
      </contact>
      <contact fullname="Shailesh Prabhu">
        <organization>Nokia</organization>
        <address>
          <email>shailesh.prabhu@nokia.com</email>
        </address>
      </contact>
      <contact fullname="Qiufang Ma">
        <organization>Huawei</organization>
        <address>
          <email>maqiufang1@huawei.com</email>
        </address>
      </contact>
    </section>
  </back>
  <!-- ##markdown-source:
H4sIAAAAAAAAA6V963LkxrHmfzxFLSfimLS6Wx5Jx5Y7fBGHcxHjzIUiKSl0
NtYR1UB1N0Q00MaFnNbMbPgVNuL8OftrH2R/7aP4BfYVNq91QTeH4/VE2CJB
oFCVmZWXL7MS0+k068u+cnNzdNrm67J3eT+0zti6MJfur0PZuo2r+84sm9ac
Dn1TN5tm6MzpCq6aN4vOtbd2UVZlv5uYs6bu26aih8/rHv4EN5VNfZTZxaJ1
t/CSMm9q00YDH2W57d2qaXdzU9bLJsuKJq/tBmZUtHbZTzf53bTZdvZuNcWH
p/HD0998lXXDYlN2Hbym323hqfNn18+NeWRs1TX4wrpwWwf/V/dHE3PkirJv
2tJW+Mv56RP4Dyzs6Pzy+vlRVg+bhWvnWQEzmmfwss7V3dDNTd8OLoPpf5nB
uK2zc3N6+ewUfrlr2ptV2wzbufnxhfkRfivrlXmBV7Ibt4M/F/PMTPco1+HF
167H580rW9sVLYj/iH9LKIsXhLb4Y0zaLLNDv25g0tPMGLMcqoqJ911Zmx8H
vNa0K1uXv1i8fW6+HeydK/G629iymht4RTW7G75Z0x9mebMZD/UUHneVM2cu
z2H1VVXuD3tWdnkTjVrkfPM3Of7BjxoGfTmU3cy8mvHCXGuBJKMxr+Gly6Yu
c5v5cSt4bFOuBlfBmPLgZmhhDc03vb//wPt4EebfgD97L3pp69x2QFTzfV3e
urYjmvulzJCp31R608zms+FmNPyLcujcduvM87LJ86ayey/xhJdhV/LEbClP
jDgQxj5bOxCqf183wM4R1V+dnWU64C9wQ4637n7efQNbGR5ugLmOBsyIWuUC
5FBkZY80PzQ71+5NWxmrxLC3eNu9bL1aw22uW5uL1i7Ww95wr5ubMmJnJ7fP
tnT7NzX++ZAMflcOSwtUeGU/QaQ39q98++OYplndtBt45Bb2doaqJvw2nU6N
XXR9a/M+y67XZWdACw20JQu3LGvXwb4fqUdrOtebZpmoM9KTh9XiJBvrxYNK
FXbF9drtXza5rc0CX73TKx3w29jOK5KNVySZ3AHjX7kc9kevD82y7Lw3JerD
clnCulZ224HmNe5t2fWovTYuXwN1u01Hy+y2Luc7ZZ0F3A1rAFLhEnK75YXC
HdkCJuJcLdahG7aw1BJVs+l2sHVkxP2lHY9XMlaJ3Ymxedt0ndkMVV9OgYBF
02auvi3bpibKT3Smua2qnWlSHuTCA5pAO8DiN47XIbwgqmcJK225MX1jVoNt
LdzpYJDNtnWwxToQm4mpyqXLd3nldHTTgPI4sDx8p6vtonKZTAvfSJNCmYNp
TJK58Czzpm0dExlmgZYIBK8WAjVAWhrFVjDpDlbp6tzJczBIPcCygdck2puy
KODdYK/OcZ7FkLPpODDTFqmSg4nrQBSAjGA8K9jwBYlqvSdnprfdTWfevfvz
+fTp7G7zy7TetKupxdGmddFPcdd8+JD9/W//geNWQ4EShiQoYbbbtmHxwIs4
dX0BLGEJSp5XaFAcV0Bvfcx2QAqrywX718BGdgXs6Zzk2hSlXdVNVzLlgTxN
NTCPf1yDujH9mnjvKYGb2MqWKlc1yVDdw+rLDU4RRB+eyNwSriOZd/cQA5jY
k9sBg7vbsgeG78yihcV1uIaqAt3swq7FK0MOapqYQTLyFvYqTWiowc6WIr3A
xmcHNidOgmYdEQRcIJF/eB42AWy8HsbPSYjBnyor2GxutpqhwG2H/vNm6OE/
2a2tykKk0osWrKVq7ip4c/f5omryG/pxAmxzU9n9dosEstXJxNwRaXEqG5xo
v7ZIjIqnmC3h1Si/m6ZwXpXBQKxdixlY3qq8cSBvsA1gAFxubrpm2d+hTIr6
mJh1c+dgk03My5evpgvbgWQy5zL3dl0ugAHAipaosnBre1s2bcdzgXfWDV4l
q7ID0YA3lFuUHFSTwFeYGuo2JVk7gGVCkXHAHRwRJyRqbEuyA9sRpAOWSMQg
bYs7h+UZRl7Lq5dIB6B0B+IZLVpelC2aoS5sCwqUJAjcm3VvKmcL3PdtiRtM
ZWaoUU/UONFDewSZ01QlSCgsvKK/dJMMpgWeS25p7wkjSOXjPhAxnqHZc7Fa
wTWCxkKiR6YPrgdRZj0Ff1ij01WxKWndCkSNRcCN1HCWqOFY5dEWDOrIBnWE
3m0zrNakjHp0F/DJTFVOXSTRwbb78GE2NuGLoawKIN4WVem66VywfwVPGgjN
1mMXzLrrOrwJ1pVYBeRopqYNpat2MModSIkoS1JmPP8SYx0YQIgc79mP2Kcs
tUvPhxYo2W6a1gUN472S2nMHtxeOf3725rVBhXuemJSz+A2Jh3KPGzKmYnAE
kLF77hAYx82AckDsTEimbgE9xxoL5oC/7bsIMwPuSdHAW3C3wg7BrVGUv3it
7VoUTtj+yRRA8MFBx42X2QqiybJfo+TCwsjAsuoE3hdN1axwDcDg/qCbBVc3
natA6+9RIEzLy8rWtrCFh8q2uF/6JkcKgya1pOkqmgFYkYoowaQ5vTifwcAo
hn0D6prFvAEmNyvaeCCM/WgvJuRU9QFC4Ujvom5oXeZVAwwAak6t3rR2AxCh
guU8evSpITvFsktQ/0io/eg1Q61oTs/fXFyZUwi+kU+get+KGqL5Q3jTEsPg
L3fAD5RVcLzaoUOVOx4TtRTcsAcxiLXad3H57yc8NEzUdb2hwQ1EJkgYYu8+
TIF8ymFvkww+A9s1MFv08h3Ekkg+mHmJux9EjygKnK1A1tiZ48d0fLU0xkcV
sG+zc3SOgclAwDWodNLkkXH1mqAAX8GScV+2zQb4afvYHXNvQdh6nkPR0LKy
AsSP9oxO1oF6r6zchQtfD0CpGYRG8J/opXQ/MCblNTo9IGTgUKsjK1dgMPLR
wGx5B4LkXPxSUhwJCUDI/jv8w2Dsvn+fTdN/n2X71/Ay3fxelvCGltC07zO8
tvfvffT/0VW+2YspxPUopu/DNML/0TTuHTn8+D6e7V9Gs6W//DDV/6Mx08fj
hY7e9n7vZvi/9+Hm03PzwjMhvVl2sR/ws3R26TSumLfjt1+6LeggvPOc92yY
QzpswjjECHHn6c0qV44usGzo6j6/dN0WQbUwsswFfo524n2kiC9cyG598OaP
kmJ885gUfsHK0x9iRgNTolHf78eu76PXeFIECY6o41/1p0RXvf/Y1hjR4f3H
9txolM8O3TuCHMf/hFVkgZc2d7LR383NI7ITBCP/8ejKorXz5uMIdBiRZQqa
dFX/8Sh3OMDRB4xGQWxFBXGk9hQNW0m/szt643YIsYLvdvTq+6trxGzxv+b1
G/r58tl3359fPnuKP199e/rypf8hkzuuvn3z/cun4afw5NmbV6+evX7KD8NV
k1zKjl6d/nTEburRm4vr8zevT18esc8cewTkoDZiLlwLvj3qYNuBhu7ytlxw
QPHk7OL//K/HX0GY/F8un5998fjx7z98kF++fvy7r+AXdB/5bU0Nji7/Cnp8
l0GE5SxaFgqmcrsFHVah5w1BAQRDNXkBoHV//V+RMv9tbv6wyLePv/qTXMAF
JxeVZslFotn+lb2HmYgHLh14jadmcn1E6XS+pz8lvyvdo4t/+HMFro+ZPv76
z3/Kssyk/hkYNnY9lg1GrhSDgOMcPCagIpD9vrhhDgP+erQN8EqKt8MFxeLx
ZzFPhBpD3LY3J3XUD0xrzqise9vPszmBfgfQHXImJwnkBuODJdyxvIBNG/RW
fRycUrvBQBoxdQ3EYYsecHYhwARVhWkPdht4aIrGPJ6WvJwgLgLhYJvj8ENb
o6f8yHiM4lWKUXwsVTTZczyz7HSJSHzrclfeUizFnmTLlmaisRW5MkAn9Ljg
HnhlWU+b5RTc6AED6OOz5vokjsdZU04w7qgxjqIBQsxJ8SUCSLj7MOCijQ3P
3wAz7zh4QbQLqQHR4rAg6Isc/GJX2w3jLpmM0SMIdNvcOE8rcOQkdumbBncw
6AqI+W+duQVvCkcBRiOi0Znjy9MXJxOGE9i8YvCXRd4lu4pxBEWul2cBpkJA
AoCTMZpL3mTuMHrviTUIeFPGCn4oypEUweta24FLTQEW+ucejvExB4XWPNYI
uWGgBDxQBWws6nhb7X7RfXhv/E4s2tHwYGgYMIQhnKnKTclBVMcBNyjHqmSn
9wCM/hxhnbdkjyYB3ob4b8XygBINIpGRygV5A0PD3reI+h1Mubc3jpBaHKVH
TI2SjfD83XpHUhRuCgCnD3R/1fmQNUtEEaTdRoDtEgEJ+JVCF5h6YGTLFPBs
BDqjcy6IrEBVOAoqRttmAUNEAIrBAoG+wHhQtI6z4wW9pSdFfCP4Ed76Mwml
RMqHwAE/RfBLI3Rx25Yb25YIPpISgyX2Os0Y6FJEK4YhTYAhKTqLgMZ87fIb
To2A/zgSak8SCtMEUz+g7TBULOsYgYthdAExQKKIM/FkFzA3lkmEN10AN7cN
CMMCNnfA20KeJuCLnAAggDHbAxhPOyShIosJ+q4khGfqpv773/5HusnS9EdP
pBFMcQNjEMyH9KEYDjhV1t0gIDaCxrwkEQ4cOdc8RDtse0mVwLZAjU/6Zqij
RWUeXwVhOK1Y7eKQiAchZNtsGO5tawl0dYlEPY0r/ftQ3d2gSu6ATSAbcWJJ
fKEW83uo+8C6kU+pFmqSLI00J4wPouh62+4Y2wTaENS3afryFok6QrFA8/mB
ZemjtN5HgbtsD9FMnI4YqwJ/D29+9y5+A6g9zFRgrF/egp7B3M0jc5rM77mf
n8f53j1KRhbEqpP4XL1Qdj9atwTmkNaJwTsdi/OOyZ/2lvDhQ4arR7niMdU+
IPVow2i+CvgO65D3RoRUFFEGTUmg6EG2F7F86j+KbA6E8WbsqO3f8P6Bt/7l
/j8djKfGQz/094+8+vYTFsxu1pV3B3bmorLgKz/02oPEevCff3QUWJroUvJL
uOIffZ/GuvS3GMl4H/uF7w++9S/pi96nb/3L+K0J+pLS8SO/KndDCO/JwJcU
RBXSaBVPCjvGdOZYuovpmTrBxjxFDPmqB1tA6bSU+Ad+5SEfWORIjn44IEe8
omfoauaMs36yGMUv3uO9YBaja/povKL3/v9Gy02vRY/ynB8b8wcc9U964Qu6
MJvNomv16NH/37fGArYncela/zJa6/6why/Ec0jeuqcNDqmH249QGP49H2o2
Ea+aAt0Q8y/mGsOS+9f6D/z77J/TpR5XQoujuBJZu7hE8WPI0qP9sFyQcK/+
WwduYKcZH8zETCtHyVyqp8MdKykiNvsh8UAZKnFfuDIAvMB+GrznpXPFAgIr
9ErQje7MqmoWmFHF3Cy5M627Ld2d5DkVvde8maMsO/kT4G5CgILpA5ld4mFg
yg1u60wxYJWBAVuP4SNlUpoNkIVyWObX5oKTwjjkma85AY3zM/sJ88zMk1QB
pjXzZqiwJAHJ1JloCjE4ESpY6LXBZ1ZPnfM/XcZIWWvrjtMUFERvLJapuSko
uQKrYzyBzGLH7k1elZIuNB2Vm3B2Q5LcLmipjFz3pkb+0JKfBZp+C49DdLSi
ZVLiCrOm5GcpA8A3H5CynFDdLMrVgHFDBzIFy2kmCDBAlAZv7X02syiX5E/1
ga8Z0d6E9Axl+cbxHdUDYFYUMRkbhyP9Goi9bqqCs1fR+ii96TIImzqsZu0C
HEGxhaR/OoxIgUaeixBdcCrIX1K+lgRxcP2GQ4FEWeAFgNOOyc04iMV3EhbD
SqNDKYX1CKm54gIYkmSVrttytcJyWqB6lAujLOASw1xHnCgkAaaVHCGbJqk/
W3suwehcKpQhOoFYMUqYerVV02yplIN3ItzIBSKIWg19Qa+g1Cxl6qS8ikO6
Lc74ZMK0yiI1QcAZkHWzcQVOcoKKYCAcXDaP5vemEG6I3oCnW45t2D2msJBX
k6kuiEId3rJ+2aHuqzvR7Qv65ZnXL89FvxBln7hdc09J22TEet3ThAlo/GVR
a/RUvoGAVKMRiOY4yRtRjYaYikKYMLAWXE1E3+wo8oLIHoG25VBFpVf7c9nY
nRAxk6K+AhZQd6xY9I1eCDrQbF2Crfz9b//ZjettJp56FO5isMx8y3x9gAHm
wPtpqrpGGfavwFhV/A1mQV3FjDiZMaqbUsjPkciaYdA/dIxCDNtCQ0wgNIiX
gch3y1uUYD3c74QrduTixelVbyRAMRAneXYZxuJDy6IOM+zKTYllByo3CBW3
5dJXeHaYOenXZsPC4GuyxnxoLZWKgXoFKbJ3std8RWObmhwtcsi2dlc1Fm1P
ifSGgBU1/k5EDFPMG1J1lXtLAAludHr1dAn2ARQylZ1sbE/rUzSothRLZsAr
oMhKkUYifWV3Ib9tkwpTjHZIQdKf1coIUqsIZhEtKimxkWw3B/lUJFxJbTGr
p7LjymnK6qNzcU+olWWn98yq7KJqhFCtF0McEaaqQsQuB2gc4B6wiit3Wrca
aHH71VJNTcJQLUklpWwmpwWmgdUvXCAIRqoZtlhNpVhypmp2ZHVm5nXTK+h1
zwq5aI0RUBBPxs99YRhOPCktA+Vn21DWxqOGetq4pjLQBZS4+mRgR7eOf8Fk
Cx4UQcBknL5h29NLMgH3Xii/NbzzOpaXTdn3SopoW95LkcgFRFd3vKmoKCUp
Fx4ZNyAClj1JbEhldCjV8jtmD7hCjRKxMem8Z0cgF6c/SJj85g/+nsSlSgWL
rqjgNugst1LcInc/Va/lokHv8Pji6cUJwvSXz8++fPz7rz98YAnw26tTa2mC
cyHlPvBTPOfVAKupKA1GW3KPFDHWGrBkVNHj5UcOJzEhzr2Y7dChMfUVfNHW
J6yVSEaLxWFj35UzPM29/P6In6PUBVdPYgnn74NRYEK9FN/Q3gtV9JR7swL3
eV8hlA7iHFutmMBcFBMpqe0M4jDxlZ2TMfmphHRmvt8SsCBIr8QLbPn3ikbZ
SGkGTlwe79f4uIO2S5AC9ZqoTBGWQeB1F+cRY39IN//WorXAbBRB2/DICW0I
5iYOjCV5nkVjxzj4/ehl2oLzWKFS0u/9YSubegOeBFCZhqZ6A/IMIeRg0ofc
xIG4zIPXnnHCz0CGpHozwzIwSTWhhaYK0QDY369PwTvCuq7NwhVY0iepi/2i
80xQ9c/fXF2Rr+zTjPuHMNC3D/Vz6I6g9hBPiMOiYQu3T9HUtlGRK48VG789
gIgLNsIfE/BI7J86qVHeAlFg1vD76RrJfkxUzUUZNJIPcegmVJpnFw2lSkjz
sv1RdjIyT8nYxOJCbNt0HHVh7oIKUu/FRYgkJinrePduKXcjdA3uTyspEJAQ
ul1z1Vmz6G3EvTiRS6rfeywwhTIuIgeTB/KtetNvarL1aLEP52pnY2akUJ7f
ESNcgYP4ckVHErQcMS1JQNsGStlvJa3T9ocXJNVAXjiqLk6H0iERENMt7jL8
L8SltQdW0Bep3Aq9dCyn7bj6gIJbXHTEy5l5ZkFUAtRCY3IkcdtUt475TO/k
JLtyKEMLAb+fXpzD/9/UzR14PiunSfi4sKmTzPvQESYhOxTjtT2RIR58XGSA
F0+HVmXWUm0DLc0vIq5U3WeWlJ12yaLBS8a6/kjHg21BjYJRC5LAV2FjUrvT
VF6HYRbMxPM0eENd6tLs8/BA8ouDaVHJ+64vz5+y1EEH7Ylmsli4ESvvugMA
D6aRI3tVMnBHXEC/EEmaRSQNufiFQ7CBaS41IKQ09PqIZNHJHjnWwak9uR39
mFtBIQwEcRQ2s40mCpLJsRAAb2VbcIlCN8oUoEOcgCWaEZC9GZzy+whL+UFQ
x/dK37tHQTtBZIJFUNsy79Ns3iS4Gx+VQiCFqBylTpaqHPAdrPkEBQoCS6HB
muADKSvCagpQ216bISAEfIpCy1OdJWlxcvp5vCTeG2lPXyYt6hMcvhwL9FJ/
Oo8VqgEXy7XVLtolcXbbg8ZU5IeOJubpndcy6MriQamUxNF0GSnQo6YwQAum
D9UbRseY22/QbSLokV1Yz0M2FEhJkjPUeYhabrYWa5qWcakL49lS1K8DTFEB
elSE9FzQZo23lcrd2E+QkB98K7sVjLQQZNafJnv97PrszevnEi/89ouvHuPK
L59d0eWML3/9m69+8+HDCWlhg/r+zu5CIRTHiZFutoQjBQfPY2iXpy9wn3Ld
1FTrphD/uwHLdDI5rLwn8XFB0qOgT7Zy0CU6WkLv69SLjKwClWcmHj0dl0xP
d6izO8tOw3kljLX9oD5sZZGAH/Ro2IHIVsoIJQwGPudU5CjSmmTW4ZmPHXpN
EI+ooi+c2v2YGtcI9R4FQcf4GRXuEQbEyWd+fexc0P4Ahxk9B91AtT92jegu
2hQtsfW1GFwIkfSiePcoKRvYP9eS3C4n25K/p+d86fgNnSjXzERarSkdKkCN
c4logGKvtVBqJwXMEkK/pFDv+N07eO0U1+dA7ulZyuu+wFCJCsBgL+SUe9CZ
yTMrf4c+mC7wPNW+CXlkiFRB6zDMwFe45fIOuFYJxKlPbfgvdDval09e7LtH
Ya1YwPHmydX08dxcgYc2Xeym+F943TU9enDMMy5Pg0fnhkpRQjnOho71sHMQ
4yai1rk2T06aUvLycClb7BYEHxsmNfFmwAcV8Th0VNNtRQUc9p4o+AwHmOkc
FI8Rkkhy8Lbn9ShYxmV5ikH7YHkDngM3q4B/3htgPf2raPpU+MqqjRnpgW6W
Yx5Ao/H7zlhjMssr87OX5+FA6U+WwXXUeyc8mCqDbljInvejom/qEtJM+Og7
Ie91Me2bKfyHxyFh8YcQeYllLe67H9Itl8DAmcrUF3OQ9jgO/DdvMC58XeU/
LESHijNFBoLMCLpFPgKdTCRH0iegJvuVnIzZsijdyl+IYZ35GaZTLndaShqV
W+9VgfMAIatoMXtSsMNJqyKvk4p5Q/gf7GjXDG1O2Un8RyANjMLNbkSmN8hf
mopDAKfzxcmFhA6yRIRJhHcevJDks05vurE3yhpuepDyGbHp5k63l0w2jojh
52rgl8UpyMAh2oteHr6ck4MJ+8/78A9pkv1CWEoWRIWozVIkvZJybXN8JU4E
R5CwRRAoYg/iRBxTApH8nCNtIyRLckoCBxKSofX6ZlGSUAlXghbj2C0s+ivJ
10+B3vDC6UtMfeIjryiTxkr+KUfVLEBACZUWXT6D1ni+sO0T98ArgihJOWGc
DnwrMBmY9TpRFRlAsrUk2nn2Pj2m6ZVGQ35VthJ03MlZIVgejRglizkxqCkp
RXl80DziK+8AWsk0MgbpyWRF/yYcEhaeSJpBhLlrRXTyypkYxJEF55YmqRFn
WxjZcOXbv3JXIy7NxwBw1Sr+fyaCWKPPe+HPWD6oyXrw+mG9rF76uDRaM85E
g3a37ZtVa7fgRwKjOtztJ3zAk7KMWNzLlS/oBNmqj86pNtJgi4fCo/EHzauw
jzKl3K6k84e2wzrzeJ1jn5UgBS/lv50DIcpbm+8+hSAYae98MXvrCuubp2Af
r5JytnSaZqzXfYr2be8jIKwIwrPiu1g3TcwFqEz2Y0VWpZEA6bnzSIsdX5yf
n0gjFyzwoE4CnUcdVAhEtaNIlVhm0eJZaulI8Rb5i70xrsnV1/XoQWVa9MKp
jNNBoqml8xmk0vHPWNkNAYqT4EIao2DtOGa+Jc6QIcKZESp2DsIQkojKmN/N
RxL/oJSWsAV7DsmA5r0/haGdV0ZuW+Q02N5nX/FubxwVGRVVJc1h1FSCpGs/
k5Gjg2ky5PIdCLltN91JaP4gR510Nv5Inzoy2HTAW3uB2z6n4DJCkGKbr4pu
SYmnrp/6FjVMhdGRA64K405E4vYdJCbu2LZz/nDIAaCWjzSw/8kuGeJad5iv
sCV1TaHFK3rn188HwKQcRHEU3vYtrxdj9wgv003GqUGq+MEgqldt+elhCyvN
UdSiEvf1HBMEVJhHTbvMGeEsV7s6X7eN9gIz/2KekTJ70xYE0t0rl778pfYF
fzxuTuOyy8RetWwwsH5AFNKV00aG5yYP5pheOtWXIvTlKt+xCpSFSKUWErgi
AjVmY4Xps+wjj2cSeRFjcRv539qGgXRB1zU5pbj4eW7FIGVI1Y7SoKhzsLqu
hA2F9oQKp+ikpawhmrrs1OjoiVcLv4+t20W55SEufXuqwI1U6W/11kTKCW5C
lqATQVWI2OdDSClavkPIy3scCO5JmYoWEgYDN1ZyKOcbSWGiob5bu4pKrQVx
p3opS7UYi53EbkEvxDn9Mz16eH3P0UME5yWXbTjpsmy5gm63hz+Tryw94Dxd
ujVXGJFOKfSkHlbtCK2AW8vp2oHZXmu5CAMXUbqrb1Q5oiVlm1MBcydaAUE2
3iCSChOjJAjIRk3FTv5EOAgCHtZhRLKPyBlRTbveoDipGrgXduBdr6iDBw5+
M5eWD4yqfktLm6As0c5kfj8LHblk5Ie9pbVPqYhBkVfjnkEcCnbwL17nSdIj
mshaJpI3nZyQCm3BZCdLXC/HxsqOh0JLTOcXGW9dMjB4SKNS0lwRiWASeRjP
ndSqqVOuD/cQjdS0taW2cTJW5zJQ5AVdY2oWpva8hOAWYioc4fj6+vk1p+Pp
z+D+mDfcMox9Pbnr4s31iTjU4t/5lXBY4kDR0gjXDTBxa8vWHL+6vr484aSy
5kX2cTut2frnEDuBLb3b+iIcWKROt9iaRedw/O5d3lehntsjZ+IRhbztKQPU
owdtXukjUllzgVmdwjfog/ulkG83fjYPf0oBu0Ag3+tPHgnd/zxm94+s9t2j
dLHwzrPrl4jcnbIA8t0VmBHqi+dFcX5om2kxhK/ZRXyOn+XImJrgSB051gJr
owmRdnHmXjZ3E5CZohw2E/MtKEwIuCX3d2KozpZaIuqkI49J3+ajPQp40cQV
csQ9NMPBfsEotO3K9ZJzwo3kkRKOzZuefXf0oyUNFhlb6dBnnoaaMZ+7XGHF
kwzl58HHR7GgMVCC2jsSoh6KyqUiWvrrySg+UtZzw74Wio7MIeO+mJtX9m25
GTbmCZCiN5cWyNiZl6h7dDYHeadTsEG3LKgWj0db0Ggtj7ZUa2YcJuTjsJ6O
MaJKpbzeHvnUoWByUwzh6Q227kYv+W6P/BwoPJgjOPwtZ0gmWjiB2tfcNhXQ
NRYDqS2gdWmzJuR+sgoJxkI0S/7egpyPsWTiwXlXsH/A1Inr9bEzX4W6AII2
9DyweaSUS8G+96AZ0DatFAx8+3IOnIJJEp8UPzugKT6Fg1QIQ8bGC4ofRvQp
ojEJqTRUiRCBOFV2n7Ok+UIjrgUnbhveammxEWaJJI8ru2GDATv5o4hg8MMq
C3hFqcTMlsL5aHHUVODOYRuHzsupX6yYKCkk8ZzCw/XISlf4NUskbcAlGzj2
5uMQUnelki6sDdXwnnlfeW15hoFcJXjYldvQgenufoXJJz/4gIu4KP49eTxW
l4xldB/hupw/loHOfzc33/E6jsFcArNoDVgjQTlGRtM7Re/USgArj1foenJz
TF+Kx361ehd3dLp7iefTQTWcRJGuh6/gtT5u5hx58E2kmYWv0YEfKI71au1k
pkctqddNtHwBQD2rED+QHgg2QSICUwhrgyirlcTyGUMkWMn4A/YZUJ/2nq3U
MUJsfUWmHsZn5SaSW/pdFPCSUKRHkQI3ZkXfB1yTAmFOcxr58L5ILDIU0gfB
CcgJkoto2SQgadp5U5Z3K+vxuLXiQZM0MNTGwgkggnGAaEIpxqBGmT6Ef9Dv
YRcC3R6kPZL+t3OQfUS11cl+OlB/6Ac1F9MWhN0/bCGcWZklRlt7yAZba8oH
FdM3NdLyom2wpmHCLKYln+oZp5B5dFJIhs/LUNQsaYGMklZ71N0i7xP0jhwC
3BoUKtHpKqkAkUhBraIviPYoHHaKIAPhc2BpdBbAAl6VWnzZu14pxKl5G3NG
oo+IdAlAqCRmDA6uN72320ldA0yavJLIp/jdHIKC2k1foLPhPP/xuYtAjex+
w6RoSwRO902s+2RyMlUsrHLTlbwtDr/SA4awXGKbZlIjx0NHUkf0V51UVsRg
n683anCrwv4Sr6Rz3OaY6168exJKcBLD89Pp6xfA4sLpAVItW5FWitwrlJwh
JFbvMRTaemhZKc2Ko9BexKEE1bm8OGPwEE9I+qN54tsG/gRwLN6k4jpGJyHv
339qe7iTCpd/Rpjgaj0ldzW19lE5qtXu8JTmVVllX0d92D13C/OXMpR0EdNp
JA5olGCS1Ol+u1kUqxpkVk1+A5toQOul7/b125KwLrkUpfErdrSzOwQ8qkDZ
32MGolkh+IQaKKXy91tEmVmA0f+n3x6mMZ74DEMmezhq8xM87P3C6CKUC4SC
co2dyEdDeZliX6NJRBHZHejVgA3B0KeJTxF5vkjaIj2QoiKr6xxNnFWGzizE
WP4EJh/g2wS3LKQ00ch8eqTM1iYOlD23EDU6I+jTnEZZA+JPhL2+bKjp1cOc
Yhg1yUD4jlnJyTC/oyseetymPfikSUYT/sJH4kY4U+fdIA2jSc3ZXIJreo05
Rg0jvY2BK1hqVXARlQ9qOVSKolnYmqVGv+CRnFAhGd/bCrTWhQBbDkdIlQki
yjqxMzkMzZU0srXUhN7jRkNojp0M9Ry1jAS20Wu0yOQ8fgysRIs4fUrKOTrS
xKewL/3R0o9FRL44b9SejIztlPW+BuyjiaWfDQiHxqnGz9ZdaOwmz4sV0X2I
CigUEmFLnoE9t++aq0nyGQt9knG2cG5GJ8RHRWScsEAiN82S++xszNDF8Smf
qNdDyZSpSHPCfk4RXG5vqEO9bkLq/SQr8XedzCTaYZbLYMD4NaaNC2zyXFZh
9oTWyTxJKpLA2IfESSM7lYIv5uZpwrhT350hqIpPAzVSAViXQGTweXbqeC1B
+NVmK3l4P8xHLYiBiGgRHfk1OgfQmVej4zLeb3gT+VZi2A90qyMZy6N9lZyW
sq3zcskV4hOyyxAlR+zSHUyiAdcdprWxN3ZyV1OnENfeDckw8j4djkqH7tmz
X861d/APSSM3COfAxka6/2Mhl0RbPgSKDqmE0y59FDGlJfPxORUzPqey74GI
RY3kGKv7Cay0fVQ1l8ZM3Q4071tpSyFxeYgLqR9J5L+P580O9z2HGmME9wDo
y9YvwnwVr/0KdwpZ5sI80VYCCEjIGFzG+32NRw7XcZPfj8ES6Z6JsurRxzW4
EWMKJlVNx/rLZ4+YEOhScF8PntXn9yFEcVDm/Sb6KEaHCKxLlRz20yCEAZXc
3BzbE/PcltX0yi511xwLrEen9j5P21noB3q47ag4Thwww7Y+Xsho3zaagkPT
K1VjatbFMmDGh40eVRioaeRmnse5jAQOiA9hj+VzPTEMyXq8wrsgSATlUaTe
FveFkE33r/P4a0nMZoTMzektvMtGJ4xfOF8AdN41UUjwgBtE3evteLSVH41c
6ZJGDKFNOOgYmtWNuR2X9sefd0KjGr9PxvwFFZfkr/WjP5RIQ4PCNilGCYJD
0oEcSItP7COqcyQHZarwsC/eQ0kattLI0gOmMmONx4sBYxxqLEH/PPNI7/jc
asSn34pyxA1629F0EYq6ooT9pUMXERb7yUwRsUEL0iYP+/40+jkIdbSSCgGp
F8YZ8AXu16fnjjStK2ZJbsHSGRkNzyZQHhkNkQ1KVGtA0BfdMPgfMQvzd0Wy
xpDR2AfQwb3G7U2MSWuQmKK/A5UndQBP9Gz0KRYNfDIRuTotauQiGHPeNPgJ
G5vUEqTAa+zHx8UQcd2rVinYAot9Se49QHcY1VDnsccqXFd70IARlii2owgu
hGVebZ2EiAtz8FPCHQ+1lZZiAQ708ERGQH0ePUob+ewnZZOzJP9cZvZSzgSH
bGXy7uN372CQ/WTsRdpy61IxZrlfMWe9PeoGpSP6K3rPWfjemtwTOvH41OoD
0333KJ1tlp2/vsZk6uh+qaGQtt/RQWvFt7luugmNh8gicX8j0GB0MI6as7Da
5csCL7RDrXl+XzytJ6+955NlQEQ6eY8icAVDZw+gFoI2t7tEjvj0vpyKd9Ic
lM7oR4ULrD9EtlfcVGDcMqOX8gNpEq2+Gjflphi3Nkv+FJJYW8phREAcRBK2
LZhMXI+mWYz49CwfEG+9Jkc329Z96uFlJkl61CGhjR+V06P/WB4Un6eloXwa
4r6GEUDn8If0G1jBdAmttvyGiV8KVe2qkOjplAxrkvxnbqu0c13UgpoKGOOq
Mi85dIK1vJWiXPoKaDh2fUh+Jqacudm4Cjvx14C4WBS14BxRaIrh+z1g4eRU
uv1qjXjJtd+dpJqi3l+hQxv4ET/THPWjcv6LdtISLK68araE69oCMRMIsanT
FleO9k1Prgt+bE8JkAXI3VKmTIG2B+hB/P4BQweFJLkgDSmBe/H//u//+ZHN
5RFTkDc9trFRaJ4zdmEsgQYPdwJU+6HigpySwn3cF+CIcmJjNZRUAq7eAgx4
JIPI8WVXHNHrw2Vutn4kfYIPd0rRMhD8LEBmpEUwidnS14L7WQvypMmncD5+
7XuMTPaeyhQ6DF54MeHvcEk9o7/IRVYTYDBSNcY1VXJYUkiPYCxHZXbBOwAO
N0NMeSkyxOpBDfs8fnnYHrFB8OaI7QEeYdIbCOZnx3T3sDnQyl8fuFRo+Xfc
gZ7QFKQP8WY20ubJ3vRuNrjwNX69jJNQWJKTJwVlCPg9UY+CuIkz0BhAS2KW
MVGZZV59Jm/IPNQvOZu4PMt/cuwleiLYVucSX9Z38eEo6vhAXRbp9FmfHkeg
QlltlhKpwCzx0TmPMPE7nTPNfqfDO+ncj+1utKSvY+nP6RuuBMNhmgwDNPJz
uKXc6IsDP47tRlMvGvk0ok1SKVL5MPqeA5Gwo3CEvwpjtWqQSslHiASdRBot
k2jF3+W8cW7rjxj6Bn3oZMPGwEZu6GY3dFoA5juLuHKN5RP7HKnpwK42Vojs
gjRr4VWmLbC8TKCcYVX0nmNKtoq/rYmfNqHMOe1/BqL18LQbMYeqdPEL4jgt
b2iSZIp+Q8J//5INTGwmZUGBfli7ySQfsTZ1CZZUWaffSqMi2nASVMqYBMKN
uCuBEgo3coLp6CkEo92VW+55xh2PaG7xF3MzTEwgJJckj9lqYRUCphFnoxJC
97Y/wMuqOsSJcUSOHfioepW6uVDMIiFzhnXYTmsOhC3abQybCsEIGACG5QXW
cGLKxavUfpBoQ9Jvz7RGiVOGXjVVfGhBC9dThmWamLLx0P6kT9sMC/wKOci/
AOioZcV6BhckNLhpHUyS6UCHQXlbRTSg9n0gsyuOtaVNF4TT58tkhztSINxF
WHmMVTEdPVrKobQ7u6NDn8vK3jk2iTvqAMGHCf1LGSVVImdGDkf7DUg1KyJU
9DWpQ5+QpaOlsURxiRGtNvPH870+VqazGYziLAmFQpjFtu/LeZyQfjA6TwSF
v2IUTp76NG9cGeKbfiTN0bTuhTMSOJbA56HfM/UkipLNolcy2uzkkgjWx2Q+
9jUe+mmIE/2WBmobdiXwtyhFk/mvNYWirKg3jvGdguJ5UDHeofOOmQZc6TlZ
cU1VKMhOIwqHSubgN2gQeq4yKkLl6hCQK7shNAZPdBK6xuyNQmRmbxQhM3u/
mkc37fszisipP+Ob8NZ7/Sy9j6btufDD9+ppeDghJFrZk7igShP8y6X0VD6X
E11zLGJupRJDe7CqSdzrhGU816WSFDikZW2wDZJCYuxw2ND3VeljYT9L1BCK
vJKjDKEBd4eTOt0qGK2Miw7ox721/Y7j2sfZaLmv5LNEcOdZaIEbjYXCgC/E
3cUNbuRLRhPpVluY0Hw4qmLzAckkOu0hxygpTUzHJEn5xqe4OQD39MPPmbMT
KZq47LtRnMYrekXNp/HahdBFc43wMkS3kadnieLilD9Tk5A25apuCUnjJMlR
Vu7pkexuEn06jZcXnAE68+XPb+oHqqIvUEXNkbhnyZWmV8+k/pwN695XhfVT
zuOeP+Pv/qIX88lfnzn01SY9cK2qITpOGbW3Z4hv9M1r/SYyTJsPlaqbFp1H
Cvnk26FCimtx2yy7pLZPk7SpzejDMPi9ID8CQvbUCTRqEpvUVU0yrXYgDY4/
5t5iF9GZYxwFQjWnZ+tEMy98F0nvxYw6+XBrckxjoC8q3zNDvp6fvj59gKdr
7GXc8J0Sq8Gj0+mUHBj6so+P9BlXfTfnhgyu+OPR0ladO/rAjGD71O21BDJ3
oZl3Vd5w62PYCTfmiaubskd1V2Lcf3VnN7vaUsutJxPz0g5kxc5Ke2tXVQn7
+AL0YmfRY0JFW+Ixq18shKg3A/z8csAyuxknEmG9sEnegHFqzYum/sVW7hcg
knlaNnD934EN35XYL+QlPHgGv63gWjNMsqego2GXmTOX59hvuoK/wzXzQ0Nt
Eq/XYKg786K1y4k5xe+SfTvgMM8dqqef4Ocd/I9bkXA5HB6U9XVgfAjx/wGW
yYSUzIoAAA==

-->

</rfc>
