<?xml version="1.0" encoding="UTF-8"?>
  <?xml-stylesheet type="text/xsl" href="rfc2629.xslt" ?>
  <!-- generated by https://github.com/cabo/kramdown-rfc version 1.7.39 (Ruby 3.3.8) -->


<!DOCTYPE rfc  [
  <!ENTITY nbsp    "&#160;">
  <!ENTITY zwsp   "&#8203;">
  <!ENTITY nbhy   "&#8209;">
  <!ENTITY wj     "&#8288;">

]>


<rfc ipr="trust200902" docName="draft-yang-ancp-home-app-usecase-00" category="info" submissionType="IETF" xml:lang="en">
  <front>
    <title abbrev="ANCP Use Cases">Use Cases &amp; Requirements for ANCP</title>

    <author initials="F." surname="Yang" fullname="Feng Yang">
      <organization>China Mobile</organization>
      <address>
        <postal>
          <street>Xuanwumen West Street</street>
          <city>Beijing</city>
          <country>CN</country>
        </postal>
        <email>yangfeng@chinamobile.com</email>
      </address>
    </author>
    <author initials="J." surname="Song" fullname="Jian Song">
      <organization>China Mobile</organization>
      <address>
        <postal>
          <street>Xuanwumen West Street</street>
          <city>Beijing</city>
          <country>CN</country>
        </postal>
        <email>songjianyjy@chinamobile.com</email>
      </address>
    </author>

    <date year="2026" month="November" day="16"/>

    
    
    <keyword>ancp</keyword>

    <abstract>



<t>This document describes use cases for the Access Node Control Protocol in home applications, where a Broadband Network Gateway (BNG/BRAS) exchanges home-application policy with a Home Gateway (HGW). ANCP may operate either between BNG and OLT, or directly between BNG and HGW. When ANCP runs only between BNG and OLT, additional configuration via OMCI is required to reach the HGW. The use cases in this document are illustrated in the mode where ANCP runs directly between BNG and HGW.</t>

<t>The use cases cover three primary scenarios: managed access to operator-hosted large model services, application-aware QoS, and controlled remote access to home LAN resources.</t>



    </abstract>



  </front>

  <middle>



<section anchor="introduction"><name>Introduction</name>

<t>RFC 6320 defines the Access Node Control Protocol (ANCP) between a Broadband Access Server (BNG/BRAS) and an Access Node (AN, e.g., OLT, DSLAM). Standard ANCP is used for line state reporting, port configuration, and QoS coordination at the access node.</t>

<t>In residential PON deployments, ANCP may operate in two operational modes:</t>

<t><ul>
  <li>Mode A: BNG-to-OLT ANCP. ANCP runs between BNG and OLT. In this mode, policy intended for the HGW cannot be delivered directly by ANCP; OMCI<xref target="ITU-T-G.988"></xref> is required to carry configuration from the OLT to the HGW/ONU.</li>
  <li>Mode B: BNG-to-HGW ANCP. ANCP runs directly between BNG and HGW. The OLT transparently forwards the ANCP TCP session and does not interpret the home-application policy TLVs. This is the mode illustrated by all use cases in this document.</li>
</ul></t>

<t>The HGW terminates the PPPoE session and acts as the policy enforcement point for home-side applications. Operators wish to provide services for home application without heavyweight device management workflows or static VLAN stitching across HGW, OLT, and BNG.</t>

<t>This document describes the use cases in which the BNG exchanges application policy with the HGW in Mode B, and identifies the protocol areas that may need enhancement to support them. The key motivations are:</t>

<t><ul>
  <li>Centralized operator control of home AI application access and credential management;</li>
  <li>Differentiated service at application granularity;</li>
  <li>On-demand, authorized remote access to home LAN resources;</li>
  <li>Decoupling application service rollout from forwarding-path changes, enabling faster service activation.</li>
</ul></t>

<section anchor="requirements-language"><name>Requirements Language</name>

<t>The key words "<bcp14>MUST</bcp14>", "<bcp14>MUST NOT</bcp14>", "<bcp14>REQUIRED</bcp14>", "<bcp14>SHALL</bcp14>", "<bcp14>SHALL
NOT</bcp14>", "<bcp14>SHOULD</bcp14>", "<bcp14>SHOULD NOT</bcp14>", "<bcp14>RECOMMENDED</bcp14>", "<bcp14>NOT RECOMMENDED</bcp14>",
"<bcp14>MAY</bcp14>", and "<bcp14>OPTIONAL</bcp14>" in this document are to be interpreted as
described in BCP 14 <xref target="RFC2119"/> <xref target="RFC8174"/> when, and only when, they
appear in all capitals, as shown here.</t>


