<?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.17 (Ruby 2.6.10) -->


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

]>


<rfc ipr="trust200902" docName="draft-vladyka-schc-vxlan-fragmentation-00" category="std" consensus="true" submissionType="IETF" tocInclude="true" sortRefs="true" symRefs="true">
  <front>
    <title abbrev="SCHC VXLAN Fragmentation">SCHC No-ACK Fragmentation of VXLAN Payloads</title>

    <author initials="A." surname="Vladyka" fullname="Andrii Vladyka">
      <organization></organization>
      <address>
        <email>andrii.vladyka@gmail.com</email>
      </address>
    </author>
    <author initials="A." surname="Pelov" fullname="Alexander Pelov">
      <organization>IMT Atlantique</organization>
      <address>
        <email>alexander.pelov@imt-atlantique.fr</email>
      </address>
    </author>

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

    <area>Internet</area>
    <workgroup>SCHC</workgroup>
    

    <abstract>


<?line 28?>

<t>This document proposes a SCHC No-ACK profile for carrying VXLAN payloads, including those larger than the path MTU, over a managed UDP path. On a configured peer association every frame is carried as a SCHC Packet made of a NoCompress rule identifier, the uncompressed VXLAN header and the Ethernet frame. The packet is sent unfragmented when it fits the path MTU and fragmented otherwise. A four-bit fragment counter supports up to eight fragments. An optional receiver procedure for reordering is described separately because it changes the RFC 8724 No-ACK receiver behavior. The earlier indexed fragmentation proposal is retained in an appendix for comparison. The mapping and operational parameters require working group review.</t>



    </abstract>



  </front>

  <middle>


<?line 32?>

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

<t>VXLAN <xref target="RFC7348"/> carries Ethernet frames over UDP. On a peer association configured for this profile, every frame is carried in this format on one configured UDP binding. A frame whose SCHC Packet fits the underlay IP path MTU (PMTU) is sent unfragmented; a larger one is sent as fragments in separate UDP datagrams. The receiver checks reassembly integrity before forwarding a reconstructed frame. A peer association not configured for this profile uses ordinary VXLAN unchanged. No acknowledgments or retransmissions are introduced. Unicast peer pairs in a managed fabric are the initial scope; broadcast, unknown unicast and multicast traffic can be handled by ingress replication to separately configured unicast peers.</t>

<t>The primary profile uses the No-ACK fragmentation and reassembly procedures of <xref target="RFC8724"/>. These procedures assume in-order delivery; a path and receiver processing that preserve order are therefore required for the ordered receiver. The sender transmits fragments in packet order. This document also describes an optional reordering-tolerant receiver extension that changes the treatment of All-1 and is not the unmodified No-ACK receiver procedure. Peer configuration determines which behavior is available. No inter-frame delivery order is guaranteed.</t>

<t>RFC 7348 Section 4.3 states that VTEPs <bcp14>MUST NOT</bcp14> fragment VXLAN packets. Here the input to SCHC is a VXLAN UDP payload and each fragment is carried in a separate UDP datagram on a distinct configured binding; IP fragmentation of an ordinary VXLAN packet is not used. Whether this distinction requires clarification of RFC 7348 is an open standards issue, not a claim that the question is resolved.</t>

</section>
<section anchor="conventions-and-terms"><name>Conventions and Terms</name>

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

<?line -18?>

<t>A peer association identifies configured local and remote tunnel endpoints, direction, binding, RuleID, widths, timers and resource limits. PMTU is the underlay IP path MTU. A packet is the fragmented unit described below. The first-arrival deadline is an optional extension parameter distinct from the RFC 8724 inactivity timer. All integer and bit fields are transmitted most significant bit first.</t>

</section>
<section anchor="binding-and-profile"><name>Binding and Profile</name>

<t>The sender forms a SCHC Packet consisting of an eight-bit NoCompress C/D RuleID, the eight-byte VXLAN header, and the complete Ethernet frame including carried VLAN tags and excluding FCS. This explicitly identified uncompressed packet follows the packet mapping of Sections 4, 5.1 and 7.2 of <xref target="RFC8724"/>. The C/D RuleID is configured at both ends, identifies the uncompressed VXLAN payload, and is distinct in function from the outer fragmentation RuleID. It appears once per packet, not once per fragment. After reassembly and RCS verification, the receiver checks and removes the C/D RuleID before VXLAN processing. Unknown C/D rules <bcp14>MUST</bcp14> be rejected. NoCompress support is mandatory and is the default; compression rules are outside this version. A SCHC Packet that fits the budget of the Sender Procedure is sent as one UDP payload without SCHC fragmentation; only a larger SCHC Packet is fragmented.</t>

<t>Unfragmented SCHC Packets and fragments use the same locally configured UDP destination port, distinct from ordinary VXLAN. Both peers <bcp14>MUST</bcp14> know the binding and profile before traffic is sent. There is no in-band negotiation or version field. The receiver selects exactly one configured association using the local IP address, local UDP destination port, remote IP address and direction, before parsing the RuleID. That association fixes the RuleID width and wire variant; source UDP port is not part of this lookup. Ambiguous configurations <bcp14>MUST</bcp14> be rejected. After the association is selected, a datagram whose first eight bits equal the configured NoCompress C/D RuleID is an unfragmented SCHC Packet; any other datagram is parsed as a fragment using the association's fragmentation RuleID width. The prefix-free assignment in the Fragment Format section makes this classification unambiguous. Multiple variants for the same peers require distinct local addresses or destination ports. The same outer source port and five-tuple <bcp14>SHOULD</bcp14> be used for all fragments of a packet to support flow affinity; the receiver identifies the peer independently of source UDP port. A sender <bcp14>MUST</bcp14> generate a UDP checksum for each fragment and the receiver <bcp14>MUST</bcp14> reject a zero or incorrect checksum, including over IPv4. Ordinary VXLAN behavior is unchanged on associations not configured for this profile; such an association <bcp14>MUST NOT</bcp14> carry a frame that exceeds the ordinary VXLAN payload budget.</t>

<t>Optional future compression requires independently specified matching rules and explicit context provisioning at both peers. It cannot be inferred from this profile. Rule mismatch can misroute traffic if VNI is elided; a future rule should preserve the VNI unless equivalent isolation is assured.</t>

</section>
<section anchor="fragment-format"><name>Fragment Format</name>

<t>The No-ACK W field is absent. Each UDP payload carries a RuleID, DTag, four-bit FCN and fragment payload; the All-1 format also carries the 32-bit RCS immediately after the FCN, before its payload. Each fragment contains one nonempty tile. Field widths and bit order are as follows:</t>

<texttable title="Configured wire variants" anchor="tab-variants">
      <ttcol align='left'>Variant</ttcol>
      <ttcol align='left'>RuleID</ttcol>
      <ttcol align='left'>DTag</ttcol>
      <ttcol align='left'>FCN</ttcol>
      <ttcol align='left'>Regular header</ttcol>
      <ttcol align='left'>All-1 header</ttcol>
      <c>Compact</c>
      <c>4 bits</c>
      <c>32 bits</c>
      <c>4 bits</c>
      <c>5 bytes</c>
      <c>9 bytes</c>
      <c>Extended</c>
      <c>8 bits</c>
      <c>60 bits</c>
      <c>4 bits</c>
      <c>9 bytes</c>
      <c>13 bytes</c>
</texttable>

<t>DTag size is configurable for each association and RuleID; additional sizes require the sum of RuleID, DTag and FCN widths to be a multiple of eight bits. Both ends <bcp14>MUST</bcp14> agree on all sizes and meanings before parsing. An existing RuleID mapping or association variant <bcp14>MUST NOT</bcp14> be changed until sender admission has stopped and the quarantine below has elapsed, including traffic not yet observed by the receiver. DTag width is selected by the already parsed fragmentation RuleID. For this binding, fragmentation and C/D RuleID assignments <bcp14>MUST</bcp14> be prefix-free within the configured context: an eight-bit C/D RuleID cannot begin with an assigned four-bit fragmentation RuleID, and in the extended variant the C/D RuleID <bcp14>MUST</bcp14> differ from every assigned eight-bit fragmentation RuleID. For example, compact fragmentation RuleID 1 and NoCompress C/D RuleID 0 are compatible. The default proposed variant is compact. The RuleID identifies the configured fragmentation rule; RuleID assignment is local to the association in this version. There is no W field or padding for these byte-aligned messages.</t>

<section anchor="fcn-values"><name>FCN Values</name>

<t>The FCN is four bits, written <spanx style="verb">Fccc</spanx> for regular fragments. F identifies the first fragment. The three-bit c is the number of regular fragments remaining after this one, excluding All-1. For K fragments, 2 &lt;= K &lt;= 8, the first FCN is <spanx style="verb">1</spanx> followed by K-2; subsequent regular FCNs are <spanx style="verb">0</spanx> followed by the countdown from K-3 to zero. The final FCN is <spanx style="verb">1111</spanx>. Values <spanx style="verb">0110</spanx> and <spanx style="verb">0111</spanx> are invalid. The first regular tile contains the C/D RuleID and complete VXLAN header.</t>

<texttable title="Example FCN sequences" anchor="tab-fcn">
      <ttcol align='left'>K</ttcol>
      <ttcol align='left'>FCNs in sender order</ttcol>
      <c>2</c>
      <c>1000, 1111</c>
      <c>3</c>
      <c>1001, 0000, 1111</c>
      <c>4</c>
      <c>1010, 0001, 0000, 1111</c>
      <c>8</c>
      <c>1110, 0101, 0100, 0011, 0010, 0001, 0000, 1111</c>
</texttable>

<t>RFC 8724 Section 8.4.1 permits a profile to set FCN width and define non-All-1 values. This encoding does not by itself change the RFC receiver's behavior.</t>

</section>
<section anchor="reassembly-check-sequence"><name>Reassembly Check Sequence</name>

<t>The RCS is CRC-32C over the entire packet in wire order, including its C/D RuleID and VXLAN header. The Castagnoli polynomial is 0x1edc6f41 (reflected 0x82f63b78); input and output are reflected, the initial register and final XOR are 0xffffffff, and the check value for ASCII <spanx style="verb">123456789</spanx> is 0xe3069283. Serialize the result most significant byte first. The profile chooses CRC-32C instead of the Ethernet CRC recommended in Section 8.2.3 of <xref target="RFC8724"/>. No padding is present for the byte-aligned binding described here. The UDP checksum and RCS detect errors but do not authenticate a sender.</t>

</section>
</section>
<section anchor="sender-procedure"><name>Sender Procedure</name>

<t>Let P be the configured IP PMTU and H the outer IP header size including options and any other encapsulation consuming the same PMTU budget. On an association configured for this profile, the SCHC Packet for an Ethernet frame of E bytes has E+9 bytes. If E+9 &lt;= P-H-8, the sender <bcp14>MUST</bcp14> send the SCHC Packet unfragmented as one UDP payload. On an association not configured for this profile, the sender uses ordinary VXLAN if E+8 &lt;= P-H-8 and otherwise drops and counts the frame.</t>

<t>Otherwise let A be the All-1 header size, 9 or 13 bytes, and set C=P-H-8-A. The sender <bcp14>MUST</bcp14> require C&gt;=9 and compute K=ceil((E+9)/C). K is then at least 2. It <bcp14>MUST</bcp14> reject frames outside configured size limits or K outside 2..8. It snapshots C for the packet, divides the packet into K contiguous nonempty tiles, with every regular tile C bytes and the last tile at most C bytes, and transmits them in order. The unused four-byte RCS allowance in regular fragments keeps the sizing uniform. The IPv4 DF bit <bcp14>MUST</bcp14> be set and IPv6 source fragmentation <bcp14>MUST NOT</bcp14> be used. PMTU discovery is not specified; <xref target="RFC8899"/> describes a possible method. UDP operational considerations are discussed in <xref target="RFC8085"/>.</t>

<t>The sender allocates one DTag for the complete packet and uses the same RuleID and DTag on every fragment. No SCHC ACK, ACK REQ or retransmission is sent. This profile does not send Sender-Abort. Each association must be provisioned so its minimum supported PMTU and maximum frame length fit within eight fragments.</t>

</section>
<section anchor="ordered-receiver"><name>Ordered Receiver</name>

<t>For the ordered receiver, Section 8.4.1 of <xref target="RFC8724"/> governs No-ACK processing. The receiver assembles regular fragment payloads in reception order and resets its inactivity timer on each regular fragment. On All-1 it appends the payload and checks the RCS; if the check fails it drops the packet, and reassembly concludes. On inactivity timer expiry it drops the incomplete packet. The timeout and RCS parameters are configured per rule. An All-1 arriving early is not held for missing fragments by this receiver.</t>

<t>The receiver <bcp14>MUST</bcp14> validate peer association, UDP checksum, rule and local resource bounds. It applies the structural validation below, but does not reorder regular tiles or suppress their duplicates within the RFC No-ACK reassembly procedure. Consequently duplicate regular fragments can cause an integrity failure. Terminal identifiers are subject to the retirement admission policy below. Before delivery it validates the reconstructed VXLAN header and authorizes the VNI for the peer. It learns MAC addresses only after successful reassembly and authorization. CRC checks cannot establish sender identity or prevent intentional collisions. A path that reorders fragments can cause loss even if all fragments arrive.</t>

</section>
<section anchor="structural-validation-and-state-admission"><name>Structural Validation and State Admission</name>

<t>Both receivers <bcp14>MUST</bcp14> validate the UDP checksum and association before accessing reassembly state. An unfragmented SCHC Packet, identified by its C/D RuleID, <bcp14>MUST</bcp14> be at least 23 bytes long (C/D RuleID, VXLAN header and an Ethernet header); a shorter one is malformed. It creates no reassembly state, uses no DTag and no retirement record, and is delivered after the VXLAN header is validated and the VNI authorized, as for a reassembled packet. As with ordinary VXLAN, duplicates of an unfragmented packet are not suppressed. Let h be the regular header length. Datagrams shorter than h are malformed. A header-only All-1 (exactly h bytes) is Sender-Abort under Section 8.3.4 of <xref target="RFC8724"/>; discard and retire any matching active entry without replying. It <bcp14>MUST NOT</bcp14> be interpreted as data. All-1 data requires at least h+5 bytes (four-byte RCS and one payload byte); lengths h+1 through h+4 are malformed. Regular data requires at least h+1 bytes. FCNs 6 and 7 are invalid. A first-marked regular fragment must contain at least nine payload bytes and the configured NoCompress C/D RuleID. Unknown rules, bad lengths, invalid FCNs and invalid checksums are discarded without modifying or allocating packet state.</t>

<t>Check retired identifiers before admission. Each admitted entry reserves capacity for its future retirement record. Enforce maximum retained packet bytes (maximum Ethernet frame length plus nine), maximum tile bytes, entry limits and per-peer/global orphan budgets before allocating or copying. Do not charge identical duplicates twice in the tolerant receiver. State that cannot be admitted is dropped; capacity <bcp14>MUST NOT</bcp14> be recovered by evicting a still-protected retirement record. On terminal completion, abort or timeout, release buffers and retain the identifier for R. A structurally valid fragment conflicting with admitted tolerant state terminates and retires that state; a malformed individual datagram does not.</t>

</section>
<section anchor="optional-reordering-tolerant-receiver"><name>Optional Reordering-Tolerant Receiver</name>

<t>This section describes an experimental receiver extension, not unmodified RFC 8724 No-ACK. In particular, it may hold an early All-1 rather than immediately performing the integrity check and concluding reassembly. Its standards vehicle, including whether an RFC update or a separately specified mode is appropriate, remains open. A sender uses the same ordered sequence and cannot assume a receiver supports this extension without configuration.</t>

<t>The receiver keys state by peer association, direction, RuleID and DTag. Subject to per-peer and global entry and byte limits, any valid fragment may open an entry. An entry opened before the first fragment is an orphan and its VNI is not yet known. A first fragment reveals the C/D RuleID followed by the complete VXLAN header in the NoCompress binding; the receiver checks peer/VNI authorization and applies tenant accounting. It <bcp14>MUST</bcp14> reject unauthorized VNIs and <bcp14>MUST NOT</bcp14> learn MAC addresses before delivery.</t>

<t>The receiver stores each regular fragment by countdown and the final fragment separately. It ignores identical duplicates and aborts on conflicting duplicates. Identity compares the complete FCN and payload, and for All-1 also the RCS. A second first marker with a different countdown is a conflict; a first marker colliding with an already stored non-first position is also a conflict. An All-1 with unchanged payload but a changed RCS is a conflict. When the first marker arrives it supplies n=K-2; the expected regular positions are n down to zero, with the first marker only at n. Stored fragments outside these positions or with incompatible markers cause the entry to be discarded. Regular tiles have equal length, the final tile is no longer, and all bounds are checked before buffering. Completion requires the first fragment, all expected regular positions and All-1. The receiver assembles in countdown order, verifies the RCS once, validates the VXLAN unit and delivers once. On a complete packet with an incorrect RCS it discards immediately.</t>

<t>A fixed total deadline is measured from the first admitted fragment with a monotonic receive timestamp. A fragment arriving at or after the deadline is late. Duplicates do not extend it. A configured inactivity timer may expire sooner; regular arrivals reset that timer. The receiver discards incomplete state at the earlier expiry. Processing queues and batched timer sweeps <bcp14>MUST</bcp14> preserve the decision based on receive timestamps, including fragments received before the deadline but processed later. The deadline bounds reception of pieces, not end-to-end latency.</t>

