From b34738ed08c2227300d554b139e2495ca5da97d6 Mon Sep 17 00:00:00 2001
From: Yves-Alexis Perez <corsac@corsac.net>
Date: Thu, 28 Jun 2012 21:16:07 +0200
Subject: Imported Upstream version 4.6.4

---
 testing/tests/tnc/tnccs-20-client-retry/description.txt | 13 +++++++++++++
 1 file changed, 13 insertions(+)
 create mode 100644 testing/tests/tnc/tnccs-20-client-retry/description.txt

(limited to 'testing/tests/tnc/tnccs-20-client-retry/description.txt')

diff --git a/testing/tests/tnc/tnccs-20-client-retry/description.txt b/testing/tests/tnc/tnccs-20-client-retry/description.txt
new file mode 100644
index 000000000..c8e1afd81
--- /dev/null
+++ b/testing/tests/tnc/tnccs-20-client-retry/description.txt
@@ -0,0 +1,13 @@
+The roadwarriors <b>carol</b> and <b>dave</b> set up a connection each to gateway <b>moon</b>
+using EAP-TTLS authentication only with the gateway presenting a server certificate and
+the clients doing EAP-MD5 password-based authentication.
+In a next step the EAP-TNC protocol is used within the EAP-TTLS tunnel to determine the
+health of <b>carol</b> and <b>dave</b> via the <b>TNCCS 2.0 </b> client-server interface
+compliant with <b>RFC 5793 PB-TNC</b>. The IMC and IMV communicate are using the <b>IF-M</b>
+protocol defined by <b>RFC 5792 PA-TNC</b>.
+<p>
+The first time around both <b>carol</b> and <b>dave</b> fail the health test but they
+request a handshake retry. After remediation <b>carol</b> succeeds but <b>dave</b>
+still fails. Thus based on this second round of measurements the clients are connected
+by gateway <b>moon</b> to the "rw-allow" and "rw-isolate" subnets, respectively.
+</p>
-- 
cgit v1.2.3