</section>
</section>
<section anchor="terminology"><name>Terminology</name>

<t>ANCP: Access Node Control Protocol, defined in RFC 6320.</t>

<t>BNG/BRAS: Broadband Network Gateway / Broadband Remote Access Server, the NAS in ANCP terminology.</t>

<t>HGW: Home Gateway, the residential gateway terminating the subscriber PPPoE session.</t>

<t>OLT: Optical Line Terminal in the PON access network.</t>

<t>ONU: Optical Network Unit, located at the subscriber side; in many deployments the HGW and ONU are integrated.</t>

<t>OMCI: ONU Management and Control Interface (ITU-T G.988), used for OLT-to-ONU/HGW configuration in PON systems.</t>

<t>Home Agent: Local AI application running on home devices (smart speaker, local PC agent, home panel).</t>

<t>Home LAN: The private subscriber-side network behind the HGW.</t>

</section>
<section anchor="scope-and-design-principles"><name>Scope and Design Principles</name>

<t><ol>
  <li>ANCP supports two peering topologies: BNG-to-OLT, or BNG-to-HGW. When ANCP peering is BNG-to-OLT only, HGW-targeted policy requires additional OMCI provisioning; ANCP itself does not reach the HGW in this mode. For the use cases of this document, ANCP peering is BNG-to-HGW; the OLT performs transparent TCP forwarding and is not a policy endpoint for these extensions.</li>
  <li>Application policy is decoupled from the underlying forwarding path. New services do not require VLAN re-provisioning or end-to-end forwarding changes. Policy is subscriber-session bound and follows the PPPoE session lifecycle. Policy identifiers are address-agnostic. Identification of the application service is independent of IP prefix, destination address, or VLAN assignment.</li>
  <li>The HGW is the enforcement point for home-side application policy. Extensions are additive TLVs. Legacy ANCP implementations (BNG-to-OLT) continue to operate unaffected.</li>
</ol></t>

</section>
<section anchor="use-cases"><name>Use Cases</name>

<t>All use cases in this section are illustrated under Mode B: ANCP runs directly between BNG and HGW, and the OLT transparently relays the ANCP TCP session. In the diagrams, <xref target="RFC6320"></xref> denotes the ANCP control-plane channel; ---&gt; denotes the user data-plane traffic.</t>

<section anchor="managed-large-model-access-for-home-agents"><name>Managed Large Model Access for Home Agents</name>

<t>Home Agents running on residential devices request access to large model services. The HGW centrally manages model service credentials for home applications. The operator-controlled policy delivered via ANCP instructs the HGW to steer home-agent model requests to the operator-hosted large model platform. The operator retains control over service access without requiring each home agent to maintain independent model endpoint configuration.</t>

<figure anchor="f1">
<name>Use Case 1: LLM Access</name><artwork type="ascii-art" align="center"><![CDATA[
  [ANCP: model steering policy + credential reference]
+----------------+                    +----------------+
|      BNG       | <----------------> |      HGW       |
+-------+--------+                    +--------+-------+
        |                                      |
        |      OLT (transparent forward)       |
        +-------<---> OLT <---> ONU <--->------+
                                               |
Operator Large Model Platform  <---------------+
                                               |
Home Agent (Speaker / Home Panel) <------------+

]]></artwork></figure>

</section>
<section anchor="differentiated-service-in-application-granularity"><name>Differentiated Service in Application Granularity</name>

<t>Traditional residential value-added services such as remote education and online games often rely on dedicated VLANs. This requires end-to-end VLAN planning and configuration across HGW, OLT, and BNG, which slows service activation.
This use case deploys traffic classification on HGW to distinguish applications and uses overlay tunnel to carry traffic. It is not tied to a fixed VLAN or destination prefix. New services can be activated by pushing policy via ANCP without modifying the underlying forwarding path.</t>

<figure anchor="f2">
<name>Use Case 2: Differentiated Services</name><artwork type="ascii-art" align="center"><![CDATA[
  [ANCP: model steering policy + credential reference]
+----------------+                    +----------------+
|      BNG       | <----------------> |      HGW       |
+-------+--------+                    +--------+-------+
        |                                      |
        |      OLT (transparent forward)       |
        +--------<---> OLT <---> ONU <--->-----+
                                               |
Remote Education / Online Game / Home App <----+

]]></artwork></figure>

</section>
<section anchor="authorized-remote-access-to-home-lan-person-to-home-connectivity"><name>Authorized Remote Access to Home LAN (Person-to-Home Connectivity)</name>

<t>A subscriber's mobile device (outside the home network) accesses authorized home LAN resources such as NAS or cameras. Authorization scope, allowed sources, permitted home destinations, time windows, and bandwidth limits are defined at the BNG and delivered to the HGW via ANCP. The HGW enforces the access control policy. Access is only permitted for authorized sessions; unauthorized probes are rejected. The policy can be revoked on demand.</t>

<figure anchor="f3">
<name>Use Case 3: Remote Access to Home LAN</name><artwork type="ascii-art" align="center"><![CDATA[
  [ANCP: access ACL / whitelist / time-window policy]
+----------------+                   +----------------+
|      BNG       | <---------------> |      HGW       |
+-------+--------+                   +--------+-------+
        |                                     |
        |     OLT (transparent forward)       |
        +------<---> OLT <---> ONU <--->------+
                                              
Mobile Phone <-------------> NAS / IP Camera / Home LAN

]]></artwork></figure>

</section>
</section>
<section anchor="protocol-requirement-overview"><name>Protocol Requirement Overview</name>

<t>This section identifies the aspects in which the baseline ANCP protocol (RFC 6320) does not yet cover the use cases above, and the directions in which protocol enhancement is expected. RFC 6320 was originally designed for line and port management between a NAS and an access node; its existing TLV space and session model do not directly express home-application policy. The items below are open enhancement topics rather than finalized protocol mechanics; detailed TLV semantics, encoding, and state machines are reserved for a future revision of this document.</t>

<section anchor="new-peering-model-bng-to-hgw-ancp"><name>New Peering Model: BNG-to-HGW ANCP</name>

<t>Baseline ANCP defines the peering relationship between NAS and AN (OLT/DSLAM). The ANCP extensions are required to define how an ANCP session can be established and maintained directly between BNG and HGW, including:</t>

<t><ul>
  <li>Session discovery and association between a BNG ANCP peer and the HGW behind a given PPPoE session;</li>
  <li>Session establishment, keep-alive, and teardown lifecycle aligned with the PPPoE session;</li>
  <li>Behavior when the ANCP session to the HGW is lost, and the relationship to any parallel BNG-to-OLT ANCP session.</li>
</ul></t>

</section>
<section anchor="home-application-policy-tlv-set"><name>Home Application Policy TLV Set</name>

<t>Baseline ANCP TLVs carry line rate, port status, and basic configuration parameters. The following policy categories require new TLV definitions:</t>

<t><ul>
  <li>Application Policies: classification rules, tunnels;</li>
  <li>Service Steering Policy: endpoint and steering instructions for model services;</li>
  <li>Credential Reference: an opaque reference to model account credentials managed by the HGW;</li>
  <li>QoS Profile: priority, shaper, and scheduler treatment associated with a service identifier;</li>
  <li>Remote Access Policy: source whitelist, allowed home destinations, port constraints, time window, and bandwidth limit;</li>
  <li>Policy Lifecycle: activate, refresh, revoke, and policy versioning.</li>
</ul></t>

</section>
<section anchor="policy-state-synchronization-and-reporting"><name>Policy State Synchronization and Reporting</name>

<t>Baseline ANCP supports limited status reporting. To support on-demand service activation and revocation, the protocol needs enhancement for:</t>

<t><ul>
  <li>Per-policy installation result (success, partial success, failure with reason) reported from HGW to BNG;</li>
  <li>Active session and resource state reporting for home services, including remote-access session state;</li>
  <li>Policy revision synchronization so the BNG and HGW can detect and recover from stale or mismatched policy state.</li>
</ul></t>

</section>
<section anchor="interaction-with-omci-in-the-bng-to-olt-mode"><name>Interaction with OMCI in the BNG-to-OLT Mode</name>