</section>
<section anchor="dtag-reuse-and-restart"><name>DTag Reuse and Restart</name>

<t>DTag scope is the configured sending association and RuleID, across its VNIs and sender workers. Distinct overlapping packets <bcp14>MUST</bcp14> use distinct DTags as required by <xref target="RFC8724"/>. This proposal also requires a deployment-specific quarantine to prevent late duplicates from being associated with a new packet. Starting from zero on restart is safe only after that quarantine or with a distinguishable new association generation.</t>

<t>Define the following finite deployment bounds and configure them at both endpoints:</t>

<t><list style="symbols">
  <t>S: maximum interval from first to last emission of any fragment copy of a packet. The sender <bcp14>MUST</bcp14> stop emitting the packet when S is reached; queued work cannot resume that packet later.</t>
  <t>B: maximum interval from emission of a copy to its receiver admission timestamp, including network duplication and receive queues. A later locally emitted copy is also subject to S. Let W=S+B, which conservatively bounds the arrival spread.</t>
  <t>I: configured ordered-receiver inactivity timeout. For valid traffic, its maximum entry lifetime is D_ordered=W+I: the final regular arrival occurs within W of first arrival and can restart I.</t>
  <t>Delta: tolerant receiver total deadline. Its maximum entry lifetime is D_tolerant=Delta, irrespective of inactivity resets.</t>
  <t>D: the applicable D_ordered or D_tolerant; when behavior is not fixed, use their maximum.</t>
  <t>R: retirement retention, at least W, including timing margin.</t>
</list></t>

<t>These bounds apply to all copies, including delayed originals after an early timeout. Retaining an identifier for B alone is insufficient: the sender may still be emitting fragments after the receiver has retired it. Retention for W covers that remaining emission span and transport delay. Refreshing retirement on late copies is unnecessary under the stated bounds.</t>

<t>The sender <bcp14>MUST NOT</bcp14> reuse a DTag until Q &gt; B+D+R (including timing margin) after its previous last emission. B+D bounds how late old state may terminate; R then allows its retirement record to expire. If that last-emission time is unknown after restart, wait Q from startup. Packet-rate and width limits <bcp14>MUST</bcp14> prevent wrap before Q; otherwise stop admission. All sender workers and VNIs in the association share allocation. Persistent counter reservations or a receiver-visible generation may avoid restart waiting but are not encoded in this format.</t>

<t>An ordered receiver has no fixed total deadline in RFC 8724; D_ordered is a bound derived from compliant finite emission and delivery, not a new timer that changes its state machine. Repeated hostile traffic is outside that assumption and requires resource controls and authentication. A tolerant receiver uses its actual fixed deadline. Configure I and Delta against W and the desired discard budget; no numeric defaults are implied.</t>

<t>After receiver restart, stop sender admission and drain for W from confirmed cessation of new packet starts before reopening the same association, allowing already started packets their remaining S. Alternatively, after confirmed cessation of all emissions, drain for B. A new generation that rejects old traffic is another option. Blindly waiting B from receiver boot while a sender continues old work is insufficient. These bounds require coordinated configuration; absent defensible limits the suppression guarantee is best effort. Authenticated anti-replay protection is required against intentional replay.</t>

</section>
<section anchor="examples"><name>Examples</name>

<t>With IPv4 without options, P=1500 and H=20, an Ethernet frame of up to 1463 bytes is sent unfragmented, one byte less than ordinary VXLAN carries. With compact headers, C=1463. An untagged 1514-byte Ethernet frame yields a 1523-byte SCHC Packet (one C/D RuleID byte plus a 1522-byte VXLAN payload), split into 1463 and 60 bytes. FCNs are <spanx style="verb">1000</spanx> and <spanx style="verb">1111</spanx>, and outer IP lengths are 1496 and 97 bytes. For a 9014-byte frame, seven fragments suffice. With IPv6 and P=1280, H=40, C=1223 and the same 9014-byte frame requires eight fragments. With IPv4, P=1280 and H=20, a frame of up to 1243 bytes is sent unfragmented and a 1514-byte frame becomes a 1523-byte SCHC Packet split into compact fragments of 1243 and 280 bytes. These figures exclude additional encapsulation and require corresponding configured frame limits.</t>

<t>A four-fragment packet has FCNs <spanx style="verb">1010</spanx>, <spanx style="verb">0001</spanx>, <spanx style="verb">0000</spanx>, <spanx style="verb">1111</spanx>. A tolerant receiver may receive <spanx style="verb">1111</spanx>, <spanx style="verb">0000</spanx>, <spanx style="verb">1010</spanx>, <spanx style="verb">0001</spanx>: it holds the final fragment, learns the expected positions from <spanx style="verb">1010</spanx>, and verifies the RCS after <spanx style="verb">0001</spanx> arrives. An ordered RFC 8724 receiver instead concludes its processing on receipt of the early All-1.</t>

</section>
<section anchor="implementation-and-verification-status"><name>Implementation and Verification Status</name>

<t>The accompanying <spanx style="verb">check_vectors.py</spanx> is an executable wire codec and complete-set reassembly checker for this revision. It verifies the classification and minimum length of unfragmented SCHC Packets, the boundary between unfragmented and fragmented sending, all arrival permutations for K=2..8, missing positions, duplicate and corruption handling, malformed lengths, both header layouts and MTU examples. <spanx style="verb">wire-vectors.json</spanx> contains complete fragment UDP payloads for both variants. It is not a timed receiver or a production implementation: timer races, admission limits, restart coordination and lifetime bounds still require implementation testing and independent review. The older Python reference model applies only to the historical appendix.</t>

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

<t>Only configured peers should be admitted. Bound orphan state, total incomplete packets, per-peer and per-tenant bytes, and retirement records. A VNI is unavailable until the first fragment, so resources used by earlier arrivals cannot be charged to a tenant at admission. A sender can exhaust resources or forge headers; checksums and CRC do not prevent these attacks. Use authenticated transport and anti-replay where the threat model requires them. A receiver must enforce VNI authorization after it learns the VNI and again before delivery as appropriate. Configuration errors, mismatched rules or reuse of identifiers can cause loss or cross-packet mixing.</t>

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

<t>This version requests no IANA action. UDP port assignment, shared SCHC port demultiplexing, RuleID allocation, and any registry implications remain open.</t>

</section>
<section anchor="open-issues"><name>Open Issues</name>

<t><list style="symbols">
  <t>Review the proposed NoCompress VXLAN binding and prefix-free rule provisioning with the working group.</t>
  <t>Determine the standards vehicle for the optional tolerant receiver and its relationship to RFC 8724 and RFC 7348.</t>
  <t>Specify capability provisioning, UDP demultiplexing and any IANA requests.</t>
  <t>Set interoperable timer, packet lifetime, memory and frame-size parameters; validate DTag width against actual rate and restart requirements.</t>
  <t>Define and verify any optional compression rules separately.</t>
</list></t>

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

<t>Thanks to Laurent Toutain for the useful discussions and the inputs regarding NoAck.</t>

</section>


  </middle>

  <back>


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



<reference anchor="RFC7348">
  <front>
    <title>Virtual eXtensible Local Area Network (VXLAN): A Framework for Overlaying Virtualized Layer 2 Networks over Layer 3 Networks</title>
    <author fullname="M. Mahalingam" initials="M." surname="Mahalingam"/>
    <author fullname="D. Dutt" initials="D." surname="Dutt"/>
    <author fullname="K. Duda" initials="K." surname="Duda"/>
    <author fullname="P. Agarwal" initials="P." surname="Agarwal"/>
    <author fullname="L. Kreeger" initials="L." surname="Kreeger"/>
    <author fullname="T. Sridhar" initials="T." surname="Sridhar"/>
    <author fullname="M. Bursell" initials="M." surname="Bursell"/>
    <author fullname="C. Wright" initials="C." surname="Wright"/>
    <date month="August" year="2014"/>
    <abstract>
      <t>This document describes Virtual eXtensible Local Area Network (VXLAN), which is used to address the need for overlay networks within virtualized data centers accommodating multiple tenants. The scheme and the related protocols can be used in networks for cloud service providers and enterprise data centers. This memo documents the deployed VXLAN protocol for the benefit of the Internet community.</t>
    </abstract>
  </front>
  <seriesInfo name="RFC" value="7348"/>
  <seriesInfo name="DOI" value="10.17487/RFC7348"/>
</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="RFC2119">
  <front>
    <title>Key words for use in RFCs to Indicate Requirement Levels</title>
    <author fullname="S. Bradner" initials="S." surname="Bradner"/>
    <date month="March" year="1997"/>
    <abstract>
      <t>In many standards track documents several words are used to signify the requirements in the specification. These words are often capitalized. This document defines these words as they should be interpreted in IETF documents. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements.</t>
    </abstract>
  </front>
  <seriesInfo name="BCP" value="14"/>
  <seriesInfo name="RFC" value="2119"/>
  <seriesInfo name="DOI" value="10.17487/RFC2119"/>
</reference>
<reference anchor="RFC8174">
  <front>
    <title>Ambiguity of Uppercase vs Lowercase in RFC 2119 Key Words</title>
    <author fullname="B. Leiba" initials="B." surname="Leiba"/>
    <date month="May" year="2017"/>
    <abstract>
      <t>RFC 2119 specifies common key words that may be used in protocol specifications. This document aims to reduce the ambiguity by clarifying that only UPPERCASE usage of the key words have the defined special meanings.</t>
    </abstract>
  </front>
  <seriesInfo name="BCP" value="14"/>
  <seriesInfo name="RFC" value="8174"/>
  <seriesInfo name="DOI" value="10.17487/RFC8174"/>
</reference>



    </references>

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



<reference anchor="RFC8085">
  <front>
    <title>UDP Usage Guidelines</title>
    <author fullname="L. Eggert" initials="L." surname="Eggert"/>
    <author fullname="G. Fairhurst" initials="G." surname="Fairhurst"/>
    <author fullname="G. Shepherd" initials="G." surname="Shepherd"/>
    <date month="March" year="2017"/>
    <abstract>
      <t>The User Datagram Protocol (UDP) provides a minimal message-passing transport that has no inherent congestion control mechanisms. This document provides guidelines on the use of UDP for the designers of applications, tunnels, and other protocols that use UDP. Congestion control guidelines are a primary focus, but the document also provides guidance on other topics, including message sizes, reliability, checksums, middlebox traversal, the use of Explicit Congestion Notification (ECN), Differentiated Services Code Points (DSCPs), and ports.</t>
      <t>Because congestion control is critical to the stable operation of the Internet, applications and other protocols that choose to use UDP as an Internet transport must employ mechanisms to prevent congestion collapse and to establish some degree of fairness with concurrent traffic. They may also need to implement additional mechanisms, depending on how they use UDP.</t>
      <t>Some guidance is also applicable to the design of other protocols (e.g., protocols layered directly on IP or via IP-based tunnels), especially when these protocols do not themselves provide congestion control.</t>
      <t>This document obsoletes RFC 5405 and adds guidelines for multicast UDP usage.</t>
    </abstract>
  </front>
  <seriesInfo name="BCP" value="145"/>
  <seriesInfo name="RFC" value="8085"/>
  <seriesInfo name="DOI" value="10.17487/RFC8085"/>
</reference>
<reference anchor="RFC8899">
  <front>
    <title>Packetization Layer Path MTU Discovery for Datagram Transports</title>
    <author fullname="G. Fairhurst" initials="G." surname="Fairhurst"/>
    <author fullname="T. Jones" initials="T." surname="Jones"/>
    <author fullname="M. Tüxen" initials="M." surname="Tüxen"/>
    <author fullname="I. Rüngeler" initials="I." surname="Rüngeler"/>
    <author fullname="T. Völker" initials="T." surname="Völker"/>
    <date month="September" year="2020"/>
    <abstract>
      <t>This document specifies Datagram Packetization Layer Path MTU Discovery (DPLPMTUD). This is a robust method for Path MTU Discovery (PMTUD) for datagram Packetization Layers (PLs). It allows a PL, or a datagram application that uses a PL, to discover whether a network path can support the current size of datagram. This can be used to detect and reduce the message size when a sender encounters a packet black hole. It can also probe a network path to discover whether the maximum packet size can be increased. This provides functionality for datagram transports that is equivalent to the PLPMTUD specification for TCP, specified in RFC 4821, which it updates. It also updates the UDP Usage Guidelines to refer to this method for use with UDP datagrams and updates SCTP.</t>
      <t>The document provides implementation notes for incorporating Datagram PMTUD into IETF datagram transports or applications that use datagram transports.</t>
      <t>This specification updates RFC 4960, RFC 4821, RFC 6951, RFC 8085, and RFC 8261.</t>
    </abstract>
  </front>
  <seriesInfo name="RFC" value="8899"/>
  <seriesInfo name="DOI" value="10.17487/RFC8899"/>
</reference>
<reference anchor="RFC4459">
  <front>
    <title>MTU and Fragmentation Issues with In-the-Network Tunneling</title>
    <author fullname="P. Savola" initials="P." surname="Savola"/>
    <date month="April" year="2006"/>
    <abstract>
      <t>Tunneling techniques such as IP-in-IP when deployed in the middle of the network, typically between routers, have certain issues regarding how large packets can be handled: whether such packets would be fragmented and reassembled (and how), whether Path MTU Discovery would be used, or how this scenario could be operationally avoided. This memo justifies why this is a common, non-trivial problem, and goes on to describe the different solutions and their characteristics at some length. This memo provides information for the Internet community.</t>
    </abstract>
  </front>
  <seriesInfo name="RFC" value="4459"/>
  <seriesInfo name="DOI" value="10.17487/RFC4459"/>
</reference>

<reference anchor="I-D.ietf-schc-protocol-numbers">
   <front>
      <title>Protocol Numbers for SCHC</title>
      <author fullname="Robert Moskowitz" initials="R." surname="Moskowitz">
         <organization>HTT Consulting</organization>
      </author>
      <author fullname="Pascal Thubert" initials="P." surname="Thubert">
         </author>
      <author fullname="Carles Gomez" initials="C." surname="Gomez">
         <organization>UPC</organization>
      </author>
      <author fullname="Ana Minaburo" initials="A." surname="Minaburo">
         <organization>Consultant</organization>
      </author>
      <author fullname="Marc Blanchet" initials="M." surname="Blanchet">
         <organization>Viagenie</organization>
      </author>
      <date day="23" month="December" year="2025"/>
      <abstract>
	 <t>   This document requests an Internet Protocol Number, an Ethertype
   assignment, a CCSDS (Consultative Committee for Space Data Systems)
   Encapsulation Number, and well known ports for SCHC.  The SCHC
   architecture, the SCHC instance establishment, and the SCHC
   compression/decompression processes are simplified when SCHC is
   easily recognised.  Well-known protocol and port numbers are needed.
   The Internet Protocol Number request is so that SCHC can be used for
   IP independent of other transports such as UDP and ESP.  The
   Ethertype and the CCSDS Encapsulation Number are to support generic
   use of native SCHC over any IEEE 802 technology and CCSDS link layer
   technology, respectively, for IP and non-IP protocols.

	 </t>
      </abstract>
   </front>
   <seriesInfo name="Internet-Draft" value="draft-ietf-schc-protocol-numbers-06"/>
   
</reference>



    </references>


<?line 186?>

<section anchor="earlier-indexed-out-of-order-proposal"><name>Earlier Indexed Out-of-Order Proposal</name>

<t>This appendix is informative and preserves the earlier draft's technical sections for comparison. Its capitalized requirements describe only the historical alternative, not conformance requirements for the principal profile. Statements that an out-of-order receiver requires a total count in every fragment are superseded by the first-marker/countdown construction in the main text. Historical port-assignment claims below are not current allocation guidance. Its wire format and procedures are an alternative, not part of the main profile above; statements within this appendix describe that earlier proposal. The existing reference model and generated examples apply to this appendix only. The original standalone source remains available separately.</t>

<section anchor="introduction-1"><name>Introduction</name>

<t>VXLAN <xref target="RFC7348"/> carries Ethernet frames in UDP datagrams. When the encapsulated frame exceeds the underlay IP path MTU (PMTU), standard VXLAN cannot carry it, and VTEPs <bcp14>MUST NOT</bcp14> fragment VXLAN packets (Section 4.3 of <xref target="RFC7348"/>). This document specifies an extension that fragments such a frame into several UDP datagrams between a pair of VTEPs, reassembles it at the receiver, and delivers it only after successful reassembly. General guidance on UDP usage and on MTU issues with tunnels is in <xref target="RFC8085"/> and <xref target="RFC4459"/>.</t>

<t>This version is a framing proposal, presented to seek working group feedback and adoption. Its wire format is provisional and several parameters are left as open issues.</t>

<t>The requirements are:</t>

<t><list style="symbols">
  <t>Preserve the full input Ethernet frame as presented to the tunnel, including any tags carried by the tunnel, and excluding the Ethernet FCS.</t>
  <t>Keep standard VXLAN for frames that fit.</t>
  <t>Deliver a fragmented frame only after successful reassembly, with bounded waiting time and bounded receiver state.</t>
  <t>Tolerate reordering of fragments.</t>
  <t>Use no acknowledgments and no retransmissions in the data path.</t>
</list></t>

<t>The following are non-goals:</t>

