<?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.4.7 -->

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

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

<rfc ipr="trust200902" docName="draft-km-industrial-internet-requirements-00" category="info">

  <front>
    <title abbrev="industrial-network-req">Requirements and Scenarios for Industry Internet Addressing</title>

    <author initials="K." surname="Makhijani" fullname="Kiran Makhijani">
      <organization>Futurewei</organization>
      <address>
        <email>kiran.ietf@gmail.com</email>
      </address>
    </author>
    <author initials="L." surname="Dong" fullname="Lijun Dong">
      <organization>Futurewei</organization>
      <address>
        <postal>
          <street>Central Expy</street>
          <city>Santa Clara, CA 95050</city>
          <country>United States of America</country>
        </postal>
        <email>lijun.dong@futurewei.com</email>
      </address>
    </author>

    <date year="2021" month="June" day="10"/>

    <area>INTAREA</area>
    <workgroup>Independent Submission</workgroup>
    <keyword>Internet-Draft</keyword>

    <abstract>


<t>Industry Control Networks host a diverse set of non-internet protocols for different purposes. Even though they operate in a controlled environment, one end of industrial control applications run over internet technologies (IT) and another over operational technology (OT) protocols.  This memo  discusses the challenges and requirements relating to converegence of OT and IT networks. 
 One particular problem in convergence is figuring out reachability between the these networks.</t>



    </abstract>


  </front>

  <middle>


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

<t>An industry control network interconnects devices used to operate, control and monitor  physical equipment in industrial environments. These networks are increasingly becoming complex as the emphasis on convergence of OT/IT grows to improve the automation. On one side of Industrial internet are the inventory management, supply chain and simulation software and the other side are the control devices operating on machines. Operational Technologies (OT) networks are more often tied to set of non-internet protocols such as 
Modbus, Profibus, CANbus, Profinet, etc. There are more than 100 different protocols each with it’s own packet format and are used  in the industry.</t>

<t>It is expected that integration between the IT and OT will provide numerous benefits in terms of improved productivity, efficiency of operations by providing end to end visibility and control. Industry control applications also expect to operate at cloud scale by virtualization of several modules (especially PLCs) leading to new set of network requirements.</t>

<t>One aspect of industry control is the delivery of data associated with the Real-time, deterministic and reliability characteristics over local-area and wide-area networks. This type of inter-operability functionality and study is already covered in DETNET working group. The other aspect is rachability and interconnection keeping heterogenity of communication interfaces and a variety of services in mind. This doument focuses on the latter part only.</t>

<t>OT networks have been traditionally separate from the IT networks. It allowed OT network experts to manage and control proceses without much dependency on changes in the external networks. This is an important to consideration when dealing with the industry control networks to maintain them in a controlled environment leveraging the limited-domain networks <xref target="LDN"/> concept for an independent network control.</t>

<t>The purpose of this document is to discuss the reachability and interconnection characteristics, challenges and new requirements emerging from large-scale integration of IT and OT.</t>

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

<t><list style="symbols">
  <t>Industrial Control Networks:
The indutrial control networks are interconnection of equipments used for the operation, control or monitoring of machines in the industry environment. It involves different level of communications - between fieldbus devices, digital controllers and software applications</t>
  <t>Industry Automation: Mechansims that enable  machine to machine communication by use of technologies that enable automatic control and operation of industrial devices and  processes leading to minimizing human intervention.</t>
  <t>Human Machine Interface: An interface between the operator and the machine. The communication interface relays I/O data back and forth between an oeprator’s terminal anf HMI software to control and monitor equipment.</t>
</list></t>


<section anchor="acronymns" title="Acronymns">
<t><list style="symbols">
  <t>HMI: Human Machine Interface</t>
</list></t>

</section>
</section>
<section anchor="arch" title="Industrial Network Reference Architecture">

<t>In the scope of this document the following reference  industrial network will be used to provide structure to the discussion. In the Fig. <xref target="indusarch"/> below, a hierarchy of communications is shown. At the lowest level, PLCs operate and control field devices; above that Human Machine Interface
 (HMI) interconnects with different PLCs to program and control underlying field devices. HMI itself, sends data up to applications for consumption in that industry vertical.</t>

<figure title="Hierarchy of Functions Industrial Control Networks" anchor="indusarch"><artwork><![CDATA[
      +-+-+-+-+-+-+
   ^  | Data Apps |....             External business logic network
   :  +-+-+-+-+-+-+   :
   :        |         : 
   v  +-+-+-+-+-+-+  +-+-+-+-+--+
      | vendor A  |  |vendor B  |     Interconnection of 
      | controller|  |controller|     controllers (system integrators)
   ^  +-+-+-+-+-+-+  +-+-+-+-+-+    
   :       |         |          
   :   +-+-+-+-+  +-+-++-+
   :   | Net X |  | Net Y|
   v   | PLCs  |  | PLCs |--+        device-controllers
   ^   +-+-+-+-+  +-+-+--+  |
   :      |        |        |
   :   +-+-+    +-+-+    +-+-+
   v   |   |    |   |    |   |   Field level devices 
       +-+-+    +-+-+    +-+-+
]]></artwork></figure>

<t>Unlike commercial networks that uniformly run IP protocols, the communication links run different protocols at along the different level of the hierarchy. One of the key requirement from new industrial applications is the integration of different types of communication protocols including Modbus, Profinet, Profibus, ControlNet, CANOpen etc.</t>

<t>A vertically integration system involves a network between the external business applications and higher controllers (for e.g. SCADA, HMI, or system integrators) is IP based. The second level of networks between  the controllers can be either IP or non-IP (Profibus, BACNet, etc.). The lowest field-level networks between industrial controllers and field-level may be any of the fieldbus or device control protocols (More details of the industry networks can be found in  <xref target="SURV"/>).</t>

<section anchor="communication-patterns" title="Communication Patterns">

<t>The following communication patterns are commonly observed:</t>

<t><list style="symbols">
  <t>controller to controller: A communication between multi-vendor controller maybe required by system integrators to work in complex systems.</t>
  <t>controller to field level devices:  This is a fieldbus communication between device such as I/O modules, motors, controllers. This communication represent.</t>
  <t>Device to device: allows direct communication between wired industrial devices and wireless devices to enhance automation use cases. For an exmaple, use of camera to visually monitor and detect anamolies in other devices.</t>
  <t>controller to compute: vertical communication between a controller and compute integrates IP-based technologies with non-IP since OT product systems and solutions are not connected with IP based networks.</t>
</list></t>

<t>A certain level of inter-operability is required to exchange data between the above endpoints from different vendors. One of the challange is that Ethernet (which unifies IT standards) that’s not always possible in Industry networks.</t>

</section>
<section anchor="industry-control-network-nuances-current-state" title="Industry Control Network Nuances (current state)">

<t>The Industry control networks are engineered for the idustry verticals they belong to and depict unique properties as below:</t>


<t><list style="symbols">
  <t>location bound:  The Control Device’s location or the network they are
   attached to is predetermined and changes rarely. However, the network resources may 
   not get efficiently utilized to avoid contention between them.</t>
  <t>security by separation: Typically, security is enhanced by keeping IT/OTnetworks separate. The 
operators control how data  goes in and out of a site through firewalls and policies.</t>
  <t>data growth: Even though the size of network remains the same, data generated is much higher. For example, cameras installed for visual inspection to determine the quality of manufactured product generates a high bandwidth demand.</t>
  <t>Wired device constraints: A bulk of machines are over wired network, their constraints vary from LPWAN  and IoT devices which is an active area of standardization work. device lifetime, or power-requirements are  not typical constraints. Instead direct process control mechanisms are more important.</t>
  <t>Real-time behavior: The control devices require realtime as well as deterministic behavior between a controller (such as an HMI station) to the equipment. The DetNet working group covers several aspects.</t>
</list></t>

<t>The goal of the document is not to reinvent the Industry control infrastructure. See section <xref target="relevance"/> on related standards work. It is meant to exclude the already covered by other WGs.</t>

<t>Since a device connects to network through its address, the document explores different address specific nuances in control devies - such as management, device discovery and integration requirements. This document concerns with the identification of and role networks, specifically from the organization of industry control devices.</t>

<t>The goal of this document is to outline some of the challenges and improvement of connectivity aspects of Industry control networks.</t>

</section>
</section>
<section anchor="problem" title="Problem Statement">

<t>In industrial networks, a good number of devices still communicate over a serial or field bus (although Ethernet is being gradually adopted). The operations on these devices are performed by writing provide direct access to operation-control. i.e what operation to perform is embedded in the type of interface itself. For instance, Profibus, Modbus networks are implicitly latency sensitive and short control-command based.</t>

<figure><artwork><![CDATA[
  ModBus
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   | address | Function  code  | data|
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

  CANBus

   +-+-+-+-+-+-+-+-+-+-+--+-+-+
   |   message id  |    data  |
   +-+-+-+-+-+-+-+-+-+-+-++-+-+
   Profibus - todo.
]]></artwork></figure>

<t>Since they are localized in an area such as factory floor or a site, such networks have evolved independently and are seperated from the IT applications. The emerging trend requires a seamless integration with intelligent software, sophisticated compute platforms and other operational aspects as highlighted below:</t>

<section anchor="heterogenity" title="Heterogenity">

<t>A typical industry control network has devices of different communication interfaces such as Fieldbus (PROFIBUS, Modbus, and HART), Ethernet (generic Ethernet/IP, PROFINET, and Modbus-TCP), and also wireless (Bluetooth, Wireless HART, and IoT). These interfaces vary at the physical and link layers and because they integrate with their own application technologies providing interoperability between these devices remains a challenge. This also makes difficult to adopt to modern integration technologies.</t>

<t>Fieldbus client-server architecture is widely deployed. It delivers commands  deterministically from a controller to the device and vice-a-versa. Interfaces of this kind have typically shorter addresses (upto 256 devices on a single bus in Modbus).</t>

<t>Some of the servers also behave as protocol gateways and interconnect different type of protocols. For example when a modbus device is being controlled by a profinet server, an gateway function will translate modbus data or encapsulate it over IP (if the controller supports it).</t>

<t>In a Gateway-centric approach, gateways are in charge of protocol translations between the devices with different interfaces. This requires packing and unpacking of data in the source and destination formats at the attached gateways. 
 Note: As an example, a Modbus device does not know whether to send command to Profibus PLC or Modbus PLC. The gateway device attaches to performs the translation. This is even worse with encapsulations, where the entire frame is carried over IP.</t>

<t>This is not ideal for latency sensitive applications. Although hardware wise, gateways need to be equipped with all the interface, it is more efficient to only perform data link conversion.</t>


</section>
<section anchor="automation-impact" title="Automation Impact">
<t>Automation of processes in industry relies on control sophisticated technologies such as machine learning, big data, etc. with minimal human intervention. Automation  needs to support scale, reliability and resiliance at large-scale.</t>

<section anchor="scale" title="Scale">

<t>Automation control at small scale applications with well defined task has been possible. In order to improve production, and eliminate stoppages and minimizing human intervention.</t>

<t>When the number or density of devices, and processes increase there is a need to schedule, route, and  coordinate over multiple control environments.</t>

</section>
<section anchor="stretch-control-fabric-to-edge-and-cloud" title="Stretch Control Fabric to Edge and Cloud">

<t>The industry control networks can be extended to cloud or edge compute platforms. Since these networks are not equipped with compute intensive servers. Now extending the communication to the edge and cloud nodes increases the distance requiring traditional L2 networks to be adopted to L3 network designs.</t>

<t>Design decisions will require to choose different transit strategies (this maybe layer 1, 2, 3 technologies or even network slices). It also influence the security policies.</t>

</section>
<section anchor="reliability" title="Reliability">
<t>Production efficiency is inversely related to number of defects in a process. System reliability is determined through measurements of its instantaneous state.</t>

<t>Automation processes  need to ensure that system is performing in an expected state and is capable of reporting anamolies fast and accurately (i.e. packet drops or jitter leading to poor quality product).</t>

</section>
<section anchor="resilience" title="Resilience">

<t>TBD.</t>

</section>
</section>
<section anchor="otit-convergence" title="OT/IT Convergence">
<t>Most of the factory floors are not equipped with IT servers to perform compute intensive tasks. Yet an IP-based device need to connect with non-IP interface to control those devices.</t>

<t>Often real-time response is necessary for example, in closed-loop control systems direct communication is desired to avoid any additional packet processing delay or overheades at the source and destination gateways, equipping IP to all OT devices and abandoning the existing investment and depolyment could result in the following obvious problems.</t>


<t><list style="symbols">
  <t>Many of the standard IP based protocols maybe too much overhead for OT devices.</t>
  <t>Cannot preserve communication characteristics of devices (different device addressing scheme, realtime, IRT, message identifiers, Bus-like properties).</t>
  <t>It relies heavily on hierarchy network stack (network layer, transport layer, application), where as OT devices do not have any, they generally operate at data link layer or below.</t>
</list></t>

</section>
<section anchor="data-oriented-networking" title="Data oriented networking">
<t>Industry verticals keep data and control on the manufacturing floor, on a closed system. There is no easy way to forward this data to enterprise level software. On premise micro data centers or edge computing are new infrastructure pieces that wil impact the design of current industrial networks.</t>

</section>
<section anchor="virtualization" title="Virtualization">
<t>Traditional Industry control infrastructure is not virtualized. Virtualization will enable deployment of new functionality in a flexible manner.</t>

<t><list style="symbols">
  <t>Virtual PLCs are considered an important component functionality customization of digital-twin realization.</t>
  <t>virtualization enables edge and cloud native computing by moving and instantiating workflows at different locations.</t>
</list></t>

<t>Implications that PLCs are no longer one-hop away.</t>

</section>
</section>
<section anchor="reqs" title="Address Space Requirements">

<section anchor="short-device-addressing" title="Short Device Addressing">
<t>Shorter addresses are inherent to industry control systems to provide implicit determinism.</t>

<t>Note: The motivation for short address is to preseve the legacy attributes of fieldbus control devices. It is not related low-power or resource constraints.</t>

<t>A large volume of the messages are of sizes shorter than the size of IP headers (v4, v6) themselves. The header tax will be very high over industry control networks.</t>

</section>
<section anchor="meaningful-addresses" title="Meaningful Addresses">

<t>The industry control floors are built bottom-up. The devices are carefully wired and connected to controllers. In a hierarchical network design, a particular type of machine can be reached in a structured manner by adding subnet or location to the address structures.</t>

</section>
<section anchor="device-name-based-addresses" title="Device name based  Addresses">
<t>HMI might require human readable address that is  undertandable to human operators or application end users. For example, a device address could be associated with its location, type of applications, attached objects etc. The network needs to support the resolution and routing based on such device addresses, which is more user friendly. On the other hand, grouping devices based on their addresses shall be easily implemented to enable group operation and communication.</t>

</section>
<section anchor="adoption-of-lean-network-layer" title="Adoption of Lean Network Layer">
<t>Challenge of Industrial network device address is that it  communicates to a physical device address. Traditionally, in a limited environment there was no need for network layer or expressing network specific service, access control.</t>

<t><list style="symbols">
  <t>If a sensor is broken, it will require reprogramming of controller and re-aligning with the new address. The benefit of network layer, removes this restriction.</t>
  <t>Note that, using IP stack is not suitable because these devices perform specific functions and any overhead in transport or large addressing can add to processing delays.</t>
  <t>Several other IP suite protocols such as device discovery should be revisited.</t>
</list></t>

</section>
<section anchor="multi-semantic-behavior" title="Multi-semantic behavior">
<t>OT networks, at least at site level are organized at much smaller scale than typical IP-capable networks. There is in turn a fixed hierarchy of networks w.r.t. location in a plant.</t>

</section>
<section anchor="interoperability-with-ip-world-machines" title="Interoperability with IP-world machines">

<t>To develop further on different type of address format support. From smaller address of legacy devices to IT based applications with IP address.</t>

<figure><artwork><![CDATA[
(OT-Address )--->(Industry Control)--->(IP-Address) 
(control dev)    (   network      )    (application)
]]></artwork></figure>

<t>Preferably allow OT devices to understand IP-addresses for the servers they connect to.</t>

</section>
</section>
<section anchor="relevance" title="Relationship with  Activities in IETF">

<section anchor="deterministic-networks-detnet-wg" title="Deterministic Networks (DetNet WG)">
<t>The Deterministic Networking (DetNet) <xref target="DETNET-ARCH"/> is working on using IP for long-range connectivity with  bounded latency in industry control networks . Its data plane <xref target="DETNET-DP"/> takes care of forwarding aspects and most close to Industry control networks but the focus is on the controlled latency, low packet loss &amp; delay variation, and high reliability functions. Not dealing with interconnection of devices.</t>

<t>In layer 2 domain, similar functionalty is convered by TSN Ethernet <xref target="IEEE802.1TSNTG"/>.</t>

</section>
<section anchor="iot-ops" title="IoT OPS">
<t>IoT operations group discusses device security, privacy, and bootstrapping and device onboarding concepts. Among the device provisioning one of the object is network identifier. We understand that the IoT OPs does not exclude evaluation of industry IoT or control devices requirements.
Given the specific functions described above it maybe necessary to configure more than an identifier, i.e. server or controller information or specific address scope and structure.</t>

</section>
<section anchor="lpwan" title="LPWAN">
<t>The LPWAN has focussed on low-power and constrained devices. There are compression related approaches that may apply are <xref target="SCHC"/> or <xref target="ROHC"/>.
To be evaluated for process control devices.</t>

</section>
<section anchor="recent-addressing-related-work" title="Recent Addressing related work">

<t>Some of the work initiated on the addressing include solutions
such as <xref target="FlexIP"/>, <xref target="Flexible_IP"/>, <xref target="FHE"/>, and <xref target="SOIP"/>.</t>

<t>Recently, a broader area of problem statement and challenges in <xref target="CHALLEN"/>.</t>

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

<t>This document requires no actions from IANA.</t>

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

<t>This document introduces no new security issues.</t>

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

</section>


  </middle>

  <back>


    <references title='Informative References'>





<reference anchor='LDN' target='https://www.rfc-editor.org/info/rfc8799'>
<front>
<title>Limited Domains and Internet Protocols</title>
<author fullname='B. Carpenter' initials='B.' surname='Carpenter'><organization/></author>
<author fullname='B. Liu' initials='B.' surname='Liu'><organization/></author>
<date month='July' year='2020'/>
<abstract><t>There is a noticeable trend towards network behaviors and semantics that are specific to a particular set of requirements applied within a limited region of the Internet. Policies, default parameters, the options supported, the style of network management, and security requirements may vary between such limited regions. This document reviews examples of such limited domains (also known as controlled environments), notes emerging solutions, and includes a related taxonomy. It then briefly discusses the standardization of protocols for limited domains. Finally, it shows the need for a precise definition of &quot;limited domain membership&quot; and for mechanisms to allow nodes to join a domain securely and to find other members, including boundary nodes. </t><t>This document is the product of the research of the authors. It has been produced through discussions and consultation within the IETF but is not the product of IETF consensus.</t></abstract>
</front>
<seriesInfo name='RFC' value='8799'/>
<seriesInfo name='DOI' value='10.17487/RFC8799'/>
</reference>



<reference anchor='DETNET-DP' target='https://www.rfc-editor.org/info/rfc8939'>
<front>
<title>Deterministic Networking (DetNet) Data Plane: IP</title>
<author fullname='B. Varga' initials='B.' role='editor' surname='Varga'><organization/></author>
<author fullname='J. Farkas' initials='J.' surname='Farkas'><organization/></author>
<author fullname='L. Berger' initials='L.' surname='Berger'><organization/></author>
<author fullname='D. Fedyk' initials='D.' surname='Fedyk'><organization/></author>
<author fullname='S. Bryant' initials='S.' surname='Bryant'><organization/></author>
<date month='November' year='2020'/>
<abstract><t>This document specifies the Deterministic Networking (DetNet) data plane operation for IP hosts and routers that provide DetNet service to IP-encapsulated data. No DetNet-specific encapsulation is defined to support IP flows; instead, the existing IP-layer and higher-layer protocol header information is used to support flow identification and DetNet service delivery.  This document builds on the DetNet architecture (RFC 8655) and data plane framework (RFC 8938).</t></abstract>
</front>
<seriesInfo name='RFC' value='8939'/>
<seriesInfo name='DOI' value='10.17487/RFC8939'/>
</reference>



<reference anchor='DETNET-ARCH' target='https://www.rfc-editor.org/info/rfc8655'>
<front>
<title>Deterministic Networking Architecture</title>
<author fullname='N. Finn' initials='N.' surname='Finn'><organization/></author>
<author fullname='P. Thubert' initials='P.' surname='Thubert'><organization/></author>
<author fullname='B. Varga' initials='B.' surname='Varga'><organization/></author>
<author fullname='J. Farkas' initials='J.' surname='Farkas'><organization/></author>
<date month='October' year='2019'/>
<abstract><t>This document provides the overall architecture for Deterministic Networking (DetNet), which provides a capability to carry specified unicast or multicast data flows for real-time applications with extremely low data loss rates and bounded latency within a network domain.  Techniques used include 1) reserving data-plane resources for individual (or aggregated) DetNet flows in some or all of the intermediate nodes along the path of the flow, 2) providing explicit routes for DetNet flows that do not immediately 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.  DetNet operates at the IP layer and delivers service over lower-layer technologies such as MPLS and Time- Sensitive Networking (TSN) as defined by IEEE 802.1.</t></abstract>
</front>
<seriesInfo name='RFC' value='8655'/>
<seriesInfo name='DOI' value='10.17487/RFC8655'/>
</reference>



<reference anchor='SCHC' target='https://www.rfc-editor.org/info/rfc8724'>
<front>
<title>SCHC: Generic Framework for Static Context Header Compression and Fragmentation</title>
<author fullname='A. Minaburo' initials='A.' surname='Minaburo'><organization/></author>
<author fullname='L. Toutain' initials='L.' surname='Toutain'><organization/></author>
<author fullname='C. Gomez' initials='C.' surname='Gomez'><organization/></author>
<author fullname='D. Barthel' initials='D.' surname='Barthel'><organization/></author>
<author fullname='JC. Zúñiga' initials='JC.' surname='Zúñiga'><organization/></author>
<date month='April' year='2020'/>
<abstract><t>This document defines the Static Context Header Compression and fragmentation (SCHC) framework, which provides both a header compression mechanism and an optional fragmentation mechanism. SCHC has been designed with Low-Power Wide Area Networks (LPWANs) in mind.</t><t>SCHC compression is based on a common static context stored both in the LPWAN device and in the network infrastructure side. This document defines a generic header compression mechanism and its application to compress IPv6/UDP headers.</t><t>This document also specifies an optional fragmentation and reassembly mechanism. It can be used to support the IPv6 MTU requirement over the LPWAN technologies. Fragmentation is needed for IPv6 datagrams that, after SCHC compression or when such compression was not possible, still exceed the Layer 2 maximum payload size.</t><t>The SCHC header compression and fragmentation mechanisms are independent of the specific LPWAN technology over which they are used. This document defines generic functionalities and offers flexibility with regard to parameter settings and mechanism choices. This document standardizes the exchange over the LPWAN between two SCHC entities. Settings and choices specific to a technology or a product are expected to be grouped into profiles, which are specified in other documents. Data models for the context and profiles are out of scope.</t></abstract>
</front>
<seriesInfo name='RFC' value='8724'/>
<seriesInfo name='DOI' value='10.17487/RFC8724'/>
</reference>



<reference anchor='ROHC' target='https://www.rfc-editor.org/info/rfc4995'>
<front>
<title>The RObust Header Compression (ROHC) Framework</title>
<author fullname='L-E. Jonsson' initials='L-E.' surname='Jonsson'><organization/></author>
<author fullname='G. Pelletier' initials='G.' surname='Pelletier'><organization/></author>
<author fullname='K. Sandlund' initials='K.' surname='Sandlund'><organization/></author>
<date month='July' year='2007'/>
<abstract><t>The Robust Header Compression (ROHC) protocol provides an efficient, flexible, and future-proof header compression concept.  It is designed to operate efficiently and robustly over various link technologies with different characteristics.</t><t>The ROHC framework, along with a set of compression profiles, was initially defined in RFC 3095.  To improve and simplify the ROHC specifications, this document explicitly defines the ROHC framework and the profile for uncompressed separately.  More specifically, the definition of the framework does not modify or update the definition of the framework specified by RFC 3095.  [STANDARDS-TRACK]</t></abstract>
</front>
<seriesInfo name='RFC' value='4995'/>
<seriesInfo name='DOI' value='10.17487/RFC4995'/>
</reference>


<reference anchor='FlexIP'>
   <front>
      <title>FlexIP Addressing</title>
      <author fullname='Robert Moskowitz'>
	 <organization>HTT Consulting</organization>
      </author>
      <author fullname='Guangpeng Li'>
	 <organization>Huawei</organization>
      </author>
      <author fullname='Shoushou Ren'>
	 <organization>Huawei</organization>
      </author>
      <date day='30' month='January' year='2019'/>
      <abstract>
	 <t>   This memo proposes an unbounded Flexible Address Space (FAS),
   consisting of a publicly routable Global Address Part (GP) and a
   locally routable Local Address Part (LP).  It expands GP and LP to
   provide address privacy and special LP formats.  Use cases are also
   provided.

	 </t>
      </abstract>
   </front>
   <seriesInfo name='Internet-Draft' value='draft-moskowitz-flexip-addressing-00'/>
   <format target='https://www.ietf.org/archive/id/draft-moskowitz-flexip-addressing-00.txt' type='TXT'/>
</reference>


<reference anchor='Flexible_IP'>
   <front>
      <title>Flexible IP: An Adaptable IP Address Structure</title>
      <author fullname='Yihao Jia'>
	 <organization>Huawei Technologies Co., Ltd</organization>
      </author>
      <author fullname='Zhe Chen'>
	 <organization>Huawei Technologies Co., Ltd</organization>
      </author>
      <author fullname='Sheng Jiang'>
	 <organization>Huawei Technologies Co., Ltd</organization>
      </author>
      <date day='31' month='October' year='2020'/>
      <abstract>
	 <t>   Along as the popularization and adoption of IP in emerging scenarios,
   challenges emerge as well due to the ossified address structure.  To
   enable TCP/IP in networks that previously using exclusive protocol, a
   flexible address structure would be far more preferred for their
   particular properties
   [draft-jia-scenarios-flexible-address-structure].

   This document describes a flexible address structure -- Flexible IP
   (FlexIP) acting on limited domains [RFC8799].  FlexIP is expected to
   proactively adapt scenarios under flexible address structure.
   Meanwhile, FlexIP still benefit from global reachability based on the
   IPv6 interoperability.

	 </t>
      </abstract>
   </front>
   <seriesInfo name='Internet-Draft' value='draft-jia-flex-ip-address-structure-00'/>
   <format target='https://www.ietf.org/archive/id/draft-jia-flex-ip-address-structure-00.txt' type='TXT'/>
</reference>


<reference anchor='CHALLEN'>
   <front>
      <title>Challenging Scenarios and Problems in Internet Addressing</title>
      <author fullname='Yihao Jia'>
	 <organization>Huawei Technologies Co., Ltd</organization>
      </author>
      <author fullname='Dirk Trossen'>
	 <organization>Huawei Technologies Duesseldorf GmbH</organization>
      </author>
      <author fullname='Luigi Iannone'>
	 <organization>Huawei Technologies France S.A.S.U.</organization>
      </author>
      <author fullname='Donald E. Eastlake 3rd'>
	 <organization>Futurewei Technologies</organization>
      </author>
      <author fullname='Peng Liu'>
	 <organization>China Mobile</organization>
      </author>
      <date day='22' month='February' year='2021'/>
      <abstract>
	 <t>   The Internet Protocol (IP) has been the major technological success
   in information technology of the last half century.  As Internet
   become pervasive, IP start replacing communication technology for
   domain-specific solutions.  However, domains with specific
   requirements as well as communication behaviors and semantics still
   exists and represent what [RFC8799] recognizes as &quot;limited domains&quot;.
   When communicating within limited domains, the address semantic and
   format may differ with respect to the IP address one.  As such, there
   is a need to adapt the domain-specific addressing to the Internet
   addressing paradigm.  In certain scenarios, such adaptation may raise
   challenges.

   This document describes well-recognized scenarios that showcase
   possibly different addressing requirements which are challenging to
   be accommodated in the IP addressing model.  These scenarios
   highlight issues related to the Internet addressing model and call
   for starting a discussion on a way to re-think/evolve the addressing
   model so to better accommodate different domain-specific
   requirements.

	 </t>
      </abstract>
   </front>
   <seriesInfo name='Internet-Draft' value='draft-jia-intarea-scenarios-problems-addressing-00'/>
   <format target='https://www.ietf.org/archive/id/draft-jia-intarea-scenarios-problems-addressing-00.txt' type='TXT'/>
</reference>


<reference anchor='SOIP'>
   <front>
      <title>Service Oriented Internet Protocol</title>
      <author fullname='Brian Carpenter'>
	 <organization>The University of Auckland</organization>
      </author>
      <author fullname='Sheng Jiang'>
	 <organization>Huawei Technologies Co., Ltd</organization>
      </author>
      <author fullname='Guangpeng Li'>
	 <organization>Huawei Technologies</organization>
      </author>
      <date day='14' month='May' year='2020'/>
      <abstract>
	 <t>   This document proposes a new, backwards-compatible, approach to
   packet forwarding, where the service required rather than the IP
   address required acts as the vector for routing packets at the edge
   of the network.  Deeper in the network, the mechanism can interface
   to conventional and future methods of service or application aware
   networking.

	 </t>
      </abstract>
   </front>
   <seriesInfo name='Internet-Draft' value='draft-jiang-service-oriented-ip-03'/>
   <format target='https://www.ietf.org/archive/id/draft-jiang-service-oriented-ip-03.txt' type='TXT'/>
</reference>


<reference anchor='FHE'>
   <front>
      <title>Asymmetric IPv6 for Resource-constrained IoT Networks</title>
      <author fullname='Sheng Jiang'>
	 <organization>Huawei Technologies Co., Ltd</organization>
      </author>
      <author fullname='Guangpeng Li'>
	 <organization>Huawei Technologies</organization>
      </author>
      <author fullname='Brian Carpenter'>
	 <organization>The University of Auckland</organization>
      </author>
      <date day='16' month='November' year='2020'/>
      <abstract>
	 <t>   This document describes a new approach to IPv6 header compression for
   use in scenarios where minimizing packet size is crucial but routing
   performance must be maximised.

	 </t>
      </abstract>
   </front>
   <seriesInfo name='Internet-Draft' value='draft-jiang-asymmetric-ipv6-04'/>
   <format target='https://www.ietf.org/archive/id/draft-jiang-asymmetric-ipv6-04.txt' type='TXT'/>
</reference>


<reference anchor="IEEE802.1TSNTG" target="https://1.ieee802.org/tsn">
  <front>
    <title>IEEE, "Time-Sensitive Networking (TSN) Task Group"</title>
    <author >
      <organization></organization>
    </author>
    <date year="2018"/>
  </front>
</reference>


<reference anchor='SURV'>
  <front>
    <title>Introduction to Industrial Control Networks</title>
    <author fullname='Brendan Galloway' initials='B.' surname='Galloway'>
      <organization/>
    </author>
    <author fullname='Gerhard P. Hancke' initials='G.' surname='Hancke'>
      <organization/>
    </author>
    <date year='2013'/>
  </front>
  <seriesInfo name='IEEE Communications Surveys &amp; Tutorials' value='Vol. 15, pp. 860-880'/>
  <seriesInfo name='DOI' value='10.1109/surv.2012.071812.00124'/>
</reference>




    </references>




  </back>

