<?xml version="1.0" encoding="UTF-8"?>
  <?xml-stylesheet type="text/xsl" href="rfc2629.xslt" ?>
  <!-- generated by https://github.com/cabo/kramdown-rfc version 1.7.35 (Ruby 4.0.2) -->


<!DOCTYPE rfc  [
  <!ENTITY nbsp    "&#160;">
  <!ENTITY zwsp   "&#8203;">
  <!ENTITY nbhy   "&#8209;">
  <!ENTITY wj     "&#8288;">

]>


<rfc ipr="trust200902" docName="draft-pjs-6lo-can-01" category="std" consensus="true" submissionType="IETF" tocInclude="true" sortRefs="true" symRefs="true">
  <front>
    <title abbrev="6LoCAN">Transmission of IPv6 Packets over Controller Area Network</title>

    <author fullname="Alexander Wachter">
      <organization></organization>
      <address>
        <email>alexander@wachter.cloud</email>
      </address>
    </author>
    <author initials="J." surname="Park" fullname="Jungsoo Park" role="editor">
      <organization abbrev="ETRI">Electronics and Telecommunications Research Institute</organization>
      <address>
        <postal>
          <street>218 Gajeongno, Yuseong-gu</street>
          <city>Daejeon</city>
          <code>34129</code>
          <country>South Korea</country>
        </postal>
        <phone>+82 42 860 6514</phone>
        <email>pjs@etri.re.kr</email>
      </address>
    </author>

    <date year="2026" month="November" day="15"/>

    <area>int</area>
    <workgroup>6lo</workgroup>
    <keyword>Controller Area Network</keyword> <keyword>CAN</keyword> <keyword>ISO 11898</keyword> <keyword>ISO-TP</keyword> <keyword>6LowPAN</keyword> <keyword>IPv6</keyword> <keyword>Adaptation Layer</keyword> <keyword>IoT</keyword> <keyword>Internet of Things</keyword>

    <abstract>


<?line 93?>

<t>Controller Area Network (CAN) is a fieldbus initially designed for automotive applications.
It has since been adopted for use in various industrial applications, such as CANopen and building automation systems.
CAN operates as a multi-master bus with frame identifiers of 11 bits or 29 bits. The CAN standard, defined in the ISO 11898 series, specifies both the physical and data-link layers.
This document describes how to transfer IPv6 packets over CAN using ISO-TP, a dedicated addressing scheme for CAN nodes, and Static Context Header Compression (SCHC).</t>



    </abstract>



  </front>

  <middle>


<?line 100?>

<section anchor="Introduction"><name>Introduction</name>

<t>Controller Area Network (CAN) is mostly known for its use in the automotive domain.
However, it is also used in industrial applications as CANopen, building automation and many more.</t>

<t>It is a two-wire, wired-AND, multi-master bus that uses Carrier Sense Multiple Access with
Collision Resolution (CSMA/CR) in its arbitration field.
CAN uses 11-bit (standard ID) and 29-bit (extended ID) identifiers to identify frames.
The arbitration field also incorporates a Remote Transmission Request (RTR), marking a frame as an RTR-frame.
The maximum payload data size is 8 octets for classical CAN and 64 octets for CAN with
Flexible Data-Rate (CAN FD).</t>

<t>The minimal MTU of IPv6 is 1280 octets, and therefore, a mechanism to support a larger payload is needed.
This document uses a slightly modified version of the ISO-TP protocol (<xref target="ISO15765-2"/>) to transfer data up to 4095 octets per packet.
Mapping addresses to identifiers uses an addressing scheme with a 14-bit source address, a 14-bit destination address, and a multicast bit.
This scheme uses extended identifiers only.</t>

<t>To make data transfer more efficient, headers are compressed with SCHC <xref target="RFC8724"/>.</t>

<t>Due to the limited address space of 14 bits, random address generation would generate duplicate addresses with an unacceptably high probability.
For this reason, a link-layer duplicate address detection is introduced to resolve address conflicts.</t>

<t>An Ethernet border translator is designed to connect a 6LoCAN bus segment to other networks.</t>

</section>
<section anchor="applicability-sec"><name>Applicability</name>

<t>CAN is used in domains other than the automotive one it was designed for. Two properties
recur in those domains: a bus that is already installed and certified as part of the
equipment, and devices that are increasingly expected to be reachable from an IP network
for monitoring, configuration or software update.</t>

<t>Elevators are an example. An elevator installation uses CAN to connect the controller with
the car, the door operator and the landing stations. The bus is specified as part of the
installation and cannot be replaced without re-certifying it, while the same installation
is expected to report its state to a building management system or to a remote maintenance
service. Such connectivity is commonly provided by a gateway that translates a
vendor-specific CAN protocol into an IP protocol, and that translation has to be provided
for each combination of equipment and management system.</t>

<t>Running IPv6 on the existing CAN bus removes that per-combination translation. The
controller, the car and the landing stations become IPv6 nodes that a management system
addresses in the same way as any other node, and the Ethernet Border Translator
(see <xref target="translator-sec"/>) is the only element that has to be adapted to the building
network. The same reasoning applies to other installations that use CAN for their internal
communication, such as CANopen machinery and building automation.</t>

<t>6LoCAN assumes a single bus segment with a modest number of nodes that are powered from the
installation rather than battery operated, and traffic that consists mostly of small
messages. It is not intended for installations that need the throughput of Ethernet, nor
for battery-operated nodes that need the duty-cycling support of <xref target="RFC6775"/> and
<xref target="RFC8505"/>.</t>

</section>
<section anchor="Terminology"><name>Conventions and Terminology</name>

<t>The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY",
and "OPTIONAL" in this document are to be interpreted as described in
BCP 14 <xref target="RFC2119"/> <xref target="RFC8174"/> when, and only when, they appear in
all capitals, as shown here.</t>

<t>This specification requires readers to be familiar with all the terms and concepts that are discussed in
"IPv6 Stateless Address Autoconfiguration" <xref target="RFC4862"/>,
"IPv6 over Low-Power Wireless Personal Area Networks (6LoWPANs): Overview, Assumptions, Problem Statement, and Goals" <xref target="RFC4919"/>,
"Transmission of IPv6 Packets over IEEE 802.15.4 Networks" <xref target="RFC4944"/>,
"Neighbor Discovery Optimization for IPv6 over Low-Power Wireless Personal Area Networks (6LoWPANs)" <xref target="RFC6775"/>,
and "SCHC: Generic Framework for Static Context Header Compression and Fragmentation" <xref target="RFC8724"/>.</t>

<dl>
  <dt>6LoWPAN Node (6LN):</dt>
  <dd>
    <t>A 6LoWPAN node is any host or router participating in a LoWPAN. This term is used when referring to situations in which either a host or router can play the role described.</t>
  </dd>
  <dt>6LoWPAN Router (6LR):</dt>
  <dd>
    <t>An intermediate router in the LoWPAN that is able to send and receive Router Advertisements (RAs) and Router Solicitations (RSs), as well as forward and route IPv6 packets. 6LoWPAN Routers are present only in route-over topologies.</t>
  </dd>
  <dt>6LoWPAN Border Router (6LBR):</dt>
  <dd>
    <t>A border router located at the junction of separate 6LoWPAN networks or between a 6LoWPAN network and another IP network. There may be one or more 6LBRs at the 6LoWPAN network boundary. A 6LBR is the responsible authority for IPv6 prefix propagation for the 6LoWPAN network it is serving. An isolated LoWPAN also contains a 6LBR in the network that provides the prefix(es) for the isolated network.</t>
  </dd>
  <dt>Duplicate Address Detection (DAD):</dt>
  <dd>
    <t>A mechanism used in IPv6 networks to ensure that no two devices share the same address, preventing address conflicts.</t>
  </dd>
  <dt>Static Context Header Compression and fragmentation (SCHC):</dt>
  <dd>
    <t>A header compression and fragmentation framework defined in <xref target="RFC8724"/>. It relies on a
context that is known to both endpoints before a packet is sent, and elides the header
fields whose values can be derived from that context.</t>
  </dd>
</dl>

</section>
<section anchor="Controller-area-network-overview"><name>Controller Area Network Overview</name>

<t>This section provides a brief overview of Controller Area Network (CAN), as specified in <xref target="ISO11898-1"/> and <xref target="ISO11898-2"/>.
CAN has two wires, CAN High and CAN Low.
When a dominant (0) bit is transmitted, CAN High is driven to a higher voltage than CAN Low,
so that the differential voltage between the two wires is nominally 2V.
Both wires are at approximately the same level when a recessive (1) bit is transmitted, so
that the differential voltage is nominally 0V. <xref target="ISO11898-2"/> specifies the voltage levels.
Because of the wired-AND structure, a dominant bit overrides a recessive bit.
The CAN specification does not define any structure for the identifier.</t>

<t>To resolve collisions in the arbitration field, a CAN controller checks for overridden recessive bits.
The sender that was sending the recessive bit then stops the transmission.
Therefore an identifier with all zeros has the highest priority.</t>

<t>CAN controllers are usually able to filter frames by identifiers and only pass frames where the filter matches.
The identifiers can be masked in order to define which bits of the identifier must match and which ones are ignored.</t>

<section anchor="iso-tp-overview"><name>ISO-TP Overview</name>

<t>This section provides information about the use of ISO-TP (<xref target="ISO15765-2"/>) in this document.
Parts of ISO-TP are used to provide a reliable way for sending up to 4095 octets as a packet.
It includes a flow-control mechanism for unicast-packets and timeouts.</t>

<t>Multicast packets do not use any flow-control mechanism and are therefore not covered by the ISO-TP standard.
However, the fragmentation and reassembly mechanism is still used for multicast packets.</t>

<t>ISO-TP defines four different types of frames: Single-Frames (SF), First-Frames (FF), Consecutive-Frames (CF), and Flow Control Frames (FC).
Single-Frames are used when the payload data size is small enough to fit into a single CAN frame.
For larger payload data sizes, a First-Frame indicates the start of the message, Consecutive-Frames carry the payload data and Flow Control Frames steer the transmission.
Network address extension and packet size larger than 4095 octets defined by ISO 15765-2 MUST NOT be used for 6LoCAN.
The 8-octet payload of a classical CAN frame is too small to carry a compressed IPv6 header
together with the ISO-TP header, whereas the 64-octet payload of a CAN FD frame allows a small
packet to be carried in a single Single-Frame. 6LoCAN therefore requires the CAN FD frame
format; see <xref target="can-fd-sec"/>.</t>

</section>
</section>
<section anchor="Spec-IPv6-over-CAN"><name>Specification of IPv6 over CAN</name>

<t>CAN has a small frame payload and therefore does not tolerate much protocol overhead.
This section specifies link-local IPv6 addresses and stateless IPv6 address autoconfiguration
(see <xref target="addr-conf-sec"/> and <xref target="link-local-addr-sec"/>), Neighbor Discovery (see <xref target="nd-sec"/>),
header compression (see <xref target="hc-sec"/>) and fragmentation (see <xref target="FAR-sec"/>), following the 6LoWPAN
work of <xref target="RFC4944"/> and <xref target="RFC6775"/> where it applies to CAN.</t>

<section anchor="can-fd-sec"><name>CAN FD Requirement</name>

<t>A 6LoCAN node MUST support the CAN FD frame format specified in <xref target="ISO11898-1"/>, and 6LoCAN
packets MUST be carried in CAN FD frames.</t>

<t>The reason is the payload size. A classical CAN frame carries at most 8 octets, of which the
ISO-TP header already takes 1 to 3; what remains cannot hold a compressed IPv6 header, so every
packet would have to be fragmented. A CAN FD frame carries up to 64 octets, which allows a
small packet to be carried complete in a single ISO-TP Single-Frame.</t>

<t>6LoCAN does not use classical CAN frames, and it does not use remote frames in either frame
format (see <xref target="link-layer-duplicate-address-detection"/>).</t>

</section>
<section anchor="IPv6-over-CAN-protocol-stack-sec"><name>Protocol Stack</name>

<t><xref target="IPv6-over-CAN-protocol-stack-fig"/> illustrates the IPv6-over-CAN protocol stack. Upper-layer protocols can be transport-layer protocols
(e.g., TCP and UDP), application-layer protocols, and other protocols capable of running on top of IPv6.</t>

<figure title="Protocol Stack for IPv6 over CAN" anchor="IPv6-over-CAN-protocol-stack-fig"><artwork><![CDATA[
+----------------------------------------+
|     Upper-Layer Protocols (CANopen)    |
+----------------------------------------+
|                 IPv6                   |
+----------------------------------------+
|   Adaptation Layer for IPv6 over CAN   |
+----------------------------------------+
|   ISO-TP     |   CAN Data Link Layer   |
+----------------------------------------+
|           CAN Physical Layer           |
+----------------------------------------+
]]></artwork></figure>

<t>The Adaptation Layer for IPv6 over CAN supports Neighbor Discovery, stateless address
autoconfiguration, header compression and fragmentation and reassembly.
Unlike the 6LoWPAN header compression of <xref target="RFC6282"/>, which compresses the IPv6 header and a
small set of next headers, SCHC compresses any header for which the context holds a rule, so
the compression is not limited to a fixed set of upper-layer protocols.</t>

</section>
<section anchor="node-addr-scheme"><name>CAN Frame Identifiers</name>

<t>This section provides information about the 14-bit node address to CAN identifier mapping.</t>

<t>Because CAN uses identifiers to identify the frame's content, an addressing scheme is introduced to map node addresses to identifiers.
Every node has a unique 14-bit address. This address is assigned either statically or randomly.
The addressing scheme uses the 29-bit extended identifier only. It is a combination of a source address, a destination address, and a multicast bit.
The multicast bit is at the highest bit-position, which causes the multicast traffic to have the lowest priority on the bus.</t>

<t>The address 0x3DFE is reserved for link-layer duplicate address detection, and address 0x3DF0 is reserved for the Ethernet border translator.
Addresses from 0x0100 to 0x3DEF are used as node addresses.
Other addresses (0x0000 to 0x00FF and 0x3DF0 to 0x3FFF) are reserved or used for special purposes.
Note that a lower address number has a higher priority on the bus.</t>

<t>The ranges listed in <xref target="tab-address-ranges"/> apply to node addresses, that is, to the source
address of every frame and to the destination address of unicast frames (see <xref target="unicast"/>).
They do not apply to the destination address of multicast frames: that field carries the
low-order 14 bits of the multicast group as specified in <xref target="multicast"/>, and the multicast bit
distinguishes such a value from a node address.</t>

<t>6LoCAN does not use the 11-bit standard identifiers. They may be used for other purposes.</t>

<texttable title="Node address ranges" anchor="tab-address-ranges">
      <ttcol align='left'>Address</ttcol>
      <ttcol align='left'>Description</ttcol>
      <c>0x3DFF - 0x3FFF</c>
      <c>Reserved</c>
      <c>0x3DFE</c>
      <c>LLDAD</c>
      <c>0x3DF1 - 0x3DFD</c>
      <c>Reserved</c>
      <c>0x3DF0</c>
      <c>Ethernet Translator</c>
      <c>0x0100 - 0x3DEF</c>
      <c>Node addresses</c>
      <c>0x0000 - 0x00FF</c>
      <c>Reserved</c>
</texttable>

<figure title="Frame Identifier" anchor="fig-identifier-layout"><artwork><![CDATA[
 0|0            1|1            2|
 0|1            4|5            8|
+-+--------------+--------------+
|M|     DEST     |     SRC      |
+-+--------------+--------------+
]]></artwork></figure>

<dl>
  <dt>M:</dt>
  <dd>
    <t>Multicast.</t>
  </dd>
  <dt>DEST:</dt>
  <dd>
    <t>Destination Address (14 bits).</t>
  </dd>
  <dt>SRC:</dt>
  <dd>
    <t>Source Address (14 bits).</t>
  </dd>
</dl>

<t>For example, a destination of 0x3055 and source address of 0x3AAF result in the following identifier:</t>

<figure title="Unicast frame identifier example" anchor="fig-unicast-id"><artwork><![CDATA[
 0|0            1|1            2|
 0|1            4|5            8|
+-+--------------+--------------+
|0|11000001010101|11101010101111|
+-+--------------+--------------+
]]></artwork></figure>

<t>A multicast group of 1 and a source address of 0x3AAF result in the following identifier:</t>

<figure title="Multicast frame identifier example" anchor="fig-multicast-id"><artwork><![CDATA[
 0|0            1|1            2|
 0|1            4|5            8|
+-+--------------+--------------+
|1|00000000000001|11101010101111|
+-+--------------+--------------+
]]></artwork></figure>

<section anchor="unicast"><name>Unicast Frame Identifier</name>

<t>For unicast packets, the multicast bit is set to zero, and the 14-bit source address is the address of the sender.
The 14-bit destination address of the receiver is discovered by IPv6 NDP defined in <xref target="RFC4861"/>.
Every node MUST be able to receive all frames targeting its address as the destination address.</t>

</section>
<section anchor="multicast"><name>Multicast Frame Identifier</name>

<t>For multicast packets, the multicast bit is set to one, and the 14-bit source address is the address of the sender.
The 14-bit destination address is the last 14 bits of the multicast group.
Every node MUST be able to receive all frames matching the last 14 bits of all joined multicast groups as the destination address.</t>

</section>
<section anchor="address-generation"><name>Node Address Generation</name>

<t>Every node has a 14-bit address. This address MUST be unique within the CAN bus segment.
The address can either be statically defined or assigned randomly.
For the random address assignment, the node tries randomly chosen addresses until the link-layer duplicate address detection succeeds.
The link-layer duplicate address detection prevents nodes from assigning an address already in use.</t>

</section>
<section anchor="link-layer-duplicate-address-detection"><name>Link-Layer Duplicate Address Detection</name>

<t>This section provides information about how to perform link-layer duplicate address detection (LLDAD).</t>

<t>LLDAD is introduced to prevent collisions of CAN identifiers and makes it possible to use random
address assignment with only 14 bits of address space.
To perform an LLDAD, a LLDAD-request is sent. If no DAD-response is received, the LLDAD is
considered successful and the node may start using the candidate address.</t>

<t>An LLDAD-request is a frame with a data length of zero whose destination address is the candidate
address and whose source address is a randomly chosen 14-bit value.
A DAD-response is a frame with a data length of zero whose destination address is the LLDAD
address (0x3DFE) and whose source address is the address that is already in use.</t>

<t>A data length of zero identifies both frames. A 6LoCAN packet always starts with an ISO-TP header
of at least one octet (see <xref target="sec-frame-format"/>), so a frame with no data cannot be mistaken for
one. Earlier versions of this specification used remote frames for the LLDAD-request. Remote
frames are not used, because the CAN FD frame format does not provide them and because support for
them in classical CAN controllers is uneven.</t>

<t>The random source address of an LLDAD-request distinguishes requests that are sent for the same
candidate address at the same time. It is not a node address, and the ranges in
<xref target="tab-address-ranges"/> do not apply to it.</t>

<t>A node MUST be able to receive frames whose destination address is the candidate address before it
sends the first LLDAD-request, and frames whose destination address is the LLDAD address for as
long as an LLDAD is in progress. The ability to receive frames addressed to the node address MUST
be retained for as long as the node uses that address, so that the node can answer later LLDAD
requests for it.</t>

<t>A node that receives an LLDAD-request whose destination address is an address it already uses MUST
send a DAD-response within 100 ms of receiving the request.</t>

<t>A node performing an LLDAD MUST wait at least 100 ms for a DAD-response. The 100 ms value allows a
responding node to be scheduled and to win bus arbitration on a loaded bus; it is not derived from
a CAN timing parameter.</t>

<t>While an LLDAD is in progress, a node that receives an LLDAD-request whose destination address is
its own candidate address, and whose source address differs from the one it used itself, MUST
abandon the candidate address. This resolves the case of two nodes probing the same address at the
same time, which neither would otherwise detect, because a DAD-response is sent only by a node that
already uses the address.</t>

<t>A node whose LLDAD fails, or that abandons a candidate address under the rule above, MUST select a
new candidate address and repeat the procedure. A node that selects candidate addresses randomly
MUST choose each new candidate independently from the node address range of
<xref target="tab-address-ranges"/>, and SHOULD delay the next attempt by a random interval of up to 100 ms, so
that two nodes that collided do not collide again. An implementation SHOULD limit the number of
attempts and report a failure to configure a node address rather than retrying indefinitely.</t>

<t><xref target="fig-dad-fail"/> shows a DAD Fail example where node A performs a LLDAD-request on address 0x3055 where this address is already in use by node B.</t>

<figure title="DAD Fail example" anchor="fig-dad-fail"><artwork><![CDATA[
    Node A            Node B
       |--LLDAD-request->|
       |                 |
       |<-LLDAD-response-|

LLDAD-request identifier (data length zero):
 0|0            1|1            2|
 0|1            4|5            8|
+-+--------------+--------------+
|0|11000001010101|    random    |
+-+--------------+--------------+

DAD-response identifier (data length zero):
 0|0            1|1            2|
 0|1            4|5            8|
+-+--------------+--------------+
|0|11110111111110|11000001010101|
+-+--------------+--------------+
]]></artwork></figure>

</section>
</section>
<section anchor="addr-conf-sec"><name>Stateless Address Autoconfiguration</name>

<t>This section defines how to obtain an IPv6 Interface Identifier.</t>

<t>The Interface Identifier for link-local addresses SHOULD be formed by taking the node address
and zero filling it to the left.
The resulting value is an IID in the sense of <xref target="RFC7136"/> and carries no embedded meaning
beyond the node address.
For example, an address of hexadecimal value 0x3AAF results in the following IID:</t>

<figure title="IID from Address 0x3AAF" anchor="fig-generate-iid"><artwork><![CDATA[
|0              1|1              3|3              4|4              6|
|0              5|6              1|2              7|8              3|
+----------------+----------------+----------------+----------------+
|0000000000000000|0000000000000000|0000000000000000|0011101010101111|
+----------------+----------------+----------------+----------------+
]]></artwork></figure>

<t>Deriving the IID from the node address allows a SCHC rule to elide it. <xref target="RFC8724"/> defines the
DEVIID and APPIID compression/decompression actions, which rebuild an interface identifier from
the device identifier of the link. On a 6LoCAN segment that identifier is the node address,
which the receiver already has from the CAN frame identifier of the frame it is processing.
An IID that cannot be rebuilt in this way has to be sent as part of the compression residue,
which costs 8 octets in every packet that carries it. On a link whose frames carry at most
64 octets of payload, this is the difference between a usefully compressed header and an
uncompressed one.</t>

<t><xref target="RFC8064"/> recommends that stable IIDs be generated with the method of <xref target="RFC7217"/> rather
than from a link-layer address, and <xref target="RFC8065"/> gives the privacy advice that an
adaptation-layer specification such as this one is expected to follow. The link-local IID
defined above is a deliberate deviation from that recommendation, made for the header
compression reason given above; its privacy properties are discussed in
<xref target="security-considerations"/>.
For addresses other than link-local addresses, a 6LoCAN node SHOULD generate IIDs as
described in <xref target="RFC7217"/>. Such IIDs cannot be rebuilt with DEVIID or APPIID and are carried
as part of the compression residue.</t>

</section>
<section anchor="link-local-addr-sec"><name>IPv6 Link-Local Address</name>

<t>The IPv6 link-local address <xref target="RFC4291"/> for a 6LoCAN interface is formed by appending the Interface Identifier, as defined above, to the prefix FE80::/64.</t>

<figure title="Link-Local address from IID" anchor="fig-link-local-address"><artwork><![CDATA[
  10 bits            54 bits                  64 bits
+----------+-----------------------+----------------------------+
|1111111010|         (zeros)       |    Interface Identifier    |
+----------+-----------------------+----------------------------+
]]></artwork></figure>

</section>
<section anchor="nd-sec"><name>Neighbor Discovery</name>

<t>A 6LoCAN bus segment is a single link. Every node attached to the segment can reach every
other node of that segment directly, and nodes do not forward packets between each other
within a segment.</t>

<t>Neighbor Discovery for IPv6 <xref target="RFC4861"/> is used for address resolution and for neighbor
unreachability detection. The Source/Target Link-Layer Address option carries the 14-bit
node address in the form specified in <xref target="unicasting-sec"/>.</t>

<t>The Neighbor Discovery optimizations for 6LoWPANs <xref target="RFC6775"/> <xref target="RFC8505"/> address
route-over, multi-hop topologies in which multicast is expensive or unreliable.
Because a 6LoCAN segment is a single link and CAN provides a multicast mechanism
(see <xref target="multicast"/>), these optimizations are not required within a segment.
Connectivity between a 6LoCAN segment and other links is provided by the Ethernet Border
Translator (see <xref target="translator-sec"/>) rather than by a 6LBR.</t>

</section>
<section anchor="hc-sec"><name>Header Compression</name>

<t>6LoCAN uses Static Context Header Compression (SCHC) <xref target="RFC8724"/> to compress headers.
A 6LoCAN node MUST implement the SCHC compression and decompression of <xref target="RFC8724"/>.</t>

<t>Only the compression part of <xref target="RFC8724"/> is used. The SCHC fragmentation and reassembly
mechanism is not used; fragmentation is provided by ISO-TP, for the reasons given in
<xref target="FAR-sec"/>.</t>

<t>Earlier versions of this specification used the 6LoWPAN header compression of <xref target="RFC6282"/>.
SCHC is used instead because it compresses the headers of the upper-layer protocols that a
6LoCAN node actually carries, not only the IPv6 header, and because a rule set can be written
for the small and largely static set of flows that an installation of the kind described in
<xref target="applicability-sec"/> runs. <xref target="RFC6282"/> is not used by this specification.</t>

<section anchor="schc-context-sec"><name>SCHC Context</name>

<t>SCHC compresses a header by matching it against a rule in a context that both ends hold before
a packet is sent. On a 6LoCAN segment the context is a property of the installation: the set of
flows is fixed when the equipment is commissioned.</t>

<t>How the context is provisioned is out of scope for this document. It MAY be built into the
nodes, provisioned together with the node addresses, or distributed by the Ethernet Border
Translator of <xref target="translator-sec"/>.</t>

<t>All nodes on a bus segment, and the Ethernet Border Translator, MUST hold the same context.
6LoCAN provides no mechanism to negotiate or to verify a context, and a node that decompresses
a packet with a rule other than the one used to compress it will deliver a corrupted packet.</t>

</section>
<section anchor="schc-ruleid-sec"><name>Rule Identifiers</name>

<t>The Rule ID size is a parameter of the context. For 6LoCAN it MUST be 8 bits.</t>

<t>An 8-bit Rule ID costs one octet in every compressed packet and allows 256 rules in a segment,
which is more than the number of distinct flows expected in the installations of
<xref target="applicability-sec"/>. A smaller Rule ID would not save an octet, because the compression
residue is octet-aligned in the frame layout of <xref target="sec-frame-format"/>.</t>

<t>The assignment of rules to Rule IDs is part of the context and therefore out of scope.</t>

</section>
<section anchor="schc-15dot4-sec"><name>Relationship to SCHC over IEEE 802.15.4</name>

<t><xref target="I-D.ietf-6lo-schc-15dot4"/> profiles SCHC for IEEE 802.15.4. The parts of that profile that
concern the compression of IPv6 and UDP headers apply unchanged to 6LoCAN. The parts that
concern SCHC fragmentation do not apply, because 6LoCAN fragments with ISO-TP.</t>

</section>
</section>
<section anchor="mtu-sec"><name>Maximum Transmission Unit</name>

<t>IPv6 requires every link to have an MTU of 1280 octets or greater <xref target="RFC8200"/>.
The subset of ISO-TP used in this document (see <xref target="FAR-sec"/>) carries up to 4095 octets
per packet and therefore satisfies this requirement.</t>

<t>The MTU of a 6LoCAN bus segment MUST be at least 1280 octets and MUST NOT exceed
4095 octets. Implementations SHOULD use an MTU of 1280 octets.
All nodes attached to the same bus segment MUST use the same MTU; 6LoCAN provides no
mechanism to negotiate the MTU on a per-node basis.</t>

<t>A larger MTU increases the reassembly buffer that every receiving node has to provide
and the number of CAN frames that a single IPv6 packet occupies.
Because ISO-TP transfers are interleaved with other bus traffic at frame granularity,
a long transfer does not block frames of higher priority, but it does increase the
latency of traffic whose identifiers have a lower priority than the transfer.
An MTU larger than 1280 octets SHOULD therefore be used only where the resulting bus
occupancy is acceptable for the application.</t>

</section>
<section anchor="FAR-sec"><name>Fragmentation and Reassembly Considerations</name>

<t>A subset of ISO-TP (ISO 15765-2) is used to fragment and reassemble the packets.
This subset of ISO-TP can send packets with a payload size of up to 4095 octets, enough for IPv6 minimum MTU size of 1280 octets.
ISO-TP is designed for CAN and its small payload data size and therefore preferred over <xref target="RFC4944"/> fragmentation.</t>

<t>The 6LoWPAN fragmentation would use more than the half of the available payload for the fragmentation headers.
This fact prevents 6LoWPAN fragmentation from being used for 6LoCAN.</t>

<t><xref target="RFC8724"/> also defines a fragmentation and reassembly mechanism. 6LoCAN does not use it.
ISO-TP is the mechanism that CAN deployments already use: it is specified for CAN in
<xref target="ISO15765-2"/>, it is widely implemented in CAN controllers and protocol stacks, and its flow
control and timeout behaviour are defined in terms of CAN. Using it lets a 6LoCAN node share
the segmentation implementation that the installation already contains.</t>

</section>
<section anchor="addr-map-sec"><name>IPv6 Address Mapping</name>

<section anchor="unicasting-sec"><name>Unicast Address Mapping</name>

<t>The address resolution procedure for mapping IPv6 non-multicast addresses into CAN Data link layer Addresses (Node addresses) follows the general description in
Sections 4.6.1 and 7.2 of <xref target="RFC4861"/>, unless otherwise specified.</t>

<t>The Source/Target Link-Layer Address option has the following form when the addresses are 14-bit CAN Data Link Layer Addresses.</t>

<figure title="IPv6 Unicast Address Mapping" anchor="unicasting-fig"><artwork><![CDATA[
 0                   1
 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|      Type     |   Length=1    |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|                               |
+-     Padding (all zeros)     -+
|                               |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|Rsv| CAN Data Link-Layer Addr. |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
]]></artwork></figure>

<t>Option fields:</t>

<dl indent="4">
  <dt>Type:</dt>
  <dd>
    <t>1: This is for the Source Link-Layer Address.
2: This is for the Target Link-Layer Address.</t>
  </dd>
  <dt>Length:</dt>
  <dd>
    <t>This is the length of this option (including the Type and Length fields) in units of 8 octets. The value of this field is 1 for 14-bit CAN Data Link Layer addresses.</t>
  </dd>
  <dt>Rsv:</dt>
  <dd>
    <t>Reserved. 2 bits. These bits MUST be set to zero by the sender and MUST be ignored by the
receiver.</t>
  </dd>
  <dt>CAN Data Link-Layer Address:</dt>
  <dd>
    <t>The 14-bit node address of the sender (Source Link-Layer Address) or of the target
(Target Link-Layer Address).</t>
  </dd>
</dl>

</section>
<section anchor="multicast-map-sec"><name>Multicast Address Mapping</name>

<t>CAN has no link-layer multicast address. An IPv6 multicast address is therefore mapped
directly onto a frame identifier: the multicast bit is set and the destination field carries
the low-order 14 bits of the multicast group, as specified in <xref target="multicast"/>.
No link-layer address resolution is performed for a multicast destination, and the
Source/Target Link-Layer Address option is not used for one.</t>

<t>Because the CAN data link layer does not provide multicast, ISO-TP is used for multicast
frames without its flow control mechanism; see <xref target="iso-tp-overview"/> and <xref target="FAR-sec"/>.</t>

</section>
</section>
<section anchor="sec-frame-format"><name>6LoCAN Frame Format</name>

<t>This section provides information about data arrangement in the frame data field.</t>

<t>The first octets of a CAN frame always contain the ISO-TP header. In the first frame of a packet
the ISO-TP header is followed by the SCHC packet of <xref target="RFC8724"/>: a Rule ID, then the compression
residue, then the payload. The SCHC packet may be spread over several frames.</t>

<figure title="6LoCAN Frame Format" anchor="fig-frame-format"><artwork><![CDATA[
+-----------------------------------------+
| ISO-TP Header (1-3 octets)              |
+-----------------------------------------+
| SCHC Rule ID (1 octet)                  |
+-----------------------------------------+
| Compression Residue (0 or more octets)  |
+-----------------------------------------+
| Payload                                 |
+-----------------------------------------+
]]></artwork></figure>

<t>The Rule ID is one octet (see <xref target="schc-ruleid-sec"/>). The size of the compression residue depends
on the rule that matched: it is empty when the rule elides every field, and otherwise it carries
the fields that the rule sends, in the order in which the rule lists them. The residue is padded
at its end so that the payload starts on an octet boundary, as described in Section 5 of
<xref target="RFC8724"/>; for 6LoCAN the L2 word is one octet.</t>

<t>Packets with a destination or source address of the 0x3DF0 (Translator address) carry the Ethernet MAC address inline directly after the ISO-TP Header.
For packets destined for the translator, it is the destination MAC address, and for packets originated by the translator, it is the source MAC address.</t>

<figure title="6LoCAN Translator Frame Format" anchor="fig-frame-format-translator"><artwork><![CDATA[
+-----------------------------------------+
| ISO-TP Header (1-3 octets)              |
+-----------------------------------------+
| Ethernet MAC Address (48 bits)          |
+-----------------------------------------+
| SCHC Rule ID (1 octet)                  |
+-----------------------------------------+
| Compression Residue (0 or more octets)  |
+-----------------------------------------+
| Payload                                 |
+-----------------------------------------+
]]></artwork></figure>

</section>
</section>
<section anchor="translator-sec"><name>Ethernet Border Translator</name>

<t>This section specifies how 6LoCAN packets are translated to and from Ethernet frames.</t>

<t>The Ethernet Border Translator connects 6LoCAN bus-segments either to other 6LoCAN bus-segments or other technologies.
Ethernet is a widely used technology that provides enough bandwidth to connect several 6LoCAN segments.
A mechanism like the 6LBR is not necessary because there is no routing on 6LoCAN segments.
To provide routing or switching capabilities, the Ethernet Border Translator connects a 6LoCAN network to such devices via Ethernet.</t>

<t>Bus segments MUST NOT have more than one translator. The translator has a fixed node address (0x3DF0) and a range of Ethernet MAC addresses.
Every packet sent to this node address or any multicast address is forwarded to Ethernet.
Every Ethernet frame matching the MAC address range and every multicast Ethernet frame is forwarded to the 6LoCAN bus-segment.</t>

<t>For translating a 6LoCAN packet to an Ethernet frame, the source address is extended with a 34 bits MAC address prefix, and the SCHC-compressed headers are decompressed.
The 34 bits prefix MUST be chosen in a way that the resulting 48-bit MAC address forms a locally administered address that is unique on the link.
The destination MAC is carried in-line before the compressed IPv6 header (see <xref target="sec-frame-format"/>, <xref target="fig-frame-format-translator"/>).
ICMPv6 messages MUST be checked for Link-Layer Address Options (LLAO), and if an LLAO is present, it MUST be changed to the extended link-layer address.
For translating Ethernet frames to 6LoCAN packets, the source MAC address is carried in-line, the destination node address is the last 14 bits of the MAC address, and the headers are compressed using SCHC.</t>

<t>The Neighbor Caches of the networking stack must be able to store link-layer addresses with a size of 14 and 48 bits.</t>

<t>For multicast Ethernet frames, the last 14 bits of the multicast group is the destination address, and the multicast bit is set. The destination address MAY also be reconstructed from the destination multicast address.
The destination Ethernet MAC address is formed from the destination IP address as described in <xref target="RFC2464"/> section 7.</t>

<t>If the translator includes a network stack, the translator MUST NOT use a MAC address within the ranges used for translation, with the following exception:
The translator MAY use the extended MAC address that corresponds to the translator node address.</t>

</section>
<section anchor="connection-scenario-sec"><name>Internet Connectivity Scenarios</name>

<t>This section shows an example of a 6LoCAN segment connected to an Ethernet network and
examples of the address translations specified in <xref target="translator-sec"/>.</t>

<t><xref target="fig-translator-setup"/> shows an example setup of a 6LoCAN segment connected to an Ethernet network.</t>

<t><xref target="fig-unicast-mac-translation"/> shows a translation from Ethernet MAC to CAN identifier.
The source (src) MAC address is carried in-line in the CAN frame data.
The 34-bit MAC address prefix for this example is 02:00:5E:10 followed by two zero bits,
written as 02:00:5E:10:00/34.</t>

<figure title="Example address translation from Ethernet MAC to CAN identifier." anchor="fig-unicast-mac-translation"><artwork><![CDATA[
|0                            4|4                              9
|0                            7|8                              5
+------------------------------+-------------------------------+
| dest MAC (02:00:5E:10:30:55) |  src MAC (02:00:5E:10:00:FF)  |
+------------------------------+-------------------------------+
                          Ethernet MAC

 0|0            1|1            2|
 0|1            4|5            8|
+-+--------------+--------------+
|0|dest (0x3055) | src (0x3DF0) |
+-+--------------+--------------+
            CAN identifier
]]></artwork></figure>

<t><xref target="fig-multicast-mac-translation"/> shows a translation from a multicast Ethernet MAC to CAN identifier.
The source MAC address is carried in-line in the CAN frame data.</t>

<figure title="Example address translation from Ethernet to CAN for multicast frames" anchor="fig-multicast-mac-translation"><artwork><![CDATA[
|0                            4|4                             9|
|0                            7|8                             5|
+------------------------------+-------------------------------+
| dest MAC (33:33:00:01:00:01) |  src MAC (02:00:5E:10:00:FF)  |
+------------------------------+-------------------------------+
                          Ethernet MAC

 0|0            1|1            2|
 0|1            4|5            8|
+-+--------------+--------------+
|1|dest (0x0001) | src (0x3DF0) |
+-+--------------+--------------+
            CAN identifier
]]></artwork></figure>

<t><xref target="fig-unicast-id-translation"/> shows a translation CAN identifier to Ethernet MAC.
The destination (dest) MAC address is carried inline in the CAN frame data.
The 34-bit MAC address prefix for this example is 02:00:5E:10 followed by two zero bits,
written as 02:00:5E:10:00/34.</t>

<figure title="Example address translation from CAN identifier to Ethernet MAC for unicast frames" anchor="fig-unicast-id-translation"><artwork><![CDATA[
 0|0            1|1            2|
 0|1            4|5            8|
+-+--------------+--------------+
|0|dest (0x3DF0) | src (0x3055) |
+-+--------------+--------------+
            CAN identifier
|0                            4|4                             9|
|0                            7|8                             5|
+------------------------------+-------------------------------+
| dest MAC (02:00:5E:10:00:FF) |  src MAC (02:00:5E:10:30:55)  |
+------------------------------+-------------------------------+
                          Ethernet MAC
]]></artwork></figure>

<figure title="Example setup with Ethernet Border Translator" anchor="fig-translator-setup"><artwork><![CDATA[
                                          +-----+  +-----+
                                          |CAN  |  |CAN  |  ...
                                          |node |  |node |
                                          +--+--+  +--+--+
+--------+---+     +---+----------+---+      |        |
|        |   |     |   |Ethernet  |   |      |        |
| Switch |ETH|<--->|ETH|Border    |CAN|------+--------+---- ...
|        |   |     |   |Translator|   |
+--------+---+     +---+----------+---+
]]></artwork></figure>

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

<t>The IANA considerations for this document have not yet been determined.
A future revision will specify the registry actions required by this
document, or state that this document has no IANA actions.</t>

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

<t>CAN itself provides no security services at the link layer: it has no authentication, no
integrity protection and no confidentiality, and any node on the bus can transmit any frame
identifier. This document adds none.
Traffic on the bus can therefore be intercepted, spoofed, or destroyed by any node attached
to the segment.
For confidentiality and integrity, mechanisms like TLS or IPsec need to be applied.</t>

<t>The link-local IID defined in <xref target="addr-conf-sec"/> is derived from the node address and therefore
exposes that address in every link-local IPv6 address of the node. Within a bus segment this
discloses nothing new, because the node address appears in the CAN frame identifier of every
frame the node sends or receives. It would become a concern if the node address were also
used to form addresses that are routable beyond the segment: such an address would remain
stable for as long as the node keeps its node address and would allow the node to be tracked
across networks, which is what <xref target="RFC8064"/> and <xref target="RFC7217"/> are intended to prevent.
For this reason the node address is used only for link-local IIDs.</t>

<t>A 14-bit node address space holds 16384 values and can be scanned exhaustively in a short
time. The size of the address space therefore provides no protection against discovery of
the nodes present on a bus segment.</t>

<t><xref target="RFC8065"/> discusses how privacy threats apply to IPv6-over-foo adaptation layers and what
such a specification is expected to say about them. Of the threats it lists, correlation of
activity over time and location tracking are the ones that the node-address-derived
interface identifier of <xref target="addr-conf-sec"/> bears on, and they are the reason that identifier
is confined to link-local addresses. Address scanning is not mitigated, as noted above.</t>

</section>


  </middle>

  <back>


<references title='References' anchor="sec-combined-references">

    <references title='Normative References' anchor="sec-normative-references">



<reference anchor="RFC2464">
  <front>
    <title>Transmission of IPv6 Packets over Ethernet Networks</title>
    <author fullname="M. Crawford" initials="M." surname="Crawford"/>
    <date month="December" year="1998"/>
    <abstract>
      <t>This document specifies the frame format for transmission of IPv6 packets and the method of forming IPv6 link-local addresses and statelessly autoconfigured addresses on Ethernet networks. It also specifies the content of the Source/Target Link-layer Address option used in Router Solicitation, Router Advertisement, Neighbor Solicitation, Neighbor Advertisement and Redirect messages when those messages are transmitted on an Ethernet. [STANDARDS-TRACK]</t>
    </abstract>
  </front>
  <seriesInfo name="RFC" value="2464"/>
  <seriesInfo name="DOI" value="10.17487/RFC2464"/>
</reference>
<reference anchor="RFC4291">
  <front>
    <title>IP Version 6 Addressing Architecture</title>
    <author fullname="R. Hinden" initials="R." surname="Hinden"/>
    <author fullname="S. Deering" initials="S." surname="Deering"/>
    <date month="February" year="2006"/>
    <abstract>
      <t>This specification defines the addressing architecture of the IP Version 6 (IPv6) protocol. The document includes the IPv6 addressing model, text representations of IPv6 addresses, definition of IPv6 unicast addresses, anycast addresses, and multicast addresses, and an IPv6 node's required addresses.</t>
      <t>This document obsoletes RFC 3513, "IP Version 6 Addressing Architecture". [STANDARDS-TRACK]</t>
    </abstract>
  </front>
  <seriesInfo name="RFC" value="4291"/>
  <seriesInfo name="DOI" value="10.17487/RFC4291"/>
</reference>
<reference anchor="RFC4944">
  <front>
    <title>Transmission of IPv6 Packets over IEEE 802.15.4 Networks</title>
    <author fullname="G. Montenegro" initials="G." surname="Montenegro"/>
    <author fullname="N. Kushalnagar" initials="N." surname="Kushalnagar"/>
    <author fullname="J. Hui" initials="J." surname="Hui"/>
    <author fullname="D. Culler" initials="D." surname="Culler"/>
    <date month="September" year="2007"/>
    <abstract>
      <t>This document describes the frame format for transmission of IPv6 packets and the method of forming IPv6 link-local addresses and statelessly autoconfigured addresses on IEEE 802.15.4 networks. Additional specifications include a simple header compression scheme using shared context and provisions for packet delivery in IEEE 802.15.4 meshes. [STANDARDS-TRACK]</t>
    </abstract>
  </front>
  <seriesInfo name="RFC" value="4944"/>
  <seriesInfo name="DOI" value="10.17487/RFC4944"/>
</reference>
<reference anchor="RFC4861">
  <front>
    <title>Neighbor Discovery for IP version 6 (IPv6)</title>
    <author fullname="T. Narten" initials="T." surname="Narten"/>
    <author fullname="E. Nordmark" initials="E." surname="Nordmark"/>
    <author fullname="W. Simpson" initials="W." surname="Simpson"/>
    <author fullname="H. Soliman" initials="H." surname="Soliman"/>
    <date month="September" year="2007"/>
    <abstract>
      <t>This document specifies the Neighbor Discovery protocol for IP Version 6. IPv6 nodes on the same link use Neighbor Discovery to discover each other's presence, to determine each other's link-layer addresses, to find routers, and to maintain reachability information about the paths to active neighbors. [STANDARDS-TRACK]</t>
    </abstract>
  </front>
  <seriesInfo name="RFC" value="4861"/>
  <seriesInfo name="DOI" value="10.17487/RFC4861"/>
</reference>
<reference anchor="RFC4862">
  <front>
    <title>IPv6 Stateless Address Autoconfiguration</title>
    <author fullname="S. Thomson" initials="S." surname="Thomson"/>
    <author fullname="T. Narten" initials="T." surname="Narten"/>
    <author fullname="T. Jinmei" initials="T." surname="Jinmei"/>
    <date month="September" year="2007"/>
    <abstract>
      <t>This document specifies the steps a host takes in deciding how to autoconfigure its interfaces in IP version 6. The autoconfiguration process includes generating a link-local address, generating global addresses via stateless address autoconfiguration, and the Duplicate Address Detection procedure to verify the uniqueness of the addresses on a link. [STANDARDS-TRACK]</t>
    </abstract>
  </front>
  <seriesInfo name="RFC" value="4862"/>
  <seriesInfo name="DOI" value="10.17487/RFC4862"/>
</reference>
<reference anchor="RFC6775">
  <front>
    <title>Neighbor Discovery Optimization for IPv6 over Low-Power Wireless Personal Area Networks (6LoWPANs)</title>
    <author fullname="Z. Shelby" initials="Z." role="editor" surname="Shelby"/>
    <author fullname="S. Chakrabarti" initials="S." surname="Chakrabarti"/>
    <author fullname="E. Nordmark" initials="E." surname="Nordmark"/>
    <author fullname="C. Bormann" initials="C." surname="Bormann"/>
    <date month="November" year="2012"/>
    <abstract>
      <t>The IETF work in IPv6 over Low-power Wireless Personal Area Network (6LoWPAN) defines 6LoWPANs such as IEEE 802.15.4. This and other similar link technologies have limited or no usage of multicast signaling due to energy conservation. In addition, the wireless network may not strictly follow the traditional concept of IP subnets and IP links. IPv6 Neighbor Discovery was not designed for non- transitive wireless links, as its reliance on the traditional IPv6 link concept and its heavy use of multicast make it inefficient and sometimes impractical in a low-power and lossy network. This document describes simple optimizations to IPv6 Neighbor Discovery, its addressing mechanisms, and duplicate address detection for Low- power Wireless Personal Area Networks and similar networks. The document thus updates RFC 4944 to specify the use of the optimizations defined here. [STANDARDS-TRACK]</t>
    </abstract>
  </front>
  <seriesInfo name="RFC" value="6775"/>
  <seriesInfo name="DOI" value="10.17487/RFC6775"/>
</reference>
<reference anchor="RFC7136">
  <front>
    <title>Significance of IPv6 Interface Identifiers</title>
    <author fullname="B. Carpenter" initials="B." surname="Carpenter"/>
    <author fullname="S. Jiang" initials="S." surname="Jiang"/>
    <date month="February" year="2014"/>
    <abstract>
      <t>The IPv6 addressing architecture includes a unicast interface identifier that is used in the creation of many IPv6 addresses. Interface identifiers are formed by a variety of methods. This document clarifies that the bits in an interface identifier have no meaning and that the entire identifier should be treated as an opaque value. In particular, RFC 4291 defines a method by which the Universal and Group bits of an IEEE link-layer address are mapped into an IPv6 unicast interface identifier. This document clarifies that those two bits are significant only in the process of deriving interface identifiers from an IEEE link-layer address, and it updates RFC 4291 accordingly.</t>
    </abstract>
  </front>
  <seriesInfo name="RFC" value="7136"/>
  <seriesInfo name="DOI" value="10.17487/RFC7136"/>
</reference>
<reference anchor="RFC7217">
  <front>
    <title>A Method for Generating Semantically Opaque Interface Identifiers with IPv6 Stateless Address Autoconfiguration (SLAAC)</title>
    <author fullname="F. Gont" initials="F." surname="Gont"/>
    <date month="April" year="2014"/>
    <abstract>
      <t>This document specifies a method for generating IPv6 Interface Identifiers to be used with IPv6 Stateless Address Autoconfiguration (SLAAC), such that an IPv6 address configured using this method is stable within each subnet, but the corresponding Interface Identifier changes when the host moves from one network to another. This method is meant to be an alternative to generating Interface Identifiers based on hardware addresses (e.g., IEEE LAN Media Access Control (MAC) addresses), such that the benefits of stable addresses can be achieved without sacrificing the security and privacy of users. The method specified in this document applies to all prefixes a host may be employing, including link-local, global, and unique-local prefixes (and their corresponding addresses).</t>
    </abstract>
  </front>
  <seriesInfo name="RFC" value="7217"/>
  <seriesInfo name="DOI" value="10.17487/RFC7217"/>
</reference>
<reference anchor="RFC8064">
  <front>
    <title>Recommendation on Stable IPv6 Interface Identifiers</title>
    <author fullname="F. Gont" initials="F." surname="Gont"/>
    <author fullname="A. Cooper" initials="A." surname="Cooper"/>
    <author fullname="D. Thaler" initials="D." surname="Thaler"/>
    <author fullname="W. Liu" initials="W." surname="Liu"/>
    <date month="February" year="2017"/>
    <abstract>
      <t>This document changes the recommended default Interface Identifier (IID) generation scheme for cases where Stateless Address Autoconfiguration (SLAAC) is used to generate a stable IPv6 address. It recommends using the mechanism specified in RFC 7217 in such cases, and recommends against embedding stable link-layer addresses in IPv6 IIDs. It formally updates RFC 2464, RFC 2467, RFC 2470, RFC 2491, RFC 2492, RFC 2497, RFC 2590, RFC 3146, RFC 3572, RFC 4291, RFC 4338, RFC 4391, RFC 5072, and RFC 5121. This document does not change any existing recommendations concerning the use of temporary addresses as specified in RFC 4941.</t>
    </abstract>
  </front>
  <seriesInfo name="RFC" value="8064"/>
  <seriesInfo name="DOI" value="10.17487/RFC8064"/>
</reference>
<reference anchor="RFC8065">
  <front>
    <title>Privacy Considerations for IPv6 Adaptation-Layer Mechanisms</title>
    <author fullname="D. Thaler" initials="D." surname="Thaler"/>
    <date month="February" year="2017"/>
    <abstract>
      <t>This document discusses how a number of privacy threats apply to technologies designed for IPv6 over various link-layer protocols, and it provides advice to protocol designers on how to address such threats in adaptation-layer specifications for IPv6 over such links.</t>
    </abstract>
  </front>
  <seriesInfo name="RFC" value="8065"/>
  <seriesInfo name="DOI" value="10.17487/RFC8065"/>
</reference>
<reference anchor="RFC8200">
  <front>
    <title>Internet Protocol, Version 6 (IPv6) Specification</title>
    <author fullname="S. Deering" initials="S." surname="Deering"/>
    <author fullname="R. Hinden" initials="R." surname="Hinden"/>
    <date month="July" year="2017"/>
    <abstract>
      <t>This document specifies version 6 of the Internet Protocol (IPv6). It obsoletes RFC 2460.</t>
    </abstract>
  </front>
  <seriesInfo name="STD" value="86"/>
  <seriesInfo name="RFC" value="8200"/>
  <seriesInfo name="DOI" value="10.17487/RFC8200"/>
</reference>
<reference anchor="RFC8505">
  <front>
    <title>Registration Extensions for IPv6 over Low-Power Wireless Personal Area Network (6LoWPAN) Neighbor Discovery</title>
    <author fullname="P. Thubert" initials="P." role="editor" surname="Thubert"/>
    <author fullname="E. Nordmark" initials="E." surname="Nordmark"/>
    <author fullname="S. Chakrabarti" initials="S." surname="Chakrabarti"/>
    <author fullname="C. Perkins" initials="C." surname="Perkins"/>
    <date month="November" year="2018"/>
    <abstract>
      <t>This specification updates RFC 6775 -- the Low-Power Wireless Personal Area Network (6LoWPAN) Neighbor Discovery specification -- to clarify the role of the protocol as a registration technique and simplify the registration operation in 6LoWPAN routers, as well as to provide enhancements to the registration capabilities and mobility detection for different network topologies, including the Routing Registrars performing routing for host routes and/or proxy Neighbor Discovery in a low-power network.</t>
    </abstract>
  </front>
  <seriesInfo name="RFC" value="8505"/>
  <seriesInfo name="DOI" value="10.17487/RFC8505"/>
</reference>
<reference anchor="RFC8724">
  <front>
    <title>SCHC: Generic Framework for Static Context Header Compression and Fragmentation</title>
    <author fullname="A. Minaburo" initials="A." surname="Minaburo"/>
    <author fullname="L. Toutain" initials="L." surname="Toutain"/>
    <author fullname="C. Gomez" initials="C." surname="Gomez"/>
    <author fullname="D. Barthel" initials="D." surname="Barthel"/>
    <author fullname="JC. Zuniga" initials="JC." surname="Zuniga"/>
    <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="I-D.ietf-6lo-schc-15dot4">
   <front>
      <title>Transmission of SCHC-compressed packets over IEEE 802.15.4 networks</title>
      <author fullname="Carles Gomez" initials="C." surname="Gomez">
         <organization>UPC</organization>
      </author>
      <author fullname="Ana Minaburo" initials="A." surname="Minaburo">
         <organization>Consultant</organization>
      </author>
      <date day="31" month="October" year="2026"/>
      <abstract>
	 <t>   A framework called Static Context Header Compression and
   fragmentation (SCHC) has been designed with the primary goal of
   supporting IPv6 over Low Power Wide Area Network (LPWAN) technologies
   [RFC8724].  One of the SCHC components is a header compression
   mechanism.  If used properly, SCHC header compression allows a
   greater compression ratio than that achievable with traditional
   6LoWPAN header compression [RFC6282].  For this reason, it may make
   sense to use SCHC header compression in some 6LoWPAN environments,
   including IEEE 802.15.4 networks.  This document specifies how a
   SCHC-compressed packet can be carried over IEEE 802.15.4 networks.
   The document also enables the transmission of SCHC-compressed UDP/
   CoAP headers over 6LoWPAN-compressed IPv6 packets.

	 </t>
      </abstract>
   </front>
   <seriesInfo name="Internet-Draft" value="draft-ietf-6lo-schc-15dot4-14"/>
   
</reference>



    </references>

    <references title='Informative References' anchor="sec-informative-references">



<reference anchor="RFC2119">
  <front>
    <title>Key words for use in RFCs to Indicate Requirement Levels</title>
    <author fullname="S. Bradner" initials="S." surname="Bradner"/>
    <date month="March" year="1997"/>
    <abstract>
      <t>In many standards track documents several words are used to signify the requirements in the specification. These words are often capitalized. This document defines these words as they should be interpreted in IETF documents. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements.</t>
    </abstract>
  </front>
  <seriesInfo name="BCP" value="14"/>
  <seriesInfo name="RFC" value="2119"/>
  <seriesInfo name="DOI" value="10.17487/RFC2119"/>
</reference>
<reference anchor="RFC6282">
  <front>
    <title>Compression Format for IPv6 Datagrams over IEEE 802.15.4-Based Networks</title>
    <author fullname="J. Hui" initials="J." role="editor" surname="Hui"/>
    <author fullname="P. Thubert" initials="P." surname="Thubert"/>
    <date month="September" year="2011"/>
    <abstract>
      <t>This document updates RFC 4944, "Transmission of IPv6 Packets over IEEE 802.15.4 Networks". This document specifies an IPv6 header compression format for IPv6 packet delivery in Low Power Wireless Personal Area Networks (6LoWPANs). The compression format relies on shared context to allow compression of arbitrary prefixes. How the information is maintained in that shared context is out of scope. This document specifies compression of multicast addresses and a framework for compressing next headers. UDP header compression is specified within this framework. [STANDARDS-TRACK]</t>
    </abstract>
  </front>
  <seriesInfo name="RFC" value="6282"/>
  <seriesInfo name="DOI" value="10.17487/RFC6282"/>
</reference>
<reference anchor="RFC4919">
  <front>
    <title>IPv6 over Low-Power Wireless Personal Area Networks (6LoWPANs): Overview, Assumptions, Problem Statement, and Goals</title>
    <author fullname="N. Kushalnagar" initials="N." surname="Kushalnagar"/>
    <author fullname="G. Montenegro" initials="G." surname="Montenegro"/>
    <author fullname="C. Schumacher" initials="C." surname="Schumacher"/>
    <date month="August" year="2007"/>
    <abstract>
      <t>This document describes the assumptions, problem statement, and goals for transmitting IP over IEEE 802.15.4 networks. The set of goals enumerated in this document form an initial set only. This memo provides information for the Internet community.</t>
    </abstract>
  </front>
  <seriesInfo name="RFC" value="4919"/>
  <seriesInfo name="DOI" value="10.17487/RFC4919"/>
</reference>
<reference anchor="RFC8174">
  <front>
    <title>Ambiguity of Uppercase vs Lowercase in RFC 2119 Key Words</title>
    <author fullname="B. Leiba" initials="B." surname="Leiba"/>
    <date month="May" year="2017"/>
    <abstract>
      <t>RFC 2119 specifies common key words that may be used in protocol specifications. This document aims to reduce the ambiguity by clarifying that only UPPERCASE usage of the key words have the defined special meanings.</t>
    </abstract>
  </front>
  <seriesInfo name="BCP" value="14"/>
  <seriesInfo name="RFC" value="8174"/>
  <seriesInfo name="DOI" value="10.17487/RFC8174"/>
</reference>

<reference anchor="I-D.wachter-6lo-can">
   <front>
      <title>IPv6 over Controller Area Network</title>
      <author fullname="Alexander Wachter" initials="A." surname="Wachter">
         <organization>Graz University of Technology</organization>
      </author>
      <date day="27" month="February" year="2020"/>
      <abstract>
	 <t>   Controller Area Network (CAN) is a fieldbus initially designed for
   automotive applications.  It is a multi-master bus with 11-bit or
   29-bit frame identifiers.  The CAN standard (ISO 11898 series)
   defines the physical and data-link layer.  This document describes
   how to transfer IPv6 packets over CAN using ISO-TP, a dedicated
   addressing scheme, and IP header compression (IPHC).

	 </t>
      </abstract>
   </front>
   <seriesInfo name="Internet-Draft" value="draft-wachter-6lo-can-01"/>
   
</reference>

<reference anchor="ISO11898-1" target="https://www.iso.org/standard/86384.html">
  <front>
    <title>Road vehicles — Controller area network (CAN) Part 1: Data link layer and physical coding sublayer</title>
    <author >
      <organization>ISO</organization>
    </author>
    <date year="2024" month="May"/>
  </front>
  <seriesInfo name="ISO Std" value="11898-1:2024"/>
</reference>
<reference anchor="ISO11898-2" target="https://www.iso.org/standard/85120.html">
  <front>
    <title>Road vehicles — Controller area network (CAN) Part 2: High-speed physical medium attachment (PMA) sublayer</title>
    <author >
      <organization>ISO</organization>
    </author>
    <date year="2024" month="March"/>
  </front>
  <seriesInfo name="ISO Std" value="11898-2:2024"/>
</reference>
<reference anchor="ISO15765-2" target="https://www.iso.org/standard/84211.html">
  <front>
    <title>Road vehicles — Diagnostic communication over Controller Area Network (DoCAN) Part 2: Transport protocol and network layer services</title>
    <author >
      <organization>ISO</organization>
    </author>
    <date year="2024" month="April"/>
  </front>
  <seriesInfo name="ISO Std" value="15765-2:2024"/>
</reference>


    </references>

</references>


<?line 830?>

<section numbered="false" anchor="acknowledgements"><name>Acknowledgements</name>

<t>This document is based on <xref target="I-D.wachter-6lo-can"/>, an earlier Internet-Draft
authored by Alexander Wachter.</t>

</section>
<section numbered="false" anchor="changes-from-draft-pjs-6lo-can-00"><name>Changes from draft-pjs-6lo-can-00</name>

<t>This section is to be removed before publication as an RFC.</t>

<t><list style="symbols">
  <t>Header compression changed from the 6LoWPAN header compression of <xref target="RFC6282"/> to SCHC
<xref target="RFC8724"/>. The section on 6LoWPAN header compression, which was empty, has been removed,
and <xref target="hc-sec"/> now specifies the use of SCHC, the provisioning of the context and the Rule
ID size. <xref target="RFC6282"/> has become an informative reference.</t>
  <t>Only the compression part of SCHC is used. <xref target="FAR-sec"/> now states why ISO-TP rather than the
SCHC fragmentation and reassembly mechanism provides fragmentation.</t>
  <t><xref target="sec-frame-format"/> replaces the dispatch and LOWPAN_IPHC fields with the SCHC Rule ID and
compression residue.</t>
  <t><xref target="addr-conf-sec"/> now justifies the node-address-derived interface identifier with the SCHC
DEVIID and APPIID actions instead of with <xref target="RFC6282"/> elision.</t>
  <t>The CAN FD frame format is now required; see <xref target="can-fd-sec"/>.</t>
  <t>The LLDAD no longer uses remote frames. LLDAD-requests and DAD-responses are frames with a
data length of zero, which is unambiguous because a 6LoCAN packet always starts with an
ISO-TP header. Retry behaviour, the handling of two nodes probing the same address at the
same time, and the origin of the 100 ms timer are now specified; see
<xref target="link-layer-duplicate-address-detection"/>.</t>
  <t>The affiliation of the first author has been removed.</t>
  <t>Comments from the review of draft-wachter-6lo-can-01 on the 6lo list have been
addressed: <xref target="RFC8065"/> is now taken into account in <xref target="addr-conf-sec"/> and
<xref target="security-considerations"/>, <xref target="security-considerations"/> now states that CAN provides no
security services at the link layer, <xref target="sec-frame-format"/> has been renamed, and the
CSMA/CR and CAN FD abbreviations are now expanded on first use.</t>
</list></t>

</section>


  </back>