<t>When ANCP runs only between BNG and OLT (Mode A), policy reaching the HGW is out of ANCP's scope and relies on OMCI. The enhancement work needs to define the boundary clearly: which policy categories can be mapped onto OMCI configuration, which cannot, and how the two control channels relate. It should be stated explicitly that this document's BNG-to-HGW extensions are not required to be carried over OMCI.</t>

</section>
<section anchor="interaction-with-existing-management-protocols"><name>Interaction with Existing Management Protocols</name>

<t>The relationship between the proposed ANCP policy channel and existing HGW management mechanisms (e.g., <xref target="TR-069"></xref> CWMP) needs to be scoped: which functions remain under device management, and which are session-bound policy delivered over ANCP. A clear division avoids overlapping or conflicting configuration.</t>

</section>
<section anchor="open-encoding-and-interoperability-issues"><name>Open Encoding and Interoperability Issues</name>

<t>The following items remain open and will be addressed in later revisions:
- Allocation of TLV type codes and sub-TLV structures within the ANCP TLV registry;
- Error and rejection message formats;
- Compatibility with existing ANCP implementations that do not recognize the new TLVs.</t>

</section>
</section>
<section anchor="security-considerations"><name>Security Considerations</name>

<t>ANCP sessions between BNG and HGW <bcp14>MUST</bcp14> be authenticated and integrity protected. An attacker must not be able to inject or modify policy messages.</t>

<t>Remote access policy is sensitive. The HGW <bcp14>MUST</bcp14> enforce the least-privilege rules delivered by the BNG. Policy revocation <bcp14>MUST</bcp14> take effect immediately. The HGW <bcp14>MUST</bcp14> log policy installation and remote access events for operator audit.
Model credential references are opaque identifiers. The ANCP channel <bcp14>MUST NOT</bcp14> carry raw secrets. Credential material is provisioned separately by secure operator channels.</t>

<t>The address-agnostic service identifier mechanism <bcp14>MUST NOT</bcp14> be used to bypass existing access control or subscriber authorization.</t>

<t>When OMCI is used as an alternate delivery path, OMCI security and authentication requirements also apply.
Privacy Considerations Remote access policy and home application policy are subscriber-specific data. Operators <bcp14>MUST</bcp14> handle policy data in compliance with applicable privacy regulations. Logging of home LAN access events <bcp14>MUST</bcp14> be limited to what is required for security and service operation.</t>

</section>
<section anchor="iana"><name>IANA</name>
<t>TBD.</t>

</section>


  </middle>

  <back>


<references anchor="sec-combined-references">
<name>References</name>

    <references anchor="sec-normative-references">
<name>Normative References</name>



<reference anchor="RFC6320">
  <front>
    <title>Protocol for Access Node Control Mechanism in Broadband Networks</title>
    <author fullname="S. Wadhwa" initials="S." surname="Wadhwa"/>
    <author fullname="J. Moisand" initials="J." surname="Moisand"/>
    <author fullname="T. Haag" initials="T." surname="Haag"/>
    <author fullname="N. Voigt" initials="N." surname="Voigt"/>
    <author fullname="T. Taylor" initials="T." role="editor" surname="Taylor"/>
    <date month="October" year="2011"/>
    <abstract>
      <t>This document describes the Access Node Control Protocol (ANCP). ANCP operates between a Network Access Server (NAS) and an Access Node (e.g., a Digital Subscriber Line Access Multiplexer (DSLAM)) in a multi-service reference architecture in order to perform operations related to Quality of Service, service, and subscribers. Use cases for ANCP are documented in RFC 5851. As well as describing the base ANCP protocol, this document specifies capabilities for Digital Subscriber Line (DSL) topology discovery, line configuration, and remote line connectivity testing. The design of ANCP allows for protocol extensions in other documents if they are needed to support other use cases and other access technologies.</t>
      <t>ANCP is based on the General Switch Management Protocol version 3 (GSMPv3) described in RFC 3292, but with many modifications and extensions, to the point that the two protocols are not interoperable. For this reason, ANCP was assigned a separate version number to distinguish it. [STANDARDS-TRACK]</t>
    </abstract>
  </front>
  <seriesInfo name="RFC" value="6320"/>
  <seriesInfo name="DOI" value="10.17487/RFC6320"/>