<t><list style="symbols">
  <t>Acknowledgment, retransmission or any other loss recovery. A frame with a missing fragment is discarded at its deadline.</t>
  <t>Inter-frame ordering. Frames are delivered as they complete, and the design gives no ordering guarantee between frames on the ordinary path and frames on the fragmented path.</t>
  <t>Header compression, which is outside the scope of this document.</t>
</list></t>

<t>Line rate is a performance target that depends on the traffic mix, the link rate and the packet expansion. This document makes no throughput claim; any such figure is pending measurement.</t>

<t>The first version targets statically provisioned unicast VTEP pairs in a managed fabric. The wire values in this document are provisional prototype choices.</t>

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

<t>The key words in this appendix have the meanings defined in the main text.</t>

<t>The following terms are used in this document.</t>

<dl>
  <dt>VTEP:</dt>
  <dd>
    <t>VXLAN Tunnel End Point, as in <xref target="RFC7348"/>.</t>
  </dd>
  <dt>PMTU:</dt>
  <dd>
    <t>The underlay IP path MTU, excluding outer Ethernet overhead. It is a sender-side configuration value per peer and direction.</t>
  </dd>
  <dt>Slice:</dt>
  <dd>
    <t>A nonempty contiguous part of the original Ethernet frame carried in one fragment.</t>
  </dd>
  <dt>Frame ID:</dt>
  <dd>
    <t>An 8-byte identifier, unique across active and recently retired frames within the configured peer association and VNI.</t>
  </dd>
  <dt>RCS:</dt>
  <dd>
    <t>Reassembly Check Sequence, a CRC-32C over the original frame bytes, carried at the end of the final fragment.</t>
  </dd>
  <dt>Δ:</dt>
  <dd>
    <t>The discard deadline. A reassembly entry expires at the first arrival time plus Δ.</t>
  </dd>
  <dt>L:</dt>
  <dd>
    <t>A configured upper bound on the arrival spread of all copies of fragments of one frame, including duplicates. Retirement records are kept for L after retirement.</t>
  </dd>
  <dt>Peer association:</dt>
  <dd>
    <t>The configured relationship between a local tunnel endpoint and a remote VTEP, with its RuleID, PMTU, port, and capabilities.</t>
  </dd>
</dl>

</section>
<section anchor="placement-and-interoperability"><name>Placement and Interoperability</name>

<t>Transmit placement is after bridge forwarding and before tunnel encapsulation. Receive placement is after tunnel classification and before bridge ingress. Both paths feed the same VNI-to-bridge mapping. A VTEP learns source MAC addresses only from complete frames.</t>

<t>A sender behaves as follows:</t>

<t><list style="symbols">
  <t>If the frame fits, it emits RFC 7348 VXLAN.</t>
  <t>If the frame exceeds the VXLAN payload budget and both peers are configured for the extension, it encapsulates each slice in a separate UDP datagram sent to a distinct, configured destination port.</t>
  <t>If the extension is unavailable or the configured limits cannot carry the frame, it drops the oversized frame and increments a local counter (drop-and-count).</t>
</list></t>

<t>Scope is unicast between VTEPs. BUM traffic is in scope only through ingress replication to individually provisioned unicast peers. Each copy uses that peer's capabilities and PMTU.</t>

<t>The extension carries the semantics of the Ethernet overlay VNI but uses its own UDP payload format. It does not fragment an already encapsulated VXLAN packet at IP. The configured UDP destination port selects this format. The sender uses the same source UDP port and outer five-tuple for every fragment of a frame, so that ordinary flow-hash affinity applies, and derives the source port from the inner frame as it does for ordinary VXLAN (Section 5 of <xref target="RFC7348"/>). The receiver identifies a configured peer independently of the source UDP port. The protocol tolerates reordering even when path affinity fails.</t>

<t>NAT is outside the target deployment. Where one is present: a rewritten source port does not matter; a rewritten outer source address must be the address configured for the peer association; and because the two directions do not form one symmetric flow, the destination port needs a static mapping.</t>

<t>The wire format and all values in this document are provisional prototype choices and are subject to change. The UDP port is locally configured in this version.</t>

<t>Open Issue: UDP demultiplexing, header versioning, any IANA request, and the need for peer capability provisioning before oversized frames are sent are not settled in this version.</t>

</section>
<section anchor="relationship-to-schc"><name>Relationship to SCHC</name>

<t>Section 8.4.1 of <xref target="RFC8724"/> defines the No-ACK fragmentation mode. It assumes in-order delivery of fragments and concludes reassembly on All-1. The indexed receiver in this document can accept the final fragment first and wait for missing indices, so No-ACK does not fit.</t>

<t>A Profile can set the FCN size above one bit and define FCN values other than All-1 (Section 8.4.1 of <xref target="RFC8724"/>), so a No-ACK Profile with several fragments is possible. It still lacks what an out-of-order receiver needs. The All-1 value identifies the end, but nothing in the fragments states how many fragments the frame has. A receiver that holds the All-1 fragment and several others cannot tell whether it holds all of them, unless the Profile fixes the fragment count; here the count varies with the frame length. Carrying the count in every fragment, with an ascending index, lets any fragment, including the final one, open an entry with a bitmap of the right size.</t>

<t>This document defines a new SCHC fragmentation mode, named Out-of-Order No-ACK, with a UDP/Ethernet binding. It is a new mode defined by its differences from No-ACK, not an extension of No-ACK. Open Issue: how the mode integrates with the SCHC framework is pending working-group agreement.</t>

<t>The mode differs from No-ACK in three ways:</t>

<t><list style="symbols">
  <t><strong>Index and count instead of FCN.</strong> In No-ACK, the FCN All-1 value only signals the last tile (Section 8.2.4 of <xref target="RFC8724"/>), the recommended FCN size is one bit, and the meaning of other values is left to the Profile (Section 8.4.1 of <xref target="RFC8724"/>). That suffices for an in-order receiver. A receiver that may see the final fragment first needs the position of every fragment and the total number of fragments from whichever fragment arrives first. Each fragment therefore carries an ascending index and the count. The index plays the role of the FCN; the count has no RFC 8724 counterpart.</t>
  <t><strong>Fixed deadline instead of Inactivity Timer.</strong> The No-ACK receiver resets the Inactivity Timer on each Regular fragment (Section 8.4.1.2 of <xref target="RFC8724"/>). Here the deadline is fixed at the first arrival and never extended.</t>
  <t><strong>Frame ID and retirement record.</strong> The Frame ID plays the role of DTag, sized so that a retired frame stays recognizable while late fragments can still arrive.</t>
</list></t>

<t>The mapping of the fields of this document to SCHC terms is as follows.</t>

<texttable title="Mapping of fields to SCHC terms" anchor="schc-mapping">
      <ttcol align='left'>Field</ttcol>
      <ttcol align='left'>SCHC term</ttcol>
      <ttcol align='left'>Status</ttcol>
      <c>RuleID</c>
      <c>RuleID</c>
      <c>Open Issue: mapping to SCHC architecture unconfirmed. One byte, configured per peer association, value 0 in the prototype.</c>
      <c>Frame ID</c>
      <c>DTag (role)</c>
      <c>Open Issue: mapping unconfirmed; width of 8 bytes is a prototype choice.</c>
      <c>Fragment index</c>
      <c>FCN (role)</c>
      <c>Open Issue: mapping unconfirmed.</c>
      <c>Fragment count</c>
      <c>none</c>
      <c>No RFC 8724 counterpart.</c>
      <c>RCS</c>
      <c>RCS</c>
      <c>Open Issue: mapping unconfirmed. CRC-32C on the final fragment, in line with the integrity check of Sections 8.2.3 and 8.4.1 of <xref target="RFC8724"/>.</c>
</texttable>

<t>RuleID comes first in the header, as in other SCHC messages, so that the format can later share a SCHC UDP port with other SCHC uses. A zero-bit RuleID is not used, because RFC 8724 leaves the RuleID size to the Profile and a whole byte preserves alignment.</t>

<t>The prototype wire format has no wire compatibility with RFC 8724. A deployment with a genuine in-order guarantee could instead specify a separate RFC 8724 No-ACK profile. Header compression is outside the scope of this document.</t>

</section>
<section anchor="fragment-format-1"><name>Fragment Format</name>

<t>This section defines the UDP payload of each fragment. The wire values are provisional prototype choices. The format has no wire compatibility with <xref target="RFC8724"/>.</t>

<t>All multibyte integers use network byte order. The UDP destination port, configured locally, selects this format. The RuleID comes first, as in other SCHC messages, so that the format can later share a SCHC UDP port with other SCHC uses and be selected by RuleID.</t>

<section anchor="header"><name>Header</name>

<t>Every fragment starts with a 14-byte header, followed by a nonempty slice of the original frame. The final fragment ends with a 4-byte RCS.</t>

<figure title="Fragment format" anchor="fig-format"><artwork><![CDATA[
 0                   1                   2                   3
 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|    RuleID     |                      VNI                      |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|                                                               |
+                           Frame ID                            +
|                                                               |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|     Index     |     Count     |   Slice (variable) ...
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+                               |
|                                                               |
~                              ...                              ~
|                                                               |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|          RCS (final fragment only, 4 bytes)                   |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
]]></artwork></figure>

<texttable title="Fragment fields" anchor="tab-fields">
      <ttcol align='left'>Byte offset</ttcol>
      <ttcol align='left'>Size</ttcol>
      <ttcol align='left'>Field</ttcol>
      <c>0</c>
      <c>1</c>
      <c>RuleID, configured per peer association; value 0 in the prototype</c>
      <c>1</c>
      <c>3</c>
      <c>VNI, with the same meaning as in the associated VXLAN deployment</c>
      <c>4</c>
      <c>8</c>
      <c>Frame ID, unique across active and recently retired frames within the configured peer association and VNI</c>
      <c>12</c>
      <c>1</c>
      <c>Fragment index, zero-based</c>
      <c>13</c>
      <c>1</c>
      <c>Fragment count, 2 through the configured maximum</c>
      <c>14</c>
      <c>variable</c>
      <c>Nonempty slice of the original frame</c>
      <c>End of final fragment</c>
      <c>4</c>
      <c>RCS, present only if index equals count minus one</c>
</texttable>

<t>There is no original-length field. The receiver relies on the fragment count, the equal-length nonfinal slices, the configured maximum frame length and the RCS.</t>

<t>The RuleID is one byte, so that the header stays byte-aligned; a zero-bit RuleID is not used. Section 6 of <xref target="RFC8724"/> leaves the RuleID size to the Profile. The RuleID is configured per peer association and is 0 in the prototype.</t>

</section>
<section anchor="mode-fields-and-binding-fields"><name>Mode Fields and Binding Fields</name>

<t>The Out-of-Order No-ACK mode proper consists of the RuleID, the Frame ID, the fragment index, the fragment count, the slice and the RCS, together with the receiver procedure and the discard deadline. The UDP/Ethernet binding for VXLAN consists of the VNI, the UDP destination port and UDP checksum, the use of an Ethernet frame without FCS as the fragmented unit, and the PMTU-derived slice budget of the sender procedure. The binding is kept explicit so that the mode can later be separated from it.</t>

<t>Open Issue: whether the mode and the binding remain in one document is not settled.</t>

</section>
<section anchor="reassembly-check-sequence-1"><name>Reassembly Check Sequence</name>

<t>The final fragment, and only the final fragment, carries a 4-byte RCS after its slice. It is the CRC-32C of the original frame bytes in wire order, serialized big-endian. The RCS guards against splicing slices of different frames, for example after a restart. It covers the frame bytes only and checks reassembly integrity; it does not protect the header.</t>

<t>CRC-32C is defined as follows:</t>

<t><list style="symbols">
  <t>Polynomial: the Castagnoli polynomial, 0x1edc6f41 (0x82f63b78 in reflected form).</t>
  <t>Input and output are reflected.</t>
  <t>The initial register value is 0xffffffff.</t>
  <t>The final XOR value is 0xffffffff.</t>
  <t>The check value for the ASCII string <spanx style="verb">123456789</spanx> is 0xe3069283.</t>
  <t>The result is serialized as four bytes, most significant byte first.</t>
</list></t>

</section>
<section anchor="udp-checksum"><name>UDP Checksum</name>

<t>A sender <bcp14>MUST</bcp14> generate the UDP checksum on every extension datagram, over IPv4 as well as IPv6. A receiver <bcp14>MUST</bcp14> drop an extension datagram whose UDP checksum is zero or incorrect. This differs from Section 5 of <xref target="RFC7348"/>, which recommends a zero UDP checksum for VXLAN. Here the UDP checksum is the only protection of the fragment header.</t>

</section>
<section anchor="udp-port-selection"><name>UDP Port Selection</name>

<t>The UDP destination port is selected by configuration and identifies this format, distinct from the port used for ordinary VXLAN. Each sender is configured with the destination port on which its peer receives this format.</t>

<t>Historical open issue: this alternative used a locally configured UDP port and did not settle shared-port demultiplexing, version indication or RuleID allocation. The current status and applicability of <xref target="I-D.ietf-schc-protocol-numbers"/> must be checked separately; this appendix makes no claim about its current allocations.</t>

</section>
<section anchor="provisional-status"><name>Provisional Status</name>

<t>The field sizes, offsets and the RuleID value in this section are provisional prototype choices and may change before any interoperable specification. A reference model implements exactly this layout (historical reference model).</t>

</section>
</section>
<section anchor="sender-procedure-1"><name>Sender Procedure</name>

<t>The PMTU used here is the underlay IP path MTU, excluding outer Ethernet overhead. <spanx style="verb">H_IP</spanx> is the length of the actual outer IP header, including any options or extension headers, and any further encapsulation that consumes the same PMTU budget.</t>

<t>PMTU is a sender configuration value per peer and per direction. This document defines no default PMTU; the value 1500 appears only in examples. The receiver does not need the sender's PMTU and <bcp14>MUST NOT</bcp14> assume a slice length.</t>

<t>The ordinary VXLAN frame budget is:</t>

<figure><artwork><![CDATA[
PMTU - H_IP - 8 (UDP) - 8 (VXLAN)
]]></artwork></figure>

<t>The slice budget <spanx style="verb">C</spanx> is the same for every fragment of a frame:</t>

<figure><artwork><![CDATA[
C = PMTU - H_IP - 8 (UDP) - 14 (fragment header) - 4 (RCS allowance)
]]></artwork></figure>

<t>Nonfinal datagrams therefore leave four bytes unused, which removes a sizing special case for the final fragment.</t>

<t>For each Ethernet frame (as presented to the tunnel, without FCS) the sender proceeds as follows.</t>

<t><list style="numbers" type="1">
  <t>If the frame fits the ordinary VXLAN frame budget, it emits RFC 7348 VXLAN.</t>
  <t>Otherwise, if the peer is not configured for this extension, it drops the frame and increments a local counter.</t>
  <t>It validates <spanx style="verb">C &gt; 0</spanx>, computes <spanx style="verb">N = ceil(frame_length / C)</spanx>, and drops the frame if the length is outside the configured frame-length range or <spanx style="verb">N</spanx> is outside the configured fragment-count range (2 through the configured maximum).</t>
  <t>It takes a snapshot of the budget once per frame, so a PMTU change affects only later frames.</t>
  <t>It sends the slices in ascending index order. Every slice has <spanx style="verb">C</spanx> bytes except the final one, which carries the remainder followed by the 4-byte RCS. Every outer IP datagram fits the PMTU.</t>
</list></t>

<t>A configuration <bcp14>MUST</bcp14> be rejected if the minimum configured PMTU cannot carry the maximum frame length in the maximum number of fragments.</t>

<t>All fragments of a frame use the same outer five-tuple, in particular the same source UDP port. The sender derives that port from the inner frame as it does for ordinary VXLAN (<xref target="RFC7348"/>, Section 5), to preserve flow-hash affinity. The receiver identifies the peer independently of the source UDP port, and the protocol tolerates reordering even when path affinity fails.</t>

<t>For IPv4 the sender sets DF. For IPv6 the sender does not use source fragmentation.</t>

<t>Worked numbers with PMTU 1500, no outer IP options or extension headers: standard VXLAN carries complete Ethernet frames of up to 1464 bytes over IPv4 (<spanx style="verb">H_IP</spanx> = 20) and 1444 bytes over IPv6 (<spanx style="verb">H_IP</spanx> = 40). The slice budgets are 1454 and 1434 bytes. Over IPv4, a 1514-byte frame produces slices of 1454 and 60 bytes; the outer IP lengths are 1496 and 106 bytes (the final datagram carries 60 + 14 + 4 + 8 + 20).</t>

<t>The first version uses a conservative static PMTU per peer and path. Open Issue: dynamic discovery is not specified. If it is specified later, it has to describe how the extension probes its own path, including ECMP and path changes; see RFC 8899 <xref target="RFC8899"/>.</t>

</section>
<section anchor="receiver-procedure"><name>Receiver Procedure</name>

<t>The wire format carries no original-length field. The receiver relies on the fragment count, on equal-length nonfinal slices, on the configured maximum frame length and on the RCS. It does not assume a slice length.</t>

<t>An entry is keyed by the configured peer association (including the local tunnel endpoint), VNI, RuleID and Frame ID. Because the RuleID of an association is configured and a mismatch is dropped, it does not distinguish entries within an association. A single worker or equivalent synchronization owns each entry. The receiver uses a local monotonic clock for admission, expiry and delivery decisions.</t>

<t><list style="numbers" type="1">
  <t><strong>Validation before allocation.</strong> Before allocating state the receiver <bcp14>MUST</bcp14> check that: the peer and VNI are authorized; the UDP checksum is nonzero and correct; the RuleID equals the value configured for the peer association (a mismatch is counted as a peer admission failure); the count is at least 2 and at most the configured maximum; the index is less than the count; the slice length does not exceed the receiver's configured maximum slice length; and a nonempty slice remains after the header and any required trailer, so that a final fragment carries at least one slice byte and the 4-byte RCS. The maximum slice length is a local bound, at most the configured maximum frame length. A datagram that fails the checksum or bounds checks is dropped and counted as malformed. Caps on incomplete entries and retained bytes apply per peer and globally. If admitting a fragment would exceed a cap, the fragment is dropped and counted as table exhaustion; an existing entry stays pending until its deadline.</t>
  <t><strong>Admission and expiry.</strong> A fragment for a retired ID, whether the frame completed, aborted or expired, is dropped and counted as late. The first admissible fragment, of any index, opens an entry with <spanx style="verb">expiry = first_rx + Δ</spanx>; the deadline is never extended. Expiry is decided by the arrival timestamp <spanx style="verb">t</spanx> alone, taken at a consistent receive stage. Expired entries are ineligible for completion even if no timer sweep has run: a fragment that finds an expired entry retires it as expired (counted once) and is itself counted as late. Timer processing can be batched.</t>
  <t><strong>Consistency and duplicates.</strong> The count <bcp14>MUST</bcp14> match across the entry, every nonfinal slice <bcp14>MUST</bcp14> have the same length, and the final slice <bcp14>MUST</bcp14> be no longer than a nonfinal slice. The receiver stores one slice per index and updates a bitmap and a running byte count. An identical duplicate, meaning a fragment with the same index and the same slice and, for the final fragment, the same RCS, is ignored and does not extend expiry. A fragment with the same index but a different slice or, for the final fragment, a different RCS is a conflicting duplicate. A conflicting duplicate, inconsistent metadata, or a byte count above the maximum frame length aborts and retires the entry.</t>
  <t><strong>Completion.</strong> When the bitmap is complete, the sum of the slice lengths <bcp14>MUST</bcp14> lie within the configured frame-length range. The receiver assembles the slices in index order, verifies the RCS and delivers the frame once. The frame is eligible if the arrival timestamp of the completing fragment is before expiry; assembly and verification time after that arrival is budgeted in <spanx style="verb">Δ</spanx>. A full bitmap with an invalid length or RCS aborts the entry.</t>
  <t><strong>Retirement.</strong> On completion, abort or timeout the receiver retires the ID and releases the buffers. A final fragment with holes stays pending until the holes fill or the deadline passes.</t>
</list></t>

<t>Open Issue: the deadline equality rule. The reference receiver treats <spanx style="verb">t &gt;= expiry</spanx> as expired, so a fragment arriving exactly at the deadline is late. This is a recommendation pending working group input.</t>

<t>Because an entry may start from any index, a fragment of a retired frame can arrive after retirement and would otherwise open a new entry. A bounded retirement record suppresses such late fragments and duplicate delivery. A record <bcp14>MUST NOT</bcp14> be evicted while the deployment still allows fragments for that ID to arrive. For the first version, <spanx style="verb">L</spanx> is configured as an upper bound on the arrival spread of all copies of the fragments of a frame, including duplicates, and a record is kept for <spanx style="verb">L</spanx> after retirement. Capacity for active and retired IDs is either provisioned for the admitted rate, or a retirement slot is reserved at admission, as the reference receiver does; new IDs are then not admitted within an exhausted scope until space returns. Drops before admission create no deliverable state. Without a defensible bound on <spanx style="verb">L</spanx>, suppression through finite retention is best effort.</t>

<t>Starting from any index supports reordering because every fragment carries its own index and the count, so the first fragment to arrive, including the final one, is enough to open an entry and size its bitmap, and missing indices simply stay pending.</t>

<t>The receiver maintains counters for: completed frames, expiration, late fragments, duplicates, integrity failure (inconsistent metadata, conflicting duplicates, bad length or RCS), malformed input, peer admission failure, and table exhaustion. Expiration and lateness are reported separately: expiration records incompleteness observed at the cutoff, while a late fragment, meaning any fragment of a retired Frame ID, is positive evidence of lateness. A duplicate is an identical fragment received while its entry is still active; an identical fragment arriving after retirement is late, not a duplicate.</t>

</section>
<section anchor="discard-deadline"><name>Discard Deadline</name>

<t>A receiver can observe incompleteness only at the cutoff. At that moment it cannot tell whether a missing fragment was lost or will arrive later. A fragment received after expiry is positive evidence of lateness. An implementation <bcp14>SHOULD</bcp14> report the two events separately: an expired entry with missing fragments (incompleteness, loss or lateness not distinguished) and a fragment arriving after expiry or retirement (late).</t>

<t>The deadline is <spanx style="verb">expiry = first_rx + Δ</spanx>, fixed at the first admissible fragment and never extended. The prototype rule, subject to the Open Issue below, is that an entry is expired for any fragment whose arrival timestamp <spanx style="verb">t</spanx> satisfies <spanx style="verb">t &gt;= expiry</spanx>.</t>

<section anchor="choosing-"><name>Choosing Δ</name>

<t>For a deterministic path, <spanx style="verb">Δ</spanx> is budgeted from three terms:</t>

<t><list style="symbols">
  <t>the maximum sender emission span for the fragments of one frame;</t>
  <t>the maximum differential path delay between fragments of the same frame; and</t>
  <t>the maximum receiver scheduling, processing and clock-resolution margin, which includes assembly and RCS verification after the completing fragment arrives.</t>
</list></t>

<t>An absolute maximum one-way latency can inform the differential bound, but it is the spread between pieces of the same frame that drives this timer.</t>

<t>For a best-effort path, the operator measures the spread under realistic contention and chooses the cutoff against the service's latency and discard budgets. The observation stage at which arrival timestamps are taken is defined when benchmarking, and <bcp14>MUST</bcp14> be applied consistently within a receiver.</t>

</section>
<section anchor="scope-of-the-deadline"><name>Scope of the Deadline</name>

<t>The first-arrival deadline bounds only the time the receiver holds a frame for reassembly. It is not an end-to-end frame age bound. An end-to-end bound requires a separate age mechanism, such as sender timestamps with bounded clock error, which is outside the base format of this document.</t>

</section>
</section>
<section anchor="frame-identification-and-restart"><name>Frame Identification and Restart</name>

<t>The Frame ID is a 64-bit counter. The sender uses one monotonic counter per sending association and VNI, and every frame fragmented in that scope takes the next value. A Frame ID <bcp14>MUST</bcp14> be unique across active and recently retired frames within the configured peer association and VNI. The counter starts at any value chosen by the sender. At 64 bits, wrapping is not expected within the lifetime of a deployment, and behaviour at wrap is not specified. The 8-byte width is a prototype choice kept for alignment; the width itself is an Open Issue.</t>

<section anchor="sender-restart"><name>Sender Restart</name>

<t>A sender restart must not result in the reuse of a Frame ID that a receiver may still hold as active or retired. This is a requirement on the deployment; the mechanism is an Open Issue. Two approaches are candidates, and neither is specified in this version:</t>

<t><list style="symbols">
  <t>it persists counter allocation, so that after a restart the counter resumes above every value previously used; or</t>
  <t>it establishes a new association generation that the receiver can distinguish, and the receiver rejects the old generation.</t>
</list></t>

</section>
<section anchor="receiver-restart"><name>Receiver Restart</name>

<t>A receiver that loses its retirement records can accept late or duplicate fragments of frames it already delivered or retired. If duplicate suppression must survive a receiver restart, the receiver needs either a fresh association or a drain interval before it reopens the old association. The drain interval covers the residual packet lifetime of the deployment.</t>

<t>The CRC-32C RCS provides a partial safeguard: it guards against splicing slices of different frames, for example after a restart. It does not replace Frame ID uniqueness.</t>

</section>
<section anchor="status"><name>Status</name>

<t>The prototype puts no epoch or generation value on the wire. Restart-safe interoperability is not claimed.</t>

<t>Open Issue: the restart and generation mechanism is not specified. It covers how a new association generation is signalled and distinguished, how the old generation is rejected, how counter persistence is performed and the length of the receiver drain interval. Until it is specified, this document makes no claim of restart-safe interoperability.</t>

</section>
<section anchor="retirement-bound-l"><name>Retirement Bound L</name>

<t>Frame ID uniqueness depends on the retirement bound <spanx style="verb">L</spanx>. The retirement record of a frame is kept for <spanx style="verb">L</spanx> after retirement. In the first prototype, <spanx style="verb">L</spanx> is configured as an upper bound on the arrival spread of all copies of the fragments of a frame, including duplicates. A receiver <bcp14>MUST NOT</bcp14> evict a retirement record while the deployment still allows fragments for that Frame ID to arrive. Without a defensible bound, suppression through finite retention is best effort.</t>

</section>
</section>
<section anchor="default-operational-profile"><name>Default Operational Profile</name>

<t>This section describes the prototype operating point. It is not a claim of general suitability.</t>

<section anchor="fragment-count"><name>Fragment Count</name>

<t>The profile starts with a configured maximum of two fragments. This is valid where the minimum configured PMTU carries the maximum allowed frame in two slices, for example an Ethernet-1500 service over a 1500-byte PMTU. The receiver can then keep a two-bit receive mask and bounded per-worker state.</t>

</section>
<section anchor="minimum-pmtu-validation"><name>Minimum-PMTU Validation</name>

<t>A configuration <bcp14>MUST</bcp14> be rejected if the minimum configured PMTU cannot carry the maximum frame length in the maximum number of fragments. Validation uses the slice budget <spanx style="verb">C</spanx> for each configured peer and direction, with the actual <spanx style="verb">H_IP</spanx>.</t>

</section>
<section anchor="configured-bounds"><name>Configured Bounds</name>

<t>An implementation provides the following configured values:</t>

<t><list style="symbols">
  <t>the maximum frame length, and the frame-length range accepted;</t>
  <t>the maximum fragment count (2 in the profile above), and the minimum count of 2;</t>
  <t>the receiver's maximum slice length, a local bound that does not exceed the maximum frame length;</t>
  <t>caps on incomplete entries and retained bytes per peer and globally; and</t>
  <t>capacity for retirement records at the admitted rate, or a reservation of a retirement slot at admission with admission stopped within an exhausted scope until space returns.</t>
</list></t>

</section>
<section anchor="meaning-and-configuration-of-and-l"><name>Meaning and Configuration of Δ and L</name>

<t><spanx style="verb">Δ</spanx> is the receiver-held reassembly time measured from the first admissible fragment, chosen as described above. <spanx style="verb">L</spanx> is the retention time of a retirement record, measured from retirement, bounding the arrival spread of all copies of a frame. Both are local receiver configuration. Neither value is carried on the wire.</t>

<t>Open Issue: this document gives no numeric default for <spanx style="verb">Δ</spanx> or <spanx style="verb">L</spanx>, for the maximum frame length, or for the entry and byte caps. The values depend on the path and on measurement. They are not set here.</t>

<t>Open Issue: the deadline equality rule is that the prototype treats <spanx style="verb">t &gt;= expiry</spanx> as expired, so a fragment arriving exactly at the deadline is late. Whether this is the final rule is to be confirmed.</t>

</section>
</section>
<section anchor="manageability-considerations"><name>Manageability Considerations</name>

<t>This extension is configured, not negotiated. An implementation <bcp14>MUST</bcp14> provide configuration for the following items, and an operator is responsible for keeping both ends of each peer association consistent:</t>

<t><list style="symbols">
  <t>the set of peer associations, each identifying the local tunnel endpoint, the peer address and the RuleID (0 in the prototype);</t>
  <t>the VNIs admitted on each peer association;</t>
  <t>the UDP destination port of the fragment format, which is locally configured in this version and distinct from the ordinary VXLAN port;</t>
  <t>the configured PMTU per peer association, from which the slice budget <spanx style="verb">C</spanx> is derived;</t>
  <t>the receiver limits: the discard deadline <spanx style="verb">Δ</spanx>, the arrival-spread bound <spanx style="verb">L</spanx> used for retirement records, the maximum number of fragments per frame (initially two), the maximum slice length, and the capacity of active and retired entries per scope.</t>
</list></t>

<t>Peer capability for the extension has to be provisioned before a sender emits oversized frames. How a peer's capability is learned is an Open Issue; this version relies on static provisioning.</t>

<t>An implementation <bcp14>SHOULD</bcp14> expose counters, kept per peer association and VNI where practical, for: frames fragmented; oversized frames dropped because the extension is unavailable or the limits cannot carry them; frames completed; entries expired with missing fragments; fragments received after expiry or retirement (late); duplicate fragments; integrity (RCS) failures; malformed input, including zero UDP checksums; peer or VNI admission failures; and table exhaustion. Expiry with missing fragments and late arrival are reported separately, as described in the discard deadline section.</t>

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

<t>This document defines no cryptographic protection. The first version targets statically provisioned unicast VTEP pairs in a managed fabric, and the considerations below assume that deployment.</t>

<section anchor="peer-and-vni-admission"><name>Peer and VNI Admission</name>

<t>A receiver <bcp14>MUST</bcp14> identify a configured peer association from the outer source address and the local tunnel endpoint, independently of the source UDP port, and <bcp14>MUST</bcp14> drop fragments from sources that match no association. A receiver <bcp14>MUST</bcp14> also drop fragments whose VNI is not admitted for that association. Drops at this stage occur before admission and create no reassembly state.</t>

</section>
<section anchor="spoofing"><name>Spoofing</name>

<t>Nothing in the fragment header authenticates the sender. A party able to inject packets with a forged outer source address can send fragments that appear to come from a configured peer, and can thereby inject frames into an admitted VNI or consume reassembly state. The CRC-32C RCS and the UDP checksum detect accidental corruption only. They are not keyed and provide no peer authentication or integrity against an attacker. A zero UDP checksum is dropped, which removes no spoofing exposure. Where spoofing is a concern, the deployment <bcp14>SHOULD</bcp14> use an authenticated underlay, such as an IPsec association or a fabric with source-address validation at its edges, or equivalent filtering that restricts the sources able to reach the configured port.</t>

<t>Because Frame IDs are a sequential counter, an attacker that can inject packets can open the next expected Frame ID with a wrong count, or send fragments that conflict with those of a genuine frame, so that the genuine frame is aborted. An unpredictable initial value only raises the cost of guessing, because the increments stay observable on the wire. The mitigation is the authenticated underlay described above.</t>

</section>
<section anchor="state-exhaustion"><name>State Exhaustion</name>

<t>Reassembly state is the main resource an attacker can consume. The receiver bounds it by construction: entries are keyed by peer association, VNI, RuleID and Frame ID, the number of fragments per frame and the slice length are bounded, and every entry expires at <spanx style="verb">first_rx + Δ</spanx>, never extended. Because retirement records are kept for <spanx style="verb">L</spanx>, an attacker that opens many Frame IDs also occupies retirement capacity. A receiver <bcp14>SHOULD</bcp14> apply the capacity limits per scope so that one peer or VNI cannot exhaust the state of others, and when a scope is exhausted it <bcp14>MUST</bcp14> stop admitting new Frame IDs in that scope rather than evict state needed for duplicate suppression. Exhaustion is counted. Admission checks run before any state is created.</t>

</section>
<section anchor="replay"><name>Replay</name>

<t>Duplicate suppression through active and retired entries stops a captured frame from being delivered twice within the retention window <spanx style="verb">L</spanx>. It is not replay protection. A replayed fragment set whose Frame ID has left the retention window, or that arrives after a receiver restart without a fresh association generation or drain interval, can be accepted and delivered again. Restart-safe suppression is an Open Issue, tied to the Frame ID restart mechanism. Protection against an active replaying attacker requires an authenticated underlay with anti-replay.</t>

</section>
<section anchor="other-considerations"><name>Other Considerations</name>

<t>A receiver never delivers a frame whose completing fragment arrived at or after expiry, so an attacker cannot extend the holding time by sending late fragments. An attacker that can delay or drop fragments can cause frames to be discarded at the deadline; this is loss, not corruption. Mixing fragments of different frames under a forged Frame ID is limited to the scope of one peer association and VNI, and a wrongly assembled frame fails the RCS check except with the probability of a CRC-32C collision, which an attacker can engineer deliberately.</t>

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

<t>This document makes no request of IANA in this version. The UDP destination port of the fragment format is locally configured by the operator on both peers.</t>

<t>The SCHC UDP port of <xref target="I-D.ietf-schc-protocol-numbers"/> is the candidate port for a later version. This historical alternative did not settle its use; the reference is informative and does not assert current allocation status. The following remain Open Issues:</t>

<t><list style="symbols">
  <t>whether this format shares the SCHC UDP port, and how RuleID values are allocated on a shared port;</t>
  <t>the eventual UDP port assignment, if any, and the need for a header version indication; and</t>
  <t>whether any request to a SCHC registry is needed.</t>
</list></t>

</section>
<section anchor="examples-1"><name>Examples</name>

<t>Both examples use the following parameters, produced by the historical reference model.</t>

<t><list style="symbols">
  <t>RuleID 0 (prototype value); VNI 12345 (0x003039); Frame ID 1 (0x0000000000000001); peer vtep-2.</t>
  <t>PMTU 1500 bytes, IPv4, H_IP = 20 bytes (no outer IP options).</t>
  <t>Illustrative Ethernet frame of 1514 bytes, with byte[i] = i mod 256.</t>
  <t>Deadline Δ = 5.0 ms; retirement record lifetime L = 50.0 ms.</t>
</list></t>

<t>The sender produces two fragments. CRC-32C over the 1514-byte frame is 0x487a7b87.</t>

<texttable>
      <ttcol align='left'>Index</ttcol>
      <ttcol align='left'>Count</ttcol>
      <ttcol align='left'>Slice length</ttcol>
      <ttcol align='left'>Outer IP length</ttcol>
      <ttcol align='left'>Header fields (hex)</ttcol>
      <ttcol align='left'>RCS (hex)</ttcol>
      <c>0</c>
      <c>2</c>
      <c>1454</c>
      <c>1496</c>
      <c>RuleID=0x00 VNI=0x003039 FrameID=0x0000000000000001 Index=0x00 Count=0x02</c>
      <c>—</c>
      <c>1</c>
      <c>2</c>
      <c>60</c>
      <c>106</c>
      <c>RuleID=0x00 VNI=0x003039 FrameID=0x0000000000000001 Index=0x01 Count=0x02</c>
      <c>487a7b87</c>
</texttable>

<section anchor="example-a-last-fragment-first-completion"><name>Example A: Last-Fragment-First Completion</name>

<t>The last fragment (index 1, carrying the RCS) arrives before the nonfinal fragment (index 0). The receiver opens the entry on the last fragment's arrival and delivers once the bitmap is complete and the RCS verifies.</t>

<texttable>
      <ttcol align='left'>t</ttcol>
      <ttcol align='left'>Event</ttcol>
      <ttcol align='left'>Header fields (hex)</ttcol>
      <ttcol align='left'>Result</ttcol>
      <ttcol align='left'>Bitmap after datagram</ttcol>
      <c>0.0 ms</c>
      <c>final fragment (index 1) arrives first</c>
      <c>RuleID=0x00 VNI=0x003039 FrameID=0x0000000000000001 Index=0x01 Count=0x02</c>
      <c>PENDING</c>
      <c>01</c>
      <c>1.0 ms</c>
      <c>nonfinal fragment (index 0) arrives second, before expiry at 5.0 ms</c>
      <c>RuleID=0x00 VNI=0x003039 FrameID=0x0000000000000001 Index=0x00 Count=0x02</c>
      <c>DELIVERED</c>
      <c>11</c>
</texttable>

<t>Delivered frame length: 1514 bytes; CRC-32C: 0x487a7b87.
Counters after Example A: completed=1, expired=0, late=0, duplicate=0, integrity_failure=0, malformed=0, peer_admission_failure=0, table_exhaustion=0.</t>

</section>
<section anchor="example-b-deadline-expiry"><name>Example B: Deadline Expiry</name>

<t>Only the last fragment (index 1) arrives. The entry opens with expiry = first_rx + Δ = 0.0 + 5.0 = 5.0 ms. No sweep runs. The missing nonfinal fragment (index 0) then arrives after expiry: the entry is ineligible for completion even though no sweep has retired it yet, so it is retired as expired on this arrival and the arriving fragment is itself counted as late.</t>

<texttable>
      <ttcol align='left'>t</ttcol>
      <ttcol align='left'>Event</ttcol>
      <ttcol align='left'>Header fields (hex)</ttcol>
      <ttcol align='left'>Result</ttcol>
      <ttcol align='left'>Bitmap after datagram</ttcol>
      <c>0.0 ms</c>
      <c>final fragment (index 1) arrives alone; entry opens, expiry = 0.0 + Δ = 5.0 ms</c>
      <c>RuleID=0x00 VNI=0x003039 FrameID=0x0000000000000001 Index=0x01 Count=0x02</c>
      <c>PENDING</c>
      <c>01</c>
      <c>7.0 ms</c>
      <c>missing nonfinal fragment (index 0) arrives after expiry; the entry is retired as expired and the fragment is counted as late</c>
      <c>RuleID=0x00 VNI=0x003039 FrameID=0x0000000000000001 Index=0x00 Count=0x02</c>
      <c>LATE</c>
      <c>01</c>
</texttable>

<t>Counters after Example B: completed=0, expired=1, late=1, duplicate=0, integrity_failure=0, malformed=0, peer_admission_failure=0, table_exhaustion=0.</t>

</section>
</section>
<section anchor="test-and-benchmark-considerations"><name>Test and Benchmark Considerations</name>

<t>An implementation can start with a maximum of two fragments and a two-bit receive mask, and should benchmark the integrity check and the fragmented forwarding path together. Throughput results are pending measurement; this document makes no throughput claim. Acceptance checks include:</t>

<t><list style="symbols">
  <t>Exact-fit and one-byte-over frame sizes for IPv4 and IPv6, including tagged Ethernet, verifying that every emitted IP packet fits the PMTU.</t>
  <t>Both arrival orders, every single-fragment loss, identical and conflicting duplicates, malformed or inconsistent headers, bad RCS, deadline equality, late arrival after retirement, and Frame ID uniqueness across restart.</t>
  <t>Normal VXLAN forwarding, unsupported peers, ingress replication, table exhaustion, and a change of configured PMTU.</t>
  <t>Benchmarks of a normal/fragmented mix, of frames just over the VXLAN threshold, and of the maximum frame size, reporting frame and packet rates, wire bit rate, latency percentiles and drops by cause, and stating whether offered load is ingress frame rate or egress wire capacity.</t>
  <t>Counters for completed frames, expiration, late fragments, duplicates, integrity failure, malformed input, peer admission failure, and table exhaustion.</t>
</list></t>

</section>
</section>


  </back>