<!-- ##markdown-source:
H4sIAAAAAAAAA+192VYbWbbge3zFWfihoVJSShhsTN6665JgKt3tgQayctVT
r5B0BJGWInRjAKuMa/VH9Bf2l/QezxARwjgrb3X14DukiOEM++x5iuFwmNRZ
vbTHZue6TPNqlVVVVuSmWJg3F3cvzEU6+2jryhR3tjSnRV6XxXIJP09Km5r3
tr4vyo87STqdlvYOxnjxtjg9eb+TzNLa3hTl5thU9TxJ5sUsT1cwybxMF/Vw
/Ws1fLEshrM0H44nSdVMZdp6s4aH3ry+Pk/yZjW15XEyK/LK5lVTHZu6bGwC
szxPkhSmh+myvN5JcAk3ZdGscf5lsZMkH+0GLs6PEzPctma6dfIe//Pm6oOZ
TI5eHckfw+sL/AVbub+QJwAS+N+Tebqu0xrh8zbd2JLuFdf0n7y2ZW5rBNz1
bZbfVEmSrUtadFXvj8evxvuw7Ka+LUpcV2Lg36JZLhkuOydL+ynN57DKX9LZ
LYy1Q0/YVZotj02qd//tnu+OZsuimfeM858bmLoo4NzwXPAmbB5u2HlWFyVd
yPKsztJlhU+P+JmqKeV9/15R3qR59lfaLtx4vbQzAGSezSoDSzHXFi4Uq1UD
V+iZylzayqbl7BaAUQFSNbXlkRx2vL6+fCMT1qW1NVzanxyZP6W/2iK/yYuB
+UtT4c/hTcPPzbIacGjnLLX4iFwr5rjS5weT/Vd6pYFDxgevCoCw+S8FnDTf
Wt8WOT793dG+Odg3Ry/G5sXh5CCCLqDjv9m6zEalHX0skyQvyhVs6c7CQZnL
89P9gxcH8vNg/9VEf746cFePXkz8z335+eLly0P5+XLy/IX+3J+8lJ9HYzcu
/NRnjwBZ9Ofh2F19uU/PvhmejTJbL4h+qtntbDg5nBc13EuyfNFe+GTyShez
f7TvFu6uHk1eulEFs5Qw6fLVByKMIe3OGOUUl0U6N3f2NpstbWX+53//HyGV
IWmanKnM7AKN7SEy1mZybM7SOjXLLP9olkg+hEfr200FGLTEYwWyAVSc0k1B
HSUYIyh5jIuiP+fAYo7N/nj/YDg+ZKSyZWYrBIO+sIO0fVXPd2DRuhN8gwev
0/IGkfC2rtfV8fff39/fj7KqGME031c1LC4t598fvXh+dDC6rVfLECD7vwNA
9o/NT9nN7bBaWxvAYQWk2qxMWtdwICub12b34t3J3m8DzPMnA2b/mwFzONkf
h4A5fPni8OuAOctSoHTgDzMTsY9HJYzZPSsiwJGsWhfwx7os6mJWLAmZFMqM
XrDtu2xmq2+C2MFTICZb/VaIHQBBMsSS4XAIfBHYYDqrk2TrtmnTGXBcs8js
cj5tKmXfy42ZwwpvcsAdoHvcXrEqkPhNul4vlSmPkje1uU0rA5uZWTO1Njfp
vFjX8hrwWxjR3KVlVtDgcxBXJYwfjTIA7AO+DsPAgoo1jgHQnjbZkmiW5uZT
rDZVbVcwLTxo4MkSQFvhi6lZNcs6G65SeKA0uJP7DHj1ogTBY7I5IHoGeywr
lKCTiZlmqHWUZv8V/RyBVLU4u1FwDmD/iwy3D+uv4aaT43J6sOi1neGglZkW
MBU+5MgMNwDnng49P4JVg+iuDGgrDREeAHhWZlN4/7a4N3UBwhzQbgHLJ91o
HelGsLSmQmiwCjGAHc+BlFETmgPI56Wt6DYwbQs7RuDjOzlIM1gqLucKdYsZ
0YD9VJufbDonklit6V2A7u7V6U+neyNGn1U2ny9tkjxD5aMs5s2MTuDzs/DP
L09ArhWQI6DTx7y4z2ldCHpBDIRZgFpzOOcsHyU/FfcWdj2ARwk9l1WBb9BZ
bMGhAHsGvaiDIFil+QbWA4I4QcQlzIfVDu+z0g4M/v/58OT92aCLTPVtWuMS
YJK0hOMvzRWojda8wwfXS2tOZsAKGOkAJMtlRhAFnaVYNjT/7unVu5PvTy/3
aBMAgrQEzCt5cUR+jNU0yWQyhJtmV7HRvDnbox3sv+IbcIIWNDa+EaI3oJH8
uWHkJ7Sz3dkYqkC2RQmcjukI1gsnYU2kq1/af29sBXNeXl/uAWhAhSPQCm0h
8cFD15dD+ptnW6WfshWImXW6WSKPRlIAHvFXizA/MsWsRsxGZJgt04pJBjeP
W3xxEN7HqwTUc1BSsylAGsX88BIWTChmzs8QY2lS4F0rGOjd9c/OwIDpJvtH
YxmRCQGQrrQwtkUiWtnZLSii1QohVzVr4vqgRiDHLd36YZgcxKidt2mYTgu2
tgRRi1i+AjUDwItSqVRLR7gHUK0XJ7ufP3uh9uXLXkT+BK1mjdcOxq8OFRxr
WhAyhVHyDnCfToEp34YHT3jAC8t7WAPxxdRMDgiTqqIpgXPLYwN/A/hGneVC
O+4ugE9Y7QyIA3mnQEQGp2kdckZ8N19u8KAKQI6Plvfodow0aexikc0yeGNg
bok5IY1YlOPEoWA8WjoyKfP5s2itX77AoGeNJQACoJfZKgtYIjDpFLaHTP+A
OP3AwJzAZ9wDNza3Qhf3RQN0IRdgiQ2zFxtAmYGXmyZPgeDBXJvCod/C4ePR
TtNptgSTYpScA+bWCBbgiFWRI1hREAxZc+gMDMCuLfPXDKUkM1jYBWyqRBZy
5x8Fi3UBb4PMSpKT3LxGbEbLcAomKYxNIF2mNfLZystwGAhezGESWAqb0cTX
KntDeAz3CxxJdRwcHVj/CXNY3hbw/jT8e1jZGQoAGCqrHH9mHl7JcMA3O1we
TCZk7PdpFekYIIPvCwQj4HkNUjUp7awpWUoUlQoHsCtTz5FJOACM5xt4Dpgl
iKE5IekMxyBChFnWqNYxISbAzLL1ipCMZLQlHY5HQ2wDhohnBvQCB2s/gYiv
GXxTi4cJzAJ50KJEDMqBxyjAEmRWKzBgAfLw8oDOKbtpBLXgZlUs6nucolmj
RggABqP3Dk+K8RyGAzN8BcJkZOBgrdzUjfE4LIIA4sGBInhnXgoTt6RrKUhQ
/DEvYBjWlopSWSCwuJxNolp0OdKBSAesnG7TgV+0GoJ0mudFzeBZL9OZkClY
ynBhyOewwXkyAPn9bQbQw9kr0suCwZKsiuANoyErRkmJKyQCT71kB1Ge3ljC
XVYKEcT0SMkyDJEF2FAKemkiqvrIXKGeKXDL7hCns4oMBeROiHt3GfKt6QbG
uYFJ79MNo4aSFTLV5A64W1EOBUYzOg/H2WHWQlBDr6nYCcZB6KHezIilExMS
IZLhmqbKfQHyDmtVjYn3Drh02eQ5qYco9QqmORCYyMNvjFI7guZOsR3wYRhO
EyyNUCHxOMVoBPi0FXlgFzCW5elJ6RSS6i428dxUNEDCBQQ16RIb5UQwihPY
ns/9yHzu2vG5ZLeyFgSC53zEmL6Q8omv0tkCOTGjw1V5yKfoc2OEqwn7Gb0S
oWqmCVofc3KSucgEWeLySkM09qoiQX1BgsBm+BC68NJlEtmlXdNnBccPdke5
2WYEwWELAwfNCbQQ0j+QX9mIo4uYX+FZ1Ib9nYhK4eEA11mDql0iA0aO1iFw
4BiOi0/TusZlidk1l7MpUxTbPCB6UwHlnM4P01WgkS0TWGUFWAA8htVu5BhE
nnMxFHtAiAoXHUp9WxbNze26ISakiDCAQUoiGFnYUBcWbtENMm9AYM02syV7
gVjPg+FIkUBf2pcvuJ+EFYvD8SEpFs/QXLpDJYZMDHJMlqBnFsviBuVh8NcX
VkI/2o1B73Bldt79fHW9M+D/mvcf6Pfl6//685vL12f4++qnk7dv3Q9+IoE/
Pvz8Vu7jL//m6Yd3716/P+OX4appXXp38hcYABe58+Hi+s2H9ydvd5jEQo0V
D51xnzASVKuaubyaoyjFkx9PL1BjImignw+gw5CZvASVC/g4mlk4FREX/wlg
3iBx2BTPM4HjBJaxzuBcUXMEzLxFCxCVb1LYvZQRF02JXA44A5LaXGwZWOYi
XYG6kZaC0TAqIQVAnk8EkA41sQCn51k1ayrWR5IdYklo/AILAP3pRPSokwZ5
cyCjd3iH6GL98mUg75Hx/ba4H14gnZhfYH00ygWsrwBqjmzeyuwCZf5ycfK+
2js2H+5Q6tj7gTlBOl2Lq+MC9ETgRbwir4j8qQAw6RJeIcBhCV+Pmbx5/fq1
ORrvjyaHowO3DjfOwQGN896ChgoKojkDyOB7G/MB1rMS/ztR4N+33Z2QkAQJ
UVE/Nn9CdRoYxDlah+QZwNm+7ozAIeAdYmbh+TilX+Y274HacSXv946TY3Ni
9DpyAVIQQaKAAlmjggCMpCYrCrSSWbZOSToCiaSGX0J+j1IDkMvptIjcgJJg
pqBiR2ZiVjfCqeBd0GmAg9uMOGXangrUIwNq0YaQFoMlns6CPVzyw7CLS95F
ztSJ3lrUfWQwkZfyktOAUSPFZdmclV9QnC0q2jLqyfwOtbCKsA0O7fKkYmeC
3L8qQKfPVJDvXl5Ve0Sv9xZoLSUz/B59EDQ0vhL5p0Ym3gQrs3iMyG2IPcCy
6b0hoVddrJFhZuiZcAAQqe7h8KMAQu0agcCyEI8Xq72/NvlMdaTKwrEisBwC
KJqijIDf5Jxs32WTNmdB7tV5EvwlapEb5EFoshRipuLaKl1Ae7Rp0aDDZjMi
RPzxUnUQAMcahSMeFbuKUfl0dAfgWmSfyPhJbzxN9s3ALjHSaPMbshQyMBAJ
KPIkOXZQeSM7LJV1MOroKKwBstrJK+Ql7FrADZ3aDaxAQUtbTVflo2fOdN09
OzmTQ/NeFTULWTHUEwFsxagriiKS0gW64ZwxVt2SkFLNy3kfYIkki73fI7KG
n8ZTFiFPEZcnL5qdDs7f0P/CwrGxwD8cMibUcIBrooKIAySGjgIXpPTKnlAU
bug2BqJdFxkS5pScUnBgTFl8zCofYEQ9KV4nDEx+PKBTMo/v0mUDDyC/mSKT
KYEDOLWOdTNcBdv125y2KrNAtfGPDDHENJSzIxrGR76oDJfTd8gERlqZ2YXR
B5E2H3USs3LgDE6Cp48Nsl4WXtpH9o/6L6nxgDfouAX0wEsY8qLn8Q8QZKPk
l1si+3kBilqK4a7xHjqCiDBZvNakzLq3UVlC4OVsTqJzB5Z9Vyxr0GBZFZbB
B0lViFmHGma2ABmB+AlyUh9XvkMqiy6VNWBcD8ZZ9v88Sn5ETOB75AqoUY8q
i0/ZCtWWjaeFJVDAkkVSSnwe8BQ4/e6kf1NVkTy+vmgl4z+PWnAOYhw4hL5F
qwCS+9HOUrR0xMnpHOgYgG9mdcMuVgd6XCFiRSl44tcvfkQJwURa4bywbC8w
vZE4d8N7VuU8jexjVK/ZTF3xztjsOMJxiTht4EKZ3drZR/Y/y3rnpAMEyxW3
OspcNpDYoYV/k5ZAPD94Hq/ksPBizaCsA9WOhiqF+vNgL17l/asti4oRHjkA
4mSFDDwjQTJiL5zfAaNRUzV0rqogLLIlylAOC6CTI/TPOmV+DWalPnNPQhCn
lHcBHwE4svnwdeE7q7T6yDQs7shCz43VJI67LVpnZlYN7IbGpnXwsyB0eR/Z
DZh6pC89e6ae9IBTgZga1uuvMyaXwYB8eYoOKlyF4K8M2/HLt+2nUYJB4ip4
hSHNPgSZi3AbbBaEO/o1EJEUM7p+fQpfqmMf7eN8tmyYQhZL0MXlWAOhSqHV
nFzwQw0TkjGerSzsC4XhO+ej1wfmBZER7hdpaMvQpA7xmQtG4ktkNLBjLIhm
aHQqCNgRqkQCkxVSwCm7Ql+5nwmPqM4Atwl45D5trxnDdDwVIxGSZFN6TmYw
o4vOgvH12FyRI2R4zui7e3UO0uU8KwFOeukcL51i2tesQXe0u3GKN8jqAMio
xDLuNQyMxqO7gyd2TDpUX7iLPCAg5tGHwVRYi5NQ3TbkKOLgGQYOWrEnNxhF
Z4LNYCiUdDFmCnAazk1rxOHSu9NZWpab7nq3bb2qrS17eJbKcFXFKOrjtCbR
YQgIsiESnSHiqwYFWEXRdaY6o/4S5CcON9jlxXznaEgDuOXDntNWIFHi/qhp
FnIC6DGnnadhSIn0UtGo6uLGkh1AbDdAdL4/YHYoPPjFQd8qOCKpodElgJPc
c+QEE5CwV2NGYeQ5G5+CByF6jTRK4wnR+UdqEZQ6UcJ87QfDjlDMe1zM2QnK
6t5VJFHVkeASCz4/wweGeJG46BAuSmDnNnXrl03pdqNIqpfSNZi4ZIWt0K/p
vOI4LEJxFPNmr15weKzA86PFeScxTlQ59014k5yikQ9HfcH4ADK3BUNBNEg/
x5AeYDfxwPS4R2ScfK4PJT3WgTx0O1OHc499wY+cn1y62RYFooUqCWLeUZqp
80ey40ZW7f2TLI2zOvRAE1GgXBSEuGQkIVff52cBKiTJiaIUeUaIytQR2sYo
wxj1mFbOvJJHTFTG0KAxdofDVhKpZ1+62saKUcgr0G7uo2QekMxu9C27HIIB
wozVBXReR/TqQoN1+hFzKhBcz3+Ap1O00DhKKdGr2wITIrbwBVSjDYq3jZIw
B4pv0zt1peqhg5ICG4ggqStnue+SGwayauURCdNYL4/AZS3BzI6YhWw14hku
MuDIEaV9DzwllI9h/vBJCZ2J8geziVcr5DKK0j6ePXTx7KEQ5tDFswHjGT0v
lBOAlT77iGlEIbcZKqMYVnhbEBYQ7rGHgOyBKECDwHwgJwajVzwDoldG5uc1
hr04DK/3nPJaa9pf+4Fk145uRgNzfXpBcPv57AJ1BZ9+1H5BfOMEvHCaNamE
gLKlhOsw7laslSUDqP72t78l3w2f+O+75IGyB3lXlDTuAF2RcY0hpT185OHb
Rw3/ETl0/33zqO0c95brGY/sN4wqtEArgv/DUSgZ+C0m3/E8fwcEcLgLTezT
0X4TBPBwPx+bx3Ef0JoTXP+40yKaDqx2JOj0BKgKp696hN0gEK9CwElHsg6e
5h6Ltf1R8nO+zD7ayJHZM46Lw+0fYexFWKPjxp6wHWdHK0VYZsVlETm62CRv
aMBJQsEAFATgdxE2TmI45xxKAPJJNEsrfhMbrVGilppfRPr7IvsEP2UBTR9r
CWQzSYM3gcn8+RkKYlFFKH3qG01XydQica4qEasEkW3NqWKwEnXXuDTDbYmD
YsWt7H+qGEDshexJJuukK8Fs0YI6mWmj5DVpWPQQq5dgyv5747YjL0ooRveF
PytJFhKpRLkHM/JwYLyF0roQ5yjdsbPSRvFIUih7ktQ4R81oZmgrByPtyZX7
liQ5G1+iOerInQNXh+uiypjehAhSt3D/ugu6F6KEYEYGmOCBS0hzQKaNKl0K
yfGn52fnrw0lp2EYQQysp+Wnye7CocadoaJ8jU5e2ig5cahB7unxp/FkPMbN
4Hivz71hnVYtXBolHzjM5kbYhbfH+vZ4fH5OC5SF8ZDnYPLTmG6RnJnOiyUV
Fxj7uikB9jjFe9SBJHtlSXFQ3a9kUTDWimN4O8Bhxzdk2VS1KtB1OnU6Et9G
NR/0iA2uNd7rQAMGA81OYfzT/BnKCyJSEmszd2ksPWhJHIpdRqrfiSInV0lT
u8YQvjiK3LIeGdGjpDpgaM2cYKyaLyrm6GxiRJA8TOeocCNQkV1PKMA9oTZH
3SalZM55Tk1W3aLDgjJqOCAimXoRaLeoycRROe/apV2HfMsQcCQg6NBHdDyH
PKA5aGTswZxRqJci/6AoPDhN4CHSC+AOI+y5GQq+wruXiqzu9mu4+vbt2cmZ
vzThN87A2uh7YwxXHSH6jCl5gKhuqET3wIF0T1ny0FgeItqKJkFNpovQqruE
owkpoLqCKpAZP4xDLXLyMAn/3H/AJ6JLBw+H4Z9HqHW19K72n8nDO1bizl6D
TaqqoTFXl6dec/vaGKqwgR409LiAbJJkMO+0Ldlxm+8wpOh8sBg4hVXgtbOA
kBRRdoUm0FSC5eFjVyxq+p5AF6EkirZFENAUnOb48JCdJpG4kpsnJ+fIB2Fl
GhDx/gi/w+N/6EHBGBPEM0BI+h/4c6K/4d+3HpR6xrO5ntDPIeMLBb7AcYe8
I21WhEnjIsz/jwHl5GEc/vt7QelAEgDzXczzt4DzGai9CvY2gYDmq0KH0VkF
k7iRBl0Wz8FwcoxgKMwLgt4yBvUsBedVu2Ad62Lbqxz0acmi4Tx6sZXEWY2W
yPuzi04KAFbqos810HDVI6YxOM3NcQ7VSqr7OEXaK7ziZu5Z4Iih68+hB75e
aDKEO6GVx2Fc5PY/FMTy8hJnflwh+FZgUhBRnavt8fG5Xws6stY0T4A3CTRl
yH/yVSOfn6kA9KUkAPWOlfOoeaM7E1MIAxDCU1qVGpF5Q44rsYamNjSIFDMx
31/NJm8hnYuS3iqF4Sc5J5GShXDxNelw+q6ZYbJJHqgJDSAdp2Q+scIF1LOZ
tXOJIT/xJUn9qSS3l7U6Wi5lA3nM8uUgqKPJ0aEfSNxjjyUwfX72RKfm0810
qexc2xLvPHW3u6TmobBnfa9jZQs4wvQGzLKJDP9KagXQ9w14B/opp5/VBft6
6UST7tlz9ItSAULSCeupRphioXsC4NMqURmhH8NSKgYlgQksakw7N3yL8uAs
24xEvXNGNt0pteSAXSCvJVSpqkWzdMyIcBKVcA53ck0s+WqwImEewJProzor
0rpFyY+n0OfS5je45wUJF0moeoRvubk8+ChrAV/rssm0Qz3CCshCAXO4A5nf
Y420cbe+XbYg9h5daMjPu+VVQk8nvctxaCfF0BLuMS7mJIGNdHmfbio+PF9N
F4VtEsS2GiZA5kyJlxRmFWsVaI4LTYdMahRSq4oYZIBstEhfm7QCCxEogdIq
Exh0ZF6n5RJlpRRqivzpJKWToRfHRdTFEaHWSGpnk4VPDhDLEhB8Kp63bXE2
Z4hqAgk8yLkY+qZG6nD9dBMOJA7shNk/mLucI4vwrghk9F01Nm1TSGxKy9Ug
t56yehUCmJKWdAhP3VqUsIYpKWHVR2yKeyVDjMcsT7Z4SdpeCXSqATI+qhe4
LKan0rO7IbmYWZ2gRlNJClQJAIrANVAX+JOmYRanF6mtQpUsCxRglTsJZvaI
CDeqJ+DGuAKzuzcVxM73E3mDETAJleZhMrD2cqiMTupeECdjWvuTCXMb6RlU
NtK8QocYpgWXwmIcjnBtvz+VmgOttNyqi2mPgiuQ6KgzCROiVdKeONc9Zpyi
NKFXY0XIzXP7dDwmVLc+EWCiQDDwCZPuU5xTWZCMR5CLJuSjkdvsbXLRXH6G
Er4YFhTQRVf0vNEa1RrTQXNS7sKkRASEwYA4GhtN9YNkfHMKpM/qTTjZBKs4
YBJMfV/ZmtIff6Eiyy34NFAK/DtOJyGd4D7v0s1gu3zhpK3KFZppGTAniNeV
XS4GfLbpFLlVvkWqs94s+Z1KvpKDel+IfojF2HruYQ65sKbEsSZ1s+eiRXNk
n5x69xkBAHUyz8DTjqz2ZQ5UNepgm0RIG4hWj4AMJz6lRZph2LiQXFKBAYUh
OsypkZxTS9Eq1DTv7EASOrBvFrye5Pa+500Oz62tkDWACRTKpqS0C48VPEjV
fT8wBBKaDvQZ3AKVrMYzZrDGNRqDORYCukPPO15BOLgtLF/alnAV3NxqEQ0F
+rDkb7WuGeYi3ahiBuiQg3FIXkybQRq0QxBJiV8uqd5XZIv8bdIb7EJCpRXo
zvDRTVkLxQB5LVpWmciCHIi5jQSeasMFdxpNtS0RGNVYAp8uuVg6Jwsuw+zv
EWZCoDdmns6HOCLmZd9yZhmizjlcUteL5AjRBCfK4aqOZh6QszgMNdO3FXKL
tD+ENo38oyQqoF+KzeLQU0VXfpTGRuZhOIzmHv7rg7tl2v/8rX9xbzGpDR/E
GPK6vPd37IYqKeqje8f/23yX+KogpHmakzmJWco/zbYm7DOkH+1dfqMfUTFX
fYhttGWP4VOqNMXd4pP7Wra4JgqL4V1MUfHhevy7F9xHcYEdQd5EBQOYXtBz
KwiMUmaiZ4PCCaaswUtmdPpRZU5I4FQMSUbSIlsu2c3nupXYhXh02JGMd1mT
YB3ozZszVyRP/YY0UwJb/kmGoIbZwOixwI3myNBWNkXHCKh+myI0nJ0IioMI
ke/zFq7PwQTCVjq8lsjXXXWd3bBK8XLHuNnBTmOePzyPLxw8HMQXXjx0Rjl8
aOUeTR724wsvH47a83Tzcn7LhST2p8O/J13oet1/j7WEFKVdaoaZ98wjtpCk
PfG8HQ4OiesMNUfFTvdcRyK7jGXKnyHtAkv1SCqCah8WujlKQ33q7PWfcVBE
x5OLC/wZpM58P7dR0tBMKqFZ8yot9TigwhdHggETJF2XPbNYHRilayyc33Fk
PuS+s43rakNODP9CVnW2PEh8LpDz+KvYQ8etA1SQVt5ZglwnRZ2UKko9GaED
CoHB2kbQKAW3XLvaEiwR8S0pSKGMu65EiUjw32zeWF34rEDby/XUwqRN8jxr
JilPzSwCj5DgRF3pWP1chEUBkl6b+B5csADJzx3wYgWGWoMxs0FtLegI2Cx2
EybShhlbedLkwS30wyTScWH8AnGqpKavYnGnFIhHkx5giCa5a8009xn6YPTc
FnPPF/cnL3Ec0qkS0qkkAyBwvUbGik6PCdY3mZoUayCXdAYAmRPSsU6eJ6lL
tJOhYmeR9vIgQJF9E/e0YZbJdmOY8P7mLFGHPSnz7AMElTebSisqwH2tP9WC
Tgcryc9bAZydZ0ZcaTHeUNL1DZU20jQ/UMBJt+o7L3WbKJDfrcE0l6G6Z7lc
HKNdKEu8ZAz6PvVJzoGnUiJDEaSu6RYddVolYTeK8Gilhw891qUoQgthRrAq
4UVa0yT51MnXiUtKzVBl4NgBbULZqsYJ4koCUSPwne7GJT64/wrrWdmVIFAI
mF4VKBPYR8OXEvYpJwNu2hGgjUsUknLy89dH4+Pj718cOHV9MmaHfihcDzqX
RBDzjVB2bUt1fTQFFqPSokWCHumG36WSxj35i673qmCmlWP7G9cQys7W6ZG7
myVocNjOTYcEB1gkKmpPrcjnZ3mnxCLsxJMFHXpYVgWxQW7E6913+tKMrEG0
q7nywPdEYrQlM50fnWfACsDKZn7G9q1YtNq6QeszlFXTwDRkIl6z1AcYk549
uoTiIM7tOmQsPANgx0zjcoHxVi7DAfOXDmrszHTxLmaInPLy/TVFw8OQnZJd
wYlUQVqZBFKSSIdx6mm5aqeSSZ4BHIWrjsKZe/ZbBO1RKi1Ao1YnUUVO0C3I
qfu+1YX2Eb0t1kHXC98zxMegRU7kVC1MCRFaP+qLrDvaTRuvXN17UIrvp3CF
l1ojFeTV7VEIDs2LaNsaw5DCs7np4spp2EstarIRrtQXQ+A6K9GSXK+1KF+U
O4EkQbba1v5eUXeqjXS6YNbd0/zh8zMp1HLpf+SZe2pb3Ej3JX8OP6E556O+
+irnP6I9RknpSiGxcqx6jOty8yGX8v/wKZVe4ZKEGIWWcKbHMvOTqA5XA1U/
tN5pnZO2HlYlgzWKSlQKUhNcoRu2N/yGCFv9LQUCo4T255tOVjW84ny0Wd0u
HdB2oiLwezP1RcdLwjMEU4Ur6IXnDAhShR5JVCMWBuu4jICSaaS06L7Ejgx5
4iJnVLqA71Bx7HIjyRtaTLAgO0zUzrgFpGziY0bIE/Ts+vy5257zC1YaVaMQ
euGBM/W1j0SyJgjIShefn9HnAKRcQuioU2WhZzfd+EQcjKWgQ7WqFS7EQqKu
KNoJpeJKPI6+Je1OKNuMPF/FQSxRFNmN6zMQQO9YhCwCOWEgo9pFdRyujNt3
W5TukFzyTB0IfkK/UjwjkQg/gH8W3KcOJMla9fGwfwDGQt+d/AWRQq1AFv2J
9OoOh+tWJLdzxIuSQraABE39JG5KpNTmpRiTAHxk3YECUIEC85QmjBJ+oNNz
QRfXckZzAFQu5UXcdzm3N0VNja64iSdwDCxDcUiiNRU+ROG5pq08nki+BCFZ
q/8sWmPapcGxbuxCix0I0NIiux9ulWVDHSG1IQORwiWOGNfuEDngTNk8UP/5
wTNX/J/6yJw3Nxgq5tyVteNCNIZ9JN1F0HdwRGkiOiZb+j4jwpn6gUmtaRYI
Lvbl7B++IIBUJpTc6j2g/uyl9XDyjSI5E2BWCy9ydqzoV3HHRgri9LAfDCwR
r8PmXrIPjrEhC6qweAUmpv3EWRIB90/EKCPiwieH6ZIz2lTVI++LJGUTfnez
RLQIxqc5URXmkuuTZGmsmUSmIVN5XOweUrgiiBVI3GYUeSLO2NOhT/CGv6ri
y1y3fHYFmDXQzCLDVbJIL1oDsrhfa0sSbeu14Da7aZ1Qd8Qy76gQ2gRAyll9
x23Kr2hypM4bJhdpvRDMFI3co2uEuRr+WAXX9VFJ/2GlgrW2d9I2Pup7+HOe
ofhZ1Y3Ai9btmiEwCZD+q+VQgFHSAz7o/Y6s5QY0FqRE1pv2x2PEC9xW1UxF
8EoqkrYti3tndqr5W9XdQXOLxHdrb2FPBTCqpKVSVulGxPTCxcjae/t0u0wX
l50Q7BDncc0z7CfMskyCJYHoicKZLorBLWF6YDYKpELHUEWa6yxNyZfuwoA/
mC7vT7bw/lr3jnwKNTRi99O0yjhmLm1E8BHp0m21uZ5rLzNt0C3JdMCY4ZNA
XC6ub9STuLRCx/Z8jbyoX67g3jc9BPDMmjV1MFTrTPBGO9pL4yJ0aMA53anH
koUStS+XEr5U0+hv4M0Gtgisc5CknKHjvwig+WHTZYGFwLw+DNbERWj46Yva
lfUrlEi7wJSdfMZKkczNDuAwY5TJR6reXGWbEw66HnJs4zmEnV1CTBTE8kiv
JVPaLla6SvmoF8AkIaimuEiUnNpf3zs1g4J75hfnHQvn0qPCaeSoBA6iZIu4
1CH43aADzZ4zLdBnK3PEBhQv37Up4hBke0zU/SlRSd0vop+EDS98skJAqQNt
F+TcLvRtC+CMCHR9LSJUmTKLe+q7j2pQG3XpMNHuURSzpzW3OsWzulNWKf1I
IiYvzEqNtlgAsIhHuoi1i9t0uVDZmt6l2ZLOV5ek5xyP5exrAvICbDKfDd4/
O7nsppa6bbX7ByWhzUydMjWOlT6xcZXrzBNVD2Limz8Djkw4Lod8hN6w62Wx
YeEXpAcda1NP563SoyOrLmxIpp/EuQfMxs6qytB9r5WoCRziXtQBwzX+qEit
0x7vYfcwgBywgQwbbVEcIPgMEvVcZh45Mj9XYt0tSfZEzg/q4JkE/kzxJ8Tp
NC69MP6ogABGO5gGvnj1BOrXTyQXYJWuhbDDqqPuwy33X1wWHTguXVoUdyWT
96W1fe6LooKoBxlxru9E8BE6X+u8G9dX7kk0iJGF4x9LMejZ0QmHf8UO0soc
jF6MuBjt5Wjf9wkiP+wA1DVKmvBpaw6ThEqf6lvVBoM+tk9uVGcZB12ZSlfg
09duw21bQw/jboDBTPDyxOyb5+bAHJoX5iVYP6/Ca5Rm8uj/aKeO6w1Y2xpJ
eEspM3+caPDgiWNs/Ydj0I8LAABCZdf1ZOQAxhPH+Oo6Lqu7hxiewTmNnjSG
BjoCZA86ihASb6EQjHB8WPvGmNUxcMvjjHL4/rhzALcRyFidOjnmLMzMJ8NL
wWoXtUaJoU/qtZ7fiopY9ELHhxNdBxFnX3HA4VVe6S53S9RAGaEBkgmPIRuh
No4AEDaSjpw+jKTBKS46KleuZ9gtClf6CIYHPQkSODZc7aXURo8Afd1X5Spu
F+o096CKUb010kTUqe9T1/JSngAQam6CtPrsww9YDcOsvzNIVKFndrce2J4p
nK+CSxNh+t2t57XXKUfsMl5fRupZtXaXy4swNN/hrZSGySpQ+5YghugtyKbB
3tFgGGiata8KCcpxWTb31T2qLRAmPUedDEigPbWTQV9X4yDkgm0menISQjGU
VZrAqTG2YI5gkc4/lzyVzYceYGpiQIkYP7aKVOYtUdYpUnGrGRiv+nS7eWpJ
jH4WSJUPVVW8pqQdDNsdXbUVXhhdAJQTjYPLX8+5kubzs47v5+nVetwHs6QE
ZPb/hg4muitf6iOpygUhPlEmDXKEpNBJlBgOF4RVTmCMy9g0CL9EY7CxkHTe
YO6Jctn7ecn3ojZpFA/Cz2SJV4uCex0PkHrVgruihwchJBlaml5Ua9TM2C6o
0LpOtez2WxuXkbyU3UnEbXcyfC6w3OtKzm8Zl1auzsbdCQ+61y+Rv2XcMCZ4
KS7J3bH7LoBb+7eOeyHmz9f+fdu4YcJDSA6qCfQQz07LiZ1VPfV3Lbf3lz35
RpIYpVsSagxXA4CNz6jGqYWo/3NH6bnaQJhEv/EKJz0nve+l2Y307M7DMo2s
jni0NMZ39oVE42D+gZI0s3AXindPLTMud7Mr3lfge16nmFubpMzBLHXY8HM4
o55LG8mAFNDpRyEG7c/sGNHvQfklB7qj3h8Cm5VGf7tPXxWKjgSI7iJ2LES9
QMqecj8cSjrD7AYxoVQlv28N7EI9705Og9SKJbbydjI2XdRSiBLRMqeEub7T
tKigNVQdRI2kZ31L6gZzDlwaifsebpnd4IOeC/YPKLsPxvqn4lIRgF2flwMO
/+z99nH/P/d7jPsNg+9jxowwIIc2T0yePRL5BI2jFU1NtvU4xpqEqByazWj3
bUHuKpjLVzvclFHr3EcWIt81rIK4wVDcL5V2iXDfrOt7xrWzqkEhy91HetyU
FM8UzxO7R/W5jYs8sWol7kssYoPn69vwc5WqOcRhfMqf8S6zoGskf0QH9c6c
PqgAjDSMFJbyEQv6QpC0VO0Mfe1b87vHgD8C2+QcBerMimHLzEpnlKfA2fu8
9Ks6BacA64ds7rLUDYQKto+WVD5QQz537yZF9h40yyMhFCAt9xLhhIXIvOMK
//GehMq1tq6XkVvXhVHbtMs3YMkGjq3Gknpn9hpfkl3IeOv3ySPH6Bv3ZQll
Ci+UPnFD7/mZWiO0J2TsaGOxNMhyH7OkL1XHPQj4+5zx6INQZARbdF0iRcI+
F5sv3AFn2/osCeTAw04GvGRV+7yFOYcedUTJ2XUdtLlTBMXs/VdIo5DJAacH
hEvRaj9KbkUBPcfAAX7F3PqujdraQXrNiEZGmam0orYkzqqgn/eQNAApjw+V
vbhn9vZ2DQPDxYxbuDK1IXxz+o4sfstfjQyAYmcfRZPosW7ZeVVh+5STD/Ix
h0x6HJx84FQdy59UChIugkg37sedeNc4H3VQq8WjfbQ8brPUVUV6gDroqEFx
Wuv2lkkddakOct5an9DmhimIou3k11MM77oxhaXJN15nH/kTLUGPhapGDOgC
yTpt1MWpDmhRBy6zJW5I1YLhYOs22/3ZehTHDhT6HD3MU/tK2zEvi2JCVFKA
lQ70oaHg86jRa11nVYd++tVol+jfO+ybi7AJWLcQYv+AamVUv3iJX0lZtBTh
8CMyKp3oHAftB50c4sTFcJ1BFyppz+GcO8HHggc+Oc2HDTD7gKjxOGkJMISx
epkcrYWzSml2yRWx80oJMxij1c3zGVcOIJijfOSrmc3TMisw+KsffS7yYSWX
e5U1rqt2n+KOEjFcbj6PpfqaP+Tgm4KJDOCw123PQ67jH+xJy2NmGd2om7Wv
APcrpRu/ab1uGu2cuEpnw2CdQb15+P3qWEvFI+w0n5bsGmZ/u1U52/sKE1Tz
3DvS0OumkrIj70RouixLhQX8HO8fj8fHh6+PJ+PYbXavzndgLYNEEnOR0oI3
4Mf3z7Vspl2OGv/rFLC2/736ygCd2tX2v8OvWT5fM4zQzKKvQCPodsNtPocf
h3sYM4Oz6d6GH9g7+eu219dXsH17IQYl/7j6dgLILnc/QAggAJwO/ZQxwklj
rO/tRtqiKbU+XwvG9rCHJxHYzhcl3jDI8mTyTfsE8ddJ+bcR8e9ATa+61eHx
v69R0+HvgMshNT1/fgz/C4QynvD//3+RmiaOmrBFxH8kNW1F8m+nJ8Hw+MNz
rIN6ovK9hJ9AUa0PLwRGMZ5GVzncxT8ekYj/rALxH8+jGY0cVjHL/vuw6v8y
PtTDaLbxIRH6/0A+1N+d+zeR7+M0Fn4ZM6Bl7VX0tH+87e/cj2949YE+YPQQ
/BiNRt/yPlk2D+7Ht636O101/q8/3O94N7KzVin1dzKxW4FPZHpw1+mXg3Nw
I37vivyp8OT1Tw//AmP/K/0SB6pA56GFWvSDoLRtXu95pT+fuq8I6dr2Uxvd
+CLZsdsdvxIKeHPy/qSbXJyledrujSAdAfD5+E63LIy9wOjk3mDAEKtosTwa
uxOio/DELBr63nFpuTaM65bYfNyIX/AG68A22l/FV+1KjV+ic1HRGH3ySb2K
8ULIm06rlqHkI5LSAaK79229ITjJh3v7RcVf+gJ/xn5mXctQn21C8WBZS9pg
ikItqd9YhJlgZv0NDYH5rWK8c/k7d1qb84euKSeee49Iwb3/TAvlZ+vnsvmb
uPSdu0Dn5QQ0BxvgSrggzJa5lhz69nBhxjul/6MfhD7FvS6KBf7Aij1g22Wx
kU4PeasVQBK3AmCvY2tT7NtUIAx85KTi0Mn12ytDueMAajDz2fSfSgq9SwuN
e5DE7ezjLltfOLM8+qh8u3dQmEae2E/0QRQT9hT1FWtbvvbpnI8w7sj8otXm
YZUJY3JWzZY0PFAMRRVyex/Xj8VLW69tWlZdXSru5MOdFviOG4P7v+IHpqRX
JlVwcoL7FL35lusUqRYqW3Qnv8cQFXoVE1dSQG2znbvU9dbF0BS5V4O2XbLv
Y+kt432VvAL+jmVS+UKJvu6uH61dV5S10DkxHoZqBf3zjCtAGuhtT9JZWeDH
j9hZ5Bo3YRY6rjzs3+Ma6kgfHi2CyedR33LtQE/lT9SVpgM1zSSjgpFWGzZs
/kIVQX1pjtSgXD7nNnnx/OiAMzwr6ZWWcx/WNKcPiX26BYTBbyMvN1IeeVuU
dcJNi9tpLfEMntJDzhZyIyl6nvumEotE9+lCEZ1q26AjEnaV0DY8HD3WXj31
LVayVb4bsv+i4KIAhum/B0jMVPuTp3UiH0eKS/BbbYqqdOO/MrcamQ/iXZZJ
MeUfs2QG7KV1ZelJqo5XyhBDIHKFeyHTEEJRRE5iR0Vugywd9zU8S832idck
vT3BKNWtzaCmROJBOuTGzeOQLGoHllB1d848ry562xWNXHCJcIYqHjgYDTIj
u0mJtZOUqrULD0pL1GmmsFmUmyezj3lxv7RzzimsQClpcq43s3P1PzsRA7+n
KSO+4cLQexAKAAOqDYU1cF9UY6W5gnq+h2cgkGr8buOtJg6fLMH6o2TfX3gI
cpWf3rIrn5j4HF8arn+tdPTheNy7PvWPZ9qlDFuioyyQSOC6mWppljSzBhSG
+f6giTNhTphG3JwceXLnBy2tBb04bJPBpCpL5Pj/lvGUed2nkmo2ICWDFC7Z
0gAGZz6mH3aG070P0jhwxQ33YsS1cETFVe1TbkFv9TBl5cDgUh4eN2XgVbA4
yX1q6h1CWhqtjQCaj7YDCbtijMJ0Wd5ATd/Ivb/VRh5R/5Sassy/2jckSNFw
bK9VFvaH3rAv9sRdpjOr3eOAidYk0Obm7Qc8rP/25gLn5sw9F1GKspkwrGL6
23X9oYch4KZ/RfbuTq2Pw/R3HYwWkBjTbXCoarZ2H8HvUONL4aFa/jgHLu/6
tr/zP3GTe6es93/DnV/nRtGYLw/y3Zbcvib6NMEobvPLbD/sLsvh4CAf26Sw
uZ4POgRCvsnT1TS7aYqmChqcPOGzDolppzxfYntjX1/GlAPoNF8q1Ty5g7cx
QQ9vJTBODVTyk87s+EgpvYw8GTOkiY889UvWeg6o+C+zqBkLJ3Ez8+0wFHzv
lFr11UE7SbTk7D01WiAm3GLzw/FEbQu4QgKXbUQcGTmU9v0/jjoYCjrxty6o
KC2dzYqGU9m7JMIU9Uh3v8FjN0O24mocw0Jv8xRLb9DPLwIoAgLaua9yMOb0
6t3J96eXruEVEFU6nZbaJLFypw1aTUq6J5Vy4BnRR0z+F9C0KxeYqgAA

-->

</rfc>

