<?xml version='1.0' encoding='utf-8'?>
<!DOCTYPE rfc [
  <!ENTITY nbsp    "&#160;">
  <!ENTITY zwsp   "&#8203;">
  <!ENTITY nbhy   "&#8209;">
  <!ENTITY wj     "&#8288;">
]>
<?xml-stylesheet type="text/xsl" href="rfc2629.xslt" ?>
<!-- generated by https://github.com/cabo/kramdown-rfc version 1.7.43 (Ruby 3.2.3) -->
<rfc xmlns:xi="http://www.w3.org/2001/XInclude" ipr="trust200902" docName="draft-ietf-dmm-srv6mob-arch-05" category="info" submissionType="IETF" tocInclude="true" sortRefs="true" symRefs="true" version="3">
  <!-- xml2rfc v2v3 conversion 3.35.0 -->
  <front>
    <title abbrev="SRv6mob-arch">Architecture Discussion on SRv6 Mobile User plane</title>
    <seriesInfo name="Internet-Draft" value="draft-ietf-dmm-srv6mob-arch-05"/>
    <author initials="T." surname="Kamata" fullname="Teppei Kamata">
      <organization>Cisco Systems, Inc.</organization>
      <address>
        <postal>
          <country>Japan</country>
        </postal>
        <email>tkamata@cisco.com</email>
      </address>
    </author>
    <author initials="J." surname="Horn" fullname="Jakub Horn">
      <organization>Cisco Systems, Inc.</organization>
      <address>
        <postal>
          <country>Czech Republic</country>
        </postal>
        <email>jakuhorn@cisco.com</email>
      </address>
    </author>
    <author initials="L." surname="Jalil" fullname="Luay Jalil">
      <organization>Verizon</organization>
      <address>
        <postal>
          <country>USA</country>
        </postal>
        <email>luay.jalil@verizon.com</email>
      </address>
    </author>
    <author initials="W." surname="Cheng" fullname="Weiqiang Cheng">
      <organization>China Mobile</organization>
      <address>
        <postal>
          <country>China</country>
        </postal>
        <email>chengweiqiang@chinamobile.com</email>
      </address>
    </author>
    <author initials="M." surname="Kohno" fullname="Miya Kohno">
      <organization>Keio University</organization>
      <address>
        <postal>
          <country>Japan</country>
        </postal>
        <email>miya_kohno@keio.jp</email>
      </address>
    </author>
    <date year="2026" month="November" day="16"/>
    <area>Internet</area>
    <workgroup>DMM Working Group</workgroup>
    <abstract>
      <?line 123?>

<t>This document describes the solution approach and its architectural
benefits of transforming mobile session information into routing
information, leveraging segment routing capabilities, and operating
within the IP routing paradigm.</t>
    </abstract>
  </front>
  <middle>
    <?line 130?>

<section anchor="introduction">
      <name>Introduction</name>
      <t>The existing mobile user plane is currently defined as an overlay
tunnel session to a mobile anchor point (UPF: User Plane Function in
5G context).</t>
      <t>While this approach may be suited for use cases requiring frequent
mobile handover and functionality tied to session initiation/
termination, it may be challenging in some deployments to cost-effectively and scalably
address the high traffic volumes of the 5G/Beyond 5G era and the
increasingly distributed data and computing demands in the future.</t>
      <t>The requirements for wireless systems are becoming more diverse, and
there are cases, such as some IoT and FWA (Fixed Wireless Access)
systems, where the frequent mobile handover is not necessarily
mandatory.</t>
      <t>This document describes the solution approach and its architectural
benefits of transforming mobile session information into routing
information, leveraging segment routing capabilities, and operating
within the IP routing paradigm.</t>
      <t>This document also clarifies the motivation for the MUP initiatives :
<xref target="RFC9433"/><xref target="I-D.mhkk-dmm-mup-architecture"/></t>
    </section>
    <section anchor="problem-definition">
      <name>Problem Definition</name>
      <t>Depending on the deployment and service requirements, a tunnel-based mobile user plane may require additional design considerations for:</t>
      <ul spacing="normal">
        <li>
          <t>Optimized any-to-any communication</t>
        </li>
        <li>
          <t>Distributed edge computing</t>
        </li>
        <li>
          <t>Fixed and mobile convergence (FMC) /
wireless-wireline convergence (WWC)</t>
        </li>
        <li>
          <t>Coordination between overlay policies and underlay path selection</t>
        </li>
      </ul>
      <t>The scalability comparison in this document refers to the amount of connectivity state needed to represent optimized any-to-any communication, rather than to the computational complexity of all mobile control-plane procedures. In the existing 3GPP architecture, the mobile control plane remains responsible for establishing and maintaining PDU sessions, including the selection of the relevant user-plane functions and GTP-U tunnel endpoints. The conventional anchor-based architecture can maintain one session per endpoint, but traffic between endpoints is generally carried through the selected anchor. If optimized any-to-any connectivity among N endpoints is instead represented using a separate tunnel or forwarding state for each communicating endpoint pair, the amount of such state can grow as N(N-1), or O(N^2).</t>
      <t>In the MUP architecture, the 3GPP session-management functions continue to manage the lifecycle and policy of mobile sessions. Relevant session information is learned by the MUP control plane and transformed into destination-based routing information. A route describing reachability to a destination can be shared by traffic from multiple sources, and transit nodes do not need to maintain GTP-U tunnel state for every communicating endpoint pair. Consequently, optimized any-to-any reachability can be represented by O(N) destination-based entries at a forwarding node, before route aggregation, rather than by O(N^2) pairwise entries.</t>
      <t>This comparison does not imply that all per-session state is eliminated. The 3GPP session-management functions continue to maintain the session lifecycle and policy information required by the mobile service. Rather, the scalability benefit described here comes from sharing reachability information among multiple sources instead of maintaining separate GTP-U tunnel or forwarding state for every communicating endpoint pair.</t>
      <t>Edge/distributed computing can be seen as one scenario involving any-to-any communication. Destination-based IP routing can facilitate reachability to distributed computing resources.</t>
      <t>As for FMC/WWC, there is currently a coordinated standardization
