Request help with the interpretation of F5 URIs in the docs

Some F5 VPNs use these to complete authentication and handoff to the
proprietary client, and we currently don't know how to interpret them in a
way that would allow OpenConnect to be used instead.

See https://gitlab.com/openconnect/openconnect/-/issues/639 and
https://lists.infradead.org/pipermail/openconnect-devel/2021-August/005035.html
for further discussion.

Signed-off-by: Daniel Lenski <dlenski@gmail.com>

diff --git a/www/f5.xml b/www/f5.xml
index 37fc873b3744218411cfa9277370937c8268a9c9..e48b73505d57a0d84814a38fe64da7829bae6f0d 100644 (file)
--- a/www/f5.xml
+++ b/www/f5.xml
@@ -52,10 +52,25 @@ or similar (see issue for details on how this was determined).</p>
 RSA or OATH tokens), please send information to <a href="mail.html">the mailing
 list</a> so that we add support to OpenConnect.</p>
 
+<h3>DTLS</h3>
+
 <p>Connectivity over DTLS is supported. On BIG-IP server v16, it is possible to use
 either DTLSv1.0 or DTLSv1.2, if configured correctly. On BIG-IP server v15, it is limited to
 DTLSv1.0 because experiments show that BIG-IP server v15 cannot negotiate correctly down to
 DTLSv1.0 when a newer version of DTLS is attempted.</p>
 
+<h3>Interpreting <tt>f5-vpn://</tt> URIs</h3>
+
+<p>Some proprietary F5 VPN clients use a web-based front-end for authentication.
+This authentication flow terminates in a URI that starts with <tt>f5-vpn://</tt>,
+for which the proprietary F5 client is registered as a handler.</p>
+
+<p>We do not yet understand how to interpret these URIs in a way that is sufficient to
+allow OpenConnect to use them to establish a connection. See
+<a href="https://gitlab.com/openconnect/openconnect/-/issues/639">GitLab issue #639</a> and
+<a href="https://lists.infradead.org/pipermail/openconnect-devel/2021-August/005035.html">this
+August 2021 discussion</a> on <a href="mail.html">the mailing list</a>. Please contribute if
+you have information that can help us understand how to use these URIs.</p>
+
        <INCLUDE file="inc/footer.tmpl" />
 </PAGE>