add some clarifications about Pulse vs. NC to the documentation

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

openconnect.8.in

@@ -80,8 +80,10 @@ protocols for data transport.
 
 It was originally written to support Cisco "AnyConnect" VPN servers,
 and has since been extended with experimental support for Juniper
-Network Connect and Junos Pulse VPN servers
+Network Connect
 .RB ( \-\-protocol=nc )
+and Junos Pulse VPN servers
+.RB ( \-\-protocol=pulse )
 and PAN GlobalProtect VPN servers
 .RB ( \-\-protocol=gp ).
 
@@ -452,9 +454,19 @@ to be used for the connection. Supported protocols are
 for Cisco AnyConnect (the default),
 .I nc
 for experimental support for Juniper Network Connect (also supported
-by Junos Pulse servers), and
+by most Junos Pulse servers),
+.I pulse
+for experimental support for Junos Pulse, and
 .I gp
 for experimental support for PAN GlobalProtect.
+
+OpenConnect does not yet support all of the authentication options used
+by Pulse, nor does it support Host Checker/TNCC with Pulse. If your
+Junos Pulse VPN is not yet supported with
+.BR \-\-protocol=pulse ,
+then
+.B \-\-protocol=nc
+may be a useful fallback option.
 .TP
 .B \-\-token\-mode=MODE
 Enable one-time password generation using the

www/pulse.xml

@@ -36,8 +36,8 @@ should be usable with OpenConnect in Pulse mode too.</p>
 
 <h3>Host Checker</h3>
 
-<p>Not yet investigated and implemented for Pulse mode. The Juniper support may
-suffice for some users.</p>
+<p>Support for Host Checker, also known as TNCC, has not yet been investigated and
+implemented for Pulse mode. The Juniper support may suffice for some users.</p>
 
 <h2>Connectivity</h2>