effort between 3GPP WWC <xref target="TS.23316"/> and BBF <xref target="BBF407"/>. These approaches can integrate wireline traffic with the mobile packet core.
Depending on the deployment and service requirements, anchoring such traffic may introduce additional considerations for path optimization and scalability.</t>
      <t>In addition, an anchor that terminates a large number of tunnel sessions may become a scaling consideration in some deployments.</t>
      <t>In the scenarios described above, shared routing information can reduce the need for pairwise tunnel state. This does not preclude the use of SRv6 source routing or hybrid approaches, including uSID-based segment encoding, for path steering. Segment Routing can provide path steering, protection, policy control, multi-tenancy, and support for reliability and SLA differentiation. Segment Routing can also be used in the underlay of a GTP-U-based architecture.</t>
    </section>
    <section anchor="srv6-mup-and-the-5gbeyond-5g-use-cases">
      <name>SRv6 MUP and the 5G/Beyond 5G use cases</name>
      <t>This section discusses the potential benefits of applying SRv6 MUP to selected 5G/Beyond 5G use cases. These benefits arise from representing relevant mobile session information as routing information and from using Segment Routing capabilities where they are applicable.</t>
      <t>In particular, the adoption of the SRv6 uSID (NEXT-C-SID) flavor <xref target="RFC9800"/> can reduce encapsulation overhead and enhance packet efficiency. Since uSID allows multiple segments to be compressed into a single IPv6 Destination Address (DA), it optimizes forwarding performance and minimizes the MTU impact even when long Segment Lists are required. This efficiency is a critical enabler for the use cases described below.</t>
      <section anchor="network-slicing">
        <name>Network Slicing</name>
        <t>Network slicing enables network segmentation, isolation, and SLA
differentiation such as latency and availability. End-to-end slicing
will be achieved by mapping and coordinating IP network slicing, RAN
and mobile packet core slicing.</t>
        <t>In a tunnel-based mobile user plane, meeting end-to-end SLAs may require coordination with the underlying IP network. An IP routing-based approach can provide another way to address this requirement.</t>
        <t>Segment Routing has a comprehensive set of slice engineering
technologies. How to build network slicing using the Segment Routing
technology is described in
<xref target="I-D.ali-teas-spring-ns-building-blocks"/>.</t>
        <t>Moreover, the stateless slice identifier encoding
<xref target="I-D.filsfils-spring-srv6-stateless-slice-id"/> may enable per-slice forwarding policy using the IPv6 header.</t>
        <t>The use of uSID can make slice-specific path steering more packet-efficient. By compressing multiple service and topological SIDs into a compact header, it can reduce the risk of fragmentation and MTU-related issues associated with deep SID stacks.</t>
      </section>
      <section anchor="edge-computing">
        <name>Edge Computing</name>
        <t>Edge computing, where the computing workloads and datastores are
placed closer to users, is recognized as one of the key pillars to
meet demanding requirements of 5G/Beyond 5G era, with regard to low
latency, bandwidth efficiency, data locality and privacy.</t>
        <t>Edge computing is more important than ever. Improvements in New Radio can reduce access-network latency. However, when traffic to a nearby application must traverse a distant user-plane anchor, the resulting path may limit the end-to-end latency benefit.</t>
        <t>Even with existing mobile architectures, it is possible to place UPFs
in a multi-tier, or to distribute UPFs, to achieve Edge Computing.
<xref target="TS.23548"/> and <xref target="ETSI-MEC"/> describe how to properly select the
UPF of adequate proximity. Depending on the deployment, branching traffic or using different UPFs may require additional signaling and coordination. Maintaining seamless handover with distributed UPFs may also require additional design considerations.</t>
        <t>When it comes to the IP routing paradigm, ubiquitous computing is
innately supported. uSID is particularly beneficial here, as edge computing frequently involves a high volume of small packets, such as those generated by IoT devices. Traditional SRv6 headers with long Segment Lists can impose a disproportionately high overhead on these small payloads. uSID minimizes this overhead, thereby maximizing effective throughput and ensuring efficient utilization of bandwidth-constrained links in distributed edge environments.</t>
      </section>
      <section anchor="urllc-ultra-reliable-low-latency-communication-support">
        <name>URLLC (Ultra-Reliable Low-Latency Communication) support</name>
        <t>3GPP <xref target="TR.23725"/> investigates the key issues for meeting the URLLC
requirements on latency, jitter and reliability in the 5G System. The solutions described in that document focus on improving the
overlay protocol (GTP-U) and provide a few hints on how
to map such tight-SLA into the transport network. These hints are
based on static configuration or static mapping for steering the
overlay packet into the right transport SLA. The scalability and operational impact of such approaches depend on the deployment.</t>
        <t>Another issue that deserves special mention is the ultra-reliability
issue. In order to support ultra-reliability with the tunnel session
paradigm, redundant user plane paths based on dual connectivity have
been proposed. The proposal has two main options.</t>
        <ul spacing="normal">
          <li>
            <t>Dual Connectivity based end-to-end Redundant User Plane Path</t>
          </li>
          <li>
            <t>Support of redundant transmission on N3/N9 interfaces</t>
          </li>
        </ul>
        <t>In the case of the former, UE and hosts have RHF(Redundancy Handling
Function). In sending, RHF is to replicate the traffic onto two GTP-U
tunnels, and in receiving, RHF is to merge the traffic.</t>
        <t>In the case of the latter, traffic are to be replicated and merged
with the same sequence for specific QoS flow, which requires further
enhancements.</t>
        <t>In either case, achieving the intended reliability benefit requires ensuring that the redundant sessions use sufficiently disjoint transport paths.</t>
        <t>An SRv6 MUP approach provides another way to address these transport-path requirements.</t>
        <t>Segment routing has some advantages for URLLC traffic.
First, traffic can be mapped to a disjoint path or low latency path
as needed. Second, Segment routing provides an automated reliability
protection mechanism known as TI-LFA, which is a sub-50ms FRR
mechanism that provides protection regardless of the topology through
the optimal backup path. It can be provisioned slice-aware.</t>
        <t>uSID further strengthens URLLC support by reducing packet length and, consequently, serialization delay, particularly on bandwidth-constrained links. Together with appropriate path selection and protection, this can help limit latency variation in applicable deployments.</t>
      </section>
    </section>
    <section anchor="co-existence-and-incremental-deployability">
      <name>Co-existence and Incremental Deployability</name>
      <t>Mobile networks are composed of radio, mobile packet core, and IP
networks (access and backbone), with separate standard organizations
and communities. Therefore, coexistence with existing systems and incremental deployment are important considerations when introducing a new user-plane approach.</t>
      <t><xref target="RFC9433"/> defines the user plane convergence between GTP-U and
SRv6, so that it can co-exist with the existing user plane as needed.</t>
      <t><xref target="I-D.mhkk-dmm-mup-architecture"/> defines the MUP architecture
for Distributed Mobility Management, which can be plugged into the
existing mobile service architecture. In the architecture, mobile
session information is transformed to routing information, and
operated using an L3VPN-based scheme.</t>
    </section>
    <section anchor="sec-security">
      <name>Security Considerations</name>
      <t>The deployment of this architecture is targeted in an administrative
domain, and the functionality is domain specific.</t>
    </section>
    <section anchor="sec-iana">
      <name>IANA Considerations</name>
      <t>This memo includes no request to IANA.</t>
    </section>
  </middle>
  <back>
    <references anchor="sec-combined-references">
      <name>References</name>
      <references anchor="sec-normative-references">
        <name>Normative References</name>
        <reference anchor="RFC9433">
          <front>
            <title>Segment Routing over IPv6 for the Mobile User Plane</title>
            <author fullname="S. Matsushima" initials="S." role="editor" surname="Matsushima"/>
            <author fullname="C. Filsfils" initials="C." surname="Filsfils"/>
            <author fullname="M. Kohno" initials="M." surname="Kohno"/>
            <author fullname="P. Camarillo" initials="P." role="editor" surname="Camarillo"/>
            <author fullname="D. Voyer" initials="D." surname="Voyer"/>
            <date month="July" year="2023"/>
            <abstract>
              <t>This document discusses the applicability of Segment Routing over IPv6 (SRv6) to the user plane of mobile networks. The network programming nature of SRv6 accomplishes mobile user-plane functions in a simple manner. The statelessness of SRv6 and its ability to control both service layer path and underlying transport can be beneficial to the mobile user plane, providing flexibility, end-to-end network slicing, and Service Level Agreement (SLA) control for various applications.</t>
              <t>This document discusses how SRv6 could be used as the user plane of mobile networks. This document also specifies the SRv6 Endpoint Behaviors required for mobility use cases.</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="9433"/>
          <seriesInfo name="DOI" value="10.17487/RFC9433"/>
        </reference>
        <reference anchor="RFC9800">
          <front>
            <title>Compressed SRv6 Segment List Encoding</title>
            <author fullname="W. Cheng" initials="W." role="editor" surname="Cheng"/>
            <author fullname="C. Filsfils" initials="C." surname="Filsfils"/>
            <author fullname="Z. Li" initials="Z." surname="Li"/>
            <author fullname="B. Decraene" initials="B." surname="Decraene"/>
            <author fullname="F. Clad" initials="F." role="editor" surname="Clad"/>
            <date month="June" year="2025"/>
            <abstract>
              <t>Segment Routing over IPv6 (SRv6) is the instantiation of Segment Routing (SR) on the IPv6 data plane. This document specifies new flavors for the SRv6 endpoint behaviors defined in RFC 8986, which enable the compression of an SRv6 segment list. Such compression significantly reduces the size of the SRv6 encapsulation needed to steer packets over long segment lists.</t>
              <t>This document updates RFC 8754 by allowing a Segment List entry in the Segment Routing Header (SRH) to be either an IPv6 address, as specified in RFC 8754, or a REPLACE-CSID container in packed format, as specified in this document.</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="9800"/>
          <seriesInfo name="DOI" value="10.17487/RFC9800"/>
        </reference>
      </references>
      <references anchor="sec-informative-references">
        <name>Informative References</name>
        <reference anchor="I-D.ali-teas-spring-ns-building-blocks">
          <front>
            <title>Building blocks for Network Slice Realization in Segment Routing Network</title>
            <author fullname="Zafar Ali" initials="Z." surname="Ali">
              <organization>Cisco Systems</organization>
            </author>
            <author fullname="Clarence Filsfils" initials="C." surname="Filsfils">
              <organization>Cisco Systems</organization>
            </author>
            <author fullname="Pablo Camarillo" initials="P." surname="Camarillo">
              <organization>Cisco Systems</organization>
            </author>
            <author fullname="Daniel Voyer" initials="D." surname="Voyer">
              <organization>Bell Canada</organization>
            </author>
            <author fullname="Satoru Matsushima" initials="S." surname="Matsushima">
              <organization>Softbank</organization>
            </author>
            <author fullname="Reza Rokui" initials="R." surname="Rokui">
              <organization>Ciena</organization>
            </author>
            <author fullname="Amit Dhamija" initials="" surname="Dhamija">
              <organization>Rakuten</organization>
            </author>
            <author fullname="Praveen Maheshwari" initials="P." surname="Maheshwari">
              <organization>Airtel</organization>
            </author>
            <date day="7" month="September" year="2022"/>
            <abstract>
              <t>   This document describes how to realize the IETF network slice using the
   Segment Routing based technology. It explains how the
   building blocks specified for the Segment Routing can be used for
   this purpose.

              </t>
            </abstract>
          </front>
          <seriesInfo name="Internet-Draft" value="draft-ali-teas-spring-ns-building-blocks-03"/>
        </reference>
        <reference anchor="I-D.filsfils-spring-srv6-stateless-slice-id">
          <front>
            <title>Stateless and Scalable Network Slice Identification for SRv6</title>
            <author fullname="Clarence Filsfils" initials="C." surname="Filsfils">
              <organization>Cisco Systems, Inc.</organization>
            </author>
            <author fullname="Francois Clad" initials="F." surname="Clad">
              <organization>Cisco Systems, Inc.</organization>
            </author>
            <author fullname="Pablo Camarillo" initials="P." surname="Camarillo">
              <organization>Cisco Systems, Inc.</organization>
            </author>
            <author fullname="Syed Kamran Raza" initials="S. K." surname="Raza">
              <organization>Cisco Systems, Inc.</organization>
            </author>
            <author fullname="Daniel Voyer" initials="D." surname="Voyer">
              <organization>Bell Canada</organization>
            </author>
            <author fullname="Reza Rokui" initials="R." surname="Rokui">
              <organization>Ciena</organization>
            </author>
            <date day="22" month="July" year="2024"/>
            <abstract>
              <t>   This document defines a stateless and scalable solution to achieve
   network slicing with SRv6.

              </t>
            </abstract>
          </front>
          <seriesInfo name="Internet-Draft" value="draft-filsfils-spring-srv6-stateless-slice-id-10"/>
        </reference>
        <reference anchor="I-D.mhkk-dmm-mup-architecture">
          <front>
            <title>Mobile User Plane Architecture for Distributed Mobility Management</title>
            <author fullname="Satoru Matsushima" initials="S." surname="Matsushima">
              <organization>SoftBank</organization>
            </author>
            <author fullname="Katsuhiro Horiba" initials="K." surname="Horiba">
         </author>
            <author fullname="Yuya Kawakami" initials="Y." surname="Kawakami">
              <organization>SoftBank</organization>
            </author>
            <author fullname="Tetsuya Murakami" initials="T." surname="Murakami">
              <organization>Arrcus, Inc</organization>
            </author>
            <author fullname="Keyur Patel" initials="K." surname="Patel">
              <organization>Arrcus, Inc</organization>
            </author>
            <author fullname="Jakub Horn" initials="J." surname="Horn">
              <organization>Cisco Systems</organization>
            </author>
            <date day="2" month="March" year="2025"/>
            <abstract>
              <t>   This document defines the Mobile User Plane (MUP) architecture for
   Distributed Mobility Management.  The requirements for Distributed
   Mobility Management described in [RFC7333] can be satisfied by
   routing fashion.

   In MUP Architecture, session information between the entities of the
   mobile user plane is turned to routing information so that mobile
   user plane can be integrated into dataplane.

   MUP architecture is designed to be pluggable user plane part of
   existing mobile service architectures, enabled by auto-discovery for
   the use plane.  Segment Routing provides network programmability for
   a scalable option with it.

   While MUP architecture itself is independent from a specific
   dataplane protocol, several dataplane options are available for the
   architecture.  This document describes IPv6 dataplane in Segment
   Routing case (SRv6 MUP) due to the DMM requirement, and is suitable
   for mobile services which require a large IP address space.

              </t>
            </abstract>
          </front>
          <seriesInfo name="Internet-Draft" value="draft-mhkk-dmm-mup-architecture-02"/>
        </reference>
        <reference anchor="BBF407">
          <front>
            <title>5G Wireless Wireline Convergence Architecture</title>
            <author>
              <organization>BBF</organization>
            </author>
            <date year="2020" month="August"/>
          </front>
          <seriesInfo name="BBF TR-407" value="Issue:1"/>
        </reference>
        <reference anchor="ETSI-MEC">
          <front>
            <title>MEC in 5G Networks</title>
            <author>
              <organization>ETSI</organization>
            </author>
            <date year="2018" month="June"/>
          </front>
          <seriesInfo name="ETSI White Paper" value="No.28"/>
        </reference>
        <reference anchor="TR.23725">
          <front>
            <title>Study on enhancement of Ultra-Reliable Low-Latency Communication (URLLC) support in the 5G Core network (5GC)</title>
            <author>
              <organization>3GPP</organization>
            </author>
            <date year="2019" month="June"/>
          </front>
          <seriesInfo name="3GPP TR 23.725" value="16.2.0"/>
        </reference>
        <reference anchor="TS.23316">
          <front>
            <title>Wireless and wireline convergence access support for the 5G System (5GS)</title>
            <author>
              <organization>3GPP</organization>
            </author>
            <date year="2021" month="September"/>
          </front>
          <seriesInfo name="3GPP TS 23.316" value="16.7.0"/>
        </reference>
        <reference anchor="TS.23548">
          <front>
            <title>5G system Enhacements for Edge Computing</title>
            <author>
              <organization>3GPP</organization>
            </author>
            <date year="2021" month="September"/>
          </front>
          <seriesInfo name="3GPP TS 23.548" value="17.0.0"/>
        </reference>
      </references>
    </references>
    <?line 295?>

<!-- # Title of Appendix A -->

<section numbered="false" anchor="acknowledgements">
      <name>Acknowledgements</name>
      <t>Authors would like to thank Satoru Matsushima, Shunsuke Homma, Yuji
Tochio and Jeffrey Zhang, for their insights and comments.</t>
    </section>
    <section anchor="contributors" numbered="false" toc="include" removeInRFC="false">
      <name>Contributors</name>
      <contact initials="F." surname="Clad" fullname="Francois Clad">
        <organization>Cisco Systems, Inc.</organization>
        <address>
          <postal>
            <country>France</country>
          </postal>
          <email>fclad.ietf@gmail.com</email>
        </address>
      </contact>
      <contact initials="P." surname="Camarillo" fullname="Pablo Camarillo Garvia">
        <organization>Cisco Systems, Inc.</organization>
        <address>
          <postal>
            <country>Spain</country>
          </postal>
          <email>pcamaril@cisco.com</email>
        </address>
      </contact>
      <contact initials="Z." surname="Ali" fullname="Zafar Ali">
        <organization>Cisco Systems, Inc.</organization>
        <address>
          <postal>
            <country>USA</country>
          </postal>
          <email>zali@cisco.com</email>
        </address>
      </contact>
    </section>
  </back>
  <!-- ##markdown-source:
H4sIAAAAAAAAA+Vba3PcOHb9zl+BjL5IVc22LI9nPaokNRrZ8mjG1ip6rJNN
JVtoEt0Ni49egpTcVvm/55wLgGS32zPeVMpfUrVT2yJB4OI+zj33Ak7TNLk/
Vs8T1+oq/5su6socq7bpTGJXjfxy7dHh4Y+HR8nKHqv/bOtsolzdtI2ZO/xa
l/zxX0niullpnbN1dbNeYY7zVzdniW6MPlbfnVetaSrTfpc8LPDny7dv1bu6
ubPVQr1u6m71XZLp9ljZal4ne7lu8fmeqkvbqrZWhWnVh7I4auaZmtuiUO3S
qKxrGlO1ioNV3ShnZGxunG1MLo+TpLVtgalOmmxpW5O1XWPUS+uyTsRU+N/1
1f0P6m09s4VRt840alXoyiR6NmsM1MLXZT1LNWZI8jqrdIn58kbP29Sadp7m
ZZm6ZhiUHj5P9u7M+qFucu5B57nSTlXG5CZPEt21y7rhi8asjG7VHKLraq38
i0SliVJ7TU2pTW5bvN1TXZXVZcnN2rnSq1VhMz0rDEfaynEybp7vurYudWsz
KNK2VhdOWfwPn0NXWYsPvPw3ZrUyVv2mMVjjad3AKKfQS62u1641Jex6XmVT
vDKltgW84E7G/pRx0BTi4FVWd1XbrI/Vr3qlq28k+q/6rpupX+qm+iq532M4
9FrtFvz0o8mW6sqsuhkE+0Y7eNPpNbZR2CLu4C+msR/rapC6wJDpew756d6/
25b89vrkG4n7zti/W404PV2aatErfWkrHeJmkDvjkIfwwU8Zx5Qy5DPF89U3
2sBbu9bqt3pZ1VH434yt1W1loVtn2/Ugf4mhf7vj0J/uMGb6fvW5mydZjT/t
DKs3McBHj5yamaJ+QFwX+D/im4MUDHPISiTwge6+0ebPGo1neHVa6PyrImae
YeSU2PbTgk+2TSczmn9UfJH+cqpOASMNILzuJbzEiHp4rl7r5t5+HSitMv/V
7uC+Xmn7rVDpr3quG3VS2K+S+yMie7fMEtYqqcRb4J/RwfoHSBtzg7yXmeBo
GH51dvrj98+eHYefLw4Pj5OEmXRrktGjXdOcpy+nECxtjXapWzXw3bRy6ayz
Rc7fMFN2547DSORhx//iSObAFBSiNYVxeAqVmtTmcXi5vLuTXFl2K8mTMR0f
K4z4+eez7w//xLFKhZT9/LV6h0TOyfwPWxl1WleI2QXl3sjp8mFIrfI7WAHz
yp+eUBwdHh2mhy/kCTK9BVOARuIHGKturlLKoc6d68zxU7x5dXN9nr59dboh
G/6GMinihWmR6O/clwTg5xsSPH2RHv7wBQk4WL3jphAUKwN0uainR5T35mp6
9OxPR883pLhuu3xNCmOqJUNS/Lmeq9uibXR6BY3Rp9Wb+iF9g9WrbA39lWVX
wdlbsp/926s3b04PlOtWK9A5bonECts6rcGTKr83tf/89enBlzb47PXl5eYG
f/zyBjkYe1FHz6bcjHr6w/Roesj9XWN/z57+sLG/3vygpeohukA2cgGdZXwf
5SeVChvwgUfRr79e9KOn6eGPvyv6NUWnnBT9T4Poz79/se28zkvwCrbxpnEi
36t8QTcuV11rJZv+n4pGOdRTCAbRptNpkqRpqvTMwSEAVsnNEuAFEtuJq4Ap
Z0haQAAqzdVFJ14BOGxqDVpEtVuIPYpWXSQzU5k5H8PTMG3liClMcz7RQz5P
rXuwkd8g5mD5suXRiwmYPYypF5ImzULECuNUhmyLGYG6BgBKYWrEhJY5Hmy7
DN56ftl/sdKNzu2iDPsubZ4D05M9oG/b1HmXcU1qwSjzwbp2JHXXM3/ieygt
ijV0NIfTCYPXKBcgbKHXSdtVlSn6rWJzOk6EQIQx1arGnhFgl2fHvqq4lLnP
kHiCRhL4CGmD+dAeQGCEPb5uaaDeACV44gwa7aD9XLwHYkIvWBf4/ffOEnjV
nD8hbRIkABbkFFRUNg8LAtfbNbwT80DawUbMaXz/JEF5BjMGs6DsCotnS10U
IHVcCRp3NbhMblZFvfY+jdmy2rWpmc/hIcgsUBoXdpkuAD/rBImnYZDSVku7
WNJp5nMk1Hs4XGm8H0nQPvnZrGt8CsXAzjILXsBfMpSQ8PgF7QGzCdHyFZ4f
lcVwgmQlHriIZPOOyWHqTe41NgrFh4gvPlTp6AZbxmzeMfBXLhTRiPslmBGP
OEhMgMq3Y5Q4r5Tz+kaEOXt3ovbP7AcI2APYieDUQeIiHXiQqUTEYD21bT04
QlW3AGF+SpKzTrg3DQKznv5/CuXNnYKBweMKKGRuw3bLGn7npYsZ4O3tZe/c
9xh2nDw+Bpb06dPj4+8Skk+fEmLGZVMje5bqJRHAeuR4iZK9Ihdi1uU6QyR4
pzegrtmmq2G/yuNFOoPb5DsQh6EWPiFPsz5gpZOxqAgSzuaiLvziFsHuUvXn
VWtL+5HYVK3Ttk7ZRMjG+R2DXo7CxTDz9KGCl95JKXcQaZxa98/eghk8QYqJ
YZLuTMH7796BHKRIaXWTB/xAELUPxvR4CTQEG6S5uFhX5eGpbpdQWWFGuOxh
wwpaUVbY2YnXeWjs3UDoq6APzYAis/PcB6JVgkOcQNho6LxwaGNWgCJhSX+o
vImCwhGlmF9XcR2vPR3sw78KJBKshJUBkyM9It8UqbcuQjAzORzLTZGIZJ4+
+0jqHjvfJHj0eJ7gJQ2Lh4rI71Z0CXI7+rvBNmeFdUtOKNbEsBb/8e/Ll7cx
jOGJgNKiE/8VmIiqjxBMO99rqIe+GaSPCcTb7vXNZXob3Bm0M5c0h33dLINX
VEE3Pg0Gjx9vEFhQ9RIijAaUASL0U04UfLbPFNGd+gUJjnA/xESBnJDpppHE
tgR6MMH0exP7UhBofv4lo48cBn4E3VxsLgSdoyLKB+/BBJ0TZWMZAhWcLKgE
5oBJHnQjSvb+JzYiCI/8Cy/jGggD20y23Fgyi/+c+lo09QMTzcX+Rfr0YMJl
/rx/8d9HJA5J8ClC3ueeJA4WNJwif+iFLxMGs9LJbNUZ+rgfIB8WFvl8nQmj
yX0Ai5tvpgaY/io6zc5s4ZAWdEMGNVv3Ym76teT5mH1M7jMMsK8NaBKcKGaG
0fRTdSKPTcx/fN9Q1xFChJmN5hJtklItdRNkCj42b+pSlV3R2hW3V3dNFnOV
CAdGVNWYCRAU8rLHlN6VN0JjZHlA4Pr3TD9lUes8CSjWk91eurGpsIexP2Ij
cIiDHWozbEwReZGhxr7JzSDKzJw0xytRLxaNWexAPz873E0EfrAgoWFa+p/k
5xFW57Xx1MUCHml0Lg1wRHyn0Ue8fvAdEoqwTpN7EPlH/TUo34e8n3un546d
MqTa3iV7l5bkDY+Wrfv4GeejQJd6spUrYXHYOjYs/kO3+swHx0t7gNl2sx5i
GF8j8O7RZcO3vogxf+hpScLq88mYQw/UOUYGgRZQI8icmQobqiEfyPq9zy+7
0+UUPGnb9UZ0jpPPdUaFUNztGN0tEbzb6weCn3jKDlLyBIRDbNNslWoanwYO
gmnkMIs6+ui5EOoTtghiKhE/w0zq8TH2Hj59EodhG+jx0TekPn0Sr4S/RyYN
Y3EvUKlZiGl6UhSBhHx27FYrnd2ZFrKxEPlfEkjJYWJt5oW4EmmjDZXtBnH8
nDF6rhWgJbhiX6SJGaaSSOIkXDOWshLAsTokkiiwb2SJqitnQAhyh41y2IXS
kXHBFIk1xAXGQu0qJad9Kot+50ahpmcgk5MI3DuSgdgF76gLTiIA7bceMGuM
zbSr8MmAVYBSUiP/KatsbEtOBr0L9gtivuV61th85BFjXtVdn78M7h+LINDk
mu8mgyEQ7Yb2nKrrMOhqFCiY9x6a2hw64ePW87VJRLWQSCceUdIWaquytc9a
46ZYI71AH258d/3mBDE3lw5waADsFkWqrZloJI9Fdc/fSXo9NO3geVMpovzh
KpmJL+Y3q/y+mxGSiAt0NPcHtKG8W2HblLJQ43qVTfs1xeyXkL5GYH27l4nB
3M/DjGU8dPfZ1CNP4DS/UwgDI3d5oTRdOKGniJ8rdaiEhy7AWroKwzmEDwWA
f2uzDtEW6GHOAB7ouuycDqf2L179+016muL3gZoX+h429wXvi8ND4NooNOCN
euUwqZ8JOWPJzEOxQxs5IpYhyFi2jeEbli9kLc1jLTfKYX6HUovNfInEfk8k
cgAAdm5Y3EPaUZJQJ6ExtP/y5EA6TpH5uHF+A2sQ5Uq7l8UNUqMfJGzy5pY0
Q2ct019FjYIA1CPFv0Fq8Z2dmPZD6A/bYxpB8mhgFGAV1EATNH0vYei5DWgk
Ryaw0t5ePAFQ1yxxUVcn8YHzD8J8rm+nB4XFTpurCx0hVyIz2YrMvs1UhCY+
x+l7bXvoVq+qnFnZMOyDGA+8JjFji3xpoRohOyU8LBaJfa7kA2TqalPqibo6
uUhGvYFRGotjQsr4g+4GwMmYSEailNim22h7ZOP2QZ9CPdSsN0UE669G3CJi
T2x1jRFUA9rJYh+0LwX6VqR14xSLjWzH6VKLT4gzw6ccj8x4JMjajCdbSlqi
HpoTQN6yqot6QUasfkGtxljgsdm2WgMqSPRurjhMIv44uJqtEt+w+uOjOdCV
JHkLCzGsA3+NB3JBbGgFfjW3Umv7vBSm/8rzPKAJ7ead2nN6mXgcsj45DVuV
0CfMmCb0YkOGFUDxDYE771YGy5vMkt5spD/fjvVOmMbQbafq53WPOHaDWQci
JXmnXolxGNxY0EVgkpoFyOElEwja4hBID3eUc97oIWZlTgBPiiwhVNPysBDu
4lydWXkiDpwbs+J6tAGM49Fi6/hHCPlAeceN4YEH04GKWue+BcOut2uhDUG1
BDGWkTUXNSMO+2LkkZLQw7N6UflS0hP6kDjukHBWwActHbSE8Rk65z75jfrk
+GK7MT/x22Op2EgJzNPjgE2oKDHLg80xYADYiW/Vw0d1T0HgZPc6W0+3VUDB
xdaAddAXJmGpQVndTNV5ydAOsoGPXJgHlGs5SpSR5fypYBpDL4gmgWkkMCRL
RBYtrlAZ3QAgQwYWK5edkw6UHACwi2Bdu9Ub8wR5Enpnjr4nrevWH92wtG19
v29AvgjigYNw/5K4qNLtQ6kxn3Lin1DOqna+9wfBxfjq9vLMJZZIHGig5Sbr
ZrOykmET2a5PCVu+OE1CKfT8+xehFHp8jKffeBARSS09vsEQK4JzIF1yVIMl
hJvlcCEWRxjzgUpYszz8YuUDp+GVEulfRqvIWZec6MRkKPJ/qVXORrkvMzZz
G3nt242KWpeChv0xiw/VUf3ZLyPc92vb8nKCBzsSQ6QfEDrGO440JqqbWcza
1p3b8HvYkBUWVeq5O7mKQCTN3pPBIjpPRk5MvJgwvjfb+/25UrEO1btUbnIA
5w/eJJWV0pgRVB2dZ7VLgElosIbuEk+3ckNIJYvmRoI2hIR6BHVemTvol5TM
iOcYSPQd7I8zyH5FrJ6LegfB2CjeWtAv6GJMAKGX+FVoCQjLoc99FMYRDyVj
bxjKCVTXdU0Y4VOJgtqKWBtDNT2OpTQ03FKOgeFidwI8+fbBiqnubVNXsZIl
1svtCrX/tdcx+nsYSSLdCYRjuPWB6IMNSZ0XUoFHDA+Jh0Q1ciy+knWTTRiv
VI/Q723bhtPhcV04XP7wdyd8Py4eJW4yEt8T6A9j5vgha1iB5yBH0p/+oHCt
s7pQ+1IsHgT8DxRNzYHhSxukBLgk0thbhV4HPKNNWa9K0qaE0o6V0rYnhL6s
85MwKXpKGPqMQBOYcG4XXeg98K6wfx4J8VweBaaxIbpnvf3aDcUZSQDBgp5G
fcLR+aaESChQYlt/1ErKBRQ/R0Q2vAJ1FRsHfRuyGnwmFAkTl/64hfAgbFkc
bWTTRD6WUycAoqcHsS3w2eCBdW+2c5IBt5hfqzwmwdC+Z7pzqtd43vkG1HCo
skQKTWZsuknYu9jq9X8Rwgg5D76bq3yJyxBK1UvOdTqeK/a0+3R61Ys0umVx
CZHw+XXYKhQ/SC62C7fUKe/FsycXP0o/r5kjmbq+CcWSLxImOZlATr19JcYF
PLZO9qWufjnbjzIgoH/Ba6ahJF70OBDtO5/6Jhwu1pKzSKEaJvq0T3viaNCF
REq4ZxKOISwJTmbs/dZMJY9ix7NMd+4B8d9KVRCWYknsS/ZelHAYzPnypHcH
ub7qDyg8z1c9Rf+3+lrNQf9IqWy2jNkSkNQ19N5kdDMt9PeMFbemZJPARCJu
0QgVj2rHXhmb7v3UPXT7vqRQr2jcvgPJ+sJ1Edv9vZH30ggfYlccVyJt1KaK
VWSAJ/flEpKI00+WCukbQ+6opmxGNaU0PXXO5pJeBOz2eaI33pltXDvYKfTl
CVX+xEkPm/Fd3YYMvCeWfJb0/+CAbT1EI9LjtjSjHcZbrpuqT4aGI3wigyGt
K9VdVT9I8+vmPH1zdhItLy0U183S54elU2dXV8nwiRiqX240qy8hhI8FJw2l
2jrma9658X0htv8Axt1KNoioaqNmZGaa3eShhNSoRNlDE74QXBH4Dha5aFnM
B41HKJytfeXgSZoAfiFDGQ4TIXrD8Ryv3+meKOQoAfFwg5zx/sOXyQOwr14Y
71KMMPE4FENClzcuRMQ02Td9he9w00tTrEJ1Ea1+rxvbd9aHRuJWf30PaJpK
lWFiP+2ct6ukti3I0TE4mj8J/ygmZFnfRCPBrAXqAaosvCY7GkQer84vk/7T
/XBTk89pxhmsdRAKyf6UKx7Z8AokPMer2CXhhheJUmtDE7eRc0vaZtjNZgnV
3+kS5Bz2OD5w2agytw5NpEaMpyv+sL8CURlXfwEroNfR5aJwY9DF1mFMk+M7
M/EQyh/r8WoZAYj/psrHSmhEZMFWQ2budzeaeAj1JPnDm00b0m3fGEgIRuMb
Q+IABOG3/UFsjPcYe0W3WMRWL4nTdgnb92HGRwPxGszmdQX/RfKFawTjGwLD
DTS1cQONmvTEa7iiUak3z/5yeRHPZEC7yng2YTIkknYt5+8jyz/uOZOlLrz9
5BtWI7cRqLJu81YLJeSpWOv5MTE1Z6XC4GcBkuQ16c2kPwjZvJgpR1HCf2Ju
9TKen1yc7JbPwiSfwrlJaco6nEHJcZYkIuPkn8NxBs7FC7GMvCT553/Czz11
w5vK3MzJSirzD+pEpem/yrInGWG+YGEj0JE8HofjPpP/y3dzVMbmOyx+4v8l
i3qou4Lwdmd82aurO3XNi4odPKd1nVsCv5GBlh1yNwb9gmjG3//RvbfJTQ0t
1qKWX1GMNShr/ooJwmkZNGUbHo+Td7t42TPA2f8ALqaVWrk4AAA=

-->

</rfc>
