From 810dfdf6183c858a1cd714ce0646a3b509f84b84 Mon Sep 17 00:00:00 2001
From: Steve Kille <steve.kille@isode.com>
Date: Thu, 5 May 2022 15:29:30 +0100
Subject: [PATCH] Updates to use SLEP

---
 xep-0365.xml | 1 +
 1 file changed, 1 insertion(+)

diff --git a/xep-0365.xml b/xep-0365.xml
index 8397ea92..9fb7acf1 100644
--- a/xep-0365.xml
+++ b/xep-0365.xml
@@ -62,6 +62,7 @@
    This specification arose from requirements to operate over HF Radio, which has exceedingly high latency (sometimes minutes) low data rates (down to 75 bits/second) and poor reliablity.   <span class='ref'><link url='http://nso.nato.int/nso/zPublic/stanags/CURRENT/5066Ed03.pdf'>STANAG 5066</link></span> <note>STANAG 5066 C3B (EDITION 3): PROFILE FOR HF RADIO DATA COMMUNICATIONS &lt;<link url='http://nso.nato.int/nso/zPublic/stanags/CURRENT/5066Ed03.pdf'>http://nso.nato.int/nso/zPublic/stanags/CURRENT/5066Ed03.pdf</link>&gt;.</note>
  is a widely used link level protocol.   Direct use of <strong>STANAG 5066</strong> enables elimination of all extraneous end to end handshaking, which is important to optimize performance.  It also enables use of <strong>STANAG 5066</strong> flow control, which is important for reslience.
 
+
   </p>
 <p>
   The solution is based on &xep0361; and requires peer configuration to be established according to <strong>XEP-0361</strong>.  The data exchanged between the XMPP servers follows exactly what is specified in <strong>XEP-0361</strong>.    The data is transferred using <strong>STANAG 5066</strong> rather than using TCP.