xeps/xep-0365.xml

<?xml version='1.0' encoding='UTF-8'?>
<!DOCTYPE xep SYSTEM 'xep.dtd' [
  <!ENTITY % ents SYSTEM 'xep.ent'>
%ents;
]>
<?xml-stylesheet type='text/xsl' href='xep.xsl'?>
<xep>
<header>
  <title>Server to Server communication over STANAG 5066 ARQ</title>
  <abstract>
  This specification defines operation over XMPP over the NATO STANAG 5066 data link service for point to point links (ARQ).   
  This enables optimized XMPP performance over HF Radio (which STANAG 5066 was designed for) and over other data links using STANAG 5066.
  </abstract>
  &LEGALNOTICE;
  <number>0365</number>
  <status>Experimental</status>
  <type>Standards Track</type>
  <sig>Standards</sig>
  <approver>Council</approver>
  <dependencies>
    <spec>XEP 0361</spec>
    <spec>STANAG 5066</spec>
    <spec>SLEP</spec>
  </dependencies>
  <supersedes/>
  <supersededby/>
  <shortname>S5066</shortname>
  <author>
    <firstname>Steve</firstname>
    <surname>Kille</surname>
    <email>steve.kille@isode.com</email>
    <jid>steve.kille@isode.com</jid>
  </author>
  <revision>
    <version>0.3</version>
    <date>2022-03-28</date>
    <initials>sek</initials>
    <remark>Make use of SLEP Streaming service, which was not available for 0.1.  This provides a better service mapping than direct use of 5066 and provides compression.</remark>
  </revision>
  <revision>
    <version>0.2.1</version>
    <date>2018-07-21</date>
    <initials>egp</initials>
    <remark>
      <p>Replace references to draft-ietf-xmpp-websocket with RFC7395 (XMPP over WebSocket).</p>
    </remark>
  </revision>
  <revision>
    <version>0.2</version>
    <date>2017-09-11</date>
    <initials>XEP Editor (jwi)</initials>
    <remark>Defer due to lack of activity.</remark>
  </revision>
  <revision>
    <version>0.1</version>
    <date>2015-09-17</date>
    <initials>XEP Editor (mam)</initials>
    <remark><p>Initial published version approved by the XMPP Council.</p></remark>
  </revision>
  <revision>
    <version>0.0.1</version>
    <date>2015-08-19</date>
    <initials>sek</initials>
    <remark><p>First draft.</p></remark>
  </revision>
</header>
<section1 topic='Introduction' anchor='intro'>
  <p>
   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='https://www.isode.com/documentation/S5066Edition4ratification.pdf'>STANAG 5066</link></span> 
    <note>STANAG 5066 C3B (EDITION 3): PROFILE FOR HF RADIO DATA 
      COMMUNICATIONS &lt;<link url='https://www.isode.com/documentation/S5066Edition4ratification.pdf'>https://www.isode.com/documentation/S5066Edition4ratification.pdf</link>&gt;.
    </note>
 is a widely used HF 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 resilience.
 </p>
  <p>
    The solution uses the streaming service specified by 
    <span class='ref'><link url='https://www.isode.com/whitepapers/S5066-APP3.html'>SLEP</link></span> 
    <note>SIS Layer Extension Protocol (SLEP) (S5066-APP3) &lt;<link url='https://www.isode.com/whitepapers/S5066-APP3.html'>https://www.isode.com/whitepapers/S5066-APP3.html</link>&gt;.
    </note> - SIS Layer Extension Protocol.   <strong>SLEP</strong> specifies three layer services that operate over STANAG 5066, including a streaming service which
    provides an equivalent service to TCP.   <strong>SLEP</strong> also provides compression, which is mandated for use by this specification.    
  </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>SLEP</strong> rather than using TCP.   

</p>
</section1>
<section1 topic='Requirements' anchor='reqs'>
  <p>
    This specification can be considered as a profile for server to server XMPP communication, to enable XMPP deployment over HF Radio using <strong>STANAG 5066</strong>.   
    This profile MUST only be used where its use has been pre-agreed and configured for both participating servers.
  </p>
</section1>

<section1 topic='Use Cases' anchor='usecases'>
  <p>
    An example scenario where this protocol is important is where two ships connected by HF Surface Wave communication only need to exchange XMPP messages. 
    A reliable link (Soft Link) can be established using <strong>STANAG 5066</strong> and XMPP communicated efficiently and reliably over <strong>SLEP</strong>.

  </p>
</section1>
<section1 topic='Business Rules' anchor='rules'>

  <section2 topic="General Operation">
  <p>
    Because of potentially very low bandwidth sending server MAY perform traffic optimisation, such as selective removal of stanzas that are not adding sufficient value, like CSNs, or strip selected elements such as xhtml-im.
  </p>
    <p>
      Applications sending data over <strong>STANAG 5066</strong> need to be aware of increased delays and any application level timers (e.g., IQ response timers) need to be set accordingly.
    </p>
 
    <p>
      &xep0198; MAY be used over <strong>SLEP</strong>.  Although reliability of stanza transfer is provided by use of <strong>STANAG 5066</strong> and <strong>SLEP</strong>, use of 
      &xep0198; is RECOMMENDED to monitor link latency. 
      
    </p>
    
    <p>
      Application-layer keepalives such as white-space pings are NOT RECOMMENDED.
    </p>

  </section2>

<section2 topic="Mapping onto SLEP">
  <p>
    The stanza stream is transferred using <strong>SLEP</strong>.  <strong>SLEP</strong> compression is mandatory.

  </p>


</section2>
  <section2 topic="Addressing">
    <p>
  The peer addressing of the <strong>STANAG 5066</strong> end points will be configured as part of the <strong>XEP-0361</strong> peer agreement.
    </p>
    <p>
      The <strong>STANAG 5066</strong> SAP MAY be set to any mutually agreed value.   It is RECOMMENDED that 6 is used which is the value 
      specified in  <strong>STANAG 5066</strong> for use by this XEP.
    </p>
  </section2>
</section1>


<section1 topic='Security Considerations' anchor='security'>
  <p>
    Security Considerations of <strong>XEP-0361</strong> apply.   <strong>STANAG 5066</strong> will frequently be employed in conjunction with link level crypto devices, which SHOULD be done when appropriate to provide data confidentiality.
  </p>

</section1>
<section1 topic='STANAG 5066 Standard' anchor='iana'>
  <p>This specification uses STANAG 5066 Edition 4 "TECHNICAL STANDARDS FOR HF RADIO
    LINK LAYER AND APPLICATION SUPPORT
    PROTOCOLS FOR SINGLE CHANNEL
    WAVEFORMS" (November 2021). </p>
  <p><strong>STANAG 5066</strong> is a NATO UNCLASSIFED  (Releasable to the Public) document that may circulated freely. It is available 
    on <link url='https://www.isode.com/documentation/S5066Edition4ratification.pdf'>https://www.isode.com/documentation/S5066Edition4ratification.pdf</link>.</p>
</section1>

  <section1 topic='SLEP' anchor='iana'>
    <p>This specification uses the streaming service specified by SIS Layer Extension Protocol (SLEP) (S5066-APP3). </p>
    <p><strong>SLEP</strong> is an openly available protocol specification with no license restrictions. It is available on 
      <link url='https://www.isode.com/whitepapers/S5066-APP3.html'>https://www.isode.com/whitepapers/S5066-APP3.html</link>.</p>
  </section1>
  
  <section1 topic="Acknowledgements">
    <p>
      Curtis King designed and validated the original approach documented in this XEP.
    </p>
    <p>
      Kevin Smith provided useful comments on this specification.
    </p>
    <p>
      Dave Cridland asked NATO about STANAG 5066 publication, leading to its availability on the Web.
    </p>
    <p>
      Edwin Mons implemented and validated the SLEP mapping.
    </p>
  </section1>
</xep>