aboutsummaryrefslogtreecommitdiff
path: root/doc/design.md
diff options
context:
space:
mode:
authorRasmus Dahlberg <rasmus.dahlberg@kau.se>2021-04-30 14:15:50 +0200
committerRasmus Dahlberg <rasmus.dahlberg@kau.se>2021-04-30 14:15:50 +0200
commit984f73e11ea1000b3af4f36199f591450afca2af (patch)
treee05c99dfd11a3a5ae0c4dbb15998dd372f33c77a /doc/design.md
parent6cae1445318e22ce909b0211fc405dbeb6db7c44 (diff)
clarified why domain hint is not in the leaf
Diffstat (limited to 'doc/design.md')
-rw-r--r--doc/design.md4
1 files changed, 2 insertions, 2 deletions
diff --git a/doc/design.md b/doc/design.md
index cb379e5..dda9efe 100644
--- a/doc/design.md
+++ b/doc/design.md
@@ -132,8 +132,8 @@ ecosystem needs more than one log to be reliable. DNS also has built-in
caching that can be influenced by setting TTLs accordingly.
The submitter's domain hint is not part of the leaf because key management is
-more complex than that. The only service that the log provides is discovery of
-signed checksums. Key transparency projects have their own merit.
+more complex than that. A separate project should focus on transparent key
+management. The scope of our work is transparent _key-usage_.
The log will _try_ to incorporate a leaf into the Merkle tree if a logging
request is accepted. There are no _promises of public logging_ as in