@@ -348,9 +348,9 @@ To construct a signature stream, the injector server computes the following comp
*`injection-id`: The unique ID of the cache entry, described in the `X-Ouinet-Injection` response header.
*`header-signature`: A signature over the headers of the cache entry. This is computed the same way as the complete cache entry signature described in the previous section, except that the `Digest` and `X-Ouinet-Data-Size` headers are absent. This absence makes it possible for the injector server to compute the `header-signature` before fetching the complete response body.
*`block(i)`: The sequence of bytes running from byte `i * block-size` in the response body, to byte `(i + 1) * block-size` in the response body. The last block in this sequence may have fewer than `block-size` bytes.
*`hash(0)`: The cryptographic hash of `block(0)`.
*`hash(i)`, for `i > 0`: The cryptographic hash of `hash(i - 1) ++ block(i)`.
*`block-signature(i)`: The signature of the bytestring `injection-id ++ '\0' ++ (i * block-size) ++ '\0' ++ hash(i)`.
*`hash(i)`: The cryptographic hash of `block(i)`.
*`chained-hash(i)`: The cryptographic hash of `block-signature(i - 1) ++ chained-hash(i - 1) ++ hash(i)`. `block-signature(-1)` and `chained-hash(-1)` are conventionally the empty string.
*`block-signature(i)`: The signature of the bytestring `injection-id ++ '\0' ++ ascii-decimal(i * block-size) ++ '\0' ++ chained-hash(i)`.
*`data-size`: The size of the complete response body, measured as a number of bytes.
*`full-signature`: The signature of the complete cache entry, as described in the previous section.
...
...
@@ -375,13 +375,11 @@ A cache entry signed using implementations of these primitives different from th
#### Examples
**TODOv6 OBSOLETE**
An injector server using Ed25519 private key `KEY` might construct the following as-yet unsigned cache entry:
