<?xml version="1.0" encoding="utf-8"?>
  <?xml-stylesheet type="text/xsl" href="rfc2629.xslt" ?>
  <!-- generated by https://github.com/cabo/kramdown-rfc2629 version 1.2.6 -->

<!DOCTYPE rfc SYSTEM "rfc2629.dtd" [
]>

<?rfc toc="yes"?>
<?rfc sortrefs="yes"?>
<?rfc symrefs="yes"?>
<?rfc comments="yes"?>

<rfc docName="draft-malis-detnet-ip-dp-00" category="std">

  <front>
    <title abbrev="DetNet IP">DetNet IP Encapsulation</title>

    <author initials="A." surname="Malis" fullname="Andrew G. Malis">
      <organization>Huawei Technologies</organization>
      <address>
        <email>agmalis@gmail.com</email>
      </address>
    </author>
    <author initials="S." surname="Bryant" fullname="Stewart Bryant">
      <organization>Huawei Technologies</organization>
      <address>
        <email>stewart.bryant@gmail.com</email>
      </address>
    </author>
    <author initials="M." surname="Chen" fullname="Mach Chen">
      <organization>Huawei Technologies</organization>
      <address>
        <email>mach.chen@huawei.com</email>
      </address>
    </author>
    <author initials="B." surname="Varga" fullname="Balázs Varga">
      <organization>Ericsson</organization>
      <address>
        <email>balazs.a.varga@ericsson.com</email>
      </address>
    </author>

    <date year="2018" month="March" day="05"/>

    
    <workgroup>DetNet Working Group</workgroup>
    

    <abstract>


<t>This document specifies Deterministic Networking data plane
operation over an IP network. It is primarily aimed at IPv4, but would work with IPv6 as well if a unified solution is desired.</t>

<t>This document is a derivative work from draft-ietf-detnet-dp-sol-01, to augment or replace the text currently contained in section 5.2.2.</t>

<t>Whether this is published as a stand-alone text, or serves as
a focal point to refine the IP design and
subsequently remerged with draft-ietf-detnet-dp-sol-01 is a matter
for the DETNET WG.</t>



    </abstract>


  </front>

  <middle>


<section anchor="introduction" title="Introduction">

<t>This document is a derivative work from <xref target="I-D.ietf-detnet-dp-sol"/>.</t>

<t>Whether this is published as a stand-alone text, or serves as
a focal point to refine the IP design and
subsequently remerged with draft-ietf-detnet-dp-sol-01 is a matter
for the DetNet WG.</t>

<t>Deterministic Networking (DetNet) is a service that can be offered by
a network to DetNet flows.  DetNet provides these flows extremely low
packet loss rates and assured maximum end-to-end delivery latency.
General background and concepts of DetNet can be found in
<xref target="I-D.ietf-detnet-architecture"/>.</t>

<t>This document specifies the encapsulation and operation of
deterministic networking over an IP data-plane.
The approach is modeled on the operation of PseudoWires (PW) over
an IP Packet Switched Network (PSN) <xref target="RFC3985"/><xref target="RFC4385"/><xref target="RFC7510"/>.</t>

<t>It is based on the “simplified model” discussed during the DetNet Interim Meeting held on 14 February 2018 [http://etherpad.tools.ietf.org:9000/p/notes-ietf-interim-2018-detnet-03].</t>

<t>It is also based on the MPLS encapsulation described in draft-bryant-detnet-mpls-dp (this reference to be updated once draft is available).</t>

<t>The DetNet transport layer functionality that provides congestion
protection for DetNet flows is assumed to be in place in a DetNet
node.</t>

<t>This document does not currently define the associated control plane functions,
or Operations, Administration, and Maintenance (OAM).  It also does
not currently specify traffic handling capabilities required to deliver
congestion protection and latency control for DetNet flows at the
DetNet transport layer. These aspects may be included in future revisions of this draft, or in other DetNet documents.</t>

</section>
<section anchor="terminology" title="Terminology">

<section anchor="terms-used-in-this-document" title="Terms used in this document">

<t>This document uses the same terminology as <xref target="I-D.ietf-detnet-dp-sol"/>. Please see that document for the definitions.</t>

</section>
<section anchor="abbreviations" title="Abbreviations">

<t>This document uses the same abbreviations as <xref target="I-D.ietf-detnet-dp-sol"/>. Please see that document for the list of abbreviations.</t>

</section>
</section>
<section anchor="requirements-language" title="Requirements language">

<t>The key words “MUST”, “MUST NOT”, “REQUIRED”, “SHALL”, “SHALL NOT”,
“SHOULD”, “SHOULD NOT”, “RECOMMENDED”, “MAY”, and “OPTIONAL” in this
document are to be interpreted as described in <xref target="RFC2119"/>.</t>

</section>
<section anchor="detnet-over-an-ip-network" title="DetNet Over an IP Network">

<t>The “simplified model” of DetNet, as discussed during the interim meeting, is carried over an IP network is shown in Figure 1:</t>

<figure><artwork><![CDATA[
DetNet    Edge       Transit   Relay       Edge        DetNet
End Sys   Node        Node     Node        Node        End Sys

+-----+             End to End Service                 +-----+
|Appln|<..............................................>|Appln|
+-----+  +---------+ DN Flow +---------+  +---------+  +-----+
| TSN |  | Service |<------->| Service |--| Service |  | TSN |
+-----+  +---+ +---+ +-----+ +---+ +---+  +---+ +---+  +-----+
|DNXpt|  |Xpt| |Xpt| |IPXpt| |Xpt| |Xpt|  |Xpt| |Xpt|  |DNXpt|
+--.--+  +-.-+ +-.-+ +-.-.-+ +-.-+ +-.-+  +-.-+ +-.-+  +--.--+
   :       :     :     : :Link :     :Link  :     :       :
   +-------+    /-------\+-----+     +------+     /-------\
      TSN       |Sub N/W|                         |TSN N/W|
      Link      \-------/                         \-------/

      Figure 1: Simplified Model of a DetNet Enabled Network
]]></artwork></figure>

<t>In this figure, “DNXpt” and “Xpt” are abbreviations for “DetNet Transport” and “IPXpt” is an abbreviation for “IP Transport”.</t>

<t>DetNet End Systems sent and receive packets over the DetNet. The
supported packet types are IP and Ethernet.</t>

<t>Note that in the Simplified Model, while the DetNet service is end-to-end, the End Systems are not DetNet-aware and do not include DetNet information to their packet headers. Rather, the packets between the End Systems and the Edge Nodes may typically consist of application information, L4 Transport (such as TCP or UDP), IP, and Ethernet headers, transmitted over a TSN link or (sub)-Network between the End System and the Edge Node.</t>

<t>Alternatively, the packets could contain Ethernet-native applications, with the application information directly encapsulated within Ethernet without L4 Transport or IP headers.</t>

<t>Because the End Systems are not DetNet-aware, Edge Nodes are responsible for the imposition and disposition
of the required DetNet encapsulation. This functionality is
similar to that in pseudowire (PW) Provider Edge (PE) routers.</t>

<t>Relay Nodes are also strategically placed and used enhance the reliability
of delivery by enabling the DetNet-layer replication of packets so that multiple
copies, possibly over multiple paths. They also reduce the impact of
replication by the eliminating surplus copies of DetNet packets.
These functions may not be performed in End Systems, as they are not DetNet-aware.</t>

<t>Relay Nodes are aware of the needs of particular
DetNet flows and take care to process them in accordance with the
required performance needs.</t>

<t>Transit nodes are normal IP routers. They are unaware of DetNet flows per se, although they may be configured to provide congestion protection and delay control in order to meet the required DetNet service level agreement (SLA) via non-DetNet-specific means (IP traffic engineering, queuing mechanisms based on DiffServ markings, etc.).</t>

</section>
<section anchor="detnet-over-ip-encapsulation" title="DetNet over IP Encapsulation">

<t>To carry DetNet over IP the following is required:</t>

<t><list style="numbers">
  <t>A method of identifying the DetNet flow to the processing element.</t>
  <t>A method of carrying the DetNet sequence number.</t>
</list></t>

<t>These latter two pieces of information are already carried in the DetNet over MPLS Encapsulation, as shown in Figure 1, where the Control Word contains a 28-bit sequence number, and the S-Label is used to identify the particular flow.</t>

<figure><artwork><![CDATA[
  +---------------------------------+
  |                                 |
  |           DetNet Flow           |
  |         Payload  Packet         |
  |                                 |
  +---------------------------------+ <--\
  |       DetNet Control Word       |    |
  +---------------------------------+    +--> DetNet data plane
  |             S-Label             |    |    MPLS encapsulation
  +---------------------------------+ <--/
  |           T-Label(s)            |
  +---------------------------------+

  Figure 2: MPLS Encapsulation of DetNet
]]></artwork></figure>

<t>To simplify operations and implementations, rather than inventing a brand new encapsulation, the IP encapsulation can take advantage of the MPLS encapsulation. By using the specification of MPLS over UDP and IP in <xref target="RFC7510"/>, the T-Label(s) in Figure 2 can be replaced by UDP and IP, resulting in the following encapsulation:</t>

<figure><artwork><![CDATA[
  +---------------------------------+
  |                                 |
  |           DetNet Flow           |
  |         Payload  Packet         |
  |                                 |
  +---------------------------------+ <--\
  |       DetNet Control Word       |    |
  +---------------------------------+    +--> DetNet data plane
  |             S-Label             |    |    MPLS encapsulation
  +---------------------------------+ <--/
  |           UDP Header            |
  +---------------------------------+
  |           IP Header             |
  +---------------------------------+

  Figure 3: IP Encapsulation of DetNet
]]></artwork></figure>

<t>Where the UDP header is used as defined in Section 3 of <xref target="RFC7510"/>.</t>

<t>In ingress Edge Nodes, the encapsulation in Figure 3 will be imposed on Detnet Flow Payload Packets as received from DetNet End Systems, and the encapsulation will be removed in egress Edge Nodes as they transmit the Payload Packets to the End Systems.</t>

<t>Note that this encapsulation works equally well with IPv4 and IPv6.</t>

<t>This encapsulation can also be used in conjunction with segment routing as specified in <xref target="I-D.ietf-spring-segment-routing-mpls"/>. In this case, the T-Label(s) in Figure 2 should be retained, and at each hop, the top T-label is popped and mapped to a corresponding UDP/IP tunnel, resulting in the following encapsulation:</t>

<figure><artwork><![CDATA[
 +---------------------------------+
 |                                 |
 |           DetNet Flow           |
 |         Payload  Packet         |
 |                                 |
 +---------------------------------+ <--\
 |       DetNet Control Word       |    |
 +---------------------------------+    +--> DetNet data plane
 |           S-Label               |    |    MPLS encapsulation
 +---------------------------------+ <--/
 |           T-Label(s)            |
 +---------------------------------+
 |           UDP Header            |
 +---------------------------------+
 |           IP Header             |
 +---------------------------------+

 Figure 4: IP Encapsulation of DetNet with MPLS-SR
]]></artwork></figure>

<t>Again, the UDP header is used as defined in Section 3 of <xref target="RFC7510"/>.</t>

</section>
<section anchor="security-considerations" title="Security considerations">

<t>The security considerations of DetNet in general are discussed in
<xref target="I-D.ietf-detnet-security"/>.  Other
security considerations will be added in a future version of this
draft.</t>

</section>
<section anchor="iana-considerations" title="IANA considerations">

<t>This document makes no IANA requests.</t>

</section>
<section anchor="acknowledgements" title="Acknowledgements">

</section>


  </middle>

  <back>

    <references title='Normative References'>





<reference anchor="I-D.ietf-detnet-dp-sol">
<front>
<title>DetNet Data Plane Encapsulation</title>

<author initials='J' surname='Korhonen' fullname='Jouni Korhonen'>
    <organization />
</author>

<author initials='L' surname='Andersson' fullname='Loa Andersson'>
    <organization />
</author>

<author initials='Y' surname='Jiang' fullname='Yuanlong Jiang'>
    <organization />
</author>

<author initials='N' surname='Finn' fullname='Norman Finn'>
    <organization />
</author>

<author initials='B' surname='Varga' fullname='Balazs Varga'>
    <organization />
</author>

<author initials='J' surname='Farkas' fullname='Janos Farkas'>
    <organization />
</author>

<author initials='C' surname='Bernardos' fullname='Carlos Bernardos'>
    <organization />
</author>

<author initials='T' surname='Mizrahi' fullname='Tal Mizrahi'>
    <organization />
</author>

<author initials='L' surname='Berger' fullname='Lou Berger'>
    <organization />
</author>

<date month='January' day='29' year='2018' />

<abstract><t>This document specifies Deterministic Networking data plane encapsulation solutions.  The described data plane solutions can be applied over either IP or MPLS Packet Switched Networks.</t></abstract>

</front>

<seriesInfo name='Internet-Draft' value='draft-ietf-detnet-dp-sol-01' />
<format type='TXT'
        target='http://www.ietf.org/internet-drafts/draft-ietf-detnet-dp-sol-01.txt' />
</reference>



<reference anchor="I-D.ietf-spring-segment-routing-mpls">
<front>
<title>Segment Routing with MPLS data plane</title>

<author initials='A' surname='Bashandy' fullname='Ahmed Bashandy'>
    <organization />
</author>

<author initials='C' surname='Filsfils' fullname='Clarence Filsfils'>
    <organization />
</author>

<author initials='S' surname='Previdi' fullname='Stefano Previdi'>
    <organization />
</author>

<author initials='B' surname='Decraene' fullname='Bruno Decraene'>
    <organization />
</author>

<author initials='S' surname='Litkowski' fullname='Stephane Litkowski'>
    <organization />
</author>

<author initials='R' surname='Shakir' fullname='Rob Shakir'>
    <organization />
</author>

<date month='February' day='23' year='2018' />

<abstract><t>Segment Routing (SR) leverages the source routing paradigm.  A node steers a packet through a controlled set of instructions, called segments, by prepending the packet with an SR header.  In the MPLS dataplane, the SR header is instantiated through a label stack. This document specifies the forwarding behavior to allow instantiating SR over the MPLS dataplane.</t></abstract>

</front>

<seriesInfo name='Internet-Draft' value='draft-ietf-spring-segment-routing-mpls-12' />
<format type='TXT'
        target='http://www.ietf.org/internet-drafts/draft-ietf-spring-segment-routing-mpls-12.txt' />
</reference>



<reference  anchor="RFC2119" target='https://www.rfc-editor.org/info/rfc2119'>
<front>
<title>Key words for use in RFCs to Indicate Requirement Levels</title>
<author initials='S.' surname='Bradner' fullname='S. Bradner'><organization /></author>
<date year='1997' month='March' />
<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="RFC7510" target='https://www.rfc-editor.org/info/rfc7510'>
<front>
<title>Encapsulating MPLS in UDP</title>
<author initials='X.' surname='Xu' fullname='X. Xu'><organization /></author>
<author initials='N.' surname='Sheth' fullname='N. Sheth'><organization /></author>
<author initials='L.' surname='Yong' fullname='L. Yong'><organization /></author>
<author initials='R.' surname='Callon' fullname='R. Callon'><organization /></author>
<author initials='D.' surname='Black' fullname='D. Black'><organization /></author>
<date year='2015' month='April' />
<abstract><t>This document specifies an IP-based encapsulation for MPLS, called MPLS-in-UDP for situations where UDP (User Datagram Protocol) encapsulation is preferred to direct use of MPLS, e.g., to enable UDP-based ECMP (Equal-Cost Multipath) or link aggregation.  The MPLS- in-UDP encapsulation technology must only be deployed within a single network (with a single network operator) or networks of an adjacent set of cooperating network operators where traffic is managed to avoid congestion, rather than over the Internet where congestion control is required.  Usage restrictions apply to MPLS-in-UDP usage for traffic that is not congestion controlled and to UDP zero checksum usage with IPv6.</t></abstract>
</front>
<seriesInfo name='RFC' value='7510'/>
<seriesInfo name='DOI' value='10.17487/RFC7510'/>
</reference>




    </references>

    <references title='Informative References'>





<reference anchor="I-D.ietf-detnet-architecture">
<front>
<title>Deterministic Networking Architecture</title>

<author initials='N' surname='Finn' fullname='Norman Finn'>
    <organization />
</author>

<author initials='P' surname='Thubert' fullname='Pascal Thubert'>
    <organization />
</author>

<author initials='B' surname='Varga' fullname='Balazs Varga'>
    <organization />
</author>

<author initials='J' surname='Farkas' fullname='Janos Farkas'>
    <organization />
</author>

<date month='October' day='30' year='2017' />

<abstract><t>Deterministic Networking (DetNet) provides a capability to carry specified unicast or multicast data flows for real-time applications with extremely low data loss rates and bounded latency.  Techniques used include: 1) reserving data plane resources for individual (or aggregated) DetNet flows in some or all of the intermediate nodes (e.g. bridges or routers) along the path of the flow; 2) providing explicit routes for DetNet flows that do not rapidly change with the network topology; and 3) distributing data from DetNet flow packets over time and/or space to ensure delivery of each packet's data' in spite of the loss of a path.  The capabilities can be managed by configuration, or by manual or automatic network management.</t></abstract>

</front>

<seriesInfo name='Internet-Draft' value='draft-ietf-detnet-architecture-04' />
<format type='TXT'
        target='http://www.ietf.org/internet-drafts/draft-ietf-detnet-architecture-04.txt' />
</reference>



<reference anchor="I-D.ietf-detnet-security">
<front>
<title>Deterministic Networking (DetNet) Security Considerations</title>

<author initials='T' surname='Mizrahi' fullname='Tal Mizrahi'>
    <organization />
</author>

<author initials='E' surname='Grossman' fullname='Ethan Grossman'>
    <organization />
</author>

<author initials='A' surname='Hacker' fullname='Andrew Hacker'>
    <organization />
</author>

<author initials='S' surname='Das' fullname='Subir Das'>
    <organization />
</author>

<author initials='J' surname='Dowdell' fullname='John Dowdell'>
    <organization />
</author>

<author initials='H' surname='Austad' fullname='Henrik Austad'>
    <organization />
</author>

<author initials='K' surname='Stanton' fullname='Kevin Stanton'>
    <organization />
</author>

<author initials='N' surname='Finn' fullname='Norman Finn'>
    <organization />
</author>

<date month='October' day='30' year='2017' />

<abstract><t>A deterministic network is one that can carry data flows for real- time applications with extremely low data loss rates and bounded latency.  Deterministic networks have been successfully deployed in real-time operational technology (OT) applications for some years (for example [ARINC664P7]).  However, such networks are typically isolated from external access, and thus the security threat from external attackers is low.  IETF Deterministic Networking (DetNet) specifies a set of technologies that enable creation of deterministic networks on IP-based networks of potentially wide area (on the scale of a corporate network) potentially bringing the OT network into contact with Information Technology (IT) traffic and security threats that lie outside of a tightly controlled and bounded area (such as the internals of an aircraft).  These DetNet technologies have not previously been deployed together on a wide area IP-based network, and thus can present security considerations that may be new to IP- based wide area network designers.  This draft, intended for use by DetNet network designers, provides insight into these security considerations.  In addition, this draft collects all security- related statements from the various DetNet drafts (Architecture, Use Cases, etc) into a single location Section 7.</t></abstract>

</front>

<seriesInfo name='Internet-Draft' value='draft-ietf-detnet-security-01' />
<format type='TXT'
        target='http://www.ietf.org/internet-drafts/draft-ietf-detnet-security-01.txt' />
</reference>



<reference  anchor="RFC3985" target='https://www.rfc-editor.org/info/rfc3985'>
<front>
<title>Pseudo Wire Emulation Edge-to-Edge (PWE3) Architecture</title>
<author initials='S.' surname='Bryant' fullname='S. Bryant' role='editor'><organization /></author>
<author initials='P.' surname='Pate' fullname='P. Pate' role='editor'><organization /></author>
<date year='2005' month='March' />
<abstract><t>This document describes an architecture for Pseudo Wire Emulation Edge-to-Edge (PWE3).  It discusses the emulation of services such as Frame Relay, ATM, Ethernet, TDM, and SONET/SDH over packet switched networks (PSNs) using IP or MPLS.  It presents the architectural framework for pseudo wires (PWs), defines terminology, and specifies the various protocol elements and their functions.  This memo provides information for the Internet community.</t></abstract>
</front>
<seriesInfo name='RFC' value='3985'/>
<seriesInfo name='DOI' value='10.17487/RFC3985'/>
</reference>



<reference  anchor="RFC4385" target='https://www.rfc-editor.org/info/rfc4385'>
<front>
<title>Pseudowire Emulation Edge-to-Edge (PWE3) Control Word for Use over an MPLS PSN</title>
<author initials='S.' surname='Bryant' fullname='S. Bryant'><organization /></author>
<author initials='G.' surname='Swallow' fullname='G. Swallow'><organization /></author>
<author initials='L.' surname='Martini' fullname='L. Martini'><organization /></author>
<author initials='D.' surname='McPherson' fullname='D. McPherson'><organization /></author>
<date year='2006' month='February' />
<abstract><t>This document describes the preferred design of a Pseudowire Emulation Edge-to-Edge (PWE3) Control Word to be used over an MPLS packet switched network, and the Pseudowire Associated Channel Header.  The design of these fields is chosen so that an MPLS Label Switching Router performing MPLS payload inspection will not confuse a PWE3 payload with an IP payload.  [STANDARDS-TRACK]</t></abstract>
</front>
<seriesInfo name='RFC' value='4385'/>
<seriesInfo name='DOI' value='10.17487/RFC4385'/>
</reference>




    </references>



  </back>

<!-- ##markdown-source:
H4sIAOwfnVoAA+1a6W4cNxL+L0DvQCh/JHh6JB/JOoMgyNiSHQG61pJXu0iC
BaebM8N1XyHZUiaxH2afZV9svyqS3T2HFMnJnwV2Eo/6IOti1VdV5CRJsr2V
VpkuZyPRuGnycntre8tpl6uROFTuTDlxfCGOylTWtsml01W5vSUnE6NuegO2
t7IqLWWBSZmRU5cUMtc2yZQrlUt0nWR1cnCwvXU7ayddV+YDuIq3pmpqyCCd
mlVmMRLWZSSDdbLM/inzqgTRhbLbW7UeiR9clQ6ErYwzampxtSj8RVoVhSqd
/YnmysbNKzPa3hIioS/+6NKOxHgoTkm09qkXelxmRt2Kt6tvKwOBv2/krdLi
SqXzssqrmVbdAFVInY+EnLHC383odghZNrC+HIpXZiFLt8L70qlbadzqy4ey
tn76cMLT75XgdChez1W5wv9UpvPl5w9lXWDmMMXM7+Y8+A62r4bib9LM5Apf
8Urm//n3r3blJTM/Mjq1tipXOU5kLn+1Qzm8oTnfqTDMM97eKitTwEVv1MhP
PE4Oh1rBq4Mjwgttla++tLWBIyZWzciDEvijo/uizm0Y+u7N62dPn37d3f3l
y6cHI+Koy+nv8JQmnWunUteYu4ZYlTZGu0VH//nXL7/s7l4857vtrSRJhJxY
Z2Tq6P5qrq1A5DUkuLC1SvUU60QhpkyhS22dTgWi7TYEWyadFHUuS7W9VdXK
cDyL6kYZIUsK9NKPHYpjJ0Ablimk0flCSF2oTEgK9psXAzFpnLitmjwTNFzc
ajenN18JacWtynOhp0KKpiR5MsRr3jAnEldZbVQ2XJcf1xKvjb5he3rKU1MV
AVPWVzI5eDoQrhKy4aWD7wijoF6qhJvjn/rFCZjW4B1USKvSSV1CHl0K2Jwl
+nL4DP+RMNdzhUkGMyEI6d5MENJz0poEYzxKGI+Y8IC4WWVuYG+J0JBiWqUy
F3WlIQmEAi7p0gsCw5LasxJWBrjZZmLVz42XyqhCmRm4sA3v0dTbB76Gtd3e
gtsx6cOjq7OjK3H9lnXwLlLoLMsV3X0hjktnqqxJPXA/3OS//bY5eD59+l82
Vkg93lh3RsmuH7fniZDYmj0K3p8iTCZKVNOpghOLyYJ0CUFDegQO07y6tUMR
b2tT3WgoRUJY5d8KmIXUgVa4RXaT6QcMzStrBeKSDFWSNW1DjAr5iy6aQiiY
1VUJ/sBIOZbMYDpGl+kCOr1VJWI6B0ymH2bAMSKAf3D8VNXOQuwoUdBjymM0
PGN9vfvAFVb9Lrwh26p+icBsewAzRYGwZO2ys3YPfQieEoanITFTQtYwHeUn
8C0qaAxTgB7x61MXF1Y1WXUNYLFi9+J6j4liaZjqhbfsJXwmJQ8NK42Bl2d7
cPSAt58+8SWBbbgklA+aezicSNsJsGM1UoQHOJZtR2Tapo2lMVlDOaXvdAhE
xFkhTpWi9CLmKmdST1+IN2piGomVfHbw9KX48Ye5c/Vof58jrJbZ0FVVbnlt
hpQdvz44ONiv98sKTuK9X3vaCc2Py3fw/MefeqLL3FbL8p9enFyurBpcNDV6
4hHSR5cvKyJRyokIMrHLcY+gRRSUFBsVeVNTYwGZAR7xdOZ8g9QtJ7naCz7U
mgR5rLQ1ajm48AJOMG1KximUUm7h462NHPjwTFmPYnjoAnxTZPdjjhkiZihZ
eaGgic8IuJBhLFUKmdrg0lkFVjBsL2tkHTKBcJVqVpFyialyn0tbwe0AadWI
8+iaqEvHmfd5/2DAgXEqacFKSWbaPR+f7gEpsEq8RCQBidcXwQfaguw1nSJ4
5iCSkw9h7eREw1oUhAYoSZmV9A7YQKV9NJvoWY2ECKjRarJmSVgfSjNMblis
obhiLJMkHKClkAtv7TRvMu9A04agA3LdaEvGoEBlv2HX4JSAURXnkcAkLoQd
+ux1xZBB5eeCH/gnVjTWs3D91VtfTgzz4GRRcQrXEaMsdU+GExe5QqgA+gPs
txRjJmGv0LzGwyCZGHNXpP3K/54wsj/4D4uD3OvIvEtUgw3feb9gs2Ltylkj
ZypG4ge1oKSfWbFz+v7yamfg/4qzc75+d/TX98fvjg7p+vL78clJe+FHbG/h
7vz9SRhAV93U1+enp0dnh3726fgfO977d84vro7Pz8YnO3EFuXv0Ckmj2rjF
etVGOV9TLEETozNV5AGdv4j+c97lkoDyUdENaN1mwwEz2ITdAVhF4UF7QPCS
SmOIynrVTG/tvLotScY3ekbe/3Tk6zIq5YOQ+BxlMxU6myuKK01P3ylEVnja
G9BiFj+HAS8XFldnUCKOaK83PuymRUGeJPR5IvofGgLL88hQ8ax+wjRP4+O4
rvPy4zfDR32+DdNW5PAX/ubwTLwBAC0923QT5RBXl2f4xv9R7o/fhLHf9p4l
Se+mnbZBjie97+W7lQErchye/b12RJn/hO/ji/7d+oA4rZVjGCgPmU38Xr5b
GRCntc3yaOlv/B6d6PJDvOPrpQH42xJ40tlaiP1w82Pfa570BnQjWgLk1zCv
/3y8bCbibP/645pDxc9HGkwj+gS8iPT5MdDfv5NAOyJ6uP+0MSguu+g/pehn
sIwBeVRSeZL1IQNlU8guU6YBBOOF2vEQ5q/MKowTHO8EolcxX4Yp7Ak7XJ+U
S9P8LKBINyO2J144Dl2nkPYsQyQeGJUq6td802A9FnXFJidnap1qIgfNQnPh
FjX1FYabLKJzRMkX6MUMz1Af+PyifYW4arSBuJ3rXPWr2tgcQa2uNRnwiL7g
xJJqGj8rkbdsO2piKn4eyoZItd1VoVK1ImraRB3mSqJhRXP1TpLwnle0wwQr
qFS5zp/AjZ4RrBIw+oIF9tBoQ/3egI05FACFp36/ohNkIE5edEskdm2DtgR5
4+r1BVUy7w8v9gYw62DJrlHagS+fCu1cmzk4QnJyckwHucleEjuTzWqsa8HL
Ns6Ro0ru3/PFsjlS3qEJ+x6tUIkf3FcUAnJH7ebqLv2RIOF1VI52PUNoxHu0
+b5q3LKxoCAcLq4cCf1KpRIF0YMcZdBfNskVJchivRC0bQUEV62sbqtbZPN4
j5J8ykPaAjl42VLvQyFD0b7UglBpgroB7Yvxfuhjo+Zu8xa0fLN54ZsU4+Xc
vTjaE7SJGHX1eb0Tn+t87gjULLgfdyi+WefSVpVz7g682Ln2Vf6CVWn7/gkt
BZBrudFMfC9F+2BxFTEpeoQNWhRN7nRNm0RpVaN7GAiYiyy68N4Z32Oim1vG
k4UXHAZsgmSwuUwdd/d9dpOF3xDIYTlyNYhnG1PnDTkkMevtQwS5fLtve50U
xyd5AkpBtFPkhr7263kL122OJdvgNpttz8gTHKJUKrPeOsbpFJ5gWtgNPRBF
nPygqOjjwhRNVKoscy24o0xTVM+8VjGAyBjB0YLg/JqZ+ZYzVHxlKxXvW+cU
I9FvgsHxrilbmZdEA22gL0yQU8DN5t4QoQ1DyPu8lQWhyT/F3c1gxmaKrSB1
ZYb8GXOp8t0YPRH5cwXcEXJmFLcYYvfyZLwnkNugVZmEBQlbRSnIQXexC01j
M6vKGfprZbi8/rlRDflLoVIEgLZFb8/lUE+nVMBBR944wvIrlw73ljsA9t71
EytYveLKfbE6kHSbVjlsSox110dz4f50KMaQBibOaAVgxdKhFV/Z26EVCYkq
egiNUDmbBAI+WybDgqzQ8Juc5ChNMUF/HRoXxETOu5gCqUEgelIfP31k9qBi
AK+LtjsJKbyvLG/4LNmFA2itY6E0r4wP8dfBJa7hEDGR0Kbos5fJRK8JPWhT
1GVyIifwCx16dRgn2i5kqBhxbLxh1yT1a/27Pm2pe3dJ2ZaWm4YGq3Cbce/Q
C7nIK5mJuId4L9XfEeABaolvekV0JB2EXVqJ3ohH0ffDvm23W3rHQZv0iau4
pE/7tb6B+EhV9zdxvfI8d+3e51qx86Tg0c9GG3y/A1Tve8CHsEWw6PaWfQag
xxzJsVYyMhx+SAqcG/JrBLMUE0PDS3W7bJZBPNdY3m2lPXhOLjK7kSA+axPT
umWH4tUCkRQxI+JpqwnP4ChHIcpCg13cKfH72F6Knnm7kH8WzwPC6RkdbPQI
DajiooKAALJcQcwlMUf/j+L/RzF9yHm+53r/c624ierxJqJ/DBuej9aqhVVk
uG6zIWnlu5g2sfHW5DSeKl+Gmuo50Vg7QyKwQJ2E8rFraAYbDs+6wHyOqjLP
eTuU+ptQCPH2sPf76NoXob6XNu4NZP4cd30XoUvSy1wjJ6OK6saro1albQvu
2M4ynVUhQiXU47myv8AbKyvc0ffi2c8N90P8E4L4o4IXAYZuvupObNaR1B9w
qfZoAMXKv0Iz4SmF33eI8PsOLn3CCWbYVH7IL0JoOz5uDaWSCvB7UBWlFTXg
bFT/0wNvfJhA0anmvKr9fFfVoJHHkqmu6jq0g4XkS/qRA1QyvvWln2uRM+5T
/dqUJW3NPB6iHx6ED8fHh+Pzw+H54dwfCc6PxOY/A5r7umzC5Qch8yOB+eHV
1ed5xP1Y/3k070f6xwB9CMYX9+G8Bwiyd3L5zoP+eIZ4HfwJqP8Fveafd/lN
xiyWlvFkym5+3ZMOLGbhlx3U6nUnVZt/uBEJElSJc6pUt7fuYhJBX2bh0FbG
Y1vUkjYYKZzR0altUOl4fDbeqE7/wLNAbUun6X40tdXKtie7Ypx+KKvbXCG3
8NHk9tZ/AWbGy3SMKgAA

-->

</rfc>