<!-- ##markdown-source:
H4sIAFwgwmAAA9VcbXPjRnL+zl8xda7KSReS+3K2z8tUUpG1Wi9zu5JqRZ9z
lUquQGBIjgUCPAwgLa1Vfnv66e4ZDEjJvq/RvSwJAjM9Pf3y9MtgMpmMsuWy
sXcz46qi823jsnJS2fa+bm4njf37qKjzKtvamSmabNVObreT5EZXtbahu3Fn
5xq7tVXrJy9fjlrXlvTMp+SyyarC3OS2yhpXe7OqGzOXkfb0QcYxZ0XRWO9d
tTajImtpCLPKSm9HOX1Z180edK7q0cjtmplpG3r89cuXb16+HmWNzWZmfrk4
+3RxNgL566budjNMYneW/q9qzU233Doavq5Gt3ZPNxWzOPfkLRY4GvmWCP1b
VtYVzb63frRzM/NfbZ2Pja+btrErT5/2W3z479Eo69pN3cxGk5Eh0vzM/Hlq
Pma3G/dzVjm6Jsz7s2uyanC9btYz865ru8beW1yw28yVM3OLO6fOtqt/X+PK
NK+3/eAfpuZtXa3juB/cz10VLh0NSby1tp2Zc1p7k5Xm4vNuT5dz1xIfb7Kq
zcx5mTXZ2JyfmTffvPzmJX6tO7qbbvixcq2lLWuJ9d7UK3O2tY3Ls57WErNP
C5r931dhWqZ3hE1qtlnr7uxsRA98eHtJ0vDu/Ls/vXlDX99eLC4vFpO313Lx
zR+Ti2efzt/L5W+/+YYu35y/P9dnX39N3z9d6fev37zB7+9K+3lOA80nb6fb
2t/W9679ZbKiq243yaI86Z1uWdq/hdt/dhnfOOnvnBDPuhxroQfO3599+HBx
2d9M8g45m/ggxpNdU9OIWz+c6eYqmaJaT7xt7lxuJ3XjaCtsQROCnvcXJN/9
XRlJ1daSZuX0+9234Nv84uLiu5evp68WN5eLH2Z0xRgiYY1d3bTtzs9evHhF
0mIt7iIBeNH6Su4SDcQAY/O7hdvayY2tvMOWmEtRcKjZCY18ahaZvzU/QGF+
x0+L7r1++eo7+ooF/fjpLzPDP729mk9fvZy+evXyzQtcntJdr6cv//TqO/xD
n78ejSaTicmWxMosJ42Kan5ek2TVZZjem03tW5OZgmhqvDWeLADJWVVX0bIY
YjDpXl2KxSjcamUbqPKua3a1t35qLu5sZUgJu/WG/rF7U+9sQ/STxtDYucxZ
kiTb6s41dQVrNDak3nShwHy9QQt3m2y3K0nUW7IU3jSkYjVRaCJRrc03VV3W
a0eacTJfnLJxy6qa5m/kXiGCnqdR4+17c3JFN8c1TY1ZbJw3W7utienO552n
NWEZJt9kRHW1tmI5UwtLX0oam3avrUEyzWfXtsotVnO14PvnC6NmnGYZmSta
7i5rWpd3pPFGxRYskuflcSJl5dZdg6HrrqV5MiJj6UqyGGZJw1lmtcX/aL/i
BLLjW1cUpR2NvoJNbeqC9IjWbx6+cvj6OBqdVYHX+8hpHUN4Sxcrm9MCCwt9
8abztG+0SN3Scb9BtMRtTRaKhMLsNntPu1Ua8GgHFmFhybYmO0/cWAyIN6TR
dG9Oa4X2llgo2TCwgP7ZkXkwmeyI3e42dA/ZwiHXmOkviOHkce49yHVbYvAd
s8mQg6i3LAlT2gWWO+8KfmreUxhFC9TgMUfjV7S6vdlmVba2IrW+I8HcQzYg
3MQD77ZdyaOTd1q193gc1zGESCNPFkYN7Av8VSnFdlc0Ub5xFVTqKhHexUDW
Ib4Dzm3rBmtpIRhONuvX1dh3+QYcHX2si2VHvvS6qVeOP52fXfZX6KmxsW3O
+9XYfrJ2Q6701cuXqTGIo0NgDXmAjXHt72l99xWJfX5LFIhDEkWlUViyICbC
bJFK0hQyVy30wH7ekSRiQZus5e1ZC0sGejAXZSOdu3dlCTruwO6qI1dZd57u
rezKkUBjItts2Y+qdBS4nZXkjtSL1rpauZz8Q77HTdF+0CB7HRj7BJtFPMY/
d8471U0QoXs77WHVk9aM4FStq0s0y9Ai87LuSKJIkSzmJJVpu6x0v8iyiSZv
SeZJJLZEdglpsJ6GIfElkbz+cO5PTWmzQu1SZe+jJKiOpzaMbAZsUuaZkN4K
91Q70brClnAPzBRySxk94muaFHvDG42bPllCoy05uTHdD0a7ynkydmo6SxeM
GGkOnBIBGfzsxVaXNa15As/O99/TFsq33oKymW73Oyuk0gAT5pwOu+qqXPQl
7IZvu2KPNWQljVRgWTDTBSRBkI4JLpiBKou5qqwyhR5uEvuLUVMriU25tXaH
ITZYdE3mCDcShWS5tl2ley5PrbJcXUlm7gi8WLlToQlLKHGt0KUWdcd2dFWT
S7Js8sBnMjU0FHsSulSywlz1nsZsMrJ6S9aOhiRBWELS4S09AjFbNfU2aE7P
XVI5uq2+t6xKQVwgpE3LBlVsYCrmUAkim0iDEMBZbWFYAtaHElXYbXagqub2
M6xRVh7uK3apgloSvidUrF4VhlNV/n5DKypIxsDrKHTP+TKlGGBRJt7+GhQh
nYFWrVltwGK3Be6eFDWG6Md8eCAQ/fiIUXK7Y3vGVCfhTWBcsASjEWRKkRI2
u5WtzWVvHROqqIPnHvj7p+TtQH3GhygFSj9AKvRPw0vjjS8BXSdiYVKTCl8Y
LClRTQhiwTrMmGk0+kPqKQ9B5IwXib0YQrgD/z5cB00YsYKiDPCTvWYwvD3Y
oF8Ua7CnXEVPeeg/0n1lqSYvXpd3dGPvq7Dd5ZGOejOJjmXlbAnXGLw02TS3
dm2/tpLQshiZ6PITC5/wa2/OIvqYmY8W+kCIwYtToxiGQKAJqxGplY9D+0HO
oFMBSsFAOkhAOfkAoUVeHsDsAD9wjyoyNDnxHjDgW/cL27Zum6kNAyQCkMIS
3/Plj0rwPJi4mTlLDN7AWQs1rDYCkHS1YnqfMZmMtffezF9ciftZEpzgEUhg
yBCECYiW2u54fMId4oIycGFl3n+c9zsltuUIw0ZppLU9zGYghr480jrDCo+X
ak4+fpyfztQ30YzQaNJAsrdOAXgi1z6vd08YAVgA6/PGLa3JfpNzcV1HYDNI
Dt3Eqk5jZZ2KHgnJWgVMPDp2P9jeOGGb3ZIMgFmw5kwoWcO63o0hgEHAGJYf
8Y8tjPpgCGbD0WAgckosfRFZSublK3OWk5rut6Qtf8CUs+fEaTSSeCaKrpod
Qhysz0T3WUPPkGIgaUDBTkZfHxH0/irX6adVDZcHyps4VqokwZozslzaGAsF
kBkzFZGvYsk50tDp37n1lDwHj8qEPdJINOuY3NHG0abStWPAwB7Rbwg8T81Z
q/twb70arzGDvR45Jk6ZTVdQ738x2VKiILITz/HXnBD7Tw/CP3axvcnk6WTl
5DG2gxk7cn1NuWcBSCefsiQR9LbliuIm8pBe9LfbYagBJIaKwOF3250qf0D9
akXJQbcIMOGbTPz750nyn3D9f4z5Yt5iorPdzpsvU/oz6d9FACFk4eFDyOyR
Oc3DdodxZgfj41Lym/x9iaNqcob+7o4e7L/0ZPLDZE4LWvoZD/RFv30fhp0f
+8zB070zwtODb8YMXNWJ3/uWUZC4/Lrxpwm/niUXizaHi/6SkBD/0psOh0o2
Z8ZPkQqb/+Ql88e/fklYR9dY2uRn/vhlIoTgT4RrkiwuWcfRzPzgl4MFRKr7
D0fUm6MPQxL14aMP71gDBGEEH5vs2bODP8zMV9FGSOrwX3/3PrUP76Jx/RUo
9jsY1x+r0t2KOyXxSQyZAgayMgjFyUkhrza/7oP3saYoUj9MiPtWMnBPRfuI
58tagfMTEAuXo5mbchJMr97afQpUxWcBvSYGeGAjNBo9QK39nIgN/XHo1dPq
qrzsGN4MEh+c5khSIMLSS1w9P7u8ImgvSRAKtM6iHRIPHwmJ6qVgMwauAydu
jwzPMC9ARnXj1og/B7oL42in5EZuzs/eno1hVsfw8k/oNJhEG7rMyFMJqPKW
xir6DYmiEAhLs1I8X54hw2Ks40iYRqOpkEmiTyc9m74/O78M+aFTmUo9FDuB
iUx4NNtxpjdC6fS5bYYkIF3eB3GJkBw5aFasNA7VHT75iPRUYSnsK314MvqQ
SIyucFV3HGAZ8s/Ioz8+nk4ZmpwPBOiaI26g+sUAMxyImd7FwQ5+QnBu6iWi
e1vMRqNJsuAEg9I3AsyHcF+5te3K1k3ULSSPE3uWNmhPAXB2LAuYQ/O6MY0q
d3G2+ICa1bHdmpk+Nu/Z/zShuiMhswiorimqMX0AOeN0vxV5DsdqCLxbLwB8
Yt7KiAyO8Wkm+QnEcQ1SM0/Tce8kwfNknIMfS2hduMhZPArI8jRHzIFWnnFh
451E+PbzNiP+jUMMlmdkWDM8fud8x8YgRBGYB/mvHHnObFuXTmJUSSsFZPSU
NGx3HSo+wcA8s8AsfU5QGD8Yd97CAEzYAAxjRUZ0qsdkfWjNV4uQ/wyCoSFt
2alBIlGuavCaIUhI9wUDk1YfSIKJcKRLoqU5ztEhnRZkFrz/LNkhjeoSQymo
lcR+VzukB9g39JZeFMIP3AmnQXg0p27uAixH5vvkfuNILuH2wIj5wnCFOWsK
Mpi4lcJFLDMr7xFn7mpC8EvOj/RRfLJUWIjnCmrmsoM4kSXKu4Zp9Sjenort
OEoLDzIkEqJxhjJEjO4A/XopryGAkCBdxG3ncvbqf+8sdhQ5Oyw08xJqzIYB
LVfrkhQa1114taR8vlZrfFCnGD9jSk8ohOAayYriRGg5xRgdrkkJa0db0tLV
HbmGZrJuXKEegwSBk2sZct6QJVZQW5aThA19kvAMNoisA9nDMeCU5jbhS7c2
q9jWI6mFORFeMK2rJusjtCDLKImSj+XsHUWmxUFkSmP/gbPRonXwEGwHbdxp
MUy/9/1dulnB4/MWZVy+JnjUUrwl4k5ySQYuJMd1ySE/SgDJIpn7nhhFuz0e
jEgLr7sGYgW/iHGxkjWJdqhYtGSCSGlL94vMld3VTvZQ8jWpdm2nukyCBrRL
qCvG9DBnqRb7nUCccX8L6jFiKtndhKz3fPHiahGFIeSYBQ4I7A2JCx8liqJa
0XizrsU4cqJKMg4Z2abWxvzBimzFPZEiMrkjc0qr9WEBPApKfu1mdliEpnF+
scPSBwROMKTPuE7Bj9uKg+gCS+QEtkAwMf72c7Zlyy8mH9SSQnMCGToq5h8X
dxqisb/SHeap/t5JRYJzlkE1+spTnN9zPoBoX9JK712B8Jsoroqw2J/YbPbQ
hwWZlAvoYdmVt4OsKKSdCyviEJUHLFWuSZ9GIWIv9vXD9U9nl0ZK1/UiOkkx
npKgz3JuXuDKDDROzWgoUGGOaSCxdCsr9SBilOj/IC8NElmOWxG3lCpkT8gh
ZUXw9pqhjDK05USq89ukBBqrB4FjsSRF0r/J7lzdzDTPOCzBKlnIvZd8O+0z
TBH+HdaywjhPu+OTAH+IU5xxbJktpyE71GcYmYy3tkXwO6hBSY3Kxzqf1KFE
4PHMus5iWJVWEZiPNa1AitZS3zkq5w0sIoUTlsMDaRF4ADa6g4I/PhpGYyVr
RXSVurtSm4XRbdWHU0yldfaDOhvZCYE9P/0gK7hh2JElQizJJq5VBuMpio+K
rTb0jIertZ93JW13mtDXGw3XQlfI5KgXluaKuNkWOf6wSWlRXwlC+q7mSmeo
vIT4blA3DfU5JYjLQUD+vU9FLQiExCiVi6B12fc8jCOxDB9jUa5u1iTXvxym
7PeHQst1cnMoFMe1JTKrJUyRr7dDqNRXjLQYzg9x9Cz5pjuuQIn8Ja0Sx+Bl
yskfJGmvtaeFG9Z4vIevtM9F8rHHuVWPPOi6rgtU7Jfo2llFvSSVK1McrCYt
Q8UUQyDRzWEL4pIT0l0x/hH3OeAfUa2sEJieFfWOpFoD1qTCL9VVb/uAgQwC
/YxEiYjyfeM49x2Sv2qZspwNU6zj02ghOTU1bmrJfhIW7cswSKLKsOxTac1F
ITVp7upJ69uck5f8qXgjdj4kbGm6QlIZB7W2LbIKDqAASoxSrI+dZwzxN2Qp
w0ZOwGFclazBaPS/+KMtpaG/7zi9NsgPPvefEafAgi5+iQkrZCKJX3QFDvfL
Pz4e+v/OLkHC88+kUxsyS96jSk3YR9JygjN+bc74fGApmYi2LuqpsmEkRiuA
OulUYJjFwEV8YbApAzAM+RQ4M5YbhjV6y6miIi0fl/vYHENQSmFJWq9P00Ui
wrG62za271HzrCTZlqPd1I5JXw5dKEu35vBECzRord1t2MvxrCGsJADfQljF
VGh3XdKbFAwELR7opQS0hr5o3EGh0vukMQJxYnD3z/ahbbI+Qh8k+J5tqQjs
fxeSFCfXn67ezb//8WYcU30g//3Zp8XpOAkMGXyRvwhXXsyvSbfw7OXFQp6R
5yeL8+tTucDdOzGVcPJ92dm2JsaMGaHxRcwzDkDqNLS7JQQz6MrETcfWOdyP
ZCvp7D7kxJY2z5B0YPGLIX70NITl0F+ViMUw5u+blnjyNBZPAoLE6gWQnPVO
Qt0dL3vLBULsCLoYGQCwReV6MSl5Uw2kLaUFDivuT14iZuGmXBj0tHznPHf/
kCqQWpT1HnlMwhzagyQ5owylpCE0671odpBZ6eudzFGuHmQTjJVN+yqYjw6U
wFghGtqGOEjsJSgV44b4vtvR2K+/+bYX1Yq1vVqjd6tj7CGyg6TiTeJ+ZdXK
UUaUjDhDFtOsaYc5EXHY/nGQ68Z4SR9rEq5It0yGLembGHp3mHTBoKyLQTgL
rpRBcgMRsaQrNVCC55WHS4lDw75i4irPdr7jn1wrfhr5Yrc6SC9z/2SNniLX
nnIxbw5Kf5DpJjn65NE0tiOiKJgZJ9zgJhLuf1kP1h6pkla9JI0UQ5hhMbNX
RJXtaDXRqAgOgfNdFb6Ftjf10RKLa+rFIwnBDJLuRh/UOkb+YQHoAb6skeI7
85JU1NAyCz48oFBExQD0txVFyrSVbHS5q1Pyfeys6Xv0WNcfzrEJOgx9E98Q
9jBIv1DkEwgi0XDCv74dy3KWqEZTOLOv32GweQy6tKMVWLdBXxmFyHgyz5oG
fagqBED+YVCsyqGLi6PnJ7DJwL+dBURHW15wq8O98zYRicpKtmOpsdUuZCgz
yOomMbljSCXiFgSKMWnCqA1p+oDIeJvZBkt3sZdWF2PS/Jn58B+PM8PLv7eR
BoQlSGjdb/aBQM3CBllWBgBrMA8IN6vYm4Mbozy2yS7GONzx8YJeD5LtO8jH
/4rkC9sw0JBzy1oBQlCQYRoki+QQecGzGBxICRYh9kzEtAFSqTSb6BPMjXQD
+1j06y0QxglOAfkePODEzYTxAUxorRhUB8IO8Hqk9ZEWwBnCTTRSPFTQlcNO
zGDRaaXzFWyWk240jBG4GR8Oi5e+lyK5RDEkMkGEz/Nbr9aJn3mBgWjY/pEX
+CbGjEQml8wrEExvKVh9E+PCqUQF1llvBELeONreGEcoayDPWJgIXShOhuRC
g+ymEPuk3QtJF7FovDdi+lI2MJWZJBn1utJ/cHPYJhZeMhF7TvmB2OMZWZ/4
7Ira8d7MKhswSkTGw9Uu4PxEo+rquedhEDiRGoSHT13YSFP6iK7g91xaTZMS
0tkepE2pyNZsBkIugJW6QbP0keNQrs2vk+1lQfxpYwfbCIPKVeVnaRvHHYIR
7hkatChl7n3dIWa2vaHulGqa+oYEEeM8Y8LoH5QexDLpgBi7QIseG3UhmU3m
YcNXX2Kbkw7n7Si5IhqjXYguOaWC1nEbDnxwnDAMVAZ4t8/tSJNTabOmIvrG
ZunWLB96oIG3hzscSQ+eaG9Mie1lRLGLNOiPB13t0uXu6YuUE9u005aryl+Z
G3wmb5KMHRvpaNAtvJZ05g7aAphWzkcWdsWFgxZnxTZc3oEMar2KW87qphCw
EA7A7OIxIIlILLqbKxbHtt7tspAF+q12z14oQ6IG5Uw47n2SsxkHYxt3UqtL
LftLJ50RekgF8KhjRpIEWnmUOEJLEAIZQHAJHJg2sGp4kkg5S9FvS1sfajTv
siVQJE1yUWjT+jmOVjAU+bW28dD78LlFRM5kypkMOEEMdRQXT01MEBweaQLa
GXrXtFhLrLuLwcCUoOG9Thva0Ifhbsghh/UIWRUFXT2XfWhC5CyRwghJDsSj
AObD60GXPLosJCmGbx/+GB04DezWFbPYvOXPdCl3XmWSxDHkzcGkTY0G9yRA
AShxUm6jgJBPLnF4Ja0LHOKaV2Pzemz+ONRhcBrYM9DhSwjWqR5RoJDJVSuK
uZXnfYUqKQ5BJD71yjm67o/CJUd8GErxscdyH9PdSEUnicgVJze4TqlCTfst
rRap9ru+UMDnlSSHvaU96UK5A0m9VutHFf3X4nASF4fB4cQk9MrTY8vKd412
cYZGDx9Aa8BgVX9gioeV8BEivWMIRgQ0FuZL/ELoTVhlXo9k5cRIeo6YceKm
RFXwqk2941352fHJk6RFfIcsVyhwqaE5jfyHMcQ2jUaL799KY40c0jtPTu6N
PuIAaujxGdSSn9EhlO81gk5yqceaBSNJu/VX+M+q74nQYCiwNoTWaXdE0hDd
t4pTKNLnSXB0ig/cNbHERMZ/R5phpQMcO8iFtRQ8I3rlYvcEPdW9P9Peiycb
W1iyfOiYkLIuuqIILgSF1n068sa1nIPd0H712OGZ4DVAz7Eym2u71zwlKfpV
Xw1kSUGJsq6CnbKf4Y1ZCgmktJz3176EutxriQSQQ+r3AaL2jVT18s5BG8JJ
7oMG/AeOtxigjJ/DJTKBB76VLI6ORdpaH80G8Qktd1L28zWfoRijNi3l96KW
lhAF3b8Z1aG0v0J2DX74I9s4enaGush89Y9vLaPe4638f7R5M4P9Omj3RzX2
Y9LMF4qKfStR38MnDqKta6nGBxFmVerXMuUxz7NKec8m4YDBRycN+9LSSe+p
Qnakf+8FgMmW8Z3Ug8dmjnxuX1yQ6p5Fu8v3nZ9wt23fd3MqtM3bgF2J/DtX
8nG4vuM/ujdEjOYkfGXHOBb3yVhTLySI8DQkXwgAJpurEivpxEoigr22FyCH
mRwz7dMc4oe5oE37qc1NbyWpJy9KCITitQrzw258z40geig0aRrSuGvYC8RW
fSx5Um36EdMXzhezJhnSxr1BwIigTHp0tLKJWdgb0pbuaFOt9prFQyY43U2y
sMVPW5c3tTyT8xP+AMOxG4SH4ZbjQa/Qztk8nK4ipAMsnYSiQEKok2qD1xM1
TYGl5i+D47ujRQLCfqM2H4xKPACMLPhwOIFgevZLUuWhgosVDY/DMoBZ6cs3
sC0VGlwM2hB1VGm0l95VOXfJDUrJkUxwra44aTMYO6eF1NukZK1H5SYt2QfW
If1tSrMdnGgW8v0RquXXliT7tESD5V0IaBVDOTmLBI6vuDM0SzPkoTsL3mS+
TcIp3tW4WhI4BLRQgspONuSWM2Qw+MyRvgrH3OyABQZv0nn4isCvf+RtvuFi
qvar9q/PGd0cFQ0k67NRhFwfxyEBCiRnjEItNyl3oIFLMskLTnIRs2IKWku7
wW85Hcsi5yPHiOw6y+FRSGSXnb5XJunuPegymMf2koCQidUTbueBPoXOtEHz
Dqp8HP2au7rs+sKHGlDtTlpxh5aPtRV+qUDauEW+gbELWuDvvh6bu29PuX2N
8Pqd1fKn3EBY73M8pMX9G9xJpW8Mea5tgTfvo83gC1ddGbbOaqP30YMJKl12
jnzhsm5J8ifh5HjaOZDT/9GYZHalAUuNo3bRDrq/udkpOQzGtcBhEDbmrGl8
dUgo/sSjohK08tFhrUv3R9MKVXcu9RSM3H23RLWnbvoWRo0uYyNNeFq5pMKN
Nx6pv064hVanLbdUhoBQEghoBpKTqTqqnOiiuIZPjDEE0NywPNC3CqJyntQ0
UffoPLPqIBs9dN4KVYC9Dt5QgNArLHYcGZimWcZ9xaZe/sxhX3j1RdyNo0RQ
yye2Q8O0dvmoyQoJSC+H4lM6LddPND/OJQmszqzgcouSj8lIMxBXfkgvirG0
hwkiFDFLM5wutTIelVvOYmQesAMWhM1WCCaZ69Ju1velhLRyhE8KBs6QHFDL
/oGUJXY6f2DoMDoPdeKD16n0EjzYodCcTQYt7ezxkuOPtfDhU7QL6bsMxiLi
ekx/cJJf0kz3GSMJjvFgEwfgimHA510AexGHhd4xfR3DOHT29Ef5J6gQZNol
zeXUpr61FdeWBgkRnGTgc5JbLR8e9Ow3dkI+cF0N3mUAr92vd2PDm0vSHlYF
g+SF6jsGKFy8BMdzSVsSjfAMzGMcV9BQQECmGnLfkXuGCCTNBUkLQIioI0P6
U73yiqV9j8ldlSBVrujB6idQGqaJvqpDGwQ1HnjgRksRdThrBOLsE++qOerQ
I7ehut5YvIal5dYlNul8aMajeTbt2UzfkjHmBK3l1EcrHccCJdkzSQserLa+
0oJTs6hdc3JWHJV2scyvJyHBkr7SQuEs+NM1DL7cZ1sMD/zGLNz9tJm2094Y
S7qplE5WPmxw0LuhpzAm9HhZxKZfclt8WIaQ/I42rZFeneqJroGgjPpCHrVm
ZFxRUAmLDTfR/YoZkmMz80VfszzIVPc1kthKdnK1mAQwdTqZTP7t5PD8hF69
DredmtFJgkVO0ct1wuUaUQT+k6tpZBR6tq5DML6XU0NpnMSlSKCKlht0rie9
5YwH9UN+CRFUyBC1taDCT1Zr4Bu3kxWbM2mX1KM+84vFOwaIoZ9WXWjaSBzf
v3aiXcA//XA60qbg49v4LXFy46l5eEhe0/f4yA0zeg8fXlKV5wI7IdtJw4di
Bl2dQjUfbgCg0zK8e/7dYN4ACWoIBsm0PRlvr4kIeXNArsBOwzbG66E/jMuf
vpXIj0Xo2bmWXTien3fsMTScTPpWlOYx0GhIgNHA3vyTZkzwfp2sr3owHkwz
ttGoIfPeDt8s88SrSvq8H2E1cSOvjbwfZow3gDngsj4ukpSwvheOu2wWN5d9
39nDw/Ctgo+Pquj1wlxd34zwb9KbKq66fzddOGynme8xmUuKAMANbhmr6xZQ
XPJAksvh++tqWeuu6Bts0GOxjYd35S6OO5DkF4GK4F1AkWQ39X1xMQ8yNT/Z
VKnYw3PLIi/I9y0toV2cNKPsjpuceeHNYRRy8NaqH9ydVqKecFHhTRqFniEj
/ykJpT4nK+hb6739+8wQ7MYVjQ2nwLUXYXj4Mr5ZU47+RCIieOYXTsgbqEKv
vXgmPmHBai5nLVDCYyFXJNeHVhovSEhlk1cqLOKb2BAds5tNmvVDUjIkL3Bc
KOP31eGJhwe8yRPt/Q19xls8IXgL6Z+RDVHAdHjcohd/zuwjoZK+KDZMz29P
GPS66QFU1woWV0VOAIKcybb9ocNR8PgPD/Je0cfHsX7WN4fqhfcX+ABG0bqu
cHk6MiMhDhgxAzzj6DAcVwmvXPSxPV1PYIVueIdzEPrKUdbJERI587PLM/ip
/m1UHCGmvfaxYYdQZ6aSyN0JeBZcuwlVql8fJ740RvHrfXoAy3eyA2c5GsNK
5ExYI0by7ke8FWc0+j99bARGUFgAAA==

-->

</rfc>

