From 7c0df8b9fb88901221e0f25d1ead8f8d3af2ef24 Mon Sep 17 00:00:00 2001 From: Dirk-Willem van Gulik Date: Mon, 13 Apr 2020 21:08:56 +0200 Subject: [PATCH] Update for decision/info from https://github.com/DP-3T/documents/issues/145 --- implementation-profiles/profile.md | 18 +++++++++--------- 1 file changed, 9 insertions(+), 9 deletions(-) diff --git a/implementation-profiles/profile.md b/implementation-profiles/profile.md index 5ee8e43..24583d0 100644 --- a/implementation-profiles/profile.md +++ b/implementation-profiles/profile.md @@ -45,17 +45,17 @@ Test vector: (Aligned with https://github.com/dirkx/DP-3T-Documents/tree/editable-version/impl/design-2-openssl-C) -The hash shall be a SHA256 (Note; given a reveal 60-90 bits - perhaps not so crucial). +The key shall be the hash as resulting from 2020/4/12 version of the Whitepaper: H(TRUNCATE128(H(seed))||i). No further hasing is required. + +Note - hash propably not needed - less than 20% exposed. The key shall be 32 bytes which are used as follows: - byte 0..3 up to Z bits for the LSB of the Cuckoo hash - byte 4..7 up to Z bits for the MSB of the Cuckoo hash - byte 8.. up to `verifylimit' bytes. + byte 0..3 up to ' bytes. -Where is the number of bits needed for the number of buckets (e.g Z=19 if the buckets are is 524288). - -Where verify limit is set as low as is feasible given the acceptable false positive rates. +Where and are set as low as is feasible given the acceptable false positive rates. The Cuckoo filter shall be serialised as: @@ -80,11 +80,11 @@ Followed by With the partial hash being limited to the number of bits needed for N buckets. -And with the Hash +So this, 1.0, version of the serialisation does not pack the bits; both hashes are padded to the a full byte. ### Cuckoo filter publication -The filter should be published prefixed by an RFC3161 timestamp. +The filter should be published prefixed by a RFC3161 timestamp.