From 50a2bc31f98dbc14fb00ca9bdbe68392ed6c8267 Mon Sep 17 00:00:00 2001 From: Philippe Pittoli Date: Wed, 30 Apr 2025 03:15:44 +0200 Subject: [PATCH] TODO: delegation. --- TODO.md | 10 ++++++---- 1 file changed, 6 insertions(+), 4 deletions(-) diff --git a/TODO.md b/TODO.md index 1525022..599d6e6 100644 --- a/TODO.md +++ b/TODO.md @@ -8,7 +8,8 @@ Modules should have their own specific API. When a module currently requires to send messages, the API should reflect semantics instead of providing the module a way to just carry raw messages. For example, there are currently modules able to send messages (with a very simple `MessageToSend message` API), but instead of dealing with raw messages that need to be built inside the module, the API should be more semantic such as `ChangePassword new-password`. -Once modules will have specific APIs, the entire state of the application could be moved into a single module (or *component*) so every state modification can be handled in a single place. +Once modules will have specific APIs, the entire state of the application could be moved into a single module (or *component*). +Thus, every state modification can be handled in a single place. Minor modifications: @@ -17,10 +18,11 @@ Minor modifications: # Features -About zone records: +Delegation: -- allow '@' in record names (replaced by the fqdn, the "root" domain, such as "example.netlib.re.") -- enable to change NS records, but after a accepting the consequences +- new RR record: the "delegation record", effectively removing all other RRs + => requires 2 nameservers +- also enable to change NS records (but after a accepting the consequences)? About the admin interface: