diff --git a/README.md b/README.md
index dca3628b7..369e01925 100644
--- a/README.md
+++ b/README.md
@@ -120,6 +120,7 @@ The prod server (acvts.nist.gov) also supports ACVP version 1.0, with the same e
 * [AES-XTS 2.0](https://pages.nist.gov/ACVP/draft-celi-acvp-symmetric.txt) - [HTML](https://pages.nist.gov/ACVP/draft-celi-acvp-symmetric.html)
 * [AES-FF1](https://pages.nist.gov/ACVP/draft-celi-acvp-symmetric.txt) - [HTML](https://pages.nist.gov/ACVP/draft-celi-acvp-symmetric.html)
 * [AES-FF3-1](https://pages.nist.gov/ACVP/draft-celi-acvp-symmetric.txt) - [HTML](https://pages.nist.gov/ACVP/draft-celi-acvp-symmetric.html) - DEMO only
+* [Ascon-AEAD128](https://pages.nist.gov/ACVP/draft-ross-acvp-ascon.txt) - [HTML](https://pages.nist.gov/ACVP/draft-ross-acvp-ascon.html)
 * [TDES-CBC](https://pages.nist.gov/ACVP/draft-celi-acvp-symmetric.txt) - [HTML](https://pages.nist.gov/ACVP/draft-celi-acvp-symmetric.html)
 * [TDES-CBCI](https://pages.nist.gov/ACVP/draft-celi-acvp-symmetric.txt) - [HTML](https://pages.nist.gov/ACVP/draft-celi-acvp-symmetric.html)
 * [TDES-CFB1](https://pages.nist.gov/ACVP/draft-celi-acvp-symmetric.txt) - [HTML](https://pages.nist.gov/ACVP/draft-celi-acvp-symmetric.html)
@@ -135,6 +136,7 @@ The prod server (acvts.nist.gov) also supports ACVP version 1.0, with the same e
 * [TDES-OFBI](https://pages.nist.gov/ACVP/draft-celi-acvp-symmetric.txt) - [HTML](https://pages.nist.gov/ACVP/draft-celi-acvp-symmetric.html)
 
 ### Secure Hash
+* [Ascon-Hash256](https://pages.nist.gov/ACVP/draft-ross-acvp-ascon.txt) - [HTML](https://pages.nist.gov/ACVP/draft-ross-acvp-ascon.html)
 * [SHA-1](https://pages.nist.gov/ACVP/draft-celi-acvp-sha.txt) - [HTML](https://pages.nist.gov/ACVP/draft-celi-acvp-sha.html)
 * [SHA-224](https://pages.nist.gov/ACVP/draft-celi-acvp-sha.txt) - [HTML](https://pages.nist.gov/ACVP/draft-celi-acvp-sha.html)
 * [SHA-256](https://pages.nist.gov/ACVP/draft-celi-acvp-sha.txt) - [HTML](https://pages.nist.gov/ACVP/draft-celi-acvp-sha.html)
@@ -152,6 +154,8 @@ The prod server (acvts.nist.gov) also supports ACVP version 1.0, with the same e
 * [SHA3-512 2.0](https://pages.nist.gov/ACVP/draft-celi-acvp-sha3.txt) - [HTML](https://pages.nist.gov/ACVP/draft-celi-acvp-sha3.html)
 
 ### XOFs
+* [Ascon-XOF128](https://pages.nist.gov/ACVP/draft-ross-acvp-ascon.txt) - [HTML](https://pages.nist.gov/ACVP/draft-ross-acvp-ascon.html)
+* [Ascon-CXOF128](https://pages.nist.gov/ACVP/draft-ross-acvp-ascon.txt) - [HTML](https://pages.nist.gov/ACVP/draft-ross-acvp-ascon.html)
 * [SHAKE-128](https://pages.nist.gov/ACVP/draft-celi-acvp-sha3.txt) - [HTML](https://pages.nist.gov/ACVP/draft-celi-acvp-sha3.html)
 * [SHAKE-256](https://pages.nist.gov/ACVP/draft-celi-acvp-sha3.txt) - [HTML](https://pages.nist.gov/ACVP/draft-celi-acvp-sha3.html)
 * [cSHAKE-128](https://pages.nist.gov/ACVP/draft-celi-acvp-xof.txt) - [HTML](https://pages.nist.gov/ACVP/draft-celi-acvp-xof.html)
diff --git a/index.html b/index.html
index f47d4043a..d86d41774 100644
--- a/index.html
+++ b/index.html
@@ -176,6 +176,7 @@ <h2 id="ciphers">Block Cipher Modes</h2>
 					<li><a href="https://pages.nist.gov/ACVP/draft-celi-acvp-symmetric.txt">AES-XTS 2.0</a> - <a href="https://pages.nist.gov/ACVP/draft-celi-acvp-symmetric.html">HTML</a></li>
 					<li><a href="https://pages.nist.gov/ACVP/draft-celi-acvp-symmetric.txt">AES-FF1</a> - <a href="https://pages.nist.gov/ACVP/draft-celi-acvp-symmetric.html">HTML</a></li>
 					<li><a href="https://pages.nist.gov/ACVP/draft-celi-acvp-symmetric.txt">AES-FF3-1</a> - <a href="https://pages.nist.gov/ACVP/draft-celi-acvp-symmetric.html">HTML</a> - DEMO only</li>
+					<li><a href="https://pages.nist.gov/ACVP/draft-ross-acvp-ascon.txt">Ascon-AEAD128</a> - <a href="https://pages.nist.gov/ACVP/draft-ross-acvp-ascon.html">HTML</a></li>
 					<li><a href="https://pages.nist.gov/ACVP/draft-celi-acvp-symmetric.txt">TDES-CBC</a> - <a href="https://pages.nist.gov/ACVP/draft-celi-acvp-symmetric.html">HTML</a></li>
 					<li><a href="https://pages.nist.gov/ACVP/draft-celi-acvp-symmetric.txt">TDES-CBCI</a> - <a href="https://pages.nist.gov/ACVP/draft-celi-acvp-symmetric.html">HTML</a></li>
 					<li><a href="https://pages.nist.gov/ACVP/draft-celi-acvp-symmetric.txt">TDES-CFB1</a> - <a href="https://pages.nist.gov/ACVP/draft-celi-acvp-symmetric.html">HTML</a></li>
@@ -193,6 +194,7 @@ <h2 id="ciphers">Block Cipher Modes</h2>
 
 				<h2 id="hashes">Secure Hash</h2>
 				<ul>
+					<li><a href="https://pages.nist.gov/ACVP/draft-ross-acvp-ascon.txt">Ascon-Hash256</a> - <a href="https://pages.nist.gov/ACVP/draft-ross-acvp-ascon.html">HTML</a></li>
 					<li><a href="https://pages.nist.gov/ACVP/draft-celi-acvp-sha.txt">SHA-1</a> - <a href="https://pages.nist.gov/ACVP/draft-celi-acvp-sha.html">HTML</a></li>
 					<li><a href="https://pages.nist.gov/ACVP/draft-celi-acvp-sha.txt">SHA-224</a> - <a href="https://pages.nist.gov/ACVP/draft-celi-acvp-sha.html">HTML</a></li>
 					<li><a href="https://pages.nist.gov/ACVP/draft-celi-acvp-sha.txt">SHA-256</a> - <a href="https://pages.nist.gov/ACVP/draft-celi-acvp-sha.html">HTML</a></li>
@@ -212,6 +214,8 @@ <h2 id="hashes">Secure Hash</h2>
 
 				<h2 id="xofs">XOFs</h2>
 				<ul>
+					<li><a href="https://pages.nist.gov/ACVP/draft-ross-acvp-ascon.txt">Ascon-XOF128</a> - <a href="https://pages.nist.gov/ACVP/draft-ross-acvp-ascon.html">HTML</a></li>
+					<li><a href="https://pages.nist.gov/ACVP/draft-ross-acvp-ascon.txt">Ascon-CXOF128</a> - <a href="https://pages.nist.gov/ACVP/draft-ross-acvp-ascon.html">HTML</a></li>
 					<li><a href="https://pages.nist.gov/ACVP/draft-celi-acvp-sha3.txt">SHAKE-128</a> - <a href="https://pages.nist.gov/ACVP/draft-celi-acvp-sha3.html">HTML</a></li>
 					<li><a href="https://pages.nist.gov/ACVP/draft-celi-acvp-sha3.txt">SHAKE-256</a> - <a href="https://pages.nist.gov/ACVP/draft-celi-acvp-sha3.html">HTML</a></li>
 					<li><a href="https://pages.nist.gov/ACVP/draft-celi-acvp-xof.txt">cSHAKE-128</a> - <a href="https://pages.nist.gov/ACVP/draft-celi-acvp-xof.html">HTML</a></li>
diff --git a/src/ascon/sections/03-supported.adoc b/src/ascon/sections/03-supported.adoc
new file mode 100644
index 000000000..a843f7232
--- /dev/null
+++ b/src/ascon/sections/03-supported.adoc
@@ -0,0 +1,10 @@
+
+[#supported]
+== Supported Ascon Algorithms
+
+The following Ascon algorithms *MAY* be advertised by the ACVP compliant cryptographic module. The list is in the form "algorithm / mode / revision".
+
+* Ascon / AEAD128 / SP800-232
+* Ascon / Hash256 / SP800-232
+* Ascon / XOF128 / SP800-232
+* Ascon / CXOF128 / SP800-232
diff --git a/src/ascon/sections/04-testtypes.adoc b/src/ascon/sections/04-testtypes.adoc
new file mode 100644
index 000000000..78686bf31
--- /dev/null
+++ b/src/ascon/sections/04-testtypes.adoc
@@ -0,0 +1,47 @@
+
+[#testtypes]
+== Test Types and Test Coverage
+
+[#ttypes]
+=== Test Types
+
+The ACVP server performs a set of tests on the specified Ascon algorithm in order to assess the correctness and robustness of the implementation. A typical ACVP validation session *SHALL* require multiple tests to be performed for every supported permutation of Ascon capabilities. This section describes the design of the tests used to validate implementations of the Ascon algorithms. The number of tests *MAY* vary but the minimum number required by each test type *SHALL* be included by the server. The test type describes the format of the test rather than the intention of the test. Multiple tests of the same test type *MAY* cover different assurances regarding the implementation. 
+
+==== Ascon AEAD Test Types
+
+* Ascon / AEAD128 / * "AFT" - Algorithm Functional Test. 
+
+For each test case provided the IUT *SHALL* perform either encryption or decryption. In the case of encryption, the IUT *SHALL* use the provided key, nonce, associated data, payload, payload bit length, associated data bit length, tag length, and second key values. The IUT-computed ciphertext and tag are communicated to the ACVP server and compared to the expected ciphertext and tag. This tests the implementation of Algorithm 3 `Ascon-AEAD128.enc()` from <<SP800-232>> Section 4.1.1. The server *SHALL* provide at least 60 tests for each combination of capabilities. In the case of decryption, the IUT *SHALL* use the provided key, nonce, associated data, ciphertext, tag, ciphertext bit length, associated data bit length, tag length, and second key values. The IUT-computed payload is communicated to the ACVP server and compared to the expected payload. This tests the implementation of Algorithm 4 `Ascon-AEAD128.dec()` from <<SP800-232>> Section 4.1.2. The server *SHALL* provide at least 60 tests for each combination of capabilities.
+
+==== Ascon Hash Test Types
+
+* Ascon / Hash256 / * "AFT" - Algorithm Functional Test. 
+
+For each test case provided the IUT *SHALL* generate a valid digest given the ACVP-provided message and message bit length. The digest is then compared to the known result by the ACVP server. This tests the implementation of Algorithm 5 `Ascon-Hash256()` from <<SP800-232>> Section 5.1. The server *SHALL* provide at least 60 tests generated for each combination of capabilities.
+
+==== Ascon XOF Test Types
+
+* Ascon / XOF128 / * "AFT" - Algorithm Functional Test. 
+
+For each test case provided the IUT *SHALL* generate a valid digest given the ACVP-provided message, message bit length, and digest bit length. The digest is then compared to the known result by the ACVP server. This tests the implementation of Algorithm 6 `Ascon-XOF128()` from <<SP800-232>> Section 5.2. The server *SHALL* provide at least 60 tests generated for each combination of capabilities.
+
+==== Ascon CXOF Test Types
+
+* Ascon / CXOF128 / * "AFT" - Algorithm Functional Test. 
+
+For each test case provided the IUT *SHALL* generate a valid digest given the ACVP-provided message, message bit length, customization string, customization string bit length, and digest bit length. The digest is then compared to the known result by the ACVP server. This tests the implementation of Algorithm 7 `Ascon-CXOF128()` from <<SP800-232>> Section 5.3. The server *SHALL* provide at least 60 tests generated for each combination of capabilities.
+
+[[test_coverage]]
+=== Test Coverage
+
+The tests described in this document have the intention of ensuring an implementation is conformant to <<SP800-232>>.
+
+[[requirements_covered]]
+==== Requirements Covered
+
+* The tests will support ensuring the conformity and correctness of an implementation of the algorithms supported. 
+
+[[requirements_not_covered]]
+==== Requirements Not Covered
+
+* SP800-232 Section 4.3. Additional Requirements. Requirements outlined in this section are not testable by an ACVP server.
diff --git a/src/ascon/sections/05-ascon-aead128-capabilities.adoc b/src/ascon/sections/05-ascon-aead128-capabilities.adoc
new file mode 100644
index 000000000..356901f6f
--- /dev/null
+++ b/src/ascon/sections/05-ascon-aead128-capabilities.adoc
@@ -0,0 +1,63 @@
+
+[[Ascon_AEAD128_registration]]
+=== Ascon AEAD128 Registration Properties
+
+Each Ascon AEAD128 algorithm capability advertised is a self-contained JSON object using the following values.
+
+[[Ascon_AEAD128_caps_table]]
+.Ascon AEAD128 Algorithm Capabilities JSON Values
+|===
+| JSON Value | Description | JSON Type | Valid Values
+
+| algorithm | The algorithm to be validated | string | "Ascon"
+| mode | The Ascon mode to be validated | string | "AEAD128"
+| revision | The algorithm testing revision to use | string | "SP800-232"
+| directions | The directions for AEAD to be tested | array of strings | "encrypt", "decrypt"
+| payloadLength | The supported plaintext lengths in bits | Domain | {"Min": 0, "Max": 65536, "Inc": any}
+| adLength | The supported associated data lengths in bits | Domain | {"Min": 0, "Max": 65536, "Inc": any}
+| tagLength | The supported tag lengths in bits | Domain | {"Min": 64, "Max": 128, "Inc": any}
+| supportsNonceMasking | The support for nonce masking (second key) mode | array of booleans | true, false
+|===
+
+[[Ascon_AEAD128_capabilities]]
+==== Ascon AEAD128 Mode Capabilities Example
+
+Below is an example of the registration for Ascon / AEAD128 / SP800-232
+
+[source, json]
+----
+{
+  "algorithm": "Ascon",
+  "mode": "AEAD128",
+  "revision": "SP800-232",
+  "directions": [
+    "encrypt",
+    "decrypt"
+  ],
+  "payloadLength": [
+    {
+      "min": 0,
+      "max": 65536,
+      "increment": 1
+    }
+  ],
+  "adLength": [
+    {
+      "min": 0,
+      "max": 65536,
+      "increment": 1
+    }
+  ],
+  "tagLength": [
+    {
+      "min": 64,
+      "max": 128,
+      "increment": 1
+    }
+  ],
+  "supportsNonceMasking": [
+    true,
+    false
+  ]
+}
+----
diff --git a/src/ascon/sections/05-ascon-cxof128-capabilities.adoc b/src/ascon/sections/05-ascon-cxof128-capabilities.adoc
new file mode 100644
index 000000000..93ecd2cde
--- /dev/null
+++ b/src/ascon/sections/05-ascon-cxof128-capabilities.adoc
@@ -0,0 +1,53 @@
+
+[[Ascon_CXOF128_registration]]
+=== Ascon CXOF128 Registration Properties
+
+Each Ascon CXOF128 algorithm capability advertised is a self-contained JSON object using the following values.
+
+[[Ascon_CXOF128_caps_table]]
+.Ascon CXOF128 Algorithm Capabilities JSON Values
+|===
+| JSON Value | Description | JSON Type | Valid Values
+
+| algorithm | The algorithm to be validated | string | "Ascon"
+| mode | The Ascon mode to be validated | string | "CXOF128"
+| revision | The algorithm testing revision to use | string | "SP800-232"
+| messageLength | The supported message lengths in bits | Domain | {"Min": 0, "Max": 65536, "Inc": any}
+| digestLength | The supported digest lengths in bits | Domain | {"Min": 1, "Max": 65536, "Inc": any}
+| customizationStringLengthLength | The supported customization string lengths in bits | Domain | {"Min": 0, "Max": 2048, "Inc": any}
+|===
+
+[[Ascon_CXOF128_capabilities]]
+==== Ascon CXOF128 Mode Capabilities Example
+
+Below is an example of the registration for Ascon / CXOF128 / SP800-232
+
+[source, json]
+----
+{
+  "algorithm": "Ascon",
+  "mode": "CXOF128",
+  "revision": "SP800-232",
+  "messageLength": [
+    {
+      "min": 0,
+      "max": 65536,
+      "increment": 1
+    }
+  ],
+  "digestLength": [
+    {
+      "min": 1,
+      "max": 65536,
+      "increment": 1
+    }
+  ],
+  "customizationStringLength": [
+    {
+      "min": 0,
+      "max": 2048,
+      "increment": 1
+    }
+  ]
+}
+----
diff --git a/src/ascon/sections/05-ascon-hash256-capabilities.adoc b/src/ascon/sections/05-ascon-hash256-capabilities.adoc
new file mode 100644
index 000000000..e8fee048e
--- /dev/null
+++ b/src/ascon/sections/05-ascon-hash256-capabilities.adoc
@@ -0,0 +1,37 @@
+
+[[Ascon_Hash256_registration]]
+=== Ascon Hash256 Registration Properties
+
+Each Ascon Hash256 algorithm capability advertised is a self-contained JSON object using the following values.
+
+[[Ascon_Hash256_caps_table]]
+.Ascon Hash256 Algorithm Capabilities JSON Values
+|===
+| JSON Value | Description | JSON Type | Valid Values
+
+| algorithm | The algorithm to be validated | string | "Ascon"
+| mode | The Ascon mode to be validated | string | "Hash256"
+| revision | The algorithm testing revision to use | string | "SP800-232"
+| messageLength | The supported message lengths in bits | Domain | {"Min": 0, "Max": 65536, "Inc": any}
+|===
+
+[[Ascon_Hash256_capabilities]]
+==== Ascon Hash256 Mode Capabilities Example
+
+Below is an example of the registration for Ascon / Hash256 / SP800-232
+
+[source, json]
+----
+{
+  "algorithm": "Ascon",
+  "mode": "Hash256",
+  "revision": "SP800-232",
+  "messageLength": [
+    {
+      "min": 0,
+      "max": 65536,
+      "increment": 1
+    }
+  ]
+}
+----
diff --git a/src/ascon/sections/05-ascon-xof128-capabilities.adoc b/src/ascon/sections/05-ascon-xof128-capabilities.adoc
new file mode 100644
index 000000000..df67346df
--- /dev/null
+++ b/src/ascon/sections/05-ascon-xof128-capabilities.adoc
@@ -0,0 +1,45 @@
+
+[[Ascon_XOF128_registration]]
+=== Ascon XOF128 Registration Properties
+
+Each Ascon XOF128 algorithm capability advertised is a self-contained JSON object using the following values.
+
+[[Ascon_XOF128_caps_table]]
+.Ascon XOF128 Algorithm Capabilities JSON Values
+|===
+| JSON Value | Description | JSON Type | Valid Values
+
+| algorithm | The algorithm to be validated | string | "Ascon"
+| mode | The Ascon mode to be validated | string | "XOF128"
+| revision | The algorithm testing revision to use | string | "SP800-232"
+| messageLength | The supported message lengths in bits | Domain | {"Min": 0, "Max": 65536, "Inc": any}
+| digestLength | The supported digest lengths in bits | Domain | {"Min": 1, "Max": 65536, "Inc": any}
+|===
+
+[[Ascon_XOF128_capabilities]]
+==== Ascon XOF128 Mode Capabilities Example
+
+Below is an example of the registration for Ascon / XOF128 / SP800-232
+
+[source, json]
+----
+{
+  "algorithm": "Ascon",
+  "mode": "XOF128",
+  "revision": "SP800-232",
+  "messageLength": [
+    {
+      "min": 0,
+      "max": 65536,
+      "increment": 1
+    }
+  ],
+  "digestLength": [
+    {
+      "min": 1,
+      "max": 65536,
+      "increment": 1
+    }
+  ]
+}
+----
diff --git a/src/ascon/sections/05-capabilities.adoc b/src/ascon/sections/05-capabilities.adoc
new file mode 100644
index 000000000..276469fb5
--- /dev/null
+++ b/src/ascon/sections/05-capabilities.adoc
@@ -0,0 +1,6 @@
+
+[[prereq_algs]]
+=== Required Prerequisite Algorithms for Ascon Validations
+
+Ascon implementations do not rely on other cryptographic primitives. 
+
diff --git a/src/ascon/sections/06-ascon-aead128-test-vectors.adoc b/src/ascon/sections/06-ascon-aead128-test-vectors.adoc
new file mode 100644
index 000000000..a3e3d0c26
--- /dev/null
+++ b/src/ascon/sections/06-ascon-aead128-test-vectors.adoc
@@ -0,0 +1,139 @@
+[[Ascon_AEAD128_test_vectors]]
+=== Ascon AEAD128 Test Vectors
+
+[[Ascon_AEAD128_tgjs]]
+==== Ascon AEAD128 Test Groups JSON Schema
+
+The testGroups element at the top level in the test vector JSON object is an array of test groups. Test vectors are grouped into similar test cases to reduce the amount of data transmitted in the vector set. For instance, all test vectors that use the same key size would be grouped together. The Test Group JSON object contains meta data that applies to all test vectors within the group. The following table describes the {algo-short-name} JSON elements of the Test Group JSON object.
+
+The test group for Ascon / AEAD128 / SP800-232 is as follows:
+
+[[Ascon_AEAD128_vs_tg_table]]
+.Ascon AEAD128 Test Group JSON Object
+|===
+| JSON Value | Description | JSON type
+
+| tgId | Numeric identifier for the test group, unique across the entire vector set | integer
+| testType | The test operation performed | string
+| tests | Array of individual test vector JSON objects, which are defined in <<Ascon_AEAD128_tvjs>> | array
+| direction | The direction the block cipher operates in | string
+| supportsNonceMasking | Boolean to determine if test group uses a second key for nonce masking | boolean
+|===
+
+[[Ascon_AEAD128_tvjs]]
+==== Ascon AEAD128 Test Case JSON Schema
+
+Each test group contains an array of one or more test cases. Each test case is a JSON object that represents a single test vector to be processed by the ACVP client. The following table describes the JSON elements for each Ascon / AEAD128 / FIPS205 test vector.
+
+[[Ascon_AEAD128_vs_tc_table]]
+.Ascon AEAD128 Test Case JSON Object
+|===
+| JSON Value | Description | JSON type
+
+| tcId | Numeric identifier for the test case, unique across the entire vector set | integer
+| key | Key value | hex
+| nonce | Nonce value | hex
+| ad | Associated data value | hex
+| pt | Payload in the encrypt case | hex
+| ct | Payload in the decrypt case | hex
+| payloadBitLength | Payload bit length | integer
+| adBitLength | Assoicated data bit length | integer
+| tagLength | Tag bit length | integer
+| secondKey | Second key value | hex
+|===
+
+The following is an example JSON object sent from the server to the client for Ascon / AEAD128 / FIPS205. 
+
+[source, json]
+----
+[
+    {
+        "acvVersion": <acvp-version>
+    },
+    {
+        "vsId": 42,
+        "algorithm": "Ascon",
+        "mode": "AEAD128",
+        "revision": "SP800-232",
+        "isSample": true,
+        "testGroups": [
+            {
+                "tgId": 1,
+                "testType": "AFT",
+                "tests": [
+                    {
+                        "tcId": 60,
+                        "key": "FD49918ED109AF4237047633E899B574",
+                        "nonce": "B6B6598FFA6317E896945E69FBC05591",
+                        "ad": "47E62206F92A652B",
+                        "pt": "F2C255",
+                        "payloadBitLength": 23,
+                        "adBitLength": 64,
+                        "tagLength": 64,
+                        "secondKey": "016FBC19B1FAF20FBC6C051B6B8543A7"
+                    }
+                ]
+                "direction": "encrypt",
+                "supportsNonceMasking": true
+            },
+            {
+                "tgId": 2,
+                "testType": "AFT",
+                "tests": [
+                    {
+                        "tcId": 107,
+                        "key": "66D31B340B8B4D8C82CDF4C1B76DC4A6",
+                        "nonce": "51224C04CC0D79B992826F3478DF6C95",
+                        "ad": "63BEEE9E4B971FEFABEAEBBADBF512194EB04E0E",
+                        "pt": "9596D2",
+                        "payloadBitLength": 24,
+                        "adBitLength": 160,
+                        "tagLength": 64
+                    }
+                ]
+                "direction": "encrypt",
+                "supportsNonceMasking": false
+            },
+            {
+                "tgId": 3,
+                "testType": "AFT",
+                "tests": [
+                    {
+                        "tcId": 125,
+                        "key": "F381BF2A2CCC344C07E30DB6D93C43A5",
+                        "nonce": "538AB0C0748FA21B4841329C640E5B8C",
+                        "ad": "6421B70D86E8CA3D80C0708F72C840717BAB0D4900",
+                        "tag": "EB8DDC8F7B32334D",
+                        "payloadBitLength": 63,
+                        "adBitLength": 161,
+                        "tagLength": 64,
+                        "secondKey": "89ADE7BE07136C740708C8F10CF58970",
+                        "ct": "EA2649C1EDEA2F4A"
+                    }
+                ]
+                "direction": "decrypt",
+                "supportsNonceMasking": true
+            },
+            {
+                "tgId": 4,
+                "testType": "AFT",
+                "tests": [
+                    {
+                        "tcId": 184,
+                        "key": "E37C0BB570A0F742C72E0F26C2A72BDD",
+                        "nonce": "49F8A80BCCCA888D053F41EE35842A78",
+                        "ad": "55D138A7B7A84454D7217121446BA4AF1050B988",
+                        "tag": "6497C727EC4CBF8F",
+                        "payloadBitLength": 383,
+                        "adBitLength": 160,
+                        "tagLength": 64,
+                        "ct": "C20807710C919109AC1618D872ABCD1D8D2B3372136BB90A309F55804C0856A6FB213C2FB3CB7B58D5DEA5FDFC208673"
+                    }
+                ]
+                "direction": "decrypt",
+                "supportsNonceMasking": false
+            },
+        ]
+    }
+]
+----
diff --git a/src/ascon/sections/06-ascon-cxof128-test-vectors.adoc b/src/ascon/sections/06-ascon-cxof128-test-vectors.adoc
new file mode 100644
index 000000000..8a5a97e89
--- /dev/null
+++ b/src/ascon/sections/06-ascon-cxof128-test-vectors.adoc
@@ -0,0 +1,71 @@
+[[Ascon_CXOF128_test_vectors]]
+=== Ascon CXOF128 Test Vectors
+
+[[Ascon_CXOF128_tgjs]]
+==== Ascon CXOF128 Test Groups JSON Schema
+
+The testGroups element at the top level in the test vector JSON object is an array of test groups. Test vectors are grouped into similar test cases to reduce the amount of data transmitted in the vector set. For instance, all test vectors that use the same key size would be grouped together. The Test Group JSON object contains meta data that applies to all test vectors within the group. The following table describes the {algo-short-name} JSON elements of the Test Group JSON object.
+
+The test group for Ascon / CXOF128 / SP800-232 is as follows:
+
+[[Ascon_CXOF128_vs_tg_table]]
+.Ascon CXOF128 Test Group JSON Object
+|===
+| JSON Value | Description | JSON type
+
+| tgId | Numeric identifier for the test group, unique across the entire vector set | integer
+| testType | The test operation performed | string
+| tests | Array of individual test vector JSON objects, which are defined in <<Ascon_CXOF128_tvjs>> | array
+|===
+
+[[Ascon_CXOF128_tvjs]]
+==== Ascon CXOF128 Test Case JSON Schema
+
+Each test group contains an array of one or more test cases. Each test case is a JSON object that represents a single test vector to be processed by the ACVP client. The following table describes the JSON elements for each Ascon / CXOF128 / FIPS205 test vector.
+
+[[Ascon_CXOF128_vs_tc_table]]
+.Ascon CXOF128 Test Case JSON Object
+|===
+| JSON Value | Description | JSON type
+
+| tcId | Numeric identifier for the test case, unique across the entire vector set | integer
+| message | Message value | hex
+| messageBitLength | Length of message in bits | integer
+| digestBitLength | Length of the digest in bits | integer
+| customizationString | Customization string value | hex
+| customizationStringBitLength | Length of the customization string in bits | integer
+|===
+
+The following is an example JSON object sent from the server to the client for Ascon / CXOF128 / FIPS205. 
+
+[source, json]
+----
+[
+    {
+        "acvVersion": <acvp-version>
+    },
+    {
+        "vsId": 42,
+        "algorithm": "Ascon",
+        "mode": "CXOF128",
+        "revision": "SP800-232",
+        "isSample": true,
+        "testGroups": [
+            {
+                "tgId": 1,
+                "testType": "AFT",
+                "tests": [
+                    {
+                    "tcId": 3,
+                    "message": "380F97464AB9E035024C9B5F8D1AF3D0763BE9A7FB795B0FAE6EF5455249E93A4807D046F9BA97916E7EF9639483F4308BC8CAD3E385AEBEB38797DBC49BE2B9636017854AACD7BCA458397D80F87A2B7AC4B98A7E1657C25811937222BBCDD39B3F00346C6EE6DFF10E2F8A4C313E3A",
+                    "messageBitLength": 895,
+                    "digestBitLength": 26524,
+                    "customizationString": "0C6C61FFE1573A4D09542C",
+                    "customizationStringBitLength": 88
+                    }
+                ]
+            }
+        ]
+    }
+]
+----
diff --git a/src/ascon/sections/06-ascon-hash256-test-vectors.adoc b/src/ascon/sections/06-ascon-hash256-test-vectors.adoc
new file mode 100644
index 000000000..66f121ff1
--- /dev/null
+++ b/src/ascon/sections/06-ascon-hash256-test-vectors.adoc
@@ -0,0 +1,65 @@
+[[Ascon_Hash256_test_vectors]]
+=== Ascon Hash256 Test Vectors
+
+[[Ascon_Hash256_tgjs]]
+==== Ascon Hash256 Test Groups JSON Schema
+
+The testGroups element at the top level in the test vector JSON object is an array of test groups. Test vectors are grouped into similar test cases to reduce the amount of data transmitted in the vector set. For instance, all test vectors that use the same key size would be grouped together. The Test Group JSON object contains meta data that applies to all test vectors within the group. The following table describes the {algo-short-name} JSON elements of the Test Group JSON object.
+
+The test group for Ascon / Hash256 / SP800-232 is as follows:
+
+[[Ascon_Hash256_vs_tg_table]]
+.Ascon Hash256 Test Group JSON Object
+|===
+| JSON Value | Description | JSON type
+
+| tgId | Numeric identifier for the test group, unique across the entire vector set | integer
+| testType | The test operation performed | string
+| tests | Array of individual test vector JSON objects, which are defined in <<Ascon_Hash256_tvjs>> | array
+|===
+
+[[Ascon_Hash256_tvjs]]
+==== Ascon Hash256 Test Case JSON Schema
+
+Each test group contains an array of one or more test cases. Each test case is a JSON object that represents a single test vector to be processed by the ACVP client. The following table describes the JSON elements for each Ascon / Hash256 / FIPS205 test vector.
+
+[[Ascon_Hash256_vs_tc_table]]
+.Ascon Hash256 Test Case JSON Object
+|===
+| JSON Value | Description | JSON type
+
+| tcId | Numeric identifier for the test case, unique across the entire vector set | integer
+| message | Message value | hex
+| messageBitLength | Length of message in bits | integer
+|===
+
+The following is an example JSON object sent from the server to the client for Ascon / Hash256 / FIPS205. 
+
+[source, json]
+----
+[
+    {
+        "acvVersion": <acvp-version>
+    },
+    {
+        "vsId": 42,
+        "algorithm": "Ascon",
+        "mode": "Hash256",
+        "revision": "SP800-232",
+        "isSample": true,
+        "testGroups": [
+            {
+                "tgId": 1,
+                "testType": "AFT",
+                "tests": [
+                    {
+                    "tcId": 3,
+                    "message": "937E8B3C4BC1D5E04E7F3157D9C3936CBCBD952D",
+                    "messageBitLength": 159
+                    }
+                ]
+            }
+        ]
+    }
+]
+----
diff --git a/src/ascon/sections/06-ascon-xof128-test-vectors.adoc b/src/ascon/sections/06-ascon-xof128-test-vectors.adoc
new file mode 100644
index 000000000..97f9d929f
--- /dev/null
+++ b/src/ascon/sections/06-ascon-xof128-test-vectors.adoc
@@ -0,0 +1,67 @@
+[[Ascon_XOF128_test_vectors]]
+=== Ascon XOF128 Test Vectors
+
+[[Ascon_XOF128_tgjs]]
+==== Ascon XOF128 Test Groups JSON Schema
+
+The testGroups element at the top level in the test vector JSON object is an array of test groups. Test vectors are grouped into similar test cases to reduce the amount of data transmitted in the vector set. For instance, all test vectors that use the same key size would be grouped together. The Test Group JSON object contains meta data that applies to all test vectors within the group. The following table describes the {algo-short-name} JSON elements of the Test Group JSON object.
+
+The test group for Ascon / XOF128 / SP800-232 is as follows:
+
+[[Ascon_XOF128_vs_tg_table]]
+.Ascon XOF128 Test Group JSON Object
+|===
+| JSON Value | Description | JSON type
+
+| tgId | Numeric identifier for the test group, unique across the entire vector set | integer
+| testType | The test operation performed | string
+| tests | Array of individual test vector JSON objects, which are defined in <<Ascon_XOF128_tvjs>> | array
+|===
+
+[[Ascon_XOF128_tvjs]]
+==== Ascon XOF128 Test Case JSON Schema
+
+Each test group contains an array of one or more test cases. Each test case is a JSON object that represents a single test vector to be processed by the ACVP client. The following table describes the JSON elements for each Ascon / XOF128 / FIPS205 test vector.
+
+[[Ascon_XOF128_vs_tc_table]]
+.Ascon XOF128 Test Case JSON Object
+|===
+| JSON Value | Description | JSON type
+
+| tcId | Numeric identifier for the test case, unique across the entire vector set | integer
+| message | Message value | hex
+| messageBitLength | Length of message in bits | integer
+| digestBitLength | Length of the digest in bits | integer
+|===
+
+The following is an example JSON object sent from the server to the client for Ascon / XOF128 / FIPS205. 
+
+[source, json]
+----
+[
+    {
+        "acvVersion": <acvp-version>
+    },
+    {
+        "vsId": 42,
+        "algorithm": "Ascon",
+        "mode": "XOF128",
+        "revision": "SP800-232",
+        "isSample": true,
+        "testGroups": [
+            {
+                "tgId": 1,
+                "testType": "AFT",
+                "tests": [
+                    {
+                    "tcId": 3,
+                    "message": "F00C735A4CFAFE35",
+                    "messageBitLength": 63,
+                    "digestBitLength": 949
+                    }
+                ]
+            }
+        ]
+    }
+]
+----
diff --git a/src/ascon/sections/06-test-vectors.adoc b/src/ascon/sections/06-test-vectors.adoc
new file mode 100644
index 000000000..00c0e09c4
--- /dev/null
+++ b/src/ascon/sections/06-test-vectors.adoc
@@ -0,0 +1,35 @@
+== Test Vectors
+
+The ACVP server provides test vectors to the ACVP client, which are then processed and returned to the ACVP server for validation. A typical ACVP validation test session would require multiple test vector sets to be downloaded and processed by the ACVP client. Each test vector set represents an individual cryptographic algorithm defined during the capability exchange. This section describes the JSON schema for a test vector set used with {spec-algorithm} algorithms.
+
+The test vector set JSON schema is a multi-level hierarchy that contains meta data for the entire vector set as well as individual test vectors to be processed by the ACVP client. The following table describes the JSON elements at the top level of the hierarchy.
+
+.Top Level Test Vector JSON Elements
+|===
+| JSON Values | Description | JSON Type
+
+| acvVersion | Protocol version identifier | string
+| vsId | Unique numeric vector set identifier | integer
+| algorithm | Algorithm defined in the capability exchange | string
+| mode | Mode defined in the capability exchange | string
+| revision | Protocol test revision selected | string
+| testGroups | Array of test group JSON objects. Depending on the algorithm, see <<Ascon_AEAD128_tgjs>>, <<Ascon_Hash256_tgjs>>, <<Ascon_XOF128_tgjs>> or <<Ascon_CXOF128_tgjs>> | array
+|===
+
+An example of this would look like this
+
+[source,json]
+----
+[
+  {
+    "acvVersion": <version>
+  },
+  {
+    "vsId": 1,
+    "algorithm": "Alg1",
+    "mode": "Mode1",
+    "revision": "Revision1.0",
+    "testGroups": [ ... ]
+  }
+]
+----
diff --git a/src/ascon/sections/07-ascon-aead128-responses.adoc b/src/ascon/sections/07-ascon-aead128-responses.adoc
new file mode 100644
index 000000000..78a38409b
--- /dev/null
+++ b/src/ascon/sections/07-ascon-aead128-responses.adoc
@@ -0,0 +1,73 @@
+[[Ascon_AEAD128_vector_responses]]
+=== Ascon AEAD128 Test Vector Responses
+
+Each test group contains an array of one or more test cases. Each test case is a JSON object that represents the results of an ACVP client processing a single test vector. The following table describes the JSON elements for each Ascon / AEAD128 / SP800-232 test vector.
+
+[[Ascon_AEAD128_vs_tr_table]]
+.Ascon AEAD128 Test Case Response JSON Object
+|===
+| JSON Value | Description | JSON type
+
+| tcId | The test case identifier | integer
+| tag | The computed tag in an encrypt directtion | hex
+| ct | The computed ciphertext in an encrypt case| hex
+| pt | The computed plaintext in a decrypt case | hex
+|===
+
+The following is an example JSON test vector response object for Ascon / AEAD128 / SP800-232.
+
+[source, json]
+----
+[
+    {
+        "acvVersion": <acvp-version>
+    },
+    {
+        "vsId": 42,
+        "algorithm": "Ascon",
+        "mode": "AEAD128",
+        "revision": "SP800-232",
+        "isSample": true,
+        "testGroups": [
+            {
+                "tgId": 1,
+                "tests": [
+                    {
+                        "tcId": 1,
+                        "tag": "E2D95B2EF1A1E75AF11EF398CD5BE0E8",
+                        "ct": "BF6CEC4E476E0CBC47287ED9B07847785D6096332CE2D249D5A0455E3BEB24C92183609FD1A0AB77F6C2730E0A85ADEC"
+                    },
+                ]
+            },
+            {
+                "tgId": 2,
+                "tests": [
+                    {
+                        "tcId": 61,
+                        "tag": "3616EB39EE11827740EBB60E4A936CC8",
+                        "ct": "195CCB04AC6232B400"
+                    },
+                ]
+            },
+            {
+                "tgId": 3,
+                "tests": [
+                    {
+                        "tcId": 124,
+                        "pt": "66348919F866C983AAE911B3F556524216672E6A"
+                    },
+                ]
+            },
+            {
+                "tgId": 4,
+                "tests": [
+                    {
+                        "tcId": 191,
+                        "pt": "9ED0960B1BFDDA16"
+                    },
+                ]
+            },
+        ]
+    }
+]
+----
diff --git a/src/ascon/sections/07-ascon-cxof128-responses.adoc b/src/ascon/sections/07-ascon-cxof128-responses.adoc
new file mode 100644
index 000000000..39516854b
--- /dev/null
+++ b/src/ascon/sections/07-ascon-cxof128-responses.adoc
@@ -0,0 +1,42 @@
+[[Ascon_CXOF128_vector_responses]]
+=== Ascon CXOF128 Test Vector Responses
+
+Each test group contains an array of one or more test cases. Each test case is a JSON object that represents the results of an ACVP client processing a single test vector. The following table describes the JSON elements for each Ascon / CXOF128 / SP800-232 test vector.
+
+[[Ascon_CXOF128_vs_tr_table]]
+.Ascon CXOF128 Test Case Response JSON Object
+|===
+| JSON Value | Description | JSON type
+
+| tcId | The test case identifier | integer
+| digest | The computed digest | hex
+|===
+
+The following is an example JSON test vector response object for Ascon / CXOF128 / SP800-232.
+
+[source, json]
+----
+[
+    {
+        "acvVersion": <acvp-version>
+    },
+    {
+        "vsId": 0,
+        "algorithm": "Ascon",
+        "mode": "CXOF128",
+        "revision": "SP800-232",
+        "isSample": true,
+        "testGroups": [
+            {
+                "tgId": 1,
+                "tests": [
+                    {
+                        "tcId": 7,
+                        "digest": "EE1DAAB6F78C810129D0D6FB93DA00FD93E2A8AB1E57C7A92D48EB03A1EEF7864EB726E06973E01C2199F4948963C5D960DAD7472B94F8D552BA22D52E1DEDF3F658FE2F60B3AF36B897AFFA6EA18B8CC3FF779969F55AB5E2A7AC6F242AAD445CCF760A97BE93665DE5DF7B2BCA8C88ADEC4C3D44C0C48456FD9AD2BE20C4A61F25BDB66E4B36AB559A98C1B08A7FBC2F7CF4B9B349CC593A9F05F2D3913B7DDE78768304233A1CBDD7705AC3BA3C6C182CA9A2D90CA3896DE793ABE3884B2DB663EBD1E60739FF13A48504A2979997FE82FA18237C2BD369A10C569D5B6EF94902291579D85BE7A8D046F04DABF22360C37FBC63A589FBC88D476093A57257509E71BE05907892105EF5D603"
+                    }
+                ]
+            }
+        ]
+    }
+]
+----
diff --git a/src/ascon/sections/07-ascon-hash256-responses.adoc b/src/ascon/sections/07-ascon-hash256-responses.adoc
new file mode 100644
index 000000000..2ac514366
--- /dev/null
+++ b/src/ascon/sections/07-ascon-hash256-responses.adoc
@@ -0,0 +1,42 @@
+[[Ascon_Hash256_vector_responses]]
+=== Ascon Hash256 Test Vector Responses
+
+Each test group contains an array of one or more test cases. Each test case is a JSON object that represents the results of an ACVP client processing a single test vector. The following table describes the JSON elements for each Ascon / Hash256 / SP800-232 test vector.
+
+[[Ascon_Hash256_vs_tr_table]]
+.Ascon Hash256 Test Case Response JSON Object
+|===
+| JSON Value | Description | JSON type
+
+| tcId | The test case identifier | integer
+| digest | The computed digest | hex
+|===
+
+The following is an example JSON test vector response object for Ascon / Hash256 / SP800-232.
+
+[source, json]
+----
+[
+    {
+        "acvVersion": <acvp-version>
+    },
+    {
+        "vsId": 0,
+        "algorithm": "Ascon",
+        "mode": "Hash256",
+        "revision": "SP800-232",
+        "isSample": true,
+        "testGroups": [
+            {
+                "tgId": 1,
+                "tests": [
+                    {
+                        "tcId": 3,
+                        "digest": "84ADA53484D7D11D7B9518754542E6FC6646D2BEB8346B260EF44880A6974593"
+                    }
+                ]
+            }
+        ]
+    }
+]
+----
diff --git a/src/ascon/sections/07-ascon-xof128-responses.adoc b/src/ascon/sections/07-ascon-xof128-responses.adoc
new file mode 100644
index 000000000..8ff2b1c2f
--- /dev/null
+++ b/src/ascon/sections/07-ascon-xof128-responses.adoc
@@ -0,0 +1,42 @@
+[[Ascon_XOF128_vector_responses]]
+=== Ascon XOF128 Test Vector Responses
+
+Each test group contains an array of one or more test cases. Each test case is a JSON object that represents the results of an ACVP client processing a single test vector. The following table describes the JSON elements for each Ascon / XOF128 / SP800-232 test vector.
+
+[[Ascon_XOF128_vs_tr_table]]
+.Ascon XOF128 Test Case Response JSON Object
+|===
+| JSON Value | Description | JSON type
+
+| tcId | The test case identifier | integer
+| digest | The computed digest | hex
+|===
+
+The following is an example JSON test vector response object for Ascon / XOF128 / SP800-232.
+
+[source, json]
+----
+[
+    {
+        "acvVersion": <acvp-version>
+    },
+    {
+        "vsId": 0,
+        "algorithm": "Ascon",
+        "mode": "XOF128",
+        "revision": "SP800-232",
+        "isSample": true,
+        "testGroups": [
+            {
+                "tgId": 1,
+                "tests": [
+                    {
+                        "tcId": 1,
+                        "digest": "1C6B4531D31C9ECF60C7A0994A2EAF884F39FB052C8B0820ED8336945874DCB29EE85E5ADBA645724056715DB76B8B08E45546DACEE5CCB0CCA3C377B114C0C23C5207BBFEC6A7DC4F705550C795F381086CCD1DC2AC1B9FDF24AEA246BC6BEF6BD0B2490EC13528843C5BAE22AB556D881FEFFB20B317"
+                    }
+                ]
+            }
+        ]
+    }
+]
+----
diff --git a/src/ascon/sections/07-responses.adoc b/src/ascon/sections/07-responses.adoc
new file mode 100644
index 000000000..0f0fb7a05
--- /dev/null
+++ b/src/ascon/sections/07-responses.adoc
@@ -0,0 +1,46 @@
+
+[#responses]
+== Test Vector Responses
+
+After the ACVP client downloads and processes a vector set, it must send the response vectors back to the ACVP server. The following table describes the JSON object that represents a vector set response.
+
+[[response_table]]
+.Response JSON Object
+|===
+| JSON Property | Description | JSON Type
+
+| acvVersion | The ACVP version used | string
+| vsId | The vector set identifier | integer
+| testGroups | The test group objects in the response, see <<response_group_table>> | array
+|===
+
+An example of this is the following
+
+[source, json]
+----
+{
+    "acvVersion": "version",
+    "vsId": 1,
+    "testGroups": [ ... ]
+}
+----
+
+The 'testGroups' section is used to organize the ACVP client response in a similar manner to how it distributes vectors.
+
+[[response_group_table]]
+.Response Group Objects
+|===
+| JSON Property | Description | JSON Type
+
+| tgId | The test group identifier | integer
+| tests | The test case objects in the response. Depending on the algorithm, see <<Ascon_AEAD128_vs_tr_table>>, <<Ascon_Hash256_vs_tr_table>>, <<Ascon_XOF128_vs_tr_table>>, or <<Ascon_CXOF128_vs_tr_table>> | array
+|===
+
+An example of this is the following
+
+----
+{
+    "tgId": 1,
+    "tests": [ ... ]
+}
+----
diff --git a/src/ascon/sections/98-references.adoc b/src/ascon/sections/98-references.adoc
new file mode 100644
index 000000000..571465602
--- /dev/null
+++ b/src/ascon/sections/98-references.adoc
@@ -0,0 +1,35 @@
+
+[bibliography]
+== Normative References
+
+* [[[RFC2119,RFC 2119]]]
+* [[[RFC8174,RFC 8174]]]
+
+* [[[SP800-232, SP 800-232]]]
+
+[%bibitem]
+=== Automatic Cryptographic Validation Protocol
+id:: ACVP
+docid::
+  id::: ACVP
+contributor::
+contributor.person.name.initial:: B.
+contributor.person.name.surname:: Fussell
+contributor.person.affiliation.organization.name:: Cisco
+contributor::
+contributor.person.name.initial:: A.
+contributor.person.name.surname:: Vassilev
+contributor.person.affiliation.organization.name:: National Institute of Standards and Technology
+contributor.person.affiliation.organization.abbreviation:: NIST
+contributor::
+contributor.person.name.initial:: H.
+contributor.person.name.surname:: Booth
+contributor.person.affiliation.organization.name:: National Institute of Standards and Technology
+contributor.person.affiliation.organization.abbreviation:: NIST
+contributor::
+contributor.role:: publisher
+contributor.organization.name:: National Institute of Standards and Technology
+contributor.organization.abbreviation:: NIST
+date::
+date.type:: published
+date.value:: 2019-07-01
diff --git a/src/draft-ross-acvp-ascon.adoc b/src/draft-ross-acvp-ascon.adoc
new file mode 100644
index 000000000..3e65fb896
--- /dev/null
+++ b/src/draft-ross-acvp-ascon.adoc
@@ -0,0 +1,84 @@
+= ACVP Ascon JSON Specification
+:doctype: internet-draft
+:docname: ascon
+:docnumber: draft-ross-acvp-ascon-01
+:abbrev: ACVP Ascon
+:ipr: trust200902
+:submission-type: independent
+:area: Internet
+:intended-series: informational
+:revdate: 2025-04-14
+:forename_initials: N.G.
+:lastname: Ross
+:fullname: Noah Ross
+:organization: National Institute of Standards and Technology
+:street: 100 Bureau Drive
+:city: Gaithersburg
+:code: 20899
+:country: United States of America
+:email: noah.ross@nist.gov
+:role: editor
+:docfile: draft-ross-acvp-ascon-adoc
+:mn-document-class: ietf
+:mn-output-extensions: xml,rfc,txt,html
+:area: General
+:keyword: acvp, crypto
+
+// Singular name of the algorithm
+:spec-algorithm: Ascon
+:algo-short-name: Ascon
+
+include::common/common-sections/00-abstract.adoc[]
+
+include::common/common-sections/01-intro.adoc[]
+
+include::common/common-sections/02-conventions.adoc[]
+
+include::ascon/sections/03-supported.adoc[]
+
+include::ascon/sections/04-testtypes.adoc[]
+
+include::common/common-sections/05-capabilities-description.adoc[]
+
+include::common/common-sections/051-prerequisites.adoc[]
+
+//include::ascon/sections/05-capabilities.adoc[]
+
+include::ascon/sections/05-ascon-aead128-capabilities.adoc[]
+
+include::ascon/sections/05-ascon-hash256-capabilities.adoc[]
+
+include::ascon/sections/05-ascon-xof128-capabilities.adoc[]
+
+include::ascon/sections/05-ascon-cxof128-capabilities.adoc[]
+
+//include::common/common-sections/06-test-vector-intro.adoc[]
+
+include::ascon/sections/06-test-vectors.adoc[]
+
+include::ascon/sections/06-ascon-aead128-test-vectors.adoc[]
+
+include::ascon/sections/06-ascon-hash256-test-vectors.adoc[]
+
+include::ascon/sections/06-ascon-xof128-test-vectors.adoc[]
+
+include::ascon/sections/06-ascon-cxof128-test-vectors.adoc[]
+
+include::ascon/sections/07-responses.adoc[]
+
+include::ascon/sections/07-ascon-aead128-responses.adoc[]
+
+include::ascon/sections/07-ascon-hash256-responses.adoc[]
+
+include::ascon/sections/07-ascon-xof128-responses.adoc[]
+
+include::ascon/sections/07-ascon-cxof128-responses.adoc[]
+
+include::common/common-sections/10-security.adoc[]
+
+include::common/common-sections/11-iana.adoc[]
+
+include::common/common-sections/99-acknowledgements.adoc[]
+
+// References must be given before appendixes
+include::ascon/sections/98-references.adoc[]