<!-- ##markdown-source:
H4sIAAks+moAA819a3YbV5Lmf6wix/5hUU6gSIqSJbJV3RQltXksSyqJtrtP
dx8zASTILAGZqMwEKVS5+swiagGzlllALWJWMvG+cTMTlLvKnmlVWSKBfNxH
3Hh+ETEej0dt0S7z4+Sz92dfnyWvq/Hp2TfJyzq7WuVlm7VFVSbVIvn+X16d
vk7eZttllc2bz0bZdFrnN3oXfxvd9NloXs3KbAVPntfZoh3fLLP59kM2bmbX
s/HNx2VWjhf+hvH+/miWtflVVW+Pk6adj5rNdFU0DXzXbtfwnPMXFy9Hxbo+
Ttp607SH+/tP9g9HWZ1n8F3Z5nWZt6Pbqv5wVVeb9XGCQxs1bVbOf8yWVQlP
2ObNaF0cJ//WVrM0aaq6rfNFAz9tV/jDf4yyTXtd1cejJBnDf0nCEzgt53VR
JN/zDOiLfJUVy+Mko28mMrd/usJPJ7Nq1X3AMv8Il+Z18jZfVjf0TVVfZWXx
R5o7jP/bi+S0hUVpiz9s8ugVeu9kjff+U7Fqx5ldOVnUo7KqV/CYmxzH/e7l
2VcPjh7Lj4+/Ojw6HhXlonPJ4/3HD/XHx0+eyI9HRw/px/Px80mRtwveq3Vd
wXJVy3G5WU3zujkejcfjJJs2bZ3N2tHo4rpoEtjsDW5lAlevqyZvkizxBAUf
L4plnsBAkllW19uivBKyWQtRpUlRzpabOX4Du9DkyTKrr2DN2uushL9yuLK9
Tr69+C5Nqhv4PEtWWZld5fPku+dv6ctJ8qaEj2dVuSiuNjV8s87xwqapZgXT
cg53bhOgvFWewLhxLAVcl9mA32azD3kLj57nSPgZzOCsWq3rvGmSegNTKOYw
z2JR5HVKo9qUM/kensNTus4z3GzYNrriBfyFxMmvnSQXNBd6DQyhwWXblHoY
4CG313mZFHB50TbRxOmJ7sIKH3xbNPDMU1jaTT2eFq1dAOuwwWORNJv1Gmi9
STbrpK2SvLi6Dlc1cC8c8TWuTrZM6nyWF7i6sGOzfA6LSHtW51UNU8K9wd3O
m1ldTGEETb7Oaji1y20yzWfZBnYNRjCDHbvKeexAVwmSoVKCvWCaX2c3RVXz
euRZvYQlBRqY5x/zMEveNaYqGB68vM7brCjhkgL2Gv6/XuflvPjIpAU7kdVF
U5X81BV8i2PGdavWeZ3JLHHQqxzWBh/3h00Bs0TGgZcS84BPb4r8djIiWl8V
8/kyH40+RzZTV/PNDB8zGvFm/+lPcub+/Gchp6az4w3TK1CpEGiPKh3F4jRa
PFJyZNJdJFuUfB2f7QT5dJn7J+GpmMJ6wqyIPugBt3SyPKUblW2QyyyzbXL+
NlDcvbfw994gnZ7ATOSI4pv1EjhKRls4SCURGs88a7MrGEjD+2PEMLvOZx9w
M2BV8tUUyKmAV1zVRYuEBVMkMrzNamIPGd5YlcCBYCuYWFZ0BnoLW1btXYub
bJBVVfjUDNaYNxQONNHvfAI0m8AildXtMp/LjOgwAOsrGxFOwDlgdIVQBt71
XVnMsqbl0ayzoqZ1COxqkU3rYka34boXZdEWQJTNDEj0JJnWwA3x/hRGgu8u
4V9+IJLxarNs+TcYxGIBz5nBKZjmCYwZqHSeTHHtrphf5eslXEsrAQffHVa3
Jhs32maC/BwYTl2scEGiZcKxyiGOTycOy+2ccY4GGSgdD2QAf/4z7XmT+wvg
pg2SdTkm/gKcZYn0sEXaIhrkZ3ueBItOEiJDYQOPq2/yhG+WBa2ZXuRg66bL
RXl4HJMg0CzeKzvadohX2DTditd7UZctm8pYYYO8yHFRZZfjtloC34HLbRb5
xzYvG9oTnIRnlqCPZC09HFbudLkcH9ACwFuRkPmQrqo5Sp95j6Hask5AzcAz
JXvMmzRHdrcCxtkADyhm18Z/8enZDega2XSZE8nj0avHzC90Q2SJ4dqrTYbz
yYHSRyPk7sj7kvc5McXkaPIAlDcgsoZn9/3Fi7dN8u137y+S128ugmxS2Y/L
C8zg69wOw3rTIrESi8KhyaUs40lVoDXJM5iDPS7mi9kw00EemSXzomlB04j4
grDJE2R9i67uixsbc4ggvHFb4HDAof/hOkfaY/ai78AnCB3CAIFZws7N7MG2
eIVQD4h90leBzQH1wdEA7o9vyPDeYsUriqsEml9DTyF52FTLG9qNz5OzqrxB
9YTYEqzSBex5w2f6Q75FIQdP/gy347OU/8VtwZ/fvfjdd+fvXjzHn99/ffrq
lf0wkivef/3mu1fPw0/hzrM333774vVzvhm3Ofpo9Nm3p/8K3+B4Pnvz9uL8
zevTV5+Z/ArnCUmgQlZGBAiHuyXNbBTUDbjn2dnb//2/Do6Ar/wPWL/Dg4Mn
IHf5l8cHXwGXIfWJ31aVwI74V1i17Qh1hawmClkugWDWRQuHOEWR1Vwjo0Xm
Aet4/99wZf7jOPmH6Wx9cPRb+QAnHH2oaxZ9SGvW/6R3My/iwEcDr7HVjD7v
rHQ83tN/jX7XdXcf/sM/LoEdJOODx//429FoNCA9TdVt/GFZVjNgccyYVxWc
sXZTlvkyAUa6rmDrYEHnQPBE/akerTR5B8rz+fM0uS3m7TVc0xYr1L/4OQ0o
rzPQ+AtkwcC/UPUodqslJOvtEOJVTisGgdY6FXUKZtMt8/oFiGKwnoBP3MAM
5qCl0woUMfMO/NnUxMA0FnW1ivVaYAww1RvUVGhKE2TcrL6IDUBKeZEv56wq
qKjBsa4qkLxNcVUSY4BDwNfCMOk4P+PFo6e8ZVnMh1mkFup+XcsFFSMa7ZUw
L9L3yTJwpszZb57bjuB05KItbKe3YVIzYlC1XsJadHRbZ7QpA/4ebweOy3ub
f9TvX569FxGaf0S9pGhRzVMSm8eGlOzuolrC7qkVJJYZ6/QwORE6TXKUJg8n
LCu/mhwOqR1uwiQsAjkDS52CIYXkizZoIPkdxp0IoVQls5EGsJXFRpi+kUm1
QfKJZQoPY5KctwlzJFCUSqD+NamLOElm+/ah3g6ktcDHOWULB/Hu7H0CMtpk
C+9oV7fWA3sjU3MLIhq2zM+ULNRkWQHFa9H4FUk+xaf/Pkfde+KJSgxNXJUV
irG2qre6TPjKeb7IQH09SXRRST7Sc/FgwFo1sP4sFmDk+DWedE/dJALNZJlu
5lc5KUv423s+FG/NcnUmCVooXoW4LdpreB8/O9qeExYbZtv4txeNYzRwQr/z
Zru7sIks9QZVBBphgyeG+Gesg5OWgiK9FHsXVjHtMJ1YB5kkz5BoSWnnTcGd
4kVxTEMVeNlhNRlkYehk8DqVqPaNp3hPmV9VrUgAUA9lI5iDdcy2Jl8CFeCB
Bh4IU+pYoF6WbERtl/kjN8/mcySCVD4ZXgSRMeFympcXMDw14NX2Bj1gF0gs
fhCL4qO6JZjySRjRE2/RCXADGhpw4ZNE5BFRjFA0nkh4iVAbfLCsqg+bNRDo
agrzrTZNrHEPnRU+vvj+SMw2spA5cpWgrrKtTtJAnDZTJHzQJ2G1mCfbUg+y
dpFsmx1UCkZWuWUnUngpGsewlOoTMw077J8b+hfNIGvjZRVHF5hjxUewJnK6
E0QdK+zs0lOfcfKSvRiNmBGr7ANtVEFqM9xmevOmzHS9J8m3aAyDWNKNa8zY
o5PGp0M9PHacRIFhciL7v0d34p+gpzALF4ogaqDDDQdg3G7w5aK2TclOZnsT
9ctw/MmPKOIL7XBhkwsQbQkeSFBYwOKNmHZHDpFqhr4xdHbBN3jWFl0qRV4p
igGR3lVe5mQEZXQJy4HNigYYm08q5O31dD/TLdz9x7yucJVg9aoaD549yztt
ycl1/vbmaJK8ie0lb2qad4WssUBKzad8NXAoN7Nrcvm5s2OWJXmVmWBXOYsJ
UD3ASm3U+I8tOBYDLECAk79R7W+xaVF0RBJKLbh4A5p1PmPNBSh3do1LILKM
1B5WcXBGLWiUOIubAh9HrFl0Dva5oCIAyh/On4yfRV7TArAOEVZgQscrWRUN
vZAcP/BLjQQaWPsi+f71Oa40WO5z9tLJnMh9DYbOZjkPrhNcHLxhUy6ReeBU
QTlmm7paGoNCR00tRmbn0LJGKt6IH1hO0C1TljEvkNS87FUvaWYa6POLDCwE
82C/PHsdCVC9k88I+0XE7UlOGH0gfvvgkB6BOlGxWuXzgh1emXFeeLgJDWSn
8mwZp3Oel+hnZs2hhL9Wa9LwcRte0hTZkDENP/ig0APKeuvxaPRT8j3zpuQn
5Y4/0XzhH5wnfJpfbUDX0KjBTzJB/RWegE7oT/wNV6EAADEMnxyxoPgJFkN/
so8eJqjk409P9Ce49wXaPEAt8PFjvfLRfu9muyU5eGB3/+k4+bzNpmPjwRRR
fPrZWTjLXrg2n/15NKIFaIo/5l4ZRwdUYE7+lJOWS4t3gny7kLOKDwj8ndg+
sDf0rDi6optxpWW/2MWQsSMV2TdcH6Sr6FVoDDBvAakIkqtilwG/kNyweYYn
uemoHxRMyT+K/SX7bRZLbF3LegQWBsNS3rgB5r9UZp7NxdWcXKOnoq3AaJgb
z/4D++PQkCVTly7Kl9m6QXXCxdSEQSCb2aLSPCUGQA5jz/snvGqsGTnVRK/L
lmB+zLeqJQybNi+VeZv533cZOz0lKAZBa/KKA2rrojE4CSGs9Tg2ct1jjale
wc34DJEe8C4SMJ2AmZ+CmHf8zlxPh25Zx36iIc+LxYJsNeDaHLKxN4XB7V4t
UKHRwE45hjUbvjRhG3dY2dsn5kO3twX5ci+CzaWB2TAHOnj0Kr5QVcZY8fAC
ORoQCpOT/v4lpBijfgXnrKfolh3bzpsfKjkqNILnRLKizIESjLxmnC15OVcw
8ewqx2DF55/T0f4+W25y8XPi7xQW29R0otPktkZnS5lcvpzNZpcSz2Se66Kg
L7tTZ8U72N748PYayJF2cqZGLYfFkYv0HorGC8gQkvgifwoSKKlzixC3ZxoI
gRUY9WHyD0/hE/jrcerGI9O7PLgUIcMn85vxISpIcKb/sMkp2sBjgcvZuL7c
j2/gzQU+M0cDn6j2m/ED3DXU9tRfhlzW3gh/Liey1vC8gwN4JJIj/gjD4TAY
KA/F3LnbbCQoOoNU7ZwgfIx5mLwDaoIS9BuWlRJOJJ7I0rYjHOG3Q5RN+/v7
aYLDpY8e8EcHabIff3FEXxzs0xf9rx/j1wf09QF9fbBPlx7QpTtuU2G4mJUq
B1/wyaZ15O2Z5SQEzYWowZPHk6PJAXp8KBCVmfVOsbs2CDE2gYE9smoyZoXh
hjZGXWygqhN5zaucVWuMC7bAzBciZMyLqYz/iybE5OlkvQtupjPU92GcPHo+
aKRiAQd6dzZ+cHjG6j9xSzhEdUA4lCz9acO8PMIpdigg2nj22mUN2KVltSzA
wlluy2pVMApg/+NBPp89WhwdJPdAUIiI2v/4+HDx6MH0q8d7JxJKojjApqUf
KSq4UEvbx16BSEFmi7+Wyf5f3ryjO/Y/LuSPc4bSctCCEzs5fX92fg4n5PDB
0cNHXz1+cslDzB/sP3py+PjBBFYOmO4S9R0WtQ2y5L7zF92v7P0V25n3f3Zd
EaZGlxoOUAuLpH4v88jC9xQZB72XxBWsfSCtw8mDnmP0dWW8lsyMnNxlakNH
TFe9SsGxTsESGmdkXapHEgOOIMbAlqnACJ/C+s8rjmZt4OElBrHJNOUDTYZF
14E3Gr2CWb1FbaAji87fcowAX/a1c7TC56I3s3IZjNN1CIoFrwcQM+hJm6Wh
MGAC6uYg259eIkYiYTfKn4/bIJekB1qg/ld2/eewJS9ElUbF7cWXomODVbig
30AAvB1/PRYh4O17/Ln3lsjZ03d8Ds3iE4Z39OIhwESBA31sA+Ujp9CkZA6K
RyMMflO2Fq5ZYaTtjV0GnD851Z2OLCDcyRRMDxiWWh18EpEnnj2ld45Po2i+
uC/YLjj77dMnJmDQVP7mKTC85b17sLp7vznbm4B8YVleomG+zBENcUhWuXeD
KJRHnNRuwYjUOHSVkBTXaw4nk8f0nKYEMruukOPZ6VJP/7y4gWujEEdRAsf/
hoSleBYjAxRVGlRmWcuM5OuZkJIyqiUBRfCbTPjNmV/BgHqAi1fILwzpgLEP
cWehmoycCU91hhpEhoGJohxQeD7k+ZqnAouCJ2kDzA0sdX4iOoeS5y/JXFY1
HzcRhwLfPVKHVqxpevuIY+10KudFM6toBcQ5a/6YE2Fyj59gbNghNECGgKKK
VuYqb68rhOrAyfDAMAqezXP14GbsNpxtKP4DM+YH7z9+CNwzisThuswI9oAH
jiwo3WjTa2R3cbYGqCEu40Qg3elxiqJ8vhZExOnZNyn+lbx78bs+Fsk79h3K
yXQA4hjMZcenU3IZvuja2qtN07L9JQ4rpPCKxDXwxmIFLF4cmPCFMeFV9pG+
Yqa2zMsrINAF7LOYbl3QIbL7NwLIeScKyGj0cgdUJ+2oSLEcS66QDmC7AtjU
IlhRuELUGfIZxJRrKFQm61m+lvCH4jhRNCIkiGBBccCXtgtXsftQ4rXMyopW
gIp6zgOQRcJzLWtUJ8hNg4qxyIolvlW4qOcbHdQVUC7KOhQcb8r+GPOP6wKP
in9SUXZIU2wcuKESzQmPvANLsoHp0LU12YHk9RC4EgbX8eAjoNOO5jUadnge
iE7RsjOOQaYIwVjE/cDHKvZEk1GB6kIXopBGukfKLk4cONugBiyYguiZNxpy
XaqJxwjCTQ2Xyitw18mNkorKIidHEF0RtyVuj2eBLHF4XlEn8w1D7hBmFZwW
qGYbXKsPlJsgbkcsN/jcnjHAYNHnyzjbrHQYSaQTetAFgbxQRzaYMm8b2IYk
xsQsB74BspGd/+ZeAhW7mG0VMfGMPVuGAAPa0X1o1GPkQJg96DOD6cljpk5m
k305CplzErZ4cL89PfPxmNIcts1mhkd5sVl2g976dNqyCam+cpLE65OD5TBd
Fs21smhekXZLHoY6v+EwVMtwKeL9yyUxvIbhJcDAKIwgW98M7sKyQqf5DQK2
F52oDx2FnBXbQGffBzrDabxHrFxyqlswGpH7Uam/6ZB/O6Rse+Yt3shspjhJ
t2oEy6OjuisgmHo4BtuLEVBEZXbQktQLvKzgXff8tX1ycKovf7yHsQlQi+o2
QIhX2RL1BZTyGBVBPCSdwN5EUpah8I05eekqI2ukztrBNJiMUSm2UEA0RvRL
yToH5yoSrdHxPGXXfk0AZBUmc2Oep3zmO+px6nkCI3Ki9VetoM5ZRAs/wRVA
6+dadeI6DhOwiJ0kzxVRbStJ+RLX9EC3mqdy45hOFzPrexq3v+ZtJJy3Vw8Y
fOWE74PJUUf4npCClNVzEUhk+6OFZUExkkTkFoAlUdwFQpO3JKHPYw94jP2j
uPREhos/h2CcEeH1lxrTuNfRVQkCGKQtfgE0xysH5taXB+jPqzZX1/DzUXfB
NCyz860HaqiRa+oRo49iL9ipQM5WWf2B1JmO1kG6lvjEwqPLojPooM9/KuIf
IDsUigQhBo+QCac6LnEKkn+bP1B+EjRe2NA8oGQIc7zVGAaruvib0C5zltGI
vURMA/NIAilfUj6neudccHBMHBKTRP4KTya5hkFjDOtLBLN7vOE5mNw0y00B
tfQQGZtQhn7dsb5FUV0v0caC2/ZSexBZTWIr8fDExCNcDZwQFGK/uVpWU+Dq
Vb3GU8eegjDdsFKUnLJmin/OfpDZNQKMZJlQW3F8or0t2MTCTe9ByCciNhg/
bpFjW01kdzVFiU7CUvpDhovHzBC4fH5TzFpOq2hg0kvK+GJ/2sB6g3LZqo4h
6iPpYRnxC5TvrD4icgfJGUFaGBhRABqROmmfRh60y+8IvWByEpgSk6YPyC6W
MlKO5eh0bX0aXhUenh4bnoPA0emKE8rFkIOOQX20wBFTYyAYVfvYTFFowLuA
6r/QVwbbhSwuxa9EaQGge8NdZNC6BCuDmTLYzwH7OylTwCIJigpEgtwjRUVs
lQHTrpYkVVnTZhYJhuu1igAf/oYB4HTVtxUURzYz2DtizrIga5E9Nw6UfpNf
FzN0CQXP2q0A3+GNOPDNmjQVEpIu4cSBJao5Q27XGJKqC5LlHChpCAPvYCyx
maxWoTrRedhM/pJIkjlsmma9tQw5VVCv8rQIrNW1Oj7k20bIabodsDoc/qxj
vMPZDJq2sgn6VlgF8xJCDaCgYqaSksjsUDxuMiUF4CbjXRxdpvvxcwI3M66v
F65SUDPzJeL1sBSCDNEQMEkKk1LhXlSOs2UvSNMPHw0EbJRpOfFk2RVDsFTi
ol7NCrqxWWp5iUcNlFp0IEZKg/jmNmVQ0nCSfPKN45GV0TEyprF10yWApq2Q
aQza9Tj/EDpT0cxRA7sm0D6Ntrgq6YGD3J4mOyViFaeyMrpwETxF7RfOcrQA
rWyCgmYifDIFJ9gwR6CMOBn4hMF75rLzpJ/UwlYlkm0ZpDRLysTRkRGmyN9I
ptM8cObSUAK0jnOKUvEd66opDFSEYwqPdW4EekyAigW4FiXDyKcSgPIP+AGd
uOE0yPDYEiM/CnIFIqryKYVMOby/VnHHG61jZHUIuDmugERGxffaewcbraC8
oXCufLy8ccBmSn+zp1ey5OyI4ai9PK8R+1ICanDiGbdiullQUNkVcZ2hjk3Q
UFZqUkeVpMtwmB0tNcX1o73KnhH27OCJDEyF5TYdtzMT9EET7vOclB5412rC
OyXcvcMvV5SO5iRkyND23FxkhItPO74ITd0sWgmOLtl+xmstLTz2wyqpBlQj
EVSra9x4CTrBBBmED6O60XayR1YgLzcOsqcLYxqKcQU5YasKWHBVFjNdA9Ka
QN6s1pKqK7hM9aZlpFoFy9W/fUlm/fPATiTOxqgVmBA+0hkOPd8gyhnyD4Kc
rcBgqk9s7yRXpmH/J+tQkuUS7WBYsuBTZPEpGWua381+yAnH+NhFAcJ8I0xw
ijYjLjGNq7mlaAKx8QivOAddgmT5NGsYSNpbxqicgAdk0HWR4LS1RO4ivmNM
c4LR14qh0Sv4sDgH8SJZF/Bbw0ocrPe4rca47Hh7OduSBkkeinc5e+3Q3w1D
rFtFwWHar4JJfFQpFxj/IA4OztqsRt+TiPVGImKkNmEuOwFLnyvkGbX9pcDQ
JOmS1xXHZMBoHA9CPUPuLEi6TiYNhxU4G5/4dzCNYZ3Wy2qLKz0WfW/m4Wmo
EInfDVfHS0A6ONPcz1fMT3hsmd+aj+U9rhzvKdzBwGTcflpRCn9ki9x7EIlk
3SAqJ+YIpbcpmmtCHuJr/GILfJq1w+eMtqCzTWoQjQHhA7mbtnFT1qd5Kzm2
5tKMOEvueDS6n7w/NnuTHB83pELAzJiBwIpRBC9XDy35j7beKFpvPby8HwVF
uCDe37aq/Cv7Q1H5njNIMzx1J3wS50Q+qlcjVEHx1HIjHwwY/LNdg4+Gy2Ns
OYIUWL45ne3I+hMLFjqNQkkkpJnzOWeegYyNRmM5NbkwXHqnahjO9f2enWo/
PH3/5bNUEqHRiY2DRy8V1rHgLSTsmmQKNmtUZnDK58f+iIpBMg6o/Zi1gtxn
YBcr9oLATDmWJiunroVFjnfgmJ//KM99+sOX8L4gxTtMOalms01tcYYfcLVF
7sgFYh/Z8TjHKTzPl2123HcqdOQaW353jVKf8JSeCLMCIYrHnrx9MBa3GBw9
o7fzhEi1n9Gxs+ni0QxPPWEC9akDSI8kglNNqCpqHSE++91x7LAQ134aPGs/
RIDYguxh0LeuCjEAG2PxOECiWsoUroDJRxIF9ItsS0MurnBvGuE2Zo7b9r8j
jwfnY3V9Hs8SKkyEcwPjd4PEUcAFxx5wgcKZ3DKo/dk5dlEG0wlsI6+Jg4sT
jofAK0Ev/SEh30+jwQ1FKNqhbdZiMVJkmTJVaLr4oAXsJGc6hIWGW4id8ypx
jkeJMrFBHzh7kDnYRkxdQnFR9NwstZqFJEtMBkH/Lvlt8uzL51++S+7t2Ls9
WQRC82PlFkRMRHxzgk/Qrb2ubnnA6D9hJQUX2dxGJ8k7AYNw7inzrY4jjArp
kM5EQB1aS3zlOPd8jReDHbKZpG7SUQTek4Gm+Tvml/QRppJxGGbMSTulpBio
31H1IBKgt3W2ViXmdycObkP83vlZMRk5VgsYaocqg5jqXuiBLHSOS3zAWwTr
Nq0vKMS6WGZGTPC6jBEygKc6CE9a3OymKubGh3DuuH3TTYh7EGCxV9YG1e6y
BwcgCgdbZlgfL82BduKYCxmKRAEJ+vBuVFsndZUA0SLNbQOdHbHVOgyoI7By
GtXuKNrGKAmDHpiqk69zovfrqiHzy+VeBnswE8/V2kk4Uacsdo3xgbpaNhb2
FPCcZMf2GTl5zchTPWvRHuRlCozdEjOSc3ZbIf9Osiv0wAGPNI/GPG+Ih2iA
h73bJ7jyJSgFWMNG0OVSAwdXknKENE1ZBmRET8TZy2qgha7RL8z8SfYFBkkO
WuIkqm0HXZBPjTly6hxdYhF4L/LYZaq0Bc9EVof4m8bvAz9EL8kSq8qJYpDK
Cd4xMDJ9tSRQ6ubzDDcJh+2OhLDe31PyLLIhRxxZydhERiwC54JNm2MdCzk0
z3h9Qh2tqkJljjBeuraEHCvRqsKHkybVkTFai8csGsbKzSoOXrIO5RykJ5LO
hTuOjlQ848KXaL0lakl6sxaIwXdOc2TDiwWnJzrkJ7qu22KMccCMoBCtuM4L
Z34oTfowPd9BdpUgq5vR6AdU6Qlepu5dAXymydunBw/39xkp+vRwPx3GYHJp
tIOjRxrRHqp4lVI4kd22DPno14aRXLRJQkPSZA72jcJozp7iOyQK32ZX6Mc6
eHhwxFHLzri2UjQCrjh8wFd4qOc9HI1P48cLKJRFdxz6cg7iQduDMwiHVCCG
NF1cGEz1crFMyhdAFL3g+wn5nyqUmmG2GkXFaw+OnnD488lX9hwSC0/2dWY0
IXg5QSWC9sIEmctqEQaQal08PTh8DFv19dOjfVqzw8MHxpbobHeeHNhmr7qd
kUYqj/Wk0COAw6O7CIBZsNswvn2KmOt890a5Je9m9xAkgN6Kj8bRyQLy8WQ+
3Ui6SO6T32LsshMdCbmzQHFj/0GcwbOyIivk0MJ4ucPA0WhRuBIZXGJyBOz7
JeY5yL/0u2SCDMkeFPZqpCndhPv8847R1YYxrMaZOMGVKMigyD8bPInEAvV5
OPeek5CZNb9KHcBc6lBRhxplc9Ybw+oNSicapXmq1NG0tpITLvZGHOkc+VGc
5va9q8xBcduNJCphPAOIoaS4+iU5X3+8gYlWdTNZby8lgpN/zGebliylW97c
eT6L8mXG6JnzSEBy49YBx40qMSuD5228UJ3cegJyCsZTIuN4MnYVuWAPM0kQ
5H9TsNnzvOwfGPerOLXYU6xmKia8bFpRJ3HU3zxF5HRqaEHbd4elkSWo6w3r
TlT+jh4dQrsGfCDPiwJnsi3qXxwhuvhOE++AOC5xgce6Bb9vqvIyJCyZW9OO
i0PV87DpLZrlylGfRvRG1Bmd/krMcW2lJElzCmRzLCpmnZFjMShKGitUPdqk
tW6eGegi1tlwVL4QvwUMHs5SZSCIZbYnUvuSPElwPDEhYwsyFWmfwkIItgAi
XFp8jrxtgisEeoPVowCXVuaU1I7ZhgLOZxHCejR6U8alULhmg2SpO1ADJuai
8i4RTcGAse7fA7LCGkWhV/xFoogO/d4z6sihJDHSTWlF8cQQHQp4kP+T9fSG
qz8goEJ83eY8DxANxnyQ9ZhZXLON7DXT4ejwX2cbyqHTd1R0rq9y1ShOPHYH
k2rfnan/X01FjjplbQtLAzP8Dn+JFLFg5zNOL6hlt9dalw8THymFADfex4BW
OOTA/nG0uUByBqK6Yqd77k5XlaLrdcOyVIQkAAWC7SLVfCm5KLWSCHjGNgLM
ZVcC+qEcDqkD3ERUDnrRx1pbqviI8S7i5KevT3vEeuGyV2kV4AiRJUpXZzPW
2K1qTEiLTdmwFv4pPhXNQP/o6qM50zu1ZCXOTkMI7srcoZpcypAJxqkA8z3H
qoENupbf0TFmj6/m/rqgvFTmiGoFhYRrwlFHJSss6hkVymWHolSWVC9PjBUJ
9TcVR9PXGhSfUOeszjTXBaljJqMp8CHlEvGd7ym8sCV007RYImPxo02lmJBf
YVtN2ivdPHoYp9zkNWWC4IEn/puaw1u4KtBZvtKSVqRLjSn1JwDkTwJU1yXR
qxUj5rh5d5SNy3GSxAhcUIo1mFqz5Yw1Xb5+8SyHNUBCOLWStfzM0Z+OOUk5
nz/9bAEMKcfs0wtgox+oHMKrbEPR/guQi2q14obBMUHgtSTAWASXAUTrDe3X
lZTkfV3BW6Ve8hSWjcwz4YPnUtP5zaYdV4sxpX1gAJCCSHKorIwz2alWr1wJ
U3CBPpJIZeW/QHTI7LokgdNoObhuKehzgmxTtUdCiPgFN6iWiLGODAsegNTy
5HBwKAWjxxi0vQZpVKxRrdGqLQTW46vY41OiGYVLoTkF5iexUBoLNnK4oUcr
TgcSQD9QKxzqgMdxWNP6NyGMbiB9S8FHNxX+kH8Eo/zrMFvkS2OXy09VRxsp
K6GOOpDjRC2BUYHFDzRPgXZcaVJTtTwLbV8o90vY4P6qhrpaMjTNXMqm1Q1W
/gkraFkVnmhsD7nuj1CIximlwrhW5eipMYjNklJJc1MHQwQgfhVSiehG4vsX
lkeefHHZKZwtqBDREcXk6r+1lDjMvVNI2zAvwSI0W8+XQLqjvndqbNu8GKSx
cFGlQrKNflYt3+SeLwWsWHGe1F63hLKiAsXSieoieycBQoWt3iRlw8N50JJx
BoBXAySjotvUtgJHnDqwPmGABJIQkssixAiW8vlEAsok+Weil6VRPpqGOJgN
FqYQ4HnCRUxRHov0pDqpDbM4n0pIN9Dv2IJBUgudplFIJTaKeShVp5qvzepk
k+cfOkXsF7D1yItZ8s3Vodg9oxzRZ9kpQUNd307q1zJfcDFF1DR4Zoabc6wQ
LqXg9luP2YAVXEpKfsfLlTXxTEjdpKXyETcUgVRUVMuMCtPTK3HYoahG69Pi
sfAoDOebPF936Ry5thwsrSwpMVLWS7ztKq6iT9CG4MPIAMNYunhtySojiIt8
4ZCGBJ6/nzCmmLK+rNkChnRDzuR9Ut7LflH6kP0SFaYXZk8ZDNQfgzcrABiY
p5fjqwq0Atqz0+jJaeeRZLha9jyp0AIl37oWA4Jx6qT6Sa1UySxAuiPhK0EJ
jK27suO6ABMsNrYSyeFSeIijbc0oD5UZMGZxBRKJ8H5lZQ9yXmllE5rQXWrK
Kbtxrex8/H2UsYNLeT/5mh0KTh9TSEEU48kF4qN1I5X7wW68Qj2P9pyOuKC0
iaG0aCgK4optcxuKBgvAWmEXDKzgh6BWOoxH/nGdlVpqxzNerq9YVpoAg8eS
pD3XhCSOKzEiZA8CRRKcmwz+wuxh5VM8Zg6FFQzI8FnE2mkAufLuvggsXKVi
GJWaGawU7lkWtajBJkFYKaOYaWUgzoWsltXVtlsCvadBEHyS1A8t7MX1VeZ9
jal7iND6YQLdNC6A6bYZJ3w8Ohaec8Hlsl+gnxuRQJRVpgKBBSXcg3IZ77nY
Ibl9CSF2yhu/w/OI7gF1QWlYaBwVLtAiZFjDhCoPq7PEsO0wivdgbuY4jNNQ
gsCVJfB6m6lDHfbu6vKjhmTJ0aMRHe3k/Dk9v0wes+Pc99cBigEzTaFukkim
OCDKlVWcgxzW4UJhvcLmEgHHBgZn7/H1O0vdYIygV+HGpiruf3YpWS8hQTyW
VqAl9m3DW//6F91aja2G6Oyp9+Uy7oaBBo0+OQb5kGShqM9f/4IshXfLN/hY
rylMuGGtpA9s0vClADi8zMFfZNdWUdaHB6a/6/nR6DR8yNdc9OSVYR/0OqTv
zp7ogriBR96AoNxJebG46LxEZqRaMB44EcQoZRQy+ZbODdcVZmyUeA8KZRlv
l9kst5Ko58EpQD4GOPlSMAMWXC8sFIMDzAss7qhPTRmApjpcF7SZaPbQ0NPk
hgEPvcKz+XXS60XrQWcYk0PFL4TKgNARlCrXSzFC8nQiHxZPnBguA4nYASWR
a8CLg0fipySEFrVycVUv7zMoRgNkC3JbFwTIwf3Qxhdcyrp7tTdahsq1ih5l
5a87VQnUEncJVkXrjSNJ62iWkmO3q10Ihf/IU6sI2dS/p1sz2M0jmDIdT7KV
BAndFDiIHhlcthRpXLCBcFvkwRDNmTz3M9O75WgoTOce3jmGi8b0yR7ycwUb
qyzWY0WWEhDRd996LALWW2PdhX0jnCy7o71QSKTbIfel2i1lfhJAU9K7Mv7q
iyY6kBwIxmYPLHDDmvpyr8An0WE9a3rFsBjyvCX/MgKNDBWDPhFfjlaQRigs
rdyDq4xsgJHIvI4awcAEzt9OuuxrqJ65VUz3GCeP2Y0z3rplyEME3pWfpoqp
sX+IcLcacq94iU3BxbLT4+usubba0xrJUUuYs2VoFK7qtSU3FMCZ6mC8FbJu
OI4OGMJ8AQ+HPAHD5a77/ft6da/dyELt6wt2dFOvQnExtwSjMhOAsAeEKmUd
X2dPRVaAyl6fXnQ1d9HCA8Kb3C1Yzo5hm2K4HpPo0TqTftGMomCjW8ys8BdG
lcW1vL3W3yE5LZ8NcLeuTnMisiGkDbW3VdDlLCsEaY5G32xXYNojiGtB5U7E
eorJtSRGnIlGb8KDT2TX0Yc6xN+ssvMT4kIlDK8LNea0FP9AB4VuaVGs6K3h
kOOBaECq4WC5gYPSnehAMCtxHWjpadl3RB1UMnfYtNRf0VXgOkxtuxwcNZVd
jIMg1Md0dGcBJLZV7mjRhp5Orn5DebJNv+NarPa5hOA8astXlT6DS7s1OghF
Z98x4IbVSNaqukZJkqLJluwniSoEoTSh8DfwL5lS4M4FAUO1JQ69hNOTpMom
RmXIdcyALUsKo7gKXiFkyn4MgnFJRYy7lnmPBpPpcPTtpGaqx8x1j2us3BjX
gKNY/BKDsMCE7goD0KHjBXaVPbvlaYEhco0ixAvyikWOikb7sCHeeeWzRlwJ
PgT7RAFcEhUBlSO11n2fAJ0prZ0pLm0Ok9NUcAP2IEdgfr1KtcI8PlaXLvTj
cBktGwT/W+CZQyCIqjA3qg1ea6CcaUfZcEMvZpK6AtAz8WcQ+SLUiCjeX+tb
0SrVUt3eKB9bXV1AYMAZVTLVhEBDGpx0u+PqOWUgcb/3DJ3TlLoGd8JlTHM6
CWRovzFNx5p8qrmPD6c0e/VhSC0fTeydacaVPpVAKt4DD1PR4gOej15LixnO
4aciAlbqir7QKa1yBZ2q70hc02N2TVNVdedH4tEWXCjCDY2JmkqAZ1s2LO7f
p3iisCjeayuHCmd7ch9diTY15Qn+JJE2i35CTXIPZRLv+YKp3Vo3e9ZZyUqs
Grvhws5ICkFqiC+JjGg6GCodG3ali7NbT8PdzEfa2QhistFyosbIQ3GQ7nGm
FJI8382ASzO3LDsbi+J3Yo4yKY5MhqrXgavQvpEDFG/tZLHiiLmybdxnobWG
ndYWondE7d203070oOG8lWJk1TLXEwibcuJ4gWQLGJhA7CN0Xk2IoF5GAHlP
T+chh+mC0l6BuC6CkPUId8GQ926x8oDvumUE4v3u9S3bc20xfb4vw/kHfUEU
B8itugimifMExdM2DHvSSdlV/VXlBh2s1KhBkcXONxQ3W44HXGFjc0IsEiyd
km3i4mksDK1CGrGA0NeNJ0bY567T3FqDste18H4HqhXOvTl+Chfhz4S6HG6l
MXJtOewHz/N0XPrirJ5dFwhWR+c49oeTdADMMmdfYBpbMPVA/RDmQ/sqs00b
ntCAbCOkU8g93Ia9HeNyQzgRwAks2uOAYs56yra9RQIzdJS4HcnPfVXnEXzQ
fiInMfzzesdp4+U+e5/o3598i/leywH2hXI6oWNhAqhb2cZ3CeQa2HgEhhjs
RKq3U9N723Qu4f5toE2hy4gMqZi7tJwgIDifStlc66RIZhELArpX+xgEG52m
yAYVnhLObZWULL7HzCCuNBceho4DZP2YEs0dcKwFmDapTc08tM1Z5pma+nI9
CbOOYGLf6u11JRWxHCKHyoM7QR5IzVuHwoEFwMylLth+omnocHD8LpladJ2r
vNwwWxZJF0J5M0KJKr9uBBTm/Hnd7vOGyenH7n520O7zwQ5IUfGnYI15RxPK
VC/7+pGuTwe2uLHCz1pVT9tgLQG/JQOYgyzcnpQ7E2qyNX3jCkAPN+TrdoLF
kPdOr1b/VPy/OAfiCola10h9PNy+z2X3R6MXsYojGWVCd5rjoefXlz/KQjiM
3cjdIBgXOHddNOwlFMmVVxxZsUIY2H/CnxHIhP6fg4HPDgc+e4C3H8BXD5Kj
5GHyKPkK5MCT/8pnoy/Hf+f/gMHDH9l3/PPTwEDhD7plB//89EuN4e/4A2O4
41sTz3f8+UXG8AutA9tL9Ez6+4yEtf5OId7kHuUtTFH2TyaTT7/6k4P/+6f/
n3dfAMO8+4L//G+0BfQHVZ57HW6ApmiKDda4/uqvMwbiLKjbAOMeC18VzcYk
GX+MmsxPyTMSBIsF+tRAe0aNwBTrHTr0PjbLMRX6kxrwyU4NmJ6GT8K2PcAk
XL0tComoTZ310tctKuNUCG3zg7189Nj+6rACnsKhrEisZqeioFHhIrruQfc6
Upix/5PG2zqv1ZocdDdOTo8uKd6flkrc8I/RCR1q5MUCOjVwIftKioUYCVRg
rBF1f1WUG/Z6uL5Hoh53qYs+Zth5aPml4xpbv4B+i+E6lxyjATehtC7HMekj
SlwnAuUu2X28Y/Gi8q/qXmA57PQWdeqQUeeVE21NQiav75NzIu1Sd6jgE6ul
/Kjrw/9Zqnjcqq351DHjCHEzZGiyIvQt+t1eSpoxXKsN5/kjXosBPyT769aE
jUik4bxFYH1b+XDmot2To7BrR5l43a5gotcV+5aNGxiFGL48gAB7oBpRZ3s+
U/KiCeS5Mw3iParC9wJj+Kq49QBeKhlH/QxzzUp/iZmpscebA+TOa4gx77HW
qOCliPucS6jYtQ/A6emMioaRN9aB1tMt7VtQqacBmC7lMIq2EzpTn77drcPU
90kaksC7zE+jTVk40iXk9omOYl3rnnHUS81uiL8MXWSPXMlvKwRDC6cucbzf
PAmDPFG8JXGzska7dmH7qyss61ZkpRxBeBnaoXhuJL2nofWGFWHWgy8KlTRZ
kKQcrJeGcFIySPOAuOK91ubJo4Ex6ri0biEuImcejxOLxHP2H1VUcNwKC3Rr
A7EAb+zAdt5alzWuQjTYgC2N2q+FpmvcPEWbsaFGscfA3rsasRH0+XqgFZtE
vRrXgU2vDR3a7rio26SN4lnUqK1pCQ+wu1+bPEH6tJFpb5SQaW9JRv3d1cSN
iR7ZxJmwCYebilt0K6Oxzg7WAygEZRSYlIZW2ziaWwy9wb9YPSFy/nNb0hrr
AZUDj5H+8tFbYaq9Zt+KHfbRmV24DgVAW4ik0fbhvQ7kjP0KLu7uOOiQlsuo
Nki1iGWGEbau81vkze/J7Ke8ml1ujG5j2xgUS1LTR1vNq5GGYokGh6HnWef3
GAEj0Q7tQBIJbJNkvcFhlWrGkbdcIFn3NPawjEYudyvkZBzzRS7JikeXDeEm
ImjRvJg7pi0pq+PBbFVLTcEwvRTBqfs5rAKKkpSxhv3wVtt5pigKIqLz8fNJ
kbeLMXlgFcoz5khTAxqSImO0Tm3IqTpJYjS3wdsJ045QgA3nG/ST1xqhnrfO
7earNHBTWmr8nIpNFNIgZb7ChAT7oG7Anwd5weCcNOTUrgHltpOOqsU0reZT
N4XNMvuxUgi39KChcK2D5J7LaOzcuscOzX7nxQvRRJh2VGknJedvRaNffv3j
+dtLfUwoMEFGHOfGdro4dhOAtItj5crnh9o6muC72NRtv7sjF+yiFo8eYuc7
PDLq3kPmP42Wx18CYj4ZjvcDJWofZnwDByf5YVycCAg3q0XMI3TBalJEtpAJ
99IAvjTKL5rQiM3S86wiPquQgpXgje3A9ETTYCWzQEUAHQb0yHGCmwb/PE7u
Aa/Y45/otj26isv4eS318sz2mFb4TnyivOsseZrseh/YuPc6HB8/hk+jhoQy
nNdqAIa8wBBiJhvLiW/pcRik1qqioIZ2L6SDh4ha7GOhOkQPzf9SW9Z3lP57
d2W2OYtgr6fVE+jOxzUPJn1AtaixO3fyDsD14SSxzpupdpxjrGWzsx1ojKcO
qOSfg0WejB5w9Rkr2n15lvw2weo90pUTPnkNRECdOemJPwqD+E1ytidFfrrv
lIHLhZ34TbfukXoIauK1MKnL15d330P7y9hpuevep5wywE6PaKItSaDMOn8q
n1NLDhnwWlG0giujAyCyIANli4rDIUdgY02h9w8ZTmbNBMXcKPqwCYnlcJSD
zyjGjPCAMvkj0j5C5hHGScriOpQ123hzKioU94BwEQx5j7Fw0zONWAXNfdrh
qtpWjAviISxSMsGlFJFbZl6iLlZ+0KljeVv83QBgRaJiUbKLphkriJYbj3Qg
1xR3Dh1ZwoWDoGQ52AFWjXj3vxVQHenapoUjMKkKNdL7CO/dcOtw8n8Gyjo4
Kf4+pDVyTDJfHOMjxer5Sy4dR5Xg3Jcm+XBfhrrEwkN/qKjJluiLrF4TvaCI
TcnfqKR5lx5x3M+F54NgOTDdlHxfPvBIDXaz0O6J2vM0Odzfo/U7ODrqXvbI
XXa0L+h4L1W10N7DI3nEgyOtFPdGX5UOlKbjIlN545wS9hCt+sfqyN2V/Q72
H2krrcAt7ITrEsETv0R5/WWC/z2G/2DOg6miHKaNam8ryJz2LNaxMOE2worM
t2W2wvqjO5sAk8As2NCz3kPESEl8IR9sq1A4QpGNgRxg5aYuYwTH4NXRF2ff
vrXBaSHYE8LZEejg8ZMnvg2xQrvlAHYUbY+V0LX8Rfzj6EW40z1e9aIaOz3k
cimxep8rs0vRtF5F5JHc5q5v0O4Qyr0YeTuY6wfcjpyzrvOS+pmxa2nIgJAL
2CPr3xIb4gxv0RpSrntaGnnUXL8AmpgCkotuQ3Uq4gVXLnMpuUx85g8bhOiR
GbwtZ6BFlFoVC8hLUtJy7vIUbbCcFF6J0DhkBh98YBCoFg9Ltcuvr1xszTJE
jbx//3vf6TbqUwdDv39f+7665nXSV82PimQ2e9hQoB0HOaJBMAJrWFemk0Ef
D5AjOYe0ll+OvYXczkm4KVhLPyMRBtTuaC9ZAyW/XSYXW0E9aZu759GihWvy
eMi0Ia3Thw/KiYhwVLgI2KuFYe2RJy6oIefJiIpzHaO1/aIZOo7+9hMh2Q4G
xarOWEn4qP3qNtTVbWuYOHm4DcvZiQSad12XglKGWCBtXaEBr/9dOHUrmm0R
CJjSkNNPLGkH3n8aBA0X6aCm2K26eMlbWmvJQ3GQh0McgOJMBK7F5xno5klV
+vqBerAFKJsJfL61gkCRYOKWbtTiayGVCrmRoq3jLSHUZJczzBzqhsJ2DpSL
fkoJQMnwClWMmLVyAFIx9lynMK6rcYhH/jSqtS09eOCou1ZD2taW494YsfOR
H0nll1WaS7vHfM4aFGanI7PcORVuURS0ADmBOL8Q0JHeJhIbRH9m08m0uBT+
9pQf82P9ETSMv/7l8kTcqAEj3QFBJy+k/XlD7NDVzPJZ9NSFJLlsL7ktQ0pG
HPVlzTQ6mIeqdbj2mJz2gqcfKIcawAL3veL5SS0yaZ+lraKx9EZocsQtGzbl
sScdKUjD/WR0la1TKje1LKgej353T5cczcs9Df4CPeTLxcB20PtdeVuMC4Iq
JE2YyGS/f/9MJz4TuRIS/wU2zmyTBAIzXcFVkDqFo03F/RMrH3yH1d1owokP
Vkbv8mkeepgxl806j+1IT+njF7jXWkwdTirgbpVNyOGRMgKgcFBC37a1pIPT
cqh5XxoAKe7QR4iVOIWB7UQNcKc7vEppuJbC37iN1EGQj5YTH9TjS7tqnd49
Bm6fF4KSAhKpd4/CX91rtxfVgdAmY70vSGkOp2cFTBXZecpFcMMKS8LeTnte
GiSGDAZHYeR1QVrVc4a0aXXRZGuLYMLJ8qLgWPSEs5Q4A7V6B+6n707a2c8u
9s84r8xAW7uoCllgutzB7iI4veC8K3MRR0mficm0lPF0yjCJ2sdUc5JYKNkq
TlpWP1WtCn209EX4DDJLOYf1EngwER/W+JLVDt31uPmRuvtrnutUWrPaBj7E
DQyVRHAD35SOc/Y7DMcKqacJS3ShBsSNON4ofMndTiNVh0aK2PZmUJySHkXf
LjBnpeo04Fvj6jUd0ER0BSmx1AVpszRK0SBMyNTC+roNSJ/kt09lZy4dbxcX
YZxTRXqAxHsE4NFvDEgRCTq3FpSVUGOcmSdF46hEG0xH7SiTwNyIKFO/lRPV
bljkQYvTgigDmBJ9emVgOPOXNKTQwIYzLCmHUcyhU1c0rduGRxtP5FImsJNr
FEms0OyVo+R4v++KTY2wMTBLWUu8moYklIwlbgnkct4qORpAc1gqhDOayIfV
dp0eaXL56rJre5Jw/xtK9Hgl0nsuh4v0pFYfh2atGCEcPY6pV58HVePQgT1C
SKqCSESVF6Qi+mofKkqs+WVNQsCpl7yey6rlXh/ks5xHZbBTBUkNHBSUfSdE
HjiGjNEDJXsi9JXBLBf1GaPFlM/BZ7qByVE3+U1dYptEiit0e9QnMzySOQfv
iHA4GEv1+qitRMXyNHREsR2ERU2jpigaNpAmQ9acrNsjZTSKOxzaMQv9rJ2f
VfN5OuE1Nd7UdzWQRCmmX69ttNHwHTnQuO8lB0GqTkI0JYhTOix25iFJwKTX
SeuHi1ZoTSHDVUbUbcGMxqzW3qcgEp2242CFGKiKeKRk1sUMII3OQEgOE8Of
3E1DuslwD+YUdOOOJNvz/QaId6Y7nAyi1XaMOrEfXAl/7BuKPgQGSa3ZzApQ
h2M3Wyu3FQxYurWahjNFO75pq8UitS5B0Ro5Dbbshmj1tAcYJ1c1KIgfAL+c
09mEa3XYZK0bw+UWFkFttqdbH1YeElKL+QqF0xLPOdlxf2iM2xUpIve0YVfQ
T8kB+1yQoc9FTGIwKnQkx4oMvHS9FS2DiOXVhImKibaq+MXtYC2EgUKYt2iC
ofeDepFaHqx2nD0dWCaeZm5W7Kf2oNtSInn/9ZvvXj0XguJA9G1F1mjbRNTV
MzVJPerOoeGTE1YotYL6RsAdn2k+3xMhtGsXZXpVtJ/38HkaQ/DazS5nQDqY
IN13OAwlS4ciQoTTQYUt9QVp8IFBz+PC2CmDHbighxGxruFCKqaGzSfQ3bDb
AbuJNWQTRGqgIJTOrquKNuGvf+EIGooeLr2PqzyTEAUq45GCLmFGLKJA2aqE
8/RmlsTY4gaQZhEOlgI86TzCrMSCqgajhxNbRvpaq+EpZpXyo3AjOo8L5jt6
Ijbc18V5Ksi9hA7wMXbGWG6kzyA2g7QSrFq8JrJu0PaILJzgKx2ylbRvEAUz
sim9KowSVmN8m2211TPxD65dz8qjXxPxe04Jh2bwGNbtdJG4k3R/hZi65ho+
xpupFoFSAeoPY9YfhAYonofosRYr6nDV1uiV3JUTflwy6WBNT1FIGGUMpCZ3
MLszlDMHZWtQlfMvGps6owd9m0DBLjE/ld6SLRXHbmWHemdAtDlyujmEsvSB
LWfXWNpeCjXNzR/EtcvmzkO33JoCGKpi8Bl6H5J6cycEzDM51kF1W34bDJ1M
4sjylFI3iswh9hUqhbsuQKXvDy7R/it5A/Fs9zVrkq4hgKU04y2rHAOORbNK
pTh6o4fYLWZUh5rDRdQvZUeR4qlgnDAGuTPrGbUAwQ64ipTW0BzX0bIjyeZ8
dESZMAoD6pW6Q47iglpSuXBNeIDh/ucU+iM3tiq9qyiZohCoH+v7jMPB+ZXA
5TmKhCLWRqlk9GuXmg2uUs4bIl9WS7JBQlsoGEr1S/MakZKBmAKqn4k9X9eS
4sHOP+mL5oZiHaBIfwv2ayo50dRNeVPTKazZKdYJm+M4pRQvV5MYLCER7Eer
AMBeeLmHfc6s/wWJqaeQCcDIxjDx2hGFkL7afnxplRSspU8W9s9KkbgGdKxB
4rkk+1o6UqtaMY99Ila4Xi3vsGg8Izts/ekkF6BEUX8i7KAulUhhoRnjloqK
wTZyBEToFH4jkYxVZbnXrlk8UTcgi9XFaSPBpuMFJHgr+1L5hAhoVRojL6ns
5vwE1oPfiU+ZLlFB09JRnny7TUsjzocCz2l4wW/vvHK/l8IA3G45PM4yguRK
Rwxx9aJlpYU7+/26fHk5bulcO+sjUjrk1GLAROp5hnLynjTOF+4J3oInmgRB
ekOMISr9w81to4lzSSXZepQNOaKx3MKy/lZz6lSLMnKpHogC58fxL123CF1A
mnB8p0sbgjdREdZu9yKVeq6WJTNsTQpC3YgcOaQ1Mb4NHVDZIqdMJ2rY+Gvk
PFk0g7qOzZwIYaZMNo1wDofMDyyJehGVYM6sqxkZ5o5qteKXMKeaWjPTu8c4
M4+051wERcBi5gAlrnUdu3ruKADs2lx7NtGFIlliF+KM7jxlyCaoMtlSYz3e
hEoNqBSfJvakMXySr3GiVOJ3Usq/FmeFntUYhx/cbBGBTZLvJLYc8bE0VhO6
eRfwzPqutTYeYOeae/y9CrXhHQl02yA4dsDa0uWrS3Wvd93EDtn5ad/nudYa
QsvRqOz/o/e2n9WFHmtyV8dOVZnt3+TADhI1uLF3Ozn/Vu8m+mAkE+LNWogX
1knSm3uFdBidJyhVO+9s2nBn0KJs41abRnpX0qOn2RRtTHCWlk6VMIybUK2j
uAbMADYFdw+kfkARmzbBga7QM3E3fjkgq/WpmcCqhUZLeoeC9CIGGnKLx5Q7
IsYYQ0kzAruy9kZo6zgwOWNYUgknIF9jl7FbTlRXSMMqa7hbkJoN2DhTMGzS
p4bTxnlmY5pOwJP9N4J2u1G5mtrdNJWFZm70NHjfB8OVoJA0Jcbqql8m3Evs
qyFvQcf/ZoKVTr71DnHv5RJQPeeMn7gDRvQzGlgNAs2u/wBfo+3eoasFEHqs
7bmqlbY3G/YDH+ojHUJtCOeVxigvcVsMIN2G5obvmP2X8FiDSCz1Js18/GpA
cRRVdjhIFVwWzgseolY+UiWMwn5tWgZA/dciUHKqzA8/7/Q5hWH89S/0OYhG
dfD5HRlfY5aiywonjU88P+YCvBN+JfZnFjoizpk0Jir4ROgKaw9WZm95086b
wwUpk4YGlT4lJjOto0XNLagFWcVJjMrQ/DJNkteicFtWuPZk8fpfV6PzCoz1
jQKekmNtdE3bI20BF561hoCYGT6nVW0XhMAYY12AxpkrS8031mp0hNZ9ijTK
0G4J79j6+uGUkvmzYQfmo44F6a8GOvjBsIMsGkME0UZTUSqvVXok1eBb6gSl
mvhg992otUZgn6nkRV5VLZUCGoqBkDASRtyRU+btNs4MeszKckqDM5Uj1utK
dCG8D2UpBWORRllBlUJ/PWdQ8FEan2+4rkf3Uoxq4iMkU8eqWw8C4tn2lLAj
dwzoZCjf61eA2VOu/v3r8yYwQq1W26vYJFcPZtN38/I1Wd4cjZ+u2O9sHZ9c
38l/wrfpSLq6w3Cl1VCUeFgFIEcz1VrpSjlpzSLHqlNShphB6pnYWL35aouE
mgB9+ZN+SoEJyYEYaaPKGMjVb6u9+NaO/NUQv0o/5KF98IYKVXKzolDSfkyu
sUGvi46mzEzzCO6hqAkXRWqbXguESfI1Gb7dPi9bhsxnNXVa67jXTmICCZku
kijkey9MhpQuCXoCN8OYm6IIUrb/dtZLwuQFVuLXNS7eDAueEPJAfEjB2XzS
7/WgCGjfieNT7YB29ABanehDDfJwYnunAcbh8OyJo6ThIPJQlPVkyHl24mAT
mHG9p4AG+KYHfQjWa6/oB1xOy42lPzA9pIuPaE7uAkjsjEMrZiLUwB7GTaSx
ZqOtMbvHurHWd+Snnm3qnZJoKMt/Vm/XbXVVZ+trJtA2FAb4VbolujMfjVGb
NnNulnaRDI4/Knnh03UsRSDywJLIVBk00JrHn53As4fa2pi7aViA/fzs01DV
xjkx8NV8teg5jETHVqlxXlY8s2wJCk7nWRygxyVRl4KKRnOVRM9k8BhpQgRe
wfhcNZthiYEuoIxCqwYqc9q6t63fryuwy8orLGUw2NjDsno2aMq37CKKg0bk
vIX9ol722JmLAAzaoVl8GzA4pKPB3eKOKuXcrQvPnApVUG+eisJuCFHrUoU2
16Nh1zk2n+ABqA8eWzij414XFhe7qrU4R39hkq6bWokpyidDMAQ6xGYzIljy
itf1Zs0WlLbtDko05yRSCqfohLApTNVhZcVVH1iger5x/G2LK1pr2e1eepul
EcblJeA1jWwyyyaq4cZ9pewLRdrP8rrU5kzmyxPBJvhcTwhzK88SQsNwyflb
YGz9+APzEOlgQxQwVgq4Cf4T6dWbz6lGc5zLuCiwzBBrpxnF67ClVOu7hzVG
hzVplt2IKTsGFW+sbkhpFg9UiO5fikSIAE/92vNrGXkREfmMtfYyxH4tXGqe
TjkIt3VFrhjOmK0HCV8BgeoKqjQQqdXJQyEHs7Oir2hDOWmKbJNNCeriHJ5I
i6PFz1x/kjorDIJBYLFFcrVh/EsaaReu6gbBKQVyQfqFD3tckG+nLa4sYkDa
6yDx9HwAIfySg0BW4TwaveucVX0s1QREcA6zFbdhuDFy0jveSYFaFK1U5AJS
2pD0PI6SqyyXuK/s70oL5gN0t5ptCTo+cxHfJ75QDzrIu21ZL7sYtC6wTMl7
yBXle6WSb6FH3xwMpCZO7nyg8EJJQ94S92DV/iN5JyyDkxgjG0G0TzMGQsfA
Mo9UNtFPRTfjxaI91/42Yi8TYCeTh5HJrh6wQvLE0Evm8iUxHBbmFQM4QJ+x
Hl0c8eB3YoBVZPJgvHbiyNSlAU+ComO1FDelL71lZMySOpSuxK4oo9HzweCw
BkDuMLZwzg2ngLYhjYhF6DSngI8FpNtbpEEH6whut1vQlECxo1hXCHtQ5HQb
KZyn8qGrZUPOBtZvjAeiVcfNiAZekyaVz/zJGxe/jcPfVs9oKNbt4pRVN7KY
atqh+q99HhT+hvK2E7P1K981GuGoF6Hakk3TkCUapZ1gzEnrCnqhzjvIa0fe
WD2JAYy1S+Rq0lNbjPl+oR2qtdQzItzhZG5hyV8aquSt2g1MJJArCnJn2LHP
Lua3LlMQFwWBMdzchOqLGtIqhs6TlOqLWcZ10jZGajOxdWJxouWxq0AMrIDH
VUvrxHyDCBxOpeqU6muT5NviY2zoDUALBMZoqqyHnhFXC4Rg3TyMqe3ElYlC
gO5NyeOzs2qJ56iEcvUDKaFkESIsG+LKGobu4bNquSw4uUXwjx2hCBIH1kXo
YJqz2cqGKDWlvNsItdC79K6k7lV4W7fH5M7WHju8eDvcd4JTM8coVpOwlsyC
LIk7dVCRx3/8ZJVHUSAMRiW1kkhf5UJYbiZwsatt6EtedmpZooQD4jwRNqdZ
RUiBJc9T+bava5LDm/slI6WOpfZiUY+xFEIOrIiDebfeFS5LSpU1eZ7RGjEB
InzDV5YUVZjfzy7aTIpzRg5RQvNjeDIU9WwaAedRlTcQbwMtTbNOK1RX01Oj
aZbMIEUkkL6oMTaNniv2Sg0eEstMtS+kiiEo9+Qal1+ttlZYOnTSrHJ2zknF
IqOw3bUrJ7i8slD7yb0Q1qBV2zshpYVq/GKR4v39B/sPnsCnxiUO+OPoz8Ge
uKlu2nw9PsRKwFZDSkv+cq0lqlOIRZ20LtJAgSkuf7xcghpSM4V1SgRiOaaH
B0f6ZIbsws///m/Fv/8HPL3AmSaHDx/hgxSvjLHAp8nDyX6CTrU+/MMQX6/w
sn26Tk5kKDLIVaE6SAarkX0joPhuOakCyyQfPf4q+2r6+Cvqt3YuzcPOpAPY
e68+/4TF43NXVQo+kc5L0ijg3nX+cU/agcnPQx0mdvacoC4LWNDqJ65VpR0o
nuLOIgE81Z3nfZdv4j3nSfAtNA/8EZ/8f/7nX6wfBf7+iNpc7P/drzmIX6ML
Cu8ifUEOTnJ6nLzKmnaseJXxS3IghjR33lTqXmlc+x5n+x1whXQLHJHnVrU4
UXeJDWj1hO4D9rs9ugMikc0fMS6jt3/RRL0ITaOheod4dT8XP4SqLDcj51Z+
SE4vkKftphqGB/+UPJPqDaQIWbWYT5ISEhEdD/hgeBUOwqKx9/aX3fm3L14/
P3/9z/ATfEOUpsO5Y19sRA2cd8oq8fn8qGg91Kf8kofh+YtX59+/ePcC2xIe
4GhHz01L99HvY8fSTpSlHEd840wTOnnDHL1bpOPpQaoxjqf7nNaJ/5qth7+Y
V+5HiSHghxaTwF+Qlf9oDlh/Gfldfgxxhqf7k/jwPTsODJdDEKPRG80CGT5y
tjN8cuSY0LEhzj6csQa/IxF+SbumfH2CPRS5NgzYp416bzj6cRdtELwrttb4
tcfu6JLac2eJGjTmrsiB7grUiEULVvw25wziQnK4+QtXiqYSrdNzAwuWdutR
7KhQ89+QB1BhoBO/s2nYVd5FJ5x/bWbxlb7l5xDGEE2cxDQxsI8OcGbb1dmn
X5jNvDq9eKFT3MUonnlGsR8YxYEwioNfn1EkF7m0rn+mqWl9C78Xkebet+ov
oWjeMKpULNEhgCar8M011c2wvDhxBcfdT7u7xxr/bVbPWetGm1Ua6yCHIR8W
NujgtBvpRyneAYdGOkl2wL7b8AiC4U6SU/LqYH1uq8zGiZlkG71AHNF4UUh3
kDInXXNc3ZhXlgrvE4fidhdwGZZLjaoTZFdo/KtmLZV1thaTEJetxJqoaD0l
RnTKEt9XkBkzLKqx0GjpKi7nOLZTwD6LkJjO9c6GawaEILl01bB6A1a5HssK
UJ2nHnor7QS3O2D1NHJze7C8JLJpngVM7zXankstFG5kgO3QpLaExO+oUsIV
RYHQjVVoAlI3NK/uEilZXS26kBxaVCVQAfSVNIrfOIpcFR9Tl6Hze/QtmwHC
o8Xs5QbdVtITaDEAvUNKSSXyLwJGvPqy33UmNlZNaqhAPjWDdZ3XmOdXLAVs
yrXGMRCBTi05cy2jztUcrsgdhX1QM660JqvGr64lISnnD7lNq7rmYWWMtzn5
+0sUtfh7K1KM/i/gwrpaFvoAAA==

-->

</rfc>