</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="TR-069" target="https://www.broadband-forum.org/pdfs/tr-069-1-6-1.pdf">
  <front>
    <title>CPE WAN Management Protocol</title>
    <author >
      <organization>Broadband Forum</organization>
    </author>
    <date year="2020" month="June"/>
  </front>
  <seriesInfo name="Broadband Forum" value="TR-069"/>
</reference>
<reference anchor="ITU-T-G.988" target="https://www.itu.int/rec/T-REC-G.988-202211-I/en">
  <front>
    <title>ONU management and control interface (OMCI) specification</title>
    <author >
      <organization>ITU-T</organization>
    </author>
    <date year="2022" month="November"/>
  </front>
  <seriesInfo name="ITU-T" value="Recommendation G.988"/>
</reference>


    </references>

</references>



  </back>

<!-- ##markdown-source:
H4sIAAAAAAAAA+1b7XLbRpb9j6foVap2pA1BWU4qk9CJZ2lZdjSlr5Hk8aRc
rq0W0CTbBgFMNyCGEyfPss+yT7bn3u4GGiStsbO7/1ZVqZAg+ut+nHvuve00
TRPbyDL/D1lUpZqIxrQq0bXhT7Z5/OjRd48eJ5lsJkKXsyqx7d1SW6urslnX
eP/05PbFjhmSvMpKucTX3MhZk65lOU9lmdXpolqqVNZ12lqVSavSR4+SpNFN
gXdfWSWO8cyKfxXX6u+tNmqpysaKWWXE9OL4KpF3d0bdT/hL/3pSYPqJUGXy
fjVJhEgFLZXItllUZpKkwlSYHj/o0k7Ei7H4Ce/jq9vhC1XOw5PKYJ7jhS6l
OK/udKHwzDZGKZz/b60sVy02JF4r24gbfozfM92sJ+KZ0u80z5FVbdkYPDq+
wDe1lLqYCBLADAv9e0aTL3nucVYtNzf357G4qaLN/VnLMjz5P9ucxfzvsND6
3Xprf0lZmaVs9D3v8frF8TdfPX40ScgYoue31+mjb76jT0J4Ze4dX52I19ML
cS5LOWdFiitTNVVWFXv8YtCP4D8+3TNTyfwO1iReVKZd8k+5bDDd40ePH2EN
t4I0czr0omlqOzk8XK1W47swMp3RyDGmO6zzmT1sDG0tPUq/SY/GeMIzWGW0
snSIsPzGyhN/pAQ/753evkpv05fj7779dm94xsuLV2LZn4+GZ3ANqBTqbJSZ
yUyJ/cvz49MDYWuV6ZmGL8F7PioBXmt47sfp0dHg3HvxwXXTjrHWoVHZ4W16
fXLsNprSwKOj9PRQ+cW2z8xrTeBqUDT2n/POBA9PkjSFG93BvmTWJMntQlsB
p275nLmymdF3cFR4scjYZclHm4US0yxT1oqLKod3elkEvUMoggBAAAAKLwk7
EquFMngW6eBCNavKvBcvIYOVXIv9ZxcvD59dT28OhPo5W8CZsGKAkjCTqCt8
XIuVbhaY7UdaqJvgx5evD8YON5b4XtXK4Ceh8K4y4g7rKTgPlmElXp7djqAP
kQOCsqZYb72A6cbi9QJPeErTllZU5Y4XeSaZ55p2KAsyj5met8bt+F5LQdYh
IF3jEC8XTYXPMluwOHmhW3zoJQ0hNgN1SEhPF0VLymowAb+gxJJU4GTbb/LB
E5Ge45Wy6l6RVgEmojZ6Kc1a2EyV0ugKYOUsPxfSqRz7dmKtDGDe0k4Kslje
SEH2d6/x4ijWfipXtPu/VDej2HsKjAX4V9BQPzlbzhkQxShbtQaPx8LZ6VLn
OeAw+UKc0vC8zWjuJAFcCcIrGOxMlzjQPzXQfZLUQSec2Cb9uBscA0KJLJJ+
BErH82KakVDj+XjkDOD5zdn0HPZ3Q5FSmtwpRLP/5Ow6BfYHNCebNKquTAO8
Hgn6MDQZJybIC48rkwOs2ZBkw2fzwiqxByjztCRR6Rw2omF6V5cXEERdVGuO
qqNtbyDDWQUtOnsl3UHVkDOCDk42nZDFpE2V4mA8wziyrh3WP4ZOnL3SVKPg
pASPZe4P7w0dVleWVYNZsM8CoYW8oTfYNS/0hB3mTYTJbze9J5MGhjr0tJmp
lrwObRvv+CUPgeDj7nDPusPRbjYP9zAY3Ia5jSxtDaMu6VWcDgaee8ujqW7x
H3zLstYwOK8UKaxxAaM2ymnyY+B2e/ZXS4vhyNr2bh67PwQli+IBwPB+TmfE
kkuyIe8bV1dX1clge0B/K6T71W9BUezPXMSrK2ybdcgbJmMbgPtYXHpIsMBl
uyDR16a6p/cCIHTD45GM4lXbiIWS9+uV0vMFxR0aEEdcihKzolpZQmtyH52J
vxJGWIRo4jJznMBU8Amc1jsjHQuqG388qjWbeLtaaI/HpPM+BH0s+gSDxlBn
WG5V54oz7ZeoA+rAWljE8GJyx1JBi6rEGl7KEJptawYDjFs6Y3uv1tA9GJiT
NE0yIUs+xggjC/0PTBLwuGMl1cxJeno62LvHDUZgOJEHjF7OTzDvcz2bKcM/
kZV57RHyxDPNYf4tYB+8kwZdlmkOllnmI092eFufAO28IohJi6lJidESYWWK
E2Qh7Nre0fBuWktowGsIKFzKO55iJhGSTL/vLIgOhvDFF8OE4wyDW5zdOQpJ
GoYGL947f3Vzuzdy/xcXl/z5+uQvr06vT57T55sfp2dn3YfEv3Hz4+Wrs+f9
p37k8eX5+cnFczcYT8XgUbJ3Pv1pz9nO3uXV7enlxfRsbzcBgBTvVA8iFJZt
EkyaOcGz46v/+s+jr8Uvv/wLAiPI4Xe//uq/fHv0x6/xBWTBBxjmMu4rLG6d
QP5KGpqFoCWTtW5kQaHcCruoVqB1MA0I8t/ekGTeTsT3d1l99PVT/4AOPHgY
ZDZ4yDLbfrI12Alxx6Mdy3TSHDzfkPRwv9OfBt+D3KOH3/+Jw3V69O2fniZE
O24ZRquimq+ThGB+8iDNGHlCwmoJJAXSC5xi8gAVPox+u3Z+NGAmrDBxMb2h
uTniNP3msAZgaTLgxm5ATBTmfqkQHMh76B0k/86czDBQYFYA6wRQD/jF+DMS
jhOJLAIbJfYR6Ik7Eg27eNUPCyd9VepmJIoqY5zxzCZamzb6hKYFrqxjRtPB
LlMPpGZMjOERcw6MtB6ow4R/Oh9mbUFDp33WxgzDZUMHo56o4aTMfi5eHTJl
GbAMbIrOadeAmqUlaTPYzrHMRJxVdMoN5AWzKEm+lc+MXIizYt+CbTeUNMr3
pNSCB18dC0mTjdzLtSxVcRCWAX5OODKAqt8Tnetl5gKzlztwAoEx79ILMuCb
DKGCJfEchjDHMYwuM10XyibJkWdBPgZZJom1Qj5JhlHVZFqaWGLPDDl76rlU
nCuFgQCwiEkS4IxoO6nLciFtH1A9s7NxFsU5E/MIsj/M9sQz6saqYtZzqkEe
1eEmMaYx5fkbgR7BcYCro49tGJM96cgkQizVQmzM/Jjl9SHJBX+3JdnTqLxn
T5gM21A/gxRb5k1O6tv0grbnwiLZYyC1Lai0KdYc5vpVKRCO4VarnmrllZcL
y9RRJaPSWJSkOeyNzon/xfP5mDoWV91eYhPzrPGuajkhoqEFU7NtZlnomcrW
WaH6uQI1MsxkSNnQuU3lvEQqqTOkEf4NLw9WltpJDIgbQyA1JRiQL948hRYN
IPdnQl5MF7ImtwgbK4tCWjJ+z5GPHM9iy3GH+Azm6/U1FiedTsO5NFXNPJE/
U3OZrb3xLqFUmtsTuv3ePQ6YwOmyVX2WTVqXoGSZg7YvonpoMt3J/63K3LE3
6gVsPV0G9GkJj6MJzc6kx6hCrnenPD4bBM5pCVReQvZvfFHxLVQD21TRQM9a
07oA0LH5Ae+eCKT8Twcv46iG6mXSv4ntzGAojtid+yrFGdcizrkW4SMmaa9H
aBvDtY2ROQ6OAaDJhajU2pPYXcWO3oQyR8shHker7fDNiHfvToj8VF2FJaqU
eGjoc2YqKzmTKqHjNotCI6USDQDNJ5h0VL8RfyAbsuOHajkQc0OgN9wTpmgk
luyzjfsB4WZBhbzOQRAJmDHaHXfus50lpqGpBn7slu5gcxB5oepfJuCm8N4f
9kjUyuxRFwAZxw97syN8Nhz7Umpb/LAnbaZ1imd7rpT7w15wHnGEQH127i1k
79ck+e2336gK/MbROq+0xscEL/ov47QJQEN5UqbeJl+mG39fih1/228lH3xV
Gg7n/j6I7zffeir8W6RX/1a3Yjfnwyt2ryfhpw+73t/++7A5gGBgPw6BPnAc
bA0Ia37PZ6Bx/hNoGX/a3NIn/n1IQq1h4OtX3lbFlgR/xwo9QIj9G8fNwMj5
6RWTseEiX3rzAQxtpM83IVaVgyj/sk+fkXsa2TGeGILuZdHCd/O8T8MpEsOL
pA25tcrbkNu7dI44+VwumeYgIhFIrwnbMIl2TJsiYKgtdaQrYgIcIQlgy0Bp
huT3Y4WWkS+fWCYDu/JvXjLEK8/obUBxkRUUlvvAXwYgyzWF8nlLdaUYKXnh
lhkdAKigTKalyNHXBkOAEKdN4GWNdsVDKUATvDS4BRDxBcchNihVJkvKvP15
XP2tbu0igocOjwP4AUX0bB3yqofY24O49vgzcO3x5CMm+P8g94C/bwz4fJD7
Jyj3OyDIJ/0nnYMfikvn3i/h3gGNACpOmBEETfsK3LByALMPGaTYvwIFr0pO
c+gZMuOSeOM9IOkAzDKi/H8gDkOd4lCY3YdtMxEOFeyQch746E9ZXL+J7apf
h2JUv6CyJU5kJEApbN0TfcpWR1SKqlaEgW7wiFKxpW6aMHXkuvix0Xi0AqEA
CjlsohrKSufNAvkIxjmCHiozvu4QKG9PrvrmQefXPcvzGYKNuzGBDYWMwAtd
+45hv2mifZF4PGW2T4jo94+Rq1GNmvZq1DtH/13a79zU45FR99V7KgETxFMF
9mGK9NVnQMlXk4/bTwCTDku8EKbHZzBNBIIGggRtPmR9pE4ffuufCCW/D0l+
P5D8j3FkE0Y+G0X+l5lS4q6PiKtFBdQYCuopu94hZczH7HwBUKDbgCR9uzQq
movLe4onauXbKiHZ3Oh5SLoG0Ww0Ve5gVYxgrt7SNWNDafSgr+isVdO1pePa
jbzDwz4pdakrk4FupW7euLWCnaqfa+9FXb94JamhpOdUwCwos6KyQNyppXW4
HxP1ovqmMYnQd4WjjuwTKk9hNcdaqAAgYACZmyxURlzo9WWaLgHHFqlQ8bGu
oPN/TTVH7AKgyOgAjCw32ki1zsDtJN95aPADuE7pW0WddJaKEm28+ATnRhJG
GSbvlVCkwXPqqWRVzg1q3jp3rZeS2m0dMBE9CpAmZm3T8lNXZNoqtLlEnVjV
laccTN23urFJ8mxgKXFbP1TpqPjAil/oulNJUAjFN7jRYejH34ZKgxpWaeJu
slsEol9xl/8i6t96qEWYoR6TXShX9wrZ66B7vauEosusaEmQ3Li78bOC1rKF
r50NWVtl2mk7upaAabriZGf1JCdf3JVijnhVDutuT6JVuk27Sud7pepUUozz
TqQASNTY6Up1LnTgTF2Hc2vuZ2oh7zVUTp2jvowTxBVFTii/qGzTO+xAbUTD
S0RGSQUTuMPGjYOo7wCzCXSn84mrrlOOwzabNkN1N58F8EMqgfmLFmTIbccN
LKUegwSH9rNUiJu+FuPqmxFDpjxqXtE1q67CWsKoaSdsRZzMWVb21oa5gL6R
6pi2IFrjshfrtOeyp5vAzd1hJ31ZxHlkKFn7+g8bNvnisDpFMx73nP46cPoJ
WXpVy7+3qif6XJfh4cA0ukY4KFmFu0BIfryOaXK6p4JgMdN0W642MA2wyJGw
C1lTU4P3msFtcE4AklGycR0Zb/PB2GRf2u3KxDT9kIUEUTg62HONnijuYIXh
hg3VQjXfiol44k6aSAt7EzsLvjHp0r8RCQzwtxh5BjbyscIlgrAdV2V3tuvn
uWEEvVmDjBn8+o8+cb8Od4E2zbjrxfCeVO6Nt788BBPtbw1UoQ2/I/3mdWiv
mb9gNLiaQHcR7CCKzOjGIslAmbS7zIPVi8IbrbJt0Yh9UPmMi+twGzav7sEM
QYXiAeuWrj5U5YHfeGhq+Awfjk/inmZcMo/vpYSUYfPOVF877e+bdTDriyOp
D8phPp4iUmsXp+yGRmw1yAn8lSUKkwB5vy1HTvgQJBRFacxS26VsyNCDIfCS
zga45Siz7tKLvxBYhqUC8lFITJJPvHMo9t1trYNR30aT7j5MBMFUikAspumQ
y9muBwgwJgzDhmgvDuxiE+AuorOMPkAykaPeD90ShE9IU8AZPfXawkcfOpd0
sYCSFMzD59647OaGu3thzpMoDtNS1IMMmZXvDFgXRRSXdeyiaouc1mBZ58Sh
CGYpGPNNmwED+UPc29tkA1HHLPf3LCiAUMGIlc1C2q3Lk8D2dtyCtu52yU7C
4n2wrqjt7AK9F6E7Kouio5K054iIegZnwQb33SXEN+4281tx/Pr86qBXHUmH
tJ4HRc3a0kcLQ5fDS98b2rp45XThxpCIvCulrvm31ZBgMfn7dM42wHK8k8n7
SuehVFfXvgNJdoBJ+HiblX4I+pK47YmnobwXFj13IpDbIMqIU2tb5WXcR2pH
kv3hmCHzQXRRcBHPNQTdxQwyJdOBgaV/SDAtiqrvP1Jcp2QZG8yVqzra9i5l
ssxht6UKKtmBjtgQ/WzUHKozfEXqxJjKeLd755OmJTYBSQt3yd7F6WpZY2V/
ODauTv8724ds5F2/N6vmgDHnpZ6TWNf5V1lLUZkKPVS7cVK27hpLV4PYxV8F
3+whqbWYlVIDd2GDet186YJmpUDis6spXVNtZEY182VrG+HveoKGMrnQJR1f
OJaiZ+tgRl4YtN3rwcWxviVuyV0pRvSVGN6cL8fwqWF1tknpbgTYCGTL5Cqy
Uc9c6GZgFAiCunm6Rr4HEHLPFeJeqpw4SrHeWLSo5mJXYHQqjg+g7rt/3tL1
0CQiFRIi17vYVXC1Prljdha1zaNsJoBEuHrl+a6RVLbGnA1ePo7v+cHQ6QMk
2d0E4AIUMV46IQnHkqFEzb4Auv426WbDfgdl64Gp39mdcldrCIzWtbRRgrxR
PqMLnv0lIBkXBMc+Loar9DyjtJx/FzgbXXANml5zYX3k3rXB+DnT6s3Y8Zjo
QiAobsU9hvU4uaLrNdmmw4idtuki1nLX1QCHm9H9Cf/vQ7iRHd+bZVlBbnnR
1fjoFYKoDKBQaIrLnii7Vcihar9LQE1bhA7yWTWfM8DO+uLr0BaDTwdaCb2s
CEjiK9ZkrwPJBVV3F8cZWU6nF9Pk9tnzMd/Rv4PjJ/8NY6ACp3A2AAA=

-->

</rfc>

